Puppet agent throws random errors

Describe the Bug
For a project, we operate approx. 40 servers of exact same hardware specifications. On most of them, puppet runs stable. But on several others, puppet seems to be instable and throws random errors. We do not have any clue, what the problem could be.
Expected Behavior
Puppet agent should not throw random errors.
Steps to Reproduce
To reproduce, we can just use any simple puppet agent command and execute it multiple times after one another.
e.g. configprint:
root@host ~ # puppet agent --configprint ssldir
Error: Could not initialize global default settings: can't modify frozen File: #<File:/opt/puppetlabs/puppet/lib/ruby/vendor_gems/gems/hocon-1.3.1/lib/hocon/impl/config_node_simple_value.rb>
root@host ~ # puppet agent --configprint ssldir
/etc/puppetlabs/puppet/ssl
root@host ~ # puppet agent --configprint ssldir
/etc/puppetlabs/puppet/ssl
root@host ~ # puppet agent --configprint ssldir
/etc/puppetlabs/puppet/ssl
root@host ~ #
root@host ~ # puppet agent --configprint ssldir
Traceback (most recent call last):
        21: from /opt/puppetlabs/puppet/bin/puppet:4:in `<main>'
        20: from /opt/puppetlabs/puppet/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:83:in `require'
        19: from /opt/puppetlabs/puppet/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:83:in `require'
        18: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:12:in `<top (required)>'
        17: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:12:in `require_relative'
        16: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:335:in `<top (required)>'
        15: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:335:in `require_relative'
        14: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/parser.rb:6:in `<top (required)>'
        13: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/parser.rb:6:in `require_relative'
        12: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/parser/compiler.rb:8:in `<top (required)>'
        11: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/parser/compiler.rb:8:in `require_relative'
        10: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops.rb:1:in `<top (required)>'
         9: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops.rb:120:in `<module:Puppet>'
         8: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/model/ast.rb:4669:in `register_pcore_types'
         7: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/loaders.rb:111:in `static_loader'
         6: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/pcore.rb:65:in `init'
         5: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/types/types.rb:61:in `register_ptypes'
         4: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/types/types.rb:61:in `each'
         3: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/types/types.rb:65:in `block in register_ptypes'
         2: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/types/types.rb:760:in `register_ptype'
         1: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/types/types.rb:53:in `create_ptype'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/pcore.rb:103:in `create_object_type': can't modify frozen Hash: {} (FrozenError)

Example: confdir
root@host ~ # puppet agent --configprint confdir
/etc/puppetlabs/puppet
root@host ~ # puppet agent --configprint confdir
/etc/puppetlabs/puppet
root@host ~ # puppet agent --configprint confdir
Traceback (most recent call last):
        27: from /opt/puppetlabs/puppet/bin/puppet:4:in `<main>'
        26: from /opt/puppetlabs/puppet/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:83:in `require'
        25: from /opt/puppetlabs/puppet/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:83:in `require'
        24: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:12:in `<top (required)>'
        23: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:12:in `require_relative'
        22: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:335:in `<top (required)>'
        21: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:335:in `require_relative'
        20: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/parser.rb:6:in `<top (required)>'
        19: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/parser.rb:6:in `require_relative'
        18: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/parser/compiler.rb:8:in `<top (required)>'
        17: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/parser/compiler.rb:8:in `require_relative'
        16: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops.rb:1:in `<top (required)>'
        15: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops.rb:120:in `<module:Puppet>'
        14: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/model/ast.rb:4669:in `register_pcore_types'
        13: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/loaders.rb:111:in `static_loader'
        12: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/pcore.rb:65:in `init'
        11: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/types/types.rb:68:in `register_ptypes'
        10: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/types/types.rb:68:in `each'
         9: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/types/types.rb:68:in `block in register_ptypes'
         8: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/types/p_meta_type.rb:48:in `resolve'
         7: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/types/p_object_type.rb:738:in `_pcore_init_from_hash'
         6: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/types/p_object_type.rb:738:in `map'
         5: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/types/p_object_type.rb:738:in `each'
         4: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/types/p_object_type.rb:744:in `block in _pcore_init_from_hash'
         3: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/types/p_object_type.rb:744:in `new'
         2: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/types/p_object_type.rb:286:in `initialize'
         1: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/types/type_asserter.rb:33:in `assert_instance_of'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/types/type_asserter.rb:41:in `report_type_mismatch': Puppet::Pops::Types::TypeAssertionError
root@host ~ # puppet agent --configprint confdir
/etc/puppetlabs/puppet

or even only version output:
root@host ~ # puppet agent --version
7.30.0
root@host ~ # puppet agent --version
Traceback (most recent call last):
        11: from /opt/puppetlabs/puppet/bin/puppet:4:in `<main>'
        10: from /opt/puppetlabs/puppet/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:83:in `require'
         9: from /opt/puppetlabs/puppet/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:83:in `require'
         8: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:12:in `<top (required)>'
         7: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:12:in `require_relative'
         6: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:41:in `<top (required)>'
         5: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:129:in `<module:Puppet>'
         4: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/defaults.rb:231:in `initialize_default_settings!'
         3: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/settings.rb:1019:in `define_settings'
         2: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/settings.rb:1019:in `each'
         1: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/settings.rb:1026:in `block in define_settings'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/settings.rb:763:in `newsetting': can't modify frozen Hash: {:default=>"", :desc=>"A command to run before every agent run.  If this command returns a non-zero\\n      return code, the entire Puppet run will fail.", :name=>:prerun_command, :section=>:main} (FrozenError)

Environment

e.g. with Version 7.30.0 and Version 7.23.0
We are seeing this on some servers running on Debian Bookworm and also on some servers running on Debian Bullseye.
uname -a:

Linux host 6.5.13-5-pve #1 SMP PREEMPT_DYNAMIC PMX 6.5.13-5 (2024-04-05T11:03Z) x86_64 GNU/Linux
Linux host 6.5.11-8-pve #1 SMP PREEMPT_DYNAMIC PMX 6.5.11-8 (2024-01-30T12:27Z) x86_64 GNU/Linux

Additional Context
Nothing.

@lordwebbie I can't reproduce this. There's something going on in your environment. If I had to guess you have a mix of ruby and/or puppet versions. You're better off reaching out in community slack to help track down the issue:
root@red-empathy:~# dpkg-query -W puppet-agent
puppet-agent	7.30.0-1bookworm
root@red-empathy:~# facter os
{
  architecture => "amd64",
  distro => {
    codename => "bookworm",
    description => "Debian GNU/Linux 12 (bookworm)",
    id => "Debian",
    release => {
      full => "12.5",
      major => "12",
      minor => "5"
    }
  },
  family => "Debian",
  hardware => "x86_64",
  name => "Debian",
  release => {
    full => "12.5",
    major => "12",
    minor => "5"
  },
  selinux => {
    enabled => false
  }
}
root@red-empathy:~# puppet agent --configprint confdir
/etc/puppetlabs/puppet
root@red-empathy:~# puppet agent --configprint confdir
/etc/puppetlabs/puppet
root@red-empathy:~# puppet agent --configprint confdir
/etc/puppetlabs/puppet
root@red-empathy:~# puppet agent --configprint confdir
/etc/puppetlabs/puppet
root@red-empathy:~# puppet agent --configprint confdir
/etc/puppetlabs/puppet
root@red-empathy:~# puppet agent --configprint confdir
/etc/puppetlabs/puppet
root@red-empathy:~# puppet agent --configprint confdir
/etc/puppetlabs/puppet


Introduce third breakpoint color to indicate "bound in some process"

I don't know whether this was suggested before. Now we show red breakpoints only when the bp is bound in the selected debug process, and gray otherwise. I think it would be really helpful to be able to tell the difference between a breakpoint that isn't bound anywhere, and one that is bound but in a different process from the selected one. Often I want to check that my breakpoints are bound, and have to check the list of debug processes to make sure.
So we would see something like

Red: bound in selected process
Dark red: bound in some process, not the selected
Gray: not bound anywhere

cc @weinand

This proposal makes a lot of sense.
We just have to keep in mind that for accessibility reasons the shape should differentiate the breakpoint state as well.

Dark red feels stronger than red. Shouldn't that decoration be less strong since it is not currently bound?
PR welcome
Code pointer
https://github.com/Microsoft/vscode/blob/469786a7913ef99199d54683e0187c7e8e7e6f89/src/vs/workbench/parts/debug/browser/breakpointsView.ts#L569

By "dark red", I'm imagining something like a cross between gray and red. The "bright red" we have should look stronger and "active". I have no idea how the shape should be differentiated.

@roblourens I closed this issue since now the breakpoints should always properly show their status depending on the active session.
But sure we can keep this open.

But they still are gray when bound, but not in the active session, right? My complaint is that they look the same whether unbound or bound in a different session, and I just want to know that they are bound somewhere.

@roblourens correct, your complaint is valid

I'm going to try and work on this one.

@isidorn would you object to changing property "verified" of class "BaseBreakpoint" into enum with three values: 1. notVerified 2. verified 3. verifiedInanotherSession.

@YisraelV I guess that makes sense if we want this feature request.
However I do not have time to look into this this milestone. If the PR is straight forward and clean please submit it and I can reveiw some time mid December. Thanks

@isidorn ok thanks. Are there any issues that would be more helpful to look into?

@YisraelV this one for example https://github.com/Microsoft/vscode/issues/62851

@weinand I'm working on this right now and saw you suggested the shape should be different. Any ideas as to how?

@isidorn it seems to me that regardless of this issue, the code at getBreakpointMessageAndClassName would benefit from refactoring  as it is a bit messy.
would you consider, when you have the time, a pull request that made the code cleaner?
I'm adding my ideas so you can understand what kind of changes I'm talking about.
A few points that could use tidying up:

The constants "state" and "debugActive" are declared a few lines before they are used, which creates a confusion about their role.
the function "appendMessage" is used only once, and is declared much before it's used, which is also confusing.
the function "appendMessage" checks for a condition that is always true.
when checking for unsupported breakpoint type,  a different coding flow style is used for log point vs conditionals breakpoint, even though the underlying logic is exactly the same.
Through the function there are many conditionals, Including nested ones. This number could possibly be reduced.
the same type of breakpoint gets different css class prefixes based on available css classes. This is confusing. Rather we should give every type unique prefix and add selectors in the css to accommodate all of them.

