Archmage armor not working.

Archmage armor is implied to only work when self cast. Can probably be fixed by prioritizing spells to be cast by the targeted character then first available.

Are you saying there are cases where the mod is allowing you to cast archmage armor on someone else?
Can I have a screenshot please?

Archmage armor is not a separate spell from mage armor but a modification of it when self cast.
Say I have 3 characters who all can cast mage armor and have the archmage armor trait. When the buff is cast the first character will have the extra ac from the trait but the other 2 will only have the base 4.

In BubbleBuffs it will appear as a separate spell that is locked to self cast.


Updating Itineraries

I have added the code to update Itineraries and viewing the updated itineraries.

Can we get a button from the itineraries page that can take us to the add itinerary page? And then probably some sort of navigation from the add itinerary page?

Justin, i have created links to and from the create itinerary page, delete itinerary page and itineraries page and have created a new PR for that. please check it out!


Please export format.dart in layout.dart

Without this it is not possible to create a custom layout format
version 1.0.2

Is the issue still on ?


mark non-self-hostable software as SaaS, non-Free software with ©

fixes https://github.com/onurakpolat/awesome-analytics/issues/94
https://github.com/onurakpolat/awesome-analytics/issues/93

ping @koconder @jtagcat

thanks

thanks


Enable cmake target configuration

@marcel-behlau-elfin ,
The PR contains errors.
https://github.com/redboltz/mqtt_cpp/pull/632/checks?check_run_id=741451173#step:6:15
It seems that the errors are caused by #633 issue.
I just reverted #623.
Could you rebase your PR from be71a5d7acd60bc57d3c0a2b7f1399db19df4428 ?
I guess that the CI error would be disappeared.

@marcel-behlau-elfin , thank you for updating!


Workspace command not evaluating local files - using "chat model gpt-3.5-turbo"

VS Code Version: 1.85.1
OS Version: Version	10.0.19045 Build 19045

When using @workspace, I am not getting back any relevant results based on my local code. The code is identified correctly when gathering references, but I am then told that it cannot access my files. Copilot Chat appears to use ChatGPT 4 until the final response, where it uses [chat fetch] chat model gpt-3.5-turbo.
2 examples:

Logs:
2024-01-08 16:57:21.203 [info] [gitExtensionService] Initializing Git extension service.
2024-01-08 16:57:21.203 [info] [gitExtensionService] Successfully activated the vscode.git extension.
2024-01-08 16:57:21.203 [info] [gitExtensionService] Enablement state of the vscode.git extension: true.
2024-01-08 16:57:21.203 [info] [gitExtensionService] Successfully registered Git commit message provider.
2024-01-08 16:57:22.988 [info] [auth] Logged in as K2Designs
2024-01-08 16:57:23.688 [info] [chat] copilot token chat_enabled: true
2024-01-08 16:57:23.689 [info] [githubTitleAndDescriptionProvider] Initializing GitHub PR title and description provider provider.
2024-01-08 16:57:23.690 [info] [githubTitleAndDescriptionProvider] GitHub.vscode-pull-request-github extension is not yet activated.
2024-01-08 16:57:23.690 [info] [auth] Got Copilot token for K2Designs
2024-01-08 16:57:23.817 [info] [auth] Logged in as K2Designs
2024-01-08 16:57:23.821 [info] [chat] copilot token chat_enabled: true
2024-01-08 16:57:23.821 [info] [auth] Got Copilot token for K2Designs
2024-01-08 16:57:47.504 [info] [chat fetch] engine https://api.githubcopilot.com/chat
2024-01-08 16:57:47.504 [info] [chat fetch] modelMaxTokenWindow 4096
2024-01-08 16:57:47.504 [info] [chat fetch] chat model gpt-4
2024-01-08 16:57:49.437 [info] [chat fetch] request.response: [https://api.githubcopilot.com/chat/completions], took 1931 ms
2024-01-08 16:57:53.575 [info] [streamMessages] message 0 returned. finish reason: [stop]
2024-01-08 16:57:53.577 [info] [streamChoices] request done: requestId: [92d3c6af-b89d-48af-a1b9-44b4f752313e] responseId: [b9402097-7ef4-4472-ab70-218940bb2c3d] model deployment ID: [x74a4b0e7ace1]
2024-01-08 16:58:05.986 [info] [chat fetch] engine https://api.githubcopilot.com/chat
2024-01-08 16:58:05.986 [info] [chat fetch] modelMaxTokenWindow 4096
2024-01-08 16:58:05.986 [info] [chat fetch] chat model gpt-4
2024-01-08 16:58:07.369 [info] [chat fetch] request.response: [https://api.githubcopilot.com/chat/completions], took 1382 ms
2024-01-08 16:58:12.249 [info] [streamMessages] message 0 returned. finish reason: [stop]
2024-01-08 16:58:12.250 [info] [streamChoices] request done: requestId: [fac3cd94-6c38-4af9-b60f-8d7ea88dfc16] responseId: [a68dd6b1-8a88-48e0-85a5-54cdfcfe1b00] model deployment ID: [x74a4b0e7ace1]
2024-01-08 16:58:12.288 [info] [chat fetch] engine https://api.githubcopilot.com/chat
2024-01-08 16:58:12.289 [info] [chat fetch] modelMaxTokenWindow 8192
2024-01-08 16:58:12.289 [info] [chat fetch] chat model gpt-3.5-turbo
2024-01-08 16:58:13.101 [info] [chat fetch] request.response: [https://api.githubcopilot.com/chat/completions], took 811 ms
2024-01-08 16:58:13.674 [info] [streamMessages] message 0 returned. finish reason: [stop]
2024-01-08 16:58:13.675 [info] [streamChoices] request done: requestId: [c97028dc-3f7a-4931-bad7-c0b5edd33c81] responseId: [dcd11ce0-da0b-4c9a-9d8e-7df9186fdd43] model deployment ID: [x338b9c029b38]

Logs:
2024-01-08 17:06:53.961 [info] [chat fetch] engine https://api.githubcopilot.com/chat
2024-01-08 17:06:53.961 [info] [chat fetch] modelMaxTokenWindow 4096
2024-01-08 17:06:53.961 [info] [chat fetch] chat model gpt-4
2024-01-08 17:06:56.462 [info] [chat fetch] request.response: [https://api.githubcopilot.com/chat/completions], took 2499 ms
2024-01-08 17:07:00.355 [info] [streamMessages] message 0 returned. finish reason: [stop]
2024-01-08 17:07:00.357 [info] [streamChoices] request done: requestId: [53ffba69-4662-441b-b559-dc538c8b6aa5] responseId: [6ad6f25e-3d43-4e51-aaf6-2bf98c8b6453] model deployment ID: [x74a4b0e7ace1]
2024-01-08 17:07:04.265 [info] [chat fetch] engine https://api.githubcopilot.com/chat
2024-01-08 17:07:04.265 [info] [chat fetch] modelMaxTokenWindow 4096
2024-01-08 17:07:04.265 [info] [chat fetch] chat model gpt-4
2024-01-08 17:07:05.740 [info] [chat fetch] request.response: [https://api.githubcopilot.com/chat/completions], took 1475 ms
2024-01-08 17:07:11.904 [info] [streamMessages] message 0 returned. finish reason: [stop]
2024-01-08 17:07:11.905 [info] [streamChoices] request done: requestId: [977f41af-9762-4d9f-bc81-164cdab8e456] responseId: [d36aab12-4cce-45b1-b74d-f2bd4f1e1168] model deployment ID: [x74a4b0e7ace1]
2024-01-08 17:07:11.924 [info] [chat fetch] engine https://api.githubcopilot.com/chat
2024-01-08 17:07:11.924 [info] [chat fetch] modelMaxTokenWindow 8192
2024-01-08 17:07:11.925 [info] [chat fetch] chat model gpt-3.5-turbo
2024-01-08 17:07:14.132 [info] [chat fetch] request.response: [https://api.githubcopilot.com/chat/completions], took 2207 ms
2024-01-08 17:07:15.741 [info] [streamMessages] message 0 returned. finish reason: [stop]
2024-01-08 17:07:15.743 [info] [streamChoices] request done: requestId: [7d6c3a52-ac7f-45f9-b402-7fdca9973cc2] responseId: [2c8205c6-527d-48e1-8b0f-1e50a232831b] model deployment ID: [x338b9c029b38]

Difficult to investigate this without an example project to try out. However since this was opened we've fixed a number of issues about how context from the workspace is included and also switched to improved models
If you're still seeing issues with the current release, please share an example workspace and question so we can try looking into the issue


LBN tempalte TS app to BTP CF migration

Migration result app UI Preview:

With Dynamic App Launcher UI Preview:


centos安装扩展失败

编译最后一步
sudo make && make install
In file included from /usr/local/src/php-ext-excel-export/library/third_party/minizip/zip.c:186:
/usr/local/src/php-ext-excel-export/library/third_party/minizip/crypt.h:35: error: expected ‘;’, ‘,’ or ‘)’ before ‘*’ token
/usr/local/src/php-ext-excel-export/library/third_party/minizip/crypt.h:48: error: expected ‘;’, ‘,’ or ‘)’ before ‘*’ token
/usr/local/src/php-ext-excel-export/library/third_party/minizip/crypt.h:65: error: expected ‘;’, ‘,’ or ‘)’ before ‘*’ token
/usr/local/src/php-ext-excel-export/library/third_party/minizip/crypt.h:94: error: expected ‘;’, ‘,’ or ‘)’ before ‘*’ token
/usr/local/src/php-ext-excel-export/library/third_party/minizip/zip.c: In function ‘zipOpenNewFileInZip4_64’:
/usr/local/src/php-ext-excel-export/library/third_party/minizip/zip.c:1245: error: ‘curfile64_info’ has no member named ‘crypt_header_size’
/usr/local/src/php-ext-excel-export/library/third_party/minizip/zip.c:1251: error: ‘curfile64_info’ has no member named ‘pcrc_32_tab’
/usr/local/src/php-ext-excel-export/library/third_party/minizip/zip.c:1254: error: ‘curfile64_info’ has no member named ‘pcrc_32_tab’
/usr/local/src/php-ext-excel-export/library/third_party/minizip/zip.c:1255: error: ‘curfile64_info’ has no member named ‘crypt_header_size’
/usr/local/src/php-ext-excel-export/library/third_party/minizip/zip.c: In function ‘zip64FlushWriteBuffer’:
/usr/local/src/php-ext-excel-export/library/third_party/minizip/zip.c:1375: error: ‘curfile64_info’ has no member named ‘pcrc_32_tab’
/usr/local/src/php-ext-excel-export/library/third_party/minizip/zip.c:1375: error: ‘curfile64_info’ has no member named ‘pcrc_32_tab’
/usr/local/src/php-ext-excel-export/library/third_party/minizip/zip.c: In function ‘zipCloseFileInZipRaw64’:
/usr/local/src/php-ext-excel-export/library/third_party/minizip/zip.c:1610: error: ‘curfile64_info’ has no member named ‘crypt_header_size’
make: *** [library/third_party/minizip/zip.lo] Error 1

环境
PHP 7.2.13 (cli) (built: Dec  8 2018 12:27:01) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.2.0, Copyright (c) 1998-2018 Zend Technologies
with Zend OPcache v7.2.7, Copyright (c) 1999-2018, by Zend Technologies
rinting-4.0-noarch
Distributor ID:	CentOS
Description:	CentOS release 6.7 (Final)
Release:	6.7
Codename:	Final

zlib 依赖是否安装？

这个安装过的。
发自我的iPhone
------------------ 原始邮件 ------------------
发件人: viest<EMAIL_ADDRESS>发送时间: 2019年6月30日 15:25
收件人: viest/php-ext-excel-export<EMAIL_ADDRESS>抄送: needrunning<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>主题: 回复：[viest/php-ext-excel-export] centos安装扩展失败 (#134)
zlib 依赖是否安装？
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

On CentOS, don't build from sources, simply use https://rpms.remirepo.net/
Which have nearly all extensions available, including this one.

@remicollet  👍

@remicollet 👍

看了链接 不太明白啊 那如何解决这个扩展安装失败问题？

@needrunning
https://rpms.remirepo.net/wizard/
选择你的系统版本、PHP版本、安装类型，下面会生成一个使用向导。

@needrunning  我将重新开启这个 issues ，待解决时关闭。

Would be nice to use english....

@remicollet
I will create a new issue to guide the user to use https://rpms.remirepo.net/

@needrunning
Has your problem been solved?

@needrunning
Has your problem been solved?

@needrunning
Has your problem been solved?

I'm working on something that hasn't been solved yet

@needrunning
Has your problem been solved?

now I have two problems
one：    in order to install pxlswriter  via pecl install pxlswriter,  Do you need to reinstall PHP？
two： I have  runed     pecl install pxlswriter  in my server ，
As shown below
lude/php -I/usr/include/php/main -I/usr/include/php/TSRM -I/usr/include/php/Zend -I/usr/include/php/ext -I/usr/include/php/ext/date/lib -I/tmp/pear/install/xlswriter/library/include -I/tmp/pear/install/xlswriter -I/tmp/pear/install/xlswriter/include -DHAVE_CONFIG_H -g -O2 -c /tmp/pear/install/xlswriter/library/third_party/minizip/zip.c  -fPIC -DPIC -o library/third_party/minizip/.libs/zip.o
/tmp/pear/install/xlswriter/library/third_party/minizip/zip.c:160: error: expected ‘:’, ‘,’, ‘;’, ‘}’ or ‘attribute’ before ‘’ token
In file included from /tmp/pear/install/xlswriter/library/third_party/minizip/zip.c:186:
/tmp/pear/install/xlswriter/library/third_party/minizip/crypt.h:35: error: expected ‘;’, ‘,’ or ‘)’ before ‘’ token
/tmp/pear/install/xlswriter/library/third_party/minizip/crypt.h:48: error: expected ‘;’, ‘,’ or ‘)’ before ‘’ token
/tmp/pear/install/xlswriter/library/third_party/minizip/crypt.h:65: error: expected ‘;’, ‘,’ or ‘)’ before ‘’ token
/tmp/pear/install/xlswriter/library/third_party/minizip/crypt.h:94: error: expected ‘;’, ‘,’ or ‘)’ before ‘*’ token
/tmp/pear/install/xlswriter/library/third_party/minizip/zip.c: In function ‘zipOpenNewFileInZip4_64’:
/tmp/pear/install/xlswriter/library/third_party/minizip/zip.c:1245: error: ‘curfile64_info’ has no member named ‘crypt_header_size’
/tmp/pear/install/xlswriter/library/third_party/minizip/zip.c:1251: error: ‘curfile64_info’ has no member named ‘pcrc_32_tab’
/tmp/pear/install/xlswriter/library/third_party/minizip/zip.c:1254: error: ‘curfile64_info’ has no member named ‘pcrc_32_tab’
/tmp/pear/install/xlswriter/library/third_party/minizip/zip.c:1255: error: ‘curfile64_info’ has no member named ‘crypt_header_size’
/tmp/pear/install/xlswriter/library/third_party/minizip/zip.c: In function ‘zip64FlushWriteBuffer’:
/tmp/pear/install/xlswriter/library/third_party/minizip/zip.c:1375: error: ‘curfile64_info’ has no member named ‘pcrc_32_tab’
/tmp/pear/install/xlswriter/library/third_party/minizip/zip.c:1375: error: ‘curfile64_info’ has no member named ‘pcrc_32_tab’
/tmp/pear/install/xlswriter/library/third_party/minizip/zip.c: In function ‘zipCloseFileInZipRaw64’:
/tmp/pear/install/xlswriter/library/third_party/minizip/zip.c:1610: error: ‘curfile64_info’ has no member named ‘crypt_header_size’
make: *** [library/third_party/minizip/zip.lo] Error 1

