docs: Map stable RTD version to VERSION

When readthedocs requests to build the "stable" build, configure the
links into GitHub to search for the release version specified in the
root of the repository. This fixes the links for examples in the Cilium
github repository for the stable version of the docs, such as those used
in the kubernetes getting started guide.

This change is

test-docs-please

Unfortunately there'll be no way to test this properly with RTD until we release a stable version with this code, as RTD will only specify the version as "stable" when attempting to build a new "stable" page using a newly tagged release version from Github.


User/ole

:white_check_mark: Build TheIdServer 1.0.0-user-ole1-0182 completed (commit https://github.com/Aguafrommars/TheIdServer/commit/9375f324fb by @aguacongas)


install latest docker-compose

Hello, thanx for great image, but is possible to add latest docker-compose via pip? Because by default is outdated version. Every time I have to reinstall it manually...
Thank you! :)

Hello,
If you need the last stable docker-compose version (currently the 1.23.2) you can install it via the documented way :
$ sudo curl -L "https://github.com/docker/compose/releases/download/1.23.2/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose
$ sudo chmod +x /usr/local/bin/docker-compose

After this, you will need to start a new session and check the version again :
$ docker-compose --version
docker-compose version 1.23.2, build 1110ad01

But I agree, a last docker-compose version packaged with the docker image would be well appreciated !
Thank you :)


Strange, hard-to-debug behavior when selectedItem changes to undefined

downshift version: 2.1.4
node version: 8.11.3
npm (or yarn) version: Yarn 1.9.4

Relevant code or config
Note that the Downshift is controlled, but it can set itself to undefined, which I believe switches it to being uncontrolled. (NONE_OPTION is just a Symbol)
<Downshift
  selectedItem={selectedItem}
  onChange={newItem => onChange(newItem === NONE_OPTION ? undefined : newItem)}
>
  {({ getItemProps }) => (
    <div>
      <Item
        {...getItemProps({
          item: NONE_OPTION,
        })}
      >
        None
      </Item>
      {items.map(item => (
        <Item
          {...getItemProps({
            item,
          })}
          key={item}
        >
          {item}
        </Item>
      ))}
    </div>
  )}
</Downshift>

What you did and what happened:
Open the reproduction repository: https://codesandbox.io/s/w08on9y7nl

Click on the button ("Black")
The dropdown opens. Choose "None."
Click on the button ("Select an item ...") again
"Black" is still highlight in the dropdown. (expected: None should be highlighted)
Choosing "Black" closes the dropdown and otherwise does not change the state; the button still reads "Select an item..." (expected: the dropdown should close and "Black" should now be selected).

Reproduction repository:
https://codesandbox.io/s/w08on9y7nl
Problem description:
The flow of changing a selection to "None" and then not being able to change back to what was previously selected is surprising.
The problem can be worked around by making "none" translate to null instead of undefined, and maybe it's not reasonable to expect "undefined" to be an accepted value of selectedItem, but the current behavior is so bizarre that it took me a good few hours to figure out what was going on.
Suggested solution:
One or both of these options would solve the problem, I think:

Warn when switching between controlled and uncontrolled, like React itself does for input elements.
When switching from controlled to uncontrolled, also clear the selected item from the internal state so that it's not left over from when the component was controlled.

I think I'd prefer option 1! Thank you!
Could you make a pull request for it?

Sure! I'll start working on that.

Here's a PR for this: https://github.com/paypal/downshift/pull/568

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Menu (non mobile) checks for externalLink instead of checking the category type first

Description
The external link of a category should only be used, if its type is set accordingly.
Possible Solution
Adjust templates.

Hello,
Within our company roadmap and work capacity, we try to address each bug or improvement request but admit that not each one will be resolved. To continue our culture of honesty and openness, we are closing this issue to focus on our roadmap on behalf of all Shopware users.
If you feel like this issue is still impacting you, please create a new issue and let us know.
Thank you again for your valuable feedback.


Collapsed Sidebar for Firewall Rules

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[x] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[x] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Describe the bug
I have 27 interfaces/groups and Floating rules under the Firewall --> Rules; therefore, it may requires to scroll up/down depending the location of the interface from the list.
If the Sidebar is expanded, this is not an issue since I can scroll up and down. However, when the Sidebar is collapsed and going to Firewall --> Rules --> {some-interface}, some of the interfaces including the Foating option cannot be selected. I can only view the last 16 interfaces/groups.
My screen resolution is 1080p, and have not tried this issue on a much higher resolution TV or monitor since I do not have one.
To Reproduce
Steps to reproduce the behavior:

Collapse the sidebar
Go to 'Firewall --> Rules
The first half of the Rules list will not be visible and cannot be selected

Expected behavior
The admin should be able to see all the items under the Firewall/Rules even when the Sidebar is collapsed.
Describe alternatives you considered
N/A
Screenshots
Sreenshots.
N/A
If applicable, information from log files supporting your claim.
N/A
Add any other context about the problem here.
N/A
Software version used and hardware type if relevant, e.g.:
OPNsense 21.7.7 (amd64, OpenSSL)
Commit: 3f5165238

The sidebar is a bit limited in visible items, due to the lack of scrolling. Increasing the max number of items based on the size of the screen might be an option, but with a lot of interfaces there likely will always be a scenario where it just doesn't fit.
Marking this "help wanted" for now in case anyone would like to suggest some changes.

At first glance, I'm seeing a compounding of issues:

Menu rises up into the header and goes behind it (happens with dropdown/dropups as well).
Sub menu attaches to the top of the previous menu entry and initially goes down until it reaches the bottom of the screen, and if the bottom of the screen is reached, the menu changes and attaches to the bottom of the menu entry and goes up.
Menu doesn't stack horizontally when it doesn't fit vertically.

It doesn't appear to be a number limitation, but it's how the menu handles reaching the bottom of the screen. It's forcing it up and out of reach, which is why you only see the last end of the entries of the menu. I'd bet that the menu entries are there for all of the interfaces, and how the menu is rendered makes them inaccessible. The screen would have to be tall enough to exit the Rules menu button and extend down without hitting the bottom of the screen.
@AdSchellevis I think this is a little bit out of my depth, but I did take a look through the source and found some stuff in src/opnsense/www/js/opnsense_theme.js which was related to the side bar, but nothing there stood out to me as logic about what to do when the bottom of the screen is reached.
Also I was able to replicate this without having so many interfaces by adding a bunch of entries to a plugin Menu.xml, and then adjusting the bottom of the window using the Dev Tools panel. Around 21 entries is probably enough to get the menu to appear correctly without touching the bottom of the screen, and then adjusting the bottom higher, and viewing the menu again and it will push up off of the screen.

