text:
TestRunShutdownHook failed if no ZafiraListener registered

2020-04-27 21:22:01 CucumberRunner [main-1] [INFO] Report json: cucumber-json-report.json
ERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the console.
2020-04-27 21:22:06 Messager [main-1] [INFO] INFO: '**************** Test execution summary ****************'.
2020-04-27 21:22:06 Messager [main-1] [INFO] RESULT #1: TEST [Grip - feature] PASS
...
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 153.306 s - in TestSuite
2020-04-27 21:22:09 com.qaprosoft.zafira.listener.ZafiraEventRegistrar$TestRunShutdownHook [Thread-4] [INFO]: TestRunShutdownHook was executed with result: true
log4j:ERROR null
java.util.concurrent.TimeoutException
at com.rabbitmq.utility.BlockingCell.get(BlockingCell.java:77)
at com.rabbitmq.utility.BlockingCell.uninterruptibleGet(BlockingCell.java:120)
at com.rabbitmq.utility.BlockingValueOrException.uninterruptibleGetValue(BlockingValueOrException.java:36)
at com.rabbitmq.client.impl.AMQChannel$BlockingRpcContinuation.getReply(AMQChannel.java:502)
at com.rabbitmq.client.impl.ChannelN.close(ChannelN.java:622)
at com.rabbitmq.client.impl.ChannelN.close(ChannelN.java:547)
at com.rabbitmq.client.impl.ChannelN.close(ChannelN.java:540)
at com.rabbitmq.client.impl.recovery.AutorecoveringChannel.close(AutorecoveringChannel.java:73)
at com.qaprosoft.zafira.log.event.impl.RabbitMQService.releaseConnection(RabbitMQService.java:81)
at com.qaprosoft.zafira.log.impl.LogAppenderServiceImpl.onClose(LogAppenderServiceImpl.java:87)
at com.qaprosoft.zafira.log.log4j.LogAppender.onShutdownHook(LogAppender.java:80)
at java.lang.Thread.run(Thread.java:748)
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0

with enabled ZafiraListener a little bit different exception:
Exception in thread "Thread-2" com.rabbitmq.client.AlreadyClosedException: channel is already closed due to clean channel shutdown; protocol method: #method<channel.close>(reply-code=200, reply-text=OK, class-id=0, method-id=0)
at com.rabbitmq.client.impl.AMQChannel.processShutdownSignal(AMQChannel.java:401)
at com.rabbitmq.client.impl.ChannelN.startProcessShutdownSignal(ChannelN.java:292)
at com.rabbitmq.client.impl.ChannelN.close(ChannelN.java:613)
at com.rabbitmq.client.impl.ChannelN.close(ChannelN.java:547)
at com.rabbitmq.client.impl.ChannelN.close(ChannelN.java:540)
at com.rabbitmq.client.impl.recovery.AutorecoveringChannel.close(AutorecoveringChannel.java:73)
at com.qaprosoft.zafira.log.event.impl.RabbitMQService.releaseConnection(RabbitMQService.java:81)
at com.qaprosoft.zafira.log.impl.LogAppenderServiceImpl.onClose(LogAppenderServiceImpl.java:87)
at com.qaprosoft.zafira.log.log4j.LogAppender.onShutdownHook(LogAppender.java:80)
at java.lang.Thread.run(Thread.java:748)
Exception in thread "Thread-4" com.rabbitmq.client.ShutdownSignalException: clean channel shutdown; protocol method: #method<channel.close>(reply-code=200, reply-text=OK, class-id=0, method-id=0)
at com.rabbitmq.utility.ValueOrException.getValue(ValueOrException.java:66)
at com.rabbitmq.utility.BlockingValueOrException.uninterruptibleGetValue(BlockingValueOrException.java:36)
at com.rabbitmq.client.impl.AMQChannel$BlockingRpcContinuation.getReply(AMQChannel.java:502)
at com.rabbitmq.client.impl.ChannelN.close(ChannelN.java:622)
at com.rabbitmq.client.impl.ChannelN.close(ChannelN.java:547)
at com.rabbitmq.client.impl.ChannelN.close(ChannelN.java:540)
at com.rabbitmq.client.impl.recovery.AutorecoveringChannel.close(AutorecoveringChannel.java:73)
at com.qaprosoft.zafira.log.event.impl.RabbitMQService.releaseConnection(RabbitMQService.java:81)
at com.qaprosoft.zafira.log.impl.LogAppenderServiceImpl.onClose(LogAppenderServiceImpl.java:87)
at com.qaprosoft.zafira.util.upload.DirectAppender.onShutdownHook(DirectAppender.java:54)
at java.lang.Thread.run(Thread.java:748)
Caused by: com.rabbitmq.client.ShutdownSignalException: clean channel shutdown; protocol method: #method<channel.close>(reply-code=200, reply-text=OK, class-id=0, method-id=0)
at com.rabbitmq.client.impl.ChannelN.close(ChannelN.java:594)
at com.rabbitmq.client.impl.ChannelN.close(ChannelN.java:547)
at com.rabbitmq.client.impl.ChannelN.close(ChannelN.java:540)
at com.rabbitmq.client.impl.recovery.AutorecoveringChannel.close(AutorecoveringChannel.java:73)
at com.qaprosoft.zafira.log.event.impl.RabbitMQService.releaseConnection(RabbitMQService.java:81)
at com.qaprosoft.zafira.log.impl.LogAppenderServiceImpl.onClose(LogAppenderServiceImpl.java:87)
at com.qaprosoft.zafira.log.log4j.LogAppender.onShutdownHook(LogAppender.java:80)
... 1 more

closing as won't fix because new generation of agents don't have direct connection with rabbitmq anymore

repo: zebrunner/zebrunner


text:
add support for opam

Which locally it is fairly easy to start zed with the right environment using opam exec -- zed and have ocamllsp properly detected, this technique doesn't work with remote projects. Supporting opam is a must.
Relevant code is probably:
https://github.com/zed-extensions/ocaml/blob/f03fd28794a003e8f266eeb91f1483e438b07f7d/src/ocaml.rs#L21-L31

actually the remote ssh mode doesn't support extensions yet. But it will be necessary later on.

source: gharchive/issue

repo: zed-extensions/ocaml

license_type: permissive

license_source: github-api


text:
Terminal mouse selections sometimes incorrectly omit the first clicked character

Check for existing issues

[X] Completed

Describe the bug
Sometimes, when clicking and dragging to select text in the terminal, the first character that I'm trying to select is incorrectly excluded from the selection.
To reproduce

Click and start dragging with the mouse in the middle of a character, but toward the left edge.
Drag the mouse to the right to select some text
:boom: The first character isn't selected, even though the drag started near the left edge of that character

Expected behavior
If the drag started on the left half of a character, that character should be included in the selection
Environment
Zed 0.54.1 – /Applications/Zed.app
macOS 12.4
architecture arm64
If applicable, add mockups / screenshots to help explain present your vision of the feature
No response
If applicable, attach your ~/Library/Logs/Zed/Zed.log file to this issue
No response

I'm really struggling with this, it's quite annoying. Sometimes the selection grabs one more character, or sometimes it skips one. And then it also seems to be flaky when I release the mouse. Combined with the fact that I can't "double-click first word" + Shift + "double-click last word" to select text, it makes for a very frustrating experience.
https://user-images.githubusercontent.com/1189716/228391685-144985e8-8f16-40e1-9f76-c16be69c7006.mov

I believe this issue may have been fixed, I can't seem to reproduce it on our latest distributed build. Please comment if this is observed again.

I just tried with 0.82.8 and the behavior remains.

Ahh, I see the issue now. Sorry for the false hope :)

This has now been fixed and will be available in a few weeks. Once a drag has been initiated the character under cursor should always be included.

After some experimentation, this seems to match behavior internal to the version of alacritty that we're using:
https://user-images.githubusercontent.com/2280405/233751897-0e8ad596-245e-412c-9958-1b066ff52271.mov
And therefore will not be fixed for a while.

I use Alacritty as a standalone terminal and don't see the same behavior. I tried with today's latest version of Zed and the problem persist.

authors: aybabtme maxbrunsfeld mikayla-maki

repo: zed-industries/community

license: MIT


text:
bugfix and AreCollectionNotEmpty

Changes

bugfix AreCollectionEmpty
add AreCollectionNotEmpty

Methodic checks

[x] Multiple time zones was checked.
[x] Data updates do not spoil data.
[x] Each borrowed code was checked for compliance with the license of this library and added to LICENSE.NOTICE.

Manual codebase checks

[x] 4 spaces per indentation level.
[x] Messages and synonyms have English and Russian localization.
[ ] Methods descriptions of public interface.
[x] Code comments are clear and don't have mistakes.
[x] Variable naming convention is not broken.
[ ] Form modules don't contain public interface.
[ ] Command modules don't have export methods.
[ ] Modify Data property setted for commands that changes the data.
[ ] Metadata standard attributes names for Parent and Owner have synonyms.
[ ] Roles rights don't contain dangerous actions.

User mode checks

[x] Interface style guide is fully compatible to #std (RU).

Thank you

source: gharchive/pull-request

authors: astrizhachuk zeegin

repo: zeegin/OpenSubsystemsLibrary


text:
Resolves issue #147 At-will spells not appearing in Spellcasting text

This resolves #147.
I've updated isSpellcaster(), isInnateSpellcaster(), isWarlock() and hasAtWillSpells() to all reference item.data.data.preparation.mode instead of item.data.preparation.mode.
The first three methods do not appear to be used anywhere, but I wanted to update the methods anyway as item.data.preparation will always be null.

It looks like those all got factored out when I created CastingPreper and unified the spellcasting feature handling. I've removed them. I'm somewhat unsure if I should leave hasAtWillSpells where it is, or move it to CastingPreper. I guess I'l leave it for now.


text:
TypeScript compilation with --no-babel

I am trying the sleep.js example with TypeScript and avoid Babel Transpilation since TypeScript performs Transpilation.
The output I get from TypeScript is the following:
var __awaiter = (this && this.__awaiter) || function (thisArg, _arguments, Promise, generator) {
    return new Promise(function (resolve, reject) {
        generator = generator.call(thisArg, _arguments);
        function cast(value) { return value instanceof Promise && value.constructor === Promise ? value : new Promise(function (resolve) { resolve(value); }); }
        function onfulfill(value) { try { step("next", value); } catch (e) { reject(e); } }
        function onreject(value) { try { step("throw", value); } catch (e) { reject(e); } }
        function step(verb, value) {
            var result = generator[verb](value);
            result.done ? resolve(result.value) : cast(result.value).then(onfulfill, onreject);
        }
        step("next", void 0);
    });
};
var micro_1 = require('micro');
var then_sleep_1 = require('then-sleep');
exports.default = function (req, res) {
    return __awaiter(this, void 0, Promise, function* () {
        yield then_sleep_1.default(500);
        micro_1.send(res, 200, 'Ready!');
    });
};

It appears to start fine however visiting localhost:3000 has the following error
TypeError: then_sleep_1.default is not a function

I suspect this might require changes to then-sleep module however it would be nice to see how the same example without the async/await.
What is the expected ES6 code (without async/await) for this sleep example?

Are you running it with the --no-babel flag?

@rauchg Correct I am running with --no-babel as the title says. I'm not entirely convinced that it is avoiding babel because startup time is still 1 or 2 seconds.
https://github.com/styfle/micro-ts-example/blob/master/package.json

I believe the problem comes from the fact that all of the babel modules (except babel-register) get imported unconditionally.
:+1: for fixing this because at the moment I'm not using micro CLI, partly because of this startup time issue.

You can use micro without the CLI this way:
import micro from 'micro';

async function requestHandler(req, res) { ... }

micro(requestHandler).listen(process.env.PORT || 3000);

I don't know TS, but basically, the idea is that if you import micro you can use it to create a HTTP server passing your requestHandler (your function) as an argument and then using .listen(port).
This way you can just run node index.js, of course, you should need to transpile your code from ES* or TS to JS.
You can read about it in the docs.