Good points. I am open for a PR that addresses these issues. I would keep that PR seperate from this feature request. Thanks

tl/dr: could we render breakpoint as resolved if it was resolved in at least one of the sessions?
My worry is that the average user won't be able to appreciate the difference between resolved and resolved in the current session states. For example, a full stack developer will be switching to a Node session and all their browser breakpoints will get rendered as half-resolved. User will be wondering if that means those breakpoints were disabled. As a result, we are putting too much burden on them and confuse them w/o bringing much add value.
I like the clear contract where resolved breakpoint is something that will eventually be hit, while unresolved is something that is not going to be hit. It sends a clear signal to the user. Could we try keeping it this way and render breakpoint as resolved if it was resolved in at least one of the sessions?
In order to cover the edge case with the resolved breakpoint not being hit in a different session where it was not resolved, you could render a list of sessions the breakpoint is resolved in on hover.
Another side-note on the session selection UX: it should be clear what switching the session control does and what it does not. Since it does not control the breakpoint behavior, the rendering of the breakpoint should not be changed upon that change. It is important to build a solid mental model of what sessions do and preferably limit it to the changes to the pause/resume control and debugger console selection selection.

This is a good point. It would be fine with me, as long as there is still a way for me to tell exactly which sessions it's resolved in.

@pavelfeldman good points and this makes sense to me.
However what would happen if a breakpoint is set on Line 9. The debug session says it should be set on line 10 instead. And the user now clicks on another debug session which has the breakpoint as unverified. Should the breakpoint stay on line 10, or should it jump to its original location of line 9?
How about if a third session verified the breakpoint and it says that is should be on line 15 instead. Changing from first to third should clearly make the breakpoint jump to line 15.
I believe we should use the following herustic:
If a session says the breakpoint is unverified that means most of the time that it is not interested in that breakpoint. And switching focus to that sessions should make no UX difference to the user regarding the breakpoint. The breakpoint should only get changed if the focus moves to another session which also resolved the breakpoint.
Regarding the PR: I am not a big fan of the comlex Hover showing all the states since I doubt that many users will benefit from it. I would only add it later if we hear from users that they are confused.
@weinand @roblourens @pavelfeldman @dgozman  let me know what you think. This is just a pragmatic idea.

Isidor, I like your heuristic idea since it means that the general use case won't be affected. There is a minor counter-argument to your proposal:
In your example, as I select the session, breakpoint jumps between the lines 9, 10 and 15. But no matter which session I select, when one of the sessions breaks, it'll break on its own line.  I'm primarily trying to avoid confusions like this for the general case.
How about an even simpler heuristic: if the breakpoint is resolved into a number of different locations in different sessions, you render it in its original location?
I've been dogfooding a full stack multi-session environment and in my use cases, sessions sharing the same files were rare, exotic. Sessions sharing the same files compiled into different targets with different resolved states were non-existent. So I would only be interested in providing a slick experience for the general 95% use case vs barely enabling those interested in differently resolved breakpoints in selected session by less prominent means and UIs.
I also saw your comment on the PR and I wanted to follow up on the following:

A lot of our UI is sort of a slave of the focused session. This goes against this

I believe that if we want to make multi-session a common case, we would need to go against that principle and reduce the amount of UI affected by the selected session to a pre-defined minimum. Selected session does not affect any of the system's the behavior, it only affects selected inputs, namely console and pause/resume controller, for good. If we wanted to stick with the principle you refer to all the way, breakpoints would only be set in a selected session at the first place, but we don't do that and for a good reason. Session will be a new concept to a lot of these users and we should only introduce new UX primitives to improve their experience. In this case, it seems de-emphasizing session's importance to merely be a selector that suggests which process my REPL is for and what I'm about to start / stop sounds sufficient. The simpler the rules of the game are, the easier they would be to accept.
WDYT?

How about an even simpler heuristic: if the breakpoint is resolved into a number of different locations in different sessions, you render it in its original location?

I think that having a breakpoint resolved in different locations for different sessions is probably a rare edge case. Unless it's more common for a different workflow/language that I'm not familiar with? This solution is probably ok. Or, show it in every resolved location.

@pavelfeldman yes, your heuristic simplifies the things even more since now the breakpoints view is not a slave to the focused session in any way.
So I went ahead with our combined proposal. Please try it out in vscode insiders from Monday and let me know how it goes.
Since this was mostly debt / cleaning up work in code I decided to do it right now and drop the PR https://github.com/microsoft/vscode/pull/81068 even though that one was also a fine approach, I believe tackling it fully on the model level is cleaner. This allowed me to also add some test. As for the nice hover, I suggest that we add it later users get confused.
@roblourens even though we are not adding a new color I closed this issue as I would like that you try the new approach and if you still think we need a new color we can reopen this one.
As for the overall UX as slave to the focused session agree that we should try to simplify the rules of the game and that breakpoints no longer depening on this makes thing simpler and better.

@isidorn I like this approach! Played with it and found a small issue. When breakpoint is supported by one session, and not supported by another, we render it differently depending on focused session. Also, rendering in the editor and in the breakpoints list sometimes disagrees (unsupported vs verified). I think that if we move notion of supported to the breakpoint model (similar to verified), this will be automatically fixed.

@dgozman good catch and you are correct about the way to fix this. To track this issue I have created https://github.com/microsoft/vscode/issues/81303 and plan to look into it later today / tomorrow.


neurofibromatosis type 1 MONDO v MONARCH

http://purl.obolibrary.org/obo/MONDO_0018975
neurofibromatosis type 1
http://purl.obolibrary.org/obo/MONDO_0008078
neurofibromatosis, familial spinal
https://monarchinitiative.org/disease/MONDO:0008078
neurofibromatosis, familial spinal MONDO:0008078 (Redirected from MONDO:0018975)
I don't understand why MONDO:0018975 is redirected to the the child term MONDO:0008078 in Monarch, what have they been merged? is this correct/what you would expect to see?

Thank you @lcdaugherty
From a quick look it seems this is not a problem with Mondo, but with Monarch - I have asked the Monarch UI team (@monicacecilia, @kshefchek) to take a look.

Thank you @matentzn - I knew it wasn't a MONDO thing but was confident you could solve it bu knowing the right people! :)

It looks like there are some incorrect equivalences in http://purl.obolibrary.org/obo/mondo/releases/2021-03-03/mondo.owl
http://purl.obolibrary.org/obo/DOID_0111253 is an exact match to MONDO:0018208, and MONDO:0008078, and MONDO:0018975
looks like this has since been fixed so this should be fixed for the next monarch data load

@kshefchek great thank you!

thanks all, I will close this


feat: add eip165 abi

Description
What changes are made in this PR? Is it a feature or a bug fix?
Additional Information

[x] I read the contributing guide
[x] I added documentation related to the changes made.
[x] I added or updated tests related to the changes made.

Your ENS/address: izayl.eth

PR-Codex overview
This PR adds support for EIP-165, an Ethereum Improvement Proposal for standardizing smart contract interfaces.
Detailed summary

Added eip165Abi to src/test/abis.ts
Added eip165HumanReadableAbi to src/test/human-readable.ts
Updated src/test/index.ts to include eip165Abi and eip165HumanReadableAbi in exports
Added a test in src/test/index.test.ts to ensure correct exports

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

Looks good. Could you add a changeset? Also, would you mind changing the name address  to zeroAddress  so that we have the same as viem?


Debugging Electron app from VSCode with using a graphics tablet causes input issues.

Issue Type: Bug
I was told to report this issue here from the Electron github even though this probably has nothing to do with vscode.
When trying to debug my Electron app, my Electron app has input issues with my graphics tablet though only when debugging it. When I build and launch there is no issues with the inputs on my Electron app.
https://github.com/electron/electron/issues/25850
Snippet of launch configuration on the Electron app:
{
        "name": "Debug Main Process",
        "type": "node",
        "request": "launch",
        "cwd": "${workspaceRoot}",
        "runtimeExecutable": "${workspaceRoot}/src/node_modules/.bin/electron",
        "windows": {
          "runtimeExecutable": "${workspaceRoot}/src/node_modules/.bin/electron.cmd"
        },
        "program": "${workspaceRoot}/src/electron.js",
        "protocol": "inspector",
        "outputCapture": "std"
      },
      {
        "name": "Debug Renderer Process",
        "type": "pwa-chrome",
        "request": "launch",
        "sourceMaps": false,
        "runtimeExecutable": "${workspaceRoot}/src/node_modules/.bin/electron",
        "windows": {
          "runtimeExecutable": "${workspaceRoot}/src/node_modules/.bin/electron.cmd"
        },
        "runtimeArgs": [
          "${workspaceRoot}/src/electron.js",
          "--remote-debugging-port=9222"
        ],
        "webRoot": "${workspaceRoot}"
      }

The code having problems on the Electron app:
document.addEventListener('mouseup', function() {
console.log('mouseup')
})

document.addEventListener('mousedown', function() {
console.log('mousedown')
})

Expected results:
I should be able to detect mouse up and mouse down when using a graphics tablet on my Electron app.
Actual results:
Randomly the mouse up and mouse down events are called when trying to use my graphics tablet while debugging the Electron app. Though it works completely on a built Electron app.
VS Code version: Code 1.50.0 (93c2f0fbf16c5a4b10e4d5f89737d9c2c25488a3, 2020-10-07T06:10:52.432Z)
OS version: Windows_NT x64 10.0.19041

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-4460  CPU @ 3.20GHz (4 x 3199)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offopengl: enabled_onprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.94GB (8.24GB free)

Process Argv
--crash-reporter-id 42982bb0-7699-43a6-83a9-a4ec4dcf2308

Screen Reader
no

VM
0%

Extensions (12)

Extension
Author (truncated)
Version

markdown-checkbox
bie
0.1.3

better-toml
bun
0.3.2

vscode-firefox-debug
fir
2.9.1

auto-using
Fud
0.7.15

discord-vscode
icr
4.0.0

vscode-json5
mrm
1.0.0

csharp
ms-
1.23.3

vsliveshare
ms-
1.0.2902

vsliveshare-audio
ms-
0.1.91

