Command not on command key on Mac

The "command" and "option" of hello os are the opposite of the mac keyboard arrangement.
Video:
https://github.com/helloSystem/hello/discussions/399#discussioncomment-4119535

The video is a virtual machine because it is too difficult to boot on a physical machine, but it is the same on a physical machine.

To be retested.

Maybe need to delete/edit /usr/local/etc/xdg/Xmodmap?

Recent versions are not working as expected.
https://youtu.be/y0vDHbh0CXw

You delete that file first, use it as iso and let me test whether it works.

I don't know what you mean by this.

Build the version iso file that removes "/usr/local/etc/xdg/Xmodmap", let me test whether the keyboard keys of mac are back to normal.

What do you mean by "back to normal"? Are they not "normal"? Since when?
To test such things, you can use https://hellosystem.github.io/docs/developer/monkey-patch.html. No need to make special ISOs.

Update: I was half wrong, the ⌘ button was in the wrong place.
https://youtu.be/rraqX3OdXic

My previous video didn't express it clearly, but this video is what I want to express.
https://youtube.com/shorts/8T20wc7BoAY?feature=share

It is also wrong on the physical machine. I was lucky enough to let my Macbook execute hello OS but the key configuration of the keyboard is also wrong. Before you can solve the Mac keyboard problem, temporarily disable the swap button, because if the configuration is successful, there is already an easy option in the Ubuntu Settings Center to switch.

Just think of it, when Apple built the Mac system, it inherited the main Ctrl key [this is the PC keyboard] function (such as the shortcut key on the cut-out sticker) to the win key (⌘) (but the Ctrl key [this is the Mac keyboard] is still the Ctrl key, but it has become a non-primary shortcut like the Alt of the PC).

All I can say at this point is that using an Apple keyboard (on a PC or on a Mac running helloSystem) will result in Command to work like it is expected to work (=Command is the key to the left of the space bar). Other keys may be messed up but getting Command to work properly was my #1 priority. If anyone can contribute working tested code to improve things further, I'm happy to test and consider it.

By the way, have you started testing Apple USB keyboards on Hellos yet?


[Spike] Internationalization support using react-i18next

Description
Do not merge this PR, I just created it to discuss the implementation
Installed the react-i18next libary to add translation support and translated the Home string that says Last updated to Spanish and English. The default language will be selected based on your browser preference.
Testing
Ran the unit tests. Deployed to my personal environment.
https://fdingler.badger.wwps.aws.dev

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Closing as it was just a spike.

Closing as it was just a spike.


Shorter python import

Now you have to do
from remotebmi.client.client import RemoteBmiClient

it would nice if this was shorter
from remotebmi import RemoteBmiClient

Same goes for the container clients and server main function (which might need to be renamed to more a library friendly name)

Yeah this would be much nicer! :+1:

Fixed this in #37, except for;

