text:
App: animation_url used to load .metaversefile in app, but NFT marketplaces will show as json then

For loading NFTs from wallet in Webaverse, it looks like putting the path to the .metaversefile in the animation_url metadata field was decided on.
This will make it easy for Webaverse to pull NFTs from a user's wallet and load them into the world. The downside of this is that NFT marketplaces will then show json as the preview image.
I'm not sure if there is a better solution, but wanted to bring this up.

Note: that the NFTs are rendered using the image and not animation_url when outside of the specific asset detail's page, for example this is the image which links to a gif:

For loading NFTs from wallet in Webaverse, it looks like putting the path to the .metaversefile in the animation_url metadata field was decided on.

Putting .metaversefile into the token url itself is not the intended usage. Does some documentation say otherwise? (we should fix that)
.metaversefile is designed to be out of the way, in the same directory as the content you are trying to render. That is why it is a dotfile. If you point animation_url to a bare directory the .metaversefile should be auto picked up.
IMO we should just have "metaverse_url": "https://path/to/.metaversefile or https://directory/containing/metaversefile/", but that handling needs to be implemented.

metaverse_url would work for me. I don't think this exists in the documentation currently, I asked in #dev channel in discord and was told it was animation_url.
Was trying to figure out which field to use so that when someone connects their web3 wallet to Webaverse, they are able to load the .metaversefile into the world.
Since OpenSea uses animation_url to showcase the nft, it makes sense not to put the .metaversefile there since it would show as json ^.
I'm cool with whatever field will be used to load into webaverse, I think animation_url has been used since that is where most 3d nfts put their glb/etc.
Webaverse could look at an NFT and load it in based on a priority of:

Does it have a metaverse_url, load that in
If not, then animation_url
If not, then image or image_data (raw svg)

Yeah I think that's the right priority for keeping things opt-in and optimally compatible. It sounds like a small feature to implement that.


text:
perf(tangle-dapp): Fix performance issue in Nomination page

Summary of changes
Provide a detailed description of proposed changes.

The performance of the Nomination page had severely degraded after changes were made to the data fetching hooks, this PR addresses that.
Was using the wrong data fetching function (Promise-based API when should be using RxJS). Performance is back to what it was, but the slight freeze remains. That still needs to be optimized. However, it is currently usable.
Made some changes so that when updating nominations and delegating, it will load validator data when the modal is opened, instead of doing it all on page load, which would significantly slow down page load. This affects the modal opening animations, but it is a worthy compromise for now.
Also took the opportunity to cleanup and refactor delegation & nomination code, that is why there are many modified files.
Made some unrelated changes adjusting balance calculations & modifying the structure and styling of the account page.

Proposed area of change
Put an x in the boxes that apply.

[ ] apps/bridge-dapp
[ ] apps/hubble-stats
[ ] apps/stats-dapp
[x] apps/tangle-dapp
[ ] apps/testnet-leaderboard
[ ] apps/faucet
[ ] apps/zk-explorer
[ ] libs/webb-ui-components

