[BUG] Unable to Call Stored Procedure with CLOB Parameters

Describe your system

odbc Package Version: 2.3.5
ODBC Driver: IBM i Access ODBC Driver
Database Name: Db2 for i
Database Version: 7.2
Database OS: IBM i 7.2
Node.js Version: 12.18.4
Node.js OS: IBM i

Describe the bug
Calling a stored procedure with CLOB parameters doesn't work. When called using connection.query() the call succeeds, but the output parameter data is not returned. When called using connection.callProcedure() the call fails with an error:
[Error: [odbc] Error retrieving the result set containing information about the columns in the procedure] {
  odbcErrors: [
    {
      state: '',
      code: 30160,
      message: '[IBM][System i Access ODBC Driver]Column 15: Numeric value out of range.'
    },
    {
      state: '',
      code: 30160,
      message: '[IBM][System i Access ODBC Driver]Column 15: Numeric value out of range.'
    }
  ]
}

Expected behavior
CLOB parameters should work the same as any other.
To Reproduce
To reproduce, create a simple stored procedure with CLOB parameters, like this:
create procedure yourlib/testclob (
  in a clob(128K),
  out b clob(128K)
)
language sql
set b = a

Then try calling, like this:
const odbc = require("odbc");

(async () => {

  try {

    const connection = await odbc.connect(`Driver=IBM i Access ODBC Driver;System=localhost;uid=YOU;password=YOURS`);
    let result = await connection.query("call yourlib.testclob(?, ?)", ["Hello, world", ""]);
    console.log(result);
    result = await connection.callProcedure(null, "YOURLIB", "TESTCLOB", ["Hello, world", ""]);
    console.log(result);
    await connection.close();

  }
  catch (error) {

    console.error(error);
    process.exit(1);

  }

})();

Two things:

That warning has nothing to do with CLOB support, it actually is because ParameterType is bound to an unsigned smallint, and CLOB indicator is -99, so it complains. This will be fixed in the next version.

Even when that is fixed, CLOB support currently doesn't work with the IBM i ODBC driver. See: #129 .  It checks an allowlist of data types for binding parameters, and that list doesn't include CLOBs. When I add CLOBs to the list it just works, but that issue won't be available until the changes get merged into the driver proper. I believe @worksofliam opened an RFE about it.

Since this isn't an issue odbc the NPM package, but instead with the driver, I am going to close this as "wontfix". I will try to get those changes in the driver soon!


Migrating credentials failure

Hi, I am testing this script for an upcoming migration and get the error:
Enter credentials for the 'source' Azure Subscription...
WARNING: The provided credentials failed to authenticate or are not associcated to a valid subscription. Exiting the script
I have ensured that I have the correct credentials but to no avail - any assistance will be appreciated. Thank you.

@KobusOlie4   Which version of AzureRM.Profile are you using?  Use Get-Command Login-AzureRmAccount to find out.  Also, is there a SubscriptionID when you use Get-AzureRMSubscription after logging in with the same credentials you use to execute the script?

@KobusOlie4  I confirmed it is the newer modules causing your problem.  AzureRM version 3.2 used SubscriptionID, but now that property is just ID in 4.2.1.  I'll check that fix in when I add the Managed Disk support, but for now you can import-module AzureRM -Requiredversion 3.2.0 as workaround.

Resolved in the latest release.


[Bug]: java rainbow highlighting not working

Neovim version
0.9.1
Language affected
Java
Query
No response
Strategy
No response
Description
package com.transformity.pos.util;

import java.math.BigDecimal;
import java.math.RoundingMode;

public class Utils {
  public static String toUpperCamelCase(String input) {
    String[] words = input.split("\\s+");
    StringBuilder result = new StringBuilder();
    for (String word : words) {
      if (!word.isEmpty()) {
        String capitalizedWord =
            word.substring(0, 1).toUpperCase() + word.substring(1).toLowerCase();
        result.append(capitalizedWord);
      }
    }
    return result.toString();
  }

  public static BigDecimal calculateProfitMargin(BigDecimal sellPrice, BigDecimal buyPrice) {
    if (sellPrice == null || buyPrice == null) {
      return null;
    }
    try {
      return ((sellPrice.subtract(buyPrice)).divide(buyPrice, RoundingMode.HALF_UP))
          .multiply(BigDecimal.valueOf(100));
    } catch (ArithmeticException e) {
      return null;
    }
  }

  public static int calculateBuyRangeImportance(String buyRange) {
    if (buyRange == null) {
      return -1;
    }
    return switch (buyRange) {
      case "PRICE INCREASE" -> 100;
      case "BUY 30", "BUY 60", "BUY 90", "BUY 120", "BUY 150" -> 90;
      default -> 0;
    };
  }
}

Works for me. Do you have the Tree-sitter grammar installed? What does checkhealth rainbow-delimiters display?

==============================================================================
rainbow-delimiters: require("rainbow-delimiters.health").check()

- ERROR The healthcheck report for "rainbow-delimiters" plugin is empty.

Looks like the plugin did not install properly for you. Can you please try uninstalling and installing it again? If that does not work, can you please post the directory contents of your local copy? You can use the tree command to print a nice directory tree.

https://gist.github.com/jay-babu/787c7376f0b058f1ca51c26df4a5bc1d. I uninstalled and installed and the same error came up again

That's weird. Which version of Neovim are you running? Are you somehow lazy-loading this plugin?

NVIM v0.9.1
Build type: Release
LuaJIT 2.1.0-beta3

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/usr/share/nvim"

Run :checkhealth for more info

I was lazy loading, but just tried without it. the same problem

I am using the lazy plugin manager

Does the problem still persist on the current master? Are languages other
than Java affected? If you :edit the buffer again does it work then?
As for the health check, we can compare hash values. Here is the SHA-256 of my
file:
5e78ec80c7c62699d0309bc646142922ed1e24224fcfd5a8eeb0866a80ab5a01  lua/rainbow-delimiters/health.lua

If yours differs then there is something wrong with your file.


Missing Office connector [Shared Connectors].

Describe the Bug with repro steps

In VS Code , Create a Project and add stateful workflow.
Open the Designer, Try to find the Office connector.

Expected: Should be load.
Actual: Not loading.

What type of Logic App Is this happening in?
Standard (VSCode)
Are you using new designer or old designer
New Designer
Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
Yes
Workflow JSON
No response
Screenshots or Videos
No response
Browser
VS Code
Additional context
VS Code extension: vsix icon vscode-azurelogicapps-2.43.0.vsix
NuGet package:   https://artprodeussu2.artifacts.visualstudio.com/A41bf5486-7392-4b7a-a7e3-a735c767e3b3/b32aa71e-8ed2-41b2-9d77-5bc261222004/_apis/artifact/cGlwZWxpbmVhcnRpZmFjdDovL21zYXp1cmUvcHJvamVjdElkL2IzMmFhNzFlLThlZDItNDFiMi05ZDc3LTViYzI2MTIyMjAwNC9idWlsZElkLzc2MDIyNjQzL2FydGlmYWN0TmFtZS9kcm9wX2J1aWxkX0J1aWxkQXJ0aWZhY3RzX1dpbmRvd3M1/content?format=file&subPath=%2FMicrosoft.Azure.Workflows.WebJobs.Extension.1.30.1.nupkg
Extension Bundle (CDN URL): https://cdnforlogicappsv2.blob.core.windows.net/logicapps-vendortesting
Extension Bundle (Direct Download): https://cdnforlogicappsv2.blob.core.windows.net/logicapps-vendortesting/ExtensionBundles/Microsoft.Azure.Functions.ExtensionBundle.Workflows/1.30.1/Microsoft.Azure.Functions.ExtensionBundle.Workflows.1.30.1_any-any.zip
AB#24506334

@ccastrotrejo Issue fixed in vsix : 2.45.2


Remove duplicate code in NetCoreSpec

Lots of duplicate code here to acquire the mutex before running a function. I created a helper function to acquire the mutex to remove this duplicate code.

LGTM. Code is leftover from some annoying threading shenanigans I had to debug so it probably also could have been stripped, but I'd like to also improve log level usage a bit (right now it's always set to trace) so having stuff like this consolidated will help those efforts as it'll make it easier to bump up things that don't need to be trace to debug & up that default level at some point.


View transition not working with Presenter mode

Describe the bug
View Transition is not shown in presenter mode. It works with play mode.
It seems this from.meta/to.meta doesn't return the value of the slide if it's in presenter mode.
https://github.com/Jannchie/slidev/blob/dad957728e5d73b5926cb8635ae03228baca52eb/packages/client/composables/useViewTransition.ts#L14
refs #1100 #1101
To Reproduce
Steps to reproduce the behavior:

Open https://stackblitz.com/edit/slidev-xaqvhc?file=slides.md
Open it with play mode and check that view transition works
Switch to presenter mode and check that it doesn't work

Desktop (please complete the following information):

OS: Windows 11
Browser: Chrome 118.0.5993.89
Slidev version: 0.43.7

I'm seeing the same issue on Ubuntu with slidev 0.43.8.


bug: env vars in meltano.yml cause exception while running meltano install since v2.13.0

