Gather feedback on training

I (Britt) was thinking I could host an interview style session with calhr folks to gather feedback on each training module which would inform future MDSA trainings.
I am happy to do it alone (which may be the safest format for CalHR folks to feel they can give honest feedback without the folks in the room with whom theyve done most of their trainings with). I am also happy to do it with Aeri as on the other hand their familiarity with them may solicit more honest feedback.

My next step on this would be to draft a questionnaire that we can use to guide the interview unless either of you have other thoughts on the best way forward? @jasonlally @AeriShan-ODI

I think drafting a questionnaire for the interview and sending around to the team is a great first step. We can briefly discuss at standup about whether @AeriShan-ODI should participate. I think it's fine you doing it from a more neutral standpoint.
Either way, drafting some questions would be great!

Agree with Jason's comment. I think a quick meeting with informal discussion might be helpful as an addition, if there is time.
One of the things I'm most interested in is getting a sense of fitting & adapting the training to the needs of different levels of experience as well as different learning styles. E.g. I think John was frustrated with the training and I can relate - I also learn by just diving in and doing.
I don't need to be involved unless it's helpful but I'm definitely curious about the feedback :)

Planning to reach out to CalHR team thursday morning - please review and leave feedback before then. Otherwise I will move forward with scheduling a session to gather feedback based on what i have.
https://docs.google.com/document/d/1YCy3c_Gex6RDxt9GwGpMkIi6vxYyvqd-BijVZtLhj18/edit
cc: @ian-r-rose @AeriShan-ODI @jasonlally

@britt-allen - this looks good to me! @AeriShan-ODI did you take a look? Everything good?

Yes, forgot to comment mainly because it also looks good to me!

Action Item: @britt-allen to send Survey to Joel, Scott, Tiare and will schedule training feedback with John and Brian.


Switch ace build from default to noconflict

Ace editor v1.2 overrides window.require() which cause some issue with application build with webpack. Switching to the build noconflict doesn't apply the override and make ace require() available under window.ace.require()
Repo with all available builds: https://github.com/ajaxorg/ace-builds

LGTM

Why did we switch to 1.2.2?

Why did we switch to 1.2.2?

1.2.0 is not available under any CDN 😩

LGTM

⚠ Make sure not to merge this branch before it is tested in botify-report


Add NUMBER support

Pull Request Etiquette

[x] I have checked the PRs for upcoming features/bug fixes.
[x] I have read the contributing guidelines.

Changes

[ ] Internal code
[x] Library interface (affecting end-user code)
[ ] Documentation
[ ] Other: _____

Closes Issue: #1744
Description
Adds support for the NUMBER (type 10) option for Slashcommands.
This also adds a DataObject#getAsDouble(String) method. Didn't add one for default values yet.
If I read the docs correctly is number one option that allows choices so I set the boolean for it.
I am not sure if I got all the places necessary updated, so please inform me if there are other ones missing.

I applied some new changes, but I'm not sure about a few things.
For once am I not sure how we should address fromData's handling of the value.
The if seems to check if it is a Number instance (Which double counts towards), but then only gets the value as int.
So I'm not sure if we could just change this to if (value instanceof Integer/Long) and add an else-if for the Double case...

I'm wondering if we should be using getNumber instead of getDouble to better match the Discord docs and also the OptionType.
It is definitely confusing that there is an OptionType.NUMBER but not getNumber

I'm wondering if we should be using getNumber instead of getDouble to better match the Discord docs and also the OptionType.
It is definitely confusing that there is an OptionType.NUMBER but not getNumber

I think a change to getNumber would be good. Will commit this real quick.

The second one could have a check for if both the value and defaultValue are null and throw in such a case, because then it could be a simple getX(String, null) call for the main method.
Downside I see here is, that we would need to use the non-primitive options for the defaultValue to have the nullability, which would probably be breaking...
But I feel like the duplicated code stuff should be reduced a bit...

After actually looking do I wonder where you want getDouble changed to getNumber
The Choice option has getAsDouble and that one matches the naming of the other options which are getAsString for String and getAsLong for long
By the logic you provided would we be required to also change getAsLong to getAsInt because Discord treats the info as Integer and the DataType is also declared as INT
The getDouble in the DataObject is also fine since there are other methods to get as string, (unsigned) integer and (unsigned) long...
I'm just a bit confused where stuff should change...

I created some private setters as suggested by @DV8FromTheWorld on Discord.
I'm not too sure about this because to achieve this did I had to remove the final from the values and apply default values instead.


Select Linting Issue

