Events - match full list against pattern

Fixes #4384

Codecov Report

Merging #4534 (bb5c7bd) into master (20ba807) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #4534      +/-   ##
==========================================
+ Coverage   95.14%   95.16%   +0.01%
==========================================
  Files         513      514       +1
  Lines       58172    58372     +200
==========================================
+ Hits        55350    55551     +201
+ Misses       2822     2821       -1

Flag
Coverage Δ

servertests
48.06% <100.00%> (-0.09%)
:arrow_down:

test_responses
32.31% <0.00%> (-0.04%)
:arrow_down:

unittests
95.07% <100.00%> (+0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

moto/events/models.py
94.67% <100.00%> (+<0.01%)
:arrow_up:

moto/apigateway/responses.py
93.47% <0.00%> (-0.21%)
:arrow_down:

moto/ds/responses.py
100.00% <0.00%> (ø)

moto/ds/exceptions.py
100.00% <0.00%> (ø)

moto/cognitoidentity/responses.py
100.00% <0.00%> (ø)

moto/ds/validations.py
100.00% <0.00%> (ø)

moto/s3/responses.py
95.68% <0.00%> (+<0.01%)
:arrow_up:

moto/apigateway/exceptions.py
99.17% <0.00%> (+0.02%)
:arrow_up:

moto/__init__.py
98.49% <0.00%> (+0.03%)
:arrow_up:

moto/apigateway/models.py
93.33% <0.00%> (+0.03%)
:arrow_up:

... and 4 more

Continue to review full report at Codecov.

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


Building the plugin

Hi,
I am trying to follow the instructions in the README. While ./clang/setup.sh has been successful, I am unable to do a make test subsequently (CLANG_PREFIX points to the correct install directory within the repo). I get the following on a make test:
/Applications/Xcode.<IP_ADDRESS>C40b.app/Contents/Developer/usr/bin/make -C analyzer all make[1]: *** No rule to make target build/PluginMain.o', needed by build/FacebookAnalyzerPlugin.dylib'.  Stop. make: *** [all] Error 2
What needs to be done? I tried a cmake on the analyzer directory which doesn't help either.
Thanks,
M.
PS: Also, is there a mailing list to ask questions regarding the plugins?

CLANG_PREFIX should not be set
One of the included header files needs to be commented out

Thanks for posting the solution to your question :) What did you need to comment out?
Re: PS: there is no mailing list, feel free to open issues here to ask more questions.

I commented out #include "clang/Analysis/AnalysisContext.h" in analyzer/ObjCARCQualifierChecker.cpp


[Improvement][style] Add code import style automatic formatter

What is the purpose of the pull request
Add code import style automatic formatter for idea, it can automaticly help contributor to format the import to avoid a lot of changes about java code import
Brief change log

Add intellij-java-code-style.xmll

+1


FR: Support for file selection

Please consider adding the ability to select files, that's the only thing preventing me from switching to swiftDialog completely and letting go of cocoaDialog.
https://web.archive.org/web/20200628050802/https://cocoadialog.com/v2/#fileselect_control
Using a picker would be sufficient, but if it were possible to also drag and drop a file into the dialog as well, that would be fantastic.

what's the use case for file selection and how does it get used?
I'd expect that the all dialog would do is return the path of the file to your calling script. there's wouldn't be any validation done (that would be left up to the script).
I'm not super familiar how this was used in cocoadialog so want to make sure I understand the functionality.

I'd love to stop using Pashua for my on-prem Jamf Pro server deployment tool.
(I select a downloaded ROOT.war — and only .war files — which is then expanded and configured.)

My use case is a script in Jamf Self Service to allow users to install non-standard apps without admin rights. They need to be able to select the .app or .pkg they need installed.
Dragging and dropping a file into a text field works currently (i.e. the path is put into the field) if the text field is clicked on to select it first.
Honestly, I could get by with drag-and-drop into an existing text field if it wasn't required to click on it first, but having the actual file picker would be a bonus.

Nice! This will be a great addition to the tool.

--textfield "Pick an image (PNG),fileselect,filetype=PNG"
Example:

Quick question, what's the parameter name to specify the file selection button text? When we try your sample code the button reads "button-select"

I previously used CocoaDialog and Pashua for file selection but both are no longer in development. I have had to move to the homebrew version of Zenity, which has many overlapping features with swiftdialog. But I absolutely need a simple, elegant file and directory picker. swiftdialog's is not there yet. I can pick a file but it unnecessarily clutters the dialog box with a text field and prompts and buttons whereas the other 3 just pick a file or directory. Also, swiftdialog's directory selection is an afterthought (as the file selector seems to be as well), and I have not found a way to select ONLY directories with it. I will move from Zenity to swiftdialog in a flash if the file/directory picker problems are sorted out. But for now, this is a show-stopper.

Do what you need to do @precaf but just so you know, I'm not paid to write or maintain this project (other than what I get from my employer which I would get anyway whether I wrote this app or not). Barking commands like "do this or I go elsewhere" will do nothing to encourage anyone to help you.

Nobody is barking at you. You’ve got something that could be very useful for more than the niche admin user community if only an important use case were addressed. I’m already using Zenity. I’d switch if swiftDialog were usable. Sorry I hurt your feelings but that’s a very different message than "do this or I go elsewhere.”
On Mar 27, 2024, at 5:03 PM, Bart Reardon @.***> wrote:

Do what you need to do @precafhttps://github.com/precaf but just so you know, I'm not paid to write or maintain this project (other than what I get from my employer which I would get anyway whether I wrote this app or not). Barking commands like "do this or I go elsewhere" will do nothing to encourage anyone to help you.
—
Reply to this email directly, view it on GitHubhttps://github.com/swiftDialog/swiftDialog/issues/137#issuecomment-2023985975, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AXFASPVVNGBISI6VUCBBEJDY2MXZVAVCNFSM5ZNHNY6KU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMBSGM4TQNJZG42Q.
You are receiving this because you were mentioned.Message ID: @.***>

Don't worry, my feeling weren't hurt in the slightest. I'll let you know though that "I'll use your app if you would only do this one thing that several other apps do" is not the motivation you think it is - quite the opposite. I think it's a rude way to approach someone working for free on an app you didn't pay for.
If you have an idea for an improvement then I suggest you raise it as a seperate feature request (since this one was closed a while ago) detailing the layout or behaviour that you think would be beneficial. Don't include comparisons to other apps, just describe the behaviour.


support multi-level subdomains on *.now.sh

I'd like to alias foo.my-app to my my-app deployment on the default now.sh domain.
When attempting to do this in the web console, the following error message is rendered:

Multi-level .now.sh subdomain is not allowed.

It seems like there are many related issues but none (that I could find) that are asking for this ability --apologies if I overlooked a duplicate.
In an ideal world, I'd love to be able to request the entire wildcard when available, ie: *.my-app, but it's understandable if that's not possible.
what do y'all think? is there history / context for why this isn't supported?

This is a security issue because *.now.sh is shared between everyone using the platform.
However, you can use wildcards with your own domain.
See this blog post: https://zeit.co/blog/wildcard-domains

could you please provide a bit more color as to what the security risk is?
if I already have control of my-app.now.sh, how does preventing me from using foo.my-app.now.sh impact the security posture of the rest of the platform?
one of the reasons I'm interested in this is because it improves my ability to create more secure applications by imposing stricter controls/policies (eg: CSP, cookies, CORS).

I must have misunderstood.
There is already a feature for generating preview domains based on your project name and username as well as git branches. For example:
packagephobia.styfle.now.sh
packagephobia-git-master.styfle.now.sh

I will mark this as a feature request, thanks!

awesome, thank you! if there's anything I can do to assist, please let me know :smile:

Thank you for creating this issue!
Please note that – in order for us to be able to handle each feature request with care – we have to consume all of them through a unified pipeline that makes it easier for us to prioritize, track and progress on the features our user base is interested in.
In turn, the Issues tab on this repository is best only be used for reporting bugs, which we can immediately act on.
For well-explained feature requests (like the one you just posted), please contact us at<EMAIL_ADDRESS>so that we can consider adding it to our roadmap.


Move ReleaseDate field to locale manifest

Description of the new feature / enhancement
I know there are several packages which already have ReleaseDate in their installer manifest, so we may hold up until:

https://github.com/microsoft/winget-pkgs/issues/55921
https://github.com/microsoft/winget-pkgs/issues/125

are implemented.
ReleaseDate field should be in Locale manifest instead of Installer manifest. Here's why:

It's more related to "Package-Metadata" rather than the installer's (meta)data or properties.
ReleaseDate is for a specific version of a package and not for the installer.

Proposed technical implementation details
Make changes in the client🤔, schema, winget-create, and pipelines.

ReleaseDate is for a specific version of a package and not for the installer.

I disagree. I've seen a few times where the release date for an exe installer is not the same as the release date for an msi installer, even if they are the same package version.

It's more related to "Package-Metadata" rather than the installer's (meta)data or properties.

Again, I disagree, especially since we don't know how Channels will be implemented yet. A beta installer will most likely have a different release date than a stable installer. If "channel" is defined at the installer level, then release date also must be defined at the installer level.

Make changes in the client🤔, schema, winget-create, and pipelines.

This would be a breaking change anyways, and would have to wait until schema 2.0

I think in this case, I agree with @Trenly. The release date is per installer. I've seen cases where different architectures have different release dates for the same "version" of a package.


add drop, desc, show, rebuid index's validator and executor

still in progress

I will add tests in another pr


Changed getting started install doc to use pre alpha.

The Gemfile.lock still shows a prealpha version so changing the doc to follow along with that.

/lgtm
/approve

/lgtm


Helm Upgrade from 1.4.0 to 1.5.2 Fails with IngressClass Error

Attempting to upgrade from 1.4.0 to 1.5.2 with Helm fails with the following error:
Error: UPGRADE FAILED: unable to recognize "": no matches for kind "IngressClass" in version "networking.k8s.io/v1"
Also tried uninstalling 1.4.0 and installing 1.5.2 with Helm and received the same error.  Reinstall of 1.4.0 succeeded.
Kubernetes version:  1.18.14
Helm version:  3.8.2
See attached files for installation details.
ingress-details.txt
ingress-config.yaml.txt

This was due to 1.5.2 not being compatible with Kubernetes version 1.18.14.  Upgrade succeeds with Kubernetes 1.21.9.


