fix(frontend): permit drop_table catalog even when catalog is missing

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
As mentioned: https://github.com/risingwavelabs/risingwave/pull/17576#issuecomment-2209453665.
The following sequence of events can occur:

MV with id 2000 committed to meta store
FE killed.
CN killed
From (3), Finish stream job fails.
From (2) FE restarted, subscribe meta.
From (3), Meta cleans up catalogs, removing id=2000.
From (2) Meta notifies the newly subscribed meta of the existing catalogs. This does not include 2000 since it's already cleaned.
From (3), Meta issues a clean stream job command for 2000, but it's not in the FE catalog at all, only tables from (7) are inside. So FE will just panic when trying to remove this stream job's table.

The solution is just to permit drop_table to fail with a warn log, if the table is missing.

Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added test labels as necessary. See details.
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[ ] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

From (3), Meta issues a clean stream job command for 2000, but it's not in the FE catalog at all, only tables from (7) are inside. So FE will just panic when trying to remove this stream job's table.

IIUC, meta always notify catalog changes to FE while persisting catalog in metastore, which is mutually exclusive with the read of snapshot for subscribe. 🤔  And we always unwrap the operation of catalog changes in FE is to verify the mechanism of notification, we'd better not change it.

From (3), Meta issues a clean stream job command for 2000, but it's not in the FE catalog at all, only tables from (7) are inside. So FE will just panic when trying to remove this stream job's table.

IIUC, meta always notify catalog changes to FE while persisting catalog in metastore, which is mutually exclusive with the read of snapshot for subscribe. 🤔 And we always unwrap the operation of catalog changes in FE is to verify the mechanism of notification, we'd better not change it.

Yes it is exclusive originally. But after #17484, we can have:

fe receives and updates catalog snapshot on subscribe.
fe also receives delete notification for a dropped stream job. The table id may not be in the snapshot of 1.

And we always unwrap the operation of catalog changes in FE is to verify the mechanism of notification, we'd better not change it.

I don't mind keeping it, but haven't thought of a better way to solve this problem yet, since deleting a catalog in meta and FE receiving and processing the notification is not transactional.

Yes it is exclusive originally. But after #17484, we can have:

fe receives and updates catalog snapshot on subscribe.
fe also receives delete notification for a dropped stream job. The table id may not be in the snapshot of 1. You can see the PR description for how this can happen. See buildkite.com/risingwavelabs/main-cron/builds/2788 for the failing test.

Does it caused by non-transactional of cancel_create_materialized_view_procedure?

I don't mind keeping it, but haven't thought of a better way to solve this problem yet, since deleting a catalog in meta and FE receiving and processing the notification is not transactional.

If so, can we make it transactional like start_create_materialized_view_procedure? We can release the core lock after notification.

If so, can we make it transactional like start_create_materialized_view_procedure? We can release the core lock after notification.

Actually yes, that could work.

If so, can we make it transactional like start_create_materialized_view_procedure? We can release the core lock after notification.

Actually yes, that could work.

It works.


fix 1051: reset backup target to default

Problem:
After PR of #1447, the "Use the default value" of "backup target" will be refused by webhook, the error message is:
admission webhook "validator.harvesterhci.io" denied the request: Destination URL hasn't been specified
It is not possible to reset backup target to the default value in the web UI.
Solution:
In webhook, check the backup target as per specific requirements to each field,  S3, NFS, Default are different.
For S3, there is an re-update operation, needs special check to identify it is from user input or internal
In controller, add process of default backup target.
Related Issue:
#1051
Test plan:
Setup a harvester cluster (one node is also OK)

The initial backup target is blank (default), when you create a VM and operate the "take backup", will be refused.

Set the backup target
2.1 When backup target has error (endpoint is not reachable/bucket name is wrong/bad credentials...), "save" will be refused with an error message, and after refreshing the web page, the backup target is still the last setting
2.2 When backup target is correct, it is saved.
2.2.1 "take backup" on VM will be allowed
(another commit will block user change the backup target if a backup target is ongoing)

2.3 "Edit" again, click "Use the default value" button and "save", it will be success, and backup target is reset to default value.
2.3.1 "take backup" on VM will be refused
2.4 Set a correct backup target of S3/minio, then "edit", if you leave input access key / ID  blank, and change the bucket name/region/endpoint,  save will NOT be allowed,   before this commit, you can do it, it is a BUG
2.5 Set a correct backup target of S3/minio, use kubectl can check a related secret created
kubectl get secrets -A | grep backup
longhorn-system                          harvester-backup-target-secret                                       Opaque                                8      57s

change the backup target to NFS or reset to default, this secret will be deleted.  Before this commit, it is leaved there.

FYI.
I still have a few open questions regarding this commit, but would like to have a pull request to review the overall code changes first.

@FrankYang0529 @guangbochen
The "use the default value" of backup target, change / refactor the original part, please take time to review it, thanks.
Please skip the "CodeFactor" issues, some of them are already existing, only because this commit changes some of the related file.

The panic caused by nil pointer access, is merged via
https://github.com/harvester/harvester/pull/1674


Wrong highlighting color for the field named type

Hi, after the recent updating of the plugin in phpstorm the type field name is highlighted wrong. The plugin version is 3.1.4.

@mostafa-rz hi! What color scheme do you use?

@vepanimas Dracula


some problem with  TX Ultimate 4 Gang US (T5-4-120)

Hi, I'm having some issues with the TX Ultimate 4 Gang US (T5-4-120):
If I turn on the light, I'm unable to turn it off again.
The same light doesn't fully illuminate (photo attached).
All the LEDs (top-right-left-bottom) are not correctly synchronized (I’m attaching a photo of the top light), and they don't turn off.
Have other people had the same problems?
I can't figure out how to correct the error!

I can try to,duplicate the issues, however, I’m unsure if I fully understood all of those. Could you please provide more details of what was expected behaviour and how it is behaving for each of the issues you reported?

🤔

Sorry, I was quite busy those days...
I will look at this later today.

Unfortunately, the problem hasn't been resolved. A short section of the LEDs is not lighting up.
Additionally, when I turn on the LEDs, it's not possible to turn them off. The switch on the panel turns off, but the LEDs remain on.
Is there anything I can do to help you understand the issues?
Thank you for your efforts.

Could you please update to the latest version and try again?
Please let me know the results.


Feature request - get app description

Similar to getAppName

Windows has description also, it's often the subtitle when the app is shown in a list

Windows Object (including description): https://docs.microsoft.com/en-us/uwp/api/windows.applicationmodel.package
Example usage
https://github.com/Microsoft/Windows-universal-samples/blob/master/Samples/Package/js/js/scenario1_identity.js#L55


Installation Issue

Im tryi ng to install on my windows 10 64 bit and I ge tthe following error:
problem running post-install step. Installation may not complete correctly
Error creating directory H:/ .flickr-downloadr
The progrma will not start after this, any ideas?

It looks like you might not have access to write into the H:\ drive.
You could temporarily add an environment variable named HOME that points to %USERPROFILE% and rerun the installer.  To see how to set an environment variable, see this article

I do have access to write to the h drive it's my pers9nal network drive

From: Hari Menon<EMAIL_ADDRESS>Sent: 06 June 2017 00:10:37
To: flickr-downloadr/flickr-downloadr-gtk
Cc: theweazel; Author
Subject: Re: [flickr-downloadr/flickr-downloadr-gtk] Installation Issue (#51)
It looks like you might not have access to write into the H:\ drive.
You could temporarily add an environment variable named HOME that points to %USERPROFILE% and rerun the installer. To see how to set an environment variable, see this articlehttps://www.computerhope.com/issues/ch000549.htm
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/flickr-downloadr/flickr-downloadr-gtk/issues/51#issuecomment-306335981, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AbnNsjrtXiETlcXRDUGEpJwTLf4QbfT9ks5sBIrtgaJpZM4Nma2b.

Uhm so your home directory is a network disk? Probably the software is appending "/.flickr-downloadr" to "H:", which is not a good idea :)
Try what has been said before:

add an environment variable named HOME that points to %USERPROFILE% and rerun the installer

Please try again with the latest version and let us know if this issue needs to be reopened.


ignore precompile.jl for coverage

Coverage remained the same at 89.212% when pulling 1d4a749a9f1593705ed55c88cb892758a13ad753 on hr/ignore_precompile_coverage into 216c546e224704c5a0b853882e44e0120dfcd636 on main.


run "publish to s3" steps on the new deploy-production agents

The "deploy" queue currently runs on the bastion, and we're trying to move things off that so it can be shut down.
publishing to s3 requires the buildkite-agent (to fetch metadata) and awscli (to push to s3), both of which are available on the elastic stack agents that process the "deploy-production" queue.
There's a good chance the agents won't have IAM permissions for pushing to the bucket, but we can address that if it happens.

This is difficult to test ahead of time, so I'm going to just merge and see how it goes.
I've set the release pipelines to DRY_RUN: true, so nothing will actually be deployed.


#1033 Values moved to placeholders

Close #1033
Thank you for your Pull Request! We have developed this task checklist from the Development Process Guide to help with the final steps of the process. Completing the below tasks helps to ensure our reviewers can maximize their time on your code as well as making sure the admiral codebase remains robust and consistent.
Please check off each taskbox as an acknowledgment that you completed the task or check off that it is not relevant to your Pull Request. This checklist is part of the Github Action workflows and the Pull Request will not be merged into the devel branch until you have checked off each task.

[x] Code is formatted according to the tidyverse style guide
[x] Updated relevant unit tests or have written new unit tests - See Unit Test Guide
[x] If you removed/replaced any function and/or function parameters, did you fully follow the deprecation guidance?
[x] Update to all relevant roxygen headers and examples
[x] Run devtools::document() so all .Rd files in the man folder and the NAMESPACE file in the project root are updated appropriately
[x] Address any updates needed for vignettes and/or templates
[x] Update NEWS.md
[x] Build admiral site pkgdown::build_site() and check that all affected examples are displayed correctly and that all new functions occur on the "Reference" page.
[x] Address or fix all lintr warnings and errors - lintr::lint_package()
[x] Run R CMD check locally and address all errors and warnings - devtools::check()
[x] Link the issue so that it closes after successful merging.
[x] Address all merge conflicts and resolve appropriately
[x] Pat yourself on the back for a job well done!  Much love to your accomplishment!

@teckla-gsk I think this is ready to review!  Hopefully all the tests past now.

Hey Teckla. I'm trying to fix the check_tempaltes.  Can you re-approve this to see if it goes through okay?

Done.


auto compile failed

demo
steps

open .scss
change backround value
preview not reload successfully，you must click refresh button

