Lua plugin error: undefined symbol: lua_gettop

I'm trying to use redis with lua plugin:
require('redis')
local redis = require 'redis'
local client = redis.connect('<IP_ADDRESS>', 6379)
local response = client:ping()

....

and got the error message below:
ERROR: [ReverseProxy] failed to add remap rule at /opt/ats/etc/trafficserver/remap.config line 196:
Failed to create instance for plugin "/opt/ats/libexec/trafficserver/tslua.so":
[ts_lua_add_module] lua_pcall /opt/ats/etc/trafficserver/script/test_global_hdr.lua failed:
error loading module 'socket.core' from file '/usr/local/lib/lua/5.1/socket/core.so':
/usr/local/lib/lua/5.1/socket/core.so: undefined symbol: lua_gettop

require('redis')  works in luajit.
How can i fix that ?
Version :
Trafficserver 8.0
Luajit 2.0.5
Lua 5.1.4
OS:
CentOS 7

There is another person on the mailing list asking a similar question.
Let me try it out tonight and see.

Ok. I tried to reproduce this with a fresh ubuntu genial vm (latest TS on master, luajit-2.0.5, luasocket-2.0.2, redis-lua-2.0.4) and yes, I can reproduce that.
Here are some points

I have used luasocket before and it worked. The reason is that luasocket is compiled to not dynamic linked to Lua library. Instead it relied on the caller of luasocket to have those symbols/references exposed. So it worked great for previous version of ATS because we were bringing in luajit into the core. Starting a few months ago, we stopped doing that and instead we make the ats lua plugin to have a dynamic link requirement instead. So if you "require" luasocket in your lua script for the ats lua plugin, you will get the above error during start up

I get it to work with my fresh new setup by compiling luasocket differently. Specifically inside src/Makefile, I added "-lluajit-5.1 -ldl -lm" at the end to all the LD lines that is responsible for generating the shared object (*.so).

Please let me know if it does not work.

@shukitchan I ran in to this with the lua crypto library as well.  So another possible solution, if we add
lua_tslua_la_LDFLAGS += -lluajit-5.1
To the tslua Makefile.inc that forces the tslua.so to actually link against the luajit.so

You should not need that in lua_tslua_la_LDFLAGS because we have this - https://github.com/apache/trafficserver/blob/master/build/luajit.m4#L88
I tried out luacrypto-0.3.2 and I do a cmake and then make to generate the "so". I did a ldd and notice that it is dynamically linked to the lua library I installed on my vm (with ats master branch installed). And as expected, it won't work with the ats lua plugin. I changed to make it dynamically linked to luajit instead and it worked fine with the ATS lua plugin after that.
@ezelkow1 , I don't understand how your problem got fixed still. When I run ldd against tslua.so , I can see luajit as a dependency. Also I think by default we need luajit installed to have tslua.so to be generated. Perhaps you can tell me a bit more on how your build env generates tslua.so ?

just saw your message on irc. so I think we are good then.

@shukitchan @ezelkow1 could you give me a hand to figure out what I'm missing? my build is still not working. The entire build process could be seen in this dockerfile.
In short, I (think) patched the luasocket src/makefile as @shukitchan suggested and also tried to patch the tslua makefile following @ezelkow1 but the tslua plugins still giving me the symbol error.
If I ran a simple lua test script using both lua or luajit I connect successfully into redis (making me belive that luasocket+redis-lua were installed ok).
However my lua script plugin still raising the error: ERROR: [ts_lua] lua_pcall failed: error loading module 'socket.core' from file '/usr/local/lib/lua/5.1/socket/core.so':         /usr/local/lib/lua/5.1/socket/core.so: undefined symbol: lua_gettop.
I'm using ATS 8.0.3, LuaJIT 2.0.5, LuaRocks 3.0.4 and Luasocket 3.0.rc1 (Luasocket is being compiled using luarocks after patching the src/makefile).
If needed you an replicate the error by cloning my repo and build/running ats with docker-compose. All my testes were done from inside the docker container (docker-compose up -d && docker-compose exec trafficserver /bin/bash)
I really appreciate any help. =) cheers.

For us it was the luacrypto library. What I had to do was start building the luacrypto library, with LDFLAGS=-lluajit-5.1. I then package that up in to our ats rpm so it gets distributed with it. Then had to modify the systemd script to set Environment=LUA_CPATH=/your/installpath/forlua/plugins, i.e. for us it was trafficserver/lua/crypto.so for the crypto plugin we packaged with our rpm

Finally I've figure it out! =) I was patching the luasocket src/makefile to make it properly export the symbols as you guys pointed out. But I was still using luarocks to build it and for some reason luarocks does not build it apply the patched parameters (not sure but it seems it build it for an invalid "unix" target instead of "linux").
To fix it what I did is to first  install luasocket and luaredis using luarocks (just because easier to install and control dependencies) and after that I manually build luasocket from source with patched src/makefile (make linux && make install) effectively replacing the socket.so libs with a properly built version.
Cheers =)

@shukitchan i did'nt understood this line, can you please help?
I get it to work with my fresh new setup by compiling luasocket differently. Specifically inside src/Makefile, I added "-lluajit-5.1 -ldl -lm" at the end to all the LD lines that is responsible for generating the shared object (*.so).

So should i build luasocket(in my use case it is lpeg) from the source code and edite the makefile with this line "-lluajit-5.1 -ldl -lm" ?

Yes. That's right.

@shukitchan Actually in the lpeg library source code there is no src/Makefile, so how should i do it : https://github.com/luvit/lpeg

@Bharat786 let's keep the conversation in #8222


Ethereum types refactor

@NikVolf @rphmeier @tomusdrw tell me what you think. to see the interface do cargo doc -p ethereum-types

wow, but we had been using bigint from crates.io for quite a time already, no?

@debris
we already have parity-hash crate with dependency on bigint, why no just use that?

Hash really should be in separate crate
This crate is just for integer arithmetic and stable for a long time

It is in a separate crate:
bigint - impl_uint macro
fixed-hash - impl_hash macro
ethereum-types - Ethereum-specific instances of those types (both H256 & U256)

Yeah, but why in this repository?

@NikVolf the idea for this pr is to separate uint/hash crates from their usage. Mostly to clean existing architecture where different crates where using different hashes and where it is weird that some types are implemented by default why the others are not
eg. H256, H1025, U256 are implemented but, it's not clearly described why U1024 is not.
Also, I believe that reusing hash and integer type is now easier for polkadot and other projects
I made a pr in this repo, cause I wanted to put it up for a discussion. I agree, maybe we should have a new repo for it? or rename this one?

@debris
I totally agree with your motivation,
code looks great, i just think bigint should be left alone as a stable library in this dedicated repository


Add default protocol for the tip url

ref #765,
ref #767

I like the suggestion, but there are a lot of pages on the web still not using SSL (also a lot of tips in superhero are such).
Let's support both http:// and https:// for now, and consider everything else invalid.
When we extend the tipping protocol to support other links such as magnet we can extend the list of supported protocols.

whats the state of this?


Verify potential race conditions on microservices launching

[ ] analyse potential places on the sequence diagram that race conditions might occur

Are you done with this?

We wait for peerd hello now until we proceed.


The error during the discovery phase

-- Process 1 terminated with the following error:
Traceback (most recent call last):
  File "/disk/work/slcheng/anaconda3/envs/pt10/lib/python3.8/site-packages/torch/multiprocessing/spawn.py", line 59, in _wrap
    fn(i, *args)
  File "/disk/work/slcheng/anaconda3/envs/pt10/lib/python3.8/site-packages/detectron2/engine/launch.py", line 126, in _distributed_wor
ker
    main_func(*args)
  File "/home/slcheng/Documents/code/RNCDL/tools/train_discovery.py", line 181, in main
    do_train(args, cfg)
  File "/home/slcheng/Documents/code/RNCDL/tools/train_discovery.py", line 152, in do_train
    trainer.train(start_iter, cfg.train.max_iter)
  File "/disk/work/slcheng/anaconda3/envs/pt10/lib/python3.8/site-packages/detectron2/engine/train_loop.py", line 159, in train
    self.after_train()
  File "/disk/work/slcheng/anaconda3/envs/pt10/lib/python3.8/site-packages/detectron2/engine/train_loop.py", line 168, in after_train
    h.after_train()
  File "/disk/work/slcheng/anaconda3/envs/pt10/lib/python3.8/site-packages/detectron2/engine/hooks.py", line 557, in after_train
    self._do_eval()
  File "/disk/work/slcheng/anaconda3/envs/pt10/lib/python3.8/site-packages/detectron2/engine/hooks.py", line 525, in _do_eval
    results = self._func()
  File "/home/slcheng/Documents/code/RNCDL/tools/train_discovery.py", line 140, in <lambda>
    hooks.EvalHook(cfg.train.eval_period, lambda: do_discovery_test(cfg, model)),
  File "/home/slcheng/Documents/code/RNCDL/tools/train_discovery.py", line 45, in do_discovery_test
    instantiate(cfg.discovery_test_loader_knowns),
  File "/disk/work/slcheng/anaconda3/envs/pt10/lib/python3.8/site-packages/detectron2/config/instantiate.py", line 77, in instantiate
    return cls(**cfg)
  File "/disk/work/slcheng/anaconda3/envs/pt10/lib/python3.8/site-packages/detectron2/config/config.py", line 210, in wrapped
    return orig_func(*args, **kwargs)
TypeError: build_detection_test_loader() got an unexpected keyword argument 'batch_size'

Hello, I encountered the above error when running the supervised experiment, and I found the funcion "build_detection_test_loader() got an unexpected keyword argument 'batch_size'". Did you know how to solve this problem? Thanks

Hi chengsilin,
The problem is that you probably didn't do the inplace modifications of Detectron2 that we require. Could you please check this section of our ReadMe file and let me know if it works.

Thank you for your seggestions! I have sloved it now!


