proposal: add a set data type

A set data structure, similar to the one in Python, would be a useful addition. For example, it is sometimes required to ensure no duplicate values exist in a list, for example, and a set is the most ergonomic solution.
names = ["Thomas", "David", "Michelle", "David"] # contains duplicate names
unique_names = set(names) # building a set from the list removes duplicates

Other common use cases are:

Efficiently checking for membership
Filtering
Performing mathematical operations (difference, intersection, symmetric difference, union...) among sets

Thoughts? Should I make an attempt at writing a proposal?
Use case example
As an example, I have run into this need while adding automatic dependency exploration in my fork of kklochkov/rules_qt, a ruleset for building Qt applications with Bazel. When generating a rule instantiation, the deps attribute cannot contain duplicate values. Because my feature analyzes Qt shared libraries in the system, and they can be duplicated with different names (for example, libQt6Quick.so and libQt6Quick.so.6.4.3) This introduces the need to enforce each dependency is only added once. Of course, there are ways to work around this problem, but it would be easily solved with a set.

The standard recommendation thus far has been to use a dict with None as the values. I've used that in practice and while it's not quite as nice, it's perfectly workable.

@dieortin @ndmitchell It's already half-done in Go: https://github.com/google/starlark-go/issues/492

@suganoi that's nice! I have also just seen https://github.com/bazelbuild/starlark/issues/20, but it doesn't seem to include the existence of set.
IMO the set API selected for the Go version makes sense and should be added to the general spec. @laurentlb what do you think?

For the record, the example above can be written:
names = ["Thomas", "David", "Michelle", "David"] # contains duplicate names
unique_names = {n: None for n in names}.keys()

In many cases, people want sets just to remove duplicates; this workaround may be sufficient for that use-case.
In Bazel BUILD files, there's a tradition of using lists in most places. For example, deps and srcs are lists, even when the order is not relevant and duplicates are forbidden. In Bazel rules, sets should usually be avoided, and depsets should be used most of the time. So there were concerns that adding a native type set could cause more problems to Bazel. When a set is really needed in Bazel, a set implementation is provided in skylib (https://github.com/bazelbuild/bazel-skylib/blob/main/lib/new_sets.bzl).
As mentioned previously, Starlark-Go has a implementation for sets (https://github.com/google/starlark-go/blob/master/doc/spec.md#set - https://github.com/google/starlark-go/blob/90ade8b19d09805d1b91a9687198869add6dfaa1/starlark/library.go#L990).

I'm not opposed to a set data type, although if we do add it, I think we ought to also support the literal {foo, bar, ...} syntax. I regularly field questions from new macro and rule authors asking for where is Starlark's set data type :) In Bazel, it would entail a bit of work to chase down the native methods that currently require a starlark list as argument but which could also take a set as argument where it makes sense. And of course we'd need clear documentation for when to use sets vs. depsets.

I think we ought to also support the literal {foo, bar, ...} syntax

This is not as easy decision: people constantly make mistakes by writing {} assuming it is an empty set (and in many cases it behaves like empty set, e.g. in in operator or iterator, making it harder to debug). And writing set([foo, bar, ...]) is OK-ish, and has no perf difference if optimized properly.
I suggest to have separate issues/discussions for set() builtin, and {...} syntax for sets.

Given the discussions ... is there any status on the set data type feature?

@tomaspipes - given the positive reaction from the community here and elsewhere, I want to take a few days this summer to add a set data type to the Java implementation, and have it enabled in Bazel 8. The Go implementation already has set behind a flag, we may want to flip the flag to enabled.

Didn't have time to look at this in summer - but I finally wrote an experimental implementation for Java / Bazel: https://bazel-review.git.corp.google.com/c/bazel/+/263411
In light of this, let's hammer out a language spec. Current feature matrix:

comparison operators implement a partial order via subset relation

Supported: python3, starlark-go
Not supported: starlark-rust
Undecided: bazel

update() method

Supported: python3, starlark-rust, bazel
Not supported: starlark-go

intersection_update(), difference_update(), symmetric_difference_update()

Supported: python3, bazel
Not supported: starlark-go, starlark-rust

Multiple-argument form of union(), intersection(), difference() (and corresponding _update methods, if implemented):

Supported: python3, bazel
Not supported: starlark-go, starlark-rust

For the spec, I propose the following:

Do not support comparison operators - their behavior is surprising/confusing
Support update(), intersection_update(), difference_update(), symmetric_difference_update() - since these are generally useful, easy to implement, and help memory efficiency
Not sure about multiple-argument form of union(), intersection(), difference() etc. - these are generally useful, but while they are completely trivial to implement in java, it seems that it would be rather awkward to add them starlark-go (due to how starlark-go does its argument parsing for builtins), so perhaps we can live without them. (Did not look at starlark-rust.)

Proposed spec (with multiple-argument form of union() etc.): https://github.com/bazelbuild/starlark/pull/290


dom4j has a security vulnerability

Details of CVE-2018-1000632 security vuln. Fix is to upgrade to 2.1.1 or greater. Mentioned by a user in JanusGraph/janusgraph#1342

fixed in 0.9.12


Use python function as go function

I'm trying to implement a simple HTTP server, but it seems I can't send a python function as a go function to HandleFunc.
from __go__.net.http import ListenAndServe
from __go__.githubcom.gorilla.mux import NewRouter
from __go__.fmt import Fprintf

def HomeHandler(w, r):
    Fprintf(w, "Hello world")

r = NewRouter()
r.HandleFunc("/", HomeHandler)
ListenAndServe(":8000", r)

I'm receiving this error:
$ cat web.py | make run
TypeError: cannot convert grumpy.Object to func(http.ResponseWriter, *http.Request)
exit status 1
make: *** [run] Error 1

Yeah, this used to work but I think it got removed as part of some other refactoring. I'll spend some time getting it working again.


Make LocalizeReads optional

The LocalizeReads task was recently introduced to GatherSampleEvidence to simplify cases for CRAMs sourced from requester-pays and multi-regional buckets. This simplified the code quite a bit. However, it would be beneficial in some cases to be able to bypass this for some cost and time savings. Adding an optional boolean skip this would be easy to implement.

Addressed in #620


Fix SegmentBounds's ofs

May cause some 6xx idb can't extract_function_names

I confirm it fixes the problem.


{AKS} Remove deprecated code

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

Remove v1 decorator.
Fix model imports in custom.py.
Sort out imports and remove useless code.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
The precondition is to put your code inside this repository and upgrade the version in the pull request but do not modify src/index.json.

AKS


NoCode log error

I tried to check the log, but file has only this content:

I spend two days and did not found any solution.

Try changing

to this

Should work fine now

Tried and shows me this:

Thanks, my issue is solved :dancer:

This is tough one. You are using StackOverflow to solve this ?

I just ran into this... I don't know if it's because I use nocontainers or nologging?
Can we reopen this?


Not using docker, website detects no linked mentions

Hello there,
First of all, great project! Fantastic work pulling this all together.
I'm trying to run it on a server of mine without docker, I pointed an apache server to the perfile directory and put the Demo vault in there. The website runs just fine but it doesn't detect any linked mentions between documents. Any idea why that is?
The image is exemplifier of the problem:

Just set $rootDir = 'Demo'; in the helper.php file so that metadata.json is in the root folder.


docs: upgrade to Sphinx 4.3

Trying to fix breakage in CI due to docutils 0.18 incompatibility.

The newer Sphinx works fine, and more importantly it constrains the version of docutils so that pip picks 0.17 as desired:
Collecting docutils<0.18,>=0.14
  Downloading docutils-0.17.1-py2.py3-none-any.whl (575 kB)

which lets the check-docs job pass in CI.


Support other fingerprint forms for the RDKit fingerprint

There has been no discussion or further requests for this enhancement in the past 5 years. Closing as "won't fix"


Update runbooks based on downstream wording

What this PR does / why we need it:
There is some wording on downstream runbooks that we can move to the upstream runbooks to make them more similar
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to kubevirt-dev was considered

Release note:

Update runbooks wording

/cc @ousleyp

/lgtm


Fixed #33061 -- Fixed handling nonexistent keys with negative deltas in incr()/decr() in memcached backends.

This PR makes sure a ValueError is raised when a user tries to increment or decrement the value of a key that does not exist.
According to the ticket (33061), this may or may not have been true before, but now should always be true.
Here are the relevant docs stating the intended behavior. Specifically, this sentence was brought up in the ticket discussion as relevant:

A ValueError will be raised if you attempt to increment or decrement a nonexistent cache key.

The ticket has some more context if anything is unclear 🙂

I had a little bit of trouble running the right tests locally:
❯ ./tests/runtests.py cache.tests.PyMemcacheCacheTests
Testing against Django installed in '/Users/sondrelg/Documents/django/django'
Found 58 test(s).
Creating test database for alias 'default'...
System check identified no issues (0 silenced).
ssssssssssssssssssssssssssssssssssssssssssssssssssssssssss
----------------------------------------------------------------------
Ran 58 tests in 0.001s

OK (skipped=58)
Destroying test database for alias 'default'...

For anyone reviewing this, do you know (off the top of your head) how to enable a specific cache backend in the test settings?