vsliveshare-pack
ms-
0.4.0

lua
sum
0.21.2

vscode-todo-highlight
way
1.0.4

(1 theme extensions excluded)

Thanks for the report. Does this happen if you run the electron process directly without going through the debugger? i.e. if you manually run ./src/node_modules/.bin/electron src/electron.js

I manually ran the command into powershell on VSCode and the same issue occurs.

Okay, thanks for the info. I think this is pretty decisive evidence that the issue is not related to VS Code; I'd recommend following back up with the Electron follks with that information.


[CRASH]

Mod version: 1.10.4+ 1.21 (latest as of 08/16/24)
Game version: Fabric 1.21
When shielding a spider attack while webProjectileGoal is true, the game boots me to main menu. It doesn't when it is false.

"Caused by: java.lang.IllegalArgumentException: Can't find id for 'Block{sihywtcamd:messy_cobweb}"
"lost connection: Internal Exception: io.netty.handler.codec.EncoderException: Failed to encode packet 'clientbound/minecraft:block_update'"

log: latest.log

Hello, thanks for the report! Mmh that's weird, I'll try this out. Just a quick thought, maybe it's because you ran the game without the option enabled and didn't restart the game in-between? This setting needs a game restart to be effective, you should get a warning when updating it.

Nah, I restarted for sure. Both times when trying it out when on false and true.

I can't reproduce the issue. Are you on a server? If yes, did you update the config on the server and reboot it?

It shouldn't be an incompatibility issue. Make sure to not update the config during a fight with a spider because if a messy cobweb is spawned and then you restart the game, issues could happen

Well it turns out it has nothing to do with blocking an attack. It just boots me out of the world when a spider hits me with its web.
I ran a world with just the mod alone and didn't get booted out, but did on my normal modded world, so I am thinking it is an incompatibility. I did made sure to restart after config changes.
latest.log

Thank you for the additional information. I have another issue with blocks in parallel, so I'll investigate those asap!

If you have the opportunity to test with less mods to determine what mods can cause your issue, that would be a great help :)

Same.
https://paste.atlauncher.com/view/66511b85-f6b9-41f5-bbc3-2b5ad1a0164d
latest.log

i have a similar issue with this modset:
https://github.com/user-attachments/files/17004873/logs.and.specifications.txt
Im unsure if its an incompatibility, i just wanted to know if this issue has been resolved?

@TinLikesCode I didn't find anything related to the issue or to my mod in your log, but no this is not yet fixed.
@seriousfreezing @ImWhiff You both have the same issue. Thanks to this issue #61, I discovered that your issue is an incompatibility with ModernFix. I don't know yet what exactly causes the issue, but at least now I know where to look. I will keep you tuned

@TinLikesCode I didn't find anything related to the issue or to my mod in your log, but no this is not yet fixed.
@seriousfreezing @ImWhiff You both have the same issue. Thanks to this issue #61, I discovered that your issue is an incompatibility with ModernFix. I don't know yet what exactly causes the issue, but at least now I know where to look. I will keep you tuned

Well thanks anyway, I was able to find a temporary fix by disabling the attack using the config so I don't have a problem, and I'm pretty sure I am using modern fix


Fix typo in layout example code

remove extra closing div tag from the layout example code

You can preview this change here:
Built with commit 628f6db3b311ff9131c4081e5b14fae7f42ce65a
https://deploy-preview-256--govuk-design-system-preview.netlify.com

I believe the build may have failed since external contributors don't have access to secrets, If we run the tests on your behalf they should go green, which I'll do as soon as I can.


Update README.md

The recently added link for System Coupling was to the repo rather than the doc (as all the others were). I changed the URL to that for the doc and moved it to where it belongs in the list alphabetically. I also took this opportunity to insert Ansys in descriptions since most but not all of them had this.

Interesting. We might want to move this as well to https://github.com/pyansys/pyansys @PipKat - could you take care of that. We'll have to include it in the metapackage as well (it's not there yet)


Interests: category_type main and non-board

Hi,
Its not really an issue/bug but i have a question to the interests method. In your Readme there is an explaination about interests:
1. Get a list of main categories. Required bot to be logged in:
$categories = $bot->interests->main();
2. Get category info by name (can be taken from main()):
$info = $bot->interests->info("gifts");
The second one is not clear to me. How do you get the interest "gifts"? The info-method returns that this has category_type of "non-board".
Array
(
    [images] => Array
        (
            [45x] => Array
                (
                    [url] => http://i.pinimg.com/categories/gifts-1384730624-45x.jpg
                    [width] => 45
                    [height] => 45
                )

        )

    [category_type] => non_board
    [type] => category
    [name] => Gifts
    [key] => gifts
)

While the output of "main()" just returns "main" category_types. So, i dont unterstand how you found the interest "gifts" with the usage of "main()" method.
Thank you

Hi, @razza-guhl
Sorry for late response. It looks like Pinterest has changed interests, that were returned as main


Yaml to bytes converter

converter.go reads yaml and fileDescriptorSet, and creates proto bytes from it. It uses reader.go to do the actual crawling over yaml and matching it to proto fields. reader.go walks over the yaml and calls back into converter.go which accumulates all the observed state into a tree and later prints the data on a proto buffer. The walker (inside reader.go) will be used by other components, yet to be implemented, for creating expression evaluator data-structure to be used at runtime.
So far only simple primitives and message type is supported. I am working on adding more types, but will add it as a separate PR. Want to send this out so @mandarjog can use parts of it for runtime evaluator module.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: mandarjog
Assign the PR to them by writing /assign @mandarjog in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

mixer/OWNERS

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

Is there a short description of what this code does? Is this a custom serializer from YAML to proto binary? What extent of YAML spec do we want to cover? I don't see cross-references, for example.

This is meant to be a Yaml => binary form proto converter. It is currently very task specific: read a Yaml description of a particular type of adapter configuration and convert it directly into serialized proto (to be sent over the wire to remote adapters). The intent is to cover our current adapter config needs. It can be extended though.
What is the scenario for Yaml => Proto in Pilot? Does it need conversion to the binary serialized form?

It implements yaml.protomarshal(yamlinput, proto_descriptor) —> bytes
Marhshal yaml as proto without proto codegen.

@costinm this is only interesting if you don’t have static protos. If you have static protos that can be code gen’d that will always be more performant.

@guptasu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
ffcbc67c166fb25a054d5bfd60d57c0d8b9d1f32
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@guptasu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
a8be08aa4f6d6fa1d13505ba1087f5b2bdbacfdf
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/lgtm

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

Needs approval from an approver in each of these files:

OWNERS [mandarjog]

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

/test istio-pilot-e2e

@guptasu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
a8be08aa4f6d6fa1d13505ba1087f5b2bdbacfdf
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@mandarjong do you know any generator to support yaml to static protos ?
Right now Pilot is reading/parsing CRD yaml,
saving the 'spec' part as another yaml, converts the second yaml to json,
and parses the json using the generated gogo proto
using UnmarshalString - which I believe is quite similar with this PR so I
don't see how even that part will be more performant.
On Tue, Apr 10, 2018 at 9:46 AM, mandarjog<EMAIL_ADDRESS>wrote:

@costinm https://github.com/costinm this is only interesting if you
don’t have static protos. If you have static protos that can be code gen’d
that will always be more performant.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/4793#issuecomment-380169959, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAFI6knM2VLborU_Yn5hllfoziEAZ5Axks5tnOHfgaJpZM4TKSPg
.


Protractor unable to start a webdriver session

I have the latest selenoid and selenoid-ui installed with docker. From the UI interface I have green lights for SSE and SELENOID.
I have protractor config using the selenoid server:
seleniumAddress: 'http://<IP_ADDRESS>:4444/wd/hub',
When I run protractor, I get an error that WebDriver from the newly started container didn't respond. From docker I can see the new container started up.
$ protractor e2e/protractor.conf.js
(node:16928) [DEP0022] DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.
[16:47:04] I/launcher - Running 1 instances of WebDriver
[16:47:04] I/hosted - Using the selenium server at http://<IP_ADDRESS>:4444/wd/hub
[16:47:34] E/runner - Unable to start a WebDriver session.
(node:16928) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): WebDriverError: wait: http://<IP_ADDRESS>:4444/ does not respond in 30s
(node:16928) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
[16:47:34] E/launcher - Error: WebDriverError: wait: http://<IP_ADDRESS>:4444/ does not respond in 30s
at Object.checkLegacyResponse (C:\Users\me\repos\wbhtml5\power-designer\node_modules\protractor\node_modules\selenium-webdriver\lib\error.js:546:15)
at parseHttpResponse (C:\Users\me\repos\wbhtml5\power-designer\node_modules\protractor\node_modules\selenium-webdriver\lib\http.js:509:13)
at doSend.then.response (C:\me\me\repos\wbhtml5\power-designer\node_modules\protractor\node_modules\selenium-webdriver\lib\http.js:441:30)
at
at process._tickCallback (internal/process/next_tick.js:188:7)
[16:47:34] E/launcher - Process exited with error code 100
error Command failed with exit code 100.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Anyone able to get protractor to run with selenoid?

@bhoppeadoy sure, a lot of persons are using Protractor with Selenoid. This error can mean that Selenoid container is started in one Docker network and its containers in another network. If you are launching Selenoid manually with --network flag or with Docker compose (which is creating custom network automaticall) - then make sure you are also adding -container-network <network-name> flag to Selenoid command line arguments.