There is 2 ways
1/ build everything from sources (php, libraries, extensions...)
notice : "pecl install" is building from sources
2/ use the package manager and rely on a good packages provider
How was installed you PHP ?
Using "remi" is the most easy way (and the only provider for CentoOS 6)
Nothing need to be built from sources
yum install php-pecl-xlswriter

@viest BTW, I confirm that building from sources xlswriter using bundled library doesn't work on old C6 with old compiler an old system tools / libraries.
C6 is now terrible old (9 years), and will be EOL in a few months (Nov 220).
RPM packages build fine on C6, but only use the system library which is built separately, with another build system, which probably detect more needed compatibility options.

@remicollet  The serious backwardness of the CentOS version is indeed a problem.

@remicollet   I will post an emergency fix version 1.2.6

The serious backwardness of the CentOS version is indeed a problem.

https://twitter.com/RemiCollet/status/903155214441738240  ;)

@remicollet  Thank you for your contribution 👍


Support UNC paths in xRemoteFile

I'd like xRemoteFile to be able to download to a UNC path.

PowerShell DSC resource MSFT_xRemoteFile  failed to execute Set-TargetResource functionality with error message: Specified DestinationPath is not valid: "\VBOXSVR\buildprovisioning\bin\advinst.msi". DestinationPath should be local path instead
of UNC path.

Hi,
Could you tell me what is the scenario you are trying to accomplish?
Do you want to specify UNC path on the local machine for some reason?
Or you want to specify UNC path to point DestinationPath to the remote node?

Sure. I want to download from the Internet to a shared folder accessed via UNC path.
I'm in the process of converting a provisioning script to DSC. I have several VMs that share a folder. The first VM to be configured downloads some large install media to the shared folder and runs the media. Then, subsequent VMs can skip the download to save time/bandwidth. I'm using VirtualBox's shared folders, which are accessible via UNC path by default.

@JVimes: Either I'm missing something or youre not using the resource correctly.
For start, the error message should have said "\VBOX.." so i hope thats not a mistype from your side on the DesitnationPath. Never the less the resource description states: "ensures the presence of remote files on a local machine". From my understanding, this resource would make sure a file on a share will be compared to a file on the local machine and if needed it will be downloaded localy.
Taking your example, if you download the file from the share localy to the vm and then run it from the local folder, then you can use this resource to make sure each vm will have a copy localy of the installation. Since you want to avoid that all together, if that share was on a VM of its own, as in a VM running a Windows OS, then you can use this resouce to download the installation from the web to the local folder (that has the share on it). Then from each VM you can use other commands to run the installation from that share, but theres no use for this resource in that case.

The resource description can and should be changed if it makes the resource better. Supporting UNC paths would make it better. It is a reasonable use case.
The install media I'm downloading is about 4 GB, so downloading multiple times is not an option.
There was a second slash in my config, as evidenced by the error message.

The main reason UNC paths are not supported is that resource should be configuring state of the current node. We download remote file on the local machine, thus changing it's state. If we were downloading the file onto another machine, we would be changing state of the other machine instead.
The workaround for your scenario would be what @ArieHein proposed - use xRemoteFile on VM hosting the share to download remote file to the local folder (which is shared), then access it from all other VMs.

If a resource finds that its state already exists, it just moves on. So the
subsequent VMs will find that the file is already in the destination and
keep going. This seems like a perfectly fine scenario for desired state
configuration. The destination state is shared between VMs, as is the
configuration.
It's unnecessarily complicated to make my script span both the VM host and
the VM's. And it's not necessary. The shared folder is conceptually part of
the guests and not the host. The host does not make use of that folder.
On Nov 18, 2015 7:31 PM, "KarolKaczmarek"<EMAIL_ADDRESS>wrote:

The main reason UNC paths are not supported is that resource should be
configuring state of the current node. We download remote file on the local
machine, thus changing it's state. If we were downloading the file onto
another machine, we would be changing state of the other machine instead.
The workaround for your scenario would be what @ArieHein
https://github.com/ArieHein proposed - use xRemoteFile on VM hosting
the share to download remote file to the local folder (which is shared),
then access it from all other VMs.
—
Reply to this email directly or view it on GitHub
https://github.com/PowerShell/xPSDesiredStateConfiguration/issues/44#issuecomment-157908845
.

@JVimes: "If a resource find that its state..."  its not the resource state, its the node state. Since the share isnt on a "node" but a general share, theres no state as theres no node. If the share was on a VM running windows OS for example then yes, you could have used this resource on the script that runs on that node.
I do think your requirement is valid but just not using the right resource. Maybe a cadidate for writing a custom resource or just adding something like this: https://gallery.technet.microsoft.com/scriptcenter/files-from-websites-4a181ff3

Conceptually, the share is part of the node. I think you're being idealistic at the expense of usefulness. But I'm not going to keep arguing. I gave up on DSC for a few reasons, this only being one of them. Best of luck with it.

Sorry to hear that. If you would like to discuss those reasons, we would be glad to hear that. Microsoft Connect is good place for general DSC requests/bugs: https://connect.microsoft.com/PowerShell


Bump dependencies as much as possible

js-yaml, minimatch and node-fetch are not upgraded to their latest major
releases as they all break tests in one way or another.

One can hope. Only trying to deploy will really tell if things still work after all the recent changes.


Send a reload command to the webserver

Sending a restart means we have the possibility of dropping requests, which is bad news bears :(

Thanks for your contribution @josegonzalez!
Kind regards,
David

<3 :)


[application-layout] Accessibility issues

Bug Report
Description
The application layout component has started getting accessibility issues when tested with updated dependencies. The error is there are <img> tags without alt attributes.
It seems some dependency has updated which is triggering errors because this issue has just started occurring and happens on master branch.
Steps to Reproduce

Change to master branch on git
NPM install or clean:install to update dependencies
Run webdriver tests on application layout

Closed in cerner/terra-core #1719


pagination - test file generation

