Deprecation of DSDL definitions

Split out the deprecation discussion into this thread (why do we always seem to wander off topic)
The state of the discussion when split up
Pavel:

I have added a @deprecated keyword to the current draft a couple of weeks ago; it's supposed to be translated into language-specific deprecation markers, e.g. [[deprecated]] in C++ or DeprecationWarning in Python.

Kjetil:

How do we express deprecation?

Let's address this concern before moving on to the bigger concerns.

I have added a @deprecated keyword to the current draft a couple of weeks ago; it's supposed to be translated into language-specific deprecation markers, e.g. [[deprecated]] in C++ or DeprecationWarning in Python.

That's nice. I was playing around with a similar idea myself. What i was thinking about was adding
@lifecycle <pre-release|released|deprecated|removed>, this way we can add a new type without releasing it, yank a buggy type and deprecate old types. This is how i vision it would work.

Pre-realease - do not generate code for this definition unless some dangerous keyword is presented.
Released - As normal (as it currently works)
Deprecated - Issue a warning that the type is deprecated and will be removed in the future.
Removed - Issue an error that this type has been through the deprecation process and is no longer usable.

Even if we initially only supported deprecated It would allow us to add other lifecycle items (like removed) later on without making a new directive. Both our solutions would of course require the directive related to deprecated to be an exception to the immutability guarantees together with comments and whitespaces (which is of course totally fine).

Pavel:

I like the flexibility argument, but I have two questions:

What's the point of the removed option if the definition can be just physically removed to the same effect?
pre-release goes against the versioning guarantees that once something is published it can't be removed or changed without a proper deprecation process. If you want tentative volatile definitions, use version 0. I think we can make this work but that would be at the cost of extra complexity in the specification, so I am against it.

If the two options mentioned above are removed, we're back to just deprecated and released. I think the meaning of the keyword @lifecycle might be slightly less transparent than @deprecated, i.e. somebody who is not familiar with the UAVCAN specification might fail to understand what it means; @deprecated seems more approachable. Also, most published data type definitions will be in the release stage, meaning that it would make sense to assume release by default if not specified, so @lifecycle release becomes redundant.
I suggest keeping @deprecated.

What's the point of the removed option if the definition can be just physically removed to the same effect?

The main idea was to give information about potential DTID/name/path conflicts for future definitions while failing users of the definition to compile. We should probably at least keep this element out of the mix until we can see what the dsdl checker ends up doing in a bit more detail.

pre-release goes against the versioning guarantees that once something is published it can't be removed or changed without a proper deprecation process. If you want tentative volatile definitions, use version 0. I think we can make this work but that would be at the cost of extra complexity in the specification, so I am against it.

Well my intention was to not consider it "published" before it reached released. The pre-release was meant as a way for early testers to evaluate 2.0 definitions and the like before released.
It's actually a bit different than 0.x definitions for a few reasons:

It's quite more dangerous since it may conflict with released stable versions. This would need to make it very hard  to enable by mistake.
It should be thought more of as a way to develop the type replacing the current.
It can be used with "stable" types
It can even be used with 0.x types to

My counter proposal would be to use @lifecycle <released|deprecated> with an implicit default to @lifecycle deprecated. This would allow most people not to think about it while allowing us to add more stages at a later point.
With that said I also totally accept @deprecated. We should in any case leave this issue open for a week or two in case someone else wants to bikeshed this further (Hey! perhaps @deprecated should be an alias for @lifecycle release :laughing: ). I won't object to you closing this thread with the decision you're in favor for when you feel it has cooked long enough, unless you want to discuss it further.

The main idea was to give information about potential DTID/name/path conflicts for future definitions while failing users of the definition to compile. We should probably at least keep this element out of the mix until we can see what the dsdl checker ends up doing in a bit more detail.

I would like to propose a general principle we should follow: one should get a full understanding of the current DSDL set just by looking at the list of files in the DSDL namespace directory, without having to look inside the files. That would rule out things like @lifecycle removed and @lifecycle pre-release.
Specifically, I don't think that @lifecycle removed is necessary because by the time the data type is removed it has already been deprecated for at least two years, giving users supposedly sufficient time to upgrade their systems and move away from it. That means that by the time it is physically removed, its DTID can be safely repurposed immediately.
As for @lifecycle pre-release - I see the value, but again I'm not sure whether the added complexity would be worth it. As an alternative, we could explore lifting the compatibility guarantees from data type definitions where the minor version number is 0.
I think that we should strive to keep definitions as clean and simple as we can. That means that the most commonly used state shall also be the default state. Otherwise, we'll end up with boilerplate code, requiring virtually every definition to contain @lifecycle released. I am very much against that.
I suggest accepting @deprecated, released-by-default, and keeping in mind the possibility of adding new directives in the future.

Looks like have a consensus here
I am curious what's your take on this:

As an alternative, we could explore lifting the compatibility guarantees from data type definitions where the minor version number is 0.

I don't think this is a good idea. It goes against what users will expect when it comes to versioning.

Okay. Do we consider this one resolved?

[ ] @pavel-kirienko
[ ] @kjetilkjeka
[ ] @thirtytwobits


SPIKE: Cosmos Staking Module

Staking abstraction module? (similar enough to support both cosmos chains and yearn?, separate implementations?). Provides logic to build a delegate/undelegate/etc transaction in the same way buildSendTransaction works in ChainAdapters. These payloads are then passed to signTx in ChainAdapters.
Single sided staking abstraction?
Look at Yearn and other single sided use cases and see if it is worthwhile. Could Single sided handle Yearn, Fox Farming, and Cosmos? Less web code and complexity.
https://twitter.com/joey__santoro/status/1478489634300588032
Acceptance Criteria:
Create the API specification for how the web front end would call this module. The spec should be able to handle single-sided staking for cosmos, yearn, and FOXy. Something similar to this for unchained. But it shouldn't be a .ts file, can just be markdown: https://github.com/shapeshift/lib/blob/main/packages/chain-adapters/src/api.ts
Consider this only at the lib layer, unchained will handle a lot of the abstraction. Work with Adam on what belongs where exactly.

Vault/Validator

Does an asset support staking / vaults?
Find out if they are staked and what their staked balance / unstaking in progress balance/time

Per ASSET, not per account

Get APR for each staking opportunity
Get transaction / gas fee
Does the staking opportunity have an unbonding period (typically in days)
Stake / Unstake
Available balance in terms of the crypto asset (plus fiat value)
Destination / Address (validator / vault) - display name / address
Get Available Destinations
Sign / Broadcast / get TXID
Typed Errors
Rewards -

claimable Pending Rewards - show claim button
auto-compounding rewards / rebasing - don't show rewards at all?

Unstaking

sometimes unstaking will claim your rewards

Does the opportunity require approval / is it already approved?

Lending

Supply / Borrow
Various protocols (compound, rari, etc)
Supply - enable as collateral (not all protocols support this)
Rewards in "n" assets (1 or 2 usually) - not necessarily the same asset

APR (per asset, blended?)

Affiliate revenue ?

import BigNumber from 'bignumber.js'

export interface SingleSidedStakingOpportunity {
  id: string
  displayName: string
  displayIcon?: string // URL?
  assetId: string // CAIP19
  address: string
  apr: BigNumber // where 1 = 100%
  commission: BigNumber // 0-1 where 1 = 100%
  tvl: BigNumber // current balance of the vault/validator
  deposit: (amount: BigNumber) => Promise<unknown>
}

export interface SingleSidedStakingPosition {
  id: string
  opportunityId: string
  apr: BigNumber // where 1 = 100%
  assetId: string // CAIP19
  balance: {
    crypto: BigNumber
    fiat: BigNumber // USD?
  }
  createdAt: Date
  costBasis: BigNumber // crypto amount
  findPendingRewards: () => Promise<SingleSidedStakingReward[]>
  deposit: (amount: BigNumber) => Promise<unknown>
  withdraw: (amount: BigNumber) => Promise<unknown>
}

export interface SingleSidedStakingReward {
  positionId: string
  balance: {
    claimable?: BigNumber
    unclaimable?: BigNumber
    lifetime?: BigNumber
  }
  assetId: string // CAIP10
  claim: () => Promise<unknown>
}

export interface SingleSidedStaking {
  findActivePositions: () => Promise<SingleSidedStakingPosition[]>
  findOpportunities: () => Promise<SingleSidedStakingOpportunity[]>
}

closing per @asamere based on web architecture conversations from ~2/18


If I have a hectic job how do I find the time to learn outside it?

How do you separate time from work to learn. I always find myself working on my job tasks and yes i work on weekends and even after working hours. Because of this i find very less time to attend meetups or learn concepts. yes the office work i do is interesting, but they want me to complete as fast a i can. Please guide me what should i do

Don't work too much. You need to give relaxed timelines. If the job forces you to do it, talk to your manager and make him understand that your relaxation and self learning is important as well. If things persist, I would advise you to find another job. Even if it is low paying, your per hour rate would be more and you should work towards increasing it even more.
Say you work 80 hours .a week at $10 per hour, all you're making is $800
If you work for 50 hours a week at $20 per hour, you would be making $1000.
The key to getting rich is more money per hour and to do that you need time to learn.


Entity: userdefined predefined type returns an error

IDS-Audit-tool reports this error:
Error 103: Invalid value "X" to match "PredefinedTypes" (no valid values exist) in the context of Ifc2x3, Ifc4 on "simpleValue at line 22, position 26
with this ids:
<ids xmlns="http://standards.buildingsmart.org/IDS"
    xmlns:xs="http://www.w3.org/2001/XMLSchema"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://standards.buildingsmart.org/IDS http://standards.buildingsmart.org/IDS/ids_09.xsd">
    <info>
        <title>Inherited predefined types should pass</title>
    </info>
    <specifications>
        <specification name="Inherited predefined types should pass" ifcVersion="IFC2X3 IFC4" minOccurs="1" maxOccurs="unbounded">
            <applicability>
                <entity>
                    <name>
                        <simpleValue>IFCWALL</simpleValue>
                    </name>
                </entity>
            </applicability>
            <requirements>
                <entity>
                    <name>
                        <simpleValue>IFCWALL</simpleValue>
                    </name>
                    <predefinedType>
                        <simpleValue>X</simpleValue>
                    </predefinedType>
                </entity>
            </requirements>
        </specification>
    </specifications>
</ids>

IDS test case: [PASS] Inherited predefined types should pass
The IDS element "predefinedType" contains either a predefinedType (defined by ifc) or an objectType ("X" in this case when USERDEFINED).

That's a correct observation, when USERDEFINED exists in the enumeration I should skip the check.

Solved in a previous commit 27223f7607e9298e1300d621d12026bf608f0bb7


Controller should store rules as K8S third party resource objects