Can't repro. Reopen with reproducible case if possible ;)


[3.0.0] Should we have messageId and name fields in Message Object?

We had discussion about it in the 3.0 meeting - https://youtu.be/H5P-gBwdFs0?t=506 (started from given second - about 25 minutes).
We wonder if we need name and messageId in new v3 spec. We can treat keys in channel[x].messages object as messageId. This means that messageId (object key) then will be unique against the channel and not against the specification/application. We should discuss whether the change is a good one or whether we should rather leave messageId and name. WDYT?
cc @jonaslagoni @fmvilas @smoya @derberg @dalelane @char0n
You are also very important @WaleedAshraf You added messageId to the specification and we will be very grateful if you will add your 2 cents :)

@WaleedAshraf Yeah, but that messageId will be indicated by map key, where message is defined, so it will be required but you won't have option to not define key of map - in other words, messageId will be always set.
However, thinking about it second time I think that messageId is very important when you have registry for your system - each app which will reference to the registry should "share" this same message and messageId can indicated uniqueness of message in system.

From https://github.com/asyncapi/spec/pull/796#issuecomment-1167242385
Let's check the definition for messageId field at https://www.asyncapi.com/docs/reference/specification/v2.5.0#messageObject:

A machine-friendly name for the message.

Now let's think, Isn't the messageId right made for that purpose?
My suggestion is to go further and deprecate name field.

Another discussion that should take place (unless there is a clear reason) is why do we have title. I would either leave name or title, but not both.

@smoya title is a human friendly readable value, but name is machine friendly, so title is used usually for documentation generation and name for code generation.
As for the message fields, I would leave the messageId and remove the name because they currently serve the same purpose and the messageId has the + that it must be unique in the document.

I would completely remove it instead of deprecating it. We already use keys as ids in v3.0.0.

@fmvilas

I would completely remove it instead of deprecating it. We already use keys as ids in v3.0.0.

And it's not true 😄 Why? For operation of course, because we can define operations in one place, new operations section, but messages you can define in each channel, so it means that id for given message can be different - if is used in multiple channels, and I think that people can reuse given message in few topics/events. So I will left messageId.

Sounds reasonable. Can we then just remove name and rename messageId to id? The "message" part is redundant IMHO.

I think this wasn't include (for some reason) in https://github.com/asyncapi/spec/issues/691. Considering the freeze we set up, I wonder if we shall discard it for 3.0 and rather be a candidate for 4.0.


fix(svg): svg shadow to solve apache/echarts#12614

apache/echarts#12614 reports an SVG rendering bug when all line series data have the same value and no line was drawn if has shadow.

It seems it has some issue with branches. Close this an open a new PR later.


Rule 144 contains questionable advice

Rule 144: Should: Only Use UUIDs If Necessary currently lists the following as a negative aspect:

not ordered along their creation history and no indication of used id volume

I'd argue that this can and has been a downside for us in the past. Having a sequence that increases monotonically without gaps is not desirable in most cases, since it allows someone from the outside to regularly measure velocity and derive some insights that wouldn't otherwise be possible.

@whiskeysierra this is surely a considerable aspect that public exposed IDs, that are able to transport information about our business success, should be designed carefully with respect to such considerations. A random value (e.g. a UUID) can be a solution here beside others.
As these public exposed IDs are an exception, I would still argue, that our should rule as well as the argumentation is reasonable. Especially, the ordering along the creation history is an often favorable behavior in company internal APIs.

As these public exposed IDs are an exception

Doesn't that imply that we always need to translate IDs of this kind to some external format and back?


make: *** [run-example] Error 1

error log

python -W default::Warning examples/chat.py
Traceback (most recent call last):
File "examples/chat.py", line 80, in
main(*sys.argv[1:])
TypeError: main() missing 1 required positional argument: 'args'
make: *** [run-example] Error 1

What is this? No comment just close issue
Sent from Mail for Windows 10
From: Manish Goregaokar
Sent: Saturday, March 30, 2019 12:50 PM
To: Manishearth/ChatExchange
Cc: Rai Talha Rehman; Author
Subject: Re: [Manishearth/ChatExchange] make: *** [run-example] Error 1 (#154)
Closed #154 via 0c1e328.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@raitalharehman If you noticed carefully enough, https://github.com/Manishearth/ChatExchange/commit/0c1e328914b02a90e525d4aa4fdbf106ce16faf9 fixed this issue; Github shows the same:

Manishearth closed this in 0c1e328 8 hours ago

@fortunate-man thanks


Problems with text bounding boxes in symbols and spec export

I noticed in a recent spec export that bounding boxes of text that is within a symbol is being drawn incorrectly. The size dimensions appear to be correct in the right side data panel, but hovering over the box shows a different story. This results in incorrect spacing between the other elements around the text block.
The only way that I've found to eliminate this is to detach everything from symbols prior to export, but that defeats the purpose of the symbol. Any ideas on how to fix this?

Can you give me some screenshot?

I just stumbled upon the same problem. You can't "measure" inside of a symbol, which is too bad because combined symbols make a very efficient workflow.
Simply put, I made a Text Input box as a symbol with a couple of elements inside of it. You can only measure the bounding box of the whole symbol, the child elements are no longer recognised.


[fastlane] Version bump

This release adds plugin support to fastlane, you can find more information on how to get started at Plugins.md

LGTM :) So excited for this !

:gem: :sparkles:

It's getting serious 👍


fix: Link icon example missing isExternal prop (fix #742)

Closes #742
📝 Description
https://nextui.org/docs/components/link#external-link miss isExternal prop.
⛳ Current behavior (updates)

🚀 New behavior

💣 Is this a breaking change (Yes/No):

No
📝 Additional Information
Link uses isExternal prop just to control whether to show LinkIcon. The literal meaning of isExternal is a bit obscure. Maybe naming it icon is better? When icon is set true, show default internal LinkIcon; When icon is set other icon component, then just show it. @jrgarciadev

whats the deal with the icon prop here? it just puts Warning: Received 'true' for a non-boolean attribute 'icon'. in the console

whats the deal with the icon prop here? it just puts Warning: Received 'true' for a non-boolean attribute 'icon'. in the console

For now, icon prop is useless, see https://nextui.org/docs/components/link#link-props，and Link will pass it directly into the a tag which causes the warning output. I'll remove it from the example.


RestClient.delete throw ShopifyErrors.HttpRequestError with status 200

Issue summary
When I make a request using RestClient.delete({path: "recurring_application_charges/{id}"}), the error is caught in the try-catch clause, even though the status code is a 200 response.
error HttpRequestError: Failed to make Shopify HTTP request: FetchError: invalid json response body at https://{shop}.myshopify.com/admin/api/2021-10/recurring_application_charges/{id}.json reason: Unexpected end of JSON input

This is because the delete endpoint is returning only the status code and executing await response.json() inside the fetch.
https://github.com/Shopify/shopify-node-api/blob/main/src/clients/http_client/http_client.ts#L184
To avoid throwing an error even if request.body is null, why don't you modify the code as follows?
const body = await response.json().catch(() => {});

Expected behavior
Status 200 without ShopifyErrors.HttpRequestError
Actual behavior
Status 200 with ShopifyErrors.HttpRequestError.

I'm seeing this as well. Sometimes it's because we're trying to fetch something for a theme that's been deleted on the given shop.
Kind've frustrating that there's no info given on the error w/r/t to the response to introspect status code or some other way to handle this gracefully

@kazukinagata  we have updated the library to v6 a couple of month ago. Could you try to update to new version and let me know if this is still an issue? As you can see here we are handling the response deserialization a bit differently now and I believe you should not have the issue anymore.

The original issue was fixed in June 2022 and released as part of 3.1.2 on June 7 ... the code has been carried forward through all releases to v5.3.0.
In v6, due to the underlying isomorphic changes, the code is different but the JSON.parse is still within a try {} catch {} block to prevent the error.


update fwlink

update fwlink so existing one with shipped PSGet is for 5.1

Update-Help doesn't work with HTTPS HelpInfoUri


⚠ Bofrost.de has degraded performance

In 0460d74, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 2564 ms

Resolved: Bofrost.de performance has improved in 70e0967 after 1 hour, 22 minutes.


Update CodeSnippet to allow reference to

The pre tags inside of CodeSnippet contain the content that a user would expect to see copied when they click the copy button. As of now there is no direct way to reference this node element while setting up a copy function.

Apologies, this issue got lost under more recent issues. Will mark this as a bug

Hi there! 👋
Thanks so much for reporting this issue. I went ahead and opened up a PR #273 for this, let me know if it doesn't address your needs or doesn't match the behavior you expect!


How can I validate a code with builder.Prompts in Nodejs

Hi folks,
I would like to validate a code in a waterfall dialog but I cannot see examples about this. The idea is the user recieves a code and he has to validate with the bot that the code he entered is the right one (maybe two retries would be useful). I'm implementing a second factor authentication so the bot cannot share the code with the user in order to demostrate that he has real access to the operation.
Any ideas?
thanks!

here is a solution;
https://github.com/Microsoft/BotBuilder-Samples/tree/86ebba09bfe5ccfdbbd66eaf9c7d19fa9bb239d1/Node/demo-ContosoFlowers/bot

Hi @0GiS0, did the sample above help you out?

Closing for now. Let us know if that sample did not work!


reduce() is deprecated in Python3

According to Python3's "whats new" page, reduce() is deprecated, and one should either use a for loop, or if absolutely necessary, functools.reduce().  As it is, this is broken on 3.
It's used here:
git_lint/reporters.py#L35
The actual error:
Traceback (most recent call last):
  File "/usr/bin/git-lint", line 9, in <module>
    load_entry_point('git-linter==0.0.6', 'console_scripts', 'git-lint')()
  File "/usr/lib/python3.5/site-packages/git_lint/__main__.py", line 57, in main options)
  File "/usr/lib/python3.5/site-packages/git_lint/reporters.py", line 36, in print_report
    messages = reduce(operator.add, [item[3] for item in group[1]], [])
NameError: name 'reduce' is not defined

Thank you.  Found and fixed.

Awesome!

Pushed to pypi, fixed in 0.0.7.


Course list (aka search page) drop every metas

Bug Report
Expected behavior/code
A clear and concise description of what you expected to happen (or code).
The meta tags from the "base.html" template should be always present on every pages.
Actual Behavior
The meta tags from the "base.html" are not present on the Course list page.
This is because the "search.html" template override the whole "meta" block:
https://github.com/openfun/richie/blob/master/src/richie/apps/search/templates/search/search.html
Steps to Reproduce