Closing this for now (cf. https://github.com/camunda/camunda-modeler/issues/3119).


Very long "blank" period when transitioning

After resizing, the process of switching between tabs to accordion and viceversa leaves the user with a blank screen, this doesn't seem to be a good user experience, maybe we could show a spinner during that time - or something along those lines.

Its not a long period - its just until the resizing is released, no big deal - closing this - Sorry. Ha!.


New Deployment Landing Page

Summary
This turns all of the links from the Install, Deploy, Upgrade, and Scale toctree into a structured guide. It also creates a redirect from the toctree page to point here.
Ticket Link
N/A

@BenLloydPearson @justinegeffen - This is a change we'll need to confirm working in Production. Previews won't be able to show us that a 301 redirect to a new page is working because that new page isn't available in Production yet.

@cwarnermm, would the orphan tag on the page create any build issues?

@justinegeffen I believe the orphan directive lets a document be built, but doesn't notify Sphinx that it isn't reachable via a toctree. All source files need to be part of some toctree, else Sphinx will spit out a warning on build because it means that the file in question won't be reachable via standard LHS navigation.
We should use the orphan directive on any source page we intentionally don't want to show up in the LHS (such as install subsections of content that we reuse across topics), but should not be used on any page the user would expect to get to via LHS navigation.


Where is the OTP number? I can't find it.  App fails if i enter random value.

Please go through Savedseats class and add your phone number, then run it again OTP will be sent to your entered mobile number.


vscode import/extensions no use

const path = require('path');

module.exports = {
  root: true,
  extends: [
    'dwing',
    'plugin:vue/recommended'
  ],
  rules: {
    'import/extensions': [2, 'always', { js: 'never', vue: 'never' }]
  },
  settings: {
    'import/resolver': {
      webpack: {
        config: 'build/webpack.config.js'
      }
    }
  }
};

// webpack
```js
  resolve: {
    modules: [
      'node_modules',
      path.resolve(__dirname, '../src')
    ],
    extensions: ['.js', '.vue', '.json', '.css'],
    alias: {
      vue$: 'vue/dist/vue.esm.js',
      public: path.resolve(__dirname, './public')
    }
  }

source code can found: https://github.com/AirDwing/vuetify-demo/blob/master/src/router/index.js#L3

What happens on the command line? Editor integrations often have issues; eslint CLI is what's important to test.

Linting should be run via an npm run-script, and should be run on the command line as part of tests and CI. You shouldn't have or need a global eslint installation.

sourcecode at: https://github.com/AirDwing/vuetify-demo/

Try npx eslint .?

 ~/Desktop/vuetify-demo   master ●  npx eslint .
 ~/Desktop/vuetify-demo   master ● 

nothing print

hm, that's strange - npm install && ./node_modules/.bin/eslint .?

 ~/Desktop/vuetify-demo   master ●   ./node_modules/.bin/eslint .
 ~/Desktop/vuetify-demo   master ● 

ok - that implies there's no linting errors. have you configured vscode to use the local eslint? (you can verify by npm uninstall -g eslint, since you shouldn't need a global one)

Closing pending a response.


Add support for generic callbacks in the Machine

The callbacks are called every time a transition happens and have the same call signature as normal callbacks
This patch address #13

@tyarkoni please let me know if want me to update README.md too

Looks good; thanks for the PR!


S-104590 Update ArgoCD Workflows with helm chart and revision

Please go the Preview tab and select the appropriate PR sub-template:
Feature

Workflows
Templates

This should point to the 24.1 branch. I will update PR and we can merge it after S-96970


swaygrab: make focused output default

This makes swaygrab use the currently focused output as source if no
other output is defined with the -o, --output <output> option.
Note this changes the way swaygrab is called:
Usage: swaygrab [options] [file]

  -h, --help             Show help message and quit.
  -c, --capture          Capture video.
  -o, --output <output>  Output source.
  -v, --version          Show the version number and quit.
  -s, --socket <socket>  Use the specified socket.
  -R, --rate <rate>      Specify framerate (default: 30)
  -r, --raw              Write raw rgba data to stdout.

If you don't like this change, please let me know.
I will update the man page when/if this is accepted.

Thanks!


change API from char* to int8_t*, implement standard BERT run_classifier.py

change API from char* to int8_t*, avoid misunderstanding between '0' and 0.

implement standard BERT run_classifier.py, add num_labels and output_bias.

The python API should also be modified in https://github.com/zhihu/cuBERT/pull/12

cc: @ericxsun

cc: @ericxsun
okay

LGTM


Can't get it working in Lambda (Cannot find module 'vite-plugin-ssr/dist/cjs/node/index.js')

Hey there ☺

I'm trying to deploy a Vite React app using vite-plugin-ssr to provide SSR but testing the Lambda via AWS Console results in Cannot find module 'vite-plugin-ssr/dist/cjs/node/index.js' so it seems it's not correctly bundling the right version or something?
I opened an issue at the plugin repo but was told it's more likely some bundling issue with Pulumi
I'm running
pulumi version => v3.10.3
node -v => v16.5.0

The full error from the AWS Lambda Console:
{
  "errorType": "Error",
  "errorMessage": "Cannot find module 'vite-plugin-ssr/dist/cjs/node/index.js'\nRequire stack:\n- /var/task/__index.js\n- /var/runtime/UserFunction.js\n- /var/runtime/index.js",
  "trace": [
    "Error: Cannot find module 'vite-plugin-ssr/dist/cjs/node/index.js'",
    "Require stack:",
    "- /var/task/__index.js",
    "- /var/runtime/UserFunction.js",
    "- /var/runtime/index.js",
    "    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:889:15)",
    "    at Function.Module._load (internal/modules/cjs/loader.js:745:27)",
    "    at Module.require (internal/modules/cjs/loader.js:961:19)",
    "    at require (internal/modules/cjs/helpers.js:92:18)",
    "    at /var/task/__index.js:80:15",
    "    at Object.__f2 [as createPageRender] (/var/task/__index.js:85:6)",
    "    at /var/task/__index.js:105:32",
    "    at Generator.next (<anonymous>)",
    "    at /var/task/__index.js:16:71",
    "    at new Promise (<anonymous>)"
  ]
}

Steps to reproduce

git clone https://github.com/CanRau/pulumi-bundle-issue
yarn
cd www
yarn && yarn build
cd ..
pulumi up to some test environment if possible

Expected:  Working Lambda
Actual:  Error as in title
I use www/server/lambda.ts as Lambda function handler index.ts#L3
Which as mentioned in the plugins docs imports import "../dist/server/importBuild";
Actually lambda.ts itself already imports vite-plugin-ssr.
Maybe I've got some tsconfig.json confusions?
Let me know if I can provide anything else 🙏

I just tried again with these versions (same as you, minus node where I'm behind):
"@pulumi/aws": "4.17.0"
"@pulumi/pulumi": "3.11.0"
pulumi CLI: v3.11.0
node: v14.16.1

I'm still able to pulumi up without issue 🤷♀  As for how I got the toLowerCase error, I just went to the lambda console in AWS and triggered a test event

Uh, the toLowerCase happens probably because I didn't provide a test event 😅
{
  "body": "",
  "resource": "/{proxy+}",
  "path": "/",
  "httpMethod": "GET",
  "isBase64Encoded": true,
  "queryStringParameters": {},
  "multiValueQueryStringParameters": {},
  "pathParameters": {
    "proxy": "/"
  },
  "stageVariables": {
    "baz": "qux"
  },
  "headers": {
    "Accept": "text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8",
    "Accept-Encoding": "gzip, deflate, sdch",
    "Accept-Language": "en-US,en;q=0.8",
    "Cache-Control": "max-age=0",
    "CloudFront-Forwarded-Proto": "https",
    "CloudFront-Is-Desktop-Viewer": "true",
    "CloudFront-Is-Mobile-Viewer": "false",
    "CloudFront-Is-SmartTV-Viewer": "false",
    "CloudFront-Is-Tablet-Viewer": "false",
    "CloudFront-Viewer-Country": "US",
    "Host": "1234567890.execute-api.us-east-1.amazonaws.com",
    "Upgrade-Insecure-Requests": "1",
    "User-Agent": "Custom User Agent String",
    "Via": "1.1 08f323deadbeefa7af34d5feb414ce27.cloudfront.net (CloudFront)",
    "X-Amz-Cf-Id": "cDehVQoZnx43VYQb9j2-nvCh-9z396Uhbp027Y2JvkCPNLmGJHqlaA==",
    "X-Forwarded-For": "<IP_ADDRESS>, <IP_ADDRESS>",
    "X-Forwarded-Port": "443",
    "X-Forwarded-Proto": "https"
  },
  "multiValueHeaders": {
    "Accept": [
      "text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8"
    ],
    "Accept-Encoding": [
      "gzip, deflate, sdch"
    ],
    "Accept-Language": [
      "en-US,en;q=0.8"
    ],
    "Cache-Control": [
      "max-age=0"
    ],
    "CloudFront-Forwarded-Proto": [
      "https"
    ],
    "CloudFront-Is-Desktop-Viewer": [
      "true"
    ],
    "CloudFront-Is-Mobile-Viewer": [
      "false"
    ],
    "CloudFront-Is-SmartTV-Viewer": [
      "false"
    ],
    "CloudFront-Is-Tablet-Viewer": [
      "false"
    ],
    "CloudFront-Viewer-Country": [
      "US"
    ],
    "Host": [
      "0123456789.execute-api.us-east-1.amazonaws.com"
    ],
    "Upgrade-Insecure-Requests": [
      "1"
    ],
    "User-Agent": [
      "Custom User Agent String"
    ],
    "Via": [
      "1.1 08f323deadbeefa7af34d5feb414ce27.cloudfront.net (CloudFront)"
    ],
    "X-Amz-Cf-Id": [
      "cDehVQoZnx43VYQb9j2-nvCh-9z396Uhbp027Y2JvkCPNLmGJHqlaA=="
    ],
    "X-Forwarded-For": [
      "<IP_ADDRESS>, <IP_ADDRESS>"
    ],
    "X-Forwarded-Port": [
      "443"
    ],
    "X-Forwarded-Proto": [
      "https"
    ]
  },
  "requestContext": {
    "accountId": "123456789012",
    "resourceId": "123456",
    "stage": "prod",
    "requestId": "c6af9ac6-7b61-11e6-9a41-93e8deadbeef",
    "requestTime": "09/Apr/2015:12:34:56 +0000",
    "requestTimeEpoch":<PHONE_NUMBER>000,
    "identity": {
      "cognitoIdentityPoolId": null,
      "accountId": null,
      "cognitoIdentityId": null,
      "caller": null,
      "accessKey": null,
      "sourceIp": "<IP_ADDRESS>",
      "cognitoAuthenticationType": null,
      "cognitoAuthenticationProvider": null,
      "userArn": null,
      "userAgent": "Custom User Agent String",
      "user": null
    },
    "path": "/prod/path/to/resource",
    "resourcePath": "/{proxy+}",
    "httpMethod": "POST",
    "apiId": "1234567890",
    "protocol": "HTTP/1.1"
  }
}

Yeah because it's supposed to be a APIGateway event and I don't yet verify it and just access toLowerCase on event.httpMethod 😅
And maybe because of this you don't get the "correct" error as it fails earlier


fix: fixed the radar names. there is no base link in the radars

as per the description

@yukkysaito
Friendly ping. We need this for gen2 experiments

@yukkysaito

Sorry for late.
I'll merge this PR🙏


chore(deps): update dependency colors to v1.3.3

This PR contains the following updates:

Package
Type
Update
Change
References

colors
devDependencies
minor
1.1.2 -> 1.3.3
source

Release Notes

Marak/colors.js
v1.3.3
Compare Source
v1.3.2
Compare Source
v1.3.1
Compare Source
v1.3.0
Compare Source
v1.2.5
Compare Source
v1.2.4
Compare Source
v1.2.3
Compare Source
v1.2.2
Compare Source
v1.2.1
Compare Source
v1.2.0
Compare Source

Renovate configuration
:date: Schedule: At any time (no schedule defined).
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR is stale, or if you modify the PR title to begin with "rebase!".
:no_bell: Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

colors is only used in validate-build script… YOLO :D

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


Add error handling for missing environment variables

Changes Made

Added checks for missing SUPABASE_URL and SUPABASE_ANON_KEY environment variables in middleware.ts.
Updated logging to include error messages when environment variables are not found.
Corrected Redis configuration to resolve production build errors.

Related Issue
None
Description
Implemented error handling for missing Supabase environment variables (SUPABASE_URL and SUPABASE_ANON_KEY) in middleware.ts. Also addressed Redis configuration issues that were causing errors during the production build process.
Type of PR

[ ] Bug fix
[x] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)
None
Checklist:

[x] I have performed a self-review of my code
[x] I have read and followed the Contribution Guidelines.
[x] I have tested the changes thoroughly before submitting this pull request.
[ ] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[x] I have commented my code, particularly in hard-to-understand areas.

Additional context:
Included proper error handling for missing Supabase environment variables and corrected Redis configuration to ensure smooth production builds.

Thank you for submitting your pull request! 🙌 We'll review it as soon as possible. In the meantime, please ensure that your changes align with our CONTRIBUTING.md. If there are any specific instructions or feedback regarding your PR, we'll provide them here. Thanks again for your contribution! 😊

@dhairyathedev Please have a look here.
@iamabhishek2828 Remove console logs, and reset the NEXT_PUBLIC_URL as it was. You can use it as process.env.NEXT_PUBLIC_URL || localhost

@iamabhishek2828 Resolve suggestions and merge conflicts


Bundler encourages upgrading to pre-release versions

Currently during any bundle invocation, bundler encourages its users to upgrade to pre-release software:
❯ bundle info nokogiri
The latest bundler is 1.16.0.pre.3, but you are currently running 1.15.4.
To update, run `gem install bundler --pre`

I really love bundler and I think it's far superior to a lot other package and dependency mangers but I'm concerned that it may give beginners the wrong idea to upgrade software that is considered unstable. What do you think?

This has been disabled by default in 1.16.0.pre.3. I’m on my phone so I can’t link, but there are several other issues about this.

See #6031

Thank you !


Uncaught ReferenceError: process is not defined

Hi,
I'm trying to use https://xstate.js.org/docs/ and I'm experiencing an issue:
environment.js:3 Uncaught ReferenceError: process is not defined
    at environment.js:3
    at createCommonjsModule (index.js:9)
    at constants.js:6
    at index.js:6
(anonymous) @ environment.js:3
createCommonjsModule @ index.js:9
(anonymous) @ constants.js:6
(anonymous) @ index.js:6

Seems this is connected with Rollup.
Here some similar issues:

https://github.com/davidkpiano/xstate/issues/706
https://github.com/davidkpiano/xstate/issues/443

Can You fix this in the CLI or Can I exdends the configuration of Rollup?

This should fix the problem, I've tested in the global package (install the dependency):
const babel = require('rollup-plugin-babel')
const resolve = require('rollup-plugin-node-resolve')
const commonjs = require('rollup-plugin-commonjs')
const babelPresentEnv = require('@babel/preset-env')
const babelPluginTransFormSpread = require('@babel/plugin-transform-spread')
const babelPluginTransFormParameters = require('@babel/plugin-transform-parameters')
import replace from '@rollup/plugin-replace'

module.exports = {
  plugins: [
    resolve({
      mainFields: ['main', 'browser']
    }),
    commonjs(),
    babel({
      presets: [
        [
          babelPresentEnv,
          {
            targets: {
              chrome: '44',
            },
            spec: true,
            debug: false,
            useBuiltIns: 'usage',
            corejs: '^2.6.11',
          },
        ],
      ],
      plugins: [babelPluginTransFormSpread, babelPluginTransFormParameters],
    }),
    replace({
      'process.env.NODE_ENV': JSON.stringify('production')
    })
  ],
  output: {
    format: 'iife',
    sourcemap: true,
  },
}

Can I submit the code?
$ git push origin 24
remote: Permission to WebPlatformForEmbedded/Lightning-CLI.git denied to MattiaPontonioKineton.
fatal: unable to access 'https://github.com/WebPlatformForEmbedded/Lightning-CLI.git/': The requested URL returned error: 403

Hello @michielvandergeest,
any updates on this issue?
Updating the CLI breaking my developer experience today in my project with wpe-lightning + xstate.
I think that should break even other use of other libraries in the wpe-lightning modules.
Best regards :)
Mattia

This should be fixed in release 1.7.0


Simple Gallery Pro

Submission for Simple Gallery Pro, which belongs to the open source Simple Mobile Tools suite https://www.simplemobiletools.com/gallery containing 13 Android apps

closing this for https://github.com/trek/beautiful-open/issues/549


TOMCAT Container Logs not pushing to Splunk

What happened:
We have manually deployed the manifest file and not using the HELM option. Tomcat Container logs are not pushing to splunk but other containers logs are pushing to splunk. Other container logs path is '/var/logs' and path for tomcat logs is '/usr/local/tomcat/logs/erefill_*.log'.
Specifications of Tomcat Logs :

Logs Format - log4j
Time Format - yyyy-MM-dd HH:mm:ss,SSS
Regex - ^(\d{4}+-\d+-\d+ \d+:\d+:\d+,\d+)|([\d+])|(\S+:\d+)|-|(\S+)|

Tomcat Conf File:
   `	tomcat.conf: |-
<source>
  @id tomcat.log
  @type tail
  @label @CONCAT
  tag tail.containers.var.log.containers.toolbox*
  path /usr/local/tomcat/logs/erefill_*.log
  pos_file /var/log/tomcat.log.pos
  path_key source
  read_from_head true
  refresh_interval 60
  <parse>
	@type json
	time_format %Y-%m-%dT%H:%M:%S.%NZ
	time_key time
	time_type string
	localtime false
  </parse>
</source>`

Filter for Tomcat Logs which is added in output.conf file :
   `<filter tail.containers.var.log.containers.toolbox*toolbox*.log>
    @type concat
    key log
    timeout_label @SPLUNK
    stream_identity_key stream
    multiline_start_regexp /^(\d{4}+\-\d+\-\d+ \d+:\d+:\d+,\d+)|(\[\d+\])|(\S+:\d+)|-|(\S+)|
    multiline_end_regexp /\\n$/
    separator ""
    flush_interval 5s
  </filter>`

Question/Doubts :

Which parsing plugin should be used for log4j logs format..? And How..?
Are above stanza's are correct, can you pls verify once.

Kindly suggest and help to resolve this issue.

I have already mounted the '/usr/local/tomcat/logs/*' directory in daemonset.yaml file. Take a look :
`
apiVersion: apps/v1
kind: DaemonSet
metadata:
name: splunk-kubernetes-logging
namespace: fluentd-amax
labels:
app: splunk-kubernetes-logging
engine: fluentd
version: 1.4.6
spec:
updateStrategy:
type: RollingUpdate
selector:
matchLabels:
app: splunk-kubernetes-logging
template:
metadata:
labels:
app: splunk-kubernetes-logging
version: 1.4.6
annotations:
prometheus.io/scrape: 'true'
prometheus.io/port: '24231'
spec:
serviceAccountName: splunk-kubernetes-logging
nodeSelector:
beta.kubernetes.io/os: linux
tolerations:
- effect: NoSchedule
key: node-role.kubernetes.io/master
containers:
- name: splunk-fluentd-k8s-logs
image: docker.io/splunk/fluentd-hec:1.2.4
imagePullPolicy: IfNotPresent
securityContext:
runAsUser: 0
privileged: false
env:
- name: K8S_NODE_NAME
valueFrom:
fieldRef:
fieldPath: spec.nodeName
- name: MY_NAMESPACE
valueFrom:
fieldRef:
fieldPath: metadata.namespace
- name: MY_POD_NAME
valueFrom:
fieldRef:
fieldPath: metadata.name
- name: SPLUNK_HEC_TOKEN
valueFrom:
secretKeyRef:
name: splunk-kubernetes-logging
key: splunk_hec_token
- name: SSL_CERT_FILE
value: "/fluentd/etc/splunk/hec_ca_file"
resources:
requests:
cpu: 100m
memory: 200Mi
volumeMounts:
- name: varlog
mountPath: "/var/log"
- name: varapp
mountPath: "/usr/local/tomcat/logs"
- name: varlogdest
mountPath: "/var/vcap/store/docker/docker/containers"
readOnly: true
- name: journallogpath
mountPath: "/run/log/journal"
readOnly: true
- name: conf-configmap
mountPath: "/fluentd/etc"
- name: secrets
mountPath: "/fluentd/etc/splunk"
readOnly: true
terminationGracePeriodSeconds: 30
volumes:
- name: varlog
hostPath:
path: "/var/log"
- name: varapp
hostPath:
path: "/usr/local/tomcat/logs"
- name: varlogdest
hostPath:
path: "/var/vcap/store/docker/docker/containers"
- name: journallogpath
hostPath:
path: "/run/log/journal"
- name: conf-configmap
configMap:
name: splunk-kubernetes-logging
- name: secrets
secret:
secretName: splunk-kubernetes-logging
`
Can you pls review the above file once...
Now I will make the other 2 suggested changes :

tag tail.tomcat.*
<filter tail.tomcat.usr.local.tomcat.logs.erefill_*.log>

Will let you the feedback on these changes. Thank you..!!

but do you also have /usr/local/tomcat/ path mounted to your tomcat pod?
do you get any errors regarding tomcat log files on fluentd pod?

Hey @jaypalpatil , were you able to get tocat logs in splunk? Please let us know.

Closing the issue for now. Feel free to reopen or create a new one if needed.


Why currentColor in generated css

Bug, feature request, or proposal:
Maybe a newbie question: Is it normal to have in the generated css : color: currentColor; ?
.mat-input-element {
    font: inherit;
    background: 0 0;
    color: currentColor;
    border: none;
    outline: 0;
    padding: 0;
    width: 100%;
    vertical-align: bottom;
}

I can see that in the source code of Material there are several places with color: currentColor;
E.g.
.mat-button, .mat-raised-button, .mat-icon-button {
  color: currentColor;
  .mat-button-wrapper > * {
    vertical-align: middle;
  }
}

What is the expected behavior?
To have the currentColor replaced by the color code (hexa or rgb/a)?
What is the current behavior?
The following scss from Material
.mat-button, .mat-raised-button, .mat-icon-button {
  color: currentColor;
  .mat-button-wrapper > * {
    vertical-align: middle;
  }
}

generates
.mat-input-element {
    font: inherit;
    background: 0 0;
    color: currentColor;
    border: none;
    outline: 0;
    padding: 0;
    width: 100%;
    vertical-align: bottom;
}

Why currentColor is not replaced by a value?
What are the steps to reproduce?
What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Material, OS, browsers are affected?
Angular 4.0.1, Angular CLI 1.0.0, Material 2.0.0-beta.3, node 7.5.0, npm 4.2.0
Is there anything else we should know?

Ok, after searching :

icon.md
https://developer.mozilla.org/en-US/docs/Web/CSS/color_value#currentColor_keyword


Add i18n support

Currently English is the only supported language for Fancy Mumble. We want to be able to support more than one language.
Here are some possible frameworks / libraries for this:
https://github.com/projectfluent/fluent-rs
https://www.i18next.com/

implemented in 0.2.2


linter configuration files at the user level are not being used

Configuration options for linters in the user's home directory are not used by the internal linters.
The only possible method is to use the arguments function to specify a file, but then this overrides the ability to have intelligent levels of config files.
This issue is clearly with vscode/vscode-python, as the functionality works as expected when run through the command line
Environment data

VS Code version: 1.36
Extension version (available under the Extensions sidebar): 2019.6.22090
OS and version: Windows 10 home 1903
Python version (& distribution if applicable, e.g. Anaconda): 3.7.3
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A
Relevant/affected Python packages and their versions: All Linters
Jedi or Language Server? (i.e. what is "python.jediEnabled" set to; more info #3977): Jedi

Expected behaviour
Configuration files for linters that have been placed in the user home folder (C:\Users_username_.pylintrc for example) are read by the linters and used to configure them.
Actual behaviour
Linters only read configuration files found in the project folder.
Steps to reproduce:

Activate pylint linter
Generate pylintrc file and place in user home directory
Modify settings for pylintrc file that will be readily visible on python program
See that linter running inside vs code does not follow

Logs
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
##########Linting Output - pylint##########

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help; turn on source maps to make any tracebacks be useful by running Enable source map support for extension debugging)
[Extension Host] Info Python Extension: 2019-07-07 00:03:45: Cached data exists getEnvironmentVariables, d:\Documents\test\test.py
4console.ts:134 [Extension Host] Info Python Extension: 2019-07-07 00:03:47: Cached data exists getEnvironmentVariables, d:\Documents\test\test.py

After reloading the program it suddenly is worked. I don't know why.

Thanks, closing as the issue has been resolved.


Barometer fix may need both FIRST and AFTER[CNAR]

https://github.com/harveyt/Wacapella/blob/ca5b554391e3d1ce664a8b1aa74726179efef375/GameData/Wacapella/CNAR-ForumFixes.cfg#L45

Fixed by da0469f9c190091bb28b9e4936e09e5dcc83f4d5

Fixed in release 1.0.4


Add 'netbase' package to base image.

The netbase package provides /etc/networks, /etc/protocols, /etc/rpc, /etc/services.
Before this change, the differences in packages between Dockerhub debian:8 and GCP debian8 were:
+ii  ca-certificates          20141019+deb8u3          all          Common CA certificates
+ii  libssl1.0.0:amd64        1.0.1t-1+deb8u6          amd64        Secure Sockets Layer toolkit - shared libraries
+ii  openssl                  1.0.1t-1+deb8u6          amd64        Secure Sockets Layer toolkit - cryptographic utility
-ii  inetutils-ping           2:<IP_ADDRESS>.3a460-3       amd64        ICMP echo tool
-ii  iproute2                 3.16.0-2                 amd64        networking and traffic control tools
-ii  netbase                  5.3                      all          Basic TCP/IP networking system
-ii  passwd                   1:4.2-3+deb8u3           amd64        change and administer password and group data
-ii  perl-base                5.20.2-3+deb8u6          amd64        minimal Perl system
After this change, 'netbase' is installed in both.

Please review @dlorenc @sharifelgamal
CC @jonparrott @liyanhui1228

Kokoro config stale? cp: cannot stat ‘/tmpfs/src/gfile/google-cloud-sdk-153.0.0-linux-x86_64.tar.gz’: No such file or directory

Yep, I'll fix the config tomorrow. Otherwise LGTM and should be ready to merge once the tests pass.

Thanks Doug!


[BACKLOG-778][BACKLOG-35780][BACKLOG-35781] - Remove twitter ktrs from the list of all ktrs to be run by run all job

:white_check_mark: Build finished in 3m 4s
Build command:
mvn clean verify -B -e -Daudit -amd -pl assemblies/samples

:exclamation: No tests found!
:information_source:  This is an automatic message


Follow up on Capacity -> ClusterQueue

Signed-off-by: Carlos Eduardo Arango Gutierrez<EMAIL_ADDRESS>Followup on #95
What type of PR is this?
/kind cleanup

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
FollowUp on #95

/assign @ahg-g

some of this is already covered in https://github.com/kubernetes-sigs/kueue/pull/90, can we try to merge that first so we avoid conflicts?

some of this is already covered in #90, can we try to merge that first so we avoid conflicts?

/hold

rebased , ready for review
/hold cancel

obliterate capacity concept for the ClusterQueue concept

/lgtm

/lgtm

Sorry Aldo, but PR needed rebase. can you hit it again, thanks

@ahg-g can we merge this one before more rebases 😅

/approve
yeah, I thought Aldo approved

Sorry :upside_down_face:


autoapi class.rst doesn't render multiple return types

🔍 Before submitting the issue

[X] I have searched among the existing issues
[X] I am using a Python virtual environment

🐞 Description of the bug
    @property
    def geometry(self) -> StlFile | BuildFile:
        """Part geometry."""
        return self._geometry

renders as

📝 Steps to reproduce
Write a class property or method that returns multiple possible types and annotate it using 3.10+ annotation style. Generate documentation using autoapi and  ansys-sphinx-theme. Only the last return type is shown in the generated docs.
💻 Which operating system are you using?
Windows
📀 Which ANSYS version are you using?
24.1
🐍 Which Python version are you using?
3.9
📦 Installed packages
ansys-api-additive==1.4.1
ansys-api-platform-instancemanagement==1.0.0
ansys-platform-instancemanagement==1.1.2
ansys-templates==1.7.0
arrow==1.3.0
binaryornot==0.4.4
bleach==6.1.0
bokeh==3.3.0
cachetools==5.3.2
certifi==2023.7.22
cfgv==3.4.0
chardet==5.2.0
charset-normalizer==3.3.2
click==8.1.7
colorama==0.4.6
contourpy==1.1.1
cookiecutter==2.2.3
coverage==7.3.2
dill==0.3.7
distlib==0.3.7
exceptiongroup==1.1.3
filelock==3.13.1
google-api-core==2.12.0
google-api-python-client==2.106.0
google-auth==2.23.4
google-auth-httplib2==0.1.1
googleapis-common-protos==1.61.0
grpcio==1.59.2
grpcio-health-checking==1.48.2
httplib2==0.22.0
identify==2.5.31
idna==3.4
importlib-metadata==6.8.0
iniconfig==2.0.0
isort==5.12.0
Jinja2==3.1.2
linkify-it-py==2.0.2
Markdown==3.5.1
markdown-it-py==3.0.0
MarkupSafe==2.1.3
mdit-py-plugins==0.4.0
mdurl==0.1.2
nodeenv==1.8.0
numpy==1.26.1
packaging==23.2
pandas==2.1.2
panel==1.3.1
param==2.0.0
Pillow==10.1.0
platformdirs==3.11.0
plotly==5.18.0
pluggy==1.3.0
pre-commit==3.5.0
protobuf==3.20.3
pyasn1==0.5.0
pyasn1-modules==0.3.0
pyparsing==3.1.1
pyproject-api==1.6.1
pytest==7.4.3
pytest-cov==4.1.0
python-dateutil==2.8.2
python-slugify==8.0.1
pytz==2023.3.post1
pyviz_comms==3.0.0
PyYAML==6.0.1
requests==2.31.0
rsa==4.9
six==1.16.0
tenacity==8.2.3
text-unidecode==1.3
tomli==2.0.1
tornado==6.3.3
tox==4.11.3
tqdm==4.66.1
types-python-dateutil==<IP_ADDRESS>
typing_extensions==4.8.0
tzdata==2023.3
uc-micro-py==1.0.2
uritemplate==4.1.1
urllib3==2.0.7
virtualenv==20.24.6
webencodings==0.5.1
xyzservices==2023.10.1
zipp==3.17.0

This is more of a sphinx-autoapi issue if I am not mistaken. Assigning to @jorgepiloto

Thanks for the ping. Roberto is right, we need to check if this comes from our class.rst template or it originates in the internals of sphinx-autoapi.

I thought the | symbol for representing a union was only supported in Python 3.10+. Could you try using:
from typing import Union

  @property
    def geometry(self) -> Union[StlFile, BuildFile]:
        """Part geometry."""
        return self._geometry

This also ensures compatibility with 3.9.

@jorgepiloto The source file contains from __future__ import annotations. I'd prefer to keep the 3.10+ type specifications if possible.


build: add a CMake based build system

This will allow using Swift System in the toolchain stack, allowing us
to bootstrap a toolchain.

@swift-ci please test

@swift-ci please test


Register Severity enum for reflection to support native applications that use gcp logging

I'm using version 2.11.0 of the quarkus-google-cloud-logging quarkiverse extension so that I can log to GCP.
Logging works as expected for non-native Quarkus applications, but in native all logs appear with DEFAULT severity in GCP console rather than INFO, DBUG etc.
This is because the LoggingHandler#transform method uses Gson to serialize a value of the com.google.cloud.logging.Severity enum, and in native builds this always serializes to null unless that class is registered for reflection.
Rather than rely on applications to do this, the quarkus google cloud logging extension should ensure that the enum is registered with ReflectiveClassBuildItem in the processor (presumably as a @BuildStep annotated method of the LoggingBuildSteps class).

Thanks for the issue, this is easy to fix, as you have it sorted out maybe you want to propose a PR?
Otherwise I'll take care of it.

Hi @loicmathieu - I'm happy to have a go at this one, given that it looks like just a few additional lines.

Great! Thank you!


Preliminary Ishiiruka port needs gtk2 and wxwidgets dependencies

I modified the dolphin script to work with ishiiruka only way for me to find the WX widgets libraries and gtk2 libraries is to install dolphin emu and then uninstall I don't know if you want to use this script in your experimental ports section should require minimal modification to work with the dependencies

dolphin.log

This repo is mainly aimed at stuff that is functional for the Raspberry Pi, so I don't feel that it's approrpriate here as I will have no way to maintain it later if things break.


Explicit styling for buttons

With the exception of the "Run" button, the styling of button controls are not consistent when page is zoomed. We should probably use explicit styling to keep the control appearance consistent.

Just checking but for this issue do we just want to address the "Reset Code" button or should we also style the dropdowns?

Both (explicit styling for all controls). The Run button is OK since it already has explicit styling.

Fixed in #337. Thanks @dchen97!


Adds Android FHIR SDK for data capture

Adds Android FHIR SDK for data capture
:gear: Release Notes
This PR adds the Android FHIR SDK's data capture module which provides functionality for rendering FHIR Questionnaires and FHIR data types for HealthConnectOnFHIR.
:pencil: Code of Conduct & Contributing Guidelines
By submitting creating this pull request, you agree to follow our Code of Conduct and Contributing Guidelines:

[X] I agree to follow the Code of Conduct and Contributing Guidelines.

Thank you for the additions here @vishnuravi & @Basler182!
As far as I can interpret the log we are still failing with the same coverage report failure due to the large file transformation.
It might make sense to still merge this into messages and then follow the approach that @eldcn proposed to at least temporarily disable coverage reports for the main app target and then investigate this in a smaller and separate PR?

Not quite sure why the diff is so large; shouldn't this just be a small addition to feature/messages?

I noticed that this branch has been created from main in later state compared to feature/save-measurements. I just pushed the needed changes in #53 directly at this commit, we can observe next if the jacocco issue get's resolved (then we can close this PR in favor of #53). If not, we can temporarily disable coverage report and address in a smaller follow up. CC: @PSchmiedmayer @vishnuravi @Basler182

Thank you @eldcn for the context!


NYC Taxi example

This borrows some feature engineering ideas from the competition and builds a notebook to demonstrate Kaskada's feature engineering.

Should we close this? Dust it off and merge it? Something else?


Hello, there are 2 problems in using DPF.JS in the project:

1.The PDF file viewed by using PDF.JS is not clear enough when printed on paper.
2.When printing on paper, horizontal and vertical cannot adapt themselves.
May I know what can be done?

How about sharing your PDF, the printed PDF and explaining what you mean? And "Hello, there are 2 problems in using DPF.JS in the project" is not really a useful title. If everybody would do that, the bug list would look like this:
10985 I got this error and please help
10986 Something doesn't work right in the Xfdh.js projekt
10987 Please help me I don't know what is happening
10988 Is this real? The paper looks weird
10999 PDF problem, pls guide me
10100 image is wrong in that browser on my computer
10111 My computer mad at me
10112 I'm lost here why is this so
10113 Screen is wrong

I agree. Unless more information is provided, I'm closing this as a duplicate of many other issues in https://github.com/mozilla/pdf.js/issues?q=is%3Aopen+is%3Aissue+label%3A4-printing.


Mirror the following repos to flutter.googlesource

The following repositories are used for building mac tools:

~cocoapods~
homebrew-flutter
ideviceinstaller
ios-deploy
libimobiledevice
libplist
libtasn1
~libtasn1-flutter~
libusb
libusbmuxd
libzip
openssl

@christopherfujino do we need to keep the ones with -flutter?

i think one of the libtasn1 repos is redundant. as for homebrew-flutter, we can deprecate that once we stop using homebrew to compile libimobiledevice.

@godofredoc is this a ticket queue bug?

cocoapods does not need a third party fork

https://flutter.googlesource.com/third_party/ideviceinstaller is ready with 1h updates.

https://flutter.googlesource.com/third_party/libimobiledevice is ready with 1h updates.

https://flutter.googlesource.com/third_party/ios-deploy is ready with 1h updates.

https://flutter.googlesource.com/third_party/libzip/ is ready with 1h updates.

https://flutter.googlesource.com/third_party/openssl/ is ready with 1h updates.

We are missing homebrew-flutter

https://flutter.googlesource.com/third_party/libimobiledevice is ready with 1h updates.

Seems something is misconfigured. I am not able to checkout. For example:
https://flutter.googlesource.com/third_party/libimobiledevice/+/refs/heads/master
git clone https://flutter.googlesource.com/third_party/libimobiledevice
Cloning into 'libimobiledevice'...
remote: Total 9777 (delta 7591), reused 9777 (delta 7591)
Receiving objects: 100% (9777/9777), 2.71 MiB | 677.00 KiB/s, done.
Resolving deltas: 100% (7591/7591), done.
warning: remote HEAD refers to nonexistent ref, unable to checkout.

Also the repo is not being updated (latest change is on 05/10/2022)

@keyonghan I don't think these are setup to be mirrored? Atleast not through copybara.

There was a typo on the mirror link, it was updated and now things are working properly.

Reopening this issue as other repos need a gob config fix as well (now only libimobiledevice works).
I tried updating the default branch from main to master, but hit permission issues:
gob-ctl repos update-ref flutter/third_party/libplist --ref=HEAD --old-ref-target=refs/heads/main --new-ref-target=refs/heads/master
E0721 10:35:43.904463  135768 errorlogger.go:93] gob-ctl GGoB::PERMISSION_DENIED_BY_REPOSITORY_ACL (canonical: PERMISSION_DENIED, elapsed: 0.1998s, deadline: none, caller: unknown, backend: unknown, traced: false, trace_id: 0x0000000000000000)
[type.googleapis.com/google.rpc.RequestInfo]
request_id:  "60f0d4f1dff042b98dcab520738e90d7"

Here are the list that needs a fix:

[ ] https://flutter.googlesource.com/third_party/ideviceinstaller
[ ] https://flutter.googlesource.com/third_party/ios-deploy
[ ] https://flutter.googlesource.com/third_party/libplist
[ ] https://flutter.googlesource.com/third_party/libtasn1
[ ] https://flutter.googlesource.com/third_party/libusbmuxd
[ ] https://flutter.googlesource.com/third_party/libusb/
[ ] https://flutter.googlesource.com/third_party/libzip/
[ ] https://flutter.googlesource.com/third_party/openssl/

All work now. Thanks!


Implied matrix sizes from inputs inconsistent

B = A
where
A ∈ℝ^(n × n)

compiles and the output will be n × n (I❤LA correct determines the size of B implied by assignment from A), however
A_ij = { 1 if i+1=j

where
A ∈ℝ^(n × n)

does not compile and complains
Error on line 1 at column 8. Sparse matrix: dim n is not defined.
A_ij = { 1 if i+1=j
       ^

This error message feels ironic. Clearly n is known to be a dimension, but it's not defined. The current compiler requires extra (redundant input arguments):
A_ij = { 1 if i+1=j

where
A ∈ℝ^(n × n)
n ∈ ℤ

This means the prototype of the compiled function in our targets will have a c-style api where you need to give the array and then also the length as a separate variable.

Sparse matrix is a special case and it may be confusing here.
For the dense parameter A, we know the size is n while n is not a parameter.
For sparse A, we require the dimension to be defined and n ∈ ℤ illustrates that it's a parameter.
I don't know which way is better. If we don't require n ∈ ℤ in the where block and still use it as a parameter, that may also be confusing.

Ah, I think I was misunderstand my own example, A is an output but awkwardly appears in the where block (where we normal only have inputs). Maybe we should revisit this confusion (I recall we once discussed whether all inputs go in the given...)

Meanwhile, this ought to compile:
given
x ∈ ℝ^n

A_ij = { 1 if i+1=j
E = xᵀ A x

but instead gets confused about the size of A
A_ij = { 1 if i+1=j
       ^

In your last example, the dimension of A is still not known. n may come form the size of x, but you didn't declare A ∈ ℝ^(n×n).

I'm confused what's not known? The size of A is fully determined.

If we're talking about this:
given
x ∈ ℝ^n

A_ij = { 1 if i+1=j
E = xᵀ A x

I don't see any statements about A's dimensions. You could argue that we should figure it out based on the xᵀ A x, but that's adds a huge amount of complexity in the general case.

yes, that's what I'm argueing

I do think we should make this change for identity matrices, though.


Not able to run on raspberry pi

I installed ATK on a raspberry pi mainly to use Organizr but I it is not possible to open the program as it aperantly cannot open the URL.

Hi,
Thanks for logging an issue and sorry i've not got back to you sooner.
I'll look into this as it does appear on first glance its not working correctly.

This should now be resolved. Can you give it another try and report back?
Thanks

Closing due to inactivity and the fact I think this is now working correctly!
If anyone is still having trouble please create a new issue and fill out the Issue template.
Thanks
Tom


Removed the invalid URL

Remove redundant URL in "For example" section.

I signed it!

Closing this PR as this not against master, please open a new PR against master
CC @mihaimaruseac


Correctly return nil in build_tag_tagging_path() routine

build_tag_tagging_path() was introduced in https://github.com/ManageIQ/manageiq/pull/16401 by splitting part of assign_to_tags() into its own routine.
The original routine would skip creation of a tag string in case the Classification object doesn't
exist. To retain the same semantics, build_tag_tagging_path() needs to return nil here, otherwise
an exception would occur few moments later, when creating that
"#{klass.underscore}/tag#{obj.ns}/#{obj.parent.name}/#{obj.name}"

tag string.

@gtanzillo PTAL

@gtanzillo : please, add appropriate tags to both PRs. Thx!


optionally provide more versatile tile-map functionality

I see in https://github.com/ethereumdegen/bevy_mesh_terrain/blob/85eccf1767b75af17abb8f2c4fd50ce6def526a3/assets/shaders/terrain.wgsl#L4 the link to bevy_terrain's advanced shader, which uses a function to find the individual tile texture. The RGBA hack this plugin uses currently is very clever, but it'd be nice to have some more versatile options:

N-bit grayscale image indicating tile number in a larger atlas
N-bit RGBA but use R and B for tile number and G and A for alpha respectively
Multiple ordered layers, with alpha channel the tiles in the atlas in "higher" layers (so the lower ones show through)
For any of the above, plus the current RGBA blend approach, a seeded randomization (to pick, say, one of 16 variant grass tiles).
automatic selection of edge/corner transition tiles
load tiled-format maps (as bevy_tiled can in 2D (example: https://github.com/StarArawn/bevy_ecs_tilemap/blob/main/examples/tiled.rs)

What do you think?

If you're interested, this looks like something I could experiment with....

I experimented with this and figured out how to support 255 textures ! check it out and let me know what you think .

Cool — I've been busy with other things but will look when I get a chance.


Add WinXL spec to Jenkins pipelines

OpenJ9 only
JDK8,11,12,HEAD

Fixes #1099
Signed-off-by: Adam Brousseau<EMAIL_ADDRESS>

First draft at adding a spec to the builds. I'm not sure what I may have missed.

has a one-off build been tested

I have not done anything on the Jenkins/Build side. I don't have access there :)


[BUG] ebpf不支持4.14.105

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

DeepFlow Component
Agent
What you expected to happen
ebpf采集可以支持4.14内核tlinux2.2
How to reproduce
os使用tlinux2.2
DeepFlow version
deepflow-agent -v
9830-284d3dbbf93c7cb028232d3e9cd20bc1181d449d
Name: deepflow-agent community edition
Branch: v6.4
CommitId: 284d3dbbf93c7cb028232d3e9cd20bc1181d449d
RevCount: 9830
Compiler: rustc 1.75.0 (82e1608df 2023-12-21)
CompileTime: 2024-04-30 05:03:06
DeepFlow agent list
No response
Kubernetes CNI
No response
Operation-System/Kernel version
awk -F '=' '/PRETTY_NAME/ { print $2 }' /etc/os-release
"Tencent tlinux 2.2 (Final)"
uname -r
4.14.105-1-tlinux3-0023.1
Anything else
deepflow-agent 日志
[2024-05-06 23:05:33.522024 +08:00] INFO [src/ebpf_dispatcher/ebpf_dispatcher.rs:657] ebpf collector init...
[2024-05-06 23:05:33.522150 +08:00] INFO [src/ebpf_dispatcher/ebpf_dispatcher.rs:405] ebpf golang uprobe proc regexp is empty, skip set
[2024-05-06 23:05:33.522231 +08:00] INFO [src/ebpf_dispatcher/ebpf_dispatcher.rs:421] ebpf openssl uprobe proc regexp is empty, skip set
[2024-05-06 23:05:33.522320 +08:00] INFO [src/ebpf_dispatcher/ebpf_dispatcher.rs:444] ebpf golang symbol proc regexp is empty, skip set
[2024-05-06 23:05:33.522394 +08:00] INFO [src/ebpf_dispatcher/ebpf_dispatcher.rs:449] l7 protocol Custom parse enabled
[2024-05-06 23:05:33.522485 +08:00] INFO [src/ebpf_dispatcher/ebpf_dispatcher.rs:449] l7 protocol Http1 parse enabled
[2024-05-06 23:05:33.522563 +08:00] INFO [src/ebpf_dispatcher/ebpf_dispatcher.rs:449] l7 protocol Http2 parse enabled
[2024-05-06 23:05:33.522647 +08:00] INFO [src/ebpf_dispatcher/ebpf_dispatcher.rs:449] l7 protocol DNS parse enabled
[2024-05-06 23:05:33.522718 +08:00] INFO [src/ebpf_dispatcher/ebpf_dispatcher.rs:449] l7 protocol SofaRPC parse enabled
[2024-05-06 23:05:33.522800 +08:00] INFO [src/ebpf_dispatcher/ebpf_dispatcher.rs:449] l7 protocol MySQL parse enabled
[2024-05-06 23:05:33.522870 +08:00] INFO [src/ebpf_dispatcher/ebpf_dispatcher.rs:449] l7 protocol Kafka parse enabled
[2024-05-06 23:05:33.522959 +08:00] INFO [src/ebpf_dispatcher/ebpf_dispatcher.rs:449] l7 protocol Redis parse enabled
[2024-05-06 23:05:33.523027 +08:00] INFO [src/ebpf_dispatcher/ebpf_dispatcher.rs:449] l7 protocol MongoDB parse enabled
[2024-05-06 23:05:33.523105 +08:00] INFO [src/ebpf_dispatcher/ebpf_dispatcher.rs:449] l7 protocol PostgreSQL parse enabled
[2024-05-06 23:05:33.523183 +08:00] INFO [src/ebpf_dispatcher/ebpf_dispatcher.rs:449] l7 protocol Dubbo parse enabled
[2024-05-06 23:05:33.523263 +08:00] INFO [src/ebpf_dispatcher/ebpf_dispatcher.rs:449] l7 protocol FastCGI parse enabled
[2024-05-06 23:05:33.523349 +08:00] INFO [src/ebpf_dispatcher/ebpf_dispatcher.rs:449] l7 protocol Oracle parse enabled
[2024-05-06 23:05:33.523449 +08:00] INFO [src/ebpf_dispatcher/ebpf_dispatcher.rs:449] l7 protocol MQTT parse enabled
[2024-05-06 23:05:33.523529 +08:00] INFO [src/ebpf_dispatcher/ebpf_dispatcher.rs:449] l7 protocol TLS parse enabled
[2024-05-06 23:05:33.523672 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO Currently "/proc/sys/net/core/bpf_jit_enable" value is 1, not need set.
[2024-05-06 23:05:33.523792 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO log2_default_hugepage_sz 21
[2024-05-06 23:05:33.523908 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO linux version : 4.14.105-1-tlinux3-0023.1 (version code : 265833)
[2024-05-06 23:05:33.523989 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO RLIMIT_NOFILE cur:1048576, rlim_max:1048576
[2024-05-06 23:05:33.524117 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO sys_boot_time_ns :<PHONE_NUMBER>605591628
[2024-05-06 23:05:33.524294 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO [deepflow-ebpfctl] sockopt register succeed, type get: 404 - 404 set: 400 - 403
[2024-05-06 23:05:33.524452 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO register_period_event_op 'kick_kern' succeed.
[2024-05-06 23:05:33.524531 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO register_period_event_op 'boot time update' succeed.
[2024-05-06 23:05:33.524671 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO Tracer 'socket-trace', Not Found.
[2024-05-06 23:05:33.524744 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO Tracer 'socket-trace', Not Found.
[2024-05-06 23:05:33.524828 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO Tracer 'socket-trace', Not Found.
[2024-05-06 23:05:33.525062 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO Set ports_bitmap[DNS] success, ports 53,5353
[2024-05-06 23:05:33.525257 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO Set ports_bitmap[TLS] success, ports 443,6443
[2024-05-06 23:05:33.525506 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO Set ports_bitmap[FastCGI] success, ports 1-65535
[2024-05-06 23:05:33.525757 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO Set ports_bitmap[HTTP1] success, ports 1-65535
[2024-05-06 23:05:33.526003 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO Set ports_bitmap[MySQL] success, ports 1-65535
[2024-05-06 23:05:33.526244 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO Set ports_bitmap[Oracle] success, ports 1-65535
[2024-05-06 23:05:33.526485 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO Set ports_bitmap[PgSQL] success, ports 1-65535
[2024-05-06 23:05:33.526732 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO Set ports_bitmap[MongoDB] success, ports 1-65535
[2024-05-06 23:05:33.526979 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO Set ports_bitmap[MQTT] success, ports 1-65535
[2024-05-06 23:05:33.527237 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO Set ports_bitmap[HTTP2] success, ports 1-65535
[2024-05-06 23:05:33.527501 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO Set ports_bitmap[Custom] success, ports 1-65535
[2024-05-06 23:05:33.527767 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO Set ports_bitmap[Kafka] success, ports 1-65535
[2024-05-06 23:05:33.528045 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO Set ports_bitmap[Redis] success, ports 1-65535
[2024-05-06 23:05:33.528324 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO Set ports_bitmap[Dubbo] success, ports 1-65535
[2024-05-06 23:05:33.528588 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO Set ports_bitmap[SofaRPC] success, ports 1-65535
[2024-05-06 23:05:33.528670 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO check_kernel_version Linux 4.14.105-1
[2024-05-06 23:05:33.535815 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO Tracer 'socket-trace', Not Found.
[2024-05-06 23:05:33.536177 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO license: GPL
[2024-05-06 23:05:33.536793 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO Update map ("__socket_info_map"), set max_entries 524288
[2024-05-06 23:05:33.536924 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO Update map ("__trace_map"), set max_entries 524288
[2024-05-06 23:05:33.627294 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO Kernel not support interfaces bpf_probe_read{kernel,user}[_str]
[2024-05-06 23:05:34.636341 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO bpf load "socket-trace-bpf-linux-common" succeed.
[2024-05-06 23:05:34.636437 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO Perf buffer reader cpu(0) -> queue(0)
[2024-05-06 23:05:34.636646 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO Perf buffer reader cpu(1) -> queue(0)
[2024-05-06 23:05:34.636849 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO btf_vmlinux is null.
[2024-05-06 23:05:34.636877 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO [eBPF Kernel Adapt] Set offsets map from btf_vmlinux, not support.
[2024-05-06 23:05:34.636935 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO Received limit_size (0), the final value is set to '4096'
[2024-05-06 23:05:34.636976 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO Insert into map('__progs_jmp_tp_map'), key 0, program name bpf_prog_tp__proto_infer_2
[2024-05-06 23:05:34.637001 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO Insert into map('__progs_jmp_tp_map'), key 1, program name bpf_prog_tp__data_submit
[2024-05-06 23:05:34.637021 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO Insert into map('__progs_jmp_tp_map'), key 2, program name bpf_prog_tp__output_data
[2024-05-06 23:05:34.637045 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO Insert into map('__progs_jmp_tp_map'), key 3, program name bpf_prog_tp__io_event
[2024-05-06 23:05:34.637068 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO Insert into map('__progs_jmp_kp_map'), key 0, program name bpf_prog_kp__proto_infer_2
[2024-05-06 23:05:34.637088 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO Insert into map('__progs_jmp_kp_map'), key 1, program name bpf_prog_kp__data_submit
[2024-05-06 23:05:34.637111 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO Insert into map('__progs_jmp_kp_map'), key 2, program name bpf_prog_kp__output_data
[2024-05-06 23:05:34.637133 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO Insert adapt kern uid : 264993 , 267558
[2024-05-06 23:05:34.637442 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO config_proto_ports_bitmap, update eBPF ports_bitmap[HTTP1] success.
[2024-05-06 23:05:34.637474 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO config_proto_ports_bitmap, update eBPF ports_bitmap[HTTP2] success.
[2024-05-06 23:05:34.637496 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO config_proto_ports_bitmap, update eBPF ports_bitmap[Dubbo] success.
[2024-05-06 23:05:34.637522 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO config_proto_ports_bitmap, update eBPF ports_bitmap[SofaRPC] success.
[2024-05-06 23:05:34.637547 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO config_proto_ports_bitmap, update eBPF ports_bitmap[FastCGI] success.
[2024-05-06 23:05:34.637569 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO config_proto_ports_bitmap, update eBPF ports_bitmap[MySQL] success.
[2024-05-06 23:05:34.637619 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO config_proto_ports_bitmap, update eBPF ports_bitmap[PgSQL] success.
[2024-05-06 23:05:34.637645 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO config_proto_ports_bitmap, update eBPF ports_bitmap[Oracle] success.
[2024-05-06 23:05:34.637670 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO config_proto_ports_bitmap, update eBPF ports_bitmap[Redis] success.
[2024-05-06 23:05:34.637692 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO config_proto_ports_bitmap, update eBPF ports_bitmap[MongoDB] success.
[2024-05-06 23:05:34.637717 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO config_proto_ports_bitmap, update eBPF ports_bitmap[Kafka] success.
[2024-05-06 23:05:34.637739 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO config_proto_ports_bitmap, update eBPF ports_bitmap[MQTT] success.
[2024-05-06 23:05:34.637765 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO config_proto_ports_bitmap, update eBPF ports_bitmap[DNS] success.
[2024-05-06 23:05:34.637790 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO config_proto_ports_bitmap, update eBPF ports_bitmap[TLS] success.
[2024-05-06 23:05:34.637827 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO config_proto_ports_bitmap, update eBPF ports_bitmap[Custom] success.
[2024-05-06 23:05:34.637847 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO tracer(socket-trace) attach ...
[2024-05-06 23:05:34.645541 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO attach enter kprobe: 'kprobe/__sys_sendmsg', success!
[2024-05-06 23:05:34.653891 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO attach enter kprobe: 'kprobe/__sys_sendmmsg', success!
[2024-05-06 23:05:34.662547 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO attach enter kprobe: 'kprobe/__sys_recvmsg', success!
[2024-05-06 23:05:34.671495 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO attach enter kprobe: 'kprobe/__sys_recvmmsg', success!
[2024-05-06 23:05:34.677176 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO attach enter kprobe: 'kprobe/do_writev', success!
[2024-05-06 23:05:34.683062 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO attach enter kprobe: 'kprobe/do_readv', success!
[2024-05-06 23:05:34.683308 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO attach tracepoint: 'tracepoint/syscalls/sys_enter_write', succeed!
[2024-05-06 23:05:34.683389 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO attach tracepoint: 'tracepoint/syscalls/sys_enter_read', succeed!
[2024-05-06 23:05:34.683440 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO attach tracepoint: 'tracepoint/syscalls/sys_enter_sendto', succeed!
[2024-05-06 23:05:34.683518 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO attach tracepoint: 'tracepoint/syscalls/sys_enter_recvfrom', succeed!
[2024-05-06 23:05:34.683605 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO attach tracepoint: 'tracepoint/syscalls/sys_enter_connect', succeed!
[2024-05-06 23:05:34.683684 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO attach tracepoint: 'tracepoint/syscalls/sys_exit_socket', succeed!
[2024-05-06 23:05:34.683781 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO attach tracepoint: 'tracepoint/syscalls/sys_exit_read', succeed!
[2024-05-06 23:05:34.683923 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO attach tracepoint: 'tracepoint/syscalls/sys_exit_write', succeed!
[2024-05-06 23:05:34.683978 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO attach tracepoint: 'tracepoint/syscalls/sys_exit_sendto', succeed!
[2024-05-06 23:05:34.684027 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO attach tracepoint: 'tracepoint/syscalls/sys_exit_recvfrom', succeed!
[2024-05-06 23:05:34.684072 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO attach tracepoint: 'tracepoint/syscalls/sys_exit_sendmsg', succeed!
[2024-05-06 23:05:34.684121 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO attach tracepoint: 'tracepoint/syscalls/sys_exit_sendmmsg', succeed!
[2024-05-06 23:05:34.684170 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO attach tracepoint: 'tracepoint/syscalls/sys_exit_recvmsg', succeed!
[2024-05-06 23:05:34.684218 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO attach tracepoint: 'tracepoint/syscalls/sys_exit_recvmmsg', succeed!
[2024-05-06 23:05:34.684275 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO attach tracepoint: 'tracepoint/syscalls/sys_exit_writev', succeed!
[2024-05-06 23:05:34.684330 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO attach tracepoint: 'tracepoint/syscalls/sys_exit_readv', succeed!
[2024-05-06 23:05:34.684379 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO attach tracepoint: 'tracepoint/syscalls/sys_exit_accept', succeed!
[2024-05-06 23:05:34.684428 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO attach tracepoint: 'tracepoint/syscalls/sys_exit_accept4', succeed!
[2024-05-06 23:05:34.684500 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO attach tracepoint: 'tracepoint/sched/sched_process_fork', succeed!
[2024-05-06 23:05:34.684566 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO attach tracepoint: 'tracepoint/sched/sched_process_exec', succeed!
[2024-05-06 23:05:34.684625 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO attach tracepoint: 'tracepoint/syscalls/sys_enter_getppid', succeed!
[2024-05-06 23:05:34.684681 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO attach tracepoint: 'tracepoint/syscalls/sys_enter_close', succeed!
[2024-05-06 23:05:34.684752 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO attach tracepoint: 'tracepoint/syscalls/sys_exit_close', succeed!
[2024-05-06 23:05:34.684818 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO attach tracepoint: 'tracepoint/sched/sched_process_exit', succeed!
[2024-05-06 23:05:34.684847 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO Successfully completed attach.
[2024-05-06 23:05:34.685080 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO thread sk-reader-0, detached successful.
[2024-05-06 23:05:34.685144 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO register_extra_waiting_op 'offset-infer-server' succeed.
[2024-05-06 23:05:34.685186 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO register_extra_waiting_op 'offset-infer-client' succeed.
[2024-05-06 23:05:34.685208 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO register_period_event_op 'check-map-exceeded' succeed.
[2024-05-06 23:05:34.685230 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO register_period_event_op 'check-kern-adapt' succeed.
[2024-05-06 23:05:34.685255 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO [deepflow-ebpfctl] sockopt register succeed, type get: 504 - 504 set: 500 - 503
[2024-05-06 23:05:34.685280 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO [deepflow-ebpfctl] sockopt register succeed, type get: 603 - 603 set: 600 - 602
[2024-05-06 23:05:34.685359 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO check_kernel_version Linux 4.14.105-1
[2024-05-06 23:05:34.747803 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO set java_syms_write_bytes_max : 10178560
[2024-05-06 23:05:34.747890 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO set java_syms_update_delay : 600
[2024-05-06 23:05:34.747917 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO [CP] Set 'cpu_aggregation_flag' successful, value 0
[2024-05-06 23:05:34.748464 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO Tracer 'continuous_profiler', Not Found.
[2024-05-06 23:05:34.748648 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO license: GPL
[2024-05-06 23:05:34.789838 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO bpf load "continuous_profiler" succeed.
[2024-05-06 23:05:34.789936 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO set_enable_perf_sample() success, enable_flag:0
[2024-05-06 23:05:34.789975 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO Perf buffer reader cpu(0) -> queue(0)
[2024-05-06 23:05:34.790075 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO Perf buffer reader cpu(1) -> queue(0)
[2024-05-06 23:05:34.790136 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO Perf buffer reader cpu(0) -> queue(0)
[2024-05-06 23:05:34.790202 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO Perf buffer reader cpu(1) -> queue(0)
[2024-05-06 23:05:34.795044 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO tracer(continuous_profiler) attach ...
[2024-05-06 23:05:34.795152 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO attach perf event sample_freq 99 pid -1 cpu 0 done
[2024-05-06 23:05:34.795198 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO attach perf event sample_freq 99 pid -1 cpu 1 done
[2024-05-06 23:05:34.795220 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO tracer "continuous_profiler" attach perf event prog successful.
[2024-05-06 23:05:34.795236 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO Successfully completed attach.
[2024-05-06 23:05:34.795314 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO thread java_update, detached successful.
[2024-05-06 23:05:34.795377 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO thread cp_reader-0, detached successful.
[2024-05-06 23:05:34.795397 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO [deepflow-ebpfctl] sockopt register succeed, type get: 703 - 703 set: 700 - 702
[2024-05-06 23:05:34.795434 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO [CP] Set 'profiler_regex' successful, pattern : '^deepflow-.*'
[2024-05-06 23:05:34.795458 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO [CP] Set 'cpu_aggregation_flag' successful, value 0
[2024-05-06 23:05:34.795474 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO All tracers finish!!!
[2024-05-06 23:05:34.795501 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO Received limit_size (8192), the final value is set to '8192'
[2024-05-06 23:05:34.795555 +08:00] INFO [src/ebpf_dispatcher/ebpf_dispatcher.rs:672] ebpf collector initialized.
[2024-05-06 23:05:34.795579 +08:00] INFO [src/rpc/synchronizer.rs:524] Reset version of acls, groups and platform_data.
[2024-05-06 23:05:34.795705 +08:00] INFO [src/rpc/synchronizer.rs:524] Reset version of acls, groups and platform_data.
[2024-05-06 23:05:34.795765 +08:00] INFO [src/trident.rs:2573] Staring agent components.
[2024-05-06 23:05:34.795827 +08:00] INFO [src/platform/platform_synchronizer/linux.rs:983] socket info sync start
[2024-05-06 23:05:34.795853 +08:00] INFO [src/platform/kubernetes/active_poller.rs:255] starts kubernetes active poller
[2024-05-06 23:05:34.795908 +08:00] INFO [src/platform/prometheus/targets.rs:140] prometheus watcher is starting
[2024-05-06 23:05:34.795933 +08:00] INFO [src/platform/prometheus/targets.rs:146] did not turn on the kubernetes_api_enabled switch, or the environment is not suitable for the prometheus collection
[2024-05-06 23:05:34.795976 +08:00] INFO [src/debug/debugger.rs:393] debugger started
[2024-05-06 23:05:34.796025 +08:00] INFO [src/sender/uniform_sender.rs:242] 3-doc-to-collector-sender uniform sender id: 3 started
[2024-05-06 23:05:34.796074 +08:00] INFO [src/sender/uniform_sender.rs:242] 2-protolog-to-collector-sender uniform sender id: 4 started
[2024-05-06 23:05:34.796127 +08:00] INFO [src/sender/uniform_sender.rs:242] 3-flowlog-to-collector-sender uniform sender id: 2 started
[2024-05-06 23:05:34.796185 +08:00] INFO [src/sender/uniform_sender.rs:242] 2-packet-sequence-block-to-sender uniform sender id: 5 started
[2024-05-06 23:05:34.796233 +08:00] INFO [src/flow_generator/packet_sequence/parser.rs:88] packet sequence parser (id=0) started
[2024-05-06 23:05:34.796305 +08:00] INFO [src/flow_generator/protocol_logs/parser.rs:881] app protocol logs parser (id=0) started
[2024-05-06 23:05:34.796352 +08:00] INFO [src/flow_generator/protocol_logs/parser.rs:881] app protocol logs parser (id=1) started
[2024-05-06 23:05:34.796376 +08:00] INFO [src/collector/quadruple_generator.rs:738] new quadruple_generator id: 0, second_delay: 8, minute_delay: 68, l7_metrics_enabled: true, vtap_flow_1s_enabled: true collector_enabled: true
[2024-05-06 23:05:34.797707 +08:00] INFO [src/platform/kubernetes/active_poller.rs:93] kubernetes poller updated to version (1)
[2024-05-06 23:05:34.797814 +08:00] INFO [src/collector/quadruple_generator.rs:662] quadruple generator id: 0 started
[2024-05-06 23:05:34.797956 +08:00] INFO [src/debug/debugger.rs:126] debugger listening on: [::]:54870
[2024-05-06 23:05:34.798206 +08:00] INFO [src/collector/flow_aggr.rs:121] l4 flow aggr id: 0 started
[2024-05-06 23:05:34.798339 +08:00] INFO [src/collector/collector.rs:1240] second_collector id=(0) started
[2024-05-06 23:05:34.798463 +08:00] INFO [src/collector/collector.rs:1240] minute_collector id=(0) started
[2024-05-06 23:05:34.798544 +08:00] INFO [src/collector/quadruple_generator.rs:738] new quadruple_generator id: 1, second_delay: 8, minute_delay: 68, l7_metrics_enabled: true, vtap_flow_1s_enabled: true collector_enabled: true
[2024-05-06 23:05:34.799833 +08:00] INFO [src/collector/quadruple_generator.rs:662] quadruple generator id: 1 started
[2024-05-06 23:05:34.799919 +08:00] INFO [src/collector/collector.rs:1240] second_collector id=(1) started
[2024-05-06 23:05:34.800000 +08:00] INFO [src/collector/collector.rs:1240] minute_collector id=(1) started
[2024-05-06 23:05:34.800042 +08:00] INFO [src/collector/l7_quadruple_generator.rs:506] new l7 quadruple_generator id: 0, second_delay: 8, minute_delay: 68, l7_metrics_enabled: true, vtap_flow_1s_enabled: true collector_enabled: true
[2024-05-06 23:05:34.800289 +08:00] INFO [src/dispatcher/local_mode_dispatcher.rs:63] Start dispatcher (0)
[2024-05-06 23:05:34.800544 +08:00] INFO [src/collector/l7_quadruple_generator.rs:448] l7 quadruple generator id: 0 started
[2024-05-06 23:05:34.800756 +08:00] INFO [src/collector/collector.rs:1382] second_collector id=(0) started
[2024-05-06 23:05:34.800961 +08:00] INFO [src/collector/collector.rs:1382] minute_collector id=(0) started
[2024-05-06 23:05:34.801048 +08:00] INFO [src/collector/l7_quadruple_generator.rs:506] new l7 quadruple_generator id: 1, second_delay: 8, minute_delay: 68, l7_metrics_enabled: true, vtap_flow_1s_enabled: true collector_enabled: true
[2024-05-06 23:05:34.805716 +08:00] INFO [src/collector/l7_quadruple_generator.rs:448] l7 quadruple generator id: 1 started
[2024-05-06 23:05:34.805868 +08:00] INFO [src/collector/collector.rs:1382] second_collector id=(1) started
[2024-05-06 23:05:34.805981 +08:00] INFO [src/collector/collector.rs:1382] minute_collector id=(1) started
[2024-05-06 23:05:34.806036 +08:00] INFO [src/collector/l7_quadruple_generator.rs:506] new l7 quadruple_generator id: 2, second_delay: 8, minute_delay: 68, l7_metrics_enabled: true, vtap_flow_1s_enabled: true collector_enabled: true
[2024-05-06 23:05:34.806451 +08:00] INFO [src/collector/l7_quadruple_generator.rs:448] l7 quadruple generator id: 2 started
[2024-05-06 23:05:34.806522 +08:00] INFO [src/collector/collector.rs:1382] second_collector id=(2) started
[2024-05-06 23:05:34.806591 +08:00] INFO [src/collector/collector.rs:1382] minute_collector id=(2) started
[2024-05-06 23:05:34.806660 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:05:34.834281 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO ctrl_main begin !!!
[2024-05-06 23:05:35.835013 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO cpus_kick begin !!!
[2024-05-06 23:05:35.926281 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] INFO [eBPF Kernel Adapt] kernel_offset_infer_server close.client_count:2
[2024-05-06 23:05:36.806778 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:05:38.806942 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:05:40.807106 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:05:42.807302 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:05:44.807484 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:05:46.807649 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:05:48.807813 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:05:50.808012 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:05:52.808184 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:05:54.808343 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:05:56.808507 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:05:58.808669 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:06:00.808839 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:06:02.809016 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:06:04.809187 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:06:06.809357 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:06:08.809519 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:06:10.809700 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:06:12.809863 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:06:14.810028 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:06:16.810188 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:06:18.810367 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:06:20.810525 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:06:22.810690 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:06:24.810841 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:06:26.811020 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:06:28.811176 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:06:30.811333 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:06:32.811489 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:06:33.410357 +08:00] INFO [src/rpc/synchronizer.rs:205] Update PlatformData version 0 to<PHONE_NUMBER>.
[2024-05-06 23:06:33.410488 +08:00] INFO [src/rpc/synchronizer.rs:217] Update IpGroups version 0 to<PHONE_NUMBER>.
[2024-05-06 23:06:33.410517 +08:00] INFO [src/rpc/synchronizer.rs:227] Update FlowAcls version 0 to<PHONE_NUMBER>.
[2024-05-06 23:06:33.410534 +08:00] INFO [src/rpc/synchronizer.rs:809] Grpc version ip-groups:<PHONE_NUMBER>, interfaces, peer-connections and cidrs:<PHONE_NUMBER>, flow-acls:<PHONE_NUMBER>
[2024-05-06 23:06:33.411602 +08:00] INFO [src/rpc/synchronizer.rs:826] Grpc finish update cost 1.066317ms on 4 listener, 1 ip-groups, 15 interfaces, 0 peer-connections, 4 cidrs, 0 flow-acls
[2024-05-06 23:06:33.440345 +08:00] INFO [src/platform/platform_synchronizer/linux.rs:562] Platform information changed to version<PHONE_NUMBER>
[2024-05-06 23:06:33.440393 +08:00] INFO [src/platform/platform_synchronizer/linux.rs:826] local version changed to<PHONE_NUMBER>
[2024-05-06 23:06:33.657631 +08:00] INFO [src/flow_generator/flow_map.rs:412] loaded 0 wasm and 0 so plugins
[2024-05-06 23:06:34.811644 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:06:36.069962 +08:00] INFO [src/collector/flow_aggr.rs:315] now slot start time is<PHONE_NUMBER>s have flushed minute slot count is<PHONE_NUMBER>
[2024-05-06 23:06:36.811801 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:06:38.811960 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:06:40.023991 +08:00] INFO [src/sender/uniform_sender.rs:407] 2-protolog-to-collector-sender sender tcp connection to <IP_ADDRESS>:30033 succeed.
[2024-05-06 23:06:40.812127 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:06:42.812293 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:06:43.016512 +08:00] INFO [src/sender/uniform_sender.rs:407] 3-flowlog-to-collector-sender sender tcp connection to <IP_ADDRESS>:30033 succeed.
[2024-05-06 23:06:44.812451 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:06:46.812624 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:06:48.812783 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:06:49.080048 +08:00] INFO [src/sender/uniform_sender.rs:407] 3-doc-to-collector-sender sender tcp connection to <IP_ADDRESS>:30033 succeed.
[2024-05-06 23:06:50.812941 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:06:52.813115 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:06:54.813282 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:06:56.813454 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:06:58.813609 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:07:00.813763 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:07:02.813922 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:07:04.814085 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:07:06.814258 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:07:08.814413 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:07:10.814561 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:07:12.814720 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
[2024-05-06 23:07:14.814867 +08:00] ERROR [src/ebpf_dispatcher/ebpf_dispatcher.rs:613] [eBPF Kernel Adapt] The socket_tracer_start() error. Kernel offset adapt failed. Please ensure that BTF is enabled (kernel built with CONFIG_DEBUG_INFO_BTF=y option). If the current kernel version is low (<5.2), upgrading the Linux kernel to 5.2+ (kernel built with CONFIG_DEBUG_INFO_BTF=y option) can solve the problem. If it is not possible to upgrade the kernel, the kernel-devel package can be provided for developers to adapt and solve the problem.
[2024-05-06 23:07:14.814975 +08:00] INFO [src/ebpf/mod.rs:643] [eBPF] WARN func socket_tracer_start() [user/socket.c:2176] [eBPF Kernel Adapt] Adapting the linux kernel(4.14.105-1-tlinux3-0023.1) is in progress, please try the start operation again later.
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

@qyzhaoxun 感谢您的问题
从日志看，内核已经加载成功了，但是没有适配。
https://github.com/deepflowio/show-kernel-struct-offset ，根据这个，贴一下信息，我们来适配一下。


Add Quick Buttons

https://github.com/JasonStein/Notepads/pull/834
https://github.com/JasonStein/Notepads/pull/834
Dear friends and colleagues.
I created Quick Buttons. Look how do you like it?
I have Visual Studio buggy. I can't make a Pool request.
I had to use "GitHub Desktop".
First I made the buttons in Visual Studio. But then there were problems.
I used notepad to make separate changes to the project folder, I used "GitHub Desktop" to make a Pull request.
I ask for help to conduct a check and can fix some errors.

Only adds the function of quick buttons. But you only need to check the click execution for the buttons.. This will allow you to create quick buttons in any sequence. The sequence is determined by the order in which the switches are turned on. And it also uses saving settings , and uses localization for Label name

Move button to right to buttons window.
Testing click buttons
Testing in small mode.


[Bug?]: The Solid Start docs are broken

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
When I open https://start.solidjs.com/ this happens:

Expected behavior 🤔
The site should load normally
Steps to reproduce 🕹
Steps:

Open https://start.solidjs.com/

Context 🔦
No response
Your environment 🌎
System:
 OS: macOS Sonoma
 Browser: Arc, Safari, Firefox

Can confirm

Looks like there might be a Javascript error preventing the stylesheet from loading!
https://start.solidjs.com/core-concepts/assets/ssr-2f166d92.css

Should be fixed now (bump to vinxi 0.0.64)


Displaying ads images

If there are images for some ads, they will be got from DB and displayed on /postlist and /postdetails pages
Please, configure new virtual host img.ads-board2 for ads_images folder (folder will be created after ads creation)
and do then sudo chmod -R 777 ads_images/

Don't forget update your configs /application/config/default/site.php


PSDD Model Library fails to validate

Issue and tracking information
Developer's time Estimated effort to fix (hours):
Developer's Actual time spent on fix (hours)
Issue reporter to provide a detailed description of the issue in the space below
Our example using the PSDD model library does not validate.

I believe the problem is this line here: https://github.com/ZeligsoftDev/CX4CBDDS/blame/3b99c87145f1a561c0367b216fec0707346616b2/bundles/com.zeligsoft.domain.dds4ccm.psddconnector/models/CCM_PSDD.uml#L73  and this query is null.
Looking into the middleware for AXCIOMA, I don't see any attribute for query:
https://github.com/RemedyIT/ciaox11/blob/master/connectors/psdd4ccm/idl/ccm_psdd.idl#L33
I am not sure how this didn't break before but It is throwing errors now

Is this gating for the release? Let me know so I can work on it. Thanks.

Is this gating for the release? Let me know so I can work on it. Thanks.

Shooting an email now to you all to summarize our vision for what issues make it into the release. I figured that would be easier than commenting on the individual tickets.

Sounds good, Thanks!

Here is the updated PSDD library. Can you please take a look to see if it is o
PSDD.zip
k?

I imported your models into my workspace and overrode the installed pathmap for PSDD with the contents of your zip file. After that, I repaired module instantiations for our PSDD example and everything validated and generated correctly. I was also able to build using the generated idl and taginfo.xml files. I believe the updated PSDD library here fixes the issue we were seeing, although I will want to test again after it has been merged into the codebase and automatically installed into papyrus.

It is now merged to the papyrus branch. Let me know if you find any issues with the library. Thanks.

I verified the model library with the CX installed into Papyrus. Thank you.


GH-34852: [C++][Go][Java][FlightRPC] Add support for ordered data

Rationale for this change
No ordering is unnecessarily limiting.  Systems can and do implement distributed sorts, but they can’t reflect this in Flight RPC.
What changes are included in this PR?
These changes add FlightInfo.ordered.
Are these changes tested?
Yes.
Are there any user-facing changes?
Yes.
This PR includes breaking changes to public APIs.

Closes: #34852
Closes: #35085

An integration test is added.
We can review this but we can NOT merge this yet. We need one more implementation and a formal vote before we merge this.

@github-actions crossbow submit preview-docs

I took a look at the Go implementation. It seems that we don't need to change the Go implementation for this. (We just need to regenerated Flight.pb.go.)
I'll add a Go integration test for this before we start a discussion for this proposal.

Preview URL: http://crossbow.voltrondata.com/pr_docs/35178/format/Flight.html

@github-actions crossbow submit preview-docs

@github-actions crossbow submit preview-docs

The vote thread: https://lists.apache.org/thread/gnxv7cm5l01zgfos7mw52gr2337qofln
The vote result (passed):  https://lists.apache.org/thread/v05hxvffc118qtd4z4yqclryb7qslgfv
I'll merge this.

Thank you @kou


Integration tests cleanup, slot fixes

.. and some bonus removals of Infinispan tests

https://hibernate.atlassian.net/browse/HSEARCH-1864

outdated now, see #829 which includes this.


protoc 3.5.0 on linux-ppcle_64

Hi @nakul02
protobuf 3.5.0 is out, can we get protoc 3.5.0 binary on linux-ppcle_64?

Sure, I am waiting for access to a ppc64le machine. Once I get it, I’ll send you the protoc 3.5.0 binary.

Get it from here : https://send.firefox.com/download/9a6e738bcb/#soYPA-394whGOmAYGtwzhw

Thank you. But the file is 50MB. Could the binary be stripped (build disable-shared, strip)? Thanks

My bad. Here is the reduced file, built with install-strip.
https://send.firefox.com/download/6005589910/#dRkwRwvor2DJnWN7oEqjMw

Thanks! File added


Use Agg backend in examples with plot functionality

Fixes #7201

Jenkins, test this please.

Jenkins CI test (for commit edeffd4c78e6af1152b66f91c571f47fa50a7cd6, target branch master) failed with status FAILURE.

Jenkins failure looks unrelated.


[FEAT] Close all panes on hardware back button event

What are you trying to add to Cupertino-Pane?
Ability to close any and all existing panes.
Describe your feature request detailed
Throughout my Ionic App i use Cupertino Panes (they're great) and i track my hardware back button (see below)... it goes back in the navigation stack and shows a toast "press back again to exist app" once it has reached the last page. This is working well.
I want to add something, so that when a pane is opened... it is closed first when somebody presses the back button.. and then the normal behaviour continues.
This function (see below) is in a service file, and doesn't have access to the components in which the panes are presented.
public hardwareBackButtonEvent(): void {
   this.platform.backButton.subscribeWithPriority(10, () => {
     let currentTime = new Date().getTime();
     if (!this.canGoBack() && this.lastBackTime && this.lastBackTime > 0 && (currentTime - this.lastBackTime < this.intervalExitApp)) {
       (window.navigator as any)["app"].exitApp();
       return;
     }
     // if there is no previous page, show toast to exit app
     if (!this.canGoBack()) {
       this._createToastExitApp();
     } else {
       this.back();
     }
   });
 } // End of backButtonEvent()

I'm not sure how best to approach it, perhaps with events. that when i create a pane, it sends a signal to the navigation service? i'm not sure.
Is there an alternative at the latest version?
[ ] Yes (descripe the alternative)
[X] No
Is this related to an issue?
[ ] Yes (Give a link to the issue)
[X] No

@woutersteven2020 Thank you, I'm understand the issue.
Good a feature request, it's would be nice access to Pane instances from window object, from any code part, like window['pane']: [CupertinoPane, CupertinoPane, CupertinoPane, ...].
I will review this feature for the future.
For now, I suggest you to place your pane to some Singleton service where you collect global app variables:
import { SharedService } from '../services/shared/shared/shared.service.ts';

constructor (shared: SharedService) {

  // when you initiate a pane save it to shared scope
  this.shared.pane = new CupertinoPane(...);
}

Than access it from your hardware button service.
Some similar issues about hardware button (#143, #150)


Implement User Management for Java client

Create a new EventStoreDBUsersClient which supports the following operations:

[x] CreateUser
[x] GetUser
[x] DeleteUser
[x] EnableUser
[x] DisableUser
[x] UpdateUser
[x] ChangeUserPassword
[x] ResetUserPassword

https://github.com/EventStore/EventStoreDB-Client-Java/pull/227#issuecomment-1578577560