If we dont find developers for Hornet Plugin in a reasonable timeframe - check if thoralfs solution can be extended with the functions we discussed

checked with thoralf and Muxxer. It is not a recommended way to continue on that and it will be not possible to speed up development going the permanode way


Updated to clean up scripts for NOT singularity

Updates from @AnikMumssen21 for singularity work.

@AnikMumssen21 Looks like there's a bug in the non-singularity path. I think I see the issue and we can fix it tomorrow.

Tested and the new autosite code (taken from gcm_setup) works! Woot!


Avoid hardcoded conversion to float32 in GraphBuilder

There were some places in the GraphBuilder that had a hard-coded conversion to float32. I added an init argument that now makes it possible to avoid this behavior completely. The lsl.Model likewise gains the to_float32 boolean flag as an argument, since if grow=True, the model internally uses a graph builder instance for growing.

@wiep thank you! I added the missing information to the docs.

See https://github.com/liesel-devs/liesel/issues/213 regarding the tests timing out.


Cannot render on server-side

Im trying to render application on server-side with React.renderToString method
https://github.com/mhart/react-server-example
and have got an error:
e:\repos\wt-site\node_modules\react-scroll\lib\mixins\cancel-events.js:6
			document.addEventListener(events[i], cancelEvent);
			^
ReferenceError: document is not defined
    at Object.module.exports.register (e:\repos\wt-site\node_modules\react-scroll\lib\mixins\cancel-events.js:6:4)
    at Object.<anonymous> (e:\repos\wt-site\node_modules\react-scroll\lib\mixins\animate-scroll.js:11:14)
    at Module._compile (module.js:456:26)
    at Object.require.extensions.(anonymous function) [as .js] (e:\repos\wt-site\node_modules\node-jsx\index.js:26:12)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (e:\repos\wt-site\node_modules\react-scroll\lib\mixins\Helpers.js:4:21)
    at Module._compile (module.js:456:26)

Interesting, actually never tried to render it server side. Seems like its looking for the DOM element when it does not exists. Not sure what the best solution is atm.

Here is a suggestion: add a check to see if DOM can be used
var canUseDOM = !!(
  typeof window !== 'undefined' &&
  window.document &&
  window.document.createElement
);

And mock document object in non-DOM environments.

yes, i did it in my fork:
https://github.com/juvty/react-scroll/commit/7f6d72353c290c19a796dd3c7767f1e1d4c9dd88

make a PR and will look at it :)

Should work now!

@fisshy
Hi all.
The following option:
var canUseDOM = !!(
  typeof window !== 'undefined' &&
  window.document &&
  window.document.createElement
);

has a conflict with a GSAP option for fixing Server-Side rendering:
http://greensock.com/forums/topic/7422-using-tweenlite-timelinelite-server-side-with-nodejs/
I think we need to use an another option in this library.


Problem when call to "/refresh"