Go to https://demo.richie.education/
Look for the site favicon in your browser tab, you should see the red book icon. Or more precisely you can watch in page HTML source code to see there is a lot of meta tags.
Open https://demo.richie.education/fr/cours/ in a new tab, the favicon is not present anymore and more precisely in the page HTML source code you can see almost every meta tags are absent.

Environment

Richie version: 2.0.0-beta.6
Platform: Linux

Possible Solution
Use the {{ block.super }} in the "meta" block (preferably at the beginning) and the initial content from "base.html" will be here again.

The PR https://github.com/openfun/richie/pull/1457 fixes this issue.


Request throttling

I have the need to upload many (thousands) small files to OneDrive, to various folders. I also need to achieve high throughput/bandwidth.
Since the LiveSDK API is all asynchronous, I was hoping that I could get reasonable performance by executing dozens of requests (upload/create folder) at the same time, and adding more as soon as some finish.
However, it seems that the server is throttling the clients a lot. It seems to add all the requests into a single sequential queue and respond to the requests at a rate of about 1 response per second (not counting the time it takes to actually upload the files). For example, if I want to create 20 folders, I execute 20 LiveConnectClient.PostAsync at once and then await all the Tasks, but I have to wait for about 20 seconds because the requests become sequential at the server.
What also happens is that some of my asynchronous operations begin to time out, since the server does not respond in timely fashion (since the queue is too large). Furthermore, I start getting LiveConnectException stating that:

ErrorCode: request_throttled
Message: The request wasn't made because the same type of request was repeated too many times. Wait X seconds and try again.

The server increases X if I do not actually wait at least X. Now, since all my requests are asynchronous, when I am told to wait X, some other request is just hitting the server and increasing the X at the server to Y (Y > X). So after waiting X, the server tells me to wait Z (Z > Y; because I did not wait Y), and the cycle repeats over and over again, basically having the client wait indefinitely. I guess this could be solved by having some layer built on top of LiveSDK that would handle the request_throttled exceptions on all requests and keeping track of what the actual wait time should be, but the error text says that:

because the same type of request was repeated too many times

So I would like to ask, what does qualify as the "same type of request"?  How coarse-grained is this criterion?
I understand why these "wait" mechanisms are in place, but it does make the development significantly more complicated. So I would like to ask, what is the recommended solution for this issue? How to achieve high throughput when I need to upload thousands of small files? How to keep the server happy so it does not to mark my client as rogue/DDoS?
And finally, it would be REALLY good if the SDK supported something like "request coalescing". I would like to bundle uploading of dozens of files into a single request. It could easily work by specifying all the uploaded files in the request header, along with an "offset" and "length" of the file contents in the request data stream. And the request data stream would just contain concatenated file contents of all the files to upload. This would bring the number of requests to minimum, and also achieve very high bandwidth.

Issues described in this post do not relate in any way to my previous issue Server is always offline when moving non-existent file. They are completely separate instances.

This is a no trivial problem for us on the OneDrive team.  With the creation of the Live Connect APIs there were certain design goals that shaped our client usage patterns especially around scalability, which is why there are limits like you are seeing when your requests are throttled.  While adding features in the SDK to help support high-performance scenarios could help ease the burden on developers, it wouldn't change the constraints that are limiting requests to the service.
We have been working diligently to free developers from these limitations with the OneDrive API.  It takes something to grok and then transition to other technologies and I appreciate this is not trival.  We are taking this route to create the future of the OneDrive service that will have full parity with everything the OneDrive sync client does, as well as the website available to you as well since everything will use a uniform API.
With all that said you had some specific questions that I don't want to leave you hanging on, the OneDrive apis that LiveConnect exposes are throttled into 2 buckets, read-only operations  (GETs)
and write operations (POST, PUT, etc).  The bucket size for reads is much larger than writes and so if you want to make sure that you aren't wasting cycles while performing write operations against the service, use two separate requests queues for reads and writes and you should be better able to detect where delays should be applied.

Thank you so much for your response. So if I understand you correctly, Live SDK is kinda "legacy" / "for compatibility" and the OneDrive API is the place to go for new projects? I have been looking into the OneDrive SDK, but that project seems to be in very early stage of development, with virtually zero (human) comments, and randomly commented-out code. Live SDK on the other hand looks much more mature so I am a bit confused.
I realize that the suggested request coalescing feature would definitely not change any constraints to the service (which wasn't it's goal anyway), but it would work around them in such a way that these constraints would no longer be a limit for many more benign applications.
The request throttling into 2 buckets (read; write) apply to the OneDrive API as well? Or is that limited to the Live Connect API?
Furthermore, could you please help me to make sense of how the throttling actually works? As per OP, I have dozens of outstanding requests at the server, which processes them one at a time. At some point, it starts throttling the requests in its queue, so all the subsequent requests invoke some kind of incremental throttling - which however seems to behave very strangely.  So as you can see, the server is punishing my client, increasing the wait time as it finally begins to deal with the backlog of requests in it's queue (at which point my client has no way of actually stopping this incremental punishment). But then suddenly the punishment seems to randomly start floating around "20 seconds", then jump up again and drop yet again... My client stops sending any requests as soon as it sees the first throttling response, so all these throttling responses are received as the server deals with the backlog queue. How am I supposed to react to his? Should I take average of all the wait times? Or the longest one? I am not sure what the server expects...

RE: OneDrive API - the project you linked to is sample code to show an example of how to use the API. We have not yet delivered an SDK project that works with OneDrive API and are working on that. Live SDK is a more mature product in that it's existed for years, where OneDrive API has just launched in February, but it is where all of our team's attention is focused right now.

Always wait the max time that you've seen from the service. There is some variability depending on which one of our many servers you see for any given request and the refresh state of the throttle information (hence the slightly confusing times).
The OneDrive API limits are an order of magnitude higher than the LiveConnect APIs.  An application that flirts with these limits on LiveConnect will not ever encounter them on OneDrive API.

Thank you guys so much, it seems OneDrive API is the way to go for my particular project.
Since the Live Connect API throttles requests into 2 buckets (read; write), is the same throttling algorithm used in the OneDrive API backend as well? I understand that OneDrive API does have much more generous limits, but it's better to be ready. :-)

With the OneDrive API I would advise you manage all of your requests to the service through a single system that can detect the throttling requirements and keep all of your requests backed off until after the cool off period has expired.
The internal system that OneDrive uses to manage throttling will change over time so trying to design for its specific design right now would be less than ideal when changes are introduced.


Add page "Useful links" to the wiki

Add page "Useful links" to the wiki.
Here we can document links to useful content related to the project

Page added
6 links inserted


External console/Globals explorer: add Workspace-like options "import" and "save"

From pierre.raybaut on 2010-01-06T05:54:16Z
Everything is in the title...
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=132

From pierre.raybaut on 2010-06-10T13:24:05Z
Status: Fixed

From pierre.raybaut on 2010-04-21T01:00:39Z
Labels: Milestone-Release1.2


13.22 update

Please update to 13.22, I'm not good at compiling or changing the offsets by myself. I'd appreciate if you, @hotline1337, could release the update for 13.22. Thanks in advance.

Yup it's working fine. Thanks!


chore: remove v1alpha5 metrics and counter

Fixes #N/A
Description
This is first of changes to remove v1alpha5 APIs from the codebase.
This removes the metrics and counter controllers for Provisioners and Machines
How was this change tested?
make presubmit
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
6 unchanged lines in 3 files lost coverage.
Overall coverage increased (+0.02%) to 82.506%

Files with Coverage Reduction
New Missed Lines
%

pkg/controllers/provisioning/scheduling/topology.go
2
87.17%

pkg/controllers/provisioning/scheduling/topologygroup.go
2
96.75%

pkg/test/cachesyncingclient.go
2
80.21%

Totals

Change from base Build<PHONE_NUMBER>:
0.02%

Covered Lines:
9192

Relevant Lines:
11141

💛  - Coveralls


Add DSA digests, and round out _fp API

Block of related commits adding new convenience functions:

i2d_DSAPublicKey_fp() and d2i_DSAPublicKey_fp() adding *_fp() methods to complement the existing homologues;
DSA_public_digest() and DSA_private_digest(), to hash public or private keys;

Tests are provided for all of these except the first which is trivial.
Note that the DSA_public_digest() has a workaround for issue #6445.

CLA has been signed, scanned, and email today... awaiting processing.

close/open to kick the cla bot.

We are well into feature-freeze for 1.1.1 now. Do these new functions make up for things that used to be possible, but were broken because we made structures opaque?  If so, can you point to code/apps that used them?  If not, then these new API's would have to wait for the next release after 1.1.1

No, they are new functionality. How should I version them?
And how to deal with DSAPublicKey arguably being the wrong format?

Don't worry about versioning, it will be fixed up when this is merged (after 1.1.1)  As for the format read/written by DSAPublicKey we can't change it or else we break interop.  Do the i2d/d2i publickey functions do the right thing?

And how to deal with DSAPublicKey arguably being the wrong format?

It isn't. It just predates the RFC format. It's unfortunate that the RFC then ended up using the same name we already had for something else. But we do support the SPKI format for DSA - just use DSA_PUBKEY instead.

Is it possible to do those things with the EVP layer? If not, would it make sense to add them to the EVP layer?

But we do support the SPKI format for DSA - just use DSA_PUBKEY instead.

But that's not the format I need either.  I just need the ASN.1 INTEGER representation of .DSA.pub_key.  Does it make sense to add another typedef that handles this with the associated marshaling and bio/fp adornment, etc?

Do the i2d/d2i publickey functions do the right thing?

Well, that's a partisan question, or at least a nuanced one.
I guess it depends on what you believe the right thing to be for the format of the public key... there's the public key itself (which is what I need), there's the SubjectPublicKeyInfo (per RFC-5912), and there's the DSAPublicKey format which duplicates the DSAParams and doesn't seem to be defined in any RFC at all (or ITU document, that I can tell, but without a subscription to the service I have limited search capabilities).

Moving the RSA digest to a separate PR since there seems to be more consensus on what canonical key format is for RSA.

Does it make sense to add another typedef that handles this with the associated marshaling and bio/fp adornment, etc?

Since we're just talking about a plain ASN1 Integer here it doesn't seem worthwhile since we already have i2d_ASN1_INTEGER(). I don't see much point in improving the DSA API since we shouldn't be encouraging its use anyway and there should be few new applications using it.

