Add logger implementation to test scope

Basic information

nrich version:
1.1.1
Module:
Project

Additional information

Enhancement description
Currently in tests there is only a warning logged about missing logger implementation, it would be better to add a logger implementation at least in the test scope.
Current behaviour
No logs in tests.
Wanted behaviour
Logs in tests visible.
Possible workarounds

Fixed in https://github.com/croz-ltd/nrich/pull/22


Feature Request: Feedback/response about deployment

Hello,
I have a new feature request, but I'm not so sure if it is possible at all. Yesterday I have ran into a slight error. I was setting up my own server and I screwed up the permissions, etc. Long story short, plugin said deployment was successful, but in reality, my files never got uploaded in the folder because my FTP user didn't have write permission.
I would love to get an error with a message explaining the issue, so I could figure out what is the problem quicker. It is a minor issue, but still, I think it would be nice.
However, I'm not sure it is possible through Javascript but I thought asking doesn't hurt.
Thanks and looking forward to your answer!

@realee94
For FTP uploads I use the ftp module, which returns error objects in the callbacks when an error occurrs.
It looks like the server does not report errors (in that case).
What server software do you use and does this also happens when you use another FTP client?

@mkloubert
I have a basic cloud setup with Ubuntu 16.10 and Apache web-server, Proftpd FTP server and the usual stuff (Mysql, php, etc). I didn't try it with anything else, because I quickly realized what is the issue. Once I have time I will check out other FTP clients too.
Any suggestion which ones to try with and see what error they throw?

WinSCP or ftp on Linux / Mac.

@realee94
I think I found the bug.
While I am implementing the download feature, I found out that the extension is the one that reports wrong results.
I think today or tomorrow you will get the bug fix including the new download / pull feature :-)

@mkloubert
Sorry for not responding but I didn't have time to check it out.
You're doing god's work man! I can't wait for the update. ;) Keep it up!
👍

@realee94
Should be fixed since version 6.0.0.


Consider including also some "low level" options for GoodData Writer

Marcus wrote in ticket:

I think it's important to link the github into the component description no matter what. these are pretty key things to know and that needs to be replaced in the orchestrator for many clients. so these parameters are things that everyone needs.

He speaks about:

loadOnly - skip model update, just load data

multiLoad - flag if the tables should be integrated one by one or all at once (may be good for some situations, see https://help.gooddata.com/display/developer/Multiload+of+CSV+Data)

^ mentioned options are available only in component's repo https://github.com/keboola/gooddata-writer-v3

Zalozil som to sem, lebo si mysli, ze ked uz, tak to ma byt v dokumentacii. Imho nechceme na stranke komponenty otravovat usera s takymito vecami.

https://keboola.zendesk.com/agent/tickets/10150

https://keboola.atlassian.net/jira/software/projects/DOC/boards/15?selectedIssue=DOC-13


Add AttributeTable module

This PR adds a attribute table to Wegue.

it can be activated in the configuration file like other modules
it provides a drop-down-menu with all vector layers and displays them accordingly in the table
works for both desktop and mobile (see GIFs below)
a click on the column name sorts the table
the human-readable names of the columns can be defined using the layer-property columnMapping
the documentation has been updated

Desktop

Mobile

@chrismayer thanks for the  review. I addressed your comments.
Additionally I added basic tests for AttributeTable, AttributeTableWin, ToggleButton (Attribute Table).
And I added a label to the drop-down menu. See gif below

@chrismayer I addressed your comments

@chrismayer I noticed that I did not copy the files from app to appStarter. I fixed it with
0170b8c. I also updated the branch to the latest master

Thank you very much for this @JakobMiksch , LGTM now! 'Ill merge...


Disable blob deduping temporarily

We can enable slowly in future. Allowing host to set policy so that it can be turned on without making changes at driver layer.
Currently we are facing Data corruption issue where directory blob is wrongly showing as map blob. We already disabled handle expansion but for now to be safe we are disabling entire blob deduping. Currently we are not facing the issue after disabling handle expansion but we can monitor telemetry before making any further conclusions.

My only concern here is around whether we will ever turn this back on. If there isn't a plan to turn it back on i'd rather just remove the code, and unused code will just accur dept


File data type and extensions

How about info on the File data type and extensions?

Documentdetails
⚠ Dit gedeelte niet bewerken. Het is vereist om problemen te koppelen tussen docs.microsoft.com en GitHub.

ID: 3297fe6c-82c8-2ea5-da1b-9fe98107fcda
Version Independent ID: 0296caa3-0ea4-6e09-3046-a629473940ac
Content: File Data Type - Business Central
Content Source: dev-itpro/developer/methods-auto/file/file-data-type.md
Service: dynamics365-business-central
GitHub Login: @solsen
Microsoft Alias: solsen

Hi, the methods in this article are automatically generated from AL and should reflect what available in AL. If you find that this is not the case, please file a product bug. Thanks for the feedback!

Ouch, do you really mean that? So you think the current info makes sense? This is not inline with many other MS platform and library kind of information, and now your are reverting the issue to me. This is really disappointing. I take quite some time in reporting things. Feels I am not taken seriously.

Hi Luc, first of all we want you to know that your input and ideas for improvement are highly valued. We have reopened this issue to see if we can somehow address this. We think this type of reference topic is on par with other reference you can find; knowing that it does lack good sample code. We will keep this issue open and find some time to improve the description of the File data type with some examples.  Thanks.

Appreciated.


Fix #276

See https://github.com/Yggdroot/indentLine/issues/276#issuecomment-541486799 for rationale

@richin13 This fixed the issue, may I know why was it closed?

The logic currently being used is a bit complex & hard to follow. The change I did introduced many new bugs :sweat_smile:


[WIP] new arch on android

Thanks for working on this!
Just FYI, Android will need a custom C++ Shadow node in order to layout the bottom navigation bar properly.
Here is a reference of this in another library: https://github.com/callstack/react-native-slider/pull/589
We can also split the work (base implementation and Cxx shadow node separately)

Hi @okwasniewski
I have added the custom C++ shadow node but I am still facing some issues.
The bottom tab bar is not displayed on the screen but the screens are visible.
Here is a screenshot

I have tried layout inspector on this and these are the results

If you look at these screenshots we can see that there is some BottomNavigationView is shown in Layout Inspector. But it is not displayed on the screen. Please let me know your thoughts about this

Hey, I merged #64, I am looking into this!

Hey,
Huge thanks for working on this! I've started off your work and fixed all the issues here: #79

Hi @okwasniewski, I appreciate your review of this PR; could we discuss the mistake I made regarding the Shadow Node (Was it Event Dispatcher or anything else), as I'm unsure about it, and could you also recommend any resources for further reading(Specially for Custom Shadow Node and CPP code of RN)?

Hi @okwasniewski, I appreciate your review of this PR; could we discuss the mistake I made regarding the Shadow Node (Was it Event Dispatcher or anything else), as I'm unsure about it, and could you also recommend any resources for further reading(Specially for Custom Shadow Node and CPP code of RN)?

Sure! Sorry for not providing you any feedback.
I've spent a lot of time figuring out whats was wrong you were mostly on point but the main issue was the method signature of the measure call on the ViewManager level as it wasn't called at all. I also made it work for iOS because when you opt-out of codegen passing interfaceOnly it's not generated for iOS either.
Regarding the dispatcher I removed it and attached it separately for both architectures as I think this makes things simpler, otherwise it was great work!
Regarding resources, I don't think there are any... I was mostly going through RN source code and checking how it's done for built-in components
There aren't many resources

I've merged #79 once again thanks for your help!

Thanks for your feed back this is really helpful.


Problems with infinite page dimensions

Using #set page(width: auto) (or height: auto) leads layout to report infinite dimensions (in the v0.0.5 patch). This should be accounted for in code (currently it crashes Typst).

Should hopefully be fine now

Complemented with https://github.com/PgBiel/typst-tablex/commit/bb49c658cdbc174a1c4fc18c45e7777f70ef946e

See also https://github.com/typst/typst/issues/1918


async/await support?

it would be interesting support async / await to be possible to test methods like this
Smock.Run(async context =>
{
    await target.Run();
}

Hi, thanks for the suggestion. This should be fairly straightforward to add, so I will definitely consider this for a future version.


Remoteapp: Flickering and dialog boxes not showing up most of the time when minimize and click from taskbar

I saw that in the new releases (>3.2) there were improvements to the behavior of popups/dialogs. These changes are affecting me when I minimize all dialog windows and reopen them from the taskbar. Most of the time there is a flickering, I imagine it is an attempt to show itself but it fails and I have to click more than once to get it to open
Video:
https://github.com/user-attachments/assets/351c9e2d-e747-49c4-8902-05a94d462f31
For example:
/u:test /app:program:"||iexplorer",cmd:'"https://example.com/"' /title:"Test" /d:test.test /smartcard /p:"test" /v:localhost:3389 /size:100% /cert:ignore
Any setting that could improve this behavior?
Application details
This is FreeRDP version 3.10.2
/u:test /app:program:"||iexplore",cmd:'"https://example.com/"' /title:"Test" /d:test.test /smartcard /p:"test" /v:localhost:3389 /size:100% /cert:ignore
OS version connecting to (server side)
Windows Server 2016
OS: Fedora
Version/Distribution: 37 with lxqt desktop environment
Architecture: amd64

@akallabeth any idea? :)


Why does the vehicle speed seem to be unchanged after training.

Hi, I was following the tutorial of E2E deep learning for autonomous driving. Now the vehicle is able to successfully run by itself after training. However, the speed of the vehicle seemed to be unchanged, which was always around 5. Does the model really take the vehicle speed as a feature during training? Did anyone meet this problem? Thanks!

Hi @BrianN92 , thanks for trying out the tutorial. The car speed is indeed part of the previous_state tuple which contains: (steering, throttle, brake, speed) values as the last known state of the system. This tuple is fed into the training network as a feature vector along with image features extracted from convolutional layers. The prediction from the model however, is only for the steering angle. You can confirm this by making note of the single neuron in the output layer of the network:
merged = Dense(1, name='output')(merged)
The model is predicting the steering angle based on visual input through the camera as well as awareness of its last known state comprising of the steering, throttle, brake and speed values. When you run the trained model there is a PID controller that helps maintain constant speed as your model takes control of the steering wheel.
You are most definitely encouraged to play around with the tutorial to predict more than one output (you will have to make some minor edits to the Cooking.py file, around that line 95 for loop). Another thing to note if you do decide to predict more than just the steering angle, you should not be predicting speed, but rather the throttle. It's just like driving in real life where you don't control the speed of your car directly, you control how hard you press the gas pedal instead.

Thanks for your advice, @adshar !


Improvements in the Rate Limiting documentation

Summary
We have identified a few improvements in Rate Limiting documentation.
Update the misconfigured links in the  Rate Limited Entities section
Update the text formatting in OAuth Server, Account App, Gateway Configuration Server, Interop Server, Metrics, Health, pprof section
Why do we need this?
...
What is already there? What do you see now?
Rate Limiting documentation
What is missing? What do you want to see?

Clicking on the text content of a section is redirecting to the next section. Please check and fix this.

Example:
Hover and click the space between the Key and Example attributes of the Application Server MQTT Client Connections subsection.
https://user-images.githubusercontent.com/9304207/158823419-341a6498-8d2a-4ed5-ab6a-0dac5963aea9.mp4
On clicking, it is redirecting to the next subsection, Application Server MQTT Downlink Traffic.
Please ignore if this is as intended.

Update the text formatting in the Description of OAuth Server, Account App, Gateway Configuration Server, Interop Server, Metrics, Health, pprof subsection
We see that the text formatting is displayed as below. Fix it if possible.

`{{ Server }}` is `oauth`, `account`, `gcs`, `interop`, `metrics`, `health`, `pprof`

How do you propose to document this?
...
Can you do this yourself and submit a Pull Request?
No

These are all rendering issues so I'm assigning this to @benolayinka

This content is out of date and those fixes are applied now.


Make url clickable inside terminal

Is it possible to make all url clickable inside the terminal to open a browser ?
In the sample bellow, I click on "Ctrl" above the link to activate the navigation.
Here you are a link to a video : https://youtu.be/-QsOepOU6j0

This actually landed in the Insiders build 2 days ago :+1:
Duplicate of https://github.com/Microsoft/vscode/issues/7321


Fixes popover.js dynamically set title not displaying when previously hidden

Tests passed. Automated cross-browser testing via Sauce Labs and Travis CI shows that the JavaScript changes in this pull request are: CONFIRMED
Commit: 86de231ec0a2cbc470aad7e14de3d632b2728b01
Build details: https://travis-ci.org/twbs-savage/bootstrap/builds/146388936
Docs preview: http://preview.twbsapps.com/c/${commitSha.sha}
(Please note that this is a fully automated comment.)

This PR has incorrect indentation.

Bootstrap 3 is no longer being officially developed or supported.
All work has moved onto our next major release, v4. As such, this issue or pull request is being closed as a "won't fix." For additional help and support, we recommend utilizing our community resources. Thanks for your understanding, and see you on the other side of v4!
<3,
@mdo and team


fix clippy warnings

What did you implement:
Fix clippy warnings

Thanks! I will fix other issues in upcoming PR, was a while since I've looked at new lints.


API Manager 3.0.0 - Error occurred when trying to import API definition for already created REST APIs.

Steps to reproduce:

Create an API with the option "I Have an Existing REST API".
Choose the OpenAPI file option and upload the swagger definition.
Give the necessary information and create the API.
Then go to the API definition and click on "Import Definition"
Upload the same swagger definition which is used to create this API.
Observed below error.

I tried to reproduce this issue but couldn't reproduce with example in here
Can you please provide the OpenAPI definition that you have used when this issue occurred.
And also please provide the browser console logs as well


feat(otlp-exporter-base): add retries

Which problem is this PR solving?
Adding retries to otlp http & proto exporters.
Note: this pr does not add retries to the grpc otlp exporter.
Fixes #1233
Short description of the changes
Added retry logic to sendWithHttp and sendWithXhr functions. It does the following:
If the exporter gets a failed response that is retryable, we check if the response included a "retry-after" header.

If yes, retry again in the time specified in the retry-header which can be seconds or a date/time.
If no, we use an exponential backoff with jitter

This logic is retried until there is a successful response or until the exporter timer times out (set via timeoutMillis in the exporter config or via env vars). If the exporter timers times outs, the request is aborted with a "Request Timeout" error.
Type of change
Please delete options that are not relevant.

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

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] Unit Tests - for browser only

