Add pack flag to disable hook dialog errors during install and update and pack option to extend hooks timeout.

Is your feature request related to a problem? Please describe.
It's highly frustrating for users when they encounter the error message, "Installation has completed, but the application install hook failed. It may not have installed correctly."
In my case, when using start and update hooks on Windows, I'm preloading a .NET application to ensure it launches quickly after installation. However, due to antivirus software delays, the process sometimes takes longer than expected, causing the user to see this warning. Although this message does not indicate a true installation failure, it creates the impression of an error, which is misleading and unhelpful for users.
Describe the solution you'd like
Add velopack pack flag --disable-hook-dialogs to silent this warnings.
Add velopack pack option -- hook-dialogs-timeout [value_in_seconds] default is 30, so developer can extend this time.
Additional context
Enhance the user experience during the installation process for a smoother and more pleasant interaction.

Can you tell me more about this? What do you mean by preloading?

The first run of a .NET application is typically slow due to JIT (Just-In-Time) compilation. One way to improve startup performance is by publishing the app with the PublishReadyToRun=true option, though this significantly increases the application's size.
To address this issue, I run the application at startup/update hooks using an invisible window. This approach forces the JIT compilation to occur during the installation/update process, allowing the application to launch immediately once the installation/update is complete. This provides a much better user experience, as otherwise, the application would take time to start after installation, leaving the user without feedback.
In my case, for a self-contained Avalonia application, the initial startup after installation typically takes about 5 seconds due to JIT compilation. However, subsequent launches are almost instant since Windows caches the results of the previous compilation.
Certain antivirus software, such as McAfee, can significantly delay the first startup of the application, sometimes causing it to take more than 30 seconds to launch. This often results in a warning dialog being displayed, but once the application starts, it runs as expected without further issues.

The dialog is shown if the application running the hook must be killed. If this happens, it's likely that the application is not configured correctly (eg. did not handle the hook), or the code within the hook (which could be extracting files etc) did not complete successfully. Usually this means the app will be broken in one way or another. Letting a developer mute this is therefore probably the wrong thing most of the time.

This warning dialog cannot be configured, meaning the user has no control over it, which can lead to frustration during their first impression of the application. After reviewing the Velopack source code, I found that with a silent install, these warning dialogs are not displayed. Therefore, if the application is installed via Winget, the user will not encounter any warning dialogs.

This has been requested before, in general my reluctance to add this feature is: slower install/updates is definitely not a better user experience. Install/Uninstall are given 30 seconds (used to be 15), and before/after update still only gets 15 seconds. There's no reasonable way during those periods to communicate with your user about what you're doing, so unreasonably long delays will cause frustration, maybe people even killing the setup/update process via task manager.

I believe the user experience could be improved if the progress bar continued moving during the hook process, rather than freezing. This would provide clearer feedback to the user that the installation is still progressing, preventing confusion and improving the overall experience.

I am happy for you to try and further convince me this is a necessary and beneficial feature, but at the moment I suspect this is more likely to make customer experiences worse in general.

Overall, it's better to provide developers with the flexibility to decide which features they need during installation, allowing them to configure these options according to their specific requirements, rather than hardcoding them. This approach ensures greater adaptability and customization for different use cases.
PS
This could potentially be implemented by reading the application's output while the hooks are running. The application could write real-time progress updates to stdout, which would then be displayed by the updater process. This approach would make the installation process more user-friendly by providing continuous, clear feedback on what is happening during the installation.


2 ghostnodes now out of sync after initially upgrading to 3.0.1 without issue

2 synced ghostnodes upgraded from 3.0.0 to 3.0.1, resynced successfully but fell out of sync a few days later.

Expected ghostnodes to stay in sync with chain like the others did (which were upgraded same time)

Ubuntu 16.04, via sharks install/update script
debug2.log
debug1.log

for info, the nodes have been resynced again and are currently matching explorer


Let's talk: Mod Dependencies and JarInJar

Allow me to explain:

Mod dependencies refers to being able to declare what other mods(maybe java libraries?) your mod requires, is compatible with, breaks with, on a per version basis.
JarInJar refers to the ability to package mods(or libraries) inside other mods, and have the loader properly identify them.