@sergiodxa I think this is really the correct solution. Thanks!
Here is the same thing in typescript:
import * as micro from 'micro';
import {IncomingMessage, ServerResponse} from 'http';

async function requestHandler(req: IncomingMessage, res: ServerResponse) {
    res.writeHead(200);
    res.end('hello world');
}

micro(requestHandler).listen(process.env.PORT || 3000);

Moving forward, we're making micro-serve(1) take the exported file that's been pre-compiled, which should be much better for production.

authors: TooTallNate rauchg sergiodxa styfle

repo: zeit/micro

license: mit

license_source: bigquery


text:
"" in _document.js doesn't do client-side transitions

First: thanks for this guys, this is awesome.
Second: It seems any React onClick-event handlers aren't installed client-side when given via the _document.js-file. This way, for example Link.onClick isn't fired for elements in the _document.js. Or in nested elements, e.g. in a menu on all pages...
This may be expected behaviour, but it took me a while to figure out why all <Link>'s would initiate a server-side transition.

The custom document is not meant to contain <Link>s, but e.g to customize the  and .

But i think its tempting to add something like a menu if that should be on all pages...
Maybe add a warning to the documentation?

Yes, I think a pull request to clarify that could be helpful. _document.js isn't meant to serve as a shared app layout. You can get that behaviour by wrapping each page in a HOC e.g like https://github.com/relatenow/relate/blob/master/hocs/page.js.

Thanks @sedubois for helping out.
Yeah! Having something in the docs would be nice.
It'd be great, if you can send us a PR.

authors: Reggino arunoda sedubois


text:
[Bug next 7] React bundled in development mode

Bug report
Describe the bug
Since moving react and react-dom to AutoDLLPlugin, there's no more React user timings showing up in the devtool performance panel.
This seems to be be lost because react is then always bundled in production mode. I've check that the process.env.NODE_ENV = development during the build process and runtime; but somehow it must be overriden when the AutoDLL initial build occur.
To Reproduce

Profile a Next.js app with the chrome devtool performance panel
After stopping the profiling, there won't be any user timings showing up.

Expected behavior
React should be bundled in development mode so we get access to the deprecation warnings and performance tracking tools.
System information

Version of Next.js: 7-canary.1

I noticed this yesterday and fixed it already, but was working on another bugfix so couldn't PR it yet. Just opened the PR 👍

authors: SBoudrias timneutkens


text:
Added asPath for dynamic router support

For dynamic router support, because pathname maybe static ['entity']

Stats from current PR

Default Server Mode

General

zeit/next.js canary
Baukaalm/next.js patch-2
Change

buildDuration
14.8s
14.6s
-219ms

nodeModulesSize
48.2 MB
48.2 MB
✓

Client Bundles (main, webpack, commons)

zeit/next.js canary
Baukaalm/next.js patch-2
Change

main-HASH.js
18.3 kB
18.3 kB
✓

main-HASH.js gzip
6.64 kB
6.64 kB
✓

webpack-HASH.js
1.53 kB
1.53 kB
✓

webpack-HASH.js gzip
746 B
746 B
✓

4952ddcd88e7..2b8407376.js
21.9 kB
21.9 kB
✓

4952ddcd88e7..7376.js gzip
7.81 kB
7.81 kB
✓

de003c3a9d30..2ca0edb75.js
43.2 kB
43.2 kB
✓

de003c3a9d30..db75.js gzip
15.5 kB
15.5 kB
✓

framework.5b..dbaff70d3.js
125 kB
125 kB
✓

framework.5b..70d3.js gzip
39.4 kB
39.4 kB
✓

Overall change
210 kB
210 kB
✓

Client Bundles (main, webpack, commons) Modern

zeit/next.js canary
Baukaalm/next.js patch-2
Change

main-HASH.module.js
16.5 kB
16.5 kB
✓

main-HASH.module.js gzip
6.39 kB
6.39 kB
✓

webpack-HASH.module.js
1.53 kB
1.53 kB
✓

webpack-HASH..dule.js gzip
746 B
746 B
✓

de003c3a9d30..c0.module.js
45.6 kB
45.6 kB
✓

de003c3a9d30..dule.js gzip
16.5 kB
16.5 kB
✓

framework.5b..d3.module.js
125 kB
125 kB
✓

framework.5b..dule.js gzip
39.4 kB
39.4 kB
✓

Overall change
189 kB
189 kB
✓

Client Pages

zeit/next.js canary
Baukaalm/next.js patch-2
Change

_app.js
1.81 kB
1.81 kB
✓

_app.js gzip
873 B
873 B
✓

_error.js
12 kB
12 kB
✓

_error.js gzip
4.73 kB
4.73 kB
✓

hooks.js
12.7 kB
12.7 kB
✓

hooks.js gzip
4.79 kB
4.79 kB
✓

index.js
318 B
318 B
✓

index.js gzip
222 B
222 B
✓

link.js
8.14 kB
8.14 kB
✓

link.js gzip
3.5 kB
3.5 kB
✓

routerDirect.js
408 B
408 B
✓

routerDirect.js gzip
281 B
281 B
✓

withRouter.js
419 B
419 B
✓

withRouter.js gzip
280 B
280 B
✓

Overall change
35.8 kB
35.8 kB
✓

Client Pages Modern

zeit/next.js canary
Baukaalm/next.js patch-2
Change

_app.module.js
1.7 kB
1.7 kB
✓

_app.module.js gzip
832 B
832 B
✓

_error.module.js
23.3 kB
23.3 kB
✓

_error.module.js gzip
8.59 kB
8.59 kB
✓

hooks.module.js
1.52 kB
1.52 kB
✓

hooks.module.js gzip
793 B
793 B
✓

index.module.js
294 B
294 B
✓

index.module.js gzip
223 B
223 B
✓

link.module.js
8.53 kB
8.53 kB
✓

link.module.js gzip
3.68 kB
3.68 kB
✓

routerDirect.module.js
394 B
394 B
✓

routerDirect..dule.js gzip
281 B
281 B
✓

withRouter.module.js
404 B
404 B
✓

withRouter.m..dule.js gzip
278 B
278 B
✓

Overall change
36.1 kB
36.1 kB
✓

Client Build Manifests

zeit/next.js canary
Baukaalm/next.js patch-2
Change

_buildManifest.js
81 B
81 B
✓

_buildManifest.js gzip
61 B
61 B
✓

_buildManifest.module.js
81 B
81 B
✓

_buildManife..dule.js gzip
61 B
61 B
✓

Overall change
162 B
162 B
✓

Rendered Page Sizes

zeit/next.js canary
Baukaalm/next.js patch-2
Change

index.html
3.62 kB
3.62 kB
✓

index.html gzip
947 B
947 B
✓

link.html
3.66 kB
3.66 kB
✓

link.html gzip
955 B
955 B
✓

withRouter.html
3.67 kB
3.67 kB
✓

withRouter.html gzip
943 B
943 B
✓

Overall change
10.9 kB
10.9 kB
✓

Serverless Mode

General

zeit/next.js canary
Baukaalm/next.js patch-2
Change

buildDuration
15.8s
15.2s
-601ms

nodeModulesSize
48.2 MB
48.2 MB
✓

Client Bundles (main, webpack, commons)

zeit/next.js canary
Baukaalm/next.js patch-2
Change

main-HASH.js
18.3 kB
18.3 kB
✓

main-HASH.js gzip
6.64 kB
6.64 kB
✓

webpack-HASH.js
1.53 kB
1.53 kB
✓

webpack-HASH.js gzip
746 B
746 B
✓

4952ddcd88e7..2b8407376.js
21.9 kB
21.9 kB
✓

4952ddcd88e7..7376.js gzip
7.81 kB
7.81 kB
✓

de003c3a9d30..2ca0edb75.js
43.2 kB
43.2 kB
✓

de003c3a9d30..db75.js gzip
15.5 kB
15.5 kB
✓

framework.5b..dbaff70d3.js
125 kB
125 kB
✓

framework.5b..70d3.js gzip
39.4 kB
39.4 kB
✓

Overall change
210 kB
210 kB
✓

Client Bundles (main, webpack, commons) Modern

zeit/next.js canary
Baukaalm/next.js patch-2
Change

main-HASH.module.js
16.5 kB
16.5 kB
✓

main-HASH.module.js gzip
6.39 kB
6.39 kB
✓

webpack-HASH.module.js
1.53 kB
1.53 kB
✓

webpack-HASH..dule.js gzip
746 B
746 B
✓

de003c3a9d30..c0.module.js
45.6 kB
45.6 kB
✓

de003c3a9d30..dule.js gzip
16.5 kB
16.5 kB
✓

framework.5b..d3.module.js
125 kB
125 kB
✓

framework.5b..dule.js gzip
39.4 kB
39.4 kB
✓

Overall change
189 kB
189 kB
✓

Client Pages

zeit/next.js canary
Baukaalm/next.js patch-2
Change

_app.js
1.81 kB
1.81 kB
✓

_app.js gzip
873 B
873 B
✓

_error.js
12 kB
12 kB
✓

_error.js gzip
4.73 kB
4.73 kB
✓

hooks.js
12.7 kB
12.7 kB
✓

hooks.js gzip
4.79 kB
4.79 kB
✓

index.js
318 B
318 B
✓

index.js gzip
222 B
222 B
✓

link.js
8.14 kB
8.14 kB
✓

link.js gzip
3.5 kB
3.5 kB
✓

routerDirect.js
408 B
408 B
✓

routerDirect.js gzip
281 B
281 B
✓

withRouter.js
419 B
419 B
✓

withRouter.js gzip
280 B
280 B
✓

Overall change
35.8 kB
35.8 kB
✓

Client Pages Modern

zeit/next.js canary
Baukaalm/next.js patch-2
Change

_app.module.js
1.7 kB
1.7 kB
✓

_app.module.js gzip
832 B
832 B
✓

_error.module.js
23.3 kB
23.3 kB
✓

_error.module.js gzip
8.59 kB
8.59 kB
✓

hooks.module.js
1.52 kB
1.52 kB
✓

hooks.module.js gzip
793 B
793 B
✓

index.module.js
294 B
294 B
✓

index.module.js gzip
223 B
223 B
✓

link.module.js
8.53 kB
8.53 kB
✓

link.module.js gzip
3.68 kB
3.68 kB
✓

routerDirect.module.js
394 B
394 B
✓

routerDirect..dule.js gzip
281 B
281 B
✓

withRouter.module.js
404 B
404 B
✓

withRouter.m..dule.js gzip
278 B
278 B
✓

Overall change
36.1 kB
36.1 kB
✓

Client Build Manifests

zeit/next.js canary
Baukaalm/next.js patch-2
Change

_buildManifest.js
81 B
81 B
✓

_buildManifest.js gzip
61 B
61 B
✓

_buildManifest.module.js
81 B
81 B
✓

_buildManife..dule.js gzip
61 B
61 B
✓

Overall change
162 B
162 B
✓

Serverless bundles

zeit/next.js canary
Baukaalm/next.js patch-2
Change

_error.js
253 kB
253 kB
✓

_error.js gzip
67.6 kB
67.6 kB
✓

hooks.html
3.75 kB
3.75 kB
✓

hooks.html gzip
980 B
980 B
✓

index.js
253 kB
253 kB
✓

index.js gzip
68 kB
68 kB
✓

link.js
261 kB
261 kB
✓

link.js gzip
70 kB
70 kB
✓

routerDirect.js
254 kB
254 kB
✓

routerDirect.js gzip
68 kB
68 kB
✓

withRouter.js
254 kB
254 kB
✓

withRouter.js gzip
68.1 kB
68.1 kB
✓

Overall change
1.28 MB
1.28 MB
✓

Commit: c2a2c64f91af41d30f372fd010b4c64d55681c84

authors: Baukaalm ijjk


text:
now --docker hitting lstat error

ETA:

now version 4.0.1
node 7.1.0
docker version 1.13.0
ubuntu 16.10