"create_large_fb_index.py" is in branch feature/paging. It creates a large test file in JSON line format in /test. Execute  $ python create_large_fb_index.py -h to learn more. Use that index in a development environment, such as "kibana", to implement the ES search_after method.


IndexOutOfBounds in XlsxWorkbookReader

I've a file here (that I cannot supply publicly, but can work out a way to provide if needed) that causes EDR to throw an IOOB from the constructor for the EDR:

The xfselem doesn't have a count attribute, so this ends up with c as 0, and the xfMap is 0 long. I'm wondering if an alternative value for c could sensibly be xfsElem.ChildNodes.Count ?
The file itself has some issues, but I'm raising a spearate ticket for a feature request for those

Got the file. I agree with your analysis. I think that completely ignoring the count attribute and just using the child node count is the correct fix. Are you interested in submitting a PR? Or should I just fix it myself?
There is a subsequent issue with the file. The sheet data has inlineStr cells that don't contain any content which I've never seen before. Must be a quirk of the JasperReports tool that created this, and also easy enough to fix it.

I realize now I did also note that second problem too; i just commented out the throw and went about my work, forgetting to report it. The workaround I've been using to date was to delete the two blank lines at the head of the file, then re-save in Excel, which probably fixed things up somehow so I experienced neither problem..
Can sub a PR for the first one; are you taking the second or do you want me to roll something in (and what is sensible? string.Empty?) ?

Yep, I set the value to string.empty, and set the cell type to null. If you want to roll it all into once PR that works.


Certificate revocation returns 403

1. What version of Caddy are you using (caddy -version)?
Caddy 0.11.0
2. What are you trying to do?
I was trying to revoke a certificate because private key might have been compromised.
3. What is your entire Caddyfile?
n/a
4.  Please paste any relevant HTTP request(s) here.
n/a
6. What did you expect to see?
Confirmation of revocation.
7. What did you see instead (give full error messages and/or log)?
Error 403 - urn:ietf:params:acme:error:unauthorized - The key ID specified in the revocation request does not hold valid authorizations for all names in the certificate to be revoked

8. How can someone who is starting from scratch reproduce the bug as minimally as possible?
Get a cert and try to revoke it.

Revocation isn't implemented in our ACMEv2 library yet.


It takes up to 5 minutes to see a new secret synced after creation

Describe the solution you'd like
It takes up to 5 minutes to see a new secret synced after creation. It also takes longer than the set 60s (for example) to sync existing secrets.
What is the added value?
Immediate availability of the secrets
Give us examples of the outcome
Observations (Constraints, Context, etc):
ESO installed with Helm chart version 0.4.3, K8s version 1.21.9. Issue exists regardless of which secret store is used, in this example we have Vault running on a separate AWS account.
Example secret template:
apiVersion: external-secrets.io/v1alpha1
kind: ExternalSecret
metadata:
  name: nexus-testl
  namespace: default
spec:
  refreshInterval: "60s"
  secretStoreRef:
    name: vault-backend
    kind: ClusterSecretStore
  target:
    name: nexus-credential
    template:
      type: kubernetes.io/dockerconfigjson
  data:
  - secretKey: .dockerconfigjson
    remoteRef:
      key: k8s-management/nexus
      property: nexus-credential

Manifest applied to the cluster at 12:41 but secret only synced at 12:46. No sync_call errors seen on the pod, after around 5 minutes the container just shows secret is created:
kubectl logs external-secrets-77b4b66f75-lptxn -n external-secrets
{"level":"info","ts":1651578279.372186,"logger":"controllers.ExternalSecret","msg":"reconciled secret","ExternalSecret":"default/my-secret","SecretStore":"/vault-backend"}
{"level":"debug","ts":1651578279.3722456,"logger":"events","msg":"Normal","object":{"kind":"ExternalSecret","namespace":"default","name":"my-secret","uid":"adfec3be-85f7-41f8-beec-9f16dbd54aff","apiVersion":"external-secrets.io/v1alpha1","resourceVersion":"331853"},"reason":"Updated","message":"Updated Secret"}

kubectl get externalsecrets.external-secrets.io
NAME        STORE           REFRESH INTERVAL   STATUS
my-secret   vault-backend   60s

➜  ~ kubectl get externalsecrets.external-secrets.io
NAME        STORE           REFRESH INTERVAL   STATUS
my-secret   vault-backend   60s                SecretSynced

Any indication of why it is taking several minutes to create the secrets?

Hi @nausicaaonacids ! Can you share your ClusterSecretStore definition as well?

Hi @gusfcarvalho, please see below:
apiVersion: external-secrets.io/v1alpha1
kind: ClusterSecretStore
metadata:
  name: vault-backend
spec:
  provider:
    vault:
      caBundle: "###"
      server: $VAULT_ADDR
      path: 'kv'
      version: 'v2'
      auth:
        # VaultAppRole authenticates with Vault using the
        # App Role auth mechanism
        # https://www.vaultproject.io/docs/auth/approle
        appRole:
          # Path where the App Role authentication backend is mounted
          path: 'approle'
          # RoleID configured in the App Role authentication backend
          roleId: $EXT_SECRETS_VAULT_ROLE_ID
          # Reference to a key in a K8 Secret that contains the App Role SecretId
          secretRef:
            name: 'external-secrets-approle'
            key: 'secret-id'
            namespace: $VAULT_SECRETS_OPERATOR_NAMESPACE

It is possible to attach a strace probe to the external-secrets pod (you can do it by accessing the node where the pod is running)? This seems to be somewhat difficult to troubleshoot from the manifests only.


Tableau starts flickering with certain formatting settings in combination with any extension

Hi,
I have been investigating an issue of one our customers, they reported that their dashboards started to flicker when they upgraded their Tableau Desktop environment on Mac (intel).
I compared on XML level the difference between a working and non working dashboard and found out that if you put a background color on the tiled container, the whole dashboard starts to bug and elements become invisible until you hover over them, and it keeps repeating itself. See attached video.
The behaviour disappears whenever you remove the background color from the tiled container.
Version information:

Tableau Desktop version: 2021.3
OS: Mac OS Monterey
Browser .
Version .

Steps to reproduce (please include a code snippet, if possible):
See video
https://user-images.githubusercontent.com/16118919/149118236-99eca620-5ed1-4535-b657-cc37bdb921ed.mov

Hi Merlijn
This is pretty crazy. Thanks for the video. I have reproduced the issue in 2021.3, but it looks like it was fixed in 2021.4 and (the upcoming) 2022.1. I've reached out to the team that would own this to see if they can give us any more information. I'll post more here when I get the reply.
John

Merlijn:
An update. The issue is not fixed in 2021.4 and 2022.1. It just takes a little more effort to manifest itself. The team is investigating the cause. I'll update again when I have more information.
John

Logged as defect #1364779

The issue manifests itself with QWebEngine software rendering. Right now, it looks like it is fixed in the upcoming 2022.2, but the team is still narrowing it down and investigating if it could be included in a maintenance release.

Hi Merlijn:
Just following up. This has been fixed in the upcoming 2022.2 because of an update to our internal Qt version. As I mentioned earlier, it still happens in 2021.4 and 2022.1, but appears to only happen with a WebPage object added to the dashboard.
Meanwhile, there is a work-around, but becomes harder with the complexity of the dashboard. Do not have background tiled objects with color, just put them as filler around the extension and/or webpage zone. These can be colored without any problem.
John


Bump version to 0.5.1 ?