I'm launching selenoid using 'cm selenoid start'. Looking at the network settings they appear to be on the same network.
Here's the network for the selenoid container:
"NetworkSettings": {
"Bridge": "",
"SandboxID": "2b5fe3593b73548e5bece8c214f3c181c60cf612f48b1f9c52dab39c8769c083",
"HairpinMode": false,
"LinkLocalIPv6Address": "",
"LinkLocalIPv6PrefixLen": 0,
"Ports": {
"4444/tcp": [
{
"HostIp": "<IP_ADDRESS>",
"HostPort": "4444"
}
]
},
"SandboxKey": "/var/run/docker/netns/2b5fe3593b73",
"SecondaryIPAddresses": null,
"SecondaryIPv6Addresses": null,
"EndpointID": "97fc2a9ca33ebbdd695fcaf40bf9a42ac88e734335081500586e8501f8b72460",
"Gateway": "<IP_ADDRESS>",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"IPAddress": "<IP_ADDRESS>",
"IPPrefixLen": 24,
"IPv6Gateway": "",
"MacAddress": "02:42:c0:a8:c4:02",
"Networks": {
"bridge": {
"IPAMConfig": null,
"Links": null,
"Aliases": null,
"NetworkID": "e10fdc450766bfbebd1feecbee0818b20eb5b6e76d161a6c3c86fc545f1b9d31",
"EndpointID": "97fc2a9ca33ebbdd695fcaf40bf9a42ac88e734335081500586e8501f8b72460",
"Gateway": "<IP_ADDRESS>",
"IPAddress": "<IP_ADDRESS>",
"IPPrefixLen": 24,
"IPv6Gateway": "",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"MacAddress": "02:42:c0:a8:c4:02"
}
}
}
Here's the network for the started test container:
"NetworkSettings": {
"Bridge": "",
"SandboxID": "27f76a638d1a22ab87e39f9754bcf6290ae93d7751f40fb3005632cf8619694b",
"HairpinMode": false,
"LinkLocalIPv6Address": "",
"LinkLocalIPv6PrefixLen": 0,
"Ports": {
"4444/tcp": null,
"8080/tcp": null
},
"SandboxKey": "/var/run/docker/netns/27f76a638d1a",
"SecondaryIPAddresses": null,
"SecondaryIPv6Addresses": null,
"EndpointID": "8f0aad7f4131b15b5c6391599ce228db065d5f9ccda45ca338652026611397fd",
"Gateway": "<IP_ADDRESS>",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"IPAddress": "<IP_ADDRESS>",
"IPPrefixLen": 24,
"IPv6Gateway": "",
"MacAddress": "02:42:c0:a8:c4:04",
"Networks": {
"bridge": {
"IPAMConfig": null,
"Links": null,
"Aliases": null,
"NetworkID": "e10fdc450766bfbebd1feecbee0818b20eb5b6e76d161a6c3c86fc545f1b9d31",
"EndpointID": "8f0aad7f4131b15b5c6391599ce228db065d5f9ccda45ca338652026611397fd",
"Gateway": "<IP_ADDRESS>",
"IPAddress": "<IP_ADDRESS>",
"IPPrefixLen": 24,
"IPv6Gateway": "",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"MacAddress": "02:42:c0:a8:c4:04"
}
}
}

Also I forgot to mention that my selenoid is on a remote server. I'm running tests from one machine and selenoid on another. Since <IP_ADDRESS> is local network to the selenoid host obviously i can't see that from another machine.
So I guess the real question is how do I run against a remote selenoid server?

@bhoppeadoy should work on any remote server. Couldn't it be a Windows-specific Docker firewall issue? At least on Linux Docker is using a bridge network interface to provide network communication between containers. Here <IP_ADDRESS> is a browser container internal IP address inside this custom Docker network. Take a look at the following troubleshooting guide: https://success.docker.com/article/troubleshooting-container-networking

@bhoppeadoy you could try to start two containers manually and try to telnet port 4444 from one container to another. If it timeouts - then you have issues in Docker.

@vania-pooh looks like the issue is with my bridge network. Running 'docker network inspect bridge' I see this option:
        "com.docker.network.bridge.enable_icc": "false",

This Enables or Disables Inter Container Connectivity. I'm going to try to get this set to true and see if it solves my issue.

@vania-pooh I might not be able to change the above setting, so would I be able to configure selenoid to always pass the '--link selenoid' option to docker run command when it starts a browser container?

@bhoppeadoy no, linking is not supported.

@vania-pooh Just FYI, I was able to configure icc=true and now I'm able to run tests against Selenoid remotely. Thanks for all your help with tracking this issue.

@bhoppeadoy great!


Integrate Dex ROCK in CKF 1.8

Context
We'd like to use the image from canonical/dex-auth-rocks#7 for CKF distributions
What needs to get done

once canonical/dex-auth-rocks#7 is complete, update this charm to use the image from canonical/dex-auth-rocks#7
test that image in the dex-auth charm w/a minimal kubeflow environment using auth

Definition of Done

the updated image included in this repo's gh:main and published to ch:latest/edge

closed by #183

@ca-scribner this issue should not be closed, since the image was not included in the track/2.36 branch
cc @DnPlas who also reviewed


Skip holland backup check for short lived machines

Recently a MaaS check for holland was introduced which checks that
yesterday's backup exists. This makes sense for production but not for
gate runs. In the same PR a mechanism for excluding checks from local
MaaS verification was added, however not all gate runs use local verification
and no mechanism was included for excluding the check from full MaaS API
verification.
This commit attempts to guess the age of a machine by stat-ing
/etc/hostname.  If that file is less than a day old, then the check is
skipped with a successful status returned. This means that gate runs
will pass with no backups, and production deploys will be indicating
backup failures before they are handed over to customers.
Also:

Removes local verification check exclusion mechnaism as its no longer used.
Removes duplicate state keys in holland_preinstall

Connects rcbops/u-suk-dev#950

This is MaaS Related, so needs a gate check with DEPLOY_MAAS=yes :  http://jenkins.propter.net/job/JJB-RPC-AIO_master-swift-periodic/18/

Post lint fix check job: http://jenkins.propter.net/job/JJB-RPC-AIO_master-swift-periodic/19/

@hughsaunders Commit messages must be under 50 characters :/

@alextricity25 I was about to get super mad, but thankfully its only the title 😅

+1

@hughsaunders @alextricity25  I would have welcomed not to back out all of my changes, since there maybe reasons to exclude checks from verification in the future


Update AspectRatio.php

Adds more standard aspect ratio

Looks good to me :+1:
Might have a refactoring on this ^^

It looks good to me too.
@hanserdev Could you update your branch with the latest master?
@romainneutron I think this is mergeable, don't you think?

@Romain Why you don't update it with latest master?

@jens1o, I cannot do it.
I need @hanserdev to update his branch with master first.

Ah, in most cases the owner is able to update the branch with just a click...

Yep...

Oh my god, sorry 👍

Thanks!


Do you have any scripts for visible result?

Hello, I'm very new in this field.
And I want run and show the results by the images of the videos.
MMDetect provides some demos like image_demo.py or webcam_demo.py.
Do you have any scripts or code like this, or how can I get this?
Thank you for your helps.

I think you can directly use image_demo.py to visualize the results.

Thank you for your quick answer.
I tried like this.

python demo/image_demo.py demo/demo3.jpg configs/fcos/fcos_center- ... _dcn0.py work_dirs/fcos_center- ... _dcn0/latest.pth

But, when I tried I got error message belows

Traceback (most recent call last):
File "demo/image_demo.py", line 28, in
main()
File "demo/image_demo.py", line 24, in main
show_result_pyplot(model, args.img, result, score_thr=args.score_thr)
File "/home/hyeri/work/AlignPS/mmdet/apis/inference.py", line 167, in show_result_pyplot
img = model.show_result(img, result, score_thr=score_thr, show=False)
File "/home/hyeri/work/AlignPS/mmdet/models/detectors/base.py", line 341, in show_result
out_file=out_file)
File "/home/hyeri/anaconda3/envs/work-jun/lib/python3.7/site-packages/mmcv/visualization/image.py", line 120, in imshow_det_bboxes
assert bboxes.shape[1] == 4 or bboxes.shape[1] == 5
AssertionError

Am I wrong?
Thank you for your helps.

demo/demo3.jpg configs/fcos/fcos_center- ... _dcn0.py work_dirs/fcos_center- ... _dcn0/latest.pth

Hello, Have you solve the problem? I am encountered the same problem, could you please tell me the solution?

This is because we concatenate the reid features with box results, to solve this. You can simply find the boxes results and replace it with boxes = boxes[:, :5].
Or you can replace this line:
https://github.com/daodaofr/AlignPS/blob/c20cf329b2934a8693e2064435d3e3f65c496095/mmdet/models/detectors/single_stage_reid.py#L123
with:
https://github.com/daodaofr/AlignPS/blob/c20cf329b2934a8693e2064435d3e3f65c496095/mmdet/models/detectors/single_stage.py#L119

Thanks for your solution,
but it is not still worked.
I get the bbox_results is 2D-array but it contains 2D numpy.ndarray.
Also I don't get the meaning of boxes results.
How does it consist of? Cause I cannot find the information like bbox coordinates at the bbox results.

I solve this.
Add "boxes = boxes[:, :5]" below.
https://github.com/daodaofr/AlignPS/blob/98138c959059bc39e793a2a6dd164fba8388f19a/mmdet/models/detectors/base.py#L300
Thank you.


Rework api directory structure and rename Status to ResponseStatus

New structure:

Codecov Report

Merging #63 into develop will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           develop    #63   +/-   ##
======================================
  Coverage      100%   100%
======================================
  Files            7      7
  Lines           38     38
  Branches        10     10
======================================
  Hits            38     38

Continue to review full report at Codecov.

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


[Feature] Support wildcard target

I recently came across this useful tool and since have been replacing Makefiles in many of my projects with Justfiles. However, there is one make feature that I cannot achieve using make:
In projects that use a containerized dev setup, my last Makefile entry used to be
# pass all commands to compose cli
%:
    docker-compose $@

This allowed to execute convenience functions like make up, make down, make build, make ps etc very quickly. When using just, I have to use the following code to achieve the same thing:
# docker-compose
@compose *flags:
    {{ compose }} {{ flags }}

# docker-compose up
@up *flags: _data
    {{ compose }} up {{ flags }}

# docker-compose down
@down *flags:
    {{ compose }} down {{ flags }}

# docker-compose build
@build *flags:
    {{ compose }} build {{ flags }}

# docker-compose ps
@ps *flags:
    {{ compose }} ps {{ flags }}

# docker-compose pull
@pull *flags:
    {{ compose }} pull {{ flags }}

This way I can still use commands like just up -d, just ps but for commands not specified explicitly I will have to execute e.g. just compose config.
Would it be possible to create a default wildcard option in just to achieve something similar to what is possible using make?

This could be done with an attribute making a recipe a fallback recipe, in case no other recipe matches, which would receive the full command line, including the recipe name, as arguments:
[fallback]
foo *args:
  {{ args }}