What's the use case here? If you're hashing just the INTEGER representation of the public key, you aren't including any of the parameters, which are an important part of what key you've got. So if you're using this as some kind of key fingerprint, you aren't capturing all the context. (And, of course, you also aren't capturing the type of key in either of these.)
If whatever you're doing with these includes separately considering these hashes in the context of DSA + specific DSA parameters, then this is plausible. But if you have somewhere pre-configured that a hash of a DSA public key, via this scheme, and are trying to authenticate someone by it, unless your application has already separately authenticated or hardcoded the fact that the key is DSA and a particular set of DSA parameters, this isn't secure.
This sort of thing is why HPKP hashes the entire SubjectPublicKeyInfo and not just the subjectPublicKey value inside it.

This is adding API calls to deprecated DSA API so it is not really relevant for 3.0 and on.
Closing.

This is adding API calls to deprecated DSA API so it is not really relevant for 3.0 and on.
Closing.


background: fix loading background along with scene

Background should be of higher priority than scene. So the presents
of Scene should not prevent Background from taking effect.

I'm not 100% sure about this. The original scene variable check might be doing something essential. But it did fix the problem for me.


New maintainer wanted

Hi @marco-brandizi,
would you be up to take over this project as a new maintainer? I'm not really interested anymore, because

I haven't worked with Neo4J for ages
I would nowadays solve the problem using Docker with Testcontainers
You are the only recent contributor to the project

I don't want to become a bottle neck in your development.
Best regards,
André

Hi @harti2006,
sorry for my late reply, this issue slipped through my messed-up inbox...
While you aren't my bottleneck (I use the fork when I have changes that haven't reached the main repo yet), I would be fine with taking over with managing the main repo.
At least, I can maintain this good plugin until I move to something like Testcontainers too, which is something I'm considering (I'm undecided, cause that approach is more lightweight and more general, but it introduces Docker as pre-requirement, I've always liked the idea of making people able to quickly do clone/mvn/run!).
I've sent you a linkedIn invitation, together with contact details.
Thanks! Marco.

Awesome, let's continue discussion in the LinkedIn chat...


Test for irregular and invalid regexp character ranges

