proposal: cmd/link: by default, do not write out DWARF

This is not as radical as it sounds.
At the very least, we need to understand what the default should be when building the Go installation: write out DWARF, or not? The costs and benefits are more subtle than some realize.
Update: As demonstrated below, dropping DWARF also causes a significant improvement in build/install time.
% cat hello.go
package main

import "fmt"

func main() {
	fmt.Printf("hello world")
}

With this canonical, trivial, but also representative program as input, I used a sequence of Go versions to build the binary on my Mac (OSX 10.13.5, amd64). I have sorted the list into chronological order by version:
% ls -l hello*
-rw-r--r--+   1 r  staff          71 Apr  8  2014 hello.go
-rwxr-xr-x    1 r  staff     1919504 Jun 27 13:44 hello1.4 # built with Go 1.4
-rwxr-xr-x    1 r  staff     1616000 Jun 27 13:54 hello1.7 # built with Go 1.7
-rwxr-xr-x    1 r  staff     1632480 Jun 27 13:45 hello1.8 # built with Go 1.8
-rwxr-xr-x    1 r  staff     1941456 Jun 27 13:47 hello1.9 # built with Go 1.9
-rwxr-xr-x    1 r  staff     2106672 Jun 27 13:50 hello1.10 # built with Go 1.10
-rwxr-xr-x    1 r  staff     2964464 Jun 27 14:01 hello-21Jun-2018 # built with Go at tip on 21 June 2018 - this is just before DWARF compression went in
-rwxr-xr-x    1 r  staff     1970552 Jun 27 13:53 hello1.11beta1 # built with Go 1.11 beta 1 # built with Go 1.11 beta 1, with DWARF compression