NG: convert on setattr by default

Not doing that from the get-go was an oversight.
Are we OK with this?
Fixes #835

Yuck, looks like our doctests saved us from a performance regression.
This is gonna be more work than it looked like.

Looks like we've needlessly added a cached setattr to all classes that were derived from a slotted one (instead of just frozen ones). The setattr wasn't used, but it was a waste of space.


Feature Key file - ensure that the decoding works more robustly

If the Feature key file is encoded in Base-64 with line breaks, then extraction fails at the first line break.

Possible solution - use regex pattern to check spaces in FeatureKeyFile field
Proposed solution [to be tested]
  FeatureKeyFile:
    Description: Base64 encoding of the feature key file. This is the Aerospike key to use for this deployment. Keeping this blank works only for single node cluster.
    Type: String
    Default: ""
    ConstraintDescription: Must no have spaces in beginning or end
    AllowedPattern: '^[^\s].+[^\s]$'


🐛 extra="allow"/"ignore" doesn't seem to be working with dataclasses

Initial Checks

[X] I have searched GitHub for a duplicate issue and I'm sure this is something new
[X] I have searched Google & StackOverflow for a solution and couldn't find anything
[X] I have read and followed the docs and still think this is a bug
[X] I am confident that the issue is with pydantic  (not my code, or another library in the ecosystem like FastAPI or mypy)

Description
I am trying to ignore/silently pass the extra argument I receive while constructing a dataclass.
I am trying to use extra="ignore" and extra="allow" in my dataclass config - but it doesn't seem to work as expected.
Example Code
from pydantic.dataclasses import dataclass

class DataclassConfig:
    arbitrary_types_allowed = True
    extra = "allow"

@dataclass(config=DataclassConfig)
class MyDataclass:
    name : str
    age: int

my_obj = MyDataclass(**{"name": "John WIck", "age": 12})
print(my_obj)
>>> MyDataclass(name='John WIck', age=12)

my_obj = MyDataclass(**{"name": "John WIck", "age": 12, "gender": "M"})
print(my_obj)
>>> TypeError: __init__() got an unexpected keyword argument 'gender'

class DataclassConfig:
    arbitrary_types_allowed = True
    extra = "ignore"

@dataclass(config=DataclassConfig)
class MyDataclass:
    name : str
    age: int

my_obj = MyDataclass(**{"name": "John WIck", "age": 12})
print(my_obj)
>>> MyDataclass(name='John WIck', age=12)

my_obj = MyDataclass(**{"name": "John WIck", "age": 12, "gender": "M"})
print(my_obj)
>>> TypeError: __init__() got an unexpected keyword argument 'gender'

Python, Pydantic & OS Version
pydantic version: 1.9.0
pydantic compiled: True
install path: /opt/anaconda3/envs/llm-env/lib/python3.8/site-packages/pydantic
python version: 3.8.12 (default, Oct 12 2021, 06:23:56)  [Clang 10.0.0 ]
platform: macOS-10.16-x86_64-i386-64bit
optional deps. installed: ['typing-extensions']

Affected Components

[ ] Compatibility between releases
[ ] Data validation/parsing
[ ] Data serialization - .dict() and .json()
[ ] JSON Schema
[X] Dataclasses
[ ] Model Config
[ ] Field Types - adding or changing a particular data type
[ ] Function validation decorator
[ ] Generic Models
[ ] Other Model behaviour - construct(), pickling, private attributes, ORM mode
[ ] Settings Management
[ ] Plugins and integration with other tools - mypy, FastAPI, python-devtools, Hypothesis, VS Code, PyCharm, etc.