I think, "irregular" character ranges like in
var a = /[+--]/;
var b = /[--z]/;
var c = /[(-.]/

or invalid ones like in
var a = /[z-a]/;
var b = /[\xCC-b]/;

should be tested by jshint.

No,
I fixed the regex parser so it's valid to use [a-] and [-a].


Update README.md

Updated readme to address https://github.com/3DGenomes/ngx-resizable/issues/11

Many thanks Stephen!


Specify the mypy plugin by path instead of module

This will make it so that mypy edb works, instead of needing to do
python3 -m mypy edb.

(Oh, it looks like the current version will work when edgedb is installed in the current venv. I still want to make this change, though, so it doesn't need to be installed, and so we run the same version of the plugin either way we run mypy)


Warisha

Overview 🚀
Give the brief about your changes
How Has This Been Tested? 🚨
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

Manual

Screenshots 📸
Checklist ✅

[ ] My code follows the style guidelines of this project

[ ] I have performed a self-review of my own code

[ ] 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

[ ] Any dependent changes have been merged & published in downstream modules

Amazing
Appreciates your contribution
@Warisha32


Refactor/consolidate tabset styling, use shiny-mode-tabset more generally

The main purpose of this PR is to allow .shiny-mode-tabset to be used more generally throughout the site (and look better without hacks on https://shiny.posit.co/py/docs/ui-overview.html)
While I was there, I discovered we have a lot of overlapping tabset styling logic, scattered in 3 different places. This PR removes that redundancy and also leans on .nav-underline to provide (most of) the underline styling.

@gregswinehart merging this for now since this has some important fixes, but feel free to send me your CSS tweaks for the tabsets!


Allow typing vector arguments on command callables

Without this PR, you'll get an error if you try to use a callable that types its vector arguments, for example:
func spawn_entity(p_entity_name: String, p_position: Vector2i) -> void:
    pass

However, with this PR, there won't be an error and it'll work correctly!

Oh my, I had no idea vector args were broken :sweat_smile:
Thanks for the fix! :+1:


New Lint quick-fixes: REMOVE_TYPE - 3 different lints

This quick-fix just remove a type, it is useful to 3 lints by now, they are:
From [Linter] (http://dart-lang.github.io/linter/lints/avoid_return_types_on_setters.html)
From [Linter] (https://github.com/dart-lang/linter/pull/545)
From [Linter] (https://github.com/dart-lang/linter/pull/551)

@bwilkerson now this is ready to review, I made some fixes, PTAL

@bwilkerson yes, that was I referred to

Apparently all travis builds are failing, should we wait or merge? @bwilkerson

As far as I can see, one test failed with a timeout:
Chrome 60.0.3080 (Linux 0.0.0)  lib/html/queryall_test FAILED
	Error: timeout of 10000ms exceeded. Ensure the done() callback is being called in this test.
	    at finish (test/browser/language_tests.js:829:11)
	    at Context.<anonymous> (test/browser/language_tests.js:862:13)
Chrome 60.0.3080 (Linux 0.0.0): Executed 2237 of 2537 (1 FAILED) (0 secs / 1 min 5.22 secs)

I'd ignore it because I'm fairly sure this change didn't cause it.


The "phpiredis" extension is required by this connection backend.

Hi,
I'm trying to make redis cluster using this code:
$client = new Predis\Client($multiple_servers, [     'cluster' => 'redis',     'connections' => [         'tcp'  => 'Predis\Connection\PhpiredisStreamConnection' ]]);
I tried to install it from https://github.com/nrk/phpiredis but the same problem shows up.
Any help.

The client is configured correctly but check from the output of phpinfo() that phpiredis is indeed loaded by PHP at runtime, the only possible explanation is that you compiled phpredis but didn't configure PHP to load the extension.


Text Classification

Goal(s)

Assign a sentence or document an appropriate category

Input(s)

Sentence or document

Output(s)

Category

Objective Function(s)

TBD

See tasks/natural-language-processing/text-classification


Motion benchmark

Adds Macrobenchark tests.
UI code to be measured is in macrobenchmark-app. See MotionLayoutBenchmarkActivity.
Test code to run the benchmark is in the submodule macrobenchmark-app.benchmark. See MotionLayoutMacrobenchmark.
Also fixed a minor issue with MotionLayout.

Here are examples of the UI benchmarked for this PR
NewMessage
benchmarkMessage.webm
CollapsibleToolbar
benchmarkToolbar.webm


Document the multi-value syntax for my-cnf

Hi,
many thanks for this useful action!
Unfortunately I'm not able to guess the correct syntax for my-cnf: values.
The source code doesn't help me either, that's simply not my programming language. :wink:
What I got working:
my-cnf: 'datadir=/dev/shm/mysql'

How to get in tmpdir=/dev/shm/mysql_tmp? I tried all sorts of white space, escaped newlines, ...
No clue.

my-cnf have same syntax with my.cnf files.
my-cnf: |
  datadir=/dev/shm/mysql
  tmpdir=/dev/shm/mysql_tmp

my-cnf: |

Now I feel really silly...
An example in the README might save the next person struggling with it some time.


Orquesta workflow gets stuck in running state

SUMMARY
Orquesta workflow gets stuck in running state, and with-items works incorrectly (at least it's different from mistral and not documented that it's this way by design). In mistral, task with with-items does not transition to another task until all items are processed, regardless whether they fail or not in the middle of the loop. In orquesta, if task with the first item fails, it immediately starts the task that's defined under failed() condition. If all items succeed, orquesta works exactly as mistral by processing all items first, then transitioning to the next task. I think this is a bug, which in its turn leads to the workflow never reaching final state and gets stuck in running state.
STACKSTORM VERSION
Paste the output of st2 --version:
st2 3.2.0, on Python 2.7.5

OS, environment, install method
Post what OS you are running this on, along with any other relevant information/

CentOS 7, installed using documentation https://docs.stackstorm.com/install/rhel7.html

Steps to reproduce the problem
Meta:
---
pack: "playground"
name: "wf_orquesta_stuck3"
description: "Orquesta workflow gets stuck in running bug, st2 v3.2.0"
runner_type: orquesta
enabled: true
entry_point: "workflows/wf_orquesta_stuck3.yaml"

Workflow:
---
version: '1.0'

tasks:
  init_task:
    action: core.noop
    next:
      - when: <% succeeded() %>
        do:
          - task_1
          - task_2
  task_1:
    with:
      items: i in <% ["1", "2"] %>
      concurrency: 1
    action: core.local
    input:
      cmd: "exit <% item(i) %>"
    next:
      - when: <% succeeded() or failed() %>
        do:
          - run_check_1

  task_2:
    with:
      items: i in <% ["0", "0"] %>
      concurrency: 1
    action: core.local
    input:
      cmd: "exit <% item(i) %>"
    next:
      - when: <% succeeded() or failed() %>
        do:
          - run_check_2

  run_check_1:
    with:
      items: i in <% ["0", "0"] %>
      concurrency: 1
    action: core.local
    input:
      cmd: "exit <% item(i) %>"
    next:
      - when: <% succeeded() %>
        do:
          - all_good
      - when: <% failed() %>
        do:
          - check_failed

  run_check_2:
    with:
      items: i in <% ["0", "0"] %>
      concurrency: 1
    action: core.local
    input:
      cmd: "exit <% item(i) %>"
    next:
      - when: <% succeeded() %>
        do:
          - all_good
      - when: <% failed() %>
        do:
          - check_failed

  all_good:
    join: all
    action: core.noop

  check_failed:
    action: core.noop
    next:
      - do:
          - fail

Expected Results
Two task_1 executed and fail, then two run_check_1 executed and finally complete the workflow and not get stuck.
Actual Results

So as can be seen here, right after task_1 failed, orquesta engine started run_check_1 task without waiting for another item in the list to be processed. But in case of task_2 it did wait for both of the items to be processed before transitioning to run_check_2, which is what expected in both cases. And this workflow never completes.

The provided workflow is a very simplified version of what I have here working fine with mistral but struggling to find a workaround in orquesta after conversion so far :(

The workflow can be simplified to:
---
version: '1.0'

tasks:
  init_task:
    action: core.noop
    next:
      - when: <% succeeded() %>
        do:
          - task_1

  task_1:
    with:
      items: i in <% ["1", "1"] %>
      concurrency: 1
    action: core.local
    input:
      cmd: "exit <% item(i) %>"
    next:
      - when: <% succeeded() or failed() %>
        do:
          - run_check_1

  run_check_1:
    action: core.local
    input:
      cmd: "exit 0"
    next:
      - when: <% succeeded() %>
        do:
          - all_good
      - when: <% failed() %>
        do:
          - check_failed

  all_good:
    action: core.noop

  check_failed:
    action: core.noop
    next:
      - do:
          - fail

Ok, I dug a bit into the sources of orquesta, and found a couple of things:
First:
https://github.com/StackStorm/orquesta/blob/master/orquesta/machines.py#L305:
        events.ACTION_FAILED_TASK_DORMANT_ITEMS_INCOMPLETE: statuses.FAILED,

Changed it to:
        events.ACTION_FAILED_TASK_DORMANT_ITEMS_INCOMPLETE: statuses.RUNNING,

and also added (probably not necessary, because in my case the one above was causing this issue, but I added it just in case, to complete the herd, so to speak):
        events.ACTION_FAILED_TASK_ACTIVE_ITEMS_INCOMPLETE: statuses.RUNNING,

That restored the logic of "process all items first, then transition to next task" based on the condition defined in when.
Second - and this one is a bit more complicated:
https://github.com/StackStorm/orquesta/blob/master/orquesta/conducting.py#L912-L915
            # Remove task from staging if exists but keep entry
            # if task has items and failed for manual rerun.
            if not (task_spec.has_items() and new_task_status in statuses.ABENDED_STATUSES):
                self.workflow_state.remove_staged_task(task_id, route)

This condition doesn't remove staged task when a task with with-items fails after processing all items leading to workflow getting stuck in the running state. When I remove the condition and remove staged task every time, this bug gets fixed, however, I don't know consequences for "manual rerun" mentioned there in the comments.
@m4dcoder could you suggest a better fix than removing the condition?

By the way, this also fixes https://github.com/StackStorm/st2/issues/4968

Possibly related - https://github.com/StackStorm/orquesta/issues/212


Change From<&'a [u8]> to an explicit function

Most of the From conversions to Bytes are shallow copies, just grabbing a pointer and pulling it in. There is also the from_static function to save copying a static set of bytes. However, the From<&'a [u8]> impl will copy the slice into a new buffer (either inline or a new heap allocation, depending on size).
Unfortunately, that &'a [u8] means it applies to &'static [u8] as well. In cases where one is generic over Into<Bytes>, a user can easily and accidentally cause copies of static slices, instead of remembering to call Bytes::from_static. This issue proposes to change the defaults, so that the faster way is easier.

Remove From<&'a [u8]> for Bytes/BytesMut.
Add From<&'static [u8]> for Bytes/BytesMut.
Add a new constructor that can take &'a [u8], that explicitly shows a copy will happen.

The name of this new method could be a few things, these just some examples that occurred to me:

Bytes::copy(slice)
Bytes::copy_from(slice)

Oh, this would be a breaking change, so would require (block?) 0.5.

Just to clarify,
From<&'a [u8]> for BytesMut can stay because static slices are not mutable, so a copy has to happen from the  'static  slice when creating BytesMut.
So only Bytes would have its From<&'a [u8]> removed.

Mentioned by @arthurprs:

While I understand the reasoning this severely limits Byte as a Vec replacement, like backing a https://crates.io/crates/string

Specifically, this issue: https://github.com/carllerche/string/issues/6


Documentation needed

Can you please add the sample's link into the documentation as well as a link to the sample code? I believe it will be time saving for many others! Btw, thanks for the great work!

There's a link in the description of this repository.


Fullfill feature requests & Publish in CI

Closes #107
Closes #111
Closes #114
Closes #115
I also added a "Publish" step in the Github Actions CI but I don't think that will auto-bump the version number. So it would require a commit with a manual version number bump and then tagging that commit as a release. It would also require setting up a secret. I closes stuck to this guide which also links to creating the secret. Not sure if this is feasible to use for simpler deploy of the extension or not, but you be the judge of that  :)

Check out https://github.com/stevensona/shader-toy/actions/runs/314509974
It appears to be skipping the publish step, even with the release created. Feel free to play around. The PAT should be in place now, but nothing sticking out at me as to what is preventing publish step from running.
Going to go ahead and attempt a manual release.

I screwed up back in July when I bumped the version to release the attribution fix but forgot to push the changes back up here. So I released your changes as 0.10.13. Apologies for that.

I looked a bit closer into it and I think the issue is with having Publish in the same workflow as the tests. I'll try separating the Publish step into its own workflow, just need to figure out inter-workflow dependencies. But there's no urgency with this I would think  :)


how to AUTOMATICALLY save all articles to files, and quit?

newsboat 2.21.0:
I already posted this one week ago on the google group , but seeing no answer, I'm trying here now:
Greetings,
I just started using newsboat and it's great, but there must be something basic that I don't understand, or recognize, in the documentation. I would like to run newsboat from a bash script, so that it:

downloads ONE feed
downloads all the articles in that feed
saves each of those articles in a separate, plain text file that I can parse later
quits

Is this possible? If yes, how? As I said, I have already read the documentation and tried several combinations of options, but they are either invalid, or not doing what I need, so I must miss something (again, assuming what I want to do is possible to begin with, which I am not sure of)
thanks,
Marcoo

Hi Marcoo,
Newsboat is designed to be operated by humans, not so much by scripts. Hence, it's probably not possible. Let me suggest to use rsstail or something along those lines instead. Some feed parser library for your favorite programming language should do the trick. To me, Newsboat doesn't sound like the right tool for your job.
However, if you still want to try your luck with Newsboat, have a look at the --execute flag and save-all operation as a start.

It's definitely possible, one idea maybe is you could write a query on the cache sqlite3 database using an external script. Just a starting point to expand your script to dump it to a file:
#!/bin/sh
# dump data, .mode ascii: Columns/rows delimited by 0x1F and 0x1E

sqlite3 ~/.newsboat/cache.db <<!EOF |
.headers off
.mode ascii
.output
SELECT
        i.pubDate, i.title, i.url, i.content, i.content_mime_type,
        i.guid, i.author, i.enclosure_url,
        f.rssurl AS rssurl, f.title AS feedtitle, i.unread
        -- i.id, i.enclosure_type, i.enqueued, i.flags, i.deleted, i.base
FROM rss_feed f
INNER JOIN rss_item i ON i.feedurl = f.rssurl
ORDER BY
        i.feedurl ASC, i.pubDate DESC;
.quit
!EOF
LC_ALL=C awk '
BEGIN {
        FS = "\x1f";
        RS = "\x1e";
}
{
        print $9 ": " $2 " " $3;
}'

Hi @hiltjo , and thanks a lot for the great tip, I'm almost there thanks to it.
As is, your sample code gave me an error because sqlite3 says that there is no column like i.content_mime_type in the database. But if I just remove that column from the query, it runs and produces output lines like:
FEEDNAME: TITLE URL
FEEDNAME: TITLE URL
...
that are just fine for the postprocessing I want to do
so the only missing piece is how to launch newsboat from a shell script so it just starts, reloads ALL the feeds listed in a rsslist.txt file and quits.
I tried this:
newsboat -u rsslist.txt -c temporary-cache.db -r -x quit
but it says "quit: unknown command"
so I am surely missing something obvious here. What?
Again, thanks for pointing me in the right direction!

I tried this:
newsboat -u rsslist.txt -c temporary-cache.db -r -x quit

It would seem that -x reload is the command you are looking for, instead of -r -x quit.
Although, that does not reload just one feed, but all the feeds. Of course you could work around that by having only one feed at a time in the rsslist.txt.

It would seem that -x reload is the command you are looking for, instead of -r -x quit.

YES, this is it, thanks. It loads, fills the sqlite3DB that can later be queried as @hiltjo said, and then quits. Just what I need.
And doing once per feed, with a different 1-line rsslist.txt every time is what I need to do anyway, because it makes easier the postprocessing I want to do.
Again, thanks a lot!

It looks like the the question got fully answered, so I'm closing as resolved.
If there are any other issues, feel free to reopen or open a new issue.


SUP-431: Updated notes section regarding recreation of replication slots

What changed, and why it matters
Since the release of this January blog post about PG logical replication slots recreation upon failover, we should update our documentation "Note" sections to mention that services that have been updated or deployed since January 2023 would have this feature available and doesn't require restarting nodes.
For PostgreSQL services that have not been updated from December 2022 and earlier, service nodes wouldn't have this feature and would still lose their logical replication slots per internal discussion.

Recreation of replication slots
Manage inactive or lagging replication slots

Thank you for submitting this PR, @bcrisologo! Made an editorial check.
@alexole , please confirm this is correct in terms of tech info communicated. Thank you :-)


The video is not working

Challenge build-a-tribute-page has an issue.
User Agent is: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/603.1.30 (KHTML, like Gecko) Version/10.1 Safari/603.1.30.
Please describe how to reproduce this issue, and include links to screenshots if possible.

@KudratP Videos are now deprecated for the updated version of freeCodeCamp and will be removed soon. So, please use the Codepen links provided to see what you have to built and try to include the test file in your submission and check if your project passes the test or not!
Please close the issue, and go for your project :+1:

The videos are going away. See: https://github.com/freeCodeCamp/freeCodeCamp/issues/12753


How work with .net core transactions

It is question.
I have two different contexts. I need accept all changes in one transaction.
I not expert in transactions at all :) A lot of issues about this problem in .net core confuse me even more.
Please explain me. Would this example work as expected?
All items will insert after scope disposed? If something happen in scope all changes will rollback?
class Program
{
    static void Main(string[] args)
    {
        using (var scope = new TransactionScope(TransactionScopeOption.Required, new TransactionOptions { IsolationLevel = IsolationLevel.ReadCommitted }, TransactionScopeAsyncFlowOption.Enabled))
        {
            using (var itemsCntx = new ItemsContext())
            using (var unitsCntx = new UnitsContext())
            {
                itemsCntx.Items.Add(new Item());
                unitsCntx.Units.Add(new Unit());

                itemsCntx.SaveChanges();
                unitsCntx.SaveChanges();
            }

            scope.Complete();
        }

        Console.ReadLine();
    }
}

class Item
{
    public int Id { get; set; }
}

class Unit
{
    public int Id { get; set; }
}

class UnitsContext : DbContext
{
    public DbSet<Unit> Units { get; set; }

    protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)
        => optionsBuilder.UseNpgsql("Host=localhsot;Database=units_db;Username=postgres;Password=1;Pooling=false");
}

class ItemsContext : DbContext
{
    public DbSet<Item> Items { get; set; }

    protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)
        => optionsBuilder.UseNpgsql("Host=localhost;Database=items_db;Username=postgres;Password=1;Pooling=false");
}

net.core 2.2.0
ef core 2.2.0
npgsql provider 2.2.0

It won't work with an unpooled connection because of npgsql/npgsql#2408. Data will be inserted on SaveChanges.
I'm closing this issue, but don't hesitate to continue the discussion.

It is strange! because I try this example without scope.Complete() and with Pooling=false  .I don't see any new data in my tables (Units and Items) after application complete.
May be I missing something?

Today I tryed example in debugger step by step and after savechanges I don't see any new data also.
All data insert after scope disposed. Looks like all work as expected and now I more confused :)

Maybe EF Core closes the underlying connection on data context dispose. This could describe the behavior you see.
@austindrenski Can you confirm this?

@YohDeadfall EF Core indeed closes the DbConnection when a DbContext is disposed (relying on ADO.NET pooling to keep things efficient). In fact, IIRC it even sometimes closes/reopens the connection even within the lifetime of the DbContext.

I have several queastions :)

