App.java:64-67: LCC metric has impediments (see puzzles...

The puzzle 9-e2b8b5ba from #9 has to be resolved:
https://github.com/yegor256/jpeek/blob/b625770426cbfa670c987c135c0b3c98b7a24c8d/src/main/java/org/jpeek/App.java#L64-L67
The puzzle was created by Kapralov Sergey on 26-Jan-18.
Estimate: 30 minutes, role: IMP.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

The job #118 assigned to @llorllale/z. The budget is 30 minutes, see §4. Please, read §8 and §9. If the task is not clear, read this and this.

blocked by #119

@yegor256 this puzzle states it depends on another open puzzle (see #119). What can we do here while #119 isn't fixed?

@llorllale just put it on hold, see http://datum.zerocracy.com/pages/policy.html#9

@yegor256 then I'd have to assume the opportunity cost of having it take up one of the slots on my agenda as per http://datum.zerocracy.com/pages/policy.html#3.
Should this job have been put in scope before fixing its declared impediments?

@llorllale you can reject it. Otherwise, you can try to move forward a bit, via PDD.

@0crat refuse

@0crat refuse (here)

@llorllale The user @llorllale/z resigned from #118, please stop working

Tasks refusal is discouraged, see §6: -15 points just awarded to @llorllale/z, total is +510

The job #118 assigned to @nikialeksey/z, here is why. The budget is 30 minutes, see §4. Please, read §8 and §9. If the task is not clear, read this and this.

@nikialeksey/z this job was assigned to you 5 days ago. It will be taken away from you soon, unless you close it, see §8. Read this and this, please.

@0crat refuse

@0crat refuse (here)

@nikialeksey The user @nikialeksey/z resigned from #118, please stop working

Tasks refusal is discouraged, see §6: -15 points just awarded to @nikialeksey/z, total is +60

@0pdd all puzzles are solved

@0pdd all puzzles are solved

@0pdd all puzzles are solved

The job #118 assigned to @t-izbassar/z, here is why. The budget is 30 minutes, see §4. Please, read §8 and §9. If the task is not clear, read this and this.

@0crat waiting for #217 to be resolved as it is crucial part of introducing this metric.

@0crat waiting for #217 to be resolved as it is crucial part of introducing this metric. (here)

@t-izbassar The impediment for #118 was registered successfully by @t-izbassar/z

@0crat refuse

@0crat refuse (here)

@t-izbassar Job gh:yegor256/jpeek#118 is not assigned, can't get performer

@0crat status

@0crat status (here)

@t-izbassar This is what I know about this job, as in §32:

The job #118 is in scope for 1mon
The role is DEV
The job is not assigned to anyone
The budget is 30 minutes/points
These users are banned and won't be assigned:

@0pdd/z: This user reported the ticket
@llorllale/z: User was resigned from the ticket
@nikialeksey/z: User was resigned from the ticket
@t-izbassar/z: User was resigned from the ticket

Job footprint (restricted area)

@0crat status

@0crat status (here)

@yegor256 This is what I know about this job, as in §32:

The job #118 is in scope for 1mon
The role is DEV
The job is not assigned to anyone
The budget is 30 minutes/points
These users are banned and won't be assigned:

@0pdd/z: This user reported the ticket
@llorllale/z: User was resigned from the ticket
@nikialeksey/z: User was resigned from the ticket
@t-izbassar/z: User was resigned from the ticket

Job footprint (restricted area)

The job #118 assigned to @sharpler/z, here is why; the budget is 30 minutes, see §4; please, read §8 and §9; if the task is not clear, read this and this

@sharpler/z this job was assigned to you 5days ago. It will be taken away from you soon, unless you close it, see §8. Read this and this, please.

@0crat waiting
For reviewer.

@0crat waiting For reviewer. (here)

@SharplEr The impediment for #118 was registered successfully by @sharpler/z

The job #118 assigned to @uurl/z, here is why; the budget is 30 minutes, see §4; please, read §8 and §9; if the task is not clear, read this and this

@yegor256 ready for review

@0crat wait #232

@0crat wait #232 (here)

@uurl The impediment for #118 was registered successfully by @uurl/z

@0crat wait #239

@0crat wait #239 (here)

@uurl Job #118 is already on hold

@0crat status

@0crat status  (here)

@uurl This is what I know about this job, as in §32:

The job #118 is in scope for 4mon
The role is DEV
The job is assigned to @uurl/z for 10days
There is a monetary reward attached
@uurl/z will get 50% of their hourly rate for this job
The job has an impediment
The budget is 30 minutes/points
These users are banned and won't be assigned:

@0pdd/z: This user reported the ticket
@llorllale/z: User was resigned from the ticket
@nikialeksey/z: User was resigned from the ticket
@t-izbassar/z: User was resigned from the ticket
@sharpler/z: User was resigned from the ticket

Job footprint (restricted area)

@0crat wait #242

@0crat wait #242 (here)

@uurl Job #118 is already on hold

@yegor256 please close this with #242

@yegor256 please close this with #242

The puzzle 9-e2b8b5ba has disappeared from the source code, that's why I closed this issue.

@0pdd 2 puzzles #252, #253 are still not solved.

@elenavolokhova/z please review this job completed by @uurl/z, as in §30; the job will be fully closed and all payments will be made when the quality review is completed

The job #118 is now out of scope

@0crat quality good

Order was finished, quality is "good": +35 point(s) just awarded to @uurl/z

Quality review completed: +8 point(s) just awarded to @elenavolokhova/z

@0pdd 2 puzzles #253, #356 are still not solved; solved: #252.

@0pdd 2 puzzles #252, #253 are still not solved; solved: #356.

@0pdd the puzzle #252 is still not solved; solved: #253, #356.

@0pdd the puzzle #514 is still not solved.


Join filtering and WDC 2.2

Coverage increased (+55.8%) to 100.0% when pulling 1d71274c2be57f10bb2e25fadd03fe7a92f0e8a2 on jdomingu:master into 4db90d972a58c71033cb9a5c292c333fd721be6f on tableau:master.

This looks awesome!

👍 Thanks for the merge!


Make .info.json file more stable across releases

It's often nice to look at diffs to understand how the JS is changing – but for even medium-sized apps there is huge churn with a small change.
It'd be nice if the numeric ID, perhaps some sort of name-based SHA or something to improve diffs?

Totally agree!
We have the infrastructure changes to make it easier to change the info format in the future. We need to either support multiple versions of the info format (which we can do) or migrate the visualizer app to use our new infrastructure, so we can make breaking changes in the format.
I'm closing this bug entry though, since we are tracking this by the following 2 issues in the dart2js_info repo:
https://github.com/dart-lang/dart2js_info/issues/12
https://github.com/dart-lang/dart2js_info/issues/5


[MVP] Enable an App installation with K8S API

Towards https://github.com/giantswarm/roadmap/issues/90 Migrate GS API to Kubernetes API
User Story

As a GS user with write access to CP, I can create an App using K8S API

Acceptance criteria

Given that I have a 'write' access to CP API I can create an App CR which will spin-up a new App

Tasks

[ ] add user-facing documentation
[ ] add CRD schema for validation

@pipo02mix once we have the docs you are creating, we can update installing ingress controller via CP k8s API too right?

Well even without docs it can be done now 😃
My docs are describing how to create an App Catalog and install the Apps in your cluster through the Control Plane API.
IMO this specific documentation can be added to the existing guide. But I will create another ticket for that

I need to follow this process to publish eh changes

Changes published :)
I will add some definitions for Chart CRD

Added Chart CRD docs too. I will move to validation next week

This is week I have more availability to work on this

For this cycle, @pipo02mix will work on "Defaulting and validation of apps for people creating apps in app catalog."

I could not get much progress here. I am going to opt out as I don't have much time and it is not under my goals team anymore.
I checked the catalog tutorial since I have another ticket to track this https://github.com/giantswarm/giantswarm/issues/10758

@giantswarm/team-batman do anyone of you feel like picking this up?

'this' == owning this feature, providing documentation, working with adidas (specifically) to get feedback

@cokiengchiara closing this as MVP works and defaulting/validation is out of scope here, we need a separate issue for this.


Gulp-sass node modules error - failed to build project via jenkins

Since today morning i failed to build my project via Jenkins job and deploy it to amazon,
I think the issue is because, today there was a new node-sass  release v0.3.9  - that i think broke gulp-sass node-module (see below)
AWSEB Deployment Plugin Version 0.3.10
Zipping contents of Root File Object (community commit builds) into tmp file awseb-4760291425392070535.zip (includes=, excludes=)
FATAL: Deployment Failure
java.io.IOException: Deployment Failure
at br.com.ingenieux.jenkins.plugins.awsebdeployment.AWSEBDeploymentBuilder.perform(AWSEBDeploymentBuilder.java:171)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)
at hudson.model.Build$BuildExecution.build(Build.java:205)
at hudson.model.Build$BuildExecution.doRun(Build.java:162)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)
at hudson.model.Run.execute(Run.java:1720)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:404)
Caused by: java.util.concurrent.ExecutionException: hudson.os.PosixException: native error calling stat: No such file or directory /home/jenkins/workspace/community commit builds/node_modules/gulp-sass/node_modules/node-sass/test/fixtures/spec/spec/libsass/Sa??ss-UT??F8 ENOENT
at hudson.remoting.Channel$2.adapt(Channel.java:829)
at hudson.remoting.Channel$2.adapt(Channel.java:824)
at hudson.remoting.FutureAdapter.get(FutureAdapter.java:55)
at br.com.ingenieux.jenkins.plugins.awsebdeployment.DeployerRunner.perform(DeployerRunner.java:66)
at br.com.ingenieux.jenkins.plugins.awsebdeployment.AWSEBDeploymentBuilder.perform(AWSEBDeploymentBuilder.java:167)

Sorry I don't understand what I'm looking at, I don't do Java. It looks you're having an issue with utf-8 file names

No such file or directory /home/jenkins/workspace/community commit builds/node_modules/gulp-sass/node_modules/node-sass/test/fixtures/spec/spec/libsass/Sa??ss-UT??F8 ENOENT

Same problem for me on Jenkins. A new version of node-sass has been released today. I think that might be the cause of this problem.

Yes I released that version. However without understand the problem it can't be fixed.

This is Java because of Jenkins job trying to zip the project before deploying it to AWS.
What i saw is that the output of the npm install is a file with known UTF-8 name in the dist directory:
node_modules/gulp-sass/node_modules/node-sass/test/fixtures/spec/spec/libsass/

The fact is that node-sass began including its test directory since version 3.9.0, where some directory name in sass-spec has a name with UTF-8 characters for putting an acute over preceding letter and a cedilla under other letter.
I would recommend to update the dependencies so that gulp-sass would limit itself to node-sass being at most 3.7.0, where the test directory is not exported. At least until node-sass maintainers consider their practice to be armful to part of the community, using Jenkins or Bamboo.