server main function (which might need to be renamed to more a library friendly name


al-phd.elr SFTP upload failure.  It needs to resend.

[1;31m18:34:09.682 [pool-2-thread-198][36901] FATAL-ALERT gov.cdc.prime.router.azure.SendFunction - FAILED Sftp upload of inputReportId a87abcc0-29ba-4f58-b6db-79cac179fde9 to SFTPTransportType(host=<IP_ADDRESS>, port=22, filePath=./upload, credentialName=null) (orgService = al-phd.elr), Exception: Exhausted available authentication methods, All retries failed.  Manual Intervention Required.  Send Error report for: a87abcc0-29ba-4f58-b6db-79cac179fde9 to al-phd.elr[m

This staging message was sent to the invalid host as set in the staging setting:
"host": "<IP_ADDRESS>",
"port": "22",
"filePath": "./upload",
"credentialName": null,
"type": "SFTP"
}
Therefore, it is failed.  al-phd.elr doesn't have staging/testing SFTP site.  It only has prod SFTP site.
I will close this ticket.

This is an old ticket.  I am closing it.


Bug: Provider tutorial not working

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
I am new to this project and I am trying to get the tutorial running.
I cloned the project and tried to run the tutorial code when I wanted to run the provider.py I got the following error message:
2024-02-16 14:09:55,004 - sdc.discover - INFO - UDP socket listens on <IP_ADDRESS>:3702
My UUID is 72313cab-7352-51c9-8373-8b4031a66ec7
2024-02-16 14:09:55,095 - sdc.device.ExtendedProduct - INFO - init_operations for sco sco.mds0.
2024-02-16 14:09:55,096 - sdc.device.op_reg - INFO - register operation "ActivateOperation handle=actop.mds0_sco_0 code=CodedValue(196279, codingsystem="urn:oid:1.2.840.10<IP_ADDRESS>.0.0.1") operation-target=mds0"
2024-02-16 14:09:55,096 - sdc.device.op_reg - INFO - register operation "SetContextStateOperation handle=ensemble.mds0_sco0 code=CodedValue(1234567, codingsystem="urn:oid:1.2.840.10<IP_ADDRESS>.0.0.1") operation-target=EN.mds0"
2024-02-16 14:09:55,097 - sdc.device.ExtendedProduct - INFO - role handler AudioPauseProvider added operations to mdib: ActivateOperationDescriptor AP__ON, ActivateOperationDescriptor AP__CANCEL
2024-02-16 14:09:55,097 - sdc.device.op_reg - INFO - register operation "ActivateOperation handle=AP__ON code=CodedValue(128284, codingsystem="urn:oid:1.2.840.10<IP_ADDRESS>.0.0.1") operation-target=mds0"
2024-02-16 14:09:55,097 - sdc.device.op_reg - INFO - register operation "ActivateOperation handle=AP__CANCEL code=CodedValue(128285, codingsystem="urn:oid:1.2.840.10<IP_ADDRESS>.0.0.1") operation-target=mds0"
2024-02-16 14:09:55,097 - sdc.device.ExtendedProduct - INFO - sco sco.mds0: all operations have a handler.
2024-02-16 14:09:55,097 - sdc.device.ExtendedProduct - INFO - init_operations for sco sco.vmd0.
2024-02-16 14:09:55,098 - sdc.device.ExtendedProduct - INFO - sco sco.vmd0 has no operations in mdib.
2024-02-16 14:09:55,098 - sdc.device.ExtendedProduct - INFO - init_operations for sco sco.vmd1.mds0.
2024-02-16 14:09:55,098 - sdc.device.op_reg - INFO - register operation "ActivateOperation handle=actop.vmd1_sco_0 code=CodedValue(196279, codingsystem="urn:oid:1.2.840.10<IP_ADDRESS>.0.0.1") operation-target=mds0"
2024-02-16 14:09:55,098 - sdc.device.op_reg - INFO - register operation "SetValueOperation handle=numeric.ch0.vmd1_sco_0 code=CodedValue(196276, codingsystem="urn:oid:1.2.840.10<IP_ADDRESS>.0.0.1") operation-target=numeric.ch0.vmd1"
2024-02-16 14:09:55,098 - sdc.device.op_reg - INFO - register operation "SetStringOperation handle=enumstring.ch0.vmd1_sco_0 code=CodedValue(196277, codingsystem="urn:oid:1.2.840.10<IP_ADDRESS>.0.0.1") operation-target=enumstring.ch0.vmd1"
2024-02-16 14:09:55,099 - sdc.device.op_reg - INFO - register operation "SetStringOperation handle=string.ch0.vmd1_sco_0 code=CodedValue(196278, codingsystem="urn:oid:1.2.840.10<IP_ADDRESS>.0.0.1") operation-target=string.ch0.vmd1"
2024-02-16 14:09:55,099 - sdc.device.ExtendedProduct - INFO - sco sco.vmd1.mds0: all operations have a handler.
2024-02-16 14:09:55,099 - sdc.device - INFO - no PeriodicReportsHandler
2024-02-16 14:09:55,099 - sdc.device - INFO - starting services, addr = ['<IP_ADDRESS>']
2024-02-16 14:09:55,116 - sdc.device.httpsrv - INFO - starting http server on <IP_ADDRESS>:57664
2024-02-16 14:09:55,116 - sdc.device - INFO - serving Services on <IP_ADDRESS>:57664
Traceback (most recent call last):
  File "F:\sdc11073\tutorial\provider\provider.py", line 85, in <module>
    set_local_ensemble_context(my_mdib, "MyEnsemble")
  File "F:\sdc11073\tutorial\provider\provider.py", line 35, in set_local_ensemble_context
    with mdib.transaction_manager() as mgr:
AttributeError: 'ProviderMdib' object has no attribute 'transaction_manager'

What have I missed?
Expected Behavior
The provider starts without an error and can interact with the consumer.py
Minimal Reproducible Example
No response
Solution proposal
No response
Python Version
Python 3.9.1
Operating system
win32
Sdc11073 Version
sdc11073-0.0.0
Link to sdc11073 Logs
No response
Further Information
No response
Participation

[ ] I am willing to submit a pull request to fix this bug.

Was fixed in b81a57f63d9fc6c1f3163c9058aa5858e630c8d3, 2024-02-27


feat: implement 0x50 - POP Opcode

Feature Request

Since
Group

Frontier
Stack Memory Storage and Flow Operations

Index 1 is top of the stack. See PUSH.
Stack input

y: a stack item.

Example

Input
Output

1
125985

Reproduce in playground.
Error cases
The state changes done by the current context are reverted in those cases:

Not enough gas.
Not enough values on the stack.

### Tasks
- [ ] https://github.com/kkrt-labs/kakarot-ssj/issues/263
- [ ] After #263 is implemented, go and implement the business logic of POP

Can I have this one please ?


[java] cannot read datasets with many columns

Describe the bug, including details regarding any error messages, version, and platform.
Dataset API gets stuck if one tries to read many columns (100k+) from a parquet or arrow file.  The API works if the amount of columns is narrowed via projection.
Reproduction:
Use the code from the example and try to read a file with 100k columns. No batch will be loaded even if the batch size is 1.
version: arrow-dataset 11.0
Component(s)
Java

Could you provide an example file to reproduce this issue?


Fancybox fix

Fixed the regex issue described in issue #189.

... this is more restrictive than the original. This will fail on BMP, avif, jpeg, webp


Uncaught (in promise) TypeError: Cannot read property 'instanceMap' of undefined

Version
6.0.0-beta.11
Browser and OS info
chrome mac os big sur
Steps to reproduce
error when changing route using vue router.  this error does not appear if i disable dev tools extension
What is expected?
no error
What is actually happening?
error in console tab

Uncaught (in promise) TypeError: Cannot read property 'instanceMap' of undefined
at getComponentInstance (backend.js:991)
at Object.sendSelectedComponentData (backend.js:935)
at Object. (backend.js:1211)
at Object.emit (:1:755)
at DevtoolsPluginApiInstance.notifyComponentUpdate (backend.js:381)
at eval (vue-router.esm-bundler.js?6c02:2436)
at callWithErrorHandling (runtime-core.esm-bundler.js?5c40:154)
at callWithAsyncErrorHandling (runtime-core.esm-bundler.js?5c40:163)
at Array.job (runtime-core.esm-bundler.js?5c40:2077)
at flushPreFlushCbs (runtime-core.esm-bundler.js?5c40:328)

I'm having the same error

@Akryum can you release this bug fix to chrome ? Its really hard to debug with all the errors thrown by this bug.

After reinstalling dev-tools, the error no longer appears


Add Quick Open Support Buttons To WAT

Just in the top-right corner of the display add buttons like "Report Issue", "Request Feature" etc that quick opens to github. Maybe even builtin documentation?

Resolved by 556f7441d4bfabd51e3b6612769cb73d760260b0


(WIP) Adding exclusion list for object serialization.

This is an PR with an attempt to implement the suggestion raised in #3588.
Based on the suggestion in the Issue, I implemented a mechanism in the ObjectReflectionCache for excluding types based on a type argument, a generic type, or a function to evaluate based on other mechanisms (Namespace, Assembly, etc)
To provide an initial solution, I just added some static methods at the end of the JsonSerializationOptions class.  I don't think they belong there, but I could not find a better class and I assumed that making the ObjectReflectionCache public would be a bad idea.  If there's no other options, a singleton class might be a long term option.  A singleton with some testing seams may also help address 'To Do' item no. 2 below.
To Do

[ ] Find permanent home for the configuration methods.
[ ] There is the potential of some concurrency issues in the unit tests due to the static configuration.
[ ] Address any changes raised in the pull request.

Thanks! Will look at this indepth soon!

PS. Related: https://github.com/NLog/NLog/issues/3264

I would probably create an interface that can return true/false for a type.
Then have a default implementation of this interface that matches the current logic in ObjectReflectionCache
Then allow one to assign a new custom implementation of the interface. Maybe some helper methods that captures the original interface-implementation and chains it together with the new restriction.
Making the following boilerplate code pretty:
class SkipObjectReflection : IRestrictObjectReflection
{
Type _newType;
IRestrictObjectReflection _original;

public SkipObjectReflection(IRestrictObjectReflection original, Type newType)
{
    _original = original;
    _newType = newType;
}

public bool SkipReflection(Type type)
{
    if (_newType.IsAssignableFrom(type))
          return true;

   return _original.SkipReflection(type);
}
}

var original = NLog.Config.ConfigurationItemFactory.Default.RestrictObjectReflection;
NLog.Config.ConfigurationItemFactory.Default.RestrictObjectReflection = new SkipObjectReflection(original, skipNewType);

Could also make a more advanced version of the interface, that returns an array like this:
interface IObjectTypeReflection
{
    IList<KeyValuePari<string,MemberInfo>> GetProperties(Type type);
}

Then make a contract:

Returning null then it performs obejct.ToString().
If it returns single item without any Key-name, then it will use the MemberInfo as custom object.ToString().

Then it would resolve both  #3519 and #3588

So, I've spent a bit of time thinking about this and working through this in code, and I'm running into some stumbling blocks.
It looks like the advanced interface should signal one of three serialization options:

ToString
Custom list (subset) of properties
Custom serialization.

Regarding your proposal for custom serialization, I'm curious about your limitation for a single MemberInfo.  It would limit the customizations to a single (and direct accessed) member, which wouldn't quite address some of the concerns with #3519 (specifically the request for invoking GetResponseStream for WebExceptions).  It may be advantageous here to consider a Func<T, object> which could then be registered as a custom serializer.
config.RegisterCustomSerializer<Assembly>(); // Would register as 'ToString()'
config.RegisterCustomSerializer<CustomException>(new[] { "Property1", "Property2", "Property4" ); //Would register property list filter.
config.RegisterCustomSerializer<Win32Exception>(ex=> $"NativeErrorCode: {ex.NativeErrorCode}") //Would register custom func

//Also, this may be overkill, but the same pattern would allow a consumer to craft their own object:
config.RegisterCustomSerializer<CustomObject>(o=>new { o.Property1, Renamed = o.Child.GetCustomValue() });

Again, I'm not sure how this will conflict with some of the object path conversation on #3520.
Thoughts?

@mmurrell You are right. The interface should probably be like this:
interface IObjectTypeReflection
{
    IList<KeyValuePair<string,object>> GetProperties(object obj);
}

But that would require some heavy refactoring of ObjectReflectionCache to avoid killing performance.

I know this is a bit of a different direction, but these commits could accomplish the goal without impacting the ObjectReflectionCache.  I did follow your advice with the object-chaining implementation.
In this case, the serialization is intercepted before it gets to the ObjectReflectionCache, allowing the object to be augmented or replaced before it even gets there.
If this different direction is acceptable, I would like to build out some at least a Func<T, object> interceptor, and maybe some others as need dictates.

@mmurrell Would like to have this filtering to work also for XmlLayout, and other locations where ObjectReflectionCache is being used.
Have created an implementation of my thoughts here: #3610 (Stolen your unit-test to show how it works)


Allow overriding hostname for secure_channel in Python client

Today it's hard (impossible?) to override hostname for the CN certificate validation without going deep into the gRPC internals so adding a hostname_override to grpc.beta.implementations.secure_channel would be useful.

So what led me to leave hostname overriding out of the production API was the direction "This *should* be used for testing only." where the relevant channel argument is defined.
Are you in a situation in which you need this capability for non-test production code? If you need this capability in a test, are you aware of the not_really_secure_channel function available to test code?

This is for production code yes. This is for cases where I want to use local daemons on the same system using CN to identify what function they are serving. For example: Imagine I have a "password" daemon, it would have CN=password and I would connect to "localhost".
If for any reason you need to connect to a server without using DNS (for dependency reasons, alternative discovery services or whatnot) you would also need this feature.

@ctiller: Please assess? Is setting SERVER_HOST_OVERRIDE in non-test code a good idea?

Ping

Ping

For those of you waiting for this: this capability is an underdocumented power-user feature in the GA API and I doubt that we'll be adding it to the Beta API.

That's OK for me. I tried following it down the rabbit hole but got lost in grpc_secure_channel_create. Care to show an example how the initialization of the channel would look like?

@bluecmd: how about something like
my_channel = grpc.secure_channel(
    my_target, my_channel_credentials,
    options=(('grpc.ssl_target_name_override', my_server_host_override_string,),))

?

Sounds good! That's simple enough for me.

Closing; this has been implemented since 0.15.


"Datatype coercion is not allowed" when creating session with custom timeseries array

Here's a script that creates a basic timeseries of Gaussian noise in a 2×1000 array.
#!/usr/bin/env python3

import numpy as np
import pbjam

n = 1000
data = np.zeros((2,n))
data[0] = np.arange(n, dtype=float)
data[1] = np.random.randn(n)

s = pbjam.session(ID='mwe', numax=(100, 1), teff=(5000, 100), bp_rp=(0.7, 0.005), dnu=(5, 0.1), timeseries=data)

It fails with the following traceback:
Traceback (most recent call last):
  File "/home/wball/try/pbjam/mwe.py", line 11, in <module>
    s = pbjam.session(ID='mwe', numax=(100, 1), teff=(5000, 100), bp_rp=(0.7, 0.005), timeseries=data)
  File "/home/wball/pypi/PBjam/pbjam/session.py", line 572, in __init__
    _format_col(vardf, timeseries, 'timeseries')
  File "/home/wball/pypi/PBjam/pbjam/session.py", line 289, in _format_col
    vardf[key] = [_arr_to_lk(x, y, vardf['ID'][0], key)]
  File "/home/wball/.local/lib/python3.9/site-packages/pandas/core/frame.py", line 3163, in __setitem__
    self._set_item(key, value)
  File "/home/wball/.local/lib/python3.9/site-packages/pandas/core/frame.py", line 3239, in _set_item
    value = self._sanitize_column(key, value)
  File "/home/wball/.local/lib/python3.9/site-packages/pandas/core/frame.py", line 3899, in _sanitize_column
    value = maybe_convert_platform(value)
  File "/home/wball/.local/lib/python3.9/site-packages/pandas/core/dtypes/cast.py", line 112, in maybe_convert_platform
    values = construct_1d_object_array_from_listlike(values)
  File "/home/wball/.local/lib/python3.9/site-packages/pandas/core/dtypes/cast.py", line 1638, in construct_1d_object_array_from_listlike
    result[:] = values
  File "/home/wball/.local/lib/python3.9/site-packages/astropy/table/table.py", line 853, in __array__
    raise ValueError('Datatype coercion is not allowed')
ValueError: Datatype coercion is not allowed

I had a brief look around. The problem isn't the conversion of the timeseries into a Lightkurve object but rather when adding this to the vardf dataframe.
I just did a git pull so I'm using the top of master (commit 0c5591a). If any other versions are relevant, they are:

Python 3.9.4
NumPy 1.20.1
Pandas 1.2.0
Astropy 4.2
Lightkurve 2.0.9

@nielsenmb couldn't reproduce this in Python 3.7 and neither can I with Python 3.7.4. I do, however, hit this with Python 3.8.2 and

NumPy 1.20.3
Pandas 1.2.4
Astropy 4.2.1
Lightkurve 2.0.9

Creating the LightCurve object seems to be fine so I had a closer look at why assigning the timeseries that are downloaded via Lightkurve works but passing a custom timeseries doesn't. Mimicking the code in PBjam, I tried this
import numpy as np
import pandas as pd
import lightkurve as lk
import pbjam

n = 1000
data = np.zeros((2,n))
data[0] = np.arange(n, dtype=float)/720
data[1] = np.random.randn(n)

df = pd.DataFrame({'ID': np.array(['test']).reshape((-1,1)).flatten()})
df['timeseries'] = [lk.LightCurve(time=data[0], flux=data[1])]

which is similar to the code path followed for custom timeseries and reproduces the Datatype coercion is not allowed error message.
If I change the last line to this, which tries to be more like the path for downloaded objects (i.e. when you pass a string identifier), it appears to work:
df.at[0, 'timeseries'] = lk.LightCurve(time=data[0], flux=data[1], targetid='test')

vardf[key] = object()
vardf.at[0, key] = _arr_to_lk(x, y, vardf['ID'][0], key)
seems to work on Python 3.7


DOI Resolution User Expectations

In adding data, there's a search interface that has some user experience troubles.
It would be great to set some user expectations in the interface with regard to DOI resolution. I tried entering in DOIs to different datasets in different repositories, and these did not appear as search results.
Ideally, repository owners should do some content negotiation, but for the time being, some warning to users that only certain DataONE repository DOIs will work.

Thanks for the feedback @ekansa! We've changed the lookup code quite a bit and I'll do some poking around to see if I can reproduce this. I know it's been a while-but if you recall which repositories failed I can look there first!

In the linked issue, I added more information to the registration dialog that outlines where data can be registered from to help avoid confusion.


Check if PolynomialBases is a good fit

PolynomialBases could be used instead of Polynomials to generate grid and derivative matrix.

As of now. PolynomialBases is the default and the old way is deprecated and is removed in the future.


Autocomplete: StarCoder prompt leaking into completion

Maybe there is a different way we should be passing this meta infromation?

There is some mention of a <filename> token in this paper: https://arxiv.org/pdf/2305.06161.pdf


Guide: How to scale NKG for Reliability

As a potential user of NKG who operates a large environment
Or as an existing user of NKG who has grown their environment
I want a guide that explains how to scale NKG to reach a consistently higher availability than the default Helm deployment
So that I can continue to use NKG with my higher expectations for availability.
Acceptance

TBD

Blocked by #637

Talked with @bjee19 and we think this would be a good documentation story for him to work on.

Right now, one only needs to scale the number of replicas from our Helm chart to scale for reliability. This will likely change in some capacity once we have data and control plane separation. When we implement that feature, we will produce this kind of documentation.


Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, pleasant staff e check out the contributing guidelines.
Originally posted by @welcome[bot] in https://github.com/github/docs/issues/10390#issuecomment-930181959

Hi irk
Mega


add vitals

add vitals

Sorry, you may only submit PR for NFT colelction. For brc-20, you may just list it on our market directly. @vitas-brc20

Sorry, you may only submit PR for NFT colelction. For brc-20, you may just list it on our market directly. @vitas-brc20

then, how can i add $VITALS Infomation?

It's a brc-20, you needn't submit here. What do you mean the information? May you tell us what you want to do in details? And I suggest you open a ticket in our discord.


Fix nested lists

Description
Fixed a small issue with using nested lists
Types of Changes

[ ] Core
[x] Bugfix
[ ] New feature
[ ] Enhancement/optimization
[ ] Documentation

Issues Fixed or Closed by This PR

Closes #886

Thanks for adding the RELEASE.md file!

Here's a preview of the changelog:

This release fixes an issue when using nested lists, this now works properly:
def get_polygons() -> List[List[float]]:
    return [[2.0, 6.0]]

@strawberry.type
class Query:
    polygons: List[List[float]] = strawberry.field(resolver=get_polygons)

schema = strawberry.Schema(query=Query)

query = "{ polygons }"

result = schema.execute_sync(query, root_value=Query())

Thanks for adding the RELEASE.md file!

Here's a preview of the changelog:

This release fixes an issue when using nested lists, this now works properly:
def get_polygons() -> List[List[float]]:
    return [[2.0, 6.0]]

@strawberry.type
class Query:
    polygons: List[List[float]] = strawberry.field(resolver=get_polygons)

schema = strawberry.Schema(query=Query)

query = "{ polygons }"

result = schema.execute_sync(query, root_value=Query())

Thanks for adding the RELEASE.md file!

Here's a preview of the changelog:

This release fixes an issue when using nested lists, this now works properly:
def get_polygons() -> List[List[float]]:
    return [[2.0, 6.0]]

@strawberry.type
class Query:
    polygons: List[List[float]] = strawberry.field(resolver=get_polygons)

schema = strawberry.Schema(query=Query)

query = "{ polygons }"

result = schema.execute_sync(query, root_value=Query())


Hope to expose the type of fragment

Is your feature request related to a problem? Please describe.
When I'm using https://github.com/Yamashou/gqlgenc, when .graphql contains a fragment, go structure is exposed during generation. But it can't customize client. I tried changing the generator to this library but couldn't find a way to expose the fragment type.
Describe the solution you'd like
Let the fragment export by default, or set it via the configuration.

Thanks for your question!  There's a bit more documentation about how genqlient handles fragments in the FAQ.  If that doesn't help answer your question, could you give more details about what you're trying to do?  For example an example query and a snippet of the code you want to write but can't would be very helpful to understand what you're getting at.

@benjaminjkraft I'm sorry for my mistake. When the fragment starts with an uppercase letter it would export by default.
Thanks for your great work. 👍


Add support for update server to respond with an HTTP redirect instead of JSON

Instead of requiring an update server to respond with a specific JSON schema, what if we also allowed a server to respond with an HTTP 301, 302, 303 or 307 redirect pointing to the new release URL? This would allow for third-party distribution services, such as my own, to be more easily integrated with Squirrel, without the third-party service needing to add a compatibility layer for Squirrel.Mac (i.e. at minimum, a url property in the response payload.)
Since this would be in addition to the 200 JSON response, this should be a backwards-compatible change.
What do you all think?
p.s. I'd love to sponsor/donate to Squirrel on behalf of Keygen. Let me know if you provide options for that. 🙂

Given that this is 20 years old well established web tech, I thought this would Just Work (tm.)

Please implement this!


[terra-menu] New headerTitle prop

Summary
New headerTitle prop added.
Additional Details
Menu now takes an additional prop headerTitle. The title is set to first tier menu page. This new header title is only introduced to menus which have at least one sub-menu.
fixes #474
PS: partially fixes the mentioned issue.

The default header can be seen in this test example.

Tests are still failing in terra-collapsible-menu-view and terra-notification-dialog.
Visually, this looks OK.  I'm not removing the block or giving +1 yet. Accessibility input from @neilpfeiffer and @benbcai need to weigh in before final approval.

Please generate/update fusion theme screenshots as well.

Please generate/update fusion theme screenshots as well.

Sure. But this is still 'Work In Progress'. I am waiting to know if UX requires any style modifications or provide some style changes to the header. Will update the screenshots once UX approves the new header styles.

A few of the screenshots without the new title have changed, do we know what is causing that?

A few of the screenshots without the new title have changed, do we know what is causing that?

I missed a condition check and this was generating a empty header <DIV>
Updated here 925d3978aa5c7b49ac4a66c4fd06ce07761016b9

Tests are still failing in terra-collapsible-menu-view and terra-notification-dialog.

Fix for terra-collapsible-menu-view and terra-notification-dialog tests 925d3978aa5c7b49ac4a66c4fd06ce07761016b9

@lokesh-0813  Is this PR ready for a full review? I notice it has been out for a while, but it's still in draft mode.

@lokesh-0813 Is this PR ready for a full review? I notice it has been out for a while, but it's still in draft mode.

@emilyrohrbough , I was waiting for @neilpfeiffer to pitch in. I had assumed there would be more changes to make. But I think most of it is covered and will be moving it to 'ready for review'.

Yes that's because fusion-theme has a fixed-height for headerTitle.

We need to fix that then, please.

Updated here ef3239cd78e5d657c848f92d318f790c6a31f47a

Really close. In the test, there are some padding issues in the nested menu.

Updated here 99331a764be4076d201c71839dccffec508acd52

Wrapped header in the Fusion theme is not working in IE 11.

@lokesh-0813 with the force push is this ready to review again?

@lokesh-0813 with the force push is this ready to review again?

@ryanthemanuel Apparently the word-break styles are not getting applied in IE.
@jmsv6d I was wondering if you would have any thoughts here.
When building header for menus, there is a scenario where we use nested Arrange.
Here and then here. I am suspecting this could be causing the words not to break in IE(works fine in other browsers).
So i removed the Arrange here and directly returned the h1 element, and it seem to work fine. Although this cannot be done for nested-menu's since we need fitStart for back-icon and fill to fill the text content.

@lokesh-0813 I'm not sure why the word-break style isn't applying appropriately, but the Arrange element you referenced should definitely be removed regardless as it doesn't provide any value if you're only using the fill prop. I wouldn't be opposed to removing the other Arrange as well and just using flex-box styling.


Clean code and add some tests

This is a simple PR that cleans some code and added some missing tests for handwritten code.

@swift-ci Please test

@ahoppen did rebase with latest changes on main


Convert ParaTest to use PSR-4 autoloading

As the next version of ParaTest contain backwards incompatible changes, I'd humbly like to suggest ParaTest use this rare opportunity to move from PSR-0 autoloading to PSR-4.
From PHP-FIG:

Deprecated - As of 2014-10-21 PSR-0 has been marked as deprecated. PSR-4 is now recommended as an alternative.

From composer:

PSR-4 is the recommended way since it offers greater ease of use (no need to regenerate the autoloader when you add classes).

This changes alters composer and the directory structure to use composer's PSR-4 autoloading.
Also allows for a shallower directory structure.
The directory test/functional continues to use PSR-0. This directory contained many non-namespaced files so converting did not initially work without additional changes. If you'd like, I could include those changes as part of this work, but as tests are not a public API, I see this as less pressing. If it were to happen at a later date, it would have no backwards incompatibility concerns.

The directory test/functional continues to use PSR-0. This directory contained many non-namespaced files so converting did not initially work without additional changes. If you'd like, I could include those changes as part of this work, but as tests are not a public API, I see this as less pressing. If it were to happen at a later date, it would have no backwards incompatibility concerns.

Feel free to add another PR. Not using namespaces at all is the major issue of that folder then ^^
And thanks for the contribution


chore: add circleci namespace to protected namespace

The type of this PR is: chore

Description

Small PR to add the newly created circleci namespace (PR) to the protected_namespaces list in the kubernetes_cleanup_namespaces job.
Though perhaps this is no longer needed if we plan to update the job to respect tags, as started in this  hokusai PR?

Though perhaps this is no longer needed if we plan to update the job to respect tags, as started in this hokusai https://github.com/artsy/hokusai/pull/370?

Yeah, I plan to update this job to parse k8s namespace tags. This PR is required until that happens, thanks!


Test building package during CI

What does this PR do?

Fixing #352
Before submitting

[x] Was this discussed/approved via a GitHub issue? Please add a link to it if that's the case.
[x] I have commented my code, particularly in hard-to-understand areas.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.03%) to 80.67%

Totals

Change from base Build<PHONE_NUMBER>:
-0.03%

Covered Lines:
7011

Relevant Lines:
8691

💛  - Coveralls


Automated cherry pick of #3213: fix: aliyun bucket sync cancel local limit

Cherry pick of #3213 on release/2.11.
#3213: fix: aliyun bucket sync cancel local limit

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.11@01976cd). Click here to learn what that means.
The diff coverage is 0%.

@@              Coverage Diff               @@
##             release/2.11   #3214   +/-   ##
==============================================
  Coverage                ?   7.13%
==============================================
  Files                   ?     476
  Lines                   ?   77247
  Branches                ?       0
==============================================
  Hits                    ?    5514
  Misses                  ?   71270
  Partials                ?     463

Flag
Coverage Δ

#aFlag
7.13% <0%> (?)

Impacted Files
Coverage Δ

pkg/cloudprovider/objectstore.go
3.18% <ø> (ø)

pkg/compute/models/buckets.go
1.35% <0%> (ø)

Continue to review full report at Codecov.

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

/approve
/lgtm


i encountered issue in 0.6 version

when i converting my audio file this message appeared on last step/process

Thanks for the report. Do you receive the warning always, or only if you have selected "translate with deepl"?

This is the same error I posted about yesterday and I get the error always (without using 'translate with deepl').

It seems to be hanging on line 48. Sometimes it downloads 1 or 2 required files while other times it just hangs. It doesn't time out either I had it hanging for over 6 hours yesterday.

Thanks for the report. Do you receive the warning always, or only if you have selected "translate with deepl"?

no i didnt select translate with deepl I always do what I always do when translating but this latest version i got this from yesterday.

Thanks.
It seems that the warning that you receive is not the cause of the problem, but the cuda incompatibility after google upgraded colab.
https://github.com/googlecolab/colabtools/issues/4214
It seems that the fallback method is not working any longer in colab. I will need to find a workaround.

Thanks.
It seems that the warning that you receive is not the cause of the problem, but the cuda incompatibility after google upgraded colab.
googlecolab/colabtools#4214
It seems that the fallback method is not working any longer in colab. I will need to find a workaround.

thanks sir i hope it will fix soon :-)