may be we can just limit level3 max-height and allow scroll? (like https://github.com/kulikov-a/core/commit/158999b1113c8f54d9100275b9547b55f28436a3 not tested)

@kulikov-a That's a good idea. I tried these changes, not with the opnsense theme, but with cicada theme. They didn't seem to have the desired affect. Something is still forcing the menu to drop up, and then go out of view. I did confirm that all of the menu items are there in the HTML, they just aren't in view.
I also noticed that scrolling moves the whole page, and isn't isolated to the menu itself. If the menu size can be limited to a portion of the screen height, and scrolling working on it (and not scrolling the page) that would be a good compromise.

Ok, so I kept poking at this, and I found where I think the dropup is occuring:
https://github.com/opnsense/core/blob/de3a021dd948c89c14cea2a49b07a9b4f0a2e227/src/opnsense/www/js/opnsense_theme.js#L65
Commenting that out prevents the dropup from occurring. It also prevents the dropup from occurring on all menus, so any that are near the bottom of the screen will continue to go down out of view, which is not ideal.
I also discovered that I was mistaken in that the changes didn't have the desired effect. I tried again in ui_devtools and it worked. I found that I just happened to try it under circumstances that make it appear not working. The issue is that sometimes the menu doesn't appear at all and that's what I saw. It has something to do with the number of items, and how tall the box should be (aka how tall the items are) with respect to the bottom of the screen. I'd venture a guess that with the height of the box limited to 40vh, the calculation for adjusting the menu to drop up then puts the entire menu out of view because (I'm guessing) that the calculation takes into account the height of the items in the box. I'm seeing margin-top adjusting to around -800 when the menu drops up, so it ends up being a menu limited to 40vh dropped up nearly the full height of the screen which would put it completely above the view.
It does work though, there would have to be some other adjustments and more testing to make sure it's reliable though.
Here's what it looks like:

@agh1467 i will take a look at the problem. I just can't say when I'll get to it. I have a lot to do at my job at the moment. but thanks for the input.

The first submenu is only folded down if there is enough space. If this is not the case, it folds up and if there is not enough space at the top, it moves the submenu down according to the number of entries that are above the visible area. This works great for the first submenu. But with the second submenu, pushing down doesn't work. I'll take a look.

@agh1467 @fichtner I think i fixed it. Ready for testing!

fix >> https://github.com/opnsense/core/pull/5556

i tested it and it works perfect for all submenues! no problem found!

https://github.com/opnsense/core/pull/5556 + https://github.com/opnsense/core/pull/5570 +https://github.com/opnsense/core/pull/5571


Mark getAdapterFor method of AdapterFactory public.

or it will not be able to be overridden.

 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.

Codecov Report

Merging #56 into master will not change coverage.
The diff coverage is 0%.

@@          Coverage Diff           @@
##           master     #56   +/-   ##
======================================
  Coverage    9.69%   9.69%
======================================
  Files          96      96
  Lines        4815    4815
======================================
  Hits          467     467
  Misses       4348    4348

Impacted Files
Coverage Δ

...pterSocket/Factory/ShadowsocksAdapterFactory.swift
0% <0%> (ø)
:white_check_mark:

src/Socket/AdapterSocket/SpeedAdapter.swift
0% <0%> (ø)
:white_check_mark:

...t/AdapterSocket/Factory/SOCKS5AdapterFactory.swift
0% <0%> (ø)
:white_check_mark:

src/Socket/AdapterSocket/AdapterSocket.swift
0% <0%> (ø)
:white_check_mark:

.../Socket/AdapterSocket/Factory/AdapterFactory.swift
0% <0%> (ø)
:white_check_mark:

...apterSocket/Factory/SecureHTTPAdapterFactory.swift
0% <0%> (ø)
:white_check_mark:

...t/AdapterSocket/Factory/RejectAdapterFactory.swift
0% <0%> (ø)
:white_check_mark:

...et/AdapterSocket/Factory/SpeedAdapterFactory.swift
0% <0%> (ø)
:white_check_mark:

...ket/AdapterSocket/Factory/HTTPAdapterFactory.swift
0% <0%> (ø)
:white_check_mark:

...AdapterSocket/Shadowsocks/ShadowsocksAdapter.swift
0% <0%> (ø)
:white_check_mark:

... and 1 more

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 713dbd5...e199a91. Read the comment docs.


Add rule to forbid usage of unknown globals

It would be a grate mechanism of early error detection and ability to control the usage of global scope in project

Sounds similar to http://eslint.org/docs/rules/no-undef
We released 3.0 recently! We also wrote a post about how 3.0 will be our last major release (since we are deprecating the project) and that we are merging with ESLint!
Thus we won't be working on any new features moving forward which includes new rules/options. We will continue to fix bugs and work on CST/better autofixing for current rules in the upcoming months both to help JSCS users and to gain experience that we can hopefully use in ESLint. But otherwise we both teams will be working on getting ESLint feature parity with JSCS and just a nice transition for our users.
I'm putting an orphaned label to note this issue isn't planned to be worked on, but might be a good contribution as a custom rule (not in JSCS core itself).
I would encourage anyone who wants the rule to try writing it themselves: I would either write a custom rule or submit an issue to ESLint and if accepted a PR. Otherwise a custom rule that won't be in core repo itself.
JSCS rules are also very similar to ESLint rules: here are some resources to get started:

Project-specific Lint Rules with ESLint
Creating Custom Rules for ESLint
Maintaining JavaScript Code Quality with ESLint


Custom metric example has errors.

In doc blocks repository is defined as string but is used as actual repository.
Also service definition example does not match actual class. Some constructor arguments are missing in service.

Looks like actual code in tests has the same problem.


[ClipboardPickle] Clarify wording of privacy delta against status quo

This is mostly a wording nitpick, but I think it's important to avoid confusion.
In the Security and Privacy Questionnaire for the clipboard pickle feature, there's this claim (emphasis added):

Currently copy-paste operation (ex. of plain text payloads) does expose highly sensitive PII such as SSN, DOB, passwords etc. and this feature doesn't expose anything new.

In the explainer, it mentions:

These custom formats may be less visible to the user compared to the plain-text format so it might still be possible to transfer PII data without the knowledge of the user.

It seems like this (less-visible or non-visible content transferred in a paste operation) would be transferred to the web app with this new API, whereas it wouldn't without this API (since content that's not plain text gets removed).
I think this delta only exists for the app -> web direction; for web -> app, the web app can intercept the copy event and call call Clipboard.write() if the web app is the active tab and incorporate content that wasn't in the user selection.
Anyways, I think it's not quite true to say that it "doesn't expose anything new", but that the risk (PII exposure, etc.) is comparable to status quo (or some better wording). I think it's probably not too likely that PII would be encoded in non-visible content, but some metadata that might be sensitive (like document date creation, edit history, or the geolocation information of images embedded in a portion of a document that's being pasted) may get transferred as part of a paste, depending on the particulars of the format in question. My understanding is the pickle format would be understood by the native app and web app, but otherwise the format is custom.
Perhaps user agents could help explain the potential for these risks (or even have more sophisticated logic to detect sensitive information and allow users to cancel such pastes), but I also understand the desire for simplicity and to avoid permission fatigue.
But for now, let's change the phrase "doesn't expose anything new" to be a bit more clear.

Hi, friendly ping?

@caraitto Sorry, totally forgot to respond to this post.

I think this delta only exists for the app -> web direction; for web -> app, the web app can intercept the copy event and call call Clipboard.write() if the web app is the active tab and incorporate content that wasn't in the user selection.

Currently it is possible via DataTransfer APIs as well which web authors can access in the copy/paste event handler. Only the default copy/paste command works off of the current selection.
I agree that "doesn't expose anything new" is not technically true, but also the risk is comparable to the DataTransfer APIs that expose unsanitized HTML content in the standard HTML format, which is separate from custom format, in that the native apps have to explicitly opt-in to read/write custom formats supported by the webapps.

I think it's probably not too likely that PII would be encoded in non-visible content, but some metadata that might be sensitive (like document date creation, edit history, or the geolocation information of images embedded in a portion of a document that's being pasted) may get transferred as part of a paste, depending on the particulars of the format in question. My understanding is the pickle format would be understood by the native app and web app, but otherwise the format is custom.

Yes, your understanding is correct.

But for now, let's change the phrase "doesn't expose anything new" to be a bit more clear.

Agree. I'll make the changes. Thanks!


remove addr:unit from Brazil addresses field

addr:unit is not common in Brazil addresses

Thanks @willemarcel :+1:, it does seem this is true:


Fixing crash and Issue 9

Fixes the Issue of upscaled images wich occurs if the partition algorithm assigns a single item to one row.
Incorporates a fix for a crash on [UICollectionView insertSections:] from Pull Request #24
It implements swipe in and out animations, when inserting or removing cells.

