documentation: Add /help article for supported browsers

Created new /help article for supported web browsers and updated
links in the /apps page as well as the unsupported-browser template
and the help/set-up-your-account article.
Decided on a simple straight-forward text that will not need to be
updated regularly. Similar information pages on Slack and Discord
(see links) are geared toward both OS as well as browser support,
which could be another way to address this issue, but could possibly
require more content maintenance.

Slack
Discord

In addition to lint and test suites, did a visual check of links
in the development environment (see below). I do not have Windows
or Internet Explorer, so I was unable to visually check the updates
to the unsupported-browsers template.

Fixes #14732

@laurynmm is this ready to be marked as no longer a draft?

Yes! I had forgotten about that. It's the first time I've used that feature. Thanks!

@timabbott - This seems to be good to go now as @alya gave it another review yesterday. Let me know if I need to make any other changes to the pull request so that it can be merged. Thanks!

@timabbott should we get this merged?

Pushed an update to this to cover the other content I wanted -- pinned tabs and cross-protocol desktop apps, with some warnings about the latter.
I think this is probably good enough for this detail, tagged to merge once CI passes, thanks @laurynmm!


Fix plugin id

Set the plugin id to @jupyterlite/xeus-python-kernel-extension:kernel to avoid collisions with other xeus based kernels, which would otherwise result in plugin activation errors:

Probably we can update the other xeus kernel that has the same plugin id.


Enchancement: Show reason of skipping a test

Currently, the blue "Skip" label is just a static label. It would be useful if the label could be expanded to show reason for skipping.

Good idea. I've attempted an implementation in #32.

Implemented and released under version 1.2. Thanks @JamesMTSloan  you have done a lot of work for this project


Minimal errata fixes in documentation

Just a couple of typos and an error on a comment that I spotted while working on #423 .

bors r+


Issue6246-Let statement should rewrite rhs with comments after equal sign

Pull Request Template
Checklist

[x] Confirmed that cargo test passes

Related Issues/PRs
https://github.com/rust-lang/rustfmt/issues/6246
Changes
The problem in 6246
fn main() {
    let foo =
    // 114514
    if true {
        1919
    } else {
        810
    };
}

Rustfmt doesn't seem to account for comments between the = sign and the if expression. I solve it by checking the existence of a comment span and insert it back after rewrite.
Testing
added a test case tests/source/issue-6246.rs

Haven't had a chance to review this yet (and likely won't for a little while), but I wanted to point out that https://github.com/rust-lang/rustfmt/pull/5501 is already open to address the same issue. Didn't catch that until recently. This one is much simpler, but it might not be accounting for multi-line comments or block comments.

Closing my PR as https://github.com/rust-lang/rustfmt/pull/5501/files is addressing the same issue


Don't check swSrc for hardcoded injection point in wizard flow

R: @philipwalton
Fixes #2447
Using the wizard mode in the workbox-cli, there was previously a validation step that would check to see if your swSrc file contained the manifest injection point. This check wasn't updated for Workbox v5, so it was still looking for precacheAndRoute([]).
There's already runtime validation that will check for the proper injection point when you run workbox injectManifest after you complete the wizard step. That runtime validation will work properly if you happen to override the injectionPoint configuration option, which this previous  hardcode assertion didn't support.
So I'm just dropping the assertion from the wizard flow entirely.

so we can not use workbox now...Please release a verson!

In the meantime, you can also work around this issue by just adding in
// precacheAndRoute([])

commented out in your swSrc file.


Support for nested function resolution

When a property-function returns another function, and so forth, we should do nested resolution, while reusing this for the original function call.

Implemented and released in v0.4.1
Now property-functions of any depth are resolved reclusively.


(chore): Added Card Grid Component for the Fourth theme

Signed-off-by: Abhijay Jain<EMAIL_ADDRESS>Description
Added Card Grid Component for the Fourth theme
Resolves #387
Screenshots (In case of UI changes):

Desktop  View

Types of changes

[x] New feature (non-breaking change which adds functionality)

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] All new and existing tests have passed and it does not give any unexpected error for the same.

Merge #394 this PR before, that this one


Mongo-SideCar unable to connect to Mongodb

$ kubectl logs mongo-0 -c mongo-sidecar

><EMAIL_ADDRESS>start /opt/cvallance/mongo-k8s-sidecar
> forever src/index.js

warn:    --minUptime not set. Defaulting to: 1000ms
warn:    --spinSleepTime not set. Your script will exit if it does not stay up for at least 1000ms
Using mongo port: 27017
Starting up mongo-k8s-sidecar
The cluster domain 'cluster.local' was successfully verified.
Error in workloop { MongoError: failed to connect to server [<IP_ADDRESS>:27017] on first connect [MongoError: connect ECONNREFUSED <IP_ADDRESS>:27017]
    at Pool.<anonymous> (/opt/cvallance/mongo-k8s-sidecar/node_modules/mongodb-core/lib/topologies/server.js:336:35)
    at emitOne (events.js:125:13)
    at Pool.emit (events.js:221:7)
    at Connection.<anonymous> (/opt/cvallance/mongo-k8s-sidecar/node_modules/mongodb-core/lib/connection/pool.js:280:12)
    at Object.onceWrapper (events.js:326:30)
    at emitTwo (events.js:135:13)
    at Connection.emit (events.js:224:7)
    at Socket.<anonymous> (/opt/cvallance/mongo-k8s-sidecar/node_modules/mongodb-core/lib/connection/connection.js:187:49)
    at Object.onceWrapper (events.js:324:30)
    at emitOne (events.js:125:13)
  name: 'MongoError',
  message: 'failed to connect to server [<IP_ADDRESS>:27017] on first connect [MongoError: connect ECONNREFUSED <IP_ADDRESS>:27017]' }

Hi deploying the example statefulset to azure seems to give me the following error. Any ideas? Is there any specific configuration required for azure?
I am using the azure storage config as mentioned:
azure_ssd.yaml
I also attempted to add the following environment variables:
- name: MONGO_SIDECAR_POD_LABELS
   value: "role=mongo,environment=test"
- name: KUBE_NAMESPACE
   value: "dev"
- name: KUBERNETES_MONGO_SERVICE_NAME
   value: "mongo"

So as of MongoDB 3.6, the default for MongoDB is to bind to localhost <IP_ADDRESS> which means it cannot accept the connection from the mongo-sidecar container by default.
To resolve set the bindip as a command option in the service file:
mongo-statefulset.yaml
Example:
containers:
        - name: mongo
          image: mongo
          command:
            - mongod
            - "--replSet"
            - rs0
            - "--bind_ip"
            - <IP_ADDRESS>
            - "--smallfiles"
            - "--noprealloc"
          ports:
            - containerPort: 27017


ProgressBar rendering artifacts

Repro: Just run the app, scroll in Preview tab item to ProgressBar's and wait.
https://github.com/wieslawsoltes/Avalonia/tree/7b90780404aa178a1e728c0acf764a73acb2a6ba/samples/ThemeEditor
Skia+OpenGL+Win7 x64

duplicate of https://github.com/AvaloniaUI/Avalonia/issues/1960

I've noticed that happening even without scaling on Skia/OpenGL/X11, so I don't think it's an exact duplicate.

does this happen on ImmediateRenderer too?

@jmacato #1960 shows what happens on immediate
its different effect, its not related to dpi as 1960 incorrectly implies.

this issue may be fixed in pr #2002

Just taken another look at this and it seems to still be an issue. Problem seems to occur for me only when scaling is != 100% on both skia and D2D backends.

https://github.com/AvaloniaUI/Avalonia/issues/1960


Appstudio update mvp-test-component

Pipelines as Code configuration proposal

Pipelines as Code CI/mvp-test-component-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
8 seconds
init

✅ Succeeded
25 seconds
clone-repository

✅ Succeeded
1 minute
build-container

✅ Succeeded
22 seconds
sanity-inspect-image

✅ Succeeded
21 seconds
deprecated-base-image-check

✅ Succeeded
21 seconds
clair-scan

✅ Succeeded
56 seconds
clamav-scan

✅ Succeeded
10 seconds
sbom-json-check

✅ Succeeded
12 seconds
sanity-label-check

✅ Succeeded
12 seconds
sanity-optional-label-check

✅ Succeeded
6 seconds
show-summary


Added in Find and Filter parts in Appendix G of DG, updated PPP

Pull Request Test Coverage Report for Build 449

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 63.747%

Totals

Change from base Build 448:
0.0%

Covered Lines:
1994

Relevant Lines:
3128

💛  - Coveralls


feat(dashboard): resizable panes rewritten in react

Overview
This is a rewrite of the resizable pane feature from #162 #187 from Stencil to React.
Legal
This project is available under the Apache 2.0 License.

Please recreate this pull request off the new head, a history rewrite was pushed. Closing. You should be able to cherry-pick your commits onto the new head.


Invalid config undetected.

Alertmanager is starting fine without any errors about the group_interval in the global section.
./alertmanager -version
alertmanager, version 0.4.2 (branch: master, revision: 9a5ab2fa63dd7951f4f202b0846d4f4d8e9615b0)
  build user:       root@2811d2f42616
  build date:       20160902-15:33:13
  go version:       go1.6.3

global:
  resolve_timeout: 2m
  group_interval: 1m   # this is invalid config

  hipchat_auth_token: 'xxxx'

# The root route on which each incoming alert enters.
route:
  group_by: ['cluster']
  group_interval: 1m   # this is valid config
  receiver: team-hipchat

  routes:
  - match_re:
      severity: hipchat
    receiver: team-hipchat

receivers:
- name: 'team-hipchat'
  hipchat_configs:
  - room_id: 123456
    send_resolved: true
    message_format: html
    notify: true

This appears to be fixed in 0.6.0.
I couldn't reproduce issue with the provided config


Sort.ts is incorrectly generated with 24.4 alpha7

Describe the bug
With 24.4 alpha5 and 2.5, Sort.ts is generated as
interface Sort {
    orders: Array<Order_1 | undefined>;
}

but with alpha7 it is
interface Sort {
    orders?: Array<Order_1 | undefined>;
}

