Commit status isn't updated when pushing to existing Pull Request

I've noticed that when an existing Pull Request is updated with new commits, this app doesn't set a commit status until the title is changed (or at least re-saved with the same text). For example, my initial commit here has a correctly-set status but the current head doesn't have any status from wip-bot.

Thanks for reporting the issue! By the way the logs are public in case you run into any trouble. In your case some error occured: https://zeit.co/gr2m/wip-bot/ggkwiearje/logs?redirect=1&query=https%3A%2F%2Fgithub.com%2Fjarrodldavis%2Fprobot-gpg%2Fpull%2F43
I’ll investigate

Ah I get what you mean now, it set the status, but it did not set it again after you pushed a commit

Just ran into this, hope you can do it :beers:

whee I just found out an easy fix for this, thanks to a tip @bkeepers, PR incoming 🎉

this should no be resolved :)


No doco for AbstractControl.valueChanges

Return a 404 for this link
https://angular.io/docs/ts/latest/api/forms/index/AbstractControl.valueChanges

Open an issue at angular/angular. API issues belong there.


Meta modelling

Please include a summary of the change and the issue/story number.
Type of change
Please delete options that are not relevant.

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
This change requires a documentation update

Add unit tests for checking equality between things with/without metadata: (metadata should be ignored)

string with scheme and string with scheme
string with scheme and string without scheme
string with scheme and string with template


Investigate if Edge on iOS/Android has a debugging protocol (and if so add support)

Doesn't look like there's one 😞


Does it have hardware flow contrl function?

No.  Software
On Jan 11, 2017 08:58, "skylin008"<EMAIL_ADDRESS>wrote:

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/plieningerweb/esp8266-software-uart/issues/13, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAdXU2xuvE7WjwiZM7aPOh5-k3pc8V5Lks5rRIuJgaJpZM4LgSef
.


Last chunk size too large

If multiple chunks are created, the last chunk is always larger than the chunk size set in the config.
var r = new Resumable({
    target: function (chunk) {
        console.log(chunk)
        return '/test/'
    },
    query: {},
    maxChunkRetries: 2,
    simultaneousUploads: 1,
    chunkSize: 1 * 1024 * 1024 // 1MB
});

The chunk size is 1MB or 1048576 bytes.
I uploaded a 2.5 MB file, but only two chunks were created. Below are the console logs returned from the target function. The first chunk size matches the chunk size set in the config, but the second chunk size is too large.
I also uploaded a 1096 MB file and all the chunk sizes matched the chunk size set in the config, except the last one, which was too big.
[
  "resumableChunkNumber=1",
  "resumableChunkSize=1048576",
  "resumableCurrentChunkSize=1048576",
  "resumableTotalSize=2459177",
  "resumableType=application%2Fpdf",
  "resumableIdentifier=2459177-March222018-RigorDefectReportpdf",
  "resumableFilename=March%2022%202018%20%20-%20Rigor%20Defect%20Report.pdf",
  "resumableRelativePath=March%2022%202018%20%20-%20Rigor%20Defect%20Report.pdf",
  "resumableTotalChunks=2"
]

[
  "resumableChunkNumber=2",
  "resumableChunkSize=1048576",
  "resumableCurrentChunkSize=1410601",
  "resumableTotalSize=2459177",
  "resumableType=application%2Fpdf",
  "resumableIdentifier=2459177-March222018-RigorDefectReportpdf",
  "resumableFilename=March%2022%202018%20%20-%20Rigor%20Defect%20Report.pdf",
  "resumableRelativePath=March%2022%202018%20%20-%20Rigor%20Defect%20Report.pdf",
  "resumableTotalChunks=2"
]

Closing. Duplicate of https://github.com/23/resumable.js/issues/51


Empty search pages should display a message

The current search results page is blank, and a more link is visible. This is not a great UI.

Fixed


fix: reverse node export conditions

