Support JilDirective in Deserialization

Let's say i have json file with this element : "24hr": { ... }
I need to properly deserialize it without using attribute on my POCO (I need clean domain).
I can use this
[Jil.JilDirective(Name = "24")]
public Day_24hr Day { get; set; }
But I would preffer to have something like this :
var directives = new Jil.Directives() { new NameDirective ("24", "Day_24") };
and then do deserialization with :
var myObject = Jil.JSON.Deserialize( json,directives: );
Is this possible ? If it is, I don't see it in documentation.
Thanks.

I have a similar issue - I have properties that already have the [JsonProperty] attribute of Newtonsoft.Json. It would be nice to be able to customize the serialization/deserialization names. (by making some of the extension methods (or at least GetSerializationName) more polymorphic)


Need screenposition of hotspot but queryHotspot function not defined

Description
I am trying to create svg lines that connect parts of my model with a Hotspot text.
I know there is an example based on #3844 on the model viewer website but each time I am trying to get a similiar result I only get the error code:
"queryHotspot is not a function". On the website it says that this function is used to get the screenposition of any Hotspot (thats what I need) but somehow this function doesn't seem to be implemented.
Live Demo
https://modelviewer.dev/examples/annotations/index.html the custom Overlays example.
Version

model-viewer: v2.0.2

Browser Affected

[X ] Chrome, version: xx.x.xxxx.xx
[X] Edge
[ ] Firefox
[ ] IE
[] Safari

OS

[ ] Android
[ ] iOS
[ ] Linux
[ ] MacOS
[X] Windows

Sorry, that function was just added, so it hasn't been released yet on npm. If you'd like to test, you can build locally or grab the latest here<EMAIL_ADDRESS>but don't use it for production as it updates on each merge (you can always copy it and serve it yourself).

Thank you for your help @elalish 😊. I should have checked that first (#3837 < #3844) 🤦♂. Looking forward to the release of that function 👍


homebridge-z2m never reads occupancy sensor state

Hi there,
Love the plugin.  Recently I picked up a Linkind ZS1100400-IN-V1A02 PIR motion sensor, which is supported by zigbee2mqtt (see here).  Sure enough, in the zigbee2mqtt console, I see the device on the network, and I can see that it changes the "occupancy" state from false to true and vice versa when it picks up motion.
Homebridge-z2m adds the device and I see it in the Home app.  Using the latest homebridge-z2m as of the time of this post.
However, the Home app never picks up on the occupancy sensor state change.  There is never any corresponding log in the Homebridge console that would indicate that homebridge-z2m also picked up on the occupancy state change.  However, I can see the state change in zigbee2mqtt.
Other devices connected via zigbee2mqtt work just fine through homebridge-z2m.... but for some reason, its like homebridge-z2m doesnt know what to look for in the case of an occupancy sensor.
What can I provide, here?  I don't seem to have any logs on the homebridge-z2m side because nothing ever happens.

You can start by logging the MQTT messages, via an additional MQTT client.
I'm particularly interested in the status updates published by Zigbee2MQTT.
Also, do you have debug logging on in Homebridge?
That should provide some information about the messages that were received.

I'll enable debug logging in homebridge and see if anything is showing up
there.
I'll see about logging the MQTT messages via another client - I'll see if I
can get one configured tomorrow.
On Mon, Jun 28, 2021 at 1:03 AM Arno Moonen @.***>
wrote:

You can start by logging the MQTT messages, via an additional MQTT client.
I'm particularly interested in the status updates published by Zigbee2MQTT.
Also, do you have debug logging on in Homebridge?
That should provide some information about the messages that were received.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/itavero/homebridge-z2m/issues/224#issuecomment-869356680,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANENNG3IE67OAH3HJYXDXXLTU77DNANCNFSM47M6WR3Q
.

OK, I have some updates here.  Thanks @itavero !
Here's the messages which are being received by zigbee2mqtt when the occupancy sensor detects motion:
{"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/MBR Closet Sensor/occupancy', payload 'true'"}
true
{"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/MBR Closet Sensor/tamper', payload 'false'"}
false
{"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/MBR Closet Sensor/battery_low', payload 'false'"}
false
{"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/MBR Closet Sensor/last_seen', payload '2021-06-28T18:52:06+00:00'"}
2021-06-28T18:52:06+00:00
{"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/MBR Closet Sensor/linkquality', payload '255'"}
255

...and, here's what's showing up in the Homebridge debug output at the same time:
[6/28/2021, 2:52:06 PM] [zigbee2mqtt] Unhandled message on topic: MBR Closet Sensor/occupancy
[6/28/2021, 2:52:06 PM] [zigbee2mqtt] Unhandled message on topic: MBR Closet Sensor/tamper
[6/28/2021, 2:52:06 PM] [zigbee2mqtt] Unhandled message on topic: MBR Closet Sensor/battery_low
[6/28/2021, 2:52:06 PM] [zigbee2mqtt] Unhandled message on topic: MBR Closet Sensor/last_seen
[6/28/2021, 2:52:06 PM] [zigbee2mqtt] Unhandled message on topic: MBR Closet Sensor/linkquality

It looks to me like the plugin doesn't quite know what to do with the messages sourcing from the occupancy sensor.

Can it be that you have changed the default output format in the Zigbee2MQTT configuration?
This plugin only processes JSON messages, so it should be set to json or attribute_and_json.
I think someone reported a similar issue before, but I wasn't able to find it quickly. Changing the configuration back solved it in that case.

I’ll double check, but the other devices reporting through zigbee2mqtt all
seem to be working.  I’ll give it a look and report back!
On Tue, Jun 29, 2021 at 3:02 AM Arno Moonen @.***>
wrote:

Can it be that you have changed the default output format in the Zigbee2MQTT
configuration https://www.zigbee2mqtt.io/information/configuration.html?
This plugin only processes JSON messages, so it should be set to json or
attribute_and_json.
I think someone reported a similar issue before, but I wasn't able to find
it quickly. Changing the configuration back solved it in that case.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/itavero/homebridge-z2m/issues/224#issuecomment-870317080,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANENNGZGLWUOOQTNKHO7NYTTVFVWVANCNFSM47M6WR3Q
.

...wow, sure enough it was set to "attribute," and switching it back to "json" fixes the issue, now the sensor reports occupancy.  Great call, thank you @itavero !
I have no idea why it was ever changed in the first place, but weirder things have happened.

...wow, sure enough it was set to "attribute," and switching it back to "json" fixes the issue, now the sensor reports occupancy. Great call, thank you @itavero !
I have no idea why it was ever changed in the first place, but weirder things have happened.

I'll see if I can add a warning in the logs if such a configuration is detected. 🤔

That would have definitely saved me some digging!  Thanks again; love the plugin.  It's mostly hands off :)


Fix DebuggedProcess.HandleBreakModeEvent for deleted breakpoints

The change to support async stop events had a bug that caused us to leave the debuggee in stop state but not send a stopping event to the UI if a breakpoint was deleted in run mode by the user, but the breakpoint was hit before it made it to the command line debugger.
This fixes it.

@paulmaybee please review

👍


Fix config syntax in Layer 4 routing

https://docs.trafficserver.apache.org/en/latest/admin-guide/layer-4-routing.en.html#sni-routing
The example config uses JSON format, but we have moved to YAML parsing so it would be wrong.
The HTTP CONNECT arrow in the diagram is also misleading. That is an internal mechanism through which ATS tunnels the bytes to the upstream.

Looks like this has been fixed.  Please reopen if there is still an issue.


ENH: Split composite_stack into restoration and reference specific params

This PR splits the composite_stack argument in RestorationArea() into two parameters, restoration_image_stack and reference_image_stack. Splitting this parameter helps avoid forcing users to create larger-than-necessary datasets, especially when their reference and restoration polygons are far apart, see #57 for more info.
If a user is computing metrics using a historical recovery target, then they proceed similar to before,
ra = RestorationArea(
            restoration_polygon=polygon,
            restoration_start=year,
            restoration_image_stack=restoration_data_array,
            reference_years=ref_years,
        )

However, now if using reference polygon target, users must provide both reference_polygon and reference_image_stack,
ra = RestorationArea(
            restoration_polygon=polygon,
            restoration_start=year,
            restoration_image_stack=restoration_data_array,
            reference_polygon=ref_polygon,
            reference_years=ref_years,
            reference_image_stack=reference_data_array,
        )

If reference_polygon is passed then reference_image_stack must also be provided, otherwise a TypeError is thrown.
Closes #57.

Will probably be made redundant by changes discussed in #91

Closing as too outdated, not worth the effort of merging.


Update README.md for SciPy 2023 CFP

Overview

Let's update README.md for SciPy 2023 CFP.
After this PR is merged. @tkoyama010 will post the CFP (Submissions close on February 22, 2023.).

Details

@akaszynski @banesullivan Please update the instructors' bio (If you want).

Wow, have we really gon from 500 to 1400 direct downstream projects this year?!


Avoid polling fences in the Future implementation

As can be seen here https://github.com/NotAPenguin0/phobos-rs/blob/master/src/sync/fence.rs#L283
fences are polled, this means futures have a limited time granularity plus they keep spawning threads while waiting.
It should be possible to instead wait on the Fence from that thread and call wake after the wait.
An atomic can be used to make sure only one thread is spawned that waits on the fence.
I will follow this up with a draft

Implemented in #56


Add Pagination and Top Polls Feature

Summary
This pull request introduces pagination to the poll listing and updates the home page to display the top 5 polls for non-logged-in users. The PollFilter component has been added to manage pagination and list length filtering, allowing for a more organized and scalable codebase.
Changes Made
Added PollPagination Component:
Created a new PollFilter component to handle pagination and list length filtering.
This component manages pagination state and passes the filtered list of polls to the PollList component.
Updated Home Component:
Added logic to sort polls by the total number of votes and display the top 5 polls for users who are not logged in.
Incorporated the new PollPagination component to manage and display polls with pagination for logged-in users.
Simplified UI

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


Build an executable JAR file without the Gradle Shadow plugin

Embulk's executable JAR no longer needs package relocation. The Gradle Shadow plugin is no longer needed. Dependency JARs can be unzipped in build.gradle.
The Gradle Shadow plugin is too complicated inside, and has some potential problems as commented in build.gradle. It's reasonable to stop using it if we need just a simple thing. It was still reasonable to use it when we needed package relocation, though.

Thanks!


More natural phrasing in README.rst

Sorry, I did not see this when the PR was opened, so just creating a new PR 😬
These are just small changes to the new README.rst in places where I found the phrasing a bit unnatural. Also, I removed the part mentioning the decoding of MEG, SEG and ECoG, since the lib does not support this other data modalities yet AFAIK.

I made a small commit to change this ECoG and MEG issue (because of the MNE), and to copy the information to index.rst for the new documentation. @sliwy or @cedricrommel, for me you can apply the merge in PR.

Sorry guys, I am a bit taken by the NeurIPS rebuttal phase. I would recommending not merging this PR yet as I found some other copy-paste mistakes in the FAQ if I remember well. Would be nice to gather all these small fixes in this PR. Will be back actively next week!

I'm not so sure about the changes removing EEG/MEG etc, like brain signals can also be fMRI, which we don't really do at all so far?

Alright guys, I just fixed the few things I saw but did not have time to deal with last week :)
Thanks for helping to make the homepage text neat!! 🚀
Good to go as far as it concerns me!