It seems like https://github.com/vaadin/hilla/blob/5d05a07cdcb39874449da399bcd59dbb60476084/packages/java/runtime-plugin-transfertypes/src/main/java/com/vaadin/hilla/mappedtypes/Sort.java#L27 nonnull here is ignored
Expected-behavior
As in alpha5
Reproduction
Use Sort
System Info
24.4 alpha7

This is introduced by https://github.com/vaadin/hilla/pull/2136

Fixed by https://github.com/vaadin/hilla/pull/2152


Description of "Default Caching" Functionality?

I've read through a number of Docs, GitHub issues and StackOverflow questions but I have not been able to identify the logic for caching (DLL caching I suppose to be more specific) in Blazor.
My overall feedback (in the form of a request) is to put a description of how to cache-bust the cached runtime DLLs? In the below passage, you mention the default behavior of caching the .dll & .wasm files, but I don't know what that behavior is:

BlazorCacheBootResources also disables Blazor's default behavior of caching the .dll, .wasm, and other files based on their SHA-256 hashes because the property indicates that the SHA-256 hashes can't be relied upon for correctness. Even with this setting, the browser's normal HTTP cache may still cache those files, but whether or not this happens depends on your web server configuration and the cache-control headers that it serves.

Essentially, if I publish / deploy a new version of the application, what is the mechanism to trigger redownload of the runtime code (.wasm/.dll)s.

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

ID: be59faf1-5a20-b7e9-19ff-06589023bb15
Version Independent ID: 250e7458-3c1d-0117-261d-c03ac136f16a
Content: Host and deploy ASP.NET Core Blazor WebAssembly
Content Source: aspnetcore/blazor/host-and-deploy/webassembly.md
Product: aspnet-core
Technology: aspnetcore-hostdeploy
GitHub Login: @guardrex
Microsoft Alias: riande

Hello @taylorchasewhite ... After confirming that an issue hasn't already been created (open or closed ... search both), open this for the product unit at ...
https://github.com/dotnet/aspnetcore/issues
I don't think that the remark is too cryptic ... browsers are going to honor cache-control headers. Fine. Your question is an excellent follow-up: What does the PU recommend for cache-busting approach(es)? Can we enhance this coverage with further guidance on it?
Please add ...
cc: @guardrex https://github.com/dotnet/AspNetCore.Docs/issues/24748

... to the bottom of your opening comment so that I can follow along. Normally, I close these until I hear their response. In this case tho, I'm almost certain that we can improve the guidance. I'll set it up as a P2 - Medium Priority issue for the time being. I'll take care of this if you'll add my ping line ☝ to your opening issue over there ... or if you find an existing open issue that you can comment on (add me to your comment). They might already be planning something. I'd like to follow that if you find such an open issue.

Sounds good--I will take these steps. Thanks Luke!

That's perfect. I think that they'll provide helpful guidance 🤞, then I'll likely be able to turn it into a doc update. I'll keep an 👁 on it, and you can let this docs issue close automatically when the docs PR merges later.

Sounds good, thanks!

Ok ... that's what Javier recommends. I'll see if I can work something up from his notes on the PU issue. I'll get to this as soon as I can, but it could take anywhere from a few weeks to a few months given the workload. Until then, this open issue is available to doc readers from the "View all page feedback" link at the bottom of the topic. Thanks for asking about this scenario.

For sure! Thanks @guardrex -- I'm going to deep dive through the comments on that other thread and I'll post back if I figure anything else out. Thanks!


Added new schema for WorldBank priority 0 import

Added new schema for the first set of the large scale WorldBank import.

Thanks, Ian. Due to sync problems, we're just adding schema to g3 now. I've sent out a CL and it should be in soon.


optimize Dockerfile

Description
cc @epifanio @ricardogsilva
Carrying on from https://github.com/geopython/pycsw/pull/613#pullrequestreview-407505149, find ways to speed up build, reduce image size, and testing.
Environment

operating system:
Python version:
pycsw version:
source/distribution

[ ] git clone
[ ] DebianGIS/UbuntuGIS
[ ] PyPI
[ ] zip/tar.gz
[ ] other (please specify):

web server

[ ] Apache/mod_wsgi
[ ] CGI
[ ] other (please specify):

Steps to Reproduce
NA
Additional Information
NA

@ricardogsilva the following test builds in 40 seconds but creates an image of 334MB.  Any ideas to reduce the size?
FROM python:slim-buster
LABEL maintainer="massimods<EMAIL_ADDRESS>
ARG PYCSW_HOME=/tmp/pycsw

ENV PYCSW_CONFIG=/etc/pycsw/pycsw.cfg

COPY . ${PYCSW_HOME}

RUN apt-get update && apt-get install -y ca-certificates

RUN pip3 install --upgrade pip setuptools \
  && pip3 install wheel \
  && pip3 install gunicorn \
  && pip3 install --requirement ${PYCSW_HOME}/requirements.txt \
  && pip3 install --requirement ${PYCSW_HOME}/requirements-standalone.txt \
  && pip3 install --requirement ${PYCSW_HOME}/requirements-pg.txt

ADD docker/pycsw.cfg ${PYCSW_CONFIG}
ADD docker/entrypoint.py /usr/local/bin/entrypoint.py

WORKDIR ${PYCSW_HOME}