Today, the controller is using redis as its backend datastore for storing the rules. It needs to store the rules into K8S as third party resources (http://kubernetes.io/docs/user-guide/thirdpartyresources/) which is backed by etcd. This relieves the dependency on redis, for Kubernetes deployments.

completed by #451


Linux: Installation process needs an additional step

Attempted to run a fresh install of nostr_startr on a Linux distro
Following the readme.md file I realise it is missing a step to add the executable permission to the nostr_console that has been downloaded by the python script.
I doubt this can be done within the .py as it is a permission escalation at the system level. The command is listed in the update process further down chmod +x "nostr_console_binary_file" and it is an intuitive to linux power users but maybe not by all.
Suggestion Adding a step or separate process in the install for linux users in readme.md where they need to download the nostr_console zip for their architecture nd make it executable before someone starts nostr_startr for the first time, to avoid program crash as I experienced today.

As long as the user running startr is the owner of the downloaded file (nostr_console_file) no privilege escalation is needed to make it executable.
At this point startr allows you to install and give execution permissions to nostr_console automatically when it does not detect any nostr_cosole binaries. Even if you select to launch nostr_console without having previously downloaded nostr_console, also the install/update nostr_console option in the menu does this.
However, you made me realise that it would be good to include u+x to the chmod statement in startr to avoid conflicts in more permission-limiting environments and only give execution permissions to the current executing user and not to everyone (a+x vs u+x).
This way the additional step in the installation process is not necessary, however I will include it as an optional step.


loggerd: extract write_encode_data  and eliminate recursion from handle_encoder_msg

Changes:

Refactored handle_encoder_msg: Moved the encoding packet writing logic to a new function, write_encode_data, improving code clarity and separation of concerns while preserving the existing writing behavior.
Eliminated Recursive Calls: Replaced recursive calls within handle_encoder_msg with direct calls to write_encode_data for writing queued packets in the new segment. This change prevents potential crashes by handling queued packets safely, even if they are out of sync with the encoderd.
Improved Memory Management: Replaced raw pointers with std::unique_ptr for managing Message objects, improving memory safety.
Removed Redundant Parameter: Removed the service.name parameter from handle_encoder_msg, as it duplicates the re.publish_name value already available through the re parameter.

Resolves  #28857

This PR was closed because of a git history rewrite.
Please read https://github.com/commaai/openpilot/issues/33399 for what to do with your fork and your PRs.


Add approving currencies to exchanges

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 3 (0.0%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage remained the same at 0.0%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

contracts/ExchangeProxy.sol
0
3
0.0%

Files with Coverage Reduction
New Missed Lines
%

contracts/ExchangeProxy.sol
1
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
0

Relevant Lines:
710

💛  - Coveralls


[QUESTION] What's the best way to log request body?

[x] I've read the docs of nestjs-pino
[x] I've read the docs of pino and pino-http
[x] I couldn't find the same question about nestjs-pino
[x] This is not a question about how to use this library with pino-transport-name-goes-here

Question
I have a bunch of webhook endpoints and I want to log their bodies. What are my options? I saw https://github.com/pinojs/pino-http/issues/37 but I don't know how this applies to nest.
Please mention other relevant information such as Node.js version and Operating System.
Our main.ts:
import { NestFactory } from '@nestjs/core'
import { AppModule } from './app.module'
import { Logger, LoggerErrorInterceptor } from 'nestjs-pino'

async function bootstrap() {
  const app = await NestFactory.create(AppModule, { cors: true })
  app.useLogger(app.get(Logger))
  app.setGlobalPrefix('v2')
  app.useGlobalInterceptors(new LoggerErrorInterceptor())
  await app.listen(3000)
}
void bootstrap()

nevermind. I found the answer in the readme. hiding with embarrassment


Work around a race condition with ScriptServer during initialization

Split off from #73793
Currently, WorkerThreadPool is initialized before ScriptServer, so there's a race condition where worker threads call into ScriptServer::thread_enter() before languages are registered. Since ScriptServer isn't always initialized (for example, when Godot is run with --help), there's no synchronization point where threads can wait for languages to be registered before proceeding, so we just disable it for now.
The proper fix is of course to rearrange main() so that threads and WorkerThreadPool are initialized last, which should probably wait until after #49362 (or possibly even be done there). This can be reverted afterwards.
Needed for ThreadSanitizer #73777

Closing in favor of https://github.com/godotengine/godot/pull/76586#issuecomment-1600455334


useDefineForClassFields breaks augmentation/overwrite of class members with decorators

TypeScript Version:  3.8.0-dev.20191113
Search Terms:
decorators, useDefineForClassFields, useDefineForClassFields decorators bug
Code
function Decorator() {
    return function (target, propKey, descriptor) {
        const symbol = Symbol();
        target.constructor.prototype[symbol] = descriptor ? typeof descriptor.initializer !== 'undefined' ? descriptor.initializer() : undefined : undefined;
        return {
            configurable: true,
            enumerable: true,
            set(value) {
                this[symbol] = value;
            },
            get() {
                return this[symbol] + 'decorated';
            }
        }
    }
}

class TestTSDefine {
    @Decorator()
    myProp = "test";
}

console.log(new TestTSDefine().myProp);

Expected behavior:
output should be 'testdecorated'
Actual behavior:
output is 'test'
Use the same code with "useDefineForClassFields = false"
output is the expected 'testdecorated'
with babel (also [[Define]] behaviour) everything works.
Playground Link: http://www.typescriptlang.org/play/?useDefineForClassFields=true&experimentalDecorators=true&ssl=1&ssc=1&pln=23&pc=40#code/GYVwdgxgLglg9mABAEQKYTgJwIZSwCgEpEBvAKEUsU1ShEyVElgUXym0wHNaAaRAA6Y4AgNKoAnvwAmqAM4RMMAXkzFyVTYgxg5URHIkBbAEZwANogC8iAMrGz5ogG4KWyh260AdDr2YQaCxvITg8KAkBVABtQ1MLAF1rRFkFJRUsRAB+RAiouGAU+UVlVW8YMBhYbHMYAC9UTEQAQisbAHJwWWAK1Gl27KK00uCKqpga+saiRAAuRC7UHrA+uYWwbt7pV3dKGjoGUjddqh0ernpsE3NUeagA1F5jk8RUMBAjRqubu4enl6oclo+AAbjUQKh1M8AR4ABYwOSxByJZJg8wQnYwgC+-xhPCgMw0MM0+3oSCg8MRcUcSQA1Ih2rIMDgoH12piAVjoVQuZouVyyBBzNg5HJEAAVeRQcW2NDLVBHTQAATQzNwBEIzyMEgACsIBMkAESsvSG1wCvwWVDecxwLj4FYAdwlUplct6RG82r1IkIziAA
** Repository to reproduce with Babel and Typescript **: https://github.com/mzeiher/decorator-ts-define-bug (see README)

Regarding this bug, it would be nice if the typescript team could align the implementation for decorators and define semantics for fields to the current babel implementation (legacy mode) this would make a lot of things much easier especially for framework developers who ship decorator libraries (currently I'm detecting and testing TS legacy, Babel Legacy and the Babel Stage 2 implementation) a 4th decorator flavor makes it just harder to maintain (yes I know decorators are highly experimental ;))
one thing regarding inheritance, currently the useDefineForClassFields just overrides the property descriptor of super (defines a new one on the instance), it would be nicer if something like the babel helper could be used: this will just update the value but leave a possibly augmented (by a decorator or manual) intact (just the initalizer value is overridden)
function _defineProperty(obj, key, value) { if (key in obj) { Object.defineProperty(obj, key, { value: value, enumerable: true, configurable: true, writable: true }); } else { obj[key] = value; } return obj; }

In relation to replacing a class field/property/method - following code works on existing implementations of decorators with exception of TypeScript fields when using useDefineForClassFields. Unfortunately this is breaking without workaround. If fully aligning implementation with either babels "modern" or "legacy" decorators is too much work, perhaps consider implementing #29299 Option to disable decorator transform instead and let people further transform them themselves.

Fields
Properties
Methods

Babel "modern"
✅
✅
✅

Babel "legacy"
✅
✅
✅

TypeScript (without "useDefineForClassFields")
✅
✅
✅

TypeScript (with "useDefineForClassFields")
⛔
✅
✅

Code here:
Gist
TypeScript playground
Babel repl

Ay updates here? We're increasingly seeing users complain that their components are broken because of this issue, and the symptom is very hard to track back to this unless you already know about it.
For some reason many tools that integrate the TypeScript compiler are enabling useDefineForClassFields and some of them don't give users control of the config, so there's no good workaround (except to delete own properties which puts objects into dictionary mode).

We're still seeing this in TypeScript 4.0.3. It breaks the Aurelia framework, which is blocking us from using a library that requires useDefineForClassFields.

I just ran into this because this seems to mean that it's not possible to use MobX decorators and lit-element decorators together with TypeScript. MobX decorators seem to require "useDefineForClassFields": true but that breaks lit-element decorators (like @property and @query).

This isn't a bug, but rather the expected behavior. It is unfortunate, but is a consequence of several interactions:

--useDefineForClassFields mimics the proposed behavior of ECMAScript fields.
The proposed behavior for ECMAScript fields is that they are defined in the constructor (i.e., using Object.defineProperty).
Defining a field on an instance means that a prototype walk will not occur, so the get/set you are defining on the prototype will never occur.
Defining a field does not trigger setters.
Even declaring a field like myProp: string; with --useDefineForClassFields will result in a new field definition on the instance that will shadow the prototype.

We introduced declare fields in TS specifically for this reason:
function Decorator() {
    return function (target, propKey, descriptor) {
        const symbol = Symbol();
        target.constructor.prototype[symbol] = descriptor ? typeof descriptor.initializer !== 'undefined' ? descriptor.initializer() : undefined : undefined;
        return {
            configurable: true,
            enumerable: true,
            set(value) {
                this[symbol] = value;
            },
            get() {
                return this[symbol] + 'decorated';
            }
        }
    }
}

class TestTSDefine {
    @Decorator()
    declare myProp: string; // does not result in redefinition
//  ^^^^^^^
    constructor() {
        this.myProp = "test"; // initializer must be moved to constructor
    };
}

console.log(new TestTSDefine().myProp);

Playground Link

Babel's decorators support permits two things TypeScript never has:

Decorating a "descriptor" for a field.
A decorator can intercept the initializer of a field descriptor.

These were part of an early draft for stage-2 decorators that has since been abandoned. Implementing this would be a major change for TypeScript decorators, a feature which is essentially "frozen" until a stable decorators proposal reaches Stage 3 in TC39.
Changing the behavior of decorators is out of scope, and changing the field definition semantics in --useDefineForClassFields to be incompatible with the ECMAScript fields proposal is also out of scope.
Until a stable decorators proposal reaches consensus, we don't intend to make any substantial changes to our decorators implementation. It may not be much, but we added declare fields as an alternative to further complicating the decorator landscape.

The problem here is that some toolchains set this compiler flag and it breaks existing decorator usage. Previously, decorators could assume that they could define accessors and they would work. I think it would be reasonable to automatically use set semantics for decorated fields to keep them working even in the presence of this flag.


Admin API and arrays

We support sending arrays with an explicit array index param[1]=v1&param[2]=v2. We should also support adding arrays without an index in the form of param[]=v1&param[]=v2.
Evaluate removing the comma separator in favor of arrays.

I don't see why we would drop the comma separated way of passing arrays. It would be a breaking change.
Instead we should advocate the array way of doing things, but not breaking the comma separated ones.

the underlying problem is fixed in #1399.

The way I see it, the comma separation is just a non-elegant solution to a problem that can be already fixed with form-encoded arrays using square brackets.

Hmmm... do we want to break backward compatibility because on non-elegance?

Addressed in the new Admin API - entities are now slowly migrating there.


Dependency on private repository

We currently depends on github.com/neticdk/go-common which is private, meaning this repository can not be build if your not part of the neticdk organization.

As I understand it this about being able to package the command line? I think maybe we should create a gh action that triggers on the creation of new releases and build binaries for arm and amd64 for downloads. That would eliminate the need to know the magic of private go modules (and having a token in git "keychain")

not really, I'm trying to create a Nix deriviation to install ic and Nix doesn't really play nice with private repositories. I will try to workaround the issue, but it is a bit of a nuance that you can't build from source.


support image pull secrets

Signed-off-by: mahao<EMAIL_ADDRESS>
Ⅰ. Describe what this PR does
support image pull secrets
Ⅱ. Does this pull request fix one issue?

#2037

hi @cheyang @yangyuliufeng   please review whether we plan to support Image Pull Secret
If yes, is it reasonable to set a global set of Image pull secret ?
because fluid contains a lot of images
this is applicable in our scenario because we have unified registry of images

hi @cheyang @yangyuliufeng please review whether we plan to support Image Pull Secret If yes, is it reasonable to set a global set of Image pull secret ?
because fluid contains a lot of images
this is applicable in our scenario because we have unified registry of images

I think it's reasonable to support image pull secret in global.


Add Metadata poll timer metric

Fixes #46 and #49

@seglo I am not really sure how to write tests for this scenario. Do you have any suggestion ?

Thanks a lot for working on this @anbarasantr.  I took a quick look.  The ideal way to test this would be to use the Akka typed testkit in ConsumerGroupCollectorSpec where the metric is reported.  You may need to modify ConsumerGroupCollector to accept a custom java.time clock in order to control time correctly.
You could also add this to an existing or new integration test in IntegrationSpec by asserting that the metric exists and has some valid value.


Invalid config for [sensor.mqtt]: value is not allowed for dictionary value @ data[‘device_class’]. Got ‘motion’. (See ?, line ?). Please check the docs at https://home-assistant.io/components/sensor.mqtt/

Just upgraded to 0.69.1 (finally as Ubuntu 18.04 is now out and using new python)
but seem to be getting this error and my motion sensors are not showing up.
Invalid config for [sensor.mqtt]: value is not allowed for dictionary value @ data[‘device_class’]. Got ‘motion’. (See ?, line ?). Please check the docs at https://home-assistant.io/components/sensor.mqtt/

fixed, for some reason i had
device_class: motion
set in the yaml config.


Fixed the external.invoke by @pierredavidbelanger

Fixes #19

@pierredavidbelanger Hello. First of all I'm sorry for all the mess.
Since the maintainer of the original repo is 2 years absent, I'm trying to accept community contributions here and have them released automatically.
I finally ironed out most of the GitHub Workflows kinks to publish built releases upon PR merge commits.
I'm ready to investigate you contribution now.
In the original PR I said something about hardcoding an OS and that was wrong of me — seems I confused some of your changes with parts of another PRs changes by another person.
I wanna try building your latest change, but before I do that, can you confirm that the latest build in the releases section still has an issue to fix? Give me a signoff and I'll merge this PR here to trigger a build for testing whether your change fixes it for all platforms.

Oh! Nice of you of resurecting this tool. Ill help.
As soon as I have a couple minute in front of the PC ill try your latest release.
Then I will clone your fork instead of the upstream version so I can tryt to help, it will not be much though, I have no clue about what i am doing when working with Rust yet.

Your fix branch is already part of this here PR, so you don't really have to re-fork necessarily.
I realized I accidentally made it package extra crud from the compilation directory along with the executable with the release. Afraid of touching the build script right now, during this PR. Hopefully that's not a problem. You can discard everything aside from the executable.

Ok, I can confirm , your latest build for linux throws a lot of javascript error, and also has no widgets in the UI

I may be worth to note, I am starting the app with custom gamelog and soundpack options (both paths exists):
./soundsense-rs -l ../thelongnight/gamelog.txt -p packs

That's how it was on the original repo, I have to assume.
Well, let's try merging now. A new release should be posted in about 10 minutes or less.

Gosh. Something went wrong with the workflow run.
I'm very sorry. Need to understand how to fix that first in order to be able to build a release.

I think the permissions are restricted for fork PRs.
I could only test the build script with my own PRs so far.

Couldn't really re-run the workflow after changing its permissions on this already merged PR.
Triggered a release with another bogus PR.
Time to test the new binaries.

Seems to work fine on Windows here.

By the way… 😅

I have no clue about what i am doing when working with Rust yet.

Me neither!
I'm not actually getting into developing this project but just want to maintain it in order to allow community contributions — like yours.
Don't even have the Rust development environment set up locally. That should explain why I'm relying on remote building so much.

Had my friend @Elerphore test on Ubuntu 22.04.1 LTS x86_64 and he reported no issues.
Playback functions. Sliders slide. No errors in the log.


CRF is broken with Theano backend

With Theano (git version 8f3f254 due to compiler issues) the CRF layer is broken. Unfortunately I am unable to test this with the current stable Theano. Theano git runs other recurrent models without problems.
% python conll2000_chunking_crf.py
Using Theano backend.
[...]
Epoch 1/10
8936/8936 [==============================] - 15s - loss: nan - viterbi_acc: 0.0098 - val_loss: nan - val_viterbi_acc: 0.0093
Epoch 2/10
8936/8936 [==============================] - 15s - loss: nan - viterbi_acc: 0.0098 - val_loss: nan - val_viterbi_acc: 0.0093
[...]

With the TensorFlow backend, the example runs perfectly on my machine.

Can confirm, same on my machine

@joelkuiper Which Theano version are you using?

The problem is also there with Theano-rel-0.10.0beta1.

Yup ! I also confirm!

I met the same problem with Keras 2.1.5 and Theano 1.0.1 on Win10.

I have the same problem with keras 2.1.5 and theano 1.0.1 on ubuntu 16.


Change print statements to logging

Currently printing when loading/saving data, should instead use the logging module.

I don't think there's any more of these left.


Migrate build to JUnit5 Vintage engine

As the prerequisite of dogfooding distributed test.

@bot-gradle test this

OK, I've already triggered ReadyForMerge build for you.

@bot-gradle test RFN

OK, I've already triggered ReadyForNightly build for you.

@bot-gradle test RFN

OK, I've already triggered ReadyForNightly build for you.

I manually compared tests executed by Vintage engine and old JUnit 4 engine, no issues found.


SSLHandshakeException

I'm seeing the same issue as https://github.com/square/okhttp/issues/1582 when connecting to https://jet.com. All devices are accessing the internet through the same wifi connection.
05-11 16:31:12.465    5977-6080/com.jet.jet.staging D/Retrofit﹕ javax.net.ssl.SSLHandshakeException: javax.net.ssl.SSLProtocolException: SSL handshake aborted: ssl=0xb8f9d4a8: Failure in SSL library, usually a protocol error
    error:14077102:SSL routines:SSL23_GET_SERVER_HELLO:unsupported protocol (external/openssl/ssl/s23_clnt.c:714 0x9dd58d4d:0x00000000)
            at org.apache.harmony.xnet.provider.jsse.OpenSSLSocketImpl.startHandshake(OpenSSLSocketImpl.java:436)
            at com.squareup.okhttp.Connection.upgradeToTls(Connection.java:242)
            at com.squareup.okhttp.Connection.connect(Connection.java:159)
            at com.squareup.okhttp.Connection.connectAndSetOwner(Connection.java:175)
            at com.squareup.okhttp.OkHttpClient$1.connectAndSetOwner(OkHttpClient.java:120)
            at com.squareup.okhttp.internal.http.HttpEngine.nextConnection(HttpEngine.java:330)
            at com.squareup.okhttp.internal.http.HttpEngine.connect(HttpEngine.java:319)
            at com.squareup.okhttp.internal.http.HttpEngine.sendRequest(HttpEngine.java:241)
            at com.squareup.okhttp.Call.getResponse(Call.java:271)
            at com.squareup.okhttp.Call$ApplicationInterceptorChain.proceed(Call.java:228)
            at com.squareup.okhttp.Call.getResponseWithInterceptorChain(Call.java:199)
            at com.squareup.okhttp.Call.execute(Call.java:79)
            at retrofit.client.OkClient.execute(OkClient.java:53)
            at retrofit.RestAdapter$RestHandler.invokeRequest(RestAdapter.java:326)
            at retrofit.RestAdapter$RestHandler.access$100(RestAdapter.java:220)
            at retrofit.RestAdapter$RestHandler$1.invoke(RestAdapter.java:265)
            at retrofit.RxSupport$2.run(RxSupport.java:55)
            at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
            at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:305)
            at java.util.concurrent.FutureTask.run(FutureTask.java:137)
            at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1076)
            at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:569)
            at retrofit.Platform$Android$2$1.run(Platform.java:142)
            at java.lang.Thread.run(Thread.java:856)
     Caused by: javax.net.ssl.SSLProtocolException: SSL handshake aborted: ssl=0xb8f9d4a8: Failure in SSL library, usually a protocol error
    error:14077102:SSL routines:SSL23_GET_SERVER_HELLO:unsupported protocol (external/openssl/ssl/s23_clnt.c:714 0x9dd58d4d:0x00000000)
            at org.apache.harmony.xnet.provider.jsse.NativeCrypto.SSL_do_handshake(Native Method)
            at org.apache.harmony.xnet.provider.jsse.OpenSSLSocketImpl.startHandshake(OpenSSLSocketImpl.java:395)
            ... 23 more