It has been added in v1.10 (see https://github.com/pydantic/pydantic/blob/main/HISTORY.md#v1100a1-2022-08-22). It's still in beta but should be released soon


Works: next.js Error on IE 10

TypeError: Unable to get property 'groupedVenues' of undefined or null reference
Looks like next.js will serve JS to IE10, whereas on the old app we don't.
Not sure if that's why this error occurs, but it''s flagged it, and we'll need to fix it before swapping over.

[ ] TypeError: Unable to get property 'groupedVenues' of undefined or null reference

This seems to be something to do with babel-plugin-transform-class-properties, which doesn't seem to work properly for the OpeningHours.js - at least writing it out longhand with constructor removes the error. Still looking at how to get the plugin working.
There are also other errors in IE10:

[ ] Page not displaying correctly (poss. CSS loading issue)
[ ] Prop did not match server errors - related to svg
[ ] Uncaught (in promise)TypeError: Invalid calling object
at g (https://cdn.polyfill.io/v2/polyfill.js?features=default,Array.prototype.find,Array.prototype.includes,WeakMap:2995:1815)


Created 'edit_task' view

Fixes #117 #113
When entering the single task view -> click on the edit button redirect you to an edit task page.

created the HTML page edit task, based on the new task form
linked the button from the single task view to the edit task page
created the functions to render the page -

edit_single_task: to render the page
update_task: if the method is 'POST', the function will update the task
task_validate : validate that the new details is correct , it is by the created task function

You can see the changes here:
https://www.loom.com/share/649b51f5af614d1a88ce46886e0399a7

Please CR but do not merge because it has conflicts with PR #134

Great job !! maybe consider to redirect to the task's view template once the update succeed (instead of display a success message and staying in the edit page)

just say to where? to the single task page ?

I know that I already approved here, but as discussed in today's, tests should be added here. 😢

I know that I already approved here, but as discussed in today's demo, tests should be added here. 😢

DONE!

Change the description's first line to
Fixes #117
Fixes #113

Just for the auto-close

Can a manager from a different team edit the task?

Can a manager from a different team edit the task?

yes, I'll fix it today

Can a manager from a different team edit the task?

No .


cleanup: delete extra line

This change is

Did you mean to include both commits in this PR?

@coryan deleting one line is no easy task for me....


healthchecks: 2.2.1 -> 2.4.1, nixos/healthchecks: automatically invoke sudo in the wrapper

Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Thanks! You'd need to adapt the nixos test for this service as well with the new sudo. It tests for that because an earlier version caused silent failures in healthchecks-manage shell, which is used by some of the bg jobs iirc.


V0.18.1

updates android, libraries and bitcoin/knots/liquid daemons

I think even if we merge this we can't release soon as there's a bunch of bugs in master to be dealt with

Attaching a signed RC
RC.zip

@johnyukon21
Do you want to give it a try/look? if there's no blockers we can release

ack 2726cc4


[problem] after updating from 1.1 to 1.3

I created a few posts on xda, I am on version 1.3 & had updated from 1.1. I have a Samsung A50 A10 one ui 2.0, use nova launcher & Klwp & tasker. All permissions have been given, I have done a fresh install, wiped cache & data, restarted. Everything I have read or knew of, I have done.
The app is working, but it isn't, I can not change any settings as the app is stuck at "connection to services" but as I have said it's still working, apps that I had forced via 1.1 are still in dark mode (after I run adb Wifi cmd). The big one for me is Amazon shopping app, because of late night window shopping lol.
Is there anything I can do to fix the problem? Or something I did that is causing it?
Apologies for posting in the wrong github, somehow my wires got crossed, and I posted in tap tap
Edit:
Been about a month, I am not bitchin or complaining, I am just wondering if at the very least I can get a link to version 1.1 apk? Or is it right in front of me and I don't see it?

You can find the old versions here: https://www.apkmirror.com/apk/mighty-quinn-apps/darq/
As for the bug, I can't really do much about it without having access to the device. Service connection using the root services concept can be buggy on some devices, and very hard to debug if it can't be reproduced. Could you try 1.2 as well, see if it's new in 1.3 or also in that version?

Thank you, I think I was confused on the version I was using BTW,
I am not rooted, so 1.2 seems to be the version that works for me. But you
can close the report, as 1.2 fixed the issue I was having.
Thank you for the link, time, and a great app!
Bradford Adams
On Wed, Nov 25, 2020, 5:09 PM Kieron Quinn<EMAIL_ADDRESS>wrote:

You can find the old versions here:
https://www.apkmirror.com/apk/mighty-quinn-apps/darq/
As for the bug, I can't really do much about it without having access to
the device. Service connection using the root services concept can be buggy
on some devices, and very hard to debug if it can't be reproduced. Could
you try 1.2 as well, see if it's new in 1.3 or also in that version?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/KieronQuinn/DarQ/issues/19#issuecomment-733967858,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABMB63Q3SCMVLS6ZLTCZ3RTSRV6DLANCNFSM4SZ3LJYA
.


fix typo(two side -> many side)

@neednlab : Thanks for your contribution! The author(s) have been notified to review your proposed change. @peter-myers

@neednlab : Thanks for your contribution! The author(s) have been notified to review your proposed change. @peter-myers

Looks good. Thanks @neednlab.

Looks good. Thanks @neednlab.


LCD methods created.

I made LCD methods, so please review and merge it if you like.

Thanks!
I will update the documentation and pin your name in the changelog!
Thanks!


fix recursive bug by refactoring transformWorkToStep to use javascript generators

I found a bug in the recursion where not all of the JSON returned from the server was getting transformed into form elements in the react-json-schema-form.
The best way I can think of solving this (besides the server maybe returning a simpler JSON) is to use javascript generator functions that have a unique suspend and resume quality that is ideal for this very complex model.
The form is complex as well with a nested stepper so for now, I think this is the best solution.
Below is a screenshot of the nested JSON and the correctly rendered form:

I think the use of generators is an elegant solution here, I like it.
The only drawback can be in the future - if we hand the project over and a less experienced maintainer will come. The generators are not so often used. However it's part of the standard and good fit here, so let's use it.


[Feature Request] support “onContinuousPress” GestureDetectore

Use case
Add a new property to GestureDetector
"onContinuousPress" that will receive a (Function, Duration) and it will execute the function repeatedly once every duration as long as the finger (or the mouse click etc...) is in contact with the button and stop executing the given function once the finger is off the button.
Right now this behaviour is achieved using combination of "onTapDown" and "onTapUp"
it will be nice to have this feature as a built in one.

Right now, this behaviour can be implemented by combining 2 separate properties of the GestureDetector, as follow:
`var _timer;
void _startTimer(Function func, {int dealy = 100}) {
timer = Timer.periodic(Duration(milliseconds: dealy), () => func());
}
void _stopTimer() {
_timer.cancel();
}
GestureDetector(
child: Container(
child: Icon(
Icons.arrow_downward,
),
),
onTapDown: (details) => _startTimer(_refToFunc, dealy: 50),
onTapUp: (details) => _stopTimer(),
);`

Right now, this behaviour can be implemented by combining 2 separate properties of the GestureDetector, as follow:
var _timer;

void _startTimer(Function func, {int dealy = 100}) {
timer = Timer.periodic(Duration(milliseconds: dealy), () => func());
}

void _stopTimer() {
_timer.cancel();
}

GestureDetector(
child: Container(
child: Icon(
Icons.arrow_downward,
),
),
onTapDown: (details) => _startTimer(_refToFunc, dealy: 50),
onTapUp: (details) => _stopTimer(),
);

But still I think this a common use case that needs to be built in to Flutter.

It seems to me that this feature can be implemented with your approach with decent amount of code. It would take a great amount of demand to convince us to imbed this into the core framework.
I'm closing this issue. Feel free to follow up or reopen if necessary.


[BUG] infinigen.org has default opengraph params set

Describe the bug
Incorrect open graph parameters on infinigen.org cause issues when sharing (to twitter, etc.) or airdrop properly.
It opens this page:
https://your-docusaurus-test-site.com/

Thanks for catching this! It's now fixed.


[New Feature] Add marquee component

先看一下在这里加一些性能对比图片ok吗，ok我就继续写了

https://fury.apache.org/docs/introduction/benchmark
there seems to be a performance related page here, something else should be put here or some introduction should be made here to direct the user to the performance introduction page
/cc @chaokunyang

https://fury.apache.org/docs/introduction/benchmark
there seems to be a performance related page here, something else should be put here or some introduction should be made here to direct the user to the performance introduction page
/cc @chaokunyang

Yes, maybe we can keep the work in performance page


engine: fix reopen failure.

I have restarted this PR's travis-CI several times, no error showed up again. Seems problem is fixed.
PTAL @siddontang @ngaut


Channel.SCHEDULE cpu usage

Hello,
When using Channel.select in the browser, I'm noticing high cpu usage.
Is this "expected" from the library / are there any best practices for this?
I was wondering if setImmediate is the way to go on browser environments.
I was hoping that await/async could help on this to avoid pulling..
thanks for the great work!

Hi @pedroteixeira - thanks - there's actually support for setImmediate, but it needs to be provided externally (e.g. it's the default in node or via polyfill). See here: https://github.com/thi-ng/umbrella/blob/master/packages/csp/src/channel.ts#L233
The CPU usage should only be high for ops involving select() or merge(). I've noticed it too (not just in this implementation), but I just didn't see a way around it apart from increasing the timeout period or maybe adding an additional arg to select to make it configurable on a case-by-case basis (i.e. use longer timeout by default, but allow higher throughput if needed).

thanks for explaning, right now I'm considering setting for a browser scope something like this:
Channel.SCHEDULE = f => setTimeout(f, 1000);
Perhaps having something like a "onClose promise" could be used to get notified about closed channel. I don't think I had this issue with this other library https://github.com/AppliedMathematicsANU/plexus-csp/ - perhaps can give some ideas :)

You can do this, but I'd say 1 second is waaayyy too long, for normal use cases at least. You'll then wait at least this long if none of the input channels given to select are readable in the first round. A 16ms (or less really) timeout should be sufficient (IMHO) and give you only a single frame delay (if used for UI purposes). Also, thanks for the link to the other lib, will check it out! I only had prior experience with ClojureScript's core.async and that too had similar behavior...
As for the onclose promise - that's a good idea, but would not help in this specific case. The issue w/ select is that we need to repeatedly poll the input channel's readable & closed flags, but can only read / take a value from the first which becomes available. The high CPU load only happens if all inputs are producing values rather slowly/infrequently and/or a long timeout is used.
In my experience a better approach is to use short timeouts for select, and have another timeout in your processing loop, like so. Channel.timeouton its own is super cheap (just a promise resolved via native setTimeout...
(await () => {
    while(true) {
        let [val, ch] = await Channel.select([a,b, Channel.timeout(1)]);
        if (val === undefined) break;
        // do something
        await Channel.timeout(16);
    }
})();

Other ideas I've already semi-tried and might re-integrate:

use an exponentially increasing delay over time. i.e. double the delay between polling rounds every few rounds (up to a maximum period, of course :)
use a select internal promise to handle the polling and then once a value is read (or an input closed) resolve the main promise. In my earlier tests this didn't seem to show much lower CPU usage though and the current implementation is more simple... will look into it again asap

Thinking about experimenting a different approach without select for my case here with "merge":
export function mergeChannels(chans: Array<Channel<any>>, out?: Channel<any>, close = true, named = false) {
  out = out || new Channel<any>();
  chans.forEach(inChannel => {
    inChannel.consume(x => {
      if (out.isClosed()) {
        return inChannel.close();
      }
      return out.write(named ? [inChannel.id, x] : x);
    });
  });
  return out;
}

One frequent doubt I have is how best handle when channels are closed.. Sometimes it feels odd only handling isClosed only in a future write.


Opportunity templates and pizzas

Adds templates to the Opportunity meetup creation page. The default software provides: 4 kinds of pizzas, 5 days work week and 7 days week. The software customized for xymus.net also provides: pizzas special LATECE and meeting hours for UQAM Sciences.
It is already available at http://xymus.net/opportunity/.

+1
I like the detail of the separate local-latece-uqam things from the general templates in the business logic.

:shipit: !
But why translate the name of the software to Opportunité in French ? Should not the name of the software stay the same, regardless of the language ?

Loi 101?
Le jeu. 25 juin 2015 10:19, Lucas Bajolet<EMAIL_ADDRESS>a
écrit :

[image: :shipit:] !
But why translate the name of the software to Opportunité in French ?
Should not the name of the software stay the same, regardless of the
language ?
—
Reply to this email directly or view it on GitHub
https://github.com/privat/nit/pull/1539#issuecomment-115273408.

If we go all the way through this path then a well-known OS should change its name to Fenêtres in its French distribution, but this would only make it even more ridiculous :)
I do think the name should be uniform for all languages, but I'm not that shocked after all, we can name it Opportunité, I don't mind, it just caught my attention

The pun is still here. So I'm fine. I don't know how it will be in the German, Japanese and Polish.


Some issues by Vinod sir

Describe the bug

inoice transaction pe click karne par side panel me ledger option aa raha hai par receipt and discount transaction pe click pe ledger nahi aa rha
https://ac-74.s1.easycloudbooks.com/TransactionPrint?crids=HAMzzG-7tEqpwQbiO4JlmA period ko top pe ledger ke neeche centre pe rakho
print date ko neeche rakho and woh bhi ek hi line pe
ledger ko A4 me print leke dekho mere hisaab se problem aayega

Screenshots
If applicable, add screenshots to help explain your problem.

There is not any ledger showing

https://www.berrycast.com/conversations/e2157951-2c2a-51b4-b7f1-16b01d122df8


[IS-698] - Remove redundant Update matcher

We replaced this Update matcher with the functional UpdateWithFunc matcher in some places and should therefore replace it everywhere and remove the (fundamentally) broken Update matcher.

@JoelSpeed: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pull-wave-test-1.12
1e72a36e2fd9ef1266324777a6523b5ea83d2cb5
link
/test 1.12

Full PR test history

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@JoelSpeed: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pull-wave-test-1.12
1e72a36e2fd9ef1266324777a6523b5ea83d2cb5
link
/test 1.12

pull-wave-build
1e72a36e2fd9ef1266324777a6523b5ea83d2cb5
link
/test build

Full PR test history

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@JoelSpeed: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pull-wave-test-1.12
1e72a36e2fd9ef1266324777a6523b5ea83d2cb5
link
/test 1.12

pull-wave-build
1e72a36e2fd9ef1266324777a6523b5ea83d2cb5
link
/test build

pull-wave-test-1.13
1e72a36e2fd9ef1266324777a6523b5ea83d2cb5
link
/test 1.13

Full PR test history

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@JoelSpeed: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pull-wave-test-1.12
1e72a36e2fd9ef1266324777a6523b5ea83d2cb5
link
/test 1.12

pull-wave-build
1e72a36e2fd9ef1266324777a6523b5ea83d2cb5
link
/test build

pull-wave-test-1.13
1e72a36e2fd9ef1266324777a6523b5ea83d2cb5
link
/test 1.13

pull-wave-test-1.11
1e72a36e2fd9ef1266324777a6523b5ea83d2cb5
link
/test 1.11

Full PR test history

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@JoelSpeed: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pull-wave-test-1.12
1e72a36e2fd9ef1266324777a6523b5ea83d2cb5
link
/test 1.12

pull-wave-test-1.13
1e72a36e2fd9ef1266324777a6523b5ea83d2cb5
link
/test 1.13

pull-wave-test-1.11
1e72a36e2fd9ef1266324777a6523b5ea83d2cb5
link
/test 1.11

pull-wave-build
1ce7c16b6dedcd17759944a94d4b08d6e64905eb
link
/test build

Full PR test history

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@JoelSpeed: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pull-wave-test-1.12
1e72a36e2fd9ef1266324777a6523b5ea83d2cb5
link
/test 1.12

pull-wave-test-1.11
1e72a36e2fd9ef1266324777a6523b5ea83d2cb5
link
/test 1.11

pull-wave-build
1ce7c16b6dedcd17759944a94d4b08d6e64905eb
link
/test build

pull-wave-test-1.13
1ce7c16b6dedcd17759944a94d4b08d6e64905eb
link
/test 1.13

Full PR test history

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@JoelSpeed: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pull-wave-test-1.12
1e72a36e2fd9ef1266324777a6523b5ea83d2cb5
link
/test 1.12

pull-wave-test-1.11
1e72a36e2fd9ef1266324777a6523b5ea83d2cb5
link
/test 1.11

pull-wave-build
1ce7c16b6dedcd17759944a94d4b08d6e64905eb
link
/test build

pull-wave-test-1.13
1ce7c16b6dedcd17759944a94d4b08d6e64905eb
link
/test 1.13

pull-wave-test-1.14
1ce7c16b6dedcd17759944a94d4b08d6e64905eb
link
/test 1.14

Full PR test history

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@JoelSpeed: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pull-wave-test-1.11
1e72a36e2fd9ef1266324777a6523b5ea83d2cb5
link
/test 1.11

pull-wave-build
1ce7c16b6dedcd17759944a94d4b08d6e64905eb
link
/test build

pull-wave-test-1.13
1ce7c16b6dedcd17759944a94d4b08d6e64905eb
link
/test 1.13

pull-wave-test-1.14
1ce7c16b6dedcd17759944a94d4b08d6e64905eb
link
/test 1.14

pull-wave-test-1.12
1ce7c16b6dedcd17759944a94d4b08d6e64905eb
link
/test 1.12

Full PR test history

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@JoelSpeed: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pull-wave-test-1.11
1e72a36e2fd9ef1266324777a6523b5ea83d2cb5
link
/test 1.11

pull-wave-test-1.13
1ce7c16b6dedcd17759944a94d4b08d6e64905eb
link
/test 1.13

pull-wave-test-1.12
1ce7c16b6dedcd17759944a94d4b08d6e64905eb
link
/test 1.12

pull-wave-test-1.14
8479e55b7c96aa212aec18b7bd173125206cc78c
link
/test 1.14

Full PR test history

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@JoelSpeed: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pull-wave-test-1.11
1e72a36e2fd9ef1266324777a6523b5ea83d2cb5
link
/test 1.11

pull-wave-test-1.13
1ce7c16b6dedcd17759944a94d4b08d6e64905eb
link
/test 1.13

pull-wave-test-1.14
8479e55b7c96aa212aec18b7bd173125206cc78c
link
/test 1.14

pull-wave-test-1.12
8479e55b7c96aa212aec18b7bd173125206cc78c
link
/test 1.12

Full PR test history

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@JoelSpeed: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pull-wave-test-1.11
1e72a36e2fd9ef1266324777a6523b5ea83d2cb5
link
/test 1.11

pull-wave-test-1.14
8479e55b7c96aa212aec18b7bd173125206cc78c
link
/test 1.14

pull-wave-test-1.12
8479e55b7c96aa212aec18b7bd173125206cc78c
link
/test 1.12

pull-wave-test-1.13
8479e55b7c96aa212aec18b7bd173125206cc78c
link
/test 1.13

Full PR test history

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@JoelSpeed: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pull-wave-test-1.11
1e72a36e2fd9ef1266324777a6523b5ea83d2cb5
link
/test 1.11

pull-wave-test-1.14
8479e55b7c96aa212aec18b7bd173125206cc78c
link
/test 1.14

pull-wave-test-1.12
8479e55b7c96aa212aec18b7bd173125206cc78c
link
/test 1.12

pull-wave-test-1.13
8479e55b7c96aa212aec18b7bd173125206cc78c
link
/test 1.13

pull-wave-verify-manifests
433d76d5af0cc0ee0954b3f06420bcdcf33a2179
link
/test verify-manifests

Full PR test history

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test verify-manifests

@JoelSpeed: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pull-wave-test-1.11
1e72a36e2fd9ef1266324777a6523b5ea83d2cb5
link
/test 1.11

pull-wave-test-1.12
a24e904e1dfd560884bfcbd1b9be80e154eb8eec
link
/test 1.12

Full PR test history

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@JoelSpeed: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pull-wave-test-1.11
1e72a36e2fd9ef1266324777a6523b5ea83d2cb5
link
/test 1.11

pull-wave-test-1.12
a24e904e1dfd560884bfcbd1b9be80e154eb8eec
link
/test 1.12

pull-wave-test-1.13
385de05367b6750df9e53d6aa97f25faac7ecbbc
link
/test 1.13

Full PR test history

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test 1.13

@JoelSpeed: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pull-wave-test-1.11
1e72a36e2fd9ef1266324777a6523b5ea83d2cb5
link
/test 1.11

pull-wave-test-1.13
385de05367b6750df9e53d6aa97f25faac7ecbbc
link
/test 1.13

pull-wave-test-1.12
85aa14a8ce5441160ff17152c67a9ebd8aca5fbb
link
/test 1.12

Full PR test history

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test 1.13

/test 1.12


Pick up TS 4.9.5

Tracks picking up the Ts 4.9.5 recovery build
Includes:

https://github.com/microsoft/TypeScript/pull/52419
https://github.com/microsoft/TypeScript/pull/52426

To verify, open a TS file and check the  TS version in the language status item


pull request for e2e test at 12/03/2016 01:26:03

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


Changed missing german translation

1. Why is this change necessary?
Because it's possible that a german shopware translation displays english messages which should not happen.
2. What does this change do, exactly?
Adds missing german translation for 3 text snippets
3. Describe each step to reproduce the issue or behaviour.
Go to the article list, activate the split-view mode and try to activate the split-view mode again. You will get an english message stating that it's not possible to activate split view mode again.

4. Please link to the relevant issues (if any).

5. Which documentation changes (if any) need to be made because of this PR?

6. Checklist

[ ] I have written tests and verified that they fail without my change
[X] I have squashed any insignificant commits
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[X] I have read the contribution requirements and fulfil them.

Hey @entensee403,
can you sign the cla and change the target branch to 5.6?

Opened a new PR: https://github.com/shopware/shopware/pull/2225


Can't breed moos.

[x] I am using a release version of the mod
[x] I have mods that integrate with this installed:

[x] Tinker's Construct
[x] Mine Factory Reloaded
[x] Mine Addons
[ ] Moo Fluids
[x] Waila
[x] Avaritia

[x] I also have other mods installed
[x] I have searched for this issue previously and it was either (1) not previously reported, or (2) previously fixed and I'm having the same problem.
[ ] I am crashing and can provide my crash report(s)

Additional Information

[ ] Java Version:

[ ] Java 6
[ ] Java 7
[x] Java 8

[ ] Minecraft Version:

[x] 1.10.2

Issue Description
I am trying to breed Refined Fuel Moos, I have a bunch of them but Mini Wheat doesn't seem to work 99% of the time. I have to feed about 20 Mini Wheat to two Moos each and then they might start breeding.
I am playing FoolCraft 2.

Reproduce Steps
Try to breed Refined Fuel Moos.

Additional Information
None.

@liquid600pgm I'm going to look into it as soon as I can, thank you for pointing this out.


Fast path monitoring with open scale gui

Looks like travisCI failed:
https://travis-ci.com/github/IBM/cloudpakfordata-telco-churn-workshop/jobs/322302658

closing here and working in upstream


Cannot read properties of undefined (reading 'createFromBlockArray')

i am using very basic sample from readme. it throws an exception 'Cannot read properties of undefined (reading 'createFromBlockArray')'
Example code:
`
const sampleMarkup =
'Bold text, Italic text<br/ >' +
'  ';
  const blocksFromHtml = htmlToDraft(sampleMarkup);
  const { contentBlocks, entityMap } = blocksFromHtml;
  const contentState = ContentState.createFromBlockArray(contentBlocks, entityMap);
  const editorState = EditorState.createWithContent(contentState);`

npm packages:
"@types/draft-convert": "^2.1.4",
"@types/html-to-draftjs": "^1.4.0",
"@types/react-draft-wysiwyg": "^1.13.4",
"@types/node": "^12.20.19",
"@types/react": "^17.0.16",
And how do display the image having base64 encoded bytes?

works fine.


chore: added widget binding accelerators in store

Description
For Entity binding success event, the accelerators from where the binding was originated has to be maintained. This PR solves that for 1 click binding and self use case. These params will be sent to same ENTITY_BINDING_SUCCESS event.
Limitations:

This PR has issue in resetting the set accelerators, as when the reset accelerator is called for the binding, it doesn't get set from the PostEvaluations saga.
One click binding when done with datasource then the event ENTITY_BINDING_SUCCESS is not called as the PostEvaluations saga is not called.
Need to implement binding accelerators for all the binding properties for one click which updates multiple other properties not just tableData.

Fixes #31175
Automation
/ok-to-test tags=""
:mag: Cypress test results

[!CAUTION]
If you modify the content in this section, you are likely to disrupt the CI result for your PR.

Summary by CodeRabbit

New Features

Introduced widget binding accelerators, allowing users to bind data to widgets more efficiently.

Enhancements

Improved data binding logic in the Widget Query Generator and Property Pane based on keyboard interactions.

Bug Fixes

Fixed issues related to widget data binding by implementing new actions and reducers.

Closing this PR as the issue is moved to product backlog.


feat: add ability to set small multiples domain for each row or column

Closes #947

Thanks for this pull request, really appreciate it. Here's some general bit of feedback:

I'm not keen on having the xDomainAccessor property as well as xDomain (and the same on y of course!). Could you make it so that the xDomain property can either accept a regular domain (i.e. an array of values), or a function which returns a domain? You'd have to modify your code so that domain is no longer re-bound from the underlying scale.
I'm not keen on the logic that creates component-scoped state variables xDomains / yDomains, which are then use by component-scoped functions. If any temporary state is required, my feeling is it should be scoped to the rendering function. Also, do you need to cache the domains? the domain accessors described in (1) will likely have very simple switch / case type logic, so I don't think you need to cache their output.

Finally, the example feels a bit weak, it doesn't look terribly different from the one above it! What about re-creating this one:
http://bl.ocks.org/mbostock/1157787
If you want to discuss any of the above, give me a shout. Definitely moving in the right direction.

Cheers Colin, I've removed the xDomains and yDomains from the component scope and updated the example. I'm unsure how I can avoid caching the domains since they're being used in a couple of different places (to generate each multiple and each axis).

Cool - thanks for the update. I'll take a look at this tomorrow :-)

Thanks for the updates, looking good :-)
I've made some additional changes in #963. Rather than caching the domains, I've made it easier to obtain the domain for a specific cell, allowing the removal of transient state.


