"invalid wire type" error when decoding GTFS realtime feed

I'm fetching feed data from a URL endpoint of the form <baseUrl>/<feedName>.proto, but for some reason I get an "invalid wire type" error when I do GtfsRealtimeBindings.transit_realtime.FeedMessage.decode(body) in Node.js. I'm using the example code from the Node.js README:
var GtfsRealtimeBindings = require('gtfs-realtime-bindings');
var request = require('request');

var requestSettings = {
  method: 'GET',
  url: '<baseUrl>/<feedName>.proto',
  encoding: null,
};
request(requestSettings, function (error, response, body) {
  if (!error && response.statusCode == 200) {
	console.log(body)
	var feed = GtfsRealtimeBindings.transit_realtime.FeedMessage.decode(body);
	feed.entity.forEach(function(entity) {
	  if (entity.trip_update) {
		console.log(entity.trip_update);
	  }
	});
  }
});

// <Buffer 68 65 61 64 65 72 20 7b 0a 20 20 67 74 66 73 5f 72 65 61 6c 74 69 6d 65 5f 76 65 72 73 69 6f 6e 3a 20 22 31 2e 30 22 0a 20 20 69 6e 63 72 65 6d 65 6e ... 37282 more bytes> object
// C:\Users\Chris Marais\code\js\protobuf\node_modules\gtfs-realtime-bindings\node_modules\protobufjs\src\reader.js:375
			throw Error("invalid wire type " + wireType + " at offset " + this.pos);
			^

// Error: invalid wire type 7 at offset 12

Is the array buffer encoded incorrectly perhaps? Unfortunately I'm unable to share the data, but I can confirm that it conforms to the GTFS realtime specification

Is the array buffer encoded incorrectly perhaps? Unfortunately I'm unable to share the data, but I can confirm that it conforms to the GTFS realtime specification

@Mchristos Just to confirm the .proto file is a binary file - can you open the .proto file in a text editor and read the contents in plain text?
Typically files with the extension .proto are the protocol buffer definition files, and aren't the compressed binary representation of the actual data - those typically have a .pb extension.

Thanks @barbeau - yes I thought something was a bit odd - yes the files are plain text, which from my understanding is not the usual way of sending protobuf. But, this is the data I'm dealing with. Any suggestions?

So, to clarify, I'm looking at plain-text snapshots of the binary protobuf data, but I only have access to the plain text. Any way to recover or parse the data somehow?

@Mchristos Are you sure that the producer isn't maybe providing the .proto file as an extension to the gtfs-realtime.proto file, and the actual message is in another field?
If the .proto file looks like https://developers.google.com/transit/gtfs-realtime/gtfs-realtime-proto, then it's probably an extension file. In that case, you'd need to generate your own code bindings from that .proto file (see https://github.com/MobilityData/gtfs-realtime-bindings/blob/master/nodejs/UPDATING.md for how we do this for Node.js in this project, and this issue for someone else that just did this). And, you'd need to find another binary message from the producer that contains the actual data you could parse using the bindings you created.
If the .proto file looks more like https://github.com/google/transit/blob/master/gtfs-realtime/spec/en/examples/trip-updates-full.asciipb, then it's basically a JSON-ized plain text version of the protocol buffer data. I know Google's protocol buffer compiler gives you an option to export a message object to JSON, and I think it might have an option to read one in too. Or, if the message is valid JSON, you could use any JSON parser.

Yup, its definitely the latter (a JSON-ized version of an actual message). But, it doesn't look exactly like JSON to me (if so it would have an array of entities, rather than repeated entity {} declarations). Might be tricky to parse, but I can try and report back. I'll also try using google's protocol directly like you suggested.

@Mchristos Yes, please let me know what you find. It's certainly worth reporting this issue to the producer too - maybe they don't realize that they actually aren't sharing a true protocol buffer message.

