1 user story per person, due 1/26

[ ] Victor
[ ] Ashray
[ ] Brandon
[ ] Jason
[ ] Lucas
[x] Alexi: issue

Be sure to check the box and link your issue once it's done.

Questions for Kyle

Can we use Home Assistant Cloud?
Any thoughts before we dive into connecting local devices to the cloud HA instance?


Update readme to say tslint is depreciated

Honestly, you either make a PR, or make a good issue description, or...
Technically this package here is not deprecated, as we just support the legacy.

Sorry, I didn't mean to get on anyone's nerves. I just was a little irritated I set up tslint only to find that it is depreciated in the npm messages, had to uninstall, etc. It would be useful if there was at least some mention of tslint being depreciated in the readme / package manager for sublime text. Obviously that's up to you people though if you want something there or not.

Yeah, why not.  But of course we have lots of plugins for outdated/legacy linters.  A short PR is always welcome. 👍


Update Autoprefixer and migrate to enb-validation-code

Just tested it on my project, works fine.

/cc @mdevils @blond

ping

Hi!
In<EMAIL_ADDRESS>was broken backward compatibility: autoprefixer.default has been removed.
Need use browserslist. See https://github.com/postcss/autoprefixer-core/issues/26.

Added browserslist

Thanks!

Released in v0.3.0.

They returned back autoprefixer.defaults in next 5.1 version.
"Return autoprefixer.defaults as alias to current browserslist.defaults."
https://github.com/postcss/autoprefixer-core/blob/master/ChangeLog.md#51-jianyuan
And browserslist is dependency of autoprefixer-core itself:
https://github.com/postcss/autoprefixer-core/blob/master/package.json#L14


Adding date range selection. Fix for issue # 5

@indrimuska Can you please add any other reviewers that need to approve this for merging?


No selectable items in required fields

After upgrading from version 1.1.1 to 1.2.0 I encountered a problem. When trying to save model with blank required fields, items of chained selects are not load:

With Django 1.9.1 I have same problem, but unable to downgrade for django-smart-selects 1.1.1. Currently no usable version for 1.9.x.
My models:
class Continent(models.Model):
    name = models.CharField(max_length=255)

    def __str__(self):
        return self.name

class Country(models.Model):
    continent = models.ForeignKey(Continent)
    name = models.CharField(max_length=255)

    def __str__(self):
        return self.name

class Location(models.Model):
    continent = models.ForeignKey(Continent)
    country = ChainedForeignKey(
            Country,
            chained_field="continent",
            chained_model_field="continent",
            show_all=False,
            auto_choose=False
    )
    name = models.CharField(max_length=255)

    def __str__(self):
        return self.name

Demo project:
bug_demonstation.zip

Yes, we knew it and will fix it soon. Thank you.

fixed and released


Email delivery error: uninitialized constant OpenSSL::SSL::VERIFY_FALSE

Email delivery error: uninitialized constant OpenSSL::SSL::VERIFY_FALSE

Anyone get that?
So far as I can tell that is with this ENV added:
SMTP_OPENSSL_VERIFY_MODE=false

Closing due to old age


Needs a changeable background and color options please!!!!

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

+1

This is not possible because this library uses .gif files to load the spinners, that's why the color cannot be edited.
Perhaps it could be changed by applying a filter but that goes further.


Aggregation Typing not working as expected

Hey! Love the project, really hope Papr makes it big!
I'm trying to figure out how to get proper typing out of the aggregation pipeline. Docs reference that says this is possible:
https://plexinc.github.io/papr/#/api/model?id=aggregate

Returns:
Promise<Array<Aggregate>> A custom data type based on the pipeline steps

Given these two models:
import { types, schema } from 'papr';
import papr from '@db/papr';

export enum Kind {
  dog = 'dog',
  cat = 'cat',
}

const petSchema = schema({
  name: types.string({ required: true }),
  owner: types.objectId({ required: true }),
  kind: types.enum(Object.values(Kind), { required: true }),
});

export type PetDocument = typeof petSchema[0];

const Pet = papr.model('pets', petSchema);

export default Pet;

import { types, schema } from 'papr';
import papr from '@db/papr';

const ownerSchema = schema({
  firstName: types.string({ required: true }),
  lastName: types.string({ required: true }),
  address: types.object(
    {
      line1: types.string({ required: true }),
      line2: types.string(),
      city: types.string({ required: true }),
      state: types.string({ required: true }),
      zip: types.string({ required: true }),
      country: types.string({ required: true }),
    },
    { required: true }
  ),
  phoneNumber: types.string(),
});

export type OwnerDocument = typeof ownerSchema[0];

const Owner = papr.model('owners', ownerSchema);

export default Owner;