My project has compiled src in ./dist. I build a docker to run it w/ pm2 w/ this Dockerfile:
FROM node:7-alpine
# add git so we can add npm packages from repos
RUN apk update && apk upgrade && \
    apk add --no-cache bash git openssh

# create dir and copy relevant files
RUN mkdir -p /usr/src/app

COPY ./index.js /usr/src/app/
COPY ./package.json /usr/src/app/
COPY dist usr/src/app/dist

WORKDIR /usr/src/app

RUN npm install --production
RUN npm install pm2 -g
EXPOSE 8080

CMD ["pm2-docker", "index.js"]

This Dockerfile works with now in another of my projects (or did, the last time i tried it last month), and it builds fine with regular docker build ..
However, when running now --docker in the project root (where the Dockerfile is), I'm hitting a loop in the build process with repeated errors of lstat dist: no such file or directory. Here's a sample:
>  ---> Using cache
> Step 4 : RUN mkdir -p /usr/src/app/dist
>  ---> Running in ea73b512a4bd
>  ---> 05fee9b99a01
> Removing intermediate container ea73b512a4bd
> Step 5 : COPY ./index.js /usr/src/app/
>  ---> 334750f94400
> Removing intermediate container 5f5967a6b719
> Step 6 : COPY ./package.json /usr/src/app/
> Step 7 : COPY dist usr/src/app/dist/
> lstat dist: no such file or directory
>  ---> c726069ecc8b
> Removing intermediate container 5d9831a66cf9
> ▲ Storing image
> ▲ docker build
Sending build context to Docker daemon   215 kBkB
> lstat dist: no such file or directory
> Step 4 : RUN mkdir -p /usr/src/app/dist
>  ---> Using cache
>  ---> 05fee9b99a01
> Step 5 : COPY ./index.js /usr/src/app/
>  ---> Using cache
>  ---> 334750f94400
> Step 6 : COPY ./package.json /usr/src/app/
>  ---> Using cache
>  ---> c726069ecc8b
> Step 7 : COPY dist usr/src/app/dist/
> ▲ Storing image

Any tips? Googled the issue, and none of the fixes apply (I have no .dockerignore, and the dist folder is in the Dockerfile's context)

Try running now with the -d flag to see which files it ignores. IIRC it uses .gitignore and possibly .npmignore in addition to always ignoring files like .git and node_modules

I am having exactly same issues here.

The lstat basically means that the file it tries to ADD/COPY is not anywhere to be found.
So it's probably not being pushed to now when deploying.
now -d should show which files it uploads/ignores

^

@jamo I do not see any files. Here is the output.
$ now --docker -d -f
> Deploying ~/Work/Development/app
> [debug] Forcing `deploymentType` = `docker`
> [debug] locating files /Users/gunjansoni/Work/Development/app 31.444ms
> [debug] Getting files: 37.441ms
> [debug] Computing hashes: 29.742ms
> [debug] /now/create: 4974.676ms
> Ready! https://<someurl>.now.sh (copied to clipboard) [5s]
> Initializing…
> [debug] closing agent
> Building
> ▲ docker build
> Status: Downloaded newer image for ubuntu:latest
> 2508cbcde94b: Pull complete

authors: brandonmp guns2410 jamo leo

repo: zeit/now-cli


text:
[now-build-utils] Fix now dev to use system node

This PR will use the system installed version of Node.js and avoid printing a warning or error if a discontinued version is selected.
This optimization was already in @now/node but for some reason it was never add to @now/next.
The reason why its relevant today is because the warnings turned into errors due to Node 8 deprecation and we don't have the "Project" in now dev so we don't know which version of node to select.
So instead of determining the version, now dev will always use node in the PATH and avoid printing warnings or errors. This also results in less FS reads since we no longer need to read package.json.

Force merging to get now dev tests working again

repo: zeit/now


text:
How to use goji.ServeTLS()

I'm baffled at how to use the goji.ServeTLS
i see what it says about a config but i don't c what format the config needs to be in or what is expected vs optional etc

Hey @kitsushadow— have you had a look at the documentation for tls.Config (https://godoc.org/crypto/tls#Config)? If the documentation isn't helpful, I'd search around the internet for guides—it's a standard type and should have plenty of tutorials

authors: kitsushadow zenazn

repo: zenazn/goji


text:
Remove stdlib dependency

Hi,
This is a similar issue with https://github.com/mtymek/expressive-config-manager/issues/9.
I'm having various issues currently with conflicting versions, as Stdlib includes too much code, has dependency to unrelated stuff (mainly hydrator), which poses some issue for nothing.
I'd suggest that this package adds a trait "ArrayMergeTrait", that uses the code from the merge method in Stdlib, so dependency to Stdlib can be removed from all templates project.
I can do the PR if you want.

@bakura10 That would be fine. However, there are some details in the ArrayUtils::merge() functionality that are not easily ported: two interfaces exist to allow configuration writers to signal what behavior to implement when merging specific values (replace/remove, respectively), and having multiple ways to signal that information between components will quickly lead to issues. You can see these problems in zendframework/zend-servicemanager#68.
Ideally, any pull request you do follows the approach from that pull request, once it's finalized.

We inlined the logic some time ago... and it's now removed entire, so I'm closing this.

repo: zendframework/zend-expressive-template


text:
Add cookbook entry for accessing common data in templates

As the title says: It adds a cookbook entry for accessing common data in templates.

[x] Are you creating a new feature?

[x] Why is the new feature needed? What purpose does it serve?
[x] How will users use the new feature?
[x] Add only one feature per pull request; split multiple features over multiple pull requests
[x] Add documentation for the new feature.
[x] Add a CHANGELOG.md entry for the new feature.

Thanks, @xtreamwayz!

authors: weierophinney xtreamwayz

repo: zendframework/zend-expressive


text:
Is this project dead?

...no updates for months...

...no updates for months...

Doesn't mean dead :-)
Most libraries nowadays rely on the PSR-7 standard, so there is no interest/traction in adding features to this API. zend-diactoros is our own PSR-7 implementation.

I consider a project with unanswered pull requests and issues a dead project...

@mlocati be my guest in answering issues and pull request from 4 years ago on many of my (personal stuff, not just zf) actively maintained projects :-)

That means that you don't have time to give feedback to requests to zend-http?

Yes, and I generally answer things as they come up in my inbox.
If I skip something, it's just because I wasn't working on it at that time,
and then it gets archived when I clean up my inbox.
Also, most contributors only work on this when they have free time, at the
end of the day or before going to work.
Marco Pivetta
http://twitter.com/Ocramius
http://ocramius.github.com/
On Thu, Jan 12, 2017 at 6:12 PM, Michele Locati notifications@github.com
wrote:

That means that you don't have time to give feedback to requests to
zend-http?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/zendframework/zend-http/issues/104#issuecomment-272223151,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJakCexKRKMZbljj8ZE8aBUutfoqzU8ks5rRl8ZgaJpZM4Lh-Vo
.

authors: Ocramius mlocati

repo: zendframework/zend-http


text:
Run performance tests against vanilla Postgres too for comparison

First attempt here: https://github.com/zenithdb/zenith/pull/523. But need to make it less tedious to write the baseline Postgres tests, and present the results side-by-side.

pgbench -c 10 -N  -s 1000 results:
zenith@notebook: 5k TPS
zenith@ec2 storage node: 8k TPS
vanilla@ec2 storage node: 25k TPS

Here are the current results, running release build on my laptop with shared_buffers=1MB.
| test                                     | zenith (sec) | vanillla (sec) | zenith/vanilla |
| test_bulk_insert.insert                  |       18.175 |          6.293 |           2.89 |
| test_copy.delete                         |        3.657 |          1.348 |           2.71 |
| test_small_seqscans.run                  |       18.786 |         10.724 |           1.75 |
| test_write_amplification.run             |       18.913 |         11.034 |           1.71 |
| test_pgbench.init                        |        3.274 |           2.56 |           1.28 |
| test_gist_buffering_build.build          |       25.272 |           19.9 |           1.27 |
| test_copy.copy_reuse                     |        1.911 |          2.251 |           0.85 |
| test_copy.copy_extend                    |        2.023 |          2.393 |           0.85 |
| test_parallel_copy_same_table.load       |        25.88 |         47.353 |           0.55 |
| test_copy.vacuum                         |        0.911 |          1.732 |           0.53 |
| test_parallel_copy_different_tables.load |       18.432 |         37.379 |           0.49 |
| test_pgbench.5000_xacts                  |        4.533 |         20.536 |           0.22 |

I think more can be done here. Ideallly our perf tests should be an accurate representation of what's important to improve, so that we can easily compare the performance of different solutions, and prioritize our efforts well. Some next steps to get us there:

[ ] Choose a fair value of shared_buffers for each test
[ ] Plot this zenith/vanilla column in grafana (or here)
[ ] (out of scope for this issue) Write a bigger version of each test (same test, bigger parameters). The small version is useful as regression test in CI, while the big version is an accurate representation of real performance. We can run these big tests only when there's a need, or maybe when the small test suggests we would see a difference. Either way, persisting the parameters in the repo is valuable.

I did some more investigations of performance comparison of Zenith vs. Vanilla which can clarify bottlenecks and future directions for performance improvement. The results were produced at my notebook with SSD much slower than server SSD. I use configuration without safekeepers to exclude its disk IO.

Write performance.
I want to estimate maximal possible speed at which pageserver is able to write data.
GC and checkpointer are disabled. Autovacuum turned off. So pageserver is mostly scattering received WAL records

1.1 pgbench -i -s 1000
pgbench is using COPY for populating data which write FPI.
wal size: 19Gb
storage size: 14Gb
time: 114 sec
write speed: 125Mb/sec
CPU usage:
postgres: 100%
pageserver: ~30%
So looks like in this case performance is mostly limited by COPY processing or disk write speed.

1.2. create table t(pk bigint, val text default repeat(' ', 256));
insert into t (pk) values (generate_series(1,100000000));
   In this case large table (~30Gb logical size) is created using inserts.
   storage size: 35Gb
   time: 411 sec
   write speed: 83Mb/sec
   CPU usage:
        postgres: ~50%
        pageserver: ~70%
        write speed: 85Mb/sec

 So in this case speed is more limited by pageserver which has to do more processing.

1.3  The same as 1.2 but checkpointer is enabled. Insertion is completed even faster: 399 seconds, but checkpointer finish its work only after 17 minutes.
  time: 999 sec
  storage size: 66Gb
  write speed: 68Mb/sec

Read performance.
I am reading 't' table created above.  I have inserted loop through all relation pages in pageserver itself, to eliminate   roundtrip overhead. So I am measuring maximal possible speed of extracting pages by pageserver itself.

2.1. No image layers. With checkpointer disabled there are no image layers, so pageserver has to reconstruct each page using wal_redo postgres.
time: 220 sec
read speed: 160Mb/sec

2.2. With image layers
time: 29 sec

read speed: ~1Gb/sec

Vanilla
insertion time: 889 sec (488 with fsync=off)
read time (select count(*)):
sequential plan: 21 seconds
parallel plan: 15 seconds

So zenith without safekeeper and checkpointer is inserting data even faster than vanilla.
But in this case read speed is about 10 times slower than with materialized pages.
With image layers read speed is comparable with  Vanilla, which means that ideal prefetch/bulk-loading mechanism should
eliminate ~10x performance difference with vanilla. But it is possible only for seqscan (OLAP queries).

Here are the current results, running release build on my laptop with shared_buffers=1MB.
| test                                     | zenith (sec) | vanillla (sec) | zenith/vanilla |
| test_bulk_insert.insert                  |       18.175 |          6.293 |           2.89 |
| test_copy.delete                         |        3.657 |          1.348 |           2.71 |
| test_small_seqscans.run                  |       18.786 |         10.724 |           1.75 |
| test_write_amplification.run             |       18.913 |         11.034 |           1.71 |
| test_pgbench.init                        |        3.274 |           2.56 |           1.28 |
| test_gist_buffering_build.build          |       25.272 |           19.9 |           1.27 |
| test_copy.copy_reuse                     |        1.911 |          2.251 |           0.85 |
| test_copy.copy_extend                    |        2.023 |          2.393 |           0.85 |
| test_parallel_copy_same_table.load       |        25.88 |         47.353 |           0.55 |
| test_copy.vacuum                         |        0.911 |          1.732 |           0.53 |
| test_parallel_copy_different_tables.load |       18.432 |         37.379 |           0.49 |
| test_pgbench.5000_xacts                  |        4.533 |         20.536 |           0.22 |

I think more can be done here. Ideallly our perf tests should be an accurate representation of what's important to improve, so that we can easily compare the performance of different solutions, and prioritize our efforts well. Some next steps to get us there:
* [ ]  Choose a fair configuration of vanilla for each test. Make sure the lack of safekeepers in test setup doesn't give us advantage (pageserver doesn't fsync as often)