Thanks for merge.
Could you release 0.5.1 with latest commit?
I know that there is no change in source,
but last digit would fit with .ignore change.
My purpose is to change ReactiveKit/Bond podspec to depend on 0.5.1
so that no more git dirty state after just running carthage update in Bond.
(I'm not a author of Bond, just wanna make contributors like me feel better)
Thanks for great library!

You can do it now! 👍 but sure, I can do it, too later in the day.

I don't have any prior experience related with Github release process, so this is my first try.
I created a release in my fork at https://github.com/jechol/Diff.swift/releases,
what should I do from here?
It would be great if I can release this myself.

please wait for this and associated PR to be merged.
Update version in the podspec to point to 0.5.1 and create a PR (please include [ci skip] in the commit message to avoid rebuilding it on travis (like [ci skip] version 0.5.1).
Create a release on github just like you made in your repository, but here.

Afterwards I'll push the pod spec.

Oh, and please accept my invite for you to be a Collaborator.

fixed in #36

My purpose is to change ReactiveKit/Bond podspec to depend on 0.5.1

I'll take care of that - just battling Travis CI at the moment. When it's passing, I'll get it into master.

If you mean battling Travis here, then I'd let go. Non deterministic, failing builds are annoying but the issue is apparently within travis/simulator. This repo is relatively calm so restarting one or two jobs a week doesn't bother me this much.
Of course any contribution is welcome but I'm worried that it's just a waste of time.

No, no, I'm battling it over on Bond's repo right now. Error 65 😑
I'm using their travis_retry workaround - I'll let you know how it goes.

This also seems promisisng

@tonyarnold I would appreciate if you would handle the upgrading to 0.5.1. Thanks.

Bond has been updated to include v0.5.1: https://github.com/ReactiveKit/Bond/pull/357

Great!
On Fri, 13 Jan 2017 at 6:32 AM Tony Arnold<EMAIL_ADDRESS>wrote:

Bond has been updated to include v0.5.1: ReactiveKit/Bond#357
https://github.com/ReactiveKit/Bond/pull/357
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/wokalski/Diff.swift/issues/35#issuecomment-272290438,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAwh9cBOBS2zvgFpPSJqsz3V1gHAtAI4ks5rRpwAgaJpZM4Lhi_J
.


Is there any misinformation?

For example, I had a java project which speified jackson-databind version to <IP_ADDRESS> in the pom.xml, but the report still showed me a jar called jackson-mapper-asl-1.9.11.jar with jackson-databind cve below 2.8.x, so I wonder if it's a false positive or just some deep checking mechanism into the jars? Here are my report and some key infos
https://github.com/Q5EbA7Vdyw84efER/myreport

jackson-mapper-asl-1.9.11.jar
Description:
Data Mapper package is a high-performance data binding package
built on Jackson JSON processor
License:
The Apache Software License, Version 2.0: http://www.apache.org/licenses/LICENSE-2.0.txt
File Path: /mnt/sonarshell/projects/udesk-fever-framework_0.0.3/fever-metrics/target/dependency/jackson-mapper-asl-1.9.11.jar
MD5: 8f10143a94de3e786dd53db10fa54598
SHA1: 45d70862fa016993193075a1e8e32a01dcf438e8
SHA256:246ee4dcb26cb040608eab5d978efe2618564568923c0a98e6118f8858b31def
Evidence
Identifiers
<EMAIL_ADDRESS>(Confidence:High)
cpe:2.3:a:fasterxml:jackson:1.9.11:::::::*  (Confidence:High)  suppress
cpe:2.3:a:fasterxml:jackson-mapper-asl:1.9.11:::::::*  (Confidence:High)  suppress
Published Vulnerabilities
CVE-2017-15095 (OSSINDEX)  suppress
A deserialization flaw was discovered in the jackson-databind in versions before 2.8.10 and 2.9.1, which could allow an unauthenticated user to perform code execution by sending the maliciously crafted input to the readValue method of the ObjectMapper. This issue extends the previous flaw CVE-2017-7525 by blacklisting more classes that could be used maliciously.
CVSSv3:
Base Score: CRITICAL (9.8)
Vector: /AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Likely a false positive. Please see:

How dependency-check works
Reading the report
False positives

After looking at this more - it looks like jackson-mapper-asl-1.9.11.jar is being included somehow in your project.  Possibly via a transitive dependency.
It looks like you are using the CLI to scan the project instead of the maven plugin. I would highly recommend using the maven plugin as it will be more accurate.

After looking at this more - it looks like jackson-mapper-asl-1.9.11.jar is being included somehow in your project.  Possibly via a transitive dependency.
It looks like you are using the CLI to scan the project instead of the maven plugin. I would highly recommend using the maven plugin as it will be more accurate.


kubectl set env not working for initcontainers

What happened:
I'm currently implementing a CI/CD pipeline where I want to initialize a container using an initcontainer image, the initialization is driven by parameters I'd like to pass to the init container as environment variables.
When I execute the command kubectl set env --all=true deployment/my-app --from=configmap/my-configmap the command succeed with output:
deployment.apps/my-app updated
But the initContainer image is not updated and the env vars are not valued.
I attempted to use command:
kubectl set env -c init-image deployment/my-app --from=configmap/my-configmap where init-image is the name of my initcontainer image, but the command failed with output:
warning: deployments/my-app does not have any containers matching "init-image"
What you expected to happen:
Using the --all=true option I expected to be able to set environment variables values for any initcontainer image part of the deployment.
How to reproduce it (as minimally and precisely as possible):
I provide a minimal deployment with a pod complete of image and initcontainer and a configmap with the env var I'd like to set on both images.
To reproduce the issue, apply the deployment:
kubectl apply -f my-app.yaml
Check that the initcontainer logged "blue" as env value and that the container image is continuously logging "blue" as using the same env var.
Perform the following command:
kubectl set env  deployment/my-app --all=true --from=configmap/env-value
Once the image is running, inspecting the log I would expect to read 'red' both into the image and initcontainer logs, however, the initcontainer log is still reporting 'blue': the configmap/env-value was not applied to the initcontainer image.
In the following the sample deployment:
apiVersion: v1
kind: List
items:
- apiVersion: apps/v1
  kind: Deployment
  metadata:
    labels:
      app: my-app
    name: my-app
  spec:
    progressDeadlineSeconds: 600
    replicas: 1
    revisionHistoryLimit: 10
    selector:
      matchLabels:
        deployment: my-app
    strategy:
      rollingUpdate:
        maxSurge: 25%
        maxUnavailable: 25%
      type: RollingUpdate
    template:
      metadata:
        labels:
          deployment: my-app
      spec:
        containers:
        - env:
          - name: SAMPLE_VALUE
            value: blue
          image: alpine:latest
          name: my-app
          command:
          - /bin/sh
          - -c
          - 'while true; do echo $SAMPLE_VALUE; sleep 5; done'
          resources: {}
        initContainers:
        - command:
          - /bin/sh
          - -c
          - echo $SAMPLE_VALUE
          image: busybox
          name: init-image
          env:
          - name: SAMPLE_VALUE
            value: blue
          resources: {}
- apiVersion: v1
  kind: ConfigMap
  metadata:
    labels:
      app: my-app

    name: env-value
  data:
   SAMPLE_VALUE: red

Anything else we need to know?: none
Environment:

Kubernetes client and server versions (use kubectl version): Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.0", GitCommit:"af46c47ce925f4c4ad5cc8d1fca46c7b77d13b38", GitTreeState:"clean", BuildDate:"2020-12-08T17:59:43Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"18+", GitVersion:"v1.18.3+2fbd7c7", GitCommit:"2fbd7c7", GitTreeState:"clean", BuildDate:"2020-10-15T16:25:45Z", GoVersion:"go1.13.4", Compiler:"gc", Platform:"linux/amd64"}
Cloud provider or hardware configuration: on premises Openshift 4.7
OS (e.g: cat /etc/os-release): Current client OS is Windows 10

/triage accepted
Potentially similar work to what was done for set image.

set resources might have a similar issue. Someone should look at this as an umbrella for all set init commands.

/assign

/assign

@SaiHarshaK Sorry, I didn't notify you beforehand


add test find by id

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 82.85%. Comparing base (61684a4) to head (a23d522).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff            @@
##               main      #63   +/-   ##
=========================================
  Coverage     82.85%   82.85%
  Complexity      460      460
=========================================
  Files            40       40
  Lines          1009     1009
=========================================
  Hits            836      836
  Misses          173      173

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


connlib: send candidates in batches where we can

Should decrease connection setup latency slightly.

Needs https://github.com/firezone/firezone/issues/3928 to be able to nicely aggregate the SignalIceCandidate events from snownet into the one from firezone-tunnel where we have a list of candidates.
I think on the snownet level, we should retain a single event for simplicity.


"SampleName" as the new "sample_name"

Looking at other code, it seems like "SampleName" is the header field / column name used in data from the SRA (maybe also ENA then?) If so, it could be convenient to use this as the required attribute in a couple of places where it's checked (off hand, as a Sample attribute, and as a key/column in the sample annotations sheet that looper reads). There's already some groundwork in place that would simplify this transition. Namely, that "sample_name" is stored as a constant, and that there's an alias for the relevant Sample attribute (name for sample_name).

it's a good thought -- and we actually knew this at the very beginning. but we elected to go with underscores anyway, and now I think it's too deep in to change (all looper projects created so far, which is a lot, use sample_name, so there's no going back...)
I think get_geo fixes this for data coming directly from SRA.
so, for better or worse, we have decided that the column names would use lowercase and underscores, and I think that's permanent at this point...

OK

I think get_geo leaves it as "SampleName" (I'm working now with metadata generated by get_geo now), but maybe that's something we could add.

yeah, could be useful.
I thought as a python guru you would be a staunch advocate of sample_name :smile:

Ha I'm getting used to more back-and-forth between Python and R, and just generally seeing more style crossover. You're right, though, a few months ago I probably would've been more adamant about that ;D


More useful error message for invalid device files

Checklist

[ ] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[ ] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[ ] I've read the Contribution Guidelines
[ ] I've updated the documentation if necessary.

Motivation and Context

Description

Testing Steps

@googlebot I signed it!

@googlebot I consent.


Kubernetes/OpenShift Client version conflict

In the bom, we explicitly declare version 2.2.14 for both Kubernetes and OpenShift Client. When using this bom in a booster, there is a conflict with Kubernetes/OpenShift client version 1.4.34 within io.openshift:openshift-test-utils which throws .
Workaround si to explicitly declare version in the booster pom:
    <dependency>
      <groupId>io.fabric8</groupId>
      <artifactId>kubernetes-client</artifactId>
      <version>1.4.34</version>
    </dependency>
    <dependency>
      <groupId>io.fabric8</groupId>
      <artifactId>openshift-client</artifactId>
      <version>1.4.34</version>
    </dependency>

In future, we will replace OpenShiftTestAssistant with Arquillian Cube which has its own solution for version conflicts, see http://arquillian.org/arquillian-cube/#_dealing_with_version_conflicts

I have found a solution which currently works for both boosters and qe tests. We explicitly declare kubernetes/openshift client v 1.4.34 in the bom and we downgrade spring-cloud-kubernetes-core + spring-cloud-starter-kubernetes-netflix to 0.1.4 (that uses kubernetes client 1.4.34):
<version.io.fabric8.kubernetes-client>1.4.34</version.io.fabric8.kubernetes-client>
    <version.io.fabric8.openshift-client>1.4.34</version.io.fabric8.openshift-client>
    <version.io.fabric8.spring-cloud-kubernetes-core>0.1.4</version.io.fabric8.spring-cloud-kubernetes-core>
    <version.io.fabric8.spring-cloud-starter-kubernetes-netflix>0.1.4</version.io.fabric8.spring-cloud-starter-kubernetes-netflix>

This targets beta1 as we need compatibility with OpenShiftTestAssistant (openshift-client v1.4.34).

downgrade

I would prefer that we keep the version 2.x for kubernetes/openshift client as spring cloud kubernetes will be released using version 2.x of the client. As the tests look promising to use Arquillian cube (Openshift/Kubernetes), can we replace the openshiftItAssistant in order to use for bossters, qe and integrationTests version 2.x ? @RadekKoubsky

I am all for version 2.x. However, I have several concerns:

Arquillian Cube works for the spring-boot-http booster
But it is not perfect, see 743. I cannot say how it will work with other boosters, there might (will) be issues.
Replacing OpenShiftTestAssistant with Arquillian Cube
If we successfully replace it in all spring-boot boosters, other teams will need to replace it as well (if we want to be consistent), and Ladislav might need to update Boosters CI. QE tests use custom deployment for the apps and tests, no work needed here.
Time estimates
Speaking about the spring-boot BOM, I am in the context of beta1. Arquillian Cube is target for future. If we want to merge these together, it might take more time to make it work and test.

I think we can implement the BOM with kubernetes-client 1.4.34. When there is time to move to Arquillian Cube and new version of spring-cloud-kubernetes/kubernetes-client, we should be able to switch to the new versions easily by changing versions in the BOM. I suggest this approach as there are too many moving parts for me to embrace.

I have tested spring-boot-config map with 1.4.34 compatible versions and raised a PR to be merged when we release spring-boot-parent.

Spring Boot BOM 1.4 is deprecated


Share button like Wordle has

Wordle has a "share" button on the win screen, which allows one to share their result as a set of emoji without revealing the word or their guesses (the asterisk indicates "hard mode", other parts should be self-explanatory):
Wordle 220 3/6*

⬜⬜🟩🟨⬜
⬜🟩🟩⬜⬜
🟩🟩🟩🟩🟩

I've written a javascript bookmarklet to do this, but it would be nice to have this as a "proper" feature.

This is coming soon, the rough implementation is already at beta.sanuli.fi but I need some proper place for the button & a toast message to let the user know that the input was copied to their clipboard.

Love to hear it!

And perhaps polyfill browsers without navigator.clipboard features, but that is annoying to do at non-js world

ah, the perils of web design: always constrained by backwards compatibility

Ah, went to try it just now, and you might have an off-by-one error (today's is 19). I agree that the button is not really in a good place now, also you seem to insert newlines for all unguessed rows too?
Sanuli #18 3/6

⬛🟩⬛🟩⬛
⬛🟩⬛🟩🟩
🟩🟩🟩🟩🟩

The deployed version indeed has the off-by-one error and the newlines, both fixed at local dev branch :)
I'm also planning another sharing feature: a way to generate a link to share any completed game, not just the daily word, which would open the game without the characters shown, and the user who clicked could either reveal them, or try to solve the same word from the beginning.
This is something that the refactoring I've done last week would allow without resetting the current streaks the user might have at sanuliketju/classic mode

A simple version of this was deployed yesterday, clicking the link after päivän sanuli is solved copies the string on clipboard.

The link sharing feature was now also added, closing this issue.


how to remove ', TDLib 1.6.0' from aplication_version value in Telegram session

hi
when we create session by tdlib that add extra string to application_version value in telegram session
this is my parameter value
tdlibParameters: {
device_model: 'Firefox',
system_version: 'Windows',
application_version: '5.7.0',
enable_storage_optimizer: true,
apiId: api_id,
apiHash: api_hash
}
but when i see telegram sessions
application_version: 5.7.0, TDLib 1.6.0
how to caler this copy right
i have used native build from tdlib nativ

It can't be removed without altering TDLib's source code.

thanks .
for some business  competitive  and security reason, I have to hide the connection method and the method used in the sessions. .
but which file and which line ?

I can't help with that.


Moon-John

Write a short description about your art piece, such as what your artwork represents and your experience drawing it!
Next, make sure you go through each item in the following checklist. Delete this line after!

[ ] I have read the steps to getting a blot
[ ] I am submitting art that...

[ ] is algorithmically generated (will meaningfully change each time the program is run)
[ ] is your own work that is not copied from somewhere else
[ ] is drawable through the editor(does not use outside tools)
[ ] doesn't call Math.random() (See the documentation on randomness)
[ ] is drawable on Blot itself (doesn't have lines overlap more than 5 times)

[ ] Doesn't overlap lines more than 5 times
[ ] Fits in the working area of 125x125mm
[ ] Doesn't rely on colour to look good

If you used based your art on something else, used a tutorial, or remixed it from something else, please link it here:
Lastly, link a picture of your art piece here:

Short description: This is an auto moon generator! Everytime run is clicked a new "moon" is drawn with different craters all around!
It took a long time to fix a bunch of bugs and make it look acceptable on every run. Sometimes it breaks a bit but it normally works well!

Just an update, I will be closing this PR! Please create a new PR once you have updated your art! We are doing this due to new management of the PR system.


Paper request

Hello, I am interested in your research. I want to get a deeper understanding by reading your paper, but I could not retrieve your paper on arxiv.org. Can you give me this paper? ? I promise that it will only be used for personal research and not spread, my email address is<EMAIL_ADDRESS>thank you very much

Thanks for your interest in our work. We are improving our paper, and will make the paper available in the following 1~2 days.

Thanks for your interest in our work. We are improving our paper, and will make the paper available in the following 1~2 days.

Ok, thank you very much for your reply

The paper is now available at: https://yikaiw.github.io/projects/NeurIPS20-CEN/paper.pdf


Change relation_id to CatalogRelation& in relational operators

This modification is the first step of isolating temporary relations.
Note that in a bigger plan, we will decouple the Quickstep frontend from its backend, where the frontend only acquires a readonly copy of the catalog. So temporary relations will not be allowed to be directly  inserted into the catalog by the frontend query planner. Instead, we will create a temporary CatalogDatabase that stores the temporary relations, then send the temporary database to the backend to be merged into the stored database.
So for a relational operator, at the time point when serialization/deserialization happens, a relation may either from the stored database, or from the temporary database. One single "relation_id" won't be sufficient to differentiate these two situations. And a quick solution is to use the reference CatalogRelation&.

@pateljm Sorry for the late comment after merging.
If we are moving the master catalog as a service, this PR does not make sense, as operators now have to keep a copy of CatalogRelations, instead of the simple relation ids.


Asyncio integration

It would be nice if I could do:
@click.command()
@ascyncio.coroutine
def command():
    yield from whatever

I think the only place that should be changed to make that work would be Context.invoke (check if function is coroutine, do loop.run_until_complete()). But it's hard to subclass context in current click.
Would you mind making this functionality built-in?

Just curious if this is still the recommended practice now that async/await is a first-class language feature.
I feel a little dirty having to redundantly decorate all my commands with a @coroutine wrapper as well as a async def. Or maybe theirs a neater way that I've not thought of where I don't need to decorate each command.
Thanks - minor thing I know.

Just curious if this is still the recommended practice now that async/await is a first-class language feature.
I feel a little dirty having to redundantly decorate all my commands with a @coroutine wrapper as well as a async def. Or maybe theirs a neater way that I've not thought of where I don't need to decorate each command.
Thanks - minor thing I know.

Any update on this? Is it possible to pass an async generator into a progressbar as iterable for example?

Just to reinforce that this does not need to be in click, there are plugins like click-contrib/trio-click that provide the desired functionality.

Can this issue be re-opened and considered?

This is an updated version making use of asyncio.run() from Python 3.7:
import asyncio
from functools import wraps

def coro(f):
    @wraps(f)
    def wrapper(*args, **kwargs):
        return asyncio.run(f(*args, **kwargs))

    return wrapper

Usage:
@click.command()
@coro
async def command():
    await asyncio.sleep(1)
    click.echo("Delayed hello")

BTW, there is the fork of click, which allows to use it with asyncio https://github.com/python-trio/trio-click

New click user here. Thanks for this great tool.
I naively tried decorating a coroutine with @click.command() and received the cryptic error:
sys:1: RuntimeWarning: coroutine 'main' was never awaited

I believe it would be reasonable for @click.command() to examine the function it is decorating and, if a coroutine is found, automatically wrap it with the @coro decorator suggested above. In the meantime, the workaround worked great.


Bucklers don't have an option that lets them appear in the Shield section of the Character Sheet (and engage with automation accordingly) without being Gripped.

Rules text: https://2e.aonprd.com/Shields.aspx?ID=1

You can Raise a Shield with your buckler as long as you have that hand free or are holding a light object that’s not a weapon in that hand.

This means you can always Raise a Buckler even when you aren't Gripping it, unless your hand is occupied by something else as defined above. And so long as it's strapped to your arm.
However, the way the foundry game system is configured, you must grip the Buckler to have it be acknowledged in the Shield section. This is incorrect for how the game system works, because the Buckler doesn't occupy your hand while you can Raise it, unless you are also actively gripping it (for example, to Shield Bash, since that requires 1 hand to use as an attack).
What I recommend is having a separate setting for Buckler to be acknowledged in the Shield section of the character sheet. Something like "Strapped" that doesn't occupy your hand and doesn't give you the Shield Bash Attack for it, but does have it show correctly in the Shield section.
Without this, you can't use the Buckler without setting it to Gripped, when in truth, that may not be what's actually happening.
I guess you could just Grip 3 things and not worry about it, but this seems unnecessarily confusing to have to work around.

One must still wield a buckler to raise it.

The Buckler should not use a hand to be accessible for Raising & Shield Blocking.
As here: #15788, the system treats the hand as occupied, when it is not necessarily occupied.
If this won't be fixed, then I'll just work around it, but this interaction has degraded any interest I had in helping this system improve.

I appreciate that.
For what it's worth, and in hopes it helps, the text is here:
https://app.demiplane.com/nexus/pathfinder2e/items/buckler-rm

You can Raise a Shield with your buckler as long as you have that hand free or are holding a light object that’s not a weapon in that hand.

If a Buckler uses a hand to be accessible for Raising & Shield Blocking, then this sentence does nothing and is superfluous.


externs: useCapture parameter of EventTarget's addEventListener() and removeEventListener() methods should be optional

Documentation for these methods from MDN says its optional:
https://developer.mozilla.org/en-US/docs/Web/API/EventTarget/addEventListener
https://developer.mozilla.org/en-US/docs/Web/API/EventTarget/removeEventListener

This change is

In the MDN documentation, there's this note:

Note: useCapture became optional only in more recent versions of the major browsers; for example, it > was not optional before Firefox 6. You should provide this parameter for broadest compatibility.

So I guess the current version is better for compatibility with more browsers.

If someone wants to try this out in IE7/8 and make sure it works, then this could probably be removed. IIRC FireFox was the only browser that was picky about having all 3 arguments present, and that restriction was removed many versions back.

If someone wants to try this out in IE7/8 and make sure it works, then this could probably be removed.

According to the same MDN page, basic support for addEventListener() wasn't even added until IE9, and the useCapture argument was optional from the start. It says that before IE9, attachEvent() was used instead.

@googlebot I signed the CLA

@Chadkillingsworth If Google is testing on very old Firefox browsers internally it would have to wait...

@Dominator008 But this just makes the argument optional right? It's still part of the signature.

@Chadkillingsworth Well people writing new code may omit the argument and find out their tests fail on, say, Firefox 3

@Matrixfrog Are old Firefox versions (<6) still being tested internally? If not, we are safe to merge this.

I can't say for sure there are zero projects that still care about Firefox <6 but it's probably okay to take this. Will give it a few days to see if anyone else objects.

We'll try to do an internal release early next week. Let's wait until after that.

Tyler was working through updating these signatures.

It looks like this PR is obsolete since this is now marked optional at https://github.com/google/closure-compiler/blob/50de7abb88f8f00c4e37b23da0515b840e9ed00c/externs/browser/w3c_event.js#L36 ?

Oh cool when I commented it auto-unassigned me which is all I really wanted anyway ;)


Remove proxy from repo file as dnf interprets "none" as a url

Remove the proxy from the repo file

Signed-off-by: Will Johnson<EMAIL_ADDRESS>

@johnsonw Unit tests are failing in travis.

looking

Landed as: 3a4d2b8998e23d26daf73d7d243724d34888fd09


[BACKLOG-11444]  Pooled big-data connections fail in Spoon

When configuring the DataSource, the call to setDriverClassname
would fail if the driver is not in the current thread's classpath.
Addressed by explicitly setting the BasicDataSource driver cp.
http://jira.pentaho.com/browse/BACKLOG-11444

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
ant -Dtestreports.dir=bin/reports/unit-test -f core/build.xml clean-all resolve jacoco && ant -Dtestreports.dir=bin/reports/integration-test -f core/build.xml jacoco-integration checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  core/src/org/pentaho/di/core/database/ConnectionPoolUtil.java
  core/test-src/org/pentaho/di/core/database/ConnectionPoolUtilTest.java

Still Broken Tests:
org.pentaho.di.core.row.value.ValueMetaBaseTest.testConvertDataUsingConversionMetaData:
:red_circle: junit.framework.AssertionFailedError
junit.framework.AssertionFailedError: expected:<Sun Feb 18 06:00:00 UTC 1990> but was:<Sun Feb 18 00:00:00 UTC 1990>
	at org.pentaho.di.core.row.value.ValueMetaBaseTest.testConvertDataUsingConversionMetaData(ValueMetaBaseTest.java:676)

Unit test coverage change
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.
org.pentaho.di.core.database.ConnectionPoolUtil

Complexity Change: -.78%:small_red_triangle_down:
Instruction Change:  + .57%
Line Change:  + .42%

Build Completed
:x: This pull request has errors. They will need to be addressed before it can be accepted. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
ant -Dtestreports.dir=bin/reports/unit-test -f core/build.xml clean-all resolve jacoco && ant -Dtestreports.dir=bin/reports/integration-test -f core/build.xml jacoco-integration checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  core/test-src/org/pentaho/di/core/row/value/ValueMetaBaseTest.java

Newly Fixed Tests:
org.pentaho.di.core.row.value.ValueMetaBaseTest.testConvertDataUsingConversionMetaData:
:red_circle: junit.framework.AssertionFailedError
junit.framework.AssertionFailedError: expected:<Sun Feb 18 06:00:00 UTC 1990> but was:<Sun Feb 18 00:00:00 UTC 1990>
	at org.pentaho.di.core.row.value.ValueMetaBaseTest.testConvertDataUsingConversionMetaData(ValueMetaBaseTest.java:676)

Unit test coverage change
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.
org.pentaho.di.core.database.ConnectionPoolUtil

Branch Change:  + 2.00%
Complexity Change:  + 1.85%
Instruction Change:  + .57%
Line Change:  + .42%

org.pentaho.di.core.logging.KettleLogStore.new TimerTask() {...}

Branch Change:  + 50.00%
Complexity Change:  + 33.33%
Instruction Change:  + 75.68%
Line Change:  + 83.33%
Method Change:  + 50.00%

org.pentaho.di.core.logging.LoggingBuffer

Complexity Change:  + 1.72%
Instruction Change:  + 1.09%
Line Change:  + 1.53%
Method Change:  + 3.45%

org.pentaho.di.core.row.value.ValueMetaBase

Branch Change:  + .24%
Complexity Change:  + .20%
Instruction Change:  + .14%
Line Change:  + .16%

Checkstyle violations
The code submitted is not complying with one or more of our guidelines. To perform these checks locally, please use this tool.
/home/buildguy/project/core/test-src/org/pentaho/di/core/row/value/ValueMetaBaseTest.java

:heavy_exclamation_mark: Unused import - java.util.Locale. at Line: 72 Column: 8

Build Completed
:white_check_mark: This pull request has passed all validations.
Build Commands
ant -Dtestreports.dir=bin/reports/unit-test -f core/build.xml clean-all resolve jacoco && ant -Dtestreports.dir=bin/reports/integration-test -f core/build.xml jacoco-integration checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  core/test-src/org/pentaho/di/core/row/value/ValueMetaBaseTest.java

Newly Fixed Tests:
org.pentaho.di.core.row.value.ValueMetaBaseTest.testConvertDataUsingConversionMetaData:
:red_circle: junit.framework.AssertionFailedError
junit.framework.AssertionFailedError: expected:<Sun Feb 18 06:00:00 UTC 1990> but was:<Sun Feb 18 00:00:00 UTC 1990>
	at org.pentaho.di.core.row.value.ValueMetaBaseTest.testConvertDataUsingConversionMetaData(ValueMetaBaseTest.java:676)

Unit test coverage change
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.
org.pentaho.di.core.database.ConnectionPoolUtil

Branch Change:  + 2.00%
Complexity Change:  + 1.85%
Instruction Change:  + .57%
Line Change:  + .42%

org.pentaho.di.core.row.value.ValueMetaBase

Branch Change:  + .24%
Complexity Change:  + .20%
Instruction Change:  + .14%
Line Change:  + .16%


cannot download mongodb error server misbehaving

I'm not seeing any issues on the server side - Can you re-try and open this issue again if the issue persists?


macOS prompts me for a Bluetooth keyboard on wake

This only happens when I have Karabiner-Elements installed. I do not use a Bluetooth keyboard, but when I wake my MacBook Air from sleep, I sometimes see this dialog (from Bluetooth Assistant):

I'm getting this too, in combination with the keyboard modifiers not working with mouse clicks (i.e. cmd-click in chrome, shift-click to select a range of files in Finder or Mail.app... I was going crazy until I remembered I was running Karabiner-Elements. :-)
A reboot fixes these issues for a little while, but it appears that these things start going wrong after the mac goes to sleep and is resumed.

@akohlsmith is there an issue open already about the keyboard modifiers not working with mouse clicks?

It's sort of mentioned in #83, but really I think this is more related to the issues where the modifier keys just stop working altogether.

I believe this issue has been fixed in the latest version.

This issue is still occurring actually..

I can confirm, this is still happening.

Can confirm it's still happening to me too.

Same thing here

This is happening for me. 0.90.64

Happening for me too. Can't remember if it was fixed at some point, but has been happening at least for several weeks. 0.90.66. Could someone re-open this?

Yes please reopen! :) @tekezo ?

Still happening to me on Karabiner-Elements 11.1.0
It's quite annoying to be honest

Still happens to me as well. It's easy for me to reproduce too. All I have to do is start up my computer with Karabiner-Elements, do some editing with it, lock the computer (sending it to the lock screen) and then try to log back in. My entire keyboard is dead - but my mouse works. Only way to get back on is a reboot or connecting my bluetooth keyboard. Oddly enough, once I log in with my bluetooth keyboard, Karabiner (and actually the entire keyboard) starts working again immediately.

Yeah, This issue is still there !


Fix strictNullChecks incompatibility

The ConnectionHeaders interface does not work with strict: true or strictNullChecks: true.
Though this point needs further investigation on TypeScript itself, this should help to have type suggestions on ConnectionHeaders in strict mode.
If this isn't consistent enough the only solution (afaik) is to remove the optional keys and the undefined key definition. In this case you will lose the type suggestion:
export interface ConnectionHeaders {
  [key: string]: string;
}

Related to: https://github.com/Microsoft/TypeScript/issues/17277
If you agree to these changes, dont forget to bump the version 🥇

I agree to the changes because I trust you guys to maintain your own typescript stuff.
If you can enlight me on this one #47 also it would be great!


Python: modernise cls self argument name checks

One thing I'm not sure about is the fact that I deprecated the old class ZopeInterfaceMethod extends PyFunctionObject,  but I thought it was the easy way to remember it by doing it now!

Fix the things from review + rebased on newest master... so now it should hopefully all be good :tada:

Forgot to update the filename in the .expected test files. now tests should actually pass :tada:


Expect Azurite to fail when inserting doubles greater than MAX_VALUE but succeeds instead

Which service(blob, file, queue, table) does this issue concern?
Table storage
Which version of the Azurite was used?
Azurite 3.29.0
Where do you get Azurite? (npm, DockerHub, NuGet, Visual Studio Code Extension)
npm
What's the Node.js version?
v18.15.0
What problem was encountered?
When using azurite emulated table storage, entities that have a property of type Edm.Double who's value is greater than the MAX_VALUE can be  upserted successfully, whereas with Azure Table Storage this operation will fail with "InvalidInput: An error occurred while processing this request."
When inserted into emulated table storage, the value of the property in azurite will also be null.
This causes a problem when trying to query/list entities in the table. There will be an error when trying to parse the response body with something similar to:
Error "SyntaxError: Unexpected token 'I', ...","Property10":Infinity,""... is not valid JSON" occurred while parsing the response body

Steps to reproduce the issue?
Create an entity with a property that has the type Edm.Double and a value of the string 13e7705.
Try upserting the entity into Azurite table storage.
Expect the operation to fail, however it succeeds.
Have you found a mitigation/solution?
Have azurite emulate the behavior of table storage and throw an error when trying to insert a number greater than MAX_VALUE.

@richardMSFT
Thanks for raising this issue!
I have raised a PR to fix it: https://github.com/Azure/Azurite/pull/2388

The fix PR is merge. Normally will release in the next Azurite release.


Updated PackageReference from 4.7.5 to 4.8.0.

Description

Updated PackageReference for GLWpfControl.csproj.
Updated PackageReference for Example.csproj.

Fixes #114
Dependencies

OpenTK 4.8.0.

Type of change

[x] Bug fix (non-breaking change which fixes an issue).

How Has This Been Tested?
I tested the example locally on my machine and everything still needs to be working. Furthermore, I created my own local package and tested it in my own personal project to make sure that I would no longer receive the warnings described in #114.

Test Configuration:

Operating System: Windows 10 Home
Hardware: Intel i7-6700HQ, 32GB RAM, GTX 950M
Toolchain: VS Community 2022 17.5.4

Possible Issues
I don't know if this will directly fix the issue once a new release is made. I think there is something that the maintainers of the NuGet package will have to address unless I can be pointed in the right direction. When uploading my own package of the control to NuGet instead of checking if the version was between 4.3.0 and 5.0.0 it ensured that it was greater than or equal to 4.8.0.

To update these references you also need to update the version in the paket file:
https://github.com/opentk/GLWpfControl/blob/master/src/GLWpfControl/paket
Updating this version will fix the nuget package version range.

My new laptop charger is on its way, express shipping. Once it comes around I'll make this change and hopefully we can update the package :)

@softwareantics ping if you forgot this

Closing if favor of #86


Reduced the fontSize for the small devices

To optimise for smaller devices, the font size for the copyright section has been reduced.

Fixes Issue
#1625

Changes proposed

Screenshots

Note to reviewers

@Anmol-Baranwal, I have made the changes please review it.

@rupali-codes, review it

Thanks for contributing @the-shivam-gupta! If you stay updated on LinksHub's progress, join our Discord! :) We loved to see more of your ideas! 😊


Empty string makes tail comma with .field method

squel.select()
  .field('foo')
  .field('')
  .from('bar')
  .toString()
// output: SELECT foo,  FROM bar

v5.10.0
It is a bug?

No, this is not a bug. It's intended behaviour since the field value is allowed to be anything, even an SQL function.

But
squel.select()
  .field('')
  .field('foo')
  .field('')
  .from('bar')
  .toString()
// output: SELECT foo FROM bar
// this is the way to avoid tail comma now

squel.select()
  .field('')
  .field('foo')
  .from('bar')
  .toString()
// output: SELECT foo FROM bar

Tail comma can lead to errors in many database,such as MySQL,SQLite.
So I think that tail comma should be ignored.
@hiddentao
Would you think about removing tail comma as a new feature in next version?

@homura
The only thing I think this can be used is if you are dynamically passing the field, say its a variable containing the string
let some_field = (some_condition) ? 'col' : '';
squel.select()
    .field(some_field)...

otherwise, you can just fix right here if @hiddentao approves of it..
https://github.com/hiddentao/squel/blob/master/src/core.js#L1250

Yeah, tail comma could be removed, though it's an exception situation - could you not check the field name you're dynamically setting to ensure it's not empty?


fix: ledger locked stx, ref #4539

Try out this version of Leather — Extension build, Test report

This PR removes StacksLedgerAssetsList which created two versions of our Stacks asset list (software and hardware). This was done bc if the Stacks keys haven't been loaded yet, the account loader address would return null and cause a UI bug (I think). Instead, I think the loader can just be for the address specifically and return an empty string until the keys are loaded to prevent the error? The loader didn't need to be for the entire account object. Also, I renamed StacksBalanceItem here to StacksAssetList bc it renders both the STX balance and all other Stacks FT balances, it really isn't just an item imo. I have tested this with Ledger. It seems to be working w/out an error so far.

Any other ideas how we might solve this, without duplicating components per wallet type, not relying on an empty string?
I understand that if the key isn't there, we still want to show the row so we can add the ledger keys? What if we followed a similar pattern to Suspense, where if the data isn't there, we provide a fallback?

Yeah, I wasn't confident this was a good idea, def think prob doing the fallback is better so I'll try that today. Thanks for feedback.

@kyranjamie can you approve/unblock this before you head out?


Change NSUInteger to NSInteger in public API

#200

🔥
Gonna wait on CI to go ✅

Duped w/ #205, this one is much lighter but I'll give that PR a chance to cleanup before merging since it was chronologically first in.

@rnystrom Sure😊

Thanks @zhubofei ! 🙌

Coverage remained the same at 91.441% when pulling e840c6566c4a94e8e0c148befd5674bfe45319ee on zhubofei:integer into 204f7d53908d1746d0ae08c32ffa26bfd446c316 on Instagram:master.

Coverage remained the same at 91.441% when pulling e840c6566c4a94e8e0c148befd5674bfe45319ee on zhubofei:integer into 204f7d53908d1746d0ae08c32ffa26bfd446c316 on Instagram:master.


node 4.5.2 missing linux-x64-48_binding.node

Hi folks, the installation is not finding linux-x64-48_binding.node. Please advise. Thanks.
$ npm -v
3.10.8
$ node -v
v6.9.1
$ node -p process.versions
{ http_parser: '2.7.0',
node: '6.9.1',
v8: '5.1.281.84',
uv: '1.9.1',
zlib: '1.2.8',
ares: '1.10.1-DEV',
icu: '57.1',
modules: '48',
openssl: '1.0.2j' }
$ node -p process.platform
linux
$ node -p process.arch
x64
$ node -p "require('node-sass').info"
module.js:471
throw err;
^
Error: Cannot find module 'node-sass'
at Function.Module._resolveFilename (module.js:469:15)
at Function.Module._load (module.js:417:25)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at [eval]:1:1
at ContextifyScript.Script.runInThisContext (vm.js:25:33)
at Object.exports.runInThisContext (vm.js:77:17)
at Object. ([eval]-wrapper:6:22)
at Module._compile (module.js:570:32)
at bootstrap_node.js:357:29
$ npm ls node-sass
/tmp/temp1
âââ (empty)
npm ERR! code 1
attempt to install node-sass 4.5.2
$ npm install node-sass
npm WARN deprecated<EMAIL_ADDRESS>This package is deprecated. Use Object.assign.

<EMAIL_ADDRESS>install /tmp/temp1/node_modules/node-sass
node scripts/install.js

Downloading binary from https://github.com/sass/node-sass/releases/download/v4.5.2/linux-x64-48_binding.node
Cannot download "https://github.com/sass/node-sass/releases/download/v4.5.2/linux-x64-48_binding.node":

I can confirm the binary exists at that location. Please try again, if
problems persist check your network snd proxy settings.
On 11 Apr. 2017 4:12 am, "ayhkusa"<EMAIL_ADDRESS>wrote:

Hi folks, the installation is not finding linux-x64-48_binding.node.
Please advise. Thanks.
$ npm -v
3.10.8
$ node -v
v6.9.1
$ node -p process.versions
{ http_parser: '2.7.0',
node: '6.9.1',
v8: '5.1.281.84',
uv: '1.9.1',
zlib: '1.2.8',
ares: '1.10.1-DEV',
icu: '57.1',
modules: '48',
openssl: '1.0.2j' }
$ node -p process.platform
linux
$ node -p process.arch
x64
$ node -p "require('node-sass').info"
module.js:471
throw err;
^
Error: Cannot find module 'node-sass'
at Function.Module._resolveFilename (module.js:469:15)
at Function.Module._load (module.js:417:25)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at [eval]:1:1
at ContextifyScript.Script.runInThisContext (vm.js:25:33)
at Object.exports.runInThisContext (vm.js:77:17)
at Object. ([eval]-wrapper:6:22)
at Module._compile (module.js:570:32)
at bootstrap_node.js:357:29
$ npm ls node-sass
/tmp/temp1
âââ (empty)
npm ERR! code 1
attempt to install node-sass 4.5.2
$ npm install node-sass
npm WARN deprecated<EMAIL_ADDRESS>This package is deprecated. Use
Object.assign.
<EMAIL_ADDRESS>install /tmp/temp1/node_modules/node-sass
node scripts/install.js
Downloading binary from https://github.com/sass/node-
sass/releases/download/v4.5.2/linux-x64-48_binding.node
Cannot download "https://github.com/sass/node-
sass/releases/download/v4.5.2/linux-x64-48_binding.node":
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sass/node-sass/issues/1948, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjZWKcIboTVTgULk4CdP3Ln6K16cKpoks5runEPgaJpZM4M5IbM
.

Being we aren't allowed install via the proxy. Is there a way to tell node-sass install to look for the binding.node file in our internal artifactory? Thanks.

The bindings are hosted on github releases. You can mirror them on an internal server and set the config documented at https://github.com/sass/node-sass#binary-configuration-parameters


[Automation] Generate Fluent Lite from mixedreality#package-2021-01

[Automation] Generate Fluent Lite from mixedreality#package-2021-01

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-resourcemanager-mixedreality


grafana-image-renderer: 3.7.1 -> 3.7.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/grafana/grafana-image-renderer/releases.
meta.description for grafana-image-renderer is: A Grafana backend plugin that handles rendering of panels & dashboards to PNGs using headless browser (Chromium/Chrome)
meta.homepage for grafana-image-renderer is: https://github.com/grafana/grafana-image-renderer
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.7.2 with grep in /nix/store/a41rrxk7w20qq2y3j5dgh4iwa8nv9izj-renderer-3.7.2
found 3.7.2 in filename of file in /nix/store/a41rrxk7w20qq2y3j5dgh4iwa8nv9izj-renderer-3.7.2

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
grafana-image-renderer

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/a41rrxk7w20qq2y3j5dgh4iwa8nv9izj-renderer-3.7.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A grafana-image-renderer https://github.com/r-ryantm/nixpkgs/archive/1ae540b1990d0ab1c4bf1b0a5e131022c17119f7.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/a41rrxk7w20qq2y3j5dgh4iwa8nv9izj-renderer-3.7.2
ls -la /nix/store/a41rrxk7w20qq2y3j5dgh4iwa8nv9izj-renderer-3.7.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

grafana-image-renderer

Maintainer pings
cc @Ma27 for testing.

@wegank is there any specific reason you're sneaking in some "cleanups" here rather than doing that in another PR?

There's not much difference to me. I can open another PR if you want.

@wegank this is kinda bold. Why do you even ask in the first place if you don't care?

I'm sorry, I thought it had been tacitly approved, not having received an immediate response. I won't do it next time.

not having received an immediate response

OK, but for the next time please keep in mind that the lack of an immediate response doesn't justify a quick merge. Especially in a case like this where we're absolutely not in a hurry.


Update readme with logs for deployment errors

Just a small reminder for logging deployment errors

How this suppose to work? This is simply getting logs.

@arunoda if you just use mup logs -f you can't really see what happened in the server if there was a problem.
I just wanted to point out in the readme so people don't need to search in the issues to see a better log :smiley:


Github #278: change lastInsertId to return the last sequence number

Fix for #278.
Change lastInsertId to return the last sequence number when the sequence name is provided. Previously when a table name is provided, the driver returns the last id inserted of that table. Now when a table name is given, an empty string is returned.

Coverage increased (+0.4%) to 53.006% when pulling 201383badec8c03c499e24da59d9150e8b16cf94 on v-kaywon:lastInserId_Sequence into f73c23be1e34270a3a9de942b105de006b994ce6 on Microsoft:dev.

Coverage increased (+0.4%) to 53.072% when pulling e417541d6592c5ac30c934ae385511d8b13161ba on v-kaywon:lastInserId_Sequence into f73c23be1e34270a3a9de942b105de006b994ce6 on Microsoft:dev.

@meet-bhagdev: this PR does not include the connection option, it simply change the lastInsertId function to return the last sequence number. Depending on the decision if a connection option for sequence number is wanted, the code will/will not be changed.

Coverage increased (+0.4%) to 53.072% when pulling 7b55c3ca2f88ecea46b3cd983e7e7d503898ffb3 on v-kaywon:lastInserId_Sequence into f73c23be1e34270a3a9de942b105de006b994ce6 on Microsoft:dev.

Coverage increased (+0.4%) to 53.072% when pulling 981b48da54799b237e0688e9a8b913be05de969e on v-kaywon:lastInserId_Sequence into f73c23be1e34270a3a9de942b105de006b994ce6 on Microsoft:dev.

Coverage increased (+0.4%) to 53.072% when pulling 12dcf76d8c6f173612caf0a9b2afe4de75446065 on v-kaywon:lastInserId_Sequence into f73c23be1e34270a3a9de942b105de006b994ce6 on Microsoft:dev.

Coverage increased (+0.4%) to 53.072% when pulling 2c7695fcfb116b23eb92e1d185ece64d4be7f5e2 on v-kaywon:lastInserId_Sequence into f73c23be1e34270a3a9de942b105de006b994ce6 on Microsoft:dev.

Coverage increased (+0.4%) to 53.072% when pulling 0f30435cfc7b5fe9234d8c36454b1317755d1f51 on v-kaywon:lastInserId_Sequence into f73c23be1e34270a3a9de942b105de006b994ce6 on Microsoft:dev.

Coverage increased (+0.4%) to 53.072% when pulling e0bd36380e362acb4fc928fba31dd1a1e6e1818d on v-kaywon:lastInserId_Sequence into f73c23be1e34270a3a9de942b105de006b994ce6 on Microsoft:dev.

Coverage increased (+0.7%) to 53.299% when pulling 5a3cc536646630e234ad1f27a1b2b84adb3ea627 on v-kaywon:lastInserId_Sequence into f73c23be1e34270a3a9de942b105de006b994ce6 on Microsoft:dev.

@yitam :  did that already :)

So when the user is running an old sql server but supplies a name to lastInsertId() the method simply returns an empty string?

yes, in fast when the user tries to create a sequence, the stmt returned would be false

Coverage increased (+0.7%) to 53.299% when pulling 4003aaa7dff57355118f035d50afac87dffa0f7f on v-kaywon:lastInserId_Sequence into 75d1f2269072858e66cc6ba96f59a08cc71a6ab7 on Microsoft:dev.

Coverage decreased (-24.0%) to 28.684% when pulling 5225490fcbd1c59a9d81022beef240950abbc45d on v-kaywon:lastInserId_Sequence into 75d1f2269072858e66cc6ba96f59a08cc71a6ab7 on Microsoft:dev.

Coverage increased (+1.1%) to 53.753% when pulling e3c08fa11abe93cc03cb29b6204d747c775b9263 on v-kaywon:lastInserId_Sequence into 75d1f2269072858e66cc6ba96f59a08cc71a6ab7 on Microsoft:dev.

Coverage increased (+1.1%) to 53.753% when pulling e3c08fa11abe93cc03cb29b6204d747c775b9263 on v-kaywon:lastInserId_Sequence into 75d1f2269072858e66cc6ba96f59a08cc71a6ab7 on Microsoft:dev.

Coverage increased (+1.1%) to 53.753% when pulling e3c08fa11abe93cc03cb29b6204d747c775b9263 on v-kaywon:lastInserId_Sequence into 75d1f2269072858e66cc6ba96f59a08cc71a6ab7 on Microsoft:dev.

@v-kaywon, thanks for signing the contribution license agreement. We will now validate the agreement and then the pull request.
Thanks, Microsoft Pull Request Bot

@david-puglielli can we close this PR now?

Yes this PR can be closed.


Tailwind 1.4.x breaks social media cards

Issue:
I noticed this issue after an improvement I made to my personal site. After upgrading to v1.4.4 my social media sharing cards were no longer working. It took me a while to debug as it's not initially clear what is causing the issue. The site does not error locally, builds correctly, and does not appear broken on deploy - it is only social media cards which are broken.
Issue version: 1.4.x
Last known safe version: 1.2.0
My site setup: Gatsby, Contentful & Tailwind.
I'm not sure if this is just an issue with SSG's (and any other Critical CSS approaches as they pull CSS into the head). It is probably not an issue with Gatsby's implementation of Tailwind due to version 1.2.0 working as expected. It's not clear exactly what is causing this issue, but it appears when upgrading versions without making any other changes.
How to test:
Open up any site using tailwind 1.4.x site (the site I used is here).
Open up the opengraph debugger
Add the URL and scrape the site to fetch new information

That appears to be pulling in a lot more than just the critical CSS for your site, it seems like almost every class in the head is not even present on your page.
I suspect the root cause is maybe the page being too large because of all the unnecessary inlined CSS and sites pulling the cards are giving up on streaming the content after a certain size limit.
I would be looking at how you've got Critical CSS configured, because it appears to be misconfigured as far as I can tell.
Just as an example, not a single one of these classes is actually used on your site, let alone critical:

Looks like my gatsby purgecss config wasn't specific enough, and tailwind 1.4.x must have a lot of extra generated styles leading to the issue. For the record, this is Gatsby's default approach, i haven't changed anything.
Before - 50% reduction
{
  resolve: `gatsby-plugin-purgecss`,
  options: {
    printRejected: true,
    tailwind: true,
    ignore: ['src/scss', '/react-carousel/', '/prismjs/'],
  },
},

After - 98% reduction
{
  resolve: `gatsby-plugin-purgecss`,
  options: {
    printRejected: true,
    tailwind: true,
    ignore: ['./src/scss', '/react-carousel/', '/prismjs/'],
  },
},

Yep, just updated, and that's fixed the issue.


Automatic transactions getting added

What happened?
I'm running a two-organization Hyperledger Fabric network using Bevel Operator and encountering an unusual issue. Blocks are being added every minute automatically, even though no transactions are being executed on the network. Upon inspecting the transactions within the blocks, they appear to be config transactions
Note: I'm running the channel via CRD's using main and follower channels

What did you expect to happen?
Network should only add new transactions when the any transaction is occurred on the network
How can we reproduce it (as minimally and precisely as possible)?
Create a network using the main channel and follower channel
Anything else we need to know?
No response
Kubernetes version

# kubectl get nodes -o wide

Should be solve in the next release 1.11 coming this week @pshgpt


Remove application project template.

Summary
This PR removes application project template on the Gradle plug-ins project (./gradle).
Background, Problem or Goal of the patch
The application project templates had been moved by asakusafw/asakusafw-distribution#1.
Design of the fix, or a new feature
N/A.
Related Issue, Pull Request or Code
asakusafw/asakusafw-distribution#1
Wanted reviewer
@akirakw

BUILD SUCCESS. <jenkins-prb-asakusafw-sdk-102>


Dark mode - verify React output

If possible set up something deployable to view it on a web page.

@enowak1031 Breaking down this one into two separate issues.

@enowak1031 closing the issue, it is not required as we are doing the spike to test Modus Web - React


Payload data object is not found while app is not in memory.

Notification works perfectly. I have been facing an issue with tapping on the notification. After taping on the notification I get the payload data object in my app onNotificationOpen subscription only if the app is in memory.
I don't get the payload data while the app is not in memory. In other words, it does not work accordingly if the app is not in memory. This issue has been with the older version as well.
Is there any patch for this?
I am using Firebase cloud messaging for this matter

I'm currently working on a rewrite of the notifications functionality of this plugin which will address this issue in addition to fixing other existing issues and adding more features.
But I'll leave this issue open for now to capture the problem and when my new version is finished, it can be tested against this criteria.

BTW which platform are you seeing this issue on? iOS, Android or both?

In android. Not tested in iOS yet.

Thanks - I have observed the same issue in Android but also not tested this on iOS.

├───build_script
│   ├───new_script
│   │   └───src
│   │       ├───log
│   │       └───vcs
│   └───resources
│       ├───com.cit.vericash.empcustomer
│       │   ├───googleServices
│       │   ├───img
│       │   │   └───mahfazti
│       │   │       └───svg
│       │   ├───res
│       │   │   ├───icon
│       │   │   │   ├───android
│       │   │   │   └───ios
│       │   │   ├───notificationSmallIcon
│       │   │   │   ├───drawable-hdpi
│       │   │   │   ├───drawable-mdpi
│       │   │   │   ├───drawable-xhdpi
│       │   │   │   ├───drawable-xxhdpi
│       │   │   │   └───drawable-xxxhdpi
│       │   │   └───screen
│       │   │       ├───android
│       │   │       └───ios
│       │   └───translations
│       │       └───app
│       ├───com.fbnquest.demo.vericash
│       │   ├───app_icons
│       │   ├───css
│       │   │   └───theme
│       │   ├───googleServices
│       │   ├───img
│       │   │   ├───menu_theme
│       │   │   ├───mutual_funds
│       │   │   └───standerd

FYI this should be fixed on the dev branch if you want to give that a test.
I'm currently reworking the plugin on dev  - when rework is completed, I'll merge to master and release a new major version.

I have tried with dev branch. It does not work accordingly. App loads when the app is not in memory while opening the app. That can not find the payload data.

I've just published<EMAIL_ADDRESS>This is a major version that reworks the cloud messaging code and so will resolve this issue.
Please regression test using v5.0.0 of this plugin to confirm.
Note: v5.0.0 makes breaking changes to the plugin API - see the CHANGELOG for details.
You may find it useful to test using the example project which has a built-in FCM messaging client with test messages.

Fixed in v5.0.0

yup it is working just fine.

@dpa99c Please look into this. I am using firebase cloud function to trigger the notification. I am using firebase-admin. Show the payload looks something like this.
const payloadMobile =  {               notification: {                 title: title,                 body: body,                 icon: icon,                 vibrate: '1',                 color: "#f7066a",                 sound: 'my_sound',                 notification_android_sound: "my_sound",               },   data: {                 patient_id: patient_id,                 notification_type: notification_type,                 title: title,                 body: body,                 payment_status: payment_status,                 color: "#f7066a",                 sound: 'my_sound',                 notification_android_sound: "my_sound"               }             }
const responseMobile = await admin.messaging().sendToDevice(uniqueDevicesTokenArrayMobile, payloadMobile).
which works fine, I can get the notifications with custom color and custom icons. I am facing issue with the custom sound.
I also tried with the script as you have explained in the docs.
npm run send -- --message=android_notification.json --token="chLm2WNJcDY:APA91bFQxiTOg5aq8wJtVowkHyAIQXpzLYsuZdk00sl4D-iO5kmsuP0DcocEhDJe326d2PG9a0o1_0JQw3p0V2T9Iti5zRbukHNzmGCasxfA__XQd4g9qsxSZHrOKBasJ9qX39ZiA5ZO"
This also works fine except the sound property. Even if I remove the sound property also it gives me default sound here from script run.
<resource-file src="resources/android/raw/my_sound.mp3" target="app/src/main/res/raw/my_sound.mp3" />
this is also there in config.xml and does its job without any issue.
What might be the issue for which I can not make the custom ring tone work? From both firebase function and the samle .json files?
Platform - ionic 3, firebase-x 9.0.2(@latest)

why to open an issue rather fix here. any suggestions will help me a lot. Thanks.

Have you tried to reproduce this by building and running the example project app?

No, I have not tested the app. As I am implementing it in ionic. So can I build and test Example Ionic 3 project  app?

I have tried and it does not work with the example project you have suggested.
Please Watch this

@dpa99c does it work for you? It is simply not working with the test app. Could you please check? Android version - 10

For Android 8.0 and above, it's the notification channel that defines the sound, not the sound key in the FCM message payload (see https://stackoverflow.com/a/54308706/777265)
I've updated the Android Notification Sound and Android Notification Channels sections of the documentation to make this clearer.


ExtendedImageSlidePage for other widgets?

Hi there,
thanks for the great plugin! We are using it for a gallery in our app and it works great.
In the gallery, we use the ExtendedImageSlidePage to go back from a detail image view to the gallery overview. Since we also have videos in the gallery, there should be the same gesture for returning from a detail video page to the gallery overview. Is this possible with ExtendedImageSlidePage or does this only work in combination with ExtendedImage?

I have  public ExtendedImageSlidePageHandler. hope it works for you.
https://github.com/fluttercandies/extended_image/blob/4c2c5767b61252424e1f832b29a989d2ea554a20/example/lib/pages/simple/slide_page_demo.dart#L103


Non-IDV new bidder registering through typical registration form sees information about identity verification

addresses https://artsyproduct.atlassian.net/browse/AUCT-950
This adds a new text to explain what IDV is for users who are new to it. On larger screens, it looks totally fine. But on iPhone SE the button at the bottom was pushed down to outside of the viewport. So I replaced the container with a <ScrollView>. This blog post https://medium.com/@peterpme/taming-react-natives-scrollview-with-flex-144e6ff76c08 was heplful to get the components positions right.
Screenshots
iPhone X

iPhone SE

This PR is ready for review upon ✅

@dleve123 Here are the screenshots: