bug: Cant open files "Could not find oil adapter for scheme ://"

Did you check the docs and existing issues?

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

Neovim version (nvim -v)
NVIM v0.9.5
Operating system/version
NixOS Unstable
Describe the bug
Whenever I try to open a file with oil i get the error above along with the following:
E5108: Error executing lua: ...ir/pack/myNeovimPackages/start/oil.nvim/lua/oil/util.lua:825: assertion failed!
stack traceback:
	[C]: in function 'assert'
	...ir/pack/myNeovimPackages/start/oil.nvim/lua/oil/util.lua:825: in function 'get_edit_path'
	...ir/pack/myNeovimPackages/start/oil.nvim/lua/oil/init.lua:668: in function 'open_next_entry'
	...ir/pack/myNeovimPackages/start/oil.nvim/lua/oil/init.lua:705: in function <...ir/pack/myNeovimPackages/start/oil.nvim/lua/oil/init.lua:550>

It seems to only happen when oil is opened floating
What is the severity of this bug?
breaking (some functionality is broken)
Steps To Reproduce

nvim -u repro.lua
:lua require("oil").open_float()
Select a file and press enter

Expected Behavior
The file should be opened
Directory structure
Any
Repro
-- save as repro.lua
-- run with nvim -u repro.lua
-- DO NOT change the paths
local root = vim.fn.fnamemodify("./.repro", ":p")

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

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({
    "git",
    "clone",
    "--filter=blob:none",
    "--single-branch",
    "https://github.com/folke/lazy.nvim.git",
    lazypath,
  })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  {
        "stevearc/oil.nvim",
        config = function()
            require("oil").setup({
              -- add any needed settings here
            })
        end,
  },
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

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

Did you check the bug with a clean config?

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

Please ensure you are on the most recent version of oil and provide a minimal init.lua file, such as provided in the bug report template. Ensure that the error reproduces when using that minimal init file.

Please ensure you are on the most recent version of oil and provide a minimal init.lua file, such as provided in the bug report template. Ensure that the error reproduces when using that minimal init file.

Where can i see the version?
I have provided the minimal init file which im using and I can reliably reproduce it. to prove it I have a gif here

Oh I just realized that the repro.lua in the template also has stuff to change paths etc. still with the exact template from the bug report
(
-- save as repro.lua
-- run with nvim -u repro.lua
-- DO NOT change the paths
local root = vim.fn.fnamemodify("./.repro", ":p")

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

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({
    "git",
    "clone",
    "--filter=blob:none",
    "--single-branch",
    "https://github.com/folke/lazy.nvim.git",
    lazypath,
  })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  {
        "stevearc/oil.nvim",
        config = function()
            require("oil").setup({
              -- add any needed settings here
            })
        end,
  },
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

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

)
It still happens exactly the same, perfectly reproducible

I have the same issue.  Neovim version: v0.9.5 on NixOS Unstable. This only happens when using open_float()

I have the same issue
$ nvim -v
NVIM v0.9.5
Build type: Release
LuaJIT 2.1.1693350652

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "
/nix/store/aszfdv0palw8vgpswijvgn273fip4306-neovim-unwrapped-0.9.5/share/nvim
"

Run :checkhealth for more info

Only in floating mode.

Crazy, this seems to only be happening in NixOS, and the issue is that where we expect to have the oil bufnr, instead we have a handle to the repro.lua bufnr. That means that somewhere in this block of code the current buffer changes from the oil buffer to the target file.
https://github.com/stevearc/oil.nvim/blob/010b44a79d497c697686e2727049d3dd215bbbd6/lua/oil/init.lua#L589-L643
There shouldn't be any way for that to happen, and it especially shouldn't be platform-dependent. I added a couple of debug print statements to this branch: https://github.com/stevearc/oil.nvim/tree/stevearc-nix-test
Could you do the repro again and show me what it prints when the error happens?

and it especially shouldn't be platform-dependent
For me, the issue occurs now only when I install and set up Oil through nixos package-manager. With Lazy everything works good, without any errors.

when installing oil like this
      package = pkgs.vimUtils.buildVimPlugin {
        pname = "oil.nvim";
        version = "2023-11-16";
        src = pkgs.fetchFromGitHub {
          owner = "stevearc";
          repo = "oil.nvim";
          rev = "3151d9dd616ea33fa219dd4b198f01c49d8f76c3";
          sha256 = "17mi1hs3jmmrxqxhykqf0xj91ssxzzzig7gmdlyak6pgwln2ziyr";
          fetchSubmodules = true;
        };
        meta.homepage = "https://github.com/stevearc/oil.nvim/";
      };

To check out your branch it doesn't happen anymore
@stevearc

@VoreckLukas that's concerning, because all I did in that branch is add some print statements. That might indicate that the issue is a very consistent race condition. I've reworked that branch to write to a log file instead of printing to hopefully get the error to trigger again. If you can get it to repro, the logs should be under ~/.local/state/nvim/oil.log (or if your XDG directories are different on NixOS, you can find the dir with :echo stdpath('log')).

I was a bit busy the last few Weeks and will try the branch out in a few days. Has to be noted though that the standard package delivered by nixpkgs works again


Unable to set custom layout

Custom layout is set when published, however, the ordering of the following events is jacked:

restoring default layout
setting custom layout
rendering page

Currently the page is rendering before the custom layout is set, which causes the setting of the custom layout to remove the page content.

fixed with version 1.2.3


Addnodes

Hello, are there any addnodes?  Ty

Hello, are there any addnodes? Ty

Hello TylerAnder,
At the moment not yet, we are in the launch phase of the project.

Hey sorry to bother you again, is there any official launch date? thanks

Hello @le2Ks
we are finalizing the binaries for the first version release, we just had a few hiccups with the project certificate to sign the binaries. Soon we will have version 1.0.

Hey sorry to bother you again, is there any official launch date? thanks

Hello @le2Ks we are finalizing the binaries for the first version release, we just had a few hiccups with the project certificate to sign the binaries. Soon we will have version 1.0.

Hello, sounds amazing! Can't wait! Will there be a presale or ICO phase where we can buy?

Hello @le2Ks ,
we probably won't have it, as it is a mineable and decentralized currency, only mining it to get it initially. :> > > Hey sorry to bother you again, is there any official launch date? thanks

Hello @le2Ks we are finalizing the binaries for the first version release, we just had a few hiccups with the project certificate to sign the binaries. Soon we will have version 1.0.

Hello, sounds amazing! Can't wait! Will there be a presale or ICO phase where we can buy?

Hello @le2Ks ,
we probably won't have it, as it is a mineable and decentralized currency, only mining it to get it initially. ⛏ ⚡

Hello @le2Ks , we probably won't have it, as it is a mineable and decentralized currency, only mining it to get it initially. ⛏ ⚡

Oh ok sounds good! Will look forward! Will there be a discord or telegram group as well?

Hello, at the moment we don't have it, maybe later along with the community.


BUG Always validate Member credentials against DRAFT stage

Our current authentication logic runs against whatever stage the current request runs. In theory this, could allow an attacker to login with an old password if:

the Versioned extension as been applied to Member and
the attacker can fool the authentication request to happen against an old stage.

This PR aims to redress this issue by making sure that we always fetch the user in the DRAFT stage.
Note
We considered treating this as a security issue but opted to handle it as a security enhancement as there's no way to exploit this by itself.

Just pushed a minor tweak to the unit test to logout our versioned Member at the end of the test.


Added reconfigurable video mode (RGB, IR)

This change is

Review status: 0 of 3 files reviewed at latest revision, 4 unresolved discussions.

cfg/Astra.cfg, line 26 at r1 (raw file):

video_type_enum = gen.enum([  gen.const(  "RGB", int_t, 0,  "RGB video mode"),
                              gen.const(  "IR", int_t, 1,  "IR video mode")],
                              "output mode")

Maybe the description should be "video RGB/IR switch" or something like that. "output mode" is the same string as output_mode_enum

cfg/Astra.cfg, line 28 at r1 (raw file):

                              "output mode")

gen.add("camera_override_mode", int_t, 0, "Override video type; 0=default, 1=IR", 0, 0, 1, edit_method = video_type_enum)

The text string has no RGB option. If RGB is default, maybe it should be "Override video type; 0=RGB(default), 1=IR" ?

include/astra_camera/astra_driver.h, line 167 at r1 (raw file):

  int camera_override_mode_;
  static const int RGB = 0;

even in a restricted namespace, these names are awful short and might cause a conflict. I would make them CAMERA_OVERRIDE_MODE_RGB and CAMERA_OVERRIDE_MODE_IR