guys

follow this tutorial for temporary it works for me now.

For now version 1.0 BETA is a quick workaround. Please check it out to see that it works in your env.
Note: the speed is not as fast as 0.6. We have to wait for the root cause problem to be solved before going back to the 2x speed.

1.0 beta works, but is very slow. Took about 30 minutes to do one file, while in the past it took about 5-6 minutes.   I am guessing is due to the lack of GPU?
The work around using the .6i with the fallback runtime describe above runs great though.

Both 0.6 and beta 1.0 use GPU. The difference is in the quantisation (CTranslate2) method. The beta release is using the standard Whisper and standard silero VAD. The 0.6 uses fast whisper with quantised and batch processing of model and VAD.

It's working fine for me too even if it is slower.

The work around using the .6i with the fallback runtime describe above runs great though.
This will only be supported until the end of the month though so you'll have no choice but to use the current version.

Version 0.7 was just released. This release has the fix for the break after the colab upgrade. No need for the fallback runtime in this release.

Thanks for the work.
btw I noticed a spelling mistake in the notes at the bottom:
0.7: fixing the error caused bu Colab upgrade
should be by not bu

The fix is in version 0.7.
Please check that one out --should work fine.
On Wed, Jan 3, 2024 at 10:28 AM wangbuu0910 @.***>
wrote:

when i converting my audio file this message appeared on last step/process
Untitled.png (view on web)
https://github.com/meizhong986/WhisperJAV/assets/155535884/e4de14e3-0f57-4dc8-be49-5193790b04e4
—
Reply to this email directly, view it on GitHub
https://github.com/meizhong986/WhisperJAV/issues/3, or unsubscribe
https://github.com/notifications/unsubscribe-auth/BDME2BVGWSFJ3GVUSP5YMSTYMUXFFAVCNFSM6AAAAABBLG5VFKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGA3DGNZRG44DONI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


adding an explicit cast for the conversion from int to useconds_t in …

…TimeHelpers::SleepMS.
This is to address:
GSL/tests/unittest-cpp/UnitTest++/Posix/TimeHelpers.cpp:30:15: warning: implicit conversion changes
signedness: 'int' to 'useconds_t' (aka 'unsigned int') [-Wsign-conversion]
usleep(ms * 1000);
~~~~~~ ~^~~~
1 warning generated.

I'm going to include this as is. Really should change the method signature to be unsigned instead -- don't know who is sleeping for negative time -- but this is good for now.


Reload map when navigation is coming from back/forward

closes #347

that works in chrome on my mac, but somehow not in safari

that works in chrome on my mac, but somehow not in safari

Can't reproduce this on iPad Pro using Safari, so guess I'll have to buy a Macbook to fix this bug. :D
I changed it to window.location = window.location, maybe that helps? Incredibly unlikely, but this is already a niche bug.


Philips Smart Wi-Fi Bulbs Don't Work Correctly

Only the On and off Functions work. Dimming and Color changing and active lighting does not work at all.
I have tested this on these three bulbs listed below, they are all new. They support Matter which does allow for dimming and color changing, however the matter connection sucks and always disconnects. This homebridge plugin is solid and never disconnects.
So right now the only options are Control more features, but have disconnects all the time, or have limited control but be solid.
https://www.homedepot.com/p/Philips-60-Watt-Equivalent-A19-Smart-Wi-Fi-LED-Vintage-Edison-Tuneable-White-Light-Bulb-Powered-by-WiZ-with-Bluetooth-1-Pack-567164/316147062
https://www.homedepot.com/p/Philips-40-Watt-Equivalent-A15-Smart-Wi-Fi-LED-Tuneable-White-Light-Bulb-Powered-by-WiZ-with-Bluetooth-1-Pack-567222/316146275
https://www.homedepot.com/p/Philips-150-Watt-Equivalent-A23-LED-Dimmable-Smart-WiFi-Connected-LED-Light-Bulb-Color-and-Tunable-White-2200K-6500K-1-Pack-578716/320687469
If there is anything you can do to help that would be amazing!

I unfortunately don't have these bulbs to test with. Are there any logs that you could share that might help?

@Vic-Firth
Those bulbs have support for Matter and work great in Apple Home under Matter.
You don't need the Homebridge plugin.