Checklist:

[x] Followed the style guidelines of this project
[x] Unit tests have been added
[x] Documentation has been updated

For some reason, using req.destroy() in a real http request export here is not triggering any of the following events:

'aborted' on the res object
'error' on the res object with an error with message 'Error: aborted' and code 'ECONNRESET'.
'error' with an error with message 'Error: socket hang up' and code 'ECONNRESET'

These events should fire depending on when the request is aborted (before socket assigned, before connection succeeds or after response is received).
If I use req.abort() then it works (fires the correct events) but req.abort() was deprecated in node 14 so I was trying to avoid using it in node 14 and higher.
Any idea what I'm missing here or what's going on?

For some reason, using req.destroy() in a real http request export here is not triggering any of the following events:

'aborted' on the res object
'error' on the res object with an error with message 'Error: aborted' and code 'ECONNRESET'.
'error' with an error with message 'Error: socket hang up' and code 'ECONNRESET'

These events should fire depending on when the request is aborted (before socket assigned, before connection succeeds or after response is received).
If I use req.abort() then it works (fires the correct events) but req.abort() was deprecated in node 14 so I was trying to avoid using it in node 14 and higher.
Any idea what I'm missing here or what's going on?
If you run this test and use req.destroy() here instead of `req.abort() and use node 16, you'll see what I'm referring to.

Those events only fire if you call req.destroy after the response is received https://nodejs.org/api/http.html#httprequesturl-options-callback.

I would love some feedback on the current implementation of the retry logic.
I still need to confirm and add the following items:

"jitter" to the retry logic
confirm the retryable codes (I think there is an issue open about this in the spec)

I've added the following:

jitter to exponential backoff
added logic to check for "retry-header" to use in retry logic
fix some tests and removed a flaky real http request test (node)

I'm unable to add real node tests to test this retry logic because the tests are very flaky when I use a real node http request. I tried to use "nock" but I found out that it overrides the client http request so I can't test the retry logic.

I'm unable to add real node tests to test this retry logic because the tests are very flaky when I use a real node http request. I tried to use "nock" but I found out that it overrides the client http request so I can't test the retry logic.

I am wondering if you could use msw for this?

I'm wondering if it would be possible to unify the retry handling around the sendWithXhr and sendWithHttp -- it only depends on the 'Retry-After' header and the response status code.

Sure I can give that a shot after thanksgiving break.

@legendecas Regarding your comment:

I'm wondering if it would be possible to unify the retry handling around the sendWithXhr and sendWithHttp -- it only depends on the 'Retry-After' header and the response status code.
It may be simpler if the platform-dependent part can be minimized.

Sorry for the delay on this.
I don't think I can unify the retry handling between sendWithXhr and sendWithHttp. There's quite a few difference between the two (ex. how the retry-after header is retrieve, how the OTLPExporterError is created, how the request status codes are retrieved....etc). Did you happen to see a way this can be done and point me in the right direction?

ex. how the retry-after header is retrieve, how the OTLPExporterError is created, how the request status codes are retrieved....etc.

I think we should create a dedicated http client abstraction on both Node.js and browser, either by using widely adopted npm package (like superagent or axios)  or creating our own one (since we may need to tweak it to be able to use sendBeacon too). Anyway, I believe this can be done in a follow up PR.

I've updated the parseRetryAfterToMillis function based on @legendecas feedback. This PR is ready for review.

I'm going to merge this as @opentelemetry/instrumentation-http:test failure on node-windows-tests is being tracked at https://github.com/open-telemetry/opentelemetry-js/issues/3628.


Information Clears When Switching Between Tabs

Information entered on the 'Describe Exports', 'Choose Formats', 'Select Features' and 'Summary' tabs disappears when switching between them (on staging).

Fixed in a1f8bc2a4a7aa0a2c7b4f5a4294104fac0d4bf09


Using smooth scroll prevents use of :target css selector

I suspect this is an issue that is a browser implementation issue, but I thought I would mention it incase it's not.
The desired behavior can be seen here:
https://css-tricks.com/on-target/
there is a bug in the article that may be on point for this project.
https://bugs.webkit.org/show_bug.cgi?id=83490
To recreate, add
:target { background-color:yellow; }   to a page using smooth-scroll and then click on a smooth scroll link.  the target won't light up.  If you reload the page it does.
Thanks for the project.  Find it quite useful.

Known issue, no workaround, as there's no way to programatically set the scrolled to element with the :target pseudo.
Accordingly, closing as won't fix.

Should have mentioned: thanks for the issue, and the links!

It works in IE11


Add support for Nodes exclusion

This pull request adds support for excluding nodes in the processing. Users can now specify a list of nodes to exclude during the handleClickOutside event listener, which can be useful for filtering out unwanted nodes as event target.
Here is an example :
const ref1 = React.useRef<HTMLDivElement | null>(null);
const ref2 = React.useRef<HTMLDivElement | null>(null);
const result = useClickOutsideListener<HTMLDivElement>({...options, exclude : [ref1, ref2]});

return (

        {/* render other elements */}

)

click event (or supported options events) on  both ref1, ref2 elements will have not effect !

It's done !


HDDS-3124. Fix time interval calculate error

What changes were proposed in this pull request?
Just as the image shows, the time interval in log "Unable to communicate to SCM server at scm-0.scm:9861 for past " is 0, 3000 seconds, but actually it is 0, 300 seconds.

What is the link to the Apache JIRA
https://issues.apache.org/jira/projects/HDDS/issues/HDDS-3124
How was this patch tested?
No need to test.

@ChenSammi Could you help review this patch ? Thank you very much.


Remove: chrisant996.Clink version 1.2.37.de5dfb

## .\Tools\YamlCreate.ps1 -SkipPRCheck -Mode 5 -PackageIdentifier chrisant996.Clink -PackageVersion 1.2.37.de5dfb

[X] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?

[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.0 schema?

Microsoft Reviewers: Open in CodeFlow

/azp run


Installation instructions

Could you please outline how to install / use this linter?

Oh huh. linter.aip.dev seems to be down. :-(
Release is here: https://github.com/googleapis/api-linter/releases

Looks like it got swept in the master -> main branch change. Should be back up soon.


Looser peerDependencies for CDK modules

While I don't believe this is totally accurate, as such, I suspect that there are CDK versions below 1.64 where this module will work fine, but it looks like npm is now stricter when peer dependencies are not satisfied.
Attempting to install this module where I'm using an older version of CDK, I get an error like:
$ npm i --save cdk-datadog-integration
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@aws-cdk/aws-cloudwatch
npm ERR!   peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/@aws-cdk/aws-lambda
npm ERR!     peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/@aws-cdk/aws-cloudformation
npm ERR!       peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!       node_modules/cdk-datadog-integration
npm ERR!         cdk-datadog-integration@"*" from the root project
npm ERR!   peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/@aws-cdk/aws-applicationautoscaling
npm ERR!     peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/@aws-cdk/aws-lambda
npm ERR!       peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!       node_modules/@aws-cdk/aws-cloudformation
npm ERR!         peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!         node_modules/cdk-datadog-integration
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@aws-cdk/aws-ec2
npm ERR<EMAIL_ADDRESS>from the root project

That is, npm is - not unreasonably - complaining because my package.json has "@aws-cdk/aws-ec2": "1.55.0" but this module has "@aws-cdk/aws-cloudformation": "^1.64.1", and each of those wants a compatible @aws-cdk/aws-cloudwatch, which are incompatible. It looks like this is different behaviour between npm 6 and 7, where 6 was more lenient, but 7 errors.
One option would be for me to upgrade CDK. In my case that is not possible.
Another would be to update this modules package.json to have the loosest functioning peer dependencies, but alas, I'm just not that diligent.
Thus, I have arrived at the changes that I have here.

Hey @plumdog - thanks for this PR. I'm sure there's some version earlier than 1.64.1 that breaks this library but I'm OK with loosening this requirement as long as there's a note about compatibility.
Would you be willing to do two things with this PR?

Add a comment in README.md that this library is tested with 1.xx (1.55.0 if you've tested against it, 1.64.1 if not). A disclaimer should be included that "your mileage may vary" with versions earlier than the tested version.
Add <2 to the peer dependencies while we're updating it. v2 is a breaking change and I'm assuming I'll need to do some updates to be compatible when it's released.

Thanks for your contribution!

It does indeed work fine with 1.55.0, based on my testing - which is to say: it successfully creates the stacks I expect, and metrics and logs are arriving in Datadog, so I consider that "passed testing". I've added a note to the README to say as much.
I believe that the version constraints already in package.json do exclude a new major version. NPM's docs have the example:

^1.2.3 := >=1.2.3 <2.0.0

so I think the version constraint is already set to the right thing. See https://docs.npmjs.com/cli/v7/using-npm/semver#caret-ranges-123-025-004 for excessive detail.

Sadly, it appears that the build is broken now, so the release did not succeed. I don't have time to take a look at it for a few days, so I opened https://github.com/blimmer/cdk-datadog-integration/issues/29


Checksum of /versions does not match the checksum provided by server

When using bundler-1.12.0.rc.4, I get this error when doing a bundle install:
$ bundle install
Fetching gem metadata from https://gem.fury.io/ecraft-gems/.....
Fetching version metadata from https://gem.fury.io/ecraft-gems/...
Fetching dependency metadata from https://gem.fury.io/ecraft-gems/..
Checksum of /versions does not match the checksum provided by server! Something
is wrong.

As can be seen, I am using a 3rd party gem source. (Gemfury)
When using the released bundler 1.11.2, it works properly:
$ bundle install
Warning: the running version of Bundler is older than the version that created t
he lockfile. We suggest you upgrade to the latest version of Bundler by running
`gem install bundler --pre`.
Fetching gem metadata from https://gem.fury.io/ecraft-gems/.....
Fetching version metadata from https://gem.fury.io/ecraft-gems/...
Fetching dependency metadata from https://gem.fury.io/ecraft-gems/..
Fetching gem metadata from https://gem.fury.io/ecraft-gems/.....
Fetching gem metadata from https://rubygems.org/...........
Fetching version metadata from https://gem.fury.io/ecraft-gems/...
Fetching version metadata from https://rubygems.org/...
Fetching dependency metadata from https://gem.fury.io/ecraft-gems/..
Fetching dependency metadata from https://rubygems.org/..
Resolving dependencies....
Installing rake 11.1.1
[...]

Any ideas what could be causing this? /cc @rallenecraft

@perlun a bug in either the server or client for the new index. Thanks for reporting this!

@perlun can you provide some more information, so that we can try to reproduce this issue? The output from bundle install --verbose would be very helpful. When I try to install gems from my own GemFury account, everything works fine.

It would also be very helpful to see

It would also be very helpful to see what, exactly, is being returned for you when you use your GemFury credentials to access the url https://gem.fury.io/ecraft-gems/versions. For my account, that is a 404. It seems that it must not be a 404 for your account, and I don't understand how that's happening...

I just started getting this same error on appveyor builds (see https://ci.appveyor.com/project/winrb/winrm/build/master-166). I then tried it on a local windows machine (blowing away my Gemfile.lock first) and got the same error.
Testing with Gem: https://github.com/WinRb/WinRM
version: 1.12.0
Works fine with 1.11.2.

forgot to add --verbose output:
C:\dev\WinRM [pin_bundler]> bundle install --verbose
HTTP GET https://index.rubygems.org/versions
HTTP 200 OK
HTTP GET https://index.rubygems.org/versions
HTTP 200 OK
Checksum of /versions does not match the checksum provided by server! Something
is wrong.

Any chance you are on windows @perlun?
This looks to be a classic case of carriage return injection on windows platforms. I just submitted #4479  to fix that.

Yes. This was on Windows.

I get this on Windows:
$ bundle install --verbose
HTTP GET http://gems.on-private.server/versions
HTTP 404 Not Found Bundler::Fetcher::FallbackError: Net::HTTPNotFound
C:/Ruby/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/fetcher/downloader.rb:34:in `fetch'
  C:/Ruby/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/fetcher/compact_index.rb:76:in `block in compact_index_client'
  C:/Ruby/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/vendor/compact_index_client/lib/compact_index_client/updater.rb:23:in `call'
  C:/Ruby/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/vendor/compact_index_client/lib/compact_index_client/updater.rb:23:in `update'
  C:/Ruby/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/vendor/compact_index_client/lib/compact_index_client.rb:63:in `update'
  C:/Ruby/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/vendor/compact_index_client/lib/compact_index_client.rb:54:in `update_and_parse_checksums!'
  C:/Ruby/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/fetcher/compact_index.rb:63:in `available?'
  C:/Ruby/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/fetcher/compact_index.rb:15:in `call'
  C:/Ruby/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/fetcher/compact_index.rb:15:in `block in compact_index_request'
  C:/Ruby/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/fetcher.rb:154:in `use_api'
  C:/Ruby/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/source/rubygems.rb:331:in `block in api_fetchers'
  C:/Ruby/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/source/rubygems.rb:331:in `select'
  C:/Ruby/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/source/rubygems.rb:331:in `api_fetchers'
  C:/Ruby/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/source/rubygems.rb:336:in `block in remote_specs'
  C:/Ruby/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/index.rb:10:in `build'
  C:/Ruby/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/source/rubygems.rb:335:in `remote_specs'
  C:/Ruby/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/source/rubygems.rb:82:in `specs'
  C:/Ruby/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/lazy_specification.rb:56:in `__materialize__'
  C:/Ruby/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/spec_set.rb:91:in `block in materialize'
  C:/Ruby/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/spec_set.rb:88:in `map!'
  C:/Ruby/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/spec_set.rb:88:in `materialize'
  C:/Ruby/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/definition.rb:140:in `specs'
  C:/Ruby/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/definition.rb:129:in `resolve_remotely!'
  C:/Ruby/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/installer.rb:195:in `resolve_if_need'
  C:/Ruby/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/installer.rb:70:in `run'
  C:/Ruby/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/installer.rb:22:in `install'
  C:/Ruby/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/cli/install.rb:102:in `run'
  C:/Ruby/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/cli.rb:175:in `install'
  C:/Ruby/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
  C:/Ruby/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in `invoke_command'
  C:/Ruby/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/vendor/thor/lib/thor.rb:359:in `dispatch'
  C:/Ruby/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/vendor/thor/lib/thor/base.rb:440:in `start'
  C:/Ruby/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/cli.rb:11:in `start'
  C:/Ruby/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/exe/bundle:27:in `block in <top (required)>'
  C:/Ruby/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/friendly_errors.rb:98:in `with_friendly_errors'
  C:/Ruby/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/exe/bundle:19:in `<top (required)>'
  C:/Ruby/bin/bundle:23:in `load'
  C:/Ruby/bin/bundle:23:in `<main>'
