Objects extended with AllOf are generated wrong

Take for example this model
        "PartialCompany": {
            "type": "object",
            "allOf": [
                {
                    "$ref": "#/definitions/Company"
                }
            ],
            "properties": {
                "partner": {
                    "type": "object",
                    "properties": {
                        "id": {
                            "type": "integer"
                        }
                    }
                }
            },
            "description": "A representation of a company with optional partner"
        },
        "Company": {
            "type": "object",
            "required": [
                "name",
                "description",
            ],
            "properties": {
                "name": {
                    "type": "string"
                },
                "description": {
                    "type": "string"
                },
                "image": {
                    "type": "string"
                }
            },
            "description": "Base company"
        },

This generates a partial company that looks like this
<?php

namespace Fitbug\BackOfficeApiClient\Model;

class PartialCompany
{
    /**
     * @var Partner
     */
    protected $partner;
    /**
     * @return Partner
     */
    public function getPartner()
    {
        return $this->partner;
    }
    /**
     * @param Partner $`partner
     *
     * @return self
     */
    public function setPartner(Partner $partner = null)
    {
        $this->partner = $partner;
        return $this;
    }
}

Obviously this is missing the base models fields

name
description
image

Does the partial company schema should more look like this:
        "PartialCompany": {
            "type": "object",
            "allOf": [
                {
                    "$ref": "#/definitions/Company"
                }
                {
                    "type": "object",
                    "properties": {
                        "partner": {
                            "type": "object",
                            "properties": {
                                "id": {
                                    "type": "integer"
                                }
                            }
                        }
                    }
                }
            ],
            "description": "A representation of a company with optional partner"
        },

Or should both be valid ?

From what I can tell from the Spec, both are valid. Both validate when tested in the swagger schema validator.

This should be resolved now.


Add defensive loading of data from Airtable

This patch prevents build failure due to inconsistency in Airtable data.
The builds have been failing due to problems with opportunity owners:
Error occurred prerendering page "/opportunities/recxWt15iPiGXW6Va". Read more: https://nextjs.org/docs/messages/prerender-error
18:52:50.565  TypeError: Cannot read property 'profilePictureUrl' of undefined
18:52:50.565      at Page (/vercel/path0/.next/server/pages/opportunities/[slug].js:407:72)
18:52:50.565

And with project coordinators:
Error occurred prerendering page "/projects/jehlomat". Read more: https://nextjs.org/docs/messages/prerender-error
18:52:51.594  Error: Error serializing `.coordinators[3]` returned from `getStaticProps` in "/projects/[slug]".
18:52:51.594  Reason: `undefined` cannot be serialized as JSON. Please use `null` or omit this value.
18:52:51.594

We need to improve checking the data and also error reporting.


Merge pull request #7 from melpatjen16/capstone-project_Branch1

Capstone project branch1

Trying to get up to date


selectrows() doesn't work with AbstractDict

When class_w is passed to a machine during construction, it eventually throws an error on evaluation. (Holds true for any fit... function)
X, y = table(rand(100, 5)), coerce(rand([1,2,3], 100), Multiclass)
class_w = Dict(1=>1, 2=>2, 3=>3)
model  = @load DeterministicConstantClassifier
mach = machine(model, X, y, class_w)
evaluate!(mach, measure=multiclass_f1score)

On first pass, I believe its because selectrow() in data_utils.jl doesn't support AbstractDicts yet.
I can work on it, if it's to be added.

Ah yes, we have essentially been assuming all the args in fit(model, verbosity, args...) are objects to be subsampled, but in the class weights case this is not so.
One solution would be to have a fallback for selectrows that just returns the object unsampled. But this might mean objects not meant to be sampled, but which appear to be iterable (any table, matrix or vector) would get sampled. So such objects would need to be passed to fit in some wrapped form to force the selectrows fallback to kick in. Since I can't actually think of a single use-case (maybe https://github.com/alan-turing-institute/MLJ.jl/issues/480), this may not be so bad.
An alternative would be to pass objects not intended for sampling as keyword arguments (keyword arguments are currently forbidden). So, for example, if w is a per-sample weight, we do
fit(model, verbosity, X, y, w)

but for class weight class_w, we do
fit(model, verbosity, X, y; class_weight=class_w)

I think it would be complicated to adapt the machine interface and the composition interface to this change; I'm not enthusiastic about the prospect. The user would also need to use keywords in the machine constructor, and is would probably appear weird to users to have a keyword for class weights and no keyword for sample weights.
So my vote is for the first option.
Any other ideas?
Option 1 is a simple PR, so I'll make that now; but we can sit on that for a week or so.

Ah yes, we have essentially been assuming all the args in fit(model, verbosity, args...) are objects to be subsampled, but in the class weights case this is not so.
One solution would be to have a fallback for selectrows that just returns the object unsampled. But this might mean objects not meant to be sampled, but which appear to be iterable (any table, matrix or vector) would get sampled. So such objects would need to be passed to fit in some wrapped form to force the selectrows fallback to kick in. Since I can't actually think of a single use-case (maybe https://github.com/alan-turing-institute/MLJ.jl/issues/480), this may not be so bad.
An alternative would be to pass objects not intended for sampling as keyword arguments (keyword arguments are currently forbidden). So, for example, if w is a per-sample weight, we do
fit(model, verbosity, X, y, w)

but for class weight class_w, we do
fit(model, verbosity, X, y; class_weight=class_w)

I think it would be complicated to adapt the machine interface and the composition interface to this change; I'm not enthusiastic about the prospect. The user would also need to use keywords in the machine constructor, and is would probably appear weird to users to have a keyword for class weights and no keyword for sample weights.
So my vote is for the first option.
Any other ideas?
Option 1 is a simple PR, so I'll make that now; but we can sit on that for a week or so.

The new data front-end also provides the possibility of overriding any (most?) unexpected behaviour with option 1. So let's go for that.

The new data front-end also provides the possibility of overriding any (most?) unexpected behaviour with option 1. So let's go for that.


Rename file Dark-Telegram.styl to Dark-Telegram.user.styl

Dark-Telegram.styl should be renamed to Dark-Telegram.user.styl, so Stylus could recognize and be able to install it.

You're right changing now!
Thanks
I never used the styl file to install..

Although I think in this case it's a bit unnecessary but can you confirm the fix before closing the issue? thanks


webpack failed: Module parse failed: Unexpected token (1:918)

Webpack failed then importing setupPlugins

Seems like don't have webpack loader
I am using babel 6
module: {     rules: [       ...styles.loaders({useDevServer: true}),       {         test: /\.js?$/,         exclude: /(node_modules)/,         loaders: [           'babel-loader?presets[]=react,presets[]=es2015,presets[]=stage-0'         ]       },       {         test: /\.(jsx)?$/i,         loader: 'babel-loader',         options: {           presets: [             'react',             'stage-0',             'es2015',           ],           comments: false,           plugins: [             'react-hot-loader/babel',             'transform-flow-strip-types',             'transform-class-properties',             config.webpack.flowRuntimeEnabled ? ['flow-runtime', {               assert: false,               warn: false,               annotate: true,             }] : null,             'transform-decorators-legacy',           ].filter((plugin) => plugin != null),         },         exclude: [           /node_modules/,           /\.(spec|e2e)\.js$/,         ],       },     ],   },
.babelrc
{     "presets": [         "stage-0",         "react",         "es2015",         "flow"     ],     "env": {         "production": {             "presets": [                 "babili"             ]         }     },     "compact": true,     "plugins": [         "transform-flow-strip-types",         "transform-react-jsx",         "transform-object-rest-spread",         "git-version",         "transform-class-properties"     ] }
Environment
superset version: superset version 0.32.0rc2.dev2
python version: python --version 3.6.7
node.js version: node -v v8.16.0
npm version: npm -v 6.4.1

Why are you using babel 6? Could you try latest master?

Hello, I try started it locally, with my webpack config...Update to babel 7 do nothing for me...
{         test: /\.js?$/,         exclude: /(node_modules)/,         loaders: [           'babel-loader?presets[]=react,presets[]=es2015,presets[]=stage-0'         ]       },       {         test: /\.(jsx)?$/i,         loader: 'babel-loader',         options: {           presets: [             'react',             'stage-0',             'es2015',           ],           comments: false,           plugins: [             'react-hot-loader/babel',             'transform-flow-strip-types',             'transform-class-properties',             config.webpack.flowRuntimeEnabled ? ['flow-runtime', {               assert: false,               warn: false,               annotate: true,             }] : null,             'transform-decorators-legacy',           ].filter((plugin) => plugin != null),         },         exclude: [           /node_modules/,           /\.(spec|e2e)\.js$/,         ],       },

Ok. this issue is work for me:
https://github.com/webpack/webpack/issues/8656

I think your should update acorn

Same issue i am facing in superset-ui-plugins demo run. Please help me.  how to resolve


make touch/pen useable on command line “UI”

source: https://www.raspberrypi.org/forums/viewtopic.php?p=839857
It would be a better usability if the pen/touch displays could be used like a simple POS without an ssh connection or full keyboard.

That would one way to go, but maybe not the best time investment.
Because 1) i would like to change the LCD in the future to a ePaper HAT like this (no touch, but buttons) and 2) POS should ne done thru a connected mobile device (like smartphone) - much better and secure.

ok, not reasonable for the assumed usecase

Because this was asked again on twitter:
https://twitter.com/raumi75/status/1099066019899953152
Some more resources if someone likes to dig deeper here and activate touch ... here is the manual of the LCD: https://www.elegoo.com/tutorial/Elegoo 3.5 inch Touch Screen User Manual V1.00.2017.10.09.zip


H2 used in test profile

H2 is still used as a database kind for the test-profile. This is hardcoded in the DatabaseIntegrationTest.java. We should refactor this test, if even needed, to get rid of the H2 database and use PostgreSQL for all profiles.

Can the tests rely on Quarkus-specific annotations, or should they continue using manual Hibernate configuration?

@codespearhead See linked PR. Please provide your feedback.
I don't see the need for any specific Quarkus annotations in this case. This project aims to showcase Quarkus so if there are any Quarkus specific improvements to be made, please describe so we can discuss.


Add example VCF format for phase-reads to documentation

It would be really helpful in the documentation to include an example of how you expect the input VCF to be formatted and how that information is used in the program.

Good idea, this is long overdue.
Jared

On Nov 21, 2019, at 6:12 PM, Shian Su<EMAIL_ADDRESS>wrote:

It would be really helpful in the documentation to include an example of how you expect the input VCF to be formatted and how that information is used in the program.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

I have improved the --help message in 0b28ff0. Let me know if I missed any information that you're looking for.


Use RPATH instead of RUNPATH

Libraries shipped in conda-forge should specify the RPATH instead of RUNPATH. Addresses conda-forge/cuda-cudart-feedstock#21

@conda-forge-admin , please restart CI

Restarted the one failing job. Looks like it just got the old package before
Note that Travis CI's status in GH isn't updating, but the job is running


Support Summary V2

Closes  #4

Coverage increased (+0.01%) to 99.753% when pulling 9e8cc40cf203ae2b4037dfe415b4f28ea4828662 on f002 into 32b00f32f5c58119b5ef488ef2444740ad92cefc on master.


[FEAT] - Add Back-To-Top functionality

The details page is long and will only get longer. A back-to-top button is absolutely necessary.

Wrong repo - oops!


Provisional Gamepad Support

Hi @spite,
First off, fantastic work! I hope I'm not stepping on your toes, but I was considering adding an emulated HTC Vive controller in a fashion similar to your monkey-patching of navigator.getVRDisplays. Initially just something simple in terms of being able to position/orient it in space and depress buttons. Should I get something functional in a PR in order to discuss further?
Thanks,
lollerbus

Yes! It would work similarly, but for navigator.getGamepads() (and all the related methods, objects, events...)
To begin with, exposing two "controller-like" boxes that can get a pose like the hmd, and attach the TransformControls. Then it might make sense to refactor the code so it can be generalised for hmd, controllers ... and anything else that might come in the future.
Do you have any thoughts about how to handle buttons and touchpads?
Also, it might be interesting to not override all gamepads, in case a developer is also using a standard gamepad for whatever reason.


feat: added skeleton component

Checklist

[x] Fix linting errors
[x] Tests have been added / updated (or snapshots)

Change information

added component
added tests
added en docs

Closes #773

@unix thanks for your review and sorry that you had to wait for so long. I'll fix the issues in a bit

so can we merge this? its beautiful

@Geczy I think so
@unix is there something holding the merge back?

any eta for this merge guys?

when merge eta?


Updating alternative index value

I've got list with both a track by and and order by on it
<ul ui-sortable ng-model="products">
<li ng-repeat="product in products | orderBy: 'listIndex' track by product.listID" ng-controller="product">ID {{product.listIndex}}
</li>
</ul>

Then i've got a product controller that will update the server when the product is updated.  I need it to update also when I rearrange.
Previously I had this done just watching for the $index to change.  But with the track by and order by the index value never updates.
I've managed to add sortableOptions to the ui-sortable and get the product i'm dragging to update... but this doesn't work for all of the other ones.
$scope.sortableOptions = {
	stop: function(e, ui) {
		var originalIndex = ui.item.sortable.index;
		var newProdArray = ui.item.sortable.resort.$modelValue;

		newProdArray[originalIndex].listIndex = ui.item.index() + 1;
	},
	axis: 'y'
};

So how do I either get it to update $index or let me specify what to use as the index?

+1


chore(main): release veto 0.3.5

:robot: I have created a release beep boop
0.3.5 (2024-05-21)
Bug Fixes

veto: include zod types with --dts-resolve (684e9b6)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/fuf-stack/uniform/releases/tag/veto-v0.3.5 :sunflower:


Development display next launch

Description
This PR Handles Next Launch state which is true if the launch is available to our clients, false if we're working on it.
Next Launch should allow login page normally, user is blocked once she/he logs in.
Changes
- Server:

models: database.go, netxlaunch.go (model),
app: app.go, admin_handler.go, admin_handler_tests.go

- Client:

Login.vue
NextLaunch.vue
Default.vue
Home.vue
index.js
userservice.js

Related Issue
Issue link
Checklist

[x] Tests included
[x] Build pass
[ ] Documentation
[x] Code format and docstring

Remove package-lock.json file, we depend on yarn

Remove package-lock.json file, we depend on yarn

Done.
sorry, didn't realize It was created, my bad

For frontend, give it more testing because it is not working

Can we add the update feature in frontend? A button in admin page that allow to enable/disable next launch

okay will be working on it


After importing the @ nuxtjs/i18n module, the automatically imported function cannot find the type declaration in the template

Environment
nuxt v3.12.4
Reproduction
This issue occurred in the newly created nuxt3 project without any other configuration made
Describe the bug

When 'i18n' is not imported, there is no problem using the automatic import function of utilis in the Vue file, but after importing 'i18n', the type prompt becomes invalid.
Additional context
No response
Logs
No response

This should be resolved in the next release: https://github.com/nuxt/nuxt/pull/28466.


value_to_usize loses precision

On 32-bits architectures, usize is 32-bits, by definition, so any conversion from a larger type into this will drop some bits. On 64-bits architecture, converting from 128-bits to 64-bits will also lose bits. It seems that it's only used for key paths computations, so for instance on 64-bits, that would require a static access in a list at an index >= 2**64 to cause an issue, so it's rather unlikely to happen, but it's still a real bug.

Probably worth testing if we can change that function to only handle usize and not cast the type integer types, like it does now. So only return Some for Value::usize.
I wrote it like this originally because I was worried about integer literals defaulting to i32 would be an issue but I haven't actually tested that.

We could also just panic if a lossless conversion fails. Like you say hitting that requires accessing very large lists.


I'm not able to run server locally. It throws ACME error.

This is a command which I'm using and error when I'm trying open ordinals in http://localhost:8080
$ ord --cookie-file /Volumes/T7/Bitcoin_Core/.cookie server --https-port 8080
Listening on https://<IP_ADDRESS>:8080
[2023-03-23T20:46:05Z ERROR ord::subcommand::server] ACME error: Order(Acme(HttpRequest(Non2xxStatus { status_code: 400, body: "{\n  \"type\": \"urn:ietf:params:acme:error:rejectedIdentifier\",\n  \"detail\": \"Error creating new order :: Cannot issue for \\\"my-macbook.local\\\": Domain name does not end with a valid public suffix (TLD)\",\n  \"status\": 400\n}" })))

ehh ... I set https instead of http


how to Assign a resolver function to a field.

hi @HigoRibeiro @angelomsq ; i'm trying to assign a resolver function to a field as lighthouse on Laravel  did:
type Query {
  jobs: [Job!]! @field(resolver: "App\\Http\\GraphQL\\Query@jobs")
}

