txnbuild: Injects the source account as the issuer in AllowTrust.FromXDR

PR Checklist
PR Structure

[x] This PR has reasonably narrow scope (if not, break it down into smaller PRs).
[x] This PR avoids mixing refactoring changes with feature changes (split into two PRs
otherwise).
[x] This PR's title starts with name of package that is most changed in the PR, ex.
services/friendbot, or all or doc if the changes are broad or impact many
packages.

Thoroughness

[ ] This PR adds tests for the most critical parts of the new functionality or fixes.
[x] I've updated any docs (developer docs, .md
files, etc... affected by this change). Take a look in the docs folder for a given service,
like this one.

Release planning

[x] I've updated the relevant CHANGELOG (here for Horizon) if
needed with deprecations, added features, breaking changes, and DB schema changes.
[x] I've decided if this PR requires a new major/minor version according to
semver, or if it's mainly a patch change. The PR is targeted at the next
release branch if it's not a patch change.

What
When decoding an AllowTrustOp from raw XDR, the resulting Asset.Issuer field will be blank, because its not included in the XDR directly. However, the issuer will always be the operation's source account, so we can backfill intelligently:

Allow Trust
This can only be called by the issuer of a trustline’s asset

Why
We should decode XDR to be as close as possible to their original pre-encoded structures.
Known limitations
If the operation is created without an issuer, decoding it will inject the issuer, meaning the operations aren't identical. This is unavoidable: we either never have an issuer (there isn't one in the XDR) or always have an issuer (pull it from the source account). Given that custom assets should always have issuers, the latter is preferred.

New snafu found in 8582fe52: since an operation's source account is optional, this will only sometimes back-fill.

an operation's source account is optional, this will only sometimes back-fill.

Oh, good point. In those cases it comes from the transaction source account, but we don't have that in this scope.
What a conundrum.
What if we remove the issuer from the AllowTrustOp?
I guess ignore the problem is also an option, if benefit to fixing it is less than the effort and consequences.
This has been a helpful learning experience for me regardless. We frequently make decisions at the protocol layer on the assumption a higher up layer can abstract the inconvenience, but abstractions are leaky.

Eric and I discussed this offline, and ultimately decided that this should be put on ice given the design & implementation challenges / time commitments appear to outweigh the benefits. This clearly needs more thought, more dev time (especially to work through test cases that appear to depend on this arguably-broken but inarguably-confusing behavior), and perhaps even breaking changes to the SDK.

Just to summarize our collaborative investigations for posterity,
The original problem
If you encode an AllowTrust operation with a valid CreditAsset (i.e. the Issuer field set) into XDR, then decode that XDR back into an AllowTrust object, the asset's issuer will be empty.
Why? Well, only the issuer of the asset can create a valid AllowTrustOp in the first place, so this redundant information isn't stored in the XDR.
However, this is problematic and unintuitive, because SDK consumers expect consistency between a pre-encoded structure (i.e. a structure they crafted and sent on the wire) and the post-decoded structure (i.e. one they receive from the wire). In this case, the SDK is over-promising and under-delivering in its higher-level abstraction: xdr.AllowTrustOp.Asset (of type xdr.AssetCode) can only partially fill txnbuild.AllowTrust.Type (of type txnbuild.CreditAsset).
The original solution
The solution seemed straightforward: backfill AllowTrust.Asset.Issuer from the source account when parsing.
A can of bugs
Even with this best-effort attempt, there are some non-trivial considerations:

We have to be careful about muxed accounts.

The operation's source account is optional, so it only sometimes work. If the goal is to make the pre-encoding and post-decoding structures match, we still fall short.

Certain test cases (e.g. TestAllowTrustNoIssuer) seemed to have expected this behavior.

Other projects in the monorepo (e.g. regulated-assets-approval-server, with this test) also broke with this change.

Possible resolutions

We can continue with the "best-effort backfill," only working works when the operation's source account is set. This will require non-trivial refactoring to test cases across the monorepo.

func (at *AllowTrust) FromXDR(xdrOp xdr.Operation, withMuxedAccounts bool) error {
	// [...]
	t.Issuer = accountFromXDR(xdrOp.SourceAccount, false)
	// [...]
}

We can create a new type that conforms closer to the XDR (like CreditAssetCode) and doesn't include an issuer. This would literally only be used for the now-deprecated AllowTrust operation.

We can add more sanity-checking when building the AllowTrust operation, for example ensuring that if the source account is set, it matches the asset issuer, and that the asset issuer must be set, since a CreditAsset object without an issuer is somewhat nonsensical. This doesn't have many tangible benefits, though.

We can call this "working as intended," or say "prefer SetTrustLineFlags instead of this deprecated op," and just move on.

Regardless, this is no longer trivial and should be put on hold until time, bandwidth, desire, or need permits.


Handle long column names better in Key/Value Columns dialog

@thadguidry is this ticket going to be in review status for some more time, or it can be set as done ?

@obarabanov issues are closed when the corresponding PR is merged (automatically if they have been properly linked, by writing "closes #898" or "fixes #898" in the pull request or commit message).

ah ok it's like in other collaboration platfrorms. But I haven't linked it properly, anyway.
My idea was just to give idea / to indicate this ticket is taken / being worked on.
Not sure who's going to merge the PR ?

Sure, we can assign you for that.

Closed by #2352.


Error when trying to change image in gallery

Whenever I try to change the image in a gallery of a collection the CMS throws the following error:
TypeError: t.getObjectValue(...).set is not a function
    at ListControl.js:163:57
    at onChange (EditorControl.js:70:48)
    at n.value (withMediaControl.js:56:9)
    at ii (react-dom.production.min.js:149:32)
    at Ai (react-dom.production.min.js:177:1)
    at ua (react-dom.production.min.js:201:16)
    at ca (react-dom.production.min.js:202:231)
    at Ka (react-dom.production.min.js:211:214)
    at Ha (react-dom.production.min.js:210:277)
    at za (react-dom.production.min.js:210:113)

This is my collection config:
collections:
  - name: "projekt" # Used in routes, e.g.,
    label: "Projekt" # Used in the UI
    folder: "projekti" # The path to the folder where the documents are stored
    create: true # Allow users to create new documents in this collection
    slug: "{{year}}-{{month}}-{{day}}-{{slug}}" # Filename template, e.g., YYYY-MM-DD-title.md
    fields: # The fields for each document, usually in front matter
      - {label: "Naslov", name: "title", widget: "string"}
      - {label: "Publish Date", name: "date", widget: "datetime"}
      - {label: "Opis", name: "description", widget: "markdown"}
      - {label: "Aktualen", name: "active", widget: "boolean", default: true}
      - {label: "Opomba", name: "disclaimer", widget: "string", required: false}
      - label: "Galerija"
        name: "gallery"
        widget: "list"
        summary: '{{fields.image}}'
        field: { label: Image, name: image, widget: image }
      - label: "Kategorija"
        name: "category"
        widget: "select"
        options: [ "Gradnje", "Nadzori" ]

The image extensions are jpg and jpeg

My bad I was using netlify-cms@1 package version.


Optimize chart

Description

Fix the chart so it can be used directly
Optimize the chart to use etcd v3.4 and above
Related issues
Closes #347

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.曹阳兴 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

thanks


change os.path to pathlib.Path #798

This pull request aims to replace string type variables with pathlib.Path type variables that represent file system paths.

thank you @DiegoRomeo! i will do a close review of this PR in the morning. i can see you're already on the right track of using pathlib.
i'm general, i'm likely to provide some feedback suggesting that pathlib.Path instances be passed throughout the program whenever possible, so there should be as few conversions to/from str as you can. also, it may help to introduce type annotations to make the types of function arguments and return values more clear. again, i can provide more specifics in the morning.

Ok thanks for your support and feedback!
I am already working to change all the string paths used as arguments and return values (and also the type hints).
While working on main.py I noticed some functions from external libraries like viv_utils that only accept string arguments for paths, so I convertet the pathlib.Path back to a string type.
Also I noticed that there is a dataclass "Metadata" (which is in floss/results.py): should I change the argument type to Path?

Just used isort on changed files to improve code style


Missed CHANGELOG.md

this will be very helpful

@NeoLSN up this topic again because version in package.json doesn't match the versions in github releases tag list!


jasonpilz patch

Fix for "error: 'baro' was not declared in this scope" - when switching to Altimeter mode.

Change baro to sensor in both firmware example files.
Change baro to sensor in the README example.

Thanks for your input.

No problem! Thanks for your awesome libraries.


Code reorganization

Made a couple big changes:

No more args. Encoder/Decoder now take in already created input_network and output networks and a few explicit named arguments. I like this better because it is self-documenting, and forces a little pain for adding more arguments/

Encoder/Decoder no longer know about LSTMs. They know rnn size and num of effective layers. The rest is pushed to the LSTM class.

Encoder/Decoder no longer know anything about words or features. They use the Data class to get inputs, they use a generator to get outputs. Features just become a separate input network and a separate generator.

Small: Encoder backward returns gradients.

The downside of this PR is that it pushes some logic to train.lua. However I would rather try to keep encoder / decoder clean and simple.
Test plan: Running Integration test.

This looks good to me.
I isolated the model creation to a new file, did some minor cleaning and revised the model saving and loading part.
@srush If this also looks good to you, we can merge this. I'm doing more tests but the training logic should be unchanged.


[BUG] Deletion of Role/Rolebinding through kube-burner causes fatal error

Bug Description
Deletion of created Role/RoleBinding through a kube-burner job causes fatal error
Output of kube-burner version
Version: 1.10.4
Git Commit: 2b0a32be8f0b3a3df2328e4aecc9da06da742666
Build Date: 2024-07-12T19:25:04Z
Go Version: go1.21.12
OS/Arch: linux amd64
Describe the bug
Deleting Role/Rolebindings using kube-burner causes a fatal exit with the following error message
time="2024-07-23 09:33:19" level=info msg="🔥 Starting kube-burner (1.2.9@4a36d42712bd22e9308035149a3de93b33896f54) with UUID a5311366-1b07-4052-a942-a59dc20ca6ad" file="job.go:99"
time="2024-07-23 09:33:19" level=fatal msg="no matches for kind \"RoleBinding\" in group \"\"" file="delete.go:44"

To Reproduce
Steps to reproduce the behavior:

Create a Kube-burner custom workload that uses Role/Rolebindings, such as the kubectlapp workload in the templates available here
Attempt to delete the created role/rolebindings using kube-burner using a delete job such as

---
jobs:
  - name: remove-roles
    qps: 2
    burst: 2
    jobType: delete
    waitForDeletion: true
    objects:
      - kind: RoleBinding
        labelSelector: {kube-burner-job: du-workload}
      - kind: Role
        labelSelector: {kube-burner-job: du-workload}