HTTP GET http://gems.heco.de/api/v1/dependencies
HTTP 200 OK HTTP GET https://index.rubygems.org/versions
HTTP 200 OK
HTTP GET https://index.rubygems.org/versions
HTTP 200 OK
Checksum of /versions does not match the checksum provided by server! Something
is wrong.

This should now be fixed in 1.12.1!

I am getting this error after upgrading to Rails 5.0 today. I am using 1.12.5. Any thoughts?

Getting this on install of bundler 1.12.5 e.g. https://travis-ci.org/Dynamoid/Dynamoid/jobs/150380064

@pboling homu is a bot, and probably can't help you. I believe that we fixed this issue (to instead print a warning and then automatically use the full index), but we haven't released it yet. For the time being, you can work around this problem by running bundle install --full-index.

I'm having the same issue in 1.13.2, fixed with bundle install --full-index

Yes, I am also currently getting this - wasn't there last friday - and running bundle install --full-index fixes it.

Same here

facing same issue

The issue has been fixed client-side on bundler master, and @dwradcliffe has rolled back the changes on rubygems.org that caused this issue to crop up


Obfuscation of information that gets saved in the logs.

Please Select if your Request is Either something new or an Enhancement

[ ] Enhancement of an existing Feature.
[x] Request of a new feature.

Please select the area your request applys to. (Multiple selections are Possible)

[ ] Onboard. Initial vault setup and import/export pods
[ ] Create. Note creation, lookup, snippets and templates
[ ] Retrieve. Backlinks, references, graph view
[ ] Structure. Refactoring, multi-vault and schemas
[ ] Publish. Sharing your repo with the world
[x] Misc (Choose this if your not sure)

Is your feature request related to a problem? Please describe
Today users on the discord mentioned some privacy concerns,  about the information that is contained in the logs.
Describe the solution you'd like

That the logs that get written have the hostname entry removed or obfuscated.

I don't see why this information is needed for debugging purposes.

That the Filenames get Obfuscated.

by replacing each filename segment with a * that way there is still some value in them but we are not saving maybe sensitive information at locations that may or may not be outside of the scope of Control from the user.

Additionally it should be further noted, that we only save data we truly need in these logs.

and should possibly Investigate which information we truly need.

Additional context
Beginning of the Discord discussion.
https://discord.com/channels/717965437182410783/717965437182410786/836625205291646986

I'd like to see obfuscation of the username too. It's typically part of the file path. I routinely replace it before sending logs

Also the vault path and the log path

Some of us who use git in certain corporate contexts have to use PAT's with (for example) github. I'd appreciate it if the log export could obfuscate the token, or even the full git url.
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>for instance.


issue not loading in chrome

i try'd using a number of different versions and none of them worked on chrome but they did work on firefox currently im using frozen cookies and it works on chrome

i just opan'd a new tap and the same thing happened, does cookie master stay installed after getting a new tap?

Well I would need to see the error when Cookie Master was never loaded.  All I know is that the error you screenshot shows Cookie Master is conflicting.

