Print cash report when a user closes out their till

When a user closes out their till, a copy of the report displayed on that screen should be printed so they can include it with their cash box. (It displays totals by payment type, etc - see org.kumoricon.site.utility.closeouttill.*)
Currently, that report is only displayed on screen, but it should be printed auomatically. In general, I would expect printing the report to work about like printing badges does - generate a PDF, then send the PDF to the appropriate printer.
Unresolved questions:

Print where? Options:

Print it to the badge printer defined for that computer and waste a badge (not a major concern besides looking ugly) If option 1, format the report for 8.5" x 5.5" paper.
Have a network printer set up somewhere (manager station? with regular paper?) where all the reports would be printed. Users would have to get up and walk to that printer, but they'll be getting up anyway. (You would only expect someone to close out their till and print the report when they're leaving their station at the end of their shift)

Would need to add a reprint button just in case (always allow for printers to be evil)

Printing should be automatic when you close out the till.

Like printing badges, this should respect the kumoreg.printing.enablePrintingFromServer setting in application.properties

Thinking through it, I like printing to the printer at each station. It saves a printer, and I think it would be easier for people to remember to grab the report if it prints right next to them.


[BUG]Clients of Azure File Share Client Library can not operate some exmples on README.md

Describe the bug
When using clients created by SASToken to complete some examples mentioned on README.md, there is an exception.
However, when using clients created by connection string to complete the examples, there are no exceptions.
Links for the examples are given below:
https://github.com/Azure/azure-sdk-for-java/tree/master/sdk/storage/azure-storage-file-share#copy-a-file
https://github.com/Azure/azure-sdk-for-java/tree/master/sdk/storage/azure-storage-file-share#get-a-share-access-policy
https://github.com/Azure/azure-sdk-for-java/tree/master/sdk/storage/azure-storage-file-share#set-a-share-access-policy
Exception or Stack Trace
Exception of "copy a file":
Exception in thread "main" com.azure.storage.file.share.models.ShareStorageException: Status code 404, "CannotVerifyCopySourceThe specified resource does not exist.
RequestId:b7433745-901a-000a-6292-14f742000000
Exception of "get a share access policy" and "set a share access policy":
Exception in thread "main" com.azure.storage.file.share.models.ShareStorageException: Status code 403, "AuthorizationFailureThis request is not authorized to perform this operation.
RequestId:1d9dcb7a-d01a-0056-5692-14a21a000000
Expected behavior
There are no exceptions with both clients.
Setup (please complete the following information):

OS: [e.g. iOS]
Windows
IDE : [e.g. IntelliJ]
VSCode
Version of the Library used
azure-storage-file-share
12.5.0-beta.1.dev.20200415.1
JDK 1.8

Additional context
Add any other context about the problem here.
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[ ] Bug Description Added
[ ] Repro Steps Added
[ ] Setup information Added

/cc @sima-zhu

@rickle-msft How is this issue going?

We have not yet begun working on this, but it is still in our backlog

@rickle-msft These 3 samples mentioned above shows two kinds of operations: copy file and get/set AccessPolicy. For clients created with SASToken, copy file should work, get/set AccessPolicy should not work as SASToken can't be used for such purpose.
1. Copy a file
While copy file with SASToken, the SASToken should be appended to the source file url.

Copy file would fail.

Copy file would successful.
Suggestion: In method beginCopy, if the client created with sastoken, append the sastoken to source URL.
2.  get/set AccessPolicy
SAStoken can’t be used to update access policy. It is better to have some description about this in readme, sample, and the sdk code comments.
Suggestion: Add  description  about this in readme, sample, and the sdk code comments.
Readme:

Sample:

code comments:

Now the operation copy file problem were fixed. And we push pr https://github.com/Azure/azure-sdk-for-java/pull/18470 to fix the operation  get/set AccessPolicy problem.

Now the operation copy file problem were fixed. And we push pr https://github.com/Azure/azure-sdk-for-java/pull/18470 to fix the operation  get/set AccessPolicy problem.

Closing as PR has been merged


AddDbUtils

Coverage decreased (-1.7%) to 98.276% when pulling d82f3d67744b0a63d0e22c3007558da3ecc0a3cf on addDbUtils into 37e95a3962831234694a30abd4150f49b6024eea on master.

Coverage remained the same at 100.0% when pulling ecef53e06c8681cdd37ece6b6f3030b4e48f756d on addDbUtils into 37e95a3962831234694a30abd4150f49b6024eea on master.


fixing classification report

This PR fixes the classification_report.py script in order to run as expected.
To QA:
Run python3 deep_audio_features/bin/classification_report.py -m <model> -i <folder1> <folder2>
The testing folders must have the same basename as the ones that the model was trained on, but no need to have the same order.

Results see ok for the 1-sec musical genre dataset:
Confusion matrix:
 [[160   5  20   7  43   7  48   3  31]
 [  2 281   3   2   0   0   8   0   1]
 [ 27  10 168   0  13   1  15  26  22]
 [  4   5  11 173  66  16   9  37   3]
 [ 35   1  16  31  97  20  31  36  22]
 [  9   0   4  15  14 281   5  24   4]
 [ 66  12   4   5  27   7 135  20  11]
 [ 10  10  42  35  21  47  10  88  37]
 [ 40   6  42  15  24  11  11  21 235]]
Classification report:
                     precision    recall  f1-score   support

                          0.45      0.49      0.47       324
          classical       0.85      0.95      0.90       297
            country       0.54      0.60      0.57       282
   electronic_dance       0.61      0.53      0.57       324
      funk_rnb_soul       0.32      0.34      0.33       289
             hiphop       0.72      0.79      0.75       356
               jazz       0.50      0.47      0.48       287
                pop       0.35      0.29      0.32       300
rock_metal_hardrock       0.64      0.58      0.61       405

           accuracy                           0.56      2864
          macro avg       0.55      0.56      0.56      2864
       weighted avg       0.56      0.56      0.56      2864


Whatsapp call support

May you can make it possible to call? Maybe this is not possible because it's the web version, but maybe you can add some like css or html to make it possible to call with someone. (Sorry if i post many suggestions, i always like to give suggestions.)

Currently this app only supports what's possible in the web app, not the desktop app. Once calls are supported in the web app, they should work out of the box here.

Yes, i understand that.


Shape Component

Add a shape component that when attached to an entity (or child entity) using a body with shape: none updates the shapes on the CANNON.Body. This enables an easy way to define a body made of multiple primitive shapes, which should be a performant alternative to using convex hulls.
The updating of the body is delayed until tick so that if multiple shape components are defined, the body is only updated once. Does not currently support removing of shapes.
Also updated the wireframe code in body to handle shape offsets and orientations correctly, as well as multiple shapes per body.

