Debian/Ubuntu package repository broken

When doing apt update:
Error:16 http://packages.microsoft.com/repos/vscode stable/main amd64 Packages
  File has unexpected size (156354 != 156065). Mirror sync in progress? [IP: <IP_ADDRESS> 80]
  Hashes of expected file:
   - Filesize:156065 [weak]
   - SHA512:12e6dffcd247d1ff067acfa61a3c4eb6078c326c2858feb4f6f141a1d809e22292a78282414a5c103038ea80bb63cd734c7516782c9809c341335083d4e7611b
   - SHA256:c850f35f1979831ac75641978c397e51519fa22313598ec12bde5f52277044c0
   - SHA1:1f65f4a7388c22bcf7b7f30fb7bc337c60d94b2e [weak]
   - MD5Sum:4153a12e4a5629bfb14ed98f4c8ac234 [weak]
  Release file created at: Thu, 12 Dec 2019 19:59:19 +0000

me too:
Holen:32 http://packages.microsoft.com/repos/vscode stable/main amd64 Packages [156 kB]
Fehl:32 http://packages.microsoft.com/repos/vscode stable/main amd64 Packages
Datei hat eine unerwartete Größe (156354 != 156065). Eventuell läuft gerade eine Spiegel-Synchronisierung? [IP: <IP_ADDRESS> 80]
Hashes of expected file:

Filesize:156065 [weak]
SHA512:12e6dffcd247d1ff067acfa61a3c4eb6078c326c2858feb4f6f141a1d809e22292a78282414a5c103038ea80bb63cd734c7516782c9809c341335083d4e7611b
SHA256:c850f35f1979831ac75641978c397e51519fa22313598ec12bde5f52277044c0
SHA1:1f65f4a7388c22bcf7b7f30fb7bc337c60d94b2e [weak]
MD5Sum:4153a12e4a5629bfb14ed98f4c8ac234 [weak]
Release file created at: Thu, 12 Dec 2019 19:59:19 +0000

Seems, this has happened already in last January and has to be fixed by the repo-admins.

Can confirm.

Same here

Hi! Exact same thing here.
E: Impossible de récupérer http://packages.microsoft.com/repos/vscode/dists/stable/main/binary-amd64/Packages.bz2  Le fichier a une taille incohérente (156354 != 156065). Le miroir est peut-être en cours de mise à jour ? [IP : <IP_ADDRESS> 80]
   Hashes of expected file:
    - Filesize:156065 [weak]
    - SHA512:12e6dffcd247d1ff067acfa61a3c4eb6078c326c2858feb4f6f141a1d809e22292a78282414a5c103038ea80bb63cd734c7516782c9809c341335083d4e7611b
    - SHA256:c850f35f1979831ac75641978c397e51519fa22313598ec12bde5f52277044c0
    - SHA1:1f65f4a7388c22bcf7b7f30fb7bc337c60d94b2e [weak]
    - MD5Sum:4153a12e4a5629bfb14ed98f4c8ac234 [weak]
   Release file created at: Thu, 12 Dec 2019 19:59:19 +0000

Debian 10 Buster. This issue really looks like to #41094 and #45868

I also confirm the issue

Same for me on Ubuntu 18.04.3 LTS, looks also similar to #86858

Me too on Debian Bullseye
Err:11 http://packages.microsoft.com/repos/vscode stable/main amd64 Packages
  File has unexpected size (156354 != 156065). Mirror sync in progress? [IP: <IP_ADDRESS> 80]
  Hashes of expected file:
   - Filesize:156065 [weak]
   - SHA512:12e6dffcd247d1ff067acfa61a3c4eb6078c326c2858feb4f6f141a1d809e22292a78282414a5c103038ea80bb63cd734c7516782c9809c341335083d4e7611b
   - SHA256:c850f35f1979831ac75641978c397e51519fa22313598ec12bde5f52277044c0
   - SHA1:1f65f4a7388c22bcf7b7f30fb7bc337c60d94b2e [weak]
   - MD5Sum:4153a12e4a5629bfb14ed98f4c8ac234 [weak]
  Release file created at: Thu, 12 Dec 2019 19:59:19 +0000
Fetched 3,959 B in 2s (2,229 B/s)

E: Failed to fetch http://packages.microsoft.com/repos/vscode/dists/stable/main/binary-amd64/Packages.bz2  File has unexpected size (156354 != 156065). Mirror sync in progress? [IP: <IP_ADDRESS> 80]
   Hashes of expected file:
    - Filesize:156065 [weak]
    - SHA512:12e6dffcd247d1ff067acfa61a3c4eb6078c326c2858feb4f6f141a1d809e22292a78282414a5c103038ea80bb63cd734c7516782c9809c341335083d4e7611b
    - SHA256:c850f35f1979831ac75641978c397e51519fa22313598ec12bde5f52277044c0
    - SHA1:1f65f4a7388c22bcf7b7f30fb7bc337c60d94b2e [weak]
    - MD5Sum:4153a12e4a5629bfb14ed98f4c8ac234 [weak]
   Release file created at: Thu, 12 Dec 2019 19:59:19 +0000

same

Same for me. Ubuntu 19.04

Same issue

I'd suggest people stop adding "mee too" comments, if it's broken on the server then it's broken for everyone.

Not only vscode, I see dotnet repo broken too

/duplicate of #86858


Missing build.upload main file gives: Uncaught TypeError: Main module name is not present in bundle.

Following on from #1951, if a user misconfigures the main file for a modules project, no error is reported from the command line. Instead, the file appears to be uploaded but then the API actually reports the following error:
Error: Something went wrong! Status: 400 Bad Request, Details {
  "result": null,
  "success": false,
  "errors": [
    {
      "code": 10021,
      "message": "Uncaught TypeError: Main module name is not present in bundle.\n  at line 0\n"
    }
  ],
  "messages": []
}

Obviously, wrangler should be verifiying that whatever file it's trying to upload actually exists before this, and report an error message like Error: main file './dist/dist/index.mjs' does not exist. Cannot upload Worker.. This would indicate to the user that the error is the in the config (i.e. the path ./dist/dist/index.mjs is not what's specified in wrangler.toml), not in the contents of the file ("main module name is not present").
Reporting this so the error message is googlable, if you hit this the bug is probably the same one I hit in #1951

TODO add better error specifying which module is missing

Please do soon, linking weirdness around specifying upload file with this template: https://github.com/cloudflare/modules-rollup-esm/blob/master/wrangler.toml
Apparently you pass the bundle output to dist, and then point wrangler to top level directory when neither input nor output are in it.

This is a lot better in wrangler2; we're explicit about the path to the worker (re: https://github.com/cloudflare/wrangler/issues/1951#issuecomment-1064831946) and we specifically call out that we couldn't resolve a file at the given path in the error message in the above scenario.

Closing this since wrangler v2 is now in GA


gsl: 2.6 -> 2.7

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/gsl/versions.
meta.description for gsl is: "The GNU Scientific Library, a large numerical library"
meta.homepage for gsl is: "https://www.gnu.org/software/gsl/"
meta.changelog for gsl is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

/nix/store/2wrbz52jjq0150jmlraxbqqlcx5yypys-gsl-2.7/bin/gsl-randist passed the binary check.

/nix/store/2wrbz52jjq0150jmlraxbqqlcx5yypys-gsl-2.7/bin/gsl-histogram passed the binary check.

/nix/store/2wrbz52jjq0150jmlraxbqqlcx5yypys-gsl-2.7/bin/gsl-config passed the binary check.

3 of 3 passed binary check by having a zero exit code.

1 of 3 passed binary check by having the new version present in output.

found 2.7 with grep in /nix/store/2wrbz52jjq0150jmlraxbqqlcx5yypys-gsl-2.7

found 2.7 in filename of file in /nix/store/2wrbz52jjq0150jmlraxbqqlcx5yypys-gsl-2.7

directory tree listing: https://gist.github.com/0892bb7a046611cb3fb023a8b80e223c

du listing: https://gist.github.com/dbc5fa270a2ba3357088ec1f2b303f51

Rebuild report (if merged into master) (click to expand)

514 total rebuild path(s)

156 package rebuild(s)

156 x86_64-linux rebuild(s)
142 i686-linux rebuild(s)
75 x86_64-darwin rebuild(s)
141 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
ViennaRNA
adapta-gtk-theme
arc-theme
arx-libertatis
asciidoc-full
asciidoc-full-with-plugins
bibata-cursors
bibata-cursors-translucent
bibata-extra-cursors
btrbk
calligra
capitaine-cursors
ccache
ccacheStdenv
ccacheWrapper
chrome-gnome-shell
cinnamon.cinnamon-screensaver
cinnamon.iso-flags-png-320x420
cinnamon.iso-flags-svg
clevis
clight
d-seams
dblatexFull
digikam
disorderfs
emojione
enblend-enfuse
est-sfs
ezminc
fim
giac
giac-with-xcas
gjay
gmic-qt-krita
gnome.gnome-documents
gnome.gnome-session
gnome.gnome-shell
gnome.gnome-terminal
gnome.gnome-tweak-tool
gnome.gnome-tweaks
gnome.gnome_session
gnome.gnome_shell
gnome.gnome_terminal
gnome.pomodoro
gnomeExtensions.easyScreenCast
gnomeExtensions.gsconnect
gnomeExtensions.night-theme-switcher
gnss-sdr
gnuradio
gnuradio3_7

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/2wrbz52jjq0150jmlraxbqqlcx5yypys-gsl-2.7 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A gsl https://github.com/r-ryantm/nixpkgs/archive/e5e91af069e8f0e2f9e21ab59f0c2f38c3aafe79.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/2wrbz52jjq0150jmlraxbqqlcx5yypys-gsl-2.7
ls -la /nix/store/2wrbz52jjq0150jmlraxbqqlcx5yypys-gsl-2.7/bin

Pre-merge build results
NixPkgs review skipped

Maintainer pings

Result of nixpkgs-review pr 125453 at e5e91af0 run on x86_64-linux 1

9 packages marked as broken and skipped:

gnuradio3_7
gnuradio3_7Packages.ais
gnuradio3_7Packages.gnuradio
gnuradio3_7Packages.gsm
gnuradio3_7Packages.limesdr
gnuradio3_7Packages.nacl
gnuradio3_7Packages.osmosdr
gnuradio3_7Packages.rds
k2pdfopt

1 package failed to build:

lush2

130 packages skipped due to time constraints:

adapta-gtk-theme
arc-theme
arx-libertatis
asciidoc-full
asciidoc-full-with-plugins
bibata-cursors
bibata-cursors-translucent
bibata-extra-cursors
btrbk
calligra
...

9 packages built successfully:

ViennaRNA (python38Packages.ViennaRNA ,python39Packages.ViennaRNA)
est-sfs
gsl
indilib
lib2geom
python38Packages.cvxopt
python38Packages.picos
python39Packages.cvxopt
xaos

1 suggestion:

warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/libraries/gsl/default.nix:21:3:
   |
21 |   meta = {
   |   ^

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement. Does something look off? Please file an issue or reach out on IRC.

nixpkgs-review reports no new failures for macos 10.15.


Using httprouter

The httprouter by Julien Schmidt allows greater modularity by separating the routes by verb and isolating the routes in a separate file.

@GaiusMartius I'll do a proper review in a day or so: caught up with end of semester final exams here :(
Thanks!

Hi @GaiusMartius, sorry if I don't get this but in this case httprouter and alice work together to wrap middleware onto specific request methods. Wouldn't middleware be simpler using the stldlib?
e.g. something like this would achieve similar effect
//..
http.Handle("/create",CORS(http.HandlerFunc(createCommentHandler)))
//...

// CORS middleware
func CORS(next http.Handler) http.Handler{
    return http.HandlerFunc( func(w http.ResponseWriter, r *http.Request){
        w.Header().Set("Access-Control-Allow-Origin", "*")
        next.ServeHTTP(w,r)
    })
}

As for method routing, simply checking r.Method may suffice since we are using few handlers, unless am missing something. Otherwise, I think a lot stuff in these commits are great.

Alice allows the chaining of middleware which gets more convenient the larger number of methods you have.
Consider this example:
`
unsecured = alice.New(RecoverHandler, CleanupHandler, TimingHandler)
secured = alice.New(RecoverHandler, JwtHandler)
router.Get("/comments", secured.ThenFunc(getCommentsHandler))
router.Post("/comments", secured.ThenFunc(createCommentHandler))
router.Get("/version", unsecured.ThenFunc(versionHandler))
`
Now, if I would like to make the version endpoint above a secured endpoint I only need to delete two letters and 'unsecured' becomes 'secured'.
Another benefit of alice is that it makes it easier to read off which middleware being used as you can just read function names left to right as in the above example. It helps with code readability.

Closing (see gitter)


Strange returned value from MQTT switch

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.46.1
Python release (python3 --version):
3.4
Component/platform:
switch
mqtt
raspberry pi 3
NodeMCU devkit
Description of problem:
Strange returned value when I turn the mqtt switch On-Off.
When turned on: "ON0-1"
When turnmed off: "OFF-1"
Expected:
When turned on: "ON"
When turned off: "OFF"
Problem-relevant configuration.yaml entries and steps to reproduce:
switch 0:
  - platform: mqtt
    name: mist-generator-1
    command_topic: "room/manual-control/mist-generator-1"
    payload_on: "ON"
    payload_off: "OFF"

Write arduino program, using PubSubClient to subscribe the topic described above
Upload the code on a NodeMCU dev-kit and open serial monitor to view the return value from the topic

Traceback (if applicable):

Additional info:

Can you double-check your code for the nodemcu especially the callback part? What do you get when subscribing to room/manual-control/# with mosquitto_sub?

I will close this issue due to the lack for further information.
Please use the forum for questions about installation, setup, and configuration.
If it's a bug, please re-open the issue.


New version: Termius.Termius version 8.9.7

Pull request has been created with komac v2.1.0 :rocket:

Resolves #140062

Microsoft Reviewers: Open in CodeFlow

Close with reason: Duplicate of #139932;


Request: add specialized message class

In my plugin PhantomWorlds, the version v2.0.0 added a specialized class for creating messages with placeholders. I want to transfer that class into MicroLib so developers can use it in their plugins. I want to implement this into LevelledMobs as soon as it is added.

Done


Berlin Hardfork Updates

Update for upcoming Berlin hardfork, specifically adding BEGINSUB, JUMPSUB, and RETURNSUB opcodes from EIP-2315.

The Berlin spec has been (mostly?) finalized. Fork block is still TBD.
https://github.com/ethereum/eth1.0-specs/blob/master/network-upgrades/berlin.md

The Berlin spec has been (mostly?) finalized. Fork block is still TBD.
https://github.com/ethereum/eth1.0-specs/blob/master/network-upgrades/berlin.md

I'm looking forward to your breakdown of the dynamic costs of SLOAD and SSTORE from EIP-2929. :slightly_smiling_face: Lately I find myself consulting this EIP but I find it hard to navigate.
Love this resource you've put together. Thanks!

@frangio yeah this is a tricky EIP. I need to take a bit more time on this one, but I'm hoping to update it soon

https://gist.github.com/holiman/460f952716a74eeb9ab358bb1836d821

https://twitter.com/TimBeiko/status/1362772348047294466

@frangio If you have a chance to look over the diff for EIP-2929, any corrections you see are very appreciated.

Merged in #8.


Upgrading to 1.0.18 breaks application

Just upgraded ng2-bootstrap to version 1.0.18 and started receiving this error in console every time I load my application

Error: (SystemJS) ReferenceError: __decorate is not defined
at eval (http://localhost:3000/node_modules/ng2-bootstrap/components/accordion/accordion.component.js:30:5)
at Object.eval (http://localhost:3000/node_modules/ng2-bootstrap/components/accordion/accordion.component.js:46:2)
at eval (http://localhost:3000/node_modules/ng2-bootstrap/components/accordion/accordion.component.js:49:4)
at eval (http://localhost:3000/node_modules/ng2-bootstrap/components/accordion/accordion.component.js:50:3)
Evaluating http://localhost:3000/node_modules/ng2-bootstrap/components/accordion/accordion.component.js
Evaluating http://localhost:3000/node_modules/ng2-bootstrap/components/accordion.js
Evaluating http://localhost:3000/node_modules/ng2-bootstrap/ng2-bootstrap.js
Evaluating http://localhost:3000/build/component/configuration/configuration-mode.component.js
Evaluating http://localhost:3000/build/component/configuration/routes.js
Evaluating http://localhost:3000/build/app.routes.js
Evaluating http://localhost:3000/build/main.js
Error loading http://localhost:3000/build/main.js

Downgrading to 1.0.17 resolves this issue.
Thanks in advance

See https://github.com/valor-software/ng2-bootstrap/issues/719

@ArtemBrovko Fixed in 1.0.20


Fixes #8 : node_for_release should not return []

Fixes #8
Ping @jeriox

Successful PR Checklist:

[x] Tests

[ ] (not applicable?)

[ ] Documentation

[x] (not applicable?)

[x] Had a good time contributing?

Damn, is this repo still using travis ? Guess I'll have to update first.


Fixes #6641

One more try ;). Accroding to the contribution guidelines now.

The only thing which follows contribution guidelines is your branche's name.
Closing. Please, read contribution guidelines carefully.
1.Give your PR a title descriptive to your changes.
2. Do not include issue numbers in you PR's title, branch name or commit message. If your PR fixes some issue you can add closes #xxxx to your comment where xxxx is issue;s number. This will close that issue when your PR is merged.
Feel free to reopen with changed title and amended commit or open a new PR which follows contribution guidelines. Thanks.


Fix dlsym definition

Checklist

[ ] Used a fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

Jinja2 variable references are suggested to take a {{<one space><variable name><one space>}} form. See lines [9].

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@ph-ilten I don't know if anyone monitors GitLab for Pythia 8 but I've opened a merge request with this patch and details for why I think it's needed: https://gitlab.com/Pythia8/releases/-/merge_requests/1

@chrisburr I've closed that merge request and opened it in the private Pythia 8.3 repository. For this patch, can we just remove all the lines that redefine dlsym? With recent versions of GCC this fixes the problem, and does not result in us just redefining what is already defined in the header.


Add FCLCrypto to default deployed contracts

FCLCrypto contract should be deployed along with default contracts on emulator start
Dev wallet relies on FCLCrypto Contract and currently needs to be manually deployed to avoid an error
when authenticating with FCL ^1.0.0
If added as one of the default contracts on emulator start, this step and error can be avoided.
https://github.com/onflow/fcl-contracts/tree/main/contracts

@gregsantos sorry for late reply, should we prioritize this in this sprint?

No problem @sideninja
Yea, i think it is a good idea to prioritize this sprint as it will address a prominent issue with local development.

why this contract exists btw ? it seems like it is just one function.

@gregsantos I'm finishing up this task, but I would need the https://github.com/onflow/fcl-contracts to become public repo.

@psiemens may need to open as code owner
@bluesign This contract is used in verifying signatures (user, and account-proof)

I understand @gregsantos but as I mentioned earlier[0], especially emulator has so many unnecessary contracts.
To run a single function, deploying a new contract, seems little unnecessary to me. Is there a specific reason for this to be a contract, instead of Function in the script ?
[0] https://github.com/onflow/flow-emulator/issues/170

@bluesign Thanks Deniz, your thoughts on emulator contracts makes sense.
We created the FCLCrypto contract when the cadence Crypto lib was removed and to help with transition to account-proof v2. We may switch back to using a script, making this unnecessary soon. For now it might be better to deploy the contract along with others in the dev-wallet. Closing this in favor of https://github.com/onflow/fcl-dev-wallet/issues/136


Added ZRS Locations for Image Version Replication Regions

Added a ResourceTypes API call for Microsoft.Storage to get the zone mappings for storage accounts.  If a user selects ZRS storage for the Storage Account Type input, the zone mapping locations are used for the allowed values in the drop-down menu for the Image Version's primary and DR locations.  Since the ZRS supported locations are now included, I also removed the warning boxes about selecting an appropriate location for ZRS storage.  Thank you @shawntmeyer for the help with this!!

@danycontre, hold off on merging this PR.  Found an issue.  My build failed b/c I picked a region that didn't support ZRS.
@shawntmeyer, the zone mappings locations don't appear to be accurate.  I was able to pick West US which is not zone redundant.

After comparing the zone support doc against the values in the drop-down menu, there appear to be two locations in the drop-down menu that don't exist in the doc: North Central US and West US.  I can attempt to manually filter these out and submit feedback to have it fixed.  What are your thoughts @danycontre & @shawntmeyer?

I ran an API call in PowerShell to check the data.  So, for some reason those two locations have been added even though they have no zones. We'll have to add another filter for the zone mappings locations that don't have an array length of 3 on the zones.
location             zones

Australia East       {2, 3, 1}
Brazil South         {2, 3, 1}
Canada Central       {2, 3, 1}
Central India        {2, 3, 1}
Central US           {2, 3, 1}
East Asia            {2, 3, 1}
East US              {2, 3, 1}
East US 2            {2, 3, 1}
France Central       {2, 3, 1}
Germany West Central {2, 3, 1}
Japan East           {2, 3, 1}
Korea Central        {2, 3, 1}
North Central US     {}
North Europe         {2, 3, 1}
Norway East          {2, 3, 1}
Qatar Central        {2, 3, 1}
South Africa North   {2, 3, 1}
South Central US     {2, 3, 1}
Southeast Asia       {2, 3, 1}
Sweden Central       {2, 3, 1}
Switzerland North    {2, 3, 1}
UAE North            {2, 3, 1}
UK South             {2, 3, 1}
West Europe          {2, 3, 1}
West US              {}
West US 2            {2, 3, 1}
West US 3            {2, 3, 1}

I added a filter to ensure each location has 3 zones which removes North Central US and West US.  All is well now so this PR is ready for review and merging.

@jamasten sorry i'm late to the discussion, agree with introducing a filter to remove zones flagged as AZ capable even though they have none.
A usual thanks for your contribution.

@danycontre, I’ve implemented the filter which fixes the locations.  North Central US and West US are no longer displayed in the drop down menus.  This can be merged unless there’s another problem that I missed.


New Output For Batch Plugin

For testing the process mining algorithm, we need a new output for batch activities whis is a csv file with the following data:

Case id
Activity name
Enable time
Start time
Completion time
Resource
Batch id
One row should visualize, one process instance with all data described before.

Has been closed by 73f052902c646023719babb3130580833a2ebb0d and the following commits


TE-2.1 tests both PRESERVE and DELETE, and other gRIBI skip style fixes

Resolves #601
Co-authored-by: mojiiba<EMAIL_ADDRESS>

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1462

Relevant Lines:
2012

💛  - Coveralls

Conflicting file needs to be resolved:

feature/gribi/otg_tests/ipv4_entry_test/ipv4_entry_test.go


Removed saicharan0112/OpenFASOC:openfasoc_ci branch dependency for CI

I removed my openfasoc_ci branch dependency for smoke testing. Now the testing happens with a new image which was created above efabless/openlane:2021.12.22_01.51.18 along with the addition of pdk data (which was built somewhere around Nov 2021).
This is still a temporary solution until we find stable commit numbers of all tools for OpenFASOC to run.

Sorry for all those later commits.. I was just updating the readme file to run the generators using this docker image.


[main] Upgrade to latest dependencies

Cron -knative-prow-robot
/cc knative-extensions/serving-writers
/assign knative-extensions/serving-writers
Produced by: knative-extensions/knobots/actions/update-deps

needs https://github.com/knative/pkg/pull/2966

/retest
/lgtm
/approve

/lgtm

/hold cancel


hide address as soon as its use is detected in the tx pool

Feather hides an address when a confirmed transaction had paid to it. this is great for preventing address reuse and protecting privacy that some wallets fail to realize.
I suggest hiding an address at an earlier stage, when an unconfirmed transaction in the transaction pool is expected to pay to it. this would further reduce the chance of giving out the same address twice. this gains further importance when the transaction isn't included in a block for a longer time (e.g. fee too low for network conditions).
if the transaction is never included in a block, it would still make sense to keep the address hidden, since the unconfirmed transaction's appearance proves that the address had been given out.
the downside is that restoring the same wallet from the mnemonic wouldn't result in the same set of unused addresses. however, I think this is close to being a non-issue, and keeping the address hidden even in just one instance of the wallet would still reduce the chance of the address being reused.

I suggest hiding an address at an earlier stage, when an unconfirmed transaction in the transaction pool is expected to pay to it.

Implemented in https://github.com/feather-wallet/monero/commit/665c304735b68b2a6e55ed8a5efadbeb60056248.


Folder names should not have spaces

Folder names should not use spaces as a delimiter; use an underscore or hyphen.

Hi
Thank you for sharing your thoughts with us; we truly value your feedback.


Ellipsis class content is garbled

I'm seeing garbled content for the .ellipsis class when the tree is collapsed.

Inspector Content:

Has anyone run into this issue?
Thanks!

Just needed to add UTF-8 charset as a meta tag in head
<meta charset="utf-8"/>

I would consider adding this to the sample index.html file in the README.
Thanks!

@sarus dup of https://github.com/Rebilly/ReDoc/issues/29

@sarus nice catch with <meta charset="utf-8">.
Adding to sample index.html
Thanks

For information, it may not be enough to add <meta charset="utf-8"> in the page. The response header can override this setting.
In my case, the index.html page is served by a Java servlet, and I need to set the response encoding explicitly (response.setCharacterEncoding("UTF-8")).


Fix android CHIPTest linkage after #36297 .

Tested locally that android-arm64-chip-test builds.

Hotfixing it in as this is only tested in master CI currently and I checked compilation locally.


Use more descriptive middleware names

We currently let you use a lot of components like ConversationState, UserState, and the LuisRecognizer either as middleware or free standing within your bot logic.  One issue with this approach is that when you use() one of these components as middleware its not abundantly clear what's being done.  An alternate approach we could take would be to wrap things like ConversationState with a separate class when used as middleware and then use much more descriptive names for our middleware that better describe whats being done.  For example (in JavaScript):
const storage = new MemoryStorage();
const conversationState = new ConversationState(storage);
const userState = new UserState(storage);

adapter.use(new CatchErrors((err) => console.error(err.toString())))
            .use(new ReadAndWriteBotState(conversationState, userState));

The ReadAndWriteBotState class in the example above is just our existing BotStateSet class renamed.  This could be generalized even further to a ReadAndWrite class that can work with any component that implements ICanReadAndWrite.

@Stevenic This sounds like a similar conversation I was having with @billba and @drub0y earlier this week where I was talking specifically about BotState.  Here is a summary of my comments...
At the moment I feel it is confusing for developers that BotState is implemented as middleware, with the option of also using it on its own (this works in JS currently and there is an open PR to address this in the immediate term for .Net).  I think this can be confusing for developers – even I who have a descent understanding of what is there at present had not understood that BotState could be used outside of middleware.  It also leaves the naming of BotState inconsistent with other middleware components, with all other components having the ‘middleware’ suffix. E.g. ShowTypingMiddleware and RegExpRecognizerMiddleware.
Clear split out BotState into its own class which handles the storage and retrieval of state objects, along with the option to key the state objects to allow N number of objects to be stored against a conversation or a user.  The BotState could be used on isolation with the appropriate Read / Write methods to store and retrieve state.  This unblocks the ability for middleware to manage it’s own state and also means that, should a developer choose to, they can explicitly choose when state is read from and written to within their bot.
A potential solution for this could be the following....A separate middleware component, BotStateMiddleware, would be created which would use the BotState class to provide the current ability to have state read from storage and stored on the context.services property and automatically persisted on the trailing edge of the pipeline.  This also has the advantage of ensuring that the middleware component is only responsible for a specific set of activities. I.e. adding current state to the context at the start of a turn and persisting any changes at the end of a turn.

I am not wedded to the idea of having a middleware suffix, but I do like the separation of things like state and middleware that takes advantage of state or, another example, luis recognizer, with middleware that uses the recognizer.

@garypretty I'm not crazy about putting the Middleware suffix on every class.  We discussed this internally and everyone agreed that it feels a bit redundant in most cases.  What I'm arguing for as much as anything is for naming the describes what the middleware is doing.  Another example is the BatchOutput class. Nothing in the class name tells you that when you add it as middleware it's going to automatically flush the batch at the end of the request but if you instead add use(new FulshBatchOutput())  to your bot it's a little clearer that adding that will cause any batched replies to be automatically flushed.

@Stevenic Yes. Agree with this. As I say, not tied to the suffix for the naming. I definitely agree that more descriptive naming is a great idea. Your example around state maps perfectly to my thoughts (I think!). Ie. Have an object, UserState that manages state, but then middleware that can use this to read stage to the context and  persist changes, named say, ReadAndPersistUserState. I guess I'm just not a massive fan of mixing the two together into a single object (which then precludes the more descriptive naming). At the end of the day I don't think it's the end of the world or something that HAS to change either, but wanted to come in with my thoughts.

Another idea is to use a specific named method from an object, e.g.
.use(ConversationState.readAndPersistState)

So the other thing I'd say about state in particular. I'f you're managing more than one piece of state you're likely going to want to read & write them in parallel so you're down the path of a separate component that you pass your individual state objects into.  We already have that component it's called the BotStateSet class.
To make the changes from this proposal a bit more concrete... We would rename BotStateSet to something more descriptive like ReadAndWriteBotState as that's what it does.  We'd then change BotState and derived classes to not implement Middleware.  If you want to automatically read and write even a single piece of state you would have to use the ReadAndWriteBotState middleware.
I know this is actually removing functionality but I think it's potentially removing some confusion I saw our documentation writers struggling with last week.  The fact you can use BotState on it's own or as middleware seemed to confuse things for them to the point they were trying to do both in their code. They added ConversationState to their bot as middleware then tried manually call write() at the end of their code.  My hope is the separation of concerns will make everything a bit clearer and I think this applies to more than just state which is why I called the change out as philosophical change.

This makes a lot of sense to me. It aligns with stuff @drub0y's has been working on.

Just to be clear, are we suggesting that we have ReadAndWriteBotState for managing state via middleware, but we still give the user the ability to use BotState on its own if desired? If so then this is exactly what I would like to see and aligns with my proposal too.

Looks like this is in line with what @drub0y is suggesting as part of his DCR / PR #375 for state overhaul. 👍


file clang bug on scaling problem with fold-expressions

At https://github.com/mattbierner/Super-Template-Tetris/blob/master/tetris/main.cpp#L16, some kind of problem is observed with large fold-expressions in Clang. It'd be great if you could file a [bug report] (http://llvm.org/bugs) on that issue (or if not, give me some steps to reproduce it and I'll file it for you).
(Sorry, couldn't find another way to get in touch...)

Thanks, I filed clang bug 23919: https://llvm.org/bugs/show_bug.cgi?id=23919
Seems to be a problem for folds over around 1200 elements.


Update the-super-tiny-compiler.js

Made some modifications to make the newly-added text fit into existing paragraphs.

@thejameskyle updated.


Failing autentication after vaillant update

The vaillant APP VRC700 is gone, and I must had to move to myVaillant.
I rebuild my password, and that is working right with the myVaillant APP, but does not work on the HA multimatic integration.
The returned error is the next:
2024-03-06 23:37:28.578 ERROR (MainThread) [custom_components.multimatic.config_flow] Unable to authenticate: Cannot get token at https://smart.vaillant.com/mobile/api/v4/account/authentication/v1/token/new, status: 401, response: {"errorCode":"NOT_AUTHORIZED"}
More friends with this issue?

Multimatic component integration for HA not working anymore if you are migrated to myvaillant.
You have to use an other component.
Best regards

I just received the invitation to update to the myVAILLANT app, and came to ask if I should expect problems. Now I have my answer. @thomasgermain Any chance there will be a fix for this before myVAILLANT becomes obligatory on 1.4.2024?

Multimatic component integration for HA not working anymore if you are migrated to myvaillant. You have to use an other component.

What other component is that?

What other component is that? This one?

yes, i think so

Hello,
I made a communication here: https://community.home-assistant.io/t/vaillant-multimatic-integration/87240/562.
This integration will work until you migrate, after that you will have to switch to the new integration (it requires some maintenance, since the system is quite different from multimatic).
For now, ambisense it not yet integrated, but I'm busy with @signalkraft


Less noisy test

Motivation
This test currently fails every time someone adds a definition to payload.
Make it not.
This should make it easier for external folks to contribute
Test plan
See included automated tests.

Closing in favor of #1315 that did it better.


Questions about the API key

Hello,
I apologize for the interruption. I am a student majoring in Big Data, and our teacher has assigned us a task to read and implement the methods described in a research paper. Our group is particularly interested in the paper titled "Benchmark for Research Theme Classification of Scholarly Documents." However, we encountered some confusion with parts of the code after cloning your repository. Despite spending an entire day on it, we haven't been able to achieve the correct results. Specifically, we are puzzled about the api_key mentioned in the code.
We are also not very familiar with using GitHub and hope you can point out our mistakes.
We are unsure of your time zone, and we apologize if this message reaches you at an inconvenient time.

Hi @tide29,
Thank you for reaching out.
To use the CORE API mentioned in the code, you first need to register and obtain an API key. You can do this by visiting the following link: CORE API. Once registered, you'll receive an API key that you can place in the api_key.txt file.
Here are the steps you need to follow:

Go to the CORE API Registration page.
Sign up for an account and apply for an API key.
Once you receive your API key, create a file named api_key.txt in the ../data/ directory of your project.
Paste the API key into this file and save it.
After completing these steps, your code should be able to read the API key correctly and proceed without the FileNotFoundError.

If you have any further questions or run into any other issues, feel free to ask.
Best,
Wojciech

Hi，Sincerely thank you for your reply,
I will try your suggestion as soon as possible. Thank you so much


Wrong tag for 2.1.3

All releases/versions so far have been prefixed with v, but not 2.1.3.
I'm not sure whether this was intentional, but it might cause some annoyance for people using dependency management tools like dep as the version format is no longer consistent.
CC: @jung-kurt (you're the only one who can currently create tags)

Oops, my fault. Thanks for bringing that to my attention, @TwinProduction.


Request for DR-HTF009S

Thanks for writing and supporting this integration, kudos to you !
Model - DR-HTF009S
Number of speeds the fan supports (not including "off") - 9
Does the fan support oscillating? YES
What preset modes are supported? Normal, Natural, Sleep, Auto
Is temperature supported? YES
Thanks
Mark

Committed to main in #96


removed utils.mkdir with reset=True for most ipynb

In the tutorials, the working_dir was often created via utils.mkdir(...., reset=True). When people use this on folders with other data, the content of the folder can get removed. To not bring people to the idea of using this, we use now on almost all tutorials the utils.gettempdir(..., reset=True) option.  In some cases, utils.mkdir(...., reset=True) is still used, but then I added a warning in the code (as suggested by @fmaussion):

Beware! If you use reset=True in utils.mkdir, ALL DATA in this folder will be deleted! Use with caution!

Thanks to Kim Cholibois for reporting this issue!

:raised_hands: thanks!


Fix negation of 0 length Decimal

A Decimal value with _length 0 and _isNegative set to 1 is interpreted as a NaN. The 'negate()' function however, flipped the _isNegative flag without regard for the _length 0 case. This meant that -0 would become NaN. The fix checks for the _length 0 special case. In NSDecimalSubtract() the same check was performed. Since this now happens in negate(), it is removed from the NSDecimalSubtract() function.
This pull request fixes rdar://33311786

When I run
import Foundation
var e = Decimal(0)
print(e)
e.negate()
print(e)

in an Xcode playground I see
0
NaN

so it looks like we are already compatible with Darwin here?

Ok, I fixed the wrong error then.
In Xcode 9 beta 3 the infix operator - started behaving differently. For:
import Foundation
let e = Decimal(0)
print(e)
print(-e)
In Xcode 8.3.3 you get:
0
0
While in Xcode 9 beta 3 you get
0
NaN
So the error appears to be in the infix operator overload instead.
I would love to see if I can find the correct place to fix it.

Ok, now I have compared the file:
stdlib/public/core/Integers.swift.gyb in swift-4.0-branch of the swift repo
and
stdlib/public/core/IntegerArithmetic.swift.gyb in swift-3.0-branch
In swift 3 we had:
public prefix func - (x: T) -> T {
return 0 - x
}
While in swift 4 the SignedNumeric defines:
extension SignedNumeric {
@transparent
public static prefix func - ( operand: Self) -> Self {
var result = operand
result.negate()
return result
}
@_transparent
public mutating func negate() {
self = 0 - self
}
}
Since the Decimal type implements it's own 'negate' then I guess this is why we get the NaN instead of the 0 when using the minus prefix operator.
It is not 100% clear to me how this should be fixed - but it is probably in the swift core instead of in corelibs-foundation.
Would you happen to have some insight into how this could be fixed?

The difference in behaviour between Xcode 8 and 9 is interesting. It might be worth filing a Radar about that - what do you think @phausler?

I filed a radar before beginning to look into the issue: rdar://33311786 (http://www.openradar.me/radar?id=5031952226713600)
I must admit that I was getting a bit confused about what lies in Foundation and what is a swift overlay. As far as I can tell the 'negate' behavior is not Foundation, but part of stdlib/public/SDK/Foundation/Decimal.swift.
As such, I believe that 'negate' has been broken since the Decimal extensions were introduced. But if you used the prefix operator instead of calling negate directly, you would never see this since SignedNumber called the infix minus operator (on 0 - value) - thus hitting the NSDecimalSubtract function.
So the issue is that in Swift 3, 'a.negate(); return a' behaved differently than '-a' - and in Swift 4 they behave the same since '-a' just calls 'a.negate(); return a'.
So it does not seem possible to maintain backwards compatibility here (without beginning to redefine the behavior of the SignedNumeric protocol in Swift 4).
I would opt for fixing the logical error here. This would basically merge both this pull request and a similar one in the Swift repo version of stdlib/public/SDK/Foundation/Decimal.swift
As a funny side-effect to the existing issue, calling negate on NaN gives 0. It does not make a whole lot of sense. :-)

I've now made similar changes to the swift repo. Let me know if you think that I should create a pull request for the similar change. @ianpartridge @phausler

Yea this should be done in both places: thanks for taking this on

@swift-ci please test

@phausler my pleasure - happy to be able to contribute. :-)
Here's my similar pull request for the swift repo:
https://github.com/apple/swift/pull/10967


Handle local time zones

The current example for creating key credential from cer-file assumes that the code is running in the GMT time zones. I have added the code required to convert the local DateTime object to GMT and format it in the same way as $cer.GetExpirationDateString().

Docs Build status updates of commit b89afdc:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

azureadps-2.0/AzureAD/New-AzureADApplicationKeyCredential.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

This one is broken. See #430.


iOS 13: DKImageAssetExporter doesn't export properly

DKImageAssetExporter.exportImage makes a call to asset.fetchImageData and looks for let fileURL = info["PHImageFileURLKey"] as? NSURL.
This was working for us in iOS 12, with the info dictionary containing 8 keys:
Dictionary.Keys([AnyHashable(“PHImageFileURLKey”), AnyHashable(“PHImageResultIsPlaceholderKey”), AnyHashable(“PHImageResultIsDegradedKey”), AnyHashable(“PHImageResultDeliveredImageFormatKey”), AnyHashable(“PHImageResultRequestIDKey”), AnyHashable(“PHImageFileSandboxExtensionTokenKey”), AnyHashable(“PHImageResultIsInCloudKey”), AnyHashable(“PHImageResultWantedImageFormatKey”)])
However, in iOS 13 this gives: Dictionary.Keys([AnyHashable(“PHImageFileUTIKey”), AnyHashable(“PHImageFileDataKey”), AnyHashable(“PHImageResultIsDegradedKey”), AnyHashable(“PHImageResultRequestIDKey”), AnyHashable(“PHImageFileOrientationKey”)])
The outcome is all exported assets are given the same default name: asset.fileName = "Image.jpg"

Hello,
I am also facing this same issue, did you find any solution for this?

I saw this while using exportsWhenCompleted.   To get around this I just copied the files manually.

Fixed in develop. Thanks!


All icons with title

Easier to know which icon you are seeing.

Fixes #17

I'm into that.

Thanks [=

No worries dude :)
On 17 Oct 2015 16:19, "Jhonny Moreira"<EMAIL_ADDRESS>wrote:

Thanks [=
—
Reply to this email directly or view it on GitHub
https://github.com/connors/photon/pull/24#issuecomment-148923288.


Responsenet Implementation into SPRAS

The wrapper implementation for ResponseNet.
Note: This is actively working, there are many issues that need to be ironed out. This is mainly for easier access for other maintainers to see the code.

Last update from me RE: ResponseNet wrapping.
As it stands, there is still an error with running the docker container. Anna and I were able to run interactively both my Docker image and the ReedCompBio image, but when trying to run it through SPRAS, the following error appeared:

Also as it stands, the wrapping is not yet complete. I started the wrapping process and its likely finished, but I was unable to do any testing of the wrapper due to previous errors. Thus, the things that need to be done are as follows:

[ ] Finish and test the wrapper functions for SPRAS
[ ] Add ResponseNet as a full fledged algorithm for SPRAS
[ ] Write Pytests

After creating this comment, I'm going to turn this PR into a draft PR for whenever it may be revived. I am also adding Anna, Tony, Altaf, and Oliver as contributors.
Have a good year y'all o7


Replies much more like twitter rather than having to type the reply in the box above the annotations

related: #19


ConnectNetworkAsync results in error

#Output of dotnet --info:
.NET Command Line Tools (1.0.0-preview2-1-003177)

Product Information:
 Version:            1.0.0-preview2-1-003177
 Commit SHA-1 hash:  a2df9c2576

Runtime Environment:
 OS Name:     Mac OS X
 OS Version:  10.11
 OS Platform: Darwin
 RID:         osx.10.11-x64

What version of Docker.DotNet?:
                "Docker.DotNet": "2.124.3",

Steps to reproduce the issue:
           var network = this.dockerClient.Networks.ListNetworksAsync().Result;
            var d = network.First(x => x.Name == "integrationtests");
            this.dockerClient.Networks.ConnectNetworkAsync(d.Name, new NetworkConnectParameters() { Container = "am2" }).Wait();

What actually happened?:
An exception back with
"Docker API responded with status code=NotFound, response={\"message\":\"network integrationtests/connect not found\"}\n"

What did you expect to happen?:
For it to connect
Additional information:
When running curl POST --data "{\"container\":\"am2\"}" -H "Content-Type:application/json" http://<IP_ADDRESS>:2376/v1.24/networks/integrationtests/connect -v it worked so not sure why it's not working via this API

I think the API wrapper is expecting you to provide "d.ID" (network id) instead of the name.
try changing:
this.dockerClient.Networks.ConnectNetworkAsync(d.Name, new NetworkConnectParameters() { Container = "am2" }).Wait();
to:
this.dockerClient.Networks.ConnectNetworkAsync(d.ID, new NetworkConnectParameters() { Container = "am2" }).Wait();

Same issue
On Thu, 9 Mar 2017 at 18:15, robborden<EMAIL_ADDRESS>wrote:

I think the API wrapper is expecting you to provide "d.ID" (network id)
instead of the name.
try changing:
this.dockerClient.Networks.ConnectNetworkAsync(d.Name, new
NetworkConnectParameters() { Container = "am2" }).Wait();
to:
this.dockerClient.Networks.ConnectNetworkAsync(d.ID, new
NetworkConnectParameters() { Container = "am2" }).Wait();
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/Docker.DotNet/issues/184#issuecomment-285433728,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGapuNdjkY6ZkWBKnSjCv6a11IAtFfXks5rkEGmgaJpZM4MYFr-
.


not working AE CC 2018

It seems not working in AE CC 2018
There is no result file in folders: \result, \temprJDvktdUG\
Error message: ENOENT: no such file or directory, stat 'C:\Users\devua\nexrender-boilerplate\temp\rJDvktdUG\result.avi'
{ Error: ENOENT: no such file or directory, stat 'C:\Users\devua\nexrender-boilerplate\temp\rJDvktdUG\result.avi'
  errno: -4058,
  code: 'ENOENT',
  syscall: 'stat',
  path: 'C:\\Users\\devua\\nexrender-boilerplate\\temp\\rJDvktdUG\\result.avi' }

this is related to ae 2018 not having h264 support
just make sure you provide into your project config
outputExt: 'avi'

The same result:
C:\Users\devua\nexrender-boilerplate>node start.js
Started local static server at port: 23234
Project {
uid: 'rJ4YqJcIz',
state: 'queued',
template: 'project.aepx',
composition: 'main',
type: 'default',
assets:
[ { type: 'project',
name: 'project.aepx',
src: 'http://localhost:23234/assets/nm05ae12-q.aepx' },
{ type: 'image',
name: 'background.jpg',
src: 'http://localhost:23234/assets/2016-aug-deep.jpg',
filters: [Array] },
{ type: 'image',
name: 'nm.png',
src: 'http://localhost:23234/assets/nm.png' },
{ type: 'audio',
name: 'audio.mp3',
src: 'http://localhost:23234/assets/deep_60s.mp3' },
{ type: 'script',
name: 'data.js',
src: 'http://localhost:23234/assets/2016-aug-deep.js' } ],
actions: [],
settings:
{ outputModule: 'h264',
startFrame: 0,
endFrame: 3600,
outputExt: 'avi' },
errorMessage: null,
callbacks: {},
ticker: null,
api: null,
error: null }
[rJ4YqJcIz] setting up project...
[rJ4YqJcIz] downloading assets...
[rJ4YqJcIz] renaming assets...
[rJ4YqJcIz] filtering image assets...
[rJ4YqJcIz] patching project...
[rJ4YqJcIz] rendering project...
[rJ4YqJcIz] verifying project...
[rJ4YqJcIz] project failed
Error message: ENOENT: no such file or directory, stat 'C:\Users\devua\nexrender-boilerplate\temp\rJ4YqJcIz\result.avi'
{ Error: ENOENT: no such file or directory, stat 'C:\Users\devua\nexrender-boilerplate\temp\rJ4YqJcIz\result.avi'
errno: -4058,
code: 'ENOENT',
syscall: 'stat',
path: 'C:\Users\devua\nexrender-boilerplate\temp\rJ4YqJcIz\result.avi' }

did you check your temp folder, was there any generated file ?

Yes, there is a new folder inside temp each rendering with all assets but witout result.avi
And the result path is enpty (except readme.txt)

I have installed QuickTime Alternative and use h264 codec

seems like aerender doesnt want to generate the file, you need to check the after effects log itself to see the reason

Unfortunately the same for avi.

are you sure it spawns the rendering process right ?
there is supposed to be output information created by aerender
where is it ?

Hii
I am also getting same error on AE 2018?
Error message: ENOENT: no such file or directory, stat 'D:\nodejs\first\nexrender-boilerplate\temp_zrTTHoSI\result.avi'
{ [Error: ENOENT: no such file or directory, stat 'D:\nodejs\first\nexrender-boilerplate\temp_zrTTHoSI\result.avi']
errno: -4058,
code: 'ENOENT',
syscall: 'stat',
path:
'D:\nodejs\first\nexrender-boilerplate\temp\_zrTTHoSI\result.avi' }
please help me to solve this issue.
Thanks.

Change outputExt to avi and remove outputModule works form me, but....the result file has 9gb :(
I need to render in mp4.

@rafaelboschini i suggest you to checkout the latest version of the https://github.com/inlife/nexrender
it has built-in ffmpeg encoder, that allows you to convert your temp avi/mov result into mp4, or any other format with much less used size


Feature: RSS feed

Generate RSS every build.
I want to make sure it works with github pages, but the xml-sitemaps method doesn't work when the website is generated with npm run export, and it looks like there really isn't a way to change the default content-type in pages/.
One possible method is generate the site map on build, inside getStaticProps in index.js, or run another script to do it manually. Personally, I prefer the first one.

Added in ff0f3cfbd3d41f4ec298b405b668cf2eb17249e1


Big integer literals are not available in the configured target environment

Problem

Installation/Config error
Fails to compile

Expected Output
Compiles and allows access to Tailwind styles and Smelte components.

Environment
Operating System: Microsoft Windows 11 Pro 10.0.22000
Node.js: v16.13.1
PNPM: 6.31.0
Svelte: 3.44.0
Svelte Kit: 1.0.0-next.281
Smelte: 1.1.8

Same, it is maybe because not using rollup in svelte Kit

This issue has already been resolved in a svelte-kit repo
https://github.com/sveltejs/kit/issues/859

I'm actually running a brand new fork of this repo, and the issue is still happening. Overriding the build target per the comments in that issue has not fixed the errors either here. I've even tried updating sveltekit to the latest next.315, no change.
It seems like multiple people are missing the fix here, so could someone please explain the solution in more detail.

Would it be too rude to bump this?  bump.

@adrian13val Seems like configuring Vite's target build indeed solves the issue when building. However, it still reproduces when running the dev server, this configuration seems to have no effect there

Adding this into my vite config helped solve the problem
 optimizeDeps:{     esbuildOptions:{       target: 'es2020'     }

Adding this into my vite config helped solve the problem  optimizeDeps:{ esbuildOptions:{ target: 'es2020' }

adding it gives me this new error
Internal server error: Failed to resolve import "svelte-waypoint" from "node_modules\smelte\src\components\Image\Image.svelte". Does the file exist?
  Plugin: vite:import-analysis
  File: D:/languages/web/projects/svelte-todo-android/node_modules/smelte/src/components/Image/Image.svelte
  29 |  } from "svelte/internal";
  30 |
  31 |  import Waypoint from "svelte-waypoint";
     |                        ^
  32 |  import { fade } from "svelte/transition";
  33 |  const file = "D:/languages/web/projects/svelte-todo-android/node_modules/smelte/src/components/Image/Image.svelte";
      at formatError (file:///D:/languages/web/projects/svelte-todo-android/node_modules/vite/dist/node/chunks/dep-71eb12cb.js:35035:46)
      at TransformContext.error (file:///D:/languages/web/projects/svelte-todo-android/node_modules/vite/dist/node/chunks/dep-71eb12cb.js:35031:19)
      at normalizeUrl (file:///D:/languages/web/projects/svelte-todo-android/node_modules/vite/dist/node/chunks/dep-71eb12cb.js:40181:33)
      at async TransformContext.transform (file:///D:/languages/web/projects/svelte-todo-android/node_modules/vite/dist/node/chunks/dep-71eb12cb.js:40315:47)
      at async Object.transform (file:///D:/languages/web/projects/svelte-todo-android/node_modules/vite/dist/node/chunks/dep-71eb12cb.js:35284:30)
      at async loadAndTransform (file:///D:/languages/web/projects/svelte-todo-android/node_modules/vite/dist/node/chunks/dep-71eb12cb.js:39812:29)


https doesn't work for https://docs.mesg.tech

The right url this https://docs.mesg.com

great, could you update the url here as com please? https://github.com/mesg-foundation/mesg-js

good point, I also just in case added the https on the .tech


Error:(75, 0) Could not get unknown property 'GROUP' for object of type org.gradle.api.internal.plugins.DefaultExtraPropertiesExtension.

Do you want to request a feature or report a bug?
What is the current behavior?
Error:(75, 0) Could not get unknown property 'GROUP' for object of type org.gradle.api.internal.plugins.DefaultExtraPropertiesExtension.
Open File
If the current behavior is a bug, please provide the steps to reproduce.

Any logs, error output, bugreport etc?

What is the expected behavior?
Any other comments?
ALSO POM VALUES ARE MISSING
<--
developerId = POM_DEVELOPER_ID
developerName = POM_DEVELOPER_NAME
developerEmail = POM_DEVELOPER_EMAILID
licenseName = POM_LICENCE_NAME
licenseUrl = POM_LICENCE_URL
allLicenses = [POM_ALL_LICENCES]
-->
sims like maven dependency missing
how to resolve
What versions of software are you using?

Device Information:

Android Version:

Configuration Information:

Misc:

@MantraUser Could you explain to me what are you trying to do, when you get this error. The reason those values are not checked in is because they are used to publish the library to JCenter. If you compile the app and library should work without any issue. The values cannot be shared because they define the ownership of the library to me in JCenter, otherwise anyone would be able to publish it to the namespace and break the build for everyone.

i was trying to build cloned project i want to use it as seperate module but now i know that i can improt only library module, Thanks

Ok. I guess that solves your issue. Closing this issue for now.


[C++][FS][Azure] Generic filesystem tests for DeleteDir/DeleteDirContents/GetFileInfoSelector failed with Azure

Describe the enhancement requested
[ RUN      ] TestAzureHierarchicalNSGeneric.DeleteDir
/home/kou/work/cpp/arrow.kou/cpp/src/arrow/filesystem/test_util.cc:277: Failure
Failed
Expected 'fs->DeleteDir("AB/def")' to fail with IOError, but got OK
[  FAILED  ] TestAzureHierarchicalNSGeneric.DeleteDir (1434 ms)
[ RUN      ] TestAzureHierarchicalNSGeneric.DeleteDirContents
/home/kou/work/cpp/arrow.kou/cpp/src/arrow/filesystem/test_util.cc:306: Failure
Failed
Expected 'fs->DeleteDirContents("abc")' to fail with IOError, but got OK
[  FAILED  ] TestAzureHierarchicalNSGeneric.DeleteDirContents (1535 ms)

[ RUN      ] TestAzureHierarchicalNSGeneric.GetFileInfoSelector
/home/kou/work/cpp/arrow.kou/cpp/src/arrow/filesystem/test_util.cc:149: Failure
Expected equality of these values:
  info.mtime()
    Which is: 8-byte object <00-8C 22-1E 29-D7 C0-17>
  mtime
    Which is: 8-byte object <FF-FF FF-FF FF-FF FF-FF>
For path 'AB'
/home/kou/work/cpp/arrow.kou/cpp/src/arrow/filesystem/test_util.cc:753: Failure
Failed
Expected 'fs->GetFileInfo(s)' to fail with IOError, but got OK
[  FAILED  ] TestAzureHierarchicalNSGeneric.GetFileInfoSelector (860 ms)

Component(s)
C++

I've split CopyFile() to #41095.

Issue resolved by pull request 41068
https://github.com/apache/arrow/pull/41068


Update database-mail-common-errors.md

Hi SQL Server Docs Team,
I've added the command to set 'show advanced options' back to false and also fixed the code block that wasn't properly closed.
Best regards,
Vlad Drumea

Awesome, thanks @VladDBA ! :) #sign-off


Add relation and expose metrics from knative-operator

Context
The knative-operator deployment already exposes metrics here, however charm is not using this and do not provide metrics-endpoint and grafana-dashboard endpoints.
We need to add relation using prometheus_scrape and grafana_dashboard interfaces.
What needs to get done

Expose port for metrics as ServicePort
Implement metrics-endpoint endpoint
[Optional] Find and add some alert rules for metrics
Find or create dashboard
Implement grafana-dashboard endpoint

Definition of Done

knative-operator has metrics-endpoint and grafana-dashboard endpoints
Integration with cos is tested
knative-operator provides grafana dashboards and alert rules

Duplicated issue, #184


Feature request to open multiple file in quick open file

i suggest to have open multiple file in quick open file.

After search file and then can select multiple file to open at same time

Open single file : open it by type search, then press enter to open
Open multiple file : after type search in quick open, hold Ctrl key and press spacebar to select/unselect then press enter to open

/findDuplicates

@bpasero Cool. thank you


Ordered objects?

Is there any chance we could have objects preserve insertion order in goja? The ES spec no longer mentions if objects should be ordered or unordered, but Chrome, Firefox and Node all preserve insertion order.
Test script:
let obj = {"a": 1, "b": 2, "c": 3}
for (key in obj) { console.log(key) }

Hm... I thought it was already preserving the order. It is indeed not part of ES5.1, but since it's common behaviour goja should conform. I'll take a look a bit later.

I tried running this and I'm getting a, b, c. Not sure what is the problem.

Ah, my bad, I was looking at Go Object instances and made a poorly verified assumption about the JS-side behavior. There's no Keys() function, and the only way to access the list of keys is to export it into an unordered map[string]interface{}.

@uppfinnarn The ordering requirements (or lack thereof) of a for-in statement hasn't changed. Before ECMAScript 6, it was implementation defined, and it still is. Code shouldn't rely on any sort of ordering that follows the Enumerate semantics.

@uppfinnarn There is now.

👍
@Perelandric Generally speaking, I agree with you, but in this case I'm working with an application-specific DSL, not portable code.


Improvement for k8s.io/docs/tasks/administer-cluster/migrating-from-dockershim/change-runtime-containerd/

Migrating to containerd requires settings on /etc/systcl.d/99-kubernetes-cri.conf
e.g.
cat <<EOF | sudo tee /etc/sysctl.d/99-kubernetes-cri.conf
net.bridge.bridge-nf-call-iptables  = 1
net.ipv4.ip_forward                 = 1
net.bridge.bridge-nf-call-ip6tables = 1
EOF

The migration worked for me until I rebooted due to kernel upgrade. Apparently there were iptables rules left by docker install that allow containerd to work. After the reboot the docker iptables were gone and my nodes could not run e.g. kubernetes dashboard.

/language en
A few questions @scudella

Which network plugin (if any) were you using with Docker Engine?
Which network plugin are you using now?
What version of Kubernetes are you running?

Those answers will help us work out what advice to give to readers.

I was using (and still using) Weave cni plugin.
I believe I was running 1.23.4, then I did the dockershim migration to containerd and upgraded to 1.24.3. A couple of days ago I upgraded to 1.24.4 and rebooted. Then I had the problems with the work nodes.
I did install the cluster with instructions on https://github.com/jpetazzo/ampernetacle.git, commit 12616e3...
These iptables rules were still around before rebooting the nodes. After rebooting they were gone. I guess they might be related to the issue.

You can google how to make 'sysctl' effective immediately.
/kind support
/close


Insecure options ondisk

Disable checking the treestore when using --insecure-options=ondisk
which is implemented in this change.
This reduces the start-up time of big images dramatically.
For example, with docker://jenkins.
docker://jenkins
real	0m7.200s
user	0m6.740s
sys	0m0.550s
docker://jenkins --insecure-skip-verify
real	0m0.384s
user	0m0.100s
sys	0m0.030s

LFAD.


Clarify that Callable will not be encoded with var_to_bytes

Only added to @GlobalScope, can add to FileAccess as well if desired, but it links there so didn't want to repeat too much

Fixes: #79802

Thank you for fixing!

I wonder if this should be in the Callable doc instead.

I'd say here or both, as you won't necessarily think to look at Callable when doing IO

Also the matching detail for var_to_str is here from a previous PR

Thanks!

Thank you!

Cherry-picked for 4.2.2.


Add jupyter-server and notebook to the build environment

This should help fix the missing contents in the deployed site: https://derthorsten.github.io/xeus-javascript/lab/index.html
As noticed in https://github.com/DerThorsten/xeus-javascript/actions/runs/7583515865/job/20655314743

The notebook dependency should bring the following UI items to switch between lab and notebook:

@DerThorsten looks like the workflow may have some issues for the deploy step: https://github.com/DerThorsten/xeus-javascript/blob/main/.github/workflows/main.yml
Maybe it's because my fork does not have the github-pages environment.

But this can be addressed separately.
Looking good when checking the built artifact:

But this can be addressed separately.

Opened https://github.com/DerThorsten/xeus-javascript/issues/2.


[FEATURE REQUEST] Early Hints support (103 HTTP code)

Currently, roadrunner allows sending 1 response at the time, this means we can't send early hint ( or any other 1xx ) responses.
Describe the solution you'd like
A solution to be able to send multiple responses at the time to the roadrunner server, this could be done by changing the structure of the payload to be sent ( and ofc ensuring the HTTP server itself is able to handle 1xx responses )
Describe alternatives you've considered
N/A
Additional context
ref:

https://github.com/golang/go/pull/42597
https://github.com/php/php-src/pull/7025
https://github.com/lucas-clemente/quic-go/pull/3047

Hey @azjezz , thanks for the FR. Likely it will be supported for the http3 (quick protocol) RR plugin rather than the actual HTTP plugin. At the moment we can't write to the ResponseWriter multiply times. According to the chromium discussion and Mozilla, Early Hints are not supported by the ecosystem.

while early hint is currently no supported by the ecosystem ( servers mostly ), it is supported by browsers, and unlike HTTP2/push, there's no plans to remove it.
from the OP: https://groups.google.com/a/chromium.org/g/blink-dev/c/K3rYLvmQUBY/m/vOWBKZGoAQAJ

The 103 Early Hints status code (https://tools.ietf.org/html/rfc8297) is expected to provide better performance under certain circumstances by allowing information about resources that the client should request to be sent as soon as available and then making the connection available for carrying data on other streams until the final response is sent.  There is active effort to measure the potential latency gain of 103 Early Hints (compared to not using it, without using server push in either case), with the understanding that resources will be allocated to implementing it in Chromium in case data look promising.  See https://chromium.googlesource.com/chromium/src/+/master/docs/early-hints.md for more details.

Therefor, i think HTTP2/push feature of RR should be deprecated once 1xx support is accomplished.

it is supported by browsers

I guess only Google Chrome supports the Early Hints (Safari??), because according to Mozilla bugtracker, at least Firefox does not support it. But, anyway, thanks for the FR, we will track support for the Go's stdlib and when multiply writes will be supported, there are no problems to add 103 HTTP code support.


[Bug Report] Right aligned submenu opens second level submenu off screen to the right

Element UI version
2.12.0
OS/Browsers version
MacOS 10.14.6 / 76.0.3809.132
Vue version
2.5.13
Reproduction Link
https://jsfiddle.net/plindelauf/9gts38qh/10/
Steps to reproduce

Open the submenu by hovering over the user icon
Hover over the option "English" to open the submenu

What is Expected?
I expect to see the second level submenu (under English) to open to the left.
What is actually happening?
You see the submenu arrow correctly pointing left, yet the submenu opens to the right.

<el-submenu index="1-1" popper-append-to-body="true">

@1207934561 Yes, then it basically works, but it messes up my styling since, it is out of its menu context :(


Not sure where to get framework from to build solution

Not sure where to get framework from to build solution. The hyperlink is gone. I know where to get vmread obviously.

After a bit more of inspection I noticed some of the CPP files were moved into https://github.com/Heep042/m0dular


Some recipes missing producers in K2+SE

Holmium solenoid and holmium cable are two that I can remember off the top of my head

Reported by Sebbo in Discord

There may also be an issue with the iron plates recipe, in calc it is 16sec, Bat in Discord reports it should be 48sec.

Closed in #843


sync ops for queue

I was looking to see if I could replace the Mutex<VecDeque<T>> from the deadpool crate, but there's an interesting requirement here - deadpool has a resize method that can resize the queue.
Not to be deterred, I am hoping to use a RwLock<ArrayQueue<T>>. 99% of ops will call slots.read().pop(), but for the resize function, I was intending to use slots.write() to get sole ownership, then I could mem::swap in a new queue. This would be fine, but I thought it could be more efficient.
This PR introduces an efficient implementation of some of the sync (&mut self) operations for inserting into the queue, as well as that resize method.
pop_sync,push_sync,force_push_sync are much like their shared counterparts, except they don't need to care about atomic load orderings. (I'm open to alternative namings)
resize is a little more complicated:

We 'reset' the queue. This shifts all live slots to the front of the slice
We take out the buffer from the queue as a vec - leaving a dangling empty box in it's place
We either reserve and fill, or truncate and shrink our vec
We turn our vec back into a boxed slice, and update our queue to match

Developing for older MSRVs on an M1 mac is hard 🙃 the minimum rust I can install is 1.49

Developing for older MSRVs on an M1 mac is hard 🙃 the minimum rust I can install is 1.49

FYI, you can use rustup toolchain add 1.38-x86_64-apple-darwin and cargo +1.38-x86_64-apple-darwin build.

Developing for older MSRVs on an M1 mac is hard 🙃 the minimum rust I can install is 1.49

FYI, you can use rustup toolchain add 1.38-x86_64-apple-darwin and cargo +1.38-x86_64-apple-darwin build.

Thanks, it seems to build locally now 😅

Ok - I'm in no rush for this to get reviewed. Having swapped out the deadpool queue for this impl, I get noticeable regressions for some reason :(

Ok, marking this as draft for now.


Add docs

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


Add a new project root-signing-staging

Summary
Add new repository root-signing-staging, see #345 for details.
Fixes #345 (although further tweaks may be required: we'll see how the bot permissions match what tuf-on-ci expects, and what is needed to configure Pages publishing from GH actions).

Gentle ping on this one. Like I said I'm not 100% confident this configuration is exactly correct but it's as close as I can get it: I believe we need to try and see how it goes. If you have questions, let me know.
cc @cpanato who seems to do a lot around here or I guess the  tsc folks @bobcallaway @trevrosen @lukehinds @priyawadhwa @SantiagoTorres ?

Yeah this looks fine, let's give it a shot and iterate as we need to.

Can a TSC member merge this?


Take time as an Int32.t in seconds in Dhcp_server.input_pkt.

float made sense in the past since Unix.time and mirage's clock gave it in floats.
Now it makes no sense anymore, we should use Int32.t which would also avoid a bunch of conversions.

is there any absolute time in DHCP on the wire (or only relative times, i.e. the lease period)?  and time is expressed in seconds as a 4 byte unsigned integer I assume?
I'd somehow expect the tick/handler to accept a Ptime.t (int * int64) -- this is what PCLOCK.now_d_ps returns, and based on that decide which leases to expire/renew/...

The times are always relative, the only drawback I see is that with a monotonic clock it gets harder to reason about when a lease expires (we need to know when "now" is.).
I couldn't figure out what Ptime.t (int * int64)  is
what is the int and what is the int64 ?
The second thing is, I would not be able to use Duration.to_sec in it (in mirage skeleton), since on a 32bit system I'd have only 31 bits to express time.

ptime: look at the source, https://github.com/dbuenzli/ptime/blob/master/src/ptime.ml#L45-L68
I suspect there are two different time things we're talking about here: the lease time to be written on the wire, and the server which needs to find out which leases have expired now.  For the latter, I'd use an explicit time (either periodically as tick, or as part of every input) -- see https://hannes.nqsb.io/Posts/ARP for further explanation what I mean.  ATM I'd suspect that no explicit time function, but rather requiring a Ptime.t in each input call would be more efficient (I've plans to rework ARP to not have an explicit tick funciton)..

Yes, time is always expressed as int32 on dhcp options.
There are some odd DHCP options that use absolute time, they're obsolete and not handled by the library. We still interpret them but the only the user of the library may decide to do something with it.
What you suggest is exactly like things were, if you always pass an absolute timer or a relative timer, the library will work correctly, as long as the absolute timer never goes back (which could be the case before if someone changed the date).
Actually by using monotonic we respect the leases correctly in case the date changes, this was my orinal idea in the past, but I had no access to monotonic clocks in mirage.

Argh, now I realize I posted this issue before deciding to use a monotonic time as input.
We can't use an int32 as asbolute since it is too short, but a monotonic int32 we can.

Have a look at: d689ac99ccda6e961b4554d546ebebf12c6e868c
I didn't commit to master.

looks good to me


Doesn't seem to recognize non proxy routes (express)

Expected behavior
When setting up an express router, routes not in proxy context are not recognized.  IE if filter function returns false, non proxy routes in sub application should be found.
Actual behavior
404 for routes in sub application
Setup

http-proxy-middleware: 0.17.0
server: express
other relevant modules

proxy middleware configuration
var filter = function (pathname, req) {
    return pathname.match(new RegExp('^/api'));
};
var apiProxy = proxy(filter, {target: 'http://www.example.org:8000'});

server mounting
var sub = new express.Router();
sub.use(proxy);

// main app, mount the sub application
var app = express();
app.use('/sub', sub);

other route in sub application
sub.get('/someroute',
   function(req, res, next) {
      // won't find route
   }
);

In your filter function you are using a string instead of regex in the match function pathname.match('^/api').
Think it should be: pathname.match(/^\/api/) or pathname.match(new RegExp('^/api'))
This piece of code is also weird:
var proxy = proxy(filter, {});

You are overriding the original proxy function... use a different variable namevar proxyExample = proxy(filter, {});
proxy(filter, {}); is missing the target value: proxy(filter, {target: 'http://example.org'});`

@chimurai you are correct, I did not copy my example and made a few mistakes when typing it in.  Still having problems, if the filter function returns false, non proxy routes are not hit.
IE, in my example the sub app has a context of sub so if I hit 'http://myserver.com/sub/api', the proxy filter will return true and the request will be proxied.
However if I hit 'http://myserver.com/sub/someroute', the filter function returns false as it should, but the request does not go through to the subroute endpoint.

@newmanw: Could be provide a minimal/small sample app; showing the problem you described? This will help me debug this issue.

@chimurai absolutely, working on it now.

@newmanw Thanks for providing the example.

Hi @newmanw,
Think I've fixed the issue. Can you verify it?
Still need to write some tests for this use-case

Works as I would expect.  Awesome turn around time, thanks so much!

Just pushed v0.17.1 with the fix.
Thanks for reporting the issue and helping out with debugging. Greatly appreciated!


[FEATURE] Sparse Models Pretraining Code & Data

Is your feature request related to a problem?
I could not find any information on the sparse neural search models hosted on HuggingFace. What's their archictecture? Are they multilingual? And most importantly how were they pre-trained? We would like to have our own models pretrained on our own data with the architectures that best suit our needs.
What solution would you like?
I would like to have access to the pretraining code and data.

@zhichao-aws take a look?

@dhrubo-os if you trained the models, can you publish the training code and data? thanks!

Hi @contrebande-labs , the paper for the sparse model is public now, https://arxiv.org/abs/2411.04403
The training code and data is still under the review process

@dhrubo-os if you trained the models, can you publish the training code and data? thanks!

Hi @contrebande-labs , we have public the code of fine-tuning the model(repo link). It can also be used to train a sparse model from scratch. You can reproduce the results if following the process of generating training data described in the paper.
We also aim to release the training data generated by us, but not sure whether this comply with the licenses of all used datasets and it's still under review.

Hi @zhichao-aws ! Thanks so much. We are evaluating and benchmarking many sparse and late interaction models now on our own data and we will look into it in the next couple of days. Please leave this issue opened until the data is published or there are new models trained on open data.


option 'flush: false' does not work

$('body').terminal(function(command, term){
    term.echo('some text', {raw: true, flush: false});
});

It always show the text, I think 'flush' not work.
note: I have never call the 'flush()' method.

I can't reproduce, which version of jQuery Terminal you're using?

If you run this code twice it will echo both texts because terminal is echo command and it need to call flush, and flush is flushing previous texts.
If you want to have flush that don't echo anything you can use echCommand option set to false:
var term = $('body').terminal(function(command) {
    if (command.match(/flush/)) {
        this.flush();
    } else {
        this.echo(this.get_prompt() + command, {flush: false});
        this.echo('some text', {
            raw: true,
            flush: false
        });
    }
}, {
    onBlur: function() {
        return false;
    },
    echoCommand: false
});

Here is demo

Thanks for your demo


A Hierarchical Neural Autoencoder for Paragraphs and Documents

reference: https://github.com/BUPT/awesome-chatbot/issues/88
A Hierarchical Neural Autoencoder for Paragraphs and Documents
poster
no new friends

A Hierarchical Neural Autoencoder for Paragraphs and Documents


Build & publish dspace/dspace-angular imgs with -dist suffix

References

The direct motivation is similar to: DSpace/DSpace#8679

Description
Adds a Dockerfile for building a dspace-angular dist image. This can be used to deploy the default ui using a relatively small (currently ~300mb) Docker image.
Instructions for Reviewers
# directly build the dist image
docker build -f Dockerfile.dist -t dspace/dspace-angular:dspace-7_x-dist .

# equivalent thing using docker compose (should be fast due to cache)
docker compose -f docker/docker-compose-dist.yml build

# run it with the demo backend
docker compose -f docker/docker-compose-dist.yml up -d

# view the logs
docker logs -f dspace-angular

Changes are exclusively Docker related. No other project files are impacted.
Check that things work as expected at: http://localhost:4000/ -- should be running with the Demo site backend
You may need to use docker-compose rather than docker compose depending on how compose is installed.
Checklist

[x] My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
[x] If my PR includes new features or configurations, I've provided basic technical documentation in the PR itself.

So far haven't been able to reproduce the build error, but that's using Mac & Ubuntu. I'll see if I can use a Windows 11 PC to find out what happens with Docker Desktop there. I'm super unfamiliar with Windows. @tdonohue  is that running the docker commands from the Windows terminal / powershell? If it's potentially memory related you can try bumping the Docker Desktop memory allocation? Although that wouldn't obviously explain the difference between docker build and docker compose build ...

@mark-cooper : I did more detailed testing on the build problems yesterday/today.
I've found that the problems do appear to be memory-related.  I had 6GB of memory allocated to Docker (including the Docker Engine itself).  It appears this build occasionally will bypass that 6GB limit, which causes it to fail during the yarn build:prod step.  It doesn't appear to have anything to do with docker-compose build vs docker build... with further testing I found both would fail & succeed almost randomly.  (For some reason docker build seems to succeed slightly more frequently, but it could just be based on how the Docker Engine runs each command)
That said, I've found a few fixes for this scenario:

First, if I stop all running containers prior to running the build, it seems to succeed more frequently at the 6GB memory level.
Second, I simply bumped up the memory to 8GB.  Even with a few running containers, the build succeeds (and even runs a bit faster, which shows me the 6GB limit was quite limiting).   (The 6GB limit was rather arbitrary anyways... I think it was set when I was looking at minimum requirements for running DSpace 7 in Docker)

So, overall, this build is working.   The memory requirements are no fault of this PR...so it's good as-is.   I'll do a bit more testing today of the PR itself (now that the build is working), and provide final feedback on this PR.


Promo component

What is this PR trying to achieve?

Makes the promo component more generic for use in the various explore page blocks.
Adds some styles for the different promo variants.

What does it look like?

For interface components

[X] Browser testing - Have you checked the component in our supported browsers
[X] No javascript - Have you checked the component with javascript disabled
[ ] A11y testing - Have you run pa11y against the component and fixed/verified all errors, warnings and notices?

Can we please please define what we mean by Promo?
It sounds like an ad?


z3 fail -> build fail

[ ] Ensure that if a snippet cannot be processed during build, the entire github action fails as well (and no deployment is generated).
[ ] Ensure that logging is good enough to trace which snippet needs to be investigated. Try to generate an formatted error message in the output so that the github action automatically highlights where the problem is

Snippet cannot be processed => something with syntax error?
eval_smtlib2_string guarantees to return a string, meaning the error messages will be part of stdout if an error occurs. I think we want the syntax errors for debugging/changing the snippets?

All errors are now rendered in the front-end, so examining the errors by hand on the website is feasible

I guess the expectation is that I fix the errors unless it is obvious.
There are other errors that don't require me in the critical loop:

I wonder what happend to the "Arithmetic" section. It looks incomplete. It has "Division" but no other subsections.
I ended up fixing various low hanging issues. For example, _ should be escaped in markdown mode.
So overall a lot of quality control left at this point, not considering the new material on Sequences I have been adding today.

Incomplete "Arithmetic" section: looks like you are missing .md suffixes for some files

meaning the error messages will be part of stdout if an error occurs

Note that you can call Z3.get_error_code right after calling Z3.eval_smtlib2_string to determine if there was an error without needing to parse the output, as in console.log('had error?', Z3.get_error_code(ctx) !== Z3_error_code.Z3_OK). You'll need to import Z3_error_code in the same place you import init.
There's also Z3.get_error_msg but unfortunately it will include the rest of the output from eval_smtlib2_string. I haven't checked if this is a bug in the wasm frontend or if that's just what Z3 itself does.

in smtlib2 mode (where it interprets a string) the errors are printed to the output string. There can be multiple errors.
This is what is relevant to the SMTLIB2 interpreter mode.
Those errors are not accessible from the error code or message.

close?


bower install should not use timestamps from the archive

bower install bootstrap
Create a Makefile that runs lessc to compile bootstrap.css from bower_components/less/bootstrap.less
Run make
Install a different bootstrap version with bower install bootstrap\#3.0.0
Run make again

What should happen: make notices that bootstrap.less has a new mtime and rebuilds bootstrap.css
What actually happens: nothing.
Why?  Because the timestamps of the files in bower_components/bootstrap/less/*.less are from last December, because unpacking the .tar.gz restored the mtimes.  It shouldn't do that, for the same reason 'git checkout' doesn't restore the mtime of checked out files.

Bower is now deprecated we encourage to use Yarn instead. You can migrate with bower-away


Macbook Pro 2016 Touchbar Support

Love this app. It is has kept me using GPM over spotify, Google should really be supporting it. One great feature would be support for the new MBP touchbar.

Will leave this open for now but unless someone can clearly define what "supporting the touchbar" actually means I will be closing this out.
I.e. I want a clear spec for what kind of interactions you expect to have with the touchbar, what buttons, what sliders, what should appear when?  Without this information I do not personally see any benefit from touch bar integration.  Please note I do have a Touch Bar MBP 2016, just don't see the benefits in this particular app 👍
Also note this is separate from the system wide MPRemoteCommandCenter integration in this issue https://github.com/MarshallOfSound/Google-Play-Music-Desktop-Player-UNOFFICIAL-/issues/1965#issuecomment-269101328

Actually, it seems the issue you linked is exactly what I was referring to. The screenshot you posted is precisely what I was thinking. If you look at the spotify app they implement this nicely. Being able to play/pause and skip tracks from any screen with the touchbar. Looks like what you posted but with skip/prev track buttons as well. Feel free to close this issue if you think it is redundant.

The most action my touchbar gets is hot changing iterm colours. I would love to see the following functionality on my touchbar - regardless of application I am in (unsure on feasibility)

Seek through track playing
Thumb up current playing track
Swap playlists
Some showing of tracks in playlist

Playing mode, has track seek option using most of the touch bar - traditional media keys on the right of bar - Including a thumbs up button

Playlist button (maybe option on the right side) drops it into playlist "now playing" mode. Uses the the bar to display playlist options, swipe through your playlists to change quickly.

Visualisation - total nice to have - but since its not doing anything pretty lights on the keyboard to music would be fantastic

Is possible using the native controls I hacked into working in the linked issue above

Is possible but only when the application is in focus as that is how the touch bar works, (1) is an exception to the rule because their are specific global touch bar API's

Is not possible

Got a proper module written up now for the macOS system media service
https://github.com/MarshallOfSound/electron-media-service
I'll be moving our existing windows and linux logic into there over the coming days so it's a truly cross platform module then pull it into here 👍


box CLI does not correctly handle certain special characters in JSON output:  – or  •

[x] I have checked that the SDK documentation doesn't solve my issue.
[x] I have checked that the API documentation doesn't solve my issue.
[x] I have searched the Box Developer Forums and my issue isn't already reported (or if it has been reported, I have attached a link to it, for reference).
[x] I have searched Issues in this repo and my issue isn't already reported.

Description of the Issue
box CLI version 2.9.0 on Windows JSON output does not successfully handle certain characters:

long hyphen character:  –  (encodes as: â€“ )
Mac-centric dot character:  •  (encodes as: ΓÇó )
Possibly other characters but I did not exhaustively search, and rather just shared what I have encountered across the account so far.  It is my hope an adjustment to character encoding/handling will address both these characters and hopefully all others which I have not yet encountered.

Steps to Reproduce

Create a box file or folder with either or both of these characters in the file/folder name:  – or  •

Run either of the following for the file itself or the parent folder respectively:
box files:get --as-user   --json
box folders:get  --as-user=$asUserID --json

For box files:get, examine the "name" attribute returned in the JSON object and not the character encodings

For box folders:get, expand item_collection, expand entries, and for the entry for the respective file, note the "name" attribute and the character encoding for the special characters noted above.

Expected Behavior
Ideally, these characters would be preserved as they are supported by the Box web GUI and by the operating system
Error Message, Including Stack Trace
Not applicable
Screenshots

Versions Used
Box CLI: 2.9.0
Operating System: Tested on Windows Server 2016 and 2019
Thanks!

Hi @nathaneig,
Unfortunately I cannot reproduce this issue on my machine with Windows 10,  it's always displays correts characters.
It may be a problem with current code page you are using.
So can you check in your Window PowerShell console which code page you are using (type chcp in console or check in Properties->Options-> Current code page)?
Can you change code page to 65001(UTF-8) and check the box api call again?

Thanks for checking and providing another direction for testing.  It appears this is a Windows centric bug in that old school Windows command shell produces the correct output, Powershell Core version 7 shell produces the correct output, a stand-alone Powershell 5.1 produces the correct output, but the Powershell 5.1 ISE mangles the output as does Powershell 5.1 when called by our automation platform.
Thanks for looking into my report but it appears you can swiftly close this bug report as a false positive as this seems to come down to a historical Windows Powershell issue that is best addressed by us modernizing our automation platform which is easier said than done.
My apologies for sending you on a wild goose chase and thanks again for your consideration and review.
From: Artur Jankowski @.>
Sent: Wednesday, January 12, 2022 4:43 AM
To: box/boxcli @.>
Cc: Nathan Eigsti @.>; Mention @.>
Subject: Re: [box/boxcli] box CLI does not correctly handle certain special characters in JSON output: – or • (Issue #269)
Hi @nathaneighttps://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnathaneig&data=04|01|nathan_eigsti%40gensler.com|229e1350971c4c90363c08d9d5c0a353|94a74758f2ff413c9f705725701b8d02|0|0|637775845623579356|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=3h6VZ%2FJAihGO7W4j7Ue8UrvEi%2FAmOKlfL7jxEXBD0Ec%3D&reserved=0,
Unfortunately I cannot reproduce this issue on my machine with Windows 10, it's always displays correts characters.
It may be a problem with current code page you are using.
So can you check in your Window PowerShell console which code page you are using (type chcp in console or check in Properties->Options-> Current code page)?
Can you change code page to 65001(UTF-8) and check the box api call again?
—
Reply to this email directly, view it on GitHubhttps://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fbox%2Fboxcli%2Fissues%2F269%23issuecomment-1010955568&data=04|01|nathan_eigsti%40gensler.com|229e1350971c4c90363c08d9d5c0a353|94a74758f2ff413c9f705725701b8d02|0|0|637775845623579356|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=x4CZmP8avvyMnhT0BDfce7wiXAq69JOJsFU5fwmculo%3D&reserved=0, or unsubscribehttps://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAOAPH6RQQOVAYKUCIWY25KDUVVSK7ANCNFSM5LSIBLJA&data=04|01|nathan_eigsti%40gensler.com|229e1350971c4c90363c08d9d5c0a353|94a74758f2ff413c9f705725701b8d02|0|0|637775845623579356|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=SQdE0wT%2F8bPMOUHjNux3NzRCRlIgtGrQiNyWPyy9yxk%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01|nathan_eigsti%40gensler.com|229e1350971c4c90363c08d9d5c0a353|94a74758f2ff413c9f705725701b8d02|0|0|637775845623579356|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=IMoV6qQJpCDllxVD%2BlHyyNbn%2BcKaCsIepJMat2VIgQo%3D&reserved=0 or Androidhttps://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01|nathan_eigsti%40gensler.com|229e1350971c4c90363c08d9d5c0a353|94a74758f2ff413c9f705725701b8d02|0|0|637775845623579356|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=iSCsHEJyoCyn9JIGjtyConoWodImeCptcdCVh5ubhx4%3D&reserved=0.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>


Remove myself from the CoC

I'm not active on this project anymore, so I shouldn't be the CoC contact.
@kngwyu @davidhewitt Feel free to add yourself instead.
Thank you for contributing to pyo3!

I'm kind of sad to see this, but @konstin thank you for all your work on PyO3!
I really learned a lot from working with you.


make 'assert (!is Exception x)' wrap the exception when it fails

Since 1.3.1, there is a new idiom:
assert (!is ParseException float = Float.parse(input));

In cases like this, the thrown AssertionError should preserve the ParseException by wrapping it.

P.S. we should also consider introducing some new syntax to streamline !is ParseException
assert (!bad float = Float.parse(input));

Or whatever. Something to think about.

we should also consider introducing some new syntax to streamline !is ParseException

Why doesn’t it actually throw the exception? Then, we could have a try/catch operator/expression:
value float = try Float.parse(input) catch(e) 0.0;

Of course, then it wouldn’t be statically typed, but still.
Maybe we can have a do/catch expression to “catch” returned exceptions:
value float = do Float.parse(input) catch(e) 0.0;

Of course, that would come at the cost of introducing a new keyword, but I think it’s worth it. It not only allows us to “catch” these returned exceptions, but it also allows us to decide which exceptions we want to catch, and even handles Foo|Exception|Null very cleanly (unlike “just using else” like it’s been suggested on Gitter).
If we had a throw/assert expression, then we could do this:
value float = do Float.parse(input) catch(e) assert(false);

value float = do Float.parse(input) catch(e) throw(AssertionError(e));

I don’t think that we should have a bad keyword or something like this for checking against exceptions. I think the syntax we already have (is Exception) is already neat enough.

Great, thanks @tombentley !!


bump gogogate2 version

Description:
This PR bumps the version of the pygogogate2 component which fixes an issue with encryption for the gogogate2 api
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#<home-assistant.github.io PR number goes here>
Example entry for configuration.yaml (if applicable):
Checklist:
[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[] If user exposed functionality or configuration variables are added/changed:
[] Documentation added/updated in home-assistant.github.io
[] If the code communicates with devices, web services, or third-party tools:
[x] New dependencies have been added to the REQUIREMENTS variable (example).
[] New dependencies are only imported inside functions that use them (example).
[x] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[] New files were added to .coveragerc.
If the code does not interact with devices:
[] Tests have been added to verify that the new code works.

Thanks, updated

:)