Reference issue to close (if applicable)
Specify any issues that can be closed from these changes (e.g. Closes #233).

Closes #2144

Screen Recording
If possible provide a screen recording of proposed change.

Code Checklist
Please be sure to add .stories documentation if any additions are made to libs/webb-ui-components.

[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

@yurixander
Have you checked on this problem: Sine values are still being displayed even with no wallet connection because local storage still stores those values

@yurixander
Have you checked on this problem: Sine values are still being displayed even with no wallet connection because local storage still stores those values

Those values are sort of "public" values so they don't depend on an active wallet, but yea they're being displayed without an active wallet. We might as well remove local storage caching for them since now they do load relatively faster than before so caching might not be needed.

source: gharchive/pull-request

repo: webb-tools/webb-dapp

license_type: permissive

license_source: github-api


text:
Using with the Spock framework

I'm converting a project from Spock 1.3 to 2.0, which requires migrating from JUnit 4 dependencies to JUnit 5. We made use of Stefan Birkner's system-rules library, and this seemed like a handy replacement. However, I can't get the environment variables to work anymore. I have tried adding in this library like so:
@SpringBootTest
@ExtendWith(SystemStubsExtension.class)
class ServiceTest extends Specification {
    @Shared
    @SystemStub
    static final EnvironmentVariables environmentVariables = new EnvironmentVariables().set("KAFKA_RUNTIME_ENV", "dev")

    // unit tests follow
}

However, the system is not picking up the KAFKA_RUNTIME_ENV variable:
Unable to determine Environment through Environment Variable, ensure that one of the following is set: KAFKA_RUNTIME_ENV, ENVIRONMENT
What am I missing?

@spartanhooah - great question.
Here's the thing. The Annotation @SpringBootTest is processed BEFORE the SystemStubsExtension is able to turn on the environment variable.
In this situation, I would normally use @Nested classes.
See the example here - https://github.com/webcompere/system-stubs/blob/main/system-stubs-jupiter/src/test/java/uk/org/webcompere/systemstubs/jupiter/examples/SpringAppWithDynamicPropertiesTest.java#L36
This controls the lifecycle of the environment variables BEFORE Spring ever gets a chance to decide how to build a context.
You might get lucky by putting @ExtendWith(SystemStubsExtension.class) before @SpringBootTest, but I prefer the above pattern.
Alternatively, you can manually execute the setup() and teardown() methods on EnvironmentVariable so that the static initializer of the class turns on the configuration, and then the @AfterAll turns it off. I'd avoid that.
One last thing to bear in mind, the demonstrated pattern is especially useful when you're making resources on temp ports and you want spring to know about them through either environment variables or system properties. You initialize test resources in the outer test, which then delegates to the inner @SpringBootTest when everything's all set up right.

Ok, thanks for all the information. I'll look into your suggestions.

source: gharchive/issue

authors: ashleyfrieze spartanhooah

repo: webcompere/system-stubs

license: MIT


text:
How to use PHP 7.1 or even PHP 7.2?

PHP 7.0 is good, just that some applications I have use the 7.2 features
Any ideas on how to upgrade both dev and production?
I could use this image  webdevops/php-apache-dev:7.1  but then I get Memcached >= 2.2.0 is required
Thank you.

I think I made it work by installing memcached-3.0.4
I'm open to a more elegant solution
FROM webdevops/php-apache-dev:7.1

ENV PROVISION_CONTEXT "development"

# Deploy scripts/configurations
COPY etc/             /opt/docker/etc/

RUN ln -sf /opt/docker/etc/cron/crontab /etc/cron.d/docker-boilerplate \
    && apt-get update && apt-get install -y libmemcached11 libmemcachedutil2 build-essential libmemcached-dev libz-dev \
    && pecl install memcached-3.0.4 \
    && echo extension=memcached.so >> /usr/local/etc/php/conf.d/memcached.ini \
    && chmod 0644 /opt/docker/etc/cron/crontab \
    && echo >> /opt/docker/etc/cron/crontab \
    && ln -sf /opt/docker/etc/php/development.ini /opt/docker/etc/php/php.ini

# Configure volume/workdir
WORKDIR /app/

Tried using:
FROM webdevops/php-apache-dev:7.2
and it failed:
ERROR: Service 'app' failed to build: manifest for webdevops/php-apache-dev:7.2 not found
So, is PHP 7.2 supported?

See https://github.com/webdevops/Dockerfile/issues/211

authors: hhoechtl kniziol patrioticcow

repo: webdevops/php-docker-boilerplate

license: mit

license_source: bigquery


text:
Can't resolve the file - Something wrong with splitChunks, scss and image

See branch https://github.com/silveoj/pug-plugin-responsive-loader-issue/tree/scss-and-chunks
I can't build if I use
splitChunks: {
  chunks: 'all', // remove it to work
},

I get error on Win and Linux:
Can't resolve the file ../src/assets/img/image.png in ..\src\html\pages\view-2.pug
here:
header
  img(src=require('~Images/image.png'))

Also it starts to works SOMETIMES if I remove .browserlistrc
I can replace padding-bottom to padding-top and it will work.
I can remove random line and it CAN start to work.

I think it's pug-plugin issue because error with require('~Images/image.png')
To run webpack-dev-server I need to remove require('~Images/image.png'), run server and restore require. Now it's work on dev-server.
But there is no chance to build dist files

@silveoj thank you for the issue report.
I will fix it.

@silveoj
I can't reproduce the issue.
See please the PR.
In your repo I have updated pug-plugin to v2.8.0 and added splitChunks. It's works on macOS.
Could you add the needed code to [repository] (https://github.com/silveoj/pug-plugin-responsive-loader-issue/tree/scss-and-chunks) to reproduce the issue.
P.S.  I will check it on Win10 yet.

@webdiscus
main branch works for me also.
See please scss-and-chunks branch. All packages are out of date.

@webdiscus
main branch works for me also.
See please scss-and-chunks branch. All packages are out of date.
Win10 / Ubuntu 18

@webdiscus
main branch works for me also.
See please scss-and-chunks branch. All packages are out of date.
Win10 / Ubuntu 20

@silveoj ah, sorry, I will get the scss-and-chunks branch.

@silveoj
As temporary solution disable the postcssOptions by postcss-loader and it's works with splitChunks.
Seems, the postcss-loader breaks CSS standard syntax.  I will add supports for this case.

@silveoj
The problem was by Webpack splitChunks. It's not a bug of pug-plugin.
Webpack splits all JavaScript files and those that not should, that completely breaks the compilation process.
I have some improvements in v2.9.3, update please the pug-plugin.
Solution
You must concrete specify what scripts should be splitted, using optimization.splitChunks.cacheGroups:
module.exports = {
  optimization: {
    splitChunks: {
      cacheGroups: {
        scripts: {
          test: /\\.(js|ts)$/,
          chunks: 'all',
        },
      },
    },
  },
  // ...
};

Note: in the test option must be specified all extensions of scripts which should be splitted.

@silveoj see the PR, it works now.

authors: silveoj webdiscus

repo: webdiscus/pug-plugin

license: ISC


text:
Handle accordions that are visible but disabled and have no panel

This works in 3.x with jQuery but does not yet work in #4

closed by #8

closed by #8

repo: webfactory/accordion


text:
On windows, the component inspector is not working

http://0.0.0.0:8080/__open-in-editor?file=src/views/login/login.vue:74:6

ref  https://github.com/webfansplz/vite-plugin-vue-devtools/issues/58
@alexzhang1030  @webfansplz

单独使用 vite-plugin-vue-inspector 也无法工作

https://devtools.vuejs.org/guide/open-in-editor.html#open-component-in-editor
可以试试这个看看有没有效果，确认一下是不是上游库的问题，另，你在 WSL 中启动的 vite dev server 吗

  server: {
    port: 8080,
    host: '0.0.0.0'
  }

我排查到了是因为我设置了 host 0.0.0.0

这种有解决方案吗，还是说从   https://github.com/webfansplz/vite-plugin-vue-inspector/blob/7201322b77d38e2349c7151dd8fc2bada4f2ff98/packages/core/src/Overlay.vue#L209 这里修改，将 baseUrl 中的host统一为localhost  @alexzhang1030 @webfansplz

@webfansplz 可以考虑给 vite-plugin-inspect 加一个参数 参考这个

@alexzhang1030  既然是本地开发，是不是可以通过正则将  ... 统一转为 localhost

repo: webfansplz/vite-plugin-vue-devtools


text:
[BUGFIX] Fix wrong path for package.json

[DESC.]
Now 'Help -> About' dialog will show up.
Related to OPTC-64.
Note that in the dialog, the version number is still 1.5.0 which is hard-coded.
@kyungmi will fix the version number when we release 1.6.0.

@happibum Thanks a lot!

authors: happibum kyungmi

repo: webida/webida-client


text:
docs(config) document new stats preset

document new stats preset
Fixes #3002

Thanks!

authors: EugeneHlushko montogeek


text:
Fix https settings for own certs

Hi! If you want to use own https certificate for hmr with devServer you should pass cert & key in the devServer.https object not just root devServer object.

I believe it's a change in webpack-dev-server v4 which is still in beta. The current documentation targets the latest released version, i.e., v3.

I believe it's a change in webpack-dev-server v4 which is still in beta. The current documentation targets the latest released version, i.e., v3.

I see the same https object config one paragraph above at the https://webpack.js.org/configuration/dev-server/#devserverhttp2 so let the bring docs consistent?

Lets allow and add a badge for beta version.

@vladimirmartsul That would make sense. I've tested against webpack-dev-server v3, the object version works as well:

authors: chenxsan snitin315 vladimirmartsul


text:
[webpack 5]Switch to on/off ESM usage info log in chunks.

Feature request
Seems like webpack 5 generate ESM usage info in chunks for the sake of tree-shaking and that's awesome!
But it may takes up too much bytes in dev mode.
We are actively working on a long-term monorepo(over 1 million lines of code). After switch to webpack 5, the prod mode chunks are slightly smaller than webpack 4. But the dev mode chunks are almost 40M bigger.
Size built on webpack 4:

Size built on webpack 5:

And most of the incremental bytes are these logs:

Is it necessary to add a config that can manually switch on/off the tree-shaking feature or ESM usage info in dev mode? Or am i missing something that will do the same?

What is the expected behavior?
It's available to switch off ESM usage info in dev mode.
What is motivation or use case for adding/changing the behavior?
Smaller chunks means faster load time and greater development experience.
How should this be implemented in your opinion?
A switch to on/off the tree-shaking feature or ESM usage info in dev mode.
Are you willing to work on this yourself?
yes

Please use terser-webpack-plugin to remove comments or you can disable all optimization https://github.com/webpack/webpack/blob/master/lib/config/defaults.js#L833

A switch to on/off the tree-shaking feature or ESM usage info in dev mode.

output.pathinfo: false disables the info comments.

authors: ZKHelloworld evilebottnawi sokra

repo: webpack/webpack


text:
On Windows, wepback build is blocked during 'emit' phase

I'm submitting a bug report
Webpack version:
1.13.1
Please tell us about your environment:
Linux & Windows 10
Current behavior:
I created a simple webpack project for a Typescript library : https://github.com/lbar/test-webpackts-issue
On linux, npm run build finishes successfully:
> rimraf dist && webpack --progress --profile
10% 0/1 build modulests-loader: Using typescript@1.8.10 and /tmp/testwebpack/tsconfig.json                                                                                8030ms1217ms optimi5ms emit
Hash: 8eac1502f3b7a9a19be2
Version: webpack 1.13.1
Time: 2596ms
Asset       Size  Chunks             Chunk Names
index.js  816 bytes       0  [emitted]  index
index.js.map    6.07 kB       0  [emitted]  index
/tmp/testwebpack/dist/index.d.ts   31 bytes          [emitted]
/tmp/testwebpack/dist/src/info.d.ts   49 bytes          [emitted]
+ 2 hidden modules

On Windows, npm run build is blocked during 'emit' phase. The output is :
> rimraf dist && webpack --progress --profile

10% 0/1 build modulests-loader: Using typescript@1.8.10 and C:\tmp\testwebpack\tsconfig.jso
1836ms build modules
3ms seal
7ms optimize
3ms hashing
7ms create chunk assets
79ms additional chunk assets
19ms optimize chunk assets
837ms optimize assets
95% emit

The version of node differs: 6.2.2 on Windows and 4.4.5 on Linux. I don't know if it may be the cause. Has anyone an idea about the problem? Issue in webpack, ts-loader or typescript?
One more thing, call to tsc is working on both systems.
Thanks for your help
Expected/desired behavior:
Windows terminates building of package.

Language: TypeScript 1..8

Are you using
declartion: true

in ts.config?
So check the following:
https://github.com/TypeStrong/ts-loader/issues/185

Yes, exactly. So the issue comes from ts-loader and not webpack. Happy to learn that!
Thank you I close the issue.

Workaround is use awesome-typesript-loader instead of ts-loader, without cache option.
See https://github.com/s-panferov/awesome-typescript-loader/issues/152


text:
Fix module of electron target: web-view -> web-frame

See this commit.
The web-view has been renamed to web-frame.

Could you keep both versions to support older electron versions?

Could you keep both versions to support older electron versions?

ping

@sokra sorry, I forget about it. :\
It's done. :)

Thanks


text:
Added missing semicolon on the final output

On some external libraries, there is and issue with the minifications of the JS code with this missing semicolon.
Related issue

https://github.com/wp-media/wp-rocket/issues/5512

What kind of change does this PR introduce?

Added missing semicolon on the final output.

Did you add tests for your changes?

No.

Does this PR introduce a breaking change?

No it doesn't.

What needs to be documented once your changes are merged?

Nothing.

But you don't need ; after }

Sorry, we can't add ; in any places, it should be fixed on the minimizer side and don't use regexps to parse JS code, because it is unsafe and dangerous, after } we don't need ;

Anyway feel free to feedback

authors: alexander-akait iruzevic


text:
Cannot run pnpm create @knip/config in nx monorepo root

I was running pnpm create @knip/config in my nx monorepo root and the execution fails with the following error.
.../Library/pnpm/store/v3/tmp/dlx-15451  |   +1 +
.../Library/pnpm/store/v3/tmp/dlx-15451  | Progress: resolved 1, reused 1, downloaded 0, added 1, done
node:internal/errors:865
  const err = new Error(message);
              ^

Error: Command failed: pnpm add -D knip typescript @types/node
    at checkExecSyncError (node:child_process:885:11)
    at execSync (node:child_process:957:15)
    at main (file:///Users/pavindu/Library/pnpm/store/v3/tmp/dlx-15451/node_modules/.pnpm/@knip+create-config@1.0.1/node_modules/@knip/create-config/index.js:26:3)
    at file:///Users/pavindu/Library/pnpm/store/v3/tmp/dlx-15451/node_modules/.pnpm/@knip+create-config@1.0.1/node_modules/@knip/create-config/index.js:35:1
    at ModuleJob.run (node:internal/modules/esm/module_job:194:25) {
  status: 1,
  signal: null,
  output: [
    null,
    Buffer(352) [Uint8Array] [
      226, 128, 137,  69,  82,  82,  95,  80,  78,  80,  77,  95,
       65,  68,  68,  73,  78,  71,  95,  84,  79,  95,  82,  79,
       79,  84, 226, 128, 137,  32,  82, 117, 110, 110, 105, 110,
      103,  32, 116, 104, 105, 115,  32,  99, 111, 109, 109,  97,
      110, 100,  32, 119, 105, 108, 108,  32,  97, 100, 100,  32,
      116, 104, 101,  32, 100, 101, 112, 101, 110, 100, 101, 110,
       99, 121,  32, 116, 111,  32, 116, 104, 101,  32, 119, 111,
      114, 107, 115, 112,  97,  99, 101,  32, 114, 111, 111, 116,
       44,  32, 119, 104,
      ... 252 more items
    ],
    Buffer(0) [Uint8Array] []
  ],
  pid: 15471,
  stdout: Buffer(352) [Uint8Array] [
    226, 128, 137,  69,  82,  82,  95,  80,  78,  80,  77,  95,
     65,  68,  68,  73,  78,  71,  95,  84,  79,  95,  82,  79,
     79,  84, 226, 128, 137,  32,  82, 117, 110, 110, 105, 110,
    103,  32, 116, 104, 105, 115,  32,  99, 111, 109, 109,  97,
    110, 100,  32, 119, 105, 108, 108,  32,  97, 100, 100,  32,
    116, 104, 101,  32, 100, 101, 112, 101, 110, 100, 101, 110,
     99, 121,  32, 116, 111,  32, 116, 104, 101,  32, 119, 111,
    114, 107, 115, 112,  97,  99, 101,  32, 114, 111, 111, 116,
     44,  32, 119, 104,
    ... 252 more items
  ],
  stderr: Buffer(0) [Uint8Array] []
}

Node.js v18.17.0

It seems like pnpm add doesn't work in nx/pnpm workspace root unless -w flag is provided. Is there a way to run pnpm create @knip/config in monorepo root without errors?

Thanks for the report! I think we should add the -w for pnpm in monorepos. Would you like to submit a pull request?

Getting same issue but even with -W param now.
node:internal/errors:983
  const err = new Error(message);
              ^

Error: Command failed: yarn add -W -D knip typescript @types/node
    at genericNodeError (node:internal/errors:983:15)
    at wrappedFn (node:internal/errors:537:14)
    at checkExecSyncError (node:child_process:888:11)
    at execSync (node:child_process:960:15)
    at main (file:///private/var/folders/7t/x_27lndd5lz_qt50v0jfdygc0000gn/T/xfs-107abe5b/dlx-5250/node_modules/@knip/create-config/index.js:44:3)
    at file:///private/var/folders/7t/x_27lndd5lz_qt50v0jfdygc0000gn/T/xfs-107abe5b/dlx-5250/node_modules/@knip/create-config/index.js:53:1
    at ModuleJob.run (node:internal/modules/esm/module_job:268:25)
    at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:543:26)
    at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:116:5) {
  status: 1,
  signal: null,
  output: [
    null,
    Buffer(233) [Uint8Array] [
       27,  91,  51,  49, 109,  27,  91,  49, 109,  85, 110, 107,
      110, 111, 119, 110,  32,  83, 121, 110, 116,  97, 120,  32,
       69, 114, 114, 111, 114,  27,  91,  50,  50, 109,  27,  91,
       51,  57, 109,  58,  32,  85, 110, 115, 117, 112, 112, 111,
      114, 116, 101, 100,  32, 111, 112, 116, 105, 111, 110,  32,
      110,  97, 109, 101,  32,  40,  34,  45,  87,  34,  41,  46,
       10,  10,  36,  32, 121,  97, 114, 110,  32,  97, 100, 100,
       32,  91,  45,  45, 106, 115, 111, 110,  93,  32,  91,  45,
       69,  44,  45,  45,
      ... 133 more items
    ],
    Buffer(0) [Uint8Array] []
  ],
  pid: 5255,
  stdout: Buffer(233) [Uint8Array] [
     27,  91,  51,  49, 109,  27,  91,  49, 109,  85, 110, 107,
    110, 111, 119, 110,  32,  83, 121, 110, 116,  97, 120,  32,
     69, 114, 114, 111, 114,  27,  91,  50,  50, 109,  27,  91,
     51,  57, 109,  58,  32,  85, 110, 115, 117, 112, 112, 111,
    114, 116, 101, 100,  32, 111, 112, 116, 105, 111, 110,  32,
    110,  97, 109, 101,  32,  40,  34,  45,  87,  34,  41,  46,
     10,  10,  36,  32, 121,  97, 114, 110,  32,  97, 100, 100,
     32,  91,  45,  45, 106, 115, 111, 110,  93,  32,  91,  45,
     69,  44,  45,  45,
    ... 133 more items
  ],
  stderr: Buffer(0) [Uint8Array] []
}

Node.js v22.11.0

It's happening with yarn
node:internal/errors:983
  const err = new Error(message);
              ^

Error: Command failed: yarn add -W -D knip typescript @types/node
    at genericNodeError (node:internal/errors:983:15)
    at wrappedFn (node:internal/errors:537:14)
    at checkExecSyncError (node:child_process:888:11)
    at execSync (node:child_process:960:15)
    at main (file:///private/var/folders/7t/x_27lndd5lz_qt50v0jfdygc0000gn/T/xfs-107abe5b/dlx-5250/node_modules/@knip/create-config/index.js:44:3)
    at file:///private/var/folders/7t/x_27lndd5lz_qt50v0jfdygc0000gn/T/xfs-107abe5b/dlx-5250/node_modules/@knip/create-config/index.js:53:1
    at ModuleJob.run (node:internal/modules/esm/module_job:268:25)
    at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:543:26)
    at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:116:5) {
  status: 1,
  signal: null,
  output: [
    null,
    Buffer(233) [Uint8Array] [
       27,  91,  51,  49, 109,  27,  91,  49, 109,  85, 110, 107,
      110, 111, 119, 110,  32,  83, 121, 110, 116,  97, 120,  32,
       69, 114, 114, 111, 114,  27,  91,  50,  50, 109,  27,  91,
       51,  57, 109,  58,  32,  85, 110, 115, 117, 112, 112, 111,
      114, 116, 101, 100,  32, 111, 112, 116, 105, 111, 110,  32,
      110,  97, 109, 101,  32,  40,  34,  45,  87,  34,  41,  46,
       10,  10,  36,  32, 121,  97, 114, 110,  32,  97, 100, 100,
       32,  91,  45,  45, 106, 115, 111, 110,  93,  32,  91,  45,
       69,  44,  45,  45,
      ... 133 more items
    ],
    Buffer(0) [Uint8Array] []
  ],
  pid: 5255,
  stdout: Buffer(233) [Uint8Array] [
     27,  91,  51,  49, 109,  27,  91,  49, 109,  85, 110, 107,
    110, 111, 119, 110,  32,  83, 121, 110, 116,  97, 120,  32,
     69, 114, 114, 111, 114,  27,  91,  50,  50, 109,  27,  91,
     51,  57, 109,  58,  32,  85, 110, 115, 117, 112, 112, 111,
    114, 116, 101, 100,  32, 111, 112, 116, 105, 111, 110,  32,
    110,  97, 109, 101,  32,  40,  34,  45,  87,  34,  41,  46,
     10,  10,  36,  32, 121,  97, 114, 110,  32,  97, 100, 100,
     32,  91,  45,  45, 106, 115, 111, 110,  93,  32,  91,  45,
     69,  44,  45,  45,
    ... 133 more items
  ],
  stderr: Buffer(0) [Uint8Array] []
}

Node.js v22.11.0

authors: julianCast pavinduLakshan webpro

repo: webpro-nl/knip


text:
Fix cards drift off bug

fixes #30 by using the fix proposed here

Can this be merged? It fixes a bug that appears when we migrate to RN 0.73.X (from 0.71.X, for instance).

merged and released under 2.0.17

authors: blacktemplar nunofgm webraptor

repo: webraptor/react-native-deck-swiper


text:
Revert "DSPL-233 add spacing between rich text and title"

This reverts commit 38ceb198d834c3486e5a88841db55b68659ef7db.

Description

Motivation and Context

Screenshots (if appropriate)
Upgrade notes (if appropriate)

Types of changes

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

Checklist:

[ ] My code follows the code standards of this project.
[ ] My change requires updating the documentation. I have updated the documentation accordingly.

Codecov Report

Merging #740 (803dd54) into main (998c0e6) will not change coverage.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff            @@
##               main     #740   +/-   ##
=========================================
  Coverage     64.15%   64.15%
  Complexity      151      151
=========================================
  Files            28       28
  Lines           371      371
  Branches         31       31
=========================================
  Hits            238      238
  Misses          112      112
  Partials         21       21

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

repo: websight-io/howlite


text:
Task based docker

Run tasks within Docker?
Ref task: webplatform/ops#153
Try container: https://registry.hub.docker.com/u/webspecs/publican/

Its still incomplete. I’ll make another fork.

repo: webspecs/publican


text:
🛑 The Good Cyclist is down

In e346617, The Good Cyclist (https://thegoodcyclist.iwview.com) was down:

HTTP code: 521
Response time: 96 ms

Resolved: The Good Cyclist is back up in 30a01ba after 416 days, 3 hours, 31 minutes.

repo: webworldview/uptime


text:
🛑 Jeff with Susan is down

In 6e556cc, Jeff with Susan (https://www.jeffwithsusan.com) was down:

HTTP code: 521
Response time: 138 ms

Resolved: Jeff with Susan is back up in d80ea05 after 420 days, 21 hours, 36 minutes.


text:
🛑 TestPlayDump is down

In ea92287, TestPlayDump (https://www.testplaydump.com) was down:

HTTP code: 400
Response time: 320 ms

Resolved: TestPlayDump is back up in 43d387b.


text:
Move some common utils functions and types to @sunmao/shared

What problem does this feature solve?
What does the proposed API look like?

May call it @sunmao/shared is better? Because utils, constants, types also have common parts.

Not only utils functions. Many types are need to be sharedEditorServices, Category.

authors: MrWindlike tanbowensg

repo: webzard-io/sunmao-ui


text:
[BUG]room.MemberAll 返回的列表有问题

问题：
room.MemberAll 获得所有人列表， 发消息at时没有效果
代码：

日志：

请确认下 room.MemberAll 是否获取到了群成员？
你用的是什么 puppet ？

1 索取列表之后就打log了，看起来只获取到了自己
2 是用的 padlocal

那问题是没有获取到群成员，而不是@没效果，  你不妨遍历下获取到的群成员列表打印下，看获取到了什么

那问题是没有获取到群成员，而不是@没效果， 你不妨遍历下获取到的群成员列表打印下，看获取到了什么

您看上面截图，直接打印，自己获取到了，另一个就报地址有问题了（测试群只有两个人），我稍后遍历打印试试。

另外 @ 要把机器人自己过滤掉

另外 @ 要把机器人自己过滤掉

嗯嗯。这个就是功能细节了好说～

@chasonnchen 现在还有问题吗？

问题仍然存在，没有定位到具体原因，我这边就先不实现 @all 这个功能了
附上咱们在群里聊天记录

我的项目地址：https://github.com/chasonnchen/wechat_bot

@chasonnchen 这个问题已经修复，请升级到 v0.3.9

authors: chasonnchen dchaofei

repo: wechaty/go-wechaty


text:
Cheers! The first version that passed the CI!

See: https://github.com/wechaty/python-wechaty/actions/runs/53675385
@wj-Mcat We should have some beer! :beers:

@huan 🍻🍻 we have to go on.

Yes, let's move on.
You have made a great process, I appreciate your work!!

authors: huan wj-Mcat

repo: wechaty/python-wechaty


text:
No dependency management file

This project currently has no dependency management.
It cannot be compiled.
we should use sbt and  add build.sbt

Thanks for the contribution!
Could you please also add a GitHub Action to enable CI for this repo, so that we can make sure your PR works as expected?
After that, I'd like to merge your PR, thank you very much.

Sure. Enabling CI for sbt is not a easy task for me. Will work on it.

authors: YipZong huan

repo: wechaty/scala-wechaty-getting-started


text:
Set up Project

[x] Create Project
[x] Add collaborators
[x] Configure status options
[x] Set up workflows
[x] Associate with repository
[x] Configure views

@ffund Please review our project

:+1:


text:
🛑 Authentication is down

In 2bead93, Authentication (https://auth.wectrl.io) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Authentication is back up in 3854e50 after 42 minutes.

repo: wectrl-io/upptime


text:
Confetti Animation

Add confetti animation when you request a new term

Check: https://react95.io/

repo: wego-technologies/freightwebster


text:
matcher graph generator TLC

The matcher graph generator  is creaking a little.  It could do with some care.

If you run it without Graphviz installed, it claims to have generated a PDF, but has not.
Ideally, we would be able to optionally specify a pipeline date as a CLI argument (e.g. to compare differences between a live and non-live pipeline).

I achieved this by just hardcoding the date I wanted, but a "proper" way would be better

Appending "(suppressed)" to suppressed images makes the HTML labels invalid, and prevents dot creating the image.

an HTML-Like label can either be text or a table, not both,  so it needs to be inserted into the table, not appended afterwards as it is for text labels.
When this happens, it fails in the same manner as 1, above, rather than informing the user of any problems.

Thinking about the pipeline date thing.  I think the main reason for this is to compare between multiple existing pipelines, so perhaps having some incantation that tells it to generate multiple graphs would be nice.

If we're going to be working on this tool, I wonder if it would be useful to annotate the edges with the reasons at the same time? Or have a flag for doing that?

authors: alexwlchan paul-butcher

repo: wellcomecollection/catalogue-pipeline


text:
Only deploy ECS services that have actually changed

This patch makes two changes:

Drastically simplify the output from a successful 'deploy' command. At most I want to know stuff is happening; the exact deployment IDs are massively overkill.
The ECR tagging function already returns a status: noop if the image tags aren't changing. If we can catch and notice that, we can skip churning services that won't be changed with a deployment.

Previously:

Now:

The deployment ID is a critical bit of info if you want to track deployment success, visibility of the tagging operations was very helpful in debugging - I suggest you put them behind the verbose flag.

I saved them to a file instead, and always show you the path – the verbose flag is helpful if you know you're in debugging mode, but you can't go back and get verbose logs for a deploy you've just run which failed.

repo: wellcomecollection/weco-deploy


text:
Better health checks in the API

Last week the healthcheck/alerting failed to spot that a change to the Elasticsearch credentials had clobbered the API. Previously it’s failed to spot when the ES cluster was in an unhealthy state.
We should make sure our monitoring systems can spot this, and nag us if it’s broken.

Closing as out of date.

authors: alexwlchan kenoir

repo: wellcometrust/platform


text:
[WIP] bucket-to-bucket archive storage bagit flow

This is an experiment with the flow that will eventually, for a given identifier (for now, only b numbers of digitised objects) collect METS, METS-ALTO, and digitised assets from various locations, create a bagit ingest package, drop it in an ingest bucket, and initiate the archival storage process for that identifier.
This serves three purposes:

A tool to create a vast supply of test content for the archival storage service by bagging existing things
A means of evolving the specification for what Intranda need to change in Goobi, by transforming METS into what we think we want
The code to migrate every digitised thing in Preservica into the new storage

Currently only works for single-manifestation METS files (not multi volume works) and doesn't actually collect the assets.


text:
Prismic Home page

Date
30.05.18 - 03.06.18
Page
https://wellcomecollection.org/
Purpose / Hypothesis
To see how people are interacting (scroll and click) with the new Prismic home page.
Primary outcome
"Visit us" most clicked on part of the page.
Sample size / power
2000 pageviews.
Comments

https://insights.hotjar.com/h?site=3858&heatmap=2718120&token=cede530e9dd1a89f3a384f19aa168aaf

authors: hthair jamesgorrie


text:
refresh prismic API every minute

Type

🔧 Fix
Value
We make sure we return the latest version of the article.
If we only load the Prismic API on app launch, and then update the master ref (essentially the master branch of our content), we will be retrieving an old value.
I could setup a webhook on Prismic but that's feels a little to decoupled, but might if this causes problems, which I can't imagine it will.

Merging as it's blocking and doesn't affect user content.


text:
VSResize resizes command line if there are no splits below

@greduan: This works as expected. Calling :VSResize resizes the current window to show the given range (which is the current line by default). The same happens when you type 1<C-W>_ in normal mode (which is exactly what the plugin is doing internally).
Maybe you wanted to use :VSSplit, :VSSplitAbove or :VSSplitBelow?
I agree that this might be unexpected and it happened to me too. You can type <C-W>_ to maximize the window again.
I'd like to avoid this behavior, but I'm not aware of a Vimscript function that I can use to find out if the current window is part of a vertical split. Please let me know if there is a way to do that. I'd be happy to use that.

This seems to hint that the solution is to test if you can switch to a window below/above you to detect if there's a split: http://stackoverflow.com/questions/6435792/check-if-vim-split-window-is-most-bottom-most-right
That's the solution I came up with before checking it as well, although I haven't confirmed if it would work in a script.
BTW my solution to this would be to split below so as to make sure that the other splits aren't resized, only the one I'm on.

@greduan: Thanks for the link. I might consider something like that. I'd need to check in both directions (above and below), though.
@mattn: Would you still recommend that approach of trying to switch to a window above/below to check if the current window is in a vertical split or are you aware of any better way to do that check? (I'm referring to your answer here: http://stackoverflow.com/a/6436112)

could you please let me know the way to reproduce?

@mattn: Assuming you're willing to use this plugin for testing:

Install plugin.
Open any file (your .vimrc for example).
Execute this command: :VSResize.

This will execute :1wincmd _ to resize the current window to hight 1. If you don't want to use that plugin you could type that instead.
This is the expected behavior of this plugin if there are multiple windows split vertically, because then resizing one of them to a smaller hight will make the other one bigger. What we would want to do is avoid resizing if there are no windows above and below the current one. Practically disable that commend in a single window layout.
In the linked stackoverflow question you answered a similar question, but that's almost five years ago, so I was wondering if you might be aware of a less hacky way to do that now. Are there any vimscript functions to explore the current tabs window layout to make such decisions?
Thanks for your help!

@greduan: I implemented a check in #7 similar to the stackoverflow thing you linked. Please let me know if that works for you. Thanks for bringing this up!

@wellle Cool I'll let you know when I try it out, going to give Emacs a serious try for programming this week so it'll be a while before I try it. Also I never got into the habit of using this plugin since it had this behaviour that I reported.
In any case, it's a good change. :)

authors: greduan mattn wellle


text:
disconnect from APRS server if connection hangs

Previously a hanging TCP connection (i.e. on an intermittent network) would cause the APRS client to hang indefinitely. Now, it'll disconnect after a minute of hearing nothing. The APRS-IS servers send heartbeats regularly so this shouldn't cause any false disconnects

Looks good. Can you bump the version to 0.3.2 and then I'll merge and release.

Done!

repo: welshdave/simple-aprs


text:
runtime/libtorch/run with local build ERROR

您好，我尝试使用aishell自己训练之后得到final.zip，然后使用runtime/libtorch/run with local build进行推理，在进行到cmake --build .这一步时出现了下面的错误，请您帮忙解答一下谢谢
Consolidate compiler generated dependencies of target post_processor
[ 42%] Built target post_processor
Consolidate compiler generated dependencies of target kaldi-base
[ 44%] Built target kaldi-base
Consolidate compiler generated dependencies of target kaldi-util
[ 48%] Built target kaldi-util
Consolidate compiler generated dependencies of target kaldi-lat
[ 50%] Built target kaldi-lat
Consolidate compiler generated dependencies of target kaldi-decoder
[ 52%] Built target kaldi-decoder
Consolidate compiler generated dependencies of target kaldi-lm
[ 55%] Built target kaldi-lm
Consolidate compiler generated dependencies of target kaldi-fstext
[ 57%] Built target kaldi-fstext
Consolidate compiler generated dependencies of target arpa2fst
[ 59%] Built target arpa2fst
Consolidate compiler generated dependencies of target fstaddselfloops
[ 61%] Built target fstaddselfloops
Consolidate compiler generated dependencies of target fstdeterminizestar
[ 62%] Built target fstdeterminizestar
Consolidate compiler generated dependencies of target fstisstochastic
[ 64%] Built target fstisstochastic
Consolidate compiler generated dependencies of target fstminimizeencoded
[ 66%] Built target fstminimizeencoded
Consolidate compiler generated dependencies of target fsttablecompose
[ 67%] Built target fsttablecompose
Consolidate compiler generated dependencies of target decoder
[ 74%] Built target decoder
Consolidate compiler generated dependencies of target wenet_api
[ 75%] Linking CXX shared library libwenet_api.so
/usr/bin/ld: 找不到 -lmkl_intel_ilp64
/usr/bin/ld: 找不到 -lmkl_core
/usr/bin/ld: 找不到 -lmkl_intel_thread
collect2: error: ld returned 1 exit status
api/CMakeFiles/wenet_api.dir/build.make:118: recipe for target 'api/libwenet_api.so' failed
make[2]: *** [api/libwenet_api.so] Error 1
CMakeFiles/Makefile2:2012: recipe for target 'api/CMakeFiles/wenet_api.dir/all' failed
make[1]: *** [api/CMakeFiles/wenet_api.dir/all] Error 2
Makefile:155: recipe for target 'all' failed
make: *** [all] Error 2

see http://linuxtoolkit.blogspot.com/2012/02/ld-cannot-find-lmklintelilp64a.html

authors: Rita-ritally xingchensong


text:
Is there a pretrained checkponit to use?

Is there a pretrained checkponit to use?

@bjmajic As #1 mentioned, there are no available checkpoints to use now. Sorry!

I am going to close this issue. Please feel free to reopen or create a new one if you have more questions.

authors: bjmajic wenwenyu

repo: wenwenyu/PICK-pytorch


text:
Documentation issue: wrong return type of PublicSuffix::List.parse

The documentation for PublicSuffix::List.parse states that it returns Array<PublicSuffix::Rule::*> instances, but it actually returns a single PublicSuffix::List instance.

Thanks.

authors: mwpastore weppos

repo: weppos/publicsuffix-ruby


text:
chore: release 1.1.150

:robot: I have created a release *beep* *boop*
1.1.150 (2022-08-04)
Miscellaneous Chores

release 1.1.150 (6eef236)

This PR was generated with Release Please. See documentation.

test

authors: alexey-igrychev flant-team-sysdev

repo: werf/werf


text:
npm start - TypeError: Cannot read properties of undefined (reading 'layout')

Followed the documentation (clone, npm install, npm start) and didn't touch any files, but when I get to the npm start command, it fails.
I'm running Windows 11 and Nodejs 18.12.1 if that helps. Netlify deploys the site just fine, I have not been able to run it locally.
I've pasted the full output below.
PS D:\Code\my-site> npm start

> metalsmith-netlify-cms-starter@0.0.1 start
> cross-env NODE_ENV=development NODE_PATH=./node_modules npm run watch & npm run serve

> metalsmith-netlify-cms-starter@0.0.1 watch
> nodemon metalsmith.js

[nodemon] 2.0.20
[nodemon] to restart at any time, enter `rs`
[nodemon] watching path(s): src\**\* templates
[nodemon] watching extensions: js,css,scss,njk,json,html,md
[nodemon] starting `node metalsmith.js`
D:\Code\my-site\node_modules\@metalsmith\layouts\lib\index.cjs:53
  if (file.layout || file.layout === false) {
           ^

TypeError: Cannot read properties of undefined (reading 'layout')
    at getLayout (D:\Code\my-site\node_modules\@metalsmith\layouts\lib\index.cjs:53:12)
    at validate (D:\Code\my-site\node_modules\@metalsmith\layouts\lib\index.cjs:108:18)
    at D:\Code\my-site\node_modules\@metalsmith\layouts\lib\index.cjs:168:56
    at Array.filter (<anonymous>)
    at Ware.layouts (D:\Code\my-site\node_modules\@metalsmith\layouts\lib\index.cjs:168:37)
    at Ware.<anonymous> (D:\Code\my-site\node_modules\wrap-fn\index.js:45:19)
    at Immediate.next (D:\Code\my-site\node_modules\ware\lib\index.js:85:20)
    at Immediate.<anonymous> (D:\Code\my-site\node_modules\wrap-fn\index.js:121:18)
    at process.processImmediate (node:internal/timers:471:21)

Node.js v18.12.1
[nodemon] app crashed - waiting for file changes before starting...

I have not used node 18 yet. I am using 16.17.1 on a Mac. I can't upgrade right now, so you'll have to try to use v16.

I am checking with the Metalsmith maintainer if there are any known issues with node 18. Will let you know

I've also tried node 16 w/ npm 8.15.0, same error, unfortunately.

This looks like an error by the @metalsmith/layouts plugin. I'll be checking with the Metalsmith maintainer. He is in Europe so I'll not be hearing from him until tomorrow.

There is an issue with the permalink plugin that impacts windows. In metalsmith.js add the following option: .use(permalinks({relative: false})) that should do it. I have also updated the repo.

Experiencing a different issue now: when running npm start, it skips running npm run serve. Everything works fine on a chromebook running linux, but not on my windows machine. Pasted the output below.
PS D:\Code\metalsmith-netlify-starter> npm start

> metalsmith-netlify-cms-starter@0.0.2 start
> cross-env NODE_ENV=development NODE_PATH=./node_modules npm run watch & npm run serve

> metalsmith-netlify-cms-starter@0.0.2 watch
> nodemon metalsmith.js

[nodemon] 2.0.20
[nodemon] to restart at any time, enter `rs`
[nodemon] watching path(s): src\**\* templates
[nodemon] watching extensions: js,css,scss,njk,json,html,md
[nodemon] starting `node metalsmith.js`
[nodemon] clean exit - waiting for changes before restart

authors: eaaasun wernerglinka

repo: wernerglinka/metalsmith-netlify-starter


text:
Modularize the visibility filter, content filter, action, and archive options

Hi,
If you could modularize along the following lines:

visibility filter=default is "non-hidden" (to optimise processing), can be set to "all" messages

content filter=default is "none" , can be set to "match keyword"

Pattern matching can be done by appending to the facebook url activity log itself (and thereby making facebook do the heavy lifting on the server side).
Inverting the keyword match, Matching a pattern, Inverting the pattern match can be stretch goals

action=default is "hide" (non-destructive default but still private and inaccessible), can be set to "delete"

archive=default is "save" the fsm div to JSON whose filename is set to the original timestamp , can be set to "don't save"

then users can choose a variety of actions. e.g.

Users can now feed a list of keywords to hide for e.g. travelling to China ? hide/delete your "Tibet" and "Hong Kong" posts.
Users can make all posts about a specific trip private and inaccessible, while leaving the rest of their facebook content accessible

Thanks, I'll think about this and see what I can do

authors: rshetye weskerfoot

repo: weskerfoot/DeleteFB


text:
Update zerowaste to 0.2.22

About this PR
📦 Updates com.github.ghik:zerowaste from 0.2.1 to 0.2.22
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

🔍 Files still referring to the old version number
The following files still refer to the old version number (0.2.1).
You might want to review and update them manually.
website/yarn.lock

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.github.ghik", artifactId = "zerowaste" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.github.ghik", artifactId = "zerowaste" }
}]

labels: library-update, early-semver-minor, semver-spec-patch, old-version-remains, commit-count:1

Superseded by #589.

repo: weso/shex-s


text:
Update circe-core, circe-generic, ... to 0.14.8

About this PR
📦 Updates

io.circe:circe-core
io.circe:circe-generic
io.circe:circe-parser

from 0.14.2 to 0.14.8
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

🔍 Files still referring to the old version number
The following files still refer to the old version number (0.14.2).
You might want to review and update them manually.
project/plugins.sbt

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.circe" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "io.circe" }
}]

labels: library-update, early-semver-minor, semver-spec-patch, version-scheme:early-semver, old-version-remains, commit-count:1

Superseded by #408.

repo: weso/srdf