Need I think about this internals when use TransactionScope? I asked because it looks strange that I need think about pooled connection or not.
This behavior specific ef core or npgsql? Will it works if I change ef core provider (for example to mssql provider).
And what happen when DbConnection closed?
Why it important where and why DbConnection closed?
And how setting Pooling=false may affect to transactions?

@wesfin I haven't yet investigated the issue above. However, as @YohDeadfall wrote above, Npgsql specifically does not currently enlist to ambient transactions (TransactionScope) if pooling is off (turning off pooling is extremely rare in general). Although we will fix this at some point, EF Core may run very slowly if you try to use it without pooling - (or at the very least some external pooling solution).
Aside from that, connection open/close logic has some subtle interactions with TransactionScope. If two connections are enlisted to the same TransactionScope, that triggers an escalation to a distributed transaction (supported only on .NET Framework). However, two consecutive connections do not trigger escalation, as the same physical connection can be reused. Therefore, open/close logic is important in determining whether two connections are open simultaneously under the same TransactionScope.
Apart from that you're not really supposed to know or care about anything else.

Aside from that, connection open/close logic has some subtle interactions with TransactionScope. If two connections are enlisted to the same TransactionScope, that triggers an escalation to a distributed transaction (supported only on .NET Framework). However, two consecutive connections do not trigger escalation, as the same physical connection can be reused. Therefore, open/close logic is important in determining whether two connections are open simultaneously under the same TransactionScope.

If I understand correctly my sample should create distributed transaction because in TransactionScope I create two different DbContext's (UnitsContext, ItemsContext) it is two different physical database. As you say it should not work in .net core application.
And it should not work if it is ambient transaction because poolling is off. Besides it is two different database and connections can't be reused anyway.
So how and why this sample work?

I continue experement with transactions in .net core apps.
If I change my EF provider to mssql (UseSqlServer("")), this sample not work.
That's exactly what said @roji

that triggers an escalation to a distributed transaction (supported only on .NET Framework)

And in second SaveChanges I get exception System.PlatformNotSupportedException.
So why behavior depends on EF provider?

UseSqlServer() - distributed transaction
UseNpgsql() - ???

Then I chek pooling options when use row npgsql.
Ant it is works like @YohDeadfall said

It won't work with an unpooled connection because of npgsql/npgsql#2408.

In this example with Pooling=false data inserted after command.ExecuteNonQuery();
static void Main(string[] args)
{
    using (var itemsConn = new NpgsqlConnection("Host=localhost;Database=items_db;Username=postgres;Password=1;Pooling=false"))
    using (var unitsConn = new NpgsqlConnection("Host=localhost;Database=units_db;Username=postgres;Password=1;Pooling=false"))
    {
        using (var scope = new TransactionScope())
        {
            itemsConn.Open();
            unitsConn.Open();

            using (var command1 = itemsConn.CreateCommand())
            {
                command1.CommandText = "INSERT INTO \"Items\" (\"Id\") VALUES (@p)";
                command1.Parameters.AddWithValue("p", 100);
                command1.ExecuteNonQuery();
            }

            using (var command2 = unitsConn.CreateCommand())
            {
                command2.CommandText = "INSERT INTO \"Units\" (\"Id\") VALUES (@p)";
                command2.Parameters.AddWithValue("p", 100);
                command2.ExecuteNonQuery();
            }

            scope.Complete();
        }
    }

    Console.ReadLine();
}

So why options Pooling affects to npgsql, but not affects to Npgsql.EntityFrameworkCore.PostgreSQL.
All this quations because I need understand can I use different dbcontext's in TransactionScope with option Pooling=false (I can't enabled pooling). And Will it be transactionally? If this scheme may have problems, how I can save data in two different DB transactionally, with Pooling=false?

I think I can attach this issue https://github.com/npgsql/npgsql/issues/1743.


Run libreoffice

Getting libreoffice running...

On AWS, I had to do 3 things:

Changed handler to ds-caselaw-pdf-conversion.lambda_function.handler
Changed RAM to 512MB
Changed timeout to 1 minute

Currently running, but terminating with com::sun::star::container::NoSuchElementException

This is now working using a gzipped rebuild of the brotli layer. I've uploaded it at https://eu-west-2.console.aws.amazon.com/lambda/home?region=eu-west-2#/layers/libreoffice-without-brotli/versions/1?tab=versions. We'll need to copy it over to production at some point

https://github.com/shelfio/libreoffice-lambda-layer/issues/24 is the underlying issue with the gzip layers, which seem to be broken.


Array type in query does not accept a solitary item

In this specification:
  /demo:
    x-swagger-router-controller: demoController
    get:
      parameters:
        - name: filter
          in: query
          required: false
          type: array
          items:
            type: integer
          collectionFormat: multi
      responses:
        "200":
          description: Success
          schema:
            $ref: "#/definitions/DemoResponse"
        default:
          description: Error
          schema:
            $ref: "#/definitions/Error"

I defined an array-type query string parameter, filter. However, during testing it appears that when a single element is passed a validation error is thrown. Example:
http://localhost/demo?filter=10

Throws an INVALID_REQUEST_PARAMETER error: Expected type array but found type integer.
However, adding an additional instance is then accepted:
http://localhost/demo?filter=10&filter=20

Is this the expected behaviour of an array type? This behaviour is the same regardless whether the collectionFormat is csv or multi.

I would say the expected behavior is to accept this as an array with a single element (i.e. [10] in JSON).
So what you have is likely a bug with whatever tooling you are using on your server.
Please open an issue in that tooling's project – this repository is for the specification.

What @ePaul said.

This is a problem with Sway, which you can see here.


Update test matrix

Coverage remained the same at 100.0% when pulling ba20085be923c7f335649ca1a61172dd0d22ab04 on update-test-matrix into 35da2290f6cf9352d12b0371dfc6b2de19f58aa0 on main.


IdentityProviderSSOBinding and buildAuthnRequest

There is a string member IdentityProviderSSOBinding in the SAMLServiceProvider struct, which doesn't seem to be used anywhere.
And in buildAuthnRequest there is no way to set ProtocolBinding to anything other than HTTP-POST. Was the IdentityProviderSSOBinding field expected to be used here?

PR: #70 for fixing this


Tnitter: read the latest tnits on the go with the new Tnitter portable app!

Intro a portable client for Tnitter listing the more recent 16 tnits. It is more of a test and example on using AsyncHttpRequest to do both simple request to a REST server and implement push notifications using an open request. By design, this client does not support posting Tnits, this feature would require much more code and it may be simplified by future services in the lib.
To support the client the server has a few new REST interfaces. One to list the tnits and the other for push notifications.
This PR also fixes a few bugs on the Tnitter server: losing the session on posting and empty post being accepted by the server.

Note for the reviewers: You may be better to read commits individually. There are 2 bigs commits, one extracts the database logic from the model module and the other introduces code generated by Jwrapper for the native layer of that Android ui implementation.

+1

+1

There's the parallel execution bug on test_neo, so the tests are ok.

ok to test

You forgot to gitignore and make clean the res directory
http://gresil.org/jenkins/job/nit_test_tools/896/testReport/cmd/check/clean_workdir/

By the way, you should add the upstream.apk metadatum in the package.ini
eg. https://github.com/nitlang/nit/blob/master/contrib/tinks/package.ini

you MUST also add the res/ directory (or its generated content) to the gitignore file

Ok ok, it should be ok now.


File Clarification

Thanks for providing this file!
From the instructions, it is not clear whether you add the .tar.gz to the card/USB root, extract it, in the folder or not...
Could just be my misunderstanding, if you could clarify.  Thanks!

Hi, thanks for your interest.
Alpine apkovl overlays files are gzip archives, and must be named with .apkovl.tar.gz to that system picks-one up at boot.
They must be located at root of any volume.
Hope this helps.

Super, many thanks for the clarification!


Provide a way to enable Cassandra logging through a Kong environment variable

Summary
As far as I can tell from both the source and the documentation, there is no way to set the logging level of the Cassandra driver.. There should be a way to set the logging level of the Cassandra driver to add visibility and help with debugging issues with Kong's connection to Cassandra.

Nevermind, I see how the silent variable is being used. My bad.
Are the Cassandra driver logs written to the nginx log file? For some reason I'm unable to see them

Hi, make sure that you are using the appropiate log level (quick way to try this is KONG_LOG_LEVEL=debug kong start).


macOS DatePicker in an NSMenu can have low contrast in dark mode

Environment Information

Platform:

[ ] iOS
[x] macOS

Package version(s): 0.4.6, Swift Package Manager
Xcode and OS versions: macOS Monterey 12.2.1, Xcode 13.2.1

Please provide a reproduction of the bug:
Using the macOS DatePicker in an NSMenu or similarly configured visual effect view can result in low contrast text when in dark mode with a light element behind it.

Put your Mac in Dark Mode
Launch the sample app
Launch Word or another text editor with a white background
Position the sample app window over the light background so that the calendar menu will show over the white background

Actual behavior:
Potential for low contrast, this is 1.4:1 ratio for example:
Example in the sample app:

Example in a sample menu bar app:

Expected behavior:
I would expect the control to have reasonable contrast when in an NSMenu, even if it's placed over top something bright like a website or blank document.
Priorities and help requested:
Are you willing to submit a PR to fix? Yes
Requested priority: Normal
Products/applications affected: Anything using the macOS DatePicker in an NSMenu

My proposed solution is to override allowsVibrancy in the CalendarDayButton class so that the OS handles ensuring the content is vibrant and visible over whatever material it's presented on.

If the property is true, the view takes appropriate measures to ensure its content is vibrant on top of any underlying material.

override var allowsVibrancy: Bool {
	return true
}

With the same setup as the bug logs, here's the vibrant example, at a 3.2:1 contrast ratio:

