Unable to run / install

npm run ionic:serve

<EMAIL_ADDRESS>ionic:serve /home/johnny/Projects/PICO/picoDeploy-master
npm run config && npm run cart && ionic-app-scripts serve

<EMAIL_ADDRESS>config /home/johnny/Projects/PICO/picoDeploy-master
node config/copyConfig.js

Using the following config: picoDeployConfig.json

<EMAIL_ADDRESS>cart /home/johnny/Projects/PICO/picoDeploy-master
rm -rf www/cart && mkdir www/cart && cp -r cart/* www/cart

mkdir: cannot create directory ‘www/cart’: No such file or directory
npm ERR! Linux 4.15.0-64-generic
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "run" "cart"
npm ERR! node v8.10.0
npm ERR! npm  v3.5.2
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>cart: rm -rf www/cart && mkdir www/cart && cp -r cart/* www/cart
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>cart script 'rm -rf www/cart && mkdir www/cart && cp -r cart/* www/cart'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the picoDeploy package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     rm -rf www/cart && mkdir www/cart && cp -r cart/* www/cart
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs picoDeploy
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls picoDeploy
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /home/johnny/Projects/PICO/picoDeploy-master/npm-debug.log
npm ERR! Linux 4.15.0-64-generic
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "run" "ionic:serve"
npm ERR! node v8.10.0
npm ERR! npm  v3.5.2
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>ionic:serve: npm run config && npm run cart && ionic-app-scripts serve
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>ionic:serve script 'npm run config && npm run cart && ionic-app-scripts serve'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the picoDeploy package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm run config && npm run cart && ionic-app-scripts serve
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs picoDeploy
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls picoDeploy
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /home/johnny/Projects/PICO/picoDeploy-master/npm-debug.log

Running Elementary OS (ubuntu 18)

Ah! I've been super busy lately, but once I'm done moving I'll check this out 😄 @novusabeo

does this issue cover npm install failing?

@novusabeo Sorry I haven't taken a look at this yet 😢 After moving (which I'm still slowly unpacking), I had a huge debacle with Spotify outside of my music stuff, and been catching up with a lot of friends. I also switched jobs recently and stuff, so it's just been a lot going on 😢
@Chovin It seems like this does.
I'll try and take a look as soon as I can. Currently flying to give a talk at a conference!

@novusabeo WAYYYY overdue, but I finally did a fix for this. Just had to updated the dependencies, and use mkdirp to fix the script 😄


Standalone port of the Quark chat feature?

With no Quark version 1.20 available, could this potentially be used instead?
https://www.curseforge.com/minecraft/mc-mods/showcase-item

while it would work, do note that this mod is both a client and server side mod, which means everyone that wanted to connect to the modpack would have to download this mod in addition of their modpack


Add Atlas Mascot as favicon for gsd.id

This doesn't seem to work locally, despite following the minima documentation... Not sure what's going on. Also having weird issues with my devcontainer on this, despite using the exact same config on my personal jekyll site just fine.

That said, adding favicon.ico to the root did seem to get it rendering the favicon at least, even thought the custom head file was being ignored.


[v6.4.x] Request to make "Disable Gestures" toggle only disable facial expressions, not gestures.

In v6.4.x, a Disable Gestures toggle was created which has the same effect as disabling gestures through the default vrc setting. This causes issues for people that want to have face tracking with disabled facial expressions while still being able to interact with different avatar systems and/or props on their avatars that require gestures. As currently, they cannot interact with their avatar props while the Disable Gestures toggle is on.
In previous versions, you had people create a facial expressions toggle which seems to now have been replaced with this Disable Gestures toggle. I hope a better solution can be made to have a similar effect as the previous way of doing it, else I think this change should be reverted, as it seems to be no different than the default vrc gestures setting and is a duplicate.
For example, in one of my props I have recently released, you have to grab the prop from your hip using Gestures. I have replicated and verified this issued with two other people who have also encountered this problem.

Unpack the prefab and remove the Gesture Disable sub object.

Changed the Disable Gesture Expressions to Disable Facial Expressions. Remove the Gesture Disable VRCFury toggle prefab. v6.4.2


Products not adding to database after constrait fix on Mar 19th

Lamdba function setting product version to none/null when field can no longer be null.  Setting values to default '1111-11-11T11:11:11.11Z' if the processor does not specify a version.

Fix has already been applied to AWS Lambda


SW-3352 MortalityRateInNursery Not Required

A change in requirements means that for species in a planting site, the
mortality rate in nursery is no longer required. And the input for this
has been removed on the frontend. To allow a report to be validated,
remove the requirement.

Seems safe enough. If the input is going away, should the field go away entirely, as opposed to just the validation?

Good point, I will remove it.

Any related schema changes?

No, if you mean SQL schema changes. The report data is all serialized as json before going into/out of the DB


Missing method popup_message_toast (interface Z2UI5_IF_CLIENT)

Related to developer challenge : https://groups.community.sap.com/t5/application-development-discussions/sap-developer-challenge-open-source-abap-week-2/m-p/260727#M1372
The class created for the challenge few months ago seems to not compile any more today :
Method "POPUP_MESSAGE_TOAST" is unknown or PROTECTED or PRIVATE.
This method seems to be missing interface Z2UI5_IF_CLIENT today.
Example of repo that are no more working today :
https://github.com/chaouki-akir/developer_challenge2023/blob/main/week2/zcl_app_week_02
https://github.com/AndreaBorgia-Abo/abap2ui5-tests/blob/main/src/zcl_abo_abap2ui5_simpleapp.clas.abap

seems like an old version of abap2ui5, alot of refactoring was done since

yes if you install the actual abap2UI5 version the examples & solutions from the developer challenge are not working anymore.
but i recommend to install the newest abap2UI5 version and also install the samples repository:
https://github.com/abap2UI5/abap2UI5-samples
There you will find demos with all needed functions.
you can display the message toast for example now with the method:
client->message_toast_display
i also recommend to read the blog series to get a basic understanding how to create apps:
https://blogs.sap.com/2023/02/22/abap2ui5-development-of-ui5-apps-in-pure-abap-1-3/
Best regards.

Thank you. I will check that


chore(rdmd to rmdx): wrap scripts + styles in an

🧰 Changes

[x] wrap scripts + styles in an
[x] add test cases
[x] ~implement compatabilityMode option~
discussed with @kellyjosephprice and we're gonna deprecate compat mode for RMDX (8ad57ac)

🧬 QA & Testing
Pull this branch down and try running the test suite for the RDMD→MDX conversion:
npm run test -- compatability.test

If these new tests pass, this worked! :tada:

This PR was released!
🚀 Changes included in v7.5.0


When using bounds="parent" how to drag outside of the parent

How to drag outside of the parent like absolute positioning left: 100% with bounds="parent". I don't want to subtract draggable element's width from the draggable range.

-a selector restricts movement within the targeted node
bounds: "selector-class"

An object with left, top, right, and bottom properties. These indicate how far in each direction the draggable can be moved.
bounds: {left?: number, top?: number, right?: number, bottom?: number}


Fix typos in docs

Description
Fix typos in docs.
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #177.
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[x] Code compiles correctly
[x] Created/updated tests
[x] Extended the documentation

 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.:x: lnquy sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Thanks for this contribution!


Connection constructor's documentation is missing key details

The Connection object is missing some important details about its options parameter. Here are a few of the problems I noticed:

options.port is actually optional and defaults to 27017
options.host is actually optional and defaults to localhost
options.bson is required but undocumented (the constructor will throw if you don't pass it in)
options.tag is undocumented (although I could understand why this one might be omitted based on the comment in the source)
options.maxBsonMessageSize is undocumented
The following SSL-related options are undocumented:

options.ciphers
options.ecdhCurve

I think that covers everything but I may have missed something.

Filed NODE-1730 to track


Improve Video Shortcut

The current video shortcut is not very configurable. By default, videos occcupy huge spaces, and use plyr, which, while it looks great, ofuscates a bit how to improve the shortcode. I would like something similar to the image shortcut, in the lines of:
{{ $type := .Get "type" }}
{{ $randNumber :=  index (seq 200 | shuffle) 0 }}

<video class="video-player" id="video-{{ $randNumber }}" playsinline controls>
  <source src="{{ .Get "src"}}"
  type="{{ $type | default "video/mp4" }}"
  {{ if .Get "title"}}
        alt="{{.Get "title"}}"
    {{end}}
    {{ if .Get "width"}}
        width="{{.Get "width"}}"
    {{end}}
    {{ if .Get "height"}}
        height="{{.Get "height"}}"
    {{end}}
    {{ if .Get "float"}}
        style="float: {{.Get "float"}};"
    {{end}}
    {{ if .Get "align"}}
        class="{{.Get "align"}}"
    {{end}}
  />
</video>

Also, there is the problem with the video ID: currently, there is risk of collusion. Either the randnum could be augmented, or another method could be devised
Describe alternatives you've considered
I tried to do it by myself, but I couldnt get it to work due to plyr

I have tried wrapping it inside a DIV, but it just doesnt center

Thank you @MarionMoseby for reporting this issue. I will take a look soon.


Fix null lyric on USTX load

The English word "null" cannot be used in lyrics when saved as a USTX file. The YAML parser reads a literal null on load and fails. Discord bug report

Surround UNote lyrics with quotes " " to force YAML to serialize literal strings
Remove quotes from lyric on load
Literal null lyrics convert to default lyric on load to prevent loading null lyric
Add AfterSave to UPart, make UProject execute AfterSave to remove multiple quotes on consecutive saves

Admittedly this is probably clunky and not perfect, but it's better than failing to load because of a YAML quirk

"null" string can not only exist in lyrics but also in other strings, such as voicebank names, part names. so this should be global for yaml serializer. You can use WithQuotingNecessaryStrings in OpenUtau.Core/Util/Yaml.cs


Custom Blade directives?

Hey guys,
Was checking out jigsaw-core.php and saw this on line 102:
(new BladeDirectivesFile($c['cwd'] . '/blade.php'))->register($bladeCompiler);
I see BladeDirectivesFile will register directives from a given file. Am I right in assuming one can add a blade.php file where custom directives can be registered?
If so, where would you add this? And how would custom directives be registered in it? Tried adding it to /source and root of project, but it doesn't work with Blade::directive(). Appreciate any insight/pointers.

You would add the blade.php file to the root of the project (same level as config.php), and return an array of directives to register. Each directive receives two parameters:

$expression, which is specified when you call the directive, e.g. @mydirective('expression')
$page, which is the usual $page variable for whichever page the directive is called on.

So, for example:
<?php

return [
    'datetime' => function($expression, $page) {
        return '<?php echo date("Y-m-d H:i:s", ' . $expression . '); ?>';
    },
];

The feature came from this request but hasn't been documented. I'll make a note to add it to the docs on the next update.


Update index.html.md.erb

Updating for 1.0.6 patch release, also validated 1.0 on pcf 1.12 now

Thanks!


[REQUEST] Theme scyfin

Project Website
https://github.com/loof2736/scyfin
Project Description
Theme scyfin

This theme is already included in the list:
https://github.com/awesome-jellyfin/awesome-jellyfin/blob/main/THEMES.md#scyfin-by-loof2736


merge MONDO_0020536 'pigeon-breeder lung disease'

there is a comment on this class: Editor note: merge this
not sure what it is meant to be merged with though? I am guessing maybe it should be merged with MONDO_0005668 'bird fancier's lung'
Note, there is a typo in the def for MONDO_0020536 'pigeon-breeder lung disease', but maybe this term will be obsoleted.
"Pigeon-breeder's lung disease, also called bird fancierBs lung...."

the child seems incorrectly classified:
'hypersensitivity pneumonitis, familial'


build: read build tags from an environment variable

When using a toolkit that needs to use build tags (such as appengine), several tools in golang.org/x/tools/cmd become useless (godoc, gorename, etc.) become useless because they don't take build tags as arguments and ignore all of your source files.
If build's defaultContext() read build tags from an environment variable (e.g. $GOTAGS), all of these tools would support projects that use build tags. This is much cleaner and easier to deal with than adding a -tags option to every one of these commands.

Whenever new environment comes up, there's always a lot of pushback. Go isn't very fond of them in general.
Also, that means all tools need to decide precedence or merging between explicit flags and the environment.
I think the proper fix is adding flags to tools where it's lacking.

Russ also suggested that he was thinking about refactoring cmd/go into some
reusabl pieces. Hopefully if this were to happen it would allow tool
writers to consume a single way of talking about go packages and source
files which might make this problem less of an issue.
On Thu, 2 Feb 2017, 11:59 Brad Fitzpatrick<EMAIL_ADDRESS>wrote:

Whenever new environment comes up, there's always a lot of pushback. Go
isn't very fond of them in general.
Also, that means all tools need to decide precedence or merging between
explicit flags and the environment.
I think the proper fix is adding flags to tools where it's lacking.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/golang/go/issues/10063#issuecomment-276833723, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAAcAwMaLeBAHe7RrOClI_alB82Ukqa1ks5rYSpggaJpZM4DocbY
.


1.0.0rc6

Signed-off-by: Stephen Curran<EMAIL_ADDRESS>

Updated the Changelog to include the 11.1, 11.2, 11.3 and 12.2 entries that weren't released from the main branch. Otherwise, a straight forward (I hope) release candidate.

Integration tests are failing. I thought it might have been because of the BCovrin reboot this morning, but that was not it.  @jamshale -- can you please investigate.
Errors:
Failing scenarios:
  features/0453-issue-credential.feature:321  Issue a credential with revocation, with the Issuer beginning with an offer, and then revoking the credential -- @1.3
  features/0454-present-proof.feature:138  Present Proof where the issuer revokes the credential and the proof fails -- @1.1
  features/0454-present-proof.feature:143  Present Proof where the issuer revokes the credential and the proof fails -- @2.1
  features/0454-present-proof.feature:204  Present Proof for multiple credentials where the one is revocable and one isn't, neither credential is revoked -- @1.1
  features/0454-present-proof.feature:262  Present Proof for multiple credentials where the one is revocable and one isn't, and the revocable credential is revoked, and the proof checks for revocation and fails -- @1.1
  features/0454-present-proof.feature:263  Present Proof for multiple credentials where the one is revocable and one isn't, and the revocable credential is revoked, and the proof checks for revocation and fails -- @1.2
  features/0586-sign-transaction.feature:107  endorse a schema and cred def transaction, write to the ledger, issue and revoke a credential, manually invoking each endorsement endpoint -- @1.1
  features/revocation-api.feature:42  Using revocation api, issue, revoke credentials and publish -- @1.1
  features/revocation-api.feature:44  Using revocation api, issue, revoke credentials and publish -- @1.3

I notice all the failures are with revocable credentials -- issue and present.  I can't think of where that might be breaking but...

Looks like it is a tails file issue -- although I would think that would affect the non-revocation tests as well. There must be some, right?
7hAcme.agent | aries_cloudagent.revocation.error.RevocationError: Tails file for rev reg HsWgudheR1Wa3tBhJW6xJt:4:HsWgudheR1Wa3tBhJW6xJt:3:CL:1532186:Acme.agent.initial.129198.Schema_DriversLicense:CL_ACCUM:fd0dd658-0976-4a9f-887c-5ba5d9010ace failed to upload: Exceeded maximum upload attempts

Same problems as the nightly fail. Looks like both issues with the tails server and ledger. I guess re-booting it didn't work :/

I rebooted the tails server now, I don;t think I did this morning. We need to figure out what is causing that poisoned lock there, i will log an issue that we can tackle.


Game Crash: Null array out of bounds

client.log
Hey guys I have been having problems with Runelite client crashing due to a java error I suppose.
My client will freeze, or crash (client will close) randomly throughout playing.
These instances happen at random, nothing specific to my gameplay or area location.
Perhaps its an on-screen problem?
I was hoping someone may be able to help me out. I do not have any third party or extra downloadable plugins installed. I play my client basically as its 'vanilla' form. I have a FPS and ping counter on screen, and of course boosts and other helpful info boxes that are on the sides of the game. But nothing special added to runelite.
Please let me know if you'd like anymore logs or extra information!
Thanks so much!
Here are a few examples of some crashes from my logs, and I have attached 2 client .txt files that have crashes inside them.
2020-11-08 21:42:49 [Client] ERROR client-patch - Game crash: null
---java.lang.ArrayIndexOutOfBoundsException: Index 16777268 out of bounds for length 104
at hz.ql(hz.java:902)
at ef.cg(ef.java)
at fu.xi(fu.java:28163)
at bv.gs(bv.java:4616)
at ax.ik(ax.java:9441)
at kv.io(kv.java:9330)
at client.zv(client.java:4263)
at client.ak(client.java:1621)
at ba.d(ba.java:361)
at ba.run(ba.java:315)
at java.base/java.lang.Thread.run(Unknown Source)
--- java.lang.NullPointerException: null
at net.runelite.client.plugins.slayer.SlayerPlugin.taskLookup(SlayerPlugin.java:831)
at net.runelite.client.chat.ChatCommandManager.lambda$onChatMessage$0(ChatCommandManager.java:122)
at net.runelite.client.util.RunnableExceptionLogger.run(RunnableExceptionLogger.java:41)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.base/java.lang.Thread.run(Unknown Source)
2020-11-07 08:14:25 [Client] WARN  client-patch - error during tile underlay rendering
java.lang.ArrayIndexOutOfBoundsException: null
2020-11-07 08:22:11 [Client] WARN  client-patch - error during tile underlay rendering
java.lang.ArrayIndexOutOfBoundsException: null
2020-11-07 08:27:17 [Client] WARN  client-patch - error during tile underlay rendering
java.lang.ArrayIndexOutOfBoundsException: null
2020-11-07 08:36:37 [Client] WARN  client-patch - error during tile underlay rendering
java.lang.ArrayIndexOutOfBoundsException: null
2020-11-07 08:39:15 [Client] WARN  client-patch - error during tile underlay rendering
java.lang.ArrayIndexOutOfBoundsException: null
2020-11-07 08:40:40 [Client] WARN  client-patch - error during tile underlay rendering
java.lang.ArrayIndexOutOfBoundsException: null
2020-11-07 08:47:54 [Client] WARN  client-patch - error during tile underlay rendering
client_2020-11-07.0.log

Any suggestions anyone?

Reopen this issue if the problem persists in the current version of RuneLite.

Reopen this issue if the problem persists in the current version of RuneLite.


Updated for Terraref BETYdb change

Updated for BETYdb change
No review

Codecov Report

Merging #61 (05d1572) into main (8d9e018) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #61   +/-   ##
=======================================
  Coverage   62.09%   62.09%
=======================================
  Files           5        5
  Lines         372      372
=======================================
  Hits          231      231
  Misses        141      141

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 8d9e018...05d1572. Read the comment docs.


Fix scrollbar contrast when in dark mode, by relying on built in color-scheme

Docs: https://developer.mozilla.org/en-US/docs/Web/CSS/color-scheme
Also included:

ember-auto-import and embroider upgrades, because I ran in to this issue, which is fixed in recent version.
npx ember-apply tailwind, which gives the test app Tailwind 3 + JIT in the least invasive way, in that it uses the Tailwind CLI without integrating with webpack or anything as this approach does (which is really good! just not what we want since we need to support pre-embroider workflows as well). The main advantage to this native tailwind CLI approach is that it works well with Ember-CLI's CSS-hot-reloading (both with and without embroider), so we can tweak the config and CSS without re-loading the page we're viewing.
a demo page for the manual test, and potentially something for us to run Percy against later
I removed ember-cli-typescript as it was breaking the build. ec-ts is also being sunset in general.

Things for later,

(and @simonihmig and I have started talking about this), but we need to set up a central renovate config for all our open source repos to extend, as we have enough now, where some things have begun to slip through the cracks as we iterate and forget to propagate changes. In this case, regular test-app dependency updates had been disabled because at one point we thought it was a good idea to keep the tests using the oldest dependencies we wanted to support. We haven't done that in a long time though, and if there is anything we actually need to support, we should declare it so, explicitly in the ember-try.js config.
we may want to create multiple test / example apps for our presently supported tailwind integration scenarios, as right now they are only documented on the README -- it would be good to get thees approaches integrated in to C.I.

Tailwind 2 + ember-cli-postcss -- non-embroider
Tailwind 2 + ember-css-modules -- non-embroider
Tailwind 3 + JIT + tailwind-CLI -- with and without embroider
Tailwind 3 + JIT + webpack CSS -- embroider-only
(note that Tailwind 3 + JIT is not possible to support with ember-cli-postcss)

it may make sense to pull this package (and its test app) in to the toucan-core monorepo at some point -- especially if we can work through the dependenciesMeta.*.injected issue described here

How to test manually

checkout this branch
pnpm i
in 3 terminals:

pnpm build
cd test-app && pnpm tailwind:watch
cd test-app && pnpm start

LGTM!
TS tests fail with Property 'instance' must be of type 'EmberObject', but here has type 'EmberObject'. 😅
Possibly duplicated @types packages with different versions?

Possibly duplicated @types packages with different versions?

likely, been having a big problem with that with all the @types/ related stuff lately

atm, I'm getting this error:
❯ pnpm tsc
error TS2688: Cannot find type definition file for 'ember__test-helpers'.
  The file is in the program because:
    Entry point for implicit type library 'ember__test-helpers'

which, I've gotten on other projects, but I forgot the resolution.

This has gotten crazy enough, where I'm going to pull out all the basic maintenance stuff out to a separate PR.
I think there is some incompatibility with various @types/ember* packages and the ember* packages that now provide their own types.. :-\

which, I've gotten on other projects, but I forgot the resolution.

Wasn't it updating to latest @ember/test-helpers (which ships its own types) and removing @types/ember__test-helpers?

Wasn't it updating to latest

yeah, there were a couple other dependencies that ended up needing to be updated as well as they were also bringing in the old @types/ember__test-helpers

a demo page for the manual test, and potentially something for us to run Percy against later

I love this idea!

we may want to create multiple test / example apps for our presently supported tailwind integration scenarios, as right now they are only documented on the README -- it would be good to get thees approaches integrated in to C.I.

For sure, I can definitely see value in this.

it may make sense to pull this package (and its test app) in to the toucan-core monorepo at some point -- especially if we can work through the dependenciesMeta.*.injected issue https://github.com/CrowdStrike/ember-headless-table/pull/44

Saad had a question about this today as well, so nice you're touching on it here!  I agree that it'd be nice to move it there eventually! 🙇 To your point above about Percy, then we can really exercise Toucan as a whole (both styling + components) - I dig it!


feat: optional caption for clients section

:tada: This PR is included in version 0.54.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add option to reject delegated zcaps with an expiration date too far in the future

We want to enable enforcement of expiration on delegated zcaps. This means not only requiring an expiration date to be present on delegated zcaps, but also that its value not be too far into the future.

This restriction should also apply to zcaps submitted to the revocation endpoint. While zcaps with expirations far into the future won't be able to be revoked -- they also won't be able to be invoked.

Use new zcapld release once https://github.com/digitalbazaar/zcapld/pull/73 lands.

Addressed by #19.


Small fixes for compatibility with Octave

Added a fclose to close file, and some small fixes to make the code work with Octave. @bjonkman let me know if this looks fine to you.

@rafmudaf (or whoever else has write access on this repo)... could you merge this PR?


On-chain formats for secondary and tertiary roots of trust

There are certain disadvantages of using a ledger over a witness pool, namely interoperability outside of the eco-system. However, while witness pools are very well suited to enterprise use cases, for me there is still an open question on how the average user in the Cardano ecosystem selects witnesses in a reliable but simple manner. (in absence of being able to run their own witness networks)
I am still trying to think of a nice way to create an incentive-based eco-system of witnesses and watchers over the Cardano eco-system and stake pools but until then the CF wallet probably needs to use the ledger as a secondary root of trust to buy time and grow adoption of KERI in our eco-system. Even when witness pools pop up in our eco-system, there would be a time period where there aren't enough witnesses, or watchers with reputation etc so this could serve as a base while transitioning.
Hence, I'd like to open a discussion on this topic for those interested.

There needs to be an on-chain standard (CIP-10, and CIP-???? for KERI) that supports both secondary and tertiary roots of trust:

Secondary coming directly from wallets in the ecosystem holding funds.
Tertiary both as a witness backup mechanism and possibly for a watcher reputation checkpoint.

https://github.com/WebOfTrust/keripy/issues/90 defines a method of marking an AID as backed by a ledger and using a ledger registrar as a hook. Since Cardano uses Ed25519 keys which is a public key primitive in CESR, we can directly convert a ledger registrar AID to an "enterprise" Cardano address only containing a payment part and not a staking part - see CIP-19.
Secondary root of trust: Firstly considering this alone. As a verifier or watcher indexing the chain, I may find:

a KEL from the registrar address
a KEL from another address
a KERL (receipted by the ledger registrar) from the registrar address
a KERL (receipted by the ledger registrar) from another address

Limiting to just the registrar address is problematic in case the controller needs to rotate ledger registrars is problematic for a verifier if they were only indexing KELs from a pool of Cardano addresses (or a single one), assuming notifying out of band of the registrar address is infeasible for all interactions. I think it's better to allow it to come from any address and globally index the chain:

This still allows sub eco-systems to restrict to a set of addresses (and not necessary the same as the registrar) as business logic for performance gains while indexing the chain - and it's up to that sub eco-system to remain up to date with the address changes.
It also allows for use of normal, staked Cardano addresses. This is important as the more ADA staked, the better for decentralisation.

Secondary, the secondary root of trust is the ledger itself. It's up to verifiers and watchers to make sure they are only retrieving key events from the chain, so I don't see the added value of a ledger registrar receipt in the transaction. Receipts means more signatures which means higher tx fees and more chain bloat.
Simply getting a receipt from a ledger registrar API and not the ledger would be wrong so it almost feels like the Cardano transaction itself is the "receipt". (though you need to verify the history of the chain to know the receipt was valid)
This is why I would propose simply: a watcher should index the chain on all addresses for normal KELs and build up an database of AID -> KEL mappings. There could exist an eco-system of global watchers that index the entire chain and provide watcher receipts on their result, which opens the door to reputable watchers of Cardano-backed (secondary root of trust) KELs (with judges etc). If there exists a particular sub eco-system within Cardano, their verifiers/watchers could index a set of predefined addresses that the AIDs of the sub eco-system will use - while still being picked up by global watchers for others outside that sub eco-system.
The caveat here is that if there is no registrar backer, there is simply a seal with e.g. CARDANO_MAINNET and an empty backer list. Further investigation needed if this is problematic to support.
Tertiary root of trust: I've thought less on this and maybe @rodolfomiranda can weigh in but this could include KERLs witnessed by witnesses (as a form of backup) or by watchers as a form of reputable watchers (different to the reputable watchers I described in the last paragraphs).
I think just a KERL is enough to differentiate from secondary root of trust. A judge or watcher that is reading from the ledger the tertiary root of trust receipts from a particular witness/watcher will be looking for a particular AID for that witness/watcher so I don't think there is a need to differentiate between a witness receipt and a watcher receipt.
Duplicitous event log: This should be considered too if it makes sense to also go on-chain. (maybe not necessary for secondary root of trust KELs on Cardano, since the duplicity is already evident - but useful for a tertiary root of trust scenarios to post duplicity from a witness backed KEL)

@iFergal , I like the idea of having Cardano as a secondary root of trust for the Cardano community. Submitting the transactions directly to the ledger instead of the Cardano-backer seems to be a good approach. We'll need to standardize that mechanism and detail how they should be validated when reading the chain. The watcher will play a fundamental role to validate the minted KEL.
I think that a trait telling that the AID is backed in Cardano Mainnet should suffice, since they are meaningful for the Cardano Community that should be aware of the corresponding CIP.  However we should also leave the possibility to move out of Cardano in an future rotation event by adding witnesses (or other trait)
I'll be happy to collaborate on the CIP and work on a watcher that can read and validate KELs submitted as metadata into the blockchain.

@rodolfomiranda @iFergal

However we should also leave the possibility to move out of Cardano in an future rotation event by adding witnesses (or other trait)

Version 2.0 of KERI adds the config trait field, c to rotation and delegated rotation events so that you can change to/from registrar (cardano) backers to regular witness pools with a rotation. Not merely setup at inception.

Thanks both; and apologies for more delayed response.
@SmithSamuelM Would the idea of having an identifier with the RB config trait (and a seal containing CARDANO_MAINNET for example) but no registrar backer identifier work for a KERI agent? (b=[], bt=0) So if an agent understood how to securely read from CARDANO_MAINNET, they would fetch KELs from there and not care about the Cardano address that created the transaction. (maybe the config trait would be LB for ledger backed then... as there's no "registrar")
If we need to keep the registrar backer identifier in line with https://github.com/WebOfTrust/keripy/issues/90 (and possibly for some keripy code reasons) - no issues! Only curious in case we can reduce the footprint on-chain, and set the rules for what to expect in Cardano watcher code. If this is the case @rodolfomiranda I would probably explicitly say that a watcher must expect KERLs (receipted from registrar) and ignore KELs.

@SmithSamuelM Thanks, I would first make sure I understand fully the utility in this context before closing the door to it. :) In this scenario (public permissionless blockchain), we will have public access to KELs protected by the ledger. So I'm curious of there is utility of a declaration made by a registrar that I'm missing.
I guess if the registrar is the entrypoint to a ledger (posts transactions), then it could provide a receipt to the controller that it has seen the KEL, and as such a controller would expect it must be on the ledger after a certain period of time. Not sure if this is a strong enough utility. Mostly because I think we'll have hybrid SSI/crypto wallets that can submit the KEL on-chain without an intermediary registrar - since transactions cost money. And enterprise use cases can run witness pools instead.

It depends on how transactions are entered on the ledger.  It may be that the same key pair for KEL's Contoller AID is the "address" used to enter transactions on the ledger, but then that would only work if the AID was single Sig since most ledgers do not support multisig  and even in the single sig case one woukd have to enter rotation events twice  once for the key pair before the rotation and one after which is entirely problematic. So in general the "address" the enters transactions on the ledger has a different key state than the KELs AID.   Alternatively one could let any address work but then in the case of key compromise there could be multiple inconsistent (duplicitous) copies of the KEL on the ledger at the same time.  So one approach would be to have multiple ledger registrars declared like witness pool with a threshold  and now each registrar is itself highly available because its transactions are backed by the ledger. This protects in case one of the registrars addresses gets compromised which can be recovered from by rotating in a replacement registrar.  So when you consider that any address on a ledger might have its private keys compromised and any AID controller might have its private keys compromised at some time in the past then you start to have to consider how to either recover or protect against duplicity.   As you know were there a surprise quantum attack on key pairs almost no ledger would be safe they would almost all fail catastrophically. So the only thing you can depend on with a ledger is a type of high availability given there is no key compromise ever. Unlike KERI which is duplicity evident by design, Ledgers are duplicity hiding by design. If the private key of a ledger address are compromised there is no way for a verifier to detect it because whatever is written to the ledger is absolute truth.

Alternatively one could let any address work but then in the case of key compromise there could be multiple inconsistent (duplicitous) copies of the KEL on the ledger at the same time.

Any address was the plan I was considering, but only in absence of registrar identifiers. However I understand your point. In case of key compromise of an old rotation key (since current is protected by pre-rotation), the ledger could have duplicitous KELs.
Though I had also intended to have the same "first seen" rule witnesses have, when using a ledger in this setup. First seen next event (on any address) in the order of the ledger wins, others thereafter are discarded and considered to be from old compromised keys.
Not sure if there are any recovery or timing (w/ ledger delay) issues with this approach though. So if there is I would for sure opt to keep registrar identifiers.


ESP32 PINS setup

Where do i setup the pins on ESP 32 that control my devices or measure temperature/humidity e.g. DHT sensor?

Please see the Tutorials for step-by-step instructions.


Console - settings identity provider - first part

Issue
https://gravitee.atlassian.net/browse/APIM-3952
Description
Migration of identity provider tab
Additional context
Screenshot:

📚  View the storybook of this branch here

Could you link this PR to Jira issue ? and add some screen capture ? :)

Done


Fix broken link on Install Tools page

Fixes #39134
Updated page Install Tools

The new link is better.
/lgtm
/approve


gui: fix flaky "load more" comments button

Due to the button start mark gravity, it would break after expansion of a preceding "replies" button.

Is there any point in supporting ytdlp_comments considering how slow and limited it is?

Is there any point in supporting ytdlp_comments considering how slow and limited it is?

The support for yt-dlp commenrs is experimental and not enabled by default. I think it's worth keeping basic support for it just in case the invidious comments will no longer work in the future (which happened in the past).
See also: https://github.com/trizen/pipe-viewer/issues/23


Documentation for FlowCV website

Describe the Feature you want to end
adding Readme file to the site

Expected behavior
It helps in giving great understanding for the fellow contributors and can anvigate easily with interface

Screenshots (optional)

Additional context (optional )

@MohitGupta121 Kindly,assign this to me


Preview function aren't working with Twitter URL

I'm trying to open Twitter preview but it doesn't work.
My code
AnyLinkPreview(
link: "https://x.com/mahmoudanwar74/status/1802647958149632408",
)
I can view the preview correctly on other sites, but this link does not show the preview.
Please advise!

@mostafasany I don't know the reason, but I have checked with 'https://x.com/mahmoudanwar74/status/1802647958149632408/' and it shows a preview. Adding a slash at the end of the URL fixes the issue.

@harshit-kishor2 I tried adding slash at the end of the URL  but it doesn't help

Here is the response ~
A. With slash -
{title: مۭــحۡــمۭــۏد انوُرٍ Mahmoud Anwar (@mahmoudanwar74) on X, description: بلسان لبيب اهو النادى عايش على فلوس #تركى_ال_شيخ يا شوية شحاتين ومتسؤلين يا مهزقيين اسمعوا رئيسكم بيقول ايه يا افقين يا مدلسيين, image: https://pbs.twimg.com/ext_tw_video_thumb/1802596459545575424/pu/img/T8TJSo2OkjQB6pGp.jpg:large, url: https://x.com/mahmoudanwar74/status/1802647958149632408, timeout:<PHONE_NUMBER>}
b. Without slash
{title: x.com, description: null, image: null, url: https://x.com/mahmoudanwar74/status/1802647958149632408, timeout:<PHONE_NUMBER>}
Here is my fetching method-
Metadata? metadata = await AnyLinkPreview.getMetadata(
link: 'your_url',
cache: const Duration(days: 7),
);

Well I'm stuck with this url-
https://www.viator.com/blog/First-Timers-Guide-to-London/l29233
Here i'm getting null.

Well I'm stuck with this url- https://www.viator.com/blog/First-Timers-Guide-to-London/l29233 Here i'm getting null.

I got solution for my issue-
I have used this header property
Metadata? metadata = await AnyLinkPreview.getMetadata(         link: getUri,         cache: const Duration(days: 7),         headers: {             'User-Agent': 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.124 Safari/537.36',             'Referer': 'https://www.google.com/',             'Accept-Language': 'en-US,en;q=0.9',             'Accept':'text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8',             'Connection': 'keep-alive',           }       );

@harshit-kishor2  Using the bellow code return Metadata  but has empty image
link = 'https://x.com/mahmoudanwar74/status/1802647958149632408/';
    Metadata? metadata = await AnyLinkPreview.getMetadata(
        link: link,
        cache: const Duration(days: 7),
       );

Hi, The User Agent change is the fix & one of the contributors submitted the same in their PR which I have merged it today.
Commnity can hope this fix to be included in the next PR.

@sur950  When are the fixes  will be available ?


Missing Types for GNOME Shell imports

This is more a feature re quest than a bug: currently, most GNOME API's and GJS built-in  modules have types through this package, but (unless I'm missing something), GNOME Shell imports are not typed (i.e. imports.misc and imports.ui). I would love to see this implemented! This has made working with GJS infinitely better.

Hi @pcbowers,
I have now added initial support for GNOME Shell Extensions, which should make it easier for others to contribute more types to this project. Since I am currently not working on any extensions, I don't have this in focus. Because imports.misc and imports.ui are written in JavaScript, these types cannot be automatically generated and must instead be mostly written by hand. I have done this as an example for imports.misc.extensionUtils and also added an example.
If you are creating the corresponding types for your project anyway, we would be very happy if you could send them back to us. For this, they would just have to be inserted here.

I just noticed this as well, and it seems that these types are included unconditionally, see https://github.com/sammydre/ts-for-gir/issues/101#issuecomment-1385116676
Would you mind to add an option to turn the shell types off, to have correct types in a plain Gjs environment?

@swsnr done

To enable GNOME Shell Types you need to pass the new option --gnomeShellTypes, now.
You can reuse the config file from the GNOME Shell Example, in which the girDirectories option must also be modified to include all types needed for GNOME Shell extensions:
module.exports = {
    environments: ["gjs"],
    modules: ["St-1.0"],
    girDirectories: [
        // General gir files
        '/usr/share/gir-1.0',

        // GNOME Shell gir file (package: gnome-shell-common / gnome-shell)
        '/usr/share/gnome-shell',
        '/usr/share/gnome-shell/gir-1.0',

        // GNOME Shell gir file dependencies on Fedora Workstation 36 (package: mutter)
        '/usr/lib64/mutter-10',

        // GNOME Shell gir file dependencies on Fedora Workstation 37 (package: mutter)
        '/usr/lib64/mutter-11',

        //  GNOME Shell gir file dependencies on Ubuntu 22.04 (package: libmutter-10-dev)
        '/usr/lib/x86_64-linux-gnu/mutter-10',

        //  GNOME Shell gir file dependencies on Ubuntu 22.10 (package: libmutter-11-dev)
        '/usr/lib/x86_64-linux-gnu/mutter-11',
    ],
    pretty: true,
    moduleType: "commonjs",
    gnomeShellTypes: true,
}

Dont know if this is the best place to comment about this but by using that example folder (the one on https://github.com/gjsify/ts-for-gir/tree/main/examples/Gjs/gnome-shell-hello-world) the imports don't really work. I had to add:
"paths": {
    "@imports/*": ["../@types/*"]
 }

To the compiler options of the tsconfig.json

Not sure if I did it right, but imports.misc.extensionUtils.getSettings() function wasn't generated in the ExtensionUtils.d.ts.
Here's the command I used for reference:
yarn ts-for-gir generate Gtk-3.0 --generateAlias --gnomeShellTypes

@gilbertorconde @sansmoraxz @swsnr @pcbowers I have moved the TypeScript types for the GNOME Shell to this repository: https://github.com/gjsify/gnome-shell.
The types are written by hand, so if you find errors that can be corrected quickly by hand, I would be happy about a PR/MR, but a new issue is also welcome.


Allow a custom time provider in TracerProviderBase

This mirrors the capability in WebTracerProvider.
Which problem is this PR solving?
I have an opentelemetry implementation using the Dart library (thanks!). I've noticed clock skew between my web/flutter client and dart backend. I have clock synchronisation in the client. This PR allows me to provide my own TimeProvider which exposes synchronised time time, nicely aligning traces between app and server.
The WebTracerProvider constructor does allow providing a TimeProvider, but cannot be used in non-web platforms.
Fixes # 99 which is expanded in opentelemetry-js 1652
Short description of the change
Simply provide a named parameter to override the default TimeProvider in the TracerProviderBase, as is done in the WebTracerProvider.
How Has This Been Tested?
I have added a unit test demonstrating a custom time provider.
Checklist:

[X] Unit tests have been added
[ ] Documentation has been updated

The README.md references a TimeProvider for WebTracerProvider. Should I update for TracerProviderBase?

Security Insights
No security relevant content was detected by automated scans.
Action Items

Review PR for security impact; comment "security review required" if needed or unsure
Verify aviary.yaml coverage of security relevant code

Questions or Comments? Reach out on Slack: #support-infosec.

This is my first pull request!

QA +1 CI is sufficient

@Workiva/release-management-p


Add Genius as an option for annotation

http://genius.it/peerj.github.io/paper-now

Disable hypothes.is when on the genius.it domain, as they both perform similar functions.

Added Genius as the default annotation tool.


Note to Validators

Hi,
I'm operating a relayer. If you are operating a validator, it is very important that you:
systemctl enable systemd-timesyncd
systemctl start systemd-timesyncd

please.
If you do not, there are time drift errors, and well, the Hermes default of five seconds is really pretty generous.  We should be less than five seconds apart.

Oct 12 09:04:56 archive hermes[741991]:    0: GRPC call return error status status: InvalidArgument, message: "failed to execute message; message index: 0: cannot update client with ID 07-tendermint-1457: failed to verify header: invalid header: new header has a time from the future 2021-10-12 07:04:50.046283195 +0000 UTC (now: 2021-10-12 07:04:43.209109453 +0000 UTC; max clock drift: 5s): invalid request", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc"} }

Per that ibc-rs issue, my reading is that increasing this time moderately has ~no risks / downsides. Its mostly about tolerating clock drift on smaller scales. (Or at least thats my reading, I am admittedly horribly under-informed here)

Whats the sitaution like now? I think we're going to be more able to get this resolved via pinned announcements on the discord/telegram. We can coordinate if you'd like to make a discord announcement

This is still happening, but less often, and may have been related to fee calculation in hermes..... but the same thing would happen with the Go relayer, too.


Support new Postgres "B" suffix for bytes

Postgres commits 6e7baa3227 and b06d8e58b5 added a new unit suffix "B"for memory parameters for bytes.

This one is rather important for anyone wishing to go to PG 11, and should be prioritized.

Please merge this one :)

Is there any ETA on this merge?


assert.equal() deprecation warning shown when using strict import

Issue Type: Bug

Create a new JavaScript file.
Import the strict set of Node.js "assert" module.
Use assert.equal().
Observe crossed out word with deprecation message.

VS Code version: Code 1.50.1 (d2e414d9e4239a252d1ab117bd7067f125afd80a, 2020-10-13T14:53:05.704Z)
OS version: Darwin x64 19.5.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz (16 x 2300)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
2, 2, 1

Memory (System)
16.00GB (1.82GB free)

Process Argv
-psn_0_12762155 --crash-reporter-id bb3c5ac4-5dd5-4dc7-a1e1-bfcc15bc24b8

Screen Reader
no

VM
0%

I don't think this is a TS issue per se, I see that the definition file has been updated in the repository, VSCode just hasn't downloaded the updated version...

You can delete the containing folder; it's a cache and will be automatically re-fetched.

You can delete the containing folder; it's a cache and will be automatically re-fetched.

I was able to do that as a workaround. I'm not so sure that should be seen as a solution though. Perhaps it would be worthwhile to add a "Clear TS typings cache" option to VSCode, as the folder where I found this file is new to me, took some time to find, and that was after I'd narrowed it down to a typings issue.

I had the same symptom.  An older version of @types/node was in my node_modules directory (apparently a dependency of some other module).  Doing npm install @types/node from the project directory got a newer, fixed version.  VSCode refreshed the editor within a second or two, and equal was no longer marked deprecated.

I had the same symptom.  An older version of @types/node was in my node_modules directory (apparently a dependency of some other module).  Doing npm install @types/node from the project directory got a newer, fixed version.  VSCode refreshed the editor within a second or two, and equal was no longer marked deprecated.


Validate zappa_settings.json before uploading

It's quite easy to forget a comma or other simple formatting mistakes. Please consider validating settings.json prior to full zip/upload/deploy to avoid issues proactively.

On the client side, we actually use hson rather than json. Should we use that server side as well? I've been holding off on that as it seems server side settings should be more strict.

Wait, I'm actually confused by what you mean by this. Can you give me an example?

It came up in slack - essentially the problem is that if you have a syntax error in your zappa_settings.json file, the error doesn't show up until you actually run the code on lambda, and the error it gives isn't very helpful in chasing down the actual problem.
[1471201248450] need more than 1 value to unpack: ValueError
Traceback (most recent call last):
  File "/var/task/handler.py", line 249, in lambda_handler
    return LambdaHandler.lambda_handler(event, context)
  File "/var/task/handler.py", line 107, in lambda_handler
    return cls().handler(event, context)
  File "/var/task/handler.py", line 123, in handler
    module, function = whole_function.rsplit('.', 1)

sees a missing comma in his zappa_config

I think this is taken care of?


fix: add missing dep flatted (fixes #3222)

Check that your description matches the automatic change-log format:
http://karma-runner.github.io/latest/dev/git-commit-msg.html
then delete this reminder.

I signed it!


Add a postConstruct( ) method to result maps

This will allow for adding/modifying properties of an object after construction.

This one is tricky because it is difficult to figure out when the object is fully constructed. As more result sets come in, they could be modifying existing objects.

After much use, it appears that this feature is not really needed.


Linting libraries phase 1 - continued

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/datorama/akita/blob/master/CONTRIBUTING.md#commit
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?
[ ] Bugfix
[ ] Feature
[x] Code style update (formatting, local variables)
[x] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[x] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

Does this PR introduce a breaking change?
[ ] Yes
[x] No

Additional info
Part of #401

@NetanelBasal have you had some time to look at this? Can I help somehow?

Hi, I'm not sure what's the status here?

I updated it with master (at the time) and fixed the remaining linting rules (and relaxed them a bit)
The changes shouldn't change how any business rules and only be formatting/flavor changes

Ok, I'll go over it later on. Thanks


chore(main): release 1.0.3

:robot: I have created a release beep boop
1.0.3 (2024-07-07)
Bug Fixes

update template (b4c62b9)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v1.0.3
:sunflower:


Issue from   flutter  WebSockets

connecting my url : ws://<IP_ADDRESS>:6055  is  failed, but test in websocket.org is ok !

please what's problem with me ?

mycode :
import 'package:flutter/foundation.dart';
import 'package:flutter/material.dart';
void main() => runApp(new MyApp());
class MyApp extends StatelessWidget {
@override
Widget build(BuildContext context) {
final title = 'WebSocket Demo2';
return new MaterialApp(
title: title,
home: new MyHomePage(
title: title,
channel: new IOWebSocketChannel.connect('ws://<IP_ADDRESS>:6055'),
),
);
}
}
class MyHomePage extends StatefulWidget {
final String title;
final WebSocketChannel channel;
MyHomePage({Key key, @required this.title, @required this.channel})
: super(key: key);
@override
_MyHomePageState createState() => new _MyHomePageState();
}
class _MyHomePageState extends State {
TextEditingController _controller = new TextEditingController();
@override
Widget build(BuildContext context) {
return new Scaffold(
appBar: new AppBar(
title: new Text(widget.title),
),
body: new Padding(
padding: const EdgeInsets.all(20.0),
child: new Column(
crossAxisAlignment: CrossAxisAlignment.start,
children: [
new Form(
child: new TextFormField(
controller: _controller,
decoration: new InputDecoration(labelText: 'Send a message'),
),
),
new StreamBuilder(
stream: widget.channel.stream,
builder: (context, snapshot) {
return new Padding(
padding: const EdgeInsets.symmetric(vertical: 24.0),
child: new Text(snapshot.hasData ? '${snapshot.data}' : ''),
);
},
)
],
),
),
floatingActionButton: new FloatingActionButton(
onPressed: _sendMessage,
tooltip: 'Send message',
child: new Icon(Icons.send),
), // This trailing comma makes auto-formatting nicer for build methods.
);
}
void _sendMessage() {
if (_controller.text.isNotEmpty) {
widget.channel.sink.add(_controller.text);
}
}
@override
void dispose() {
widget.channel.sink.close();
super.dispose();
}
}

@laozhang700 Did you manage to solve the issue? Do you use flutter stable v1.9.1+hotfix.2 and web_socket_channel 1.0.15?

Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.


Embed a visualize dashboard for envoy is possible？

If you are reporting any crash or any potential security issue, do not
open an issue in this repo. Please report the issue via emailing
<EMAIL_ADDRESS>where the issue will be triaged appropriately.
Title: Embed a visible dashboard for envoy is possible？
Description:

It is difficult to read the configuration of the envoy, I develop a dashboard for the envoy. I want to know if people need it.

[optional Relevant Links:]

https://github.com/saltbo/seenvoy

cc @mattklein123 @alyssawilk @htuch

+1 this is very cool. I am a bit torn as it would be more convenient for us to have this tightly integrated, and having a richer UI expression integrated into the stats declaration can help keep it in sync with the code a little bit easier than having it be in its own repo.
I was going to re-open #19546 soon; just need a couple small tweaks. Now that I'm through a long planning cycle and just got back from vacation I am hoping to clean this up.

Thank you for your recognition. I do want to integrate more closely with the envoy. For example, maybe we can use seenvoy instead of the current HTML admin page. However, I also have some concerns because seenvoy is
developed using SPA. As a result, it may be larger in size than the SSR HTML admin page.

It's easy to integrate SPA like https://github.com/saltbo/seenvoy/blob/master/main.go
I want to transfer the saltbo/seenvoy to the envoyproxy/dashboard. Then compile the dist directory of dashboard into envoy

Take a look also at https://github.com/envoyproxy/envoy/pull/18670 - that won't be functional right now but look at the description and screenshot. I think you need deeper C++ integration to build a usable view of the stats like that for, say, 100k clusters, which would be 10M stats. I want to get https://github.com/envoyproxy/envoy/pull/19546 merged first though and then we can get a high-performance hierarchical view.

My skill in C++ is weak. I do not intend to go deep into the development of C++ in the short term. I hope to develop the front code using envoy API.

Thinking about this further, a couple of options look feasible.
You've clearly got a lot of value-add in this visualization (css, js etc), but the Go part is pretty small. Would you consider translating that to C++ and integrating it with admin.cc etc? The benefit is that anyone that compiles Envoy (without the flag to disable admin HTML) would get your visualization for free, without changing their deployment.
Another possibility is to leave the visualization server outside the Envoy binary as you have it. We could still access high-cardinality structures but we'd have to document and stabilize the interface between the Go server and the C++ server. That would make it a little more complicated to evolve over time as you wouldn't be able to upgrade production installations of the two servers concurrently, so it would effectively become an API surface. Anyone wanting to use this would need to run parallel Go servers -- or maybe just one Go server that can point to any Envoy?
I don't think we could use that as it would complicate our already-complex deployment so we'd probably keep a custom one in  in C++.
So from my perspective the lowest-friction path is to translate your 90 lines of Go into C++ and integrate. WDYT?

Yes, I agree.  I would translate the 90 lines of Go into C++ and integrate it with admin.cc.

Great! You might want to scan through https://github.com/envoyproxy/envoy/pull/19546 (which I just opened for review; it was previously in draft) which will help you get familiar with the mechanism it adds to embed CSS and HTML files into the C++ binary at build time, simplifying deployment. It will also show you some of the hook-points for your transliterated Go. I don't think that part will be complicated once you know where to put it. But mostly look at the BUILD files for how to embed CSS/HTML into C++ constants.
One question on your impl: do you use 3rd party JS libraries? That might be an issue if you are referencing (say) jquery servers from inside a private network that can't reach the internet.

Don't worry, I'm not using 3rd party JS libraries.
#19546 Thank you, I will try it.

One other thing to keep in mind is that for the non embedded parts we could potentially bundle what is needed in the full sized (ubuntu) docker images. That would make it easy to try/use for the average user. IMO we should keep it out of the slim (distroless) images. cc @phlax

That's a good point -- Docker probably makes it feasible to serve JS & CSS
from files provided alongside the binary.
Is it sufficient, though, to rely on the compile-time option to cut out the
HTML entirely? Or do you want to be able to be able to enable the HTML but
leave the text out of the binary? The total amount of text is pretty small
compared to the binary, and would be in 'text' space when declared as a
static constexpr char[].
On Tue, Jul 12, 2022 at 10:50 AM Matt Klein @.***>
wrote:

One other thing to keep in mind is that for the non embedded parts we
could potentially bundle what is needed in the full sized (ubuntu) docker
images. That would make it easy to try/use for the average user. IMO we
should keep it out of the slim (distroless) images. cc @phlax
https://github.com/phlax
—
Reply to this email directly, view it on GitHub
https://github.com/envoyproxy/envoy/issues/22099#issuecomment-1181857098,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAO2IPN22SXRF3YXR3KLLP3VTWA4DANCNFSM53GZ4NTQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Is it sufficient, though, to rely on the compile-time option to cut out the
HTML entirely? Or do you want to be able to be able to enable the HTML but
leave the text out of the binary? The total amount of text is pretty small
compared to the binary, and would be in 'text' space when declared as a
static constexpr char[].

IMO it's probably fine to just have all of it be guarded by the compile time flag. As long as people can compile it out I'm fine with having it all be under that guard.
In terms of all the extra stuff that would be required outside the binary (if we don't compile it in, which is probably simpler for dev anyway), IMO would could just have bundle/install instructions and then just auto bundle/install in the docker image?

I think dev is not too bad when compiling it in; you can also tweak the build to allow reading files when serving so you can edit them without recompiling or even restarting Envoy.

I have a high level question, do we really need to add a web UI to Envoy itself?
Embedding fancy dashboard will increase the binary size heavily, while a simple web page is too difficult to use for ops. I think Envoy should only expose RESTful APIs, and leave to other developers to setup their own dashboards, or separate into a new project like envoy-webui owned by ourselves.
For some further thoughts, we can add a tab dashboard into the homepage of Envoy, where we can connect to the Envoy admin and view or modify these configs with these fascinating graphs.
CC @mattklein123 @jmarantz

Embedding fancy dashboard will increase the binary size heavily, while a simple web page is too difficult to use for ops. I think Envoy should only expose RESTful APIs

i would generally agree with this point - i think we risk various kinds of bloat, and additiional maintenance including a UI ourselves, whereas an API could be more powerful, and agnostic to the UI tech etc

i guess the upside to embedding a UI is that you dont need to worry about a separate process/container/networking/etc
re API - realizing that is what we have already - i guess there is already tooling that is hooking into this

I found the config_dump API is so slow when the config size is big. This causes seenvoy to load very slowly. I think maybe need a cache for it. but the frontend tech stack maybe not support, eg: localStorage is limit 5MB. Maybe must depends on a backend server to resolve it?
What do you think about it?

Or implement the cache for config_dump API, and use a querystring to refresh it?

@saltbo can you add a separate issue for config_dump being slow? This is parallel to https://github.com/envoyproxy/envoy/issues/18675 which is largely addressed for non-Prometheus cases. Landing https://github.com/envoyproxy/envoy/pull/19898 would finish it off.
I think the solution to slow endpoints is streaming and possibly also filtering. I don't think it should be necessary to add a cache, as that would (a) risk staleness confusion (b) still be slow on first query (c) trap a bunch of memory.

Maybe it's different. For the frontend, It needs to parse the JSON data, if we use the streaming, Although the data can be received, it is not complete JSON data and still cannot be parsed, still waiting for received done...

I found the influxdb to save the config_dump data, I will try it.

There are two challenges:

the server bogs down buffering up the entire config as text, locking up the main thread for a significant time, and holding a significant amount of memory. During this process no other main-thread activities occur, including config updates, stats sinks, and other admin requests
browser overhead parsing that monolithic chunk of text and generating DOM structures to present it in a usable fashion

Both of these can be addressed by structuring the server endpoints to deliver consumable chunks and a UI to progressively disclose that so that users can more rapidly get to what their looking for compared to sifting through a gigantic text dump.
In any case I think it makes sense to discuss the problem -- as you perceive it -- in a separate issue.

I use influxdb to save the data from config_dump API, then the seenvoy logic is based on it. Now the user experience is very great.


Fix evaluating in pure evaluation mode

With #712, I ended-up needing to ensure evaluation was as-expected when done in pure evaluation mode. So this started with the tooling to evaluate in pure evaluation mode...
... except that pure evaluation is kind of awful to use outside of Flakes. So I also added another helper that does unsavoury things in Nix to work around the fact that pure evaluation ends-up adding the repository to the store for every edit. That helper should not be considered a safe interface to use, and only used as a development help.
 $ nix-instantiate support/nix/forbid-builtins.nix --argstr system "x86_64-linux" --arg path ./examples/hello --arg  device ./devices/pine64-pinephone -A outputs.default

The "actual" check for pure evaluation should be done with the other helper.
 $ support/nix/pure-eval.sh --argstr path "examples/hello" --argstr device "uefi-x86_64" -A outputs.default

Note that bin/hydra-eval is now working with pure eval, so that is the actual proper check for all intents and purposes. Though it would be better the results were visible on contributions... Something to consider adding to the

So after writing tooling to check things were proper, and comparing with the existing state before any fixes, I ended-up having to write fixes to understand how and why it was failing in the other PR.
In addition to that, I also ended-up implementing the additional fixes for the example systems. They also needed to be updated.
So the main issue in #712 was how keeping the pkgs and system coherent is not trivial. It ended-up leading to builtins.currentSystem being used even for cross-compilation.
I ended-up further de-duplicating argument handling in the entrypoints. And to prevent system to lack coherence with pkgs's system, it cannot be passed at the same time. TBF, system as an argument here is only needed for pure-evaluation in entrypoints of this repo when also wanting to use the pinned Nixpkgs.
cc @RossComputerGuy

:thinking: SIGKILL, AFAICT, on the CI / Instantiation action... Ugh.

I'll move the whole issue about fixing the release.nix instantiation into another PR... It's not supposed to be the changes here that causes the new failures. I've checked locally and the evals are in the same ballpark of sizes on development... So I'm not sure exactly why it's now failing, since OOMs as experienced here don't leave much to go on about.

Thank you for trying to fix this, I'll look into it tonight after work. Been kinda busy recently.


Add Gunicorn to Docker setup

We should add gunicorn to our stack to benefit from mature process management, as uvicorn by default only comes with 1 process.
Impact
Will mean load testing results are more realistic and useful.

We're going to postpone action on this ticket until the Fides repositories have been unified, to minimise the amount of overall refactoring required across the projects.


Add retry logic(bind and group) for ikea button

CHAD-9927

Under testing, whether this commit is really necessary.


[LBT][GHA] combine build and test jobs

LBT divides the workflow into has two jobs: build and test. Only the
test job will comment on the PR when it fails.  If the build job fails,
the PR owner is left in the dark, pondering why their PR isn't landing.
This commit is a temp fix to combine the jobs to leverage the comment
step.  The proper long term fix, however, is to generalize this comment
step into a standalone action so that it can be reused in other
jobs or workflows.
Case in point,  #3103 is trying to land aaa5819.

The build failed in https://github.com/libra/libra/runs/538101233?check_suite_focus=true

No comment posted in the PR alerting the owner about the breakage

@bors-libra delegate+

:v: @sausagee can now approve this pull request

When build fails there seem to be no feedback on why did it fail. Do we want to do something about it? Is there way to fetch, say, last 50 lines of build log and include it into job?

When build fails there seem to be no feedback on why did it fail. Do we want to do something about it? Is there way to fetch, say, last 50 lines of build log and include it into output of build script?

AFAIK, there is no direct access to stdout or stderr from the previous step.  We run into the same situation with the workflow on CircleCI.  In the LBT case here, I think we can work around it by capturing the last X number of lines and set it as the output of the step.

@bors-libra r=andll

:pushpin: Commit 497e24f has been approved by andll

:hourglass: Testing commit 497e24f924e40f6cc8bc8054ccac532eecac5af9 with merge 7a943fdd5534e7e971828833fe42ca8de0af9754...

@bors-libra r-
Found issue with workflow.

@bors-libra r=andll

:pushpin: Commit 8bf4bb6 has been approved by andll

:hourglass: Testing commit 8bf4bb628ee0f58fc7f472a19a0afaed305991ae with merge e0087929e3c061f433a58bb7b9d5819115a6f9f6...

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: andll
Pushing e0087929e3c061f433a58bb7b9d5819115a6f9f6 to master...


Checking ID_LIKE - KDE Neon support

Environment data
.NET Command Line Tools (1.0.0-preview2-003131)
Product Information:
Version:            1.0.0-preview2-003131
Commit SHA-1 hash:  635cf40e58
Runtime Environment:
OS Name:     neon
OS Version:  16.04
OS Platform: Linux
RID:         neon.16.04-x64
Steps to reproduce
Attempt to start the debugger in VSCode
Expected  behavior
The debugger will start
Actual behavior
The VSCode log will display Error: Unsupported linux platform
This code file checks the platform by looking at os-release. My OS release looks like this:
NAME="KDE neon"
VERSION="5.8"
ID=neon
ID_LIKE="ubuntu debian"
PRETTY_NAME="KDE neon User Edition 5.8"
VERSION_ID="16.04"
HOME_URL="http://neon.kde.org/"
SUPPORT_URL="http://neon.kde.org/"
BUG_REPORT_URL="http://bugs.kde.org/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial

Though my distro is clearly Ubuntu based, the code only checks the id property. Perhaps the switch could be updated to check the if ID_LIKE contains a recognized platform, if it exists, or Ubuntu-based distros like Neon could be mapped to the Ubuntu platform.

@0xFireball Have you tried using the Ubuntu 16.04 version of the .NET CLI? I can build you a custom .vsix that will look at ID_LIKE/VERSION_ID assuming that the Ubuntu 16 CLI actually works on KDE Neon.

KDE Neon is LTS Ubuntu with KDE, unlike Kubuntu, which is the latest Ubuntu with KDE.
Everything should be fully compatible.
A custom VSIX would be really helpful, thanks.

Maybe you could change this in the actual code, assuming everything else works as expected

@0xFireball yes, that is definitely my goal. I just want to verify that I am actually resolving the issue before I submit a checkin a fix.

@0xFireball I am attaching a new version of the C# extension to this work item:
csharp-1.5.0-dev-kdeneon.vsix.renamed.zip

Download the file
Remove the '.renamed.zip' part of the extension
In VS Code: View->Extensions
Click the '...' to bring up the additional command menu and select 'Install from VSIX...', and navigate to the downloaded file
Confirm that downloading assets succeeds and debugging works

Thanks!
Gregg

@0xFireball did you have a chance to give that .vsix a try?

Not yet, but I will later today

@0xFireball: Does the latest release (shipped yesterday on the VS Marketplace) fix the issue for you?

I'm going to go ahead and close this. Let us know if the latest release doesn't address this issue.

sorry about how long it took me to get back :( @DustinCampbell
thanks for your quick fix! it works perfectly, just like on Windows :tada:

Excellent! Thanks for letting us know.


Adding gymnasticon.json to boot makes 2 gymnasticon services run at startup

I know this is a work in progress as you’re both adding stuff on a daily basis and it’s not a big issue- more of a comment.
Current image 1.4 with keiser added written to sd card and gymnasticon.json added for keiser bike before first boot makes 2 gymnasticon services run on boot
(I’m assuming that’s the case - SSH login it’s shows the gymnasticon logo twice on the screen.)
Thanks for all the work on this to you both @ptx2 @chriselsen it’s working great.

There are actually two gymnasticon services that get started on boot:

gymnasticon-mods: That service pulls in the JSON config file from /boot to /etc. It should terminate very shortly after boot.
gymnasticon: The actual service that runs the "gymnasticon" binary.

After login you can check with ps ax if there is more than 1x gymnasticon process running.
Will need on check the 1.4 image to see about the SSH login. The gymnasticon icon comes from the /etc/motd file and I haven't seen any changed to that file.

Ah! I’ve only tried/seen it first boot after adding the json to boot- just rebooted the pi and it’s now 1 logo after login.


LEDs not changing in mode 6

When using mode 6, it seems the rest of the settings are just ignored. When the program starts with mode 6(temperature controlled) configured, it'll just show a yellowish-green color, no matter what color is defined in the settings and no matter what temperature the system runs on.
I'm running this on a MSI GTX 1060 Gaming 6G, tested the mode with Kombustor / Afterburner running to read and ramp up the temperature.

Okay, seems I figured that out myself. It were multiple things at once - first of all, it looks like the dragon LED won't give out full RGB but instead only green, yellow and red. I'm not sure if that's a limitation of the card or the program though.
Also, I had to set OverwriteSecurityChecks to true. That option lacks documentation on what it actually does, "disables device ID checking" is a little broad.
Lastly, I expected the mode to do something else, just when reading the code I realized this would go from green to red and not shift the brightness from 0 to 100% when the temperature changes, which would cooler for my general colour-scheme.


ensure that custom build paths can have their permissions fixed

Issue
The Buildkite BuildPath config allows us to set a custom build path. However, this build path is hardcoded to /var/lib/buildkite-agent/builds in the fix-buildkite-agent-builds-permissions script, which results in this script not setting permissions properly.
We ran into this issue when we set a custom build path, and subsequently noticed that some docker artifacts on host could not be cleaned up properly by buildkite-agent, because some files in the workspace (residual artifacts of docker) were owned by other users.

Fix
The fix is to add the build path as a parameter to the fix-buildkite-agent-builds-permissions script.

Test Plan
docker-compose -f docker-compose.unit-tests.yml run unit-tests ran successfully

Ooh, this is an interesting edge to the problem! It's very locked down because we don't want to allow chmod-ing or chown-ing arbitrary file paths. Is there a way that $BUILDKITE_BUILD_PATH can be controlled and changed before this script is run which might allow running this script on arbitrary paths?

I don't believe so. As I understand it:

$BUILDKITE_BUILD_PATH is set on the env of the bootstrap process.
the permissions-fixing script runs in the agent env hook, which should run prior to all other hooks per the docs here

Since there's no user-runnable code or hooks that can modify the env of the buildkite-agent bootstrap process prior to the agent env hook, I don't think it's possible to remap $BUILDKITE_BUILD_PATH for a running job.

We remain a bit nervous about this @albertywu, mainly the risk of us overlooking a way for BUILDKITE_BUILD_PATH to be changed and arbitrary files to be chmod.
I believe the root issue that led to this PR was exploring this was exploring ways to use instance local storage for the builds directory to improve performance. Work that we started in #557, but haven't managed to land yet. We'd really love to get that merged though, it's a great feature that will be useful to many customers.
I think our ideal path forward would be to re-visit #557 and allow stacks to opt in to using instance local storage, without a need to customise the build path or change fix-buildkite-agent-builds-permissions.


handle api deprecation

In a near future we may need to deprecate some version of the api.
We have to decide of an http response to notify the borg user of a future deprecation of the api and possibly an api which is non available anymore.
This may required updating api response with something like:
valid response
{
    "status": "OK",
    "data": {/* data response */}
}