Meltano Version
2.13.0
Python Version
3.9
Bug scope
CLI (options, error messages, logging, etc.)
Operating System
Windows 10 (using WSL2), same issue occurs on Ubuntu 22.04 VM
Description
Slack thread
Using Meltano's Docker image I set up env vars in the meltano.yml file to utilize dynamically created database connections (using docker compose) cross-projects. This worked like a charm in v2.12.0, however since v2.13.0 I'm receiving an exception during the meltano install step in the Dockerfile.
This exception occurs:
invalid literal for int() with base 10: ''

For example, the meltano.yml contains the following loader:
loaders:
  - name: target-postgres
    variant: transferwise
    pip_url: pipelinewise-target-postgres
    config:
      host: ${DB_HOST}
      port: ${DB_PORT}
      user: ${DB_USER}
      password: ${DB_PASS}

And in the docker-compose.yml I set up the env vars:
services:
  meltano:
    <<: *meltano-image
    command: ui
    environment:
      DB_HOST: ${DB_HOST}
      DB_PORT: ${DB_PORT}
      DB_USER: ${DB_USER}
      DB_PASS: ${DB_PASS}

If I remove the env vars from the meltano.yml, the exception doesn't occur.
Also, if I comment out the meltano install command from the Dockerfile, run the container and bash into it, the exception doesn't occur if I manually execute meltano install. In that case the env vars are also passed correctly, which I checked using the meltano config target-postgres list command.
The Dockerfile for reference:
# registry.gitlab.com/meltano/meltano:latest is also available in GitLab Registry
ARG MELTANO_IMAGE=meltano/meltano:latest-python3.9
FROM $MELTANO_IMAGE

RUN apt-get update && apt-get install libpq-dev -y

WORKDIR /project

# Install
# Install any additional requirements
COPY ./requirements.txt .
RUN pip install -r requirements.txt

# Copy over Meltano project directory
COPY . .

RUN meltano install

# Don't allow changes to containerized project files
# ENV MELTANO_PROJECT_READONLY 1

ENTRYPOINT ["meltano"]

Code
No response

The old behavior when an env var wasn't found within a string setting value while expanding env vars was to return None. re.sub interprets this as the empty string, but if the whole setting string matches the regex, then instead of calling re.sub the substitution function was called directly, so None was returned instead of a string. This is... weird. I don't know why it was implemented like this, but it seems like this behaviour was relied on by src/meltano/core/settings_service.py::SettingsService.get_with_metadata, since it passes the value returned by expand_env_vars to setting_def.cast_value, which is a no-op when the value is None, but errors if the value is the empty string and its trying to cast it to int.
I'm hesitant to restore the old behaviour because it seems incorrect. A better way to do what it was doing without changing too much is probably to detect whether the setting string was not empty before expansion and is empty after expansion. If that's the case, then we replace the value with None.


pter adds CRLF line terminators on Linux

Steps to reproduce (tested under Manjaro Linux with pter 3.0.0):

Create a new todo.txt in Vim or Neovim, add a few tasks, and exit the editor.

Run file todo.txt. It should show the following output:
todo.txt: Unicode text, UTF-8 text

Open todo.txt in pter, make some edits (for example, mark a task as done).

Run file todo.txt again. Now it shows the following:
todo.txt: Unicode text, UTF-8 text, with CRLF line terminators

Neovim also shows this change, by running :set ff or looking at luabar with the default configuration.
While I'm not seeing any negative effects of this right now, a few weeks ago, when I opened one of my todo.txt files in Neovim, I noticed that it contained ^M at the end of every line. Then I realised it had been edited with pter. I think that was somehow related to this issue.

Please try to update pytodotxt through pip install -U pytodotxt. There has been a fix recently that addresses that problem.
Let me know if that does the trick!

Yes, updating that package fixes the issue. Thank you!


Publish 02/22/2022 3:30 PM PT

Docs Build status updates of commit 325c3ab:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsOnlineUser.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Get-CsOnlineVoiceUser.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


XHR requests time out even though jQuery ajaxSettings timeout is set to higher value

Description
Ajax call (with long server processing time), done via jQuery, has timeout set to value higher than 60 seconds.
Request times out after 60 seconds, unfinished, resulting in ajax error.
Timeout value in ajax settings is not respected in the plugin.
Preferences
<preference name="NativeXHRLogging" value="full" />
<preference name="AllowUntrustedCerts" value="true" />
<preference name="InterceptRemoteRequests" value="all" />
<preference name="allowFileAccessFromFileURLs" value="true" />
<preference name="allowUniversalAccessFromFileURLs" value="true" />

Expected behavior
When using $.ajaxSettings.timeout of e.g. 180000, I expect the network request to only err/timeout after 180 seconds, not earlier.
Device