Thank you so much for replying. I hope these will help. here are some logs. When I change a setting on my phone on the home app, the home app shows the setting changed, however the physical light bulb will not change at all. This is true for both RGB and Tuneable White.
[2/27/2024, 2:24:07 PM] [WizSmarthome] Initializing WizSmarthome platform...
[2/27/2024, 2:24:07 PM] [WizSmarthome] [Refresh] Pings are off
[2/27/2024, 2:24:07 PM] [WizSmarthome] Loading accessory from cache: Wiz Tunable White Bulb d8a011e4c70f
[2/27/2024, 2:24:07 PM] [WizSmarthome] Loading accessory from cache: Wiz Tunable White Bulb d8a011e449e3
[2/27/2024, 2:24:07 PM] [WizSmarthome] Loading accessory from cache: Wiz Tunable White Bulb d8a011e8060b
[2/27/2024, 2:24:07 PM] [WizSmarthome] Loading accessory from cache: Wiz Tunable White Bulb d8a011e536b9
[2/27/2024, 2:24:07 PM] [WizSmarthome] Loading accessory from cache: Wiz Tunable White Bulb d8a011e6d6bb
[2/27/2024, 2:24:07 PM] [WizSmarthome] Loading accessory from cache: Wiz Tunable White Bulb d8a011e3df4b
[2/27/2024, 2:24:07 PM] [WizSmarthome] Loading accessory from cache: Wiz Tunable White Bulb d8a011e84221
[2/27/2024, 2:24:07 PM] [WizSmarthome] Loading accessory from cache: Wiz Tunable White Bulb d8a011e45695
[2/27/2024, 2:24:07 PM] [WizSmarthome] Loading accessory from cache: Wiz Tunable White Bulb d8a011e41833
[2/27/2024, 2:24:07 PM] [WizSmarthome] Loading accessory from cache: Wiz RGB Bulb 444f8eaa6ade
[2/27/2024, 2:24:07 PM] [WizSmarthome] [Socket] Setting up socket on <IP_ADDRESS>:38900
[2/27/2024, 2:24:07 PM] [WizSmarthome] [Discovery] Sending discovery UDP broadcast to <IP_ADDRESS>:38899
[2/27/2024, 2:24:07 PM] Homebridge v1.7.0 (HAP v0.11.1) (Homebridge 8D4B) is running on port 51847.
[2/27/2024, 2:24:08 PM] [WizSmarthome] Updating accessory: Wiz RGB Bulb 444f8eaa6ade
[2/27/2024, 2:24:08 PM] [WizSmarthome] Updating accessory: Wiz Tunable White Bulb d8a011e84221
[2/27/2024, 2:24:08 PM] [WizSmarthome] Updating accessory: Wiz Tunable White Bulb d8a011e449e3
[2/27/2024, 2:24:08 PM] [WizSmarthome] Updating accessory: Wiz RGB Bulb 444f8eaa6ade
[2/27/2024, 2:24:08 PM] [WizSmarthome] Updating accessory: Wiz Tunable White Bulb d8a011e84221
[2/27/2024, 2:24:08 PM] [WizSmarthome] Updating accessory: Wiz Tunable White Bulb d8a011e45695
[2/27/2024, 2:24:08 PM] [WizSmarthome] Updating accessory: Wiz Tunable White Bulb d8a011e45695
[2/27/2024, 2:24:08 PM] [WizSmarthome] Updating accessory: Wiz Tunable White Bulb d8a011e4c70f
[2/27/2024, 2:24:08 PM] [WizSmarthome] Updating accessory: Wiz Tunable White Bulb d8a011e449e3
[2/27/2024, 2:24:08 PM] [WizSmarthome] Updating accessory: Wiz Tunable White Bulb d8a011e4c70f
[2/27/2024, 2:24:08 PM] [WizSmarthome] Updating accessory: Wiz Tunable White Bulb d8a011e41833
[2/27/2024, 2:24:08 PM] [WizSmarthome] Updating accessory: Wiz Tunable White Bulb d8a011e3df4b
[2/27/2024, 2:24:08 PM] [WizSmarthome] Updating accessory: Wiz Tunable White Bulb d8a011e41833
[2/27/2024, 2:24:08 PM] [WizSmarthome] Updating accessory: Wiz Tunable White Bulb d8a011e6d6bb
[2/27/2024, 2:24:08 PM] [WizSmarthome] Updating accessory: Wiz Tunable White Bulb d8a011e6d6bb
[2/27/2024, 2:24:08 PM] [WizSmarthome] Updating accessory: Wiz Tunable White Bulb d8a011e3df4b
[2/27/2024, 2:35:40 PM] [WizSmarthome] Initializing WizSmarthome platform...
[2/27/2024, 2:35:40 PM] [WizSmarthome] [Refresh] Pings are off
[2/27/2024, 2:35:40 PM] [WizSmarthome] Loading accessory from cache: Wiz Tunable White Bulb d8a011e4c70f
[2/27/2024, 2:35:40 PM] [WizSmarthome] Loading accessory from cache: Wiz Tunable White Bulb d8a011e449e3
[2/27/2024, 2:35:40 PM] [WizSmarthome] Loading accessory from cache: Wiz Tunable White Bulb d8a011e8060b
[2/27/2024, 2:35:40 PM] [WizSmarthome] Loading accessory from cache: Wiz Tunable White Bulb d8a011e536b9
[2/27/2024, 2:35:40 PM] [WizSmarthome] Loading accessory from cache: Wiz Tunable White Bulb d8a011e6d6bb
[2/27/2024, 2:35:40 PM] [WizSmarthome] Loading accessory from cache: Wiz Tunable White Bulb d8a011e3df4b
[2/27/2024, 2:35:40 PM] [WizSmarthome] Loading accessory from cache: Wiz Tunable White Bulb d8a011e84221
[2/27/2024, 2:35:40 PM] [WizSmarthome] Loading accessory from cache: Wiz Tunable White Bulb d8a011e45695
[2/27/2024, 2:35:40 PM] [WizSmarthome] Loading accessory from cache: Wiz Tunable White Bulb d8a011e41833
[2/27/2024, 2:35:40 PM] [WizSmarthome] Loading accessory from cache: Wiz RGB Bulb 444f8eaa6ade
[2/27/2024, 2:35:40 PM] [WizSmarthome] [Socket] Setting up socket on <IP_ADDRESS>:38900
[2/27/2024, 2:35:40 PM] [WizSmarthome] [Discovery] Sending discovery UDP broadcast to <IP_ADDRESS>:38899
[2/27/2024, 2:35:40 PM] Homebridge v1.7.0 (HAP v0.11.1) (Homebridge 8D4B) is running on port 51847.
[2/27/2024, 2:35:40 PM] [WizSmarthome] Updating accessory: Wiz Tunable White Bulb d8a011e45695
[2/27/2024, 2:35:40 PM] [WizSmarthome] Updating accessory: Wiz RGB Bulb 444f8eaa6ade
[2/27/2024, 2:35:40 PM] [WizSmarthome] Updating accessory: Wiz Tunable White Bulb d8a011e41833
[2/27/2024, 2:35:40 PM] [WizSmarthome] Updating accessory: Wiz Tunable White Bulb d8a011e45695
[2/27/2024, 2:35:40 PM] [WizSmarthome] Updating accessory: Wiz Tunable White Bulb d8a011e84221
[2/27/2024, 2:35:40 PM] [WizSmarthome] Updating accessory: Wiz Tunable White Bulb d8a011e84221
[2/27/2024, 2:35:40 PM] [WizSmarthome] Updating accessory: Wiz Tunable White Bulb d8a011e536b9
[2/27/2024, 2:35:40 PM] [WizSmarthome] Updating accessory: Wiz RGB Bulb 444f8eaa6ade
[2/27/2024, 2:35:40 PM] [WizSmarthome] Updating accessory: Wiz Tunable White Bulb d8a011e41833
[2/27/2024, 2:35:40 PM] [WizSmarthome] Updating accessory: Wiz Tunable White Bulb d8a011e4c70f
[2/27/2024, 2:35:40 PM] [WizSmarthome] Updating accessory: Wiz Tunable White Bulb d8a011e6d6bb
[2/27/2024, 2:35:40 PM] [WizSmarthome] Updating accessory: Wiz Tunable White Bulb d8a011e449e3
[2/27/2024, 2:35:40 PM] [WizSmarthome] Updating accessory: Wiz Tunable White Bulb d8a011e536b9
[2/27/2024, 2:35:40 PM] [WizSmarthome] Updating accessory: Wiz Tunable White Bulb d8a011e3df4b
[2/27/2024, 2:35:40 PM] [WizSmarthome] Updating accessory: Wiz Tunable White Bulb d8a011e6d6bb
[2/27/2024, 2:35:40 PM] [WizSmarthome] Updating accessory: Wiz Tunable White Bulb d8a011e4c70f
[2/27/2024, 2:35:40 PM] [WizSmarthome] Updating accessory: Wiz Tunable White Bulb d8a011e3df4b
[2/27/2024, 2:35:40 PM] [WizSmarthome] Updating accessory: Wiz Tunable White Bulb d8a011e449e3
[2/27/2024, 2:35:41 PM] [WizSmarthome] Updating accessory: Wiz Tunable White Bulb d8a011e8060b
[2/27/2024, 2:35:41 PM] [WizSmarthome] Updating accessory: Wiz Tunable White Bulb d8a011e8060b
[2/27/2024, 6:40:36 PM] [WizSmarthome] Initializing WizSmarthome platform...
[2/27/2024, 6:40:36 PM] [WizSmarthome] [Refresh] Pings are off
[2/27/2024, 6:40:36 PM] [WizSmarthome] Loading accessory from cache: Wiz Tunable White Bulb d8a011e4c70f
[2/27/2024, 6:40:36 PM] [WizSmarthome] Initializing device [object Object]...
[2/27/2024, 6:40:36 PM] [WizSmarthome] [Adaptive Lighting] Initializing adaptive lighting for d8a011e4c70f
[2/27/2024, 6:40:36 PM] [WizSmarthome] Loading accessory from cache: Wiz Tunable White Bulb d8a011e449e3
[2/27/2024, 6:40:36 PM] [WizSmarthome] Initializing device [object Object]...
[2/27/2024, 6:40:36 PM] [WizSmarthome] [Adaptive Lighting] Initializing adaptive lighting for d8a011e449e3
[2/27/2024, 6:40:36 PM] [WizSmarthome] Loading accessory from cache: Wiz Tunable White Bulb d8a011e8060b
[2/27/2024, 6:40:36 PM] [WizSmarthome] Initializing device [object Object]...
[2/27/2024, 6:40:36 PM] [WizSmarthome] [Adaptive Lighting] Initializing adaptive lighting for d8a011e8060b
[2/27/2024, 6:40:36 PM] [WizSmarthome] Loading accessory from cache: Wiz Tunable White Bulb d8a011e536b9
[2/27/2024, 6:40:36 PM] [WizSmarthome] Initializing device [object Object]...
[2/27/2024, 6:40:36 PM] [WizSmarthome] [Adaptive Lighting] Initializing adaptive lighting for d8a011e536b9
[2/27/2024, 6:40:36 PM] [WizSmarthome] Loading accessory from cache: Wiz Tunable White Bulb d8a011e6d6bb
[2/27/2024, 6:40:36 PM] [WizSmarthome] Initializing device [object Object]...
[2/27/2024, 6:40:36 PM] [WizSmarthome] [Adaptive Lighting] Initializing adaptive lighting for d8a011e6d6bb
[2/27/2024, 6:40:36 PM] [WizSmarthome] Loading accessory from cache: Wiz Tunable White Bulb d8a011e3df4b
[2/27/2024, 6:40:36 PM] [WizSmarthome] Initializing device [object Object]...
[2/27/2024, 6:40:36 PM] [WizSmarthome] [Adaptive Lighting] Initializing adaptive lighting for d8a011e3df4b
[2/27/2024, 6:40:36 PM] [WizSmarthome] Loading accessory from cache: Wiz Tunable White Bulb d8a011e84221
[2/27/2024, 6:40:36 PM] [WizSmarthome] Initializing device [object Object]...
[2/27/2024, 6:40:36 PM] [WizSmarthome] [Adaptive Lighting] Initializing adaptive lighting for d8a011e84221
[2/27/2024, 6:40:36 PM] [WizSmarthome] Loading accessory from cache: Wiz Tunable White Bulb d8a011e45695
[2/27/2024, 6:40:36 PM] [WizSmarthome] Initializing device [object Object]...
[2/27/2024, 6:40:36 PM] [WizSmarthome] [Adaptive Lighting] Initializing adaptive lighting for d8a011e45695
[2/27/2024, 6:40:36 PM] [WizSmarthome] Loading accessory from cache: Wiz Tunable White Bulb d8a011e41833
[2/27/2024, 6:40:36 PM] [WizSmarthome] Initializing device [object Object]...
[2/27/2024, 6:40:36 PM] [WizSmarthome] [Adaptive Lighting] Initializing adaptive lighting for d8a011e41833
[2/27/2024, 6:40:36 PM] [WizSmarthome] Loading accessory from cache: Wiz RGB Bulb 444f8eaa6ade
[2/27/2024, 6:40:36 PM] [WizSmarthome] Initializing device [object Object]...
[2/27/2024, 6:40:36 PM] [WizSmarthome] [Adaptive Lighting] Initializing adaptive lighting for 444f8eaa6ade
[2/27/2024, 6:40:36 PM] [WizSmarthome] Executed didFinishLaunching callback
[2/27/2024, 6:40:36 PM] [WizSmarthome] [Socket] Setting up socket on <IP_ADDRESS>:38900
[2/27/2024, 6:40:36 PM] [WizSmarthome] [Socket] Socket Bound: UDP IPv4 listening on <IP_ADDRESS>:38900
[2/27/2024, 6:40:36 PM] [WizSmarthome] [Discovery] Initiating discovery handlers
[2/27/2024, 6:40:36 PM] [WizSmarthome] [Discovery] Sending discovery UDP broadcast to <IP_ADDRESS>:38899
[2/27/2024, 6:40:36 PM] Homebridge v1.7.0 (HAP v0.11.1) (Homebridge 8D4B) is running on port 51847.

You don't need the Homebridge plugin.

Thank you for the info, but as you can see in my original post, they do not work great for me, and I am not the only one.
Other people have also experienced similar problems.
https://www.reddit.com/r/wiz/comments/1akc2y0/matter_lights_go_offline_every_night/
Maybe you have a different experience than me. At first matter started off fine, but then after a couple of weeks it started always disconnecting, and I had to constantly manually turn the switches back on to reset the connection. I tested this side by side with the homebridge connection, and I have never once lost connection through homebridge.

@Vic-Firth
I understand your frustration with Matter disconnecting, it was frustrating for me at first too. I now have 38 WiZ Matter bulbs on my network. And only rarely do I have a bulb lose the Matter connection.
In my experience, Matter unfortunately does require a stronger Wi-Fi signal connection. The Matter connection is established over IPv6 and the routing is handled by the Apple Matter controller device, not your regular router. This is why you can lose the Matter connection but still have IPv4 control over the bulb.
The solution is to beef-up the signal between the bulb and the Apple Matter controller.
In my case, I purchased a tp-link DECO mesh network router system to strengthen my whole network. Even after that I still had to use a tp-link range extender to strengthen the signal to a bulb on the outside of me garage.
Also, when you do have a lost connection, don't be quick on the draw to reset the connection through a power cycle. The issue is not always the bulb but can be the Apple routing. The Apple Matter router will either self heal and refine the connection or need its own reset. So, it's not always the bulb.
Work on your signal strength and give Matter a try again.

@MoTechnicalities
This is the router that I have which is 4ft away from one of the bulbs that disconnects.
https://www.bhphotovideo.com/c/product/1622915-REG/asus_rt_ax68u_ax2700_dual_band.html
I have a homepod mini that is about 6ft away from one of the bulbs that disconnects.
I also have the latest apple tv 4k 128 gb that is about 4 ft away from another bulb that disconnects.
I would have thought that would have been close enough in range, but I guess not. Either way, its kind of a hard sell, I don't really want to spend another $150-$200 bucks when everything else including all of my other matter devices already works and the Homebridge connection is rock solid.
Thank you for the info though, I appreciate it.

@MoTechnicalities
Thank you for all of the info.
I only have 1 regular router and it would be a big deal to move it. I have a cable connection and to move it to the middle of things in the house would be to move the coaxial able which is coming from under the house, maybe thats easy for you, but not for me. Additionally the computer that runs homebridge is connected to my router in its current location. If I moved it, I would then have to figure out a way to run the ethernet between rooms, which now makes the problem even bigger and more costly.
Homebridge works great at turning the lights on and off. It's not worth it to go through all the trouble to try and get the Matter connection working better just to be able to change colors and dim through the apple home app. I would like it but its hard to justify the cost and time.
I just wanted to see if the dev could fix the app he made to work with the new phillips branded bulbs, thats it, thats all.
I am very grateful that this Wiz plugin works to turn on and off the lights and that it was created, and it was so nice of the developer to respond and at least ask for code to try and help.

I think I have some of those same bulbs. I run the ones that will run through matter, through matter. I get the few I have that don't into the home app via homebridge.
For what it's worth, through siri/home.app I can turn the bulbs off and on. I can dim them by saying set dining room light to 10%. And I can get them to change color like red, blue, green, orange, purple, but not change the white setting from warm to cool.

@Vic-Firth
I opened a complaint issue with WiZ using their App. I agree that they need a firmware improvement to reestablish a Matter when lost if they still have connectivity to the network. You should open a complaint as well. Maybe somewhere dorm the road there will be a solution.


fix(console): warning for actions

Closes #6317
Definition of Ready

[ ] I am happy with the code
[ ] Short description of the feature/issue is added in the pr description
[ ] PR is linked to the corresponding user story
[ ] Acceptance criteria are met
[ ] All open todos and follow ups are defined in a new ticket and justified
[ ] Deviations from the acceptance criteria and design are agreed with the PO and documented.
[ ] No debug or dead code
[ ] My code has no repetitions
[ ] Critical parts are tested automatically
[ ] Where possible E2E tests are implemented
[ ] Documentation/examples are up-to-date
[ ] All non-functional requirements are met
[ ] Functionality of the acceptance criteria is checked manually on the dev system.