Now that that's out of the way, let's talk about how I am planning on doing all of this.
The current implementation of felis, uses what I like to call a jar-tree that basically allows me to consider files inside of other files as usable class/resource providers. All that is really left for JarInJar is to decide on a directory inside the mod jar, where dependencies will be located and open the contents of said directory as part of the jar-tree. Specifically with mods, a very simple recursive parsing model(related to #6) where a mod attempts to parse it's included mods as well, makes sense.
Of course the issue with both cases, is resolution and conflicts.
Resolution
For resolution I am thinking some graph based system where each mod can specify the versions of mods it provides as well as the versions that it's compatible with. Then just check if all mods are compatible with available versions and everything is good.
Versioning
Of course we are enforcing semver 2.0.0 to everyone.
Conflicts
In terms of conflicts, there isn't much we can do.
If mod X requires and provides mod Y's 1.0 version but mod Y requires and provides mod Y's 1.2 version, things will get messy.
Therefore my idea is:

Mods are required to specify a range of compatible versions for their dependencies(either mods or libraries). Specifying a single version won't work.
For libraries included in mods, they need to specify a provided version. This is a single version of the dependency included.
For mods included in mods, since they have a mods.toml, use that for the version.
Always use the newest compatible version that is available in the environment. All others are dropped at runtime(completely ignored).
If no version is found that is compatible with all mods in the environment, insta-crash.

Therefore, the above example cannot work, since mods X and Y have to require a range of versions. Say X requires >=1.0 and Y 1.2.. In that case, the final version that will be resolved is 1.2 since it's the newest available version and is compatible with all other requirements(>=1.0 and 1.2.0 match with 1.2).
However, if X requires >=1.3.0 and provides 1.3.1, then things don't work out. That's because Y's 1.2. is not matched. In that case we would get a conflict crash.
I'd like to know your opinions on the above points.

Will probably wait until after my finals to do this.

Mod dependencies have been implemented. I finally finished finals so now that I have time, I got started on this again.

version 1.7.0 closes this

Closed by b8beb90


Add Carrot test for EHdn WDL

This PR adds a Carrot-based unit test for the ExpansionHunter denovo (EHdn) WDL.

Thank you @mwalker174. I agree incorporating MainVcfQc.wdl is a good next step.


Add getScrollPosition to History, and scrollX/scrollY to Location

I just typed up the code snippets from @mjackson and @gaearon in the comments above, and added just a little bit of error handling (there's now a fallback if getScrollPosition is not supplied).
I'm also looking into writing a test for this, I'm stuck because I don't know how to mock the scroll position changing in a test.
Also, I don't know if I should include the generated changes in lib/umd/History.js and lib/umd/History.min.js.
This addresses Issue #17.

Thanks for this PR @duncanmak! I think I may not have explained myself very well in #17.
This PR adds the scroll position to the next location, but we need to store scroll position on the previous location so that when we go back to it we'll know where to scroll the page. In order to persist state across transitions, we'll need to store some stuff in location.state, probably under a reserved key.
I'll take a stab at this today and see if I can show you what I mean. Code may be more clear than words :)

I think we can get by using the setState method introduced in 63091d2c6ce15a8a9a4d188923e86607dcbf9615 instead of getScrollPosition. Closing for now.
Thanks again, @duncanmak!


Connection timeout bug in search API

Describe the bug
No result from provider 'creodias' due to an error during the search.
urllib3.exceptions.ConnectTimeoutError: (<urllib3.connection.HTTPSConnection object at 0x7f0614fa07f0>, 'Connection to finder.creodias.eu timed out. (connect timeout=5)')
Timeout error is not properly handled and propagated back. The error (len() of None) appears already inside the eodag code:
normalize_remaining_count = len(results)
TypeError: object of type 'NoneType' has no len()

Code To Reproduce
all_products = session.search_all(**search_criteria) -> with the specific search and creodias provider for example.
Output
[2022-11-14 23:38:30,795][eodag.core][INFO] - Searching product type 'S2_MSI_L1C' on provider: creodias
[2022-11-14 23:38:30,795][eodag.core][INFO] - Iterate search over multiple pages: page #1
[2022-11-14 23:38:30,795][eodag.plugins.search.qssearch][INFO] - Sending search request: https://finder.creodias.eu/resto/api/collections/Sentinel2/search.json?startDate=2019-05-01T00:00:00&completionDate=2019-10-01T00:00:00&geometry=POLYGON ((9.1010 46.6489, 9.0945 46.6490, 9.0946 46.6534, 9.1011 46.6534, 9.1010 46.6489))&productType=L1C&maxRecords=2000&page=1
[2022-11-14 23:38:35,883][eodag.plugins.search.qssearch][ERROR] - Skipping error while searching for creodias QueryStringSearch instance:
Traceback (most recent call last):
  File ".../lib/python3.9/site-packages/urllib3/connection.py", line 174, in _new_conn
    conn = connection.create_connection(
  File ".../lib/python3.9/site-packages/urllib3/util/connection.py", line 95, in create_connection
    raise err
  File ".../lib/python3.9/site-packages/urllib3/util/connection.py", line 85, in create_connection
    sock.connect(sa)
socket.timeout: timed out

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File ".../lib/python3.9/site-packages/urllib3/connectionpool.py", line 703, in urlopen
    httplib_response = self._make_request(
  File ".../lib/python3.9/site-packages/urllib3/connectionpool.py", line 386, in _make_request
    self._validate_conn(conn)
  File ".../lib/python3.9/site-packages/urllib3/connectionpool.py", line 1042, in _validate_conn
    conn.connect()
  File ".../lib/python3.9/site-packages/urllib3/connection.py", line 358, in connect
    self.sock = conn = self._new_conn()
  File ".../lib/python3.9/site-packages/urllib3/connection.py", line 179, in _new_conn
    raise ConnectTimeoutError(
urllib3.exceptions.ConnectTimeoutError: (<urllib3.connection.HTTPSConnection object at 0x7f0614fa07f0>, 'Connection to finder.creodias.eu timed out. (connect timeout=5)')

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File ".../lib/python3.9/site-packages/requests/adapters.py", line 489, in send
    resp = conn.urlopen(
  File ".../lib/python3.9/site-packages/urllib3/connectionpool.py", line 787, in urlopen
    retries = retries.increment(
  File ".../lib/python3.9/site-packages/urllib3/util/retry.py", line 592, in increment
    raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='finder.creodias.eu', port=443): Max retries exceeded with url: /resto/api/collections/Sentinel2/search.json?startDate=2019-05-01T00:00:00&completionDate=2019-10-01T00:00:00&geometry=POLYGON%20((9.1010%2046.6489,%209.0945%2046.6490,%209.0946%2046.6534,%209.1011%2046.6534,%209.1010%2046.6489))&productType=L1C&maxRecords=2000&page=1 (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x7f0614fa07f0>, 'Connection to finder.creodias.eu timed out. (connect timeout=5)'))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File ".../lib/python3.9/site-packages/eodag/plugins/search/qssearch.py", line 864, in _request
    response = requests.get(url, timeout=HTTP_REQ_TIMEOUT, **kwargs)
  File ".../lib/python3.9/site-packages/requests/api.py", line 73, in get
    return request("get", url, params=params, **kwargs)
  File ".../lib/python3.9/site-packages/requests/api.py", line 59, in request
    return session.request(method=method, url=url, **kwargs)
  File ".../lib/python3.9/site-packages/requests/sessions.py", line 587, in request
    resp = self.send(prep, **send_kwargs)
  File ".../lib/python3.9/site-packages/requests/sessions.py", line 701, in send
    r = adapter.send(request, **kwargs)
  File ".../lib/python3.9/site-packages/requests/adapters.py", line 553, in send
    raise ConnectTimeout(e, request=request)
requests.exceptions.ConnectTimeout: HTTPSConnectionPool(host='finder.creodias.eu', port=443): Max retries exceeded with url: /resto/api/collections/Sentinel2/search.json?startDate=2019-05-01T00:00:00&completionDate=2019-10-01T00:00:00&geometry=POLYGON%20((9.1010%2046.6489,%209.0945%2046.6490,%209.0946%2046.6534,%209.1011%2046.6534,%209.1010%2046.6489))&productType=L1C&maxRecords=2000&page=1 (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x7f0614fa07f0>, 'Connection to finder.creodias.eu timed out. (connect timeout=5)'))
[2022-11-14 23:38:35,888][eodag.core][INFO] - No result from provider 'creodias' due to an error during search. Raise verbosity of log messages for details

File ".../sentinel_api.py", line 49, in search_products
    all_products = session.search_all(**search_criteria)
  File ".../lib/python3.9/site-packages/eodag/api/core.py", line 1099, in search_all
    for page_results in self.search_iter_page(
  File ".../lib/python3.9/site-packages/eodag/api/core.py", line 953, in search_iter_page
    products, _ = self._do_search(
  File ".../lib/python3.9/site-packages/eodag/api/core.py", line 1339, in _do_search
    res, nb_res = search_plugin.query(count=count, **kwargs)
  File ".../lib/python3.9/site-packages/eodag/plugins/search/qssearch.py", line 341, in query
    eo_products = self.normalize_results(provider_results, **kwargs)
  File ".../lib/python3.9/site-packages/eodag/plugins/search/qssearch.py", line 677, in normalize_results
    normalize_remaining_count = len(results)
TypeError: object of type 'NoneType' has no len()

Environment:

Python version: 3.9
EODAG version: 2.6.0

Additional context
The above error appeared in a large-scale search for 50k different searches. The error appeared on a specific search, after 10s of thousands of successful searches.

Additional note: The error might occur in the first place because of the long search windows and only 5s timeout.

Hello @ds2268 and thanks for submitting this issue. That's right, the TypeError should not be raised here, and should be handled in eodag

Do you have any idea when the fix can be expected in order for me to know how much to catch such exceptions on my side with ad-hoc patches?

I think this can be fixed by the end of november, but there are no guarantees

I've just run into this issue too.
I believe it's caused by a call to QueryStringSearch.do_search in QueryStringSearch.query returning None here due to the error catch for RequestError here (which itself is raised from the request exceeding 5 seconds.)
This then causes the call on the next line to QueryStringSearch.normalize_results to fail as it tries to take the length.
Could be fixed by returning an empty list in .do_search instead of None (mimicing what is normally returned by that function).
With dag=EODataAccessGateway(), dag.search_all returns SearchResult([]) and dag.search returns (SearchResult([]), 0), printing out some cascading connection timeout errors, but not raising an error itself.

Alternatively testing for None in .normalize_results before the call to len(results) with something like
        if(results is None):
            normalize_remaining_count = len(results)
        else:
            normalize_remaining_count = 0

has the same effect as the other fix.

Happy to submit a patch for this

@catchSheep: I like the first approach better. An empty list should probably mimic better the situation when there is a timeout error. The only missing thing would be in knowing that that happened and not that there are no results that could be found. An alternative would be to properly propagate the timeout exception all the way back to the user. This approach would probably be the most transparent.

Thanks for the suggestions @catchSheep and @ds2268 . The thing to do here is to make do_search() return [] instead of None is a RequestError is catched. This will prevent issues when processing the result, and also stop iterations in search_all() as expected.


HTML response in utf 8.

Hi,
I created an index.html file that displays "Moderation" with the  tag.
In my main.py there is:
from fastapi import FastAPI
from fastapi.responses import HTMLResponse
import os
app = FastAPI ()
@ app.get ("/ testHTML /", response_class = HTMLResponse)
async def read_items ():
f = open ("index.html", "r")
return HTMLResponse (f.read ())
But when I test I see this on the webpage:

I tried to add utf-8 meta tag to the HTML but it didn't change anything, I think it's an encoding problem in the HTMLResponse.

Did you try use decode?
f.read().decode("utf-8")

Hello,
decode generates an error (AttributeError: 'str' object has no attribute 'decode') and encode does not change anything.
Thanks anyways !

You also can try this f = open("index.html", "r", encoding="utf-8")

Thank you ! It works perfectly!


feature: add configurable proxy_origin

I have situation where I need to run the Vite dev server outside the docker container, which means, that I need Vite to use different origin than the ViteController::proxyBuild uses or else the proxy will end up failing because there is nothing running in the docker container on that specific origin.
This is a bit unusual/edge case, but it would be nice to have, since it does not introduce any bugs or compatibility issues.

Thank you @FluffyDiscord, it's perfect !
Have a nice day


Fix deprecated “publish” command

`wrangler pages publish` is deprecated and will be removed in the next major version.

  Please use `wrangler pages deploy` instead

Warning fixed

Thank you for your help in maintaining this repository 🧡. We've migrated to wrangler-action and are making improvements to ensure that contributions like this will be more easily integrated and better supported. Please come join us at wrangler-action!


SwiftyOnboardPage isn't setup correctly if the view isn't fullscreen.

This is because, the container view's x & y are shifted, according to the non-fullscreen view's x & y.
Steps to reproduce:

In the example project's use 'Storyboard Example View Controller'

Adjust the view that is connected to the code, and shrink in size.

Try running, and find that the customPage is also shifted wrt the view's x & y.

Visual representation of issue:

It was resolved into this:


Show username in navbar after login

After login username will be visible beside logout button

Right now username doesn't exist, also using the full name or email id won't be appropriate.

Right now username doesn't exist, also using the full name or email id won't be appropria

Right now username doesn't exist, also using the full name or email id won't be appropriate.

I was thinking of using first name
but i guess this change can wait till a username field is added in registration form


GattManager issues

Android GATT callbacks appear to be executing on arbitrary Binder threads.  I think GattManager#onCharacteristicChanged() needs to be synchronized to avoid concurrent access to mCharacteristicChangeListeners.
Also, this:
public BluetoothGatt getGatt(BluetoothDevice device) {
    return mGatts.get(device);
}

Should be mGatts.get(device.getAddress()).

Hi. If you could make a pull request we can get it merged :D

I encountered the same problem. The issue is still not solved. The arbitrary threads is from bluetooth stack.


add code and i18nParams too all completionRecord

@nwinter okay then we need you to merge it. i don't have write permission on esper.js strange 😂 so you find me to open this pr from my fork 😂


Blog about private repositories

Add blog post about private repositories

This is an automated message:
You can preview this docs PR at http://386.docs-pr.validatedpatterns.io
Note that they get generated every five minutes, so please wait a bit.


Events not being sent back to ElasticSearch if the connection is restored

A few questions before you begin:

Is this an issue related to the Serilog core project or one of the sinks or
community projects.
This issue list is intended for Serilog Elasticsearch Sink issues. If this issue relates to another sink or to the code project,
please log on the related repository.  Please use Gitter chat and Stack Overflow  for discussions and questons.

Yes this issue is related to the ElasticSearch sink.
Does this issue relate to a new feature or an existing bug?

[x] Bug
[ ] New Feature

What version of Serilog.Sinks.Elasticsearch is affected?  Please list the related NuGet package.
7.1.0
What is the target framework and operating system? See target frameworks & net standard matrix.

[x] netCore 2.0
[ ] netCore 1.0
[ ] 4.7
[ ] 4.6.x
[ ] 4.5.x

Please describe the current behavior?
I am facing an issue with the durability feature of this sink.
My application's log events are correctly pushed to an ElasticSearch index. The problem occurs when the index becomes unavailable and then the events written in the bookmark file are not sent back to ElasticSearch after the index becomes available and the application is restarted. If the index is unavailable I am also seeing a lot of invalid-200.json files corresponding to the unsent events.
Please describe the expected behavior?
IF there is an issue with the connectivity between the Sink and the ElasticSeach server should not the bookmarked logs be sent once the connectivity is restored?
If the current behavior is a bug, please provide the steps to reproduce the issue and if possible a minimal demo of the problem

Create a small console .NET Core application and configure Serilog to use the self debug log.
Use Autofac as the IOC implementation and add the following Serilog extension: https://github.com/nblumhardt/autofac-serilog-integration
Using the following Nugget version for this demo:

Autofac 4.9.2
Serilog 2.8.1-dev-01054
Serilog.Sinks.ElasticSearch 7.1.0
Serilog.Settings.Configuration 3.1.0
Serilog.Sinks.File 4.0.0

Run the console app and see the logs being pushed correctly to all configured sinks. The buffer file is created correctly. Close the console
Make the index read only
Re-run the application and see the logs being pushed correctly to the Console and the File sinks but no to elastic search. The serilog self debug log has a lot of the following errors:

2019-06-21T13:48:33.5349452Z Received failed ElasticSearch shipping result 403: {"type":"cluster_block_exception","reason":"blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];"}. Failed payload : {"@timestamp":"2019-06-21T16:48:31.8932771+03:00","level":"Information","messageTemplate":"This is an audit message with {@AuditUserDto}","message":"This is an audit message with AuditDataDto { UserId: 2, TenantId: 1, TenantUserId: null, CorrelationId: 225a3656-b66d-44a0-874d-234dcb03eb30, ChannelId: null, BotId: null, ConnectorHostId: null, Message: "This is step 0 of execution", Exception: null, FlowId: null, FlowName: null, FlowStepId: null, FlowStepName: null, ConnectorActionId: null, ConnectorActionName: null, ConnectorTaskId: null, ConnectorTaskName: null }","AuditUserDto":{"_typeTag":"AuditDataDto","UserId":2,"TenantId":1,"TenantUserId":null,"CorrelationId":"225a3656-b66d-44a0-874d-234dcb03eb30","ChannelId":null,"BotId":null,"ConnectorHostId":null,"Message":"This is step 0 of execution","Exception":null,"FlowId":null,"FlowName":null,"FlowStepId":null,"FlowStepName":null,"ConnectorActionId":null,"ConnectorActionName":null,"ConnectorTaskId":null,"ConnectorTaskName":null},"SourceContext":"SerilogConsole.LogWriter","MachineName":""DESKTOP-HSAMU3J"","ThreadId":1,"CustomProperty":"72ba1f99-ba98-492d-964c-6028c118d6af","Application":"SerilogConsole.Marius.Perciun"}.

Below I have attached my serilog configuration which resides under an appSettings.json file:
{
"Serilog": {
"MinimumLevel": "Debug",
"WriteTo": [
{
"Name": "File",
"Args": {
"path": "../../../Logs/SerilogConsole-Log-.json",
"rollingInterval": "Day",
"outputTemplate": "{Timestamp:yyyy-MM-dd HH:mm:ss.fff zzz} [{Level}] {Message} {Properties:j}{NewLine}{Exception}",
"formatter": "Serilog.Formatting.Compact.CompactJsonFormatter, Serilog.Formatting.Compact",
"fileSizeLimitBytes": 104857600
}

},
{
"Name": "Elasticsearch",
"Args": {
"nodeUris": "xxxxxxxxxxxxxxxxxxxxxxxxx",
"batchPostingLimit": 1,
"period": 1,
"inlineFields": true,
"bufferBaseFilename": "../../../Logs/SerilogConsole-Provisioning-ELK-Buffer",
"deadLetterIndexName": "dev-deadletter-{0:yyyy.MM}",
"indexFormat": "dev-serilogpoc-{0:yyyy.MM}",
"bufferFileSizeLimitBytes": 5242880,
"bufferLogShippingInterval": 1000,
"bufferRetainedInvalidPayloadsLimitBytes": 5000,
"bufferFileCountLimit": 31,
"connectionGlobalHeaders": "xxxxxxxxxxxxxxxxxxxxx",
"connectionTimeout": 5,
"emitEventFailure": "WriteToSelfLog",
"queueSizeLimit": "100000",
"autoRegisterTemplate": true,
"autoRegisterTemplateVersion": "ESv6",
"overwriteTemplate": false,
"numberOfShards": 5,
"numberOfReplicas": 1
}
}
],
"Enrich": [ "FromLogContext", "WithMachineName", "WithThreadId", "WithCustomEnricher" ],
"Properties": {
"Application": "SerilogConsole.Marius.Perciun"
}
}
}

It sounds like I have the same issue. I can successfully create an index, but the transmission got dropped somehow after a short period of time. All logging data got stored into the buffer file. If I keep interacting with my API, sometimes the hit counts of the elasticsearch get increased. However, it seems the new logging data get merged into old entries. I wonder what caused this issue.

Got same issue with .net framework version of serilog elasticsearch sinks.

Getting same issue. Logs fine to files. Going to use File Beat for now to get logs to Elastic

Old issue, cleaning up. Still facing this issue, feel free to reopen.

@mivano I have the same issue as the author with the last version - Serilog.Sinks.ElasticSearch 8.4.1


Add a gfg question: Maximum number produced by k adjacent swaps

Aim
Given an array a[ ] and the number of adjacent swap operations allowed are K. The task is to find the max number that can be formed using these swap operations.
Details
Features of this script:

Step by step explanation of the code
Clean and concise code with time complexity analysis

Programming language

[ ] C
[x] C++
[ ] Java
[ ] Python

@Ayush7614 can you please assign this to me under Hacktoberfest?


implement the full tooltip headless component with floating-ui + Daisy Impl

Todos:

[ ] Auto positioning
[ ] Fix initial un-positioned flicker
[ ] Daisy theming
[ ] Add tests / storybook

I'm taking the first three. @shairez can have fun with fixing the tests.

Looks like tooltip is now implemented;
Could this issue be closed? - @shairez @nnelgxorz ?

Yep we have it.


Fix error http request method of "consul.agent.registerService"

I think that there is a typo in registerService function. Please take some time to check. I hope this commit do some help. Thanks.

Dupe of #9?

Oh, yeah. Sorry for posting before checking existent issuses.


Bug: IR Fan  throwing error in the logs on 4.0.0 worked fine on 3.8.3

Describe the Bug
I have an IR controlled fan that worked fine under 3.8.3 and since upgrading to 4.0.0 I'm getting the following
v4.0.0 - Fan works but strange error in the logs. Apple Home thinks the fan is not responsive but it works anyway.
[10/14/2024, 9:08:33 PM] [SwitchBot] Fan: Bedroom Fan Sending request to SwitchBot API, body: [object Object],
[10/14/2024, 9:08:33 PM] [SwitchBot] Fan: Bedroom Fan failed pushChanges with OpenAPI Connection, Error Message: ""[object Object]" is not valid JSON"
3.8.3 - Fan works and no error. Apple home works as normal.
[10/17/2024, 10:09:59 PM] [SwitchBot] Fan: Bedroom Fan Sending request to SwitchBot API, body: {"command":"turnOn","parameter":"default","commandType":"command"},
[10/17/2024, 10:10:04 PM] [SwitchBot] Fan: Bedroom Fan request to SwitchBot API, body: {"command":"turnOn","parameter":"default","commandType":"command"} sent successfully
To Reproduce
upgrade to 4.0.0
Expected Behavior
Fan should work as in 3.8.3 and not throw the error and not show non-responsive in Apple Home.
Relevant Log Output
[10/14/2024, 10:59:47 AM] [SwitchBot] Initializing SwitchBot platform...
[10/14/2024, 10:59:47 AM] [SwitchBot] Initializing child bridge 0E:91:44:A2:6B:F7
[10/14/2024, 10:59:51 AM] [SwitchBot] Launched child bridge with PID 445
[10/14/2024, 10:59:59 AM] [SwitchBot] Loaded @switchbot/homebridge-switchbot v4.0.0 child bridge successfully
[10/14/2024, 10:59:59 AM] Loaded 8 cached accessories from cachedAccessories.0E9144A26BF7.
[10/14/2024, 11:00:00 AM] Homebridge v1.8.4 (HAP v0.12.2) (SwitchBot) is running on port 34697.
[10/14/2024, 11:00:00 AM]

NOTICE TO USERS AND PLUGIN DEVELOPERS
> Homebridge 2.0 is on the way and brings some breaking changes to existing plugins.
> Please visit the following link to learn more about the changes and how to prepare:
> https://github.com/homebridge/homebridge/wiki/Updating-To-Homebridge-v2.0

[10/14/2024, 9:08:33 PM] [SwitchBot] Fan: Bedroom Fan Sending request to SwitchBot API, body: [object Object],
[10/14/2024, 9:08:33 PM] [SwitchBot] Fan: Bedroom Fan failed pushChanges with OpenAPI Connection, Error Message: "\"[object Object]\" is not valid JSON"
[10/15/2024, 6:00:18 AM] [SwitchBot] Fan: Bedroom Fan Sending request to SwitchBot API, body: [object Object],
[10/15/2024, 6:00:19 AM] [SwitchBot] Fan: Bedroom Fan failed pushChanges with OpenAPI Connection, Error Message: "\"[object Object]\" is not valid JSON"
[10/15/2024, 6:00:46 AM] [SwitchBot] Fan: Bedroom Fan Sending request to SwitchBot API, body: [object Object],
[10/15/2024, 6:00:56 AM] [SwitchBot] Fan: Bedroom Fan Unknown statusCode: undefined, Submit Bugs Here: https://tinyurl.com/SwitchBotBug, statusCode: undefined
[10/15/2024, 6:45:03 AM] [SwitchBot] Fan: Bedroom Fan Sending request to SwitchBot API, body: [object Object],
[10/15/2024, 6:45:03 AM] [SwitchBot] Fan: Bedroom Fan failed pushChanges with OpenAPI Connection, Error Message: "\"[object Object]\" is not valid JSON"
[10/15/2024, 9:25:16 PM] [SwitchBot] Restarting child bridge...
[10/15/2024, 9:25:16 PM] Got SIGTERM, shutting down child bridge process...
[10/15/2024, 9:25:21 PM] [SwitchBot] Child bridge process ended
[10/15/2024, 9:25:21 PM] [SwitchBot] Process Ended. Code: 143, Signal: null
[10/15/2024, 9:25:28 PM] [SwitchBot] Restarting Process...
[10/15/2024, 9:25:28 PM] [SwitchBot] Launched child bridge with PID 39437
[10/15/2024, 9:25:30 PM] Registering platform<EMAIL_ADDRESS>[10/15/2024, 9:25:30 PM] [SwitchBot] Loaded @switchbot/homebridge-switchbot v4.0.0 child bridge successfully
[10/15/2024, 9:25:30 PM] Loaded 8 cached accessories from cachedAccessories.0E9144A26BF7.
[10/15/2024, 9:25:30 PM] Homebridge v1.8.4 (HAP v0.12.2) (SwitchBot) is running on port 34697.
[10/15/2024, 9:25:30 PM]

NOTICE TO USERS AND PLUGIN DEVELOPERS
> Homebridge 2.0 is on the way and brings some breaking changes to existing plugins.
> Please visit the following link to learn more about the changes and how to prepare:
> https://github.com/homebridge/homebridge/wiki/Updating-To-Homebridge-v2.0

[10/15/2024, 9:55:47 PM] [SwitchBot] Fan: Bedroom Fan Sending request to SwitchBot API, body: [object Object],
[10/15/2024, 9:55:47 PM] [SwitchBot] Fan: Bedroom Fan failed pushChanges with OpenAPI Connection, Error Message: "\"[object Object]\" is not valid JSON"
[10/16/2024, 2:31:46 AM] [SwitchBot] Color Bulb: Sink Set On: false
[10/16/2024, 6:00:19 AM] [SwitchBot] Fan: Bedroom Fan Sending request to SwitchBot API, body: [object Object],
[10/16/2024, 6:00:19 AM] [SwitchBot] Fan: Bedroom Fan failed pushChanges with OpenAPI Connection, Error Message: "\"[object Object]\" is not valid JSON"
[10/16/2024, 6:00:46 AM] [SwitchBot] Fan: Bedroom Fan Sending request to SwitchBot API, body: [object Object],
[10/16/2024, 6:00:46 AM] [SwitchBot] Fan: Bedroom Fan failed pushChanges with OpenAPI Connection, Error Message: "\"[object Object]\" is not valid JSON"
[10/16/2024, 6:45:03 AM] [SwitchBot] Fan: Bedroom Fan Sending request to SwitchBot API, body: [object Object],
[10/16/2024, 6:45:03 AM] [SwitchBot] Fan: Bedroom Fan failed pushChanges with OpenAPI Connection, Error Message: "\"[object Object]\" is not valid JSON"
[10/16/2024, 4:07:41 PM] [SwitchBot] Fan: Bedroom Fan Sending request to SwitchBot API, body: [object Object],
[10/16/2024, 4:07:41 PM] [SwitchBot] Fan: Bedroom Fan failed pushChanges with OpenAPI Connection, Error Message: "\"[object Object]\" is not valid JSON"
[10/16/2024, 4:12:46 PM] [SwitchBot] Fan: Bedroom Fan Sending request to SwitchBot API, body: [object Object],
[10/16/2024, 4:12:46 PM] [SwitchBot] Fan: Bedroom Fan failed pushChanges with OpenAPI Connection, Error Message: "\"[object Object]\" is not valid JSON"
[10/16/2024, 11:06:53 PM] [SwitchBot] Fan: Bedroom Fan Sending request to SwitchBot API, body: [object Object],
[10/16/2024, 11:06:53 PM] [SwitchBot] Fan: Bedroom Fan failed pushChanges with OpenAPI Connection, Error Message: "\"[object Object]\" is not valid JSON"
[10/17/2024, 6:00:11 AM] [SwitchBot] Fan: Bedroom Fan Sending request to SwitchBot API, body: [object Object],
[10/17/2024, 6:00:11 AM] [SwitchBot] Fan: Bedroom Fan failed pushChanges with OpenAPI Connection, Error Message: "\"[object Object]\" is not valid JSON"
[10/17/2024, 6:00:40 AM] [SwitchBot] Fan: Bedroom Fan Sending request to SwitchBot API, body: [object Object],
[10/17/2024, 6:00:40 AM] [SwitchBot] Fan: Bedroom Fan failed pushChanges with OpenAPI Connection, Error Message: "\"[object Object]\" is not valid JSON"
[10/17/2024, 6:04:51 AM] [SwitchBot] Fan: Bedroom Fan Sending request to SwitchBot API, body: [object Object],
[10/17/2024, 6:04:51 AM] [SwitchBot] Fan: Bedroom Fan failed pushChanges with OpenAPI Connection, Error Message: "\"[object Object]\" is not valid JSON"
[10/17/2024, 9:10:29 PM] [SwitchBot] Fan: Bedroom Fan Sending request to SwitchBot API, body: [object Object],
[10/17/2024, 9:10:30 PM] [SwitchBot] Fan: Bedroom Fan failed pushChanges with OpenAPI Connection, Error Message: "\"[object Object]\" is not valid JSON"
[10/17/2024, 10:00:43 PM] [SwitchBot] Fan: Bedroom Fan Sending request to SwitchBot API, body: [object Object],
[10/17/2024, 10:00:43 PM] [SwitchBot] Fan: Bedroom Fan failed pushChanges with OpenAPI Connection, Error Message: "\"[object Object]\" is not valid JSON"
[10/17/2024, 10:00:48 PM] [SwitchBot] Fan: Bedroom Fan Sending request to SwitchBot API, body: [object Object],
[10/17/2024, 10:00:49 PM] [SwitchBot] Fan: Bedroom Fan failed pushChanges with OpenAPI Connection, Error Message: "\"[object Object]\" is not valid JSON"
[10/17/2024, 10:01:13 PM] [SwitchBot] Fan: Bedroom Fan Sending request to SwitchBot API, body: [object Object],
[10/17/2024, 10:01:13 PM] [SwitchBot] Fan: Bedroom Fan Sending request to SwitchBot API, body: [object Object],
[10/17/2024, 10:01:13 PM] [SwitchBot] Fan: Bedroom Fan failed pushChanges with OpenAPI Connection, Error Message: "\"[object Object]\" is not valid JSON"
[10/17/2024, 10:01:13 PM] [SwitchBot] Fan: Bedroom Fan failed pushChanges with OpenAPI Connection, Error Message: "\"[object Object]\" is not valid JSON"
[10/17/2024, 10:01:13 PM] [SwitchBot] Fan: Bedroom Fan Sending request to SwitchBot API, body: [object Object],
[10/17/2024, 10:01:14 PM] [SwitchBot] Fan: Bedroom Fan failed pushChanges with OpenAPI Connection, Error Message: "\"[object Object]\" is not valid JSON"
[10/17/2024, 10:01:24 PM] [SwitchBot] Fan: Bedroom Fan Sending request to SwitchBot API, body: [object Object],
[10/17/2024, 10:01:24 PM] [SwitchBot] Fan: Bedroom Fan failed pushChanges with OpenAPI Connection, Error Message: "\"[object Object]\" is not valid JSON"
[10/17/2024, 10:02:32 PM] [SwitchBot] Restarting child bridge...
[10/17/2024, 10:02:32 PM] Got SIGTERM, shutting down child bridge process...
[10/17/2024, 10:02:37 PM] [SwitchBot] Child bridge process ended
[10/17/2024, 10:02:37 PM] [SwitchBot] Process Ended. Code: 143, Signal: null
[10/17/2024, 10:02:44 PM] [SwitchBot] Restarting Process...
[10/17/2024, 10:02:44 PM] [SwitchBot] Launched child bridge with PID 93963
[10/17/2024, 10:02:46 PM] Registering platform<EMAIL_ADDRESS>[10/17/2024, 10:02:46 PM] [SwitchBot] Loaded @switchbot/homebridge-switchbot v4.0.0 child bridge successfully
[10/17/2024, 10:02:46 PM] Loaded 8 cached accessories from cachedAccessories.0E9144A26BF7.
[10/17/2024, 10:02:47 PM] Homebridge v1.8.4 (HAP v0.12.2) (SwitchBot) is running on port 34697.
[10/17/2024, 10:02:47 PM]

NOTICE TO USERS AND PLUGIN DEVELOPERS
> Homebridge 2.0 is on the way and brings some breaking changes to existing plugins.
> Please visit the following link to learn more about the changes and how to prepare:
> https://github.com/homebridge/homebridge/wiki/Updating-To-Homebridge-v2.0

[10/17/2024, 10:03:45 PM] [SwitchBot] Fan: Bedroom Fan Sending request to SwitchBot API, body: [object Object],
[10/17/2024, 10:03:46 PM] [SwitchBot] Fan: Bedroom Fan failed pushChanges with OpenAPI Connection, Error Message: "\"[object Object]\" is not valid JSON"
[10/17/2024, 10:07:46 PM] [SwitchBot] Restarting child bridge...
[10/17/2024, 10:07:46 PM] Got SIGTERM, shutting down child bridge process...
[10/17/2024, 10:07:51 PM] [SwitchBot] Child bridge process ended
[10/17/2024, 10:07:51 PM] [SwitchBot] Process Ended. Code: 143, Signal: null
[10/17/2024, 10:07:58 PM] [SwitchBot] Restarting Process...
[10/17/2024, 10:07:58 PM] [SwitchBot] Launched child bridge with PID 94270
[10/17/2024, 10:08:00 PM] Registering platform<EMAIL_ADDRESS>[10/17/2024, 10:08:00 PM] [SwitchBot] Loaded @switchbot/homebridge-switchbot v4.0.1-beta.1 child bridge successfully
[10/17/2024, 10:08:00 PM] Loaded 8 cached accessories from cachedAccessories.0E9144A26BF7.
[10/17/2024, 10:08:00 PM] Homebridge v1.8.4 (HAP v0.12.2) (SwitchBot) is running on port 34697.
[10/17/2024, 10:08:00 PM]

NOTICE TO USERS AND PLUGIN DEVELOPERS
> Homebridge 2.0 is on the way and brings some breaking changes to existing plugins.
> Please visit the following link to learn more about the changes and how to prepare:
> https://github.com/homebridge/homebridge/wiki/Updating-To-Homebridge-v2.0

[10/17/2024, 10:08:48 PM] [SwitchBot] Fan: Bedroom Fan Sending request to SwitchBot API, body: [object Object],
[10/17/2024, 10:08:48 PM] [SwitchBot] Fan: Bedroom Fan failed pushChanges with OpenAPI Connection, Error Message: "\"[object Object]\" is not valid JSON"
[10/17/2024, 10:09:09 PM] [SwitchBot] Fan: Bedroom Fan Sending request to SwitchBot API, body: [object Object],
[10/17/2024, 10:09:09 PM] [SwitchBot] Fan: Bedroom Fan failed pushChanges with OpenAPI Connection, Error Message: "\"[object Object]\" is not valid JSON"
[10/17/2024, 10:09:37 PM] [SwitchBot] Restarting child bridge...
[10/17/2024, 10:09:37 PM] Got SIGTERM, shutting down child bridge process...
[10/17/2024, 10:09:42 PM] [SwitchBot] Child bridge process ended
[10/17/2024, 10:09:42 PM] [SwitchBot] Process Ended. Code: 143, Signal: null
[10/17/2024, 10:09:49 PM] [SwitchBot] Restarting Process...
[10/17/2024, 10:09:50 PM] [SwitchBot] Launched child bridge with PID 94514
[10/17/2024, 10:09:52 PM] Registering platform<EMAIL_ADDRESS>[10/17/2024, 10:09:52 PM] [SwitchBot] Loaded @switchbot/homebridge-switchbot v3.8.3 child bridge successfully
[10/17/2024, 10:09:52 PM] Loaded 8 cached accessories from cachedAccessories.0E9144A26BF7.
[10/17/2024, 10:09:52 PM] Homebridge v1.8.4 (HAP v0.12.2) (SwitchBot) is running on port 34697.
[10/17/2024, 10:09:52 PM]

NOTICE TO USERS AND PLUGIN DEVELOPERS
> Homebridge 2.0 is on the way and brings some breaking changes to existing plugins.
> Please visit the following link to learn more about the changes and how to prepare:
> https://github.com/homebridge/homebridge/wiki/Updating-To-Homebridge-v2.0

[10/17/2024, 10:09:59 PM] [SwitchBot] Fan: Bedroom Fan Sending request to SwitchBot API, body: {"command":"turnOn","parameter":"default","commandType":"command"},
[10/17/2024, 10:10:04 PM] [SwitchBot] Fan: Bedroom Fan request to SwitchBot API, body: {"command":"turnOn","parameter":"default","commandType":"command"} sent successfully
[10/17/2024, 10:11:15 PM] [SwitchBot] Fan: Bedroom Fan Sending request to SwitchBot API, body: {"command":"turnOff","parameter":"default","commandType":"command"},
[10/17/2024, 10:11:15 PM] [SwitchBot] Fan: Bedroom Fan request to SwitchBot API, body: {"command":"turnOff","parameter":"default","commandType":"command"} sent successfully
[10/17/2024, 10:11:17 PM] [SwitchBot] Restarting child bridge...
[10/17/2024, 10:11:17 PM] Got SIGTERM, shutting down child bridge process...
[10/17/2024, 10:11:22 PM] [SwitchBot] Child bridge process ended
[10/17/2024, 10:11:22 PM] [SwitchBot] Process Ended. Code: 143, Signal: null
[10/17/2024, 10:11:29 PM] [SwitchBot] Restarting Process...
[10/17/2024, 10:11:30 PM] [SwitchBot] Launched child bridge with PID 94701
[10/17/2024, 10:11:32 PM] Registering platform<EMAIL_ADDRESS>[10/17/2024, 10:11:32 PM] [SwitchBot] Loaded @switchbot/homebridge-switchbot v4.0.0 child bridge successfully
[10/17/2024, 10:11:32 PM] Loaded 8 cached accessories from cachedAccessories.0E9144A26BF7.
[10/17/2024, 10:11:32 PM] Homebridge v1.8.4 (HAP v0.12.2) (SwitchBot) is running on port 34697.
[10/17/2024, 10:11:32 PM]

NOTICE TO USERS AND PLUGIN DEVELOPERS
> Homebridge 2.0 is on the way and brings some breaking changes to existing plugins.
> Please visit the following link to learn more about the changes and how to prepare:
> https://github.com/homebridge/homebridge/wiki/Updating-To-Homebridge-v2.0

[10/17/2024, 10:18:56 PM] [SwitchBot] Restarting child bridge...
[10/17/2024, 10:18:56 PM] Got SIGTERM, shutting down child bridge process...
[10/17/2024, 10:19:01 PM] [SwitchBot] Child bridge process ended
[10/17/2024, 10:19:01 PM] [SwitchBot] Process Ended. Code: 143, Signal: null
[10/17/2024, 10:19:08 PM] [SwitchBot] Restarting Process...
[10/17/2024, 10:19:08 PM] [SwitchBot] Launched child bridge with PID 95028
[10/17/2024, 10:19:10 PM] Registering platform<EMAIL_ADDRESS>[10/17/2024, 10:19:10 PM] [SwitchBot] Loaded @switchbot/homebridge-switchbot v3.8.3 child bridge successfully
[10/17/2024, 10:19:10 PM] Loaded 8 cached accessories from cachedAccessories.0E9144A26BF7.
[10/17/2024, 10:19:10 PM] Homebridge v1.8.4 (HAP v0.12.2) (SwitchBot) is running on port 34697.
[10/17/2024, 10:19:10 PM]

NOTICE TO USERS AND PLUGIN DEVELOPERS
> Homebridge 2.0 is on the way and brings some breaking changes to existing plugins.
> Please visit the following link to learn more about the changes and how to prepare:
> https://github.com/homebridge/homebridge/wiki/Updating-To-Homebridge-v2.0

[10/17/2024, 10:19:13 PM] [SwitchBot] Fan: Bedroom Fan Sending request to SwitchBot API, body: {"command":"turnOn","parameter":"default","commandType":"command"},
[10/17/2024, 10:19:14 PM] [SwitchBot] Fan: Bedroom Fan request to SwitchBot API, body: {"command":"turnOn","parameter":"default","commandType":"command"} sent successfully
[10/17/2024, 10:21:30 PM] [SwitchBot] Restarting child bridge...
[10/17/2024, 10:21:30 PM] Got SIGTERM, shutting down child bridge process...
[10/17/2024, 10:21:35 PM] [SwitchBot] Child bridge process ended
[10/17/2024, 10:21:35 PM] [SwitchBot] Process Ended. Code: 143, Signal: null
[10/17/2024, 10:21:42 PM] [SwitchBot] Restarting Process...
[10/17/2024, 10:21:42 PM] [SwitchBot] Launched child bridge with PID 95348
[10/17/2024, 10:21:44 PM] Registering platform<EMAIL_ADDRESS>[10/17/2024, 10:21:44 PM] [SwitchBot] Loaded @switchbot/homebridge-switchbot v3.8.3 child bridge successfully
[10/17/2024, 10:21:44 PM] Loaded 8 cached accessories from cachedAccessories.0E9144A26BF7.
[10/17/2024, 10:21:44 PM] Homebridge v1.8.4 (HAP v0.12.2) (SwitchBot) is running on port 34697.
[10/17/2024, 10:21:44 PM]

NOTICE TO USERS AND PLUGIN DEVELOPERS
> Homebridge 2.0 is on the way and brings some breaking changes to existing plugins.
> Please visit the following link to learn more about the changes and how to prepare:
> https://github.com/homebridge/homebridge/wiki/Updating-To-Homebridge-v2.0

Config for homebridge-switchbot
{
    "name": "SwitchBot",
    "credentials": {
        "token": "REMOVED",
        "secret": "REMOVED",
        "notice": "Keep your Token & Secret a secret!"
    },
    "options": {
        "refreshRate": 3600,
        "logging": "none"
    },
    "_bridge": {
        "username": "0E:91:44:A2:6B:F7",
        "port": 34697
    },
    "platform": "SwitchBot"
}

Screenshots
No response
Device and Model
N/A
Node.js Version
v20.18.0
NPM Version
10.8.2
Homebridge Version
1.8.4
Homebridge Switchbot Plugin Version
4.0.0
Homebridge Config UI X Plugin Version
4.61.0
Operating System
Docker on Synology

Thanks that should be an easy fix. I will get it in the next release

Thanks that should be an easy fix. I will get it in the next release

Great to hear! Love the plugin!

Okay latest beta has this fix

Okay latest beta has this fix

I can confirm this appears to have fixed the issue. Many thanks!


Use prefixed QNames in XPath expressions used by all implementations of ICmdletProviderSupportsHelp interface

Fixes #2088 Provider-specific help cannot be loaded from MAML XML files because of incorrect XPath query.
Also includes these bugfixes:

WSManConfigProvider.GetHelpMaml: Tried to load XML from
MemoryStream that was created from file name string. Use XmlReader
instead.
WSManConfigProvider.GetHelpMaml: Use Path.Combine instead of
platform-specific directory separator character.
WSManConfigProvider.GetHelpMaml: CmdletHelpPath MAML XML element
attribute ID must be lowercase.

I have no idea how to test this using Pester, -- affected classes seem to be difficult (or impossible?) to isolate in tests. I would appreciate any ideas.

Hi @0xfeeddeadbeef, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;

@0xfeeddeadbeef, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, MSBOT;

The changes looks good. Can you add tests for this under: https://github.com/PowerShell/PowerShell/blob/master/test/powershell/engine/HelpSystem.Tests.ps1
In the test you could use Select-Xml to get the provider specific help for Get-Item like:

$Namespace = @{command = "http://schemas.microsoft.com/maml/dev/command/2004/10"; maml = "http://schemas.microsoft.com/maml/2004/10"; dev = "http://schemas.microsoft.com/maml/dev/2004/10"; msh = "http://msh"}

$Path = "$PSHome\en-US\System.Management.Automation.dll-help.xml"

$xPath = "/msh:helpItems/msh:providerHelp/msh:CmdletHelpPaths/msh:CmdletHelpPath[@id='FileSystem']/command:command[command:details/command:verb='Get' and command:details/command:noun='Item']"

$op = Select-Xml -Path 'C:\Windows\System32\WindowsPowerShell\v1.0\en-US\System.Management.Automation.dll-help.xml' -XPath $xPath  -Namespace $Namespace | Select-Object -ExpandProperty Node

$op.description.para

$op.description.para should match the description returned from the
(get-help get-item).description

Tests failed, get details here:  https://ci.appveyor.com/project/PowerShell/powershell/build/6.0.0-alpha.9-329/tests

I've added some basic tests, ran CI build multiple times and results are not good:
When invoked at AppVeyor, Get-Help -Name "$verb-$noun" -Path $path cmdlet returns "bare" help, i.e. only command syntax, - no description, no synopsis, no other details. It even fails to locate the default help. I was unable to find the root cause of this.
This happens at AppVeyor:
Get-Help -Name "New-Item" -Path 'Cert:\' | Select-Object -ExpandProperty Synopsis

# output
New-Item [-Path] <string[]> [-ItemType <string>] [-Value <Object>] [-Force] [-Credential <pscredential>] [-WhatIf] [-Confirm] [<CommonParameters>]

New-Item [[-Path] <string[]>] -Name <string> [-ItemType <string>] [-Value <Object>] [-Force] [-Credential <pscredential>] [-WhatIf] [-Confirm] [<CommonParameters>]

This output, obviously, will not match the text from help.xml.
When run locally, using fresh & clean build, same cmdlet is able to load text from help.xml file:
Get-Help -Name "New-Item" -Path 'Cert:\' | Select-Object -ExpandProperty Synopsis

# output
Creates new certificate stores in the LocalMachine store location.

As for Linux (Travis CI), these tests would fail, because:

Fresh build output does not contain help.xml files, Pester test must run Update-Help to retrieve them; but Update-Help is not yet supported on Linux (It is using Windows Cabinet API internally). Without Update-Help, there will be no help.xml files to load provider-specific help from.
Cert:\ and WSMan:\ providers are not yet supported on non-Windows platforms (Correct me if I'm wrong).

I've disabled these tests when build is not running on Windows.
Looks like I am stuck here.
@adityapatwardhan Any ideas?

@0xfeeddeadbeef , to build the same way and run the same tests which are failing, please run the following on windows from the root of the PowerShell repo:
Import-Module .\tools\appveyor.psm1
Invoke-AppVeyorFull

You may need to rebase the latest changes as this command was only added recently.
Warning: this will rerun start-psbootstrap

@TravisEz13 Thank you. That's really useful tip. I was able to attach a debugger and I think I'm onto something: when running with generated native images, ProviderBase.ProviderInfo.HelpFile property returns something like this: OriginalAssemblyName.ni.dll-Help.xml - notice the ni in the name. Looks like this bug is burrowed even deeper. I'll try to figure it out...

@0xfeeddeadbeef No Problem, it's a very recent change.  I haven't even documented it yet.

@0xfeeddeadbeef It seems all the tests are passing. Are more changes expected for this issue?

@adityapatwardhan That's all. No more changes.

:shipit:


Type#method_missing calls super

Earlier implementation returned nil on unknown method calls, which would make debugging much harder.

:+1:

Thanks!


Can I registe a usertype function,and It's return value is a enum

I trying to do this ,but I get a error when i compile my program.It's say: can not transfer value"EDir" to "EDir &".
Any idea how to do this?

Can you post your usertype registration code and the code of the function you're trying to bind?

What @OrfeasZ said.
The following code works flawlessly. Unless you can provide me with your program that doesn't compile, compiler version / IDE you're using (Visual Studio, XCode, something + gcc...), and any other helpful information, I don't think I'll be able to help you. Please be more specific.
#include <iostream>
#include "sol.hpp"

int main() {

	enum class strict_t {
		e_a,
		e_b,
		e_c
	};

	enum norm_t {
		e_a = 4,
		e_b = 5,
		e_c = 6,
	};

	struct test_a {
		norm_t g() {
			return norm_t::e_a;
		}
	};
	struct test_b {
		norm_t g() {
			return norm_t::e_b;
		}
	};

	sol::state lua;

	lua.set_function("f", []() {
		return strict_t::e_a;
	}
	);
	lua.set_function("g", []() {
		return strict_t::e_b;
	}
	);
	lua.set_function("h", []() {
		return strict_t::e_c;
	}
	);
	lua.new_usertype<test_a>("test_a",
		"f", []() {
			return strict_t::e_b;
		},
		"g", &test_a::g
	);
	lua.new_simple_usertype<test_b>("test_b",
		"f", []() {
			return strict_t::e_c;
		},
		"g", &test_b::g
	);

	sol::function f = lua["f"];
	lua.script("v0 = f()");
	strict_t v1 = f();
	strict_t v0 = lua["v0"];
	assert(v0 == strict_t::e_a);
	assert(v1 == strict_t::e_a);

	lua.script("ta = test_a.new()");
	lua.script("tb = test_b.new()");

	lua.script("v2 = ta:g()");
	lua.script("v3 = tb:g()");
	norm_t v2 = lua["v2"];
	norm_t v3 = lua["v3"];
	assert(v2 == norm_t::e_a);
	assert(v3 == norm_t::e_b);
	return 0;
}

I'm... going to consider this solved. Post here again if you continue to have trouble, and we'll help troubleshoot your issue. Just make sure to be more specific about what you're using / doing.
Thanks for using sol2!


Do not call exception handler on IOException during connection closing/draining

Fixes https://github.com/nats-io/java-nats/issues/217.
Confirmed exceptionOccurred is not triggered with the same example code listed in 217.

I will take a look this week, trying to wrap something up.

Added fix to connection code, and updated R->r :-)
fix is in the 2.4.2 branch.


undefined method `name' for nil:NilClass

Hello folks,
After quite some time figuring out how to install Fluxday properly I can finally get to be connected, I created some users but I cannot assign Managers to teams or anything it would give me this:
undefined method `name' for nil:NilClass
Would someone know a fix for that ? During the installation I tried to use ruby 2.1.0 but it woudnt let me bundle without being at 2.3.0, and I am afraid of the whole thing crumbling down if I dare downgrate it...
Thanks in advance !

You can try it out with this empty fluxday at http://<IP_ADDRESS>/

i have installed the application using ruby 2.1.0 and its working fine for me. Can you please try to install with ruby 2.1.0 and share the error

Retried but it couldn’t work, going to try another tool


Restart development of v2

Quick Glance

Current v2 branch is partly broken
Unnecessary monorepo -- the ui package is empty
Design system doesn't match Svelte's
Acessibility concerns

Description
Given Svelte 5 was recently released, together with sv, I identified some discrepancies between recommended practices and practices used in the v2 branch.

[!NOTE]
This is not a rant. It's just me questioning whether the current implementation is the best one for the users and developers. We can gladly move this conversation to Discussions or Discord if better suited, but I thought I'd make an issue because some things seemed a little inconsistent or out-of-date to me.

The new sv CLI
Database
sv introduces the possibility to quicky add drizzle, which helps defining data structures, initializing the schema and some more useful things. My suggestion would be to use drizzle for database management. Database Management is also where the v2 branch is broken: db:init throws an invalid syntax error (even though the database seems to be initialized without any problems). Another problem is inconsistent naming. The schema specifies a content table which is later refered to as published_content, causing multiple errors. Drizzle would drastically reduce mistakes like this.
User Authentication
sv introduces the possibility to quickly add lucia, but I don't know if the lucia implementation is better or worse than the implementation used in v2. The code of the v2 implementation was not reviewed or tested, so I can't really tell.
Internationalization
sv introduces the possibility to quickly add paraglide, which would add the option of translating sveltesociety.dev, making it available for more people. I recommend adding i18n, but since svelte.dev isn't translated either, this is just a suggestion.
Why the monorepo?
The v2 branch is currently structured like this:
- nginx        (Reverse proxy config)
- packages
  - ui         (SvelteKit library project)
- sites
  - www        (SvelteKit website project)

This is great if you want to manage multiple packages or sites in a monorepo. But why do it for sveltesociety.dev? I mean, yeah, you could put all of your ui stuff in the ui package to keep your www site clean. But that hasn't happened here. The ui package does not seem to contain anything (nor is it included as a dep in www), and there also aren't multiple packages or sites, making the monorepo structure seem unnecessary.
So what are other reasons one might still want to structure the repo like this? Well, if somebody wants to use sveltesociety.dev UI components in their personal projects, this structure would certainly make it easier. But since the ui package is empty, you can't do that.
So my suggestion would be to either use the monorepo structure, or to switch to a classic single-project repo structure instead.
Design System and Brand Identity
Style Mismatch
Both the old (current) sveltesociety.dev and new v2 sites use a design system that greatly differs from the design system used on svelte.dev. Yes, Svelte and Svelte Society are two different things. But are they, really? Let's see:

Svelte
Svelte Society

Community-ran
yes
yes

References community packages
yes
yes

Contains documentation
yes
yes (recipies)

Contains tutorials
yes
yes (resources, but only links)

Contains a playground
yes
no

Contains a blog / feed
yes
kinda (v2)

Contains events
no (mentions Svelte Society)
yes

Official annoucement channel
yes
yes

So does it really make sense to split up Svelte and Svelte Society? Yes! Svelte Society is the community, and Svelte is the product. That's not the same thing and it's important to distinguish between that. But does Svelte Society need a completely different brand identity? I don't think so, especially because Svelte Society also serves official purposes apart from community purposes (Svelte Summit for example).
Accessibility
Some minor accessibility concern at first glance: The sidebar links have a smaller height than the WCAG recommended minimum of 44px. Also the sidebar section titles might be hard to read for some people due to the combination of light font weight and the text color used. I've also noticed some issues regarding keyboard navigation. Since one of Svelte's main goal is to make the web accessible, it would be weird if Svelte Society didn't have the same standards.
Conclusion
While it's cetainly possible to continue development on v2 the way it currently is, it might be helpful to make a clean restart of the development and put new technologies into use. Also, since Svelte Society is very tighly related to Svelte, I think the design of the website should represent this relation.

[!NOTE]
I'm eager to help support the development to make Svelte Society better for everyone.

BTW, I am opening an issue on v2 because I didn't like the user experience of v1, wanted to contribute, and then saw you were already working on v2.


Choreprint log before task execute

Proposed changes
Issue Number: close #xxx

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

run buildall

run feut


Update to match upstream

Coverage decreased (-0.2%) to 99.41% when pulling f912ab93ba4ecbef9b86307c6d8d80622fb19861 on CyberiaResurrection:UpdateToMatchUpstream into 0854e7dad939a9bd8487f36995d0f3349679ac77 on Algo-Web:master.


Add efs

what
Support EFS

Change setup
Add unix uid to input

Sorry I meant to merge this to my fork


[TypeScript] Currently not possible to use business variables in a theme with "withStyles"

I'm using TypeScript and I'm trying to define custom business variables in my theme, as described in the docs here.
This is what I have so far:
interface MyThemeExtension {
    status: {
        danger: string
    };
}

export const theme = createMuiTheme<MyThemeExtension>({
    status: {
        danger: orange[500]
    }
});

export type MyTheme = Theme<MyThemeExtension>;

But now I'm having trouble to use the withStyles HoC, because the theme argument of StyleRulesCallback is of type Theme. I'm no TS expert, but I think the types of Theme and StyleRulesCallback need to be changed to something like this (at least this worked for me):
type StyleRulesCallback<ClassKey extends string = string> = (theme: Theme) => StyleRules<ClassKey>;

// changed to:

type StyleRulesCallback<ClassKey extends string = string, T = {}> = (theme: Theme<T>) => StyleRules<ClassKey>;

function withStyles<ClassKey extends string>(
  style: StyleRules<ClassKey> | StyleRulesCallback<ClassKey>,
  options?: WithStylesOptions
): <P>(
  component: React.ComponentType<P & WithStyles<ClassKey>>
) => React.ComponentType<P & StyledComponentProps<ClassKey>>;

// changed to:

function withStyles<ClassKey extends string, T = {}>(
  style: StyleRules<ClassKey> | StyleRulesCallback<ClassKey, T>,
  options?: WithStylesOptions
): <P>(
  component: React.ComponentType<P & WithStyles<ClassKey>>
) => React.ComponentType<P & StyledComponentProps<ClassKey>>;

These changes allowed me to do: withStyles((theme: MyTheme) => ({...})
Again, I'm not sure if this is the correct way. Please let me know.
Your Environment

Tech
Version

Material-UI
1.0.0-beta.21

React
16.1.1

TypeScript
2.5.3

@simonvizzini yep, I think you're right about what needs to be changed. Care to open a PR? 🙂

Sooo I guess something big happened since beta.16 with how styling works. @pelotom I am looking through docs and example of what has changed. Why is there such a large breaking change from 16 to beta.21?
Why are all my styles now incorrect. Also the examples in the example project are very minimal and look very hackish and I do not understand what is going on as well. Maybe some comments would help enlighten the situation.

@marcusjwhelan it's hard to know what your issue is without a concrete example that reproduces it. If you post one I might be able to help, and as a bonus it could even serve as the basis for a less hackish example project 😃

@pelotom  with the lower half also being part of the issue https://github.com/mui-org/material-ui/issues/8824
This is the use case and how I have used withStyles.
const styles = (theme: any) => ({
    root: { /* styles **/},
    /* other styles **/
});

interface IclassStyles {
    classes: any;
}

interface InjectedProps {
    title: string;
}

interface ComponentStateProps {
    note: any;
}

type ComponentProps = IclassStyles & InjectedProps & ComponentStateProps;

class MyComponent extends Component<ComponentProps, ComponentStateProps> {
    constructor(props: ComponentProps) {
        super(props);
        this.state = {
            note: '',
        }
    }
   /* other methods and render **/
}

export const MyComponent_class = withStyles(styles)<InjectedProps>(MyComponent);

This is how it was typed in beta.16. The injected props were the properties that were required by the parent for that component to function. This was also how it was shown to many people how to do it and I currently have beta.21 and am not receiving any errors from Typescript except when I compile.
Here is an example error that every one of my components are now receiving after migrating
 ERROR in /Users/marcuswhelan/work/ClientElectron/src/renderer/containers/WorkOrder/components/Ownership_component.tsx(137,84)
      TS2345: Argument of type 'typeof WOOwnership' is not assignable to parameter of type 'ComponentType<IWOOwnershipInjectedProps & WithStyles<"root" | "formLabel" | "formControlLabel" | ...'.
  Type 'typeof WOOwnership' is not assignable to type 'StatelessComponent<IWOOwnershipInjectedProps & WithStyles<"root" | "formLabel" | "formControlLabe...'.
    Type 'typeof WOOwnership' provides no match for the signature '(props: IWOOwnershipInjectedProps & WithStyles<"root" | "formLabel" | "formControlLabel" | "labelClass"> & { children?: ReactNode; }, context?: any): ReactElement<any> | null'.

The Styles interface being separate from the component props is so that the component would not ask for styles from the parent component and have localized styling for each component that could overwrite the main theme if need be, or import properties of the main theme as seen in the documentation throughout material-ui.
Possibly related

https://github.com/mui-org/material-ui/issues/8928
https://github.com/mui-org/material-ui/issues/9141
https://github.com/mui-org/material-ui/issues/9160
https://github.com/mui-org/material-ui/issues/9192
https://github.com/mui-org/material-ui/issues/8598

Is this how it needs to be done now?

https://github.com/mui-org/material-ui/issues/8661

@marcusjwhelan I don't think your problem is related to any of the issues you linked, but rather #8824. That actually turned out to be an issue with the React typings, fixed here, so I think if you upgrade @types/react it should go away. Your example works fine for me.

and am not receiving any errors from Typescript except when I compile

What does this mean? If you're getting different TypeScript errors in one context vs. another (e.g. editor vs command line), make sure everything is configured to use the same version of TypeScript. The errors you showed here occur with TypeScript 2.6+ and --strictFunctionTypes, using the old @types/react.

@pelotom Should I remove @types/react? Does react now ship typings with their project? And the errors I am missing are the IDE highlighting. I guess there is something missing. Should I add in the flag --strictFunctionTypes to my config? I was helping out with Typescript errors from beta 9 to beta 16 but since stopped. I have a rather large project using this and have a lot of instances I can get errors from.
I will try to keep upgrading my project with each release to send in more errors if more come.

Should I remove ?

Remove what?

Does react now ship typings with their project?

No, they come from @types/react.

And the errors I am missing are the IDE highlighting. I guess there is something missing. Should I add in the flag --strictFunctionTypes to my config?

You should point your IDE to use the same TypeScript compiler and tsconfig.json as your commandline tools if you want to see the same errors in both places.

I was helping out with Typescript errors from beta 9 to beta 16 but since stopped. I have a rather large project using this and have a lot of instances I can get errors from.
I will try to keep upgrading my project with each release to send in more errors if more come.

Great, please do.

Getting back to the original issue, there's a small problem with the proposed solution, which is that it isn't type safe. Since the place where the global theme is defined is divorced from the place where we want to use it, there's no way to enforce that your global theme is a MyTheme. In fact you could claim to have any old type of theme, anywhere you use withStyles, and the type system will just happily agree with you:
  withStyles((theme: Theme<{ foo: { bar: number } }>) => ({
    root: {
      lineHeight: theme.foo.bar,
    },
  }));

It may be an ok compromise to make, I just want to point out that it's really no safer than doing a cast like this:
  withStyles(theme => ({
    root: {
      backgroundColor: (theme as MyTheme).status.danger,
    },
  }));

In general this is making me wonder why there is any advantage to using withStyles with a callback, vs. exporting your theme from a module and then importing it everywhere that you want to use it:
// src/theme.ts

import createMuiTheme from 'material-ui/styles/createMuiTheme';
import { red, purple } from 'material-ui/colors';

export default createMuiTheme({
  palette: {
    primary: red,
    secondary: purple,
  },
  myCustomScalar: 3,
});

// src/component.ts

import * as React from 'react'
import { withStyles } from 'material-ui/styles'
import theme from './theme'

export default withStyles({
  root: {
    margin: theme.spacing.unit * theme.myCustomScalar
  }
})(...);

Deleted some comments that were not pertinent to the issue.

Thanks for the insight, @pelotom! I totally agree that the proposed solution with regards to type safety doesn't make much sense, and so I will just import and use the theme directly, instead of using a callback with withStyles. Same for custom business variables, I'll just import them wherever I need them.
So this issue can be closed from my side.

Theme as global does not work if you app runs on the server-side/isomorphic (my case) and we need to have some customization per-user. In this scenario theme as it is is really helpful. I seens to me that Theme with Parameterized type would be a better solution since it does not block you from using theme as global variable/require when suitable.

Even though this bussines variables are theme related?

@gariggio I suggest taking a look at this page for the latest best practice for customizing the theme in TypeScript:
https://material-ui-next.com/guides/typescript/#customization-of-theme


added deeplab + depth cropping experiment

Looks awesome - thanks!  Once we have the depth-RGB alignment released (https://github.com/luxonis/depthai-python/pull/147), we should update this to allow running off of right or RGB (and when run off RGB, we enable the depth-RGB alignment enabled.


Add target to download nanoCLR on build

Description

Add target to download nanoCLR file on build.

There is a shortcoming though, derived from the fact that nfproj is not fully supported by nuget. When updating the Test Framework nuget the import path is not automatically updated on the nfproj file. The same goes when adding the Test Framework NuGet package "in cold". The Unit Test template will include this out-of-the-box.
The msbuild tasks is set to continue on error, therefore not being able to download nanoCLR won't ever break the build.
Plus the Test Framework includes a copy of the nanoCLR to make the build possible out-of-the-box and even without the import of the correct target.
Motivation and Context

Need to be able to use the latest nanoCLR version without having to constantly update and publish the Test Framework nuget package.

How Has This Been Tested?

POC solution.

Screenshots
Types of changes

[ ] Improvement (non-breaking change that improves a feature, code or algorithm)
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Config and build (change in the configuration and build system, has no impact on code or features)
[ ] Dependencies (update dependencies and changes associated, has no impact on code or features)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

@nfbot updatedependents


name-suggestion-index should be time-aware

OHM’s fork of iD currently uses the mainline name-suggestion-index for brands and operators. This is fine in general, but OHM has some needs beyond OSM, for example:

Defunct brands that NSI considers “dissolved”, such as Blockbuster Video
Historical brands that NSI has never known about, such as the Burger Chef restaurant chain and (I kid you not) the McKids clothing store chain
Renamed brands, such as Domino’s (formerly Domino’s Pizza) and 76 (formerly Union 76); some chains have joined and left the Big Boy franchise over the years
A validator warning when a feature is tagged as belonging to a brand but existing before the brand came into existence or after it went out of business

In principle, each NSI entry should have properties indicating its start and end dates, and separate entries would represent older versions of a brand. However, this could be quite a bit of extra complexity for the main NSI project. Forking would come with its own extra overhead; NSI changes almost every day and most of the changes would reasonably apply to OHM. Maybe an OHM project could extend NSI with what it needs but still consume the main project?
/cc @bhousel @tas50

I don't think that we even need to fork NSI. We can just create a historical NSI repo where we store only historical data and reuse NSI's build script to compile our data. Then iD could (in theory) merge the historical NSI and current NSI during runtime.
NSI could add start_date to the meta tags of brands (and end_date won't be needed since these entries can be moved to the historical NSI where the end dates can be stored). In case NSI maintainers are not ok with having start and end dates, we can create our own list for it. Something like this:
[
    "branda-dsdsc": {"start_date": "2000", "end_date: "2011-05"},
    "brandb-ljhjkkj": {"start_date": "2010-12-15", "end_date: "2015-06"}
]


multicast setsockopt fail, errno = 92( Protocol not available)

Hi,
this is a old question. I user bellow code to create a udp multicast server, but join a mcast group failed.
the test code is find to PC.
   #define LWIP_IGMP 1         // first, make LWIP_IGMP is 1

// join a mcast group
struct ip_mreq mreq;
mreq.imr_multiaddr.s_addr = inet_addr(MCAST_ADDR);	// mcast group ip
mreq.imr_interface.s_addr = htonl(INADDR_ANY);      // local ip
ret = setsockopt(sock_fd,IPPROTO_IP,IP_ADD_MEMBERSHIP,&mreq,sizeof(mreq));
if(ret < 0) {
	WARNING("setsockopt() fail-%d:IP ADD MEMBURSHIP", errno);

//		goto __exit;
}
the debug msg printf  "errno = 92", Macro definition as follows:
#define  ENOPROTOOPT  92  /* Protocol not available */
Hope that the engineer can solve this problem, Thank you very much.

Did you rebuild lwip?  As you pointed out LWIP_IGMP is not set in the prebuilt bins.

yes, i rebuid it.  Now I'am use udp broadcast to find device,  feel that  efficiency is not high.


无法在本地开发

Describe the bug
我在本地拉取项目，但是在执行air -c scripts/.air.toml时全部超时，我也开了代理
Steps to reproduce
air -c scripts/.air.toml
Screenshots or additional context

Please check your network. This is not a bug related to memos.

@xyhcode  hi ,did you resolve this problem? I tried go intall air many times but none of them successful ? if you were ok could you help me for a little while? Thank you.


Tensorflow.python.framework.errors_impl.InvalidArgumentError: 2 root error(s) found.

System information

Tf 2.2.0
Windows10
Python version: 5.7.6
git version v2.2.0-rc4-8-g2b96f3662b

When I pass class_weight to model.fit() this error comes and when I do not pass it goes? any idea how to solve it?
`
Tensorflow.python.framework.errors_impl.InvalidArgumentError: 2 root error(s) found.
(0) Invalid argument:  indices[84] = 31 is not in [0, 31)
[[{{node GatherV2}}]]
[[IteratorGetNext]]
[[ReverseSequence_1/_502]]
(1) Invalid argument:  indices[84] = 31 is not in [0, 31)
[[{{node GatherV2}}]]
[[IteratorGetNext]]
0 successful operations.
0 derived errors ignored. [Op:__inference_train_function_28314]
Function call stack:
train_function -> train_function
`
`       model_input = tf.keras.layers.Input(shape=(timesteps,), dtype='int32')
self.createBertLayer()
    bert = self.bert_layer(model_input)

    self.d = tf.keras.layers.Dense(num_hiddens, activation=tf.nn.relu)(bert)
    h = tf.keras.layers.Dropout(0.5)(self.d)
    self.y1 = tf.keras.layers.Dense(classes, activation=tf.nn.softmax)(h)

    self.crf = CRF()
    output = self.crf(self.y1)

    model = Model(model_input, output)
    model.build(input_shape=(None, timesteps))
    self.bert_layer.apply_adapter_freeze()
    self.bert_layer.trainable = False

    model.compile(loss=self.crf.loss, optimizer=tf.keras.optimizers.Adam(0.001), metrics=[self.crf.accuracy])

    history = self.model.fit(
        training_set,
        training_label,
        class_weight=class_weights,
        epochs=n_epochs,
        # validation_data=(testing_set, one_hotted2),
        validation_split=0.1,
        verbose=1,
        batch_size=256
        # callbacks=[cp_callback]
    )

`
I checked class_weight keys and there was no problem with it.

@mahdiabdollahpour,
On running the code, I'm facing an error stating NameError: name 'timesteps' is not defined. Please find the gist of it here.
In order to expedite the trouble-shooting process, could you please provide the complete code to reproduce the issue reported here. Thanks!


Improve error handling for to_apify_request serialization failures

The PR addresses the problem identified in Issue #189, where to_apify_request could fail silently during serialization of the Scrapy request. This PR has introduced enhanced error handling to ensure users are informed if serialization of a request fails, preventing the request from being not enqueued without notification.

Maybe we should log it as errors rather than warnings, since it actually is an issue that the developers should solve. But I agree that it's better to not fail the whole Actor in this case.

Ok, enqueue_request logs an error message when the conversion fails.


Adding new forms engine.

Merge after:
https://github.com/droolsjbpm/droolsjbpm-build-bootstrap/pull/252
Adding forms engine I:

Added API
Layout Generation
Dynamic Form Engine*

Adding forms engine II:

Added Form Editor
Added Form Widgets

Adding forms engine III:

Fixing issues generating dynamic-forms with ListBoxes that user SelectDataProvider

Adding forms engine IV:

Added CRUD component
Fixing small issues

Test's are also failing on master. I'll take a look tomorrow.

Ok over 300 files. Is this all just being moved from location A to B?

jenkins retest this.

@Rikkola yes,  it was placed on the livespark repo.  It has to be moved here to be used by other components.

Should we perhaps migrate the whole git history? Or was it decided not to do so for some reason?

@psiroky not needed. This is only part of the LS work...related to forms which needs to be re-usable in other projects.

@csadilek great, thanks for the explanation!

Jenkins, please retest this.

@pefernan Normally I'd add inline comments where appropriate, but there are so many files that looking at the diff in GitHub is too slow so I've aggregated all my notes here.
First I'll say great stuff, Pere! I've tried out LS with the changes in this and related branches and it's all working quite well.
That being said, here are some issues I noticed:

There are some types in your test cases that you call mocks, but they are not really mocks: DynamicFormRendererMock, MockFieldManager, FormFieldProviderMock, and FormHandlerMock. These are actually testable subclasses of the types being tested (you never mock something you are testing; you mock the types you are not testing). A more accurate naming convention would be to use the prefix "Test" or "Testable" (i.e. TestFieldManger or TestableFieldManager).

The PictureWidgetDriver has a significant amount of JavaScript code and no tests. I think there's enough going on there to be at least a single test. Also if you ever need to modify this type in the future, I think it would be worth while to try and reduce the amount of JS (probably by using JSInterop), but that's less important than there being some test coverage.

The DynamicFormRendererTest.doBind method has some verify statement inside a callback. The test would be more reliable if you verified that this callback is invoked (it could just never be invoked and the test would pass).

The FormDefinitionSerializerImplTest.doSerializationTest method uses assertNotSame to compare integers, but ought to use assertNotEquals (the former is less reliable since the parameters will be auto-boxed to Integers, at which point they could be different object references while both representing the same int).

The FormEditorPresenterTest has a couple blocks with commented out code that ought to be deleted.

@romartin if you haven't already done so, it would be great if you could take a look at this tomorrow to see it all works for you.
@Rikkola this will be worked on more in the next couple of months, but it would be great if you could take a look as well.
Thanks.

@csadilek I think that @romartin is on vacation until september. Maybe we can wait to merge it until then, I can spend the time fixing the comments Max provided.

We try to make a separate class for the MVP View interface. I see here it was usually in the Presenter. Wouldn't change this for this PR, just something to keep in mind in the future.
Over all I think the code is even better than the existing kie-wb-common code. Short, clean and easy to read. Test coverage is not the best. We should try to raise the coverage when new features go in or bugs are fixed, but if this code is just moved from one location to another ( = QA has tested it and probably has some UI tests ) then I don't see a reason to block the PR because of this.  The JavaScript should have at least one test so who ever works on this code in the future has an example and a starting point.
Another thing that I might want to bring up is the location of the codes. Currently they are in the root as kie-wb-common/kie-wb-common-forms. kie-wb-common is split into 3 sections screens, services and widgets. I believe all this should go into screens ( kie-wb-common/kie-wb-common-screens/kie-wb-common-forms ).

So @manstis was ok with this location. I still feel it might be best to place it in screens, but I can live with this location and then we change it later if possible.

Added some changes as @mbarkley suggested, pending add testing to PictureWidgetDriver

+1 (Since Pere is starting PTO now, better to merge now and get the last test when he returns.)

Thanks @mbarkley and @Rikkola for the reviews. I will go ahead an merge this as it will get us unstuck. Also, the quality is rather high for work in progress and other projects (except Stunner and LiveSpark) are currently not affected.
+1


Add export and import keyboard settings in the "Keyboard Manager"

📝 Provide a description of the new feature
Please add an export and import keyboard settings file in the in the "Keyboard Manager". It can help us to export our settings to other computers 👍👍👍👍

closing as duplicate of #1881. work is being tracked there and in #4452


Add nanprod_along_batch to BatchedArray

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

Comparison is base (a24786d) 100.00% compared to head (67a175e) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #555   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           24        24
  Lines         1997      2005    +8
  Branches       263       263
=========================================
+ Hits          1997      2005    +8

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


Add script to update history.md

As discussed at CukenFest, this will avoid manual error when updating
history. It still needs to be run manually, and requires that one of the
type: * labels has been applied to the PR.
It's still going to save me time!

❤ this!

Sweet!


cargo-deny action failure --possibly due to use of a beta on crates.io?

Describe the bug
I've created a very basic project illustrating the problem I'm experiencing during a CI run:  https://github.com/daringordon/cargo_deny_error_reproduction/runs/3701686133?check_suite_focus=true#step:4:9
Is the problem related to use of a beta version crate?  Thanks for checking.
Device:

OS: Debian Stretch
Version:  latest cargo deny action v1

I believe this is because you have set CARGO_NET_GIT_FETCH_WITH_CLI. The cargo-deny-action doesn't include the git executable so that fails, is there a reason you are using CARGO_NET_GIT_FETCH_WITH_CLI? If there is you would need to install git before running cargo-deny.

@Jake-Shadle CARGO_NET_GIT_FETCH_WITH_CLI was necessary to address an error that triggered before this one: cargo-deny's runtime was failing to access private github repositories, despite that ssh-agent is set up for the workflow and used successfully in other tasks.  Removing CARGO_NET_GIT_FETCH_WITH_CLI did clear this issue, leaving me to deal with the prior one again.

Ahh I see, I would open a bug on cargo-deny-action then to include git in the container.


Jquery callback for input fields

I created a set of input fields that accepts numbers and planned to sum the inputted numbers somewhere, but jquery callback doesn't work with newly duplicated items.

DR

                                                    <input type="text" class="form-control dr" name="DR"
                                                           placeholder=""/>

CR

                                                    <input type="text" class="form-control cr" name="CR"
                                                           placeholder="" />

   $('.cr').blur(function () {
        var sum = 0;
        $('.cr').each(function () {
            sum += Number($(this).val());
        });
        $('.total-cr').html(Intl.NumberFormat('en-US', {}).format(sum))
    });
 $('.dr').blur(function () {
        var sum = 0;
        $('.dr').each(function () {
            sum += Number($(this).val());
        });

        $('.total-dr').html(Intl.NumberFormat('en-US', {}).format(sum))
    });

@ladaposamuel any chance you got this working?

@ladaposamuel any chance you got this working?

Decided to go a different route using vuejs

Oh alright. Anyways, I figured out a way to handle this.
All you have to do is add a event listener in the repeater show function.

Oh alright. Anyways, I figured out a way to handle this.
All you have to do is add a event listener in the repeater show function.

Can you put a snippet here for any future person that stumbles on this issue too. :)