dehydrated issues certificate chains leading to expired root

Letsencrypt's root expired on 21 September:
https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/
I have discovered a machine that is having letsencrypt certs be renewed, but the chain provided by dehydrated is providing the old cert chain that points at the expired cert.
Systems using old openssl (CentOS7 and below) then break in all sorts of ways.
To fix this, make sure the chain doesn't lead to an expired cert.

The chain is supplied by Let's Encrypt not dehydrated. dehydrated simply downloads the default chain Let's Encrypt supplies.
You can select the alternative (short) chain using PREFERRED_CHAIN="ISRG Root X1" in your config file

This is the expected behavior as per Lets Encrypt's own documentation, and the very article you linked explains why.

The chain is supplied by Let's Encrypt not dehydrated. dehydrated simply downloads the default chain Let's Encrypt supplies.
You can select the alternative (short) chain using PREFERRED_CHAIN="ISRG Root X1" in your config file

Alas, no luck.
[root@chestnut ~]# dehydrated -x -c
# INFO: Using main config file /etc/dehydrated/config
# INFO: Using additional config file /etc/dehydrated/conf.d/local.sh
Processing redwax.eu
 + Checking domain name(s) of existing cert... unchanged.
 + Checking expire date of existing cert...
 + Valid till Feb  5 07:35:21 2022 GMT (Longer than 30 days). Ignoring because renew was forced!
 + Signing domains...
 + Generating signing request...
 + Requesting new certificate order from CA...
 + Received 1 authorizations URLs from the CA
 + Handling authorization for redwax.eu
 + 1 pending challenge(s)
 + Deploying challenge tokens...
 + Responding to challenge for redwax.eu authorization...
 + Challenge is valid!
 + Cleaning challenge tokens...
 + Requesting certificate...
ERROR: Alternative chain with CN = ISRG Root X1 not found, available options: issuer= /O=Digital Signature Trust Co./CN=DST Root CA X3, issuer= /C=US/O=Internet Security Research Group/CN=ISRG Root X1

Unfortunately the error message doesn't contain quotes around the values, so it's not clear where the values start and end, or whether they include the "issuer=".

I'm guessing you are on the latest release-version of dehydrated? Can you please check if the latest version from master branch works for you? There already should be a fix for the CN extraction (29b67962ac07d5d2b24f69c863a9ef31e8ac53ee).
Other than that what others already reported is correct, dehydrated doesn't generate or actively selects the chain. It uses the default chain pushed by the CA unless given instructions to use a different one.

The chain is supplied by Let's Encrypt not dehydrated. dehydrated simply downloads the default chain Let's Encrypt supplies.
You can select the alternative (short) chain using PREFERRED_CHAIN="ISRG Root X1" in your config file

Alas, no luck.
[root@chestnut ~]# dehydrated -x -c
# INFO: Using main config file /etc/dehydrated/config
# INFO: Using additional config file /etc/dehydrated/conf.d/local.sh
Processing redwax.eu
 + Checking domain name(s) of existing cert... unchanged.
 + Checking expire date of existing cert...
 + Valid till Feb  5 07:35:21 2022 GMT (Longer than 30 days). Ignoring because renew was forced!
 + Signing domains...
 + Generating signing request...
 + Requesting new certificate order from CA...
 + Received 1 authorizations URLs from the CA
 + Handling authorization for redwax.eu
 + 1 pending challenge(s)
 + Deploying challenge tokens...
 + Responding to challenge for redwax.eu authorization...
 + Challenge is valid!
 + Cleaning challenge tokens...
 + Requesting certificate...
ERROR: Alternative chain with CN = ISRG Root X1 not found, available options: issuer= /O=Digital Signature Trust Co./CN=DST Root CA X3, issuer= /C=US/O=Internet Security Research Group/CN=ISRG Root X1

Unfortunately the error message doesn't contain quotes around the values, so it's not clear where the values start and end, or whether they include the "issuer=".

or try
PREFERRED_CHAIN="issuer= /C=US/O=Internet Security Research Group/CN=ISRG Root X1"

Just wanted to add another data point.  On CentOS 7 (EL7) systems with dehydrated version 0.7.0 (release-version), I need to use the long version of the chain.  On Oracle Linux 8 (EL8) with same dehydrated version, I need to use the short preferred chain string.
Kind of related - any chance of a new release version soon(ish)?  In our environment, we usually need to use released versions.  That may help with the above for consistency.

Apparently dehydrated version 0.7.1 had been released, and it fixes this problem on CentOS 7 (PREFERRED_CHAIN="ISRG Root X1" works, while it did not with dehydrated 0.7.0); there is even a new enough dehydrated-0.7.1-1.el7 package in EPEL.  So I suppose that this issue can be closed as fixed.


Content excpetion handling in GenerateXmlElements function

Handling of failed generating XML sitemap
"Geta.SEO.Sitemaps.XML.SitemapXmlGenerator : Error on generating xml sitemap
EPiServer.Core.PageNotFoundException: Content with id XXXXX was not found"
As IContentRepository TryGet actually throws an exception when there is something wrong.  GenerateXmlElements function's for-each loop breaks and failed the sitemap generation job

Thank you for the contribution, added a comment in your PR.
Also could you change the target branch to develop? So we test out the change before we merge it to master.

@patkleef all done btw


remove original http extension and replace it with jsonrpc

The original http extension is based on spring's http invoker.  Since we now have json-rpc which serves the same purpose, I propose to remove the original http extension and make json-rpc extension as the default http provider.

The idea of this PR is somewhat similar #4781


[BUG] - Unknown element <[object Object]> in collection  in Components/Dropdown

Describe the bug
When I'm using the Dropdown component with dynamically import multiple named exports from a module in next.js 13.0.0, I'm getting this error Unknown element <[object Object]> in collection .
Your Example Website or App
https://github.com/vercel/next.js/discussions/13139
Steps to Reproduce the Bug or Issue
1 :  import dynamic from "next/dynamic";

2 :  const { name }  = { name: dynamic(() => import("@nextui-org/react").then(module => module.name))};

3 : <Dropdown> { code } </Dropdown>

4 : Click on trigger button

Expected behavior
reference to Describe the bug section
Screenshots or Videos
reference to Steps to Reproduce the Bug or Issue section
Operating System Version
Linux
Browser
Firefox

Hey please update to v2.0 https://nextui.org/blog/nextui-v2 due to v1 will not receive more updates.

Hey please update to v2.0 https://nextui.org/blog/nextui-v2 due to v1 will not receive more updates.

I got same error with next-app-template. Should I use use client for the dropdown component?

Hey @nurullah we're checking this with react-aria team, please use use client on top of the file in the meantime


Static method added to retrieve tools onboarded in config file

This PR exposes a static method on the Analytics class that will allow the tool using this package to retrieve a list of DashTool enums for each tool that has been onboarded into the config file. If there has been no tool added, or the file does not exist, it will return an empty list
This will help other tools that are not able to show a message to the developer get approval to send telemetry simultaneously with other tools. For example, if a user is using the analyzer inside vim, it won't be possible to prompt the user with a message informing them about analytics collection. However, in the case with the analyzer, it is part of the same codebase as the dart-tool and when the dart-tool displays it messages, it can also approve the analyzer to send messages since they are within the same logical grouping of dart tools.
Usage within production code:
final List<DashTool> onboardedTools = Analytics.onboardedTools();

// Returns a list of DashTool enums
// ie. --> [DashTool.flutterTools, DashTool.languageServer]

Usage within test code where we need to provide a filesystem and point to a different home directory:
// Setup the filesystem with the home directory
final FileSystemStyle fsStyle =
    io.Platform.isWindows ? FileSystemStyle.windows : FileSystemStyle.posix;
fs = MemoryFileSystem.test(style: fsStyle);

// Setup the home directory since `MemoryFileSystem.test()` is empty
const String homeDirName = 'home';
final Directory home = fs.directory(homeDirName);
home.createSync();

final List<DashTool> onboardedTools = Analytics.onboardedTools(fs: fs, homeDirectoryOverride: home);

fyi @bwilkerson @jcollins-g – pending our conversation tomorrow with Michael, I have drafted up this PR that will allow us to expose which tools have already been onboarded.
Even if we decide that we can't lump dart-tool with language-server, i think this method can still be useful to have included

Closing as this isn't necessary anymore


feature: add caps to m from terminal

Is your feature request related to a problem? Please describe.
Can't use m to make requests that require an attached capability.
Describe the solution you'd like
We should allow the user to specify the capability to attach to the request.
Perhaps automagically attach all caps that were issued by foo:bar:baz.os when sending a request to foo:bar:baz.os. I don't think we currently expose this information to processes, however.

I mean, this is a necessary restriction of the security model. The terminal can only attach capabilities to m that the terminal itself has. If a process doesn't want to give the terminal messaging capabilities, m cannot be used. If a process does want to make sure m can be used, it can just grant necessary capabilities to the terminal, which (I think) will pass them all on to m.
If a process wants to be usable as a CLI without giving capabilities to the terminal, it should include in its package 1 or more scripts that can be used with it. Those scripts can be granted various capabilities in scripts.json.

Hmm, yeah, good point. In #596 I modified m to attach all caps terminal has for the target process.
However, as noted there, there's still an issue. Userspace caps can't be granted to terminal, and hence m cannot inherit them. Two proposed ways to get around this are:

Change manifest field grant_capabilities to allow non-messaging caps to be granted,
Add a terminal:terminal:sys api that allows processes to give it capabilities.

done; see #581 for relevant PRs


fix(vite): can not resolve node_module package which has a query surfix

Description
When I import a node_module package with query surfix, vite can't resolve it and give me a error:
const Vue3Lottie = async () => (await import( "vue3-lottie?chunkName=vue-lottie")).Vue3Lottie;

error logs:
[vite]: Rollup failed to resolve import "vue3-lottie?chunkName=vue-lottie" from "src/pages/demo/demo.vue".
This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
`build.rollupOptions.external`
error during build:
Error: [vite]: Rollup failed to resolve import "vue3-lottie?chunkName=vue-lottie" from "src/pages/demo/demo.vue".
This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
`build.rollupOptions.external`
    at onRollupWarning (D:\work\ytt-pc-1\node_modules\vite\dist\node\chunks\dep-8f5c9290.js:41772:19)
    at onwarn (D:\work\ytt-pc-1\node_modules\vite\dist\node\chunks\dep-8f5c9290.js:41588:13)
    at Object.onwarn (D:\work\ytt-pc-1\node_modules\rollup\dist\shared\rollup.js:23224:13)
    at ModuleLoader.handleResolveId (D:\work\ytt-pc-1\node_modules\rollup\dist\shared\rollup.js:22508:26)
    at ModuleLoader.resolveDynamicImport (D:\work\ytt-pc-1\node_modules\rollup\dist\shared\rollup.js:22560:120)
    at D:\work\ytt-pc-1\node_modules\rollup\dist\shared\rollup.js:22455:32