Error when trying to instantiate environment.

Hello, I get the next error when I try to run an instance of the environment (env = gym.make("gvgai-aliens-lvl0-v0"))
Connecting to host <IP_ADDRESS> at port 52923 ...
Client connected to server [OK]
ERROR:root:module 'scipy.misc' has no attribute 'imread'
Traceback (most recent call last):
  File "/path_to_GVGAI_GYM/GVGAI_GYM/gym_gvgai/envs/gvgai/clients/GVGAI-PythonClient/src/utils/ClientCommGYM.py", line 305, in processLine
    self.sso.image = misc.imread(os.path.join(self.tempDir.name, 'gameStateByBytes.png'))
AttributeError: module 'scipy.misc' has no attribute 'imread'

I have Pillow installed. I'm running Python 3.7.3 and Ubuntu 18.04.
What can I do?

The new version of Scipy doesn't support imread anymore as they want you to just use Pillow of that. In the Ascii branch we have implemented the change but we have not pushed it to the main branch yet. If you are just working with the library you can change branches for now or you can use an older version of Scipy until we have a chance to merge a number of changes.


weaviate: 1.25.9 -> 1.26.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/weaviate/weaviate/releases.
meta.description for weaviate is: ML-first vector search engine
meta.homepage for weaviate is: https://github.com/semi-technologies/weaviate
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.25.12 with grep in /nix/store/3w9cllzkxyp6vghkkc19d20mcyay1lxy-weaviate-1.25.12
found 1.25.12 in filename of file in /nix/store/3w9cllzkxyp6vghkkc19d20mcyay1lxy-weaviate-1.25.12

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