Device: iPad
OS: iOS 14.2
Browser: WKWebView
Hybrid app: Cordova build, using VoltBuilder

Example call
$.ajax({
  type: "POST",
  contentType: "application/json",
  url: "url_to_server_endpoint",
  dataType: "json",
  timeout: 180000,
  data: encodeURIComponent("someJSONdata"),
  success: function (data) {
    // ...
  },
  error: function(result,status,errorThrown) {
    // ...
  }
});

The max timeout for a XMLHttpRequest in Safari & Chrome is 60 seconds.

Sorry, can't confirm this, longer timeouts are possible as well.
Following test:
Running cordova app on iPad, debugging in Safari on Mac.
Breaking at this line ...
https://github.com/globules-io/cordova-plugin-ios-xhr/blob/f1352921ac71d9e19da511d0db0c39be90bb15ab/src/www/ios/xhr-polyfill.js#L603
... and setting timeoutInSecs to 100 manually in console.
I'm then halting the server code with server-side breakpoints.

If I halt the server code for more than 100 seconds, then the request in the app ends with timeout.
If I halt the server code for anything between 60 and 100 seconds, and continue this way, the request ends successfully, XHR response is received.


Further coverage for compression

Hitting https://github.com/grpc/grpc/compare/master...dgquintas:compression_coverage_2?expand=1#diff-7fafa5ac05a9939cf1c9b30b01c8e828R73 remains ellusive though...

Can you take a few kb from /dev/random and try to decompress it as gzip?
On Wed, Dec 9, 2015, 5:26 PM David G. Quintas<EMAIL_ADDRESS>wrote:

Hitting
https://github.com/grpc/grpc/compare/master...dgquintas:compression_coverage_2?expand=1#diff-7fafa5ac05a9939cf1c9b30b01c8e828R73
remains ellusive though...
You can view, comment on, or merge this pull request online at:
https://github.com/grpc/grpc/pull/4381
Commit Summary

Further coverage for compression

File Changes

M src/core/compression/message_compress.c
https://github.com/grpc/grpc/pull/4381/files#diff-0 (10)
M test/core/compression/message_compress_test.c
https://github.com/grpc/grpc/pull/4381/files#diff-1 (40)

Patch Links:

https://github.com/grpc/grpc/pull/4381.patch
https://github.com/grpc/grpc/pull/4381.diff

—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/4381.

Not really portable :-)
On Wed, Dec 9, 2015 at 5:34 PM, Craig Tiller<EMAIL_ADDRESS>wrote:

Can you take a few kb from /dev/random and try to decompress it as gzip?
On Wed, Dec 9, 2015, 5:26 PM David G. Quintas<EMAIL_ADDRESS>wrote:

Hitting

https://github.com/grpc/grpc/compare/master...dgquintas:compression_coverage_2?expand=1#diff-7fafa5ac05a9939cf1c9b30b01c8e828R73

remains ellusive though...
You can view, comment on, or merge this pull request online at:
https://github.com/grpc/grpc/pull/4381
Commit Summary

Further coverage for compression

File Changes

M src/core/compression/message_compress.c
https://github.com/grpc/grpc/pull/4381/files#diff-0 (10)
M test/core/compression/message_compress_test.c
https://github.com/grpc/grpc/pull/4381/files#diff-1 (40)

Patch Links:

https://github.com/grpc/grpc/pull/4381.patch
https://github.com/grpc/grpc/pull/4381.diff

—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/4381.

—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/4381#issuecomment-163458311.

Copying it into a string and embedding it in the test is.
On Wed, Dec 9, 2015, 5:35 PM Nicolas Noble<EMAIL_ADDRESS>wrote:

Not really portable :-)
On Wed, Dec 9, 2015 at 5:34 PM, Craig Tiller<EMAIL_ADDRESS>wrote:

Can you take a few kb from /dev/random and try to decompress it as gzip?
On Wed, Dec 9, 2015, 5:26 PM David G. Quintas<EMAIL_ADDRESS>wrote:

Hitting

https://github.com/grpc/grpc/compare/master...dgquintas:compression_coverage_2?expand=1#diff-7fafa5ac05a9939cf1c9b30b01c8e828R73

remains ellusive though...
You can view, comment on, or merge this pull request online at:
https://github.com/grpc/grpc/pull/4381
Commit Summary

Further coverage for compression

File Changes

M src/core/compression/message_compress.c
https://github.com/grpc/grpc/pull/4381/files#diff-0 (10)
M test/core/compression/message_compress_test.c
https://github.com/grpc/grpc/pull/4381/files#diff-1 (40)

Patch Links:

https://github.com/grpc/grpc/pull/4381.patch
https://github.com/grpc/grpc/pull/4381.diff

—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/4381.

—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/4381#issuecomment-163458311.

—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/4381#issuecomment-163458427.

We need only one bad test vector.
On Wed, Dec 9, 2015, 5:43 PM Craig Tiller<EMAIL_ADDRESS>wrote:

Copying it into a string and embedding it in the test is.
On Wed, Dec 9, 2015, 5:35 PM Nicolas Noble<EMAIL_ADDRESS>wrote:

Not really portable :-)
On Wed, Dec 9, 2015 at 5:34 PM, Craig Tiller<EMAIL_ADDRESS>wrote:

Can you take a few kb from /dev/random and try to decompress it as gzip?
On Wed, Dec 9, 2015, 5:26 PM David G. Quintas<EMAIL_ADDRESS>wrote:

Hitting

https://github.com/grpc/grpc/compare/master...dgquintas:compression_coverage_2?expand=1#diff-7fafa5ac05a9939cf1c9b30b01c8e828R73

remains ellusive though...
You can view, comment on, or merge this pull request online at:
https://github.com/grpc/grpc/pull/4381
Commit Summary

Further coverage for compression

File Changes

M src/core/compression/message_compress.c
https://github.com/grpc/grpc/pull/4381/files#diff-0 (10)
M test/core/compression/message_compress_test.c
https://github.com/grpc/grpc/pull/4381/files#diff-1 (40)

Patch Links:

https://github.com/grpc/grpc/pull/4381.patch
https://github.com/grpc/grpc/pull/4381.diff

—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/4381.

—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/4381#issuecomment-163458311.

—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/4381#issuecomment-163458427.

I left some Python code in tools/codegen/core today to do the escaping...
Marry that with the read from random from some other Python script.
On Wed, Dec 9, 2015, 5:43 PM Craig Tiller<EMAIL_ADDRESS>wrote:

We need only one bad test vector.
On Wed, Dec 9, 2015, 5:43 PM Craig Tiller<EMAIL_ADDRESS>wrote:

Copying it into a string and embedding it in the test is.
On Wed, Dec 9, 2015, 5:35 PM Nicolas Noble<EMAIL_ADDRESS>wrote:

Not really portable :-)
On Wed, Dec 9, 2015 at 5:34 PM, Craig Tiller<EMAIL_ADDRESS>wrote:

Can you take a few kb from /dev/random and try to decompress it as
gzip?
On Wed, Dec 9, 2015, 5:26 PM David G. Quintas <
<EMAIL_ADDRESS>wrote:

Hitting

https://github.com/grpc/grpc/compare/master...dgquintas:compression_coverage_2?expand=1#diff-7fafa5ac05a9939cf1c9b30b01c8e828R73

remains ellusive though...
You can view, comment on, or merge this pull request online at:
https://github.com/grpc/grpc/pull/4381
Commit Summary

Further coverage for compression

File Changes

M src/core/compression/message_compress.c
https://github.com/grpc/grpc/pull/4381/files#diff-0 (10)
M test/core/compression/message_compress_test.c
https://github.com/grpc/grpc/pull/4381/files#diff-1 (40)

Patch Links:

https://github.com/grpc/grpc/pull/4381.patch
https://github.com/grpc/grpc/pull/4381.diff

—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/4381.

—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/4381#issuecomment-163458311.

—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/4381#issuecomment-163458427.

No dice. Trying with random data (different each time, using rand()) still goes out the "zlib: not all input consumed" branch

Can one of the admins verify this patch?

LGTM. Merge at will.


DJANGO_API: Publish of a dandiset during upload silently does nothing

I am still uploading https://gui-beta-dandiarchive-org.netlify.app/#/dandiset/000020 which is large in numer of files.  To check if I can publish while it is being uploaded (as it was suggested on what has happened in https://github.com/dandi/dandi-api/issues/199#issuecomment-811929491) -- I pressed Publish when it was at about 1900 files uploaded.  Nothing happened. Pressed again a few times - nothing happened.  In papertrail I saw some errors on that but since advised not to copy paste into public, I don't .  It happened around now (Thu 01 Apr 2021 05:59:10 PM EDT)
trying in swagger (curl analog was curl -X POST "https://api.dandiarchive.org/api/dandisets/000020/versions/0.000000.0001/publish/" -H  "accept: application/json") lead to
Code | Details
-- | --
404Undocumented | Error: Not FoundResponse bodyDownload{   "detail": "Not found." }

Silly me should've specified the version to publish not there desired version for it, so you get a  500 then without details


Instructions should be collection scripts instead of a README