What is the purpose of this pull request?

[X] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[X] Read the Contributing Guidelines.
[X] Read the Pull Request Guidelines and follow the Commit Convention.
[X] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[X] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[X] Ideally, include relevant tests that fail without this PR but pass with it.

packagefoo/bar?baz.js might mean bar?bar.js inside packagefoo. (though it is not recommended to do that)
So we could not use id.split('?') there.


Update specs2-core, specs2-scalacheck to 4.12.0

Updates

org.specs2:specs2-core
org.specs2:specs2-scalacheck

from 3.+ to 4.12.0.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.specs2" } ]

labels: test-library-update

Superseded by #30.


newUuid server response not working (chunking upload)

Type of issue [REQUIRED]
bug?
Uploader type [REQUIRED]
traditional
Fine Uploader version [REQUIRED]
5.13.0
Browsers where the bug is reproducible [REQUIRED]
Firefox 51.0
Operating systems where the bug is reproducible [REQUIRED]
Linux
Hello my server send newUuid, but in chunking upload not working. Fineupload don't respect new uuid.
When i upload non chunging, fineuploader new uui respected.
Here is my log from broswer...
Chunking upload - not working:
[Fine Uploader 5.13.0] Sending chunked upload request for item 2.0, bytes 1-2000000 of 5917584.  fine-uploader.js:162:21
[Fine Uploader 5.13.0] xhr - server response received for 2  fine-uploader.js:162:21
[Fine Uploader 5.13.0] responseText = {"newUuid":"23cf9b49-ff28-44ed-af80-df23cffcf36d","success":true,"preventRetry":false}
  fine-uploader.js:162:21
[Fine Uploader 5.13.0] Received response status 200 with body: {"newUuid":"23cf9b49-ff28-44ed-af80-df23cffcf36d","success":true,"preventRetry":false}
  fine-uploader.js:162:21
[Fine Uploader 5.13.0] Chunked upload request succeeded for 2, chunk 0  fine-uploader.js:162:21
[Fine Uploader 5.13.0] Chunk 0 for file 2 uploaded successfully.  fine-uploader.js:162:21
[Fine Uploader 5.13.0] Sending chunked upload request for item 2.1, bytes 2000001-4000000 of 5917584.  fine-uploader.js:162:21
[Fine Uploader 5.13.0] xhr - server response received for 2  fine-uploader.js:162:21
[Fine Uploader 5.13.0] responseText = {"newUuid":"e04bb3e4-9111-45ee-8efc-abd9768f9bc6","success":true,"preventRetry":false}
  fine-uploader.js:162:21
[Fine Uploader 5.13.0] Received response status 200 with body: {"newUuid":"e04bb3e4-9111-45ee-8efc-abd9768f9bc6","success":true,"preventRetry":false}
  fine-uploader.js:162:21
[Fine Uploader 5.13.0] Chunked upload request succeeded for 2, chunk 1  fine-uploader.js:162:21
[Fine Uploader 5.13.0] Chunk 1 for file 2 uploaded successfully.  fine-uploader.js:162:21
[Fine Uploader 5.13.0] Sending chunked upload request for item 2.2, bytes 4000001-5917584 of 5917584.  fine-uploader.js:162:21
[Fine Uploader 5.13.0] xhr - server response received for 2  fine-uploader.js:162:21
[Fine Uploader 5.13.0] responseText = {"newUuid":"87ab72d9-c744-4689-aa59-770c3a07025b","success":true,"preventRetry":false}
  fine-uploader.js:162:21
[Fine Uploader 5.13.0] Received response status 200 with body: {"newUuid":"87ab72d9-c744-4689-aa59-770c3a07025b","success":true,"preventRetry":false}
  fine-uploader.js:162:21
[Fine Uploader 5.13.0] Chunked upload request succeeded for 2, chunk 2  fine-uploader.js:162:21
[Fine Uploader 5.13.0] Chunk 2 for file 2 uploaded successfully.  fine-uploader.js:162:21
[Fine Uploader 5.13.0] All chunks have been uploaded for 2 - finalizing....  fine-uploader.js:162:21
[Fine Uploader 5.13.0] Submitting All Chunks Done request for 2  fine-uploader.js:162:21
[Fine Uploader 5.13.0] Sending POST request for 2  fine-uploader.js:162:21
[Fine Uploader 5.13.0] Received response status 200 with body:   fine-uploader.js:162:21
[Fine Uploader 5.13.0] Finalize successful for 2

Normal upload - working:
[Fine Uploader 5.13.0] Sending simple upload request for 1  fine-uploader.js:162:21
[Fine Uploader 5.13.0] xhr - server response received for 1  fine-uploader.js:162:21
[Fine Uploader 5.13.0] responseText = {"newUuid":"2784dbb2-b711-4921-b703-854c817f26e0","success":true,"preventRetry":false}
  fine-uploader.js:162:21
[Fine Uploader 5.13.0] Received response status 200 with body: {"newUuid":"2784dbb2-b711-4921-b703-854c817f26e0","success":true,"preventRetry":false}
  fine-uploader.js:162:21
[Fine Uploader 5.13.0] Simple upload request succeeded for 1  fine-uploader.js:162:21
[Fine Uploader 5.13.0] Server requested UUID change from '77d58f5c-72e7-423e-808e-2763e428892d' to '2784dbb2-b711-4921-b703-854c817f26e0'  fine-uploader.js:162:21

As the issue template asked, please show your code

And also let me know when this last worked (version)

@rnicholus
<!-- Fine Uploader JS file     ====================================================================== -->     <script src="/static/fine-uploader/fine-uploader.js"></script>     <script src="https://cdnjs.cloudflare.com/ajax/libs/jquery/3.1.1/jquery.min.js"></script>
...

<!-- Your code to create an instance of Fine Uploader and bind to the DOM/template
====================================================================== -->
<script>
    var manualUploader = new qq.FineUploader({
        element: document.getElementById('fine-uploader-manual-trigger'),
        template: 'qq-template-manual-trigger',
        request: {
            endpoint: "/upload-server/upload"
        },
        chunking: {
            enabled: true,
            success: {
                endpoint: "/upload-server/chunksdone"
            }
        },
        thumbnails: {
            placeholders: {
                waitingPath: '/static/fine-uploader/placeholders/waiting-generic.png',
                notAvailablePath: '/static/fine-uploader/placeholders/not_available-generic.png'
            }
        },
        maxConnections: 3,
        autoUpload: false,
        debug: true
    })

    qq(document.getElementById("trigger-upload")).attach("click", function() {
        manualUploader.uploadStoredFiles();
    });
</script>

