text:
WIP : Upgrade chat console for rasa12

As I said, still working on it, so I put it as a WIP.
To clarify the code, I split your core_router class into two class. Most of the current code is in core_server_V10 (with the lastest update) and I put mine in core_server_V12 which is chose when the core version is > 11
#132

@pradeepmvn - do you have some experience with Rasa Core to check this PR?

Change to WIP again since I need to use the correct model when calling (using the default one for the moment)

@paschmann Sure. This would be a major implementation change. We might need more time to test different componets and make sure both the versions are in good shape before we merge.
@huberrom Awesome work!! Can you please update once you are done. Will pull this and run some tests.

@huberrom Iam thinking should we even need rasa-ui to proxy rasa core requests for v12 and above? I think the bot can directly hit the rasa core end point and rasa-ui can piggyback on it for conversations and history.

@huberrom Makes sense. thanks Huberrom. I will merge into master. Thanks for your contribution.

authors: huberrom paschmann pradeepmvn

repo: paschmann/rasa-ui


text:
🛑 argocd is down

In 1ea66d7, argocd (https://argocd.pastis-hosting.net) was down:

HTTP code: 521
Response time: 193 ms

Resolved: argocd is back up in 223c89f.

source: gharchive/issue

repo: pastis-hosting/status

license: MIT

license_type: permissive

license_source: github-api


text:
Update projection.md

Added missing name column in projection example

@robinlehrmann thanks :)

@robinlehrmann thanks :)

source: gharchive/pull-request

authors: DavidBadura robinlehrmann

repo: patchlevel/event-sourcing


text:
Just Errors in console