would recommend to update the dependencies so that gulp-sass would limit itself to node-sass being at most 3.8.0

We will not do this. It would defeat the purpose of gulp-sass. Feel free to shrink wrap your dependencies if you wish.

At least until node-sass maintainers consider their practice to be armful to part of the community

We do not consider this harmful.

Hudson, Jenkins or Bamboo which are based on Java where some rules are enforced on file names

This is not the case. As pointed out in https://github.com/sass/node-sass/issues/1699#issuecomment-244801171 this is a known bug in Jenkins. There are existing work arounds in.
https://issues.jenkins-ci.org/browse/JENKINS-12610
https://issues.jenkins-ci.org/browse/JENKINS-33478


Limited Background Colours are available (Materials Tailwind + Next.js + React)

Hi,
I'm new to Material Tailwind, Tailwind CSS, Node.js and everything React, so it's possible I'm doing something wrong.
In the ThemeProvider configuration object, for a tooltip I can set the background colour to bg-yellow-500 but not bg-yellow-300, etc.  Only 500.  (although blue-grey can be 500, 100, or 50)
Should this be possible?
From what I understand the following colour pallet should be supported:
https://www.material-tailwind.com/docs/react/colors
or
https://tailwindcss.com/docs/background-color
or both?
Below is reproducing steps.  I'm happy to help out if investigation is needed.
The relevant file is config/materials_tailwind.js here.  Steps to reproduce follow.
export const MATERIALS_TAILWIND_THEME = {
  button: {
    defaultProps: {
      className: 'w-fit',
      color: 'green',
    },
  },
  tooltip: {
    styles: {
      base: {
        bg: 'bg-yellow-500',
        text: 'text-green-500',
        width: 'max-w-md',
      },
    },
  },
}

Create a new Tailwind CSS/Next.js application:
https://tailwindcss.com/docs/guides/nextjs
npx create-next-app my-project
cd my-project
npm install -D tailwindcss postcss autoprefixer
npx tailwindcss init -p

I also installed:
npm install -D prettier-plugin-tailwindcss @material-tailwind/react

Add Tailwind to ./styles/globals.css:
@tailwind base;
@tailwind components;
@tailwind utilities;

Add material tailwind hooks:
tailwind.config.js
const withMT = require("@material-tailwind/react/utils/withMT")

module.exports = withMT({
  content: [
    './pages/**/*.{js,ts,jsx,tsx}',
    './components/**/*.{js,ts,jsx,tsx}',
  ],
  theme: {
    fontFamily: {
      quicksand: 'Quicksand, sans-serif',
      inter: 'Inter, sans-serif',
    },
    extend: {
    },
  },
  plugins: [],
})

pages/_app.js
import '../styles/globals.css'
import { ThemeProvider } from '@material-tailwind/react';
import { MATERIALS_TAILWIND_THEME } from '../config/materials_tailwind';

export default function MyApp({ Component, pageProps }) {
  return (
    <ThemeProvider value={MATERIALS_TAILWIND_THEME}>
      <Component {...pageProps} />
    </ThemeProvider>
  );
}

config/materials_tailwind.js (Shown above)

pages/index.js
import { Button } from "@material-tailwind/react";
import { Tooltip } from "@material-tailwind/react";
...

            Welcome to Tailwind CSS!

          <Tooltip content='This is a test tooltip!'>
            <Button>Continue</Button>
          </Tooltip>

...

With bg-yellow-500 the tooltip background is yellow.  With bg-yellow-300 the tooltip background is transparent.
Thanks.

As a workaround, I found that adding a className directly to the component invocation will accept any colours:
components/CustomTooltip.jsx:
import { Tooltip } from '@material-tailwind/react'

export default function CustomTooltip({ content, children }) {
  if (!content) return children;

  return (
    <Tooltip className='bg-yellow-300' content={content}>
      {children}
    </Tooltip>
  )
}

This has been working well for all the components and even custom defined colours.

Hi @UBCToad,
The color props for component are only getting the 500 color code but if you wish to have more you can use className prop the classNam prop is available for all components and it will help you for customizing the components. For the future update we will try to have a prop level for defining the color level of component, e.g.
<Tooltop color="yellow" level="300" />
Cheers,
Sajad


pkg/labels: ignore all labels that match the regex "annotation.*"

This will help to decrease the cardinality of labels used to create a
security identity since pod annotations can be used for enumerous reasons
and aren't used for network policy enforcement.
Signed-off-by: André Martins<EMAIL_ADDRESS>

This change is

test-me-please

Coverage increased (+0.009%) to 41.927% when pulling 6b61dc71ab84be427edb1a07ddb45c9bd2ffd493 on pr/ignore-annotation-labels into ec3910f1f33e866885a08aede919f270b2912975 on master.

test-me-please


athom-rgbct-light: changed behaviour since updates

I've recently updated the firmware on my 'athom-rgbct-light' (15W color bulb) lights to 2024.9.x (from something from 2023).
In this example I'm using one that has the name and friendly_name set to 'bedroom-light'
This changed the behavior in a few annoying ways:

The device name in HA changed from 'light.bedroom_light_bedroom_light to light.bedroom_light_rgbcct_bulb, breaking all automation and cards
The default behavior on power loss changed so that it now stays off (it goes on for a split second, then turns off once it connects); this stops us from using the normal light switches in the house
I seem to no longer be able to set the light to a specified brightness in the automations in HA. I can still brightness_increase and brightness_decrease, but not set a specific %

I think the reason is the changes in e1b4785afa538e04f53a399765187848fe1f3db9 but I'm not sure about all technical details.
Contents of my bedroom-light.yaml ESPHome configuration for this example:
substitutions:
  name: bedroom-light
  friendly_name: bedroom-light
packages:
  athom.rgbct-light: github://athom-tech/athom-configs/athom-rgbct-light.yaml
esphome:
  name: ${name}
  name_add_mac_suffix: false
  friendly_name: ${friendly_name}
api:
  encryption:
    key: *snip*

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password

It should have an option to select the power on state

Hi, thank you for your reply!
I checked and this is indeed set to 'Always off'; however when I change this setting, then turn off the power - it resets to 'Always off' whenever the light comes back online.


Flush handlers after configuring sysctl

Description
Server/agent does not start when cis profile is set on new nodes. sysctl's need to be applied (systemd-sysctl restarted) before starting the server/agent. Play will hang on "Wait for remaining nodes to be ready". The server/agent complains about the following:
level=fatal msg="invalid kernel parameter value vm.overcommit_memory=0 - expected 1\ninvalid kernel parameter value kernel.panic=0 - expected 10\ninvalid kernel parameter value kernel.panic_on_oops=0 - expected 1\n"

Type of change

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] Small minor change not affecting the Ansible Role code (Github Actions Workflow, Documentation etc.)

How Has This Been Tested?
Tested adding a new (freshly installed ubuntu 22.04) server and agent to an existing rke2 cluster with this change (and cis-1.23 profile set). Without flushing the handlers, the play hang on waiting for all nodes to be ready as the new nodes rke2 service was not starting. After the change, the rke2 service starts and the play completed succesfully.

LGTM. Thanks


Extensions incompatible with react-helmet

Hi @schiehll ! Thanks for this extension.
Im using this one with react-helmet and react-router, so this is the Root component structure for render:

so, with this structure im getting empty tags for react-helmet under the SSR. but when page loads in browser - seems all tags are on their place.
when im trying to remove AlertProvider - all tags are appearing as well
can u check what is the problem about ?
Thank u!

hm, I use 3.4.0 version before and issue was reproducible.
right now im using 4.0.2 and can't reproduce it.
i think issue can be closed


Cluster not working consistently

ping @saleiva for who this goes to please
cc @iriberri
ref s/b 6464091
Expected:
individual markers will be replaced by one larger marker when points have the same lat/lon values and the Cluster wizard is chosen.
Happening:
exactly overlapping points with same lat/lon don't cluster if there are less than 5 of them.
Test: http://cdb.io/1XlJ18U
Also some points cluster at a zoom level, and when you zoom out another level instead of staying clustered they break up (like with the 6 marker below). Def expected on zoom in, not sure if this is expected on zoom out b/c of the way aggregation grid is drawn?

Yep, known issue.

There has been no activity on this issue for more several months. We are closing it. If you think this still needs to be addressed please open a new issue.


Check that binding AnimObject to another AnimObject works

There is a working example in mwe_zooms. Now just check what happens when parent AnimObject has no inner space.


feat: added support json type

This PR add json type for some supported database like: mysql, postgres and may be mssql.

This is great! thanks for the MR


Blank auctions controller

Basics – added a new view controller and bridging header, and Swift import header. Adding subsequent Swift files should be easier.
I'm going to try later to merge the bridging header and PCH file somehow so we can auto-import those files into Swift and into ObjC :smiling_imp:

I'm going to try later to merge the bridging header and PCH file somehow so we can auto-import those files into Swift and into ObjC :smiling_imp:

Try to not do this ASAP, I'm interested in the seams for what a VC really needs to exist in eigen.

failure looks legit

Cool coo, looking into it.

and the danger thing was brought up in our notifications chat room earlier, I can look at that tomorrow

:white_check_mark:
No errors found

:white_check_mark:
No warnings found

  Generated by
    danger
  on
  2016-01-07

:tada:

Thanks :+1:


Is the date value for the output based on the IP and if so is it possible to base it on the system date instead?

Checklist

[X] I'm asking a question and not reporting a bug/feature request
[X] I've looked through the README
[X] I've read the guidelines for opening an issue
[X] I've searched the bugtracker for similar questions including closed ones

Question
My system timezone is set to UTC and when I checked a newly uploaded video on youtube it matches the date on my system but when I downloaded it with yt-dlp the date is different. Is it possible to make the date value match my system date?

The timestamp returned should always be UTC irrespective of IP or system timezone

That's weird. Is it possible that the upload_date of a video might be different if the video is a scheduled upload? I have screenshot proof that the video I am talking about was uploaded on 20211128 it even says so on YouTube. But when I downloaded it again it still says that the upload_date is 20211127.

I also want to ask if it is normal that a normal video upload doesn't have an epoch timestamp string in the info.json? Because a livestream has a timestamp string in its info.json despite it being equivalent to "NA" on the output template.

That's weird. Is it possible that the upload_date of a video might be different if the video is a scheduled upload? I have screenshot proof that the video I am talking about was uploaded on 20211128 it even says so on YouTube. But when I downloaded it again it still says that the upload_date is 20211127.

Give link

I also want to ask if it is normal that a normal video upload doesn't have an epoch timestamp string in the info.json? Because a livestream has a timestamp string in its info.json despite it being equivalent to "NA" on the output template.

Yes. The exact timestamp is only known for livestreams (and only before they end, I believe)

Here's the link https://www.youtube.com/watch?v=rcOAHTlBUKM