`

And also let me know when this last worked (version)

I don't know, I tested 5.13.0, 5.10.0 - Not working...

Looks like this may have never been implemented for chunked uploads. The safest option may be to check for newUuid on the response to the request made to the chunking.success.endpoint.

In docs:
Providing your own UUID for files

If you would like to track files with your own generated UUID, you can return the new UUID for the file at any time in your server's response. If chunking is enabled, it generally would be most prudent to return this new UUID in the response to the first or last chunk. Once you return the new UUID in your response, Fine Uploader will update its client-side records and begin to use that UUID from that point forward. New UUIDs must be returned as the value of a newUuid property. See the values section above for an example.
http://docs.fineuploader.com/endpoint_handlers/traditional.html

That may have made sense a while back, but the concurrent chunking feature changes that a bit. Since it was never implemented, or at least it hasn't been possible for quite a long time, it's not clear to me now if that was ever a reasonable assumption. Again, the safest approach is the mandate the newUuid be returned in response to the success endpoint

ok thx.

I'll leave this open as it must be addressed. It is indeed a bug.

Since I believe implementing this will be non-trivial, I plan to wait until I hear from other users who depend on or expect the ability to change the UUID of a file via an upload request response.

@rnicholus I too would like the behaviour that is documented. Is there a workaround to change the UUID based on a response callback?

Depending on your needs, this may help https://docs.fineuploader.com/branch/master/api/methods.html#setUuid

Thanks for the quick response, that's just what I was after. Here's what I'm doing for other peoples reference:
onUploadChunkSuccess: (id, chunkData, response) => { uploader.methods.setUuid(id, response.uuid) }

I experience the same problem with chunked upload.
My need is to free chunks on the server when the upload is canceled. The problem is that when we submit the file through addFile, we don't get an id or uuid in return to trace the upload.
When we add our own id through params to addFile, we don't get it back when we call getUploads.
This leaves us with no means to trace uploads when canceled. We tried to use newUuid but it is not working. Do you have any suggestion ?
Thanks.

I have the same problem as @sellou. Would be highly useful if addFile will return id/UUID or both. I use S3 and can't use the newUUID because even if I set the param object I am not able to get these params within FineUploader.getUploads(id) method. After uploading the file I use the returned URL to submit this URL to my backend and register the file to be used(play video) by the logged USER on my Web APP. So if addFile will return the ID or UUID everything will be much easier.
Note: just add that I noted the UUID can change in case we already uploaded some % of a file and the resume feature is used. In that case inside onSubmit callback we have one UUID and inside onUpload callback we have another UUID, So will be nice if addFile will return consistent UUID.


Attempt user cohort filter fix (closer to frontend)

Modelled off the Frontend behaviour found here:
https://github.com/guardian/frontend/blob/master/static/src/javascripts/projects/common/modules/commercial/contributions-utilities.js#L160
From what I can tell, the Frontend logic doesn't attempt to assign a single user cohort to a user, but rather applies certain boolean checks against the user for the given cohort of the test to see if there is a match.

Going to close this in favour of https://github.com/guardian/contributions-service/pull/97 unless people really prefer this approach.


[Bug] Cookie name and subtext are not clickable

🐞 Bug Report
Describe the bug

When you hover the text after the chackbox, the mouse switch to pointer, but there is nothing clickable.

Is this a regression?

To Reproduce

open options
mouseover text
the mousecursor change to pointer

Expected behaviour

Make the text clickable to check the box false and true OR disable the mouseover

Media prove

Your environment

OS:
Node version:
Npm version:
Browser name and version:

Additional context

Hey @Gismo1337 !!
Could I work on this?

assigned @Aspireve

could i work on this?

If Aspireve surrender =) I ping you here @mahamat-abdelkerim-abakar

Hi @Gismo1337 , So I have to remove the mouse pointer right?

please read the ticket :-)

looks good for me @Aspireve

Yoo Thanks!! I'll make my PR then (my first one for the HacktoberFest 🥳🥳!!)


gcc version 8.3.0 (Debian 8.3.0-6)

error: unknown option after '#pragma GCC diagnostic' kind [-Werror=pragmas]
#pragma GCC diagnostic ignored "-Wfloat-conversion"

@AiPacino If you are using older versions of GCC, you may need to modify/remove the errors supported by your version in usqlite.c https://github.com/spatialdude/usqlite/blob/2c91f8fdf2c1eba681029214196ab56beb6babba/usqlite.c#L38


Devils game today not appearing

The game appears if I log into the MSG+ site as starting with pregame at 12:30pm Eastern, but doesn't show up in the M3U generated by EPlus. I don't know if this is because the feed is being shared with NHL Network and I'm also not sure which one is getting the direct feed vs which one is simulcasting, but I would think it being available on the MSG+ website and app would be enough.

Can you email your MSG credentials so I can look at it real quick? It's been a minute since I've done anything with that service

Sent. You're the man.

Okay, new version is going out now

You absolute angel. Thank you so much!


Fix redirecting

It will fix #22.
That issue was caused by the busy flag in observable. I've added the stack to avoid this issue.

it lools good @cognitom thank you

@GianlucaGuarini Thanks!

I've published v2.3.1-beta to npm.
https://www.npmjs.com/package/riot-route


Show Google Map within Flutter Widget

Not able to achieve like Google Map within Flutter Widgets like Ola uber android app UI. check screen shot for reference.

Closing as dup of #21101


[Packaging] Add Ubuntu 22.04 Jammy Jellyfish support

Description
Close https://github.com/Azure/azure-cli/issues/21857
As the next LTS (Long-Term Support) version of Ubuntu - 22.04 Jammy Jellyfish will be released on April 21, 2022, we use the devel docker image to build the preview package.

Packaging


Get the release id not the application id

Change-type: patch
Signed-off-by: Theodor Gherzan<EMAIL_ADDRESS>

retest this please


Techdocs: use lighter color for block quotes and horizontal rulers

Signed-off-by: Erik Larsson<EMAIL_ADDRESS>Hey, I just made a Pull Request!

Both blockquotes and horizontal rulers (see examples below) are currently missing expected colors in Techdocs, making them not distinguishable (the css variables are not set). The default from mkdocs material theme is a "lighter" left border and "light" text color on blockquotes and a "lighter" border on hrs. I found textSubtle and textVerySubtle colors in the palette that seemed to fit the bill and work in both light and dark themes.

Blockquotes

:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

This looks like it addresses https://github.com/backstage/backstage/issues/6987


Migrate to Vite

Some useful links:

vitesse
Svelte + TS
vite-boilerplate

Migration completed in commit b481490 :tada:.


[UXE-4364] feat: default theme supporting dark/light mode

:tada: This issue has been resolved in version 1.5.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


mqtt failed, rc=-2 on MKR1010

Hi thanks for the amazing guideline
I've read #2 and #3 but still facing rc=-2 problem as below
16:48:04.885 -> Getting the time from time service:
16:48:04.920 -> Current time: 29. August 2020 - Saturday 07:48:05
16:48:04.955 -> Getting IoT Hub host from Azure IoT DPS
16:48:15.020 -> Starting IoT Hub connection
16:48:25.205 -> ---> mqtt failed, rc=-2
16:48:37.233 -> ---> mqtt failed, rc=-2
16:48:49.262 -> ---> mqtt failed, rc=-2
16:49:01.284 -> ---> mqtt failed, rc=-2
.
.
.
And I did not get couldn't connect to DPS error message like this post ,  anyone know how should I fix this problem ?

Hi , thanks for the suggestions in #2 and #3 , they worked for except iotc_scopeId is name for oithubHost in configure.h .
So I commented out these 3 lines in mkr10x0iotc.ino and added  iothubHost = iotc_scopeId;
// char hostName[64] = {0};
// getHubHostName((char*)iotc_scopeId, (char*)iotc_deviceId, (char*)iotc_deviceKey, hostName);
// iothubHost = hostName;
iothubHost = iotc_scopeId;


Suggest property query includes a type when none is selected

When reconciling a column, using a service that supports a /suggest/property endpoint, if I select Reconcile against no particular type, OpenRefine includes the most recently selected type in the query.
For example, in this screenshot, I selected Reconcile against no particular type and then started typing test in the As property box.

Current Behavior
In that example, OpenRefine sent the following request to the reconciliation service:
https://wikidata.reconci.link/en/suggest/property?prefix=test&spell=always&exact=false&scoring=schema&prefixed=true&type=Q223393
Expected Behavior
I would expect the type to be sent in the suggest/property query if one is selected so that a reconciliation service has the option to filter the suggested properties by the included type.
If Reconcile against no particular type is selected, then I expect no type to be included in the query so that the reconciliation service does no filtering on the suggested properties.
Versions

Operating System: MacOS Monterey
Browser Version: Chrome
JRE or JDK Version: JDK 13.0.2
OpenRefine: Version 3.6.2

Additional context
I'm creating a reconciliation service and this affects how we need to implement the internal logic of the suggest property endpoint.

Adding the "reconciliation API design" tag because this parameter isn't mentioned by the specs yet. It would be good to align the theory and practice here. I would recommend adding the type parameter to the specs and removing the unspecified parameters from the calls OpenRefine is making.

@wetneb I don't understand the link to the reconciliation API design - isn't this just a bug that the type is included here when it shouldn't be?

Well it looks like @nhervieu is trying to use this information in her service, so instead of removing it, I am proposing (in https://github.com/reconciliation-api/specs/issues/104) to include it in the specs.
Given that the specs were originally written to match OpenRefine's behaviour, and this has been around for years, the fact that this parameter is not in the specs is actually an oversight on my part.

Well it looks like @nhervieu is trying to use this information in her service, so instead of removing it, I am proposing (in https://github.com/reconciliation-api/specs/issues/104) to include it in the specs.
I'd understood the issue being reported here to be that it's being included even when Reconcile against no particular type has been selected, and that limits the response to the type that was previously selected - which is not desired.

Yes absolutely, but according to the current specs, this type parameter just does not exist - it should never be passed at all.
So either we decide to indeed drop it from OpenRefine entirely, or we update the specs to allow it. Or we decide to diverge from those specs, I guess?

So either we decide to indeed drop it from OpenRefine entirely, or we update the specs to allow it. Or we decide to diverge from those specs, I guess?

OK - just want to keep this issue focussed on fixing the current bug - which doesn't seem to be either of the options you mention

We need to keep the discussion of OpenRefine bugs and spec bugs separate.

I'd understood the issue being reported here to be that it's being included even when Reconcile against no particular type has been selected, and that limits the response to the type that was previously selected - which is not desired.

I agree with this interpretation.

Perhaps it's nitpicking but the current bug is not a bug if this parameter does not mean anything according to the specs - as services are not supposed to rely on it.

If you're talking about the draft W3C spec, I don't think it's relevant. What's relevant is that OpenRefine is sending a parameter value which doesn't represent what the user selected in the UI. That seems like a clear bug to me. I don't think fixing it would have a negative affect on compatibility with existing services.

So either we decide to indeed drop it from OpenRefine entirely, or we update the specs to allow it. Or we decide to diverge from those specs, I guess?

It's strongly desirable that the W3C spec preserve backward compatibility with OpenRefine, but it's a separate issue from whether or not OpenRefine breaks compatibility with existing reconciliation services. I don't see why we'd remove functionality in a backward-incompatible fashion without very strong motivation and lots of advance notice to the reconciliation service developers.

As a reminder in another place where OpenRefine departs from the Reconciliation API spec, or at least does something unanticipated by the recon API spec - in #4224 it looks like OpenRefine "preflights" a couple of rows to a recon API server when the user is getting set up with the service - so before the user has pressed 'Start Reconciling...'  OR has sent a couple of rows over to the service to see what the responses look like (and in particular, it uses the types on candidate matches that come back from that "preflight query" as the possible types it presents to the user, rather than looking at the manifest of the recon service)
It might not be a terrible idea for OpenRefine to be able to say "use old OR behavior against this recon API server" to preserve backwards compatibility if the recon API server isn't advertising the right things the service's manifest.

From my perspective this "preflight" query has not got the same sort of status in terms of specs compliance: this conforms to the specs because those preflight requests are valid reconciliation requests on their own. Clients are free to make successive recon requests with slightly varying data. As an end user I often find myself reconciling some rows multiple times anyway (by faceting and using different settings). But that's probably a discussion for another issue.

The preflight is something the spec should consider - maybe there's a better way to support what the OR preflight is doing - but that can be a discussion on the other repo.
I don't think the preflight from OR is documented anywhere right now and it was a heck of a surprise when implementing a service, especially since OR makes decisions about what types to use before the user in theory has any opportunity to steer it in the right direction.

It's a garden variety bug with a simple fix that I've put up for review in #5543.

@epaulson I'm pretty sure this isn't true

[OpenRefine] makes decisions about what types to use before the user in theory has any opportunity to steer it in the right direction.

but if you have evidence to support it, please create a separate bug report for it.

@tfmorris well this will be true later, sorta.  It will depend on the reconciliation service manifest.  And relatedly https://github.com/reconciliation-api/specs/issues/104


debian packging warns source-contains-unsafe-symlink

A run of
lintian -I --pedantic
across the package reveals
E: juju-core source: source-contains-unsafe-symlink src/github.com/prometheus/procfs/fixtures/26231/exe
Anyone packaging this project needs to delete the fixtures directory, but then the tests cannot be run.

We could create the file on-the-fly, maybe during make test. I guess it'd make more sense to remove the test data from debian packages though.

We did remove the fixtures directory from the source to make the package acceptable for Ubuntu. Now it isn't possible to run the tests. the ideal solution is for the test suite to create the symlink as needed.

@sinzui, actually, that file is correct there, and you need to add a lintian override.
having said that, there is no need to package this for ubuntu, it is been in debian for quite some time: https://packages.qa.debian.org/g/golang-procfs.html

Thanks @TheTincho. Closing this as I trust you in all questions around Debian packages.


Add support for Jinja 3.1.x

Jinja 3.1.0 removes jinja2.Markup, which has been deprecated since version 2.5.1 (https://jinja.palletsprojects.com/en/3.1.x/changes/#version-2-5-1).
The suggested replacement is markupsafe.Markup (https://jinja.palletsprojects.com/en/3.1.x/changes/#version-3-1-0)
This PR patches this by first attempting to import jinja2.Markup, and then falling back to markupsafe.Markup.

Thanks for your PR!

Thanks for your PR!


script to run tests under dcos-docker

:ship:

This dirties up the current directory and doesn't add things to gitignore and the like. Also, if we ran it in CI would make the hosts very dirty / usable only for one build then have to be wiped.


New Wallet Setup - Create Password error message

Issue description
When creating a new wallet, I am receiving an error code 'error.password.undefined' instead of an error message when setting the password.  This occurs when I use 'test' as the password.
Also, a small variation of the above issue.  When creating a new wallet, I am receiving an error code 'error.password.word' instead of an error message when setting the password.  This occurs when I use 'tes' as the password.
Wallet version
0.3.1
System specification
What is your operating system?
Windows 10
Is it a repeatable issue?
Y
Steps To reproduce the issue
Explain how the maintainer can reproduce the issue.

Create a new wallet.
Set password to 'test' or 'tes'.
Select Continue.

Expected behaviour
I expect a descriptive error message is displayed.
Actual behaviour
An error code is displayed.

This will be fixed in the next version. Please reopen if you see it again.


Adding environment variables to Jenkinsfile

[x] This contribution adheres to CONTRIBUTING.md.
[ ] New tests have been created for any new features or regression tests for bugfixes.
[x] tox successfully runs, including unit tests and style checks (see CONTRIBUTING.md).

What does this Pull Request accomplish?
Established environment variables in the Jenkinsfile to specify hardware for CI testing.
Why should this Pull Request be merged?
To enable CI testing with hardware.
What testing has been done?
Verified Jenkins executes test script on my dev fork.

py2-test failed because of #116.  I'm working on a fix for that but it does raise the question, why are we running the tests on Python 2.7.0 instead of the latest Python 2.7 release?
Granted, the latest python release is also broken, see #127.  My fix will hopefully fix both.

I installed 2.7.0 because it is the earliest version that we claimed to support at the time of setup. It looks like we have since modified our claimed support to 2.7.7 so I can update the test machine accordingly.

Previously, I was only aware of us claiming 2.7.  I guess the question is does that presume the latest or earliest 2.7.

I'm confirming with our other python projects for consistency purposes.
When we decided on Python 2.7 support, I presume Python 2.7. because those dot-releases are bug fixes and we should only guarantee support with all the latest bug fixes, similar to when an SP1 of LabVIEW comes out, we stop supporting the non-SP1 (I think).


[Everyone]

No new issues for now, I am working on a new mockup that I should have ready by tonight. Please work on any issues assigned to you and make sure your pr is linked to the issue so that we can check them. I have went through and merged or commented on all linked issues to pr's. Any others not finished will be closed tomorrow. Any new issues created after this will be closed until old issues are cleaned up.

Hi! Can I align the text of features, testimonials and never miss any updates? It looks unordered!


Character display issue

VSCode Version: 1.42
OS Version: Windows_NT x64 10.0.15063

Does this issue occur when all extensions are disabled?: Yes

Some Turkish characters do not display properly when I open some 'example.log' file, however when I type in the same characters they display as normal. I wonder if anyone can help me with this problem ?
[DEBUG] [19228] 2020-02-07 20:52:14,234 Manager HandleDynamicFunctions
Fonksiyon �al���r�lacak:'QueryHost'
burası gayet düzgün çalışıyor

VS Code supports a wide range of file encodings. You can see the full list when you click on the lower right status bar where the encoding is shown and then choose to either reopen the file with a specific encoding or save the file with a specific encoding:

There are two options how to configure the encoding for files
Configure the encoding as a setting for all files or files of specific type
We provide a files.encoding setting that you can use to set an encoding for all files. You can also configure this encoding for specific file types, e.g. like this:
"[markdown]": {
    "files.encoding": "utf8"
}

Configure VS Code to automatically detect the encoding when opening files
We provide a files.autoGuessEncoding setting that you can enable to let VS Code detect the encoding of every file automatically. Note that this approach is known to not be accurate in all cases. This guessing of encoding is rather a heuristic that can produce wrong results (that is also why this setting is not enabled by default).
Please also check out issues that are already reported with the files-encoding label: https://github.com/Microsoft/vscode/issues?q=is%3Aopen+is%3Aissue+label%3Afile-encoding


tool: FK not shown as disabled

Reproduce: Select schema and then right click and select "Disable All Tables". Expand a disabled table and the fk are not shown as disabled.

Won't fix.


Misleading description of Managing Endpoint Certificates

Description:
Misleading description of "Managing Endpoint Certificates¶"
"If your API backend is secured with a self-signed certificate (or a certificate which is not signed by a CA) you need to import the backend certificate to the API manager (Gateway) client-truststore and restart the server. This feature enables you to upload the backend certificate through API Publisher while creating or editing your API without restarting the server. "
In fact if API is signed you need to have complete certificate chain in client-truststore.jks.
If new CA or intermediate certificates are added server need to be restarted after that.
If you are adding connetction to self signed API you also need to add its certificate to client-trustsrore.jks and restart server
So there is only one possibility when restart is not needed - if chain of certificates or self-signed certificate to API is already in client-truststore.jks and server restart was done before.

Hi @lacrimal,
From the issue description, it seems that adding certificates through the Publisher portal didn’t work as expected for you. Please let me know if I’ve misunderstood. To analyze the issue further, could you share the steps you followed to reproduce the issue?

Gave you precise information about acapite that need to be updated:
You need restart API manager if you want to use freshly imported client-truststore certificate. You can import new certificate to client-truststore but without restart API manager you can't use this certificate
That should be clearly pointed out.

Hi @lacrimal.
If you need to restart APIM server, this indicates a potential bug rather than a documentation issue. Therefore, I'll transfer the issue to the api-manager repository, where we handle product-related issues.


Question

Hi, bro, I have one question if it is possible to help me, please how I can run WebSocket in your project I configured webpack for development mode and the project is working correctly but, I can't run WebSocket in the project
this is my code below
localhost:3300 is webpack port
var options = {
wsURL: "ws://localhost:3300/rtspoverwebsocket",
rtspURL: "rtsp://<IP_ADDRESS>:554/cam/realmonitor?channel=1&subtype=0",
username: "admin",
password: "admin123"
}

@Doniyor4120 WebSocket should be available in latest Dahua cameras and you should give that in the configuration. It is websocket from Dahua IP camera, we wont create any in the project.

any luck with this @Doniyor4120

@Nidheeshv0312. There is no WebSocket server in the project. Dahua camera provides WebSocket and this code will connect to it.

Thank you guys

i can't run webpack server can you fix it?

Webpack dev server is not added in config. Please use 'npm run build' command and host the output of the build.

Hi, bro, I have one question if it is possible to help me, please how I can run WebSocket in your project I configured webpack for development mode and the project is working correctly but, I can't run WebSocket in the project this is my code below localhost:3300 is webpack port
var options = { wsURL: "ws://localhost:3300/rtspoverwebsocket", rtspURL: "rtsp://<IP_ADDRESS>:554/cam/realmonitor?channel=1&subtype=0", username: "admin", password: "admin123" }

do you have run success? i have meet the same problem

i do not know how wsURL works

@deng0515001. This project uses the websocket provided by Dahua in their cameras. New Dahua cameras support rtsp over websocket and we are using that.

@deng0515001 can you open your network inspector in the browser and check for URL ending with /rtspoverwebsocket. if it is present then this project should work without any issue since we are using it regularly.

no, it does not work, and i do not know how this works.
do you use any web plugins? like dahua`s webplugin.exe or WebActiveX?