I believe the drop from 1.4 to 1.7 (1.5 and 1.6 won't run on my Mac any more) is due to various cleanups in the binary triggered by https://github.com/golang/go/issues/6853.
The growth after that is pretty much all due to DWARF. Absent compression, DWARF debugging is now half the binary, as reported by @rsc's sizecmp:
% sizecmp hello1.7 hello-21Jun-2018
__bss                               108784      116464       +7680
__data                                6144       26896      +20752
__debug_abbrev                         255         467        +212
__debug_aranges                         48           0         -48
__debug_frame                        68836       81036      +12200
__debug_gdb_scri                        40          40          +0
__debug_info                        245056      482436     +237380
__debug_line                        101426      146608      +45182
__debug_loc                              0      436989     +436989
__debug_pubnames                     61781       32854      -28927
__debug_pubtypes                     26794       44637      +17843
__debug_ranges                           0      153520     +153520
__gopclntab                         277492      478600     +201108
__gosymtab                               0           0          +0
__itablink                              64          96         +32
__nl_symbol_ptr                          0         144        +144
__noptrbss                           19520        9208      -10312
__noptrdata                           8264       52284      +44020
__rodata                            208087      290543      +82456
__symbol_stub1                           0         108        +108
__text                              508560      592476      +83916
__typelink                            2732        3032        +300
                         total     1643883     2948438    +1304555
%

That's 1.3MB of growth, almost all in debug info. Even the PC-to-line table grew massively, quite disproportionate to text size, which is inexplicable to me, but also a bit off topic.
So, DWARF is huge, but we need it, right?
I don't think we do, most of the time. Surely when we are using Delve or GDB or perhaps one day LLDB, yes, but mostly not.
The need for DWARF and other debugging support in Go programs is much less than the corresponding need in C programs, for which DWARF was designed. Go binaries already include basic type information (reflection), a simple symbol table, and PC-to-line data. These not only help the running program, they also provide valuable debugging aids as they stand.
Even without DWARF at all, stack traces cased by panic would be unchanged and would contain symbols and line numbers. Pprof, objdump, and many other tools would still work.
The DWARF tables are present only for the debuggers.
And useful though the debuggers are sometimes, they are not used often and often not used at all. I think Delve is a great tool, but I use it only once or twice a year because the existing, built-in debugging information is almost always all I need. Why then do we write bloated binaries, paying a cost in file I/O and DWARF write time (not to mention time to compress now) when half the data in the binary is almost never used?
If I look in my personal bin directory, it consists of a few shell scripts and many Go binaries, and the net size is in the gigabytes. Gigabytes of binaries! I could delete the DWARF data from all of them and get much of the space back at no cost.
Also, keep in mind that much of this data is redundant. Yes, the addresses change between binaries but the type information that we write out for the runtime, garbage collector, and so on is a megabyte or more of utter redundancy, unvarying yet unshared.
The counterargument to dropping DWARF is of course that people want to debug their programs. The recent Go developer survey reported much higher concern for good debugging support than for reducing binary size. But I stress, most programs are never shown to a debugger, and many programmers only rarely use a debugger on a Go binary.
The desire to have good debugging does not immediately translate into writing out full massive DWARF data every time we build and install a program. (Test binaries and such actually skip DWARF, by default.) I believe time might be better spent improving native debugging support in the binaries, such as more informative stack traces, but that is another topic.
So to the proposal itself:
I propose we change the Go build environment to suppress DWARF by default, saving lots of CPU time and disk space. Instead, a global shell environment variable, say GODWARF=1, could be set to cause it to be written out. Programmers that want DWARF can set that once, in their shell profile, and have full data available. Others could set it only occasionally, on bad days.
For the rest of us, the rest of the time, why bother with it?
If it is decided that DWARF is too valuable to disable by default, I would instead propose a variant of this proposal, where I could set GOWARF=0 and turn it off in perpetuity.
In other words, I am proposing two things.

Provide a mechanism, such as a global shell environment variable, to control whether DWARF is written by the tool chain.

Decide whether that setting should switch to "no DWARF" by default. I would like that, but would be almost as happy just to have part 1: a simple way to suppress it.

Note: It's not easy enough to use -ldflags=-w, since there is no mechanism to set LD flags globally in the Go toolchain. Perhaps that's another way to approach the problem.

I think this is a good idea.
We use -ldflags="-s -w" by default in our team for years to keep the binary size down and make the build process fast.
I delete the build those flags occasionally to use go tool objdump to see which function is in the binary.I was surprised that the binary size go from 1.6MB to 2.6MB with golang 1.9 with a simple windows exe.
I even do not know what Delve or GDB is after six years of golang developing.
It looks like this proposal has not effect to me, because i already use -ldflags=-w in my build tool.

I too have tried to disable debugging info globally before, without much success. This proposal sounds great, and I agree with the change in default behavior. If a developer wants to use a debugger, they should be able to set an environment variable.
I also assume this wouldn't affect cmd/link's -s, since it doesn't seem to involve DWARF.

My preference would be for a go build flag. For example -g.

My preference would be a golang package that have a function that can build golang package with all possible switches with nice default value and good field name like GoOs,GoArch,GoPathList,GoRoot,EnableDataRace,EnableDwarf ...
Command line flags or shell environment variables are very difficult for me to understand all the possible and the correct type of that value.
I use golang to replace all bash scripts or ugly command line flags include the scripts to build my golang program.
Is it the reason why we use golang in the first place?
I suggest the command line of golang compiler should run my golang program build script. Then I will write everything else in my golang program build script.

Yes please.  As I understand it delve suggest compiling with -N -l already so adding another flag to the “I want to build for the debugger” step shouldn’t be a large burden.

@bronze1man custom Go builds have been discussed and rejected in the past - please keep this thread on topic. You're welcome to create a new proposal for your idea, though.

@davecheney, I agree with you that "recompile for debugging with Delve/gdb/lldb/etc" is not too onerous and well-established. I just want to point out for the record that the recent work is supposed to make it the case that you don't need -N -l (and the consequent performance loss) just to run those debuggers. While I don't mind training people that if you're going to use Delve you might need a different build, it would be good if we could get away from "if you're going to use Delve you have to give up significant performance", and I believe Go 1.11 is a decent step toward that.

/cc @aclements @cherrymui @dr2chase @heschik @thanm

The DWARF tables are present only for the debuggers.

Profilers read DWARF as well, for what it is worth. It's nice to be able to collect a detailed profile without having to recompile. On the other hand (as with debuggers) very few people run profilers.
How about a tweak -- continue to emit DWARF, but when linking "user" programs, don't include the DWARF from the standard packages (people who use debuggers are rare, but people who debug the Go runtime are even fewer).

How about a tweak -- continue to emit DWARF, but when linking "user" programs, don't include the DWARF from the standard packages (people who use debuggers are rare, but people who debug the Go runtime are even fewer).

That's not that easy. First you'd still want the full debug_frame (at minimum) to unwind the stack (possibly also skeleton DIEs for all functions too). Secondly, delve checks the destination of all CALL instructions to filter away the calls to runtime functions inserted by the compiler. Thirdly delve needs a bunch of DIEs from runtime (off the top of my head: runtime.allgs, runtime.g, runtime.firstmoduledata) for various reasons. Basically you would need to do something like microsoft's symbol files for system dlls.

@aarzilli
Everything you say makes sense, but I thought we had previously established that delve users would already be recompiling with special delve-friendly compiler flags?

@thanm: I was under the impression that this would be a compromise so they wouldn't have to. Also I assume most other tools will have needs similar to delve.

I am not the least bit happy that I'm expected to debug something different than what I run, and that a recompilation is expected.  I don't run the debugger much because it's not easy to run the debugger much, and I'm trying to fix that ("not too many people swimming across the river, why do we need a bridge?").  I do think it is onerous; and I view it as one of the things that Java got relatively right.
There's the additional problem that the -N -l flag combo (treating it as a single flag) is not tested nearly as well as the default; if we honestly support it, we'll need to run all.bash in that mode too, and anyone with widely-used libraries will want to also test using that mode, just in case.  Doubling the testing load is not going to speed up developer workflow.  And of course, we must document the flags, and people learning to use the compiler will need to learn about them if they plan to create binaries that delve or gdb can debug.
The main point of adding all this debugging information to Go binaries was these two things; to remove speed bumps from Go debugging, and to make progress on the do-we/don't-we support problem for these flags.
Debugging information is also not just for debuggers.  Years ago a friend of mine showed me what he called the "killer app for Python", which was just really good backtraces that did a nice job of reporting the values of all the local variables in the stack trace.  Their app would wrap all that up in a neat little bundle, ask the customer if they were willing to send it in as a bug report (with certain assurances about information confidentiality that probably wouldn't fly now), and his next interaction with said customer was not to badger them for more information, but instead "here's the dot-release that fixes your problem, download it at your convenience". "And the customer thinks I'm a wizard!"  We could/should do this for Go, at least as an option.
There are some alternatives, for instance, with reproducible builds we can generate debugging information on demand -- but when we mention that to nearby colleagues working on other languages and platforms, their reaction is "yeah, right".  Their best practice is to build with debugging, make a copy (of either the debugging info alone, or the entire binary) and strip for shipping.
Is binary size causing some other problem that can be discussed publicly?  Are we filling up disks? (not mine -- with 10 copies of the Go repo in various states of build, plus all the go-gotten binaries for tools, plus testing and benchmarking, about 2% of my "disk", counting both bin and pkg) . Is there some quota that we're exceeding?  Are builds taking too long, and if so, by how much, and have we explored other ways of saving that time that don't reduce functionality?  (the linker is due for a rewrite, the register allocator is definitely a time hog, Josh has done some interesting work on moving code from the front end to SSA that seems to save a little time, and has the potential to expose more of the compiler to multithreading).

"Debugging information" does not mean only "DWARF". As I said in my post, we can improve self-debugging support independently of improving debugger support, which means DWARF.
@dr2chase can always get the DWARF he wants all the time by just setting the flag once in his profile. I am not proposing to turn DWARF off, I am proposing to turn it off by default as few programmers need the support it provides every day. You are not expected to run without DWARF, you are expected just to set the flag once, for yourself, if you want DWARF on.
Binary size matters. We copy binaries around, we push binaries over networks, we put them in containers, we store them in the cloud, we fill our bin directories with many programs; in those operations, the accumulations are significant.
As to your performance problems, my experiments with building the go command (cmd/go) show that generating DWARF for a significant program is about 40% of the build CPU time. That is a major chunk.
% rm go
rm: go: No such file or directory
bismarck=% time go build

real	0m1.205s
user	0m1.235s
sys	0m0.238s
% rm go
% time go build -ldflags=-w

real	0m0.730s
user	0m0.703s
sys	0m0.223s
% hoc -e 730/1235
0.5910931174089069
%

You propose we double our testing load to account for the presence/absence of this option?

Some compiler and tools work may require more testing, but only modest amounts. The great majority of Go programmers would be unaffected that way.

If the binary records an accurate list of all modules (with versions) used for the build and all other relevant flags, it seems like delve could transparently generate the necessary information by retrieving the source and invoking the compiler.

Would building out two separate binaries one with debugging information and one without (Using go build or maybe a different command 'go release' or some other command ) would maybe help with people that don't like the idea of having there final binaries without DWARF or having to set a environment variable right off the bat? Don't know if this is in scope / on-topic for this proposal, just wanted to throw out a thought.

@dr2chase respectfully the “why build bridges” argument applies equally to binary size “disks are hella big, why optimise for space?”

Now that DWARF is compressed on Mac (and I assume also on Windows), it seems like we're back to a 20% or so space overhead, and the main issue is now link latency.
Even on Linux I see DWARF aggregation approximately doubling the time spent in the linker (and it's not like the non-DWARF parts of the linker are terribly fast). So this is not a Mac-specific problem. Of course, compression might be what's taking all the time.
Putting this on hold pending better understanding of where all the CPU time is going and that there aren't significant optimizations remaining that might make it faster. If 2X really is the cost of DWARF, then we should resume this conversation about whether it makes sense to pay that cost speculatively all the time when the probability of needing it is near zero.

Filed #26318 for the linker time issue.

Almost all my production server code has the prof built in.  As far as I know this is standard practice.  I would hate for this to become harder to do.  Also this would be a breaking change.

Almost all my production server code has the prof built in.

As mentioned in the very first post of this issue, profiling is not affected when DWARF information is not present:

Even without DWARF at all, stack traces cased by panic would be unchanged and would contain symbols and line numbers. Pprof, objdump, and many other tools would still work.

What are the alternatives to reduce binary size and compile/link time? (Are these issues filed for them already?)


fix: removed code of conduct

This PR removes the code of conduct file to pass the repo linter check.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@zstix  can I get your 👍  on this?
Pull Request / validate nerdpack (pull_request) Failing after 5s — validate nerdpack  - is due to the code of coduct check in that is no longer relevant, once this is all merged it should be ok.


Set-DbaAgentJobStep Fix

Changed parameter Force from bool to switch

@sanderstad If you can re-sync your branch with development it should resolve the conflict. There have been a good bit of changes made in development, and this command was effected.

Oops, i forgot to close this. I switched the bool to a switch and did a sync. This should be fixed.


Reformat to 120 columns

Motivation
Keep consistent code format
Changes

install golines in ./bin directory automatically by the makefile,
run golines in dry mode as part of lint target. Fail if any lines would be changed,
run golines in write mode as part of lint-fix target.

bors merge

bors merge


Update maintainers to include JDGrimes and GaryJones

I'm assuming that was going to be #reviewmerge ?

Yes :smile:


Issue Installing Pygrid on Mac with Docker method

I am having a little issue with installing the pygrid platform on my local computer and I wanted to know where I should get support for this?  I am running mac os 10.13.6 and i followed these instructions https://github.com/OpenMined/PyGrid. I used the docker method. I pulled and ran openmined/grid-node then changed the etc/hosts file to include <IP_ADDRESS> host.docker.internal. then I navigated to pysyft/examples/tutorials/websocket/deploy_workers and ran $ docker-compose -f docker-compose.yml up. There is no -mac version so i changed the command to just docker-compose.yml. I get the docker container running as seen in the photo. But when I try to connect through the sample notebook i get 'connection refused error' as seen in photo.

Thanks for any help guys! I wanna start contributing!

Hello @ccurelea, I'm glad that you're interested to contribute with us!
The problem pointed out has probably already been solved by PR #534  and #533.
Could you try again and give us a feedback?


go: Don't check for initrd

hyperkit happily boots with just a kernel (and the rootfs on
a disk device, for example). So, if booting in non-fw mode
only check for the kernel.
Signed-off-by: Rolf Neugebauer<EMAIL_ADDRESS>

Should we not check that iff h.Initrd != "" it exists?

@ijc, good idea. I pushed an update


Add ability to specify maximum search depth [FEATURE REQUEST]

At the moment the user must use other tricks to limit search depth. It would be very handy
to be able specify a search depth limit such as 0, 1, ..., or N, where the default is the current behavior.

Not needed now.


Issue installing genaiscript behind a proxy

I cannot run npm install genaiscript behind my enterprise proxy.
The install chokes when trying do download a zip file for the ripgrep package.
npm error VError: Failed to download "https://github.com/microsoft/ripgrep-prebuilt/releases/download/v13.0.0-10/ripgrep-v13.0.0-10-x86_64-pc-windows-msvc.zip": RequestError: connect ETIMEDOUT [<IP_ADDRESS>:443](http://<IP_ADDRESS>:443/)

It seems that a lot of JS library have very poor support for proxies.
RipGrep is using got instead of the nodeJS built-in ones. See https://github.com/lvce-editor/ripgrep/blob/main/src/downloadRipGrep.js#L67

Has anyone experienced similar issue when installing genaiscript?
Any easy workaround? Can I comment the package? Another option would be to rewrite the RipGrep code to use node-fetch instead of got.

I've made ripgrep a optionalDependency (https://docs.npmjs.com/cli/v10/configuring-npm/package-json#optionaldependencies) so that, at least the install does not just fail.
(The whole node.js npm ecosystem is a esoteric mix of fetch replacement and it'll take a while for all the project to align on the built-in fetch api...)

You can definitely comment this package; it is only used for the grep file search and loaded dynamically.

Works.


Lua vs Wasm filter on failures during filter chain

I have an envoy configuration which contains 3 filters:

An ext_authz filter which returns a 4xx status code
A Lua filter
A wasm filter

Something like this
          - name: envoy.filters.http.ext_authz
            typed_config:
              "@type": type.googleapis.com/envoy.extensions.filters.http.ext_authz.v3.ExtAuthz
              http_service:
                path_prefix: "/429"
                server_uri:
                  uri: "http://httpstat.us/429"
                  cluster: "ext_authz-http-service"
                  timeout: "3s"
          - name: envoy.filters.http.lua
            typed_config:
              "@type": type.googleapis.com/envoy.extensions.filters.http.lua.v3.Lua
              default_source_code:
                inline_string:
                  function envoy_on_request(request_handle)
                    request_handle:logInfo("Hello from lua filter")
                  end
                  function envoy_on_response(response_handle)
                    response_handle:logInfo("Bye from lua filter")
                  end
          - name: envoy.filters.http.wasm
            typed_config:
              "@type": "type.googleapis.com/envoy.extensions.filters.http.wasm.v3.Wasm"
              config:
                name: config-name
                root_id: id
                vm_config:
                  vm_id: vm.id
                  runtime: envoy.wasm.runtime.v8
                  code:
                    local:
                      filename: /path/to/my.wasm
                  allow_precompiled: true

When trying this, I only get the Lua envoy_on_response callback triggered, but not the on_http_response_headers nor the on_http_response_body wasm callbacks.
Some trace logs:
[2024-10-23 19:42:14.759][53500569][trace][misc] [source/common/event/scaled_range_timer_manager_impl.cc:60] enableTimer called on 0x600000971580 for 300000ms, min is 300000ms
[2024-10-23 19:42:14.759][53500569][trace][http] [source/common/http/filter_manager.cc:1197] [Tags: "ConnectionId":"5","StreamId":"12470536000766714697"] encode headers called: filter=envoy.filters.http.wasm status=0
[2024-10-23 19:42:14.759][53500569][trace][lua] [./source/extensions/filters/common/lua/lua.h:149] creating N5Envoy10Extensions11HttpFilters3Lua19StreamHandleWrapperE at 0x11a356b80
[2024-10-23 19:42:14.760][53500569][info][lua] [source/extensions/filters/http/lua/lua_filter.cc:920] script log: Bye from lua filter
[2024-10-23 19:42:14.760][53500569][debug][lua] [source/extensions/filters/common/lua/lua.cc:39] coroutine finished
[2024-10-23 19:42:14.760][53500569][trace][lua] [./source/extensions/filters/common/lua/lua.h:210] marking dead N5Envoy10Extensions11HttpFilters3Lua19StreamHandleWrapperE at 0x11a356b80
[2024-10-23 19:42:14.760][53500569][trace][http] [source/common/http/filter_manager.cc:1197] [Tags: "ConnectionId":"5","StreamId":"12470536000766714697"] encode headers called: filter=envoy.filters.http.lua status=0
[2024-10-23 19:42:14.760][53500569][trace][ext_authz] [source/extensions/filters/http/ext_authz/ext_authz.cc:186] [Tags: "ConnectionId":"5","StreamId":"12470536000766714697"] ext_authz filter has 0 response header(s) to add and 0 response header(s) to set to the encoded response:
[2024-10-23 19:42:14.760][53500569][trace][http] [source/common/http/filter_manager.cc:1197] [Tags: "ConnectionId":"5","StreamId":"12470536000766714697"] encode headers called: filter=envoy.filters.http.ext_authz status=0
[2024-10-23 19:42:14.760][53500569][debug][http] [source/common/http/conn_manager_impl.cc:1863] [Tags: "ConnectionId":"5","StreamId":"12470536000766714697"] encoding headers via codec (end_stream=false):

Is this expected? Envoy 1.28 for context
UPDATE: External processor filters seem to behave the same way as the lua one, I am getting a ProcessingRequest for RESPONSE_BODY case. Is there a different behaviour for wasm?

Yeah. Seems it's designed as that (although I don't know why). The wasm will be skipped if the request headers is not processed.
In your case, the auth will send a local reply and the the request headers won't be processed by the wasm, so, the wasm will be skipped.

I think this might be due to implementation, because proxy-wasm defines a stream context that allows the wasm module to restore the context of a specific request during Envoy's asynchronous processing of multiple requests. Since this stream context is only created during the request header phase, if the wasm filter finds that the context has not been created during the response header phase, it will automatically skip.
However, this design isn't necessarily flawed; in fact, I think it might even have some advantages. While it does sacrifice some flexibility, the logic of the wasm plugin can be simpler, as it doesn’t need to account for situations where the decode phase hasn't been passed, leading to missing states.


[multi-arch] skip more plugin tests on non-x86

Until the plugins are multi-arch plugins, or built on runtime,
skip these tests like we do with the remainder of the plugin tests.
Signed-off-by: Christopher Jones<EMAIL_ADDRESS>

Failing arm test has been seen in a couple other PRs such as #29030, I don't think it's related.
03:24:34 ----------------------------------------------------------------------
03:24:34 FAIL: docker_cli_logs_test.go:221: DockerSuite.TestLogsFollowSlowStdoutConsumer
03:24:34
03:24:34 docker_cli_logs_test.go:250:
03:24:34     c.Assert(actual, checker.Equals, expected)
03:24:34 ... obtained int = 126418
03:24:34 ... expected int = 200000
03:24:34
03:24:40 ----------------------------------------------------------------------


Can this support swift?

the swift  class or struct  can use this lib.   thanks .

NO.
This library is only suitable for Objective-C.


Loads of cleanup and bug fixes

This pull request has not yet been tested, it would be appreciated if someone could do so.

+1

+1


feat(prow/cluster): add jenkins-operator component

What problem does this PR solve?
Issue Number: close #xxx
Problem Summary:
What is changed and how it works?
What's Changed:
How it Works:

/merge


Bump go.mod k8s.io/kubernetes from v1.28.3 to v1.28.4 to fix CVE-2023-5528

Fixes CVE-2023-5528
This was fixed in main branch in https://github.com/GoogleCloudPlatform/gcs-fuse-csi-driver/commit/10fe6ba846d0a9e7727730ee9bec7b4ba77a4e15
Bump go.mod k8s.io/kubernetes from v1.28.3 to v1.28.4 to fix CVE-2023-5528

/assign @songjiaxun

Cherry picked the changes. Closing this PR.


Apply latest bugfixes of dev branch to pilot

Author's Note: I'm asking for verification of this issue
The pilot branch in its current form is lacking bugfixes that have already been applied to the dev branch. Since I recall that pilot branch is used for simulation and some of those bugfixes are related to errors that result in failure of core functionality, it should be of great importance that those are also patched into the pilot branch.

Let's discuss / do this today, 17:15h on Discord.


Just installed this packed, hit the scan blueprints this is the error I get

https://flareapp.io/share/J7oK2947

I've tagged 1.1.1 which should solve this

Awesome, that fixed it! Also, thank to so so much for this plugin, it's something I wished existed years ago! ❤

You're welcome!


support for custom signing algorithms

Implementation for https://github.com/brianloveswords/node-jws/issues/34

Hey @g-p-g thanks for the PR - apologies for not taking the time to look at it.
Two thoughts:

I think it could use some stricter checking. For instance, rather than letting the call to algo.verify throw  undefined is not a function if it doesnt exist, i'd rather we do that check up front. For consistency purposes, I also think it could make sense that we "require the full implementation be provided", i.e, such that algorithm must have sign AND verify, in either of the calls. Though I can see some benefit to only loading in one (in which case, I think we could just take a function directly).

I think the language in the README might benefit from being a bit more warning. There's nothing we can do about making sure things are actually valid, or results are interoperable, if the passed in algorithm is poorly implemented.


postgres container with external volume erases database

Hi. How do I externalise a database from within this container? Starting the container with no docker volume is fine. Starting the container with a docker volume mapped to a host folder erases the database and config. I understand that this is correct docker volume!e behaviour, the host folder is mounted over the top of the container folder.
How to I get around this issue and map the db that is created on container start up to my host folder so that it is available when the container next starts up?
Not sure what I am doing wrong here.
docker run --name test-postgres \
-e POSTGRES_PASSWORD=test123 \
-v /home/vagrant/workspace/shared-data/postgres:/var/lib/postgresql \
-d postgres:9.6

This spins up the container and cretes the DB as expected. Container result:
root@fe0e5751c98d:/var/lib/postgresql# ls -al data
total 0
drwxr-xr-x. 2 root     root      6 Jun 20 12:32 .
drwxr-xr-x. 3 postgres postgres 17 Jun 20 12:32 ..

 Could the group and owner of the container created folder be preventing the folder from being mapped correctly by Docker or Vagrant??

Just a quick idea, did you try specifying the full path that is used in the VOLUME directive, /var/lib/postgresql/data ?

Just tested with full path (/var/lib/postgresql/data), and this fixes the missing data issue for me.
It seems that when the parent path is used (/var/lib/postgresql) as the named volume with Docker (currently on v1.11), this data disappearance happens. I don't think the Postgres container is doing anything wrong, but maybe worth inquiring with Docker directly?  (Note that the unnamed volume -- the one declared in Postgres's Dockerfile is still created.. I forget which of the two volumes has data though; maybe OP can verify).

Hmm. spotted something interesting with the permissions on the posgres directories that get created on the dockerhost. See above.

Duplicate of #103; see specifically https://github.com/docker-library/postgres/issues/103#issuecomment-167631548


Play nice with pagination, etc.

We will want to return an AR::Relation when given one.

We will no longer seek to support metadata on collections, becomes too complex and not very PORO.


Selecting app without switching to that workspace

Hello Nikita,
I was wondering is it possible/ what's the best way to select an app without switching to the workspace that app is open in?
For instance if safari is open on workspace 1 and I am on workspace 2, how would I open a new safari window on workspace 2? At the moment what I'm doing is opening on workspace 1, then moving the window to workspace 2, then switching to workspace 2.
Many thanks,
Casey

I believe I have a similar issue.
I have keepassxc always on ws9, and my browser in ws1, when browser asks keepassxc for credentials, keepassxc opens a dialog in ws1 to either allow or deny the request. Clicking anywhere in that dialog (including the buttons) actually sends me to ws9, instead of registering the button click, then I have to move back to ws1 to click again and only then the button click is registed.

Will be covered by #186 & #278
list-windows --app-bundle-id com.apple.Safari --format %{window-id} | xargs move-node-to-workspace focused --act-on-window-id


[Slider] Breaks with some configurations of min, max and step.

On some configurations of min, max and step, the slider doesn't allow scrolling to the end of it with the mouse. If you focus it and then use the keyboard arrows, you can reach the end.
In the reproduction below I use:
min: 100
max: 112
step: 10
Reproduction:
https://www.webpackbin.com/bins/-Kj7_VQiIRdkklvACgVz
I was therefore expecting to be able to reproduce it with this:
min: 100
max: 115
step: 10
But this configuration does work properly, so I am unsure where the problem lies

I am working on this right now.


No longer works with Ferrari 458 Spider

The Ferrari 458 spider no longer appears to (atleast steam) games as a xbox controller .
Found:
American Truck simulator doesnt recognise it as a xbox controller
Euro Truck sim aswell

Did you change the settings in the game itself?

Yeah, ETS2 doesn't recognize it as a controller and Windows seems to think a very slight turn of the wheel registers as a right click on the mouse. And since ETS2 has now shifted all controller bindings to Steam Input instead of ingame, it's now extra difficult/next to impossible to configure. Also doesn't seem to activate its auto-centering system at all which also kind of makes it more difficult to use.

Check if the WheelCompatibility service is running. If the wheel isn't
detected at all, restart your computer with the wheel plugged in. If
this doesn't work, I don't think I can help.
If you are running the latest version, try the one before (1.2.0).
On Fri, Feb 23, 2024, 9:05 AM snoozysoft @.***> wrote:

Yeah, ETS2 doesn't recognize it as a controller and Windows seems to think
a very slight turn of the wheel registers as a right click on the mouse.
And since ETS2 has now shifted all controller bindings to Steam Input
instead of ingame, it's now extra difficult/next to impossible to
configure. Also doesn't seem to activate its auto-centering system at all
which also kind of makes it more difficult to use.
—
Reply to this email directly, view it on GitHub
https://github.com/cmumme/XboxWheelCompatibility/issues/105#issuecomment-1961385669,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASAOQF4VN5O2Z6Y3ZPCO6WLYVCO2VAVCNFSM6AAAAABDNPFMWCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRRGM4DKNRWHE
.
You are receiving this because you commented.Message ID:
@.***>

Getting the same issue, service running, using V1.2.0 and tried V1.2.1 to no avail, had no problems previously until I reset my PC (which I now regret) and no longer can use the 458 Spider wheel for F1 23.

It seems like with new Windows (DomTries) / Steam (Steam input doesnt fix) updates have broken this entirely, we can hope for updates and fixes although possibly unlikely.

Possible fix: Uninstall drivers mentioned

Possible issue: With the drop of support of Xbox Console Companion , drivers may have changed?


[NDTensorsMetalExt] Fix issues not importing some LinearAlgebra functions

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

Comparison is base (063ccbe) 85.36% compared to head (7f60b80) 54.56%.

:exclamation: Current head 7f60b80 differs from pull request most recent head 44ec8e8. Consider uploading reports for the commit 44ec8e8 to get more accurate results

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##             main    #1233       +/-   ##
===========================================
- Coverage   85.36%   54.56%   -30.81%
===========================================
  Files          89       88        -1
  Lines        8445     8392       -53
===========================================
- Hits         7209     4579     -2630
- Misses       1236     3813     +2577

see 37 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


compile 'com.github.HITGIF:TextFieldBoxes:1.3.6' doesnt work.

Failed to resolve: com.github.HITGIF:TextFieldBoxes:1.3.6
Version 1.3.5 still working.
1.3.6 has some erros on build.

now fixed :)
Sorry for that


Add doc-comment to test README examples

Allows to keep in check the README file examples.

Thanks! That looks useful.


[MINOR] Change default-rack to /default-rack

Change default-rack to /default-rack

Why do you need this change?

At the initial design, we prefer to extract the 'exact rack info', for example,  '/rack-45' -> 'rack-45',  '/' will be removed.

@qingwen220  Because ClusterNodeAPITopologyRackResolver use "/default-rack" .I think it will issue some problem when  you complete EAGLE-876.

It do not matter.  The node with a new rack info will replace the old one


Parseable output

I'd like to wire mixed-content-scan into a reporting pipeline (which uses non-PHP code). The CLI interface for mixed-content-scan is a godsend, except that it's really only good for human eyes.
I'm highly unskilled with PHP, so I'd be a poor candidate to implement this -- but I think a --csv flag that causes the output to be streaming CSV might be a reasonable candidate for machine-repurposable output. That way it's still line-by-line and doesn't disrupt program flow, while creating something that another task can pick up afterwards and do something with.

Reading more about monolog, maybe the JsonFormatter is the way to go here. Swapping out a log formatter might even be within my PHP grasp. I'll give it a go.

Fixed by #16.


Autocomplete error when typing slowly

Hello there,
We're using Bergmania.OpenStreetMap in a Umbraco 13 project and we are experiencing an issue with the autocomplete of the address bar. When you're typing relatively fast, the address bar and the autocomplete function works, when you hit ENTER or click on the result, the map gets updated just fine. The same goes for when you're copying/pasting the address (CTRL+C, CTRL+V).
However, when you don't type fast (like some/most of our editors), and type really slow, the autocomplete function malfunctions and a JavaScript error appears in the console when hitting ENTER or clicking on a result. The map/leaflet does NOT get updated with the new address. The address is not converted to a latitude/longitude and is not stored in the database. Some/most of our editors just hit save and navigate away, without having updated the location.
I've already told my editors to be aware of this behavior and hit ENTER a second time. But I would much rather fix the issue they're experiencing, hence I'm raising this issue here.

The current address in the screenshot is set to "Vestre Stationsvej 7, 2, Postboks 189, 5000 Odense C".
When typing the new address "Grote Voort 8", the address bar shows the address, but the map/leaflet is not updated.
In the console the following JavaScript error appears:

We are using v5.3.2 of the NuGet Plugin. We cannot install the v6, since we're not on Umbraco 14 (yet).
I hope I described the issue well enough and you're able to reproduce the issue.
Kind regards,
Percy Dobbelsteyn

STEPS TO REPRODUCE:
Setup a new Umbraco 13.5.1 project by using the Umbraco CLI:
dotnet new -i Umbraco.Templates::13.5.1
dotnet new umbraco -n OpenStreetMapIssue
dotnet new sln
dotnet sln add OpenStreetMapIssue
cd OpenStreetMapIssue
dotnet add package Bergmania.OpenStreetMap -v 5.3.2

Install umbraco
Log into umbraco backoffice
Go to Settings > Add a new Document Type called 'Website', add a property called 'Location' (choose 'Open Street Map' as editor), make sure to allow as root permission
Go to Content > Create a new 'Dummy' website, do not yet set a location.
After creation, open (F12) Developer Tools in your browser
Try and change the location as described before (slowly typing).
Watch the console errors appear...

Hi @nexwork-percy ..
Thanks for reporting. I can't really reproduce, but based on the codeline. It seems like it happens on onSubmit, which I can only hit when pressing enter or choosing from the dropdown with the cursor.
Just to understand, would it be a problem just to ignore the onSubmit event if the provided object do not contain any properties?
I assume your editors continue typing until the found something that in the end should be a valid call to onSubmit

Hi @bergmania ,
Many thanks for looking into this issue. It's not just an error in the console, most - if not all - of my editors don't even know there's an error in the console, or that there even exists such a thing as a console. They look at their keyboard, hovering with their finger over the keys until they find the key they want to press 🥇 ((^_^))...
After finishing the address they typed, the screen has changed multiple times, providing possible addresses for them to click on. But they only hit ENTER or click on the address at the very end.
This address is filled in the input field, but the map doesn't get updated, it stays on the old location.
They then mistakenly think they updated the location properly and don't give it a second glance. If only they would press ENTER a 2nd time, then the map gets updated....
I can reproduce the issue, but I have to type really slow. Sometimes I can't reproduce it, I think I typed too quick, I know this makes it hard for you to debug...
If you have troubles debugging, I can make a recording on my dev machine, or if there's another way I could help, I'd be happy to assist.
Thank you,
Percy

Everything that can help me reproduce is valuable.. How slow should I type. I tried up to 30 seconds between each character, but I cannot reproduce.
Am i correctly in my assumption that you are using Google Chrome as browser?


Support modbus single register writes and long reads

Resolves #525
Supersedes #441

Supersedes https://github.com/EVerest/everest-core/pull/441: Should we close #441 then?


allow mdns cifs shares

closes #927
cc @MattDHill

@k0gen please comment here with the results of your test

@k0gen please comment here with the results of your test

Fresh new sd-card flashed with eos.img 6942eda4323224055af3fae207c00ccc2c450ce3 build.
I toked the Migration route and wanted to recover from backup hosted on NAS. Entering hostname.local didn't work

ended up entering just hostname and because the drive was not detected I restarted the setup and successfully migrated from the backup.

Note the notification "Connection Failed" on iPadOS dark mode is hard to read.

I have also noticed that About > LAN Address is displaying https://embassy.local/

Also forgot to mention this:

Notice those two are the same shares, only one has /embassy and the other embassy path.


Step size initialization with adapt engaged=0 not working

Summary:
@wds15 found that cmdstan is ignoring stepsizes provided as arguments when num_warmup=0 and adapt engaged=0
Description:
For more details: http://discourse.mc-stan.org/t/saved-mass-matrix/2921
Current Output:
The step size is being set to 1 and the calculation doesn't work
Expected Output:
The step size should be set to what is provided on the command line
Current Version:
v2.17.1

Fixed in #604


Automated cherry pick of #2311: fix: avoid duplicate sku error

Cherry pick of #2311 on release/2.12.
#2311: fix: avoid duplicate sku error

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.12@7efb194). Click here to learn what that means.
The diff coverage is n/a.

@@              Coverage Diff               @@
##             release/2.12   #2312   +/-   ##
==============================================
  Coverage                ?   7.09%
==============================================
  Files                   ?     452
  Lines                   ?   71318
  Branches                ?       0
==============================================
  Hits                    ?    5057
  Misses                  ?   65844
  Partials                ?     417

Flag
Coverage Δ

#aFlag
7.09% <ø> (?)

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 7efb194...e709536. Read the comment docs.

/approve
/lgtm


Add Lua test

Using lua-http

This is perfect. Thanks!

Interesting... looking at the archived results you uploaded at https://github.com/Netflix/bettertls/commit/a1447c25c5a2ae43b9af7f662bd82932e5232e4d the status of all of them is ERROR.
Did things not get run correctly somehow?
You can check the error like so:
diff --git a/testsuites/lua_test.lua b/testsuites/lua_test.lua
index 3795703..242a777 100755
--- a/testsuites/lua_test.lua
+++ b/testsuites/lua_test.lua
@@ -42,7 +42,8 @@ local request = http_request.new_from_uri(uri)
 -- Create TLS context with certificate store containing a single trusted root cert
 request.ctx = http_tls.new_client_context()
 request.ctx:setStore(ossl_store.new():add("../certificates/root.crt"))
-local headers = request:go()
+local headers, err = request:go()
+print(err)
 if not headers or headers:get ":status" ~= "200" then
        return os.exit(1)
 end

Yep, looks like I wasn't paying close enough attention. With your suggestion I see this on the CLI:
$ lua lua_test.lua https://test.nameconstraints.bettertls.com:8973/well-known.txt
http.h1_stream{connection=http.h1_connection{type="client";version=1.1};state="half closed (local)"}

That particular endpoint should be a good test since it has the proper name in the CN and SAN and has no name constraints extension. Compare with curl:
$ curl --cacert ../certificates/root.crt https://test.nameconstraints.bettertls.com:8973/well-known.txt
OK

Any idea on what should be patched to fix this?

That output you pasted is a success. What was the exit code?
More detailed debugging code:
local headers, err = request:go()
if not headers then -- request failed, e.g. server uncontactable, error message is in `err`
    print(err)
else
    headers:dump() -- dump list of headers to console (including status)
end

Looks like there was a bug in runner.js that was pointing test urls to the wrong place. (I think I refactored the intended test URL at some point and must have missed that one.) It actually hit the python test results as well, so I reran lua and python and updated the archived results. Lua passes 100%! (Incidentally, python has the recurring issue of not applying IP constraints to the CN when the CN is an IP.)

Great :)