resolves https://github.com/sanity-io/client/issues/308
this tries to fix an issue we're experiencing triggered by the module export condition being added. Because the first matching condition is picked, it would likely be safer to add the import before module bundler.
(I would also suggest removing the module condition as it's not supported by node, and this is within the node condition. But I'm not sure why it was added in the first place so I'm reluctant to make changes.)

Bundlers like Webpack in Next.js target the export condition pattern we're using. We specifically need only nodejs to use the node.import condition because it's the only environment that comprehends the ESM CJS re-export pattern. When bundlers like those in Astro encounter this pattern, they fail. In Next.js, it also bloats the bundle due to added cruft from the re-export and module format change. node.module is a condition ignored by nodejs but targeted by bundlers like webpack. It signals transpilation expectation for bundlers. We use both patterns to avoid issues in native nodejs environments, especially since some dependencies in @sanity/client aren't node-ready.
Regarding your error, it seems to be trying to use node.import rather than node.module. So, removing node.module might not solve the issue.

The error message in the linked run is a little confusing. We use http://github.com/vercel/nft in Nuxt and Nitro to trace dependencies, and it is picking the 'module' condition and only copying the module across, but of course node is looking for the 'import' condition and this file is missing.
I have tested and confirmed this fix works for us (as does removing the 'module' condition entirely) but of course it does need to work for the rest of the ecosystem too. Do you have a Next.js project I can test with to confirm?

We have a matrix you can use. If your nft setup is working optimally and supports the 'module' condition then it shouldn't be hitting the 'node.import' one. I fear the changes in this PR will cause the problem in Astro to regress 😅
Another case that's related and why we've started using node.module in this way: https://github.com/portabletext/react-portabletext/issues/70

We would of course prefer to be able to drop the exports.node condition entirely, but previous attempts have failed 😅

Thanks, that's helpful. FWIW, we don't want the module dependency. We want the import one to be picked as we output native node ESM, which is why I'd suggest moving module below it.

No, we're not using a bundler. We're copying across files to a new tree-shaken node_modules folder.

Copying files without a bundler! I see, then copying ./dist/index.cjs.js and ./dist/index.cjs is what you need for node 👍

Exactly! Check out https://github.com/vercel/nft - it's pretty cool.

Yeah, did an internal search and in one place we're using nft we set these options to:
  conditions: ['module', 'node']

Maybe try that?

There's precedence for it but not a lot of information out there. In fact, there's not a lot of information on how to ship ESM and CJS, or JS that works universally with the current npm ecostystem, is there 😅

Hi @pi0 @danielroe,
Thanks for your feedback. Our initial need for node.module was for Astro compatibility. However, with Astro v3, this issue seems resolved.
While I value the bundlesize savings in frameworks like Next.js, I'll prioritize ecosystem compatibility. If I don't find a workaround by EOD, I'll remove node.module. Thanks for your understanding! 🙌


Mikel & Tyler CSS

-Adding animations
-Further Styling
-Branding & LOGO

close

We can change it if it is better. I had some help from Daniel for set up so
not sure if he knew to merge to develop instead
On Sun, Jun 5, 2022 at 11:34 PM Kevin Fang @.***> wrote:

@.**** requested changes on this pull request.
I think its asking to merge develop into main, maybe it should've been
from feature branch to develop?
—
Reply to this email directly, view it on GitHub
https://github.com/utorteam11/MOAT/pull/16#pullrequestreview-996114184,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXSDRBTUQWN7PHORSKKJY43VNVWVHANCNFSM5X3VYOQQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


nbdev_docs tries to execute code despite skip_exec

I am trying to run nbdev_docs and the conversion keeping failing on a nb which has
#| nbflags skip_exec
import darts

(nb2) devengqc@17-CN0065CL-1:~/git/projects/ubc$ nbdev_docs
[ 1/13] Hydrotrek_Flow_Path_calculation.ipynb
[ 2/13] bldg_along_wtrmainbreak.ipynb
[ 3/13] geojson_polylines.ipynb
[ 4/13] darts.ipynb
Traceback (most recent call last):
  File "/home/devengqc/mambaforge/envs/nb2/lib/python3.9/site-packages/IPython/core/interactiveshell.py", line 3398, in run_code
    exec(code_obj, self.user_global_ns, self.user_ns)
  File "<ipython-input-1-f5d9044e7f0c>", line 1, in <cell line: 1>
ModuleNotFoundError: No module named 'darts'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/home/devengqc/mambaforge/envs/nb2/bin/nbdev_filter", line 8, in <module>
    sys.exit(nbdev_filter())
  File "/home/devengqc/mambaforge/envs/nb2/lib/python3.9/site-packages/fastcore/script.py", line 116, in _f
    return tfunc(**merge(args, args_from_prog(func, xtra)))
  File "/home/devengqc/mambaforge/envs/nb2/lib/python3.9/site-packages/nbdev/cli.py", line 127, in nbdev_filter
    with redirect_stdout(dn): filt.nb_proc(nb).process()
  File "/home/devengqc/mambaforge/envs/nb2/lib/python3.9/site-packages/nbdev/process.py", line 130, in process
    for cell in self.nb.cells: self._process_cell(cell)
  File "/home/devengqc/mambaforge/envs/nb2/lib/python3.9/site-packages/nbdev/process.py", line 111, in _process_cell
    cell = opt_set(cell, proc(cell))
  File "/home/devengqc/mambaforge/envs/nb2/lib/python3.9/site-packages/nbdev/processors.py", line 298, in __call__
    if self.k.exc: raise Exception(f'Error: cell {cell.idx_}:\n{cell.source}') from self.k.exc[1]
Exception: Error: cell 4:
import darts

We've recently made a change to move away from nbflags to instead just using YAML frontmatter . Create a raw cell (preferably at the top of your NB) containing:
---
skip_exec: true
---


NVCC fails when using vscode-cmake-tools and ninja on Windows

Brief Issue Summary
NVCC has been failing to run when building within VSCode and using the Ninja generator on Windows. Changing the generator or running the exact same CMake command line from a terminal works just fine - even the VSCode integrated terminal.
I've noted that this affects;

Enabling CUDA from the CMake project command: project(X CUDA)
Using check_language(CUDA)
Trying to build a previously configured project which invokes nvcc.

With all these situations only failing when invoke from the vscode-cmake-tools extension and using the Ninja generator.
CMake Tools Diagnostics
{
  "os": "win32",
  "vscodeVersion": "1.72.2",
  "cmtVersion": "1.12.27",
  "configurations": [
    {
      "folder": "d:\\projects\\test\\check-cuda",
      "cmakeVersion": "3.24.2",
      "configured": true,
      "generator": "Ninja",
      "usesPresets": false,
      "compilers": {
        "C": "C:/Program Files (x86)/Microsoft Visual Studio/2019/Professional/VC/Tools/MSVC/14.29.30133/bin/Hostx64/x64/cl.exe",
        "CXX": "C:/Program Files (x86)/Microsoft Visual Studio/2019/Professional/VC/Tools/MSVC/14.29.30133/bin/Hostx64/x64/cl.exe"
      }
    }
  ],
  "cpptoolsIntegration": {
    "isReady": true,
    "hasCodeModel": false,
    "activeBuildType": "Debug",
    "buildTypesSeen": [
      "Debug"
    ],
    "requests": [],
    "responses": [],
    "partialMatches": [],
    "targetCount": 0,
    "executablesCount": 0,
    "librariesCount": 0,
    "targets": []
  },
  "settings": [
    {
      "communicationMode": "automatic",
      "useCMakePresets": "auto",
      "configureOnOpen": false
    }
  ]
}

Debug Log
[main] Configuring folder: check-cuda
[main] Saving open files before configure/build
[driver] Start configure
[driver] Running pre-configure checks and steps
[cmakefileapi-driver] Configuring using kit
[cmakefileapi-driver] Invoking CMake C:\Program Files\CMake\bin\cmake.EXE with arguments ["--no-warn-unused-cli","-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON","-DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=TRUE","-DCMAKE_BUILD_TYPE:STRING=Debug","-Sd:/projects/test/check-cuda","-Bd:/projects/test/check-cuda/build","-G","Ninja"]
[proc] Executing command: "C:\Program Files\CMake\bin\cmake.EXE" --no-warn-unused-cli -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=TRUE -DCMAKE_BUILD_TYPE:STRING=Debug -Sd:/projects/test/check-cuda -Bd:/projects/test/check-cuda/build -G Ninja
[cmake] Not searching for unused variables given on the command line.
[cmake] STDOUT:
[cmake] d:\projects\test\check-cuda\build>call "C:/Program Files (x86)/Microsoft Visual Studio/2019/Professional/VC/Tools/MSVC/14.29.30133/bin/HostX64/x64/../../../../../../../VC/Auxiliary/Build/vcvars64.bat"
[cmake] **********************************************************************
[cmake] ** Visual Studio 2019 Developer Command Prompt v16.11.20
[cmake] ** Copyright (c) 2021 Microsoft Corporation
[cmake] **********************************************************************
[cmake] #$ C:/Program Files (x86)/Microsoft Visual Studio/2019/Professional/VC/Tools/MSVC/14.29.30133/bin/HostX64/x64/../../../../../../../VC/Auxiliary/Build/vcvars64.bat
[cmake] nvcc fatal   : Could not set up the environment for Microsoft Visual Studio using 'C:/Program Files (x86)/Microsoft Visual Studio/2019/Professional/VC/Tools/MSVC/14.29.30133/bin/HostX64/x64/../../../../../../../VC/Auxiliary/Build/vcvars64.bat'
[cmake]
[cmake] STDERR: The input line is too long.
[cmake] -- Configuring done
[cmake] The syntax of the command is incorrect.
[cmake]
[cmake] -- Generating done
[cmake] -- Build files have been written to: D:/projects/test/check-cuda/build
[cmakefileapi-parser] Read reply folder: d:\projects\test\check-cuda\build\.cmake\api\v1\reply
[cmakefileapi-parser] Found index files: ["cache-v2-8bdb1868777d35eaa737.json","cmakeFiles-v1-cd0e12a8d8786ce9bc1b.json","codemodel-v2-5c2cef2c6329c1e141f5.json","directory-.-Debug-d0094a50bb2071803777.json","index-2022-10-31T23-54-47-0228.json","toolchains-v1-3cab24418fee7e253880.json"]
[cache] Reading CMake cache file d:/projects/test/check-cuda/build/CMakeCache.txt
[cache] Parsing CMake cache string
[visual-studio] OK running C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Auxiliary\Build\vcvarsall.bat x64, env vars: {"DevEnvDir":"C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\Common7\\IDE\\","Framework40Version":"v4.0","FrameworkDir":"C:\\Windows\\Microsoft.NET\\Framework64\\","FrameworkDIR64":"C:\\Windows\\Microsoft.NET\\Framework64\\","FrameworkVersion":"v4.0.30319","FrameworkVersion64":"v4.0.30319","INCLUDE":"C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\VC\\Tools\\MSVC\\14.29.30133\\ATLMFC\\include;C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\VC\\Tools\\MSVC\\14.29.30133\\include;C:\\Program Files (x86)\\Windows Kits\\NETFXSDK\\4.8\\include\\um;C:\\Program Files (x86)\\Windows Kits\\10\\include\\10.0.22000.0\\ucrt;C:\\Program Files (x86)\\Windows Kits\\10\\include\\10.0.22000.0\\shared;C:\\Program Files (x86)\\Windows Kits\\10\\include\\10.0.22000.0\\um;C:\\Program Files (x86)\\Windows Kits\\10\\include\\10.0.22000.0\\winrt;C:\\Program Files (x86)\\Windows Kits\\10\\include\\10.0.22000.0\\cppwinrt","LIB":"C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\VC\\Tools\\MSVC\\14.29.30133\\ATLMFC\\lib\\x64;C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\VC\\Tools\\MSVC\\14.29.30133\\lib\\x64;C:\\Program Files (x86)\\Windows Kits\\NETFXSDK\\4.8\\lib\\um\\x64;C:\\Program Files (x86)\\Windows Kits\\10\\lib\\10.0.22000.0\\ucrt\\x64;C:\\Program Files (x86)\\Windows Kits\\10\\lib\\10.0.22000.0\\um\\x64;C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\VC\\Tools\\MSVC\\14.29.30133\\ATLMFC\\lib\\x64;C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\VC\\Tools\\MSVC\\14.29.30133\\lib\\x64;C:\\Program Files (x86)\\Windows Kits\\NETFXSDK\\4.8\\lib\\um\\x64;C:\\Program Files (x86)\\Windows Kits\\10\\lib\\10.0.22000.0\\ucrt\\x64;C:\\Program Files (x86)\\Windows Kits\\10\\lib\\10.0.22000.0\\um\\x64","LIBPATH":"C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\VC\\Tools\\MSVC\\14.29.30133\\ATLMFC\\lib\\x64;C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\VC\\Tools\\MSVC\\14.29.30133\\lib\\x64;C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\VC\\Tools\\MSVC\\14.29.30133\\lib\\x86\\store\\references;C:\\Program Files (x86)\\Windows Kits\\10\\UnionMetadata\\10.0.22000.0;C:\\Program Files (x86)\\Windows Kits\\10\\References\\10.0.22000.0;C:\\Windows\\Microsoft.NET\\Framework64\\v4.0.30319;C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\VC\\Tools\\MSVC\\14.29.30133\\ATLMFC\\lib\\x64;C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\VC\\Tools\\MSVC\\14.29.30133\\lib\\x64;C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\VC\\Tools\\MSVC\\14.29.30133\\lib\\x86\\store\\references;C:\\Program Files (x86)\\Windows Kits\\10\\UnionMetadata\\10.0.22000.0;C:\\Program Files (x86)\\Windows Kits\\10\\References\\10.0.22000.0;C:\\Windows\\Microsoft.NET\\Framework64\\v4.0.30319","NETFXSDKDir":"C:\\Program Files (x86)\\Windows Kits\\NETFXSDK\\4.8\\","Path":"C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\Common7\\IDE\\\\Extensions\\Microsoft\\IntelliCode\\CLI;C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\VC\\Tools\\MSVC\\14.29.30133\\bin\\HostX64\\x64;C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\Common7\\IDE\\VC\\VCPackages;C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\Common7\\IDE\\CommonExtensions\\Microsoft\\TestWindow;C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\Common7\\IDE\\CommonExtensions\\Microsoft\\TeamFoundation\\Team Explorer;C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\MSBuild\\Current\\bin\\Roslyn;C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\Team Tools\\Performance Tools\\x64;C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\Team Tools\\Performance Tools;C:\\Program Files (x86)\\Microsoft Visual Studio\\Shared\\Common\\VSPerfCollectionTools\\vs2019\\\\x64;C:\\Program Files (x86)\\Microsoft Visual Studio\\Shared\\Common\\VSPerfCollectionTools\\vs2019\\;C:\\Program Files (x86)\\Microsoft SDKs\\Windows\\v10.0A\\bin\\NETFX 4.8 Tools\\x64\\;C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\Common7\\IDE\\CommonExtensions\\Microsoft\\FSharp\\Tools;C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\Common7\\Tools\\devinit;C:\\Program Files (x86)\\Windows Kits\\10\\bin\\10.0.22000.0\\x64;C:\\Program Files (x86)\\Windows Kits\\10\\bin\\x64;C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\\\MSBuild\\Current\\Bin;C:\\Windows\\Microsoft.NET\\Framework64\\v4.0.30319;C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\Common7\\IDE\\;C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\Common7\\Tools\\;C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\Common7\\IDE\\\\Extensions\\Microsoft\\IntelliCode\\CLI;C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\VC\\Tools\\MSVC\\14.29.30133\\bin\\HostX64\\x64;C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\Common7\\IDE\\VC\\VCPackages;C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\Common7\\IDE\\CommonExtensions\\Microsoft\\TestWindow;C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\Common7\\IDE\\CommonExtensions\\Microsoft\\TeamFoundation\\Team Explorer;C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\MSBuild\\Current\\bin\\Roslyn;C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\Team Tools\\Performance Tools\\x64;C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\Team Tools\\Performance Tools;C:\\Program Files (x86)\\Microsoft Visual Studio\\Shared\\Common\\VSPerfCollectionTools\\vs2019\\\\x64;C:\\Program Files (x86)\\Microsoft Visual Studio\\Shared\\Common\\VSPerfCollectionTools\\vs2019\\;C:\\Program Files (x86)\\Microsoft SDKs\\Windows\\v10.0A\\bin\\NETFX 4.8 Tools\\x64\\;C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\Common7\\IDE\\CommonExtensions\\Microsoft\\FSharp\\Tools;C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\Common7\\Tools\\devinit;C:\\Program Files (x86)\\Windows Kits\\10\\bin\\10.0.22000.0\\x64;C:\\Program Files (x86)\\Windows Kits\\10\\bin\\x64;C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\\\MSBuild\\Current\\Bin;C:\\Windows\\Microsoft.NET\\Framework64\\v4.0.30319;C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\Common7\\IDE\\;C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\Common7\\Tools\\;C:\\Program Files\\PowerShell\\7;C:\\Program Files\\Microsoft\\jdk-<IP_ADDRESS>-hotspot\\bin;C:\\VulkanSDK\\<IP_ADDRESS>\\Bin;C:\\Program Files (x86)\\Intel\\oneAPI\\tbb\\latest\\redist\\intel64\\vc_mt\\;C:\\Program Files (x86)\\Intel\\oneAPI\\tbb\\latest\\redist\\ia32\\vc_mt\\;C:\\Program Files (x86)\\Intel\\oneAPI\\compiler\\latest\\windows\\redist\\intel64_win\\compiler;C:\\Program Files (x86)\\Intel\\oneAPI\\compiler\\latest\\windows\\redist\\ia32_win\\compiler;C:\\Program Files (x86)\\IntelSWTools\\system_studio_2020\\OpenCL\\sdk\\bin\\x64;C:\\Program Files (x86)\\IntelSWTools\\system_studio_2020\\OpenCL\\sdk\\bin\\x86;C:\\Program Files\\NVIDIA GPU Computing Toolkit\\CUDA\\v11.5\\bin;C:\\Program Files\\NVIDIA GPU Computing Toolkit\\CUDA\\v11.5\\libnvvp;C:\\Windows\\system32;C:\\Windows;C:\\Windows\\System32\\Wbem;C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\;C:\\Windows\\System32\\OpenSSH\\;C:\\Program Files\\PuTTY\\;C:\\ProgramData\\chocolatey\\bin;C;C:\\Program Files\\Microsoft VS Code\\bin;C:\\Program Files\\dotnet\\;C:\\Program Files\\NVIDIA Corporation\\Nsight Compute 2021.3.1\\;C:\\Program Files (x86)\\NVIDIA Corporation\\PhysX\\Common;C:\\WINDOWS\\system32;C:\\WINDOWS;C:\\WINDOWS\\System32\\Wbem;C:\\WINDOWS\\System32\\WindowsPowerShell\\v1.0\\;C:\\WINDOWS\\System32\\OpenSSH\\;C;C;C:\\Program Files\\PowerShell\\7\\;C:\\Program Files\\nodejs\\;C:\\Program Files\\Git\\cmd;<snip>;d:\\Omniverse\\Library\\isaac_sim-2022.1.1;C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\VC\\Tools\\Llvm\\x64\\bin;C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\Common7\\IDE\\CommonExtensions\\Microsoft\\CMake\\CMake\\bin;C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\Common7\\IDE\\CommonExtensions\\Microsoft\\CMake\\Ninja;C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\Common7\\IDE\\VC\\Linux\\bin\\ConnectionManagerExe;C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\VC\\Tools\\Llvm\\x64\\bin;C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\Common7\\IDE\\CommonExtensions\\Microsoft\\CMake\\CMake\\bin;C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\Common7\\IDE\\CommonExtensions\\Microsoft\\CMake\\Ninja;C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\Common7\\IDE\\VC\\Linux\\bin\\ConnectionManagerExe","UCRTVersion":"10.0.22000.0","UniversalCRTSdkDir":"C:\\Program Files (x86)\\Windows Kits\\10\\","VCIDEInstallDir":"C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\Common7\\IDE\\VC\\","VCINSTALLDIR":"C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\VC\\","VCToolsRedistDir":"C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\VC\\Redist\\MSVC\\14.29.30133\\","VisualStudioVersion":"16.0","VSINSTALLDIR":"C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Professional\\","WindowsLibPath":"C:\\Program Files (x86)\\Windows Kits\\10\\UnionMetadata\\10.0.22000.0;C:\\Program Files (x86)\\Windows Kits\\10\\References\\10.0.22000.0","WindowsSdkBinPath":"C:\\Program Files (x86)\\Windows Kits\\10\\bin\\","WindowsSdkDir":"C:\\Program Files (x86)\\Windows Kits\\10\\","WindowsSDKLibVersion":"10.0.22000.0\\","WindowsSDKVersion":"10.0.22000.0\\","WindowsSDK_ExecutablePath_x64":"C:\\Program Files (x86)\\Microsoft SDKs\\Windows\\v10.0A\\bin\\NETFX 4.8 Tools\\x64\\","WindowsSDK_ExecutablePath_x86":"C:\\Program Files (x86)\\Microsoft SDKs\\Windows\\v10.0A\\bin\\NETFX 4.8 Tools\\","TMP":"<snip>"}
[extension] [8101] cmake.configure finished (returned 0)

Additional Information
I've distilled this down to a very simple CMake script which shows the failure. Hopefully the following steps will reproduce the issue on other Windows computers:

Open the folder containing the attached CMakeLists.txt file in VSCode
Set the CMake generator to Ninja: "cmake.generator": "Ninja" in settings.json
Open the command palette and run CMake: Configure
Observe the failure in the Output window
From the top of the Output window, copy the CMake command line.
Open the VSCode Integrated Terminal
Paste and run the copied command line
Observe the expected, successful behaviour

The diagnostics (attached) seem to cover most of the relevant items, but I'll add the Ninja version is 1.10.2.
The failure output I observe has been added to the Debug Log requested (with "cmake.loggingLevel": "debug" set) modified slightly for some path sanitisation.
CMakeLists.txt

Sorry, we're not CUDA experts here and have been trying to get your repro to print out the same thing you shared, but have not been successful.  nvcc seems to depend on the MSVC environment being pre-set since it depends on cl.exe.  This is something we do for projects that build with the Visual Studio compiler, and use the Ninja generator.
Are you using Kits or CMakePresets to select the compiler/environment?  When I pick the [Unspecified] Kit I get one error, but if I pick a Visual Studio Kit, the build environment is correctly set up for Ninja and I get an error with your execute_process command: "nvcc fatal   : Don't know what to do with '__cmake_determine_cuda'".  I have CUDA 11.8.  This suggests that we are correctly setting up the environment when the Visual Studio Kit is selected.
Looking at your log, CMake seems to complete the configuration despite the error printed out by vcvars64, so CMake doesn't generate a failure log that we can look at.  I'm not really sure where to look next since we don't see what you're seeing.

Hi Bob,
Thanks for looking at this.

Looking at your log, CMake seems to complete the configuration despite the error printed out by vcvars64

That's a red herring in this case. I've just distilled the issue down to the minimal case. This will fail to configure when using enable_language(CUDA) or project(X CUDA).
As for kits, I'm using a Visual Studio Kit, but I think there are some additional environmental factors here. Playing with the kits and the launch environment, I can replicate the error you see. I think my attempt to distil a minimal CMake which shows the error is wrong. The following configuration highlights the issue better, but obscures the cause (i.e., the command line being too long).
cmake_minimum_required(VERSION 3.18)
project(CheckCUDA)
include(CheckLanguage)
enable_language(CUDA)

Make sure to clear the build directory each time as once it succeed it will continue to succeed.
I've done a bit more digging and I suspect this is more an nvcc issue (I'll follow up there). Also, I think I can identify the cause and why it can fail from the VSCode extension while working from the VSCode terminal. The breakdown follows.
As far as I can tell, the cause is the PATH environment variable. There's a point at which this gets to be "too long" for whatever nvcc does - likely the Windows MAX_PATH continues its haunting. I hypothesise I'm seeing this occur from within the VSCode CMake extension, but not the VSCode terminal because;