As I see in spring-cloud/spring-cloud-netflix#196. This bug fixed.
I have zuul config
zuul:
  ignoredServices: '*'
  routes:
    admin:
      path: /admin/**
      stripPrefix: true
      serviceId: admin

I want to add a "pages" service like, and I add before path "/admin/**
zuul:
  ignoredServices: '*'
  routes:
    pages:
      path: /admin/pages/**
      stripPrefix: true
      serviceId: pages
    admin:
      path: /admin/**
      stripPrefix: true
      serviceId: admin

And POST to "http://localhost:8765/refresh"
It seem zuul not reload routes.
And I test, change it into
zuul:
  ignoredServices: '*'
  routes:
    admin:
      path: /admin/**
      stripPrefix: true
      serviceId: admin
    pages:
      path: /bla/pages/**
      stripPrefix: true
      serviceId: pages

Amazing, it works. Please tell me why doesn't it work if I add it before first routes
I must restart zuul, first case must work

I don't know why the second works, but the first doesn't.

It's almost 2 months since this was reported. It's more likely to be an issue in Spring Cloud Netflix than anything here, so I would recommend opening a new one there if there is something that needs to be fixed.

Ok. Now when I change zuul config, I must restart zuul :(

So open a new issue as suggested. Let's be frank about this though: it only affect new routes that are us paths of existing routes. You can add a new "normal" rout was far as I know.

I opened new issue here :)
https://github.com/spring-cloud/spring-cloud-netflix/issues/767


Fuzzing

In https://github.com/Zondax/filecoin-signing-tools/pull/551 we have removed the fuzzing code. When introducing the remote serde feature we removed the need for intermediary structure to convert from JSON to CBOR.
Therefore some of the fuzzing code wasn't relevant anymore. However we should not loose the fuzzing feature and would need to see where it is needed now.

:link: zboto Link

I have gone thru the codebase and, whilst I believe fuzzing is good, I doubt it would be very useful in the project.
If we were to fuzz the structures we'd basically be fuzzing serde, and the functionality provided by the main crate is simply a series of operation packages as a simple function, so there are no invariant being held by the library that would benefit from being fuzzed...
We'd simply be fuzzing the parsing being done by thirdy party crates etc. Most operations are fallible and errors are bubbled up, so if we fuzz we'd just be hitting a lot of these cases...


How to execute silently

I'm trying to execute rclone silently to have only execution log in a log file
Is it possible to have no output at all in the console?
I've tried without success:
rclone sync /mybackup/path remote:container --log-file="/var/log/rclone.log"

rclone sync /mybackup/path remote:container > "/var/log/rclone.log"

This should do the trick
rclone sync /mybackup/path remote:container > "/var/log/rclone.log" 2>&1

Thanks a lot!


Invariant Violation: requireNativeComponent: "VRTAmbientLight" was not found in the UIManager

"react": "17.0.1",
"react-native": "0.64.2",
"react-viro": "2.17.0",

Please Update to the Community Version of the Viro-react for react-native Latest Version Support. below is the Link : ->
https://github.com/ViroCommunity/viro


[mesheryctl] mesh validate response optimization

Description

./mesheryctl mesh validate -s smi -a meshery-osm:10009 -t ~/Downloads/auth.json is running but not connected to a kubernetes cluster.
Expected Behavior

Better response than empty {} to help user understand the issue well

@leecalcote need more context into this issue you were talking about


I'm writing height below display: inline-block, why does the style change like this?

I'm writing height below display: inline-block, why does the style change like this?

@VictorTolbert

what is the problem?

I'm writing height below display: inline-block, why does the style change like this?
image

It's more a CSS issue than a Nuxt issue. It seems the property is overriden. It's impossible to help you with just a screenshot of your code… 😉


Recovery alert

Feature Description
A user can optionally setup a recovery alert on a Vault. Only available from Pro version upwards.
The user will get notification by default on the main app if someone is trying to recover the wallet.They will have to approve, deny or do nothing. Do nothing will mean approval after 24 hours. For that time, the backend will not provide it with the metadata/ Wallet image and so they won't be able to recover the wallet.
They can decide to add other Keeper apps (contacts) or Signer Only Keepers (SOK) or email or phone number where they can get alert if someone is trying to recover. If none of them decline or all approve then they can recover. Else not.
This will feature in with the time lock option for Vaults (Vault settings?). And will be visible on the Vault HS symbol as it is a security aspect.
There will be a UAI for the user for this
Trigger pro Vault setup complete
Priority 20
Condition isRecoveryAlertSetup
**Pre-requisites/ dependencies
-Designs
-Research
-Discussion with a Senior
**Task Break Down
-TASK 1
-TASK 2
**Test Cases
**Design
**Flow
**ERD

We've implemented a version of this in the form of Canary Wallets.


Updated from <IP_ADDRESS> to <IP_ADDRESS> several errors when viewing admin console

Hello,
I have updated manually by uploading the the package into the app catalog from <IP_ADDRESS>
These are the errors I have when viewing the admin page
Message: TypeError: Cannot read property 'length' of undefined - DataService (refreshCache)
Message: CustomDataService (getCustomConfig) No configuration was found for CDN Default and Language fr-fr
Message: TypeError: Cannot read property 'length' of undefined - DataService (refreshCache)
Uncaught ReferenceError: exports is not defined
The second error is a bit strange because I have removed the FR language, just to get the upgrade working in EN - we will ultimately need FR
I have joined the error file
Thank you for your help
loccitanegroup.sharepoint.com-1608025414752.log
Alison

Deleted custom config, and seems to be working now


gitalk can NOT work without cors-anywhere

https://github.com/Rob--W/cors-anywhere/issues/301
gitalk can NOT work without cors-anywhere. Is there any way to fix it?

Need help on this problem as well

Forked https://github.com/Rob--W/cors-anywhere repo to host proxy on my own.
Changed the proxy url and got it fixed

solution: https://mp.weixin.qq.com/s/Lwl9rf95EqlTYLfconjflQ

solution: https://mp.weixin.qq.com/s/Lwl9rf95EqlTYLfconjflQ

https://github.com/Zibri/cloudflare-cors-anywhere

To create your own is very easy, you just need to set up a cloudflare account and upload the worker code.

不是很懂为什么一句话能解决的事情需要写一篇若干k的文章解决问题。

solution: https://mp.weixin.qq.com/s/Lwl9rf95EqlTYLfconjflQ

当然，谢谢你的热心。

@Germey 感谢老哥的文章，让我清晰认知到了这个问题出现的原因以及解决问题的长久之计，写得很详细，方案也很好，不用去修改 js 源码，文章很棒！

It will be a work-around, but if you are running on a platform that has a backend API such as Netlify or Vercel, you can create a backend and change the proxy as follows. I hope this is helpful.
API functions/src/cors-proxy-github.js
const axios = require('axios')

exports.handler = (event, context) => {
  const body = JSON.parse(event.body);
  const headers = {
    accept: 'application/json',
  };
  return axios.post('https://github.com/login/oauth/access_token', body, {headers: headers}).then((response) => {
    return {
      statusCode: 200,
      body: JSON.stringify({access_token: response.data.access_token, token_type: response.data.token_type, scope: response.data.scope}),
    };
  }).catch((error) => {
    return {
      statusCode: 500,
      body: JSON.stringify({error: error})
    }
  })
};

gitalk.jsx
  constructor (props) {
    super(props)
    this.options = Object.assign({}, {
      id: window.location.href,
      number: -1,
      labels: ['Gitalk'],
      title: window.document.title,
      body: '', // window.location.href + header.meta[description]
      perPage: 10,
      createIssueManually: false,
      proxy: 'https://blog.tubone-project24.xyz/.netlify/functions/cors-proxy-github',
      flipMoveOptions: {
        staggerDelayBy: 150,
        appearAnimation: 'accordionVertical',
        enterAnimation: 'accordionVertical',
        leaveAnimation: 'accordionVertical',
      },
      enableHotKey: true,

@tubone24
Thank you for you suggestion!!
I set up a worker on cloudflare to be my proxy. And my gitalk installed on my blog is working now.
https://github.com/Zibri/cloudflare-cors-anywhere

更新版本到 1.7.2 或者修改配置增加 proxy: 'https://cors-anywhere.azm.workers.dev/https://github.com/login/oauth/access_token'
需要动手的同学也可以参考楼上 @tubone24 @ShuYuMo2003 提供的方法自己搭建。


Does mmclassification support fine-grained classification?

If inscribe

We do not specifically support fine-grained classification.

@Ezra-Yu Thanks your reply.


Multiple deployments

This will require refactoring of the code to be less dependent on env variables, and more dependent on
dagster configs.
Multiple deployment of same PROJECT to same portainer
need to separate the PROJECT from the deployment. Right now, PROJECT is part of traefik labels, and PROJECT generates the code.
Let's change to DAG_PROJECT
Add DAG_DEPLOY variable so that we can deploy multiple dagsters on same portainer for same project.
use that in traefik labels. Maybe maybe container names.

"traefik.http.routers.sched-${DAG_DEPLOY:-deploy}.entrypoints=http"
the NETWORK and VOLUME shared with gleaner/nabu will need to be named for each 'stack'
Will need it's own network, so that it does not get confused (aka same containers on same network with same name...)
dagster_host:
driver: overlay
using project name is a bit tricky from dagster code, and needs to be external for a
container to use them
name: dagster-${DAG_DEPLOY:-deploy}
name: dagster_host
attachable: true
volume..
It think the postgres local volume is ok. It's defined as part of the stack, each stack separate
dagster-project:
external: true
name: dagster-${DAG_DEPLOY:-deploy}
#name: dagster_gleaner_configs

Dagster docker compose now use a project variable.


[FR] migrate atlas / template /parcellation / region to brainscapes api

main issue: https://github.com/HumanBrainProject/interactive-viewer/issues/889

Waiting for URL endpoint for precomputed volumes


Opening Kleki hyper lags my trackpad for a few minutes

I have no idea why Kleki and only Kleki does this, I am fully willing to accept that it might be on my end. When opening kleki, I'll suddenly have extreme lag when clicking on things (won't register clicks for a few seconds), and it flat-out won't let me click and drag to make strokes, or drag anything onto my canvas from my files. I'm on chrome and using a macbook.

Only extension I have is ublock origin, which I did disable and it didn't work. I'm currently using the newest version I believe (23-10-31). The lag is inconsistent so I'm unsure how to replicate it, but it tends to happen after an extended period.


Remove unused SASL attributes from sasl_passwd

'smtp_sasl_user_name' and 'smtp_sasl_passwd' turned up in
templates/sasl_passwd.erb's @settings.sort.map and wrongly
put into the configuration file as relayhost names.
Description
This brings file /etc/postfix/sasl_passwd back to the working format
before introducing the "multiple-relayhost-feature" in
https://github.com/chef-cookbooks/postfix/pull/134
Issues Resolved
https://github.com/chef-cookbooks/postfix/issues/148
Check List
Apologies, I just noticed this issue at a customers site and currently
have no way of testing it.

@k0ffee Can you sign this off for the DCO so I can merge it.

@tas50 done. This is green in travis now.
However, this fixes issue https://github.com/chef-cookbooks/postfix/issues/148 only.
I guess many people run into compatibility problems as described here:
https://github.com/chef-cookbooks/postfix/pull/134#issuecomment-396585275

Just curious - why it is not fixed yet? For almost half year we are living with broken cookbook, while PR is in the GitHub. @tas50  - it is time for action :)

@tas50 I'm seeing the same issue:
root@default-ubuntu-1804:/etc/postfix# cat /etc/postfix/sasl_passwd

# Auto-generated by Chef.
# Local modifications will be overwritten.

smtp_sasl_passwd :
smtp_sasl_user_name :

where for example say Sendgrid, it'd look like this:
[smtp.sendgrid.net]:587 yourSendGridUsername:yourSendGridPassword


Workspace fails to build

Using a fresh clone of Laradock as of today (25/04/2017), it fails to build workspace.
ERROR: Service 'workspace' failed to build: One or more build-args [INSTALL_LINUXBREW INSTALL_SOAP YARN_VERSION INSTALL_V8JS_EXTENSION INSTALL_LARAVEL_ENVOY INSTALL_MC INSTALL_DEPLOYER] were not consumed, failing build.
Using Ubuntu 17.04.

Confirmed, It seems the php71 container doesn't have soap (maybe others) in it's installation steps

Without a doubt, we should fix that. However, there may be another issue, as when I try to reproduce that issue, I'm getting an warning, not an error.
[Warning] One or more build-args [INSTALL_MC INSTALL_V8JS_EXTENSION INSTALL_LARAVEL_ENVOY INSTALL_LINUXBREW INSTALL_DEPLOYER YARN_VERSION INSTALL_SOAP] were not consumed

Should be fixed now 👍 Let us know if you're still experiencing issues.

i am getting the following error in ubuntu
Service 'workspace' failed to build: One or more build-args [INSTALL_MSSQL] were not consumed, failing build.

Moved to #895

Hi @aft3rlife  Please upgrade docker version > 1.13
https://github.com/moby/moby/pull/27412


feat(grid layout generators): CSS layout generation has been created

CSS grid layout generation has been created
The number of rows and columns for the grid can be obtained from the user's input, and it can be previewed in CSS grid preview, User can get the CSS code and tailwind class for the generated CSS grid
Resetting inputs will clear the preview
I have put CSS grid generation under CSS layout generation list, because in future, we can add other layouts under CSS layout generation list
Features planned to add in the future
Column gap and row gap can be added to generate a CSS grid more accurately
Fixes Issue
My PR closes #434
👨💻 Changes proposed(What did you do ?)
✔ Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title and description of the PR is clear and explains the approach.

Note to reviewers

📷 Screenshots
Initial stage

When entering the number of rows and columns

After copying the CSS code

@Thilakmani-dev you have an error to fix:

and your PR description too

@Thilakmani-dev you have an error to fix:
and your PR description too

i have checked that, fixing this @Dun-sin , thanks for mentioning that

@Thilakmani-dev you have an error to fix:
and your PR description too

done

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

You did great, thanks for contributing, I hope you will stick around and continue to contribute to this project.
Consider giving this project a star and joining the community discord server for more resources and opportunities to connect with others. 👉🏽here👈🏽

Yes i will @Dun-sin , thanks for giving me this opportunity to contribute


Upgrade Jenkins core version to 2.426.3

Description
Upgrade Jenkins core version
Issues Resolved
https://github.com/opensearch-project/opensearch-ci/issues/389
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Hi @Divyaasm Can you see if you can remove org.jenkins-ci.plugins dependencies? We added some of them to resolve the CVEs but since overall we are bumping the version, I don't think they are valid anymore.

Hi @Divyaasm Can you see if you can remove org.jenkins-ci.plugins dependencies? We added some of them to resolve the CVEs but since overall we are bumping the version, I don't think they are valid anymore.

Sure, will take a look.

Hi @Divyaasm Can you see if you can remove org.jenkins-ci.plugins dependencies? We added some of them to resolve the CVEs but since overall we are bumping the version, I don't think they are valid anymore.

Hey @gaiksaya, tried by removing the dependencies, I've noticed that an older version than previously specified is being pulled. Shall we move forward with the current changes?

Hi @Divyaasm Can you see if you can remove org.jenkins-ci.plugins dependencies? We added some of them to resolve the CVEs but since overall we are bumping the version, I don't think they are valid anymore.

Hey @gaiksaya, tried by removing the dependencies, I've noticed that an older version than previously specified is being pulled. Shall we move forward with the current changes?

Sure! Thanks!

@Divyaasm @gaiksaya Should this change be backported ?

@Divyaasm @gaiksaya Should this change be backported ?

Yes! Thanks!


0.8.6: TypeError: Cannot read property 'pingTimer' of undefined

node_modules/nats/lib/nats.js:641:13

@zpr  what version of the library?
In master the code looks valid.

@zpr - Please attach a stack trace. Thanks.

Just downloaded the master as the npm version is 0.8.4 not 0.8.6. Same issue in both.
TypeError: Cannot read property 'pingTimer' of undefined
at Client.close (node_modules/nats/lib/nats.js:641:13)
at Timeout._onTimeout (node_modules/nats/lib/nats.js:1355:13)
at ontimeout (timers.js:458:11)
at tryOnTimeout (timers.js:296:5)
at Timer.listOnTimeout (timers.js:259:5)
node -v
v9.5.0

@zpr - Not quite sure how you are getting to close() when the client is null. Can you show me callbacks where you are calling close().

@zpr - No replies to the queries, so I am assuming the issue is resolved. If not please reopen and provided the requested information. Thanks.


add some resources to the docs

@jaimergp found this https://cheatsheetseries.owasp.org/cheatsheets/Secrets_Management_Cheat_Sheet.html
We should curate some trusted resources in the readme maybe?

Another https://github.com/ossf/wg-securing-software-repos


error: command 'g++' failed with exit status 1 with the last step pip install -v -e .  # or "python setup.py develop"

I strictly follow the getting_started.md, with cuda 10.1, pytorch 1.5.0, however there is always the g++ error said no some .o file, but i think there is no wrong operation with my compiling process:
g++: error: /home/mm/new/mmdetection3d/build/temp.linux-x86_64-3.7/mmdet3d/ops/spconv/src/all.o: No such file or directory
g++: error: /home/mm/new/mmdetection3d/build/temp.linux-x86_64-3.7/mmdet3d/ops/spconv/src/reordering.o: No such file or directory
g++: error: /home/mm/new/mmdetection3d/build/temp.linux-x86_64-3.7/mmdet3d/ops/spconv/src/reordering_cuda.o: No such file or directory
g++: error: /home/mm/new/mmdetection3d/build/temp.linux-x86_64-3.7/mmdet3d/ops/spconv/src/indice.o: No such file or directory
g++: error: /home/]mm/new/mmdetection3d/build/temp.linux-x86_64-3.7/mmdet3d/ops/spconv/src/indice_cuda.o: No such file or directory
g++: error: /home/mm/new/mmdetection3d/build/temp.linux-x86_64-3.7/mmdet3d/ops/spconv/src/maxpool.o: No such file or directory
g++: error: /home/mm/new/mmdetection3d/build/temp.linux-x86_64-3.7/mmdet3d/ops/spconv/src/maxpool_cuda.o: No such file or directory
error: command 'g++' failed with exit status 1
ERROR: Command errored out with exit status 1: /home/pkudba/.conda/envs/new_open-mmlab/bin/python -c 'import io, os, sys, setuptools, tokenize; sys.argv[0] = '"'"'/home/pkudba/mm/new/mmdetection3d/setup.py'"'"'; file='"'"'/home/pkudba/mm/new/mmdetection3d/setup.py'"'"';f = getattr(tokenize, '"'"'open'"'"', open)(file) if os.path.exists(file) else io.StringIO('"'"'from setuptools import setup; setup()'"'"');code = f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' develop --no-deps Check the logs for full command output.

I think you may need to rebuild MMDetection3D:
pip uninstall mmdet3d
rm -rf ./build
find . -name "*.so" | xargs rm

I think you may need to rebuild MMDetection3D:
pip uninstall mmdet3d
rm -rf ./build
find . -name "*.so" | xargs rm

thank you, but actually my problem is that i can't successfully install mmdet3d(the last compiling step failed), so there is nothing for me to  pip uninstall...

Sorry, could you please run python mmdet3d/utils/collect_env.py to collect necessary environment infomation?

Close due to inactivity.


Make Analytics opt-in

I would suggest opt-out.  Have it selected by default.

I'd rather have it an encouraged opt-in during the intro, telling the user that they won't get any support if they run into problems without analytics enabled. This way most people will activate it (because it takes less clicks), but F-Droid still wont give a large red warning that we are actively tracking users, because it is still opt-in.

Make sense, I didn't grasp the FDroid constraint.
On 30 March 2017 at 10:57, Jan Christian Grünhage<EMAIL_ADDRESS>wrote:

I'd rather have it an encouraged opt-in during the intro, telling the user
that they won't get any support if they run into problems without analytics
enabled. This way most people will activate it (because it takes less
clicks), but F-Droid still wont give a large red warning that we are
actively tracking users, because it is still opt-in.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/jcgruenhage/PlayMusicExporter/issues/30#issuecomment-290361740,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACuadQ-Uw-F3O9Le4jolciVIHr1VEEgwks5rq3x1gaJpZM4MuGZC
.

Have a loot at this: https://f-droid.org/repository/browse/?fdfilter=anecdote&fdid=io.gresse.hugo.anecdote
That keeps people from using it ^^

Now the only thing still missing is opt-out in the settings.

The warning on F-Droid actually went live some time ago, so this is a little more urgent now then before, when the F-Droid people didn't realize this yet.


fix: duplicated bindings in the activity API

Changes

Add RgbppCollector.isIsomorphicTx() method to help validate isomorphic transactions in depth and fix the duplicated binding recognization issue in RgbppCollector.queryRgbppLockTxByBtcTx

Previously mentioned in #193

Fix the validate logic of RgbppCollector.queryBtcTimeLockTxByBtcTxId()

Previously mentioned in #193

Rename ckbRawTx to ckbVirtualTx in the IsomorphicTransaction type

Originally commented at https://github.com/ckb-cell/btc-assets-api/pull/182#discussion_r1679050841

TODO

[x] Test: query L1-L1 transactions

Query via route: /rgbpp/v1/address/tb1qrkh7g0gkllttvsu9kzm7f5c25agnj8ype88xsg/activity
View transaction on RGB++ Explorer

[x] Test: query L1-L2 transactions

Query via route: /rgbpp/v1/address/tb1qrkh7g0gkllttvsu9kzm7f5c25agnj8ype88xsg/activity
View transaction on RGB++ Explorer

[x] Test: query L1-L1/L2-l1 multi-bound UTXO

L1-L1 that generates a new UTXO a986...245c:1

Query via route: /rgbpp/v1/address/tb1ql4rmhtkzdf043cq4a876y2fsq6wqqh02njwsf7/activity
View transaction on RGB++ Explorer

L2-L1 that leaps asset to the same UTXO a986...245c:1

View transaction on RGB++ Explorer

Issues

We can only reverse search L1-L1 and L1-L2 transactions with BTC TxIds, as only these types of transactions will ensure at least one rgbpp-lock cell is included in the inputs. For other types of transactions, we will have trouble identifying duplicated binding assets in them.
The RgbppCollector.queryBtcTimeLockTxByBtcTxId() method has an issue where the CkbIndexer.getTransactions() method requires manual pagination. This part is currently missing in the codebase, so the method only searches the first 100 records in the blockchain, causing inaccurate matching results of the btc-time-lock transactions.
related issue: #45

@ahonn IS_MAINNET and TESTNET_TYPE are created in the constants.ts file to simplify things. If you are okay with the constants, I can create another PR to refactor the codebase to use these constants instead of using env.NETWORK everywhere:
-env.NETWORK === NetworkType.mainnet.toString()
+IS_MAINNET

@ahonn IS_MAINNET and TESTNET_TYPE are created in the constants.ts file to simplify things. If you are okay with the constants, I can create another PR to refactor the codebase to use these constants instead of using env.NETWORK everywhere:

-getXScript(env.NETWORK === NetworkType.mainnet.toString())

+getXScript(IS_MAINNET)

LGTM

The preview deployment is ready. 🟢
Open Preview

Hi, @Dawn-githup
https://194.assets-api-342ddd42.nip.io/docs is the PR preview link for testing.

curl 'https://btc-assets-api-git-fix-182-duplicated-bindings-cell-studio.vercel.app/rgbpp/v1/address/tb1q4vsuv95gdum3cdrswujv9qzqf72ehqxh7vhhak/activity?rgbpp_only=false' \

It is recommended to cache the data. It takes a long time to check the data now.

The preview deployment is ready. 🟢
Open Preview

Hi, @Dawn-githup https://194.assets-api-342ddd42.nip.io/docs is the PR preview link for testing.
Related test

feat: add rgbpp address activity api  #182 (comment)

updated
https://github.com/ckb-cell/btc-assets-api/pull/182#issuecomment-2303873618


The steps described in Build a React App don't work

File: runtime/tutorials/how_to_with_npm/react.md
> deno run -A npm:create-vite@latest --template react-ts
✔ Project name: … test-project

Scaffolding project in /Users/***/***/***/test-project...