+1 for this idea
I frequently need a shape different from what three2cannon will produce (e.g. a box that doesn't expand to include child entities or a box that is just a little thicker than the plane geometry it encloses for easier grabbing), and the current process involves writing a custom component each time to listen for the body loaded event and create the shapes

Nice work, thanks! Will test this out a bit and then cut a new release.

Published 3.1.0. 🎊

It looks like compound colliders break when an orientation property is specified (3.3.0) for any component shape; an alternative is using the constraint functionality to create a complex physics body (rotation seems to work fine for primitive body shapes) but I'm worried about overhead with this methodology. Looking into using wmurphyrd's aframe-physics-extras for this


PublishModulesAndMofsToPullServer.psm1: Fixes style inconsistencies

Pull Request (PR) description
Fixes style inconsistencies in PublishModulesAndMofsToPullServer.psm1.
This Pull Request (PR) fixes the following issues

Fixes #530

Task list

[x] Added an entry under the Unreleased section of the change log in
CHANGELOG.md. Entry should say what was changed, and how that affects
users (if applicable).
[ ] Resource documentation added/updated in README.md.
[ ] Resource parameter descriptions added/updated in README.md, schema.mof
and comment-based help.
[ ] Comment-based help added/updated.
[ ] Localization strings added/updated in all localization files as
appropriate.
[ ] Examples appropriately added/updated.
[ ] Unit tests added/updated. See
DSC Resource Testing Guidelines.
[ ] Integration tests added/updated (where possible). See
DSC Resource Testing Guidelines.
[x] New/changed code adheres to
DSC Resource Style Guidelines and Best Practices

This change is

Codecov Report

Merging #604 into dev will not change coverage.
The diff coverage is n/a.

@@         Coverage Diff         @@
##            dev   #604   +/-   ##
===================================
  Coverage    74%    74%
===================================
  Files        27     27
  Lines      4078   4078
  Branches      4      4
===================================
  Hits       3038   3038
  Misses     1036   1036
  Partials      4      4

Awesome work @mhendric ... Real tedious job to clean up all the discrepancy


Remote logging to S3 bucket did not succeed

Checks

[X] I have checked for existing issues.
[X] This report is about the User-Community Airflow Helm Chart.

Chart Version
8.7.0
Kubernetes Version
Client Version: version.Info{Major:"1", Minor:"27", GitVersion:"v1.27.0", GitCommit:"1b4df30b3cdfeaba6024e81e559a6cd09a089d65", GitTreeState:"clean", BuildDate:"2023-04-11T17:04:23Z", GoVersion:"go1.20.3", Compiler:"gc", Platform:"darwin/arm64"}
Kustomize Version: v5.0.1
Server Version: version.Info{Major:"1", Minor:"25+", GitVersion:"v1.25.8-eks-ec5523e", GitCommit:"83fe90de881ffe7450876d204ccdc37a0f95bda3", GitTreeState:"clean", BuildDate:"2023-03-20T21:32:06Z", GoVersion:"go1.19.7", Compiler:"gc", Platform:"linux/amd64"}

Helm Version
version.BuildInfo{Version:"v3.11.1", GitCommit:"293b50c65d4d56187cd4e2f390f0ada46b4c4737", GitTreeState:"clean", GoVersion:"go1.18.10"}

Description
I've decided to use S3 bucket among Remote Providers to Manage Airflow Logs as described in this link.
As described in below Custom Helm Values file, I have set necessary configurations such as airflow.config, airflow.connections, and serviceAccount.annotations. I've also confirmed that my IAM role linked to the Service Account has necessary permissions to write to the above-mentioned S3 bucket.
I've run canary_dag in the example in the bottom of this link, and it ran successfully.
I expect that the logs produced by this DAG are sent (remotely) to the S3 bucket that I've designated. However, when I go into my AWS account and check the bucket, nothing was written down.
What may be the problem? Or at least, where can I find necessary log messages related to the failure of sending the log remotely to the S3 bucket? I.e., among the pods that are deployed via User-Community Airflow Helm Chart, which pod (and which container) is responsible for this remote logging?
Relevant Logs
No response
Custom Helm Values
airflow:
  config:
    AIRFLOW__LOGGING__REMOTE_LOGGING: "True"
    AIRFLOW__LOGGING__REMOTE_BASE_LOG_FOLDER: "s3://<REDACTED>/logs"
    AIRFLOW__LOGGING__REMOTE_LOG_CONN_ID: "aws-conn-id"
  connections:
    - id: aws-conn-id
      type: aws
      description: AWS connection used for remote log writing to a S3 bucket
      extra: |
        {
          "region_name": "ap-northeast-2"
        }

serviceAccount:
  annotations:
    eks.amazonaws.com/role-arn: "arn:aws:iam::<REDACTED>:role/<REDACTED>"

Anyone have any ideas?


Reaction messages

Summary
Store message_id on ReactionEvents to allow for message matching. Also add support for from and in matching.

Added

from, in, and message matchers for ReactionAddEvent and ReactionRemoveEvent
message and in matchers for ReactionRemoveAllEvent
message_id instance variable on ReactionEvent

This was merged via shardlab/discordrb@a0499dae3ded50fce605e51274fbac28c5272090 in the new repo and released in v3.4.0 and can be closed.


Background gradient is not set on the main Bootstrap website

https://getbootstrap.com/docs/4.1/utilities/colors/#background-gradient

As mentioned in the documentation:

By default, $enable-gradients is disabled and the example below is intentionally broken.


cannot change .time property (typo?)

my usecase: I set a default value for 'time' but before starting the timer I want to change it (the value to use comes from an API)
however, due to a typo in mixin.js it will always use the default value.
my code:
    timers: {
      settings: {
        callback: ...,
        autostart: false,
        repeat: true,
        immediate: false,
        time: 60*1000,
      }
    },

then, in the component's created() I do something like:
            this.timers.settings.time = 5 * 1000;
            this.$timer.start('settings');

(instead of 5 I'm using a dynamic value)
as I see, the problem comes from a typo in mixin.js, line #97:
        data[name].instance = generateTimer(
          set('timer', data[name].time, options[name]),
          vm
        )

if I change it to
set('time', data[name].time, options[name]),

it works as expected.

Fixed in 1.7.2. Sorry for delay


Bitcoin gold support

Not a bug, but an improvement.
With the new fork of bitcoin on the way (Bitcoin Gold, the 25 of October), will it be possible to support the coin in this wallet?

@juanrodgil  I think they should fork and customize for their wallets. For example, they could fork electrum and create Electrum_Gold or something.

@juanrodgil   No, sorry.

@fyookball are you aware this page https://www.electrongold.org/ is sending to this repository? It seems like a scam.


Lexical match metadata

Currently we include preprocessing and match fields for lexical matches, but there are other things to consider like:

edit distance (threshold based, like semantic similarity, some kind of lexical_similarity_score. Maybe generalise the semantic similarity score we already have to `similarity_score?

The problem is that mapping tool are often made of a bunch of components and very often include a "lexical matcher" and "a semantic similarity measure" too. The score obtained by each of these "components" are only significant if normalized and in the case the tool is only made of one component. => I mean if the score of the component does actually represent the score of the mapping.
I would in fact propose two properties  "mapping_score" and "mapping_normalized_score"  that would typically be the score (aggregated by the mapping tool) and also normalized [0-100]. If not normalized, these score are hardly re-usable in multiple mappings contexts.

What you are saying makes total sense, but do you really believe that recording an unnormalised score is useful at all? My feeling was to assume all scores to be normalised..

I sort of agree with this too...

I will close this issue as not actionable, concrete feature requests will be dealt with separately.


windows: connect ok, but all operations are no-ops

[Windows version on win10]
I've created and imported a new PK and FS seems to connect. (At least choosing the Firebase Console brings up the correct app.)
All query operations give no results, and inserts after "commit' do nothing; however, there are no errors generated of any kind. (Also an invalid table name, or invalid SQL will simply spin for a while and then produce nothing.)
thanks

Same, even when trying to select the entire database, there is nothing returned. There is data in the database. Specifying a specific database yields the same results.


Add a parm list of ulimits to set in the container.

@lazzurs  please take a look and share you feedback on possibility to add following feature.


i broke the colours and cant reset them

whats the default colours help me

https://github.com/dude719/ReClassEx/blob/7530109a33fa1f38e05f23614e1b212274e874bc/ReClass/stdafx.cpp#L22-L39


Move start calculation functionality into search batch page

Synopsis
As a user
I want to be able to start a batch from the batch overview page
So that I don't have to navigate between two pages
AC

[ ] A new batch can be created from a modal on the batch (calculations?) page
[ ] UX

@renehossle could you maybe paste the UX for this issue, I cant find it.


Add more handling for undefined vars

Also ensure tests are run with 'nounset' flag.
Resolves #17

I'm not sure why, but the set -o unset in run_tests isn't being enforced

Oh, It might be because run_tests kicks off a new shell for each test! I wonder if adding a setup to each test or modifying run_tests to set nounset in the shell would work. I also realized these options might different slightly between shells, it'd be good to look at different set options and ensure shpy runs under the most restrictive options
I'll check out the subshell angle and approve this if that doesn't pan out or update with that change

It appears that it (nounset) is supported:

dash<EMAIL_ADDRESS>zsh: https://linux.die.net/man/1/zshoptions

I also verified this by adding
set -u
echo ${no_such_var}

to the top of run_tests, and then running each of make test_bash, make test_dash, make test_sh, make test_zsh.  Each one failed with the same error

Also, each of the four shells supports a -u option when invoking it, so we can just remove the set -o nounset from the top of individual tests and add -u to the shell invocation.  I'll add that to this PR

There's a wrinkle.  Invoking a script via bash -u SCRIPT_NAME sets the -u flag, but bash -u -c "SCRIPT_NAME" does not.  Investigating

I wonder if we could add a test to verify the testing environment, something that references an undefined variable and expects itself to fail

We could change
  "$SHELL" -c "SHUNIT_PARENT=$test_file $test_runner $test_file" || exit $?

to
  SHUNIT_PARENT=$test_file "$SHELL" -u $test_file || exit $?

and to ensure kcov is used, we could put the original version in an if statement.
But that's getting too complicated, and I think it would be far simpler to just stick a set -u at the beginning of each test

It's also possible to use a here-doc to feed multi-line input to the shell's stdin, which might make it clean and easy to call set and retain $test_runner and $SHUNIT_PARENT

That's another approach that will work but I think it might make the runner (run_tests) too complicated and harder to maintain.

So I made some interesting discoveries poking at an unrelated hunch of mine:

The tests aren't all running under different shells, the shebang in each test is set to sh and the test runner is invoking them in such a way that the shebang is used
There are more places where nounset causes errors, which only became apparent once each test shell was running with it set

I've gotten a test in place which verifies nounset is set in the test environment, and which also fixes the shells used to run the test. I'd like to keep your undefined variable fixes and the cleanup tests, but I think the rest of your PR is covered by what I'll be putting up soon 🙏

OK sounds good!  Just to clarify, should I kill this PR?

I'd say leave it open and I'll add to it. I don't want you to lose your contributions!

I've had some other priorities come up recently but I'll be returning to this next weekend

Sounds good! I'll try getting my fixes up, it looks like there were some rather large mistakes I made with testing under different shells and getting coverage reports…


Adds support for importing wallets using private keys

Thanks for building this! I was looking to set up e2e tests locally that would interact with a node provisioned by hardhat, but realized I'd need to pass in a private key, rather than a mnemonic phrase, to connect a wallet. This PR adds support for this. The browser automation looks like this.
If you're interested in merging, happy to make further updates. Let me know.

@noahlitvin Thanks for good words, awesome work! I will take a look over weekend.

@noahlitvin sorry for keeping you waiting! should be finished by tomorrow.

@noahlitvin released as<EMAIL_ADDRESS>will be promoted as production release (0.9.26) later this week, cheers!

Amazing, thanks!


Update local connection monitor on local connection update

Description
Update local connection monitor on local connection update
Motivation and Context
If NSE has been changed during the healing, client does not receive an update for the opened local connection. It can lead to some problems if client behavior depends on connection parameters.
How Has This Been Tested?

[ ] Covered by existing integration testing
[x] Added integration testing to cover
[x] Tested locally
[ ] Have not tested

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

This PR is based on #1146 and so comes after.

@nickolaev
Are you talking about creating a new /test/application directory with common docker images and so that all new testing-only applications will be located there?
Or do you mean that examples directory is no more need in networkservicemesh/networkservicemesh as we have networkservicemesh/examples and so it should be completely transformed to /test/application directory?

@nickolaev
Here is #1160 to rename examples to test/applications and so I've moved new monitoring-nsc to this new directory : 5eed0f8

Ok, so we waiting for https://github.com/networkservicemesh/networkservicemesh/pull/1160 to be merged, before merging this one.


Compare Java SDK for compute TypeSpec migration

We are working on the compute TypeSpec migration.
Would like Java to verify the SDK generation of the corresponding swagger of the converted TypeSpec.
We have split compute into multiple sub services and done the conversion for each of them.
For instance, Compute sub-service:

https://github.com/Azure/azure-rest-api-specs/blob/feature/cplat-typespecTest/specification/compute/Compute.Management/readme.md is the readme containing input files of original swaggers.
https://github.com/Azure/azure-rest-api-specs/blob/feature/cplat-typespecTest/specification/compute/Compute.Management contains the converted TypeSpec, we need to compile them firstly to get the corresponding swgger then generate SDK
Get diff from the generated SDK from original swagger and new swagger

Current major issue is that some of the LIST operations are not generated with pageable, e.g.
https://github.com/XiaofeiCao/azure-rest-api-specs/blob/typespec_compute/specification/compute/resource-manager/Microsoft.Compute/ComputeRP/stable/2024-07-01/ComputeRP.json#L1582
Original swagger: https://github.com/XiaofeiCao/azure-rest-api-specs/blob/typespec_compute/specification/compute/resource-manager/Microsoft.Compute/ComputeRP/stable/2024-07-01/computeRPCommon.json#L171-L173
Majority compilation issues are caused by this.

Current major issue is that some of the LIST operations are not generated with pageable, e.g. https://github.com/XiaofeiCao/azure-rest-api-specs/blob/typespec_compute/specification/compute/resource-manager/Microsoft.Compute/ComputeRP/stable/2024-07-01/ComputeRP.json#L1582
Original swagger: https://github.com/XiaofeiCao/azure-rest-api-specs/blob/typespec_compute/specification/compute/resource-manager/Microsoft.Compute/ComputeRP/stable/2024-07-01/computeRPCommon.json#L171-L173
Majority of the compilation issues are caused by this.

Could you give me a complete list for this?

Compilation issues
1. LIST without pageable

VirtualMachineSizes_List
AvailabilitySets_ListAvailableSizes
DedicatedHosts_ListAvailableSizes
VirtualMachines_ListAvailableSizes

2. VirtualMachineScaleSetExtension without settable name property
Though there's PUT operation for VirtualMachineScaleSetExtension, we can still create one within VitualMachineScaleSet. Thus name property should be included as well.
(name property in common model ProxyResource is read-only and not settable)
current swagger: https://github.com/XiaofeiCao/azure-rest-api-specs/blob/a5f4c22d62eecd7f15f2434d0fca00dc3589b01d/specification/compute/resource-manager/Microsoft.Compute/ComputeRP/stable/2024-07-01/ComputeRP.json#L19009-L19027
original swagger: https://github.com/XiaofeiCao/azure-rest-api-specs/blob/typespec_compute/specification/compute/resource-manager/Microsoft.Compute/ComputeRP/stable/2024-07-01/virtualMachineScaleSet.json#L4479-L4481
(Current Java codegen still has issue even if it's added, could be azure-json issue. Though name should be there anyway.)
3. No AvailabilitySetSkuType model
This seems an orphan model, though Java still uses it in handwritten code. Not sure if other languages use it.
https://github.com/XiaofeiCao/azure-rest-api-specs/blob/typespec_compute/specification/compute/resource-manager/Microsoft.Compute/ComputeRP/stable/2024-07-01/availabilitySet.json#L490

@pshao25 I've compiled a list of current swagger issues that generate compilation issues.
I've yet to run tests and generate apiviews. Will update above list once those are done.

Compilation issues
1. LIST without pageable

VirtualMachineSizes_List
AvailabilitySets_ListAvailableSizes
DedicatedHosts_ListAvailableSizes
VirtualMachines_ListAvailableSizes

2. VirtualMachineScaleSetExtension without settable name property
Though there's PUT operation for VirtualMachineScaleSetExtension, we can still create one within VitualMachineScaleSet. Thus name property should be included as well. (name property in common model ProxyResource is read-only and not settable) current swagger: https://github.com/XiaofeiCao/azure-rest-api-specs/blob/a5f4c22d62eecd7f15f2434d0fca00dc3589b01d/specification/compute/resource-manager/Microsoft.Compute/ComputeRP/stable/2024-07-01/ComputeRP.json#L19009-L19027 original swagger: https://github.com/XiaofeiCao/azure-rest-api-specs/blob/typespec_compute/specification/compute/resource-manager/Microsoft.Compute/ComputeRP/stable/2024-07-01/virtualMachineScaleSet.json#L4479-L4481 (Current Java codegen still has issue even if it's added, could be azure-json issue. Though name should be there anyway.)
3. No AvailabilitySetSkuType model
This seems an orphan model, though Java still uses it in handwritten code. Not sure if other languages use it. https://github.com/XiaofeiCao/azure-rest-api-specs/blob/typespec_compute/specification/compute/resource-manager/Microsoft.Compute/ComputeRP/stable/2024-07-01/availabilitySet.json#L490

Hi @XiaofeiCao, we found the missing AvailabilitySetSkuType model in the TSP. Currently being fixed to enable it to generate corresponding JSON code after converting from TSP to Swagger, but it has now been renamed as AvailabilitySetSkuTypes, so I would like to ask which name you would like to keep?

Thanks @melina5656 . If possible, we still want it to be AvailabilitySetSkuType. Though we can always add @clientName in client.tsp.

Thanks @melina5656 . If possible, we still want it to be AvailabilitySetSkuType. Though we can always add @clientName in client.tsp.

@XiaofeiCao ,
Okay, I will solve this problem by adding @@clientName in the client.tsp file.


Future improvement: rdf:langString (lang tag) inlining

It could be possible to inline the language tag for some rdf:langStrings by sacrificing some bits in
the LiteralID to encode a fixed set of lang tags and using only the remaining bits to refer to the backend.
This only works for sufficiently small backend ids.

More details about a possible implementation now that I have though about it.
First create an enum CommonLanguageTags or similar.
On rdf:langString creation do roughly the following, if the language tag is a common language tag:

NodeStorage::find_or_make_id(LiteralView{lexical_form, lang_tag})
in the resulting NodeID check if the upper X bits of the LiteralID are unset

If yes, store the language tag (= the enum value) as in these X bits and set the inlining tagging bit
If no, you are done

On language tag fetching do the following:

if the inlining tagging bit is set look at the upper X bits and index a lookup table that translates the enum value into a string in static memory otherwise do the normal thing

This approach has two interesting properties

language tags are effectively stored twice (once in static memory and once in the backend, but that is probably fine and saves some branches elsewhere)
rdf:langString is a type that can be partially stored in the backend which is new for rdf4cpp

The remaining question is: How many bits should this use?

more bits means more different language tags can be inlined (i.e. the number of variants in CommonLanguageTags increases)
the threshhold where language tag inlining is possible decreases (i.e. more than 2^(42-X) literals means no more language tag inlining)


Disable smoke reactions

Lots of shitcode abuse and complaining so just dump the reactions for now.
:cl:

remove: Removed smoke reactions until someone makes a better system.

Commenting out/removing the following part will make you not puke your chemstream onto the floor anymore, preventing you from being able to mass produce medicine by puking and then mopping it up. It still pukes out stuff in the stomach so removing this part of code will probably also be a better representative of puking(you don't puke out stuff already absorbed into your blood after all). It does not prevent people from making healing smoke/foam, but it fixes at least one of the big issues without completely axing the mechanic.

https://github.com/space-wizards/space-station-14/pull/17697
I tweaked the vomit code a bit to prevent duplication through it


[Suggestion] crawling underwater and on air

i think the crawling animation underwater should be the swimming animation or at least be the swimming animation when you are not on the ground because it looks like the player is crawling on an invisible surface, and the same thing on the air as well.

Was fixed.


VS Code: intersection types, type not assignable

Hello, using VS Code to have typed JS (checkJs: true), but it seems to be having troubles with intersection types that work in both TS and JS in TS Playground without any error. Interestingly enough, properties from a second intersected type are correctly detected by VS Code despite the error on assignment of the typed value (see intellisence tooltip on the screenshot in Actual behavior).
TypeScript Version:  3.9.0-dev.20200420

Search Terms:
not assignable, Intersection types
Code
const ExtraProps = {
    one: 1,
    two: 2
}

class Test { }

/** @type {Test & ExtraProps} */
const inst = new Test();
inst.one;    // no complains

Playground Link
Assigning a properly defined type also does not work:
/**
 * @typedef {{[x in "one"|"two"]: number}} ExtraPropsType
 */

/** @type {Test & ExtraPropsType} */
const inst = new Test();

Expected behavior:

Actual behavior:

The behavior in VS Code is the desired one. Something's wrong with the Playground

The behavior in VS Code is the desired one. Something's wrong with the Playground

is both error for value assignment and later proper property detection desired tho?
regarding the playground: does the same problem occur in the following TypeScript code?

Playground Link

Just in case - there are no errors reported for JavaScript in current playground (see https://github.com/microsoft/TypeScript-Website/issues/203) so unfortunately you can't rely on it.
But you can see same error in Errors tab of new playground

wasn't aware of the new playground, thanks.
seems like a bug then, but, I'm wondering, how should this TS code behave then. no errors even in the Errors tab, correct recognition of properties from the second intersected type:

Playground Link

This one is type assertion which is completely different and might be not safe.

Type assertions are a way to tell the compiler “trust me, I know what I’m doing.”

This is definitely not the same as JS which correctly reports type that has missing properties.
Anyway you can use
/** @type {Test & ExtraPropsType} */
const inst = (new Test());

Which won't allow to check types in JS and won't complain. But it's still unsafe (as with most JS checks) so use it with care.

Thanks. Everyday, I'm learning some many new things about TS :).
I might have wrong thinking with all this overly complex structures and a bit too generic approaches, but I like to follow DRY principle and as TS does not support https://github.com/microsoft/TypeScript/issues/38115, I have to use some workarounds to have my code realm by my desires.

Linking this to https://github.com/microsoft/TypeScript-Website/issues/203 - I'm aiming to get this in before the 3.9 release build of the playground

How much ugly is this workaround :)?
type extraProps = {
    DecoratedProp: number;
    ExtendedProp: string;
}

function decorator(target: Function) {
    target.prototype.DecoratedProp = 2;
}

@decorator
class Test {
    Prop: number;
    constructor() {
        this.Prop = 1;
    }
}

Object.defineProperty(Test.prototype, 'ExtendedProp', { writable: true });

const DecoratedTest = Test as ((new () => Test & extraProps) & typeof Test);

const inst = new DecoratedTest();
console.log(inst.DecoratedProp);    // outputs "2"
inst.ExtendedProp = 'test';
console.log(inst.ExtendedProp);    // outputs "test"

Playground Link

The JS support for errors should be fixed on the staging site as of tomorrow: https://www.staging-typescript.org/play

The Playground and VS Code provide the same errors the same here when in JS mode on nightlies:

@IllusionMH  is right, the underlaying misconception here is what the @type is being applied to:
/** @type {Test & ExtraPropsType} */
const inst = new Test();

is like const inst: Test & ExtraPropsType = new Test(); vs
/** @type {Test & ExtraPropsType} */
const inst = (new Test());

is like const inst = new Test() as Test & ExtraPropsType
Which is why we get the error without the braces. This leaves the question to me as: Should we consider this a bug and always assume the as condition in this space?

Yeah, so I double checked this the behavior is as expected


Possible new/old social consensus bug? SocialConsensus validating failed with result 47 for block

Describe the bug
A clear and concise description of what the bug is.
Staking has stopped for multiple nodes and netstake weight is down to around 900000.
Possible social consensus bug?
To Reproduce
Steps to reproduce the behavior:
run node.
get error.
Expected behavior
stakeing should be automatic. I was getting around 8 to 10 a day and netstakeweight was around 3 or 4 million. Now it's 900 thousand and there have been no staking since yesterday. It's rather unusual. At this difficulty etc it should be at least 10 or so stakes for half a day.
Screenshots
No screen shots but there's some logs:
Pocketnet Core version 0.21.3 (release build)
2023-10-21T17:25:17Z +++ Block connected to chain: 2458645 BH: ace0d7fb48ccda6e832fc6b0d8ac8f04cf7a392501139c97f9d7adcc1c835ac0
2023-10-21T17:37:22Z Potential stale tip detected, will try using extra outbound peer (last tip update: 725 seconds ago)
2023-10-21T17:37:53Z New outbound peer connected: version: 70016, blocks=2458645, peer=618, peeraddr=<IP_ADDRESS>:37070 (full-relay)
2023-10-21T17:47:25Z Potential stale tip detected, will try using extra outbound peer (last tip update: 1328 seconds ago)
2023-10-21T17:47:26Z New outbound peer connected: version: 70016, blocks=2458645, peer=619, peeraddr=<IP_ADDRESS>:37070 (full-relay)
2023-10-21T17:57:30Z Potential stale tip detected, will try using extra outbound peer (last tip update: 1933 seconds ago)
2023-10-21T17:57:40Z New outbound peer connected: version: 70016, blocks=2458645, peer=620, peeraddr=<IP_ADDRESS>:37070 (full-relay)
2023-10-21T18:07:42Z Potential stale tip detected, will try using extra outbound peer (last tip update: 2545 seconds ago)
2023-10-21T18:07:42Z New outbound peer connected: version: 70016, blocks=2458645, peer=621, peeraddr=<IP_ADDRESS>:37070 (full-relay)
2023-10-21T18:17:51Z Potential stale tip detected, will try using extra outbound peer (last tip update: 3154 seconds ago)
2023-10-21T18:18:04Z New outbound peer connected: version: 70016, blocks=2458645, peer=622, peeraddr=<IP_ADDRESS>:37070 (full-relay)
2023-10-21T18:24:59Z GUI: Check updates result: error:  QNetworkReply::NetworkError(ProtocolUnknownError)
2023-10-21T18:28:03Z Potential stale tip detected, will try using extra outbound peer (last tip update: 3766 seconds ago)
2023-10-21T18:28:15Z New outbound peer connected: version: 70016, blocks=2458645, peer=623, peeraddr=<IP_ADDRESS>:37070 (full-relay)
2023-10-21T18:38:10Z Potential stale tip detected, will try using extra outbound peer (last tip update: 4373 seconds ago)
2023-10-21T18:39:12Z New outbound peer connected: version: 70016, blocks=2458449, peer=624, peeraddr=<IP_ADDRESS>:37070 (full-relay)
2023-10-21T18:41:28Z New outbound peer connected: version: 70016, blocks=2458645, peer=626, peeraddr=<IP_ADDRESS>:37070 (full-relay)
2023-10-21T18:48:21Z Potential stale tip detected, will try using extra outbound peer (last tip update: 4984 seconds ago)
2023-10-21T18:48:32Z New outbound peer connected: version: 70016, blocks=2458645, peer=627, peeraddr=<IP_ADDRESS>:37070 (full-relay)
2023-10-21T18:58:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 5592 seconds ago)
2023-10-21T18:59:15Z New outbound peer connected: version: 70016, blocks=2458645, peer=628, peeraddr=<IP_ADDRESS>:37070 (full-relay)
2023-10-21T19:08:38Z Potential stale tip detected, will try using extra outbound peer (last tip update: 6201 seconds ago)
2023-10-21T19:09:02Z New outbound peer connected: version: 70016, blocks=2458645, peer=630, peeraddr=<IP_ADDRESS>:37070 (full-relay)
2023-10-21T19:18:53Z Potential stale tip detected, will try using extra outbound peer (last tip update: 6816 seconds ago)
2023-10-21T19:19:09Z New outbound peer connected: version: 70016, blocks=2458645, peer=631, peeraddr=<IP_ADDRESS>:37070 (full-relay)
2023-10-21T19:19:49Z socket receive timeout: 1201s
2023-10-21T19:20:47Z New outbound peer connected: version: 70016, blocks=2458645, peer=632, peeraddr=<IP_ADDRESS>:37070 (block-relay)
2023-10-21T19:24:59Z GUI: Check updates result: error:  QNetworkReply::NetworkError(ProtocolUnknownError)
2023-10-21T19:29:01Z Potential stale tip detected, will try using extra outbound peer (last tip update: 7424 seconds ago)
2023-10-21T19:30:26Z New outbound peer connected: version: 70016, blocks=2458645, peer=634, peeraddr=<IP_ADDRESS>:37070 (full-relay)
2023-10-21T19:39:16Z Potential stale tip detected, will try using extra outbound peer (last tip update: 8039 seconds ago)
2023-10-21T19:39:40Z New outbound peer connected: version: 70016, blocks=2458645, peer=635, peeraddr=<IP_ADDRESS>:37070 (full-relay)
2023-10-21T19:39:47Z === Staking : new PoS block found hash: 2458646 - 8ac48b853106eca6c8037b94323bd738987fae9379fa7cd5682f51fed770f390
2023-10-21T19:39:48Z WARNING: SocialConsensus validating failed with result 47 for block 8ac48b853106eca6c8037b94323bd738987fae9379fa7cd5682f51fed770f390
2023-10-21T19:39:48Z ERROR: ConnectTip: ConnectBlock 8ac48b853106eca6c8037b94323bd738987fae9379fa7cd5682f51fed770f390 failed, failed-validate-social-consensus
2023-10-21T19:39:50Z === Staking : new PoS block found hash: 2458646 - c318582e6bbb8d2624ff35a42dd8c4cd35b5b5c8e82e491c42b2404920b4a900
2023-10-21T19:39:50Z WARNING: SocialConsensus validating failed with result 47 for block c318582e6bbb8d2624ff35a42dd8c4cd35b5b5c8e82e491c42b2404920b4a900
2023-10-21T19:39:50Z ERROR: ConnectTip: ConnectBlock c318582e6bbb8d2624ff35a42dd8c4cd35b5b5c8e82e491c42b2404920b4a900 failed, failed-validate-social-consensus
2023-10-21T19:39:52Z === Staking : new PoS block found hash: 2458646 - c318582e6bbb8d2624ff35a42dd8c4cd35b5b5c8e82e491c42b2404920b4a900
2023-10-21T19:39:52Z WARNING: SocialConsensus validating failed with result 47 for block c318582e6bbb8d2624ff35a42dd8c4cd35b5b5c8e82e491c42b2404920b4a900
2023-10-21T19:39:52Z ERROR: ConnectTip: ConnectBlock c318582e6bbb8d2624ff35a42dd8c4cd35b5b5c8e82e491c42b2404920b4a900 failed, failed-validate-social-consensus
2023-10-21T19:39:54Z === Staking : new PoS block found hash: 2458646 - 85966dbdbfccb02b91c8f7d594d2ff18e1f0ec994ab6f511a2b599b88337df15
2023-10-21T19:39:57Z WARNING: SocialConsensus validating failed with result 47 for block 85966dbdbfccb02b91c8f7d594d2ff18e1f0ec994ab6f511a2b599b88337df15
2023-10-21T19:39:57Z ERROR: ConnectTip: ConnectBlock 85966dbdbfccb02b91c8f7d594d2ff18e1f0ec994ab6f511a2b599b88337df15 failed, failed-validate-social-consensus
2023-10-21T19:39:59Z === Staking : new PoS block found hash: 2458646 - 388c8ffc8ea0c8cb9921d75afc465c49a400949bf893b1018c2fde969e9b1bfb
2023-10-21T19:39:59Z WARNING: SocialConsensus validating failed with result 47 for block 388c8ffc8ea0c8cb9921d75afc465c49a400949bf893b1018c2fde969e9b1bfb
2023-10-21T19:39:59Z ERROR: ConnectTip: ConnectBlock 388c8ffc8ea0c8cb9921d75afc465c49a400949bf893b1018c2fde969e9b1bfb failed, failed-validate-social-consensus
2023-10-21T19:40:01Z === Staking : new PoS block found hash: 2458646 - 9f1981c8bf713ed70660e9135c57dbaedfcb8d3bdceb4b2da5b3d213af369c60
2023-10-21T19:40:01Z WARNING: SocialConsensus validating failed with result 47 for block 9f1981c8bf713ed70660e9135c57dbaedfcb8d3bdceb4b2da5b3d213af369c60
2023-10-21T19:40:01Z ERROR: ConnectTip: ConnectBlock 9f1981c8bf713ed70660e9135c57dbaedfcb8d3bdceb4b2da5b3d213af369c60 failed, failed-validate-social-consensus
2023-10-21T19:49:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 8652 seconds ago)
2023-10-21T19:49:39Z New outbound peer connected: version: 70016, blocks=2458645, peer=636, peeraddr=<IP_ADDRESS>:37070 (full-relay)
2023-10-21T19:51:29Z New outbound peer connected: version: 70016, blocks=2458645, peer=637, peeraddr=<IP_ADDRESS>:37070 (full-relay)
2023-10-21T19:59:35Z Potential stale tip detected, will try using extra outbound peer (last tip update: 9258 seconds ago)
2023-10-21T20:00:27Z New outbound peer connected: version: 70016, blocks=2458645, peer=638, peeraddr=<IP_ADDRESS>:37070 (full-relay)
2023-10-21T20:09:47Z Potential stale tip detected, will try using extra outbound peer (last tip update: 9870 seconds ago)
2023-10-21T20:10:28Z New outbound peer connected: version: 70016, blocks=2458645, peer=639, peeraddr=<IP_ADDRESS>:37070 (full-relay)
2023-10-21T20:20:07Z Potential stale tip detected, will try using extra outbound peer (last tip update: 10490 seconds ago)
2023-10-21T20:20:19Z New outbound peer connected: version: 70016, blocks=2458645, peer=640, peeraddr=<IP_ADDRESS>:37070 (full-relay)
2023-10-21T20:24:57Z GUI: Check updates result: error:  QNetworkReply::NetworkError(ProtocolUnknownError)
2023-10-21T20:29:50Z     Block indexed: 2458646 BH: 102b95ebd73c5f8192741235bb183d6dfdf79478d1141701dd3753ff0fbfcfd9
2023-10-21T20:29:50Z +++ Block connected to chain: 2458646 BH: 102b95ebd73c5f8192741235bb183d6dfdf79478d1141701dd3753ff0fbfcfd9
2023-10-21T20:31:41Z     Block indexed: 2458647 BH: 011251a59a75f13ec73724ddb74dd9d4549deab6d58d6557d3ef6d02cec92199
2023-10-21T20:31:41Z +++ Block connected to chain: 2458647 BH: 011251a59a75f13ec73724ddb74dd9d4549deab6d58d6557d3ef6d02cec92199
further logs a few mins later:
2023-10-21T20:55:15Z     Block indexed: 2458664 BH: 440f38787375897ea0227f3f2a11b3e6f44444e72685de2b4b4ad19005cfb81a
2023-10-21T20:55:15Z +++ Block connected to chain: 2458664 BH: 440f38787375897ea0227f3f2a11b3e6f44444e72685de2b4b4ad19005cfb81a
2023-10-21T20:55:17Z === Staking : new PoS block found hash: 2458665 - 4a143f689b3a0b0061572ee35ab4e57f22776f4a6843eca664d19d45939f6cc6
2023-10-21T20:55:17Z WARNING: SocialConsensus validating failed with result 47 for block 4a143f689b3a0b0061572ee35ab4e57f22776f4a6843eca664d19d45939f6cc6
2023-10-21T20:55:17Z ERROR: ConnectTip: ConnectBlock 4a143f689b3a0b0061572ee35ab4e57f22776f4a6843eca664d19d45939f6cc6 failed, failed-validate-social-consensus
2023-10-21T20:55:18Z === Staking : new PoS block found hash: 2458665 - 675152380fb4bd85dce454a0899302ec648e45d96f0b9b882d3f6db5e4771e5f
2023-10-21T20:55:19Z WARNING: SocialConsensus validating failed with result 47 for block 675152380fb4bd85dce454a0899302ec648e45d96f0b9b882d3f6db5e4771e5f
2023-10-21T20:55:19Z ERROR: ConnectTip: ConnectBlock 675152380fb4bd85dce454a0899302ec648e45d96f0b9b882d3f6db5e4771e5f failed, failed-validate-social-consensus
2023-10-21T20:55:20Z === Staking : new PoS block found hash: 2458665 - 675152380fb4bd85dce454a0899302ec648e45d96f0b9b882d3f6db5e4771e5f
2023-10-21T20:55:21Z WARNING: SocialConsensus validating failed with result 47 for block 675152380fb4bd85dce454a0899302ec648e45d96f0b9b882d3f6db5e4771e5f
2023-10-21T20:55:21Z ERROR: ConnectTip: ConnectBlock 675152380fb4bd85dce454a0899302ec648e45d96f0b9b882d3f6db5e4771e5f failed, failed-validate-social-consensus
I restarted the node and later got these errors:
2023-10-22T08:00:43Z +++ Block connected to chain: 2459337 BH: 010836045c1586fda128bacdfa06dc5eec2c1ed3dab0dbe560dbe5ac0dbb83c9
2023-10-22T08:02:10Z === Staking : new PoS block found hash: 2459338 - 445c0be6955a0a2204a99f04eaff93ed401acfc6982302746646520a62de64f1
2023-10-22T08:02:10Z WARNING: SocialConsensus validating failed with result 47 for block 445c0be6955a0a2204a99f04eaff93ed401acfc6982302746646520a62de64f1
2023-10-22T08:02:10Z ERROR: ConnectTip: ConnectBlock 445c0be6955a0a2204a99f04eaff93ed401acfc6982302746646520a62de64f1 failed, failed-validate-social-consensus
2023-10-22T08:02:12Z === Staking : new PoS block found hash: 2459338 - fdc0606a6a3197210a22d97b6501ea4dae32c03595e27d50369435ff76b1bc3f
2023-10-22T08:02:12Z WARNING: SocialConsensus validating failed with result 47 for block fdc0606a6a3197210a22d97b6501ea4dae32c03595e27d50369435ff76b1bc3f
2023-10-22T08:02:12Z ERROR: ConnectTip: ConnectBlock fdc0606a6a3197210a22d97b6501ea4dae32c03595e27d50369435ff76b1bc3f failed, failed-validate-social-consensus
2023-10-22T08:02:14Z === Staking : new PoS block found hash: 2459338 - fdc0606a6a3197210a22d97b6501ea4dae32c03595e27d50369435ff76b1bc3f
2023-10-22T08:02:14Z WARNING: SocialConsensus validating failed with result 47 for block fdc0606a6a3197210a22d97b6501ea4dae32c03595e27d50369435ff76b1bc3f
2023-10-22T08:02:14Z ERROR: ConnectTip: ConnectBlock fdc0606a6a3197210a22d97b6501ea4dae32c03595e27d50369435ff76b1bc3f failed, failed-validate-social-consensus
2023-10-22T08:02:16Z === Staking : new PoS block found hash: 2459338 - e2f3b7ba655ab0cc7e36586b390cbf802734f1e9b2d586285508e96aaa341131
2023-10-22T08:02:16Z WARNING: SocialConsensus validating failed with result 47 for block e2f3b7ba655ab0cc7e36586b390cbf802734f1e9b2d586285508e96aaa341131
2023-10-22T08:02:16Z ERROR: ConnectTip: ConnectBlock e2f3b7ba655ab0cc7e36586b390cbf802734f1e9b2d586285508e96aaa341131 failed, failed-validate-social-consensus
2023-10-22T08:02:18Z === Staking : new PoS block found hash: 2459338 - e2f3b7ba655ab0cc7e36586b390cbf802734f1e9b2d586285508e96aaa341131
2023-10-22T08:02:18Z WARNING: SocialConsensus validating failed with result 47 for block e2f3b7ba655ab0cc7e36586b390cbf802734f1e9b2d586285508e96aaa341131
2023-10-22T08:02:18Z ERROR: ConnectTip: ConnectBlock e2f3b7ba655ab0cc7e36586b390cbf802734f1e9b2d586285508e96aaa341131 failed, failed-validate-social-consensus
2023-10-22T08:02:20Z === Staking : new PoS block found hash: 2459338 - dcd8b74b6442525096fa169caa511ab5f9ab0f702b27576db2184fea31378f09
2023-10-22T08:02:21Z WARNING: SocialConsensus validating failed with result 47 for block dcd8b74b6442525096fa169caa511ab5f9ab0f702b27576db2184fea31378f09
2023-10-22T08:02:21Z ERROR: ConnectTip: ConnectBlock dcd8b74b6442525096fa169caa511ab5f9ab0f702b27576db2184fea31378f09 failed, failed-validate-social-consensus
2023-10-22T08:02:22Z === Staking : new PoS block found hash: 2459338 - b19aab1f131be5c7779263be70888327faea5dcbc3c311ff6b59dc1af81716d5
2023-10-22T08:02:22Z WARNING: SocialConsensus validating failed with result 47 for block b19aab1f131be5c7779263be70888327faea5dcbc3c311ff6b59dc1af81716d5
2023-10-22T08:02:22Z ERROR: ConnectTip: ConnectBlock b19aab1f131be5c7779263be70888327faea5dcbc3c311ff6b59dc1af81716d5 failed, failed-validate-social-consensus
2023-10-22T08:02:24Z === Staking : new PoS block found hash: 2459338 - b19aab1f131be5c7779263be70888327faea5dcbc3c311ff6b59dc1af81716d5
2023-10-22T08:02:24Z WARNING: SocialConsensus validating failed with result 47 for block b19aab1f131be5c7779263be70888327faea5dcbc3c311ff6b59dc1af81716d5
2023-10-22T08:02:24Z ERROR: ConnectTip: ConnectBlock b19aab1f131be5c7779263be70888327faea5dcbc3c311ff6b59dc1af81716d5 failed, failed-validate-social-consensus
Desktop (please complete the following information):

OS: Windows 10
palemoon and chrome
newest.

Additional context
Add any other context about the problem here.
This issue is happening to a few others. I'm going to try and see if I can play around with the forking cli commands and try and find a working chain.

I added persistmempool=0 to the config file and restarted the node. Staking has started again. I don't know if the consensus error is still there.
I'm still seeing v0.21.2 nodes connecting to this node. I assumed that the older versions would be dropped?

I have one extra thing that may or may not mean anything. I consolidated a few hundred coin inputs a day or two before the issue. I have no idea if that may cause an issue.

Could you show the output of the getmempoolinfo command?

This problem was fixed and resolved in #618


Added i2c_master function

Adds i2c_master function and some necessary imports. Tested with Arduino 33 IoT and SSD 1306 OLED display.

Would you mind if I added you to our "board owner list" so you can be pinged in the future for testing with this board?

Sure, no problem! I'll be happy to help.


Version Packages

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
<EMAIL_ADDRESS>Patch Changes

b26534b: Added batch-loader plugin

<EMAIL_ADDRESS>Patch Changes

b26534b: Added batch-loader plugin
Updated dependencies [b26534b]

<EMAIL_ADDRESS>

The following preview packages were published:

Name
Version
Install Command

@frontside/backstage-plugin-batch-loader
0.1.2-changeset-release-main.0
yarn add @frontside/backstage-plugin-batch-loader@changeset-release-main

Generated by @thefrontside/actions


 \/\ \
      \ \_\ \____/\ \____/ /\____\ \__/.\_\ \_\ \_\
       \/_/\/___/  \/___/  \/____/\/__/\/_/\/_/\/_/
Create a new ZanPhp application.
Which type application would you create? (use <space> to select)
 ○ HTTP
❯ ● TCP
Your application name: (ex: zanphp-demo)
Use default application name: zanphp-demo
Your application namespace: (ex: zanphp/zanhttp)
Use default namespace: zanphp/zanhttp
Please input a output directory:
/git/zan-installer
Downloading the source code archive ...
Extracting archive ...
PHP Warning:  file_get_contents(/git/zan-installer/zanphp-demo/init/app.php): failed to open stream: No such file or directory in /git/zan-installer/src/Installer.php on line 254

Warning: file_get_contents(/git/zan-installer/zanphp-demo/init/app.php): failed to open stream: No such file or directory in /git/zan-installer/src/Installer.php on line 254
Set {{APP_NAME}} fail :(

  __    __
  /\ \  /\ \
  \ `\`\\/'/ ___   __  __  ____      __      ___
   `\ `\ /' / __`\/\ \/\ \/\_ ,`\  /'__`\  /' _ `\
     `\ \ \/\ \L\ \ \ \_\ \/_/  /_/\ \L\.\_/\ \/\ \
       \ \_\ \____/\ \____/ /\____\ \__/.\_\ \_\ \_\
        \/_/\/___/  \/___/  \/____/\/__/\/_/\/_/\/_/
Create a new ZanPhp application.
Which type application would you create? (use <space> to select)
  ○ HTTP
❯ ● TCP
Your application name: (ex: zanphp-demo)
Use default application name: zanphp-demo
Your application namespace: (ex: zanphp/zanhttp)
Use default namespace: zanphp/zanhttp
Please input a output directory:
/git/zan-installer
Downloading the source code archive ...
Extracting archive ...
PHP Warning:  file_get_contents(/git/zan-installer/zanphp-demo/init/app.php): failed to open stream: No such file or directory in /git/zan-installer/src/Installer.php on line 254

Warning: file_get_contents(/git/zan-installer/zanphp-demo/init/app.php): failed to open stream: No such file or directory in /git/zan-installer/src/Installer.php on line 254
Set {{APP_NAME}} fail :(

Sorry, we do not yet open source TCP version of Zan. Please wait, we will inform you of open source.


Final release of Bridge.Collections with maximum version configured

As of Bridge 16.0, Bridge.Collections has been merged into the main Bridge repo within the System namespace.
In order to prevent an old Bridge.Collections package from being included in a Bridge 16+ project, a new Bridge.Collections package should be published with a maximum version set in the <dependencies>.
<dependencies>
  <dependency id="Bridge.Core" version="(,15.7.0]" />
</dependencies>

See Also

https://github.com/bridgedotnet/Bridge/issues/2730
https://github.com/bridgedotnet/Bridge/issues/2758#issuecomment-306456328

The final Bridge.Collections with the maximum version on 15.7.0 constraint has been published to NuGet.
https://www.nuget.org/packages/Bridge.Collections/


Failed DBT Install with Brew, Success with Pip, But DBT Throws Errors

Describe the bug
I used brew install dbt a few times and it would run for awhile and then blow up at the end with a half-page full of errors.  I then tried pip and couldn't get that to work, finally tried python3 -m pip install dbt and that ran all the way through!  The problem now is when I try a dbt command I get an error log every time. The same error log no matter the command.
To me it feels like DBT needs to use a recent version of Python but this old 2.7 version, which I'm not sure how it got there and I don't need, may be interfering? I never overtly installed any versions of Python but somehow I seem to have acquired 3. Just a guess.
Steps To Reproduce
Expected behavior
If I type "dbt --version" I expect to simply see the version.  Instead I get an error log.
Screenshots and log output
System information
Which database are you using dbt with?

[ ] postgres
[ ] redshift
[ ] bigquery
[ ] snowflake
[ ] other (specify: None yet_)

The output of dbt --version:
Traceback (most recent call last):
  File "/opt/homebrew/bin/dbt", line 5, in <module>
    from dbt.main import main
  File "/opt/homebrew/lib/python3.9/site-packages/dbt/main.py", line 11, in <module>
    import dbt.version
  File "/opt/homebrew/lib/python3.9/site-packages/dbt/version.py", line 100, in <module>
    installed = get_installed_version()
  File "/opt/homebrew/lib/python3.9/site-packages/dbt/version.py", line 29, in get_installed_version
    return dbt.semver.VersionSpecifier.from_version_string(__version__)
  File "/opt/homebrew/lib/python3.9/site-packages/dbt/semver.py", line 100, in from_version_string
    return cls.from_dict(matched)
  File "/opt/homebrew/lib/python3.9/site-packages/hologram/__init__.py", line 618, in from_dict
    cls.validate(data)
  File "/opt/homebrew/lib/python3.9/site-packages/hologram/__init__.py", line 957, in validate
    schema = _validate_schema(cls)
  File "/opt/homebrew/lib/python3.9/site-packages/hologram/__init__.py", line 183, in _validate_schema
    schema = schema_cls.json_schema()
  File "/opt/homebrew/lib/python3.9/site-packages/hologram/__init__.py", line 942, in json_schema
    return cls._json_schema_recursive(
  File "/opt/homebrew/lib/python3.9/site-packages/hologram/__init__.py", line 913, in _json_schema_recursive
    schema = cls._schema_defs_from_cache(definitions)
  File "/opt/homebrew/lib/python3.9/site-packages/hologram/__init__.py", line 900, in _schema_defs_from_cache
    schema = cls._collect_json_schema(definitions)
  File "/opt/homebrew/lib/python3.9/site-packages/hologram/__init__.py", line 863, in _collect_json_schema
    properties[target_field], is_required = cls._get_field_schema(
  File "/opt/homebrew/lib/python3.9/site-packages/hologram/__init__.py", line 809, in _get_field_schema
    field_schema, required = cls._get_schema_for_type(
  File "/opt/homebrew/lib/python3.9/site-packages/hologram/__init__.py", line 783, in _get_schema_for_type
    raise ValidationError(f"Unable to create schema for '{type_name}'")
hologram.ValidationError: Unable to create schema for 'Optional'

The operating system you're using:
Big Sur 11.0.1
The output of python --version:
Python 2.7.16
Additional context
brew list | grep python
<EMAIL_ADDRESS><EMAIL_ADDRESS>Even though Homebrew ran for awhile trying to install dbt I thought I'd try to get rid of it and I get this:
brew uninstall dbt
Error: No available formula or cask with the name "dbt".

Hey @jkellogg1998!
Based on the error message, it appears that your python3 is using python 3.9. You can confirm this by running:
$ python3 --version

The latest version of dbt v0.19.0 has full support for python 3.6, 3.7, and 3.8. You can try reinstalling or relinking python to use<EMAIL_ADDRESS>(installed via brew) instead of python 3.9:
# reinstall
$ brew reinstall<EMAIL_ADDRESS>
# or relink
$ brew unlink<EMAIL_ADDRESS>$ brew link --force<EMAIL_ADDRESS>
If you do know which adapter you're planning to use, and it's not Snowflake, you can install that specific adapter in a py3.9 environment. This doesn't work for dbt-snowflake because of some dependencies of the Snowflake python connector.
$ pip install dbt-postgres

FYI: This isn't the best place for installation help. If you're working out the quirks of your local system or python env, StackOverflow is going to be more helpful (and likely someone has already experienced your same issue, or similar). If you believe there is a bug with dbt, making it impossible or exceedingly difficult to install, then opening an issue in the dbt repo is the right move.


Refactor add_sorter helper methods to work more like add_tab_set

Simplifies the logic of the sorter methods to assemble attribute arrays from the raw sorts, and then HTML from the attribute arrays.
Hopefully makes it easier to refactor the HTML, later.

coverage: 93.685% (+0.001%) from 93.684% when pulling 6d3786c37f61d9721611d31cd3b9f1467c57b099 on nimmo-rubric into f99cb49385904c472716f8f8dc0612733c07ffb6 on main.


Receptive Field & Dilation

This library is truly amazing !
In my search for a library to calculate the receptive field size, I was really excited to find this library.
(I especially appreciate the support for Conv1d.)
But I have two questions.

it does not seem to support Dilation.
The receptive field is smaller closer to the input layer and larger closer to the output layer, but the library is showing the opposite.

P.S.
I've written a patch for both of them, but there is a problem that the receptive field size is not properly displayed when the max_depth is reduced...
# Applied patch

import torch.nn as nn
from torchscan import summary

m = nn.Sequential(
    nn.Conv1d(1, 1, 3, dilation=1),
    nn.ReLU(),
    nn.Conv1d(1, 1, 3, dilation=2),
    nn.ReLU(),
    nn.Conv1d(1, 1, 3, dilation=3)
)

n = nn.Sequential(
    nn.Conv1d(1, 1, 3, dilation=1),
    nn.ReLU(),
    nn.Conv1d(1, 1, 3, dilation=2),
    nn.ReLU(),
    nn.Conv1d(1, 1, 3, dilation=3)
)

l = nn.Sequential(
    m, nn.ReLU(), n
)

summary(l, (1, 100), receptive_field=True, max_depth=2)

# max_depth=2
____________________________________________________________________________________________________________
Layer                        Type                  Output Shape              Param #         Receptive field
============================================================================================================
sequential                   Sequential            (-1, 1, 76)               0               1
├─0                          Sequential            (-1, 1, 88)               0               13
|    └─0                     Conv1d                (-1, 1, 98)               4               3
|    └─1                     ReLU                  (-1, 1, 98)               0               3
|    └─2                     Conv1d                (-1, 1, 94)               4               7
|    └─3                     ReLU                  (-1, 1, 94)               0               7
|    └─4                     Conv1d                (-1, 1, 88)               4               13
├─1                          ReLU                  (-1, 1, 88)               0               13
├─2                          Sequential            (-1, 1, 76)               0               25
|    └─0                     Conv1d                (-1, 1, 86)               4               15
|    └─1                     ReLU                  (-1, 1, 86)               0               15
|    └─2                     Conv1d                (-1, 1, 82)               4               19
|    └─3                     ReLU                  (-1, 1, 82)               0               19
|    └─4                     Conv1d                (-1, 1, 76)               4               25
============================================================================================================

max_depth=1
____________________________________________________________________________________________________________
Layer                        Type                  Output Shape              Param #         Receptive field
============================================================================================================
sequential                   Sequential            (-1, 1, 76)               0               1
├─0                          Sequential            (-1, 1, 88)               12              3
├─1                          ReLU                  (-1, 1, 88)               0               13
├─2                          Sequential            (-1, 1, 76)               12              15
============================================================================================================

max_depth=0
____________________________________________________________________________________________________________
Layer                        Type                  Output Shape              Param #         Receptive field
============================================================================================================
sequential                   Sequential            (-1, 1, 76)               24              13
============================================================================================================

Hi @khirotaka,
Glad it was helpful and thanks for the issue!
Regarding dilation, you are correct. I actually was trying to come up with a more modularized way to handle this. If you do have a suggestion, I'm more than happy to discuss a PR :pray:
Regarding the receptive field, it's actually a design choice I made earlier:

the receptive field value the library outputs for each layer represents the receptive field relative to the output of the model, rather than its input.

This might be misleading but the idea was to be able to trace back the relative spatial dependency to a node in the output layer. However, I understand this can be confusing and perhaps it would be best to add an option to specify whether it is relative to the output of the model or the input (and to set the default in the order you suggested).
Regarding the reduction process, I actually implemented it to work using the receptive field increasing order of my initial PR over there: https://github.com/frgfm/torch-scan/blob/master/torchscan/utils.py#L175-L177
So we are to move forward with PRs, I would suggest splitting them up:

option to take input or output and receptive field basis, and adapt the reduction accordingly
support of dilation in conv layers

I'll look into this, but let me know if you want to help / submit a PR :+1:

Hey @khirotaka,
Actually, I didn't manage to really fix the receptive field computation as the values are really bound to be computed reversely (cf. https://distill.pub/2019/computing-receptive-fields/) for the whole model. If you have a draft that managed to get a 212 value on torchvision.models.vgg16, I'd be happy to take a look at it.
I tried a few things but it was far from ideal (had to reverse some changes from #31 in #33)

Hey! I'm going to share my idea for a patch. I hope this helps a little bit...
https://github.com/khirotaka/torch-scan/commit/e0932c227de38484413128181252bb0f48d5aa74

Hi @khirotaka,
Thanks for the suggestion! I actually managed to handle this by reversing the recurrence equations in #34 :ok_hand:
For the dilation part, I actually only integrated into the module kernel size to avoid changing the interface. It's working as a charm!
Thanks again :pray:

Thank you as well! I'm looking forward to the latest release!


Option to use message index instead of record sequence for partitioning

Motivation
Currently all the partitioners use the recordSequence field in order to partition messages. That field doesn't handle batch messages and, consequently, objects could be loss on the target storage. The record sequence has the same value for all the entries in a batch message. Only the last entry of the batch will be persisted on the storage.
Modifications

New option partitionerUseIndexAsOffset (default to false for compatibility) to use the message's index for partitioning.
The index is exposed only if the brokers expose the metadata (see https://github.com/apache/pulsar/wiki/PIP-70%3A-Introduce-lightweight-broker-entry-metadata). In case the index is not available on a message, the record sequence will be used.

Documentation

Does this pull request introduce a new feature? (yes)
If yes, how is the feature documented? (docs)

The record sequence has the same value for all the entries in a batch message. Only the last entry of the batch will be persisted on the storage.

Can you explain this scenario a bit more, why would only the last message be persisted? If all messages in a batch share the same recordSequence, I would expect them to end up in the same output file

The record sequence has the same value for all the entries in a batch message. Only the last entry of the batch will be persisted on the storage.

Can you explain this scenario a bit more, why would only the last message be persisted? If all messages in a batch share the same recordSequence, I would expect them to end up in the same output file

Sure. Let's take this scenario. We set batchSize=2.
We receive 3 records that are in the same BK entry, so they have same recordSequence.
1 and 2 are in the same flush cycle. Record 1 is taken to get the output filename (-> recordSequence). S3 objects created.
When the third message is flushed, the resulting output filename is the same because recordSequence is the same of the first one. So the previous object is overridden in S3.

But this PR is not solving the root cause here, which is the cloud storage connector do not handle file overwritten case.

It's true. Moreover the index approach is not enabled by default. But the solution is not that easy.

When a target file exists, the cloud storage connector should either load the file content, append the new content and overwrite it

This will violate the batchSize parameter

use another file name to save the file.

That would make sense. A time-based solution could be implemented as a new partitioner type.
However both the time-based approach and the index one will not guarantee absence of duplicates in case of ProcessingGuarantees = ATLEAST_ONCE.
The only way to avoid duplicates is to set batchSize = 1 (but it's not a good idea in terms of efficiency)
I think it's fine to merge this pull anyway.

Could you resolve the doc conflicts and add the new parameter to the azure provider config properties too? Then it's good to merge IMO :)


Build problem

While building this error shows:
Complete output from command python setup.py egg_info:
           running egg_info
           creating pip-egg-info/psycopg2.egg-info
           writing pip-egg-info/psycopg2.egg-info/PKG-INFO
           writing dependency_links to pip-egg-info/psycopg2.egg-info/dependency_links.txt
           writing top-level names to pip-egg-info/psycopg2.egg-info/top_level.txt
           writing manifest file 'pip-egg-info/psycopg2.egg-info/SOURCES.txt'
           Error: could not determine PostgreSQL version from '10.5'

           ----------------------------------------
       Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-4g2i4civ/psycopg2/
 !     Push rejected, failed to compile Python app.
 !     Push failed

Fixed in ef828f5e82aebbbc3511486589ac443339665b1f. Please try again.


cowboy and ranch version not compatible ?

What's the reason to use ranch 2.0.0 while cowboy 2.8.0 actually depend on ranch 1.7.1 ?
I believe the example app is having various issues due to this

That's most likely true, but since we're not actively maintaining this project that much anymore… it might take a while until it's fixed.
That is… unless you feel like submitting a PR 😉

I bumped ranch in https://github.com/inaka/cowboy_swagger/pull/126, pretty sure due to static analysis issues. Tests didn't complain. Running this in production didn't either, so I assumed everything was Okay. It is possible the example app is either not being tested or not updated properly (I don't remember having looked at it). Pull requests are accepted, though 😉

That's most likely true, but since we're not actively maintaining this project that much anymore… it might take a while until it's fixed.
That is… unless you feel like submitting a PR 😉

We are trying to adopt cowboy_swagger in our project. May I ask why you have stopped (actively) maintaining it?

I bumped ranch in #126, pretty sure due to static analysis issues. Tests didn't complain. Running this in production didn't either, so I assumed everything was Okay. It is possible the example app is either not being tested or not updated properly (I don't remember having looked at it). Pull requests are accepted, though 😉

I will try to test it again and get back to you with the incompatible parts.

for example: {connection_type, supervisor} leaked down to inet as socket options, resulting in this crash:
=CRASH REPORT==== 26-May-2021::16:36:33.466341 ===
  crasher:
    initial call: supervisor:ranch_acceptors_sup/1
    pid: <0.471.0>
    registered_name: []
    exception exit: badarg
      in function  inet_tcp:listen/2 (inet_tcp.erl, line 142)
      in call from ranch_acceptors_sup:start_listen_socket/4 (ranch_acceptors_sup.erl, line 78)
      in call from ranch_acceptors_sup:start_listen_sockets/5 (ranch_acceptors_sup.erl, line 54)
      in call from ranch_acceptors_sup:init/1 (ranch_acceptors_sup.erl, line 34)
      in call from supervisor:init/1 (supervisor.erl, line 301)
      in call from gen_server:init_it/2 (gen_server.erl, line 417)
      in call from gen_server:init_it/6 (gen_server.erl, line 385)
    ancestors: [<0.459.0>,ranch_sup,<0.442.0>]


price amount in API request and response

Description
How are you representing price amount in your APIs? I think most popular choices are strings and number. But for connexion, type: number, format: decimal is not supported yet I believe. What is the best practice for this?
In case of number, I guess there could be added some converter to convert number to decimal right after validation? What about returning price objects? Would it be also easy to serialize decimal for responses?
Strings I think are easier for handling, would be converted to decimal inside handler. But then there is missing validation and price is a number, not a string obviously.
I've seen this related issue in OpenAPI

Hey @lucas03 - are you referring to this example in the cookbook docs?
https://github.com/zalando/connexion/blob/master/docs/cookbook.rst#custom-type-format

I forgot I've read that in the past, thanks :)
more or less I was wondering if you use string or float or custom type for money. I found a few related articles:
Fun fact: Int was actually suggestion by Mark Ralphson, member of OpenAPI initiative.

*Relevant texts to price in API*
https://stackoverflow.com/questions/35709595/why-would-you-use-a-string-in-json-to-represent-a-decimal-number
https://allegro-restapi-guideline.readthedocs.io/en/latest/Representation/#price-and-currency
https://www.oreilly.com/ideas/how-a-restful-api-represents-resources

*Usages:*

*String*
https://developer.paypal.com/docs/api/overview/#make-your-first-call
http://developers.payu.com/en/restapi.html
https://help.shopify.com/en/api/reference/sales-channels/payment
https://w3c.github.io/payment-request/
https://www.twilio.com/docs/phone-numbers/pricing
https://github.com/NationalBankBelgium/REST-API-Design-Guide/wiki/REST-Resources-Actions

*Number*
https://docs.microsoft.com/en-us/azure/architecture/best-practices/api-design
https://stripe.com/docs/api
there are more of course, but we should not decide based on which one is used the most.

*TLDR*: I’ve read a few articles and now I’m leaning towards string as well.

I’d use `{"type": "string", "format": "decimal"}` with custom validation.

thanks for linking me document, I'll resolve this issue now.

Thanks for reporting back! Glad you were able to find a good solution, and
thanks for posting all that content for the next person to read up on.
On Tue, Nov 20, 2018, 8:59 AM Lukas Vojt<EMAIL_ADDRESS>wrote:

I forgot I've read that in the past, thanks :)
more or less I was wondering if you use string or float or custom type for
money. I found a few related articles:
Fun fact: Int was actually suggestion by Mark Ralphson, member of OpenAPI initiative.
Relevant texts to price in APIhttps://stackoverflow.com/questions/35709595/why-would-you-use-a-string-in-json-to-represent-a-decimal-numberhttps://allegro-restapi-guideline.readthedocs.io/en/latest/Representation/#price-and-currencyhttps://www.oreilly.com/ideas/how-a-restful-api-represents-resources
Usages:
Stringhttps://developer.paypal.com/docs/api/overview/#make-your-first-callhttp://developers.payu.com/en/restapi.htmlhttps://help.shopify.com/en/api/reference/sales-channels/paymenthttps://w3c.github.io/payment-request/https://www.twilio.com/docs/phone-numbers/pricinghttps://github.com/NationalBankBelgium/REST-API-Design-Guide/wiki/REST-Resources-Actions
Numberhttps://docs.microsoft.com/en-us/azure/architecture/best-practices/api-designhttps://stripe.com/docs/api
there are more of course, but we should not decide based on which one is used the most.
TLDR: I’ve read a few articles and now I’m leaning towards string as well.
I’d use {"type": "string", "format": "decimal"} with custom validation.
thanks for linking me document, I'll resolve this issue now.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/zalando/connexion/issues/782#issuecomment-440056706,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAlPSRHaRUQmq0enHdZTou-fKfNlqV-7ks5uwymrgaJpZM4YgE-8
.


CloudFormation stack fails to create with error

Describe the bug
Cloudformation stack fails to create with error:
[ElasticSearchStreamingLambdaCodeS3Bucket, ElasticSearchStreamingLambdaCodeS3Key] do not exist in the template
To Reproduce
Steps to reproduce the behavior:
Setup an environment
Have @searchable directive fail based on aws-amplify/amplify-cli#566
Remove @searchable directive for the time being and try again
Try to deploy again and get the above error
Expected behavior
I've remove all references to @searchable so I'm not sure that any references to ElasticSearch or ElasticSearch buckets should exist.
Versions:
amplify-cli - 0.2.1-multienv.7

Update:  Created a new environment to test out if a previous failure matters, and it appears to fail no matter what with this same error.  I'm not sure what would cause this.

Thanks for reporting this. If you have removed the @searchable directive then it should remove all dependencies on ES. Can you do me a favor and check the parameters.json file in your amplify/backend/api/[project] directory? Does that file contain a value for "ElasticSearchStreamingLambdaCodeS3Key" or "ElasticSearchStreamingLambdaCodeS3Bucket"? If so try removing them and pushing again. If you don't see those values in the params file please let me know as well.

I was at a point where I could re-create the project from scratch, so I did that to solve my issue.
Before I did that, I did look for those keys and do remember seeing them in the parameters json file.  I thought later to remove them, but have since updated the project.  I do believe that to be the source of the problem.  If I can, I will try to re-create and confirm.

Thanks a lot @mikeparisstuff !!
I have to mention though. While making a push, parameters.json is modified by amplify I guess, so I had to edit this file right before the update to the cloud begins.

Closing this issue. Please feel free to re-opne if the issue persists.

@kaustavghosh06 Can we please re-open this issue?  This has occurred again.
After encountering https://github.com/aws-amplify/amplify-cli/issues/631, I tried to back out my change to the schema.  I was not able to and got the same error as above.
@mikeparisstuff I did see the keys in the parameters.json file and tried removing them.  Running amplify push puts them back in, and then the push then fails for the same reason.  There doesn't appear to be a way to undo this change.  Please advise.

I was seeing this issue as well, after adding and removing @searchable from my schema. Manually deleting the directory amplify\backend\api\<api_name>\build seems to workaround the issue.

@jesse-bonzo This was able to solve my issue with doing a push.  Thanks!

Hey guys, this issue seems to be fixed in the latest version of the CLI. Pleae feel to re-open if you're still seeing this issue.

[ElasticSearchStreamingLambdaCodeS3Bucket, ElasticSearchStreamingLambdaCodeS3Key] do not exist in the template

@kaustavghosh06 I'm getting this error again with the latest version of the CLI.  Can we please re-open?  This time it doesn't appear to have anything to do with @searchable...


Getting logprobs from Mistral / Mixtral?

I am looking at the code for these models and would like to return the raw output of scores, as well as the softmax probabilities?
Is there a parameter for this when calling the vLLM instance? As I am looking at the: https://github.com/vllm-project/vllm/blob/main/vllm/engine/llm_engine.py and https://github.com/vllm-project/vllm/blob/main/vllm/model_executor/models/mixtral.py respectively as the areas where I would look to: 1) either fine the logprobs parameter or 2) code it myself, as I was using this in HuggingFace I would look to adapt the model.generate function to obtain these?
I know this links to other examples, but I would appreciate your help on this specifically?

I have traced the issue and found that the [sampling_params.py](https://github.com/vllm-project/vllm/blob/c9b45adeeb0e5b2f597d1687e0b8f24167602395/vllm/sampling_params.py) script does include the log probs and the main api_server.py has the additional args as kwargs, so I can expose the parameters for anyone else who has had issues with this.


Navigation does not work in thinclient_drives with the last PKG

Hello,
With the latest "Sudo Apt -Get Update - Upgrade" in my Buster Raspberry Pi distribution, XRDP has been updated.

The following packages will be updated:
"... Vim-Tiny Wireless-Regdb XRDP Xserver-Common Xserver-Xorg-Core XXD"

Since then, navigation does not work in thinclient_drives. The shared file folder appears empty continuously.
The previous version that works (OK):

"PKG_CONFIG_PATH =/BUILD/XRDP-Q47NHL/XRDP-0.9.9/PKGCONFIG"

The current version that does not work (KO):

"PKG_CONFIG_PATH =/BUILD/XRDP-X6KNLD/XRDP-0.9.9/PKGCONFIG"

What does dpkg -l xrdp give you for both? Has xrdp been patched by the distro?

ls ~/thinclient_drives
My_LC

`ls /home/pi/thinclient_drives/My_LC
2019-10-11-125251_1920x1080_scrot.png
'3d Tag Cloud.livecode'
'Achat Web.livecode'
advanced-multimedia.livecode
aGarderEtiquettesQR.livecode
alignement.livecode
....
`
and all the share is on the shell but not in pcmanfm of raspbian buster...
One more thing, I uninstalled XRDP and I reinstalled it: no difference.

Sorry, I don't understand what you are saying. What is My_LC? Is it a share?

Yes from Microsoft Remote Desktop

I still don't understand. It sounds to me like xrdp is working properly. Is it just the file manager on the desktop that isn't allowing the browsing?

yes, xrdp working fine, not the mount of thinclient_drives, after the last update of xrdp or something else.

@JM-Teule
I don't think we're understanding each other.
When I say "xrdp is working properly", I'm including the remote mount in that. You can browse files which are being exported by your xrdp client in your xrdp session from the command line using standard command like cd and ls. Is that right?
Can you access the files from the command line? What do you get for these commands:-
ls -l ~/thinclient_drives/My_LC/2019-10-11-125251_1920x1080_scrot.png
cksum ~/thinclient_drives/My_LC/2019-10-11-125251_1920x1080_scrot.png

Hello,
Sorry for that.
2 short videos will be better than long texts :
https://nextcloud.inrae.fr/s/cC6cAfzgFH6WpK6
Le 11 mai 2023 à 10:51, matt335672 @.***> a écrit :
@JM-Teulehttps://github.com/JM-Teule
I don't think we're understanding each other.
When I say "xrdp is working properly", I'm including the remote mount in that. You can browse files which are being exported by your xrdp client in your xrdp session from the command line using standard command like cd and ls. Is that right?
Can you access the files from the command line? What do you get for these commands:-
ls -l ~/thinclient_drives/My_LC/2019-10-11-125251_1920x1080_scrot.png
cksum ~/thinclient_drives/My_LC/2019-10-11-125251_1920x1080_scrot.png
—
Reply to this email directly, view it on GitHubhttps://github.com/neutrinolabs/xrdp/issues/2661#issuecomment-1543599389, or unsubscribehttps://github.com/notifications/unsubscribe-auth/APEQVSFZGEHDEYVLAZYRYP3XFSSCHANCNFSM6AAAAAAX4QB5BQ.
You are receiving this because you were mentioned.Message ID: @.***>
Cordialement,
Jean-Marc Teulé
IP - Informatique de Proximité
@.***
INRAE
UMR INRAE-UPPA 1224 Ecobiop
INRAE - Aquapôle, Ibarron
64310 St-Pée-sur-Nivelle, France
Tel 05 59 51 59 45
Portable 06 99 06 52 09
[cid:890099A3-BD84-4431-A14A-4ABC1890D740]

I'm afraid I'll have to insist on the textual description.
Other people may be reading this and searching for a solution to their problem. Also, viewing unsolicited videos simply isn't safe on the modern internet.

I have no more time for that !

The share is running int shell but not in graphic way !


DEPRECATION: ember-cli-babel 5.x has been deprecated

ember-index has a dependency on ember-cli-babel 5.x but the majority of ember modules have moved up to version 6. The project still tries to pull in version 5 and as a result we get a deprecation notice.

DEPRECATION: ember-cli-babel 5.x has been deprecated. Please upgrade to at least ember-cli-babel 6.6. Version 5.2.8 located: cafe-rouge -> ember-index -> ember-cli-babel

Please can you upgrade the module dependencies to remove this warning.
Using Ember v3 causes this message too.

fixed in https://github.com/ramybenaroya/ember-index/pull/12


Browser disconnected while run on kubernates pod

What is the Current behavior?
XXX browser disconnected. This problem may appear when a browser hangs or is closed, or due to network issues
What is the Expected behavior?
Do not disconnect or freeze chromium browser
Steps to Reproduce:
The setup we currently have where the problem reproduces is official testcafe/testcafe docker image run on the kubernates pod with the following resources allocated:
resourceLimitCpu: '5000m',
resourceLimitMemory: '5000Mi',

The error XXX browser disconnected. This problem may appear when a browser hangs or is closed, or due to network issues is happening in random places of the testsuite with arbitrary frequency. If to run the same docker image locally on Mac or if to run tests in debian VM everything works just fine and tests never crash.
It reproduces on chromium run with the following flags --no-sandbox --disable-dev-shm-usage and on the latest testcafe version 1.1.1. More frequently if to reduce the test run speed to 0.2 (--speed).
I've taken a look onto chromium logs but there is nothing suspicious except the following errors at the middle of the log file
[0403/084113.645826:ERROR:gpu_process_transport_factory.cc(1016)] Lost UI shared context.
[0403/084113.659220:ERROR:zygote_host_impl_linux.cc(270)] Failed to adjust OOM score of renderer with pid 657: Permission denied (13)
[0403/084113.704354:ERROR:gl_implementation.cc(292)] Failed to load /usr/lib/chromium/swiftshader/libGLESv2.so: Error loading shared library /usr/lib/chromium/swiftshader/libGLESv2.so: No such file or directory
[0403/084113.706164:ERROR:viz_main_impl.cc(201)] Exiting GPU process due to errors during initialization
[0403/084113.707268:ERROR:service_manager_context.cc(250)] Attempting to run unsupported native service: /usr/lib/chromium/content_gpu.service
[0403/084113.754683:ERROR:gl_implementation.cc(292)] Failed to load /usr/lib/chromium/swiftshader/libGLESv2.so: Error loading shared library /usr/lib/chromium/swiftshader/libGLESv2.so: No such file or directory
[0403/084113.756565:ERROR:viz_main_impl.cc(201)] Exiting GPU process due to errors during initialization
[0403/084113.757762:ERROR:service_manager_context.cc(250)] Attempting to run unsupported native service: /usr/lib/chromium/content_gpu.service

It never reproduces if to run tests on BrowserStack browsers, so I believe there could be something wrong with GCP kubernates configuration or a hosting environment. So any suggestions on how to localize and reproduce the problem are very welcome.
Your Environment details:

testcafe version:                   1.1.1
node.js version:                    8.15.0 / 10.15.0
command-line arguments:  CHROME_LOG_FILE=$(pwd)/chrome_debug_$(date +%s).log testcafe 'chromium:headless --no-sandbox --disable-dev-shm-usage --enable-logging --v=1 --disable-gpu --disable-translate --disable-extensions --no-proxy-server --disable-setuid-sandbox --disable-web-security' 'testcafe/'
browser name and version: Chromium 68/Chromium 72
platform and version:          Linux Alpine / Linux Debian 9

I can only assume that there is an issue with GCP configuration as you correctly mentioned. Perhaps your pricing plan does not provide enough performance for a browser. I cannot currently determine the real cause of the issue and can only share common recommendations from the documentation: https://devexpress.github.io/testcafe/faq/#not-enough-resources-in-the-container-or-ci-system

@AlexKamaev thank you for your response. As I mentioned in the issue we have a plenty of resources available and allocated for the pod

resourceLimitCpu: '5000m',
resourceLimitMemory: '5000Mi',

Where tests run fine locally even on a low end macbook pro 2010. So I just don't believe this is a case.

Set the concurrency factor to 1.

Confirm, it is 1

Deploy the application's Web server on a separate machine.

Tried that out and it works in VM as mentioned

Run tests on a local device outside a container.

Works as well
A part from those steps any other suggestions to investigate the causes of a issue? May network outage or VRAM effect? Anything you would suggest to take a look?

Hi @valerii-cognite

Based on the description, it looks like this issue is not related to TestCafe, but to the kubernetes setup/configuration or something else. We are not familiar with Kubernetes pod, so we cannot provide any valid suggestions. If you are able to provide us with a simple example to reproduce this issue, please reopen this issue.

In timecafe src I found a notion of HEARTBEAT_TIMEOUT which if exceeds the error above is going to be fired. In order to prevent that from happening every HEARTBEAT_INTERVAL browser should send a heartbeat to /browser/heartbeat/{id} callback of which will reset the interval. So for some reason even though I can see a chromium process up and running and recording logs the heartbeat may be absent for some random intervals or sometimes even exceeding the HEARTBEAT_TIMEOUT. What may cause such a problem?

I connected to the chromium instance through --remote-debugging-port option and ssh port forwarding. It seems tests are just stuck from time to time, here is an example (be patient it is 29s long)

Here is the test code sample
import { Selector } from 'testcafe';
import uuid from 'uuid/v4';
const salt = uuid();

fixture('Checklists').page('/checklists');

test('Checklists', async t => {
  const createButton = Selector(`[data-test-id="checklist-list-add-button"]`);
  const createConfirmButton = Selector(`[data-test-id="add-custom-list-create-button"]`);
  const createNameInput = Selector(`[data-test-id="add-custom-list-input"]`);
  const newChecklistName = `new checklist ${salt}`;

  console.log('Create new checklist without items');
  await t
    .click(createButton)
    // make sure confirm button is disabled for empty name
    .expect(createConfirmButton.hasAttribute('disabled'))
    .ok()
    .typeText(createNameInput, newChecklistName)
    // make sure confirm button is enabled
    .expect(createConfirmButton.hasAttribute('disabled'))
    .notOk()
    .click(createConfirmButton);
});

Below is the heartbeat breakdown for this test where you can see a gap for heartbeat:
[0409/193603.942928:VERBOSE1:network_delegate.cc(32)] NetworkDelegate::NotifyBeforeURLRequest: http://<IP_ADDRESS>:38209/browser/heartbeat/mvNvxG7
[0409/193603.942981:VERBOSE1:network_delegate.cc(32)] NetworkDelegate::NotifyBeforeURLRequest: http://<IP_ADDRESS>:38209/browser/heartbeat/mvNvxG7
[0409/193605.931130:VERBOSE1:network_delegate.cc(32)] NetworkDelegate::NotifyBeforeURLRequest: http://<IP_ADDRESS>:38209/browser/heartbeat/mvNvxG7
[0409/193605.931182:VERBOSE1:network_delegate.cc(32)] NetworkDelegate::NotifyBeforeURLRequest: http://<IP_ADDRESS>:38209/browser/heartbeat/mvNvxG7
[0409/193640.603728:VERBOSE1:network_delegate.cc(32)] NetworkDelegate::NotifyBeforeURLRequest: http://<IP_ADDRESS>:38209/browser/heartbeat/mvNvxG7
[0409/193640.603810:VERBOSE1:network_delegate.cc(32)] NetworkDelegate::NotifyBeforeURLRequest: http://<IP_ADDRESS>:38209/browser/heartbeat/mvNvxG7
[0409/193650.096301:VERBOSE1:network_delegate.cc(32)] NetworkDelegate::NotifyBeforeURLRequest: http://<IP_ADDRESS>:38209/browser/heartbeat/mvNvxG7
[0409/193650.096357:VERBOSE1:network_delegate.cc(32)] NetworkDelegate::NotifyBeforeURLRequest: http://<IP_ADDRESS>:38209/browser/heartbeat/mvNvxG7
[0409/193656.527291:VERBOSE1:network_delegate.cc(32)] NetworkDelegate::NotifyBeforeURLRequest: http://<IP_ADDRESS>:38209/browser/heartbeat/mvNvxG7
[0409/193656.527388:VERBOSE1:network_delegate.cc(32)] NetworkDelegate::NotifyBeforeURLRequest: http://<IP_ADDRESS>:38209/browser/heartbeat/mvNvxG7

If to load the same page just with chromium without testcafe and run same instructions it works without any freezes. I'm wondering, what can block testcafe thread so heavily?

Just to summarise.
I figured out those freezes were happening locally as well but almost not noticeably (less than a 1s) during the first page load. That was because of the high amount of data sent through the web socket connection calculating of which has been blocking the main thread. When I reimplemented that part tests became to be more stable (no issue occurred within a week so far). It seems (still not sure) on a lower end virtual machines those freezes were significant, which with testcafe polling overhead made a page hanging from time to time for more than 2 minutes.

Thank you for sharing your research. We will think if we can do something to avoid this problem in such conditions.


Add a way to log and view metrics

Currently considering Exceptionless and the one big missing thing we'd love is the ability to track metrics, specifically performance metrics. An application could be basically not working and still never throw and exception. Things like request times, query times, performance counters, contention, and high levels of requests can be extremely valuable information to have for diagnosing issues.
First class support for these would be awesome, but failing that, a way to send data to Exceptionless in a https://github.com/exceptionless/Foundatio#metrics like way and get good visualizations and alerts for it would be great.

Yes, currently we use statsd/librato for application stats for exceptionless and really like it. It would be nice to have a dashboard with some basic gauges / stats for this and alerts when we don't get a specific event in for a while at some point. Since we do have feature usage it might be nice to have usage times displayed. I'm not sure if this is out side of the scope.
@ejsmith @RichiCoder1  thoughts?

While it's outside of the scope of the name "Exceptionless", I think it's very in scope as a solution for diagnosing apps in production. Just about every app monitoring solution (new relic, app insights, etc...) provides some level of support for logging quantity, duration, or percentage of some metric. Even basic support would be fantastic.

I should give some back story too why this is valuable. The apps we construct are largely for internal use only. LoB apps. Because of this, more than a few don't either A) allow access to the general internet or B) don't want data (even anonymized) being transmitted to third party services. For the ones that meet neither, we'd normal go with on the above providers I mentioned. But because we can't go to the cloud, we need good hosted solutions of which there aren't many. Enter Exceptionless. Meets our logging and exception needs very well, but we still need some place to send metrics. Short of a Metrics.Net/Kibana nightmare, there aren't lot of good solutions. So there's a lot of value in extending Exceptionless to make it the one stop shop for this need.

Yeah I agree with you. We'll keep this in mind. We are currently working on site performance and then will be focusing on feature work.

Sounds good! Let me know if and how I can help move this along :)

I'm worried about us adding more features vs improving the ones that we do have, but maybe there is something simple that we can do. How would you see this working?

Probably the simplest, for a given level of simple, would be to allow submitting various metrics and then viewing them in an app sights-esque configurable dashboard: https://azure.microsoft.com/en-us/documentation/articles/app-insights-overview-usage/

If you just want counters, then we basically give you that ability now with being able to report events and then chart occurrences of those events over time. But timings are a whole new beast.
We are completely based around events right now... so we would have to have the concept of timings probably with percentiles and then be able to chart them over a filtered set of events that may or may not be timings. So most likely we would need a separate store just for timings which would introduce a whole new level of complexity to the entire app and clients as well.
I would love to have this feature as well, but I think the project needs to try and stay focused on doing events well for now.

I have been thinking about this some more and I think I have some ideas on how we can do it easily.

Add new event types for counter, gauge, and timing

Doesn’t really change anything on the backend, we already have a value field on events and we would just populate that field.
Site menu currently has all of our event types as 1st class menus, but this would be too many. So we need to think about how the navigation might change.
Add helper methods to the client to report these types of events.
We could pre-aggregate the data before sending a batch of events. Similar to how statsd does. Basically just summing the counter values into a single event. (Can happen later as it just saves us some processing work)
How are feature usage and counter different?

Add ability to create a custom reports page

Possibly use this: http://pkukielka.github.io/angular-panels/
Can specify the name of the report and would be listed under the reports section in the menu
2 types of widgets: timeline chart and number

Timeline would allow you to add multiple event stacks to the chart
When adding a stack, you can pick occurrences, value sum and value average.
You can label each stack you add we show that label in the chart / hover
You can select the color for the line on the chart
You can provide a value type description (like seconds or milliseconds or count)
You can provide a value transform function to do something like convert from milliseconds to seconds. This could happen after the initial launch.

Number would allow you to pick a single stack and would show the event value from the most recent event.

Would be able to add a label to the widget header

I report the request done to Blake to get:

most day of week with errors
most hour of the day with errors
most used operating system
most used browser

I was just about to open an issue for this. Performance metrics would make exceptionless a good competitor to app insights on azure. I think you would need to adjust the pricing/number of events though - longer retention in exceptionless but more events in App insights.  I'm unsure of what Session data vs Other data points though is on azure so maybe not.

You can do this today by submitting an event and specifying a value on the event.


Debugging cells doesn't work for untitled cells - it will open a temporary file instead of the unsaved file

This is a known limitation in the debugger. The debugger doesn't know about unsaved files.
This might be a solution to that problem:
https://code.visualstudio.com/docs/nodejs/nodejs-debugging#_access-loaded-scripts

See #6738