It probably shouldn't be called [fallback] though, since there's already the fallback setting.

I also thought about something like [default], which will likely also be misleading, the most descriptive attribute name I came across would be something like [catchall] (or [catch_all]). I also thought about something like [wildcard] but I don't think this name is really descriptive.

I'd love to see this too. My use case for just is that I work on different projects which each have standardized around a different package manager (and sometimes change package managers mid-project).
So I've created just files that allow me to type just start or just install and not worry about which package manager exists for a project. However, that means for the standard scripts in package.json, I have to go and re-define every script in my .justfile. Having a fallback script would allow me to do:
[fallback]
run script:
   pnpm run {{script}}

Then I could just type just test or just build and it would automatically use the correct package manager for the project I'm working in.
Also, rather than use a script attribute, the target name could be an asterisk to indicate it was the catch-all definition:
* script:
   pnpm run {{script}}

Since * is currently not allowed as a character for a target name, this wouldn't break any backwards compatibility.


The ssh password is reset to default after upgrading from 0.3.8 to 0.3.9

I used to be able to SSH into the box using the same password as the web dashboard.
I needed to SSH into the box after flashing 0.3.9 when I realized that 0.3.9 did not resolve this other issue.
But I cannot login over SSH using the web dashboard password anymore. I had to use the default password.
How does that make any sense? There is no note about this in (non-existing) release notes.

We did not reset the password, also release notes exist here on GitHub. A reflash however resets the password until you login into the dashboard, this has nothing to do with the update.

I can't login to the dashboard because of issue #613.
So this behaviour still makes no sense to me.

It is impossible to do this securely, because then we would have to store your password in plain text on the SSD, which is very insecure, and it would also make SSH access impossible if you lost your password, with this, you can access it by reflashing.

I can't login to the dashboard because of issue #613.
WHAT DO I DO?

WHAT DO I DO?

STOP SCREAMING!
But you should join us on Telegram to get help.

Not moving the discussion to Telegram, because any tribal knowledge uncovered there will scroll out of sight. And chats are not encrypted, and there is too much noise, with people having to get banned constantly for peddlng shitcoin scams.
I would go to Telegram, then you'd help me, and then anyone with the same problem in one week or one month has to ask again, and uncover the tribal knowledge again.
This issue should at the very least explain what the user is to do when :

login to the web interface is not possible
reflashing means the default password is now in use

Am I supposed to

login using the default password
change the SSH password to the same as the dashboard

Would that be sufficient to reestablish the same configuration that existed when I had 0.3.8?
Or are there other aspects to consider?
This is what I meant with WHAT DO I DO? I was simulating the non tech user who's going to come to you with zero clue.
I'm a tech user so I'll figure it out, but please please please, see this question from the angle of one of the thousands of non tech users that will use umbrel and encounter the same problem.

The first step is fixing the web interface, then everything else is done automatically. Please run sudo ~/umbrel/scripts/debug --upload and send me the link it generates.

Please do a manual update to 0.3.9 as described on info.umbrel.tech.

There's a bug I just found in 0.3.9 which means a manual update is required, but we're working on it.

For the #613 issue, I posted the debug upload to #613, where it belongs.
This issue is about whether, after reflashing (and therefore the password being reset), changing the SSH password from default to  manually is the same as logging in successfully to the dashboard.
I will check the info.umbrel.tech page you're referring to (https://info.umbrel.tech/troubleshooting.html#manually-updating-umbrel) and another one Luke pointed me to (https://github.com/getumbrel/umbrel/blob/master/SECURITY.md) to try to figure that out on my own.

There's a bug I just found in 0.3.9 which means a manual update is required, but we're working on it.

If you have an issue number, I'm interested.

It's not a GitHub issue yet.

This issue is about whether, after reflashing (and therefore the password being reset), changing the SSH password from default to the same as Web dashboard manually is the same as logging in successfully to the dashboard.

Yes, it is

This is what I meant with WHAT DO I DO? I was simulating the non tech user who's going to come to you with zero clue.

I understand your frustration @lestephane.
Just to clarify how this works, it's only very brief. Once you re-flash the SD card, the password is reset because it can't possibly know your password. When you next login to the dashboard, which would likely be very soon after re-flashing, if there is a successful login, your system/SSH password will be updated to use that password. So Umbrel is (almost) instantly updated to use your supplied password again after a re-flash, most users would never experience the password reset.
I understand you can't complete the login process due to the LND loading screen, however the latest release has resolved that issue. The login process is no longer dependent on LND being available, so there should not be a scenario where a user re-flashes but is unable to login.

I realized that 0.3.9 did not resolve this other issue.

Are you saying you're on 0.3.9 but you're still seeing the "Loading LND..." text? That shouldn't be the case, that could is completely removed. Can you try to refresh the browser?

There is no note about this in (non-existing) release notes.

For release notes check the Umbrel releases: https://github.com/getumbrel/umbrel/releases/tag/v0.3.9
We have a strict policy of one change = one PR = one merged commit. So git log is our release notes. You can see a descriptive overview of the changes between each release by comparing the two tags, and follow the PR links for more detailed information on each change: https://github.com/getumbrel/umbrel/compare/v0.3.8...v0.3.9

Are you saying you're on 0.3.9 but you're still seeing the "Loading LND..." text? That shouldn't be the case, that could is completely removed. Can you try to refresh the browser?

This is the bug I told you about a few minutes ago, where a reflash doesn't update.

Ah, of course!
Ok, looking into that on priority now.

@lestephane this should work, are you able to try re-flashing your SD card with this build: https://github.com/getumbrel/umbrel-os/releases/tag/v0.3.9-patch-2

Are you saying you're on 0.3.9 but you're still seeing the "Loading LND..." text?

I do, at the Safest security setting. Safer security setting goes through.
The error at the safest security setting is below (HAR is attached)
Which brings up an interesting point: If I've doxed my onion service, how do I get Umbrel to generate a new onion service name? Is that something that is currently possible?  It seems kind of obvious in retrospect. But it did not occur to me to buy a couple. I only have one.
In any case, I will re-flash using my one card and report.

I reflashed, and it works at *safer *security settings, still unable to get
in at safest setting.
That's despite granting the onion service temp permissions in NoScript.
[image: image.png]
On Sat, Apr 24, 2021 at 10:28 PM Luke Childs @.***>
wrote:

@lestephane https://github.com/lestephane this should work, are you
able to try re-flashing your SD card with this build:
https://github.com/getumbrel/umbrel-os/releases/tag/v0.3.9-patch-2
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/getumbrel/umbrel-os/issues/212#issuecomment-826142020,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABJVHFHPW4JE5NMDWEUCW4LTKMLWBANCNFSM43P2OWTA
.

--

Which brings up an interesting point: If I've doxed my onion service, how do I get Umbrel to generate a new onion service name? Is that something that is currently possible? Manual steps also OK.

cd ~/umbrel && rm -rf tor/data/web && docker-compose restart tor && sleep 1 && sudo reboot

I reflashed, and it works at *safer *security settings, still unable to get in at safest setting.

Glad it's working for you now! There's really not much reason to use the strict settings in Tor Browser when accessing Umbrel. That setting is to preserve your privacy when accessing untrusted 3rd party websites by limiting browser features. It's an increase in privacy at the cost if usability. Umbrel is your own trusted server, not a third party, so you don't really need privacy from yourself. It's assumed that JavaScript and all browser APIs are fully operational in the Umbrel UI. Tor is providing secure remote access in this use case, not anonymity.

This should do the trick:

Thanks!

The recommended steps for people experiencing the problem on 0.3.9 is to flash 0.3.9-patch2 as Luke describes. closing.


test(react): add test code for the Wrap class

Overview

add test code for the Wrap class

before

after

PR Checklist

[x] I did below actions if need

I read the Contributing Guide
I added documents and tests.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 77.60%. Comparing base (7714f92) to head (73971f5).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1156      +/-   ##
==========================================
+ Coverage   76.26%   77.60%   +1.34%
==========================================
  Files          62       62
  Lines         594      594
  Branches      116      117       +1
==========================================
+ Hits          453      461       +8
+ Misses        131      123       -8
  Partials       10       10

Components
Coverage Δ

@suspensive/utils
47.16% <ø> (ø)

@suspensive/react
100.00% <ø> (+4.25%)
:arrow_up:

@suspensive/react-query
72.18% <ø> (ø)

@suspensive/react-query-4
0.00% <ø> (ø)

@suspensive/react-query-5
0.00% <ø> (ø)

@suspensive/jotai
0.00% <ø> (ø)

@suspensive/cache
98.23% <ø> (ø)

@suspensive/react-image
80.39% <ø> (ø)


fix: override default CXX value

fix #924

Thank you for working on this! But, I wouldn't think this is an ideal fix as clang++ is picked instead of c++ on macOS (https://github.com/poac-dev/poac/actions/runs/9906840850/job/27388403453?pr=942#step:7:79).
There is no compelling reason to use Clang by default, so maybe just removing the CXX ?= clang++ line from the generated Makefile works? This makes things clearer.

There is no compelling reason to use Clang by default, so maybe just removing the CXX ?= clang++ line from the generated Makefile works? I guess this makes things clearer.

Yes, I think so too. Just removing the line is easy, but BuildConfig.cc already depends on the predefined CXX value in other areas, and I am concerned about losing consistency.
https://github.com/poac-dev/poac/blob/0.9.3/src/BuildConfig.cc#L36
https://github.com/poac-dev/poac/blob/0.9.3/src/BuildConfig.cc#L319
https://github.com/poac-dev/poac/blob/0.9.3/src/BuildConfig.cc#L415
And Runtime Requirements on README.md does not list B. So does this mean that relying on clang++ as CXX is not the original intent? If so, it seems like a lot of work to fix it properly.
https://github.com/poac-dev/poac/blob/0.9.3/README.md?plain=1#L126-L135

This clang++ is for dependency analysis within the Poac scope. I did a bit of research on this problem, and the best way to share the behavior between Poac and Make seems to use --print-data-base. Since we want to minimize runtime dependencies, you may want to implement a function to extract CXX from the output. You can use getCmdOutput in Algos.hpp to make the shell command output into std::string.
$ make --print-data-base 2>&1 | grep 'CXX ='
CXX = c++
$ export CXX=g++
$ make --print-data-base 2>&1 | grep 'CXX ='
CXX = g++