I saw some of the work arounds in the other issue, and this is what my ConnectionSpec looks like:
        ConnectionSpec spec = new ConnectionSpec.Builder(ConnectionSpec.MODERN_TLS)
                .tlsVersions(TlsVersion.TLS_1_2)
                .build();
        okHttpClient.setConnectionSpecs(Collections.singletonList(spec));

From my understanding this will ensure that all the overlapped CipherSuites are used. Here are the results I got from testing it on different Android versions:
OkHttp 2.3.0
5.1 - working
5.0 - working
4.4.4 - error
4.3 - error
4.2.2 - error
4.1.1 - error
4.0 - error
OkHttp 2.2.0
5.1 - working
5.0 - working
4.4.4 - working
4.3 - working
4.2.2 - working
4.1.1 - working
4.0 - error

You'll also need to manually install additional cipher suites. See here for more details.
https://github.com/square/okhttp/wiki/HTTPS
(Even better: get your HTTPS server to use a more modern cipher suite.)

Is this still an issue with OkHttps 2.5?


Add "Grid Engine with Preemptible VMs"

Staged to:
http://googlegenomics.readthedocs.org/en/staging-2/use_cases/setup_gridengine_cluster_on_compute_engine/preemptible_vms.html

Woot!  LGTM


Incorrect Calculation Result with Tumbling Window in SQL Query

Environment:

eKuiper version : 1.11

What happened and what you expected to happen:
What happened:
I encountered a discrepancy in the calculation result when using the following SQL query:
select
  DevCode as DevCode_Sink,
  DataType as DataType_Sink,
  "WNAC_WdSpd_AVG_10s" as Metric_Sink,
  AVG(Value) as Value_Sink,
  window_end() as Time_Sink
from iotSource
GROUP BY TUMBLINGWINDOW(ss, 10) FILTER(where Metric = "WNAC_WdSpd"),DevCode

What I expected to happen:
I intended to calculate the average of "WNAC_WdSpd" within a tumbling window of size 10 seconds. However, it appears that the calculation result does not align with the left-closed and right-open interval semantics, which is unexpected.
Interestingly, when I switched from using "TUMBLINGWINDOW" to "HOPPINGWINDOW," the calculation result was as expected.

@retoool
Could you paste the input and and the result for the both outputs from sql with tumbling window and sql with hopping window in order we can know the expected result from your view.

Sure, here's a response you could provide:
Certainly! I'd be happy to provide the input and results for both SQL queries using the tumbling window and hopping window for your reference.
Input

Local Time
Value

17:54:01
10.49835

17:54:05
10.45806

17:54:10
9.52328

17:54:14
8.99291

17:54:18
10.01893

17:54:23
8.91996

17:54:27
9.73717

17:54:31
10.78512

17:54:36
10.74094

17:54:40
10.71955

17:54:44
9.22239

17:54:49
9.05869

17:54:53
8.95866

17:54:57
10.12559

17:55:02
10.0555

17:55:06
9.60793

17:55:10
10.45217

17:55:15
10.95324

17:55:19
10.05545

17:55:23
9.17934

17:55:28
8.85587

17:55:32
8.87322

17:55:36
8.07647

17:55:40
7.66734

17:55:45
7.07179

17:55:49
6.92314

17:55:53
7.32626

17:55:58
9.98239

SQL Query with Tumbling Window (Not as Expected):
select
  DevCode as DevCode_Sink,
  DataType as DataType_Sink,
  "test0001" as Metric_Sink,
  AVG(Value) as Value_Sink,
  window_end() as Time_Sink
from iotSource
GROUP BY TUMBLINGWINDOW(ss, 10) FILTER(where Metric = "WNAC_WdSpd" and DevCode = "DTZJJK:PHFC:Q1:W001")

Result of Tumbling Window:

Local Time
Value

17:54:00
11.6136

17:54:20
9.50592

17:54:30
9.328565

17:54:40
10.76303

17:54:50
9.14054

17:55:00
9.542125

17:55:10
9.831715

17:55:20
10.504345

17:55:30
9.017605

17:55:40
8.474845

17:55:50
6.997465

17:56:00
8.654325

SQL Query with Hopping Window (Expected Result):
select
  DevCode as DevCode_Sink,
  DataType as DataType_Sink,
  "WNAC_WdSpd_AVG_10s" as Metric_Sink,
  AVG(Value) as Value_Sink,
  window_end() as Time_Sink
from iotSource
GROUP BY HOPPINGWINDOW(ss, 10, 10) FILTER(where Metric = "WNAC_WdSpd" and DevCode = "DTZJJK:PHFC:Q1:W001")

Result of Hopping Window:

Local Time
Value

17:54:00
11.6136

17:54:20
9.50592

17:54:30
9.328565

17:54:40
10.76303

17:54:50
9.666876667

17:55:00
9.542125

17:55:10
9.831715

17:55:20
10.48695333

17:55:30
9.017605

17:55:40
8.474845

17:55:50
7.220756667

17:56:00
8.654325

Thanks, after I fixed this problem in https://github.com/lf-edge/ekuiper/pull/2212 and re-tested it with your case, and finally got the expected result.


jax gpu support with nvidia 5.15?

I recently upgraded and was hitting this error:
kernel version 515.48.7 does not match DSO version 510.73.5 -- cannot find working devices in this configuration

Downgrading to:
    sudo apt install nvidia-driver-510

and reinstalling:     sudo apt install nvidia-cuda-toolkit
brought it back to working state again.
Am posting this here to ask if anyone has 515 working and hopefully this helps anyone else landing in this same spot (as you will now land here with Ubuntu 22.04 accepting all defaults I think).

I think this isn't a JAX issue. (e.g., does any CUDA program work, or even things like nvidia-smi?): I'd guess you have a version mismatch between your kernel and installed libraries. Perhaps rebooting may help?


Reorganize and update the documentation for 1.0

This builds on #75 and would close both PRs.
Run tox -e docs and then start at build/sphinx/html/README.html in your browser.
@Mortal @kozzztik comments welcome!  Maybe 1.0 final can go out on Monday?

Nice reorganization and editing! Looks good to me.
1.0 final release on Monday sounds good!


[WIP] go version update

https://github.com/jenkins-x/jx/issues/8283

/cc @ankitm123

@ankitm123 should we first start doing jx-logging jx-helpers , all the jx projects required in this and after that we should do this or is it cool ?

should we first start doing jx-logging jx-helpers , all the jx projects required in this and after that we should do this or is it cool ?

Yes, we should start with the core packages.

Updated the docs: https://jenkins-x.io/community/maintainer_guide/go-upgrades/
Also post in the main issue, which package u are upgrading, so it's easier for others to keep track of the work.

Done @rajatgupta24 : ).

Change commit message (and PR title) to follow semantic convention

/ok-to-test


Modified generate_wordcloud function and added test function

Ok, something like this?
def test_wordcloud_valid_output_length()
     l = generate_wordcloud(df)
     assert(len(l) == 3, "generate_wordcloud should return 3 images")

Looks good. You can merge this first but I think you should add a test that checks that the function returns a list of 3 items.

Something like this?
def test_wordcloud_valid_output_length()
     l = generate_wordcloud(df)
     assert(len(l) == 3, "generate_wordcloud should return 3 images")


About the mask schedule during training

First of all, thank you for the awesome work!
I'd like to ask about the sampling of mask ratio during training: why is the ratio [0.7, 1.0] instead of [0, 1.0]?
To me picking the mask ratio in [0, 1.0] seems more fit with the inference process.
This wasn't explained in the paper, so I wonder how does the mask ratio range impact the training dynamics as well as the inference quality?

Thanks for your interest! We follow MAE for this sparse encoder design. Using [0.7, 1.0] is to reduce the training cost -- the encoder will only see at most 30% sequence during training, which largely reduces the computation (both memory and speed). This allows us to train larger models (like MAR-H) on our GPUs.

Thank you for the fast reply. So technically speaking, given enough computational resources, lowering the min bound to, say 0.3, will improve the overall performance of this method?

We once ablated this and the performance was not significantly improved when I reduced the min masking ratio from 0.7 to 0.6 and 0.5.

Got it, thanks!


failed to output 3dsx

As issue #44 ,I try to fresh install libctru(@Steveice10 fork).
But still get error,
Here is log:
build/source/ui/section/action/launchtitle.o
build/source/ui/section/action/pastefiles.o
build/source/libkhax/khaxinit.o
output/FBI.elf
output/3ds/FBI/FBI.smdh
output/3ds/FBI/FBI.3dsx
make: *** [output/3ds/FBI/FBI.3dsx] Error 95
rm build/source/default.shbin.c
It seems the build is sucessfuly but output failed.

Check if you can build a 3dsx from the outputted elf manually.

Yes, 3dsxtool input.elf output.3dsx works.Thank you！
Maybe build script need some fix.

Nothing wrong with the build script. With my environment, and only updating to make v4.1, I get no issues at all. Still sad that so many other projects won't work withthe 4.1 make though, but work with v3.18. Had to revert to that just today to build Godmode9.

I had the same issue on my office PC. (Win7 64Bit + devkitARM_r45-win32)
But it's woking fine on my home PC. (Win10 32Bit + devkitARM_r45-win32)
The environment on both PCs should be the same.

@damnnfo Works fine.Thank you！


Document singularity remote enhancements and implications

Needs to cover changelog items:

Allow configuration of global custom keyservers, separate from remote endpoints.
The remote login commmand now suports authentication to Docker/OCI registries and custom keyservers.
New --exclusive option for remote use allows admin to lock usage to a specific remote.


Leverage LoadingInfo as a parameter to continueLoading on MediaPeriodHolder

In preparation of being able to pass other parameters here

This fell under the radar I'm afraid, but I started the import process now and it should be merged soon.

No worries. Thank you!


Mccalluc/remove safari warning messages

Fix #94. No longer able to reproduce the original bug.

@jkmarx : ping! (Hopefully the merge from master will fix the linting problem, and not introduce any new issues.)


Add Spaceshrooms

About the PR

This PR adds Spaceshroom, FoodSpaceshroom, and CookedSpaceshroom.
It also adds a GatherableByHand component system, and expands on RandomFillSolution.
Spaceshroom is a structure that spawns randomly in maintenance.
It can be harvested by hand to yield 2 to 3 FoodSpaceshroom.
FoodSpaceshroom always has a small nutritional and vitamin value.
FoodSpaceshroom uses RandomFillSolution, each has a random chosen reagent on spawn, meaning a random effect when consumed.
The following is the pool of random reagents, with their weights and quantities:
weights:
SpaceDrugs: 10
Water: 5
Ephedrine: 3
Lexorin: 1
Amatoxin: 1
quantities:
SpaceDrugs: 10
Water: 0
Ephedrine: 10
Lexorin: 10
Amatoxin: 15
FoodSpaceshroom can be cooked in the microwave for 5 seconds to yield CookedSpaceshroom.
CookedSpaceshroom can be eaten for a higher nutritional value, and does not contain any random reagents.
FoodSpaceshroom can be juiced to yield 10 units of SpaceDrugs.
GatherableByHand Component and System have been added to support harvesting spaceshrooms by hand.
weightedRandom and RandomFillSolution have been expanded to allow quantities to be optionally specified.
Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog

:cl: forthbridge, Devi

add: Added Spaceshrooms, which spawn randomly in maintenance. Consume the raw version for a random effect!

https://github.com/space-wizards/space-station-14/assets/79264743/27bb20ae-d88d-44e6-aae0-d304b3c5a76c

I like this


Where to download the trained model 'weights.26-1.07.h5'

In Notebook 5, the model is loaded by using:
model.load(r"C:\Users\Mathias Felix Gruber\Documents\GitHub\PConv-Keras\data\logs\imagenet_phase2\weights.26-1.07.h5", train_bn=False)
But where can I download the trained model? I only want to run the test and do not want to perform training.

In Notebook 5, the model is loaded by using:
model.load(r"C:\Users\Mathias Felix Gruber\Documents\GitHub\PConv-Keras\data\logs\imagenet_phase2\weights.26-1.07.h5", train_bn=False)
But where can I download the trained model? I only want to run the test and do not want to perform training.

have u got the pre-trained model or weights ? i use the pconv_imagenet model to test , but i got a bad prediction.

You can find the link to download weights in readme.
`Pre-trained weights
I've ported the VGG16 weights from PyTorch to keras; this means the 1/255. pixel scaling can be used for the VGG16 network similarly to PyTorch.
Ported VGG 16 weights
PConv on Imagenet
PConv on Places2 [needs training]
PConv on CelebaHQ [needs training]`

You can find the link to download weights in readme.
`Pre-trained weights
I've ported the VGG16 weights from PyTorch to keras; this means the 1/255. pixel scaling can be used for the VGG16 network similarly to PyTorch.
Ported VGG 16 weights
PConv on Imagenet
PConv on Places2 [needs training]
PConv on CelebaHQ [needs training]`

Thanks, i have tried to test with the pre-trained weights , but i got the bad prediction . Is there any specific requirement for the input ?

You can find the link to download weights in readme.
**_**Pre-trained weights**_** I've ported the VGG16 weights from PyTorch to keras; this means the 1/255. pixel scaling can be used for the VGG16 network similarly to PyTorch. Ported VGG 16 weights PConv on Imagenet PConv on Places2 [needs training] PConv on CelebaHQ [needs training]

Thanks, i have tried to test with the pre-trained weights , but i got the bad prediction . Is there any specific requirement for the input ?

hello，when i tried to test with the pre-trained weights(pconv_imagenet.h5),i got an error at this function:
model=PConvUnet()
model.load('./data/model/pconv_imagenet.h5')
ValueError:Layer #0 (named "p_conv2d_17" in the current model) was found to correspond to layer p_conv2d_49 in the save file. However the new layer p_conv2d_17 expects 3 weights, but the saved weights have 2 elements. it sames like the pre-trained model and the PConvUnet() have different structures.but i am not sure.can you help me to figure it out?thanks.

You can find the link to download weights in readme.
**_**Pre-trained weights**_** I've ported the VGG16 weights from PyTorch to keras; this means the 1/255. pixel scaling can be used for the VGG16 network similarly to PyTorch. Ported VGG 16 weights PConv on Imagenet PConv on Places2 [needs training] PConv on CelebaHQ [needs training]

Thanks, i have tried to test with the pre-trained weights , but i got the bad prediction . Is there any specific requirement for the input ?

hello，when i tried to test with the pre-trained weights(pconv_imagenet.h5),i got an error at this function:
model=PConvUnet()
model.load('./data/model/pconv_imagenet.h5')
ValueError:Layer #0 (named "p_conv2d_17" in the current model) was found to correspond to layer p_conv2d_49 in the save file. However the new layer p_conv2d_17 expects 3 weights, but the saved weights have 2 elements. it sames like the pre-trained model and the PConvUnet() have different structures.but i am not sure.can you help me to figure it out?thanks.

The possible cause could be the TF version. What version do you currently use?

You can find the link to download weights in readme.
**_**Pre-trained weights**_** I've ported the VGG16 weights from PyTorch to keras; this means the 1/255. pixel scaling can be used for the VGG16 network similarly to PyTorch. Ported VGG 16 weights PConv on Imagenet PConv on Places2 [needs training] PConv on CelebaHQ [needs training]

Thanks, i have tried to test with the pre-trained weights , but i got the bad prediction . Is there any specific requirement for the input ?

hello，when i tried to test with the pre-trained weights(pconv_imagenet.h5),i got an error at this function:
model=PConvUnet()
model.load('./data/model/pconv_imagenet.h5')
ValueError:Layer #0 (named "p_conv2d_17" in the current model) was found to correspond to layer p_conv2d_49 in the save file. However the new layer p_conv2d_17 expects 3 weights, but the saved weights have 2 elements. it sames like the pre-trained model and the PConvUnet() have different structures.but i am not sure.can you help me to figure it out?thanks.

Based on @mrkeremyilmaz reply, I tried pip install -r requirements.txt with all versions specified by the author. And this problem no longer exists.

You can find the link to download weights in readme.
**_**Pre-trained weights**_** I've ported the VGG16 weights from PyTorch to keras; this means the 1/255. pixel scaling can be used for the VGG16 network similarly to PyTorch. Ported VGG 16 weights PConv on Imagenet PConv on Places2 [needs training] PConv on CelebaHQ [needs training]

Thanks, i have tried to test with the pre-trained weights , but i got the bad prediction . Is there any specific requirement for the input ?

hello，when i tried to test with the pre-trained weights(pconv_imagenet.h5),i got an error at this function:
model=PConvUnet()
model.load('./data/model/pconv_imagenet.h5')
ValueError:Layer #0 (named "p_conv2d_17" in the current model) was found to correspond to layer p_conv2d_49 in the save file. However the new layer p_conv2d_17 expects 3 weights, but the saved weights have 2 elements. it sames like the pre-trained model and the PConvUnet() have different structures.but i am not sure.can you help me to figure it out?thanks.

Based on @mrkeremyilmaz reply, I tried pip install -r requirements.txt with all versions specified by the author. And this problem no longer exists.

You can find the link to download weights in readme.
`Pre-trained weights
I've ported the VGG16 weights from PyTorch to keras; this means the 1/255. pixel scaling can be used for the VGG16 network similarly to PyTorch.
Ported VGG 16 weights
PConv on Imagenet
PConv on Places2 [needs training]
PConv on CelebaHQ [needs training]`

Hello I have tried to train model with(pconv_imagenet.h5) but got this error:
ValueError                                Traceback (most recent call last)
 in ()
1 # Instantiate the model
2 model = PConvUnet(vgg_weights='./data/logs/pytorch_vgg16.h5')
----> 3 model.load("/content/gdrive/MyDrive/Partial_Conv/pconv_imagenet.h5", train_bn=False)
 in load(self, filepath, train_bn, lr)
238
239         # Load weights into model
--> 240         epoch = int(os.path.basename(filepath).split('.')[1].split('-')[0])
241         assert epoch > 0, "Could not parse weight file. Should include the epoch"
242         self.current_epoch = epoch
ValueError: invalid literal for int() with base 10: 'h5'.
is there any way to correct this error?

You can find the link to download weights in readme.
**_**Pre-trained weights**_** I've ported the VGG16 weights from PyTorch to keras; this means the 1/255. pixel scaling can be used for the VGG16 network similarly to PyTorch. Ported VGG 16 weights PConv on Imagenet PConv on Places2 [needs training] PConv on CelebaHQ [needs training]

Hello I have tried to train model with(pconv_imagenet.h5) but got this error:
ValueError Traceback (most recent call last)
in ()
1 # Instantiate the model
2 model = PConvUnet(vgg_weights='./data/logs/pytorch_vgg16.h5')
----> 3 model.load("/content/gdrive/MyDrive/Partial_Conv/pconv_imagenet.h5", train_bn=False)
in load(self, filepath, train_bn, lr)
238
239 # Load weights into model
--> 240 epoch = int(os.path.basename(filepath).split('.')[1].split('-')[0])
241 assert epoch > 0, "Could not parse weight file. Should include the epoch"
242 self.current_epoch = epoch
ValueError: invalid literal for int() with base 10: 'h5'.
is there any way to correct this error?

It seems that the file name of the saved weights must be of the form "<N_of_epoch>-.h5", such as "weights.26-1.07.h5".

You can find the link to download weights in readme.
**_**Pre-trained weights**_** I've ported the VGG16 weights from PyTorch to keras; this means the 1/255. pixel scaling can be used for the VGG16 network similarly to PyTorch. Ported VGG 16 weights PConv on Imagenet PConv on Places2 [needs training] PConv on CelebaHQ [needs training]

Thanks, i have tried to test with the pre-trained weights , but i got the bad prediction . Is there any specific requirement for the input ?

My situation is the same as yours. Have you found a solution?

You can find the link to download weights in readme.
**_**Pre-trained weights**_** I've ported the VGG16 weights from PyTorch to keras; this means the 1/255. pixel scaling can be used for the VGG16 network similarly to PyTorch. Ported VGG 16 weights PConv on Imagenet PConv on Places2 [needs training] PConv on CelebaHQ [needs training]

Thanks, i have tried to test with the pre-trained weights , but i got the bad prediction . Is there any specific requirement for the input ?

My situation is the same as yours. Have you found a solution?

Hello, i have the same problem. did u find a solution? thanks


Add 22h49.one to the webring

Hi!
I want to propose my website for the webring.
Just a disclaimer since I know the person reviewing this probably lives on a boat, loading all pages (excluding the photos from the portfolio and git diffs) will take up about 6.5 MB of bandwith without compression, and ~4MB with brotli. The site makes moderate use of various visuals (and gifs).
The logo and circular links are at the bottom of this site.
I've taken the liberty of normalizing the indentation in the index.html file. Some of the newer entries were space indented whist the rest was tabs.
Thanks!

Sick and wild, I love it. Took me a while to get to it because we've only just returned to reliable connectivity :)
Welcome to the webring!


scan: fix error when reading an empty table

Previously TableScan struct was requiring a Snapshot to plan files and for empty tables without a snapshot an error was being returned instead of an empty result.
Following the same approach of Java [0] and Python [1] implementation this commit change the snapshot property to accept None values and the plan_files method was also changed to return an empty stream if the snapshot is not present on on PlanContext.
[0] https://github.com/apache/iceberg/blob/main/core/src/main/java/org/apache/iceberg/SnapshotScan.java#L119
[1] https://github.com/apache/iceberg-python/blob/main/pyiceberg/table/init.py#L1979
Fixes: https://github.com/apache/iceberg-rust/issues/580

Just some notes for reviewers:
I'm not 100% sure that this the best approach to fix this issue, I've just tried to follow the same approach used on Java and Python implementation, but I don't know if there is a better way to implement in Rust.
Another point is that I'm bit confusing where should I write a test case for this issue?

Thanks for the contribution!  Do we need to address this inside scan though? Why let someone build a TableScan that will always be useless?
This can be handled instead in the code that invokes table.scan(), without needing to make changes to the scan builder, scan, and context objects just for this edge case.

let scan_builder = table.scan();
// (customize builder here if reqd)...

let Ok(scan) = table_scan_builder.build() else {
    return Ok(stream::empty().boxed());
};

scan().plan_files()

Hi @sdd , thanks for your review.
I'm not sure if I understand your suggestion. I agree that would be better to fix this edge case with a smaller change, but I'm not sure If I understand your suggestion correctly.
The idea would be make the callers of TableScanBuilder.build() to handle the case where the table don't have any data? The scan_builder.build() currently returns a TableScan and the TableScan.plan_files that actually may return a stream::empty().boxed(), so I don't know if I'm missing something here? (I'm new on this codebase)
Just adding another idea: would make sense to return an error like Error::new(ErrorKind::EmptyTable) when calling TableScanBuilder.build()?

Just to clarify, not having any snapshots is not necessarily the same as not having any data. If there is no current snapshot then there can't be any data, but someone could delete all data from a table, resulting in there being a snapshot, but no data. The existing code would handle this second case just fine - we only need to handle the issue of no snapshots.

@sdd I've changed the code to return a ErrorKind::TableWithoutSnapshot instead of FeatureUnsupported. With this the user can differentiate\ a table without snapshots and a table without data. WYT?

We've been very selective when it comes to adding new values to ErrorKind. I'd personally go for Unexpected here - but maybe @liurenjie1024 or @Xuanwo can confirm what would be best.

We've been very selective when it comes to adding new values to ErrorKind. I'd personally go for Unexpected here - but maybe @liurenjie1024 or @Xuanwo can confirm what would be best.

Yes, I'm on Unexpected too, except this error kind is meaningful for users to make decisions.

@Xuanwo @sdd could you guys please take a look?


