The integration hardcodes the receiver id

the integration hardcodes in the scraping request the received id so your tariff would not be respected if not changed that ID to any other correct ID
See here https://github.com/slesinger/HomeAssistant-PREdistribuce/blob/master/custom_components/predistribuce/sensor.py#L126
change povel to your HDO ID

Thanks for fixing it


The problem of code

Dear donghao
I try to use the Rivulet_plugin.cpp but it can not run well in VS2010 and VS2013.

Try to ubuntu

I think Zhi fixed it on windows?
Get Outlook for iOShttps://aka.ms/o0ukef

From: donghaozhang<EMAIL_ADDRESS>Sent: Wednesday, September 27, 2017 9:09:35 PM
To: RivuletStudio/Rivulet-Neuron-Tracing-Toolbox
Cc: Subscribed
Subject: Re: [RivuletStudio/Rivulet-Neuron-Tracing-Toolbox] The problem of code (#21)
Try to ubuntu
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/RivuletStudio/Rivulet-Neuron-Tracing-Toolbox/issues/21#issuecomment-332487672, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABfshYDAJ0eQgpS7I603pjDFJjAL-I8Wks5smizvgaJpZM4PllVN.

Thanks for the reminder @lsqshr .

@hnuwangchao I can not be certain. I remember two or three months ago, zhi fixed the windows compiling. But I am not sure vaa3d undergo some major changes or not which not lead to compiling error. https://github.com/Vaa3D/Vaa3D_Wiki/wiki/Build-Vaa3D-on-Windows-(QMake). It is the best you fix the comping error by yourself. If you stuck somewhere for a long time, you can try to seek  zhou zhi's help. But I can not be sure, he got time to reply you. zhi is very busy.

Compiling Vaa3D on Ubuntu is the easiest. On mac, it is easy. On windows,
forget about doing it yourself. I tried many times, never succeeded.
On 28 September 2017 at 11:02, donghaozhang<EMAIL_ADDRESS>wrote:

@hnuwangchao https://github.com/hnuwangchao I can not be certain. I
remember two or three months ago, zhi fixed the windows compiling. But I am
not sure vaa3d undergo some major changes or not which not lead to
compiling error. https://github.com/Vaa3D/Vaa3D_Wiki/wiki/Build-Vaa3D-
on-Windows-(QMake). It is the best you fix the comping error by yourself.
If you stuck somewhere for a long time, you can try to seek zhou zhi's
help. But I can not be sure, he got time to reply you. zhi is very busy.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/RivuletStudio/Rivulet-Neuron-Tracing-Toolbox/issues/21#issuecomment-332697407,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABfsha_Z78UISU6vMqO_X1yuDjDZUdhfks5smvAwgaJpZM4PllVN
.

--
Regards,
Siqi


Fix the bug where failing to copy correct row value when query results have been re-ordered

Summary

Fix the bug where failing to copy correct row value when query results have been re-ordered
How did you test this change?

[ ] Test(s) added
[x] Manual testing (please provide screenshots/recordings)
[ ] No testing (please provide an explanation)

before:
https://github.com/finos/legend-studio/assets/73408381/f3796ffc-59bc-433e-9d54-879ee5f72602
after:
https://github.com/finos/legend-studio/assets/73408381/504fa04a-69eb-4fb7-9026-a67bb09d28a9

fixed by https://github.com/finos/legend-studio/pull/2518


Multiple instances started when I specify --watch

Hi,
when I start jest with --watch option and babel-jest is enabled in the package.json, multiple instances of jest are launched at the same time, which looks like this on the cli:
1 test passed (1 total in 1 test suite, run time 0.035s)
Using Jest CLI v0.8.2, jasmine1
Using Jest CLI v0.8.2, jasmine1
 PASS  __tests__/test_add.js (0.022s)
1 test passed (1 total in 1 test suite, run time 0.028s)
 PASS  __tests__/test_add.js (0.004s)
1 test passed (1 total in 1 test suite, run time 0.008s)

Might it be that there are some temporary files being created which messes with fs change detection of the --watch option?
Version Info:

babel-core 6.4.0
jest 0.1.40
babel-jest 6.0.1
node v5.4.1

jest indeed writes the result of the preprocessor to a cache file whose location is specified by the cacheDirectory option of jest. It seems to be related to the this bug in jest: jest's --watch watches the whole rootDir as notices changes in cacheDirectory which leads to multiple starts.
As a temporary workaround I moved the cache directory somewhere else like this:
package.json:
  "jest": {
    "scriptPreprocessor": "<rootDir>/node_modules/babel-jest",
    "cacheDirectory": "/tmp/jest_cache",
   ...
   }

I'm closing this issue since it's not an issue with babel-jest.


Error UpdateOnboardingQuestionnaire.Run failed when submitting the onboarding product step

UpdateOnboardingQuestionnaire.Run failed: The data returned in the response is invalid. Response data should be a valid JSON object.

Latest deploy to PPE


default filter setting: by topmost parent element (for hierarchies)

Describe the bug
a data cube shall be filtered by the topmost parent element initially by default (in case hierarchy exists)
To Reproduce
Steps to reproduce the behavior:

Go to https://test.visualize.admin.ch/create/new?cube=https://environment.ld.admin.ch/foen/fab_hierarchy_test12_switzerland_canton_municipality/3
See left filter at 'Zurich'

Expected behavior
the topmost parent 'Schweiz' (Switzerland) shall be selected as an initial default
Screenshots

Environment (please complete the following information):

Visualize environment and version: TEST 3.8.0
Browser and version [e.g. Chrome 95]

Does this dimension have a hierarchy ? I could not see Switzerland when using this dimension as a color and when I check here : https://s.zazuko.com/aFuJs, I cannot see a hasHierarchy or inHierarchy predicate.

@ptbrowne 💯 hierarchy was missing...
works as expected with hierarchy in: https://test.visualize.admin.ch/en/browse/dataset/https%3A%2F%2Fenvironment.ld.admin.ch%2Ffoen%2Ffab_hierarchy_test13_switzerland_canton_municipality


Karma doesn't start server in browsers

I'm having a problem where karma never actually starts the server. It seems to start the browsers, but never the server. I've tested in Chrome, and after it's launched the http://localhost:9876/ never loads. Running on windows 8, and node 0.10.33
The weird part is, I have the same exact configuration for grunt-karma, and it works no problem.
I get the error below:
INFO [karma]: Karma v0.12.28 server started at http://localhost:9876/
INFO [launcher]: Starting browser PhantomJS
INFO [launcher]: Starting browser Chrome
WARN [launcher]: PhantomJS have not captured in 60000 ms, killing.
WARN [launcher]: Chrome have not captured in 60000 ms, killing.
WARN [launcher]: PhantomJS was not killed in 2000 ms, sending SIGKILL
WARN [launcher]: Chrome was not killed in 2000 ms, sending SIGKILL.

Here is my package.json for karma
"karma": "^0.12.3",
"karma-chrome-launcher": "^0.1.3",
"karma-coverage": "^0.2.1",
"karma-jasmine": "^0.1.5",
"karma-ng-html2js-preprocessor": "^0.1.0",
"karma-phantomjs-launcher": "^0.1.4",

@maksimr so anything come up relating to this? Is it just something we have to deal with?

@vernak2539  It's hard for me to say something sorry.
The best case is to look at the project.
Are you try run on linux?
Thanks!

Sorry, but I'm closing this due to inactivity. Please feel free to reopen with new details.

I'm having the same issue on debian:
06 04 2016 14:30:43.056:WARN [launcher]: PhantomJS have not captured in 60000 ms, killing. 06 04 2016 14:30:45.062:WARN [launcher]: PhantomJS was not killed in 2000 ms, sending SIGKILL. 06 04 2016 14:30:47.068:WARN [launcher]: PhantomJS was not killed by SIGKILL in 2000 ms, continuing.

Why closing this issue is still happening? Same WARN messages as the above user, but with CHROME instead of PhantomJS

@nicopeeters We had to split out our test running into batches. Seems the amount of files loaded when doing them all at once was too much. not sure if it applies to you, but if so. Not the best solution to be honest

same issue on Mac

OS X 10.9.5 - same issue here

I too am seeing the same issue as nicopeeters on the same environment.

same issue

same issue

Hi， I have the same problem with you , have you fixed it?

Same problem here...

Same problem here

30 07 2017 17:23:55.837:WARN [launcher]: Firefox was not killed in 2000 ms, sending SIGKILL.
30 07 2017 17:23:57.841:WARN [launcher]: Firefox was not killed by SIGKILL in 2000 ms, continuing.

Same problem. Chrome works fine.

02 08 2017 11:05:50.036:WARN [launcher]: Firefox have not captured in 60000 ms, killing.
02 08 2017 11:05:52.038:WARN [launcher]: Firefox was not killed in 2000 ms, sending SIGKILL.
02 08 2017 11:05:54.040:WARN [launcher]: Firefox was not killed by SIGKILL in 2000 ms, continuing.

+1
Same problem. Chrome works fine.

02 08 2017 11:05:54.040:WARN [launcher]: Firefox was not killed by SIGKILL in 2000 ms, continuing.

Same here and resolved. There was no Firefox browsers in my server just in my case.

Same problem, did anyone resolve this issue?

Hi, Did any one resolve this issue?
I had faced this issue in ChromeHeadless Browser

Same problem I don't know anymore how to solve it. Since I the error message is too ambiguous.
20 03 2018 14:56:41.565:INFO [karma]: Karma v2.0.0 server started at http://<IP_ADDRESS>:9876/
20 03 2018 14:56:41.567:INFO [launcher]: Launching browser ChromeHeadless with unlimited concurrency
20 03 2018 14:56:41.573:INFO [launcher]: Starting browser ChromeHeadless
20 03 2018 14:57:41.575:WARN [launcher]: ChromeHeadless have not captured in 60000 ms, killing.
20 03 2018 14:57:41.600:INFO [launcher]: Trying to start ChromeHeadless again (1/2).
20 03 2018 14:58:41.630:WARN [launcher]: ChromeHeadless have not captured in 60000 ms, killing.
20 03 2018 14:58:41.665:INFO [launcher]: Trying to start ChromeHeadless again (2/2).
20 03 2018 14:59:41.675:WARN [launcher]: ChromeHeadless have not captured in 60000 ms, killing.
20 03 2018 14:59:41.695:ERROR [launcher]: ChromeHeadless failed 2 times (timeout). Giving up.
npm ERR! code ELIFECYCLE

Trying to use a custom launcher in karma.conf.js:
    customLaunchers: {
      ChromiumNoSandbox: {
        base: 'ChromiumHeadless',
        flags: ['--no-sandbox']
      }
    },
    browsers: ['ChromeHeadless',  'ChromiumNoSandbox'],

@danger89
Hi Melroy, to answer my own question..

Remove the whole node_modules folder
If you didn't add puppeteer yet to the devdeps, run: npm i --save-dev puppeteer
Set the NODE_ENV correctly! Run: export NODE_ENV=development
npm install
Enable userns in the kernel (Debian only?):
echo 'kernel.unprivileged_userns_clone=1' > /etc/sysctl.d/00-local-userns.conf
service procps restart
Run the headless Chrome browser test: ng test --browsers ChromeHeadless --single-run=true

As you may noticed. I am using puppeteer to get the Chromium binary from the internet.
My karma.conf.js looks like:
// Set the CHROME_BIN
process.env.CHROME_BIN = require('puppeteer').executablePath()

module.exports = function (config) {
  config.set({
    basePath: '',
    frameworks: ['jasmine', '@angular/cli'],
    plugins: [
      require('karma-jasmine'),
      require('karma-chrome-launcher'),
      require('karma-jasmine-html-reporter'),
      require('karma-coverage-istanbul-reporter'),
      require('@angular/cli/plugins/karma')
    ],
    client: {
      clearContext: false // leave Jasmine Spec Runner output visible in browser
    },
    coverageIstanbulReporter: {
      reports: [ 'html', 'lcovonly' ],
      fixWebpackSourcePaths: true
    },
    angularCli: {
      environment: 'dev'
    },
    customLaunchers: {
      ChromeDebugging: {
        base: 'Chrome',
        flags: ['--remote-debugging-port=9222']
      },
      ChromiumNoSandbox: {
        base: 'ChromiumHeadless',
        flags: ['--no-sandbox']
      }
    },
    reporters: ['progress', 'kjhtml'],
    port: 9876,
    colors: true,
    logLevel: config.LOG_INFO,
    autoWatch: true,
    browsers: ['ChromeHeadless', 'ChromeDebugging', 'ChromiumNoSandbox'],
    singleRun: false
  })
}

same issue, linux

I encountered the same issue. What helped me:

Remove node_modules folder completely.
Run npm install.

Apparently karma files got corrupted and couldn't be fixed automatically.


Exceptions captured with option "include_local_variables" are not monitored/displayed at Sentry Dashboard.

How do you use Sentry?
Sentry Saas (sentry.io)
Version
1.21.0
Steps to Reproduce
We're capturing an exception in a celery task, with capture_exception(exception, include_local_variables=True). This exception is not getting monitored at Sentry Dashboard. While,  capture_exception(exception) catches the exception, and is monitored at Sentry Dashboard.
Captured exceptions in other Celery tasks, and API calls are working as expected - which are not using include_local_variables option.
Requirements
Python:  3.8.10
Django: 3.2.19
Django Rest Framework: 3.12.4
Sentry-SDK: 1.21.0
Celery: 4.4.0
Expected Result
capture_exception(exception, include_local_variables=True) should monitor the exception with local variables.
Actual Result
capture_exception(exception, include_local_variables=True) is not monitoring the exception.
capture_exception(exception) is monitoring the exception.

Hi @sarvesh-ridecell, thanks for reporting.
Could you please try updating to the newest version of the SDK (1.29.2 at the point of writing) and seeing if the error still occurs? We've made some updates to the Celery integration in the past couple of releases.
Does this occur only within a Celery task, specifically, or also outside/in a program that's not using Celery?
If you init the SDK with debug=True, is there anything interesting in the output (if you can see it while running Celery 🤔)? Do you see the msg about the error event being sent?

Hey @sentrivana, First of all - Thanks for the reply, and helping us debug the issue.
We tried out the steps mentioned, and found out both values for the flag include_local_variables are producing the same issue for us.
We upgraded our SDK to the version 1.30.0, and Initialised the Sentry with debug=True. It returned some logs, and we actually found something interesting - and I think it'll help us debugging the issue.
Attaching the log here -
{"logger_name":"sentry_sdk.errors", "level":"ERROR", "pid":9, "module":"", "log_timestamp":"2023-08-31T14:58:02.180646+00:00", "source_line":"/usr/local/lib/python3.8/dist-packages/sentry_sdk/hub.py:417", "message": "Internal error in sentry_sdk"}
Traceback (most recent call last):
File "/src/services/tasks/services_tasks.py", line 38, in update_system_status
raise Exception("Testing Sentry's upgrade to 1.30.0 in automatically called tasks.")
Exception: Testing Sentry's upgrade to 1.30.0 in automatically called tasks.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.8/dist-packages/sentry_sdk/hub.py", line 401, in capture_exception
return self.capture_event(event, hint=hint, scope=scope, **scope_args)
File "/usr/local/lib/python3.8/dist-packages/sentry_sdk/hub.py", line 347, in capture_event
scope = _update_scope(top_scope, scope, scope_args)
File "/usr/local/lib/python3.8/dist-packages/sentry_sdk/hub.py", line 82, in _update_scope
final_scope.update_from_kwargs(**scope_kwargs)
TypeError: update_from_kwargs() got an unexpected keyword argument 'include_local_variables'

We checked the dashboard as well, but no error was monitored/caught. The same log can be found for both values for flag include_local_variables.

Hey @sentrivana, Thank you so much for timely support! We found the issue in our codebase, and the expected exceptions are being monitored now. We really appreciate the help. Closing the issue with this.

Awesome, happy to hear that!


Opentelemetry helm chart upgrade from version 0.12.1 to 0.13.1 breaks jaeger traces receiver

We use 2 receivers in our configuration, jaeger and otel. Jaeger receiver is used to receive traces from traefik ingress controller because it does not support opentelemetry yet.
After helm chart upgrade to version 0.13.1 jaeger traces receiver stopped working in agent collector, while otel collector works as expected.
The following error is logged in the traefik ingress:
{"level":"error","msg":"Tracing jaeger error: failed to flush Jaeger spans to server: write udp <IP_ADDRESS>:44543-\u003e<IP_ADDRESS>:6831: write: connection refused","time":"2022-04-13T09:51:34Z","tracingProviderName":"jaeger"}
Relevant configuration:
opentelemetry-collector:
  config:
    receivers:
       otlp:
        protocols:
          grpc:
            endpoint: <IP_ADDRESS>:4317
          http:
            endpoint: <IP_ADDRESS>:4318
      jaeger:
        protocols:
          thrift_compact:
            endpoint: <IP_ADDRESS>:6831
  ports:
    otlp-http:
      enabled: true
    jaeger-compact:
      enabled: true
      containerPort: 6831
      servicePort: 6831
      hostPort: 6831
      protocol: UDP

   agentCollector:
      service:
        pipelines:
          traces:
            receivers: [otlp, jaeger]

Chart version 0.13.1 updated the default collector version to 0.48.0.  I am curious, if you use chart version 0.13.1 but set the image back to 0.47.0 what happens?
image:
  # Overrides the image tag whose default is the chart appVersion.
  tag: "0.47.0"

Similarly what happens if you use chart version 0.12.1 but update the collector version to 0.48.0?
image:
  # Overrides the image tag whose default is the chart appVersion.
  tag: "0.48.0"

Both 0.13.1 + 0.47.0 and 0.12.1 + 0.48.0 do not work. In fact, these combination are not compatible and produce errors in opentelelmetry-collector:
2022-04-13T18:44:26.655Z	error	exporterhelper/queued_retry_inmemory.go:106	Exporting failed. No more retries left. Dropping data.	{"kind": "exporter", "name": "otlp", "error": "max elapsed time expired rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial tcp: lookup opentelemetry-collector on <IP_ADDRESS>:53: no such host\"", "dropped_items": 35}

Strangely enough, the above mentioned error in the traefik log disappear in both combinations

The most recent error makes it seem like the collector is not able to export data to <IP_ADDRESS>:53.  Your setup is currently working on default 0.12.1?

I have tested all combinations again:
version 0.12.1 with default image (0.47.0) works correctly;
all other combinations 0.13.1 with default image (0.48.0), 0.13.1 + 0.47.0 and 0.12.1 + 0.48.0 produce the same error:
2022-04-13T18:44:26.655Z	error	exporterhelper/queued_retry_inmemory.go:106	Exporting failed. No more retries left. Dropping data.	{"kind": "exporter", "name": "otlp", "error": "max elapsed time expired rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial tcp: lookup opentelemetry-collector on <IP_ADDRESS>:53: no such host\"", "dropped_items": 35}

I could not reproduce the very first error
{"level":"error","msg":"Tracing jaeger error: failed to flush Jaeger spans to server: write udp <IP_ADDRESS>:44543-\u003e<IP_ADDRESS>:6831: write: connection refused","time":"2022-04-13T09:51:34Z","tracingProviderName":"jaeger"}

It was most likely caused by intermittent network issue

Is the configuration provided in the description your entire values.yaml?  If not, but you share all of it?  Can you also provide the collector logs?
What triggers this error?  Is it during startup or when data is sent to the collector?

Full values.yaml
opentelemetry-collector:
  # This allowes the k8sattributes processor to enrich the telemtry data with metadata
  clusterRole:
    create: true
    rules:
      - apiGroups: [""]
        resources: ["pods"]
        verbs: ["get", "list", "watch"]
  config:
    receivers:
      otlp:
        protocols:
          grpc:
            endpoint: <IP_ADDRESS>:4317
          http:
            endpoint: <IP_ADDRESS>:4318
      jaeger:
        protocols:
          thrift_compact:
            endpoint: <IP_ADDRESS>:6831
      prometheus: null
      zipkin: null
    service:
      pipelines:
        metrics:
          receivers: [otlp]

  ports:
    otlp-http:
      enabled: true
    jaeger-compact:
      enabled: true
      containerPort: 6831
      servicePort: 6831
      hostPort: 6831
      protocol: UDP
    jaeger-thrift:
      enabled: false
    jaeger-grpc:
      enabled: false
    zipkin:
      enabled: false
  ingress:
    enabled: true
    annotations:
      external-dns.alpha.kubernetes.io/alias: "true"
      kubernetes.io/ingress.class: traefik-internal

  agentCollector:
    resources:
      requests:
        cpu: 100m
        memory: 100Mi
      limits:
        cpu: 500m
        memory: 500Mi
    extraEnvs:
      - name: NODE_NAME
        valueFrom:
          fieldRef:
            fieldPath: spec.nodeName
      - name: OTEL_RESOURCE_ATTRIBUTES
        value: "host.name=$(NODE_NAME)"
    configOverride:
      exporters:
        otlp:
          endpoint: "opentelemetry-collector:4317"
          tls:
            insecure: true
      processors:
        # The k8sattributes in the Agent is in passthrough mode
        # so that it only tags with the minimal info for the
        # collector k8sattributes to complete
        k8sattributes:
          passthrough: true
        # Overwrite the host.name tag with the k8s node name as specified in OTEL_RESOURCE_ATTRIBUTES env var
        resourcedetection:
          detectors: [env]
          timeout: 5s
          override: true
      service:
        pipelines:
          traces:
            receivers: [otlp, jaeger]
            processors: [memory_limiter, resourcedetection, k8sattributes, batch]
            exporters: [otlp]

  standaloneCollector:
    enabled: true
    replicaCount: 3
    resources:
      requests:
        cpu: 200m
        memory: 400Mi
      limits:
        cpu: 1
        memory: 2Gi
    extraEnvs:
      - name: DD_API_KEY
        valueFrom:
          secretKeyRef:
            name: opentelemetry-collector
            key: datadog-api-key
    configOverride:
      exporters:
        datadog:
          api:
            site: datadoghq.eu
          env: dev
      processors:
        batch:
          timeout: 10s
        k8sattributes: {}
        # The translation of opentelemetry traces to Datadog traces for server spans
        # forms a Datadog resource using a combination of http.method + http.route.
        # However the io.opentelemetry.javaagent.tomcat-7.0 library only set http.method, and not http.route
        # This makes it hard to distinguish health calls from actual traffic.
        # We will copy the span name to the http.route attribute (but only if the attribute does not already exist)
        # 1. Extract the route from the span name to a temporary attribute
        span/extract_route:
          include:
            match_type: regexp
            libraries:
              - { name: "^io\\.opentelemetry(\\.javaagent)?\\.tomcat-7\\.0" }
          name:
            to_attributes:
              rules:
                - ^(?P<http_path_temp>.*)
        # 2. Copy the temporary attribute to the http.route attribute
        attributes/insert_route:
          include:
            match_type: regexp
            libraries:
              - { name: "^io\\.opentelemetry(\\.javaagent)?\\.tomcat-7\\.0" }
          actions:
            - key: "http.route"
              from_attribute: http_path_temp
              action: insert
        # 3. span/extract_route will replace the span name with {http_path_temp}, restore it back to its original value.
        span/restore_name:
          include:
            match_type: regexp
            libraries:
              - { name: "^io\\.opentelemetry(\\.javaagent)?\\.tomcat-7\\.0" }
          name:
            from_attributes: [http_path_temp]
        # 4. Delete temporary attribute
        attributes/delete_http_path_temp:
          include:
            match_type: regexp
            libraries:
              - { name: "^io\\.opentelemetry(\\.javaagent)?\\.tomcat-7\\.0" }
          actions:
            - key: "http_path_temp"
              action: delete
      service:
        pipelines:
          traces:
            receivers: [otlp]
            processors:
              [
                batch,
                k8sattributes,
                span/extract_route,
                attributes/insert_route,
                span/restore_name,
                attributes/delete_http_path_temp,
              ]
            exporters: [datadog]

This is the full collector log:
logs.txt

Also, traces from otel receiver are successfully exported to datadog, while the traces from jaeger receiver are failing

The errors I see definitely make me think that the daemonset collector cannot communicate with the deployment collector correctly.  Are both otlp and jaeger traces flowing through the daemonset to the deployment and then to datadog?
Can you provide the logs for the 0.48.0 deployment instance and also a the helm chart 0.12.1 daemonset and deployment logs?

These are the logs of 0.48.0 daemonset instance
logs_0.13.1.txt

Are both otlp and jaeger traces flowing through the daemonset to the deployment and then to datadog?
Yes. It is working for otel and not working for jaeger in 0.13.1
If I configure the jaeger receiver in the deployment instance, I am able to send the jaeger traces directly there; it works as expected. But the idea is to use the daemonset

@dmitryax what do you think?

I'm inclined to think if it was the charts causing the problem then using collector version 0.48.0 with chart 0.12.1 would work, and if it was the collector causing the issue I'm inclined to think that chart version 0.13.1 with collector version 0.47.0 would work.

I spent time trying to reproduce this error in a GCP k8s cluster using your values.yaml but have been unable to do so.  The closest I got was when I misconfigured the install and gave it a name so the service was example-opentelemetry-collector instead of opentelemetry-collector like the agent exporter expects. It was the exact same error though, which is interesting.  can you double check that the service installed with the deployment is named opentelemetry-collector

It seems like k8s DNS is not updated once the chart is upgraded to the new version. So a version shouldn't matter. Look like it caused by an upgrade. Please try to change replace opentelemetry-collector in the endpoint to the k8s new service IP address and see if it helps to isolate the issue

Replacing opentelemetry-collector by the service ClusterIP doesn't help. Moreover, it breaks the 0.12.1 working deployment.

Are you doing fresh installs or helm upgrade ?

I am doing ArgoCD sync. It basically does helm template and then kubectl apply

Please try a fresh install with the new version and see it the issue is still appears

Fresh install is seemingly working

Of course, it not a preferred way to do an upgrade in production :) because now it was a test environment.