Has this issue been solved? I am seeing a similar error.
err: {       "type": "Error",       "message": "invalid wire type 6 at offset 77",       "stack":           Error: invalid wire type 6 at offset 77               at Reader.skipType (/....../node_modules/protobufjs/src/reader.js:377:19)               at Reader.skipType (/....../node_modules/protobufjs/src/reader.js:368:22)               at Function.decode (/....../node_modules/gtfs-realtime-bindings/gtfs-realtime.js:150:28)
The endpoint providing the data is publicly available http://gtfsr.vbn.de/gtfsr_connect.bin
I'd be grateful for any hint.

Exactly the same problem for me : I have an url wich is supposed to be a GTFS RealTime update in proto file type. So I downloaded the gtfs-realtime.proto file to get the types but my first problem is that there are multiple messages and types but almost each time I get the same error :
throw Error("invalid wire type " + wireType + " at offset " + this.pos);
^
[  Error: invalid wire type 4 at offset 1
My code looks like this : (i use protobufjs in node with import protobuf from "protobufjs")
try {
const response = await fetch(url);
if (!response.ok) {
throw new Error(Erreur HTTP : ${response.status});
}
    const buffer = await response.arrayBuffer();
    const arrayBuff = new Uint8Array(buffer);

    protobuf.load("gtfs-realtime.proto", function(err, root) {
        if (err)
            throw err;

         // Obtain a message type
        const ProtoMessage = root.lookupType("transit_realtime.FeedMessage");
        // Decode an Uint8Array (browser) or Buffer (node) to a message
        const message = ProtoMessage.decode(arrayBuff);
        // ... do something with message

        console.log(message);
    });

    return response;
}

Does someone find the solution ?
if I download and open the file I get from URL it looks like this in NotePad++
450375424626689018:02:0020231125  *118219533168149150   "3377704015496221(
I"3377704015495624( 'óÿÿÿÿÿÿÿÿy"3377704015495803( (Òÿÿÿÿÿÿÿÿ…"3377704015496100( i"3377704015495675( DD"3377704015495383(
F"3377704015495283(
g"3377850044383400(
C"3377850044383436(

Hey @toops61 ! You shouldn't need to use protobufjs at all if you're using gtfs-realtime-bindings. This package already generates the JS code for you based on the protobuf schema.
Take a look at the example usage here: https://github.com/MobilityData/gtfs-realtime-bindings/blob/master/nodejs/README.md#example-code

@saretter Sorry for the super late response, but I was able to use your provided endpoint with no errors! I based my code off the example provided in the README: https://github.com/MobilityData/gtfs-realtime-bindings/blob/master/nodejs/README.md#example-code

For what it's worth, I don't think there is actually any bug here. From what I can tell, this was simply someone producing bad or confusing data, so the GTFS bindings library was being pointed at something that wasn't actually GTFS protobuf data.
@isabelle-dr When you have a minute, please close this issue!

thanks for your answers. I don't use gtfs-realtime-bindings actually, that's why I was using protobufjs. Ok now I know that's it's not my code the problem ;-) (but I have to find a way to use the url that the client gave me anyway, I'll try other solutions. thanks again for the help.

and I'm also looking for a way to use all messages types that the gtfs-realtime.proto contains if it's possible (FeedMessage, FeedHeader, FeedEntity, TripUpdate, etc...) ?

@toops61 This issue that you're commenting on is for a Github Issue in the gtfs-realtime-bindings repo, so discussion here should revolve around that specific tool! If you have questions about the GTFS realtime spec / proto more broadly or protobufjs, I would advise going to those repos / projects more directly (here and here).
For what it's worth, gtfs-realtime-bindings may be a good use-case for you, since it hides all the complexity typically involved with getting protocol buffers set up by distributing the generated code directly.

Hello!
Thanks for the ping @jameslinjl.
Closing this issue since it seems this is a problem with the input data and not the realtime bindings.


CircleCI can't source Postgres Image

Trying to set up tests in our CI pipeline using the cimg/postgres:14.1.0 image and when it runs in CI I am getting this - Error response from daemon: manifest for cimg/postgres:14.1.0 not found: manifest unknown: manifest unknown
Literally copied and pasted the image tag from the docs, also can't seem to find it on DockerHub

Resolved this one quick - solution is to not include the patch version #. So cimg/postgres:14.1 worked


ExternalDnsAddOn: Unable to start on ARM architecture

Describe the bug
ExternalDNSAddOn starts the bitnami docker image https://hub.docker.com/r/bitnami/external-dns/tags.
This image only exists for AMD architecture, hence the addon is deployed but the pod is unable to start on ARM based nodes
Expected Behavior
ExternalDNSAddon should be compatible with both K8S architecture
Current Behavior
The pod enters in a CrashLoopBackOff state
Reproduction Steps
Create a managed node group with ARM_64 arch
    const clusterProvider = new blueprints.GenericClusterProvider({
        version: KubernetesVersion.V1_23,
        kubectlLayer: new KubectlV23Layer(kubectlLayerStack, "KubectlLayer"),
        managedNodeGroups: [
            {
                minSize: 1,
                maxSize: 3,
                id: "mng-main-group-1",
                amiType: NodegroupAmiType.AL2_ARM_64,
                instanceTypes: [new InstanceType("c7g.large")],
                diskSize: 50,
            },
        ],
    });

Simply use the ExternalDnsAddOn
    new blueprints.addons.ExternalDnsAddOn({
        hostedZoneResources: [GlobalResources.HostedZone]
    }),

Possible Solution

Use another docker image supporting multi arch not provided by bitnami. Kubernetes SIGs may be a good alternative ?
https://github.com/kubernetes-sigs/external-dns/
docker pull --platform linux/arm64 us.gcr.io/k8s-artifacts-prod/external-dns/external-dns:v0.13.1

Update the documentation to warn that this addon isn't compatible with ARM without overriding the default image.

Additional Information/Context
No response
CDK CLI Version
2.56.0 (build 1485f48)
EKS Blueprints Version
1.5.2
Node.js Version
18.12.1
Environment details (OS name and version, etc.)
alpine
Other information
No response

@sylwit Thank you for submitting the issue. As shown here, lack of ARM support on helm charts appears to be a Bitnami-wide issue.
Short term solution might be to document the lack of ARM support. As for the SIGs helm chart, we will investigate and take a look.

Just posting my workaround in case it could help. Simply override the helm chart
new blueprints.addons.ExternalDnsAddOn({
        hostedZoneResources: [GlobalResources.HostedZone],

        repository: 'https://kubernetes-sigs.github.io/external-dns/',
        version: '1.12.0',
}),

@elamaran11 is it is the case? Can we close it if later version of external DNS work with arm?

@shapirov103 This looks like repo change and version change. we are at 6.x with bitnami repo. I will work on testing it and update doc as well.

@sylwit Please track with #739 PR


Ambiguous use of 'filter' error.

I'm getting an "Ambiguous use of filter" error in LifetimeTracker+DashboardView.swift.
Any ideas?
I'm running:
Mac OS X 10.12.6
Xcode 9.2
Build version 9C40b

you have to be on old version of code because we fixed this already https://github.com/krzysztofzablocki/LifetimeTracker/pull/25

Weird. I just installed it for the first time today, via Cocoapods, and
used the instructions from the README.
On Sat, Mar 10, 2018 at 7:24 PM Krzysztof Zabłocki<EMAIL_ADDRESS>wrote:

Closed #39
https://github.com/krzysztofzablocki/LifetimeTracker/issues/39.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/krzysztofzablocki/LifetimeTracker/issues/39#event-1514890814,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACLlHF4M21LS9ZApiqw_6UNP5h-pkdmWks5tdJj2gaJpZM4Slgf7
.

I went ahead and updated Cocoapods itself, and then reinstalled LifetimeTracker following the instructions in the README, but still got a bunch of errors. Just a friendly FYI.

What's the version of the pod it fetched?

Installing LifetimeTracker (1.3.3)
And here's an error I get in my project.

On Tue, Mar 13, 2018 at 1:08 PM, Krzysztof Zabłocki <
<EMAIL_ADDRESS>wrote:

What's the version of the pod it fetched?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/krzysztofzablocki/LifetimeTracker/issues/39#issuecomment-372801198,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACLlHLArqaga3Teoe3XRIDg8Wr5CnOeXks5teCc2gaJpZM4Slgf7
.


Type Generation : returned payload type on upsert not using include

Breaking commit: https://github.com/prisma/prisma/commit/4cee9296e77e63aa856f60b9a33555ab01d9b039#diff-55d3b6703244dc96a4a668b570e5c70d
^^ Issue is caused by the above commit, related to prisma/prisma#615. There is not explanation given as to why this change was made. @timsuchanek could you clarify this change?
Bug description
The include option only expands the result type when the query options passed to the Prisma Client extend the findMany options.
The following line decides when includes will expand the return type:
https://github.com/prisma/prisma/blob/c86af74877d9f39936b18276b3c1db8d5ff7b310/src/packages/client/src/generation/TSClient.ts#L553
How to reproduce
Add includes to an upsert, or findOne that uses a where with a composite unique lookup, that is not available in {...}WhereInput.
Using the blog fixture example:
model Like {
  id  String  @default(cuid()) @id

  userId  String
  user    User    @relation(fields: [userId], references: [id])

  postId  String
  post    Post    @relation(fields: [postId], references: [id])

  @@unique([userId, postId])
}

  const like = await prisma.like.upsert({
    where: {
      userId_postId: {
        userId: userId,
        postId: post.id,
      }
    },
    create: {
      post: {connect: {id: post.id}},
      user: {connect: {id: userId}},
    },
    update: {},
    include: {post: true},
  });

  const p = like.post;
                 |--|
                 ^ TS2339: Property 'post' does not exist on type 'Like'.

typeof like is Like despite the includes.
Expected behavior
The type correctly has the fields specified in includes.
In the above example, typeof like should be Like & {post: Post}.
Prisma information
Example in https://github.com/squirly/prisma/tree/bug-example/src/packages/client/fixtures/blog
Environment & setup

OS: Mac OS & Arch
Database: PostgreSQL
Prisma version:

Broken in: 2.0.0-beta.2
Works in 2.0.0-beta.1

Node.js version: 12.16.1

Thanks for reporting @squirly.
As mentioned in the commit (https://github.com/prisma/prisma/commit/4cee9296e77e63aa856f60b9a33555ab01d9b039#diff-0cc91727f49088eeb56266cf1b886c81R131) the fix I introduced there was about the nested findMany with orderBy case.
Your PR would have broken that case again.
Instead, I now added a type union, which is executed in the type inference by 2 separate statements. (Does it extend the first type? If not, check if it extends the second type).
This issue is fixed in the latest alpha version of @prisma/cli.
You can try it out with npm i -g @prisma/cli@alpha.
In case it’s not fixed for you - please let us know and we’ll reopen this issue!


Extension is not working on Ubuntu

Hi Juan,
There's another issue
VSCode Version: 1.51.1
OS Version: Ubuntu 20.04.1 LTS
Steps to Reproduce:
1.Install VS Code on Ubuntu (via application hub or via snap)
2.Install extension: ext install JuanBlanco.solidity
Symptoms are:
The extension is installed but shows no signs of life:

No context menu
No syntax highlighting

I need to recreate my vm to test this, i don't think running wsl2 will help on the test.

Brand new image

@juanfranblanco Yes, I restarted it
How did you install vscode? Through app hub or other?

@juanfranblanco
I fixed it
I had to remove the while $HOME/.vscode folder and vs code
Then I installed vscode from snap and installed the extension again and it worked

@Dmdv I think i did it through app hub. But yes it seems that the installation was broken, somehow.


Combine commands into one API call

This will require some good refactoring. Maybe we should pass through all the commands and combine them into one command if necessary, marking the last one as the one that should run, and the previous ones as "COMBINED", or something like that. Because if there is only one API call, it does not make sense to "run/finish" each individual command.
Try to use the PATCH endpoint for an item.

Actually, the api only allows patching per statement.


Fix pendingIntent for android 12 compatibility

Fixes #1322. Required for Android 12 compatibility as well as #1269.
Without these, it'll fail to build for Android 12 or crash once loaded.

Testing has shown that this fix unfortunately causes crashes on Android 5. Currently I don't have a fix for that yet.

@Vashiru Any update on this?

It looks like this issue has been addressed by the v2.2.0 android rewrite effort: https://github.com/doublesymmetry/react-native-track-player/pull/1269
I'm going to close this PR but let me know if I'm wrong. In any event any issues in the latest RC concerning this issue should be addressed in a PR against the feature/kotlinaudio branch.

since the rewrite isn't live it would have been nice to have this fix rather than try to trace it down via issues and comments.

@fierysolid you can install v2.2.0-rc3 currently. However, it's technically not considered ready to release as a fully stable version yet.
CC'ing @dcvz here in the event that he thinks this is something we can fix in a patch release. However, based on the conversations we've had I don't think it's likely.
My recommendation would be to fix this with patch-package.

After using patch-package it still seemed like the next branch was more stable

@fierysolid just to make sure I understand you, are you saying that you upgraded to v2.2.0-rc3 and you're having better results?

Correct. 2.2.0-rc3 seems to be working better on android. 👍

Great news! Thanks for the feedback.


Unstable video description?

Sometimes I cant see the video description being triggered and I cant start it manually either. This happens quite often. I have set the trigger method to automatic and it still persists
I can speak Chinese & English feel free to answer me in either of those

What version are you using, if it is chrome, the improvements I have made have not been updated as the new version has not yet been approved, I have fixed this in the new version

Oh thank you I will try Edge version

Does the problem still exist?


Fix paths relative to SVN prefix

Added 'svn' prefix on three commands on the migration process. Without it, the process will fail.

@andersonpimentel : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@hkamel
Could you review the proposed changes to your article?
Thanks!

Hi @chcomley Is this a PR you are able to review? Thanks.

Adding @steved0x

@steved0x: I'm sorry - only the author of this article, @hkamel, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

#sign-off

Thanks, folks!


Fix UUID handling in OData queries

Pull Request Description
This pull request addresses the issue of UUID handling in odata-query with SQLAlchemy, ensuring that UUIDs are treated correctly in query filters, which was previously causing errors. My solution is particularly relevant to the ongoing discussion in Issue #25 ("Filter not working for uuid column") raised by schwingkopf and others, where similar issues were encountered when filtering on UUID columns.
Problem Statement:
In my case, I encountered an issue where filtering by UUID columns in a PostgreSQL database resulted in the following error:
sqlalchemy.exc.ProgrammingError: (psycopg.errors.UndefinedFunction) operator does not exist: uuid = character varying
HINT: No operator matches the given name and argument types.

This occurred because odata-query was generating SQL queries that incorrectly treated UUIDs as VARCHAR types, leading to invalid SQL statements. The error message highlighted that the UUID type was being compared with a VARCHAR, which is not allowed.
This issue mirrors the one reported in Issue #25, where filtering by UUID columns produced no results due to a similar type mismatch.
Changes Made:

grammar.py Changes:

Introduced a new UUID pattern (_UUID_PATTERN) to properly recognize UUIDs with or without quotes._UUID_PATTERN = r"'?[\da-f]{8}-[\da-f]{4}-[\da-f]{4}-[\da-f]{4}-[\da-f]{12}'?"

Updated the GUID method to remove unnecessary quotes and parse UUIDs as GUID objects:t.value = ast.GUID(t.value.strip("'"))

This change ensures that UUIDs are treated correctly in the query parsing phase.

common.py Changes:

Modified the visit_GUID method to ensure UUIDs are passed as UUID objects in SQLAlchemy queries instead of VARCHAR strings:return literal(node.py_val, type_=Uuid())

This is essential to prevent the type mismatch that was causing the errors. As mentioned in Issue #25, SQLAlchemy expects UUIDs to be handled in a specific way, and this change resolves the mismatch by ensuring that the UUID remains in its proper form throughout query generation.

Test Changes:
Updated tests in both test_odata_to_sqlalchemy_core.py and test_odata_to_sqlalchemy_orm.py:

Updated UUID comparisons to use UUID objects:
BlogPost.c.id == uuid.UUID("a7af27e6-f5a0-11e9-9649-0a252986adba")

Updated IN clause tests:
BlogPost.c.id.in_([
    literal(uuid.UUID('a7af27e6-f5a0-11e9-9649-0a252986adba')),
    literal(uuid.UUID('800c56e4-354d-11eb-be38-3af9d323e83c'))
])

These changes ensure that the UUIDs are passed in their correct type during tests, which prevents the type mismatch errors that were mentioned in Issue #25 when handling UUIDs in IN clauses.

Contribution to the Discussion:
This pull request contributes directly to the ongoing conversation in Issue #25, where both I and other users faced similar UUID-related problems. The problem, as described in the issue, revolves around handling UUIDs properly in queries, particularly ensuring they are treated as UUID types instead of strings or VARCHARs.
In my solution, I upgraded SQLAlchemy to version ^2.0, which offers better support for UUIDs. I have tested my changes with both PostgreSQL and SQLite databases, and in both cases, I was able to successfully filter records using UUID values.
Thank you for providing such a useful library, and I hope this PR helps to resolve the issue or at least opens further discussion on UUID handling.

Thanks @OliverHofkens and @AHMETCEMRE , this is a great fix!


Updating model and context to enforce 1 itinerary max per request.

Added a unique index on the request id for the ItineraryRequests table to prevent a request being linked there twice.
Updated the Request to have a single Itinerary navigation rather than a collection.
Updated the mapping for the context creation
Added a migration - This tested locally for me without an issue. It should only fail in an unlikely case that a request is listed more than once in the ItineraryRequest table. This shouldn't be possible through the UI so is unlikely. I've checked the allReadyD database and there's no records in that table so this should deploy fine (famous last words!)

Fixes #1700

@stevejgordon, you must have eaten your Wheaties today b/c  you're knocking stuff out left and right! Let me create a couple intineraries, requets, etc... in the branch I have local now... then I'll pull this. That will be a good test of the migration (b/c as we all know, I am now super-aware of migration issues)

@mgmccarthy Haha, on a bit of a roll this week. It's the excitement for the code-a-thon next week energising me. That and not sleeping well; so I got an early start!

@tonysurma :shipit:


v5.0.0-beta.0

[ ] I have followed (at least) the PR section of the contributing guide.

Don't forgot to announce a merge lock in slack, rebase onto next and then add the new changelog items right before you intend to merge.

@oliviertassinari Should I also bump versions (alpha -> beta) of docs/packages/feedback, packages/eslint-plugin-material-ui and packages/netlify-plugin-cache-docs?

Should I also bump versions (alpha -> beta) of docs/packages/feedback, packages/eslint-plugin-material-ui and packages/netlify-plugin-cache-docs

Only if these changed.

Also, there are references to alpha inside test/bundling/fixtures/** - should these be updated as well?

Fixtures should rarely be touched. I plan on updating them every 6 months.


Multithreaded snap-it

What did you fix? (provide a description or issue closes statement)

Fixed FullScreenShot debug image missing timestamp in name
Fixed status displaying snap-it processing as finished after filtering instead of after actual snap-it processing.
Added option to multithread snap-it for a siginificant speed improvement.
When multithreaded snap-it is enabled, also adds white line below every row of text to solve issue of letters/words on different rows fusing together according to the OCR in certain circumstances.
Added proper combine order logic when piecing together item names, rather than just relying on the OCR doing it in the right order.

NOTE: multithreaded snap-it is currently turned off by default, you may want to change that.
The splitting of the image for the multithreading is based on density of black pixels on each row and column, this may or may not need tuning in the future for other themes. For now the density numbers are available in the settings file, so they can be modified on the fly if needed.
Reproduction steps

Enable "Multithread Snap" in settings (below snap noise)
Use snap-it

Evidence/screenshot/link to line
For the text rows fusing together issue, here are a handful of images that experience the issue to test with. Remember that Multithread Snap must be enabled for the fix to be in effect:
(Akjagara Prime Blueprint experiencing the issue)

(Karyst Prime Blueprint, no full image available so you may need to manually force theme to Vitruvian)

Considerations

Does this contain a new dependency? [No]
Does this introduce opinionated data formatting or manual data entry? [No]
Does this pr include updated data files in a separate commit that can be reverted for a clean code-only pr? [No]
Have I run the linter? [No]
Is is a bug fix, feature request, or enhancement? [Bug Fix/Enhancement]

Tested across a range of different scaled inventories and themes, seems to work well on 1440p as well. Only side effect being that the different items now disappear at "random" rather than nicely one after another. Adding changes to turn it on by default.


HsOpenSSL fails to build with GHC 9.12 due to Setup.hs

[1 of 2] Compiling Main             ( Setup.hs, /build/tmp.Tt5zAR40li/Main.o )
Setup.hs:75:44: error: [GHC-16444]
    • non-bidirectional pattern synonym ‘ConfigCommonFlags’ used in an expression
    • In a record update at field ‘configVerbosity’
      and with pattern synonym ‘ConfigCommonFlags’.
      In the second argument of ‘setFlag’, namely
        ‘cfg {configVerbosity = toFlag silent}’
      In the second argument of ‘($)’, namely
        ‘setFlag (mkFlagName f) cfg {configVerbosity = toFlag silent}’
   |
75 |                     setFlag (mkFlagName f) cfg { configVerbosity = toFlag silent }
   |                                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

I will gladly accept the patch that fixes this.

I revised the published versions with the Cabal < 3.14 bound:
2024-12-31T10:16:13Z  	AndreasAbel	  HsOpenSSL-0.11.7-r1
2024-12-31T10:16:13Z  	AndreasAbel	  HsOpenSSL-<IP_ADDRESS>-r1
2024-12-31T10:16:13Z  	AndreasAbel	  HsOpenSSL-<IP_ADDRESS>-r1
2024-12-31T10:16:12Z  	AndreasAbel	  HsOpenSSL-<IP_ADDRESS>-r2
2024-12-31T10:16:12Z  	AndreasAbel	  HsOpenSSL-<IP_ADDRESS>-r1
2024-12-31T10:16:12Z  	AndreasAbel	  HsOpenSSL-<IP_ADDRESS>-r1
2024-12-31T10:16:12Z  	AndreasAbel	  HsOpenSSL-<IP_ADDRESS>-r2
2024-12-31T10:16:11Z  	AndreasAbel	  HsOpenSSL-<IP_ADDRESS>-r4
2024-12-31T10:16:11Z  	AndreasAbel	  HsOpenSSL-<IP_ADDRESS>-r1
2024-12-31T10:16:11Z  	AndreasAbel	  HsOpenSSL-0.11.6-r1
2024-12-31T10:16:11Z  	AndreasAbel	  HsOpenSSL-<IP_ADDRESS>-r1
2024-12-31T10:16:11Z  	AndreasAbel	  HsOpenSSL-<IP_ADDRESS>-r1
2024-12-31T10:16:10Z  	AndreasAbel	  HsOpenSSL-0.11.5-r2
2024-12-31T10:16:10Z  	AndreasAbel	  HsOpenSSL-<IP_ADDRESS>-r1
2024-12-31T10:16:08Z  	AndreasAbel	  HsOpenSSL-<IP_ADDRESS>-r1
2024-12-31T10:16:07Z  	AndreasAbel	  HsOpenSSL-<IP_ADDRESS>-r1
2024-12-31T10:16:07Z  	AndreasAbel	  HsOpenSSL-<IP_ADDRESS>-r1
2024-12-31T10:16:07Z  	AndreasAbel	  HsOpenSSL-<IP_ADDRESS>-r1
2024-12-31T10:16:07Z  	AndreasAbel	  HsOpenSSL-<IP_ADDRESS>-r3
2024-12-31T10:16:07Z  	AndreasAbel	  HsOpenSSL-<IP_ADDRESS>-r2
2024-12-31T10:16:06Z  	AndreasAbel	  HsOpenSSL-<IP_ADDRESS>-r2
2024-12-31T10:16:06Z  	AndreasAbel	  HsOpenSSL-<IP_ADDRESS>-r1

It seems like Setup.hs does not actually influence the installation, it only provides advice to mac users how to install the system libraries.  This could as well be restricted to the README.
If my assumption about Setup.hs is correct, I suggest to simply remove it and use build-type: Simple instead.
Custom setups easily break with Cabal updates and the cabal developers are discouraging custom setups, looking for a new, more declarative model.
If you agree @vshabanov , I can submit a PR to that extend.

CC @Kleidukos maybe you have an opinion on this...

In favour of removing the Custom build type, which can be replaced with the new Hooks build type when it gets sufficiently adopted, if needed. :)


⚠ Bofrost.com has degraded performance

In 2d7e2e3, Bofrost.com (https://www.bofrost.com) experienced degraded performance:

HTTP code: 200
Response time: 1196 ms

Resolved: Bofrost.com performance has improved in fe23a32 after 6 minutes.


Contribution guideline: avoid false positives.

Suggestion: Contributions should avoid false positives.
It's easy to add a new language with a file extension in languages.yml (or add a new extension to an existing language), but that may result in a great number of files being misdetected.  This isn't doing new languages any service, since e.g. searches, trendling lists, etc will be cluttered with unrelated results.  Usually this can be avoided with a heuristic.

@arfon Looks great!  Closing this.

@arfon Looks great!  Closing this.

:+1: thanks!

:+1: thanks!


Update backup-instant-restore-capability.md

Not sure if this is the best wording, but we have a customer confused by this paragraph. They are looking for actual snapshot resources created by Backup, but those don't exist for managed disk VM backups. You can contact me here or internally at v-dibr with questions.

@dcbrown16 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@ShannonLeavitt : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Stop gradle build when "gradle detects a problem"

Hi,
Expected Behavior
I want to have the ability to break the build if gradle detects a problem. Something like ./gradlew --break-on-problems. As these problems could be serious.
Current Behavior
Quietly logged and mostly overseen.
Execution optimizations have been disabled for task ':foobar:server:checkstyleMain' to ensure correctness due to the following reasons:
  - Gradle detected a problem with the following location: '/Projects/workspace/foobar/server/target/resources/main'. Reason: Task ':foobar:server:checkstyleMain' uses this output of task ':foobar:server:writeGitPropertiesFile' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.1.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.

Context
Incorrect results being produced will be overseen

You need to clarify what is "problem". If you mean break on any warning output, you can customize logging and abort the build upon any warning logs, or any specific texts. https://docs.gradle.org/current/userguide/logging.html

Whenever gradle logs "Gradle detected a problem with the following", the build should be terminated. I want it to be reliable. Not that the gradle team change the wording and then my logchecker does not work anymore.

I see, I'm reopening it, but I don't thing it would be implemented in a short term.

There is already --warning-mode fail that does what is requested.

Build will fail if in case of using deprecated method which will be removed in next version.


Migrated db

The following tasks were accomplished in this milestone

[x] Migrated data models and update some files

Status: Approved 🟢 🟢 🟢
Hi @binodbhusal ,
Your project is complete! There is nothing else to say other than... It's time to merge it: ship it:
Congratulations! 🎉
Highlights:
✅ Tasks  👍🏽
✅ Good descriptions of tasks 👍🏽
👉🏼 All the best and good luck with your project
Cheers, and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.


Improve ImageConverter performance

Converting a 2208x1242 RGB image to BGR using the airo_camera_toolkit is much slower (~100x) than the equivalent OpenCV cvtColor method.

The reason is that we store the image as 0-1 float images as an intermediate step. This requires 4x the memory and also a division by 255.0 for all pixels.  For this reason I've started to use cvtColor in my performance critical code.
I'm not really sure what the best solution is. We want to keep the ImageConverter for easy torch integration, but maybe we should take a more functional approach like OpenCV and remove the intermediate storage as a float-image?
@tlpss thoughts?

yeah reason for this 'unified' intermediate is to keep implementation complexity low. My first thought is to mention this in the code? This is a simple implementation for convenience, if you need high performance, consider using optimized methods such as opencv? Because if you work on GPU, even opencv will be slow.. so would be hard to support the best option for each case
If you want to provide better performance by dropping the intermediate layer by adding more logic to the class, that is also fine! we could store the image in the format we get it, and then write optimized conversions for all types? But still I would add the warning to the image class!


Screen lineal - Add button to show it now

Description of the new feature / enhancement
On Powertoys menu there is a feature called "Screen lineal" (or something like that). This is nothing I need a hotkey for but I would like to have a button on this page to show this overview when I need it. Right now it can only be opened with a hotkey.
Scenario when this would be used?
If we want to display it without having to assign and use a key combination
Supporting information
No response

/dup #21763

Why is this a dupe? Its for a different feature?

Because it's all about the same: having a button instead in addition to a hot key.


add append time smoke test

add append time smoke test about #223

(Jove Github Bot) added it to the current sprint.


License?

Before I download this and give it a shot, is there a license for this?

@bvarner I've added LICENSE into this repository. Now this is distributed under MIT License.
Thank you very much for having an interest on this project!


"There was an error during cups operation: success"

Describe the bug
"There was an error during cups operation: success" when adding a remote printer using LPR. In cups webGUI, I'd entered the same printer address than in the Linux Mint add printer GUI, nothing happens when clicking "Continue". The page just get reloaded.
To Reproduce
Steps to reproduce the behavior on CUPS webGUI:

Go to 'Add printers'
Fill with info
Click continue
nothing happens.

Steps to reproduce the behavior on Linux Mint add printers:

Go to 'Add printers'
Fill with info
Click continue
"There was an error during cups operation: success".

Expected behavior
On both Linux GUI and CUPS webGUI, the select driver interface supposed to show up.
Screenshots

System Information:

OS and its version: Linux Mint 21.3 x64
CUPS version 2.4.1

Additional context
I did search and, there was similar issues but not exactly what covering my problem.
I do have 3 other printers on the system.
Since few time, I do have the same error when adding other printers as well.

Hi,
please turn on CUPS debugging, reproduce the issue and upload the logs here with .txt suffix.

Hello,
Sorry for the delays.
When reproducing the issue, it only writing lines in access_log , nothing in error_log .
access_log.txt
It affect also another computer, in the same way.
Guillaume

Is that issue can be reopened? I still have an issue.

No logs in error_log is strange - have you enabled the CUPS debug logging? Or do you redirect logs into syslog/journal?
I don't plan to reopen until I have at least logs to examine.

This is what we're looking for:
error_log.txt
Guillaume

I see from the logs:
D [11/Jul/2024:14:23:55 -0400] [CGI] Started ippfind (PID 656011)
I [11/Jul/2024:14:23:56 -0400] Expiring subscriptions...
D [11/Jul/2024:14:24:54 -0400] [Client 6] Closing on unexpected HTTP read state HTTP_STATE_POST_SEND.
D [11/Jul/2024:14:24:54 -0400] [Client 6] Closing connection.
D [11/Jul/2024:14:24:54 -0400] cupsdSetBusyState: newbusy="Not busy", busy="Active clients"
I [11/Jul/2024:14:24:54 -0400] Expiring subscriptions...
D [11/Jul/2024:14:24:54 -0400] Report: clients=2
D [11/Jul/2024:14:24:54 -0400] Report: jobs=0
D [11/Jul/2024:14:24:54 -0400] Report: jobs-active=0
D [11/Jul/2024:14:24:54 -0400] Report: printers=0
D [11/Jul/2024:14:24:54 -0400] Report: stringpool-string-count=397
D [11/Jul/2024:14:24:54 -0400] Report: stringpool-alloc-bytes=5624
D [11/Jul/2024:14:24:54 -0400] Report: stringpool-total-bytes=6784
D [11/Jul/2024:14:24:54 -0400] PID 655985 (/usr/lib/cups/daemon/cups-driverd) was terminated normally with signal 9.

I see starting ippfind, but no end of it - probably we could see more when debug2 was enabled, but I kind of recall this was an issue in the past - ippfind from driverless backend from cups-filters project took too long, causing listing drivers to timeout.
For sure we should not end with "success", but otherwise it is not CUPS issue.
Can you try some latest versions of cups-filters? 2.0.0 or such - based on CUPS version I guess cups-filters there will be pretty old too.

To emphasize - the fix here will be only change of error message, otherwise the issue lies in the other project -> cups-filters, but I would guess the issue is fixed in newer cups-filters releases.
Basically, cups-filters needs to tell ippfind to end within reasonable time.

So, I just need to update CUPS on those two machines?
Simple as that?

Not cups, but cups-filters - two different projects on Github and two different packages. And first - I don't know for sure, but I'm running on latest projects versions in Fedora and I don't see the issue, the second - I speak from the project perspective. Whether the latest upstream versions are in your OS, that's the question for your distro maintainers.


Scope of cache being stored

If a PR restores cache that was scoped to master and saves it at the end of the action, does the scope of the cache change to that of the PR's or does it remain in master's scope?
For example -
Let's say I have folder tempFolder cached on the master branch.
I create a PR that restores cache from master and downloads tempFolder. The action then makes some changes tempFolder, and at the end, the cache is saved.
Does the scope of tempFolder change from master to that of the PR?

It would create a new cache in the scope of the PR.  This would result in a cache in master with the old tempFolder and a cache in the PR with the modified tempFolder.

Closing this issue.  Please feel free to re-open if you have any further questions.


Support for Grist

Grist

A modern, open source spreadsheet that goes beyond the grid.

Open source alternative to Airtable/Baserow/Nocodb, see their website, repo gristlabs/grist-core | Github (⭐ 6.1K)
What do you use this database for?
Collaborative database with REST API. Highly customisable and extendable.
Are there any popular and well-maintained clients for this database?
REST API Reference, or Typescript SDK
Are you interested in contributing this database connector?

If you're interested in having a go at this, check out our new docs on creating a plugin connector!
https://docs.evidence.dev/plugins/creating-a-plugin/datasources


Improve localization docs for JS users

Following up on https://github.com/lit/lit/pull/2188, update https://lit.dev/docs/libraries/localization/ to document how to use localize with plain JS instead of TS.

Done in https://github.com/lit/lit.dev/pull/585


symbiotic build - git_submodule_init() doesn't copy submodules to the build directory

directories LLVMSlicer, dg and svc15 are not created during build, build is aborted

Works fine here (tried with fresh clone). Can you provide more information?

Well, the build is aborted on line 261, saying there is no directory called LLVMSlicer. I fresh cloned symbiotic and I am building in other dir called symb-build - empty one. I don't know how "git submodule" works, but it is called in symbiotic main directory, so I can't see why should it create directories in build. From log it seems the clone runs, but i suppose it does so in symbiotic directory. Am I missing something here?

Oh, am I supposed to build in main directory now? The wiki hasn't been changed, but I see that may be the only case here.

Oh, yes, you're right. I'll change the wiki and also fix the script so that the build will work in or out of the main directory. Thanks


Dynamic includes

http://docs.ansible.com/ansible/playbooks_conditionals.html#applying-when-to-roles-and-includes
- include: ec2_autoscaling.yml
 when: {{ enable_auto_scaling_group }}

done for a few


feat: add work permit fields

References CAR-9275
Motivation and context
Related PR : https://github.com/carforyou/carforyou-listings-web/pull/3919

I asked BE and it's too much effort for them to change the name.
To be honest I though workPermit was fine and I confirmed BE could go with that. The blame is on me here and it seems like there's little I can do to fix it


[components] support multiple owners

What does this PR do?
[components] support multiple owners

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge

/merge


Problem: can't compile LCNF to alternative backends

Solution: compilers for alternative backends would like to know the bodies of functions that are exposed to the world. One example of such function is Float.ofScientific.

Sorry, silly Github defaults!


Correctly compute  pyproject.toml path

Fixes #212

repro fixed: https://github.com/messense/polars/actions/runs/6381117939/job/17317269189#step:13:95


Voice Chat is global

Did you read the README?: Yes
Describe the bug
When we load in and talk we can hear eachother from across the map.

Not a pma-voice issue


Add support for scanning container images in remote registries

This will allow for manifesting of managed services, which are deployed off of specific Quay.io images and built directly from source (mostly GitHub repos).

@RedHatProductSecurity/corgi-devs Please review.


#200 - Moving three.js outside of whs build

This PR is related to issue #200

Coverage increased (+6.6%) to 56.851% when pulling 8ca1ebb571fdffc5383306437be25cb97a97e883 on #200 into fbaadb33bc3e35200a897dae8a37d3bb5295f935 on beta.


Update graphdb-runtime-extension

Pull in latest main changes so we can do private & public paths (https://github.com/holium/memedeck/pull/8).
The process_lib fork also needs to be updated: https://github.com/holium/process_lib

@drunkplato seems like some merge conflicts were not resolved:
https://github.com/holium/holon/blob/8bbd6b1011d94a420d9e3cc69bb977155fb5d3b9/Cargo.toml#L3


[Bug]: Remote Work Configurations Won't Work Beacuse of Turkish Characters

Apache Hop version?
2.6.0
Java version?
<IP_ADDRESS>
Operating system
Windows
What happened?
Create a simple workflow with a start and a pipeline and make sure the name or the action of the pipeline contains one of many Turkish specific characters such as Ş, Ç, Ö, Ğ etc. This makes it so that Remote Run Configurations won't work with the error:
Invalid byte 1 of 1-byte UTF-8 sequence.

Tested on both Linux/Windows servers and with both Turkish locale installed and not. Maybe i'm doing some simple step wrong but couldn't find any solution.
Thanks in advance.
Issue Priority
Priority: 3
Issue Component
Component: Hop Server

Test case to repoduce the problem, work fine on local but not on remote server.
remote-execute-with-Turkish-characters.zip


[libwebrtc] x64 compilation failing

The bundled nasm toolchain is not finding a glibc that is likes.
| FAILED: obj/third_party/dav1d/dav1d_asm/itx16_avx2.o
| vpython3 ../../build/gn_run_binary.py nasm -DPIC -felf64 -P ../../third_party/dav1d/config/linux/x64/config.asm -I../../third_party/dav1d/libdav1d/src// -I../../third_party/dav1d/config/linux/x64/ -I./ -I../../ -Igen/ -DSTACK_ALIGNMENT=16 -MD obj/third_party/dav1d/dav1d_asm/itx16_avx2.o.d -o obj/third_party/dav1d/dav1d_asm/itx16_avx2.o ../../third_party/dav1d/libdav1d/src/x86/itx16_avx2.asm
| ./nasm: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by ./nasm)
| ./nasm: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by ./nasm)
| ./nasm: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by ./nasm)
| nasm failed with exit code 1

Resolved with https://github.com/meta-flutter/meta-flutter/pull/631


Update key Id generation logic

Update keyid logic to generate keys ids between 10 and 99
Removed auth from private key endpoint. For alpha, we will reply on attestation report

The CI did not pass

@sureshchahal The CI fails. Try make demo and npm run test Status: 200 Response data: {"auth":null,"description":["azure-privacy-sandbox-kms","Key Management Service","1.0.0","true"]}
✅ [PASS] - Assert OK statusCode
file:///workspaces/azure-privacy-sandbox-kms/test/e2e-test/src/index.ts:235 const currentValue = toTest[fieldName]; ^
TypeError: Cannot read properties of null (reading 'policy') at Demo.assertField (file:///workspaces/azure-privacy-sandbox-kms/test/e2e-test/src/index.ts:235:36) at Demo.start (file:///workspaces/azure-privacy-sandbox-kms/test/e2e-test/src/index.ts:69:12) at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
Node.js v22.9.0
💀 Stopped sandbox process due to an error 💥 Error details: Exit Status : 1 Last Command : ${testScript} 2>&1
Error Output : No log available

make: *** [Makefile:76: demo] Error 1
Error: Dev container exec failed: (exit code: 2) Error: Dev container exec failed: (exit code: 2)

@beejones  I checked CI result and all e2e tests passed. For npm run test, they pass on my local but look like CI is not able to find them. To me, it seems like a setup issue with CI rather than pull request itself. I am getting different result in local vs server. How can we move forward on this.
I am seeing this in latest CI run
_ ✅ [PASS] - Assert Member 0::key == dPcnQRbpEZXVi+Nj/T5BpHkbEu+Gjct2MFPpR0Etcl8=
✅ [PASS] - Assert Member 0::id == 100002
✅ [PASS] - Assert headers["cache-control"] == "max-age=254838"
===============================================
🎉 All Tests Passed...
🏁 Test Completed...
💀 Stopped sandbox process

test
node --experimental-vm-modules node_modules/jest/bin/jest.js

No tests found, exiting with code 1
Run with --passWithNoTests to exit with code 0
In /workspaces/azure-privacy-sandbox-kms
143 files checked.
testMatch: /test/unit-test//*.test.(ts|js|mjs) - 6 matches
testPathIgnorePatterns: /node_modules/, /lib/ - 134 matches
testRegex:  - 0 matches
Pattern:  - 0 matches
Error: Dev container exec failed: (exit code: 1)
Error: Dev container exec failed: (exit code: 1)
_

Local Test run
Test Suites: 6 passed, 6 total Tests:       27 passed, 27 total Snapshots:   0 total Time:        1.19 s, estimated 3 s Ran all test suites.


Complete normalization

What does this PR do?

Fix ascii range
Fix early exit in ascci case
Make unicode handling faster by checking lowercase class before computing the lowercasing

Motivation
What inspired you to submit this pull request?
Additional Notes
Anything else we should know when reviewing?
How to test the change?
Describe here in detail how the change can be validated.

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

Project coverage is 70.43%. Comparing base (e7822db) to head (eefad2f).

Additional details and impacted files
@@                           Coverage Diff                           @@
##           vianney/inplace-trace-normalization     #520      +/-   ##
=======================================================================
- Coverage                                70.45%   70.43%   -0.02%
=======================================================================
  Files                                      205      205
  Lines                                    27922    27884      -38
=======================================================================
- Hits                                     19672    19640      -32
+ Misses                                    8250     8244       -6

Components
Coverage Δ

crashtracker
16.70% <ø> (-0.02%)
:arrow_down:

datadog-alloc
98.76% <ø> (ø)

data-pipeline
51.15% <ø> (ø)

data-pipeline-ffi
0.00% <ø> (ø)

ddcommon
86.12% <ø> (-0.46%)
:arrow_down:

ddcommon-ffi
74.15% <ø> (-1.17%)
:arrow_down:

ddtelemetry
59.37% <ø> (+0.04%)
:arrow_up:

ipc
84.66% <ø> (ø)

profiling
78.63% <ø> (ø)

profiling-ffi
58.19% <ø> (ø)

serverless
0.00% <ø> (ø)

sidecar
36.19% <ø> (ø)

sidecar-ffi
0.00% <ø> (ø)

spawn-worker
54.98% <ø> (ø)

trace-mini-agent
69.70% <ø> (ø)

trace-normalization
98.24% <100.00%> (-0.11%)
:arrow_down:

trace-obfuscation
95.75% <ø> (ø)

trace-protobuf
77.16% <ø> (ø)

trace-utils
91.12% <ø> (+0.36%)
:arrow_up:


Remove duplicated lines with -p

get_real_title() generates the same line when the diff object include the same urls.
Solution:
diff_lines -> map of get_real_title() -> list -> sorted(set)

Related #45


[feat]Use SSA form in global variable

The form should like:
x = 1

fn foo() {
  println(x)
}

fn main() {
  let x = 2
  println(x) // 2, override outside scope
  foo() // 1
}

The reason is I don't think mutable global var can bring good code.

Complete at commit: 9ad1fbd8ac7dbc760f6e876d4abd08325887a065


mods

Are you sure the mods are working for you? Im trying to zero out the stamina cost of jumping, but its not working:
ExecuteAsync(function()
    GameSettingInstance = FindFirstOf("PalGameSetting")
    GameSettingInstance.JumpSP = 0
end)

Could it be client-sided? I'll check it out later.

Here's another mod that stops Stomach from decreasing and it's working:
ExecuteAsync(function()
    GameSettingInstance = FindFirstOf("PalGameSetting")
    GameSettingInstance.StomachDecreace_perSecond_Player = 0.0
end)

I think the issue is whether the stamina is localized, or the real variable that's getting used is somewhere else.

Here's another mod that stops Stomach from decreasing and it's working:
ExecuteAsync(function()
    GameSettingInstance = FindFirstOf("PalGameSetting")
    GameSettingInstance.StomachDecreace_perSecond_Player = 0.0
end)

I think the issue is whether the stamina is localized, or the real variable that's getting used is somewhere else.

Yes.
I imagine that stamina is client-side.
Is there a more practical way to determine if the function is client or server-side?

Here's another mod that stops Stomach from decreasing and it's working:
ExecuteAsync(function()
    GameSettingInstance = FindFirstOf("PalGameSetting")
    GameSettingInstance.StomachDecreace_perSecond_Player = 0.0
end)

I think the issue is whether the stamina is localized, or the real variable that's getting used is somewhere else.

Yes. I imagine that stamina is client-side. Is there a more practical way to determine if the function is client or server-side?

You'll need to figure it out by testing or reverse engineering. In my opinion, testing is more practical


PoseLandmarker - segmentationMasks not in  the PoseLandmakerResult

Have I written custom code (as opposed to using a stock example script provided in MediaPipe)
Yes
OS Platform and Distribution
Windows
Mobile device if the issue happens on mobile device
No response
Browser and version if the issue happens on browser
Google Chrome
Programming Language and version
JavaScript
MediaPipe version
0.10.8
Bazel version
No response
Solution
PoseLandmarker
Android Studio, NDK, SDK versions (if issue is related to building in Android environment)
No response
Xcode & Tulsi version (if issue is related to building for iOS)
No response
Describe the actual behavior
segmentationMasks not in poseLandmarker results with options outputSegmentationMasks: true
Describe the expected behaviour
poseLandmarker results should have segmentationMasks with MPMask type
Standalone code/steps you may have used to try to get what you need
Set options:

const options: PoseLandmarkerOptions = {
  baseOptions: {
    modelAssetPath: `https://storage.googleapis.com/mediapipe-models/pose_landmarker/pose_landmarker_lite/float16/latest/pose_landmarker_lite.task`,
    delegate: "GPU"
  },
  runningMode: "VIDEO",
  numPoses: 2,
  outputSegmentationMasks: true,
};
const poseLandmarker = await PoseLandmarker.createFromOptions(vision, options);

The listener:
poseLandmarker.detectForVideo(videoRef.current, startTimeMs, (result) => {
  console.log(result)
})

Results only have landmarks, worlodLandmarks and g.
Don’t know what g is, but its format is similar to MPMask.

### Other info / Complete Logs

_No response_

Oops. Will fix this ASAP.


New version: FaSTLMM v0.2.3

Registering package: FaSTLMM
Repository: https://github.com/sens/FaSTLMM.jl
Created by: @sens
Version: v0.2.3
Commit: 17c463dc58eb12d930eb5c2f5095cfd9328cbd89
Git reference: master

Needs a [compat] section in Project.toml with at least an entry for julia itself, e.g.:
[compat]
julia = "1"

would mean that the package is compatible with Julia versions [1.0.0, 2.0.0).

I have added the compat section as you outlined.

You need to retrigger the registration.

Please use consecutive version numbers in the future.

BTW, the package does not appear on pkg.julialang.org/docs.  What else do I need to do for it to appear there?


Enhancement.

It was suggested to me over at GitLab that I pull in missing hosts for my new ZuckerBlock hosts-file. It includes Giphy hosts, as well as Oculus & Libra, and is CC0. So have a look, pull in what you need, and I'll do the same as we are both using the CC0 license. The repo is here: https://gitlab.com/intr0/zuckerblock. Peace.

Gitlab have smaller community so i don't know which improvements this will give you.

I want to be able to quickly delete all fb-related cookies, etc from my browser, so I'm looking for a list of expressions to search the cookie list to delete.  I can sort of eyeball a corporations/Facebook/all or ZuckerBlock list, looking at the second level part of the domains (SLD) and do it that way.  Anyone else interested in such a list?  (Facebook, insta, fbc...?   ).   As long as this Issue has a vague title, this seems like a not awful place to mention this enhancement idea - and get feedback.  Thinking selecting out the SLDs plus | sort | uniq would be an OK way to generate it, but maybe not.

Send PRs.


No applets and touchpad gestures

Hello
Today i installed cosmic. But i find it difficult to adapt because of the following problems. I can't add any applets, because every time i go in the settings and go to Panel / Applets a window on the side opens but there aren't any applets displayed.
Another Problem are the touchpad gestures. When i go to the touch pad gestures in the settings app it only shows Workspace Swipe.
Aren't there any other options or do i need to add them manually?
And my third problem is my touchscreen. Is it possible to set up touchscreen gestures in cosmic?
Thanks for any help

I am also experiencing issues, that I cannot change any applets.
I tried the follwoing two options:

I am also having problems that applets dont appear. I have tried adding cosmic-applets the following ways in my configuration.nix
    environment.systemPackages = with pkgs; [
        # inputs.nixos-cosmic.legacyPackages.${pkgs.system}.cosmic-applets   # does not rebuild
        cosmic-applets    # does rebuild, but doesnt chagne the situation
    ];

I am also having problems that applets dont appear. I have tried adding cosmic-applets the following ways in my configuration.nix. This did not work though.
    environment.systemPackages = with pkgs; [
        # inputs.nixos-cosmic.legacyPackages.${pkgs.system}.cosmic-applets   # does not rebuild
        cosmic-applets    # does rebuild, but doesnt chagne the situation
    ];

The issue not that cosmic-applets is missing (else applets wouldn't be running at all)
This is a recent (like last week or two) cosmic-settings regression and no one has had time to debug it

Okay, thank you for the heads up!

This appears to have been fixed upstream now. Can you retest?

Just tested it. The applet customization works again :+1:
I cannot speak though on the touchpad problem of @Postboote1 as I do not have a touchpad


request doesn't support rpcTimeOut

Unlike csharp and java, a "request/reply" action doesn't seem to allow for a timeout after which the request is auto-failed.

Sure it does! The timeout is not specified with the request. Instead there's a timeout function that you can call and associate with the subscriber id (returned by subscribe and request). Here's an example.
#!/usr/bin/env node

'use strict';

var nats = require('nats').connect();

nats.on('error', function(e) {
  console.log('Error [' + nats.options.url + ']: ' + e);
  process.exit();
});

var sid = nats.request("foo", {'max':1}, function(e) {
  console.log('callback called: ' + e);
});

nats.timeout(sid, 1000, 1, function(sid){
  console.log('the subscriber timedout: ' + sid);
});


Commiting pending changes before change accessor leaves due to read access?

I often see Commiting pending changes before change accessor leaves due to read access. in the dev tools running out of sources and I have no clue what this means or what I should do to prevent it.
This warning needs some explanation or be removed if useless.

I cannot reproduce now anymore but I think I often saw it when saving an untitled file (where we quickly replace the editor with its saved version).


Arnej/config class should not be public

I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.
@bratseth please review
@baldersheim @hmusum @toregge FYI

Consider moving the using statements to the document::config namespace

I tried that first, but it felt like more work for less consistent and less readable code.

I tried that first, but it felt like more work for less consistent and less readable code.

But that means that config-documenttypes.h won't work as a drop-in replacement for documenttypes_config_fwd.h, you might need both if you depend on the using being in the global namespace and you need the actual config definition.


Cannot link that fatal error LNK1120: 1 unresolved externals

= note:    Creating library F:\rust\lapce-master\target\release\deps\lapce.lib and object F:\rust\lapce-master\target\release\deps\lapce.exp
libtree_sitter_json-07069347542251e6.rlib(tree_sitter_json-07069347542251e6.tree_sitter_json.e2be5b27-cgu.0.rcgu.o) : error LNK2019: unresolved external symbol tree_sitter_json referenced in function _ZN16tree_sitter_json8language17h5e9cd0f39d07829bE
F:\rust\lapce-master\target\release\deps\lapce.exe : fatal error LNK1120: 1 unresolved externals
error: could not compile lapce due to previous error
evn: windows 10, rust 1.60

Does this happen consistently, i.e. after running cargo clean?

after cargo clean & cargo build --release, compling is ok, but when starting up:


popup won't install

I was trying to install auto-complete but its dependency, popup, won't install. I ran brew update, upgrade, and doctor but nothing seems to help.
~ >>> brew install popup
==> Installing popup from homebrew/emacs
==> Downloading https://github.com/auto-complete/popup-el/archive/v0.5.3.tar.gz
==> Downloading from https://codeload.github.com/auto-complete/popup-el/tar.gz/v0.5.3
######################################################################## 100.0%
==> make travis-ci CASK=/usr/local/Cellar/cask/0.8.1/bin/cask
Last 15 lines from /Users/souper/Library/Logs/Homebrew/popup/01.make:
shut-up.el:150:1:Warning: the following functions are not known to be defined:
    shut-up-write-region-original, shut-up-load-original
Done (Total of 1 file compiled, 2 skipped)
Setting ‘package-selected-packages’ temporarily since "emacs -q" would overwrite customizations
Generating autoloads for package-build.el...
Generating autoloads for package-build.el...done

Checking /private/tmp/popup-20161111-69647-gqy760/popup-el-0.5.3/.brew_home/.emacs.d/.cask/25.1/bootstrap/package-build-20161014.2251...
Compiling /private/tmp/popup-20161111-69647-gqy760/popup-el-0.5.3/.brew_home/.emacs.d/.cask/25.1/bootstrap/package-build-20161014.2251/package-build-autoloads.el...
Compiling /private/tmp/popup-20161111-69647-gqy760/popup-el-0.5.3/.brew_home/.emacs.d/.cask/25.1/bootstrap/package-build-20161014.2251/package-build-pkg.el...
Compiling /private/tmp/popup-20161111-69647-gqy760/popup-el-0.5.3/.brew_home/.emacs.d/.cask/25.1/bootstrap/package-build-20161014.2251/package-build.el...
Done (Total of 1 file compiled, 2 skipped)
touch .cask/25.1.1/elpa
touch: .cask/25.1.1/elpa: No such file or directory
make: *** [.cask/25.1.1/elpa] Error 1

READ THIS: https://git.io/brew-troubleshooting

I'm running emacs version 25.1.1

Ah, I ran into that a while ago but forgot to fix it.  Once https://github.com/Homebrew/homebrew-emacs/pull/503 is merged it should work again.

oh awesome. thanks!


[ISSUE #2284]Simplify the code

Fixes https://github.com/apache/incubator-eventmesh/issues/2284
Motivation
Explain the content here.
Explain why you want to make the changes and what problem you're trying to solve.
Modifications
Describe the modifications you've done.
Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
If a feature is not applicable for documentation, explain why?
If a feature is not documented yet in this PR, please create a followup issue for adding the documentation

@weihubeats why you add the Assert class, junit has already done it.

Assert is only used for testing, the added Assert is used for null checking in the program, or we can rename the Assert to AssertUtils

Assert is only used for testing, the added Assert is used for null checking in the program, or we can rename the Assert to AssertUtils

Ok, maybe rename to AssertUtils is better.

ok


Rfxtrx binary sensor

Description:
This brings a new platform "rfxtrx" in the binary sensors components. It mainly supports cheap binary sensors that can be found on some chinese web sites (motion sensors, door / window opening, doorbells...) based on the PT-2262 RF chip.
It also provides a few specific configuration options that could be ported to other binary sensor platforms.
Related issue (if applicable): N/A
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#2336
Example entry for configuration.yaml (if applicable):
# Example configuration.yaml entry
binary_sensor:
  platform: rfxtrx
  automatic_add: True
  devices:
    091300006ca2c6001080:
    name: motion_hall
    sensor_class: motion
    off_delay:
      seconds: 5
<PHONE_NUMBER>670e013b70:
      name: window_room2
      sensor_class: opening
      data_bits: 4
      command_on: 0x0e
      command_off: 0x07

Checklist:
If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

Hi @ypollart,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

I'm looking for a feature like this. Any chance that this will be merged in the near future @ypollart @Danielhiversen?

@Danielhiversen is this PR ready to merge?

The rfxtrx component is broken: https://github.com/home-assistant/home-assistant/issues/6581#issuecomment-286562487 and https://github.com/home-assistant/home-assistant/pull/6844#issuecomment-290117240
I do not have much time for HA these days, so I am not sure when I will have time to look in to it.
Maybe not a good idea to add more features before this is fixed?

Just merged that bug fix @Danielhiversen.

It seems like you have some commits in this branch that are not yours, please clean it up.

I rebased my branch and merged with dev. Should be on now. Thanks.

@DanielHiversen if you have time, could you give this PR a 👍  or 👎  ?

Could this change be causing https://github.com/home-assistant/home-assistant/issues/8907


Prevent subclassing

It seems the subclassing of NucleusActivity is the only option for now. I can see from your code that all the logic actually lies in PresenterHelper, but it would probably be a little bit verbose to use it in all activities. I guess that's why you introduced NucleusActivity.
Starting from API 14 we can register callbacks on activity lifecycle, so the subclassing could probably be replaced by a simple call to something like Nucleus.bind(this) in the onCreate() of each activity.
What do you think?
EDIT: It would probably be a second option rather than a replacement, since it wouldn't be compatible with API < 14.

You need to have a field in activity so activity can easily access presenter, and that field should also be accessible from the code that controls the presenter's lifecycle. This is encapsulation break. Otherwise you will need to implement NucleusAcitivtyManager, and access presenter from that manager, so instead of getPresenter() you will have to write Nucleus.getPresenter(this) every time. All of this looks like overcomplication to me. Inheritance just works.
There are also uniformity considerations. Right now you can be sure that all presenters and views in Nucleus work the same way, so it is easy to understand the whole picture.
If you will create an implementation for Manager, I would like to see it anyway, probably you will find an elegant solution :)

Inheritance just works.

Until another lib decides to do the same.

You will need to have a field in activity so activity can easily access presenter, and that field should also be accessible from the code that controls the presenter's lifecycle. This is encapsulation break. Otherwise you will need to implement NucleusAcitivtyManager, and access presenter from that manager, so instead of getPresenter() you will have to write Nucleus.getPresenter(this) every time. All of this looks like overcomplication to me.

The proper way would probably be to inject the presenter in a @Presenter or @Inject annotated field during the Nucleus.bind(this) call.

There are also uniformity considerations. Right now you can be sure that all presenters and views in Nucleus work the same way, so it is easy to understand the whole picture. (There are also NucleusLayout and NuleusFragment classes).

Good point.

If you will create an implementation for Manager, I would like to see it anyway, probably you will find an elegant solution :)

I'll really try to get my hands on Flow/Mortar for my next project, but yeah, I'll keep you posted if I do. :)

| Until another lib decides to do the same.
I am aware of such possibility, this is why Nucleus is not tied to any specific view class - you can just copy/paste code that controls Presenter.


App extension flag

@ipodishima here's a much simpler app-extension compatibility PR that uses a WA_APP_EXTENSION flag to avoid calling [UIApplication sharedApplication].
Thanks for the sweet library, btw.  Not being able to define a stack of view controllers was my main frustration with existing routing libs also.  You saved me from having to write all this from scratch :)

:+1:
Thanks for the contribution!
I'm still in the process of integrating it into a final app, so there might some bugs or things I did not thought about. Will debug it in the next few weeks but if you find something else...

Sure, no problem :smile:
I'll let you know if I run into anything while I'm playing with it


Indices are (wrongly?) assumed to be integers and zero-based

I have a comment regarding terminology.
The indices the library computes for the Edit steps are currently always integers and always zero-based (i.e. the first index is 0). This works great for the intended main use case (table and collection view updates) because the index paths of a table or collection view are also zero-based and composed of integers.
However, it doesn't reflect the reality of Swift's collection types. For example, ArraySlice uses integer indices, but they aren't zero-based. If you compute the changeset for two ArraySlice instances, the result is arguably wrong or at least confusing:
let source = [2,3,4,5].dropFirst() // ArraySlice<Int>
let target = [3,4,5,6].dropFirst() // ArraySlice<Int>
let edits = Changeset.edits(from: source, to: target)
print(edits)
// Prints "[delete 3 at index 0, insert 6 at index 2]"

If you tried to apply this changeset literally to the source collection (i.e. delete the element at index 0 from source), youʼd get a crash because source doesnʼt have an "index" 0.
In a way, a similar issue is when you compute changesets for strings (as most of the unit tests do) because string indices are not integers, so saying something like "insert "a" at index 5" doesn't strictly make sense in Swift.
I find this a little confusing and misleading. Changeset appears to be generic for any collection, and yet it doesn't follow Swift's conventions where the term "index" has a very specific meaning.
When I first noticed this "problem" I wanted to suggest replacing the integer indices in Edit and EditOperation with the collection's index type (i.e. something like T.Index). On second thought, this doesn't make sense because a changeset would have to compute "virtual" indices for a collection that doesn't really exist, and since collections are free to invalidate any existing index upon mutation, I don't think you could compute the indices in a generic way. Moreover, using real collection indices would make supporting table/collection view updates harder, not easier.
After writing all this, I realize that the way this works is actually the best solution for the given problem. Having written this, I'm going to submit it too, even though I don't have a specific suggestion. Feel free to close this issue, and maybe it will help others understand this better when they find it in search.
My only suggestion would be to make it clear that Changeset and Edit aren't concerned with indices, but with offsets. I think if the debugDescription read "delete x at offset 0" etc. I would have been less confused. This is exemplified by the use of enumerated() to compute the column value in edits(from:to:), since enumerated() computes offsets from 0 and not indices (see http://khanlou.com/2017/03/you-probably-don't-want-enumerated/ for more info on enumerated() and how it's often misinterpreted).

Thanks for your comments, @ole. You make a very valid point and, as always, in a well-articulated way.

[The] Edit steps are currently always integers and always zero-based (i.e. the first index is 0). This works great for the intended main use case (table and collection view updates) because the index paths of a table or collection view are also zero-based and composed of integers.

I have toyed with the idea of supporting a generic index type (the collection’s). This would make it easy to apply table/collection view data source changes spanning multiple sections, for example, using IndexPath.
(Now, more than a year later, I still feel like a newbie when it comes to Swift and haven’t yet taken the time to fully understand the problem and possible solutions.)
Your suggestion to use the term offset where applicable is just excellent. I will do that and clarify the issue in the README.
Thanks.

I think even if you wanted to use the collection's generic index type, it's not going to work. Take strings as an example — or String.CharacterView, to be exact, because String doesn't conform to Collection in Swift 3 (but that will likely change again in Swift 4). When I talk about string indices in the following, I mean String.CharacterView.Index, which is typealiased to String.Index.
Say we want to compute:
Changeset.edits(from: "ABC".characters, to: "😜BD".characters)

The result should clearly be:
[replace with 😜 at offset 0, replace with D at offset 2]

(I'm using "offset" here for what the library currently calls "index".)
If we wanted to refactor the library to use the collection's index type rather than integer offsets, we run into a problem. Here's the transformation matrix:

0: "😜"
2: "B"
3: "D"

0: "A"

1: "B"

2: "C"

The number before each character indicates the character's string index value. Notice that the index value of "B" in the target row is 2 and not 1, as one would perhaps expect. String indices are opaque values, but internally they currently use a UTF-16 offset to indicate the character's position in the string's storage. Since the emoji character takes up two UTF-16 units, all following characters have their index value incremented. The index with the value 1 doesn't exist in the target string. (Note that the offset of "B" from the start of the target string is still 1; that's why it's important to distinguish between index and offset.)
Now see what happens if we apply the first substitution (replace the "A" at index 0 with "😜"): Making this change invalidates the indices of all subsequent characters in the string. That is, if we have earlier obtained an index for the "C" character in the source string, it would no longer be valid after performing the first substitution (the same index now points to the "B" character; depending on the change, it may also have become entirely invalid and cause a crash if you tried to subscript the mutated with it).
It's probably possible (if difficult) to apply the current algorithm to strings using the string index type because the algorithm goes through the collections from left to right (top to bottom) and never has to consider values to the right (bottom) of the current element, but the Collection protocol makes no such guarantees. Collections are free to invalidate any existing index upon mutation. Therefore, I'm not sure it's even possible to write a generic version of the algorithm that uses the collection's index type. And even if it's possible, it may not be a good idea.

Closed by #39.


Fallback to arena allocator if RMM failed to initialize with async allocator

This adds an additional attempt layer into the initializeRmm() method, allowing RMM to fallback to initialize with arena
allocator if it could not be initialized with async allocator. This allows smooth RMM initialization (through fallback) instead of throwing an exception.
Closes https://github.com/NVIDIA/spark-rapids/issues/7649.

build

This will be kept in draft mode until being tested with vGPU.

build

build

LGTM

build

build


Cannot install eta 0.8.0b1 via etlas

When trying to install the latest version of eta i get the following error:
$ etlas select latest
Downloading executable 'eta'...
Downloading executable 'eta-pkg'...
Downloading executable 'eta-serv.jar'...
Selected eta-0.8.0b1.
etlas: The program 'eta' is required but the version of
/home/jonathan/.etlas/binaries/cdnverify.eta-lang.org/eta-<IP_ADDRESS>/binaries/x86_64-linux/eta
could not be determined.

Running the binary home/jonathan/.etlas/binaries/cdnverify.eta-lang.org/eta-<IP_ADDRESS>/binaries/x86_64-linux/eta produces:
$ home/jonathan/.etlas/binaries/cdnverify.eta-lang.org/eta-<IP_ADDRESS>/binaries/x86_64-linux/eta
/home/jonathan/.etlas/binaries/cdnverify.eta-lang.org/eta-<IP_ADDRESS>/binaries/x86_64-linux/eta: /lib64/libtinfo.so.5: no version information available (required by /home/jonathan/.etlas/binaries/cdnverify.eta-lang.org/eta-<IP_ADDRESS>/binaries/x86_64-linux/eta)
eta: can't find a package database at /home/jonathan/.eta/<IP_ADDRESS>/package.conf.d

This issue has been fixed in master, so you can either clone and build the repo, or wait for a revision which I guess will soon be released by typelead.

@Supernerd11 We just deployed the linux binary for 0.8.0b2 which should work. Run these:
etlas update
etlas select latest


Take uptime to consideration for znode reward

Hi guys,
I got a better understanding thanks to @oti-dev on #174
So uptime so far is just used as an entry requirement for shortlist
Could we consider uptime as another factor for the sorting algorithm inside the shortlist? E.g: the longer uptime a znode is, the higher rank it becomes?
Thanks.

So you want to shortlist the shortlist? E.g. if uptime > uptime of 50% of shortlist, they should end up in the shortlisted shortlist and be more likely to be selected?
Why do you want earlier nodes to benefit? I feel they are already benefiting/have already benefited from the fact that they have been set up at a time when fewer nodes existed. For example the first few payouts in late December/early January happened on very short time frames (like 5 days) which will probably never be possible again. People there got paid twice more than once if you know what I mean.
If you're referring to the fact that it's actually possible to move along nicely with the queue without being online consistently, that's a valid concern. However I feel it's very theoretical in nature. Who would benefit from taking a few days off after each payout? Why would you put in the effort to bring your node up and down on a schedule like that if there is no benefit? Or can I just not think of one?

so if a longevity node get pay it will be back to the end of qualified queue, i think our qualified queue (sort with last paid block) eliminates double pay quite well
e.g. assume 1500 qualified nodes are static, we will have 150 nodes in shortlist, given node X get pay this round, i believe X will wait for 1350 blocks to get back in shortlist
problem with current lotto algo in shortlist is that it doesn't guarantee (? pls correct me if im wrong) that a node will get pay :neckbeard:
specifically is this algo here https://github.com/zcoinofficial/zcoin/blob/master/src/znode.cpp#L144
uptime is just my suggestion as a proof of service, can definitely use something else as long as it could determine a payment timeframe for nodes fairly 💵

This would make it more punishing if your node went down. It would make it harder for people who run their own nodes to be competitive and probably push people who dont need providers to providers. Also, it would further incentivize top nodes to be ddos'd since you are creating an even smaller pool to pick from.
I am against this. The algorithm is working fine now. Everyone has got paid out eventually. People who dont get paid out because of their own user errors the majority of time. This will get even worse if we add uptime as a parameter.

agree on ddos attack, it could the reason of doing random picking for winner in shortlist, but i wonder how sure are we when say "eventually" there? Might put it this way: how long would it take (relatively) for a node in shortlist to get pay?
uptime is just my suggestion as a proof of service, can definitely use something else as long as it could determine a payment timeframe for nodes fairly

We already have an estimate. Its The node amount / 144 block on avg. Which is around 18 days now. The majority of time people dont get paid at this time is because they made their own mistakes by either restarting the node or breaking it some way.

i was relying on that calculation actually 😆 just to realize it's not that correct, when i say relatively before i mean something like 1500 ± n (blocks)
for me, estimation of qualified nodes / 144 will fall to gambler's fallacy (because chance of particular node in shortlist to win a block reward doesn't change over time)


Style Icon and Icon.Button via styles object

Hi,
I think it will be easier to style Icon via styles-object,
Currently
<Icon name="rocket" size={30} color="#900" />
Proposed Change
<Icon style={{name="rocket",size="30", color="#900"}} />
Advantage
<Icon style={[defaultStyle, this.props.customStyle]} />
This will help incase we want to change the default style via props, like we are able to do with other React Components.
Similarly we can do for <Icon.Button />
If you feel this can be helpful for others too, then I can work on the PR.
Regards.

You can use {color: '#900', fontSize: 30} as referenced in the documentation, but name is a prop (it's not styling IMHO).

i guess it is up to users preferences.  i prefer the way it works right now, whereby you are putting in the important props like name.  however, you can do style={styles.whateverIcon} and define the font and other styles there.
either way is pretty cool though.

@281330: Yeah, the user can choose whichever style they prefer. Closing this.


Bookmark "Symmetric cell pairs" the table can't be loaded

Did you push these changes? Because for me it still throws an error:

Should be fixed. Please try again tomorrow.

Fixed, thanks!


New version: PCSX2Team.PCSX2 version v2.2.0

Pull request has been created with komac v2.8.0 :rocket:
Microsoft Reviewers: Open in CodeFlow

@microsoft-github-policy-service agree


upterm bin not found

Describe the bug
somehow upterm not found.
➜  ~ ls -lha /nix/store/ | grep dr- | grep upterm
dr-xr-xr-x    4 root root    4,0K Jan  1 1970 238xps8q5caipvzh93fb6y9lgyw8gcaz-upterm-0.9.0
dr-xr-xr-x    2 root root    4,0K Jan  1 1970 g7yrb4rhcwr0vrc16c6xm5j7vvj9phkd-unit-uptermd.service
dr-xr-xr-x    3 root root    4,0K Jan  1 1970 pa8k4fbfngvn1jifvvgk6wns9ijnhshv-unit-script-uptermd-pre-start
➜  ~ ls -lha /var/run/current-system/sw/bin/ | grep upterm
➜  ~ ls -lha /nix/store/238xps8q5caipvzh93fb6y9lgyw8gcaz-upterm-0.9.0/bin/
total 28M
dr-xr-xr-x 2 root root 4,0K Jan  1 1970 .
dr-xr-xr-x 4 root root 4,0K Jan  1 1970 ..
-r-xr-xr-x 2 root root  15M Jan  1 1970 upterm
-r-xr-xr-x 2 root root  14M Jan  1 1970 uptermd
➜  ~ upterm
fish: Unknown command: upterm

Steps To Reproduce
Steps to reproduce the behavior:

enable uptermd services

  services = {
    uptermd = {
      enable = true;
    };
  };

rebuild system and run upterm

➜  ~ upterm
fish: Unknown command: upterm

Expected behavior
upterm can work properly.
Screenshots

Additional context
none.
Notify maintainers
@hax404
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
➜  ~ nix-shell -p nix-info --run 'nix-info -m'
this path will be fetched (0.01 MiB download, 0.04 MiB unpacked):
  /nix/store/0jmdsgfnd6aakxdr0sl5l7zzfs59hdrw-stdenv-linux
copying path '/nix/store/0jmdsgfnd6aakxdr0sl5l7zzfs59hdrw-stdenv-linux' from 'https://cache.nixos.org'...
 - system: `"x86_64-linux"`
 - host os: `Linux 6.3.1, NixOS, 22.11 (Raccoon), 22.11.4147.9656e85a15a`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.11.1`
 - channels(hervyqa): `""`
 - channels(root): `"nixos-22.11"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Does it help if you add upterm to your systemPackages? i.e.
{ pkgs, ... }:

{
  environment.systemPackages = with pkgs; [ upterm ];
}

I am guessing that services.uptermd.enable enables the uptermd server locally, which might not be what you intended to do.

Does it help if you add upterm to your systemPackages? i.e.

yes, it works
➜  ~ upterm
Upterm is an open-source solution for sharing terminal sessions instantly with the public internet over secure tunnels.

Usage:
  upterm [command]

Examples:
  # Host a terminal session that runs $SHELL with
  # client's input/output attaching to the host's
  $ upterm host

I think by just enable the service, the package will be automatically downloaded. such as mysql, jupyter, colord, fstrim, and other packages that can be used immediately by enabling the service.

I think the confusion here is the distinction between upterm and uptermd. upterm seems to be a client program that you use to share your terminal, whereas uptermd is a server program that is used by servers like uptermd.upterm.dev and connected to by the upterm client.
The upterm program doesn't seem to need any special environment, so it probably does not need a NixOS module, and it is sufficient to just add the upterm derivation to your systemPackages.

Thanks for the explanation, now i understand. I think i will delete the uptermd service section.


Remove arguments for shade_dark and legend in plots

Many plots have an argument to shade the dark periods (shade_dark) and for adding a legend (legend).  While intended to be convenient, these can actually be somewhat annoying to work with.
For the legend, you are unable to exert the same control in placement you have when simply calling plt.legend() or ax.legend().   There can be problems where the initial plot call places the legend in a bad place, in which case you have to move to using matplotlib anyway.
For shading the dark periods, calls to multiple plotting functions will cause the darkness to be shaded multiple times, unless the user explicitly specifies shade_dark=False.  This is demonstrated in one of the plots in this section of the documentation (left & right pokes on the same plot).   Instead, it might be nice to just have a function which gets the current axis and draws the shading on it (e.g., fed3.plot.shade_dark()).   I believe this would be possible?

The arguments are still there, but there is now an option for toggling their default behavior (either include or exclude).
To do so, see fed3.plot.OPTIONS, a dictionary.  It is currently initialized as
OPTIONS = {'default_shadedark': True,
           'default_legend': True}

So to turn off plotting the legend by default, call fed3.plot.OPTIONS['default_legend'] = False.
Also, fed3.plot.shadedark.shade_darkness() should be able to be called to shade the dark periods on a non-shaded plot, either 'datetime' or 'time' alignment.


Cache not being used when loading commonvoice 8.0.0

Describe the bug
I have commonvoice 8.0.0 downloaded in ~/.cache/huggingface/datasets/mozilla-foundation___common_voice_8_0/en/8.0.0/b2f8b72f8f30b2e98c41ccf855954d9e35a5fa498c43332df198534ff9797a4a.  The folder contains all the arrow files etc, and was used as the cached version last time I touched the ec2 instance I'm working on.  Now, with the same command that downloaded it initially:
dataset = load_dataset("mozilla-foundation/common_voice_8_0", "en", use_auth_token="<mytoken>")

it tries to redownload the dataset to ~/.cache/huggingface/datasets/mozilla-foundation___common_voice_8_0/en/8.0.0/05bdc7940b0a336ceeaeef13470c89522c29a8e4494cbeece64fb472a87acb32
Steps to reproduce the bug
Steps to reproduce the behavior:

dataset = load_dataset("mozilla-foundation/common_voice_8_0", "en", use_auth_token="<mytoken>")
dataset is updated by maintainers
dataset = load_dataset("mozilla-foundation/common_voice_8_0", "en", use_auth_token="<mytoken>")

Expected behavior
I expect that it uses the already downloaded data in ~/.cache/huggingface/datasets/mozilla-foundation___common_voice_8_0/en/8.0.0/b2f8b72f8f30b2e98c41ccf855954d9e35a5fa498c43332df198534ff9797a4a.
Not sure what's happening in 2. but if, say it's an issue with the dataset referenced by "mozilla-foundation/common_voice_8_0" being modified by the maintainers, how would I force datasets to point to the original version I downloaded?
EDIT:  It was indeed that the maintainers had updated the dataset (v 8.0.0).  However I still cant load the dataset from disk instead of redownloading, with for example:
load_dataset(".cache/huggingface/datasets/downloads/extracted/<hash>/cv-corpus-8.0-2022-01-19/en/", "en")

> ...
> File [~/miniconda3/envs/aa_torch2/lib/python3.10/site-packages/datasets/table.py:1938](.../ python3.10/site-packages/datasets/table.py:1938), in cast_array_to_feature(array, feature, allow_number_to_str)
   1937 elif not isinstance(feature, (Sequence, dict, list, tuple)):
-> 1938     return array_cast(array, feature(), allow_number_to_str=allow_number_to_str)
...
   1794         e = e.__context__
-> 1795     raise DatasetGenerationError("An error occurred while generating the dataset") from e
   1797 yield job_id, True, (total_num_examples, total_num_bytes, writer._features, num_shards, shard_lengths)

DatasetGenerationError: An error occurred while generating the dataset

Environment info
datasets==2.7.0
python==3.10.8
OS:  AWS Linux

You can avoid this by using the revision parameter in load_dataset to always force downloading a specific commit (if not specified it defaults to HEAD, hence the redownload).

Thanks @mariosasko this works well, looks like I should have read the documentation a bit more carefully.
It is still a bit confusing which hash I should provide:  passing revision = c8fd66e85f086e3abb11eeee55b1737a3d1e8487 from https://huggingface.co/datasets/mozilla-foundation/common_voice_8_0/commits/main caused the cached version at ~/.cache/huggingface/datasets/mozilla-foundation___common_voice_8_0/en/8.0.0/b2f8b72f8f30b2e98c41ccf855954d9e35a5fa498c43332df198534ff9797a4a to be loaded, so I had to know that it was the previous commit unless I've missed something else.


Weaviate support

pom.xml of new weaviate module doesn't contain license-maven-plugin,  coz I have no idea how to use it for the moment
I've used prettier as code formatter, I suggest to use it globally. Small config for just max line length is added.

pom.xml of new weaviate module doesn't contain license-maven-plugin,  coz I have no idea how to use it for the moment

@Shastick weaviate library has a BSD3-Clause license, I guess we will need to include license plugin exclusion for it, right? BTW it seems that this license plugin has ignored this BSD3 license during the run.

I've used prettier as code formatter, I suggest to use it globally. Small config for just max line length is added.

Good idea! Is it possible to use it for free? In Intellij IDEA plugins it is available only for ultimate edition it seems...

Good idea! Is it possible to use it for free? In Intellij IDEA plugins it is available only for ultimate edition it seems...
In fact I have ultimate IntelliJ, I cannot try, but I haven't heart that's ultimate is really required...


feat(errors): rethrow errors that are nested in an object

In InstantSearch and the helper we use .emit('error', { error: new Error() }) in some cases. This can be fixed in events, or in the helper/instantsearch. As those two optoins are open and changing inside instantsearch could be a breakign change

We've changed InstantSearch to not need this anymore


Add Goblin diplomacy

Partially worked on, Need to populate RetrieveGoblinMailLeaf, retrieve woad leaves, pay witch in draynor to make the dyes, dye the goblin mail before talking to goblin generals

Goblin diplomacy has been added.


Manage websocket disconnection on the frontend

We can also add a loader to the chat window while the socket connection is being established


Change GitHub Actions cache key to invalidate cache

Even if it seems unlikely, it really appears that we're getting :x: failed checks on master and PRs due to a corrupted cache.  The same PR works on my fork when the cache is enabled, and disabling the cache works on this repo.
AFAICT, there isn't any way to clear the cache, but we can either (1) turn it off for a week, since all the cached packages are dropped after seven days, or (2) directly call actions/cache with a new cache id to create a new cache.  This PR implements the second option.
You can't specify the cache id using actions/setup-java unfortunately.
Either way, we can revert this commit in 7 days and restore the "normal" cache mode integrated with setup-java.

How is the cache breaking the build? (I didn't look it up, just want to understand what this is fixing).
I think the commits can be squashed.
What changes in 7 days? Is the issue the dependencies updated via dependeabot?

@RyanSkraba ping

Hello!  My apologies, your comment got drowned in other notifications.
I have never encountered a corrupt package cache before, but many signs point to this being the problem.  When the cache on mac is untarred during the setup-java action, a checksum error occurs and the workflow fails.  There is no workaround to invalidate package caches.
The same project on my fork (without an existing cache) works, as does manually setting the cache id to a different value (which is not possible when using the actions/setup-java@v2 action, but can be done by using the actions/cache explicitly).
Any package cache not used after 7 days is dropped, which is why once any fix (no longer accessing the corrupt cache) can be reverted after this period.
My new proposal is to try rebasing one of the dependabot PRs tomorrow and see if :point_up: the 7 days worked!

Looks like waiting long enough made the problem go away :partying_face:


Feature Request: A button to sort equipment alphabetically within eq. categories.

Some sort of "sort alphabetically within categories" button in the Equipment tab on the player sheet would really help those less organised/more hoardy players.
One of my players simply LOVES consumables and it has gotten to a stage when it's hard to find anything.
Of course, those consumables are narratively kept in a Bag of Cheating... I mean Holding, but Foundry-wise they're in the general inventory.

Additionally, all columns sortable would be great. Sort by bulk, by equipped status, etc.

I asked in the Pf2e discord something like this. Personally, I´d love it if we could sort them by level.
Additionally, if the level was shown in the inventory window right away would be amazing. Getting inside each object´s details to see it is very tiresome. Thanks!

The same applies for loot/merchant sheets. It's hard for players to find items if there are a lot of them and the items aren't sorted.

Duplicate of #1152


Added MUI Progress bar to calculator pages

On mobile for the second stage of the stepper it is missing the lines between the stepper sections. Desktop is looks good the whole way through.

Ah sorry, should've specified this PR is for desktop view only. Was gonna do another PR for mobile

Ok, it looks good then!