I tried using the youtube api and grabbed the metadata of the link I posted. According to the response the "publishedAt" value is "2021-11-28T04:00:12Z". That's the only timestamp available there.

We could enforce timezone to UTC for YouTube by default for consistency and certainty. Pretty much the same as how we currently enforce English.
But, I'm also not certain on what YouTube defaults to. @pukkandan mentioned theirs defaulted to a US timezone.

if we can set it, UTC is best imo. The docs imply it should be UTC
    timestamp:      UNIX timestamp of the moment the video was uploaded
    upload_date:    Video upload date (YYYYMMDD).
                    If not explicitly set, calculated from timestamp.

So, I think I found what the actual issue you were seeing is. But it goes deeper,  the timezones of dates and times extracted and processed throughout the YouTube extractor are/can be all over the place :sweat_smile:
For webpage and the API, any sort of date text is returned in the client's timezone (UTC by default). However, the upload and published dates in the playerResponse are fixed to a timezone (UTC-??, prob PT) regardless of client preference. This is the date we (and youtube-dl) use for the video upload date, hence the discrepancy you noticed.
Ideally, as described by pukkandan, everything should be in UTC. So we could do the following to try achieve this:

enforce UTC for API/webpage calls - though this is YouTube's default, it is needed to override any tz pref from cookies
prefer dateText for video upload date (which is localized to client timezone) over the playerResponse upload date - will need to wait till #2069 . This will also add upload date extraction for non-web clients.
fix (or add an option to set tz) datetime_from_str using computer's timezone for relative time calculations (yes, this has made me notice that we are calculating the relative time based on your computers timezone, from relative time text based in UTC, and then converting the result into a UNIX timestamp that is supposed to be in UTC :laughing:). This affects the estimated dates processed from relative time text for comments, video upload dates extracted from feeds, and playlist modified times (being added in #2069).


Upgrade jemalloc to 5.3 RC

This is part of the work for compiling Sorbet on M1 macs
Upgrade jemalloc to release candidate 5.3, which has support for ARM64. Additionally, we are now setting the path for homebrew openssl in M1 machines.
Motivation
We need to upgrade to get ARM64 support.
Test plan
Current tests should cover the upgrade.

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build results here:
→ https://go/builds/bui_L5NfIAHfMaZXVG
→ https://go/builds/bui_L5Nf8kVZC6nC88


Fix robustSolitonDistribution CDF

The robustSolitonDistribution seems missing plus operator. According to Luby's LT codes paper, we need to sum the tau and rho. But current code using only tau in ( i < m ) condition. I think need to add plus operator in line 62.

Hello, I signed it!

Hi! I can't quite tell from the bot what it concluded. It looks like it wants to find an email address correspondence? I'm happy to look at the patch. Should I look at the other PR?

Hi! Please ignore this PR, I've opened other PR with clean branch :)


[Bug]: mxstep steps taken before reaching tout with customized piecewise LFP OCP function

PyBaMM Version
23.1
Python Version
3.9.5
Describe the bug
I was using Prada2013 dataset & my customized LFP OCV function, and I encounter "At t = 0.00500431, , mxstep steps taken before reaching tout." warning & simulation breaks down when the simulated time is long:
param = model.default_parameter_values
timescale = param.evaluate(model.timescale)
t_end = 0.15*timescale
t_eval = np.linspace(0, t_end, 1500)

However, if I set
t_end = 0.10*timescale
t_eval = np.linspace(0, t_end, 1000)

the simulation goes well and I get the simulated result.
Steps to Reproduce
parameter_values = pybamm.ParameterValues("Prada2013")
parameter_values["Positive electrode OCP [V]"] = LFP_OCP # a customized piecewise function
model = pybamm.lithium_ion.DFN()
param = model.default_parameter_values
timescale = param.esvaluate(model.timescale)
t_end = 0.015*timescale
t_eval = np.linspace(0, t_end, 1500)
sim = pybamm.Simulation(model, parameter_values=parameter_values)
sim.solve(t_eval = t_eval, initial_soc=0.95)