how can i do it ?
(im not sure about the right question ,whenever im trying to get a relation between the authors and them books
# Schema.grahpql
type Query {
  book(id:ID!): [Book]
  author(id:ID!): [Author]

  books: [Book]
  authors: [Author]
}

type Book{
  id:ID
  title:String
  author:[Author]
  address:String
}
type Author{
  id:ID
  name:String
  age:Int
  books:[Book]
}

// SchemaController.js
var books=[
  {id:1,auth_id:1,title:'Lead Group Developer'},
  {id:2,auth_id:1,title:'Legacy Optimization Administrator'},
  {id:3,auth_id:2,title:'Human Directives Engineer'},
  {id:4,auth_id:4,title:'Global Intranet Director'},
  {id:5,auth_id:3,title:'Internal Operations Analyst'},
  {id:6,auth_id:5,title:'Internal Factors Architect'},
  {id:7,auth_id:5,title:'Customer Program Agent'},
  {id:8,auth_id:4,title:'Direct Program Associate'},
  {id:9,auth_id:3,title:'Future Directives Planner'},
  {id:10,auth_id:6,title:'Customer Functionality Engineer'},
  {id:11,auth_id:1,title:'Global Creative Producer'},
]
var authors=[
  {id:1,name:'Stella Moreno',age:23,address:'232 Itipa River'},
  {id:2,name:'Christina Parks',age:86,address:'1719 Nijan Turnpike'},
  {id:3,name:'Antonio Edwards',age:50,address:'1768 Bekep Glen'},
  {id:4,name:'Rosa Bailey',age:30,address:'167 Cagwe Park'},
  {id:5,name:'Ollie Lewis',age:88,address:'1205 Nidoh Boulevard'},
  {id:6,name:'Sam Ford',age:64,address:'900 Akhih Terrace'},
]
class SchemaController {
  async books() {
    return books
  }
  async authors() {
    return authors
  }
  async book(parent, arg) {
    return books.filter(b=>b.id==arg.id)
  }
  async author(parent, arg) {
    return authors.filter(a=>a.id==arg.id)
  }
/**
  * im trying to make the BookType to resolve this function when i query for the book author
  * coz it's return null
  * @example
  * ```query
  * {
  *   book(id:1){
  *      title # work
  *      author{  # return null coz cant attach the Book author field to a resolver which
  *               # filter the authors by the parent `id` @ `auth_id` on the authors array
  *         name
  *         id
  *       }
  *   }
  *```
  */
  // async authorBook(parent, arg, ctx) {
  //   return books.filter(a=>a.id==parent.auth_id)
  // }
}

module.exports = SchemaController

this an example using apollo have same ida which im trying to solve
https://codesandbox.io/s/github/tylerbuchea/graphql-apollo-example
and the right question is " How to create a custom resolver as apollo did via adonis-gql ?


Need more section description languages

We have languages for sections 1 (Reference Material), 2 (Introduction) and now references.  We still need to do the same for

[x] Stakeholders
[ ] General System Description
[ ] Scope of the Project
[ ] Specific System Description
[ ] Requirements
[ ] Likely Changes
[ ] Traceability Matrices and Graphs
[x] Values of Auxiliary Constants
[ ] Appendix

Once this is done Verbatim should be removed.

As mentioned in the comments of commit 6da3116, I was wondering if subsections that are created by an overarching function should be their own types? For example, the current stakeholderGeneral function that is used to create the Stakeholders section automatically creates the subsections for "The Client" and "The Customer", which is why I'm hesitant in breaking up the StkhldrProg type... The same goes for the scopeOfTheProjF function that is used by ScpOfProjSec.  @JacquesCarette @szymczdm

The current stakholderGeneral has a very fixed view of how the document will look, and thus forces things to appear in subsections, and also forces subsections for the client and customer.
From an SE perspective, this is great, as it forces people to think about these things.  From a flexibility perspective, this is awful, as it forces a certain look.
My feeling is that the Drasil framework should, at its core, be flexible, and not force these things.  On top of that flexibility, we should layer some checks that will tell you if it is a "good SE document".  [These would, of course, have to be written].
Long story short: please do split.

What is the status of this issue? It looks like it can be closed but I wanted to confirm that I'm not missing something important.

Well spotted - this is indeed done.

@szymczdm
In order to completely remove the use of Verbatim, the remaining sections need DocLang implementations:

[ ] Off-the-shelf solutions (used in GamePhysics)
[ ] Properties of a Correct Solution (used in SWHS)

Related to #504.

Is that really all that's missing? Not bad.


User worning

i am having the following issue:
Update your fit_generator call to the Keras 2 API
What should i do about it?
I know i am asking a lot, but i am working on a graduation project about lip readign
please if any one could help me.
Thanks a lot

Try to use these names of the arguments to the fit_generator
lipnet.model.fit_generator(generator=lip_gen.next_train(),                         steps_per_epoch=lip_gen.default_training_steps, epochs=stop_epoch,                         validation_data=lip_gen.next_val(), validation_steps=lip_gen.default_validation_steps,                         callbacks=[checkpoint, statistics, visualize, lip_gen, tensorboard, csv_logger],                          initial_epoch=start_epoch,                          verbose=1,                         use_multiprocessing=True,                         max_queue_size=5,                         workers=4)

It's okay, it is just a warning.


Microk8s fails to start after rebooting the host.

I installed microk8s on Dell T440 server with Ubuntu 20.04.2 LTS.
sudo snap install microk8s --classic --channel=1.19
Most of the time, when I restart the server , microk8s fails to be restarted properly.
microk8s status
microk8s is not running. Use microk8s inspect for a deeper inspection.
A "microk8s.stop; microk8s.start" doesn't solve the problem. The only workaround I found is to uninstall/reinstall microk8s.
Please find attached the tar file produced by "microk8s inspect"
Thanks a lot for your help.
Best regards

I miss to attach  tarball of "microk8s inspect".
Here it is:
inspection-report-20210310_133050.tar.gz

Something changed with your system clock?
Coz i see this error.
Unable to connect to the server: x509: certificate has expired or is not yet valid: current time 2021-03-10T13:30:47+01:00 is before 2021-03-10T13:26:42Z

Maybe you want to check the expiration date of the CA cert with sudo microk8s.refresh-certs -c.

Thank you Balchua and ktsakalozos
I may have an issue with the NTP server just after the server reboot.
On the  next server reboot  I will check both timedatectl status and certificate validity.

I did a new reboot of my server and reproduced the issue:
# microk8s status
microk8s is not running. Use microk8s inspect for a deeper inspection
There is no issue with time synchronization. And all certificates are valid, see the attached file certs.tar.
# sudo microk8s.refresh-certs -c
The CA certificate will expire in 3648 days.
# microk8s.enable dns
Enabling DNS
Applying manifest
Unable to connect to the server: x509: certificate has expired or is not yet valid: current time 2021-03-12T14:18:12+01:00 is before 2021-03-12T13:34:28Z
Failed to enable dns
#timedatectl
           Local time: ven. 2021-03-12 14:18:31 CET
       Universal time: ven. 2021-03-12 13:18:31 UTC
             RTC time: ven. 2021-03-12 13:18:31
            Time zone: Europe/Paris (CET, +0100)
System clock synchronized: yes
          NTP service: active
      RTC in local TZ: no

So, the issue is somewhere else.
I attached a new inspection-report tar file.
Thanks a lot for your help

inspection-report-20210312_134953.tar.gz
certs.zip

Hello again,
Could you confirm my following analysis :
1 - The server has been rebooted at 13:34:28 CET time. (UTC+1, GMT+1)
$ journalctl --list-boots
0 c3f0e50deea5409684f062653aff41d7 Fri 2021-03-12 13:34:28 CET—Fri 2021-03-12 16:27:58 CET
2 - k8s cluster-info logs reports :
To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
Unable to connect to the server: x509: certificate has expired or is not yet valid:
current time 2021-03-12T13:49:50+01:00 is before 2021-03-12T13:34:28Z
This means that the cluster uses UTC time 12:49:50 and compares it to certificate time 13:34:28
3 - What is wrong: Upon reboot , server.crt is regenerated. But the time is not correct. It appears to be GMT but actually is GMT+1 !
$:/var/snap/microk8s/current/certs$ openssl x509 -noout -text -in server.crt
Certificate:
Data:
Version: 3 (0x2)
Serial Number:
81:86:78:fd:1c:0b:75:4c
Signature Algorithm: sha256WithRSAEncryption
Issuer: CN = <IP_ADDRESS>
Validity
Not Before: Mar 12 13:34:28 2021 GMT
Not After : Mar 12 13:34:28 2022 GMT
Subject: C = GB, ST = Canonical, L = Canonical, O = Canonical, OU = Canonical, CN = <IP_ADDRESS>
Thank you

Is it possible that when MicroK8s was installed, the system time was in GMT all certs were generated using this. Then after the reboot the system time is finally changed to GMT+1?

Hi @hpannetier this is my setup.  The certificates validity generated are always in UTC.
hor@norse:/var/snap/microk8s/current/certs$ openssl x509 -noout -text -in server.crt
Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:
            21:d0:d3:d4:61:dc:99:bb:ef:22:a4:62:af:c9:d6:85:0e:98:67:ca
        Signature Algorithm: sha256WithRSAEncryption
        Issuer: CN = <IP_ADDRESS>
        Validity
            Not Before: Mar 13 03:35:20 2021 GMT
            Not After : Mar 13 03:35:20 2022 GMT
        Subject: C = GB, ST = Canonical, L = Canonical, O = Canonical, OU = Canonical, CN = <IP_ADDRESS>
        Subject Public Key Info:
            Public Key Algorithm: rsaEncryption
                RSA Public-Key: (2048 bit)
                Modulus:

My system time is this
thor@norse:/var/snap/microk8s/current/certs$ date
Sat 13 Mar 2021 11:54:09 AM +08

There must be some tweaking to do on your system time settings.  Since in your case, the UTC time isnt really UTC, it is still ahead by an hour when converted to UTC.(or GMT).

Hello @balchua
Thanks for your help.
I finally found that the issue came from the NTP configuration on the Esxi Vmware where NTP server was set but NTP client service was not started.
It's now working fine.
The tricky part of this issue is that I didn't imagine that the microk8s server certificate would be regenerated upon server reboot and even if the VM is properly synchronized at startup the date/time which appear in the new certificate is the date/time of the esxi rather that the date/time of the VM.
Thanks again for given me the right direction for this trouble-shooting.

Glad to hear that you have nailed this down @hpannetier .  Feel free to open an issue when you encounter some weirdness.


Good Document!!!!

Nicely done!

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

ID: 624b3329-cc27-fe94-e6ed-d13ef4f659b2
Version Independent ID: d603f3e6-bb85-ff8f-d639-415b2b149a6d
Content: Zero Trust Guidance Center
Content Source: zero-trust/index.md
Service: security
GitHub Login: @garycentric
Microsoft Alias: v-gmoor

Thank you for the positive feedback! :)


Report data leakage that causes unfair few-shot setting

As I mentioned in yanxp/MetaR-CNN#36, the released code of Meta R-CNN exists a bug in shot sampling.
Take coco 10shot for example, you will first construct a meta-data set encomprising 30 (3x shots) (prn_image, prn_mask) pairs for each class. The image indexes of these sampled images are saved in a file named annotations/instances_shot2014.json.
After that, roidb needs to be contructed to provide query samples for finetuning purpose. According to the definition of few-shot setting, you can only access to the N-shot (N instances per class) data no matter whether you perform finetuning or not. Therefore, the roidb dataset should contain the same instances as in meta-data set, otherwise it will exceed the designated number of shots. However, as I find in your code, you does not save the anno_index of the selected instances in meta-data set. Instead, you again randomly sample the shot instances from the images list indicated in annotations/instances_shot2014.json. In this case, I am concern about how you guarantee that the newly sampled instances are exactly the same as the ones in meta-data set.
Hope that you can check about this issue and clarify my concern. Thanks a lot.

does the accuracy drops after merging?

does the accuracy drops after merging?


watercourse discharge tool instructions

Hi all. I was asked by Erin to add instructions on how to use the DEA Maps 'Watercourse Discharge" tool to the docs. This work was done as a part of the HNRS project. Please reach out if you have any questions/concerns.

This is awesome - I totally didn't know this was still a thing! Everything looks good to me, can see if anything looks weird once it renders to the docs 😃

Thank you for reviewing this Robbi! I've just merged it!


persist file location

Where is the persis cache fie location on OSX. Cannot find homebridge and need to delete files? Cannot seem to locate. Please be specific

Try this: https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man1/mdfind.1.html

Same as all platforms ~/.homebridge/persist
i.e .homebridge in the users home folder.
Mac OS X hides folders and files that start with a "." So user terminal.
cd ~/.homebridge
rm -rf persist


Update 5.0 -> 5.2: not switching ruby version by '.ruby-version' file in repository

After updating 5.2 from 5.0, ruby version is not switched by '.ruby-version' file in the repository.
It have switched before updating.

Thanks for the issue report. Please reformat your issue to conform to the issue tracker guidelines found in our contributing guidelines.

@jacobvosmaer I have updated the issue report.


add my.articles.series.series to search

Adding the ability to return the search content list with articles.
Not too fussed about the querying, it works. Prismic is finally opening up GraphQL (including queries) so I imagine we will be going dow that route.

@wellcometrust/experience-dev out of WIP


Avoided side-effect of client

Note: Don't comment before looking at 'semistandard fix' which is more than what the desc says. I hadn't had a coffee yet.

The pgm may use a "const" { query: { $client: {...}}} as the hook.params in several method calls.
The client hook will modify this "const" object and it will not function as expected in subsequent method calls.
This subtle effect may be time consuming to find.

const avoidHooks = { query: { $client: { _offline: { ignore: true } } } };
service.create(data1, avoidHooks); // works as expected
service.create(data2, avoidHooks); // doesn't work as avoidHooks was modified above

Yup, whitelist is always an array. Thanks.

A potential gotcha remains once this change is merged. I'm not saying its an error, just that it may trip people up.
const aQuery = { $client: { _offline: { ignore: true } } };
service.create(data1, { query: aQuery });
// aQuery = { $client: { _offline: { ignore: true } } } as expected

const aParams = { query: { $client: { _offline: { ignore: true } } } };
service.create(data1, aParams);
// aParams = { query: {}, _offline: { ignore: true } } which may not be expected

:shipit:


Setting js-only properties on an Element

I'm trying to determine the best way to set an indeterminate state for a checkbox input element. Because this is a property accessible only via javascript, I don't believe vdom has any options I can pass to h() to set this value.

Is there a purely vdom-way I can set this value?
If not, what's the recommended way for obtaining the resulting html element after rendering?

Is there a purely vdom-way I can set this value?

Same as any other DOM-node property. :-)
h('input', {
  type: 'checkbox',
  indeterminate: true,
})

Every property you set with virtual-hyperscript gets set on the resulting DOM node, even if it's not part of the JS DOM API. I found this out by accident; I misspelled a property name.

If not, what's the recommended way for obtaining the resulting html element after rendering?