Cookie Master is still there (says ...okiemaster.min).  I think it's a Chrome extension.  You should remove that extension.

works great now, thanks :)

Great!  Glad it works!  Closing this.


in myDIG have the ability to

run etk on specific tld(s)
delete tlds
a. delete from es
b. delete data from mydig
delete all the data from a project
delete a project

This is done


用不起呀

发两次就卡住吗，而且都没有成功，是怎么回事呢？

MicroPython v1.18

Hello. Could you please share your code? It’s hard to know what’s going on without it..

@zkbutt I'm closing this issue since there was no feedback. Please feel free to re-open it and add more details.


Python 3 compatibility

content.sort(key=lambda (k, v): k) is invalid in Python 3, it should be content.sort(key=lambda k: k[0]) which is compatible for both Python 2 and 3.

Any news?


Support Vue >= 2.5

Current version does not works with Vue 2.5.
This PR fixes problems when using with Vue 2.5.

Still not work with TypeScript 2.6 :(

I've updated ts version in https://github.com/ktsn/sinai/commit/0e3154192d4a1ab03aa57a03533244e46ffac033 :)


Submitting  StarfaceUCC version <IP_ADDRESS>.yaml

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

Microsoft Reviewers: Open in CodeFlow

New to Github.


Main page API

stuff such as /public etc

Mostly done, needs to get the user from authentication, once implemented, and manual testing

Finished


Vault unit is in error state when vault service is sealed

Describe the bug
Deploy vault and another charm and relate them. Vault unit went into error state.
Expected vault to be in Blocked state.
To Reproduce
Steps to reproduce the behavior:

Deploy vault charm and any charm that requires tls_interface_certificate library
Relate both the charms
Verify juju status. vault unit is in error state

Expected behavior
Vault unit should be in Blocked state.
Logs
unit-vault-0: 09:14:45 ERROR unit.vault/0.juju-log certificates:3: Uncaught exception while in charm code:
Traceback (most recent call last):
  File "./src/charm.py", line 242, in <module>
    main(VaultCharm)
  File "/var/lib/juju/agents/unit-vault-0/charm/venv/ops/main.py", line 438, in main
    _emit_charm_event(charm, dispatcher.event_name)
  File "/var/lib/juju/agents/unit-vault-0/charm/venv/ops/main.py", line 150, in _emit_charm_event
    event_to_emit.emit(*args, **kwargs)
  File "/var/lib/juju/agents/unit-vault-0/charm/venv/ops/framework.py", line 355, in emit
    framework._emit(event)  # noqa
  File "/var/lib/juju/agents/unit-vault-0/charm/venv/ops/framework.py", line 856, in _emit
    self._reemit(event_path)
  File "/var/lib/juju/agents/unit-vault-0/charm/venv/ops/framework.py", line 931, in _reemit
    custom_handler(event)
  File "/var/lib/juju/agents/unit-vault-0/charm/lib/charms/tls_certificates_interface/v1/tls_certificates.py", line 969, in _on_relation_changed
    self.on.certificate_creation_request.emit(
  File "/var/lib/juju/agents/unit-vault-0/charm/venv/ops/framework.py", line 355, in emit
    framework._emit(event)  # noqa
  File "/var/lib/juju/agents/unit-vault-0/charm/venv/ops/framework.py", line 856, in _emit
    self._reemit(event_path)
  File "/var/lib/juju/agents/unit-vault-0/charm/venv/ops/framework.py", line 931, in _reemit
    custom_handler(event)
  File "./src/charm.py", line 80, in _on_certificate_creation_request
    certificate = self.vault.issue_certificate(
  File "/var/lib/juju/agents/unit-vault-0/charm/src/vault.py", line 269, in issue_certificate
    return self._issue_certificate(**config)
  File "/var/lib/juju/agents/unit-vault-0/charm/src/vault.py", line 278, in _issue_certificate
    response = self._client.write(
  File "/var/lib/juju/agents/unit-vault-0/charm/venv/hvac/v1/__init__.py", line 264, in write
    return self._adapter.post(f"/v1/{path}", json=kwargs, wrap_ttl=wrap_ttl)
  File "/var/lib/juju/agents/unit-vault-0/charm/venv/hvac/adapters.py", line 125, in post
    return self.request("post", url, **kwargs)
  File "/var/lib/juju/agents/unit-vault-0/charm/venv/hvac/adapters.py", line 356, in request
    response = super().request(*args, **kwargs)
  File "/var/lib/juju/agents/unit-vault-0/charm/venv/hvac/adapters.py", line 322, in request
    utils.raise_for_error(
  File "/var/lib/juju/agents/unit-vault-0/charm/venv/hvac/utils.py", line 58, in raise_for_error
    raise exceptions.VaultDown(message, errors=errors, method=method, url=url)
hvac.exceptions.VaultDown: Vault is sealed, on post http://localhost:8200/v1/charm-pki-local/sign/local

Environment

Vault version: latest/edge
Juju version: 3.0/edge
Cloud Environment juju+microk8s
Kubernetes version 1.25

Additional context
Needs a check if Vault is ready or not here [1] and defer the event if vault is not ready.
Also need to catch hvac.exceptions.VaultDown, hvac.exceptions.Forbidden exceptions in Is_ready function [2]
I tried to implement this but one caveat is the deferred event is not triggered until next hook is triggered ( in this case update-status)
Any ideas to trigger the event sooner?
[1] https://github.com/canonical/vault-k8s-operator/blob/main/src/charm.py#L80
[2] https://github.com/canonical/vault-k8s-operator/blob/main/src/vault.py#L58-L71

This issue is fixed. Now Vault automatically initialises and unseals.


Use a proper test runner and actually assert expected behavior

The current test setup only printed some log messages, without checking the result. So even if a breaking change is introduced the tests wouldn’t fail. That’s why I think it is a good idea to use a proper test runner and do proper assertions.

Any feedback on this PR?

Also, for a future PR we could add a more extended set of test cases to cover different types of reported errors.

I agree. Actually I did this PR because I was planning to make a follow-up PR to solve an issue when using intersections, but I want to make sure I don’t break the existing functionality.


Bump java-operator-plugins to v0.11.1

Description of the change:
Update java-operator-plugins to v0.11.1.
Motivation for the change:
https://github.com/operator-framework/operator-sdk/issues/6645
Fixed #6645

Docs are failing bc k8's site has a cert expired.


[Question] why is fvm no longer recommended for global flutter version control?

saw in the documentation that now FVM is no longer globally supported and I would like to know the main reason? Because, in my opinion, it made the transition between projects much easier, not having to change any internal configuration or even the way to run the commands inside the project

@rodrigorahman you can read more about it here https://github.com/fluttertools/fvm/discussions/469


Unify TICKLESS_IDLE & TICKLESS_KERNEL

Unify TICKLESS_IDLE & TICKLESS_KERNEL code and do the cleanup.
Idea is to get rid of TICKLESS_IDLE and use TICKLESS_KERNEL.

I think we can close this.  The two kconfigs are still separate because multiple tests and the legacy timer drivers are written to assume they are different, but the kernel internals no longer care about the distinction.
At least in theory, it's possible to imagine a system where no arbitrary cycle-counted interrupt is available, but where it's able to sleep without that interrupt for long periods using some other hardware.  We don't have such a driver, but it's not IMHO completely insane, and corresponds to the case where TICKLESS_IDLE is true but TICKLESS_KERNEL is not.

This does not seem to be a bug,  I 'd close this @andyross @nashif

closing.


[WIP]Move the common Redis code to internal

Description
Move Redis client and its metadata to internal.
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: #857
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[x] Code compiles correctly
[ ] Created/updated tests
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

I will refactor it to setting pattern.

@Taction I love that you will use the settings pattern. Thank for doing it! Just be careful that we don't have a regression. That will be the challenge getting it applied to all the existing components.

@pkedy Now it is ready to be reviewed. I try to modify the existing content as little as possible to facilitate code review. I extracted the part of parsing redis client and settings form properties.And I've tested the redis cluser and node mode in my local enviroment.
One thing needs extra attention, I changed the behavior of parsing time.Duration in file internal/config/decode.go. If it is a negative value, keep the original value instead of resolving to milliseconds(because -1 is a useful vaule in some redis duration option) .

/cc @pkedy

@Taction This is great! I'll try to review this tomorrow. Got my 2nd vaccine shot today so if not tomorrow then early next week.
The change to the config package makes sense to me. Thanks again for incorporating it! You are a true hero :)

Redis state store already have maxRetries  and maxRetryBackoff metadata, for backward compatibility I make this change.

@artursouza Let's update go.mod in dapr/dapr as soon as this is merged so we can have it proactively go through e2e testing.

@mukundansundar Have you had the chance to take a look a this?


feature: drag and train functionality.

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
feature: drag and train functionality.
Why was this change needed? (You can also link to an open issue here)
fixes #1167

Currently, this logs the dropped file to the console, gotta add the upload functionality but I'm stuck as the conversation and upload are 2 different components. maybe a new redux slice has to be implemented.

Hi @Srayash
Think we can do it in this way, by importing the Upload component in the conversation.tsx
Certain changes will be required in the Upload component, where the activeTab is by default null we can maybe make a prop of the activeTab's default value lets say "file" for our use case.
But still the issues might arise when passing files as prop from the conversation component, because the states are already set as the component gets mounted, so better conditionally render the component when modalState === 'ACTIVE'

Some tests are failing after I merged main into this branch, will close this for now and raise a new PR.
thank you.


[Responsiveness of navbar icons]

What happened?
Hello @agamjotsingh18,
I am an GSSOC'23 contributor and would like to contribute to fix the following bug/issue
On small screen the hacktober fest icon is not having proper spacing and looks odd..

How can we reproduce this bug?
The Icon and the navbar responsiveness can be improved by using flex-box properly

Using the Margin and flex properties to make the responsiveness better in small screen size..

Desktop Information (Optional)
No response
Urgency (Optional)
None

Sure @sahilduhan , make sure to check for both desktop and mobile view as the issue you raised is very easy

Please assign me this issue so that I can resolve it under GSSOC-23


Compile time dependencies.

You use TMS FNC Cloud Pack, but most developers don't have that pack.
Maybe it's better if you use TRestClient or any other open-source library.

There you, @AliDehbansiahkarbon, are right. In the README.md I have now learned why I am currently using the FNC components and that I will see in the future if I can provide an alternative version without FNC components. Thanks for pointing out TRestClient, I'll have a look at that.


Enable skipping feed validations

If the message sent over SQS contains :skip-validations true,
version-specific validation pipelines will be omitted from the pipeline.
While this might be useful in certain situations, the default is to keep
validations as part of the pipeline.

merged.


AXI4 Scoreboard file

Adding AXI4 Scoreboard file for review

Adding AXI4 interface, AXI4 scoreboard and a basic write sequence for AXI4.

new version to be added


Instance property type is erased, when assigned inside constructor

I was able to reduce my problem to the following snippet (reproduces with Try Flow):
/* @flow */

class CanDoIt {
    doIt(): void {}
}

function xform(obj: CanDoIt): Object {
    return obj;
}

class B {
    _a: CanDoIt
    _b: CanDoIt
    _c: CanDoIt
    _d: number
    _e: CanDoIt
    constructor(a: CanDoIt) {
        super()
        let b: CanDoIt = xform(a)
        this._b = xform(a)
        b.xxx // Error is expected here
        this._b.xxx // Why is no error here?
    }
}

new B(new CanDoIt())._a.xxx // Error is expected here

Somehow, Flow begins to see this._b type as more generic. Because Object allows any property, CanDoIt is compatible with it, i.e. every CanDoIt is an Object. But not every Object is a CanDoIt. Checker seems to think otherwise?
Easy workaround is to cast value returned by xform, like so:
this._b = (xform(a): CanDoIt)

To me this seems like a bad choice, because I have to know xform returns widened type.

I am very new to Flow, so this report might be a user error. Thanks for the great tool nevertheless!

This behavior is expected. A good way to see why is to try changing the let b line to not have an explicit type declaration and notice that the error goes away. In short, explicitly setting the value's type changes how it can be used and this is one of those ways.


LauraTTS: _pickle.UnpicklingError: invalid load key, 'v'.

Environment

PyTorch version: 1.12.0
Python version: 3.8

Issue Description
I believe I have correctly installed the required PyTorch version as per the README instructions and have also executed pip install --editable ./ to install the necessary requirements. However, while trying to run the "Use LauraTTS to synthesize speech" example, executing the following command:
bash demo.sh --stage 1 --model_name ${model_name} --output_dir results --text "nothing was to be done but to put about, and return in disappointment towards the north."
I encountered the following error:
Traceback (most recent call last):
  File "/root/miniconda3/envs/lg/lib/python3.8/runpy.py", line 194, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/root/miniconda3/envs/lg/lib/python3.8/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/root/autodl-tmp/FunCodec/funcodec/bin/text2audio_inference.py", line 561, in <module>
    main()
  File "/root/autodl-tmp/FunCodec/funcodec/bin/text2audio_inference.py", line 557, in main
    inference(**kwargs)
  File "/root/autodl-tmp/FunCodec/funcodec/bin/text2audio_inference.py", line 381, in inference
    inference_pipeline = inference_func(
  File "/root/autodl-tmp/FunCodec/funcodec/bin/text2audio_inference.py", line 287, in inference_func
    my_model = Text2Audio.from_pretrained(
  File "/root/autodl-tmp/FunCodec/funcodec/bin/text2audio_inference.py", line 227, in from_pretrained
    return Text2Audio(**kwargs)
  File "/root/autodl-tmp/FunCodec/funcodec/bin/text2audio_inference.py", line 53, in __init__
    model, model_args = Text2AudioGenTask.build_model_from_file(
  File "/root/autodl-tmp/FunCodec/funcodec/tasks/abs_task.py", line 1941, in build_model_from_file
    src_state = torch.load(model_file, map_location=device)
  File "/root/miniconda3/envs/lg/lib/python3.8/site-packages/torch/serialization.py", line 713, in load
    return _legacy_load(opened_file, map_location, pickle_module, **pickle_load_args)
  File "/root/miniconda3/envs/lg/lib/python3.8/site-packages/torch/serialization.py", line 920, in _legacy_load
    magic_number = pickle_module.load(f, **pickle_load_args)
_pickle.UnpicklingError: invalid load key, 'v'.

Question:
Is there an issue with how I am using the program? I am eager to experience your project and would greatly appreciate your guidance or suggestions for resolving this issue.

Have you follow the README step by step ? You should first set:
model_name="speech_synthesizer-laura-en-libritts-16k-codec_nq2-pytorch"
and then
run the command:
bash demo.sh --stage 1 --model_name ${model_name} --output_dir results --text "nothing was to be done but to put about, and return in disappointment towards the north."
This script will download models from ModelScope or Huggingface into exp/speech_synthesizer-laura-en-libritts-16k-codec_nq2-pytorch and exp/audio_codec-encodec-zh_en-general-16k-nq32ds640-pytorch. Are these directories existed ?

Have you followed the README step by step ? You should first set: model_name="speech_synthesizer-laura-en-libritts-16k-codec_nq2-pytorch" and then run the command: bash demo.sh --stage 1 --model_name ${model_name} --output_dir results --text "nothing was to be done but to put about, and return in disappointment towards the north."
This script will download models from ModelScope or Huggingface into exp/speech_synthesizer-laura-en-libritts-16k-codec_nq2-pytorch and exp/audio_codec-encodec-zh_en-general-16k-nq32ds640-pytorch. Are these directories existed ?

Yeah, I did follow the README.md step by step. I've set the model_name, and like you mentioned, I've got those two files. Also, there's a model.pth file in the folder.I took a screenshot of the contents in the folder. I believe it matches what you described.

Have you followed the README step by step ? You should first set: model_name="speech_synthesizer-laura-en-libritts-16k-codec_nq2-pytorch" and then run the command: bash demo.sh --stage 1 --model_name ${model_name} --output_dir results --text "nothing was to be done but to put about, and return in disappointment towards the north."
This script will download models from ModelScope or Huggingface into exp/speech_synthesizer-laura-en-libritts-16k-codec_nq2-pytorch and exp/audio_codec-encodec-zh_en-general-16k-nq32ds640-pytorch. Are these directories existed ?

Then, I ran the following command: bash demo.sh --stage 2 --model_name ${model_name} --output_dir results --text "nothing was to be done but to put about, and return in disappointment towards the north." --prompt_text "one of these is context" --prompt_audio "demo/8230_279154_000013_000003.wav". It threw the error I initially described. Although the command line indicated that the results were saved in the 'results' folder, I couldn't find this folder in the project. So, I'm guessing something might have gone wrong somewhere.

Sorry for the late response. From your Traceback, I find the error occurred when loading the model. I guess it is probable that your model is not downloaded properly. Have you installed the git lfs? We use git lfs to manage the model checkpoint files. You can check your model size, it should be the same as the ModelScope model page.

Sorry for the late response. From your Traceback, I find the error occurred when loading the model. I guess it is probable that your model is not downloaded properly. Have you installed the git lfs? We use git lfs to manage the model checkpoint files. You can check your model size, it should be the same as the ModelScope model page.

Model speech_synthesizer-laura-en-libritts-16k-codec_nq2-pytorch should have the size of 387.44MB.
Model audio_codec-encodec-zh_en-general-16k-nq32ds640-pytorch should have the size of 265.94MB


about bp node

Apply to be a bp node. What are the officially recommended memory, bandwidth, and network requirements?And the hard drive, thank you

EOSeoul Spec
● Type : Cloud(AWS)
● Location : Seoul AWS region
● Machine : m4.2xlarge instance
● Number : 1
● Memory : 32GB
● CPU : vCPU 8 Core
● Storage : SSD 300GB
● Network
○ uplink capacity : 1G High Shared Network
○ VM interface bandwidth : 1G High Shared Network
● Monthly Bill : USD $457

live service.
● Location : Seoul AWS region
● Machine : m5.12xlarge (up to x1.32xlarge)
● Number : 1
● Memory : 192GB (up to 2TB)
● CPU : vCPU 48 Cores (up to 128 Cores)
● Storage : SSD 2TB * 2EA(NVME) + EBS 16TB (Provisioned IOPS 20000)
● Network : 10 Gbps (up to 25 Gbps)
● Monthly Bill : USD $2,800 (up to $19,361)
● Type : Cloud(AWS)

Thanks to EOSeoul for sharing detailed technical specifications.
Block producer candidates should join the block producer Telegram channel and use whatever other venues that channel recommends.  This forum is for managing defects in the software itself.


What does this integration do?

Nothing is stated in the readme.
And I ask because I have this switch, but I have issues when connecting HomeAssistsant through the switch. It causes issues where it says "reset network adapter". If I connect directly from the router there's no problems

Updated the readme, please check if it clearer now.


Question: can you use this for runtime access of env vars for built apps?

Thanks for this package. I am using it successfully to access env vars to a vite-built app which then gets served by nginx in a Docker environment. To comply with 12factorapp principles I want to be able to access the env vars at runtime not just at build time. Have you found an approach for that either using your package or another?

Hi there!
Given that env variables are statically replaced in your built code, the only way to have "runtime" access to env variables, is to build in the server/environment that has the variables.
In your case, you would need to build in the same container that you plan to deploy.
Feel free to ask follow-up questions
Moving to discussions.


Added property for mouse draggable tab scrollbar to TabbedPanel

Added bar_width and scroll_type properties for ScrollView to enable mouse control of tab scrollbars.
Example:
tp = TabbedPanel(bar_width='10dp', scroll_type=['content', 'bars'])

Maintainer merge checklist

[x] Title is descriptive/clear for inclusion in release notes.
[x] Applied a Component: xxx label.
[ ] Applied the api-deprecation or api-break label.
[x] Applied the release-highlight label to be highlighted in release notes.
[ ] Added to the milestone version it was merged into.
[ ] Unittests are included in PR.
[ ] Properly documented, including versionadded, versionchanged as needed.

I added the version tags.
Please tell me if I make a mistake.


Allow access to a classroom by its password

Allow students to access a classroom using its password.
Stretch goal: separate logged in and not-logged in visualization of classroom

Branch issue-13-allow-access-to-a-classroom-by-its-password created for issue #13.


Error with default settings for bootstrap

execute[bootstrap-platform] action run
================================================================================
Error executing action run on resource 'execute[bootstrap-platform]'
Mixlib::ShellOut::ShellCommandFailed
Expected process to exit with [0], but received '1'
---- Begin output of /opt/opscode/embedded/bin/bundle exec ./bin/bootstrap-platform ./bootstrapper-config/config.rb ./bootstrapper-config/pivotal.yml ----
STDOUT:
STDERR: /opt/opscode/embedded/lib/ruby/2.1.0/net/http.rb:879:in initialize': Connection refused - connect(2) for "<IP_ADDRESS>" port 9463 (Errno::ECONNREFUSED)     from /opt/opscode/embedded/lib/ruby/2.1.0/net/http.rb:879:in open'
from /opt/opscode/embedded/lib/ruby/2.1.0/net/http.rb:879:in block in connect'     from /opt/opscode/embedded/lib/ruby/2.1.0/timeout.rb:76:in timeout'
from /opt/opscode/embedded/lib/ruby/2.1.0/net/http.rb:878:in connect'     from /opt/opscode/embedded/lib/ruby/2.1.0/net/http.rb:863:in do_start'
from /opt/opscode/embedded/lib/ruby/2.1.0/net/http.rb:852:in start'     from /opt/opscode/embedded/service/gem/ruby/2.1.0/gems/rest-client-1.6.8/lib/restclient/request.rb:206:in transmit'
from /opt/opscode/embedded/service/gem/ruby/2.1.0/gems/rest-client-1.6.8/lib/restclient/request.rb:68:in execute'     from /opt/opscode/embedded/service/gem/ruby/2.1.0/gems/rest-client-1.6.8/lib/restclient/request.rb:35:in execute'
from /opt/opscode/embedded/service/gem/ruby/2.1.0/gems/rest-client-1.6.8/lib/restclient.rb:74:in post'     from ./bin/bootstrap-platform:101:in create_object_in_authz'
from ./bin/bootstrap-platform:47:in bootstrap'     from ./bin/bootstrap-platform:120:in '
---- End output of /opt/opscode/embedded/bin/bundle exec ./bin/bootstrap-platform ./bootstrapper-config/config.rb ./bootstrapper-config/pivotal.yml ----
Ran /opt/opscode/embedded/bin/bundle exec ./bin/bootstrap-platform ./bootstrapper-config/config.rb ./bootstrapper-config/pivotal.yml returned 1
Resource Declaration:
In /opt/opscode/embedded/cookbooks/cache/cookbooks/private-chef/recipes/bootstrap.rb
45: execute "bootstrap-platform" do
46:   command "/opt/opscode/embedded/bin/bundle exec ./bin/bootstrap-platform ./bootstrapper-config/config.rb ./bootstrapper-config/pivotal.yml"
47:   cwd opscode_test_dir
48:   retries 3
49:   not_if { OmnibusHelper.has_been_bootstrapped? }
50:   notifies :restart, 'service[opscode-erchef]'
51: end
52:
Compiled Resource:
Declared in /opt/opscode/embedded/cookbooks/cache/cookbooks/private-chef/recipes/bootstrap.rb:45:in `from_file'
execute("bootstrap-platform") do
action [:run]
retries 3
retry_delay 2
default_guard_interpreter :execute
command "/opt/opscode/embedded/bin/bundle exec ./bin/bootstrap-platform ./bootstrapper-config/config.rb ./bootstrapper-config/pivotal.yml"
backup 5
cwd "/opt/opscode/embedded/service/chef-server-bootstrap"
returns 0
declared_type :execute
cookbook_name "private-chef"
recipe_name "bootstrap"
not_if { #code block }
end

Running handlers:
[2016-01-11T12:39:36-05:00] ERROR: Running exception handlers
Running handlers complete
[2016-01-11T12:39:36-05:00] ERROR: Exception handlers complete
Chef Client failed. 22 resources updated in 38 seconds
[2016-01-11T12:39:36-05:00] FATAL: Stacktrace dumped to /opt/opscode/embedded/cookbooks/cache/chef-stacktrace.out
[2016-01-11T12:39:36-05:00] FATAL: Mixlib::ShellOut::ShellCommandFailed: execute[bootstrap-platform] (private-chef::bootstrap line 45) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '1'
---- Begin output of /opt/opscode/embedded/bin/bundle exec ./bin/bootstrap-platform ./bootstrapper-config/config.rb ./bootstrapper-config/pivotal.yml ----
STDOUT:
STDERR: /opt/opscode/embedded/lib/ruby/2.1.0/net/http.rb:879:in initialize': Connection refused - connect(2) for "<IP_ADDRESS>" port 9463 (Errno::ECONNREFUSED)         from /opt/opscode/embedded/lib/ruby/2.1.0/net/http.rb:879:in open'
from /opt/opscode/embedded/lib/ruby/2.1.0/net/http.rb:879:in block in connect'         from /opt/opscode/embedded/lib/ruby/2.1.0/timeout.rb:76:in timeout'
from /opt/opscode/embedded/lib/ruby/2.1.0/net/http.rb:878:in connect'         from /opt/opscode/embedded/lib/ruby/2.1.0/net/http.rb:863:in do_start'
from /opt/opscode/embedded/lib/ruby/2.1.0/net/http.rb:852:in start'         from /opt/opscode/embedded/service/gem/ruby/2.1.0/gems/rest-client-1.6.8/lib/restclient/request.rb:206:in transmit'
from /opt/opscode/embedded/service/gem/ruby/2.1.0/gems/rest-client-1.6.8/lib/restclient/request.rb:68:in execute'         from /opt/opscode/embedded/service/gem/ruby/2.1.0/gems/rest-client-1.6.8/lib/restclient/request.rb:35:in execute'
from /opt/opscode/embedded/service/gem/ruby/2.1.0/gems/rest-client-1.6.8/lib/restclient.rb:74:in post'         from ./bin/bootstrap-platform:101:in create_object_in_authz'
from ./bin/bootstrap-platform:47:in bootstrap'         from ./bin/bootstrap-platform:120:in '
---- End output of /opt/opscode/embedded/bin/bundle exec ./bin/bootstrap-platform ./bootstrapper-config/config.rb ./bootstrapper-config/pivotal.yml ----
Ran /opt/opscode/embedded/bin/bundle exec ./bin/bootstrap-platform ./bootstrapper-config/config.rb ./bootstrapper-config/pivotal.yml returned 1
[root@vm1729701]~# Error executing action run on resource 'execute[bootstrap-platform]'
-bash: run: command not found
-bash: Error: command not found
Try to perform re-run, but still fails, not sure where the issue lies

same here, i don't have any clue. tried to install 12.3.1 and 12.4 so it's should not be version related. i suspect something in the setup but i don't really know what. i'm only running gitlab on my server.

STDERR: /opt/opscode/embedded/lib/ruby/2.1.0/net/http.rb:879:in initialize': Connection refused - connect(2) for "<IP_ADDRESS>" port 9463

9463 is the port by used by the authorization service.  Can you provide the output of:
chef-server-ctl status

tail -100 /var/log/opscode/oc_bifrost/current

sorry @stevendanna , i wiped my vps (ovh) and can't reproduce ; for the record, it was a debian8/64 so i decided to go by the book and i installed a clean ubuntu 14.04 64. I couldn't finish the install of the latest version properly, everytime a different bug (i had the 502 error on all the api calls and also the [pivotal.rb doesn't exist]((/etc/opscode/pivotal.rb does not exist))). Thinking about to shift to ansible/puppet but still giving a try until monday ; available for debug if you're in the will .


fix(@ngtools/webpack): change of CSS no longer breaks rebuild

Fixes #4326
Fixes #4329

nit fixed using regex consts

@Brocco tested the fix in the PR, does not trigger the error anymore 👍

great guys, when do you think this will get into NPM?


[Suggestion] Accept Modded Seeds

As many mods allow vanilla Chickens to be bred with their Seeds, I suggest making those seeds work in the Breeders.

@timrwood Here's what Simple Corn does.


Block type refresh broken

Seems that the block type's refresh method no longer works. When I do changes to the block type's db.xml, it does not update the database table after refreshing the block from the dashboard.

This was actually due to using mixed field definitions (old db.xml format vs new one). I copied it from one of the core blocks although my block was using the new format.
I think this error is still valid in a sense that it would be great if I saw an error instead of c5 not telling me anything when it fails to read a column definition from the db.xml file.

We ran into issues with block types not refreshing as well. What we found after stepping heavily through the code was that there was a duplicate declaration in db.xml for one of the field names. This causes an error in Concrete5 and it fails silently.
Hitting refresh on a block type shows nothing if it doesn't find updates or fails silently and will show this message if it succeeds:

Block Type Refreshed. Any database schema changes have been applied.


Semi-automatic registration

It is possible to make struct registration semi-automatic, using inventory crate. The solution simplifies registration a lot and does not require a centralized registration function with all the structs listed.
A feature (which may not be enabled by default) can be introduced to toggle this, since it requires an additional dependency which may not be wanted.
It can be achieved using these three things:

A helper struct:

pub struct Register(pub fn(&mut World));

An attribute #[register] for impl Trait for Struct, which generates:

inventory::submit!(bevy_trait_query::Register(|world| {
    use bevy_trait_query::RegisterExt;
    world.register_component_as::<dyn Trait, Struct>();
}));

A global registration function, which should be called manually (that's why the solution is semi-automatic):

fn register_traits(world: &mut World) {
    inventory::collect!(Register);
    for callback in inventory::iter::<Register> {
        callback(world);
    }
}

This wouldn't be possible with wasm, maybe the linkme crate would be a better solution

I think we can look into that. As far as I'm aware, inventory isn't supported on WASM though, so this would probably be feature gated. Nice find!

Another option I looked into a while ago is moving trait registration into a method on the Component trait. This would still require you to manually register each trait for each component type (likely using an attribute on the component derive macro) but we could make it a compile-time error if you forget to do so.
When I tried this I ran into issues because currently we rely on all trait components being registered at app startup, whereas with the approach I'm describing each component would only be registered the first time it's used in the World. There's likely a way to work around this, though
I'm on my phone rn but I can go into more detail later if needed

We'd need to add a default method to the Component trait and then add a bevy-trait-query::Component derive macro that would implement it. Its a very small change and the method doesn't need to be for trait queries specifically


Input from image

Import ndarray from a single channel bitmap
AC:

discriminate RGB matrices with error message
amp & phase can be imported through image
lightfield should accept only maching size
add test coverage

Pillow already in packages


Add files URL into product version file

We need to add a new tag to product/version.xml file that will point to /files/ path in order to obtain direct URL to the installation file. It is required to implement in-app updater.

verified


Add link to deployment section

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/reference-architectures/data/enterprise-bi-adf.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


[Issue 10522] support mock zookeeper with different session

fixes #10522
Motivation
support mock zookeeper with different session
Modification
wrap MockZookeeper to support mock zookeeper with different session

ping @merlimat PTAL

Good work @linlinnn


Chinese (and other languages) IME does not work correctly in Edge and IE11

Using the Chinese (and other languages) IME (Input Method Editors) with Monaco in Windows 10 does not work correctly with Monaco in Edge and IE11 browsers.  It seems to work fine in Chrome.
Setup to use Chinese IME, as shown below in Windows 10 task bar:

Typing hazni should give 哈祝你 as it does here.  I have no idea what this spells.  Hopefully, nothing offensive.
Now try to do that in Monaco at https://microsoft.github.io/monaco-editor/playground.html
Using Chrome - works pretty well
Using IE - flaky, but sometimes works
Using Edge - doesn't really work at all

This issue was moved to Microsoft/monaco-editor#104


How to overwrite or remap one directory to another

Is it possible to "remap" a directory to another using polka and sirv?
I created a repository to test the following code:
// index.js
const polka = require('polka');
const sirv  = require('sirv');

const { PORT=3000 } = process.env;

polka()
  // Make "localhost:3000/components" to serve content from "public/compiled_components"
  .use('components', sirv('public/compiled_components'))

  // And everything else remains the same, on "public"
  .use(sirv('public'))

  .listen(PORT, err => {
    if (err) throw err;
    console.log(`Running on localhost:${PORT}`);
  });

My project has the following structure:
project
│   index.js
│
└───public
│   │
│   └───components (non compiled components)
│       │   component1.txt
│       │   component2.txt
│       │   ...
│   └───compiled_components (automatic compiled components, during development time)
│       │   component1.txt
│       │   component2.txt
│       │   ...

But, on the path localhost:3000/components, instead of serving the content of public/compiled_components it is still serving the content of public/components

Sirv shares cache object for all files. I have a change for that incoming to not overwrite existing keys, but for now I think it'll work if you swap the sirv order. That way your compiled components are overwriting what you had inside uncompiled paths.
Really though, you should always be working from a single directory to make your life easy. It also means that your file server has to do less work, sirv or any

for now I think it'll work if you swap the sirv order

Even when swapping, strangely it isn't serving the content of compiled_components:
polka()
  // This first
  .use(sirv('public'))

  // And this later
  .use('components', sirv('public/compiled_components'))

  .listen(PORT, err => {
    if (err) throw err;
    console.log(`Running on localhost:${PORT}`);
  });

I am creating a development tool for a routing library to Svelte, with automatic reload when file changes.
I am trying to don't change the original src files of the developer and, instead, remapping only the directory of components, letting the remaining files untouched.

.use(sirv(public), sirv(public/compiled))

if that doesn't work I have to check back later. I'm traveling today and on the road so I can't take a look right now

Ok, thanks! I will take a look and try my best here :)

You can also run one of the instances in dev mode. This isn't as ideal just because it skips the file caching, which means it will traverse the file system every time. Little more expensive, but that's exactly how other file servers work.
You would have to have the public one in development, But maybe even both

Just to advance the subject, this (and only this) works:
.use(sirv('public/compiled'), sirv('public'), sirv('public/compiled'))

But sharing cache object for all files is a good thing and is performance-wise. And I do not believe my use-case justifies a modification in sirv, since it is not normal.

Your last response was the key. I was forgetting to enable development mode on this test, but I have done it on the library. Doh for me :sweat_smile:

I am doing more tests now.

It works!
polka()
  .use(sirv('public/compiled', { dev: true }), sirv('public', { dev: true }))

This also works:
polka()
  .use(sirv('public/compiled', { dev: true }))
  .use(sirv('public', { dev: true }))
  .listen(PORT, err => {
    if (err) throw err;
    console.log(`Running on localhost:${PORT}`);
  });

Only this does not work, but it isn't an issue for me:
polka()
  .use('components', sirv('public/compiled/components', { dev: true }))
  .use(sirv('public', { dev: true }))
  .listen(PORT, err => {
    if (err) throw err;
    console.log(`Running on localhost:${PORT}`);
  });

Thanks for everything! I believe sirv and polka must remain exactly as they already are. They are awesome!

Great! The last sample will only work in the next version of Polka. The reason it isn't currently working is because stable polka is running use() before use('/foo')

Thanks a lot!


Inconsistent .zprofile documentation

I'm confused by the README file in the runcoms/ folder:

in the entry for .zprofile, it says

See the description of zlogin below for what it may contain.

in the entry for .zlogin, it says

This is not the file to define aliases, functions, shell options, and key bindings. It should not change the shell environment.

in the file zprofile in the runcoms/ folder, you change the shell environment quite a bit

What is the correct way of doing things, here?  The docs in this file give advice which contradicts the files in this directory ...

That file is commonly used for showing login messages.


[Backport 2.12] Update to Gradle 8.5 (#617)

https://github.com/opensearch-project/performance-analyzer/pull/617

@shivamg2017 You are supposed to cherry-pick the single commit only. Looks like you are backporting all the commits from the main to 2.12.


Missing image group

manifest used https://englishextra.github.io/manifest.json
http://manifoldjs.com/generator warning together with the parsed code of the manifets.json:
{
  "name": "englishextra",
  "short_name": "englishextra",
  "manifest_version": 2,
  "icons": [
    {
      "src": "/favicon-16x16.png",
      "sizes": "16x16",
      "type": "image/png"
    },
    {
      "src": "/favicon-32x32.png",
      "sizes": "32x32",
      "type": "image/png"
    },
    {
      "src": "/android-chrome-36x36.png",
      "sizes": "36x36",
      "type": "image/png",
      "density": 1.5
    },
    {
      "src": "/android-chrome-48x48.png",
      "sizes": "48x48",
      "type": "image/png",
      "density": 1.5
    },
    {
      "src": "/favicon-50x50.png",
      "sizes": "50x50",
      "type": "image/png"
    },
    {
      "src": "/favicon-54x54.png",
      "sizes": "54x54",
      "type": "image/png"
    },
    {
      "src": "/favicon-64x64.png",
      "sizes": "64x64",
      "type": "image/png"
    },
    {
      "src": "/favicon-70x70.png",
      "sizes": "70x70",
      "type": "image/png"
    },
    {
      "src": "/android-chrome-72x72.png",
      "sizes": "72x72",
      "type": "image/png",
      "density": 1.5
    },
    {
      "src": "/favicon-90x90.png",
      "sizes": "90x90",
      "type": "image/png"
    },
    {
      "src": "/android-chrome-96x96.png",
      "sizes": "96x96",
      "type": "image/png",
      "density": 1.5
    },
    {
      "src": "/favicon-106x106.png",
      "sizes": "106x106",
      "type": "image/png"
    },
    {
      "src": "/apple-touch-icon-128x128.png",
      "sizes": "128x128",
      "type": "image/png"
    },
    {
      "src": "/mstile-150x150.png",
      "sizes": "150x150",
      "type": "image/png",
      "density": 1.8
    },
    {
      "src": "/mstile-71x71.png",
      "sizes": "71x71",
      "type": "image/png",
      "density": 1.8
    },
    {
      "src": "/apple-touch-icon-76x76.png",
      "sizes": "76x76",
      "type": "image/png"
    },
    {
      "src": "/mstile-99x99.png",
      "sizes": "99x99",
      "type": "image/png",
      "density": 1.8
    },
    {
      "src": "/apple-touch-icon-120x120.png",
      "sizes": "120x120",
      "type": "image/png"
    },
    {
      "src": "/apple-touch-icon-152x152.png",
      "sizes": "152x152",
      "type": "image/png"
    },
    {
      "src": "/mstile-170x170.png",
      "sizes": "170x170",
      "type": "image/png",
      "density": 1.8
    },
    {
      "src": "/apple-touch-icon-180x180.png",
      "sizes": "180x180",
      "type": "image/png"
    },
    {
      "src": "/android-chrome-144x144.png",
      "sizes": "144x144",
      "type": "image/png",
      "density": 1.5
    },
    {
      "src": "/android-chrome-192x192.png",
      "sizes": "192x192",
      "type": "image/png",
      "density": 1.5
    },
    {
      "src": "/android-chrome-196x196.png",
      "sizes": "196x196",
      "type": "image/png",
      "density": 1.5
    },
    {
      "src": "/favicon-256x256.png",
      "sizes": "256x256",
      "type": "image/png"
    },
    {
      "src": "/favicon-512x512.png",
      "sizes": "512x512",
      "type": "image/png",
      "density": 1.5
    },
    {
      "src": "/favicon-1024x1024.png",
      "sizes": "1024x1024",
      "type": "image/png",
      "density": 1.5
    }
  ],
  "splash_screens": [
    {
      "src": "/apple-touch-startup-image-1496x2048.png",
      "type": "image/png",
      "sizes": "1496x2048"
    },
    {
      "src": "/apple-touch-startup-image-1536x2008.png",
      "type": "image/png",
      "sizes": "1536x2008"
    },
    {
      "src": "/apple-touch-startup-image-320x460.png",
      "type": "image/png",
      "sizes": "320x460"
    },
    {
      "src": "/apple-touch-startup-image-640x1096.png",
      "type": "image/png",
      "sizes": "640x1096"
    },
    {
      "src": "/apple-touch-startup-image-640x920.png",
      "type": "image/png",
      "sizes": "640x920"
    },
    {
      "src": "/apple-touch-startup-image-748x1024.png",
      "type": "image/png",
      "sizes": "748x1024"
    },
    {
      "src": "/apple-touch-startup-image-768x1004.png",
      "type": "image/png",
      "sizes": "768x1004"
    },
    {
      "src": "/screen-hdpi-landscape.png",
      "type": "image/png",
      "sizes": "800x480"
    },
    {
      "src": "/screen-hdpi-portrait.png",
      "type": "image/png",
      "sizes": "480x800"
    },
    {
      "src": "/screen-ldpi-landscape.png",
      "type": "image/png",
      "sizes": "320x200"
    },
    {
      "src": "/screen-ldpi-portrait.png",
      "type": "image/png",
      "sizes": "200x320"
    },
    {
      "src": "/screen-mdpi-landscape.png",
      "type": "image/png",
      "sizes": "480x320"
    },
    {
      "src": "/screen-mdpi-portrait.png",
      "type": "image/png",
      "sizes": "320x480"
    },
    {
      "src": "/screen-portrait.jpg",
      "type": "image/jpeg",
      "sizes": "480x800"
    },
    {
      "src": "/screen-620x300-landscape.png",
      "type": "image/png",
      "sizes": "620x300"
    },
    {
      "src": "/screen-868x420-landscape.png",
      "type": "image/png",
      "sizes": "868x420"
    },
    {
      "src": "/screen-768x1024-portrait.png",
      "type": "image/png",
      "sizes": "768x1024"
    },
    {
      "src": "/screen-1024x768-landscape.png",
      "type": "image/png",
      "sizes": "1024x768"
    },
    {
      "src": "/screen-1536x2048-portrait.png",
      "type": "image/png",
      "sizes": "1536x2048"
    },
    {
      "src": "/screen-2048x1536-landscape.png",
      "type": "image/png",
      "sizes": "2048x1536"
    },
    {
      "src": "/screen-1242x2208-portrait.png",
      "type": "image/png",
      "sizes": "1242x2208"
    },
    {
      "src": "/screen-2208x1242-landscape.png",
      "type": "image/png",
      "sizes": "2208x1242"
    },
    {
      "src": "/screen-750x1334-portrait.png",
      "type": "image/png",
      "sizes": "750x1334"
    },
    {
      "src": "/screen-1334x750-landscape.png",
      "type": "image/png",
      "sizes": "1334x750"
    },
    {
      "src": "/screen-640x1136-portrait.png",
      "type": "image/png",
      "sizes": "640x1136"
    },
    {
      "src": "/screen-640x960-portrait.png",
      "type": "image/png",
      "sizes": "640x960"
    },
    {
      "src": "/screen-xhdpi-landscape.png",
      "type": "image/png",
      "sizes": "1280x720"
    },
    {
      "src": "/screen-xhdpi-portrait.png",
      "type": "image/png",
      "sizes": "720x1280"
    },
    {
      "src": "/screen-1116x540-landscape.png",
      "type": "image/png",
      "sizes": "1116x540"
    }
  ],
  "scope": "/",
  "mjs_access_whitelist": [
    {
      "url": "https://englishextra.github.io/"
    }
  ],
  "start_url": "https://englishextra.github.io/",
  "display": "standalone",
  "orientation": "landscape",
  "theme_color": "#D54848",
  "background_color": "#D54848",
  "related_applications": [
    {
      "platform": "web"
    },
    {
      "platform": "android",
      "location": "https://build.phonegap.com/apps/1824701/share"
    },
    {
      "platform": "windowsphone",
      "location": "https://build.phonegap.com/apps/1824701/share"
    }
  ],
  "prefer_related_applications": "false"
}

Warnings (2 items)
icons
Missing image group: A splash screen logo of any of the following sizes is required for Windows: 620x300, 868x420, 1116x540. Platforms affected: windows.

Missing image: A launch image of the following sizes is required: 750x1334, 1334x750, 1242x2208, 2208x1242, 640x1136, 640x960, 1536x2048, 2048x1536, 768x1024 and 1024x768. Platforms affected: ios.

The images exist in th root of the site and they are mentioned in the manifest.json

Thanks for pointing it out.  I think that is just a improper validation rule, should be easy to fix.

Validation is not taking into account splash_screens member. It needs to be updated.

actually, splash screen needs to be removed, it was removed from the W3C manifest.  moving to 0.5.5

@boyofgreen How do you mean? Remove
remove this stuff:
 "splash_screens": [...]

Right?

well, then removed it from the spec, and put everything into the icons section, so we will want to follow suite in the tool.  In your case, your splash screen icons would just move up to the icons set

BTW< @englishextra   this is a beautiful app.  Did you publish it yet?  do you need any help from us?

@boyofgreen I see, thanks, will move splashes to icons for now.
Yes, I published with https://marketplace.firefox.com/
but this:
https://wiki.mozilla.org/Marketplace/FutureofMarketplaceFAQ
got me to remove my webapp.
So I rewrote manifest.json in accordance with http://manifoldjs.com/generator
(that's why I am here)
I have in parallel a redused website version for mobile and desktop
https://englishextraapp.codeplex.com/releases/view/619051
Bu these are not a webapp story what is meant to be:
As I understand it - is that a user visits some site that tells them that a website has or can be a webapp - zipped or online, and manifest.json helps to arrange that.
There I stopped.
Just need to be pointed to further steps - some specs - and I will do it: summer is ahead, there will be
more free time for that.
Thanks for your interest and cooperation.

Hi @englishextra  hope all is well with you.  We are releasing a preview of the next version of manifoldjs specifically geared towards PWAs.  Would you be interested in helping us out as a preview app?  If you email me  I'm<EMAIL_ADDRESS>or boyofgreen on twitter.


space bar

Issue Type: Bug
if am coding and press space bar is not working properly .

You can try this with F1 and >Developer: Reload Window With Extensions Disabled
Please also specify what does "space bar is not working properly" means. Steps to reproduce and recording would be helpful.

On Fri, 8 Apr 2022 at 3:19 PM, VS Code Issue Triage Bot <
@.***> wrote:

Thanks for creating this issue! We figured it's missing some basic
information or in some other way doesn't follow our issue reporting
guidelines https://aka.ms/vscodeissuereporting. Please take the time to
review these and update the issue.
Happy Coding!
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/147088#issuecomment-1092911835,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUDW4LMVAEQP5YI7YIPLFW3VEA55RANCNFSM5S4V6FVA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Thanks it’s working now

If it doesn't work with extensions and works without them you can follow steps from https://code.visualstudio.com/blogs/2021/02/16/extension-bisect to find which extension causes troubles and report issue to corresponding issue tracker.


Vulkan Support

Please consider adding Vulkan support, since it's a newer API that takes advantage of the advancing hardware. In terms of performance, it's better than OpenGL, and also consumes less power, which is especially important for mobile devices. Also, if it's not a stretch, could you possibly just replace OpenGL entirely with Vulkan?
P.S. I'm a novice when it comes to software development, and I don't possess in-depth knowledge of this field yet, so I'm not entirely sure what's possible and what's not.

Never mind, I didn't see that Vulkan support was in progress.

@kdnfgc no one is working on it.  If you want it to exist, I urge you to write it.


Implement process.exit(...) in the runtime

An implementation of process.exit(...) as part of Node.js compat.
Unlike in Node.js, calling process.exit(...) does not actually exit the workerd process, for obvious reasons. Instead, when called within the scope of a request, calling process.exit(...) will cause the current IoContext to be aborted and will call isolate->TerminateExecution() to prevent further execution of JavaScript while leaving the isolate in a good state to run other requests.
This needs to be evaluated very carefully. The approach is a bit of a hack and there might be a better way of doing this that I'm not seeing. So let's not rush this in.

Maybe trigger a specific trace event on process.exit?
I think it can be very confusing to debug a worker that had some random library decide to process.exit().
Possibly even attaching a stacktrace?

Maybe trigger a specific trace event on process.exit?

The error that is reported via ioContext.abort(...) where there is a current IoContext should include the JS stack trace identifying the location of the error, AFAICT. When there isn't an active IoContext the warning that is emitted will also include the stacktrace.

Maybe trigger a specific trace event on process.exit?

The error that is reported via ioContext.abort(...) where there is a current IoContext should include the JS stack trace identifying the location of the error, AFAICT. When there isn't an active IoContext the warning that is emitted will also include the stacktrace.

But will that be reported to a trace worker?

But will that be reported to a trace worker?

Ah, good question. No, because we're aborting the IoContext it would not be reported. I've updated to report to the tracer (if it exists) before calling abort.

Sidenote: When documenting this, we need to remember to emphasize that folks really should not be making use of process.exit(...) in workers, and that any code that does depend on it should be rewritten to avoid it. While we're making it act reasonably here, the pattern of abruptly aborting the request context and terminating javascript execution can be problematic, especially if that happens in the middle of updating some global state.

aborting the request context and terminating javascript execution can be problematic

It's way above my understanding of workerd. But could the workerd impl be more problematic than a process.exit() on i.e. Node?

I'm not sure I understand the question. The key difference in workerd is that we're not actually going to destroy the isolate so additional requests can be processed. Depending on when the process.exit(...) is called and what else is happening, the globalThis state could potentially be left in a bad state but there's not a lot we can do about that. I suppose we could take the additional step of condemning the isolate but I'm not sure that's the right thing. Interested in @kentonv's thoughts on that

I'm not sure I understand the question.

That's probably because I don't know enough about workerd.

globalThis state could potentially be left in a bad state

That sounds scary to me - do we really want to allow this?

Well, the bad state would essentially be bad application state, not runtime state... and it's entirely dependent on what the user code is doing.... which gets us back to warning developers away from depending on / using process.exit at all. Also, in the future if/once we get Lightweight Isolate Clones this problem goes away entirely. I think for right now, as long as the runtime state is good and we've got proper warning markers in place telling folks to avoid using process.exit(...) we should be fine.

That sounds scary to me - do we really want to allow this?

Well, the bad state would essentially be bad application state, not runtime state... and it's entirely dependent on what the user code is doing.... which gets us back to warning developers away from depending on / using process.exit at all. Also, in the future if/once we get Lightweight Isolate Clones this problem goes away entirely. I think for right now, as long as the runtime state is good and we've got proper warning markers in place telling folks to avoid using process.exit(...) we should be fine.

Perhaps a compat flag that would switch between aborting and throwing a JS exception would be nice to allow users to “gracefully” shutdown in case an external library process.exit’d

Well, the bad state would essentially be bad application state, not runtime state...

Ok so that was my initial understanding and the reason why I asked the initial question: how different would it be in workerd vs Node? Would this impl of process.exit() in workerd potentially cause more damage than calling process.exit() in Node?

Just throwing a catchable error is likely to be more dangerous -- we really shouldn't allow the user to ignore that process.exit(...) was called as that would be more likely to lead to conditions of application code getting into a bad state. I think we want to be noisy and disruptive when process.exit(...) is called -- if for no other reason than to make it explicitly clear that code running in workers should NOT be depending on it.

I think we should start charging customers $10 each time they call that process.exit ;)

We're really excited about this one! Biggest issue for us is that there are dependencies that have process.exit, that will not be called in the production code path. But because of build time checks, we can't actually use those dependencies. So this will be a huge unblock. Thanks everyone!

We're really excited about this one! Biggest issue for us is that there are dependencies that have process.exit, that will not be called in the production code path. But because of build time checks, we can't actually use those dependencies. So this will be a huge unblock. Thanks everyone!

@pkiv if there is any other blockers for you, please open an issue at the workerd repository. we'll like to take a look!

think we should start charging customers $10 each time they call that process.exit

Feel free to direct all payments into my venmo account.

We should add a test for behavior in Durable Objects. The behavior should be that it restarts the object -- same as DurableObjectState::abort() would.

DO test added

This landed in https://github.com/cloudflare/workerd/releases/tag/v1.20241018.0 but isn't yet available to use on latest Wrangler (3.83.0) — unenv throws an unimplemented error.
I think we have added to the runtime but until unenv is updated, this is not actually usable in practice. Verified by going to the Quick Editor in the dash — because there is no polyfilling there, you can see this working.

This landed in https://github.com/cloudflare/workerd/releases/tag/v1.20241018.0 but isn't yet available to use on latest Wrangler (3.83.0) — unenv throws an unimplemented error.
I think we have added to the runtime but until unenv is updated, this is not actually usable in practice. Verified by going to the Quick Editor in the dash — because there is no polyfilling there, you can see this working.

The PR should be in the next release on Tuesday


[Tab] tab.onFirstLoad fires multiple times

https://jsfiddle.net/vdff7xep/
tab.onFirstLoad is called multiple times when using tab.tab('change to', 'path'). When executing this command, you'll get the same number of callbacks through onFirstLoad() as you have tabs, yet each time the path parameter is the same (the one used in the command). If you don't use the change to command, then clicking on the tabs works as expected, with a single call through onFirstLoad for each clicked tab.
My intention is to use onFirstLoad to initialize the data in each tab segment on user demand.

Technically you are calling change tab three times, because each item is invoking change tab
You can solve this by using
$tabs.first().tab('change tab', 'one');

https://jsfiddle.net/qfdz44ps/