I tend to start VSCode from a Visual Studio command line environment, so the PATH includes Visual Studio paths.
This PATH is still ok for nvcc, so I can configure cmake from the VSCode terminal (which inherits the command line I started VSCode from).
The VSCode plugin fails because it appends more stuff to the PATH.

Specifically I noticed that the PATH variable contents from the VSCode CMake extension and the terminal contained the same information, but the extension added the Visual Studio paths a second time. I propose this then blows out the PATH and nvcc fails. I was able to replicate the failure in the terminal by making the PATH bigger. In powershell I set: $env:PATH=$env:PATH + ";" + $env:PATH.
At this point, the best I can suggest that maybe the CMake extension could filter the PATH environment variable and remove duplicates, but that may have side effects. I guess I need to follow up with NVIDIA.

I should add, I know ninja is afflicted by the windows path limit legacy, so it may be that's the issue not nvcc. Hard to know where to take this next.

If you start VS Code from a Visual Studio Developer Command prompt, trying using the [Unspecified] Kit so that we don't add the VS paths again.
I would think having a long PATH variable is different from having a path in the PATH that is too long.  I thought the problem was the latter, not the former, but maybe nvcc does have some limit.  Most PATH's that I see are longer than MAX_PATH.  Env variables in Windows 10 have a higher character limit than that.  I want to say that it's MAX_SHORT or something like that.

There's a nice tip in there; I played around with using the [Unspecified] Kit when launching from the VS Dev prompt and that avoids the issue. Likewise, starting VSCode from explorer - i.e., not a VS Dev prompt - and selecting the VS kit also works. I can use these as a workaround. The main reason I'd still start from a VS Dev prompt is when I am also using another environment based library such as ROS.
I'm still not sure where to take this next; is it Ninja - known to have path length limitations on Windows - or nvcc? I'll sit on it for now.
Thanks for the help.


When search_engine='rxivist', it does not still show papers from medrxiv

br = BiorxivRetriever(search_engine='rxivist')
papers = br.query("...", metadata=True, full_text=False)

Even, in this case, it shows only papers from Biorxiv but not from Medrxiv.
However, if I make the same query on rxivist web site (downloads, all time, 100 results per page, all repos), I see papers from Medrxiv as well.
You can use "D614G" as the query string to reproduce the problem.
Regards

Hi. Thanks for your suggestions. Please feel free to submit a pull request and I will review it.
Thank you


SetColWidth changes font in the column

Hi,
I'm running v2.0.2 and when I do:
	f := excelize.NewFile()

	index := f.NewSheet("TestSheet")
	f.SetColWidth("TestSheet", "B", "B", 20)

	f.SetCellValue("TestSheet", "B2", "Hello there!")
	f.SetActiveSheet(index)
	// f.SetDefaultFont("Liberation Sans")

	if err := f.SaveAs("Book1.xlsx"); err != nil {
		println(err.Error())
	}

it changes the width, but also seems to have "Calibri" font, and now 11px size and not 10px which seems to be the default for me. I open the file in LibreOffice. If I also do the commented out row there, it goes back to what seems to be the default font for me.
I would expect it to not change the font, so what am I missing here? Oh, and yes, not doing the SetColWidth it doesn't change the font.
Thanks!