Most of the time when you need the resulting DOM element, you would use a hook. It's unnecessary here (which is great because this 2x as much code), but it could be done:
var IndeterminateSettingHook = function() {}

// The node arg is the actual DOM node that gets rendered, not a vdom node.
IndeterminateSettingHook.prototype.hook = function(node) {
  node.indeterminate = true;
}

h('input', {
  // It doesn't matter what you call the property you assign it to, but "hook" isn't a bad one.
  hook: new IndeterminateSettingHook(),
  type: 'checkbox',
};

That's immensely helpful, thanks. Unfortunately I'm blocked on using checkboxes entirely until I have a fix for #335


Move JSON files to src/main/resources and access them from classpath

This should fix #90

If you are pulling this change on an existing project in VS Code, you will need to delete .classpath to have VS Code generate a new one that includes src/main/resources for testing to work in VS Code.

Replaced by #109


Crashing game while using text entities

while editing the text entity, pressing CTRL A to select all the dialogue in the text selects every object in the level. If you chose to delete the text, it will also delete everything else in the level as well. Once you exit the text editor the game crashes because the original place where the text originally was no longer exists and the game doesn't like that. It's really annoying and it happens to me on accident way to many times. Fixing both of these bugs would be a blessing for me.

Minor note, this doesn't happen with just text, but any entity that you can adjust the settings within the entity.

86aac741d2eadeb78e64eb931eec304f92dd74a2


Unable to test due to loadig issue with GoogleMapsLoader

Getting error when I ru my test  as below:
console.error node_modules/react-test-renderer/cjs/react-test-renderer.development.js:6309
The above error occurred in the  component:
in GoogleMapsLoader (at GooglePlacesSuggest.js:72)
● UserDetails component › matches the snapshot
TypeError: Cannot read property 'parentNode' of undefined

  at _addScript (node_modules/little-loader/lib/little-loader.js:43:17)
  at _lload (node_modules/little-loader/lib/little-loader.js:209:7)
  at loadGoogleMapsSdk (node_modules/react-google-maps-loader/lib/loadGoogleMapsSdk/index.js:43:34)
  at GoogleMapsLoader.componentDidMount (node_modules/react-google-maps-loader/lib/index.js:45:37)
  at commitLifeCycles (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:6444:22)
  at commitAllLifeCycles (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:7540:7)
  at HTMLUnknownElement.callCallback (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:1899:14)

I am using jest

Add this code to your jest test file -
beforeAll(() => {
  const script = document.createElement("script")
  document.body.appendChild(script)
})

could you make a PR to resolve this?


chore: upgrade storybook 8

📝 Description
Currently, there are many issues and incorrect usages with version 7 of Storybook.
Some typical problems include:

HMR invalidate Could not Fast Refresh, reducing development efficiency.
Errors on the homepage in development mode.
Outdated configuration file definitions.

To resolve the issues mentioned above we have upgraded to the latest Storybook 8.
The main changes include:

Resolved the fast refresh issue for components, leading to an improved development experience.
Changed the configuration file from main.js to main.ts for better type hinting.
Renamed xxx.storybook.mdx to xxx.mdx.
Added the autodocs addon.
Fixed errors on the homepage.

Summary by CodeRabbit
Summary by CodeRabbit

New Features

Upgraded Storybook to version 8.4.5, introducing new features and improvements.
Added support for remark-gfm to enhance documentation capabilities.
Introduced a new Vite configuration for improved performance with React.
Added a tags property to the preview object for enhanced documentation features.

Bug Fixes

Improved logic for determining strict mode in Storybook.

Documentation

Updated paths and configurations in Storybook documentation files for clarity and consistency.

Chores

Cleaned up and standardized code formatting across various files.

Still have some hot reload issues

Thank you! @winchesHe


[TST] Fix test filtering and add recordset test tiers

Description of changes
Summarize the changes made by this PR.

Improvements & Bug fixes

...

New functionality

...

Test plan
How are these changes tested?

[ ] Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Documentation Changes
Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs repository?

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#2385  👈
#2383
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @HammadB and the rest of your teammates on  Graphite


Improve experience for creating signers

This PR adds a new package farcaster-js-cli that is included in the farcaster-js package for creating signers. It also updates the neynar package to simplify signer creation. These changes are reflected in the top level README so developers can easily find this information.
Example CLI runs:
$ farcaster-js create-signer
There are 2 options for creating a signer.

Developer Managed:
- A signer is generated by interacting with the KeyGateway Contract on Optimism (0x00000000fc56947c7e7183f8ca4b62398caadf0b).
- You must have a small amount of funds (~0.001) in your account's custody address on Optimism.
- You will need to provide the mnemonic for your account.
- This signer can be used anywhere (except with Neynar).

Neynar Managed:
- Neynar creates a signer using your developer mnemonic.
- Approval is done through the Warpcast App by any user.
- Payment is required in the app using Warps or a $0.99 in-app purchase.
- A Neynar API Key is necessary.
- This signer is exclusive to Neynar APIs.

Which type of signer will you be creating?
 (Use arrow keys)
❯ developer
  neynar
? Enter your mnemonic: your mnemonic goes here
Transaction written to OP Mainnet. Check txn status at https://optimistic.etherscan.io/tx/<txn hash>
Transaction Confirmed! Your signer is ready to use.

$ farcaster-js create-signer
There are 2 options for creating a signer.

Developer Managed:
- A signer is generated by interacting with the KeyGateway Contract on Optimism (0x00000000fc56947c7e7183f8ca4b62398caadf0b).
- You must have a small amount of funds (~0.001) in your account's custody address on Optimism.
- You will need to provide the mnemonic for your account
- This signer can be used anywhere (except with Neynar).

Neynar Managed:
- Neynar creates a signer using your developer mnemonic.
- Approval is done through the Warpcast App by any user.
- Payment is required in the app using Warps or a $0.99 in-app purchase.
- A Neynar API Key is necessary.
- This signer is exclusive to Neynar APIs.

Which type of signer will you be creating?
 (Use arrow keys)
  developer
❯ neynar
? Enter your Neynar API Key: <neynar api key>
? Enter the mnemonic for the developer: your mnemonic goes here
Creating a new Neynar signer...
 ▄▄▄▄▄▄▄ ▄▄▄ ▄▄ ▄▄ ▄  ▄ ▄  ▄▄▄▄▄▄▄
 █ ▄▄▄ █  ▄██ ▀█ █▄█▀█▄▀▄▄ █ ▄▄▄ █
 █ ███ █ ██ ▄▀▄ ▀█▀ ▄   █▄ █ ███ █
 █▄▄▄▄▄█ █ █ ▄ █▀▄ █ █▀▄ █ █▄▄▄▄▄█
 ▄   ▄ ▄▄█▀ ▄█  ▄ █▀▀▀█▀  ▄▄▄▄▄  ▄
 █▀▀▀▀▄▄▄▀█▀█▀▄▄█▀▀█ ▄▀▄█ ▀   █▀█
 ███ █▄▄▀ ▀  ▀█ █▄  █ ███ ▀█ ▄▄  ▄
  ▄▄██▀▄▀█▀ ▀▄▀█▄ ▀█▀█▀▀█▄█▄█ ▀▄▄
 ▄█▄ ▀█▄▀█▄█  ▄ ▀▀█ ▄ ██▀█▀█▀█▀ ▄
  ▀█ ▄█▄▄▀▀▄  ▄██▄▄▀ ▄ ▄█ ▀ ▄ █▀▄
 ▄▀▀▄▄ ▄ ▄ ▀██▀ ▀ ▀█▀█▀ ▀█▀▄█▄▄ ▄▄
 ▀▀▄▄█▀▄▄▀█  █▀▀ █▄▄█  ▄█ ▄ ▀▄▀▄█
 ▄▄▄██▄▄ █▄▄█ ▀█▄ █ ▀██▄▀█████  ▀▀
 ▄▄▄▄▄▄▄ ██▀ ▀▀▀██▀█ █▀ ▀█ ▄ █▄▀▄
 █ ▄▄▄ █ ▄ ▀▄█▀█ █   ▀ █ █▄▄▄█▄ █
 █ ███ █  ▀▄▀▄█ ▄ ▄▀▀█▀ ██ █████▀
 █▄▄▄▄▄█ ▄█▄▀▀█▀▀██▀▄▄█▄▄█       ▄
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀

URL: https://client.warpcast.com/deeplinks/signed-key-request?token=<register token>
Signer UUID: <signer uuid>

Scan the QR code above or visit the URL on a logged in device to approve signer

-----------------------------------

Once approved, you can start using your signer with Neynar to write data to Farcaster
( ●    ) Approved! Now you can start using this signer.
Signer UUID: <signer uuid>
✔

It also refactors signer creation in the neynar package, see below:
Creating a neynar signer before:
  // create signer
  const signer = await client.v2.createSigner();

  // create signature
  const signature = await generateSignature(
    signer.public_key,
    signerFid,
    privateKey,
    deadline,
  );

  // register signer
  const registeredSigner = await client.v2.registerSigner(
    signer.signer_uuid,
    userBotFid,
    deadline,
    signature,
  );

Creating a signer neynar after:
const registeredSigner = await client.v2.createAndRegisterSigner(
  signerFid,
  deadline,
  privateKey,
);

Open questions:

Should we mask input for mnemonics?
Should we warn users about protecting signer private keys / signer uuids?

@gsgalloway ready for another review. Looking into what went wrong with docs generation now.


Snapshotting Arrays with Matchers

🐛 Bug Report
Creating a snapshot with array + matchers is not possible without wrapping array into an object.
To Reproduce
expect(['foo']).toMatchInlineSnapshot([expect.any(String)]);

Expected behavior
expect(['foo']).toMatchInlineSnapshot([expect.any(String)], `
  Array [
    Any<String>,
  ]
`);

Actual behavior
expect(['foo']).toMatchInlineSnapshot([expect.any(String)], `
  Object {
    "0": "foo",
  }
`);

I'm able to get by by taking my result and placing it in an object then doing the snapshot, but I feel like I should be able to snapshot an actual array with matchers.

cc @pedrottimark noticed something when dealing with propertyMatchers in https://github.com/facebook/jest/pull/9049?

Sadly, snapshot testing with property matchers is unusable with arrays at the moment.

This also tripped me up, and I've confirmed it is still an issue on 26.2.2. My use case involves nested objects in arrays. Specifically rows that come out of a testing database where there are columns that default to the current time (and are thus outside the control of mocking).
A simple way to replicate the error:
expect([
      { id: 1, createdAt: new Date() },
      { id: 2, createdAt: new Date() },
    ]).toMatchSnapshot([
      { createdAt: new Date() },
      { createdAt: new Date() },
    ]);

The snapshot I'd expect:
Object {
  "0": Object {
    "createdAt": Any<Date>,
    "id": 1,
  },
  "1": Object {
    "createdAt": Any<Date>,
    "id": 2,
  },
}

The snapshot I get:
Object {
  "0": Object {
    "createdAt": 2020-08-06T23:54:53.133Z,
    "id": 1,
  },
  "1": Object {
    "createdAt": 2020-08-06T23:54:53.133Z,
    "id": 2,
  },
}

The object wrapping approach @j suggested has worked:
expect({ data: [
    { id: 1, createdAt: new Date() },
    { id: 2, createdAt: new Date() },
  ]}).toMatchSnapshot({ data: [
    { createdAt: expect.any(Date) },
    { createdAt: expect.any(Date) },
  ]});

Produces a snapshot of:
Object {
  "data": Array [
    Object {
      "createdAt": Any<Date>,
      "id": 1,
    },
    Object {
      "createdAt": Any<Date>,
      "id": 2,
    },
  ],
}

Any progress on this feature?

Just ran into this issue, would love to see a fix.

Any updates?

Any updates?

Would love to see this feature implemented, just wanted to bump to keep the issue from getting stale

Any updates on this?

Encountered this issue today. Bummed that it hasn't been fixed in 5 years.


Run WorkerThreadPool tasks on the main thread when in single-threaded mode

Includes a partial fix for some issues that come up when threading/worker_pool/max_threads is set to 0.

cc @RandomShaper

Thanks!


Add upload button to upload the required file.

I think the plugin will be helpful if the upload button is added to the frontend. If the user can manually add the required data format, it will be helpful for user.

u can find solutions on ytube


allow setting annotations

This adds a new build flag for setting annotations on image indexes and manifests.
Annotations are no longer copied from the base image. org.opencontainers.image.base.digest and
org.opencontainers.image.base.name
are always set to the resolved values.
Usage example:
ko build --image-annotation foo=bar,fizz=buzz .

Fixes #1090
Fixes #1090
Fixes #1231
Fixes #1235
Fixes #1395

This looks good! I slightly wonder if we should have some mode (possibly default) where labels are just copied to annotations, but I don't feel strongly and this is clearly something that folks want, so let's just do it.
Thanks for this contribution!

Cool, thank you!


deps

dear miss, i wanted to copy your codes for PHP runtime but refrained. that header file contains fprints and other "std" output functions which doesnt quite fit sucha tool as PHP. see, the output should not be bound to those, its better to decide on integer codes.

Hi,
The <stdio.h> functions used by this library don't actually print anything to the terminal (for a large part).
https://github.com/kspalaiologos/yarg/blob/main/yarg.h#L48 handles allocation failures by terminating and vsnprintf is used by https://github.com/kspalaiologos/yarg/blob/main/yarg.h#L52 to format error messages into a string.
Is the PHP interpreter forbidden from using the libc? If this is the case, we would have to provide substitutes for str* functions (e.g. strcat, strcpy), which is out of scope of this project - feel free to host your own fork!

ye, oke. you position it as a library so imo its better to provide numeric error codes, because PHP (or others) formatting may be different or absent. i just want to drop unnecessary deps to improve PHP core. argument parsing is a singleton operation there. ive made a clone and compiled it several times, but building procedure is very complicated, i have to simplify it first.

I designed yarg to be a more-or-less drop-in getopt replacement, because getopt_long is not available on a lot of non-GNU platforms and existing implementatons have weird licensing implications. I think that this library perhaps has not been made with your specific purpose in mind, but you're free to host a fork. Thanks for filing the ticket.

ye, you right, i dont know what is getopt_long, i only know arguments :]


Error: Not found: /

When building the hugging face hub using the command doc-builder preview hub {path}/docs/hub/ --not_python_module where path is my local path to the cloned repository, it is giving 404: Not Found Error.
I have followed the same steps as mentioned on the hugging face hub repository: https://github.com/huggingface/hub-docs#previewing-locally.
Can someone please help in what the issue could be and a possible solution for the same?
Terminal Logs:

Website Output:

I encounter the same with main - I have to use an older commit to get it to work well.

Thanks for the help.
I'm still having trouble with doc-builder preview hub /hub-docs/docs/hub --not_python_module for example and
same error Not Found: /
im on debian bullseye, python3.10, node 20

I went back to 3de0a0e9f824fc50e78c873732ef4a4ebaeb005b, though that's probably further than necessary.


Overlay: Add accessible names to Overlay dialog examples

Adds an accessible name (aria-label) to Overlay dialogs.
Dialogs are typically named based on the content it provides, adding labels to the dialogs in the stories help convey what the dialog is for initially to assistive technologies.
Changelog

New

Adds aria-label to Overlay dialog examples

Rollout strategy

[ ] Patch release
[ ] Minor release
[ ] Major release; if selected, include a written rollout or migration plan
[x] None; if selected, include a brief description as to why - This is a storybook only change and doesn't change anything else.

Testing & Reviewing

Merge checklist

[ ] Added/updated tests
[ ] Added/updated documentation
[x] Added/updated previews (Storybook)
[ ] Changes are SSR compatible
[x] Tested in Chrome
[ ] Tested in Firefox
[ ] Tested in Safari
[ ] Tested in Edge
[ ] (GitHub staff only) Integration tests pass at github/github (Learn more about how to run integration tests)

After looking at the conflicts, we don't need this change anymore as we've added it in another PR. Closing!


PrDataset will not use the projection interface

Is your feature request related to a problem? Please describe.
We decided not to use projection in the dataset because of management issues.
Describe the solution you'd like
The projection interface of  PrDataset will be removed
"detail" projection won't use.
"preview" parameter will be used instead.
Describe alternatives you've considered
Additional context

dataset doesn't use projection interface.
@paigechoi is an assignee now.


Add embedded app server

Added TomEE application server using tomee-maven-plugin that could quickly run application using mvn tomee:run.

Thanks @AlexOreshkevich


Issue with k8s.io/docs/setup/best-practices/node-conformance/ setting kubelet

This is a Bug Report
Inability to set kubelet api-servers
Problem:
As per https://kubernetes.io/docs/setup/best-practices/node-conformance/
Point your Kubelet to localhost --api-servers="http://localhost:8080", because the test framework starts a local master to test Kubelet.
** Expected result **
Kubelet should point to the correct api-servers.
** Actual result **
kubelet cannot start because --api-servers is not a valid option, since it was changed to --kubeconfig
Proposed Solution:
Modify the documentation to create a kubeconfig file that points to the api servers http://localhost:8080.
Page to Update:
https://kubernetes.io/docs/setup/best-practices/node-conformance/
Kubernetes Version: v1.18.5

/language en
/kind bug
/assign

/remove-lifecycle stale


Fix a problem in the manageorg User class currentFolder.setter method

@mgleahy  can you please provide some code to reproduce your issue?

import arcrest
sh = arcrest.AGOLTokenSecurityHandler(username='mgleahy', password='xxxxxx')
admin = arcrest.manageorg.Administration(securityHandler=sh)
content = admin.content
currentUser = content.users.user()
currentUser.currentFolder = 'SomeFolderThatIsNotRoot'
currentUser.currentFolder = 'root'
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "arcrest\manageorg\_content.py", line 2024, in currentFolder
    self.location = self.root
AttributeError: can't set attribute

It seems to me like that whole elif block for handling / or root folder names is redundant - it could simply be include in the initial if value is None: block - maybe just if value is None or value.lower() in ('/', 'root'):
Just a thought...


Add support for PK lookup if additional filters are combined by AND

If filters are combined by AND operators in addition to filters
on primary key columns, the optimized PK lookup plan is used now.
Closes #10298.

moved back to draft mode, as I completely forgot to add the filters to the execution (filter projections) 🤦

As a follow up - we should probably tweak the explain output so that the query part is visible?

As a follow up - we should probably tweak the explain output so that the query part is visible?

Ah good point, will do.


Going beyond a simple flat Object as a parameter in a signalR server-side method

All the examples I've come across from Microsoft documentation uses a simple "flat" object, such as
public class TotalLengthRequest
{
    public string Param1 { get; set; }
    public string Param2 { get; set; }
}

How about doing some nesting, for example:
public class TotalLengthRequest
{
  public string Param1 { get; set; }
  public string Param2 { get; set; }
  public NestedType MyNestedObj  {get; set;}
}

This is no longer straight-forward, when calling from a JS client to a server-side method;
In fact, i suspect it does not even work, with only one level of nesting, as I've already tried this without success;
(sending to a client-side method from the server seems ok).
It would be good if the "official" documentation gave an example, or made some remarks whether it is even possible to go beyond a simple object.

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

ID: 2f06ca2b-9d96-9979-46a8-d09900af0653
Version Independent ID: 0f0d321d-46ed-25cb-6bb4-e4611343b131
Content: SignalR API design considerations
Content Source: aspnetcore/signalr/api-design.md
Product: aspnet-core
Technology: aspnetcore-signalr
GitHub Login: @bradygaster
Microsoft Alias: bradyg

This should work fine. What doesn't work?

Closing due to inactivity.


⚠ Bofrost.at has degraded performance

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

HTTP code: 200
Response time: 857 ms

Resolved: Bofrost.at performance has improved in 6253069.


Code reveiw

In this project i am using HTML and CSS. All requirements are added.

Hi @adel-gu ,
I made the changes that you provided me can you please check this.


Failed to update application: '**', because patch resource group failure [with latest az cli version 2.37.0]

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Related command
Installed version
Dependencies:
msal                            1.18.0b1
azure-mgmt-resource      21.1.0b1
azure-cli                         2.37.0

To Reproduce
az tag create
--resource-id /subscriptions//resourceGroups//providers/Microsoft.Databricks/workspaces/***
--tags version=*****
Expected behavior
it should update the tag for the mentioned resource, In this case it should update the tag version of databricks.
Environment summary
Running command on Ubuntu Server
Additional context
ERROR: (ProviderError) {"error":{"code":"ApplicationUpdateFail","message":"Failed to update application: '**', because patch resource group failure.","details":[{"code":"NoRegisteredProviderFound","message":"No registered resource provider found for location 'eastus2' and API version '2019-08-31' for type 'userAssignedIdentities'. The supported api-versions are '2015-08-31-PREVIEW, 2018-11-30, 2021-09-30-PREVIEW, 2022
Our Resources are already registered and were working fine with previous az cli version 2.36.0

ARM

I didn't get you, What do mean by ARM?

This is an ARM service related issue. We need the server team to confirm whether they register the resource provider or we upgrade the api-version

Please let me know if any other details is needed

any update on this?

"message":"No registered resource provider found for location 'uksouth' and API version '2019-08-31' for type 'userAssignedIdentities'.
I got similar error while modifying databric workspace (re-deploying) via Terraform  ..... Details=[{"code":"NoRegisteredProviderFound","message":"No registered resource provider found for location 'uksouth' and API version '2019-08-31' for type 'userAssignedIdentities'. The supported api-versions are '2015-08-31-PREVIEW, 2018-11-30, 2021-09-30-PREVIEW, 2022-01-31-PREVIEW'. The supported locations are 'southafricanorth, southafricawest, uaenorth, australiacentral, australiaeast, australiasoutheast, canadacentral, canadaeast, brazilsouth, centralindia, westindia, jioindiawest, southindia, japanwest, japaneast, eastasia, southeastasia, koreacentral, koreasouth, northeurope, westeurope, ukwest, uksouth, swedencentral, switzerlandnorth, germanywestcentral, centralus, northcentralus, eastus, eastus2, southcentralus, westus, westus2, westus3, westcentralus, francecentral, norwayeast'."}]
Microsoft.Databricks  and Microsoft.ManagedIdentity both registed prior to deployment still this error

@zhoxing-ms Please let me know if you have any update on the ongoing issue

No registered resource provider found for location 'eastus2' and API version '2019-08-31' for type 'userAssignedIdentities'.

@mvvsubbu Could you please help take a look at the Microsoft.Databricks RP service related issue

@kamlesh2015 sorry to hear you are facing this issue, can you please share me the azure resource id of the workspace to take a look at the issue?

@kamlesh2015 we figured out the issue, we are working on deploying a fix, it should available in few days. My colleague @sabose1 is going to update you the state of the fix deployment. Sorry for the inconvenience again.

@mvvsubbu Thanks for the reply, Please keep us updated on the progress :)

My colleague @sabose1 will post updates next week as I am going on PTO.

@mvvsubbu , @sabose1  Many thanks for your quick response; please keep us on loop on this progress.

The fix has been tested and merged. It will be deployed in public regions before June 10th.

Deployment has now been completed in all regions. I have tested the scenario in uksouth and it seems to work.

Hi @sabose1 , I tested it worked. Thank you for sorting this out this issue.

Thanks @sabose1 for addressing this issue. @vivek602 can you close this issue?

Thanks @mvvsubbu.


Table history timestamp missing timezone information

Environment
Delta-rs version:
See below.
Binding:
Python - delta-spark = '1.2.1'

Bug
What happened:
Retrieving the last commit timestamp from table history returns a value in the format 2022-09-21 13:45:08.100000. This timestamp contains no timezone information. Am I to assume this is UTC?
What you expected to happen:
Timestamp will include timezone information.
How to reproduce it:
from delta import DeltaTable

table = DeltaTable.forPath(spark_context, backend_url)
timestamp = table.history(depth).first()['timestamp']

More details:

This repo is for the Rust-based implementation (deltalake). For the Spark-based one (delta-spark), you can report here: https://github.com/delta-io/delta/issues


=== with integer subtype

In slalpha5, this:
function f(int:Signed32|object{} v) returns boolean {
  return v === 0;
}

gets the error operator '===' not defined for '(int:Signed32|object { })' and 'int'.
Changing int:Signed32 to int makes the error go away.

Fixed in https://github.com/ballerina-platform/ballerina-lang/pull/31861.


support rollup function in druid 0.9.2

RT , support ability to disable rollup released in druid V0.9.2.

@gianm Could you have a check on this? Tests aren't passed because they were not before.

Hey @GavinGavinNo1, thanks for the contribution! Reviewing now.
Could you also please fill out our CLA at: http://druid.io/community/cla.html (it's the same CLA as Druid). Thanks!

The tests are a little sketchy when running on Travis unfortunately… but they should pass eventually. I'll try running them again.

@gianm I have already updated it.

Thanks @GavinGavinNo1, 👍 on this change. Could you please fill out the CLA (http://druid.io/community/cla.html) so we can merge it?

Hey @GavinGavinNo1, for individuals it's simpler for us (and you) if you fill out the online form; would you mind doing that?

@gianm Not at all.  I filled out the online form just now, please check it. Thanks.

thanks @GavinGavinNo1, got it!

👍


KAFKA-17860: Remove log4j-appender module

JIRA: KAFKA-17860
Since we are migrating to log4j2, we have to remove the log4j-appender module due to it being deprecated and its dependency on the clients module.
https://github.com/apache/kafka/blob/2d896d9130f121e75ccba2d913bdffa358cf3867/build.gradle#L3354-L3375
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Would you be willing to replace log4j-appender with a refactored version of the Log4j Core 2.x Kafka appender?
Currently the appender is deprecated and planned to be removed in Log4j 3.x, mostly because of the outstanding issues and the lack of Kafka experts in the Logging PMC.
Personally, I am not even sure if ProducerRecord<byte[], byte[]> is the right kind of object to be sent to Kafka.

hi @ppkarwasz
Thanks for the suggestion. Could you please consider sharing this information on the dev channel (dev@kafka.apache.org)? It would be great to see how many users are interested in having this appender :)

Thanks, I opened a thread on dev@kafka.


update constructor to return an error if the token is missing

Hey @ryankurte,
I have implemented a way to check in the base constructor whether the token provided is empty (invalid) or not, what do you think?
Also, running tests I notices two errors with Errorf but I don't think this is related to this PR code, is it?
ok  	github.com/ryankurte/go-mapbox/lib	(cached)
?   	github.com/ryankurte/go-mapbox/lib/base	[no test files]
ok  	github.com/ryankurte/go-mapbox/lib/directions	(cached)
ok  	github.com/ryankurte/go-mapbox/lib/directions_matrix	(cached)
ok  	github.com/ryankurte/go-mapbox/lib/geocode	(cached)
ok  	github.com/ryankurte/go-mapbox/lib/map_matching	(cached)
# github.com/ryankurte/go-mapbox/lib/maps
lib/maps/tile.go:48: Errorf format %d has arg offsetX of wrong type float64
lib/maps/tile.go:51: Errorf format %d has arg offsetY of wrong type float64
FAIL	github.com/ryankurte/go-mapbox/lib/maps [build failed]

Cheers,
Cédric

Also, I could add something to check the token format, as we know it should be a valid JWT token as explained here: https://www.mapbox.com/api-documentation/#the-token-format. What do you think?

Looks good to me, thanks!

I don't think it's worth worrying about token validity since the API should error on that anyway, and I'm not seeing those errors here at the moment, will have to look into why that is.

I'm still on 1.9.2 apparently, so could well be.


Initial ms parser

Very much a WIP, but I thought I'd share just so you know I'm working on it at least!
The basic approach of adapting the msprime argparse code will work I think, and I think the error handling for parsing is working well - setting parser.error = ValueError seems to do the trick quite nicely.
One high level question though: what should we do with ms command line args that aren't to do with directly defining the demography? There's two classes I think:

Arguments for defining the sample size. This is intrinsically linked up with defining the demography, so I'm currently returning a tuple DemeGraph, num_samples, so that we return the parsed-out number of samples per deme. I'm not at all sure this is the right approach - maybe we should just ignore all the sample size stuff?

What do we do with arguments like num_replicates, -T, -t etc? Should we accept an valid ms command string, but ignore any stuff that isn't about defining demography? Currently we'll error on any arguments that aren't about the demography, but I'm not sure this is the correct thing.

Anyway, thoughts appreciated. i wouldn't bother looking at the code much, it's not ready for review.

Edit: I should add that the plan is not to import msprime like it's doing at the moment

Cool! Thanks @jeromekelleher! In general, I think we could just warn about arguments that are unused/untranslated. Maybe have a warn_unused param to from_ms() that defaults to True? Returning the sample info is a good idea too. But probably we need to think harder about sampling?
It's clear that all simulators that consume deme graphs will also need to think about samples. At least, users will specify sampling somehow, and the samples and sampling times should at least be checked against the demes and deme existence times. I think it will also be common to want to prune a deme graph, given a set of samples, to just the ancestry of those samples.

It's clear that all simulators that consume deme graphs will also need to think about samples. At least, users will specify sampling somehow, and the samples and sampling times should at least be checked against the demes and deme existence times.

Yes, I guess we do need some way of describing samples, although I'd hoped that this could be left to the individual simulators. In principle, forward simulators don't need samples.

I think it will also be common to want to prune a deme graph, given a set of samples, to just the ancestry of those samples.

Yes, good idea. So we reason about the demes that are unreachable from the sampling demes, given the migration rates etc. Sounds do-able.

I'm not making a whole pile of progress on this, and it seems I'm unlikely to get the time to actually get into this for while. If anyone else would like to pick this up, I'd be happy to give pointers on where to go with it. Basically, the text parsing is taken care of and we "just" need to translate the model into a demes graph.
Just in case anyone is wondering where this PR is going ...

I've just pushed a commit that completes the ms converter. The API is open to discussion, and test converage is still low, but it works for the examples in the ms manual and for the zigzag and Gutenkunst OOA models.

I'm going to squash and merge this. Its too big to expect an in-depth code review and I'm fairly confident it's doing the right thing (>1000 lines of tests).


integration: Disable installing Security Profile Operator

The security profile operator is only used by TestAuditSeccomp to install a simple seccomp profile in the cluster. This is an overkill.
This commit uses a simpler approach by copying the profile by using a DaemonSet to the node and disables installing this by default. The code to deploy/undeploy the SPO isn't removed as it could be useful to test the "advise seccomp" gadget in the future.
Some reasons to avoid deploying the SPO are:

It needs quite a lot of resources
It takes a lot of time to be deployed
Some times it fails to be deployed, and also to be cleanup, leaving it running on the cluster

Merging now, I'll monitor this test to see if there are any issues later on.


cannot pickle fugashi

t dude followed the readme, tried to run ytdl-tui, got this

fixed in v1.2


Add Trans-Canada road shield

https://en.wikipedia.org/wiki/Numbered_highways_in_Canada

We'd track province shields in other issues, as needed.

This has been completed and is checked into the Illustrator files, but is awaiting publishing.


Implement a caching mechanism

It would be great to implement caching on various to minimize IO operations.

My first implementation was kind of dummy, the hooks for getting / settings a cache value are not at the proper place. Instead of caching the final result (model instances, and so on, we should cache the underlying backend (SQL, http...) response.


[Bug]:metric k8sgpt_number_of_results_by_type is missing

Checklist

[X] I've searched for similar issues and couldn't find anything matching
[X] I've included steps to reproduce the behavior

Affected Components

[ ] K8sGPT (CLI)
[X] K8sGPT Operator

K8sGPT Version
0.2.0
Kubernetes Version
1.31
Host OS and its Version
linux
Steps to reproduce
1 - install k8sgpt operator
2 - install kube-prometheus-stack
3 - identify grafana is not exposing k8sgpt_number_of_results_by_type
Expected behaviour
expect k8sgpt_number_of_results_by_type to be exposed by metric by k8sgpt opeator
Actual behaviour
k8sgpt_number_of_results_by_type should be exposed by k8sgpt opeator based on the code
https://github.com/k8sgpt-ai/k8sgpt-operator/blob/6dba661ce6bbf6be14edbfb457c0a5d56d7dc17b/controllers/k8sgpt_controller.go#L111
However it is not exposed
From grafana dashbord, you can see the k8sgpt_number_of_results_by_type metric is missing

Additional Information
No response

As referenced #584  Agree this is a bug


TBL data to CSV

Solves #25
This code can be used to export TBL data sections into a CSV format, enabling compatibility with other software for tabular data analysis. It enables us to store the extracted TBL data in a structured format suitable for CSV output, ensuring that the correct mapping of attributes occurs. It implements logging (e.g., info or warning) to document issues like empty or malformed sections without interrupting the export process.
Screenshots:

Image showing the output_csv directory containing the resultant CSV files

Image showing the warning on the terminal when there is incorrect or improper data

@DeviPriya-Kolla, I have updated the README.md with dependencies.


Fix Local Path Issue for any-dns Dependency

The any-dns dependency in Cargo.toml is currently pointing to a local path:
https://github.com/pubky/pkdns/blob/master/server/Cargo.toml#L16
# any-dns = "0.3.1"
any-dns = {path = "/Users/severinbuhler/git/pknames/any-dns"}

I tried replacing it with any-dns = "0.3.1", and it compiles fine. However, I’m not sure if it will work in every situation or if a modified version is needed.
Could someone clarify or make adjustments to ensure it works universally?
Thanks!

That's my bad, a development artifact. Fixed.


Add publishing and release to the build script

Currently, there is a limited target for publishing dev builds to myget. We need the full standard set of targets, including publishing to NuGet and Chocolatey and creating draft and final releases on GitHub.

:tada: This issue has been resolved in version 2.0.0 :tada:
The release is available on:

GitHub Release
NuGet Package
Chocolatey Package


Full vertical scroll (or less internal components)

I'm using Readium with a specific requirement: full vertical scroll, instead of the existing mix of vertical scroll + swipe to switch chapters. This currently requires skipping a lot of the library UI code and managing my own RecyclerView of chapters with R2WebView items inside. With the version currently in develop this kind of usage becomes harder because a lot of important navigator components are internal like EpubNavigatorViewModel and WebViewServer.
a) Could the visibility of those components be revised?
b) A ViewPager is currently being used for displaying chapter resources. Could a RecyclerView with a PagerSnapHelper be an interesting alternative? That way switching between all pages, scroll + chapter pages, or full scroll would be way easier.

I'm using Readium with a specific requirement: full vertical scroll, instead of the existing mix of vertical scroll + swipe to switch chapters.

That's interesting. If you already implemented it, could you share a screencast of what it looks like? We are not particularly happy with the horizontal swipes across chapters and would be opened to have a different behavior.

a) Could the visibility of those components be revised?

Unlikely, because they would increase the API surface and prevent any significant implementation changes. We used to have too much stuff public and are trying to reduce the public API to keep it maintainable and the private implementation flexible.
That being said, we're open to make public some components as "helpers", if they are really independent and their APIs clearly defined. WebViewServer and ReadiumCss could make good candidates. Though this is pretty low priority and we want to be careful when exposing private details.

b) A ViewPager is currently being used for displaying chapter resources. Could a RecyclerView with a PagerSnapHelper be an interesting alternative? That way switching between all pages, scroll + chapter pages, or full scroll would be way easier.

The EPUB navigator didn't change much since the beginning. There was an attempt to migrate to ViewPager2, but it was aborted because it is only a good fit for paginated modes. There's also an old issue suggesting just that, but not much else.
In the context of Navigator 2, we (core developers) are experimenting with Jetpack Compose to implement a new navigator. At the moment, we don't plan to improve the way resources are displayed in the current EPUB navigator. However, if you want to tackle this in the current implementation, I think it would be a welcome contribution.

That's interesting. If you already implemented it, could you share a screencast of what it looks like? We are not particularly happy with the horizontal swipes across chapters and would be opened to have a different behavior.

Here's how it's looking with the latest develop branch. I haven't migrated to the new ReadiumCss so the layout isn't how it should be.
https://user-images.githubusercontent.com/106415/208692958-d0505bab-f44d-4b02-8a2f-82db78e9f156.mp4

Unlikely, because they would increase the API surface and prevent any significant implementation changes. We used to have too much stuff public and are trying to reduce the public API to keep it maintainable and the private implementation flexible.
That being said, we're open to make public some components as "helpers", if they are really independent and their APIs clearly defined. WebViewServer and ReadiumCss could make good candidates. Though this is pretty low priority and we want to be careful when exposing private details.

Right now this means I had to copy over the WebViewServer, ReadiumCss, Layout and HtmlInjector. And I will either have to duplicate the EpubNavigatorViewModel as well, with more internal dependencies likely, or just copy the code that maintains the Preferences API + ReadiumCSS.

Here's how it's looking with the latest develop branch. I haven't migrated to the new ReadiumCss so the layout isn't how it should be.

This looks great. Why don't you contribute it back into Readium? That would solve the problem of accessing internal components.
As a first step and to limit regressions until it's battle tested, it could be a copy of the EpubNavigatorFragment, or better have the EpubNavigatorFragment be able to switch between the current implementation and the RecyclerView one based on a config option.

Alright, I'm looking forward to it if you find the time to extract your implementation!
So for this, you used a RecyclerView, and the PagerSnapHelper is used when in paginated mode? For the continuous scroll, do you resize the WebViews every time the HTML height changes, and disable any scrolling directly in the web view?

So for this, you used a RecyclerView, and the PagerSnapHelper is used when in paginated mode? For the continuous scroll, do you resize the WebViews every time the HTML height changes, and disable any scrolling directly in the web view?

I'm using a plain RecyclerView. We don't support a paginated mode, just a full vertical scroll. RecyclerView items naturally expand with the contents of the WebView, it's the RecyclerView that scrolls and not the WebViews.

One more question! How do you deal with the loading time? For instance when a fling would get beyond the already loaded resources. When working on that, I felt like it would be a mess to handle this edge case.

One more question! How do you deal with the loading time? For instance when a fling would get beyond the already loaded resources. When working on that, I felt like it would be a mess to handle this edge case.

Before the WebView has loaded we show a progress bar for each chapter, and the view has some minimum fixed height. So basically once you reach a chapter that hasn't loaded yet, you can scroll through chapters very quickly, which is a bit weird, but works out well if you tapped a link to go to another chapter far away.
The good thing is that without the WebServer, chapters are loading very fast now.


Failure when matching on one specific return

If a function can return more than one type, and I match on one specific type, the check fails.
I'm not sure if this is intended behaviour, but raising here as an issue, thinking this usage should not raise any failures?
Cheers!
defmodule Gradissue do
  @spec foo(integer()) :: :ok
  def foo(x) do
    :ok = bar(x)
  end

  @spec bar(integer()) :: :ok | {:error, term()}
  defp bar(0), do: :ok
  defp bar(x), do: {:error, x}
end

❯ mix gradient
Compiling 1 file (.ex)
Typechecking files...
lib/gradissue.ex: The function call on line 4 is expected to have type :ok but it has type :ok | {:error, term()}
2   @spec foo(integer()) :: :ok
3   def foo(x) do
4     :ok = bar(x)
5   end
6

Thanks, Victor!
In this case the warning is valid, since bar spec is explicit about the possible return values, but one of them is ignored. This makes the program unsound. If the other type gets returned we'll get a runtime crash, and the type system's purpose is exactly that - to prevent runtime crashes.
If you really want to convert from an error-as-value to an exception, it has to be explicit:
defmodule Gradissue do
  @spec foo(integer()) :: :ok
  def foo(x) do
    case bar(x) do
      :ok ->
        :ok
      {:error, reason} ->
        ## given FooError is defined
        raise FooError, reason: reason
        ## or maybe just:
        ## :erlang.error(reason)
  end

  @spec bar(integer()) :: :ok | {:error, term()}
  defp bar(0), do: :ok
  defp bar(x), do: {:error, x}
end

Ahh got it, I thought matching on a subset and crashing otherwise was ok, so that's fine then. If that could be a flag haha, that would be great, but I guess that depends more on gradualizer than gradient itself?
Something I've noticed though is that using case, it's not making sure I'm considering all the paths:
defmodule Gradissue do
  @spec foo(integer()) :: :ok
  def foo(x) do
    case bar(x) do
      :ok ->
        :ok

      {:error, _} ->
         :ok
    end
  end

  @spec bar(integer()) :: :ok | {:error, term()} | {:wupwup, term()}
  defp bar(0), do: :ok
  defp bar(x) when x < 0, do: {:error, x}
  defp bar(x), do: {:wupwup, x}
end

❯ mix gradient
Compiling 1 file (.ex)
Typechecking files...
No problems found!

It passes even if I remove the {:error, _} -> clause.

Ahhh, that's interesting 🤔 What happens if you check with this instead?
  @spec bar(integer()) :: :ok | {:error, integer()} | {:wupwup, integer()}

Indeed, it's what I expected. With:
$ cat lib/gradissue.ex
defmodule Gradissue do
  @spec foo(integer()) :: :ok
  def foo(x) do
    case bar(x) do
      :ok ->
        :ok

      {:error, _} ->
         :ok
    end
  end

  @spec bar(integer()) :: :ok | {:error, integer()} | {:wupwup, integer()}
  defp bar(0), do: :ok
  defp bar(x) when x < 0, do: {:error, x}
  defp bar(x), do: {:wupwup, x}
end

We get:
$ mix gradient
Compiling 1 file (.ex)
Typechecking files...
lib/gradissue.ex: Nonexhaustive patterns on line 5
Example values which are not covered:
	{wupwup, 0}

The thing is that term() (and any() which is a synonym to term()) is the unknown type in the gradual type system. It means it's compatible with anything, which in turn means it cannot be used for exhaustiveness checking - that is figuring out whether you missed a branch or not.
In other words, if we want to rely on Nonexhaustive patterns ... warnings, our type variants cannot use term() or any().

@rodrigues I hope this is a convincing answer :) Let me know if that's not the case :D Until then, I'll close this one.


Add FPS display

Objective
Add a simple average FPS display that updates every second and a dark overlay for readability when there are many rectangles.
Motivation
I'm presuming FPS in release builds was previously being determined through some sort of external overlay or something, as FrameTimeDiagnosticsPlugin was only enabled for debug builds.
I'd like to make it easy to measure perf on every platform.

FPS in release builds was previously being determined through some sort of external overlay

Ahhhhhhh-or-be-super-lazy-and-move-the-two-lines-out-of-the-if-statement-each-time-chooooo! What? No I didn't say anything :innocent:.
Anyway, this is much nicer, thank you lol.

Removed the TODO b/c we'll still need a container for the background color + formatted the code the way I like.

we'll still need a container for the background color

Actually, TextBundle can have a background_color now, but padding doesn't work.
Sounds good though.

Oh neat, added it back then: https://github.com/SUPERCILEX/bevy-vs-pixi/commit/cb336168981cbab8475d58395792ab3261c16cd9


Bluetooth: Mesh: Fix NULL pointer access with GATT Proxy

The conversion to the new net_buf_simple API was done incorrectly
here. The buffer initialization should use net_buf_simple_init()
instead of net_buf_simple_reset(), so that buf->__buf gets properly
initialized (and not left pointing at NULL).
Signed-off-by: Johan Hedberg<EMAIL_ADDRESS>

Codecov Report

Merging #6173 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #6173   +/-   ##
=======================================
  Coverage   52.86%   52.86%
=======================================
  Files         412      412
  Lines       40284    40284
  Branches     7802     7802
=======================================
  Hits        21296    21296
  Misses      15773    15773
  Partials     3215     3215

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 4c123a5...585ef54. Read the comment docs.


Lag when transition to another page

when the page changes the transitions become laggy, I found out that it is laggy because of an API call. The transition is getting blocked when calling the API. How do I avoid this problem?

hi @aibrahim3546! this is something that will have a clearer path forward in the future, when async react is a reality. in the meantime, i'm not certain how or when you're making an api call, but deferring it or prefetching it should work well enough. if you're fetching in the componentDidMount of a transitioning component, i would expect there to be a lag. maybe give deferring the call or prefetching it a try.

Thank you for the response, So I guess the only way is to delay the API call.

@aibrahim3546 no problem–i might give requestIdleCallback a shot here, if you have it shimmed.


Add support for viewing/editing 7zip SFX archives

What's the Problem?
7zip offers to compress as an SFX archives which show as .exe file (it's just a .7z file and mini extraction program) but Files doesnt support viewing and editing the contents.

Solution/Idea
Add a right click option to view archive.
Alternatives

Priorities
No response
Files Version
No response
Windows Version
No response
Comments
No response

Is there any way to detect that it's an archive? We're able to detect 7z files based on the extension but that won't work for exe files.

Not sure. I dont know how there internally structured, but the archive itself should just be a .7z file not sure if it can be read.
There is also meta data in properties > details, it has a file version and a copyright added to it from 7zip that could mabey be used.


Is the license valid?

See https://news.ycombinator.com/item?id=10277207

Duplicate, sorry.

No problem!
Other issue was here: https://github.com/delight-im/FreeGeoDB/issues/1
And we should switch to a license that fits better than Apache 2.0: https://github.com/delight-im/FreeGeoDB/issues/9


Support for Brazilian holidays

I need to provide unit test coverage for this, but I opened the PR already to keep track of it!
Thanks for the module!

Thank you very much.. I'll be merging your work when you're done!
Cheers

Hey @dr-prodigy. Just finished unit tests for this PR. Can you check if it needs any other work.
Thank you!

Very good work: I just had to update some documentation, then I merged everything to beta branch (will be released pretty soon).
Thank you very much, cheers!

Oh, I forgot about the docs, sorry!
I should thank you for the module it is very helpful.
Glad I could contribute!

Python_holidays grows up and gets better daily mainly due to your contributions.. So I thank you very much for your support and help!
Cheers


Link to Java/Karate framework for ACP tests

@edwardsph what do you think?

we will be providing test cases for any of the specifications that we implement in ESS. They will also be used by CSS.

Please don't do this Emmet. I am begging you. It's not good for Solid as a whole in general if one of the companies from the eco-system attacks our independent test suite. Granted, Inrupt is a particularly big company and obviously a great benefactor of Solid, contributing many resources and engineer hours to the improvement of Solid. But that doesn't give you the right to behave this way. The meeting that Sarven called on Monday, where we were all present, and the proposed plan to move forward, which Yvo subsequently posted in https://gitter.im/solid/test-suite?at=603cf692120cd84f78e81d76, were our last attempt to de-escalate the situation.
I'm begging you one last time, please back down, please, let's merge this proposal, so that Pete can work on the ACP tests, using whichever programming language and DSL and framework he prefers, and we don't question the validity of our existing WebID-provider, CRUD, and WAC tests.

It is quite likely we will add some more example test cases (alongside the ones that already exist) to show how people could create ACP tests whilst we also look at other capabilities the harness needs to provide. However our priorities at the moment include work on the architecture of the whole harness, the test description documents and the reporting elements.

By all means, work on your framework and use it in your own development cycle internally.
Just don't compete with the EXISTING independent Solid test suite for WebID, CRUD, and WAC. So don't publish the results of your internal tests as some sort of "competing truth" about which server correctly implements the spec.
We already have the results for 4 out of 5 implementations (TrinPod coming soon), and I've been told engineers are working as we speak to fix the last few failing tests in their respective servers, so all servers will soon be 100% green on WebID, CRUD and WAC. Don't ruin that, please.
This PR is to propose that we use your framework for the ACP tests ONLY. There is no competition there, because ACP is not covered yet and I don't think any other panel members are writing them yet, so that's a win-win.
There, Inrupt could really contribute to the Solid test suite!

We will be ensuring that the test cases are reviewed and formally signed off by the relevant members of the specification team.

I understand your best intentions, but please don't give them more work. They're already swamped and unable to attend to https://github.com/solid/solid-crud-tests/issues/46 and https://github.com/solid/web-access-control-tests/issues/34 as (understandably!) @csarven told me yesterday. Adding a competing test suite and more lists of disputed tests will only bog us down further. We need to one day arrive at a spec with zero disputed issues, where all servers behave in the same way, and all servers pass the same test suite.
Let's focus on what we have, improve it, add your ACP tests to it, and try to keep working peacefully alongside each other! <3

swamped and unable to attend

The disputes you've put together are really useful, and thanks again for that work! I would like to get a chance to respond. Part of that requires us to process the available information and write things up.
I'd also like to better understand the type and causes of disputes eg. are there different interpretations (or preferences) on functionality and why? can we verify the test results? How can we improve from here?

@michielbdejong The work you’re doing in the independent test suite is valuable to both specification editors and server implementers alike.   You’ve requested I intervene.
In that regard, I’d like to make clear that neither I, the Spec Editors, nor the Solid Admin team have endorsed or designated any “Official test suite” or set of test suites for the Solid Specification. While such guidance certainly may occur in the future, at this time no such decision has been made.
It’s an open community and positive contributions from all parties are welcome. That is why it is a valuable and positive thing for the ecosystem to encourage broad test suite development and innovation.  At the moment, there are two test suites for Solid.
Just as how multiple server implementations help to inform and fill in gaps in the specification, multiple test suites help uncover ambiguities in the specification that otherwise go undetected or have defaulted to the interpretation of one suite. A difference in test results can serve to highlight clarifications needed in the spec or bugs in a test suite.
While it’s possible that test suites sometimes consolidate or merge, I expect server implementations want to run against multiple test suites to ensure spec compliance and interoperability (especially where parts of the spec are in draft and being finalized).
I hope this explains why we will move forward better together with test suites coexisting to provide even more value to the Solid ecosystem.
Thanks

OK, I can see the point in that. So we'll just have multiple overlapping test suites then, and only the spec itself will be unique. Thanks!


c_predict_api BUG in new mxnet version.

One of my project(using MXPredForward of c_predict_api on CPU context) consumes 940MB memory when running on the version on about Oct 30,2017, but on the 0.12.0(Release) version (or versions after that) It consumes up to maximum 9GB memory. I have tested it in two computers and both occur. So I think there is a bug after Oct 30,2017.

It's the BUG with MKL2018 when set USE_MKL_IF_AVALIABLE is on.


python312Packages.python-whois: 0.8.0 -> 0.9.3

Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 299951 run on x86_64-linux 1

6 packages built:

offensive-azure
offensive-azure.dist
python311Packages.python-whois
python311Packages.python-whois.dist
python312Packages.python-whois
python312Packages.python-whois.dist


Hugging Face

Hi,
This looks really cool! Do you think it's possible to mirror the models to the Hugging Face Hub for faster downloads?
Thanks!

We will open a HF space. Working on that

Sorry, I was referring to hosting the models there

Got it. Let me talk to my team

Hi @Zengyi-Qin, I'm Yoach, ML Engineer at Hugging Face, nice to meet you!
Congrats on the release ! The models are definitely of great quality!
I'd be happy to help you set up the model weights on the Hub! In addition to being hosted directly on the Hub, this will also help facilitate the discovery of your models and allow you to add model cards to describe them.
The first step would probably be to create one repo on the HUB per model here.
You can then get inspiration from what audiocraft did here to load checkpoints / configs in the most efficient way!
Let me know if I can be of any help! Happy to discuss OpenVoice integration as well!

Hey Yoach! Let's talk via slack


Deprecation notice when using class .language-*

Node - 16.13.0
HighlightJS - 11.3.1
PostHTML - 0.16.5
posthtml-highlight - 1.1.2
I really appreciate you creating this plugin and have been using it with Parcel v2 using a simple .posthtmlrc which is as follows:
{
    "plugins": {
        "posthtml-highlight": {
            "inline": true
        }
    }
}

This allows me ship highlighted code-blocks in my website without shipping hljs with it however in areas where the highlighting isn't working properly, I add the language specific classes like .language-cpp to the <code> element which invariably leads to this notice on build-time which I do not get when they are removed.
console: Deprecated as of 10.7.0. highlight(lang, code, ...args) has been deprecated.
console: Deprecated as of 10.7.0. Please use highlight(code, options) instead.
https://github.com/highlightjs/highlight.js/issues/2277

Even though the src/index.ts of this project suggests that this notice shouldn't be shown, I could be wrong in my superficial reading of the code. I'm just bringing this to your notice to test out.
Cheers

oops, latest version didn't get published to npm.
You should now be able to upgrade to posthtml-highlight 3.0.0 and resolve this warning. Breaking changes between 1.1.2 and 3.0.0 are in CHANGELOG.md, but for convenience:

dropped support for Node <10
highlightjs language aliases changed upstream (https://github.com/highlightjs/highlight.js/blob/main/VERSION_11_UPGRADE.md)


Add docs on SSL especially certificate pinning

Note: We need to tell developers that we support TLSv1.2/1.3 and will never support 1.1/1.0