[feature request] CSR Only mode

Describe the problem
Im frustrated that Kit uses my CF Workers Quota, when I just want a Client Side Rendering, MultiPage Svelte App without client side routing with {#if page=="somthing"} {/if}
Describe the proposed solution
A adapter that Client side renders the svelte, but still does routing
Alternatives considered
Not using SvelteKit, or using all of my workers quota when my app goes fully public (i get more requests then the default quota)
Importance
i cannot use SvelteKit without it
Additional Information
repo: link

Client side rendering; fp based routing
On Mon, Jan 23, 2023, 9:47 AM Ben McCann @.***> wrote:

I don't understand what you want. In "Describe the problem" you say you
want something "without client side routing" and then in "Describe the
proposed solution" you say you want an adapter that "still does routing"
—
Reply to this email directly, view it on GitHub
https://github.com/sveltejs/kit/issues/8672#issuecomment-1400568792, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AQHW4P7QRRPMGVVW3CYIB7LWT2RZLANCNFSM6AAAAAAUD6YFNI
.
You are receiving this because you authored the thread.Message ID:
@.***>

What is "fp based routing"?
Is this "I want an SPA"? What except export const ssr = false (https://kit.svelte.dev/docs/page-options#ssr) do you need?

Basically all I'm asking for is all client side rendered, but still with
multiple pages. (That does not use cf workers quota)
Iv tried pretender & adapter-static , but fails because I use LocalStorage
and other Client Side APIS that need to be done before onMount is called
On Mon, Jan 23, 2023, 10:19 AM Simon H @.***> wrote:

What is "fp based routing"?
Is this "I want an SPA"? What except export const ssr = false (
https://kit.svelte.dev/docs/page-options#ssr) do you need?
—
Reply to this email directly, view it on GitHub
https://github.com/sveltejs/kit/issues/8672#issuecomment-1400618207, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AQHW4P7GVKYDS7QBXGAP35TWT2VPJANCNFSM6AAAAAAUD6YFNI
.
You are receiving this because you authored the thread.Message ID:
@.***>

Highly recommend following the steps in this page to achieve what you want (as per dummdidumm's suggestion).
You client-side APIs should have no issue with export const ssr = false in the root layout (src/routes/+layout.js).
If you're still experiencing issues, you could provide a copy of the logs / a detailed example of it.

I'm going to defer this til I get home, and I had already set SSR to false


Default values should be carefully selected

Background
Default value like DELETE_INSTANCE_ID=true is wrong as it requires athenz permission and outputting error message without permission isn't the best
TODOs

[ ] Check the default values
[ ] Check if every env must be modifiable under Makefile

Deleting the instance certificate should be the default behavior because of the following:

improve security
reduce ZTS load

I think the focus should be the error message.


Wrong dates added for non-English locales

I uploaded a few pictures a few days ago using the latest version of the app. An automatic category to sort the pictures by date was added to each of them, which is cool, but the category does not exist:
See eg:
https://commons.wikimedia.org/wiki/File:Krucifix_na_západ_od_Zlíčka.jpg
Also the app thinks I uploaded them on 10th August 2020 rather then 2019... could that be a problem with my phone, though?

Hmm, I've just tested the alpha and found no issue with the date taken - https://commons.wikimedia.org/wiki/File:San_Gimignano_2.jpg . The hidden category https://commons.wikimedia.org/wiki/Category:Photographs_taken_on_2019-07-05 does exist for me.
Is anyone else able to reproduce this? Vojtech does your phone display the current date correctly to you (aside from this app)?

Do we really need this date?
Maybe the bug is that the date format varies with the locale?

I don't think the category was made by us, it seems to be added to Upload Wizard uploads too, i.e. https://commons.wikimedia.org/wiki/File:Kirkkokatu_27_Raahe_20190705.jpg

Then the easiest is probably to create a Phabricator ticket and forget about it :-)

I don't think the problem is with the category creation though... it seems to be a side effect of the wrong upload date. It makes sense for uploads made "in the future" to not have the category created yet.

A few examples found:

Photographs taken on 10. 08. 20 (Czech locale)
Photographs taken on 27/08/2019 (Nepali locale)
Photographs taken on 2019-07-05 (English locale)  ← Only this one is valid

So, instead of writing the date using the user's locale, we should code it explicitly as year + "-" + month + "-" + day.

@nicolas-raoul , is this the same issue as the one reported in our public forum:

@misaochan Yes, I am pretty sure it is, and I share your view that it is a priority issue, because it forces Commons people to fix our mess, giving the app a bad reputation.

@nicolas-raoul Agreed. Unfortunately I am away for 2 weeks starting this Saturday, and by the time I get back 2.12 should be close to ready, which means that a hotfix may not make sense. :/ Or alternatively, could you and @ashishkumar468 collaborate on this, where he sends a hotfix to our 2.11-release branch, and you do the 2.11.1 hotfix release when it is ready?

I am looking for a new apartment right now so I have to focus on that, unfortunately :'-/ But I can review a pull request :-)

Ah, okay. I'll try to release 2.11.1 with the hotfix as soon as I get back, then.

I will look into the issue and raise a PR for the same :)

I am not able to reproduce this, I can see the actual date for both Hindi & English Locales. Is there a specific way to produce this ?

Maybe Hindi & English locales use the same date format.
@ashishkumar0207 Would you mind trying Czech or Nepali locale?

@nicolas-raoul  Sure, I will try that .

It seems this is a fairly general phenomenon... just found out the same bug appears in pictures from another Czech uploader: https://commons.wikimedia.org/wiki/File:Plastika_Prostřený_stůl_v_ulici_Na_Mlejnku.jpg
So it could really be due to language settings.

I can't reply this bug with my phone, with Czech, Nepali, English or Russian locale.

@PavelAplevich Thanks for trying! Could you please post the URL to the images you uploaded in each locale? Thanks :-)

https://commons.wikimedia.beta.wmflabs.org/wiki/File%3AMemoriál.jpg
This image upload now. But on "Summary" i see "6 August 2019"

That's with the Czech locale right?
Could you please try uploading to the production server instead? Using the prod flavour.

I undestand. This is the date the file was created on my device.

@nicolas-raoul
I did't understand you( Sorry, tell me more what I need to do

I mean, please run ./gradlew installProdDebug (or select the productionDebug flavour in Android Studio, as described at https://stackoverflow.com/a/27549441/226958). :-)

I run build with "prod" and "debug" on my phone and app doesn't work :D

Doesn’t works as in what error are you getting?
On Mon, 9 Sep 2019 at 1:13 PM, PavelAplevich<EMAIL_ADDRESS>wrote:

I run build with "prod" and "debug" on my phone and app doesn't work :D
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/commons-app/apps-android-commons/issues/3126?email_source=notifications&email_token=AEESAKVASCQDTE6FQXNP5YDQIX5A5A5CNFSM4ILDJFQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6GRL2A#issuecomment-529339880,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEESAKWEO7IBOPEJCKECOZDQIX5A5ANCNFSM4ILDJFQQ
.

--
Thanking You,
Ashish Kumar

09-09 10:53:14.164 17895-17895/? E/libprocessgroup: failed to make and chown /acct/uid_10065: Read-only file system
--------- beginning of main

09-09 10:53:14.164 17895-17895/? W/Zygote: createProcessGroup failed, kernel missing CONFIG_CGROUP_CPUACCT?
09-09 10:53:14.165 17895-17895/? I/art: Not late-enabling -Xcheck:jni (already on)
09-09 10:53:14.761 17895-17895/fr.free.nrw.commons.beta I/ACRA: ACRA is enabled for fr.free.nrw.commons.beta, initializing...
09-09 10:53:14.780 17895-17895/fr.free.nrw.commons.beta D/SoLoader: init start
09-09 10:53:14.780 17895-17895/fr.free.nrw.commons.beta D/SoLoader: adding system library source: /vendor/lib
09-09 10:53:14.780 17895-17895/fr.free.nrw.commons.beta D/SoLoader: adding system library source: /system/lib
09-09 10:53:14.780 17895-17895/fr.free.nrw.commons.beta D/SoLoader: adding application source: com.facebook.soloader.DirectorySoSource[root = /data/app/fr.free.nrw.commons.beta-1/lib/x86 flags = 0]
09-09 10:53:14.780 17895-17895/fr.free.nrw.commons.beta D/SoLoader: adding backup source from : com.facebook.soloader.ApkSoSource[root = /data/data/fr.free.nrw.commons.beta/lib-main flags = 1]
09-09 10:53:14.780 17895-17895/fr.free.nrw.commons.beta D/SoLoader: Preparing SO source: com.facebook.soloader.DirectorySoSource[root = /system/lib flags = 2]
09-09 10:53:14.780 17895-17895/fr.free.nrw.commons.beta D/SoLoader: Preparing SO source: com.facebook.soloader.DirectorySoSource[root = /system/vendor/lib flags = 2]
09-09 10:53:14.780 17895-17895/fr.free.nrw.commons.beta D/SoLoader: Preparing SO source: com.facebook.soloader.DirectorySoSource[root = /data/app/fr.free.nrw.commons.beta-1/lib/x86 flags = 0]
09-09 10:53:14.780 17895-17895/fr.free.nrw.commons.beta D/SoLoader: Preparing SO source: com.facebook.soloader.ApkSoSource[root = /data/data/fr.free.nrw.commons.beta/lib-main flags = 1]
09-09 10:53:14.781 17895-17895/fr.free.nrw.commons.beta V/fb-UnpackingSoSource: locked dso store /data/data/fr.free.nrw.commons.beta/lib-main
09-09 10:53:14.781 17895-17895/fr.free.nrw.commons.beta I/fb-UnpackingSoSource: dso store is up-to-date: /data/data/fr.free.nrw.commons.beta/lib-main
09-09 10:53:14.781 17895-17895/fr.free.nrw.commons.beta V/fb-UnpackingSoSource: releasing dso store lock for /data/data/fr.free.nrw.commons.beta/lib-main
09-09 10:53:14.781 17895-17895/fr.free.nrw.commons.beta D/SoLoader: init finish: 4 SO sources prepared
09-09 10:53:14.781 17895-17895/fr.free.nrw.commons.beta D/SoLoader: init exiting
09-09 10:53:14.802 17895-17895/fr.free.nrw.commons.beta D/AndroidRuntime: Shutting down VM
09-09 10:53:14.802 17895-17895/fr.free.nrw.commons.beta E/ACRA: ACRA caught a RuntimeException for fr.free.nrw.commons.beta
java.lang.RuntimeException: Unable to start activity ComponentInfo{fr.free.nrw.commons.beta/fr.free.nrw.commons.auth.LoginActivity}: android.view.InflateException: Binary XML file line #40: Error inflating class TextView
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2325)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2387)
at android.app.ActivityThread.access$800(ActivityThread.java:151)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1303)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.java:5254)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)
Caused by: android.view.InflateException: Binary XML file line #40: Error inflating class TextView
at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:763)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:806)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:809)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:809)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:809)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:809)
at android.view.LayoutInflater.inflate(LayoutInflater.java:504)
at android.view.LayoutInflater.inflate(LayoutInflater.java:414)
at android.view.LayoutInflater.inflate(LayoutInflater.java:365)
at com.android.internal.policy.impl.PhoneWindow.setContentView(PhoneWindow.java:378)
at android.app.Activity.setContentView(Activity.java:2145)
at fr.free.nrw.commons.auth.LoginActivity.onCreate(LoginActivity.java:127)
at android.app.Activity.performCreate(Activity.java:5990)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1106)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2278)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2387)
at android.app.ActivityThread.access$800(ActivityThread.java:151)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1303)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.java:5254)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)
Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'void androidx.appcompat.widget.AppCompatBackgroundHelper.onSetBackgroundDrawable$130e17e7()' on a null object reference
at androidx.appcompat.widget.AppCompatTextView.setBackgroundDrawable(AppCompatTextView.java:119)
at android.view.View.setBackground(View.java:16226)
at android.view.View.(View.java:4103)
at android.widget.TextView.(TextView.java:637)
at android.widget.TextView.(TextView.java:632)
at androidx.appcompat.widget.AppCompatTextView.(AppCompatTextView.java:95)
at androidx.appcompat.widget.AppCompatTextView.(AppCompatTextView.java:91)
at androidx.appcompat.app.AppCompatViewInflater.createTextView(AppCompatViewInflater.java:182)
at androidx.appcompat.app.AppCompatViewInflater.createView(AppCompatViewInflater.java:103)
at androidx.appcompat.app.AppCompatDelegateImpl.createView(AppCompatDelegateImpl.java:1266)
at androidx.appcompat.app.AppCompatDelegateImpl.onCreateView(AppCompatDelegateImpl.java:1316)
at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:725)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:806)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:809)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:809)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:809)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:809)
at android.view.LayoutInflater.inflate(LayoutInflater.java:504)
at android.view.LayoutInflater.inflate(LayoutInflater.java:414)
at android.view.LayoutInflater.inflate(LayoutInflater.java:365)
at com.android.internal.policy.impl.PhoneWindow.setContentView(PhoneWindow.java:378)
at android.app.Activity.setContentView(Activity.java:2145)
at fr.free.nrw.commons.auth.LoginActivity.onCreate(LoginActivity.java:127)
at android.app.Activity.performCreate(Activity.java:5990)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1106)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2278)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2387)
at android.app.ActivityThread.access$800(ActivityThread.java:151)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1303)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.java:5254)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)
09-09 10:53:15.201 17895-17895/fr.free.nrw.commons.beta I/Process: Sending signal. PID: 17895 SIG: 9