yes looks good to me what do others think?

Merging it then!


Customizable shortcut for turning off screens

A customizable keyboard shortcut for putting the monitor(s) to sleep.

Other people probably may have a much better way, but in the mean time...
I know a programming way to do this.


Update README.md

I changed  #Aditional Notes:
mingw compiler  → MinGW compiler

Hey sorry, I completely missed this pull request - will rectify shortly


Add Event Notification API

Purpose
This PR is to add the Event Notification API pages.
This will fix https://github.com/wso2/docs-open-banking/issues/779.

Please find a copy of the local build (for reference): Event Notification API


Cannot match type float64 vs float32

my code :
ndim = 3
dtype = 'float64'

out_grad = tvm.placeholder([tvm.var() for _ in range(ndim)], name='out_grad', dtype=dtype)
out_data = tvm.placeholder([tvm.var() for _ in range(ndim)], name='out_data', dtype=dtype)
in_grad = tvm.compute([tvm.var() for _ in range(ndim)],
                      lambda *index: (out_grad[index] * out_data[index] * np.log(3, dtype=dtype)), name='in_grad')

s = tvm.create_schedule(in_grad.op)
print(tvm.lower(s, [in_grad, out_data, out_grad], simple_mode=True))

print(in_grad.dtype)

the error is :
Traceback (most recent call last):
  File "/Users/sguangyo/PycharmProjects/sgy/test.py", line 72, in <module>
    lambda *index: (out_grad[index] * out_data[index] * np.log(3, dtype=dtype)), name='in_grad')
  File "/Users/sguangyo/.local/lib/python3.7/site-packages/tvm-0.6.dev0-py3.7-macosx-10.7-x86_64.egg/tvm/api.py", line 309, in compute
    body = fcompute(*[v.var for v in dim_var])
  File "/Users/sguangyo/PycharmProjects/sgy/test.py", line 72, in <lambda>
    lambda *index: (out_grad[index] * out_data[index] * np.log(3, dtype=dtype)), name='in_grad')
  File "/Users/sguangyo/.local/lib/python3.7/site-packages/tvm-0.6.dev0-py3.7-macosx-10.7-x86_64.egg/tvm/expr.py", line 55, in __mul__
    return _generic.multiply(self, other)
  File "/Users/sguangyo/.local/lib/python3.7/site-packages/topi-0.6.dev0-py3.7.egg/topi/generic_op_impl.py", line 83, in _tensor_bop_impl
    return orig_bop(lhs, rhs)
  File "/Users/sguangyo/.local/lib/python3.7/site-packages/tvm-0.6.dev0-py3.7-macosx-10.7-x86_64.egg/tvm/generic.py", line 79, in multiply
    return _make._OpMul(lhs, rhs)
  File "tvm/_ffi/_cython/./function.pxi", line 310, in tvm._ffi._cy3.core.FunctionBase.__call__
  File "tvm/_ffi/_cython/./function.pxi", line 245, in tvm._ffi._cy3.core.FuncCall
  File "tvm/_ffi/_cython/./function.pxi", line 234, in tvm._ffi._cy3.core.FuncCall3
  File "tvm/_ffi/_cython/./base.pxi", line 170, in tvm._ffi._cy3.core.CALL
tvm._ffi.base.TVMError: Traceback (most recent call last):
  [bt] (4) 5   libtvm.dylib                        0x0000000112e6e6b8 TVMFuncCall + 72
  [bt] (3) 4   libtvm.dylib                        0x0000000112649c91 std::__1::__function::__func<void tvm::runtime::TypedPackedFunc<HalideIR::Expr (HalideIR::Expr, HalideIR::Expr)>::AssignTypedLambda<tvm::ir::$_8>(tvm::ir::$_8)::'lambda'(tvm::runtime::TVMArgs const&, tvm::runtime::TVMRetValue*), std::__1::allocator<void tvm::runtime::TypedPackedFunc<HalideIR::Expr (HalideIR::Expr, HalideIR::Expr)>::AssignTypedLambda<tvm::ir::$_8>(tvm::ir::$_8)::'lambda'(tvm::runtime::TVMArgs const&, tvm::runtime::TVMRetValue*)>, void (tvm::runtime::TVMArgs, tvm::runtime::TVMRetValue*)>::operator()(tvm::runtime::TVMArgs&&, tvm::runtime::TVMRetValue*&&) + 129
  [bt] (2) 3   libtvm.dylib                        0x00000001127cee81 tvm::operator*(HalideIR::Expr, HalideIR::Expr) + 33
  [bt] (1) 2   libtvm.dylib                        0x00000001127cd411 tvm::BinaryOpMatchTypes(HalideIR::Expr&, HalideIR::Expr&) + 1777
  [bt] (0) 1   libtvm.dylib                        0x0000000112629329 dmlc::LogMessageFatal::~LogMessageFatal() + 57
  File "/Users/sguangyo/tvm/src/lang/expr_operator.cc", line 78
TVMError: Cannot match type float64 vs float32

i don't know how to deal with it , float32 is right , but float64 is error

I think there's some bug within tvm.convert
import tvm
a = np.log(3).astype('float64')
print(a.dtype) # float64
a_ir = tvm.convert(a)
print(a_ir.dtype) # float32

After some tracing, I find that the type inference here is not correct:
https://github.com/dmlc/tvm/blob/187600daef6cf89f9ab1d8a8a44316b8536475c1/python/tvm/_ffi/node_generic.py#L81-L102
It's either float32 or int32

@sxjscience The general principle is to make sure we are consistent with numpy. can you try to send a PR to correct this?

i think the error is in
 return _api_internal._const(value, dtype)

in order to make my code work, i reread my  code like this:
cc = tvm.var('cc', dtype )
cc = tvm.log(cc)

i think  you must give the dtype, if i only give a number, tvm think dtype is none
tvm.const(np.log(3,dtype=dtype), dtype)
it's ok,

After some tracing, I find that the type inference here is not correct:
https://github.com/dmlc/tvm/blob/187600daef6cf89f9ab1d8a8a44316b8536475c1/python/tvm/_ffi/node_generic.py#L81-L102
It's either float32 or int32

thanks

if tvm want to be better, i think tvm should make   user easy to use it,lol

@tqchen @gyshi I'll fix that.

thx

@gyshi https://github.com/dmlc/tvm/pull/3861 fixes the problem of tvm.convert and tvm.const. However, there are still some problems within the type parsing of tvm expressions in general. For example:
import tvm
a = tvm.var('a', dtype='float64')
c = a * 1.0 # raise en error.

Why do you mix np.log with tvm IR building...

