Create logging interface

In GitLab by @JoerivanEngelen on Jul 25, 2023, 17:33
Create a simple logging interface which can be used (in the follow-up tasks) e.g. to :

To log at package writing and dumping
To log at simulating writing and dumping
Validation
Time Discretization
Things happening with Grid Agnostic packages behind the scenes (e.g. removing invalid wells)
regridding/clipping/masking

We should apply Loguru here, as it:

doesn't require much code
is well maintained
most-popular third-party logging package
Also used in iMOD Coupler, so the product line has experience.

[x] #751
[x] #752

Merged in https://github.com/Deltares/imod-python/pull/754


Upgrade to numpy 2.0+

This fixes the complex warning in CV gates when using Numpy 2.0. The internals of qiskit cast parameters to float when possible, and numpy only raises a warning if this happens. This modifies the ParameterizedUnitaryGate to convert all numpy complex objects to the builtin python complex type, which forces qiskit to not downcast to float, preserving the complex parameters.

We may be able to upgrade to Numpy 2.0.x, but Numpy 2.1.x requires Python 3.10+ (https://numpy.org/devdocs/release/2.1.0-notes.html). I've been trying to keep compatible with supported Python versions, and Python 3.9 is expected to be supported until October 2025 (https://devguide.python.org/versions/).
Would we be able to upgrade to Numpy 2.0.2 instead and keep the complex number fix?

Yes it seems to work locally with numpy 2.0.2


Expose the Cognito group used for authorization as a CFn parameter.  Allow multiple groups.

Is your feature request related to a problem? Please describe.
Many customers have existing identity management / SSO solutions deployed inside their enterprises e.g. Azure AD.  They commonly want to integrate access to the QnABot designer, etc, with this infrastructure, generally using SAML federation.  After a SAML IdP is configured inside cognito, when a user tries to login in, they are denied access.  At this point, the user must be added to the Admin group inside cognito.  This can be done manually or with a Lambda function tied to the cognito Post-confirmation hook and maintained by the customer.
Describe the feature you'd like
Add the group used for Cognito authorization as a CFn parameter.  As a bonus, support multiple groups.  Then when a federated identity is added to cognito, the group associated with these users could be added to QnABot and users granted access.
For example, if a federated sign-in identity provider named AzureAdIdp is added to the user pool, a group called region_XXXXXXXXX_AzureAdIdp is automatically created and all users federating in via this provider are added to the group.  It would be nice to click Update on the stack, add this name to a CFn parameter, and have access to the QnABot designer be granted.

The enhancement did not receive enough support to be added to the roadmap


Increase ScyllaDB CI timeout

Motivation
Seems to be timing out for some PRs
Proposal
Increase timeout
Test Plan
CI

Current dependencies on/for this PR:

main

PR #1254   👈

This stack of pull requests is managed by Graphite.

Seems like this could be caused by a known bug, so closing for now


Mark as read broken?

This weekend I upgraded my 2 year old stringer to the latest code, sadly this broke the "marked as read" in my reeder apps somehow. Not sure what happend there. Anyone else having the same issue?

Okay, the reason is this:
NoMethodError - undefined method `update_attributes' for #<Story id: 328478, ....">
Did you mean?  update_attribute:
	/home/bitboxer/stringer/vendor/bundle/ruby/3.0.0/gems/activemodel-<IP_ADDRESS>/lib/active_model/attribute_methods.rb:458:in `method_missing'
	/home/bitboxer/stringer/app/commands/stories/mark_as_read.rb:10:in `mark_as_read'
	/home/bitboxer/stringer/app/fever_api/write_mark_item.rb:26:in `mark_item_as'
	/home/bitboxer/stringer/app/fever_api/write_mark_item.rb:16:in `call'

In the tests this method is mocked out and makes test still green. Sadly this method was removed in ActiveRecord 6.1:

Remove deprecated ActiveRecord::Base#update_attributes and  ActiveRecord::Base#update_attributes!.

See: https://guides.rubyonrails.org/v6.1/6_1_release_notes.html


Put the new Mongo Pool Size config in sails-mongo

Node version: 16.20.2
Sails version (sails): - (NestJS App)
ORM hook version (sails-hook-orm): -
Sockets hook version (sails-hook-sockets): -
Organics hook version (sails-hook-organics): -
Grunt hook version (sails-hook-grunt): -
Uploads hook version (sails-hook-uploads): -
DB adapter & version (e.g. sails-mysql@5.55.5): "sails-mongo": "2.1.0"
Skipper adapter & version (e.g. skipper-s3@5.55.5):  -
mongodb version :  "mongodb": "6.3.0"

First I want to thank you very much for updating sails-mongo 🚀❤
Here is the problem :
Error happen when server is starting.
[Nest] 269955   - 03/04/2024, 4:25:33 PM   Invalid configuration for datastore `mongo`:  Unrecognized options (`maxPoolSize`) specified as config overrides.
This adapter expects only whitelisted properties.
--
See http://sailsjs.com/config/datastores#?the-connection-url for info,
or visit https://sailsjs.com/support for more help. +132ms
Error: Invalid configuration for datastore `mongo`:  Unrecognized options (`maxPoolSize`) specified as config overrides.
This adapter expects only whitelisted properties.
--
See http://sailsjs.com/config/datastores#?the-connection-url for info,
or visit https://sailsjs.com/support for more help.
    at Object.registerDatastore (/home/app/application/node_modules/sails-mongo/lib/index.js:209:58)
    at /home/app/application/node_modules/waterline/lib/waterline.js:717:27

See with @DominusKelvin, mongo parameter poolSize is now deprecated, I've replace it by maxPoolSize wich is not reconized by the new release of sails-mongo.
Regards 😃

Thanks @marecatg for this detailed PR. I'll look to providing a patch release of sails-mongo to add maxPoolSize connection option.
Also I'll further investigate what other configs were deprecated as well and what else to add.

Hey @marecatg I just opened a PR to add the maxPoolSize config. This will be merged as soon as possible. Thanks for your patience on this one. cc @eashaw

Thank you @DominusKelvin 🚀

Hello, any news about the PR ? Thank you?

Hey @marecatg the PR has been merged that added the new pool size config to sails-mongo. There is also a new patch release as well.


First pass at Adventures in Middle Earth character sheet

Modified the 5e SRD sheet to support the changes needed
for Adventures in Middle Earth by Cubicle 7.

I've gone ahead and corrected the naming of your translation file (it should simply be translation.json) for you, make sure future changes operate on that.  Everything else looks good.  Thanks!


why this only response once?

const app = require('koa')();
const fetch = require('node-fetch');
const FormData = require('form-data');

app.use(function* (next) {
  console.log('receive request');
  yield next;
  this.body = 'success';
});

app.listen(9999);

const form = new FormData();
form.append('a', 1);

const headers = form.getHeaders();

// fetch 1
fetch('http://localhost:9999', {
  method: 'POST',
  body: form,
  headers: headers
}).then(() => console.log('response1'))
  .then(() => {

    // fetch 2
    fetch('http://localhost:9999', {
      method: 'POST',
      body: form,
      headers: headers
    }).then(() => console.log('response2')).catch(error => console.error(error))

  }).catch(error => console.log(error));

I post the form twice, but only receive one response

You want to simplify your example to a pure node-fetch test.

And use a service like http://httpbin.org/ instead of your localhost.

And the way you nest your promise chain is not helping anyone (including yourself) to debug this issue.

I'm getting a little dizzy and not sure the problem is come from node-fetch, I'll continue to check this problem, thank you anyway!
const fetch = require('node-fetch');

const form = {
  a: 1
};
const headers = {
    'Content-Type': 'application/json'
};

// fetch 1
fetch('http://httpbin.org/post', {
  method: 'POST',
  body: form,
  headers: headers
}).then(() => console.log('response1'))
  .then(() => {

    // fetch 2
    fetch('http://httpbin.org/post', {
      method: 'POST',
      body: form,
      headers: headers
    }).then(() => console.log('response2')).catch(error => console.error(error))

  }).catch(error => console.log(error));

from your code it's not obvious why you would want to nest the fetch sequentially, you could very well have them in parallel with Promise.all().
if you need sequential, a better solution is to return your second fetch, that way you can use a single catch() to handle errors from all your fetch.

you are right, thank you!


General: Standardise AnteHandler

Ideally we don't have to create an AnteHandler for each module. A standard IxoAnteHandler should be created. If necessary, each module could then implement module-specific functionality that is called by the IxoAnteHandler.
Note that a general NewIxoAnteHandler function does exist, but this just creates a router to the module AnteHandlers.

Closed by #118


frontend-assignment<3>

Metric
Value

alert_status
:white_check_mark: OK

bugs
1

code_smells
12

reliability_rating
C (at least 1 Major Bug)Note: A being best, E being worst

security_rating
A (0 Vulnerabilities)Note: A being best, E being worst

vulnerabilities
0


search assets action via shortcut

Extension
https://www.raycast.com/colbyfayock/cloudinary
Description
Search Assets action shows nothing when triggered via shortcut
Here is a video of an issue - https://capture.dropbox.com/9nYrvXtOtQNCm4ZT
Steps To Reproduce

Open Raycast
Search for "Search Assets" command
Hit enter

OR
Press assigned shortcut (option + A in my case)
Current Behaviour
In case of triggering a command with a shortcut it doesn't show any assets.
Expected Behaviour
The same as triggering a command like this:

Open Raycast
Search for "Search Assets" command
Hit enter

hey @romanskorobagatko i opened up a ticket on the actual repository. i plan on getting to this, i just haven't yet: https://github.com/colbyfayock/raycast-cloudinary/issues/9


Add Sentinel-2 and Landsat option to animation notebook

Proposed changes
A small PR to add a combined "Sentinel-2 and Landsat" layer to our interactive animations notebook. This will allow users to create animations that combine both Sentinel-2 and Landsat data:

Hi Robbi, awesome update. I can't find any changes to suggest.I ran the notebook in the sandbox and the mixed product worked fine. I did receive an error that I did not get when running a single product animation, but it didn't stop the animation from being produced. Pretty sure nothing to worry about...."/env/lib/python3.8/site-packages/rasterio/warp.py:344: NotGeoreferencedWarning: Dataset has no geotransform, gcps, or rpcs. The identity matrix will be returned.
  _reproject(


[Bug]: Build Environment Variables passed to Dockerfile buildpack

Description
Heyo!
I created a resource with a "Dockerfile" build pack where i put all of my Environment Variables, which should be included at Build Time with the flag "Build Variable?" checked.
These Environment Variables are not being included in the build process, as you can see in the logs below.
What am i doing wrong? Do i need to do something else to include these Environment Variables in the build process?
Thanks for the help 🙏
#15 [builder 6/8] RUN echo -e "\e[1;33mENVIRONMENT VARIABLES\e[0m"
[2024-Apr-02 08:47:00.447127]
COMMAND:
docker exec h4sgwcc bash -c 'bash /artifacts/build.sh'

OUTPUT:
#15 0.468 -e ENVIRONMENT VARIABLES
[2024-Apr-02 08:47:00.683328]
COMMAND:
docker exec h4sgwcc bash -c 'bash /artifacts/build.sh'

OUTPUT:
#15 DONE 0.5s

#16 [builder 7/8] RUN env
[2024-Apr-02 08:47:00.788315]
COMMAND:
docker exec h4sgwcc bash -c 'bash /artifacts/build.sh'

OUTPUT:
#16 0.260 NODE_VERSION=20.12.0
#16 0.260 YARN_VERSION=1.22.19
#16 0.260 HOME=/root
#16 0.260 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
#16 0.260 WIREIT_LOGGER=simple
#16 0.260 PWD=/app
#16 0.260 NODE_ENV=production
[2024-Apr-02 08:47:00.893188]
COMMAND:
docker exec h4sgwcc bash -c 'bash /artifacts/build.sh'

OUTPUT:
#16 DONE 0.3s

Minimal Reproduction (if possible, example repository)
No response
Exception or Error
No response
Version
v4.0.0-beta.248

even when i try to add them in the Docker like this:
ENV BROWSERLESS_URL=$BROWSERLESS_URL
ENV DATABASE_URL=$DATABASE_URL
ENV GOOGLE_CLIENT_ID=$GOOGLE_CLIENT_ID
ENV GOOGLE_CLIENT_SECRET=$GOOGLE_CLIENT_SECRET
ENV MAGIC_SK=$MAGIC_SK
ENV NEXT_PUBLIC_MAGIC_PK=$NEXT_PUBLIC_MAGIC_PK
ENV NEXT_PUBLIC_UMAMI_SCRIPT_URL=$NEXT_PUBLIC_UMAMI_SCRIPT_URL
ENV NEXT_PUBLIC_UMAMI_WEBSITE_ID=$NEXT_PUBLIC_UMAMI_WEBSITE_ID
ENV NEXTAUTH_SECRET=$NEXTAUTH_SECRET
ENV NEXTAUTH_URL=$NEXTAUTH_URL
ENV REDIS_URL=$REDIS_URL
ENV S3_UPLOAD_BUCKET=$S3_UPLOAD_BUCKET
ENV S3_UPLOAD_KEY=$S3_UPLOAD_KEY
ENV S3_UPLOAD_REGION=$S3_UPLOAD_REGION
ENV S3_UPLOAD_SECRET=$S3_UPLOAD_SECRET
ENV VERCEL_URL=$VERCEL_URL
ENV WEBSNAP_URL=$WEBSNAP_URL

they are still empty and undefined:
#15 [builder 6/8] RUN echo -e "\e[1;33mENVIRONMENT VARIABLES\e[0m"
#15 0.174 -e ENVIRONMENT VARIABLES
#15 DONE 0.2s

#16 [builder 7/8] RUN env
#16 0.268 DATABASE_URL=
#16 0.268 NODE_VERSION=20.12.0
#16 0.268 YARN_VERSION=1.22.19
#16 0.268 NEXTAUTH_SECRET=
#16 0.268 MAGIC_SK=
#16 0.268 HOME=/root
#16 0.268 NEXT_PUBLIC_UMAMI_WEBSITE_ID=
#16 0.268 NEXT_PUBLIC_UMAMI_SCRIPT_URL=
#16 0.268 S3_UPLOAD_BUCKET=
#16 0.268 VERCEL_URL=
#16 0.268 GOOGLE_CLIENT_ID=
#16 0.268 GOOGLE_CLIENT_SECRET=
#16 0.268 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
#16 0.268 S3_UPLOAD_REGION=
#16 0.268 S3_UPLOAD_SECRET=
#16 0.268 WIREIT_LOGGER=simple
#16 0.268 NEXTAUTH_URL=
#16 0.268 BROWSERLESS_URL=
#16 0.268 PWD=/app
#16 0.268 WEBSNAP_URL=
#16 0.268 REDIS_URL=
#16 0.268 NODE_ENV=production
#16 0.268 S3_UPLOAD_KEY=
#16 0.268 NEXT_PUBLIC_MAGIC_PK=
#16 DONE 0.4s

I will add a small fix to the next version.

@ChiefORZ Did you found a solution for this? :)

@timootten not yet unfortunately

@ChiefORZ The solution with this:
ENV DATABASE_URL=$DATABASE_URL
Works for me, in the logs it’s just empty, to not leak the data/key.
You have to define all your ENV variables like this and it should work.
I had another problem with SvelteKit, their you must use process.env.DATABASE_URL and not the import from SvelteKit

@andrasbacsai please help, i can not get the environment variables passed to my dockerfile.
here is the setup of my Dockerfile:
FROM node:20 AS nodeenv

ENV PNPM_HOME="/pnpm"
ENV PATH="$PNPM_HOME:$PATH"

ENV BROWSERLESS_URL=$BROWSERLESS_URL
ENV DATABASE_URL=$DATABASE_URL
ENV GOOGLE_CLIENT_ID=$GOOGLE_CLIENT_ID
ENV GOOGLE_CLIENT_SECRET=$GOOGLE_CLIENT_SECRET
ENV MAGIC_SK=$MAGIC_SK
ENV NEXT_PUBLIC_MAGIC_PK=$NEXT_PUBLIC_MAGIC_PK
ENV NEXT_PUBLIC_UMAMI_SCRIPT_URL=$NEXT_PUBLIC_UMAMI_SCRIPT_URL
ENV NEXT_PUBLIC_UMAMI_WEBSITE_ID=$NEXT_PUBLIC_UMAMI_WEBSITE_ID
ENV NEXTAUTH_SECRET=$NEXTAUTH_SECRET
ENV NEXTAUTH_URL=$NEXTAUTH_URL
ENV REDIS_URL=$REDIS_URL
ENV S3_UPLOAD_BUCKET=$S3_UPLOAD_BUCKET
ENV S3_UPLOAD_KEY=$S3_UPLOAD_KEY
ENV S3_UPLOAD_REGION=$S3_UPLOAD_REGION
ENV S3_UPLOAD_SECRET=$S3_UPLOAD_SECRET
ENV VERCEL_URL=$VERCEL_URL
ENV WEBSNAP_URL=$WEBSNAP_URL
ENV WIREIT_LOGGER simple

# Start with the official Node.js image.
FROM nodeenv AS deps
RUN corepack enable

# Set the working directory.
WORKDIR /app

# Copy package.json and pnpm-lock.yaml before other files
# Utilise Docker cache to save re-installing dependencies if unchanged
COPY package.json ./
COPY pnpm-lock.yaml ./

# Install dependencies
RUN --mount=type=cache,id=pnpm,target=/pnpm/store pnpm install --frozen-lockfile

# Build the Next.js app
FROM nodeenv AS builder
RUN corepack enable

WORKDIR /app

# Copy all files
COPY . .

# Copy the previously installed dependencies
COPY --from=deps /app/node_modules ./node_modules

# print the env variables
# with a "ENVIRONMENT VARIABLES" title in a different color
RUN echo -e "\e[1;33mENVIRONMENT VARIABLES\e[0m"
RUN env

# Build the Next.js app
ENV NODE_ENV production
RUN pnpm run build:next

# Only copy over the Next.js pieces we need
FROM nodeenv AS runner
RUN corepack enable

ENV NODE_ENV production

WORKDIR /app

COPY --from=builder /app/.next/ ./.next/
COPY --from=builder /app/node_modules/ ./node_modules/
COPY --from=builder /app/prisma/ ./prisma/
COPY --from=builder /app/public/ ./public/

COPY --from=builder /app/src/env.mjs ./src/env.mjs
COPY --from=builder /app/next.config.mjs ./next.config.mjs
COPY --from=builder /app/package.json ./package.json

# Expose the listening port
EXPOSE 3000
ENV PORT 3000

# Run pnpm start to launch the app
CMD ["pnpm", "start:next"]

I marked all my Environment Variables as Build Variables of course.
I also recreated the ressource and recreated it completely, because i thought i missed something

@andrasbacsai right, just confirrmed it. it works if i add them manually, but there seems to be an error if i add all of them with the Developer View and change them to Build Variables on the Normal View afterwards

This is also happening to me. I've spent 5 hours trying to get my environment variables to be read on the Dockerfile bu I haven't been successful yet. I've tried creating them again, locking them, deploying without cache and nothing seems to work. This is my Dockerfile
# syntax = docker/dockerfile:1

# Make sure RUBY_VERSION matches the Ruby version in .ruby-version and Gemfile
ARG RUBY_VERSION=3.3.3
FROM registry.docker.com/library/ruby:$RUBY_VERSION-slim AS base

# Rails app lives here
WORKDIR /rails

# Set production environment
ENV RAILS_ENV="production" \
    BUNDLE_DEPLOYMENT="1" \
    BUNDLE_PATH="/usr/local/bundle" \
    BUNDLE_WITHOUT="development"

ENV RAILS_MASTER_KEY=$RAILS_MASTER_KEY
ENV LITESTREAM_REPLICA_BUCKET=$LITESTREAM_REPLICA_BUCKET
ENV LITESTREAM_ACCESS_KEY_ID=$LITESTREAM_ACCESS_KEY_ID
ENV LITESTREAM_SECRET_ACCESS_KEY=$LITESTREAM_SECRET_ACCESS_KEY
ENV TWITCH_CLIENT_ID=$TWITCH_CLIENT_ID
ENV TWITCH_CLIENT_SECRET=$TWITCH_CLIENT_SECRET

RUN env

# Throw-away build stage to reduce size of final image
FROM base AS build

# Install packages needed to build gems
RUN apt-get update -qq && \
    apt-get install --no-install-recommends -y build-essential git libvips pkg-config wget

# Install application gems
COPY Gemfile Gemfile.lock ./
RUN bundle install && \
    rm -rf ~/.bundle/ "${BUNDLE_PATH}"/ruby/*/cache "${BUNDLE_PATH}"/ruby/*/bundler/gems/*/.git && \
    bundle exec bootsnap precompile --gemfile

# Copy application code
COPY . .

# Precompile bootsnap code for faster boot times
RUN bundle exec bootsnap precompile app/ lib/

# Precompiling assets for production without requiring secret RAILS_MASTER_KEY
RUN SECRET_KEY_BASE_DUMMY=1 ./bin/rails assets:precompile

# Final stage for app image
FROM base

# Install packages needed for deployment
RUN apt-get update -qq && \
    apt-get install --no-install-recommends -y curl libsqlite3-0 libvips && \
    rm -rf /var/lib/apt/lists /var/cache/apt/archives

# Copy built artifacts: gems, application
COPY --from=build /usr/local/bundle /usr/local/bundle
COPY --from=build /rails /rails

# Run and own only the runtime files as a non-root user for security
RUN useradd rails --create-home --shell /bin/bash && \
    chown -R rails:rails db log storage tmp
USER rails:rails

# Entrypoint prepares the database.
ENTRYPOINT ["/rails/bin/docker-entrypoint"]

# Start the server by default, this can be overwritten at runtime
EXPOSE 3000
CMD ["bin/bundle", "exec", "foreman", "start"]

This is my output, haven't change a bit no matter what I tried

The empty envs are the ones that Coolify is supposed to add

I get the same result as @dmfigueroa on coolify v4.0.0-beta.319

same, issue with v4.0.0-beta.323, it ignores the ENV statement when is run in coolify. Minimal Dockerfile:
FROM python:3.11

# Install Poetry
ENV POETRY_HOME=/opt/poetry
ENV PATH="$PATH:$POETRY_HOME/bin"
RUN curl -sSL https://install.python-poetry.org | python3 - --version 1.8.3

# Test poetry is found
RUN echo $(poetry --version)

[ ] We should add a checkbox in the developer view to set all variables as build variables at once.
[ ] Also test if you paste the envs in the developer view and then switch to normal and set them as build variables if that is working correctely.

Hey everyone! Is this fixed? I'm using coolify 4 beta 370 and I'm still unable to pass env vars to dockerfile buildpack.
My use-case is to allow database connection to be able to use new Prisma TypedSQL, it demands a db connection to generate types: https://www.prisma.io/docs/orm/prisma-client/using-raw-sql/typedsql
I've checked to be "Build variable":

docker-compose.yml
    environment:
      - DB_HOST=${DB_HOST}
      - DATABASE_URL=${DATABASE_URL}
      - DIRECT_URL=${DIRECT_URL}

Dockerfile
ARG DATABASE_URL
ARG DIRECT_URL
ARG DB_HOST

RUN env

output
2024-Nov-26 14:49:39.036381
#20 0.208 NODE_VERSION=22.11.0
2024-Nov-26 14:49:39.036381
#20 0.208 YARN_VERSION=1.22.22
2024-Nov-26 14:49:39.036381
#20 0.208 SHLVL=1
2024-Nov-26 14:49:39.036381
#20 0.208 HOME=/root
2024-Nov-26 14:49:39.036381
#20 0.208 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
2024-Nov-26 14:49:39.036381
#20 0.208 PWD=/usr/app


failed to attach BPF xdp to device docker0:

I am trying to use gobpf, following is the snippet. Program fails to attach to an interface.
    module := bpf.NewModule(src, []string{})
    fn, err := module.Load("tcp_filter", C.BPF_PROG_TYPE_SOCKET_FILTER, 1, 65536)
    if err != nil {
            fmt.Fprintf(os.Stderr, "Failed to load xdp prog: %v\n", err)
            os.Exit(1)
    }
    err = module.AttachXDP(device, fn)
    if err != nil {
            fmt.Fprintf(os.Stderr, "Failed to attach xdp prog: %v\n", err)
            os.Exit(1)
    }_

bpf: Attaching prog to docker0: Invalid argumentFailed to attach xdp prog: failed to attach BPF xdp to device docker0:
Any idea as to why i get this error ?

I guess the problem is that only XDP programs (BPF_PROG_TYPE_XDP) can be attached as XDP.

Thanks for the reply iaguis.
I did not find anything in module.go to attach it socket. Is there a way at all ?

There is a test case to use socket filter
https://github.com/iovisor/gobpf/blob/88f8fa14ec93d0b99775e6696ea033f11c7d9400/bpf_test.go#L439
Sample example of socket filter
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/samples/bpf/sockex1_user.c
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/samples/bpf/sockex1_kern.c
On Thu, Jul 11, 2019 at 8:45 AM kkbrat9<EMAIL_ADDRESS>wrote:

Thanks for the reply iaguis.
I did not find anything in module.go to attach it socket. Is there a way
at all ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/iovisor/gobpf/issues/191?email_source=notifications&email_token=AAJ6PM7KJSE52DLD63PBQ2DP642OLA5CNFSM4IAF5UKKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZWX2AA#issuecomment-510491904,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJ6PM32INCVUJDDB5KAVQTP642OLANCNFSM4IAF5UKA
.

gobpf elf have socketfilters defined
type Module struct {
        fileName   string
        fileReader io.ReaderAt
        file       *elf.File

        log                []byte
        maps               map[string]*Map
        probes             map[string]*Kprobe
        uprobes            map[string]*Uprobe
        cgroupPrograms     map[string]*CgroupProgram
        socketFilters      map[string]*SocketFilter
        tracepointPrograms map[string]*TracepointProgram
        schedPrograms      map[string]*SchedProgram

        compatProbe bool // try to be automatically convert function names depending on kernel versions (SyS_ and __x64_sys_)
}

While gobpf bcc does not
type Module struct {
        p              unsafe.Pointer
        funcs          map[string]int
        kprobes        map[string]int
        uprobes        map[string]int
        tracepoints    map[string]int
        rawTracepoints map[string]int
        perfEvents     map[string][]int
}


MVP pollish: Fix the back button

ACs:

Fix the back button, this probably involves just using the history library correctly.
When the back button works, we can make this change without making the app unusable: Hide the footer in task detail and article detail pages.

See https://github.com/pg-irc/pathways-frontend/issues/130 & https://github.com/pg-irc/pathways-frontend/issues/102

I have confirmed the issues outlined in the two aforementioned issues.  It appears, when observing location state in redux, that there is a "previous path" or something along those lines that does appear to have accurate path values for the previous page although the back() call appears to take from the history stack which works as outlined in #130.


controller, overlay-network reconciler: Create NetworkAttachmetDefinition

On update/create of OverlayNetwork, create corresponding
NetworkAttachmentDefinition.
The NetworkAttachmentDefinition is created with OwnerReference [1] pointing to
the reconciled object.

This change sets basic the net-attach-def CNI network config.

Changes: resolve review comments

NAD rendering is also moved to its own package.
subnets validation is changed to use builtin net package instead of k8s.


System Admin UI: Display contents of System_Job_Log

Show the last run details for each job (grouped by job name and entity kind)

Option to view history of each job

Add SKIPPED to JobStatus enum

Rohit, is this something you are asking for us to implement or are you intending to contribute this code ?


[fix][sys] login ad file addon is shown on password policy or menu setting

Coverage decreased (-7.9%) to 58.856% when pulling b8a627817935083d774a75e39eb6d13fb2069f7a on sunny4381:fixes/login-ad-addon into 32bf2d6762ded2768a0fc40870f79b62a4da7f41 on shirasagi:master.


Generalize attention fusion

Comeplete solution for #2812
Changes (applicable when mlir attention is enabled):

No longer use gemm_softmax_gemm matcher in prefuse_ops pass
Add matcher for softmax base ops
Look for dot -> fused_reduce -> dot (-> pointwise) pattern in fuse_mlir pass

for valid attention fusion, fused_reduce should end with softmax base ops
create a single fused module consisting of these ops

Verified that the attention fusion works as before on various transformer models in our nas (bert, gpt, etc.)

@pfultz2 @causten
I added a commit here to accept graphs with the extra reshape here, it should fix perf regressions related to that issue. This can probably be generalized to accept some number of shape ops, I think that can be a topic for a separate PR.


⚠ Bofrost.at has degraded performance

In 56c6fad, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1559 ms

Resolved: Bofrost.at performance has improved in 5506d57 after 15 minutes.


cmock: can't use :subdir option because of the way generated c files are added to the MOCK_GENERATED_SRCS list (IDFGH-12326)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
Hello,
While trying to play with CMock for my project I noticed that it is not possible to mock component that use some kind of namespaced headers (e.g #include <myproject/logic.h>) and for that use :subdir option from CMock.
The issue is caused by the way mocked files are added in: https://github.com/espressif/esp-idf/blob/60a2bf6a68867fd468a250966230a067f8d97ea2/tools/cmake/component.cmake#L553
Every mocked files are expected to be directly under /mocks/, is it possible to maybe add another configuration option to idf_component_mock to specify a SUBFOLDER ?
Since the :subdir option is closely related to :mock_path maybe it would be useful to have by default mocks and something else if specified otherwise ?

Example of mock_config.yaml used :
:cmock:
  :subdir: "myproject"
  :plugins:
    - :ignore
    - :callback

Currently, the build fails because it will not be able to find the c files generated under mocks/myproject/Mock<...>.c and expect c files mocks/Mock<...>.c.

Hi @BastienGermond! It seems that there are two different aspects here:

The place where the generated mock implementations are placed.
Problems including the correct header files.

Do you have problems with both or just one of these aspects?
Regarding 1.: Usually, it shouldn't matter where the source files (*.c) are placed, the includes are absolute paths. Furthermore, the IDF build system should take care of setting up the compiler calls so all source files are found. Do you have source files with the same name which would conflict with each other after the mocks have been generated?
Regarding 2.: This should also work as long as the include directories  are set in the CMakeLists.txt of your mocking component (the one that is creating the mocks).

Hi @0xjakob,

The place where the generated mock implementations are placed.

The issue is that the files generated with the cmock_configuration :subdir: myproject would be created in this path ${MOCK_GEN_DIR}/mocks/myproject/Mock${file_without_dir}.[ch].
What I'm trying to say is that currently the path is hardcoded expecting the default values from CMock (:subdir: "", :mock_path: "mocks" and :mock_prefix: "Mock").
In case we have a mock_config.yaml like this :
:cmock:
  :subdir: "myproject"
  :mock_prefix: "Espressif"
  :mock_path: "EspMocks"
  :plugins:
    - :ignore
    - :callback

This would generate files following this path : ${MOCK_GEN_DIR}/EspMocks/myproject/Espressif${file_without_dir}.[ch]

the IDF build system should take care of setting up the compiler calls so all source files are found.

https://github.com/espressif/esp-idf/blob/60a2bf6a68867fd468a250966230a067f8d97ea2/tools/cmake/component.cmake#L552-L553
https://github.com/espressif/esp-idf/blob/60a2bf6a68867fd468a250966230a067f8d97ea2/tools/cmake/component.cmake#L558-L560
And because of this different path the c-files are not registered correctly (and thus not found/compiled during compilation causing missing symbols during linking).

Problems including the correct header files.

I also have this problem caused by not using :subdir, in my project I use a #include "myproject/nvs.h" but generating mocks for this without subdir will include "nvs.h" and not the expected "myproject/nvs.h" in Mocknvs.h.
I patched it the first time the same way esp-idf does for freertos with adding manually my correct header with :includes_h_pre_orig_header.
https://github.com/espressif/esp-idf/blob/60a2bf6a68867fd468a250966230a067f8d97ea2/tools/mocks/freertos/mock/mock_config.yaml#L2-L4
CMock still add an #include "nvs.h" in the mock header generated but at least this added afterward the correct #include "myproject/nvs.h".
However, in case the "nvs.h" was not something found in any include path or something that is not wanted in this header, the compilation will fail with an include not found error or maybe collide with the right header (myproject/nvs.h).

I apologize if my explanation was unclear. Please let me know if you did not catch what I mean and I will try to rephrase it :smile:.

It starts to make much more sense now, thanks! Supporting :subdir: makes sense then, in particular because of the includes.
Regarding support for custom :mock_path: and :mock_dir:: I think we could also add that option, although I don't quite understand why they are necessary. Taking :subdir: aside, is there a situation where you have a custom :mock_path: or :mock_prefix: configured in IDF?

Taking :subdir: aside, is there a situation where you have a custom :mock_path: or :mock_prefix: configured in IDF?

Not really, and I agree that I don't see a use case right now. Maybe some company may have some convention about filename enforced by tools ?
I was mentioning them only since they will not work with the current process, the real issue for me was the missing :subdir support.


introduce TraceDetails and modify some APIs

Signed-off-by: zhongzc<EMAIL_ADDRESS>The total duration is needed. Introduce an elapsed_ns to represent time diff from enabling to collecting.

Maybe move and modify some APIs to a independent PR is better.

Got. WIP

Done. PTAL @Renkai


Cannot create two influx databases on the same node from ays

Influxdb uses two ports one of them is configurable through ays and the other is not. So creating a service even with a different port fails at creating the second service because the other port (8088) is already in use.

Software Version
96700d6f42264111ba2d06cea4dfce6d29aff13b


Changing Case

Due to difference in case, multiple section created in ARM documentation - https://docs.microsoft.com/en-us/rest/api/monitor/scheduledqueryrules
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[ ] The title of the PR is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[ ] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[ ] If applicable, the PR references the bug/issue that it fixes.
[ ] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[ ] I have read the contribution guidelines.
[ ] My spec meets the review criteria:

[ ] The spec conforms to the Swagger 2.0 specification.
[ ] The spec follows the guidelines described in the Swagger checklist document.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

Automation for azure-libraries-for-java

Automation for azure-sdk-for-python

Automation for azure-sdk-for-node

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-go


crypto/x509: SystemCertPool return nil, nil on NaCl

It should return an error if no CertPool was available.
SystemCertPool is similarly limited on Windows, but there it returns a custom error.
https://play.golang.org/p/0llHDstj2Hp

Duplicate of #21405


bug: Multi-line string literal comments parsed as expression_statement instead of comment

Did you check existing issues?

[X] I have read all the tree-sitter docs if it relates to using the parser
[X] I have searched the existing issues of tree-sitter-python

Tree-Sitter CLI Version, if relevant (output of tree-sitter --version)
No response
Describe the bug
Multi-line string literal  comments parsed as expression_statement instead of comment
Steps To Reproduce/Bad Parse Tree

Parse a python class definition like below:

class Hello:
  """
  A test hello class
  """
  def __init__(self):
     pass

The parsed Tree for Hello class body , child 0 which is expected to be a comment is parsed as an expression_statement

Expected Behavior/Parse Tree
Would have expected a 'comment' Node , getting expression_statement
Repro
# Example code that causes the issue
class Hello:
  """
  A test hello class
  """
  def __init__(self):
     pass

Those are strings, not comments. This is expected.

Those are strings, not comments. This is expected.

Thanks for the clarification


Cant run modpack on AMD system

Hi,Thanks for your work.
Im trying to run this pack on AMD machine(AMD 5900X + AMD 6800XT),but I can only get 1-3FPS .
Im not sure which part I need to change .
Would you mind give me any suggestion? Thank you very much

@kuma-zhao , mod author was recommending to have optifine included/installed on your AMD machine. Also double check how much ram you have assigned (I run 12 GB, but 10 GB minimally). This fixed some issues for folks on my server.

To run this pack smoothly I'll recommend to allocate about 10GB to 12GB amount of RAM.
Also is fully recommended to add OptiFine mod.

hi Taylor
Thanks for your reply!
I will check the mod file and ram again to see if  I can work it .
Taylor Bonar @.***> 于2022年8月31日周三 02:47写道：

@kuma-zhao https://github.com/kuma-zhao , mod author was recommending
to have optifine included/installed on your AMD machine. Also double check
how much ram you have assigned (I run 12 GB, but 10 GB minimally). This
fixed some issues for folks on my server.
To run this pack smoothly I'll recommend to allocate about 10GB to 12GB
amount of RAM.
Also is fully recommended to add OptiFine
https://www.curseforge.com/linkout?remoteUrl=https%253a%252f%252foptifine.net%252fadloadx%253ff%253dOptiFine_1.16.5_HD_U_G8.jar
mod.
—
Reply to this email directly, view it on GitHub
https://github.com/DexxKnight1/Age-of-Fate-1.16.5/issues/19#issuecomment-1231976429,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQXEU6QPSDKESYRXMNXH4N3V3ZCKXANCNFSM554ZBRRQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


Add definitions for cgroupfs and cgroup2fs MAGIC

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @gnzlbg (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

I think CI failure is not related to my changes

@MikailBag Looks good! Could you rebase to check current CI status?
r? @JohnTitor

@JohnTitor I rebased on master.


Windows ARM support

Is your feature request related to a problem? Please describe.
Even though waveterm works well on windows11 arm64 using emulation and the x64 installer, I am sure a native version would run even better.
Describe the solution you'd like
I would kindly ask to add an arm64 build if possible

Hey, we're waiting on some GitHub to add GA support for Windows ARM runners before we add this. Right now, they ship a barebones runner with no tools installed. The main holdup for us making these barebones runners work is that Ruby doesn't have a Windows ARM version (see https://github.com/oneclick/rubyinstaller2/issues/362) and I'm not going to spend time building it myself

This issue is also blocking our Windows ARM support: https://github.com/actions/partner-runner-images/issues/19


Bugfix empty array values

Fixes bug which occur when we trying to POST or PUT entity with empty value (which means the array value is "null")
Sometimes Shopware has a problem when you try to post an array with some null values. We fix this by complete unsetting the array elements with null value.

Hey there, your PR is failing...


improve the performance of dbs file insert

fixes #8740

Not tested. One other question I have is whether we need to add unmerged ACDC files in DBSBuffer.
I guess if we have parents files we need to add it to tract it but in case we don't have parents we might not need this. (In that case, I can create another patch to skip that)

@amaltaro, Alan I added code to skip the unmerged acdc files without parents for inserting dbsbuffer.

You're right Seangchan. I mixed things up and I thought that comparison wouldn't work, sorry!

You're right Seangchan. I mixed things up and I thought that comparison wouldn't work, sorry!

I thought you just want to improve the code. :smile: I updated the patch anyway.

Seangchan, I didn't test it after you added the /store/unmerged handle, but it should be fine to go in for further tests.

and we might have to push this fix in to vocms0254, which is struggling with an ACDC workflow (almost 200k files):
vlimant_ACDC0_task_SUS-RunIIFall17wmLHEGS-00016__v1_T_180807_032626_4371


Default tag does not get overriden.

Hi, Im trying out version 5.0.0-alpha.0 and have noticed new behavior with tags.
As mentioned in #916

This means that the default tag (the handler function name by default) will be added if not overridden with the tag attribute.

However, I do not experience this behavior.
Using this configuration
#[derive(OpenApi)]
#[openapi(
    paths(
        super::handlers::accounts_handler::get_account,
         ...
    ),

and
/// Get Account
///
/// Gets a specific account of the user with metadata.
#[utoipa::path(
    get,
    path = "/api/users/:user_id/accounts/:account_id",
    tag = "Accounts",
    responses(
        ...
    ),
    params(
        ...
    ),
    security(
      ...
    )

)]
pub async fn get_account(

My openapi spec generates like this
"/api/users/:user_id/accounts/:account_id": {
      "get": {
        "tags": [
          "Accounts",
          "super::handlers::accounts_handler"
        ],
        "summary": "Get Account",
        "description": "Gets a specific account of the user with metadata.",
        "operationId": "get_account",
...

This results in my redoc view having double of everything.
Reproducable example can be found here
https://github.com/EinarasGar/myra/blob/crate-update/server/api/src/openapi.rs
https://github.com/EinarasGar/myra/blob/crate-update/server/api/src/handlers/accounts_handler.rs

Got the same problem. You have to add an import statement for what you are using as a path or an api. In your case this should fix it, if super works the same as crate:
use super::handlers::accounts_handler::get_account;

#[derive(OpenApi)]
#[openapi(
    paths(
        get_account,
         ...
    ),

I see the same issue here. But my handler and the #[derive(OpenApi)] are in the same module, so I do not need to import.
In the generated spec I see my custom tag, as well as the module name.
#[derive(OpenApi)]
#[openapi(
    tags((name = "Authentication", description = "Authentication operations")),
    paths(authenticate, refresh),
    components(schemas(
        Credentials,
        RefreshCredentials,
        AuthenticationResult
    ))
)]

Solved it: Had to import the classes for nest() the same way as described in https://github.com/juhaku/utoipa/issues/955#issuecomment-2155553055

While that works as well, there was a bug in the tags support that caused havoc. This is also elaborated here #978 And should be fixed here #1002.


Pause Democracy Earth Investor Community App Reviewer

We have seen multiple issues arise with some of the challenges presented by involving the Token holding community as voters (e.g. #72 and #66) but the biggest questions are around voter engagement and incentives. The concept is great in principle, and the Democracy Earth team has been an incredible partner with many exciting projects ahead. But the open questions could take many months of research to properly solve. We are most interested in moving App Mining forward in the most equitable way possible. In this forum post, we propose pausing Democracy Earth as an app reviewer. Thoughts and feedback welcome.

Makes sense!

I would have to agree in pausing democracy earth.  There isn't enough engagement from the investor side and is not a great representation of the full breadth of "token" holders

I am in full support of this!

I support it - unless there is a way to make a fix or drive engagement up. It is a great signal, but unfortunately it doesn't seem like it is ongoing from the voters.

Thanks to everyone for the review and input. We are proceeding with pausing Democracy Earth as a reviewer starting in May.


fix(module:message): fix container instance not exposed

close #3845
PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/NG-ZORRO/ng-zorro-antd/blob/master/CONTRIBUTING.md#commit
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Application (the showcase website) / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: #3845
What is the new behavior?
Does this PR introduce a breaking change?
[ ] Yes
[x] No

Other information

@cipchk You can try to build from this PR and try it with your demo. It should work now.

@wendzhue Yes, already working in HMR mode (includes other projects).


[FEAT]: GPT4ALL + sBert (RAG/Localdocs)

What would you like to see?
Would like to see support for Gpt4all and sBert plugins.

What specifically from GPT4ALL, like being able to use it as your LLM? Do you have any documentation on sBERT plugins - that is not something I'm familiar with.

You should be able to select one of the local llm options and put in your Gpt4All server mode endpoint there, as they all follow the openAI API standards. As an example, I am using llamafile for inference, and I put my llamafile endpoint into the LocalAI option


Yarn

Use the Yarn package manager instead of npm

Coverage remained the same at 47.212% when pulling 21f75e5dd9e687a724b9b6faa6025a1c7590eaea on yarn into 2a6155213509a0677b737f6015d62339a3a63d2c on master.

Current coverage is 40.99% (diff: 100%)

Merging #207 into master will not change coverage

@@             master       #207   diff @@
==========================================
  Files            33         33
  Lines          1305       1305
  Methods         180        180
  Messages          0          0
  Branches        166        166
==========================================
  Hits            535        535
  Misses          770        770
  Partials          0          0

Powered by Codecov. Last update 2a61552...75f121c

Coverage remained the same at 47.212% when pulling 0c49be126b2b7ce1f45b1fa6ba2d0b3ba8e14992 on yarn into 2a6155213509a0677b737f6015d62339a3a63d2c on master.

Coverage remained the same at 47.212% when pulling 954bb8c6f0b39a90096ef25eae83bbafb8fd355e on yarn into 2a6155213509a0677b737f6015d62339a3a63d2c on master.

Coverage remained the same at 47.212% when pulling 5e260e20acd3adec31904fbf94fdcfdea0ea63b5 on yarn into 2a6155213509a0677b737f6015d62339a3a63d2c on master.

Coverage remained the same at 47.212% when pulling cf87ae53215f018d84c59a67e36a5d759b3ae0a3 on yarn into ef3ce9adddd6f5344972209e00589c0e357dfc9f on master.

Coverage remained the same at 46.886% when pulling 4845dc1eb12bdb1df2f33a2d3cdaa7fcfa6f7344 on yarn into aa88c3b4e07578fb53ad676bdb343513b6216411 on master.

Coverage remained the same at 46.886% when pulling 4845dc1eb12bdb1df2f33a2d3cdaa7fcfa6f7344 on yarn into aa88c3b4e07578fb53ad676bdb343513b6216411 on master.


refactor [redmine] plugin rating services

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @chris48s!

  Generated by :no_entry_sign: dangerJS


OTE-02: Updating J-FRAME values

Updating J-FRAME V2Ref, V3Ref, and V3IdlYAngle values, along with pre-delivery data as part of OTE-02.

@tonysohn has watched these changes and gives approval to this PR


Extend lpc55-builder and update quickstart guide

This PR adds development provisioning to the lpc55-builder and updates the LPC55 quickstart guide for the NK3ANH.

@freswa @runcom Once you receive your NK3ANH devices, you can use the quickstart guide in this PR to get started.  Please let me know if you run into any issues or something is missing.

I’ve asked for assembly instructions and will let you know once we have something that can be published.  Still I recommend to first try the initial provisioning and flashing before assembling the casing because you might need to access the BL pin in case something goes wrong.

I continued working on this with the following Dockerfile (could still be optimized a bit with a build container):
FROM rust:latest
RUN apt-get update && \
    apt-get install -y python3 git curl llvm clang libclang-dev \
    gcc-arm-none-eabi libc6-dev-i386 make wget python3-toml usbutils libudev-dev
RUN git clone https://github.com/lpc55/lpc55-host.git
RUN cd lpc55-host && cargo build --release && cp target/release/lpc55 /usr/local/bin/
RUN cargo install flip-link cargo-binutils
RUN rustup target add thumbv8m.main-none-eabi
RUN cargo install cargo-binutils
RUN rustup component add llvm-tools-preview
WORKDIR /app

Unfortunately while trying to us the BL pins, the ribbon cable broke. I think the new design where the ribbon cable connector has been turned 180 ° makes the cable tangle up way more thus the longer cable part to the button comes off way easier.

❯ nitropy nk3 test --except provisioner
Command line tool to interact with Nitrokey devices 0.4.31
Usage: nitropy nk3 test [OPTIONS]
Try 'nitropy nk3 test --help' for help.

Error: No such option: --except Did you mean --exclude?

I guess you'll need to pull another release?
nitropy is also needed on the image for flashing the firmware.
Flashing the provisioner firmware and the develop firmware worked in the end.
I used another antenna, but unfortunately the button is pretty unreliable here, so the tests fail for me. Unsure if this is a Layer 8 or a hardware problem. The changed connector is at least a problem for inserting the cable.

works like a charm - didn't test debugging tho


Add mv/cp commands that take typed input

The error message:
[WARN] ...nvim/lua/neo-tree/sources/filesystem/lib/fs_actions.lua:263 Could not rename the files

https://user-images.githubusercontent.com/24765272/153801933-25030e6c-7f9a-49d3-b16f-0957136daf27.mov
debug Info.
NVIM
NVIM v0.7.0-dev+1082-g046950f63
Build type: Release
LuaJIT 2.1.0-beta3

tested on
neo-tree.nvim commit: d20d630

I've added new mappings for filesystem:
        ["y"] = "copy", -- takes text input for destination
        ["m"] = "move", -- takes text input for destination

which will behave the way you want. You can also just change your r mapping to the new "move" command.

Sorry for my late reply, was busy about Unity things. Let me check this now :)

You can also just change your r mapping to the new "move" command.

It's a great success. Very satisfying result to me :) Let me close this now!


Feature request: Apply random for selected steps only

I wish that feature exist:
Select some steps with the shift button and only apply the gen function to these steps only. As per now random values are automatically applied to all steps.
Thanks for considering

+1 Great Idea for changing note and length of specific step!!!

+1 Great idea - would like this to work for pitch, gate and length if possible 👍


[AL] 'OnNextRecord' is not a valid trigger

Hey guys, I am trying to create a trigger in my extension, but VSC shows me, that my trigger is not a valid trigger...
Does anybody know, how to solve this?

Hi @malue19, can you provide us with the following information so that we can start investigating your issue?
Which version of the compiler are you using?
What is the error you are getting?
On which type of object are you using this trigger?
The OnNextRecord Trigger can only be used on pages and request pages.

Hi @qutreson,

The error message I get is:
[AL] 'OnNextRecord' is not a valid trigger local trigger OnNextRecord(Steps: Integer): Integer
The object I would like to extend is not a standard object of NAV, it is a page of my own extension.
The version of the AL Language Package I am using is 0.16.19969.

It is currently not possible to use this trigger on a page extension. It can currently only be used from a page or a request page object.
We will use this issue to track this issue if we consider making this trigger available from page extensions in the future.
In the meanwhile, what you can do, is create an event in the base page and raise this event in the OnNextRecord trigger on the page. Then, you can subscribe to it from your extension and re-use it there.

As a clarification: it is not possible to use the OnNextRecord trigger on base product pages (i.e. Customer Card), as the only way to modify these resources is through page extensions or event subscribers.

@epernst @bssi-danielf as this is a request for a new feature, please go ahead and post this to our Ideas forum at https://aka.ms/BusinessCentralideas, or vote up the idea if its already there. We're constantly monitoring top Ideas and will consider them for a future release.

The suggestion:
https://experience.dynamics.com/ideas/idea/?ideaid=f4c5909f-bbb1-eb11-89ee-0003ff45a9b7


export/csv: prepend a unique id to file name of csv exports

PR: https://github.com/cockroachdb/cockroach/pull/52547
From release notes:

Exported CSV files are now prepended with a long unique ID. This can help to mitigate situations where multiple export runs are written to the same directory, resulting in mixed data. This change does not prevent mixed data; rather, it makes it possible to identify files from distinct runs, so that an operator can clean up. [#52547][#52547] {% comment %}doc{% endcomment %}

Query ID (check PR?)

Closed by https://github.com/cockroachdb/docs/pull/9699


Remove trailing whitespace from selected creating link

What's going on
When editors select a word using double click the word and any trailing spaces are selected.
When converting the selected text into a hyperlink using the link action the full text including white spaces are moved into the “Text to display” portion of the link editor.
What is requested
It would be more productive if the trailing spaces automatically trimmed when created from a selected text portion.
Now the links appear a bit awkward if editors forget to remove the trailing white space manually.
image example:

Additional context
I believe the trimming should only occur when the “Text to display” is automatically populated from selected text.
If editors manually enter data in the “Text to display” field any whitespace should be preserved.

The 2.42.0 version has been updated.
If this issue has not been resolved, please reopen this issue.
Thank you.


Pytorch: DLL load failed: The operating system cannot run %1

hello.
as the title says, i am experiencing this problem when i preprocess the ljspeech dataset.
python preprocess.py --path /dataset_folder/ Traceback (most recent call last):   File "preprocess.py", line 4, in <module>     from utils.display import *   File "F:\Downloads\ForwardTacotron-master\ForwardTacotron-master\utils\__init__.py", line 6, in <module>     import torch   File "C:\Users\****\Miniconda3\envs\tacotron\lib\site-packages\torch\__init__.py", line 81, in <module>     from torch._C import * ImportError: DLL load failed: The operating system cannot run %1.
can someone help? thanks

Hi, this seems to be a version problem with pytorch and some other library. Did you try to switch to another pytorch version?


fix(denols): revert #2000

I found the root cause of denols problems its https://github.com/neovim/neovim/pull/19797
With that pr applied (and with this revert) denols works perfectly almost identical to vscode deno, its missing some features but I imagine those are out of scope for lspconfig.
Applying the revert now means that until nvim merges a fix https://github.com/neovim/nvim-lspconfig/issues/1998 and other problems will reappear.
I think that's an ok tradeoff because using single_file_support=true breaks workflow for other ppl see https://github.com/neovim/nvim-lspconfig/issues/2069
So my opinion is to just merge this and the user will have to wait for the fix in neovim it self.

Makes sense. Please rebase then will merge.

done


Overhaul how ballot papers work

embeds can probably be used to streamline the UX

I'm quickly realizing that depending on how this is implemented, it may fix #43 as well. It's probably worth visiting this ASAP to resolve that.

I will work on a quick prototype just to demonstrate the idea I had going


port clearMerge

System Info
nothing
Details
The merge function in resolve.rs is currently unable to correctly handle by_. Thus, we need to port the clearMerge from webpack.
Reproduce link
No response
Reproduce Steps
nothing

/assign @bvanjoi


SeriesHelper: Is it possible to set client in constructor?

I would like to set the client in the constructor of MySeriesHelper:
MySeriesHelper(client=self.db, time=timestamp.isoformat('T'), station=station, snow_depth=float(data[1]), fresh_snow=float(data[2]), air_temperature= float(data[3]))

What's the right way of doing this?

See the serieshelper.py example here: https://github.com/influxdata/influxdb-python/blob/master/examples/tutorial_serieshelper.py
I believe you'll want to extend the SeriesHelper class and pass in the client argument there.


Hide the menu button for Include and Exclude Lists section cards

Describe the solution you'd like
Hide the menu button for Include and Exclude Lists section cards that are currently disabled.

Closing due to duplicated ticket: #1843


⚠ ClamAV has degraded performance

In faae5bc, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 70 ms

Resolved: ClamAV performance has improved in 799c4f7.


PR comments in terraform format (instead of diff)

...to get even better highlighting here in GitHub

(inspired by seeing https://github.com/runatlantis/atlantis/pull/1751, which takes this even further)

@mdobosz-isp / @marcind: Any thoughts?

Thank you for the submission but we won't be merging this in.


Added documentation on how to configure Bolt to install Puppet agent without internet

The default puppet_agent::install task goes out to the internet and downloads things. This breaks in "air gapped" environments. I thought it would be an interesting example to add to the documentation in order to showcase the plugin-hooks feature using existing tasks.

Thanks @nmaludy!


Unable to select year on date picker

🐛 Bug Report

Clicking year on date picker shows years but does not allow years to be selected.
To Reproduce
Steps to reproduce the behavior:
Click date picker input, select year at top left, attempt to click year and its greyed out.
Expected behavior

I expect year to change when clicked

Link to runnable example or repository (highly encouraged)

https://akveo.github.io/react-native-ui-kitten/docs/components/datepicker/overview#rangedatepicker
UI Kitten and Eva version

Package
Version

@eva-design/eva
@latest

@ui-kitten/components
@latest

Environment information
On Website

@OmarKhattab this is most likely should be documented, but it's actually correct behavior.
In the examples from the documentation, there is no min and max props set. If those props are not set, the calendar will take props by default: min as the beginning of the current year and max as the end.https://github.com/akveo/react-native-ui-kitten/blob/04481cec49a78f859c4cde65a45b157770ea1439/src/components/ui/calendar/baseCalendar.component.tsx#L91


Can tensorflow.js decode MP4 video?

Can tensorflow.js decode MP4 video?

@caggl Could you please post this issue in tfjs repository ? You will get the right help there. Thank you!


[FLINK-19470][orc][parquet] Parquet and ORC reader reachEnd returns f…

…alse after it has reached end

What is the purpose of the change
Fix the issue that ORC and parquet reader reachEnd methods return false after it has reached end.
Brief change log

Fix the readers
Add test cases

Verifying this change
Added test cases
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

Is this related to https://github.com/apache/flink/pull/13479?


recipe button and survival gui

I did remove the old effect icons, but I still have the old file if needed

Can you give some screenshots of what it looks like in game?

I havent textured the recipe book yet, and in the second image, I am hovering over the recipe book button

A few notes:

I don't like that the recipe book looks too much like a regular book floating on the screen
Can you remove the white border along the bottom and right in the recipe window, or otherwise try to hide it among the rest of the UI?
The tabs have a much better colour than the body of the recipe book gui. Perhaps use that for all of it and make the unselected tabs a slightly darker shade?

I haven't addressed number 1 yet

oh and the book icon is the same as the current one from the pack


fix docker compose file

fix docker-compose.yml
and .env for docker-compose.yml

Thank you for your interest in this project! But I can't merge because I don't understand the use case of this. Could you explain, please?


Citation Addition

Hi @teixeirak,
I've been laying low on the Climate Portal the last few days as you re-work the folder organization, but I thought that maybe it would be okay to carry on with adding citations for original data sets.  That said, it seems that not all data sets are offer data users full citation information.  The format that I'm aiming for (unless a data source provides a full citation - then I keep their format) is:
Last, F., F. Last, and F. Last.  Year.  Data title ver #.  Edited by F.M. Last.  Repository Name.  DOI link [or link to data if no DOI available].  Accessed Year-0M-0D.
Is that alright with you, or do you have a different citation style that you'd prefer?
Take care,
Caly

Last, F., F. Last, and F. Last. Year. Data title ver #. Edited by F.M. Last. Repository Name. DOI link [or link to data if no DOI available]. Accessed Year-0M-0D.

I think that's good; thanks!

You can go ahead and add citations as direct edits; no need for me to review in pull requests.


Firefox can't find libnotify.so.4, falls back to XUL popups

Issue description
Firefox uses XUL-based notification OSD, because it seems to be unable to dlopen("libnotify.so.4"). The result is somewhat non-native look-and-feel (YMMV), as the OS integration's lacking. This seems to be a bug — rather than intentional omission — because libnotify is mentioned in the expression.
When started as env  LD_LIBRARY_PATH=$LD_LIBRARY_PATH${LD_LIBRARY_PATH:+:}/nix/store/67kcj066h5djf8g3j1566lrlm60a9p0s-libnotify-0.7.6/lib firefox notifications mostly work, so the derivation may possibly benefit from a small makeWrapper update.
I wrote "mostly" because there's an independent issue — notifications that have icon/image URL specified usually fail silently. This is caused by this Firefox bug, which seems to be fixed only in Firefox 50.
If desirable (I'm new to Nix), I think I can try to make a pull request for this, but not sure how it's best to approach things and what are the policies regarding Firefox packaging.
One idea I have is making a derivation for 50a2 Developer Edition (firefox-devedition?), with a wrapper including libnotify path. Or maybe even 50b1, which should be released tomorrow.
Another idea is to stick with the stable version but backport all the relevant patches to 48.0.2.
All of this if it's desirable to have libnotify support, of course (which, given that it haven't seen much use, could be somewhat unstable).
Steps to reproduce

With a DE that supports XDG Desktop Notifications via libnotify (I'm using KDE5), install firefox (not firefox-bin)
Make the browser emit some notification. One option is https://jsfiddle.net/yoshi6jp/Umc9A/
Notice the notification is non-native - just a window created by Firefox itself, completely alien to the desktop environment.
Run with LD_LIBRARY_PATH including ${libpng}/lib
Repeat the test above (keep the "icon" field empty), observe that now the notifications are native.

Technical details

System: 16.03.1299.a8e0739 (Emu)
Nix version: nix-env (Nix) 1.11.2
Nixpkgs version: 16.03.1299.a8e0739

Thanks!

I was able to backport the patches from v50 in my branch here: https://github.com/drdaeman/nixpkgs/commit/4fbdf15de47955c939c077f74189d0220def106e
Haven't tested it much yet, but seem to work for me.

The wrapper is a possible place to fix it, but I'm just testing a patch that should fix firefox-unwrapped already as I think that's better.

Works, but I'll re-test with ESR and thunderbird notifications before pushing.
As for the patch, I don't feel like reviewing such nontrivial stuff, leaving that to upstream 8-)

Great!
Yes, I totally understand the patch is absolutely non-trivial. While all I did was taking the 3 (out of 4 - I've ignored the OS X one) patches from the upstream's linked bug, applying them to the vanilla sources (resolving trivial merge conflicts and ignoring images as patch doesn't handle binaries), then replacing newer-style imgLoader::NormalLoader back to do_GetService("@mozilla.org/image/loader;1") and running diff on the result, it's still a complicated mess.
For ≤49, I guess it would make sense to make libnotify support optional (like it's with enableGTK3 etc) and opt-in, though — because of the bug, not everyone would appreciate silent loss of notifications to the OS integration. (Any chance of v50 inclusion in unstable? What's the policy on this?)
Thanks a lot!

Normally we don't add unstable or testing versions to nixpkgs – unless there's some specific reason. Firefox is quite a popular package, I believe, so I personally think we could have some firefox-unstable, especially if multiple people would want to use it...

@drdaeman: thanks a lot for finding a solution!
Do you have any idea why the same approach wouldn't work for thunderbird? (It's easiest to try $LD_LIBRARY_PATH, as that doesn't require a costly rebuild.)

Unfortunately, no, haven't checked Thunderbird yet. I'll try to take a look when the time'll permit (unfortunately, for me, this week's going to be a busy with other matters, so maybe on another weekend) and write here if I'll find something.
As for the Firefox - a "Developer Edition" derivation may be a good middle grounds. Technically, it's of beta-stability (currently 50a2, but personally I haven't ever had any issues for year), but Mozilla themselves market it to web developers, so it may be worthy of inclusion.


Add Arm Linux packages, build all Linux binaries with Docker/Depot in CI

This PR adds arm64 / aarch64 binaries for Linux, supporting both glibc and musl. This should allow using moon inside Dockerfiles built on M1 Macs, for instance.
Additionally, this PR uses an optimized Dockerfile for building all Linux builds (both x86 and arm64, for both gnu and musl). In order to avoid QEMU, it uses Depot builders to run the Arm builds on real Arm machines. ✨
The Dockerfile is optimized for caching all dependency crates on their own layer using cargo-chef. This should speed up the Docker build when third-party dependencies are not changed.
A few notes:

The release profile config is moved into .cargo/config.toml - cargo-chef modifies the root Cargo.toml while building the dependencies, so unless the release profile config is moved elsewhere, it won't apply during dependency caching and will bust the cache
The Dockerfile uses messense/rust-musl-cross as the environment for statically compiling moon, as that image supports both amd64 and arm64. The image does not supply openssl source, and instead they recommend using the openssl-src crate instead. We can do that here by enabling the reqwest native-tls-vendored feature
There are comments in the Dockerfile, but the basic idea is that you can select which binary you want to build via the --target flag, which will be built for the current --platform and placed on an empty scratch stage. Then via Docker's --output type=local,dest=. flag, you can copy that built binary to the current directory. The Dockerfile arranges the output layer to preserve the target/TARGET/release/moon structure, so it can unpack in the expected layer
Depot authentication happens via GitHub OIDC (the id-token: write permission), so no API token secrets are needed

There's not a clean way to test this in GitHub actions without just running it - I've run the builds locally via the depot CLI to verify that they work.

This is an absolutely fantastic PR. Thanks for doing this, much appreciated. Very stoked to be using Depot!
I left a few comments, but this PR is basically perfect.


[Bug] RayJob Volcano integration

Search before asking

[X] I searched the issues and found no similar issues.

KubeRay Component
ray-operator
What happened + What you expected to happen
When label RayJob with volcano scheduler and queue，ray operator crashes. Raycluster object would be created with no status. None of relevant cluster pod would be created. Rayjob is the sample job provided in examples.  This happens in both v.0.6.0 and v.1.0.0
Tried same setup for RayCluster, everything works as expected.
The log from ray operator is the following:
INFO    controllers.RayCluster  reconcileHeadService    {"1 head service found": "rayjob-sample-raycluster-klhw9-head-svc"}
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x13ad868]

goroutine 786 [running]:
github.com/ray-project/kuberay/ray-operator/controllers/ray/batchscheduler/volcano.(*VolcanoBatchScheduler).DoBatchSchedulingOnSubmission(0xc001758368?, 0xc008176500)
        /workspace/controllers/ray/batchscheduler/volcano/volcano_scheduler.go:55 +0xe8
github.com/ray-project/kuberay/ray-operator/controllers/ray.(*RayClusterReconciler).reconcilePods(0xc0003054f0, {0x194d558, 0xc008536ed0}, 0xc008176500)
        /workspace/controllers/ray/raycluster_controller.go:550 +0x23f
github.com/ray-project/kuberay/ray-operator/controllers/ray.(*RayClusterReconciler).rayClusterReconcile(0xc0003054f0, {0x194d558, 0xc008536ed0}, {{{0xc00812ee68, 0x8}, {0xc00814ab00, 0x1e}}}, 0xc008176500)
        /workspace/controllers/ray/raycluster_controller.go:340 +0xea8
github.com/ray-project/kuberay/ray-operator/controllers/ray.(*RayClusterReconciler).Reconcile(0xc0003054f0, {0x194d558, 0xc008536ed0}, {{{0xc00812ee68, 0x8}, {0xc00814ab00, 0x1e}}})
        /workspace/controllers/ray/raycluster_controller.go:158 +0x21e
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile(0xc00025edc0, {0x194d558, 0xc008536e10}, {{{0xc00812ee68?, 0x163d900?}, {0xc00814ab00?, 0x4045d4?}}})
        /opt/app-root/src/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.11.1/pkg/internal/controller/controller.go:114 +0x28b
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler(0xc00025edc0, {0x194d4b0, 0xc000d2f040}, {0x158c6a0?, 0xc006dccf00?})
        /opt/app-root/src/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.11.1/pkg/internal/controller/controller.go:311 +0x352
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem(0xc00025edc0, {0x194d4b0, 0xc000d2f040})
        /opt/app-root/src/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.11.1/pkg/internal/controller/controller.go:266 +0x1d9
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2()
        /opt/app-root/src/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.11.1/pkg/internal/controller/controller.go:227 +0x85
created by sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2
        /opt/app-root/src/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.11.1/pkg/internal/controller/controller.go:223 +0x31c
Reproduced steadily. Volcano works fine with RayCluster, it’s only problematic with RayJob.  (both v.6.0.0 and V.1.0.0)

Reproduction script
apiVersion: ray.io/v1alpha1
kind: RayJob
metadata:
name: rayjob-sample
labels:
ray.io/scheduler-name: volcano
volcano.sh/queue-name: kuberay-test-queue
spec:
entrypoint: python /home/ray/samples/sample_code.py
rayClusterSpec:
rayVersion: '2.7.0' # should match the Ray version in the image of the containers
# Ray head pod template
headGroupSpec:
...
Anything else
The immediate fix is pretty trivial. Not sure whether further refactor is desired.
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

@Jeffwan FYI

@zhiyi57

The immediate fix is pretty trivial

What fix is this? Would you be willing to open a PR with the fix?

@zhiyi57

The immediate fix is pretty trivial

What fix is this? Would you be willing to open a PR with the fix?

The basic fix is to check whether this filled is set or not before use it.
A better fix would be set default value on initialization. Not sure whether we would want a pr down on this road though.

Any updates of this issue?


[WiP] new number-parser library - incorporation

Hi everyone, for the past couple of weeks I have been working on a number-parser library. (the goal is to parse numbers written in natural language). A basic English only version is available here. I will constantly improve the library in the coming months. A detailed plan for the same is available here.
The current goals for the library include:-

Handling ordinal numbers (third, seventh, five thousand and sixth)
Support for multiple languages (similar to how date-parser allows user to contribute language specific nuances)
Supporting year specific lingo ( saying nineteen eighty as opposed to one thousand nine hundred and eighty).

The current PR removes away the need to have the hard-coded values for numbers in the data translation files. It also allows dates like 'thirty May two thousand and nine' to parse correctly.
Currently, the number-parser is called inside the 'get_date_data' function of 'DateDataParser' as that seemed to be called prior to parsing by all features ( except search ? ).
I would appreciate any inputs with regards to incorporation and bugs/features/ideas that you can think of for the number-parser library. Please feel free to raise issues in the library.
To test this update you will need to clone it from the GitHub link and install using 'pip install -e' , as it hasn't been updated in the dependency.

I guess related issues would be: https://github.com/scrapinghub/dateparser/issues/651, https://github.com/scrapinghub/dateparser/issues/239, and https://github.com/scrapinghub/dateparser/issues/46.

Hi @arnavkapoor !
I think we can move your addition to another place. Let me explain it.
Inside the get_date_data() method we find:

checking for the correct type
(your addition)
trying with provided date formats (parse_with_formats)
sanitization (sanitize_date)
for loop trying applicable locales

I would move it at least after the sanitization part. However, as number-parser will support different locales, it could be a good idea to add it inside the for loop, where we can pass directly the locale to number-parser.
This approach has some advantages and some disadvantages. Summarizing:
Pros:

If we don't implement any lang detection to number-parser, this will allow us to directly pass the desired locale.
In case we implement a sort of lang detection in number-parser, passing the correct language will save time.
We will be translating to the expected locale, so no mixing logic from different locales.

Cons:

This approach will call multiple times to the number-parser parser, even if there isn't anything to "parse", so it could more expensive.

As the disadvantage is not quite important, I think that I would proceed with the second approach.
We could add:
...
for locale in self._get_applicable_locales(date_string):
    date_string = parser.parse(date_string, locales=[locale.shortname])
    ...

If you like it, go ahead and add the locales parameter to the parse method in number-parser.
I added a list to allow to pass multiple possible locales, but you can also implement a locale parameter, up to you.
Let me know what you think about this.
On the other hand, we should add some tests to dateparser to ensure that this integration works, so you could also add some tests to this PR. Those tests should be as easy as testing different sentences with "natural written numbers" in different languages.
In any case, good job on this @arnavkapoor ! The progress is quite amazing! :rocket: :smile:

Ok, I've been looking at the code, and it seems that dateparser lang detection doesn't work when passing for example "one of january of two thousand eight", as "one" is not recognised as English.
We have here two options:

Improve the lang detection in dateparser
Make number-parser to autodetect the language and put it before the for  loop.

Even the second option could be good, in dateparserI think that the second option would be better as in this way we could avoid mixing languages logic (imagine we "translate" a sentence coming from Spanish, for example, and then we parse it in dateparser we use a wrong locale).
To implement the second option we could implement a function like is_a_number() in number-parser and use it inside dateparser (should be applied in the are_tokens_valid "any" check). This function could add an optional locale argument to ensure that we are using the expected locale. This function would check the passed string against the numbers (ordinal and cardinal) for that language.
Let me know if you have any other ideas.

By the way, number-parser is not supporting Python 2 (and I don't think it should be supporting it), so I think that this integration could come at the same time as a major release of dateparser without Python 2 support :tada: .
@Gallaecio what do you think?

It’s about time! :stuck_out_tongue:

Hi @arnavkapoor!
Do you need help with the tests/pipeline?
The Python 3.5 pipeline is expected to fail because of the f-strings. Don't worry about it because we will remove the Python 3.5 support in the next version, at the same time we release this change.
The other python versions are failing because of an issue with Arabian if I'm not wrong. Could you check it? Let me know if you need help or feedback.

Hi @noviluni , Yes I was investigating a bit about the failing test cases and it does seem that the failure wasn't due to number-parser. Though I am surprised that all cases with second are passing. Will look into this.
Also I was removing other hard-coded values for es , which basically was un and una. Doing this did cause a test-case to fail in test_languages - the string hace un horas. However
dateparser.parse("hace un horas") seems to be working correctly and returns a time one hour ago so I guess it's some intermediary transaltion which is not being performed.
Apart from this I tried out other strings like May twenty seventh , two thousand and seventeen and more similar cases and they seem to be working fine. So will also create a new tests/test_number_parser file (better name ? ) to add these cases. Apart from these I don't see any other major changes needed for incorporation.

@arnavkapoor
Great! Let me know when you are ready with the tests. I think a better name for the file would be test_natural_language_numbers or something similar, as we are not going to test the number_parser package but the result of using it.
Try to use real date examples in different languages, but you can also try with some polemic/weird cases and discuss them here if they are failing or you have any doubt.
If you check other tests in this package, you will see that they are written with the nose package (which is compatible with pytest), but I would prefer if you don't use those examples and you use pytest instead, as we migrated the test suite to it and it's better to write the new tests using pytest.
When having a moment I will check the failing tests, it is possible that we have to change them :+1: .

Hi @noviluni , I have added the test files. I did try using pytest , however there seemed to be some error. (will try fixing it)  For the time being I have created it with a similar structure as the other test files.
With regards to the actual test-cases :-

I did try looking out for actual instances of such dates online but couldn't find a large source. Mostly these cases arise for spoken language. I have added some cases based on what I could find. Would appreciate if others with the specific language knowledge can also contribute.
For Spanish there seems to be an el preceding the dates , however with this el dates aren't accurately detected , hence I have removed them for the time-being.
There is one error with number-parser whitespace handling with Hindi that I detected , for the other languages it works fine and returns the correct output '1999 11:08'. I will create a new issue in number-parser and resolve it.

>>> number_parser.parse("1999 11:08", "hi")
'199911:08'

Apart from this currently there are no tests for how this affects search functionality (and other features ?). So I will add them too.

Would appreciate all opinions and advice.

As this is not a breaking change but an improvement, I changed the milestone from 1.0.0 to 1.1.0.
We need to improve number-parser by adding support for more languages as well as improving the coverage before integrating it with dateparser.


Show Event Date and Weekday in same line

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
weekday appears above the date, which looks weird in hoursOnSameLine mode
Sun
18
Expected behaviour
put weekday next to the date
Sun 18
Possible Solutions
No response
Mode
Event (default)
Context / Reason
First, thank you for the great card!
I use "hoursOnSameLine" to get a compact view, but I would also like to show the weekday next to the event-date on the left side.
At the moment the weekday appears above the date, which looks weird in hoursOnSameLine card.
Is there a way to put it in front of the date instead?
A solution with cardmodder or a hint how to change the .js file would also be ok, if you don't have time to make a feature.
Code of Conduct

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

initial_view: listWeek
type: custom:atomic-calendar-revive
entities:

entity: calendar.arzttermine
icon: mdi:doctor
color: MediumBlue
entity: calendar.privates
color: DarkViolet
icon: mdi:account-multiple
entity: calendar.thomas
color: limegreen
icon: mdi:human-male
entity: calendar.events
color: mediumvioletred
icon: mdi:party-popper
entity: calendar.geburtstage_2
color: lightseagreen
icon: mdi:cake-variant
entity: calendar.jahrestage
color: firebrick
icon: mdi:calendar-month
entity: calendar.eva_dienstplan
color: HotPink
icon: mdi:briefcase
entity: calendar.feiertage_in_osterreich
color: gold
icon: mdi:calendar
maxDaysToShow: 7
maxEventCount: 20
showDate: false
showLoader: true
showNoEventsForToday: true
sortByStartTime: true
showNoEventDays: true
showLocation: false
showWeekDay: true
showMultiDayEventParts: true
showRelativeTime: false
hideFinishedEvents: false
showAllDayEvents: true
hoursOnSameLine: true
weekdayOnSameLine: true
refreshInterval: 120
cardHeight: 533px
fullDayEventText: ganztägig
noEventText: keine Termine
compactMode: false
titleLength: 24
showEventDate: true

As you can see, I tried nearly all options, I really love this very customizible card, thank you again :-)

Please could you install v9.0.0-beta.1 issues around  this should be resolved as part of that.
Let me know if you have any issues.

Hi, sorry for my late answer and thanks for your effort.
But I´m still not absolutely happy with it.
Why is the progress-bar now in the left column with the date? I'd like to have it right under the event, as it was before.
Please move it or tell me how to put it there. Thank you!

That was a bug, update to latest version and this is fixed

I did not say anything 😅🙊

Could it be that the bugfix no longer allows the weekday and date to be placed underneath each other instead of next to each other?
I use a stack-in card with a mushroom card as a header and now my calendar entries can no longer be properly aligned with the mushroom card. Previously, the weekday and date were underneath each other and I was able to align it perfectly with the calendar symbol at the top with ha-card and adjusting margin-left.
Or is there a way to set the distance between weekday/date and the event?
Now:

Before (Photoshop):


Leverage Cost Calculator

I love the project!
It would be fantastic to add a leverage cost calculator that calculates the leverage cost as an APR (rather than the current price per week day and weekend).
Would also be great to colour code the Trade box, for both Buy and Sell, and leverage - so a 2x leverage would be green a 5x would be blue etc. to avoid mis-clicks (which I have done many times).

Fantastic ideas, thanks for sharing, I will add them to my todo list!


Godeps clones all dependencies from the internet

Relevant pstree snippet from running make build:
https://gist.githubusercontent.com/juliusv/1a91e10cda75cded9889/raw/fa8bdd40d33720c472ba65fd2ecfe6e1ed50ce2a/gistfile1.txt
This shouldn't clone any of the external dependencies from GitHub (or elsewhere), since they are vendored.

cc @stuartnelson3


GPU computation failing with CUDA Driver: an illegal memory access was encountered (Linux)

Description
Some specific symbol evaluation fail with a CUDA error. I have reproduced this problem on:

mxnet 1.6 + CUDA 10.1
mxnet 1.6 + CUDA 11.2
mxnet 1.7 + CUDA 11.2

(didn't try mxnet 1.7 + CUDA 10.1). My GPU is a GTX 1650 Mobile.
Error Message
mxnet.base.MXNetError: Traceback (most recent call last):
  [bt] (11) /lib/x86_64-linux-gnu/libc.so.6(clone+0x43) [0x7fcfe137d293]
  [bt] (10) /lib/x86_64-linux-gnu/libpthread.so.0(+0x9609) [0x7fcfe1241609]
  [bt] (9) /lib/x86_64-linux-gnu/libstdc++.so.6(+0xd6d84) [0x7fcfcfe04d84]
  [bt] (8) /home/matteo/Git/mxnet-build/Build/Linux-x86-64/CUDA/mxnet/python/mxnet/../../lib/libmxnet.so(std::thread::_State_impl<std::thread::_Invoker<std::tuple<std::function<void (std::shared_ptr<dmlc::ManualEvent>)>, std::shared_ptr<dmlc::ManualEvent> > > >::_M_run()+0x4a) [0x7fcf900d826a]
  [bt] (7) /home/matteo/Git/mxnet-build/Build/Linux-x86-64/CUDA/mxnet/python/mxnet/../../lib/libmxnet.so(std::_Function_handler<void (std::shared_ptr<dmlc::ManualEvent>), mxnet::engine::ThreadedEnginePerDevice::PushToExecute(mxnet::engine::OprBlock*, bool)::{lambda()#4}::operator()() const::{lambda(std::shared_ptr<dmlc::ManualEvent>)#1}>::_M_invoke(std::_Any_data const&, std::shared_ptr<dmlc::ManualEvent>&&)+0x4e) [0x7fcf900dcb9e]
  [bt] (6) /home/matteo/Git/mxnet-build/Build/Linux-x86-64/CUDA/mxnet/python/mxnet/../../lib/libmxnet.so(void mxnet::engine::ThreadedEnginePerDevice::GPUWorker<(dmlc::ConcurrentQueueType)0>(mxnet::Context, bool, mxnet::engine::ThreadedEnginePerDevice::ThreadWorkerBlock<(dmlc::ConcurrentQueueType)0>*, std::shared_ptr<dmlc::ManualEvent> const&)+0x11d) [0x7fcf900dc8fd]
  [bt] (5) /home/matteo/Git/mxnet-build/Build/Linux-x86-64/CUDA/mxnet/python/mxnet/../../lib/libmxnet.so(mxnet::engine::ThreadedEngine::ExecuteOprBlock(mxnet::RunContext, mxnet::engine::OprBlock*)+0x11f) [0x7fcf900d91ff]
  [bt] (4) /home/matteo/Git/mxnet-build/Build/Linux-x86-64/CUDA/mxnet/python/mxnet/../../lib/libmxnet.so(+0x18ae22a) [0x7fcf900ff22a]
  [bt] (3) /home/matteo/Git/mxnet-build/Build/Linux-x86-64/CUDA/mxnet/python/mxnet/../../lib/libmxnet.so(mxnet::exec::FComputeExecutor::Run(mxnet::RunContext, bool)+0x6d) [0x7fcf900f143d]
  [bt] (2) /home/matteo/Git/mxnet-build/Build/Linux-x86-64/CUDA/mxnet/python/mxnet/../../lib/libmxnet.so(void mxnet::FusedOp::Forward<mshadow::gpu>(nnvm::NodeAttrs const&, mxnet::OpContext const&, std::vector<mxnet::TBlob, std::allocator<mxnet::TBlob> > const&, std::vector<mxnet::OpReqType, std::allocator<mxnet::OpReqType> > const&, std::vector<mxnet::TBlob, std::allocator<mxnet::TBlob> > const&)+0x9e5) [0x7fcf938e6585]
  [bt] (1) /home/matteo/Git/mxnet-build/Build/Linux-x86-64/CUDA/mxnet/python/mxnet/../../lib/libmxnet.so(mxnet::FusedOp::CompileCode(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, int)+0x1228) [0x7fcf938de8c8]
  [bt] (0) /home/matteo/Git/mxnet-build/Build/Linux-x86-64/CUDA/mxnet/python/mxnet/../../lib/libmxnet.so(dmlc::LogMessageFatal::~LogMessageFatal()+0x72) [0x7fcf8ff79e92]
  File "/home/matteo/Git/mxnet-build/Build/Linux-x86-64/CUDA/mxnet/src/operator/fusion/fused_op.cu", line 672
MXNetError: CUDA Driver: an illegal memory access was encountered

To Reproduce
Download this json file then run the script:
sym.zip
import mxnet as mx

ctx = mx.gpu()
sym = mx.symbol.load('path/to/sym.json')
ex = sym.bind(ctx, args={"input": mx.nd.array([[1, 2, 3, 4]], ctx=ctx)})
outputs = ex.forward()
print(outputs)

What have you tried to solve it?
I'm building mxnet from source with cmake, and I also happen to be in possession of a 1.6 + CUDA 10.1 build (which is one of the combinations I've tried) which doesn't have this problem (but I don't have all the details on the settings/environment which produced it). This suggests that the problem can be fixed by some build settings, however I have spent significant time rebuilding with various settings and never managed to get anything.  Not installed from pre-built package or built from source.
Library      : ['/home/matteo/Git/mxnet-build/Build/Linux-x86-64/CUDA/mxnet/python/mxnet/../../lib/libmxnet.so']
Build features:
✔ CUDA
✔ CUDNN
✖ NCCL
✔ CUDA_RTC
✖ TENSORRT
✔ CPU_SSE
✔ CPU_SSE2
✔ CPU_SSE3
✖ CPU_SSE4_1
✖ CPU_SSE4_2
✖ CPU_SSE4A
✖ CPU_AVX
✖ CPU_AVX2
✔ OPENMP
✖ SSE
✖ F16C
✖ JEMALLOC
✖ BLAS_OPEN
✖ BLAS_ATLAS
✔ BLAS_MKL
✖ BLAS_APPLE
✖ LAPACK
✖ MKLDNN
✖ OPENCV
✖ CAFFE
✖ PROFILER
✖ DIST_KVSTORE
✖ CXX14
✔ INT64_TENSOR_SIZE
✔ SIGNAL_HANDLER
✖ DEBUG
✖ TVM_OP
----------System Info----------
Platform     : Linux-5.8.0-41-generic-x86_64-with-glibc2.29
system       : Linux
node         : pajarulo
release      : 5.8.0-41-generic
version      : #46~20.04.1-Ubuntu SMP Mon Jan 18 17:52:23 UTC 2021
----------Hardware Info----------
machine      : x86_64
processor    : x86_64
Architecture:                    x86_64
CPU op-mode(s):                  32-bit, 64-bit
Byte Order:                      Little Endian
Address sizes:                   39 bits physical, 48 bits virtual
CPU(s):                          16
On-line CPU(s) list:             0-15
Thread(s) per core:              2
Core(s) per socket:              8
Socket(s):                       1
NUMA node(s):                    1
Vendor ID:                       GenuineIntel
CPU family:                      6
Model:                           158
Model name:                      Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
Stepping:                        13
CPU MHz:                         4161.311
CPU max MHz:                     5000,0000
CPU min MHz:                     800,0000
BogoMIPS:                        4800.00
Virtualization:                  VT-x
L1d cache:                       256 KiB
L1i cache:                       256 KiB
L2 cache:                        2 MiB
L3 cache:                        16 MiB
NUMA node0 CPU(s):               0-15
Vulnerability Itlb multihit:     KVM: Mitigation: VMX disabled
Vulnerability L1tf:              Not affected
Vulnerability Mds:               Not affected
Vulnerability Meltdown:          Not affected
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp
Vulnerability Spectre v1:        Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:        Mitigation; Enhanced IBRS, IBPB conditional, RSB filling
Vulnerability Srbds:             Mitigation; TSX disabled
Vulnerability Tsx async abort:   Mitigation; TSX disabled
Flags:                           fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch
                                 _perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2
                                 apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi
                                  flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat
                                 pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d arch_capabilities

Can you try with the latest v1.x version? For example, https://repo.mxnet.io/dist/python/cu110/mxnet_cu110-2.0.0b20210202-py3-none-manylinux2014_x86_64.whl

Could you try v1.x with CUDA 11.1?

The version at the link provided by @leezu works (however mxnet.__version__ is 2.0.0 on that package and not 1.x)
I have tried to build the latest v1.x branch from source and I still find the same error
I have tried to build v2.0 (master) but the build failed to link with

/usr/bin/ld: ../libmxnet.so: undefined reference to `nvrtcGetCUBINSize'
/usr/bin/ld: ../libmxnet.so: undefined reference to `nvrtcGetCUBIN'

Anyway, let me repeat that I don't think this is a problem with the source code, but with the build procedure. As I have stated in the report, I am in possession of a 1.6 + CUDA 10.1 build (which is one of the combinations I've tried) which doesn't have this problem, but unfortunately I don't know the exact details/settings of that build. My build settings are in the report, what could be wrong there?

For your build settings: Do you need ILP64? Otherwise I suggest you disable DUSE_INT64_TENSOR_SIZE and ILP64.
Further, you don't need +PTX for the cuda arch. Just provide the correct Arch number for your gpu

Seems the nvrtcGetCUBIN' , nvrtcGetCUBINSize' were introduced in CUDA 11.1+. Did you install CUDA10.2 or CUDA11.2 in your system?

@leezu switching off USE_INT64_TENSOR_SIZE fixes the problem!
@TristonC I had both installed to make my tests and it's possible that I have set some path wrong when building/running v 2.0. Anyway, this doesn't matter anymore.
Anyway, this looks like a bug with USE_INT64_TENSOR_SIZE right? Should I open a separate issue for this?
Thank you


Added proper testing for cookie

@tomfuertes If it seems like I'm on the right path here I'll go ahead and build out the other browser-dependant tests. I couldn't think of a great way to test the cookie stuff, so I'll have to think on that a bit.

Yeah this is $$$ - :shipit:


force fact check of all nodes first thing

Fixes issue #414

+1 This doesn't add any extra time to deployment. Quick and simple solution.


feat: Sunrise AppVersion

Changes
add AppVerison variable in version/version.go
change Hardcoded App: 0 to this variable
now, set AppVersion = 2

PR checklist

[ ] Tests written/updated
[ ] Changelog entry added in .changelog (we use unclog to manage our changelog)
[ ] Updated relevant documentation (docs/ or spec/) and code comments

It solve this issue https://github.com/SunriseLayer/sunrise-node/issues/4


3 - US: As a server admin, images can be hosted on my server.

They're hosted for a short period of time until the dyno sleeps or is reinitialized

#63


boardd: reduce unnecessary allocations

@adeebshihadeh both before and after this PR the send vector allocated is way too large (and before this commit 3/4s of the data sent to the panda was garbage / null), since .size() and .resize() is in elements (4 bytes here) instead of bytes.
I refactored it a bit more in the multipanda PR #22402


Updated Infinite streaming sample

The new sample uses result_end_time to resend unfinalized results in subsequent requests.
Would like advice on making a test.

Noticed the Java 8 test failed.
I looked at the logs and it seems to be unrelated to the file I was working on.
This is for recognizeIT punctuation discrepancies in from an audio file:
expected to contain:
How old is the Brooklyn Bridge?
but was:
Transcript : how old is the Brooklyn Bridge
Is this blocking my PR even though it's on a different file?


[microTVM][Zephyr] Enable -O2 optimization on build by default

This PR adds CONFIG_SPEED_OPTIMIZATIONS=y to zephyr project generation by default which results in -O2 optimization for the zephyr project
cc @alanmacd @areusch @gromero @guberti

@gromero Here is a report. It seems to have minimal affect on building anomaly detection model
without -O2 optimization
[237/237] Linking CXX executable zephyr/zephyr.elf
Memory region         Used Size  Region Size  %age Used
           FLASH:      585968 B         2 MB     27.94%
            SRAM:      566544 B       640 KB     86.45%
        IDT_LIST:          0 GB         2 KB      0.00%

with -O optimization:
[237/237] Linking CXX executable zephyr/zephyr.elf
Memory region         Used Size  Region Size  %age Used
           FLASH:      601872 B         2 MB     28.70%
            SRAM:      566544 B       640 KB     86.45%
        IDT_LIST:          0 GB         2 KB      0.00%

@tvm-bot rerun

@tvm-bot rerun

@guberti yes, it improves performance for all mlperftiny models.