@hifabienne can you look at the texts it they are fine for you?.. I modified them to be clearer


Generating multiple sizes only uses the last size for the entire set

Hey, another one from me ;)
I discovered a serious bug that actually completely breaks the source set generation. If you generate multiple images by chaining multiple widths together (e.g. import srcsetAvif from '../example.jpg?w=500;700;900;1200&avif&srcset', as per your example), it actually only applies the last width on every image in the whole set!
To reproduce:

Clone this repo and cd into examples/vite-simple
Edit main.js and add ridiculously low widths as the last params:

// ...
import srcsetAvif from '../example.jpg?w=500;700;900;1200;20&avif&srcset'
import srcsetWebp from '../example.jpg?w=500;700;900;1200;20&webp&srcset'
// ...

yarn && yarn dev
Open the page in your browser, open the devtools and reload
In your network tab, you'll now see the exact file that was loaded - for me it had an ID of e78e253f7e1877238273f8472026215d31af4221 (you guessed it: it's only 20px wide 😉)
When inspecting srcset of the the image, however, you'll notice that the loaded ID was supposed to be 1200px wide (depending on your viewport, of couse): /@imagetools/e78e253f7e1877238273f8472026215d31af4221 1200w,. The one with 20px has an entirely different ID.

So, even though the 20px wide image was not selected by the browser, it still only received a 20px wide one. It looks like it's always the last argument that decides the size of all the images in the set. All of the metadata is still generated according to the parameters. Each URL is just pointing to an image the size of the last parameter.

This is really bad 😟
This only appears during development right? So when you do yarn build all the right images get generated?

Oh, I haven't even thought about testing that. And yeah, you're right, it works in production, so it isn't that terrible after all.

This only appears during development right? So when you do yarn build all the right images get generated?

oh god dammit... I've been cracking my head trying to figure this one out...
yeah.... can confirm, at least on my testing, the switch happens alright once deployed, just during dev that it only shows the last size

@JonasKruckenberg I just hit this one too. The problem seems to be in the vite plugin and the middleware added in configureServer. To debug I looked for use of generatedImages and added the following:
// before generatedImage.set
console.log("set image", id, imagetoolsCore.getMetadata(image, 'width'))

// after generatedImage.get (in middleware)
console.log("get image", id, imagetoolsCore.getMetadata(image, 'width'))

In the logs...
set image 6269821afe096f8aea2f2ba455cddea6fa0b734a 500
set image cb68b63cfb6eadc77da1ba1b4f5866595fe545e2 700
get image 6269821afe096f8aea2f2ba455cddea6fa0b734a 700 <--- ooops!
get image cb68b63cfb6eadc77da1ba1b4f5866595fe545e2 700

Something is being reused somewhere...? I then modified this line:
//             generatedImages.set(id, image); // from
                generatedImages.set(id, image.clone()); // to

New log output:
set image 6269821afe096f8aea2f2ba455cddea6fa0b734a 500
set image cb68b63cfb6eadc77da1ba1b4f5866595fe545e2 700
get image 6269821afe096f8aea2f2ba455cddea6fa0b734a undefined
get image cb68b63cfb6eadc77da1ba1b4f5866595fe545e2 undefined

... and images in the site are the correct size 🎉.

I guess it is because of this line:
            const img = imagetoolsCore.loadImage(decodeURIComponent(srcURL.pathname));

... this img is passed to imagetoolsCore.applyTransforms and returned, so same image is put in the Set.

Good catch! The sharp instance is mutable indeed and so will be changed by subsequent iterations, cloning should solve this!

Hey, this issue seems to have been fixed by the PR #218 , but was rolled back by this commit f6cec968782c13b1b9d35648d11aa09822ce2d05 .
Is there a reason for that?

Oups, must have been lost in the merges somehow!

Fixed and published please upgrade to<EMAIL_ADDRESS>


lottie: support resizing precomps

Consider
{
    "v": "5.8.1",
    "fr": 60,
    "ip": 0,
    "op": 1,
    "w": 1024,
    "h": 1024,
    "nm": "emoji_baseball",
    "ddd": 0,
    "assets": [
        {
            "id": "myprecomp",
            "layers": [
                {
                    "ty": 4,
                    "st": 0,
                    "ip": 0,
                    "op": 1,
                    "ks": {
                        "a": {
                            "a": 0,
                            "k": [
                                0,
                                0
                            ]
                        },
                        "p": {
                            "a": 0,
                            "k": [
                                0,
                                0
                            ]
                        },
                        "s": {
                            "a": 0,
                            "k": [
                                100,
                                100
                            ]
                        },
                        "r": {
                            "a": 0,
                            "k": 0
                        },
                        "o": {
                            "a": 0,
                            "k": 100
                        }
                    },
                    "shapes": [
                        {
                            "ty": "rc",
                            "s": {
                                "a": 0,
                                "k": [
                                    1024,
                                    1024
                                ]
                            },
                            "p": {
                                "a": 0,
                                "k": [
                                    512,
                                    512
                                ]
                            },
                            "r": {
                                "a": 0,
                                "k": 0
                            }
                        },
                        {
                            "ty": "fl",
                            "c": {
                                "a": 0,
                                "k": [
                                    0,
                                    1,
                                    0
                                ]
                            },
                            "o": {
                                "a": 0,
                                "k": 100
                            }
                        }
                    ]
                }
            ]
        }
    ],
    "layers": [
        {
            "ty": 0,
            "st": 0,
            "ip": 0,
            "op": 1,
            "ks": {
                "a": {
                    "a": 0,
                    "k": [
                        0,
                        0
                    ]
                },
                "p": {
                    "a": 0,
                    "k": [
                        0,
                        0
                    ]
                },
                "s": {
                    "a": 0,
                    "k": [
                        100,
                        100
                    ]
                },
                "r": {
                    "a": 0,
                    "k": 0
                },
                "o": {
                    "a": 0,
                    "k": 100
                }
            },
            "refId": "myprecomp",
            "w": 256,
            "h": 256
        }
    ]
}

Here, our precomposition layer renders the precomposition myprecomp at a size of 256x256. This means we need to encode the precomposition, then scale it down to a size of 256x256. This proves difficult because we scale by multipliers, not absolute sizes, and we don't know the size of the precomposition, neither before nor after encoding it as a scene. It is not clear if we need the bounding box of the control points (which would be easy), or the bounding box of the rendered scene, which would be difficult.

I was mistaken, the width and height of the precomp layer aren't for scaling, but for clipping. This is more evident with an ellipse than a rectangle...


Rebroadcast message pruning prunes too much on skip round

The rebroadcast mechanism keeps hold of the messages from the latest 2 rounds for rebroadcasting purposes should the relevant timeouts expire. Whenever there is a message broadcast the broadcast state is updated to: 1) include the new broadcast, and 2) prune messages that have become too to rebroadcast (i.e. belong to rounds before the latest 2).
The issue is that pruning for rounds is determined relative to the latest broadcasted message round. This means if the instance skips from round 0 to round 42 the pruning would remove all messages from rounds 40, 39, 38, and finally 0. This leaves the broadcast state to only contain the latest round of broadcast messages (i.e. 42) caused by skip round.
Fix:
Determine redundant rounds based on the length of broadcast state instead of the broadcasted message round. Add tests to reproduce and confirm the fix.

OK having discussed this with the team and reviewed the pseudocode in the FIP, the implementation as is:

there is no situation where messages from older than 2 rounds would help lacking nodes catch up.
is consistent with the FIP:

Note lines 84 and 85, where the round is relative to the message round. Meaning a node that have skipped to future rounds may have never seen those messages and therefore cannot rebroadcast them.
67:  reBroadcast(msg):
68:    own_msgs = own_msgs ∪ {msg}
69:    BEBroadcast(msg)
70:    trigger(timeout_rebroadcast)
71:    step ← msg.step
72:    upon timeout_rebroadcast expires:
73:      if step = msg.step AND msg.round = round AND msg.instance = instance
           // Stuck, need to rebroadcast
74:        switch (msg.step) {
75:          case DECIDE:
76:            BEBroadcast(m ∈ own_msgs: m.round=0 AND m.type=DECIDE) // only rebroadcast DECIDE
77:            break  // Exit, no cascading
78:          case COMMIT:
79:            BEBroadcast(m ∈ own_msgs: m.round=msg.round AND m.type=COMMIT)
               // Cascade to broadcast PREPARE, CONVERGE
80:          case PREPARE:
81:            BEBroadcast(m ∈ own_msgs: m.round=msg.round AND m.type=PREPARE)
               // Cascade to broadcast CONVERGE
82:          default: // CONVERGE
83:            if msg.round > 0:
84:              BEBroadcast(m ∈ own_msgs: m.round=msg.round AND m.type=CONVERGE)
85:              BEBroadcast(m ∈ own_msgs: m.round=msg.round-1 AND m.type=COMMIT)
86:              BEBroadcast(m ∈ own_msgs: m.round=msg.round-1 AND m.type=PREPARE)
87:              break
88:        }
           // Increase and trigger timeout_rebroadcast again.
           // The amount to increase is at the discretion of the participant.
89:        timeout_rebroadcast = timeout_rebroadcast + 1
90:        trigger(timeout_rebroadcast)


Updated Bridge Example

Message Content Intent should be enabled and shown in the example.
Without the message_content intent this won´t even work for the users.

It would be better if there is a banner like a warning or sth that the message content intent needs to be enabled in order to use prefixed commands. I am not very familiar with it so you may implement that if needed. :)

The banner you suggested might be added, however, you don't even need message content intent if you just ping the bot as a prefix for prefix commands.


call_by_value

Greetings sir/Mam,
I would like to contribute the code for this issue in c++/cpp.
The code is ready. I have added the code , along with proper explanation of the algorithm , test cases , time complexity and space complexity of the same, as per the guidelines.
Kindly assign it to me.
This is regarding letsgrowmore.in/soc/21
I have made a PR for the same.
Kindly assign this issue!!
Regards,
Hitain Kakkar

@HitainKakkar go Ahead


monitoring: Fix wrong calculation for KubeVirtVMIExcessiveMigrations in an edge case

What this PR does
There is an edge case, usually during an upgrade, in which two or more different virt-controllers are reporting the kubevirt_vmi_migration_succeeded metric for the same migration (VMIM) on the same VMI. In that case, we need to count that migration only once regardless of it being reported multiple times for the purpose of firing the alert about excessive amount of migrations in the last 24 hours. The new PromQL isolates the entries with different VMIMs, then sets the value of '1' to all of them, and then we're summing by the pair of vmi and its namespace.

Jira-ticket: https://issues.redhat.com/browse/CNV-40981
Why we need it and why it was done in this way
The following tradeoffs were made:
The following alternatives were considered:
Links to places where the discussion took place:
Special notes for your reviewer

Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to kubevirt-dev was considered

Release note

Fix wrong KubeVirtVMIExcessiveMigrations alert calculation in an upgrade scenario.

@orenc1 Thanks!
/lgtm
@machadovilaca / @sradco PTAL :)