Xingjian's fix helps us with numpy ndarray types, but think about it: the solution, duck typing, is interesting that now we assume that we just assume we know it (i mean we just assume dtype exists), but it now doesn't help at all in type guessing when we want to distinguish i32 and i64 when a python scalar is given (see Xingjian's example https://github.com/dmlc/tvm/issues/3855#issuecomment-526771142), because now we don't know immediately.
A general approach when we implement an ordinary compiler is that we just leave it blank and infer it in later passes, for example, let's just implement a unification-based type solver in this level of IR, which, @sxjscience welcome to contribute if you have time.

Another solution is that you just document it out...I don’t think implementing a general type solver would be worth your effort...

math.log
because i use tvm to write mxnet op exp2, use log(2) in backward.

@junrushao1994
because i use tvm to write mxnet op exp2, use log(2) in backward.
i use tvm.const() to solve this problem. but when we use a const to compute in tvm.compute(), it will be 'int32' or 'float32', if my data dtype is 'float64', it will be an error.

It doesn’t explain the overuse of np.log given math.log exists...

because if input is int, output must be int, so i need log(2)  astype int or float , now i have relsove this problem, but thx your help


Build error

FAILURE: Build failed with an exception.

What went wrong:
Could not resolve all files for configuration ':app:debugRuntimeClasspath'.

Could not find any version that matches com.facebook.react:react-native:0.55+.
Versions that do not match:
0.20.1
0.20.0
0.19.1
0.19.0
0.18.0
+ 13 more

"react": "16.6.1",
"react-native": "0.57.5",

duplicate with https://github.com/januslo/react-native-bluetooth-escpos-printer/issues/5


Update docker-compose.yml

fix error "command traefik error: failed to decode configuration from flags: field not found, node: docker"

Thanks, @mlbx this is quite an old project that needs some attention.


Compatibility with Levels Module

Hello! Thank you for this module; it is a game-changer for me! It works great, however, when I have maps that utilize the Levels module, it only displays the main Level (0-9) regardless of what elevation the tokens are at. Is this a known thing or am I missing a setting?

Levels doesn't support Foundry observers, and so Stream View can't support Levels in its current state. The Levels author initially said they might consider improving things, but later I believe said that was unlikely to happen.
Duplicate of #21


Graphite server not listening on port 2003

Graphite server not listening on port 2003. It did just 'stopped working' :/
As You can see - it was working before:
[handoff] 2016/02/23 15:30:48 Starting hinted handoff service
[handoff] 2016/02/23 15:30:48 Using data dir: /influxdb/influxdb/hh
[tcp] 2016/02/23 15:30:48 Starting cluster service
[shard-precreation] 2016/02/23 15:30:48 Starting precreation service with check interval of 10m0s, advance period of 30m0s
[snapshot] 2016/02/23 15:30:48 Starting snapshot service
[admin] 2016/02/23 15:30:48 Starting admin service
[admin] 2016/02/23 15:30:48 Listening on HTTP: [::]:8083
[continuous_querier] 2016/02/23 15:30:48 Starting continuous query service
[httpd] 2016/02/23 15:30:48 Starting HTTP service
[httpd] 2016/02/23 15:30:48 Authentication enabled: false
[httpd] 2016/02/23 15:30:48 Listening on HTTP: [::]:8086
[retention] 2016/02/23 15:30:48 Starting rentention policy enforcement service
[graphite] 2016/02/23 15:30:48 Starting graphite service, batch size 1000, batch timeout 1s
[http] 2016/02/23 15:30:49 <IP_ADDRESS> - root [23/Feb/2016:15:30:49 +0000] POST /write?consistency=&db=so1influxdb&precision=&rp= HTTP/1.1 500 60 - sysinfo_influxdb v0.5.6 6a73591f-da42-11e5-8001-000000000
000 3.02867ms
[metastore] 2016/02/23 15:30:49 Node at <IP_ADDRESS>:8088 [Leader]. peers=[<IP_ADDRESS>:8088]
[metastore] 2016/02/23 15:30:49 Updated node id=1 hostname=<IP_ADDRESS>:8088
[graphite] 2016/02/23 15:30:49 Listening on TCP: [::]:2003
2016/02/23 15:30:49 InfluxDB starting, version 0.9.3, branch 0.9.3, commit 5d42b212fca8facfe9db0c83822f09b88be643ec
2016/02/23 15:30:49 GOMAXPROCS set to 2
[run] 2016/02/23 15:30:49 Listening for signals

Now
[handoff] 2016/03/21 10:29:51 Starting hinted handoff service
[handoff] 2016/03/21 10:29:51 Using data dir: /influxdb/influxdb/hh
[tcp] 2016/03/21 10:29:51 Starting cluster service
[shard-precreation] 2016/03/21 10:29:51 Starting precreation service with check interval of 10m0s, advance period of 30m0s
[snapshot] 2016/03/21 10:29:51 Starting snapshot service
[admin] 2016/03/21 10:29:51 Starting admin service
[admin] 2016/03/21 10:29:51 Listening on HTTP: [::]:8083
[continuous_querier] 2016/03/21 10:29:51 Starting continuous query service
[httpd] 2016/03/21 10:29:51 Starting HTTP service
[httpd] 2016/03/21 10:29:51 Authentication enabled: false
[httpd] 2016/03/21 10:29:51 Listening on HTTP: [::]:8086
[retention] 2016/03/21 10:29:51 Starting rentention policy enforcement service
2016/03/21 10:29:51 InfluxDB starting, version 0.9.3, branch 0.9.3, commit 5d42b212fca8facfe9db0c83822f09b88be643ec
2016/03/21 10:29:51 GOMAXPROCS set to 2
[run] 2016/03/21 10:29:51 Listening for signals

The logs does not indicate anything.
I did not change the config.
I did try with influxdb config > /tmp/test.config
But it did not start either....
My config is:
/etc/opt/influxdb# less /etc/opt/influxdb/influxdb.conf
reporting-disabled = true

[meta]
  dir = "/influxdb/influxdb/meta"
  hostname = "<IP_ADDRESS>"
  bind-address = ":8088"
  retention-autocreate = true
  election-timeout = "1s"
  heartbeat-timeout = "1s"
  leader-lease-timeout = "500ms"
  commit-timeout = "50ms"
  cluster-tracing = false

[data]
  dir = "/influxdb/influxdb/data"
  max-wal-size = 104857600
  wal-flush-interval = "10m0s"
  wal-partition-flush-delay = "2s"
  wal-dir = "/influxdb/influxdb/wal"
  wal-enable-logging = true
  wal-ready-series-size = 30720
  wal-compaction-threshold = 0.5
  wal-max-series-size = 1048576
  wal-flush-cold-interval = "5m0s"
  wal-partition-size-threshold = 20971520

[cluster]
  force-remote-mapping = false
  write-timeout = "5s"
  shard-writer-timeout = "5s"
  shard-mapper-timeout = "5s"

[retention]
  enabled = true
  check-interval = "10m0s"

[shard-precreation]
  enabled = true
  check-interval = "10m0s"
  advance-period = "30m0s"

[admin]
  enabled = true
  bind-address = ":8083"
  https-enabled = false
  https-certificate = "/etc/ssl/influxdb.pem"

[http]
  enabled = true
  bind-address = ":8086"
  auth-enabled = false
  log-enabled = true
  write-tracing = false
  pprof-enabled = false
  https-enabled = false
  https-certificate = "/etc/ssl/influxdb.pem"

[[graphite]]
  bind-address = ":2003"
  database = "graphite"
  enabled = false
  protocol = "tcp"
  batch-size = 1000
  batch-timeout = "1s"
  consistency-level = "one"
  separator = "."

[collectd]
  enabled = false
  bind-address = ":25826"
  database = "collectd"
  retention-policy = ""
  batch-size = 5000
  batch-timeout = "10s"
  typesdb = "/usr/share/collectd/types.db"

[opentsdb]
  enabled = false
  bind-address = ":4242"
  database = "opentsdb"
  retention-policy = ""
  consistency-level = "one"
  tls-enabled = false
  certificate = "/etc/ssl/influxdb.pem"

[monitoring]
  enabled = false
  write-interval = "1m0s"

[continuous_queries]
  log-enabled = true
  enabled = true
  recompute-previous-n = 2
  recompute-no-older-than = "10m0s"
  compute-runs-per-interval = 10
  compute-no-more-than = "2m0s"

[hinted-handoff]
  enabled = true
  dir = "/influxdb/influxdb/hh"
  max-size =<PHONE_NUMBER>
  max-age = "168h0m0s"
  retry-rate-limit = 0
  retry-interval = "1s"

What can I debug?

Invalid? Somehow it was enabled = false
enabled = true
now it is working again

What does you do for running?

Hello @sirkubax can u share the steps of sharing graphite metrics to influxdb. Please


How to suppress Download the React DevTools warnings?

ReactDOM console.infos some messages like "Download the React DevTools" that are normally suppressed when running in node with the user agent check. However, running tests in electron has the chrome user-agent and those are still printed.
Apparently, it can also be suppressed with https://github.com/facebook/react/pull/11448 but I can't make it work with babel-jest to inject it early enough.
Did you guys run into this problem and have a quick workaround? I admit this question not related to this project very directly.

What I ended up doing for now is roughly this:
// react-dom-helper.js
import suppressed from "react-dom-helper-suppress-warning";
import ReactDOM from "react-dom";
// react-dom-helper-suppress-warning.js
window.__REACT_DEVTOOLS_GLOBAL_HOOK__ = { isDisabled: true };
export default true;

Truly hacky, because there's no guarantee that the suppress module is going to be evaluated first but with the current implementation it is.

That's an interesting thought. Although, I'm wondering then why test runners prefer NODE_ENV=test over NODE_ENV=production?

My assumption would be that setting the environment to production or development should be at the discretion of the user. Therefore test is a sane default they can depend on if the environment is not explicitly set.
The reason you're seeing the react devtools message is because the logic only checks for the existence of a production environment, which means development and test would both execute their non-production logic branch if it returns false.

I still wish there was a better way of suppressing this message that having to set the environment to prod. But I think I'm satisfied for now.
Thank you for the discussion @JM-Mendez!

@neojski you can add a jest setup file that sets the global variable!
i do this in our nuclide testing framework
https://github.com/facebook-atom/jest-electron-runner/blob/df406f1443053bf8af8e025306ef12ae57430a1d/packages/nuclide-e2e/src/nuclide-e2e-injected-package/nuclide-e2e-injected-package.js#L18
and we do this in Nuclide tests
https://github.com/facebookarchive/nuclide/blob/master/jest/setupTestFrameworkScriptFile.atom.js#L17

since a lot of elecron apps are built in react i think it might make sense to add this hook at the top of https://github.com/facebook-atom/jest-electron-runner/blob/master/packages/electron/src/browser_window_injected_code.js

since a lot of elecron apps are built in react i think it might make sense to add this hook

Seems simple enough. I can push a PR for it tomorrow.

Oh, nice! Thank you!


Translate help

I'm going to translate the new help system: what about the approach of the Guide translation: add-page commit?
If it's ok I'll translate all the remaining guides.

Notice: in the add-page guide, the second and the third steps have the same texts...

Thanks mlocati. I'd like to translate these help dialogs before 5.7.4 release.

Me too :wink:
I'm just waiting for a go/no-go from @aembler

This looks great. Once we get them translated I'll go back in there and make sure that the text is right.
Thanks again.

@hissy @aembler Done :wink:

Thanks for the quick turnaround; this is great.

:wink:


Some work on the build system

Some improvements (I think xD) to the build system (We HAVE to find something better than GNU Make).

Replaced 'mac' by 'darwin' globally.
Reusing cached object files by not explictly deleting .build.
Added a new filed to add reusable chunks of code.
Added a small shell function to build the release tarball.
Wired the release scripts to the new function.

:+1:


Nightly CI failure

Looks the problem is related to mpmath.
https://github.com/NVIDIA/TensorRT-LLM/pull/1146
https://pypi.org/project/mpmath/1.4.0a0/
(thanks @take-cheeze for investigation)

https://github.com/pfnet/pytorch-pfn-extras/blob/8f03af2b6b4a81401b8519d21fe36123b24e7d40/.github/workflows/nightly-test-cpu.yml#L28
Let's replace --pre torch torchvision torchaudio with "torch>0.0.0a1" "torchvision>0.0.0a1" "torchaudio>0.0.0a1" to avoid using pre-releases for dependencies.


protect default branch

So far the "master" branch is hardcoded. I suggest to protect the default branch instead.
For people who have not changed the default branch that's "master" for other people it's the default branch they have defined for their repository.
Sorry for https://github.com/genuinetools/pepper/pull/10 - force pushing was a bad idea ;-)

can you update the readme as well and not bump the version, thanks!


KAFKA-4194 follow up patch for KIP-79

@ijuma The patch is updated. I am also running a branch builder test on this branch.

@becketqin One other minor cleanup. This variable is no longer used: https://github.com/apache/kafka/blob/trunk/core/src/main/scala/kafka/log/FileMessageSet.scala#L167.

@hachikuji Suggested tests are added. branch builder test has one failure which looks irrelevant. I kicked off another one just now.

@hachikuji Comments addressed. Could you take another look. Branch builder tests failed at different places, it seems irrelevant to this change.

@becketqin Did you see my comment here? https://github.com/apache/kafka/pull/1897#issuecomment-249089438.
One other thing worth discussing. For the listTopics() and partitionsFor() APIs, we use request.timeout.ms as the maximum blocking time. Is there any reason we cannot do the same thing here? Although we cannot easily change the indefinite blocking for internal calls to this API (i.e. when setting the initial positions), I think user calls through offsetsForTimes can use a timeout without affecting consumer behavior since it is an isolated request API call. What do you think?

@hachikuji I have removed the unused variable in the latest update, do you still see it? Yes, I agree we should make them behave the same. I'll make the change in the getOffsetsByTimes() loop in the Fetcher.

@becketqin Yep, you're right. Thanks for the fix. Been having some issues with stale github data.

@hachikuji Would you take another look?

@ijuma Sorry I did miss the follow-up comments in the previous RB. I just replied in the previous RB and updated the patch. Thanks.

@becketqin Other than the last couple minor comments, LGTM.

@hachikuji Thanks for the review. I updated the patch. I did not add validation to the constructor of OffsetAndTimestamp because internally the timestamp could be -1. We could add validation before we return the value, but it seems an over fitting test in the code itself and the unit test should have covered that.

I submitted a PR with a few minor clean-ups: https://github.com/becketqin/kafka/pull/2, LGTM otherwise.

LGTM with Ismael's minor tweaks. Great work getting KIP-79 ready in a hurry for this release!

Thanks @hachikuji and @ijuma The changes LGTM.

@becketqin I'll merge this as soon as you accept Ismael's PR.

@hachikuji Done. I'll update the KIP wiki for the new error code.

Merged to trunk and 0.10.1. I changed the title slightly, hopefully it's reasonable.

The title change looks good. Thanks a lot for the review @hachikuji @ijuma


subtitle cannot be displayed when playing files with m3u8

I think I meet the same problem,
Do you finally found the solution?
When I use m3u8 ,  p tags can't properly load...
When I use the mp4, it work properly:

But when I use m3u8, no subtitles:

Repeated with #1244


triallelic sites in VCF files

Our implementation of VCF can not handle triallelic sites. I don't necessarily suggest merging this PR as it would break read/write fidelity, but it may be worth revisiting the VCF struct at some point...

this has come up before, specifically when we did the last major overhaul of VCF. The AlleleOne and AlleleTwo fields will need to become a slice of Alleles, which will have some downstream effects but should be rather manageable. Lots of popgen theory assumes biallelic sites, so we could just ignore triallelic positions in those programs


read in new metadata and positional metadata for a exisiting Sequence object

Some GenBank file only contains metadata but no sequence in itself. We can read the sequence to create the Sequence object and then read GenBank annotation into the object. This seems just a new API?
This is also required genome annotation (http://bit.ly/1jbRaxe). We incrementally add more features into a existing Sequence object with running one annotation tool after another.

:+1: this is an interesting use case! Let's talk about this on our call next week b/c it's related to what we'll be discussing. Sound good?

That sounds good. We need a solution soon because this is the blocking step to solve #1141 and other implementations.

To support this, we will have hashable sequence features that can be stored as columns on the positional metadata DataFrame. Then features can easily be merged using pandas because you'll just be merging DataFrames.
We also need to support an optional FASTA file on the GenBank reader.


Added NeurIPS-21 paper on Safe RL (IBM, Tshinghua)

Dear gym-minigrid contributors,
Thank you for releasing this great repository! We used gym-minigrid environment for our environment, and got our paper accepted to NeurIPS-21. Please consider our paper in the publication list.
Best,
Akifumi

Congratulations on your accepted paper Akifumi! :)


About memory missing location information

I noticed that the memory retrieval and update happens before 'apply_rotary_pos_emb'. Wondering whether the memory lacking location information would confuse the model's perception of the order of historical information?

From the readme: "Can train 'infinite' context -- check train.gemma.infini.noclm.1Mseq.sh with 1x H100 80G (with AdamW optimizer, No gradient checkpointing)". However I can train it with 12GB with 8b quantization and a segment size of 400.

I can also run through training. However, the current training results are not very good. I'm trying to train further

I also have same question, can you solve it ?

You can try to adjust the memory retrieval process to the end of 'apply_rotary_pos_emb' and compare the training performance. However, I did not try it further.

Thanks for your response.

Can this retain location information?


Cancelling the DropItemEvent.Destruct event no longer preserves inventory items x2

This is once again the case: https://github.com/SpongePowered/SpongeCommon/issues/654
Affected version:
    Minecraft: 1.11.2
    SpongeAPI: 6.1.0-SNAPSHOT-a15cc3e
    SpongeForge: 1.11.2-2315-6.1.0-BETA-2398
    Minecraft Forge: <IP_ADDRESS>5

Also noticed this in Stable-5.

This looks like it may have been changed intentionally:
https://github.com/SpongePowered/SpongeCommon/blob/bleeding/src/main/java/org/spongepowered/common/event/tracking/phase/entity/DeathPhase.java#L150-L167
Though that makes this logic effectively useless:
https://github.com/SpongePowered/SpongeCommon/blob/bleeding/src/main/java/org/spongepowered/common/mixin/core/entity/player/MixinInventoryPlayer.java#L170-L187

This will NOT be changed in SpongeForge as it caused all sorts of issues with mods that use soulbound items such as Tinkers Construct. The event works exactly like Forge's PlayerDropsEvent
https://github.com/MinecraftForge/MinecraftForge/blob/1.11.x/src/main/java/net/minecraftforge/event/entity/player/PlayerDropsEvent.java#L34
"Canceling the event will prevent ALL drops from entering the world"
If you need to move items to the newly spawned player then you need to use the RespawnPlayerEvent.
https://github.com/SpongePowered/SpongeAPI/blob/bleeding/src/main/java/org/spongepowered/api/event/entity/living/humanoid/player/RespawnPlayerEvent.java

So to elaborate,

"Canceling the event will prevent ALL drops from entering the world" and also does not place the items back on the (currently dead) player?

The dead players inventory will be cleared on respawn, except for items that are soulbound, if keep inventory is on.

to keep items on respawn, you can carry them from the dead player, to the new player?

It should keep the items on the dead player.
The dead player should still have the items on "corpse". If this is not happening then it is a bug that I have to fix as you should be able to copy/transfer items from the dead player to newly respawned player.
Yes

Yeah the inventory is copyable at the time of death. I already implemented a "workaround" solution before your reply. It uses my player state service.
Implementation code here if someone comes across this issue looking for guidance:
https://github.com/Skelril/Skree/blob/master/src/main/java/com/skelril/skree/content/zone/ZoneInventoryProtector.java
https://github.com/Skelril/Skree/blob/master/src/main/java/com/skelril/skree/service/internal/playerstate/PlayerStateServiceImpl.java
Not terribly well documented, but hopefully helpgul.

Why does it store, then immediately release the inventory @DarkArc

@ryantheleach implementation detail. Release basically tells the service if the player logs out and back in, or respawns, it's free to restore the "general" inventory store. The thought being, if there is a minigame or something where they should have an isolated inventory, and their original inventory should not be restored on death, that is possible.


Use pre instead of div, make sure the code body will be rendered prefectly even when script could not load

At https://github.com/abhinav/goldmark-mermaid/blob/main/client_render.go#L36, it used div as the box, but when the script couldn't load or load slowly by some reason, the page will be so ugly.
Suggest use <pre> not <div>, then users will feel comfortable when the script could not load

There are also some other issues: I am using a plugin to convert the returned content to jsx syntax, but the line breaks in the div will be lost after being compiled by Babel, while pre has better compatibility.

Hey, yes, sure, that's completely reasonable!
Thanks for the PR, @zbysir. I'll look at it shortly.

Just a quick update, @zbysir, @zyxkad.
I plan to make a similar change to the server-side renderer.
I'll be able to release this change after that.

Released! https://github.com/abhinav/goldmark-mermaid/releases/tag/v0.4.0
Thanks for the fix, @zbysir!


Patient tests don't read all patients

The Patient tests don't read all Patients when multiple ids are provided. They should either read all Patients or the input should be renamed to indicate it is only a single Patient id. Reading multiple patients is preferred as it may be difficult to populate all Must Support fields with a single Patient.

Fixed by #28


[Bug] Daily Data date filter not working

Describe the bug
Daily data date filter is not working (doesn't return a response, just a spinning wheel).
Impact on ReportStream
Impacts Daily Data users which is a handful of STLTs and RS Prime Admins. The only other way to see specific dates is to go through all of the pages in the table. This issue happened when Support team was interfacing with a STLT.
Steps to reproduce
Steps to reproduce the behavior:

In Production, On Daily Data table
Add a date range (even a short range, say 1/24-1/25)
Click Filter
Spinning circle never stops and no data/table is returned

Expected behavior
Should return only the table data that is within the date range.
Resources

Logs

Device info
Mac Work computer
Desktop (please complete the following information)

OS: MacOS Monterey 12.6.2
Browser Chrome
Version 109.0.5414.87

Smartphone (please complete the following information)
--
Additional context
Add any other historical context about the problem here.

This looks good @chris-kuryak thanks.


no tags registered when compinit is called by plugin when sourced through zinit

Describe the bug
When compinit is called from within a plugin that is loaded through zinit light-mode, then this causes no tags registered to be output for the first several times when the user attempts completion (for example, by pressing Tab).
To Reproduce

Create an empty plugin: zinit light-mode for zdharma/null
Create a ~/.zinit/plugins/zdharma---null/null.plugin.zsh and put autoload -Uz compinit && compinit in it.
In your .zshrc, putrm ~/.zcompdump
zinit light-mode for zdharma/null

Restart your shell.
Try a completion.

Expected behavior
Completions are shown, just like when I would just source the plugin.
Actual behavior
Stuff like this:
_tags:comptags:67: no tags registered
_requested:comptags:8: no tags registered
_next_label:comptags:8: no tags registered
_all_labels:comptags:26: no tags registered

Versions:

$ZSH_VERSION == 5.8
Operating system name and version: Darwin Kernel Version 19.5.0; root:xnu-6153.121.2~2/RELEASE_X86_64 x86_64

Correction: This output happens only when I also use Powerlevel10k’s instant prompt feature.

I found a workaround: Call .zinit-shade-off $___mode before calling compinit and .zinit-shade-on $___mode afterwards.

Yes, that would explain it. I'll take a look if something can be done to skip the additional calls.

Any update on this?
So in my case, I let OMZ generate the compdump, by loading it last.
and I noticed that I don't get these errors if I generate as well initially, and let OMZ overwrite it later, but it keeps trashing around the file.
#zinit
declare -A ZINIT
ZINIT[BIN_DIR]="$ZSH_VENDOR_PATH/zinit"
ZINIT[HOME_DIR]="$ZSH_VENDOR_PATH/zinit_downloads"
ZINIT[ZCOMPDUMP_PATH]="$ZSH_CACHE_DIR"
export ZSH="$ZINIT[HOME_DIR]/plugins/ohmyzsh---ohmyzsh"
source "$ZINIT[BIN_DIR]/zinit.zsh"

#These lines two lines removed, will trigger the issue.
autoload -Uz compinit
compinit -i -C -d "${ZSH_COMPDUMP}"

source "$ZDOTDIR/zinit_plugins.zsh"

As I said, if I remove these two lines
autoload -Uz compinit
compinit -i -C -d "${ZSH_COMPDUMP}"

I get that error for a few seconds before going away.
My zinit_plugins.zsh look like this
zinit ice lucid wait depth"1"
zinit light zsh-users/zsh-syntax-highlighting

zinit ice lucid wait depth"1"
zinit light zsh-users/zsh-history-substring-search

zinit ice lucid blockf wait depth"1"
zinit light zsh-users/zsh-completions

plugins=(
z
)
zinit ice lucid nocompletions blockf wait depth"1"
zinit light ohmyzsh/ohmyzsh

zinit ice lucid nocompletions blockf depth"1"
zinit light denysdovhan/spaceship-prompt

This popped up again, but in a different way: https://github.com/marlonrichert/zsh-autocomplete/issues/335
@psprint Are you ever going to fix this?

Workaround:
[[ -v functions[.zinit-shade-off] ]] &&
  .zinit-shade-off "${___mode:-load}"


limit?

The bot works but when the conversation passes 4000 tokens the bot becomes unstable in its responses I already changed these parameters: truncation_length chat_prompt_size, but still with the same problem

Which model do you use?
Except truncation_length chat_prompt_size there is no context length parameters. Perhaps it is model problem.

I tried with wizard vicuna 30b and now with LLaMA2-13B-Psyfighter2 and I got the same problem, which uncensored model would be the ideal?

Hard to say... Default LLaMA2 as I know support 4096 token length, but Llama2 forks support up to 16k tokens, so I dont know about LLaMA2-13B-Psyfighter2. I'll try to test it later, perhaps will find something.

Thanks for your response, what model do you recommend?


Add support for Gulp file with Babel

Changes proposed:

Add

Things I've done:

Add support for gulpfile.babel.js

@mamadoo could you rebase your branch with our master? I'll merge it after that. Thanks for your PR!

We can do that too @robertohuertasm ?

Yes, I know but I prefer users do that if possible.

Okay.

I don't clone the forked repository in my computer at first. I change this file directly in github online and the create the PR for that. I don't know how to rebase forked account directly in github online (i just know in command line).
If you can Please do it.
If not i clone in computer and then pull it.

@mamadoo What you did it equally fine.


[collab] presence dot issues

Two Composer issues.
Missing hover text
Only for blue dots, not white ones.
Screenshot:

White dot is hard to see
Screenshot:

@thure I also noticed for this one that the - still shows on hover and can be removed now


Add reason to headwind config

Note that Reason's regexp is the same as javascript-react...

This PR should not include change of https://github.com/iamcco/coc-tailwindcss/pull/28

Oops -- just rebased. Sorry about that!


Added Azure Infrastructure Provisioning for Harness Delegate tutorial

Added first draft of Provisioning Azure Infrastructure for Harness Delegate Tutorial.
Following the style conventions to ensure a consistent user experience.
Signed-off-by: Dhrubajyoti C<EMAIL_ADDRESS>Screenshots:

Preview environment: https://ci.pr.harness.io/pr-232

@kat-enos please provide an editorial review. Thanks.

@codewdhruv thanks for the contribution, mind creating two elements in the Platform and All Tutorial Sections for your stuff?
All:
https://github.com/harness/developer-hub/blob/main/src/components/LandingPage/AllTutorials.tsx
Platform:
https://github.com/harness/developer-hub/blob/main/src/components/LandingPage/Platform.tsx
Cheers,
-Ravi

Preview environment: https://ci.pr.harness.io/pr-232

Updated elements at AllTutorials.tsx & Platform.tsx
Tested the build locally. No errors. cc: @ravilach

Thanks @codewdhruv! Looks good from my side. Just need a review from @kat-enos and we are good to go. Heads up any suggestions please bulk-commit/accept. Each commit to the PR is a build :-)

Looks good to me. Will merge post PR build with @kat-enos's edits. Congrats on being published, @codewdhruv!

Preview environment: https://ci.pr.harness.io/pr-232

Just my luck, @wei-harness dropped another plug-in for our image resizing. @codewdhruv can you re-base your branch [the yarn.lock has merge conflicts] and re-base?

Preview environment: https://ci.pr.harness.io/pr-232

Merging. Thanks for the help @wei-harness and @kat-enos. Looked like the Merge Conflict maybe was from the IDE formatting a few lines in the yarn lock. @codewdhruv. We are all set.

Thanks.


fix: nil pointer after increase min version

Description

Motivation and Context

How Has This Been Tested?

Types of changes

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

Checklist:

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have followed the guidelines in CONTRIBUTING.md, including the required formatting of the commit message

this pull request is closed because I'll create for cloudfoundry-community one


Fix lint error for generate

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm


add RSA support

add key param to authenticate method
update auth_token model to support key param
update readme
tests for HSA and RSA decoding in auth_token model

I'm sorry I haven't taken the time to look into this yet. I will do it soon.

Hey nsarno, any movement on this?  thanks!

I'll go through it sometimes this week. I had a lot going on recently but I'm going to be more active on this very soon.
Thank you for your patience! :)