Putting instructions on a README makes it hard to automake checks. You have no way of knowing when images become unavailable. I think you should instead just create a simple shell script that takes the URL of the resource to fetch, have the URLs in separate files, and test the wget return code.
This way you could easily script getting all the images and report when one is broken. Addind a new image would be as simple as putting a file on the repository.
To handle the metadata, you could just put in your data files something like:
IMAGE_URL=https://...
WINDOWS_VERSION_NUMBER="8.1"
WINDOWS_VERSION_NAME="Windows ${WINDOWS_VERSION_NUMBER}"

You source this file before calling your script, then call your script with these arguments, and you can do that in a loop.

Good idea - but not something I have the time to play with sadly.
I will update the image URL's to correct 8/9/10 images as per your last raised issue.
This repository is going to have diminishing returns anyway - at some point MS might stop offering IE8/9/10 images anyway as those browsers finally die a death they deserve and people move onto better quality browsers.


parsing the url with host returns no host

I am not sure if this is expected or is a problem.
For example when I use a example url like :
$uri = UriFactory::factory('www.test.de/test/bild1.jpg');
echo $uri->getHost();

I was would expecting it to actually get the host i.e. www.test.de but get null instead.
Can this be a bug or am I missing something?

It is because www.test.de/test/bild1.jpg is a relative url but not a valid relative url with authority. www.test.de here is just a part of the path.
Valid format for that url would be //www.test.de/test/bild1.jpg
Confusion can stem from the browser location bar, where user input is fixed to a proper url if first path segment looks like a valid hostname since browser does not accept path relative url there.
Please see https://tools.ietf.org/html/rfc3986#section-3.2

The authority component is preceded by a double slash ("//") and is
terminated by the next slash ("/"), question mark ("?"), or number
sign ("#") character, or by the end of the URI.


NATS Jetstream optimistic concurrency headers

Hi, folks! Is it possible to access the special NATS headers on send, for example Nats-Expected-Last-Sequence
These headers would allow event sourcing with CloudEvents. The neat thing is that consumers don't need to do anything. It's more like a quality of service between NATS client and the server.
If not currently possible, are there workarounds? Could we find a way to add support without breaking the current API?

If I understand the current nats_jetstream protocol implementation correctly, it ignores this header during the CE conversion: https://github.com/cloudevents/sdk-go/blob/e6a74efbacbf4ac70fc8ed598e678f94b6be7a6d/protocol/nats_jetstream/v2/message.go#L57-L97
IMHO it can be added without breaking the API similar to what we do in the Kafka protocol bindings.

I'd be happy with a change to enable this, but not sure on the correct approach. I'm not too familiar to how other protocol bindings work, but http just has an exported struct field:
https://github.com/cloudevents/sdk-go/blob/6408c0101c4ea93de70e28cd4624cb8c40f79027/v2/protocol/http/message.go#L37-L49
If you did something similar, users can then just do the following:
var msg binding.Message

if msg, ok := msg.(*jetstreamv2.Message); ok {
  fmt.Println(msg.Header)
}


Sends new toast instead of updating ?

Hello and thank you for this interesting project - just one step closer to VSCode feature parity :D
I've tried the plugin and it does work great, but with one small issue - it seems that it sends multiple nvim-notify notifications instead of updating the one.
I'm using a setup based on ecovim, so I don't think there's anything I've done which broke things. My setup is available at nvim-dotfiles.
I'm pretty new to Vim and don't know exactly how to debug this, although I do have a basic understanding of the pieces involved in the setup. I do see that updating notifications should be possible.
The notifications look like this:

Thanks again!

I'm seeing the same behaviour

You see I do something similar in my own dotfiles/configuration of nvim-notify (https://github.com/dmmulroy/dotfiles/blob/main/.config/nvim/after/plugin/nvim_notify.lua#L7-L14)
vim.notify = function(message, level, opts)
  for _, msg in ipairs(filtered_message) do
    if message == msg then
      return
    end
  end
  return notify(message, level, opts)
end

That fixed it, thanks a lot!

Awesome - the new PR is also up here https://github.com/ecosse3/nvim/pull/133 if you'd like to add any input.

I'm having the same issue with this minimal lazy.nvim configuration:
{ 'dmmulroy/tsc.nvim', config = true },
{
  'rcarriga/nvim-notify',
  config = function()
    vim.notify = require('notify')
  end
}

This is what :Notifications looks like after I've run :TSC with the config above:

Beautiful. Adding that return fixed this problem for me. Thank you!

@mawkler Most likely the hide_from_history option needs to be added to the notification options. https://github.com/dmmulroy/tsc.nvim/blob/main/lua/tsc/init.lua#L95

@mmirus That solves it! I've created a PR: #10

@mmirus That solves it! I've created a PR: #10

Awesome!


chore(plugins/github): update readme

What type of PR is this?
/kind cleanup
Any specific area of the project related to this PR?
/area documentation
What this PR does / why we need it:
This fixes some inaccuracies in the readme of the github plugin, including a broken link.
Which issue(s) this PR fixes:
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jasondellaluce
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jasondellaluce]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 8db81f0eb56896965672b21c7bc214135de2b481