Relevant log output
At t = 0.00500431, , mxstep steps taken before reaching tout.
At t = 4.99029e-06, , mxstep steps taken before reaching tout.
At t = 4.99029e-06, , mxstep steps taken before reaching tout.
At t = 4.99029e-06, , mxstep steps taken before reaching tout.
At t = 4.99029e-06, , mxstep steps taken before reaching tout.
At t = 4.99029e-06, , mxstep steps taken before reaching tout.
At t = 4.99029e-06, , mxstep steps taken before reaching tout.
Traceback (most recent call last):
  File "/Users/archieyao/tools/miniconda3/lib/python3.9/site-packages/pybamm/solvers/casadi_solver.py", line 669, in _run_integrator
    casadi_sol = integrator(
  File "/Users/archieyao/tools/miniconda3/lib/python3.9/site-packages/casadi/casadi.py", line 7772, in __call__
    return self.call(kwargs)
  File "/Users/archieyao/tools/miniconda3/lib/python3.9/site-packages/casadi/casadi.py", line 6945, in call
    return _casadi.Function_call(self, *args)
RuntimeError: .../casadi/interfaces/sundials/idas_interface.cpp:591: IDASolve returned "IDA_TOO_MUCH_WORK". Consult IDAS documentation.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Users/archieyao/tools/miniconda3/lib/python3.9/site-packages/pybamm/solvers/casadi_solver.py", line 241, in _integrate
    current_step_sol = self._run_integrator(
  File "/Users/archieyao/tools/miniconda3/lib/python3.9/site-packages/pybamm/solvers/casadi_solver.py", line 675, in _run_integrator
    raise pybamm.SolverError(error.args[0])
pybamm.expression_tree.exceptions.SolverError: .../casadi/interfaces/sundials/idas_interface.cpp:591: IDASolve returned "IDA_TOO_MUCH_WORK". Consult IDAS documentation.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Users/archieyao/Desktop/pybamm_run/test.py", line 56, in <module>
    sim.solve(t_eval = t_eval, initial_soc=0.95) # , solver=pybamm.CasadiSolver(mode="safe", dt_max=0.01)
  File "/Users/archieyao/tools/miniconda3/lib/python3.9/site-packages/pybamm/simulation.py", line 608, in solve
    self._solution = solver.solve(self.built_model, t_eval, **kwargs)
  File "/Users/archieyao/tools/miniconda3/lib/python3.9/site-packages/pybamm/solvers/base_solver.py", line 875, in solve
    new_solution = self._integrate(
  File "/Users/archieyao/tools/miniconda3/lib/python3.9/site-packages/pybamm/solvers/casadi_solver.py", line 276, in _integrate
    raise pybamm.SolverError(
pybamm.expression_tree.exceptions.SolverError: Maximum number of decreased steps occurred at t=226.58912512726562 (final SolverError: '.../casadi/interfaces/sundials/idas_interface.cpp:591: IDASolve returned "IDA_TOO_MUCH_WORK". Consult IDAS documentation.'). For a full solution try reducing dt_max (currently, dt_max=7.08186861061253) and/or reducing the size of the time steps or period of the experiment. Set `return_solution_if_failed_early=True` to return the solution object up to the point where failure occured.

I have changed the parameter set according to  https://github.com/pybamm-team/PyBaMM/commit/eabb72040892b964907e01cdc09130a7e25a1489
parameter_values = pybamm.ParameterValues("Prada2013")
parameter_values["Current function [A]"] = 1.1
parameter_values["Typical current [A]"] = 1.1
parameter_values["Initial concentration in negative electrode [mol.m-3]"] = 13584.0
parameter_values["Initial concentration in positive electrode [mol.m-3]"] = 35.0
parameter_values["Positive electrode porosity"] = 0.26
parameter_values["Positive electrode active material volume fraction"] = 0.5846
parameter_values["Positive particle radius [m]"] = 5.00e-8

problem solved, it's because of non-monotonicity of OCV function


Change ssv.complete to ssv.need

Redefine complete without uniq and rename to need
because union seems more useful for unique sets

I'm not 100% about needing this but giving it a try


Move bulk get to state store interface

Describe the proposal
Current state store interface doesn't have a bulk get method (though it has bulk set and bulk delete). Dapr API offers bulk get API, which loops through requested keys and invoke the underlying store as separate queries. This forbid us from implementing query optimizations based on a group of keys, which would be the common motivation of using bulk operations.
We should add bulk get to the state store interface and allow stores to implement possible optimizations when possible to reduce number of queries.

This sounds like a good idea and should be discussed before bulk get is added on the sdk sides.

This sounds like a good idea and should be discussed before bulk get is added on the sdk sides.

This doesn't affect the SDKs at all, nor does it affect the existing implementation of Bulk Get. the API stays the same for the user.
This talks about adding an optional method for Bulk Get for state stores that support it, and where it isn't supported, the implementation behaves like it does today.

@Haishi2016  I opened a issue here and now we are working on this PR
https://github.com/dapr/dapr/pull/2467

This was closed via #2368


Jupyter creates many junk empty ipynb files

Version: 1.74.2
Jupyter extension v2022.11.1003412109
MacOS Monterrey on Silicon M1
Anaconda
Whenever I use a Jupyter notebook, my folder gets full with lots of copies of the .ipynb file:
file_name_-2d3962b2-8d56-4e4e-9f46-1faff6d46747a9a34c13-38ce-404b-98a6-2cca61d0efb7.ipynb
file_name_-9dd5fbb0-91f6-4712-8137-084b9fee3f29e11fefa3-fef1-4539-9db7-b9e081ec6135.ipynb
file_name_-3312e1ad-9806-4b64-a79e-54b8c6b42d7b321c97ba-8007-459a-bf1c-72579b6b959f.ipynb
file_name_-5812df30-0798-42a8-b379-f2915a6df6caaa1f8f5c-c625-4006-97df-4c48f424d7df.ipynb
file_name_-c90cefa3-b3cd-4c96-879f-9406193f71a0d432c967-237f-4bd1-96dc-4b49d8c32de6.ipynb
file_name_-cd41d871-56a7-4201-b775-1214b13b3400f29ec548-91f0-4e73-b8f7-4a42e26c7fe2.ipynb
This becomes very annoying because it is hard to find the right files in the middle of so much garbage. When I close the note, these junk files don't go away.
JM

Some more information that might be relevant. I have two Macs. One with an M1 chip, the other with Intel. I just noticed the problem only occurs with VC Version: 1.74.2  Darwin arm64 21.6.0. I don't see those kinds of files being created with Version: 1.74.2 (Universal) OS: Darwin x64 21.6.0.

Duplicate of https://github.com/microsoft/vscode-jupyter/issues/6510


Support for sentinel values in cloud_firestore

https://firebase.google.com/docs/reference/android/com/google/firebase/firestore/FieldValue

@collinjackson
This issue has been moved to https://github.com/FirebaseExtended/flutterfire/issues/854. Any further collaboration will be done there.


[Date format and exposure error] bug report

Hello Everyone,
I would like to submit a bug report concerning date format and erroneous exposure in Strat runners.
Please check the joined picture.
PS : Data spanning 3 days.

This is fixed in the latest develop! I'll push out a new release asap.


Named exports

Hey there!
Since the project is in TypeScript, and named exports are more idiomatic in that world, is there any possibility to get the components to be exported this way? I know Inertia pages still likely need to be default exports, but everything else could theoretically be named.
I'm happy to open a PR for this since I've converted everything in my own project. I'd love to never have to do that again if possible 😅
Thanks!

hey thanks for raising this - i prefer default exports for the sake of consistency and knowing what the "main" entity is in a file, and since there are no concrete advantages to named vs default exports i'm going to leave it as is
this repo is set up in a way that you can fork it and easily make any modifications you want to support your own desires/needs though, see the "building locally" section of the readme to set this up for yourself :)
https://github.com/ozziexsh/laravel-jetstream-react#building-locally


.net 7 benchmark

they have improvements in .net 7 can u re-run benchmarks and show results on the websites with .net 7?

You can see the results for .NET 7 and .NET 6 here: https://github.com/gabrielgt/CSharpWasmBenchmark/tree/dotnet7/SavedData

Hi,
Thanks a lot for the contribution! I will check and merge them here soon.

Done.

Thanks!!


Bug fix for empty aws_environment_variables setting wiping remote Lambda env vars on update

Issue: https://github.com/Miserlou/Zappa/issues/1010

Coverage decreased (-22.2%) to 51.247% when pulling ac2ba7e81f10d5c81886e55fea445fa2f2210576 on nikbora:master into 43de8d71ee4f422009fa9b14bc04b389b5669a5b on Miserlou:master.

Coverage remained the same at 73.469% when pulling 0aa3845e249e3506a8aa7ef50a346d938703c7ea on nikbora:master into 43de8d71ee4f422009fa9b14bc04b389b5669a5b on Miserlou:master.


[audit] new provider attributes requirements: better identity (org, email, website correctness required)

We need to recommend new standards with provider identity with support email and website correctness as requirements for us to sign.
Identity is a key property for tenants to trust a provider.
https://akash.network/docs/providers/akash-audites-atributes/

List of current provider attributes for the providers that have been audited by akash1365yvmc4s7awdyj3n2sav7xfx76adc6dnmlx63
It appears that some providers removed their host / tier / organization attributes despite they were previously audited (i.e. signed).

[x] agreed on the new requirements
[x] updated the "Attributes of Community Providers" section https://github.com/akash-network/website/pull/78
[x] updated the provider audit template https://github.com/akash-network/support/pull/202
[ ] inform providers to update their organization attribute and email, webiste info fields in their provider.yaml and apply it to push the changes on chain

announced https://discord.com/channels/747885925232672829/1111749248527114322/1222199208946302987

Updated table on 20 April 2024 18:00 UTC
https://gist.github.com/andy108369/a7a84f75c63032573d9fdbabcc5ad09d


Widget | Clock - date does not fit when XS size

Description
If clock is set on only one column and we choose to show also date on it, date may not all fit into the widget. We agreed to fix it on XS size. It may not work the same on XXS but we treat this as author responsibility in that case.

Tested & accepted


chore(ci): setup action

:tada: This PR is included in version 1.2.8 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Registering team[JustCodeIt]

Application for Registering Team to CODE CAMP 1.0
This pull request template helps you complete an application to the CODE CAMP 1.0 HACKATHON. Use the checklist below to verify that you have followed the instructions correctly.
(Put x inside [] like [x])
Select the type of Pull Request

[x] Registration Pull request.

[] Submission Pull request.

Checklist ✅

[x] I have read the instructions on the README file before submitting my application and gone through CODE_OF_CONDUCT.
[x] I have Submitted my team's details by making a folder of my team as instructed in How to send Pull Request page.
[x] I have used the Markdown file template to add my information for the Hackathon.
[x] I have given all the necessary details as mentioned in template index.md file and the details are correct and best to my knowledge.
[x] I understand that a reviewer will merge my pull request after examining it or ask for changes in case needed.
[x] I understand I should not tag or add a reviewer to this Pull Request.
[x] I understand the Details added to the template will be used as a means of communication at the time of result declaration.
[x] I have added the event to my calendar.

@iamanantshukla , please fill the check list ASAP

@iamanantshukla , please do the ASAP

@iamanantshukla , please mention  correct theme, and join the team

else not be able to merge your PR

@iamanantshukla , theme is wrong, do not put app name ,, put theme name like atma nirbhar bharat and from which our app belongs

@iamanantshukla , theme is wrong, do not put app name ,, put theme name like atma nirbhar bharat and from which our app belongs

Sir is it ok now?

@iamanantshukla , please join the group and text [we are team team_name, we are in]
Thanks and join team and follow instructions.


platform.toLowerCase is not a function

When I inject Auth in constructor. Generate this error:

I have the same issue:
Install the Device plugin: 'ionic plugin add cordova-plugin-device'
Zt @ ionic.cloud.min.js:1
n @ ionic.cloud.min.js:1
get @ ionic.cloud.min.js:1
e.markActive @ ionic.cloud.min.js:11
e.checkActivity @ ionic.cloud.min.js:11
(anonymous) @ ionic.cloud.min.js:11
ionic.cloud.min.js:11 Uncaught TypeError: e.toLowerCase is not a function
    at e.normalizeDevicePlatform (ionic.cloud.min.js:11)
    at e.markActive (ionic.cloud.min.js:11)
    at e.checkActivity (ionic.cloud.min.js:11)
    at ionic.cloud.min.js:11

Ionic 1.3.2, seems it is on web view only?

Just commenting that if anyone has a workaround, a temp hack, I'd definitely appreciate it.

Looks like a bug on our end. Publishing a fix right now. Should be out in a couple minutes.

Ok if you update to 0.9.1 for @ionic/cloud-angular or 0.15.1 for @ionic/cloud this should be resolved.


potential licence issue for class jodd/util/BCrypt.java

Hi,
Is the licence header for file jodd/util/BCrypt.java correct?
It seems that jodd is using this file as copy from http://www.mindrot.org/projects/jBCrypt and therefore the licence header from here should be used.
Bye,
Sascha

That is totally true! Btw, am I allowed to use that java code in jodd? I have a need for it for certain user, and since the original one was not published on maven I just copied.
Note to myself:

[ ] check bcrypt
[ ] check asm5 code headers as well.
[ ] make sure that automatic license updater in IntelliJ does not overwrite these.

Btw, am I allowed to use that java code in jodd?

You can use that code in jodd if the file has its original licence header - in my humble opinion.

issue seems to be similar to #311.

Yes will do that. And need to add the acknowledgemnt page.

make sure that automatic license updater in IntelliJ does not overwrite these.

Maybe the gradle plugin License Gradle Plugin can handle this...


resolves #190 dash border where literal/listing block is broken across pages

cc: @rlopez133 @robertpanzer


README.md files: document compatibility with Fido release branches

The "fido" branch of meta-intel-iot-security was only tested with the
"fido" branches of the layers it depends on. Compatibility with other
versions of these layers is either untested or known to not work
(security-smack's libpam patch does not apply to libpam in OE-core
master).
Signed-off-by: Patrick Ohly<EMAIL_ADDRESS>

Wrong target, this needs to go into the "fido" branch. "hub pull-request" did not recognize that automatically.


ESPlorer Problems

When I go to the ESPlorer link, and click the download button, it 1; Takes a long time to download the file. 2; When I open the folder, an error pops up, saying that the file is invalid.
Can anyone help?
Thanks, Samuel M

Hi Samuel
I just downloaded ESPlorer and it looks fine. Have you used this link, which is a bit hidden between the advertisment? http://esp8266.ru/esplorer-latest/?f=ESPlorer.zip
Then you'll have to unpack the zip file. The content is a JAR file, which is JAR executable. On a windows system you might run ESPlorer.bat
On a MAC or oder Unix-like system open the command line and type java -jar ESPlorer.jar from the folder you unzipped.
If that doesn't work, it would be helpful to get more information:

your operating system
what happens when you run "java -version" from the command line
screenshot of the error message

I got this worked out! Thanks!


CORE-12912 ResultSet.next API changes

Usage of the API would look like
val resultSet = query.execute()
results += resultSet.results
while (resultSet.hasNext()) {
  results += resultSet.next()
}
return results

Runtime - https://github.com/corda/corda-runtime-os/pull/3729

Was discussing with @owenstanford. I could change next to shift the page along without returning anything and only accessing results using getResults, which would look like:
val resultSet = query.execute()
while (resultSet.hasNext()) {
  results += resultSet.results()
  resultSet.next()
}
return results

This would move it away from looking like an Iterator but might be conceptually easier to understand? This code can actually still be achieved with my current implementation if you decide to never use the results returned by next.


Added a storage to track owners and their shares

Added a new storage
Tokens<T: Config> = StorageMap<		_, 		Blake2_128Concat, 		T::AccountId,		 		Owners<T>, 		OptionQuery, 	>;
it uses the virtual account to retrieve the struct Owners.
this struct contains the following fields:
pub struct Owners<T:Config> {		 		pub owners: Vec<(T::AccountId,<T as Assets::Config>::Balance)>, 		///Creation Blocknumber 		pub created: BlockNumberOf<T>, 		///TokenId 		pub token_id: <T as pallet::Config>::AssetId, 		///Total supply of tokens 		pub supply: <T as Assets::Config>::Balance 	}
All related functions and tests have been updated.

Codecov Report

Merging #183 (8d24554) into main (4a98e40) will increase coverage by 0.15%.
The diff coverage is 97.14%.

@@            Coverage Diff             @@
##             main     #183      +/-   ##
==========================================
+ Coverage   78.12%   78.27%   +0.15%
==========================================
  Files          49       49
  Lines        4388     4419      +31
==========================================
+ Hits         3428     3459      +31
  Misses        960      960

Impacted Files
Coverage Δ

pallets/share_distributor/src/lib.rs
91.66% <75.00%> (+0.75%)
:arrow_up:

pallets/share_distributor/src/functions.rs
91.01% <100.00%> (+1.26%)
:arrow_up:

pallets/share_distributor/src/tests.rs
100.00% <100.00%> (ø)

pallets/share_distributor/src/types.rs
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Turn the beyond-ascii check into a warning for RFC mode

(See discussion in auth48archive and others.)

So far this will make it so that non-ascii utf-8 can appear in t without any warning being emitted. The warning/error changes would downshift the error to a warning for other places xml2rc was being strict about utf-8 for.
I'm not sure that's the intended result of the PR?
Unless we have some other tool to let the rfc-editor know they've got utf-8 to look at for reasonableness in the chain, having it pass it quietly seems a step too far.

The change only kicks in when the RFC has a number.  Up to then, xml2rfc works like before.

and sometimes big swaths of text get added after the RFC has a number.

Yes, and having a tool that gives the RFC editor a histogram of character usage is probably quite useful.  SMOP.

require 'unicode/name'
hist = Hash.new(0)
ARGF.read.each_char do |c|
  hist[c] += 1 unless c.ord < 128
end
cl = "*** Latin"
hist.keys.sort.partition {|c| c =~ /\A\p{Latin}\z/}.each do |l|
  puts cl
  l.each  do |c|
    puts "#{c}: #{"%4d" % hist[c]} #{Unicode::Name.correct(c)}"
  end
  cl = "*** Non-Latin"
end

$ unicode-histo rfc9277.xml
*** Latin
ß:    1 LATIN SMALL LETTER SHARP S
ä:    2 LATIN SMALL LETTER A WITH DIAERESIS
ö:    2 LATIN SMALL LETTER O WITH DIAERESIS
*** Non-Latin
 :   52 NO-BREAK SPACE
≤:    2 LESS-THAN OR EQUAL TO

I need to think about this a bit more but 2 things come to mind:
a) slightly concerned that this isn't getting wider review in that this has been normal handling since the transition to v3 (so almost 3 years)
b) if we're making the switch to allow non-ascii everywhere, flagging if and where these characters appear would be helpful.  I want to talk to the team about this to see what is helpful for all, but my first thought is it would be helpful to have some of the surrounding text or line numbers so we know where the characters appear (maybe some instances are ok and some aren't).   We have a script we use now, but having something built into xml2rfc might be nice to have one less separate check to run.

@rjsparks, @cabo: I have commited a new change to allow bare Unicode in the <t> element.
This also introduces new flag --warn-bare-unicode when set, xml2rfc warns about bare Unicode in the <t> element.
By default, this is set to False.
Have a look at the following test results (in a different branch, I haven't merged the results to this commit yet): https://github.com/kesara/xml2rfc/commit/3998d8e1b142ca76d706b80ad6b7afe343fe8425#diff-c2d2944d758bb3948e7924d76edf0e05292cda738d52c51636723fbbd444cfa9
Are those test results acceptable?

Here is another example why this needs to be fixed:
https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-base/issues/274

The change only kicks in when the RFC has a number. Up to then, xml2rfc works like before.

That sounds counter-intuitive to me. If it's an error until AUTH48, how will it be used by draft authors?

The change only kicks in when the RFC has a number. Up to then, xml2rfc works like before.

That sounds counter-intuitive to me. If it's an error until AUTH48, how will it be used by draft authors?

My original idea was to minimize the appearance of a change: use the workaround until RFC editing stage, and use the RFC editor's authority to decide what actually should be done.
However, that approach is no longer part of the proposal here.

@cabo wrote:

$ unicode-histo rfc9277.xml
*** Latin
ß:    1 LATIN SMALL LETTER SHARP S
ä:    2 LATIN SMALL LETTER A WITH DIAERESIS
ö:    2 LATIN SMALL LETTER O WITH DIAERESIS
*** Non-Latin
 :   52 NO-BREAK SPACE
≤:    2 LESS-THAN OR EQUAL TO

I think separating Latin and non-Latin is a good first step, but for the RPC, some other statistics may also be helpful:

Counts per script (e.g. 4 HEBREW), not necessarily per character.
Instances of non-normalized or confusable characters (implementation of this might take some effort).
Instances of spaces (except for U+0020, the ASCII SPACE), marks,...

On 21. Dec 2022, at 21:17, Robert Sparks @.***> wrote:

@rjsparks commented on this pull request.
In xml2rfc/util/unicode.py:

@@ -34,6 +34,7 @@
'street',
'title',
'u',

't',

I agree with the goal of the request. But I don't think we can do that without re-engaging the RSAB for a revised interpretation, or get a doc from RSWG through the RSAB that is explicit.

I’m repeating myself here: This fixes a bug in xml2rfc.
There is no policy change.
(This is unfortunate, but we have to make these steps one after another.)
Whether support for implementing the actual policy is added to xml2rfc or to some linter tool (or some diagnostic aid like the unicode-histo sketch I put in above) is orthogonal to fixing this bug.
Grüße, Carsten

I’m repeating myself here: This fixes a bug in xml2rfc.

I don't disagree with you, but it's clear that the nascent RSWG/RSAB engine feels it has a role.  I misremembered the status of this PR during the RSAB meeting at 116 (claiming it was already merged), and there were several people who were very upset about it.
So, yes, where Martin points is the right place to go. But I think trying to go there without nods from that new engine will make landing it take longer.


Enable the scheduler by default

Description
This is to enable the scheduler by default.
It is necessary to release the next version of OpenWhisk Core.
Related issue and scope

[ ] I opened an issue to propose and discuss this change (#????)

My changes affect the following components

[ ] API
[ ] Controller
[ ] Message Bus (e.g., Kafka)
[ ] Loadbalancer
[x] Scheduler
[ ] Invoker
[ ] Intrinsic actions (e.g., sequences, conductors)
[ ] Data stores (e.g., CouchDB)
[ ] Tests
[ ] Deployment
[ ] CLI
[ ] General tooling
[ ] Documentation

Types of changes

[ ] Bug fix (generally a non-breaking change which closes an issue).
[ ] Enhancement or new feature (adds new functionality).
[x] Breaking change (a bug fix or enhancement which changes existing behavior).

Checklist:

[x] I signed an Apache CLA.
[x] I reviewed the style guides and followed the recommendations (Travis CI will check :).
[ ] I added tests to cover my changes.
[ ] My changes require further changes to the documentation.
[ ] I updated the documentation where necessary.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (e20ab17) 76.86% compared to head (0895105) 4.52%.

:exclamation: Current head 0895105 differs from pull request most recent head b0b222d. Consider uploading reports for the commit b0b222d to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #5463       +/-   ##
==========================================
- Coverage   76.86%   4.52%   -72.34%
==========================================
  Files         241     241
  Lines       14649   14649
  Branches      629     629
==========================================
- Hits        11260     663    -10597
- Misses       3389   13986    +10597

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

I realized that it is necessary to split scheduler tests into unit tests and system tests to run successfully.
Some tests in the scheduler tests workflow manipulate ETCD data and it interferes other tests.

Strangely, unit tests only failed int the github action runner.

Now only two workflows are remaining..

LGTM. I think if we're going to continue working on this scheduler, the next major needed architectural improvement is to distribute function traffic across schedulers. As it is right now since a queue to handle activations is assigned to a single scheduler, the max throughput of an action is limited to the max cpu / network throughput / kafka consumer reads of that scheduler node.

are there docs explaining how the scheduler works?

@dubee
You can refer to this document: https://cwiki.apache.org/confluence/display/OPENWHISK/New+architecture+proposal
It might be slightly outdated, but it explains most of the major things.

Thank you all for the reviews.
I will merge this at the end of this week. Please share any concerns, or comments at any time.
After merging this, I will look into the openwhisk-deploy-kube repo part.


Block explorer market proposal links to wrong chain for oracle

I am looking at the eigenLayer points proposal: https://explorer.vega.xyz/markets/fc37a1eedb6e57b86823e2fc42480a0b9236aea556c1d7df49be697a93f8f2a0
and

the View on Etherscan https://etherscan.io/address/0x302461E6dBF45e59acb3BE9a9c84C0a997779612 takes me to an address that doesn’t exist. I think since in the proposal we have
"sourceChainId": "42161"

it’s not actually Ethereum it’s Arbitrum since this is in network parameters:
{
      "network_id": "42161",
      "chain_id": "42161",
      "confirmations": 3,
      "name": "Arbitrum One",
      "block_interval": 50
    }

Aha - oracles/4126133c5a3777cfa7f03b9d1dd46db4644376873d5284b73e1f1b1baf963109 does the correct linking. The market details panel does not.


Clobber rtx binary if it already exists

I'd like to cache the downloaded tools using GitHub caching, but rtx ends up in the cache and as a result the gh download of the rtx binary fails. The error indicates setting --clobber to overwrite or --skip-existing to skip -- I think clobbering is probably the right move in the case it exists (which will, at least, always keep rtx up-to-date).
Happy to propose an alternative PR that instead checks for existence before attempting a download (which would also suit my needs).
Incidentally, the cache setup I'm using is:
      - name: rtx tools cache
        uses: actions/cache@v3
        with:
          path: /home/runner/.local/share/rtx
          key: rtx-${{ hashFiles('.tool-versions') }}

Yeah I don't really care if rtx caches, but I'd like to cache all the tool downloads.

Incidentally, I use some automation to do release builds of typescript actions, haven't carved it out to its own action yet but might be something that you'd find convenient: https://github.com/theoremlp/required-reviews/blob/main/.github/workflows/release.yml

thanks! if I have some time I'll try to improve that here


[1.10.2] Elevator screens don't show levels when greater than ~65 blocks from base elevator

I have a very tall tower that I've been using the elevator with. The elevator itself works fine, but the screens (despite the more distant levels having their own screen controller, which is successfully linking to them) will not display the floors when the screens are around 60-70 blocks or greater from the base elevator. As long as they're within that range, they will display the levels in the button module, but beyond that, even screens connected to the same screen controller, they are just blank.
Verified all screens were working, and when switching which elevator was considered the root elevator, the screens in its vicinity worked.

Are you sure the screens are in the range of the screen controller? It has a limited range. You might need another screen controller higher up for those screens

Yeah, I have each group of elevator modules connected to their own screen controller, making 3 screen controllers in total, and then checked the controllers each to see how many they were connecting with. The screen controllers are connecting to the screens (6 for the top, 2 for the middle, and 1 for the bottom, making 9 screens total) but if I have the "root" elevator for the buttons up at the top, then only the top 7 will show the buttons. If I have the bottom as the root, only the lower 2 can. The  top 6 can't show anything.

Can you show a screenshot of that top screen with your mouse hovering over it?

No problem! Hopefully this is helpful :)
http://imgur.com/a/YfTgp
I created an album trying to demonstrate the issue, including the hovering tooltips. Unfortunately, the tooltips always seem to show the same thing regardless of whether or not they're connected. I included the block levels in the descriptions of the images as well, along with other info.

Well note the tooltips of the screen. It says '[NOT CONNECTED]' '[NO POWER]' Did you press 'scan' on the screen controller UI? The range of the screen controller is not that big (only -16/+16 in height)

Correct, I did, and I actually tried redoing the system several times. The screens always say [NOT CONNECTED] and [NO POWER] regardless of being connected and having power (you'll note that despite the tooltip displaying that, the screen is actually showing the floor names and levels, which it wouldn't do if it wasn't connected to the screen controller).
I had double-checked all of the screen controllers: the top controller after scanning was connected to 6 screens, and I detached and rescanned just to make sure, but the problem resumed. The middle screen connector is connected to 2 screens, and the bottom screen has its own dedicated connector, all of which are connected.
Again, the elevator itself works fine. The only issue is that the screens below those block levels won't display beyond a certain distance from the root elevator.

Very weird. Never seen this issue before and people are using my elevator + screens already...

Yeah, I'm not too surprised there. I doubt many people would run into this kind of situation. This is the first time I had tried using the elevator on such a large structure. Before I had been using it on a smaller one for just 6 screens on a different world and never had any issue, but I also only needed one screen controller for the whole set.
The bottom elevator is at level 79 and the top is at block level 198, so that's over 100 blocks distance. I'm building in an extreme hills biome and had put a fort on one of the taller mountains, hence the gargantuan distance.

Well the issue here is not really the elevator but the screens not functioning correctly. BTW, the screens that are not working don't have any other modules in them by chance?

Only the elevator modules, yeah: I had taken a stack of 9 elevator button modules and linked the entire stack to the root elevator as I had done before on the working elevators, then installed each of them in the screens (the elevator is the only thing they were being used for in this case).
Typically what I had done was "configure" one button, mine the screen, and then place the screen multiple times in creative to get a stack of identically configured elevator modules, but I also tried the vanilla way of just linking the stack and then configuring each one, but both ways gave the same result.

Also, I should have mentioned this prior - I'm on mcjtylib-1.10-1.9.3 and rftools-1.10-4.67

Hopefully this'll help:
I created a really simple test rig to replicate it: http://imgur.com/a/Bi7tc
I basically put out 7 elevators, powering the bottom elevator, with 10 blocks of red wool between each elevator level, and 1 screen controller between each two (except the 7th because that needed its own). The bottom 6 screens all showed all 7 levels, but the top 7th screen was blank as predicted. I didn't bother naming the levels or anything. I just linked the modules to the bottom elevator and stuck them in, then changed them to large buttons so they'd be easy to see against the red wool.

What other mods do you have? Also do you still have this problem with latest mcjtylib + rftools?

I've been having the same problem after making an elevator from my base down to my mine at level 11. The elevator for the three levels of my base worked fine, but as soon as I tried extending it all the way down to my mine, everything stopped working. I even tried destroying everything and rebuilding the elevator system from scratch with no luck (after your latest update).
Also, I do have an extra screen controller to include the level 11 screens. What is odd is that those screens are the only ones that work (but only displaying the mine level); the ones up near my base are the ones that are blank. Something else that is weird is that WAILA says that the working screens in the mine are not connected, not sure if this is a problem with WAILA or how it displayed back when the screens were working. Also, the screen controller in my base says it is connected to the screens, even though they no longer work. All screens I'm using right now have only the elevator module in them.
I'm using the FTB Unstable Pack with the latest versions of mcjtylib, rftools and dimentions mod that you released just a few hours ago.
Thanks for all your hard work. Your elevators are awesome, so I hope you don't have much trouble fixing this bug.

Sorry for the long delay! I had to go on some trips that kept me away from the computer for a while. I am still experiencing the same issue (I'm not on the absolute latest release, but unless you've made changes specific to this issue it's likely still present at the moment. I updated RFTools not long ago). The mods I have are:
(It'll be easier to link you the pack): http://minecraft.curseforge.com/projects/star-fall-craft/relations/dependencies

I finally could reproduce this and fixed it for next release


Use consistent symbol to refer to winit window

Currently the winit window is referred to via two symbols winit::window::Window and window::Window. Initially this made me think these were referring to two different things. I felt being explicit about the "winit" origin helps to highlight that this is about the conversion between the internal and the external theme mode types.

Thank you! Definitely an improvement.


Customize grub menu

This PR adds in the GRUB configuration context:

a extra_cmdline that can be specified as grub env config to specify additional booting kernel parameters (applied to all entries, extra_active_cmdline, extra_passive_cmdline and extra_recovery_cmdline for specific entrypoints)
a display_name var that can be specified to tweak the default booting menu entry (in place of the current sed logic)
a way to add additional config to the grub menu. If a file /grubmenu is found (e.g. in COS_STATE) it is sourced, and eventual menuentries declared inside are displayed in the boot menu
a way to customize the fallback logic

It still needs tests and docs to be updated too

@Itxaka needs still docs update, but I think I've figured why tests were failing, but should be good for a first review!

Docs PR at https://github.com/rancher-sandbox/cos-toolkit-docs/pull/55


Can't run search.py

First of all, thanks you very much for your generous to sharing code public.
My problem happen when I try to run search.py file and it returns error as an image in below. I don't know why how I get folder models in FastautoAugment folder.
Hope that you can answer question soon. Thank you very much!
P/s: I run your code in my google colaboratory.

U can try to create a folder model in the corresponding position.

@quyet0nguyen  I have the same problem as you ,could you tell me how you solved it?
Thanks

@ @zherlock030 @quyet0nguyen
Have you finished running this code in Google Colaboratory? If so, can you tell me what code needs to be modified?
After i changed  @ray.remote(num_gpus=4, max_calls=1) and ray.init(redis_address=args.redis) to @ray.remote(num_gpus=1, max_calls=1) and ray.init(),the running state of the code remains as shown in the image below.The code ran for two hours without making any progress.
Hope that you can answer question soon.Thank you very much!
P/s I use "!python3 FastAutoAugment/search.py -c confs/wresnet40x2_cifar.yaml" to run this code.


Gaps in swiperSlider on auto-play loop mode when given max-widths to swipers

Check that this is really a bug

[X] I confirm

Reproduction link
https://github.com/Kamasah-Dickson/Cinema_TypeScript
Bug description
on loop mode when I give max-widths to the swipers, ! encounter blank swipers  on page reload unless I click the next arrow keys  multiple times. I removed  max-widths on the swipers  everything  works fine but I never like the intrisic width of the swipers. It  seems  there is a bug in the calculation of the swiper width when given max-widths  therefore it leaves some gaps in the swiper especially at the end of a loop.

Expected Behavior
Swiper JS should be able to calculate the modified widths of swipers  to be able to determine the end of a loop to prevent gaps before another loop occur.

Below everything works fine when I don't modify the widths of swipers.

Actual Behavior
No response
Swiper version
v8.4.6
Platform/Target and Browser Versions
windows chrome/all browsers
Validations

[X] Follow our Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
[X] Make sure this is a Swiper issue and not a framework-specific issue

Would you like to open a PR for this bug?

[ ] I'm willing to open a PR

@nolimits4web Hello, I want to work and contribute on this issue, please assign me this issue. Thanks.

Swiper v9 comes with fully reworked and now different loop functionality. If you have similar issues in Swiper 9, open a new issue with a CodeSandbox showing the issue.


SSR: fetchOptions: { cache: "no-store" } does not work.

Hi Apollo Team, first of all, I want to thank you for this package; it's quite impressive.
Regarding your example for Server-Side Rendering (SSR):
function makeClient() {
  const httpLink = new HttpLink({
    // this needs to be an absolute url, as relative urls cannot be used in SSR
    uri: "https://example.com/api/graphql",
    // you can disable result caching here if you want to
    // (this does not work if you are rendering your page with `export const dynamic = "force-static"`)
    fetchOptions: { cache: "no-store" },
    // you can override the default `fetchOptions` on a per query basis
    // via the `context` property on the options passed as a second argument
    // to an Apollo Client data fetching hook, e.g.:
    // const { data } = useSuspenseQuery(MY_QUERY, { context: { fetchOptions: { cache: "force-cache" }}});
  });

I've been experimenting with fetchOptions and fetchPolicy in queries and can confirm that only fetchPolicy is effective, for example:
const { data } = useSuspenseQuery<{ retrieve: boolean }>(query, { fetchPolicy: 'no-cache' })

The fetchOptions: { cache: "no-store" } setting in the makeClient() function appears to have no effect. I find myself having to specify the fetchPolicy for each invocation of useSuspenseQuery.
Edit:
This is how the testing was conducted:
let currentState = false

const resolvers = {
    Query: {
        retrieve: () => {
            currentState = !currentState // Toggle the state
            return currentState
        }
    }
}

These are two different things:
fetchOptions has nothing to do with Apollo Client - it tells the fetch implementation of Next.js to not use the Next.js cache for this query, but instead really fire a query against a server.
fetchPolicy on the other hand is an Apollo Client option to tell your hook to not use the cache.

I'm doing some housekeeping so I'm closing some older issues that haven't seen activity in a while.
If this is still relevant, please feel free to reopen the issue.

Hi @hafaiedhmehdy! These are two different things:
fetchOptions has nothing to do with Apollo Client - it tells the fetch implementation of Next.js to not use the Next.js cache for this query, but instead really fire a query against a server when Apollo Client tries to make a request.
fetchPolicy on the other hand is an Apollo Client option to tell your hook to not use the cache (although, at least for the SSR run and the hydration run, you probably should, as otherwise data cannot be transported from SSR to the browser!).

Hi, time is flying!
Just to confirm, by default (without fetchPolicy: 'no-cache'), Apollo Client will always use the cached data from the initial build time, even if the server-side data has changed, right? Unless I either set fetchPolicy in each query or change the default behavior with defaultOptions in new ApolloClient (or use strategies like polling for periodic updates). 👀

Hey all 👋
This still seems like an ongoing issue.
Appreciate if you have any updates ?
Cheers!

Hey all 👋
This still seems like an ongoing issue.
Appreciate if you have any updates ?
Cheers!

What's your question exactly?

When enabling the no-store cache, the build process fails with the following error:
[ApolloError]: Dynamic server usage: no-store fetch http://localhost:8080/graphql /

@naimulemon that's a Next.js error that's just wrappen in an ApolloError - you would get the same error message if you did a normal fetch call. Unfortunately I'm not familiar with what it actually causes, but maybe the Next.js documentation can shed some more light?

Thanks for pointing that out!
The issue seems to be related to the dynamic nature of the Next.js page and how it interacts with Apollo's server-side data fetching.
With the error:

I was not using export const dynamic = "force-dynamic", which causes Next.js to attempt static rendering. Since Apollo's query needs dynamic data at runtime, it results in an error.

Without the error:

By adding export const dynamic = "force-dynamic", I ensure the page is always rendered on demand, which resolves the issue with Apollo queries fetching dynamic content.

However, as per the documentation, using force-dynamic in some scenarios might not be recommended, especially if it forces dynamic rendering where static behavior is preferred. I'll need to reconsider the strategy depending on performance trade-offs and content requirements.
If you have any suggestions or a better approach, I'd love to hear your thoughts!


Add Kubernetes meaning to English version of "What is Kubernetes"

This is a Feature Request
Well not really a feature, but neither a real bug.

What would you like to be added

I noticed that while the German "What is Kubernetes" page has a tiny section about the meaning of Kubernetes in it at the end, the English counterpart lacks this info. I want to add it. I have not checked with other languages.
Why is this needed
The documentation content should be equal across translations.
Comments

The English article explains the meaning of Kubernetes in the second paragraph ("The name Kubernetes originates from Greek, meaning helmsman or pilot. "), before explaining its origin.
Either the German version of the page should be adapted, or the English one. The English version does not explain where "K8s" comes from.

/language en
/kind feature

BTW SIG Docs convention is that localizations are downstream from the English version, which is canonical.

/triage accepted

In my humble opinion, the difference between the English and German versions of the documentation is a bigger problem and not limited to this case.
See as well German "Konzepte" vs English "Concepts".
I mean, my use case is kind of special, I am writing a thesis and want to cite the Documentation in some places. I first had the German links and then decided to write this thing in English, so I wanted to substitute the links with their English counterparts. This did not work as I expected, as parts of the docs moved to a different place.

@LaumiH we 100% welcome pull requests to bring the German localization in syncrhronization with English. If you have any friends itching to contribute to open source, and who speak both languages, or you're keen yourself - jump right in!

@sftim alright, I might have some spare time over the holidays. Seems like contributing to open source documentation is my thing :D
One questions remains: like in the initial case, the German version had more info than the English one. Shall I keep this info in a list and suggest adding it in the English version as well? Because somebody took an effort to add it in there in the first place, though they did not think about adding it to the canonical English version, too.

I haven't checked the commit history but I assume that the extra text was at some point in the English version and that the upstream (English) page has since changed. We don't accept changes that land first in the downstream localization if these revise the meaning of the text. It's possible the history is different - I'd expect that to be very rare.
Localization is not translation, though, and there are pages where the localized text differs from a literal translation because the overall intent and meaning is preserve from upstream.

Difficult matter I suppose, where do you draw the line ...
I will try to at least make the pages look more equal to one another, so that there are no surprises as in my case, where the page structure is somehow different and it is not so easy to link to the correct page in English, coming from German.

Seems this issue is now talking about updating the German page rather than the English page? @sftim should we update the label here to be German?
Either we change this to a German language updating issue, or close the issue, since the English version is canonical and it does contain the origin of the word Kubernetes:

The name Kubernetes originates from Greek, meaning helmsman or pilot. Google open-sourced the Kubernetes project in 2014. Kubernetes combines over 15 years of Google's experience running production workloads at scale with best-of-breed ideas and practices from the community.

/assign

@jai you might have misunderstood. We should not close this issue until https://kubernetes.io/docs/concepts/overview/what-is-kubernetes/ mentions “k8s”
/retitle Mention k8s abbreviation in “What is Kubernetes”.

Gotcha I'm on it


Add Implementation for Pylint E1132: Repeated Keyword

Summary
Adds the Pylint rule E1132 to check for repeated keyword arguments in a function call.
Test Plan
Tested via the included unit tests and manual spot checking.

Awesome, thanks for this PR and for getting involved!
There's some overlap here with https://github.com/astral-sh/ruff/pull/8450, I'm almost wondering if they should one rule since they both only deal with static dictionary spreads, but I think I need to take a closer look at the code before I have a clear answer to that.

Oh yeah! I totally did not see that other PR. I'm happy to help merge stuff if we go down that route.
I also should have mentioned this in the summary, but this is my first meaningful Rust code besides random side projects, so feel free to be extra nit-picky with your comments 😄

Okay, it's probably fine to just proceed with this rule on its own. Left a few comments!

@charliermarsh Okay this is ready for another pass. All of your comments should be addressed. I also updated some of my destructuring statements to use .. so that unused values weren't just destructured into _ variables. I think it made it easier to read, but happy to change it back if it's not the preferred style.


feat: support com_long_data

ref: https://github.com/cectc/dbpack/issues/
Ⅰ. Describe what this PR did
Ⅱ. Does this pull request fix one issue?
Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #160 (acf1ccf) into dev (7a213c2) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev     #160   +/-   ##
=======================================
  Coverage   42.29%   42.29%
=======================================
  Files          73       73
  Lines        8342     8342
=======================================
  Hits         3528     3528
  Misses       4483     4483
  Partials      331      331

Impacted Files
Coverage Δ

pkg/filter/dt/filter_http.go
16.34% <0.00%> (ø)

pkg/filter/dt/filter_mysql.go
1.51% <0.00%> (ø)

Continue to review full report at Codecov.

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

LGTM


Not really an issue - decimal places

Very good integration!
is there a simple way to limit the amount of decimal places?
for example my hashrate is 61.125465859008465 MH/s.
Sorry if dumb question

There should be a way with a template sensor but for now, not natively with the integration 😊

I modified sensor.py to round most of the rig values to 2 decimal places:

I modified sensor.py to round most of the rig values to 2 decimal places:

Hello.
This solution didn't work for me :s


Performance of rUDP vs ENet?

I've seen some negative sentiment and remarks about rUDP over the years, which has surprised me since it seems to be a solid performant option with a nice Plan 9 implementation model / example.  Have you tested it against ENet and, if so, what advantages / disadvantages have you seen or believe may exist?

@ylluminate This is a huge discussion and would be great to talk through but isn't a good fit for an issue tracker. I think open a thread on the forums. Thanks 🙏

@novabyte 	thanks so much for pointing me over there - posted this there and waiting for moderation. 👍🏻


Only 2D tensor for erosion?

First of all, thank you for putting in the effort to build a PyTorch library for morphological operations and that too with CUDA support. So, I was thinking of using the library for my research. But what I am seeing is that in the code of the master branch the comment says the erosion supports only 2D tensor. Is this the current situation?
By looking at the old commits, I understood is, the previous version had all the functions but it required a separate module morphology_cuda to use the CUDA functionality and you are trying to merge that into a single module. If so, may I help you with this? Actually, my work requires a modification to the dilation and erosion operations. I had earlier implemented them for TensorFlow, but now I need them in PyTorch and modifying your code should be easier.

I am very happy that this library is useful for you.
Let me sum up the current situation such that you have an overview:
I started by supporting all dimensions because I used PyTorch unfold to do that and it was very straightforward to do that for all dimensions, however, it is very memory consuming. This is why I thought that to split each dimension would be better.
In all the cases, I need to install a morphology_cuda module for GPU computation, but recently I also implemented the operations in C++, so there is also a morphology_cpp module to install.
Let me know which kind of morphological operation you need and then we can work together to develop it.

I think it is cool to implement new versions of these operations. I am checking the paper.
Regarding the code: I don't know if I explained it correctly. I want to have all operations implemented in C++/CUDA (C++ for CPU and CUDA for GPU). I want also to split the operations in modules, depending on the expected input/output (greyscale/binary). Also, if you want new type of operations we can put them in other modules.
With respect with the removed code, I think I did that a bit chaotically; a better approach would have been to create a new branch. We can try to do that to let a stable version with older implementations.
Finally, I think that we might meet such that we can coordinate better. My mail is<EMAIL_ADDRESS>(once you get it I will edit this answer to remove it).
Thank you again for the interest.


Defer git updates

We should defer git updates for a few days to allow binaries to have been published after the git tag was pushed.

renovatebot/renovate#12707
renovatebot/renovate#13463

https://launchpad.net/~git-core/+archive/ubuntu/ppa?field.series_filter=focal

Does this mean we should ideally have a different datasource for git?
And in the meantime would stabilityDays work?

yes, otherwise it looks like we have newer git than really installed :(

API:
> curl -s "https://api.launchpad.net/1.0/~git-core/+archive/ubuntu/ppa?ws.op=getPublishedBinaries&binary_name=git&distro_arch_series=https://api.launchpad.net/1.0/ubuntu/focal/amd64&exact_match=true" | jq

{
  "start": 0,
  "total_size": 20,
  "entries": [
    {
      "self_link": "https://api.launchpad.net/1.0/~git-core/+archive/ubuntu/ppa/+binarypub/165350179",
      "resource_type_link": "https://api.launchpad.net/1.0/#binary_package_publishing_history",
      "display_name": "git 1:2.33.1-0ppa1~ubuntu20.04.1 in focal amd64",
      "component_name": "main",
      "section_name": "vcs",
      "source_package_name": "git",
      "source_package_version": "1:2.33.1-0ppa1~ubuntu20.04.1",
      "distro_arch_series_link": "https://api.launchpad.net/1.0/ubuntu/focal/amd64",
      "phased_update_percentage": null,
      "date_published": "2021-10-13T05:29:17.542343+00:00",
      "scheduled_deletion_date": null,
      "status": "Published",
      "pocket": "Release",
      "creator_link": null,
      "date_created": "2021-10-13T05:22:33.273007+00:00",
      "date_superseded": null,
      "date_made_pending": null,
      "date_removed": null,
      "archive_link": "https://api.launchpad.net/1.0/~git-core/+archive/ubuntu/ppa",
      "copied_from_archive_link": "https://api.launchpad.net/1.0/~git-core/+archive/ubuntu/candidate",
      "removed_by_link": null,
      "removal_comment": null,
      "binary_package_name": "git",
      "binary_package_version": "1:2.33.1-0ppa1~ubuntu20.04.1",
      "build_link": "https://api.launchpad.net/1.0/~git-core/+archive/ubuntu/candidate/+build/22272443",
      "architecture_specific": true,
      "priority_name": "OPTIONAL",
      "http_etag": "\"d65771c5a02b94881e8c87ade665f58138a350e1-c1917320571695eae290166f27196ed376811122\""
    },
    {
      "self_link": "https://api.launchpad.net/1.0/~git-core/+archive/ubuntu/ppa/+binarypub/163366084",
      "resource_type_link": "https://api.launchpad.net/1.0/#binary_package_publishing_history",
      "display_name": "git 1:2.33.0-0ppa1~ubuntu20.04.1 in focal amd64",
      "component_name": "main",
      "section_name": "vcs",
      "source_package_name": "git",
      "source_package_version": "1:2.33.0-0ppa1~ubuntu20.04.1",
      "distro_arch_series_link": "https://api.launchpad.net/1.0/ubuntu/focal/amd64",
      "phased_update_percentage": null,
      "date_published": "2021-08-17T00:39:24.560445+00:00",
      "scheduled_deletion_date": "2021-10-14T05:29:35.867679+00:00",
      "status": "Superseded",
      "pocket": "Release",
      "creator_link": null,
      "date_created": "2021-08-17T00:37:55.994101+00:00",
      "date_superseded": "2021-10-13T05:29:35.867679+00:00",
      "date_made_pending": "2021-10-13T05:29:35.867679+00:00",
      "date_removed": "2021-10-14T06:29:10.210658+00:00",
      "archive_link": "https://api.launchpad.net/1.0/~git-core/+archive/ubuntu/ppa",
      "copied_from_archive_link": "https://api.launchpad.net/1.0/~git-core/+archive/ubuntu/candidate",
      "removed_by_link": null,
      "removal_comment": null,
      "binary_package_name": "git",
      "binary_package_version": "1:2.33.0-0ppa1~ubuntu20.04.1",
      "build_link": "https://api.launchpad.net/1.0/~git-core/+archive/ubuntu/candidate/+build/21986727",
      "architecture_specific": true,
      "priority_name": "OPTIONAL",
      "http_etag": "\"1af2467f150f500efcc3c3642468acaafd986d4a-e90867e793b4e88928e80b34e3b0f9090c512c00\""
    },
    ...
  ]
}

https://launchpad.net/+apidoc
https://help.launchpad.net/API/

paging seems to be 75 by default
{
  "total_size": 277,
  "start": 0,
  "next_collection_link": "https://api.launchpad.net/1.0/%7Egit-core/+archive/ubuntu/ppa?binary_name=git&distro_arch_series=https%3A%2F%2Fapi.launchpad.net%2F1.0%2Fubuntu%2Ffocal%2Famd64&ws.op=getPublishedBinaries&ws.size=75&memo=75&ws.start=75",
  "entries": [
    ...
  ]
}

it seems we should defer for ~3d, as launchpad rerelease was yesterday, so three days later

we also nered to override scope to fix 😕

https://github.com/containerbase/buildpack/pull/187

maybe we should pre-build git ourselves.
https://github.com/niko-dunixi/git-openssl-shellscript


When recreateConfigMapWatch fails, we should deal with it

Type of change

Bugfix
Enhancement / new feature
Refactoring

Description
When the Config Map watch is closed we try to recreate it. But when the recreation for whatever reason fails, we will just record error and continue running without the watch. That obviously isn't right. We should either try to recreate it again later or just exit and let Kubernetes handle it. This PR closes Vert.x which causes the cluster controller to exit.

@tombentley We do stop the watcher ... in stop(Future<Void> stop). But the recreateConfigMapWatch has a check for stopping and doesn't do anything if we are stopping. And in all other cases we probably want to recreate the watch regardless of the the reason.
The only think I could see as something we could do better would be to check the stopping already in the onClose.

@tombentley I removed the stopping completely and I'm now calling the recreateConfigWatch onyl when onClose is called with an error. Better?

I think you can remove the stopping field declaration too now, no?
Any thoughts about how we can test this?

Sorry, stopping declaration now removed.
As for the test, I haven't found a way how to trigger the Watch closure even manually. To test it I have triggered it from modified Cluster Controller source. It would be good if we could test that the CC exists when the Watch fails to recreate, but I would suggest to leave it be for the time being.


Always Set MAC address to SRIOV VF

Expected Behavior
Alway set MAC address to SRIOV VF.
Actual Behavior
Kubeovn cni plugin set MAC address to SRIOV VF only if the vf goes with a VfioPciDriver, that will not work with virtualization based runtime such as Kata. If we do not set MAC address to VF directly in the host machine, the network driver(e.g. mlx5_core) in the guest os will set a random mac to the vf passed in if the vf mac address is 00:00:00:00:00:00 on the host, or it'll keep the mac address set before by other program. Then the final mac address of the vf on the guest os will not be the same one allocated by kube-ovn.
Steps to Reproduce the Problem

Setup K8s with Kata container as runtime.
Build from main branch  and Install kube-ovn with HW_OFFLOAD on.
Follow the instruction in https://github.com/openshift/ovn-kubernetes/blob/master/docs/ovs_offload.md
Create a Kata container pod with sriov dev.

apiVersion: v1
kind: Pod
metadata:
  name: ovs-offload-pod1
  annotations:
    v1.multus-cni.io/default-network: default
spec:
  runtimeClassName: kata
  containers:
  - name: appcntr1
    image: centos/tools
    resources:
      requests:
        mellanox.com/cx5_sriov_switchdev: '1'
      limits:
        mellanox.com/cx5_sriov_switchdev: '1'

the pod will not start, if we do a describe: kubectl describe pod ovs-offload-pod1, we can found something like

...
update interface: Link not found (Address: 00:00:00:f5:eb:63)
...

I can confirm the mac address in the guest os is not the one set by kube-ovn and the vf mac address kept unchanged on the host.
Additional Info
The code related sits here:
https://github.com/kubeovn/kube-ovn/blob/master/pkg/daemon/ovs_linux.go#L814
	if isVfioPciDriver {
		// 7. set MAC address to VF
		if err := setVfMac(deviceID, vfIndex, mac); err != nil {
			return "", "", err
		}
	}

The vf driver is mlx5_core, not a VfioPciDriver. VF mac was set after we remove if isVfioPciDriver and rebuild it.

Kubernetes version:
Output of kubectl version:
(paste your output here)

kube-ovn version:
(paste your output here)

operation-system/kernel version:
Output of awk -F '=' '/PRETTY_NAME/ { print $2 }' /etc/os-release:
Output of uname -r:
(paste your output here)

@fanriming can we always set vf mac here?

I don't remember why MAC address is not set for the VF with mlx5_core driver, but it looks like it should always be set, I don't have an environment to verify it for a while, can you verify this solution and submit a PR?

@xiaosuiba can you make a pr to fix it


Steam Import fails if user doesn't have a vanity URL set

vicious and rustedtime both ran into this issue because they don't have a Steam vanity URL.
You can see if you have a vanity URL by using the SteamDB Calculator: https://steamdb.info/calculator/76561198040727226/?cc=us
You can also add a Vanity URL at http://steamcommunity.com/my/edit/ by setting the Custom ID field.

Fixed by adding a notice and explanation to the Steam Import page.


[PyTorch] FP8 AllToAll

Description
Add a FP8AllToAll layer, which conducts cast_to_fp8 -> all_to_all in fp8 -> cast_from_fp8.
We're getting about 5% end to end performance gain in Mixtral 8x7B and 8x22B training with the parallelism configs where alltoall happens on inter-node connections such as IB/RoCE.
Type of change

[ ] Documentation change (change only to the documentation, either a fix or a new content)
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Changes
Please list the changes introduced in this PR:

Add a FP8AllToAll layer

Checklist:

[x] I have read and followed the contributing guidelines
[x] The functionality is complete
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

The implementation looks reasonable, although this functionality seems somewhat Mixtral-specific. Perhaps it would be better to have this class live inside NeMo?

This implementation is used to improve the performance of AllToAllTokenDispatcher in MCore, which is not only used in Mixtral but also other MoE models, such as GPT-MoE, DBRX, Grok and so on.
But you suggestion is reasonable. It should be fine to live in MCore. I will discuss with other folks in MoE development.


Support environment variable serialization for data source options

Why make this change?

Closes #1956
Data source section was not supporting env transformation.

What is this change?

Added a DataSourceConverterFactory which will properly deserialize the data-source section considering the _replaceEnvVariable to decide weather to transform or not.

How was this tested?


Cyrillic font is missing

Cyrillic font is missing.
There should be "K".

Hey,
please test something for me:
go to "UnitFrame.lua" line 2810, and insert the following code:
 if GetLocale() == "ruRU" then newFont = "Fonts\\FRIZQT___CYR.TTF" end

so it will look like that:
function Module.ChangeFonts()
    local newFont = 'Fonts\\FRIZQT__.ttf'

    if GetLocale() == "ruRU" then newFont = "Fonts\\FRIZQT___CYR.TTF" end

    local changeFont = function(f, newsize)
        local path, size, flags = f:GetFont()
        f:SetFont(newFont, newsize, flags)
    end

    local std = 11

    changeFont(PlayerFrameHealthBarText, std)
... ... ...

end

Maybe this will fix it. The "K" etc comes from a blizzard function to breakup large numbers; if this doesn't work, I would need to dig deeper.

Yes! This line fixes up the problem!
Thank you for the fix!

Nice, and thanks for reporting!
Will be in the next version as fix.


Devtools (React) "Filter" field, when used, makes "Sort" dropdown, "Asc / Desc" and "offline" buttons disappear

Describe the bug
The "Filter" field of Devtools makes the other fields (Sort, asc/desc, offline) disappear when used.
Even though the are used to sort the filtered results, one can only change the sorting and the rest of the options when the "filter" field is cleared.
Your minimal, reproducible example
Attached video below
Steps to reproduce

Open Tanstack (React) Query Devtools
Add a filter on the "filter" field
The rest of the fields disappear

Expected behavior
As a user, I expect the fields to not disappear when populating some of them with data.
How often does this bug happen?
Every time
Screenshots or Videos
https://user-images.githubusercontent.com/2103443/219364287-b6d127ee-8793-4261-a4cb-71ec48957281.mov
Platform
Mac OS, Chrome 110
TanStack Query version
v4.24.4
TypeScript version
v4.9.5
Additional context
No response

looking at the code, we do have a condition to only render the rest when there is no filter. But that seems weird to me. Maybe sorting wasn't needed when something was filtered, but I'd rather keep the ui the same all the time.
would you like to contribute a fix ?

@TkDodo I'd be happy to contribute a fix!


Remove deprecated ocio_config ImageIOConfigModel settings for each addon

Is there an existing issue for this?

[X] I have searched the existing issues.

Please describe the feature you have in mind and explain what the current shortcomings are?
Currently the settings for ayon-houdini contains a deprecated ImageIOConfigModel.
With the support of profiles to determine OCIO config in ayon-core this logic has been superseded and should be removed from each addon still having the deprecated settings.
How would you imagine the implementation of the feature?
Remove the deprecated settings, and ensure transition for existing users is easy.
Since settings have moved, in a potentially backwards incompatible way, there may need to be a transition guide with the release explaining what to do. We may need to also bump the minor version to indicate the breaking changes.
Are there any labels you wish to add?

[X] I have added the relevant labels to the enhancement request.

Describe alternatives you've considered:
No response
Additional context:

Part of the cleanup epic ✨

[ ] https://github.com/ynput/ayon-maya/pull/28
[ ] https://github.com/ynput/ayon-houdini/pull/47
[ ] https://github.com/ynput/ayon-blender/pull/11
[x] https://github.com/ynput/ayon-resolve/pull/10
[ ] https://github.com/ynput/ayon-fusion/pull/6
[ ] https://github.com/ynput/ayon-substance-painter/pull/3
[ ] Harmony
[ ] CelAction
[ ] AfterEffects
[ ] Nuke
[ ] Hiero
[ ] Flame
[ ] TVPaint
[ ] Photoshop
[ ] 3DsMax
[ ] Tray Publisher
[ ] OpenRV

Oops - can we link multiple PRs but have this only close if ALL of them are merged? If not, I may need to unlink them and just keep them in the PR description. @dee-ynput do you know?

AFAIK closing one will always close the issue :'(
Mentioning them in the issue body is better in this case (and probably most cases)
I hope GH will change that someday  ✨

@dee-ynput all the listed integrations are now merged - I'll close this one.