Done. Now run:

  cd test-project
  npm install
  npm run dev

> cd test-project/

> deno install
error: npm package '@rollup/rollup-freebsd-arm64' does not exist.

> deno task dev
Task dev vite
vite: command not found

> deno --version
deno 2.0.3 (stable, release, aarch64-apple-darwin)
v8 <IP_ADDRESS>-rusty
typescript 5.6.2

I am running it on macOS 14.7 (23H124) Darwin 23.6.0 arm64

It depends on rollup-linux-x64-gnu add it as an optional Dependency it should resolve the problem
Append this to the package.json
"optionalDependencies": {    "@rollup/rollup-linux-x64-gnu": "4.6.1" }


Gh 882 speed up build

Codecov Report

Merging #958 into develop will increase coverage by 0.78%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             develop     #958      +/-   ##
=============================================
+ Coverage      62.77%   63.56%   +0.78%
- Complexity       909     3099    +2190
=============================================
  Files            480      480
  Lines          13900    13900
  Branches        1577     1577
=============================================
+ Hits            8726     8835     +109
+ Misses          4545     4428     -117
- Partials         629      637       +8

Impacted Files
Coverage Δ
Complexity Δ

...gaffer/rest/service/GraphConfigurationService.java
90.14% <0%> (+1.4%)
24% <0%> (+24%)
:arrow_up:

...uk/gov/gchq/gaffer/proxystore/ProxyProperties.java
44.82% <0%> (+44.82%)
17% <0%> (+17%)
:arrow_up:

...java/uk/gov/gchq/gaffer/proxystore/ProxyStore.java
69.49% <0%> (+69.49%)
30% <0%> (+30%)
:arrow_up:

Continue to review full report at Codecov.

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


Bump to elasticsearch 7

@adrianlzt Could you please give this one a try ? Thanks !

I have tested with ES 7.7 and looks good.
FYI, from version 6.8 exists ILM that allows to manage the lifecycle of index (rotate by size/age and delete by age).

What about putting this into scripts/ci/run-tests-utils.sh ?
function es_setup {
    docker run -d --name elasticsearch  -p 9201:9200 -p 9301:9300 -e "discovery.type=single-node" elasticsearch:7.7.1
}

function es_cleanup {
    docker stop elasticsearch
    docker rm elasticsearch
}

if [ "$BACKEND" = "elasticsearch" ]; then
    es_setup && trap es_cleanup EXIT
fi

I could say that I did it this way because I wanted to test but actually I was too lazy :) Thanks for the script


Android 4.1.2: can't find source for layer 'mapbox-location-bearing-layer'