* [ ]  Plot this zenith/vanilla column in grafana (or [here](https://zenithdb.github.io/zenith-perf-data/))

* [x]  (out of scope for this issue) Write a bigger version of some tests (same test, bigger parameters). The small version is useful as regression test in CI, while the big version is an accurate representation of real performance. We can run these big tests only when there's a need, or maybe when the small test suggests we would see a difference. Either way, persisting the parameters in the repo is valuable.

Spilling the remaining tasks here https://github.com/zenithdb/zenith/issues/1299

authors: bojanserafimov hlinnaka knizhnik

repo: zenithdb/zenith


text:
[要望]helpの出し方に一貫性が無いので統一されていてほしい

概要
zennコマンド自体はhelpを出すのにzenn helpのようにハイフン無しのサブコマンドを利用するのに対し、サブコマンドはzenn <subcommand> --helpのようにハイフン有りのオプションになっており混乱してしまうので、統一された方法もしくは別のやり方が欲しいです。
提案
個人的にはzennコマンド自体も--helpを受け付けるようにする方法と、Goのツールチェーンの様にzenn help <subcommand>でサブコマンドのhelpが出る方法のどちらかでどうだろうかと思っています。

あ、仰る通りですね。「zennコマンド自体も--helpを受け付ける」ようにしようと思います。

repo: zenn-dev/zenn-editor


text:
Update label of GPT3.5 as worst to best in README.md

Changed GPT3.5, being labeled as "worst" to "best" performing model.

Description

References

Foo
Bar
Baz

Blocked by

NA
(or link to PRs)

Thank you!

authors: Pogayo neubig

repo: zeno-ml/zeno-build


text:
net: ICMPv4 echo reply packets do not use default values in the IP header

Describe the bug
The ICMPv4 echo reply packets are build by reusing the echo request packet, only changing a few fields of the IP header. This means some fields of the outbound packet are taken from the inboud packet instead of using the default values from the interface, and most notably the TTL, flags and fragment offset. It might be safer to create a new packet using net_ipv4_create() and icmpv4_create() and copying only the payload.
To Reproduce
Send an ICMP echo request packet with a given TTL different than 64 (the default value in Zephyr). See how the echo reply packet comes back with the same TTL (if on the same subnet or lower if it goes through a router). Use a different TTL and observe how the echo reply packet use that different TTL.
Expected behavior
The echo reply packet should use the default IP header values and not the one from the inbound packet.
Impact
Conformance issue. It also means that the IP header sent by the board for ICMPv4 packets can partially be controlled by the inbound packet. It might have security impacts.

It's because clone sets the same attributes to the cloned pkt as the original one.
It's just a matter to reset the ttl of the reply. Note that net_ipv4_create and net_icmpv4_create are used, it can work in both situation overwriting or not.
will send a patch, directly part of #12989

Thanks this commit indeed fixes the issue. Now I wonder why not just copy the payload to avoid this kind of issue, like it is already done for IPv6?

In IPv6 it made sens to avoid cloning due to the fact option headers should not be present in the reply. In icmpv4 it's all the same (beside the ip src/dst addr, the icmp type and the ttl obviously): using cloning was a little bit simpler. (one clone vs net_pkt_alloc_with_buffer + net_pkt_copy).
Ok a really tiny bit simpler :)

repo: zephyrproject-rtos/zephyr


text:
coverage: When enable coverage, some testcases need more time

Describe the bug
I am testting coverage on qemu_arc_em and nsim_em with sanitycheck. I found that when enable coverage, some testcases will timeout.

nsim_em:

tests/lib/heap_align/lib.heap_align FAILED: Timeout
tests/kernel/timer/timer_monotonic/kernel.timer.monotonic FAILED: Timeout
tests/crypto/mbedtls/crypto.mbedtls FAILED: Timeout
tests/kernel/lifo/lifo_usage/kernel.lifo.usage FAILED: Failed

The above 3 timeout failures will pass when use west,. But accoding to the console output, these testcases need more time to finish
For tests/kernel/lifo/lifo_usage/kernel.lifo.usage, if increase timeout (K_MSEC(timeout + 10)) , it will pass. For examples, K_MSEC(100).
https://github.com/zephyrproject-rtos/zephyr/blob/3dba8cc8509b1c52d5bebf6eafcf95c0eb8b2cbe/tests/kernel/lifo/lifo_usage/src/main.c#L328

qemu_arc_em:

ERROR   - qemu_arc_em               samples/portability/cmsis_rtos_v2/timer_synchronization/sample.portability.cmsis_rtos_v2.timer_synchronization FAILED: Exited with 1
ERROR   - qemu_arc_em               samples/scheduler/metairq_dispatch/sample.kernel.metairq_dispatch FAILED: Exited with 1
ERROR   - qemu_arc_em               samples/portability/cmsis_rtos_v1/timer_synchronization/sample.portability.cmsis_rtos_v1.timer_synchronization FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/portability/cmsis_rtos_v2/portability.cmsis_rtos_v2 FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/subsys/logging/log_immediate/logging.log_immediate FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/subsys/logging/log_immediate/logging.log_immediate.clean_output FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/posix/common/portability.posix.common        FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/posix/common/portability.posix.common.newlib FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/portability/cmsis_rtos_v1/portability.cmsis_rtos_v1 FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/kernel/workq/critical/kernel.workqueue       FAILED: Failed
ERROR   - qemu_arc_em               tests/kernel/workq/work_queue/kernel.workqueue     FAILED: Failed
ERROR   - qemu_arc_em               tests/kernel/workq/work_queue_api/kernel.workqueue.api FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/kernel/sched/schedule_api/kernel.scheduler.multiq FAILED: Failed
ERROR   - qemu_arc_em               tests/kernel/sleep/kernel.common.timing            FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/kernel/sched/schedule_api/kernel.scheduler   FAILED: Failed
ERROR   - qemu_arc_em               tests/kernel/sched/schedule_api/kernel.scheduler.multiq_no_timeslicing FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/kernel/sched/schedule_api/kernel.scheduler.no_timeslicing FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/kernel/sched/preempt/kernel.scheduler.preempt FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/kernel/queue/kernel.queue.poll               FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/kernel/queue/kernel.queue                    FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/kernel/pipe/pipe/kernel.pipe                 FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/kernel/pipe/pipe_api/kernel.pipe.api         FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/kernel/mem_pool/mem_pool_threadsafe/kernel.memory_pool.threadsafe FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/kernel/mem_pool/mem_pool_concept/kernel.memory_pool.concept.legacy FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/kernel/common/kernel.common                  FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/kernel/common/kernel.common.misra            FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/kernel/context/kernel.common                 FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/kernel/fifo/fifo_timeout/kernel.fifo.timeout FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/kernel/fifo/fifo_timeout/kernel.fifo.timeout.poll FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/kernel/fifo/fifo_api/kernel.fifo             FAILED: Failed
ERROR   - qemu_arc_em               tests/kernel/fifo/fifo_api/kernel.fifo.poll        FAILED: Failed
ERROR   - qemu_arc_em               tests/kernel/mbox/mbox_usage/kernel.mailbox.usage  FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/crypto/mbedtls/crypto.mbedtls                FAILED: Exited with 1
ERROR   - qemu_arc_em               tests/benchmarks/timing_info/benchmark.kernel.timing.default FAILED: Exited with 1

I tested samples/portability/cmsis_rtos_v2/timer_synchronization with west , if I increase the TIMER_TICKS to 250, it will pass:
https://github.com/zephyrproject-rtos/zephyr/blob/3dba8cc8509b1c52d5bebf6eafcf95c0eb8b2cbe/samples/portability/cmsis_rtos_v2/timer_synchronization/src/main.c#L15

not sure how the timeout in the code relates to the timeout of running the test and failing due to timeouts in sanitycheck.

are any of these tests CPU bound? coverage accounting will add nontrivial overhead.

I think this one was already fixed with recent move to multiprocessing.

authors: andrewboie nashif wangnuannuan


text:
west flash to teensy 41 fail, use blinky with west build

I follow the Getting Started Guide, then

zephyrproject\zephyr>$ west build -p auto -b teensy41 samples\basic\blinky
zephyrproject\zephyr>$ west flash   <<Fail
zephyrproject\zephyr>$ cd build
zephyrproject\zephyr\build>$ west flash   <<Fail
zephyrproject\zephyr\build>$ ninja flash   <<Fail
Here is the error message show in windows10 cmd :
[0/1] Flashing teensy41
-- west flash: rebuilding
ninja: no work to do.
FATAL ERROR: either a pristine build is needed, or board teensy41 doesn't support west flash/debug (no ZEPHYR_RUNNERS_YAML in CMake cache)
FAILED: zephyr/cmake/flash/CMakeFiles/flash C:/Users/canic/Desktop/zephyrproject/zephyr/build/zephyr/cmake/flash/CMakeFiles/flash
cmd.exe /C "cd /D C:\Users\canic\Desktop\zephyrproject\zephyr\build && "C:\Program Files\CMake\bin\cmake.exe" -DTARGET=flash -DDEPENDENCIES="" -P C:/Users/canic/Desktop/zephyrproject/zephyr/cmake/flash/check_runner_dependencies.cmake && "C:\Program Files\CMake\bin\cmake.exe" -E env C:/Users/canic/AppData/Local/Programs/Python/Python39/python.exe -m west flash"
ninja: build stopped: subcommand failed.

Is any step I do it wrong?

Nothing wrong, the board doesn't support west flash/debug.  There is no board.cmake describing how to invoke the west runners for flashing purposes.

authors: WolsYang galak


text:
Phython 3.10.12 venv install failure in Ubuntu 22.04

Hi @rrozario1968, I believe that venv is already installed in all recent distributions of python.  Please proceed with the command to create a venv:
python3 -m venv .venv

Note here that I named the venv .venv.
If that is working for you then please close this ticket.
Cheers,
JP

What install instructions are you following? I would recommend you follow the getting started instructions to the letter, in this case it would have you install python3-venv, which I think should get you past the error your having by trying to force a specific version.

What install instructions are you following? I would recommend you follow the getting started instructions to the letter, in this case it would have you install python3-venv, which I think should get you past the error your having by trying to force a specific version.

I can confirm that following the getting started instructions and using sudo apt-get install python3-venv succeeds on Ubuntu 22.04.
@rrozario1968 Please reopen this issue with further details if this does not work for you.

Hi,
I tried it in different ways but it would not install venv. I tried to follow the guide word for word and it did not work.
Best Regards,
Robert
From: Benjamin Cabé @.>
Sent: Tuesday, February 6, 2024 12:06 AM
To: zephyrproject-rtos/zephyr @.>
Cc: Rozario Robert (CSS SMD AMR SIS TM) @.>; Mention @.>
Subject: Re: [zephyrproject-rtos/zephyr] Phython 3.10.12 venv install failure in Ubuntu 22.04 (Issue #68580)
Caution: This e-mail originated outside Infineon Technologies. Do not click on links or open attachments unless you validate it is safehttps://intranet-content.infineon.com/explore/aboutinfineon/rules/informationsecurity/ug/SocialEngineering/Pages/SocialEngineeringElements_en.aspx.
What install instructions are you following? I would recommend you follow the getting started instructions to the letter, in this case it would have you install python3-venv, which I think should get you past the error your having by trying to force a specific version.
—
Reply to this email directly, view it on GitHubhttps://github.com/zephyrproject-rtos/zephyr/issues/68580#issuecomment-1928974166, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A2NWJMLO2DZAORDVMP6BZJ3YSHP7FAVCNFSM6AAAAABC3AWUOGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRYHE3TIMJWGY.
You are receiving this because you were mentioned.Message ID: @.@.>>

As mentioned, please share more details (and actual text, not screenshots, please) if you want help. It is virtually impossible to troubleshoot your problem if all we know is that "[you] tried it in different ways but it would not install". Thanks!

authors: JPHutchins henrikbrixandersen kartben rrozario1968


text:
[TOPIC-GPIO] gpio: add driver for MCP23S17 GPIO chip

Just basic support without interrupt

@tbursztyka @henrikbrixandersen
Any idea's to on how to support gpio cs when supporting multiple devices? I believe this is the first one

@sknsean each and every struct gpio_mcp23s17_config  would need to store the gpio dev name and the pin I guess. If such dev name is empty, and thus device_get_binding() will return NULL, just assume there is no gpio/cs there. Something like that.

Codecov Report

Merging #11406 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #11406   +/-   ##
=======================================
  Coverage   48.37%   48.37%
=======================================
  Files         265      265
  Lines       42188    42188
  Branches    10137    10137
=======================================
  Hits        20408    20408
  Misses      17703    17703
  Partials     4077     4077

Continue to review full report at Codecov.

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

@galak the driver uses the GPIO API why do we need a sample app?

Addressed the defines and devicetree options
Sample app is still a mystery...

Sample app is to ensure that your driver code at least get compile tested.

Yes i get that... But I can’t find anything similar for a GPIO driver

@galak added sample app

@nashif can you please tell me whats is wrong with the license check?

@galak ping :-)

ping^2

Thanks @sknsean for picking up work on the driver. We are currently in the process of updating all existing GPIO drivers to the new API. This work is almost completed. You should target this PR on topic-gpio branch.
The current code looks good overall. However, there is still some not insignificant amount of work that needs to be done. You can check out the description of #18530 for basic information on how to convert the driver. Then you can also have a look at gpio_sx1509b.c which is a good example of external GPIO driver supporting the new API. Unlike the driver in this PR  gpio_sx1509b.c is connected via I2C bus but that doesn't really make much of a difference.
Some remarks:

we are moving away from using Kconfig to enable driver instances. It would be good if you converted your driver to use DTS. Here gpio_pca95xx.c should be a good example.
All the API calls that referred to GPIO_ACCESS_BY_PORT were removed. There is no need to support this mode any more. All related code can be removed from the driver. In a few functions that still take access_op you can place following code somewhere at the beginning.

	if (access_op != GPIO_ACCESS_BY_PIN) {
		return -ENOTSUP;
	}

Is these mandatory with the new API?
.port_get_raw = port_get,
.port_set_masked_raw = port_set_masked,
.port_set_bits_raw = port_set_bits,
.port_clear_bits_raw = port_clear_bits,
.port_toggle_bits = port_toggle_bits,
GPIO_ACCESS_BY_PORT is replaced with port_get_raw ?

Is these mandatory with the new API?
.port_get_raw = port_get,
.port_set_masked_raw = port_set_masked,
.port_set_bits_raw = port_set_bits,
.port_clear_bits_raw = port_clear_bits,
.port_toggle_bits = port_toggle_bits,

The functions are mandatory, however this section should be written as
	.port_get_raw = mcp23s17_port_get_raw,
	.port_set_masked_raw = mcp23s17_port_set_masked_raw,
	.port_set_bits_raw = mcp23s17_port_set_bits_raw,
	.port_clear_bits_raw = mcp23s17_port_clear_bits_raw,
	.port_toggle_bits = mcp23s17_port_toggle_bits,

GPIO_ACCESS_BY_PORT is replaced with port_get_raw ?

No, not really. GPIO_ACCESS_BY_PORT is already removed from the current master. port_get_raw is a new function. The new functions are implemented only as the port variant. However, thanks to the inline code in include/drivers/gpio.h we get also pin variant functions.

Can someone point me to where I can find info about the Kconfig error?

@MaureenHelm @mnkp @pabigot @galak Can you re-review?

@mnkp @galak is this ready to be merged?

@mnkp adressed most of the comments

authors: carlescufi codecov-io henrikbrixandersen mnkp sknsean tbursztyka


text:
[TOPIC-BLE-LLCP]: Bluetooth: controller: llcp: split out control procs

The control procedures are splitted out in their own file, making it
easier to merge in the new LLCP
This work is far from finished, but is intended to give us a basic for discussion on our thursday meeting

Closing this PR. The conclusion is that we do not want to refactor the existing ull_conn due to the amount of work and risks


text:
logging: add padding for RISC-V 64bits environment

This patch add padding in filter structure of log system.
In RISCV && 64BIT environment. Log system is facing alignment bug.
struct log_source_dynamic_data {
uint32_t filters;
};
static inline uint32_t *log_dynamic_filters_get(uint32_t source_id)
{
return &__log_dynamic_start[source_id].filters;
}
A sizeof(log_source_dynamic_data) = 4, address offset of
&__log_dynamic_start[] are:

&__log_dynamic_start[0]: +0
&__log_dynamic_start[1]: +4
&__log_dynamic_start[2]: +8

But RISCV 64bit gcc/ld places each log_dynamic_log, log_dynamic_os
and log_dynamic_test per 8bytes alignment. So address offset of
log_dynamic_* are:

&log_dynamic_log : +0
&log_dynamic_os  : +8
&log_dynamic_test: +16

tests/subsys/logging/log_core cannot set correct log filters in
RISCV && 64BIT environment, so test is always going to fail.
Signed-off-by: Katsuhiro Suzuki katsuhiro@katsuster.net

Hello @nordic-krch,
Thank you for your review. Yes, right. It's almost same issue on NIOS2.
There is a small difference. NIOS2 required to ensure 'over' 8 bytes.
RV64 required 8 bytes aligned size, so using same size of NIOS2 (= 12 bytes) did not work...


text:
drivers/ivshmem: MSI API change was not applied in this drivers

commit id ec2b9d42afbffa27076bf42b4953eacfb8a3c709 missed that ivshmem
uses pcie_msi_enable as well, thus fixing it now.
Signed-off-by: Tomasz Bursztyka tomasz.bursztyka@linux.intel.com

@nashif @carlescufi  This need to get merged as soon as it's ready to be, it's breaking ivshmem build and blocking ACRN users


text:
ipc_service: cleanup and re-organize paths

Before going to introduce new backends, cleanup a bit the ipc_service space. Refer to the (straightforward) commits.

I noticed that the IPC_SERVICE_REG_BACKEND_PRIORITY and IPC_SERVICE_NUM_ENDPOINTS_PER_INSTANCE configs are defined in ipc/ipc_service/Kconfigs. Could we move them to the backend as used in ipc_rpmsg_static_vrings_mi.c?

Actually those are going to be used (potentially) by all the backends so that's why they are in the general Kconfig.

I noticed that the IPC_SERVICE_REG_BACKEND_PRIORITY and IPC_SERVICE_NUM_ENDPOINTS_PER_INSTANCE configs are defined in ipc/ipc_service/Kconfigs. Could we move them to the backend as used in ipc_rpmsg_static_vrings_mi.c?

Actually those are going to be used (potentially) by all the backends so that's why they are in the general Kconfig.

Please, could you clarify what would require this, in case of several backends?
I would expect that all backends would be  in ipc/ipc_services/backends/ and therefore these configs would be declared in ipc/ipc_services/backends/Kconfig.

and therefore these configs would be declared in ipc/ipc_services/backends/Kconfig.

Oooh, you mean ipc/ipc_services/backends/Kconfig, I thought you were suggesting to move those to Kconfig.rpmsg_mi. Yup, I can do that.

@arnopo added new commit

authors: arnopo carlocaione


text:
subsys/ztest: Make 1cpu tests run on CPU 0 specifically

Some hardware has "interesting" configuration like asymmetric default
interrupt masking (the intel_adsp devices in particular, but x86's
IO-APIC driver has tripped over this in the past too) that needs
special treatment if you want to run something on "core 1"
specifically, and 1cpu test cases pretty much by definition are going
to have been written without SMP details in mind.  Switch the logic
around a tiny bit such that these test cases always run on CPU ID zero
explicitly.
Actually in practice this was ALMOST guaranteed to be true already,
because test setup and happens serially, having been started on the
main thread, which starts on CPU 0 by definition.  Then the test
teardown aborts all the spawned threads that might have been running
on CPUs 1+, so those reach idle, and the next test case starts
syncronously on the same thread (and thus CPU) where it started.  But
nonetheless that wasn't actually enforced, and we've found at least
one simulation environment where timing conspires to break things.
Signed-off-by: Andy Ross andrew.j.ross@intel.com

Recreating a new PR to replace https://github.com/zephyrproject-rtos/zephyr/pull/42803 , as that seems to have gotten into some kind of weird state following a rebase.   Needs re-review, obviously.


text:
tests: timer_monotonic: Use volatile for timing variables

This commit adds the volatile qualifier to the timing variables, in
order to ensure that the compiler does not try to optimise the test in
a way that can affect the execution time measurements.
Signed-off-by: Stephanos Ioannidis root@stephanos.io
NOTE: This fixes the qemu_arc_hs6x failure seen here. For more details, refer to the discussion on Discord.

I missed the party here, but looking at the code in question, this seems really unlikely to be a root cause fix and frankly looks more like a platform bug.  Check the cycle counter implementation on ARC.  My guess is that it turns into an inline expansion of something without a compiler barrier: e.g. an __asm__ block missing a volatile, a spinlock or atomic definition without a memory clobber, etc...
What's seems to have happened is that gcc thought it was OK to move around the result of k_cycle_get_32(), and that can't be allowed to happen.  In general platforms get this feature for free (again by the use of things like volatile asm blocks or things like spin/irq locks that contain them).
Either that, or it's a compiler bug I guess.

this seems really unlikely to be a root cause fix

Yea, this was never meant to be a fundamental fix; as noted in the linked Discord thread, it is likely a compiler bug and I have pinged the ARC guys to have a look.
That aside, these variables should have been volatile anyways.

That aside, these variables should have been volatile anyways.

They look fine to me.  The natural code generation on most platforms in fact is going to leave them in callee-saved registers across the k_sleep() call (which is a proper ABI function everywhere because of how we define it) and never have them in memory at all.
Broadly, I'm really suspicious about situations where code has naked volatiles sitting on local variables, especially so when their address is never taken or passed around.   Per the spec, I'm pretty sure that this is a noop anyway -- volatile doesn't guarantee the compiler won't optimize situations it can logically prove, it just says that the compiler must assume that other contexts (which don't exist here!) might change memory state (basically: volatile is really underspecified).  If we actually do have a situation where there is a true logical ordering requirement that the compiler can't see for some reason, the proper tool is a compiler barrier like __asm__ volatile("" ::: "memory");

authors: andyross stephanosio


text:
ADXL372: add names for KConfig choices

This patch adds names to the KConfig choices of the ADXL372 driver.
Signed-off-by: Maximilian Deubel maximilian.deubel@nordicsemi.no

Could we merge this? @MaureenHelm

Could we merge this? @MaureenHelm

It needs a second approval. Ping @gmarull @teburd

authors: MaureenHelm maxd-nordic


text:
samples: bluetooth: broadcast_audio_sink: main needs to return a value

main is now int main(void), so it needs to return a value.

Already implemented by https://github.com/zephyrproject-rtos/zephyr/pull/56837

authors: Thalley gmarull


text:
fix fallthrough on sample_channel_get on AQI

There is a small bug present in ENS161 sensor driver where while getting samples for AQI logging return ERRNO -134
Cause was a lack of break in switch statement.

@KryQ almost there with compliance check - please amend git author name/email to match the sign-off entry

authors: KryQ kartben


text:
Remove infura id and provide env related hints

as mentioned in title :)

Hey @itinance! Thanks for contributing. We appreciate it a lot! 🚀 ❤

authors: itinance ylv-io

repo: zeppelinos/zepkit


text:
Draft constants are missing: ZMQ_RECONNECT_STOP_CONN_REFUSED ZMQ_RECONNECT_STOP_HANDSHAKE_FAILED ZMQ_RECONNECT_STOP_AFTER_DISCONNECT

I wanted to try and see if they would solve the lack of error messages from ZMQ for TCP peers that can't be connected to but these constants are missing.

You're right, these draft constants are not yet exported. draft support in pyzmq is often incomplete.
In the meantime, you can use their actual values (1, 2, 3). pyzmq doesn't need to be aware of most libzmq constants for them to be used.

I tried to use them like this: socket.setsockopt(2, 1), but it throws an exception Invalid argument.

I've never used these options, but I believe those are values for the ZMQ_RECONNECT_STOP option:
socket.setsockopt(zmq.RECONNECT_STOP, 1) # or 2 or 3

authors: minrk yurivict

repo: zeromq/pyzmq


text:
zmq.utils z85 decode (of string) does not work with python 3

>>> print("libzmq-%s" % zmq.zmq_version())
libzmq-4.1.2
>>> print("pyzmq-%s" % zmq.pyzmq_version())
pyzmq-15.2.0
>>> print("Python-%s" % sys.version)
Python-3.4.4 (v3.4.4:737efcadf5a6, Dec 20 2015, 19:28:18) [MSC v.1600 32 bit (Intel)]

Steps to reproduce:
>>> z85.decode("Z9]q$")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "F:\Python\python-3.4.4\lib\site-packages\zmq\utils\z85.py", line 55, in decode
    value += Z85MAP[z85bytes[i+j]] * offset
KeyError: 'Z'

Expected behaviour from python 2.7:
>>> z85.decode("Z9]q$")
'\xbe(\x96\xd5'

Now I know I can fix this by prepending b"" to my string and it works as expected but should the decode function check whether I am passing in bytes or a string and raise a specific Exception? Or should it just automatically convert a string to a bytearray?

Pull request #816 is a possible fix for this

Actually, emulating the behaviour of hashlib under python3 might make more sense:
TypeError: Unicode-objects must be encoded before hashing
I will update my pull request


text:
吃饭

赛百味
辣椒炒肉饭
羊杂汤

煎鸡蛋
牛肉/鱼肉
奶

每周吃一次鱼/牛排。
每天吃鸡蛋，奶，水果
多看抖音健身食材


text:
ability to delete secrets

deletion can be done by setting an empty string as value.
deletion should delete the secret from the persistent storage too, to safe space, it should also unregister the secret from memory (secrets map) as well.

punting to v11

done.

repo: zerotohero-dev/aegis


text:
Idea: conditonal parser, which takes a parser and a condition

I originally tried to implement the idea with then_with or custom and a captured value, but then_with won't work because I can't return two different parser types and custom doesn't provide the right interface. It would be very useful if you had a conditional parser, which takes a condition and a parser that outputs O and returns a parser that outputs Option<O>.
This would will allow us to write similar parsers without repeating a whole bunch of code, by putting the part that is different in a conditional parser.

Perhaps .filter(...) is what you're looking for? You can do a.filter(|a| a.is_foo()). I think you might be a bit confused about how parser outputs work though: Fallibility is built in to a parser, if the filter closure returns false, then the parser just won't parse anything.

Ah, are you trying to dynamically change the behaviour of your parser at runtime based on some configuration for the parser? I assumed that the condition was dependent on the output of the parser. In that case, there are a few approaches you can take:

Parsers can be dynamically dispatched, so you can do if condition { a.map(Some).boxed() } else { empty().to(None).boxed() } and this should type-check just fine (the parser in the else branch always succeeds while parsing no tokens)

Use custom like so:

custom(|inp| if condition { inp.parse(a).map(Some) } else { Ok(None) })

this approach avoids the dynamic dispatch of the previous approach.

Ah yes! Thank you those are exactly what I need

authors: dexterdy zesterer

repo: zesterer/chumsky


text:
⚠ API has degraded performance

In c12aef0, API ($ZESTY_API) experienced degraded performance:

HTTP code: 403
Response time: 1196 ms

Resolved: API performance has improved in 728c67c.

repo: zesty-co/status


text:
Automatically fetch blockchain modules docs

Cosmos SDK module docs specs should be fetched and added to the content of the docs website as a top-level section.
Blocked on zeta-node repo not being open source.

https://github.com/zeta-chain/docs/pull/54

repo: zeta-chain/docs


text:
Bug: Zeta Hub shows false delegate power

There is a bug in Zeta Hub's website. It shows millions of ZETA power in the stake page even thought I don't have 1 ZETA.
Checkout this video to understand the bug: https://drive.google.com/file/d/1Py1qNcO6dVuyon76o842rCzKxjXJa8DZ/view?usp=sharing
Also, I just want to say that there was lots of mistakes about the airdrop distribution. I have tested ZETA for a long time, I was making the quests and I have lots of roles on DC (DC: 0xemin). I just get 1 ZETA. Community is angry about that.

@fadeev ser could you please check it?

@eminmtas ZetaHub has a Feedback link in the footer to submit bug reports and feedback in general. I've submitted a bug report on your behalf, but in the future, please, use this dedicated feedback form. Thank you.

I didn't know about the feedback form, sorry about that. Thank you🙏

authors: eminmtas fadeev


text:
Get the list of chains from configuration

Currently GetChainFromChainID uses the DefaultChainsList function to get the list of chains, which is hard-coded. Should we read the list of chains from the configuration? This makes it more flexible and configurable.
https://github.com/zeta-chain/node/blob/6567637545769a01a8406fd8fc9ad4427b7cb725/common/chain.go#L189

We plan to remove the different build types: https://github.com/zeta-chain/node/issues/1331
I think this task will be part of it since we will no longer be able to directly use hardcoded values.

Closing as we can now get the supported chains for the observer module through the chain params

repo: zeta-chain/node


text:
ci: add semantic pr workflow

Add a CI workflow to validate pr title using semantic standard

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 8.30%. Comparing base (d1250ea) to head (48c3ff9).

Additional details and impacted files
@@          Coverage Diff          @@
##            main     #45   +/-   ##
=====================================
  Coverage   8.30%   8.30%
=====================================
  Files          1       1
  Lines        253     253
=====================================
  Hits          21      21
  Misses       232     232

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

authors: codecov-commenter lumtis

repo: zeta-chain/protocol-contracts-solana


text:
Difficulty with exporting torch -> caffe2 model conversion: RuntimeError: Only tuples, lists and Variables are supported as JIT inputs/outputs

Hi,
First, I should say thanks for doing this great work!
I'm looking into this now and have been having trouble with exporting the model to a format for caffe2, as outlined in the paper (section 4.4).
I have installed the versions of the mentioned requirements, and when using export_model.py from the detectron2 repository, I come across the following error:
Traceback (most recent call last):
  File "C:\Users\xxx\deep_learning\android\DensePoseFnL\export_model.py", line 239, in <module>
    exported_model = export_caffe2_tracing(cfg, torch_model, sample_inputs)
  File "C:\Users\xxx\deep_learning\android\DensePoseFnL\export_model.py", line 58, in export_caffe2_tracing
    caffe2_model = tracer.export_caffe2()
  File "c:\users\xxx\deep_learning\android\detectron2\detectron2\export\api.py", line 81, in export_caffe2
    predict_net, init_net = export_caffe2_detection_model(
  File "c:\users\xxx\deep_learning\android\detectron2\detectron2\export\caffe2_export.py", line 146, in export_caffe2_detection_model
    onnx_model = export_onnx_model(model, (tensor_inputs,))
  File "c:\users\xxx\deep_learning\android\detectron2\detectron2\export\caffe2_export.py", line 56, in export_onnx_model
    torch.onnx.export(
  File "C:\Users\xxx\miniconda3\lib\site-packages\torch\onnx\__init__.py", line 316, in export
    return utils.export(model, args, f, export_params, verbose, training,
  File "C:\Users\xxx\miniconda3\lib\site-packages\torch\onnx\utils.py", line 107, in export
    _export(model, args, f, export_params, verbose, training, input_names, output_names,
  File "C:\Users\xxx\miniconda3\lib\site-packages\torch\onnx\utils.py", line 724, in _export
    _model_to_graph(model, args, verbose, input_names,
  File "C:\Users\xxx\miniconda3\lib\site-packages\torch\onnx\utils.py", line 493, in _model_to_graph
    graph, params, torch_out, module = _create_jit_graph(model, args)
  File "C:\Users\xxx\miniconda3\lib\site-packages\torch\onnx\utils.py", line 437, in _create_jit_graph
    graph, torch_out = _trace_and_get_graph_from_model(model, args)
  File "C:\Users\xxx\miniconda3\lib\site-packages\torch\onnx\utils.py", line 388, in _trace_and_get_graph_from_model
    torch.jit._get_trace_graph(model, args, strict=False, _force_outplace=False, _return_inputs_states=True)
  File "C:\Users\xxx\miniconda3\lib\site-packages\torch\jit\_trace.py", line 1166, in _get_trace_graph
    outs = ONNXTracedModule(f, strict, _force_outplace, return_inputs, _return_inputs_states)(*args, **kwargs)
  File "C:\Users\xxx\miniconda3\lib\site-packages\torch\nn\modules\module.py", line 1102, in _call_impl
    return forward_call(*input, **kwargs)
  File "C:\Users\xxx\miniconda3\lib\site-packages\torch\jit\_trace.py", line 127, in forward
    graph, out = torch._C._create_graph_by_tracing(
  File "C:\Users\xxx\miniconda3\lib\site-packages\torch\jit\_trace.py", line 121, in wrapper
    out_vars, _ = _flatten(outs)
RuntimeError: Only tuples, lists and Variables are supported as JIT inputs/outputs. Dictionaries and strings are also accepted, but their usage is not recommended. Here, received an input of unsupported type: DensePoseChartPredictorOutputWithConfidences

I get a similar error with all 3 of the models referenced in the project, sadly (albeit with a different type mentioned if the CSE model is used).
Is there a script you're using to convert this, or is there something I'm missing in this process?
Thanks your your help!

Hello,
The script was available on a previous version of the. Please have a look at previous commits.
This also requires a model to be caffe2 exportable, in this version we haven't preserve this feature

Regarding the error you see. This issue occurs because the model you are trying to trace returns detectron2 structure and not a list or tuple of torch.Tensors. Rewrite (S,I,U,V) output of DensePose model as a tuple of Tensors, that'll help

If the current version of the repo doesn't have this functionality, I'll have a look through previous commits and see if I can get it working, thanks!

@zetyquickly , Can you add the previous model which was caffe2 exportable ?

the previous weights are out of date because of unknown issue which led to performance degradation. I assume that the current weights still might be exportable, but you need to follow the export scripts from previous version

detectron2 export is all you need (c)
https://detectron2.readthedocs.io/en/latest/modules/export.html

I was able to convert the models using detectron but, the inference from both torchscript and onnx model were empty.
 (tensor([], size=(0, 4), grad_fn=<ReshapeAliasBackward0>), tensor([], dtype=torch.int64), tensor([], grad_fn=<IndexBackward0>), tensor([1067,  800]))
I am using this commit git checkout bb96d0b01d0605761ca182d0e3fac6ead8d8df6e of detectron.
The model I used is: mobile_parsing_rcnn_b_wc2m_s3x.pth.

authors: karl-mccarron pramishp zetyquickly

repo: zetyquickly/DensePoseFnL


text:
Add (usage of) aliases for ContentValidationListener

Provide a narrative description of what you are trying to accomplish:

[x] Are you creating a new feature?

[x] Why is the new feature needed? What purpose does it serve?

Usage of an alias allows users to provide own implementation of ContentValidationListener

[x] How will users use the new feature?

Users might wish to add/remove/alter ContentValidationListener implementation (like me :) )

[x] Base your feature on the develop branch, and submit against that branch.

Done

[x] Add only one feature per pull request; split multiple features over multiple pull requests

Done -> Adding aliases. Implementing single usage of aliases in Module.php.

[-] Add tests for the new feature.

Not a feature, no change in functionality.

[x] Add documentation for the new feature.

Updated with changes

[-] Add a CHANGELOG.md entry for the new feature.

Not a feature, just expanding and making optional which one to use, without modification of current implementation. Would this require changelog entry?

Coverage remained the same at 78.922% when pulling 4edd17871437812c5c95b13a8d34cf22334e30d2 on rkeet:develop into c36b369912afc5bce8792838785de431407a61bb on zfcampus:develop.

Created this PR so that I (and others when they know about it) can choose to implement their own/a modified ContentValidationListener.
I've also run into this issue (#59). I'll be creating a feature branch with a fix for it shortly. However, if that [new PR] does not pass the wishes of the maintainers for this repo, then maybe this PR can at least give the option for others to implement what they need outside of this repo.

another wee ping @weierophinney

authors: coveralls rkeet

repo: zfcampus/zf-content-validation


text:
context-path: /   之后，启动报错.AuthenticationException: token为空!

版本号：2.1.4
问题描述：context-path: /   之后，启动报错
.AuthenticationException: token为空!
截图&代码：

友情提示： 未按格式要求发帖，会直接删掉。

前端未启动，仅启动了后端项目

修改了WebMvcConfiguration 中的
public void addViewControllers(ViewControllerRegistry registry) {
registry.addViewController("/").setViewName("index.html");
}
错误还是一样

repo: zhangdaiscott/jeecg-boot


text:
增强问题

版本号：1.0
问题描述：
按照官方给定的文档测试“JS增强”以及“自定义按钮”，配置完成之后，进行功能测试，跟预期一样，所见即所得。但【代码生成】之后的页面上却没有“自定义按钮”和“JS增强”逻辑。不知道是不是我什么地方没有操作对
另外，官方是否有将前端自定义的组件打成可直接引用的类库包
截图&代码：
如下两张图是在online开发上做功能测试时的情形，自定义按钮有显示，而且也能满足预期

下图是【生成代码】后测试情形，没有看到自定义按钮

友情提示： 未按格式要求发帖，会直接删掉。

不支持自定义按钮和增强的生成

不支持自定义按钮和增强的生成

authors: haozhangzh zhangdaiscott


text:
您好，能不能把预训练好的bert_language模型给我分享一下，我下不了（跪求）

$ wget https://drive.google.com/file/d/1sayx7qwOd79XE4RFdvSXG3zyQH4FpyYJ/view?usp=sharing
--2022-03-23 18:09:05--  https://drive.google.com/file/d/1sayx7qwOd79XE4RFdvSXG3zyQH4FpyYJ/view?usp=sharing
Resolving drive.google.com (drive.google.com)... 31.13.95.37, 2001::68f4:2b68
Connecting to drive.google.com (drive.google.com)|31.13.95.37|:443... failed: Connection timed out.
Connecting to drive.google.com (drive.google.com)|2001::68f4:2b68|:443... failed: Network is unreachable.
，网盘账号是15603379965

$ wget https://drive.google.com/file/d/1sayx7qwOd79XE4RFdvSXG3zyQH4FpyYJ/view?usp=sharing --2022-03-23 18:09:05-- https://drive.google.com/file/d/1sayx7qwOd79XE4RFdvSXG3zyQH4FpyYJ/view?usp=sharing Resolving drive.google.com (drive.google.com)... 31.13.95.37, 2001::68f4:2b68 Connecting to drive.google.com (drive.google.com)|31.13.95.37|:443... failed: Connection timed out. Connecting to drive.google.com (drive.google.com)|2001::68f4:2b68|:443... failed: Network is unreachable. ，网盘账号是15603379965

您可以加一下我的微信，账号见project主页。


text:
🛑 ZY is down

In bfec63d, ZY (https://ziyuan.baidu.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ZY is back up in 4c1f5f9.

repo: zhaodylan/uptime-ziyuan


text:
🛑 ZY is down

In f4d976d, ZY (https://ziyuan.baidu.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ZY is back up in 19bec93.


text:
retrigger registration again

@JuliaRegistrator register

Error while trying to register: "Tag with name v1.0.0 already exists and points to a different commit"

@JuliaRegistrator register

Error while trying to register: "Tag with name v1.0.0 already exists and points to a different commit"

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/84591
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v1.0.0 -m "<description of version>" 8cd1006072abdb8dd8343d34e298f2c7abb6e3c6
git push origin v1.0.0

@JuliaRegistrator register

Error while trying to register: "Tag with name v1.0.0 already exists and points to a different commit"

@JuliaRegistrator register

Error while trying to register: "Tag with name v1.0.1 already exists and points to a different commit"

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/84592
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v1.0.1 -m "<description of version>" ce4b0c9cff0ba4b159c0bc104e1f8320fec02b45
git push origin v1.0.1

Also, note the warning: This looks like a new registration that registers version 1.0.1.
Ideally, you should register an initial release with 0.0.1, 0.1.0 or 1.0.0 version numbers
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

@JuliaRegistrator register

Registration pull request updated: JuliaRegistries/General/84591
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v1.0.0 -m "<description of version>" 0115ef6de366a925baebc0a7746ab9a2f994be97
git push origin v1.0.0

authors: JuliaRegistrator zhaoli-IHEP


text:
🛑 腾讯云 COS 节点 is down

In e00b2f4, 腾讯云 COS 节点 (https://lisz.ink) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 腾讯云 COS 节点 is back up in b49effa.

repo: zhonger/upptime


text:
🛑 腾讯云 COS 节点 is down

In 36de6b6, 腾讯云 COS 节点 (https://lisz.ink) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 腾讯云 COS 节点 is back up in dfa704b.


text:
Typo in docblock

Short description of what this resolves:
Typo in docblock
Changes proposed in this pull request:

Coverage remained the same at 94.0% when pulling e74a9ffb2e739a6c411c782f451de2db6d230a8c on michaelKaefer:patch-2 into 1fa7231c79bf0a5d4a3546d14d8910dee9f6c6d7 on zibios:master.

Coverage remained the same at 94.0% when pulling e74a9ffb2e739a6c411c782f451de2db6d230a8c on michaelKaefer:patch-2 into 1fa7231c79bf0a5d4a3546d14d8910dee9f6c6d7 on zibios:master.

Coverage remained the same at 94.0% when pulling e74a9ffb2e739a6c411c782f451de2db6d230a8c on michaelKaefer:patch-2 into 1fa7231c79bf0a5d4a3546d14d8910dee9f6c6d7 on zibios:master.

Coverage remained the same at 94.0% when pulling e74a9ffb2e739a6c411c782f451de2db6d230a8c on michaelKaefer:patch-2 into 1fa7231c79bf0a5d4a3546d14d8910dee9f6c6d7 on zibios:master.

Thank you @michaelKaefer for your help

authors: coveralls michaelKaefer zibios

repo: zibios/wrike-php-guzzle


text:
Wonder if you would reproduce the i2i function? Thanks.

aka "My Subject in My Style"

please stay tuned

authors: carvychen zideliu

repo: zideliu/StyleDrop-PyTorch


text:
Template for all groups page

When we go to https://muscat-tech.org/groups we should see a list of all the groups.
The file to change will be https://github.com/zidhuss/muscat-tech.org/blob/main/layouts/events/list.html

I'll give it a go.
Thinking of showing a simple list similar to the one in single event's page.
Let me know if you have another idea @zidhuss

authors: mohdrasbi zidhuss


text:
Expose device events for the puck stopping

Adds the STOP event from a symfonisk device as a device action.
The symfonisk puck will send a left/right event when starting to spin, then a stop event when it is back at standstill.

This change is at the moment untested, and perhaps it needs fixes for translations in home assistant.
I have tested with raw zha events and and a blueprint against KNX relative dimming where it works well.

Codecov Report

Merging #1426 (ed5f546) into dev (e3fa034) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##              dev    #1426   +/-   ##
=======================================
  Coverage   80.52%   80.53%
=======================================
  Files         222      222
  Lines        6414     6415    +1
=======================================
+ Hits         5165     5166    +1
  Misses       1249     1249

Impacted Files
Coverage Δ

zhaquirks/ikea/symfonisk.py
100.00% <ø> (ø)

zhaquirks/const.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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

Pull Request Test Coverage Report for Build 1966106807

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.003%) to 80.53%

Totals

Change from base Build 1947732782:
0.003%

Covered Lines:
5166

Relevant Lines:
6415

💛  - Coveralls

I is trying getting the tuya TS004F rotating knob working with one quirk and its have one tuya mode and one dimmer mode.
I was missing the stop command in DA for this device but i have not time looking on it.
Is its possible getting fast roaring left and right ?
I think its sending one other command for that and can being used (thinking = not knowing / remember).
Also the stop can being selected if its stop from right and left if implanting the direction it was having being rotated as is doe in the Open / Croce remote is have getting.
Its only suggestions if you have time and like getting more out of the nice device.
Great work done !!!

I've not seen any fast rotate on this device. It is still tricky to hook up in home assistant.
I'm not sure I follow what you said about stop direction. The device doesn't seem to indicate which direction is stopping.

The fast i can have misunderstanding then i have not testing it with the SYMFONISK but the old round gyro is sending one command for slow rotating and one other for fast rotating.
True its not direction of the stop command.
But you always have one move command before with direction 0 or 1 = Right / Left.
If you like you can using this logic:
https://github.com/zigpy/zha-device-handlers/blob/e3fa034284437595d1997326a8597086d623f413/zhaquirks/ikea/opencloseremote.py#L47from the open / close and saving  the direction and using it for the stop command and adding the last "saved" direction.
No must but only if you like.

LGTM, @elupus if you are set w/ the change we can merge it.

I dont think there is much benefit to knowing which direction did stop. A stop is a stop. There is a lack of support for these type of continuous commands in home assistant anyway. So a blueprint will be needed to make any good use of it.

Its not needed but the IKEA Open/Close is having it as device automation and i thinking doing the same TS004F Knob.
Im not but many user like have so much function they can for triggering automatons in there system but in the end you need on long list on the device for all and its not practical.
Better merging this and later i moving the rotating from IKEA INIT to constants so it can being user for more rotating devices :-)

@elupus ill merge this as soon as I get the green light from you. (Just in case you’re still soliciting feedback)

I'm good with this solution.

Thanks

@dmulcahey @MattWestb any of you have the other IKEA dimmer? It seems it uses same args for left/right, so seem very likely it also exposes stop.

I have 2 of the "retro" dimmers and i can looking later how it working but if i remember its sending nearly the same commands but i was wrong then its sending one other for fast rotating and the symfonisk not then its sending toggle on pressing.
It can also being that the args is wrong for the device automation but i fixing that if is so.
I must first getting the tuya TS004F rotating Knob working without  tuya ZBGW and it can taking little time.

This really looks to be standard LevelControl events. I don't think these device triggers should be added by quirks at all. It should be done by the devices just having LevelControl cluster. The slow fast is just the rate parameter, it should be a property of the device trigger rather than a separate trigger.

@elupus just using the presence of clusters would cause more triggers to show that aren’t functional. So many devices don’t follow specs. We’re also working on some changes that may affect how this all works. Also, can we move the rest of this to an issue or a discussion so we aren’t chatting on a merged PR? Thanks!

I think it wold being good is ZHA was having device automatons tigers for standard light controllers functions so not need doing quirk for all devices if they is not needing it for the normal Zigbee functionality.
Also new usier is not knowing how to using one light controller for automation (i dont do it then better using one HA switch for that) and is no good instruction what i have seen.
David can you open one discussion with appropriate topic so user can feeding there input and getting more good ideas ?
Im not so good on that then im more one spammer (as you knowing).

authors: MattWestb codecov-commenter coveralls dmulcahey elupus

repo: zigpy/zha-device-handlers


text:
Zig 0.13 build error

Following the Readme, you get the following error when trying to build.
error: no field named 'path' in union 'Build.LazyPath'
Build.zig
   const zap = b.dependency("zap", .{
       .target = target,
       .optimize = optimize,
       .openssl = false, // set to true to enable TLS support
   });

   exe.root_module.addImport("zap", zap.module("zap"));

   b.installArtifact(exe);

I use master branch with zig 0.13.0 and my app runs OK. @Paul-0x5061756c

I use master branch with zig 0.13.0 and my app runs OK. @Paul-0x5061756c

@stepasite I'm struggling with this problem as well. If you don't mind me asking,
Did you use the setup instructions from the README.md in this repo? How did you install zig?
thanks,

Looks like the lazy path should have been fixed with this PR. https://github.com/zigzap/zap/pull/105

The same problem here, how should I resolve it?

If I'm not mistaken adding this line fixed it for me:
exe.linkLibrary(zap.artifact("facil.io"));

If I'm not mistaken adding this line fixed it for me:
exe.linkLibrary(zap.artifact("facil.io"));

This didn't fix it for me.

If I'm not mistaken adding this line fixed it for me:
exe.linkLibrary(zap.artifact("facil.io"));

This didn't fix it for me. Would you mind showing me build.zig.zon?

Yea I wouldn't mind, but I messed around with Zap and deleted the code after... sorry about that

If I'm not mistaken adding this line fixed it for me:
exe.linkLibrary(zap.artifact("facil.io"));

This didn't fix it for me. Would you mind showing me build.zig.zon?

Yea I wouldn't mind, but I messed around with Zap and deleted the code after... sorry about that

lol, please do not mind :)
I'm just a beginner of Zig so I might be making stupid mistakes...

repo: zigzap/zap


text:
docs: Automated Changelog Update for v5.0.0-beta5.42

copilot:all
Automated changes by create-pull-request GitHub action

🤖 Generated by lychee action
Summary

Status
Count

🔍 Total
1273

✅ Successful
369

⏳ Timeouts
0

🔀 Redirected
0

👻 Excluded
903

❓ Unknown
0

🚫 Errors
0

Full action output
Full Github Actions output


text:
[Bug]: OpenAI Azure key doesn't seem to be supported even now

Current Behavior
from dotenv import load_dotenv
import time
import os
from gptcache import cache
from gptcache.adapter import openai
from gptcache.embedding import OpenAI
from gptcache.manager import CacheBase, VectorBase, get_data_manager
from gptcache.similarity_evaluation.distance import SearchDistanceEvaluation

load_dotenv()
openai_embd = OpenAI()

cache_base = CacheBase('sqlite')
vector_base = VectorBase('chromadb', dimension=openai_embd.dimension)

data_manager = get_data_manager(cache_base, vector_base)

cache.init(embedding_func=openai_embd.to_embeddings, data_manager=data_manager, similarity_evaluation=SearchDistanceEvaluation())
cache.set_azure_openai_key()

In the above code, I get an error from GPTCache saying
AttributeError : 'Cache' object has no attribute 'set_azure_openai_key'.
But then it works when I replace the last line with cache.set_openai_key().
I assume the issue is because of like 2 checks not passing in this PR
Expected Behavior
Ideally on initializing this, the code should run as normal and alloow me to interact with GPT and make the necessary API calls to it.
Steps To Reproduce
1. In the Python environment have Python 3.11.4
2. Install GPTCache
3. Try out the code above and you should see the error

Environment
Python 3.11.4
GPTCache 0.1.38

Anything else?
It'll be great to know by when this can be fixed and please let me know if there are any issues with my code.

@gssakash because there is no official release yet which includes this fix. And it is expected to be released tomorrow. You can install the dev version according to the source code.

@gssakash the 0.1.39 has been released, and you can try it. Looking forward to your feedback.

@gssakash I will close the issue. And If you have other problem, please create a new issue

authors: SimFG gssakash

repo: zilliztech/GPTCache


text:
Fix scann range search

issue #171
Faiss is highly optimized for batch searching, and different queries will search the same ivf bucket by gathering different queries' nprobe list which could reorder the npobe sequence, this could cause bug since range search goes as a 'early termination' manner, it will go through all ivf buckets and early terminate when no results found in one bucket, we have to search buckets by its sorted distance to query. Also, knowhere will split nq to single query, no need to gather queries' nprobe list.
before this pr
SCANN {"metric_type": "L2", "radius": 65.0} 0.0088
SCANN {"metric_type": "IP", "radius": 8.699999809265137} 0.003
SCANN {"metric_type": "COSINE", "radius": 0.20000000298023224} 0.0018

range search recall for IVF_FLAT with same param:
IVF_FLAT {"metric_type": "L2", "radius": 65.0} 0.1613
IVF_FLAT {"metric_type": "IP", "radius": 8.699999809265137} 0.1643
IVF_FLAT {"metric_type": "COSINE", "radius": 0.20000000298023224} 0.1675

after this pr
SCANN {"metric_type": "L2", "radius": 65.0} 0.2464
SCANN {"metric_type": "IP", "radius": 8.699999809265137} 0.0886
SCANN {"metric_type": "COSINE", "radius": 0.20000000298023224} 0.1035

/kind bug

/run-e2e

/run-e2e

/run-e2e

/lgtm

authors: chasingegg liliu-z

repo: zilliztech/knowhere


text:
Support for custom storage limits with the Minio deployment in operator

Hello, is there a way to specify how much storage is requested by the PVCs for Minio? I'm trying to do a POC deployment on my homelab and 500Gib per instance is WAY more than I can afford to spare.
I checked the values files on the chart as well as the cluster configuration options and the docs on the storage component and didn't find anything, so if it already exists, and if I'm just missing where to configure it, let me know.

@Tanchwa  It seems you put the size field in the wrong place. I tested it my self and it works fine. below is my full CR:
apiVersion: milvus.io/v1beta1
kind: Milvus
metadata:
  name: my-release
  labels:
    app: milvus
spec:
  config: {}
  components:
    standalone:
      replicas: 1
      serviceType: LoadBalancer
  dependencies:
    etcd:
      inCluster:
        values:
          replicaCount: 1
        deletionPolicy: Delete
        pvcDeletion: true
    storage:
      inCluster:
        values:
          mode: standalone
          resources:
            requests:
              memory: 100Mi
          persistence:
            size: 20Gi
        deletionPolicy: Delete
        pvcDeletion: true

Nope, that's where I have it, too.
apiVersion: milvus.io/v1beta1
kind: Milvus
metadata:
  name: my-release
  labels:
    app: milvus
spec:
  mode: cluster
  dependencies:
    etcd:
      inCluster:
        values:
          replicaCount: 1
    pulsar:
      inCluster:
        values:
          components:
            autorecovery: false
            functions: false
            toolset: false
            pulsar_manager: false
          monitoring:
            prometheus: false
            grafana: false
            node_exporter: false
            alert_manager: false
          proxy:
            replicaCount: 1
            resources:
              requests:
                cpu: 0.01
                memory: 256Mi
            configData:
              PULSAR_MEM: >
                -Xms256m -Xmx256m
              PULSAR_GC: >
                -XX:MaxDirectMemorySize=256m
          bookkeeper:
            replicaCount: 2
            resources:
              requests:
                cpu: 0.01
                memory: 256Mi
            configData:
              PULSAR_MEM: >
                -Xms256m
                -Xmx256m
                -XX:MaxDirectMemorySize=256m
              PULSAR_GC: >
                -Dio.netty.leakDetectionLevel=disabled
                -Dio.netty.recycler.linkCapacity=1024
                -XX:+UseG1GC -XX:MaxGCPauseMillis=10
                -XX:+ParallelRefProcEnabled
                -XX:+UnlockExperimentalVMOptions
                -XX:+DoEscapeAnalysis
                -XX:ParallelGCThreads=32
                -XX:ConcGCThreads=32
                -XX:G1NewSizePercent=50
                -XX:+DisableExplicitGC
                -XX:-ResizePLAB
                -XX:+ExitOnOutOfMemoryError
                -XX:+PerfDisableSharedMem
                -XX:+PrintGCDetails
          zookeeper:
            replicaCount: 1
            resources:
              requests:
                cpu: 0.01
                memory: 256Mi
            configData:
              PULSAR_MEM: >
                -Xms256m
                -Xmx256m
              PULSAR_GC: >
                -Dcom.sun.management.jmxremote
                -Djute.maxbuffer=10485760
                -XX:+ParallelRefProcEnabled
                -XX:+UnlockExperimentalVMOptions
                -XX:+DoEscapeAnalysis -XX:+DisableExplicitGC
                -XX:+PerfDisableSharedMem
                -Dzookeeper.forceSync=no
          broker:
            replicaCount: 1
            resources:
              requests:
                cpu: 0.01
                memory: 256Mi
            configData:
              PULSAR_MEM: >
                -Xms256m
                -Xmx256m
              PULSAR_GC: >
                -XX:MaxDirectMemorySize=256m
                -Dio.netty.leakDetectionLevel=disabled
                -Dio.netty.recycler.linkCapacity=1024
                -XX:+ParallelRefProcEnabled
                -XX:+UnlockExperimentalVMOptions
                -XX:+DoEscapeAnalysis
                -XX:ParallelGCThreads=32
                -XX:ConcGCThreads=32
                -XX:G1NewSizePercent=50
                -XX:+DisableExplicitGC
                -XX:-ResizePLAB
                -XX:+ExitOnOutOfMemoryError
    storage:
      inCluster:
        values:
          mode: standalone
          persistance:
            size: 20Gi

On Tue, Dec 5, 2023, 03:27 shaoyue @.***> wrote:

@Tanchwa https://github.com/Tanchwa It seems you put the size field in
the wrong place. I tested it my self and it works fine. below is my full CR:
apiVersion: milvus.io/v1beta1kind: Milvusmetadata:
name: my-release
labels:
app: milvusspec:
config: {}
components:
standalone:
replicas: 1
serviceType: LoadBalancer
dependencies:
etcd:
inCluster:
values:
replicaCount: 1
deletionPolicy: Delete
pvcDeletion: true
storage:
inCluster:
values:
mode: standalone
resources:
requests:
memory: 100Mi
persistence:
size: 20Gi
deletionPolicy: Delete
pvcDeletion: true
—
Reply to this email directly, view it on GitHub
https://github.com/zilliztech/milvus-operator/issues/54#issuecomment-1840250508,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVIZ4SV7KOWLNYYKCCHVF2DYH3LHBAVCNFSM6AAAAABADVNEH2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBQGI2TANJQHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

@Tanchwa Then it's because you didn't delete the PVC before you redeploy. By default milvus-operator won't delete the depencencies & data when you delete Milvus CR.
The minio release & data is only deleted when you specify Milvus CR like below.
spec:
  dependencies:
    storage:
      inCluster:
        deletionPolicy: Delete
        pvcDeletion: true

So here is how to fix this, you should add the deletionPolicy & pvcDeletion values to apply you milvus CR again, and then delete it, and wait for the PVCs to be cleaned, and then create the Milvus CR once more.

I already said that I had deleted them and restarted. Do you try another reason why it could not be working?

@Tanchwa I'm quite sure about the reason, did you set your CR like below before you delete it ?
spec:
  dependencies:
    storage:
      inCluster:
        deletionPolicy: Delete
        pvcDeletion: true

If not, use helm list & kubectl get pvc to check the left behind things in your kubernetes.
Use helm uninstall xxx & kubectl delete pvc xxx to clean them up.

@Tanchwa Oh, there's a typo in your manifest, it's persistence not persistance

Jesus, can you feel me facepalm through the internet?

Yes buddy, it happens...

authors: Tanchwa haorenfsa

repo: zilliztech/milvus-operator


text:
🛑 Minecraft Server (Main) is down

In 454ae93, Minecraft Server (Main) (articles-permit.gl.at.ply.gg) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Minecraft Server (Main) is back up in 324fc3c after 3 hours, 52 minutes.

repo: zimavi/uptime-webs