valid response with deprecation warning
{
    "warning": "this api version is deprecated and stop working the 31 december 2016, please update borg",
    "status": "OK",
    "data": {/* data response */}
}

error response for an api not available anymore
{
    "status": "ERROR",
    "error": "you tried to use a version of the api wich is not anymore available, please update borg."
}

Should we use error codes perhaps?

why not, I just wanted to make at least deprecation a special case that we can catch in a high level way.

http://stackoverflow.com/questions/13884141/convention-for-http-response-header-to-notify-clients-of-deprecated-api
Seems like status codes are fine for already deprecated APIs but not ones which are 'soon to be deprecated'

Closing this, since the borg api already handles this


Mention strictPropertyInitialization requires strictNullChecks

Fixes https://github.com/Microsoft/TypeScript/issues/23659

thanks!

Thanks @HerringtonDarkholme !


Add unit test for SQLTokenGenerateEngine

Pull Request Test Coverage Report for Build 8763

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 61.67%

Totals

Change from base Build 8757:
0.0%

Covered Lines:
8463

Relevant Lines:
13723

💛  - Coveralls


Recent alexg changes

Cherry-picking two recent PRs in Cesium into our fork:

Adding an event to track tile load progress
Adding the ability to dynamically enabled/disable feature picking in imagery providers that support it.