Originally posted in navigation repo https://github.com/mapbox/mapbox-navigation-android/issues/533
This only seems to be happening on Android 4.1.2 Device see Logcat Below
Logcat
11-23 11:43:30.307 21616-21872/uk.co.ainscough.routeinfo W/mbgl: {Thread-4689}[Render]: can't find source for layer 'mapbox-location-bearing-layer'
11-23 11:43:30.317 21616-21872/uk.co.ainscough.routeinfo W/mbgl: {Thread-4689}[Render]: can't find source for layer 'mapbox-location-bearing-layer'
11-23 11:43:30.337 21616-21872/uk.co.ainscough.routeinfo W/mbgl: {Thread-4689}[Render]: can't find source for layer 'mapbox-location-bearing-layer'
11-23 11:43:30.347 21616-21872/uk.co.ainscough.routeinfo W/mbgl: {Thread-4689}[Render]: can't find source for layer 'mapbox-location-bearing-layer'
11-23 11:43:30.357 21616-21872/uk.co.ainscough.routeinfo W/mbgl: {Thread-4689}[Render]: can't find source for layer 'mapbox-location-bearing-layer'
11-23 11:43:30.377 21616-21872/uk.co.ainscough.routeinfo W/mbgl: {Thread-4689}[Render]: can't find source for layer 'mapbox-location-bearing-layer'
11-23 11:43:30.387 21616-21872/uk.co.ainscough.routeinfo W/mbgl: {Thread-4689}[Render]: can't find source for layer 'mapbox-location-bearing-layer'
11-23 11:43:30.407 21616-21872/uk.co.ainscough.routeinfo W/mbgl: {Thread-4689}[Render]: can't find source for layer 'mapbox-location-bearing-layer'
11-23 11:43:30.417 21616-21872/uk.co.ainscough.routeinfo W/mbgl: {Thread-4689}[Render]: can't find source for layer 'mapbox-location-bearing-layer'
11-23 11:43:30.438 21616-21872/uk.co.ainscough.routeinfo W/mbgl: {Thread-4689}[Render]: can't find source for layer 'mapbox-location-bearing-layer'
11-23 11:43:30.448 21616-21872/uk.co.ainscough.routeinfo W/mbgl: {Thread-4689}[Render]: can't find source for layer 'mapbox-location-bearing-layer'
11-23 11:43:30.468 21616-21872/uk.co.ainscough.routeinfo W/mbgl: {Thread-4689}[Render]: can't find source for layer 'mapbox-location-bearing-layer'
11-23 11:43:30.478 21616-21872/uk.co.ainscough.routeinfo W/mbgl: {Thread-4689}[Render]: can't find source for layer 'mapbox-location-bearing-layer'

This is just constantly filling up the logcat.
Gradle Config
// Mapbox Maps SDK
    implementation 'com.mapbox.mapboxsdk:mapbox-android-plugin-traffic:0.3.0'
    implementation ('com.mapbox.mapboxsdk:mapbox-android-navigation-ui:0.7.1-SNAPSHOT') {
        transitive = true
    }

@cammace is this still an issue?

While I'm unable to physically check, the location source which the bearing layer uses is the same as all the other layers in the latest release. Therefore, I think we are safe to close unless @Danny-James is still having problems here.


Create branch & Preview URL for redesign work