(Last one should be optional, but I didn't have time to implement that yet)

@graetzer Thanks for your PR. I am no longer maintaining this project. Would you mind if I just point people to your fork in the README?

Sure I think that's the best idea, if you don't want to test and merge the code.

Honestly it's been too long since I looked at this code, and I don't have the time to maintain it at the moment. I updated the REAME. Thanks again.


Add Tagline

Waiting on the text for it.

@msilski - Just wanted to ping you on this issue to remind you that we are waiting on text for a tag line.

I made this completely configurable. Tag line text is in config.json:tagLine and the link is in config.json:links.tagLine.
config.json:links.tagLine = "" (not clickable)

config.json:links.tagLine = "https://test.com" (clickable)

Thanks for the configurable tagline. Could you add a little bit of horizontal spacing between the title and tagline? Would it also be possible to italicize it - we'd like to see how that looks.
And Bert and I noticed that on small mobile/small screens, the tagline begins to disappear under the four-circle mini logo. Would it be possible to remove the tagline at small screens, force it to the next line, or whichever solution would be easiest for you? Thanks.

Something like this?

margin-left: 5px;
font-style: italic;

Nice catch on the smaller screens. I'll fix that.

That looks great. Let's go with that.

Sorry - Bert has a minor change on this one. He would like to align the base of the tagline with the base of the title, and slightly increase the font, like this:

Of course, this change adds an extra space between the tabs and the map. Either moving the tabs down or the map up would be fine. Can you make this CSS adjustment for the revised tagline?

Excellent. Looks great, and thanks for making the corresponding adjustment to the tabs/map.


x/pkgsite/cmd/frontend: no longer loads stdlib if go-proxy cannot parse fake stdlib module

What version of Go are you using (go version)?

$ go version
go version go1.20.2 linux/amd64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/net_home/alatter/.cache/go-build"
GOENV="/net_home/alatter/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/net_home/alatter/go/pkg/mod"
GONOPROXY="*."
GONOSUMDB="*."
GOOS="linux"
GOPATH="/net_home/alatter/go"
GOPRIVATE="*.epic.com"
GOPROXY=",direct"
GOROOT="/net_home/alatter/local/go1.20.2.linux-amd64"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/net_home/alatter/local/go1.20.2.linux-amd64/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.20.2"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/net_home/alatter/source/pkgsite/go.mod"
GOWORK=""
CGO_CFLAGS="-O2 -g"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-O2 -g"
CGO_FFLAGS="-O2 -g"
CGO_LDFLAGS="-O2 -g"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build1051915940=/tmp/go-build -gno-record-gcc-switches"

What did you do?
We run pkgsite and host it internally to provide documentation for our own packages. We run it in "direct" mode, and send it through our internal go-proxy (Athena), which has credentials to fetch our internal go-modules.
We run pkgsite with arguments like the following:
$ go run ./cmd/frontend -bypass_license_check -direct_proxy -proxy_url https://<redacted> -host :8080

After commit f159e616582641bdbeb2d6a0018ca4c8c472fbb5 we are no longer able to load godocs
for stdlib packages - for example, loading http://localhost:8080/io will return HTTP-500 with the following logs from pkgsite:
2023/09/26 15:11:41 Info: Listening on addr :8080
2023/09/26 15:11:46 Info: 0 /io map[requestType:request start]
2023/09/26 15:11:46 Info: FetchDataSource: fetching std@latest
2023/09/26 15:11:46 Info: FetchDataSource: fetched std@latest using *fetch.proxyModuleGetter in 226.3µs with error FetchModule("std", "latest"): proxy.Client.Info("std", "latest"): Client.readBody("std", "latest", "info"): Client.escapedURL("std", "latest", "info"): path: malformed module path "std": missing dot in first path element: invalid argument
2023/09/26 15:11:46 Error: serveUnitPage(ctx, w, r, ds, &{io std latest}): FetchDataSource.GetUnitMeta("io", "std", "latest"): FetchDataSource.findModule("io", "std", "latest"): FetchDataSource.getModule("std", "latest"): FetchModule("std", "latest"): proxy.Client.Info("std", "latest"): Client.readBody("std", "latest", "info"): Client.escapedURL("std", "latest", "info"): path: malformed module path "std": missing dot in first path element: invalid argument
2023/09/26 15:11:46 Info: 500 /io map[isRobot:false requestType:request end]

The error malformed module path "std": missing dot in first path element: invalid argument appears to be coming from
our go-proxy (Athena). It is objected to a module named std, which seems like a reasonable thing to object-to.
If I swap the order of the getters used in fetchdatasource.Options in the direct-mode branch of frontend startup everything seems to work for me:
	if *directProxy {
		sourceClient := source.NewClient(&http.Client{Transport: &ochttp.Transport{}, Timeout: 1 * time.Minute})
		ds := fetchdatasource.Options{
			Getters: []fetch.ModuleGetter{
				fetch.NewProxyModuleGetter(proxyClient, sourceClient), // <-- if I move this down one line my problem goes away
				fetch.NewStdlibZipModuleGetter(),
			},
			ProxyClientForLatest: proxyClient,
			BypassLicenseCheck:   *bypassLicenseCheck,
		}.New()
		dsg = func(context.Context) internal.DataSource { return ds }
	} else {

Bisect result:
f159e616582641bdbeb2d6a0018ca4c8c472fbb5 is the first bad commit
commit f159e616582641bdbeb2d6a0018ca4c8c472fbb5
Author: Michael Matloob<EMAIL_ADDRESS>Date:   Wed Jul 5 14:02:46 2023 -0400

    internal/fetch: add two stdlib getters

    This breaks out the behavior of getting the stdlib into its own
    getter, stdlibZipModuleGetter. Most (but not all) of the special cases
    in the fetch code for the stdlib are in the stdlibZipModuleGetter,
    which is installed on the frontend. For the local pkgsite command, we
    add a new builder for the goPackagesModuleGetter that loads the
    packages from the stdlib given a GOROOT. The stdlibZipModuleGetter is
    also installed for pkgsite in as a fallback if the
    goPackagesModuleGetter doesn't successfully fetch the stdlib module
    (I'm not sure if that's possible).

    Fixes #60114

    Change-Id: Ida6a5367343643cc337c6d05e0d40095f79ca9e5
    Reviewed-on: https://go-review.googlesource.com/c/pkgsite/+/507883
    Reviewed-by: Jamal Carvalho<EMAIL_ADDRESS>    TryBot-Result: Gopher Robot<EMAIL_ADDRESS>    Run-TryBot: Michael Matloob<EMAIL_ADDRESS>    kokoro-CI: kokoro<EMAIL_ADDRESS>

What did you expect to see?
What did you see instead?

If I swap the order of the getters used in fetchdatasource.Options in the direct-mode branch of frontend startup everything seems to work for me:

Hmm. I suspect that's a bug in the fetch.proxyModuleGetter. ./internal/fetchdatasource checks for derrors.NotFound to skip errors:
https://cs.opensource.google/go/x/pkgsite/+/master:internal/fetchdatasource/fetchdatasource.go;l=166-168;drc=14233af499055be3ba3fe6816af8e7d4a4efa9ad
Probably if a module with an invalid path is requested from fetch.proxyModuleGetter it should return an error for which errors.Is(err, derrors.NotFound) returns true.
@aslatter, want to send a fix?

Just to make sure I understand, you mean something like this?
diff --git a/internal/proxy/client.go b/internal/proxy/client.go
index 92adc32c..dec80330 100644
--- a/internal/proxy/client.go
+++ b/internal/proxy/client.go
@@ -175,7 +175,14 @@ func (c *Client) ZipSize(ctx context.Context, modulePath, resolvedVersion string
 }

 func (c *Client) EscapedURL(modulePath, requestedVersion, suffix string) (_ string, err error) {
-       defer derrors.WrapStack(&err, "Client.escapedURL(%q, %q, %q)", modulePath, requestedVersion, suffix)
+       defer func() {
+               // if we cannot correctly craft a URL for the request module, it's possible we are dealing with
+               // something we cannot proxy (i.e. stdlib).
+               //
+               // Pass-back "NotFound" so we keep searching.
+               err = fmt.Errorf("%w: %s", derrors.NotFound, err)
+               derrors.WrapStack(&err, "Client.escapedURL(%q, %q, %q)", modulePath, requestedVersion, suffix)
+       }()

        if suffix != "info" && suffix != "mod" && suffix != "zip" {
                return "", errors.New(`suffix must be "info", "mod" or "zip"`)

I can think of two options:

Special-case "std" inside the methods of the proxy-client, and directly return "NotFound" (at minimum in "info", but extending that to the other "getters" makes sense).
Special-case "std" inside "./internal/fetch", to skip module-getters which are not appropriate

Both of these feel kinda icky - (2) has a higher density of weird coupling of components, but (1) requires the proxy-client having to know about the "std" module.
My comment about flipping the order of the getters in the issue-description was not a serious suggestion - it was more describing what I'd done to diagnose things. But it doesn't seem worse than these options? Every module which is handled by the stdlib-getter can never be handled by the proxy-getter.

cc @jba

As far as I can tell this issue is a blocker for running in "direct proxy" mode. Any work-arounds would be appreciated (or guidance/advice for running in non-proxy mode).
I'd be happy to send a fix, but it seemed like the direction we wanted to take wasn't clear.

I'm not sure if this is related, but I can't get frontend to serve stdlib even in database mode (just get 404 responses). As far as I can tell, the database has to be populated with stdlib info, but that is only done by a worker, which only runs when frontend is hosted on GCP? I'm having a hard time understanding how this is all supposed to work.

I expect that's a different issue - in direct-proxy mode stdlib browsing works almost works if the request gets routed to the back-end for it. Once that happens the discovery/download happens on the fly, similar to proxy-discovered packages/modules.

Yea, I think I figured out that I need to run seeddb in order to populate the database with stdlib info. Unfortunately, when I run it, my PostgreSQL instance gets killed due to OOM error (with 32 GB of RAM). So this is sort of unrelated to direct-proxy mode, but I'm not sure why frontend doesn't just fetch stdlib the same as any other missing package when running with a database.


Azure Static Webapp step fails with upload timeout error

In the pipeline, the build passes but the static web app step fails with below error

The same issue is happening to us since yesterday evening:

I'm seeing the same issue as well.

Yeah, same issue here:

Hi, we are aware of an issue related to Static Web Apps deployments intermittently failing. We have identified a fix and are in the process of rolling it out. Deployments should now be going through more reliably.

Thanks @mishapos ! The deployments have started to stabilize on our end.

I am still intermittently seeing this issue, October 13, 2022. https://github.com/MaxWilson/POCDungeonDraw/actions/runs/3246742217

We are still experiencing this issue.


Remove Duplicate Footer and Update Links

Summary

Removed the duplicate footer section from the website.
Removed the Terms of Use and Privacy Policy links in the footer, as they are already included in the Quick Links section above.

Details

The footer now contains only the copyright notice for a cleaner layout.
This change enhances the user experience by eliminating redundancy.

Before and After

Before:

After:

Additional Notes

No functional changes were made to the site's behavior.

Resolve the conflicts in the mentioned files. Ensure you pull all the latest changes before pushing your feature/bug fixes to the main branch. After resolving the conflicts, please open a new PR for review.
Thank you!


fixed another typo

Docs Build status updates of commit 1015334:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Language/Reference/User-Interface-Help/name-statement.md
:white_check_mark:Succeeded
View

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


[bug][gui] New update notification broken

I just downloaded the 1.3.3 release. Specifically the windows jre-free version.
It claims there is a new version available, and clicking it takes me to the release I just downloaded. Might be a string compare issue? The About window says my version is 1.3.3-1 and the release is 1.3.3 (no suffix).

That is because our VersionComparator only splits at . and not at -. In such a case it tries to convert 3-1 to an integer and fails which ends up in a NuberFormatException that is interpreted as "there is an update".
@skylot I think  it is better not to catch the NuberFormatExeption, just let it pass so it ends up in error log.

What does the -1 suffix indicate in this situation? The other available 1.3.3 downloads do not include it. In a similar vein, earlier version of the windows no jre build do not include the suffix. It seems to be introduced with this release.

@cskwrd
I commit a fix to handle package version (number after a dash), so this should resolve issue.
I think re-upload of that release file is not really needed because this feature disabled by default now.
@jpstotz thanks! I apply both of your suggestions. And to be honest, I have no idea why I don't use only latest version :(

Thanks!

good


fix(container): allow the same port number with different protocols (#3508)

Backport
This will backport the following commits from k8s-28/main to k8s-27/main:

fix(container): allow the same port number with different protocols (#3508)

Questions ?
Please refer to the Backport tool documentation

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 3989

Questions ?
Please refer to the Backport tool documentation


Remove old scripts that are no longer in use.

I am using this pull-request to test the CI system.

@swift-ci Please test

@swift-ci Please test Linux

@shahmishal Is this how you request @swift-ci to test my commit?

@swift-ci Please test

Close enough. Merging.


Returning the status codes from TestLogin API

API /v1-auth/testlogin was always returning a 401, now returning the error
based status codes.
https://github.com/rancher/rancher/issues/9462

@prachidamle I recall seeing at "200" status in the error message when AD login failed for reasons other than a bad password.
Is that accurate and if so, is returning a 200 in the PR going to cause weirdness bc that is actually the HTTP code for a successful response.

LGTM


Update package dependencies, metadata, and scripts

update dependencies (including typescript -> 3.7.x)
fix license and repository entries
change "ci" script to "check" (since npm has a "ci" command already)

This updates to TypeScript 3.7.x as well, which has some nice features that I think we should take advantage of.  Most notably, please be aware of optional chaining and nullish coalescing.  See: https://www.typescriptlang.org/docs/handbook/release-notes/typescript-3-7.html
@ngfreiter, @kjmahalingam, @mint-thompson -- I would also like to change author to contributors and add all of your names and MITRE email addresses.  Please indicate if you are comfortable with that.  @jafeltra can add her name with her first pull request. ;-)

@cmoesel i am comfortable with having my name and MITRE email added to the contributors list.

@cmoesel I am comfortable with being added onto the list, in name and email.

@cmoesel I am also comfortable with having my name and email added to the list.

OK, I've added you all as contributors (in alphabetical order by last name)!  When it passes Travis, can you merge it, @kjmahalingam?


Cursor location after insert and quit

I noticed that after insert in DAG, the cursor stays at where it was.  It would be be convenient to move the cursor to the new added node.
After quitting, the DAG still exists, until it goes out of the scope. Is this an expected behaviour?

I noticed that after insert in DAG, the cursor stays at where it was. It would be be convenient to move the cursor to the new added node.

Good point - I think this was the behaviour mostly because I forgot to implement anything else.  I'll go through the cases individually...
Inserting siblings (i* and a*)
For i* and a*, I 100% agree - this should be the default behaviour (in fact, it is already the default for i*).
Do you want to fix a*? - I can make a good-first-issue for it or if you want to do it you can simply make a PR.  The current infrastructure for edits leaves some things to be desired about how easy it is to break things by moving the cursor at the wrong time (you have to move the cursor after the call to finish_edit, which is really counter-intuitive).
Inserting siblings (o*)
However, for o* there's the added complication of what the behaviour of adding a count should be.
For example, suppose I have simply an empty JSON array ([]), which I'm selecting.  Intuitively, I think I would expect 3ot to insert true three times into the array resulting in [true, true, true].  I'm not sure where the cursor should end up - I think either no movement or moving to the last thing you inserted would both be logical.
If the cursor doesn't move when o* is run, then the expected behaviour of 3ot is trivial since 3ot should be the same as ototot and inserting true 3 times manually will insert it as children of the cursor as expected.
If the cursor does move when o* is run, then the expected behaviour of 3ot is not what happens if you type ototot, since the first ot would move the cursor to the newly created true and all further insertions would fail.
However, moving the cursor differently in the case of counts is definitely not without precedent: in Vim, typing 3rX on [H]ello World (where [*] donates the cursor location) results in XX[X]lo World (the cursor has been moved forwards so that 3 different chars got replaced) - whereas typing rXrXrX would result in [X]ello World (the same character getting replaced three times because the cusor didn't move).
I think that in general we should try to avoid counts having different behaviours wherever possible, but in this case I think it's probably worth making an exception as not doing so is probably less intuitive.  @Kixunil, what do you reckon?

After quitting, the DAG still exists, until it goes out of the scope. Is this an expected behaviour?

I think so?  In Rust every variable exists until it goes out of scope so I'm not sure I understand the question (I may just be being silly, though).  At any rate, once the DAG has returned from its mainloop no further edits are possible so the DAG won't be modified.

Hmm, interesting. I guess making 3ot adding three times true to an array without adding any other feature would be mosrt practical. However, I could imagine someone wanting to create 3-deep array/object, so having a separate feature for it would make sense. One way to do it is to allow both 3ot and o3t and let them behave differently  (3dl and d3l are both accepted in vim and behave the same, I think this kind of divergence is reasonable). Not entirely sure which should be which but 3oa making 3-deep array and o3a appending 3 arrays feels more intuitive. We would have to prohibit numbers to identify node types but that doesn't sound like  bad thing.
You bring a good point about r and I think that this kind of inconsistency results in a more practical outcome. While I like consistency in general, it may not be the most important thing in the world. So 3ot inserting 3 times true and then moving cursor at the last inserted true would still make sense to me.

I can to fix this.

@Kixunil

Hmm, interesting. I guess making 3ot adding three times true to an array without adding any other feature would be mosrt practical. However, I could imagine someone wanting to create 3-deep array/object, so having a separate feature for it would make sense. One way to do it is to allow both 3ot and o3t and let them behave differently (3dl and d3l are both accepted in vim and behave the same, I think this kind of divergence is reasonable). Not entirely sure which should be which but 3oa making 3-deep array and o3a appending 3 arrays feels more intuitive.

I really like this - it fits very nicely with how English works: o3t = o(3t) should 'insert three trues' whereas 3oa = 3(oa) should '(insert an array) three times'.

We would have to prohibit numbers to identify node types but that doesn't sound like bad thing.

I think this would be useful to avoid confusion anyway - I think it would be nice to have things like + and * as node-type identifiers for standard expressions, but I think banning numbers is probably fine.

@stokhos

No need to make it good-first-issue, I can fix this.

Coooool!

I thought DAG should be invalid after quitting, but this seems trivial.

I think that the real issue is that Quit is an Action, and therefore has to be passed through DAG.  But DAG should not decide when Sapling should quit because that quitting requires returning from the mainloop of Editor (which is not DAG's responsibility).  I have a plan to do some bigger refactoring that will hopefully resolve this.

I have fixed a*.

Are you sure you've fixed a* in #56? I've tested it in master, and got the old behaviour.
Also, in #53 I've completely refactored how the code for DAG works, which will make your change really hard to merge in.  So you'll have to redo it - this is just one of those things with working on projects with small code and lots of big changes.

Are you sure you've fixed a* in #56? I've tested it in master, and got the old behaviour.
Also, in #53 I've completely refactored how the code for DAG works, which will make your change really hard to merge in. So you'll have to redo it - this is just one of those things with working on projects with small code and lots of big changes.

I guess I made a mistake when using git.
I will redo it .

I guess I made a mistake when using git.

This is very easily done - git is an amazing piece of software, but is objectively hard to learn. I recently found this article from Github which does a nice job of clearing up some of the more confusing bits of Git.

I will redo it.

Cool - none of the edit code for a* has actually changed very much - the only real difference is that moving the cursor during an edit doesn't cause everything to break.


link in readme.md is broken

Link http://stilldesign.co.nz/PhysX is broken in readme.md

Hi,
Was a DNS issue


Add master toleration and soft affinity

Towards https://github.com/giantswarm/giantswarm/issues/5344

This should do the trick but E2E fails with a tiller error:
{"caller":"github.com/giantswarm/chart-operator/integration/setup/setup.go:29","level":"error","message":"failed to install resources","stack":"[{/go/src/github.com/giantswarm/chart-operator/integration/setup/setup.go:66: } {/go/src/github.com/giantswarm/chart-operator/vendor/github.com/giantswarm/helmclient/helmclient.go:341: } {/go/src/github.com/giantswarm/chart-operator/vendor/github.com/giantswarm/helmclient/helmclient.go:317: } {/go/src/github.com/giantswarm/chart-operator/vendor/github.com/giantswarm/helmclient/helmclient.go:751: label selector: `app=helm,name=tiller` namespace: `giantswarm`} {tiller not found error}]","time":"2019-02-15T12:42:58.261042+00:00"}

Is this related or something known?

LGTM
Sadly the test is flakey. It fails intermittently and its always that error.

I tested this on ginger, after moving the toleration to the correct spec it behaves as expected:

chart-operator gets the taint
chart-operator is scheduled on master following the soft affinity


Question - please explain COMPONENT_ID and COMPONENT_NAME

json_logging.COMPONENT_ID and json_logging.COMPONENT_NAME seem to be mean't to be customized.  Is there a mechanism to read these from framework settings?  If not, how are these mean't to be used.

the value can be easily to override by assigned it value directly before init the logging. similar to ENABLE_JSON_LOGGING value:
https://github.com/thangbn/json-logging-python#21-non-web-application-log


Allow Offset in addition to ConstOffset for texture operations

As part of an upcoming Vulkan maintenance extension I'm developing CTS tests for, we want to allow using Offset in addition to ConstOffset for image operations. This was already possible for image gather operations, but not for others, and is mainly enforced by VUID-StandaloneSpirv-Offset-04663. There are other VUIDs affected by this but that's the main one. On the SPIR-V side there's no such restriction, so SPIR-V doesn't need any special capability nor a new extension to support this behavior.
This issue is related to the following glslang issue: https://github.com/KhronosGroup/glslang/issues/3765
CTS uses the validator from SPIRV-Tools by default in Debug mode, and the new tests were failing validation due to VUID-StandaloneSpirv-Offset-04663. I got the validator to stop emitting this validation error by commenting out a code block like this:
diff --git a/source/val/validate_image.cpp b/source/val/validate_image.cpp
index 04100dd7..8968e31b 100644
--- a/source/val/validate_image.cpp
+++ b/source/val/validate_image.cpp
@@ -454,6 +454,7 @@ spv_result_t ValidateImageOperands(ValidationState_t& _,
              << " components, but given " << offset_size;
     }

+#if 0
     if (!_.options()->before_hlsl_legalization &&
         spvIsVulkanEnv(_.context()->target_env)) {
       if (opcode != spv::Op::OpImageGather &&
@@ -466,6 +467,7 @@ spv_result_t ValidateImageOperands(ValidationState_t& _,
                   "OpImage*Gather operations";
       }
     }
+#endif
   }

   if (mask & uint32_t(spv::ImageOperandsMask::ConstOffsets)) {

In that code block, I see that if I enable the before_hlsl_legalization option I could also skip that check. CTS allows us to pass shader build options when creating shader programs. Currently there's no code to wire anything to a call to spvValidatorOptionsSetBeforeHlslLegalization, but it's easy to do so (we already have other stuff wired to other validator options). My doubt is if that's the right solution: if I enable such an option when compiling shaders for the new tests, am I also allowing other "undesirable" things in the validator? If, on Vulkan implementations that have the new maintenance extension feature enabled, this is going to be legal, should we simply remove the check from the validator for all shaders? What's the right approach here?
/cc @spencer-lunarg since the the layers also use the SPIR-V validator (right?) and this could affect a validation layers release based on the spec that will include the maintenance extension.

Alan will have the final word, but the right fix should be to change the vulkan environment check to reflect the change in the spec.  I don't know how the spec is changing, so I can't suggest the actual change.

I'll CC you and Alan in the internal Khronos spec MR so you have more context.

So looked into this now, we are simply moving what use to be a Vulkan env standalone validation rule to a runtime validation rule around a new feature bit.
I would personally purpose to just move this check (VUID 04663) from a spirv-val and move the check to Validation Layers (since it is already in a spvIsVulkanEnv(_.context()->target_env) wrapper anyway)
We could even do the transition now (can make the PR quickly if we agree for both repos), and when the maintenance extension is release, we update the Validation Layers to check against the new feature bit

I would personally purpose to just move this check (VUID 04663) from a spirv-val and move the check to Validation Layers (since it is already in a spvIsVulkanEnv(_.context()->target_env) wrapper anyway)

The maintenance extension is a change to the validation rules for Vulkan.
I would model it as a feature bit in ValidationState_t::Feature  See https://github.com/KhronosGroup/SPIRV-Tools/blob/02433568af277324e6d7fe4582b663f14165c563/source/val/validation_state.h#L67
Normally those would be turned on by a change in the environment; but there's no new Vulkan version so instead turn it on via a new method spvValidatorOptionsSet....  (see the example like spvValidatorOptionsSetRelaxBlockLayout)
cc: @alan-baker

Just as some info, in the validation layers https://github.com/KhronosGroup/Vulkan-ValidationLayers/blob/main/layers/utils/shader_utils.cpp#L131 we take the runtime Vulkan features and pass in make calls like SetRelaxBlockLayout, so we are very capable to adding this flow
My concern is most people I assume just want to run spirv-val --target-env ... and having to keep track of an increasing number of random flags that just allow/disallow a check seems like something that is better served in a runtime check than a command line tool


fix: VTT Cue Parsing On PlayStation 4

Addresses issue/4321

I've corrected and resubmitted CLA agreement again. Should be good now.


Added sdb_array_sort() and sdb_array_sort_num()

Second part of the split pull request #67. Completes #59.
Implemented sdb_array_sort and sdb_array_sort_num. Will add sdb_array_add_sorted later. @alvarofe can maybe already use these.

@radare as per the register discussion from #67. With those swap functions using register hints didn't produce a significant improvement. Compiler chose to use rbx, but poping and pushing it kind of cancelled out it's positive effect. And compiler ignored inline hint. Why not use optimization flags?

Thanks!

Yep, there are some articles that talk about not using compiler hints with modern compilers because they are just ignored to avoid human errors. But i'm not sure if we should go to for this kind of optimizations yet. There are still several places to optimize sdb, and i'll try to work on them before 1.0, but current priority right now is to fix the remaining tests market as broken. And add more tests.
The query syntax parser is quite ugly and i would like to rewrite it after 1.0, and probalby change the syntax, but i need to think more on this and discuss, so
Can you do the sdb_array_add_sorted() and num_sorted() functions too? in some situations is better to use sorted-adds instead of just adding them all in a shot and then sort.
Also, after 1.0 i have plans to split the API into different levels to cover backend, core, value abstractions (json, array, ranges, ..) and high level constructions (sdbtypes in C and with more complex types). This way i can stabilize and track the issues and design of each module independently and keep it open to support more helpers for working with complex data structures into sdb.


DPG should fix casing of parameters borrowed from OData

The Azure REST API Guidelines recommend standard query parameters borrowed from OData. Some of these parameters have names that contain multiple words but are all lowercase run together, e.g. "orderby", "maxpagesize".
For client libraries, we want these names to be exposed as multi-word names using the appropriate language idiom, e.g. "orderBy" in .NET.
Our DPG generators (autorest-based or Cadl-based) should ensure the correct transformation of the parameter names in the REST API to idiomatic form for the target language.

@archerzz @lirenhe the maxpagesize (or, better, maxPageSize) shouldn't even be exposed. See https://github.com/Azure/azure-sdk-for-net/issues/29342 for what the .NET architects requested. /cc @KrzysztofCwalina @tg-msft


output commands of extensions

Good afternoon, very useful extension, but unfortunately does not pull infarmation on other extensions, such as "ADetailer" and "ControlNet " . Can you add it?

It does pull information of extensions. It’s under alwayson_scripts.


Create a SciGraph dynamic template to replace GO taxon server

Input: (speciesTaxonomyClass, anyOntologyClass)
Return: true/false  (true if there is a violation)
This is essentially a path check, or a union of two path checks using

RO:0002160 ! only in taxon
RO:0002161 ! never in taxon

Composed with other OPs (to be specified)
The most elegant way to implement this would be a dynamic template - it is possible to use two variables, see http://datagraph.monarchinitiative.org/docs/#!/dynamic/get_evidence_for_a_pair_of_ids
We may also want to call this by direct JVM calls too
Note: should be assigned to @hdietze
Tester: @selewis (in PAINT)

Happy to test, but I should also commit the taxon lookup code (for
attempting to determine the correct NCBI taxon id). Not a dependency, but
be good to have both available. Later today I hope.
-S
On Thu, Jul 23, 2015 at 8:40 AM, Chris Mungall<EMAIL_ADDRESS>wrote:

Input: (speciesTaxonomyClass, anyOntologyClass)
Return: true/false
This is essentially a path check, or a union of two path checks using

RO:0002160 http://purl.obolibrary.org/obo/RO_0002160 ! only in
taxon
RO:0002162 http://purl.obolibrary.org/obo/RO_0002162 ! in taxon

Composed with other OPs (to be specified)
The most elegant way to implement this would be a dynamic template - it is
possible to use two variables, see
http://datagraph.monarchinitiative.org/docs/#!/dynamic/get_evidence_for_a_pair_of_ids
We may also want to call this by direct JVM calls too
Note: should be assigned to @hdietze https://github.com/hdietze
Tester: @selewis https://github.com/selewis (in PAINT)
—
Reply to this email directly or view it on GitHub
https://github.com/SciGraph/SciGraph/issues/140.

Note you can also do reconciliation using SG vocab services, e.g. http://geoffrey.crbs.ucsd.edu:9000/scigraph/vocabulary/term/mammals?limit=20&searchSynonyms=true&searchAbbreviations=false&searchAcronyms=false

Per @cmungall can test with:
http://geneontology.org/page/download-ontology#go-plus.owl

@cmungall Can you provide several test cases with concrete IRIs please?

Prefix: : <http://scigraph.io/>
Prefix: RO: <http://purl.obolibrary.org/obo/RO_>
Prefix: only_in_taxon: <http://purl.obolibrary.org/obo/RO_0002160>
Prefix: never_in_taxon: <http://purl.obolibrary.org/obo/RO_0002161>
Prefix: part_of: <http://purl.obolibrary.org/obo/BFO_0000050>

## Taxon test
Ontology: <http://scigraph.io/test.owl>

ObjectProperty: never_in_taxon:
ObjectProperty: only_in_taxon:
ObjectProperty: part_of:

## Taxonomy

Class: :animal
Class: :vertebrate SubClassOf: :animal
Class: :mammal SubClassOf: :vertebrate
Class: :mouse SubClassOf: :mammal
Class: :human SubClassOf: :mammal
Class: :bird SubClassOf: :vertebrate
Class: :chicken SubClassOf: :bird

## Ontology with taxon constraints

Class: :hair
  SubClassOf: only_in_taxon: some :mammal
Class: :whisker SubClassOf: :hair
  SubClassOf: never_in_taxon: some :human
Class: :tip_of_whisker SubClassOf: part_of: some :hair
Class: :hair_root SubClassOf: part_of: some :hair

## EXPECTED:
## R = [SubClassOf, part_of]
##
## violation(whisker, human) = true
## violation(whisker, mammal) = false
## violation(whisker, vertebrate) = false
## violation(whisker, chicken) = true
## violation(tip_of_whisker, human) = true
## violation(tip_of_whisker, mammal) = false
## violation(tip_of_whisker, mouse) = false
## violation(hair, chicken) = true
## violation(hair_root, chicken) = true
## violation(hair, bird) = true
## violation(hair_root, bird) = true
## violation(hair, vertebrate) = false
## violation(hair_root, vertebrate) = false

Implemented and added to the Monarch instance in the meantime.
Next is to deploy a GO SciGraph instance.


Unable to broadcast transaction

The era of the node and the tx do not match. The node is running in the Shelley era, but the transaction is for the Byron era.
Sent from PPHub

Can you provide the full cardano-cli command you're trying to execute?
As the error message states, this error is indicative of one attempting to submit a Byron transaction while in the Shelley era. Once in the Shelley era, you can only submit Shelley transactions.

Can you provide the full cardano-cli command you're trying to execute?
As the error message states, this error is indicative of one attempting to submit a Byron transaction while in the Shelley era. Once in the Shelley era, you can only submit Shelley transactions.

Thank you, I did rebuild Byron transactions, but I don't know the specific difference between Byron transactions and Shelley transactions. Is there any relevant code? No need for haskell, I'm not familiar

@vae520283995: You should probably look through our docs to get an idea of how to use cardano-cli in the Shelley era.

Closing this issue as the presented error message is indicative of cardano-cli behaving correctly.
If you run into any problems, feel free to reopen this issue or raise a new one.


size_in_bytes the same for all splits

Describe the bug
Hi, it looks like whenever you pull a dataset and get size_in_bytes, it returns the same size for all splits (and that size is the combined size of all splits). It seems like this shouldn't be the intended behavior since it is misleading. Here's an example:
>>> from datasets import load_dataset
>>> x = load_dataset("glue", "wnli")
Found cached dataset glue (/Users/breakend/.cache/huggingface/datasets/glue/wnli/1.0.0/dacbe3125aa31d7f70367a07a8a9e72a5a0bfeb5fc42e75c9db75b96da6053ad)
100%|██████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 3/3 [00:00<00:00, 1097.70it/s]
>>> x["train"].size_in_bytes
186159
>>> x["validation"].size_in_bytes
186159
>>> x["test"].size_in_bytes
186159
>>>

Steps to reproduce the bug
>>> from datasets import load_dataset
>>> x = load_dataset("glue", "wnli")
>>> x["train"].size_in_bytes
186159
>>> x["validation"].size_in_bytes
186159
>>> x["test"].size_in_bytes
186159

Expected behavior
The expected behavior is that it should return the separate sizes for all splits.
Environment info

datasets version: 2.7.1
Platform: macOS-12.5-arm64-arm-64bit
Python version: 3.10.8
PyArrow version: 10.0.1
Pandas version: 1.5.2

Hi @Breakend,
Indeed, the attribute size_in_bytes refers to the size of the entire dataset configuration, for all splits (size of downloaded files + Arrow files), not the specific split.
This is also the case for download_size (downloaded files) and dataset_size (Arrow files).
The size of the Arrow files for a specific split can be accessed: for the "test" split only
ds["train"].info.splits["test"].num_bytes

I agree this is confusing and maybe we should improve it.


"fabric_rpc:open_revs/3 error:undef" print stack

Description
We catch issue when on one node we can see error messages

[error] 2023-12-02T03:02:01.186324Z<EMAIL_ADDRESS><0.10897.1475> -------- rexi_server: from: couchdb@db0a.example.com(<17902.8977.1460>) mfa: fabric_rpc:all_docs/3 exit:timeout [{rexi,init_stream,1,[{file,"src/rexi.erl"},{line,300}]},{rexi,stream2,3,[{file,"src/rexi.erl"},{line,241}]},{fabric_rpc,view_cb,2,[{file,"src/fabric_rpc.erl"},{line,494}]},{couch_mrview,finish_fold,2,[{file,"src/couch_mrview.erl"},{line,672}]},{rexi_server,init_p,3,[{file,"src/rexi_server.erl"},{line,146}]}]

And on other node

[error] 2023-12-02T04:47:42.328226Z<EMAIL_ADDRESS><0.5507.1008> 2cabd72b84 rexi_server: from: couchdb@db0b.example.com(<17533.119.1516>) mfa: fabric_rpc:open_revs/3 error:undef [{fabric_rpc,open_revs,[<<"shards/80000000-ffffffff/account/dd/0f/7499dd7f62950b58fa2c375aef7a-202311.1698796829">>,[{{<<"202311-1261be79-d7ee-44d6-a3fe-671f733bc7c3">>,all},[]},{{<<"202311-117b562b-7257-4656-a414-57f646484eee">>,all},[]},{{<<"202311-117fb1dc-f20f-4469-a363-a8de609579da">>,all},[]} ....

Full error message in the attached file
couchdb-open_revs_3.log
Here call fabric_rpc:open_revs/3 contains big array of docs_id and do not allow print full stack.
Looks like error hapens after calling
curl -s -X POST \
        -H "Content-Type: application/json" \
        -d @/tmp/request_body.json \
        --output - \
        "${COUCHDB_URL}/${db}/_bulk_get?include_docs=true&attachments=true"

Where "request_body.json" contains about 1000 of docs_id.
Steps to Reproduce
Do not know
Expected Behaviour
Looks like something goes wrong in the couch_db:open_doc_revs/3 and function return not expected result.
https://github.com/apache/couchdb/blob/2af3cd811f5c714dc9f23320b797be54f6ed0f14/src/couch/src/couch_db.erl#L353-L363
I think required additional wraper function to catch errors and print stack without docs_id list.
Your Environment
Used  3 nodes cluster with apache/couchdb:3.3.2 docker image.
[root@ippbx-0b ~]# curl -s http://<IP_ADDRESS>:5984| jq
{
  "couchdb": "Welcome",
  "version": "3.3.2",
  "git_sha": "11a234070",
  "uuid": "3d809247857132201f34cd9ead11668f",
  "features": [
    "access-ready",
    "partitioned",
    "pluggable-storage-engines",
    "reshard",
    "scheduler"
  ],
  "vendor": {
    "name": "The Apache Software Foundation"
  }
}

CouchDB version used: 3.3.2
Browser name and version: do not used
Operating system and version: Linux CentOS 8 aarch64

Additional Context
NA

I have set docs_id array to one element in the my curl command and have rerproduced error.
Here is stack error

[error] 2023-12-02T05:57:21.583678Z<EMAIL_ADDRESS><0.19605.1025> 5ddaa614bb rexi_server: from: couchdb@db0b.example.com(<17533.26366.1526>) mfa: fabric_rpc:open_revs/3 error:undef [{fabric_rpc,open_revs,[<<"shards/00000000-7fffffff/account/33/0d/7bfd3f38d7b0e0f2bd6ec392f975-202311.1698796803">>,[{{<<"_design/resources">>,all},[]}],[{user_ctx,{user_ctx,<<"admin">>,[<<"_admin">>],<<"default">>}},attachments]],[]},{rexi_server,init_p,3,[{file,"src/rexi_server.erl"},{line,141}]}]

The fabric_rpc:all_docs/3 exit:timeout looks a fabric request timeout. Wonder if it would help to increase fabric request_timeout value a bit:
[fabric]
request_timeout = 60000

Maybe make that 90000 (90 sec).
This one mfa: fabric_rpc:open_revs/3 error:undef indicates one of the functions in the call is not defined at all. In this case the first candidate might be the the fabric_rpc:open_revs/3 function itself. That function is new in 3.3.2 so wonder if there is a possibility some of your nodes were upgraded and some were not , and some new nodes were dispatching requests to un-upgraded yet (old) <3.3.2 nodes.

yes, you are correct.
I found used wrong verions on the one node. Here on the two nodes used 3.3.2 and on the one node 3.2.1
Thank you for hint.
Closing.


Replace flag --goerli with --testnet

We define a general --testnet flag for the client that replaces the --goerli flag.
The flag determines the threshold network against which the client runs and is used to resolve Ethereum and Bitcoin networks.
After we added Bitcoin support the --goerli flag was confusing to use, as it relates to Ethereum only.
To run the client against the mainnet network no flag is required. To maintain backward compatibility the --mainnet flag remained available but it was marked as deprecated. We will remove the --mainnet flag in the future.
Refs: https://github.com/keep-network/keep-core/issues/3579

Let's remember about updating relevant parts of docs.threshold.network and infrastructure setup.

Yes, we track the remaining parts in https://github.com/keep-network/keep-core/issues/3579.
Docs were already updated in https://app.gitbook.com/o/R2meumXNNad4y1B10iL7/s/WosjlL4zUGUMlcMfuSAp/~/changes/216


raw_html and html code in the mhtml file are different from the html code of the real web page in the browser.

Hi, thank you very much for publishing the datasets and all of the hard work related to this!
I am trying to extract the original web page's ground-truth element and HTML code for a project, however, I found the HTML code from raw_html contains some extra "elements" compared to the original HTML code in the browser. For example, a target element in a raw_html is <span backend_node_id="137" bounding_box_rect="77,1708,112.203125,20" class="Pills__PillContents-sc-b74366a9-33 iqyJvU" data_pw_testid_buckeye="f3ae6144-2f6c-407a-b5c2-bcb9d069ad84"><text backend_node_id="2059" bounding_box_rect="77,1710,112.203125,16">Change Location</text></span>, but in the original HTML in the browser, the text content Change Location is directly contained in the <span> element. There is no such <text> element.
The HTML code in the mhtml file is also different from the HTML code shown in the browser, it contains some iframe elements that the original HTML code doesn't have, for example: <iframe __playwright_src__=3D"/snapshot/frame@f=.
I wonder whether there is a way to get the HTML code that is aligned with the HTML in the browser? I would appreciate it if you can shed a light on this. Thank you!

@holen-zhang Thanks for your interest in our work! This issue is similar to #27 . Hope this can be helpful to you.

Hi some of the observations that you had is not related to the processing and is as expected. Modern browser would construct/modify the HTML during rendering, and the <text> tags that you are seeing is one example, and similarly some other pseudo elements. When exporting the page as MHTML, the browser would want to save it follow general standard, and some elements that only appear during runtime will get dropped.
This is also why the html code in the data files and used in our experiments are processed from the dump of the DOM tree, as it contains retains more render information. You can also check Chrome Dev Tool specifications to see how you could dynamically obtain the web page state at runtime.
Hope this is helpful.


Remove 'RSpec' heading from code block

Aside from being unclear, this also seemed to be effecting the code block parsing for the remainder of the file (see screenshots below)

The hosted version:

My version previewed in YARD:

eek, this wasn't on a topic branch. sorry! doing that now.


utf8 encoding

hello, i have problem with encoding, when i try to export table to xsl spreadsheet. When i have in table words that contains ľčščžýá it replaces it with weird characters. I know it is an encoding issue. I also tried to set default parameter $.fn.tableExport.charset = "charset=utf-8"; but this didnt help me.

@zelo12000 – Can you please provide a link to the source or some context on the application environment in which you are implementing the plugin?
Often times, the issue can be remedied by adding the the js-xlsx dependency to your project, for example, if you have a basic static web project, then you can simply add the xlsx.core.js script to your project. Consult this reference. Let me know if the problem persists.

thanks a lot mate !
i moved xlsx.core.js BEFORE the FileSaver.js and now it is working.


Support BrowserStack in UI testing

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)

Proposed changes
In this pull request, I added code to execute UI testing on BrowserStack.
The discussion slides about the BrowserStack support are as follows (page 12-17).
https://github.com/node-red-hitachi/node-red-notes/blob/master/Meeting/20200127/02-Testing.pdf
[Procedures to execute UI testing]
(1) Set BrowserStack credentials to environment variables
BROWSERSTACK_USERNAME=<user name>
BROWSERSTACK_ACCESS_KEY=<accesss key>
(2) npm install
(3) scripts/install-ui-test-dependencies.sh
(4) grunt test-ui --browserstack
Checklist

[x] I have read the contribution guidelines
[ ] For non-bugfix PRs, I have discussed this change on the mailing list/slack team.
[x] I have run grunt to verify the unit tests pass
[ ] I have added suitable unit tests to cover the new/changed functionality

Can we make sure the instructions for using BrowserStack are added somewhere, such as the Wiki page? https://github.com/node-red/node-red/wiki/UI-testing

@knolleary Okay, I added the instructions into the Wiki page as follows.
https://github.com/node-red/node-red/wiki/UI-testing/_compare/c2c6208a8e89423afbb92d5edc8290547abfafb3


(Comment on this to vote) Let's create a Discord server (or else) for contributors to fast discussion and ideation

I think we need a fast-moving room for discussion with other contributors, and maybe there's a crazy idea that we could discuss or just get to know each other and be friends

Now I'm scared 😅
I'd like to mention some of our contributors to see if there's interest.
@Billboz @BigSpaces @matt-humphrey @Mraiih @threetriangles @SRFowler @waranlogesh @mvkvc @lgmfred @padmaJS @miguelbermudez @drueck @zorn @byronsalty @matt-humphrey @czrpb @IciaCarroBarallobre @paulo-valim @auranykh @crismxiex @aar2dee2 @TheGriffinCircus @aroojahmad

It could also be a channel on an existing server.

Down for another server but if everyone is already in DYA or Elixir Newbie maybe just create a collab text/voice channel that is open to everyone.

The DYA server would probably streamline it under one umbrella.  The only issue is for self-led like myself the server might need to be tweaked to allow both students and self-led on it.

I'm more in line with Cris, Marko and Williams's idea(s).

I agree, if we made a group I would make on the DYA Discord.
We could have a contributor role and contributor only chats. I'll also have to make some slight modifications so that student-only channels are protected.
It would also be interesting if we could get github integration on Discord 🤔

If you need any help with discord let me know

Not 100% percent sure what is being asked for. Chat spaces for discussion can work, though they lean on a more synchronous-style than I usually experience/prefer in open-source contributions. I would throw out GitHub Dicussions as a feature/space to talk about curriculum improvements or suggestions outside of PRs if you wanted to turn that on. 🤷♂
https://docs.github.com/en/discussions
Honestly, I'm not actively doing much work here, so do what you will with the suggestion.

Would we want to create some regular event(s) to get contributors together and plan some tasks? I can think of a few useful activities.

Regression Testing and tracking issues
working on tickets
planning tickets and reporting progress
helping first timers make PRs

Not 100% percent sure what is being asked for. Chat spaces for discussion can work, though they lean on a more synchronous-style than I usually experience/prefer in open-source contributions. I would throw out GitHub Dicussions as a feature/space to talk about curriculum improvements or suggestions outside of PRs if you wanted to turn that on. 🤷♂
https://docs.github.com/en/discussions
Honestly, I'm not actively doing much work here, so do what you will with the suggestion.

Very valid point and part of why I want to see if others do or don't want this. Open source is often a low pressure async activity and I like it that way.
Do other people think like they would really use a Discord chat for making contributions?

I think I'm with @zorn in trying to understand the value vs using the DYA existing Discord for comms. I'm happy to get involved in however this shakes out though. I'm with @BrooklinJazz in that I hope this ends up mostly low-key and async.

The easiest thing IMO is to create another text channel in DYA ex. #contrib for async and the existing Public channel for sync. I don't think it implies any commitment and people can drop in and out as they wish.

Awesome idea! I think linking this with DYA presents a great opportunity for us noobies to get started contributing with access to help/mentoring as we learn and I agree that a #contrib channel makes the most sense.

I'd love to contribute. I'd say definitely link it to DYA existing discord instead of making a completely new discord. Also While maybe using github discussions could be useful, I think more people are likely to have discord open or pay attention to chats there than relying on notifications from github. Worst case make a channel on the DYA discord and see how it shakes out? It costs nothing to make a channel.

Between the D&D level scheduling conflicts that would prevent real time contribution, the requirement that the curriculum remain somewhat static during an active cohort, and the lack of a real necessity to have large coordinated projects to rework Dockyard Academy I personally don't see a need for a dedicated space to facilitate high bandwidth discussion.

Jumping in here mostly to express interesting in contributing. But! I will echo others in saying that simply adding a dedicated channel to the existing DYA server makes most sense to me. Also: many folks may not be able to e.g. attend weekend meetups, so primarily asynchronous info exchange may be preferable...but it would be good to have a dedicated DYA contributor Voice Channel that people could log onto at any given time to discuss things with anybody else who happens to be online. This would be especially useful for early-stage developers.

An argument for having a DYA space is to incentivize and provide a place for support for new programmers to participate in contributing to the DYA curriculum and getting the general experience of working with shared repos.
Having a space for contributors to communicate about the steps of contribution, to debate on how to contribute to GitHub discussions, and about early thoughts on improving the curriculum seems enough to start one and see how it goes.
I think a DYA space for contributors is outside of GitHub discussions since it ideally would support and guide new programmers to use GitHub discussions properly and where useful.

Yes, I like to contribute

I'm in as well! =D

A bit late to the party but I'm interested! I don't have a lot of time to contribute at the moment but I'd love to help with new ideas and chip in where I can.

I’d also love to be involved :)

From: auranykh @.>
Sent: Friday, March 10, 2023 4:30:24 AM
To: DockYard-Academy/curriculum @.>
Cc: Matt Humphrey @.>; Mention @.>
Subject: Re: [DockYard-Academy/curriculum] (Comment on this to vote) Let's create a Discord server (or else) for contributors to fast discussion and ideation (Issue #860)
A bit late to the party but I'm interested! I don't have a lot of time to contribute at the moment but I'd love to help with new ideas and chip in where I can.
—
Reply to this email directly, view it on GitHubhttps://github.com/DockYard-Academy/curriculum/issues/860#issuecomment-1462737290, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AIHGZTJCCL22YGTYEPBF7YDW3I4WBANCNFSM6AAAAAAVN5A5XQ.
You are receiving this because you were mentioned.Message ID: @.***>

I'll be glad to help as well :)

Thank you all for your thoughts!
After hearing everyone's input, I've decided using the Elixir Newbie discord is best to start. You can join here:
https://discord.gg/kJSpkjhCb7 (link expires in 7 days - message me if you need another) See the #dya-contributors channel for the forum we'll use to organize discussions.
If this group is successful, we can consider moving it to the DYA Discord in the future.
We're going to run weekly sessions Sunday at 9 am PT in the General voice channel. I look forward to seeing you all there.


Universal font and other agreement issues

We need to all agree as a group on one font. Also I noticed that some people are changing things for the sake of changing things without adding anything meaningful to the site. I think we should agree not to mess with the styling sheet unless we are fixing formatting errors or doing something that actually contributes to the site instead of just slightly changing the values for padding and font size.

PRs are now required so this shouldn't happen again.

comic sans
On Mon, Nov 23, 2015 at 10:56 AM, johntheawesomeguy <
<EMAIL_ADDRESS>wrote:

We need to all agree as a group on one font. Also I noticed that some
people are changing things for the sake of changing things without adding
anything meaningful to the site. I think we should agree not to mess with
the styling sheet unless we are fixing formatting errors or doing something
that actually contributes to the site instead of just slightly changing the
values for padding and font size.
—
Reply to this email directly or view it on GitHub
https://github.com/mhsengineering/mhsengineering.github.io/issues/9.

--
Best Regards,
Loving Members of the Board
--
This email and any attached information (“email”) is confidential and
intended solely for the use of the individual or entity to whom they are
addressed in the body of the email. This email may contain information that
is privileged, confidential and prohibited from disclosure or unauthorized
use under applicable law.  If you are not the intended recipient or person
responsible for delivering this email to the intended recipient, you have
received this communication in error, and any review, use, disclosure,
dissemination, forwarding, printing, copying, distribution or taking any
action in reliance on this email is strictly prohibited.  If you have
received this email in error please immediately notify the system manager,
sender or the Morris School District by telephone or email and permanently
delete the original email and remove all copies from your system.


W3 logger

@dOrgJelli  General idea

Do we plan to support args with message (eg. (message: string, ...args: unknown[]) and let logger implementation handle args or just handle string message?
In issue it says  to log long running processes and sequential step processes. Do we plan to handle that on interface level
or let client modules handle message formatting and just log that string?

Changes:

add w3 logger function
change LogInfoAction to LogAction with log level
add optional logger param when instatiating web3 js client

Closes: #33

@mpetrun5 conflicts

Closing this one and starting fresh as mentioned above


Unit test failure: TernarySearchTree

I can't find the referenced file, but it happens in the TernarySearchTree unit tests:
  Map - /FIREFOX/
    ✓ LinkedMap - Simple
    ✓ LinkedMap - Touch Old one
    ✓ LinkedMap - Touch New one
    ✓ LinkedMap - Touch Old two
    ✓ LinkedMap - Touch New two
    ✓ LinkedMap - Touch Old from middle
    ✓ LinkedMap - Touch New from middle
    ✓ LinkedMap - basics
    ✓ LinkedMap - Iterators
    ✓ LinkedMap - LRU Cache simple
    ✓ LinkedMap - LRU Cache get
    ✓ LinkedMap - LRU Cache limit
    ✓ LinkedMap - LRU Cache limit with ratio
    ✓ LinkedMap - toJSON / fromJSON
    ✓ LinkedMap - delete Head and Tail
    ✓ LinkedMap - delete Head
    ✓ LinkedMap - delete Tail
    ✓ PathIterator
    ✓ URIIterator
    ✓ TernarySearchTree - set
    ✓ TernarySearchTree - findLongestMatch
    ✓ TernarySearchTree - basics
    ✓ TernarySearchTree - delete & cleanup
    ✓ TernarySearchTree (PathSegments) - basics
    ✓ TernarySearchTree - (AVL) set
    ✓ TernarySearchTree - (BST) delete
    ✓ TernarySearchTree - (AVL) delete
    ✓ TernarySearchTree: Cannot read property '1' of undefined #138284
    ✓ TernarySearchTree: Cannot read property '1' of undefined #138284 (simple)
2022-01-14T15:41:59.605Z pw:browser [pid=28105][err] JavaScript error: resource://activity-stream/lib/PersonalityProvider/PersonalityProvider.jsm, line 73: TypeError: / is not a valid URL.
2022-01-14T15:43:59.694Z pw:browser [pid=28105][err] JavaScript error: resource://activity-stream/lib/PersonalityProvider/PersonalityProvider.jsm, line 73: TypeError: / is not a valid URL.
2022-01-14T15:48:59.697Z pw:browser [pid=28105][err] JavaScript error: resource://activity-stream/lib/PersonalityProvider/PersonalityProvider.jsm, line 73: TypeError: / is not a valid URL.
2022-01-14T15:53:59.704Z pw:browser [pid=28105][err] JavaScript error: resource://activity-stream/lib/PersonalityProvider/PersonalityProvider.jsm, line 73: TypeError: / is not a valid URL.
##[error]The task has timed out.

##[error]The task has timed out.

Sure it is unit test failure and not something with the infrastructure?


UAT Round 2 | E-filing | Drafts not accessible

I am creating a case as a litigant and adding Complainant Details.
Post this, clicking on Save Draft.
Receiving confirmation message that draft has been saved successfully.
However, the Draft is not visible in the list of cases.
To Reproduce
Steps to reproduce the behavior:

Login as Litigant
Create Case
Add Complainant Details
Save Draft
Go to home page

For reference, created a case by user Complainant 1|  Mobile Number<PHONE_NUMBER> | Vijay Jonathan Srinivasan  and saved draft.
Cannot view Draft.
Expected behavior: Draft cases are visible in list of cases
Desktop (please complete the following information):

Browser: chrome
Device: Macbook

This issue is fixed and working as expected in UAT Env.

This is still not working @Amityadav012

working as expected


Cannot read property 'kind' of undefined

Hi,
I've tried to use this package but got following error:
cziken@cziken-ThinkPad-T540p:~/Documents/healthly/healthly-dev-docker/code/healthly-web-app$ ng add @lime.it/ng-dockerize

Skipping installation: Package already installed
✔ Packages installed successfully.
Cannot read property 'kind' of undefined

hadn't dig on the root cause yet, please let me know if you have any adivce on above.
cheers,

Hi can you please attach a repro of the issue? Or at least attach the angular.json file of your angular project, you appmodule and tell the version of angular you are using?


YCSB connects to zookeeper on port 2181 instead of the one configured in hbase-site.xml

Im using release 0.9.0 to run benchmark tests on a hbase cluster ( 1.1.2) using the below command
./bin/ycsb load hbase10 -P workloads/workloada -cp hbase/conf/ -p table=usertable -p columnfamily=cf -s
hbase/conf/ contains hbase-site.xml with the below contents
`

hbase.master
cluster3:60000

hbase.rootdir
hdfs://hdfs-mesos/hbase

hbase.cluster.distributed
true

hbase.zookeeper.quorum
zk1.service.local:2182,zk2.service.local:2182,zk3.service.local:2182

`
When I start YCSB the zookeeper client tries to connect to zookeeper instances on port 2181 instead of 2182 which is configured in hbase.zookeeper.quorum

2016-06-23 00:01:14,815 INFO  [Thread-3] zookeeper.ZooKeeper: Client environment:java.library.path=/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
2016-06-23 00:01:14,815 INFO  [Thread-3] zookeeper.ZooKeeper: Client environment:java.io.tmpdir=/tmp
2016-06-23 00:01:14,815 INFO  [Thread-3] zookeeper.ZooKeeper: Client environment:java.compiler=
2016-06-23 00:01:14,815 INFO  [Thread-3] zookeeper.ZooKeeper: Client environment:os.name=Linux
2016-06-23 00:01:14,816 INFO  [Thread-3] zookeeper.ZooKeeper: Client environment:os.arch=amd64
2016-06-23 00:01:14,816 INFO  [Thread-3] zookeeper.ZooKeeper: Client environment:os.version=3.10.0-229.20.1.el7.x86_64
2016-06-23 00:01:14,816 INFO  [Thread-3] zookeeper.ZooKeeper: Client environment:user.name=root
2016-06-23 00:01:14,816 INFO  [Thread-3] zookeeper.ZooKeeper: Client environment:user.home=/root
2016-06-23 00:01:14,816 INFO  [Thread-3] zookeeper.ZooKeeper: Client environment:user.dir=/home/cloud-user/ycsb-0.9.0
2016-06-23 00:01:14,817 INFO  [Thread-3] zookeeper.ZooKeeper: Initiating client connection, connectString=zk2.service.local:2181,zk1.service.local:2181,zk3.service.local:2181 sessionTimeout=90000 watcher=hconnection-0x4ae692db0x0, quorum=zk2.service.local:2181,zk1.service.local:2181,zk3.service.local:2181, baseZNode=/hbase

Ran YCSB on a separate host and it worked. Not clear why it failed on the 1st host

Can you confirm that the configuration files were the same on the first host and the separate host?

Yes. The difference between the 1st host and the separate host was that the 1st one was running the hbase master whereas the 2nd host was not running any hbase processes

@madhavshree Is this still an issue?

Closing due to no update.


Particles aren't up to date

Hey, is there any schedule for updating ParticleContainer to latest one?

Are you talking abt pixi-particles contributed by @halfabench https://github.com/pixijs/pixi-haxe/pull/28 ?

No this one https://github.com/pixijs/pixi-haxe/blob/dev/src/pixi/particles/ParticleContainer.hx which can't be used anymore.
Concerning the issue you mentionned, I see things into pixi/plugins/particles/cloudkid/AnimatedParticle.hx but they don't exist anymore? Cloudkit doesn't exist anymore in Pixi.js

Not sure what you mean. What's the issue with https://github.com/pixijs/pixi-haxe/blob/dev/src/pixi/particles/ParticleContainer.hx?
It's used in bunnymark test.
https://github.com/pixijs/pixi-haxe/blob/dev/samples/src/bunnymark/Main.hx

Well indeed it works but it has less options than the new (official) plugin.
The new particle system comes with an editor https://github.com/pixijs/pixi-particles-editor so it would be nice to be able to use those files generated directly.
Do you add plugins to the externs?

pixi-particles is not here atm and of course, it can be added. I don't use particles and I can take a look when I get a chance. If you can contribute, I am fine with that as well.
There is a plugins folder which already has spine and dragon bones externs.


jsoncolor does not colorize elements that implement MarshalJSON

Currently, if an element implements MarshalJSON, jsoncolor will delegate the byte encoding to that method, and then use those returned bytes. Instead, we should allow the MarshalJSON method to return bytes, and then re-parse those into a v interface{}, which should then be passed to the usual jsoncolor funcs.

The same issue affected handling of RawMessage. The PR does handles colorization of both (in practice, the encodeJSONMarshaler gets the JSON bytes and delegates to encodeRawMessage), but with the unfortunate side-effect that keys can be re-ordered in the output.
A preferable solution would be an implementation of encodeRawMessage that decodes the raw tokens and then re-encodes (with indent/color) without marshaling into a map at any time (as the map will lose the key order). This is beyond scope though.


Feature: Support Conversational Memory with Amazon Bedrock

Support Conversational Memory with Amazon Bedrock. Opensearch Conversational Memory is in preview.

Added Conversations with Bedrock and Opensearch serverless


Feature Request - Implement type-safe of 'OnDestroy'

Please add type-safe of untilDestroyed or create new function something like 'untilComponentDestroyed'
export const untilComponentDestroyed = (componentInstance: OnDestroy) => untilDestroyed(componentInstance);
it's nice to use type checking right ?

It's easily wrapped anyway:
import { OnDestroy } from '@angular/core';
import { untilDestroyed } from 'ngx-take-until-destroy';

export function takeUntilDestroy (component: OnDestroy) {
  return untilDestroyed(component);
}


localeResolutionCallback returns twice, first null

localeResolutionCallback returns twice, once null and after the corect locale
2019-05-31 21:35:15.926735+0300 Runner[83951:12397738] flutter: null
2019-05-31 21:35:16.020703+0300 Runner[83951:12397738] flutter: en_US

[✓] Flutter (Channel dev, v1.6.6, on Mac OS X 10.14.4 18E226, locale en-RO)
• Flutter version 1.6.6 at /Users/cosinus/flutter
• Framework revision e1a784ae3f (3 days ago), 2019-05-28 21:53:03 -0700
• Engine revision 8dc3a4cde2
• Dart version 2.3.2 (build 2.3.2-dev.0.0 e3edfd36b2)
When using debug from visual code all works fine. Even from device(stopped debugging) I get this strange behaviour.
Also when running from XCode on device.

https://github.com/flutter/flutter/issues/24747
If this is the desired behaviour then I think the documentation should say something about this
https://flutter.dev/docs/development/accessibility-and-localization/internationalization#specifying-the-apps-supportedlocales-parameter

catch that with an if-clause if locale is null or not. Just a workaround

I think you need to use Builder class in order to preserver the context

@cosinus84 is it the same while using current flutter stable v1.9.1+hotfix.4?

Hi @cosinus84
This seems like it's fixed

Could everyone who still has this problem please file a new issue with the exact descriptions what happens, logs and the output of 'flutter doctor -v'  please.
All system setups can be slightly different so it's always better to open new issues and reference related issues.
Thank you

Thank you @TahaTesser, the project I was working is "live" no need for features so far. I am afraid to open and update things over there as the project will be full of blood as soon as I open it. :)


Displaying the No Items Found Message

Hello,
I would like to thanks first for such pagination directive.
I have one question

I want to display the message No Items Foundi if the user search is not available or say data.length==0.

Thank You.

Why not use ng-show/ng-hide?

Or ngIf (would probably require a wrapper element). I don't think that any special message should be part of the standard directive - but you can modify the existing one to suit your needs of course.

Okay Thank You so much. now its working for me.
On Sun, Jun 14, 2015 at 6:50 PM, Pawel Kozlowski<EMAIL_ADDRESS>wrote:

Or ngIf (would probably require a wrapper element). I don't think that
any special message should be part of the standard directive - but you can
modify the existing one to suit your needs of course.
—
Reply to this email directly or view it on GitHub
https://github.com/angular-ui/bootstrap/issues/3816#issuecomment-111826881
.

--
@Bahuguna Goyal


Missing saveSigningCondition function?

**Before reporting, I have already ***

checked LIT Protocol developer docs and/or the lit-js-sdk.
searched for other open issues.

Describe the bug
Currently I'm working with lit-js-sdk which I gather is v1 and wanted to check out v2 since the v1 will be deprecated sooner than later. In doing so, I can't seem to find the saveSigningCondition which is required for the JWT auth path.
1. Why do I need to call saveSigningCondition() before getSignedToken()? Shouldn’t the former just return a JWT?

The reason behind this separation is that saveSigningCondition() is a function that an admin/developer of a website will most likely call only once to set up the token-gating mechanism. The function getSignedToken() can then be called for every website visitor. You can view this as a 1-to-many relationship.

I do see a commit https://github.com/LIT-Protocol/js-sdk/commit/c262f044b5ea5a5e02fcf07eded5af2683d2fb54 adding it but I can't seem to find it now? (I'm still a newb at github it seems) but I'm pretty sure it's because packages/utils/src/lib/litNodeClient.ts doesn't exist on master anymore?
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
packages/utils/src/lib/litNodeClient.ts might need to be added back to master?
Screenshots
If applicable, add screenshots to help explain your problem.
Environment:

Lit SDK version (including the network (ie, "serrano") if different, and type - browser or backend)
Node version
Framework (React, Vue, Angular, Svelte - just Plain HTML!, etc)
Specific tooling (Webpack, Vite, browserify, etc)

Additional info
Add any other context about the problem here.

Hey, it's here packages/lit-node-client/src/lib/lit-node-client.ts and not in packages/utils
https://github.com/LIT-Protocol/js-sdk/blob/master/packages/lit-node-client/src/lib/lit-node-client.ts#L1814
It should be working for you if you try to use it.  Are you still having issues?

I'm closing this thread, if not please let me know if you are still having issues


Is there anyway to invoke arbitary external cargo cmd, such as the cargo-auditable with cargo-zigbuild?

In cargo-quickinstall, we use cargo-auditable to build the crates to embed dependencies versions into the final binary so that it is auditable by crates like cargo-audit.
Currently, we creates a file called zig.sh which then calls cargo-zigbuild zig cc -- and specify it as the CC and -C linker
https://github.com/cargo-bins/cargo-quickinstall/pull/180 .
It would be great if we can directly call cargo-zigbuild with cargo-auditable, e.g. cargo-zigbuild auditable ...

I thought it should be cargo auditable zigbuild?

I thought it should be cargo auditable zigbuild?

We need to install the crates to CARGO_ROOT, zigbuild would only build the crate.

I don't know if it works now, but if cargo-auditable supports setting the CARGO env var, this might just work?
CARGO=cargo-zigbuild cargo auditable install

I think CARGO will be set by cargo when calling subcommands, so I don't think this would work as it would be overwritten by cargo.
And I think cargo doesn't have a CARGO_WRAPPER argument.
I think cargo-zigbuild could just export a few environment variables (CC, RUSTC_FLAGS) to call  wrapper of cargo-zigbuild?

What about CARGO=cargo-zigbuild cargo-auditable auditable install? it should bypass cargo.

And I think cargo doesn't have a CARGO_WRAPPER argument.

Yeah, it's just an idea that cargo-auditable could support.

I think cargo-zigbuild could just export a few environment variables (CC, RUSTC_FLAGS) to call wrapper of cargo-zigbuild?

I'm not totally sure what you mean by this, but pull requests are welcome!

I will have a try of setting cargo-zigbuild later and let you know the result

Looks like it works.

Thanks!
I've tried it on my laptop and it indeed works!


Some blocks look very bad when converted to external inputs

There must be a more compact way to render that, right?

Never mind, it's functions like translated and colored that look bad.

Conversely, case and list comprehension blocks are in need of some extra punctuation when converted to inline styles.

It significantly improved matters to make standardFunction from funblocks-client put inputs in the same field with the preceding punctuation.  I'd be very happier if the punctuation were right-aligned.
Unfortunately, not all blocks use standardFunction, so I'll also have to verify the remaining blocks to ensure that they aren't overusing dummy inputs, as well.


Remove oqc

Issue #, if available:
Prepare for offboarding OQC devices
Description of changes:
Remove all mentions and uses of OQC devices.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Can also remove those mocks now?

Can also remove those mocks now?

I believe that folder (and other mentioning of OQC in the test folder) has been removed in this PR. Could you please check again?


Fix clang compiler warnings.

Need this to fix Fedora CI check for https://github.com/apache/trafficserver/pull/8041 .

[approve ci autest]


AutoFit Zoom to window

Neither the NestMonitor nor Preview Auto-Fit functions are optimal. I have to admit the Canvas scaling/drawing was all new to me and I found it a bit obscure tbh, and nesting multiple instances in a List hasn't worked out ideal; but it's good enough for now.
The current functionality is based on Kevin Stumpf's "WPF simple zoom and drag support in a ScrollViewer" which can be found here on CodeProject.

This is fixed in my "development" branch on my fork if you're interested.

Yes, zoom routine should be fixed to maintain outer zooms.