Verica Karanakova's first commit.

Approved @verica-kar! Did the pipeline run in Prefect fail? Wondering why the log screenshot was red.

The first two runs failed completely and the most recent one had some 'fails' but mostly 'succeeds'.  Could that be the reason for it being red?


Expose metrics from components installed by kubeadm

components deployed by kubeadm can't be accessed by prometheus

/test create

Fixed by https://github.com/giantswarm/roadmap/issues/1204

/test create


SMTP setting not working

I tries our company SMTP detail mail not worked . I tried Gmail SMTP still it is not working
I am getting the error Failed to create a leave request. where can i see complete logs ?
I am using below settings
"allow_create_new_accounts" : false,
"send_emails"              : true,
"application_sender_email" : "My Mail",
"email_transporter" : {
"host" : "smtp.gmail.com",
"port" : 465,
"auth" : {
"user" : "My Mail",
"pass" : "Pass"
}
},
"crypto_secret" : "!2~`HswpPPLa22+=±§sdq qwe,appp qwwokDF_",
"application_domain" : "http://app.timeoff.management",
"promotion_website_domain" : "http://timeoff.management"

I had to add an extra line to tell nodemailer to use ssl.  Also if your email account is using two factor you will have to create an app password to use, or if its not using two factor you need to enable "less secure apps" (https://myaccount.google.com/lesssecureapps)
"allow_create_new_accounts" : false,
"send_emails" : true,
"application_sender_email" : "My Mail",
"email_transporter" : {
"host" : "smtp.gmail.com",
"port" : 465,
"secure" : true,
"auth" : {
"user" : "My Mail",
"pass" : "Pass"
}
},
"crypto_secret" : "!2~`HswpPPLa22+=±§sdq qwe,appp qwwokDF_",
"application_domain" : "http://app.timeoff.management",
"promotion_website_domain" : "http://timeoff.management"

@HyperSquiZ, thank you for sharing about email settings.
@cprashant1 hope the above suggestion works for your setup.

Thanks , can you tell me where can i see logs for any failure ? also i want to work with our company's Outlook 365
{
"allow_create_new_accounts" : true,
"send_emails"              : true,
"application_sender_email"<EMAIL_ADDRESS>"email_transporter" : {
"host" : "outlook.office365.com",
"port" : 587,
"secure" : true,
"ignoreTLS": false,
"auth" : {
"user"<EMAIL_ADDRESS>"pass" : "My_Pass"
}
},
"crypto_secret" : "!2~`HswpPPLa22+=±§sdq qwe,appp qwwokDF_",
"application_domain" : "http://app.timeoff.management",
"promotion_website_domain" : "http://timeoff.management"
}

With default settings they just go to STDOUT, so if you "npm start" from your console app would just keep spiting log messages into that terminal session. If you want to herd those messages into files you have to redirect the STDOUT and STDERR into those files. E.g. node bin/wwww_cluster >> /log_dir_path/log/all.log  2>&1

Thanks it worked with Gmail. but i am still facing issue with our company's office 365 account
I turned on TLS flag to true since 587 is TLS port but still it doent work , any idea ?
{
"allow_create_new_accounts" : true,
"send_emails" : true,
"application_sender_email"<EMAIL_ADDRESS>"email_transporter" : {
"host" : "outlook.office365.com",
"port" : 587,
"secure" : true,
"ignoreTLS": false,
"auth" : {
"user"<EMAIL_ADDRESS>"pass" : "My_Pass"
}
},
"crypto_secret" : "!2~`HswpPPLa22+=±§sdq qwe,appp qwwokDF_",
"application_domain" : "http://app.timeoff.management",
"promotion_website_domain" : "http://timeoff.management"
}

I believe the secure option is only true for port 465.  If using port 587 I think you need "secure" false.

Try setting secure option to false.
"secure – if true the connection will use TLS when connecting to server. If false (the default) then TLS is used if server supports the STARTTLS extension. In most cases set this value to true if you are connecting to port 465. For port 587 or 25 keep it false" - https://nodemailer.com/smtp/

even after secure false and using TLS port still not working
{
"allow_create_new_accounts" : false,
"send_emails"              : true,
"application_sender_email" : "testmail",
"email_transporter" : {
"host" : "smtp.office365.com",
"port" : 587,
"secure" : false,
"auth" : {
"user" : "testmail",
"pass" : "pass"
}
},
"crypto_secret" : "!2~`HswpPPLa22+=±§sdq qwe,appp qwwokDF_",
"application_domain" : "http://skuawinserv1:3000",
"promotion_website_domain" : "http://skuawinserv1:3000"
}

try the below.  I've seen some posts about having to specify SSLv3 for Office365 SMTP.
{
"allow_create_new_accounts" : false,
"send_emails" : true,
"application_sender_email" : "testmail",
"secure" : false,
"email_transporter" : {
"host" : "smtp.office365.com",
"port" : 587,
"tls" : { "ciphers" : "SSLv3" },
"auth" : {
"user" : "testmail",
"pass" : "pass"
}
},
"crypto_secret" : "!2~`HswpPPLa22+=±§sdq qwe,appp qwwokDF_",
"application_domain" : "http://skuawinserv1:3000",
"promotion_website_domain" : "http://skuawinserv1:3000"
}

@cprashant1, there was similar issue few months ago, please have a look at the thread: https://github.com/timeoff-management/application/issues/142#issuecomment-293970765

Itried below but no luck , not sure what extra paramater office365 expecting . I also tried with "ignoreTLS": false , still it doesnt work.
{
"allow_create_new_accounts" : false,
"send_emails"              : true,
"application_sender_email" : "mail",
"email_transporter" : {
"host" : "smtp.office365.com",
"port" : 587,
"secure" : false,
"tls" : { "ciphers" : "SSLv3" },
"auth" : {
"user" : "myemail",
"pass" : "pass"
}
},
"crypto_secret" : "!2~`HswpPPLa22+=±§sdq qwe,appp qwwokDF_",
"application_domain" : "http://web:3000",
"promotion_website_domain" : "http://web:3000"
}

Not sure it is possible to find the solution for this issue without access to the environment where it manifests itself.

Hi, use
"auth" : null
and it works
{
"allow_create_new_accounts" : false,
"send_emails"              : true,
"application_sender_email" : "TimeOFF.Request TimeOFF@xxx",
"email_transporter" : {
"type" : "smtp",
"host" : "xxxx",
"port" : 25,
"secure" : false,
"ignoreTLS" : false,
"tls": {
"rejectUnauthorized": false
},
"auth" : null


Closes #1331 and #1586 Update description for new contributors and PR

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

[x] Place Closes #<insert_issue_number> into the beginning of your Pull Request Title (Use Edit button in top-right if you need to update)
[x] Code is formatted according to the tidyverse style guide. Run styler::style_file() to style R and Rmd files
[x] Updated relevant unit tests or have written new unit tests - See Unit Test Guide
[x] If you removed/replaced any function and/or function parameters, did you fully follow the deprecation guidance?
[x] Update to all relevant roxygen headers and examples
[x] Run devtools::document() so all .Rd files in the man folder and the NAMESPACE file in the project root are updated appropriately
[x] Address any updates needed for vignettes and/or templates
[x] Update NEWS.md if the changes pertain to a user-facing function (i.e. it has an @export tag) or documentation aimed at users (rather than developers)
[x] Build admiral site pkgdown::build_site() and check that all affected examples are displayed correctly and that all new functions occur on the "Reference" page.
[x] Address or fix all lintr warnings and errors - lintr::lint_package()
[x] Run R CMD check locally and address all errors and warnings - devtools::check()
[x] Link the issue in the Development Section on the right hand side.
[x] Address all merge conflicts and resolve appropriately
[x] Pat yourself on the back for a job well done! Much love to your accomplishment!

See https://github.com/pharmaverse/admiraldev/pull/173 for additional comments as both this and that pull request make very similar updates

@bms63 when you get the chance, can you take a final look at this again?


Input for owner

Few things:

We need to rebuild using make dist-rebuild right? https://github.com/ForAllSecure/mcode-action#how-to-contribute <-- I would assume after we merge in https://github.com/ForAllSecure/mcode-action/pull/45
We should test that this works (I see the comment about adding the integration tests)
We should test that the new release works (i.e. ForAllSecure/mcode-action@<SHA>)

A few things upon review:

We need to rebuild using make dist-rebuild right? I don't see the related artifacts that get updated after rebuilding, see https://github.com/ForAllSecure/mcode-action#how-to-contribute <-- I would assume after we merge in Add coverage junit input runid output #45
We should test that this works (I see the comment about adding the integration tests)
We should test that the new release works (i.e. ForAllSecure/mcode-action@<SHA>)

Good point. 1. is done. 2. added a test. 3. need to do

We should test that this works (I see the comment about adding the integration tests)

Works. Verified manually. --owner vlussenburg instead of forallsecure

We should test that the new release works (i.e. ForAllSecure/mcode-action@)

@Andrew5194 I would argue that the integration tests do exactly that and there's no need to do it from an external repo. WDYT?


Fix Travis build error

Fixes the "can't modify frozen String" error on recent builds. Apparently it's a problem with RubyGems and it's fixed in the latest version, so just update that in the build before running.

@jekyllbot: merge +dev


GitHub Actions Installing Dependencies Failed

It appears that npm could not resolve certain dependencies for the latest few actions runs (here and here).
We need to resolve these dependencies to allow GitHub Actions to run as expected.

Recreated locally:

If I drop ethereum-waffle version from ^4.0.0-alpha.0 to ^3.0.0 in the package.json, build completes. However, not knowing much about node, this didn't look great:


Update extension of kube config files from '.js' to '.json'.

cc @vmarmol

LGTM

Self merging since it has been reviewed already!


[DOP-10395] - add detect_hwm_store decorator

Change Summary

add decorator: detect_hwm_store in etl_entities.hwm_store (source code was imported from onetl.hwm.store)
add tests
update documentation

Related issue number

Checklist

[x] Commit message and PR title is comprehensive
[x] Keep the change as small as possible
[x] Unit and integration tests for the changes exist
[ ] Tests pass on CI and coverage does not decrease
[x] Documentation reflects the changes where applicable
[x] docs/changelog/next_release/<pull request or issue id>.<change type>.rst file added describing change
(see CONTRIBUTING.rst for details.)
[x] My PR is ready to review.

Поменяй в codecov.yml процент покрытия на 94


Error "Cannot read properties of undefined (reading 'command')" when starting project

Describe the bug
Receiving an error when starting a project
node:internal/event_target:920
  process.nextTick(() => { throw err; });
                           ^
TypeError [Error]: Cannot read properties of undefined (reading 'command')

at
at Object.workerScript (path/node_modules/vite-plugin-checker/lib/worker.js:63:60)

Reproduction
package.json
{
  "name": "react-project-template",
  "version": "0.0.0",
  "scripts": {
    "dev": "vite",
    "build": "tsc && eslint --ext .tsx,.ts . && vite build",
    "clean": "rm -rf dist/",
    "serve": "vite preview",
    "start": "vite",
    "predeploy": "npm run build",
    "deploy": "netlify deploy --prod --dir=dist"
  },
  "prettier": {
    "trailingComma": "es5",
    "tabWidth": 2,
    "semi": false,
    "singleQuote": true,
    "useTabs": false
  },
  "dependencies": {
    "classnames": "^2.2.6",
    "react": "^17.0.0",
    "react-dom": "^17.0.0",
    "react-hook-form": "^7.32.2",
    "react-i18next": "^11.17.2",
    "react-rangeslider": "^2.2.0",
    "react-router": "^5.2.0",
    "react-router-dom": "^5.2.0",
    "typescript": "^4.7.4",
    "uuid": "^8.3.2"
  },
  "devDependencies": {
    "@types/i18next": "^13.0.0",
<EMAIL_ADDRESS>"^1.11.0",
    "@types/react": "^17.0.0",
    "@types/react-dom": "^17.0.0",
    "@types/react-rangeslider": "^2.2.4",
    "@types/react-router": "^5.1.18",
    "@types/react-router-dom": "^5.3.3",
    "@types/uuid": "^8.3.4",
    "@typescript-eslint/parser": "^5.33.1",
    "@vitejs/plugin-react-refresh": "^1.3.6",
    "eslint": "^8.18.0",
    "eslint-config-prettier": "^8.3.0",
    "eslint-config-react-app": "^7.0.1",
    "eslint-plugin-jsx-a11y": "^6.4.1",
    "eslint-plugin-prettier": "^4.2.1",
    "eslint-plugin-react": "^7.25.1",
    "eslint-plugin-react-hooks": "^4.2.0",
    "prettier": "^2.3.2",
    "sass": "^1.39.0",
    "vite": "^3.0.8",
    "vite-plugin-checker": "^0.4.9",
    "vite-plugin-linter": "^1.2.0"
  }
}

vite.config.ts
import { defineConfig } from 'vite'
import reactRefresh from '@vitejs/plugin-react-refresh'
import checker from 'vite-plugin-checker'
import { EsLinter, linterPlugin } from 'vite-plugin-linter'

// https://vitejs.dev/config/
export default defineConfig((configEnv) => ({
  plugins: [
    reactRefresh(),
    checker({
      // TypeScript config
      typescript: { tsconfigPath: './tsconfig.json' },
    }),
    linterPlugin({
      build: {
        disable: true,
      },
      include: ['./src/**/*.ts', './src/**/*.tsx'],
      linters: [
        new EsLinter({
          configEnv: configEnv,
          serveOptions: { cache: false, formatter: 'visualstudio' },
        }),
      ],
    }),
  ],
}))

Run npm start
Expected behavior
No error. I have not tried (yet) moving away from vite-plugin-linter to use the eslint built into vite-plugin-checker yet. This maybe an incompatibility between the two projects?
System Info
System:
    OS: macOS 12.5.1
    CPU: (8) x64 Intel(R) Core(TM) i7-1068NG7 CPU @ 2.30GHz
    Memory: 1.00 GB / 32.00 GB
    Shell: 5.9 - /usr/local/bin/zsh
  Binaries:
    Node: 18.6.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 8.13.2 - /usr/local/bin/npm
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chrome: 104.0.5112.79
    Firefox: 103.0.2
    Firefox Developer Edition: 91.0
    Safari: 15.6.1
  npmPackages:
    vite-plugin-checker: ^0.4.9 => 0.4.9

### Additional context

The only change I can think of is the update to node/npm.

If I add a `console.log` just before the error:

console.log(import_worker_threads.workerData)
const isBuild = import_worker_threads.workerData.env.command === "build";

I get:

{
env: { mode: 'development', command: 'serve', ssrBuild: false },
checkerConfig: { typescript: { tsconfigPath: './tsconfig.json' } }
}
{
command: 'serve',
linterName: 'EsLinter',
pluginName: 'vite-plugin-linter-serve',
workingDirectory: 'path'
}

The second one lacks an `env` so there is an error

### Validations

- [X] Read the [docs](https://github.com/fi3ework/vite-plugin-checker#readme).
- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.

Change your config:
    checker({
      eslint: {
+        lintCommand: 'eslint --ext .js,.vue,.ts src'
-        files: ['./src'],
-        extensions: ['.ts', '.vue', '.js'],
      },
    })

The second one lacks an env so there is an error

I think there's something for the co-existing for the two plugin? Could you provide a minimal re-production or move away the vite-plugin-linter?

I had a separate ESLinter as well. Keeping just one fixed this for me.

These two plugins are very similar functionality. Using one plugin will be a good practice. Close for long-time inactive. Feel free to re-open if a minimal reproduction could be provided.


What's the issue if we use Snippet and NPM setup at the same time?

According to the documentation, we are not supposed to use Snippet and NPM setup at the same time.
https://docs.microsoft.com/en-us/azure/azure-monitor/app/javascript

Our service runs behind a reverse proxy which injects a "shell" for some common headers and styles. In the shell they inject, they are using the Snippet setup to initialize Application Insights and we use the NPM setup in our Angular app to initialize a new instance of Application Insights.
We noticed that we are not getting all client side logs in our Application Insights. Our various APIs losses anywhere from 20% to 99% of the logs.
I'd like to know if this could be due to using both the Snippet as well as NPM setup and if so what do you recommend to workaround this?

Technically, Its possible, but it depends a lot on how things are used and initialized
For example

if as part of the common headers they are initializing the global instance with their iKey for all automatic events then they will get those (as expected)
If you are using NPM to initialize application insights AND only use your initialized instance (via a local variable) then you will get all of your events including page view etc
The above work because you each have your own references.

An issue comes about however, if both of you are initializing, using  and setting the global instance (by default appInsights or (window.appInsights)), in this case you will have a race condition about who sets the global instance last and at that point all references are going only to that instance and iKey.
The main reason for the notice is size, as you will have the AI code getting downloaded from the CDN and included by your packages (assuming downloaded via CDN also).
To avoid this either (or both) of you should change the "global" name that you are using for the instance that you are using.
For the snippet that is what this config is for (with the current snippet)

// name: "appInsights", // Global SDK Instance name defaults to "appInsights" when not supplied

And for NPM users either ensure that the following is run within a closure (or your own module etc) or just change the name from appInsights to avoid a name clash.

const appInsights = new ApplicationInsights({ config: {

Thanks for the quick response. I checked and confirmed that we are not using the same global instance, appInsights or window.appInsights. The issue must be somewhere else then. I'll keep digging.

Closing this issue as I think we have answered this question, if you find something specific please open a new issue.


Reactor Kafka and Spring Cloud Function example

Is there any support/ example for using Reactor Kafka with Spring Cloud Function? I understood that Spring Cloud Function supports Project Reactor I couldn't manage to find any example. I think it would be helpful if some reactive examples appeared in the samples section of this repository.

@sobychacko can you please follow up on this?

@roger751 Here is a sample. However, I see that you have found this issue and your update. We will discuss how can we address it on that issue. Most likely, as part of 4.0 version of Spring Cloud Stream.

@sobychacko @olegz thanks. If you will I have a few questions about the situation:

What is the current recommended way to consume a Kafka topic, if I want high performance? Is there any alternative currently for using reactor and consume from kafka?
If you would create a project now, would you consume the topic with Spring Cloud Functions that use reactor kafka & core?
Spring Cloud Stream & its Kafka Binder can be reactive?
When does the 4.0.0 is planned to be released (approximately of course, if you can tell)?

Thank you very much

@roger751 Before I answer your individual questions, let me re-iterate the reactor situation with the current Kafka binder:  Without proper implementation of this issue in Kafka binder, we will not get full reactive support. The reason is that the Kafka binder is based on MessageChannel, not reactive types. With that said, if you want to use Project Reactor with Spring Cloud Function and Kafka, you need to write code on your own to do that until we implement it formally in the binder.
Here are my takes on the questions you asked.
1.spring-cloud-stream-binder-kafka is fully based on Spring for Apache Kafka. All the foundational elements in the binder come from Spring Kafka. Binder adds connectivity, opinionated primitives on top of the functional programming model through spring-cloud-function.
2. You still consume behind the scenes through spring-kafka in an async manner, but when you involve reactor like that, at the moment there is an impedance mismatch in the binder. We need to build a dedicated binder based on reactor-kafka for that which is the main focus of the other issue we pointed out.
3. As mentioned above, you need to hand-craft code to do that at the moment.
4. I think the answer here is highly dependent on your current use case. You can achieve really good performance with te message channel based Kafka binder, but you need to run benchmarks and adopt to your particular situation.
5. You can do that, but you need to do what I said in 3. I wouldn't go that route, but stick with the message channel based binder, but again based on your requirements you may want to write a different stack using reactor-kafka.
6. Without the other issue in the binder addressed, we cannot claim reactive capabilities for the binder. This is because from the moment records are delivered to the consumer by the binder, you are no longer in the reactive world, but rather handled through the message channel. In order to properly handle this we need to make sure that consuming layer is also reactive, thus a solution is needed based on reator-kafka - which is most likely a new binder variant for kafka (based on reactor-kafka).
7. We are planning 4.0.0 for 2022. This is going to be based on Spring Framework 6.0 and Spring Boot 3.0. We are hoping to get a first milestone out in early 2022 (but no final dates have been set for this yet).
Hope that answers some of your questions.
I will link this issue from the other issue for more visibility and feedback.

Thank you very much. This answers all I wanted, but it raises to me 2 more things:

Instead of Spring Cloud Function and SCSt, do you think it is possible to implement a reactor-kafka/core based application that uses Spring Boot, Spring Data and Spring Cloud features? e.g. spring cloud k8s. The application won't use Spring Integration. Do you see any traps?
In a case that I want to be able to upgrade to the futuristic binder when it'll be released, what would you say that will probably be easier to refactor - a reactor kafka based application as I've described in question 1, or a non-reactive Spring Cloud Stream application?

Sorry for my 5 fingers. Re.

The application won't use Spring Integration

It is still OK to start your application from the reactor-kafka KafkaReceiver (or just ReactiveKafkaConsumerTemplate) and feed the result Flux into a FluxMessageChannel from Spring Integration. The rest of your flow would still be the same: https://docs.spring.io/spring-integration/docs/current/reference/html/core.html#flux-message-channel. Or you just can start the flow from that Flux. See IntegrationFlows:
	/**
	 * Populate a {@link FluxMessageChannel} to the {@link IntegrationFlowBuilder} chain
	 * and subscribe it to the provided {@link Publisher}.
	 * @param publisher the {@link Publisher} to subscribe to.
	 * @return new {@link IntegrationFlowBuilder}.
	 */
	@SuppressWarnings("overloads")
	public static IntegrationFlowBuilder from(Publisher<? extends Message<?>> publisher) {

The rest of the story to explain I leave to @sobychacko .
Thanks

You can do that with reactor-kafka and boot. That is fine I think, but keep in mind that you are not using any SCFn/SCSt features here at all. Here are some examples from reactor-kafka. This is the part I said above basically that you need to implement the feature on your own until there is a formal one from the binder. See the comment from Artem above about FluxMessageChannel. That would also be a valid approach.
If you are running a reactor kafka based application, then that will be easier to refactor to a futuristic reactor-based binder.

Btw - you are more than welcome to contribute any PR's for this.

If we talk about a contribution, it is not so hard these days to implement a reactive channel adapter.
The Inbound part is just simply an extension of the MessageProducerSupport with the subscribeToPublisher(Publisher<? extends Message<?>> publisher) call from the start().
See MongoDbChangeStreamMessageProducer for example.
The Outbound part is just a ReactiveMessageHandler implementation.
Of course if we talk about a solution based on Spring Integration and its reactive bits with FluxMessageChannel and ReactiveStreamsConsumer...

@sobychacko thank you ! I'm not sure that I will have enough time for such a contribution. So I currently try to find a solution for my use case first.
@artembilan If I want a Spring Cloud application that consumes from reactor kafka, do you think it will be easiest and safest way to go is by implementing a reactive channel adapter (the MessageProducerSupport)? If that isn't an easier option that passing a flux from reactive kafka to some spring data component for instance, I'm failing to see the value of it. Will Spring Integration give any added value and features that you see as relevant in this use case?

@artembilan another question - the solution you've just mentioned is the same for the user implementation as for the contribution's implementation? In case of implementing your suggestion, will it be a valid contribution for the ideal situation of the Spring Cloud Stream Kafka Binder?

End-user solution could be whatever is convenient for you.
What is the fix for Spring Cloud Stream framework still not clear: it might fully not be based on Spring Integration.
So, you need to decide for yourself if you stick with integration flow solution with whatever reactive capabilities are present there, or try to come up with something function-based.
Either way I don't see how the current Kafka Binder can help you to keep Spring Cloud Stream model if you are seeking a reactive solution which is not present over there yet...
Please, let's continue discussion in the issue Soby has just mentioned.


Chrisgriffith master

NOT READY TO BE PULLED IN YET. WORK IN PROGRESS.
Continuation from #9

@chrisgriffith

I think I have also found a wide-open default CSP that works with windows as well as the other platforms.

I think this is good to review now:
@mwbrooks @chrisgriffith @hollyschinsky etc

@devgeeks why are the wp8 icon and splash commented out?

They shouldn't be. I think I actually have a tiny bit more to do.

One last thing (I hope). Since comments are stripped from the config.xml when a developer creates an app using the template, I am going to add all the info the comments convey as prose to the README

Sounds like a wise idea.
On Mon, Mar 28, 2016 at 4:56 PM, tommy-carlos williams <
<EMAIL_ADDRESS>wrote:

One last thing (I hope). Since comments are stripped from the config.xml
when a developer creates an app using the template, I am going to add all
the info the comments convey as prose to the README
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/phonegap/phonegap-template-hello-world/pull/10#issuecomment-202632454


Deceptive Site Warning

My site is getting a deceptive site warning on all search browsers. Not sure why and this is fairly recent.

Were you ever able to fix this? I also started getting this recently and it's a really scary warning! In my case, I switched from WordPress to Notion after a few years so I think maybe there is an SSL
The worst part is that my YouTube videos are getting unlisted and I'm getting violation warnings for including my link in my videos :(

Same, getting the same error: Attackers on [my website] may trick you into doing something dangerous like installing software or revealing your personal information (for example, passwords, phone numbers, or credit cards). Learn more

Not sure what's happening here or what the right fix is.

That sort of warning is usually triggered by a lookup of the domain against Google's 'Safe Browsing' registry: https://transparencyreport.google.com/safe-browsing/search?url=youtube.com
If you're sure you didn't do anything fishy, some other possibilities might include: (a) leftover bad-reputation a prior owner of the domain; (b) some content/sites cn the same IP address; (c) some content/JS inserted that you're unaware of (more common on things like compromised WordPress sites). The 'webmasters' link atop https://safebrowsing.google.com/ contains some tips for checking your site & requesting a review if it's been flagged in error.

I'm getting this warning now too and I strongly suspect it has to do with Fruition unintentionally triggering Google's phishing detection. No idea what to do to fix it though.

Well, I submitted an "incorrect report" report and now my site says "safe" again...


Fix CTE query expressions

Fix bug with Oracle when CTE aliases is not quoted.
Fix bug with Oracle and MSSQL: RECURSIVE expression is not needed for CTE.

Q
A

Is bugfix?
✔

New feature?
❌

Breaks BC?
❌

Fixed issues
-

Fix bug with Oracle when CTE aliases is not quoted.

Fix bug with Oracle and MSSQL: RECURSIVE expression is not needed for CTE.

Q 	A
Is bugfix? 	✔
New feature? 	❌
Breaks BC? 	❌
Fixed issues 	-

Please add links to db-* PR's

Done


Fix lifetime of Object::peel_to_* result

The peeled object lives as long as the repo.
Fixes #299.

Thanks!


respond to label updates

Fixes dotnet/docs#22653
See https://github.com/dotnet/docs/issues/22653#issuecomment-773525546
The dotnet/docs repo now uses the PRMerger bot to add labels to GitHub issues.
With that change, we're using the practice of /prod and /tech labels for areas and sub-areas, respectively.
This PR updates those descriptions. Some of the details were removed to make this more future proof.

ping @tdykstra for review

Thanks @tdykstra I've accepted all suggestions.
#sign-off

@Jim-Parker This is ready for final review and merge.


Create Base Query Compiler object for query compilers

What do these changes do?

Related issue number

[ ] passes git diff upstream/master -u -- "*.py" | flake8 --diff
[ ] passes black --check modin/

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Modin-Performance-PRB/346/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Modin-PRB/407/
Test PASSed.

Merged build finished. Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Modin-PRB/408/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Modin-PRB/409/
Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Modin-Performance-PRB/349/
Test PASSed.

Build finished. Test PASSed.

Build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Modin-PRB/410/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Modin-Performance-PRB/350/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Modin-PRB/411/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Modin-PRB/412/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Modin-Performance-PRB/351/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Modin-Performance-PRB/352/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Modin-PRB/413/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Modin-Performance-PRB/353/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Modin-Performance-PRB/354/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Modin-PRB/415/
Test PASSed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Modin-PRB/414/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Modin-Performance-PRB/355/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Modin-PRB/416/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Modin-Performance-PRB/356/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Modin-PRB/417/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Modin-PRB/475/
Test PASSed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Modin-PRB/486/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Modin-PRB/487/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Modin-PRB/489/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Modin-PRB/519/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Modin-PRB/520/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Modin-PRB/526/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Modin-PRB/527/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Modin-PRB/530/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Modin-PRB/532/
Test FAILed.


Need to remove unused synapse API

Description
Need to remove repository/deployment/server/synapse-configs/default/api/_OpenService_.xml from the API-M pack
Steps to Reproduce

Affected Component
APIM
Version
4.4.0
Environment Details (with versions)
No response
Relevant Log Output
No response
Related Issues
No response
Suggested Labels
No response

This is the BotDetection feature right??  I think we have documented this and also working fine.


Add more information on how to test the installation

I'm missing more detailed information in the README on how to verify that the installation was successful and the master and worker could be successfully started.
My worker.log looks good: there are no error messages and the last lines are:
2015-12-06 18:30:07 -    INFO:   __main__: Opening websocket connection to master server
2015-12-06 18:30:07 -    INFO:   __main__: Opened websocket connection to server

But testing with dictate.js and client.py does not produce any recognition results. E.g. I'm trying inside and outside the container:
python kaldi-gstreamer-server/kaldigstserver/client.py --uri ws://localhost:80/worker/ws/speech -r 8192 models/test/data/bill_gates-TED.mp3

python kaldigstserver/client.py --uri ws://localhost:8080/worker/ws/speech -r 8192 test/data/bill_gates-TED.mp3

but in both cases the server closes the socket and the client finishes without producing any output.

Hi. Could you please repeat your tests changing the uri? If possible, try these lines:
python kaldi-gstreamer-server/kaldigstserver/client.py --uri ws://localhost:80/client/ws/speech -r 8192 models/test/data/bill_gates-TED.mp3
python kaldigstserver/client.py --uri ws://localhost:8080/client/ws/speech -r 8192 test/data/bill_gates-TED.mp3
I think it's gonna work, since the worker was correctly started. I'll try to update the README.

Thanks, replacing "worker" by "client" did the trick. Please mention it in the README.

I updated the README. I rewrote the "Testing" section. I think it's gonna be clearer ... Thanks for your comments!

Thanks!


Support Tag2Link rules to get URLs for a tag

See Tag2Link and JOSM ticket #21988.
Also an appropriate SPARQL query could return a format constraint as a regular expression.
See SIRET number  on wikidata.
See also https://github.com/Zverik/every_door/issues/140#issuecomment-1125789680.

No. There will be no wikidata, sparql or any other obscure things in this editor. The editor is for collecting data, not for in-depth maintenance of mapped objects. The less fields the better.

Could we discuss this point ?

The editor is for collecting data,
👍

One could check data on the field, like Facebook or official identifiers like SIRET.
SPARQL is difficult to learn but that's not the point.

You could get a simple json from this project.
Tag2Link is a universal way to add links, open them (and check identifiers values).
It is used at least by JOSM and Osmose Q&A.

The less fields the better.
👍

One could use the future profile system to display only what he need.

Thing is, this editor is intended to be used in the field. You tap a button, fill as much info as possible in a short timeframe, and move to the next amenity. This proposal introduces a dependency on a web service (of which the app has just two: imagery and OSM, both optional when surveying). I do not want that, since it rises a question, why package all the presets and imagery lists when I could download them when needed.
Also this is a working plugin for JOSM, so people who are interested (and I believe there are less than 100 of them in the world) could use it to mass-add needed information.

This proposal introduces a dependency on a web service

No if rules are packaged with the app: a script run SPARQL queries and store data in a json file.
The script could be run manually or run automatically by continuous integration workflows.
(JOSM do SPARQL queries in the past, now it use webjar. A script run manually "build" the index.json file stored in this webjar).
But if Every Door will have custom presets (see #119) then tag2link is not mandatory 😃


Linux package for ssh access

For ubuntu, the necessary package is openssh-client (not -server).  I'm not sure if we want to get into the weeds with other distribution package names.
https://github.com/fhdsl/FH_Cluster_Guide/blob/7e20de40058ad951031afea2733c381ed33b432d/docs/terminal.html#L239

Looks like this is in the 01-101.Rmd file

Yup- not sure how I missed it with my search!
https://github.com/fhdsl/FH_Cluster_Guide/blob/7e20de40058ad951031afea2733c381ed33b432d/01-101.Rmd#L134

It was a bit tricky with the subsections being inside that file.

Yup- not sure how I missed it with my search!
https://github.com/fhdsl/FH_Cluster_Guide/blob/7e20de40058ad951031afea2733c381ed33b432d/01-101.Rmd#L134

It was a bit tricky with the subsections being inside that file!

@atombaby Thank you for catching this! I can also split up the Rmd sections if that makes it easier to review!


Added kollekt.fm

Added support to kollekt.fm
@Paszt @david-sabata  would you be able to take a look? How would be better to implement the checking for the existence of the player-controls element on the DOM?
I was thinking of changing the following in the starter to something like this:
	console.log('Web Scrobbler: Setting up stateChangeObserver');

		var playerSelectorObserver = new MutationObserver(function() {
			if (document.querySelector(Connector.playerSelector) !== null) {
				playerSelectorObserver.disconnect();
				var stateChangeObserver = new MutationObserver(Connector.onStateChanged);
				stateChangeObserver.observe(document.querySelector(Connector.playerSelector), {
					childList: true,
					subtree: true,
					attributes: true,
					characterData: true
				});
			}
		});

		playerSelectorObserver.observe(document.body, {
			childList: true,
			subtree: true,
			attributes: false,
			characterData: false,
		});

Perhaps this could be implemented as a flag that controllers can override
Connector.waitForPlayer = true or something.
Also I noticed that if the track/artist is null on the new connectors then notifications are null. Ill try to look into this later. I guess because null is a valid artist :/ will have to filter these out from the pipeline.
refs #622

@inverse I think (hope) that this wouldn't be a frequented case. But you're right that some mechanism of waiting for player to be ready might come handy. Otherwise people would invent their own ways, which are often wrong :)
I don't see any better way than the one you presented. Using observers should be fine even in pages that change elements often and in high quantities. Only thing that gives me bad feeling is observing the body, but again, I don't think there's a better way.
I'd consider starting the double-observing automatically in starter if the player element is not present at the time of injection. That way the flag won't be needed and we could prevent potential timing issues, which could otherwise cause headaches to people who try to add a connector but don't see what's actually happening under the hood.
What do you think?
I'm merging this anyway. We can continue in some new issue.


How to get realtime stream of the sampleBuffer after it was encoded by AVAssetWriter, anyone can help? Thanks

Hey @hery-sysu please use stackoverflow for discussions with keyboard 'PBJVision'
http://stackoverflow.com/questions/13010530/live-streaming-through-mp4


[BUG] The node name is not presenting in the prompt since the VM pod is not scheduled

To Reproduce
Steps to reproduce the behavior:

Enable VLAN
Create a VLAN name it vlan178
Disable VLAN
Create a VM using vlan178
Check the VM on the list

Expected behavior
The prompt should be displayed when the pod is scheduled.
Result
The node name is not presenting in the prompt since the VM pod is not scheduled

Environment:

Harvester ISO version:
Installation Mode: ISO/app-mode
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630):

Additional context
Add any other context about the problem here.

Validated on 0.2.0-rc1


Calling into Native Code is not supported in the context

Description
Sort of related to a few other issues I have created, this one deals with native code being called while debugging in general. I am using a debuggertypeproxy for the debug views. The proxies call into native code. In the example I show below, I have a few public properties defined on the proxy which show in the debug view. Those properties ultimately call native code and the evaluation fails.
I have blacked out a lot of the picture due to sensitive information. This is a general inquiry and bug report as this is not the only instance I have seen this behavior in. Whenever a debugged object seems to call into native code, evaluation fails.
Environment data
dotnet / vscode latest
omnisharp 1.25.1
OmniSharp log
Steps to reproduce
One thing to note is that I have I am not using DLLImport for the native method calls. I am using the NativeLibrary API to create function pointers to the native methods in the form: delegate* <x,y,z> NativeFunc. The function pointers are then executed as such: z = NativeFunc(x, y). I am not 100% sure, but fairly certain evaluation still fails with DllImport instead. Regardless, I need to use the function pointer mechanism for the native interaction, because I need to reload those pointers multiple times during runtime.
Expected  behavior
Evaluation works
Actual behavior
Evaluation fails
Additional context

This isn't really an O# issue, it's something the debugger doesn't support. @gregg-miskelly, not sure where to forward this to?

I think I would need more information in order to comment. "Evaluation of native methods in this context is not supported" errors come about because the debugger is in a scenario where it cannot execute real func-evals (force a real function to execute), so it falls back to interpreting IL. It's possible that your scenario is one where we are incorrectly interpreting when we don't need to be. It is probably more likely that this is "by design" because we really can't func eval. But I would need more information.

Can you explain what you mean by "real function"? Just to see what would happen, I replaced the native call in the code with a function pointer that does not call into the native method, but a managed method. I get the same result of "xxx calls into native code, context unsupported". I then went into Dot Peek to check out the IL. It seems like there is an issue with the calli instruction in the debugger.

Woops.. Trying to create the bare minimum example reveals a different issue. I know for a fact that I can twiddle the code around and get the debugger to show that Point struct properly with the native call, because I have done it. I will just have to remember how I did it..
Anyways, this is a bare minimum example that reveals yet another issue I have run into. The debug view fails silently. Instead of an exception somewhere in the view, it just doesn't show any of the fields. Would be nice to have a Debug.WriteLine somewhere when exceptions are thrown internally so we can see when it fails in the debug console.
You can comment / uncomment the native call (GetPos) in the view constructor and see the view fail / not fail.
tst.zip

Ah! There it is. Change struct Foo to class Foo OR readonly struct foo. No clue why, but now it magically works fine.
Likewise if I change my object in the original issue to readonly struct instead of struct, now it works.
Debugger doesn't like regular structs

I also have this problem. For example, this conditional breakpoint expression reports an error because it calls a native method: System.IO.Directory.GetCurrentDirectory() == "". This is just a simple example, but in my real-world use cases, I would like to be able to use conditional breakpoints to detect error conditions in hardware devices and to do that, the .NET methods need to call native methods.
This limitation exists in Visual Studio 2022 also and I upvoted an similar issue on the developer community. I am using .NET framework 4.6.2 because it is required by some third-party dependencies.


secret "cert-manager-webhook-webhook-tls" not found

Bugs should be filed for issues encountered whilst operating cert-manager.
You should first attempt to resolve your issues through the community support
channels, e.g. Slack, in order to rule out individual configuration errors.
Please provide as much detail as possible.

Describe the bug:

use helm install jetstack/cert-manager
webhook fails to start MountVolume.SetUp failed for volume "certs" : secret "cert-manager-webhook-webhook-tls" not found
cert-manager doesnt work, cant apply clusterissuers, cant issue certs, nothing cert-manager related seems to be functioning properly

Expected behaviour:
functioning properly
Steps to reproduce the bug:
Steps to reproduce the bug should be clear and easily reproducible to help people
gain an understanding of the problem.
Anything else we need to know?:
Environment details::

Kubernetes version: 1.14.1
Cloud-provider/provisioner: bare-metal/kubespray
cert-manager version: helm repo update, 0.8.0?
Install method: helm
/kind bug

user@laptop:~$ kubectl --context=dev3 -n kube-system get pod | grep cert-manager
cert-manager-6b7c647548-cgrfj                    1/1     Running             0          10m
cert-manager-cainjector-6bbbd87b97-vjrlc         1/1     Running             0          10m
cert-manager-webhook-5bdc99c85d-r462t            0/1     ContainerCreating   0          10m
user@laptop:~$ kubectl --context=dev3 -n kube-system describe pod cert-manager-webhook-5bdc99c85d-r462t
Name:               cert-manager-webhook-5bdc99c85d-r462t
Namespace:          kube-system
Priority:           0
PriorityClassName:  <none>
Node:               node-6qjgv/<IP_ADDRESS>
Start Time:         Tue, 28 May 2019 16:11:33 +0200
Labels:             app=webhook
                    pod-template-hash=5bdc99c85d
                    release=cert-manager
Annotations:        <none>
Status:             Pending
IP:
Controlled By:      ReplicaSet/cert-manager-webhook-5bdc99c85d
Containers:
  webhook:
    Container ID:
    Image:         quay.io/jetstack/cert-manager-webhook:v0.8.0
    Image ID:
    Port:          <none>
    Host Port:     <none>
    Args:
      --v=2
      --secure-port=6443
      --tls-cert-file=/certs/tls.crt
      --tls-private-key-file=/certs/tls.key
    State:          Waiting
      Reason:       ContainerCreating
    Ready:          False
    Restart Count:  0
    Environment:
      POD_NAMESPACE:  kube-system (v1:metadata.namespace)
    Mounts:
      /certs from certs (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-blf9p (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  certs:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  cert-manager-webhook-webhook-tls
    Optional:    false
  default-token-blf9p:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-blf9p
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type     Reason       Age                   From                 Message
  ----     ------       ----                  ----                 -------
  Normal   Scheduled    10m                   default-scheduler    Successfully assigned kube-system/cert-manager-webhook-5bdc99c85d-r462t to node-6qjgv
  Warning  FailedMount  108s (x4 over 8m39s)  kubelet, node-6qjgv  Unable to mount volumes for pod "cert-manager-webhook-5bdc99c85d-r462t_kube-system(7f21058b-8152-11e9-9a03-525400aaece4)": timeout expired waiting for volumes to attach or mount for pod "kube-system"/"cert-manager-webhook-5bdc99c85d-r462t". list of unmounted volumes=[certs]. list of unattached volumes=[certs default-token-blf9p]
  Warning  FailedMount  26s (x13 over 10m)    kubelet, node-6qjgv  MountVolume.SetUp failed for volume "certs" : secret "cert-manager-webhook-webhook-tls" not found
user@laptop:~$ kubectl --context=dev3 -n kube-system get secret --all-namespaces | grep cert-manager-webhook-webhook-tls
user@laptop:~$

Out of curiosity, does the cert-manager namespace have the correct label?

apiVersion: v1
kind: Namespace
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"v1","kind":"Namespace","metadata":{"annotations":{},"labels":{"certmanager.k8s.io/disable-validation":"true","name":"kube-system"},"name":"kube-system"}}
  creationTimestamp: "2019-05-22T12:54:58Z"
  labels:
    certmanager.k8s.io/disable-validation: "true"
    name: kube-system
  name: kube-system
  resourceVersion: "1663"
  selfLink: /api/v1/namespaces/kube-system
  uid: ce1a4e71-7c90-11e9-9a03-525400aaece4
spec:
  finalizers:
  - kubernetes
status:
  phase: Active

@jaitaiwan

is it a requirement to put it in the cert-manager namespace?

kubectl --context=<some other cluster> -n kube-system get secret cert-manager-webhook-webhook-tls -oyaml | kubectl --context=dev3 -n kube-system apply -f -
copying the secret from another cluster seemed to fix it.

I'm facing now the same issue. Myself I also installed everything in kube-system. Is there a problem with that? who is responsible for creating that tls secret? Namespace is also annotated as asked above.

This is not a closed bug, also having this issue. Copying it manually from another cluster defeats the point of installing with Helm.

I got this bug but for maybe a different reason:
Make sure you don't have another certmanager running in your cluster as it will own the lease for leader controller election.
If the new cert-manager pod cannot get the lease, it will not run the secret bootstrap controller hence it will not be able to initialize the webhook pod!

I am having the same issue with v0.11.0 on a fresh cluster. Please reopen the issue

I had  the same trouble with secret "cert-manager-webhook-webhook-tls" not found
My cert-manager deployed from manifest, so update i did by this command:
kubectl apply      \
         --validate=false  \
        -f https://github.com/jetstack/cert-manager/releases/download/v0.8.1/cert-manager.yaml

For me helped just apply new manifest twice. After this pod cert-manager-webhook started as expected.

Confused, why didn't fix it

I ran into the same issue, but @lainra hint helped. I removed and installed a new version of cert-manager using regular manifests, while not aware that a version of cert-manager was running that has been installed using helm.
Check:
helm ls --all cert-manager
if you have the same issue.
After removing all versions of cert-manager including the helm version using:
helm del --purge cert-manager
and installing v 0.12.0 using helm everything seems to work fine.

I am running into the same but there is only one cert-manager
helm ls --namespace cert-manager
NAME        	NAMESPACE   	REVISION	UPDATED                                	STATUS  	CHART               	APP VERSION
cert-manager	cert-manager	2       	2019-12-16 18:40:14.296856384 +0100 CET	deployed	cert-manager-v0.12.0	v0.12.0

and
du@clawfinger  ~  kubectl get pods --all-namespaces
NAMESPACE       NAME                                       READY   STATUS              RESTARTS   AGE
cert-manager    cert-manager-784bc9c58b-xq25x              1/1     Running             0          20m
cert-manager    cert-manager-cainjector-85fbdf788-d8s5l    0/1     CrashLoopBackOff    9          28m
cert-manager    cert-manager-webhook-76f9b64b45-brpp5      0/1     ContainerCreating   0          28m
default         multitool                                  1/1     Running             0          88m
ingress-nginx   default-http-backend-67cf578fc4-lr5jw      1/1     Running             0          32h
ingress-nginx   nginx-ingress-controller-7gczj             1/1     Running             0          32h
ingress-nginx   nginx-ingress-controller-x5j2x             1/1     Running             0          32h
kube-system     calico-kube-controllers-5fd6f588f8-jhtl5   1/1     Running             1          107m
kube-system     calico-node-82s74                          1/1     Running             0          92m
kube-system     calico-node-qv7fg                          1/1     Running             0          92m
kube-system     coredns-5c59fd465f-nlwcw                   1/1     Running             0          32h
kube-system     coredns-5c59fd465f-z8jvg                   1/1     Running             0          32h
kube-system     coredns-autoscaler-d765c8497-hrkzk         1/1     Running             0          32h
kube-system     metrics-server-64f6dffb84-5mwrk            1/1     Running             0          32h
kube-system     rke-coredns-addon-deploy-job-mldcf         0/1     Completed           0          32h
kube-system     rke-ingress-controller-deploy-job-wxvt7    0/1     Completed           0          32h
kube-system     rke-metrics-addon-deploy-job-szd4v         0/1     Completed           0          32h
kube-system     rke-network-plugin-deploy-job-d9cbg        0/1     Completed           0          32h

we are also facing the same issue @papanito facing.

I could able to fix this issue downgrading the cert-version to version 10, why decided to downgrade is, when you check the cert-manager releases, from release version 11, cert-manager has changes the apiVersions : https://github.com/jetstack/cert-manager/releases/tag/v0.11.0
Version 11, version 12 is not compatible with my kuberenetes cluster, friends please take this point into your mind also
cc @papanito

@papanito Whats your output of: kubectl describe pod cert-manager-cainjector-85fbdf788-d8s5l and kubectl logs cert-manager-cainjector-85fbdf788-d8s5l?
@AdimUser Glad it works for you, but why is version 11 / 12 not compatible? We have version 12 running smoothly, but had to adapt our api references.

 kubectl describe pod  cert-manager-cainjector-6659d6844d-mpxc7 -n cert-manager
Name:         cert-manager-cainjector-6659d6844d-mpxc7
Namespace:    cert-manager
Priority:     0
Node:         <IP_ADDRESS>/<IP_ADDRESS>
Start Time:   Tue, 17 Dec 2019 17:55:34 +0100
Labels:       app=cainjector
              app.kubernetes.io/instance=cert-manager
              app.kubernetes.io/managed-by=Tiller
              app.kubernetes.io/name=cainjector
              helm.sh/chart=cert-manager-v0.12.0
              pod-template-hash=6659d6844d
Annotations:  cni.projectcalico.org/podIP: <IP_ADDRESS>/32
Status:       Running
IP:           <IP_ADDRESS>
IPs:
  IP:           <IP_ADDRESS>
Controlled By:  ReplicaSet/cert-manager-cainjector-6659d6844d
Containers:
  cert-manager:
    Container ID:  docker://674aeca3b8baed3c230c349e9bfea0f50b3cc287adddb6733e282e306712ed49
    Image:         quay.io/jetstack/cert-manager-cainjector:v0.12.0
    Image ID:      docker-pullable://quay.io/jetstack/cert-manager-cainjector@sha256:9ff6923f6c567573103816796df283d03256bc7a9edb7450542e106b349cf34a
    Port:          <none>
    Host Port:     <none>
    Args:
      --v=2
      --leader-election-namespace=kube-system
    State:          Terminated
      Reason:       Error
      Exit Code:    255
      Started:      Tue, 17 Dec 2019 17:56:11 +0100
      Finished:     Tue, 17 Dec 2019 17:56:41 +0100
    Last State:     Terminated
      Reason:       Error
      Exit Code:    255
      Started:      Tue, 17 Dec 2019 17:55:38 +0100
      Finished:     Tue, 17 Dec 2019 17:56:08 +0100
    Ready:          False
    Restart Count:  1
    Environment:
      POD_NAMESPACE:  cert-manager (v1:metadata.namespace)
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from cert-manager-cainjector-token-lhz85 (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  cert-manager-cainjector-token-lhz85:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  cert-manager-cainjector-token-lhz85
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type     Reason     Age               From                Message
  ----     ------     ----              ----                -------
  Normal   Scheduled  <unknown>         default-scheduler   Successfully assigned cert-manager/cert-manager-cainjector-6659d6844d-mpxc7 to <IP_ADDRESS>
  Normal   Pulled     9s (x2 over 42s)  kubelet, <IP_ADDRESS>  Container image "quay.io/jetstack/cert-manager-cainjector:v0.12.0" already present on machine
  Normal   Created    8s (x2 over 41s)  kubelet, <IP_ADDRESS>  Created container cert-manager
  Normal   Started    8s (x2 over 41s)  kubelet, <IP_ADDRESS>  Started container cert-manager
  Warning  BackOff    <invalid>         kubelet, <IP_ADDRESS>  Back-off restarting failed container

and
kubectl describe pod cert-manager-webhook-547567b88f-b7fzk    -n cert-manager
Name:           cert-manager-webhook-547567b88f-b7fzk
Namespace:      cert-manager
Priority:       0
Node:           <IP_ADDRESS>/<IP_ADDRESS>
Start Time:     Tue, 17 Dec 2019 17:55:36 +0100
Labels:         app=webhook
                app.kubernetes.io/instance=cert-manager
                app.kubernetes.io/managed-by=Tiller
                app.kubernetes.io/name=webhook
                helm.sh/chart=cert-manager-v0.12.0
                pod-template-hash=547567b88f
Annotations:    <none>
Status:         Pending
IP:
IPs:            <none>
Controlled By:  ReplicaSet/cert-manager-webhook-547567b88f
Containers:
  cert-manager:
    Container ID:
    Image:         quay.io/jetstack/cert-manager-webhook:v0.12.0
    Image ID:
    Port:          <none>
    Host Port:     <none>
    Args:
      --v=2
      --secure-port=10250
      --tls-cert-file=/certs/tls.crt
      --tls-private-key-file=/certs/tls.key
    State:          Waiting
      Reason:       ContainerCreating
    Ready:          False
    Restart Count:  0
    Liveness:       http-get http://:6080/livez delay=0s timeout=1s period=10s #success=1 #failure=3
    Readiness:      http-get http://:6080/healthz delay=0s timeout=1s period=10s #success=1 #failure=3
    Environment:
      POD_NAMESPACE:  cert-manager (v1:metadata.namespace)
    Mounts:
      /certs from certs (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from cert-manager-webhook-token-lf56p (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  certs:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  cert-manager-webhook-tls
    Optional:    false
  cert-manager-webhook-token-lf56p:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  cert-manager-webhook-token-lf56p
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type     Reason       Age                       From                   Message
  ----     ------       ----                      ----                   -------
  Normal   Scheduled    <unknown>                 default-scheduler      Successfully assigned cert-manager/cert-manager-webhook-547567b88f-b7fzk to <IP_ADDRESS>
  Warning  FailedMount  <invalid>                 kubelet, <IP_ADDRESS>  Unable to attach or mount volumes: unmounted volumes=[certs], unattached volumes=[cert-manager-webhook-token-lf56p certs]: timed out waiting for the condition
  Warning  FailedMount  <invalid> (x9 over 118s)  kubelet, <IP_ADDRESS>  MountVolume.SetUp failed for volume "certs" : secret "cert-manager-webhook-tls" not found

Can the issue please be re-opened?

Any clue how to fix this on short term?

@papanito Whats your output of: kubectl describe pod cert-manager-cainjector-85fbdf788-d8s5l and kubectl logs cert-manager-cainjector-85fbdf788-d8s5l?
@AdimUser Glad it works for you, but why is version 11 / 12 not compatible? We have version 12 running smoothly, but had to adapt our api references.

I suspect, my kubernetes cluster version is tool old to support new certs apis, This is only a  doubt

I tried now version 0.10.0, 0.11.0 and 0.12.0 with the same issue. May this be related to latest k8s 1.16?

I've created a separate issue #2484 cause I guess is worth it.

Hi there, I received this exact error and upon pod description received this information:

I don't know why cert-manager didn't work suddenly.
I got help on the site(https://cert-manager.io/docs/tutorials/acme/ingress/.) and solved it.

I get the error:
E0526 04:13:09.767432       1 sources.go:193] cert-manager/inject-controller "msg"="unable to fetch associated secret" "error"="Secret \"cert-manager-webhook-tls\" not found" "resource_kind"="ValidatingWebhookConfiguration" "resource_name"="cert-manager-webhook" "resource_namespace"="" "secret"={"Namespace":"cert-manager","Name":"cert-manager-webhook-tls"}
But it looks like the secret exists?
Name:         cert-manager-webhook-tls
Namespace:    cert-manager
Labels:       <none>
Annotations:  cert-manager.io/allow-direct-injection: true

Type:  kubernetes.io/tls

Data
====
ca.crt:   1192 bytes
tls.crt:  1289 bytes
tls.key:  1679 bytes

https://github.com/jetstack/cert-manager/issues/1730#issuecomment-541370895

Can you please test this with 0.15 or 0.16, we did a lot of improvements. We no longer support 0.11.
Going to close this again if you see this in the latest version feel free to make a new issue for this.
/close

testing with 1.0.1, this is still an issue

@Kampe we no longer mount any secrets in, can you make a new issue?

I spoke too soon, this is only an issue if you have multiple versions issues going on, wipe clean and all is well.


[QIP][DAITO] Create Bucket in Huawei cloud fails with 500 error but succeeds in Backend

Steps:
Create Bucket with Huawei_obs as backend
Create fails with error 500 internal server.
Message is displayed in UI too.
But from backend DB the bucket is created.
Once page is refreshed, bucket appears in UI too

From browser:
Request URL: http://<IP_ADDRESS>:8088/v1/s3/aksbkt1
Request Method: PUT
Status Code: 500 Internal Server Error
Remote Address: <IP_ADDRESS>:8088
Referrer Policy: no-referrer-when-downgrade
mysql> select * from buckets;
+------------+----------------------------------+----------------------------------+---------------------+--------+----------+---------+------+--------------------------+------+------+--------+------------+-------------+---------------------+
| bucketname | tenantid                         | userid                           | createtime          | usages | location | deleted | tier | acl                      | cors | lc   | policy | versioning | replication | update_time         |
+------------+----------------------------------+----------------------------------+---------------------+--------+----------+---------+------+--------------------------+------+------+--------+------------+-------------+---------------------+
| aksbkt2    | 94b280022d0c4401bcf3b0ea85870519 | 558057c4256545bd8a307c37464003c9 | 2020-01-30 18:40:36 |      0 | aws_bknd |       0 |    1 | {"cannedAcl": "private"} | null | null | ""     | Disabled   | null        | 2020-01-30 13:10:36 |
| aksbkt1    | 94b280022d0c4401bcf3b0ea85870519 | 558057c4256545bd8a307c37464003c9 | 2020-01-30 19:00:44 |      0 | hws_bknd |       0 |    1 | {"cannedAcl": "private"} | null | null | ""     | Disabled   | null        | 2020-01-30 13:30:44 |
+------------+----------------------------------+----------------------------------+---------------------+--------+----------+---------+------+--------------------------+------+------+--------+------------+-------------+---------------------+
2 rows in set (0.00 sec)

Closing since could not reproduce this. Please reopen if this issue persists

As you could not reproduce the issue, please attach a screenshot or evidence and then close the issue.

Sure @kumarashit .
Check out these screenshots below.

Thanks @anvithks


Post-Mortem: Changes to Prepare for Next Week

Summarizing the steps to begin hardening our system for next week. Please add anything I may have missed from our discussion.

Merge PR #119 to move Data Manager into chat & cleo services
Merge PR #109 to finish updates to A2rchi Meta
Create PR to move lock from guarding OpenAI calls and only guard update(s) to vector store
Merge this^ PR to main
Write simple script w/for loop to submit N API calls to our Flask app, measure and plot histogram of latencies for N = [10, 100, 1000, 10000]

Call A2rchi at t3desk19.mit.edu:7683 ~5 times using the PSET 7 question to get some sense of the distribution for the latency
Simulate N calls to Flask app by deploying DumbLLM in dev but on t3desk19 with time.sleep(np.random.normal(mean, std)) where mean and std are guesstimates of latency parameters based on calls to t3desk19.mit.edu

Running experiment on t3desk  is important b/c parallelism will be different compared with submit06

Record and store results

Depending on performance results from 5., we may have to contemplate load-balancing w/multiple containers

And separately but also importantly:
7. remove raise e from inside our main try-except block in ChatWrapper

One edit here is that Ludo raised an issue (#115) that the DumbLLM is no longer compatible. We need to resolve this issue before we get to step 5 with a PR

Another final addition we will likely want to make is merging in my work on the db backend once it's ready. Without that we will also need to lock the conversations.json file (which is plausible), but could harm performance.

I believe we also discussed introducing timeouts in the requests in the app. Not sure if we want to open an issue about that.

With the new PR for request timeouts (#141), I believe we can close this issue once the PR is merged.


Slice len is always non-negative

Mostly a stylistic change but also might improve assembly. However, changed lines are not hot. WDYT ?

@cristaloleg I don't really see this making any difference, since it is just swapping one instruction for another similar one. But I don't mind it as a cleanup thing.


Puzzle pieces are blocked on the "Block Puzzle" game

Describe the bug
Dear developer!
In the process of using, I found a bug in layout / display. As shown in the figure below, on the main page, puzzle pieces at the bottom of this page could not be seen fully. This may be an adaptation problem. I suspect it is because display and font size are set to large (mainly due to display size).
Because of some problems with my eyesight, I often use the largest font and display.

App version is 7.0, my mobile phone is Google Pixel 2, and the screen resolution setting is 1920* 1080.  Also, my Android system version is 10.0.
The above is a description of the problem. The overall experience of the software is good. You can see that the design is very attentive. Thank you very much for the efforts of the developers all the time. I hope to receive a reply. Thank you so much!!
Expected behavior
I hope that I can see all of the pieces fully, and in this circumstance, part of them seem to be blocked.
Steps to reproduce the behavior:

use the largest font and display in the display setting
open this app for the very first time
click "STONE WARS"
click "CONTINUE"
click "Liberate planet (Block Puzzle)"
this error could be seen

Screenshot
(The blocked parts are circled in red rectangles)

Environment

Version of blockpuzzle: 7.0
Device : Google Pixel 2,
OS version : Android 10.0

Thank you for your contribution. I will process this in about a month.


Automatically start in insert mode when inside the terminal

As above /\ also make it toggleable.

autocmd BufEnter term://* startinsert
autocmd BufLeave term://* stopinsert
This is what worked for me although I see a lot of people using
:au BufEnter * if &buftype == 'terminal' | :startinsert | endif


Same partition consume by two distinct consumer under the same groupID

Describe the bug
With a code I consume a topic under a consumer group id then I run a second instance under the same groupId and the same topic
So I expect that each consumer handle their half of topic partition (and with a auto commit set to 1 message, I expect maximum 1 duplicate due to balancing)
But I get a batch size duplicate (and even multi times if more than 2 consumer instances) and that can be really large number (like 50% of duplicate)
I observe that:

Consumer 1 start.
Consumer 1 get a batch from a partition 1.
Consume 1 end the and get another from partition 2.
Consumer 2 start.
Consumer 1 and 2 emit consumer.events.GROUP_JOIN
Consumer 2 get a batch from partition 2
Consumer 1 get a batch from partition 1
But Consumer 1 process message from partition 1 and 2 batch

To Reproduce
const consumer = kafka.consumer({
      groupId,
      allowAutoTopicCreation: false
 })
await consumer.connect()
await consumer.subscribe({ topic, fromBeginning: true })
consumer.run({
    autoCommitThreshold: 1,
    eachMessage: async ({ topic, partition, message }) => {
      await new Promise((resolve) => setTimeout(resolve, 1000))
      console.log(`P${partition}-M${message.offset}`)
    }
  })

On a topic with already data (with 2 partition for reproduce easily the issue)
lunch a first instance.
wait to process some message.
lunch a second instance.
look your logs.

My logs:
Instance1:
{"message":"Begin of P6-BatchSize3061-BeginAt776428-EndAt779488","level":"info"} <- START_BATCH_PROCESS events
P6-M776428 <- P for partition and M with message offset
P6-M776429
P6-M776430
P6-M776431
P6-M776432
P6-M776433
P6-M776434
P6-M776435
P6-M776436
P6-M776437
P6-M776438
P6-M776439
P6-M776440
P6-M776441
P6-M776442
P6-M776443
{"message":"Begin of P7-BatchSize3056-BeginAt776697-EndAt779752","level":"info"}
{"message":"consumer.events.GROUP_JOIN","level":"warn"} <- GROUP_JOIN events
P7-M776697
{"message":"Begin of P8-BatchSize3055-BeginAt777232-EndAt780286","level":"info"}
P8-M777232
P7-M776698
P8-M777233
P7-M776699
P8-M777234
P7-M776700
P8-M777235
P7-M776701
P8-M777236
P7-M776702
P8-M777237
P7-M776703
P8-M777238
P7-M776704
P8-M777239
P7-M776705
P8-M777240
P7-M776706
P8-M777241
P7-M776707

Instance 2
{"message":"consumer.events.GROUP_JOIN","level":"warn"}
{"message":"Begin of P7-BatchSize3056-BeginAt776697-EndAt779752","level":"info"}
P7-M776697
P7-M776698
P7-M776699
P7-M776700
P7-M776701
P7-M776702
P7-M776703
P7-M776704
P7-M776705

Environment:

OS: windows 10 (but also with docker and node:12.22.4 image)
KafkaJS version 1.15.0
Kafka version 2.7.x
NodeJS 12.22.4

Hi @20011127 . any news regarding that ?
we are facing the same issue


Update React guides to react-scripts 5.0.0

Working on Vote/Poll SDK I noticed new issues with create-react-app 5.0.0.
It looks like it's possible to use cra-webpack-rewire to work around these issues (polyfills) without ejecting from cra.
Guides and example should be updated as the polyfill issues are non-trivial.

Done with https://github.com/vacp2p/docs.dappconnect.dev/pull/19


OWLS-74720: update the image name used in the create weblogic domain samples

Manually run the two create weblogic domain samples, domain-home-in-image and domain-home-on-pv samples. Both works fine.
Jekins job is running. http://wls-jenkins.us.oracle.com/job/weblogic-kubernetes-operator-javatest/1708/

PR 1085 does not contain modifications to these two README.md files.
If the README.md files are not used anymore, they need be removed.
If we still need them, we need update the cross-reference in the two files. The correct cross-reference should be [WebLogic Docker images](../../../../../site/v2.0.1/weblogic-docker-images.md.

Simon, in the new docs, these README files are docs-source/content/samples/simple/domains/domain-home-on-pv/_index.md and docs-source/content/samples/simple/domains/domain-home-in-image/_index.md. I agree that the old README.md files are not used and should be removed.
Please review the _index.md files in PR1085 to align the image names with your results.

The removed README.md files are still referenced by kubernetes/samples/README.md file. We probably need to change the kubernetes/samples/README.md to point to the new doc locations: docs-source/content/samples/simple/domains/domain-home-in-image/_index.md and  docs-source/content/samples/simple/domains/domain-home-on-pv/_index.md.


Branch 0.6 Groovy Interpreter

What is this PR for?
Groovy Interpreter
What type of PR is it?
Feature
Todos

[Code] - Task
[Samples] - Task
[Documentation] - Task
[Test cases] - Task

What is the Jira issue?
TODO
How should this be tested?
Outline the steps to test the PR here.
Samples
%groovy
//get a parameter defined as z.angularBind('ngSearchParam', value, 'paragraph_id')
//g is a context object for groovy to avoid mix with z object?
def param = g.angular('ngSearchParam')
//send request https://www.googleapis.com/customsearch/v1?q=ngSearchParam_value
def r = HTTP.get(
  //assume you defined groovy interpreter property `search_baseurl`='https://www.googleapis.com/customsearch/v1'
  //in groovy object o.getProperty('A') == o.'A' == o.A == o['A']
  url : g.search_baseurl,
  query: [ q: param ],
  headers: [
    'Accept':'application/json',
    //'Authorization:' : g.getProperty('search_auth'),
  ]
)
//check response code
if( r.response.code==200 ) {
  g.html().with{
    //g.html() renders %angular to output and returns groovy.xml.MarkupBuilder
    h2("the response ${r.response.code}")
    span( r.response.body )
    h2("headers")
    pre( r.response.headers.join('\n') )
  }
} else {
  //just to show that it's possible to use println with multiline groovy string to render output
  println("""%angular
    <script> alert ("code=${r.response.code} \n msg=${r.response.message}") </script>
  """)
}

%groovy

//renders a table with headers a, b, c  and two rows
g.table(
  [
    ['a','b','c'],
    ['a1','b1','c1'],
    ['a2','b2','c2'],
  ]
)

Questions:

Does the licenses files need update?
no
Is there breaking changes for older versions?
no
Does this needs documentation?
yes

Thanks for contributing new Groovy interpreter but we didn't manage the branch-0.6 anymore. Can you rebase your contribution onto current master?

Hello
Current - is it next to 0.7 ?
30 January 2017, 08:02:58, by Jongyoul Lee <<EMAIL_ADDRESS>>:
Thanks for contributing new Groovy interpreter but we didn't manage the branch-0.6 anymore. Can you rebase your contribution onto current master? —
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub , or mute the thread .
-- Regards, Dmitry

If you contribute code based on master, we will review and merge it into master and branch-0.7 if necessary.

Right - please develop against master and open a new PR.

and please add interpreter documentation .md file and update license information as suggested in the PR template Does the licenses files need update? should be yes.

created a new pull request #2068


Plugin does not load; WSL2 Ubuntu

I have installed the plugin, both manually and using Plug.  When I :UpdateRemotePlugins nothing is added to the remote manifest and, of course, none of the ex mode commands are available.
:checkhealth shows python 3.10.0 and the latest pynvim.
I stripped out all other plugins, and almost all key bindings and other settings, and had the same issue.
I installed Deoplete to verify that remote plugins work.
I was running an older nvim installed by apt, so I upgraded to a 0.9 build from https://launchpad.net/~neovim-ppa/+archive/ubuntu/unstable, but this did not resolve the issue.
I have tried setting g:coqtail_coq_path and g:coqtail_coq_prog to the directory and filename for coqtop.
This is different than https://github.com/whonore/Coqtail/issues/245, the other currently open, unable to reproduce WSL2 issue, as in that case the ex mode commands are present.
I'm unsure how to get any logs or other debug information, though I'm glad to follow any steps you prescribe or to provide any additional details.

Thank you, Wolf.  With your instructions, I was able to resolve the issue.
The key was adding the install location to rtp.
For what it is worth, it had the same behavior when I tried to install it on Windows (not WSL) and on a Mac.  I was surprised it didn't work on the Mac, anyway, since that's less odd than WSL and Windows.  That said, you would expect others to have had a similar issue, and I've been away from n/vim for a while, so perhaps I'm missing something that would be obvious to others.  On the other hand, if it is something you want to dig into, reopen and I'll help however I can.
I am grateful for the help.  Also, your response and the digging around I did was interesting.  I learned some new (for me) things about nvim.  I appreciate it.
For posterity, and/or other people who find this later:
Before hand, all of the variables were undefined except for b:did_ftplugin.  Makes sense, since it wasn't being loaded.  Likewise, there were no items in the log.
After wards, the variables were defined, and the log had similar entries:
006.204  000.013  000.013: sourcing /home/dan/.local/share/nvim/plugged/Coqtail/ftdetect/coq.vim

019.059  000.100  000.100: sourcing /home/dan/.local/share/nvim/plugged/Coqtail/autoload/coqtail/compat.vim

166.545  147.657  118.057: sourcing /home/dan/.local/share/nvim/plugged/Coqtail/autoload/coqtail.vim
169.675  150.852  003.195: sourcing /home/dan/.local/share/nvim/plugged/Coqtail/ftplugin/coq.vim
170.509  000.288  000.288: sourcing /home/dan/.local/share/nvim/plugged/Coqtail/indent/coq.vim
173.646  002.925  002.925: sourcing /home/dan/.local/share/nvim/plugged/Coqtail/syntax/coq.vim


Upgrade to Drive API v3

npm i -D @types/gapi.client.drive@v3
change all FileListResource to FileList
change all FileResource to File
change all PermissionResource to Permission
change all PermissionResource[] to PermissionList
change any owners arguments to type User[]
Fix errors
update Drive API version in script

With this will be possible use shared drives?

No unfortunately that's a separate upgrade. There is another issue tracking team drives /shared drives support


ImportError in 'from kernels import *': Undefined Symbol in bitsandbytes/libbitsandbytes_cuda117.so

when executing the line from kernels import *. Below is the error trace for reference:
===================================BUG REPORT===================================
Welcome to bitsandbytes. For bug reports, please submit your error trace to: https://github.com/TimDettmers/bitsandbytes/issues
================================================================================
...
AttributeError: /root/anaconda3/envs/group_chat/lib/python3.10/site-packages/bitsandbytes/libbitsandbytes_cuda117.so: undefined symbol: cdequantize_blockwise_fp16_nf4. Did you mean: 'cdequantize_blockwise_fp32'?

The main issue seems to stem from an undefined symbol cdequantize_blockwise_fp16_nf4 in libbitsandbytes_cuda117.so. The system suggests an alternative cdequantize_blockwise_fp32, but it's unclear if this is a suitable substitute.

same issue here but with cuda118:
/opt/conda/lib/python3.10/site-packages/bitsandbytes/libbitsandbytes_cuda118.so:
undefined symbol: cdequantize_blockwise_bf16_nf4

Oh my interesting @sd3ntato @GavinZhao19
Can you both tell me approx what GPU, Pytorch version.
Also can you try ldconfig /usr/lib64-nvidia

@danielhanchen Thanks for your response! Here are the details of my setup:

GPUs: I'm using two NVIDIA A800 GPUs.
NVIDIA Driver Version: 525.125.06
CUDA Version: 12.0
Python Version: 3.10.12
PyTorch Version: 2.1.1
Transformers Library Version: 4.33.2
DeepSpeed Version: 0.10.0

@GavinZhao19 Hmmm weird very weird - have you tried many an entirely new env?

@sd3ntato @GavinZhao19 If you found a fix - it'll be cool if you could share how you got it to work!
Likewise if not, have you tried reinstalling Unsloth? I'll close this issue for now! Reopen whenever!


json schema should be stored in the database and linked to the form data

[ ]  Update the application JSON schema to be a JSON object
[ ] Create a form table that contains a single record, with an intake1schema slug. The record must be inserted after deploying the sqitch changes, in an idempotent way, allowing for non-breaking changes in prod (see ciip]. If we want to keep our json schema in multiple files, we can consider having a server-side function writing it to the DB (if needed) at boot time.
[ ] The ApplicationForm component retrieves the json schema from the db
[ ] The submit_application mutation takes the total number of acknowledgements from the json schema rather than the constant

Hey team! Please add your planning poker estimate with Zenhub @AntBush @marcellmueller @matthieu-foucault @wenzowski

Hey team! Please add your planning poker estimate with Zenhub @VB-at-Bis @wenzowski

@MarsRomer I seem to have issues with it in test though it's working great on my local machine. Sorry about this.


Where to install Lustre_exporter

Hi, this is more a question than an issue.  Where is the best place to install the exporter -- on the lustre server(s) or the lustre clients?  If I put it only on the servers, will it also collect client traffic metrics?   Thanks.

Thanks for the response and info, Gabriele.  I notice that you have forked the H-P lustre exporter to your own.  Can you tell me what is different about yours vs. the H-P one listed by Prometheus (though not as an official exporter)?
best,
Greg

Hi Greg,
up to now we got mainly:

partial support for Lustre 2.12, see: https://github.com/GSI-HPC/lustre_exporter/issues/7
a new metric for Lustre Changelogs
support for newer golang version with less dependencies
added build container
improved parsing for Lustre Jobstats

You can get an overview by checking the closed issues of the project here.
For more detailed information check the commits after the last commit after the HP fork.
Best
Gabriele

Hi @gabrieleiannetti,
If you are interested, it would be very nice that you contact a Prometheus forum to add your fork to the https://github.com/prometheus-community repository.
I guess, you will need an approval from<EMAIL_ADDRESS>too.

I am not a dev, so please forgive if this suggestion does not make sense.  But instead of a second Lustre_exporter, may I suggest merging @gabrieleiannetti enhancements to this Lustre_exporter?  Thus making for one, stronger, exporter.  Thx


Multi gene

I think Multi-gene has been tested and generally works, so I'm ready to try to merge Multi-gene branch into the original branch

Wow, that was scary, my first merge of a branch. I think it worked


Add link-ippvm, allows for static linking on linux

When trying to statically link (2019.5.281) on Linux, some functions from ipps depends on ippvm. Adding this seems to fix static linking, but my testing has been limited to just Linux and that IPP version.
link-ipps might need to depend on link-ippvm, in addition to these changes.

Thanks. I did a few cleanups and fixes and then published this as ipp-sys 0.4.4.


Emit events for BuildRun objects

Changes
Enhance the BuildRun controller to emit k8s events when build runs start
and complete. If a BuildRun fails, a Warning event is issued.
This is an initial implementation for #823
/kind feature
Submitter Checklist

[x] Includes tests if functionality changed/was added
[x] Includes docs if changes are user-facing
[x] Set a kind label on this PR
[x] Release notes block has been filled in, or marked NONE

Release Notes
The build controller will emit Kubernetes events when a BuildRun starts and completes. If the BuildRun fails, a Warning event will be issued.

@adambkaplan I agree on what Sascha mentioned, we should send this via a SHIP first. I´m doing the same in https://github.com/shipwright-io/build/pull/787#issuecomment-870853586 .

/close
Will reconsider/reopen this after discussing in a SHIP.


api delete endpoint

@maddalab @Primer42

LGTM
To get a faster approval, I'm adding @roymarantz and @defect

:+1:
this code is painful for me to read, but that is scale's fault not yours :-(


Fetching large json data results in OutOfMemoryError

Description
Using fetch to get several Megabytes (currently happens for me at around 80Mb) of JSON data causes Android to panic and throw an OutOfMemoryError. This is due to the fact that the whole response is being read as bytes, quickly filling up the heap.
Stacktrace:
09-01 21:32:21.035  5480  5555 E AndroidRuntime: java.lang.OutOfMemoryError: Failed to allocate a 98836368 byte allocation with 25165824 free bytes and 88MB until OOM, target footprint 133385952, growth limit 201326592
09-01 21:32:21.035  5480  5555 E AndroidRuntime: 	at okio.Buffer.readByteArray(Buffer.kt:1429)
09-01 21:32:21.035  5480  5555 E AndroidRuntime: 	at okio.Buffer.readByteArray(Buffer.kt:1424)
09-01 21:32:21.035  5480  5555 E AndroidRuntime: 	at okio.RealBufferedSource.readByteArray(RealBufferedSource.kt:238)
09-01 21:32:21.035  5480  5555 E AndroidRuntime: 	at okhttp3.ResponseBody.bytes(ResponseBody.kt:124)
09-01 21:32:21.035  5480  5555 E AndroidRuntime: 	at com.facebook.react.modules.blob.BlobModule$4.toResponseData(BlobModule.java:134)
09-01 21:32:21.035  5480  5555 E AndroidRuntime: 	at com.facebook.react.modules.network.NetworkingModule$2.onResponse(NetworkingModule.java:512)
09-01 21:32:21.035  5480  5555 E AndroidRuntime: 	at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:519)
09-01 21:32:21.035  5480  5555 E AndroidRuntime: 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
09-01 21:32:21.035  5480  5555 E AndroidRuntime: 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
09-01 21:32:21.035  5480  5555 E AndroidRuntime: 	at java.lang.Thread.run(Thread.java:923)

React Native version:
System:
    OS: Linux 5.13 Solus 4.3
    CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
    Memory: 1.39 GB / 15.52 GB
    Shell: 5.1.8 - /bin/bash
  Binaries:
    Node: 14.17.5 - /usr/bin/node
    Yarn: 1.22.10 - /usr/bin/yarn
    npm: 6.14.14 - /usr/bin/npm
    Watchman: Not Found
  SDKs:
    Android SDK: Not Found
  IDEs:
    Android Studio: Not Found
  Languages:
    Java: 1.8.0_302-solus - /usr/lib64/openjdk-8/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: 17.0.2 => 17.0.2
    react-native: 0.65.1 => 0.65.1
  npmGlobalPackages:
    *react-native*: Not Found

Steps To Reproduce
I created a test repository that shows the aforementioned behaviour. It also includes a 100Mb JSON file for testing, that you can serve locally or access via GitHub directly.
Steps are as follows

Tap on the load data button
Wait for the app to crash

Expected Results
Getting an out of memory error shouldn't really happen with this size of data in my opinion. Sure 100Mb sounds a lot at first, but in enterprise-grade apps this is probably a common scenario. In any case I think there should be a possibility to dynamically switch to streaming the response since okhttp offers bytestream and charstream as well. I'm not that well versed in Java but it would probably help reduce all of the 150Mb landing on the heap at once?
Snack, code example, screenshot, or link to a repository:
https://github.com/curtisy1/ReactNativeFetchRepro

Try add android:largeHeap label to your AndroidManifest.xml.
<application
   ...
+    android:largeHeap="true"
   ...
```/>

Thanks for trying to help @452MJ!
I am aware of that option but that's pretty much my last resort as I think there must be another way.
Simply put, there's probably thousands of apps - and among those a few RN apps as well - on the market fetching something (once, hence not directly streaming) with a size over 100Mb and I highly doubt they all have android:largeHeap set to true. Not to mention Google also does not directly recommend it as a fix to increasing performance or OOM errors.
There's also a very informative StackOverflow question with the general answer being "do not use if you absolutely have to"

I think this is a must for RN apps. Some of the apps I worked on in the past sometimes caused OOM crash due to downloading web images. Unlike native projects whose memory footprint rarely reaches 100MB, it is common for RN projects to hit 200-300MB. This is also a weak term in RN. So I set largeHeap to true for each project.
Maybe you can try run on Hermes jsengine.😬

Unlike native projects whose memory footprint rarely reaches 100MB, it is common for RN projects to hit 200-300MB

I completely agree with this one. But most of it is probably the JS overhead and not any native implementation. In this case, however, the issue is that the bytes are accessed directly, so we get the total size of our response added to our heap. OkHttp actually warns about this and advises streaming the response. I'm not experienced enough in native Android development to tell if this would be applicable in this case, but it sounds better than having an OOM or a large heap that might cause other side effects.
That's actually why I'm interested in what the react-native team has to say about this, because setting largeHeap seems like some workaround for a bigger issue to me

Maybe you can try  using axios to replace fetch

This probably wouldn't change anything as both fetch and axios work by sending XMLHttpRequests under the hood, which then get converted to a native call to OkHttp, causing the behavior above. The only thing it would probably change is that the JSON parsing would be up to the JS side of things. But if the request in itself fails (or more accurately, the initial response conversion on Android's native side), I won't even get to parsing any JSON.

Definitely not stale. But if I have the freedom to label it, I'll gladly add it to the backlog 😉

Exactly the same problem here. I have offline-first architecture in my app and i need to fetch some big data on startup. @curtisy1  did you find any solution to this problem?

@TommysG We didn't find any solution to this. What we tried doing was reduce the size of our responses and optimize them in a way that this issue is more unlikely to happen for our use case. That is more of a bandaid solution, however and I'm fairly certain we will easily reach that cap in production where larger data is quite common

@curtisy1 I found this library react-native-fetch-api. It's overriding the default implementation of react native's fetch and let you stream the data. But I don't know how to check, if the data I received is a valid JSON and how to parse it in chunks. Also I think this will be very slow with large data.
Lastly, you said that you have this problem working with 80mb or maybe 100mb of response body, but I have this problem working with 21mb response.

Seems like we are now also facing this in production.
@shergin Seeing as you're not on the React Native Core team anymore but still the codeowner according to the codeowners file. Do you know who's the right person to mention here, so this issue gets some love maybe?

Very sorry to necro-bump this but it's been two years with the only reply being from another react-native user trying to help and one having the same issue. Since then, the CODEOWNERS got removed as well, for staleness like dear stale bot once tried to do with this issue (until... well it was removed as well).
To clarify, this is probably a fairly niche issue but I don't really consider leaving an issue alone for two years a good thing.
In my attempt to get someone to actually look at this,  I, as a user don't have any other choice but randomly bump this and ping people I think might know how to help.
For future reference, maybe you folks could implement some kind of policy on what "Triage" actually means for you? When I filter for the tag, I get 46 pages with almost 1.3k issues back, the oldest being from 2020 (that's ~81% of all open issues!). I doubt any issue would be triaged this long considering you have tags for pretty much anything.
And before you ask, yes, I know this is a community project but it still runs under the Facebook/Meta umbrella so I would expect at least a bit of dedication towards issues opened by the community. Especially when I take the time to catch a stack trace and fill out the issue template.
Microsoft does a lot better than you in that regard, so please step up your game and actually respond to issues  :smile:  (fwiw I'd also accept a won't fix with a detailed explanation and way to move forward).
Ping @cortinico because you accepted the CODEOWNERS removal, so you're the only straw I can hold onto for this year

Hey @curtisy1
I can mention that our team looks at new issues every day. I personally go over most of them on a daily basis. The reality is that our team is just so small, and we can't answer to everyone, and also we can't fix every bug. We try to prioritize those that have most upvotes or are affecting the highest number of people.
Issues that gets picked up by the community and receive a PR, are the ones that most likely to get fixed and end in a release.
As for your specific issue, the problem you're having is that your response gets processed by the BlobModule, which is loading the full response in memory. I guess the problem is that you should not be using the BlobModule at for this specific request as it should be of type json. I'm unsure why this is happening and would need further investigation.

Same issue for me. I'm reading large JSON files up to 150mb.  On ios all works fine. I can load the entire JSON file and work with it. On anrdoid, anything over 15-20MB produces out of memory errors. Also looking to resolve this!