@PavelAplevich  Can you try using clean project/ invalidate cache restart, it seems to work for me.

All my steps:
Choose "Build"->"Edit Flavours"->"prod"
"Edit Build Types"->"debug"
Restart Studio
Delete all cashe and app from my phone
Restart phone
Delete cashe and app from emulator
Run app on phone and emulator. App doesn't work(

This seems to be another issue, please create an issue for the same. We will take it from there.

@ashishkumar468 I done) I update my gradle to 3.5.0 version and all works.
@nicolas-raoul You's URL on prodDebug build
https://commons.wikimedia.org/wiki/File%3AOrigami_3.jpg

The date seems looks correct to me, @nicolas-raoul. @PavelAplevich has also uploaded the image in Czech locale.  Am I missing something, is there a specific way to reproduce this?.@PavelAplevich  I would recommend not to upload dummy images on prod, your account might get flagged :P

@PavelAplevich Any difficulty with that? I can help you step-by-step if you want :-)

(sorry please disregard the comment I posted a few minutes ago, I had not refreshed my browser)
https://commons.wikimedia.org/wiki/File%3AOrigami_3.jpg (Czech locale) has a wrong date format: {{According to EXIF data|31. 10. 2018}}
https://commons.wikimedia.org/wiki/File%3ACaf.jpg (Russian locale) has a correct date format: {{date|2019|7|28}}
So, congratulations for reproducing the problem :-)
Now, please find in the source code the places where description is generated, put breakpoints, and run in debug mode to understand better how the date is generated, then tell us :-)

@nicolas-raoul Ok, I will do it. Give me some time..

@nicolas-raoul
https://commons.wikimedia.org/wiki/File%3AUruccha.jpg
This file has wrong date too, right?

@PavelAplevich The date of that file is {{According to EXIF data|04.09.2019}} which is wrong too, yes.
By the way, rather than uploading random pictures and then nominating them for deletion, I suggest you upload these pictures (pick randomly as some have been uploaded already):
https://drive.google.com/drive/folders/1YeYGelmhKbpO_OPAKLT-S4Cw-rsbCG6V?usp=sharing

@nicolas-raoul Thank you, for pictures.
I think, the problem is:
Photos with correct date i download from my messenger. They date based on date of creating file.
Photos with wrong date i did it by myself, on my phone. They date based on EXIF.
As the result - EXIF work's wrong.
What do think about this?

There is one line where the template is filled: https://github.com/commons-app/apps-android-commons/blob/bb570a5afc32e13086460b9aa536112107c620f2/app/src/main/java/fr/free/nrw/commons/contributions/Contribution.java#L205
Either dateCreated is not in the correct format or the formatter getDateStringWithSkeletonPattern does not work properly.

@PavelAplevich Using EXIF data is fine as far as I'm aware. The problem here is with the date templates being sent, which are in the wrong format. I think https://github.com/commons-app/apps-android-commons/issues/3126#issuecomment-525686311 explains what needs to be done. :)

@PavelAplevich would you happen to have an update on this? Sorry for the rush, but this is a bit of a high-priority issue. :)

@misaochan
This is Czech locale image
hhttps://commons.wikimedia.beta.wmflabs.org/wiki/File%3AKran.jpg
This is Russian locale image
https://commons.wikimedia.beta.wmflabs.org/wiki/File%3AУручье.jpg
https://commons.wikimedia.beta.wmflabs.org/wiki/File%3AГород.jpg
This is UK locale image
https://commons.wikimedia.beta.wmflabs.org/wiki/File%3ACity.jpg
Could you please tell me, which variant is correct?

@PavelAplevich none of them are correct. We need the format "Photographs taken on 2019-07-05", which has the year first.
Take a look at the template for the images you linked - to view the format of the template, you can go to Summary > edit. The first file you linked, for instance, says:

== {{int:filedesc}} ==
{{Information
|description={{cs|1=test}}
|source={{own}}
|author=[[User:Roc|Roc]]
|date={{According to EXIF data|13. 03. 2019}}
}}

A possible solution is to code it explicitly as year + "-" + month + "-" + day.

Thanks for the PR @PavelAplevich , the same is merged with master, works for me. Can someone else also verify the same ?

Thanks so much @PavelAplevich ! :) @ashishkumar468 I am trying to review the results, but it seems like the Commons Beta DB is down at the moment? I'll try again later.

Issue is fixed for me. Thanks @PavelAplevich !

With further testing, I've found that uploaded pictures without EXIF data don't display the date at all in the summary: https://commons.wikimedia.org/wiki/File:Byron_lighthouse_2.jpg
This is quite strange since https://commons.wikimedia.beta.wmflabs.org/w/index.php?title=File:NoEXIF.jpg displays the date perfectly fine. And looking at their date templates, there is no difference.
Is there a difference between how Commons Beta and the real Commons handles display of date templates?

@misaochan
I see the correct information both there and there

Do you see the date in the summary? I don't mean Summary > Edit, but in the user-facing summary. Personally for https://commons.wikimedia.org/wiki/File:Byron_lighthouse_2.jpg this is what I see:
Description | English: Lighthouse at Cape Byron
Date |
Source | Own work
Author | misaochan2

Yes, i see.. Any ideas, what the problem is?

I'm not sure. :( Trying to figure it out myself too. @nicolas-raoul @Aschroet any idea?

@Achim55 Hope you don't mind a quick Q - do you know why the date field in the user-facing summary of https://commons.wikimedia.org/wiki/File:Byron_lighthouse_2.jpg is blank, even though the template is filled with |date={{date|2019-09-09}}``?

@misaochan I tried in various locales, and the user-facing summary is displaying the proper dates.

@misaochan I have correct data too..

I fixed it and left a note on your talk page. Best, Achim

Thanks @Achim55 , I'll modify the template that we send accordingly. :)


i got these error in angular-cli project please help me

ERROR in ./src/app/movies/page5.component.ts
Module not found: Error: Can't resolve './pages5.component.html' in 'C:\Projects\moviesapp\src\app\movies'
@ ./src/app/movies/page5.component.ts 16:22-56
@ ./src/app/movies/movies-routing.module.ts
@ ./src/app/app.module.ts
@ ./src/main.ts
@ multi main

@shahbazhaidry  page5.component.ts error in 16th line. check it

You'd also need to fill in the issue template for us to help, although this looks like a better question for Stack Overflow or the likes regardless, as it's not related to the CLI.

@Equinox is right

Closing as answered, thanks @smartHasmukh!


Aws moose source

Purpose of this pull request
This pull request (PR) ...
Issue number:

Select the type of change:

[ ] Minor Changes - Typos, formatting, slight revisions
[ ] Update Content - Revisions and updating sections
[ ] New Content - New features, sections, pages, tutorials
[ ] Site and Tools - Updates, maintenance, and new packages for the site, Gatsby, React, etc

Screenshots will be replaced during the GA release.


Unable to find specification for ZIPFoundation (= 0.9.11) and hermes-engine (~> 0.9.0)

react-native: 0.67.2
react-native-file-access: ^3.0.4
Platform: iOS
Bug
I'm getting this issue when doing pod install and is not able to run this in iOS
Unable to find a specification for ZIPFoundation (= 0.9.11) depended upon by ReactNativeFileAccess
and when doing pod update after that i'm getting
Unable to find a specification for hermes-engine (~> 0.9.0)

Solved by adding below to the PodFile
source 'https://cdn.cocoapods.org/'


Update wrapper to 8.5 RC4

@bot-gradle merge

I've triggered a build for you. Click here to see all failures if there's any.


java-microprofile: version changes

Checklist:

[x] Read the Code of Conduct and Contributing Guidelines.

[x] Followed the commit message guidelines.

[x] Stack adheres to Appsody stack structure.

Modifying an existing stack:

[x] Updated the stack version in stack.yaml

Changed versions of openliberty to <IP_ADDRESS>

Relaxed rule to allow any java 1.8 version

Updated stack version

Signed-off-by Neeraj Laad<EMAIL_ADDRESS>

This was not needed as there is another PR with same change


Remove leftover code + spinner

No references to the code and file in question were found.

released with rebase 0309ae59c7274408810c75c1fbc1b449d7ad2df4


error TS6053: File 'folder/vite-electron-ts/src/main/index.ts' not found.

after running yarn dev, this shows up:
yarn dev
yarn run v1.22.10
$ electron-dev-runner src/main/index.ts --vite

  vite v2.4.4 dev server running at:

  > Local: http://localhost:3000/
  > Network: use `--host` to expose

  ready in 319ms.

error TS6053: File 'folder/vite-electron-ts/src/main/index.ts' not found.
  The file is in the program because:
    Root file specified for compilation
error TS6231: Could not resolve the path 'D:/Projects/_PersonalProjects/New' with the extensions: '.ts', '.tsx', '.d.ts'.
  The file is in the program because:
    Root file specified for compilation