After extracting, running and guessing the port (why isn't this mentioned anywhere?) to connect, when i open the server on a browser I get this and the links don't work:

The Console only shows error and warnings:

What am I mssing?

working now, I thinks it was a firewall problem

repo: pathartl/LANCommander


text:
Add +money pop up when car crashes

[x] #110

[ ]  Replace money png with transparent background or redraw it iunno wahtever you want linco

#109 Add +money pop up when car crashes

repo: patriacaelum/godot-template

license: Unlicense


text:
Shortcut for optim.init

Hi Patrick,
what do you think about having a shortcut for this:
optim.init(eqx.filter(model, eqx.is_array))

The initialization of optim always trips me up. Maybe having something like
optim = optax.adam(learning_rate)
eqx.init_optim(optim, model)

def init_optim(optim: optax.GradientTransformation, model: PyTree):
    return optim.init(eqx.filter(model, eqx.is_array))

could be helpful.
One reason against this would probably be having optax as a dependency.

I'm afraid that I'm inclined against this, just because I'd prefer for Equinox to have as small an API surface as possible. That keeps it easy to learn. (Although the API has certainly grown a lot over time.) Even the existence of eqx.apply_updates makes me a bit annoyed, actually -- it's just a tree-map over addition, after all!
FWIW this wouldn't need Optax as a dependency though, since it's only explicitly used as a type annotation.

Okay, got it. I had thought since there exists eqx.apply_updates (and this init is kind of related) that you actually wanted these helpers, but turns out it was the other way around 😄. I can fully understand the rational. Closing this then.

authors: Artur-Galstyan patrick-kidger

repo: patrick-kidger/equinox

license_source: bigquery


text:
[TPU] XLA: Channel is used for multiple host instructions

I'm training a custom arch of mine, and had a usecase where I wanted to perform 2 (different) forward passes which have a different computational graph. I wanted to take the outputs from both flows, and evaluate an aggregated loss.
But apparently, if I compute two branches, I get the below error.
Traceback
Traceback (most recent call last):
  File "/kaggle/working/ReAct_Jax/train_model.py", line 47, in <module>
    main(key)
  File "/kaggle/working/ReAct_Jax/train_model.py", line 43, in main
    trainer.train(args.epochs, trainloader, valloader, key)
  File "/kaggle/working/ReAct_Jax/ReAct/utils/trainer.py", line 235, in train
    loss, model, opt_state = make_step(model, seq, label, pad_mask, rndm_n, rndm_k,
                             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/equinox/_jit.py", line 206, in __call__
    return self._call(False, args, kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/equinox/_module.py", line 875, in __call__
    return self.__func__(self.__self__, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/equinox/_jit.py", line 198, in _call
    out = self._cached(dynamic_donate, dynamic_nodonate, static)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
jaxlib.xla_extension.XlaRuntimeError: INTERNAL: during context [pre-optimization]: RET_CHECK failure (third_party/tensorflow/compiler/xla/service/hlo_verifier.cc:2330) instructions.size() == 2 channel 11 is used for multiple host send/recv instructions
--------------------
For simplicity, JAX has removed its internal frames from the traceback of the following exception. Set JAX_TRACEBACK_FILTERING=off to include these.

Code
I don't have a repro unfortunately. But my codeflow looks like this:
@jax.jit
def n_k_loop(model: eqx.Module, input_arr: Array, pad_mask: Array, n: int, k: int, key: PRNGKeyArray) -> Array:
    key1, key2 = jax.random.split(key, 2)

    # forward pass the model without tracking grads
    _, intermediate_array = model(
        input_arr, n,
        pad_mask=pad_mask,
        prev_thought=None,
        key=key1)

    intermediate_array = jax.lax.stop_gradient(intermediate_array)

    # n-k passes, but track the gradient this time
    output, _ = model(input_arr, k, pad_mask=pad_mask, prev_thought=intermediate_array, key=key2)

    return output

@jax.jit
def k_loop(model: eqx.Module, input_arr: Array, pad_mask: Array, n: int, k: int, key: PRNGKeyArray) -> Array:
    key1, key2 = jax.random.split(key, 2)

    output, _ = model(input_arr, n, pad_mask=pad_mask, prev_thought=None, key=key1)

    return output

This is a bit convoluted, but the core is that there are the 2 different forward passes which explicitly depend on the same model and is reutilized here, with slightly different arguments (mainly prev_thought)
Because the error occurs only when both of the flows are present - either through using jax.lax.cond to dynamically switch between both or simply aggregating outputs from both forward passes simultaneously, the common problem seems to be when XLA is unable to handle both computational flows.
(Note: jax.lax.cond is lowered to select when vmap-ed, which is why both flows do end up getting computed too)

This error is triggered only on TPUs, not on GPUs so perhaps it might just turn out to be a limitation of equinox. I don't understand much of how equinox maintains state - my basic understanding is that the actual state at runtime is held by jax internally and equinox just issues host callbacks to mutate that state as needed - where the Module is just the abstract PyTree representation?

The error kindof sounds like equinox issued multiple host callbacks and they collide. Why its only a problem on TPUs specifically, could be down to TPU-specific optimizations of XLA.

Would you have any idea regarding this?

This looks like a bug in XLA:TPU. I'd suggest filing it either on the main JAX repository or on the XLA repo. You'll probably need to find a MWE, though.

I don't understand much of how equinox maintains state - my basic understanding is that the actual state at runtime is held by jax internally and equinox just issues host callbacks to mutate that state as needed - where the Module is just the abstract PyTree representation?

Equinox doesn't maintain any state, actually! It was an important part of Equinox's design that we not go around mutating things. The Module is a PyTree of arrays, and these are explicitly updated, by you, when you do things like gradient descent.
Equinox actually uses callbacks sparingly -- these are the only functions which use them, and they're all fairly uncommon:

eqx.error_if, eqx.branched_error_if,
eqx.filter_pure_callback,
eqx.debug.store_dce,
eqx.internal.noinline (and this one isn't even a documented feature :) )

are you explicitly using any of these?

are you explicitly using any of these?

Nope. So its probably some constraint on TPUs placed by XLA 😥 I guess I'll try and debug it, but so far hadn't had any luck

@patrick-kidger Turns out, the problem was using eqx.internal.while_loop, specifically the checkpoint-ed form. Using the bounded type of loop works perfectly fine.
I don't know if you feel its worth it to resolve the bug on TPUs 😅 If you have access to them, I can try to make a repro for them.

Ah! Indeed I'd forgotten, eqx.internal.while_loop uses eqx.error_if, which then uses a callback.
I'd suggest reporting this as an XLA bug regardless, but it's probably not a bug I can resolve directly.
As a possible workaround, you can try commenting out every error_if inside the implementation of eqx.internal.while_loop. I imagine I'll actually do something like that in the next release of Equinox, actually -- this code has now proven itself pretty reliable.

Thanks! I tried commenting out all the callbacks and rebuilt equinox like this and kind='checkpointed works pretty well now.
I talked to James Bradbury on twitter, and he said its a bit harder to work with equinox as host callbacks as "messy" and are closer to a "hack" so its likely that its clashing with some TPU specific optimizations built directly into XLA. I guess it'd require quite a bit of surgery to fix this bug - so it might be some time before its fixed 🙂
Until that's fixed, I suppose in the next release, maybe you could expose some flag for internal.while_loop that optionally disables host callbacks if the user desires (atleast the non-critical ones). It might go against the equinox philosophy of simplicity I suppose, but IMO its fine because its already an internal application to users are more likely to be careful when using it and (hopefully) read all the documentation.
Again, thanks for everything and providing such a lovely library ❤ and have a good weekend!

Ah, marvellous! I'm glad that's working for you. I've just written #631 to fix this up for the next release.
Since it is specifically error_if that is causing you problem,s the one other option worth knowing is the environment variable EQX_ON_ERROR=nan. (Documentation here.) This will disable every eqx.error_if used anywhere in your program. This is really intended as a "debug vs release mode" optimisation -- to remove the checks once you're satisfied that your program should always work. But it could also help with this issue.

Looks like using EQX_ON_ERROR=nan works pretty well here and resolves the issue 😄
#631 looks good - I guess in the future, if more XLA bugs crop up, we could setup a dedicated TPU_DEBUGGING flag that in turn would switch on and off the various flags to minimize collisions with XLA, since its a bit of a black box that we usually need to work around...
Thanks for everything again and have a great weekend!


text:
@click handler

I'd like to be able to utilize Vue's @click handler in order to swap between two layers when the user clicked the minimap. Something like this...
<vue-leaflet-minimap
    :layer="minimapLayer"
    :options="minimapOptions"
    @click="switchLayer"
/>

But, this component doesn't seem to react to the @click. Is there any vuejs way to solving this problem with minimal vanilla javascript?

The rendering of the minimap is handled by Leaflet and I don't believe the minimap plugin has a click event listener set.
I'd probably recommend using the emitted ready event which passes the minimap plugin instance. Then you can add your own event listeners.
Something like:
methods: {
  minimapReady(minimap) {
   ... add event listener here.
  }
}
...
<vue-leaflet-minimap
    :layer="minimapLayer"
    :options="minimapOptions"
    @ready="minimapReady"
/>

authors: CodyBontecou patrickcate

repo: patrickcate/vue-leaflet-minimap


text:
add a second state without filter selector

Hi, i was looking for an example to add a selector (state) when the user select other option, for example:

Color
<button type="button" class="control control-color" data-filter=".green">Green</button>
<button type="button" class="control control-color" data-filter=".blue">Blue</button>
<button type="button" class="control control-color" data-filter=".pink">Pink</button>
<button type="button" class="control control-color hidden" data-filter=".red">Red</button>

I have this RED button in the markup to add the class to some options, but I wont show it in the page, but I need to display the Red matching products when the Pink one is selected, I found something similar with the "comand"function, but this override the mix filter results. I need to only showing both matching products (red and pink) when the Pink is selected, with no Red filter display. Any suggestion?
Thanks

If you need to show or hide your control buttons based on which filter is selected, you can do this by hooking into the onMixEnd callback, and checking the state.activeFilter.selector to determine the current filter and which controls should be hidden or shown. This requires writing a small amount of custom JavaScript.
If you need to actually adjust your filter results based on which filter is selected, it might be better just to add a "red" classname to every "pink" product. That way whenever you filter by "pink", it will show all the "red" items too. I'm not sure if this is what you want, but that would be very easy to achieve purely by adjusting your HTML.
If you want to do anything more complex, you would need to create your own control event handlers, and then manually create your desired DOM selector string and send it to MixItUp via its API (e.g. mixer.filter('.red, .pink').
I hope that helps.

Thanks, just adjusted the HTML. thanks so much. !

authors: gcoutino patrickkunka

repo: patrickkunka/mixitup


text:
switchover pg cluster，but master not failover

What happened?
Before creating slots and pubs, the switchover is executed multiple times and is not aware of the service
master：
first ：create slot and pub
second： pgsync-service sub pub
three：patronictl switchover cluster_name
|># patronictl switchover cvd
Current cluster topology

Cluster: cvd (7340474031893890113) -------+-----------+----+-----------+----------------------+
| Member          | Host          | Role    | State     | TL | Lag in MB | Tags                 |
+-----------------+---------------+---------+-----------+----+-----------+----------------------+
| pgsql16_node001 | ******| Leader  | running   | 22 |           | failover_priority: 2 |
|                 |               |         |           |    |           | spec: 16C.64G.500G   |
|                 |               |         |           |    |           | version: '16.2'      |
+-----------------+---------------+---------+-----------+----+-----------+----------------------+
| pgsql16_node002 | ******| Replica | streaming | 22 |         0 | failover_priority: 2 |
|                 |               |         |           |    |           | spec: 8C.32G.500G    |
|                 |               |         |           |    |           | version: '16.2'      |
+-----------------+---------------+---------+-----------+----+-----------+----------------------+
Primary [pgsql16_node001]:
Candidate ['pgsql16_node002'] []:
When should the switchover take place (e.g. 2024-07-17T17:59 )  [now]:
Are you sure you want to switchover cluster cvd, demoting current leader pgsql16_node001? [y/N]: y
Switchover failed, details: 503, Switchover status unknown

switchover/failover failed many number but leader status is stop and  not improved slave to the master
|># patronictl list

Cluster: cvd (7340474031893890113) -------+-----------+----+-----------+----------------------+
| Member          | Host          | Role    | State     | TL | Lag in MB | Tags                 |
+-----------------+---------------+---------+-----------+----+-----------+----------------------+
| pgsql16_node001 | *****| Leader  | stopping  |    |           | failover_priority: 2 |
|                 |               |         |           |    |           | spec: 16C.64G.500G   |
|                 |               |         |           |    |           | version: '16.2'      |
+-----------------+---------------+---------+-----------+----+-----------+----------------------+
| pgsql16_node002 | ****| Replica | streaming | 22 |         0 | failover_priority: 2 |
|                 |               |         |           |    |           | spec: 8C.32G.500G    |
|                 |               |         |           |    |           | version: '16.2'      |
+-----------------+---------------+---------+-----------+----+-----------+----------------------+

How can we reproduce it (as minimally and precisely as possible)?
patroni 3.2.2
pg 16.2
操作系统 centos7
What did you expect to happen?
one: i hope swithover failed and master status is not ok，quickly elevate from the master
two: Is there any parameter control that can synchronize pub and slots to the new master during master-slave switching
Patroni/PostgreSQL/DCS version

Patroni version: 3.2.2
PostgreSQL version:
DCS (and its version):

Patroni configuration file
loop_wait: 10
maximum_lag_on_failover: 1048576
postgresql:
  parameters:
    archive_cleanup_command: find ../wal_archive/ -type f -mtime +1 -delete
    archive_command: mkdir -p ../wal_archive/ && test ! -f ../wal_archive/%f && cp %p ../wal_archive/%f
    archive_mode: 'off'
    archive_timeout: 1800s
  pg_hba:
  - local all all trust
  - local replication all trust
  - host all all 127.0.0.1/32 trust
  - host all all ::1/128 trust
  - host replication all 127.0.0.1/32 trust
  - host replication all ::1/128 trust
  recovery_conf:
    restore_command: cp ../wal_archive/%f %p
  remove_data_directory_on_rewind_failure: true
  use_pg_rewind: true
  use_slots: true
primary_start_timeout: 20
primary_stop_timeout: 30
retry_timeout: 10
synchronous_mode: false
ttl: 30

patronictl show-config
loop_wait: 10
maximum_lag_on_failover: 1048576
postgresql:
  parameters:
    archive_cleanup_command: find ../wal_archive/ -type f -mtime +1 -delete
    archive_command: mkdir -p ../wal_archive/ && test ! -f ../wal_archive/%f && cp %p ../wal_archive/%f
    archive_mode: 'off'
    archive_timeout: 1800s
  pg_hba:
  - local all all trust
  - local replication all trust
  - host all all 127.0.0.1/32 trust
  - host all all ::1/128 trust
  - host replication all 127.0.0.1/32 trust
  - host replication all ::1/128 trust
  recovery_conf:
    restore_command: cp ../wal_archive/%f %p
  remove_data_directory_on_rewind_failure: true
  use_pg_rewind: true
  use_slots: true
primary_start_timeout: 20
primary_stop_timeout: 30
retry_timeout: 10
synchronous_mode: false
ttl: 30

Patroni log files
2024-07-17 17:00:03 +0800 INFO: Lock owner: pgsql16_node001; I am pgsql16_node001
2024-07-17 17:00:03 +0800 INFO: updated leader lock during switchover: demote
2024-07-17 17:00:13 +0800 INFO: Lock owner: pgsql16_node001; I am pgsql16_node001
2024-07-17 17:00:13 +0800 INFO: updated leader lock during switchover: demote
2024-07-17 17:00:16 +0800 INFO: received switchover request with leader=pgsql16_node001 candidate=None scheduled_at=None
2024-07-17 17:00:16 +0800 INFO: Got response from pgsql16_node002 http://************:8008/patroni: {"state": "running", "postmaster_start_time": "2024-07-17 16:36:23.167047+08:00", "role": "replica", "server_version": 160002, "xlog": {"received_location": 8417605990328, "replayed_location": 8417605990328, "replayed_timestamp": "2024-07-17 16:59:36.614582+08:00", "paused": false}, "timeline": 22, "replication_state": "streaming", "dcs_last_seen": 1721206814, "tags": {"failover_priority": 2, "version": "16.2", "spec": "8C.32G.500G"}, "database_system_identifier": "7340474031893890113", "patroni": {"version": "3.2.2", "scope": "cvd", "name": "pgsql16_node002"}}
2024-07-17 17:00:16 +0800 INFO: Lock owner: pgsql16_node001; I am pgsql16_node001
2024-07-17 17:00:16 +0800 INFO: updated leader lock during switchover: demote
2024-07-17 17:00:26 +0800 INFO: Lock owner: pgsql16_node001; I am pgsql16_node001
2024-07-17 17:00:26 +0800 INFO: updated leader lock during switchover: demote
2024-07-17 17:00:36 +0800 INFO: Lock owner: pgsql16_node001; I am pgsql16_node001
2024-07-17 17:00:36 +0800 INFO: updated leader lock during switchover: demote
2024-07-17 17:00:46 +0800 INFO: Lock owner: pgsql16_node001; I am pgsql16_node001
2024-07-17 17:00:46 +0800 INFO: updated leader lock during switchover: demote
2024-07-17 17:00:56 +0800 INFO: Lock owner: pgsql16_node001; I am pgsql16_node001
2024-07-17 17:00:56 +0800 INFO: updated leader lock during switchover: demote
2024-07-17 17:01:06 +0800 INFO: Lock owner: pgsql16_node001; I am pgsql16_node001
2024-07-17 17:01:06 +0800 INFO: updated leader lock during switchover: demote
2024-07-17 17:01:16 +0800 INFO: Lock owner: pgsql16_node001; I am pgsql16_node001
2024-07-17 17:01:16 +0800 INFO: updated leader lock during switchover: demote
2024-07-17 17:01:26 +0800 INFO: Lock owner: pgsql16_node001; I am pgsql16_node001
2024-07-17 17:01:26 +0800 INFO: updated leader lock during switchover: demote
2024-07-17 17:01:36 +0800 INFO: Lock owner: pgsql16_node001; I am pgsql16_node001
2024-07-17 17:01:36 +0800 INFO: updated leader lock during switchover: demote
2024-07-17 17:01:46 +0800 INFO: Lock owner: pgsql16_node001; I am pgsql16_node001
2024-07-17 17:01:46 +0800 INFO: updated leader lock during switchover: demote
2024-07-17 17:01:55 +0800 WARNING: Exception happened during processing of request from *******:58904
2024-07-17 17:01:55 +0800 WARNING: Traceback (most recent call last):
2024-07-17 17:01:56 +0800 INFO: Lock owner: pgsql16_node001; I am pgsql16_node001
2024-07-17 17:01:56 +0800 INFO: updated leader lock during switchover: demote
2024-07-17 17:02:06 +0800 INFO: Lock owner: pgsql16_node001; I am pgsql16_node001
2024-07-17 17:02:06 +0800 INFO: updated leader lock during switchover: demote
2024-07-17 17:02:13 +0800 INFO: received failover request with leader=None candidate=pgsql16_node002 scheduled_at=None
2024-07-17 17:02:13 +0800 INFO: Got response from pgsql16_node002 http://*****:8008/patroni: {"state": "running", "postmaster_start_time": "2024-07-17 17:01:16.487436+08:00", "role": "replica", "server_version": 160002, "xlog": {"received_location": 8417599029248, "replayed_location": 8417605990328, "replayed_timestamp": "2024-07-17 16:59:36.614582+08:00", "paused": false}, "timeline": 22, "dcs_last_seen": 1721206927, "tags": {"failover_priority": 2, "version": "16.2", "spec": "8C.32G.500G"}, "database_system_identifier": "7340474031893890113", "patroni": {"version": "3.2.2", "scope": "cvd", "name": "pgsql16_node002"}}
2024-07-17 17:02:13 +0800 INFO: Lock owner: pgsql16_node001; I am pgsql16_node001
2024-07-17 17:02:13 +0800 INFO: updated leader lock during switchover: demote
2024-07-17 17:02:23 +0800 INFO: Lock owner: pgsql16_node001; I am pgsql16_node001
2024-07-17 17:02:23 +0800 INFO: updated leader lock during switchover: demote
2024-07-17 17:02:33 +0800 INFO: Lock owner: pgsql16_node001; I am pgsql16_node001
2024-07-17 17:02:33 +0800 INFO: updated leader lock during switchover: demote
2024-07-17 17:02:43 +0800 INFO: Lock owner: pgsql16_node001; I am pgsql16_node001
2024-07-17 17:02:43 +0800 INFO: updated leader lock during switchover: demote
2024-07-17 17:02:53 +0800 INFO: Lock owner: pgsql16_node001; I am pgsql16_node001
2024-07-17 17:02:53 +0800 INFO: updated leader lock during switchover: demote
2024-07-17 17:03:03 +0800 INFO: Lock owner: pgsql16_node001; I am pgsql16_node001
2024-07-17 17:03:03 +0800 INFO: updated leader lock during switchover: demote
2024-07-17 17:03:28 +0800 INFO: Selected new etcd server http://*******:2379
2024-07-17 17:03:28 +0800 INFO: Trying to authenticate on Etcd...
2024-07-17 17:03:28 +0800 INFO: No PostgreSQL configuration items changed, nothing to reload.
2024-07-17 17:03:28 +0800 WARNING: Postgresql is not running.
2024-07-17 17:03:28 +0800 INFO: Lock owner: pgsql16_node002; I am pgsql16_node001
2024-07-17 17:03:28 +0800 INFO: pg_controldata:
2024-07-17 17:03:28 +0800 INFO: Lock owner: pgsql16_node002; I am pgsql16_node001
2024-07-17 17:03:28 +0800 INFO: Local timeline=22 lsn=7A7/E06A37B8
2024-07-17 17:03:28 +0800 INFO: primary_timeline=23
2024-07-17 17:03:28 +0800 INFO: primary: history=19     5D8/2171F7C0    no recovery target specified
2024-07-17 17:03:28 +0800 INFO: running pg_rewind from pgsql16_node002
2024-07-17 17:03:28 +0800 INFO: running pg_rewind from dbname=postgres user=rewind_user host=***** port=5432 target_session_attrs=read-write
2024-07-17 17:03:36 +0800 INFO: Lock owner: pgsql16_node002; I am pgsql16_node001
2024-07-17 17:03:36 +0800 INFO: running pg_rewind from pgsql16_node002 in progress
2024-07-17 17:03:41 +0800 INFO: pg_rewind exit code=0
2024-07-17 17:03:41 +0800 INFO:  stdout=
2024-07-17 17:03:41 +0800 INFO:  stderr=pg_rewind: servers diverged at WAL location 7A7/E06A37B8 on timeline 22
2024-07-17 17:03:41 +0800 WARNING: Postgresql is not running.
2024-07-17 17:03:41 +0800 INFO: Lock owner: pgsql16_node002; I am pgsql16_node001
2024-07-17 17:03:41 +0800 INFO: pg_controldata:
2024-07-17 17:03:41 +0800 INFO: Lock owner: pgsql16_node002; I am pgsql16_node001
2024-07-17 17:03:41 +0800 INFO: starting as a secondary
2024-07-17 17:03:41 +0800 WARNING: Removing unexpected parameter=promote_trigger_file value=promote.signal from the config
2024-07-17 17:03:41 +0800 INFO: postmaster pid=104598
2024-07-17 17:03:42 +0800 INFO: establishing a new patroni heartbeat connection to postgres
2024-07-17 17:03:42 +0800 INFO: establishing a new patroni restapi connection to postgres

PostgreSQL log files
not info message

Have you tried to use GitHub issue search?

[X] Yes

Anything else we need to know?
No response

Switchover failed, details: 503, Switchover status unknown

Switchover status unknown means that switchover didn't finish within 2*loop_wait seconds.
As you can see, leader is in stopping state, and the standby will not be promoted until the leader is shut down cleanly.
You just have to wait, and eventually it will finish.
Also, you may spend your time trying to figure out why shut down of the primary is taking so long.
Please post further questions on Slack.

the primary state is stopping, and the replica node is not promoted to primary.

Meh, how is it different from what I said?

And this failure time is far greater than 2*loop_wait

After 2*loop_wait patronictl (and REST API) are giving up on waiting and showing the above error.

3min+. Finally, it is OK to force restart the master server

That is, instead of figuring out why the shut down takes so long you just shoot the primary. Well done... (NO!)

repo: patroni/patroni


text:
Create 0000-01-02-patryk0703.md

I am currently learning

I am still learning


text:
unable to install starterkit

I'm not able to install pattern lab 2 with the starterkit-mustache-demo.
Installation of the starterkit-mustache-demo fails with a fatal error:
PHP Fatal error:  Uncaught exception 'Alchemy\Zippy\Exception\RuntimeException' with message 'Unable to create the inflator' in.
According to the guys by the Zippy extenstion, this issue is fixed since 2014.
https://github.com/alchemy-fr/Zippy/issues/69
Any ideas what I'm doing wrong?
I try to get it work on a windows machine.
PHP Version: 5.5.35
Composer: 1.1.2

@dominixdesign -
First off, thanks for trying it out. Second, I appreciate you trying to do some research on this. I haven't run into this problem but if I could:

get a more detailed error and
get you to agree to be a guinea pig to test

I'd appreciate it.
To get the more detailed error try:
composer create-project pattern-lab/edition-mustache-standard patternlab2-example -v

If you can paste it to gist or here that would be awesome. That will give a stack track that I can work with a little better.
To be a guinea pig and test changes I make without my having to push full releases you can do the following:
composer create-project pattern-lab/edition-mustache-standard:dev-dev patternlab2-test

Then when I push changes you'll be able to do a composer update pattern-lab/core and get my latest commits.
I'll try to look at this problem in the meantime. Thanks.

Ah... I think I might know the problem. Zippy is set to a really old version in Core's composer.json. I'm going to muck with that. Sorry.

This error is now catched as of v2.7.0 of core. I don't have a great fix but at least the error explains the workaround. Please run composer update to get the latest version of PL. Full list of fixes.

authors: dmolsen dominixdesign

repo: pattern-lab/patternlab-php

license: mit


text:
fix: pfe-jump-links offset & updates to demo file

Add fake navbar to demo page
Tidy demo CSS
shorten length of paragraphs between panel headings
Add offset variable in the jump links nav

Demo page

@starryeyez024 Can you take a look at why the CI is failing?

Lazarra good to merge

authors: Djfaucette castastrophe starryeyez024

repo: patternfly/patternfly-elements


text:
Google Gemini LLM generation config problem

The following line in Google Gemini LLM seems to be wrong.
If the temperature is defined, the whole generation_config object gets replaced thus ignoring any pre defined parameters there!
https://github.com/patterns-ai-core/langchainrb/blob/0efc39269e5c2c123886fa34e10b28c682ada948/lib/langchain/llm/google_gemini.rb#L45

@mazenkhalil Do you have a suggested fix?
I think we should set the possible values directly, something like the following:
parameters[:generation_config] ||= {}
parameters[:generation_config].merge({temperature: parameters.delete(:temperature)}) if parameters[:temperature]
parameters[:generation_config].merge({top_k: parameters.delete(:top_k)}) if parameters[:top_k]
...

authors: andreibondarev mazenkhalil

repo: patterns-ai-core/langchainrb


text:
Feature Request: Support git worktrees

I think git worktrees offer a great workflow for a tool like aider. Worktrees reduce the friction that naturally stems from having an external tool commit automatically, resulting in a smoother experience.
In case you're not familiar: man git-worktree.
A sample workflow would look something like this:
mkdir mydir && cd mydir

# create a dummy repo
mkdir myrepo && cd myrepo && touch README.md && git init && git add -A && git commit -m "Initial commit"

# aider works here
aider -v

# create a worktree to fix some bug. CD into it.
mkdir ../worktrees
git worktree add ../worktrees/bugfix
cd ../worktrees/bugfix

# use aider to help fix the bug (This will result in the error shown below)
aider -v

Traceback (most recent call last):
  File "/home/nbe/.local/bin/aider", line 8, in <module>
    sys.exit(main())
  File "/home/nbe/projects/playground/python-exp/venv/lib/python3.10/site-packages/aider/main.py", line 216, in main
    coder = Coder(
  File "/home/nbe/projects/playground/python-exp/venv/lib/python3.10/site-packages/aider/coder.py", line 85, in __init__
    self.set_repo(fnames)
  File "/home/nbe/projects/playground/python-exp/venv/lib/python3.10/site-packages/aider/coder.py", line 149, in set_repo
    repo = git.Repo(repo_paths.pop(), odbt=git.GitDB)
  File "/home/nbe/projects/playground/python-exp/venv/lib/python3.10/site-packages/git/repo/base.py", line 265, in __init__
    raise InvalidGitRepositoryError(epath)
git.exc.InvalidGitRepositoryError: /home/nbe/mydir/myrepo/.git/worktrees/bugfix

Thanks for reporting this issue. I just pushed a fix. Let me know if it works for you.

Works great. Thank you!

authors: paul-gauthier thenbe

repo: paul-gauthier/aider


text:
Widget not fully showing the numbers and change to glucose levels

I noticed that when I have it show blood glucose in mmol/L the decimal numbers do not show correctly. Also change to the blood glucose is shown as -1 when actual change was -0.60. This issue is most likely only with european way of using mmol/L vs mg/dL, but could it be possible to show actual changes in decimals as well, as it feels like a bug or oversight.

@Ryptahi Do you mean the "," because that comes from your local Windows settings. The fact that it doesn't fit is a real issue that I will look at. But I have no test sites that use mmol/L so it will be difficult to reproduce.

@Ryptahi please try this
CareLink3.8.2.0x64.zip

@Ryptahi please try this CareLink3.8.2.0x64.zip

Thank you, now it is absolutely perfect!

Thanks I will update and release a new version today.


text:
Default values apply first, then the props, resulting in a flicker on page load

Hi,
I've noticed that on page load, the default values of 2 columns and 0 gutter is applied, before the values I've specified in the props (:cols = "{default: 1, 9000: 2, 1024: 1}", gutter="16"). I set the default to 1 and the next upper bound to 9000, to try and force the default to go to 1, but that didn't work.
You can see it on my site here: Sean Lloyd
In a smaller (mobile) view, it briefly loads the two columns before pinging back to one:

On the larger (desktop) view, it's already set to 2 columns fortunately, but the gutter bounces to 16 once the page has loaded:

Is there anything I can do about this? On slower connections, it seems to take longer to reposition the elements, so I'm guessing masonry waits for DOMContentLoaded or something similar before running - can we run it sooner?
Something to note is that the elements are not loaded with the page, and more elements are added with lazy loading as the user scrolls - not sure if that's what is causing the issue!

Almost immediately solved my own problem!
Moving my loading logic into "mounted" rather than "created" changed the order of the load - my guess is that the masonry layout is applied once the component is mounted, since it can rely on the content being added.

repo: paulcollett/vue-masonry-css


text:
Added a condition for the protoc artifact so builds on M1 macs can work

This fix didn't used to be necessary. I'm not sure what broke but this fixes it.
You need to add protoc_platform=osx-x86_64 to your flutter project's build.gradle file on M1 macs for this fix to do anything.

@Rexios80 where does this property go in the build.gradle file ?


text:
Separate header name for request and response

Ref: pauldijou/jwt-scala#61

Thx for the work. Released in 0.14.0

authors: Isammoc pauldijou

repo: pauldijou/jwt-scala


text:
AsyncHttpClient conflicts with other Netty based libraries

First of all, thanks for this library is very useful.
I've tried to use scala-influxdb-client and expose services with Finagle (an RPC system form Twitter) which also uses Netty but a different version of Netty and a dependency versions conflict arises at run time.
The error is:
java.lang.NoSuchMethodError: io.netty.util.internal.PlatformDependent.newAtomicIntegerFieldUpdater(Ljava/lang/Class;Ljava/lang/String;)Ljava/util/concurrent/atomic/AtomicIntegerFieldUpdater;
For solving this error you can include async-http-client as an explicit dependency excluding netty with something like:
libraryDependencies += "com.paulgoldbaum" %% "scala-influxdb-client" % "0.5.2"
libraryDependencies += "org.asynchttpclient" % "async-http-client" % "2.0.32" exclude("org.jboss.netty","netty") exclude("io.netty","netty")
Please pay attention to the versions you use when including aync-http-client explicitly, obviously this will change with time.
Possible further solutions to this issue may include:

Shade async-http-client like Play here -> https://github.com/playframework/play-ws#shading
Try to coordinate with async-http-client and the Netty creators better paths for upgrading
Do nothing and let the versions get stable with time

@csaltos I had the same problem with grpc-java. Using newer version of asynchttpclient fixes the problem. I will make a pull request with asynchttpclient:2.1.0-alpha21 with works for me.

Fixed this by updating to the current release, which is the same in both projects. I'm not sure of the best long-term solution because shading seems like overkill but it might be the only way to avoid these issues. Will think about it.
Thanks for the input!

authors: csaltos paulgoldbaum rpt

repo: paulgoldbaum/scala-influxdb-client


text:
Add Get Order By Id Endpoint

https://github.com/ariesprayoga/swagger-java-sample-app/blob/master/src/main/java/com/wordnik/swagger/sample/resource/PetStoreResource.java

closed by #43

repo: pauljamescleary/scala-pet-store


text:
Cannot assign to 'DST_LABEL' because it is a read-only property.ts(2540)

hi! i got a error when to change DST_LABEL.
import * as bls from 'noble-bls12-381';

// Default domain (DST) is `BLS_SIG_BLS12381G2_XMD:SHA-256_SSWU_RO_NUL_`, use `bls.DST` to change it.
bls.DST_LABEL = 'BLS_SIG_BLS12381G2_XMD:SHA-256_SSWU_RO_AUG_';

/** Cannot assign to 'DST_LABEL' because it is a read-only property.ts(2540) */

is any other way to change it?

Use utils.setDSTLabel(), aa9ca2e

great!

authors: HFJingchuang gwang74 paulmillr


text:
Read lockstyle from config if no option is chosen.

Title pretty much says it: when invoking betterlockscreen -l the style defined in betterlockscreenrc will be selected instead of the default "resized" one.
I've been running this on my system and I do prefer this behavior and was wondering if it could have been of general interest.
This doesn't really change anything for users who don't have lockstyle in their config: since it won't be found in there, not specifying the style will fallback to the previous behavior.

Will be fixed with Multilockscreen-Merge :)

authors: SebTM dpdani

repo: pavanjadhaw/betterlockscreen


text:
Make WebIRC use the latest socket.io

package.json now restricts the version of socket.io to pre-1.0. Update to use the new API.

No longer using socket.io :)

repo: pavben/WebIRC


text:
TypeError: route_params_decorator_1.assignMetadata is not a function

/Users/sitapati/workspace/SMA/endpoint-2.0/endpoint/node_modules/@nestjs/microservices/utils/param.utils.js:14
        Reflect.defineMetadata(constants_1.PARAM_ARGS_METADATA, route_params_decorator_1.assignMetadata(args, paramtype, index, undefined, ...pipes), target.constructor, key);
                                                                                ^
TypeError: route_params_decorator_1.assignMetadata is not a function

When I decorate the complete parameter with Ctx(), I get this error. Without it, complete is undefined at runtime...
I've double-checked all the versions, and this is using all the same dep versions in your package.json.

Got it working with these versions:
    "@nestjs/common": "^6.10.12",
    "@nestjs/core": "^6.10.12",
    "@nestjs/microservices": "^6.10.12",
    "@nestjs/platform-express": "^6.10.12",

repo: pay-k/nestjs-zeebe


text:
[Android] Dupicate VERSION_NAME

When i install your library in my project and run with Android, i found error be like this image.
I tried to fix it by going into the directory and deleting this line but it doesn't seem to work when I run the npx react-native run-android command again.

I use
react-native: 0.62.3
payjp-react-native: 0.6.3

Please tell me how can i fix this, thank you.

I run example and it works. Could you try to run example?

@Ppang0405 i found a resolve for my problem.
Open .../node_modules/payjp-react-native/android/build.gradle, find and delete line in buildConfig
buildConfigField "String", "VERSION_NAME", "\"$pluginVersion\""

repo: payjp/payjp-react-native-plugin


text:
postgres-db: localized fields inside of tabs/groups that have name with camelCase

Link to reproduction
https://github.com/r1tsuu/payload-tabs-localized-fields-inside-issue
Describe the Bug
screen-capture (1).webm
Hhere is a config from reproduction:
const CollectionTest: CollectionConfig = {
  slug: 'test',
  fields: [
    {
      type: 'tabs',
      tabs: [
        {
          name: 'tabName', // In camelCase
          fields: [
            {
              type: 'array',
              name: 'array',
              fields: [
                {
                  type: 'text',
                  name: 'text',
                  localized: true,
                },
              ],
            },
          ],
        },
        {
          name: 'tabnamenocamelcase', // Without camel case

          fields: [
            {
              type: 'array',
              name: 'array',
              fields: [
                {
                  type: 'text',
                  name: 'text',
                  localized: true,
                },
              ],
            },
          ],
        },
      ],
    },
  ],
}

Created tables:
test
test_tab_name_array
test_tab_name_array_locales
test_tabnamenocamelcase_array
test_tabnamenocamelcase_array_locales
Now if we try to save localized text inside of tabName_array, it will be actually saved to the database, but not paginated when queried.

I debugged payload code from main branch, here's what i've found
traverseField.ts 52 - here we are changing our path for the next traverse with tab name, okay, it should be equal tabName
traverseField.ts 81 - here we are resolving arrayTableName by path and currentTableName that currently is empty. So should be "tabName_array"
traverseField.ts 83 - here we are checking if localized array table exists, tabName_array_localized, but it doesn't, only tab_name_array_localized.
The problem also appears with groups on top level instead of tabs and blocks/select etc on bottom level instead of arrays.
To Reproduce
Clone the repo from reproduction and use Tests collection
Payload Version
Reproduction 3.0-alpha, but bug exists with 2.0 also.
Adapters and Plugins
db-postgres

Closing in favor of https://github.com/payloadcms/payload/issues/7109 (the same issue)

repo: payloadcms/payload


text:
Can’t use payload in admin.condition function of field, can’t use async/await, can’t create options for select field dynamically

Link to reproduction
No response
Payload Version
beta
Node Version
20.15.1
Next.js Version
15.0.0-rc.0
Describe the Bug
We are trying to either conditionally render the options of a select field or render the whole field conditionally based on siblingData  from a relationship field. Since the siblingData only show a number for the relationship field, we would need to fetch the related collection entry to get its “slug” to decide if the field should be rendered.
The options seems to be static, so we tried to create multiple fields for each set of options and render them conditionally. Sadly the information given within the condition function arguments is not sufficient. It also appears that the condition field won’t take an async function.
Another solution would be if payload would allow the depths of the given data and sibling data to be configured somehow.
Reproduction Steps

export const maasRouteField: SelectField = {
  name: 'route',
  type: 'select',
  options: ['/', '/products/'],
  admin: {
    position: 'sidebar',
    condition: async (_data, siblingData) => {
      console.log('siblingData:', siblingData, payload)

      return await payload.findByID({
        collection: 'tenants',
        id: siblingData?.tenant,
      })
    },
  },
}

Adapters and Plugins
No response

Hey @robinscholz — right now, this is deliberate, but I think we could potentially change this in the future. The thing is that conditional logic runs very frequently and should be heavily optimized so that your UI doesn't slow down. Generally, querying on data in a condition will add latency to the function and that would slow down the reactivity of the conditions themselves.
Instead, what we normally do here is add a virtual field to the field schema that you need to run your condition against, and in that virtual field, populate the slug or whatever field you need from your related item into that virtual field - then run your condition against that field instead. In this case, your virtual field could have a custom UI component that fetches the related item one time and stores the related item's field in its field in the form state. That would be way more performant.
Does that make sense? I will convert this to a Feature Request so that we can evaluate others' interest in supporting the Local API inside conditions, but generally, you probably don't want to do this. You want to find a pattern to fetch that related data one time, and then use it accordingly rather than fetching it every time the condition runs (which is a lot).

authors: jmikrut robinscholz


text:
Feature request: Comparision to sanity

Hi, it'd be very helpful to also have a comparision with sanity, since they are said to be similar.

We have the full Sanity comparison posted here: https://payloadcms.com/compare/sanity
You can locate others @ payloadcms.com/compare.

repo: payloadcms/website


text:
feat: create public api

This PR should create our public API and add the dependency on retrofit for HTTP requests.

@rosariopfernandes do we expect to allow the modification of configuration after creating an instance of Client?

@edsonmichaque No, a Client is not supposed to be modified. What are you suggesting?

@rosariopfernandes, I think the Client interface doesn't need getters and setter for configuration properties. We can have only receive, send, query and revert.

@edsonmichaque the getters are for our own use internally and the Client class has no setters. The setters are present in the Builder.

@rosariopfernandes, my bad, about the setters
But Client is the user facing class, so anyone call call the getters

@edsonmichaque Yes. Thought it might useful in the future for developers who may want to extend our SDK in any kind of way.

@rosariopfernandes I agree, when we need them we will add them

@edsonmichaque I've updated the PR accordingly. PTAL

@rosariopfernandes, maybe we dont need to declare an Environment member in client, but we can still receive in class Builder

authors: edsonmichaque rosariopfernandes

repo: paymentsds/mpesa-java-sdk


text:
Card Client Docs

Summary of changes

Add Docs for iOS Card Client Integration

Checklist
~- [ ] Added a changelog entry~
Authors

@minhthenguyen
@sshropshire

See iOS-SDK #29

Sorry ignore all these comments, I moved them to the correct PR in the iOS repo 🤦

authors: sarahkoop sshropshire

repo: paypal/Android-SDK


text:
Showing Error page with "Invalid Scope"

I was unable to find a reason why this error comes.

Please help me to solve this.
I have completely followed the document without any mistake.

Hey @gkpatel461 please ensure that from your REST App underneath "Login With PayPal" and under the "Personal profile" section that both "Full name" and "Email" are checked. If they are checked both checked then please provide your client id so that I can look into this issue further.

Thank you for your reply. But I am unable to get the "REST App underneath" for the Login with Paypal option.
I just want to use the Paypal Checkout option as a payment gateway for the eCommerce Android App. No need for login with PayPal.
Client ID: AXrxro3r5RiaVIK6rGZHxwMj_arNmQWqABQP7DhulP5NEKwc87MjYnH44MJHuzdGFP1xhle4YkUALYbM
Also, I have tried this demo app by adding a return URL per the document in the dashboard, but I am still getting the same error.
Please help me to solve this.

@gkpatel461 it looks like the Client ID is missing scopes that are granted after following the "Know Before You Code" section of our official developer documentation. Enabling Login with PayPal is necessary for the SDK to function as buyers will be redirected to PayPal to first login before they can see their account details.

Thank you for your reply. Its worked.
Is there an option for the user to pay using a card only without login into PayPal?

@gkpatel461 happy to hear that worked. We currently only support authenticated PayPal flows, however once the buyer has logged in they should remain logged in for future purchases.
I'll go ahead and close this issue out.

repo: paypal/android-checkout-sdk


text:
[Proposal] Advanced style overrides/theming for reusable components

Problem
Glamorous offers theming, and while this is certainly useful I think there's still a missing solution for style overrides in complex reusable components.
As an example, let's consider a <Datepicker> component (like react-datepicker). We'd like to expose a theme prop where users can customize the theme colors. This is easy, we can pass the user theme to <ThemeProvider> and then use these values to style the internals of our reusable component like this:
const Day = glamorous.div((props, theme) => ({
  borderColor: theme.mainColor
}))

This works well enough for the simple case, but what if someone wants to change a style we haven’t initially anticipated? For example, adding a border radius, changing font-face/weight/size, or removing white space across all elements for a more condensed view. Our component could quickly grow into the following:
const Day = glamorous.div((props, theme) => ({
  backgroundColor: theme.themeColorDark,
  padding: theme.dayPadding || '4px',
  borderRadius: theme.dayRadius || '2px',
  font: props => theme.dayFont,
  // etc...
}))

You might even consider spreading in a style overrides object, but you‘d also need to spread into any pseudo-classes since spreads don’t merge objects recursively:
const Day = glamorous.div((props, theme) => ({
  padding: '4px',
  ':hover': {
    backgroundColor: theme.themeColorDark
    ...theme.dayHover
  },
  ':first-child': {
    padding: '2px',
    ...theme.dayFirstChild
  },
  ...theme.day
}));

Maintaining solutions like this can be quite tedious as a developer, and we can likely offload some of this to the library.
Proposed Solution
Let's extend glamorous's theming layer by allowing optional theme identifiers on glamorous components, and internally glamorous will do the job of merging overrides with the base component styles.
Revisiting our date picker example, we can use this new strategy:
const Day = glamorous.div('DatePickerDay', {
  borderColor: '#ccc'
})

Here we’ve added an argument that is an optional theme identifier for the element (alternatively this could be a themeName prop passed to <Day>). Users of my datepicker component can target this identifier and others with a style override object:
const datePickerStyles = {
  DatePickerDay: (props, theme) => ({
    borderColor: props => props.selected ? '#00bbff' : '#bbb'
  }),
  DatePickerHeader: {
    padding: '4px',
  },
  // etc.
};

<DateRangePicker styles={datePickerStyles} />

Glamorous would do the heavy lifting of merging the overrides into the Day components styles, using a recursive merge so that pseudo-classes work properly. Note that we maintain the ability to use dynamic styles based on props, although we may want a mechanism to select which props become a part of the public API.
Giving all components theme identifiers also introduces other conveniences, for example we could even reference them inside a descendant combinator from a parent component:
// Parent.js
const Parent = glamorous.div('Parent', {
  ':hover $Child': {
    opacity: 1;
  }
});

// Child.js
const Child = glamorous.div('div', 'Child', {
  opacity: 0;
});

(This is an alternative API to current WIP in #136.)
When a Child renders, any rules found in a parent component that contain $Child will also be injected (the $ prefix denotes a theme identifier, syntax inspired by jss-nested). This is obviously separate functionality from the main API being proposed here and not required, just figured I'd mention it since #136 is being worked on.
Why?
This is one of the last pieces of the puzzle for me in CSS-in-JS. We are big users of various CSS-in-JS libraries at Uber, and this is easily the biggest pain point I've seen developers run into when working with our reusable component libraries. It also seems like an unsolved problem in the wider community [1, 2, 3, 4]. Finding a solution would be a major step forward for using css-in-js in reusable components libraries, as developers will have complete flexibility over re-styling for their use case.

cc @taion given your previous post. curious to hear your thoughts on an API like this.

Hi! Thanks for the issue. I haven't had time to give it a thorough look yet, but at first glance I think this may solve your issue: https://rc.glamorous.rocks/examples#Accept-style-overrides

Oh nice! I searched far and wide but didn't see that example anywhere (guessing rc.glamorous.rocks isn't fully released yet?).
Anyway, that is definitely a viable solution. It is more verbose than the proposed API, but it ultimately provides the same functionality. IMO it'd be great to see this functionality/helper built into glamorous core or released as a glamorous plugin rather than relying on users to define their own helper, but I suppose the helper is only a few lines of code and if featured prominently in the glamorous docs (looks like it will be), then it should still be straightforward for users.
Up to you–feel free to close this if you don't think there's much to be gained here beyond the example you shared.

My understand of glamorous is quite limited, so take this with a grain of salt, but:
The solution in the OP looks more like what I was picturing than the solution at https://rc.glamorous.rocks/examples#Accept-style-overrides.
The problem I was thinking of is that something like a <Button> might be used in multiple contexts that need to provide contextual styles. In the "style override" example, <Tagline> is closely coupled to <UserCard>, and seems like it's not "generic" in that sense, though that might just be a limitation of that example – though that said, using a theme provider for everything you might want to override feels like it'd be clunky.

Yeah, I think that the reusable/generic argument is solved by glamorous's normal use cases with the css prop, and composible classNames. You would only really ever do the style overrides thing for a situation where you want to expose overriding capabilities to a group of components (like an Autocomplete, or Tabs or something). Does that make sense?
So normally you'd do something like:
const Button = glamorous.button({/* basic styles */}, (props) => ({/* dynamic styles you think of ahead of time that are generic */})

<Button css={{ /* styles that are specific to your use-case */ }} />

These all merge together in a really nice and predictable way :)
I hope that helps.

Oh, and with regards to baking the accept-style-overrides idea into glamorous, I don't think that's something I'm willing to do, but I do see value in having a small library expose something like that. Seems like a pretty useful pattern.

Yeah, I think that the reusable/generic argument is solved by glamorous's normal use cases with the css prop, and composible classNames. You would only really ever do the style overrides thing for a situation where you want to expose overriding capabilities to a group of components (like an Autocomplete, or Tabs or something). Does that make sense?

Yup, this proposal was more focused on components like autocomplete, modals, tabs, pagination, datepickers etc. (let's call these "complex" components) for which the css prop doesn't really work since there are numerous elements internally.
Imagine I wanted to build something like Ant's component library, which contains dozens of complex components, and one of the project requirements is to allow developers to have full control over re-styling internals–normally a trivial task with global css. Surprisingly, most css-in-js libraries simply don't provide a great story around this use case currently (I can give other examples), even though contextual style overrides for complex reusable components are an inevitability in large applications.
While I think this is a more important use case than many libraries are accounting for, I'm excited to see that there is a solution with Glamorous. Prominently displaying the "Accept style overrides" example in the docs looks like a good solution for now, and if there is more demand down the road then a helper package or core feature could be re-evaluated.

Actually, I think there's a much better way to design your API for these components that not only makes them more flexible from a styled standpoint, but from pretty much every angle. I'm working on an autocomplete component that uses this design pattern and will definitely share when I'm done. Spoiler alert, it looks similar to this:

That would be trivial to style all components also to use to build a more traditional (options based) API on top of if needed.

I've used the paradigm before where the reusable component internals are also exported (assuming that's what you're going for), and while it certainly allows for flexibility, in my opinion it makes the public interface too complicated. 99% of the time I'm using an autocomplete, a single-component API  is sufficient and preferable (like react-select). Additionally, it's initially unclear whether child order matters–can I put a AutoComplete.Error before AutoComplete.Menu? This might also be really complicated for a datepicker–imagine rendering the weeks and days with a selected time range.
Certainly a good solution for some cases, but not sure it obviates the need for a styling-specific API.

Understood. You could definitely take the API described above and create a wrapper to expose a react-select like (options based) API in addition to the component pieces API (which I think is pretty great). But at that point, you're left with the same problem.
I agree that the solution in my example is probably the way to do this for now. I'm not super excited about baking in more complexity to handle this use case, but I would be happy to get this put together in a small library or something so using it takes less work (thus encouraging the pattern). Would you be willing to build that?

Yup, I'm up for that! Let me experiment with the helper function in one of our projects, and once it's been battle-tested I'll put together a small lib in a separate repo and solicit your feedback before publishing it. Thanks for your help and consideration on this 👍

Ah! I remember having this conversation with @threepointone on Twitter now. The context-based API is pretty neat, especially with syntactic sugar around it. It mostly works, which is neat. The one limitation was that (glancing through the docs in a cursory way) it doesn't really allow using more complex relational selectors, e.g. something like:
.form {
  & .btn + .btn {
    /* something */
  }

  & .input + .btn {
    /* something else */
  }
}

It's not a pattern we used a lot, but we had a few cases where we did a bit of that. Ended up using global hook classes with CSS Modules to get this working (& :global(.__button-hook) + :global(.__button-hook)), which was good enough.

FWIW, the appropriateness of that more complex API above depends a bit on the specific example. If e.g. your application uses autocompletes all over the place, it's probably a bit verbose to do that everywhere, but e.g. listing out <Tab> elements under a higher-level <Tabs> feels pretty natural to me. Does something like a :first-child selector work well in that context? Seems like "sort of"?

it doesn't really allow using more complex relational selectors, e.g. something like...

glamor (and hence glamorous) definitely supports selectors like that 👍

If e.g. your application uses autocompletes all over the place, it's probably a bit verbose to do that everywhere

The nice part of that kind of API is you could easily wrap it in another component and use that options-based API everywhere (while still allowing for the more powerful API).

Oh, and:

Does something like a :first-child selector work well in that context? Seems like "sort of"?

Definitely. You could try it out in https://help.glamorous.rocks and send along a link if you have any trouble.

It's not a question of whether relational selectors are supported. It's a question of which relational selectors are supported. I've seen https://github.com/paypal/glamorous/#example-style-objects, which shows something similar to CSS modules across modularized classes – i.e.:
/* works */
.foo {
  & div + div {
    color: red;
  }
}

/* doesn't work */
.foo {
  & .btn + .btn {
    color: red;
  }
}

Ah, but that actually totally does work. Right now you'd have to manually add classes (which is trivial), but eventually we will have support for referring components in the selector directly.
But in either case, doing something like that is quite simple with glamorous

Sure, so manually adding classes is about the same as what you get with CSS modules – global hook classes and all. It's okay, but ideally you'd want something within the system, e.g. explicit hooks (like the :external support that CSS modules will get, eventually).
That styled-components bit is really cool, though, and it's almost exactly what I was thinking.

If you'd like, glamorous's equivalent to that feature is ready for review: #183 :smile:

Closing in favor of: https://github.com/kentcdodds/glamorous-website/issues/222
Thanks for the discussion everyone!

authors: kentcdodds schnerd taion

repo: paypal/glamorous


text:
Used valid url for refund details

All Submissions:
Updated the refund rul as wrong url was used in the refund details api earlier.

[ ] Have you followed the guidelines in our Contributing document?
[ ] Have you read and signed the automated Contributor's License Agreement?
[ ] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

New Feature Submissions:

[ ] Does your submission pass tests?
[ ] Have you lint your code locally prior to submission?

Changes to Core Features:

[ ] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your core changes, as applicable?
[ ] Have you successfully ran tests with your changes locally?

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant navin-math

repo: paypay/paypayopa-sdk-python


text:
🛑 Departamento is down

In 4d75f80, Departamento (http://cca.unb.br/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Departamento is back up in 944077b after 22 minutes.


text:
ProgressIndicator.showSimple(true); Not Working

Cordova 5.3.3
IONIC 1.6.4
It is not working please help

Cordova v5.4.1
pure AngularJS v1.5.0
same problem with ngCordova
PS: please notice that plugin link for installation doesn't work too

I also can't get this working with ngCordova.
I was trying it on the browser,  not sure what that would even do.
I get an error
angular.js:13550 ReferenceError: ProgressIndicator is not defined
I get the same look on my screen on the Android phone (not sure if I can debug that any).

repo: pbernasconi/cordova-progressIndicator


text:
Emojify

Let's 🤝 be 🐝 honest. 😇 Normal 👩🦯 text 📩 is boring! 😪 Things 🕑 are much 😩 more 🙅 interesting 🤔 (and funny) 😃😅😂😃❓ with emojis! 💢
This module adds the !emojify command, which can be used to add emojis to the most recent message. You can call !emojify with a nick to get that user's most recent message. You can also use the -p flag to write your own phrase to emojify!

Codecov Report
Base: 52.34% // Head: 53.30% // Increases project coverage by +0.95% :tada:

Coverage data is based on head (4bcb71c) compared to base (e31b43a).
Patch coverage: 62.33% of modified lines in pull request are covered.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@               Coverage Diff                @@
##           bobbit-0.2.x      #72      +/-   ##
================================================
+ Coverage         52.34%   53.30%   +0.95%
================================================
  Files                19       21       +2
  Lines               726      803      +77
================================================
+ Hits                380      428      +48
- Misses              346      375      +29

Impacted Files
Coverage Δ

src/bobbit/modules/emojify.py
51.72% <51.72%> (ø)

tests/test_module_emojify.py
94.73% <94.73%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

This is amazing.  LGTM. TYFYS

authors: codecov-commenter evstar3 pbui

repo: pbui/bobbit


text:
Special characters of Contact no. not shown in Table. (Agent Panel)

Description of  the bug
If we write contact number +1287678987654. then + is not shown in Table.
To Reproduce
Steps to reproduce the behavior:

Go to 'https://www.pulseptt.com/agent.html'
Login with valid credential:- 1. User name: john 2. Password: 12345678
Navigate to Company management.
Check on View Company List.

Expected behavior
+ sign should show in Table also.
Screenshots

Desktop (please complete the following information):

OS: Windows 10
Browser :Version 100.0.4896.60 (Official Build) (64-bit)
Version [0.1.1]

will work now if you now modify or create new contacts. Previously it was not properly updated to the database.

Special character should be optional. Now , if we entered Contact number 9876567898 then it is showing error but after entering +9876567898 it is accepted.


text:
not working with PDF version 1.3

I am trying to extract text from few pdf docs. pdfminer.six is able to parse text from pdf v1.4-1.7 but it is not working for pdf v1.3. Most of the time it is returning text from starting from the 3rd page instead of page 1.

Hi @NitinSafaya, thanks for raising the issue! Could you attach an example PDF + code that you are using. This helps us debugging and fixing the issue.

    for lt_object in lt_objects:
        if isinstance(lt_object, LTTextBox) is False:
            continue
        for inner_obj in lt_object:
            if isinstance(inner_obj, LTTextLineHorizontal) is False:
                continue
            text = inner_obj.get_text()

Unfortunately, I can not share the PDF v1.3 file due to client's restrictions

Hi @NitinSafaya, without the pdf there is not much we can do. For that reason I'm closing this. If you ever find another PDF with version 1.3, feel free to reopen.
PDF 1.3 is a subset of PDF 1.7 so I expect most things to work and perhaps the problem is not due to the version of the PDF but other things. You could try using mutools to clean/repair the pdf and then view the PDF again.
Are you getting any errors? Is the text you want to extract selectable when you view it? Can you copy it to a text editor?

authors: NitinSafaya pietermarsman


text:
Website doesnt work

Hi,
I did everything step by step (on server) but website doesnt work. Somebody knows what is the problem ?

yeah use my peatio and my install1.sh

Hello @russlex,
I can help you get Peatio running. I also offer development services.
You can always reach me at nimpo1074@gmail.com
Best,
Oskar

HI can help you.
Add me on skype, just search Peatio Man or add by id:
cid-(-8618737192104534817)@outlook.com

hi peatioMan
I dont have skype account, can you give your email? This is my: hackedmrobot@gmail.com

@russlex
Complete Peatio Help | Support | Bug Fixing
http://peatio.algobasket.com
Free Technical Documentation below :
https://github.com/peatio/peatio/files/2457278/PeatioCryptoExchange.pdf
https://www.youtube.com/watch?v=tpieNIMSBuQ
https://github.com/algobasket/PeatioCryptoExchange/
Contact me on Skype : algobasket
Thanks in advance !!!

authors: algobasket oskanddr peatioMan russlex scatterp

repo: peatio/peatio


text:
Rename {create|update}Message to {create|update}Notification.

@matthewtole

Coverage remained the same at 100.0% when pulling 56c316caaef84650b9a3bf26efcc34ba2f3775ea on bugfix/create-update-notification into 0aeb7106e51a97c6e2fea272cf27731f5d2e57ec on master.

Coverage remained the same at 100.0% when pulling 56c316caaef84650b9a3bf26efcc34ba2f3775ea on bugfix/create-update-notification into 0aeb7106e51a97c6e2fea272cf27731f5d2e57ec on master.

:+1:

authors: Neal coveralls matthewtole

repo: pebble/pebble-api-node


text:
Large Menus Prone to Crash (Aplite)

I've been encountering reliability issues with the way menus function recently, at least on the Aplite platform. Something is causing issues with menus in my Trefoil app, which generates long lists of threads and upon selecting a thread, the posts inside them from AJAX calls:
https://github.com/gitgud-software/trefoil
Aplite builds of Trefoil have a tendency to crash reproducibly when attempting to browse any thread list from any board past Page 4, and with there being 15 threads per page, this means the crash occurs anywhere past 60 entries. If it's an issue of memory, this may be on top of the Board List Menu that the user is prompted with when opening the application. An example JSON call that generates the menus in question can be found here:
https://a.4cdn.org/g/catalog.json
Similar crashes occur when opening threads with several replies, though I haven't been able to get a fixed number at which the menu fails.
The emulator on CloudPebble, rather than crash hard when these problems occur, simply stops displaying menu text entirely, but allows for the menu to be scrolled. No error message is produced upon encountering this failure.
No problems have been encountered on Basalt though. This also didn't used to occur with previous Aplite builds, and with recent changes only having been made to support color for Basalt, the likely culprit is either in pebble.js's or the 3.0 SDK's handling of Aplite.

I'm still encountering this problem as of SDK 3.7 and the latest commits to pebble.js with Aplite, both Basalt and Chalk builds have been running without encountering any problems.

Ah, thanks for reminding me. I was meaning to take a look. I believe your assessment of it being a memory issue is very likely since menu items aren't automatically truncated which might be able to mitigate this issue. Regardless, I should still make sure that the JavaScript can't cause the C side to run out of memory for this particular case.
As a work around, you could try truncating the text that goes into menu items, and leaving the cards to have the full text.

Even using a substring of no more than 5 characters, I find that at the most I have been able to keep the crash from happening until I hit Page 5 of any given board's catalog. I did see improvement, but it remains minimal.

Ah, thanks for testing quickly! I think what I may do is revert the cache amount for aplite to the original working amount, and bump it up when I've improved the memory handling to dynamically deallocate likely unnecessary items when low on memory. This quick revert will be for aplite only since it seems fine on other platforms.

Thanks, in observation the menu where the problems start (the catalog) is the only one that utilizes sections at all. Perhaps it's the way that sections are represented in memory that's eating up the cache amount?

Hmm, yes, sections are a little tricky to handle since they complicate the tricks one can use to implement infinite scrolling with finite visible items, particularly in that they do not have the same height as a menu item. Thanks, I'll keep that in mind when I look into this. Evidently, there is another open issue related to sections wherein the selection is not regained on return since sections > 0 are not preloaded on creation.
I just uploaded a branch bugfix-aplite-menu-cache-size, if you are able to test that, I may be able to add that in the cloudpebble PR I created recently as well. Otherwise I can schedule another update in a week or two.

Yeah, I can confirm that Trefoil is now building and running without error on Aplite. Thanks for the fix.

authors: Meiguro gitgud-software

repo: pebble/pebblejs


text:
Esse método de envio está fora do ar. Por favor entre em contato conosco.

ao utilizar a versão 4.3 está ocorrendo esse erro: Esse método de envio está fora do ar. Por favor entre em contato conosco.
como corrigi-lo?
muito obrigado.
abs.

@fernandogargula, esse erro acontece quando os Correios estão fora do ar. Por favor siga as regras para reportar erros e envie os logs: https://github.com/pedro-teixeira/correios/blob/master/CONTRIBUTING.md
Você pode usar o app para iPhone para validar a API dos Correios: https://pedroteixeira.io/app-de-iphone-para-checar-se-os-correios-estao-online/

authors: fernandogargula pedro-teixeira

repo: pedro-teixeira/correios


text:
Habilitar módulo para "Recurring Profiles"

Pretendo criar uma loja que tenha a opção de assinatura para alguns itens. Atualmente, o módulo não aparece nas opções de envio se o produto for um Recurring Profile.
[Feature request]

BTW, o módulo está muito bom :D

Olá @pedro-teixeira ,
Adicionei esse atributo de classe protected $_isFixed = true; em app/code/community/PedroTeixeira/Correios/Model/Carrier/CorreiosMethod.php e consegui habilitar o módulo para produtos com recurring profile.
Porém, o peso está sendo considerado como '0' em algum momento, e por isso o usuário é impedido de usar a forma de entrega. Apenas por teste eu fiz a seguinte alteração:
+        $this->_packageWeight = 1;
         // Check weight zero
         if ($this->_packageWeight <= 0) {
             $this->_throwError('weightzeroerror', 'Weight zero', __LINE__);
             return $this->_result;
         }

E o peso foi calculado corretamente e pude efetuar a compra com este método de entrega (com produtos recurring profile e produtos tradicionais). Até o momento não identifiquei efeitos colaterais.
Você pode me indicar como corrigir o problema do peso?
Grato! :smile:

Posso dar uma olhada futuramente, para entender o motivo do peso estar errado.
Por enquanto segue essa sugestão:

Adicionar o método a seguir:
protected function _getNominalWeight()
{
$weight = 0;
$quote = Mage::getSingleton('checkout/cart')->getQuote();
if (count($quote->getAllVisibleItems()) == 0) {
$quote = Mage::getSingleton('adminhtml/session_quote')->getQuote();
}
if ($quote->isNominal()) {
foreach ($quote->getAllVisibleItems() as $item) {
$product = Mage::getModel('catalog/product')->load($item->getProductId());
$weight += $product->getWeight();
}
}
return $weight;
}

Localizar o comentário // Fix weight e adicionar o trecho a seguir:
 if ($this->_packageWeight == 0) {
     $this->_packageWeight = $this->_getNominalWeight();
 }

Importante: não foi testado!

Obrigado, @jarjar123! Sua sugestão corrigiu o problema.
Não preciso mais deixar o peso fixo!
A minha alteração combinada com a sua fez com que o módulo se aplica-se à recurring profile tambem (além dos produtos comuns)!

@matheusjardimb, pode enviar uma pull request com essas mudanças?

@pedro-teixeira claro!

https://github.com/pedro-teixeira/correios/pull/91 @pedro-teixeira @jarjar123

authors: jarjar123 matheusjardimb pedro-teixeira


text:
(Question) Changelog on readme

Can be a great ideia to organize the new features...

To organize features we are using issues not a changelog. Thanks for your idea, but I prefer github issues.

authors: pedrovgs ppamorim

repo: pedrovgs/DraggablePanel


text:
🛑 API MERCADO PUBLICO is down

In 0af9228, API MERCADO PUBLICO (https://api.mercadopublico.cl/servicios/v1/publico/ordenesdecompra.json?fecha=30122022&CodigoOrganismo=7312&ticket=E1951384-BF88-4EE5-8C33-934680281626) was down:

HTTP code: 500
Response time: 890 ms

Resolved: API MERCADO PUBLICO is back up in 11d9cae after 11 minutes.


text:
🛑 Beyond.pl is down

In f5911e8, Beyond.pl (http://www.beyond.pl) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Beyond.pl is back up in 715bee7.

repo: pejotes/upptime


text:
🛑 Beyond.pl is down

In a8aaff8, Beyond.pl (http://www.beyond.pl) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Beyond.pl is back up in a1c8aa4 after 10 minutes.


text:
🛑 Beyond.pl is down

In d31219e, Beyond.pl (http://www.beyond.pl) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Beyond.pl is back up in 6545310 after 1 hour, 34 minutes.


text:
🛑 Beyond.pl is down

In 5262a8b, Beyond.pl (http://www.beyond.pl) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Beyond.pl is back up in 29ce89e after 18 minutes.


text:
How to set an initial offset position / margin / padding  for header builder  ?

I own a StaggeredGridView which have a top padding to start the grid at 100 from top and can scroll until top screen.
How can I set an initial offset position to the header builder in order to match both starting position according the padding ?
I reproduced it with a simple list to illustrate my use case :

headerBuilder: () {
        return CustomHeader(
            refreshStyle: RefreshStyle.Behind,
            builder: (BuildContext context, RefreshStatus mode) {
              return Container(color: Colors.red, alignment: Alignment.center, child: Text("Refresh"));
        });
      },

Is there an attribute from this lib that I missed or any workaround to solve this ? Thanks

Is this possible to achieve, I'm interested too.


text:
强制裁剪回退时会看到中间页面

强制裁剪完，自动退出裁剪页面后，可以看到中间页面，虽然很快也被自动关闭了，但用户大概因为这儿会疑惑一下，因为启动时并没有看到这个中间页

嗯~这是程序设计上的问题。谢谢提醒

repo: pengjianbo/GalleryFinal


text:
Non E(3) equivariant model issue

Hi, nice paper published. Retarding to your E(3) model, I think your model might be not translational equivariant. I have similar questions with @oriondollar. I think it might be better to open a new issue here.
(1) In your model, normalized absolute coordinates were directly used as input vector features. So, I am wondering your model might not work for other test data having different absolute coordinates. As you mentioned in @oriondollar solution, that we can translate the center of pocket mass to the origin of coordinate.  I want to ask could this solve the non-translational equivariance perfectly?
(2) I noticed you used normalization factor=20 to normalize the input absolute coordinate vectors, do you have any purposes to choose 20?
(3) Similar to the question (1), For vertex vectors, I noticed you used normalized absolute coordinates directly, Could this guarantee the equivariance? If we use different normalized absolute coordinates as vertex vectors,  will your model work?
(4) You also mentioned that the embedding layer has minor effect on the translational equivariance and the model still learns the translational equivariance since the substraction of vectors remain unchanged. But from my test, it doesn't work if I used a different protein-ligand data outside training data coordinate space.
Do I misunderstand something? Do you have any ideas to solve this issue? Looking forward to your reply. Thank you in advance.

Hi, thanks for your insightful questions. Here are my answers.
(1) Theoretically, translating to the origin can ensure the translational equivariance of the model. This strategy is also applied to other related works, such as GeoDiff and TargetDiff. I think this is a simple yet effective strategy to make an O3 equivariant model be translational equivariant.
(2) The value was chosen to make the normalized vector features comparable to the scalar feature.
(3) As I explained in the (previous issue)[https://github.com/pengxingang/Pocket2Mol/issues/16], using the coordinates as the initial vector features seemed not born to be equivariant. But the model can learn the subtraction of two vector features to be equivariant. According to our evaluation, the pockets in the test set do not have the same coordinates as those in the training set but the model still worked for it. So we think the model can sample for pockets with different absolute coordinates.
(4) Most samples are coordinated around the origin so the original model with weak translational equivariance can work for them. But if the samples are moved far away, a strict equivariance is required. To solve it, we can modify the initial vector features, such as using all-zero initial vectors or relative positions as other related works do.

Hi, thank you very much for you detailed and helpful answers.
(1) Thanks for sharing the paper information. I will check.
(2) I see. So, for different input absolute coordinates, the normalization_factor should be changed.
(3) I see.
(4) I still have some questions about the ideas your provided:

Using all-zero initial vectors to replace initial absolute coordinates is interesting. But I am wondering that the zero vector might destroy global geometric features that could be learned by your model, since we changed global location/position of each node to zero and the model might not able to learn the correct directions of next atoms. As I tried, the model could work for different translations, but the performance degrades and difficult to close rings.  How do you think?
You also suggested using relative positions as vertex vector features. But I am still confusing that how should we define good relative positions, since each node could have several neighbours. Do you have any good idea for that?
BTW, do you have any plans to further improve your current implementation to strict E(3) model in the future ?

Again, thank you so much.

I did not mean using all-zero as the initial absolute coordinates. The initial atom coordinates are not changed. I just mean that only the vector features are initialized as all zeros.
A simple strategy is that the initial vector features of a vertex are calculated from the summation (of other pooling) of the relative vectors pointing from all other vertices to this vertex. Then the following update is the same as before. In this way, the initial vector features are equivariant.
You can check the paper PaiNN for more information about using vector features. In that paper, they used all-zero as vector initialization. I think it is a good idea to improve Pocket2Mol to a strict E(3) model for better generalization, using strategies discussed above or other equivariant models. But currently we do not have a plan to do that.

Thank you so much for your valuable solutions, which inspires me a lot. I would like to try these methods you mentioned, also looking forward to your updated model in the future.

authors: pengxingang yangxiufengsia


text:
文章内一级标题不会显示右侧边栏

你好，请问一级标题是无法显示右侧边栏吗？
MD文件

效果显示

一级标题不会显示在 侧边栏的。
因为 一级标题 的作用是 作为文章的大标题，而它在 fronmatter.title 中已进行配置。
因此，文章内容一般就不需要包含 一级标题 了，而是从 二级标题 开始，这也是大部分 md 写作时的通用规范了

一级标题不会显示在 侧边栏的。 因为 一级标题 的作用是 作为文章的大标题，而它在 fronmatter.title 中已进行配置。 因此，文章内容一般就不需要包含 一级标题 了，而是从 二级标题 开始，这也是大部分 md 写作时的通用规范了

好的，还有一个问题想请教，就是我设置了base属性，然后导航栏的路径出现了问题，自动给我重复了两次base的路径，这种我该怎么解决呢？
配置文件如下：

dev后，鼠标悬停放在首页，左下角还是正确的路径

点击首页跳转后，就出现了问题

发现了存在 base 导致的 链接解析生成的错误，这算是一个恶性bug了，我发个版本进行修复。

发现了存在 base 导致的 链接解析生成的错误，这算是一个恶性bug了，我发个版本进行修复。
主题版本升级到 1.0.0-rc.51 即可修复该问题。

好的，我刚刚更新了，现在是还不能用pnpm更新到最新这个版本吗

在项目根目录中添加 .npmrc 文件，并写入以下内容：
strict-peer-dependencies=false
shamefully-hoist=true
shell-emulator=true

就可以及时更新了，pnpm 默认的缓存策略，其刷新缓存的机制 偶尔会导致获取不到刚更新的新版本。

在项目根目录中添加 .npmrc 文件，并写入以下内容：
strict-peer-dependencies=false
shamefully-hoist=true
shell-emulator=true

就可以及时更新了，pnpm 默认的缓存策略，其刷新缓存的机制 偶尔会导致获取不到刚更新的新版本。

还是没办法更新的最新的版本，😢😢

emmm, npm 源确实已经更新到 1.0.0-rc.51，我在我本地进行 pnpm add xxx 也确实安装的是 1.0.0-rc.51，而且也已经更新了差不多 1小时了，应该是可以正常拉取到的

emmm, npm 源确实已经更新到 1.0.0-rc.51，我在我本地进行 pnpm add xxx 也确实安装的是 1.0.0-rc.51，而且也已经更新了差不多 1小时了，应该是可以正常拉取到的

可以了，因为我用的是淘宝的镜像，所以才没有，换成官方镜像就可以了；太感谢作者了😊
除此之外还有小问题想请教作者
博客页面个人头像展示的问题
就是这样展示不出图片头像
配置文件和图片路径如下：

页面效果

导航栏的LOGO
但是导航栏的logo可以使用个人头像上相同路径的图片

展示效果如下

然后有一个问题就是，没有在主题配置里找到可以配置出和DEMO一样的导航栏logo，就是展示出下面这样的效果

博客页面个人头像展示的问题

这个是由于在很早期的时候实现该文能时，忽略了 base 选项带来的影响，导致了这个问题，是一个 bug，我会放在下个版本计划中进行修复（大概在本周内修复），目前可以先在配置中把 base 拼接上，/blogs/ok.jpg 进行使用。

没有在主题配置里找到可以配置出和DEMO一样的导航栏logo，就是展示出下面这样的效果

我不确定你是单指 logo 还是指 logo + title， 主题的这个效果，是配置了 theme.logo， 和 userConfig.title 实现的:
 export default defineUserConfig({
   lang: 'zh-CN',
   base: '/',
+  title: 'Plume 主题',
   theme: themePlume({
+    logo: 'logo.png'
   })
 })

如果是多语言，可以这样配置：
 export default defineUserConfig({
   lang: 'zh-CN',
   base: '/',
+  locales: {
+    '/': { title: 'Plume 主题', lang: 'zh-CN' },
+    '/en/': { title: 'Plume Theme', lang: 'en-US' },
+  },
   theme: themePlume({
+    logo: 'logo.png'
   })
 })

可以了，我指的就是logo+title的效果，另外关于base的路径问题，还有归档和标签的路径解析有bug
标签路径bug

归档路径bug

辛苦作者了，太感谢了😊

我排查下与 base 相关的跳转链接，在下个版本中一并修复这些问题。

主题版本 1.0.0-rc.52 已可修复 相关问题。

主题版本 1.0.0-rc.52 已可修复 相关问题。

可以了，辛苦作者啦，

authors: YTAZWC pengzhanbo

repo: pengzhanbo/vuepress-theme-plume


text:
[SP-2812][PDI-8931] SlaveServer Synchronized methods need to be examined

Removed unnecessary synchronization, added lacked synchronization
Test written
Checkstyle applied
@mchen-len-son Could you please merge it?

This is completely wrong. This is along the lines of the PR I closed. Instead, you should be looking at the fixed PR that Ivan re-worked and was merged here: https://github.com/pentaho/pentaho-kettle/commit/dbac4c9e042a795288c5cdf8fc5519e9275e00e9

authors: AliaksandrShuhayeu mbatchelor

repo: pentaho/pentaho-kettle


text:
[PDI-16229]-Dummy job entry can not be opened/renamed.

-fixed

Build Completed
:x: This pull request has errors. They will need to be addressed before it can be accepted. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -fn -f 'pom.xml' -pl 'ui,engine' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'ui,engine' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  engine/src/main/resources/org/pentaho/di/job/entries/special/messages/messages_en_US.properties
  ui/src/main/java/org/pentaho/di/ui/job/entries/special/JobEntrySpecialDialog.java
  ui/src/main/java/org/pentaho/di/ui/spoon/delegates/SpoonJobDelegate.java

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes (click to expand)
org.pentaho.di.core.injection.bean.BeanInjector

Branch Change: -0.7% :small_red_triangle_down:
Complexity Change: -1.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.datagrid.DataGridMeta

Branch Change: -2% :small_red_triangle_down:
Complexity Change: -1.7% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.replacestring.ReplaceStringMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.singlethreader.SingleThreaderMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.textfileinput.TextFileInputMeta

Branch Change: -0.5% :small_red_triangle_down:

Checkstyle violations
The code submitted is not complying with one or more of our guidelines. To perform these checks locally, please use this tool.
/home/buildguy/project/ui/src/main/java/org/pentaho/di/ui/job/entries/special/JobEntrySpecialDialog.java

:heavy_exclamation_mark: '(' is not followed by whitespace. at Line: 154 Column: 28

:heavy_exclamation_mark: ')' is not preceded with whitespace. at Line: 154 Column: 49

:heavy_exclamation_mark: '(' is not followed by whitespace. at Line: 229 Column: 30

:heavy_exclamation_mark: ')' is not preceded with whitespace. at Line: 229 Column: 51

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -fn -f 'pom.xml' -pl 'ui,engine' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'ui,engine' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  engine/src/main/resources/org/pentaho/di/job/entries/special/messages/messages_en_US.properties
  ui/src/main/java/org/pentaho/di/ui/job/entries/special/JobEntrySpecialDialog.java
  ui/src/main/java/org/pentaho/di/ui/spoon/delegates/SpoonJobDelegate.java

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes (click to expand)
org.pentaho.di.core.injection.bean.BeanInjector

Branch Change: -0.7% :small_red_triangle_down:
Complexity Change: -1.2% :small_red_triangle_down:

org.pentaho.di.job.entries.ftpsget.JobEntryFTPSGet

Branch Change: -0.6% :small_red_triangle_down:
Complexity Change: -0.5% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.job.entries.waitforsql.JobEntryWaitForSQL

Branch Change: -0.8% :small_red_triangle_down:
Complexity Change: -1% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.datagrid.DataGridMeta

Branch Change: -2% :small_red_triangle_down:
Complexity Change: -1.7% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.dimensionlookup.DimensionLookupMeta

Method Change: -1% :small_red_triangle_down:

org.pentaho.di.trans.steps.groupby.GroupByMeta

Branch Change: -1.1% :small_red_triangle_down:
Complexity Change: -1% :small_red_triangle_down:

org.pentaho.di.trans.steps.singlethreader.SingleThreaderMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.uniquerows.UniqueRowsMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.webservices.WebServiceMeta

Branch Change: -1.7% :small_red_triangle_down:
Complexity Change: -1.2% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.gpload.GPLoadMeta

Branch Change: -0.9% :small_red_triangle_down:
Complexity Change: -0.8% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.salesforceupsert.SalesforceUpsertMeta

Instruction Change: -0.1% :small_red_triangle_down:

authors: denisprotopopov wingman-pentaho


text:
[BACKLOG-23747] Moving topic UI section to its own composite for better reuse

[BACKLOG-23747] Moving topic UI section to its own composite for better reuse

Build Completed
:x: This pull request has errors. They will need to be addressed before it can be accepted. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -fn -f 'pom.xml' -pl 'ui' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'ui' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  ui/src/main/java/org/pentaho/di/ui/core/widget/TopicSelection.java

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes (click to expand)
org.pentaho.di.trans.steps.salesforceupsert.SalesforceUpsertMeta

Instruction Change: -0.1% :small_red_triangle_down:

:new: org.pentaho.di.ui.core.widget.TopicSelection

Coverage: 0% :exclamation:

:new: org.pentaho.di.ui.core.widget.TopicSelection.Builder

Coverage: 0% :exclamation:

License header violations

:heavy_exclamation_mark: Couldn't find acceptable copyright on ui/src/main/java/org/pentaho/di/ui/core/widget/TopicSelection.java

:heavy_exclamation_mark: Couldn't find acceptable license on ui/src/main/java/org/pentaho/di/ui/core/widget/TopicSelection.java

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -fn -f 'pom.xml' -pl 'ui' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'ui' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  ui/src/main/java/org/pentaho/di/ui/core/widget/TopicSelection.java

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes (click to expand)
org.pentaho.di.trans.steps.salesforceupdate.SalesforceUpdateMeta

Instruction Change: -0.2% :small_red_triangle_down:

:new: org.pentaho.di.ui.core.widget.TopicSelection

Coverage: 0% :exclamation:

:new: org.pentaho.di.ui.core.widget.TopicSelection.Builder

Coverage: 0% :exclamation:

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -fn -f 'pom.xml' -pl 'ui,plugins/streaming/impls/mqtt' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'ui,plugins/streaming/impls/mqtt' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  plugins/streaming/impls/mqtt/src/main/java/org/pentaho/di/trans/step/mqtt/MQTTConstants.java
  plugins/streaming/impls/mqtt/src/main/java/org/pentaho/di/trans/step/mqtt/MQTTProducer.java
  plugins/streaming/impls/mqtt/src/main/java/org/pentaho/di/trans/step/mqtt/MQTTProducerDialog.java
  plugins/streaming/impls/mqtt/src/main/java/org/pentaho/di/trans/step/mqtt/MQTTProducerMeta.java
  plugins/streaming/impls/mqtt/src/main/resources/org/pentaho/di/trans/step/mqtt/messages/messages_en_US.properties
  plugins/streaming/impls/mqtt/src/test/java/org/pentaho/di/trans/step/mqtt/MQTTProducerMetaTest.java
  ui/src/main/java/org/pentaho/di/ui/core/widget/TopicSelection.java

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes (click to expand)
org.pentaho.di.trans.step.mqtt.MQTTProducerMeta

Complexity Change: -0.8% :small_red_triangle_down:
Instruction Change: -0.6% :small_red_triangle_down:
Line Change: -0.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.salesforceupsert.SalesforceUpsertMeta

Instruction Change: -0.1% :small_red_triangle_down:

:new: org.pentaho.di.ui.core.widget.TopicSelection

Coverage: 0% :exclamation:

:new: org.pentaho.di.ui.core.widget.TopicSelection.Builder

Coverage: 0% :exclamation:

authors: ricksjames wingman-pentaho