No idea what Travis is on about...


Add NEAR coin definition

returns empty tx now

Are you going to continue current PR or merge step by step?

Step by step, will query real txs when mainnet


[LPIF] Regression script is broken in 0.9.5

While the smoke test is properly defining LPIF_DIE_A_PL_PROTOCOL and LPIF_DIE_B_PL_PROTOCOL macros and running to completion, the regression script is generating configs without these macros defined causing compilation to fail for all test cases.

Fixed in 0.9.6

Michael is able run nightly so closing this issue. Michael re-open if this is still an issue.


Valgrind reports allocated mem at close

I ran valgrind on some code I had written and found that some memory isn't deallocated on close. This probably doesn't matter unless you keep closing/opening the X lib a LOT, but it's nice to tidy up after ourselves ;). I used x11_dl, haven't checked x11.
Of course it might be a leak in X, or some mem that can only be allocated once, in which case it doesn't matter.
Valgrind report
==4119== Memcheck, a memory error detector
==4119== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==4119== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
==4119== Command: ./target/debug/main
==4119==
==4119==
==4119== HEAP SUMMARY:
==4119==     in use at exit: 32 bytes in 1 blocks
==4119==   total heap usage: 136 allocs, 135 frees, 83,124 bytes allocated
==4119==
==4119== 32 bytes in 1 blocks are still reachable in loss record 1 of 1
==4119==    at 0x4C2EF35: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==4119==    by 0x4E3A63B: ??? (in /usr/lib/libdl-2.26.so)
==4119==    by 0x4E39F21: dlopen (in /usr/lib/libdl-2.26.so)
==4119==    by 0x148E98: x11_dl::link::DynamicLibrary::open (link.rs:90)
==4119==    by 0x149391: x11_dl::link::DynamicLibrary::open_multi (link.rs:119)
==4119==    by 0x14A6C6: x11_dl::xlib::Xlib::open (link.rs:57)
==4119==    by 0x11C1A8: main::run (main.rs:7)
==4119==    by 0x11CBB6: main::main (<quick_main macros>:4)
==4119==    by 0x17E6DC: __rust_maybe_catch_panic (lib.rs:99)
==4119==    by 0x17811B: try<(),closure> (panicking.rs:459)
==4119==    by 0x17811B: catch_unwind<closure,()> (panic.rs:361)
==4119==    by 0x17811B: std::rt::lang_start (rt.rs:59)
==4119==
==4119== LEAK SUMMARY:
==4119==    definitely lost: 0 bytes in 0 blocks
==4119==    indirectly lost: 0 bytes in 0 blocks
==4119==      possibly lost: 0 bytes in 0 blocks
==4119==    still reachable: 32 bytes in 1 blocks
==4119==         suppressed: 0 bytes in 0 blocks
==4119==
==4119== For counts of detected and suppressed errors, rerun with: -v
==4119== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