weaviate

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/509ce64f87be560b28caa06bfc18dc42d93a9c1f#weaviate

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/3w9cllzkxyp6vghkkc19d20mcyay1lxy-weaviate-1.25.12
ls -la /nix/store/3w9cllzkxyp6vghkkc19d20mcyay1lxy-weaviate-1.25.12/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

weaviate

Maintainer pings
cc @dit7ya for testing.

Add a :+1: reaction to pull requests you find important.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/weaviate/weaviate/releases.
meta.description for weaviate is: ML-first vector search engine
meta.homepage for weaviate is: https://github.com/semi-technologies/weaviate
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.25.13 with grep in /nix/store/248xdmgqgmbsb4q2la91bvi9v2vccbrx-weaviate-1.25.13
found 1.25.13 in filename of file in /nix/store/248xdmgqgmbsb4q2la91bvi9v2vccbrx-weaviate-1.25.13

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

weaviate

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/c234828c551c277d70feecd5da7f599ba94e7a8a#weaviate

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/248xdmgqgmbsb4q2la91bvi9v2vccbrx-weaviate-1.25.13
ls -la /nix/store/248xdmgqgmbsb4q2la91bvi9v2vccbrx-weaviate-1.25.13/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

weaviate

Maintainer pings
cc @dit7ya for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/weaviate/weaviate/releases.
meta.description for weaviate is: ML-first vector search engine
meta.homepage for weaviate is: https://github.com/semi-technologies/weaviate
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.26.3 with grep in /nix/store/shnyvwazpb2i8y7w7gpngaz05xy6n2z9-weaviate-1.26.3
found 1.26.3 in filename of file in /nix/store/shnyvwazpb2i8y7w7gpngaz05xy6n2z9-weaviate-1.26.3

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

weaviate

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/af90e390944c2dff13cb1d8a7c24b9264be01b73#weaviate

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

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

weaviate

Maintainer pings
cc @dit7ya for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/weaviate/weaviate/releases.
meta.description for weaviate is: ML-first vector search engine
meta.homepage for weaviate is: https://github.com/semi-technologies/weaviate
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.26.4 with grep in /nix/store/mbyx0nrqdqfirkjhlln7jjp2svpypic9-weaviate-1.26.4
found 1.26.4 in filename of file in /nix/store/mbyx0nrqdqfirkjhlln7jjp2svpypic9-weaviate-1.26.4

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

weaviate

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/be6aec109c0ca0f42b2f5d535f59ab097c3fa89d#weaviate

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

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

weaviate

Maintainer pings
cc @dit7ya for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 335863 run on aarch64-darwin 1

1 package built:

weaviate


support set OPENAI BASE URL

support set OPENAI BASE URL

You can now set the BaseURL via the openAI options


kaplan_meier_fitter: RuntimeWarning: divide by zero encountered in log

When I try to calculate KM for
T = [0, 3.5232, 3, 2, 1, 2]
E = [1, 1, 0, 0, 1, 1]

I read the following warning:
.../kaplan_meier_fitter.py:97: RuntimeWarning: divide by zero encountered in log
  return (np.log(population - deaths) - np.log(population))

Are there any consequence and is there a way to fix?

Hey there, I actually fixed that in a recent change, but I have not released a new cut. One second...
Okay, I cut a new release, <IP_ADDRESS>, that handles these warnings (they are harmless btw)

Hey @CamDavidsonPilon , thank you so much! : )

...but now the same code trigger this error:
ax = kmf.plot(show_censors=True, ci_show=False)

  File "/.../plotting.py", line 292, in plot
    set_kwargs_color(kwargs)
  File "/.../plotting.py", line 229, in set_kwargs_color
    kwargs["ax"]._get_lines.get_next_color())
AttributeError: '_process_plot_var_args' object has no attribute 'get_next_color'

Is it due to new modifications?

Ah I believe i also deprecated some old versions of matplotlib - which version are you using?

I'm using matplotlib==1.5.3

shoot, hm, let me get this fixed asap

<IP_ADDRESS> was just released with a 🎩'd fix


Add weight_only support for PyTorch framework

Type of Change
feature
No API changed
Description
Add weight_only support for PyTorch framework
Expected Behavior & Potential Risk
the expected behavior that triggered by this PR
How has this PR been tested?
Quantized model with weight-only quantization successfully.

extension test：https://inteltf-jenk.sh.intel.com/view/nlp-toolkit-validation/job/nlp-toolkit-validation-top-mr-extension/1310/

Add a dependency: https://github.com/intel/intel-extension-for-transformers/pull/297

Coverage Drop
Unit Test failed with lines coverage decrease -2.310%
Unit Test failed with branches coverage decrease -4.126%
please add UT to cover newly-added modules. @PenghuiCheng


[Reviewed] [Gamepad] Simplify stick expressions

Changes

StickRotationValue is renamed StickAngle
AxisValue is split into StickX and StickY

Demo

https://github.com/GDevelopApp/GDevelop-examples/pull/529

StickX and StickY both have parameters Left and Right.
Please consider Up and Down for StickY.

Just a thing on naming. StickX and StickY both have parameters Left and Right. Please consider Up and Down for StickY.

It's about left and right sticks.


Ensure resulting cvsPreviousHash is strict in updateBlock