Saving number-type values as actual numeric values

I noticed that when adding a new number-type value, it was stored as a string in the crate. In my opinion, it would be better to store numbers as numbers for clearer and more efficient data handling.

Good find @csontosreka

Could you please create a new release of this fix?

Ahh sorry - just created it.


Added Gitea, GitBucket, Bitbucket, Bitbucket Cloud and GitLab webhooks

References #12.
Added Gitea, GitBucket, Bitbucket, Bitbucket Cloud and GitLab webhooks support.
This pull request does not contain update on README or Dashboard/Integration page.
Gitea
Developed and tested with self-hosted version 1.4.0
https://docs.gitea.io/en-us/webhooks/
GitBucket
Developed and tested with self-hosted version 4.23.0
Uses SHA-1 for signature.
https://github.com/gitbucket/gitbucket/wiki/API-WebHook
(it says "The GitBucket api/webhook is designed for compatibility with GitHub's implementation.", but that is not fully true)
Bitbucket
Developed and tested with self-hosted version 5.10.0
Uses SHA-256 for signature.
https://confluence.atlassian.com/bitbucketserver/event-payload-938025882.html#Eventpayload-Push
Bitbucket Cloud
This one is only developed by documentation and sending custom REST requests.
Does not support (by documentation) secret nor signatures.
https://confluence.atlassian.com/bitbucket/event-payloads-740262817.html#EventPayloads-Push
GitLab
Developed and tested with self-hosted version 10.7.1
https://docs.gitlab.com/ee/user/project/integrations/webhooks.html#push-events
https://docs.gitlab.com/ee/user/project/integrations/webhooks.html#tag-events

Thanks a lot for your work, @tvrzna – TBH I didn't test any because I lack the time and capability to do so. If something doesn't work, someone will complain when they want to use it :')


Replace Brad with Dai

👍 merge when ready. However the code this is toggling probably needs removing anyway since it was an aborted project. @daibach should know if thats the case.


test: check headers for ansible_managed, fingerprint

Check headers of generated files for ansible_managed, fingerprint

@natoscott @kurik There seems to be an issue with the spark test - I've tried it with the current main branch code, on several different platforms:
TASK [Check if pcp2spark is running] *******************************************
task path: /home/rmeggins/ansible-pcp/tests/check_pcp2spark.yml:3
Tuesday 25 April 2023  09:29:17 -0600 (0:00:00.070)       0:00:58.215 *********
fatal: [/home/rmeggins/.cache/linux-system-roles/rhel-8-9.qcow2]: FAILED! => {
    "changed": false,
    "cmd": [
        "systemctl",
        "is-active",
        "pcp2spark"
    ],
    "delta": "0:00:00.013426",
    "end": "2023-04-25 11:29:18.314532",
    "rc": 3,
    "start": "2023-04-25 11:29:18.301106"
}

STDOUT:

activating

MSG:

non-zero return code

PLAY RECAP *********************************************************************
/home/rmeggins/.cache/linux-system-roles/rhel-8-9.qcow2 : ok=13   changed=5    unreachable=0    failed=1    skipped=0    rescued=0    ignored=1


go-ethereum: set meta.mainProgram = "geth"

This lets nix run nixpkgs#go-ethereum do something useful, namely run geth.
Also migrates go-ethereum to pkgs/by-name while we're at it.
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[x] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Thanks, @Aleksanaa. I've split the change into two commits.


Migrate registry build tools over from devfile/registry

Signed-off-by: John Collier<EMAIL_ADDRESS>Please specify the area for this PR
What does does this PR do / why we need it:
Migrates the existing build scripts and Dockerfile from https://github.com/devfile/registry to this repository. No functional changes were made to the build tools, just a small change to allow the registry folder to be specified. Once this PR is merged, I'll remove the build tools from the registry repo.
The build tools are still relatively simplistic, but we can make further, centralized improvements to them in this repository now (under the build-tools folder), rather than on a per-registry basis.
Which issue(s) this PR fixes:
N/A
PR acceptance criteria:
N/A
How to test changes / Special notes to the reviewer:

Git clone this repository and devfile/registry
cd to build-tools in this repository
run ./build.sh <path-to-cloned-devfile/registry>

Build should succeed and produce a devfile index container image.

@GeekArthur Thanks for the review. Review comments addressed, see my note about the index generator build.


NotAllowedError

NotAllowedError: The request is not allowed by the user agent or the platform in the current context, possibly because the user denied permission.

iOS 11.4


Port data out of Redis, and into an on-disk data storage

Currently, all data is stored in Redis, and backed up using the AOF. I would like to change this so that the source of data truth is disk.
Evaluate the options for switching from Redis to something that can handle on-disk storage. Everything is an option, from nosql to sql databases. Since my schema is currently implemented using a K/V store with no bells and whistles, it seems likely that a NoSQL database would be an easier port target.

I think that getting my data model and storage in a good state is necessary for supporting both Discord and Twitch


Question - can class-transformer distinguish access modifiers?

I use default config, it exposes private fields.
I defined this
private hidden: string = "test";

And hidden: 'test' found in plain object

No, it doesn't check private modifiers. You have to use the @Exclude decorator.

thx for answering


Travis build successful with failed publish task

Tool
Name: LuisGen
Platform: Travis - Linux - bash
Build Failing: # 1575.1
Describe the bug
When the CRON job fails in at least one of the tools, the build doesn't fail (which is fine), and neither does it show a message adverting about the failure in the publishing.
To Reproduce
Steps to reproduce the behavior:

Go to the Travis Build # 1575.1
Read the log where the LUISGen tool fails

Expected behavior
It would be great if the Travis Build had a message warning if any of the tools failed when publishing, although the other tools publish correctly.
Screenshots

[bug]

agree we could do something about this, but we won't so closing for now


Get depth buffer from the capture handle failed!

I am getting occasional failures when trying to obtain both the color image and body index from a Femto Mega camera. When it gets in this mode it stops receiving any images and I have to restart the system.
This is happening with the latest 1.10.8 version of the Orbbec SDK and version 1.10.1 of the K4A wrapper. Our users have also reported this in the 1.9 SDKs and with the Femto Bolt camera.
Could this be an issue of having frame sync off? If it receives a color frame without a depth frame?
The log:
[06/19 17:16:23.664511][info][45012][Pipeline.cpp:188] Check and set config start!
[06/19 17:16:23.664668][info][45012][Pipeline.cpp:223] Check and set config done!
[06/19 17:16:23.667423][info][45012][Pipeline.cpp:288] Try to start streams!
[06/19 17:16:23.667582][info][45012][VideoSensor.cpp:646] start OB_SENSOR_DEPTH stream with profile: {type: OB_STREAM_DEPTH, format: OB_FORMAT_Y16, width: 1024, height: 1024, fps: 15}, Backend Format: OB_FORMAT_Y16
[06/19 17:16:23.678731][info][45012][VideoSensor.cpp:646] start OB_SENSOR_IR stream with profile: {type: OB_STREAM_IR, format: OB_FORMAT_Y16, width: 1024, height: 1024, fps: 15}, Backend Format: OB_FORMAT_Y16
[06/19 17:16:23.700245][info][45012][VideoSensor.cpp:646] start OB_SENSOR_COLOR stream with profile: {type: OB_STREAM_COLOR, format: OB_FORMAT_BGRA, width: 1920, height: 1080, fps: 15}, Backend Format: OB_FORMAT_BGRA
[06/19 17:16:23.728324][info][45012][Pipeline.cpp:301] Start streams done!
[06/19 17:16:23.728559][info][45012][Pipeline.cpp:277] Pipeline start done!
[2024-06-19 17:16:25.137] [error] [t=45012] [K4ABT] ..\src\TrackerHost\DepthFrameBlobK4A.cpp (13): Initialize(). Get depth buffer from the capture handle failed!
[2024-06-19 17:16:25.138] [error] [t=45012] [K4ABT] ..\src\TrackerHost\TrackerHost.cpp (274): EnqueueCapture().  PID: 0x0669, SN: CL2K83P000X
[06/19 17:16:27.384353][info][43136][VideoSensor.cpp:303] VideoSensor destroyed, @OB_SENSOR_IR
[06/19 17:16:27.384440][info][43136][VideoSensor.cpp:303] VideoSensor destroyed, @OB_SENSOR_COLOR
[06/19 17:16:27.384781][info][43136][VideoSensor.cpp:303] VideoSensor destroyed, @OB_SENSOR_DEPTH
[06/19 17:16:27.619211][info][43136][Context.cpp:84] Context destroyed

You can set synchronized_images_only in k4a_device-configuration_t to ensure that all frame data is received simultaneously in one frameset. Otherwise, you will need to manually check it yourself

I'm seeing the same issue when only running depth and IR with sync turned off.  We have 3 running over ethernet.