Do you think this is doable? Please let me know if you find any drawbacks of this way.


Fix trademark language on website

per @markt-asf:
mt: Website looks good. One minor nit with the footer "s/are the trademarks of/are trademarks of/"

addressed in #121


brew install taplo fails certificate verification

brew reinstall taplo
==> Fetching taplo
==> Downloading https://ghcr.io/v2/homebrew/core/taplo/manifests/0.8.0
Already downloaded: /Users/alnoki/Library/Caches/Homebrew/downloads/92db36df43f8344f3e3777365222ca4ef49a4630bb0c8b81059b5df793c80b6c--taplo-0.8.0.bottle_manifest.json
==> Downloading https://ghcr.io/v2/homebrew/core/taplo/blobs/sha256:5647a9506b7ef922984d37cf9a49c4c66f62ac924726e3e81b2b556689ce66fe
==> Downloading from https://pkg-containers.githubusercontent.com/ghcr1/blobs/sha256:5647a9506b7ef922984d37cf9a49c4c66f62ac924726e3e81b2b556689ce66fe?se=2023-03-24T21%3A05%3A00Z&sig=5p1zBpGf%2BHUvZAiBYcptLt%2FGFQ1o1UFaUP9uCD0CKh4%3D&sp=r&spr=https&sr=b&sv=2019-12-12
curl: (60) SSL: no alternative certificate subject name matches target host name 'pkg-containers.githubusercontent.com'
More details here: https://curl.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

Error: Failed to download resource "taplo"
Download failed: https://ghcr.io/v2/homebrew/core/taplo/blobs/sha256:5647a9506b7ef922984d37cf9a49c4c66f62ac924726e3e81b2b556689ce66fe

No longer fails as of 2023-03-27


Work Pool Queue creation headers are noisy

Right now when you go to create a work pool queue, most fields are optional; providing "(Optional)" on each field seems excessive and redundant - ideally there is some visual cue we can use instead to signify the difference between required and optional fields (maybe a red asterisk?).

@cicdw we had this discussion as long as we had forms. We tried asterisks but decided against them. We had this discussion a while back, and I don't remember all the detail. @brigidgliwa, @znicholasbrown, @pleek91, @zhen0, @stackoverfloweth should we rehash our take on (Optional)? Why did we decide to keep it instead of using an asterisk?

The redundancy is hard to avoid. Some forms have no required fields, some forms have all required fields. So either way some forms are going to have every field marked as required or optional.
If I remember correctly the decision to use "(Optional)" had a few reasons.

Using a red asterisk was noisy visually. Made fields stand out a lot because of the color distinction.
At the time most of our forms had mostly required fields. So identifying the optional fields was less intrusive.
We ultimately decided consistency of any pattern was better than no pattern at all.

This decision was not unanimous and there were lots of different opinions and ideas. But no one felt super strongly that I can remember. I think this is something we could revisit and improve but remaining consistent application wide is more important than making an individual form less redundant or more visually appealing.

+1 to everything Craig said. I originally wanted to use the red asterisk because I was working on the work queues form at the time and saw that the majority of those were optional, but after going through the rest of the forms in the UI there were more required fields than optional ones in most forms.

Another options is asterisks but not red?

A happy middle ground here would be to find a less-noisy indicator (whether for optional or required, I agree with all the above comments wrt consistency being extremely important). @brandonreid's screenshot there is a good example of this and is pretty common across other applications. If we can find a similar heuristic for optional, we could use that as a drop-in replacement for (Optional) text in every form, which I agree is noisy

I'm adding this to the UI Backlog project as we'll want to make sure this change is consistent across the UI. I see as low priority vs other work but open to push back.
This ticket will require going through all forms to check which fields are required.  Whoever takes it on should give some thought to see if we can make a future change more easily. (That may not be possible).

Agreed that the black asterisk would be a good way forward.

Yea, agreed on all counts that this isn't an immediate priority, and that @brandonreid 's proposal looks really clean to me.


[fastrtps]

Is your feature request related to a problem? Please describe.
1、First I made sure vcpkg executed git pull and update.
2、Installation screenshot:

3、Cmake project reference method:
find_package(fastcdr REQUIRED)
find_package(fastrtps REQUIRED)
target_link_libraries(${PROJECT_NAME} fastcdr)
target_link_libraries(${PROJECT_NAME} fastrtps)
4、run:
debug model crash

release model normal
Proposed solution
Use the .cmake included in the windows platform binary installation package provided by fastdds to introduce it into the project. Any mode is normal.
So I suggest checking the references of vcpkg to the Fastdds library in debug and release modes. Compare the cmake scripts to check if there are any problems with the introduction in debug mode.
Describe alternatives you've considered
If I directly introduce the .cmake configuration file list in the fatsdds official binary installation package in the cmake project (APPEND CMAKE_PREFIX_PATH "${CMAKE_CURRENT_SOURCE_DIR}/../3rd/fastdds/cmake"), it is easy to use in this case. vcpkg should compare the difference with the official .cmake direct introduction to determine whether there is a reference error problem.

The above picture is the cmake configuration file in the official binary installation package
Additional context
No response

What's the result when you use below commands?
find_package(fastrtps CONFIG REQUIRED)
target_link_libraries(main PRIVATE fastdds::optionparser)

find_package(fastcdr CONFIG REQUIRED)
find_package(fastrtps CONFIG REQUIRED)
target_link_libraries(${PROJECT_NAME} PRIVATE fastcdr)
target_link_libraries(${PROJECT_NAME} PRIVATE fastdds::optionparser)
result:

Why transfer static libraries?

Why transfer static libraries?

There is a fastrtpsd-2.14.lib "import lib" for dynamic library linkage. i.e. not a static lib, and no lib prefix.

@dg0yt I used the cmake style find_package and controlled the parameters -Dfastrtps_SHARED_LIBS=ON -Dfastcdr_SHARED_LIBS=ON to reference the dynamic library, but an error was reported saying that libfastrtpsd-2.14.lib could not be found.

If I first introduce the cmake folder path in the official FASTDDS binary installation package, and then uninstall the fastdds installed by vcpkg, everything will be normal after compilation.

-Dfastrtps_SHARED_LIBS=ON -Dfastcdr_SHARED_LIBS=ON will probably not interact as expected with vcpkg:
The linkage offered by fastrtps in vcpkg is controlled only by the vcpkg triplet and port. x64-windows normally means shared library linkage.
Anyways you must check where the unexpected lib prefix in libfastrtpsd-2.14.lib comes from.
First try a clean build with vpckg, i.e. without any CMake cache.
(Does the "official FASTDDS binary installation" provide binaries with lib prefix?)

yes,provide binaries with prefix

What you said makes sense. Maybe the parameters -Dfastrtps_SHARED_LIBS=ON -Dfastcdr_SHARED_LIBS=ON are not effective in vcpkg. Next, I will try to delete any cmake cache before using vcpkg.

-Dfastrtps_SHARED_LIBS=ON -Dfastcdr_SHARED_LIBS=ON How should vcpkg be used to make this parameter effective?

-Dfastrtps_SHARED_LIBS=ON -Dfastcdr_SHARED_LIBS=ON How should vcpkg be used to make this parameter effective?

Basically, if these options don't match the vcpkg triplet, the cmake package must return an error.

I tried againafter clearing the cache  and
find_package (fastcdr required)
find_package (requires fastrtps)
target_link_libraries (${PROJECT_NAME} fastcdr)
target_link_libraries(${PROJECT_NAME} fastrtps)
can be compiled normally using this method, but the debug mode crashes and the release mode is normal;
If add this sentence
list(APPEND CMAKE_PREFIX_PATH "${CMAKE_CURRENT_SOURCE_DIR}/../3rd/fastdds/cmake")
to refer to the cmake folder of the official binary installation package, and other statements remain unchanged, any mode can run normally.

find_package(fastcdr CONFIG REQUIRED)
find_package(fastrtps CONFIG REQUIRED)
target_link_libraries(${PROJECT_NAME} PRIVATE fastcdr)
target_link_libraries(${PROJECT_NAME} PRIVATE fastdds::optionparser)       error: not open libfastrtpsd-2.14.lib

What I understand:

After a clean build with vcpkg deps only, debug mode crashes.

I tried again after clearing the cache and
find_package (fastcdr required)
find_package (requires fastrtps)
target_link_libraries (${PROJECT_NAME} fastcdr)
target_link_libraries(${PROJECT_NAME} fastrtps)
can be compiled normally using this method, but the debug mode crashes and the release mode is normal;

After changing variables that modify find_xxx behavior to search the official distribution, code runs normally.

If add this sentence
list(APPEND CMAKE_PREFIX_PATH "${CMAKE_CURRENT_SOURCE_DIR}/../3rd/fastdds/cmake")
to refer to the cmake folder of the official binary installation package, and other statements remain unchanged, any mode can run normally.

fastdds::optionparser introduces a link reference to a missing libfastrtpsd-2.14.lib.

find_package(fastcdr CONFIG REQUIRED)
find_package(fastrtps CONFIG REQUIRED)
target_link_libraries(${PROJECT_NAME} PRIVATE fastcdr)
target_link_libraries(${PROJECT_NAME} PRIVATE fastdds::optionparser)
error: not open libfastrtpsd-2.14.lib

These might be three different sub-issues. Needs more analyzes.

Yes, I think as long as the debug mode of question 1 can run normally, it meets my needs
Question 2 is an auxiliary solution to problem 1 in terms of thinking
Question 3 is a different way of referencing question 1

Yes, I think as long as the debug mode of question 1 can run normally, it meets my needs
Question 2 is an auxiliary solution to problem 1 in terms of thinking
Question 3 is a different way of referencing question 1


Per-method resiliency policies for app invocations

In what area(s)?

/area runtime
/area operator

/area placement

/area docs

/area test-and-release