It is possible that updateBlock can return a ChainValidationState which contains thunks within its cvsPreviousHash :: !(Either GenesisHash HeaderHash) field.
Before the fix
This is the heap object representation of the cvsPreviousHash field after validating mainnet epoch no. 1 (notice the ThunkClosure):
ConstrClosure {info = StgInfoTable {entry = Nothing, ptrs = 1, nptrs = 0, tipe = CONSTR_1_0, srtlen = 1, code = Nothing}, ptrArgs = [0x0000004204429450], dataArgs = [], pkg = \"base\", modl = \"Data.Either\", name = \"Right\"}
|
`- ThunkClosure {info = StgInfoTable {entry = Nothing, ptrs = 1, nptrs = 0, tipe = THUNK_1_0, srtlen = 28157384, code = Nothing}, ptrArgs = [0x0000004204429528/1], dataArgs = []}
   |
   `- ConstrClosure {info = StgInfoTable {entry = Nothing, ptrs = 4, nptrs = 0, tipe = CONSTR, srtlen = 0, code = Nothing}, ptrArgs = [0x0000004204429568/1,0x00000042044295a0/1,0x00000042044295c0/1,0x00000042044295d8/1], dataArgs = [], pkg = \"cardano-ledger-<IP_ADDRESS>-GrvZSU1raNtyHMRMZltXs\", modl = \"Cardano.Chain.Block.Block\", name = \"ABlock\"}
      |
      +- ConstrClosure {info = StgInfoTable {entry = Nothing, ptrs = 6, nptrs = 0, tipe = CONSTR, srtlen = 0, code = Nothing}, ptrArgs = [0x0000004204429640/1,0x0000004204429658/1,0x0000004204429670/1,0x0000004204429688/1,0x00000042044296b0/1,0x00000042044296c8/1], dataArgs = [], pkg = \"cardano-ledger-<IP_ADDRESS>-GrvZSU1raNtyHMRMZltXs\", modl = \"Cardano.Chain.Block.Header\", name = \"AHeader\"}
      |  |
      |  +- ConstrClosure {info = StgInfoTable {entry = Nothing, ptrs = 2, nptrs = 0, tipe = CONSTR_2_0, srtlen = 0, code = Nothing}, ptrArgs = [0x00000042044297d8/1,0x00000042044297b0/1], dataArgs = [], pkg = \"cardano-binary-1.5.0-4JPaYj1JXNrBeSyDLJ1mHT\", modl = \"Cardano.Binary.Annotated\", name = \"Annotated\"}
      |  |  |
      |  |  +- ConstrClosure {info = StgInfoTable {entry = Nothing, ptrs = 0, nptrs = 1, tipe = CONSTR_0_1, srtlen = 0, code = Nothing}, ptrArgs = [], dataArgs = [764824073], pkg = \"base\", modl = \"GHC.Word\", name = \"W32#\"}
      |  |  |
      |  |  `- ConstrClosure {info = StgInfoTable {entry = Nothing, ptrs = 1, nptrs = 3, tipe = CONSTR, srtlen = 0, code = Nothing}, ptrArgs = [0x0000004204435ee8/3], dataArgs = [283535015952,22013,5], pkg = \"bytestring-<IP_ADDRESS>\", modl = \"Data.ByteString.Internal\", name = \"PS\"}
      |  |     |
      |  |     `- ConstrClosure {info = StgInfoTable {entry = Nothing, ptrs = 1, nptrs = 0, tipe = CONSTR_1_0, srtlen = 2, code = Nothing}, ptrArgs = [0x0000004204010000], dataArgs = [], pkg = \"base\", modl = \"GHC.ForeignPtr\", name = \"PlainPtr\"}
      |  |
      ...

We can see that the strictness annotation on the cvsPreviousHash :: !(Either GenesisHash HeaderHash) field at least guarantees that the Either value (in this case, the Right constructor) will be in WHNF. However, there's still the possibility for the GenesisHash or HeaderHash value to be lazy.
After the fix
No more ThunkClosure after validating mainnet epoch no. 1:
ConstrClosure {info = StgInfoTable {entry = Nothing, ptrs = 1, nptrs = 0, tipe = CONSTR_1_0, srtlen = 1, code = Nothing}, ptrArgs = [0x00000042044283f0/1], dataArgs = [], pkg = \"base\", modl = \"Data.Either\", name = \"Right\"}
|
`- ConstrClosure {info = StgInfoTable {entry = Nothing, ptrs = 1, nptrs = 0, tipe = CONSTR_1_0, srtlen = 0, code = Nothing}, ptrArgs = [0x0000004204428418], dataArgs = [], pkg = \"basement-0.0.10-2z2JaOuy7fVLQL3Bi1dEbr\", modl = \"Basement.Block.Base\", name = \"Block\"}
   |
   `- ArrWordsClosure {info = StgInfoTable {entry = Nothing, ptrs = 0, nptrs = 0, tipe = ARR_WORDS, srtlen = 0, code = Nothing}, bytes = 32, arrWords = [15576469751458287675,4322980304539735369,4525514649686251034,1263748243132727432]}

bors r+


Feature Request: Preview of open tabs in task bar

I would like to have each of my tabs show up in my task bar when I hover over the icon like Edge browser.

This is a good idea.

This is really difficult for our app actually. DWM and Shell interact to only provide window previews for things with HWNDs. Since we're using XAML UI, our terminals don't actually have HWNDs.

I believe tabbed shell provided an API to do just this. I remember talking to Raymond Chen on this during his Build talk from 2018. Wonder if that API is still in or did it get pulled

@DHowett I wonder if this would help🤔🤔

Example code doesn’t change the fact that we don’t have HWNDs to register with the compositor :)

There’s probably some clever hack we can do by allocating hidden windows and giving them fake contents, intercepting their activation events, etc. We just have done that yet!

Example code doesn’t change the fact that we don’t have HWNDs to register with the compositor :)

So, there needs to be a separate hwnd for each preview in a group?

Yes.

This and in the alt-tab window selector too. I hope the method chosen provides both.
Its really the only thing left thats keeping me on putty for my SSH terminal windows. Tabs are great, but they NEED to be properly integrated. Latest pre-releases have detachable tabs, just waiting on things like this to complete the experience.


Use Points Instead of Line for Historical Data

Historical data looks odd when there are calibration shifts or periods of missing values with the line graph. Using points (dots) would help show this more clearly.

Rather than using dots, what if we kept the nulls for missing values and pulled fingersticks into their own series?

I still tend to have a preference for individual points (engineering hammered that into me), but a line for CGM readings that breaks for null values and split-out fingerstick values works well.

Fixed in #36


Create weekly panel and daily panels

Codecov Report

Merging #86 (f4023ce) into master (66e5e2a) will decrease coverage by 1.02%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master      #86      +/-   ##
============================================
- Coverage     71.81%   70.79%   -1.03%
  Complexity      401      401
============================================
  Files            71       72       +1
  Lines          1242     1260      +18
  Branches        126      129       +3
============================================
  Hits            892      892
- Misses          318      336      +18
  Partials         32       32

Impacted Files
Coverage Δ

src/main/java/seedu/unify/ui/DayCard.java
0.00% <0.00%> (ø)

src/main/java/seedu/unify/ui/TaskListPanel.java
0.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 66e5e2a...f4023ce. Read the comment docs.

LGTM


Added default encoding in case it is not specified by the client

Issue describing the changes in this PR
resolves #1986
Pull request checklist

[x] My changes do not require documentation changes

[ ] Otherwise: Documentation issue linked to PR

[x] My changes should not be added to the release notes for the next release

[ ] Otherwise: I've added my notes to release_notes.md

[x] My changes do not need to be backported to a previous version

[ ] Otherwise: Backport tracked by issue/PR #issue_or_pr

[x] I have added all required tests (Unit tests, E2E tests)

@microsoft-github-policy-service agree


Implement Admin functionality to administer all blogs.

add admin functionality to perform read and delete on blogs to monitor and filter the content on the website.
PR1: add admin table to the db and necessary backend api for authentication of admin.
PR2: add a login page for admin with proper styling and auth functionality
PR3: add admin dashboard which displays all blogs with read and delete functionality
this issues can be further extended to add more admin functionalities as per discussion with the PA.
@Anuj3553

Hyy @ShivanshPlays, I'm assigning this issue to you. Make this according to our website color pallate and after this give the video attached with PR.

sure! I will raise the necessary PRs soon


Position 'Search Fields' in the 'Content' section of JSON file

I found out that sometimes the field ‘Search Fields’ appears in the JSON files.
In Haddaway, 2022, the following is said about the Search Fields field: ‘Can be populated automatically from search history export. Optional if this is specified in the search string itself'.
However, this is not always the case, it can also happen that the ‘Search Fields’ field exists, but no search fields have been defined in the ‘Search’ field.
@k-schnickmann @ThomasFleischmann
Have you also noticed this?
Do you have any suggestions on how we should deal with it?
Suggestion from @geritwagner
From the user's point of view, it might be helpful to receive the parsed query before the SearchField translation or to call it explicitly (optional).

I will try to clarify the different cases that could happen. The search_field can be empty, or contain a value, which match or contradict the SearchField specified in the search_string. These cases should be handled with appropriate user notifications.
For each of the following cases, a different response of the SearchQuery parser would be appropriate (suggestions):

Search-Field required
Search String
Search-Field
Implications/Actions

Yes
With Search-Field
Empty
ok

Yes
With Search-Field
Equal to Search-String
ok - with warning: data redudancy

Yes
With Search-Field
Different from Search-String
error: contradiction in search fields

Yes
Without Search-Field
Empty
error: search field missing

Yes
Without Search-Field
Given
ok - with warning: recommend to specify search-field in search string

No
With Search-Field
Empty
ok

No
With Search-Field
Equal to Search-String
ok - with warning: data redudancy

No
With Search-Field
Different from Search-String
error: contradiction in search fields

No
Without Search-Field
Empty
ok - with warning: recommend to specify search field explicitly

No
Without Search-Field
Given
ok - with warning: recommend to specify search-field in search string

Notes:

If a SearchField is not required by a database, a predefined field is used per default.
Passing SearchField separately to the parser should be optional.
The case empty could be "SearchField not passed to parser" or "Empty SearchField passed to parser".

@Peteer98, @k-schnickmann and @ThomasFleischmann, please have a look at it and let us know whether you agree or propose changes.

Hello, @Peteer98 , @k-schnickmann and me had a meeting this week and we agree with the suggestion.
Additionally, we discussed to differentiate between a strict and non-strict way. If the user chooses strict and there is an issue with the search field, for example:

if it is required but not there,
a not supportet search field
one SearchField and one in the search term itself,

then the user should be prompted to make corrections to the string.
If non-strict, the parser automatically adds/translates/chooses an appropriate search field value.

Thank you - this is a good point! I tried to summarize how that could be explained in the documentation. Please check and suggest clarifications.
Parser modes
Strict mode: Forces the user to maintain clean, valid input but at the cost of convenience.

Fails on fatal or error outcomes. Prints warnings.

Non-strict mode: Focuses on usability, automatically resolving common issues while maintaining transparency via warnings.

Fails only on fatal outcomes. Auto-corrects errors as much as possible and prints a message (adds a fatal message if this is not possible). Prints warnings.

An additional "silent" option may be used to silence warnings.
Messages
The parser/linter can add different messages (level: fatal, error, warning). Initial examples for the messages are:
Fatal

tokenizing-failed (F0001)
unbalanced-parentheses (F0002)
missing-operator (F0003)

Error

search-field-contradiction (E0001)
search-field-missing (E0002)

Warning

search-field-redundant (W0001), description: recommend specifying search-field in the search string only
search-field-extracted (W002), description: recommend specifying search-field in the search string
search-field-not-specified (W003), description: search-field should be specified explicitly

Search Field Validation in Strict vs. Non-Strict Modes

Search-Field required
Search String
Search-Field
Mode: Strict
Mode: Non-Strict

Yes
With Search-Field
Empty
ok
ok

Yes
With Search-Field
Equal to Search-String
ok - search-field-redundant
ok

Yes
With Search-Field
Different from Search-String
error: search-field-contradiction
ok - search-field-contradiction. Parser uses Search-String per default

Yes
Without Search-Field
Empty
error: search-field-missing
ok - search-field-missing. Parser adds title as the default

Yes
Without Search-Field
Given
ok - search-field-extracted
ok

No
With Search-Field
Empty
ok
ok

No
With Search-Field
Equal to Search-String
ok - search-field-redundant
ok

No
With Search-Field
Different from Search-String
error: search-field-contradiction
ok - search-field-contradiction. Parser uses Search-String per default

No
Without Search-Field
Empty
ok - search-field-not-specified
ok - Parser uses default of database

No
Without Search-Field
Given
ok - search-field-extracted
ok

I just added the overview to the documentation: here and I also added the search-field-unsupported error as suggested.


fix throw RejectedExecutionException to prevent http hanging by Future

Proposed changes
cherry-pick #29607
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

refer to  https://github.com/apache/doris/pull/29607


NTR: Term to describe toll ligand proteolytic cascade

The Toll signaling pathway GO:0008063 is described as "A series of molecular signals initiated by the binding of an extracellular ligand to the receptor Toll on the surface of a target cell, and ending with regulation of a downstream cellular process, e.g. transcription."
We would like to have a term to describe the upstream protease cascade (plus its regulation) that leads to the generation of an active ligand (spatzle) for Toll receptors.

Suggested term label:
Either:
Toll ligand activation cascade
Pro-spatzle activation cascade

Definition
A zymogen activation cascade that leads to the generation of an active protease that cleaves a pro-ligand to an active ligand for the Toll receptor. Starting with the activation of the protease cascade by extracellular recognition factors and ending with the cleave of the Toll receptor pro-ligand (in Drosophila, this ligand is Spatzle).

Reference

PMID:21209287

Gene product name and ID to be annotated to this term

Parent term(s)
GO:0072376 	protein activation cascade ?(not sure)

Children terms (if applicable)

regulation (+ve/-ve) terms as well, please!
tagging @gantonazzo

I would suggest a child of signaling receptor ligand precursor processing (GO:0140448). I have used its grandchild to annotate the proteases that process EGF-family ligands.

I would suggest a child of signaling receptor ligand precursor processing (GO:0140448). I have used its grandchild to annotate the proteases that process EGF-family ligands.

Oh, yes. I like that very much!

@hattrill what is the source of the figure 2 above? It is not PMID:21209287, I believe. That would be a better reference for below terms.
If I understand it correctly, "Toll signaling pathway" includes TLRs that do not use Spatzle as ligands. How about:
Subclass of GO:0016486 peptide hormone processing
"Toll peptide ligand processing" definition "The generation of a mature active peptide ligand for the Toll receptor by the proteolytic cleavage of a pro-ligand to generate a functional ligand. In Drosophila, this ligand is Spatzle."
Subclass of GO:0060568 regulation of peptide hormone processing
"regulation of Toll peptide ligand processing" definition "Any process that modulates the frequency, rate or extent of Toll peptide ligand processing."
"positive regulation of Toll peptide ligand processing" definition "Any process that activates or increases the frequency, rate or extent of Toll peptide ligand processing."
"negative regulation of Toll peptide ligand processing" definition "Any process that stops, prevents, or reduces the frequency, rate or extent of Toll peptide ligand processing."

@hattrill what is the source of the figure 2 above? It is not PMID:21209287, I believe. That would be a better reference for below terms.

@raymond91125 the source for that figure is PMID:23632253

If I understand it correctly, "Toll signaling pathway" includes TLRs that do not use Spatzle as ligands.

Actually, TLRs are covered by GO:0002224 toll-like receptor signaling pathway - the TLR is activated by directly binding pathogen molecules (PAMPs) whereas the Drosophila/insect Toll receptors are activated by processed Spaetzle ligand and are  covered by GO:0008063 Toll signaling pathway.

Thinking about signaling receptor ligand precursor processing/peptide hormone processing, I realise that this won't work for Spatzle as what I want to capture is the cascade of events that final leads to processing of the ligand, whereas "signaling receptor ligand precursor processing" is for the processing steps that act on the ligand itself.
I therefore think that 'protein activation cascade' is more appropriate as the steps are a series of zymogen-activations ending in Spatzle activation by cleavage.

I therefore think that 'protein activation cascade' is more appropriate as the steps are a series of zymogen-activations ending in Spatzle activation by cleavage.

I see. How about:
"spatzle activation cascade" definition: "A zymogen activation cascade that leads to the generation of an active protease that cleaves an inactive to an active ligand, spazle, for the Toll receptor. Starting with the activation of the protease cascade by extracellular recognition factors and ending with the cleavage of spatzle." PMID:23632253.
Given that there are three parallel cascades, is one term enough for you? You probably don't want to mix the annotations.
But then I don't know if this gets too granular for GO. @pgaudet What do you think?

I agree this is very specific, but we have all these other ones:

@hattrill isn't signaling receptor ligand precursor processing sufficient with the ligand as the input?
Thanks, Pascale

Yet another vignette for the hard uniform-granularity discussion>

signaling receptor ligand precursor processing DEF The cleavage of a peptide bond in a precursor form of a signaling receptor ligand, resulting in the mature (active) form of the ligand. That sounds like a single-step process. What @hattrill wants, I believe, is something more like a 'regulation of signaling receptor ligand precursor processing', specifically, the toll ligand spatzle. But the regulation is in itself complex, involving pathways that consists of cascades of proteolytic reactions and their regulations. Thus the proposal of a child of protein activation cascade seems more direct and better.

That sounds like a single-step process.

That's right - we should make the definitions more general, as we did for small non-coding RNA processing, which is now "A process leading to the generation of a functional x" (+ including some additions steps as needed).
Wouldn't 'maturation' be more appropriate than 'processing?
Thanks, Pascale

Similar to the term GO:0072378 blood coagulation, fibrin clot formation. a child of protein activation cascade, how about:
"Toll receptor ligand protein activation cascade" definition "A protein activation cascade that contributes to the generation of an active peptide ligand for the Toll receptor and consists of the cascade of enzymatic reactions initiated by by extracellular recognition factors, leading to the cleavage of the inactive form of spatzle." PMID:23632253.

I like that. It works for me.

@hattrill Sorry, I spoke too soon. Do you think it's workable for you to annotate genes involved in the spatzle activation cascade with (new term) signaling receptor ligand activation cascade: A series of modifications to a set of proteins where the product of one reaction catalyzes the following reaction, ultimately leading to the generation of a mature ligand.
is_a protein activation cascade (GO:0072376); and specify spatzle as the ligand in annotation extension?
We prefer to do it this way because it would avoid specifying a single gene product in the GO term.
Thanks for your consideration and patience.

Hi @raymond91125 I think that this is an exceptional case - can't think of many similarities and as this is a distinguishing feature of arthropod Toll signaling pathways (not TLRs) and there are mulitple enzymes explictly dedicated to this process and many routes, it would get too hard. Spz is at the end, so the individual step would the pro-enzyme as the "has_input" rather thgan spz and then another extension would be needed to say how it was activated e.g. part_of DV axis or innate immune response to X pathogen.
So, would like a special term please!

@hattrill does this only occur for the toll ligand? maybe then we dont create the grouping term?

I think the question is about whether it's best to create a term addressing Spz specifically (with or without a grouping term) or let Spz be specified some other way (annotation extension or GO-CAM). I'm not experienced in annotation practices. @ukemi @vanaukenk Could you advise? Thanks!

WRT the complement system, it seems GO:0006956 complement activation should be given the additional superclass 'protein activation cascade'.
Thanks, Pascale

It looks like GO:0006956 complement activation already 'has part' some 'protein activation cascade', per AmiGO.

good catch @addiehl

Wouldn't is_a be more accurate ? I dont see the other parts of complement activation?

@hattrill Would you be interested in coming to a GO ontology developer meeting (Monday 9AM PST) so that we can discuss this with the larger group in real time? @pgaudet When do you think we can fit Helen in, June 20th?
Again, I'm sorry this takes so much time but it touches on some fundamental issues of GO moving forward.

June 20th would be fine for me.

Summary of alternative proposals
protein maturation
is_a protein activation cascade (GO:0072376)
is_a signaling receptor protein ligand activation cascade
OR   is_a Toll receptor ligand protein activation cascade

regulation terms added. Thanks for reminding me. @hattrill


Button sizing when in group

Describe the feature in detail (code, mocks, or screenshots encouraged)
It seems impossible to adjust the button sizing when they are grouped. It would be a nice additional feature.
What type of pull request would this be?
None
Provide relevant links or additional information.
No response

@bartcuijpers can you expand with an example. In most cases I'm aware of the group controls the sizing.

Individual buttons can be sized using the btn-sm, btn-lg and btn-xl classes. These classes don't work when multiple buttons are grouped in a buttongroup. It would be nice to be able to size the entire button group, just like Bootstrap.

I second this request. I'm trying to make the "metropolitan" and "atlantic" buttons small, however it seems the 'btn-sm' class is overridden by the 'btn-group' class in the parent.
I can work around this by making the 'btn-sm' class important on the child button, however ideally it would work just by setting a button size class on either the button group or individual child buttons

While working with this I've noticed another behavior that I think could be considered a bug. If I have a button group and want to change the color of one of them to indicate it's been selected using a different variant class, it works, however if I hover over the highlighted button, the background color goes back to the button group color.
This is confusing when trying to change the color of the button to indicate it's been clicked, because the background will stay the previous color until the user moves their cursor off the button. I confirmed this is not the case with regular buttons. Not sure if this is the correct place to discuss

@campbelljlowman

While working with this I've noticed another behavior that I think could be considered a bug. If I have a button group and want to change the color of one of them to indicate it's been selected using a different variant class, it works, however if I hover over the highlighted button, the background color goes back to the button group color.

Right, we've seen this behavior before. The trick is to make sure to apply ! (important) to the style applied to the child element. This will resolve the issue.
I'd also encourage you keep an eye out for this change in the new release next week. This resolves the disabled state for child buttons in a button group:
https://github.com/skeletonlabs/skeleton/pull/2160

In an effort to prepare for Skeleton v3, we're consolidate some related issues down to a single ticket. This will ensure that we can see the full context of requests when the time comes to refactor and update this feature going forward. If you wish to add additional feedback or suggestions, please so here:

https://github.com/skeletonlabs/skeleton/issues/2377


[Training] of GitHub for Designers

As we will move to Jira by the end of the year, there is no need to train Designers on how to use GitHub


Verbose logging is not working

It seems that verbose logging is not working anymore.

@didiladi logs appear to be correctly to .logs/(timestamp).log for me


Add RefreshToken strategy

Coverage increased (+0.5%) to 99.478% when pulling e58e3f9cfed5872773a327bc508bb024de9eb061 on add_refresh_token_strategies into efe9322d5073e3f5d4954ce80060f897ba29709a on master.


Full prompt for a specific task

Thank you so much for developing such a useful tool. I usually only use Python and other mathematical software, and I am not familiar with TypeScript. I don't know from this library how to give a complete prompt for a specific problem. Can you add a description to the documentation? For example, what is the full prompt for the sentiment task?

Hey there! Hopefully we can provide a more Python-like experience in the future. There's a README in the sentiment example which points out that input.txt has a few examples of inputs for the prompt.
A translator object will construct a prompt using a set of TypeScript types, a specific type for the response, and whatever user input was provided.
I'm also developing some documentation around using TypeChat over at https://github.com/microsoft/TypeChat/pull/65.
Does that answer your question? Is there something that would make some of this more obvious?

Hey there! Hopefully we can provide a more Python-like experience in the future. There's a README in the sentiment example which points out that input.txt has a few examples of inputs for the prompt.
A translator object will construct a prompt using a set of TypeScript types, a specific type for the response, and whatever user input was provided.
I'm also developing some documentation around using TypeChat over at #65.
Does that answer your question? Is there something that would make some of this more obvious?

Thank you very much for your reply, which gave me some insight into the code structure. I'll try it myself.


Sending 'silent' notifications

Hello,
I was wondering if it would be possible to send 'silent' notifications. So notifications that basically skip the  devices' notification center in both Android and iOS. Any idea how?
Thanks in advance!

Hi @bmourat, unfortunately not yet. Still waiting for a response.

Hi
if by 'silent' you mean push notification which device wont handle (wont show any notif to user), it called dry run. you can set option dry run to true. it actually a feature by gcm for developers.

@aliemam thanks!

@aliemam Thank you, I'm going try this soon.


[Improvement][CI] deploy to k8s

Purpose of the pull request

close #14525
This PR should wait for #14512 fix

The first stage, build and deploy, verify the docker image and helm charts, k8s deployment is successful.

Build docker images of each component
Create a kind of k8s cluster
helm charts deploys ds on k8s

Brief change log

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

(or)
If your pull request contain incompatible change, you should also add it to docs/docs/en/guide/upgrede/incompatible.md

Codecov Report

Merging #14555 (6c97b3d) into dev (06b6ea8) will increase coverage by 0.02%.
 Consider uploading reports for the commit 320dbfd to get more accurate results

@@             Coverage Diff              @@
##                dev   #14555      +/-   ##
============================================
+ Coverage     38.71%   38.73%   +0.02%
+ Complexity     4576     4575       -1
============================================
  Files          1237     1237
  Lines         43537    43490      -47
  Branches       4821     4788      -33
============================================
- Hits          16854    16845       -9
+ Misses        24811    24777      -34
+ Partials       1872     1868       -4

Impacted Files
Coverage Δ

.../server/master/runner/WorkflowExecuteRunnable.java
10.55% <13.33%> (-0.07%)
:arrow_down:

... and 35 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Please check the failed E2E-K8S CI.

@SbloodyS This PR still WIP. Should wait for issue #14512 fixed by PR #14561

Then you can mark this PR as draft so that no one else will review.

@SbloodyS @zhongjiajie @EricGao888 @Radeity  PTAL

Wanna double check? @SbloodyS @Radeity

Wanna double check? @SbloodyS @Radeity

Sorry, I missed the failed CI.

@Gallardot There is no need to test HA in K8S CI. Could u plz set the replicas of master and worker to 1 in K8S CI values and see whether it could finish in 20 min?

There is no need to test HA in K8S CI. Could u plz set the replicas of master and worker to 1 in K8S CI values and see whether it could finish in 20 min?

good idea. I will have a try.


Can't see if a simulation has already been run by another user

nsims
https://jira.jpl.nasa.gov/browse/AERIEQS-365
Moderate
Users would like to observe simulation results in the plan without re-simulating if another users has already done so

addressed along with the temporal subset sim feature with the history view


set-script has been removed from npm 9

It is used here:
https://github.com/rails/cssbundling-rails/blob/d435ad15352da2a2b3df08056214f2eb9e4fbc72/lib/install/sass/install.rb#L11
Related issue: https://github.com/rails/jsbundling-rails/issues/138

Fixed in 1.1.2


Donate / Sponsor Page

[x] Put link in header
[x] Add link to or embed donate form
https://secure.codeforamerica.org/page/contribute/?brigade=open austin
[ ] include previous sponsors and examples - https://docs.google.com/document/d/1pAsvnfr_6t6vkTax5NPfv6os8ZNLf_p4DzAVCT4YQrE/edit
[x] contact us for other partnerships / sponsorships / etc.

I think we should change the page link to say "Donate" instead of "Support"
Support is kind of ambiguous.

Moving on to this page...
Talked to some folks at Civic Hack Saturday about "Donate" vs "Support". I think support works if the page is meant to tell people all the ways they can get involved. Folks also felt like getting solicited to donate from the landing page nav is off putting.
So yes, its ambiguous, but for a reason.

Barebones page is here:
http://open-austin.github.io/open-austin-org/support/
Open to feedback, @mapineda @amaliebarras @VictoriaODell @luqmaan

I see. I think I just missed something about what the page was for since the top comment seemed to mainly focus on sponsorships stuff.
I feel like this page is a little fuzzy right now. The content is stuff we for sure need but it needs to be reorganized a bit.
I believe I can work on some suggestions/edits this evening.

That would be awesome. Thanks Vickie :smile_cat:
Maybe we also add a section to recognize partners with their logos?

WeWork
Urban Co-Labs
City of Austin
St Edwards
Code for America
Google Fiber

If we do that, how long do we keep logos up?

I think we should only put their logo if they constantly/currently sponsor or support us in a consistent way. Hmm, we don't really have any sponsorship levels or anything do we?

closed this issue now that we are live. If there are new content or design suggestions, let's open new issues for them.


Deprecate all versions prior to 4.x

Users should be warned that their setups will we soon broken with new Node.js releases.
This means to push a patch release to 1.x, 2.x, and 3.x branches.
Something similar to what lodash does:
npm WARN deprecated<EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained. Upgrade to<EMAIL_ADDRESS>npm WARN deprecated<EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained. Upgrade to<EMAIL_ADDRESS>
Tracking issue: https://github.com/nodejs/node/issues/5213

Proposed solution:
add
  "deprecated": "graceful-fs<4.0.0 is deprecated and will be broken on newer Node.js versions. Upgrade to<EMAIL_ADDRESS>or later.",

to package.json of v2.1.0 and v3.0.8 and publish those as v2.1.1 and v3.0.9.
/cc @isaacs

Thanks for the suggestion.  I'll do this when I get to a computer.
Just so you know, and for posterity, editing package.json and publishing a new version is not the best way to deprecate a package. Deprecation should be done using the npm deprecate command.

@isaacs Ah, I wasn't aware that it is possible to that way, thanks!

Done.
npm deprecate<EMAIL_ADDRESS>"graceful-fs version 3 and before will fail on newer node releases. Please update to<EMAIL_ADDRESS>as soon as possible."

Thanks!


Drop PHP < 8

Type: refactoring
Breaking change: yes

I have a few followups for this one :D

Once we settle on a version and merge we can use php-cs-fixer to make migrations of old style php docs to native types and other code modinizatios automatically in follow up, that way we can heep the version deprication PR as simple to review as possible

Yes, but sadly many of them are incomplete, for instance, many of our PHPDoc types miss a nullable flag: getReport() which had @return Report but actually @return Report|null so it will still need manual attention.

And why the test fail is actually for the same reason. PHPDoc said @return int for getIntProperty but it's actually int|null and it rely on the null to check property was set or not.
I don't think we have any rule that could need a integer value to be set to 0 so maybe we can just simplify typing and consider 0 not set.

Well I feel that this is even more of a reason to split it in multiple PRs

Oh, I have already few other branches soon to be pushed. 😄

Cool! will make development much more pleasant :)

Yes, but sadly many of them are incomplete, for instance, many of our PHPDoc types miss a nullable flag: getReport() which had @return Report but actually @return Report|null so it will still need manual attention.

I prefer to first get a project to pass PHPStan level 9 before doing the conversion for this reason.


Unable to Access Lantern

ISSUE: Unable to access elements such as lanterns with the MCPI.  https://minecraft.gamepedia.com/Lantern
SUGGESTION: 1) Update the MCPI package to include this capability.
SUGGESTION: 2) Update the Minecraft Wiki, to provide a python implementation example.
SUGGESTION: 3) Provide links to community forums in the readme, as to help the community better collaborate.
COMMENTS: This library is truly fantastic, and happy to contribute where I can.  For now it is just sharing observations.  However, I'm happy to participate in items such as updating the Wiki, if the community feels that would be beneficial.

Lanterns don't exist in Minecraft Pi. If you're using the newer Minecraft versions, check your version, and the block ID.