For anyone reviewing this, do you know (off the top of your head) how to enable a specific cache backend in the test settings?

You need to install memcached and pylibmc/pymemcache locally, and define a CACHES setting that points at your memcached instance, see docs.

It was defining the CACHES setting I was a little bit confused by, but I ended up just changing global_settings temporarily and that at least did the trick. Thanks for the feedback 🙂
With PyMemcacheCache enabled, the first commits regression tests fail as intended in 94d7c2a04d8c4136a6f4590a2722753 👍
❯ git checkout 94d7c2a04d8c4136a6f4590a2722753d8e1d2f37
Note: switching to '94d7c2a04d8c4136a6f4590a2722753d8e1d2f37'.

...

HEAD is now at 94d7c2a04d Refs #33061 -- Add regression test

❯ ./tests/runtests.py cache.tests
Testing against Django installed in '/Users/sondrelg/Documents/django/django'
Found 546 test(s).
Creating test database for alias 'default'...
Creating test database for alias 'other'...
System check identified no issues (0 silenced).
..............................................................................................................................................................................ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss...............ss..F.................F..................s.......................................................................................................................................................................................................
======================================================================
FAIL: test_decr (cache.tests.PyMemcacheCacheTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/sondrelg/Documents/django/tests/cache/tests.py", line 398, in test_decr
    cache.incr('does_not_exist', -1)
AssertionError: ValueError not raised

======================================================================
FAIL: test_incr (cache.tests.PyMemcacheCacheTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/sondrelg/Documents/django/tests/cache/tests.py", line 382, in test_incr
    cache.incr('does_not_exist', -1)
AssertionError: ValueError not raised

----------------------------------------------------------------------
Ran 546 tests in 86.253s

FAILED (failures=2, skipped=119)

@sondrelg Thanks :1st_place_medal:  Welcome aboard :boat:
@cjerdonek Thanks for the review :+1:


Set up CI/CD in GitHub

Resolves #8.

The build is currently failing. It should pass once https://github.com/Australian-Genomics/CTRL/pull/10 is merged and I rebase on main.


General polish and simplification

Simplifies the Readme by removing need for db instructions
Consolidate the controllers, views and routes into application controller for simplicity
Removes some of the scaffolded stuff
Removes included sqlite database
Adds some instructions and links for testing on the index page

Ok, fixed up the urls being generated in the lti xml by creating a named route and using the routes_helpers in those views.
Some other minor polish:

line returns at the ends of several files
more accurate titles when referencing the name of the project
changed route to use rails preferred match (due to launch responding to get and post)
added some more stuff to the git ignore
removed unused stuff from the lti_config


Bump decompress from 4.2.0 to 4.2.1 Port to release

Bumps decompress from 4.2.0 to 4.2.1.

Release notes
Commits

Signed-off-by: dependabot[bot]<EMAIL_ADDRESS>Co-authored-by: dependabot[bot]<EMAIL_ADDRESS>

@shigupt202 you need to locally run npm install --production to ensure the package is actually updated in the node_modules


Return filename from UseTempLogFile()

This is related to a comment that @owenwaller left in his updated hugo/utils_test.go: https://github.com/spf13/hugo/pull/818
Is modifying UseTempLogFile() so that it returns the temp filename a change you would support? If so I can make a pull request.

My gut feel would be this....
If jww created the file - as is the case of UseTempLogFile() or
SetLogFilePath() then jww is responsible for that file. So jww
should ensure that the file is properly closed.
If jww is passed a *File to use as the log file (if this is indeed
the case) then jww is not responsible for the *File its the callers
responsibility, and they must Close() it.
In terms of returning the filename form UseTempFileName yes, I'd
support it :) It would simplify the test in question - spf13/hugo#818
But there's also I few other minor changes that I can think off as well

such as removing the fmt.Printf's in the package or at least being
able to turn them off.

So if you want to generate a pull request for the file name change, I
can build on that to do the other minor changes,
Owen
On Thu, 2015-02-19 at 15:39 -0800, Joel Scoble wrote:

This is related to a comment that @owenwaller left in his updated
hugo/utils_test.go: spf13/hugo#818
Is modifying UseTempLogFile() so that it returns the temp filename a
change you would support? If so I can make a pull request.
—
Reply to this email directly or view it on GitHub.

--
Dr. Owen Waller
Head of Development
Kulawe Limited
Forsyth House
Cormac Square
Belfast
Northern Ireland
BT2 8LA
+44 (0)757 882 9933
<EMAIL_ADDRESS>www.kulawe.com
Company Number: NI604010
VAT Number : GB 122 6319 42

After investigating this further, I'm not sure this is really needed. If the name of the file created by TempLogFile() is needed, it can be obtained by:
LogHandle.(*os.File).Name()
While it may be useful to a user of jww to have the created filename returned, it is something that can be obtained  with another line of code and some assertion.
This is a decision I will leave to Steve. I this is something that should be supported I will make a pull request, otherwise this issue can be closed.
It should be noted that such a change would not affect existing code.

I agree. Given that we can access the file handle via the exported LogHandle variable then I don't see any point in returning it.
But looking at the public interface again though it still doesn't feel right.
We have both the SetLogFile() and UseTempLogFile() which are basically "Open" or "Create" functions. But there's no corresponding Close() function. We are expecting the user to remember to do this, and to do it via the exported LogHandle. There is the DiscardLogging function which could be mistaken for a Close() function, but it isn't and that's not its intent.
Maybe the simplest thing we can do is just to add a Close() function. At least then it is obvious to a user of the package that they need to so something to stop the logger cleanly.

Well just adding a Close() function isn't as simple as one may think. First the LogHandle must get something else then, even if it is just an ioutuil.Discard. Also if you add Close() then the SetLogFile() and UseTempLogFile() need to be modified. It starts getting a little complex and ugly.
I started thinking about this for the Hugo issue that spawned this, until casting the LogHandle interface to access the *os.File's Close() method was used, and I wasn't satisfied with any of the implementations that I came up with. I didn't spend very long on it though.
As jww is currently written, I'm not sure there is a pressing need for Close(). I can think of one scenario where it might be useful, when logging to a temp file on application start-up and then switching to the configured application log file once the ocnfiguration has been read, but that adds its own issues and I'm not sure about supporting that scenario.
I have been toying with the log flow described above and haven't been satisfied with anything I've done. I've been thinking about adding it to a custom branch of jww, but haven't gotten beyond contemplating it.

I will soon remove this method and replace it with a new method that takes an io.Writer.


MySQL database is destroyed if MySQL workspace service is updated

Issue
If you update the MySQL workspace service it will destroy and recreate the attached MySQL database.
This also occurs with Gitea as it creates a MySQL database.
This occurs on current main
Example with the MySQL workspace service:
1. Install the MySQL component:
Porter logs show the following:

2. Update the MySQL component (clicking the three dots, then Update in the UI):
Porter logs show the destruction of the database:

Please note this issue exists in:

MySQL workspace service
Gitea shared service


Fix Bug (issue #51)

I won't change it this way because it won't work for nested folders.

I won't change it this way because it won't work for nested folders.


fix: test error in worker test

Description
try to fix test error in worker test

Additional context

What is the purpose of this pull request?

[x] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

https://github.com/vitejs/vite/pull/7518/commits/52aceaaa61396fe4ba3640d65f886bcdb8a68b6b
after move worker.spec.ts into dirs.
https://github.com/vitejs/vite/pull/7518/commits/3e63af1a03b7282b7f18c9109a7e212ffdc0aa9b
I don't know why, but it seems to resolve the test issues. 🫣


Restrict IAM policy to not allow write access without constraints

Feature scope
BitmapWidget
Describe your suggested feature
Hello,
When creating a dynamic dashboard factory as per Custom dashboards section it seems that behind the scenes an IAM policy that allows write access without constraint (logs:PutRetentionPolicy, logs:DeleteRetentionPolicy) is created which fails a Checkov static code analysis check (CKV_AWS_111) 'Ensure IAM policies does not allow write access without constraints'. This policy can be seen in BitmapWidget.test.ts.snap
ASK:

Limit the scope of this Log retention IAM policy to just affect the Lambda function log groups (which I assume its interacting with) for better security compliance / enable passing of Checkov static code analysis checks

Partial Checkov Output
{
    "check_type": "cloudformation",
    "results": {
        "failed_checks": [
            {
  		"check_id": "CKV_AWS_111",
                "bc_check_id": "BC_AWS_IAM_57",
                "check_name": "Ensure IAM policies does not allow write access without constraints",
                "check_result": {
                    "result": "FAILED",
                    "evaluated_keys": []
                },
                "code_block": [
                    [
                        221,
                        "  \"LogRetentionaae0aa3c5b4d4f87b02d85b201efdd8aServiceRoleDefaultPolicyADDA7DEB\": {\n"
                    ],
                    [

                    ...
				"resource": "AWS::IAM::Policy.LogRetentionaae0aa3c5b4d4f87b02d85b201efdd8aServiceRoleDefaultPolicyADDA7DEB",
				...
                "check_class": "checkov.cloudformation.checks.resource.aws.IAMWriteAccess",
                "guideline": "https://docs.bridgecrew.io/docs/ensure-iam-policies-do-not-allow-write-access-without-constraint",
	...
}

Thanks!

Hi, bitmap widgets rely on a Lambda function to do the rendering, and Lambda functions have these roles automatically created by AWS CDK.
You can refer to https://github.com/aws/aws-cdk/issues/11878 and the other linked issues there to learn more about why they're as permissive as they are.


Audiobook support phase 1: DB representation

In an effort to avoid major breaking changes down the road, I'll plan to add DB-level support for audiobooks alongside #196. For context as to why or how this makes sense, read this comment: https://github.com/stumpapp/stump/issues/196#issuecomment-1902759400

This is probably a little early on. But if you add audiobooks and epubs together, there is a FOSS program called Storyteller that can overlay the two. Similar to Amazon's whisper sync. That would be a nice addition

I'll look into it a bit closer to when this will be worked, sounds neat - thanks! I assume you mean this

That is correct


Codable Range proposal

Full proposal version of #914

@airspeedswift is there anything else that I can do to help push this further along?

@dlbuckley The proposal is described as a "purely additive change", so my guess would be Swift 5.1, but that decision is nothing to do with me.
@airspeedswift Conditional conformance collisions might be a problem.

@airspeedswift other people having written their own implementations of this is indeed an issue when updating to a newer version of the language with this included.
We actually had an issue recently where we were encoding values of Measurement type, and while the encoded data was correct, it was a pain to query in mongo. What we ended up doing was wrapping up all uses of Measurement in the Encode/Decode methods where it was used. This allowed us to use our own method of encoding and decoding Measurement types.
While that example was a work around, I do wonder if this highlights an extension point in Encoder/Decoder that allows for registering custom encode/decode methods for a specific type which then ignores the default Codable conformance of the type. Maybe this is something that @itaiferber can chime in with here?
As for the suggestion of first trying to decode the type with an unkeyed unarchiver and then trying again with the keyed unarchiver; I think there are a number of risks with that. Firstly, how do you know which keys that are being used? In my first version I used keys that helped to distinguish between all of the different Range types, but I know other extensions have just kept to the names of the properties (upperBound and lowerBound). The biggest problem I see is that if the data is read in from the keyed format, and then saved out as the unkeyed format, it could break whatever is relying on that data.
I think we are now past the point where this can be added in without causing a number of headaches. We just need to decide if causing the headaches is worth it, or it's best to leave Swift without the 'batteries-included' implementation of the Range types.

We're still in early days of Swift, so I think it would be a mistake to just give up on doing this permanently.
With respect to the extension point on Encoder for custom types, it was always our view that the way to do this in general was by making a wrapper struct for your type. I think it's still pretty important to the design of Codable to preserve encapsulation as much as possible. We made exceptions for a few types in various encoders like JSONEncoder because of the prevailing conventions of data encoded in those formats (e.g., URL as a single String, in that case, or Date stored as ISO8601).

As far as existing extensions go, I agree with @parkera. It's never been safe to extend others' types with Codable, and will never be safe: the only right thing to do is to create wrapper structs around others' types which you control (@dlbuckley mentions with Measurement). This is something I've mentioned a lot in discussion, but it's not something we can really force folks to do. (We could technically prevent extension Foo : Encodable and extension Foo : Decodable if Foo is defined outside of the current module, but not without a ton of breakage, and kludge in the compiler.)
So I think we need to consider to what extent we are worried about extensions like this. No matter what we do, adopting Codable on the Range types is going to be a source-compatibility issue for others. I personally thing that the right thing for them to do at that point is to resolve the source-breakage by going and wrapping their existing Codable ranges with the wrapper types that maintain their format. Or, if they really care to, they can keep their overriding implementations of init(from:) and encode(to:) and those keep working for them within their modules. (I would say this is brittle and pretty wrong, but it is at least easy.)
As for allowing the defeat of Codable implementations in general as an extension point on Encoder/Decoder — we discussed this during the initial design but decided pretty strongly against it; ignoring the design constraints of now forcing this capability on all Encoders and Decoders, there's a fundamental encouragement to breaking encapsulation that that facility offers. We break this already for some types with JSONEncoder in highly targeted cases, but even that feels wrong in a sense. (The philosophically-consistent solution might be to instead offer Codable wrappers for these types, like ISO8601CodableDateWrapper or something.)
In any case, I don't think we can start guessing at others' representations for Range and the like — as flexible as Codable is, we can't guess at keys used in keyed containers, or how to decode something like [12, 57, 96, 22].

We're still in early days of Swift, so I think it would be a mistake to just give up on doing this permanently.

I agree, and there's also a significant benefit to doing it in 5.0 to avoid having to gate on OS version to use it if we add it in the future.
I think a best efforts approach would be reasonable here. It's actually perfectly acceptable IMO to break code that had conformed std lib types to Codable manually. It's not OK to conform a library's types to that same library's protocols for exactly this reason. It's just nice of us not to if possible, depending on the combination of circumstances.

@dlbuckley

As for the suggestion of first trying to decode the type with an unkeyed unarchiver and then trying again with the keyed unarchiver; I think there are a number of risks with that. Firstly, how do you know which keys that are being used?

Since we're talking about the range, where the lower bound should be less than or equal than the upper bound, we don't really care about the exact values of the keys. It should be possible to just obtain all the keys, try them, and then assign the smaller value to lower bound. I'm not too comfortable with Codable to know for sure if it's at all possible to obtain all the values from a keyed container without specifying the keys, though.

Since we're talking about the range, where the lower bound should be less than or equal than the upper bound, we don't really care about the exact values of the keys. It should be possible to just obtain all the keys, try them, and then assign the smaller value to lower bound. I'm not too comfortable with Codable to know for sure if it's at all possible to obtain all the values from a keyed container without specifying the keys, though.

Unfortunately it's not possible to just obtain all of the keys like that. Due to the nature of Codable you need to specify the keys you expect when getting the keyed container. Using the allKeys property on a keyed container only returns all of the keys you give it, not the other way around.
I've updated the PR with a change that was requested by @moiseev last week which hopefully mitigates his concerns around decode error handling.
@itaiferber thanks for chiming in. I totally agree with you and @parkera regarding the reasoning around protecting encapsulation here. I was simply thinking out loud on if there was a way around it to be nice to people who have already gone down the avenue of their own implementations.

Unfortunately it's not possible to just obtain all of the keys like that. Due to the nature of Codable you need to specify the keys you expect when getting the keyed container. Using the allKeys property on a keyed container only returns all of the keys you give it, not the other way around.

@dlbuckley Just FYI, that's not strictly true — you can get all of the keys in a given keyed container by getting that keyed container with a key type that allows any String or Int value. This is how Dictionary decodes itself, using _DictionaryCodingKey

This proposal is now going to be run through a review.  I will merge and patch up the document for review.
Given the updates @airspeedswift and @moiseev have done on this proposal as well, I think it makes sense to add them as proposal authors as well to address any questions related to technical concerns and data compatibility issues.


Should "latest" Docker image be the portable image (it is since last release)?

Currently the Docker CI setup is unclear, and the portable build-and-push step is overwriting the latest image with the portable image.
Do we want the latest image to be the portable image?

If yes, then we should disable the latest tag for the non-portable image build step
If no, then we should disable the latest tag for the portable image build step

closing, latest is the portable build, starting at mev-boost v1.4.0


Some problems of flow_warp.py

I saw the flow_warp.py and was confused of the code annotation （w,h,2）：
 grid_y, grid_x = torch.meshgrid(torch.arange(0, h), torch.arange(0, w))
 grid = torch.stack((grid_x, grid_y), 2).type_as(x)  # (w, h, 2)

I try to see the dimension of grid and got （h,w,2）.Is there something wrong?

(h, w, 2) is correct. It is the comment that is wrong. Thanks for letting us know.

Fixed in #655, thanks!


Update spfx-doctor.mdx

add npm install command

Hi @bforsyt4
Could you explain a bit why you added this section to the docs of this command? According to me it's not really related to the comand.

I believed this to be the related install command in order to use spfx-doctor. Please correct me if I am wrong.
Thanks,
Brian Forsythe
Document Collaboration Services
Technology Management Specialist, Rally Process Coordinator
<EMAIL_ADDRESS>From: Milan Holemans @.>
Sent: Thursday, September 14, 2023 5:05 PM
To: pnp/cli-microsoft365 @.>
Cc: Forsythe, Brian (D.) @.>; Mention @.>
Subject: Re: [pnp/cli-microsoft365] Update spfx-doctor.mdx (PR #5488)
WARNING: This message originated outside of Ford Motor Company. Use caution when opening attachments, clicking links, or responding.
Hi @bforsyt4https://clicktime.symantec.com/15uBY4EwHKqYEvAMvcygL?h=GUTVycv7Iyqqvu4ZHuuh_W65t0imR0I_u4cgaVFpyRY=&u=https://github.com/bforsyt4
Could you explain a bit why you added this section to the docs of this command? According to me it's not really related to the comand.
—
Reply to this email directly, view it on GitHubhttps://clicktime.symantec.com/15uBhidWCZCj4opD1jmya?h=oG8CitCAQMqbkFi-eiQ3sIN_Jx4eLmeXc5u7XqRwwB4=&u=https://github.com/pnp/cli-microsoft365/pull/5488%23issuecomment-1720150996, or unsubscribehttps://clicktime.symantec.com/15uBctSDjwX8erzHUBNpx?h=5iUYLtnJoVe7zBfkuV3RIvl5EgTd2Zj9S8hOJ_rR_lI=&u=https://github.com/notifications/unsubscribe-auth/AJ3N762FRYS5S2S6OIKZAZTX2NWP7ANCNFSM6AAAAAA4YOZOPQ.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

You are correct, but you must do this to run any command. We have a dedicated section on installing CLI for Microsoft 365 on our home page and user guide. This should be sufficient, there is no need to repeat this on every command page.
It's like you are using Photoshop and use a manual to work with it. This manual also won't tell you how to download Photoshop in every chapter.
If you would like to contribute you can always go to our issue list and filter on the labels help wanted and good first issue. These issues should be good to get started. I will close this PR.


Datastore Key isn't in the left-navigation

To get to the Key documentation (http://googlecloudplatform.github.io/gcloud-ruby/docs/master/Gcloud/Datastore/Key.html) you have to find a link to it somewhere.
Any chance we could add it to the left nav?

Yes, Key was originally in the left nav, but I removed it to closer match the gcloud-node left nav. I'll add it back.

The key left nav is now there for both master and v0.1.0.


BUG - String subtraction in aa_doprocessing

The following code in aa_doprocessing appears to contain a bug. TODO: Check whether indeed bad.
msg(1:length(msg-2)) is probably meant to be msg(1:length(msg)-2)
        if (strcmp(task,'doit'))
            if (alldone)
                aas_log(aap,false,sprintf('- done: %s for all %s',description,domain));
            else
                if (length(msg)>2)
                    msg=msg(1:length(msg-2));
                end

It is a bug, indeed. Good catch!


Project-Stats CI Workflow failing due to merge conflicts

Description
The Project-Stats CI Workflow has been failing since yesterday.
The first failure shows the error:
To https://github.com/newrelic/opensource-website
 ! [rejected]            master -> master (fetch first)
error: failed to push some refs to 'https://github.com/newrelic/opensource-website'
hint: Updates were rejected because the remote contains work that you do
hint: not have locally. This is usually caused by another repository pushing
hint: to the same ref. You may want to first integrate the remote changes
hint: (e.g., 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.
Error: Process completed with exit code 1.

Subsequent failures then all show a variety of merge conflicts, for example:
CONFLICT (content): Merge conflict in src/data/project-stats/newrelic-docs-website.json
Auto-merging src/data/project-stats/newrelic-developer-website.json
CONFLICT (content): Merge conflict in src/data/project-stats/newrelic-developer-website.json
Auto-merging src/data/project-stats/newrelic-demo-deployer.json
Auto-merging src/data/project-stats/newrelic-centurion.json
CONFLICT (content): Merge conflict in src/data/project-stats/newrelic-centurion.json
error: could not apply 64e6df4ed... chore(stats): updated project stats files
hint: after resolving the conflicts, mark the corrected paths
hint: with 'git add <paths>' or 'git rm <paths>'
hint: and commit the result with 'git commit'
Error: Process completed with exit code 1.

this is not the first time this has failed for that reason. i think the workflow just needs a git pull when committing to the master branch.
also, im not sure if this qualifies as a bug since this is all internal code, and not product facing.


Console not loading, including backup links

Description
Console including backup links is receiving the error "upstream timeout".
Steps to Reproduce

Go to console
Click on the main console link (https://vegafairground.eth.limo/) or backups

Screenshots

The same is true for Mainnet as well
https://vegaprotocol.eth.limo/

This appears to have been a temporary availability issue - web gateways were timing out finding the content on IPFS.


diff (staged) is empty

Hey!
I've started to use lumen, and if it works perfectly, I have a strange error.
PS R:\IUT_Code\S3\24hmans> lumen draft
error: diff (staged) is empty

As you can see, it doesn't detect any changes. But when I run git diff:
PS R:\IUT_Code\S3\24hmans> git diff
diff --git a/frontend/src/views/HomeView.vue b/frontend/src/views/HomeView.vue
index c774958..8567b9c 100644
--- a/frontend/src/views/HomeView.vue
+++ b/frontend/src/views/HomeView.vue
@@ -1,112 +1,112 @@

...

Reloading the cache of git didn't worked.
Also, I found it pretty strange that the lumen explain --diff command works

Hi, did you stage the changes? For example using git add .

Yes I did, it was one of the first things I checked. What's weird is that sometimes it works


use PointerEvent instead of MSPointerEvent if supported.

Please don't edit the concatenated output files, but the source files.

going to close this since it has not been updated as requested


MediaProjection shows up red after stopping the service

After running the app, there's a red MediaProjection icon that doesn't disappear.

Only force quitting the app removes the icon, which breaks the accessibility setting.

Also, is there a way for me to test bug fixes without installing a 2nd version of the apk? I can't replace your version with mine because it's not signed with the same certificate.

Also, is there a way for me to test bug fixes without installing a 2nd version of the apk? I can't replace your version with mine because it's not signed with the same certificate.

I think that is intended behaviour. Release versions of an application should be signed with a different key from the Debug builds.

And do you have some tutorial for Xamarin? I'm currently struggling to find the connections between the different kind of files.
Every tutorial I've seen starts with a Layout with some buttons, but your Settings Layout is almost empty.

Actually, you don't need to know much about Xamarin. I've not used the Xamarin.Forms library here, only Xamarin.Android, which is pretty much a wrapper around the android library. There are a few minor differences, but basically it's like you're writing Android apps in C#.
The difference in the Settings layout is that it uses the Android Preference library, specifically AndroidX Preference library (for compatibility across various versions of Android).
Preference library allows us to create settings UI pretty easily without worrying much about how they are store, how they are displayed. Android handles that for us.
I'd suggest looking about Android in general. I'm doing the same and just translating it to C#.
I prefer C# over JAVA, that's why I picked Xamarin.


Copy docker-compose file to host during quickstart

This copies the docker-compose file to the host during the quickstart
script. This allows to later change paramters to containers and also the
used images.
This makes the quickstart script configurable based on the
docker-compose file used, you can change the name of the install folder,
and you can change the project name used by docker-compose.
To not just simply override user changes, we give him the chance to show
a diff.

@jannikluhn Is that solving your configuration issue? This way you can not really configure before running the quickstart, but after it is setup, you can just change the docker-compose file.

Yes, this would have solved the problems I had.

Codecov Report

Merging #486 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master    #486   +/-   ##
======================================
  Coverage    92.2%   92.2%
======================================
  Files          17      17
  Lines         872     872
======================================
  Hits          804     804
  Misses         68      68

Flag
Coverage Δ

#bridge_end2end
85.77% <ø> (+0.22%)
:arrow_up:

#bridge_unit
76.14% <ø> (ø)
: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 2e972c8...ada3a41. Read the comment docs.


Consider ROR for organizational entities

https://ror.org/
We have found great inconsistencies across different venues for contributor orgs. ROR is not perfect but it helps ;-).

We probably need to find a way to give multiple PID for both organisation and people.
In particular, orcid is not using ROR, is it?

Agree, the model should provision for 1...n person PIDs, and perhaps 0...n org PIDs.
ORCID was planning to use ROR and has been a contributor and partner in design; conversations have been going on for >5 years so I'm hoping recent advances in tech and governance for ROR will push us over the edge!

in #17, we have (following jats4r)
PID:
      type: RINGGOLD
      id: 9373

Will it allow multiple elements by having multiple PID elements, or should we nest multiple elements in the PID entry ?

I think we are seeing some overlaps with regard to the ID systems, right? I'll just drop my idea in here for completion, but we might want to center the author and affiliation-id discussion around one single issue…?
affiliation:
  - name: institution name
    ringgold-id: asdf
    ror-id: wasd

This way the parser could just save all available IDs, if there are any, which would solve them being optional (if no ID-properties are defined, then there is no ID), as well as stackable (all available IDs can be stored internally in the parser using any arbitrary AST)

indeed solved in #20


:SwitchReverse gives me \bprivate\b

:Switch works great for me now.
But :SwitchReverse gives me \bprivate\b

Ah, good catch. I can reproduce that issue. Let me work on a fix.

@huyz I think I fixed the issue. Could you upgrade your plugin to version 1.0.1 and let me know if it works for you?

Works, thank you


Revert "Change comments to Doxygen friendly format"

Reverts WSU-CEG-6110-4410/UncleBuck-sCraft#13

Merged incorrect branch... disregard


--set-file and []uint8 type for content instead of string

werf uses []uint8 type for file contents instead of the string that helm uses.
There is a sample chart for example:
chart.yaml:
apiVersion: v2
name: werf-setfile-test
description: A Helm chart for Kubernetes
type: application
version: 0.1.0
appVersion: "1.16.0"

templates/configmap.yaml:
apiVersion: v1
kind: ConfigMap
metadata:
  name: test
data:
  file.txt: |-
{{ .Values.file | indent 4 }}

Helm successfully deployed this chart:
% helm upgrade -i --set-file file=test.txt werf-test .
Release "werf-test" does not exist. Installing it now.
NAME: werf-test
LAST DEPLOYED: Wed Feb 16 15:00:50 2022
NAMESPACE: default
STATUS: deployed
REVISION: 1
TEST SUITE: None

but werf returns an error:
% werf helm upgrade -i --set-file file=test.txt werf-test .
Release "werf-test" does not exist. Installing it now.
Error: template: werf-setfile-test/templates/configmap.yaml:7:25: executing "werf-setfile-test/templates/configmap.yaml" at <4>: wrong type for value; expected string; got []uint8

As workaround I can cast file content variable to string using print function, but I think herl and werf behaviour for --set-file directive must be the same.

Confirmed, results in []uint8 (like [116 101 115 116 46 116 120 116 10]) even with werf render/converge.
Thanks, we'll fix this.


FR: Double click to open folder note

I wonder if it'd be feasible to allow for double click to open the folder note of the folder clicked on if it exists. Thanks for the awesome plugin! :D

Obsidian (and browsers in general) don't have a standard way to detect double clicks.  But double-Enter will do this from the keyboard, since the folder note gets selected when you enter a folder (unless it's the folder you opened QE from, in which case you need to do Home-Enter).


Outer-most context linewraps over inner contexts

If I have a function:
PetscErrorCode CreateOperatorForDomain(Ceed ceed, DM dm, SimpleBC bc,
                                       CeedData ceed_data, Physics phys,
                                       CeedOperator op_apply_vol,
                                       CeedOperator op_apply_ijacobian_vol,
                                       CeedInt height,
                                       CeedInt P_sur, CeedInt Q_sur,
                                       CeedInt q_data_size_sur, CeedInt jac_data_size_sur,
                                       CeedOperator *op_apply, CeedOperator *op_apply_ijacobian) {
//[..........]
  if (phys->has_neumann || 1) {
    // --- Setup
    ierr = DMGetLabel(dm, "Face Sets", &domain_label); CHKERRQ(ierr);

    // --- Get number of quadrature points for the boundaries
    CeedInt num_qpts_sur;
    CeedBasisGetNumQuadraturePoints(ceed_data->basis_q_sur, &num_qpts_sur);

    // --- Create Sub-Operator for inflow boundaries
    for (CeedInt i=0; i < bc->num_inflow; i++) {
      CeedVector          q_data_sur, jac_data_sur;
      CeedOperator        op_setup_sur, op_apply_inflow,
                          op_apply_inflow_jacobian = NULL;
      CeedElemRestriction elem_restr_x_sur, elem_restr_q_sur, elem_restr_qd_i_sur,
                          elem_restr_jd_i_sur;

it'll show the context as:

So the function is wrapped into one line, but then cutoff because it's too long. Perfectly fine.
If I move past the if statement, I see:

So the excess of the function signature context has now been wrapped onto the next context line. Note that the line number for the if context is correct, but it's not showing the correct one. Note that the function signature still isn't complete...
Continuing to move past the for loop, I see:

So now the function signature been wrapped over-top of both the if and for statements. Not ideal.
If I expand the width of the screen such that the function signature context can fit on two lines, I get:

Where the if context is now there and the line number next to it is incorrect (that's for the for context).
This seems to be an intended consequence of the patch that closes #10. Or perhaps an overlooked issue when making the patch for that.
I think the less annoying solution is just to keep each context limiited to it's own line. Being able to see the full context line would be nice, but not in exchange of not being able to see the other contexts.

I can't reproduce but I've added a PR to explicitly set the nowrap option, but now that I think it might not be the wrapping. Would you mind testing that branch? Also could you share you config, if there is any, and the full file there?

I tested out the branch, but the issue is still present. Let me try and push up my dotfiles real quick. The file/function in question is here: https://github.com/CEED/libCEED/blob/6e1e594c1a1c9083662b4f212401e3d6898dccad/examples/fluids/src/setuplibceed.c#L77, but I've encountered the problem consistently whenever the top-level context is forced to be cutoff.

Here's the dotfiles repo: https://github.com/jrwrigh/dotfiles2.0/tree/fermat-initlua/.config/nvim

Here's a more minimal config that I was able to reproduce the issue with:
vim.cmd [[set runtimepath=$VIMRUNTIME]]
vim.cmd [[set packpath=/tmp/nvim/site]]
local package_root = '/tmp/nvim/site/pack'
local install_path = package_root .. '/packer/start/packer.nvim'
local function load_plugins()
  require('packer').startup {
    {
      'wbthomason/packer.nvim',
      {
        'nvim-telescope/telescope.nvim',
        requires = {
          'nvim-lua/plenary.nvim',
          { 'nvim-telescope/telescope-fzf-native.nvim', run = 'make' },
        },
      },
      { 'nvim-treesitter/nvim-treesitter', config = function()
            require('nvim-treesitter.configs').setup {
              ensure_installed = {'c', 'python', 'fortran', 'bash', 'lua', 'vim', 'cpp'},
              highlight = {
                enable = true, -- false will disable the whole extension
              },
            }
            end
},
    { 'nvim-treesitter/nvim-treesitter-context', config=function() require('treesitter-context').setup() end}
      -- ADD PLUGINS THAT ARE _NECESSARY_ FOR REPRODUCING THE ISSUE
    },
    config = {
      package_root = package_root,
      compile_path = install_path .. '/plugin/packer_compiled.lua',
      display = { non_interactive = true },
    },
  }
end
_G.load_config = function()
  require('telescope').setup()
  require('telescope').load_extension('fzf')
  -- ADD INIT.LUA SETTINGS THAT ARE _NECESSARY_ FOR REPRODUCING THE ISSUE
end
if vim.fn.isdirectory(install_path) == 0 then
  print("Installing Telescope and dependencies.")
  vim.fn.system { 'git', 'clone', '--depth=1', 'https://github.com/wbthomason/packer.nvim', install_path }
end
load_plugins()
require('packer').sync()
vim.cmd [[autocmd User PackerComplete ++once echo "Ready!" | lua load_config()]]

(partially stolen from telescope's issue submission)

Not sure what was wrong with my previous test, but that branch is working fine now!

@grimgort I'd open up a  new issue. I haven't seen these problems, so it's likely a different root cause.

@grimgort I'd open up a new issue. I haven't seen these problems, so it's likely a different root cause.

Thanks !  I look forward to the correction :)


!!! BUILD FAILED --> LND PGP Verify not OK / signature(0) verify(1)

Hello. So when I finish the build_sdcard.sh it comes up with the error above. I followed: https://github.com/rootzoll/raspiblitz/blob/v1.6.1/README.md#build-the-sd-card-image
**--2021-01-29 03:05:01--  https://keybase.io/roasbeef/pgp_keys.asc
Resolving keybase.io (keybase.io)... <IP_ADDRESS>, <IP_ADDRESS>
Connecting to keybase.io (keybase.io)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 6900 (6

.7K) [text/plain]
Saving to: 'pgp_keys.asc'
pgp_keys.asc               100%[========================================>]   6.74K  --.-KB/s    in 0s
2021-01-29 03:05:02 (33.3 MB/s) - 'pgp_keys.asc' saved [6900/6900]
gpg: WARNING: no command supplied.  Trying to guess what you mean ...
pub   rsa4096 2019-10-13 [C]
E4D85299674B2D31FAA1892E372CBD7633C61696
uid           Olaoluwa Osuntokun<EMAIL_ADDRESS>sub   rsa4096 2019-10-13 [E] [expires: 2024-10-11]
sub   rsa4096 2019-10-13 [S] [expires: 2024-10-11]
sub   rsa4096 2019-10-13 [A] [expires: 2024-10-11]
!!! BUILD WARNING --> LND PGP author not as expected
Should contain PGP: BD599672C804AF2770869A048B80CD2BB8BD8132
PRESS ENTER to TAKE THE RISK if you think all is OK
gpg: key 372CBD7633C61696: "Olaoluwa Osuntokun<EMAIL_ADDRESS>not changed
gpg: Total number processed: 1
gpg:              unchanged: 1
goodSignature(0)
correctKey(1)
!!! BUILD FAILED --> LND PGP Verify not OK / signature(0) verify(1)**

You chose to build the image yourself, its not necessary but it is a seurity measure, as you can garantee its equal to the raspiblitz repository before boot.
The link you shared on the second line is about 1.6.1. Even though it is getting the correct file build_sdcard.sh from branch v1.6, its weird you went to an older version. So, to check the version you are using:
cat /home/admin/_version.info | grep "codeVersion"
Type this to verify if its 1.6.3. If it is or isnt the version 1.6.3, reflash again the microSD. (https://github.com/rootzoll/raspiblitz/blob/v1.6/build_sdcard.sh)

You chose to build the image yourself, its not necessary but it is a seurity measure, as you can garantee its equal to the raspiblitz repository before boot.
The link you shared on the second line is about 1.6.1. Even though it is getting the correct file build_sdcard.sh from branch v1.6, its weird you went to an older version. So, to check the version you are using:
cat /home/admin/_version.info | grep "codeVersion"
Type this to verify if its 1.6.3. If it is or isnt the version 1.6.3, reflash again the microSD. (https://github.com/rootzoll/raspiblitz/blob/v1.6/build_sdcard.sh)

You chose to build the image yourself, its not necessary but it is a seurity measure, as you can garantee its equal to the raspiblitz repository before boot.
The link you shared on the second line is about 1.6.1. Even though it is getting the correct file build_sdcard.sh from branch v1.6, its weird you went to an older version. So, to check the version you are using:
cat /home/admin/_version.info | grep "codeVersion"
Type this to verify if its 1.6.3. If it is or isnt the version 1.6.3, reflash again the microSD. (https://github.com/rootzoll/raspiblitz/blob/v1.6/build_sdcard.sh)

I had to build it my self because of an error while using the pre compiled image. Can you send an img to me that you know is working?

You chose to build the image yourself, its not necessary but it is a seurity measure, as you can garantee its equal to the raspiblitz repository before boot.
The link you shared on the second line is about 1.6.1. Even though it is getting the correct file build_sdcard.sh from branch v1.6, its weird you went to an older version. So, to check the version you are using:
cat /home/admin/_version.info | grep "codeVersion"
Type this to verify if its 1.6.3. If it is or isnt the version 1.6.3, reflash again the microSD. (https://github.com/rootzoll/raspiblitz/blob/v1.6/build_sdcard.sh)

I had to build it my self because of an error while using the pre compiled image. Can you send an img to me that you know is working?

I get the i2c issue

I get the i2c issue

Im trying to understand the i2c issues. Its been on the Pi since the beggining. Some people say its power failure, other say its a pi bug never corrected.
This image is working the current one (https://raspiblitz.org/raspiblitz-v1.6.3-2021-01-13.img.gz)
Im using this img, when there is a power failure, certainly stops at i2c and I need to enter the root password, but to recommend something for you about i2c, first give me some info.
What Pi (3 or 4)?
How do you normally turn off/ reboot the pi?

[ ] Were there power failures recently for you?

[ ] Do you have an LCD attached?

[ ] Do you have a pin fan attached?

SSD attached to usb (3.0 or 2.0)?

[ ] Powered SSD?

Im trying to understand the i2c issues. Its been on the Pi since the beggining. Some people say its power failure, other say its a pi bug never corrected.
This image is working the current one (https://raspiblitz.org/raspiblitz-v1.6.3-2021-01-13.img.gz)
Im using this img, when there is a power failure, certainly stops at i2c and I need to enter the root password, but to recommend something for you about i2c, first give me some info.
What Pi (3 or 4)?
How do you normally turn off/ reboot the pi?

[ ] Were there power failures recently for you?

[ ] Do you have an LCD attached?

[ ] Do you have a pin fan attached?

SSD attached to usb (3.0 or 2.0)?

[ ] Powered SSD?

Im trying to understand the i2c issues. Its been on the Pi since the beggining. Some people say its power failure, other say its a pi bug never corrected.
This image is working the current one (https://raspiblitz.org/raspiblitz-v1.6.3-2021-01-13.img.gz)
Im using this img, when there is a power failure, certainly stops at i2c and I need to enter the root password, but to recommend something for you about i2c, first give me some info.
What Pi (3 or 4)?
How do you normally turn off/ reboot the pi?

[ ]  Were there power failures recently for you?
[ ]  Do you have an LCD attached?
[ ]  Do you have a pin fan attached?

SSD attached to usb (3.0 or 2.0)?

[ ]  Powered SSD?

I am using a Raspberry pi 3b+
No I have not have any power failures.
I do not have a LCD attached
Yes I do have a pin fan attached, but I have tried removing it, and it didnt work.
I am using a hdd. I have also tried disconnecting it but it didnt work.

Im trying to understand the i2c issues. Its been on the Pi since the beggining. Some people say its power failure, other say its a pi bug never corrected.
This image is working the current one (https://raspiblitz.org/raspiblitz-v1.6.3-2021-01-13.img.gz)
Im using this img, when there is a power failure, certainly stops at i2c and I need to enter the root password, but to recommend something for you about i2c, first give me some info.
What Pi (3 or 4)?
How do you normally turn off/ reboot the pi?

[ ]  Were there power failures recently for you?
[ ]  Do you have an LCD attached?
[ ]  Do you have a pin fan attached?

SSD attached to usb (3.0 or 2.0)?

[ ]  Powered SSD?

I am using a Raspberry pi 3b+
No I have not have any power failures.
I do not have a LCD attached
Yes I do have a pin fan attached, but I have tried removing it, and it didnt work.
I am using a hdd. I have also tried disconnecting it but it didnt work.

Reflash for now, if it stops again, will try to solve that for you by other means.

Reflash for now, if it stops again, will try to solve that for you by other means.

Reflash for now, if it stops again, will try to solve that for you by other means.

I just tried reflashing it but it stopped

Reflash for now, if it stops again, will try to solve that for you by other means.

I just tried reflashing it but it stopped

How do you know its i2c if you dont have lcd? Do you use hdmi?

How do you know its i2c if you dont have lcd? Do you use hdmi?

I plugged in hdmi

I plugged in hdmi

and I cant ssh into it. I have added wifi and ssh with files.

and I cant ssh into it. I have added wifi and ssh with files.

Ok. For the hdmi. Plug the microSD to your computer/laptop.
Open the file called config.txt
Edit the line hdmi_safe to look like this - NO # before the line (this will lower the resolution, but its the only workaround).
hdmi_safe=1
Add a file called hdmi. How do you do this? You create a text file and just remove the extension .txt

Ok. For the hdmi. Plug the microSD to your computer/laptop.
Open the file called config.txt
Edit the line hdmi_safe to look like this - NO # before the line (this will lower the resolution, but its the only workaround).
hdmi_safe=1
Add a file called hdmi. How do you do this? You create a text file and just remove the extension .txt

How do you normally turn off/ reboot the pi
You forgot this one.

Please answer....
Do you remove the power cable, do you type reboot, or other?

How do you normally turn off/ reboot the pi
You forgot this one.

Please answer....
Do you remove the power cable, do you type reboot, or other?

How do you normally turn off/ reboot the pi
You forgot this one.

Please answer....
Do you remove the power cable, do you type reboot, or other?

I dont turn of the pi. I just reflash the image everytime

How do you normally turn off/ reboot the pi
You forgot this one.

Please answer....
Do you remove the power cable, do you type reboot, or other?

I dont turn of the pi. I just reflash the image everytime

I dont turn of the pi. I just reflash the image everytime

Well, I dont understand how you do that.... How do you reflash the sdCard?
Type XXshutdown.sh wait for the screen to be black and the waint 10 more secs,. Turn off the power.
Do as described about hdmi above.

I dont turn of the pi. I just reflash the image everytime

Well, I dont understand how you do that.... How do you reflash the sdCard?
Type XXshutdown.sh wait for the screen to be black and the waint 10 more secs,. Turn off the power.
Do as described about hdmi above.

I dont turn of the pi. I just reflash the image everytime

Well, I dont understand how you do that.... How do you reflash the sdCard?
Type XXshutdown.sh wait for the screen to be black and the waint 10 more secs,. Turn off the power.
Do as described about hdmi above.

Ok wait

I dont turn of the pi. I just reflash the image everytime

Well, I dont understand how you do that.... How do you reflash the sdCard?
Type XXshutdown.sh wait for the screen to be black and the waint 10 more secs,. Turn off the power.
Do as described about hdmi above.

Ok wait

Do you unplug the microSD without turning off the power of the pi?
Please join telegram group, this thread is getting extensive.

Do you unplug the microSD without turning off the power of the pi?
Please join telegram group, this thread is getting extensive.

Do you unplug the microSD without turning off the power of the pi?
Please join telegram group, this thread is getting extensive.
https://t.me/raspiblitz

I am not doing that.

Do you unplug the microSD without turning off the power of the pi?
Please join telegram group, this thread is getting extensive.
https://t.me/raspiblitz

I am not doing that.

I dont know to which line you answered, there is a clear communication problem.
Detail how do you do the reflash and how do you boot.
How I would recommend for you to do.
Download the image.
Use balena etcher to reflash the sd card with the image you just downloaded.
Unplug safely the microSD from your computer and plug it again so you can access the files.
Edit the /boot/config.txt as said above.
Add the wpa_supplicant (ethernet cable is best), hdmi and ssh file.
Unplug safely the microSD.
With the pi turned off, insert the microSD on the slot.
Turn on the power.
Try with hdmi attached and unattached (mine works attached on the boot, RPI4)
As you are using RPI3, it is not as stronger as RPI4.
on the i2c problem, it just stops for 1 minute, or does it appear Ctrl +D or root password option?
If it doenst appear any of this, Alt +F2 to bypass that, user=admin, password =raspiblitz (you will be able to change that after)
As it seems its your first time trying to use blitz, if it does bypass this, try waiting some time and let the Pi running.
Run this blitz.stresstest.sh

I dont know to which line you answered, there is a clear communication problem.
Detail how do you do the reflash and how do you boot.
How I would recommend for you to do.
Download the image.
Use balena etcher to reflash the sd card with the image you just downloaded.
Unplug safely the microSD from your computer and plug it again so you can access the files.
Edit the /boot/config.txt as said above.
Add the wpa_supplicant (ethernet cable is best), hdmi and ssh file.
Unplug safely the microSD.
With the pi turned off, insert the microSD on the slot.
Turn on the power.
Try with hdmi attached and unattached (mine works attached on the boot, RPI4)
As you are using RPI3, it is not as stronger as RPI4.
on the i2c problem, it just stops for 1 minute, or does it appear Ctrl +D or root password option?
If it doenst appear any of this, Alt +F2 to bypass that, user=admin, password =raspiblitz (you will be able to change that after)
As it seems its your first time trying to use blitz, if it does bypass this, try waiting some time and let the Pi running.
Run this blitz.stresstest.sh

I get the i2c problem, and I cant click ALT + F2 Nothing happends!

Could you screenshot or take a photo?
if it stops on i2c, try to wait 1 minute (https://github.com/rootzoll/raspiblitz/issues/1984#issuecomment-770409014)
Try Ctrl+D instead. Never seen a case where this doennt work.

OK the build sd card got a big update for the upcomming v1.7RC1 release. The LND verification should be fixed and also lots of additional parameters to to custom build the image now. So I put this to final testing.

OK the build sd card got a big update for the upcomming v1.7RC1 release. The LND verification should be fixed and also lots of additional parameters to to custom build the image now. So I put this to final testing.
There were some other ideas/issue for the sd card build in here ... maybe some need to be extracted into single issues.

Hello. Thank you for answering! When is this update gonna be released to public?

@Johan4j https://github.com/rootzoll/raspiblitz/milestone/10
Milestone 1.7 Release
There is no exact date, but as Rootzoll said that the first release candidate is ready (v.17 RC1), I would say less than a month for 1.7 for the public.

OK we are getting closer to a final ... tomorrow we should have a RC3 and if nothing critical pops up anymore a final v1.7 close after. Closing this issue.


Compilation issues with clang

DirectX Tool Kit won't build with clang, primarily because it relies on the XMVECTOR operator overloads

Last year I updated DirectXMath to compile with clang. One of the issues I encountered is that clang does not define __m128 as a struct the way Visual C++ and the Intel compiler do. Instead it's defined as an opaque type. Because of C++ rules you're not able to overload just on the type. Therefore I added logic to remove those overloads when building with clang. Obviously that means any client code that relies on those overloads has to be updated as you've done. I explain this in detail in this blog post

Will also likely need to silence some 'warnings all' noise in pch.h
#ifdef __clang__
#pragma clang diagnostic ignored "-Wdeprecated"
#pragma clang diagnostic ignored "-Wfloat-equal"
#pragma clang diagnostic ignored "-Wlanguage-extension-token"
#pragma clang diagnostic ignored "-Wnonportable-system-include-path"
#pragma clang diagnostic ignored "-Wsign-conversion"
#pragma clang diagnostic ignored "-Wswitch-enum"
#pragma clang diagnostic ignored "-Wzero-as-null-pointer-constant"
#endif

The DirectXMath issues are fixed in this pull request


where is # Install dependencies ./install.sh

Platform
Ubantu 22
Panel Version
10.0
Daemon Version (Optional)
4.3.0
Recurrence Probability
100%
Bug Description
You can't find install.sh after decompressing the file when installing according to your document. You note the steps of installing dependencies./install.sh ("# Install dependencies
./install.sh") I was confused
就是按照你们的文档安装的时候 解压完文件找不到install.sh ，你们批注写了安装依赖的脚步./install.sh ("# Install dependencies
./install.sh") 我很疑惑

node 16

I hope it can be solved as soon as possible, thank you. In addition, I hope we can communicate at noon. I am Chinese 希望可以尽快解决，谢谢你们，另外希望可以中午沟通，我是中国人

为什么中午沟通？因为早晚会出事？

I hope it can be solved as soon as possible, thank you. In addition, I hope we can communicate at noon. I am Chinese 希望可以尽快解决，谢谢你们，另外希望可以中午沟通，我是中国人

为什么中午沟通？因为早晚会出事？

hhh 打错字力，然后翻译也错了，哈哈哈哈哈，笑死

问题也解决了，我下载了低版本的，这个issues怎么关？（疑惑）


Reset analytics

Original issue by robsannaa on 2021-01-22 12:59:28+00:00
Hello! First of all thanks for this. It is really great to have something like built for Streamlit!
I have tried saving the analytics as JSON, and I have noticed that if I delete the .json file, once I run the app again I will still get my "old" analytics files. Is there a wy to reset the tracking and start from zero at some point?

Comment by jrieke on 2021-01-22 18:56:39+00:00
Hey @robertosannazzaro, at the moment the easiest solution would be to restart your streamlit app (i.e. re-run streamlit run), then all metrics should be reset. I don't have time for this project right now but I hope I can get back to it during the next weeks, then I'll think about how a programmatic reset could be implemented! :)

Comment by jrieke on 2021-01-29 22:40:32+00:00
@robertosannazzaro The newest version (v0.2.1) has a section at the bottom of the page that allows you to reset all results (see image). Let me know if that works for you and feel free to re-open if not!

Comment by robsannaa on 2021-01-31 09:58:29+00:00
Hi @jrieke, tested and like it very much! Thanks for pushing this one!

Comment by joshua-bowden on 2023-07-06 01:39:34+00:00
would be great to be able to disable this in code, especially since these analytics are mostly used with no password/ not secure


Clarification and/or configurability of what it means for a server to be dead/down

While working with @djcarlin and @bryancall to understand an issue from deploying the dead server no retry feature added in PR #7142, we were surprised by when exactly servers are marked dead.
In the case where transactions are retryable, things pretty much worked as expected.  If the handshake failed or the request is sent but the origin fails to return data and is retryable, the address is tried the number of times specified in proxy.config.http.connect_attempts_rr_retries (at least once PR #7288 is applied) before marking the IP address as down and moving onto the next IP address.
However, if the transaction failed after sending the header and it is not retryable (e.g. a POST request), the ip address is marked down immediately (the retry count in proxy.config.http.connect_attempts_rr_retries is ignored).  If the origin only times out now and again due to larger requests, taking it down immediately seems bad particularly using the new feature that avoids the retries against the down server in the dead period.  However, if the server is consistently failing to respond to post requests, it should be marked down.
Probably this down decision criteria needs to be configurable.  Some origins need different criteria than others.  Some should only be marked down in the initial handshake fails.  Others should be marked down but only if no data was returned.  Or maybe you want to mark things down only for specific origin connection failures.

I noticed squid.log entries with "ERR_CONNECT_FAIL 502" when a POST was happening, and Content-Length sent by client request differed greatly from %<cqql> log field - "Client request header and content length combined, in bytes."
In our case, Content-Length was tens of megabytes and cqql was only hundreds of bytes. This was marking origin down and breaking other valid requests.

I ran across the proxy.config.http.down_server.abort_threshold setting.  I think the comparison is backwards from the description.  But if the client times out in more than this many seconds and the origin hasn't sent anything back yet, it will count towards marking that origin down.   The default value for this setting is 10..
The intent is to include "slow servers" in the set of dead servers to be avoided.  But if your client side inactivity timeout is less than your origin side inactivity, the bad client scenario that @djcarlin identifies will trigger this and increment the counts for the origin connection to be down.
It is easy enough to take proxy.config.http.down_server.abort_threshold out of the equation by setting it higher than any of your inactivity timeouts.  But I think we may want to reconsider this setting.  The intent of marking "slow" servers as down is admirable, but identifying the slowness as an issue on the origin side vs the client side is sketchy at best.

@djcarlin updated our configs to set  proxy.config.http.down_server.abort_threshold  higher than any of our other timeouts (basically making sure this config never did anything), and our down server failures greatly reduced.

Did some more work today on down servers in our environment.
One think I hadn't noticed before was that an origin failure only contributes to the down server count if the t_state->current.server->connect_result is non-zero.   That is a real error happened during the TCP/TLS connection failure.  There are many messages generated in error.log where the connect_result is 0 and a failure happened between connect open and  first byte from server.  These transactions are available for retries, but they don't contribute to the counts to marking a server down.
Locally, we are trying a built that only adds a log to error.log if it really is a connect failure.  It really cut down the noise in our logs.

Based on the type of connection errors we are seeing in our environment, I'm adding a setting to adjust which connection failures count towards the down server count.
For our environment, a TCP connection failure (no route, timeout, or refused) is very different from a SSL cert verification failure.   For some of our next level machines, quite a few connections will be routed to the same machine with different SNI and host names.  A failure for one host name/SNI (due to cert verification failure) should not take down the origin for all the other requests for other host names.
So we will experiment with a setting that has the following options

All connection failures (TCP and TLS) count towards the down server count.  Existing function.
Only TCP connection failures count towards the down server count


[REVIEW] Http cache JCR storage - 6.3

I am doing something wrong with the service user.
Somehow I get a constraint violation exception when installing and thus the user is not there.
Anybody that sees what I am doing wrong? I tried to copy the approach that other service users follow.
Much appreciated.

Please check for review. The 8 issues to fix are trivial. Also, are powermock tests included in the coverage?

@Sc0rpic0m are there areas (Files) the changed from the 6.0 PR to focus on? Thanks

Only real logic that changes was

the service class, to use the service user
HttpCacheEngineImpl.java -> to adhere to sonar, reduce a little code. Definitely check this one just to make sure. But I tested the branch locally and it seemed fine, however better safe then sorry of course.

Looks like a few minor codeclimage issues as well.

Thanks @Sc0rpic0m !!

Not yet. Il contact david on how to extend the docs.

The documentation generated from https://github.com/Adobe-Consulting-Services/adobe-consulting-services.github.io. Please submit pull requests against that repository

Working on it. In meantime: basically this is just a jcr storage unit instead of in-mem (guava) storage unit for the http cache. Good side is it can handle large amounts of data and persist through restarts, downside its has a slower lookup.


make docs error in Ubuntu

I've tried the command make docs from Mac and Ubuntu machines. This command works without any problem from the Mac machine, but I receive this error from the Ubuntu machine

I tried to debug and strace the make process, removing this line @pkill -f "mkdocs serve" 2>/dev/null || true solves the problem.

@pchalasani. thank you for spotting out.
I found these two ways that work for both Ubuntu and MacOS:

@-kill `ps aux | grep ".*mkdocs serve" | grep -v grep | awk '{print $2}'` 2>/dev/null || true
@-kill `pgrep -f ".*mkdocs serve"` 2>/dev/null || true

So now every time you run the command make docs or make nodocs the mkdocs will be killed, and restarted for the make docs
However, the problem with the second one is that there is a possibility pgrep isn't installed on the Mac machine.
Please let me know which approach you prefer and if I need to create a new PR

Second solution is fragile. In any case,  it's not such a big deal... I wonder why doesn't pkill  work

Based on my understanding, when I run pkill command in the makefile directly from the terminal, the process isn't captured, the full path needs to be provided like this @pkill -f "/nobackup/langroid/.venv/bin/python /nobackup/langroid/.venv/bin/mkdocs serve" 2>/dev/null || true, while when the command is executed from inside the Makefile, the make process gets killed because for some reason the mkdocs process is spawn through the make.
`

I think solved


simply everytime i attempt lime test windows, this happens

Describe your problem here.
please help me

Are you modding a build from source or with Lua?
Source
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No

haxelib git linc_luajit https://github.com/superpowers04/linc_luajit master

and don't make duplicate issues

k

also i got error Eof when i tried

also i got error Eof when i tried

show

Downloading linc_luajit-0,0,6.zip...
Download complete: 0.25KB in 0.8s (0.2KB/s)
Download complete: 1.83MB in 0.9s (1910.4KB/s)
Failed to download https://lib.haxe.org:443/files/3.0/linc_luajit-0,0,6.zip. (1/3)
Custom([file_write,C:/HaxeToolkit/haxe/lib/linc_luajit-0,0,6.zip])
Download complete: 0.25KB in 0.9s (0.2KB/s)
Download complete: 1.82MB in 1.4s (1253.3KB/s)
Failed to download https://lib.haxe.org:443/files/3.0/linc_luajit-0,0,6.zip. (2/3)
Custom([file_write,C:/HaxeToolkit/haxe/lib/linc_luajit-0,0,6.zip])
Download complete: 0.25KB in 0.8s (0.2KB/s)
Download complete: 3.43MB in 2.5s (1365.1KB/s)
Error: Eof

make sure you have enough space to install it and it can also be a wifi issue, and not to mention you're supposed to do
haxelib git linc_luajit https://github.com/superpowers04/linc_luajit master not install it from haxelib

so it was space, i tried both. i might've fixed it


Optimization

When the water spread a lot, for example if you let the water flow from very high the game can lag or even worst, crash.
Suggestion:
Made a water manager where is saved for each position (block) the parents (from where comes) and childs (what generate) of each block. RAM in exchange of performance.
Note: Use "recursivity" between clases with threads

It's harder that i thought.

Thanks Zun & Pandaros with the help of this issue.


client: Improved load config errors

Coverage: 82.601%. Remained the same when pulling e14757509f7fe3817e4006bb3bdd71fe88d803b9 on dissoupov into 5bef769329f380a6736f87a82fc2be30338acff6 on main.


Document gamepad.rs

Objective

Fixes #5544
Part of the splitting process of #3692.

Solution

Document everything in the gamepad.rs file.
Add a doc example for mocking gamepad input.

Changelog

Added and updated the documentation inside of the gamepad.rs file.

@alice-i-cecile Great points. Thank you!
Regarding your request to add another example to the GamepadEventRaw:
I moved the example from the GamepadEvent to the GamepadEventRaw and linked to it in the docs of the GamepadEvent. Let me know if that's what you were after or if you wanted an additional example.

bors r+


Suggestion: set [font-display] property and enable to display alternative font during data-loading

Suggestion
Set font-display: block; into feathericon's @font-face.
Background
When I dealed with improve our web site's loading speed, I found that feathericon's  file loading is costing time a little.
Google introduces the way to shorten font loading time by setting font-display property into @font-face,
so I suggest to introduce this solution into feathericon.
Here is the reference about it.
How to avoid showing invisible text | google web.dev
Supplement
The documentation above introduces font-display: swap; as a solution for text font, by displaying alternative font during loading.
However, in the case of icon font, which has no alternative font, font-display: block; is the optimal solution. It displays blanc object during loading.
Reference: font-display #the_font_display_timeline | MDN
For your refference, other open source icon font FontAwesome adopts font-display: block; , too.
https://github.com/FortAwesome/Font-Awesome/blob/fcec2d1b01ff069ac10500ac42e4478d20d21f4c/css/all.css#L4590

merged #127


Support more than 10000 children when using factory contracts

Currently, factory contract support is limited in the amount of child instances you can index.
As per docs:

Scaling: The sync engine does not currently support factory contracts with more than 10,000 children. This includes Uniswap V2, V3, and many other permissionless pool-based DeFi protocols. Why not? The Ethereum JSON-RPC API does not scale well for factory contracts. There's only so much that Ponder's sync engine can do about this while remaining compatible with the JSON-RPC API. We're actively working to address scaling challenges via features like remote sync, shared caching, and concurrent indexing. Thanks for your patience.

Ideally, it would be possible to extend to unlimited number of children.

Made an issue mostly for tracking purposes, but have you explored shifting to full block log querying once you exceed the threshold?
E.g. start with a narrow eth_getLogs query filtering by instance addresses (I think that's how it works now?), and then switch to an unfiltered eth_getLogs query once the number of instances exceed 10000.

Fixed this starting in 0.5.19


[question] How to launch

Hello! I find your project interesting, and I want to try it. But can I easily start that player? There is no information in the README.

@HOTHEAD01TH can you create a basic setup guide under readme?

Done

Done


Thread model

Implement the classes:

[ ] elrond::interface::Task: interface for tasks
[ ] elrond::runtime::SynchronousPeriodicTask: Class to hold some synchronous task
[ ] elrond::runtime::AsynchronousPeriodicTask: Class to hold some asynchronous task

The C++17 allows a better support for multithreading and some features extra features. Due this, for this runtime implementation will use C++17.

The C++17 allows a better support for multithreading and some features extra features. Due this, for this runtime implementation will use C++17.

This is not necessary, for now.

Due non copyable nature of std::future, will be necessary a data structure to hold instances of std::future and can handle it easily.


displayName

displayName does not show when you configure the Body of a list form.
According to doc at:
https://docs.microsoft.com/en-us/sharepoint/dev/declarative-customization/list-form-configuration#configure-custom-body-with-one-or-more-sections
You should be able to do like this.
{
"displayName": "Details",
"fields": [
"Department",
"Email",
"Country"
]
},
Section grouping works, but displayName is not visible at the form.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 0f6aeedd-a76d-88b0-7ed5-93e20ac218bc
Version Independent ID: 64315895-1103-d5f6-0195-9b5b61211132
Content: Configure the list form
Content Source: docs/declarative-customization/list-form-configuration.md
Product: sharepoint
GitHub Login: @VesaJuvonen
Microsoft Alias: vesaj

Dupe #6647 #6637

Dupe #6647 #6637


Merging QR Image with Base64 encoded PDF

Hi ,
I have PDF in base 64 encoded form. I want to edit and add an QR image to it using PDF kit.
Somehow when i try to merge the streams the content fails . Below is the code.
var base64 = require('base64-stream');
var PDFDocument  = require('pdfkit');
    var doc = new PDFDocument ();

    doc.image('test.jpeg', {
            fit: [250, 300],
            align: 'center',
            valign: 'center'
    });

    var finalString = ''; // contains the base64 string
    var stream = doc.pipe(base64.encode());
    doc.end();

    var finalString = '';

    stream.on('data', function(chunk) {
            finalString += chunk;});

    stream.on('end', function() {
     // the stream is at its end, so push the resulting base64 string to the response
            read.writeFileSync('./report.pdf', finalString);
     });

Same for me here.

Yes I did. I will post the solution.

good day, promised to write a solution.
the problem is relevant enough for me