error TS6231: Could not resolve the path 'folder/vite-electron-ts/dist/main' with the extensions: '.ts', '.tsx', '.d.ts'.
  The file is in the program because:
    Root file specified for compilation
error: error TS6053: File 'folder/vite-electron-ts/src/main/index.ts' not found.
  The file is in the program because:
    Root file specified for compilation
error TS6231: Could not resolve the path 'D:/Projects/_PersonalProjects/New' with the extensions: '.ts', '.tsx', '.d.ts'.
  The file is in the program because:
    Root file specified for compilation
error TS6231: Could not resolve the path 'folder/vite-electron-ts/dist/main' with the extensions: '.ts', '.tsx', '.d.ts'.
  The file is in the program because:
    Root file specified for compilation

error Command failed with exit code 9.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

请查看启动时主进程的入库文件目录地址是否正确


[Constraints]: Comparison gate

Add lt, gt gates to the constraint system.
Reference: r1cs-std's cmp.rs

Note: we use range_check(a, bit_len) -> Vec<BoolVar> that ensure variable a \in [0, 2^bit_len) and return the binary representation of a as a building block, this gate costs (bit_len boolean constraint + bit_len / 3 linear combination) constraints
(see "Range check" section in cap-spec for details, or code here).
iiuc, arkworks' cmp.rs constraint logic for checking a<b goes as follows:

check MSB of a and b is 0, by checking a<(p-1)/2 && b<(p-1)/2 -- takes 2 range_check
compute c = (a-b)*2 in circuit, and decompose into binary representation and return the MSB of c -- takes 1 subtraction gate and a range_check gate

the constraint works because if a<b, then after subtraction, the MSB would be flipped from 0 to 1,
However, the limitation of arkworks' approach is that, they won't allow comparison between two variables lies within [(p-1)/2, p).

Fortunately, with a little tweak, we can compare any two field elements.
Idea: either the a.MSB = 0 AND b.MSB = 1 or the |p|-1-least-significant bits of a and b follow the constraints above.
We denote $\ell$ as the bit length of $p$, and assume that to be a multiple of three (if not, we pad with zero)

first decompose $a, b$ as:a= (a_0, a_1, \ldots, a_{\ell-1}), b= (b_0, b_1, \ldots, b_{\ell-1})

to check $a_0=0 \land b_0 = 1$: constrain $a_0 * (b_0-1) = 0 \land a_0 + (b_0-1) = 0$
to check the second half of the statement: reuse the second last acc value calculated during decomposition in the first step and compute $a', b'$, essentially\begin{matrix}
a'= (a_1, \ldots, a_{\ell-1}) = acc_{a,\, \ell/3 - 1} * 8 + 2 * a_1 + a_2 \\
b'= (b_1, \ldots, b_{\ell-1}) = acc_{b,\, \ell/3 - 1} * 8 + 2 * b_1 + b_2
\end{matrix}

we are sure both a', b' < (p-1)/2, and we enforce the constraints listed in arkworks
finally we add a logic_or_gate() on the above two conditions

Notes:

our current decompose_vars_gate() implementation calculate $acc_i$ from MSB to LSB, but here we require the other way around in order to reuse and not recompute all intermediate values again.
additional cost compared to arkworks is ~ 5 more gates.

WDYT? @chancharles92 @mrain

Generally LGTM, there are some details to be checked more carefully.
Idea: either the a.MSB = 0 AND b.MSB = 1 or the |p|-1-least-significant bits of a and b follow the constraints above
We may add one more constraint at the end to distinguish the cases a.MSB=b.MSB=0 and a.MSB=b.MSB=1.
Also we need to be careful with the case that (i) a.MSB=1, b.MSB=0 and (ii) the |p|-1-least-significant bits of a and b follow the constraints above. This still satisfies your predicate, but a < b doesn't hold.

My proposed solution for comparison gate between 2 input variables a and b.

Transform it into canonical form of "strictly less than": a < b.

For strictly greater than, simply swap 2 variables.
When equality has to be checked, add a logical negation gate upon it. E.g. a <= b to NOT(b < a).

Compare both a and b to (p-1)/2. Set a'=1 iff a <= (p-1)/2 and a'=0 ow, similarly for b'.

Check if a'=0 and b'=1, constrain a' * (1 - b') = 0 AND a' + (1 - b') = 0.
Put constraints to check if a' = b' and (a - b) > (p-1)/2. When a and b are both (no) greater than (p-1)/2, over F_p we have a < b if and only if (a-b) > (p-1)/2.

To complete the solution, we need to implement another gate to compare a variable to a constant (p-1)/2. I don't think range_check applies here, because it only supports power-of-2 range check.
@chancharles92 @alxiong WDYT?

A typo: a <= b to NOT(b < a) -> a <= b to NOT(b > a)
For point 2, we can discuss a bit more.

Minor suggestion: a <= b to NOT(b < a) -> a <= b to NOT(a > b)

no need, @mrain 's transformation perfectly fine, cuz you only need to implement <, (as for >, we just swap operands as suggested)

we need to implement another gate to compare a variable to a constant (p-1)/2. I don't think range_check applies here, because it only supports power-of-2 range check.

agree, how do you plan to implement a <= (p-1)/2?

`Minor suggestion: a <= b to NOT(b < a) -> a <= b to NOT(a > b)
no need, @mrain 's transformation perfectly fine, cuz you only need to implement <, (as for >, we just swap operands as suggested)Oh, it's just meant for readability of the comment, nothing need to change in terms of correctness. Actually I now understand why @mrain usesNOT(b < a)because we only have an API for<`.

agree, how do you plan to implement a <= (p-1)/2?

Take the bits representation of a and build a binary circuit for it. @alxiong

I'm thinking, is it better to use interfaces like is_le, is_geq rather than is_cmp(ordering)?
WDYT @alxiong @chancharles92

Yes, I think so. It's more understandable.


SchemaFilter NuGet Version?

Which Version of swashbuckle supports SchemaFilter?
I don't find it in mine. (v6.0.0-rc1-final for swaggerGen and swaggerUI)

So, the version you're using is next-gen (targeting ASP.Net "Core") and is not reflected in the current readme. I'm working hard to close out critical issues with the 5.x line before re-shifting my focus back to 6.x (including providing some docs for that version).
In the meantime, I can tell you that SchemaFilter's are called ModelFilter's in the next-gen version. Hopefully this helps.


Why does reid not contribute on MOT17 val ?

Thanks for your neat work first 🌹
I got BoT-SORT without reid(i.e. merely YOLOX) achieve
HOTA DetA AssA
69.175,67.239,71.683
Seems consistent with BoT-SORT-ReID in Table.1
python3 tools/track.py datasets/MOT17 --default-parameters -expn official_mot17_val --with-reid --benchmark "MOT17" --eval "val" --fp16 --fuse

While BoT-SORT with reid only got
HOTA DetA AssA
68.727,67.285,70.713
python3 tools/track.py datasets/MOT17 --default-parameters -expn official_mot17_val --with-reid --benchmark "MOT17" --eval "val" --fp16 --fuse --with_reid

🤔
That's strange. I ran multiple times, the results stay the same

how you get the result,like HOTA?


Words

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

wat?


MQL features

See also bootstrapping. Things like finding "name" predicates, and various schema or type enforcement.
An important failure of MQL before was that it was never well-specified. Let's not fall in that trap again, and be able to document what everything means.

Closed and moved to: https://discourse.cayley.io/t/mql-features/226


Tmuxinator unsupported version tmux 3.3

Describe the bug
A clear and concise description of what the bug is.
I got this,
    WARNING: You are running tmuxinator with an unsupported version of tmux.     Please consider using a supported version:     (3.2a, 3.2, 3.1c, 3.1b, 3.1a, 3.1, 3.0a, 3.0, 2.9a, 2.9, 2.8, 2.7, 2.6, 2.5, 2.4, 2.3, 2.2, 2.1, 2.0, 1.9, 1.8, 1.7, 1.6, 1.5)
To Reproduce
Steps to reproduce the behavior.
When you upgrade tmux 3.3,
then use tmuxinator,
Expected behavior
A clear and concise description of what you expected to happen.
use tmuxinator
Environment

tmuxinator Version: [output of tmuxinator -v, e.g. "tmuxinator 0.13.0"]
tmuxinator 3.0.2

tmux Version: [output of tmux -V, e.g. "tmux 2.3"]
tmux 3.3

Ruby Version: [output of ruby -v, e.g. "ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-linux]"]
ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [arm64-darwin21]

OS: [specific command varies, e.g. "Debian GNU/Linux 9.5 (stretch)"]
Darwin mac 21.5.0 Darwin Kernel Version 21.5.0: Tue Apr 26 21:08:37 PDT 2022; root:xnu-8020.121.3~4/RELEASE_ARM64_T6000 arm64

Additional information
Add any other context or (potentially) useful information about the problem here. Feel free to include screenshots, videos, scripts, Dockerfiles, etc. which may help others diagnose/reproduce the issue.

Warning is annoying, --suppress-tmux-version-warning=SUPPRESS-TMUX-VERSION-WARNING


Move sidebar to the left

Hi, is there a way to move the sidebar to the left ?

Hi! I just pushed a change that should allow that.
You need to add to your config file, in the Params section the following parameter:
swapColumns = true


Build error after installing plugin

Describe the bug
I added the plugin and tried building my app, but it always throws the error below and the build simply aborts.
> Task :capacitor-community-capacitor-googlemaps-native:compileDebugJavaWithJavac
E:\Projects\twalako\driver\node_modules\@capacitor-community\capacitor-googlemaps-native\android\src\main\java\com\hemangkumar\capacitorgooglemaps\CapacitorGoogleMaps.java:26: error: package com.getcapacitor.annotation does not exist
import com.getcapacitor.annotation.CapacitorPlugin;
                                  ^
E:\Projects\twalako\driver\node_modules\@capacitor-community\capacitor-googlemaps-native\android\src\main\java\com\hemangkumar\capacitorgooglemaps\CapacitorGoogleMaps.java:27: error: package com.getcapacitor.annotation does not exist
import com.getcapacitor.annotation.Permission;
                                  ^
E:\Projects\twalako\driver\node_modules\@capacitor-community\capacitor-googlemaps-native\android\src\main\java\com\hemangkumar\capacitorgooglemaps\CapacitorGoogleMaps.java:52: error: cannot find symbol
@CapacitorPlugin(
 ^
  symbol: class CapacitorPlugin
3 errors

> Task :capacitor-community-capacitor-googlemaps-native:compileDebugJavaWithJavac FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':capacitor-community-capacitor-googlemaps-native:compileDebugJavaWithJavac'.
> Compilation failed; see the compiler error output for details.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

To Reproduce
Steps to reproduce the behavior:

Install the plugin using npm i --save @capacitor-community/capacitor-googlemaps-native
Update Manifest.xml and MainActivity.java as described in the docs.
Sync using the command npx cap sync
Build the apk using the command ionic capacitor copy android --prod && cd android && .\gradlew assembleDebug && cd ..
See error

Expected behavior
The app should build without any errors.

This error was brought about by the @capacitor/android version. I updated it to the latest version and it disappeared.