API breaking after some time?

Maybe it was already reported, sorry then, but after some time (about a week), when a bot using this API is launched, this happens:
ERR! Error in uploadAttachment Error: form-data: ENOENT: no such file or directory, open '(text message [which the bot was trying to send] content)'
ERR! Error in uploadAttachment   at Error (native)
ERR! Error in uploadAttachment
ERR! Error in uploadAttachment  { Error: form-data: ENOENT: no such file or directory, open '(text message [which the bot was trying to send] content)'
ERR! Error in uploadAttachment   at Error (native)
ERR! Error in uploadAttachment
ERR! Error in uploadAttachment   cause:
ERR! Error in uploadAttachment    { Error: form-data: ENOENT: no such file or directory, open '(text message [which the bot was trying to send] content)'
ERR! Error in uploadAttachment      at Error (native)
ERR! Error in uploadAttachment
ERR! Error in uploadAttachment      errno: -2,
ERR! Error in uploadAttachment      code: 'ENOENT',
ERR! Error in uploadAttachment      syscall: 'open',
ERR! Error in uploadAttachment      path: '(text message [which the bot was trying to send] content)' },
ERR! Error in uploadAttachment   isOperational: true,
ERR! Error in uploadAttachment   errno: -2,
ERR! Error in uploadAttachment   code: 'ENOENT',
ERR! Error in uploadAttachment   syscall: 'open',
ERR! Error in uploadAttachment   path: '(text message [which the bot was trying to send] content)' }
ERR! Error in getUserInfo { error: 'JSON.parse error. Check the `detail` property on this error.',
ERR! Error in getUserInfo   detail:
ERR! Error in getUserInfo    SyntaxError: Unexpected token < in JSON at position 0
ERR! Error in getUserInfo      at Object.parse (native)
ERR! Error in getUserInfo      at /var/www/Concierge/node_modules/facebook-chat-api/utils.js:542:20
ERR! Error in getUserInfo      at tryCatcher (/var/www/Concierge/node_modules/bluebird/js/main/util.js:26:23)
ERR! Error in getUserInfo      at Function.Promise.attempt.Promise.try (/var/www/Concierge/node_modules/bluebird/js/main/method.js:31:24)
ERR! Error in getUserInfo      at /var/www/Concierge/node_modules/facebook-chat-api/utils.js:523:24
ERR! Error in getUserInfo      at tryCatcher (/var/www/Concierge/node_modules/bluebird/js/main/util.js:26:23)
ERR! Error in getUserInfo      at Promise._settlePromiseFromHandler (/var/www/Concierge/node_modules/bluebird/js/main/promise.js:510:31)
ERR! Error in getUserInfo      at Promise._settlePromiseAt (/var/www/Concierge/node_modules/bluebird/js/main/promise.js:584:18)
ERR! Error in getUserInfo      at Promise._settlePromises (/var/www/Concierge/node_modules/bluebird/js/main/promise.js:700:14)
ERR! Error in getUserInfo      at Async._drainQueue (/var/www/Concierge/node_modules/bluebird/js/main/async.js:123:16)
ERR! Error in getUserInfo      at Async._drainQueues (/var/www/Concierge/node_modules/bluebird/js/main/async.js:133:10)
ERR! Error in getUserInfo      at Immediate.Async.drainQueues (/var/www/Concierge/node_modules/bluebird/js/main/async.js:15:14)
ERR! Error in getUserInfo      at runCallback (timers.js:574:20)
ERR! Error in getUserInfo      at tryOnImmediate (timers.js:554:5)
ERR! Error in getUserInfo      at processImmediate [as _immediateCallback] (timers.js:533:5)
ERR! Error in getUserInfo    ,
ERR! Error in getUserInfo   res: '<title>Redirecting...</title><meta http-equiv="refresh" content="0;url=https://www.facebook.com/common/invalid_request.php?__req=61" />' }

