Visual Boy Advance doesn't open the rom

I have a problem were the emulator doesn't open the rom with the patch and just says "Loaded battery" to then turn all white.
Any help?

The randomizer only seems to boot with mGBA, and not with VBA.

I'm having the exact same issue. The randomizer only seems to boot with mGBA, and not with VBA.

Which version?


Change Lato font to webfont (version 2.015)

This PR:

Adds additional formats (woff2, woff, eot) to the existing ttf format
The woff(2) files are about 25%-50% of the size of the ttf files, which decreases time to download
Supports modern browsers through woff(2), IE < 9 through eot, older Safari/Android through ttf. Unused font files are not downloaded by the browser.
Updates Lato to the latest official release from latofonts.com
Does not check for local installs of Lato. This can be added at the slight risk of making the font look different. Users with the font installed will not need to download the webfont.
Does not use character subsetting. Much smaller files are possible if only the Latin set is required
Makes the font look sliiiiighlty more squished vertically at the default size of 16px. This is true for any version of Lato I have tested, except for the ttf that the theme previously used. This is also present on readthedocs.org after rtfd/readthedocs.org#3982

Related: rtfd/readthedocs.org#3982, rtfd/readthedocs.org#3564, #524 and #642

Also, I believe these are slightly smaller than the ones we are using on .org. I will make a small PR to update the .org.

Also, I believe these are slightly smaller than the ones we are using on .org. I will make a small PR to update the .org.

You generated the woff(2) on .org from the original ttf right? The font files in this PR came from the original latofonts.com website.

Do we want to prefer a locally installed version of the font if available? This can save the download, although the version the user has installed may differ from what we use.

We could reduce bandwidth further by splitting each font file into a latin and one or more non-latin subsets. Browsers that view documentation that only uses latin characters will download the small font file. Other subsets will be downloaded as needed.
Since this requires some font file wrangling and a lot of testing, I prefer to not do that in this PR.


[bitwardenrs/speedtest] remove deprecated charts

Description of the change

These are been marked as deprecated, so removing them.
Checklist

[x] Chart version bumped in Chart.yaml according to semver.
[x] Title of the PR starts with chart name (e.g. [home-assistant])
[x] Variables are documented in the README.md (this can be done with using our helm-docs wrapper ./hack/gen-helm-docs.sh stable <chart>)

Merging.


ipq807x: fix dts for gl-ax1800

Signed-off-by: Jianhui Zhao<EMAIL_ADDRESS>

merged, Thanks !


NZBHydra v1 No Longer in Development, Can ATK be Updated for NZBHydra2?

New features
Can NZBHydra be replaced with NZBHydra2 in ATK? NZBHydrav1 is no longer in development and has been replaced with NZBHydra2 (which is awesome by the way)
The problem
See feature request
My Linux distribution and version is:
Ubuntu 16.04
I'm seeing this behaviour on:

Any install fresh or not

I'm not a dummy, so I've checked these!

I'm using the latest version of AtoMiC-ToolKit.
All my Linux distro packages are up to date and I don't see any errors while updating.
I've checked there are no current open issues relating to my problem!

New features are currently not being added to ATK. Please see the readme.


No such file or directory

hi, when I run_pose_training, I got the following error.
No such file or directory: '/home/u2/cosypose/local_data/bop_datasets/ycbv/index_train_pbr.feather
how can I get this file?
thx

solved from https://github.com/ylabbe/cosypose/issues/24#issuecomment-755430804


feat: td.TupleFrom() is td.Flatten() compliant

Pull Request Test Coverage Report for Build 703

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 99.789%

Totals

Change from base Build 700:
0.0%

Covered Lines:
6627

Relevant Lines:
6641

💛  - Coveralls


Increase visibility of test results

Is your feature request related to a problem? Please describe.
Our test matrix and test display should be improved.
Describe the solution you'd like
We want to increase visibility of tests:

Provide test matrix and make it visible to team.
Include test matrix review as part of DoD.

Describe alternatives you've considered
No.
Additional context
No.

IMO improved with output of tests on every pull.


Fluent syntax for arithmetic

Is it planned to have fluent syntax instead of arithmetic?
http://fuse-box.org/page/bundle#arithmetic-symbols
For instance instead of ">index.js" write .output("index.js")
Or "-remove.js" write .ignore("remove.js")
And so on

@NN--- not a priority ATM. We had some implementation by @aretecode
I think you can even use it.
https://github.com/fuse-box/fuse-box/blob/master/src/arithmetic/Fluent.ts#L124

IMO fluent is much nicer than arithmetic language.
It is also more maintainable and doesn't require writing any parsers.

@NN--- I agree, I have a plan for doing this sometime with the rest of the functionality, the fluent arithmetic should still work yup. Been working on this for the ultimate in fluent https://github.com/fluents/chain-able


First init module iteration

The init module should fulfill the following tasks:

Fetch parameters
Fetch config values
Define basic ui values
Fetch, check and distribute preset data
Sort sector markers to specific arrays
Initialize the save manager
Connect unlockable vehicles to military sectors
Load and save very basic data like date, sector ownership, FOB positions and unlockable vehicle sector links
Manage sector color changing
Manage FOB markers

Only a reupload of finished code with some smaller tweaks.


Release notes for 0.13.1, plus an update to the list of authors.

These notes assume that #1338 gets merged before the release. If it doesn't get merged, remove the mention of BlackrockIO.
Note that I added affiliations for new contributors where I could find them. If you see yourself in the author list and there's no affiliation given, please let us know in the comments if you'd like your affiliation to be added. If there's an error in your affiliation, please also let us know.

@apdavison can we wait for this https://github.com/NeuralEnsemble/python-neo/pull/1457 too?

sure. I was planning to make the release at the end of the afternoon tomorrow.

Perfect, both the PRs have tests passing. @samuelgarcia had mentioned that he was going to look at #1338 previously so not sure if he wants to give that a look-over before or not. I took a quick look at it and it seemed fine, but I'm not super familiar with BlackRock. #1457 should be ready for merge as well by tomorrow morning. So sounds good to me.
Release notes look good to me.

@zm711 : #1338 is OK for me. merci.

Thanks all!


don't ask for overwrite for the char device

/dev/videoX should always exists for the --muxer=v4l2, don't ask permission to override it. Fixes #140 .

@soreau please review

/dev/videoX should always exists for the --muxer=v4l2, don't ask permission to override it. Fixes #140 .

If this is the case, wouldn't it make better sense to check if the muxer is "v4l2"?

@soreau for that we probably need enum and validation of params and etc.
Logic that is implemented is more straightforward - ask for regular files, no sense to ask for the devices.
I don't know libav at all, but I would think there are more situation possible when -f isn't regular file.

@soreau for that we probably need enum and validation of params and etc.

My suggestion is to pass params.mutex to user_specified_overwrite() in addition to params.file here. Then in the function, you can check mutex == "v4l2" instead of checking if the file is a character device file. No need for an enum or anything.

Logic that is implemented is more straightforward - ask for regular files, no sense to ask for the devices.
I don't know libav at all, but I would think there are more situation possible when -f isn't regular file.

I don't know of other cases where you would be passing an irregular existing file type to wf-recorder.

@denisok Looking at this again, I think I agree with your original proposal (e.g. check whether it is a character device), not only whether the muxer is v4l2. I am also not aware of any other use-case, but there is nothing inherently special about v4l2.


Makefile, gitignore and MAINTAINERS improvements

I have improved the Makefile to result in reproducable builds, I have replaced the build date with the commit short SHA. I have also updated the list of maintainers and the gitignore to ignore coverage   output.

@tboerger this branch is out of date but LGTM

LGTM

LGTM


Doc: Beautify pipe code example slightly more

We intentionally didn't use any open Js.Array2 to keep topics isolated

While that may be off-putting to JS devs at first sight, usually we don't open the module before a pipe-chain since sometimes you have e.g. myArray->Array.map(doWhatever)->Map.String.fromArray->Map.String.... and then you immediately see that it is now a Map.String on which the operation continues.
Closing this now.


Remove debug log written with Console.WriteLine

The same log is already logged with the proper logging mechanism (which can be configured) 3 lines below.

Thanks!


Update active-directory-view-access-usage-reports.md

2 proposed changes:
1- Updated formatting. The previous formatting seemed untidy
2- Included scope of sign ins over which suspicious activity is detected

Hi @SSalahAhmed, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.azure.com.

TTYL, AZPRBOT;


Experiment work for MVP of Scratch Extension block

Fixes #2
Some inspiration for the code is taken from here. To test the code, do the following:

In the repo containing this code, run http-server. Check that http://localhost:8080/vizblocks.js exists.
Go to this page, https://sheeptester.github.io/scratch-gui/
Load the extension:

The new block should be visible in Scratch

However, it seems like unofficial extensions (what we are working on now) don't have access to the runtime, which is also discussed in this post.
Alternative options:

Find other ways to draw without using the runtime.
Work on a forked copy of Scratch GUI by making our extensions and registering the extensions in the forked codebase. However, we may need to explore ways to embed specific sections of Scratch in our own project as we do not want to redirect the user to a different page hosted on another domain.

Closing this issue as having access to the runtime is crucial for drawing things in the Renderer section. Work is continued here:

https://github.com/VisualizationLiteracyPlayground/scratch-gui/pull/1
https://github.com/VisualizationLiteracyPlayground/scratch-vm/pull/1


skip instruction does not skip long form of index register assignment

Consider the following example:
: main
   vc := 10
   vd := 10
   v0 := 0

   :breakpoint before
   if v0 == 0 then i := long data
   if v0 == 1 then i := long data
   :breakpoint after #CORRUPTED V0 HERE

   loop again

:org 0x7000
 0 1 2 3 4 5 6 7 8
: data
 0 1 2 3 4 5 6 7 8
 0 1 2 3 4 5 6 7 8

I think this is basically working 'as designed' since the 4XNN, 5XNN opcodes just increment the PC by 2 and i := long NNNN is 4-bytes.

Correct. It didn't seem wise to modify the semantics of existing opcodes to accommodate new (XO-Chip specific) instructions, even if it might be more convenient in some cases.

those instructions are called SKIP, and semantically it's a conditional predicate. Since long form of assignment was added in XO chip, I'd expect it to skip it properly.

It didn't seem wise to modify the semantics of existing opcodes