I would expect the below snippet to return a type where owner is fully enumerated, but I'm still seeing that it's type ObjectId. Actually the entire return type of the pipeline is just PetDocument.
When I add a project stage to this pipeline and try and select only a few fields, it also doesn't change the return type.
This does work at runtime as expected (ie I can get the owner.address off of the $lookup => $unwind). We just don't get type hinting from tooling and actually gives us some tsc errors (even though, again,  it works at runtime).
async function findPetsByOwnerState(state: string) {
  const res = await Pet.aggregate([
    {
      $lookup: {
        from: 'owners',
        localField: 'owner',
        foreignField: '_id',
        as: 'owner',
      },
    },
    {
      $unwind: '$owner',
    },
    {
      $match: {
        'owner.address.state': state,
      },
    }
  ]);

Supporting truly typed aggregate operations is out of the scope of papr. The MongoDB aggregation pipeline syntax is extremely complicated that adding support for this would be very difficult.
The papr docs around aggregate() should be clearer in this regard though. The following is currently supported:
const res = await Pet.aggregate<YourCustomType>([ ... ]);

With the caveat that you'll have to define your own result type based on the aggregation operations.

Thanks for the response!


Prom metrics

Adding section for documentation around the Prometheus Client Exporter

Small suggestion to move it above FAQ:


Integration of ElasticSearch request builder

This integrates the ElasticSearch request builder, that will generate a *elastic.SearchService based on given parameters.
The code as is, is not merge ready. Indeed, there are no unit tests written for it.

This code is now ready to merge, as unit tests have been added.
Please note that right now the function GetElasticSearchParams (the only exported function) is not tested as a local ElasticSearch is needed to test it.


Unsupported protocol scheme

A runtime error is observed with a certain collection:

Get : unsupported protocol scheme ""

Reported by @danni-popova in #43.

Example conversion result that hits the error.
// Auto-generated by the Load Impact converter

import "./libs/spo-gpo.js";
import "./libs/shim/core.js";
import URI from "./libs/urijs.js";
import aws4 from "./libs/aws4.js";

export let options = { maxRedirects: 4 };

const Request = Symbol.for("request");
postman[Symbol.for("initial")]({
  options
});

export default function() {
  postman[Request]({
    name: "discovery",
    id: "aa538977-373a-463b-937a-f371ddd71968",
    method: "GET",
    address:
      "https://{replaced_url}",
    auth(config, Var) {
      const address = new URI(config.address);
      const options = {
        method: "GET",
        protocol: address.protocol(),
        hostname: address.hostname(),
        port: address.port(),
        path: address.path() + address.search(),
        region: "eu-west-1",
        service: "cf"
      };
      const credential = {
        accessKeyId: "{replaced_access_key}",
        secretAccessKey: "{replaced_secret_key}"
      };
      const signed = aws4.sign(options, credential);
      const [path, query] = signed.path.split("?");
      config.address = new URI()
        .protocol(address.protocol())
        .hostname(signed.hostname)
        .path(path)
        .query(query)
        .toString();
      Object.assign(config.headers, signed.headers);
    }
  });
}

This might be something to do with the AWS auth logic.

I remember now I saw this and thought AWS requests require a query, so it wouldn't come up. It happens when the URL has no query string. You end up with undefined and it nulls out some later values.
I'll get a patch underway, but you can work around it by changing this line:
      const [path, query] = signed.path.split("?");

To this, to default query to the right type even when it's empty:
      const [path, query = ""] = signed.path.split("?");

@danni-popova

That worked! Thank you ever so much for looking into this!

Quite welcome!

Opened #47 to patch this.


Automatically generate list of notices that failed due to parsing problem

Describe the problem
As a user, I want to know which notices did not run when a validator fails, so that I'm not misled by false negatives. Right now, it's unclear which notices ran and which ones did not.
Proposed solution
Generate the list of notices that failed due to parsing issues with the validators.
Alternatives you've considered
No response
Additional context
Some investigation is required to determine how this could work with the code generated validators.

Duplicate of #1485


Invalid byte sequence in UTF-8 (in file name)

I'm syncing files on our server to S3 successfully. However, one particular directory - uploads (where people upload a variety of documents) - fails with the following:
2012/02/29 06:58:10][message]   Generating checksums for /storage/data/uploads
[2012/02/29 06:58:15][error] ModelError: Backup for Backup to S3 (cnbc_s3_backup) Failed!
[2012/02/29 06:58:15][error]   An Error occured which has caused this Backup to abort before completion.
[2012/02/29 06:58:15][error]   Reason: ArgumentError
[2012/02/29 06:58:15][error]   invalid byte sequence in UTF-8
[2012/02/29 06:58:15][error]
[2012/02/29 06:58:15][error] Backtrace:
[2012/02/29 06:58:15][error]   /home/mlarocque/.rvm/gems/ruby-1.9.3-p125/gems/backup-3.0.23/lib/backup/syncer/cloud.rb:101:in split' [2012/02/29 06:58:15][error]   /home/mlarocque/.rvm/gems/ruby-1.9.3-p125/gems/backup-3.0.23/lib/backup/syncer/cloud.rb:101:in local_files'
[2012/02/29 06:58:15][error]   /home/mlarocque/.rvm/gems/ruby-1.9.3-p125/gems/backup-3.0.23/lib/backup/syncer/cloud.rb:93:in `all_file_names'
It appears that one or more of the filenames has characters which backup doesn't like.
Any ideas?

Would validating the user's uploaded file names be an option?
I don't think backup should change the names, since those files when restored would be different.

I agree that validating file names should be done, and I believe it is now. These files are from a 5+ year old Rails app and there have been a ton of file uploads over that time. Perhaps it might be possible for backup to fail somewhat less spectacularly and identify the file that is causing the issue?

@mlarocque This has been taken care of in the 'cloud-syncers' branch if you're still needing this :)
https://github.com/meskyanichi/backup/tree/cloud-syncers
It will simply skip any file paths with invalid UTF-8 characters and log a warning with a reference to the skipped path.
There were other changes made and issues addressed in this branch, as well as those addressed in 'develop' (which cloud-syncers is based on). So, it may take several days before we're comfortable releasing a gem with these updates.
You can add this following to your Gemfile for now, so you can sync and identify those bad files.
gem 'backup',
  :git => 'git://github.com/meskyanichi/backup.git',
  :branch => 'cloud-syncers'


Team Member can assign engagements to other users even if they are not assigned to it themselves from UM Listing page

Team members should only be able to assign engagements to others if they are assigned to the engagement themselves.
Reported by Taya as a Team Member

Passing in DEV


Allow Bearer authentication

Allow OAuth2 Bearer authentication ( http://self-issued.info/docs/draft-ietf-oauth-v2-bearer.html ) for the backend.
Or at least, allow sending custom headers to the backend.
Use Case:
I am a customer and I have a backend that provides tiles but it needs an OAuth2 token in the header ( "Authorization: Bearer " header). I would like to use tangram to render the tiles, so I need a way to give tangram my Oauth2 credentials or at least be able to tell tangram to pass this custom header with a provided token.

Yep, I remember I looked at this a couple times. If I recall, one issue is that for CORS requests, custom headers need to be whitelisted by the server with Access-Control-Allow-Headers. And some more info/example here.
The Netzen tiles do not directly support this concept (though I suppose they could, and could mimic back the list of headers requested by the client, for example). But if the client is serving their own tiles (or maybe proxying another source), I believe it would work if configured properly. Worth trying a prototype.

Allowing sending custom headers as @matteblair  proposes would be the more generic solution, that will solve Auth problems, CORS problems, etc...
For the usecase: the user could manage getting a proper token and refresh it in custom code meanwhile.

@pakore re: my comments about Access-Control-Allow-Headers, that makes sense and fits into your workflow?

I currently don't have any problems with CORS because my server accepts all, but I think definitely is a use case that needs to be solved for other users also and allowing custom headers could be a solution.

See #670 for an implementation of this.

Released in v0.16.0


Level_name options

It would be great to have optional level_name name. For example NLog has feature to make level_name as 1, 3 letters or full name.
Current situation (log strings):
[2022-21-12 10:10:01.718][INFO][<IP_ADDRESS>] '6': user login
[2022-21-12 10:10:01.724][WARNING][<IP_ADDRESS>] '6': domain gmail.com is forbidden to use or does not exist
[2022-21-12 10:10:01.724][ERROR][<IP_ADDRESS>] '6': user email is forbidden to use
If set it level_name as 1 or 3 letters logs can be like this:
[2022-21-12 10:10:01.718][INF][<IP_ADDRESS>] '6': user login
[2022-21-12 10:10:01.724][WRN][<IP_ADDRESS>] '6': domain gmail.com is forbidden to use or does not exist
[2022-21-12 10:10:01.724][ERR][<IP_ADDRESS>] '6': user email is forbidden to use
[2022-21-12 10:10:01.718][I][<IP_ADDRESS>] '6': user login
[2022-21-12 10:10:01.724][W][<IP_ADDRESS>] '6': domain gmail.com is forbidden to use or does not exist
[2022-21-12 10:10:01.724][E][<IP_ADDRESS>] '6': user email is forbidden to use
It helps to read logs.
Idea do make option:
INFO = INF = I
ERROR = ERR = E
WARNING = WRN = W
DEBUG = DBG = D
and so on...

So this would be for LineFormatter only right? Probably could easily be added as an additional option via a setMaxLevelNameLength(1)?


API Design Requirements

Description
Started writing up design requirements for OpenKCC API overhaul.
Basically, the current api as of version 1.2.x is trying to satisfy too many users and not doing a good job at it. If someone wants to fully customize something they might as well use the lowest level APIs in KCCUtils and if someone wants another action or feature to add onto the basic KCC they have to write a whole new state machine.
So, let's rethink who will use the API, how they will use the API, and how to design the API to fit the different needs of stakeholders.

Squashing this PR to add the notes to the public website but we can review and update as needed in future changes :)


maintaining header when opening link

Is posible maintaining header when opening links inserted in a page(no in external link on menu). I try to modify href.coffee, but I can not do
thanks!

What do you mean by "maintaining"?

I want to show the menu bar when I open a link in a page.
For example now have a page with events, when I click on a links now opens external browser.
I want you to open the event show the menu bar

https://github.com/shprink/wordpress-hybrid-client/blob/develop/config/config.default.cson#L45-L48

I do not mean links on the menu, I mean links in the content of a page.
Thanks.

Yes @alcholever is right you can Achieve that through the conf.
Check the link and use the right config https://github.com/apache/cordova-plugin-inappbrowser#cordovainappbrowseropen


ForwardAuth Middleware - trustForwardHeader and authResponseHeaders cause 500 response

Do you want to request a feature or report a bug?
Bug
What did you do?
I got Traefik configured to route traffic to a Docker container via labels (with docker-compose). Then added the ForwardAuth middleware.
Simply adding the forwardauth.address middleware works fine: The 'address' returns 200 and Traefik forwards the request on.
Then I tried using the forwardauth.trustForwardHeader and forwardauth.authResponseHeaders middleware.
What did you expect to see?
I expected the responses to continue to come back as 200's.
What did you see instead?
Traefik started returning 500 responses. The ForwardAuth 'address' endpoint continued to return 200's, but an error started occurring when any combination of middleware was provided:

forwardauth.trustForwardHeader
forwardauth.authResponseHeaders
forwardauth.trustForwardHeader and forwardauth.authResponseHeaders

Traefik log:
reverse-proxy_1  | time="2020-01-03T05:37:00Z" level=debug msg="Error calling . Cause: Get : unsupported protocol scheme \"\"" middlewareName=svc1-forwardauth-headers@docker middlewareType=ForwardedAuthType

Output of traefik version:
Docker image
traefik:v2.1

What is your environment & configuration (arguments, toml, provider, platform, ...)?

Docker Compose
Traefik is hooked into the Docker Socket to get labels from the services.

version: '3.7'

services:
  reverse-proxy:
    image: traefik:v2.1
    command: --api.insecure=true --providers.docker --log.level=DEBUG
    ports:
      - "80:80"
      - "81:8080"
    networks:
      - api
      - default
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock

  svc1:
    image: containous/whoami
    ports:
      - target: 80
    networks:
      - api
    labels:
      - "traefik.http.routers.svc1.rule=PathPrefix(`/svc1/`)"
      - "traefik.http.middlewares.svc1-stripprefix.stripprefix.prefixes=/svc1"
      - "traefik.http.services.svc1.loadbalancer.server.port=80"
      # Each of these three will fail fail - meaning any combination of middleware fails
      - "traefik.http.routers.svc1.middlewares=svc1-stripprefix, svc1-forwardauth-address, svc1-forwardauth-trust, svc1-forwardauth-headers"
      - "traefik.http.routers.svc1.middlewares=svc1-stripprefix, svc1-forwardauth-address, svc1-forwardauth-headers"
      - "traefik.http.routers.svc1.middlewares=svc1-stripprefix, svc1-forwardauth-address, svc1-forwardauth-trust"
      # But this is fine
      - "traefik.http.routers.svc1.middlewares=svc1-stripprefix, svc1-forwardauth-address"

      # This alone works fine
      - "traefik.http.middlewares.svc1-forwardauth-address.forwardauth.address=http://validator:3000/verify"

      # But when including 'trustForwardHeader' or 'authResponseHeaders' middleware
      #  a 500 response occurs from within Traefik
      - "traefik.http.middlewares.svc1-forwardauth-trust.forwardauth.trustForwardHeader=false"
      - "traefik.http.middlewares.svc1-forwardauth-headers.forwardauth.authResponseHeaders=X-Forwarded-User"

If applicable, please paste the log output in DEBUG level (--log.level=DEBUG switch)
This error results from including the authResponseHeaders middleware
reverse-proxy_1  | time="2020-01-03T05:37:00Z" level=debug msg="Error calling . Cause: Get : unsupported protocol scheme \"\"" middlewareName=svc1-forwardauth-headers@docker middlewareType=ForwardedAuthType

Labels:
# - "traefik.http.routers.svc1.middlewares=svc1-stripprefix, svc1-forwardauth-address, svc1-forwardauth-headers"
# - "traefik.http.middlewares.svc1-forwardauth-address.forwardauth.address=http://validator:3000/verify"
# - "traefik.http.middlewares.svc1-forwardauth-headers.forwardauth.authResponseHeaders=X-Forwarded-User"

And again the same error occurs when including the trustForwardHeader middleware.
reverse-proxy_1  | time="2020-01-03T05:39:45Z" level=debug msg="Error calling . Cause: Get : unsupported protocol scheme \"\"" middlewareName=svc1-forwardauth-trust@docker middlewareType=ForwardedAuthType

With these labels
# - "traefik.http.routers.svc1.middlewares=svc1-stripprefix, svc1-forwardauth-address, svc1-forwardauth-trust"
# - "traefik.http.middlewares.svc1-forwardauth-address.forwardauth.address=http://validator:3000/verify"
# - "traefik.http.middlewares.svc1-forwardauth-trust.forwardauth.trustForwardHeader=false"

I also was hit by (probably) this bug?
When using forwardAuth with nextcloud docker.
After debug looks like requests for HEAD method are mailformed when forwardAuth accepted them

Here a similar problem is described
https://github.com/thomseddon/traefik-forward-auth/issues/156
https://github.com/traefik/traefik/blob/de458b735762ab12a66e92807ddc47345cdb44d0/pkg/middlewares/auth/forward.go#L104-L113

Hello @gregberns and thanks for you interest in Traefik. It seems there's an error in your docker labels. The label "traefik.http.routers.svc1.middlewares=svc1-stripprefix, svc1-forwardauth-address, svc1-forwardauth-trust, svc1-forwardauth-headers" tells traefik to make requests pass through the 4 given middlewares:

svc1-stripprefix
svc1-forwardauth-address
svc1-forwardauth-trust
svc1-forwardauth-headers

When it encounters svc1-forwardauth-address it forward the request to the specified address http://validator:3000/verify. But then, since none of the svc1-forwardauth-trust and svc1-forwardauth-headers middlewares defines an address, it just output the error:

unsupported protocol scheme """

I'm going to close this issue as it's just due to a problem in your configuration. Don't hesitate to ask for help in the community forum.
@jsuchenia, @volker-schukai The problem you are encountering doesn't seem to be related to this one.


MIQBookingAssistance.exe stopped working

miq-nz-booking-assistance-Windows-v0.10.1.exe has stopped refreshing the page. I think it might be because it's waiting for an element with the class .flatpickr-input to exist but it never exists now?
https://github.com/jvolker/miq-nz-booking-tools/blob/5966bb7928e3ce1f273cf978746b6a1595ee915f/MIQ-Booking-Assistance/miq-assistance.js#L113

Have the same problem: stopped working as off 1430hrs NZtime Friday 23July.
Closed and restarted programme: no success
Restarted laptop: no success
Removed app and reloaded: no success.......
Hopefully some-one can help us.

yeap they've changed the way the backend once again making it harder to scrape.. none of the tools are working currently as a result.

Same problem here. Hopefully it's an easy fix!

I got this issue ...... any help  ?   Refused to apply inline style because it violates the following Content Security Policy directive: "default-src 'self'". Either the 'unsafe-inline' keyword, a hash ('sha256-3juv2Ft1FaY3xWYNGXExi9oTqA3RQ4gGhU='), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the 'unsafe-hashes' keyword is present. Note also that 'style-src' was not explicitly set, so 'default-src' is used as a fallback.

same help please.. :(

I also have not been able to get back online line as well checked 9.0 it also does not scan the month request

The MIQ website has been updated and all the flatpickr calendar elements have changed.

You are correct @alistairgraham  in thinking .flatpickr-input never exists because it doesn't anymore. Probably this was an attempt by them to combat bots.
They have done the same thing to the calendar at https://allocation.miq.govt.nz/portal/ so none of the tools will work anymore.
The MIQ date notifications twitter bot is broken too.
I managed to check the page source when a date became available and it seems like they are also now obfuscating 'data-arrival-dates' which means the current method of for checking for dates matches will no longer work either.

miq-nz-booking-assistance-Windows-v0.10.1.exe has stopped refreshing the page. I think it might be because it's waiting for an element with the class .flatpickr-input to exist but it never exists now?
https://github.com/jvolker/miq-nz-booking-tools/blob/5966bb7928e3ce1f273cf978746b6a1595ee915f/MIQ-Booking-Assistance/miq-assistance.js#L113

Looks like the calendar has id="accommodation-calendar" now. Maybe it's possible to check for any dates that do not have the class q14-disabled?

Please only comment here if you have any new information. It really helps anyone working on improving/fixing this tool to not get a flood of messages. Thanks.

Looks like the calendar has id="accommodation-calendar" now. Maybe it's possible to check for any dates that do not have the class q14-disabled?

It looks like unique class tags are being generated for each session

and see my previous comment where it shows 's9r

and see my previous comment where it shows s9r

Not sure if this helps, but it seems it cycles through a limited number of class tags, at least for me, the only variations I'm getting are:

s9r-day
yyh-day
bki-day
g10-day
it7-day
vv8-day
mi4-day

i have a script that is running fine, would you need that mate?

i have a script that is running fine, would you need that mate?

Sharing caring :)

@MannerlyApple94 I've had a look at the CSS and there are 8 combinations. The eighth is q14-day.

i have a script that is running fine, would you need that mate?

@nz029 hopefully its still working. waiting for you to share.

@nz029 Can you create a PR?

Here is the method that parses the data-arrival-dates attribute.
                key: "getAvailableDates",
                value: function() {
                    if (this.calendarElement.getAttribute("data-arrival-dates").length <= 0)
                        return [];
                    for (var e = [], t = [58501527, 28741588, 61219430, 20294527, 57613046, 20913046, 23093500, 40765602], n = this.calendarElement.getAttribute("data-arrival-dates").split("_"), a = 0; a < n.length; a++) {
                        n[a] = n[a].split("").reverse().join(""),
                        n[a] = "" + (Number(n[a]) - t[a % t.length]);
                        var i = n[a].substring(0, 4) + "-" + n[a].substring(4, 6) + "-" + n[a].substring(6, 8);
                        e.includes(i) || e.push(i)
                    }
                    var o = r()(this.getMaxDate(), "YYYY-MM-DD");
                    return e.filter((function(e) {
                        return r()(e, "YYYY-MM-DD") < o
                    }
                    ))
                }

@nz029 Can you create a PR?

i am a civil engineer alex.... know nothing about coding or the coding language. But necessity can teach you anything..... haha
what do you mean by PR? :/ :(
PS: I haven't created that that script, just using it.
I have messaged it to jvolker on twitter

@nz029 Thanks nz029. Not sure which twitter handle you used because jvolker on twitter is a different person to on github. Either way I think I've got a fix that bypasses miq spoofing the css classes.

@nz029 Thanks nz029. Not sure which twitter handle you used because jvolker on twitter is a different person to on github. Either way I think I've got a fix that bypasses miq spoofing the css classes.

I sent it to the correct handle mentioned on his profile.
https://twitter.com/jeremiasvolker

@nz029 Thanks nz029. Not sure which twitter handle you used because jvolker on twitter is a different person to on github. Either way I think I've got a fix that bypasses miq spoofing the css classes.

I sent it to the correct handle mentioned on his profile.
https://twitter.com/jeremiasvolker

Thanks a lot, everyone, for fixing the script! Especially @alexDrinkwater for implementing the fix and creating a new release.
I did receive the script on Twitter but have been off for 1.5 days. Please post anything related to this script here instead. Then everyone can work with it right away.


Add glonlas from Internap

Minor change to add new contributor

Thank you for contributing to openstack/stackalytics!
openstack/stackalytics uses Gerrit for code review.
If you have never contributed to OpenStack before make sure you have read the
getting started documentation:
http://docs.openstack.org/infra/manual/developers.html#getting-started
Otherwise please visit
http://docs.openstack.org/infra/manual/developers.html#development-workflow
and follow the instructions there to upload your change to Gerrit.


add root-level conftest.py to skip doctest only in _indices.py

add root-level conftest.py to skip doctest only in _indices.py
See SO answer here
xref #81

resolved via #83


Add tests and CI

resolves #240

Description
Added CI
Checklist

[x] I have signed the CLA
[x] I have run this code in development and it appears to resolve the stated issue
[x] This PR includes tests, or tests are not required/relevant for this PR
[ ] I have updated the CHANGELOG.md and added information about my change to the "dbt-glue next" section.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

As a general note I recommend this approach to use in your CI:

unit tests - where you mock as much as possible everything that you need, e.g. using moto. unit tests do not need a real account to run, and they can be run easily even locally.
functional tests, they implement dbt-tests-adapter tests, so pretty much a real case scenario test with real models. Those tests at the contrary require a real AWS account with some infra to run on. In dbt-athena we run those conditionally in the CI (for cost reasons), but they should be separated from unit tests. I do not see any functional tests added here, and without those, you miss a big part of it.

As a general note I recommend this approach to use in your CI:
* unit tests - where you mock as much as possible everything that you need, e.g. using moto. unit tests do not need a real account to run, and they can be run easily even locally.

* functional tests, they implement dbt-tests-adapter tests, so pretty much a real case scenario test with real models. Those tests at the contrary require a real AWS account with some infra to run on. In dbt-athena we run those conditionally in the CI (for cost reasons), but they should be separated from unit tests. I do not see any functional tests added here, and without those, you miss a big part of it.

Thanks for the feedback. It was planned but not added yet yesterday.
Today I have separated tests into unit test and functional test, and used AWS account only for the functional test.


binding an ipv6 address on an epoll channel when ipv6 is disabled "succeeds"

Expected behavior
Trying to bind an IPv6 address if IPv6 is disable on the system should fail.
Actual behavior
The program silently binds the wrong port.
Steps to reproduce
Run the code below after sysctl net.ipv6.conf.all.disable_ipv6=0. When nio is used, the program fails with an expected exception:
Exception in thread "main" java.net.SocketException: Protocol family unavailable
	at sun.nio.ch.Net.bind0(Native Method)
	at sun.nio.ch.Net.bind(Net.java:433)
	at sun.nio.ch.Net.bind(Net.java:425)

When epoll is enabled, the program binds IPv4 <IP_ADDRESS>!
Minimal yet complete reproducer code (or URL to code)
import io.netty.bootstrap.ServerBootstrap;
import io.netty.channel.*;
import io.netty.channel.epoll.*;
import io.netty.channel.nio.*;
import io.netty.channel.socket.SocketChannel;
import io.netty.channel.socket.nio.*;
import java.net.InetSocketAddress;

public class Example {
  public static void main(String[] args) throws Exception {
    EventLoopGroup bossGroup;
    EventLoopGroup workerGroup;
    Class clazz;
    if (args.length > 1) {
      bossGroup = new EpollEventLoopGroup(1);
      workerGroup = new EpollEventLoopGroup();
      clazz = EpollServerSocketChannel.class;
    } else {
      bossGroup = new NioEventLoopGroup(1);
      workerGroup = new NioEventLoopGroup();
      clazz = NioServerSocketChannel.class;
    }

    ServerBootstrap b = new ServerBootstrap();
    b.group(bossGroup, workerGroup)
        .channel(clazz)
        .childHandler(
            new ChannelInitializer<SocketChannel>() {
              @Override
              public void initChannel(SocketChannel ch) throws Exception {}
            });

    ChannelFuture f = b.bind(new InetSocketAddress("[::1]", 0)).sync();
    f.channel().closeFuture().sync();
  }
}

Netty version
4.1.51
JVM version (e.g. java -version)
8
OS version (e.g. uname -a)
Linux

This sounds unexpected... I will try to have a look soon. That said if you have time and want to contribute I am happy to review a PR as well

@normanmaurer
I tried to work around this in Bazel by checking NetUtil.isIpV4StackPreferred() as suggested by @benjaminp , but it didn't work for me. It still returned false in my docker container where ipv6 is disabled (net.ipv6.conf.all.disable_ipv6 = 1).
Is there any other way to check ipv6 availability in netty?

io.netty.channel.unix.Socket.isIPv6Preferred() returned true in a docker container where net.ipv6.conf.all.disable_ipv6 = 1, maybe this implies the issue is in the JNI library?

Looks like related issue is https://github.com/netty/netty/issues/7021

@meteorcloudy @benjaminp I can't reproduce this with latest 4.1 release in a vm (I am using parallels) after running sudo sysctl net.ipv6.conf.all.disable_ipv6=1
It fails with:
io.netty.channel.unix.Errors$NativeIoException: bind(..) failed: Cannot assign requested address

Which I think is what you are after. Can you provide a reproducer docker image ?

@normanmaurer
The docker image can be found here: https://github.com/bazelbuild/bazel/issues/11756#issuecomment-657722457
I haven't tried to reproduce with the lastet netty release, the version I was using is 4.1.34

Just confirmed the issue still exists with 4.1.51

@meteorcloudy can you provide a docker image that just contains Netty and the test code that fails without bazel etc?

You can just login to the docker container and run:
#!/bin/bash

set -x

mkdir netty-bug
cd netty-bug

wget https://repo1.maven.org/maven2/io/netty/netty-all/4.1.51.Final/netty-all-4.1.51.Final.jar -O netty-all.jar

cat > Example.java <<EOF
import io.netty.bootstrap.ServerBootstrap;
import io.netty.channel.*;
import io.netty.channel.epoll.*;
import io.netty.channel.nio.*;
import io.netty.channel.socket.SocketChannel;
import io.netty.channel.socket.nio.*;
import java.net.InetSocketAddress;

public class Example {
  public static void main(String[] args) throws Exception {
    EventLoopGroup bossGroup;
    EventLoopGroup workerGroup;
    Class clazz;
    if (args.length < 1) {
      System.out.println("Use epoll");
      bossGroup = new EpollEventLoopGroup(1);
      workerGroup = new EpollEventLoopGroup();
      clazz = EpollServerSocketChannel.class;
    } else {
      System.out.println("Use nio");
      bossGroup = new NioEventLoopGroup(1);
      workerGroup = new NioEventLoopGroup();
      clazz = NioServerSocketChannel.class;
    }

    ServerBootstrap b = new ServerBootstrap();
    b.group(bossGroup, workerGroup)
        .channel(clazz)
        .childHandler(
            new ChannelInitializer<SocketChannel>() {
              @Override
              public void initChannel(SocketChannel ch) throws Exception {}
            });

    ChannelFuture f = b.bind(new InetSocketAddress("[::1]", 0)).sync();
    f.channel().closeFuture().sync();
  }
}
EOF

javac -cp netty-all.jar Example.java

# Use NIO
java -cp netty-all.jar:. Example nio

# Use Epoll
java -cp netty-all.jar:. Example

wget https://gist.githubusercontent.com/meteorcloudy/a3704682ed60965cb360ae926ac705c0/raw/9922772bef8335a6e5061c69f75861b1330e8499/reproduce.sh
chmod +x reproduce.sh
./reproduce.sh

I had no time to dig further into this today... Will try to pick up tomorrow again

@benjaminp @meteorcloudy thanks for the reproducer... This should be fixed by https://github.com/netty/netty/pull/10415


🌟

Adds StarChat2 recipe, along with logic to decontaminate the datasets against HumanEval.

Hello @lewtun
This broke the cpt use-case because this line makes bold assumptions about the columns in a user's dataset.
https://github.com/huggingface/alignment-handbook/blob/595023faa401b8a0ea8338aac712a6f768ee9b34/src/alignment/data.py#L176
Even in DPO/SFT settings users may have different column names than the ones given here:
https://github.com/huggingface/alignment-handbook/blob/595023faa401b8a0ea8338aac712a6f768ee9b34/src/alignment/data.py#L26
Is there a better way to solve this by giving more control to the users? For cpt I'm working on a fix so that text_column from the dataconfig gets passed and is not removed but on top of that I feel like this is being very restrictive on a user's data layout.


update antd to 4.23.2

What does this PR do and why?
need to update the package for menuitemtypes
Provide a description of what this PR does. Link to any relevant GitHub issues, Notion tasks or Discord discussions.
Screenshots or screen recordings
If applicable, provide screenshots or screen recordings to demonstrate the changes.
Acceptance checklist

[ ] I have evaluated the Approval Guidelines for this PR.
[ ] I have tested this PR in all supported browsers.
[ ] I have tested this PR in dark mode and light mode (if applicable).

Current dependencies on/for this PR:

main

PR #2047

PR #2048   👈

This comment was auto-generated by Graphite.


Defensive/more explicit handling of MCMC with unfixed params that don't have a prior

At the moment, all parameters that are not fixed are included in the HMC, including those that do not have priors set explicitly. I think it'd be good if GPflow had a check for this and raise an error (or at least a warning) when you do MCMC with params where fixed=False but prior=None: most of the time you would want to set a prior, and in those cases where you do want an "uninformative" prior it'd be better to have an extra prior class to encode that. This would take away the risk of overlooking one param that hadn't gotten a prior yet and getting weird behaviour in the sampling.

Could point. I agree.

This has caught me out in the past. Good idea

Would this be as simple as inserting in training.hmc.HMC a loop over all trainable parameters and checking that param.prior is not None? and raising a warning (or exception) if there are any?
Should we have something like priors.Empty() (or "uninformative" or whatever you want to call it) that has the same effect as None, except it then wouldn't generate the warning/error?
(Is this even possible - as build_prior() returns constant 0.0 if prior is None, whereas otherwise you get the sum of prior.logp() and transform.log_jacobian(), so even if priors.Empty.logp() returned 0.0 there would still be the log_jacobian of the transform?)


fix: set working AWS_URI example

Ticket: MC-6809
External Contributor Checklist

🚨 Please review the guidelines for contributing to this repository.

[x] Make sure that all commits follow the conventional commit specification for the Mender project.

The majority of our contributions are fixes, which means your commit should have
the form below:
fix: set working AWS_URI example

Changelog: None
Ticket: MC-6809

[x] Make sure that all commits are signed with git --signoff. Also note that the signoff author must match the author of the commit.

Description
The AWS_URI specified in the doc doesn't work with S3. I tested the right URL and updated the example.

@mender-test-bot cherry pick to:

3.4.x
3.3.x

@mender-test-bot cherry-pick to:

3.4.x
3.3.x


Enhance rate limit handling, add email config param

Changes

Add rate limit count as a config parameter: RATE_LIMIT_COUNT
Add rate limit window length as a config parameter: RATE_LIMIT_WINDOW
Add email as a config parameter: EMAIL
Add limit route & page view
Add contact partial
Update 404 & 500 views to use the contact partial
Update SK translations

Details
Rate limit enhancements
The original express-rate-limit code returns default generic message on exceeding the configured rate limit: Too many requests, please try again later. (English only). What's worse, administrators don't have any clue this is happening.
Users often share their IPv4 IP address as operators are using IPv6 and provide a shared IPv4 IP for hundreds of users. I've already experienced this on the SK deployment when users were affected unable to submit their reports until one user notified me having no clue what's going on.
This PR tries to address this situation and brings new /limit route, that can provide more localized info for users and also give us (admins) information, the rate limit has been reached (seeing /limit route in the analytics).
Email as a config param
Twitter handler was the only configurable contact available on the site. There are countries where twitter is not very popular or used, or some people don't have twitter account unable to contact us.

Since this a page that is not part of the ordinary flow, I guess it is ok to merge it without getting translations for all languages first. In the rare case where people hit the rate limit, it should be ok that it is in english.

Could you fix the conflicts, and then we'll merge!

Is this one ready to be merged?

Is this one ready to be merged?

Going to rebase and will be ready soon :-)


Disable mobile zoom

How to disable mobile zoom when the user drags two fingers on the screen? However, it would be interesting to zoom in if you press the "+" button. Thank you.

Fork one and change the source code for your own case if necessary.


CS:GO Music kit ST doesnt works.

header /\

The README tells you so

Note: Some my not work due to them being only counted on official servers, one example is the MVP counter on music kits.


Remove ... more from Pins category

We are moving away from ... more paradigm to single category with less important blocks at the bottom as students scan from top to bottom

Using groups will impact the Microbit as well? Is that ok?

Ah lets not do it then. Closing.


Diagnose and fix errors in ockam status command

This command has three known issues that must be addressed.
1. Fails when there are no nodes registered.
How to reproduce
ockam reset -y
ockam show

Fix proposal
This section of the code is incorrect because list() will return an empty list instead of an error where there are no nodes in the system. That part should be rewritten as follows:
let node_states = opts.state.nodes.list()?;
if node_states.is_empty() {
    return Err(anyhow!("No nodes registered on this system!").into());
}

2. No output when there are no identities enrolled.
How to reproduce
Note: the previous error must be solved to reproduce this one.
ockam reset -y
ockam show

Fix proposal
Currently, when running ockam status on a fresh install the command exits successfully without showing any output. The command should return an error when there are no enrolled identities. Before calling the print_status, there should be a check like this:
if status_identities.is_empty() {
    return Err(anyhow!("No enrolled identities found! Try passing the `--all` argument to see all identities.").into());
}

3. It fails when there is more than 1 node registered.
How to reproduce
ockam reset -y
ockam node create
ockam node create
ockam show

Fix proposal
For every registered node, this command runs an Rpc request. Currently, it tries to create a new TcpTransport on each request, resulting in the following error:
» ockam status
Version 0.77.0, hash: 99c3431ec67affcdf80d393f75e40bd69575c33b
failed because router state: a router for this type already exists

Caused by:
    failed because router state: a router for this type already exists

To fix this, the get_node_status must be refactored so it accepts a TcpTransport reference as a parameter. The TcpTransport must be created before the node_states loop.

We love helping new contributors!
If you have questions or need help as you work on your first Ockam contribution, please leave a comment on this discussion.
If you're looking for other issues to contribute to, checkout this discussion and labels - https://github.com/build-trust/ockam/labels/good first issue or https://github.com/build-trust/ockam/labels/help wanted

Can I take it?

Sure! Ping me if you have any questions 👍


Add image to PostgresCluster.yaml that pulls from bcgov artifactory

I see in the following chat you are recommending getting images from the bcgov artifactory
https://chat.developer.gov.bc.ca/channel/crunchydb?msg=xeo4BowwnLySQmXRo
Could you update the README.md to that affect and add in a sample image into PostgresCluster.yaml?

This has been covered by PR #23


Use of Azure IPAM in non-default Azure clouds

General Information

Cilium version 1.9.6
AKS with Kubernetes 1.19.9

I attempted to deploy Cilium with Azure IPAM onto an AKS cluster in the AzureChinaCloud which differs from the public Azure cloud in some details.
Ref: https://docs.microsoft.com/en-us/azure/active-directory/develop/authentication-national-cloud
Ref: https://docs.microsoft.com/en-us/azure/china/resources-developer-guide
When using Azure CNI and Cilium in chaining mode, these differences do not matter, but with Cilium Azure IPAM, they do.
When preparing, I found that the Cilium Helm chart does not allow passing azure.cloudName yet, even though this is a valid flag for the operator already.
In the operator itself, the cloudName is used to configure the Azure client authorizer to acquire tokens from the correct AAD.
However, when creating the resource clients themselves, NewSomethingClient(subscriptionId) is called which defaults to the public Azure endpoints. Using NewSomethingClientWithBaseURI(baseURI, subscriptionId) should also allow calls to other Azure clouds. The respective endpoints can be loaded from here.
If you want, I could take a look into generalizing the code.

@joshmue -- I've put a draft PR to add support for custom clouds but I do not have any way to test it at the moment. Can you give it a spin?

Sure! I'll provide feedback ASAP.


Support content version.message / page history comment field

Scenario: To keep my generated confluence docs in sync with project releases, I'd like to have my confluence page history somewhat related to git describe --tags (or something else for other projects). To do so I'd need either to modify updated_page['version']['number'] or add version comment. Apparently confluence supports version comment:

To fill in the comment column at the moment it's required to either use available UI while editing or make an API call (see here)
It looks like this can be achieved by adding another parameter and extending the version object. I'll submit PR this week.

Thanks @mkostyla !
@jdknight would you spare some time to take a look? We'd love to use this feature at our company.

Changes have been added in #633 (thanks to @mkostyla) to support users the ability to hint on the version field through a configuration entry. This change has been added into the main branch and should be made available next stable release (v1.8). Users needing to use this feature before a release is made, the development version of this extension can be installed.

v1.8 is now available on PyPI -- marking as closed.


feat(advanced_console): Add ESP32-P4 ESP32-C5 model support in 'version' command output (IDFGH-13722)

Description
This PR enhances the version advanced console command output in the iPerf example to correctly display the model names for the ESP32-P4 and ESP32-C5 microcontrollers. The iPerf example now prints the ESP-IDF version number, chip information, and model name when the "version" command is executed.
Previous Behavior
Before this change, the models ESP32-P4 and ESP32-C5 were displayed as "Unknown".
As an example, the execution before modification serves

IDF Version:v5.4-dev-2744-g59e1838270-dirty
Chip info:
        model:Unknown
        cores:1
        feature:/802.11bgn/BLE/External-Flash:8 MB
        revision number:0

The model is unknown.
New Behavior
After the modification, the model names are correctly displayed.
Here’s an example of the output when using the ESP32-C5:
IDF Version:v5.4-dev-2744-g59e1838270-dirty
Chip info:
        model:ESP32-C5
        cores:1
        feature:/802.11bgn/BLE/External-Flash:8 MB
        revision number:0

The model ESP32C5 is now known and is now correctly printed with the model name ESP32-C5.
The code before

/* 'version' command */
static int get_version(int argc, char **argv)
{
    const char *model;
    esp_chip_info_t info;
    uint32_t flash_size;
    esp_chip_info(&info);

    switch(info.model) {
        case CHIP_ESP32:
            model = "ESP32";
            break;
        case CHIP_ESP32S2:
            model = "ESP32-S2";
            break;
        case CHIP_ESP32S3:
            model = "ESP32-S3";
            break;
        case CHIP_ESP32C3:
            model = "ESP32-C3";
            break;
        case CHIP_ESP32H2:
            model = "ESP32-H2";
            break;
        case CHIP_ESP32C2:
            model = "ESP32-C2";
            break;
        default:
            model = "Unknown";
            break;
    }

and  the code after the change / add

/* 'version' command */
static int get_version(int argc, char **argv)
{
    const char *model;
    esp_chip_info_t info;
    uint32_t flash_size;
    esp_chip_info(&info);

    switch(info.model) {
        case CHIP_ESP32:
            model = "ESP32";
            break;
        case CHIP_ESP32S2:
            model = "ESP32-S2";
            break;
        case CHIP_ESP32S3:
            model = "ESP32-S3";
            break;
        case CHIP_ESP32C3:
            model = "ESP32-C3";
            break;
        case CHIP_ESP32H2:
            model = "ESP32-H2";
            break;
        case CHIP_ESP32C2:
            model = "ESP32-C2";
            break;
        case CHIP_ESP32P4:
            model = "ESP32-P4";
            break;
        case CHIP_ESP32C5:
            model = "ESP32-C5";
            break;
        default:
            model = "Unknown";
            break;
    }

Code Changes
The following cases were added to the get_version function:

        case CHIP_ESP32P4:
            model = "ESP32-P4";
            break;
        case CHIP_ESP32C5:
            model = "ESP32-C5";
            break;

The ESP32-P4 and ESP32-C5 models have been added.
Example ESP32-C5
iperf> version
IDF Version:v5.4-dev-2744-g59e1838270-dirty
Chip info:
        model:ESP32-C5
        cores:1
        feature:/802.11bgn/BLE/External-Flash:8 MB
        revision number:0
iperf>

 Attached Picture as Link

Related

Testing
Tested with ESP32-C5-DevKitC-1 and iPerf example and modification
successful printed out the right found model name
iperf> version
IDF Version:v5.4-dev-2744-g59e1838270-dirty
Chip info:
        model:ESP32-C5
        cores:1
        feature:/802.11bgn/BLE/External-Flash:8 MB
        revision number:0
iperf>

https://github.com/espressif/esp-idf/issues/14021#issuecomment-2350926729
https://github.com/espressif/esp-idf/issues/12996

Checklist
Before submitting a Pull Request, please ensure the following:

[x ] 🚨 This PR does not introduce breaking changes.
[ ] All CI checks (GH Actions) pass.
[ ] Documentation is updated as needed.
[ ] Tests are updated or added as necessary.
[x ] Code is well-commented, especially in complex areas.
[x ] Git history is clean — commits are squashed to the minimum necessary.

Thanks for the contribution @ESP32DE! LGTM!

sha=27b5f6298c34431549c7e04690ce2cefa2fb7f52

Thanks for contribution, changes have been merged with https://github.com/espressif/esp-idf/commit/4281f58229067be58206fdf6122c049948a918cc.


[BUG] SmartScaler can't scale down cluster

What is the bug?
When trying to scale down nodes in a cluster, smartscaler produces error messages that look like this:
operator-controller-manager {"level":"error","ts":"2024-04-09T15:06:37.623Z","msg":"failed to exclude node clone-opensearch-nodes-5","controller":"opensearchcluster","controllerGroup":"opensearch.opster.io","controllerKind":"OpenSearchCluster","OpenSearchCluster":{"name":"clone-opensearch","namespace":"clone-opensearch"},"namespace":"clone-opensearch","name":"clone-opensearch","reconcileID":"3299605f-04ca-4b28-9943-81ee248c45e5","error":"invalid character 'U' looking for beginning of value","stacktrace":"opensearch.opster.io/pkg/reconcilers.(*ScalerReconciler).excludeNode\n\t/workspace/pkg/reconcilers/scaler.go:228\nopensearch.opster.io/pkg/reconcilers.(*ScalerReconciler).reconcileNodePool\n\t/workspace/pkg/reconcilers/scaler.go:127\nopensearch.opster.io/pkg/reconcilers.(*ScalerReconciler).Reconcile\n\t/workspace/pkg/reconcilers/scaler.go:55\nopensearch.opster.io/controllers.(*OpenSearchClusterReconciler).reconcilePhaseRunning\n\t/workspace/controllers/opensearchController.go:321\nopensearch.opster.io/controllers.(*OpenSearchClusterReconciler).Reconcile\n\t/workspace/controllers/opensearchController.go:142\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.15.0/pkg/internal/controller/controller.go:118\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.15.0/pkg/internal/controller/controller.go:314\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.15.0/pkg/internal/controller/controller.go:265\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.15.0/pkg/internal/controller/controller.go:226"}
How can one reproduce the bug?
Spin up a new OpenSearch cluster with operator version 2.4.0 (2.6.0 has the same issue) and cluster version 1.3.6
What is the expected behavior?
Being able to scale the cluster up and down without issues
What is your host/environment?
Kubernetes version 1.26.x
Do you have any screenshots?
No
Do you have any additional context?
I've tried this both with more elaborate setups as well as very simple setups, but the error remains the same.
Would love any pointers!

User error, if anyone encounters this:
We had a newline character in our cluster-admin-credentials secret.


App logos

ETHSimple
Apps section
https://ethsimple.com/

Under Apps
Multis
https://multis.co/

Change the link for the POAP app to:
https://www.poap.xyz/


latest build doesn't show json

Version
What version of the Emulator are you using.

Describe the bug
I updated to latest preview and it stopped display json.  I rebooted, still not display json.  I installed 4.11.0 and it started working again.
To Reproduce
Install 4.11 212215
Expected behavior
To be able to see json
[bug]

I can repro this in dev. Looking into a fix.

There was a breaking change in Electron that flew under the radar when I bumped up the version. <webview> tags are now disabled by default, and need to be explicitly enabled in the code. All the inspectors are hosted within these <webview> tags.
I have a PR up that re-enables them: #2233


Adding Retry for statusCode 0

Adding default retry for status Code 0
As investigated on a project with millions of users around the world, we found that status code 0 is not a permanent failure, and we should retry on them...
status code 0 represents a list of retriable things like: -

DNS: sometimes requests failed because of DNS, and we need a retry on them; and that is not permanent.
TCP: we found a huge request failed on tcp connection with the server and retrying them helps.
TLS: this is tls handshake connection with the server

due to JavaScript limitations, they actually hide the actual reason for status code 0 and we can't capture the exception from the onerror method to differentiate different types of error code 0; some of them are actually will be no internet and some others will be normal retriable errors like specified above (DNS, TCP and TLS handshake)
we can override the errorDefaultHandler, but this is counterintuitive for the default error handler, and we actually didn't notice there was no retry or this is permanent for a very long time.

We were always torn about what the right thing to do with statuscode 0 is.  As you say, often times it's retryable.  But there's also a pile of times when it's really not (or, at least, it's unlikely to work any time soon) -- CORS issues, actual network failure, etc.    But it probably does make sense that the stupid simple/dumb default error handler takes the conservative approach and auto-retries statuscode 0s, since at least some nontrivial portion of those are retryable.  We always ended up using a different error handler for the overwhelming majority of our SimpleRestClients, which ended up dealing with 0s pretty specially.
My main concern is if this turns into a breaking change for folks and I'm torn on if this is just a minor version bump or actually a major one, technically...
I don't actually have admin on this repo anymore, since I have long since moved on from MSFT.  @berickson1 you have thoughts here? (and/or admin access? :D )

I am still a maintainer here. I have a few discussion points

The original reason for not retrying on status code 0 is that you don't know if a request succeeded or not. It's entirely possible that the service fully processed the request and sent a response, but the connection was interrupted before the client received it. This likely isn't problematic on GET requests, but could be problematic on POST, PUT or PATCH requests.
Consider a POST request that is initiating a payment/purchase flow. If that request was processed by the service twice (or retried at a later time due to backoff), it could cause substantial negative impact to the user. Similarly for time-sensitive requests.  I'm really torn on saying that any request that failed with no info should be retried indefinitely. I'd lean towards this being opt-in configurable behaviour rather that default behaviour
Error handling changes probably constitute a breaking change like @deregtd mentioned above.  A major version bump would need to accompany this, unless we made this opt-in config based

thanks @berickson1 for clarifying your points of view; here is my what I think: -
1- if this is made because of POST/PATCH type requests; the default retry count is 0 which will not make retries... then the coder knows exactly if he will add a retry to the POST/PATCH request he must make sure the flow will not create duplicates or inconsistencies in date and handle that on his side that what I would do if I added a retry to a POST request
2- In the defaultErrorHandler(), we don't retry on (0, 4xx, 5xx) which make me wonder. What are the status codes we will retry on? because the rest are not errors.
Thanks

Been thinking about this on and off for the last week.  Unfortunately, I think I'm with Brent on this one.  I'm okay with the default handler being very pessimistic, because being optimistic can be dangerously wrong sometimes, and I'd prefer if devs had to explicitly understand that and handle it.  Out of the box, virtually nothing will retry automatically, because retrying can end up storming endpoints, which can be pretty bad for folks.  So I'm going to close this PR, and really just push people to make custom error handlers if they have behavior they want to specifically retry around.  The handlers are super easy to extend, by design, so I'm hoping that doesn't scare folks away.


Ensure openEQUELLA is handling files appropriately

It would be good to come up with a way to ensure openEQUELLA is handling files appropriately.

Verbose logging whenever attachments are touched - this would provide the necessary audit trail to 'prove' openEQUELLA handled attachments properly.
A rubbish-bin area that instead of a file being deleted, it is moved there and logged, and a system admin has to manually go in and empty it - in theory, this would ensure you could always recover a file from openEQUELLA.
Detail / enhance known ways to monitor openEQUELLA file handling

CDM group thoughts:

Consider the 'Trash' folder, maybe making it more persistent.
For the rubbish-bin thought, you'd want an audit-trail to know where the files came from
Might want a scheduled task (configurable) to clear out older rubbish-bin content
It'd be a lot of effort to create a more transactional methodology, but that would eliminate some of the race conditions that can cause these concerns.
Consider a background task to check if there are any missing attachments (ie convert ping-{open}equella).


uv sync does not install a workspace member's dependency with extra

Context
Consider the following project structure where:

The root project is the workspace root with two members: a-lib and an-app
The root project has a-lib as a dependency
The a-lib library has an optional dependency network = ["httpx>=0.27.2"]
The an-app application has a dependency "a-lib[network]"

.
├── README.md
├── a-lib
│   ├── README.md
│   ├── pyproject.toml
│   └── src
│       └── a_lib
│           └── __init__.py
├── an-app
│   ├── app.py
│   └── pyproject.toml
├── hello.py
├── pyproject.toml
└── uv.lock

Expected behavior

uv sync should install httpx as:

httpx is in the network extra of a-lib
a-lib[network] is a dependency of an-app, which is a workspace member

Actual behavior

Running uv sync in the repository root does not install httpx.

Output of uv sync -v:
DEBUG uv 0.4.0
DEBUG Found project root: `/Users/nomura/tmp/uv-opt-dep`
DEBUG Found workspace root: `/Users/nomura/tmp/uv-opt-dep`
DEBUG Adding current workspace member: `/Users/nomura/tmp/uv-opt-dep`
DEBUG Adding discovered workspace member: `/Users/nomura/tmp/uv-opt-dep/a-lib`
DEBUG Adding discovered workspace member: `/Users/nomura/tmp/uv-opt-dep/an-app`
DEBUG Searching for Python >=3.12 in managed installations or system path
DEBUG Searching for managed installations at `/Users/nomura/Library/Application Support/uv/python`
DEBUG Found managed installation `cpython-3.12.5-macos-aarch64-none`
DEBUG Found `cpython-3.12.5-macos-aarch64-none` at `/Users/nomura/Library/Application Support/uv/python/cpython-3.12.5-macos-aarch64-none/bin/python3` (managed installations)
Using Python 3.12.5
Creating virtualenv at: .venv
DEBUG Using request timeout of 30s
DEBUG Acquired lock for `/Users/nomura/Library/Caches/uv/built-wheels-v3/editable/927367c801095033`
DEBUG Found static `pyproject.toml` for: a-lib @ file:///Users/nomura/tmp/uv-opt-dep/a-lib
DEBUG Found workspace root: `/Users/nomura/tmp/uv-opt-dep`
DEBUG Adding root workspace member: `/Users/nomura/tmp/uv-opt-dep`
DEBUG Adding current workspace member: `/Users/nomura/tmp/uv-opt-dep/a-lib`
DEBUG Adding discovered workspace member: `/Users/nomura/tmp/uv-opt-dep/an-app`
DEBUG Acquired lock for `/Users/nomura/Library/Caches/uv/built-wheels-v3/path/380ad038dfb54863`
DEBUG Found static `pyproject.toml` for: an-app @ file:///Users/nomura/tmp/uv-opt-dep/an-app
DEBUG Found workspace root: `/Users/nomura/tmp/uv-opt-dep`
DEBUG Adding root workspace member: `/Users/nomura/tmp/uv-opt-dep`
DEBUG Adding current workspace member: `/Users/nomura/tmp/uv-opt-dep/an-app`
DEBUG Adding discovered workspace member: `/Users/nomura/tmp/uv-opt-dep/a-lib`
DEBUG Acquired lock for `/Users/nomura/Library/Caches/uv/built-wheels-v3/path/f80ace0e74a88082`
DEBUG Found static `pyproject.toml` for: uv-opt-dep @ file:///Users/nomura/tmp/uv-opt-dep
DEBUG Found workspace root: `/Users/nomura/tmp/uv-opt-dep/`
DEBUG Adding current workspace member: `/Users/nomura/tmp/uv-opt-dep/`
DEBUG Adding discovered workspace member: `/Users/nomura/tmp/uv-opt-dep/a-lib`
DEBUG Adding discovered workspace member: `/Users/nomura/tmp/uv-opt-dep/an-app`
DEBUG Acquired lock for `/Users/nomura/Library/Caches/uv/built-wheels-v3/editable/927367c801095033`
DEBUG Found static `pyproject.toml` for: a-lib @ file:///Users/nomura/tmp/uv-opt-dep/a-lib
DEBUG Found workspace root: `/Users/nomura/tmp/uv-opt-dep`
DEBUG Adding root workspace member: `/Users/nomura/tmp/uv-opt-dep`
DEBUG Adding current workspace member: `/Users/nomura/tmp/uv-opt-dep/a-lib`
DEBUG Adding discovered workspace member: `/Users/nomura/tmp/uv-opt-dep/an-app`
DEBUG Existing `uv.lock` satisfies workspace requirements
Resolved 10 packages in 1ms
DEBUG Using request timeout of 30s
DEBUG Directory source requirement already cached: a-lib==0.1.0 (from file:///Users/nomura/tmp/uv-opt-dep/a-lib)
Installed 1 package in 0.78ms
 + a-lib==0.1.0 (from file:///Users/nomura/tmp/uv-opt-dep/a-lib)

If you remove the project.optional-dependencies section from a-lib/pyproject.toml and run uv add httpx --optional network, it will install httpx as expected. However, running uv sync will remove httpx again.

For reproduction
For reproduction, please follow the instruction on this repository: https://github.com/shunichironomura/uv-opt-dep
Environment

uv platform: macOS
uv version: uv 0.4.0 (d9bd3bc7a 2024-08-28)

Thanks for the thorough writeup and repro, I will read it closely and take a look today.

Thank you for the comment, it worked. However, although adding the extra in the root pyproject.toml is a valid workaround, my intention was to reflect the actual requirements that the extra is only required by the an-app, and not required by the root project (i.e., the hello.py script in the above example).
Or maybe specifying different extras for one dependency across workspace members is invalid in the first place?

If you use uv run or uv run --package, uv will automatically sync prior to running the command (if you're out-of-sync). Alternatively, if you uv run or uv sync from within the member directory (like, in ./an-app), it will automatically sync that member.

Understood. Thank you!

Hmm -- this behaviour was pretty unexpected. I've got a workspace set up with a number of members that are plugins (comfyui custom node directories) to comfyui. I've got a pyproject.toml set up for each of them, but comfyui doesn't actually directly depend on them; they're discovered dynamically.
I'd really like uv sync in the workspace root to install all dependencies (basically, everything in the lock file) up front. Is there any reason to not do this? Otherwise I'd need to manually uv sync every single plugin. Worst case a flag like uv sync --all, but I'd think that should be the default in the workspace root and there should be a flag to limit to just the workspace root. (Rough-and-very-imperfect analogy to cargo -- a cargo build in the workspace root builds all projects; it's explicitly a workspace after all.)

@vvuk -- You might be interested in https://github.com/astral-sh/uv/issues/5727 -- probably better to discuss there than in this closed issue.


Validate user input for username field when sign up

As a developer, I want to prevent the user from entering invalid characters in the username field, such as uppercase letters, space and special symbols other than - and _ . This would ensure the consistency and security of the user data.
Acceptance criteria:

The username field should only accept lowercase letters, numbers, hyphens, dot and underscores
The username field should display an error message if the user enters any invalid character
The username field should not allow the user to submit the form until the error is resolved

@tehseen01 can i work on this issue?

Sure, feel free to work on this issue. Please make sure to follow the contribution guidelines and check for any updates before submitting your pull request

@tehseen01 i have some problems when running this repo, it stucks at 404 page.

Sure, feel free to work on this issue. Please make sure to follow the contribution guidelines and check for any updates before submitting your pull request

yes just saw you update README. thanks

if you have not setup backend then you will see 404 error

if you don't want to setup backend then simply you can just paste this url in the .env file
NEXT_PUBLIC_API_URL= https://social-api-three.vercel.app/api/

@tehseen01 i pushed into my fork but when i click compare & pull request. this shows up.


Configure GoogleService-Info.plist with multiple schemes

How to configure GoogleService-Info.plist if consists of multiple schemes?

Please consider asking support questions in one of the other channels listed at http://flutter.io/support . (#15567, #19252)
There is currently only limited support.


[BUG - Release] Palworld Crash

Branch or Release
v0.3.2
Game and Engine Version
Palworld
Describe the bug
A process has crashed: UE-Pal
Mods directory
A zip of your Mods folder if you've installed any mods that don't come with UE4SS by default
To Reproduce
Steps to reproduce the behavior:
Play the game
Expected behavior
Not to crash
Screenshots, UE4SS Log, and .dmp file
LoginId:afd01b8b474e00a2f6e5c8bf8396440a
EpicAccountId:b34597742b8c434d98d94e44a2380bcc
Abort signal received
ucrtbase
ucrtbase
ucrtbase
VCRUNTIME140_1
VCRUNTIME140_1
VCRUNTIME140_1
VCRUNTIME140_1
ntdll
ntdll
ntdll
KERNELBASE
VCRUNTIME140
UE4SS
UE4SS
UE4SS
UE4SS
VCRUNTIME140_1
VCRUNTIME140_1
ntdll
UE4SS
UE4SS
UE4SS
ucrtbase
kernel32
ntdll

Desktop

OS: WIN10

Additional context
.

So you aren't using any mods and there is no crash dump?

same problem here with https://steamcommunity.com/app/526870/discussions/1/3815166994148341924/  this is not ue4ss bug i belive

There isn't much evidence to suggest the two crashes are related aside from similar crash stack trace log. What we really need is OP to actually send their mods.zip, crash dump (if any) and their ue4ss log file. Otherwise there just isn't enough info to say conclude anything...


Add integration tests for ringpop-labels

This PR adds tests for the labels feature in ringpop to the integration test suit. Currently the feature is only implemented in ringpop-go and the test is a non mandatory test for now and enabled via the --enable-feature labels command line option.

Looks really good! Three non-blocking nits (and the console.log you already found)

LGTM!

Looks pretty awesome. Just one question: are we testing upgrade/rollback behaviours in here?

The integration tests don't really test the upgrade/rollback behavior of ringpop. It is a great idea but I am not sure that it can be easily tested. Most often what actually happens goes into your gut feeling so I think it is best to keep testing those paths with a test cluster.
When I ran an upgrade without using labels it worked as always. No faulties, no fullsyncs. When having labels set during an upgrade or rollback there is slightly more gossip due to continues reincarnation of nodes with labels. The old version will treat the member as if it has no labels and gossips that around, this will reach the member in question which disagrees and reincarnates.
If you have ideas on how to test these scenarios it would be great to have a chat about it.

Sweet, LGTM


Deprecate warp

Proposed Changes

Mark warp option as deprecated to remove it in future relaese

Related Issues
#191

Happy about suggestions regarding the documentation and a potential link to include to a tutorial on how to migrate to a managed tunnel @AlecRust


How can i check a values exists in an array ?

I have a simple question. I have a property groupBy which is an array and contain only two possible values "product" and "date". Now i want to make another property required based upon a value exists in the groupBy array. In this case when my groupBy array contains "date" i want to make resolution required! How can i do that ?
Who can i check if an array contains a value ?
var data = {
    "pcsStreamId": 123123,
    "start": moment().valueOf(),
    "end": moment().valueOf(),
    "groupBy" : ["product"]
};

var schema = {
        "type": "object",
        "properties": {
            "pcsStreamId": { "type": "number" },
            "start": { "type": "integer", "minimum" : 0 },
            "end": { "type": "integer", "minimum" : 0 },
            "groupBy": {
                "type": "array",
                "uniqueItems": true,
                "items" : {
                    "type": "string",
                    "enum": ["product", "date"]
                },
               "oneOf": [
                   {
                       "contains": { "enum": ["date"] },
                       "required": ["resolution"]
                   }
                ]
            },
            "resolution" : {
                "type": "string",
                "enum": ["day", "year", "month", "shift"]
            },
        },
        "required": ["pcsStreamId", "start", "end", "groupBy"]

};

To express conditions you can use anyOf/oneOf or if/then/else keywords (the latter is defined in ajv-keywords package and is planned to be included in draft-07 of JSON-Schema)

Yeah but i dont't know the correct syntax for that. Can you give me some help pls ?


(FLK-E101) Indentation contains mixed spaces and tabs

Description
Indentation has has both tabs and spaces in it. You should use either tabs or spaces, but not both.
Occurrences
There are 8 occurrences of this issue in the repository.
See all occurrences on DeepSource → deepsource.io/gh/XenonTheInertG/Rec-Boot-Bot/issue/FLK-E101/occurrences/

@XenonTheInertG Fy,i fixed that


Fix on os x, reduce  blinking.

That's a good catch that rm asks for confirmation on osx. What is the benefit of deleting and then touching the temp file rather than the oneliner?
I guess whether to show the prompt in one go or as it's elements load is personal preference. I'd like to wait on the discussion at https://github.com/bhilburn/powerlevel9k/pull/262

The one liner does not work on OS X, it complains that the file already exists.

do you have setopt noclobber set somewhere? >! could be used to force clobber.
Yes definitely.

No, don't think so. I think this approach is better, as rm and touch works everywhere.

Alright, if POWERLEVEL9K_RPROMPT_RENDER_ASAP is true, it renders on each part, otherwise when they are all finished.

I might have noclobber set somewhere, but I did not do so myself. This leads me to believe that noclobber is the default in OS X, so I think we should rather go with the approach that works by default (instead of asking users to change the defaults).

alright, it now uses the force clobber.

Alright nice. The POWERLEVEL9K_RPROMPT_RENDER_ASAP is a good idea.  I'll merge your changes and that should change my pull request to bhilburn.

Thanks! Also, great idea btw! I had disabled most segments on my setup due to the slowness, but this makes it all much nicer.

Ha I usually just use the status and vcs element. I enabled all of them and even added a sleep in the loop to check they were loading asynchronously.


foreach() argument must be of type array|object, null given

ErrorException
foreach() argument must be of type array|object, null given
:dart: Illuminate\Foundation\Bootstrap\HandleExceptions::handleError
:page_facing_up: /app/resources/views/individuals/partials/about.blade.php
10      @foreach($individual->working_languages as $language)
11          <li>{{ get_language_exonym($language) }}</li>
12*     @endforeach
13  </ul>
14

Open in Flare

Default to user's indicated primary written/spoken language and sign language.


fix(backend): add feature flag for underline-color

Windows 7 doesn't support the underline color attribute, so we need to
make it optional. This commit adds a feature flag for the underline
color attribute - it is enabled by default, but can be disabled by
passing --no-default-features to cargo.
We could specically check for Windows 7 and disable the feature flag
automatically, but I think it's better for this check to be done by the
crossterm crate, since it's the one that actually knows about the
underlying terminal.
To disable the feature flag in an application that supports Windows 7,
add the following to your Cargo.toml:
ratatui = { version = "0.24.0", default-features = false, features = ["crossterm"] }

Fixes https://github.com/ratatui-org/ratatui/issues/555

Ping @rigelminer


Editor hovers flicker/re-render when trying to click into them

I believe this is relatively new (since its not uncommon for me to copy text out of the hovers) -- but when trying to click into a hover to select text is often flickers/re-renders losing the selection and sometimes just disappears. FYI, it seems like it disappears more often if your mouse end up outside the editor area.

/cc @alexdima

@eamodio You might have been running into https://github.com/microsoft/vscode/issues/154577 . That one was caused by a change in the markdown renderer which would emit an event 50ms too late, which would cause the hover to be layouted later by 2-3 frames (i.e. flicker). We pushed a fix for that yesterday via https://github.com/microsoft/vscode/pull/155629, so today's build (expected in ~1hr) would contain the fix. Could you please try out the fix?

Will check it out and report back -- thanks!

Looks like its fixed now, so will close this out. Thanks!


Add customizations property

I left the blank settings property as I thought these might have a slightly different use case than the vscode-dev-containers definitions and it'd be helpful to include it as a reference, but happy to discuss further.

I left the blank settings property as I thought these might have a slightly different use case than the vscode-dev-containers definitions and it'd be helpful to include it as a reference, but happy to discuss further.

For the samples I think it is fine. 👍

Thanks for the feedback and for all the approvals!


backdrop is not removed on alert removal

Backdrop is not removed when the alert is removed.
An issue was already reported here https://github.com/artemsky/ng-snotify/issues/41 and closed I don't know why.
This is happening on even your example site (https://artemsky.github.io/ng-snotify/).
Just keep backdrop set to 1 and click 'Success' to show success alert. After the timer, the alert goes away but the backdrop stays.
Need help with this, otherwise great library mate.

Check now pls.

I have the same problem.. any solution?


CAMEL-10038 don't throw exception if BlueprintPropertiesParser#parseP…

…roperty would return null (breaks fallbackToUnaugmentedProperty behavior, and an exception will be thrown anyway by the parent DefaultPropertiesParser if the value is still null after fallback)

Thanks for the PR it has been merged. Do you mind closing this?

Closed. Thanks for your assistance.
On Jul 21, 2016 7:36 AM, "Claus Ibsen"<EMAIL_ADDRESS>wrote:

Thanks for the PR it has been merged. Do you mind closing this?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/apache/camel/pull/1075#issuecomment-234228893, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA6cH5W2zgOxZSX5lC_47enk-lUNu4kAks5qX1mlgaJpZM4JL6kn
.

@mzipay something went wrong, this PR is not yet closed. Can you try again


There is no System.Metrics.Prometheus.Concurrent.Http

and this module is mentioned in the example in the .cabal file and README.

Fixed - thanks.

Thank you!


Use poetry for dependency management

Poetry is a modern way to manage python projects. Right now dependency management is a bit messy with 2 separate dependency lists in requirements and .github/workflows/constraints.txt. And you need to manually create virtualenv if you don't want to mess with system packages.

Poetry can install all project dependencies in virtualenv with poetry install and it manages dependency versions.
It separates between normal dependencies and dev dependencies (black, flake8, etc)
Then you can run any tools with poetry run, e.g. poetry run black, can be integrated with pre-commit as well.
Some extra configuration is required for dependabot.

I want to switch everything (pre-commit config, github actions) to use poetry.
Any objections?

No objections at all, not hand down 🤩💥
Never user poetry but I would love to hear and learn more about it! Thanks for taking an initiative with it 💥🤩

Same opinion as @leikoilja :smile:
And it looks very simple and easy use


Use a contract address in every call to wasmVM.Instantiate

In order to be able to migrate contract instances we need to instantiate contracts with contract addresses.
Context
In x/wasm contract migration requires the contract to have an address, which is passed in the env parameter. In 08-wasm we currently do not have addresses for the light client contracts. In x/wasm the contract address is generated during contract instantiation, each contract instance gets its own contract address.
In x/wasm there is MsgMigrateContract with a field contract that is the address of the contract that should be migrated. The code_id field references the new contract that migrates to.
Proposal
Investigate if we can use the client identifier as contract address (thanks @srdtrk for this suggestion). The 08-wasm module does not have knowledge of the client identifiers, so we need to investigate if we can retrieve it from the client-prefixed store that is passed to Initialize.
If we cannot use the client identifier as contract address, then we could generate a contract address using the code hash and a similar trick as we do when we generate the interchain account address. In the Initialize function we also have access to the client store, so we could store the contract address under a contracAddress key. We need this for https://github.com/cosmos/ibc-go/issues/4925 so that we can retrieve the contract address in MigrateContract.
Regardless of the contract address that we use, it needs to be passed to wasmVM.Instantiate in the env parameter.

Some initial thoughts after some research but before experimenting:

It seems possible to retrieve the clientID from the prefixed store (will verify experimentally later)
It is probably not necessary to pass the clientID or contractAddress to the env. Passing to env only allows the contract to know its own clientID. Regardless, I think we should pass it to env.
I don't know why this issue only covers wasmVM.Instantiate. We should be able to pass whatever address we use to Sudo, and Query as well (in the env).

I don't know why this issue only covers wasmVM.Instantiate. We should be able to pass whatever address we use to Sudo, and Query as well (in the env).

 Should be used in the other calls as well. Do you mind to add that as well in your PR?

Already in my PR @crodriguezvega. The only issue I faced is having to use reflect to get the value of prefix since it is a private field. (I didn't find any public getters for it)

closed by #4939, many thanks @srdtrk


[UI] In Container Details page the progress bar is over static text

In container details page if i hit the restart button, the progress bar is on top of static text.

Fixed in rancherio/ui#105

Verified Fixed


Create LICENSE.md

Fixes #6

sorry already fixed... try one of the other more involved issues if you'd like :)


Cross-platform "unixtools" derivation

Motivation for this change
"unixtools" is intended to replace uses of "procps" and "util-linux".  Also adds compatibility for "nettools". See #25188. Still needs better documentation.
List of tools guaranteed to be in "nettools"

arp(8)
hostname(1)
ifconfig(8)
netstat(8)
rarp(8)
route(8)

List of tools guaranteed to be in "unixtools"

cal(1)
chfn(1)
chsh(1)
col(1)
colcrt(1)
colrm(1)
column(1)
dmesg(1)
getopt(1)
hexdump(1)
kill(1)
last(1)
login(1)
look(1)
mesg(1)
newgrp(1)
nologin(8)
pgrep(1)
pkill(1)
ps(1)
renice(1)
rev(1)
script(1)
su(1)
sysctl(8)
ul(1)
uptime(1)
vipw(8)
wall(1)
whereis(1)
write(1)
w(1)

Success on x86_64-linux (full log)
Attempted: nettools, unixtools
Partial log (click to expand)
these derivations will be built:
  /nix/store/zjz0yd4bzn2v25piiawig75wl4wjvf4p-unixtools.drv
building '/nix/store/zjz0yd4bzn2v25piiawig75wl4wjvf4p-unixtools.drv'...
created 126 symlinks in user environment
/nix/store/44h6cshmzlb1mv045zl2n1f2n1wnzla1-net-tools-1.60_p20170221182432
/nix/store/9bq5jhh4dkqbni06pgn0y7r9zxiiqbwd-unixtools

Success on aarch64-linux (full log)
Attempted: nettools, unixtools
Partial log (click to expand)
these derivations will be built:
  /nix/store/ahv09dni626hsm699f56ga0hsr909d6f-unixtools.drv
these paths will be fetched (0.11 MiB download, 0.45 MiB unpacked):
  /nix/store/vwbcdkz7xjyy03z5lnryldyrdwrk0pwk-net-tools-1.60_p20170221182432
copying path '/nix/store/vwbcdkz7xjyy03z5lnryldyrdwrk0pwk-net-tools-1.60_p20170221182432' from 'https://cache.nixos.org'...
building '/nix/store/ahv09dni626hsm699f56ga0hsr909d6f-unixtools.drv'...
created 124 symlinks in user environment
/nix/store/vwbcdkz7xjyy03z5lnryldyrdwrk0pwk-net-tools-1.60_p20170221182432
/nix/store/xqwffvnn0ysg921r90qskpxy8wmzsjgx-unixtools

Success on x86_64-darwin (full log)
Attempted: nettools, unixtools
Partial log (click to expand)
copying path '/nix/store/j2z3v4g8y39ph0z03mh2cv2xaqvfmrai-shell_cmds-osx-10.11.6' from 'https://cache.nixos.org'...
copying path '/nix/store/wsp5kgs9gqwk8f7qy83v1kvsp32d4yq7-system_cmds-osx-10.11.6' from 'https://cache.nixos.org'...
copying path '/nix/store/9bn99x3y22sc44bp18a70nlqfjs1hlq0-libutil-osx-10.11.6' from 'https://cache.nixos.org'...
copying path '/nix/store/a634ammydlsmnq5653d7i93rkfaycx7k-adv_cmds-osx-10.11.6' from 'https://cache.nixos.org'...
building '/nix/store/mgw2qcjaa1m975mz6sfncsiza2ahhmc9-nettools-darwin.drv'...
building '/nix/store/dn9ij18vqzbjzvf6b67zcdaiip023vk7-unixtools.drv'...
created 83 symlinks in user environment
created 79 symlinks in user environment
/nix/store/nra9620i8shcc477zp4sqxz7cwg0lr6y-nettools-darwin
/nix/store/srxp2xknbvvsfi01mhx5h67ii7ksxjar-unixtools

How do we teach people to use unixtools instead of utillinux people already know?

Maybe it is better to have a unixtools derivation that includes only the tools provided on all supported platforms? Debugging macOS builds without access to macOS is annoying, so a package explicitly intended to be a compatibility layer should probably aim to behave in the same way everywhere.

How do we teach people to use unixtools instead of utillinux people already know? Would it be simpler to just call it utilinux?

I guess that's possible. It's a little bit inaccurate because of how many things are unavailable in BSDs:
https://en.wikipedia.org/wiki/Util-linux

Maybe it is better to have a unixtools derivation that includes only the tools provided on all supported platforms?

That seems like a good idea, and something I think we can do with buildEnv.

An alternative to have one set of packages would be to explicit: for example having an attribute called kill.

So I thought about this and I think for kill and ps at least it makes sense. We probably still want some sort of compatibility for procps, etc.

Ok so I've redone this PR. Interested in whether this breaks anything on Linux. So far so good! Still needs documentation though.

@7c6f434c We can maybe put warnings on the originals, telling people to use these instead?

We can maybe put warnings on the originals, telling people to use these instead?

That's probably not going to work for certain cases. For instance unshare only exists in Linux AFAIK. I think it might make more sense to just refer to util-linux for that (I guess we could provide "unshare" here and throw an error on non-Linux).
There are definitely a lot more commands that we could add but are unavailable on Darwin for various reasons (I haven't been able to get pkill or pgrep to build correctly).

@matthewbauer Yeah even if its missing some places (or like unshare unlikely to be ported) I think its better to list them one by one.

Re: warnings: these warnings will also happen for user environment construction, though, which is not desirable. I think that we need to create a stalled RFC (I have no illusions here) to gather enough support to just slowly convert most cases. If the RFC gets little support of gets actually closed, then we know this won't work…
(Note that sometimes it does make sense to use full util-linux for a build, too…)

@7c6f434c I do not understand what you want to make a RFC about?

The new version looks much better and future proof (with regards to new platforms).

Deprecate usage of utillinux and procps as build inputs for packages in the Nixpkgs mainline.

@7c6f434c I don't think we need an RFC for that. There are not really deprecated. This is just an abstraction that uses either utillinux or something else depending on the platform to have less nix boiler code and less breakages, if macOS support breaks by people adding utillinux to buildInputs.

@Mic92 I believe you two are in agreement. @7c6f434c is saying that the possible next step of deprecating the old ones would require an RFC. Nobody thinks this PR needs an RFC.

I will write a section in the manual under "Packaging in a cross-friendly manner" tonight if I find the time.
But what are opinions on this? I'd like to get it merged into staging soonish but also keep working on some of the edge cases (especially with adding new "tools"). This shouldn't break anything but just want to make sure people are okay with this PR (or at least not strongly against).

I really like the idea of making the commands explicit instead of using package collections like utillinux that don't work across multiple platforms. I'm not entirely sure if it's a good idea to expose the fallback collections top-level since not everything is in there but it's probably fine is most cases.

Merging now, so @Ericson2314 can make his changes. Also working on some documentation but that will go in another PR. (sorry for the large merge!)

FWIW looks like hexdump should come from utillinux (or utillinuxMinimal? not sure), it's not available in procps where we currently try to grab it from.
(I'd put together a PR but am currently rebuilding all the things to get to the point where I can test such.. haha)

Ok thanks! I hope none of these tools are used in bootstrapping stdenv. My understanding is utillinuxMinimal only makes sense in those cases (although it does have hexdump, so maybe it would shrink dependencies).


TFTdisplay

Hello, dear staub!
I want to ask you to help me. Could you write an example using a TFT display?
I've been trying to understand your library, but since I'm a low-level programmer, I don't have an understanding of some complex lines of code.
Thank you.

No, the code depend on the display type and driver. So use the example codes of the display vendor as a start point.


Free Open Source GitHub Security Engineer plugin - Hardens Code, Fixes Bugs & addresses Sonar Issues

To start receiving these code recommendations, install pixeebot for your repo here, https://github.com/apps/pixeebot.

Helpful Recommendations @pixeebot has already provided:
https://github.com/netease-youdao/QAnything/pulls?q=is%3Apr+is%3Aclosed+author%3Apixeeai+


Reschedule with freq

Currently Reschedule() only allows you to set the start time. It doesn't let you change the frequency which means I need to destroy the original job and create a new one. This is more error prone and slower because I need to update reference job id's in my db to do this. It might also be a good idea to let us change a job's retry count.

@epelc thank you. To keep the API consistent and preserve backwards compatibility, I'll add a RescheduleRecurring method. So then we'll have Schedule and ScheduleRecurring which are methods on job.Type and Reschedule and RescheduleRecurring which are methods on job.Job. Targeting this for 0.3.1.

@albrow Thanks!


[Do Not Merge] Generate SBOM for CPython dependency.

Summary

Conform to new filesystem-based SBOM introduced in packit v2. See #288.
Also there were some minor tweaks to integration tests to fix the logging assertions - we were asserting some lines were empty when they actually contained deprecation notices. These deprecation notices aren't relevant to the tests, so I removed the empty line assertion entirely, rather than replacing it with a new deprecation assertion. We could have bumped the version of python that these tests were using to avoid the deprecation notice, but I felt that was a bigger change than removing an assertion that a line was empty.
Use Cases
See #288.
Checklist

[x] I have viewed, signed, and submitted the Contributor License Agreement.
[x] I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
[x] I have added an integration test, if necessary.
[x] I have reviewed the styleguide for guidance on my code quality.
[x] I'm happy with the commit history on this PR (I have rebased/squashed as needed).

There have been enough changes to the way we want to approach SBOM and the way we would implement it that it would be simpler and quicker to start over rather than leverage this PR. I'm going to close this without merging.


Release v1.6.0

The release enables metrics support by default as OpenTelemetry Go metrics API is stable (v1.16.0).

Added

Add Version function to the following Go modules. (#1992)

github.com/signalfx/splunk-otel-go/distro
github.com/signalfx/splunk-otel-go/instrumentation/database/sql/splunksql
github.com/signalfx/splunk-otel-go/instrumentation/github.com/confluentinc/confluent-kafka-go/kafka/splunkkafka
github.com/signalfx/splunk-otel-go/instrumentation/github.com/go-chi/chi/splunkchi
github.com/signalfx/splunk-otel-go/instrumentation/github.com/gomodule/redigo/splunkredigo
github.com/signalfx/splunk-otel-go/instrumentation/github.com/graph-gophers/graphql-go/splunkgraphql
github.com/signalfx/splunk-otel-go/instrumentation/github.com/miekg/dns/splunkdns
github.com/signalfx/splunk-otel-go/instrumentation/github.com/syndtr/goleveldb/leveldb/splunkleveldb
github.com/signalfx/splunk-otel-go/instrumentation/github.com/tidwall/buntdb/splunkbuntdb
github.com/signalfx/splunk-otel-go/instrumentation/gopkg.in/olivere/elastic/splunkelastic
github.com/signalfx/splunk-otel-go/instrumentation/k8s.io/client-go/splunkclient-go

Add WithMeterProvider function in github.com/signalfx/splunk-otel-go/instrumentation/database/sql/splunksql. (#2258)

Changed

OTEL_METRICS_EXPORTER defaults to otlp. Therefore, metrics support are enabled by default. (#2259)

Fixed

Fix telemetry.sdk.version resource attribute to properly return the github.com/signalfx/splunk-otel-go/distro Go module version. (#1990)
Fix instrumentation scope version value to properly return the instrumentation library versions. (#1990)

Removed

Drop support for Go 1.18 as go.opentelemetry.io did the same in [v1.15.0][otel-v1.15.0]. (#2095)

Codecov Report
Patch and project coverage have no change.

Comparison is base (c8fb88d) 82.15% compared to head (3bebea9) 82.15%.

:exclamation: Current head 3bebea9 differs from pull request most recent head 464d478. Consider uploading reports for the commit 464d478 to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2262   +/-   ##
=======================================
  Coverage   82.15%   82.15%
=======================================
  Files          76       76
  Lines        2891     2891
=======================================
  Hits         2375     2375
  Misses        451      451
  Partials       65       65

Flag
Coverage Δ

Linux
82.15% <ø> (ø)

macOS
78.55% <ø> (ø)

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


[Improvement]helm does not support storage options

Describe the question
Currently installing dolphinscheduler through helm does not enable the HDFS enabling option, but using the resource center in dolphinscheduler requires HDFS to be mandatory
What are the current deficiencies and the benefits of improvement
Hope the helm installation method can add support for HDFS parameterization
Which version of DolphinScheduler:
-[1.3.x]

Close by #4693, since 1.3.5-release has supported


Update Documentation for 64bit

The advise regarding detection rule probably needs to be updated to address the 64 bit client.

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

ID: 087b8ed9-0b08-88a2-825f-727915801554
Version Independent ID: afd3bb47-f8a7-d1eb-a790-ff49c0794d2f
Content: Install the sync app per machine - OneDrive
Content Source: OneDrive/per-machine-installation.md
Service: one-drive
GitHub Login: @adeejoseph
Microsoft Alias: adjoseph

Hello @SirBeredan how are you? Hope you are doing good.
The 64-bit client is still in public preview, once it reaches GA the article could be updated.
Thank you!