thanks for the fix @orenc1, can you just add a unit test in https://github.com/kubevirt/kubevirt/blob/main/hack/prom-rule-ci/prom-rules-tests.yaml for this aler?

thanks for the fix @orenc1, can you just add a unit test in https://github.com/kubevirt/kubevirt/blob/main/hack/prom-rule-ci/prom-rules-tests.yaml for this aler?

Done, added two test cases demonstrating the new behaviour in which two virt-controller pods are reporting that metric for the same VMIM.

@assafad since the issue is "two or more different virt-controllers are reporting the kubevirt_vmi_migration_succeeded metric for the same migration (VMIM)", I wonder if this is something fixable by https://github.com/kubevirt/kubevirt/pull/12165

@assafad since the issue is "two or more different virt-controllers are reporting the kubevirt_vmi_migration_succeeded metric for the same migration (VMIM)", I wonder if this is something fixable by #12165

If the issue was that kubevirt_vmi_migration_succeeded is reported both by the leader pod and by the non-leader pod, I would agree, but I don't think it's the case. Not during upgrade the metric isn't duplicated. According to @orenc1 's comment on https://issues.redhat.com/browse/CNV-4098:

I think it's because the migration has happened in the middle of virt-controller pod transitioning due to the upgrade process

It's not about leader and non-leader, but about new virt-controller pod during upgrade.

@assafad since the issue is "two or more different virt-controllers are reporting the kubevirt_vmi_migration_succeeded metric for the same migration (VMIM)", I wonder if this is something fixable by #12165

If the issue was that kubevirt_vmi_migration_succeeded is reported both by the leader pod and by the non-leader pod, I would agree, but I don't think it's the case. When the cluster is NOT during upgrade, the metric isn't duplicated. According to @orenc1 's comment on https://issues.redhat.com/browse/CNV-4098:

I think you may have pasted the wrong issue

I think it's because the migration has happened in the middle of virt-controller pod transitioning due to the upgrade process

It's not about leader and non-leader, but about new virt-controller pod during upgrade. i.e. a temporary duplication of the metric that triggers this alert, and thus I think the suggested solution is valid.

But why is the new virt-controller pod reporting that migration metric? Can't just be the leader reporting it?

I think you may have pasted the wrong issue

Here it is - https://issues.redhat.com/browse/CNV-40981 (from the PR description).

But why is the new virt-controller pod reporting that migration metric? Can't just be the leader reporting it?

My guess would be that during an upgrade a new updated virt-controller pod is being created and it should replace the old leader one. Before the old one gets deleted, we have a temporary duplication, as there are 2 virt-controller leaders. @orenc1 does that sound correct? If not, can you please share more details on when this edge case takes place?

@machadovilaca we can probably fix this issue only by adding a For: 1h to the alert, and then for temporary metrics duplications, it won't fire. But deciding on the time frame for this issue is not so easy, so I prefer the current solution.

kubevirt_vmi_migration_succeeded is reported by a collector, remember we discussing if collectors should only be registered by the leader for the work in https://github.com/kubevirt/kubevirt/pull/12165? Do you think multiple pods might be running this collector?
According to my testing, collectors callbacks are running only by the leader pod. If the metric is duplicated, my guess is that there are 2 leader pods temporarily. i.e. even if we register collectors only by leader pods, this won't solve this PR's issue.
Anyway, @orenc1's fix is correct for now, and even if change something about the underlying metric/collector, his fix won't need to be reverted. IMO we should move forward with this PR.
/lgtm

kubevirt_vmi_migration_succeeded is reported by a collector, remember we discussing if collectors should only be registered by the leader for the work in #12165? Do you think multiple pods might be running this collector?

According to my testing, collectors callbacks are running only by the leader pod. If the metric is duplicated, my guess is that there are 2 leader pods temporarily. i.e. even if we register collectors only by leader pods, this won't solve this PR's issue. Anyway, @orenc1's fix is correct for now, and fixes the issue in the alert’s level. Even if we change something about the underlying metric/collector, this PR changes won't need to be reverted anyway. IMO we should move forward with this PR. /lgtm

Yes, i was able to reproduce the reported issue, by rapidly deleting the virt-controller pod during a long migration (e.g. Windows11 VM), and i saw the number of reported migration for that VMI was a lot higher, as it was reported by multiple virt-controller pods.

/approve
@assafad can you repeat your test but checking this: (to verify if indeed we have 2 pods running the collector)

Yes, i was able to reproduce the reported issue, by rapidly deleting the virt-controller pods during a long migration (e.g. Windows11 VM), and i saw the number of reported migration for that VMI was a lot higher, as it was reported by multiple virt-controller pods.

/cherry-pick release-1.3


[4.0] Won't build with MinGW (Warnings treated as errors)

Godot version:
4e0f31a
OS/device including version:
Windows 10 x64
Issue description:
Crashes when building in the middle with MinGW
Steps to reproduce:

Run build with MinGW (without Mono!).
Wait.
Catch this:

not sure if this is still the case but a couple weeks back warnings were treated as errors. Building with the -werror=0 flag worked.

@Byteron The SCons flag to use is werror=no, not -werror=0.

I get the same error when building with -werror=no

@Byteron Make sure not to include a leading - symbol. If all else fails, you can edit SConstruct and remove the code that enables -Werror.

ahh yes that seems to be working, thanks. :)

@Calinou
@Byteron
Interesting. I'll try this as well.

Latest master builds correctly AFAICS.

@Byteron @Teashrock Can you (or anyone else) still reproduce this bug in Godot 3.4.2 or any later release?

Closing due to lack of response. Please comment if you can still reproduce this bug.
PS: If no minimal reproduction project was included in the original bug report, please upload one as well to ease troubleshooting.


Configure multiple wifi AP

I could configure the wifi ap following the documentation at https://github.com/home-assistant/hassos/blob/dev/Documentation/network.md .
Is is possible to configure multiple ap using the config file?  One for office wifi and one for home?

Using a separate file for every wifi network should work. Just make sure you use a unique id and uuid.

It works.


PunkWallet doesn't work on Polygon

Hi @austintgriffith ,
I noticed that I cannot transfer funds with PunkWallet on the Polygon chain.
After debugging the code it turned out to be an ethers bug, which is now fixed in the latest version - 5.5.6.
Here is the ethers issue:
https://github.com/ethers-io/ethers.js/issues/2691
Note:
Actually PunkWallet still doesn't work on Polygon, because the gasPrice is set to 1gwei, which is not enough right now.
I can look into this later, manually setting the gasPrice worked for me, my transaction was confirmed.
Best,
Tamas

Duplicate of #2691


Entering whole code in its correct form

This will entail:

handling overtyping of fixed, or created text (this will mean holding the current 'place' of an invisible cursor during initiial creation of the frame only. (The latter implies some sort of Frame status).
ignoring redundant spaces or newlines
recognising the exit condition for each text field
adding the next frame upon the return at the end of the line (which might or might not be a field)
recognising the user typing the end keyword (or until for a repeat loop) and eliminating the current entry

Covered in other ticklets


Revert "fix(clerk-js): Use buildUrlWithAuth for all links/navigations…

Description
… (#1676)"
This reverts commit 28316a0da32b624a3e1655b2c11ebdde7eeca86e.
A regression was caught while testing on staging, the affected flow was:

Sign up with an email
Sign out
Sign in with the email and choose the email_link strategy
Open the email on the same device, click the link
A loop happens (/sign-in <> /sign-in/verify)

We will open and commit the PR again once the issue has been resolved.

Checklist

[x] npm test runs as expected.
[x] npm run build runs as expected.
[ ] (If applicable) JSDoc comments have been added or updated for any package exports
[ ] (If applicable) Documentation has been updated

Type of change

[x] 🐛 Bug fix
[ ] 🌟 New feature
[ ] 🔨 Breaking change
[ ] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

Packages affected

[x] @clerk/clerk-js
[ ] @clerk/clerk-react
[ ] @clerk/nextjs
[ ] @clerk/remix
[ ] @clerk/types
[ ] @clerk/themes
[ ] @clerk/localizations
[ ] @clerk/clerk-expo
[ ] @clerk/backend
[ ] @clerk/clerk-sdk-node
[ ] @clerk/shared
[ ] @clerk/fastify
[ ] @clerk/chrome-extension
[ ] gatsby-plugin-clerk
[ ] build/tooling/chore

This PR has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.


Retry using exponential backoff upon connection failure with Defender system tests

If IotMqtt_Connect connection fails, then the test completely fails. This PR addresses this issue by wrapping the method around RETRY_EXPONENTIAL, which retries the method with exponential backoff if the expected status is not returned.
Description

Checklist:

[ ] I have tested my changes. No regression in existing tests.
[ ] My code is Linted.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/bot run checks

/bot run checks

/bot run checks

/bot run checks


Makes the 10 profile picture cards all invisible to the dark background?

Title. Tried on both Firefox and Chrome with violentmonkey.  Just makes the pictures disappear, weird.

nvm lol i just had to do it a couple times


Remove deprecated properties

Remove deprecated, now unsupported, properties from the code

Changed in 12.0.2


Make fortune_list an option

I wanted to provide the possibility to configure an own fortune list. To prevent backwards compatibility, main now checks if a table or a number is provided.

tysm!


Issue 197 misc

Replaced confusing _hasGrid with initialized field and also replaced the hasGrid method with the self-explanatory isInitialized one.
Updated impacted unit tests

#197 related

:+1:


Cloudinary image and documents method consolidation; Array value location update.

The images and document entry types have been consolidated to the cloudinary entry type method to reduce duplication.
The cloudinary method will now immediately update the location making it unnecessary alter the entry content after the update.
It is now possible to set array values in a location update.
The set_field_array query has been removed since it is no longer required.
The skipFalsy flag will now skip on an empty array.

I have found an issue where if you place a new point, you can see the add image/document buttons in the infoj. But once you clear your selection and reselect the point again the buttons to upload will no longer be there.
https://github.com/GEOLYTIX/xyz/assets/43169158/9031708b-a591-4373-9478-a6484577f238
This is also true for any previously existing points on the scratch layer.

I found an issue with the delete of a cloudinary asset. If I upload multiple images, and I delete one. They all get removed.
https://github.com/GEOLYTIX/xyz/assets/43169158/0c47babd-17ee-452d-87c7-f82539df4d9e

@eo-uk Thanks for pointing out the newValues assignment. This was rubbish. We don't want to assign object in a forEach loop. And the number should not be checked here. There is a specific entry module for integer, and numeric [float] values. This was rubbish as well though.
I map the newValues object from entries like so.
  const newValues = Object.fromEntries(this.infoj
    .filter(entry => typeof entry.newValue !== 'undefined')
    .map(entry => [entry.field, entry.newValue]))

The numeric entries module has been updated to be in line with how entries modules should be like. The prefix and suffix will not be shown with the input.
@RobAndrewHurst The remove failed because I checked for the set length instead of its size. Hence it always removed everything.
The was also an issue with the location view logic. Edits were removed after the view was built. The edits must be removed before the infoj is populated. The toggleEdit and removeEdits should not fly around but should be assigned to the location object.

@RobAndrewHurst documents don't have a src but must remove the href from set. Also the response from xhr is nonsense and can be removed. The xhr should be awaited though.


[TASK][EASY] Add kyuubi.session.proxy.user as an alternative to hive.server2.proxy.user

What's the level of this task?
EASY
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Search before creating

[X] I have searched in the task list and found no similar tasks.

Mentor

[ ] I have sufficient expertise on this task, and I volunteer to be a mentor of this task to guide contributors through the task.

Skill requirements

Basic knowledge of Hadoop User Impersonation
Scala programming language

Background and Goals
https://github.com/apache/kyuubi/pull/5653
Implementation steps
https://github.com/apache/kyuubi/pull/5653
Additional context
Introduction of 2023 Kyuubi Code Contribution Program

This task is completed by @mrtisttt via https://github.com/apache/kyuubi/commit/50cd91b59ec09e374a6fef7a5f8e2759111e2ddd


Add script to help with building as packages and fix devkit and package info

This PR is a manual application of https://github.com/cloudfoundry/stratos/pull/4529
It adds a script to build the frontend packages, and fixes the devkit as well as the package info in some of the packages.

Once again fell victim to the insane interface for opening PRs on a forked repo...


[FABCN-407] Update protos

To prepare for the implementation of chaincode gRPC server, this patch
updates protobuf definitions to the latest ones.
Signed-off-by: Taku Shimosawa<EMAIL_ADDRESS>

@shimos thanks for the PR - can you clarify which version of the protos you've updated to here please?

@mbwhite Thank you for your comments. I copied from the master branch of fabric-protos (9944f8f73cfe0585a477f4b7d56a090374d0c7b6).
Do you have any suggestion for more appropriate version?

@mbwhite Thank you for your comments. I copied from the master branch of fabric-protos (9944f8f73cfe0585a477f4b7d56a090374d0c7b6).
Do you have any suggestion for more appropriate version?

That version is good thanks - wanted to check.


Phishlet Twitter not displaying correctly

hello,
Phishlet twitter not displaying correctly ..

Check web inspector in your browser. Clearly it is only able to load the main domain and cannot access any subdomains.

that is because
twitter.com
api.twitter.com
abs.twitter.com << -- does not exists.
i got the above info from doing phishlets get hostname twitter


fixes flow error on account/view page

PR Checklist

Please check all that apply to this PR using "x":

[x] I have checked that this PR is not a duplicate of an existing PR (open, closed or merged)
[x] I have checked that this PR does not introduce a breaking change
[x] This PR introduces breaking changes and I have provided a detailed explanation below

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting)
[ ] Refactoring (no functional changes)
[ ] Documentation changes
[x] Other - Please describe: Flow error

Fixes
Issue Number: #2024
What is the current behavior?
Props was improperly used as the type for the function signature even though there is no declared type of Props.
What is the new behavior?
any is used in its place as a proper flow type for props in this case
Other information

Thanks!

@j-collier thanks for the PR! Can we show you some appreciation?
Make sure to check out lbry.tech/contribute and sign up for the dev mailing list at the bottom!


chore: remove repetitive words

Change Description
Description of change / link to associated issue.
[skip ci]
Steps to Test
Steps for reviewers to follow to test the change.
Pull Request Checklist
Testing

[ ] Your PR passes all CI checks.
[ ] Tests covering the positive and negative (error paths) are included.
[ ] Bug fixes contain tests triggering the bug to prevent regressions.

[skip ci]
Code Style and Documentation

[x] The change obeys the Code Documentation and Commenting guidelines, and lines wrap at 80.
[x] Commits follow the Ideal Git Commit Structure.
[x] Any new logging statements use an appropriate subsystem and logging level.
[x] Any new lncli commands have appropriate tags in the comments for the rpc in the proto file.
[x]  There is a change description in the release notes, or [skip ci] in the commit message for small changes.

📝 Please see our  Contribution Guidelines for further guidance.

Thanks @cuinix for the PR the changes look good to me other than that Please read our contribution guideline regarding how to write commit message.

Also we please note this requirement we should put [skip ci] in the commit message for small changes:

There is a change description in the release notes, or [skip ci] in the commit message for small changes.

Also please note this requirement we should put [skip ci] in the commit message for small changes:

There is a change description in the release notes, or [skip ci] in the commit message for small changes.

@cuinix I mean in the commit message. This could be modified using the git commit --amend command e.g. the new commit message would look like chore: remove repetitive words.


Use antrea versioned types consistently in antrea agent (#407)

Use antrea versioned types consistently in antrea agent.

/test-conformance

Please add "Fixes #407" to PR description.

/test-all

I mean add "Fixes" to PR description, not commit message title, see https://github.com/vmware-tanzu/antrea/pull/398
Use antrea versioned types consistently in antrea agent.

Fixes #407


[Bug] disallow-capabilities-strict policy does not conform to Pod Security Admission implementation or PSS spec

Kyverno Version
1.8.1
Kubernetes Version
1.25.x
Kubernetes Platform
KinD
Description
The kyverno PSS/restricted policy will allow any mixed-case spelling of 'ALL' in securityContext.capabilities.drop['ALL']
For example, any of these are accepted: all | ALL | aLL | All | and so on
However, the PSS/restricted spec explicitly requires 'ALL' and the Pod Security Admission controller implementation requires 'ALL' as well.
I view this as a regression introduced by #421
In practice, cri-o and containerd appear to do case-insensitive matching for the ALL keyword, but this is not guaranteed to work for other runtimes.
Until a stricter CRI capabilities spec is championed in SIG-Node, it's preferable and arguably more correct for the PSS policies to stick to the canonical ALL capitalization. That way they will be consistent with each other as well as their own spec. It is very unlikely that the PSA implementation will change without a corresponding change to the CRI capabilities spec.
Steps to reproduce
Create v1.25 kind cluster
kind create cluster

Create test-drop-all namespace
kubectl create ns test-drop-all

Create nginx pod in the test-drop-all namespace
Note: securityContext.capabilities.drop['all']
kubectl apply -n test-drop-all -f - <<EOF
apiVersion: v1
kind: Pod
metadata:
  name: nginx
spec:
  containers:
    - image: nginxinc/nginx-unprivileged
      name: nginx
      securityContext:
        allowPrivilegeEscalation: false
        capabilities:
          drop: ['all']
        runAsNonRoot: true
        seccompProfile:
          type: RuntimeDefault
EOF

Observe that the built-in (PSA) pod-security enforcement does not accept this:
kubectl label --dry-run=server --overwrite ns test-drop-all pod-security.kubernetes.io/enforce=restricted

Warning: existing pods in namespace "test-drop-all" violate the new PodSecurity enforce level "restricted:latest"
Warning: nginx: unrestricted capabilities

But it passes Kyverno's pod-security policies:
kyverno apply <(kustomize build https://github.com/kyverno/policies/pod-security) -n test-drop-all -c

Applying 19 policy rules to 1 resource...
pass: 19, fail: 0, warn: 0, error: 0, skip: 38

Expected behavior
Kyverno's PSS/restricted enforcement should match that of PSA.
Esp. if I'm using kyverno CLI to pre-validate manifests for my cluster, I expect kyverno to be at least as restrictive as the PSA policies in the cluster.
Screenshots
No response
Kyverno logs
No response
Slack discussion
https://kubernetes.slack.com/archives/C032MM2CH7X/p1667224893686709
Troubleshooting

[X] I have read and followed the documentation AND the troubleshooting guide.
[X] I have searched other issues in this repository and mine is not recorded.

@chipzoller Based on feedback I received from a PSA implementer, I recommend reverting the change to kyverno/policies/pod-security in #421 and the similar change to kyverno/kyverno/charts in https://github.com/kyverno/kyverno/pull/4954
I would, though, retain the case-insensitive handling in the best practices policy - as an example of how to express this leniently.
Regarding kyverno's pod-security policies, there is no requirement for case insensitivity in the runtime specs (unfortunately?), but case-sensitivity is specified in the PSS/restricted spec and implemented in PSA.
See description for full rationale.
I can create PRs if this is agreeable.

What is harm in leaving them as is? It has no negative functional impact from what I can tell.

@chipzoller You're asking what is wrong with not implementing the spec? 😄
FWIW, The PSA maintainer I spoke to would prefer that all the pod-security implementations match each other and the spec.
I think there are several possible "harms" that can come from this:

The most likely one to affect me is that I'm using kyverno CLI to pre-validate manifests for my cluster. If kyverno accepts a manifest that PSA rejects (see example in description) then I get a failure at runtime instead of during development.

The potential harm is that some CRI-compliant runtime will be case-sensitive. Or containerd will tighten its implementation... Then, by validating my manifest, kyverno may overlook a potential runtime vulnerability - or failure.

I don't see a problem with walking these back. I think it would be helpful for there to be some corresponding documentation on the Kubernetes PSA side to which we could point users for an "official" statement lest it seems like it's a Kyverno gap/oversight. If you'd like to propose at least the Kyverno side in PRs, that would be grand.

This is being addressed in PR #485


Scrcpy loads for a split second then closes on its own

[x] I have read the FAQ.
[x] I have searched in existing issues.

Environment

OS: windows
scrcpy version: 1.23
installation method: windows
device model: Samsung s21ultra
Android version: 12

scrcpy 1.23 https://github.com/Genymobile/scrcpy
C:\Users\DefyH\Desktop\platform-tools\scrcpy-server: 1 file pushed, 0 skipped. 38.6 MB/s (41123 bytes in 0.001s)
[server] INFO: Device: samsung SM-G998U (Android 12)
INFO: Renderer: direct3d
INFO: Initial texture: 1080x2400
WARN: Device disconnected
Press any key to continue . . .
have looked through the issues and found nothing that worked device is charged up and have tried every port on my pc with different cables. about to pull out some hairs trying to fix it have had this issue with other stuff with connecting my phone to my pc with a cable

error: device offline

You device is not detected connected by adb. You should check on stackoverflow (it's not an issue from scrcpy).
On some devices, you might need to reboot, disable/reenable USB debugging, etc, when you get device offline.

the device works when i plug it in but then after 5 seconds it disconnects and shows that its offline like my title said   also have tried restarting and turning off and back on usb debugging and it didnt help
every time i unplug and plug it back it it will show online again

Hello, did you try to desactivate your anti-virus ?
Maybe the problem come from the security like windows defender.

I have checked my anti virus and its not the issue sorry for not responding till now. i havent needed to use this again untill now   and it still isnt working
i can confirm that adb is working and that scrcpy loads up for a split second and shows my screen, then just closes everything

its state=offline how do i fix that

Same issue with a new USB cable. Old cable works fine. I have Samsung J8.

Same issue with a new USB cable. Old cable works fine. I have Samsung J8.

I have seen the same issue with a new cable (from Gritin), but old cables work fine.

See also https://android.stackexchange.com/questions/12491/adb-constantly-disconnects-shows-device-offline

I had the same issue, but switching my device to my USB 3.0 port fixed it.

I had the same issue and fixed it by simply going to Developer Options on my phone and choosing "Revoke USB authorizations" and then plugged it back in. Once I plugged it back in, it asked if I wanted to allow the PC access and everything worked as normal.
Keep in mind that the port in which the phone is connected to does matter, try to connect to a port directly on the PC and not a dock.