Anyway, I think we can close the issue. Thanks!

Before you close, I am curious what happens if you do a fresh install of 0.12.1 and then follow your upgrade process for 0.13.1.

ok, I will try this

fresh install 0.12.1 -> works
upgrade 0.12.1 -> 0.13.1 -> doesn't work
then fresh install 0.13.1 -> works again
I am wondring why fresh install should be done and upgrade doesn't work

Has ArgoCD done any upgrades successfully in the past?  Like 0.11.0 to 0.12.1?

We didn't have any problems with upgrades in the past. But that time we had only otel receiver configured. Now we have added jager receiver and the problem occurs only with jager traces, as it is mentioned in the title of the issue.  No problem with otel traces

@sesto can this issue be closed?

Well, I still have problems. Now it stopped working even, if I do a clean install. But no matter what the otel receiver works. The problem is only with the jaeger receiver. I am kind of giving up


Log level

The article does not mention one important performance optimization that is the invocation of the logger being guarded by a log level check.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: aa00c051-c047-bbcd-5e25-ca6a722b51c3
Version Independent ID: 3f5f1b6e-06ac-cc07-48cd-b8b957a4abbb
Content: High-performance logging in .NET
Content Source: docs/core/extensions/high-performance-logging.md
Product: dotnet-fundamentals
GitHub Login: @IEvangelist
Microsoft Alias: dapine