seems excelize is unable to deal with format of cell. only reading and writing string value

Are you able to reproduce the issue?

Hi @Chillance, "Calibri" is the default font for new worksheets. I have tested and it works well at version 2.0.2, have you tried using the latest code on the master branch? or provide a .xlsx file attachment.

Hi @Chillance, it seems still not have enough info on this issue,  I'll close this issue, if you have any questions, please let me know.


Replace relative imports from tutorial with absolute imports to avoid crashes

I had been following the official FastAPI tutorials and I have had many bugs. After some time understanding them and trying to fix, I saw they were due to the usage of relative imports.
Two person in my team had this problem independently and took some hours and tweaks to make a hack to this issue. In stackoverflow i also found many people having headches due to relative imports.
Only later I have found that PEP8 warns about pitfalls of relative imports and strongly advice for usage of absolute imports. After trying this, my code of the FastAPI tutorial worked.
Could you please use absolute imports in your tutorial to avoid this recurrent problem?
Thanks!
Source of recomendation of absolute imports over relative:
https://www.python.org/dev/peps/pep-0008/

Which tutorials?

The ones in fastapi.tiangolo.com.
From those examples, people in team stared to make more adventurous relative imports and having crashes.
For example:
https://fastapi.tiangolo.com/tutorial/sql-databases/

https://fastapi.tiangolo.com/tutorial/testing/:

Good , you can open a PR :)

How did you fix this? I want to dockerize the thing from the tutorial but don't want to go creating a whole package to fix the issue with imports.

I'm not sure I understand why creating a package is difficult here, or even required? You can update the code you copy from examples to not use relative imports

I'm actually quite curious what the best practice is.
It seems very common that projects don't install as a package but use relative imports.
In the full stack example the PYTHONENV variable is set to give fully qualified imports without installing: https://github.com/tiangolo/full-stack-fastapi-postgresql/blob/master/{{cookiecutter.project_slug}}/backend/backend.dockerfile
Is there any reason not to install app as a package? It would be useful in my case because I want to grab the metadata info from the package (e.g. version)

I got this problem too. Whole app run properly but when it comes to running the package alone, there will be a problem.

I had the same problems described in this thread...
following the SQLDATABASES tutorial
mentioned above and the same thing happened...
fixing and tweaking a bit I got it to work without making much change to the file structure...
I already sent a PR... https://github.com/tiangolo/fastapi/pull/4510
I tried the tutorial application in normal mode with VIRTUALENV and with DOCKER and it runs perfectly...
i'm new to 'contributions' so if someone could give some kind of feedback would be great...
I did my best to explain what are the problems that I have when I follow the tutorial as it is... and add some photos too... I don't know if it's ok like this...

Absolute imports would also not solve it. That would mean that each of your Python files is an independent module, but they would still need to be able to find the other Python modules, so the same rules of Python imports would apply. It depends on the environment, the place from where you run your Python code, and if you have the proper directory and file structures with __init__.py files.
If you follow the tutorial from the beginning without skipping sections, you would see that the file structure is explained: https://fastapi.tiangolo.com/tutorial/sql-databases/#file-structure
And then you can see that it's used later taking into account that there's a top level directory (package) sql_app: https://fastapi.tiangolo.com/tutorial/sql-databases/#check-it


Typo fix

Changed the word "that" to "than" in the following sentence:
(for query types such a property is typed as DbQuery<T> rather that DbSet<T>)

Thanks @Sojaner!


Add tool to loop over sets of pairings, saving out a netcdf for each

This adds a function to loop over pairings, saving a paired netcdf file for each set.
This is currently intended for aircraft but I wrote it in a way that it should work for other types of pairings as well. The best way I could think of to do this was to make the user always provide a mapping between the obs and corresponding model files. This avoids having to do any complicated logic of finding the right model files for each obs file, which might need to be written specific to each model.
Currently the mapping between obs and model files for each pairing is provided as either a dict or a separate yaml file.
There is also another function to read a list of obs files and then give back the time bounds of each, so that it is easier for the user to assemble matching model files.

One thing that I wanted to get feedback on is the handling of variable names with some special characters from the obs dataset. For example, in the firexaq R1 data, there are variable names that contain / and &, neither of which can be used in a netcdf variable name. Currently I just drop any variables with those characters when saving but that isn't preferable. I could change it to error out when this happens or give a warning when certain variables have been dropped. I think that the user could provide a yaml that renames specific obs variables so that this doesn't happen once they've been warned about it.

@colin-harkins, is it possible to add an attribute to netcdf like how the units are added named something like long_name. Then in all cases just repeat the variable name in the long_name field. And for any characters that are not allowed in netcdf variable names, can you just drop those characters in the variable name, but they would still be listed in the long_name for reference later on. I've seen this done in the ATom netcdf files and this should work well for our purposes and we can explain this in our documentation. I feel like other items are going to fail if we keep characters like this in the variable names too like titles of plots, so best just to drop characters like this now. What do you think?

@rschwant I think that is a great solution. I'll implement that today and update the PR.

@colin-harkins This PR works well for develop_aircraft plots.
Just wanted to ask that did you remove this yaml file intentionally in this PR: loop_pairing(control=control_fn,file_pairs_yaml='**aircraft_looping_file_pairs.yaml**')
Since, this is in the examples/jupyter_notebooks/Monet-example_aircraft_pairing_loop.ipynb but doesn't work as the yaml file isn't present.  (if this feature doesn;t work anymore you can remove it in the notebook)
Beside the above clarification , i am going ahead to approve the PR as i can see the pairing netcdf files for different files created with variable names that contain / and & ,such as: Cl_ug/m3_DIBB' being present.

I made changes to address the comments from @rschwant  and @quaz115.

aircraft_looping_file_pairs.yaml is now included in a subfolder for supplementary yaml files

When providing a control file for the looping, many of the fields I previously had in the file are not necessary. I've commented those out in the updated version. For start_time and end_time, the fields are not necessary for the looping and are only necessary for plotting and one of the satellite pairing options. To reduce confusion, I made start_time and end_time optional in the control yaml file. Let me know what you think about this, but I don't think it will cause issues to make them optional.

I provided a .py file in the submit_jobs folder that I've tested on hera with this code

I provided a jupyter notebook and control yaml that demonstrate reading in the sets of paired observations. It works pretty much the same as the read analysis examples, but uses the netcdf files generated by the aircraft pairing loop. The only issue here is reading in model and obs data. Currently there is no functionality for reading in multiple icartt files, so the control file I made just uses a single day. This doesn't really affect the example and I can work on adding the functionality for reading multiple icartt files in the same control file in the future or I can try to add that to this PR as well. The jupyter notebook provided also makes a timeseries plot as a basic demonstration that this is working.

I still need to come up with a way to handle some of the plotting that requires analysis.models and analysis.obs directly rather than just analysis.paired, because reading in an entire campaigns worth of model data when plotting is just not really feasible in some cases. I think that is something that can be addressed in the future once develop_aircraft is merged into develop.
If this looks good to you, I'll merge it in and then start a PR for develop_aircraft into the develop branch.

@rschwant Thanks for looking at this. I'll merge and make a pull request into develop today.


Use DNSimple official Go client

Hi I work at DNSimple. We're helping OSS projects to migrate to our newer API clients.
I noticed that you are using github.com/weppos/dnsimple-go, which points to our deprecated API v1. This PR introduces github.com/dnsimple/dnsimple-go, our official client that points to our new API v2.
Read more at: https://blog.dnsimple.com/2016/12/api-v2-stable/
Thanks ✌

Thank you! :)


fix: make subscribers of store changes async

fix https://github.com/pmndrs/jotai/issues/2211
I am not familiar with this repo, so I just search all the devSubscribeStore.

Not sure if I find all the places that need a fix.
The tests are broken, I haven't taken a look yet.

Need more guidance 😅

on second thought, it might be better to detect if it's sync, and only delay if necessary.

let isRendering = true;
useLayoutEffect(() => {
  isRendering = false;
});
const callback = () => {
  const fn = () => setAtoms(Array.from(store.dev_get_mounted_atoms?.() || []));
  if (isRendering) {
    Promise.resolve().then(fn)
  } else {
    fn()
  }
};

let isRendering = true;
useLayoutEffect(() => {
  isRendering = false;
});

Tricky 😆, let me refactor it.

const isRendering = useRef(true);
useLayoutEffect(() => {
  isRendering.current = false;
});

Should it be useRef?

Now one test fails:
● DevTools - AtomViewer › List of atoms › auto unmount › should unselect the atom when an atom is unsubscribed

const isRendering = useRef(true);
useLayoutEffect(() => {
  isRendering.current = false;
});

Should it be useRef?

No, that's incorrect. Using the local variable is necessary.

const isRendering = useRef(true);
useLayoutEffect(() => {
  isRendering.current = false;
});

Should it be useRef?

No, that's incorrect. Using the local variable is necessary.

That was my oversight. In this case, we need useRef, and violate a rule of purity.
const isRendering = useRef(true);
isRendering.current = true; // This violates the purity.
useLayoutEffect(() => {
  isRendering.current = false;
});

Looks good to me as well! Thanks so much for your contribution!
Could you please help us test this on NextJs and non-NextJS applications?
You may fork these CSBs (Non-NextJS and NextJS) to save some time 🙌

@arjunvegda seems I cannot fork the cra sandbox

We were unable to fork the sandbox
Cannot fork protected sandbox out of workspace

https://codesandbox.io/p/sandbox/jotai-devtools-demo-next-forked-g6fncd
This is the forked nextjs version. Does it expose the browser devtool console? I didn't upgrade packages yet but I cannot see it anywhere

CodeSandbox is really annoying. Whenever I tried to upgrade a package, the .next cache does not change and a require of the stale chunk would fail.  I don't know what to do.

CodeSandbox is really annoying. Whenever I tried to upgrade a package, the .next cache does not change and a require of the stale chunk would fail.  I don't know what to do.

Sorry for the delayed response. Could you try running it locally? I've been bitten by that error before too. Seems caching specific

@yf-yang What's the current status?

@dai-shi Stuck here

CSB, unable to fork/unable to install the branch
install github branch from a local folder, is it viable? I can't make it work
install from another prereleased local folder, still struggling with multiple react issue.

Thanks.
@arjunvegda What do you think our options are?

Maybe I need some guidance, how do you release a branch as a npm installable cloud url? I remember you did that with jotai-scope, but I am not so familiar with the package release stuff.

Cool, will get back to you tmr.

OK, have got both tested with https://pkg.csb.dev/jotaijs/jotai-devtools/commit/6cac845d/jotai-devtools

@arjunvegda Could the patch be merged?


Possible deadlock in catkin build

I apologize in advance for this very imprecise bug report.
I noticed that, starting with the new version 0.4.x, caktin build will hang sometimes. It happens while processing a random package and very rarely (I'd say 3 out of 100 builds on our Jenkins). Also, it will run just fine if I cancel and reschedule the build.
I stumbled upon the --no-install-lock option, which I just added to our build script in the hope that it will resolve this issue. I won't be able to tell until sufficiently many builds have run, obviously.
In case anyone has an idea where to look for this problem, our build script runs the following commands:
catkin config -w ros --init --no-blacklist --install -j4 -p4 --cmake-args -DCMAKE_BUILD_TYPE=Debug -DCMAKE_C_COMPILER=/usr/lib/ccache/gcc -DCMAKE_C_FLAGS_DEBUG="-fmessage-length=0 -Wall -Wextra -Wno-unused-parameter -Wno-ignored-qualifiers -Wno-error=deprecated-declarations -Wno-error=unused-variable -Wno-error=unused-but-set-variable -O0" -DCMAKE_CXX_COMPILER=/usr/lib/ccache/g++ -DCMAKE_CXX_FLAGS_DEBUG="-fmessage-length=0 -Wall -Wextra -Wno-unused-parameter -Wno-ignored-qualifiers -Wno-invalid-offsetof -Wno-unused-local-typedefs -Wno-error=deprecated-declarations -Wno-error=unused-variable -Wno-error=unused-but-set-variable -O0" -DCMAKE_SHARED_LINKER_FLAGS_DEBUG="-Wl,-z,defs" -DCMAKE_EXE_LINKER_FLAGS_DEBUG="-Wl,-z,defs"
catkin clean -w ros --all --yes
catkin build -w ros --verbose --no-status --no-notify --continue-on-failure

The last command outputs:
--------------------------------------------------------------------------------
Profile:                     default
Extending:             [env] /opt/ros/indigo
Workspace:                   /home/jenkins/ros
--------------------------------------------------------------------------------
Source Space:       [exists] /home/jenkins/ros/src
Log Space:         [missing] /home/jenkins/ros/logs
Build Space:        [exists] /home/jenkins/ros/build
Devel Space:        [exists] /home/jenkins/ros/devel
Install Space:     [missing] /home/jenkins/ros/install
DESTDIR:            [unused] None
--------------------------------------------------------------------------------
Devel Space Layout:          merged
Install Space Layout:        merged
--------------------------------------------------------------------------------
Additional CMake Args:       -DCMAKE_BUILD_TYPE=Debug -DCMAKE_C_COMPILER=/usr/lib/ccache/gcc -DCMAKE_C_FLAGS_DEBUG=-fmessage-length=0 -Wall -Wextra -Wno-unused-parameter -Wno-ignored-qualifiers -Wno-error=deprecated-declarations -Wno-error=unused-variable -Wno-error=unused-but-set-variable -O0 -DCMAKE_CXX_COMPILER=/usr/lib/ccache/g++ -DCMAKE_CXX_FLAGS_DEBUG=-fmessage-length=0 -Wall -Wextra -Wno-unused-parameter -Wno-ignored-qualifiers -Wno-invalid-offsetof -Wno-unused-local-typedefs -Wno-error=deprecated-declarations -Wno-error=unused-variable -Wno-error=unused-but-set-variable -O0 -DCMAKE_SHARED_LINKER_FLAGS_DEBUG=-Wl,-z,defs -DCMAKE_EXE_LINKER_FLAGS_DEBUG=-Wl,-z,defs
Additional Make Args:        -j4
Additional catkin Make Args: None
Internal Make Job Server:    True
Cache Job Environments:      False
--------------------------------------------------------------------------------
Whitelisted Packages:        None
Blacklisted Packages:        None
--------------------------------------------------------------------------------
Workspace configuration appears valid.

@roehling Can you re-open this in the catkin_tools project? https://github.com/catkin/catkin_tools/issues/new

Agreed, please open on catkin_tools's issue tracker. I'll close this for now.
Also, the --no-install-lock option is dangerous because it can result in sporadic errors when two builds try to write the same file at the same time. I don't think it will help your problem. There is no state that I'm aware of that could cause deadlock between install steps (individual install steps don't depend on each other to complete themselves).

Oops, my bad, that was supposed to be in catkin_tools


Introducing GoFr Guru on Gurubase.io

Hello team,
I'm the maintainer of Anteon. We have created Gurubase.io with the mission of building a centralized, open-source tool-focused knowledge base. Essentially, each "guru" is equipped with custom knowledge to answer user questions based on collected data related to that tool.
I wanted to update you that I've manually added the GoFr Guru to Gurubase. GoFr Guru uses the data from this repo and data from the docs to answer questions by leveraging the LLM.
In this PR, I showcased the "GoFr Guru", which highlights that GoFr now has an AI assistant available to help users with their questions. Please let me know your thoughts on this contribution.
Additionally, if you want me to disable GoFr Guru in Gurubase, just let me know that's totally fine.

@kursataktas Thank you for adding Gofr to Gurubase, I tried it out and it works nice and it is a good way to get contextual answers for specific problems.

Hi @vipul-rawat ,
I’d like to update you on the release of the Maintainer Panel feature on Gurubase. With this panel, you can add, remove, or update data sources, as well as change the logo and more. You can find the details here.
In the near future, I’m planning to include analytics insights in this panel, such as the number of questions asked, the most frequently asked ones, and more. I’ll be sure to update this thread once it’s available. However, in case I miss it, I highly recommend joining our Discord channel to stay updated.
If you’d prefer that I don’t update this thread anymore, please let me know.


[Launcher]: Refine ExitDiagnostics

Coverage remained the same at 80.249% when pulling b11e6e3ed260e7a16f6ada0c4059d0458c52c47f on yqwang/launcher-dev into 2715a36f7589dca1896063d4de93d9d9eb832178 on master.


ARTEMIS-1784 JDBC NodeManager should just use DMBS clock

It avoid using the system clock to perform the locks logic
by using the DBMS time.
It contains several improvements on the JDBC error handling
and an improved observability thanks to debug logs.

These 3 Pull Requests are all about JDBC... it would be a lot easier if you posted a single Pull Request with JDBC Changes with 3 commits on it. A lot easier to manage


Add builds for arm64

This PR adds arm64 builds for alpine and base linux.
It would be extremely useful to have them (arm64 binaries) for the just released 0.7.4 tag, if feasible.

@jwilder ping ?

@jwilder Is there anything blocking the merge of this PR ?

@buchdag Nope.  Just fell off my radar.  Thanks!

Thanks for the merge.
Could you please also take a look at https://github.com/jwilder/nginx-proxy/pull/984 ? It won't take more than one minute of your time and would fix something that was supposed to work out of the box (automatic OCSP stapling with nginx-proxy + letsencrypt-nginx-proxy-companion).


feat: all public SDK functions using background queue

PR that partially closes https://github.com/customerio/issues/issues/6675. There will be multiple PRs to get that milestone crossed. I am making multiple PRs to make the (large) milestone easier to review.
Until https://github.com/customerio/customerio-android/pull/68 is merged, this will give you the changes only in this PR.
Complete each step to get your pull request merged in. Learn more about the workflow this project uses.

[ ] merge https://github.com/customerio/customerio-android/pull/68
[x] Assign members of your team to review the pull request.
[x] Wait for pull request status checks to complete. If there are problems, fix them until you see that all status checks are passing.
[ ] Wait until the pull request has been reviewed and approved by a teammate
[ ] After pull request is approved, and you determine it's ready add the label "Ready to merge" to the pull request and it will automatically be merged.

Pull request title looks good 👍. If this pull request gets merged, it will cause a new release of the software.
Example: If this project's latest release version is 1.0.0. If this pull request gets merged in, the next release of this project will be 1.1.0.
To merge this pull request, add the label Ready to merge to this pull request and I'll merge it for you.

PR blocked until https://github.com/customerio/customerio-android/pull/68 is unblocked

No longer blocked and ready for review.


Added create table functionality

:tada: This PR is included in version 1.0.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Extend TableMetadata model to accept KV pairs attributes

Summary of Changes
Sometimes we would like the table metadata model to accept additional attributes(like URI, retention, owner, etc). This PR extends to model to store those additional attributes inside the node.
Tests
What tests did you add or modify and why? If no tests were added or modified, explain why. Remove this line
Documentation
What documentation did you add or modify and why? Add any relevant links then remove this line
CheckList
Make sure you have checked all steps below to ensure a timely review.

[x] PR title addresses the issue accurately and concisely. Example: "Updates the version of Flask to v1.0.2"

In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

[x] PR includes a summary of changes.
[x] PR adds unit tests, updates existing unit tests, OR documents why no test additions or modifications are needed.
[x] In case of new functionality, my PR adds documentation that describes how to use it.

All the public functions and the classes in the PR contain docstrings that explain what it does

[x] PR passes make test
[x] I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message"

cc @jinhyukchang @youngyjd

Codecov Report

Merging #72 into master will increase coverage by 0.02%.
The diff coverage is 90%.

@@            Coverage Diff             @@
##           master      #72      +/-   ##
==========================================
+ Coverage      83%   83.02%   +0.02%
==========================================
  Files          53       53
  Lines        2500     2509       +9
  Branches      247      251       +4
==========================================
+ Hits         2075     2083       +8
  Misses        344      344
- Partials       81       82       +1

Impacted Files
Coverage Δ

databuilder/models/table_metadata.py
97.54% <90%> (-0.69%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update cd4fa94...9426f92. Read the comment docs.


chore: remove warnings about scroll into view

#925  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.


Eyetribe Calibration

Hi there,
I have used Eyetribe for some time ago and always I had problems during the calibration. The problem is that some times I don't receive the end point or start point message (so maybe is hanged) directly using json messages that Eyetribe specifies at his website. So I thought I had something wrong with my code and I decided use your API to have better luck but I didn't have. Despite the calibration using your C Api doesn't hang is difficult to have a calibration result. So my question is, Is there something wrong within eyetribe software ?
Regards

We have verified this bug. It will be addressed in our next release. This release should happen before May 16th.
Thx for your feedback.

The update has been released and should fix this issue.

Sorry for my late response and thanks arnebp :). I'll check the new release when I have time.


Implement support for incremental builds

Is your feature request related to a problem? Please describe.
Frontend is built every time.
Describe the solution you'd like
To improve build times, it'd be nice to have incremental builds implemented (https://docs.gradle.org/current/userguide/more_about_tasks.html#sec:up_to_date_checks). The inputs and outputs should be known, so no need for extra configuration, although in the case of packinging into a jar, I guess having some option to exclude directories from input/output should be possible.
UPDATE:
Much like my existing issue, I notice this is also something you can do in build.gradle like so:
assembleFrontend.inputs.dir projectDir.toString() + "/src" # just for testing
assembleFrontend.outputs.dir projectDir.toString() + "/build"

But I think the plugin could provide some appropriate defaults.

Hi @nuth,
Thank you for this feedback.
The plugin is expected to deal with builds incrementally: for instance it shall not download again a Node distribution if the version has not been changed, and the install dir has not been touched.
However, I found some issues some weeks ago, and this behaviour is still buggy. Unfortunately, I don't have time actually to work on a fix.
It's clearly the next thing I would work on in this plugin, I'm aware it can be painful since the plugin is running again tasks whose inputs/outputs have not changed.
BR,
Vincent

Hi @nuth,
I'm starting to deal again with your request, that I may have misunderstood. As exposed some months ago, the plugin relies on Gradle incremental behaviour, when relevant, i.e. when it has control on task's inputs and outputs. This is the case with the installNode task and the installYarn task. Both tasks are skipped when the configuration has not changed, and distributions have already been downloaded successfully.
With your message, I understand you would like other tasks, e.g. the assembleFrontend task, to take benefit from this incremental behaviour. Actually, it does not seem to me possible or desirable. This task itself does not assemble the frontend, like the Gradle assemble task that does not assemble anything on its own. It provides the ability to connect the developer's own JS build process to Gradle, and nothing more. Every JS build process is unique to me. This process depends on the project, the language (e.g. TypeScript, Angular, ECMA script version...), the directory layout, etc, chosen by the developer. These choices and the build process are not under the responsibility of the plugin. I mean the plugin is not aware of the inputs and outputs of this build process. It seems to me the incremental feature should be/is already handled by JS precompilers/build tools.
However, if you really want to make one of the plugin task be aware of additional I/O, and take advantage of a custom incremental behaviour, the code you introduced seems to me appropriate.
Actually, I would close this issue soon, unless you want to bring some clarifications. In this case, feel free to continue this discussion.
Thank you for your interest!
BR
Vincent


feat: add BigQuery Studio embedded notebook showing analysis with Gemini models

This PR adds a notebook for using Gemini Pro and Gemini Pro Vision models in BQ using integration in BQML. Notebook is focused on BigQuery Studio embedded notebook experience.
Thank you for opening a Pull Request!
Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[X] Follow the CONTRIBUTING Guide.
[X] You are listed as the author in your notebook or README file.

[X] Your account is listed in CODEOWNERS for the file(s).

[X] Make your Pull Request title in the https://www.conventionalcommits.org/ specification.
[X] Ensure the tests and linter pass (Run nox -s format from the repository root to format).
[N/A] Appropriate docs were updated (if necessary)

Couple of minor nits. Looks good overall! Not sure if owlbot will do this automatically, but it would also be nice if you could format the SQL cells how bigquery auto-formats them.

I made updates and also formatted the queries - some don't format nicely in BQ editor but I used formats from the docs in those cases.


Merge BuildWorldChildren and BuildChildren traits.

Objective
The BuildChildren and BuildWorldChildren traits are mostly identical, so I decided to try and merge them. I'm not sure of the history, maybe they were added before GATs existed.
Solution

Add an associated type to BuildChildren which reflects the prior differences between the BuildChildren and BuildWorldChildren traits.
Add ChildBuild trait that is the bounds for BuildChildren::Builder, with impls for ChildBuilder and WorldChildBuilder.
Remove BuildWorldChildren trait and replace it with an impl of BuildChildren for EntityWorldMut.

Testing
I ran several of the examples that use entity hierarchies, mainly UI.

Changelog
n/a
Migration Guide
n/a

Lovely, I was hoping we could do this.


Could you please remove this from pypi?!

This project has essentially just one line to compute one of the most basic algorithms in human history. Plus it features an unresolved vcs conflict so it's not even functional. Maybe you're learning how to create and publish a python project. That's ok but now is time to be civil and remove it from a public repository. People might have real projects called gcd.

What's the problem with you? Are you planning to sell names in the pypi namespace? How much do you think gcd will value in 2030? Could you please remove your "github for dummies" project from a public namespace?


Add support of micrometers to scaleline

For high resolutions it starts to use micrometers (μm) instead of millimeters(mm). For example "5 μm" instead of "0.005 mm".

I didn't cover my changes with tests, because the whole function (ol.control.ScaleLine.prototype.updateElement_) is not covered. And I guess, that big switch-operator that deals with units there needs to be extracted into separate function first.

Thanks @hajjimurad ! Can you please submit a CLA so we can merge this?
I'll add a test in an other pull request.

Thanks @fredj, I've submitted my personal CLA

Thanks for you contribution @hajjimurad


Urlinfo scheme is "http" when website is behind Cloudflare

When accessing the website with "https" but the website itself is hosted behind a proxy or load balancer such as Cloudflare, a lot of buttons such as create new content/folder, publish etc don't work. By opening browser dev tools I found ajax requests are sent with "http" instead of "https" and so the browser blocked it.
A likely reason is because a connection between client to the proxy server is done with https, but connection between the proxy server and the actual web server is done with http.
I could make it work by modifying system.php:137 to check for HTTP_X_FORWARDED_PROTO header.
if (isset($_SERVER['HTTP_X_FORWARDED_PROTO'])) {
	$uri = $uri->withScheme($_SERVER['HTTP_X_FORWARDED_PROTO']);
}
$urlinfo 				= Urlinfo::getUrlInfo($basepath, $uri, $settings);

Based on these articles, this header is added by proxy servers to indicate what protocol is used between the client and proxy server.
https://developers.cloudflare.com/fundamentals/reference/http-request-headers/#x-forwarded-proto
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Forwarded-Proto

Yes, did you try the proxy-detection in the developer tab of the system settings? There is a proxy detection and if it does not work in complex environments you can also force an url/schema

Thank you for pointing out the settings!
I tested enabling proxy as well as setting a base-url under the developer tab and these options didn't work unfortunately. When editing a content for example, clicking Publish button showed the ajax request was still sent to the same url with http (not the one that was set in base-url).

Thank you for the Information, that is strange, I only tested it with a local proxy but some clients use it successfully. I will check if I can test it with cloudflare somehow.

Sorry, just published a new release, I will have a look in the next days...

Yes, i see the problem, will be fixed with release 2.6.0

please try with version 2.6.0 now, I hope it works, let me know if you still have issues.

Thank you! Sorry I was not being able to test it soon enough.. Tested with 2.10.0 and it works flawlessly with Cloudflare.


Added Azure AI Service REST API

issue #149
please check and add gssoc and level label
thank you

Azure is a platform .. this repo is only for companies that provide API as a Service


[ALLUXIO-3078] Add safe mode to Alluxio master

https://alluxio.atlassian.net/browse/ALLUXIO-3078

Added SafeModeManager to keep track of the safe mode state
Updated DefaultBlockManager to throw UnavailableException upon request of worker information and block locations so client RPC calls will automatically retry.
Updated various places in master to either expose the exception to client or handle it appropriately.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/17993/Build result: FAILURE[...truncated 1771 lines...][JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/keyvalue/common/target/alluxio-keyvalue-common-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-keyvalue-common/1.7.0-SNAPSHOT/alluxio-keyvalue-common-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/keyvalue/common/target/alluxio-keyvalue-common-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-keyvalue-common/1.7.0-SNAPSHOT/alluxio-keyvalue-common-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/client/fs/pom.xml to org.alluxio/alluxio-core-client-fs/1.7.0-SNAPSHOT/alluxio-core-client-fs-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/client/fs/target/alluxio-core-client-fs-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-core-client-fs/1.7.0-SNAPSHOT/alluxio-core-client-fs-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/client/fs/target/alluxio-core-client-fs-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-core-client-fs/1.7.0-SNAPSHOT/alluxio-core-client-fs-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/client/fs/target/alluxio-core-client-fs-1.7.0-SNAPSHOT-tests.jar to org.alluxio/alluxio-core-client-fs/1.7.0-SNAPSHOT/alluxio-core-client-fs-1.7.0-SNAPSHOT-tests.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/pom.xml to org.alluxio/alluxio-core-common/1.7.0-SNAPSHOT/alluxio-core-common-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/target/alluxio-core-common-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-core-common/1.7.0-SNAPSHOT/alluxio-core-common-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/target/alluxio-core-common-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-core-common/1.7.0-SNAPSHOT/alluxio-core-common-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/target/alluxio-core-common-1.7.0-SNAPSHOT-tests.jar to org.alluxio/alluxio-core-common/1.7.0-SNAPSHOT/alluxio-core-common-1.7.0-SNAPSHOT-tests.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/worker/pom.xml to org.alluxio/alluxio-core-server-worker/1.7.0-SNAPSHOT/alluxio-core-server-worker-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/logserver/pom.xml to org.alluxio/alluxio-logserver/1.7.0-SNAPSHOT/alluxio-logserver-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/client/pom.xml to org.alluxio/alluxio-core-client/1.7.0-SNAPSHOT/alluxio-core-client-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/pom.xml to org.alluxio/alluxio-examples/1.7.0-SNAPSHOT/alluxio-examples-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/target/alluxio-examples-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-examples/1.7.0-SNAPSHOT/alluxio-examples-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/target/alluxio-examples-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-examples/1.7.0-SNAPSHOT/alluxio-examples-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/pom.xml to org.alluxio/alluxio-core/1.7.0-SNAPSHOT/alluxio-core-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/proxy/pom.xml to org.alluxio/alluxio-core-server-proxy/1.7.0-SNAPSHOT/alluxio-core-server-proxy-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/shell/pom.xml to org.alluxio/alluxio-shell/1.7.0-SNAPSHOT/alluxio-shell-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/shell/target/alluxio-shell-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-shell/1.7.0-SNAPSHOT/alluxio-shell-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/shell/target/alluxio-shell-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-shell/1.7.0-SNAPSHOT/alluxio-shell-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/tests/pom.xml to org.alluxio/alluxio-tests/1.7.0-SNAPSHOT/alluxio-tests-1.7.0-SNAPSHOT.pomchannel stoppedArchiving artifacts
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/17995/Failed Tests: 1org.alluxio:alluxio-tests: 1alluxio.master.FileSystemMasterClientIntegrationTest.masterUnavailable
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/17999/Failed Tests: 2org.alluxio:alluxio-tests: 2alluxio.master.file.ConcurrentFileSystemMasterCreateTest.concurrentCreateNonPersistedDiralluxio.master.file.ConcurrentFileSystemMasterCreateTest.concurrentLoadFileMetadataExistingDir
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/18003/Build result: FAILURE[...truncated 2029 lines...][JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/keyvalue/common/target/alluxio-keyvalue-common-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-keyvalue-common/1.7.0-SNAPSHOT/alluxio-keyvalue-common-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/keyvalue/common/target/alluxio-keyvalue-common-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-keyvalue-common/1.7.0-SNAPSHOT/alluxio-keyvalue-common-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/client/fs/pom.xml to org.alluxio/alluxio-core-client-fs/1.7.0-SNAPSHOT/alluxio-core-client-fs-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/client/fs/target/alluxio-core-client-fs-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-core-client-fs/1.7.0-SNAPSHOT/alluxio-core-client-fs-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/client/fs/target/alluxio-core-client-fs-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-core-client-fs/1.7.0-SNAPSHOT/alluxio-core-client-fs-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/client/fs/target/alluxio-core-client-fs-1.7.0-SNAPSHOT-tests.jar to org.alluxio/alluxio-core-client-fs/1.7.0-SNAPSHOT/alluxio-core-client-fs-1.7.0-SNAPSHOT-tests.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/pom.xml to org.alluxio/alluxio-core-common/1.7.0-SNAPSHOT/alluxio-core-common-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/target/alluxio-core-common-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-core-common/1.7.0-SNAPSHOT/alluxio-core-common-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/target/alluxio-core-common-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-core-common/1.7.0-SNAPSHOT/alluxio-core-common-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/target/alluxio-core-common-1.7.0-SNAPSHOT-tests.jar to org.alluxio/alluxio-core-common/1.7.0-SNAPSHOT/alluxio-core-common-1.7.0-SNAPSHOT-tests.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/worker/pom.xml to org.alluxio/alluxio-core-server-worker/1.7.0-SNAPSHOT/alluxio-core-server-worker-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/logserver/pom.xml to org.alluxio/alluxio-logserver/1.7.0-SNAPSHOT/alluxio-logserver-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/client/pom.xml to org.alluxio/alluxio-core-client/1.7.0-SNAPSHOT/alluxio-core-client-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/pom.xml to org.alluxio/alluxio-examples/1.7.0-SNAPSHOT/alluxio-examples-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/target/alluxio-examples-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-examples/1.7.0-SNAPSHOT/alluxio-examples-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/target/alluxio-examples-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-examples/1.7.0-SNAPSHOT/alluxio-examples-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/pom.xml to org.alluxio/alluxio-core/1.7.0-SNAPSHOT/alluxio-core-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/proxy/pom.xml to org.alluxio/alluxio-core-server-proxy/1.7.0-SNAPSHOT/alluxio-core-server-proxy-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/shell/pom.xml to org.alluxio/alluxio-shell/1.7.0-SNAPSHOT/alluxio-shell-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/shell/target/alluxio-shell-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-shell/1.7.0-SNAPSHOT/alluxio-shell-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/shell/target/alluxio-shell-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-shell/1.7.0-SNAPSHOT/alluxio-shell-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/tests/pom.xml to org.alluxio/alluxio-tests/1.7.0-SNAPSHOT/alluxio-tests-1.7.0-SNAPSHOT.pomchannel stoppedArchiving artifacts
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/18004/
Test PASSed.

@calvinjia I updated the change so it no longer use an extra thread. PTAL.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/18013/
Test PASSed.

@aaudiber @calvinjia I updated the PR to address some commented issues. PTAL.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/18037/
Test PASSed.

@aaudiber I updated the PR to address more comments. PTAL.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/18044/
Test PASSed.

Merged build finished. Test PASSed.


(BUG) [RN] The Claim button jumps after the user coming back to the dashboard

Precondition:
The dashboard is opened (the "Home" page)
Steps to reproduce:

Click the "Receive" button
Click the "Back" button
Pay attention to the "Claim" button

Actual result: The Claim button jumps after the user coming back to the dashboard
Expected result: The Claim button shouldn't jump after the user coming back to the dashboard
Video: https://www.screencast.com/t/XpYIeR3YQ9EN
Checked on native 1.3.1-1
LG V30+ // Android 8.0 // Google Chrome 86.0.4240.75
Desktop: Windows 10 // Google Chrome 86.0.4240.75

@mauriguz i recall there was some issue with react native and layout, see if its possible to find a different solution

@mauriguz isn't reproduced any more
https://www.screencast.com/t/DFM4IqW10
Checked on  QA 1.6.1-2
Desktop: Windows 10 // Google Chrome  86.0.4240.75


storage change to hardisk from memory

we need to change the storage of everything to hardisk in place of ram so that the data is not lost after the reboot. How to do that which file to tweak for the same.

To do this correctly we would have to change almost all of the Moto source code. But you might be able to get what you want by pickling (pickle.dumps) moto.backends.BACKENDS to a string and storing that in a file. Then, when you need to restore the previous state you can pickle.loads the contents of the file and restore the moto.backends.BACKENDS data.

Going to close this right now. If someone wants to propose ideas, I am open.


ValueError: could not convert string to float: '295 722'

Hi
I got a conversion error using the file from https://www.renaultgroup.com/finance/information-reglementee/
https://www.renaultgroup.com/wp-content/uploads/2022/03/969500f7jltx36oui695-2021-12-31-2.zip

Thanks for the report, I'm taking a look.

A couple of iXBRL transform mods, that test file works for me now.  Thanks for the report!

The fix is in PyPI package 0.9.4
https://pypi.org/project/ixbrl-parse/0.9.4/


Add Prometheus metrics server

Added Prometheus metrics server and implemented a number of "easy" metrics that didn't involve significant code changes. One particularly hacky one which @bkase should verify is how I'm tracking keypairs and delegators in proof_of_stake.ml (I put something in place that I think will work, but I did it in a bad way to avoid refactoring).
@yourbuddyconner once this lands, you can run the server by passing -metrics-port <port> to the daemon cli. There is currently no "phone home" logic for notifying a central service that the node is running, so you will need to manually collect the node ips/ports to give to prometheus for now.

Good show! Failing tests looking for the prometheus library, probably an easy fix.

Missing a file probably

Wow, we should have a CI process for containers...

I'm having problems getting the docker container to rebuild. Can you help out later @bkase ?


gcd(0,a) always gives 1

For an integer a, gcd(0, a) should give abs(a), so here:
https://github.com/numbas/Numbas/blob/5a5da52dc5bd295babc18165abcb002cd6f6c3b2/runtime/scripts/math.js#L1704
it should be return a, not return 1.

Thanks, I wasn't aware of this.


fix(startup): save startup time, thanks @rem, closes #40

Thanks @remy!

Whenever you initiate the update notifier and it's not within the interval threshold, it will asynchronously check with npm in the background for available updates, then persist the result. The next time the notifier is initiated the result will be loaded into the .update property. This prevents any impact on your package startup performance. The check process is done in a unref'ed child process. This means that if you call process.exit, the check will still be performed in its own process.

I think this is already taken care of/this change doesn't make any difference.

I could measure ~70ms time improvement consistently on my MBP

I just wanted to add, except for the time it takes to load the library itself into memory. But this also means the notifier is only ever called when the command doesn't fail, which isn't that cool, given that a lot of fails could result from the CLI being outdated.

good point, ignore.

Addendum II: The defaults operation could be quite expensive. We could probably speed this up by just picking name and version first, and then applying the defaults.


feat(docker): configurable DNS server

DNS_1 and DNS_2 environment variable added

So now we are able to configure our prefered DNS servers through the /etc/sysconfig/valheim-server file if we want to override the defaults.

LGTM! Thanks.


Also mount spark metrics listener jar in datalab init actions

I can share the testing details which are on internal site.

/gcbrun


Move labels so things align nicely

I do not think

looks as nice as

Is that something this plugin would appreciate as well? I can work on adding it if you like the idea.

Personally, I like the current layout more as the focus is on the title and you see that first. The labels to me are secondary.

The latter looks a lot more messy in my opinion. The title is the important part and we should optimize for that, not the labels.


[Bug] CldUploadButton doesn't reecognize uploadPreset prop

Bug Report
Describe the bug

Didn't actually try the button yet, but couldnt load the page
<CldUploadButton uploadPreset="test" />

looks like this might have been fixed too @matiasfha


server crashes

Log before crash: https://hastebin.com/agumavojul.md

This part of the thread dump is what tells you what caused the crash. The rest just says what was also going on. The cause of your crash was a skript/inventory click event error that definitely had nothing to do with LP. I'd take a look at your skript for inventory guis or something like that as the cause of the crash.

oh it just said luckperms in the top so though it was that sry :)


[WIP] Add Job Storage

Related Issue: https://github.com/coinbase/rosetta-cli/issues/112
Changes

[x] Fix tests from #117
[x] refactor construction package into job, worker, and coordinator
[ ] update broadcast storage with new interface
[ ] add job storage

[ ] expose # completed for a job type

Pull Request Test Coverage Report for Build 5122

46 of 49 (93.88%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.5%) to 78.437%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

constructor/worker/worker.go
30
33
90.91%

Totals

Change from base Build 5102:
0.5%

Covered Lines:
3281

Relevant Lines:
4183

💛  - Coveralls

Review Error for cindyxkuang @ 2020-09-01 00:04:02 UTC
User failed mfa authentication, see go/mfa-help

Review Error for cindyxkuang @ 2020-09-01 00:04:50 UTC
User failed mfa authentication, see go/mfa-help

Review Error for cindyxkuang @ 2020-09-01 00:09:19 UTC
User failed mfa authentication, see go/mfa-help


Create new SDK version

Description
This Pull Request updates the SDK to include every API endpoint and to be extensible from the maintainer's point of view and to feel natural to use from the user's point of view. Information about its usage can be found on the new README.md file.
Requirements
This new version breaks literally everything from the last version, and this is an enormous Pull Request, so it needs to be reviewed with patience.
Additional changes
The CI/CD pipeline got updated too, now using GitHub Actions, linting un push and running tests on pull requests. Releases also should happen automagically, but that pipeline hasn't been thoroughly reviewed by me, I just left the skeleton of the action.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@0f99043). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #10   +/-   ##
=========================================
  Coverage          ?   83.66%
=========================================
  Files             ?       37
  Lines             ?      355
  Branches          ?        0
=========================================
  Hits              ?      297
  Misses            ?       58
  Partials          ?        0

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0f99043...e808f0d. Read the comment docs.


NewareNDAcli defaults to software_cycle_number=False

The flag should be changed to --no_software_cycle_number and store False.

Fixed in 8c84343


[Bug]: UserLocation stops updating when followUserLocation is detached

Mapbox Implementation
Mapbox
Mapbox Version
default
Platform
iOS
@rnmapbox/maps version
#main
Standalone component to reproduce
import {
  Camera,
  Location,
  MapView,
  UserLocation,
  UserLocationRenderMode,
} from '@rnmapbox/maps';
import React, { useState } from 'react';
import { Text } from '@rneui/base';

import Bubble from './common/Bubble';

const styles = {
  mapView: { flex: 1 },
};

const BugReportExample = () => {
  const [location, setLocation] = useState<Location>();

  return (
    <>
      <MapView style={styles.mapView}>
        <Camera
          followUserLocation
          centerCoordinate={[-122.033, 37.337]}
          zoomLevel={14}
        />

        <UserLocation
          renderMode={UserLocationRenderMode.Normal}
          onUpdate={(newLocation) => {
            setLocation(newLocation);
          }}
        />

        <Bubble>
          <Text>{location?.coords.longitude}</Text>
          <Text>{location?.coords.latitude}</Text>
        </Bubble>
      </MapView>
    </>
  );
};

export default BugReportExample;

Observed behavior and steps to reproduce
When followUserLocation is detached by user interaction, e.g. panning the map, no more UserLocation.onUpdate calls are made. The user location in the map is also not updated anymore. The video is running a the Bicycle Ride Location simulation.
https://user-images.githubusercontent.com/18724559/225281525-0d51db63-39df-4e35-b6e1-605acb11fe1f.mp4
Expected behavior
UserLocation should still be updated and call onUpdate.
Notes / preliminary analysis
Can also be seen in the UserLocationChange example.
Additional links and references
No response

It actually only happens if UserLocationRenderMode.Normal is used on intial rendering.


UI5 Planning Calendar "TypeError: Cannot read properties of undefined (reading 'getTime')" - UTC datetime - SAP CAP Framework

Dear UI5 experts,
I have implemented the latest version of SAPUI5 planning calendar and I have bound it against our (CAP) data model. The projects are shown most of the times, but sometimes we get the issue: "TypeError: Cannot read properties of undefined (reading 'getTime')". The project related start- and enddatetime are maintained but this is ignored by the framework. It seems that the start- and end date times are not being saved as UTC date time by the SAP CAP framework. I can provide the source code via git or you can try to access my DEV space. As soon as we refresh the planning calendar, the projects are being shown. We got rid of that issue back then and it re-appeared. There is also this similiar issue (closed) https://github.com/SAP/openui5/issues/2524#issuecomment-1643399628.
The app is part of our product development and really important for showcases and future sales.
Please tell me what you need to reproduce and to access the apps and we can continue the communication on this behalf.
Thank you for your support.
OpenUI5 version: 1.116.0
Browser/version (+device/version): Google Chrome (latest)
Any other tested browsers/devices(OK/FAIL): No
URL (minimal example if possible): Private message possible?
User/password (if required and possible - do not post any confidential information here):
Private message possible?
Steps to reproduce the problem:

Open Planning Calendar which is bound against CAP data model
Refresh or navigate back and frontwards
Open Console and check for the error message

What is the expected result?
Planning Calendar should load every listed project entry.
What happens instead?
...but instead does not show anything or only after a refresh.
Any other information? (attach screenshot if possible)
See attachments

Fixed by https://github.com/SAP/openui5/commit/6fc8110c09777fff785b0b65eec071f48e412aac


Update dispatchers.py

In this PR, I update the dispatchers.py module.

[x] Improve docstrings
[x] Add type hints
[x] Check whether I need to add additional tests
[x] Create an example notebook
I've added a folder, explanations, in which I collect explanation notebooks for the lcm internals. This is not ideal yet, but we can easily change it.
[x] Update pre-commit hooks
[x] Delete distributions.py
This is outdated and not used anywhere.

Notes:
In line with JAX's vmap function we use F = TypeVar("F", bound=Callable) for the type hint of the function that is dispatched. This signals that the object returned is the same as the input, except that it is now vectorized.

@hmgaudecker please re-review the PR. I made the following additional changes:

I tried to integrate your comments on the dispatchers explanation notebook
I added a boolean flag to vmap_1d to choose whether the allow_kwargs decorator should be applied before returning the dispatched function, which allowed me to rewrite spacemap using only productmap and vmap_1d.


Implemented requested changes

Changes requested in https://github.com/AakashSharma7269/erin/pull/5#issuecomment-875832148

if possible please also integrate a listener which checks if a role was added to any member and if it's the mute role or not, then we can auto log it (this will essentially log the mutes of other bots too)

If you have time for this then that would be really appreciated, if not just ping me on discord and i'll get that done

I'm merging and closing this for now.


Pressing <Leader>g causes the cursor to advance 1 character

Describe the bug
Bit of a weird one. When I press <Leader>g, the cursor advances forward one character. The WhichKey pane still appears, and I can still follow up with r, d, etc., and those bindings all function as expected.
I've not noticed this issue with any other key combination (though I haven't exhaustively checked).
:checkhealth output looks fairly normal, but the WhichKey section shows this (not sure if it's an issue/related):
which-key: require("which-key.health").check()

WhichKey: checking conflicting keymaps ~
- WARNING conflicting keymap exists for mode **"n"**, lhs: **"sF"**
- rhs: ` `
- WARNING conflicting keymap exists for mode **"n"**, lhs: **"sr"**
- rhs: ` `
- WARNING conflicting keymap exists for mode **"n"**, lhs: **"sh"**
- rhs: ` `
- WARNING conflicting keymap exists for mode **"n"**, lhs: **"sd"**
- rhs: ` `
- WARNING conflicting keymap exists for mode **"n"**, lhs: **"sf"**
- rhs: ` `
- WARNING conflicting keymap exists for mode **"n"**, lhs: **"gc"**
- rhs: `<Plug>(comment_toggle_linewise)`
- WARNING conflicting keymap exists for mode **"n"**, lhs: **"gb"**
- rhs: `<Plug>(comment_toggle_blockwise)`

I tried checking out the latest Kickstart master, deleting ~/.local/share/nvim and relaunching nvim, and the issue persists.
To Reproduce

Press <Leader>g. Notice that the cursor advanced one character, but vim is still awaiting input (and WhichKey is open).

Desktop

OS: macOS 13.6.6
Terminal: iTerm2

Neovim Version
NVIM v0.9.5
Build type: Release
LuaJIT 2.1.1710088188

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/opt/homebrew/Cellar/neovim/0.9.5/share/nvim"

Run :checkhealth for more info

Are you use the default config for WhichKey from main or have you made any changes?

Thanks for the report and good catch! I can reproduce this on kickstart latest but have no idea what's going on.
I'll see if I can find the time to dig into this.

I think that's the intended behaviour. If a starting key combo does not match any defined combo, then the broken down keys are interpreted instead. A single space in normal mode if not remapped just advances the cursor for 1 character right so that what happens. As for then getting a which-key popup it's because the g key then waits for the next movement key combo. If you try space and x what will happen is cursor advances one char and deletes one char, without any which-key popup.
What was your expectation with space-g anyway?

I think I see the issue: the init.lua does not have the g key chain.
@robinjam try adding this to the require('which-key').register({}) section of your whichkey config and see if the issue persists:
['<leader>g'] = { name = '[G]it', _ = 'which_key_ignore' },

You're right. This is working as designed. Closing.

You're absolutely right, I got my keybinds mixed up 🤦♂
Sorry for the time waste


Update botframework, spark, and stackstorm hubot plugins to latest

Update dependencies to their latest versions.
This PR includes changes from #141, to fix a few issues when integrating with Microsoft Teams. Thank you to LizhangX.
This PR also switches the hubot-spark adapter to using a git commit, since the version of hubot-spark available on NPM is not the most up-to-date, and the Spark adapter in hubot-stackstorm depends on the most recent (as of this writing) changes in that hubot-spark Hubot plugin.
Thanks to @VivekSyngh, the hubot-stackstorm plugin has been updated to work against Webex (Cisco Spark was renamed to Webex Teams), so that dependency is also updated and pulled normally from NPM.
This slims down the npm-shrinkwrap.json file a bit, (I think) because we are no longer including devDependencies for hubot-stackstorm.
Not sure why the tests are failing. Will investigate and fix them.

The problem is that shrinkwrap change here includes all possible dependency updates with +2,207 −2,626 diff.
Try to follow this guide https://github.com/StackStorm/st2chatops/issues/104  to regenerate only needed dependencies in shrinkwrap.

That guide is good, and I'm redoing the PR to follow that, but using npm update wouldn't change the hubot-botframework or hubot-spark dependencies the way I need to here, since I'm not trying to simply update those components to their most recently released versions. I'm trying to install those components from specific git commits, not released versions. For those I have to use npm install --save <...>.
I'm currently redoing this PR to break up the changes to package.json and npm-shrinkwrap.json into the individual npm operations, to give better clarity into why the diff for this PR is so large. Unfortunately there was a lot of churn in the Cisco Spark to Webex rename, so the diff for that change is still rather large. As far as I know, I can't do anything about that.

The npm update command didn't update hubot-stackstorm even though version 0.10.2 is released on NPM, so I used npm install --save<EMAIL_ADDRESS>to update that one.
And a final docker-compose run xenial npm-shrinkwrap didn't change any files.


Uncaught TypeError: $(...).headroom is not a function

How can i fix it. I want to use it with jquery js.
jquery and headroom js already imported on my footer.
please see this: https://codepen.io/dimative/pen/MRLqqV

You need to load both the Headroom JavaScript AND the jQuery.Headroom plugin. These are separate files. jQuery support is only available if you load the second file.

That is correct, you need to add both. I forked your pen and did just that. I added some CSS to get the slide in/out behaviour, and fixed a typo in a the js-headroom classname: https://codepen.io/WickyNilliams/pen/EqzGjW?editors=1100