Describe the feature
While looking into Resiliency policies targeting apps, we noticed that it's not currently possible to have different policies per invoked method. Although in a strictly designed micro-service architecture, resiliency policies should behave the same for all possible methods, the reality is a bit different. We may have services in production that expose an endpoint for which a 1s timeout is too long and another one for which 5s is normal. Not saying this is ideal but it's just how it is.
We currently deal with those intricacies on the client side and would like to remove that logic from the application, if possible. In order for that to happen, Dapr would need to support per-endpoint/method policies, e.g.:
specs:
  targets:
    apps:
      appB: # app-id of the target service
        methods:
          methodX:
            timeout: general
            retry: general
            circuitBreaker: general

Considering the early alpha stage of the Resiliency CRD, I believe the breaking changes would be justifiable and the implementation effort should be relatively low.
Release Note

RELEASE NOTE: ADD  per-method Resiliency policies for Dapr applications

I agree to add per-method resiliency. The exact schema would need a formal proposal.

A potential structure that we can consider for per method resiliency is this:
specs:
  targets:
    apps:
      appB: # app-id of the target service
        target_methods: # for specific methods that the app targets --- appB calls methodX or methodY or methodZ?
          - name: methodX
            appId: "dapr-appId"
            baseURL: "" # external service invocation
            path: ["/path/to/methodY"]
            protocol: HTTP
            httpVerb: ["PUT", "POST"]
            timeout: general
            retry: general
            circuitBreaker: general
          - name: methodY
            appId: "dapr-appId"
            path: ["/path/to/methodY"]
            protocol: HTTP
            httpVerb: ["PUT", "POST"]
            timeout: general
            retry: general
            circuitBreaker: general
          - name: methodZ # gRPC method name
            appId: "dapr-appId"
            protocol: gRPC
            timeout: general
            retry: general
            circuitBreaker: general
        # for all other outbound service invocation calls that are not present in "target_methods" block.
        timeout: general
        retry: general
        circuitBreaker: general

The main addition is:
target_methods:
  name: methodX ## gRPC method name or unique identifier for HTTP
  appId: "dapr-app-id" ## no external service invocation
  baseURL: "" # external service invocation
  path: ["/path/to/methodY"]
  protocol: HTTP/gRPC
  httpVerb: ["PUT", "POST"]
  timeout: general
  retry: general
  circuitBreaker: general


[Bug] Config. Worksheet (8632, List) Action MoveUp / MoveDown don't works as expected

Page Config Worksheet (8632, List)
Version: mcr.microsoft.com/businesscentral/onprem:15.1.37793.0-de
Expectation
I add somewhere in the structure a new line and move them up or down to the prefered place.
Behavoir
After saving the new line, the line jumps to the first line. I can only move to first or last line with MoveDown and MoveUp. I can't move the line to every position in the list.

Submitted through Microsoft Collaborate.


docs(plugins): Update list of currently known eleventy plugins on npm.

Signed-off-by: André Jaenisch<EMAIL_ADDRESS>Originally filled as https://github.com/11ty/eleventy/pull/555

Thank you!


Update _loadbalancer.py

below command does not work as expected.
the reason is outbound_ports 0 is considered False. I added isinstance and none checking process.
Related command
$ az aks update -g rgname -n clustername --load-balancer-outbound-ports 0 --debug
Description
If outbound_ports 0, it is considered False.
Even if outbound_ports is not None.
there need the checking logic for outbound_ports whether None or 0.
Given outbound_ports 0, the update process should work due to it is not None
Testing Guide
$ az aks update -g rgname -n clustername --load-balancer-outbound-ports 0 --debug
$ az aks show -g rgname -n clustername -o yaml | grep allocate
allocatedOutboundPorts: 0
History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Thank you for your contribution! We will review the pull request and get back to you soon.

There is another PR which is same.
https://github.com/Azure/azure-cli/pull/28273
So i want to drop it.


Alexa for Android: CANNOT LINK EXECUTABLE "/data/app/avs/bin/SampleApp": cannot locate symbol "EVP_CIPHER_CTX_init" referenced by "/system/lib/libdrmmtkutil.so"...

IMPORTANT: Before you create an issue, please take a look at our Issue Reporting Guide.
Briefly summarize your issue:

We have deployed the alexa to MTK android develop board, but we encount CANNOT LINK EXECUTABLE "/data/app/avs/bin/SampleApp": cannot locate symbol "EVP_CIPHER_CTX_init" referenced by "/system/lib/libdrmmtkutil.so"...
What is the expected behavior?

Alexa starts with no error
What behavior are you observing?

CANNOT LINK EXECUTABLE "/data/app/avs/bin/SampleApp": cannot locate symbol "EVP_CIPHER_CTX_init" referenced by "/system/lib/libdrmmtkutil.so"...
Provide the steps to reproduce the issue, if applicable:

build alexa base on the instruction. and run it using startsample.sh
Tell us about your environment:

What version of the AVS Device SDK are you using?
   1.22.0

Tell us what hardware you're using:

[ ] Desktop / Laptop
[ ] Raspberry Pi
[√ ] Other - tell us more: MTK developping board

Tell us about your OS (Type & version):

[√ ] Linux
[ ] MacOS
[ ] Raspbian Stretch
[ ] Raspbian Jessy
[ ] Other - tell us more:

Hi @xiaqinzhan,
Can you provide the CMake flags you are building with?

Can you also provide the Android version?

I am closing this issue due to inactivity.  If you have further questions, please open a new ticket and refer to this closed one.


[SPARK-20997][CORE]'--driver-cores'  standalone or Mesos or YARN in Cluster deploy mode only.

What changes were proposed in this pull request?
'--driver-cores'  standalone or Mesos or YARN in Cluster deploy mode only.So  The description of spark-submit about it is not very accurate.
How was this patch tested?
manual tests
Please review http://spark.apache.org/contributing.html before opening a pull request.

Can one of the admins verify this patch?

Test build #3787 has started for PR 18241 at commit be9f4f0.

Test build #3787 has finished for PR 18241 at commit be9f4f0.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged to master


New jupyterlab-dataops image

I vote to not keep the extensions binaries in our repo and instead download them from the source: https://github.com/innoverio/vscode-dbt-power-user/releases

installing extensions from the source would be quite an overhead because it requries compilation, instead extensions are downloaded straight from vs marketplace repo

I vote to not keep the extensions binaries in our repo and instead download them from the source: https://github.com/innoverio/vscode-dbt-power-user/releases

installing extensions from the source would be quite an overhead because it requries compilation, instead extensions are downloaded straight from vs marketplace repo

Ah, got it.


Add navbar component

can i work on this issue?

I want to work on this

pls assign this issue to me @imabhinavagarwal

Sorry @sumit-022 @Abhishekvermaa  but I cannot re-assign until @flow6979  decides to drop it

Sorry @sumit-022 @Abhishekvermaa but I cannot re-assign until @flow6979 decides to drop it

i'll do it sirrr


Support React 0.14

This adds support for the new ReactDOM

this is massively backward compat. breaking, and will have to be a new major version rather than a patch update

Is there something I can do to help getting this merged?
@martijnrusschen you should not update the version number in a PR. This should be done by the maintainer of this repo when he prepares a release.
@Pomax You could add this scripts to make publishing easier:

Version number has been reverted. Not sure if this actually fixes all the issues now. @stoeffel Are you able to confirm this is the correct solution?

Tried it with your branch in our app and it worked. Thx.
But I think this repo could use some tests to ensure it works after a change.

@stoeffel I actually greatly prefer having a PR that comes with the updated version if it's going to break everything, which is why I asked @martijnrusschen to change it. npm is just a convenience tool, and in this case I want that major version bump before the PR is merged in. I don't want this code to land as a plain commit, it needs to be explicit about the fact that this is where things broke 0.12 and 0.13 =)
@martijnrusschen can you please put that version back in?

I actually greatly prefer having a PR that comes with the updated version if it's going to break everything

Your choice.

Done

ah, but of course, because it's a package.json change, and I had to put in a reversion, package.json needs a sync up. Can you rebase on the latest master? (probably worth picking the first and just squashing the subsequent commits so it's a single commit PR again)

Should be able to merge it now