It's probably caused by ::std::mem::forget(lib); at link.rs:60.

Hi, no problem! The output is in the <details> tag, unless you mean something else?

I'm not sure it's such a major problem to be honest, maybe just leave the issue open?


[SPARK-40089][SQL ] Fix sorting for some Decimal types

What changes were proposed in this pull request?
This fixes https://issues.apache.org/jira/browse/SPARK-40089 where the prefix can overflow in some cases and the code assumes that the overflow is always on the negative side, not the positive side.
Why are the changes needed?
This adds a check when the overflow does happen to know what is the proper prefix to return.
Does this PR introduce any user-facing change?
No, unless you consider getting the sort order correct a user facing change.
How was this patch tested?
I tested manually with the file in the JIRA and I added a small unit test.

good catch ! cc @HyukjinKwon @dongjoon-hyun  @cloud-fan

good catch! Is this a long-standing bug? cc @hvanhovell @somani @maryannxue

good catch! Is this a long-standing bug? cc @hvanhovell @somani @maryannxue

According to git blame it has been at least 7 years (Spark 1.5).
https://issues.apache.org/jira/browse/SPARK-9529

Is there a good way to kick the build to retry? the failure appears totally unrelated to this patch.

Is there a good way to kick the build to retry?

you can push an empty commit