And the message wasn't sent of course. Not sure how this API is constructed, but can't it handle these redirects or something?

In this time, Facebook changing a lot of things in Messenger, so still is new changes. But, for all people this changes is applying in other days, so for someone can work library without problems, but for someone not.

Probably a duplicate of #202 etc.  Thanks for letting us know.  This is a tricky issue that we haven't been able to get to the bottom of.

That's another thing that appeared before that error today:
ERR! Error in uploadAttachment { __ar: 1,
ERR! Error in uploadAttachment   error: 1357004,
ERR! Error in uploadAttachment   errorSummary: 'Maaf, ada masalah',
ERR! Error in uploadAttachment   errorDescription: 'Coba tutup lalu buka kembali jendela browser Anda.',
ERR! Error in uploadAttachment   payload: null,
ERR! Error in uploadAttachment   bootloadable: {},
ERR! Error in uploadAttachment   ixData: {},
ERR! Error in uploadAttachment   lid: '6329050xxxxxxxxxxxx' }


Align theme to figma

The new figma libraries release (end of 2025) simplifies our figma libraries down to a reduced set, primarily built around 1 set of components supporting 2 themes–UITK Legacy and JPM Brand.
How do we align the theme in code to mirror what design teams will providing tech teams in their documentation?
Notes from @bhoppers2008 discussion with @origami-z (10 Dec)

Salt will provide two themes (uitk and brand) for technical components.

Changing from these defaults is something a Business Library will own (i.e., i want the brand theme but blue buttons... not a Salt recommendation–technically possible but teams will have to maintain it themselves).

How do we get ourselves to a state where the defaults in code and figma are the same?

Salt Provider – Stays the same
Salt Provider Next – Deprecate

Or add a prop to the Next which changes the defaults
We still wouldn’t have the ‘Next Legacy’ in code though

Salt Provider Brand – Updated to be the same as the brand in Figma

Capability to support a Next Legacy theme but not the Salt recommendation–needs to be owned by the Business Library
Are there any open-source problems if we explicitly name the theme ‘JPM Brand’ and set the defaults to brand? Better as something more generic in code (i.e., ‘Brand’). Check with Sean if this is ok?

Should we consider removing ‘Accent’ from the new provider? Other styling options remain relevant under the hood but ‘accent’ is the difference between the UITK Legacy (blue) and JPM Brand (teal).

Have we considered just adding support the the current SaltProvider? We have a theme prop that could be set to "brand". This would potentially be more future proof as we'd avoid adding another provider and it might work if they are using SaltProviderNext already.


Czech i18n added

Please be aware of issue https://github.com/gohugoio/hugo/issues/3846#issuecomment-325635813.  There're missing pluralisation rules for few and many.

Hey @orianna-zzo, are you still around?
It would be pity to have this nice hugo template die.
Do you by any chance plan to look into reviewing the pull requests and issues, or are there other priorities on you list and no time for the AllinOne?
Cheers!

@svetlemodry I've started maintaining this theme in a new repo, found here: https://github.com/EliiseS/AllinOne

@svetlemodry I've started maintaining this theme in a new repo, found here: https://github.com/EliiseS/AllinOne

@EliiseS Awesome, thanks for taking the time!


Fusing?

This project is really neat.
Curious if you considered seperating out the load / store logic from the math to make it more easy to fuse operations? For instance would be nice to be able to use dropout (forward / backward) from within a NN+dropout fused function.

Hello,
Thank you for your interest in attorch. Yes, I have considered refactoring the math operations into a separate collection of functions that receive loaded arrays (in lieu of pointers) and return transformed arrays (in lieu of storing them), which can subsequently be incorporated into higher-level functions tasked with loading / storing data and applying the appropriate mathematical transformations. This is an appealing idea since it would enable aggressive fusion of kernels, as you say, in addition to rendering the design of most layers more modularizable (e.g., rather than having individual kernels for batch and layer normalization, they would both be instances of a more general pipeline - namely, calculate mean and standard deviation -> subtract by mean and divide by standard deviation -> perform affine transformation - that can handle arbitrary axes), but it would also sacrifice the atomic design of attorch, where each module has its own file that can easily be copy-pasted and modified to suit the user's needs. The raison d'être of this project is to facilitate exactly this type of forking or copy-pasting, and I fear that refactoring out the math would defeat the purpose. Nevertheless, I agree that for commonly-fused modules such as dropout, it would be particularly helpful to follow the pattern you refer to. I will flesh something out in the coming weeks and add support for fused dropout to linear layers.
I would be happy to hear your thoughts.

I should also add that one interesting benefit of pure math functions would be the possibility of a Triton counterpart to jax.grad to perform autodiff, but that is a completely different topic.

I agree that having single file implementations is really nice. I guess the design would be moving from 2 functions to 4 for each module where the first is a load / store from pointer and the second is the mathematical implementation. Possibly wouldn't be so bad to keep the complexity low.
Actually this idea does tie into backprop. I wrote a small library https://github.com/srush/triton-autodiff that allows you to derive backprop code in Triton. It might let you derive backprop of fused ops directly.

I like the idea of having having a layer_forward_math, layer_forward_kernel, layer_backward_math, layer_backward_kernel, but I am not sure if it is applicable to all layers. In the case of batch normalization, for example, it would not be possible to cram the math into a single function since at least two passes over the data are necessary - one to calculate the batch statistics, another to transform the input. I suppose we could have multiple math-only functions per kernel though (e.g., calc_mean_std and normalize). A compromise between the current design and a thoroughgoing refactoring of it would be to have separate calc_mean_std and normalize functions for each normalization layer. I will start experimenting with this.
triton-autodiff seems very cool. The difficulty of a full-fledged autodiff mechanism for Triton lies in impure functions, but the issue is side-stepped with math-only functions. Were you planning to add support for conditionals and loops too?