Hi @paulomorgado - thanks for posting this issue. I'm curious how is it specifically a performance optimization to check the log level before calling a Log on a logger? It is my understanding that this check happens implicitly internally on the logger.

It:

Will not call the Log method
Will not create the object[] of parameters
Will not box any value types

If you look at the implementation of the LoggerMessage methods you'll see just that.
The code generated by the new generator won't even invoke the delegate if the log level is not enabled.


Prevent Preprint Creation from Deleted Node [OSF-7240]

Purpose

Prevent a preprint from being created if the node included in the request has been deleted.

Ticket

OSF-7240

Could you rebase this on develop, please? I think we don't need to hotfix this.

@brianjgeiger, rebased.


Implement records

Include records in the type hierarchy.
Clarify the array type.
Interprete top-level records as labeled scales.
Implement record literal syntax.
Add support for record access.
Implement builtin for record entries.
Implement stdlib for record keys and values.
ref #197

Reviewer assigned based on relevance to #188 .

Missing assignment of record elements.

The in operator would be nice.

ArrayAccess should be called AccessExpression now.

Should be good now. Taking a final look and self-merging after lunch.


Deal with PmagPy version requirements better

It would be good to formalize our list of dependencies for PmagPy.  In general, we've just instructed people to download the latest version of everything, but this can cause problems.

This file is a list of dependencies with #s:  https://github.com/PmagPy/PmagPy/blob/master/pmagpy_dependencies.txt
It should be kept updated with the package numbers that work with PmagPy.
This file is also a list of dependencies, but it is OSX specific and you can use it to install needed packages:  https://github.com/PmagPy/PmagPy/blob/master/pmagpy_env_osx.txt


defects revealved by arktos network integration

this is to over-all track the defects revealed in the process of Arktos network/mizar integration