@deng0515001 no. it doesn't need any plugins. please check in your browser network tab if it has a URL ending with /rtspoverwebsocket.

i want to use this source in my react project how can i implement it in react project?


Expose the internal validate function.

This permits users to pass in an interface, so that json decoding doesn't happen twice in case it has been decoded already.

Codecov Report

Merging #4 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master       #4   +/-   ##
=======================================
  Coverage   92.32%   92.32%
=======================================
  Files           7        7
  Lines        1120     1120
=======================================
  Hits         1034     1034
  Misses         59       59
  Partials       27       27

Impacted Files
Coverage Δ

compiler.go
95.25% <100%> (ø)
:arrow_up:

schema.go
99.62% <100%> (ø)
:arrow_up:

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 1d461e6...b9ab347. Read the comment docs.

there are some concerns in exposing internal validate function:

validate function does not work for any go value. it works only for map[string]interface{}, []interface{}, string, json.Number, bool, nil
we expect that json is decoded with json.useNumber() see resource.go:26

first concern can be documented.
regarding second concern, we should relax implementation to accept either json.Number or float64
BTW, we can't expose internal validate function directly, since we have to add some error context in case of error.
I will work on this...

resolved. see b7a5b2f2d7c3acfbee30bd8c3779f4f163832b21

Awesome! Thanks very much.


Adds a DockerCluster.Status.Ready field

Signed-off-by: Chuck Ha<EMAIL_ADDRESS>What this PR does / why we need it:
Cluster API checks for the cluster object's infrastructure ref to be ready. This PR adds a field so this provider can set the ready field to true when it's ready. This will tie in with the work @ashish-amarnath is doing to create the LB as part of the cluster-ready.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #163
Adds a ready field on the DockerCluster status

/cc @amy @ericzhang08 @ashish-amarnath
/assign @ncdc

/lgtm


Not supported A4000

ERROR: paperspce-a4000-xformers-0.0.14.dev0-cp39-cp39-linux_x86_64.whl is not a supported wheel on this platform.
Paperspace - python 3.9

Upgrading pip to 22.3
root@ngtfky91c0:/notebooks# pip install paperspce-a4000-xformers-0.0.14.dev0-cp39-cp39-linux_x86_64.whl
ERROR: paperspce-a4000-xformers-0.0.14.dev0-cp39-cp39-linux_x86_64.whl is not a valid wheel filename.

Fixed. Update your notebook please.


feat: add govukHeader() component

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

119 of 119 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 98.844%

Totals

Change from base Build<PHONE_NUMBER>:
0.1%

Covered Lines:
1186

Relevant Lines:
1194

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

119 of 119 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 98.76%

Totals

Change from base Build<PHONE_NUMBER>:
0.1%

Covered Lines:
1355

Relevant Lines:
1363