Yeah I agree these are interesting complications.
Agree that you don't want full autodiff for triton, but if you have a couple of specialized impure fwd/back functions you can potentially connect them together with autodiff.
The backend for triton-autodiff actually does support if / for which is neat (it's a general purpose python source course autodiff). I haven't tested it yet thoughly.

I have gone through triton-autodiff (super cool that the code is so concise) and Tangent, and I had an idea: I will keep the design of existing layers as-is but will add a separate math module that implements the forward pass of basic mathematical functions whose gradients can be derived through triton-autodiff, thereby allowing developers to plug them into other kernels and do fusion should attorch not support their use case. There will inevitably be duplicate code involved, but I would rather have that than lose the simplicity of the neural net modules.

Cool. Feel free to reach out if I can help in anyway. Neat project.


Removal of references to default components

Description:
This PR is to remove the references to default components in opentelemetry-collector-contrib repository
Link to tracking Issue: # 3927

Is this PR filed upstream? Lets close this then. @erichsueh3


Set e2e test shoot k8s version to v1.30.0

How to categorize this PR?

/area opensource
/kind enhancement
What this PR does / why we need it:
Since https://github.com/gardener/gardener/pull/9689, Gardener supports v1.30 k8s version. This PR updates the e2e test shoot versions to the same.
Which issue(s) this PR fixes:
Part of https://github.com/gardener/gardener/issues/9508
Special notes for your reviewer:
/hold until gardener v1.95 release branch is created.
Release note:

NONE

/test pull-gardener-e2e-kind pull-gardener-e2e-kind-ha-multi-zone pull-gardener-e2e-kind-ha-single-zone pull-gardener-e2e-kind-ipv6 pull-gardener-e2e-kind-migration-ha-single-zone pull-gardener-e2e-kind-operator

/test pull-gardener-e2e-kind-migration

/unhold


[WIP] Add Landscape config

I want to automate more of the linters
Pull Request Checklist
(Please keep this section. It will make maintainer's life easier.)

[ ] Privileged views and APIs are guarded by proper permission checks.
[ ] All visible strings are translated with proper context.
[ ] All data-formatting is locale-aware (dates, numbers, and so on).
[ ] Database queries are optimized and the number of queries is constant.
[ ] The changes are tested.
[ ] The code is documented (docstrings, project documentation).
[ ] Python code quality checks pass: pycodestyle, pydocstyle, pylint.
[ ] JavaScript code quality checks pass: eslint.

Landscape.io seems to be an abandoned project. Builds fail, the docs are missing and pull request details are unreachable as they either return 404 or 500 errors.


Implement query restriction pushdown for Id

The CQL engine currently supports certain types of query restriction pushdowns, specifically for date filters. In other words, given the following CQL:
[ Condition ] C where C.onset starts 30 days or less before Today()

the CQL compiler can emit an ELM Retrieve that has that date filter captured in the datePath and dateLow elements.
Ideally, we could support the same type of push-downs for Retrieves by id. In other words, these two statements _ought to be equivalent with respect to the ELM that's generated:
[Medication] M where M.id = `123`

[Medication: id in {'123'}]

And the ELM that's generated for the Retrieve  ought to have both the id and the idProperty populated in both cases.

Note that it's the DataRequirementsProcessor that does these types of optimizations as a post-processing step. There is some date range pushdown in the translator directly, but it's not as sophisticated as what the DataRequirementsProcessor is doing, and should be deprecated in favor of the DataRequirementsProcessor, IMHO.

Just to clarify, are you saying that we should always do pushdown as post-processing? Including for Ids?


Public bot could not record log properly

Hello, could you please take a look at the logs of the public instance of the bot? I used the bot to record several sessions. But when exporting, it always prompts "Invalid session! This session doesn't hold any logs yet".
It's the Alpha server, <IP_ADDRESS>.

Your RCON password is incorrect. Use the /credentials edit command to change it.


Remove ClashX

ClashX repo - https://github.com/yichengchen/clashX has only one file.
It should not be included in this list
Category
NA
Description
NA
Why it should be included to Awesome macOS open source applications  (optional)
To help clean up invalid applications from this awesome list
Checklist

[ x] Edit applications.json instead of README.md.

Your right, will remove this MR
Thank you


Termination by SF can also have ExitCode=3221225786

When SF terminates a process/container, I've also seen traces in Fabric traces with ExitCode=3221225786, which maps to:
0xc000013a | -1073741510 | STATUS_CONTROL_C_EXIT | {Application Exit by CTRL+C} The application terminated as a result of a CTRL+C. | (from ntstatus.h)
This article mentions some other Ctrl-C error codes but not this one; perhaps this error code should be included in the article where it explains the Ctrl-C errors.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: f541a9f9-4be2-9537-5f94-bbfa02cf72ca
Version Independent ID: c44b249f-243f-6a2d-fd34-9a8497102076
Content: Diagnose common code package errors by using Service Fabric - Azure Service Fabric
Content Source: articles/service-fabric/service-fabric-diagnostics-code-package-errors.md
Service: service-fabric
GitHub Login: @grzuber
Microsoft Alias: grzuber

Thanks for the feedback! We are taking a look into this and will get back to you soon.

@suncats Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

Hi @TravisCragg-MSFT! I'm sorry but I'm no longer on the Service Fabric team, we should probably change the owner of this page I'm just not sure who the appropriate person would be

@gzuber Thanks! I will find the correct owner.

Hi @TravisCragg-MSFT Any update on this error code?

Thanks for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. Though the scope of our feedback channel here on GitHub covers specific documentation fixes, we can help redirect you to the right support channel to get an answer to your question: [reference to alternative product/service or community endpoint]. Because this issue does not relate to documentation, we are closing this issue. #please-close


Everything still works fine

[Info   :   BepInEx] Loading [EatLess 0.0.1]
[Warning: Unity Log] Failed to find expected binary shader data in 'Custom/Creature'.
[Warning: Unity Log] Failed to find expected binary shader data in 'Custom/Creature'.
[Warning: Unity Log] Failed to find expected binary shader data in 'Custom/Creature'.
Doesn't break anything, just figured I would let you know

Thanks. Not sure what it's complaining about so I'll just leave it alone.


[GEP-12] OIDC Webhook Authenticator

How to categorize this PR?
/area operations
/area security
/area user-management
/kind enhancement
/priority normal
What this PR does / why we need it:
This enhancement proposal adds ODIC Webhook Authenticator which can be used to add multiple OIDC providers to a standard Kubernetes API Server.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note:

Added GEP-12 for dynamic OIDC webhook authenticator.

/invite @donistz @ThormaehlenFred @ccwienk @vlerenc

@holgerkoser @ThormaehlenFred @vlerenc @ccwienk @donistz any comments from you or anybody else?
If not, we should probably go ahead and merge this GEP within the next days?

@rfranzke Besides the open points I would also vote for merging this PR soon.  There is no need to keep it open if there are no further comments.

Sorry for the delay - I've updated the PR and resolved the comments.

/needs rebase
because of https://github.com/gardener/gardener/pull/2541

@danielfoehrKn can you have another look?


reviewers for operator related issues and PRS

This change is

/verify-owners

@animeshsingh I have been added to the member of the org.

/verify-owners


Feature/map to vector

added map_to_vector wrapper methods in order to solve the next issue
https://github.com/SciRuby/daru/issues/512
tried to avoid breaking changes since the Gem relies a lot on the normal map method that returns an array.

Thanks @him666 for the PR. Can you please write few examples from old method and new method, so that later we can track the changes ?
Thanks again!

Thank you for your PR.
But to be honest, I don't want to add the map_to_vector method.
Because recode method already exists.
The problem is that the recode method is hard to find.
The naming of map_to_vector may be better than recode.
However, my opinion is that the behavior of map should be that of recode or map_to_vector.
And the to_a method is sufficient to convert a Daru::Vector to an Array.
But I'm not sure if this idea is really good.
I will read Daru's code this month..

@kojix2 , yes! I was thinking the same. Also it is written in recode docs. @him666 , please have a look whether map is overridden or not

Closing since we need a changed map method.


SumUp Total is compatible with SDK?

Is the Android SDK compatible with SumUP Total?
Here is the link for it: https://sumup.com.br/maquinas-de-cartao/total/

Will you also be adding support for the SumUp 3G reader in the next update? I noticed the ios sdk already has support for this.

Hi Ulissesc, Hi Niddey,
The SumUp Total reader is designed to work in full autonomy, there is no plan to have it compatible with the SDK.
The  SumUp 3G will be compatible on the next release of the SDK, you will be able to use it in Bluetooth connection (same as the AIR device).
Many thanks,


Support of request cancellation

I was working on my project, trying to cancel some API requests as following:
const TelegramBot = require('node-telegram-bot-api');

let telegramBot = new TelegramBot('BOT_TOKEN' , {polling: false})

let doAsync = () => telegramBot.sendPhoto(CHAT_ID, 'wallpaper.jpg');

doAsync().cancel();

It seems like that doAsync() is not cancellable. The request won't terminate until the photo is sent.

I found the current dependency is<EMAIL_ADDRESS>That will be nice if you could upgrade request-promise to the latest version!
A part of changelog from request-promise:
v4.1.0 (2016-07-30)
* Added cancellation support (Thanks to @not-an-aardvark for pull request #123)

This has been added in v0.25.0!
Thanks @dimotsai for your interest in this library!

@GochoMugo Good job! Thanks for supporting. This is a nice library :)


Some README work.

Codecov Report

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

@@           Coverage Diff           @@
##           master      #51   +/-   ##
=======================================
  Coverage   63.74%   63.74%
=======================================
  Files          15       15
  Lines        1371     1371
=======================================
  Hits          874      874
  Misses        400      400
  Partials       97       97

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 5acfa15...ddd89fb. Read the comment docs.


/examples directory missing in 18.0?

I am trying to access /examples/cloud-operations/network-dashboard in v18.0.0 but not seeing the directory there any longer. Am I missing something?

Yes, we renamed examples to blueprints, the folder you're looking for is still there...
https://github.com/GoogleCloudPlatform/cloud-foundation-fabric/tree/master/blueprints/cloud-operations/network-dashboard
Is there a source we could try to have updated to the new link?


Docker container fails to start

Describe the bug
Docker container fails to start
To Reproduce
Steps to reproduce the behavior:

clone https://github.com/temporalio/docker-compose
type docker compose up
log says
temporal-ui             | 2023/04/01 12:27:48 Loading config; env=docker,configDir=config temporal-ui             | 2023/04/01 12:27:48 Loading config files=[config/docker.yaml] temporal-ui             | config file corrupted: yaml: line 23: did not find expected alphabetic or numeric character temporal-ui exited with code 1

Expected behavior
Starting without errors
Screenshots

Desktop (please complete the following information):

OS: Ubuntu 22.04 LTS
Browser None
Version None

Additional context

The default one has the * part wrong, as shown in the log above. If you replace it with "*", it becomes correct syntax. But when I modified it and mounted it in the /config directory, it was overwritten and gave the same error.
If I mount it as read-only, it would exit with an error:

I must have set it up incorrectly.


Upload Cryptotrader Token

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

[ ] Filename in the lowercase format
[ ] Image format: png
[ ] Image size: 256 by 256 px

@cryptolordproject
Also, you can use these graphics to say that your ERC20 token fully compatible with Trust Wallet (https://trustwalletapp.com/logo-assets). Tokens will show up automatically once the user receives them.
Feel free to share this on social media and tag Trust Wallet:
Twitter: @TrustWalletApp
Facebook: @TrustWalletApp


NESH config and examples are outdated

The system received a significant software and hardware restructuring. All file system paths (even the file system itself) have changed, plus there is a new batch scheduler and partition structure so that the config and the examples here are now heavily outdated.
Until the NESH material is updated, you might play around with a SLURMCluster() specification yourself (without specifying the NESH config!), or use a Dask distributed LocalCluster (which limits your calculations to one compute node, though). For the latter, please open a JupyterLab session on a compute node with e.g. this script like
$ sbatch --cpus-per-task=32 --mem=180GB --time=01:00:00 jupyterlab-slurm.sh
$ sbatch --cpus-per-task=16 --mem=90GB --time=01:00:00 jupyterlab-slurm.sh

to request e.g. a full or half a compute node for e.g. one hour.

Great, it now works with this simple SLURM cluster specification:
import dask_jobqueue
cluster = dask_jobqueue.SLURMCluster(
    # Dask worker size
    cores=4, memory='24GB',
    processes=1, # Dask workers per job
    # SLURM job script things
    queue='cluster', walltime='00:15:00',
    # Dask worker network and temporary storage
    interface='ib0', local_directory='$TMPDIR'
)

Great, it now works with this simple SLURM cluster specification:
import dask_jobqueue
cluster = dask_jobqueue.SLURMCluster(
    # Dask worker size
    cores=4, memory='24GB',
    processes=1, # Dask workers per job
    # SLURM job script things
    queue='cluster', walltime='00:15:00',
    # Dask worker network and temporary storage
    interface='ib0', local_directory='$TMPDIR'
)

cc @Kristin-2002

cc @Kristin-2002


Empty @_moveOnly struct crashes swiftc

https://godbolt.org/z/M9xdhK7q4
The following crashes swiftc when -enable-experimental-move-only is passed:
@_moveOnly
struct Foo { }

swift-frontend: /home/build-user/swift/lib/SIL/Utils/FieldSensitivePrunedLiveness.cpp:431: bool swift::FieldSensitivePrunedLiveRange<swift::FieldSensitiveMultiDefPrunedLiveRange>::isWithinBoundary(swift::SILInstruction *, swift::TypeTreeLeafTypeRange) const [LivenessWithDefs = swift::FieldSensitiveMultiDefPrunedLiveRange]: Assertion `asImpl().isInitialized()' failed.

Not yet a supported feature, but it would be nice not to crash here.

CC @gottesmm

This is known.

Specifically this is rdar://104395115

This was fixed some time ago.


Separate serializer classes

Inserted classes for basic serializer/materializer. Used it to read/write variable length encoded values in cluster record

Should be merged after #135


Fix final-vars type inferring

Purpose
$title
Fixes #18166
Remarks
Came across https://github.com/ballerina-platform/ballerina-lang/issues/22959 while fixing this. This can be improved for const maps once it is fixed.
Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[x] Added necessary tests

[x] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

May be not related to this PR. But I notice that a error message which may deceive the user.
Code
    final var x = 1.6;
    x = 4.5;

Output
error: .::t1.bal:13:5: cannot assign a value to final 'x'
error: .::t1.bal:13:9: incompatible types: expected '1.6f', found 'float'

I think giving the second error message on the same line is wrong after the previous error. Probably due to checkConstantAssignment not setting expression type to semantic error.
https://github.com/ballerina-platform/ballerina-lang/blob/3831af1e92563161e20d1f33023586f52ce0f43f/compiler/ballerina-lang/src/main/java/org/wso2/ballerinalang/compiler/semantics/analyzer/SemanticAnalyzer.java#L2793
https://github.com/ballerina-platform/ballerina-lang/blob/3831af1e92563161e20d1f33023586f52ce0f43f/compiler/ballerina-lang/src/main/java/org/wso2/ballerinalang/compiler/semantics/analyzer/SemanticAnalyzer.java#L2139

Closing this temporarily.


Flannel crashoff on k3s <<<rasperry pi 4 arm64 debian bookworm

Environmental Info:
K3s Version:

Node(s) CPU architecture, OS, and Version:

Cluster Configuration:
1 Node inclu. Master
no spezifisch

Your issue report appears to be truncated? Please provide logs showing the specific errors encountered when k3s crashes on your node.


policy callback 'policy_params_fn' for other algorithms?

currently,  policy_params_fn exists only in ppo algorithm. are you going to update the policy clalback function to other algorithms too?

Hi @Rian-Jo , wasn't planning on updating that any time soon, feel free to open up a PR!


Set yarn integrity check to false for development

closes #60
I'm actually too afraid to disentangle webpacker from the app, so just flipping the yarn integrity check to false since we shouldn't be using it anyway.

@littleforest 👍


Add typescript definitions for the main exports

This feature is experimental.  Since I don't use TypeScript, I need someone who does to take a look and verify before i merge this.

node_modules/id128/index.d.ts:65:2 - error TS1169: A computed property name in an interface must refer to an expression whose type is a literal type or a 'unique symbol' type.

65  [Sybol.toStringTag]: string;
    ~~~~~~~~~~~~~~~~~~~

node_modules/id128/index.d.ts:65:3 - error TS2552: Cannot find name 'Sybol'. Did you mean 'Symbol'?

65  [Sybol.toStringTag]: string;
     ~~~~~

  node_modules/typescript/lib/lib.es2015.symbol.d.ts:48:13
    48 declare var Symbol: SymbolConstructor;
                   ~~~~~~
    'Symbol' is declared here.

node_modules/id128/index.d.ts:107:1 - error TS1046: Top-level declarations in .d.ts files must start with either a 'declare' or 'export' modifier.

107 class Id128Error extends Error {}
    ~~~~~

node_modules/id128/index.d.ts:115:2 - error TS1038: A 'declare' modifier cannot be used in an already ambient context.

115  declare const Ulid: UlidFactory;
     ~~~~~~~

node_modules/id128/index.d.ts:116:2 - error TS1038: A 'declare' modifier cannot be used in an already ambient context.

116  declare const UlidMonotonic: UlidMonotonicFactory;
     ~~~~~~~

node_modules/id128/index.d.ts:117:2 - error TS1038: A 'declare' modifier cannot be used in an already ambient context.

117  declare const Uuid: UuidFactory;
     ~~~~~~~

node_modules/id128/index.d.ts:118:2 - error TS1038: A 'declare' modifier cannot be used in an already ambient context.

118  declare const Uuid1: Uuid1Factory;
     ~~~~~~~

node_modules/id128/index.d.ts:119:2 - error TS1038: A 'declare' modifier cannot be used in an already ambient context.

119  declare const Uuid4: Uuid4Factory;
     ~~~~~~~

node_modules/id128/index.d.ts:120:2 - error TS1038: A 'declare' modifier cannot be used in an already ambient context.

120  declare const Uuid6: Uuid6Factory;
     ~~~~~~~

node_modules/id128/index.d.ts:121:2 - error TS1038: A 'declare' modifier cannot be used in an already ambient context.

121  declare const UuidNil: UuidNilFactory;
     ~~~~~~~

node_modules/id128/index.d.ts:123:2 - error TS1038: A 'declare' modifier cannot be used in an already ambient context.

123  declare namespace Exception {
     ~~~~~~~

node_modules/id128/index.d.ts:124:3 - error TS1038: A 'declare' modifier cannot be used in an already ambient context.

124     declare const Id128Error: Id128Error;
        ~~~~~~~

node_modules/id128/index.d.ts:125:3 - error TS1038: A 'declare' modifier cannot be used in an already ambient context.

125     declare const ClockSequenceOverflow: ClockSequenceOverflow;
        ~~~~~~~

node_modules/id128/index.d.ts:126:3 - error TS1038: A 'declare' modifier cannot be used in an already ambient context.

126     declare const InvalidBytes: InvalidBytes;
        ~~~~~~~

node_modules/id128/index.d.ts:127:3 - error TS1038: A 'declare' modifier cannot be used in an already ambient context.

127     declare const InvalidEncoding: InvalidEncoding;
        ~~~~~~~

node_modules/id128/index.d.ts:128:3 - error TS1038: A 'declare' modifier cannot be used in an already ambient context.

128     declare const InvalidEpoch: InvalidEpoch;
        ~~~~~~~

node_modules/id128/index.d.ts:129:3 - error TS1038: A 'declare' modifier cannot be used in an already ambient context.

129     declare const UnsupportedVersion: UnsupportedVersion;
        ~~~~~~~

It all compiles for me locally.  Please check that it actually integrates properly.  Also, I'm worried I'm bleeding types into the global namespace.  any guidance is much appreciated.

@patarapolw: Seriously, thank you for the feedback.   i've been waiting for comments to know if i can merge this since i don't write typescript.  i'll review and push a modification in the next few days.

@patarapolw  2 thoughts:

the use of unknown in this code seems equivalent to saying: "any value will do because i won't inspect it anyway".  i'm not sure I want that because it limits the ability to augment the options in the future.  by keeping it an optional {}, i can guarantee an upgradable interface.  I want the type system to say: "give me nothing or any named parameters you wish.  i'll select out what's important."  in this regard, does {} create any type issues?
i want to make sure i don't leak any of the intermediate types to to limit confusion and allow for flexibility in any future rearchitecting.  how does wrapping the file in declare module "id128" { ... } affect the visibility of the intermediate types?  what would the import line look like with this change?

unknown vs {}

{} may cause conflict in your JavaScript, unless you use // @ts-check in your JavaScript code in VSCode (not sure about WebStorm).
unknown instead will prompt // @ts-check users to declare type (via JSDoc /** @type {*} */).
Otherwise, I believe it is no different. It behaves almost the same for end-users.

how does wrapping the file in declare module "id128" { ... } affect the visibility of the intermediate types? what would the import line look like with this change?

declare module "id128" { ... } just means that you use your own declaration.d.ts, without an @types/ folder. Nothing more.
However, if you publish your own index.d.ts, there will be no declare module.

i have verified the type file locally using visual studio code.  i will clean this up and merge it shortly.


Latex LargeOperator inputs crashing application, for example \int_a^b

Open Try tab, enter the following latex \int_a^b  and you'll get
System.ArgumentNullException: 'LaTeX Symbol name must not be null.
Parameter name: symbolName'
NOTE: i'm trying to fix it myself, just need few days to get familiar with codebase first.

You will need to update Xamarin.Forms to <IP_ADDRESS>5677 before being able to build the Example project.

Better to investigate this commit instead.

nope, the problem was before. The commit just brings usage of MathListBuilder.MathListToString.
Simple test:
    [Fact]
    public void TestListToString() {
      var input = @"\int_a^b";
      var list = MathLists.FromString(input);
      var str = MathListBuilder.MathListToString(list);
      Assert.Equal(input, str);
    }

nope, the problem was before. The commit just brings usage of MathListBuilder.MathListToString.
Simple test:
    [Fact]
    public void TestListToString() {
      var input = @"\int_a^b";
      var list = MathLists.FromString(input);
      var str = MathListBuilder.MathListToString(list);
      Assert.Equal(input, str);
    }

Btw mathlisttostring returns "\int ^b_a" as a result, this is also bug right ?

I think that's just ordering of scripts that don't affect the result.

I think that's just ordering of scripts that don't affect the result.

but test is fails

That's just an example, as the result has the same meaning in LaTeX as the input, the test should be modified to accommodate the result.

Related code is here:
https://github.com/verybadcat/CSharpMath/blob/master/CSharpMath/Atoms/Factories/MathListBuilder.cs#L773-L780
So, if replace order of applying it gives \int _a^b indeed.

And it will fail for \int ^a_b.

yep, but at least it doesn't look odd for those who not so confident with LaTeX :-)
Maybe we can adjust/improve output somehow?

Maybe we can adjust/improve output somehow?

I have an idea how to do that, today later i'll update my pr.

And it will fail for \int ^a_b.

Guys I've fixed this, the only thing i've got rid whitespace to make make TestListToString unittest work. If we do need that whitespaces, then maybe better to keep them in clean whitespaces on unittests ?

The whitespace is required for cases like \sqrt a where it will become \sqrta when the space is not present, which parses as a single command.

This library is not held together by a strong type system and it definitely shows here. The eventual F# version will be a lot more structured.
This bug is an intersection of a number of problems, so there are several potential lines of attack, including fixing the limits/nolimits data on LargeOperator, expanding the AliasMap, overriding equality to make operators with different data equal, avoiding AliasMap by iterating over a list to find data, or storing TeX names in data.
I think the most efficient fix is to make the smallest, and most direct and obvious correction, which is to avoid labelling all Operators as LargeOperators. We have a problem with operators, these are incorrectly given LargeOperator types and irrelevant data about "limits"/"nolimits", and that irrelevant data is causing problems in the very fragile conversion to latex algorithms.

Actually the overuse of LargeOperators turned out to be unrelated.
The fix was to work around/with AliasDictionary:
- var command = MathAtoms.LatexSymbolNameForAtom(op);
+ var command = MathAtoms.LatexSymbolNameForAtom(new LargeOperator(op.Nucleus, null));

But the other changes in my PR I think are worth taking too as cleanup/correctness.

Agreed. Objective C in iosMath did not have a strong type system and CSharpMath inherited from it.


article_search_for_user crashes ?

this is what I see in the logs:
[Thu Sep 12 15:11:54.809889 2024] [wsgi:error] [pid 22:tid<PHONE_NUMBER>44288] [remote <IP_ADDRESS>:59078]   File "/Zeeguu-API/zeeguu/api/endpoints/search.py", line 237, in search_for_search_terms
[Thu Sep 12 15:11:54.809892 2024] [wsgi:error] [pid 22:tid<PHONE_NUMBER>44288] [remote <IP_ADDRESS>:59078]     articles = article_search_for_user(
[Thu Sep 12 15:11:54.810303 2024] [wsgi:error] [pid 22:tid<PHONE_NUMBER>44288] [remote <IP_ADDRESS>:59078]                ^^^^^^^^^^^^^^^^^^^^^^^^
[Thu Sep 12 15:11:54.810306 2024] [wsgi:error] [pid 22:tid<PHONE_NUMBER>44288] [remote <IP_ADDRESS>:59078]   File "/Zeeguu-API/zeeguu/core/util/timer_logging_decorator.py", line 10, in wrapper
[Thu Sep 12 15:11:54.810309 2024] [wsgi:error] [pid 22:tid<PHONE_NUMBER>44288] [remote <IP_ADDRESS>:59078]     result = func(*args, **kwargs)
[Thu Sep 12 15:11:54.818058 2024] [wsgi:error] [pid 22:tid<PHONE_NUMBER>44288] [remote <IP_ADDRESS>:59078]              ^^^^^^^^^^^^^^^^^^^^^
[Thu Sep 12 15:11:54.825091 2024] [wsgi:error] [pid 22:tid<PHONE_NUMBER>44288] [remote <IP_ADDRESS>:59078]   File "/Zeeguu-API/zeeguu/core/content_recommender/elastic_recommender.py", line 195, in article_search_for_user
[Thu Sep 12 15:11:54.825096 2024] [wsgi:error] [pid 22:tid<PHONE_NUMBER>44288] [remote <IP_ADDRESS>:59078]     ) = _prepare_user_constraints(user)
[Thu Sep 12 15:11:54.832280 2024] [wsgi:error] [pid 22:tid<PHONE_NUMBER>44288] [remote <IP_ADDRESS>:59078]         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[Thu Sep 12 15:11:54.832289 2024] [wsgi:error] [pid 22:tid<PHONE_NUMBER>44288] [remote <IP_ADDRESS>:59078]   File "/Zeeguu-API/zeeguu/core/content_recommender/elastic_recommender.py", line 40, in _prepare_user_constraints
[Thu Sep 12 15:11:54.832292 2024] [wsgi:error] [pid 22:tid<PHONE_NUMBER>44288] [remote <IP_ADDRESS>:59078]     declared_level_min, declared_level_max = user.levels_for(language)
[Thu Sep 12 15:11:54.833230 2024] [wsgi:error] [pid 22:tid<PHONE_NUMBER>44288] [remote <IP_ADDRESS>:59078]                                              ^^^^^^^^^^^^^^^^^^^^^^^^^
[Thu Sep 12 15:11:54.833233 2024] [wsgi:error] [pid 22:tid<PHONE_NUMBER>44288] [remote <IP_ADDRESS>:59078]   File "/Zeeguu-API/zeeguu/core/model/user.py", line 734, in levels_for
[Thu Sep 12 15:11:54.833749 2024] [wsgi:error] [pid 22:tid<PHONE_NUMBER>44288] [remote <IP_ADDRESS>:59078]     if currentCohort.language == language:
[Thu Sep 12 15:11:54.833751 2024] [wsgi:error] [pid 22:tid<PHONE_NUMBER>44288] [remote <IP_ADDRESS>:59078]        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[Thu Sep 12 15:11:54.833754 2024] [wsgi:error] [pid 22:tid<PHONE_NUMBER>44288] [remote <IP_ADDRESS>:59078]   File "/Zeeguu-API/zeeguu/core/model/language.py", line 105, in __eq__
[Thu Sep 12 15:11:54.833760 2024] [wsgi:error] [pid 22:tid<PHONE_NUMBER>44288] [remote <IP_ADDRESS>:59078]     return self.code == other.code or self.name == other.name
[Thu Sep 12 15:11:54.840241 2024] [wsgi:error] [pid 22:tid<PHONE_NUMBER>44288] [remote <IP_ADDRESS>:59078]                         ^^^^^^^^^^
[Thu Sep 12 15:11:54.842547 2024] [wsgi:error] [pid 22:tid<PHONE_NUMBER>44288] [remote <IP_ADDRESS>:59078] AttributeError: 'NoneType' object has no attribute 'code'

I unenrolled from the Merle class and then the error went away.
Does that classroom not have an associated language code?
// pause while checking...
Indeed, that cohort does not have an associated language.

i was too fast to push directly to master instead of sending you a PR.
so here's a heads up @tfnribeiro of how this bug was fixed: in the commit above i've removed the complicated and unnecessary feature. the bug is fixed also in the comment, if we ever uncomment by doing if each_cohort.language and each_cohort.language == language:. But I don't think we'll ever need that code again.


missing author for valid Atom

The event and agent feeds and entries need to have an author element to be valid Atom.
Need authors at:
/APP/event/
/APP/agent/
/APP/event/87bf2dcc7af14c78a4dd614ad1c11210/
/APP/agent/codaIngest/

Atom spec says author field should be a person construct, allowing for a name, email, and uri. What do we want for these? @ldko

I think we have been using what is in this. Is an email required?

No, uri and email are allowed but not required. I think only name is mandatory.
I'll use the same thing that's in codalib.


TAB can trigger Helm when Emacs is running slowly

When Emacs is running very slowly due to CPU load, it's possible to press TAB before the Company completions menu appears. This triggers a Helm completions buffer, which is disorienting. This latter behavior should be unbound from TAB.

Resolved in 2d37193acdc91c04348b3032620292a490df91fc.


Use block cache in get_pool_for_block

Occasionally I see the following error:
getrawtransaction failed for Bitcoin Core 0.18.1 (id=121): code: `0`; return_code: `got_nothing`; body: ``
/app/app/services/bitcoin_client.rb:195:in `rescue in getrawtransaction'

We could fetch the transaction via p2p (and keep trying if it fails) after #110. But it's probably easier to build on #111 and get the coinbase transaction directly from the cached block data, instead of fetching the transaction separately.

I haven't seen this since.


feat(core): css color parser

Add support for parsing css color function.
https://developer.mozilla.org/en-US/docs/Web/CSS/color_value
If this can proceed, the next steps are:

To parse proper color component type as currentyl everything is string-based. However, with current presets logic, only the alpha is used for arithmatic while the components mostly being joined.
To switch the presets from using RGBAColorValue to the new color type.

My concerns are whether we should support css built-in color keywords https://developer.mozilla.org/en-US/docs/Web/CSS/color_value#color_keywords. My take is just to support transparent/black/white & rebeccapurple

Should be good for now, except for more test & name changes.

I am a bit concerned about the complexity added to the core. Many at this point, we should extract those utilities in core and preset-mini to a more general @unocss/utils package?

I'm ok eaither way. Although some that I can think of splitting mostly related to css value utilities.


issues 310: Create stub files for all exercises

stub file for "Two Fer" task solution is appended
tests are un-ignored, as they got compilable over the main source base

The stub is questionable if the following aspects.
It contains hints to study about

internal scope, which is one of the label Kt features
single-expression function which is concise and idomatic tool

It does not contain a clue for default arguments. I just do not know how to mention it withount giving a precise solution.
It is quite a Kotlin-like, but I'm not sure if it fits Exercism studying methodics.
Do you wish the stub to stay as close to the reference solution as possibl?
Do you want to avoid distraction by extra study motivators (like internal keyword and = sign in a function signture)?
If you do, I will rework the stub for sure.
If you don't, I have anoher proposal: can I add these links in the function's kotlin-doc?

Why are the tests un-ignored? Only the first test should be enabled.
IMO, the stub does not need to compile, but I think it's find to give a stub without a default argument. It's a pretty natural path to add a default argument as you go.

All questionable things are undone.
We stll cannot get this compiled until PR 318  is merged.

If you don't, I have anoher proposal: can I add these links in the function's kotlin-doc?

If you show me what that would look like... sure :)

Nice!
Don't use KDoc for this, but the TrackInsert hint! Then, readme needs to be re-generated. The hint will become part of README.md.
Yes, use TODO!! That's a great fit.

Got it. Will remove the KDocs from both stubs to call it a day for this PR. Will open another one for TrackHints.

@dector if you squash-merge here, those steps are unnecessary.

@SleeplessByte Kinda. I'm not using built-in functionality here intentionally.
I'm not sure how it handles commit author info (especially, for signed commits). There is some open issues. I'm just not familiar how and what this merge mode does behind the curtain. :)
There is no rush for this PR so I suggested to do it manually.

Guys, I do appreciate your help and care. Just let me sort it out. Taming this rebase became an affair of honor for me.

@dector, made it. Can you please merge?