[x] 1. virtlet failed to start - not an issue after the default network is ready
[x] 2. arktos-up.sh needs to provide a way to allow user to define default-network template path (fixed by #722);
[x] 3. coreDNS pod aborted on node with systemd-resolved service (workaround documented in #721)
[x] 4. per network kubernetes endpoints not in result of list verb (clarified in design doc by #735)
[ ] 5. kube-proxy (as is) started by arktos-up.sh is not tenant aware (known issue; plan to impl soon)
[x] 6. flannel cni plugin does not allocate IP to pod - seems env issue; verified OK with fresh machines.
[x] 7. network crd should be installed earlier than waiting for node ready in arktos-up.sh (fixed by #728)
[x] 8. DNS of system tenant may have entries of other tenants (issue #730)
[x] 9. flannel seems dependent on cni binaries (loopback, bridge, portmap etc) installed externally (fixed by #736, #755)
[x] 10. coredns pod in isolated networks cannot connect to kube-apiserver by <IP_ADDRESS> (issue #742 - Pr#744; long-term fix is tracked by #745)
[x] 11. sometimes node is unable enter Ready state (issue #756)
[x] 12. service associated to default network should not get IP from arktos when the net is external IPAM (issue #763 to keep this issue)

after the default network of system tennt is in Ready state, virtlet pod seems able to run and enter in Reunning state shortly;
will provide machine preparatio instruction to workaround this issue;

closed; most of the defects fixed; kube-proxy is not multi-tenant yet, is a known issue.


New prop added - fireOnRapidScroll

The new Prop is to allow the developers to disable firing of onEnter/onLeave events on rapid scrolling.

@trotzig cool, let me know.

I thought I posted a general comment here too, but I must have forgot to actually hit the submit button... Here goes:
First of all, thanks for contributing! I can see this being useful in a couple of use cases, and it would be good if you could briefly describe the one you had in mind. What's missing from this commit are some tests to verify the new behavior. I'll go ahead and do that in a follow-up commit, I'll make sure to tag you so that you can make sure that I got it right.


join relation override inherit where

What steps will reproduce the problem?
Join a relation and override the default where condition from the relation.
NavItem::find()
->select(['cms_nav_item.title', 'timestamp_update', 'update_user_id', 'nav_id'])
->joinWith(['updateUser' => function ($q) {
    $q->select(['firstname', 'lastname', 'id'])->where([]);
}, 'nav'])
->where(['cms_nav.is_deleted' => false])
->limit(10)
->orderBy(['timestamp_update' => SORT_DESC])
->asArray(true)
->all();

The relation inside the model:
public function getUpdateUser()
{
    return $this->hasOne(User::class, ['id' => 'update_user_id']);
}

The find method from the User model:
public static function find()
{
    return parent::find()->where(['is_deleted' => false]);
}

So the $q->select(['firstname', 'lastname', 'id'])->where([]); will override where(['is_deleted' => false]);.
btw: I'm sure there is also a better solution for this problem, but it was working in 2.0.13 so i thought it makes sense to report.
What is the expected result?
Returns the array with results.
What do you get instead?
In the current dev-master the $q->select(['firstname', 'lastname', 'id'])->where([]); does not override the relation where condition anymore. this will raise an exception:
"SQLSTATE[42000]: Syntax error or access violation: 1064
You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ')) AND (`id` IN ('1', '0'))' at line 1
The SQL being executed was:
SELECT `firstname`, `lastname`, `id`
FROM `admin_user`
WHERE (()) AND (`id` IN ('1', '0'))"

Additional info

Q
A

Yii version
dev-master

PHP version

Operating system

Will handle it this evening

I thing in all previous Yii versions ->where([...]) overwritten previously used ->where(). You need use ->andWhere([...]) or ->orWhere([...]) to append where condition.

@pistej I know, but i did the overide on purpose, which does not work anymore.

Fixed, thank you for the report.

@SilverFire just installed the latest dev-master, works as expected. Thanks


No matching clusters msg fix

Summary
Fixes #9683

Fixed condition for No matching clusters text
Screenshot/Video

==== No cluster pin  ======

==== All clusters are pinned ======

@bisht-richa , @scures Can you make sure all PRs have milestones?


GPIO - Copy-pasting a DIN node breaks some functionality

Build from yesterday, patches applied (especially #212)
/!\ Node-red updated to 2.1.4
Copy-pasting a DIN node that has the " Send initial message with level of pin." option enabled breaks that function.
It is still broken after a node-red restart from its GUI, or by restarting the systemd service.
Here's an example.
https://youtu.be/c-uMire1idE

Thanks for reporting! @fr0st61te, could you have a look what happens here?

Today, I tried to simply add a new DIN with the correct settings, and that one didn't work either. It was on the very first run of Node-red.
Is there maybe a timing issue between the flow restart and the activation of the pin?
I'd like to specify as well that Node-Red projects are enabled, although I highly doubt that will make any sort of difference.

@Webbeh Could you please provide your "function" code?

Oh it just inverts the payload.
return { payload:!msg.payload }

I made the same scheme that you have in video with same codeblock in function which you proposed but I have the trigger just once on deploy(which seems ok from #212) and it didn't even reach the function block as I see. So, question is - am I missing something in scheme?

So the trigger works on deploy for you after copy-pasting the node ?
Odd...
I don't think there's anything that you're missing in your flows. I guess the only variant is that node-red has been updated and it might break something.

Oh, you have updated Node-RED manually - missed that "detail". Can you reproduce the problem also with the original image then?
We will likely update Node-RED "officially" for our next major release as well, and maybe then we will see the same issue.

I haven't tried. We needed an up-to-date image and I haven't tried with the original image. I'll report back once I did it, I have a few devices to setup in a week or two.
To be fair, the only annoying point right now is MRAA not compiling for NodeJS 16+...

So the trigger works on deploy for you after copy-pasting the node ?

Yes, I tried it today again and it works as expected.

To be fair, the only annoying point right now is MRAA not compiling for NodeJS 16+...

If that topic is generic (reproducible without this layer), please do not hesitate to file an issue on https://github.com/eclipse/mraa/ (if there is nothing related already).
But note that we will not update to a NodeJS version without Debian support because that will cause too much additional integration and maintenance effort. Updating Node-RED is more realistic - or does it depend on NodeJS > 12 already?

I believe Node-red 3 (end of April 2022) is the first one who's gonna drop support for Node 12.

Do you have a pointer for this plan? So far, support goes way back, even down to Node JS 8.x.

Reopen if issues persist with latest master.


Mast: Watch bcomtimetable.in

Mast requests the watch of the watch_keyword bcomtimetable\.in. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

bcomtimetable\.in has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by tripleee in Charcoal HQ


Inaccuracies parsing jars

cdxgen has difficulty detecting group and name of some jars (running under -t jar). Some known problematic jars and sources:

ant-1.10.13.jar
logback-classic-1.4.7.jar
velocity-1.7.jar
commons-math3-3.6.1.jar

I compared this against syft, which gave results that I believe to be correct in each of these cases. I know of only one case where syft gives an incorrect result and cdxgen gives the correct result, which is with the versions of BouncyCastle jars from their website that exclude the . in the version in the filename.

jar
cdxgen group
cdxgen name
syft group
syft name

ant
org.apache.tools.ant
org.apache.tools.ant
org.apache.tools.ant
ant

logback
ch.qos.logback
classic
ch.qos.logback
logback-classic

velocity
velocity
org.apache.velocity
org.apache.velocity
velocity

math3
org
apache
org.apache.commons
commons-math3

It's perhaps worth noting that in the cases of ant and velocity, syft doesn't actually put the groups in the group field, but does use them in pURLs. It seems like those groups come from Implementation-Title in the manifest files. For these two files, the root cause is that syft uses the jar name for the name by default and falls back to the manifest, while cdxgen uses the manifest by default and falls back to the filename. Because of inconsistencies in how certain manifest fields are used (for example, Extension-Name), the manifest file seems less reliable than the jar filename.
For Logback, it seems like there is plausible doubt as to whether "classic" or "logback-classic" is the proper name. The package is ch.qos.logback.classic, which suggests a name of classic, but everywhere else the name logback-classic is used. Defaulting to the jar name would also change this file.
I have no idea what's going wrong with math3. Similar issues can be found with various other Apache Commons jars, but mostly older ones. I included Math3 because it's an example of a current Commons library with this issue.

Thanks @Eiim for the detailed report. Let me look into Syft's implementation to see if there is anything that can be done quickly with cdxgen. If not, we can wait and do this properly with semantic fingerprinting instead of assuming things from filename.


Rails 7.1 updated password validation changed rendering of password inputs

I'm not entirely sure who I should report this issue to, but it looks like has_secure_password change made in https://github.com/rails/rails/pull/47708 partially broke rendering of password inputs, as it doesn't use the regular validates_length_of anymore, but instead goes with a custom validation. So the following snippet renders different output in Rails 7.0 and Rails 7.1
class User < ApplicationRecord
  # has email attribute
  has_secure_password
end
...
@user = User.new
...
= simple_form_for @user, url: login_path, method: :post do |f|
  = f.input :email
  = f.input :password

Environment

Ruby 3.2.0
Rails 7.1.2
Simple Form 5.3.0

Current behavior
<form class="simple_form form-vertical new_user" id="new_user" novalidate="novalidate" action="/login" accept-charset="UTF-8" method="post">

    Email
    <input maxlength="100" type="email" size="100" name="user[email]" id="user_email">

    Password
    <input type="password" name="user[password]" id="user_password">

</form>

Expected behavior
Notice the maxlength="72" and size="72" attributes of password input
<form class="simple_form form-vertical new_user" id="new_user" novalidate="novalidate" action="/login" accept-charset="UTF-8" method="post">

    Email
    <input maxlength="100" type="email" size="100" name="user[email]" id="user_email">

    Password
    <input maxlength="72" size="72" type="password" name="user[password]" id="user_password">

</form>

Of course, as a workaround we can just specify maxlength for every password, password confirmation and password challenge input.

Hey @arg! Nothing much can be done about it, unfortunately. Yeah, technically we could check somehow if has_secure_password or bcrypt is used and apply limits, but with custom validation, we can't do it automatically as before. I think setting it manually is an acceptable workaround, and it's simple enough.


Fix sync status numerator counting down instead of up

A commit I forgot to push for the last PR. (My bad)
Fixes the numerator starting at the queue size and counting down.

Hah, that makes sense- merged! Thank you for the fix.


Global types are breaking type tets

Hi, first of all I wanted to say thank you for the hard work on the library! 😃
At our project we wanted to introduce type testing using tsd-lite along with tsd-runner-jest. We did a basic setup according to the docs to make a sort of MVP. The setup is mirrored in this repro repo.
The problem that we encountered is that types from the global scope seem to break the type tests. In this repro we're creating a type test but also importing a function to test its signature. This function is using a global type.
After running npx jest --config jest.config.tsd.js you can see that type ThisIsNull cannot be found, but it is used in the id function. The test would also break if we used ThisIsNull directly in the type tests since it would not
be recognized unless it's explicitly imported (which would make it non-global).
Steps to reproduce:

Clone the repo and install dependencies - git clone followed by npm i
Run the tests - npx jest --config jest.config.tsd.js
Check the result

Actual result:

Expected result:
ThisIsNull type should be known to the runner when importing the id function, error shouldn't be thrown
The question
So we wanted to ask whether we can do something about it right now, maybe we missed something? And if we can - would it require us to get rid of global types or do some hacks to get around problems surrounding them? Or maybe that problem is unsolvable for the time being?
Please let us know, thanks for any help in advance!
CC @erheron

Thanks for reaching out!
Checked your reproduction. Feels like something is wrong on tsd-lite side, because tsc compiles the same file with no issues.
Hm.. Interesting what is going on here. I will try to find time to think about it and to dig around.

Actually! A better solution could be simply to wait for a brand new type testing tool, which I mentioned here: https://github.com/jest-community/jest-runner-tsd/issues/32.
Just checked it, your reproduction is passing without any issues using this runner. It is near ready to be published. Should be out in 4-6 weeks.

Quick workaround. Add the following to the test file:
import '../types.d.ts';

tsd-lite does not see files which are not imported. It only picks compilerOptions from tsconfig.json and does not know anything more about files around. That’s a limitation unfortunately. But is fixed in the new runner which will replace tsd-lite very soon (;

Thanks for such a quick response and explanation!
It's good to know that we had a good intuition and it's actually an existing limitation. We'll wait for the new runner - amazing work by the way! I'll leave it up to you to decide whether to close or keep this issue open but I personally think it's good to keep it open :)

TSTyche, the testing tool I promised, is released. For details, see https://github.com/jest-community/jest-runner-tsd/issues/32#issuecomment-1808258311
Thanks for raising the issue. It gave me another bit of motivation to move on with TSTyche. Give it a try, please.
It works as expect with case you have described here. So I can close now (;


WindscribeLimited.Windscribe version <IP_ADDRESS>

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Noticed that as well on my main machine but haven't had the chance to set up a new VM, lost mine when I wiped to install fresh 11. Figured it was just my machine being weird since I had it already installed. According to their changelog they just added the silent flag with the latest version, but didn't see anything about any other flags

I just tried literally every way I can think of to call the silent feature or any other of the flags but none of them are working. Either I'm missing some magical way to call these, or their switches just don't seem to work, launching the installer without any switches works just fine so its not a installer corruption issue

Welp, guess will just have to wait until the fix hits release unless someone else had an idea


Longer reconnect time.

General Troubleshooting
Please check off these steps before suggesting a feature or reporting a bug:

[x] I am running the latest version:
[x] I have followed all instructions on the setup page (and if applicable, Raspberry Pi)
[x] I have read through the planned and suggested features

Issue
Issue Type

[ ] Bug Report
[x] Feature Request

Description
Allow a long reconnect time when this internet goes. this is an issues with me as my internet goes often and the bot usually stops retying before the internet is back. just make it so i tyres to reconnect for longer

The bot shouldn't stop retrying, it should repeatedly attempt to reconnect (with longer backoffs each time) until you close it. Also, if you don't have stable internet, you should look into renting a VPS and hosting there.

it doesnt this is what happens after it retres one or twice

When you fill out the issue template, please make sure you actually meet all of the checkboxes. You checked I am running the latest version but your screenshot isn't JMusicBot at all, it's some python bot.


GHL integration

Wondering whether I can use Superflows with my Saas-over-GHL product. Possible? Please advise!

Just to clarify: GHL is GoHigherLevel?
If so, we've spoken to them directly and have a working demo version that connects to GHL, so I'd be happy to help set this up for you!
I think it'd be easiest to discuss over a call. Does that work for you? Here's my calendar or we can organise over email

Good to hear from you. Thanks for getting back to me about my GoHighLevel
integration question. Please send any info you have via email and I'll also
book a call with you as soon as I can. Talk soon.
~Guin
On Tue, Sep 19, 2023, 3:10 AM Henry Pulver @.***> wrote:

Just to clarify: GHL is GoHigherLevel?
If so, we've spoken to them directly and have a working demo version that
connects to GHL, so I'd be happy to help set this up for you!
I think it'd be easiest to discuss over a call. Does that work for you? Here's
my calendar https://calendly.com/henry_pulver/15-min-chat or we can
organise over email @.***>
—
Reply to this email directly, view it on GitHub
https://github.com/Superflows-AI/superflows/issues/122#issuecomment-1725119794,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEJ35XALODWDXAVDR7JQAD3X3FOPDANCNFSM6AAAAAA45KVRGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hey, don't think I have your email address (just checked all my folders for an email!) so replying here - looking forward to chatting when you book in! :)


Unify bounding box for shapes during creation

Provide a mechanism to calculate and update the bounding box of a shape while drawing it.
This will honour things like the Center or LockAspectRatio modifiers.
If done before #148, there will be more to refactor in that issue. However this is higher priority.
Complexity: 2
Involves: Editor (Rust)

I'll work on this


[Question] How to only generate the (actually) required 'providers' with Terragrunt?

If a particular provider (say "hashicorp/kubernetes") is not required to be in required_providers in all but only particular environments (say "Staging"), how can we avoid duplication?
F.e., I have the following generate block in the root terragrunt.hcl, which then causes every leaf in the dependency graph to have kubernetes in its .terraform.lock.hcl. How can I have it not listed in environments where it isn't actually used?
# root terragrunt.hcl
    generate "versions" {
      path      = "versions.tf"
      if_exists = "overwrite_terragrunt"
      contents  = <<EOF
        terraform {
          required_version = "1.1.4"
          required_providers {
            aws = {
              source  = "hashicorp/aws"
              version = "4.18.0"
            }
            # This provider is only needed in some environments.
            kubernetes = {
              source  = "hashicorp/kubernetes"
              version = "2.11.0"
            }
          }
        }
    EOF
    }

The above generate block could be placed in an intermediary/per-environment terragrunt.hcl and have it overwrite the root terragrunt.hcl's versions.tf. But this would mean that the other, actually required-everywhere providers would have to be duplicated - only "hashicorp/aws" in this example, but there could be more.
In short, is there a way to have the following snippet only in environments that need it?
            kubernetes = {
              source  = "hashicorp/kubernetes"
              version = "2.11.0"
            }

Currently there are two ways to influence the behavior of the parent blocks:

Inheritance override in a merge operation
Folder structure based overrides

For this use case, the latter is probably what you want.
For example, you could define a bunch of flags to control the parent file. Consider a file called default_flags.hcl in the root folder:
locals {
  use_kubernetes_provider = true
}

And then for you can define a file flags.hcl to override this for specific folders:
locals {
  use_kubernetes_provider = false
}

Finally in the root config, you can do something like this to make use of all of this:
locals {
  flags = read_terragrunt_config(find_in_parent_folders("flags.hcl", find_in_parent_folders("default_flags.hcl")))
}

generate "versions" {
  path      = "versions.tf"
  if_exists = "overwrite_terragrunt"
  contents  = <<EOF
terraform {
  required_version = "1.1.4"
  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = "4.18.0"
    }

%{ if local.flags.locals.use_kubernetes_provider }
  kubernetes = {
    source  = "hashicorp/kubernetes"
    version = "2.11.0"
  }
%{ endif }
}
EOF

}

Now, correct me please if the following is incorrect, but if we wanted option (B) on this diagram, that is, to have the use_kubernetes_provider flag set at a leaf, not intermediary, level, then all we need is a locals block in that leaf's terragrunt.hcl. (It seems to work - I'm only being cautious.)

That unfortunately won't work because the locals don't merge up. That is, locals from the child are not visible in the parent. Ideally you can use fileexists with a ternary to handle this, but the current HCL parser doesn't terminate ternary expressions, so you would run into an error.

A side remark on its docs: it's a bit confusing to refer to an "optional name parameter" as it's not clear (to me at least) where the name comes from - quick glance at its source code doesn't reveal anything as well.

That's fair. We've gone through a few iterations on this so if you can suggest an improvement, that would be great!


Fix typo: Change 'the are' to 'there are'

This pull request fixes a typo in the documentation.
The phrase "the are" has been corrected to "there are".
Since this is a minor change, it qualifies as CLA: trivial.

Checklist

[x] documentation is added or updated
[ ] tests are added or updated

CLA: trivial

@tom-cosgrove-arm  like that ?

@Fare-spec Err, the CLA: trivial needs to be on a line on its own - see the example in my comment here. But thanks for fixing the "by" in the commit message, it's just the CLA: trivial that needs to be fixed now.
And no need to close the PR and create a new one: you can just do the work on same the branch and force push.

I might be stupid but i can't put another line under the title... maybe i need to do it in command line ? sorry for the waste of time

@Fare-spec Err, the CLA: trivial needs to be on a line on its own - see the example in my comment here. But thanks for fixing the "by" in the commit message, it's just the CLA: trivial that needs to be fixed now.
And no need to close the PR and create a new one: you can just do the work on same the branch and force push.

well i guess i just had to read the CONTRIBUTING.md beacause if i understand i just need to put it in the description( i hope)

@Fare-spec I'm not sure how you're creating this PR - I only use the command line, sorry. The CLA: trivial line needs to be on a line of its own, with a blank line before it, in the git commit message. The PR description is usually taken from the commit message when the PR is created, but here we only have the CLA: trivial correctly in the PR description.
@t8m Is this something that would be reasonable to correct during merge?

Is this something that would be reasonable to correct during merge?

As long as there is a clear statement from the author, and all reviewers that the submission is acceptable as trivial then a missing "CLA: trivial" header can be corrected during merge.

24 hours has passed since 'approval: done' was set, but as this PR has been  updated in that time the label 'approval: ready to merge' is not being automatically set.  Please review the updates and set the label manually.

@t8m can you confirm you're okay with trivial? (Per https://openssl-library.org/policies/cla/index.html:)

In practice, it is required that the author (in the git commit message) and all approving team members (in the pull request thread) agree that a change is trivial

yes, OK with trivial

Merged to the master, 3.4, 3.3 and 3.2 branches. Thank you for your contribution.


about redis error

Change cache configuration to redis
public $handler = 'redis';

The following is wrong:
Argument 1 passed to CodeIgniter\Cache\Handlers\RedisHandler::__construct() must be of the type array, object given, called in ...

RedisHandler.php
modify  these:
	public function __construct($config)
	{
		$config = (array)$config;
		$this->prefix = $config['prefix'] ?? '';

		if ( ! empty($config))
		{
			$this->config = array_merge($this->config, $config);
		}
	}

Can run！

Good catch. Care to submit a PR for this?

I've submitted a PR.

@jinmarcus I don't see any pull requests for this listed.

https://github.com/bcit-ci/CodeIgniter4/pull/792


"stickSize" component property was added in order to add ability to set stickSize without changing scaling proportions

The original issue was that on Mobile devices handles (sticks) were too small. The only way to make them bigger was to change "parentScaleX" and "parentScaleY", which also changed a ratio of resizing step. WIth this pull request "stickSize" may be changed without scale changes.
As an addition built files were included into the build.

@kirillmurashov Hi there! I'm wondering if this pull-request is something you could merge into the main repo? Any feedback is appreciated though.


StackNavigator specific lifecycle should be emphasized

Custom Android back button behavior · React Navigation

At first, you may be inclined to use componentDidMount to subscribe for the back press event and componentWillUnmount to unsubscribe. Reason why we do not use them is that they are not generally called when entering or leaving a screen.
More specifically, consider a StackNavigator with screens A and B. After navigating to A, its componentDidMount is called. When pushing B, its componentDidMount is also called, but A remains mounted and its componentWillUnmount is therefore not called.
Similarly, when going back from B to A, componentWillUnmount of B is called, but componentDidMount of A is not because A remained mounted the whole time.

This is significantly important especially when it is integrated with Redux. However, the document is placed on the improper location.
I have formed Redux states that correspond with page components one by one whose style is often adopted on the Web. But the behaviors of componentDidMount and componentWillUnmount on StackNavigator are completely different from those on the Web. I finally noticed that a state of stackable screen must be kept in an array or placed as a local state of React rather than the global state of Redux, but it was too late. I wasted a lot of time. This important information should be written in a early section.

this seems like something valuable to add to the 'fundamentals' section

We need a lifecycle to Judgment the view.


Reduces JSON packet size by omitting default values for common properties

Reduces JSON packet size by omitting default values for common properties
Batches test requests to avoid overwhelming analyzer
Improves handling of analysis set edge case
These all popped up while I was working with a large project from a customer.

👍


failing tests with Go 1.10

As the linked travis build demonstrates, the test TestGenerateTests fails with Go 1.10 due to changes to go fmt.
Here's a breakdown of the issue:

gotests generates a test
the generated test is then formatted (using Go 1.10 fmt)
the formatted generated output is compared against the golden files  which were formatted using an older version of Go
They don't match.

The exact formatting problem lies in this block:

I'm still thinking about how to go about this in a clean way.

Coverage remained the same at 95.76% when pulling cc3b7a764fa114d5771c6bac29e6ce8416688cf4 on jawher:go-110 into 651680c71b22b1164ee36398b009b2da5839e694 on cweill:master.

Coverage remained the same at 95.76% when pulling cc3b7a764fa114d5771c6bac29e6ce8416688cf4 on jawher:go-110 into 651680c71b22b1164ee36398b009b2da5839e694 on cweill:master.

Coverage remained the same at 95.76% when pulling cc3b7a764fa114d5771c6bac29e6ce8416688cf4 on jawher:go-110 into 651680c71b22b1164ee36398b009b2da5839e694 on cweill:master.

Coverage remained the same at 95.76% when pulling cc3b7a764fa114d5771c6bac29e6ce8416688cf4 on jawher:go-110 into 651680c71b22b1164ee36398b009b2da5839e694 on cweill:master.

Darn this is annoying. I'll think about it as well. Let me know if you come up with how to resolve this.

Here's an idea: since we don't really care about the tabs in the formatting, let's replace them with the empty string "" using https://golang.org/pkg/strings/#Replace right here.

Yup. The s/<tab>// trick works for now.
It is not a bullet-proof solution though: there were other minor changes to the formatting rules, like spacing between indices in slice indexing for example: https://golang.org/doc/go1.10#gofmt
Hopefully this should not arise anytime soon 😄

Thanks for the PR and the quick fix. Merged.

If you trust go/format from the standard library, another idea to consider is to compare not against the golden files, but formatted versions of golden files.
That way, the formatting algorithm used on both will be identical.
So:
if format(got) != format(want) {
	t.Errorf(...)
}

@shurcooL That is indeed much more elegant 🎩
@cweill what do you think ? I can create a PR with the proposed solution.

@shurcooL Very elegant solution! Much better than my little work around. :)
@jawher feel free to create a PR.


Fix names and descriptions of antenna_indices and ant_1/2_array

These represent antenna numbers NOT indices (they aren't required not to have gaps).

Fixed in latest commit.


Add "Commuter Rail Alternatives" tab to OL schedule

Summary of changes
Asana Ticket: Add "Commuter Rail Alternatives" tab to OL schedule
Added a commuter rail alternatives tab to the orange line page. This contains a timetable of CR stops from South Station to Forest Hills and links to the needed stops north of South Station.

Sweeeet. How much time do you think it would take to add the custom PDF links to https://cdn.mbta.com/sites/default/files/route_pdfs/2022-summer/2022-08-10-cr-hyde-park-forest-hills-ruggles-back-bay-south-station-ol-shutdown.pdf and https://cdn.mbta.com/sites/default/files/route_pdfs/2022-summer/2022-08-15-cr-oak-grove-malden-center-north-station-ol-shutdown.pdf described in the ticket? Should we do that as part of this PR or as a quick follow-up?

Looking at this again, I'd also like some minor adjustments to the copy and headings:

"at no charge" paragraph on its own at the top
"North Side Alternatives" h2
Haverhill link paragraph
"South Side Alternatives" h2
Slightly modified version of the timetable explanation: "This is a combined timetable for all commuter rail trains that will be running to south side Orange Line stations while service is suspended."
Combined timetable and the rest of the page as it is now

Sweeeet. How much time do you think it would take to add the custom PDF links to https://cdn.mbta.com/sites/default/files/route_pdfs/2022-summer/2022-08-10-cr-hyde-park-forest-hills-ruggles-back-bay-south-station-ol-shutdown.pdf and https://cdn.mbta.com/sites/default/files/route_pdfs/2022-summer/2022-08-15-cr-oak-grove-malden-center-north-station-ol-shutdown.pdf described in the ticket? Should we do that as part of this PR or as a quick follow-up?

@lund5000  I think this should be a quick follow up. Also think the pdfs come from the Siteweb endpoint so they'd have to put via an API I believe.

Also Direction picker isn't altering the table. Will investigate and make copy changes ⌨


Investigate the effiency of the chain download pipeline

Investigate the efficiency of the chain download pipeline. There could be some pauses in the pipeline due to waiting on stages to complete.

Yes, agreed. The pipeline is a set of steps that are executing in parallel and in a certain order. Each stage is dependant from the stage before and the stage after as we can see in the diagram below. We need to review the metrics to be able to spot wait time on each step on either when putting data to the next step or when reading data from the step before.
In a perfect configuration, each step should be doing work all the time, not blocking on either the step before or the step after.


Explorer: weird hover effect when hovering into view

Steps to Reproduce:

I run out of master with fresh user data dir on macOS
zoom in once (important it seems)
open a folder
move mouse into explorer

=> 🐛 notice how the elements move up and down

Not sure if related to the translate3d issue.

I can repro when I zoom in once.
I can repro both with Open Editors and with Explorer.
The best I can do is do a Git bisect. @joamoreno let me know if you would like me to go on this path.

I have a feeling this started only recently.

There were no changes here recently. And I don't a macOS to repro. So yeah, try to bisect.
My two cents tho: Electron update, which will be a pain to bisect through. 😢

Ok bisecting.
Also we did not do an electron update in the last 2 months so I think it is something else.

This is the commit to blame
https://github.com/microsoft/vscode/commit/e074920d89c9ff425d5e582aeb85fda309bcf7cf
@sbatten can you look into this please?


Fix RangeSlider semantics node size

part of https://github.com/flutter/flutter/issues/114225
Description
This PR fixes semantics node size for RangeSlider
Current behavior simply divides the node size in half.  This doesn't match when testing on Android.
Android

Left
Right

Flutter

Before
After

Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Does this all work correctly if the text direction is RTL? I expect that there should be a RTL version of the test.

Does this all work correctly if the text direction is RTL? I expect that there should be a RTL version of the test.

Sure, we can add a semantics test for RTL
However, it looks like there is a bug in matchSemantics. Even if I match all everything, it fails in RTL in the last node.
I will look into it further in an isolated test.

I've investigate the problem, filed an issue https://github.com/flutter/flutter/issues/115079
Also fixed the tests here.


Optimize S3 upload

We can optimize our S3 upload a bit by adding the following extra flags:

--size-only: Only upload a version if the size of the object has changed.  Without this, since our timestamps are always newer (because we just copied all the files over) we're copying everything up every time.  Since the sizes of things should be changing when uploading, I think this is fairly safe to set.
--delete: We want to remove files that no longer exist locally, so that when we delete a file, it gets deleted on S3 as well.

Also, we can split the Aggregate.yml file into two pieces, on that does the build, one that does the upload, so that only the upload part is signed.  This will allow Aggregate.yml to be an unsigned pipeline, and editable without needing @thazhemadam to re-sign the pipelines.  :)

Also, we can split the Aggregate.yml file into two pieces, on that does the build, one that does the upload, so that only the upload part is signed.

Doesn't the build part also need to be signed since we encrypt the DOCUMENTER_KEY?

On second thought, we might need to consolidate both steps into one because buildkite's artifacts have an upload size limit of 5GB, which our documentation builds easily surpass, so we can't have them in separate steps. Closing this issue.


Added Azure.Arc.Kubernetes.Defender

PR Summary
Fixes #2124
Added Azure.Arc.Kubernetes.Defender rule.
PR Checklist

[x] PR has a meaningful title
[x] Summarized changes
[x] Change is not breaking
[x] This PR is ready to merge and is not Work in Progress
Rule changes

[x] Unit tests created/ updated
[x] Rule documentation created/ updated
[x] Link to a filed issue
[x] Change log has been updated with change under unreleased section

Other code changes

[ ] Unit tests created/ updated
[ ] Link to a filed issue
[ ] Change log has been updated with change under unreleased section

@BernieWhite Let me know what you think about this one.

@BernieWhite Great to hear and thanks for the suggestions. Adjusted.


Add searching by used functions in examples page

Resolves https://github.com/raysan5/raylib.com/issues/56

@RokasPuzonas Amazing work! Thank you very much! It's a big update, I did a quick review and it looks good to me.
Let me know if it's ready for merging!

@raysan5 Yup it is ready, this is the version with the JSON file trimmed to only include which examples use a certain function and not locations.

@RokasPuzonas Nice! Thanks again for this amazing improvement! 😄
Just a side note, I got plans to redesign raylib website to something more professional, specially the landing page... but undoubtely this feature will be kept!


[Demangler] Null-check a pointer before using it in arithmetic

This addresses a UBSan -fsanitize=null diagnostic seen when compiling
the stdlib:
runtime error: applying non-zero offset 128 to null pointer

@swift-ci smoke test and merge


Update truffle decoder and truffle compiler

Fixes #91 and fixes #83

Version 12 of Node breaks CI because of node-gyp not being able to build. However, v11 and LTS pass just fine.

Currently blocked by https://github.com/axic/keccakjs/issues/8


Can we use Generative models for Question Answering?

Hello, I really liked your repository.
I have a question regarding the GenerativeQA. I am basically creating an application which takes multiple documents from the user and on querying, it retrieves the relevant documents and answers the questions based upon that.
I am willing to use the "GPT-J-6B" model for it. And this is the approach I would like to go with:
# Step 1: Create document store (in haystack) and store all documents

# Step 2: Ask question. So assuming based on the question we have received top 10 relavant documents

# Step 3: Append these documents together and pass as the context.

# Step 4: Create the prompt
prompt = \
f"""Answer the question from the context below. And don't try to make up an answer.
If you don't know the answer, then say I don't know.

Context: {context}

Question: {query}

Answer:"""

# Step 5: Create a model and try generating the answers
# using gpt-neo-125m for now
tokenizer = AutoTokenizer.from_pretrained("EleutherAI/gpt-neo-125M")
model = AutoModelForCausalLM.from_pretrained("EleutherAI/gpt-neo-125M")

# Step 6: Get the answers
tokens = tokenizer(query, return_tensors="pt")
output = model.generate(**tokens,
    temperature=0.5,
    min_length=5,
    max_length=200,
    early_stopping=True,
    do_sample=True,
    num_beams=8,
    repetition_penalty=2.0, top_k=50)

print(tokenizer.decode(output[0]))

But I am getting the error here because of the long length of the prompt. Will you please help me through this?
Input length of input_ids is 553, but max_length is set to 200. This can lead to unexpected behavior. You should consider increasing max_new_tokens.
And...
The expanded size of the tensor (200) must match the existing size (554) at non-singleton dimension 0.  Target sizes: [200].  Tensor sizes: [554]
So obviously, I need to truncate the text some how.
Is this the right/fast way to create such QA systems?
Are my parameters wrong?
Please help. Thanks 🙏

Hi, I'm a newbie too. I've just tried your code with the newest version transformers: 4.27.3 and do not get any error like you. So, what version of transformers you are using? Generate text of transformers is many parameters you can check here:
https://huggingface.co/docs/transformers/main_classes/text_generation
When changing the value any parameters and output are different, so you need read more in-depth.

That worked. I used max_new_tokens and other parameters. That solved my issue. Thanks.
I have a noob question if you don't mind 😓
I was thinking to "fine-tune" the model so that instead of passing the context inside of the prompt (for my own documents), we can get the results by just asking the question.
So, if I have data of some domain, say "medical", then I will train the GPT-Neo or J with that data and then just will ask the question to get the answer.
Now, the thing is,
I have come across 2 terms.

Fine tuning
Training (usually from scratch)

The fine-tuning is I guess related more with the "transfer" learning where we instead of training whole model, just train the head, right? So, in my case
do you think I should go forward with the fine-tuning?
Apologies, for such questions 😓


feat: automated test initiation

Type of modification

[ ] Breaking change
[ ] New Feature
[ ] Bug Fix
[X] Chore (refactor, documentation, tests... all the changes with no impact on ARA functionalities.)

Changes description
Add some quick description about what your PullRequest change in
ARA's feature/behavior
Add API Test based on Postman
Technical description
Add a quick description about what your PullRequest change in
ARA's code. (example: add a processor check in...)
PR CheckList
Please make sure your PullRequest respect all those items :

[X] Your PR's title has the prefix : feat:, fix: or chore:
[X] You have asked a review from one of the ARA maintainer in your PR.
[ ] If your PR is related to an issue, add the issue's number in it.
[ ] All the code you added is documented.
[ ] All the code you added is tested and the  tests are in success.
[ ] You already signed the Contributor License Agreement and give us the document

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


README: replace maintenance badge

Proposed Changes
The year part of the Shields.io maintained badge needs to be updated with the current year for it not to show as "No" (unmaintained/abandoned).
I'd like to suggest using a different badge - "Last commit" - instead which doesn't need manual updating each year and still gives a reasonable indication of the maintenance status of the project.
Related Issues

https://shields.io/#/examples/other

Agreed, thank you for the suggestion AND the PR.


GMC: enhance log

Description
Use standard log to replace the fmt.Printf functions
use curl -X GET "http://localhost:8008/loglevel?level=debug" and curl -X GET "http://localhost:8008/loglevel?level=info" to change the debug level
Issues
n/a.
Type of change
List the type of change like below. Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would break existing design and interface)

Dependencies
n/a.
Tests
no new feature, CI/CD covers the regression tests

Thanks @KfreeZ for adding this support,  Can we change it a little bit to better relflect HTTP VERBs? like:
curl -X GET "http://localhost:8008/loglevel    -- this will return current loglevel for user
curl -X PUT "http://localhost:8008/loglevel -d '{"log_level":"debug"}'   -- this will change current loglevel to 'debug`
also plz update docs to tell user how to use it.

Thanks @KfreeZ for adding this support, Can we change it a little bit to better relflect HTTP VERBs? like:
curl -X GET "http://localhost:8008/loglevel -- this will return current loglevel for user curl -X PUT "http://localhost:8008/loglevel -d '{"log_level":"debug"}' -- this will change current loglevel to 'debug` also plz update docs to tell user how to use it.

done


perlPackages.libnet: 3.12 -> 3.13

Motivation for this change
Get the fix for https://rt.cpan.org/Public/Bug/Display.html?id=133912
Tested as part of gitFull by doing a git send-email with SMTP misconfigured.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Can you change the commit and PR-title from "perl/libnet: 3.12 -> 3.13" to "perlPackages.libnet: 3.12 -> 3.13"?

Sure, thanks, done!

@GrahamcOfBorg build gitFull perlPackages.libnet

Thx for the update!


chore: release v0.3.10

:robot: I have created a release beep boop
0.3.10 (2024-08-09)
Bug Fixes

deps: update dependency @floating-ui/dom to v1.6.10 (#100) (a3d98ca)
deps: update dependency tsx to v4.17.0 (#103) (81d2e0c)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v0.3.10
:sunflower:


Question:

Hi,
Is it possible to deploy the Springfox-swagger UI as an independent webapp, and have it load the api-docs of my deployed service? The reason I want to do this is because I want to expose the Swagger UI to clients or give them a webapp bundle which they can deploy anywhere and test, so I want the UI separate from my service code. By UI, I mean only the HTML and JS files of the springfox-swagger UI, which points to a swagger.json file by a relative path in its file dircetory. This bundel should be able to load the documentation even if the user is offline.

Yes its possible thats exactly what jhipster does. You can have one of two options

Use the standard Swagger-ui bundle
If you want a little more discovery, you need to follow the instructions here


Need support of MAC VTAP

The mac vtap is using the same macvlan_link_register as MAC VLAN did.
It should have identical options as MacVlanInfo did.

I am working on this. Thanks!

Done on #43


About Description in README

It is described in README.md
THe Perl module Date::Time can be installed using sudo apt install libdatetime-perl or sudo yum install perl-Date-Time. You can also install it from sources downloaded from CPAN.
Maybe it should be.
yum install perl-DateTime

Commit e1c0bbe fixes this issue.

您的邮件，我已接收。


geoplot installed but geoplot.crs is not found

I recently updated Anaconda today and reinstalled geopandas and geoplot successfully. However when import
import geoplot.crs as gcrs
it shows ModuleNotFoundError:
No module named 'geoplot.crs'
both geopandas and geoplot were imported successfully.

Thanks for replying? Which environments are working? I have tried Spyder and Jupyter via Anaconda. I can try another environment if it can support the geoplot. I really like it by the way.

Thanks. It's sorted now. All relevant packages have to be installed in the same environment, including the console, e.g. Spyder.


how to use heartbeat to make sure socket connection is alive?

I don't know how to  Push Notification Heartbeat Network Package from client to service .  Thanks

Please ask this on Stack Overflow.


error creating overlay mount to /var/lib/sealer/tmp/.DTmp-030492001: too many levels of symbolic links

I made an error in sealer build
command：
sealer build -m lite -t kubernetes:v1.19.8 .
ERROR：
failed to mount target /var/lib/sealer/tmp/.DTmp-030492001:error creating overlay mount to /var/lib/sealer/tmp/.DTmp-030492001: too many levels of symbolic links
Environment:

sealer version (use sealer version):v0.8.3
Cloud provider or hardware configuration:
OS :CentOS Linux release 7.2.1511 (Core)
Kernel (e.g. uname -a):5.4.8-1.el7.elrepo.x86_64

@qq510521 ,seems the build context has some error.  FYI: https://www.baeldung.com/linux/too-many-levels-of-symlinks

@qq510521，似乎构建上下文有一些错误。仅供参考：https ://www.baeldung.com/linux/too-many-levels-of-symlinks

thanks，Because the ‘’Kubefile‘’ has a duplicate


Updated faraday to 0.9.1

There's no test-suite for shenzhen, although i have a fork running using faraday-0.9.1 for quite a while and there's no errors related to faraday.

Thank you @tobiasstrebitzer :+1:

I'll publish a new version.


-ExcludeBlockDownloadPolicySiteOwners

[Enter feedback here]
Has anyone been able to use the -ExcludeBlockDownloadPolicySiteOwners parameter?  It appears that it does not exist.
I am trying to find a way to allow Owners to download, but have been unable to find the owners GUID.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: acbfb458-2ccd-84ed-b5dd-9493f6d5c003
Version Independent ID: a7db833e-2f56-e147-8f84-ccf1a86ed71a
Content: Block the download of files from a SharePoint site or OneDrive (preview) - SharePoint in Microsoft 365
Content Source: SharePoint/SharePointOnline/block-download-from-sites.md
Service: sharepoint-online
GitHub Login: @MikePlumleyMSFT
Microsoft Alias: mikeplum

Thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.


Update the aws bootstrap script with correct version

Update the bootstrap script with correct scala version and hbase version. Since we drop the support for 2.11 and we are moving towards hbase 2, I just change it to two by default.

@ronq @jrs53 @elahrvivaz first to make change to this repo, feel free to comment and review! Thanks

thanks for fixing this!

thanks for fixing this!

You are welcome. Committed the suggested changes!


Android incoming call screen

Thanks for the contribution @oluwaseye!
At this point it looks like the sample provides fairly minimal functionality. We either like the samples to provide a lot of functional code or a really nice design. The animation is good, but if you can think of anythings else to add that would be great and a good reason for us adding this to the marketplace!


Remove legacy mesos scheduler

@Xenorith fyi removing -Pmesos

thanks for the heads up. what would happen after this PR merges and -Pmesos is still set? do you know if the command will fail or will the flag be ignored?

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-PR-Builder/10684/
Test PASSed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-PR-Builder-jdk11/1/
Test FAILed.

LGTM

alluxio-bot, merge this please.

@madanadit not sure if this is related, but there's a runMesosTest option in bin/alluxio and associated docs in User-CLI.md

@Xenorith that is related, i need to remove that as well


[resource] Create resource in resource frontend selecting child categories issue

The problem only exists in cpanel but not backend
This is a screenshot from backend. if working fine, selecting Main Type: award will only allow you to choose its subcategories which are: awards, competition, certification

render same create new resource form (in cpanel) for frontend user. issue fixed.


Media Manager File Limit

Version information

Laravel: v6.2
Voyager: v#.#.#
PHP: 7.3
Database: [type] [version] (e.g. MySQL 8.0)

Description

A clear and concise description of what the bug is.
Media Manager File upload Limit is not in sync  with my server
Steps To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.
I have my server configured to upload file up to 2GB, however, the media manager is limiting me to only  256 MB.
if I upload  using the file input type it's works fine

Hi I Save that  was close however, I'm having this issue I can't upload files over 256 MB using the media Manger, however, it works  if I use a file input tag

Ok so the problem is with dropzone-js it had a default max file size of 256 Mib


[Search] - Regenerate based on latest swagger

At the time of this issue creation, we cannot regenerate. Because, the swagger is not merged. Why? Because, it has some features which might break the SDK generation process. Details to be collected yet.
Further details needed whether we need custom layer modification (I am marking the estimate to 2. If there is no custom layer code is required it might change to 1)

Code complete with PR https://github.com/Azure/azure-sdk-for-js/pull/11533


how to save the video url in remote database and access again to load the video?

the video is greyed out and doesn't play


tests for null experience

Story/Ticket Reference ID from JIRA:
Add link here
Additional Comments:
a test for null experience
Checklist:

[ x ] Unit test completed?: Y
[ x ] Docs folder up to date?: Y

All Checklist are okay.
This PR looks great - it's ready to merge! Please review and let's ship it. :)

@shawnm0705 , these codes intends to fix the sonar warning of uncovered conditions to this line of new code
activityCompleteMessage: this.utils.has(programObj, 'experience.config.activity_complete_message') ? programObj.experience.config.activity_complete_message : null,


Route Reset Warning

When a route being plotted is not Finished, a warning or alert should be added; when changing the field view/recentering the map to a new star, the unfinished route will disappear/be erased.

I placed an indicator to show that routing is active/inactive.
I added checks for starting, continue or finish to make sure you don't inadvertently lose it.


Data migrations separated from schema migrations

For testing purposes, I need to be able to execute the schema migrations separately from the data migrations. Is it possible in Phinx?
What I want to do is to have a separate data migrations folder, so on my testing environment I would apply only the schema migrations (for testing purposes, tables should be empty and only populated by fixtures), but on my staging and production environments the data migrations would be applied as soon as the schema migrations are done.
Has anyone solved this?

Closing for lack of activity on this support question. Best to join e.g. slack for some real time feedback on support issues.


Add free-text explanation boxes to instructor training application form

From @tracykteal:

On 'previous experience in teaching' and 'in training', I'd like people to put in text explaining what they've done, rather than just the multiple choice. So maybe have the multiple choice, and then have an 'explain' like in https://docs.google.com/forms/d/1O5Mx22vCKueDkCgCPrpXuuLVcR30Mzyz_7kLahD8gYA/edit

Duplciates #873.


[5.5] WIP | Separate PATCH and PUT routes in requests

Resource Controller are a great feature of Laravel: the update route responds to PUT and PATCH methods which in most case fine.
However in many cases we want to be able to provide different feature depending on the HTTP verb:

a full entity update with PUT
a partial entity update with PATCH

More about PUT/PATCH differences:

http://weblog.rubyonrails.org/2012/2/26/edge-rails-patch-is-the-new-primary-http-method-for-updates/
PUT : http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.6
PATCH : http://tools.ietf.org/html/rfc5789

At the moment, we have to use some workarounds - one of them coule be:
Route::resource('posts', 'PostController', ['except' => ['update']]);
Route::patch('posts/{post}', '\App\Http\Controllers\PostController@patchUpdate');
Route::put('posts/{post}', '\App\Http\Controllers\PostController@putUpdate');

Other solutions might exist, with Route macros - In any case no easy out-of-the-box solution exists.

This PR introduces the following changes in resource routing:

The PATCH/PUT update route will not be generated anymore
A PUT route will be generated to ...\MyController@replace
A PATCH route will be generated to ...\MyController@update

TODO:

[ ] More tests on options
[x] Ensure ApiResource also work with patch
[ ] Provide an easy solution so that people migrating to 5.5can still use mixed PUT+PATCH routes

can't you just move the put or patch route above the resource route?  then you will hit this one first and it will fall through to the other one in the resource route.
Route::put('posts/{post}', 'PostController@putUpdate');  //will execute for the 'put' request
Route::resource('posts', 'PostController');  //will execute for the 'patch' request

Sure @browner12 there are workarounds - this is handy with one or two controllers, but when you have 30 of them...
I actually had a talk with some guys, I might update a bit this PR so that PUT and PATCH are now 2 separate routes / methods out of the box

How are you using them differently? I know they're popular in statically typed language frameworks to differentiate partial and complete updates, but PHP/Laravel doesn't have the same concerns.

yah, personally i've never had any real tangible reason to differentiate between the two. I'd be curious to hear your use case.

@BrandonShar @browner12 - actually there are LOTS of use case
I am always declaring an extra PATCH route in all of my projects for all my entities

Could you share an example? I don't mean to be difficult, I've just never used a patch route in a dynamic language framework because there isn't a technical need to differentiate partial and full updates on an entity.

yah, i'm in the same boat. I'm not doubting you, I'm actually curious what they are because I've never had a need for them.

IMO injecting the request on update and check the method using ''' isMethod ''' is an acceptable workaround for the edge cases, I don't see a reason for adding 200+ lines of code into the framework for this...

According to the HTTP Spec, PUT is replacing a full resource and PATCH is applying a delta, rather than replacing the entire resource.
To stay backwards compatible, how about we use update() for PATCH as it is right now, and replace() for PUT?

I like @tillkruss' suggestion of using replace() for PUT.

What is the difference though? We haven't seen an example yet of where this matters in a dynamic language.

@BrandonShar: I run into this issue mostly (if not exclusively) during API development, sometimes I need to differentiate between replacing and updating a resource. Having a 2nd method would allow me to skip a couple of if-statements in my controllers.

Could you provide a real example though? I understand the use case in theory, I just don't understand it in practice, especially not to a degree of changing established resource method names to accommodate it.
In a dynamic MVC framework, what is the difference between "replacing" an entity and "updating" an entity?

PUT is defined in Section 9.6 RFC 2616:

The PUT method requests that the enclosed entity be stored under the supplied Request-URI. If the Request-URI refers to an already existing resource, the enclosed entity SHOULD be considered as a modified version of the one residing on the origin server. If the Request-URI does not point to an existing resource, and that URI is capable of being defined as a new resource by the requesting user agent, the origin server can create the resource with that URI.

PATCH is defined in RFC 5789:

The PATCH method requests that a set of changes described in the request entity be applied to the resource identified by the Request-URI.

Example:
You have 3 users in the database.
[{ "id": 1, "name": "Josh" , "email"<EMAIL_ADDRESS>}, { "id": 2, "name": "Brandon" , "email"<EMAIL_ADDRESS>}, { "id": 3, "name": "Lucas" , "email"<EMAIL_ADDRESS>}]

By definition you can POST /users to create a fourth user, but you can also PUT /users/4 even though that resource doesn't actually exist and be treated as a POST and create the resource.
You by definition are supposed to also replace the whole resource on every request. So if you want to update the email of Josh to<EMAIL_ADDRESS>you would have to pass the whole resource, with email changed.
With a PATCH you can send a request to that resource that just has the following in the body:
{ "email"<EMAIL_ADDRESS>}

The use case of this is properly following the spec.

Again, I'm not having an issue understanding the theoretical applications of PATCH vs PUT so providing more theory isn't helpful. I don't disagree at all that W3 defines PUT as a complete update and PATCH as a partial update.
What I don't understand is what practical difference they have in a dynamic MVC framework and how separating these methods solves that. I have never once seen a need to separate them and I'm interested where you guys have. I would venture a guess that 100% of my update method usage should technically be PATCH. Redefining the method to http-verb relations in resource routes is a pretty big breaking change that I don't see a use case for.

The use case is following the spec... What else is there to say?

PATCH does follow the spec; it has all along. But, unless there's a good reason to separate out PUT and break backwards compatibility with apps consuming Laravel apis, I don't see why it should be.
It's fine that you don't have a real world example, I don't either. Let's wait and see if someone else does and discuss from there.

So this is now a PR for a change that will break the vast majority of Laravel applications to separate out a method that no one has shared a single example of how they would use?
I'd even be willing to discuss a hypothetical example of a use for this replace method at this point because I'm so confused at how 6 (at the time of this comment) people want this change. Eloquent doesn't even have functionality to handle a "replace" that I can think of.

@BrandonShar - no it won't break anything : see TODO 3)

yah, essentially the Eloquent side of this couldn't care less if it is updating or replacing.  either way it's generating a UPDATE table query.
while we all understand the spec related to PUT and PATCH, could somebody please just share one controller example where they use both methods, so we can better understand the use case for having both?

The spec has nothing to do with Laravel or Eloquent.
If I wanted my API to properly follow the Spec, I would be making a PUT to completely replace the entity, and a PATCH to just update a property on the entity.

But what would that PUT route actually do in practice; have you ever used one in the described manner?
PUT and PATCH have been used interchangeably for a long time due to either PATCH not existing or PATCH having poor support and because of that PUT doesn't really have any meaning beyond that in a JSON API. I brought up Eloquent because the concept of "replacing" doesn't exist in it, further complicating how this would even theoretically be used in a Laravel app.

@BrandonShar: This might help you understand it better: http://williamdurand.fr/2014/02/14/please-do-not-patch-like-an-idiot/

gahhh! we understand the theory, people.
@lucasmichot you said you have about 30 controllers that run into this where you need to separate them out. Can you please just share the reasoning behind one of them so we can understand if there is a real use case that justifies this relatively significant BC?
I'm not necessarily opposed to this, I just want to make sure it's justified.
And to be honest, the last paragraph of that article almost seems to argue against what you are proposing.

I'm confused at what is not understood here... Do we have to make an example application or something?
One replaces the whole entity, the other updates a partial of the entity...
There's no other use case that can be shown to help you understand it. Either you get it, or you don't. That's why we keep referring back to the spec.

Task

Column
Type
Default

id
int

task
varchar

completed
boolean
false

public function replace(Task $task, Request $request)
{
   $id = $task->id;
   $task->delete();
   $task = new Task;
   $task->id = $id;
   $task->fill($request->all());
   $task->save();
   $task->refresh();
   return $task;
}

public function update(Task $task, Request $request)
{
    $task->update($request->all());
    $task->refresh();
    return $task;
}

Example register
{
    "id": 4,
    "task": "Provide an example",
    "completed": true
}

Example request data:
{
    "task": "Provide another example"
}

 PATCH /tasks/4
Expected return
{
    "id": 4,
    "task": "Provide another example",
    "completed": true
}

 PUT /tasks/4
Expected return
{
    "id": 4,
    "task": "Provide another example",
    "completed": false
}

Just a quick example, I'm using it for this usecase, shouldn't be a problem if we provide an easy solution for ppl migrating...

Please show a replace method and an patch only update method with real code that you would put in a real app. Both @lucasmichot and @tillkruss have said they've run into this routinely when developing so someone should have a single example of what the replace method looks like and what the patch only version of the update method looks like.
I promise all of you, I understand what the http specs say about put and patch. And @joshmanders, the article that @tillkruss posted and you thumbs up'd states that the exact example you used for patch (and the one we've all been discussing) is wrong so you may want to re-read it. It seems like @tillkruss disagrees with the definition of PATCH as a partial update that we're all using so seeing examples will help clarify that we're all picturing the same thing.

Thanks for the example @fernandobandeira, that makes this discussion much easier.
I guess this is more or less what I expected a replace to look like: a delete followed by a create where the primary key is specified. If this is the pattern the rest of you are using in nearly every API, I suppose I just have to agree to disagree.
For this use case, would you expect eloquent to fire any after delete or after create hooks? Or should it fire it's updating hooks?

Discussion is going on in laravel/internals : https://github.com/laravel/internals/issues/694