Done, thanks @ladytrekker
https://github.com/KlimaDAO/klimadao/tree/site-redesign
Live preview URL for branch (don't tweet this please lol)
https://klimadao-site-git-site-redesign-klimadao.vercel.app/

Created in #69


Draft: Generalize dirEntries to take a DirEntry predicate as parameter

The current state of dirEntries is not generic enough because it cannot traverse any directory tree X (via SpanMode.depth) without having to traverse all sub-directories of X such as .git directory trees.
Adding a template parameter
alias pred  = (scope DirEntry entry) => true

to dirEntries alleviates this problem.
No tests yet and no template restriction enabled yet because I'm uncertain if we should require the pred to take the DirEntry by ref or not given that DirEntry.sizeof is 156.
Moreover, it's unfortunate that the template parameter useDIP1000 was recently added to
dirEntries(bool useDIP1000 = dip1000Enabled, alias pred = (scope DirEntry entry) => true)

as I presume that pred is gonna be a much more common non-default template parameter than then useDIP1000 is gonna be.
Shall we add a new function say treeEntries, dirTreeEntries, dirEntriesTree or dirEntriesFiltered or whatever instead so we can make pred the first template parameter?
Note that DirEntry member
@property bool isDir() scope

is non-const on posix so that pred cannot be
(const scope DirEntry entry) => true

in the general case. Will add documentation and tests when we have settled on solutions to these issues.
For the corresponding filtering in Rust see https://crates.io/crates/walkdir section "Example: skip hidden files and directories efficiently on unix".

It's unforunate that the template parameter useDIP1000 was recently added to
dirEntries(bool useDIP1000 = dip1000Enabled, alias pred = (const scope ref DirEntry entry) => true)
as I presume that pred is gonna be a much more common non-default template parameter than then useDIP1000 is gonna be.
Shall we add a new function say dirTreeEntries or dirEntriesFiltered or whatever instead?

Moreover, it's unfortunate that the template parameter useDIP1000 was recently added

I don't think you need to worry about breakage when moving that to last position of the parameter list. The documentation says "set automatically - do not touch", it asserts null if set against what the compiler switch says, and it has existed for only a short while.

I don't think you need to worry about breakage when moving that to last position of the parameter list. The documentation says "set automatically - do not touch", it asserts null if set against what the compiler switch says, and it has existed for only a short while.

Great. Will adjust then.

Needs tests.

Lots of seemingly unrelated CI errors...

The predicate should not be a template parameter.
It increases symbol count, and prevents configurability at runtime.

@nordlow if you could add some documentation and a chengelog entry to this we can definitely merge this

What shall the default value of the predicate be? The one that I provided with DirEntry passed as ref or simply pred = void?

If null, old behavior. If non-null call it.

If null, old behavior. If non-null call it.

I believe it's more common practise to default predicate lambda parameters to void instead of null. With defaulting to void
we can use static if (is(pred ==)). Why not simply use the

If null, old behavior. If non-null call it.

I believe it's more common practise to default predicate lambda parameters to void instead of null. With defaulting to void
we can use static if (is(pred ==)).
Alternatively
alias pred = (scope ref DirEntry entry) => true
could be used.

All of which are related to template parameters. My comment was about converting it to a function parameter.

If null, old behavior. If non-null call it.
All of which are related to template parameters. My comment was about converting it to a function parameter.

Ahh. I see.

Shall
private struct DirIteratorImpl
{
    bool delegate(scope ref DirEntry entry) pred;

    this(bool delegate(scope ref DirEntry entry) pred)
    {
        this.pred = pred;
    }
    ....

be used?

It would need to be @safe (none others are needed here I think).


Fix failing ITBigQueryTest.testUpdateNonExistingTable

There's a test failing in Travis (my bad). The failing test is ITBigQueryTest.testUpdateNonExistingTable
java.lang.AssertionError: null
	at org.junit.Assert.fail(Assert.java:86)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at org.junit.Assert.assertNotNull(Assert.java:712)
	at org.junit.Assert.assertNotNull(Assert.java:722)
	at com.google.gcloud.bigquery.ITBigQueryTest.testUpdateNonExistingTable(ITBigQueryTest.java:465)

The line failing is the following:
assertNotNull(error.debugInfo());

It seems that debugInfo is not available. Noticeably this error never happened to me locally. This PR should fix this error even though I am unsure why it even happens.

Debug information is only provided by the service internally (IP, users,...).


"allOf" renders incorrect HTML doc

I have tried to use the online "playground" (http://bootprint.knappmeier.de/) to generate HTML docs for the following Swagger specification:
{
  "swagger" : "2.0",
  "info" : {
    "description" : "TODO",
    "version" : "0.0.1",
    "title" : "API Spec",
    "termsOfService" : "TODO"
  },
  "basePath" : "/v1",
  "schemes" : [ "http", "https" ],
  "paths" : {
    "/aaa" : {
      "post" : {
        "tags" : [ "AAA" ],
        "summary" : "TODO",
        "description" : "TODO",
        "operationId" : "aaa",
        "consumes" : [ "application/json", "application/xml" ],
        "produces" : [ "application/json", "application/xml" ],
        "parameters" : [ {
          "in" : "body",
          "name" : "body",
          "description" : "TODO",
          "required" : true,
          "schema" : {
            "$ref" : "#/definitions/AAA"
          }
        } ],
        "responses" : {
          "200" : {
            "description" : "Authentication was successful"
          },
          "405" : {
            "description" : "Invalid data"
          }
        }
      }
    }
  },
  "definitions" : {
    "AAA" : {
      "allOf" : [ {
        "$ref" : "#/definitions/BBB"
      }, {
        "type" : "object",
        "properties" : {
          "ttt" : {
            "type" : "string"
          }
        }
      } ]
    },
    "BBB" : {
      "allOf" : [ {
        "$ref" : "#/definitions/CCC"
      }, {
        "type" : "object",
        "properties" : {
          "vvv" : {
            "type" : "string"
          }
        }
      } ]
    },
    "CCC" : {
      "type" : "object",
      "properties" : {
        "uuu" : {
          "type" : "string"
        },
        "ppp" : {
          "type" : "string"
        }
      }
    }
  }
}

I really like the generated API docs, but unfortunately the objects AAA and BBB appear to be empty although they both contain properties.
Clearly, it seems like the use of allOf is not properly handled by bootprint-swagger.
If I convert the JSON specification to YAML and paste it to the Swagger Editor (http://editor.swagger.io/) then the objects AAA and BBB are correctly displayed.

Mhm, I have to check why this happened. I had this working already, but I didn't have tests. Time to write some...

I will gladly volunteer to test an early fix.
:)

Should be fixed with<EMAIL_ADDRESS>This was a regression introduced in<EMAIL_ADDRESS>along with the fix for #26.
I've taken the liberty to create a testcase based on your example. I hope it is OK to include it in the project (which is licensed under MIT-license). Otherwise please tell me (here or by e-mail) and I'll write my own example.
Can you verify the fix?

The fix is not on the playground yet. Give me a couple of minutes.

Now its there

It's fine to use my example in the test.
I will make a test of the fix tomorrow morning.
Thanks!

I have tested the 0.9.1 version with my real Swagger Specification and it seems to work fine.  :smiley:
Thanks a lot for the quick response!


Return table from plugin

Support for returning table from plugin.
Updated protocol with TableDescription.
Python Examples updated with examples of returning a table.
Prepared for release of version 1.1.0.
Status
[ ] Under development
[x ] Waiting for code review
[x ] Waiting for merge

Information
[ ] Contains breaking changes
[x ] Contains new API(s)
[x ] Contains documentation
[x ] Contains test
[x ] Contains examples

To-do list
[ ] [Fix this thing]
[ ] [Fix another thing]
[ ] ...

For your information, the commits will be squashed later today.

Please note that the history of the branch is rewritten due to my cleanup of all commits. If you plan to make any changes, make sure your local repository is updated with the latest changes. Thanks!


resolves ens domains in snapshot

we can't do this because it'd hit rate limit

Is this no longer in review @jakeloo ?

Going to close this for now, we'll re-open it when we have a better solution for dealing with provider rate limit issue.


Cannot find module 'react-native-collapsible/Accordion'

I am getting same issue in "react-native-collapsible": "^1.2.1",

Can you post a screenshot of the actual error

I am not using this plugin now but it was showing issue .

I am not understanding. Where/how did you see this error?

Closing as inactive. Feel free to message or create a new issue if this is still a concern.

I think he is talking about this:

It's a default export.  See readme https://github.com/oblador/react-native-collapsible#accordion-usage
import Accordion from 'react-native-collapsible/Accordion'


Make outbounds a shared memory Value (multiproc branch)

See the numaccept variable as an example.

Edit: must be an Array, not a Value.  One value for each free parameter.


document IIFE bundle format used by spago bundle-app

With the purs-nix default bundle format ESM, the bundle produced by purs-nix did not immediately work as a replacement for the bundle produced by spago bundle-app. I realize now that spago uses a different bundle format by default: https://esbuild.github.io/api/#format-iife

Some more validation that spago uses IIFE:

https://github.com/purescript/spago/blob/310a7096b0d3e86f6464c667aa2339045d85d505/src/Spago/Build.hs#L435
https://github.com/purescript/spago/blob/310a7096b0d3e86f6464c667aa2339045d85d505/CHANGELOG.md#0209---2022-05-03
https://github.com/purescript/spago/pull/880

@ursi , would you review this? I think it will help anyone who replaces Spago with purs-nix. Thanks

Hi Peter, yes, sorry. I don't like documenting it this way because it feels incomplete to me to list just one thing from the esbuild flag when there are so many others. That being said, I do think this is valuable information. What do you think about making a section in the docs somewhere about migrating from spago?

Good point, how about https://github.com/purs-nix/purs-nix/blob/98d9531b4907a0ff0c0c63853fdfa8b17b56a663/README.md#migrating-from-spago

looks good to me!

Thanks


Segmentation backfill running from oldest GA event data plus interval date.

For the segmentation data backfills, the start of the date range for the look back is running from the earliest data that has GA data available plus the number look back interval days. This range doesn't seem like what we want to train on. It seems like we would want to backfill on the current date, minus the number of days in the look back interval.
This line of SQL determines the start date:
https://github.com/GoogleCloudPlatform/marketing-data-engine/blob/37c5635af74c2ffe7794496a7244a947d8440a55/sql/query/invoke_backfill_user_segmentation_dimensions.sqlx#L20
For instance, as of now, given these parameters:
GA data available in BQ : 7/19/23 - 8/9/23
Interval Min Date : 15
The backfill SQL populates with a start date of : 8/3/23
This would only give us 6 days of data.
What I would expect:
GA data available in BQ : 7/19/23 - 8/9/23
Interval Min Date : 15
The backfill SQL populates with a start date of : 7/26/23
This would give us 15 days of data.
If I'm misunderstanding what data should be available after the backfill let me know, but right now it's trimming what could be useful input data.

This issue is being addressed by a new PR #35 that I'm opening.

@danchapman the way the backfill dates are calculated now, this is the range:

What you're proposing is:

It is not 15 days of data that your logic returns. Because we only have 22 days of data and we need to lookback (for segmentation) 15 days of interval. We can only give 7 steps in the past until we get to the beginning of the interval.


Shebang is wrong

Expected:
#!/usr/bin/env node

Actual
#! ?/,"").split(" "),u=n[0].split("/").pop(),a=n[1];return"env"===u?a:u+(a?" "+a:"")};

I'm using v1.2.8

@arnohovhannisyan what was/is your parcel-bundler version in this case?

@cyntl3r At the time, it was probably ^1.12.3. I'm not sure it still happens with the current version, but I'll test it out as soon as I can.

@cyntl3r I can confirm that this issue still exists with the newest version of Parcel, but only on this project.


Use the component to obtain the battery information of the device corresponding to bluetooth, please help, thank you

I want to use the service to obtain the electric quantity information corresponding to bluetooth device, using the headset of the latest version 5.2 of Bluetooth. Under the platform of WIN11 operating system, the electric quantity information can be displayed normally, but I use the debugging software "nRF Connect" of mobile phone, and the screenshot is as follows. How do I obtain the electric quantity information of Bluetooth device now? Please give me an example. Thank you.
**

**

If it supports the Battery service it will have a service with id 0x180F. The characteristic 0x2A19 contains a single byte with the battery percentage,

However, some (such as the part of my screenshot) do not have this service, but the bluetooth list of WIN11 can display the battery information, may I ask, is there any other way?


Very little space for actual content on iPhone landscape

More than half of the screen is being occupied by elements you cannot scroll away.

Preparing designs for it...

So the new designs for mobile landscape: https://app.zeplin.io/project/5a8e8992554d385c76ad5aeb/dashboard?seid=5b1fd052e02db4652256c1da
while scrolling it should hide the header: https://zpl.io/25qNRWe

Cool! Thanks

there are new designs for that, closing issue.


Update distribution package for name regexp change

Pick up name regexp change in distribution to allow matching of hostnames as a valid component of a repository. This should only expand the set of valid names and provide no further restrictions.
ping @mattmoor

Thanks! LGTM

Thanks @dmcgowan LGTM.

Please don't merge: holding for @stevvooe who believes we shouldn't allow for repeating ..

@icecrime I don't understand your comment, this doesn't allow for repeating (consecutive) . or _, just consecutive -.  Is that what you meant?

@icecrime Stephen's comment was in response to someone else asking about repeated ., we had since confirmed that it is not allowed and this change only allows repeated -.

Ok my bad, thanks! :+1:

LGTM


Added support for tcp proxyProtocol v1&v2 to backend

What does this PR do?
added a "proxyProtocol" struct with a version setting to loadbalancer config to allow injecting the proxyprotocol v1 or v2 headers to a tcp backend connection. updated crds
"" disable (default)
"1" use proxy protocol version1 (human readable format)
"2" use proxy protocol version2
with version 2 its possible to also add tls infos. but in this implementation only the source ip+port and dst ip+port is added.
What else does this PR do?
we also change the Listenercode to only use one proxyprotocol library: dropped c0va23/go-proxyprotocol for pires/go-proxyproto
Motivation
Currently there is no backend proxy protocol support, without this its not possible to forward smtp via tcp without loosing the client IP (its needed for detecting spam e.g.), with this postfix can be used in kubernetes with traefik as ingress tcp loadbalancer.
Fixes #5371
More

[x] Added/updated tests
[x] Added/updated documentation

Additional Notes

the alternative "config" solution would be to change the setting from boolean to "proxyProtocolVersion int"
0 disable (default)
1 could be proxy protocol version1
2 could be proxy protocol version2
the current implementation does not require external libs. to support version 1&2 i would use github.com/pires/go-proxyproto
If this gets accepted i can implement this.
Adding TLS/SSL infos to the v2 impl. is complicated because i didnt see a way to get the TLS informations

Its done, please review

@ldez do you have time to review this? Its a long wanted feature

Hello,
Your PR has been classified with the status/1-needs-design-review:  this label is assigned on PR with a scope of impact that we considered as significant.
So it means that the review cycle will be longer than a more "basic" PR.
FYI, at this stage, before the evaluation by the team, a PR can be refused because of design considerations.
https://doc.traefik.io/traefik/v2.3/contributing/submitting-pull-requests/#pr-content
https://doc.traefik.io/traefik/v2.3/contributing/maintainers/#status-workflow

@mschneider82  Thanks for your work on this PR!
As said in the original issue, Traefik supports being behind a proxy using the Proxy protocol. This behavior, as you probably seen, is configurable on the entrypoints and we are using the c0va23/go-proxyprotocol package for providing a Proxy protocol capable listener.
You did a great job on this PR but we would like to keep only one Proxy protocol dependency. That being said, your chosen dependency pires/go-proxyproto would be suitable for all our needs as it supports both client and server side. After reviewing it, it appears to be a great choice from a spec compliance and extensibility perspective.
Could you update the Proxy protocol listener? https://github.com/traefik/traefik/blob/b5198e63c446efdb488abd2bea826a59f75b1d63/pkg/server/server_entrypoint_tcp.go#L358-L385
Some changes will be required for replacing the package. pires/go-proxyproto supports Policies which is a good replacement for the WithSourceChecker(sourceCheck).

I thought about changing the listener too, but I didn't want to make this PR too big (its already not small). If it's ok for you i will do it here

@mschneider82 Yes it would be great. Thanks again for your time. Don't hesitate if you need some help.

I think this is what we need for our use-case, but want to make sure. We currently have Traefik sitting behind an AWS Classic LB with ProxyProtocol v2 enabled. With the --entryPoints.web.proxyProtocol.insecure CLI option in testing, we're not seeing the client IP passing through to our service with a basic HTTP request.
It sounds like this config will add a header exposing that IP to downstream services. Is that correct?

@citizenken Yes exactly.

@jspdown listener done. unfortunately the CI tests are only OK after merge with master (because of a timezone change)

unfortunately the CI tests are only OK after merge with master (because of a timezone change)

@mschneider82 you just have to rebase your PR.

@mschneider82 to apply the suggestion you can:

use the "Commit suggestion" button
or in the "Files changed" view, use the "Add suggestion to batch"

@mschneider82 to apply the suggestions you can:

use the "Commit suggestion" button
or in the "Files changed" view, use the "Add suggestion to batch"

sorry did not knew this feature... i have added commit hashes to the suggestions

is it normal that the ci tests randomly fails? (i had to force push the same commit 3 times today..)

i get errors when i run make generate-crd

@mschneider82 Sadly yes some integration tests are still a bit flaky. I'm investigating on the failing test to see if I can spot a reason for this flakiness.
About the make generate-crd, In order to work, traefik must be clone in your go path under $GOPATH/src/github.com/traefik/traefik and your GOPATH must be set.
If the problem persists, could you paste the output of this command here?

@mschneider82  Apparently the make generate-crd hasn't been run on this commit. We will make sure to fix to keep a clean diff. Thanks for spotting this :+1:

i have removed this commit from here so we dont get merge conflics.

@mschneider82 Could you rebase on master? Integration tests fail because of an issue with the haproxy image. It has been fixed in https://github.com/traefik/traefik/commit/b3d298ea557e1d285e3f569895dfbbce3bde438e

can i retrigger the CI via bot?

will this feature merged in v2.4 ?

@mschneider82 Yes we are planning to release it in the v2.4.

Is there a release cycle for when the v2.4 will be out? Eagerly awaiting this fix in this PR!

good choice to change version back to int

@jspdown do you know when the 2.4 version will be released, we are eagerly awaiting this fix

Hello @loreleimccollum-work It's going to be released in the coming weeks.

We just tried to apply the 2.4 rc1 to our cluster and are using an pod that can print out the client IP, and we are not seeing the client IP preserved with this 2.4 rc1. I was wondering if we are missing something in the setup. I looked at the docs on this PR, but didn't see much in way of making sure this is setup. We have this annotation set on the traefik service service.beta.kubernetes.io/aws-load-balancer-proxy-protocol: * and args on the traefik pod have       --entryPoints.web.proxyProtocol.insecure       --entryPoints.websecure.proxyProtocol.insecure any suggestions?

We just tried to apply the 2.4 rc1 to our cluster and are using an pod that can print out the client IP, and we are not seeing the client IP preserved with this 2.4 rc1. I was wondering if we are missing something in the setup. I looked at the docs on this PR, but didn't see much in way of making sure this is setup. We have this annotation set on the traefik service service.beta.kubernetes.io/aws-load-balancer-proxy-protocol: * and args on the traefik pod have       --entryPoints.web.proxyProtocol.insecure       --entryPoints.websecure.proxyProtocol.insecure any suggestions?


Problem Downloading v1.3.0

I had a problem downloading slsa-verifier 1.3.0. Is this user error? Am I missing something? Thank you!
system info: Apple M1 v12.5.1
I ran this:
$ go install<EMAIL_ADDRESS>
I got this:
go: downloading github.com/slsa-framework/slsa-verifier v1.3.0
go<EMAIL_ADDRESS>module<EMAIL_ADDRESS>found, but does not contain package github.com/slsa-framework/slsa-verifier

But I didn't have this problem with  v1.2.0:
go install<EMAIL_ADDRESS>

Looks like we forgot to update the README:
$ go install<EMAIL_ADDRESS>


Update Wasmer Python extension link

We renamed the repo from python-ext-wasm to wasmer-python :)

Thanks!


bug: An error occured at startup, even with a blank installation (no plugins)

Did you check docs and existing issues?

[X] I have read all the LazyVim docs
[X] I have searched the existing issues of LazyVim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
0.9.4
Operating system/version
Ubuntu (WSL)
Describe the bug
An error occurs when I launch neovim
Failed to run `config` for indent-blankline.nvim

.../share/nvim/lazy/indent-blankline.nvim/lua/ibl/utils.lua:428: attempt to call field 'iter' (a nil value)

# stacktrace:
  - /indent-blankline.nvim/lua/ibl/utils.lua:428 _in_ **tbl_join**
  - /indent-blankline.nvim/lua/ibl/config.lua:253 _in_ **merge_configs**
  - /indent-blankline.nvim/lua/ibl/config.lua:276 _in_ **set_config**
  - /indent-blankline.nvim/lua/ibl/init.lua:57 _in_ **setup**

Edit: I removed all my plugins to be sure:
Failed to run `config` for indent-blankline.nvim

.../share/nvim/lazy/indent-blankline.nvim/lua/ibl/utils.lua:428: attempt to call field 'iter' (a nil value)

# stacktrace:
  - /indent-blankline.nvim/lua/ibl/utils.lua:428 _in_ **tbl_join**
  - /indent-blankline.nvim/lua/ibl/config.lua:253 _in_ **merge_configs**
  - /indent-blankline.nvim/lua/ibl/config.lua:276 _in_ **set_config**
  - /indent-blankline.nvim/lua/ibl/init.lua:57 _in_ **setup**
  - vim/_editor.lua:0
  - /neo-tree.nvim/lua/neo-tree/utils/init.lua:732 _in_ **open_file**
  - /neo-tree.nvim/lua/neo-tree/sources/common/commands.lua:729 _in_ **open**
  - /neo-tree.nvim/lua/neo-tree/sources/common/commands.lua:751 _in_ **open_with_cmd**
  - /neo-tree.nvim/lua/neo-tree/sources/common/commands.lua:760 _in_ **open**
  - /neo-tree.nvim/lua/neo-tree/sources/filesystem/commands.lua:184

Steps To Reproduce

Install the starter
Launch neovim, make the lazyvim update
relaunch and open a file

I tried several times, and I also retry with a blank installation. The error occurs whatever I do.
It does not happen using the repro.lua file.
Expected Behavior
The error should not appear :)
Repro
-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  "folke/LazyVim",
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here

That's not a LAzyVim issue is it? Report it in the correct plugin repo

There is no plugin in my configuration, see the "edit" section please

(sorry for the title, I removed it by error)

What do you mean? indent-blankline is included in LAzyVim. That plugin is giving the error.
As I said submit an issue in that repo.
You can't expect me to be responsible for all issues for any plugin included with LazyVim....

The plugins directory is empty (there is the example.lua file only)
I didn't installed extras.
It's a blank installation using the LazyVim/starter repository
I don't have any other explanation... LazyVim worked for weeks, and yesterday the error appears. So I removed everything, reinstalled LazyVim with starter, and the problem is still here.

Like I said, indent-blankline IS PART OF the core LazyVim plugins.
They just made an update that is not backward compativle with 0.9.5.
I'm pretty sure that was by accident. They'll fix it.

See here https://github.com/lukas-reineke/indent-blankline.nvim/commit/98f85638a669fd7f42f59a7283676391ab9b9ca3

Ha ! Sorry, I didn't understand what you meant. All apologies.

As mentioned in the above comment, the problem arises from the incompatibility of the Neovim version. So, waiting for a while should fix the issue. However, if you want to fix it temporarily, you can add the following line to your custom plugins to downgrade the version of the problem plugin.
 { "lukas-reineke/indent-blankline.nvim", event="LazyFile", opts = { scope = { enabled = false } }, version = "=3.5.4" }

@ENEmyr can you pleasea also mention the temporary fix for the tree-sitter issue ??

The field iter is available in Neovim 0.10. So, if you update Neovim to stable 0.10 I believe it should be ok. I use stable 0.10 and don't see this error.

I am using the 0.11 version but it somehow stopped breaking now after fixing the indent-blankspace thing. Thanks for the help.

I've already fixed this in LAzyVim, so you can safely use the latest IBL version


Support the wildcard principal ("*") in STS role config

Explain the changes

Currently, if a user sets the principal which can assume a role via STS as "*", it always fails since it compares "*" to the email of the requester. This PR checks whether the policy principle is "*" and allows it

Testing Instructions:

Create two NooBaa accounts - 'assumed' and 'assumer'
Assign a role config to assumed that allows anyone ("principal": ["*"]) to assume it
Try to assume it with the credentials of assumer
Test the received credentials

[ ] Doc added/updated
[ ] Tests added

Hey @Neon-White

Regarding your question here - https://github.com/noobaa/noobaa-core/pull/8257#discussion_r1705504534 - The check of "*" removal seems to be on purpose IMO, but I don't remember, it's been more than 3 years...
Looks like the whole assume_bucket_policy code is very outdated, @nadavMiz completely transformed the S3 bucket policy with updated NotPrinciple, Conditions etc, when do we plan to do that for STS?
Please add appropriate unit tests.
We need to also remove STS tests from the black list of ceph tests, did you try to run them while working on enabling STS? Do you know what is the status there?

Adding @liranmauda @nimrod-becker for assigning https://github.com/noobaa/noobaa-core/pull/8257#issuecomment-2275695375
As it's not a part of this PR, we do want to -

Apply the new bucket policy structure to STS.
Enable STS Ceph tests.


Feature: SQS Broker

I couldn't find any plugin/extension for an AWS SQS Broker for TaskIQ, so I was thinking of creating one. Any feedback or suggestions?

Hello and thanks for raising this issue. I was thinking about it for a while, but didn't implemented it. You can take a look at different brokers and how they implemented and there's a small template for brokers.
For initial project creation, you can use https://github.com/taskiq-python/project-template.
You can ask me about anything related to this task:

My telegram
My discord: s3rius#8298

Thank you! Will do

Hello!
Has the development of this broker advanced? If yes, I would like to help. If not, I would like to know because I will start one from scratch.
Thanks in advance!

hello everyone, i'm trying to do something similar i just want to know if it has been done. @fubuloubu

hello everyone, i'm trying to do something similar i just want to know if it has been done. @fubuloubu

No, never ended up making one, but if you do and open source it, please link it here

Thanks for a quick response, it will be nice to support that in the main project just as we have redis, rabbitmq.

Okay, will do it this weekend.

i will be waiting for the update

thanks

We ended up making one and open sourcing it (h/t @mikeshultz)
Not production material, just fit our use case and wanted to open source it
https://github.com/ApeWorX/taskiq-sqs
Happy to combine with your work @s3rius

btw, we have started testing w/ https://github.com/ApeWorX/taskiq-sqs and it is working well. I hope some folks out there will give it a shot!


[Question]  Does it support a project to register HTTP and Dubbo interfaces to the gateway at the same time?

Question
Does it support a project to register HTTP and Dubbo interfaces to the gateway at the same time?

no  support both ,    but you could write a new starter  integration  springmvc and dubbo starter


Vimeo postmessage issue after destroying player

I have a vimeo player which I'm needing to destroy - but vimeo throws an error after the destroy.
VM289 plyr.froogaloop.js:1 Uncaught TypeError: Cannot read property 'postMessage' of null
Example:
https://jsfiddle.net/6okm62pf/1/
It consistently throws AFTER the destoy() since the vimeo video is still on the page.
If you remove the .plyr node itself right afterwards it seems ok. e.g.
player_reference.destroy();
var p = document.querySelector(".plyr");
p.parentNode.removeChild(p);

but then the function isn't returning the node back to its original state (my case that's ok, but it's not what it says on the tin). :)

Will take a look at this. I've just upgraded the Vimeo API to their new player.js which may help but I need to look at the destroy() method anyhow. Thanks for reporting 👍

On 1.8.12 I still have to destroy the actual plyr instance in order to make the video dissapear. If I then create a new instance, I get an uncaught typeerror - cannot set property 'embed' of undefined.
Example:
https://jsfiddle.net/6okm62pf/4/

Just run it and click destroy - the video temporarily goes away then comes back (Vimeo video seems to be calling back and recreating itself).
Click Destroy & RemoveChild - everything looks fine, no errors
Now click Create - you get the set property error, and plyr ins't properly set up.

I realise that if i'm changing source then I should be using player.source and giving it its new sources - but I can't make that work once/if the existing player is destroyed - https://jsfiddle.net/6okm62pf/7/ (clicking Create without first destroying the player still works)

I'm looking at this now along with trying to clean up the object references a little more. Will be re-writing .destroy() as I think it's been forgotten a long the way and should be used by .source() anyway as a lot of the code is replicated.

Any solutions here?  I am having the exact same problem.  I am unloading the element on an Ajax page load then re-load in a video element only to get that same error.
cannot set property 'embed' of undefined.

Really sorry - I am working on it. Hoping I can get a fix out for this, plus a load of other issues this weekend. Have you tried the .source() method for updating instead of destroying and starting over?

This should be fixed in v1.9.0 - could you give it a go? Bear in mind there were also several breaking changes so check the changelog


Suggestion: Suppress benign WMC1501 warning.

Since the WMC1501 warning is benign, you may want to add the following pragma to App.xaml.cs in NotificationFlyoutSample.Host.csproj:
using System;
using System.Collections.Generic;
using System.Configuration;
using System.Data;
using System.Linq;
using System.Threading.Tasks;
using System.Windows;

namespace NotificationFlyoutSample.Host
{
// No need to report benign warning.
#pragma warning disable WMC1501
    /// <summary>
    /// Interaction logic for App.xaml
    /// </summary>
    public partial class App : Application
    {
    }
}

I'm not sure about the other two warnings I'm seeing, WMC1006 and MSB3277.  These might not be so innocent.

Sorry, made a mistake in the module above.  And the pragma doesn't work, hmmm (should have tried it first).


release 2.11.0

Relates https://github.com/kedacore/keda/issues/4710

https://github.com/kedacore/charts/discussions/478#discussioncomment-6254672

https://github.com/kedacore/charts/discussions/478#discussioncomment-6254672

Please don't forget the notes


TerraformDirectoryPlugin - add auto-detect

Some projects put their terraform code in ./terraform, some projects do not
I want to use a Customizations library across multiple projects - some which do and some which do not use the ./terraform directory convention.
Add an 'auto-detect' feature to TerraformDirectoryPlugin.  If the given folder exists, use it.  If it does not exist, skip it and assume all terraform files are in the root folder.

<EMAIL_ADDRESS>_

Jenkinsfile.init(this)
TerraformDirectoryPlugin.autoDetectDirectory('./terraform').init()

// If ./terraform directory exists, use it.  If it does not, assume all terraform files are in the root directory
def validate = new TerraformValidateStage()
def deployQa = new TerraformEnvironmentStage('qa')
def deployUat = new TerraformEnvironmentStage('uat')
def deployProd = new TerraformEnvironmentStage('prod')

validate.then(deployQa)
        .then(deployUat)
        .then(deployProd)
        .build()

https://www.terraform.io/docs/cli/commands/plan.html#passing-a-different-configuration-directory


Left hooks and right hooks 🥊

Currently, the hook API for plugins is very minimal. Hook functions are pushed to the end of the associated array. We'll probably keep this.hook the same in that regard, but we should figure out a way to prepend a hook function (and maybe even a priority system is warranted?).
// Run after all existing "config" hooks (except right hooks).
this.hook('config', () => {});

// Run before all existing "config" hooks.
this.hookLeft('config', () => {});

// Run after all existing "config" hooks.
this.hookRight('config', () => {});

Using hookLeft guarantees your function will run before any hook and hookRight functions.
Using hookRight guarantees your function will run after any hook and hookLeft functions.

We need to figure out how to accomplish this with hookModules and hookPackages.

Added in 7a6d87e37bc84adf9e5edd39a02d0c951de079de (v0.1.0)
For the module hook, you can do:
this.hookLeft('module.js', () => {});

For the package hook, you can do:
this.hookLeft('package', () => {});


ListenPastOnce?

Would it be useful to have a ListenPastOnce function as well? I'm currently using Signals for creating some data in a remote backend and listening for the return message, but that message might have been received before the create() function returns (slim chance, but chance nonetheless). However, I definitely want the trigger to occur only once.
I could code this and submit a PR, but maybe you've got different ideas so I thought I'd check before coding.

Makes perfect sense, go for it!

Just a heads up: I'll probably get around to doing this today or later this week.


pkg/build/openbsd: require kernel config files as configuration data

Previously the config was generated directly, but testing multiple
configurations makes this cumbersome going forward. This makes
kernel_config a mandatory parameter.
@mptre, this changes the UX, let me know if you feel strongly enough that we need to provide a fallback.

Bonus: syzkaller UI shows the .config.

Bonus: syzkaller UI shows the .config.

Oh, that's nice! BTW: why the 2 in pseudo-device kcov 2?

Bonus: syzkaller UI shows the .config.
Oh, that's nice! BTW: why the 2 in pseudo-device kcov 2?

Because I failed to read the man page. I didn't realize it's a boolean flag rather than the number of devices.

On Thu, Dec 06, 2018 at 08:53:20PM +0000, Greg Steuck wrote:

Bonus: syzkaller UI shows the .config.
Oh, that's nice! BTW: why the 2 in pseudo-device kcov 2?

Because I failed to read the man page. I didn't realize it's a boolean flag rather than the number of devices.

Gotcha, /dev/kcov can be opened more than once per thread.


xDnsServerSecondaryZone: Description of masterservers invalid.

Under the readme.md in the xDnsServerSecondaryZone section, it states MasterServers: IP address or DNS name of the secondary DNS servers.
However, when I tried a FQDN it failed saying Cannot convert value "my-server.domain.com" to type "System.Net.IPAddress". Error: "An invalid IP address was specified."
It would seem that dns names are not allowed despite the documentation saying otherwise?

I would also like to add that 'masterservers' (plural) make it seem like it should take an array of servers.  But, it seems like this is just a string containing a single ip.

The parameter MasterServers is an array of strings. Could you test with the latest released version, and provide the verbose output when you get this error?


Scanner tests are excluded from build ?

Problem statement
It seems the scanner tests are excluded ... well a lot of tests tbh.
Im trying to fix a bug but the tests I wish to run are not included in the build ?
go test ./...
its all about the
// +build !go1.11 which from the go lang doc is not an operating system and will make the test be skipped like ignore. maybe NOT(go1.11) was intended or just go1.12 ?
"
To keep a file from being considered for the build:
// +build ignore

(any other unsatisfied word will work as well, but “ignore” is conventional.)
"
I would suggest removing the // +build tag  altogether.

For go 1.11+ we use moduels in the codescan package.
That build tag says for anything below go1.11. this is actually intended because for the newer go versions we use a different package that is module aware


0.2.0+mc1.21.0 crash

Hi, I just updated your mod and now it crashes while loading the map. (Solo or multi)
I was fine before the sodium update that broke your mod rendering.
java.lang.NullPointerException: Cannot invoke "net.minecraft.class_746.method_31548()" because "this.field_3712.field_1724" is null at net.minecraft.class_636.method_2911(class_636.java:302) at net.minecraft.class_636.method_2927(class_636.java:285) at net.minecraft.class_310.method_1574(class_310.java:1908) at net.minecraft.class_310.method_1523(class_310.java:1246) at net.minecraft.class_310.method_1514(class_310.java:882) at net.minecraft.client.main.Main.main(Main.java:256) at net.fabricmc.loader.impl.game.minecraft.MinecraftGameProvider.launch(MinecraftGameProvider.java:480) at net.fabricmc.loader.impl.launch.knot.Knot.launch(Knot.java:74) at net.fabricmc.loader.impl.launch.knot.KnotClient.main(KnotClient.java:23)
Do I need something else ?
I'm using iris.

are you using sodium 0.6?
sodium 0.5 won't work anymore

Yes I'm using 0.6.0-beta.1 for Fabric

i quickly tested it my self, it seems to be kinda related to iris, but the crash does still happen even without iris.
will investigate tomorrow

small note: I have taken down the version since it seems to be completely broken...
Thanks for reporting!

so i just reuploaded 0.2
this should now work
please let me know if it does not

Perfectly fine to me ✨
Thank you !

nice to hear!
thanks for reporting!


[TextField] wrong color on focused border

Problem description
It's a weird issue. The border of a TextField has the color black (see Screenshot):

Checking the CSS in the developer console:

So obviously there is no color set on the border.
This happens in Chrome, but in Firefox it works. But it get even more weird: When I build my app with the flag NODE_ENV=production then it DOES work properly.
Also changing these two lines of code here: https://github.com/callemall/material-ui/blob/master/src/TextField/TextFieldUnderline.js#L94-L95
… to borderBottom: 'solid 2px ' + focusColor, work as well, even with a normal build.
I wanted to create a Webpackbin example, but there it works fine.
I'm using Meteor, don't know if that matters. But maybe someone find a solution.
Versions

Material-UI: 0.16.4
React: 15.4.1
Browser: Chrome 54

See this minimal setup showing the problem:
text.zip

This is happening to me to. No matter which theme you use, textfield underline is always black.
Also, this is happening in chrome, and it's working fine in firefox.
Versions:

React: 15.4.1
Chrome: 55.0.2883.75
Material-UI: 0.16.0 to 0.16.4 (those are the versions I tested)

@lewisdiamond It seems your zip isn't complete. public and src folders are empty.

I think that it's a duplicate of #5697. Could you confirmed that it's solved on the master branch?

Oh, I didn't see that bug you linked although I actually tried to find that issue before opening a new one …
Anyway, it seems to work with current master (if I did everything right).

@vuhrmeister: great. I'll close this issue since it appears to be resolved, thank you for openning it!

That's quite an important issue. Let's release something before the end of the week.

Any insight into what caused this issue? I didn't even update any libraries, just did a clean install.

@rsolomon: it's probably the ^ (caret) on your Material-UI dependency in package.json, npm treats that as a update to most recent major version, so if you have a package with ^1.2.3 and it releases a 1.2.4, npm will automatically install it.

I'm still seeing this on 0.16.6 :(

Not sure what I need to change.

It appears border-color is set to initial, causing the issue.

@oliviertassinari This is still broken if you set {userAgent: 'all'} in a call to getMuiTheme, e.g., getMuiTheme({...}, {userAgent: 'all'});.
New issue created here: https://github.com/callemall/material-ui/issues/5902

@elTallarin I have the same issue as you, and only in Chrome, have you found solution?

posting for same error, using webpack HMR, userAgent all and chrome