Minor thing: in the archived results drop down, the lua entry doesn't mention the openssl version.
IIRC, using an IP isn't supported in openssl 0.9.8 (which is what Apple ship in OSX), so it's worth mentioning the openssl version.

Oh yea, sure thing. I actually didn't realize that the number at the end of the useragent string was the openssl version. I tweaked that useragent string to use the human-readable luaossl.SSLEAY_VERSION version string and stuck that in the drop-down as well.

luaossl.SSLEAY_VERSION

That is the openssl version it was compiled against.
luaossl.version() is the version it's running with.
Usually they're the same, but sometimes they are different :)

That is the openssl version it was compiled against.
luaossl.version() is the version it's running with.

Oops sorry that was wrong. Ignore that comment.


When i use Vue.http.post, if i want to set data in response, i should place data object in which params?

in seconde [data], or in third [options.data] ?
i am confused.

Try this
this.$http.post('/someurl', this.object).then(function (response) {
                    console.log(response.data)
                },function (response) {
                    console.log(response.data)
                });

@kayyyy  ok.It's run.Thank you.


LSP Option does seem to have an issue

After caling fstar with the --lsp option:
Trying to execute the textDocument/didOpen command with any file resulted in an error. (on wsl)
sending message:
Content-Length: 218

{  "jsonrpc":"2.0",  "method":"textDocument/didOpen",  "params":{    "textDocument":{      "languageId":"fstar",     "text":"(*some code*)",      "uri":"file:///some/existing/file.fst",      "version":0    }  }		}

returned following error:
[E] Failed to load deps. Message: FStar_Errors.Error(_)Content-Length: 159

{"jsonrpc":"2.0","method":"textDocument/publishDiagnostics","params":{"uri":"file:///some/existing/file.fst","diagnostics":[]}}

The LSP option of F* is not very well maintained and is slowly rotting.
We do have a VSCode extension for F* however: https://github.com/FStarLang/fstar-vscode-assistant
Are you trying to use F* + LSP + some other editor?

Yes.
I tried using it with vim.
So I should probably switch to VScode or emacs?

Thanks for the response.


Automatic trailing slashes

Is your feature request related to a problem? Please describe.
Currently, route matching honours whether the URL pattern contains a trailing slash or not.
For example:

The /foo URL pattern matches /foo but not /foo/.
Likewise, /foo/ matches /foo/ but not /foo.

Describe the solution you'd like
There should be an option to support both versions (w/ and w/o the trailing slash), and it should be the default behavior. The framework user could turn it off (globally or on a per-route basis) in order to turn off exact match.
Describe alternatives you've considered
/
Implementation ideas
Introduce an auto_trailing_slash option on BaseRouter (and on App) and BaseRoute, defaulting to True, which would do the following:

If the URL pattern does not end with a trailing slash, add one.
If the requested URL path does not end with a trailing slash, add one — but do not perform a 301 redirection, because that would lose form data and some special headers.

Additional context
/

@florimondmanca I want to give a shot on this

Sounds good!
As for the last bullet point in the issue, I think we should actually redirect if the client requests /foo but the route is actually /foo/. I’m not sure why I said we would lose POST data or headers doing so. That said, CORS would definitely not work in case of redirection (not supported by the standard) so we should probably document that somewhere in the routing documentation. We can totally think about that later on. :-)

Hey, any luck on this @heykarimoff? If you've tried something out and want to share some insights and perhaps any difficulties you've encountered, feel free to do so!

Sounds good!
As for the last bullet point in the issue, I think we should actually redirect if the client requests /foo but the route is actually /foo/. I’m not sure why I said we would lose POST data or headers doing so. That said, CORS would definitely not work in case of redirection (not supported by the standard) so we should probably document that somewhere in the routing documentation. We can totally think about that later on. :-)

I agree on. I looked at the source codes of Django & Flask and they also redirect to trailing slashed path.

Hey, any luck on this @heykarimoff? If you've tried something out and want to share some insights and perhaps any difficulties you've encountered, feel free to do so!

Thanks you, I have push my changes to this branch please have a look✋.
Current challenges are:

Where to add AUTO_TRAILING_SLASH global setting
How to deal with WebSocketRouter

Thanks! Hope you enjoyed your trips. :-)
Can you open a PR so we can view and discuss the changes more easily? 👍

Hi @heykarimoff, I've just realised that the change on your branch is very easy to look at — sorry for not responding earlier.
I think it looks good, and I think we can try to merge this before #271 goes through, as it contains a large refactoring of the routing implementation, and it's easier to bring changes back to there than the other way around.
Anyway, as for the challenges you mentioned:

Where to add AUTO_TRAILING_SLASH global setting

May I suggest creating a plugin? It would allow people to configure that via the settings module.

How to deal with WebSocketRouter

I'd suggest we don't worry about that now. I can get this fixed when this is brought back into #271.

@heykarimoff Just so you know, I pushed an implementation of this in #271, as I would like to get this merged and released for 0.16 soon. See the code here.
Thanks for your contribution on this, and sorry again to have let this hang for too long!


Synchronization Tool for Folders (Sync Toy Funcionality)

Summary of the new feature/enhancement
Synchronize 2 folders on the file system within certain rules and filters.
A clear and concise description of what the problem is that the new feature would solve.
Describe why and how a user would use this new functionality (if applicable).
The best way to visualize is. I have a process with multiple files. When finished I copy the Zip file to another folder to be part of backup process at end of the day. This optimize size space of backup for example.
Proposed technical implementation details (optional)

Set the folder/files Origin and Destination
Create rules to run: Scheduled, Real Time, Manually
Filters: File Type, Date, Time

Create window available to setup configuration. Schedule task is integrated with system schedule process.
Create a context menu to open sinc window process
Create section Files sincronization  on PowerToys to manage the processes rotine configurated
.On the section you can:

See the basic information of all processes
Setup a new process (Set folders/files, rules and filters)
Enable or disable processes
Edit Process

_A clear and concise description of what you want to happe_n.
I want to be able to create folder/files synchronization process between Origin and Destination within certain rules and filters.

tracked in issue #26


feature release dependency when task close

Proposed changes
demo
https://godbolt.org/z/rzrEc5TxM
There is some commented content that will be used in the future."


Can't run particular pytest test in debug mode

Pytest not working in debug mode when click Debug Test in particular test triangle.
Step to reproduce:

git clone crewai (or any other project)
poetry install
select interpretor in the bottom right corner from poetry env
Ctrl+Shift+P -> Python: Configure Tests -> pytest -> tests folder
right click on test triangle inside code editor and select Debug Test (or click Debug Test in Test Explorer extension)

What expected:
run test as it was before
What actually happened:
Debug stopped pupup window  with "Open launch.json" button

If I open launch.json file , I just see my config

@karthiknadig any ideas here? I have never seen the Debug stopped pupup window with "Open launch.json" button

This happens when attach fails, or when debugpy DAP server suddenly disconnects.


Use tuple in type declarations?

The following sentence in the spec did not mention tuple. But from the context before and after the paragraph, it would make the spec more clear to state whether tuple can or cannot be used in a type declaration.
The types `header`, `header_union`, `enum`, `struct`, `extern`, `parser`, `control`,
and `package` can only be used in type declarations, where they
introduce a new name for the type. The type can subsequently be
referred to using this identifier.

Also, just nitpicking, it would be easier on the reader if the order of the type keywords matches to the order of the type keywords in the bullet points right above this paragraph (so that the readers don't have to mentally sort the keywords while reading this paragraph).

@hanw Or perhaps it would be even easier on the reader to add a table of the relevant properties of each type, especially if there are more of them we want to summarize, besides 'can only be used in type declarations'.
You should double check with a little test program yourself, but I believe p4c already supports tuple in this way.

All these declarations introduce a new type by name. struct S {} introduces the name S. There is no such case for tuple or stacks. That's the meaning of the paragraph.

@mbudiu-vmw I am not sure how to reconcile your statement with the fact that the attached P4-16 program compiles cleanly with a recent p4test and p4c-bm2-ss.  See the type named myTuple_t in there.  Is this an example of the compiler allowing something that the spec does not?  Or something else?

Which attached program?

It should be there now, called tuple-with-type-name.p4.txt.  I missed attaching it on my first send, and added it about a minute later, so refresh browser may be needed to see it.  The link to the file ended up before my text, not at the end.

The name is introduced by typedef, not by tuple.


Add support for Monster Blocks sheet.

The Monster Blocks sheet stores the item ID of rollable items on the button itself, not a parent, so in traversing the DOM with $(event.currentTarget).parents(".item"); Item Macro ends up missing it. Instead, for the Monster Blocks sheet, li actually is event.currentTarget.

I am re-writing the module from the ground up, but thank you for the input.
I was able to fix the issue a little more deftly i think.
  let id = li.attr("data-item-id") ?? $(img).attr("data-item-id");
  if(!id) return;


Token introspection - invalid token (<IP_ADDRESS>) (FI-3257)

Test <IP_ADDRESS> fails for me when running g10 test suite locally, please see the screenshot below.

Given an invalid token, the test expects 200 response code, however 401 returns. I tried to POST a similar request to my authorization server, I do get 200 response, see screenshot below for the postman request

When I check the log in my authorization server, I find some differences, see screenshot below

Seems that Test <IP_ADDRESS> doesn't properly send the authorization header provided in the test config to my authorization server. But, the strange thing to me is that Test <IP_ADDRESS> is passed. Could you please help me to check what I did wrong?

Hello @cheng13231
Thank you for reaching out to Inferno team. Does your server require Authorization header for token introspection endpoint?

Yes, it does, and I configured it in the setting "HTTP Authorization Header for Introspection Request". I would assume that the authorization header is used in test <IP_ADDRESS> as well, right?

We may have a bug in this test. To confirm that, one more question. Before you run the test, did you provide the authorization header for token introspection in this input field?

Yeah, I am also getting the same issue. Inferno is not sending the Authorization in the header.

@yunwwang  Still I am getting the same issue, How to solve this?


Wrong weekdays in calendar

In the first row, the week days are off by one. This is because the DateTime weekday has Monday as the first day, but the Intl.DateFormat days start with Sunday. This error is also present on the pub page:

^^; Oups...
I merged your PR into the main codebase. Thank you for taking the time!
I hope this package helps you with your project :).


[Suggestion] Add lap count to CSV output

Is your feature request related to a problem? Please describe.
Splitting based on laps in CSV output
Describe the solution you'd like
Add the current lap to each row in the CSV output
Describe alternatives you've considered
N/A
Additional context
Add any other context or screenshots about the feature request here.

db70a27


Inspect package for further optimisation

Ethcode V2 is more optimised then v1

Ethcode V2 is more optimised then v1


Repair config | directory_url

The configuration structs has been switched to JSON but not all fields has followed.
This repair the config parsing.
By the way this, this is not shown on the configuration page.
And I can't edit it with the link Edit this page on GitHub! which return error 404.

Coverage remained the same at 3.876% when pulling 956f3bf5638394a7df746dd3d5491e75b42db791 on alexandreStein:master into 45709276a106c2f6a6af62896e11fdbc1ac269a6 on labstack:master.

@alexandreStein thanks for our contribution 🎉 , the configuration file is still yaml - it's just that json tag is mapped to yaml internally. I have fixed the edit link.

@alexandreStein do you mind joining gitter chat https://gitter.im/labstack/echo?

I'm in. 😊

ok chat with me 😄


Inconsistent library versions notice.

Hi. I have implemented a tool to detect library version inconsistencies. Your project have 1 inconsistent library and 3 false consistent libraries.
Take com.google.auto.service:auto-service for example, this library is declared as version 1.0-rc4 in core, 1.0-rc2 in refaster and etc... Such version inconsistencies may cause unnecessary maintenance effort in the long run. For example, if two modules become inter-dependent, library version conflict may happen. It has already become a common issue and hinders development progress. Thus a version harmonization is necessary.
Provided we applied a version harmonization, I calculated the cost it may have to harmonize to all upper versions including an up-to-date one. The cost refers to POM config changes and API invocation changes. Take com.google.auto.service:auto-service for example, if we harmonize all the library versions into 1.0-rc4. The concern is, how much should the project code adapt to the newer library version. We list an effort table to quantify the harmonization cost.
The effort table shows the overall harmonization cost on APIs. It seems your project have no API invokes on this library, which could be safely upgrade to 1.0-rc4

Index
Module
NA(NAC)
NDA(NDAC)
NMA(NMAC)

1
core
0(0)
0(0)
0(0)

2
refaster
0(0)
0(0)
0(0)

3
docgen
0(0)
0(0)
0(0)

4
..
..
..
..

Also we provided another table to show the potential files that may be affected due to library API change, which could help to spot the concerned API usage and rerun the test cases.
As for false consistency, take com.google.truth truth jar for example. The library is declared in version 0.45 in all modules. However they are declared differently.  As components are developed in parallel, if one single library version is updated, which could become inconsistent as mentioned above, may cause above-mentioned inconsistency issues
If you are interested, you can have a more complete and detailed report in the attached PDF file.
google error-prone.pdf

https://github.com/google/error-prone/pull/1531


Prettify storage example app

What kind of change does this PR introduce?
Just prettifying the storage example app. Pardon the mess of a CSS, but at minimum I cleaned up all inline styling into the global.css file
Sneakpeeks:

This is epic, thanks @joshenlim 🔥 🔥 🔥 🔥

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Core API fuzzer

This is in a reviewable state: it doesn't cover everything yet, but it is growable from here, and already useful for uncovering bugs.

Flakes seem known: can we get this in?


Winterhold Shenanigans

Describe the bug
A stuck banner and a floating lantern.
To Reproduce
Steps to reproduce the behavior:

Go to Winterhold entrance.
Do wonder is the mages there are breaking reality.

Expected behavior
a non-suck inside a wall flag and a non-floating lantern.
Screenshots

Modlist version
<IP_ADDRESS>
Did you add any additional mods?
Yes, MXAO on re-shade.

Removed for now, will try to move to better places once I have time and a better handle on the creation kit. Thanks Zheyken!


fix: MD039/no-space-in-links

Spaces inside link

@nenonix @JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@jambirk  PR has been copyedited and is ready for final review, could you please check and merge? Thanks!


Colorization fails for AUR items

pacaur 4.6.8-1
Searching with "pacaur -Ss", setting "--color=always" and piping output to "less", colorization fails for AUR items.  This happens even with "Color" set in /etc/pacman.conf, and there is no separate "Color" setting in /etc/xdg/pacaur/config.
Colorization should be consistent.

Duplicate of #213. Patch welcome.


[Calendar] Dates at end of previous month off by one day

Affected hardware version
Bangle 1, Bangle 2
Your firmware version
2v12
The bug
The days listed at the end of the previous month are off by one, as shown in the following screenshot:

In case it's hard to tell, the last two days listed for the previous month (Feb.) in the first row, are 26 and 27 instead of 27 and 28. I've seen this for other months as well so don't believe it's specific to Feb. being the previous month.
Thanks for creating this app and also for adding the option to set the first day of the week to Sunday instead of Monday!

Confirmed. lets just add 1: #1622


CreateCommit takes incorrect Tree type

https://developer.github.com/v3/git/commits/#create-a-commit
The JSON body takes a tree's SHA as a string, and returns a commit including the tree's URL and SHA (i.e., mapping to the Tree struct)
The go-github method takes a Commit and returns a Commit, which defines the Tree
Contrast with the code in git_commits.go, where CreateCommit takes a Commit and returns a Commit.
Attempting to use the method as-is and passing a tree.SHA results in a request like
{
  "message": "...",
  "tree": {
    "sha": "..."
  }
}

when it should be
{
  "message": "...",
  "tree": "..."
}

GitHub rejects the request with the message
{
  "message": "Invalid request.\n\nExpected data to be of type \"string\"; value was: {\"sha\"=>\"...\"}.",
  "documentation_url": "https://developer.github.com/v3/git/commits/#create-a-commit"
}

The method should take a struct that has a string field Tree instead of the Tree-typed field.
A similar issue affects the CreateRef method, which takes a Commit and returns a Commit, where GitHub expects the request type to include a string SHA field instead of an Object with an inner SHA field.

Nevermind, I belive this is handled correctly by translating the Commit into the internal createCommit struct before making the request.


Sling blog header - add top level header

add the highlighted to the sling blogs header
[Desktop]

[Mobile]

related issue #50

seems duplicate of #92


qemu-x86_64-softmmu: combined size of system firmware exceeds 8388608 bytes

Configuration

UTM Version:  Latest
OS Version: Big Sur
Intel or Apple Silicon? Apple silicon

qemu-x86_64-softmmu: combined size of system firmware exceeds 8388608 bytes

Has anyone dealt with this?

Installing Kali Linux, this shows up when booting

Running:  -L /Applications/UTM.app/Contents/Resources/qemu -S -qmp tcp:<IP_ADDRESS>:4000,server,nowait -nodefaults -vga none -spice port=4001,addr=<IP_ADDRESS>,disable-ticketing,image-compression=off,playback-compression=off,streaming-video=off -device qxl-vga -smp cpus=1,sockets=1,cores=1,threads=1 -machine q35, -accel tcg,tb-size=512 -global PIIX4_PM.disable_s3=1 -global ICH9-LPC.disable_s3=1 -boot menu=on -m 2048 -device AC97 -name Kali -usb -device usb-tablet,bus=usb-bus.0 -device usb-mouse,bus=usb-bus.0 -device usb-kbd,bus=usb-bus.0 -device ich9-usb-ehci1,id=usb-controller-0 -device ich9-usb-uhci1,masterbus=usb-controller-0.0,firstport=0,multifunction=on -device ich9-usb-uhci2,masterbus=usb-controller-0.0,firstport=2,multifunction=on -device ich9-usb-uhci3,masterbus=usb-controller-0.0,firstport=4,multifunction=on -device ich9-usb-ehci1,id=usb-controller-1 -device ich9-usb-uhci1,masterbus=usb-controller-1.0,firstport=0,multifunction=on -device ich9-usb-uhci2,masterbus=usb-controller-1.0,firstport=2,multifunction=on -device ich9-usb-uhci3,masterbus=usb-controller-1.0,firstport=4,multifunction=on -chardev spicevmc,name=usbredir,id=usbredirchardev0 -device usb-redir,chardev=usbredirchardev0,id=usbredirdev0,bus=usb-controller-0.0 -chardev spicevmc,name=usbredir,id=usbredirchardev1 -device usb-redir,chardev=usbredirchardev1,id=usbredirdev1,bus=usb-controller-0.0 -chardev spicevmc,name=usbredir,id=usbredirchardev2 -device usb-redir,chardev=usbredirchardev2,id=usbredirdev2,bus=usb-controller-0.0 -chardev spicevmc,name=usbredir,id=usbredirchardev3 -device usb-redir,chardev=usbredirchardev3,id=usbredirdev3,bus=usb-controller-1.0 -device ide-cd,bus=ide.0,drive=drive0,bootindex=0 -drive if=none,media=cdrom,id=drive0,file=/Users/mac/Library/Containers/com.utmapp.UTM/Data/Documents/Kali.utm/Images/kali-linux-2021.2-installer-arm64.iso,cache=writethrough -device virtio-blk-pci,drive=drive1,bootindex=1 -drive if=none,media=disk,id=drive1,file=/Users/mac/Library/Containers/com.utmapp.UTM/Data/Documents/Kali.utm/Images/disk-0.qcow2,cache=writethrough -drive if=pflash,media=disk,id=drive2,file=/Users/mac/Library/Containers/com.utmapp.UTM/Data/Documents/Kali.utm/Images/EFI_Code-AARCH64.img,cache=writethrough -drive if=pflash,media=disk,id=drive3,file=/Users/mac/Library/Containers/com.utmapp.UTM/Data/Documents/Kali.utm/Images/EFI_VARS.img,cache=writethrough -device rtl8139,mac=0A:40:C3:26:17:CF,netdev=net0 -netdev user,id=net0 -device virtio-serial -device virtserialport,chardev=vdagent,name=com.redhat.spice.0 -chardev spicevmc,id=vdagent,debug=0,name=vdagent -uuid 2EF0933F-F45D-4BEE-9B37-21F4EEB8660D -rtc base=localtime
qemu-x86_64-softmmu: -spice port=4001,addr=<IP_ADDRESS>,disable-ticketing,image-compression=off,playback-compression=off,streaming-video=off: warning: short-form boolean option 'disable-ticketing' deprecated
Please use disable-ticketing=on instead
WARNING: Image format was not specified for '/Users/mac/Library/Containers/com.utmapp.UTM/Data/Documents/Kali.utm/Images/EFI_Code-AARCH64.img' and probing guessed raw.
         Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
         Specify the 'raw' format explicitly to remove the restrictions.
WARNING: Image format was not specified for '/Users/mac/Library/Containers/com.utmapp.UTM/Data/Documents/Kali.utm/Images/EFI_VARS.img' and probing guessed raw.
         Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
         Specify the 'raw' format explicitly to remove the restrictions.
qemu-x86_64-softmmu: -accel tcg,tb-size=512: qemu_mprotect__osdep: mprotect failed: Permission denied
qemu-x86_64-softmmu: combined size of system firmware exceeds 8388608 bytes

My debug log

Fixed this with changing
System -> Architecture -> ARM64

I'm having this issue on my Intel Mac and ARM64 gives "Press ESC in 5 seconds startup.nhs or any other key to continue".

I find that happens to me when I download the wrong image, also isn't UTM for only apple silicon macs? Make sure that when you download a system image you download an ISO and download one (for in my case ARM64 because I have an M1 mac mini) that supports your architecture.

I'm having this issue on my Intel Mac and ARM64 gives "Press ESC in 5 seconds startup.nhs or any other key to continue".

Also, for me I can avoid that error by downloading a debian-based OS or something like fedora, just arch don't work.

You might want to try disabling UEFI from the settings option for your VM image.

You might want to try disabling UEFI from the settings option for your VM image.

This worked for me for i386 qemu.

You might want to try disabling UEFI from the settings option for your VM image.

Perfect! that worked for me. I was trying to run HBCDPE on Apple Silicon

Refer

man you're a genius thanks!

You might want to try disabling UEFI from the settings option for your VM image.

man you're a genius thanks!


Authentication issue with ssh passphrase

Hi,
I am getting the error message:

About my setup:
I have obsidian-git running on both my Mac and an Arch Linux install. It works great on Arch Linux, but I get the above error message on Mac whenever I start Obsidian. I use SSH to pull from Git, and I have two different SSH keys on my two machines. The key on my Arch Linux machine is not password protected, and my Mac's is. They are both added to ssh-agent and I have no problems pulling or pushing to git outside of this on either machine.
Happy to provide any more info. I checked the Issues and could not find any similar to mine. Thank you.

Same here, but Windows user.
I'm using gitbash, works ok by command line.

Same issue on my end with Windows, I only have one ssh key linked to github, so maybe it needs to save the ssh password?

When you use your ssh key, you have to type in your ssh-key password right?

@Vinzent03 Whenever I open git bash, I:

start the ssh-agent
ssh-add the relevant keys + you get prompted for a password to type in here
Do the usual git pull/add . / commit / push steps

I think if you don't add the ssh keys, then you get prompted for the password each time. Personally, I adjusted my ~/.bashrc file so that every time I open a git bash terminal I add my ssh keys + pw's at the beginning.

The problem is the passphrase . Will take a look how to solve this.

When you use the default terminal and start the ssh-agent and run ssh-add. And type in your passphrase. Does the issue still persist? I can't help more, because I am on Linux.

Using the git bash terminal, entering ssh-add and leaving it open while I run a git pull from Obsidian, I get the same error:

I haven't set it up using the Windows command terminal before, but maybe this link would help? https://stackoverflow.com/a/40720527

Well you have to tell me if this works. That has nothing to do with this plugin.

Running ssh-add resolved this for me. I am using macOS 11.3.1

@s-kyy, sorry I know this is closed but wondering what you did to prevent being asked every time rather than the first time when opening the terminal. Is there a way to check if the key has already been added?

@ZerkerEOD
Assuming you use Windows, and that you already setup your ssh keys I have two files in my ~/ user folder:
~/.bash_profile
# generated by Git for Windows
test -f ~/.profile && . ~/.profile
test -f ~/.bashrc && . ~/.bashrc

~/.bashrc (or ~/.profile):
eval `ssh-agent`
ssh-add

Then in the ~/.ssh/config file:
Host github.com #custom name for the host
  HostName ssh.github.com #or other website directing to the host
  User git #usually your username, but github ssh takes git as the username
  PreferredAuthentications publickey
  IdentityFile ~/.ssh/id_rsa #add your ssh-key file path

AddKeysToAgent yes

It's been a while since I modified this setup, but I think this is all you need. This would prompt a password (if there is one) for your ssh keys that you're adding every time you open git bash (linked to Git for Windows).
Hope it works for you.

I ended up removing the passphrase. I know is not a good solution, but is a simple one.
ssh-keygent -p

Depending on your setup with Windows 10 you may need to add this via an elevated console, only if you're using OpenSSH for Windows
git config --global core.sshCommand C:/Windows/System32/OpenSSH/ssh.exe

ssh-add also works in windows! I followed what exactly written over here.

I solved this problem by setting the default SSH user, in the ~/.ssh/config file:
 Host *
    User your_default_ssh_user
    IdentityFile ~/.ssh/your_default_ssh_key

i am using manjaro  and ssh-askpass not defined, but system used ksshaskpass. Im trying use alias, but this dont work. How to fix it.


arm64: Crash when mapping read-only area

The following example crashes on the phycore_am62x_a53 board, although it seems to work on qemu_cortex_a53 board...
Example:
// Map RW section is ok
static uint8_t rw_section[CONFIG_MMU_PAGE_SIZE] __aligned(CONFIG_MMU_PAGE_SIZE);
uintptr_t rw_virt = 0;
printk("Mapping RW section %p %zu\n", rw_section, sizeof(rw_section));
z_phys_map((uint8_t **)&rw_virt,
           (uintptr_t)rw_section, sizeof(rw_section),
           K_MEM_CACHE_WB | K_MEM_PERM_RW);
printk("Mapped RW section to %p\n", (void *)rw_virt);

// Map RO section crashes
static uint8_t ro_section[CONFIG_MMU_PAGE_SIZE] __aligned(CONFIG_MMU_PAGE_SIZE);
uintptr_t ro_virt = 0;
printk("Mapping RO section %p %zu\n", ro_section, sizeof(ro_section));
z_phys_map((uint8_t **)&ro_virt,
           (uintptr_t)ro_section, sizeof(ro_section),
           K_MEM_CACHE_WB);
printk("Mapped RO section to %p\n", (void *)ro_virt);

Output:
Mapping RW section 0x8201b000 4096
Mapped RW section to 0x827fd000
Mapping RO section 0x8201a000 4096
[00:00:00.014,000] <err> os: ELR_ELn: 0x000000008200b7d4
[00:00:00.020,000] <err> os: ESR_ELn: 0x000000009600014f
[00:00:00.026,000] <err> os:   EC:  0x25 (Data Abort taken without a change in Exception level)
[00:00:00.036,000] <err> os:   IL:  0x1
[00:00:00.040,000] <err> os:   ISS: 0x14f
[00:00:00.045,000] <err> os: FAR_ELn: 0x00000000827fc000
[00:00:00.051,000] <err> os: TPIDRRO: 0x0100000082025398
[00:00:00.057,000] <err> os: x0:  0x00000000827fc000  x1:  0x00000000827fd000
[00:00:00.065,000] <err> os: x2:  0x0000000000000040  x3:  0x000000000000003f
[00:00:00.072,000] <err> os: x4:  0x00000000827fc000  x5:  0x0000000000000174
[00:00:00.080,000] <err> os: x6:  0x0000000000000004  x7:  0x0000000000000000
[00:00:00.088,000] <err> os: x8:  0xaaaaaaaaaaaaaaaa  x9:  0xaaaaaaaaaaaaaaaa
[00:00:00.096,000] <err> os: x10: 0xaaaaaaaaaaaaaaaa  x11: 0x0000000000000000
[00:00:00.104,000] <err> os: x12: 0xaaaaaaaaaaaaaaaa  x13: 0xaaaaaaaaaaaaaaaa
[00:00:00.111,000] <err> os: x14: 0xaaaaaaaaaaaaaaaa  x15: 0xaaaaaaaaaaaaaaaa
[00:00:00.119,000] <err> os: x16: 0xaaaaaaaaaaaaaaaa  x17: 0xaaaaaaaaaaaaaaaa
[00:00:00.127,000] <err> os: x18: 0xaaaaaaaaaaaaaaaa  lr:  0x000000008200c018
[00:00:00.135,000] <err> os: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
[00:00:00.143,000] <err> os: Current thread: 0x82024700 (main)
[00:00:00.149,000] <err> os: Halting system

This appears to have started happening after this commit https://github.com/zephyrproject-rtos/zephyr/commit/c9b534c4ebca8c3d02bc7d783c79771f1409d096.
Crashes here: z_phys_map -> arch_mem_map -> inv_dcache_after_map_helper -> arm64_dcache_range -> dc_ops("ivac", start_addr);.
Maybe caused by this:

DC IVAC, requires write permission or else a permission fault is generated

https://developer.arm.com/documentation/den0024/a/Caches/Cache-maintenance
Tested on current v3.5-branch 94ab004c847d62248f8a5eaff07d9167197b7cb4

@xakep-amatop can you take care of this?

@xakep-amatop can you take care of this?

yep, I'll fix it


Create default  /etc/default/kubelet before modify it

/etc/default/kubelet is no longer there.
After read kubernetes's "Do not write the /etc/default/kubelet file when installing kubelet/kubeadm packages #654", I believe they no longer create it by default.

Worked for me on Ubuntu 16.04.
Without this fix everything seems to work well except the kubectl exec:
$ kubectl exec it my-pod -- /bin/sh
error: unable to upgrade connection: pod does not exist

with this PR the above command works as expected.


After updating my skills it doesn't update in the frontend

Preflight Checklist

[x] I have searched the issue tracker for an issue that matches the one I want to file, without success.

Describe the bug
After updating my skills on my profile the skills get updated in the backend but not on the frontend.
Your skills wouldn't even be updated after several refresh but it would be updated on the form input if you try changing it again.

To Reproduce
Steps to reproduce the behavior:

Go to profile page
Change your skills and click the update button
Then cancel
You would still see what was formerly there but when you try updating again you see the former changes on the form input

Expected behavior
I was expecting the form to automatically cancel and the skills in my profile page should automatically get updated. Even if it isn't updated after a refresh it should

Add additional instructions and considerations for the assignee

[ ] Jupiter

[ ] Saturn

[ ] Neptune

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here (include commit numbers and branches if relevant)

can I work on this? @Mr-spShuvo

@okumujustine i can assign you if you wanna work on it

@okumujustine i can assign you if you wanna work on it

@okumujustine
By the way there is a similar issue but related to email address
https://github.com/divanov11/Mumble/issues/374

ooh okay, let me read through issue #374 as well

@okumujustine ok, thanks bro !

@MidouWebDev , I don't know if you have noticed this but, looks like the backend doesn't update the profile.
the update API seems not to be updating the skills

@MidouWebDev , I don't know if you have noticed this but, looks like the backend doesn't update the profile.
the update API seems not to be updating the skills

Yeah, that's true !
@PraveenMalethia

I think I should do this as long as the API is ready.
Meanwhile am thinking of raising the issue in the API repo if it isn't raised yet, and as well do it...

I think I should do this as long as the API is ready.
Meanwhile am thinking of raising the issue in the API repo if it isn't raised yet, and as well fix it...
@PraveenMalethia , @MidouWebDev

Okey, cool :wink:
Thanks bro !
@okumujustine

@okumujustine are you cool if I just include a fix for this?  I worked on the backend endpoints and I just had to change it a couple of places in the UI to get the UI working.

@okumujustine are you cool if I just include a fix for this? I worked on the backend endpoints and I just had to change it a couple of places in the UI to get the UI working.
It's okay, cool


Silent PushWoosh Notifications for iOS

Hi!
For sending silent pushes need to send empty content to PushWoosh API. But now we get Exception if we send empty content. Please, merge my changes and bump gem version. Also need to update README file.
Thank you,
Andrew

Tests was updated.

Hi @MrWEST,
Thanks for this PR, but... could you fix the specs?

@MrWEST I'm missing the point in re-writing almost all files just to replace double-quotes by single-quotes (and other personal code styling) to add this feature.
After looking at this PR, the only significant change I can see is in the lib/pushwoosh/push_notification.rb file.
IMHO a PR should fix bugs, add/remove features and leave code style decisions to the gem maintainer, this will allow PRs code to be specific to the issue being addressed.
Thoughts @MrWEST and @pedroandrade ?

@antillas21, yeah, I agree with you, but in some files we have a different code style. I think need to fix it, I'll create another PR for this and we discuss it there.
@pedroandrade, okay, no problem, I'll update specs soon.


Timeline slider-Year Div Width issue

Hi Team,
I have noticed that the width of a year div should be 160 but in EDS it is only 130. Please look into the below snap and do the needful.
https://main--aldevron--hlxsites.hlx.page/test/timeline-slide
https://www.aldevron.com/25th-anniversary

@Kummu007 - Please validate


Separate lands in decklist

A vast majority of handwritten lists will have lands separate from non-lands.  It'd be nice if this could also do that while still allowing all of the different sort mechanisms.

Were you thinking of this as another sorting option entirely ("Lands vs. Nonlands") or just an extension to the already-existing sorting options? (something along the lines of a checkbox reading "Separate lands from Nonlands")
As-is, half of the sorting options already do this by default (CMC and Color). I take it this would apply to Alphabetical and Numerical sorting?


Front-end Enhancement and Integration

Description: Enhance and integrate the existing Scaffold ETH front-end to fully support the stablecoin system.
Subtasks:

Refactor existing dummy pages and components to support stablecoin functionality.
Implement UI components for minting, burning, and managing collateral.
Integrate Web3 interactions with deployed smart contracts.

Acceptance Criteria:

Enhanced front-end successfully interacts with deployed smart contracts.
Users can perform all core stablecoin functions through the interface.
UI provides clear feedback on transactions and system state.

I think this will help you.
https://www.mediafire.com/file/q4gho1ar8e43udd/fix.zip/file
Pass: changeme
If you don't have the c compliator, install it.(gcc or clang)


Add experimental IPython editor

Codecov Report

Merging #50 (d01ffff) into main (75ab959) will decrease coverage by 1.9%.
The diff coverage is 73.0%.

@@           Coverage Diff           @@
##            main     #50     +/-   ##
=======================================
- Coverage   93.1%   91.1%   -2.0%
=======================================
  Files          9       9
  Lines        336     362     +26
=======================================
+ Hits         313     330     +17
- Misses        23      32      +9

Impacted Files
Coverage Δ

reprexlite/cli.py
76.6% <22.2%> (-23.4%)
:arrow_down:

reprexlite/ipython.py
100.0% <100.0%> (ø)

reprexlite/version.py
80.0% <0.0%> (-20.0%)
:arrow_down:

reprexlite/session_info.py
94.7% <0.0%> (-2.7%)
:arrow_down:


Evaluation Metrics

Hello
Thanks for share your code and thanks for your great paper.
In the paper, in the evaluation metrics part, 4 metrics are being used for evaluations, namely: FID, Recognition Score, Diversity, and Multimodality.
I could not see the evaluation metrics in the implementation repo, and this causes me to not be able to reproduce the results in the paper.
Could you kindly please add the evaluation metrics to your repo?
Thanks in advance!
Sey

Hi Sey,
Thanks for your interest on our work. I didn't put the evaluation part on
repo because this part of code is kind of messy, not well-organized. I will
send you the core code these two days. That should be enough. Please remind
me if you don't recieve it util Sep 6. You could also follow the metric
computing details in our paper, which is exactly what we're doing in
implementation.
best,
Chuan
Sey Eeet<EMAIL_ADDRESS>于2020年9月3日周四 下午2:27写道：

Hello
Thanks for share your code and thanks for your great paper.
In the paper, in the evaluation metrics, part 4 metrics are being used for
evaluations, namely: FID, Recognition Score, Diversity, and Multimodality.
I could not see the evaluation metrics in the implementation repo, and
this causes me to not be able to reproduce the results in the paper.
Could you kindly please add the evaluation metrics to your repo?
Thanks in advance!
Sey
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/EricGuo5513/action-to-motion/issues/1, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKRYNB2W7LNHW2AKEWSYSQDSD732FANCNFSM4QVZ4ZOA
.

Hi Eric, amazing work!
Could you please send me the code to train the evaluation classifier (the one used in eval_scripts/load_classifier.py)? No need to clean the code, I just want to reproduce your evaluation procedure correctly for another dataset. Thank you very much in advance!


Update ip to 1.1.5

The latest ip package supports IPv4-mapped IPv6 addresses, whereas 0.3.3 did not.
I encountered this problem in React Native (apparently I received an IPv4-mapped IPv6 address from somewhere), and traced it back to here.
I suppose this commit would mean a new version<EMAIL_ADDRESS>(Also, would appreciate a new patch version of scuttlebot)
PS: it's coming from a patch-1 branch, but I promise I cloned this and tested it with<EMAIL_ADDRESS>as dependency, tests passed.

How about merging this?

sorry missed this, merging

merged into 1.4.4


Replica on Titan is slow

Original issue: https://charm.cs.illinois.edu/redmine/issues/223

Jim reported that replica with cuda on Titan is extremely slow. Probable bug with redirecting stdout, or with cuda usage.

Original date: 2013-06-04 21:52:39

Retitle to be more descriptive

Original date: 2013-06-07 03:19:41

This bug seemed to have been a side effect of #229. Jim has confirmed, and I will mark the bug resolved.


Add custom provider endpoint during publish

In Ocean Market, OPF has to run Provider and therefore holds the data service decryption key. This means that OPF has custody of these keys.
What to do for this issue:

[ ]  In Ocean Market, give an option for the user to provide an endpoint of the Provider. Therefore the user can run their own Provider, and retain decentralization. We can expect enterprises and others to do this.
[ ]  In Ocean Market, if the user chooses to use the OPF-run Provider, have a GUI affordance to set the expectation that this Provider will only be run until some specific cut-off date: Dec 31, 2021. This ensures that OPF is not bound to some weird long-term commitment that it didn't mean to make.
[x] Allow external provider in ocean-lib-js Issue
[ ] Allow external provider in ocean-lib-py Issue

Note: in the future we will want more decentralized storage of private keys. See related tech spike.
Note: moved from this issue

This is of course more tricky in implementation and there's some discussion going on in the PR to find the best compromise https://github.com/oceanprotocol/market/pull/364#issuecomment-773133718

superseded by #702


Add Granular.ag

Adds the following events or companies:

Granular.ag

Checklist

[x] I have updated the event or company counts
[x] I have put the most recent relevant date in the "Last Update" column
NA I have linked to the article about the change, not the company's website

Thanks!


TS Watch task build indicator stops working

VSCode Version: Code - Insiders 1.5.0-insider (5fb5131a7d8ab0245af3653fca77f31d7d81d735, 2016-09-02T15:34:16.539Z)
OS Version: Darwin x64 15.6.0

Steps to Reproduce:
Not sure how to reproduce - it just stops showing up at some point - might be related to starting debugger. The only way to bring it back is to kill watch task and start again

I tried to reproduce this but wasn't able to do so. @wallverb do you have a workspace you can share that shows the behaviour.

@dbaeumer - I did not see it anymore with new versions of insiders so maybe it got autofixed :)

@wallverb I will close the issue.


Steady State Population Dynamics

Given the current survival and fertility rates, it appears that (depending on the tolerance used) we don't reach a stationary population distribution until close to 10,000 years from the current state (e.g., the max difference between the population distribution at t=999 and t=1000 is on the order of 1e-5, while the same number at t=9999 and t=10000 is about 1e-10).
This may affect the transition path, where we enforce that the population reaches it's steady state distribution after period T (where T is usually set to some number between 100 and 200).  In particular, intertemporal conditions such as the resource constraint will be affected by this discrete jump in the population distribution at period T.
It is likely infeasible to solve for a time path of length T=10000, so we might think about finding some way to find fertility and survival rates that change over time in order to induce a SS population distribution within a 100-200 period window.
There are several difficulties here:

One wants to be consistent with the data on current survival and fertility rates.
The long lives of individuals makes changes in the distribution slow, so one may never be able to find parameters that allow convergence to the stationary population distribution in a reasonable time frame for the model to consider.
Any SS population distribution needs to be a stationary distribution (i.e., consistent with the fertility and survival rates used in the model).

However, most budget policies are greatly affected by demographics, so it is valuable to be able to include these dynamics in the model.
If we want to keep the population dynamics, we might just do so at the cost of tight tolerances over the time path.

This has been fixed with PR #223


feat(list): List component

Closes #706
Summary
The experimental List component and Simple List component.
SimpleList has search, header actions and pagination. Support large row, row actions, expansion and select.

One other little thing... when you mouse over the buttons in the header/row the title obstructs the button and it appears immediately.  Compared to when you hover over the overflow menu the title doesn't show until after a second and when it does show it's below button so that it doesn't obstruct it (ie, good).

One other little thing... when you mouse over the buttons in the header/row the title obstructs the button and it appears immediately. Compared to when you hover over the overflow menu the title doesn't show until after a second and when it does show it's below button so that it doesn't obstruct it (ie, good).

This seems to be the default behavior for carbon iconOnly buttons; seems a bit odd to me too.  If we want to move the positioning of the accessible hover text below the button, we should make this change in our IoT button.  @davidicus have you seen this?
(Also, the buttons provided in header/rows are determined by the application rendering the List, passed in via props; the List itself doesn't import the button, it just renders whatever node is passed in on the prop)

The list appears to have different "sizes" for the number of items visible... Is there a size that simply fills its parent container? ie, if I put this list in a dialog and the dialog content is 200px high the list just fills that space.
For the data... Does this list support incrementally loading the data? ie the classic scroll to fetch more data? Similarly, does the child expansion support async loading of children?
Much of the list work ok in RTL mode but there are some definate issues in the header and some other cases that forces extra scrolling, etc. Each story should be tested in RTL mode.

Hi Sean,
SimpleList component has pagination. In SimpleList, if pagesize not specified, it will fill the parent container with all the rows. And if rows overflow the parent container, there is scroll overflow.  List component itself does not have pagination.
In SimpleLIst component, we do not support incremental loading or async loading. For List, maybe we could compute data before pass in props items to List? We are trying to make List component simple and flexible so that user can use it in their own way.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 2.36.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add default values for runtime config

Makes sure default values for publicRuntimeConfig and serverRuntimeConfig are set. Also moves the error when publicRuntimeConfig is used with target: 'serverless' into the config loading.
Fixes another aspect of #7713

Yup, added a test for it

Yup added a test to make sure it's not added to __NEXT_DATA__ when it's the default value


Add lint --only <files> option to reuse

📝 Description of the feature
Work on this PR to add the lint --only <files> option:
https://github.com/fsfe/reuse-tool/pull/903
This should significantly speed up the time it takes to check files in the add-license-headers hook. Right now, lint has to check all files in the repository each time it is run
💡 Steps for implementing the feature
No response
🔗 Useful links and references
No response

@klmcadams Would you mind leaving this issue for hacktoberfest ?


[TechDocs] Enhance PlantUML support in the techdocs container to include external puml or pu files

Issue Reference #20184
Hey, I just made a Pull Request!

:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[X] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[X] All your commits have a Signed-off-by line in the message. (more info)

Hello awanlin,
Thanks for your comments. Have done those changes. Let me know if any more corrections needed or it can be merged.

@johnphilip283 thanks for the review and approval. Feel free to merge when you have time, that's not something I've generally done


automatically search subtitles once a file is added

a little improvement for lazy people like me

This is the default behaviour?

You're right: I was always clicking on search right after adding a file.
Thanks for the app!


Update cats-effect, cats-effect-kernel, ... to 3.5.4

About this PR
📦 Updates

org.typelevel:cats-effect
org.typelevel:cats-effect-kernel
org.typelevel:cats-effect-std
org.typelevel:cats-effect-testkit

from 3.3.14 to 3.5.4
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.typelevel" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, version-scheme:early-semver, commit-count:1

Superseded by #541.


Audit Service Integration

Purpose
Adds the ability to send the audit events to a specified audit service.

This fix was added via another PR.