Expected behavior
Safe deletion of role/rolebinding objects created with a kube-burner job using a template.
Only way currently to do this is to select and delete each one tediously, such as,
[kni@registry du-intensive]$ oc delete -n workload rolebinding pod-reader-binding-1
rolebinding.rbac.authorization.k8s.io "pod-reader-binding-1" deleted
[kni@registry du-intensive]$ oc delete -n workload rolebinding pod-reader-binding-2
rolebinding.rbac.authorization.k8s.io "pod-reader-binding-2" deleted

Screenshots or output
If applicable, add screenshots or kube-burner output to help explain your problem.

Hey @abraham2512 , as per the output suggests, kube-burner wasn't able to find the specified resources (Rolebinding and Role), that's expected and is because you need to configure apiVersion .
Which is the following for both resources:
apiVersion: rbac.authorization.k8s.io/v1

More info at docs https://kube-burner.github.io/kube-burner/latest/reference/configuration/#delete
Please, let me know if that solved your issue.

Hi @rsevilla87, thank you! Specifying the correct apiVersion deleted the roles/rolebindings.


improve wireless station collector

Coincides with https://github.com/ispapp/ispapp-linux-client/issues/15

ccq
per chain signal
noise

These do not exist on RouterOS:
stations[n].expected_rate       number          also known as expected throughput (@NL80211_STA_EXPECTED_THROUGHPUT)
stations[n].assoc_time          number          timestamp of station's association (@NL80211_STA_INFO_ASSOC_AT_BOOTTIME)
stations[n].beacon_loss         number          count of times beacon loss was detected (@NL80211_STA_INFO_BEACON_LOSS)

fixed https://github.com/ispapp/ispapp-routeros-client/commit/6a54ea7fbc15ecec0f6855ff0e86753377959dd9


Release 1.5.3.

Ran from
$ git log -1 --pretty=%H  # What is HEAD at time of doing "log"
9bd85220faf18349fd4ba0d4a02a1588bcf0f1f6

to check PRs since
$ git log v1.5.2..HEAD \
> | grep 'Merge pull request ' \
> | awk -F ' ' '{print $4}' \
> | sort

yields
#332
#334
#337
#346
#350
#353
#355
#356
#362
#363
#369
#370
#371
#372
#374
#375
#376
#378
#379
#380
#382
#383
#385
#389

@nathanielmanistaatgoogle Here is the summary of the PRs since the last release