The drawback to this approach is that OS modifies the colors and could could change an explicitly set brand color in the name of higher contrast. Since the DatePicker defaults to the a user-definable accent color, letting the OS handle contrast seems an appropriate approach.
I did prototype an alternative of putting a semi-transparent windowBackgroundColor behind the cutout in the CalendarDayButton but adding extra views to the view hierarchy impacted the performance of rendering the calendar.


OTP version undefined

Unsure if this is from today's changes, but we suddenly get:
Installing Erlang/OTP undefined - built on ubuntu-20.04   /home/runner/work/_actions/erlef/setup-elixir/v1/dist/install-otp.sh ubuntu-20.04 undefined   Error: The process '/home/runner/work/_actions/erlef/setup-elixir/v1/dist/install-otp.sh' failed with exit code 8
We're not having this issue with OTP 24.0.3, but it seems to be a sudden issue with otp-version: <IP_ADDRESS> ?

@paulo-ferraz-oliveira  Would this have anything to do with your recent merge?

@paulo-ferraz-oliveira Would this have anything to do with your recent merge?

I'm not sure. Could you point me to a .yml so I can examine it better?
Are you actually using <IP_ADDRESS> as the input?

Yes, we are actually using that as the input:
      - name: Setup elixir         uses: erlef/setup-elixir@v1         with:           elixir-version: '1.11.0'           otp-version: '<IP_ADDRESS>'

We JUST tried that one too,

Output:
`Installing Erlang/OTP OTP-<IP_ADDRESS> - built on ubuntu-20.04
/home/runner/work/_actions/erlef/setup-elixir/v1/dist/install-otp.sh ubuntu-20.04 OTP-<IP_ADDRESS>
Installed Erlang/OTP version follows
Erlang (SMP,ASYNC_THREADS,HIPE) (BEAM) emulator version <IP_ADDRESS>
Error: Requested Elixir / Erlang/OTP version (v1.11.0-otp-22 / OTP-<IP_ADDRESS>) should not contain '-otp-...'`

Did you try without '-otp-...'? Because that should be inferred from the Erlang version.