💛  - Coveralls


LeakCanary  【 SingleViewPresentation$PresentationContext 】

My app is a mixed project of kotlin and flutter.
When I open a  platformview  flutterActivity  and then close this activity ,
but something leakCanary  .
flutter docror :
Flutter assets will be downloaded from https://storage.flutter-io.cn. Make sure you trust this source!
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 3.3.0, on Microsoft Windows [版本 10.0.18363.836], locale zh-CN)
Checking Android licenses is taking an unexpectedly long time...[√] Android toolchain - develop for Android devices (Android SDK version 32.1.0-rc1)
[√] Chrome - develop for the web
[√] Visual Studio - develop for Windows (Visual Studio Community 2019 16.4.2)
[√] Android Studio (version 2020.3)
[√] Connected device (3 available)
[√] HTTP Host Availability

• No issues found!

log below :
LeakCanary: ├─ io.flutter.plugin.common.MethodChannel instance
LeakCanary: │    Leaking: UNKNOWN
LeakCanary: │    Retaining 24 B in 1 objects
LeakCanary: │    ↓ MethodChannel.messenger
LeakCanary: │                    ~~~~~~~~~
LeakCanary: ├─ io.flutter.embedding.engine.dart.DartExecutor instance
LeakCanary: │    Leaking: UNKNOWN
LeakCanary: │    Retaining 37 B in 1 objects
LeakCanary: │    ↓ DartExecutor.flutterJNI
LeakCanary: │                   ~~~~~~~~~~
LeakCanary: ├─ io.flutter.embedding.engine.FlutterJNI instance
LeakCanary: │    Leaking: UNKNOWN
LeakCanary: │    Retaining 240 B in 15 objects
LeakCanary: │    ↓ FlutterJNI.platformViewsController
LeakCanary: │                 ~~~~~~~~~~~~~~~~~~~~~~~
LeakCanary: ├─ io.flutter.plugin.platform.PlatformViewsController instance
LeakCanary: │    Leaking: UNKNOWN
LeakCanary: │    Retaining 1.9 MB in 3853 objects
LeakCanary: │    context instance of com.tome.ropse.MyApplication
LeakCanary: │    ↓ PlatformViewsController.contextToEmbeddedView
LeakCanary: │                              ~~~~~~~~~~~~~~~~~~~~~
LeakCanary: ├─ java.util.HashMap instance
LeakCanary: │    Leaking: UNKNOWN
LeakCanary: │    Retaining 1.9 MB in 3829 objects
LeakCanary: │    ↓ HashMap[key()]
LeakCanary: │             ~~~~~~~
LeakCanary: ├─ android.content.MutableContextWrapper instance
LeakCanary: │    Leaking: UNKNOWN
LeakCanary: │    Retaining 57.6 kB in 874 objects
LeakCanary: │    mBase instance of io.flutter.plugin.platform.SingleViewPresentation$PresentationContext
LeakCanary: │    MutableContextWrapper does not wrap a known Android context
LeakCanary: │    ↓ ContextWrapper.mBase
LeakCanary: │                     ~~~~~
LeakCanary: ├─ io.flutter.plugin.platform.SingleViewPresentation$PresentationContext instance
LeakCanary: │    Leaking: UNKNOWN
LeakCanary: │    Retaining 57.6 kB in 873 objects
LeakCanary: │    flutterAppWindowContext instance of com.tome.flutter.page.FlutterPageActivity with mDestroyed = tru
LeakCanary: │    mBase instance of android.app.Presentation$1
LeakCanary: │    SingleViewPresentation$PresentationContext does not wrap a known Android context
LeakCanary: │    ↓ SingleViewPresentation$PresentationContext.flutterAppWindowContext
LeakCanary: │                                                 ~~~~~~~~~~~~~~~~~~~~~~~
LeakCanary: ╰→ com.tome.flutter.page.FlutterPageActivity instance
LeakCanary:      Leaking: YES (ObjectWatcher was watching this because com.tome.flutter.page.FlutterPageActivity re
LeakCanary:      Activity#onDestroy() callback and Activity#mDestroyed is true)
LeakCanary:      Retaining 10.1 kB in 187 objects
LeakCanary:      key = ab4bdb00-298c-457d-a56e-d9a05984b6dc
LeakCanary:      watchDurationMillis = 71742
LeakCanary:      retainedDurationMillis = 66742
LeakCanary:      mApplication instance of com.tome.ropse.MyApplication
LeakCanary:      mBase instance of android.app.ContextImpl
LeakCanary: ====================================

Hi @JsonYuu, please provide a completed and minimal reproducible code sample so that we may verify this. In this case, it's add-to-app app, so please push the sample code to a GitHub repository and make it public so that we may verify it.
Thank you!


I intend to help out with this feature request, I'm recording the motivation and problem statement here for feedback before I fork and start a PR. You may not see this as something that should be part of the Ronin framework so its best to get your feedback first and not waste any time.
First some PROs:
I often use Ronin when I don't want to build a website for solving problems when a cmd line tool will suffice.

I imagine that most folks would want to avoid bearing the cost of hosting a public site for tooling they built.
Asking consumers of your toolset to host their own website is a high-friction point and will probably cause a lot less folks to use it in the end.

Now some CONs:
When the same CLI tool (developed with Ronin) is useful enough to be installed by users on multiple machines, some unique feedback crops up:

Depending on the developer (me), the commands can get kind of long~ish and the only thing that autocompletes is the program name and not the commands. So I hear feedback about how that's a pain. So a shared history across machines (out-of-the-box for any Ronin-built program) would be quite a sweet feature. It would let any developer's audience leverage copy/paste from within the terminal like:

$ my-ronin-program history
1. my-ronin-program my-custome-command-name --myOptionA value --myOptionB value
2. my-ronin-program my-custome-command-name --myOptionA value --myOptionB value
...
9. my-ronin-program my-custome-command-name --myOptionA value --myOptionB value

There may be scenarios where files (or some other artifacts) are spit out after crunching a task. Some of my users have compared this to a website and said: "Well with a CLI, I can't see my data across machines." Again there is a novel solution whereby linking to one's google drive or dropbox for any program built on top of Ronin could allow artifacts to be persisted and accessed across machines. Actually if the users have the respective google/dropbox agents already installed across their own machines, then all that's required is to point to the shared folder as the directory for reading/writing artifacts: $ my-ronin-program link-shared-folder ... as I finish writing this, I'm not so sure this particular bullet point is something that belongs in Ronin itself ... but I'll leave it here in case it sparks an idea on your side.

So I couldn't figure out how or where the hello.js command is being spit out by code when user runs ronin new hello-world but if I understood that better I would basically just add one called history.js that would prompt the users to provide a path to any folder that is shared across their machines. Then save a history file in there that tracks the commands being run by the user.

Hm, I really really don't think it's a good idea.

I don't use any actual use cases.
The implementation of this will only complicate Ronin, which is not the point of the whole project.
I feel that it is very very specific functionality and will not be useful to the majority of Ronin users.

If you definitely need this functionality for your program, you can either fork Ronin or implement it in your program directly.

Thanks Vadim. Makes sense.


Adding psk_key_exchange_modes extension

Resolved issues:
resolves #970
partially resolves https://github.com/awslabs/s2n/issues/2326
Description of changes:
Adding psk_key_exchange_modes extension as described in the RFC: https://tools.ietf.org/html/rfc8446#section-4.2.9
Call-outs:

Client currently sends only psk_dhe_ke mode only and not psk_ke.
A client MUST provide a "psk_key_exchange_modes" extension if it  offers a "pre_shared_key" extension.  If clients offer "pre_shared_key" without a "psk_key_exchange_modes" extension, servers MUST abort the handshake.

Address any potentially confusing code. Is there code added that needs to be cleaned up later? Is there code that is missing because it’s still in development?
TODO

Ensure/Validate that the server DOES NOT send psk_key_exchange_mode and only client sends.
Ensure that psk_key_exchange mode extension is sent by the client if a pre_shared_key extension is sent.

Testing:
How is this change tested (unit tests, fuzz tests, etc.)? Are there any testing steps to be verified by the reviewer? Unit Tested.
Is this a refactor change? If so, how have you proved that the intended behavior hasn't changed? No, it is a new feature addition.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #2376 (6b065b9) into main (efbb48b) will increase coverage by 6.04%.
The diff coverage is 96.29%.

@@            Coverage Diff             @@
##             main    #2376      +/-   ##
==========================================
+ Coverage   81.84%   87.89%   +6.04%
==========================================
  Files         268      167     -101
  Lines       18300    14093    -4207
==========================================
- Hits        14978    12387    -2591
+ Misses       3322     1706    -1616


Replace OpenMP dependence with command line driven parallelization

With OS X Mavericks, it seems Apple has made clang the default C compiler instead of GCC (well, the GCC command is there, it just calls clang). It also seems that clang does not have OpenMP support. Offhand I can only think of two places in the code I've utilized OpenMP: locus enumeration and locus pairwise comparison. It's doubtful that locus enumeration has benefited significantly from parallelization, so really the only thing at this point that would benefit is the pairwise comparison. My impression is that this would be easy to parallelize with a driver script, which launches n instances on ParsEval. The question then is whether to have each instance run a single sequence at a time or numseq / n sequences.

Parallel execution never sped ParsEval up significantly except when creating graphics in HTML output mode. If parallel execution is ever supported in the future, it should be a two-step process: ParsEval creates HTML output, GFF3 files, and a makefile/bash script that can generate the PNGs in parallel.


Implement upnp for port forwarding

https://www.npmjs.com/package/nat-api
Suggested by @mpetrunic in lodestar's Discord

With libp2p punching NAT holes so efficiently is this necessary for our needs?

With libp2p punching NAT holes so efficiently is this necessary for our needs?

how do you mean? Afaik, we are only having peers that we find and connect to us while nobody can discover and connect to us

how do you mean? Afaik, we are only having peers that we find and connect to us while nobody can discover and connect to us

I've run lodestar behind a NAT and kept a stable peer count. libp2p uses all sorts of tricks to allow connections even if you are not directly reachable https://docs.libp2p.io/concepts/nat/

how do you mean? Afaik, we are only having peers that we find and connect to us while nobody can discover and connect to us

I've run lodestar behind a NAT and kept a stable peer count. libp2p uses all sorts of tricks to allow connections even if you are not directly reachable https://docs.libp2p.io/concepts/nat/

If you find and connect to peer, nat is irrelevant but other nodes cannot find and connect you so you can only depend on nodes you can find.
It's somewhat important to have incoming connections because if there is great surge of new nodes (which will probably find same nodes as we), we would get kicked (nodes are instructed to allow new nodes to connect) and end up with not enough nodes/peers.
As said on your link, libp2p has methods to traverse nat but I'm not sure if js-libp2p implement those (maybe some) and I'm definitely sure that we don't update external ip and port from libp2p and put it in our enr.

As said on your link, libp2p has methods to traverse nat but I'm not sure if js-libp2p implement those (maybe some) and I'm definitely sure that we don't update external ip and port from libp2p and put it in our enr.

Right I've noticed that too, that's important

Actually it's already implemented by libp2p

Tracked in https://github.com/ChainSafe/lodestar/issues/3215


fix: test-build-time

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


SAM Lambda Python Functions are not being deployed with Requirements.txt Modules

Description
When deploying my template which contains Lambda functions, the modules specified on my requirements.txt file are not being deployed. Locally however, in the .aws-sam directory, if I navigate into the functions themselves that are built there, I see the modules within those folders.
The issue seems to be either in the packaging or deploy stage but I'm not sure which.
Additional Info
SAM Version: 0.38.0
On my Linux machine I have no issues, however the issue just started happening when using SAM on MacOS Catalina.
This is prohibiting me from working entirely. I cannot deploy any code changes as none of my Lambdas are working without their required modules.

@nelsynelz How are you running sam package?

If I had to guess, this is what you are running into: https://github.com/awslabs/aws-sam-cli/issues/1569#issuecomment-557196630

@jfuss
I was running it like this:
sam package --template-file template.yml --output-template-file package.yml --s3-bucket <MY_BUCKET>

But I read the template-file line could cause issues so I'm testing now with just this:
sam package --template-file template.yml package.yml --s3-bucket <MY_BUCKET>

Looks like the issue you linked is along similar lines, I'll update shortly whether that fixes my issue or not.
Do you know of a way to force deploy a stack? My issue now is that I deployed the stack and it removed all of my module dependencies. Now when I want to re-deploy it says no changes are detected. Not sure of the best way around this.

Fixed it.
For anyone looking in the future, you need to remove the "--template-file" portion from the sam package command.
sam package --output-template-file package.yml --s3-bucket <MY_BUCKET>

What is working for me is using the template inside the build folder:
sam package --template-file .aws-sam/build/template.yml --output-template-file package.yml --s3-bucket <MY_BUCKET>

@sulfasTor ‘sam package’ will pick up the ‘.aws-sam/build/template.yml’ automatically. No need to pass the ‘—template-file’ at all.


[pcl] Fix PCL install with HEAD

The second part of this patch (find_flann.patch#L16-L24) is already merged in upstream head.
Therefor, This patch doesn't apply when vcpkg install pcl with --head.
But, The first part of this patch (find_flann.patch#L5-L15) will continue to be necessary.
This pull request will fix pcl install with --head by splitting find_flann.patch.
https://github.com/PointCloudLibrary/pcl/issues/2545

LGTM Thanks 👍

I would suggest to wait @KirbX to test it and wait ack.

PCL 1.9.0 has been released! It will solve many problems.
I will send out a new pull request within a few days.


rspec-core/lib/rspec/core/metadata.rb: Allow tag syntax like below to ha...

...ve scenarios, for example, for multiply test cases. And can be run with -t test_case:123
it "should smth", :test_case => [123, 456] do

Specs, please.


Pull Request for part 1e

@Firassawan Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@Firassawan Thank you for signing the Contributor License Agreement!


Ability export test set from the UI as a CSV file

Is your feature request related to a problem? Please describe.
We would like to add a button to export the test set create in the UI as csv file
Describe the solution you'd like

Additional context
The filename should be $testset.csv, if the user did not save the test set yet, we should provide a modal reminding them to do that before (just like we do when they try to navigate out the menu)

Hey mmabrouk, I would like to work on this role. I have experience in various roles and would love to make this my first contribution.

@Sweetdevil144 awesome! I assigned this to you!

@Sweetdevil144 Any updates on this?

Okay @mmabrouk . I have taken help of @aybruhm to setup the agenta app on my system. I have been exploring the file since then and was navigating to find any method  to get my hands on the testcases. I have been facing numerous problems, like, are the test cases stored in the databases, can I use the table to export it directly into a csv format into the host's computer and more such as these. Long way short, I'm struggling to find the exact place where I can get my hands on the data of the test cases to be exported/ Do you have any clue? This is the current directory I'm searching in

I think this is the place where we need to add our export button.

I think this is the file where we need to add our export feature along with our export button

It seems you are in the right place. The data in the table is saved in rowData while the header is saved in columnDefs. I would first try to console.log these inside a useEffect each timethey change. Then I'd try to create a button that export some data as a csv, last I would try to extract that data. Hope that helps

I'm thinking of using the following method to export data.
const convertToCsvFormat = (data) => {
    // Convert data to CSV format...I will try to use the doc you sent me for this purpose
    // This is a simple conversion and might need adjustments based on the data structure.
    const header = Object.keys(data[0]).join(",");
    const rows = data.map(row => Object.values(row).join(",")).join("\n");
    return `${header}\n${rows}`;
};

const downloadCsv = (csvContent, filename) => {
    const blob = new Blob([csvContent], { type: "text/csv" });
    const link = document.createElement("a");
    link.href = URL.createObjectURL(blob);
    link.download = filename;
    document.body.appendChild(link);
    link.click();
    document.body.removeChild(link);
};

Issue fixed

### Creating a PR for the same.

Thanks for your response everyone. Let's close the issue for now. It was great working with you.


cleaned up root

Description
Fixes # (issue)
Type of change
Please delete options that are not relevant.

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

Change Status

[ ] Complete, tested, ready to review and merge
[ ] Complete, but not tested (may need new tests)
[ ] Incomplete/work-in-progress, PR is for discussion/feedback

How Has This Been Tested?

[ ] Test A
[ ] Test B

Checklist

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] My code has been reviewed by at least one peer
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] There are no merge conflicts

Hey nerds, my internet is out, will advise when back up
On Fri, Apr 17, 2020, 6:51 PM Tim Jeffries<EMAIL_ADDRESS>wrote:

Merged #83 https://github.com/Lambda-School-Labs/voicer-fe/pull/83 into
master.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Lambda-School-Labs/voicer-fe/pull/83#event-3246431170,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEVL7LZWMSA5LQMWDD2V5VLRNEBTNANCNFSM4MLE6UMA
.


Set all obj to nil and add an optional config to determine whether we should manually call runtime.GC() in the close() method

We noticed that it's not every reference relationship in the db instance will cut down when the user calls the close() method, so if we want to release memory after calling the close method. So that's an optimal approach to cut down all the reference relationships of the fields in the db instance and add an optional config in the Options object to determine whether it should call runtime.GC() to release memory immediately.
我们发现在调用close方法的时候并不是所有字段对象的引用都会在close方法中断掉，这个时候有一些内存实际上不能被马上清楚掉，所以这里提供了一个优化的机会，也就是在close方法中把所有对象都设置成nil，并且可以添加一个配置选项，在close方法的最后手动调用一次runtime.GC() 可以帮助立马释放掉内存。由于手动GC会带来一些性能损耗，比如程序停顿，所以这是一个选项，开这个口子给用户选择。

@infdahai Hi, this task has been taken a few minutes ago in this issue #347, would you like to take another interesting task? thanks.

Ok, I see that.

was fix by this PR. https://github.com/nutsdb/nutsdb/pull/374


Fix memory leak of DLManagedTensor

Motivation
https://github.com/InternLM/lmdeploy/issues/1334
This test code and valgrind can help debug this issue:
import asyncio
from lmdeploy import GenerationConfig, TurbomindEngineConfig, pipeline

engine_config = TurbomindEngineConfig(tp=1)
engine = pipeline(model_path='/workdir/llama2_13b_chat',
                model_name='llama2',
                backend_config=engine_config)

async def infer(prompt, session_id):
    async for output in engine.generate(messages=prompt,
                                    session_id=session_id,
                                    stream_response=True,
                                    do_preprocess=False):

        print(output.response)

prompts = ['hi']*10

for i, prompt in enumerate(prompts):
    asyncio.run(infer(prompt, i))

valgrind --leak-check=full python test_lmdeploy.py > log.txt 2>&1

There are some definitely lost in bind.cpp:125 and bind.cpp:308, that's about DLManagedTensor.
After this change,

rerun the valgrind test, there is no memory leak of DLManagedTensor.
test the api_server with 5000 prompts, the memory usage will increase from 3110M to 3330M.

Modification

remove the unique pointer and add the deleter for DLManagedTensor

For 20000 prompts, the memory usage will be stable at 3515M.

LGTM

@AllentDan @grimoire could you help review?

After this fix, it is confirmed that the memory leak issue of the API Server has been resolved. May you take a look? Thanks. @lvhan028 @grimoire @AllentDan
python3 -m lmdeploy serve api_server /workdir/llama2_13b_chat

python3 benchmark/profile_restful_api.py --server_addr <IP_ADDRESS>:23333 --tokenizer_path /workdir/llama2_13b_chat --dataset /workdir/ShareGPT_V3_unfiltered_cleaned_split.json --concurrency 128 --num_prompts 50000


integrate as panel in devtools

On latest Ya.Subbotnik there was a request to see dynamic test results while test are running.
You said that you can see test results while it running in tab, but test will be slowdown by chrome, since it running in not active tab.
One proposed solution was to use separate instance of chrome.
Another possible solution is to integrate dynamic report as panel in chrome devtools, so it will not affect visibility of current tab.

hi Aleksey!
I also thought about it. But there is a restriction in Chrome that only one debugger can be attached to the page: https://bugs.chromium.org/p/chromium/issues/detail?id=129539
So if we open devtools (that uses own debugger) Autotester's debugger will be detached.
Btw, why it is important for you to watch test results dynamically?


No notifications after update from 4.2.10 to 5.0.16

I'm have 2 cameras configured that I trigger via mqtt to send a picture as telegram notification.
With 4.2.10 everything works fine.
I tried twice to update to version 5.
After update I get no notifications any more. Not in camera-ui web interface and not via telegram.
After update I reconfigured the telegram settings, activated notifications (in Notification settings and for each camera).
But on mqtt message
[14.2.2022, 14:31:29] [CameraUI] Einfahrt ZM: Motion ON
is logged, but nothing else.
If I downgrade to 4.2.10 everything is working as usual.
What am I doing wrong?

I'm having the exact same issue.

Does no one have a hint for me. I have to stay on 4.2.10

Do you have enabled notifications? and camera specific notification options like telegram etc?

@seydx Yes I do.

@seydx Yes I do.

Checked also Settings > Cameras > CAMERANAME > Notifications > Telegram ?

Yes and the Telegram-specific settings match that of the other camera. I should note that it’s also native notifications that are having this issue as well. Which man’s the native recordings aren’t working either.
On Apr 10, 2022, at 23:25, seydx @.***> wrote:

@seydx Yes I do.
Checked also Settings > Cameras > CAMERANAME > Notifications > Telegram ?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.

@ucfhall
can you enable debug and trigger a motion pls, i need the full log (with debug enabled)

Posted in issue 445
On Apr 10, 2022, at 23:37, seydx @.***> wrote:

@ucfhall
can you enable debug and trigger a motion pls, i need the full log (with debug enabled)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.

Same problem. But message about sending to Telegram not appeared in log

@ucfhall @ShadyRover
can you send me your database.json (should be located in " /var/lib/homebridge/camera.ui/database/database.json)

Database in attach. My config:
{   "debug": false,   "port": 8081,   "atHomeSwitch": false,   "options": {     "videoProcessor": "ffmpeg"   },   "ssl": {     "active": false   },   "http": {     "active": false,     "port": 7272,     "localhttp": false   },   "smtp": {     "active": true,     "port": 2727,     "space_replace": "+"   },   "ftp": {     "active": false,     "useFile": false,     "port": 5050   },   "mqtt": {     "active": false,     "tls": false,     "port": 1883   },   "cameras": [     {       "name": "Main Entrance Door",       "manufacturer": "EZVIZ",       "model": "C6C",       "motion": true,       "unbridge": true,       "hsv": true,       "prebuffering": true,       "prebufferLength": 4,       "motionTimeout": 5,       "videoConfig": {         "source": "-i rtsp://root:pass@xx.xx.xx.xx:1111/ISAPI/Streaming/Channels/101",         "subSource": "-i rtsp://root:pass@xx.xx.xx.xx:1111/ISAPI/Streaming/Channels/102",         "stillImageSource": "-i rtsp://root:pass@xx.xx.xx.xx:1111/ISAPI/Streaming/Channels/102",         "rtspTransport": "tcp",         "maxStreams": 2,         "vcodec": "copy",         "acodec": "libfdk_aac",         "stimeout": 10,         "audio": false,         "readRate": false,         "debug": true       },       "mqtt": {},       "smtp": {         "email"<EMAIL_ADDRESS>        "from": "Door",         "body": ""       },       "videoanalysis": {         "active": true       },       "recordOnMovement": false     },     {       "name": "Backside",       "manufacturer": "Hikvision",       "model": "C6C",       "motion": true,       "unbridge": true,       "hsv": true,       "prebuffering": true,       "prebufferLength": 4,       "motionTimeout": 5,       "videoConfig": {         "source": "-i rtsp://root:pass@xx.xx.xx.xx:1111/ISAPI/Streaming/Channels/101",         "subSource": "-i rtsp://root:pass@xx.xx.xx.xx:1111/ISAPI/Streaming/Channels/102",         "stillImageSource": "-i rtsp://root:pass@xx.xx.xx.xx:1111/ISAPI/Streaming/Channels/102",         "rtspTransport": "tcp",         "maxStreams": 2,         "vcodec": "copy",         "acodec": "libfdk_aac",         "stimeout": 10,         "audio": false,         "readRate": false,         "debug": true       },       "mqtt": {},       "smtp": {         "email": "Backside"       },       "videoanalysis": {         "active": true       },       "recordOnMovement": false     },     {       "name": "Leftside",       "manufacturer": "Hikvision",       "model": "C6C",       "motion": true,       "unbridge": true,       "hsv": true,       "prebuffering": true,       "prebufferLength": 4,       "motionTimeout": 5,       "videoConfig": {         "source": "-i rtsp://root:pass@xx.xx.xx.xx:1111/ISAPI/Streaming/Channels/101",         "subSource": "-i rtsp://root:pass@xx.xx.xx.xx:1111/ISAPI/Streaming/Channels/102",         "stillImageSource": "-i rtsp://root:pass@xx.xx.xx.xx:1111/ISAPI/Streaming/Channels/102",         "rtspTransport": "tcp",         "maxStreams": 2,         "vcodec": "copy",         "acodec": "libfdk_aac",         "stimeout": 10,         "audio": false,         "readRate": false,         "debug": true       },       "mqtt": {},       "smtp": {         "email": "Leftside"       },       "videoanalysis": {         "active": true       },       "recordOnMovement": false     }   ] }
database.json.zip
Email and telegram notifications not working

Thank you, now it works.
One question: On version 4.x I got one notification on motion topic and another notification on motion reset topic.
e.g. on "open" and again on "closed"
With 5.0.27 I get a notification on "open", but not on the reset topic.
Here a log example:
On Motion topic this is logged:
[27.4.2022, 13:41:14] [CameraUI] MQTT: New message: Topic: homebridge/blau/fahrradschuppen - Data: auf - Type: string
[27.4.2022, 13:41:14] [CameraUI] Carport ZM: Movement delay (2s) is active, wait before triggering the event - Trigger: motion - State: true - Event: mqtt
[27.4.2022, 13:41:16] [CameraUI] Carport ZM: Motion ON
[27.4.2022, 13:41:21] [CameraUI] Carport ZM: Motion OFF - Motion handler timeout.
On Motion reset topic this is logged, but no notification:
[27.4.2022, 13:41:32] [CameraUI] MQTT: New message: Topic: homebridge/blau/fahrradschuppen - Data: zu - Type: string
[27.4.2022, 13:41:32] [CameraUI] Carport ZM: Movement delay (2s) is active, wait before triggering the event - Trigger: motion - State: false - Event: mqtt
What is wrong in my configuration?


Gauge component not working in Kitchen sink

Framework7 version: [e.g. 3.2.1]
Platform and Target: [e.g. all]

Describe the bug
framework7.esm.bundle.js is missing
import Gauge from './components/gauge/gauge';
Step to reproduce
install all dependencies
$ npm install
And build development version of Framework7:
$ npm run build:dev
Build production version of Framework7:
$ npm run build:prod
Run Kitchen Sink with production environment (configured to scripts and styles from dist/ folder):
//this will correct path for the template
$ npm run prod
Then i get the error
VM146:16 Uncaught TypeError: Cannot read property 'create' of undefined
---> var demoGauge = app.gauge.create({

Can see it here at https://github.com/framework7io/framework7/blob/master/packages/core/framework7.esm.bundle.js which built with same npm run build:prod

OK, my fault, I now see that I did not update my  build-custom-config.js file.
// Gauge
    'gauge',

Then I ran "npm run build:prod" and "import Gauge from './components/gauge/gauge';" was removed.


Fix Gallery grid demo zoom

Fixes #6449

LGTM
I wonder if we should make a widget that does this for you (listens for the gesture and transforms/clips its child).

Creating such a widget sounds like a good idea. I will take a crack at that.


Missing Pruvious Dashboard Translations

Hey Muris!
I found another thing that came up. My current project is only in German, so I was faced with updating my languages in the nuxt.config.ts as described by the docs. (So that the correct html lang="de" is rendered.)
Everything in the frontend works well, but in the dashboard, Pruvious is looking for the german translated-strings file (which currently does not exist). So now I have a couple of $item and $page springled in the dashboard. (See image attached).

I don't think this is a big issue for me at the moment, but I was thinking that it would be nice if pruvious had some translations for the dashboard in a couple of languages out of the box. I do only speak German and English (as do you afaik 😄 ), but I'd be happy to translate the default dashboard file to German with a PR. Maybe someone else would like to do other langs and so on too.
Should I create one in src/runtime/translatable-strings/standard/ ?
I the meantime, I think it would also be a good addition if English would be displayed if the other translated strings don't exist (which already kinda works, but breaks with variables as it seems).
Anyway, let me know what you think!
Cheers!

 Entweder so oder über BuyMeACoffee oder so 😃

Hey Dominik!
This should be fixed now in v3.11.7. I added a definitive fallback in English for the translatable strings API route. Before that, the fallback was the primary language (in your case DE), which is why you received a 404 error when trying to fetch the translatable strings (the dashboard strings are only available in English at the moment). The 'Search $items' and 'Add $item' are just string patterns that are displayed as fallback strings in Vue components.
Regarding dashboard translations in general - I've prepared this feature from the start, but never found the time to fully implement and test it. Users already have a hidden field called dashboardLanguage:
https://github.com/pruvious/pruvious/blob/25a83aeeceb2ca879307ba4f4a7b3334a6bf0e9f/src/runtime/collections/standard/users.collection.ts#L314-L332

Gerne können wir uns zu einem Bier treffen! Schreib mir über Discord, wann es dir passt :)


When calling $state.go with notify = false resolve function is executed

I want to change the state without reloading the controller. All seems to work fine except that my resolve function is always called.
To change state I use:
$state.go("home", {param1:"changed" + changes++}, { notify : false});

Here my plnkr: http://plnkr.co/edit/jo3C56ZwkPE27FtRU1Y6
Basically I log each time the controller is loaded or the resolve is called, then I added a button to change the state. As you can see resolve is always called also with notify = false.
What do you think? My problem is that inside the resolve I load some resource and I want this code to be called only when really changing state, not when changing state using notify=false.
I use version ui-router 0.2.15 and angular 1.4.3.

Does seem like a bug

Thinking more about this...notify is documented as:

If true will broadcast $stateChangeStart and $stateChangeSuccess events

Documentation doesn't mention nothing about controller and resolve feature.
My goal is to change the state (logically and also changing the location) without reloading the controller and without calling the resolve method again. Is the notify:false the right approach?
thanks

Looking at the code I have a possible solution, here my fork+commit: https://github.com/davideicardi/ui-router/commit/7198aa2b3618f11b376949a80e2b7c4c6640cd4c
Basically I have checked the notify options inside shouldSkipReload function. I have also added a unit test. (don't know why there are also other CRLF changes...).
If you want I can create a pull request.
Eventually I have also a workaround, http://plnkr.co/edit/hz3f7qORaHFZyiwHDZo7?p=preview. I have added a custom "resolve" params and use it as an option to check if calling or not the resolve functions. So I can call the $state.go like this:
$state.go("home", {param1:"changed" + changes++, resolve: false}, { notify : false});

But I don't like this solution, seems to be just a workaround.
What do you think? I'm not sure what is the right approach...

Seems related to #2108 and #2087

#2108 has the controller reinitialize when changing to a different state. This has the resolve fired but not the controller so its slightly different.

Documentation doesn't mention nothing about controller and resolve feature.

Right... that's because it's totally unrelated: notify is only about events. Why is this confusing?

My final goal is to change the state and browser URL (actually I just need to change a state par) without reloading the controller or calling the resolve. What is the best solution for you? I just don't understand how to solve my problem.
Thanks!

Why?

Basically I have backoffice application where the user can add new articles. So I have a state like "/stories/{id}".
When the user want to create a story I go to "/stories/new". He fills some fields and the using an autosave feature (more or less like Google doc) the story is saved and I assign it an I'd. So I want to change the state and go to "/stories/57543", but I don't actually need to reload anything.
Maybe there is another solution?
Thanks

Plenty of ways to replace the url but the original issue is still valid:

resolve is always called also with notify = false

Thanks Eddie but what do you suggest for changing url?
For me it should be some ui-router feature, something like:
$state.go("mystate", { reload: false })

or
$state.change("mystate")

In my opinion is a state change just like any other, the only problem is that the user is actually already in this state (all the required data are loaded) so I just don't want to reload anything.

$location.path() with a $locationChangeStart set to preventDefault?

Yeah, see the example with the sync() method here: https://angular-ui.github.io/ui-router/site/#/api/ui.router.router.$urlRouter

@nateabele Shouldn't the example use $locationChangeStart instead of $locationChangeSuccess?
Also, it's not helping regarding the url change imo. If I don't use sync() the url won't change, but if I use it, it will just open the state fully, not just updating the url.

@nateabele I've been working on a project and having a similar issue as that discussed here.  This is my use case:  When transitioning to a state, a resolve block is completed.  Once in the new state, a component determines whether or not the url needs to be changed.  The goal is to remain in exactly the same state, but to modify the url.  However, when I make the url modification using something like this:
$state.go($state.$current.self.name, {newparams}, {location: 'replace', reload: false, notify: false});
The entire state remains the same and the url is updated.  However, the resolve block is the called again.  Is it not possible to prevent the resolve block from running?


⚠ ClamAV has degraded performance

In d699f44, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 645 ms

Resolved: ClamAV performance has improved in 12f4fd1.


TEST ONLY Bug: MP Evaluate

Issue:
API Communication errors.  Evaluation finished on Monitoring Plan but kept loading something in other sections
Steps to Recreate:

Check out 7336 config ACT1
Go to Export & Report section
Export to file
Import from file
Go to Evaluation
Select Anderson/Config ACT1
Apply filters
Check Monitoring Plan box
Click on Evaluation

Private Zenhub Image

The errors do not seem to appear anymore.

The issue does not seem to exist anymore.


Is there a way to stop key delivery

I can use f1 to emulate button1, but f1 also triggers original function in apps

libuiohook has not implement this for X11, see issues


Windows 10. Edit files with paths longer than 255 chars.

Is your feature request about something that is currently impossible or hard to do? Please describe the problem.
Vim can not edit files with very long paths. Windows Notepad.exe can do that.
Reproduction:
Open cmd.exe
mkdir \tmp\verylongpath\verylongpath2\verylongpath2\verylongpath2\verylongpath2\verylongpath2\verylongpath2\verylongpath2\verylongpath2\verylongpath2\verylongpath2\verylongpath2\verylongpath2\verylongpath2\verylongpath2\verylongpath2\verylongpath2
vim --clean \tmp\verylongpath\verylongpath2\verylongpath2\verylongpath2\verylongpath2\verylongpath2\verylongpath2\verylongpath2\verylongpath2\verylongpath2\verylongpath2\verylongpath2\verylongpath2\verylongpath2\verylongpath2\verylongpath2\verylongpath2\test1234567.txt
Insert some text (or don't) and write the file.
The latter works fine.
vim --clean \tmp\verylongpath\verylongpath2\verylongpath2\verylongpath2\verylongpath2\verylongpath2\verylongpath2\verylongpath2\verylongpath2\verylongpath2\verylongpath2\verylongpath2\verylongpath2\verylongpath2\verylongpath2\verylongpath2\verylongpath2\test12345678.txt
:wq will result in "E212: Can't open file for writing"
Describe the solution you'd like
Notepad has no trouble to read/write/create files with long paths.
Describe alternatives you've considered
Copy the files somewhere, edit with vim and copy back. Very inconvenient.
Additional context
Console vim or gvim has the same result.
Windows 10 Version 21H1 (OS Build 19043.1466)
VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Feb  2 2022 23:14:52)
MS-Windows 32-bit console version
Included patches: 1-4286
Compiled by appveyor@APPVYR-WIN
Huge version without GUI.  Features included (+) or not (-):
+acl                +ex_extra           +multi_lang         -tag_any_white
+arabic             +extra_search       +mzscheme/dyn       +tcl/dyn
+autocmd            -farsi              -netbeans_intg      +termguicolors
+autochdir          +file_in_path       +num64              +terminal
+autoservername     +find_in_path       +packages           -termresponse
-balloon_eval       +float              +path_extra         +textobjects
+balloon_eval_term  +folding            +perl/dyn           +textprop
-browse             -footer             +persistent_undo    -tgetent
++builtin_terms     +gettext/dyn        +popupwin           +timers
+byte_offset        -hangul_input       -postscript         +title
+channel            +iconv/dyn          +printer            -toolbar
+cindent            +insert_expand      +profile            +user_commands
+clientserver       +ipv6               +python/dyn         +vartabs
+clipboard          +job                +python3/dyn        +vertsplit
+cmdline_compl      +jumplist           +quickfix           +vim9script
+cmdline_hist       +keymap             +reltime            +viminfo
+cmdline_info       +lambda             +rightleft          +virtualedit
+comments           +langmap            +ruby/dyn           +visual
+conceal            +libcall            +scrollbind         +visualextra
+cryptv             +linebreak          +signs              +vreplace
+cscope             +lispindent         +smartindent        +vtp
+cursorbind         +listcmds           -sodium             +wildignore
+cursorshape        +localmap           +sound              +wildmenu
+dialog_con         +lua/dyn            +spell              +windows
+diff               +menu               +startuptime        +writebackup
+digraphs           +mksession          +statusline         -xfontset
-dnd                +modify_fname       -sun_workshop       -xim
-ebcdic             +mouse              +syntax             -xpm_w32
+emacs_tags         -mouseshape         +tag_binary         -xterm_save
+eval               +multi_byte_ime/dyn -tag_old_static
system vimrc file: "$VIM\vimrc"
user vimrc file: "$HOME_vimrc"
2nd user vimrc file: "$HOME\vimfiles\vimrc"
3rd user vimrc file: "$VIM_vimrc"
user exrc file: "$HOME_exrc"
2nd user exrc file: "$VIM_exrc"
defaults file: "$VIMRUNTIME\defaults.vim"
Compilation: cl -c /W3 /GF /nologo -I. -Iproto -DHAVE_PATHDEF -DWIN32  -DFEAT_CSCOPE -DFEAT_TERMINAL -DFEAT_SOUND  -DFEAT_JOB_CHANNEL -DFEAT_IPV6        -DWINVER=0x0501 -D_WIN32_WINNT=0x0501 /source-charset:utf-8 /MP -DHAVE_STDINT_H /Ox /GL -DNDEBUG /arch:IA32 /Zl /MT /D_CRT_SECURE_NO_DEPRECATE /D_CRT_NONSTDC_NO_DEPRECATE -DFEAT_MBYTE_IME -DDYNAMIC_IME -DDYNAMIC_ICONV -DDYNAMIC_GETTEXT -DFEAT_TCL -DDYNAMIC_TCL -DDYNAMIC_TCL_DLL="tcl86t.dll" -DDYNAMIC_TCL_VER="8.6" -DFEAT_LUA -DDYNAMIC_LUA -DDYNAMIC_LUA_DLL="lua54.dll" -DFEAT_PYTHON -DDYNAMIC_PYTHON -DDYNAMIC_PYTHON_DLL="python27.dll" -DFEAT_PYTHON3 -DDYNAMIC_PYTHON3 -DDYNAMIC_PYTHON3_DLL="python310.dll" -DFEAT_MZSCHEME -I "C:\racket\include" -DMZ_PRECISE_GC -DDYNAMIC_MZSCHEME -DDYNAMIC_MZSCH_DLL="libracket3m_da32rk.dll" -DDYNAMIC_MZGC_DLL="libracket3m_da32rk.dll" -DFEAT_PERL -DPERL_IMPLICIT_CONTEXT -DPERL_IMPLICIT_SYS -DDYNAMIC_PERL -DDYNAMIC_PERL_DLL="perl532.dll" -DFEAT_RUBY -DDYNAMIC_RUBY -DDYNAMIC_RUBY_DLL="msvcrt-ruby300.dll" -DRUBY_VERSION=30 -DFEAT_HUGE /Fd.\ObjCULYHTRZi386/ /Zi
Linking: link /nologo /opt:ref /LTCG oldnames.lib kernel32.lib advapi32.lib shell32.lib gdi32.lib  comdlg32.lib ole32.lib netapi32.lib uuid.lib user32.lib  /machine:i386   libcmt.lib   /nodefaultlib:lua54.lib  /STACK:8388608  /nodefaultlib:python27.lib /nodefaultlib:python310.lib   "C:\Tcl\lib\tclstub86.lib" winmm.lib WSock32.lib Ws2_32.lib /PDB:vim.pdb -debug

Hm, according to a quick google https://docs.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=cmd

In the Windows API (with some exceptions discussed in the following paragraphs), the maximum length for a path is MAX_PATH, which is defined as 260 characters

But apparently you can use the \\?\ prefix
The maximum path of 32,767 characters is approximate, because the "\\?\" prefix may be expanded to a longer string by the system at run time, and this expansion applies to the total length.
so probably Notepad is doing this.
A workaround may be to use the good old cmd SUBST to map your long path to a separate drive letter.

As the above page explains, there is another way since Windows 10 1607.

To enable the new long path behavior, both of the following conditions must be met:

The registry key Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\LongPathsEnabled (Type: REG_DWORD) must exist and be set to 1.
The application manifest must also include the longPathAware element.

Anyway, current Vim's implementation depends on the MAX_PATH limit.
$ grep MAX_PATH *.c *.h | wc -l
53

yes I saw that, but I did not mention it, because I worried Vim couldn't handle it because of the MAX_PATH limit (you also mentioned) :)