Was adding 0 height mode for sprite instruction such modification too? :)
It does not seem rational to me, since the only old code it could possibly break — someone deliberately put always true in skip condition and skip f0 00 invalid opcode in some old code just for fun.  I doubt it has been used anywhere.
Lack of consistency here leads to hard-to-catch errors, if addr is also valid instruction. :(

added error message for this
https://github.com/JohnEarnest/Octo/pull/69

After sleeping on this, I've changed my mind. I will modify the interpreter to make all six conditional skip instructions skip over a double-wide i := long NNNN. I can't think of any existing, valid programs it will break, and it makes the feature easier to use.

Thanks for bringing consistency here!


Plaintext IP endpoint

Plaintext IP endpoint would be really helpful especially in scripts.
$ curl http://httpbin.org/ip.txt --proxy $PROXY >> ips.txt

That should just be content negotiation, e.g., sending Accept: text/plain as a header but I'm not sure we actually want this. There are lots of other services that already do things like this.
Further you could use jq to select the origin attribute from the response and only print that out.

Sending headers via curl require more typing, and we all know shell is for getting things done fast. Installing addtional programs for this is overkill, in my opinion.

http://ifconfig.co/


Fixed error occurring with 'docker build'

What kind of change does this PR introduce?
Bug fix.
What is the current behavior?
Running the following command:
docker build -t <your username>/node-web-app .
Produces the following error:
npm ERR! missing script: clean
npm ERR! missing script: prebuild:prod
Other information:
Added clean command to package.json.
Replaced prebuild:prod build:prod commands with build:prod:aot in Dockerfile.
Changed entry point from server:prodto start:prod

Please merge this fix!

@storbukas thanks for your PR 👍

Wow - that was quick!
One other fix I needed to connect through docker was: --host <IP_ADDRESS>

Wow that was quick! One other fix I needed to successfully connect was: https://github.com/DanielAsher/ng2-admin/commit/006740b06b08ea66a47ea59e786c9de370cf29bc


Implement printing of build instructions

Should have button for printing of build instructions document.
See http://edutechwiki.unige.ch/en/CSS_for_print_tutorial and https://www.smashingmagazine.com/2013/03/tips-and-tricks-for-print-style-sheets/.

I have created a branch for this, print-instructions. Here I've added a preliminary style sheet for print purposes.


bytes, strings: add Clone

Working directly with []byte is very common and needing to copy it comes up fairly often. A Clone helper would be nice to have.
What did you expect to see?
dup := bytes.Clone(data)

What did you see instead?
dup := make([]byte, len(data))
copy(dup, data)

Implementation
package bytes

// Clone returns a copy of b
func Clone(b []byte) []byte {
  b2 := make([]byte, len(b))
  copy(b2, b)
  return b2
}

If accepted, Clone would probably be a more clear and matching name:
go1.txt:pkg html/template, method (*Template) Clone() (*Template, error)
go1.txt:pkg text/template, method (*Template) Clone() (*Template, error)
go1.8.txt:pkg crypto/tls, method (*Config) Clone() *Config
go1.13.txt:pkg net/http, method (Header) Clone() Header
go1.13.txt:pkg net/http, method (*Transport) Clone() *Transport
go1.13.txt:pkg net/http, method (*Request) Clone(context.Context) *Request

Copy makes it sounds like the built-in copy.

Would this be a better fit for the likely generic slices package, so it could work on any []T?

There is already a generic way to do it in one line.
b2 := append([]byte(nil), b...)

This is approach is even faster because the allocated slice will not be initialized to zero values.

@ulikunitz I think that's an argument for adding a bytes.Copy function. Most of the code I've seen uses the two step approach. A helper would probably result in more people using the faster approach.

@ulikunitz

b2 := append([]byte(nil), b...)

This approach is even faster because the allocated slice will not be initialized to zero values.

For simple cases like in the example code at the thread start (no complex computation in length argument) make + copy should be faster than append since go1.15: https://github.com/golang/go/issues/26252#issuecomment-495910025

I think that even with append() being available for this, a simple generic Clone() or Copy() function in a slices package that basically just wraps that would be worth it simply to avoid the need to match the type manually:
b2 := append([]byte(nil), b...)
// vs.
b2 := slices.Clone(b)

@DeedleFake
Yout don't need to write out the type []byte manually in an append call. Just do append(b[:0:0], b...). So personally, I think the append call is more graceful the slices.Clone call. The only drawback of append calls is that they might zero some redundant elements than so they are often a little slower than make+copy calls since Go toolchain 1.15 (as mentioned as @martisch above).

Just do append(b[:0:0], b...).

While that works, I think it's definitely confusing, especially if somebody else owns b (like io.Reader). I'd personally object to that in a code review.
That said, does this proposal also require strings.Copy? IIRC there has been some confusion both in the gophers slack and in GitHub issues about whether string([]byte(s)) will always make a copy of s.

@ericlagergren strings are immutable, there's no need to copy them.

There is need to copy them. For example:
s := "big long string"
x := s[:3]
// no more uses of s, but x is kept
// alive for a long time, pinning the
// entirety of s in memory until x is
// collected

In Go programming, there are many cases in which a small piece of a memory block is active prevents the whole memory block being released, not limited to slices and strings.

See #25834.

The append trick works well, but you have to have read the Go slices tricks wiki page to know to do it. If generics add a slices package, it would make sense to have slices.Copy[T any](s []T) []T as a function. That said, I don't think it makes any sense to add bytes.Copy today because we're so close to generics and the append trick works already.

This proposal has been added to the active column of the proposals project
and will now be reviewed at the weekly proposal review meetings.
— rsc for the proposal review group

It would be nice to get a sense of how widely used this idiom is. As it stands, a Clone() function saves almost no lines of code, and it's a new API which contributes to the system complexity of the STL. I think this can only be worthwhile if it is extremely widely used.

IMHO, a builtin merge function will have more use scenarios than clone.

Whatever we add here will need to be in strings too (forcing a copy, to address #40200) for symmetry.
And whatever we add here will probably need to go into the yet-undefined generic slices package, for symmetry.
So we need to get the name right for all three.
Copy is no good because this is different from the builtin copy.
Clone seems OK.
In some cases Clone means "deep clone" (like in http.Request).
In other cases Clone means "shallow clone" (like in tls.Config).
This would be a shallow clone.
Any objections to Clone?

bytes.Clone() sounds good to me. What would the point of strings.Clone() be? Decreasing the memory footprint of heavily substringed strings? That could be useful; just have to make sure that the documentation should be clear about the intent.
That being said, I don't think that it has to exist just because bytes.Clone() does. strings.Equal() doesn't.

What would the point of strings.Clone() be? Decreasing the memory footprint of heavily substringed strings?

I think that has benefit in itself. I occasionally see string([]byte(s)) in source code and it's not clear to me that the author was trying to re-allocate a smaller string from some other massive string. Seeing strings.Clone(s) communicates intent much more cleanly.

strings.Equal(a, b) would be exactly the same as a == b.  There is no way to write the equivalent of strings.Clone.  Even string([]byte(s)) is not the same, as the compiler could in principle optimize that away (and it might even be a useful optimization after inlinining).

That's fair. I just used strings.Equal() as an example of something that isn't duplicated from one to the other. bytes.Buffer isn't exactly duplicated, either, as strings.Builder has a different name and API for obvious reasons, and it didn't exist at all for quite a while. bytes.Replacer also doesn't exist.

@ericlagergren

There is need to copy them. For example:
s := "big long string"
x := s[:3]
// no more uses of s, but x is kept
// alive for a long time, keeping the
// entirety of s in memory until x is
// collected because the GC does not
// collect partial objects.

This has implications for things like string interning.

Currently string literals are stored in a read-only section. They're not collected and probably treated as globals by GC.
Slicing string literals references the same read-only section. This also doesn't affect GC.

So there's no need to copy strings in that case. You probably meant cases where strings are built at runtime?

@creker yes. Sorry, I should have been more exacting.

Based on the reactions to last week's comment, retitled to include bytes.Clone and strings.Clone, as in:
package bytes

// Clone returns a fresh copy of b.
// Specifically, the result is like b[0:len(b):cap(b)] but in a new backing array.
func Clone(b []byte) []byte

package strings

// Clone returns a fresh copy of s.
// It is equal to s but uses a new backing array for the memory.
func Clone(s string) string

I think the comments above that suggested either rejecting this due to the one line workaround, or punting this and reevaluating in a post generics world, seem like the best options. I don’t see any reason this needs to be added now, and I think a good argument has been made that this can be better solved in the future.

I'd like to see this proposal move forward.  As we bring on more inexperienced go developers into our team,  the bytes.Clone() and strings.Clone() would be more self explanatory.  I've had to explain more than once to people why I do the append trick; and have had to resort to always commenting on the line, making things more verbose than needed.

I think the comments above that suggested either rejecting this due to the one line workaround, or punting this and reevaluating in a post generics world, seem like the best options.

I'm here for strings.Clone and its intricate semantics described in https://github.com/golang/go/issues/45038#issuecomment-824224638. Would that behavior somehow carry over to a generics implementation? I expect it would not, so a string-specific function will have to exist somewhere.

Generics will not change that there is no documented way to clone a string and have guaranteed it does not share memory with the old string. https://github.com/golang/go/issues/40200
There are ways that work with specific versions of Go but there is no contract in language spec or API that prevents a future Go compiler to not share memory when copying a string.

I’m ok with strings.Clone, I think you’re all right that generics won’t help there. Personally I think bytes.Clone is better off delayed though.

Perhaps generics will add slices.Clone, but it would probably still be worth having bytes.Clone as well just to avoid an obvious hole in the bytes API. (We are not going to deprecate the entire bytes package even once the slices package exists.)

Based on the discussion above, this proposal seems like a likely accept.
— rsc for the proposal review group

No change in consensus, so accepted. 🎉
This issue now tracks the work of implementing the proposal.
— rsc for the proposal review group

Might be a bit late for this feedback, but why should this be called Clone and not Copy? It does make a copy of the whole string/slice (including the backing array).
It's telling that the documentation of the function uses the word 'copy' two times, but does not use the word 'clone'.
// Clone creates a clone of the string

would be meaningless, because nobody knows what a 'clone' means. But everyone knows what 'copy' means. It should really be called Copy.

@fjl the convention that seems to have developed is that functions named Copy copy data from a source to a dest and functions named Clone make a fresh duplicate of an object. This was also discussed in the very first comment at the top of this thread (the original proposal was in fact Copy, not Clone).

It's telling that the documentation of the function uses the word 'copy' two times, but does not use the word 'clone'.

It's generally considered poor form to define a word/term/function in terms of itself, especially if there's a good alternative at hand.

because nobody would know what 'clone' means without further reading.

I don't agree with this assessment. Cloning is a concept many are already familiar with from other domains, and as I mentioned it's a growing convention in the Go ecosystem as well.

It also doesn't help that the copy built in function does something different. Thus, using the term "copy" would probably lead to more confusion.

This came up in the implementation comments, but it might be worth raising here for a wider group:
What are the expectations around capacity? Naively, you’d think a clone would be the same ie cap(b) == cap(clone) should be an invariant, but maybe that’s bad if the cap contains some random extra space at true end. So do we just want to make no promises around the capacity? It seems like Hyrum’s Law means people will end up relying on cap(clone) == len(clone) if Clone works with a simple make and copy.

I'd expect Clone to avoid allocating more memory than necessary. I often clone a smaller slice of a larger buffer/string - assuming the original capacity is also intended for the clone is probably incorrect (and wasteful). Depending on the memory class used, it would be useful to leave the remainder as extra capacity.

An argument on the other side is that if you wanted the extra capacity cut off, you could call slices.Clone(slices.Trim(b)) instead. Having the same capacity in the clone gives the caller the flexibility to choose.

Retaining additional capacity negates the memory management benefits. And having to use Clone(p[:len(p):len(p)] defeats the purpose of having a dead-simple API.
Most of the time, I don’t care about a slice’s capacity. And when I do, it’s usually because I’m being lazy and appending to p := make([]T, 0, n). Only rarely do I need to explicitly use the capacity, in which case I won’t be reaching for Clone at all—I’ll explicitly use make and copy so that you don’t need to double check the docs to see whether Clone has the same capacity.

I think it's unlikely people will manually trim even if they should. It is better to make the API harder to inadvertently misuse.

There are at least 3 main ways to implement cap:

newcap = oldlen
newcap = nearest_as_large_allocation_class(oldlen)
newcap = oldcap

and given existing code there are use cases for each.
https://github.com/golang/go/issues/45038#issuecomment-824224638 used 1).

I believe that bytes.Clone should return a slice whose length and capacity are the same, and are the length of the input slice.  I think that is the most natural interpretation.  It is straightforward to get something else, and of course it is straightforward to never use bytes.Clone at all.  It is being created to correspond to strings.Clone, and I think the most natural correspondence is to copy the exact slice given as input, with no additional capacity.

Since there seems no consensus (yet) maybe a bytes.Clone should not exist for now similar to how no slice equality exist (should it include comparing the cap or not?).

Well there is https://pkg.go.dev/bytes#Equal which does not take the cap into account.

Looks like bytes.Clone didn't make it into 1.18. Considering a slices.Clone will be possible now, does it still make sense to move forward with a bytes.Clone?
@rsc

I agree. bytes.Clone basically only exists for parity with strings.Clone, but now there will be at least six months of development without it. Better never than late.

I dont think we need more CLs for bytes.Clone. One has existed since Oct 2021: https://go-review.googlesource.com/c/go/+/359675 but was not approved for merge in go1.18. If approvable it can now.

The two PR differs at that one returns nil for an empty slice, the other returns an empty slice instead.

Both Clone functions in CL 392194 and CL359675 when given a nil slice as input return a nil slice as ouput. Which is aligned with the behaviour of String.Clone.

Ah, yes, their behaviors are the same.

Which is aligned with the behaviour of String.Clone.

There is not nil strings, so this should be a slice specific detail.
Personally, I recommend to return an empty slice for an empty slice.

There is not nil strings, so this should be a slice specific detail.

There is no nil string but there is a string with length and backing array pointer of 0 which can not be compared differently but is different as header value from a string with length 0 and backing array pointer that is none 0.

Personally, I recommend to return an empty slice for an empty slice.
What should the backing array point of that empty slice be? If its the same as input it is not really a clone. If its a different one each time it requires an allocation.  When only returning nil for nil we only have that special case for nil.

Here's an example of the nil behaviour being confusing:
// You can edit this code!
// Click here and start typing.
package main

import (
	"encoding/json"
	"fmt"
)

func Clone(b []byte) []byte {
	if len(b) == 0 {
		return nil
	}
	c := make([]byte, len(b))
	copy(c, b)
	return c
}

func main() {
	b := []byte{}

	data, _ := json.Marshal(b)
	fmt.Println("Original:", string(data))

	data, _ = json.Marshal(Clone(b))
	fmt.Println("Cloned:  ", string(data))
}

https://go.dev/play/p/v-1dAVqDoGt

"No backing array is allocated." Its not possible to see the backing array pointer with cap function. Two slices can have cap 0 and different backing array pointers.
Make with 0 uses mallocgc which uses runtime.zerobase as backing array. Which makes the property of not reusing the backing array when cloning not true anymore even for non 0 backing array pointers.

I think the questions about nil and whether bytes.Clone should use the same cap, cap == len, or cap == size class point in the direction of just doing nothing. Cloning a string is tricky because you might think you did it correctly, but then the something about the runtime changes in Go N+1 and it isn't copied anymore. Having strings.Clone ensures that you won't get bitten after Go changes. bytes.Clone is just a convenient way to do something you could already do, but at the cost of being potentially misleading if the user has an incorrect expectation about the behavior.

Which makes the property of not reusing the backing array when cloning not true anymore even for non 0 backing array pointers.

Why does this matter?

Why does this matter?
Because thats what Clone in this proposal is supposed to be in contrast to a copy: https://github.com/golang/go/issues/45038#issuecomment-824224638

The reason to have a new backing array is that even a zero len and cap slice with a pointer into a memory allocation keeps that allocation from being garbage collected by the Go runtime. If that pointer is from a former large slice it may keep a huge amount of memory from being reused.
To avoid those references users can use strings.Clone and bytes.Clone to make sure there isnt more memory used by the slice then needed and the old memory is not reused.
So we want the new slice to have a different backing array, but we also want to avoid unnecessary allocations. Nil is already a language concept with a special name and the null pointer at any rate will exist often in a program. There is usually also nothing new allocated or written to what it points to. So its easy to carve out the one exception in documentation and behaviour to when the new slice will not have a new backing array and that is when passing in a nil slice.

@rsc @ianlancetaylor
Now that slices.Clone exists I propose to not implement bytes.Clone at all.
The slices.Clone seems rather a slice copy with the added property that the new cap can be larger/smaller than the old cap depending on the length of the input. But gives no explicit guarantees of not reusing memory. e.g. a 0 len, 0 cap slice might just be returned as is.
So we seem to have 3 options:

align bytes.Clone with the semantics of slices.Clone (efficient cap usage and nilness preserving) -> bad because its redundant and doesnt add new semantics and misaligns in subtle ways with strings.Clone
align with strings.Clone and always (except for nil) have new backing array -> misaligns semantics with slices.Clone
not add bytes.Clone to not misalign it with either strings.Clone or slices.Clone

@martisch yes, I understand what bytes.Clone is for ... I'm asking why it matters for empty slices with zerobase as the data pointer.

@martisch yes, I understand what bytes.Clone is for ... I'm asking why it matters for empty slices with zerobase as the data pointer.

Because Clone would not have the property of returning a new backing array for slices with zerobase as it is also returns the slice with zerobase again. That means the documentation needs to clarify that excemption to say that this isnt met when one passes in special slices with a backing array pointing to zerobase. But that is an implementation detail of the current runtime and it will be hard to comprehend for users what that means. It also means the runtime can not change in that regard without changing the semantics of the Clone function.
Instead giving the property that the excemption is only for nil slices is runtime independent and its easier to comprehend what slices this applies to as nilness is defined in the language and can be tested.

The slices.Clone docs don't mention any of that.
// Clone returns a copy of the slice.
// The elements are copied using assignment, so this is a shallow clone.
func Clone[S ~[]E, E any](s S) S {
	// Preserve nil in case it matters.
	if s == nil {
		return nil
	}
	return append(S([]E{}), s...)
}

It seems like we should still implement bytes.Clone, for parallelism with strings.Clone.
We want to keep package bytes and package strings as aligned as possible.
It's also worth noting that slices.Clone is in x/exp, not the standard library.
It also seems fine to me to have bytes.Clone([]byte{}) == []byte{} in the sense that both point at zerobase.

The slices.Clone docs don't mention any of that.

Because slices.Clone has different semantics than discussed here and does not guarantee a new backing array is returned. It also can return a different cap.
I updated https://go-review.googlesource.com/c/go/+/359675 but only mentioned for len and cap != 0 a new backing array is returned as for other slices it might be the same as I do not see how we can describe without mentioning and pinning runtime internals (which we likely dont want to expose or forever keep the same) for which ones.

@martisch do you plan on continuing work on https://go-review.googlesource.com/c/go/+/359675 ?

it is stupid。
Increased code complexity

@icetech233 On this issue tracker please follow the Go Community Code of Conduct.  Please be respectful.  Thanks.


11600 fix empty search 500

Fixes #11600
Please check the following:

[x] Do the tests still pass?[^1]
[x] Does the code comply with the style guide?

[x] Run make lint from the Wagtail root.

[x] For Python changes: Have you added tests to cover the new/fixed behaviour?
[ ] For front-end changes: Did you test on all of Wagtail’s supported environments?[^2]

[ ] Please list the exact browser and operating system versions you tested:
[ ] Please list which assistive technologies [^3] you tested:

[ ] For new features: Has the documentation been updated accordingly?

Please describe additional details for testing this change.
[^1]: Development Testing
[^2]: Browser and device support
[^3]: Accessibility Target

Thank you @krukas - can you please add a unit test that covers this fix, one that would fail without this fix. This is really important so that we don't have the same issue again in the future.

Thank you @krukas - can you please add a unit test that covers this fix, one that would fail without this fix. This is really important so that we don't have the same issue again in the future.

Hi @lb-, I have added a test and also change the logic to check for PlainText. Because it expects to have an PlainText query.

The code base on main is refactored en it looks like the bug is also present: https://github.com/wagtail/wagtail/blob/main/wagtail/search/backends/elasticsearch7.py#L1023-L1030
If this is approved create a new PR for main?

@krukas Yes, please create a PR for main. Generally we prefer to work by getting things fixed on main first, and then back-porting to stable branches as required. (In this case you've saved us a job by doing that step already - thanks!)

@gasman The PR for main: https://github.com/wagtail/wagtail/pull/11626

Closing in favour of new PR on main. https://github.com/wagtail/wagtail/pull/11626

@lb- I think it is better to keep this open in that we've deprecated a bunch of the old Elasticsearch backends for 6.0 so there's a bit of backport work to do, and this PR saves us the trouble for 5.2.x

No problems. Thanks for the info.

Closing as per https://github.com/wagtail/wagtail/pull/11626#issuecomment-1944161432 (so that we don't have multiple PRs needing the same fix).


Add Error Handling to Simulator

Problem
Currently when the simulator is running and the block-node server returns an onError message, the simulator just logs the message and continues as if nothing has happenend.
Solution
Stop the streaming simulator if an error is received.
Alternatives
No response

Will be handled in https://github.com/hashgraph/hedera-block-node/issues/315, closing this duplicate item.


Support aarch64

https://github.com/rbenv/ruby-build/blob/cf9a6fcdade04c6dbe04c476482b42f04f30b2a1/share/ruby-build/truffleruby%2Bgraalvm-21.2.0#L3
truffleruby+graalvm-21.2.0 supports aarch64, but ruby-build will try to fetch the amd64 binary if uname -s matches "Linux".

True, Linux aarch64 is supported now for TruffleRuby, I'll update the update script.

@joschl Could you try https://github.com/rbenv/ruby-build/pull/1788 ?


New version: VSCodium.VSCodium.Insiders version <IP_ADDRESS>64

Pull request has been automatically created using 🛫 WinGet Releaser.
Microsoft Reviewers: Open in CodeFlow

@wingetbot run

Hello,
I don't know what the error is...
winget validate --manifest <path> and winget install --manifest <path> are working without any error.

It installs fine.
It just fails security check in Azure DevOps which will be cleared up in a few days or so.
2022-09-21 18:52:53.465 [FAIL] Installer failed security check. Url: https://github.com/VSCodium/vscodium-insiders/releases/download/<IP_ADDRESS>64-insider/VSCodiumSetup-x64-<IP_ADDRESS>64-insider.exe Result: 0x80004005
``

@wingetbot run

@ItzLevvie Thx. Where did you get the error message? When I've looked at the logs in the Azure Pipeline, there were only the message "Failed"...

It's usually published in the artifacts of the run as "InstallationVerificationLogs" https://dev.azure.com/ms/winget-pkgs/_build/results?buildId=374375&view=artifacts&pathAsName=false&type=publishedArtifacts
but it looks like it got wiped for some reason.


service: changes in pytorch installation commands with pip

When running the command: dffml service dev install Pytorch installation fails and subsequently nothing gets setup on windows.
Python Version: 3.8.3
pip version: 20.2.4
Probable Cause: The install command for pytorch with pip has now changed, look at https://pytorch.org/get-started/locally/ for more info. The command has just changed for Windows so this issue is platform-specific.

We need to add -f https://download.pytorch.org/whl/torch_stable.html to the pip install command in dffml/service/dev.py within Install command, so long as model/pytorch is not in the list of plugins to skip.

@pdxjohnny Hello, can I take this issue as my good first issue?


Implement adding/editing blog post in yii-demo

Q
A

Is bugfix?
❌

New feature?
✔

Breaks BC?
❌

Fixed issues

Thanks!

btw., how about adding tags adding / editing as well?

btw., how about adding tags adding / editing as well?

https://trello.com/c/xkJxzzw2/113-implement-adding-editing-tags-in-yii-demo


Update engine to 1.14.17 (SNAPSHOT)

This is a snapshot of the upcoming 1.14.17 release. The modules will get another update, everything else should be stable.

The new modules have finally been released. This should allow using the TTS config file for /voices requests again.


When can we expect 0.3.1 to be on rubygems?

Will try to get it released by next week.
Cheers

Released v0.3.1 https://rubygems.org/gems/rich_text_renderer/versions/0.3.1


added an extra column named description

In case any description on hover of menu item to be provided.

Hello, Please send this to the asgardcms repository.


[TabScrollButton] Left, Right icons does not work as expected

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
The left, Right icons do not work as expected when we switch the theme direction to rtl
Expected behavior 🤔
As a user, I should be able to navigate through the left and right icons no matter what the value of direction is.
Steps to reproduce 🕹
Steps:

Visit codesandbox
Add dir="rtl" to Tabs component
Click on scroll button
User is not able to navigate between scrollable tabs

Context 🔦
No response
Your environment 🌎

npx @mui/envinfo
System:
  OS: Windows 10 10.0.19044
Binaries:
  Node: 17.8.0 - C:\Program Files\nodejs\node.EXE
  Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD
  npm: 8.5.5 - C:\Program Files\nodejs\npm.CMD
Browsers:
  Chrome: Not Found
  Edge: Spartan (44.19041.1266.0), Chromium (104.0.1293.47)
npmPackages:
  @emotion/react: ^11.10.0 => 11.10.0
  @emotion/styled: ^11.10.0 => 11.10.0
  @mui/base:  5.0.0-alpha.92
  @mui/icons-material: ^5.8.4 => 5.8.4
  @mui/material: ^5.10.0 => 5.10.0
  @mui/private-theming:  5.9.3
  @mui/styled-engine:  5.10.0
  @mui/system:  5.10.0
  @mui/types:  7.1.5
  @mui/utils:  5.9.3
  @types/react:  18.0.15
  react: ^18.2.0 => 18.2.0
  react-dom: ^18.2.0 => 18.2.0
  typescript:  4.7.4

This does not happen on my end, dir="rtl" makes the default selected tab start on the right, and when it is not there the default selected tab is the leftmost one.
Maybe I am missing something? I can navigate through the tabs https://codesandbox.io/s/long-star-wu282z?file=/demo.tsx
I just used the same sandbox.

This does not happen on my end, dir="rtl" makes the default selected tab start on the right, and when it is not there the default selected tab is the leftmost one.
Maybe I am missing something? I can navigate through the tabs https://codesandbox.io/s/long-star-wu282z?file=/demo.tsx
I just used the same sandbox.

Hey @Mark-777-0, are you able to scroll the tabs and see Item Seven in Tabs component?

Have you followed https://mui.com/material-ui/guides/right-to-left/#main-content for setting up RTL?

Yes, @mnajdova, I have followed all the steps from this rtl guide, but still, I was unable to navigate through tabs as expected.

The codesandbox does not reflex this, please update it.

After doing more research, it works in a very confusing way.
Here's an example link for codesandbox
We need to add the MUI theme and also need to add dir="rtl" prop to every component, we wish to change the direction.
Initially, my understanding was to just use the MUI theme, but that is not the case.

@pratikkarad you are missing steps 3. and 4. from the Right-to-left guide.


feat: flare mainnet/testnet rpc support

Thanks! Can you run forge fmt and push the fixes? Because this PR was opened from your fork's master branch, I cannot push to it

@mds1 done, Thank you


econe tools broken due to NameErrors

Description
All econe commands fail due to unknown constants, e.g.:
$ econe-upload --help
/usr/lib/one/ruby/cli/command_parser.rb:76:in `initialize': uninitialized constant CommandParser::CmdParser::OpenNebulaHelper (NameError)
	from /usr/bin/econe-upload:49:in `new'
	from /usr/bin/econe-upload:49:in `<main>'

Details

Affected Component: Econe
Version: 5.10

Progress Status

[ ] Branch created
[ ] Code committed to development branch
[ ] Testing - QA
[ ] Documentation
[ ] Release notes - resolved issues, compatibility, known issues
[ ] Code committed to upstream release/hotfix branches
[ ] Documentation committed to upstream release/hotfix branches

To be merged

one - PR https://github.com/OpenNebula/one/pull/4227 into

one-5.10
cherry-pick into master

docs - PR https://github.com/OpenNebula/docs/pull/953 into one-5.10-maintenance


Fix the new top/bottom unit tests

The new tests accidentally labeled the p3 variable as the data type
rather than a string.

During a run of megacheck the following issues were discovered:


Merge in Snapshot changes

This PR merges in all changes with Snapshot since we started working on our integration.

Can you point out places where we had merge conflicts, so we can review those specifically?

We didn't have any conflicts. Did you see any when you were going through the instructions?
The files I am seeing changes in both the uma branch and changes we merged in from Snapshot are:

src/locales/default.json
src/plugins/safeSnap/components/SafeTransactions.vue
src/helpers/interfaces.ts


the poor effect of repeated closed loop

hello, I am tuning 3d cartographer for my vel-16 data,but the effect of repeated closed loop is poor，I can't solve it,can you help me?
the configuration files , launch file, urdf file and result png files is here ,and the bag file is here.

On first glance SPARSE_POSE_GRAPH.constraint_builder.min_score = 0.7 seems very high to me try something like ~0.55

@sunmk2006 We mentioned some problems with your data in #509 already. Could you first comment on the issues before we further investigate? Most surprising to us is that you have the exact same number of IMU messages than VLP16 packets which seem nonphysical.

Sorry, I didn't respond to your comments in time.

the exact same number of IMU messages than VLP16 packets

This phenomenon stems from a synchronous approach，locate the IMU data based on the received laser timestamp，Because my IMU device and laser device do not work at the same time, the data of the two are not collected simultaneously.The recently uploaded bag data file does not pay attention to the synchronization of the two, and directly to the cartographer processing.Is there any problem with this method?

Is there any problem with this method?

Yes, it is. The synchronization is actually sub-optimal - it means that you integrate your IMU data for longer than necessary, leading to larger errors. Why are you doing this?
We will investigate your other bag in #509, I reopened the issue. Maybe a solution for this one comes out of that as well.

@Mofef  I have changed the parameter , but the problem still exists

Why are you doing this?
Still based on data synchronization considerations，I think in advance to do data synchronization, the effect will be better.

Still based on data synchronization considerations，I think in advance to do data synchronization, the effect will be better.

I do not understand that reasoning. Why should synchronized data collection better? More data will always be better than subsampling.

I also did UDP processing, but the effect is not very good.

Not sure what you mean with this.

More data will always be better than subsampling.
If the timestamp of the first IMU data in the bag file is 1000.000001 (second), the timestamp of the first laser data is 1020.000001 (second). Can the cartographer automatically synchronize the two data?

I also did UDP processing, but the effect is not very good.
Later, I'll upload the bag file in UDP form to the Internet

If the timestamp of the first IMU data in the bag file is 1000.000001 (second), the timestamp of the first laser data is 1020.000001 (second). Can the cartographer automatically synchronize the two data?

The offline node does this automatically. The online node could too, but ROS cannot deal with this (as it tries to transform the data and TF buffers are not that long). It seems unphysical that your sensor offset is that big and constant - how did that happen?
Closing this following the analysis in https://github.com/googlecartographer/cartographer_ros/issues/509#issuecomment-336484002.

If there's a fixed offset between the two sensors, just account for it in their timestamps. No need to change the sample rate.

@ojura It isn't a fixed offset, see our analysis in the linked comment.

the new configuration files and png files is here

@sunmk2006 Could you host your bags somewhere else? Downloading your bag from baidu takes > 10 hours here in Germany and the connection terminates regularly. Google Drive is better replicated and would be preferable.

OK， but I can't use Google drive, I will reduce the bag file or try another cloud disk.

@SirVer hello,a new link is here,You can test the download speed over there, and if the speed is still slow, I'll look for other cloud disks

Does the new link requires an account? I have trouble with the chinese.

No account required，please open the link, Put the mouse on the line of test_03.bag.zip，Click the second buttons that appear

https://github.com/sunmk2006/cartographer_ros/blob/master/20171025191607.jpg

that link opens a different looking page for me:

ok，i have an account<PHONE_NUMBER>1 and the passwd is 632851

I added two more links. See if you can use them
link1
link2

Timing of sensor data now seems fine, we had a look into the graphs. Some gaps in laser data are still present but not in the first seconds, so they don't explain why tracking fails.
I had a look at your bag file with
rqt_bag ~/Downloads/test_03.bag
and observed that IMU acceleration in z-axis is positive in this bag.
For this, the urdf setting
<child link="imu" />  <origin xyz="0 0 0" rpy="3.1416 0 0" />
cannot be correct. Gravity should be pointing down.
Perhaps you can share photos of how the sensors are attached to your robot?

sorry,  I should update the urdf file,the imu to base_link rpy should "0 0 3.1415926"

<parent link="base_link" />
<child link="imu" />
<origin xyz="0 0 0" rpy="0 0 3.1415926" />

I also tried this, quality was low again. Are you entirely sure the timing of the imu matches the laser scans?
Investigating this further will be hard without

photos of the setup to ensure the urdf transforms are correct
a fork that we can simply run and test without any copy-paste.

Okay, I'll upload a picture of the device later，below is a URDF model, the relative position is correspond with actual position of equipment , the problem is that in the ROS coordinates  x-->forward,  y-->left, z-->up, but x-->left,but my own coordinates x-->right,y-->forward, z-->up, because the IMU around the Z axis rotation to 180 degrees (yaw = 3.1415926 rad) ,the coordinates of IMU is x-->left, y-->backward, z-->up,How can I tell the cartographer system about these changes?

How can I tell the cartographer system so many changes about the coordinates?

Through the URDF.

In addition, is it possible that those configuration parameters (lua files)causes the problem?

Not the Lua files. But if your URDF is wrong your IMU and Laser are constantly disagreeing, so that would be definitively lead to the fragility we observe.

As I said, I observed that IMU acceleration in z-axis is positive in your bag.
In my eyes, this does not match the upwards IMU z-axis in the first picture.
Before any fine tuning, you need to correct the URDF first.

my imu device model is xsens MTI-G-700 ,I use the official equipment software to do an experiment, when the device is placed upright, Z acceleration is positive ,when placed upside down, Z acceleration is negative

If your IMU reads (negative) -10m/s^2, your URDF settings should be that the z-axis (blue) of IMU points upward.
If it reads positive, z-axis should be configured downward.
For the other axes, we would need more information.


warn function not imported

Describe the bug
When I try to import the stiffness matrix from a file located in my Python directory (which is the same as my MAPDL directory), PyMapdl tries to send a warning message. However, the function warn is not imported, thus I have an error (see the screenshot below)
Screenshot

System Information:

OS: [e.g. iOS]
Ansys version: 2021R2
PyMAPDL version: 0.61.5

I am using Python 3.8.
Thank you,
Louis

You are right. Thank you for reporting!


Connect but no write

I’m having this issue I am able to list devices, then to connect to the chosen one but when I trie to write value, nothing happens I’m ina hurry and didn’t mind to pay for the service of helping me out solving this as is due on Thursday contact please at<EMAIL_ADDRESS>

Yes, It happens to me also.
I'm not receive any event from heartRateServiceModel, batteryServiceModel.
Please help me!


is_aux_heat property or uses the auxiliary heater methods is deprecated

Since the latest update of HA (version 2024.4.x) the luxtronic component is giving an error:
The custom integration luxtronik2 implements the is_aux_heat property or uses the auxiliary heater methods in a subclass of ClimateEntity.
Full log:
Logger: homeassistant.components.climate
Bron: components/climate/init.py:419
integratie: Klimaat (documentatie, problemen)
Eerst voorgekomen: 11 april 2024 om 15:49:47 (1 gebeurtenissen)
Laatst gelogd: 11 april 2024 om 15:49:47
luxtronik2::LuxtronikThermostat implements the is_aux_heat property or uses the auxiliary heater methods in a subclass of ClimateEntity which is deprecated and will be unsupported from Home Assistant 2024.10. Please create a bug report at https://github.com/BenPru/luxtronik/issues

It is not an Error, it is a warning and have to fix till 2024.10.*

See #245


Don't translate Git command

VSCode Version: Insider 1.10
OS Version: Windows 10 version 1511

Steps to Reproduce:

Set your VSCode locale to zh-CN
Check Git Panel > "···" Button (three dots) > Git command

"Pull" translated to "拉"
"Pull (Rebase)" translated to "拉取 (变基)" // PS: looks like "somebody become  a gay" in Chinese...(This is a Joke)

Why same word "Pull" will be translate to different word in Chinese? "Pull" > "拉" / "拉取"
We know what is Push, Pull, Rebase ,but we really don't know what is "拉取(变基)"

With the latest VSCode all commands in the command pallette are not translated (when you press F1).
Though I understand you might want to never translate git commands - so even in the git viewlet


DiffMode made public

Codecov Report

Merging #3 (bd3bfd6) into main (a1bed19) will increase coverage by 0.32%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main       #3      +/-   ##
==========================================
+ Coverage   98.01%   98.33%   +0.32%
==========================================
  Files           2        2
  Lines         151      180      +29
==========================================
+ Hits          148      177      +29
  Misses          2        2
  Partials        1        1

Impacted Files
Coverage Δ

datediff.go
97.76% <100.00%> (+0.61%)
:arrow_up:

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 a1bed19...bd3bfd6. Read the comment docs.


[EasyCodingStandard] bug with sniff excluding

Excluding works! This was caused by reporting parent class of sniff


oopsyraidsy: add cn language to oops html

I'm not sure about more localizations of other parts of oopsraidsy, will it work if I add translations to specific triggers in oopsraidsy/data/.../*.js?

Yeah, adding translations to specific triggers should do the trick.
I've tried to use effect and ability names where I could to limit the amount of translation needed.


fix swapped liveness/readiness http paths. (#4541)

created changelog fragment
fixed scaffold template for the manager resource (ansible/helm)
fixed testdata (ansible/helm)

Signed-off-by: Florin Hillebrand<EMAIL_ADDRESS>Description of the change:
Fix wrong HTTP paths of the livenessProbe and readinessProbe in the scaffold templates and testdata.
Motivation for the change:
livenessProbe and readinessProbe were swapped in templates but are correctly documented in upgrade guide.
Checklist
If the pull request includes user-facing changes, extra documentation is required:

[X] Add a new changelog fragment in changelog/fragments (see changelog/fragments/00-template.yaml)
[ ] Add or update relevant sections of the docs website in website/content/en/docs

Is it ok, having two PRs referencing the same issue? #4545 and #4546

You @estroz also cleared something up for me, thanks :)


Add links to the GitHub to the footer of the webpage

The link to this GitHub repo should be added to the base HTML template.
If you plan to work on this, please comment here first.

I can try this

#12


Bug: sdk list java produces HTML not found response

Bug report
sdk list java produces an HTML response
To reproduce
log $ sdk list java
<!DOCTYPE html>

        <title>Not Found</title>

Not Found

            For request 'GET /candidates/java/Darwin/versions/list?current=&installed='

System info

macOS
GNU bash, version 5.0.7(1)-release (x86_64-apple-darwin18.5.0)
5.9.1+575

Its 17 minutes later and I can no longer reproduce

Hi,
I've just tried and I got this error in HTML:

<title>404 Not Found</title>

404 Not Found

nginx/1.19.1

Hi @jameskleeh, we've had some abuse of our APIs lately. I've put some IP blocking in place so this should solve the problem. Please let me know if the issue persists.

Hi @jameskleeh, we've had some abuse of our APIs lately. I've put some IP blocking in place so this should solve the problem. Please let me know if the issue persists.

For me, the problem is still here :(

@chrix75 sounds like you might be having a different issue. You are getting a 404 from nginx, pointing to a potentially outdated version of sdkman. Feel free to ask on Slack #user-issues, one of us would be happy to help if your problem persists.

@marc0der the selfupdate force didn't work. So, I've tried a new installation of Sdkman and now all is working. Thanks and sorry for the mistakes.

Not at all! It's my fault for not keeping the legacy endpoints alive long enough. I'm glad you got it sorted.

@jameskleeh mind if we close this issue now?

Sure thing
On Sun, Oct 25, 2020 at 1:43 PM Marco Vermeulen<EMAIL_ADDRESS>wrote:

@jameskleeh https://github.com/jameskleeh mind if we close this issue
now?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sdkman/sdkman-cli/issues/811#issuecomment-716184255,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMCVLNHX5WSW5AYRKLHKHDSMRPSPANCNFSM4S3SS4QA
.


WIP: allow to specify timeout/interval for waiting for disk ready

@maximilien This PR is for address tracker 127370877, I committed the initial code change, I found there are a dozen SL client requests which need to be faked for the unit test, I hope to let you review the code change before implementing the unit test, it will be a big challenge to me. Thanks.

@maximilien  It failed because the package "github.com/cloudfoundry/bosh-utils/retrystrategy" is not in Godeps, I could add it in softalyer-go godeps if you are OK with leveraging bosh-utils/retrystrategy here.

@mattcui Travis is failing. Please fix that first. Note here when Travis is passing and I will review. Thx.

I will open a new one for review


[Tracking] [Docs] Model Support Streamlining

Overview
This task focuses on streamlining the process of adding new models and keeping track of the existing prebuilt model libraries and model weights we offer. Specifically, there are three main goals:

Make the prebuilt model page more intuitive and well-structured
Create an end-to-end instruction for adding a new model, (as currently, “supporting a model” is relatively vague)
A better way to track the community’s model requests and contributions

For more on the design/layout, please see the doc here. Feel free to offer your suggestions, any insights would be greatly appreciated.
Co-author: @rickzx
Action Items

[ ] Revamp the current prebuilt model page

https://github.com/mlc-ai/mlc-llm/pull/1000

[ ] Create an end-to-end instruction/checklist on how to support a model, and where to update the documentation accordingly.
[ ] Create a dashboard for new model requests (perhaps use Phi or Falco for trial to see how viable the workflow is)

Links to Related Issues and PRs

There are various past efforts to improve this aspect of MLC-LLM's workflow, e.g.:

https://github.com/mlc-ai/mlc-llm/issues/692
https://github.com/mlc-ai/notebooks/blob/main/mlc-llm/tutorial_extensions_to_more_model_variants.ipynb

We would hope this attempt to be more future-proof and long-lasting.

Hey @CharlieFRuan I love the work you've been leading on model streamlining! One additional question I'd love to discuss with you is that we will need not only a streamlined process, but also a transparent and reproducible workflow, preferably, say, a bash script or so, to release new models on all platforms, pushing them to GitHub and weights to HuggingFace.
So far, @MasterJH5574 has been in charge of new model releasing process, while knowing it's theoretically feasible, non-CMU contributors like me usually don't have sufficient incentive to push through in case of potential breaking change. Having a transparent bash script will help me personally to add new models without having to bother Ruihang all the time :)

Hi @junrushao, thanks for bringing this up! We agree that some automation would make the process a lot less cumbersome, especially given that we have so many degrees of freedom (mode size, quantization scheme, and most importantly, platforms). I added this point to the task; we will follow up on this! cc @rickzx

There are three aspects of releasing a model:

A1. The model weights, which we usually update to HuggingFace; A model architecture could correspond to multiple model weights, for example, Llama2 for Llama2 and WizardLM;
A2. The model lib, or the compiled execution of the model; A model architecture usually corresponds to a single model lib, unless there's some minor tweaks in the architecture;
A3. The default mlc-chat-configuration.

Likely A1 and A3 could be bundled together, but I was curious if we have a plan displaying (A1 + A3) and A2 in a table?

The PR here https://github.com/mlc-ai/mlc-llm/pull/1000 displays A1 and A2 into a set of tables. In the comment, there is a pdf for easier review of the page. There are three levels from high to low:

An all-in-one table, displaying all architectures and variants we support
Model lib table (A2 here), one for each architecture
Model weights (A1 here), one for each model variant

A3 is indeed missing, and we will add it to the level 3 tables!

Thanks! Let's move the discussion to that PR


terraform_docs_replace does not work in root directory

.pre-commit-config.yaml:
repos:
- repo: git://github.com/antonbabenko/pre-commit-terraform
  rev: v1.8.0
  hooks:
    - id: terraform_fmt
    - id: terraform_docs_replace
      args: ['--with-aggregate-type-defaults', '--sort-inputs-by-required']

There are *.tf and *.tfvars files in root and in directories.
README.md in directories is correct, but README.md in the root dir has this content:
Usage:
    terraform-docs [--no-required] [--no-sort | --sort-inputs-by-required] [--with-aggregate-type-defaults] [json | markdown | md] <path>...

PS: @RothAndrew could you please take a look and fix this.

Yep. I'm on it.


⚠ Fetchers has degraded performance

In cb569f7, Fetchers ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 872 ms

Resolved: Fetchers performance has improved in 1582e56.

Resolved: Fetchers performance has improved in 1582e56.


failed when Waiting for TFSparkNodes to start

hi, I encountered the following problems,
on EMR cluster,
I have 1 * r5.xlarge(4 vCore, 32 GiB memory), 1 * m4.xlarge(4 vCore, 16 GiB memory) ,
when I run :
spark-submit --master yarn --executor-memory 10G --driver-memory 6G --conf spark.executor.instances=2 --conf spark.dynamicAllocation.enabled=false --conf spark.task.cpus=1 --conf spark.yarn.maxAppAttempts=1,
however I get  only 1 reservation successfully, like below

why? Technically, I have eight cores, and I just set spark.executor.instances=2

Can you run a simple (non-TFoS) pyspark job on this cluster (with similar settings) and check that you see two executor instances?

you are right!
when i set two executors, actually only one executor is generated. I will check why this happen. thanks.

Closing due to inactivity.


send_message with asyncio.wait_for

Hello,
I am currently working on a piece of code using send_message and I have to manage the situation where connection is not available. Simply using send_message I see the code get stuck on send_message itself. I started using asyncio.wait_for together with it and I  can manage the situation as I want. However, I am getting "Task exception was never retrieved" message and I suspect there can be something I am not considering with the send_message.
I saw this https://github.com/Azure/azure-iot-sdk-python/issues/775#issuecomment-852485494 and I'd like to know if you have been able to do some steps ahead in that direction.
Thanks

@pbudel
Which version of the package are you using?

@cartertinney
~ # pip3 list|grep azure
azure-core          1.22.1
azure-iot-device    2.10.0
azure-storage-blob  12.9.0

@pbudel
Okay, so in the latest version (which you have) the above linked issue has been addressed. What I suspect you're running into is that sending a message requires a connection. By default, the client will attempt to connect first (unless you specify that auto_connect is False at client creation), and I suspect that is causing the hanging.
As for asyncio.wait_for() let me take a look and see where we're at with that.

@cartertinney thanks. I will give you a bit more context on how I am testing this situation.
The testing environment where the code is running is an embedded system with 2 network interfaces: one is ethernet, the other one is Wi-Fi. The production HW will only have Wi-Fi and what I want to achieve is to be able to detect lack of connectivity (in production environment) to handle temporary buffering of the telemetry that will be then sent out once connectivity is back.
To reproduce the "production" situation what I am doing is:

connect the HW to the Wi-Fi that provides internet connectivity
connect the HW to my PC using ethernet port (no gateway settings. Just one to one connection). I use this connection simply to ssh into the linux system and play with it
once the SW is sending telemetry through the send_message I am shutting down the Wi-Fi connectivity (ifconfig wlan0 down)

Once the system boot up and connect the first time to the hub, there is no call to disconnect or shutdown so I am assuming the client should consider itself always connected.
What happens when I am doing 3) is that send_message hung for a super long period (probably related to TCP timeout?). The use of asynio.wait_for() allows quick detection of the above mentioned situation but leads to "Task exception was never retrieved" that I don't like. This is why I am asking.
NOTE: I understand testing environment is not reproducing perfectly the production environment, but I would expect that in this case fixing the code on test environment will make it even more robust on production
Hopefully you can have a better view of the situation or you have suggestion.
Thanks again

@pbudel
I looked into it, and we are not able to support asyncio.wait_for() at this time as we cannot support task cancellation, which asyncio.wait_for() is dependent upon. We apologize for any inconvenience.
If you're looking for a way to detect a lack of connectivity, the .on_connection_state_change handler might be helpful. If you set a function on that property, it will be invoked every time the connection state changes. You can see what the connection state is by accessing the boolean property .connected on the client. Do note that depending on the keep_alive setting, a disconnection may take some time to be noticed.
I hope this helps. Let me know if there's any other assistance I can provide.

@cartertinney
ok I got it. Given that asyncio.wait_for() is not supported I have changed approach. I think you could consider adding a timeout optional parameter on the send_message implementation.
Now I am working only with the .connected boolean property and leaving keep_alive as default I see the disconnection in about 2 mins. It's far from the 3 seconds I was considering when trying asyncio.wait_for() but we can survive ;)
Last question for you, once I am getting the disconnection I see the following:
Exception caught in background thread.  Unable to handle.
["azure.iot.device.common.transport_exceptions.ConnectionDroppedError: ConnectionDroppedError('Unexpected disconnection') caused by ConnectionDroppedError('Paho returned rc==1')\n"]
Exception caught in background thread.  Unable to handle.
["azure.iot.device.common.transport_exceptions.ConnectionDroppedError: ConnectionDroppedError('Unexpected disconnection')\n"]

Do you feel this is something expected? I am "obviously" (given the message) not able to catch ConnectionDroppedError.
Thanks

@pbudel
Yeah, that looks like expected behavior when the internet connection is dropped while the client is trying to maintain a connection, which from what I understand is your use case. From the client's perspective, the connection going away is unexpected because no explicit connection ocurred.
Again, you can reduce the keep_alive to get the client to notice the connection drop faster.
I'll look into potential support for timeout, and discuss some options with our team, but I suspect we're going to run into the same issue as with asyncio.wait_for() in that supporting such a feature would require significant re-implementation.

@cartertinney
Thank you. I am able to catch the exception and I will not change for keep_alive for now, I understand however your point.
Unfortunately it seems like I have another issue, probably related to the http_pipeline (not sure). On a task I am checking for file presence and eventually I am uploading it to an azure blob storage. If the disconnection happens when I am awaiting for get_storage_info_for_blob() to return... that task remains there indefinitely even if I am calling and explicit disconnect() once I got the dropped connection event from the telemetry. Is there any chance that the HTTP request will not be dropped/aborted by the disconnect() call? If not, wouldn't be a good idea to drop also that request?

@pbudel
I'll take a look

@pbudel
#980 adds some protection against the indefinite hanging, by timing out HTTP requests after 10 seconds. At this time explicit disconnect will not immediately cancel the task, it will just need the 10 seconds to timeout. We will continue to try and make some improvements in this domain in the future, alongside the initial request to improve the area around asyncio.wait_for(), but for now this should solve your immediate problem.
We will include this fix in the next release

@pbudel
#980 has been checked in. It will be included in the next release.

@cartertinney Thanks. I appreciate it.


Added implementation for imageToRemoteImagingLocus as look direction.

I'm going to merge these changes in since the changes have been approved.


Yosys aborts on $memrd/wr cells when saving json, reloading json, and continuing the same process

Steps to reproduce the issue
Start Yosys and do this:
read_verilog CpuComplex.v
read_verilog -lib -D_ABC +/ice40/cells_sim.v
hierarchy -check -top CpuComplex
proc
write_json CpuComplex.proc.json
exit

Restart Yosys and do this:
read_json CpuComplex.proc.json
flatten

Full repro environment can be found here: https://github.com/tomverbeure/yosys_error/tree/save_reload_crash.
Just clone and execute  ./run.sh.
Expected behavior
I expected to be able to use JSON to save and restore state and pick up where I left off.
According to @daveshah1, the JSON netlist format shouldn't be used for that.
But at least, Yosys should bail with some error instead of just aborting.
Actual behavior
Yosys aborts as follows:
...
Importing module CCPipelinedMemoryBusRam from JSON tree.
Importing module CCMasterArbiter from JSON tree.

2. Executing FLATTEN pass (flatten design).
Using template VexRiscv for cells of type VexRiscv.
<suppressed ~1 debug messages>
ERROR: Assert `memory_renames.count(memid) != 0' failed in passes/techmap/techmap.cc:425.

The abort is caused by the presence of $memrd and $memwr cells in the netlist. When I remove those, Yosys proceeds as expected.
Work around
Use write_ilang/read_ilang instead of  write_json/read_json. That works fine.
The reason I wanted to use json is because it doesn't require a custom parser for most languages.

Proposed "fix": write_json should emit an error if it encounters $memrd/$memwr.

Proposed "fix": write_json should emit an error if it encounters $memrd/$memwr.

I am using "$memrd/$memwr" cells written in JSON. This proposed "fix" would break it.

I am using "$memrd/$memwr" cells written in JSON. This proposed "fix" would break it.

Without being able to associate them with memories (which are not representable in the current JSON format) there is not much that can be done with those cells. How are you using them?

Using them in a custom "cxx" like backend as ports to read and write C array content.

Are you inferring the memory width from the \WIDTH parameter of $memrd cells, and the memory depth from the \ABITS parameter?

Are you inferring the memory width from the \WIDTH parameter of $memrd cells, and the memory depth from the \ABITS parameter?

Yes.
I have added "torder" into write_json. Then those memrd and memwr cells are leveled in correct level of logic. $mem can't be used coz it's not possible to "torder" it.

It seems like you are already using a patched version of Yosys to do what you want. This means that you won't be affected by the change as you can revert it in your own fork; however, I would personally argue that the JSON format can be extended to include expanded memories. The added complexity is minor, and they are still useful even without support for processes.
That said I would leave the final decision to @cliffordwolf.

+1 to read expanded memories in with read_json.


Update cluster view to include members donut.

Yep, now it doesn't fit in windows. Not sure how to fix it as I'm really a web guy. Need help :)

I'll fix it up, np! The colors probably need adjusting as well as we're using the same colors for different states.


feat(multiselect): Restyling of multiselect - FRONT-2592

first we need to add the removable badge and see if we can adapt the functionality of removing a option using our icon.

Can you check the reason why of the difference in terms of font family or font style i see between the badge and these elements from slimselect..? I think the x as we have it is acceptable, the main difference i notice with the badge is indeed the font rendering, see if we can align that and then for me this lightweight solution can be good enough.


WIP: new version of decorators in requre

btw, is it still WIP?

btw, is it still WIP?

@lachmanfrantisek yep, forgot to remove it, but i've found that I had generation of tmpfiles ouside of requre so that tempfile everytimes changes, what was bas from git view, now I've just done property from self.tempfile so that now it is fixed and tempfile will not change everytime filename. I found it yesterday evening when playiing with copr tests :-)


bug:  codeblock-lowlight doesn't render in html output

Provide environment information
System:
OS: Windows 11 10.0.22631
CPU: (16) x64 AMD Ryzen 7 5800X 8-Core Processor
Memory: 4.96 GB / 15.92 GB
Binaries:
Node: 22.1.0 - C:\Program Files\nodejs\node.EXE
npm: 10.7.0 - C:\Program Files\nodejs\npm.CMD
pnpm: 9.0.6 - C:\Program Files\nodejs\pnpm.CMD
Describe the bug
With recent codeblock-lowlight extension integration: https://github.com/steven-tey/novel/pull/375  it works perfectly in the editor but when I render the editor contents as HTML from (window.localStorage.getItem("html-content")), it changes the code content to plain html text.
Editor:

When HTML rendered from from (window.localStorage.getItem("html-content")):

Link to reproduction
None
To reproduce
Just render the content from (window.localStorage.getItem("html-content")) using  dangerouslySetInnerHTML like:

Additional information
I am working on its fix will raise PR soon.

Fixed


Typos

Minor typo and prettier fix.
ref: https://github.com/pydata/pydata-sphinx-theme/pull/736#discussion_r900705827

Gonna self-merge since this fixes a test that always breaks 😬


Cannot edit build commands when connecting frontend web app - due to CSP?

I've selected Github repo, and I've come to step 2, where I should "configure build settings". I want to edit the auto-generated build and test settings, so I click "Edit". But in the dialog that opens, I cannot edit anything. In the Chrome console, I can see the following error:

Refused to load the script 'https://eu-west-1.console.aws.amazon.com/amplify/mode-mode.js' because it violates the following Content Security Policy directive: "script-src https://d25ir82nywnt3g.cloudfront.net/ https://d1b6ig1vwyrbxe.cloudfront.net/ https://media.amazonwebservices.com/urchin.js https://d2q66yyjeovezo.cloudfront.net/ https://d1ge0kk1l5kms0.cloudfront.net/ https://d18ovsmfaucn3d.cloudfront.net/". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback.

My chrome version is:
Version 80.0.3987.116 (Official Build) unknown (64-bit)

@stigalvestad Thank you for reporting this bug. We will investigate on this issue. I tested on  Version 80.0.3987.106 (Official Build) unknown (64-bit) and
Version 80.0.3987.122 (Official Build) (64-bit)
They all works fine. If you refresh the page and reconnect your app, would it work? If you don't mind, would you mind upgrade chrome to version 122 and try connecting your app?

I get the same result using Firefox 74.0 64bit, Chrome 80.0.3987.149, also with private/incognito mode on 2 different Windows 10 machines, in that I am unable to edit the build commands.
Also the Light/Dark theme toggle does not work when this happens.

@daunce @stigalvestad Thank you for reporting this error, we cut a ticket in our team backlog. We will working on a fix.

@daunce are you able to share how to overcome this bug to be able to edit the build command? I'm stuck and unable to continue..

I see that the problem only occurs when setting up your amplify app and linking it to GitHub. After saving and deploying, editing the build command through App settings -> build settings works as expected 👍

Same problem here. Using Chrome, latest

I'm still facing this issue as well. Then, after the build fails, the amplify console behaves as in #1343. I can't manually trigger builds and it doesn't seem to trigger a build when I push to my Github repo. The only option seems to be switching to manual deployments right now -- quite frustrating.

Also running into this issue. Would like to see movement on this, or at least a clearer wrok around for setting up Git-based deployments. Very frustrating

Hi @stigalvestad I am unable to repro the issue, please feel free to re-open if you are still facing the issue. Thanks!


Bézier-rs: Add ids to manipulator groups

Each manipulator group now has a generic id type that implements the ManipulatorGroupId trait. This allows the subpaths to integrate with Graphite's UUID system without having to depend on additional libraries or adding extra overhead to other users who may not need the ids.

I personally feel like it's a little confusing for both the generic data type and the trait to be named ManipulatorGroupId, but I don't feel too strongly about it. Otherwise, it looks good to me!

Do you have a preferred name for the generic / trait @hannahli2010?

Thanks - I've renamed as suggested @RobNadal.


refactor and clean workflow tasks and tests

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story (FLPATH-xxxx):
Fixes #
Change type

[ ] New feature
[ ] Bug fix
[x] Unit tests
[ ] Integration tests
[ ] CI
[ ] Documentation
[ ] Auto-generated SDK code

Impacted services

[x] Workflow Service
[ ] Notification Service

Checklist

[x] Subject and description added to both, commit and PR.
[ ] Relevant issues have been referenced.

@anludke I retriggered the job but it failed again. Please check why it is failing


User can approve or reject his/her own PR

Gitea version (or commit ref): bc06ab4a31c54c5d164d53ec16d5c1089be9c3fe
Git version: 2.15.2 (Apple Git-101.1)
Operating system: MacOS
Database (use [x]):

[ ] PostgreSQL
[ ] MySQL
[ ] MSSQL
[x] SQLite

Can you reproduce the bug at https://try.gitea.io:

[x] Yes ( https://try.gitea.io/lanre.adelowo/dotfiles/pulls/1#issuecomment-7378 )
[ ] No
[ ] Not relevant

Log gist:

Description
A user can approve and/or reject a PR (s)he created... This behaviour doesn't exist on Github for example
...

This is not for merging but for reviewing only.... You obviously can merge but not review

See screenshot

@adelowo you are right.


Add support for Perforce repos

Since zoekt does not seem to support indexing anything other than git repos, this is probably a non starter.
You would be well server using a took such as OpenGrok:
https://github.com/oracle/opengrok
This natively supports perforce indexing and search.

There is also p4-fusion, which can convert a perforce depot to a git repository (to my understanding). When I get some free time, I can try it out and get back to you -if it works, might be worth writing a doc about it.


Water source was accidently removed and cant get anymore water

You can make a cauldron, leave it out in the rain, and pull water out of it with a bucket. None of this should require water, if I remember correctly.


Inconsistent closed/open state for closed issues on project boards

Description
Quote here from Discord:

Hey all! 👋 Wondering if I can get some help with a small problem I have (it may be a bug too, but I can't find anything in the > Issue Tracker on Github).
I have an internal private Org with an internal private repo which has 1 project. The Project has the boards "Uncategorized" > (default?), Backlog and In Progress.
Problem I have is there are some issues in "Uncategorized" that show up but are actually closed. There seems to be no way > to fix their status from the Project/Board view. In fact the icon on the board indicates the issue(s) (two of them) are in fact open, which they are not, they are actually closed.
How did this happen?
Is this a bug?
How can I fix this?
lunny — Today at 12:36 PM
Looks like bug, could you post an issue for that?

Gitea Version
1.17.0
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
I cannot provide screenshots as the project and issues are a private org and contain confidential information.
Git Version
N/A
Operating System
Docker on BurmillaOS
How are you running Gitea?
Docker on BurmillaOS in a Docker Swarm cluster.
Database
SQLite

NB: I am unable to create an account and signin via Github to the try.gitea.io site. it is stuck at:

Activate Your Account
A new confirmation email has been sent to<EMAIL_ADDRESS>Please check your inbox within the next 3 hours to complete the registration process.

The email is not coming 😢

So what's the problem now or is this still happening in the recent Gitea version? (Sorry to necrobump such an old issue.  Just curious about this one.)
The project feature sometimes has some out-sync/concurrence bugs. It's almost driven me crazy since I could not find out the root reason.

The email is not coming

I think it's temporary.

We close issues that need feedback from the author if there were no new comments for a month. :tea:


How does SORT work for string properties

My Environment

ArangoDB Version:       3.9.3
Deployment Mode:       Single Server
Deployment Strategy:    Manual Start in Docker
Configuration:
Infrastructure:               AWS, RHEL VM
Operating System:        UBuntu 20.04, RHEL 8
Total RAM in your machine:        64GB
Disks in use:        SSD
Used Package:

Component, Query & Data
AQL, arangojs
AQL query (if applicable):
For doc in dummy
	SORT doc.r
	return doc

AQL explain and/or profile (if applicable):
Query results are:
[
  {
	"_key": "441941",
	"_id": "dummy/441941",
	"_rev": "_gZktyIC---",
	"r": "_"
  },
  {
	"_key": "441650",
	"_id": "dummy/441650",
	"_rev": "_gZktkLe---",
	"r": "-"
  },
  {
	"_key": "450584",
	"_id": "dummy/450584",
	"_rev": "_gZvbPKu---",
	"r": "0"
  },
  {
	"_key": "450600",
	"_id": "dummy/450600",
	"_rev": "_gZx0HOm---",
	"r": "1",
	"a": "whatever"
  },
  {
	"_key": "450616",
	"_id": "dummy/450616",
	"_rev": "_gZvbtu2---",
	"r": "5"
  },
  {
	"_key": "441680",
	"_id": "dummy/441680",
	"_rev": "_gZktIaC---",
	"r": "A"
  },
  {
	"_key": "441771",
	"_id": "dummy/441771",
	"_rev": "_gZktTta---",
	"r": "a"
  }
]

The sorted strings are effectively:
'_', '-', '0', '1', '5', 'A', 'a'

The sorted results are different from Array.sort() or localeCompare()
unifr@melon:~$ node
Welcome to Node.js v16.19.0.
Type ".help" for more information.
> ['_', '-', '0', '1', '5', 'A', 'a'].sort()
[
  '-', '0', '1',
  '5', 'A', '_',
  'a'
]

> ['_', '-', '0', '1', '5', 'A', 'a'].sort((a, b)=>a.localeCompare(b))
[
  '_', '-', '0',
  '1', '5', 'a',
  'A'
]

> ['_', '-', '0', '1', '5', 'A', 'a'].sort((a, b)=>a.localeCompare(b), 'en-US')
[
  '_', '-', '0',
  '1', '5', 'a',
  'A'
]

In the Arangodb container, the default LANGUAGE is set to en_US.
/var/lib/arangodb3 # cat LANGUAGE
{"default":"en_US"}

According to the documentation:  https://www.arangodb.com/docs/stable/aql/fundamentals-type-value-order.html,

string: string values are ordered using a localized comparison, using the configured
server language
for sorting according to the alphabetical order rules of that language

But I'm not sure what the compare function SORT in AQL uses in my ArangoDB.
Dataset:
Above is from a dummy document collection
Size of your Dataset on disk:
Very small
Replication Factor & Number of Shards (Cluster only):
N/A
Steps to reproduce

Add documents to collection (with the content above)
Run the AQL query

Problem:
The sort order is not what I expected
Expected result:
I would expect the same results as using a.localeCompare(b), 'en-US')

String comparisons are handled by ICU, with exceptions for ArangoSearch-related features.
The difference between JavaScript and AQL seems to be that JS sorts lowercase characters before uppercase characters, whereas in AQL it is upper before lower. This is explicitly set for ICU by the server here, but only in the fallback case:
https://github.com/arangodb/arangodb/blob/72baaac8bddafc7e826abde1b35e2a512488cf6b/lib/Basics/Utf8Helper.cpp#L172
If you explicitly specify --icu-language en_US, this attribute does not get set, and you get the default ICU behavior AFAICT.
I'm not sure if JavaScript explicitly sorts lowercase before uppercase or if it uses the default, which seems to be "off" according to the ICU Collation Demo - but I don't know whether it means "undefined order". It rather looks like the default is lowercase before uppercase (see the diff strengths in the collation demo).


Getting Error message  message: 'User not found [403]',   errorType: 'Meteor.Error' }

SETUP
HUBOT ==========Rocketchat server
.ENV
export ROCKETCHAT_URL=http://<IP_ADDRESS>:3000
export ROCKETCHAT_USER=pibot
export ROCKETCHAT_PASSWORD=password
export ROCKETCHAT_ROOM=general

COMMAND & ERROR LOGs
source .env
bin/hubot -a rocketchat

 password: 'password',
  ldap: false,
  host: 'rocket:3000',
  useSsl: false,
  timeout: 20000,
  rooms: [ 'general' ],
  allPublic: false,
  dm: false,
  livechat: false,
  edited: false,
  integrationId: 'js.SDK',
  roomCacheMaxSize: 10,
  roomCacheMaxAge: 300000,
  dmCacheMaxSize: 10,
  dmCacheMaxAge: 100000 }
[Thu Nov 07 2019 06:17:21 GMT+0000 (Greenwich Mean Time)] INFO [connect] Connected
[Thu Nov 07 2019 06:17:21 GMT+0000 (Greenwich Mean Time)] INFO [login] Logging in pibot
[Thu Nov 07 2019 06:17:21 GMT+0000 (Greenwich Mean Time)] INFO [login] Error: { isClientSafe: true,
  error: 403,
  reason: 'User not found',
  message: 'User not found [403]',
  errorType: 'Meteor.Error' }
[Thu Nov 07 2019 06:17:21 GMT+0000 (Greenwich Mean Time)] ERROR Unable to login: {"isClientSafe":true,"error":403,"reason":"User not found","message":"User not found [403]","errorType":"Meteor.Error"}

And using the same above mentioned BOT account i can login to rocket chat via GUI or WEB.
I know for sure the user account has been setup correctly(username as pibot, Role as BOT, EMAIL verified option is checked, using outlook email account and password change option disabled)
Thanks
GS

Issue got resolved after enabling View-C option for BOT under Permissions.
Had to try Hubot connection to RC multiple times.
Not sure if it's a bug.


Branch fixing checkstyle

Do not merge.

Can merge. Follow all the checkstyle, currently is failing the test cases.


Add webhint.io to auditing tools

WebHint is another great performance auditing tool (among other things). It's also a part of the JS Foundation.

Added, I haven't come across WebHint before, looks like a very useful tool. Thank you @aarongustafson!


DS-2367 Improve BitstreamReader Performance and Caching behavior in XMLUI

https://jira.duraspace.org/browse/DS-2367

Overall looks reasonable.

This has merge conflicts. Also, the first commit duplicates #799 which was just closed without merging. So, commit https://github.com/atmire/DSpace/commit/8338e64bd0dc0c744693eb06152c9965f7086a6c needs removal or fixing.
This PR needs a lot of work/love before it'd be ready to get in.

Unfortunately, this improvement PR still remains unready to merge, so we are dropping it from the 6.0 milestone. This is the second release cycle this PR has missed. I think it's going to need a dedicated sponsor to make it in for 7. Of course, the code remains available should anyone wish to incorporate it into their fork of DSpace.

While the concept behind this code is reasonable, this code is outdated/obsolete. As of the latest master, build.properties no longer exists (see https://jira.duraspace.org/browse/DS-2654). In additional all the included Flyway migrations would need to be renumbered (currently reference 5.0).
Closing this as outdated. Please open a new PR to continue this work.


Add Weights to Dimension and Subdimension model and interface

Subdimensions and Dimensions need to have weights associated with them for computing scoring.
The weight should accept a floating point number and default to 0.5.   Put the weight after the description for both dimensions and subdimensions.

https://docs.google.com/spreadsheets/d/1wOAu4OnhNeehUx0dZ6Fp3t6vKX5VjzS2e70BI0OwbQc/edit#gid=1593683221

Done


My balance is zero but it's false

My balance is zero but it's false. For lucky! I almost died of fright. I'm newbe and I thought that I had been robbed. I bought BTC a few days ago and Copay (in Android Nougat 7.1.2) indicated the total received correctly. A day later I bought ADA but the amount indicated by Copay that I sent is false. I totally uninstalled and installed again but the problem persists.
The Exodus and Electrum wallets correctly indicate the transaction sent and the current balance.
Any ideas to solve it?
Thanks in advance.

Hello @superlativo77 , sorry for the delay. Are you still having problems?
You can try this: Settings -> Wallet Settings -> More options -> Wallets addresses -> Scan addresses for funds

@superlativo77
I can recover your wallet if you want need help send me email<EMAIL_ADDRESS>

@superlativo77 I can recover your wallet if you want need help send me email<EMAIL_ADDRESS>
SCAM ALERT!


Bundle using esbuild

This uses esbuild to bundle the extension into a single file. Some notable changes:

The output of esbuild goes into the dist folder. Only that file needs to be included in the extension. We can ignore the regular compilation output that goes into out.
Make sure to install the recommended extensions (listed in .vscode/extensions.json) as the new one includes a problem matcher for esbuild.
package.json still includes the old compilation scripts. Some of them are still used for testing, which relies on regular compilation, not bundling.

With this, the extension now includes only 11 files. The output of npm run package says 13 files, but I think that includes directories. In any case, you can check which files are included with npx vsce ls.
This fixes #50 and supersedes #55

Nice to see the package half in size though


Add pluggable logging for #426 v2

See original issue. I'm of the high opinion that at least core configuration should not require logging otherwise you can't configure logging!!!
This change adds a private logging facade for archaius. I have set the default to NoOp but one could easily write a SLF4J and have it be the default. We could also use the ServiceLoader mechanism to load up a default logging implementation (I actually helped @mattrjacobs setup something similar for Hystrix plugins).
Of course the possibly simpler and perhaps better option is to not do any logging in archaius2-core and fail fast and configuration to ignore errors... etc.
Ignore the checked in pom file (I needed it because I'm mirroring in a corp environment with mercurial as a forked version and I can't edit the commit... yet). I will squash/edit the commit and remove it if there is interest in this addition.

I figured out a simpler way that requires less code if you want to get the dependency to SLF4j:
package com.netflix.archaius.api.log;

import java.util.ServiceLoader;

import org.slf4j.ILoggerFactory;
import org.slf4j.Logger;
import org.slf4j.helpers.NOPLoggerFactory;

public interface LoggerService {

	public static class InternalLoggerFactory {

		/*
		 * Simply prefix Internal in front of LoggerFactory:
		 * So instead of:
		 * Logger logger = LoggerFactory.getLogger(MyClass.class);
		 * It should be:
		 * Logger logger = InternalLoggerFactory.getLogger(MyClass.class);
		 */
		public static Logger getLogger(Class<?> clazz) {
			return getILoggerFactory().getLogger(clazz.getName());
		}

		public static ILoggerFactory getILoggerFactory() {
			return LazyHolder.INSTANCE;
		}

	    //We should not load unless we are requested to. This avoids accidental initialization. @agentgt
	    //See https://en.wikipedia.org/wiki/Initialization-on-demand_holder_idiom
		private static class LazyHolder {
			private static final ILoggerFactory INSTANCE = InternalLoggerFactory.createFactory();
		}

		private static ILoggerFactory createFactory() {
			/*
			 * You could also use a system property or static variable for resolution as well.
			 * The following looks for a file located here:
			 *  /META-INF/services/LoggerService.getPackage().getName()
			 * With the name of the class as a single line that implements LoggerService.
			 */
			ServiceLoader<LoggerService> loader = ServiceLoader.load(LoggerService.class);
			for (LoggerService ls : loader) {
				return ls.createLoggerFactory();
			}
			return new NOPLoggerFactory();
		}

	}

	public ILoggerFactory createLoggerFactory();

}