Android adaptive icons - cordova workflow

I implement ionic cordova project. In in project root directory I call
cordova-res android --icon-background-source '#7bb2f9' --verbose
Now I find in directory 'resources/android/icon' the files hdpi-foreground.png, ldpi-foreground.png, mdpi-foreground.png, xhdpi-foreground.png, xxhdpi-foreground.png, xxxhdpi-foreground.png. And in config.xml
 <resource-file src="resources/values/colors.xml" target="/app/src/main/res/values/colors.xml" />    <icon background="@color/background" density="ldpi" foreground="resources/android/icon/ldpi-foreground.png" />    <icon background="@color/background" density="mdpi" foreground="resources/android/icon/mdpi-foreground.png" />    <icon background="@color/background" density="hdpi" foreground="resources/android/icon/hdpi-foreground.png" />    <icon background="@color/background" density="xhdpi" foreground="resources/android/icon/xhdpi-foreground.png" />    <icon background="@color/background" density="xxhdpi" foreground="resources/android/icon/xxhdpi-foreground.png" />    <icon background="@color/background" density="xxxhdpi" foreground="resources/android/icon/xxxhdpi-foreground.png" />
As I read the adaptive Icons must located in target directories 'platforms/android/app/src/res/mipmap-hdpi' (-ldpi,-  mdpi, ...) named 'ic_launcher-foreground.png' and 'ic_launcer_round.png'.
When does the generated ...-foreground.png will be copied into target directories?
Because I no found the 'ic_launcher-foreground.png' and 'ic_launcer_round.png' in the target directories I called
cordova-res android --copy --icon-background-source '#f9d17b' --android-project platforms/android --verbose
(#f9d17b = orange)
The icons where copied now.
In order to test, if adaptive icons will be used in running app, I give the icon.png another backgroundcolor (#7bb2f9 = light blue) than the adaptive icon (orange - see above). But the running app shows the blue background. And I found, that the generated files "ic_launcher_round.png" also have blue background, while "ic_launcher_foreground.png" is transparent as expected.
I run the app on Samsung Galaxy A20 with Android 10 and on Honor 9 with Android 9.

Thank you @ebeling your comment above helped me resolve my issue also.

cordova-res android --copy --icon-background-source '#f9d17b' --android-project platforms/android --verbose

Cordova support will be dropped in 1.0 so this is going to be a wontfix from us. Thanks for the issue

I'm struggling with this also. Both with cordova-res and capacitor-assets v1@next, neither produces the -foreground assets. @ebeling did you solve this?


Include numeric_conversion and remove usage of deprecated boost/cast.hpp

@chhenning is this not merged for any reason?

It is now.


Withdraw the v2.0-alpha.20180212 release

See https://github.com/cockroachdb/cockroach/pull/23034.

This change is

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/0ab7b71e471c63c7b5519c7e99a70c6884539149/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/e6f1e5247043b994e8feb33fb71cbef79b713d85/

LGTM


doc.html

created some check boxes

There are lots of mistakes here please fix it then redo the pr


[BugFix][C++] Check  is not nullptr before calling ToString and fix empty prefix bug

Proposed changes
see issue #338 #340
and one more:
GraphInfo is invalidated when prefix is empty, since the prefix of graph info is the begin prefix of all path, it should be not empty and has no default value.
Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have read the CONTRIBUTING doc
[x] I have signed the CLA
[ ] Lint and unit tests pass locally with my changes
[x] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

Further comments
close  #338
close #340

@yixinglu , this Pull Request needs your review~


chore(components): bind calendar with calendar event

[x] connotation default - info
[x] appearances - filled, subtle

LGTM. I think that if we should add height to the description and add clamp. It will look better:

can this be done based on size constrain?

LGTM. I think that if we should add height to the description and add clamp. It will look better:

can this be done based on size constrain?

sadly no...
But we can restrict it maybe only to duration="1" and one line clamp and for the rest 2 lines?

LGTM. I think that if we should add height to the description and add clamp. It will look better:

can this be done based on size constrain?

sadly no... But we can restrict it maybe only to duration="1" and one line clamp and for the rest 2 lines?

it's a good idea, but let's avoid specifying design on the fly. it doesn't scale well as in the top sticky header.
mind opening a ticket for it?

LGTM. I think that if we should add height to the description and add clamp. It will look better:

can this be done based on size constrain?

sadly no... But we can restrict it maybe only to duration="1" and one line clamp and for the rest 2 lines?

it's a good idea, but let's avoid specifying design on the fly. it doesn't scale well as in the top sticky header. mind opening a ticket for it?

opened:
https://github.com/Vonage/vivid-3/issues/462


With 'winwidth' set the plugin automatically applies the settings to forced window width windows

I noticed this behavior when opening nvim-tree buffers or fugitive blame buffers. I use winwidth=130, and while the scrollview is enabled, the newly opened windows automatically take the 130 width instead of the much smaller ones its should take. This video should make my not so good explanation clear:
https://user-images.githubusercontent.com/83361786/188432772-d5683a06-e046-4f6a-a585-e2ec3a30992a.mp4
I recreated this with nvim -u ~/mini.lua plugin/scrollview.vim.

mini.lua
local Plug = vim.fn['plug#']
vim.call('plug#begin', '/tmp/')
Plug('dstein64/nvim-scrollview')
Plug('kyazdani42/nvim-tree.lua')
vim.call('plug#end')

require('scrollview').setup({
    excluded_filetypes = { 'NvimTree' },
    current_only = true
})

require("nvim-tree").setup {
    view = {
        adaptive_size = true,
        preserve_window_proportions = true
    }
}

-----------------------------------------------
-- CUSTOM
-----------------------------------------------

vim.opt.winwidth=130

Thanks for reporting the issue @pure-bliss!
I've updated the code in 7847c4b3ff0912457d0c794aef86529afbc8654e to restore the window size after processing. Does this solve the issue for you?

Hi! Thanks for the quick reply, and fix. I tried again, and couldn't reproduce the bug with the recent modifications, everything works fine now. Thanks again!


Alternative module archive formats

Terraform can handle archives in several different formats, including zip, tar.bz2 (tbz2), tar.gz (tgz), and tar.xz (txz). It'd be nice to have support for these different formats in the registry.
This could potentially be done by checking the backing store for which formats are available for a requested module and then automatically serving a download link corresponding to one of those formats, but the implementation complexity would be high and the value would be dubious since it's unclear how many people would have mixed archive formats in the backing store for their registry.
An alternative could be to add a --storage-module-archive-format flag that defaults to tar.gz (the current expected format) but can be used to switch over to zip, tbz2, etc.

I'm not sure if we really want to support dynamic file format detection right now. But adding the --storage-module-archive-format flag makes sense in my opinion :)
We should note that the upload command creates tar.gz archives right now. So as you mentioned, it makes sense to use it as the default in order to be backward compatible

I merged the PR, thanks for your contribution!
@heimweh and I want to get some more breaking changes in before we cut the v0.8.0 release. I hope that is okay for you, please let us know if you need a new release more urgently :)

It'd be nice to know what the planned breaking changes are, though. I just shuffled around some S3 artifacts yesterday to conform to the expected provider path structure with 0.7.0 and I'm going to have to redo all of that now that the structure has changed. Anything else like that going to happen?

That's hard to estimate for obvious reasons, but I hope that we can release v0.8 in weeks rather than months :)
I'm curious, can you elaborate a bit on how you upload your modules and what speaks against the CLI upload command?

We upload our modules to S3 using the AWS CLI. The upload CLI here is a little too opinionated to integrate easily (don't want to have to create an HCL file for every time we upload something), and it's a little more heavyweight to have to pull in the CLI as a dependency in our CI/CD pipeline when the AWS CLI is already baked in and can do what we need. We might use it in the future but at least right now it's easier to just stick with the AWS CLI.


[FEATURE] Unit Converter

A person sends a number, choose the unit, choose new unit. The bot responds with new number.

A person sends a number, choose the unit, choose new unit. The bot responds with new number.

New idea: A person sends a number + a correct unit. The bot responds with this number & unit but converted to other most popular units.


maxRetries field missing from ClientConfig type

The docs say I can specify maxRetries when instantiating a client, but typescript does not allow it.
Environment details

OS: macOS 10.15.3
Node.js version: 10.17.0
npm version: 6.11.3
@google-cloud/pubsub version: 1.6.0
typescript version: 3.7.2

Steps to reproduce

create a new file containing new Pubsub({projectId: "whatever", maxRetries: 5})
run tsc --noEmit

error TS2345: Argument of type '{ projectId: string; maxRetries: number; }' is not assignable to parameter of type 'ClientConfig'.
  Object literal may only specify known properties, and 'maxRetries' does not exist in type 'ClientConfig'.

Thanks for the report!
I'm not sure at a glance if this is a code or docs bug, but I'll have to look a bit more.

After looking at the code a bit, I'm going to guess this is a docs bug - I don't see maxRetries referenced anywhere else in the code besides those comments in pubsub.ts, so this is probably something that was removed earlier in the context of not supporting client-side delayed redelivery. I'm going to see if anyone else has thoughts on why this is in there.

The consensus seems to be that this library used to be based on @google-cloud/common, which did provide a maxRetries option (and thus Pub/Sub probably inherited it into its ClientConfig). But at this point, the only things between this library and the service endpoint are gax and grpc, which don't seem to support that concept of setting max retries.
So the docs do definitely need to be updated in the PubSub class.
What were you aiming to do by setting maxRetries? Maybe we can find another way to do it.

I see now that there are other ways of doing this, through the gaxOptions arguments.


Lw/client examples as individual projects

The client example projects now use Wakaama as a direct dependency. They
have also been split into three different projects (udp, tinydtls and
raw_block1). The CI and integration tests were adjusted for the new
project.

Just had a (very) brief look and noticed the following CMake warnings that did not show up before:
CMake Warning:
  Manually-specified variables were not used by the project:

    WAKAAMA_ENABLE_EXAMPLES

Will have a close(r) look once this is resolved.

Thank you for the hint. Removing that is part of the next PR (wip) with some clean-ups.
I decided to split a bigger change (#808) into smaller ones for better reviewing.


feat(client): Allow passing timeout options

With this new feature, 2 new optional options can be passed down to undici (as by doc)

can you add them to the docs too?

can you add them to the docs too?

Done and added also the other additional properties that were not mentioned in the docs 😉 4609da0c


fix: only apply CRDs if they exist

When deploying a separate staging/production environment without kuberhealthy, there are no CRDs and the boot job fails. See https://kubernetes.slack.com/archives/C9MBGQJRH/p1659537849699819

/assign @ankitm123

Have you tried this? I would think that you need to backslash the second newline as well.
Or you could write it as a oneliner. The most succinct would be:
[  ! -d $(OUTPUT_DIR)/customresourcedefinitions ] || kubectl apply $(KUBECTL_APPLY_FLAGS) --prune -l=gitops.jenkins-x.io/pipeline=customresourcedefinitions -R -f $(OUTPUT_DIR)/customresourcedefinitions

@msvticket Sorry, copy/paste error. Fixed it now.

@m1pl release pipeline is somewhat fixed, can u rebase ur jx3 version with the latest master?

@ankitm123 done

/retest

Tests passed:
Ran 1 of 1 Specs in 1066.234 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
--- PASS: TestSuite (1066.23s)
PASS
ok  	github.com/jenkins-x/bdd-jx/test/suite/spring	1066.287s
pod jx-bdd-xgnds has Succeeded
job jx-bdd has Succeeded
POD RESULT: OK

I like @msvticket 's suggestion to use the one liner. But ok with this as well.

/override gsm
/lgtm

/hold

@msvticket can remove the hold once he is ok with the change.

/hold cancel


Line Segment Support, Option to only show available frames, Updated README

Looks great, I will test soon but don't expect any issues.


Fix link to Java getting started page

@harelbr,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@harelbr : Thanks for your contribution to the Azure documentation! The author, @antonfrMSFT, has been notified to review your proposed change.

#sign-off


Change assert!s for debug_assert!s

Some functions should return a Resultinstead of using an assert because doing the latter would panic in runtime.
In general, if you don't have any choice but to panic it is better to describe the cases in which that function would panic and why in the documentation.
For this issue, we just want to replace these assertions with debug assertions. We'll address the Result in another issue.
An example would be this.

Can you write a short description? Thank you

Can you write a short description? Thank you

Description added!

Can I take it?

Can I take it?

Sorry for the delay, sure you can take it!


Fixes missing RPrim_float32

See also: https://github.com/fsprojects/FSharp.Compiler.PortaCode/issues/17
I PR'ed there too


Feat: Adding Button (Scroll top) ⬆

Describe the feature
Functionality:
Clicking the button triggers a smooth scroll animation that takes the user back to the top of the page. This can be implemented using JavaScript and CSS for the smooth scrolling effect.
Scenario:
A user is reading through a lengthy blog post on a website. After scrolling down several sections, they decide they want to revisit the navigation menu or start reading another post. Instead of manually scrolling back up, they can click the "Scroll to Top" button.
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Great idea @HK853. I am assigning this issue to you.

Issue already raised
Issue no #173


why delete Navigator?  react-navigation is uncapable、bugly and hard to use!

such as: https://github.com/react-community/react-navigation/issues/1467
in rn 0.44 Navigator is deleted
please do not delete navigator ,it is easy to customize and easy to enhance and this one is bugly

After understanding principles of using the new navigation, I found it much more attractive for my project

If you want to keep using Navigator it is available in a separate package now https://github.com/facebookarchive/react-native-custom-components

thank you @janicduplessis ,  do you test the new navigator ,i test it in android  35-40fps on genymotion android  @tanotify

@tanotify
if it really work or made some enhancement , i will really been grateful with this 。
but,talking is cheap, by my test  i use the navigator , 28~40 fps to open a webview , in react navigation,enven the same,and it still not support goback-gesture。
i wish you can try it ,and  compare each other,and do really some thing useful


DSP-943 - Resource Form Add Additional Value

resolves DSP-943

@flavens I've added what we did during our call as an initial starting point as well as many TODO comments. I think you will want to make the key value pairs the same way you did in the _makeResourceProperties method.


Document code format and code linting standards

We should document for other developers who want to contribute which code format and code linting we prefer.
We use currently black, isort and flake8 #317  in the backend and prettier and es-lint #333 in the frontend. The documentation should explain how to install it, what the benefits are, and how to install the pre-commit hook on the local system.

wait, did you already do this? Otherwise i can take care of documenting the frontend part

I only added the minimal documentation: https://docs.librephotos.com/5/dev_frontend/ This can still be improved easily :D


PLUTO-695

@ngriffin7a I have Leon signed the agreement, but he hasn't received the reply from Apache.

@dantewang @ChiZelin This is amazing work! I am very impressed with the thoroughness and attention to detail. Having said that, there are some changes that need to be made. Rather than merge this PR and then merge the changes, I'd prefer that you send a fixed PR instead. For that reason, I am closing this PR without merging. But again, this is very good work. I look forward to merging the next PR.


nuswide dataset

I can't download this dataset.
May I have a copy, please

Why can't you get the dataset? Do you have access to the Google drive?


Support for dotnetcore using new Visual Studio 2017 csproj format

I see that @adamhathcock  also added support for Microsoft.Framework.Configuration in #28 . This should probably be added as well as a separate pull request.
I wasn't sure how your continuous integration system works with regards to how the nuget packages are built etc. This probably needs some tweaking since it changed in Visual Studio 2017.

I would really like this to be merged. I was just looking into how I could use HOCON in .NET Core.

 The maintainer of this project seems to be somewhat inactive unfortunately.

Other than my few comments, it looks good to me.


Feature/e2e testing

This is the third pull request.  It contains the original cypress e2e tests.  More integration tests should be added down the road.
It is most certainly not over 9000 lines.

Codecov Report

:exclamation: No coverage uploaded for pull request base (develop@d0bd77c). Click here to learn what that means.
The diff coverage is 74.93%.

@@            Coverage Diff             @@
##             develop      #76   +/-   ##
==========================================
  Coverage           ?   75.42%
==========================================
  Files              ?       80
  Lines              ?     1778
  Branches           ?      211
==========================================
  Hits               ?     1341
  Misses             ?      290
  Partials           ?      147

Impacted Files
Coverage Δ

src/app/docs/page/page.component.ts
37.73% <ø> (ø)

src/app/app.component.ts
100% <ø> (ø)

src/app/containers/list/list.service.ts
100% <ø> (ø)

src/app/shared/workflow.service.ts
100% <ø> (ø)

src/app/sponsors/sponsors.component.ts
72.72% <ø> (ø)

src/app/stargazers/stargazers.component.ts
56.25% <0%> (ø)

...rc/app/workflow/paramfiles/paramfiles.component.ts
61.29% <0%> (ø)

src/app/mytools/mytools.service.ts
61.7% <100%> (ø)

src/app/search/search.service.ts
100% <100%> (ø)

src/app/shared/versions.ts
66.66% <100%> (ø)

... and 38 more

Continue to review full report at Codecov.

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

FYI, Cypress looks messed up in this branch
Cypress was not found: Installing a fresh copy.

You are trying to install the latest version of Cypress.

This CLI tool is deprecated and can no longer install versions of Cypress above 0.19.4.

For newer versions, please use the new cypress npm module.

Was going to add Cypress to npm at a later date...I guess I have no choice but to do it now.


Set profile background color on native

Else on master if you pull down you see white on top of the blue/green which looks funky. This way its the same color
@keybase/react-hackers

@keybase/react-hackers bump, open for 7 days


TrueNAS Core Email Alerts to Ntfy SMTP Server

Good Evening,
Thank you for all the help on Discord on 2/15/23 as we worked through the config of the SMTP server and attempts to get TrueNAS Core E-Mail alerts to publish to Ntfy.
I was able to successfully setup the Ntfy SMTP server and publish an e-mail to it using the command line instructions provided in the configuration documents, to confirm that ports were configured correctly and that Ntfy would receive the message properly. Then, I went to my TrueNAS Core server and ran the same e-mail test from the command line and Ntfy received the e-mail properly. Using the same configuration as the command line, I went to the automatic settings within TrueNAS (System --> Email && System --> Alert Services) and setup my e-mail server to point to Ntfy, but would not receive a notification on Ntfy.
After turning on debugging in the logs, I found the following multi-part messages being received by Ntfy in the logs, but not showing up in my Ntfy app on the Android or Web app. Here is the relevant section of the log which shows the start of the incoming SMTP mail of the failed TrueNAS notification.
Feb 16 01:04:00 notification ntfy[661]: DEBUG truenas.local/<IP_ADDRESS>:40404 SMTP Incoming mail, anonymous login
Feb 16 01:04:00 notification ntfy[661]: DEBUG truenas.local/<IP_ADDRESS>:40404 SMTP MAIL FROM<EMAIL_ADDRESS>(with options: smtp.MailOptions{Body:"", Size:1113, RequireTLS:false, UTF8:false, Auth:(*string)(nil)})
Feb 16 01:04:00 notification ntfy[661]: DEBUG truenas.local/<IP_ADDRESS>:40404 SMTP RCPT TO<EMAIL_ADDRESS>Feb 16 01:04:00 notification ntfy[661]: TRACE truenas.local/<IP_ADDRESS>:40404 SMTP DATA: Content-Type: multipart/mixed; boundary="===============2138658284696597373=="
Feb 16 01:04:00 notification ntfy[661]: MIME-Version: 1.0
Feb 16 01:04:00 notification ntfy[661]: Subject: TrueNAS truenas.local: TrueNAS Test Message hostname: truenas.local
Feb 16 01:04:00 notification ntfy[661]: From: =?utf-8?q?Robbie?=<EMAIL_ADDRESS>Feb 16 01:04:00 notification ntfy[661]: To<EMAIL_ADDRESS>Feb 16 01:04:00 notification ntfy[661]: Date: Thu, 16 Feb 2023 01:04:00 -0000
Feb 16 01:04:00 notification ntfy[661]: Message-ID<EMAIL_ADDRESS>Feb 16 01:04:00 notification ntfy[661]:
Feb 16 01:04:00 notification ntfy[661]: This is a multi-part message in MIME format.
Feb 16 01:04:00 notification ntfy[661]: --===============2138658284696597373==
Feb 16 01:04:00 notification ntfy[661]: Content-Type: multipart/alternative; boundary="===============2233989480071754745=="
Feb 16 01:04:00 notification ntfy[661]: MIME-Version: 1.0
Feb 16 01:04:00 notification ntfy[661]:
Feb 16 01:04:00 notification ntfy[661]: --===============2233989480071754745==
Feb 16 01:04:00 notification ntfy[661]: Content-Type: text/plain; charset="utf-8"
Feb 16 01:04:00 notification ntfy[661]: MIME-Version: 1.0
Feb 16 01:04:00 notification ntfy[661]: Content-Transfer-Encoding: base64
Feb 16 01:04:00 notification ntfy[661]:
Feb 16 01:04:00 notification ntfy[661]: VGhpcyBpcyBhIHRlc3QgbWVzc2FnZSBmcm9tIFRydWVOQVMgQ09SRS4=
Feb 16 01:04:00 notification ntfy[661]:
Feb 16 01:04:00 notification ntfy[661]: --===============2233989480071754745==
Feb 16 01:04:00 notification ntfy[661]: Content-Type: text/html; charset="utf-8"
Feb 16 01:04:00 notification ntfy[661]: MIME-Version: 1.0
Feb 16 01:04:00 notification ntfy[661]: Content-Transfer-Encoding: base64
Feb 16 01:04:00 notification ntfy[661]:
Feb 16 01:04:00 notification ntfy[661]: PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
Feb 16 01:04:00 notification ntfy[661]: L0VOIj4KClRoaXMgaXMgYSB0ZXN0IG1lc3NhZ2UgZnJvbSBUcnVlTkFTIENPUkUuCg==
Feb 16 01:04:00 notification ntfy[661]:
Feb 16 01:04:00 notification ntfy[661]: --===============2233989480071754745==--
Feb 16 01:04:00 notification ntfy[661]:
Feb 16 01:04:00 notification ntfy[661]: --===============2138658284696597373==--
Feb 16 01:04:00 notification ntfy[661]: DEBUG truenas.local/<IP_ADDRESS>:40404 SMTP Incoming mail error: EOF

Fixed in https://github.com/binwiederhier/ntfy/commit/e9b05e8ed7aaf1b66dcfdff5a6f5f66b256604af and https://github.com/binwiederhier/ntfy/commit/5f75e98861702c662d97f97ff65cf99f63e85ae0.
This was fun!


Geostationary projection & latitude_of_projection_origin

Forward from: https://github.com/OSGeo/PROJ/issues/1930
Currently the geostationary_projection has the latitude_of_projection_origin defined without any defaults provided.
Based on the issue above in PROJ, the projection parameter is not even used for anything and the latitude_of_projection_origin is always assumed to be 0. Are there use cases where the latitude_of_projection_origin is not 0 for the geostationary_projection?

Is it physically possible to have a non-zero latitude_of_projection_origin and still actually be “geostationary”?

In practice I don't know of any geostationary data that has a non-zero latitude_of_projection_origin. However, this is normally a by-product of rectification. Most geostationary products are produced by satellites that are, in fact, geosynchronous - the satellite doesn't stay consistently above a single point on the Earth, as this would expend a lot of fuel, but rather "wobbles" in a figure-eight about its nominal point. This wobble can actually take the satellite several degrees above and below the 0° latitude line.
Users never notice this because before products go out they are rectified, so it looks like the satellite was always over the same point, but if someone were to use a geostationary projection to provide geolocated but unrectified imagery, some of the products in a timeline might have a non-zero latitude at origin.
I'm not sure what NOAA's doing but my feeling says that PROJ's interpretation is right, so it might be worthwhile to be explicit about this in the Conventions.

I concur with @erget . Let's keep this attribute.

@erget, I think your explanation is very helpful and makes sense why it is there.
Thoughts on these changes for geostationary:

Making latitude_of_projection_origin an optional attribute with a default of 0
Adding a section with notes based on the response by @erget

That was really helpful, thanks @erget .


New parameter type Path

Do you think it is a good idea to add a new type called Path?
I am implementing a unzip pipeline whose output is directory instead of a File. Maybe Path is a better notation.
carmin.yaml in the branch swagger-0.2.1
  ParameterType:
    type: string
    enum: [File,String,Boolean,Int64,Double,List]

The type "Path" should be present in CARMIN 0.3 and the "Data" module.
CARMIN 0.2 is not well suited to deal with files and path and I think it is best to focus on CARMIN 0.3 for all the Path/Files related stuff.


[database] Create documentation for the JSON geo database

The JSON that undergirds the project is an informal extension of GeoJSON, adding properties that define things like fidelity, active date ranges, source annotation, and geopolitical entity constructs. These should be formalized.

This is done here:
https://docs.google.com/document/d/15D9t61Y1WYYH02BuIp3C8InJD40L19uHIcPNDfNv0Bk/edit?usp=sharing
Leaving this open until it is referenced in the GitHub project page, README, or index.html page.


Reduce time until container is ready to serve predictions

It now takes ~10 minutes to get a container up and running, ready to serve predictions. We should improve that.

Addressed in https://github.com/ucbrise/clipper/pull/160


Create SECURITY.md

@schizobyproxy Secure by Design.
OpenSpeedTest contains Only STATIC Files like HTML,CSS & JS.
So you don't need to worry about Security Updates or Hidden Exploits that may compromise your secure environments.


Indentation with case statements

I'll preface this with "I don't really know if there will be a resolution here".  Also far from an expert in tree-sitter.

This is neovim specifically, but I imagine any indent query will run into the same issue.  The grammar defines repeat1 for case_clauses, which I am guessing means 1 or more?  That's the node used to determine the beginning of indentation. Before any clauses have been added, there is nothing to match on to signify that we should start indentation.
It's not valid Gleam to have an empty case, so changing that doesn't seem correct?
I guess this is more of a question/discussion issue.  This functionality does work in VSCode, but obviously that is completely different.  Just noting that it's not particularly unusual behavior.
Is there anything that can be changed in the grammar to handle this?  If it's also a specific indent query issue, I can try to look more into that.
This might also end up just being a shortcoming of the grammar and indentation, but was just curious to get some info from more knowledgeable people :)

Does it make sense for the tree sitter grammar to be more relaxed than the compiler one? It could parse successfully even without any clauses. I'm not sure the intent with tree sitter.

That's a really good question, and I don't know the correct answer here.  I can look at a few other languages to see how they handle stuff like this.  Elixir has the benefit of using the generic do_block for indentation, so they get it easily for this "case" (oops).
I am curious if that would fix this issue though, since I'm not sure which node we'd use to start indentation even with support for no case clauses.

It looks like both Rust and JS at least do permit an empty body.  Fairly confident that's not valid Rust, so it seems like there is some validity to handling it that way?

Here's what we have in the Gleam parser.  I think maybe an empty case_clauses would allow for correct indentation?  I think I can try tweaking that and seeing if it works, though I may fail at it haha

Hello 👋 My policy with tree-sitter-gleam has been to hew as close as possible to the "real" Gleam parser, but am generally unopposed to making it somewhat more permissive.  Ultimately the two have different audiences; the real parser facilitates higher-level analyses and code generation whereas tree-sitter-gleam assists tooling.
TL;DR: I think empty cases should be permitted

Fixed by #59


s3 auditor should better handle policies limited by condition

A common use case is to set "Principal": "*" and limit access by vpc, vpce, or cidrs in the condition section.
Currently security_monkey will flag these policies as "POLICY - This Policy Allows Access From Anyone."  In addition, it will flag, "POLICY - THIS policy has conditions."
Security Monkey should better handle this situation.

fixed in #757


WIP : Adding Validation Accuracy and Loss

fixes #1641

Would it be reasonably possible to write a unit test for this?

I am not sure if there are any unit tests for the C++ implementation of activity classifier.

It was on my to-do list for this sprint to add some of the infrastructure needed to make these tests less painful to write (I didn't think it was fair to ask Shreya to write this). It's something I'm currently planning to do for the next sprint. It's definitely something we need to have before we actually replace the shipping (Python-based) toolkit with the new C++ version.

I was thinking about it. I think I am not handling the case if the given Frame for validation is empty and also I don't know what it does if the data is less then one batch size.

Don't forget to remove the "WIP" prefix before merging!


build errors with clang on 32bit of ubuntu 16

my build enviroment: clang3.8 on ubuntu 16.04 32bit
if [[ "$OSTYPE" == "linux-gnu" ]]; then
	export CXX=g++-4.9
fi

need to be commented in libs/build_dependencies.sh.
CMAKE_CXX_FLAGS need to change to
set(CMAKE_CXX_FLAGS "-m32 -std=c++11 -pthread -DBOOST_LOG_DYN_LINK -Wno-deprecated-declarations")

-stdlib=libc++  need libc++-dev to be installed for llvm,  but still leads to error: fatal error: '__cxxabi_config.h' file not found,  i've googled it, It seems like an ubuntu16 bug for clang3.8, so i just remote -stdlib=libc++.
-pthread need to be added to resove link error:
network_utils.cpp.o: undefined reference to symbol 'pthread_create@@GLIBC_2

Hi Tongshipen,
I'd never tried using clang on linux, only gcc have you have success on this?
Thanks,
Ivan.

No, I 'd never tried compiled it with gcc.  my problem is resolved by the changing in the issue, this issue is just a information.


Raise error/warning when using :if on a slotable component

We should raise a compile-time error if the user tries to use :for or any incompatible directive on a renderless component.
It should accept the same directives as <template>, which currently is just :let:https://github.com/msaraiva/surface/blob/b745e1322ce7b20fcbcf8503f507349da0772435/lib/surface/compiler.ex#L40.
Initial discussion started at https://github.com/msaraiva/surface/issues/182.

@lnr0626 does this still apply? How https://github.com/surface-ui/surface/pull/283 impact this?

Maybe there is a use case for looping over renderless components: to changes to the children.
In SurfaceBulma, I am trying to implement card the Card with the following capability:
<Card>

     Footer 1
     Footer 2
     Footer 3

</Card>

I want to either, inject the card-footer-item class into the a tags specified in the Footer, or I would like to wrap them in a
.
I have not found a way yet to do this, if there is one way to do it at the moment, please let me know.

Since we're deprecating :for in favour of {#for}, I think we can let this one go.

@msaraiva do we want to keep it around for :if?

I totally missed :if. Yeah, I guess we should keep it.

probably have the same issue when using :if, {#if}, :for & {#for}
surface version:
"surface": {:hex, :surface, "0.10.0", "54eeb1bc7d3e411e3cbd1074237f4369afb24c4e3177ba26f6aaf62336533197", ...
Have parent component Tabs.List with slot :tabs
Children component Tabs.Tab is defined to hold the :tabs slot's content - use Surface.Component, slot: "tabs"
When using Tabs.Tab with :if or :for directive - got error:
** (KeyError) key :opts not found in: nil. If you are using the dot syntax, such as map.field, make sure the left-hand side of the dot is a map
    (surface 0.10.0) lib/surface/compiler/eex_engine.ex:777: Surface.Compiler.EExEngine.generator_binding/2
    (surface 0.10.0) lib/surface/compiler/eex_engine.ex:711: Surface.Compiler.EExEngine.handle_slot_entries/4
    (surface 0.10.0) lib/surface/compiler/eex_engine.ex:581: anonymous fn/5 in Surface.Compiler.EExEngine.build_slot_props/4
    (elixir 1.14.1) lib/enum.ex:1662: anonymous fn/3 in Enum.map/2
    (stdlib 4.2) maps.erl:411: :maps.fold_1/3
    (elixir 1.14.1) lib/enum.ex:2480: Enum.map/2
    (surface 0.10.0) lib/surface/compiler/eex_engine.ex:578: Surface.Compiler.EExEngine.build_slot_props/4
    (surface 0.10.0) lib/surface/compiler/eex_engine.ex:362: Surface.Compiler.EExEngine.to_expression/3

Inserting dbg({module, props, name}) in deps/surface/lib/surface/compiler/eex_engine.ex:776 gives
[lib/surface/compiler/eex_engine.ex:776: Surface.Compiler.EExEngine.generator_binding/2]
{module, props, name} #=> {Moon.Design.Tabs.List, [], :default}

Looks like it's trying to use :default slot instead of desired :tabs


bicep build fails with Segmentation fault when run from a linux/amd64 Docker container

Bicep version
Bicep CLI version 0.30.23 (ec3612efc7)
Describe the bug
bicep build fails when trying to run Bicep in a Docker container with an ubuntu image. The container starts up fine and bicep --version completes with no issue but I hit a seg fault when bicep build is run
➜  controller-bicep git:(bicep-compiler) ✗ docker build --platform linux/amd64 -t sk/test-image:latest .
[+] Building 50.1s (9/9) FINISHED                                                                                docker:desktop-linux
 => [internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 504B                                                                                0.0s
 => [internal] load metadata for docker.io/library/ubuntu:latest                                                                                0.7s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => CACHED [1/5] FROM docker.io/library/ubuntu:latest@sha256:b359f1067efa76f37863778f7b6d0e8d911e3ee8efa807ad01fbf5dc1ef9006b                                                                                0.0s
 => [internal] load build context                                                                                0.0s
 => => transferring context: 69B                                                                                0.0s
 => [2/5] RUN apt-get update &&     apt-get install -y --no-install-recommends         curl         icu-devtools         ca-certificates                                                                                43.3s
 => [3/5] COPY ./test.bicep /test.bicep                                                                                0.0s
 => [4/5] RUN curl -Lo bicep https://github.com/Azure/bicep/releases/latest/download/bicep-linux-x64     && chmod +x ./bicep     && mv ./bicep /usr/local/bin/bicep     && bicep --version                                                                                5.8s
 => exporting to image                                                                                0.2s
 => => exporting layers                                                                                0.2s
 => => writing image sha256:f4fdbbe2fe945283ef842293cbd6b75464d4e1c97b30fbc832fec859de20f757                                                                                0.0s
 => => naming to docker.io/sk/test-image:latest                                                                                0.0s

What's next:
    View a summary of image vulnerabilities and recommendations → docker scout quickview
➜  controller-bicep git:(bicep-compiler) ✗ docker run -it sk/test-image:latest
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
# bicep --version
Bicep CLI version 0.30.23 (ec3612efc7)
# bicep build test.bicep --stdout
Segmentation fault
#

To Reproduce
Steps to reproduce the behavior:

Define a Docker image that downloads the Bicep CLI

FROM ubuntu:latest

# Install tools needed
RUN apt-get update && \
    apt-get install -y --no-install-recommends \
        curl \
        icu-devtools \
        ca-certificates

WORKDIR /
COPY ./test.bicep /test.bicep

RUN curl -Lo bicep https://github.com/Azure/bicep/releases/latest/download/bicep-linux-x64 \
    && chmod +x ./bicep \
    && mv ./bicep /usr/local/bin/bicep \
    && bicep --version

ENTRYPOINT ["/bin/sh"]

Build the container image using docker build
docker build --platform linux/amd64 -t sk/test-image:latest .

Run the container using docker run
docker run -it sk/test-image:latest

Run bicep --version to verify the binary runs

Run bicep build test.bicep to hit the seg fault

Additional context
The build command has also failed with the following error:
# bicep build test.bicep
assertion failed [block != nullptr]: BasicBlock requested for unrecognized address
(BuilderBase.h:557 block_for_offset)
 Trace/breakpoint trap

test.bicep:
extension radius

resource env 'Applications.Core/environments@2023-10-01-preview' = {
  name: 'default'
  properties: {
    compute: {
      kind: 'kubernetes'
      namespace: 'default'
    }
  }
}

cc @willdavsmith

Interestingly, I get a few different error codes:
> ./bicep build test.bicep
assertion failed [block != nullptr]: BasicBlock requested for unrecognized address
(BuilderBase.h:557 block_for_offset)
 Trace/breakpoint trap

> ./bicep build test.bicep
Segmentation fault

> ./bicep build test.bicep
terminate called after throwing an instance of 'PAL_SEHException'
Aborted

tested on mcr.microsoft.com/dotnet/runtime-deps:8.0 base image

See here in your Dockerfile - you're downloading Bicep x64 rather than arm64:
RUN curl -Lo bicep https://github.com/Azure/bicep/releases/latest/download/bicep-linux-x64 \
    && chmod +x ./bicep \
    && mv ./bicep /usr/local/bin/bicep \
    && bicep --version

The following discussion is geared towards the extension, but I think is also relevant to the CLI: #10245

I see, so the issue is the binary and image architecture need to be compatible with the host machine architecture. We were running amd64 images (hence the x64 Bicep) but on an arm64 machine. Switching everything to arm64 resolved this issue.
We did notice that where the binary is downloaded too also affects whether or not it runs as expected. We have to have it placed in usr/local/bin for it to run. Something like this doesn't work:
curl -Lo bicep https://github.com/Azure/bicep/releases/latest/download/bicep-linux-arm64 && chmod +x ./bicep
We get an error similar to:
./bicep build test.bicep Failed to load System.Private.CoreLib.dll (error code 0x80070002) Path: /System.Private.CoreLib.dll Error message: Could not load file or assembly '/System.Private.CoreLib.dll'. The system cannot find the file specified. (0x80070002)
But moving the binary to /usr/local/bin does work. This isn't a blocking issue for us and the docs do say to move the binary to /usr/local/bin so we'll stick with that guidance.
Thanks for the help with this!

Raised https://github.com/dotnet/runtime/issues/109593 to track this.


Chromecast AWS Mediatailor documentation

Have you read the Tutorials? Yes
Have you read the FAQ and checked for duplicate open issues? Yes
If the question is related to FairPlay, have you read the tutorial? No FP issue

What version of Shaka Player are you using? 4.7.11
What browser and OS are you using? Chrome Mac OSX / iOS native app / Google TV
Please ask your question

Is there any tutorial or materials that explain how to use AWS Mediatailor on a Chromecast Custom Receiver?
Is there any doc for CastProxy and CastReceiver usage?
Is somehow documented how to use custom builds of shaka? We have shakaVersion config parameter, but anyway to load custom builds? (to test PRs, etc)

From what I have seen there is no documented way to access the adManager from the receiver context, so any help is more than welcome

Ad breaks work differently in the Cast Application Framework.  At the moment, there is no direct access to Shaka Player from CAF.


Enable automatic token generation for VirtualMachineExport objects

What this PR does / why we need it
This PR introduces a new mechanism in the export controller so that when a VMExport with no tokenSecretRef is created, a corresponding secret is made using a name specific to the current object.
Which issue(s) this PR fixes: https://issues.redhat.com/browse/CNV-20651
Special notes for your reviewer: Work in progress
Release note:

Enable automatic token generation for VirtualMachineExport objects

/retest-required

/retest-required

/retest-required

/approve

@awels how about giving this a once over?

Sure let me take a look

/test pull-kubevirt-e2e-kind-1.23-vgpu-nonroot

/hold
/lgtm
Putting hold to give others chance to review, if no reviews in a few days I will remove the hold

/hold cancel

/retest-required

/test pull-kubevirt-e2e-k8s-1.24-sig-storage


Make the PR implementation work

Make the PR implementation work

[ ] Implement fetching open pull requests of the repo
[ ] Implement checking timestamps of pull requests
[ ] Implement alerting


NGINX Ingress Controller 0.32.0

error message :  could not build optimal proxy_headers_hash, you should increase either proxy_headers_hash_max_size: 512 or proxy_headers_hash_bucket_size: 64; ignoring proxy_headers_hash_bucket_size
nginx: [warn] could not build optimal proxy_headers_hash, you should increase either proxy_headers_hash_max_size: 512 or proxy_headers_hash_bucket_size: 64; ignoring proxy_headers_hash_bucket_size
2022/01/07 03:22:23 [warn] 967#967: could not build optimal proxy_headers_hash, you should increase either proxy_headers_hash_max_size: 512 or proxy_headers_hash_bucket_size: 64; ignoring proxy_headers_hash_bucket_size
nginx: [warn] could not build optimal proxy_headers_hash, you should increase either proxy_headers_hash_max_size: 512 or proxy_headers_hash_bucket_size: 64; ignoring proxy_headers_hash_bucket_size
2022/01/07 03:22:23 [emerg] 967#967: "proxy_cache" zone "authentication" is unknown in /tmp/nginx-cfg218567592:1259
nginx: [emerg] "proxy_cache" zone "authentication" is unknown in /tmp/nginx-cfg218567592:1259
nginx: configuration file /tmp/nginx-cfg218567592 test failed
I want to know which nginx-ingress-cotroller version can be installed successfully?
My environment:
kubernetes: v1.19.16
helm: 3.5.4
nginx-ingress-controller: 0.32.0

Assigning to @morarucostel

Hi @51qzpw ,
We use the nginx ingress controller 1.2.0 if you wanna give it a try.
Here is an article on how to install Flow on a local machine, which lists also the versions that are installed.
https://itnext.io/lets-put-boomerang-flow-on-our-laptop-8a63eac2b9e5
In step 3, it describes how to install nginx and what to run.
It uses the k8s.gcr.io/ingress-nginx/controller:v1.2.0 image.

Closing the issue due to inactivity.


[Retail]: RetailSearch.Samples.Tests.SearchWithQueryExpansionTest.TestSearchWithQueryExpansion is failing

Two different errors in diferent runs
Failed RetailSearch.Samples.Tests.SearchWithQueryExpansionTest.TestSearchWithQueryExpansion [3 s]
  Error Message:
   Assert.Contains() Failure
Not found: (filter expression)
In value:  SearchResponse []
  Stack Trace:
     at RetailSearch.Samples.Tests.SearchWithQueryExpansionTest.TestSearchWithQueryExpansion() in T:\src\github\dotnet-docs-samples\retail\interactive-tutorial\RetailSearch.Samples.Tests\SearchWithQueryExpansionTest.cs:line 34

Failed RetailSearch.Samples.Tests.SearchWithQueryExpansionTest.TestSearchWithQueryExpansion [250 ms]
  Error Message:
   System.ArgumentOutOfRangeException : Index was out of range. Must be non-negative and less than the size of the collection. (Parameter 'index')
  Stack Trace:
     at System.Collections.Generic.List`1.get_Item(Int32 index)
   at RetailSearch.Samples.Tests.SearchWithQueryExpansionTest.TestSearchWithQueryExpansion() in /tmpfs/src/github/dotnet-docs-samples/retail/interactive-tutorial/RetailSearch.Samples.Tests/SearchWithQueryExpansionTest.cs:line 31

This issue has been fixed on the backend and I cannot reproduce it anymore.

This continues to happen:
On nightly CI, consistently, since October 20.
Just now on presubmit:
Here: https://source.cloud.google.com/results/invocations/3af94d8b-6179-4928-8466-52fb8bec07e5/log
Failed RetailSearch.Samples.Tests.SearchWithQueryExpansionTest.TestSearchWithQueryExpansion [815 ms]
  Error Message:
   System.ArgumentOutOfRangeException : Index was out of range. Must be non-negative and less than the size of the collection. (Parameter 'index')
  Stack Trace:
     at System.Collections.Generic.List`1.get_Item(Int32 index)
   at RetailSearch.Samples.Tests.SearchWithQueryExpansionTest.TestSearchWithQueryExpansion() in /tmpfs/src/github/dotnet-docs-samples/retail/interactive-tutorial/RetailSearch.Samples.Tests/SearchWithQueryExpansionTest.cs:line 31

Here: https://source.cloud.google.com/results/invocations/348229e4-6c4a-4b7e-81c4-5deaadfb4f04/log
Failed RetailSearch.Samples.Tests.SearchWithQueryExpansionTest.TestSearchWithQueryExpansion [683 ms]
  Error Message:
   System.ArgumentOutOfRangeException : Index was out of range. Must be non-negative and less than the size of the collection. (Parameter 'index')
  Stack Trace:
     at System.Collections.Generic.List`1.get_Item(Int32 index)
   at RetailSearch.Samples.Tests.SearchWithQueryExpansionTest.TestSearchWithQueryExpansion() in T:\src\github\dotnet-docs-samples\retail\interactive-tutorial\RetailSearch.Samples.Tests\SearchWithQueryExpansionTest.cs:line 31

Thanks Amanda. It seems that the tests will fail with the current server behavior. Send https://github.com/GoogleCloudPlatform/dotnet-docs-samples/pull/1965 to fix the test case accordinlgy.

Thanks! It's green now.
Closed by #1965


Dark Theme Not Supported

Confirm this. Action sheet displays white text on white background if dark theme enabled.

Unfortunately, we cannot set a dark background color for whole Action Sheet (via actionsSheetProps) due hardcoded style:
https://github.com/Bur0/react-native-actions-sheet-picker/blob/acd8ebf0e87b50332ab4fe12da5cc9e08b304acf/src/components/Picker.tsx#L99


Observer on decorated property doesn't work

I'm submitting a bug report

Library Version:
1.0.1

Please tell us about your environment:

Operating System:
Linux Elementary Loki

Node Version:
4.4.7

JSPM OR Webpack AND Version
JSPM 0.16.39

Browser:
Chrome 52

Language:
ESNext

Current behavior:
Observing a property that is decorated results in "Cannot observe property 'xxx' of object" warning. Changes are not being responded to. Adding a decorator on a property will result in that property being added (regardless of the decorator's function). The createPropertyObserver will return a SetterObserver for that property, but SetterObserver calls Reflect.defineProperty for that property, which will fail as the property already is defined.
Expected/desired behavior:

What is the expected behavior?
It should probably fall back to a DirtyCheckProperty.

What is the motivation / use case for changing the behavior?

Proposed fix: https://github.com/aurelia/binding/pull/477

https://github.com/aurelia/binding/issues/406

this is more of a babel issue- same thing doesn't occur when using TypeScript transpilation.

@jdanyow We tried solving this with babel, and they didn't accept it with reason. Meanwhile, this is still an issue.
Do you have any suggestions on how to move forward?


Clean up AC/DC TNEP settings

For with settings rather than different problem files.

Fixed in release 0.6.0.


Censured and Hesitated instances should display evidence

https://gui.fediseer.com/instances/censured
Currently someone anonymous can only see the reaosns, but no receipts
Likewise, instance details should provide the receipts along with the censures: Example: https://gui.fediseer.com/instances/detail/1611.social

Fixed by #43


Bluetooth: GATT: Pass bt_conn to CCC cfg_changed callback

When CCC cfg_changed callback is called, it will now have
a pointer of the bt_conn that caused the change.
This behaviour is more consistent with other callbacks.
Signed-off-by: Rafał Kuźnia<EMAIL_ADDRESS>

@Vudentz @joerchan @jhedberg please take a look

Looks good to me and it cannot hurt to send more information, even though I don't see the purpose of this callback, as it will only trigger on the very first subscription (if another peer subscribes later on it will not trigger). It is only useful to know if at somebody or nobody is subscribed to the characteristic.
You can achieve the same using the cfg_write, which is triggered on every single subscribe/unsubscribe procedure.

@e-rk could you respond and state why you need the conn pointer here?

Yes, @fnde-ot is right. I overlooked the fact that cfg_changed is called only on the first subscription. This PR can be closed now.

Closing as per author's comments.


Remove flag causing failure

Teku failed to start: Invalid Default Fee Recipient: Bytes20 should be 20 bytes, but was 0 bytes.

LGTM, the error must be related to e2e test misconfiguration

Check the logs, is not e2e test misconfiguration but error logs checker failure, which may be acceptable to pass


Support INSERT queries

There is no support for the INSERT clause.

Requires to create InsertModule similar to SelectModule, UpdateModule and DeleteModule and declare analogical InsertExecutor in jdbc.scala module.
Live implementation of the executor can be done in a different PR.

i can pick this one

Implemented https://github.com/zio/zio-sql/pull/550


2.10A: messy versioning

Tar ball https://github.com/mm2/Little-CMS/releases/download/lcms2.10A/lcms2-2.10a.tar.gz has base ditrectory different than actual release. New version is 2.10a. and base directory is 2.10A.
It is possible to download https://github.com/mm2/Little-CMS//releases/download/lcms2.10A/lcms2-2.10A.tar.gz but it is not possible to download https://github.com/mm2/Little-CMS//releases/download/lcms2.10a/lcms2-2.10a.tar.gz
[tkloczko@barrel SPECS]$ rpmbuild -ba lcms2.spec
warning: Downloading https://github.com/mm2/Little-CMS//releases/download/lcms2.10a/lcms2-2.10a.tar.gz to /home/tkloczko/rpmbuild/SOURCES/lcms2-2.10a.tar.gz
curl: (22) The requested URL returned error: 404 Not Found
error: Couldn't download https://github.com/mm2/Little-CMS//releases/download/lcms2.10a/lcms2-2.10a.tar.gz

[tkloczko@barrel SPECS]$ wget https://github.com/mm2/Little-CMS//releases/download/lcms2.10A/lcms2-2.10A.tar.gz
--2020-06-05 20:12:21--  https://github.com/mm2/Little-CMS//releases/download/lcms2.10A/lcms2-2.10A.tar.gz
Resolving github.com (github.com)... <IP_ADDRESS>
Connecting to github.com (github.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://github-production-release-asset-2e65be.s3.amazonaws.com/507969/ada70e80-a76a-11ea-99ab-fb927104d73f?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20200605%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20200605T191221Z&X-Amz-Expires=300&X-Amz-Signature=903781c6defc00960aec1c1218682ef2c622941bbd3c6d4f158ae3371f4510a9&X-Amz-SignedHeaders=host&actor_id=0&repo_id=507969&response-content-disposition=attachment%3B%20filename%3Dlcms2-2.10a.tar.gz&response-content-type=application%2Foctet-stream [following]
--2020-06-05 20:12:22--  https://github-production-release-asset-2e65be.s3.amazonaws.com/507969/ada70e80-a76a-11ea-99ab-fb927104d73f?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20200605%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20200605T191221Z&X-Amz-Expires=300&X-Amz-Signature=903781c6defc00960aec1c1218682ef2c622941bbd3c6d4f158ae3371f4510a9&X-Amz-SignedHeaders=host&actor_id=0&repo_id=507969&response-content-disposition=attachment%3B%20filename%3Dlcms2-2.10a.tar.gz&response-content-type=application%2Foctet-stream
Resolving github-production-release-asset-2e65be.s3.amazonaws.com (github-production-release-asset-2e65be.s3.amazonaws.com)... <IP_ADDRESS>
Connecting to github-production-release-asset-2e65be.s3.amazonaws.com (github-production-release-asset-2e65be.s3.amazonaws.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 15763150 (15M) [application/octet-stream]
Saving to: ‘lcms2-2.10A.tar.gz’

lcms2-2.10A.tar.gz                                100%[=============================================================================================================>]  15.03M  2.15MB/s    in 6.5s

2020-06-05 20:12:28 (2.32 MB/s) - ‘lcms2-2.10A.tar.gz’ saved [15763150/15763150]

[tkloczko@barrel SPECS]$ wget https://github.com/mm2/Little-CMS//releases/download/lcms2.10a/lcms2-2.10a.tar.gz
--2020-06-05 20:13:02--  https://github.com/mm2/Little-CMS//releases/download/lcms2.10a/lcms2-2.10a.tar.gz
Resolving github.com (github.com)... <IP_ADDRESS>
Connecting to github.com (github.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2020-06-05 20:13:02 ERROR 404: Not Found.

Downloaded lcms2-2.10A.tar.gz has inside base directory lcms2-2.10a/
Is it possible to correct that?
Kind of question: is it possible to change tagging convention from lcms<version> to just <version>? With current tagging convention autogenerated https://github.com/mm2/Little-CMS/archive/lcms2.10A.tar.gz from tag tar ball has base directory Little-CMS-lcms2.10A/

Sorry, the release script was lauched by mistake. Fixed.
Please ignore the "A" mess, current version is 2.10, package name is lcms2

fixed

So there is no yer new release?
OK fine :)
What about change tagging convention? :P

Hi,
Yes, this is a new release 2.10. It was released some (few) days ago.
I was creating a script to automate all release process and
unfortunately things went messy when testing. My fault. Sorry. The
files and everything are now restored to 2.10.
Regarding tagging, yes, I could do that on next release. For now some
people is using this convention and I would break their process. But
for 2.11 I will change to version number only. It makes senses to me.
Best Regards
Marti
Quoting Tomasz Kłoczko<EMAIL_ADDRESS>
So there is no yer new release?
OK fine :)
What about change tagging convention? :P
--
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub:
https://github.com/mm2/Little-CMS/issues/219#issuecomment-639768071

Np. :)
Thanks


IOS 13 Modal Won't Dismiss, Fix recommended. [BUG]

presentationControllerShouldDismiss function must not return self.isModalInPresentation, because isModalInPresentation defaults to false, the should dismiss function only called when isModalInPresentation is false, therefore it is never set to true and sheet won't dismiss.
Suggested Solution:
Define a custom variable in DKImagePickerController as shouldPageClose and return this value based on desired behaviour.

Are you having trouble with the camera not dismissing, after taking a picture?

@dailydmello No, I am having trouble with the picker view controller which is presented with the rootVC, I mean the actual picker layout, It won't dismiss with swipe down action as opposed to new IOS 13 sheet presentation.

I have some issue with iOS 13 and use swipe to select/deselect images... the modal close it when I start the swipe

Fixed! Thanks!!!


Update FsLock c++/rust interface to use cxx

Followup on https://github.com/newsboat/newsboat/pull/1317.

Coverage decreased (-0.007%) to 57.938% when pulling 34b9cafb84a947da580e6394c953334eadf18dbb on dennisschagt:feature/fslock-rust-cxx-bridge into e57756a8033495b7ee9b624058eeb6762d3ab733 on newsboat:master.


Added step to update serviceMetadata tag

Without the metadata update the silverlight client was still throwing errors. Comments within the mdsWsHttpBehavior suggest that the need for this change is already part of the common knowledge around configuring MDS to use SSL.

@Galaeci : Thanks for your contribution! The author, @leolimsft, has been notified to review your proposed change.

@LeoLiMSFT Please confirm whether the suggested change is correct.

@Galaeci I am waiting to confirm this fix with the MDS product team. Meanwhile, before we can merge this PR, you'll have to resolve the merge conflicts. Shortly after you opened this PR, someone on my team did some bulk cleanup to make sure that all links used https and to remove the en-us/ locale portion of any URLs that had one. Please don't undo any of these changes.

#sign-off

@douglaslMS: I'm sorry - only the author of this article, @leolimsft, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


Field cleared after refresh.

Hello,
I installed your above solution in our trial environment for testing purposes and enabled it and it works as expected until we “Save” and Refresh.
Once I save, the field is populated both server and client (which is awesome) but when I save and refresh, values are still server side but on the form it looks like it is emplty.
It is really confusing for end users as they arrive on a blank field.
Am I the only one facing this issue?
Thanks in advance,
Best regards
Dimitri
PCF.pptx

Sorry to hear that.it is not an issue I have seen.more than happy to discuss with you.
Get Outlook for Androidhttps://aka.ms/ghei36

From: dim895<EMAIL_ADDRESS>Sent: Sunday, December 27, 2020 10:12:00 AM
To: markcunninghamuk/PCF_Library<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [markcunninghamuk/PCF_Library] Field cleared after refresh. (#3)
Hello,
I installed your above solution in our trial environment for testing purposes and enabled it and it works as expected until we “Save” and Refresh.
Once I save, the field is populated both server and client (which is awesome) but when I save and refresh, values are still server side but on the form it looks like it is emplty.
It is really confusing for end users as they arrive on a blank field.
Am I the only one facing this issue?
Thanks in advance,
Best regards
Dimitri
PCF.pptxhttps://github.com/markcunninghamuk/PCF_Library/files/5744379/PCF.pptx
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/markcunninghamuk/PCF_Library/issues/3, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFKLYCBU4YLKR4U4IIYH4KLSW4B7BANCNFSM4VKVYVFA.

Ah I now understand after looking. You want a way to show the selected values. This is something I can work on. It will need some extra code.
Get Outlook for Androidhttps://aka.ms/ghei36

From: dim895<EMAIL_ADDRESS>Sent: Sunday, December 27, 2020 10:12:00 AM
To: markcunninghamuk/PCF_Library<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [markcunninghamuk/PCF_Library] Field cleared after refresh. (#3)
Hello,
I installed your above solution in our trial environment for testing purposes and enabled it and it works as expected until we “Save” and Refresh.
Once I save, the field is populated both server and client (which is awesome) but when I save and refresh, values are still server side but on the form it looks like it is emplty.
It is really confusing for end users as they arrive on a blank field.
Am I the only one facing this issue?
Thanks in advance,
Best regards
Dimitri
PCF.pptxhttps://github.com/markcunninghamuk/PCF_Library/files/5744379/PCF.pptx
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/markcunninghamuk/PCF_Library/issues/3, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFKLYCBU4YLKR4U4IIYH4KLSW4B7BANCNFSM4VKVYVFA.

Hello,
Yes you got it right, this is exactly what we need so that users:

can see what has been chosen
make it possible for them to edit the field.

I guess this is something that will certainly help other too.
Best regards,
Dimtiri

would definitely love this feature as well!

Hi @markcunninghamuk @dim895
I would like to thank you so much for the innovative idea. I have tried this component in one of my model driven apps and facing the same issue. Can you please help me to know if it is something fixed? If so, can you please share updated solution or a code snippent?
Thanks in advance for your help.
Regards,
SB

Add an issue to repo and I will try look at it soon.
Get Outlook for Androidhttps://aka.ms/ghei36

From: sbv1990 @.>
Sent: Thursday, July 15, 2021 4:32:03 PM
To: markcunninghamuk/PCF_Library @.>
Cc: Mark Cunningham @.>; Mention @.>
Subject: Re: [markcunninghamuk/PCF_Library] Field cleared after refresh. (#3)
Hi @markcunninghamukhttps://github.com/markcunninghamuk @dim895https://github.com/dim895
I would like to thank you so much for the innovative idea. I have tried this component in one of my model driven apps and facing the same issue. Can you please help me to know if it is something fixed? If so, can you please share updated solution or a code snippent?
Thanks in advance for your help.
Regards,
SB
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/markcunninghamuk/PCF_Library/issues/3#issuecomment-880794971, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFKLYCDXDF5SDG3CMLHBX23TX35PHANCNFSM4VKVYVFA.

Hi @markcunninghamuk,
Thanks for your prompt reply.
It is the same issue, when I save, selected values are getting saved correctly but when I refresh, values are not getting prepopulated from previous save it looks like it is empty.
Regards,
SB

Hi all, I am making some progress on this issue, I am working on it this week.

I have tried with the react select component, sadly I cannot get it to work. I am not sure if its a bug with react-select and defaultOptions

Can you try the latest version <IP_ADDRESS> from the releases section. Please close the issue if it works for you.

Its working, I have tested it in a fresh environment. Closing this issue.


Highlighting for new lsp diagnostic

New diagnostic from lsp-handlers has new Highlights, any plan to include them.
Thanks for this colorscheme, I love it.

Already support，but i forget commit…when i wake up . I will update

update.

just another question, underline is also supported?

How about now?

thank you!
it looks really great.


[Improvement proposal] middleware architecture

I think I now understand the root cause behind the https://github.com/codeguy/Slim/issues/410 (closed, but thanks to @codeguy for the insight) and https://github.com/codeguy/Slim/issues/409 (still marked as open).
There are basically two types of completely different middleware ("the" middleware, and the "route middleware"). These are, apparently, very different in nature, since the fisrt one works outside the main application context, and the second one -- inside.
The outer middleware can't use redirect()/stop()/halt() functions as some internal exceptions won't be handled properly, flash() functionality just silently doesn't work; there may be other discrepancies in the behavior that one can tell just by trial and error.
The router middleware, on the other hand, is simple functions that do not 'wrap' the route callable, but are just run before it. They have access to all redirect helpers, and flash() works there, too. The problem is that one has to specify such middleware for each route explicitly, and there's no way to define such middleware for all routes.
One example is an authentication middleware -- it needs to run before the route, but at the same time this middleware might want to redirect the user to a new URL, or set a flash message.
Basically the 'onion' currently looks like this:
(pretty_exceptions
    (middleware2
        (middleware1
            (flash
                (slim_core -> redirect_exception_handler -> routes -> route
                    (route_middleware1 + route_middleware2 + ... + callable)
                /slim_core)
            /flash)
        /middleware1)
    /middleware 2)
/pretty_exceptions)

Proposal 1
If  flash middleware would be added at $app->run(), not at $app->__construct(), and if redirect_exception_handler wrapper would also be an outer middleware, then redirect/flash functionality should start working in outer middleware, too:
(pretty_exceptions
    (redirect_exception_handler
        (flash
            (middleware2
                (middleware1
                    (slim_core -> redirect_exception_handler -> routes -> route
                        (route_middleware1 + route_middleware2 + ... + callable)
                    /slim_core)
                /middleware1)
            /middleware 2)
        /flash)
    /redirect_exception_handler)
/pretty_exceptions)

Proposal 2
I think that the architecture would be more consistent and uniform if:
a) route middleware would allow using the same objects instantiated from Slim_Middleware class that would wrap the callables (which will be the last chain in middleware).
b) it would be possible to specify where the middleware should go: as an outer middleware as it is now, or as a route middleware that should wrap the callable.
So the onion would look like this:
(pretty_exceptions
    (redirect_exception_handler
        (flash
            (middleware2
                (middleware1
                    (slim_core -> routes -> route
                        (route_middleware1
                            (route_middleware2
                                (callable)
                            /route_middleware2)
                        /route_middleware1)
                    /slim_core)
                /middleware1)
            /middleware 2)
        /flash)
    /redirect_exception_handler)
/pretty_exceptions)

Since this has been opened for quite awhile, not sure if this has changed or if its still the same. I will close this out as a lot has changed in Slim develop branch which might reflect some of this.


Broken BackAndroid handling

We use GitHub Issues for bugs.
Description
Handling back button with BackAndroid does not work - while adding handlers works fine they are never called. The reason behind this - Array.from(new Set([1, 2, 3])) returns empty array. Sets are used by the BackAndroid module.
Reproduction

add new handler in BackAndroid and observe how it's not executed.

Additional Information

React Native version: 0.36, .40
Platform: Android
Operating System: MacOS
Device: Nexus 5, Android 6.0.1, patch lvl: October 5, 2016

Do you have any code samples that show how the error can be reproduced?

I've same issue but after rebuild the project the problem disappears.
Do you build react-native from source? React native make some changes on JSC recently, try to you rm -rf node_modules && npm install(make sure you have latest gradle script) and rebuild your project?

I have this same issue in RN 0.43.4.
I can confirm that:

The BackAndroid.android.js I see contains var subscriptions = [...backPressSubscriptions].reverse();
In the compiled version turns this becomes var subscriptions = [].concat(babelHelpers.toConsumableArray(backPressSubscriptions)).reverse();
toConsumableArray uses Array.from(arr) for non-arrays
When I dump a log for the expression Array.from(new Set([1, 2, 3])) into my project I get [] but in node.js when I do that I get [ 1, 2, 3 ].

I believe I have tracked down the underlying issue.
At the start of my code I import 'core-js/es6/symbol'; so that ES6 Symbol is available.

React Native includes its own Set polyfill in Libraries/vendor/core/Set.js
_shouldPolyfillES6Collection('Set') returns true so RN's Set polyfill is used
When the polyfill is initialized toIterator.ITERATOR_SYMBOL is '@@iterator' because Symbol does not exist
All of this happens before any application code runs or polyfills are required
During runtime if you require the symbol polyfill or any polyfill that requires the symbol polyfill

Symbol actually exists and Symbol.iterator is defined
The Array.from polyfill will then look for iterators defined using the value of Symbol.iterator instead of '@@iterator'
Because RN's custom Set polyfill doesn't use the correct iterator symbol Array.from(new Set(...)) now always returns []

If I remove all code that leads to a Symbol polyfill being required, the bug goes away.

Workaround 1
Remove anything that depends on a Symbol polyfill (not a very reasonable workaround).
Workaround 2
After requiring something that uses a Symbol polyfill, use this to hack the correct iterator into RN's custom polyfill:
{
	// https://github.com/facebook/react-native/issues/11968
	// RN currently has a custom `Set` polyfill that is broken when you use an actual Symbol polyfill
	let toIterator = require('react-native/Libraries/vendor/core/toIterator');
	if ( toIterator.ITERATOR_SYMBOL !== Symbol.iterator && Set.prototype[toIterator.ITERATOR_SYMBOL] ) {
		Set.prototype[Symbol.iterator] = Set.prototype[toIterator.ITERATOR_SYMBOL];
	}
}

Short-term fix
BackAndroid (now BackHandler.android) doesn't actually have any reason to depend on fancy iterator behaviours. The line immediately after the ES6 [...arr] syntax is an ES3 style for(var i ...) loop. And the code is unnecessarily adding more low level loops (new Set(_backPressSubscriptions) clones the set, [...backPressSubscriptions] creates an array and uses an interator function to fill it with the values in the cloned set, .reverse() then reverses the order of the array).
A simple fix would be to replace this:
  var backPressSubscriptions = new Set(_backPressSubscriptions);
  var invokeDefault = true;
  var subscriptions = [...backPressSubscriptions].reverse();

with this:
  var invokeDefault = true;
  var subscriptions = [];
  _backPressSubscriptions.forEach(function(subscription) {
    subscriptions.unshift(subscription);
  });

(If you think unshift is sub-optimal I could equally use push (or pre-calculate the array size) and make the for loop run backwards)
Long-term fix
Long term this is going to be a general problem with this pattern of React Native hardcoding its own embedded polyfill and likely will result in other parts of React Native breaking – the short-term fix after all doesn't actually fix Set; Set, Map, any any other polyfill in RN implementing an iterator will still be broken.
React Native should either abandon low-level ES6 polyfills with conflict potential like Set and Map tweaking internal RN code so it does not rely on them or React Native should directly require core-js' set and map polyfills.

haha I can't believe I just spent an entire day trying to figure out why the back button wasn't working. It's the issue @dantman described. I was importing the Symbol polyfill from core-js. Back button was working on chrome debug mode, not in the regular app.

@dantman
Can you submit a pull request?

Hi there! This issue is being closed because it has been inactive for a while.
But don't worry, it will live on with Canny! Check out its new home: https://react-native.canny.io/feature-requests/p/broken-backandroid-handling

I've added a PR

@cosmith Tried this. It still doesn't work for me.
Created backhandler-custom file and imported in my App.js
In my App.js added event listener for hardwareBackPress like this
...
import BackHandler from "./backhandler-custom"
componentDidMount(){
    BackHandler.addEventListener('hardwareBackPress', this.handleBackButton);
    ....
}

componentWillUnmount(){
    BackHandler.removeEventListener('hardwareBackPress', this.handleBackButton);
    ....
}
handleBackButton() {
    console.log('back button pressed')
    console.log('Actions.state',Actions.state)
    // return true;
    if (Actions.state.index === 0) {
      console.log('index 0')
      BackHandler.exitApp();
      return false
    }
    console.log('index ',Actions.state.index)
    Actions.pop()
    return true
  }

@rohitgoyal maybe try importing it with another name like AuroreM


Build binaries in CI and publish in github releases

It makes linux, mac and windows binaries in Travis CI and publish in github releases by git tag.
You need add repository to Travis CI and add github access token (Github Settings->Developer Settings->Personal Accwss Tokens) to environment variable GITHUB_TOKEN (Travis CI Repository Settings->Environment Variables)

fix build in windows

add ci script for automatic build

update Makefile for automatic builds

get version from git tag

Awesome stuff, thank you! Just released v.0.2.2 through this.


DNS challenge fails for cloudflare provider.

Do you want to request a feature or report a bug?
BUG
What did you do?
I'm running traefik in a docker container based on traefik:1.7-alpine. The actual version is v1.7.0-rc3.
When I use route53 provider, traefik retrieves certificates consistently, however, it fails to get certificates for cloudflare domains most of the time.
Four out of five times I got incorrect TXT record error.
That's what @nmengin wrote about this problem:
I guess the problem comes from the parametrization of the cloudflare provider into LEGO 👍
The TTL and the check timeout are equals (120s) that's why even if we try twice the problem persists.

What did you expect to see?
Certificates being generated
What did you see instead?
Error 403 - urn:ietf:params:acme:error:unauthorized - Incorrect TXT record ... found at _acme-challenge.domain.eu.com
Output of traefik version: (What version of Traefik are you using?)

A Pull Request which is already opened on LEGO seems to solve all problems with wildcard and base name domains.
I just proposed a modification in this way on the PR: https://github.com/xenolf/lego/pull/607#issuecomment-414360798
I have some tests to make with the modifications but for the moment the PR (+ my modifications) seems to work.
If you want, you can make your own tests with my home-made Træfik image nmengin/traefik:acme-dns.
If the tests are OK and  if the PR is validated by the LEGO team we will update the dependencies ASAP in the way to integrate its modifications.

Hello @A-Shleifman ,
I confirm that your problem is solved with the LEGO PR. I just tested it sucessfully with cloudflare.

Hi @nmengin,
Thanks a lot for the reply and for the modification!
Just tested it with your image as well and it works perfectly. Traefik retrieved certificates in a few seconds :)

Closed by #3888.


[Event Request] Table 43 Purch. Comment Line - procedure SetUpNewLine - OnSetUpNewLineOnBeforeFindFirst

Please add the following Event OnSetUpNewLineOnBeforeFindFirst to procedure SetUpNewLine in Table 43 Purch. Comment Line
[Event Request] Table 43 Purch. Comment Line - procedure SetUpNewLine
var
    PurchCommentLine: Record "Purch. Comment Line";
begin
    PurchCommentLine.SetRange("Document Type", "Document Type");
    PurchCommentLine.SetRange("No.", "No.");
    PurchCommentLine.SetRange("Document Line No.", "Document Line No.");
    PurchCommentLine.SetRange(Date, WorkDate());

    OnSetUpNewLineOnBeforeFindFirst(Rec, PurchCommentline); // <-- NEW Event

    if not PurchCommentLine.FindFirst() then
        Date := WorkDate();

    OnAfterSetUpNewLine(Rec, PurchCommentLine);
end;

[IntegrationEvent(false,false)]
local procedure OnSetUpNewLineOnBeforeFindFirst(var PurchCommentLineRec: Record "Purch. Comment Line"; var PurchCommentLineFilter: Record "Purch. Comment Line")
begin
end;

Availability update: We will publish a fix for this issue in the next update for release 22.
Build ID to track: 56679.


Manually generate signatures for some PInvokes to handle SetLastError.

Mimicks the generated code from LibraryImport but with handrolled Get/SetLastError as it's not available everywhere.

https://github.com/microsoft/CsWinRT/blob/cc36846eba0342e9f3dd0f457783202df198842f/src/cswinrt/strings/WinRT.cs#L32-L36
Should these signatures translate to uint?

My two cents: like with previous changes in this file, I'm not really sure this is worth the effort at all right now, as this is not code we should keep. We need to bump the TFM for CsWinRT to .NET 8 (I guess once it goes GA), and then only handle NS2.0 and .NET 8, where on the .NET 8 we'll be able to just use [LibraryImport], which will do the right thing. For downlevel, we can then either not worry about eg. the last system error, or just add polyfills then. But making so many changes now I think is not ideal, given we'll end up rewriting most of this file soon anyway once we finally can bump that TFM 🤔

We need to bump the TFM for CsWinRT to .NET 8 (I guess once it goes GA)

@manodasanW plans on moving away from the .NET 6 TFM?

I'll update the PR with multitargeting given some of the concerns raised about doing this correct downlevel.
I don't see .NET 6 getting dropped soon.

As a general rule: if a library is multi-targeting, unless very extreme cases where not possible, do not make compromises on the latest target by using downlevel APIs everywhere. Instead, add necessary polyfills only on the downlevel target, and use the best approach on the latest one.

Changed to only use new signatures on .NET 6 and newer.

We will need to continue supporting .NET 6 as it is an LTS.  But I am exploring what it means to have both .NET 6 and .NET 8 versions of the Windows SDK projection.  With that said, given we are a targeting pack, it is looking like it is going to require .NET SDK changes first before that can be done so I won't take a dependency on that for now.


Adds styling of the maintenance page

As part of this, I split the test into two. One tests the request and that the maintenance page is displayed and the other is a regular snapshot test of the new MaintenanceIndex view. I did this so the snapshot HTML is not compressed so that we get easier diffs.

Changed across the board to maintenanceMessage and MAINTENANCE_MESSAGE.

Oh and I also changed the icon. Even a server maintenance isn't anything we're "warning" anyone about, so the ⚠ symbol was less appropriate than an information icon.


Add a bloopInstall profile

This is a suggestion for your PR NVIDIA/spark-rapids#9615
We can simplify Maven command for the bloop project generation by creating a bloopInstall profile
mvn [-f scala2.13] install -B -Dmaven.repo.local=$PWD/.bloop-m2 -DbloopInstall -Dbuildver=3XY, and enforce Java11+ there.
Running bloopInstall plugin on the command line is prevented by specifying an invalid config path.
mvn -f scala2.13 -Dmaven.repo.local=$PWD/.bloop-m2 -Dbuildver=330 ch.epfl.scala:bloop-maven-plugin:bloopInstall
...
[ERROR] /dev/null/ERROR: Do not specify the bloop-maven-plugin on the command line. Instead invoke `mvn install -DbloopInstall ...`: Not a directory

We can change buildall and doc accordingly.

One thing that I don't like is that if a naive user invokes ch.epfl.scala:bloop-maven-plugin:bloopInstall from the command line with Java 8, this will still allow them to do so. Do you know of a way to disallow this default-cli invocation?

This is a good point, I have a hacky workaround, requesting users to use the profile instead of default-cli. I also share your conclusion  that skip is not implemented correctly in bloop-maven-plugin. However, even if it was it does not fully accomplish the job, it skips the execution silently without telling the user what the issue is.

@PhilDakin thanks for review, PTAL

@PhilDakin will you merge this PR into your PR branch, or should I open a separate PR against NVIDIA/spark-rapids ?

We can merge into this branch


Search response returns incorrect number of documents

Describe the bug
Search response returns root.fields.totalCount = X, but in fact lesser number of documents is returned
To Reproduce
Steps to reproduce the behavior:

launch vespa cluster with 12 pods (helm chart attached): helm create vespa -n vespa-privatemedia --create-namespace .
load vespa application package (attached)
load attached data.json via vespa-feeder cli tool: vespa-feeder data.json
execute a query as:

curl 'http://localhost:8080/search/' \
--header 'Content-Type: application/json' \
--data '{
    "yql": "select * from mp_private_media where site_id contains '\''c5402062-bedf-4e3e-80ad-d668993ed9b2'\'' and state contains '\''trash'\''",
    "hits": 100,
    "offset": 0
}'

Response contains root.fields.totalCount=54, but in fact 38 docs get returned
Expected behavior
Response should contain 54 docs, as root.fields.totalCount claims
Environment (please complete the following information):

OS: Amazon Linux
Infrastructure: Kubernetes
Versions: v1.24.17-eks

Vespa version
8.408.12
Additional context
Note: the problem varies based on the number of nodes defined in content cluster. Looks like it's a distribution key releated issue
vap_privatemedia.zip
vespa_privatemedia_helm.zip
data.json.zip

This could be due to timeout, see the doc on timeout and the further documentation this points to, e.g. soft timeout
See also documentation about summaries, especially the section on performance
An actual query response could also be helpful. In that case please include "trace.level": 4 in the query

Noe feedback, closing


[SwapRouter] misc: Delete duplication of SwapAmountInRoute between gamm module and swap router module

Background
cref: https://github.com/osmosis-labs/osmosis/pull/3880#discussion_r1059985454
Right now, we have two implementations of SwapAmountInRoute, one in the gamm module(legacy) and the new SwapAmountInRoute struct / proto that has been introduced in the swap router module.
There is no reason to keep both structs: the goal of this issue is to delete the SwapAmountInRoute from the gamm module and remove duplication of the struct between modules.
The same goes for SwapAmountOutRoute.
Suggested Design

Remove SwapAmountInRoute from gamm module
Remove SwapAmountOutRoute from gamm module

Could I work with it

@hieuvubk  We're trying to get the swap router / concentrated liquidity asap, but as long as this doesn't take to long, yeah go for it!

Would like to note that this is blocked on #3880. Please wait for that to be merged

Marked this as "Help wanted" since this is not on the critical path.

Could I work with it?

@phamminh0811 yes please!


Introducing a unified & general interface for class serialization

It's good to consider introducing a unified & general interface for from_dict
Some existing implementation & discussion

https://github.com/neulab/ExplainaBoard/blob/aaf91a57f4a5c143a6f6c2aec33a81a3e51690b8/explainaboard/utils/serialization.py#L4
https://github.com/neulab/ExplainaBoard/pull/301
https://github.com/neulab/ExplainaBoard/blob/aaf91a57f4a5c143a6f6c2aec33a81a3e51690b8/explainaboard/feature.py#L43

Duplicate of #446, close anyway


Loops docs page

I found another docs template from reading through the Segment docs (https://raw.githubusercontent.com/segmentio/segment-docs/develop/templates/partners/destination-new.md) and that also refrences the include you were asking about. I guess it's necessary to have there.
I've updated the PR to include an extra paragraph.


Tweak hat sizes

Since we updated our hat shapes I have been tweaking my own internal shape settings.
Checklist

[-] I have added tests
[-] I have updated the docs and cheatsheet
[-] I have not broken the cheatsheet

do you have a settings.json snippet I can drop in to try these instead of needing to run this PR?
I will say I'm quite hesitant to keep tweaking these shapes, as they've been working great for me and we've had no user complaints. But I promised I'd try your tweaks so I will keep my promise 😊

Absolutely here
"cursorless.individualHatAdjustments": {
        "default": {
            // "sizeAdjustment": 30
        },
        "ex": {
            // "sizeAdjustment": 15
            "sizeAdjustment": 2.5
        },
        "fox": {
            // "sizeAdjustment": 10
            "sizeAdjustment": 5
        },
        "wing": {
            // "sizeAdjustment": 2.5
        },
        "hole": {
            "sizeAdjustment": 5.5
        },
        "frame": {
            // "sizeAdjustment": 20
        },
        "curve": {
            "sizeAdjustment": 6,
            // "verticalOffset": 3
            "verticalOffset": -2
        },
        "eye": {
            "sizeAdjustment": 4.5
        },
        "play": {
            "sizeAdjustment": 0
        },
        "bolt": {
            "sizeAdjustment": 5.5
        },
        "crosshairs": {
            "sizeAdjustment": 0
        }
    },

What can I say. They don't work great for me?


test_wav_data is not working

Cell 14 in the google colab shows an error.

Hi @JaimeCababie ,
I've just tried this out, and am not seeing the error:

Please let me know if you are facing issues, the value of the test_wav_file_path variable would also be helpful.

Hi, @sandeepmistry ,
I also reproduced this error,  maybe it is caused by different versions of tensorflow and Tensorflow-io?
In Colab, My Tensorflow<EMAIL_ADDRESS>Tensorflow-io<EMAIL_ADDRESS>

@bronya5th great work tracking this down, I've created pull request #6 with your suggested fix.
Please let me know what you think.

This issue is still persisting after increasing the version to 0.24.0 too.
Is there any solution to this?


服务端, 客户端运行几个小时后会停止工作. 需要重启服务端, 客户端.

hi, @xtaci 首先我用这个项目用得很爽, 感谢, 赞一个!
最近一段时间, 我注意到有一个问题, 不知道如何改善, 表现就是运行一段时间后, 客户端, 服务端均停止工作. 以下是日志, 这次我留了个现场:)
server 的日期 +8小时和 client 一一对应.
server, ver 20170221
/root/kcp/server_linux_amd64 -t server.ip:8989 -l :4000 -mode fast2 -sndwnd 1536 --log /var/log/kcp.log
2017/03/22 05:27:27 stream opened
2017/03/22 05:27:27 stream opened
2017/03/22 05:30:37 stream closed
2017/03/22 05:30:37 stream opened
2017/03/22 05:31:39 stream closed
2017/03/22 05:31:52 stream closed
2017/03/22 05:32:20 stream opened
2017/03/22 05:34:38 stream closed
2017/03/22 05:36:20 stream closed
2017/03/22 05:36:22 stream opened
2017/03/22 05:36:50 stream opened
2017/03/22 05:40:23 stream closed
2017/03/22 05:40:51 stream closed
2017/03/22 05:47:01 stream opened
2017/03/22 05:48:48 stream opened
2017/03/22 05:51:02 stream closed
2017/03/22 05:52:40 stream opened
2017/03/22 05:52:48 stream closed
2017/03/22 05:55:54 stream opened
2017/03/22 05:55:55 stream opened
2017/03/22 05:55:56 stream opened
2017/03/22 05:56:03 stream opened
2017/03/22 05:56:11 stream closed
2017/03/22 05:56:11 stream opened
2017/03/22 05:56:40 stream closed
2017/03/22 06:00:04 stream closed
2017/03/22 06:00:12 stream closed
2017/03/22 06:00:19 stream closed
2017/03/22 06:01:09 stream closed
2017/03/22 06:01:57 broken pipe

client , ver 20170221
./client_darwin_amd64 -r "server.ip:4000" -l ":8989" -mode fast2 -rcvwnd 1536
2017/03/22 14:01:15 stream opened
2017/03/22 14:01:15 stream opened
2017/03/22 14:01:15 stream opened
2017/03/22 14:01:15 stream opened
2017/03/22 14:01:16 stream opened
2017/03/22 14:01:25 stream closed
2017/03/22 14:01:25 stream opened
2017/03/22 14:01:25 stream closed
2017/03/22 14:01:25 stream closed
2017/03/22 14:01:25 stream closed
2017/03/22 14:01:25 stream opened
2017/03/22 14:01:25 stream opened
2017/03/22 14:01:26 stream closed
2017/03/22 14:01:26 stream opened
2017/03/22 14:01:29 stream closed
2017/03/22 14:01:29 stream closed
2017/03/22 14:01:29 stream closed
2017/03/22 14:01:29 stream closed
2017/03/22 14:02:22 session marked as expired
2017/03/22 14:02:22 connection: client.ip:63642 -> server.ip:4000
2017/03/22 14:02:22 stream opened
2017/03/22 14:02:23 session normally closed
2017/03/22 14:02:32 stream closed
2017/03/22 14:02:32 stream opened
2017/03/22 14:02:42 stream closed
2017/03/22 14:02:42 stream opened
2017/03/22 14:02:52 stream closed
2017/03/22 14:02:52 session marked as expired
2017/03/22 14:02:52 connection: client.ip:51745 -> server.ip:4000
2017/03/22 14:02:52 stream opened
2017/03/22 14:02:53 session normally closed
2017/03/22 14:03:02 stream closed
2017/03/22 14:03:08 stream opened
2017/03/22 14:03:10 stream opened
2017/03/22 14:03:10 stream opened
2017/03/22 14:03:10 stream opened

PS, 实际运行时间有几个小时, 日志只是取的是最后几十条. 并且该问题出现后 , 客户端, 服务端均不再输出新的日志.
目前怀疑的点如下:
server
2017/03/22 06:01:57 broken pipe

client
2017/03/22 14:01:29 stream closed
2017/03/22 14:02:22 session marked as expired
2017/03/22 14:02:22 connection: client.ip:63642 -> server.ip:4000
2017/03/22 14:02:22 stream opened
2017/03/22 14:02:23 session normally closed
2017/03/22 14:02:32 stream closed
2017/03/22 14:02:32 stream opened
2017/03/22 14:02:42 stream closed
2017/03/22 14:02:42 stream opened
2017/03/22 14:02:52 stream closed
2017/03/22 14:02:52 session marked as expired
2017/03/22 14:02:52 connection: client.ip:51745 -> server.ip:4000
2017/03/22 14:02:52 stream opened
2017/03/22 14:02:53 session normally closed
2017/03/22 14:03:02 stream closed
2017/03/22 14:03:08 stream opened
2017/03/22 14:03:10 stream opened
2017/03/22 14:03:10 stream opened
2017/03/22 14:03:10 stream opened

不知是我遗漏了什么, 还是有什么办法可以修复该问题, 多谢!
UPDATE: 我这次又确认了一下, 重启客户端即可恢复.

可以试试最新的看有没有解决，可能是ISP的问题，也可能是某个bug导致的。

@xtaci OK
我现在已经在使用0322版本. 先观察. 不出意外今明两天可以反馈结果.

我也遇到这个问题，频繁出现session marked as expired,session normally closed，用的是20170322版本

session marked as expired
session normally closed
session reached scavenge ttl

都是由于-autoexpire设置产生的正常连接切换中断。

@xtaci 但是你可以看看我的启动参数. 应该没设置-autoexpire
那么应该是使用默认的 -autoexpire 0 吧?

没有设置就是真的连接中断的。

-l xxx.xxx.xxx.xxx:9527 -r xxx.xxx.xxx.xxx:555 -key "xxxxxx" -crypt salsa20 -nocomp true -mtu 1350 -sndwnd 245 -rcvwnd 614 -mode fast3，我就是这几个参数，也没有用到-autoexpire

还有个可能。
检查一下iptables是否有影响建立链接的选项。


Add example queries to README or wiki

For people like me who never used grafana nor prometheus before it should be helpful if you added some of your queries that you used for the dashboard screenshot.
For instance, here's two of mine that are part of this panel:

rate(factorio_item_production_output{name="high-tech-science-pack"}[2m])*100

(factorio_item_production_output{name="high-tech-science-pack"} - (factorio_item_production_output{name="high-tech-science-pack"} offset 1m)) * (60 / 36)

The latter query has this weird factor to compensate for my reduced UPS (approximately 36 UPS instead of 60). But this is another issue.
@afex I can file a PR with some of my queries if you want

I would really really appreciate any examples you can provide... This is my first grafana experience.

any example queries are welcome! if you can, provide some context on whether they are more useful for early or late-game factories.


按钮类型警告type.text is about to be deprecated in version 3.0.0, please use link instead.

ElementPlusError: [props] [API] type.text is about to be deprecated in version 3.0.0, please use link instead.
For more detail, please visit: https://element-plus.org/en-US/component/button.html#button-attributes
at debugWarn (chunk-YSZGQ4FE.js?v=57964185:1435:37)
at watch.immediate (chunk-YSZGQ4FE.js?v=57964185:1946:7)
at callWithErrorHandling (chunk-VDTT4JEB.js?v=57964185:1881:19)
at callWithAsyncErrorHandling (chunk-VDTT4JEB.js?v=57964185:1888:17)
at job (chunk-VDTT4JEB.js?v=57964185:7254:9)
at doWatch (chunk-VDTT4JEB.js?v=57964185:7292:7)
at watch (chunk-VDTT4JEB.js?v=57964185:7119:10)
at useDeprecated (chunk-YSZGQ4FE.js?v=57964185:1944:3)
at useButton (chunk-YSZGQ4FE.js?v=57964185:11758:3)
at setup (chunk-YSZGQ4FE.js?v=57964185:12840:84)

这个能升级去掉吗？ 一直在提示

已修复


Exclude test files from compilation but include for plugin processing

My tsconfig file currently looks like this
{
    "compilerOptions": {
        "alwaysStrict": true,
        "noImplicitAny": true,
        "noImplicitThis": true,
        "strictNullChecks": true,
        "noUnusedParameters": true,
        "noEmitOnError": true,
        "noUnusedLocals": true,
        "declaration": false,
        "target": "es2015",
        "baseUrl": ".",
        "paths": {
            "*": [
                "src/*"
            ]
        },
        "moduleResolution": "node",
        "lib": ["es6", "dom"]
    },
    "exclude": [
        "node_modules",
        "dist",
        "**/tests/*.test.ts",
        "src/tests"
    ]
}

And my code is setup where my unit test files are located in a tests directory as a sibling of the source file, e.g.
/lib
   /tests
      Utils.test.ts
  Utils.ts

When I compile my code the current setup works find and ignores all unit test files during compilation. However, when I open the unit test files in Sublime with this configuration it can't find any of the global types that it should find from jasmine/karma/etc.

If I remove the unit test file from the exclude list in tsconfig, then it all starts working again.
Is there a way to exclude files from TS compilation but still have the plugin process them correctly?

You will need a separate tsconfig.json that includes your test files along with the necessary compiler options and files to build the appropriate context. They are excluded in the above project, so TypeScript will effectively treat them as standalone files when opened.

It the problem only applies for jest, you can add this to your jest config:
"jest": {
    "testPathIgnorePatterns": [
      "<rootDir>/build/",
      "<rootDir>/node_modules/"
    ]
}

For more info on working with multiple tsconfig.json files, see this StackOverflow answer. Basically you'd make use of the "extends" field so as to not duplicate your compiler options overmuch.


Update quick start

Docs Build status updates of commit af4b4f5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

azure-fluid-relay-preview-pr/articles/quickstarts/fluid-quickstart.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit d39519b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

azure-fluid-relay-preview-pr/articles/quickstarts/fluid-quickstart.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 5b14c41:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

azure-fluid-relay-preview-pr/articles/quickstarts/fluid-quickstart.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Witch available at level up even when turned off

I'm not sure if this needs to be fixed here or in the multiclas mod.

Multiclass. Easy fix

It’s fixed on MC and will be there in next release.


Problem when downloading from tumblr.com

On certain blogs downloading images is not available, and I can download them in one picture.
Downloading from the cache is enabled.
I'm logged in on the site.
For example http://mrsnakestone.tumblr.com/post/174704048956/mrsnakestone-just-some-quick-snarti-pics-yarti
In this case, another extension (Download Star) sees links to these pictures.
Version Firefox 62.0a1

Those images are displayed in frames. To download them with the batch download, turn on the advanced option "Collect images from frames recursively".