security/acme-client 4.4 Error in log while exit code = 0

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[ x] I have read the contributing guide lines at https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md
[x ] I have searched the existing issues, open and closed, and I'm convinced that mine is new.
[x ] The title contains the plugin to which this issue belongs

Describe the bug
A clear and concise description of what the bug is, including last known working version (if any).
When renewing certificate everthing worked as expected, but in the general log file the output is marked as an error.
2024-08-02T09:09:20	Error	opnsense	/usr/local/opnsense/scripts/OPNsense/AcmeClient/lecert.php: AcmeClient: The shell command returned exit code '0': '/usr/local/sbin/acme.sh --renew --syslog 6 --log-level 1 --server 'letsencrypt' --dns 'dns_desec' --dnssleep '300' --home '/var/etc/acme-client/home' --cert-home '/var/etc/acme-client/cert-home/6579eb1d6ceb77.09776905' --certpath '/var/etc/acme-client/certs/6579eb1d6ceb77.09776905/cert.pem' --keypath '/var/etc/acme-client/keys/6579eb1d6ceb77.09776905/private.key' --capath '/var/etc/acme-client/certs/6579eb1d6ceb77.09776905/chain.pem' --fullchainpath '/var/etc/acme-client/certs/6579eb1d6ceb77.09776905/fullchain.pem' --domain '.XXX.nl' --challenge-alias 'XXX.dedyn.io' --domain '.XXX.eu' --challenge-alias 'XXX.dedyn.io' --domain '.XXX.com' --challenge-alias 'XXX.dedyn.io' --domain '.XXX.info' --challenge-alias 'XXX.dedyn.io' --domain '.XXX.net' --challenge-alias 'XXX.dedyn.io' --domain '.XXX.nl' --challenge-alias 'XXX.dedyn.io' --days '1' --keylength '4096' --accountconf '/var/etc/acme-client/accounts/6579cc04a21901.65345385_prod/account.conf'
Also marked as an error is the automation.
2024-08-02T09:10:03	Error	config	/usr/local/opnsense/scripts/OPNsense/AcmeClient/lecert.php: AcmeClient: The shell command returned exit code '0': '/usr/local/sbin/acme.sh --deploy --syslog 6 --log-level 1 --server 'letsencrypt' --home '/var/etc/acme-client/home' --cert-home '/var/etc/acme-client/cert-home/6579eb1d6ceb77.09776905' --certpath '/var/etc/acme-client/certs/6579eb1d6ceb77.09776905/cert.pem' --keypath '/var/etc/acme-client/keys/6579eb1d6ceb77.09776905/private.key' --capath '/var/etc/acme-client/certs/6579eb1d6ceb77.09776905/chain.pem' --fullchainpath '/var/etc/acme-client/certs/6579eb1d6ceb77.09776905/fullchain.pem' --domain '*.XXX.XXX' --deploy-hook synology_dsm'
Tip: to validate your setup was working with the previous version, use opnsense-revert (https://docs.opnsense.org/manual/opnsense_tools.html#opnsense-revert)
To Reproduce
Steps to reproduce the behavior:
Renew or issue certificate
Expected behavior
Severity marked as "notice"
Screenshots
If applicable, add screenshots to help explain your problem.
Relevant log files
If applicable, information from log files supporting your claim.
Additional context
Add any other context about the problem here.
Environment
Software version used and hardware type if relevant.
e.g.:
OPNsense 24.7_9 (amd64).
Intel N100

Duplicate of https://github.com/opnsense/plugins/issues/3955.


transformStyle eats errors

Given this in .codelyzer.js
module.exports = {
    transformStyle(code, url, decorator) {
        throw new Error('Something went horribly wrong');
    },
};

When running the lint task it will not display the error, which makes it look like the styles are passing lint!
transformTemplate does not suffer from the same issue.
Node: 6.9.1
Tslint: 4.0.2
Codelyzer: 2.0.0-beta.3
Angular: 2.2.3

It's intentional to not throw when a style is not transformed successfully but this doesn't eat linting errors.

😕 Lost a couple hours due to this. No warning whatsoever that your transform or styles are broken is pretty worrying to me

I agree, I will add a bolded warning to the README.md file.


Fixes "crashes on fetch list of media" (#180)

I encountered the same problem as described in issue OokTech#180. The server crashed, displaying "ReferenceError: path is not defined." This simple patch fixed the problem.

I don't remember why I didn't merge this, but I did put the change into the code. So I am closing this pull request.


Revise words.hk parsing script

In the discussion of Issue #29, it was brought to my attention that words.hk provides a downloadable, parseable file of all the entries in the dictionary at this link (Thanks, @hnfong!).
The old implementation scrapes all the webpages and then parses each of the downloaded files; this is brittle (prone to breaking if the structure of the webpage changes, as it has twice since mid-2020 when the initial scrape was done), and might not be the best for words.hk's servers.
This new implementation should download the provided file from that link, and then parse the downloaded file into the Jyut Dictionary database format.

I finally managed to add support for inline # links! The words.hk format looks simple at first sight but has many exceptions.  They are extremely rare but nevertheless do show up. Also, words.hk syntax for inline # links is not very bulletproof, because they actually allow punctuations in entry names like "A.math". So you might theoretically see links embedded in an English explanation like this: "See #A.math." You can't be certain which period '.' should be the word boundary here. Luckily, entries like A.math are extremely rare and I haven't seen people linking to such entries.
And since words.hk doesn't have an editor preview nor syntax checker on their dictionary page, contributors sometimes make syntax mistakes. I detected about ten mistakes just by running my parser through the CSV file. I have fixed all of them through the website, so now the parser should be able to parse everything correctly (at least the things in my test cases).
I'll add a README and some documentation for the parser soon.

Nice! That's some solid progress. I think I saw some discussion in editor groups for adding non-standard Jyutping to entries (e.g. 'sgen1' for the entry 'scan') - is that something your crate deals with at all, or do you take whatever string is in that field with no other processing?

My crate currently parses everything between the '(' and ')' after the sentence as a jyutping clause. I haven't attempted to parse the individual pronunciations because the syntax they have is quite wild... You can have '!' for incompatible sounds or as a fill-in-the-blank sort of thing. I did take a look at their Django backend code. They seem to handle some edge cases like the '!' I mentioned above. I'm gonna look into it further.

I managed to export words.hk to Apple Dictionary! The layout is quite similar to the website's though I need to tinker with the spacing more. I also finished all the docs and README and they are all on https://github.com/AlienKevin/wordshk-tools. With regard to the Jyutping parsing, I haven't implemented it in my parser because I see benefits in both the ruby approach (words.hk does this) and having a standalone Jyutping sentence underneath the Chinese characters (jyut-dict does this). It is hard to decide on which one to pick plus I'm kinda lazy. So I chose the standalone approach for now.

Nice! That's some solid progress. I think I saw some discussion in editor groups for adding non-standard Jyutping to entries (e.g. 'sgen1' for the entry 'scan') - is that something your crate deals with at all, or do you take whatever string is in that field with no other processing?

I finally managed to match the Jyutping with the words! I used a variant of the Longest Common Subsequence algorithm, which you can see in this commit. My (hopefully) finalized port of words.hk to Apple Dictionary looks like below:

@aaronhktan Happy holidays! How are you doing? I published my rust library as wordshk_tools to crates.io. Feel free to use any of the functions in the library for parsing. Complete docs for each function are on docs.rs. I'm not familiar with Qt but it seems that your library uses C++ and python. Rust offers C bindings and dylib generation that can be called in both C++ and python, so it might work with your library.
Here are some functions that might be useful:

parse_dict: Parse the entire CSV source file into a struct called Dict.
Quirks: need to manually remove the first line of metadata generated by the server during download
parse_jyutping: Parse a Jyutping (customized for words.hk)
Quirks: do not handle weird edge cases with '!', or currently invalid jyutping forms like "!sdet3" that begins with a '!'

Happy holidays!
That's great! I don't have much experience with Rust, but I'll check it out. Seems like really good work, thank you for doing this!


Example on how to define a custom panel in Python.

Is it possible to extend Editor UI using python as we do in C# dockable panels?

It is definitely possible, but also probably quite hard. I don't think it is easy to write WPF code in python, but it would not be the supported way of doing it.
At that point, I'd suggest writing it in C# instead. I am not sure I agree that this is an example we should have.

This will not be fixed.


Implement single line if-else formatting

Closes https://github.com/nrc/rustfmt/issues/92, https://github.com/nrc/rustfmt/issues/32.

looks good, r+ with the minor comments addressed and a rebase

I've added a gross hack to format nested if-else expressions correctly. Could you have a quick look at this, @nrc or @cassiersg?

r+
(And your hack isn't that hacky :smile:)


[AutoPR servicebus/resource-manager] Py conf SB 0.5.0

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/2957

(message created by the CI based on PR content)


auxiliary output

"We employ a cross-entropy loss and add an auxiliary output head together with an auxiliary loss to the output of the penultimate fusion layer."
According to your paper,the resolution of the auxiliary output is one-fourth of the input image. Do you upsample the auxiliary output to input？How do you design the auxiliary loss?

Yes, the output of the auxiliary layer is upsampled to the shape original size using bilinear upsampling. The auxlayer is specified in the inference code. It is applied to "path_2" in the DPT base model.
For fine-tuning:

Our code is based on PyTorch encoding https://github.com/zhanghang1989/PyTorch-Encoding. This should be a good starting point.
The hyper-parameters are listed in the paper. Please let us know if anything here is unclear, ambiguous, or missing.

Thanks for your reply!


script variable don't save if node is child of instanced scene

When I change in this view the script variables it will not save.

Only when opening scene (exp. selection) and then setting the variables it works.

yeah this is by design, but design will change for godot 1.1 and you will
be able to save them
On Wed, Mar 4, 2015 at 3:12 PM, puppetmaster-<EMAIL_ADDRESS>wrote:

When I change in this view the script variables it will not save.
[image: script_variable_bug]
https://cloud.githubusercontent.com/assets/10463138/6489732/1c354718-c2a1-11e4-9ccc-a9be7b856b97.png
Only when opening scene (exp. selection) and then setting the variables it
works.
—
Reply to this email directly or view it on GitHub
https://github.com/okamstudio/godot/issues/1478.

Are this the latest build(1.1)? http://sourceforge.net/projects/godotengine/files/Builds/official/

oh sorry, i meant it will change for Godot 1.2. Godot 1.1 will be out soon,
then work will start in 1.2
On Wed, Mar 4, 2015 at 3:27 PM, puppetmaster-<EMAIL_ADDRESS>wrote:

Are this the latest build(1.1)?
http://sourceforge.net/projects/godotengine/files/Builds/official/
—
Reply to this email directly or view it on GitHub
https://github.com/okamstudio/godot/issues/1478#issuecomment-77215464.

Subscene editing has been implemented for 2.0.


android build  release failed  "react-native": "0.57.0",

"react": "16.5.0",
"react-native": "0.57.0",
FAILURE: Build failed with an exception.
i try
release {
...
matchingFallbacks = ['debug', 'qa', 'release']
}
but failed

What went wrong:
Execution failed for task ':app:lintVitalRelease'.

Could not resolve all artifacts for configuration ':app:releaseStagingRuntimeClasspath'.
Could not resolve project :react-native-fast-image.
Required by:
project :app
Unable to find a matching configuration of project :react-native-fast-image:
- Configuration 'debugApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'debug'.
- Found com.android.build.api.attributes.VariantAttr 'debug' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-runtime' and found incompatible value 'java-api'.
- Configuration 'debugRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'debug'.
- Found com.android.build.api.attributes.VariantAttr 'debug' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-runtime' and found compatible value 'java-runtime'.
- Configuration 'releaseApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'release'.
- Found com.android.build.api.attributes.VariantAttr 'release' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-runtime' and found incompatible value 'java-api'.
- Configuration 'releaseRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'release'.
- Found com.android.build.api.attributes.VariantAttr 'release' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-runtime' and found compatible value 'java-runtime'.

success ， The solution =》 implementation project(path:':react-native-fast-image', configuration:'default')


fix(internet-header): add aria-label on skiplinks ul element

Preview environments are getting posted here, as soon as they are ready!

I checked the current Post Portal and the title "Navigieren auf post.ch" is used for the whole header:

While in you solution it is used for skip links only:


Repo no longer working after integration enabled

It seems that this repo is no longer properly getting PR's after the integration was enabled, even though it disabled the previously active "individual repo" mode. A dependency (stylelint) which is pinned to 7.5.0 released an update to 7.6.0 but no PR has been submitted.
Is this because the repo was already up to date when the integration was enabled, so it never got the initial update all PR? Other repos in the organization are working properly.

I seem to be having a similar issue. I noticed the problem with this repo last night and tried to configure settings for the integration. However, I get a message stating

Already installed on all repositories

However, it is clearly not keeping dependencies up to date, because I have the following list from npm outdated:
Package                            Current         Wanted        Latest  Location
@pact-foundation/pact-node           4.5.3          4.5.3         4.5.4  travi.org-admin
@travi/any                           0.6.1          0.6.1         0.7.0  travi.org-admin
babel-core                          6.18.0         6.18.0        6.18.2  travi.org-admin
babel-loader                         6.2.7          6.2.7         6.2.8  travi.org-admin
babel-preset-stage-2                6.17.0         6.17.0        6.18.0  travi.org-admin
clean-webpack-plugin                0.1.13         0.1.13        0.1.14  travi.org-admin
coveralls                          2.11.14        2.11.14       2.11.15  travi.org-admin
css-loader                          0.25.0         0.25.0        0.26.0  travi.org-admin
dotenv-safe                          2.3.3          2.3.3         3.0.0  travi.org-admin
enzyme                               2.5.1          2.5.1         2.6.0  travi.org-admin
extract-text-webpack-plugin   2.0.0-beta.3   2.0.0-beta.3         1.0.1  travi.org-admin
good-squeeze                         5.0.0          5.0.0         5.0.1  travi.org-admin
grunt-cucumberjs                    0.10.7         0.10.7        0.10.8  travi.org-admin
history                              4.3.0          4.3.0         4.4.0  travi.org-admin
istanbul                     1.1.0-alpha.1  1.1.0-alpha.1         0.4.5  travi.org-admin
jsdom                                9.8.1          9.8.1         9.8.3  travi.org-admin
lodash                              4.16.4         4.16.4        4.17.2  travi.org-admin
newrelic                            1.32.0         1.32.0        1.34.0  travi.org-admin
nock                                 9.0.1          9.0.1         9.0.2  travi.org-admin
node-sass                           3.10.1         3.10.1        3.13.0  travi.org-admin
react                               15.3.2         15.3.2        15.4.0  travi.org-admin
react-addons-test-utils             15.3.2         15.3.2        15.4.0  travi.org-admin
react-dom                           15.3.2         15.3.2        15.4.0  travi.org-admin
react-helmet                         3.1.0          3.1.0         3.2.2  travi.org-admin
react-hot-loader              3.0.0-beta.5   3.0.0-beta.5  3.0.0-beta.6  travi.org-admin
react-redux                          4.4.5          4.4.5         4.4.6  travi.org-admin
snyk                                1.19.1         1.19.1        1.20.0  travi.org-admin
stampit                              3.0.4          3.0.4         3.0.6  travi.org-admin
webpack                      2.1.0-beta.22  2.1.0-beta.22        1.13.3  travi.org-admin
webpack-dev-server            2.1.0-beta.4   2.1.0-beta.4        1.16.2  travi.org-admin
xhr                                  2.2.2          2.2.2         2.3.0  travi.org-admin

This problem appears to be far more prevalent than I thought. Using the v11 release of eslint-config-airbnb-base I'm seeing 38% of the repositories appearing to be completely ignored currently!
Repositories with no update PR:

linter-haml
linter-htmlhint
linter-js-yaml
linter-markdown
linter-moonscript
linter-puppet-lint
linter-rubocop
linter-ruby
linter-shellcheck
linter-stylelint
linter-stylint
linter-swagger
linter-tslint

Note that none of the above repos got the Update dependencies to enable Greenkeeper PR, I assumed that was because they were up to date when it was enabled on the organization, but maybe that was a sign of problems to come.
There are also 13 more repositories that might have issues, but they have pending PR's from the old method of enabling Greenkeeper that haven't been merged as of yet, so I'm not going to count them as broken as of yet.
Is there any information that I can provide to help diagnose what is going on here?

Okay, found the badge link and went through and checked the status of all of the repos in the organization to find that 53 repos never got enabled that should have been. It seems that the integration stopped processing after 30 repos!
The integration screen of course shows everything as perfectly fine:

You can see the status in the spreadsheet tracking this here.
@finnp I'm tagging you here as you seem to be the one responding to things currently and this is a major bug that needs attention.

@Arcanemagus could you give more detail about the "badge link" that you found? I'm definitely seeing this issue in many repos. At least seeing some confirmation of the ones that are not enabled would help me understand what is happening a bit better.

@Arcanemagus Seems like we lost some jobs when you installed Greenkeeper, because we didn't used to handle GitHub outages properly. I've rescheduled them, and now you should see a lot of initial PRs 😄  Sorry about that!

@travi I see you are already merging PRs 😄  I rescheduled your jobs as well.  Here's how you use the badges:  ![greenkeeper badge](https://badges.greenkeeper.io/travi/hapi-react-router.svg) ->

yes. looks like they came through.
thanks a ton for getting this resolved

@finnp what is the expectation for repos that were added after the greenkeeper integration was added to an org?
i added the badge you mentioned to a (private) repo that was created 7 days ago and the badge reports "not found". this repo did not receive a PR as a result of the rescheduling that you ran this morning, but we do have other private repos that seem to be working correctly.
is this related, or a separate issue?

@finnp Thanks for taking care of this! If it's feasible you might think about rescheduling all the orgs enabled before handling of outages was put in place as there are most likely others out there that haven't caught that Greenkeeper isn't enabled for all of their repos.

@travi This is because the greenkeeper badges are public, so we can not show the repository status for private repositories. However we're rolling out a feature soon, where badges in private repos can be used by adding a token to the badge url.
@Arcanemagus Yeah, that's a good suggestion, we'll probably do something like this soon :)

ah, that makes sense. now that i know that badges are available, i am interested in adding them. is there an issue that i can follow to track progress for the ones for private repos?


Does order by filter results also ?

Package Name:
'@azure/cosmos'
Package Version:
v3.5.3
Operating system:
[ ] nodejs

version:

[ ] browser

name/version:

[ ] typescript

version:

Is the bug related to documentation in

[ ] README.md
[ ] source code documentation
[ ] SDK API docs on https://docs.microsoft.com

Describe the bug
I'm really surprised to discover that Cosmos DB filters out the documents that don't have the property of the order by clause.
I have 16 documents in my database but 2 of them do not have any 'foo' property. If i do a simple
SELECT VALUE c FROM c
I get 16 documents no problem. But if i do
SELECT VALUE c FROM c ORDER BY c.foo
I only get 14 documents !
I think i should still be getting 16 documents with the 2 items without 'foo' property at the end or the beginning ?
Most of the Databases I've worked with in my carrer would return 16 documents, how Cosmos DB is different ?
To Reproduce
Steps to reproduce the behavior:
1.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

@abouroubi This is by design. ORDER BY pulls from the index and undefined values are not indexed by default. The solution can be found in this docs: https://docs.microsoft.com/en-us/azure/cosmos-db/sql-query-order-by#remarks You will need to add an explicit index to the property you are ordering on:
{
    "indexingMode": "consistent",
    "automatic": true,
    "includedPaths": [
        {
            "path": "/*"
        },
        {
            "path": "/foo/?"
        }
    ],
    "excludedPaths": [
        {
            "path": "/\"_etag\"/?"
        }
    ]
}

Thanks for the answer @southpolesteve, I haven't read the note that explain the solution, because it says when using .NET SDK which I'm not, I'm using the JavaScript one.
Maybe this should be fixed in the doc

Agreed. I have opened a docs PR https://github.com/MicrosoftDocs/azure-docs/pull/45992


[scheduler] Better Semantics and Naming for SchedulerHandle Functions

Description
Currently, SchedulerHandle is used to refer to both short-living and long-living operations.
The problem here is that each of these take different life-cycle paths and end up having different semantics on when their underlying reference counting is updated on WakerPageRefs.
This design does not expose a clear interface and function names do not help either.

This is also related to #593


latest RC compatible to node.js 4.8.4

Hi,
node.js below version 4.8.4 has security problems. https://nodejs.org/en/blog/vulnerability/july-2017-security-releases/ . We want to update our RC this security fix. Is RC compatible with it?

uups, sorry, wrong project. how can i move to RocketChat repository


Add a basic CI pipeline (.github/workflows/main.yml)

This PR introduces a GitHub Actions workflow for the PoseLib project. This new CI/CD pipeline will automate various tasks including code compilation, optional benchmarking, and code syntax validation.

Environment: Ubuntu-latest
Dependencies: Eigen3
Build tools: CMake

Optional Benchmarking: Includes an option to manually run benchmark tests.
Trigger: Manual (via GitHub UI)
Condition: Only runs if manually triggered and runBenchmark is set to 'true'.

CODEOWNERS
This PR also introduces the use of this file [.github/CODEOWNERS](https://github.com/PoseLib/PoseLib/blob/78b37b6269f59d9cc6c9add59042cab7e67be0f4/.github/CODEOWNERS) that forces us to be added automatically to each PR as reviewer.
Master branch restrictions
Now we master is more protected. In order to accept a PR, it needs to pass the CI pipeline and be accepted for at least one reviewer.

Looks good to me, but I also don't know anything about GitHub Actions. Perhaps @Parskatt has a better overview.

Came down with a cold, so currently out of order 🙃 The previous PR looked good.

From: Viktor Larsson @.>
Sent: Sunday, October 1, 2023 11:51:11 AM
To: PoseLib/PoseLib @.>
Cc: Johan Edstedt @.>; Mention @.>
Subject: Re: [PoseLib/PoseLib] Add a basic CI pipeline (.github/workflows/main.yml) (PR #75)
Looks good to me, but I also don't know anything about GitHub Actions. Perhaps @Parskatthttps://github.com/Parskatt has a better overview.
—
Reply to this email directly, view it on GitHubhttps://github.com/PoseLib/PoseLib/pull/75#issuecomment-1742026065, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFIIB7WYPCDMN23R6W4A3GLX5E4I7ANCNFSM6AAAAAA5NXF6VU.
You are receiving this because you were mentioned.Message ID: @.***>

As far as I can till this only compiles the C++ library (and potentially benchmark). We should make sure PYTHON_PACKAGE is set so that we check that the pybind compiles as well.

I think it would make sense to run each time the benchmark, instead of being optional. It doesn't take so much time actually. I will change, let me know if you disagree.

There are unit tests in the WIP progress branch https://github.com/PoseLib/PoseLib/tree/camera_models
One option would be to directly integrate the old benchmark into the unit tests (and perhaps retire benchmark/benchmark entirely)

@vlarsson  This PR is ready. Please made another pass, and approve if you agree (remember that now I can't merge it to master without approval).
Click here to see the steps in the pipeline:


SAPI Voice Change

SAPI Voice Change
Adds the ability to change the voice used by the Windows SAPI API to allow the screen reader language to be changed mid-game. An English language voice, like Microsoft David, would not be able to correctly read Spanish content so a Spanish language voice, like Microsoft Sabina, is required. This is intended for use in public installations where a user cannot configure their preferred language as they would on their own personal device. The language can now be changed in-game and be read correctly by the Windows SAPI API. This only works with the Windows SAPI API.
WindowsTTS.cs
Adds SetVoice(string name) function to WindowsTTS class. This will use the WindowsTTS dll to change the voice used by the Windows SAPI API. Takes the Name attribute of an installed SAPI voice as the parameter. Available names can be found in the registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech\Voices\Tokens\[voice]\Attributes.
Example
WindowsTTS.SetVoice("Microsoft David Desktop");
WindowsTTS.dll
SetVoiceSAPI function will now validate cpToken before attempting to call ISpVoice::SetVoice(cpToken). This prevents Unity crashes when invalid voice provided. Compiled, updated, dll added to Plugins/x86_x64 directory.

This is amazing. Could you also create a 32Bit version of the compiled DLL? Otherwise this feature would only be available in the 64Bit. Granted, that's probably 99.99% of all users :D but it could lead to some really confusing bug reports

This is amazing. Could you also create a 32Bit version of the compiled DLL? Otherwise this feature would only be available in the 64Bit. Granted, that's probably 99.99% of all users :D but it could lead to some really confusing bug reports

No problem. I could actually see us being in that 1% that needs 32bit. I've got another update to enable rate changes that I was just cleaning up so I will combine it all into one pull request.

SAPI Speech Rate Change
Adds ability to change SAPI speech rate. This is intended for use in public installations where a user cannot configure their preferred rate as they would on their own personal device.
Voice Change Method Added to UAP_AccesibilityManager
Adds SetVoice(string voice) method to UAP_AccessibilityManager
Voice Change added and Speech Rate method updated in UAP_AudioQueue

Adds  SetVoice(string newVoice) method to UAP_AudioQueue. Will handle call from UAP_Accessibility manager and pass them to WindowsTTS.SetVoice when WindowsTTS is used.
Updates SetSpeechRate method to also call WindowsTTS.SetSpeechRate when WindowsTTS is in use.
WindowsTTS.SetSpeechRate will scale the 1-100 speech rate value from UAP_AudioQueue.SetSpeechRate to the -10-10 value expected by the Windows SAPI API.

Adds Win32 dll to UAP/Plugins/x86
Fixes WindowsTTS Crash
Allows SetVoice and SetSpeechRate to be called from UAP_Accessibility manager, instead of directly through WindowsTTS.cs. This prevents an edge case where Unity would crash if WindowsTTS.SetVoice or WindowsTTS.SetSpeechRate was called without UAP_AccessibilityManager enabled.


Removed Equatable constraint from Storable

It's aa huge gain for usability and the loss is not that big I think
To be discussed

[Current coverage][cc-pull] is 97.95%

Merging [#77][cc-pull] into [master][cc-base-branch] will decrease coverage by 0.43%

@@             master        #77   diff @@
==========================================
  Files             9          9
  Lines           436        441     +5
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            429        432     +3
- Misses            7          9     +2
  Partials          0          0

[][cc-pull]

Powered by Codecov. Last updated by [90724a4...aef0554][cc-compare]
[cc-base-branch]: https://codecov.io/gh/devlucky/Kakapo/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/devlucky/Kakapo/compare/90724a4b845520e601cfb2d440b1b625aaafaebe...aef0554d6653934de897e0f382ff66e203a90670
[cc-pull]: https://codecov.io/gh/devlucky/Kakapo/pull/77?src=pr

I think this might be a good idea but kind of a compromise for the future. Probably we should properly document what to expect/not to expect from deletion in db before merging this.

@joanromano I added it to the deletedocumentation, is it fine?

Btw there are only two way to delete the wrong thing:

Creating an entity with same type and id: then you are supposed to understand what you are doing
Use another entity created by another DB (hard to happen)

So I wouldn't be too concerned about it, if you are we might:

create another method for Equatable so can be used by equatable
refactor if to use the id directly instead of passing the entity itself.

👍


My code is not running in output on the bottom.

Type: Bug
Whenever I am working through tutorials off Mosh, and try to mimic what the tutorials says to do, It is NOT RUNNING CODE in OUTPUT. Not sure how else to word it, or report the issue.
VS Code version: Code 1.75.1 (441438abd1ac652551dbe4d408dfcec8a499b8bf, 2023-02-08T21:32:34.589Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz (8 x 2803)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
15.70GB (8.11GB free)

Process Argv
--crash-reporter-id ec244f47-70c5-4325-b8ad-f66d2f2330c3

Screen Reader
no

VM
0%

Extensions (16)

Extension
Author (truncated)
Version

code-runner
for
0.12.0

copilot
Git
1.74.8955

vscode-docker
ms-
1.24.0

csharp
ms-
1.25.4

isort
ms-
2022.8.0

python
ms-
2023.2.0

vscode-pylance
ms-
2023.2.40

jupyter
ms-
2023.1.2010391206

jupyter-keymap
ms-
1.0.0

jupyter-renderers
ms-
1.0.14

vscode-jupyter-cell-tags
ms-
0.1.6

vscode-jupyter-slideshow
ms-
0.1.5

remote-containers
ms-
0.275.1

cpptools
ms-
1.14.3

vscode-java-debug
vsc
0.48.0

json
Zai
2.0.2

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdc:30486549
c4g48928:30535728
dsvsc012cf:30540253
azure-dev_surveyone:30548225
pyindex848:30662994
nodejswelcome1cf:30587006
282f8724:30602487
pyind779:30671433
89544117:30613380
pythonsymbol12:30671437
pythonb192cf:30669361

Please provide screenshots and the behavior you expect to see instead.

When you run files with the Python extension, it displays the results in the terminal. However, when you're using the Code Runner extension, the results are displayed in the output. Maybe that's the extension that they're using in the tutorial you're following?

Hi, yes, I do have Code runner extension. I have provided the following screenshot of the results from the tutorial (on the right) and my proggram, Visual Code on the left.  Sent from Mail for Windows From: Luciana AbudSent: Friday, February 24, 2023 7:18 PMTo: microsoft/vscode-pythonCc: brittanypup; AuthorSubject: Re: [microsoft/vscode-python] My code is not running in output on the bottom. (Issue #20753) When you run files with the Python extension, it displays the results in the terminal. However, when you're using the Code Runner extension, the results are displayed in the output. Maybe that's the extension that they're using in the tutorial you're following?—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>
@brittanypup Please file this on Code runner extension as that handles the output scenario: https://github.com/formulahendry/vscode-code-runner
Also the screenshot you sent did not render as you used github email directly to post it.


Map minor changes

[ ] Default map to US
[ ] Display lat/lng on one line in data hover --> "Latitude / Longitude:     32.0000, 134.0739"

We likely need to use a bounding box. Fixed zoom on start creates a weird behavior.


Use ConstraintLayout in fragment_explore_course_list.xml #142

Change the fragment_explore_course_list layout to Constraint layout  issue #142

@ujjwalagrawal17  could you check changes in  the fragment_explore_course_list layout to Constraint layout in my commit " changed fragment_explore_course_list from linerlayout to ConstraintLayout"  issue #142

@MarinaTaran thanks for the PR !

@ujjwalagrawal17 thank you!


connection error: connection refused to port 30000

I have completely installed the FarmVibes.AI on Azure server It was working correctly. I also Run 5 to 7 workflows. but now it gives the connection error. The error is " HTTPConnectionPool(host='<IP_ADDRESS>', port=30000): Max retries exceeded with url: /v0/workflows (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f81f585fb20>: Failed to establish a new connection: [Errno 111] Connection refused')) "
I also attached the details of the Error.
Error_details.txt

I got the same error and fixed it by running:
bash farmvibes-ai.sh restart
Which gave the output:

deployment.apps/terravibes-rest-api scaled
pod "terravibes-rest-api-57db88b46c-q7vwc" deleted
deployment.apps/terravibes-rest-api scaled
Waiting for deployment "terravibes-rest-api" rollout to finish: 0 of 1 updated replicas are available...
deployment "terravibes-rest-api" successfully rolled out
deployment.apps/terravibes-orchestrator scaled
pod "terravibes-orchestrator-656cbf6fff-nsq82" deleted
deployment.apps/terravibes-orchestrator scaled
Waiting for deployment "terravibes-orchestrator" rollout to finish: 0 of 1 updated replicas are available...
deployment "terravibes-orchestrator" successfully rolled out
deployment.apps/terravibes-cache scaled
pod "terravibes-cache-54c779c59-j9cst" deleted
deployment.apps/terravibes-cache scaled
Waiting for deployment "terravibes-cache" rollout to finish: 0 of 1 updated replicas are available...
deployment "terravibes-cache" successfully rolled out
deployment.apps/terravibes-worker scaled
pod "terravibes-worker-6d8b649b5b-8d5mv" deleted
pod "terravibes-worker-6d8b649b5b-k7djf" deleted
pod "terravibes-worker-6d8b649b5b-nv6m2" deleted
deployment.apps/terravibes-worker scaled
Waiting for deployment "terravibes-worker" rollout to finish: 2 out of 3 new replicas have been updated...
Waiting for deployment "terravibes-worker" rollout to finish: 0 of 3 updated replicas are available...
Waiting for deployment "terravibes-worker" rollout to finish: 1 of 3 updated replicas are available...
Waiting for deployment "terravibes-worker" rollout to finish: 2 of 3 updated replicas are available...
deployment "terravibes-worker" successfully rolled out
FarmVibes.AI REST API is running at http://<IP_ADDRESS>:30000

@mursaleen-bkk, may I ask for the output of the df -h command?
Also, can you please share the output of running docker logs k3d-farmvibes-ai-server-0?
Thanks!

Closing this issue for now. From the other issues opened by @mursaleen-bkk, it seems they were able to setup FarmVibes.AI.
@mursaleen-bkk, feel free to reopen the issue if that is not the case.


dont track .vscode anymore

as a matter of fact this file has been tracked on purpose. The vs configuration versioned in the workspace one to ensure

tab size to 2 spaces
no trailing spaces
no more than one blank line in html files

The only one which could be worth changing is the format on type which indeed depends on the user rather than on the project.
What do you think?

Makes sense.
But as soon as this project will gain hype (and it will!), you'll probably want to ensure these rules outside of vscode.
I'd suggest to use EditorConfig.

bad news, I'm afraid that there's no way to ensure "no more than one blank line in html files" in editorconfig...

closed in favor of #14 do you agree @antoine-richard ?

yep


make static websites fully static

Currently static website fetchs local json file, and thus require CORS to be enabled.
Instead, the html template could import them as JS files.

fixed in 842dcab


Allow OpenShift dev preview shiftstack clusters

Can one of the admins verify this patch?

FYI it looks like some of the vars have changed in the install-config, working this out now - https://github.com/openshift/installer/blob/master/docs/user/openstack/customization.md#minimal

Do you folks mind maybe checking this tomorrow so we can see if there are any changes needed?  Thanks!


Updates mocha.js to address #1700

Fixes #1700

Hi @eddies! Could you provide tests that pass thanks to this change? Cheers!

@dasilvacontin Honestly, I'm not sure how to provide a unit-like test for this. I was only triggering this issue as part of running a test w/ PhantomJS and Grunt and and various other dependencies. I did create https://github.com/eddies/mocha-test-case as a minimal example, which I believe definitively isolates the error to the specific one-line commit to mocha I highlighted.
If someone could take a look at the mocha-test-case repo and provide some suggestions as to how that might be translated into a test for the mochajs repo, I could try running with it from there.

@eddies Please make the change against runnable.js, rather than the compiled/disted mocha.js. https://github.com/mochajs/mocha/blob/49d81aa17751e47cec26a22f0607076c98c4a1fc/lib/runnable.js#L215
Beyond that, how does this impact https://github.com/mochajs/mocha/pull/1578 and https://github.com/mochajs/mocha/pull/1540 ? After updating runnable.js, I wonder if the build fails.

Picked up @danielstjules's comment and merged in a separate branch.


Does not compile

Mirror internal pbbam and pbcopper develop branches to GitHub master.

Fixed https://github.com/PacificBiosciences/minorseq/commit/34fba6bfe0459cc4605aa898f4b5e523425e2a60


Add inputs for audio and text.

Hello, thank you for taking the time to make this repo.
I think that adding regular comfyui inputs to the node would streamline generating voices.
For instance we could use a load audio node, a whisper transcribe node (already available custom node) and and have outputs fed to the F5-TTS node.
This approach would help with batch generation and will even be superior to the gradio app because in comfyui it is trivial to unload whisper model before loading F5 to further lower vram requirements.

Thanks for telling about this.  Very useful.  I have added a new node to accept an audio + text input.
Example workflow...
https://github.com/niknah/ComfyUI-F5-TTS/blob/main/examples/F5TTS_whisper_workflow.json

Thank you very much! Its great!


uuid: Move the uuid package into its own top level directory

There was no real reason to have this package embedded inside the ssntp
package and having it in there confuses dep prune making the package
harder to vendor.
Signed-off-by: Mark Ryan<EMAIL_ADDRESS>

Coverage decreased (-0.005%) to 65.869% when pulling 0cdb1541f51925cb9a1f2cc7c9dd3a007bd21987 on markdryan:move-uuid-package into 66772b769dd8916327ac5d89a3cb5ad24c585bc7 on ciao-project:master.

Coverage increased (+0.009%) to 65.883% when pulling 0cdb1541f51925cb9a1f2cc7c9dd3a007bd21987 on markdryan:move-uuid-package into 66772b769dd8916327ac5d89a3cb5ad24c585bc7 on ciao-project:master.

Coverage remained the same at 65.874% when pulling 768d90e1783900eb33319103a21b0e70f8b0017f on markdryan:move-uuid-package into 66772b769dd8916327ac5d89a3cb5ad24c585bc7 on ciao-project:master.


Mistake in code snippet on the riverpod docs website

In this section of the riverpod.dev website, there is a mistake in the code snippet.
// Current :
addTearOff(container.dispose);

// Should be :
addTearDown(container.dispose);

https://riverpod.dev/docs/concepts/combining_providers#how-to-test-an-object-that-receives-read-as-a-parameter-of-its-constructor

Thanks for the report!


ARROW-1891: [Python] Always use NumPy NaT sentinels to mark nulls when converting to array

This code path could benefit from some refactoring, but this is enough to get things working properly, and we can refactor later.

+1, appveyor build: https://ci.appveyor.com/project/wesm/arrow/build/1.0.1561


💬 RFC: Standardization on entity provider clientside throttling

🔖 Need
Ensuring that backstage doesn't become a problem for external systems when fetching data requires careful consideration on concurrency control / maximum throughput. Without clientside throttling support, backstage could hit an external system fast enough that it could cause degradation of services or temporary outages.
Take the Bitbucket server discovery provider for example. The current crawler implementation right now will fetch from every single repository in an organization using a simple for await (const repo of repositories) {} loop. Without throttle control, this could send a massive amount of requests against bitbucket in large organizations.
🎉 Proposal
Entity providers should begin to standardize on strategies for adding configurable support for throttling requests against external systems. One possibility would be to add functionality from either the bottleneck or limiter projects and add standard properties to the task scheduler configurations that can be used by entity provider implementations.
〽 Alternatives
No response
❌ Risks
It is unlikely to be able to update all entity providers to have uniform throttling features at once, so the standardization won't be there initially. We would also need to be extra vigilant that contributors adhere to the throttling standard.
👀 Have you spent some time to check if this RFC has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

@bforbis another option worth looking into is to refactor Bitbucket Entity Provider to an Incremental Entity Provider. Then the provider will automatically backoff when it hits rate limit. We could even extend Incremental Ingestion backend to support proactively backing-off before hitting the rate limit. You can read more about it here https://backstage.io/blog/2023/01/31/incremental-entity-provider

Interesting idea @taras, that certainly does look useful. My organization does not have rate limiting turned on for bitbucket right now, so that is why I was thinking client-side throttle control would be useful here.
I suppose the nature of how the incremental entity provider approach works would naturally add a little bit of throttling between bursts, but the peak requests during a burst is still unlimited if the target server does not have rate limiting enabled on the API.

You can use it for throttling too because you can control burstLength and restLength for each entity provider. bustLength controls how long the entity provider will attempt to paginate before resting. For example, you could say 1 second burst length, which means that it'll attempt to process as many pages as it can in 1 second. restLength is how long it rests between bursts. It gives the processing loop time to process the entities. The result is effectively a throttle but we could also add the ability to control burst length based on number of requests.

@Rugvip, after reading up on how BitbucketServerEntityProvider is implemented along with BitbucketServerClient, I think actually the right configuration would look more like:
integrations:
  bitbucketServer:
    - host: bitbucket.mycompany.com
       apiBaseUrl: https://bitbucket.mycompany.com/rest/api/latest
       token: ${BITBUCKET_TOKEN}
       bottleneck:
         maxConcurrent: 5
         minTime: 200

Doing it this way means the rate limiter applies to all bitbucket operations on the server side that utilizes this integration configuration, not just this individual entity provider.


module 'flutter_barcode_scanner' not found     @import flutter_barcode_scanner;

Same here, there's any solution?

Same problem, has anyone found a solution?

I managed to solve it by opening the Runner.xcodeproj file in Xcode. I navigated to Pods/Development Pods/flutter_barcode_scanner/Pod/flutter_barcode_scanner.podspec. So Xcode recognized the module and built the application without any problems. Hope this helps you too!

Same problem running on MBP M1 Pro laptop. I'm wondering if this is related to the hoops I had to go through to install the pods on the M1. Anyone else having this problem on an M1?

I fixed doing a flutter clean and then pod install

@pdivita, unfortunately, that didn't solve my problem. I'm still getting Module 'flutter_barcode_scanner' not found.

I managed to solve it by opening the Runner.xcodeproj file in Xcode. I navigated to Pods/Development Pods/flutter_barcode_scanner/Pod/flutter_barcode_scanner.podspec. So Xcode recognized the module and built the application without any problems. Hope this helps you too!

It solved for me. I used MAC OS Monterey e XCode 14.2, guys. It should be one of the problems of yours.


What is the scope of this project and how can I extend it?

Hi,
I'm currently building Axon Framework byte buddy integration. Of course it can be released as an individual library - or as a submodule here... So back to my question in the title. What is the scope of this integrations project? Do you aim to collect all integrations to all frameworks in a mono-repo library?
Cheers,
Simon

Done and the PR is waiting. Will close this for now..


Allow users to receive sign in emails out of production env

We're usually not sending emails while in staging environment. We're creating an exception for signin/createUser emails through the sendEvenIfNotProduction parameter. Also, we make websiteUrl configurable in generateLoginLink, but this will be skipped in production to avoid fishing issues.
Fix: https://github.com/opencollective/opencollective/issues/1695

Coverage decreased (-0.005%) to 67.652% when pulling 4a109bf3f14edfb99809423b51b6445e42ef735b on feat/allow-non-production-signin-emails into 7bce0f8d7ef7de4af552ba4c367f69633f4b50ef on master.


cf output

Version: 6.11.0-bba7fcf-2015-04-13T17:49:06+00:00
I am using the cli in a cygwin terming on Windows 7.  Whenever I issue any cf command in the cygwin terminal the output from CLI is formatted in an unreadable state... Looks like it's adding a bunch of spaces after each line in place of a return.  A picture is worth a 1000 words so see my attached screen capture.  Not sure if this info would be useful but my TERM variable is set to 'xterm' in the cygwin terminal.

CLI team to try to repro.

found out what is going on... if I cf login through a windows command prompt and then go to use the cf commands in a cygwin terminal is when I'm getting the bad formatting... if I do the cf login from the cygwin terminal then formatting is good.

@ncsucharlie Definitely good to know.  Thanks!

@goehmen This is due to the config file (that controls how the translation files are formatted for the system you're on) only gets written when you run certain commands - things like target, login, api, etc.

Going to close this, please feel free to reopen if you need any additional help.


MRG, FIX: Fix read_epochs w/complex data, preload=False

Fixes a bug pointed out on the mailing list.

Did indeed fix the bug on my end, thank you!


Support for message persistence

I have noticed that other MQTT client libraries support message persistence e.g. paho mqtt client libraries. Are there any plans for such a feature?
I would really like to switch to mqtt_cpp library which is a pure C++ header only library but message persistence is a feature I currently would like to have so this is the reason I am asking

What do you mean by message persistence?

See https://github.com/redboltz/mqtt_cpp/wiki/Persistence
mqtt_cpp support persistence.
But the approach is different from paho and MQTT.js.
mqtt_cpp doesn't have store parameter on constructor or setter.
Instead of that, mqtt_cpp provides some functions.
updating
Call set_serialized_handlers() after construct the client and before calling connect().

h_publish is called just before the publish packet sending. You can store the message in your way.
h_pubrel is called just before the pubrel packet sending. You can store the message in your way. Normally, overwrite stored publish message that has the same packet id.
h_remove is called puback or pubcomp is received. You can remove the stored message that has the matched packekt id.

In my example, I use level-db to store.
restoring
Call restore_serialized_message(). You call it after the client created and before connect() is calling.
This function restore one message. So you need to call it for all stored message. The store (insertion) order is the same as sending order after connection. So you need to call it old to new.
My example do that. level-db doesn't have order, so I added count in the payload and sort it before restoring. It is just PoC example, count is usually not a good choice. Timestamp is better. Because, persistence need to keep the order during reboot. (I will update the example in the future.)
MQTT v5
The functions are for MQTT v3.1.1.
For v5, set_v5_serialize_handlers() and restore_v5_message()
Design decision
I intentionally avoid introducing a store class. The store class usually contains storing way. e.g. level-db.
But user want to other way. The store class could have customization point. But it is complected for me.
So I choose callback functions and restore function.
Other resources
Test codes might be helpful to implement your own storing mechanism.
https://github.com/redboltz/mqtt_cpp/blob/master/test/resend_serialize.cpp
https://github.com/redboltz/mqtt_cpp/blob/master/test/resend_serialize_ptr_size.cpp

I really appreciate your attention; your response is much clearer and concise than I could have ever expected. Thank you so much!


resullt.getBitmap() is null

Hello
resullt.getBitmap() returns null in onActivityResult. why ?
there is a difference between returned uri and bitmap QUALITY ???
tnx

Did you ever find a way to use the result? I can't even use the uri returned because it is prefixed with content://// or file:/// can anyone help?

I face same problems, my test phone is samsung edge 8


Improve check_tool to show error when tool is not found by which

Thanks @pdcastro for this repo, I find it very useful!
This is a small fix to report missing tools instead of ending with an error and empty message.

FYI, I'm planning to merge a few additional housekeeping changes later today, at which point I will also push a new repo tag for versioning purposes. Thanks again for this contribution! 🙏


Standardize Commit Message Formatting with Template Support

Is your feature request related to a problem? Please describe.
In my current workflow, the inconsistency in commit message formats leads to confusion and inefficiencies. Many team members often skip providing detailed context, making it challenging to trace the evolution of our codebase. This has resulted in frustrations during code reviews and when attempting to understand the history of changes.
Describe the solution you'd like
I propose implementing a commit message template to enforce a clear and structured format. This template should guide developers in writing informative messages that capture the essence of each change. Here’s a suggested format:
Commit Message Template
<type>(<scope>): <subject>

<body>

<footer>

Breakdown:

<type>: Indicates the nature of the change (e.g., feat for features, fix for bug fixes).
<scope>: Optional. Describes the affected module or feature.
<subject>: A brief, imperative description (max 72 characters).
<body>: Detailed explanation (optional), wrapping at 72 characters.
<footer>: References issues (e.g., Closes: #123) or breaking changes.

Example Usage:
feat(auth): add user login functionality

This commit introduces user login via email and password.

Closes: #42

Additional context
I'm talking about this git config --global commit.template ~/.gitmessage.txt.
either we setup this automatically for user or the user can do this manually through daytona while adding git providers (advanced settings) or we can setup elsewhere

I'm talking about this git config --global commit.template ~/.gitmessage.txt.
either we setup this automatically for user or the user can do this manually through daytona while adding git providers (advanced settings) or we can setup elsewhere

Ah, I see what you're getting at.
Automatically setting this up would be too intrusive but it's something that user can set up for themselves using dotfiles which we plan to support with https://github.com/daytonaio/daytona/issues/963.
I'll close this as not planned since the functionality is covered by another issue.


How to disable specific dates

Is there any way to disable a list of dates without using minDate and maxDate?
My use case is that I have some dates that are no longer available and don't want any other users to choose these dates.

I found the mapDays prop which according to the docs accepts a disabled field. I can confirm this works and disables the day.
However, it seems like the libraries types do not accept these additional fields. The defined return type is HTMLAttributes<HTMLSpanElement> | void.
I created #76 to fix this.

Thank you, I will publish new version tomorrow.

Thanks!


Deprecated: Implicit conversion from float 4995090.007781982 to int loses precision in vendor\react\event-loop\React\EventLoop\StreamSelectLoop.php on line 137

Reason: https://php.watch/versions/8.1/deprecate-implicit-conversion-incompatible-float-string
I am using PHP 8.1.2 (cli) (built: Jan 19 2022 10:18:23) (ZTS Visual C++ 2019 x64)
PS: Thank you for reactphp ;-)

@RobertEcker Thank you for reporting. Can you provide more context and/or a gist to reproduce this? You're the first to report this and I currently fail to see how this line would raise a notice:
https://github.com/reactphp/event-loop/blob/1fd1d01c45fcf8764b00a58cc2e35283c5fd5978/src/StreamSelectLoop.php#L137

@clue Sure:

Download https://github.com/reactphp-legacy/whois
composer install --ignore-platform-reqs
start whois-master\examples\query.php
error is shown

Hope you can reproduce it, too

@RobertEcker Looks like the problem comes from using an outdated package, as that package is deprecated more than 4 years ago as per https://github.com/reactphp-legacy/whois/issues/15. Accordingly, this will try to install a somewhat dated version of this EventLoop. Using a current version, I can not reproduce this problem you're seeing (see also the test suite that comes with this project).
I'm not sure how much interest there is for an up-to-date whois package, but I would usually recommend filing this downstream. If there's enough interest, I'm sure this is something that somebody will pick up again.
I hope this helps! I believe this has been answered, so I'm closing this for now. Please come back with more details if this problem persists and we can always reopen this :+1:


Any chance to get a non deb linux build ?

Let's be honest if you care about bleeding edge compilation optimizations your probably running arch and not debian.

I use archlabs, a bunsenlabs inspired distro built on arch, and also crunchbangplusplus.
(crunchbang was a nice minimalistic distro using the openbox WM and debian, discontinued in 2015, it spawned crunchbangplusplus and bunsenlabs,and bunsenlabs birthed archlabs. All are good.
I actually do my thorium builds on crunchbangplusplus.
But yes I absolutely could offer a .zip that could be used portably, like with a script inside called thorium.sh or something that tells it to set the user profile dir to the same folder. This would run on any linux distro. Could also include a .desktop file for integration.
anyway here are the distros im talking about, check em out if you wish.
https://crunchbangplusplus.org/
https://archlabslinux.com/
https://www.bunsenlabs.org/

@Lehner82  @midzer  I will be making portable linux builds today. It will be a .zip with the contents of the thorium .deb, plus the wrapper script thats installed in /usr/bin, but modified to not initiate logging, and set the user profile dir to a subdir of the extracted .zip file. It will also have a .deesktop file that is likewise modified that can be put in ~/.local/share/applications/ or ~/bin/ It should run on any linux distro that has libnss3 and not too ancient core utils and glibc, etc. Tested working on debian 9, 10, 11 and ubuntu 16.04, 18.04, 20.04, 21.10 and arch 2020.05 and 2021.12 and popos 18 and garuda latest.

@Lehner82  @midzer  I will be making portable linux builds today. It will be a .zip with the contents of the thorium .deb, plus the wrapper script thats installed in /usr/bin, but modified to not initiate logging, and set the user profile dir to a subdir of the extracted .zip file. It will also have a .deesktop file that is likewise modified that can be put in ~/.local/share/applications/ or ~/bin/ It should run on any linux distro that has libnss3 and not too ancient core utils and glibc, etc. Tested working on debian 9, 10, 11 and ubuntu 16.04, 18.04, 20.04, 21.10 and arch 2020.05 and 2021.12 and popos 18 and garuda latest.

Cool. Definitely gonna test that.

Cool. Definitely gonna test that.

@Lehner82 @midzer  I've made a build in Thorium Special that has a portable .zip. This build is only for Haswell and higher CPU's though. If you have a CPU older than that or older than AMD Excavator or Ryzen 1, then it's okay because the next Thorium release and from here on out will have the portable zips. I also made a commit with a new folder called portable that has the files used for portable linux releases and portable windows releases which I was already doing.
https://github.com/Alex313031/Thorium-Special/releases/tag/M99.0.4800.0

@Lehner82 Regular Thorium release with a portable .zip is now up. https://github.com/Alex313031/Thorium/releases/tag/M99.0.4803.0

I tried the portable zip on arch and fedora and it worked pretty flawlessly.

@Lehner82 Nice! Thorium-Win also has installers and a portable .zip with a readme inside if your interested. Also, im about to build with some new patches that will fix icons when distilling pages in reader mode, and adds a new UI element - a right click menu on the reload button that has three options: 'normal reload', 'hard reload', and 'clear cache and hard reload'
Also, I've been building for peoples specific architectures like haswell (for me), SSE4 (guy with 1st gen core), and tigerlake (11th gen laptop). If you'll give me your machine model no. or CPU sku number/model number, I would be more than happy to make you a personal release that will take advantage of all your cpus additional instructions

@Alex313031 The portable Thorium-Win seems to work fine too.
I have a i9 9900k skylake and a 5850u AMD Ryzen 7. Would certainly be interesting if there's any difference past avx2.

@Lehner82 Not being a reddit style know it all here, but 9xxx is coffee lake refresh (but 7th through 10th gen are all really just optimizations of skylake). Which one would you like me to make a build for?
The thing is that avx and avx2 only trigger the AVX clock offset, while avx 512 will trigger it if ANY avx 512 is used. So what @midzer  (who makes the tigerlake and macos builds) has been doing, is using a BUILD.gn I made with -march=tigerlake and -mtune=tigerlake but with extra arguments underneath it like -mno-avx-vnni and -mno-avx-512. I could do the same for you, and the result is a build that is optimized to use every instruction your processor is capable of doing, while manually disabling only specific AVX 512 instructions. I would make a BUILD.gn for you and put it in the thorium-special repo, which has build files for macos, android, and raspi, as well as other architectures. Midzer would be the one building it, because I'm on a 4790K. Clang has a weird thing where you can cross compile for anything, but when compiling for the same architecture the host machine is, the host machine has to have at least the instruction features of your target, i.e.  i would need a skylake or 5000 series ryzen. He has a tigerlake (11th gen) machine, and tigerlake has (i think) the same instructions available to it as 5000 ryzen. Just lemme know which. Also would you like a .deb or portable or both?

@Lehner82 Going back through my issues. Would you still like a custom build? If so, for which machine/cpu?

@Neucher How would you like to procede. Going back through my issues again. If this issue doesn't get a reply within a couple of weeks im going to close it due to inactivity.

@Alex313031 Yes I'm closing it right now. The AVX2 build works fine.


setup.cfg: install_requires = setuptools; python_version>=3.12

% python3.12 -m pip install pipx
% pipx install setuptools-py2cfg
% setuptools-py2cfg

Traceback (most recent call last):
File "/Users/cclauss/.local/bin/setuptools-py2cfg", line 5, in
from setuptools_py2cfg import main
File "/Users/cclauss/.local/pipx/venvs/setuptools-py2cfg/lib/python3.12/site-packages/setuptools_py2cfg.py", line 7, in
import setuptools
ModuleNotFoundError: No module named 'setuptools'

Fix: pipx inject setuptools-py2cfg setuptools

I believe keeping these tests will require a solution like https://github.com/pyglet/pyglet/commit/4389bbacb5dda21813caadd189839ebb652551d7

Mock(spec) --> Mock(autospec)
https://github.com/gvalkov/setuptools-py2cfg/blob/7299f1c9f11f0d455c244d5a51ca95c3cc34dbfc/setuptools_py2cfg.py#L44

https://nedbatchelder.com/blog/202202/why_your_mock_still_doesnt_work.html


Fix for the broken @call_rule for nodes that might have a variable number of inputs

This PR fixes #210

Codecov Report

:exclamation: No coverage uploaded for pull request base (develop-delta-fn-eus@2d5aeb9). Click here to learn what that means.
Patch has no changes to coverable lines.

Additional details and impacted files
@@                   Coverage Diff                   @@
##             develop-delta-fn-eus     #211   +/-   ##
=======================================================
  Coverage                        ?   72.90%
=======================================================
  Files                           ?      208
  Lines                           ?     7082
  Branches                        ?        0
=======================================================
  Hits                            ?     5163
  Misses                          ?     1919
  Partials                        ?        0

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

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


Possible to selectively remove 'just now' and show seconds?

Use case is I am automatically updating a portion of my page every 15 seconds.  I am using timeago to display the last time an update occurred.  By default, it shows 'just now' until it reaches '10 seconds ago'.  Is there a way to change this particular usage so it is 'just now', 1 second ago, 2 seconds ago, and so on as normal?  As I am updating this every 15 seconds I would rather show the seconds value from the start rather than 'just now' for those first 9 seconds.
In all other cases I am using it I prefer the 'just now' for those first 9 seconds.

Nevermind... noticed I can create and register a custom locale and use it.  Got it working.


can webstorm debug?

i use webstorm for many years ,so i want debug with webstorm,is that possible?

No there is only a experimental vscode debugger support for now

thanks,i am new to jsbinding,hope i can  help some time, this project is amazing.


yearRange doesn't work

I put in 2004,2008 as yearRange, and it allowed me to select dates both before 2004 and after 2008.
Video here: https://bilesjeffrey.wistia.com/medias/gh5c6s4ujb
I also tried with single-integer ranges, with similar not-working-ness.

Thank you for the report and nice video. I checked with Pikaday what the expected behaviour is and found out following:
The year range is only used for the year select element. If you want to enforce a minimum and maximum date you should use minDate and maxDate in Pikaday. This is currently not yet supported but I would love to see it implemented with tests :)


[BUG] Debug problems with MacOS DIVE Desktop build

The Zip is corrupt, I don't know why.

Let's just retract the Zip and only offer the DMG.

@subdavis what's the status on this?


Enabled inline types

Is your feature request related to a problem? Please describe.
I am trying to parse Markdown but disable the link functionality. A text like "*Hello World* [Foo Bar](https://www.google.com)" should be rendered as "Hello World [Foo Bar](https://www.google.com)". While an easy solution for this problem exists for block level elements (via Parser.builder().enabledBlockTypes()), no solution for inline elements exists.
Describe the solution you'd like
A new option should be added to the parser builder to easily customize the inline feature that are enabled (via Parser.builder().enabledInlineTypes()).
Describe alternatives you've considered
I am currently trying to write a custom parser and am struggling to come up with a solution.

Found it in the docs, sry.

While I found a lot of possible configurations, I did not find any option to disable the processing of links & images. Can someone point me in the right direction?

@fynnfeldpausch, the easiest way I can see of implementing what you want is to create a custom node renderer for Link and Image nodes which would just render the node text instead of link/image HTML.
It is much easier than trying to not parse the links because the logic for these inline elements is intertwined with a lot of other inline elements, including refrence links and images.
You can take a look at custom node renderer samples as a starting point:
NodeRendererSample.java
NodeRendererSample2.java

Works like a charm. Thanks for the hint!


Implement helm charts

This PR actually implements the helm charts.
(Actually, I'm mostly opening the PR for discussion until we get the branch into shape.)

@mook-as on the PODs (except the loggregator-bridge) I see
standard_init_linux.go:211: exec user process caused "no such file or directory"
Not sure, but looks like that some part of the code is requiring files not there, do you mind me to try to add also docker images with opensuse as base? (maybe having them pushed along, just for debugging?)

I've created a simple Dockerfile for eirini-ssh: https://github.com/SUSE/eirini-ssh/pull/17 it can switch the base image, so we can use the same for both scratch, and for opensuse-based ones. Let me know your thoughts!

standard_init_linux.go:211: exec user process caused "no such file or directory"

That sounds like it's because the binaries are not built with CGO_ENABLED=0; as I'm using scratch as a base for the various -setup containers, if they're linked against libc we'll see that error on startup.  Using a base image that isn't quite as minimal would also fix that issue, of course :)

standard_init_linux.go:211: exec user process caused "no such file or directory"

That sounds like it's because the binaries are not built with CGO_ENABLED=0; as I'm using scratch as a base for the various -setup containers, if they're linked against libc we'll see that error on startup. Using a base image that isn't quite as minimal would also fix that issue, of course :)

I've checked that indeed, but the pipeline seems to build with CGO_ENABLED=0, or I'm missing something?

As for debugging, I'm (locally) experiementing with kube 1.16 + ephemeral containers.

Thanks for the tip!

At this point, the webhooks don't break pushing apps anymore (because I screwed up and made the services never find the pods).  Still need to make ssh work (it's failing to reach UAA because, as a non-cf-operator pod, it can't resolve *.cf.internal).

At this point, the webhooks don't break pushing apps anymore (because I screwed up and made the services never find the pods). Still need to make ssh work (it's failing to reach UAA because, as a non-cf-operator pod, it can't resolve *.cf.internal).

Just a heads-up to set your expectations right, it won't work also after that (with KubeCF) because it depends on an Eirinifs which is SLE-based. The ssh extensions expect an sshd daemon running inside the app POD. See also: https://github.com/cloudfoundry-incubator/kubecf/issues/476

For consistency I've created/updated a Dockerfile for each extension, following the same approach so the base can be swapped during build and can be re-used in the EiriniX pipeline instead of building it on the fly there: https://github.com/SUSE/eirini-persi/pull/21 https://github.com/SUSE/eirini-persi-broker/pull/5 https://github.com/SUSE/eirini-ssh/pull/17
So this allows also everyone to build those depending on the need.
Images from scratch can be built with the BASE_IMAGE=scratch build argument, otherwise they default to opensuse/leap

@mudler I think this PR is ready for review (as in, we can reasonably merge this to master) now.  I think we want to squash the whole thing to get rid of the intermediate commits that are (at least the ones I made) low quality, but add a co-authored-by or whatever tag to the commit message.  Please let me know how you want to proceed, thanks!
I've tried this by deploying on my hacked-up kubecf deployment.  I get running logs (cf logs --recent and cf logs, using go-env) correctly; I do not get staging logs, which will need to be dealt with later.  I can also cf ssh to the point where it fails because the pod isn't listening to anything on port 2222 (but can confirm that it does actually attempt to talk to the pod's IP address).  I have not tried persi, other than to see that it does not block cf push.
(I'll go look at the various Dockerfile PRs, plus make a kubecf PR, now.)

With native chart also, there is no anymore the eirini service account, and the one created with the chart has by default insufficient permission to create MutatingWebhook
{"level":"info","ts":1587733690.7644634,"caller":"kubeconfig/checker.go:36","msg":"Checking kube config"}
{"level":"info","ts":1587733690.7886207,"caller":"ctxlog/context.go:51","msg":"Not creating the webhook s
erver certificate because it already exists"}
2020-04-24T13:08:10.791Z    FATAL    internal/start.go:72    generating the webhook server configuration:
 generating the webhook configuration: mutatingwebhookconfigurations.admissionregistration.k8s.io is forb
idden: User "system:serviceaccount:scf:eirinix" cannot create resource "mutatingwebhookconfigurations" in
 API group "admissionregistration.k8s.io" at the cluster scope

@mudler I think this PR is ready for review (as in, we can reasonably merge this to master) now. I think we want to squash the whole thing to get rid of the intermediate commits that are (at least the ones I made) low quality, but add a co-authored-by or whatever tag to the commit message. Please let me know how you want to proceed, thanks!

I have no strong preference, I'm happy with what suits you best!

I've tried this by deploying on my hacked-up kubecf deployment. I get running logs (cf logs --recent and cf logs, using go-env) correctly; I do not get staging logs, which will need to be dealt with later. I can also cf ssh to the point where it fails because the pod isn't listening to anything on port 2222 (but can confirm that it does actually attempt to talk to the pod's IP address). I have not tried persi, other than to see that it does not block cf push.

With the Eirini native charts there are few things still not working quite right :(

@mudler: I've turned on rbac by default to make things work with https://github.com/cloudfoundry-incubator/kubecf/pull/771 — with that, things seem to deploy and at least logs work (ssh looks slightly more broken than before though; might want to do that in a follow-up?)
Also, since the persi auth password secret wasn't being created anywhere anymore, I just made it part of the chart (and the knob now does an override instead of random secret generation).
I put the pre-squash commits in mook-as/eirinix-helm-release#helm-chart-inital as a backup, and squashed everything to cone commit.

@mudler: I've turned on rbac by default to make things work with cloudfoundry-incubator/kubecf#771 — with that, things seem to deploy and at least logs work (ssh looks slightly more broken than before though; might want to do that in a follow-up?)
Also, since the persi auth password secret wasn't being created anywhere anymore, I just made it part of the chart (and the knob now does an override instead of random secret generation).
I put the pre-squash commits in mook-as/eirinix-helm-release#helm-chart-inital as a backup, and squashed everything to cone commit.

Looks good! about the ssh component: yes it's better to track the work needed there in a separate PR indeed

Merging, as what is in this PR is strictly better than master (being, nothing); no doubt we'll have more improvements later, but it's a good checkpoint.


Push metadata to ab_test block

now i can use metadata in views:
/ slim sample:
- ab_test('my_experiment') do |alternative, meta|
  h2
    = alternative
    small = meta['subtitle']

Nice, thanks @ekorneeff!


i had this issue when trying it on my machine. this change fixed it

const Dynamo = require('../node_modules/dynamodb-onetable/Dynamo');

const test = new Dynamo();

the above would give me the following error: TypeError: Dynamo is not a constructor. However, it was resolved with this small change
const {Dynamo} = require('../node_modules/dynamodb-onetable/Dynamo');

const test = new Dynamo();

But Dynamo.js has an export default at the bottom.
You should be able to do:
import Dynamo from 'dynamodb-onetable/Dynamo'
Why were you using ../node_modules.....?

Please let me know your thoughts. I want to make sure this PR is required by other users and won't break things.
The import as was, works fine for us here. So we need to understand why it doesn't work for you.

But Dynamo.js has an export default at the bottom.
You should be able to do:
import Dynamo from 'dynamodb-onetable/Dynamo'
Why were you using ../node_modules.....?

Should be able to, yes. I was scratching my head for about an hour wondering why it wouldnt work even though it was default.
Due to the project structure, packages are stored in a separate folder (so that other functions can all use them, and have a single folder location after deployment). Because of this, we access the node_modules folder directly instead of using package names, ex require('../node_modules/something') vs require('something')
Let me see if i can do a super small example and dig into this more, isolated from my actual project

@mobsense
Figured it out! Using ES6 imports (import Dynamo from 'dynamodb-onetable/Dynamo');) works perfectly fine with type: module in package.json, but my project is using ES5 imports (const Dynamo = require('dynamodb-onetable/Dynamo');) and it does NOT work, it needs to be { Dynamo }
Sample project:
npm i dynamodb-onetable/Dynamo

app.js
const Dynamo = require('dynamodb-onetable/Dynamo');
const client = new Dynamo();

node app.js

it will crash
changing app.js, it will pass
const { Dynamo } = require('dynamodb-onetable/Dynamo');
const client = new Dynamo();

Thank you for this.


Version 2.3 vs 2.5

Hi, many thanks for this node - very helpful.
I'm currently running version 2.3 on Node Red, had some challenges to get it up and running because the initial setup is not very clear and MongoDB imposes restrictions on free tiers like only allowing SCRAM-SHA-1. An example would be very helpful in this regard - showing setup for both Simple and Advanced connections.
My issue today...jsut installed on another instance of Node Red version 2.5 and duplicated the exact same creditials and it is giving an error. The 2.3 instance is still running fine.
Has anything changed in this regard or am I missing something obvious?
Many thanks!

Hi wiehannvanzyl,
thank you for using this node.
From node-red-contrib-mongodb4 v2.3 to v2.5 the mongodb driver was upgrade from v5.6 to v5.9 to support the latest mongodb server v7. Read more about other changes here, but I don't think that these changed breaking your instance.
Here's a configuration example:

Make sure to whitelist your node-red instance ip in Mongodb Atlas Security > Network Access.
Make sure that your node-red instance is running at least on NodeJS v14.20.1.
I hope this helps, otherwise I need more detailed information about the error message.

Much appreciated - let me check and revert.

Simple and Advanced settings should not be interconnected. I have improved the code at this point to make sure that this is actually the case. Please checkout<EMAIL_ADDRESS>


Docker compose error

Describe the bug
When I try to build everything by using the docker compose the following error occures.
To Reproduce
'''docker compose up
[+] Building 31.9s (15/15) FINISHED
=> [compreface-postgres-db internal] load build definition from Dockerfile                                                                                0.4s
=> => transferring dockerfile: 55B                                                                                0.0s
=> [compreface-admin internal] load build definition from Dockerfile                                                                                0.8s
=> => transferring dockerfile: 71B                                                                                0.0s
=> [compreface-fe internal] load build definition from Dockerfile                                                                                1.2s
=> => transferring dockerfile: 68B                                                                                0.0s
=> [compreface-core internal] load build definition from Dockerfile                                                                                2.6s
=> => transferring dockerfile: 70B                                                                                0.0s
=> [compreface-api internal] load build definition from Dockerfile                                                                                3.0s
=> => transferring dockerfile: 69B                                                                                0.0s
=> [compreface-postgres-db internal] load .dockerignore                                                                                1.3s
=> => transferring context: 2B                                                                                0.0s
=> [compreface-admin internal] load .dockerignore                                                                                1.6s
=> => transferring context: 2B                                                                                0.0s
=> [compreface-fe internal] load .dockerignore                                                                                2.2s
=> => transferring context: 2B                                                                                0.0s
=> [compreface-core internal] load .dockerignore                                                                                2.7s
=> => transferring context: 2B                                                                                0.0s
=> [compreface-api internal] load .dockerignore                                                                                3.1s
=> => transferring context: 2B                                                                                0.0s
=> ERROR [compreface-postgres-db internal] load metadata for docker.io/library/postgres:11.5                                                                                30.1s
=> CANCELED [compreface-admin internal] load metadata for docker.io/exadel/compreface-admin:0.5.0                                                                                29.6s
=> CANCELED [compreface-fe internal] load metadata for docker.io/exadel/compreface-fe:0.5.0                                                                                29.0s
=> CANCELED [compreface-core internal] load metadata for docker.io/exadel/compreface-core:0.5.0                                                                                28.6s
=> CANCELED [compreface-api internal] load metadata for docker.io/exadel/compreface-api:0.5.0                                                                                28.1s

[compreface-postgres-db internal] load metadata for docker.io/library/postgres:11.5:

failed to solve: rpc error: code = Unknown desc = failed to solve with frontend dockerfile.v0: failed to create LLB definition: failed to do request: Head https://registry-1.docker.io/v2/library/postgres/manifests/11.5: proxyconnect tcp: dial tcp <IP_ADDRESS>:3128: i/o timeout'''

What operation system do you use?
What are the docker and docker-compose versions?
Have you changed the code or build config before the error?
How you build the code? I assume from /dev folder docker-compose build?

The error is very strange - we use the default Postgresql image, so it shouldn't even try to build it.

What operation system do you use?
Mac OS 11.3.1
What are the docker and docker-compose versions?
Engine: 20.10.6
Compose: 1.29.1
Have you changed the code or build config before the error?
I followed the steps described at "https://github.com/exadel-inc/CompreFace/releases"

How you build the code? I assume from /dev folder docker-compose build?
need to check but normaly I use the default one

The error is very strange - we use the default Postgresql image, so it shouldn't even try to build it.

Maybe I did not get it. I am realtivly new with docker copmpose.

Found the problem it was caused by "experimental feature" enabled in docker. Deactivating fixed the problem.


Fx minor typo in app template (s/USE_PKG/USEPKG/).

This PR fixes a minor typo in application template which silently ignores required packages.
It was faster to directly submit a PR than to open an issue. If this violates your workflow in any way, please feel free to ignore it and apply the changes otherwise in the next version.

@aabadie interestingly enough the failing checks above seem to be independent of my changes :thinking:

interestingly enough the failing CI checks seem to be independent of my changes...

There was an update of black today and now it requires more formatting. I pushed an update in master. Can you rebase your PR on top of latest master ?

Well, nevermind, I'll just merge your PR as-is.
Thanks !

I just published a new tag with your fix (and a few other things), so the package should be available on pypi in a few minutes.


[Improve Existing Best Practice Guide]: Improve README for Continuous Integration to provide documentation guidance

Checked for duplicates
Yes - I've already checked
Best Practice Guide
Continuous Integration
Best Practice Guide Sections
No response
Describe the improvement
The README for Continuous Integration should be a launching point for using the Best practice Guide. In this regard, it should provide explanations of the various sub-sections and what they mean for implementing CI across an application. It should clarify what the sections are used for and what they represent.

Great idea @jpl-jengelke - might be good to see if there's a way, using Docusaurus, to auto-generate a good page for folder sections like the README for CI. Typically, pages like this should just list out the guides available and provide some basic introduction.


Allow to manually change Connection Data

Allow to manually change Connection Data

In case of connecting to a port forwarded node manually changing the Connection Data is needed because the LND Connect generates a QR with original IP address. There is no way to easily change the IP to actual IP of the node.

Thanks for your issue.
Yes that would definetly help in some situations. I'll see what I can do.

This is done now and will ship in the next version!


Merge release-1.0.1 into ballerina-1.0.x

Purpose

Merge release-1.0.1 into ballerina-1.0.x

Codecov Report

Merging #19235 into ballerina-1.0.x will increase coverage by 4.78%.
The diff coverage is n/a.

@@                 Coverage Diff                 @@
##           ballerina-1.0.x   #19235      +/-   ##
===================================================
+ Coverage            15.73%   20.51%   +4.78%
===================================================
  Files                   47       52       +5
  Lines                 1265     1394     +129
  Branches               197      216      +19
===================================================
+ Hits                   199      286      +87
- Misses                1053     1095      +42
  Partials                13       13

Impacted Files
Coverage Δ

composer/packages/tracing/src/ToolBar.tsx
71.05% <0%> (ø)

composer/packages/tracing/src/TraceList.tsx
94.44% <0%> (ø)

composer/packages/tracing/src/DetailView.tsx
72.72% <0%> (ø)

composer/packages/tracing/src/TraceLogs.tsx
70.37% <0%> (ø)

composer/packages/tracing/src/index.ts
0% <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 4482cd3...1219d56. Read the comment docs.


transcription.Properties Exceeds the maximum length for a value of 256 characters.

Previous batch transcription script is not working:
I am using swagger_client from API v2
I use azure blob (service sas key) for the transcription result
properties = {
'AddSentiment': True,
'TranscriptionResultsContainerUrl': RESULT_BLOB_URI
}

I can confirm this is an issue on v2.
We will provide a fix for this in the next deployment to PROD which is expected to be complete within 10 days.

:eyes:

The release will start rolling out beginning of next week. We just started the deployment into pre production systems. Sorry for the slight delay.

Closing this as the fix should be rolled out now. @wistreng please let us know if this is still an issue.


[Doc] update json length and modify import

What type of PR is this:

[ ] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[x] Doc
[ ] Tool

Which issues of this PR fixes:

Fixes #
Problem Summary(Required):

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto backported to target branch

[x] 3.0
[x] 2.5
[x] 2.4
[x] 2.3

@Mergifyio backport branch-3.0

@Mergifyio backport branch-2.5

@Mergifyio backport branch-2.4

@Mergifyio backport branch-2.3


Dfx 0.9.0 gets stuck when trying to deploy canister with wrong identity

Steps to reproduce:

Deploy canister with default identity
Switch to different identity
run dfx deploy --network ic

Outcome:

it gets stuck in step Starting batch. with no errors.

Expected outcome:

It should report an error

reported in https://forum.dfinity.org/t/dfx-0-9-0-gets-stuck-when-trying-to-deploy-canister-with-wrong-identity/10623

Does not happen with dfx 0.10.0 anymore.


Refresh user 2

The Apollo "reactive var" has no sense of when data is being updated, because it's designed to be a sort of unmanaged "store anything here" bucket, and thus wasn't updating with user settings changes.
I attempted to put in a thing that would update the reactive var manually when a user did a mutation on their self, but it just didn't work.
I wound up just ripping out the reactive var and replacing it with a normal Apollo request. I renamed GET_USER and UPDATE_USER with GET_SELF and UPDATE_SELF to distinguish things. (We do still have UDPATE_USERS for the new grant form).
We are doing updates based on Users.publicAddress instead of Users.id as the latter just didn't work for me. If that's a problem, I'll revisit it.
Please review the ApolloCache file because I don't really understand it at all.
(Along the way I also found a bunch of obsolete components and deleted them.)

@EricWVGG I love the idea of using the Apollo cache for the user; way better due to the reactive nature of Apollo anyway. My comments are mainly around all these new GraphQL queries and mutations.
I see how we are creating new GraphQL functions for each use case. This approach breaks the generalist magic of  GraphQL. It scales better if we create generic functions and give the definition in the variables from the consumer, so instead of passing a publicAddress to a Users Query, just pass the whole whereand the conditional in it
useQuery(
    {
       variables: {
             where:  {
                publicAddress:  {
                 _eq: <Public Address >
               }
          }
       }
    }
)

Also, for the sake of simplicity, we can call the GraphQL functions precisely as their Hasura names but written in camel case, so if the Hasura name is insert_Users we can call it: ìnsertUser
etc...
Also using array mutations and queries, makes the functions even more useful so insert_Users instead of insert_User_one or Query Users instead of Query Users_by_pk etc...
Finally, I suggested wrapping into a hook the hooks needed to grab the current user into one single hook so we do not need to load all those files every time we will check for the loggedUser..