#332 - Add Django util With decorator and views (also #383)
#337 - Avoid OAuth2Credentials id_token going out of sync
after a token refresh.
Moving many packages to contrib sub-package (#346, #353, #370, #375, #376, #382)
#372 - Add token_expiry to devshell credentials
#379 - Move Storage locking into a base class
#380 - Adding dictionary storage
#385 - Add to_json/from_json methods to all Credentials classes
Bugfix: Fall back to read-only credentials on EACCES errors (#389)

Project Admin: #334 (new logo), #350 (better error for failed file open), #355 (separating file/multistore_file tests), #356 (improved unit test line coverage), #362 (unpinning tox version in script), #363 (fixing broken test config), #369 (update language in README), #371 (factor out usage of utcnow() in client), #374 (more mocks in implicit environ tests), #378 (Removing keyring testing from py26 testing)

Care to craft it into valid notes?

@nathanielmanistaatgoogle The move of many modules to the contrib sub-package probably dictates we upgrade to 2.0.0.
Maybe we should hold off on doing this until #211 is resolved?

Phooey; that thought passed through my mind as we spoke today and then escaped before I gave it voice.
Happy to hold off. If we don't, we probably wind up with some intermediate release that gets barely any use and isn't worth the effort that went into it.

OK. Close this PR then?


Add files via upload

the university official website URL: https://uveg.edu.mx/
a URL of a page on the official website where a long-term (>1 year) IT related course is offered by the university: https://uveg.edu.mx/index.php/es/info-isc
The url of the web page corresponds to the url used by the email address.
Regards!

@leonelbetanzos First stage of verification passed, official domain is uveg.edu.mx as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@leonelbetanzos Thank you for your patience while waiting for a review and processing your request. Pull request merged.


Saved

You've imported into the project a whole bunch of libraries we're not using (in the .iml file). Shouldn't affect the app itself, so merging.

@aravindet They are dependencies of Android support library.


From Name field not honored when email is sent

Issue Summary
Sendgrid does not honor the 'fromname' field in the email options. Per the documentation here, https://www.twilio.com/docs/sendgrid/api/v2/mail#parameters, it is a supported field.
Steps to Reproduce
Code snippet is given below. The email is sent to the recipient but the 'fromname' field does not contain the string provided in the code snippet below.
Code Snippet
var email = {
                        to<EMAIL_ADDRESS><EMAIL_ADDRESS>                        from<EMAIL_ADDRESS>			fromname: 'Ananth Prakash',
                        subject: 'Your QRCode from RMV',
                        html : '
Hello',
                        attachments: [
                            {
                            content: attachment,
                            filename: "instructions.pdf",
                            type: "application/pdf",
                            disposition: "attachment"
                            }
                        ]
                    };
                    //SendGrid Send
                    sgMail.sendMultiple(email, function(err, json){
                        if(err) {     errorMessage = err.message;
                          renderPage = "false";
                          res.sendFile(path.join(currentDir+'/views/error.html'));
                        }```

### Exception/Log

No errors or exceptions are thrown
Technical details:

sendgrid-nodejs version: Latest
node version: 12 LTS

Changing fromname: 'Ananth Prakash' to fromName: 'Ananth Prakash' does not help either

@ananth3010 The reason this is not working as expected is due to the fact that the mail helper functions are written for the v3 API. You could craft the request yourself using @sendgrid/client,  using some of the v3 MailService code as a template.

@eshanholtz thanks for the response. As I indicated in my post, 'fromname' is supported in V2 API as well: https://www.twilio.com/docs/sendgrid/api/v2/mail#parameters,
Any pointers to how I make this work will be useful.

Hello @ananth3010,
If you are using the current version of this helper library, then the correct documentation is located here and the documentation specific to this helper library is located here.
Please let us know if those examples are not helpful.
With best reagrds,
Elmer

Closing due to inactivity.


Crash on server Start

Server won't start.
Here is the log:  https://pastebin.com/kAnqzABW

from the exception it seems the config file is corrupted. please remove it and compile the newly generated one instead
'%server_folder%/config/ServerSideReplayRecorder.yml'

You are right!
But i did have to create a new clean server and generate a config file there, then upload to the true server. Maybe one of the mods may have a incompatibility that is preventing the Config file to generate correctly.
If you want to take a look here is a list of the mods i use right now:
audioplayer-1.20.1-1.8.5.jar
autowhitelist-1.0.0-alpha.7.jar
banhammer-0.7.0+1.20.jar
carpet-extra-1.20-1.4.115.jar
cloth-config-11.1.106-fabric.jar
collective-1.20.1-7.13.jar
Dynmap-3.6-fabric-1.20.jar
extension-legacy-api-1.0.0.jar
fabric-api-0.91.0+1.20.1.jar
fabric-carpet-1.20-1.4.112+v230608.jar
fabric-language-kotlin-1.10.10+kotlin.1.9.10.jar
ferritecore-6.0.1-fabric.jar
firstjoinmessage-1.20.1-3.1.jar
itemswapper-fabric-0.5.3-mc1.20.1.jar
krypton-0.2.3.jar
ledger-1.2.8.jar
lilylib-0.1.0-beta.2.jar
lithium-fabric-mc1.20.1-0.11.2.jar
LuckPerms-Fabric-5.4.102.jar
LuckPerms-Fabric-PlaceholderAPI-Hook.jar
minimotd-fabric-mc1.20.1-2.0.13.jar
orderedplayerlist-0.1.2+1.20.1.jar
owo-lib-0.11.2+1.20.jar
placeholder-api-2.1.3+1.20.1.jar
shulkerplus-mc1.20.1-v1.0.7-fabric.jar
styled-chat-2.2.3+1.20.1.jar
styledplayerlist-3.1.1+1.20.1.jar
syncmatica-1.20.1-0.3.10.jar
vcinteraction-1.20.1-1.0.5.jar
viewdistancefix-1.20.1-1.0.0.jar
voicechat-fabric-1.20.1-2.4.18.jar
worldedit-mod-7.2.15.jar

i will look into the the problem from the Edit soon


notebook file name change doesn't reflect in open files

Issue Type: Bug
step 1: open a jupyter notebook.
step 2: change its filename from sidebar (explorer)
step 3: I expect the opened notebook reflect this change, but it doesn not.
Extension version: 2020.7.96456
VS Code version: Code 1.47.3 (91899dcef7b8110878ea59626991a18c8a6a1b3e, 2020-07-23T13:08:29.692Z)
OS version: Darwin x64 19.6.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz (16 x 2400)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
3, 3, 3

Memory (System)
64.00GB (25.77GB free)

Process Argv

Screen Reader
no

VM
0%

Thanks for your feedback. This issue will likely be addressed once VS Code adds native support for editing notebooks. Please see https://github.com/microsoft/vscode/issues/91987.


[BEAM-12873] Revert "[BEAM-11205] Upgrading the Libraries BOM to v22"

This reverts commit 9694f70df1447e96684b665279679edafec13a0c.
Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Run Java Postcommit

Run Java Postcommit

Run Java Postcommit


[REQUEST] Read only "my activity" room

I'm curious @Shailesh351 and @rafaelks what you think about having a read only "news feed" room that shows all active chats in a single room with the ability to click a #roomname link to go to that room. This gives the user the ability to monitor activity in a single room and not have to click around to see all the recent activity he/she may be interested in. On mobile in particular its convenient to only have to monitor one place. Maybe instead of "news feed" it would be called "my activity"?

@bizzbyster Please, move your feature request to our forums: https://forums.rocket.chat/c/feature-requests.


Stripe Payment

Your branch has merge conflicts.

Your branch has merge conflicts. Fix them

I don't know why its showing conflicts, I have just written code, I didn't install any extra packages !


Update for new bevy breaking changes

This fixes recent breakage and makes all examples work again.

Updated this for additional breaking changes.
Note: svg example is currently broken and I'm not sure if it's a bevy issue yet or if it needs to be fixed up here. See https://github.com/bevyengine/bevy/issues/5334.


Not working on Android

Hi! 👋
Firstly, thanks for your work on this project! 🙂
We implemented it and it works great on iOS, but on Android we got the next error:
TypeError: null is not an object (evaluating 'RARoutePickerContext.showRoutePicker')

We got it to work by removing all code related to showRoutePicker.

Thanks for the report, I'll have this fixed sometime over this weekend.


Smartplay + Source select players for seren

Two player files for the latest version of Seren which allow Source Select or Auto Play for both TV and MOVIES (currently only autoplay for movies is available).
Source Select for movies requires the mediatype to be omitted, otherwise it defaults to TV shows for some reason and then reports no playable sources.
Autoplay for TV and Movies works fine with either of the current player files, but i have named mine individually for easier identification.

There is a difference between "Smart Play" (it actually isn't even called this anymore... though it was on early alpha builds of Seren. It's now called "Auto Playlist Creation".) and "Auto Play".
Ideally, we would have a handful of players:

Source Select
Auto Play
Source Select w/ Smart Play
Auto Play w/ Smart Play

The "Smart Play" players would really only apply to TV shows, since that feature doesn't do anything for movies.
Last time @rickdoesxmas uploaded similar players, they were broken, and only respected the settings that were set inside Seren, rather than what the URI in the player should've accomplished.
If you can figure out how to have those players work correctly for each type of content, and for them to override the settings from Seren, I'll merge this.

Ahh right, although im confused about what the difference between Auto Play and Auto Play with Smart Play would actually be (and similarly the two source select options).
There is another method: RunPlugin(plugin://plugin.video.%s?action=buildPlaylistWorkaround&actionArgs=%s)
Could that be the option  for movies that dont need a playlist?
What options is Seren ignoring? Because playing with source select and the mediatype removed for movies things play ok for me (there is an issue with cloud files but ive issued a separate pull request for that).
And for Autoplay for movies it seems to work ok too.
So if they work for TV/Episodes and they work for movies then surely they are working?
I got the fix implemented on my system but I thought other would want this too.

I'll test these players and see if they're working as expected.
For TV Shows, there are truly four ways to play:
With Auto Play (but not Smart Play), Seren will play one episode, skipping Source Select. With Auto Play and Smart Play, it will continue in to the next episode, again skipping Source Select.
With Source Select (but no Smart Play), it should play one episode, and show the sources. With Source Select and Smart Play, it should continue to the next episode, showing sources each time.
In all of these scenarios, it would ideally ignore any of Seren's settings regarding Auto Play/Source Select and Smart Play, and only pay attention to the arguments passed with the player.

Ahh. Having had that explained I couldn't really say whether or not it's truly working then. I've got various next up things which are likely to try and kick in. Open meta, Seren, Realizer, the actual up next add-on which the skin uses too I think.
So while everything seems to be working for me I wasn't checking all those ins and outs.
I'll be interested to know if it is actually working like that now

Any chance this will get merged at some point?

@fugkco Given that OpenMeta is essentially abandoned at this point, I don't think anyone has actually tested the players regarding the points previously discussed.

I have added "Source Select" players for TMDbHelper in the corresponding branch.


Error on parsing ExportNamedDeclaration

Subject of the issue
/Users/JounQin/Workspaces/Local/test/node_modules/micromark-extension-mdxjs-esm/index.js:138
        throw new VMessage(
        ^
[5:1: Could not parse import/exports with acorn: SyntaxError: Unexpected character '#'] {
  reason: "Could not parse import/exports with acorn: SyntaxError: Unexpected character '#'",
  line: 5,
  column: 1,
  location: { start: { line: 5, column: 1 }, end: { line: null, column: null } },
  source: 'micromark-extension-mdxjs-esm',
  ruleId: 'acorn'
}

Your environment

OS: macOS Big Sur 11.1
Packages<EMAIL_ADDRESS>Env: node v12.20.0

Steps to reproduce
import React from "react";

export { React };

# MDX

Expected behavior
No error
Actual behavior
Error

Besides, if we only have the following
import React from "react";

export { React };

Another error is thrown:
/Users/JounQin/Workspaces/Local/test/node_modules/micromark/dist/util/slice-chunks.js:11
    view = [chunks[startIndex].slice(startBufferIndex, endBufferIndex)]
                               ^

TypeError: Cannot read property 'slice' of null
    at sliceChunks (/Users/JounQin/Workspaces/Local/test/node_modules/micromark/dist/util/slice-chunks.js:11:32)
    at sliceStream (/Users/JounQin/Workspaces/Local/test/node_modules/micromark/dist/util/create-tokenizer.js:89:12)
    at Object.sliceSerialize (/Users/JounQin/Workspaces/Local/test/node_modules/micromark/dist/util/create-tokenizer.js:85:28)
    at atEnd (/Users/JounQin/Workspaces/Local/test/node_modules/micromark-extension-mdxjs-esm/index.js:123:24)
    at rest (/Users/JounQin/Workspaces/Local/test/node_modules/micromark-extension-mdxjs-esm/index.js:86:16)
    at lineStart (/Users/JounQin/Workspaces/Local/test/node_modules/micromark-extension-mdxjs-esm/index.js:111:14)
    at go (/Users/JounQin/Workspaces/Local/test/node_modules/micromark/dist/util/create-tokenizer.js:136:13)
    at main (/Users/JounQin/Workspaces/Local/test/node_modules/micromark/dist/util/create-tokenizer.js:130:9)
    at Object.write (/Users/JounQin/Workspaces/Local/test/node_modules/micromark/dist/util/create-tokenizer.js:70:5)
    at exitContainers (/Users/JounQin/Workspaces/Local/test/node_modules/micromark/dist/initialize/document.js:126:17)

Huh, looks weird that this is happening (there are a ton of tests). Could you post the code you're using to run this / their versions too? Or attaxh the mdx sample as a file instead (maybe line endings is the problem?)

I’m now getting, for: import a from "b";\n\nexport {a};\n\nc, the error: "Could not parse import/exports with acorn: SyntaxError: Export 'a' is not defined".
I guess acorn is failing because I’m parsing them separately. And the second is failing because it doesn’t “know” there was an a imported before.
But this is still a different error from what you’re seeing

My testing code, all installed latest.
const fs = require("fs");

const fromMarkdown = require("mdast-util-from-markdown");
const toHast = require("mdast-util-to-hast");
const mdxFromMarkdown = require("mdast-util-mdx").fromMarkdown;
const mdxjs = require("micromark-extension-mdxjs");
const toEstree = require("hast-util-to-estree");

const doc = fs.readFileSync("./test.mdx", "utf8");

const mdast = fromMarkdown(doc, {
  extensions: [mdxjs()],
  mdastExtensions: [mdxFromMarkdown],
});

const hast = toHast(mdast, {
  passThrough: [
    "mdxFlowExpression",
    "mdxJsxFlowElement",
    "mdxJsxTextElement",
    "mdxTextExpression",
    "mdxjsEsm",
  ],
});

fs.writeFileSync("./test.json", JSON.stringify(toEstree(hast), null, 2));

Thanks for that repro! Removing the blank line between the import/export for now works.
Weird stuff!

Fixed!


Kiota should have a developer-friendly way of providing auth information in the VS Code extension

As part of calling authenticated APIs, one can provide auth information as part of the plugin manifest so Copilot can know how to call the API.
Kiota should identify the auth information from the OpenAPI description and create the right thing (https://github.com/microsoft/kiota/issues/5070).
Things to consider:
1 - Not all OpenAPI descriptions have security information
2 - Some APIs do not need authentication (either for some endpoints or all endpoints)
3 - Providing auth information in the plugin manifest is not required (because of the 2nd point mentioned above)
So, Kiota VS Code extension should have a developer-friendly way of adding/providing the auth info different from adding the information editing the manifest file manually.
Acceptance Criteria:

Kiota VS Code extension will offer a new action (CTRL+SHIFT+P) "Add authentication registration info"
When user triggers the new action, we do open in the quick picker 2 questions: "What's the auth type" and "What's the reference-id"
Once the user confirmed the input for both questions, new auth object will be generated in the plugin manifest, following the structure as defined in #5070.
If the user triggers the action for a plugin manifest which already contains the auth object, it will be overwritten with the new values.

@maisarissi Can you please provide more information?

@baywet I thought I had added descriptions for all new issues. This is fixed now.
Not sure though how to give developers a way of adding the auto info from the extension in a way that relates to their journey.
Any thoughts?

Kiota needs to understand the auth scheme of all APIs, anyways. In the future, we will want to auto-gen and scaffold some level of auth code. So this would be useful in larger scenarios.
Now, for Copilot specifically, there are requirements (reference ids, types, etc.) that will be required. If we start adding tons of switches, I feel we are going backwards and are not respecting our goal of being as simple as possible.
Any thoughts @baywet @andrueastman?

Hey @sebastienlevert , this is about the extension. The CLI discussion is over here: https://github.com/microsoft/kiota/issues/5072

Overall I'm not clear on the experience to start with, and this is why I have asked a bunch of questions to attempt clarifying it in #5072.
I don't think we want to be in the business of "storing additional information that's missing in the OAS description". And that's regardless of whether we're talking about Auth information, the AI OAS extensions, etc... We talked about overlays for that. People can also create a copy of the description and locally edit it in the meantime etc...
Here is the main reason why I don't want us to be building those kind of experiences. Imagine that we built a fancy user experience to set your token endpoint, your consent endpoint, and all the other information that's required for an OAuth2 flow.
Now we will additionally need to build user experiences to tie that information to any specific operation so we can later on identify the given operation needs that information to be exported for the plugin.
And even if you built all that additional user experience we now need to reflect it in the CLI which will be complex and convoluted and we also need to store that information somewhere so we can retrieve it during updates and other scenarios like those.
Not only this represents a ton of user experience to build but it also does not Denver agreed user experience at the end of the day especially in the CLI context.

That's why we are not getting into the business of providing auth registration. This is TDP responsibility. Kiota should only provide a way for folks to provide the type and the reference-id.
I think we shouldn't have block users of creating plugins for OpenAPI descriptions with no auth requirements and we should let them provide the auth type and reference-id to be automatically added to the plugin manifest rather than adding the "none" default version and requiring users to manually edit the json file.

No worries, I'm just trying to make sure we have a common understanding and enough information to implement things properly here.
Have you thought about additional questions in the generate copilot plugin sequence?
If we don't detect any authentication configuration for the operation, we don't ask them.
If we do, we prompt the user.
If we're refreshing an existing plugin, and the questions have already been answered, we skip them as well I guess?
Are there default placeholders we could use?
Or do we need to ask any of that at all since we're already established in #5070 that we can compute that information from the description?

Thanks for seeking all clarity needed before doing the work!
So, I thought about asking additional question, here are my thoughts:

When the auth info is provided in the OpenAPI description, we shouldn't ask them any additional questions
When there is no auth in the OpenAPI description we have 2 scenarios:

The OpenAPI doesn't require authentication (so generating the auth None is what we should do)
The OpenAPI description is missing the auth info but authenticating is necessary.
In the second option above, we would like to give users a way of providing the type and reference-id, so we can create the right thing automatically for them, rather than asking them to go and edit the json file manually.

Adding a new action (CTRL+SHIFT+P) is something one would be used to do it to add something like that?
Having a new Kiota: add authentication registration info (or something like that)

And by doing that, we do open in the quick picker 2 questions like "What's the auth type" and "What's the reference-id"?

How would people know they need to do this at this point? is the editing experience of the plugin something we could leave to TTK instead?
I'm a bit worried this will lead to a disjoint experience, but not strictly opposed to it.

We definitely want to provide a good editing experience in Kiota. Kiota helps one to maintain their plugin by editing paths, re-generating, or in this case, providing a nice way to adding auth when the OpenAPI description doesn't have the info.
The only reason I said we might want to add a new action is that we don't want to bother people by asking auth info when the API they are creating a plugin for, don't require authentication.
In the CLI, we can easily fix that by providing 2 switchers where one can provide the info. In VS Code, we need to be careful to not add unnecessary friction and asking more 2 questions (type and reference-id).
We can provide that info through docs, saying that one might manually edit the json file or use the "action".
I'm also open to other ideas on how we can make this experience better.

@maisarissi Agree with the AC as defined above?

@petrhollayms yes, agree. My only concern is to know to which plugin manifest the auth object should be applied to.
Today, there is a constraint that there is only 1 plugin per app, however, this will be worked out.
So when there is more than 1 plugin manifest, how can we ensure they are applying to the right thing?
Should we ask them to select the plugin manifest? Is there a way for us to list in the quick pick all plugin manifest available in the workspace?

@thewahome Can we ask the user a question about the manifest to use if there is more than one, with the list of all manifests in the workspace? See ^^^


New endpoint for Pay: GET /sapi/v1/pay/transactions to support user query Pay trade history

Change Log 2021-11-19
GET  {{url}}/sapi/v1/pay/transactions?timestamp={{timestamp}}&signature={{signature}}
Not Found Fields: [
Pay ID ?
recipient ?
sender ?
orderId ?
note ?
]
Example Response:
{
"code": "000000",
"message": "success",
"data": [
{
"orderType": "C2C",
"transactionId": "C_P_XXXXX",
"transactionTime":<PHONE_NUMBER>055,
"amount": "236.6",
"currency": "USDT",
"fundsDetail": [
{
"currency": "USDT",
"amount": "236.6"
}
]
}
],
"success": true
}

what do you mean? where did you find those fields? not in the API document.

I can't find sender or recipient information.

what do you mean? where did you find those fields? not in the API document.

I can't find sender or recipient information.

The endpoint is not intended to return the mentioned fields.
Consult the documentation for the response schema
https://binance-docs.github.io/apidocs/spot/en/#get-pay-trade-history-user_data


Fix #issue126, fm612xWriteRegister usage only ESP32 platform

The library does not compile under the platform esp8266, this commit solves this problem.  Function fm612xWriteRegister usage only ESP32 platform.

Fixed in latest master ... thanks


Bug: Retrieval error on the first try

Upon booting any version I sometimes get an error retrieving assets from a contract with an associated message. After refreshing, the issue resolves.

Resolved via a gateway change. Will close for now, and add notes on retrieval error handling in the future and messaging.


Named-based schema matching between table and partitions

Backport of #37
This change allows the possibility of using names to match schemas between a partition and a table and patches parquet implementation to make it compatible with it. This behavior is disabled by default and needs the usage of a configuration variable. This has only be tested with parquet datasets.
The set of changes is the following:

Add a new behavior to the StructConverter to allow matching by name instead of by index. The activation of this behavior is done through a configuration variable, so the ObjectInspectorConverters API has been changed to allow the passing of the config.
Modify the ParquetHiveSerDe to shape the data coming from the reader with the schema of the partition, as this is expected by the converter in the operator.

Co-authored-by: Miguel Liroz<EMAIL_ADDRESS>

The PR message makes reference to the initial patch and so it is outdated:

We only need one variable
The parquet reader has not been modified but the serde

You can actually be based on the message of the second patch (the one you reference) for more clarity.
Other than that it LGTM

The PR message makes reference to the initial patch and so it is outdated:

We only need one variable
The parquet reader has not been modified but the serde

You can actually be based on the message of the second patch (the one you reference) for more clarity.
Other than that it LGTM

Done, I used the PR message from https://github.com/criteo-forks/hive/pull/37


Add UUID to request logging

Currently logs look like
.c.l.LoggingClient                  : Request: {startTime=2019-08-17T12:39:19.994Z(1566045559994257), length=4970KiB(5089733B), duration=6198?s(6198300ns), scheme=none+h1c, headers=[]}
zipkin                      | 2019-08-17 12:39:20.117  WARN 1 --- [orker-epoll-2-4] c.l.a.c.l.LoggingClient                  : Response: {startTime=2019-08-17T12:39:20.117Z(1566045560117742), length=0B, duration=0ns, cause=com.linecorp.armeria.client.ResponseTimeoutException, headers=[]}

It would be useful, and probably simple, to assign a UUID to every request to add to the log to be able to associate requests and responses. Many users will be setting trace IDs that would perform similar utility, but not all of them and I think there's very little cost even if it ends up performing double-purpose.

We need to update:

RequestContext.newDerivedContext() to accept a new UUID
RequestContext.toString() to return a nicely formatted string which includes the last few digits of the UUID.


Problem installing sasl

Make sure these boxes are checked before submitting your issue - thank you!

[x ] I have checked the superset logs for python stacktraces and included it here as text if any
[ x] I have reproduced the issue with at least the latest released version of superset
[ x] I have checked the issue tracker for the same issue and I haven't found one similar
Receiving the following error when attempting to install:
"Command "/usr/bin/python2.7 -u -c "import setuptools, tokenize;file='/tmp/pip-build-enrh6u/sasl/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" install --record /tmp/pip-qb9oVE-record/install-record.txt --single-version-externally-managed --compile" failed with error code 1 in /tmp/pip-build-enrh6u/sasl/"

Superset version
superset-0.23.2
setuptools-38.5.2
pip-9.0.1
sasl-0.2.1
python 2.7
OS: solaris 2.11
Expected results
Successful installation
Actual results
'cc' command failed with exit status 1
Steps to reproduce
python setup.py install
or
pip install sasl==0.2.1

Solaris 2.11 ... 1993 version? Seems quite old...
If instead is Solaris 11, maybe try to install sasl_dev package from here: https://www.opencsw.org/packages/sasl_dev/
The dependencies are listed here: https://superset.incubator.apache.org/installation.html#os-dependencies.
Try to find the equivalent package for your OS.


GPU at 0% util throughout training process

I am training a set of images (size of each image is 1000,3000) with a Tesla P-100 GPU which has 16GB of memory. The machine also has 10 cores and 32GB of memory.
Training on this machine is extremely slow (i.e. every epoch taking around 4 hours). Further analysis shows that the GPU utilisation is continuously at 0% as per screenshot below (albeit installing tensorflow-gpu).

Is this a problem of batch_size? If so how can I update it?

The same. CUDA failed because of out of memory. So GPU is not used while it runs on the simple CNNs like that is dealing with Fashion-MNIST dataset (GPU was 32% busy then). So my CUDA, cudNN, tf and keras version are compatible and can work good.
But not in this case.
Following recommendations in this repo, I reduced number of ROIs from 32 to 16 and image size from 600 to 400. It doesn't help. Suggestions?


Demo not working in IE 11

From @Compufreak345 on December 9, 2015 12:45
It seems like a recent update broke Polymer for IE11 - my own project does not load anymore and also the demos seem to have issues.
One example :
https://elements.polymer-project.org/elements/paper-badge?view=demo:demo/index.html&active=paper-badge

Copied from original issue: Polymer/polymer#3180

From @lismore on December 10, 2015 10:52
I have been having issues with IE this last two days,  I found a solution that works for me,  maybe the feedback can help in a fix.
I have a dom-module custom element that loads in a partial view (.NET MVC View) through jquery.  However IE 11 and < 11 it would not load at all, no matter what I tried.
In the end I found that I had to wrap the jquery call in a setTimeout for it to wait until polymer custom element had loaded. Even though on screen it was visually there.  I found I had to do this in a few custom elements so it would work in IE.
Not sure if this is a polymer issue or IE.  At least now I know what to look for.
setTimeout(function() {

            // load the partial section
            jQuery(".partial-view").each(function (index, item) {
                var url = jQuery(item).data("url");
                if (url && url.length > 0) {
                    jQuery(item).load(url);
                }
            });

        }, 2000);

From @Compufreak345 on December 11, 2015 13:54
FYI: I fixed my own issues by updating webcomponentsjs (for some reason my bower did not update it with a normal bower update) - the demo still does not load in IE11.

There's a PR out to fix iron-demo-helpers on IE: https://github.com/PolymerElements/iron-demo-helpers/pull/3


fix(run): Correctly set up vars for run

There were the following issues with your Pull Request

Commit: 88f05d9f6f33cd6ad95471c79eef7a64544dcf5e
Your commit message does not contain a body

Guidelines are available at https://github.com/fabric8io/fabric8-ui

This message was auto-generated by https://gitcop.com


Transform this resource Gallery 🎉

Thinking of shipping the current resource gallery on a fully responsive website by using site generators and themes of Hugo or Astro.
doks theme and astroship theme
If you are interested to contribute, you are welcome🙏🏼
New website codes will be hosted here: make pull requests after changes.
What will be added:

More resources
Blogs
Programs

hi @Astrodevil I'd like to contribute to this issue. can you please assign me this issue.
thank you

hi @Astrodevil I'd like to contribute to this issue. can you please assign me this issue. thank you

Please see generated one try to improve it or go according to your choice to choose between two themes as mentioned above.

Need to work on resource and quick links section

Take docs, orientation, cards, navs suggestions from here. This website has various theme layouts that can be used in our project to improve.

@TonyBhargav  Any update?


GUVNOR-2297,RHBPMS-4118 - 'SAXParseException; Premature end of file' due to incorrect encoding

@mswiderski If you could merge, when you get a chance. Thanks.

+1 to merge


use .erb instead of .html in widget views

Hi!
Just wondering is it possible to use ERB template engine instead of pure html widget views?
If not, maybe it is a good feture to implement in future?
Thanks
Nikolay

You could send each peer to a different event ID (in my examples, "peer-#{peer.name}"). Then go back to using the data-foreach-peer approach, but make the ID of each element dynamic (like this: data-id="peer- | append peer.name").
You can also loop over your configuration data when dashing starts to run the Rufus jobs in parallel, so that the widgets would update independently.


python3.6

hi
can you update your python versionto 3.6 ?

I'm working on it now. Also it was developed using tf v1, so you need to use compatibility version of it with tf 2, i.e. import tensorflow.compat.v1 as tf.

Any luck with newer version of python? I'm unable to get it working with python3.7.
Thanks

@parsibox @tarasyarema @alimohyudin
Hi guys.
I did make a fork and my fork is working well with Python 3.10, TF 2.10.0, NP 1.23.4 except "multi GPU" that I am workkinng on it.
I hope it can be helpful.

@parsibox @tarasyarema @alimohyudin Hi guys. I did make a fork and my fork is working well with Python 3.10, TF 2.10.0, NP 1.23.4 except "multi GPU" that I am workkinng on it. I hope it can be helpful.

hi dear i can not find your new fork
can you send that link?

@parsibox
Hi budy
It is: https://github.com/SecurityEnthusiast/captcha-recognizer


feat: strip symbols and enable LTO

Strips symbols from the release build and enables LTO, which results in some reduction in size of the binary.
i've not been around rust in some time so this may be absolute nonsense. if so, feel free to close
as far as i can tell, stripping symbols/debug info is a no-brainer, but LTO can reduce performance in some cases. although the benchmark seemed the same or better locally
i feel like there will be other big savings to have too (without affecting perf), but i need to read up on this stuff more.  if you have any ideas, please do let me know and im happy to try them out

Oh yes! I totally forgot about the napi version requires these, thank you!

Thank you, this reduced the binary size from 1.38 MB to 705 kB, and faster too!


[App] cannot view logged video in run stats

Describe the bug
Video file type is not recognized correctly
To Reproduce
Steps to reproduce the behavior:

Log a video using
wandb.log( {"video": wandb.Video(numpy_array_or_path_to_video, fps=4, format="gif")})
Go to run>files>Media on the browser

Expected behavior
Expected to see the .mp4 video
Screenshots

Operating System

OS: Ubuntu
Browser: Chrome

Additional context
When I download and play the logged file it plays correctly.

Hi @cvphelps, any idea when will this be fixed?

@NotAnyMike, it looks like you're logging an "mp4" video but telling us it's a "gif" video.  Can you try logging with format="mp4" instead of format="gif"?

It was a typo, we are using format="mp4"

How are you generating the mp4?  Can you share a link to the problematic run?  We're just using an HTML5 video tag in our web page.  If the mp4 was generated with a codec that modern browsers don't support it won't be able to play it.  A table of browsers and what codecs are supported can be found here.

We are using opencv to generate the video, save it in disk and pass the path to wandb. The codec we use is cv2.VideoWriter_fourcc(*'MP4V') or mp4v.

@vanpelt thank you, if we change the encoding to libx264 it works,. Looks like mp4v does not work well with HTML5 video tag. Thank you. I think it is save to close this issue.

Reopening this issue because I got the same error when logging an mp4 video from slurm. When I log the video locally I can play it on Google chrome, but not on mozilla for example. I save the video as mp4 with imageio and upload it with the format specified as mp4. Any tips?

fourcc = cv2.VideoWriter_fourcc(*"avc1")  # Codec for .mp4 file format video_writer = cv2.VideoWriter(save_path, fourcc, FPS, (width, height))
Opencv with acv1 for extension '.mp4' works for me to log the video into wandb, mp4v doesn't work


Override GHC options

Synopsis:
Ensuring cabal2nix version is >= 2.2.1 ...
Ensuring git version is >= 2 ...
Ensuring cabal version is >= 1 ...
stack2nix: stack's Nix integration is incompatible with '--no-system-ghc'. Please use '--system-ghc' or disable the Nix integration.

Make Stack ignore GHC options. I don't know how it happens in stack2nix, but this should be equivalent to stack --system-ghc --no-install-ghc.

@ip1981 what is the contents of stack.yaml?

It includes these lines:
install-ghc: true
system-ghc: false


Cryptocurrency Wallet

Description
This is a simple Cryptocurrency wallet made with the help of python and its associate libraries and PubNub for the api calls. In this project it is shown how a cryptocurrency wallet keep track od the user transaction and this total project is build on the basis of Blockchain where the mining is happening and the time is dynamically adjusted with mean time of 4sec/ transaction speed. If sometime the transaction time is increased due to comparatively easy Proof Of Work (PoW) to agree to the consensus in the next transaction the complexity is increased by 1 zero(0) in front the Nonce. The program is build in such a way that it can simulate real life Blockchain ledger keeping by updating the ledger to each and every Node of the Network. In this program also a new instance of the current blockchain can be created and from that instance blocks can be mined and transactions can be made.
Fixes #771
Have you read the Contributing Guidelines on Pull Requests?

[x] Yes
[ ] No

Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)
[ ] This change requires a documentation update

Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have created a helpful and easy to understand README.md
[x] My documentation follows Template for README.md
[x] My changes generate no new warnings
[x] I have added tests/screenshots(if any) that prove my fix is effective or that my feature works.

Sir, what do I do now?

@kaustubhgupta Agreed, @Arnab11917676 the project should have a small scope. This is a full fledged project

@Arnab11917676 If you can reduce the functions of this project to some specific scripts only then we can give you 2-3 days for  that else we need to close this PR and issue

Okey sir this was a cryptocurrency wallet I don't want to reduce the functions. You can close the issue now..
Thank you sir


Update aws.md with information on SG

Proposed changes
Improved documentation regarding AWS security groups with information about how ports are opened.
Unreleased project version (optional)

Related issues (optional)
Closes #8956

Deploy preview for docsdocker ready!
Built with commit a45a94160eeea0e36500be962dd956b9e99fac26
https://deploy-preview-8957--docsdocker.netlify.com

What's the status on this?


mytetra: init at 1.42.2

Motivation for this change
Add notes manager
Things done

[x] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] Linux

[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

When I put PNG icon, it works, but not the SVG. @ttuegel please help! :) wrapQtProgram doesn't make any change.

You still need wrapQtProgram or your users will get segfaults randomly.
I see you did include qtsvg, but is the .pro linking against it? If the PNG works, but not the SVG, that suggests qmake is building the PNG into the executable by mistake; you can check the .pro for that too, I believe.

@ttuegel Thank you! It's linking:
$ ldd bin/mytetra | grep -i svg
        libQt5Svg.so.5 => /nix/store/mr1l6i5wnvi1jlnm5f439jxyx51lcmfn-qt-5.7.1/lib/libQt5Svg.so.5 (0x00007f7700c39000)

Also this program uses a lot of svg icons in the UI, they are rendered correctly. But tray icon is not visible - again svg is used for that, if I swap it with other format like png - then tray icon becomes visible

But tray icon is not visible - again svg is used for that, if I swap it with other format like png - then tray icon becomes visible

What tray are you using? It might not support SVG icons. In any case, it doesn't sound like a problem on the Qt side, if the rest of the SVG icons render correctly.

@ttuegel Standard KDE Plasma 5 tray

@ttuegel
Most other programs use either png icon for tray or QSvgRenderer
To keep things simple, I'll just make it use png icon and mark this PR as ready
Thanks

it's ready. up

bump


POST variables not serializing properly

The request payload of when using POST method passes variables as JSON string rather than object.
Expected
{
  "query": "mutation UpsertCustomer...",
  "variables": {
    "homepolish_id": 421,
    "input":{ "age": 36 }
  },
  "operationName":"UpsertCustomer"
}

Actual
{
  "query": "mutation UpsertCustomer...",
  "variables": "{"homepolish_id": 421, "input": {"age": 36}}",
  "operationName": "UpsertCustomer"
}

This is a major issue. It makes GraphQL IDE.app completely useless for any queries that include variables.

I guess not completely useless. It turns out GET works. I was told to use POST with our GraphQL server but apparently that's not actually a requirement.

The following diff appears to fix the bug:
diff --git a/src/app/components/project-detail/project-detail.jsx b/src/app/components/project-detail/project-detail.jsx
index 223b2c4..c923713 100644
--- a/src/app/components/project-detail/project-detail.jsx
+++ b/src/app/components/project-detail/project-detail.jsx
@@ -509,6 +509,17 @@ export default ({store, actionCreators, selectors, queries, factories, history,
                 return
             }

+            let queryVariables = null
+            try {
+                const variablesStr = query.get('variables')
+                if (variablesStr != '') {
+                    queryVariables = JSON.parse(variablesStr)
+                }
+            } catch (e) {
+                swal("Error", "The query variables are not valid JSON.", "error")
+                return
+            }
+
             const startTime = moment()

             this.props.tabsUpdate({
@@ -535,7 +546,7 @@ export default ({store, actionCreators, selectors, queries, factories, history,
                 params: {
                     query: query.get('query'),
                     operationName: query.get('operationName'),
-                    variables: query.get('variables')
+                    variables: queryVariables
                 }
             })

Unfortunately for me this app is useless because of this bug.

Any update on this issue?


Run dep ensure after initialization

Codecov Report

Merging #6 into master will decrease coverage by 0.58%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master      #6      +/-   ##
=========================================
- Coverage    8.46%   7.87%   -0.59%
=========================================
  Files          26      27       +1
  Lines         709     762      +53
=========================================
  Hits           60      60
- Misses        645     698      +53
  Partials        4       4

Impacted Files
Coverage Δ

pkg/grapicmd/cmd/init.go
0% <0%> (ø)
:arrow_up:

pkg/grapicmd/project/creator.go
0% <0%> (ø)

pkg/grapicmd/generate/generator.go
0% <0%> (ø)
:arrow_up:

pkg/grapicmd/cmd/generate.go
0% <0%> (ø)
:arrow_up:

pkg/grapicmd/ui/ui.go
21.27% <0%> (-7.3%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2d7f505...98a87d0. Read the comment docs.


Get listed on FMI tools page

I would like to encourage you to get FMIExchange listed on the FMI tools page https://fmi-standard.org/tools/, see https://github.com/modelica/fmi-standard.org/blob/main/CONTRIBUTING.md#updating-the-tools-list for more information

Thanks for reaching out. Expect a PR soon


Allow skipping .gitignore generation

💡 Feature description
Since implementing self-.gitignore generation in https://github.com/rustwasm/wasm-pack/issues/473, I've come across few codebases that prefer not to publish npm artifacts elsewhere nor integrate Rust build into their build process, but keep any artifacts in the Git repo.
I suggest adding --no-gitignore option for such usecases.
Alternative
Since in such cases module is not intended to be published anywhere, another alternative could be to implement this (omit .gitignore) as part of --no-pack implementation proposed here https://github.com/rustwasm/wasm-pack/issues/691.
cc @ashleygwilliams

Actually... I realised that this is easily worked around by using one-off git add --force pkg/... and it's even better because you can selectively include only files you need in the repo (e.g. omit package.json or .d.ts).

I still think this would be nice to have; came here to post the same thing.

--force is kinda icky, .gitignore lives in a repository to codify these things for a reason. Skipping the generation of this file entirely scales better for multiple collaborators and teams because the appropriate information exists at rest.

I ran into this issue when trying to publish a wrapper around the generated wasm-pack output.
src/index.ts imports ../pkg. I want to package both src and pkg into an npm package and publish it. However, bun sees the .gitignore file in pkg and skips adding it to the artifact, despite files: [ "pkg", "src" ].
$ bun pm pack --verbose
ignore [.gitignore:*] pkg/moq_web.d.ts
ignore [.gitignore:*] pkg/README.md
ignore [.gitignore:*] pkg/.gitignore
ignore [.gitignore:*] pkg/moq_web.js
ignore [.gitignore:*] pkg/moq_web_bg.js
ignore [.gitignore:*] pkg/moq_web_bg.wasm

I accidentally published a few broken versions, oops. My current work-around is to rm pkg/.gitignore after running wasm-pack.


Using method jsonify on the "Dot" inside a range .Pages errors in a stack overflow

hugo version v0.82.1+extended darwin/amd64
Does this issue reproduce with the latest release?
Yes
Error replication
layouts/_default/list.html
{{ define "main" }}
  {{ range .Pages }}
    {{ . | jsonify }}
  {{ end }}
{{ end }}

This fails and crashes in a stack overflow.

So, this is effectively https://github.com/golang/go/issues/10769
https://github.com/golang/go/issues/40745
I did some work on limiting the JSON output from Page and Site to prevent/limit this, but as you found out, there still is possible to end up in a cycle.
My current recommendation would be to not use ´jsonifyfor the entirePageobject -- if you need JSON, create a new data structure withdict´ with the fields you want, then use jsonify on that.

Thank you for this reply. I was looking to utilize some maybe lesser known data to show on my shiny new custom list page, and was curious what all was available for me. Curiosity, it seems, lead to my computer to becoming a new (intel) cookware device.
I'll take a look at the Page object. I'm not blocked by not having jsonify. Many thanks for your hard work!

I notice that we do have a test for this -- if your site source is available online, I would love to have a look.

The code I'm working on it currently closed source and internal. Would it be helpful if I spun something up new to recreate the issue?


CIFS pod volumes

Story
-As a cluster admin, I want to attach CIFS volumes to pods in order to migrate existing applications to Kubernetes.
Resources

Initial Github issue;
smb-csi-driver;

Closed for now as won't do. Will potentially rediscover in the future.


String harmonics 4th - sounding pitch can't handle SMuFL fonts

Great script, but displays the wrong character for the string harmonic (diamond) if run in a Finale document that has SMuFL for the notation font.

Please confirm you have the latest version of the script.

From the code, it is version 0.1. I had contacted the author several months ago and was told it was not yet updated for SMuFL.

On Dec 21, 2022, at 4:36 PM, rpatters1 @.***> wrote:
Please confirm you have the latest version of the script.
—
Reply to this email directly, view it on GitHub https://github.com/finale-lua/lua-scripts/issues/388#issuecomment-1362113774, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFI4IHVZF5M2HFUD2ZRJZYLWONZ7DANCNFSM6AAAAAATF7ZYQM.
You are receiving this because you authored the thread.

Idk if the version number number was updated, but the script was updated for SMuFL several months ago. Please download it again and see if the problem persists.

Thanks. Will do and let you know.

The updated script works. Thanks. I had relied on the author for an update and should have looked here.

closing as resolved


PopoverService: Improve performance

Description
Fixes: https://github.com/MudBlazor/MudBlazor/issues/7700
Fixes: https://github.com/MudBlazor/MudBlazor/discussions/7434
Old popover system is trying to initialize (connect) popover only once in OnAfterRenderAsync
https://github.com/MudBlazor/MudBlazor/blob/748f2dd393079caf66d0789cb02ec1fefe0a1b2e/src/MudBlazor/Components/Popover/MudPopoverBase.cs#L110
While new popover system will try to do it every time in the UpdatePopoverAsync
https://github.com/MudBlazor/MudBlazor/blob/748f2dd393079caf66d0789cb02ec1fefe0a1b2e/src/MudBlazor/Services/Popover/PopoverService.cs#L115
This was done to make codebase easier and not call the initialize explicitly but let service handle it automatically and have only few simple methods to work with, unfortunately we don't always early exit from the first if-case when this method is called multiples times asynchronously and we get blocked by the semaphore and exit only in second if-case. This is why this is only noticeable during page load phase https://github.com/MudBlazor/MudBlazor/discussions/7434#discussioncomment-6846013, once each popover is connected there will be early exit in the InitializePopoverIfNeededAsync and no performance issues.
It could be fixed in few ways, which would probably require changing interface.
I thought, why do we have a single global semaphore for ALL popovers, it's a waste of performance, instead we can have a lock for every individual popover based on their id (well, almost, read below).
Instead of making own solution which would be a dictionary of semaphores, I decided to look for more a performance solution and went for an open source solution https://github.com/MarkCiliaVincenti/AsyncKeyedLock (all copyrights and license are linked). Only the StripedAsyncKeyedLocker part.
NB! I know it's yet another utility for popover, but we have other services that can utilize this as well, just like the IBrowserViewportService is utilizing ObserverManager. so we can use the StripedAsyncKeyedLocker there as well as it also uses a global semaphore just like current popover rather than an individual since it's listener has its unique id as well.
NB2! This locking mechanism doesn't guarantee that each individual popover will have it's own SemaphoreSlim. This is not a concert since we don't have nested locking and our implantation can work with only one available SemaphoreSlim. However I'm not yet sure if this StripedAsyncKeyedLocker is better than AsyncKeyedLocker(dictionary based) for perfomance, theoretically if there millions of popovers on a single page the performance can degrade again.
How Has This Been Tested?
With reproduction https://github.com/WoWs-Builder-Team/WoWs-ShipBuilder
I have set in browser settings network latency simulation - 300ms
Added Task.Delay(35) middleware before and after request
Swtiched from WebSocket to  HttpTransportType.LongPolling
Its to stimulate slow internet with latency
Types of changes

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

Checklist:

[x] The PR is submitted to the correct branch (dev).
[x] My code follows the code style of this project.
[ ] I've added relevant tests.

It's ready for review, but do not merge yet as I want to post before - after, and do some other not related testings to make sure nothing is broken.

The license is MIT, so it is compatible, we only need to include his copyright in the file if we plan on using it, that's all. Seeing the implementation (with what looks to me a custom built hash function?), I wonder if it is really faster than a .net dictionary which microsoft is surely optimizing the hell out of.
I am not concerned about adding another service if it makes the library faster which people care about a lot more than how many services there are under the hood.

The license is MIT, so it is compatible, we only need to include his copyright in the file if we plan on using it, that's all.

https://github.com/MudBlazor/MudBlazor/blob/c38d8feb08859606e5a5aecab468c0c5fcdf8aac/src/MudBlazor/Utilities/AsyncKeyedLocker/StripedAsyncKeyedLockEmptyDisposable .cs#L1-L2

I wonder if it is really faster than a .net dictionary which microsoft is surely optimizing the hell out of.

That's a really good question, I could write generic bench, but this doesn't show the full picture, since WASM runtime is different from the traditional one, and as far as I know BenchmarkDotNet doesn't support into WASM compilation (at least I tried it few months ago).
I can only try both ways with like thousands of popovers and make own subjective conclusion.

See my edit/PS above about the license.
What about benchmarking in BSS? Would that work?

Or just doing some measurements with Stopwatch. It won't be as precise but still give useful results if the performance is way off.

FYI
before the fix, can notice a noticeable delay on BSS(with latency) when I click on mudselect and the popover shows up

after with current fix:

After some basic testing with Stopwatch it seems that AsyncKeyedLocker(dictionary based) is doing much better and more consistent in speed than the StripedAsyncKeyedLocker when popover amount is relatively huge, so I will replace it, but I will still take implentation from this library as it's very clean and has interesting mechanism like pooling to reduce memory allocation and it's more easy to fine tune it.

When I get time I will double check that there is no regression of these issues https://github.com/MudBlazor/MudBlazor/issues/6345 and https://github.com/MudBlazor/MudBlazor/pull/3963 the reasons why the lock mechanisms were (tbh I feel like the second issue could be fixed without the locks, but let's not experiment for now) and if everything is fine i will merge it.

OK, well done. If you made changes to the original version of the locking tool you can add a note under the copyright. Something like // Improvements Copyright (c) MudBlazor 2024

No regression https://github.com/MudBlazor/MudBlazor/issues/6345 (no flickering) and https://github.com/MudBlazor/MudBlazor/pull/3963 (the window.mudPopover.map getting cleaned correctly).

@ScarletKuro I am the author of the AsyncKeyedLock library. While I'm OK with how the code was copied into this project, I am wondering why it wasn't done as a simple package reference. On occasion, I do some performance enhancements to my library and you would be missing out on these unless you stay tracking the project and re-copying the files.
Also, the way the implementation is done is not optimal at all. You are creating 10,000 semaphoreslim objects at startup and left permanently in memory, but it's absolutely not realistic for there to be 10,000 concurrent threads each with a distinct key. That's why I usually like to use a pool size of 20 with an initial fill of 1. If you do not specify an initial fill, you will get the whole pool created. Use the initial fill to therefore set a minimum pool size and the pool size to specify a maximum pool size. There is no need to set the maximum pool size high "just in case": if there's a peak and you exceed the pool size, objects will still be created automatically and will not need to wait for one to be returned to the pool. It is NOT some limit. Therefore if you're trying to clean memory after use as much as you can, you should be conservative because after the peak is over you don't want to have a lot of items in memory either just because it had once peaked that high.

I am wondering why it wasn't done as a simple package reference.

We are trying to keep this library at zero dependencies for now, it is one of our policies. We can talk about changing it if there are significant benefits.

I am wondering why it wasn't done as a simple package reference.

We are trying to keep this library at zero dependencies for now, it is one of our policies. We can talk about changing it if there are significant benefits.

In reality you are still depending on third party code on an open source project, and the code is fully debuggable anyway so you could even set breakpoints even while using NuGet.

@ScarletKuro I am the author of the AsyncKeyedLock library. While I'm OK with how the code was copied into this project, I am wondering why it wasn't done as a simple package reference.

As @henon we have policy not to have reference 3rd party libraries. It's also to keep the library footprint minimal, this is especially important for WASM project. Trimming can make it better, but:

Not all libraries support trimming, ("AsyncKeyedLock" one doesn't use reflection or generics much, so it should be supported)
Not all customers enable trimming.

On occasion, I do some performance enhancements to my library and you would be missing out on these unless you stay tracking the project and re-copying the files.

I do keep track on this. For example I occasionally check if there was important fixes in the Blazored.Modal which was donated to MudBlazor few years ago.

Also, the way the implementation is done is not optimal at all. You are creating 10,000 semaphoreslim objects at startup and left permanently in memory, but it's absolutely not realistic for there to be 10,000 concurrent threads each with a distinct key. That's why I usually like to use a pool size of 20 with an initial fill of 1. If you do not specify an initial fill, you will get the whole pool created. Use the initial fill to therefore set a minimum pool size and the pool size to specify a maximum pool size. There is no need to set the maximum pool size high "just in case": if there's a peak and you exceed the pool size, objects will still be created automatically and will not need to wait for one to be returned to the pool. It is NOT some limit. Therefore if you're trying to clean memory after use as much as you can, you should be conservative because after the peak is over you don't want to have a lot of items in memory either just because it had once peaked that high.

Thanks for the explanation, we already adjusted that in the https://github.com/MudBlazor/MudBlazor/pull/8305 and exposed the settings for the popover as well. If it's still too high we will readjust, for now we are trying to find the optimal settings.

Understood, but two notes:

The library name is AsyncKeyedLock so it would be nice if you could rename the folder from AsyncKeyedLocker to AsyncKeyedLock.
In the original files it would also be nice if you could put in the link to the github page for AsyncKeyedLock at https://github.com/MarkCiliaVincenti/AsyncKeyedLock so that whoever would like to use that code would know it's available over a separate library.

Hi @ScarletKuro,
the following exception appeared twice in our logs since MudBlazor Release 6.17.0:
System.Threading.SemaphoreFullException:Adding the specified count to the semaphore would cause it to exceed its maximum count.
?, in int SemaphoreSlim.Release(int releaseCount)
?, in async Task PopoverService.DetachRange(IReadOnlyCollection<MudPopoverHolder> holders)
?, in async Task BatchPeriodicQueue<T>.ExecuteAsync(CancellationToken stoppingToken)

Is it caused by this change?

Is it caused by this change?

Must be, we also experience this.
See my comment/screenshot

Hi @ScarletKuro,
the following exception appeared twice in our logs since MudBlazor Release 6.17.0:
System.Threading.SemaphoreFullException:Adding the specified count to the semaphore would cause it to exceed its maximum count.
?, in int SemaphoreSlim.Release(int releaseCount)
?, in async Task PopoverService.DetachRange(IReadOnlyCollection<MudPopoverHolder> holders)
?, in async Task BatchPeriodicQueue<T>.ExecuteAsync(CancellationToken stoppingToken)

Is it caused by this change?

is your project BSS too?

Hi @ScarletKuro,
the following exception appeared twice in our logs since MudBlazor Release 6.17.0:
System.Threading.SemaphoreFullException:Adding the specified count to the semaphore would cause it to exceed its maximum count.
?, in int SemaphoreSlim.Release(int releaseCount)
?, in async Task PopoverService.DetachRange(IReadOnlyCollection<MudPopoverHolder> holders)
?, in async Task BatchPeriodicQueue<T>.ExecuteAsync(CancellationToken stoppingToken)

Is it caused by this change?

is your project BSS too?

Yes, it is.

I think my best guess for now would be that when the circuits breaks unexpectedly the Popover.Dispose is called, but in parallel there is someone in the lock state, and I need to use the overload with the CancellationToken.
But I will try to reproduce it first, I would suggest switching to the legacy popover if it's critical.

I think my best guess for now would be that when the circuits breaks unexpectedly the Popover.Dispose is called, but in parallel there is someone in the lock state, and I need to use the overload with the CancellationToken. But I will try to reproduce it first, I would suggest switching to the legacy popover if it's critical.

I think you're onto something. I will have a think about this to see if I can and should fix it from the library's end. But it's tricky. You can't even wait until all threads are finished until you dispose, because some new requests could come in. Likewise with a cancellationtoken you will still have a race condition because a new request could come in whilst you're disposing.
Probably then you would need to have an isDisposing and not accept new requests while it's disposing.


Desktop switch shortcut doesn't work

Microsoft PowerToys version
0.80.1
Installation method
Microsoft Store
Running as admin
Yes
Area(s) with issue?
General
Steps to reproduce
PowerToysReport_2024-04-14-00-28-32.zip

Run the powertoys application.
Make sure it is running in the background(it is shown in the system tray).
Press the following shortcut to switch desktops(left):
windowsKey + controlKey + leftArrowKey

✔ Expected Behavior
It is supposed to switch to the left desktop.
❌ Actual Behavior
Pressing the shortcut does nothing. The same doesn't happen when u press the shortcut to switch to the right desktop(  windowsKey + controlKey + rightArrowKey). The shortcut only works for switching to the right desktop. This bug fixes itself when u close the powertoys application from the system tray (the shortcuts work as intended for both left and right desktop switching)
Other Software
No response

Looking at your remappings in Keyboard Manager you remapped Win+Left to Right. That is why it is not working. You can disable this remap and it should work again.
/helped


cube: Try to bind to wl_compositor v4

VK_KHR_incremental_present requires the client to
bind to wl_compositor v4. This is because internally
some Vulkan Wayland drivers convert VkPresentRegionKHR
to wl_surface.damage_buffer() [1].
If the Wayland compositor advertises wl_compositor v4,
we can bind to it and make incremental present actually
work.
[1] https://gitlab.freedesktop.org/mesa/mesa/blob/master/src/vulkan/wsi/wsi_common_wayland.c#L862

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

I have adapted the code style as per Travis CI's complaint. This issue was found while working on GNOME/gtk!1116. Let me know if there's anything else that is needed for merging.

So are you saying that there is a case where the driver supports incremental_present, but the compositor does not?  Is version 4 the right version for all Wayland compositors or just one specific compositor?  Is this in any documentation that you  could point me to?  Shouldn't the driver be the place where things like this are handled?  Please forgive my lack of Wayland knowledge.

So are you saying that there is a case where the driver supports incremental_present, but the compositor does not?

Yes; Wayland protocols are versioned, and each interface must have a version. When new requests, properties or signals are added to an interface, the version number is incremented. Wayland compositors must implement all properties, requests and signals that a certain interface version has in order to advertise support for that interface version.
Wayland clients and compositors then negotiate the interface version; the compositor tells the client which interface version it supports, and the client may bind to that version, or a lower version.
In this case, the interface we're looking at is wl_compositor [1] and wl_surface [2]. These two interfaces always have their versions in sync.
The incremental present regions are converted to a call to wl_surface.damage_buffer() [3], which is a v4 method. That means that only compositors that implement wl_surface (and wl_compositor) are able to handle it. Also, the client needs to ask the compositor to use v4 of wl_surface.

Is version 4 the right version for all Wayland compositors or just one specific compositor?

Yes :)
The version number of any interface is given by the corresponding Wayland protocol (the XML file). Wayland compositors only tell whether they support that version or not.

Shouldn't the driver be the place where things like this are handled?

The driver does need to check if the correct version of the protocol is supported, and ignore incremental present if it's not. This is the case for Intel Vulkan driver.

[1] https://gitlab.freedesktop.org/wayland/wayland/blob/master/protocol/wayland.xml#L190
[2] https://gitlab.freedesktop.org/wayland/wayland/blob/master/protocol/wayland.xml#L1323
[3] https://gitlab.freedesktop.org/wayland/wayland/blob/master/protocol/wayland.xml#L1677


addes some http status flags

addes some http status flags

This change is

Coverage remained the same at 59.016% when pulling f574cccafa48adf62c2af4107814eca2b4f64a3f on http-status into d09fdb0f19a8996e868d26761e44c770fe33bb5b on master.


Fix LineEdit minimum width

-Changed theme setting name to make more sense of what it does
-Reduced amount of minimum characters, so minimum size is smaller.
As a reference, small LineEdit properties now look fixed:

Supersedes #45922 (which should likely be reverted). Done on top of it, as tab changes were correct.

@akien-mga ok should be good to merge once it passes CI.

Force pushed a rebase for you.

ah I messed up, thanks!

Thanks!


Windows ARM support

We can build ARM on x86 machine.
Also, remove skia_use_freetype=true, because Skia doesn't build with this flag on ARM.
It is safe to remove, because is already true by default on Linux, and functions from file SkFontHost_FreeType_* aren't used anywhere in Skia/Skiko on Windows/macOS (skia_use_freetype only affects including these files).
I verified that in 2 ways:

Checked that Compose still works with this new Skia on Window/macOs/Linux
Tried to build with skia_use_freetype=true, but deleted content of SkFontHost_FreeType_* files. It still worked on Windows/macOs, but fails on Linux when we run Compose (skia/skiko don't fail on Compile time)

A Skiko build with this Skia is tested here


[FEATURE REQUEST] Containerization of Pipeline

Is your feature request related to a problem? Please describe.
Not all systems come with MATLAB licenses and at times can be difficult to obtain. To lower the barrier of entry and make osprey capable of running on systems without MATLAB, containerization is suggested.
Describe the solution you'd like
I would like the application, along with its dependencies wrapped into a container for ease of use. Specifically, MATLAB Compiler Runtime will likely need to be deployed for the containerized application to run as expected.

Osprey can be compiled as a standalone version now. The server version has been tested in MN and locally. Will need further testing to finalize this as a feature for general use.


Update readme

As the package will be made available via packagist the readme file needs to be updated.

First version of the readme has been pushed. Closing.


cmd/go: enforce the documented restriction on fuzz target result parameters

The documentation for F.Fuzz states that "ff must be a function with no return value", but in practice this is not enforced. For example, the following invocation is accepted:
func FuzzFoo(f *testing.F) {
	f.Fuzz(func(t *testing.T, i int) int {
		return 0
	})
}

We should enforce the documented restriction. If we don't, users will likely depend on the current behavior.  We can always relax this restriction in the future.
Marking as a release blocker as this is an API change.
CC @golang/release @bcmills

(CC @julieqiu as well).

Marking as a release blocker as this is an API change.

Since the API is already documented to require “no return value” it's not technically an API change, but I agree that it should be a release-blocker. (Otherwise, it's too easy for users to accidentally rely on behavior counter to the documentation.)


ariles_ros: 1.1.5-1 in 'melodic/distribution.yaml' [bloom]

Increasing version of package(s) in repository ariles_ros to 1.1.5-1:

upstream repository: https://github.com/asherikov/ariles.git
release repository: https://github.com/asherikov/ariles-release.git
distro file: melodic/distribution.yaml
bloom version: 0.8.0
previous version for package: 1.1.1-1

ariles_ros
* Sync to 1.1.5.
* Remove setup.sh and other helpers from the package.
* More thorough testing.

Closing and reopening to retrigger Travis.


Extract Indoor Map Graph from GeoJSON

libs:

https://github.com/dagrejs/graphlib
https://turfjs.org/

Technically part of indoor routing, but it’s too small to be handled as a separate task. Closing this for now as it's already covered under the indoor routing work.


CreateClients should return clientID's of the clients created

The relayer interface has a CreateClients function, but it does not return any identifying information of the clients created. It could return 2 strings, the identifiers of the clients created

Just mentioning this as food for thought, no rush to implement
It'd be useful to have access to this information. I think it is worth considering taking this a step farther though and returning a type which has filled in client identifier information. In ibc-go, our testing package has an endpoint type which contains the identifier information of all the client/connection/channel associated with it. This makes for a clean API since you can call:
endpoint.CreateClient()
endpoint.CreateConnection()
endpoint.CreateChannel()

and so forth and the identifiers get filled in by the relayer
I'm still getting context around this codebase, so I'm not entirely sure how well this idea gets translated, but I think it'd be immensely useful to have some object similar to this endpoint concept. For IBC design you need sort of three interfaces:

relayer
chain
endpoint

relayers should be responsible for relaying and continuing the flow of initiated IBC actions as well as coordinating larger tasks such as setting up clients/connections/channels. chains should be responsible for actions which only require one side (ie sending a packet) and endpoints should be the way a test writer interacts with certain port/channel pairs. I think it'd be useful if endpoints could initiate IBC flows. Like in relation to this command, I only want to create a client on chainA (I don't care about chainB within the test)

reference usage https://github.com/cosmos/ibc-go/pull/2130


Fix to process expired codes periodically

This change fixes a bug that was causing expired codes to be processed almost every time rather than periodically based on an expiration time, as it was designed. Without doing this the code will more likely encounter the dead locks under significant load.

Closing due to inactivity.


PlayModeStateChange file not found

Assets/NetworkMeshAnimator.cs(42,39): error CS0246: The type or namespace name `PlayModeStateChange' could not be found. Are you missing an assembly reference?

Not sure if you have solved it already. I hit the same issue but it looks like there was an API change from Unity 2017.1.3 to Unity 2017.3.1
Updating my Unity to the latest one fixed this issue.

I also encountered the same problem. And unity version is 2018.4.11c1.


I get an error

goroutine 8 [running]:
panic(0x232480, 0xc420012080)
/usr/local/go/src/runtime/panic.go:500 +0x1a1

That is not the full error message. You selected a tiny snippet of the error message. In fact, the snippet you selected is the least useful part.

The issue was that i couldn't connect to safeval.pw because of my schools filter. Unless you can help me get passed that theres not much we can do

Ah ok. I am going to close this issue then.

The current version no longer requires safeval.pw (for now).


How to enable GPU usage

Before MiniCheck(model_name='roberta-large', cache_dir='./ckpts') has a parameter called device. Now this is no longer available.

Hi,
You can add the following lines at the beginning of your code for setting GPU:
import os
os.environ["CUDA_VISIBLE_DEVICES"] = "0"

Or you can use the export CUDA_VISIBLE_DEVICES=0  command in the terminal before running your script.
Let me know if this works for you!

You can also check the MiniCheck Model Evaluation Demo section in the README:
from minicheck.minicheck import MiniCheck
import os
os.environ["CUDA_VISIBLE_DEVICES"] = "0"

doc = "A group of students gather in the school library to study for their upcoming final exams."
claim_1 = "The students are preparing for an examination."
claim_2 = "The students are on vacation."

scorer = MiniCheck(model_name='roberta-large', cache_dir='./ckpts')
pred_label, raw_prob, _, _ = scorer.score(docs=[doc, doc], claims=[claim_1, claim_2])

Hi,
You can add the following lines at the beginning of your code for setting GPU:
import os
os.environ["CUDA_VISIBLE_DEVICES"] = "0"

Or you can use the export CUDA_VISIBLE_DEVICES=0 command in the terminal before running your script.
Let me know if this works for you!

Hi. This worked for me after I install  accelerate. Thanks.


not working for woff, ttf files

Does this work for woff, ttf files? I have the following settings:
inject: false,
inlineSource: '.(woff|ttf)$',
template: './src/index.html'

I get errors from some these files when I load the bundle on a subroute

No this plugin modifies the injected css or javascript generated by the html-webpack-plugin.

Oh wow I'm a plonker, took me a while to realise this. Is there some documentation I was silly enough to skip over?


Terraria GSI becomes obsolete with 1.4 release

Game Name: Terraria
Methods: The 1.4 promises to bring the razer chroma support, so that means the current tmodloader solution which isn't too flexible and isn't working on multiplayer can be replaced with a Razer Chroma Layer
Source: Terraria 1.4 Changelogs
https://forums.terraria.org/index.php?threads/there-back-again-a-summary-of-journeys-end.87997/

I know this, but the wrapper solutions are not as reliable as the GSI ones. We'll see what happens when 1.4 actually releases.

If this becomes implemented i would suggest to pack the legacy lighting into a plugin and provide that for people that want to continue using that

legacy lighting could target tmodloader's new renamed executable and a new wrapper lighting profile could be used for terraria 1.4

This i didn't know about. I just installed Tmodloader on steam and the exe name is indeed different. I will be renaming this profile to TModloader, along wioth a new icon. If regular terraria players want to use the chroma lighting, they're free to create a new profile with a razer chroma layer / use a chroma layer on the desktop profile.


Color Code for 221 not reflected in BTLegoMario.py

In BTLegoMario.py - there is no color defined in solid_colors for value = 221.  That's the value the color scanner reports when I put mario onto a 222.Light Purple (Bright Pink), 221. Bright Purple (Dark Pink), or 124. Bright Reddish Violet (Magenta) LEGO Brick.
Given the suspicious correlation to LEGO official color code 221 - I think it is meant to be Bright Pink (LEGO Official name) / Dark Pink (BrickLink name).

I also discovered that code 119 is reported from Peach/Mario when placed on a Bright yellowish Green / Lime LEGO brick..  This again corresponds to the official / internal LEGO Color codes.

It also recognizes 324 - which is "Medium Lavender".
I also saw a note in the code that you couldn't get blue to trigger.  I am seeing the "blue" message when on 321 - Dark Azur color, but not on 23. Bright Blue (which is the classic LEGO blue color)

I will run through some of the colors and cross check this week!

Colors were present in the 5.3 update. Wonder when they updated.

Fixed in the latest update!  What counts for pink is... interesting.  Coral (353) counts as red
Also added some other stuff.  The whole cyan ice interaction I don't quite understand.


Shared sub folders

gdrive-windows-x64.exe list  --query "sharedWithMe"
will provide root folders shared.
But I need details of the subfolder folders, like
shared with me / MIMB /  MIMB-OEM / 9.1.0
And see the files list inside it.

I would also like to know how to do this


Firmware

Hi there,
This is a great idea, specially since all of their software requires firmware 2.1 which will cost you at least $150.
Could you guys post what firmware you are using?
Thx!

This expects version 2.10.


new bufferCV bug

What version of Stacks.js are you using?
latest
Describe the bug
In bufferCV.ts, buffer.length > 1_000_000 should be buffer.length > 1_048_576.
How to reproduce
Let buffer contains (1_000_000, 1_048_576) characters, bufferCV will trigger error.
Expected behavior
Pls fix it.

Thanks for the report 🙏


editorconfig check: instruct user what to do

https://github.com/zowoq/actions-test/pull/1
Opening the log from the PR it looks like the message isn't being displayed properly, it's blocked by check error?

See https://github.com/zowoq/actions-test/actions/runs/795424920
On Thu, Apr 29, 2021, 10:48 zowoq @.***> wrote:

zowoq/actions-test#1 https://github.com/zowoq/actions-test/pull/1
Opening the log from the PR it looks like the message isn't being
displayed properly, it's blocked by check error?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/pull/121063#issuecomment-829054593, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA63AYDE7FSFB6ZQXZ74TTTLEMOTANCNFSM43XR6O2A
.

https://github.com/zowoq/actions-test/pull/1/checks?check_run_id=2465001774

If you're happy with how it looks I don't have an objection. Feel free to merge.

I'm not happy, but there's no better way without writing code to set status, which would require write permission token for all contributions.
This is the best we can do about it.

The message chosen here (‘Hey! It looks like your changes don't follow our editorconfig settings. Read https://editorconfig.org/#download to configure your editor so you never see this error again.’) is under consideration for revision in #287487, if any participants have a preference for the current wording.


ion-select readonly property

Feature Request
Ionic version: 4.0.0
Feature
ion-select readonly property
Feature Request Description
There needs to be a way to make ion-select field read-only, and not just disabled because disable also changes color of the field and make it un-selectable for copying its value etc.

Hi there,
Thanks for opening an issue with us! readonly on a select is not currently part of the native select spec, so I'm going to close this for now.
Thanks for using Ionic!


Any client issue or project should be documented as a ticket and submitted into the Infotect Design Solutions ticket database for tracking and resolution

This rule comes from the Business Analysis created in collaboration with the client. We can ensure we adhere to this rule by ensuring every issue documented by the bot is submitted as a ticket.

Terms
Ticket – The record of an issue being experienced by a customer and all actions being taken or that have been taken to solve the issue. Tickets may also be used to keep track of big projects.


whether the servers are down or whether there has been a power outage

^^^^
error when trying to connect ssh:
ssh: connect to host localhost port 22: Connection refused
translated with Google translator

Seems to be an error connecting to localhost, not srv.us?


bug: Depracation of set-output command

Describe the bug
A clear and concise description of what the bug is.
When the CI runs, I encounter this warning: Warning: The set-output command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
This is based on this update https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
This line should be updated https://github.com/rutajdash/prettier-cli-action/blob/30325c923a7b131ab8b6c99e0aff38afaddb9643/action.yml#L42

I was using v1.0.0 not the latest.


Add opensearch sink security

Description
Adds security documentation for Data Prepper opensearch sink plugin.
Issues Resolved
Checklist

[X] By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and subject to the Developers Certificate of Origin.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Pushing this through to editorial in lieu of waiting for another Doc review.