src/astra_driver.cpp, line 402 at r1 (raw file):

      if (camera_override_mode_ == IR)
      {
        // ROS_ERROR("Cannot stream RGB and IR at the same time. Streaming IR only.");

Remove this. Actually, I'd also consider removing the return

Comments from Reviewable

Review status: 0 of 3 files reviewed at latest revision, 4 unresolved discussions.

src/astra_driver.cpp, line 402 at r1 (raw file):
Previously, c-andy-martin (C. Andy Martin) wrote…
Remove this. Actually, I'd also consider removing the return

and simplifying logic, didn't finish my above statement. I can't finish the review this moment, I'll look at it more later.

Comments from Reviewable

include/astra_camera/astra_driver.h, line 167 at r1 (raw file):
Previously, c-andy-martin (C. Andy Martin) wrote…
even in a restricted namespace, these names are awful short and might cause a conflict. I would make them CAMERA_OVERRIDE_MODE_RGB and CAMERA_OVERRIDE_MODE_IR

I can really go either way on this one, actually. Up to you.

Comments from Reviewable

Reviewed 3 of 3 files at r2.
Review status: all files reviewed at latest revision, 5 unresolved discussions.

src/astra_driver.cpp, line 474 at r2 (raw file):

      if (preferred_camera_mode_ == RGB)
      {
        // ROS_ERROR("Cannot stream RGB and IR at the same time. Streaming RGB only.");

same comment as above, remove this comment, and potentially clean up the logic and not have a return

Comments from Reviewable

Review status: 0 of 3 files reviewed at latest revision, 5 unresolved discussions.

cfg/Astra.cfg, line 28 at r1 (raw file):
Previously, c-andy-martin (C. Andy Martin) wrote…
The text string has no RGB option. If RGB is default, maybe it should be "Override video type; 0=RGB(default), 1=IR" ?

This isn't actually an option, but a description (only seen when mousing over). But I agree, and actually thought I had made that change already...

src/astra_driver.cpp, line 402 at r1 (raw file):
Previously, c-andy-martin (C. Andy Martin) wrote…
and simplifying logic, didn't finish my above statement. I can't finish the review this moment, I'll look at it more later.

Done.

src/astra_driver.cpp, line 474 at r2 (raw file):
Previously, c-andy-martin (C. Andy Martin) wrote…
same comment as above, remove this comment, and potentially clean up the logic and not have a return

Done.

Comments from Reviewable

Review status: 0 of 3 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Reviewed 3 of 3 files at r3.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

@BadgerTechnologies/rosteam @cratliff please do not merge this yet


Fixed MD issue with CHANGELOG

Coverage remained the same at 96.429% when pulling 6b5eeb31c011a56601eb80e0e6448c5204093880 on Update-change-log into 00dd20bc2e561e79a92ffa8f16f1616f8064e539 on master.


feat(db): make the SDK generic over the store

This PR make the SDK generic over the store and implements the MemoryStore, to keep the properties until the device is rebooted.

Closing this since it has been separated in #207, #210, #211, #212, #213, #214 and #215


dashboard bootstrap version

site use bootstrap 2.3.2, dashboard - 2.3.1 (less)
this is trivial, but will be fine have same versions in oscar 0.8

Since the dashboard is now bootstrap 3 i'm closing this one


[Release] 1.5

[NEW] Added the ability to retrieve the generated One-Time Password from the 1Password Login if available. {#163, #199}
[NEW] Added the ability to specify unsupported  characters when using the password generator options. {#36}
[NEW] Added nullability for improved compatibility with Swift projects. {#218, #241,#245}
[NEW] Our demo apps, ACME and ACME Browser are now written in Swift 1.2 and Swift 2.0 too. {#101}
[NEW] Added ability to use the WKWebView code when the Deployment Target is iOS 7.1 or earlier. {#214}
[IMPROVED] Simplified Web View Filling. {#200}
[IMPROVED] Fully compatible with iOS 9 and Xcode 7. {#238, #241}
[IMPROVED] Improved compatibility with the latest version of CocoaPods. {#187, #235}
[IMPROVED] Improved the README, the in-code documentation and spring cleaned the entire codebase. {#200, #202, #203, #206, 241}
[IMPROVED] Improved the password generator options. {#36}
[IMPROVED] Updated the collect and fill scripts for the latest 1Password Brain. {#193}
[IMPROVED] We now assert when the sender parameter is nil on iPad. {#226, #241}
[IMPROVED] Improved Google Search in ACME Browser. {#240}
[IMPROVED] ACME Browser is now a Universal app. {#242}
[FIXED] Fixed all xcassets warnings {#196}
[FIXED] Fixed an issue where the Password Generator length keys were not honoured in 1Password 5.5. {#35}
[FIXED] Fixed typo for the AppExtensionPasswordGeneratorOptionsKey constant. {#191}

:+1:


Custom toolbar button format

I've added a custom toolbar button to add a table using the format name 'better-table-plus'
I works, but I see the warning in the console:
quill:toolbar ignoring attaching to nonexistent format better-table-plus
Is there a format I should use here?

Turns out QuillJS will always throw this warning if you don't add a handler to the toolbar options, even if you add a handler in your extension class.
I ended up creating a separate extension just for the button - it includes a dummy method for the toolbar handler just to get rid of the warning.


Toggle for gen typings in Offense/Defense page, instead of settings

It would be nice to see this option right in the Offense/Defense tabs, rather than tucked away in settings
I use your site frequently when discussing balancing changes to romhacks, and sometimes they do or don't have modern types

hmm... well originally the gen selection was on the offense/defense tabs... but i moved it because of a suggestion that it took up a lot of room for something not frequently used haha
i'm not really sure what to do about this, because it's either wasted space or critical UI depending on what you like to do?
i could always make a setting to change where the setting shows up? 😖 haha that sounds super confusing


4.4.5: $f7.views.current is undefined, (and some types are broken?)

Framework7 version: v4.4.5
Platform and Target: Chrome 75, Cordova Android 8.0

Describe the bug
this.$f7.views.current is undefined
To Reproduce
console.log(this.$f7.views.current.router)
Expected behavior
this.$f7.views.current is not undefined

Actual Behavior
Error in nextTick: "TypeError: Cannot read property 'router' of undefined"
Screenshots

Additional context
Works fine in all previous 4.* versions of Framework7.
Also, some types are broken:

(I'm not sure about types, maybe it just a WebStorm problem with Typescript support?)

Can't see such issue, i have updated all my Vue apps with latest version without the issue. Probably something else is causing it. Do you have live example or JSFiddle?

Unfortunately, it's a huge complicated Vue application (wrapped by Cordova) with non-standard module system, so it may take too much time to separate all logic :( Maybe, that is the reason of errors, haha. I will comment here if I found a solution or something related to that problem.

I'm also experiencing this in React using the same version

Problem with types was an issue of my IDE, fixed by clearing a cache.


Test intersecting channels with real SAS

Thanks @WojSad for providing certs and cbsd data, since I wasn't able to access AGW.
Testing confirmed, that channels doesn't have to match spectrum inquiry channels.
Here are the details:
SpectrumInquiry response (part of it):
{
  "spectrumInquiryResponse": [
    {
      "cbsdId": "P27-SCE4255W/2107CW5000067",
      "availableChannel": [
        {
          "frequencyRange": {
            "lowFrequency":<PHONE_NUMBER>,
            "highFrequency":<PHONE_NUMBER>
          },
          "channelType": "GAA",
          "ruleApplied": "FCC_PART_96",
          "maxEirp": 18
        },
        {
          "frequencyRange": {
            "lowFrequency":<PHONE_NUMBER>,
            "highFrequency":<PHONE_NUMBER>
          },
          "channelType": "GAA",
          "ruleApplied": "FCC_PART_96",
          "maxEirp": 18
        },
        ...

Grant request:
{
    "grantRequest": [
        {
            "cbsdId": "P27-SCE4255W/2107CW5000067",
            "operationParam": {
                "maxEirp": 18,
                "operationFrequencyRange": {
                    "lowFrequency":<PHONE_NUMBER>,
                    "highFrequency":<PHONE_NUMBER>
                }
            }
        }
    ]
}

Grant response:
{
  "grantResponse": [
    {
      "cbsdId": "P27-SCE4255W/2107CW5000067",
      "grantId": "3555-3565-881079",
      "grantExpireTime": "2022-04-07T12:32:16Z",
      "heartbeatInterval": 200,
      "channelType": "GAA",
      "response": {
        "responseCode": 0
      }
    }
  ]
}


assertIsDisabled() and assertIsNotSelected() should fail on inexisten…

…t elements. Fixes #100
Description
Fixes #100
Type of change
Please delete options that are not relevant.

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

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules


reject when expected MM match fails

closes #73

Hey @GabrielBuragev, thanks for posting the original issue. I asked around to understand why we chose to have detectEthereumProvider always resolve even when no provider was detected. The reason is that although this may not be a positive result, we don't consider it to be an unexpected one (it is just another possibility). Therefore, I don't think there's a case in which we would want to reject.
That said, I can see why you might have thought to make a change, given that detectEthereumProvider already distinguishes between one of two negative results: either a provider was not found, or it was and it's not a MetaMask provider.
So there are two options here. The first is that instead of having detectEthereumProvider return a single value, the provider, it could return an object that includes possible error messages:
const { provider, error } = await detectEthereumProvider();

if (error) {
  // This would either throw "Unable to detect window.ethereum." or "Non-MetaMask window.ethereum detected."
  throw error;
}

// Otherwise, assume we have a provider and carry on.

While this could work, I would argue that this isn't the most versatile API. My suspicion is that inevitably, either you (or someone else) will want to understand why exactly provider is null, or at the very least you will want to customize the error message. Of course you could check for the error message if you want, à la:
if (error === "Unable to detect window.ethereum.") {
  throw new Error("Could not locate an Ethereum provider. Do you have MetaMask installed?");
} else if (error === "Non-MetaMask window.ethereum detected.") {
  throw new Error("It looks like you have a wallet installed, but it's not MetaMask. Please install this first.");
}

As it stands, it is already possible for you, the developer, to distinguish between these cases, by checking the result of what you get back. That way if you want to, you can say:
const provider = await detectEthereumProvider();

if (!provider) {
  throw new Error("Could not locate an Ethereum provider. Do you have MetaMask installed?");
}

if (!provider.isMetaMask) {
  throw new Error("It looks like you have a wallet installed, but it's not MetaMask. Please install this first.");
}

or of course you can group these together:
const provider = await detectEthereumProvider();

if (!provider || !provider.isMetaMask) {
  throw new Error("Could not locate MetaMask. Do you have it installed?");
}

What do you think? Would the existing solution work for you?

@mcmire Thank you for the lengthy explanation here!
I was a little bit confused by the API as i would expect a different return for these two cases (or a rejection for the second one):

No attached provider was found on window object
An attached provider was found but it was not MetaMask (when explicitly requesting it by setting the mustBeMetamask arg to true)

In my opinion it made more sense to expect a rejection when we use the mustBeMetamask for easier differentiation but now i completely understand your reasoning for having it the way it is currently.
Your 2nd offered solution will perfectly suffice my case.
Thanks again for the swift response! Feel free to close this PR and the respective issue.


Non-upgradeable deploys, round 2

Supercedes #1240. Fixes #802.
This is quite a large pull request that adds a new deploy command that can be used for deploying both upgradeable and "regular" contracts.
The new command was built following a different architecture than all the current commands, as an experiment to see how we can refactor the entire commands layer to have better separation of concerns and better maintainability. The idea would be to refactor the rest of the codebase if we agree that this is an improvement.
In the current architecture there are command and script layers. The command layer provides a command's specification and action, and the action handles interactivity very explicitly by making use of the prompts module in the action flow. The script layer is very thin and almost all it does is error handling, and printing to stdout, then delegating to a controller.
The proposed architecture removes the scripts layer, and separates the command layer more explicitly into command specification and action. Interactivity is no longer a concern of the action, instead the command specification provides details for the behavior of each positional argument and option, and when the command is registered in the commander program these details are used to run interactive prompts prior to running the action.
The code for registering a command using this new architecture can be found in the register-command.ts file, including also the code for running the interactive prompts based on a command spec. There are no tests for this, but I think I should add a few before merging this.
The two parts of the new command are found in commands/deploy/spec.ts and commands/deploy/action.ts. This separation will allow for optimizing the loading time of the CLI because the dependencies of the action will not be imported unless the command is actually called. There is also commands/deploy/index.ts that provides the glue between the proposed architecture and the current architecture.
One of the things that I think should be improved is the naming around prompt, Question, etc., in the args and opts specification. I kind of picked these names quickly and kept them but they're not good.

I still haven't finished resolving all the review comments, but I'm signing off for today. Feel free to wait until I'm done with everything to re-review, or if you want you can also start taking a look now.


[WIP] Add integration test

Starter approximation of how we could do an integration test. Posting for feedback rather than suggesting this is a good approach...
Why:
First stab at what an integration test might look like.
This change addresses the need by:

Add a Fixture which is a basic CommandLine app
Add types with different visibility
Run a test using a make task

Build the tool
Build the fixture
Diff the generated output against a known value

Couldn't comment on it directly, but looks like your Xcode user data has been included in the MR (we don't have a full Swift gitignore setup)
No harm, but might wanna just clean that up! 😄


Socket gem basic material can be renamed in anvil and work as a socket [BUG]

Actual Behavior
My socket gem material ID is Quartz. Players can make their own fake socket gems by putting normal quartz into the anvil and renaming it to the exact name (Needles I) for example. Then they can put it into armor and the armor gets all the right properties of the real socket.
Do you know about this bug? Is there any way to prevent this? I use "prevent-crafting-with-gems: true" but that only works for renaming true socket gems, not the material ID item.
Possible workaround would be using a base item which players cant get in the survival, but I am trying to find a different solution first.
Cheers!

Any chance that this can be revisited? It's been over a year and I am now dealing with this same issue on my server.
@zorkenlide Were you ever able to find a good workaround for this? I was also thinking of using an unobtainable item for my sockets but that seems like a sub-par solution.
Thanks!

This isn't an issue if you're on the latest version of MythicDrops, running Minecraft 1.16+, and have disable-legacy-item-checks set to true. The issue comes when disable-legacy-item-checks is set to true and we need to check against item name instead of persistent data stored on the item itself.
If we're only using the persistent data (non-legacy) check, then we can ignore the names of the items and just check the data to see if the item is a socket gem.
There isn't really a good way to prevent this from happening without disabling the legacy check, as colors in the socket gems can change and the format of the socket gem name can change (and it can clearly be abused).

Yes, I was just coming back to here after seeing that there was a newer version than the one that I had. I assumed that since there was an issue here still not closed that it was still an issue in the latest version, but after some experimentation with the new version, it is not an issue. Thank you!


Migrated to AsyncKeyedLock which cleans up from the dictionary

@renataylor824

@renataylor824 ?

@renataylor824 ?

@renataylor824 ?

@renataylor824  are you interested or shall I close this PR?

@renataylor824 please let me know


Agent Elasticsearch Highlevel Client  cannot use in trace query

Please answer these questions before submitting your issue.

Why do you submit this issue?
[x]  Question or discussion
[ ] Bug
[ ] Requirement
[ ] Feature or performance improvement

Question

What do you want to know?
I use java agent 6.6 version,  In supported middlewire list, support rest-high-level-client,
My  Rest-high-level-Client is 7.0.1,but  In SkyWalking UI Trace query,cant not query  es call
information,what reason?

Bug

Which version of SkyWalking, OS and JRE?

Which company or project?

What happen?
If possible, provide a way for reproducing the error. e.g. demo application, component version.

Requirement or improvement

Please describe about your requirements or improvement suggestions.

Check the supported list document in 6.6.

Check the supported list document in 6.6.

6.6 supported list have high level client, but can not record  trace infomation

Check the test scenario in the test/plugin-test folder. You could find how it is tested.


question : how to use convertLead()

I am trying to call leadConvert function via jsforce lib
import { SoapApi } from "jsforce";
const soapApi = await new SoapApi(conn);
conn.soap.convertLead //has no exported member 'SoapApi'.
Following the documentation - https://jsforce.github.io/blog/posts/20150816-jsforce15-released.html. I am setting up connection like below
connection = new Connection({ loginUrl : this.loginUrl});
userInfo = await connection.login(this.user, this.password);
and then,
conn.soap.convertLead(leadConverts, function(err, res) {}
Property 'soap' does not exist on type 'Connection'.
Any clue? how to solve this.

Per my comment to your SO question, it seems to work just as expected for me:
https://stackoverflow.com/questions/50958561/how-to-call-convertlead-via-jsforce
Are you able to establish the connection successfully? Do other operations work as you expect them to?


Allow for Potential terms in joint_logprob

Potential terms are arbitrary terms that are added to the logprob graph without "values".
Would something like this make sense?
x_rv = at.random.normal()
potential = at.switch(x_rv < 0, -np.inf, 0)

x = x_rv.clone()

joint_logprob([x_rv, potential], {x_rv: x, potential: None})

What's required beyond the use of Aesara's existing addition Op on the output of joint_logprob?

RV -> value replacement

RV -> value replacement, otherwise there is no reason why it would require joint_logprob

We have a function that does that part alone, no?

Sure we do, it's the rv_to_values

Reopening, another reason to parse Potentials in joint_logprob would be when dealing with transforms

Don't forget that transforms are independent of joint_logprob.

What does the model in the first message represents mathematically speaking?

What does the model in the first message represents mathematically speaking?

The same as
x = at.random.normal("x")
x_vv = at.scalar("x_vv")

logp = joint_logprob({x: x_vv}) + at.switch(x_vv < 0, -np.inf, 0)

The point being that the potentials are first defined in terms of RVs, and then get replaced by the respective value (or potentially transformed) variables.

By the way I am not very married to this idea. The concern is just to help users bridge the RV-Value duality more easily. Perhaps improving rvs_to_values to accommodate value transforms would be a better approach.

Perhaps improving rvs_to_values to accommodate value transforms would be a better approach.

I think that makes more sense


test: fix merge snafu with integration_admin_test.

Race between two PR merges that interacted with the ConfigDump proto (they were both green on
CircleCI prior to the merge).
Signed-off-by: Harvey Tuch<EMAIL_ADDRESS>

@ambuc @envoyproxy/maintainers


custom request execute twice if all the rules success passed, with laravel v5.8.26

Laravel Version: v5.8.26
PHP Version: 7.1.21
Database Driver & Version: MySQL & 5.7.23

Description:
A custom request class in Laravel will validate before entering a controller action, but all methods in the custom request will be executed twice if all the verification rules are passed.
if some rules got error, executed only once.
Steps To Reproduce:
Example Controller
<?php

namespace App\Http\Controllers\Api\V1;

use App\Http\Requests\Api\V1\TestRequest;
use Illuminate\Support\Facades\Log;

class AdminOrdersController extends \App\Http\Controllers\Controller
{

    public function cancel(TestRequest $request)
    {
        Log::info("test3:".time());
    }

}

Example Custom Request:
<?php

namespace App\Http\Requests\Api\V1;

use Illuminate\Foundation\Http\FormRequest;
use Illuminate\Support\Facades\Log;

class TestRequest extends FormRequest
{
    /**
     * Determine if the user is authorized to make this request.
     *
     * @return bool
     */
    public function authorize()
    {
        Log::info("test1:".time());
        return true;
    }

    /**
     * Get the validation rules that apply to the request.
     *
     * @return array
     */
    public function rules()
    {
        return [
            'orderNo' => [
                'required', 'integer',
                'exists:orders,order_no',
                function ($attr, $value, $fail) {
                    Log::info("test2:".time());
                }
            ],
        ];
    }
}

for the example code above, if all the verification rules passed, logs like below:
[2019-06-27 13:01:58] local.INFO: test1:1561611718
[2019-06-27 13:01:58] local.INFO: [SQL] select count(*) as aggregate from `orders` where `order_no` = ? ["5614450133994844"]
[2019-06-27 13:01:58] local.INFO: test2:1561611718
[2019-06-27 13:01:58] local.INFO: test1:1561611718
[2019-06-27 13:01:58] local.INFO: [SQL] select count(*) as aggregate from `orders` where `order_no` = ? ["5614450133994844"]
[2019-06-27 13:01:58] local.INFO: test2:1561611718
[2019-06-27 13:01:58] local.INFO: test3:1561611718

if some verification rules fails, logs like below:
[2019-06-27 13:04:10] local.INFO: test1:1561611850
[2019-06-27 13:04:10] local.INFO: [SQL] select count(*) as aggregate from `orders` where `order_no` = ? ["5614450133994845"]
[2019-06-27 13:04:10] local.INFO: test2:1561611850

why executed twice if all the verification rules are passed?

Did you do anything special to "register" the request?

Did you do anything special to "register" the request?

nothing to do.

found the reason, this is a bug caused by dingo/api, v2.2.3 is work. v2.2.4 and v2.3.0 are all meet this bug.

@plhwin If it's caused by a 3rd-party-package then it does not apply here and should be closed. :)

I fork dingo/api project from 2.4.0 to my github repository , and i comment the twice call code , and i submit it in the composer "jameskid/dingo-api-fix-twice": "v1.0.0" , then , it's ok.


Unexposed options => Raw?

There are a number of unexposed client and server options.
Would you consider adding an options block that would take a key => value set? that would let this handle a larger number of unexpected variations with minimal coding required.

That sounds like a great idea.  Would you take a shot at a PR?

Closing this...


Added circuit equivalence checking to examples

Good! Do we have good examples?
We spent quite some time on that for this paper:
https://scirate.com/arxiv/2403.18813

Good! Do we have good examples? We spent quite some time on that for this paper: https://scirate.com/arxiv/2403.18813

Not yet, but I can start with the dataset used in that paper


Is 'main menu' flexible/common enough as a concept?

There's currently a limit of one "main menu" per site, which has fitted the projects we've used it on internally quite well, and means the templatetags can stay simple, but might that limitation hurt projects that may take a different approach to navigation? Can we increase flexibility without adding unnecessary complication?

With the flat_menu tag extended in v1.1.0 to allow multi-level rendering when required, I don't think the one-per-site limit on MainMenu is much of a problem any longer. The concepts of MainMenu and FlatMenu seem to fit the existing internal projects we've used it for well enough, so I don't feel an urgency to go back to the drawing board on those, and so I'm going to close this issue.


Profile-Guided Optimization (PGO) benchmark results

Hi!
Today I came up with an idea to try to optimize the library performance with PGO (as I already did for many other applications - all the results are available here). I performed some tests and want to share the results. Hopefully, for varpro users, the results will be interesting to read. Please do not treat this as an actual issue - it's just a performance report.
Test environment

Fedora 39
Linux kernel 6.7.3
AMD Ryzen 9 5900x
48 Gib RAM
SSD Samsung 980 Pro 2 Tib
Compiler - Rustc 1.76
varpro version: the latest for now from the main branch on commit f2adeec4a100714d7915fb7014ce09d91246d299
Disabled Turbo boost (for more stable results across benchmark runs)

Benchmark
Built-in benchmarks are invoked with cargo bench. PGO instrumentation phase on benchmarks is done with cargo pgo bench . PGO optimization phase is done with cargo pgo optimize bench.
All PGO optimization steps are done with cargo-pgo tool.
Results
I got the following results:

Release: https://gist.github.com/zamazan4ik/1dc05d0f78e10ebe567988031e5a0cb2
PGO optimized compared to Release: https://gist.github.com/zamazan4ik/c20cd7d4a32d3d8202c3a1ec7890cd09
(just for reference) PGO instrumented compared to Release: https://gist.github.com/zamazan4ik/1ba5190ceac795e048cb7fa09e3bcb0c

At least in the provided by the project benchmarks, I see measurable performance improvements. I don't know how these benchmarks are helpful for real-life performance evaluation - I just believe the project maintainers in this case.
Possible further steps
I can suggest the following things to consider:

Perform more PGO benchmarks in other scenarios. If it shows improvements - add a note to the documentation about possible improvements in the tracing library performance with PGO (I guess somewhere in the README file will be enough).
Evaluate where and why PGO brings performance improvements. Maybe some helpful performance optimization insights can be gathered from it e.g. better code organization for better inlining decisions.

I will be happy to answer all your questions about PGO.

Wow that's amazing, thank you! I will definitely look into this but it might be a while before I get to it.


Enable all "ruff" checks

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#8  👈
#6 : 1 other dependent PR (#7 )
#5
master

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

Join @topher200 and the rest of your teammates on  Graphite


In 7.5 you get un-versioned DOIs even when using VersionedDOIIdentifierProvider to pre-register DOIs

Describe the bug
In a repository with DOI pre-registration turned on and using the VersionedDOIIdentifierProvider in identifier-service.xml, I still get non-versioned DOIs in pre-registration when I create a new version.
To Reproduce
Steps to reproduce the behavior:

Use the 7.5 release
Turn on identifier pre-registration in identifiers.cfg
Use VersionedDOIIdentifierProvider in identifier-service.xml
Create an item
Create a new version of this item
You get an entirely new DOI, and not one using the pattern olddoi.versionnumber

Expected behavior
If you use VersionedDOIIdentifierProvider, the pre-registered DOI should use the olddoi.versionnumber pattern.
Related work
https://github.com/DSpace/DSpace/pull/8423

From a first quick analysis: this probably is a bug in VersionedDOIIdentifierProvider. To decide whether an item gets a new DOI or a history based one, it looks out for a version history of an item: https://github.com/DSpace/DSpace/blob/main/dspace-api/src/main/java/org/dspace/identifier/VersionedDOIIdentifierProvider.java#L67
I guess that this doesn't work for workfspaceitems. Out of my head I don't know when a new version is added to the history. I would expect that this happens when the workspace Item is created, but I would need to check this. The WorkspaceItem is a wrapper around an Item. If this item is part of the version history, we should be able to find it. To fix this bug, I would go in this direction. Unfortunately, I currently miss the time to go in there deeper.

This should be re-tested in 7.6.  It's possible that #8752 could have fixed or improved the behavior.

Unfortunately I am not able to test that with DSpace 7.6 at this time (since I am a DSpace-CRIS user), but I would be also very interested, if the bug is fixed in that version.

We since moved to using the non-versioned DOIIdentifierProvider because we wish to have no semantics in our DOIs. But I will test this ASAP, as I reported the bug.

@tdonohue I have now tested this in 7.6.1 and can confirm that the issue persists. We do use versioned dois and the ability to be able to pre-register and show DOIs at submission stage would be really useful and improve our workflows considerably!

@amgciadev : Thanks for verifying this still exists in 7.6.1.  I'll leave this ticket open then in search of a volunteer.

@tdonohue I think I have found the root of the issue. I am doing some more testing and will update more details here shortly

@tdonohue just checking that this one is only waiting for reviewers now?

@amgciadev : Yes, it's waiting on reviewers.  Currently, our reviewer group is very small & many are busy doing major dependency updates right now per our Release Schedule in recent developer meetings: https://wiki.lyrasis.org/display/DSPACE/2024-03-07+DSpace+Developers+Meeting  (For instance, I am not available to do reviews at this time, but will pick them back up in mid-March)

[like]  Agustina Martinez-Garcia reacted to your message:

From: Tim Donohue @.>
Sent: Thursday, March 7, 2024 4:57:35 PM
To: DSpace/DSpace @.>
Cc: Agustina Martinez-Garcia @.>; Mention @.>
Subject: Re: [DSpace/DSpace] DOIs are un-versioned even when using VersionedDOIIdentifierProvider to pre-register DOIs (Issue #8675)
@amgciadevhttps://github.com/amgciadev : Yes, it's waiting on reviewers. Currently, our reviewer group is very small & many are busy doing major dependency updates right now per our Release Schedule in recent developer meetings: https://wiki.lyrasis.org/display/DSPACE/2024-03-07+DSpace+Developers+Meeting (For instance, I am not available to do reviews at this time, but will pick them back up in mid-March)
—
Reply to this email directly, view it on GitHubhttps://github.com/DSpace/DSpace/issues/8675#issuecomment-1984002990, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGHNIVSR7VM3LA25V7GLIE3YXCL77AVCNFSM6AAAAAAVC2BVQGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBUGAYDEOJZGA.
You are receiving this because you were mentioned.Message ID: @.***>


add: Kaleem Ullah

added profile

@kaleemullah786 Thank you so much for your contribution! Your efforts are greatly appreciated and will go a long way in improving our project. Please feel free to share it with others and Star the repo to help us grow even further!

Sure thank you.


Not work v3.4.4 on cordova ios

I'm tired of trying to solve the remote video problem on iOS.
When I use Android works perfectly, when trying to use iOS I can send audio and video, but I get neither audio nor video.
I am using the code below, please someone help me
connection.videosContainer = document.getElementById('videos-container');
connection.onstream = function(event) {
    var div = document.createElement('div');
    div.id = event.streamid || event.stream.id;

    div.appendChild(event.mediaElement);

    connection.videosContainer.insertBefore(div, connection.videosContainer.firstChild);
    connection.fixAllVideos();
};

connection.onstreamended = function(event) {
    removeStreamById(event.streamid || event.stream.id);
};

connection.fixAllVideos = function() {
    Object.keys(connection.streamEvents).forEach(function(key) {
        var event = connection.streamEvents[key];
        var div = document.getElementById(key);
        if (!div) return;
        var video = div.querySelector('video');
        if (!video) return;
        video.src = URL.createObjectURL(event.stream);
        video.play();

        document.getElementById('room-urls').innerHTML += key;

        setTimeout(function() {
            video.play();
        }, 2000);
    });
};

@muaz-khan cordova

I get the same problem :(

@muaz-khan I believe the problem is in this section, because I can send audio and video, I just do not receive remote audio and video in ios (iphone x, in the test)
connection.fixAllVideos = function() {
Object.keys(connection.streamEvents).forEach(function(key) {
var event = connection.streamEvents[key];
var div = document.getElementById(key);
if (!div) return;
var video = div.querySelector('video');
if (!video) return;
video.src = URL.createObjectURL(event.stream);
video.play();
    document.getElementById('room-urls').innerHTML += key;

    setTimeout(function() {
        video.play();
    }, 2000);
});

};

I've got the same problem, did you solve it?

@pimengd Not yet, I'm trying.

@pimengd Not yet, I'm trying. I'm waiting for a feedback from him @muaz-khan , I hope he can help me

@c3bola I didn't test cordova for a while. I'll make some tests & share updated demos as well.

Thanks @muaz-khan , I'll keep trying here.
I believe the error is just the loop to display the remote videos.
Thank you very much in advance

@muaz-khan If you have an example of how to use this upgrade, it would help me a lot.
https://github.com/muaz-khan/RTCMultiConnection/blob/master/docs/upgrade.md
An example that shows how to retrieve remote videos

connection.getAllParticipants().forEach(function(pid) {
    connection.getRemoteStreams(pid).forEach(function(sid) {
        console.log('getRemoteStreams', pid, sid);
    });

    // or below code
    var native = connection.peers[pid].peer;
    console.log('native.getRemoteStreams', native.getRemoteStreams());
});

Thank you very much @muaz-khan , I got the
var native = connection.peers [pid] .peer;
The example I have to display the video is
var event = connection.streamEvents [key];
var div = document.getElementById (key);
if (! div) return;
var video = div.querySelector ('video');
if (! video) return;
video.src = URL.createObjectURL (event.stream);
video.play ();
I'm not sure how to adapt it to this return, can you help me?

Please try this:
// updated according to your "onstream" event
connection.fixAllVideos = function() {
    Object.keys(connection.streamEvents).forEach(function(key) {
        var event = connection.streamEvents[key];
        var video = document.getElementById(key);
        if (!video) return;
        video.src = URL.createObjectURL(event.stream);
        video.play();

        setTimeout(function() {
            video.play();
        }, 2000);
    });
};

Or:
connection.fixAllVideos = function() {
    connection.getAllParticipants().forEach(function(pid) {
        connection.getRemoteStreams(pid).forEach(function(stream) {
            var video = document.getElementById(stream.id);
            video.src = URL.createObjectURL(stream);
            video.play();

            setTimeout(function() {
                video.play();
            }, 2000);
        });
    });
};

@muaz-khan
I tried it that way, and the error was video.play is not a function
connection.videosContainer = document.getElementById ('videos-container');
onnection.onstream = function (event) {
document.body.appendChild (event.mediaElement);
var div = document.createElement ('div');
div.id = event.streamid || event.stream.id;
div.appendChild (event.mediaElement);
connection.fixAllVideos ();
}
connection.fixAllVideos = function () {
Object.keys (connection.streamEvents) .forEach (function (key) {
var event = connection.streamEvents [key];
var video = document.getElementById (key);
if (! video) returns;
video.src = URL.createObjectURL (event.stream);
video.play ();
setTimeout (function () {
video.play ();
}, 2000);
});
};

@muaz-khan
I tried that way,
This way, it does not return an error, but it also does not display the remote video.
connection.getRemoteStreams (pid) .forEach (function (stream) {
empty back stream
I tried it
var native = connection.peers [pid] .peer;
I was returned an object
connection.videosContainer = document.getElementById ('videos-container');
connection.onstream = function (event) {
var div = document.createElement ('div');
div.id = event.streamid || event.stream.id;
div.appendChild (event.mediaElement);
connection.videosContainer.insertBefore (div, connection.videosContainer.firstChild);
connection.fixAllVideos ();
}
connection.fixAllVideos = function () {
connection.getAllParticipants (). forEach (function (pid) {
connection.getRemoteStreams (pid) .forEach (function (stream) {
var video = document.getElementById (stream.id);
video.src = URL.createObjectURL (stream);
video.play ();
                setTimeout (function () {
                    video.play ();
                }, 2000);
            });
        });
    };

@muaz-khan this is the return of this function
connection.getAllParticipants().forEach(function(pid) {
var native = connection.peers[pid].peer;
console.log('native.getRemoteStreams', native.getRemoteStreams());
});
native.getRemoteStreams()[object Blob]
_listeners
addEventListener
removeEventListener
dispatchEvent
localDescription
remoteDescription
signalingState
iceGatheringState
iceConnectionState
pcConfig
pcId
localStreams
remoteStreams
onicecandidate
onsignalingstatechange
oniceconnectionstatechange
onremovestream
nativeClose
close
createOffer
createAnswer
setLocalDescription
setRemoteDescription
addIceCandidate
getConfiguration
getLocalStreams
getRemoteStreams
getStreamById
addStream
removeStream
createDataChannel
createDTMFSender
getStats
native.getRemoteStreams()[object Blob]
_listeners
addEventListener
removeEventListener
dispatchEvent
localDescription
remoteDescription
signalingState
iceGatheringState
iceConnectionState
pcConfig
pcId
localStreams
remoteStreams
onicecandidate
onsignalingstatechange
oniceconnectionstatechange
onremovestream
nativeClose
close
createOffer
createAnswer
setLocalDescription
setRemoteDescription
addIceCandidate
getConfiguration
getLocalStreams
getRemoteStreams
getStreamById
addStream
removeStream
createDataChannel
createDTMFSender
getStats

Hello @muaz-khan , I was able to get the remote id with this command
#for (var k in connection.peers[pid].peer.remoteStreams) {}
k = id remoto
For the local video I used,
var div = document.createElement('div');
div.id = event.streamid || event.stream.id;
#div.appendChild(event.mediaElement);
#connection.videosContainer.insertBefore(div, connection.videosContainer.firstChild);
div.id gets the id that this row returns,
However, I can not view the remote video
Can you help me?
This is my complete code
connection.peers.getAllParticipants().forEach(function (pid) {
for (var k in connection.peers[pid].peer.remoteStreams) {
connection.getRemoteStreams(k).forEach(function (stream) {
var div = document.createElement('div');
div.id = stream.id;
var video = document.getElementById(stream.id);
video.src = URL.createObjectURL(stream);
video.play();
                     setTimeout(function () {
                         video.play();
                     }, 2000);
                 });

}
});

I has the same problem, but I solved it. Maybe this can help you :)
I found that my remote video has a width of 0.
After I set the size to remote video, it succeeded.


Setup skeleton + infrastructure for Maps interaction

Write Model classes Location and Itinerary
write view model class(es) for interaction with firebase
do some tests on UI to see what we can achieve with maps UI
Deliver a first working composable to Thomas who is working on setting up navigation

Infos

Estimate Time
h

Time Spent
h


Removed the call to name property of the protobuf enum

Description
The field finish_reason, which is a protobuf enum, becomes an int externally.
The fix is to simply use Python native string interpolation. Then, it would work as both a protobuf enum field via protobuf's str and as an int, which Python interpolates already.
Fixes # 10211
Type of Change
Please delete options that are not relevant.

[X] Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[X] I stared at the code and made sure it makes sense

Suggested Checklist:

[X] I have performed a self-review of my own code
[X] My changes generate no new warnings
[X] New and existing unit tests pass locally with my changes
[X] I ran make format; make lint to appease the lint gods

This fix causes another issue on collab & query engine still doesn't work, can you please fix this?

Thanks for the bug report! Looking into it now.

We've identified that this is not a client-side library error. Rather, this is a server-side error. We have filed a bug with Google. Will be updating soon when we make progress.

We've implemented the solution. When the change is rolled out to public, we will notify this thread again.

Is there a workaround or a temporary fix right now with llama-index? Or we can only wait?

There is a workaround. See https://github.com/pikalaw/llama_index/pull/16. Please do read the warning in the PR. The workaround should be applied for development only. We do not recommend deploying the workaround for production use for reasons explained in the PR https://github.com/pikalaw/llama_index/pull/16.
FYI, we do have a fix already. It is undergoing through Google's internal release process. Should be out by early next week.
Sorry for the wait!

The solution has been deployed to public. The issue found in https://github.com/run-llama/llama_index/pull/10232#issuecomment-1908629740 should be resolved now.


⚠ PrivateHD has degraded performance

In ecfbab4, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 2084 ms

Resolved: PrivateHD performance has improved in a3a7bbb.


dockerize it

Hello, I think what's missing from this fantastic project is support for docker, so as to be able to deploy the app anywhere and seamlessly.
For instance we should be able to:
1) Build the image
docker build -t darkwire .

2) Optionally push it to our private registry
docker tag darkwire private-registry/darkwire
docker push private-registry/darkwire

3) And ultimately run the app (in the production host)
docker run -d -p 3000:3000 private-registry/darkwire

I can send you a PR for a respective Dockerfile :)
What do you think?

Definitely, this is fairly simple enough. I will push up a dockerfile soon, thanks for the suggestion!

Cool! So it's ok to close the issue.
As a side note, I'm leaving here a reference to a relative commit https://github.com/geoder101/darkwire.io/commit/4b1c376e0971bffb472421c1a07247a789035dbc
Thanks!


ServiceBus: Checkstyle Part 8

PR contains only CheckStyle errors and warning fixes.

Can one of the admins verify this patch?


Empty modal

Version used: 1.8.0
{isShowMonthPicker && (
          <MonthPicker
            onChange={(event, newDate) => {
              switch (event) {
                case ACTION_DATE_SET:
                  changeMonth(moment(newDate));
                  break;
                case ACTION_NEUTRAL:
                  break;
                case ACTION_DISMISSED:
                default:
              }
              setIsShowMonthPicker(false);
            }}
            value={monthlyState.monthAndYear.toDate()}
            minimumDate={new Date()}
            maximumDate={new Date(2025, 5)}
          />
        )}

@andraantariksa hrmm I couldn't reproduce this one. Maybe a device theme color issue?

Sorry I also couldnt reproduce this issue anymore.


Using the value of one operation as input for another, within the same TransactionalBatch

This is mostly directed at @ealsur (sorry 😉 ) in reference to a comment he made on the blog post originally announcing TransactionalBatch as a feature.
At the bottom, he stated:
"Using a value from one operation as input of another within the same TransactionalBatch is not currently supported."
Which left me wondering... is that something which will change in the future? Is that kind of functionality on the roadmap?
The reason I'm interested: I'm currently putting together something which requires an atomic read-write, and it looks like the only way to currently achieve this with CosmosDB is via a stored procedure written in JavaScript. That's fine, I've almost finished writing it, but... that particular area of CosmosDB seems stagnant at best. (The main documentation for the server-side Javascript environment it uses hasn't been updated since 2018, for example.)
So it'd be great to get a little bit of clarification on the intended future direction for situations like mine.

@abhijitpai Could you share if this is something that is on the roadmap or any ideas?

@RichWK can you give an example of why you need atomic read-write?

It's basically the same situation as described in Tom Robinson's comment on that blog post I linked to. This is what's happening:

We have a frontend where a user can request 1 to 10 unique IDs
These IDs are sequential, so they might end up with "100,000,022", "100,000,023" and "100,000,024", for example
If two users make a request at exactly the same time, they must not receive the same IDs

Previously I had an Azure Function talking to a Cosmos DB and doing this:

Read the "current ID"
Increment by however many IDs the user requested
Update the new "current" value back to the database (and supply the user with their IDs)

But that resulted in the same IDs being issued if two people made a request at exactly the same time — hence my current situation, writing a stored procedure for an atomic read-write.
Am I approaching this incorrectly?

Mmmm number incremental identifiers for distributed databases is kind of a tight pinch, isn't it?

Is there any reason unique-keys wouldn't solve the issue?

@ealsur Hahah yes, when you put it like that... it doesn't sound great. 😄 The frontend has very low usage, so CosmosDB was attractive due to serverless billing recently having entered preview status.
So regardless, it seems like this is too much of an edge case to be supported in the .NET SDK.
@j82w There isn't actually more than a single record being created, ever — this is the entire database:

If you have low concurrency for the requests trying to get these unique ids, just a read-increment-replace loop where the replace uses optimistic concurrency control as per https://docs.microsoft.com/en-us/azure/cosmos-db/database-transactions-optimistic-concurrency#optimistic-concurrency-control may suffice. The caller is only provided with the ids after the replace has succeeded.
For high concurrency, stored procedures as you mentioned could be an option for now to achieve what you need.
We are looking at exposing item patch functionality with an increment operator in future that can help simplify this use case.

Thanks for the advice! Much appreciated. @abhijitpai


Bad links 5: Fix almost all broken L<> references

For links to manpages that do not exist, do one of two things:
    If it's inline text, replace L<foo(3)> with foo(), just the function name
    If it's a SEE ALSO line, remove the entry

I think it is wrong to have manpages with broken links, with the hope that someone will write them.
We have another tool to list undocumented API (the -u/-v flags to find-doc-nits).  I don't think the manpages should knowingly be wrong.

Closing due to lack of interest; branch removal next week in case anyone wants to pick up some of the less-controversial changes.


Open streamer links in new tab

Opens streaming links in new tabs similar to the way profile links work.
/cc @hummingbird-me/staff

@vevix Added


Switch to a different default builder language

Issue description
Bash is a pain to use, it would be nice to use a different language
Goal

If we want to switch the language, we have to make the language switchable first; an instant migration is impossible.
If we make the language switchable, we will have to support at least two languages, probably indefinitely.
If we support two or more languages, solutions from one can not be trivially reused in the other, and we double the community's support load in this area.
Meanwhile, you can already use any language as a builder

either by setting the derivation builder, avoiding bash and setup.sh entirely,
or by invoking the desired language in one or more of the phases

Neither of these solutions seems particularly problematic to me, so I do not believe this issue should be acted upon. We can instead address issues as they are raised by people who actually do this.
I'd be ok with closing this.

Another alternative builder demo, based on Tcl: https://sr.ht/~fgaz/tcl-stdenv/

@roberth

If we want to switch the language, we have to make the language switchable first; an instant migration is impossible.

As @DavHau wrote, that seems useful in itself

If we support two or more languages, solutions from one can not be trivially reused in the other, and we double the community's support load in this area.

What about the language-agnostic interface you and @DavHau suggested?

Meanwhile, you can already use any language as a builder
* either by setting the derivation `builder`, avoiding bash and `setup.sh` entirely,

* or by invoking the desired language in one or more of the phases

Neither of these solutions seems particularly problematic to me, so I do not believe this issue should be acted upon. We can instead address issues as they are raised by people who actually do this.

Precisely because it isn't the default (the point of this issue) or even a documented option, nobody will actually do this in nixpkgs. I think it would be seen as unnecessary except for the absolute biggest scripts. Meanwhile, small packages continue to suffer from bash pitfalls.

Being able to write a package's build script in a different language is great, but a lot less if you have to completely sidestep stdenv and all its machinery that are integral to Nixpkgs. It may never be seamless, but stdenv and hooks currently don't have any other option to interop than with Bash variables.
The builder language in Nix is switchable. Making the builder language in Nixpkgs switchable means having composition primitives that aren't Bash strings. Even if basically all of Nixpkgs never stops using Bash, a language agnostic interface would still be fantastically useful.

What about the language-agnostic interface you and @DavHau suggested?

What is the interface, if not execv + working directory?
That's pretty much what a derivation is. builder and args are literally execv and you get a transient working directory from Nix.
If you put bash there, you can use it to delegate the whole process or parts of it to other languages.
setup.sh is mostly just an elaborate way to "do stuff in sequence", and communication between phases rarely extends beyond the contents of the working directory.
I don't recall a concrete proposal, but I suppose you could let each phase or "builder program" write a file with environment variables that it would like to pass to the next things that will run, and make setup.sh (or its replacement) load that.

Precisely because it isn't the default (the point of this issue) or even a documented option

Here's an example in the Nix manual for how you could use python instead of bash https://nixos.org/manual/nix/stable/language/derivations#attr-builder

I think it would be seen as unnecessary except for the absolute biggest scripts.

That's because usually it is unnecessary, but I'll admit that a bash script can have too much inertia at its sell-by date. Is that a problem with bash or with the contributors who don't, or don't want to recognize that their solution has outgrown a shell language.

Meanwhile, small packages continue to suffer from bash pitfalls.

Sure, although I would reserve that word for actual suffering, and not "first world problems" like this.
It's that we're going to disagree on the severity of the issue, so let's make this discussion actionable.
What does it take to make using other languages inside a derivation easier?
Here's what I would recommend:

Add a  helper function to change the bash variables according to the contents of a file in a standard location, to be written by scripts in other languages, so that they can integrate fully into the phases (instead of the 95% integration that's execv). This way bash use can be reduced to the part that is pretty reliable: invoking other scripts.

Promote the use of other languages in documentation. Reference documentation should usually stick to simple examples, such as simple commands, but more elaborate examples and nix.dev could invoke a different language.

I agree, that setting env variables is what's mostly missing rn and that could be fixed.
Though then there is still the issue that bash is bad in handling structured data, so that's a bit harder to fix without replacing bash as the default builder. We could pass json files around to fix that as well.
For me, the creme de la creme of this endeavour would be to create an abstraction in the nix language of a build step that can be rendered into either a build phase or a derivation. That will allow to phase split on demand. While this is probably an orthogonal issue, it seems to have an impact on how we thing about phases and how much of an interface they need.

JSON files sgtm.
For the environment variables, the C representation by definition preserves structure and can be written without any escaping.
Bash variables do have more structure, but it has no native JSON support, so this part of the interface needs to be optional (to allow bootstrapping, and more minimal derivations if so desired).
Why do you think Nix has to define "build step" for us? What prevents us from defining it ourselves through Nix expressions?

Sorry my bad, with nix language i actually meant nix expression.


Sort results in output geojson file to make changes stable

At the moment the ordering of results in the output file is unpredictable because it depends on the ordering of the multiple threads querying the NBN API.  It would be better if this was stable, so reprocessing files generates less diffs.

Sort by... address? locID? gnaf_pid?

Hmmmm, I think gnaf_pid would probably work best but locID could also work.

    cutoff = (datetime.now() - timedelta(hours=1)).timestamp()
    for state in data.STATES:
        for file in glob.glob(f"results/{state}/*.geojson"):
            if os.path.getmtime(file) > cutoff:
                print('Skipping', file)
                continue
            print(file)
            result = geojson.read_json_file(file)
            result["features"] = sorted(result["features"], key=lambda x: x["properties"]["gnaf_pid"])
            geojson.write_json_file(file, result, indent=1)

Massive PR https://github.com/LukePrior/nbn-upgrade-map/pull/146


Bug: Access denied error doesn't isn't displayed when editing owner in security permissions

Description
In file explorer a folder I was editing had an access denied error when changing the owner, for files it will keep the old owner and stay the same when click ok and reopening.
Steps To Reproduce

Open a restricted folder (eg. C:/Windows) properties page
Open security page
Open advanced
Change the Owner user
Click Ok
See nothing happens. Reopening the panel will have the original owner

Expected behavior
UAC prompt should be displayed asking for admin access
Files Version
<IP_ADDRESS>
Windows Version
10.0.19043.1503
Relevant Assets/Logs
debug.log
debug_fulltrust.log

@Josh-65 can you add steps to reproduce?

Done

@Josh65-2201 While this issue won't happen because I deleted the functionality temporarily, we should think how to re-implement, concerning about ERROR_ACCESS_DENIED and elevation at runtime. Elevating at runtime is impossible because elevation means giving elevated security token to a process and getting it run in a separated sandbox. However, activating a COM instance can be elevated at runtime and File Explorer uses that.
As a user, what do you think of showing classic dialog (COM dialog) when it requires to be elevated instead of displaying denial of accessing. That dialog can be elevated at runtime without creating a new process. There's Win32API called EditSecurity in aclui.h
Ultimately, we may want to create our own COM interfaces to launch WinUI dialogs but registering COM interfaces requires to elevated at installation (this is blocker on Microsoft Store).

You mean opening this dialog when clicked?

If so yeah

I mean whole property sheet and advanced security property.
That dialog can be dredesigned ContentDialog though.

If it's not possible in Files then yeah that would work.

But we can show UAC with old dialog.

In that specific case, that seems like a good workaround for now.


New parameter for syntax checking

It would be nice to add comments in the tutorials pull request when there are syntax errors in the tutorials.
For this we need to have a new paramter we can pass to the tutorial-compiler. If the parameter is set the compiler has to store the detailed error message somewhere. In addition, we then need to modify the pipeline in the tutorials repository to read this information and comment it directly into the pull request.

Also add to the comment, if an environment is incomplete, the missing function

@GuentherJulian @denise-khuu Why do we need to define a new parameter? Are there cases where this behavior is not needed? It would be easier, if it will always comment syntax errors.

What informations should the error message include besides the the missing functions?


Change default retention policy from 'default' to 'autogen'

Hi @cslysy, we have found your signature in our records, but it seems like you have signed with a different e-mail than the one used in yout Git commit. Can you please add both of these e-mails into your Github profile (they can be hidden), so we can match your e-mails to your Github profile?

Hi @cslysy, we have found your signature in our records, but it seems like you have signed with a different e-mail than the one used in yout Git commit. Can you please add both of these e-mails into your Github profile (they can be hidden), so we can match your e-mails to your Github profile?

closing due to inactivity


[php-ext] : php hangs when fork is used

Full information in https://github.com/etsy/phan/issues/889

Fixed in 1.4.4


fix: build issues on visionOS

Summary
This PR fixes build issues for visionOS. The CACurrentMediaTime API comes from QuartzCore which was not imported in this file. Unfortunately, visionOS is more strict and requires explicit imports
Test plan
Build the app for visionOS

Wrong repo, the PR upstream was merged. I'll check if adding visionOS CI is doable


multi: add BuildOnion, SendOnion, and TrackOnion RPCs

Change Description
Initial exploration into possible approach for the addition of new SendOnion (and associated construction and tracking) RPCs to the daemon.

Opted for a very slim wrapper around direct delivery of UpdateAddHTLC to the HTLCSwitch for forwarding, eg: no extra tracking by way of ChannelRouter and the ControlTower structures. This may be suitable given intended use by central proxy with instantiated ChannelRouter component, but does put more burden on users of the RPC which do not re-use code for attempt tracking/persistence in this manner.
Error information is communicated via RPC protobuf message directly such that the error types can be recreated client side if desired - as would be the case if this RPC is used by a remotely instantiated ChannelRouter .

NOTE: This version of a SendOnion style RPC was influenced heavily by its intended use. How might the RPC change if it was to be utilized by users running a "normal" lnd deployment? Would the data persisted surrounding the forwarding of onions change (eg: perhaps the ControlTower would be involved in the flow)? What about with respect to error handling?
TODO

Decide whether its's preferable to allow users of SendOnion to specify the first hop by public key and map from that to a valid short_channel_id on the server. Messed around with some htlcswitch package interfaces for this to try and keep access to link functionality limited and it might be worthy of another pass to consider the options here.
Determine whether the persistence offered by the HTLCSwitch is sufficient for these RPCs or whether the onion must be persisted as suggested here.
Finalize contents of RPC protobuf messages.
moar tests and cleanup

cc @starius

@sputn1ck: review reminder
@calvinrzachman, remember to re-request review from reviewers when ready

@sputn1ck: review reminder
@calvinrzachman, remember to re-request review from reviewers when ready

@sputn1ck: review reminder
@calvinrzachman, remember to re-request review from reviewers when ready

@sputn1ck: review reminder
@calvinrzachman, remember to re-request review from reviewers when ready

@sputn1ck: review reminder
@calvinrzachman, remember to re-request review from reviewers when ready

@sputn1ck: review reminder
@calvinrzachman, remember to re-request review from reviewers when ready

@sputn1ck: review reminder
@calvinrzachman, remember to re-request review from reviewers when ready

@sputn1ck: review reminder
@calvinrzachman, remember to re-request review from reviewers when ready

@calvinrzachman, remember to re-request review from reviewers when ready

@sputn1ck: review reminder
@calvinrzachman, remember to re-request review from reviewers when ready

@sputn1ck: review reminder
@calvinrzachman, remember to re-request review from reviewers when ready

@sputn1ck: review reminder
@calvinrzachman, remember to re-request review from reviewers when ready

@sputn1ck: review reminder
@calvinrzachman, remember to re-request review from reviewers when ready

@sputn1ck: review reminder
@calvinrzachman, remember to re-request review from reviewers when ready

@sputn1ck: review reminder
@calvinrzachman, remember to re-request review from reviewers when ready

@sputn1ck: review reminder
@calvinrzachman, remember to re-request review from reviewers when ready

@sputn1ck: review reminder
@calvinrzachman, remember to re-request review from reviewers when ready


Cannot install package due to lack of setup.py

Hey, It seems that pip cannot install this package due to lack of setup.py.
Do you mind create one?
I found some resources that may helpful.
https://python-packaging-tutorial.readthedocs.io/en/latest/setup_py.html

@smy20011 Hi, thank you for the comment. Because of pyproject.toml and poetry.lock, this package can be installed without setup.py. If you still get installation errors after trying the commands described in README.md, please provide your python environment (e.g., OS version, python version, etc.) and the error log.

Can confirm it works.Thank you so much. It must due to some wired error in my conda config.


Kraken now supports XLMUSD & XLMEUR  yet Gekko throws an error

Kraken now supports again XLMUSD and XLMEUR
https://www.reddit.com/r/Stellar/comments/7y4m61/kraken_now_trading_xlm_usd/
https://api.kraken.com/0/public/AssetPairs
https://api.kraken.com/0/public/Ticker?pair=XLMUSD
https://api.kraken.com/0/public/Ticker?pair=XLMEUR
The API says that it's ok and yet the asset is not tradeable I get this error:

https://github.com/askmike/gekko/blob/cmroche-origin/product_updates/exchanges/kraken-markets.json

On your own risk (meaning we have not tested Gekko on these pairs), you can manually run the following to update Gekko:
cd gekko/util/genMarketFiles/
node update-kraken.js

In the next release we will have updated markets (assuming they work in our testing).


Another demo issue

📚 Documentation
(A clear and concise description of what the issue is.)
Add relevant screenshot or video (if any)
(Add here)

/assign

/assign


Fix compile error, due to merge conflict

Problem
There is a merge conflict between #8045 and #8068
Change overview
Fix build error
Testing
Manually verified by unit tests

Can you merge this as hot fix?


change:length not triggering inside layer groups

When the map layers are changed on the root level, the layercontrol updates automatically, but when layers change within a group, nothing happens. We need to also listen for change:length events inside groups.

Can't reproduce currently, pushing a new layer into a group updates the layercontrol just fine. Closing for now.
      setTimeout(() => {
        const newLayer = new TileLayer({
          source: new OSM(),
        });
        document
          .querySelector("eox-map")
          .map.getLayers()
          .getArray()[0]
          .getLayers()
          .push(newLayer);
      }, 2000);

Seems like this issue still is experienced: https://github.com/EOX-A/EOxElements/issues/242
Needs more testing.

Added a fix and tests in https://github.com/EOX-A/EOxElements/commit/470820a80ea68eb0c4047a7aa059b120c923ccb9. Now the change:length listener is added to the root collection and recursively to all group collections.


Release of v19.0.0-RC1

This release is scheduled for Tue  6 Feb 2024
Prerequisites for Release

[x] Notify the community on Slack.
[x] Make sure the release notes summary is prepared and clean.
Make sure important Pull Requests are merged, list below.

[ ] #247

Make sure release blocker Issues are closed, list below.

Pre-Release

[x] Code Freeze.

https://github.com/frouioui/vitess/pull/241

[x] Copy branch protection rules.
[x] Update the SNAPSHOT version on main.

https://github.com/frouioui/vitess/pull/249

[x] Create Release PR.

https://github.com/frouioui/vitess/pull/244

[x] Create new GitHub Milestone.

https://github.com/frouioui/vitess/milestone/7

Release

[x] Merge the Release PR.

https://github.com/frouioui/vitess/pull/244

[x] Tag the release.

https://github.com/frouioui/vitess/releases/tag/v19.0.0-rc1

[x] Update release notes on main.

https://github.com/frouioui/vitess/pull/245

[x] Go back to dev mode on the release branch.

https://github.com/frouioui/vitess/pull/247

[x] Update the website documentation.
[x] Make sure the release is benchmarked by arewefastyet.
[x] Docker Images available on DockerHub.

Post-Release

[x] Notify the community on Slack for the new release.
[x] Twitter announcement.
[ ] Close this Issue.

Release completed.


Add advanced criteria

Similar to https://gist.github.com/paulcsmith/5b7ce214219021d9b2f6a350cc90d37a
Make it so types can specify which criteria to use

Closed by #18


Added my card data

Good job @1Fetcher
Congrats 🎉, your PR got merged. To be eligible for the swags from ClueLess. Follow this steps.
Note that this repo is excluded from Hacktoberfest but this PR is still eligible for ClueLess Swags.

Star this repository. ⭐

SignIn / SignUp in [ClueLess Website](https://www.clueless.tech/) .

Go to profile section from the top right hand corner.

Comment your profile URL under this comment tagging the person who merged your PR.

That’s it. Follow the leaderboard !
And don’t forget to share your achievement with your friends.

@Rajdip019
ClueLess Profile URL :
https://www.clueless.tech/profile/30271617


There are test failures

When I run mvn clean install
it stops when hit
testReplyComment(org.springframework.social.weibo.api.impl.CommentTemplateTest)
Build Failure
Please advice, thanks.

Thank you for using this project, I have just fixed the unit test. Sorry, for the convenience.


[Bug]: Input after 17 digit converts to 0 after loosing focus in Currency widget

Is there an existing issue for this?

[X] I have searched the existing issues

Description
The inputs after 17 digits are getting converted to 0 automatically in Currency Input widget
Steps To Reproduce

Drag & Drop Currency Input widget
Type in input with more 17 digits
Click outside of the currency widget
Observe that number after 17 digits got converted to 0

Public Sample App
No response
Issue video log
https://bthrujcsw8.vmaker.com/record/ladRprnBm6LCU28A
Version
Cloud / Production

Hi @chandannkumar
I would like to work on this issue.

Hello @MuhammadAakash can you please explain how you are thinking about the solution to this problem?

Hi @dilippitchika
First of all, I will figure out why this is happening, maybe there will be any type of validation of the length of numbers or the Currency widget is configured to only allow a certain number of digits.
If that is the case then i will remove that validation so it accepts if there are more than 17 digits in the input field

@dilippitchika
If you think there is any other better solution.
I would like to hear from you and then will start working according to that.

@MuhammadAakash what do you think should be limit if you now remove the 17 digit limit?

@dilippitchika
I think no limit because it totally depends on the user that how many digits he/she likes to enter.

Then i believe the problem will be in how large numbers are processed in JS. I think the 17 digit limit is already too large. Can you first investigate why there's a 17 digit limit?

@dilippitchika
Yeah sure I am cloning the repository, then I will start figuring out this limit.
But in JS The largest representable number is approximately 1.8 x 10^308, and the smallest is approximately 5 x 10^-324. Numbers outside of this range are considered "infinity" or "NaN" (not a number).

@dilippitchika
I have just visited the code and I found that where is the error
When the focus of input changes this function executes handleFocusChange and in this function, we are calling this function  getLocaleThousandSeparator to add a thousand separators in the value,
function getLocaleThousandSeparator() {       return Intl.NumberFormat(getLocale())         .format(11111)         .replace(/\p{Number}/gu, "");     }
JavaScript's Number.MAX_SAFE_INTEGER is<PHONE_NUMBER>740991 and<PHONE_NUMBER>23456789123 is much larger than that, so when passing this number to the Intl.NumberFormat will truncate the number and format it accordingly.
This means that any digits beyond the 17th digit will be truncated and not considered in the final value

Thanks for the triaging on this @MuhammadAakash really appreciate it, i don't think we need to fix today this as it's very unlikely to have a currency with 17 digits without decimals. I suggest we park this feature for now.

@dilippitchika
Sure.

Setting to low as people won't be facing this in a real scenario


Cow: Watch brosisint.com

Cow requests the watch of the watch_keyword brosisint\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

brosisint\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by cocomac in Charcoal HQ


Cartographer expects the IMU to point Z-wards

This report is a continuation of this thread on the Cartographer Google group. I think @SirVer is right, that Cartographer simply expects that the IMU is mounted with the z axis pointing upwards. The warning is caused by the following check in cartographer/mapping_2d/local_trajectory_builder.cc, which calculates the inclination of the IMU tracker orientation estimate from the z axis and complains if > 20:
  // Log a warning if the backpack inclination exceeds 20 degrees. In these
  // cases, it's very likely that 2D SLAM will fail.
  const Eigen::Vector3d gravity_direction =
      imu_tracker_->orientation() * Eigen::Vector3d::UnitZ();
  const double inclination = std::acos(gravity_direction.z());

If this assumption is not fulfilled (in our example, the IMU is mounted with the y axis pointing up), this inclination amounts to approximately 90 degrees and causes these seemingly harmless warnings about the maximum inclination being exceeded. Other than that, Cartographer seems to work fine.
I am not sure if I can definitely propose how to solve this. Perhaps this check can be rethought - e.g. transform the IMU tracker orientation estimate into the laser sensor frame, which by standard conventions should definitely have its z axis pointing up; then apply the check above in the same way.
If you would like to have a look for yourself, I have prepared an example bag which matches the situation described in the Google groups thread. To run, go into the launch folder and execute roslaunch t20_cartographer.launch from there.

I think we can just remove this check. It is a leftover from a different use case internally. @damonkohler Agreed?

+1


Failed to render Request.headers[0].value prior to sending

Describe the bug
Render error with curl like curl https://www.example.com/ --header 'foo: {%22bar%22}'
To Reproduce
Steps to reproduce the behavior:

create a new blank request
paste curl curl https://www.example.com/ --header 'foo: {%22bar%22}' in url box
click Send
See error

Expected behavior
Send request without error.
Screenshots

Desktop (please complete the following information):

OS: macOS 11.2.3
Installation Method: homebrew
App Version: Insomnia 11.2.3

@develohpanda do you happen to know how we could escape this?

in addition to escaping, it might be a good way to validate the template string before rendering it. and if invalid, it will be used as a raw string (refer to https://github.com/ramonsaraiva/jinjaninja)

Unfortunately I don't have a clear workaround for this 😞 is encoding the { } an option, or should the header sent to the server be exactly {%22bar%22}?

and if invalid, it will be used as a raw string

We certainly wouldn't want to do this by default but there could be scope for creating a user preference to support the behavior. Although I think supporting escaping would be a nicer solution, there's an existing feature request for that at #2355.
Also, currently there are request settings to disable rendering of environment variables in the request body. Maybe in the short term, that needs to be added for headers and query params as well.

Looks like you can use Nunjucks raw tags to enable this!


Barbell Graph

the barbell graph is two complete graphs connected by a bridge path
Syntax:
ag_catalog.age_create_tadpole_graph(graph_name Name,
                                    m int,
                                    n int,
                                    vertex_label_name Name DEFAULT = NULL,
                                    vertex_properties agtype DEFAULT = NULL,
                                    edge_label_name Name DEAULT = NULL,
                                    edge_properties agtype DEFAULT = NULL,
                                    bidirectional bool DEFAULT = true)

Input:

graph_name - Name of the graph to be created
m - number of vertices in both complete graphs
n - number of vertices in the bridge path.
vertex_label_name - Name of the label to assign each vertex to.
vertex_properties - Property values to assign each vertex. Default is NULL
edge_label_name - Name of the label to assign each edge to.
edge_properties - Property values to assign each edge. Default is NULL
bidirectional - Bidirectional True or False. Default True.

https://en.wikipedia.org/wiki/Barbell_graph

Working on this enhancement.

FYI: I did not close this issue, this was done by an automated task.
Please do not have automated tasks close issues under someone else's name without notifying others that you are doing so as this causes unnecessary confusion. @aked21


chore: Remove todo.md

For https://github.com/numberscope/frontscope/issues/86.

File is gone; npm run test:vue passes; npm run serve executes without warning or error; numberscope seems to work. Merging.


Add desec service provider to ddclient OPnsense backend

desec uses also dyndns2 protocol and can therefore directly added to the list of supported services. config is

Services: Dynamic DNS: Settings: Edit Account Enabled [X]
Service [desec (v6)]
Protocol  [DynDNS2]
Username [Your Domain]
Password [Your DeSec Token]
Hostname(s) [Your Domain]
Check ip method [Interface [IPv6]]
Force SSL [X]
Interface to monitor [Your WAN Interface]

Services: Dynamic DNS: Settings: Edit Account Enabled [X]
Service [desec (v4)]
Protocol  [DynDNS2]
Username [Your Domain]
Password [Your DeSec Token]
Hostname(s) [Your Domain]
Check ip method [Interface [IPv4]]
Force SSL [X]
Interface to monitor [Your WAN Interface]

@bringha1 thanks!


Class name seems incorrect

Hi.
In this example (line #36):
https://github.com/GeometryGym/GeometryGymIFCExamples/blob/master/consoleSummarizeElements/Program.cs
What is "IfcBuildingElement"? There is no such a class in GeometryGymIfc.
It seems it should be replaced with "IfcBuildingElementPart". I'm right?

Hi,
In IFC4.3 (not finalized yet), there was a decision to deprecate the class IfcBuildingElement and introduced a new class IfcBuiltElement.    As the GG toolkit supports simultaneous versions,  we renamed the base class.  I've just added a commit where this example is adjusted (and the others) to use the latest version of the nuget package.  Thanks for raising this.


feature: categorical variables ensure lowercase

Feature Request
Describe the Feature Request

Ensure all categorical variables are lower case by .tolowercase()

To make predictions if user type "Female" it must be stored "female" or "Male" to "male"


Precise free block translation

Sometimes we also need to precisely place blocks in free mode, for example the default free mode placement step does not allow us to match the road height of Tm2.

[left] Too high (+1m) [middle] Too low (+0m) [right] Perfect (+0.345m)
This module only work for TMNEXT obviously, that's why it's completely disabled for the other games.

Thanks for the pr! I'll set aside some time to review it this weekend

This looks like a good fit for the plugin and implemented pretty well. Thanks again 👍


Check hang on --panicOnWarning

https://discourse.gohugo.io/t/hugo-paniconwarning-hangs-forever/36548

I think I've found the bug. I'm going to do my best to follow the contributor guide to prepare a PR.

@Ephex2 That would be much appreciated (I've been a little busy myself lately ...)! The loggers.PanicOnWarning is a global variable (unfortunately, but that was a pragmatic choice ...); you should be able to trigger the panic in a test from hugolib, but remember to 1) Not call t.Parallel() and do a defer func() { loggers.PanicOnWarning = false } so the other tests don't ... panic.

I took note of the resetting the value of loggers.PanicOnWarning, thanks for pointing that out.
I found the bug in general.go, so I added the test into general_test.go -- let me know if there's a better test file to host it. I think that it can be put almost anywhere, since the only helpers function it uses is public.
I'll create the PR, let me know if you see anything amiss, I'm pretty new to contributing on GitHub.


Upgrade AWS Java SDK to support for EMR releases

Java SDK release 1.10.6 introduces support for
"emr releases" detailed here
This changeset introduces the ability to spawn EMR
clusters with emr-4.0.0, and also enables creating
EMR clusters with Spark preinstalled.

Added an DSL for adding Applications to JobFlowRequests
Added a SparkStep dsl + test

CircleCI is complaining update: sbt.ResolveException: unresolved dependency: com.typesafe.sbt#sbt-ghpage but sbt test:compile is working locally, please advise!

Thanks! Not sure about the circleci thing...we'll take a look.

I don't think I ever got the circleci integration working, but the Travis CI is passing so I think we're good.
Thanks, Phil!

Thanks @ogrodnek, are you able to push another build to Maven Central?

Just pushed to maven central as 1.2.5
On Thu, Sep 10, 2015 at 6:38 PM, Phil Kallos<EMAIL_ADDRESS>wrote:

Thanks @ogrodnek https://github.com/ogrodnek, are you able to push
another build to Maven Central?
—
Reply to this email directly or view it on GitHub
https://github.com/ogrodnek/spark-plug/pull/7#issuecomment-139426875.

Amazing, thanks!


Add CNAME

This adds a CNAME file to resolve routing issues.

Hopefully, fixes https://github.com/layer5io/meshery/issues/438


iFan03 is not working since 3.0.0 (e.g., light, fan and speed)

iFan03 has not been working since 3.0.0. Tried all version releases after 3.0.0 and still not working. Light and fan look available in the Device Page, however, when I press the button, it shows a popup saying: "Failed to call service fan/turn_on" and "Failed to call service light/turn_off"
In the Ewelink app, it still works nice.
Sonoff LAN: v3.0.5
iFan03 Firmware: v3.5.0
Home Assistant Core 2022.5.4
Home Assistant Supervisor 2022.05.2
Home Assistant OS 8.0
Kernel version 5.15.38
Agent version 1.2.1
Configuration.yaml:
sonoff:
username: !secret email2
password: !secret password1
force_update: [temperature, power]
scan_interval: "00:01:00" # (optional) default 5 minutes
sensors: [temperature, humidity, power, current, voltage]
devices:
1000f6e441:
device_class: [light, fan]
name: Ventilador
force_update: True
mode: cloud
Attached is the downloaded diagnostics.
sonoff-040a5976c1bd9aa6e9b2e31a8060d473-Ventilador-0263e9c0683442fdf5c4128d69aaa180.json (1).txt

You shouldn't use this device setting for iFan

Please reopen the issue if it is still relevant


ERROR: No loader is configured for ".webp" files

Hello!
I have a file that imports another file which imports .webp files. When I try to bundle it, I get this error for every .webp import:
/agents.ts:2:18: ERROR: No loader is configured for ".webp" files: /public/agents/Astra_icon.webp
How can we configure this loader?

I also note that I see the same issue for ".png".


Convert to helm thanos merge master

Thanos support to address Issue #23 long term storage.

@ramius345 I think since this has been sitting out for a while, we'll just merge and do a followup PR to address these.


I wonder use speech service Java SDK and return detailed result, anyone can help me?

When I use speech service SDK, I can only analyze wav file content info, rather than some valuable words' time offset and confidence.
I know REST method can return info above [when config is 'detailed'], but my wav files are more than 15 sec , so I have to use SDK method.
I found in Java there is a method in Java SDK: com.microsoft.cognitiveservices.speech.SpeechConfig,  and the methods below:
import com.microsoft.cognitiveservices.speech.OutputFormat;
config.setOutputFormat(OutputFormat arg);
but I didn't find out some clue to instantiate the type OutputFormat to 'detailed'
I also found current OutputFormat is Simple....
System.out.println(recognizer.getOutputFormat());
Anyone can help me? Thanks firstly~

This should work:
import com.microsoft.cognitiveservices.speech.OutputFormat;
SpeechConfig s = SpeechConfig.fromSubscription(...);
s.setOutputFormat(OutputFormat.Detailed);

Dear bro chlandsi, you are genius! @chlandsi
It really works fine, I search some methods could solve my problem according to your perfect codes. Thanks again!


[REVIEW] softavia

Project link
https://github.com/shahriarshafin/softavia

Looks good

center align logo.svg in README.md
hide wiki if not using
link https://softavia.vercel.app in README.md
create releases/tags

thanks for your suggestion


Certain pages fail when redis is configured but unavailable

When standing up a new demo that lacked redis, but had the redis URL defined in its pod environment variables, some pages seemed fine, but we found that other pages failed to load, and logged timeouts related to the redis cache.
Initial diagnosis here is that we have something (i.e. the GeneCoverage query, when loading the gene page) that is either:

not failing gracefully when it has a timeout connecting to redis
or, is waiting too long to try and connect to a dead/nonexistent redis and then timing out before it can retrieve the data from elasticsearch.

This would be a good case to try and resolve, so that the app is at least somewhat resilient to failures of the redis cache, and has the ability to run without it. Or, we could fail to start up if a cache is configured but cannot be used.

From browser meeting:

We should fail more gracefully when the cache is unavailable
There's a real prod use case of when redis is down, we'd like to be able to return things
Any query that uses withCache() will hang for 30 seconds then almost certainly fail if there's no redis


"classifier" not considered for Nexus artifact upload

When uploading artifacts to nexus only groupID, artifactID and version are considered. As a result, if I try to create 2 .jars (having different classifiers, but same groupID, artifactID, version), they appear to be duplicates since the classifier is not considered.
Best regards
Victor

Thanks for the input.
Do you want to deploy both jars or just one of them. E.g., if there is a standard one without classifier, only this one?

I would like to deploy both. I am trying to integrate Spring-Cloud-Contract, which generates an additional .jar containing wiremock stubs for all services.

Implemented in https://github.com/SAP/cloud-s4-sdk-pipeline-lib/commit/74417eedb7e558aeb4a4f00aa0e4fc885710f47d
You have to adapt the pipeline_config.yml in the following way:
Example
artifactDeployment:
  nexus:
    version: nexus2
    url: nexus.mycorp:8080/nexus
    repository: snapshots
    additionalClassifiers:
      - type: jar
        classifier: classes

The field additionalClassifiers is a list. Each item is an artifact with a classifier which should be deployed.
Type is the packaging type. We expect the artifact to be named as artifactId-classifier.type
Hope that help.
Best regards,
Daniel

Just what we needed, thanks!
Victor


staying on macOS 10.15 due to qt 6.2 compilation issue

Upgrading to macos11 / appleclang 13 reveals a missing header in Qt 6.2.1
This is now fixed in the Qt 6.2 branch:
https://codereview.qt-project.org/c/qt/qtbase/+/379349
So we should be able to use the next release - until then sticking with 6.2.0

Actually it looks like 6.2.0 has the same issue - so the interim solution would be to revert to macOS 10.15 for now, and update to macOS 11 for the next qt release


Document programmatic UI setup

The UI tutorial does not discuss programmatic setup after the page loads.  This is supported, but not clearly documented.
This should be clearly documented for application developers who would prefer to do this for any reason, including:

Video element injected on some event after page load
Building Shaka Player into a UI framework which modifies the DOM
etc

Existing API docs are here: https://shaka-player-demo.appspot.com/docs/api/shaka.ui.Overlay.html

See code snippet here to add to our tutorials: https://github.com/flutter/flutter/issues/66931#issuecomment-701040254