RUN pip3 install . \
  && useradd -ms /bin/bash pycsw \
  && cp -r ${PYCSW_HOME}/tests /home/pycsw \
  && chown -R pycsw:pycsw /home/pycsw/* \
  && rm -rf /usr/lib/python3*/*/tests \
  && rm -rf /usr/lib/python3*/ensurepip \
  && rm -rf /usr/lib/python3*/idlelib \
  && rm -f /usr/lib/python3*/distutils/command/*exe \
  && rm -rf /usr/share/man/* \
  && rm -fr ${PYCSW_HOME} \
  && find /usr/lib -name  "*.pyc" -o -name "*.pyo" -delete

WORKDIR /home/pycsw

EXPOSE 8000

USER pycsw

ENTRYPOINT [ "python3", "/usr/local/bin/entrypoint.py" ]

@tomkralidis I'm a bit swamped at the moment, but if you can give me a couple of days to look into it, I hope to be able to provide some assistance

@tomkralidis see my PR #615 for my take on this.
I wasn't able to slim the image too much, currently with 311MB, but IMHO it would be better for pycsw to be on a debian base. I leave it up to your consideration and lets discuss this further, if needed.


npm run dev doesn't work after initializing a project

Note: to fix this, I simply moved the "electron" dependency in package.json to 'dependencies' rather than 'devDependencies'.
Describe the issue / bug.
After initializing a project based on the documented instructions, npm run dev doesn't work as expected:
 ERROR in ./src/renderer/components/LandingPage.vue
  Module Error (from ./node_modules/eslint-loader/index.js):

    ✘  https://google.com/#q=import%2Fno-extraneous-dependencies  'electron' should be listed in the project's dependencies, not devDependencies
    src\renderer\components\LandingPage.vue:40:9
            require('electron').shell.openExternal(link);
             ^

  ✘ 1 problem (1 error, 0 warnings)

  Errors:
    1  https://google.com/#q=import%2Fno-extraneous-dependencies
   @ ./src/renderer/App.vue?vue&type=script&lang=js& (./node_modules/babel-loader/lib!./node_modules/vue-loader/lib??vue-loader-options!./src/renderer/App.vue?vue&type=script&lang=js&) 3:0-51 8:17-28
   @ ./src/renderer/App.vue?vue&type=script&lang=js&
   @ ./src/renderer/App.vue
   @ ./src/renderer/main.js
   @ multi ./.electron-vue/dev-client ./src/renderer/main.js
  Child html-webpack-plugin for "index.html":
           Asset      Size  Chunks  Chunk Names
      index.html  1.38 MiB       0
      Entrypoint undefined = index.html
      [./node_modules/html-webpack-plugin/lib/loader.js!./src/index.ejs] 1.14 KiB {0} [built]
      [./node_modules/lodash/lodash.js] 527 KiB {0} [built]
      [./node_modules/webpack/buildin/module.js] (webpack)/buildin/module.js 497 bytes {0} [built]

How can I reproduce this problem?
Follow the instructions described in the documentation (I'm on Windows 10), and run npm run dev after initializing the project.
If visual, provide a screenshot.

Tell me about your development environment.

Node version: 8.11.2
NPM version: 6.7.0
vue-cli version: (if necessary)
Operating System: Windows 10

The same problem occurs


Is it possible to build a filter that get the body content and save as header per request?

Please if anyone know tell me!

You can read the request body and save it as a response header.

I need to direct a request (match) based on body content. Example: If client id ends with 0 or 1 or 2 etc. (regex) the route must be forwarded to a configured cluster. This cluster can be queried maybe in some form of metadata.
My idea was to read the body field (client id) and add in request header (in the hope) I could match the client id as header since I did not found anything about matching body content.

I don't think that is possible. By the time you access request body the headers have been already sent to upstream and hence routing has been decided.

 I decided to go with a filter in Lua and it was totally possible! Thanks for your time =]


[Bug]: deleteOldCache cron fails with more than 1k keys

Describe the bug
When the deleteOldCache cron runs, and there's more than 1k keys to delete, the Worker will fail with the following exception:
{
  "Name":"Error",
  "Message":"delete: The number of keys in the request must be between 1 and 1000 inclusive. (10027)",
  "TimestampMs":1692154867482
}

This doesn't appear to be documented here https://developers.cloudflare.com/r2/api/workers/workers-api-reference/#bucket-method-definitions, but seems to match the documented 1000 limit for list.
To Reproduce
Steps to reproduce the behavior:

Create more than 1k keys to be deleted
Wait for cron to run

Expected behavior
No exceptions would be thrown.

@colinmcdonald22 thanks for reporting this!
Didn't realise this was a limitation, especially since it doesn't seem to manifest in miniflare locally at all; curious 🤔 .
Looking at the cron right now, it will likely fall over if there are a huge number of objects, and it will naturally bump up against the limits you saw. I'm working on modifying the cron so it can handle potentially 100,000+ objects, hold tight, fix is coming soon.

@colinmcdonald22 thanks for reporting this! Didn't realise this was a limitation, especially since it doesn't seem to manifest in miniflare locally at all; curious 🤔 .
Looking at the cron right now, it will likely fall over if there are a huge number of objects, and it will naturally bump up against the limits you saw. I'm working on modifying the cron so it can handle potentially 100,000+ objects, hold tight, fix is coming soon.

Sounds good, thank you. For reference here's test code I used to confirm before opening the issue:
export interface Env {
  TEST_BUCKET: R2Bucket;
}

export default {
	async fetch(request: Request, env: Env, ctx: ExecutionContext): Promise<Response> {
        	const keys = Array(1005).map((_, idx) => idx.toString());
        	await env.TEST_BUCKET.delete(keys);
        	return new Response('Deleted.');
	}
};

and
name = "r2-test"
main = "src/worker.ts"
compatibility_date = "2023-08-07"
r2_buckets  = [
  { binding = "TEST_BUCKET", bucket_name = "test-bucket", preview_bucket_name = "test-bucket" }
]

This example does work locally (wrangler dev), but does not work when actually deployed to Cloudflare

This example does work locally (wrangler dev), but does not work when actually deployed to Cloudflare

Yup I found the same thing. I'll likely raise a few issues in the miniflare and docs repository once I'm done fixing this. Local dev should match prod in an ideal world.

@colinmcdonald22 The PR I'm about to merge has been tested with a bucket that contains over 2000 objects. The issue should be resolved once it's merged 👍

@colinmcdonald22 The PR I'm about to merge has been tested with a bucket that contains over 2000 objects. The issue should be resolved once it's merged 👍

Perfect, just deployed the new version to our account. Really appreciate the quick response + fix time here! 🎉


[Bug] FormsModule and binding

Version
last version
Reproduction link
https://github.com/creativetimofficial/black-dashboard-angular/issues/6
Operating System
Windows 10
Device
Laptop
Browser & Version
Chrome lastest
Steps to reproduce
Add FormsModule in components.module.ts
Add a form
bind with a ts variable
"core.js:8046 Can't bind to 'ngModel' since it isn't a known property of 'input'."
What is expected?
Correct binding
What is actually happening?
I've added page in pages folder and this page is a form. This form cannot accept any binding "core.js:8046 Can't bind to 'ngModel' since it isn't a known property of 'input'." whereas I've added FormsModule in NgModule on components.module.ts ...

Solution
Additional comments

Hi @gdidelot,
Thank you for working with our products.
Can you please open this issue to the official Black Dashboard Angular repo (https://github.com/creativetimofficial/black-dashboard-angular)? In this way, everyone having this problem with the angular version will see it there.
Thank you,
Rares


Go service hangs when trying to "Run Without Debugging"

Bug Description

vscode, macOS (m1), Go service in a devcontainer.

Trying to start the service with "Run Without Debugging" simply hangs on:
Starting: /go/bin/dlv dap --listen=<IP_ADDRESS>:41171 --log-dest=3 from /workspaces/service-name
DAP server listening at: <IP_ADDRESS>:41171

"Start Debugging" however, works and service bootstraps successfully.
I've managed to narrow this down to the dlv v1.21.1 package, downgrading to v1.21.0 solves the hang.
mirrord.json -
{
    "target": "deployment/service-name/container/service-name",
    "accept_invalid_certificates": false,
    "feature": {
        "network": {
            "incoming": {
                "mode": "steal",
                "ignore_localhost": true
            },
            "outgoing": {
                "ignore_localhost": true
            }
        },
        "fs": "read",
        "env": true
    },
    "pause": true,
    "agent": {
        "ephemeral": true,
        "privileged": true
    }
}

Steps to Reproduce

Open repository in vscode's devcontainer
Our devcontainer's Dockerfile includes the following

RUN go install -v golang.org/x/tools/gopls@latest && \
    go install -v github.com/uudashr/gopkgs/v2/cmd/gopkgs@latest && \
    go install -v github.com/go-delve/delve/cmd/dlv@latest && \
    go install -v github.com/vektra/mockery/v2@latest && \
    go install -v github.com/golangci/golangci-lint/cmd/golangci-lint@latest && \
    go install -v github.com/fatih/gomodifytags@latest

Run "Run Without Debugging"

Backtrace
No response
Relevant Logs
No response
Your operating system and version
macOS m1
Local process
internal go service
Local process version
latest
Additional Info
No response

I believe this is an upstream bug in delve, that we aren't related to following review of Delve's changelog.
Checking their issue tracker and commit history since the release for fixes, I saw the following:
https://github.com/go-delve/delve/commit/f90ede46539400c5497cc0f0f5b6f676de72d40a
which seems to be very related to what user here experiences. Please try using compiled version post-that commit and let us know if it works for you.

User verified it works with Delve from master (known issue in 1.21.1)


Atomic create and start a test mock server

racetest is occasionally failing due to failure to start a test mock server.
I suspect this is due to two-phases creation of the server and starting it where port is being catched in  between those two calls.
Example of a failed racetest due to this can be found here with this error:
Server failed to listen 37252 listen tcp :37252: bind: address already in use

The PR is atomically creating a mock instance and starting it to avoid this.
Adds to #6730

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: ymesika
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: vadimeisenbergibm
If they are not already assigned, you can assign the PR to them by writing /assign @vadimeisenbergibm in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ymesika: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests.sh
f36c56fa55175cbd517e84393cd5436ea4cfaeef
link
/test e2e-simple

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test e2e-simple

Please move to master, not critical.

@ymesika: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
f36c56fa55175cbd517e84393cd5436ea4cfaeef
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ymesika: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
f36c56fa55175cbd517e84393cd5436ea4cfaeef
link
/test istio-unit-tests

prow/istio-presubmit.sh
f36c56fa55175cbd517e84393cd5436ea4cfaeef
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ymesika: PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Re-opened as #7481


When would the payload value ever not be a JsonElement?

When I decode the token, I get back a payload that's a Dictionary<string, object>.  When would the value ever not be of type JsonElement?

With the change from System.Text.Json it seems to be always the case unless you use a custom IJsonSerializer.

Can we type it as such then to make things easier?

I would have to take a look into in a spare time, but feel free to propose the change in a PR


[WIP][spark] Use paimon hash function to repartition when writing

Purpose
to #3651
Tests

API and Format

Documentation

This PR can avoid data skew, but it will introduce the following two problems,  close it now:

the writing performance is several times slower with the same resources.
due to the use of rdd, the spark UI cannot display sql correctly

Perhaps we should look for a solution to this problem by sticking with dataframe.


auth_time in id_token does not conform to OIDC standard

I've been having some trouble with the package oidc-client-ts
I've been receiving the error "" upon renew of the token. The package expects upon token renew the auth_time of the new id_token to be the exact same as the auth_time of the first issued id_token as per spec: https://openid.net/specs/openid-connect-core-1_0.html#RefreshTokenResponse
It seems Rauthy sends the time of authentication as the auth_time instead of the time of initial authentication when SESSION_LIFETIME is not defined.
https://github.com/sebadob/rauthy/blob/bd47f42d1d0b97ee4760efbb26ebbf22af5aee94/src/service/src/token_set.rs#L228
For reference, I've been using the Admin account on version 24.1 and 25.0 sqlite docker image.
How much work would it be to implement the 'more accurate time' as describe in code comments for the id token creation?

Thanks for the issue.
I am currently in the middle of a big cache migration under the hood, but I had a quick look. Yes it's true, that it will always re-calculate instead of re-using the original auth_time when it's a refresh. I will fix this.
The amount of work is not too big. I will probably finish the cache migration today (hopefully) and then can fix this.

I build a nightly image which includes the fix. You can test with the tags

0.26.0-20240905
0.26.0-20240905-lite

This nightly image also includes a pretty big internal migration of the cache layer, so if you stumble about any issues in this regard, please let me though. I haven't found any problems though so far.

Wow! Initial usage of the nightly seems to completely solve the problem I'm having; thanks so much.
The alternate solution I had come up with last night was to make the token validity exactly 60 seconds longer than the SESSION_LIFETIME environment variable. Very niche and very specific to the package I'm using; which refreshes the token 60 seconds before it expires... :)

Thanks for the feedback.
I already had the changes to get a 100% correct auth_time from a few releases ago. I just had to do these changes and fixes in a few steps and it has not been done in this last instance yet. I also added an integrations test for make sure the auth_time will always be properly handled in refresh scenarios.


add EquateString to cmpopts

I found myself needing this simple function that just compares the string value of two Stringer-compatible objects:
cmp.Comparer(func(x, y fmt.Stringer) bool { return x.String() == y.String() })

I propose adding this to cmpopts as e.g. EquateString.

Thanks for the proposal.
Comparing on the String method is generally considered poor practice since many types do not have documented guarantees of what the String method even means. For example, regexp.Regexp.String does specify that the String method returns source regexp, while reflect.Type.String warns against comparing on the String method. Most types follow the later model where String is intended as human debugging aid and not as a mechanism for semantic interpretation.
Also, a helper function like this will likely overly match on too many types since many types have a String method, leading to this helper option having a high probability of conflicting with another option.


SSH key forwarding

REMOTE-SSH extensions does not allow ssh key to be forwarded even if forwarding is specified in ssh config on local host.

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

x11 forwarding for vscode (#49771)

that is not related


CLOUDSTACK-8798 Fixed the vrrp virtual ip config in case of rvr enabl…

Fixed the vrrp virtual ip config in case of rvr enabled isolated networks.
changed the CsRedundant.py to bring down the public interface when rvr changes state to
backup. Also fixed vrrp authentication for isolated networks.
This fix dose not effect the vpc networks. it is only meant for rvr isolated networks.
manullay deployed a vm in rvr enabled isolated network and ran the tests below.
nosetests --with-marvin --marvin-config=/marvin-config test/integration/component/test_redundant_router_services.py
Test redundant router internals ... === TestName: test_enableVPNOverRvR | Status : SUCCESS ===

Ran 1 test in 633.336s
nosetests --with-marvin --marvin-config=/marvin-config test/integration/component/test_redundant_router_cleanups.py
Test network garbage collection with RVR ... === TestName: test_network_gc | Status : SUCCESS ===
ok
Test restarting RvR network without cleanup ... === TestName: test_restart_ntwk_no_cleanup | Status : SUCCESS ===
ok
Test restart RvR network with cleanup ... === TestName: test_restart_ntwk_with_cleanup | Status : SUCCESS ===

Ran 3 tests in 2120.263s

Hey @bvbharatk
Thanks, dude! I really loved the test report! :)
LGTM :+1:
Cheers,
Wilder

Minor issues, otherwise code changes look alright

@bhaisaab , should we wait for a new commit from @bvbharatk on this PR before merging it?
Cheers,
Wilder

I will merge this, since it got 2 LGTM, and will change the if as suggested by Rohit in my next PR that will touch the python files.

cool


Name Conflict on TypeScript

Hi.
I'm using menubar in TypeScript and found an issue.
When I import menubar as below,
// Definition in lib.d.ts
declare module "menubar" {
    function create(opts: Object): any;
    export = create;
}

// ...

// main.ts
import * as menu from 'menubar';

I got an error
browser/main.ts(3,23): error TS2497: Module '"menubar"' resolves to a non-module entity and cannot be imported using this construct.

It seems that menubar is already defined in TypeScript standard lib.d.ts.  It is defined as global variable and leads to above error.
Is there any way to solve this problem?
Now I avoid this issue in dirty way but it disables type check for whole menubar module
// Now using JS style require...
var menu = require('menubar');

hmm I actually have no idea sorry, but feel free to leave this issue open
in case someone else does
On Thursday, July 23, 2015, Linda_pp<EMAIL_ADDRESS>wrote:

Hi.
I'm using menubar in TypeScript and found an issue.
When I import menubar as below,
// Definition in lib.d.tsdeclare module "menubar" {
function create(opts: Object): any;
export = create;
}
// ...
// main.tsimport * as menu from 'menubar';
I got an error
browser/main.ts(3,23): error TS2497: Module '"menubar"' resolves to a non-module entity and cannot be imported using this construct.
It seems that menubar is already defined in TypeScript standard lib.d.ts
https://github.com/Microsoft/TypeScript/blob/a24aa6f57d281bafd3535f0f4c3f492364a8b4d6/bin/lib.d.ts#L16369.
It is defined as global variable and leads to above error.
Is there any way to resolve this problem?
Now I avoid this issue in dirty way but it disables type check for whole
menubar module
// Now using JS style require...var menu = require('menubar');
—
Reply to this email directly or view it on GitHub
https://github.com/maxogden/menubar/issues/37.

--
Sent from my phone

@maxogden
Thanks.  I'll do that.
I write the current workaround for me.
I defined the menubar object as below.
declare class MenuBar implements NodeJS.EventEmitter {
    on(event: string, listener: Function): MenuBar;
    once(event: string, listener: Function): MenuBar;
    removeListener(event: string, listener: Function): MenuBar;
    removeAllListeners(event?: string): MenuBar;
    setMaxListeners(n: number): void;
    listeners(event: string): Function[];
    emit(event: string, ...args: any[]): boolean;

    addListener(event: string, listener: Function): MenuBar;
    tray: GitHubElectron.Tray;
    app: GitHubElectron.App;
    window: GitHubElectron.BrowserWindow;
}

And I use it for the returned value from create() as below.
var mainMenu: MenuBar = require('menubar')(menuConfig);

This is better than the workaround I showed previously because now mainMenu has a type.

Menubar has since been rewritten into TS. Typings come for free.


Add jersey to engage-ui build

This PR adds a dependency that's required in 15.x.  It also fixes a checkstyle issue in the header.
Your pull request should…

[x] have a concise title
[ ] ~close an accompanying issue if one exists~
[x] be against the correct branch
[ ] ~include migration scripts and documentation, if appropriate~
[x] pass automated tests
[x] have a clean commit history
[x] have proper commit messages (title and body) for all commits

Merging this in the interest of having a working build.


[Storage] Change policy ordering to after retry async

Try 2 of this work, need CI to know what to look for locally 😄

API change check
API changes are not detected in this pull request.

https://dev.azure.com/azure-sdk/public/_build/results?buildId=3808297&view=results
Now running in live to investigate further
/azp run python - storage - tests

/azp run python - storage - tests

Will resolve this after new OAuth changes


Packaging

Depending on the actual demographics of attendees who are interested to join this one, we might have to split this into language-specific ones, unless it is about something that can handle multiple languages like conda-forge.

The Blosc team is definitely interested in packaging, mainly for Python, but C is also interesting for us.

This is something I be interested in, from a mostly Python perspective. I'd be particularly interested in sharing experiences in automated deployment and ensuring the long term stability of releases.

Merged with #18


aravisGigE: allow setting trigger source

This is needed in I22 to configure the scan, if it's not generally useful, a custom I22 aravisGigE block can be used instead, without affecting others.

Codecov Report

Merging #318 (a4f597e) into master (f354fd8) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #318   +/-   ##
=======================================
  Coverage   92.60%   92.60%
=======================================
  Files         214      214
  Lines       11325    11325
=======================================
  Hits        10487    10487
  Misses        838      838

Continue to review full report at Codecov.

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


Add a minimum required RHEL version to docs

Update Readme to mention a minimum required RHEL version due to glibc and other libs.
Fixes #777

Coverage remained the same at 84.435% when pulling 48bb706624972836abc239462962eeed628c84c4 on itroyano:patch-14 into 05eb255ba65043048352a1a26d178306a6e99a51 on redhat-openshift-ecosystem:main.

coverage: 83.689% (-0.7%) from 84.435%
when pulling 48bb706624972836abc239462962eeed628c84c4 on itroyano:patch-14
into 05eb255ba65043048352a1a26d178306a6e99a51 on redhat-openshift-ecosystem:main.

coverage: 83.689% (-0.7%) from 84.435%
when pulling 48bb706624972836abc239462962eeed628c84c4 on itroyano:patch-14
into 05eb255ba65043048352a1a26d178306a6e99a51 on redhat-openshift-ecosystem:main.


responsiveness issue fixed in the forum page due to heading

Fixes #4395
Describe the changes you have made in this PR -
Fixed the responsiveness issue on the forum page

@VaibhavUpreti sir please review my PR, thanks.


Can we update NUnit from version 3.5 to 3.8?

The used NUnit version is about 2 years old, version 3.5.0. We currently are at 3.8.0.
I tried to fix it by changing this in FSharpSource.targets to see the effect on the tests, but it didn't seem to change the used NUnit in the output dir, so I guess there is not a "single point" where this is currently configured.
<NUnitVersion>3.8.0</NUnitVersion>
<NUnitFullVersion><IP_ADDRESS></NUnitFullVersion>

@abelbraaksma Is there anything specific we gain by updating?  I don't mind updating just historically I've found NUnit versions a bit of a PITA to update and just end up sticking to the same version if there's nothing specifically wrong with it

@abelbraaksma  It looks like these commits were used to last update to 3.5: https://github.com/Microsoft/visualfsharp/commit/db5aec23dfbc71d1dbec3aee0ef98af28a90f869 https://github.com/Microsoft/visualfsharp/commit/1f6b0f75c73fb6e485a304560b062013167744c2

@PatrickMcDonald, thanks. @dsyme, I still have "hanging" tests. They appear to hang on creation or invocation and this seems to be caused by the test driver or by the test framework. To exclude that it is caused by a bug in NUnit, I would like to update.
Besides, I believe that several features have been added that may be useful, like MaxTime, Combinatorial. Some existed earlier, but were buggy, it's more stable now.

OK, thanks

I've no problem doing this. Just need to know about procedure. If a PR would "in principle" be accepted, I wouldn't mind doing the work.

Yes, it would be accepted once all CI is green.  A lot of engineering improvements fall in this category :)

I'm closing this since there's nothing specific driving the need for this

I forgot about this one, but I agree to close it for now. Though it wouldn't be a bad idea to keep external references up-to-date, including NUnit, as bugs in those libraries are getting resolved which may make our work easier too.


Integrate natively into Anki application

Integrate as an Anki plugin.
Will required at least the following

[x] update license to be compliant
[x] Write code for optional replacement ankiConnector
[x] Figure out a way to correctly packages code
[x] upload to ankiWeb
[ ] Profit

apart from profit all done!


Navbar Visibility and Home Button Not Functioning Properly

Description: The following issues have been identified with the website's navigation bar:
Navbar Text Visibility on White Background: When scrolling to sections with a white background, the navbar text becomes invisible, making it difficult for users to navigate. This is likely a problem with the color contrast between the text and the background.
Home Button Not Functioning: Clicking the "Home" button on the navbar does not redirect the user to the homepage as expected. The button appears non-responsive.
Steps to Reproduce:
Scroll to a section of the page that has a white or light background.
Observe the navbar text becoming invisible.
Click on the "Home" button and notice that it does not redirect to the homepage.
Expected Behavior:
The navbar text should maintain visibility across all sections, regardless of the background color (use contrasting colors or a background for the navbar).
The "Home" button should be functional and direct users to the homepage when clicked.
Possible Solution:
Adjust the CSS to ensure that navbar text changes color based on the background it overlays, or add a background color to the navbar itself.
Fix the functionality of the "Home" button by ensuring the correct link or redirect is in place.
Screenshot:

Description: The following issues have been identified with the website's navigation bar:
Navbar Text Visibility on White Background: When scrolling to sections with a white background, the navbar text becomes invisible, making it difficult for users to navigate. This is likely a problem with the color contrast between the text and the background.
Home Button Not Functioning: Clicking the "Home" button on the navbar does not redirect the user to the homepage as expected. The button appears non-responsive.
Steps to Reproduce:
Scroll to a section of the page that has a white or light background. Observe the navbar text becoming invisible. Click on the "Home" button and notice that it does not redirect to the homepage. Expected Behavior:
The navbar text should maintain visibility across all sections, regardless of the background color (use contrasting colors or a background for the navbar). The "Home" button should be functional and direct users to the homepage when clicked. Possible Solution:
Adjust the CSS to ensure that navbar text changes color based on the background it overlays, or add a background color to the navbar itself. Fix the functionality of the "Home" button by ensuring the correct link or redirect is in place. Screenshot:

Explain,how you are going to fix the navbar issue


Group GitHub Actions dependency updates

Updates to GitHub Actions plugins tend to come in waves, e.g., when a bunch of
plugins are updated to a newer Node.js version. Make Renovate group the updates
together into single PRs to reduce clutter in git history.

Current dependencies on/for this PR:

main

PR #1377   👈

This comment was auto-generated by Graphite.


Allow disabling of module having errors (during it's installation or in hooks)

The current implementation has possible deadlock: if the module has errors, either in the helm templates or in hooks, the tasks are stuck in the queue and disabling the module in ConfigMap don't help, because of module tasks are not removed from the queue.
Proposed change: When the module becomes disabled (in ConfigMap, or by any other means) the following should happen (in the following order):

All informers should be stopped and all crontab bindings should be disabled, so no new tasks (possibly containing errors) will be added to the queue.
All existing module tasks should be removed from the queue.
Tasks associated with module disabling should be added (helm uninstall, and afterDeleteHelm hooks)

Error in enabled script can also cause this situation. #16


ddRive

Issue #156
Project title: Decentralised Drive
A decentralized application using hardhat and ethers.js and IPFS .
Project Description
A Decentralized file strong system in which user can store their files on IPFS network using his meta mask account and user can only access only their files using their own met mask account. All of this uploading and accessing operations will be stored on blockchain using smart contract.
We can also give access of our files other people just like drive with the help of share and owner just have to pass the sharing person public address so that they can access it.
A user can also see and remove hoe many people have access to files.
Text Stack used:
✅ Solidity
✅ Ethers
✅ React
✅ HardHat
✅ remix
✅ IPFS

can u please check once , as the file is not visible to me   Your PR is empty !

can u please check once , as the file is not visible to me Your PR is empty !

I think i am doing something wrong. I myself also cant see anything


added QHAdam optimizer and fixed tests

Adding the QHAdam optimizer which has shown promise on the fastai forums when combined with Lookahead

Not sure why the checks failed, I followed the steps here : https://forums.fast.ai/t/submitting-pr-to-fastai-v2/54146
And I ran notebook2script as below
~/fastai_dev/dev$ python notebook2script.py --fname 12_optimizer.ipynb
Yet I still get this error
!!! Diff between nbs and scripts
!!!Remember to run notebook2script.py or script2notebook.py
##[error]Bash exited with code '1'.

Thanks for the PR! I have one minor issue to fix before merging if you don't mind. Will look at why the diff produces something if the problem persists.

Comment addressed :)

Thanks!


Initial MachXO2 Database

Short of possible required bug fixes, this PR contains enough fuzzed bits to route to I/Os, to tiles, to SLICEs and to global routing. I think now is a good time to merge so that I can start tracking my changes on top of the main branch of prjtrellis-db (as well as prjtrellis itself).
cc: @daveshah1, any objections?

So far everything I have looked at looks good.
My usual preference is to merge the prjtrellis changes before the corresponding prjtrellis-db changes, but if you have a good reason to merge this PR first then that is also fine.

My usual preference is to merge the prjtrellis changes before the corresponding prjtrellis-db changes, but if you have a good reason to merge this PR first then that is also fine.

On the prjtrellis side of things I've already updated the db submodule to point to this commit :P. But I guess that doesn't matter because I'll have to switch .gitmodules back to point to this repo instead of my copy anyway.

Changes have been addressed. This should be ready for merging.


app_key inside config.php cannot be empty!

hello i am getting such an error "app_key inside config.php cannot be empty!" I will be glad if you help

Open config.php file inside your installation directory and fill in some random value for app_key.

Open config.php file inside your installation directory and fill in some random value for app_key.

if they're using linux with php installed they can run php {path to setup,txt} and it will automatically put a random value into config.php


Enable observers in development

Disabling the observers in development is non-obvious and can lead to confusion.
This commit makes sure the UpdateRouterObserver and UpdateSearchObserver also run in development.
A corresponding change in the Pinfile is upcoming.

:fireworks:


Sports teams in test split

Again thanks for sharing this work. The annotations look much improved over the original CoNLL. Especially sports teams that originally were not well labeled are now much better.
However, is seems that some sports teams in the test split are still labeled as LOC, but I think they should be ORG. For example, in the first few sentences we see a couple of instances like this:
SOCCER NN I-NP O
- : O O
JAPAN NNP I-NP I-ORG
GET VB I-VP O
LUCKY NNP I-NP O
WIN NNP I-NP O
, , O O
CHINA NNP I-NP I-LOC
IN IN I-PP O
SURPRISE DT I-NP O
DEFEAT NN I-NP O
. .  O O

Japan NNP I-NP I-LOC
coach NN I-NP O
Shu NNP I-NP I-PER
Kamo NNP I-NP I-PER
said VBD I-VP O
...

In these examples "CHINA", "Uzbekistan" and "Japan" should be ORG (the other teams "JAPAN" and "China" in this example are labeled as ORG).

Thanks for catching those problems in the first document of the test fold! I must confess that I went over that document by hand at least twice and managed to miss those additional corrections :-\
The instance of CHINA in the title being tagged LOC was due to there being conflicting manual corrections. The original tag for that token was PER. One file corrected it to LOC, and another corrected it to ORG. I've changed the audited files so that both change that tag to ORG.
The remaining corrections just weren't caught by our ensembles of models, and I guess our eyes skated over them while we were looking at the problems that were flagged by the models. Go figure.
I've fixed all of these in #39.
Here are the corrections for the first document in the test fold BEFORE those additional changes:

And here is the same file AFTER, with new corrections in red and the single modified tag in blue:

Please let us know if you see anything additional problems we missed!

Fixed in #39

@frreiss awesome, thanks for correcting this!


Composition is not working

The beer hops example is not working and not saving the beer object.

The beer hops example is not working and not saving the beer object.

The beer hops example is not working and not saving the beer object.


Server-side rendering: redirects create duplicate pages

{ path: '/from', redirect: { path: '/to' } },

When using vue-server-renderer, using a redirect in the router just sends the source of the "/to" page as if it were the "/from" page: this means that the same page can be accessed at both "/from" and "/to".
There doesn't seem to be a way to intercept it and send an HTTP redirect instead, which would be preferred, especially given that SEO is mentioned in the vue-server-renderer README!
Maybe the render stream could emit a redirect event instead, somehow?
Happy to help out, just not sure where to start.

After calling router.push(context.url) in your server entry, you can check router.currentRoute.redirectedFrom to see if the result is a redirect, and return a Promise rejection with code 301/302, similar to this. You can then handle that in your stream's error event: https://github.com/vuejs/vue-hackernews-2.0/blob/master/server.js#L95-L98.
The fact that you have to do it in an error event is less-than-ideal of course, and we will think about how to improve that.

Fantastic, that should do :+1:

If you were making an application based on hackernews, then there is a check in the file entry-server.js
line 18
if (fullPath !== url) {    return reject({ url: fullPath }) }
delete these lines


add libuv and cmocka test cases with file system on sim and qemu on CI

Summary
add libuv and cmocka test cases with file system on sim and qemu on CI
Impact
CI run
Testing
localhost

Please update this page: https://nuttx.apache.org/docs/latest/platforms/risc-v/qemu-rv/boards/rv-virt/index.html to include these new tests. Please include the steps to run these python scripts, the qemu parameters, etc

Please update this page: https://nuttx.apache.org/docs/latest/platforms/risc-v/qemu-rv/boards/rv-virt/index.html to include these new tests. Please include the steps to run these python scripts, the qemu parameters, etc

done.

Please fix these errors:
kernel/fs/cases/fs_eventfd_test.c: In function 'thread_func':
Error: kernel/fs/cases/fs_eventfd_test.c:50:12: error: cast from pointer to integer of different size [-Werror=pointer-to-int-cast]
   50 |       read((int)args, &eventfd01_buffer, sizeof(eventfd_t));
      |            ^
cc1: all warnings being treated as errors
make[2]: *** [/github/workspace/sources/apps/Application.mk:200: kernel/fs/cases/fs_eventfd_test.c.github.workspace.sources.apps.testing.testsuites.o] Error 1
kernel/fs/cases/fs_fsync_test.c: In function 'test_nuttx_fs_fsync02':
Error: kernel/fs/cases/fs_fsync_test.c:120:34: error: format '%d' expects argument of type 'int', but argument 3 has type 'size_t' {aka 'long unsigned int'} [-Werror=format=]
  120 |   syslog(LOG_INFO, "the bsize = %d\n", statfsbuf.f_bsize);
      |                                 ~^     ~~~~~~~~~~~~~~~~~
      |                                  |              |
      |                                  int            size_t {aka long unsigned int}
      |                                 %ld
cc1: all warnings being treated as errors
make[2]: *** [/github/workspace/sources/apps/Application.mk:200: kernel/fs/cases/fs_fsync_test.c.github.workspace.sources.apps.testing.testsuites.o] Error 1
kernel/fs/cases/fs_stream_test.c: In function 'test_nuttx_fs_stream03':
Error: kernel/fs/cases/fs_stream_test.c:270:61: error: format '%zi' expects argument of type 'signed size_t', but argument 4 has type 'int' [-Werror=format=]
  270 |                  "len = %zi != return value from fwrite = %zi",
      |                                                           ~~^
      |                                                             |
      |                                                             long int
      |                                                           %i
  271 |                  len, ret);
      |                       ~~~
      |                       |
      |                       int
Error: kernel/fs/cases/fs_stream_test.c:303:60: error: format '%zi' expects argument of type 'signed size_t', but argument 4 has type 'int' [-Werror=format=]
  303 |                  "len = %zi != return value from fread = %zi",
      |                                                          ~~^
      |                                                            |
      |                                                            long int
      |                                                          %i
  304 |                  len, ret);
      |                       ~~~
      |                       |
      |                       int
cc1: all warnings being treated as errors
make[2]: *** [/github/workspace/sources/apps/Application.mk:200: kernel/fs/cases/fs_stream_test.c.github.workspace.sources.apps.testing.testsuites.o] Error 1
kernel/time/cases/clock_test_timer03.c: In function 'test_nuttx_clock_test_timer03':
Error: kernel/time/cases/clock_test_timer03.c:126:39: error: format '%lld' expects argument of type 'long long int', but argument 3 has type 'int64_t' {aka 'long int'} [-Werror=format=]
  126 |       syslog(LOG_INFO, "expected = %lld escaped = %lld failed = %d",
      |                                    ~~~^
      |                                       |
      |                                       long long int
      |                                    %ld
  127 |              expected, escaped, failed);
      |              ~~~~~~~~
      |              |
      |              int64_t {aka long int}
Error: kernel/time/cases/clock_test_timer03.c:126:54: error: format '%lld' expects argument of type 'long long int', but argument 4 has type 'int64_t' {aka 'long int'} [-Werror=format=]
  126 |       syslog(LOG_INFO, "expected = %lld escaped = %lld failed = %d",
      |                                                   ~~~^
      |                                                      |
      |                                                      long long int
      |                                                   %ld
  127 |              expected, escaped, failed);
      |                        ~~~~~~~
      |                        |
      |                        int64_t {aka long int}
cc1: all warnings being treated as errors


Make parse_apicast_creds not mutating

The function parse_apicast_creds in utils is currently modifying the passed creds table.
I'd suggest to make it non-mutating, in case the original table needs to be reused somewhere in the code.

Agreed. It would be safer if that method did not mutate the table received in the parameters.
If XC is the only module used, it should be fine anyway, but it could be a problem when used in combination with other modules.


Trying to fix ollama server infinite loop:

Situation: I am having ollama get stuck in an infinite loop on ubuntu 22.04 with certain requests. It appears to die, with broken pipes not breaking out and I have to restart the service. When I say "die" I mean no further requests are handled. As the log at INFO level only logs when the request has been sent back, nothing is logged in this scenario.
My approach to solving it:
set OLLAMA_DEBUG=1 and look at the journalctl logs. I've set it in two places:
environment variable:
export OLLAMA_DEBUG=1
set | grep OLLAMA
OLLAMA_DEBUG=1

And in the [Service] of ollama.service
[Unit]
Description=Ollama Service
After=network-online.target

[Service]
ExecStart=/usr/local/bin/ollama serve
User=ollama
Group=ollama
Restart=always
RestartSec=3

Environment="PATH=/home/…<various paths>…:/snap/bin OLLAMA_DEBUG=1"

[Install]
WantedBy=default.target

Then I restarted the server successfully.
sudo systemctl daemon-reload
sudo systemctl restart ollama.service
Expected output: all the slog.Debug and greater requests logged
Observed: only INFO seem to be logged. But the GPU is busy so it's doing SOMETHING.
Anyone know how I can confirm that the debug flag is set correctly?
Or more to the point, anyone know how I can better diagnose the server's infinite loop? It only happens with a particular model, so maybe the GGUF config isn't quite right? It's calebfahlgren/natural-functions:latest

Does the loop respect systemd's RestartSec=3 setting?
You could diagnose by changing the ollama.service file and setting ExecStart=ollama serve to run a wrapper script instead, for example to hold the process running and/or dump its envvars.
To see a running processes' environment and check for debug flags, just read it from procfs:
cat /proc/$PID/environ | tr '\0' '\n' | less

Ah that's great running it directly both a) set the environment variable properly and b) I can now see level=DEBUG in the logs. I guess I'm not clear how to alter the ollama.service to set the environment variable properly.

It's very interesting it seems like instructor is generating prompts that even mistral:7b can't cope with, but more interestingly indeed in a way that causes ollama to barf. I get ollama to get stuck here, not returning at all.
time=2024-02-23T15:58:59.224Z level=DEBUG source=routes.go:1225 msg="chat handler" prompt="[INST] \n                As a genius expert, your task is to understand the content and provide\n                the parsed objects in json that match the following json_schema:\n\n                {'messages': {'items': {'$ref': '#/$defs/MessagePair'}, 'title': 'Messages', 'type': 'array'}}\n                \nHere are some more definitions to adhere too:\n{'MessagePair': {'properties': {'respectful': {'title': 'Respectful', 'type': 'string'}, 'nondisrespectful': {'title': 'Nondisrespectful', 'type': 'string'}}, 'required': ['respectful', 'nondisrespectful'], 'title': 'MessagePair', 'type': 'object'}}\n\n\n                As a genius expert, your task is to understand the content and provide\n                the parsed objects in json that match the following json_schema:\n\n                {'messages': {'items': {'$ref': '#/$defs/MessagePair'}, 'title': 'Messages', 'type': 'array'}}\n                \nHere are some more definitions to adhere too:\n{'MessagePair': {'properties': {'respectful': {'title': 'Respectful', 'type': 'string'}, 'nondisrespectful': {'title': 'Nondisrespectful', 'type': 'string'}}, 'required': ['respectful', 'nondisrespectful'], 'title': 'MessagePair', 'type': 'object'}} Generate 5 pairs of short instant messages, where each pair contains a non-disrespectful (respectful or neutral) message and a corresponding disrespectful message exemplifying 'Dishonesty'. [/INST]" images=0
[1708703939] slot 0 is processing [task id: 0]
[1708703939] slot 0 : in cache: 0 tokens | to process: 370 tokens
[1708703939] slot 0 : kv cache rm - [0, end)
[1708703939] Resampling because token 17158: ' Based' does not meet grammar rules
[1708703941] Resampling because token 12069: 'Please' does not meet grammar rules
[1708703941] Resampling because token 12069: 'Please' does not meet grammar rules
[1708703941] Resampling because token 12069: 'Please' does not meet grammar rules
[1708703941] Resampling because token 12069: 'Please' does not meet grammar rules
[1708703941] Resampling because token 12069: 'Please' does not meet grammar rules
[1708703951] slot 0: context shift - n_keep = 0, n_left = 2046, n_discard = 1023
[1708703959] slot 0: context shift - n_keep = 0, n_left = 2046, n_discard = 1023
[1708703967] slot 0: context shift - n_keep = 0, n_left = 2046, n_discard = 1023
[1708703974] slot 0: context shift - n_keep = 0, n_left = 2046, n_discard = 1023
[1708703982] slot 0: context shift - n_keep = 0, n_left = 2046, n_discard = 1023

It just does this until I kill it, blocking the thread and the socket.

Hi @boxabirds, are you using JSON mode by chance? Sorry you hit this

Environment="PATH=/home/……:/snap/bin OLLAMA_DEBUG=1"

OLLAMA_DEBUG needs to be on its own Environment line
Environment="PATH=/home/…<various paths>…:/snap/bin"
Environment="OLLAMA_DEBUG=1"

@boxabirds if you're still having problems, please share a bit more information about how your calling Ollama so we can try to reproduce and understand the problem.


Increase fetching of new UTXO set

Lot of users mention that have to manually click on the marina logo to see new incoming transactions, should we add more polling on popup opening to "wake-up" the service worker?

@bordalix This would be best to try to increase fetching on every component mount (potentially having a cache of 5 minutes, to avoid too many calls in short window)


youtube_simple: play button + CSS fixes

Reference #4763
Added a SVG play button that I designed and release it under the Apache 2.0 Licence
Also fixed the CSS after some more tests.

There is a test failure:
ERROR 2018/05/25 00:49:46 error processing shortcode "_internal/shortcodes/youtube.html" for page "simple.md": html/template:_internal/shortcodes/youtube.html: "\"" in attribute name: "1\" xmlns=\"http://www.w3.org/2000"


add mirrored media

mirroredmedia.com

note the right fit. more of party and pop up design than creative tech


ui-grid footer sum double counts by including the subtotals when grouping is applied

Looks like ui-grid is including the subtotals in the footer sum. It should only sum up the base cell values.
http://plnkr.co/edit/nQ2X3OnYAj43uQaXHTHV?p=preview

I am not seeing the problem you describe in the plunker. Did you maybe find this bug in an older version?
Here is an updated version with only a few rows, so it is easier to see what totals should be:
http://plnkr.co/edit/Wq3EfNHA7cnmaZ9ZQt61?p=preview

Please expand the rows, you will see the wrong total at the bottom.

Thanks for clarifying.

Is there any workaround for this?

You could certainly turn off aggregation in the same callback you use to enable grouping.
Or do you mean hide only when there are actually grouped columns? There isn't currently an event api for grouping changes (I just opened #3868 to add one). You could use the rowExpanded event from treebase, since it this problem only occurs when there are expanded rows.
http://ui-grid.info/docs/#/api/ui.grid.treeBase.api:PublicApi

Hi,
I just verified the latest fix. There seems to be a small issue

When aggregationType: uiGridConstants.aggregationTypes.sum is there in the column template, it double counts.
When aggregationType: uiGridConstants.aggregationTypes.sum is not there in the column template, it noes not double count but it does not show any totals when all the groupings are removed.

Again, thanks everyone contributing to this awesome library.

@alam123 The grouping aggregation and the base grid aggregation use very different systems for calculation, so they can't use the same functions.  Please see the api docs for more details.
Currently grouping only applies the footer aggregation if it isn't applied at the grid level, I will take another look and consider whether that should change.
One could in theory write an adapter function which would take the grouping function and apply it as a base aggregation function, which could then be applied when grouping is added/removed. I will try to implement the events on grouping soon, so that is easier to hook into.

Sorry, I had mentioned the wong plunk. The following illustrates the issue.
http://plnkr.co/edit/a3yD0MyhiXPbRKcrqZ8F?p=preview

@alam123 I just merged a change with events for grouping. This tutorial has an example: http://ui-grid.info/docs/#/tutorial/320_complex_grouping.
docs: http://ui-grid.info/docs/#/api/ui.grid.grouping.api:PublicApi
Basically, you should hook into those events and add/remove any of your grid level aggregations. If you do write a flexible function for using the grouping aggregation functions at the grid level, please share it.

Thanks @AgDude
I just did a custom sum to fix this issue at my end. Please look at the behaviour of the last column when you expand the rows and then remove all the groupings.
http://plnkr.co/edit/QUy1bDuA3jPWVrLVyLP5?p=preview


Expo Config Plugin

Mobile Device Environment
iOS
Is your feature request related to a problem? Please describe.
You can't develop on Expo out-of-the-box with react-native-bluetooth-classic since it doesn't have a Config Plugin to handle native configuration.
Describe the solution you'd like
A Config Plugin would be a very useful addition to the library. It would also expand its use cases to Expo projects.

I can see your points, although I've never used Expo.  The few times I have (probably my own issue) I've messed things up and had to just export the project anyhow.
It looks like there are a bunch of best practice expo dependencies that I don't particularly want in the library, to me it looks like creating a expo-bluetooth-classic project and maintaining it separately would be best?  Keeping all the extra Expo related dependencies separate.
I'll have to do a little reading, and I definitely don't have time to look into this now.
I can't think of anything specific to this library that would need to be in there, so effectively any expo-bluetooth plugin that updated the correct PLIST items would work.  You've googled around and none exist?
Can you think of any other configurations in this library that would need to be included in the plugin?  Since you've obviously got way more experience than I, any thoughts would be appreciated.

Thanks for the quick response. The issue (or interesting part) with config plugins is that they were released by Expo about 3 months ago, so most React Native libraries require you to "eject" from Expo and move to pure React Native development. Furthermore, config plugins are essential for using Expo in a project with custom native code, such as yours. This means that for people like me, who want to develop iOS apps on a Windows machine and therefore can't eject from Expo, config plugins might be important.
Though I have only recently started to use Expo and develop on iOS, I might try to create the plugin according to Expo docs since it doesn't seem too complicated and the Expo docs provide an example I could use. To confirm, these:
<key>UISupportedExternalAccessoryProtocols</key>   <array>     <string>com.apple.m1</string>   </array>
are the only pList items required for native configuration, correct?
I will let you know if I get it working and if I do, the plugin might be a useful thing to link in your README.
Thanks again

That's a great idea. I'll try that as well. Thanks for helping me out with this!

No problem, whatever gets more people working faster is cool with me!
I just don't have the time at this point to really take a deep dive into it - it looks like this won't ever work with the Expo Go app - based on comments in that one library README.
I'm not sure how I feel about things like Expo in the grand scheme of things, I'd have to take a look back at it now that that they've made it possible to use more functionality (specifically for IOS).  So thanks for opening this!

Though it won’t work on the Expo Go app, Expo offers an “Expo Development Service” that lets you install a precompiled runtime with your custom native packages, such as this one. That’s what I’m trying to do and I’ve had some success with it. I think it’s pretty cool that Expo let’s you create your own versions of the Expo Go app by just installing the expo-dec-client non package and building on the cloud, though it’s very new. According to my research, developing iOS on Windows is a rapidly expanding field of services and Expo tries to be an all-in-one solution to this.
Check out this Expo-sponsored video if your interested: https://m.youtube.com/watch?v=Iw8FAUftJFU It explains the functionality very well.

From: Ken Davidson @.>
Sent: Wednesday, August 11, 2021 10:19:31 AM
To: kenjdavidson/react-native-bluetooth-classic @.>
Cc: amitferman @.>; Author @.>
Subject: Re: [kenjdavidson/react-native-bluetooth-classic] Expo Config Plugin (#124)
No problem, whatever gets more people working faster is cool with me!
I just don't have the time at this point to really take a deep dive into it - it looks like this won't ever work with the Expo Go app - based on comments in that one library README.
I'm not sure how I feel about things like Expo in the grand scheme of things, I'd have to take a look back at it now that that they've made it possible to use more functionality (specifically for IOS). So thanks for opening this!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/kenjdavidson/react-native-bluetooth-classic/issues/124#issuecomment-897006870, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFS35YXRW5OQJLQVOVLRRRDT4KWKHANCNFSM5B5UCYRA.

After looking back on this problem, I was able to find a solution and opened a pull request accordingly.


Issue 222

Description of your changes
Add the following resources:

[x] aws_cloudformation_stack
[x] aws_cloudformation_stack_set

Fixes https://github.com/upbound/provider-aws/issues/222
I have:

[x] Run make reviewable test to ensure this PR is ready for review.

How has this code been tested
Manually and Uptest

/test-examples="examples/cloudformation/*.yaml"


[forwardport] Deploy/Edit Workload page - Drop down icon disappears when hovering over protocol and port type field.

Forwardport of rancher/rancher#23987

Available in latest2.

Available in latest2.

Tested with Rancher server rancher\rancher:master-head version abd6f58c6
Deploy/edit workload pag - Drop down icons stays when hovering over protocol and port type field.

On clicking "Add Port", both protocol and port type drop down icons stay and function.


Incorrect index calculation in case item{} function is used with items{} in LazyColumn

In case
LazyColumn(state = listState, modifier = Modifier.reorderable(orderState, { a, b -> onReorder(models, a, b) })) {
item{
ListHeader()
}
items(models.size, { index -> getKey(models[index]) }) { index ->
ListItem(model = item, index)
}
}
To achieve header on top of the list, beyond which you can't drag the item. After starting the drag motion, item dragged will have position index+1 and possibly cause outOfIndexException in case you drag the item to last poistion in function .move(to, from)

If you want to a header you need to do it in  items scope (like the locked headers in sample code).
In case you wanna stick with your single item , you can do it like this :
.reorderable(state,
onMove = { from, to -> onReorder(max(from - 1, 0), max(to - 1, 0)) },
canDragOver = { it > 0 })

The canDragOver was the key, thanks. Maybe a requirement of only using items() function could be in readme. But overall very nice library, thanks.

The index always refers to the LazyList item index , the list dosn't know your data.
So mapping must be done in onMove , canDragOver  ,  (onDragEnd)  if your data index != list index .
But let's see if i can improve mapping , at least for keyed lists.


support docker-sync for mac users

Description
Every mac users suffer using docker on their macs. Sharing files through containers is very slow.
Rationale
Only mac users need this. Other users don't care :)
Use case(s) / visualization(s)
If you are using many static files in containers loading speed of each request decrease.

@hoffmannkrzysztof could the delegated flag facilitate in healing that wound somehow?

@webyneter I not sure if I understand you clearly. But docker-sync helps a lot of users who using mac while developing. Take a look at the official documentation: http://docker-sync.io/. I am using this solution and see only pros.

Every mac users suffer using docker on their macs

I am a Mac & Docker user. I didn't experience any slowness whatsoever with sharing files from docker containers. How could you reproduce exactly?

docker-sync seems to support windows/linux as well, why not support them?

Shouldn't it be an optional feature, for added complexity?

@sfdye

This issue on mac is related to a large number of I/O operations. The easy way to reproduce this issue is by using a large number of assets. Take a look for more info: https://github.com/docker/for-mac/issues/77
Of course, docker-sync support Windows and Linux and can be used.
This addon is optional. If you don't want sync when you will use regular docker-compose

I used to have that same issue until I started using docker-machine, try it, is worth the shot.

Docker for mac has improved the file sharing implementation with VirtuoFS:
https://www.docker.com/blog/speed-boost-achievement-unlocked-on-docker-desktop-4-6-for-mac/
In my experience it's much faster, so I'm closing this, I consider it no longer needed.


feat: implement oAuth for Camunda Webapp

closes #367

Codecov Report
Attention: Patch coverage is 7.69231% with 12 lines in your changes missing coverage. Please review.

Project coverage is 50.49%. Comparing base (7e7d0fc) to head (626003f).

Files
Patch %
Lines

...iranum/connect/Camunda7oAuthAutoConfiguration.java
0.00%
12 Missing :warning:

Additional details and impacted files
@@             Coverage Diff              @@
##               main     #433      +/-   ##
============================================
- Coverage     50.77%   50.49%   -0.29%
  Complexity      205      205
============================================
  Files           150      150
  Lines          1603     1612       +9
  Branches        113      114       +1
============================================
  Hits            814      814
- Misses          757      766       +9
  Partials         32       32

Flag
Coverage Δ

unittests
50.49% <7.69%> (-0.29%)
:arrow_down:

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

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


[main] Update community files (#323)

Update community files
Signed-off-by: Knative Automation<EMAIL_ADDRESS>

OCF Webhook is merging this PR


update base64-js version. follow up #6961

Motivation
This is originally a follow up of PR #6327 by @dewe and @jeremyong
And @mkonicek indicated this should split into a separate PR.
Now @philikon takes over #6327 as #6961
Test Plan:
According to #6961 and #6889
Load WebSocketExample in UIExplorer app and start websocket test server script and test sending binary data on both iOS and Android

@mkonicek Letting you merge this in since you guys update the internal fb npm cache manually.

note: this PR now depends on #6961
and needs @philikon to review

note: this PR now depends on #6961

I don't see why that's the case.

Pro-tip: make sure you explain the motivation for your PR. You're currently not giving any, instead pointing to other PRs which also don't give motivation. If you want to make it easier for reviewers, and quicker for you, I suggest editing your PR note to include a small note about why you want this change. Also please don't forget a test plan.

@philikon
thanks for your tips. update as you described.
why this PR exist and described as a follow up of #6961 are because:

original author @dewe add in his commit da084b79a9036fbd03c6f91a77e1ac4b65343edf in #6327
later #6327 hangs for a while and everybody seems busy, so I just helped to complete the rest based on @dewe 's patch --- this PR.
then @philikon takes over whole PR #6327  into #6961

This PR should be closed if no one needed

my motivation is purely hope awesome PRs won't hang.
follow up author @philikon in #6961 confirmed #6961 works on bas64-js 0.0.8 ( not necessary to upgrade )

If no one thinks this is necessary, then this PR should be closed.
How do you think @dewe ?
thanks again for all the great jobs.

I can't recall why this was upgrade was needed. Since @philikon is handling things in the other PRs, this one should definitely be closed.

Thanks @dewe
#6961 has been shipped, thank you 💯
@mkonicek @philikon
I think it is better to upgrade base64js to 1.x version if we using it as react native core.
do you think this is good to go?

Upgrading sounds good. I'll need to merge this manually into our internal node_modules store though.

@cpojer would you mind taking a look at this pull request? It's been a while since the last commit was reviewed.

@facebook-github-bot import

Thanks for importing.

It's been a while since the last commit was reviewed and the labels show this pull request needs review. Based on the blame information for the files in this pull request we identified @cpojer as a potential reviewer. Could you take a look please or cc someone with more context?

Took a while to get back to this one :)
@facebook-github-bot import

Thanks for importing. If you are an FB employee go to Phabricator to review internal test results.


Java Version Change in Windows Node

Hi All,
I have done setup from Jenkins Master to Windows node via SSH and I have set the java path in jenkins node too. And it working properly. But when my java version is upgrading in Windows node. Then jenkins slave is disconnecting automatically and its affected my job too.
How to handle this type of situation.
Khaja Sir@Could you please help me on this issue.

as you said you are set the path in jenkins node and you are upgrading the java, for my suggestion is upgrade the java path is jenkins node because you are set the path, paths are not updated automatically.

Al are the windows Azure machine . In our company couple of moth java  upgrading is going one  due to that its deleting the old java and in place of old java its putting new java. just like jdk_251 or jdk_261 due to that Jenkins node got disconnected. And its affecting the night build job.

Sir please set the explicit export statement (set JAVA_HOME) in your jenkins job if thats the case


docs: Documentation update for OpenTelemetry and tracing

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[x] Make sure to open an issue as a bug/issue before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[x] Ensure the tests and linter pass
[x] Code coverage does not decrease (if any source code was changed)
[x] Appropriate docs were updated (if necessary)

Here is a preview for the updated ReadMe:

Thank you for the great feedback @mtabasko! Updated the PR with fixes to your comments.

Is OwlBot supposed to update the README ? Otherwise LGTM

Yes OwlBot post-processor will update the README.

/gcbrun

/gcbrun

Is OwlBot supposed to update the README ? Otherwise LGTM

The OwlBot was supposed to update the README. However there is a hermetic build change which is deprecating Owlbot for java handwritten client libraries(go/hermetic-build-integration-hw-libraries). @diegomarquezp suggested we update this manually for now while his team is working on a fix. For now we have manually updated README.


⚠ Jenkins Plugins Artifactory has degraded performance

In e093f11, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1966 ms

Resolved: Jenkins Plugins Artifactory performance has improved in e27ec8e after 1 hour, 22 minutes.


Reduce clutter of files and folders and move data to the local profile folder (Windows)

Is your feature request related to a problem? Please describe.
If a user installs IPFS Desktop on Windows, it will create multiple folders:
%AppData%\Roaming\IPFS Desktop
%USERPROFILE%\.ipfs
%USERPROFILE%\.ipfs-desktop
That's pretty unintuitive where what data will be stored and why.
Describe the solution you'd like
Let IPFS Desktop create a single folder in %AppData% and move the rest of the folders below it.
Additional context
Not sure if we should really use the Roaming folder, depending on the size of the data stored and cached in IPFS it could slow down logins on mobile devices or secondary desktops in a domain significantly. I think since IPFS addresses nodes and not user profiles, we might want to move the folder to local, which means on secondary desktops or mobile devices, the folder won't be fetched. Additionally, it won't be stored in the remote profile on the domain server, but instead on the local computer only.

This is a duplicate of https://github.com/ipfs/ipfs-desktop/issues/1656, let's continue there.


Tweet-cli script

Script Title - Tweet using tweet-cli
what will change - Add script
Instructions

Create a new folder for your script and file/folder name should be appropriate.
Create a README.md in your folder for program Instructions
add requirements.txt if needed

Please add/delete options that are not relevant.

[x] Adding New Code
[x] Improving Code
[x] Improving Documentation
[ ] Bug Fix

Programming Language

[x] Python

Happy Coding,

@pawangeek
May you please approve this? I would like to grab it as well if you don't mind.

Okay go ahead, but can you brief me about exact objective and how you gonna achieve that

Okay go ahead, but can you brief me about exact objective and how you gonna achieve that

Thanks.
The Objective is to tweet in a nerdy way :monkey_face: using cli like tweet-cli "this is my tweet from tweet-cli"
This is a super easy task as we have implemented the tweet API module. So I just call this module and update the status using api.update_status() . Please share your idea enhancement if you have some.
besides I have a question. The Dockerfile also needs to be revised, would it be fine If i fix it within this issue or you want me to open a new issue for it ?

Sounds great and fix that dockerfile in this same issue. I think no need to open another one


Update to v1.1.0

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

@kalefranz I've added myself as a co-maintainer in addition to updating the version of the package. Getting this merged would allow us to close a bunch of unmerged PRs from the regro bot.

@conda-forge/core - Would anyone be willing to merge this pull request? I contacted the feedstock owner but didn't get a response. There are a number of languishing pull requests and I'd like to become a co-maintainer to help move things along.


C++ standard not set correctly

I've imported the envoy project, and I've found that IntelliJ can't find make_unique in the std namespace (i.e. std::make_unique):

Can't resolve namespace member 'make_unique'

I'm assuming this is because IntelliJ doesn't know what C++ standard to use. Normally one would specify something like so in their CMakeLists.txt to use C++ 14:
set(CMAKE_CXX_STANDARD 14)

However, adding a CMakeLists.txt to the root of the project doesn't convince IntelliJ to use the desired standard.
Here's where the envoy build system passes -std=c++14:
https://github.com/envoyproxy/envoy/blob/1039178c218db0c2fd2f85cbe8313ad2ceabee01/bazel/envoy_build_system.bzl#L15
Some questions:

Should the Bazel plugin be configuring IntelliJ to use the right standard for each file? e.g. should the plugin configure IntelliJ to honor the -std=c++14 from the envoy build system?
Is there a known way to make IntelliJ use a given standard?

This is on CLion 2017.3.4 with the Bazel 2<IP_ADDRESS>.5 plugin, running on Ubuntu 17.10.

In envoy, each cc_library independently has -std=... vs once in the crosstool. This code [1] needs to pick up those per-cc_library flags, and propagate it through. Right now, only a few things are picked up (-D, -I, ...). May need to be careful about bazel sync performance though. CLion executes the compiler with -d to have the compiler dump #defines corresponding to the cmdline flags (e.g., converting -std=c++14 to the appropriate __cplusplus value). If there are many unique flags, there will be many compiler runs.
One workaround is to specify the -std flag at the top level in the .bazelproject file, and re-run bazel sync:
build_flags:
--cxxopt=-std=c++14
Of course, that could end up applying the cmdline flag to more cc_library targets than intended within envoy.
[1] https://github.com/bazelbuild/intellij/blob/3ae2ad5c5496e160771fd74bedc1f42304ecb214/base/src/com/google/idea/blaze/base/sync/aspects/IdeInfoFromProtobuf.java#L232

This should be fixed in the next plugin release.

This is still happening with the version from https://github.com/bazelbuild/intellij/issues/494#issuecomment-498814006 / https://github.com/bazelbuild/intellij/files/3254199/clwb_bazel.zip


Change getModuleName regex to only remove extenion

Given a names like: "some.module.js" and "some.other.module.js" the current regex in DefaultFormatter.prototype.getModuleName will overmatch and only return "some" as the module name in both cases.
Changing the . character class to \w will make sure it does not pick up additional sections and returns "some.module" and "some.other.module" for the names

Damn, good catch. Thanks! I'll push out a new version in a bit.


More consistent usage of "back-end" (instead of "backend") in couple of places

related to https://github.com/openEOPlatform/documentation/commit/e118893cf681ff09d788171622d2beff8847a448

Thanks.


Better handling of different autopilot versions (M100, A3 ..etc)

A couple of people asked this question over ICRA and it would be fantastic to be able to handle other DJI's autopilots... but I guess we don't have sufficient manpower to support this at this moment?


Proposed licenses of scripts / data

this ok with you @martenson?  (just proposing something, feel free to comment / turn this into a discussion as necessary.)

there is https://github.com/martenson/public-galaxy-servers/blob/master/LICENSE
for the data I would prefer https://creativecommons.org/publicdomain/zero/1.0/

How did I forget about the MIT license, I opened the issue for that. Ok, sounds good @ zero.


Gapless SPI transfers

Currently our code transfers SPI data in chunks (sized by FIFO_SIZE) . This results in short gaps in the transmission.
While most (if not all) SPI devices should work this way this prevents us from (mis)using SPI to do other things like driving an LED-strip of addressable LEDs or similar.
It is possible to continuously write to the FIFO and avoid those gaps. Something like that is already done for pulse_control/RMT

Oh is there a way to submit data to the SPI fifo directly? Is your ticket referring to when performing CPU controlled SPI transfers there seems to be large sets of time where SPI is not transferring data? I have a project where I'm trying to pump out data over quad spi as fast as I can, and would definitely be interested in seeing ways of improving speed.

Yes that might be possible  - from the ESP32-C3 TRM (it's similar for the others)

<IP_ADDRESS> CPUControlled Master Mode
... . If the data
byte length is larger than 64, the data in SPI_W8_REG[7:0] ~ SPI_W15_REG[31:24] may be sent more
than once. For instance, 66 bytes (byte0 ~ byte65) need to send out, the address of byte65 is the
result of (65 % 64 = 1), i.e. byte65 is from SPI_W0_REG[15:8], and byte64 is from SPI_W0_REG[7:0].
For this case, the content of SPI_W0_REG[15:0] may be sent more than once.

Unfortunately, there doesn't seem to be a threshold interrupt or anything - so it might be tricky.  Also it's not clear if the hardware takes writes to the SPI_Wx_REGs during a transfer.
Probably this is more about researching this.
If it turns out we can't get it working we probably need to wait for the implementation of DMA (which we definitely want to do - it's just not yet started)

oh interesting, like maybe you could write into the Wx registers and perform a long write with SPI and then "chase" the registers. I wonder when one of  the SPI_Wx_REG is read by SPI does it empty?
There is also
// wait if currently in a write
            while block.cmd.read().usr().bit_is_set() {
                // wait
            }

but I guess that's just for "is SPI currently writing".

Also it's not clear if the hardware takes writes to the SPI_Wx_REGs during a transfer.

I ran a small experiment that set up a 128-byte transfer (in quad mode) and flipped the Wx registers from 0x0000_0000 to 0xffff_ffff while the transfer was running, and the good news is that the hardware does "see" the writes:

As you say, though, it does seem tricky to get the timing right: in that screenshot, it looks like I overwrote the back ~half of the Wx block before it was sent the first time. Letting the analyzer run for a while and eyeballing it, though, it does look like the rising edge there is consistent, which leads me to believe it'd be possible to emit a very long (though not fully continuous) waveform this way.

FYI I started implementing DMA (for the start on ESP32-C3). With that we can have single transfers up to 32k which is probably the way to go