The action is semver based, as much as possible, but some versions (like OTP's) are not, which makes us have to choose between offering a "range" -like function or be strict in versions (which is why the option I just mentioned was introduced).
As an example, take '22.3'. Some might want '22.3' exactly, some might want '22.3.1' and some '22.3.1'. We chose "ranges" by default, but it might not suit everyone: we hope it suits the majority, since this was the default behaviour.

I see. Without OTP, going back to 1.11.0 and using strict we get this:

Did you remove the v from the Elixir version?
I'm drafting #57, as a means to potentially solve your issue. This was a hidden bug, as previous behaviour was supposed to be semver -based, but apparently was not (fixing that surfaced your issue).

I have a similar error that started happening this morning. It's slightly different, but feels like it may be related.
Actions output:

Config:
env:
  MIX_ENV: test
  OTP_VERSION_SPEC: "24.0.2"
  ELIXIR_VERSION_SPEC: "1.12.1"

jobs:
  compile:
    name: Compile
    steps:
      - uses: erlef/setup-beam@v1
        id: setup
        with:
          otp-version: ${{ env.OTP_VERSION_SPEC }}
          elixir-version: ${{ env.ELIXIR_VERSION_SPEC }}
          version-type: "strict"

Adding the v back to the elixir version fixed this for us @paulo-ferraz-oliveira , thank you

Adding the v back to the elixir version fixed this for us @paulo-ferraz-oliveira , thank you

You can check the behaviour here: https://github.com/erlef/setup-beam/runs/3021625662?check_suite_focus=true#step:3:3

Hey, @vanvoljg. Your issue does seem similar, but I'll have to test further. You shouldn't need the strict, in your case, though. And if you do use it, you need a v in the Elixir version.

You shouldn't need the strict, in your case, though. And if you do use it, you need a v in the Elixir version.

I wondered if it would be required, but tested just in case. Thanks for the clarification!
If it helps you, I got the exact same error both with and without strict version type.

You shouldn't need the strict, in your case, though. And if you do use it, you need a v in the Elixir version.

I wondered if it would be required, but tested just in case. Thanks for the clarification!
If it helps you, I got the exact same error both with and without strict version type.

Can you add a v and check if that helps? (won't be the best solution, though - I'm working on it)

@paulo-ferraz-oliveira I added it and, unfortunately, it returns the same error.
Also realized I omitted a step in the config I mentioned. I don't know if will matter, but - uses: actions/checkout@v2 is also in there.
env:
  MIX_ENV: test
  OTP_VERSION_SPEC: "24.0.2"
  ELIXIR_VERSION_SPEC: "1.12.1"

jobs:
  compile:
    name: Compile
    steps:
      - uses: actions/checkout@v2
      - uses: erlef/setup-beam@v1
        id: setup
        with:
          otp-version: ${{ env.OTP_VERSION_SPEC }}
          elixir-version: ${{ env.ELIXIR_VERSION_SPEC }}
          version-type: "strict"

@vanvoljg, I'll create a test specific to your issue. In the meantime, you might want to use @v1.7.2, instead of @v1, to keep the behaviour you had before.

A new version will hopefully be out today that'll solve the Elixir versioning issue as well as the strict Erlang versioning.

https://github.com/erlef/setup-beam/releases/tag/v1.8.1 is released. Let us know if you have issues using it.


ng-minlength-valid class is applied even when it should be invalid, when ng-pattern is applied (1.2.x)

Why it matters: I work for a company that validates forms related to Healthcare Information, we do serverside validation - but it makes some data entry person's life easier if we can get the submission correct the first time.
Reproducable: Always
Browsers: Chrome 37, Firefox 32 and IE 11
Operating System: Windows 7
Here's a plunk showing the issue: http://plnkr.co/edit/wrfUGUdjBJcv7pu2zTTY
Steps to reproduce:

Load Plunker
Type in the input and exceed the min length of 2, then delete to empty the input
Inspect element > input > ng-minlength-valid class is applied even though it should be invalid

I'm not sure this is a bug. The minlength validator will pass if it's given nothing OR if the length of what is given is less than the minlength. This is true of master as well. So I believe that your example is behaving as expected.

Regardless, as 1.2.x only receives security fixes, I'm gonna close this.


net: NATs client can't connect to server when client built with go1.7: "dial tcp: no suitable address found"

Please answer these questions before submitting your issue. Thanks!

What version of Go are you using (go version)?

go1.7rc6 from docker hub:
$ docker run -ti golang:1.7 /bin/sh
# go version
go version go1.7rc6 linux/amd64

What operating system and processor architecture are you using (go env)?

Minikube - x86 VirtualBox VM on a Mac
# go env
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/go"
GORACE=""
GOROOT="/usr/local/go"
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build828064041=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1"

What did you do?

Compiled Weave Scope with go1.7 (see https://github.com/weaveworks/scope/pull/1797), ran it on a minikube instance and it couldn't connect to a NATs instance:
$ kubectl logs --namespace=scope query-1106217792-nv4ar
<app> INFO: 2016/08/16 14:04:32.999799 app starting, version 919c3be, ID 357f1fafb9b6ed6f
<app> INFO: 2016/08/16 14:04:33.000030 command line args: --app.collector=dynamodb://abc:123@dynamodb.scope.svc.cluster.local:8000/reports --app.collector.s3=s3://abc:123@scope.svc.cluster.local:4569/s3 --app.http.address=:80 --app.log.http=true --app.memcached.hostname=memcached.scope.svc.cluster.local --app.memcached.service=memcached --app.memcached.timeout=100ms --app.nats=nats://nats.scope.svc.cluster.local:4222 --app.userid.header=X-Scope-OrgID --logtostderr=true --mode=app --weave=false
<app> INFO: 2016/08/16 14:04:33.000514 Connecting nats to nats://nats.scope.svc.cluster.local:4222
2016/08/16 14:04:33 nats err: dial tcp: no suitable address found
<app> FATA: 2016/08/16 14:04:33.000747 Error creating collector: nats: no servers available for connection

The "nats: no servers available for connection" comes form the NATS client, which hides the original error.  the "dial tcp: no suitable address found" is me adding some logging to the client to show the error.

What did you expect to see?

Kubectl exec'ing into a pod on the machine shows NATs is indeed accessible:
$ kubectl exec -ti --namespace=scope pipe-4267260430-ci7f0 /bin/sh
/home/weave # nslookup nats.scope.svc.cluster.local

Name:      nats.scope.svc.cluster.local
Address 1: <IP_ADDRESS>

# telnet nats.scope.svc.cluster.local 4222
INFO {"server_id":"T452ED9wLfSbSr3lPntysO","version":"0.8.0","go":"go1.6.2","host":"<IP_ADDRESS>","port":4222,"auth_required":false,"ssl_required":false,"tls_required":false,"tls_verify":false,"max_payload":1048576}

-ERR 'Unknown Protocol Operation'
-ERR 'Parser Error'
Connection closed by foreign host

#  apk add drill
(1/2) Installing ldns (1.6.17-r3)
(2/2) Installing drill (1.6.17-r3)
Executing busybox-1.24.2-r0.trigger
OK: 25 MiB in 45 packages
/home/weave # drill  nats.scope.svc.cluster.local
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 53508
;; flags: qr aa rd ra ; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;; nats.scope.svc.cluster.local.

I expect it to connect and work, as it does with go1.6

What does running with environment variable GODEBUG=netdns=1 say?

Possibly; although the only change I made was to use a different image (1.7 vs 1.6.2).

What does running with environment variable GODEBUG=netdns=1 say?

Will have a go now.  If this doesn't help, I can try and provide a minimal reproduction tomorrow.

What does running with environment variable GODEBUG=netdns=1 say?

With go1.7rc6:
$ kubectl logs --namespace=scope query-846243711-ptwwy
<app> INFO: 2016/08/16 17:06:25.596993 app starting, version 919c3be, ID 336f06fd3b5d2bf3
<app> INFO: 2016/08/16 17:06:25.597260 command line args: --app.collector=dynamodb://abc:123@dynamodb.scope.svc.cluster.local:8000/reports --app.collector.s3=s3://abc:123@scope.svc.cluster.local:4569/s3 --app.http.address=:80 --app.log.http=true --app.memcached.hostname=memcached.scope.svc.cluster.local --app.memcached.service=memcached --app.memcached.timeout=100ms --app.nats=nats://nats.scope.svc.cluster.local:4222 --app.userid.header=X-Scope-OrgID --logtostderr=true --mode=app --weave=false
go package net: built with netgo build tag; using Go's DNS resolver
<app> INFO: 2016/08/16 17:06:25.597506 Connecting nats to nats://nats.scope.svc.cluster.local:4222
2016/08/16 17:06:25 nats: nats://nats.scope.svc.cluster.local:4222
2016/08/16 17:06:25 foo:  nats.scope.svc.cluster.local:4222
2016/08/16 17:06:25 nats err: dial tcp: no suitable address found
<app> FATA: 2016/08/16 17:06:25.597841 Error creating collector: nats: no servers available for connection

Can you compare that with Go 1.6?
For your Go 1.7 output, I see:
go package net: built with netgo build tag; using Go's DNS resolver

I think the relevant change in Go 1.7 was 72c11808 (net: don't do DNS for onion and local addresses) for #13705.
When @mikioh mentioned RFC 6762, which says:
   This document specifies that the DNS top-level domain ".local." is a
   special domain with special semantics, namely that any fully
   qualified name ending in ".local." is link-local, and names within
   this domain are meaningful only on the link where they originate.
   This is analogous to IPv4 addresses in the 169.254/16 prefix or IPv6
   addresses in the FE80::/10 prefix, which are link-local and
   meaningful only on the link where they originate.

   Any DNS query for a name ending with ".local." MUST be sent to the
   mDNS IPv4 link-local multicast address <IP_ADDRESS> (or its IPv6
   equivalent FF02::FB).  The design rationale for using a fixed
   multicast address instead of selecting from a range of multicast
   addresses using a hash function is discussed in Appendix B.
   Implementers MAY choose to look up such names concurrently via other
   mechanisms (e.g., Unicast DNS) and coalesce the results in some
   fashion.  Implementers choosing to do this should be aware of the
   potential for user confusion when a given name can produce different
   results depending on external network conditions (such as, but not
   limited to, which name lookup mechanism responds faster).

I missed this part:

Implementers MAY choose to look up such names concurrently via other
mechanisms (e.g., Unicast DNS) and coalesce the results in some
fashion.

And currently we're just always skipping DNS for *.local addresses:
// avoidDNS reports whether this is a hostname for which we should not
// use DNS. Currently this includes only .onion and .local names,
// per RFC 7686 and RFC 6762, respectively. See golang.org/issue/13705.
func avoidDNS(name string) bool {
        if name == "" {
                return true
        }
        if name[len(name)-1] == '.' {
                name = name[:len(name)-1]
        }
        return stringsHasSuffixFold(name, ".onion") || stringsHasSuffixFold(name, ".local")
}

We should probably relax the *.local case, at least for the netgo case, but maybe in all cases.
I doubt it's relevant, but what is your /etc/resolv.conf and /etc/nsswitch.conf?
/cc @mikioh @mdempsky @ianlancetaylor for any opinions and whether this is Go 1.7.1 worthy.

I am definitely for relaxing the *.local case. We use DNS for resolving .local domains and this is a blocker for us to go to Go 1.7. We actually have a local DNS server setup specifically for this case, which is local to the machine, and not propagated to upstream DNS servers.

Thanks for looking into this!
Relaxing the .local sounds like a plan, as things like kubedns and weavedns depend heavily on it.

@bradfitz I put together a quick CL to relax the .local case: https://go-review.googlesource.com/#/c/27250/

Sorry just realised there were some more outstanding questions:

Can you compare that with Go 1.6?

$ kubectl logs --namespace=scope query-846243711-d3dhl
<app> INFO: 2016/08/17 09:49:14.140623 app starting, version b3b160c, ID 24bcbcba11b7f7d3
<app> INFO: 2016/08/17 09:49:14.141131 command line args: --app.collector=dynamodb://abc:123@dynamodb.scope.svc.cluster.local:8000/reports --app.collector.s3=s3://abc:123@scope.svc.cluster.local:4569/s3 --app.http.address=:80 --app.log.http=true --app.memcached.hostname=memcached.scope.svc.cluster.local --app.memcached.service=memcached --app.memcached.timeout=100ms --app.nats=nats://nats.scope.svc.cluster.local:4222 --app.userid.header=X-Scope-OrgID --logtostderr=true --mode=app --weave=false
go package net: built with netgo build tag; using Go's DNS resolver
<app> INFO: 2016/08/17 09:49:14.146056 Connecting nats to nats://nats.scope.svc.cluster.local:4222
2016/08/17 09:49:14 nats: nats://nats.scope.svc.cluster.local:4222
2016/08/17 09:49:14 foo:  nats.scope.svc.cluster.local:4222
<app> INFO: 2016/08/17 09:49:14.152539 listening on :80

I doubt it's relevant, but what is your /etc/resolv.conf and /etc/nsswitch.conf?

These jobs are running inside an Alpine container:
/home/weave # cat /etc/resolv.conf
search scope.svc.cluster.local svc.cluster.local cluster.local
nameserver <IP_ADDRESS>
options ndots:5
/home/weave # cat /etc/nsswitch.conf
cat: can't open '/etc/nsswitch.conf': No such file or directory

Can we consider this for 1.7.1?

Alas, but as mentioned in https://tools.ietf.org/html/draft-adpkja-dnsop-special-names-problem, it's better to stay away from the disturbance of TLD usage.

cGo DNS resolution of .local hostnames is still broken in Go 1.7.5, in Kubernetes scenarios.
Working around this by configuring environment variable GODEBUG with value netdns=go.

@mcandre, if you have a bug report, please file a new bug. We don't track closed issues. I'm not sure what you're saying, though. I don't know what you mean by "broken", or what a Kubernetes scenario means.


Prototype 1 Scope

To support Notary v2 requirements for multiple signatures that don't change the artifact digest or tag, we must support new artifacts that link to existing artifacts.
Goals & Intent
Experiment with storing linked artifacts in a registry, enabling the reverse lookup pattern.
The prototype should:

Validate the independent push, link, discover, pull experience.
Mock the end to end experience for building an image, signing it all offline, without having to first push to the registry to get the digest.
Not require updating any objects in a registry, including the tag
Not require tags or other pattern matching conventions to achieve the result
Enable the nv2 client with the ability to find the required signature, based on the target artifact: eg: the net-monitor:v1 image
Enable a user to locally validate the experience, without any dependency on any particular cloud provider.

The prototype should not:

Attempt to codify a solution that could be used in production, or at any scale. Can we prove the model could work? If so, we'll harden the implementation.
Focus on private or public key acquisition. Key management is not part of this prototype.
Validate with a container host. OPA validation will be done in a future prototype.

Target Experience
The experience should focus on the e2e tooling, including the use of the docker cli.
Demo Script
Deliverables

Instance of cncf distribution to locally run. The prototype would be checked into: notaryproject/distribution/prototype-1.
A built image, users can run locally pushed to: docker.io/notaryv2/registry:nv2-prototype-1
A docker plug-in to simulate the docker build, sign, push experience

The meetings notes say this phase is complete: https://hackmd.io/_vrqBGAOSUC_VWvFzWruZw?view#March-22-2021
I'm a little confused and trying to find the deliverables, the link above doesn't seem to have any prototype code in it.
Specifically, there's no diff when comparing the prototype-1 branch to the upstream repo: https://github.com/distribution/distribution/compare/main...notaryproject:prototype-1
I'm having a really hard time following what work has been done and where the code is.

Corrected demo script link: https://github.com/notaryproject/nv2/blob/prototype-1/docs/nv2/demo-script.md


fix: default order fields must be sortable, not filterable

Coverage decreased (-0.05%) to 96.203% when pulling 36daf37c0a60bc71b1da1610e2987941414a1ff4 on fix/sortable-validation into 5f3709755d08e681cca1f1341afec320b0e8f4aa on main.


iOS and IPV6 network

If you are creating an issue for a BUG please fill out this information. If you are asking a question or requesting a feature you can delete the sections below.
Failure to fill out this information will result in this issue being closed. If you post a full stack trace in a bug it will be closed, please post it to http://gist.github.com and then post the link here.
Bug Information
Version Number of Plugin: 3.2.0
Device Tested On: iphone 6
Simulator Tested On:
Version of VS: VS4MAC 7.5.1
Version of Xamarin: XF 2.3.4
Xamarin.iOS
Version: <IP_ADDRESS> (Visual Studio Community)
Hash: 408d3574
Branch: d15-7
Build date: 2018-05-08 18:56:30-0400
Versions of other things you are using:
Steps to reproduce the Behavior
Create a IPV6 network as described in http://www.brianjcoleman.com/tutorial-how-to-test-your-app-for-ipv6-compatibility/
Connect the iphone to this IPV6 network
Excecute in Xamarin Forms this code:
                                              string myip = "https://<IP_ADDRESS>/crmf"
					var ip = new Uri(myip).Host;
					var port = new Uri(myip).Port;

					var isReachable = await CrossConnectivity.Current.IsRemoteReachable(ip, port);
					if(isReachable == false) {
						await DisplayAlert("ERROR", "ERROR", "Ok");
						return;
					}

Expected Behavior
I expect that remote server is reacheable under a IPV6 network
Actual Behavior
Server is unreachable. On a non IPV6 network, the server is reachable
Code snippet
Screenshots
@jamesmontemagno maybe not a "plugin" command, but I would like to know why this IP is not reachable...

You could try the 4.0.0 package however I do not even really recommend using IsRemoteReachable at all. Just try to make the web request.

Thanks @jamesmontemagno
Web request fails the same… which can be the problem with a xxx.xxx.xxx.xxx ip when I use a IPV6 network? There is a solution for this? It's only on iOS

not sure, i mean you would want to find the IPV6 address perhaps. I wouldn't use an IP unless you are in a network that requires it and in general. I had a blog here: https://blog.xamarin.com/making-your-ios-apps-ipv6-ready/


[BUG] -

it gives an error saying (Could not establish connection. Receiving end does not exist.)
when you try to use it

Could you give more info? The template should have listed fields you were supposed to fill out.

For example, what websites does it happen on?

Hm. Odd. Can you open the console and send me a screenshot of it? (Press f12 while on Picrew and click the Console tab.)

i downloaded the newer version and its fixed now

I'm glad to hear it! Happy Browsing!


[dy] Fix dbt file delete error

Summary
Use the last index of parts to determine the extension, and use the first n-1 elements of parts to determine the block uuid. For a block named block.py.sql, the extension is .sql, and the block uuid would be block.py.

Tests
tested locally

cc: @johnson-mage

@johnson-mage updated it


feat(build): generate TypeScript definition file as a bundle

This generates types definition for better TypeScript experience. (#61)

I get an error dts-bundle after updating to ts-loader@9
AssertionError [ERR_ASSERTION]: main does not exist: C:\work\ext\vue3-sfc-loader\dist\types\vue3\src\index.d.ts

dist/types/vue2/** and dist/types/vue3/** file structures are different, don't understand why.