yep, looks clean. Is it possible to squash into one commit? (if not, it should still be easy to roll back if absolutely necessary, a single commit's easier to track though)

Great timing @martijnrusschen, I just picked up a project to migrate to React 0.14 and was about to patch this very useful library myself. Thanks for doing it :+1:

Not sure how this should be squased into 1 commit. Steps I need to follow?

@martijnrusschen see http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html

@stoeffel's link is pretty spot on, although there is one small warning and that's the fact that this will probably open up vi or vim, in which "editing" and "save and quit" are about as unintuitive as possible:

to edit text, you type "i", which switches the input mode so that you can type actual text. you can hit "esc" to get back to the main input mode.
to save a file and quit after editing, you type ":wq", where ":" pops up vi/vim's command prompt, "w" means "write this back to file", and "q" means quit.

So if you get stuck on this, let me know and I can fork your PR, do the squashing for us, and then merge that in

I tried squasing the commits, but didn't get it right. Will try it again tomorrow, or you can do it if you're in a hurry.

@Pomax would be great if this gets merged soon. You could use https://github.com/tj/git-extras/blob/master/Commands.md#git-pr and squash and merge. No need to fork this PR.

Hmm, oddly, that command seems to no longer exist on the page you're linking to.

that will check out the pr (which is easy to do with the usual fetch + checkout), but will not let me squash it and the push it up as a PR that gets tracked through github. I'd be squashing, merging, and pushing to master through git, which prevents some handy github.com functions like one click reverts being available.

I rebased and created a new pr. Would be great if it got merged now.

v4.0.1 on https://www.npmjs.com/package/react-onclickoutside


Travis linter

This PR solves #30. Inside this PR is the following:

flake8 config which excludes a lint check on several files/directories

.travis.yml that is a configuration for Travis CI. Currently the yml installs the dependencies as per requirements.txt as well as flake 8, and runs the lint check which will fail if some code does not meet pep8

~This PR is a Work In Progress I am going to add a batch file so the lint script can be run easily on a Windows machine.~ This is no longer WIP. The batch script has been made into a separate issue #37 which should be a different PR.
Other work related to this PR was the integration of Travis CI with this project and some changes made to how PR's will be done. PR's will not be allowed to merge with master if the Travis build fails, that and 1 review is required. The protection based on Travis CI cannot be activated until this PR is merged otherwise all existing PR's would not be able to merge

Thanks for the PR, I'll review this shortly and get it merged once you feel like it's good to go.  Just let me know if you think it's completely done (based on the WIP label)

@jbonzo I think this is ready to be merged, if you can just quickly resolve the couple of conflicts from earlier PRs.

Should be good now


Add "Release Notes" section to About page

@nicholaspad help me pass these black tests?

@nicholaspad help me pass these black tests?

pushed a commit with black applied and the tests now pass. can you pull the commit, and then run
black -l 88 --check .

in the base directory? if it's working, you should see this output:
All done! ✨ 🍰 ✨
20 files would be left unchanged.

if this works, i think the problem was that the line length being used by your black isn't set to the default 88 characters.


Is the execution time invariant to number of objects where each object is of different class?

Thank you for your amazing work!
My question is whether the execution time stays invariant to the number of objects in the image if the objects are of different classes.
e.g. let's say I have two images. The first one has 5 and the second one has 10 objects. Each object in both images is of a different class. Will the execution time increase linearly? If it changes, what is an estimate of the change?
Also, the same question if the objects are of the same class.
Thanks.

Hi, yes the time increase linearly. For each object, the model will process the color embedding with the CNN encoder-decoder and the geometry embedding with the MLPs. In your example, the second one with 10 objects will cost double the time of the first one. The class of the object won't affect the inference speed.

Thank you.


Handle bad dates in DATE-REG for Delaware

What's in this PR?
Fixes a bug in the Delaware transformer introduced in https://github.com/national-voter-file/national-voter-file/pull/158. The issues is that some of the values in the DATE-REG column in an example voter file had invalid dates, notably: 19891200 (there is no 0th of the month).
In those cases, rescue from these errors and return None.
Manual Testing
Manually tested this by running the transformer with the command:
 PYTHONPATH=. python3.4 national_voter_file/transformers/csv_transformer.py -s de -o ../../data/Delaware -d ~/de-head.csv

Should we force to None or try to coerce it into a close-enough date?
I suppose the question is whether the dates look like junk, or are they possibly close to reality. Maybe some counties only capture month and year and they force the date to 00

I suppose the question is whether the dates look like junk, or are they possibly close to reality. Maybe some counties only capture month and year and they force the date to 00

Good point--I can inspect a little bit more to see if 00 is a special case, and if so I'll try parsing w/ "%Y%m"

@BenGalewsky updated!


update azd schema with build args

The buildArgs field is not an alpha feature and it is mentioned on changelog.
However, it is only available from the alpha schema.
This PR is updating the 1.0 schema with to support this fieldy

/check-enforcer override


fill closes subpaths

Addresses https://github.com/treeform/pixie/issues/222

The fill operation fills open subpaths by performing the fill operation as if an additional "closepath" command were added to the path to connect the last point of the subpath with the first point of the subpath. Thus, fill operations apply to both open subpaths within ‘path’ elements (i.e., subpaths without a closepath command) and ‘polyline’ elements.

https://svgwg.org/svg2-draft/painting.html
Fixes a few emoji and icons too which is great.

That was fast. Thank you!


I encountered error (exit code 2) during deployment

5:58:58 PM: Building site...
5:58:58 PM: Failed to build the site
5:58:58 PM: Error: Error when parsing front matter of section /opt/build/repo/__site/build/content/docs/inbox/_index.md
5:58:58 PM: Reason: YAML deserialize error: Scan(ScanError { mark: Marker { index: 91, line: 7, col: 13 }, info: "unexpected character: `@'" })
5:58:58 PM:
5:58:58 PM: ────────────────────────────────────────────────────────────────
5:58:58 PM:   "build.command" failed
5:58:58 PM: ────────────────────────────────────────────────────────────────
5:58:58 PM:
5:58:58 PM:   Error message
5:58:59 PM:   Command failed with exit code 1: rm -rf __obsidian __site && mkdir __obsidian && mv * __obsidian || true && git clone https://github.com/ppeetteerrs/obsidian-zola.git __site && __site/run.sh (https://ntl.fyi/exit-code-1)
5:58:59 PM:
5:58:59 PM:   Error location
5:58:59 PM:   In build.command from netlify.toml:
5:58:59 PM:   rm -rf __obsidian __site && mkdir __obsidian && mv * __obsidian || true && git clone https://github.com/ppeetteerrs/obsidian-zola.git __site && __site/run.sh
5:58:59 PM:
5:58:59 PM:   Resolved config
5:58:59 PM:   build:
5:58:59 PM:     command: rm -rf __obsidian __site && mkdir __obsidian && mv * __obsidian || true && git clone https://github.com/ppeetteerrs/obsidian-zola.git __site && __site/run.sh
5:58:59 PM:     commandOrigin: config
5:58:59 PM:     environment:
5:58:59 PM:       - LANDING_BUTTON
5:58:59 PM:       - LANDING_DESCRIPTION
5:58:59 PM:       - LANDING_PAGE
5:58:59 PM:       - LANDING_TITLE
5:58:59 PM:       - PYTHON_VERSION
5:58:59 PM:       - REPO_URL
5:58:59 PM:       - SITE_TITLE
5:58:59 PM:       - SITE_TITLE_TAB
5:58:59 PM:       - SITE_URL
5:58:59 PM:       - TIMEZONE
5:58:59 PM:       - ZOLA_VERSION
5:58:59 PM:       - SORT_BY
5:59:00 PM:       - GANALYTICS
5:59:00 PM:       - SLUGIFY
5:59:00 PM:       - HOME_GRAPH
5:59:00 PM:       - PAGE_GRAPH
5:59:00 PM:       - SIDEBAR_COLLAPSED
5:59:00 PM:     publish: /opt/build/repo/public
5:59:00 PM:     publishOrigin: config
5:59:00 PM: Caching artifacts
5:59:00 PM: Started saving build plugins
5:59:00 PM: Finished saving build plugins
5:59:00 PM: Started saving pip cache
5:59:00 PM: Finished saving pip cache
5:59:00 PM: Started saving emacs cask dependencies
5:59:00 PM: Finished saving emacs cask dependencies
5:59:00 PM: Started saving maven dependencies
5:59:00 PM: Finished saving maven dependencies
5:59:00 PM: Started saving boot dependencies
5:59:00 PM: Finished saving boot dependencies
5:59:00 PM: Started saving rust rustup cache
5:59:00 PM: Finished saving rust rustup cache
5:59:00 PM: Started saving go dependencies
5:59:00 PM: Finished saving go dependencies
5:59:00 PM: Build failed due to a user error: Build script returned non-zero exit code: 2
5:59:01 PM: Failing build: Failed to build site
5:59:01 PM: Finished processing build request in 2m51.107181795s
My config file is attached:

Sorry for the late response. It seems like you have removed your notes repository, if you still encounter the issue please let me know again!


Improving the UI

Hey @rohansx As I can see currently your website seems very bad and there is nothing related to books. I want to give your website a whole new look. please assign me this issue and you'll not regret it. Thank you!

@sumitkr2000 yes for now it's not that good
i'm assigning this to you
make sure your design is responsive because that's what we are looking for
color coding ,styling and other stuff can be taken care of easily
so change the ui accordingly post the pictures with pr
hope you can make some good contributions
this issue is all yours

@sumitkr2000 any updates?

I would also like to work on this issue. Can you assign it to me once/if it is free?

@k-deepak04 yes bro i am working on it. Today i was busy so was not able to continue. Tomorrow I'll mame sure it's done.

@sumitkr2000 make sure to take a pull before working

also read the contributing guidelines in the readme

@k-deepak04 yeah ik i have contributed in hacktoberfest and have won swoc so dont worry

Only some of the part of the home page if left otherwise the website is done now.

@sumitkr2000 homepage is already designed by someone
still i'm opening it again add SS will see if your's is better then we will merge it

@k-deepak04 I have designed better than this. I will use some of its content also. Please wait till I complete my work.

@k-deepak04 I have designed better than this. I will use some of its content also. Please wait till I complete my work.

Eagerly waiting

@sumitkr2000 How long will it take?

@rohansx bro actually i am not at home today so was not able to continue. Please give me tome of one more day only.

@sumitkr2000 ok np

#Have a look at it

hey@sumitkr2000 almost Ui is ready as of now, if anything more you want to change with the current UI do provide a video or ss of what kind of changes you want!! also, before moving do take reference from Scribd

@sumitkr2000 Also numerous modifications have been implemented in these days so make sure to sync with the main branch before you contribute to avoid conflicts

@rohansx @AkanshaMundel yeah sure

@k-deepak04 @rohansx Have a look at the home page. After so much hard work finally completed it. If you want any challenges tell me.

@sumitkr2000 ping me on discord : rsx#0352

@rohansx done bro

@sumitkr2000 the UI is good but not aligning with the concept of our project
it's like selling some books
while our whole project is about an online platform of reading books for free.

So if you can make changes according to this it will be good

Thank you, bro. I have not finalized the page content as I said earlier so I have to make changes accordingly. For now, I have shown you only UI. Let me know your website's features and I will make the changes. Thank you!

Should I create a pr now or after doing the changes?? @k-deepak04

@sumitkr2000 keep this on hold
i'm discussing things with rohan i'll ping you after that

@k-deepak04 Ok bro. Let me after you made a decision.

@sumitkr2000 our platform is free one so cut the pricing part
also change the feature section accordingly remove book delivery and all things and add relevant things
change most selling books to most read or somethingd relevant
rest things look good to me
also add one upload section in the navbar instead of FAQ
reference  https://www.scribd.com/home
rest great work just make sure it's responsive and create a PR
our webstie idea - a free platform for reading community where users can upload books they have and others can read those books free of cost , since there is very less few things available and in the available one popular books are not there
so we aim to design that

But how will you access the faq page then?

add it somewhere in the footer

okay bro @k-deepak04

@sumitkr2000 please do this changes as soon as possible
because people are opening issues in the current design
it won't be good for me to assign them things as design is being changed
sorry but if you won't be able to finish it by tommorow
i'll be closing this issue :(

I'll do it by today. I have habit of experimenting that's why it rakes time. Sorry for taking so much time.

@sumitkr2000 i want home page design like this

instead of faq section there will be upload button and below that same books and all that are now there in the home page

@sumitkr2000 use the updated feature one and create a new issue for changing the homepage design i will assign it to you