@cloud-fan could you please take another look?

lgtm

thanks, merging to master/3.3/3.2/3.1!


Intermittent conda validation failure due to out-of-order messages

This one is going to be tricky to track down. We are seeing intermittent failures with conda package validation on Linux that appear to be from out of order messages. The failure log looks like this:
+ pwsh src/conda-recipes/iqsharp/test.ps1
ssssssssssFs
======================================================================
FAIL: test_kernel_info (__main__.MyKernelTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/vsts/conda-bld/iqsharp_1642095301057/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_/lib/python3.7/site-packages/jupyter_kernel_test/__init__.py", line 44, in test_kernel_info
    validate_message(reply, 'kernel_info_reply', msg_id)
  File "/home/vsts/conda-bld/iqsharp_1642095301057/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_/lib/python3.7/site-packages/jupyter_kernel_test/messagespec.py", line 172, in validate_message
    nt.assert_equal(msg['parent_header']['msg_id'], parent)
AssertionError: '1ca1d670-e7c32e6cc6a6cc3aacd24a60_2' != '1ca1d670-e7c32e6cc6a6cc3aacd24a60_3'
- 1ca1d670-e7c32e6cc6a6cc3aacd24a60_2
?                                   ^
+ 1ca1d670-e7c32e6cc6a6cc3aacd24a60_3
?                                   ^
System.Management.Automation.RemoteException
System.Management.Automation.RemoteException
----------------------------------------------------------------------
Ran 12 tests in 4.520s
System.Management.Automation.RemoteException
FAILED (failures=1, skipped=11)

It seems to have started cropping up only recently, and sometimes passes if the test case is rerun. The specific assert comes from the upstream jupyter_kernel_test package, and the difference in final number indicates that a message with the wrong count was received (note the identifier matches, which points toward out of order).
As a first step we should consider finding a way to update the powershell scripts for the test such that other log info does not get lost when the session disconnects with System.Management.Automation.RemoteException.
See two instances of this failure in the e2e build logs here and here.
@kuzminrobin and @cgranade FYI

May be related or not:
Conda build mac / Testing IQ# conda packages:
See here and earlier attempt here.
These are different attempts of the same pipeline. The failures look different, but in the same stage.

One more attempt for my branch has succeeded, but another run of main has failed in the same manner as for my builds.

It looks like at least some of these failures are actually #510; there seem to be two different issues here, neither of which reproduces locally.


fix(ChangeStream): whitelist resumable errors

Description
Merging resumable error whitelist related changes from 3.6 - the goal is to rebase #2333 off these changes once merged into 3.5.
NODE-2478
NODE-2522
NODE-2565
What changed?
Are there any files to ignore?

@emadum please make sure to update the ticket to indicate that this was fixed in 3.5.8 instead of 3.6


Zero grad in residual vq

🐛 Bug Report
Zero grad in second residual vq as mentioned here (https://github.com/lucidrains/vector-quantize-pytorch/issues/33)
https://github.com/facebookresearch/encodec/blob/194329839fd812433992272fc5e7a889176e6fd1/encodec/quantization/core_vq.py#L336
The fix link is https://github.com/lucidrains/vector-quantize-pytorch/commit/ecf2f7c7c7701029488500b6b3d46b7c895063bf

@adefossez

Thanks for bringing that out!
It seem like this won't impact the Straight-Through-Estimator gradient for the Encoder, but will kill the commitment loss for all residual VQ but the first one right ?

It seems so. But I'm not sure how much it affects the final result.

I'm a bit reluctant on introducing a change we haven't tested in this codebase, as it could change the best hyper params etc. I can add a warning however if the model is used in training mode pointing to this issue.

why did you put 0 *  q1.sum() ? that is what is breaking the STE gradient. With the current code d q1 / d x = Id and d q_i d / x = 0 for all i > 1, which is okay as the overall gradient d (sum q_i) / d x = Id which is what we want. The only thing that is impacted in the commitment loss.

@adefossez @cantabile-kwok
If  residual = residual - quantized ,  then the second codebook can update with gradient but it can not afffect the first codebook.
If residual = residual - quantized.detach(), then the second codebook's gradient will affect the fisrt codebook.
In core_vq.py, there is the following code in VectorQuantization Class :

Now there is the following code in the ResidualVectorQuantization Class

So, this problem equals to the following problem. The following code snippet may illustrate this:
import torch
def quantize(x, codebook):
diff = codebook - x  # (n_code, dim)
mse = (diff**2).sum(1)
idx = torch.argmin(mse)
return codebook[idx]
dim = 5
x = torch.randn(1, dim, requires_grad=True)
codebook1 = torch.randn(10, dim)
codebook2 = torch.randn(10, dim)
q1 = quantize(x, codebook1)  # quantize x with first codebook
q1 = x + (q1 - x).detach()  # transplant q1's gradient to x
residual = x - q1.detach()  # detach q1 or not may make a difference. Compute residual for next level quantizing
q2 = quantize(residual, codebook2)  # quantize residual with second codebook
q2 = residual + (q2 - residual).detach()  # transplant q2's gradient to residual
loss = 1*q2.sum()  # loss is a function of q1 and q2, now it is independent of q1.
loss.backward()
print(x.grad)
if residual = x-q1, x.grad = 0,
if residul = x-q1.detach(), x.grad = tensor([[1., 1., 1., 1., 1.]])

@adefossez May I ask if you used the EMA method to update the codebook in the rvq algorithm?


setDefaults is not defined when passing options

Attempting to pass options when adding the plugin to the global Vue instance produces the following exceptions:
Uncaught ReferenceError: setDefaults is not defined
    at Object.install (vue-clampy.js?6bc5:374)
    at Function.Vue.use (vue.esm.js?efeb:4751)
    at eval (main.js?3479:46)
    at Object../src/main.js (app.js:10469)
    at __webpack_require__ (app.js:679)
    at fn (app.js:89)
    at Object.1 (app.js:10750)
    at __webpack_require__ (app.js:679)
    at app.js:725
    at app.js:728

Code:
import clampy from '@clampy-js/vue-clampy'

Vue.use(clampy, {
  truncationChar: ' '
})

Looking at the code, there is indeed setDefaults method call but I do not see a setDefaults method defined anywhere.

@hvaughan3 , can you try with 1.0.2?

@hvaughan3, this is now fixed in 1.0.4. Feel free to reopen the issue if necessary.

Very sorry for the delay. Just tried it out and its working great. Thanks!