ci(actions): update renovatebot/github-action action to v40.3.4

This PR contains the following updates:

Package
Type
Update
Change

renovatebot/github-action
action
minor
v40.2.7 -> v40.3.4

Release Notes

renovatebot/github-action (renovatebot/github-action)
v40.3.4
Compare Source
Documentation

update references to actions/checkout to v4.2.1 (11212af)
update references to renovatebot/github-action to v40.3.3 (7bdca51)

Miscellaneous Chores

deps: update dependency @types/node to v20.16.11 (85652f0)
deps: update dependency prettier-plugin-packagejson to v2.5.3 (9347c05)
deps: update pnpm to v9.12.1 (49efd81)

Build System

deps: update dependency typescript to v5.6.3 (9c10032)

Continuous Integration

deps: update renovate docker tag to v38.120.0 (d1179fe)
deps: update renovate docker tag to v38.120.1 (7eaca7d)
deps: update renovate docker tag to v38.122.0 (5ebe74f)
deps: update renovate docker tag to v38.123.0 (398baed)
deps: update renovate docker tag to v38.124.1 (76a4553)

v40.3.3
Compare Source
Bug Fixes

deps: update dependency @actions/core to v1.11.1 (dd7f630)

Continuous Integration

deps: update renovate docker tag to v38.115.0 (0168adb)
deps: update renovate docker tag to v38.115.1 (221a713)
deps: update renovate docker tag to v38.116.0 (56e961b)
deps: update renovate docker tag to v38.119.0 (13076db)

v40.3.2
Compare Source
Bug Fixes

deps: update dependency @actions/core to v1.11.0 (6b22ac7)

Documentation

update references to ghcr.io/renovatebot/renovate to v38.110.2 (8fcdc6e)
update references to renovatebot/github-action to v40.3.1 (593a1c0)

Miscellaneous Chores

deps: update dependency @types/node to v20.16.10 (659e9b1)
deps: update dependency @types/node to v20.16.6 (43cf848)
deps: update dependency @types/node to v20.16.7 (04140e8)
deps: update dependency @types/node to v20.16.8 (ffa56df)
deps: update dependency @types/node to v20.16.9 (04eaa9d)
deps: update dependency semantic-release to v24.1.2 (443c041)
deps: update pnpm to v9.12.0 (73c1f19)

Continuous Integration

deps: update actions/checkout action to v4.2.1 (a89ddca)
deps: update renovate docker tag to v38.105.0 (6c8aefd)
deps: update renovate docker tag to v38.106.0 (c2fef14)
deps: update renovate docker tag to v38.106.2 (bdb5ad6)
deps: update renovate docker tag to v38.106.3 (32149ad)
deps: update renovate docker tag to v38.106.4 (8015943)
deps: update renovate docker tag to v38.107.0 (6846c99)
deps: update renovate docker tag to v38.107.1 (9da33e8)
deps: update renovate docker tag to v38.109.0 (4c5ca41)
deps: update renovate docker tag to v38.110.1 (59f331f)
deps: update renovate docker tag to v38.110.2 (ccf2a06)
deps: update renovate docker tag to v38.110.4 (2fd7d6a)
deps: update renovate docker tag to v38.114.0 (1c16e18)

v40.3.1
Compare Source
Build System

deps: update dependency @vercel/ncc to v0.38.2 (336c9d5)

Continuous Integration

deps: update renovate docker tag to v38.103.1 (2f7cf70)

v40.3.0
Compare Source
Features

add docker-socket-host-path input (#862) (c0afe86)

v40.2.11
Compare Source
Documentation

update references to actions/checkout to v4.2.0 (b0990c1)
update references to ghcr.io/renovatebot/renovate to v38.101.1 (1ae1ac0)
update references to renovatebot/github-action to v40.2.10 (86ff03b)

Miscellaneous Chores

deps: update commitlint monorepo to v19.5.0 (7a0e06d)
deps: update dependency @semantic-release/github to v10.3.4 (8b7ac01)
deps: update dependency @semantic-release/github to v10.3.5 (#864) (f21eeef)
deps: update dependency eslint to v8.57.1 (3a945ba)
deps: update dependency husky to v9.1.6 (d35a34a)
deps: update dependency npm-run-all2 to v6.2.3 (8aa7554)
deps: update dependency semantic-release to v24.1.1 (f70fd7d)
deps: update pnpm to v9.11.0 (871230b)

Build System

deps: lock file maintenance (669f02b)

Continuous Integration

deps: update actions/checkout action to v4.2.0 (cea9e7c)
deps: update actions/setup-node action to v4.0.4 (926bb29)
deps: update renovate docker tag to v38.100.0 (00c426e)
deps: update renovate docker tag to v38.100.1 (e9da8a6)
deps: update renovate docker tag to v38.101.0 (af7815d)
deps: update renovate docker tag to v38.101.1 (157d4d8)
deps: update renovate docker tag to v38.84.0 (6cc098a)
deps: update renovate docker tag to v38.84.1 (e1ef94d)
deps: update renovate docker tag to v38.85.1 (e89e3ea)
deps: update renovate docker tag to v38.86.0 (9251f4a)
deps: update renovate docker tag to v38.88.1 (4d5a44a)
deps: update renovate docker tag to v38.88.2 (1caa178)
deps: update renovate docker tag to v38.89.2 (7602472)
deps: update renovate docker tag to v38.89.3 (f571b99)
deps: update renovate docker tag to v38.91.0 (7b3db30)
deps: update renovate docker tag to v38.91.2 (3607015)
deps: update renovate docker tag to v38.91.5 (063fac8)
deps: update renovate docker tag to v38.92.0 (5663610)
deps: update renovate docker tag to v38.93.0 (2b64bb7)
deps: update renovate docker tag to v38.93.1 (6e3d1f1)
deps: update renovate docker tag to v38.93.6 (bc2b6fa)
deps: update renovate docker tag to v38.94.2 (604f795)
deps: update renovate docker tag to v38.94.3 (92c7bc3)
deps: update renovate docker tag to v38.95.4 (c939d62)
deps: update renovate docker tag to v38.97.0 (e16ec5f)
deps: update renovate docker tag to v38.97.1 (93190dc)
deps: update renovate docker tag to v38.98.0 (d1ece14)

v40.2.10
Compare Source
Miscellaneous Chores

deps: update pnpm to v9.10.0 (4ecccc8)

Build System

deps: update dependency typescript to v5.6.2 (ccb9633)

v40.2.9
Compare Source
Documentation

update references to ghcr.io/renovatebot/renovate to v38.80.0 (54adf7f)
update references to renovatebot/github-action to v40.2.8 (f6f4de0)

Miscellaneous Chores

deps: update dependency @semantic-release/github to v10.3.0 (39c0ed3)
deps: update dependency @semantic-release/github to v10.3.1 (d237b41)
deps: update dependency @semantic-release/github to v10.3.2 (2533c44)
deps: update dependency @semantic-release/github to v10.3.3 (0e39ae0)
deps: update dependency @types/node to v20.16.4 (d9eb43e)
deps: update dependency @types/node to v20.16.5 (6d5784a)

Build System

deps: lock file maintenance (32073a4)

Continuous Integration

deps: update renovate docker tag to v38.73.3 (476a91f)
deps: update renovate docker tag to v38.73.5 (1649e40)
deps: update renovate docker tag to v38.74.1 (65f5c11)
deps: update renovate docker tag to v38.75.0 (fa73ff0)
deps: update renovate docker tag to v38.76.1 (438981f)
deps: update renovate docker tag to v38.77.0 (919ed13)
deps: update renovate docker tag to v38.77.2 (2009e09)
deps: update renovate docker tag to v38.77.3 (8a0ce4d)
deps: update renovate docker tag to v38.77.5 (aeffa00)
deps: update renovate docker tag to v38.77.8 (46076e2)
deps: update renovate docker tag to v38.79.0 (3f7fa1f)
deps: update renovate docker tag to v38.80.0 (eb68a01)

v40.2.8
Compare Source
Documentation

update references to ghcr.io/renovatebot/renovate to v38.61.1 (5993be6)
update references to ghcr.io/renovatebot/renovate to v38.72.1 (a4cf16d)
update references to renovatebot/github-action to v40.2.7 (511a7a7)

Miscellaneous Chores

deps: update commitlint monorepo to v19.4.1 (fe52de6)
deps: update dependency @semantic-release/github to v10.1.7 (8d1974e)
deps: update dependency @types/node to v20.16.1 (a5ef441)
deps: update dependency @types/node to v20.16.2 (e2f34af)
deps: update dependency @types/node to v20.16.3 (edf82b7)
deps: update dependency husky to v9.1.5 (18b2dca)
deps: update dependency lint-staged to v15.2.10 (2089929)
deps: update dependency prettier-plugin-packagejson to v2.5.2 (e3c4817)
deps: update pnpm to v9.8.0 (527df8e)
deps: update pnpm to v9.9.0 (8f53e8e)

Build System

deps: lock file maintenance (00a9d0f)

Continuous Integration

deps: update renovate docker tag to v38.54.1 (9e15fe4)
deps: update renovate docker tag to v38.55.1 (ebed852)
deps: update renovate docker tag to v38.55.2 (ea137aa)
deps: update renovate docker tag to v38.55.4 (47bb8fa)
deps: update renovate docker tag to v38.55.5 (8721f4c)
deps: update renovate docker tag to v38.57.0 (c8714d9)
deps: update renovate docker tag to v38.57.1 (3297675)
deps: update renovate docker tag to v38.57.3 (7467495)
deps: update renovate docker tag to v38.58.0 (44c8d6f)
deps: update renovate docker tag to v38.58.1 (da00a9c)
deps: update renovate docker tag to v38.58.2 (cda286d)
deps: update renovate docker tag to v38.59.1 (cf5432f)
deps: update renovate docker tag to v38.59.2 (282b8d8)
deps: update renovate docker tag to v38.61.1 (749b819)
deps: update renovate docker tag to v38.64.0 (71ee52a)
deps: update renovate docker tag to v38.64.1 (7337445)
deps: update renovate docker tag to v38.66.1 (5e5e62b)
deps: update renovate docker tag to v38.67.1 (8639a3d)
deps: update renovate docker tag to v38.67.2 (e7fba3a)
deps: update renovate docker tag to v38.67.4 (114ff35)
deps: update renovate docker tag to v38.67.5 (a0ebccf)
deps: update renovate docker tag to v38.68.0 (d76014f)
deps: update renovate docker tag to v38.68.1 (cd0419f)
deps: update renovate docker tag to v38.70.0 (ab6e4ab)
deps: update renovate docker tag to v38.70.2 (3e30de3)
deps: update renovate docker tag to v38.71.0 (42c77e0)
deps: update renovate docker tag to v38.72.0 (46fcd07)
deps: update renovate docker tag to v38.72.1 (7e74a7b)
deps: update wagoid/commitlint-github-action action to v6.1.2 (1c11596)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

:tada: This PR is included in version 2.0.9 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


2024 Feat:  Magic Initiate

The 2024 version of Magic Initiate only allows for Wizard, Cleric, or Druid spell lists, but it lets you pick your spellcasting  ability for those spells (Int, Wis, or Cha) when you select the feat.  This is a very powerful change (especially for an origin feat) that would be nice to have.

Feats will come after I finish subs and spells.

In order to code this one correctly I’ll have to break backward compatibility. Won’t code these changes.


Add @akaszynski as maintainer

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

@akaszynski, do you consent to being notified by this repo for life?

@akaszynski, do you consent to being notified by this repo for life?

Yes.  Would be helpful to be informed.

I think I just merge this and it'll work? we'll see


The auto detect website doesn't work ask expected.

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open the web.
 Hover on the the website, notice that the tooltip show https://[website-name]  instead of http://[website-name]
Try to click on that website, notice that it opens https website instead of http website and the website can't be opened.

Expected Result:
Tooltip should show the correct website and when user click on that website, it should open the correct url.
Actual Result:
Tooltip shows the wrong url and when user clicks on it, it opens the wrong url.
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

Version Number: 1.2.96-0
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/43996225/230504612-a0784c95-93c4-4ceb-88f0-2ecbd0082463.mov
https://user-images.githubusercontent.com/43996225/230504631-90743828-d50d-47f6-b273-28f0a58ff555.mp4
Expensify/Expensify Issue URL:
Issue reported by: @hungvu193
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1680776520260139
View all open jobs on GitHub

Triggered auto assignment to @sakluger (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

Bug0 Triage Checklist (Main S/O)

[ ] This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
[ ] This bug is not a duplicate report (check E/App issues and #expensify-bugs)

If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead

[ ] This bug is reproducible using the reproduction steps in the OP. S/O

If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
If the reproduction steps aren't clear and you determine the correct steps, please update the OP.

[ ] This issue is filled out as thoroughly and clearly as possible

Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.

[ ] I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

This is not happening for me using the websites http://www.cs.sjsu.edu/~pearce/modules/lectures/web/html/HTTP.htm and http://info.cern.ch/:

If I don't include the beginning part (so if I enter just info.cern.ch), then it defaults to https, but I'm not sure if that's the expected behavior or not. I'll ask in Slack.

If http/https prefix is not provided in the URL, it's expected behavior that we should default to HTTPS for the safer side. Closing as this is expected behavior.


Search readable property when resolving constructor arg type

Should fix #2803
Also added more info to the error message. Related to #2787

Coverage: 87.183%. Remained the same when pulling 43fcd3086d93ffc4bd2b3f6149beb71c7823ec28 on harawata:record-name-only-constructor into 4c8153c7d4242fb88d7b541c1745831d251cfc0d on mybatis:master.

Hey @harawata, this introduced a regression for us, we use to have a construct like this:
public void setDeviceType(String deviceTypeCode) {
    if (!Text.isEmptyOrNull(deviceTypeCode)) {
        this.deviceType = DeviceTypeCache.getDeviceType(deviceTypeCode);
    }
}

public DeviceType getDeviceType() {
    return deviceType;
}

Mapper XML:
<result property="deviceType" column="deviceTypeCode"/>

We relied on the fact that the javaType got determined by the setter, no the javaType is determined by the getter, and we get thousands of errors stating that a type handler could not be found.
In this example the javaType in 3.5.11 was java.lang.String, in 3.5.12 it is acme.company.DeviceType.
It seems to relate to this line:
-        javaType = metaResultType.getSetterType(property);
+       javaType = metaResultType.getGetterType(property);

Im not sure what would be the best way to resolve this, if we have to change all our entities or if we can provide some configuration option that will tell mybatis which method to use for a resultMap to determine the javaType
Also, relevant XKCD 🤣

Yeah...I kind of expected that (and hoped no one does that, but you know).
When fixing #2787 , I stupidly thought it would be helpful if users can omit javaType and that is the reason of this mess.
At this point, only fair solution I can think of is to make the javaType required as it should have been in the first place.
What do you say?
Cc: sp00m tzie0062

Yeah...I kind of expected that (and hoped no one does that, but you know).
When fixing #2787 , I stupidly thought it would be helpful if users can omit javaType and that is the reason of this mess.
At this point, only fair solution I can think of is to make the javaType required as it should have been in the first place.
What do you say?
Cc: @sp00m @tzie0062
Apologies for the double post. Forgot the @s.

By the way, I really would like to avoid adding a new option for this.
If I made javaType required, everyone will complain and I can take it.

Haha, makes sense, I agree that adding an option for something that should
be fixed in a different way is silly.
However if we make it required I think it should be a smart 'required',
i.e: if the getter and setter type are ambiguous...
Else it would force a lot of people to update a crazy amount of code.
What do you think?
On Wed, Mar 1, 2023, 18:19 Iwao AVE! @.***> wrote:

By the way, I really would like to avoid adding a new option for this.
If I made javaType required, everyone will complain and I can take it.

—
Reply to this email directly, view it on GitHub
https://github.com/mybatis/mybatis-3/pull/2804#issuecomment-1450530361,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHEYG4HBSJJG5VXMGC6SFDWZ6AJVANCNFSM6AAAAAAUYACS5E
.
You are receiving this because you commented.Message ID:
@.***>

@epochcoder ,
It sounds reasonable, but for your usage, javaType still will be required, am I right?
I mean, as the read/write types of deviceType don't match, it is considered to be 'ambiguous'.
Please let me know if I misunderstand.

@epochcoder ,
It sounds reasonable, but for your usage, javaType still will be required, am I right?
I mean, as the read/write types of deviceType don't match, it is considered to be 'ambiguous'.
Please let me know if I misunderstand.

Exactly yes, there will for sure still be some work to do on the mapper xml's, given that these are still ambiguous ;-)

Got it.
I will be away for a week or two, but I'll look into it when I am back.
Thank you very much for the report and the idea!

My 2 cents: I could live with a mandatory javaType in the XML however I'd consider this a breaking change and that's not supposed to happen in a minor version update.

The yes that is correct, it should not change such behavior in patch release, change is going to be reverted tonight.

Also impacted by this change, I like the suggested idea to make it required only when it's ambiguous. Alternative could be to even forbid ambiguous cases: the getter and the setter should have the correct type and it's up to the developer to either use a different type or create an extra method.


Keyboard doesn't dismiss when the drawer comes up

When introducing Focus widgets for the Drawer (and ModalRoutes), we weren't
actually giving them the focus. Now we move the focus scope when pushing modal
routes.
Fixes #184

@Hixie

lgtm. we should add some more tests though.

we should add some more tests though.

Added test.


support tuples

Tuples are just ordinary classes, so I don't think that the correct way to add schema for them is to add additional constructors to the Schema enum. Instead, these should be represented as normal object(...) schema with keys like _1, _2, etc.


v6.0.0rc8

Merge pr #232 by @SettingDust
Update dependencies

Coverage remained the same at 97.549% when pulling 6d07fd49e7333508638a840fda3e104d5605c26d on v6.0.0rc8 into a9e1150b23a55b8b53da83b77b19fa6e2f3cfc09 on main.


Homebridge crashes if I include the platform config

As soon as I attach the platform config to my home bridge it crashes.
Here is my config:
{
  "accessories" : [
    {
      "name" : "Pi Temp",
      "accessory" : "RaspberryPiTemperature"
    }
  ],
  "platforms": [
    {
      "platform": "DysonPlatform",
      "name": "DysonPlatform",
      "email"<EMAIL_ADDRESS>      "password": "mypassword",
      "country": "DE",
      "accessories": [
        {
          "ip": "<IP_ADDRESS>",
          "displayName": "Dyson-PureCool",
          "serialNumber": "Vxx-EU-xxxxx80A",
          "sensitivity": 1,
          "nightModeVisible" : true,
          "focusModeVisible" : true
        }
      ]
    }
  ],
  "bridge" : {
    "username" : "11:22:33:44:55:66",
    "name" : "Homebridge",
    "pin" : "031-42-666",
    "port" : 9999
  }
}

And this is the exception I got:
/usr/local/lib/node_modules/homebridge/node_modules/mkdirp/index.js:90
                    throw err0;
                    ^

Error: ENOTDIR: not a directory, mkdir '/root/.homebridge/config.json/persist'
    at Object.fs.mkdirSync (fs.js:885:18)
    at Function.sync (/usr/local/lib/node_modules/homebridge/node_modules/mkdirp/index.js:71:13)
    at LocalStorage.parseDirSync (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/node_modules/node-persist/src/local-storage.js:642:20)
    at LocalStorage.parseDataDirSync (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/node_modules/node-persist/src/local-storage.js:572:21)
    at LocalStorage.initSync (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/node_modules/node-persist/src/local-storage.js:145:14)
    at Object.nodePersist.initSync (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/node_modules/node-persist/src/node-persist.js:41:29)
    at Object.init (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/index.js:31:13)
    at module.exports (/usr/local/lib/node_modules/homebridge/lib/cli.js:24:7)
    at Object.<anonymous> (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22)
    at Module._compile (module.js:643:30)

I installed everything through the Homebridge App and so far everything works fine. The config above is shortened only for the Dyson TP04 and filled with blind data (I'm using the correct data within my real config and currently I have about 30 devices in it).

the error was from homebridge itself so i would think this was related to how you set up homebridge as it seemed that it could not create a directory to save the persist state of device

@joe-ng well the homebridge was installed with the iOS homebridge app. 9 other Plugins run fine without any problem just this one will not start. The directory he wants to use does not make sense because it is impossible to exists. '/root/.homebridge/config.json' is my config file. So "config.json" cannot be a directory and a file at the same time. Therefor it is not possible to create the directoy at '/root/.homebridge/config.json/persist'.
Because all other tried plugins are working without a problem (I tried 17 plugins total and none of them had a problem. Currently there are 9 plugins running), I'm sure this is a fault of this plugin.

This exact thing happens for me too. Homebridge setup via the app. Was any progress made on this?


Type definition of a "callable object"

Hi, I'm writing a definition file for a library. The libraries defines a sort of DSL like:
const get = () => 42;
const obj = () => ({ get: get });
obj.get = get;

which allows the following syntax
obj().get() // 42
obj.get() // 42

Now, I'm trying to model this with flow using a union type

type Resource = {
  get: () => number;
};

declare module 'foo' {

  declare class Foo {
    f: Resource | () => Resource;
  }

  declare var exports: Class<Foo>;
}

But clearly it doesn't typecheck
// @flow

import Foo from 'foo';

const f = new Foo().f;
const x: number = f().get();
const y: number = f.get();

foo.js:6
  6: const x: number = f().get();
                       ^^^ function call. Callable signature not found in
  6: const x: number = f().get();
                       ^ Resource

foo.js:6
  6: const x: number = f().get();
                           ^^^ property `get`. Property not found in
  6: const x: number = f().get();
                       ^^^ Resource

foo.js:7
  7: const y: string = f.get();
                         ^^^ property `get`. Property not found in
  7: const y: string = f.get();
                       ^ Resource

So the question is: how can I express the type of a "callable object"? It's essentially a function with some well-specified properties on it.

there are some docs here, but I don't think they're very clear: https://flowtype.org/docs/quick-reference.html#callable-objects
here's a potentially better example:
type Foo = {
  (): Foo,
  get: () => number
}

function bar(x: Foo) {
  (x().get(): number); // ok
  (x.get(): number); // ok
  (x.foo(): number); // error
}

Face meets palm...
I totally missed that documentation page, thank you @mroch!

https://flowtype.org/docs/quick-reference.html#callable-objects now redirects to a place which is irrelevant. Can someone point out the current correct location for that link please?

It looks like the new version of the docs doesn't have callable objects mentioned anywhere.

https://flow.org/en/docs/types/functions/#toc-callable-objects


large tower section pieces in WW's kremlin/drab scenery pieces from the Europe Theming set do not allow walls to be placed on all four sides

When attempting to build walls around these objects, exactly one side of the object will not allow for wall placement. This becomes especially frustrating when trying to properly renovate From The Ashes.

So, if I’m not mistaken, that’s:

[ ] Nice base
[ ] Drab base 1
[ ] Drab base 2
[ ] Nice mid-section
[ ] Drab mid-section
[ ] Nice top section
[ ] Drab top section

?

Yes.


ARROW-15909: [Python] Log uncaught exceptions in Flight RPC handlers

This isn't perfect because some exceptions are meant to propagate to the client, some are unintended, and it's not always clear which is which, but this should at least make development easier.

This looks good. Simply left minor comments.

Thanks for the review!

It's not clear to me what the intended purpose is. Why not log all exceptions?

Perhaps we can provide such a callback too?

We certainly could; that would be a breaking change. (Well, we could place it in the context, actually - that should be OK.) I'd prefer to tackle that separately, though

Well, the changes in this PR can probably be vastly simplified if we add an error callback.

I think most everything will stay the same, except we wouldn't filter the exceptions we log. (We could probably simplify things, though, if we used self.__log; I'm not a fan of exposing that to user code, even as a name-mangled property, but I don't feel too strongly about it either.)

Note that CPython has a dedicated API to print unraisable errors, you may not need to use the logging module: https://docs.python.org/3/c-api/exceptions.html#c.PyErr_WriteUnraisable

For that sys.unraisablehook() can be overriden. I have no preference personally, but not having to rely on a logger may make things easier compared to your current approach.

Ah, interesting. That should work.

Changed to use PyErr_WriteUnraisable. I still think this is orthogonal to adding an error callback, since either way we need/want to catch uncaught exceptions.
Fun fact, the Cython generated code clears the current exception inside the except block, so it was failing to log the exception…that took way too long to figure out.

Hmm, it looks like you should skip the unraisable hook-based test on Python < 3.8 where the hook doesn't exist.
Also, can you rebase to get the AppVeyor Flight crash fixed?

Filed ARROW-16023 to migrate the server RPC handler API.

@lidavidm Do you want to update this PR?

I don't think I have the time right now, but I'd probably prefer to actually implement ARROW-16023 first, then update this to just log all uncaught exceptions

So closing for now.


Support Node 0.10, 0.12, and early Node 4

We support these node versions in bittorrent-dht and they lack the
new Buffer.from, etc. methods.
safe-buffer provides a buffer with the new methods, or does nothing
if the node version is new enough.

We should probably add v0.10 & v0.12 to the .travis.yml again, to make sure this isn't screwed with in the future. @feross would you like to mend that in here?

@jhermsmeier Done -- updated the .travis.yml file 👍

:+1: @jhermsmeier?


pls update pod version .git

now the pod version is 3.0.3,but the codes are difference from zip.

Just released 3.0.4, thanks.


setChoiceByValue() not working

Version 10.2.0
edit_pid.setChoiceByValue(row.pid.toString());
when I the first use  method "setChoiceByValue" it is working, then use it again not working.

sorry , my  problem.


Risk tear sheet

Risk tear sheet: currently plots style factor weighted exposures, volume exposures, sector exposures.
To add: P&L attribution.
Example graphs can be seen in comments here

Basic risk plots added, with docstrings. Unit tests performed. Attached are screenshots illustrating an example of a risk tear sheet.
To add: P&L attribution

Several other comments:

Make legends slightly opaque in the stackplots, so we can see the colors associated with the sectors/market caps
Modify create_risk_tear_sheet so that the only required input is the positions: if nothing else is passed, simply plot nothing.

Made edits from Gus' feedback; removed 'Date' labels x axis labels, and deleted perf_attrib.py: the PR is now ready to merge with master so that the risk tearsheet is up and running. The plan is to add performance attribution and P&L attribution at a later date.

Kicked off another build now that #395 is merged.

Hi, I'm going to stick my nose into this data viz work :)
For the "rainbow" charts for sector exposures I find it nearly impossible to read the chart and understand which sector is which. The legend is long and difficult to use.
Can you:

actually label the color segments themselves and remove the legend? so the graph 'chunk' itself would be labeled with it's sector.

If that's not possible given the tools we have here
2) can you reverse sort the legend so that the order of the legend matches the order of the chart. Right now it looks like they're totally opposite.

Finally done! Ready to merge @gusgordon

I'm not quite done yet.

Sorry, didn't realize. Will hold off on merging until further feedback

Some more general thoughts:

Before we had utility functions in e.g. positions.py and plotting functions in plotting.py. Here we are grouping the math and plotting functions into the same file. I feel like we should stay consistent. Our options are:

Move all plotting functions into plotting.py
Remove plotting.py and move things into the other files

Data format: There main problem we need to solve is that this PR uses pandas.Panel which is deprecated (https://pandas.pydata.org/pandas-docs/stable/dsintro.html#panel). Thus, at a minimum we should change the Panels to multiindex dataframes. Once we have done this we could go one step further and convert all data to long (I realize this is a major refactor) where dt and sid are the index and columns are position, sector, cap, momentum, reversal, shares_held, energy etc. In that world we only have a single data structure to be passed internally, the risk tear sheet could check for the existence of certain columns and plotting functions extract a list of columns they want to plot. We have ultimately switched to the same format in alphalens under a much higher cost because we have done so much later in the game, but it definitely was worth it, as this format is also much easier to extend. I also think we will want to do something similar for the risk model output as well as for the PnL attribution, so the earlier we bite the bullet the better.

Thoughts @georgh0021, @gusgordon?

As of right now we have three issues that need addressing:

Non-identical dt indexes produce misleading graphs (pretty major bug)
Moving code around into risk.py and plotting.py (for consistency)
Data format: a) deprecating panels and b) changing to long format (for extendability)

1 and 3a have straightforward solutions: those will be my tasks over the next few days.
Wrt 2, I agree we need to stay consistent, but I think it makes more sense to do away with plotting.py and move all plotting functions into their respective modules (reasons below). If we decide on this approach, nothing needs to be done for this PR, but we'll need to open a new one to break up plotting.py.

pyfolio is modularized into separate tear sheets because that's how the user will consume the final product: tear sheet by tear sheet. It doesn't make sense to me to have the functionality of, say, the returns tear sheet split between two different modules.
pyfolio plots much more than it computes: plotting.py clocks in at around 2000 lines of code, whereas most other modules barely make 500. Refactoring so that plotting functions immediately follow their corresponding compute functions would make pyfolio much easier to read.

Wrt 3b, the spirit of long data goes way beyond the risk tear sheet: another long term PR would be to refactor all pyfolio code (i.e. from the returns tear sheet up) so that it's long data in, long data out. This will probably have to wait a while.
@gusgordon?

@twiecki @georgh0021 Agree on removing plotting.py and using the new data format. I vote we should merge this PR (once any loose ends are cleaned up), then we can open another PR where all of that refactoring is done. Do you guys think that makes sense?

Agreed on plotting.py.
I don't agree on 3b. I don't think other parts of pyfolio need to be converted to long, there is only returns (series), positions (wide), and transactions (long), these all seem fine. It's only affecting this PR.

Makes sense. I'll see if I can fix 1) by the end of today, and then we can open up a separate PR to refactor. @twiecki does that sound good?

OK, that's fine.

Fixed problem 1; ready to merge as soon as builds finish @gusgordon @twiecki

@georgh0021 test failed again for the same reason. I would see if you can reproduce it on your computer. Make sure your branch is up to date and rebased with this one (you could just pull pyfolio into a new folder and checkout this branch).

@twiecki there was a bug in test_timeseries.py caused by pandas data reader moving from Yahoo to Google: basically, there was only one drawdown in a test that tested for overlapping drawdowns. It should be fixed now.


intpips failure

mcmaster@cluster:/mnt/m10_2/buffer/prjxray/fuzzers$ time make -j $(nproc)
...
make[2]: Leaving directory '/mnt/m10_2/buffer/prjxray/fuzzers/050-intpips'
+ python3 /mnt/m10_2/buffer/prjxray/fuzzers/int_loop_check.py --max-iters 12 --stable-iters 2
   1 57fef550   7244 lines      1 stable
   2 a59c511c    776 lines      1 stable
   3 b4b06fc2    613 lines      1 stable
   4 68fe99cd    553 lines      1 stable
   5 6e4f2e44    532 lines      1 stable
   6 2bedea7d    522 lines      1 stable
   7 36f77ad5    512 lines      1 stable
   8 10e39d1c    504 lines      1 stable
   9 f5a330b8    501 lines      1 stable
  10 0d922037    498 lines      1 stable
  11 88efea8e    497 lines      1 stable
  12 028c115c    493 lines      1 stable
Complete: reached max iters (want 12, got 12)
+ break
+ true
+ make pushdb
make[2]: Entering directory '/mnt/m10_2/buffer/prjxray/fuzzers/050-intpips'
bash /mnt/m10_2/buffer/prjxray/utils/mergedb.sh int_l build/segbits_int_l.db
+ test 2 = 2
+ test -e build/segbits_int_l.db
++ mktemp -p .
+ tmp1=./tmp.jc9XBDF3uQ
++ mktemp -p .
+ tmp2=./tmp.b3LBqIZI6S
+ trap finish EXIT
+ db=/mnt/m10_2/buffer/prjxray/database/artix7/segbits_int_l.db
+ '[' -f /mnt/m10_2/buffer/prjxray/database/artix7/segbits_int_l.db ']'
+ python3 /mnt/m10_2/buffer/prjxray/utils/parsedb.py --strict build/segbits_int_l.db
Traceback (most recent call last):
  File "/mnt/m10_2/buffer/prjxray/utils/parsedb.py", line 61, in <module>
    main()
  File "/mnt/m10_2/buffer/prjxray/utils/parsedb.py", line 57, in main
    run(args.fin, args.fout, strict=args.strict, verbose=args.verbose)
  File "/mnt/m10_2/buffer/prjxray/utils/parsedb.py", line 27, in run
    bits, tag, bitss[bits])
AssertionError: strict: got duplicate bits frozenset(): INT.IMUX_L13.VCC_WIRE INT.IMUX_L12.VCC_WIRE
+ finish
+ echo 'Cleaning up temp files'
Cleaning up temp files
+ rm -f ./tmp.jc9XBDF3uQ
+ rm -f ./tmp.b3LBqIZI6S
Makefile:39: recipe for target 'pushdb' failed
make[2]: *** [pushdb] Error 1
make[2]: Leaving directory '/mnt/m10_2/buffer/prjxray/fuzzers/050-intpips'
Makefile:69: recipe for target 'run' failed
make[1]: *** [run] Error 2
make[1]: Leaving directory '/mnt/m10_2/buffer/prjxray/fuzzers/050-intpips'
Makefile:36: recipe for target '050-intpips/run.ok' failed
make: *** [050-intpips/run.ok] Error 2

real    475m4.611s
user    7113m38.424s
sys     323m1.788s

These entries are empty. Weird. Maybe we should filter them out?

In general IMUX VCC wires don't seem to solve correctly. Maybe we should filter them out
$ grep -Hni vcc build/*.db
build/segbits_int_l.db:22:INT.BYP_ALT0.VCC_WIRE 31_02 31_26 31_37 31_62
build/segbits_int_l.db:47:INT.BYP_ALT1.VCC_WIRE 30_02 30_25 30_37 30_60
build/segbits_int_l.db:811:INT.IMUX_L12.VCC_WIRE
build/segbits_int_l.db:836:INT.IMUX_L13.VCC_WIRE
build/segbits_int_l.db:1383:INT.IMUX_L34.VCC_WIRE
build/segbits_int_l.db:1408:INT.IMUX_L35.VCC_WIRE
build/segbits_int_l.db:1529:INT.IMUX_L4.VCC_WIRE
build/segbits_int_l.db:1601:INT.IMUX_L42.VCC_WIRE
build/segbits_int_l.db:1625:INT.IMUX_L43.VCC_WIRE
build/segbits_int_l.db:1744:INT.IMUX_L5.VCC_WIRE
build/segbits_int_r.db:22:INT.BYP_ALT0.VCC_WIRE 31_02 31_26 31_37 31_62
build/segbits_int_r.db:47:INT.BYP_ALT1.VCC_WIRE 30_02 30_25 30_37 30_60
build/segbits_int_r.db:813:INT.IMUX12.VCC_WIRE
build/segbits_int_r.db:838:INT.IMUX13.VCC_WIRE
build/segbits_int_r.db:1385:INT.IMUX34.VCC_WIRE
build/segbits_int_r.db:1410:INT.IMUX35.VCC_WIRE
build/segbits_int_r.db:1531:INT.IMUX4.VCC_WIRE
build/segbits_int_r.db:1603:INT.IMUX42.VCC_WIRE
build/segbits_int_r.db:1627:INT.IMUX43.VCC_WIRE

VCC wires are supposed to be dropped:
050-intpips/Makefile:12:MAKETODO_FLAGS=--re ".*" --not-endswith ".VCC_WIRE"
I'm guessing this mechanism is not working

They aren't appearing in the TODO list, but generate.py chomps whatever it finds. It has a few excludes, but it needs to be expanded I guess
        if pnum == 1 or pdir == 0 or \
                re.match(r"^(L[HV]B?|G?CLK)(_L)?(_B)?[0-9]", src) or \
                re.match(r"^(L[HV]B?|G?CLK)(_L)?(_B)?[0-9]", dst) or \
                re.match(r"^(CTRL|GFAN)(_L)?[0-9]", dst):
            ignpip.add(pip)


[DO NOT MERGE] Mesa 24.1

Description of changes
Much hack. Many oof.
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

Also fixed the fixme.

rc2 is out, if you want to update the draft

Confirmed RC2 builds, pushed.

rc3 was just released, could you check if there any regressions?
And out of pure curiosity, was there any kind of regression between rc1 and rc2?

No issues on either rc2 or rc3. That said, updated.

-rc4 works fine, also added xcbutilkeysyms to enable the Vulkan WSI to capture traces when a hotkey is pressed.

Quick note, newer versions break for me in some local testing, requiring the code from upstream MR № 26680 (as a patch) to compile.

24.1 is out

Updated to 24.1.0 release, no issues here.

Been testing this for a few days(AMD Drivers, Ryzen 7640HS CPU), and I'm seeing much better stability and performance than current main branch.

Tried on an Nvidia GPU (RTX 4090) to test the new NVK drivers with Vulkan 1.3 support, but unfortunately no Vulkan app launches (getting segmentation faults and out of memory errors on start). I don't think this is NixOS specific though, looks like my hopes for Nvidia on Mesa 24.1 were a bit too high. :') OpenGL works fine (tried Firefox, some WebGL websites, YouTube videos in 4K, Epiphany, glxgears) and is even quite performant (~70% of the FPS I see on proprietary drivers for glxgears with swapinterval 0).

Any ETA on this?
The 24.1 release of Mesa is quite important to me and to support modern ARM SBCs, as it includes support for the Mali-G610 found in RK3588-based SOCs, in boards such as the Orange Pi 5 or Radxa Rock Pi 5

We follow upstream Mesa guidance and don't ship .0 releases. Mesa 24.1.1 should be out in a few days, and we will ship that after a staging cycle.

Any ETA on this? The 24.1 release of Mesa is quite important to me and to support modern ARM SBCs, as it includes support for the Mali-G610 found in RK3588-based SOCs, in boards such as the Orange Pi 5 or Radxa Rock Pi 5

Also, Asahi driver is included.

Just changing the version and hash in this PR from what it currently is at to this builds fine. No other changes needed.
version = "24.1.1";
hash = "sha256-ADiCbG9+iNkLTOb3GRkvpYyn3t9O3KoRdM972SDvieo=";

Building a bunch of stuff locally to confirm, will merge after.

x86_64-darwin is broken: https://hydra.nixos.org/build/262379171
(aarch64-darwin perhaps as well; waiting for rustc fix first)


Adds docusuarus documentation

This creates a homepage for defiwrapper, and styles and organizes the documentation in a way that's easier to read and comprehend:

@Niraj-Kamdar I attempted to just copy over the contents of the "documentation" repo into it's own directory here, and while it worked locally, it doesn't seem to actually show up in my git commits. I'm guessing it's because the documentation has it's own package.json, but curious if you've done anything like this before. Would it be helpful if I sent over a compiled zip file of the directory?

It maybe because it has its own git file that you forget to delete.

This looks really awesome! It would be nice if we can also add how-to-guides and usage guides in the docs.


g:gutentags_resolve_symlinks=0 not working

Describe the bug
Setting named setting (which should be default) doesn't seem to be working. I have a git repo that has a symlink that points to a directory in a homedir;
opening a file in said repo triggers tags generation, and I can see projects from the symlink are resolved, resulting into tag file of multiple hundred lines long.
Steps to reproduce

Have a project similar to this:

    /path/to/my/project
    ▸ backups/
    ▸ configs/
    ▾ home/
        ▸ bin/
        ▾ dev/ -> /data/dev/
            ▸ projects/  <-- this contains loads of directories that'll get processed

Open a file in /path/to/my/project (that's not on a symlinked path when looking from /path/to/my/project)
/path/to/my/project/.tags will contain tags from projects under /data/dev/projects

Share your setup

debian buster, NVIM v0.2.0-780-g087acd79
Exuberant Ctags Version 5.9~svn20110310
Are you using g:gutentags_cache_dir?: nope

Post the logs

Run :let g:gutentags_trace = 1.
Reproduce the bug.
Run :messages and show the messages that Gutentags posted.

    "/path/to/my/project/file.sh" 4675L, 168929C
    gutentags: Scanning buffer '/path/to/my/project/file.sh' for gutentags setup...
    gutentags: No specific project type.
    gutentags: Setting gutentags for buffer '/path/to/my/project/file.sh'
    gutentags: Generating missing tags file: /path/to/my/project/.tags
    gutentags: Generating wildignore options: /tmp/nvimgmmVkR/4
    gutentags: Running: ['/home/laur89/.vim/bundle/vim-gutentags/plat/unix/update_tags.sh', '-e', 'ctags', '-t', '.tags', '-p', '.', '-o', '/home/laur89/.vim/bundle/vim-gutentags/res/ctags_recursive.options', '-x', '@/tmp/nvimgmmVkR/4', '-l', '.tags.log']
    gutentags: In:      /path/to/my/project
    gutentags: [job output]: ['Locking tags file...', '']
    gutentags: [job output]: ['Running ctags on whole project', 'ctags -f ".tags.temp"  --options=/home/laur89/.vim/bundle/vim-gutentags/res/ctags_recursive.options --exclude=@/tmp/nvimgmmVkR/4 .', '']
    gutentags: [job output]: ['ctags: Warning: Language "Go" already defined', '']

Also bunch of lines like
gutentags: [job output]: ['ctags: Warning: cannot open source file "home/dev/projects/some_project/node_modules" : No such file or directory', '']

which demonstrates it is trying to resolve symlinks.
Note the path in that warning is /home/dev not /data/dev, because /path/to/my/project is a homeshick castle (everything under ./home/ will be symlinked from ~ for easier dotfile management)

Look for the tags.log file that Gutentags' script left behind, and post its contents.
Generation takes ages, no `.tags.log' yet.

All my plugin config is
    let g:gutentags_trace=1
    let g:gutentags_ctags_tagfile = '.tags'
    let g:gutentags_resolve_symlinks=0

the following workarounds are possible:
" ctags
let g:gutentags_ctags_extra_args = ['--links=no']

" gtags
let $GTAGS_ARGS = '--skip-symlink'


Add "Toggle Forbidden Store" to context menu, colorizes, and add preference

Adds the ability to toggle forbidden stores as shown in picture.
Colorizes the store a nice red if forbidden.
Adds a preference "showForbiddenStores" which defaults to false.
This also formats #369 it to be easier to read.

There have been a few changes from veracity underneath you but they should help


Remove mc and integration tests

Part of https://github.com/deis/minio/issues/1 prescribed the following requirements:
Requirement 1:
Create a Minio MC pod to be used for testing Minio from within a Kubernetes cluster (#19)

Requirement 2:
Write an entry point on the MC pod that will run integration tests against the Minio RC to verify that it is up, running, and correctly configured. (#19)

These two requirements led to the creation of a mc directory and an integration directory under it. The direct contents of the mc directory are intended to build the mc CLI, and then the mc/integration directory is meant to package that CLI and an integration test (implemented as a bash script) into an image. The idea behind the integration testing image was to allow anyone to run it in a pod so it can run some basic CRUD operations against a running minio server to see if it's properly set up and running (i.e. ensure it's configured with the credentials that are stored in the object storage creds secret, it's running, its filesystem is properly set up, etc...)
We've since created e2e tests which have exceeded the functionality of these tests, we haven't automated these integration tests, and we don't automatically create the integration test image.
This proposal issue is for removing the mc directory entirely, which would hence remove the build scripts for the mc CLI and the Dockerfile and image creation targets for integration tests.
Of course, if we do decide to pursue integration tests in the future (another larger discussion), we can revive the integration test script and image creation logic (and we'll need to automate test runs).
This issue would obviate #99

While local integration tests would obviously be great, Workflow does effectively have test coverage of deis/minio thanks to the e2e test suite. Improving test coverage and quality is still the overall focus, but in this area the current priority is covering S3 and GCS storage instead.
I think it's safe here to simplify and remove the mc directory. 👍


Release assets should be always uploaded

UpdateChangelogAndUploadPackages doesn't upload a new release asset if an old one with the same name is already attached to a release.
While implementing #37, I noticed that the new asset and the old asset have different hashes.
This breaks generating the scoop manifest since the manifest is updated using the asset of the new asset.

The problem is how to detect that the asset hasn't changed? Usually if I need to reupload a release, I delete it entirely and manually.
It is the same for homebrew, the assets have to be generated at the same time. You could add an option to force update the assets maybe and to fail if this option is not set and assets already exists?

You could add an option to force update the assets maybe and to fail if this option is not set and assets already exists?

I'll do this


optimizer.apply_gradients fails inside tfe.defun

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes.
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): colab
TensorFlow installed from (source or binary): colab
TensorFlow version (use command below): unknown 1.6.0
Python version: 3.6.3
Exact command to reproduce: Colab: https://drive.google.com/file/d/1zj9IMWKF58TuEQRKt9DpETr24Z1sy9z0/view?usp=sharing

Describe the problem
optimizer.apply_gradients doesn't seem to work inside eager mode's tfe.defun.  The colab contains full details, but the relevant part of the exception is
/usr/local/lib/python3.6/dist-packages/tensorflow/python/training/optimizer.py in _get_processor(v)
    180   if context.in_eager_mode():
    181     return _DenseResourceVariableProcessor(v)
--> 182   if v.op.type == "VarHandleOp":
    183     return _DenseResourceVariableProcessor(v)
    184   if isinstance(v, variables.Variable):

/usr/local/lib/python3.6/dist-packages/tensorflow/python/ops/resource_variable_ops.py in op(self)
    601   def op(self):
    602     """The op for this variable."""
--> 603     return self._handle.op
    604
    605   def eval(self, session=None):

/usr/local/lib/python3.6/dist-packages/tensorflow/python/framework/ops.py in op(self)
    836   @property
    837   def op(self):
--> 838     raise AttributeError("op not supported for Eager Tensors.")
    839
    840   @property

AttributeError: op not supported for Eager Tensors.

The problem is presumably that optimizer.py's eager mode logic is disabled by defun's graph mode.
Source code / logs
Reproducing colab: https://drive.google.com/file/d/1zj9IMWKF58TuEQRKt9DpETr24Z1sy9z0/view?usp=sharing

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Bazel version
CUDA/cuDNN version
GPU model and memory

Bazel version: via colab
CUDA/cuDNN version: via colab
GPU model and memory: via colab

@akshayka can you take a look?

Sure thing, currently investigating ...

Thank you!


(FACT-2668) Networking fact on linux should have logic for selecting IPs

CLA signed by all contributors.


Typescript SDK and setVersionName

Summary
With the JS-SDK we where able to do something like the following to identify the Web-App version:
 client.setVersionName(RELEASE_VERSION);

What is the equivalent in the Typescript-SDK?

Hi @FQ400! Thanks for submitting a question! Is the release version known at time of init() call?
With this SDK consuming a new amplitude analytics HTTP API, this is now referred to as app_version in the request payload. You can assign a value in init() call for example:
amplitude.init(API_KEY, OPTIONAL_USER_ID, {
  appVersion: RELEASE_VERSION,
});

Thank you that worked


Adjust formatting in Clojure example

It's customary in Clojure to group parentheses at the end of a line
Predicates in Clojure are named with a ? suffix, rather than a p

This change is

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/3e4837d7300e5b9b639375ef8ae04b15f76ec4ed/


Add target and change update handlers api

Fixes #68
/cc @johnhaley81

If @endlo doesn't have anything to add then this looks gtg to me

Published 4.0.0-beta.3.


Binary Classification

Revamp directory structure
Create a directory for Binary Classification
Add main repo Readme  and sub-directory Readme's

now merge/delete


Update to sdk v0.3.0 and v1 proto

Description of your changes

Update to function-sdk-go:v0.3.0
Update to crossplane-runtime v1.17.0
Update imports to v1 protoBuf definitions from v1beta1
Update tests to include new Target
Update golangci-lint to 1.62.0
Update go to 1.23.3

Fixes #135
Note that Crossplane-runtime v1.18.0 causes some breaking changes with function-sdk-go, which is why this PR only covers the upgrade to 1.17.0.
I have:

[x] Read and followed Crossplane's contribution process.
[x] Added or updated unit tests for my change.

🤔 functions were promoted to v1 in 1.17, so, if we bump to v1 will this work with Crossplane 1.16 which is supported until Feb 2025? should we hold back the upgrade to v1 until then or at least set the xp constraint in the meta package.

You are right, @jbw976, forgot about the automagic conversion 🎉 then LGTM!


[Feature] CatFrames for offline data

Description
Allows CatFrames to work with offline data.
Upcoming: The tensordict provided must have its last dimension marked as time.
As of now the tensordict provided is loosely assumed to have its last dimension being the time dimension.
cc @BY571

Added padding @BY571

Added padding @BY571

Looks great to me!


Pull replication failed for large pull

Using CBL Android 1.2.0-sqlite
I was using https://github.com/couchbaselabs/GrocerySync-Android targeting a demo server http://demo-mobile.couchbase.com/grocery-sync/ with 121436 updates. The pull replication failed after a few minutes with the following stack trace.
01-21 11:40:33.321 19166-19179/? V/View: Re-indexing view: grocery-local/byDate
01-21 11:40:33.321 19166-19179/? V/Database: CBLManagerWorkExecutor Begin transaction (level 0)
01-21 11:40:33.321 19166-19179/? E/View: Cannot index view grocery-local/byDate: no map block registered
01-21 11:40:33.321 19166-19179/? V/Database: CBLManagerWorkExecutor CANCEL transaction (level 0)
01-21 11:40:33.331 19166-19179/? E/Query: Exception caught in runAsyncInternal
                                          com.couchbase.lite.CouchbaseLiteException: Cannot index view grocery-local/byDate: no map block registered, Status: 400 (HTTP 400 bad_request)
                                              at com.couchbase.lite.store.SQLiteViewStore.updateIndexes(SQLiteViewStore.java:290)
                                              at com.couchbase.lite.View.updateIndexes(View.java:321)
                                              at com.couchbase.lite.View.updateIndex(View.java:294)
                                              at com.couchbase.lite.Database.queryViewNamed(Database.java:2114)
                                              at com.couchbase.lite.Query$2.run(Query.java:483)
                                              at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:422)
                                              at java.util.concurrent.FutureTask.run(FutureTask.java:237)
                                              at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:152)
                                              at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:265)
                                              at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
                                              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
                                              at java.lang.Thread.run(Thread.java:841)
01-21 11:40:33.331 19166-19179/? D/Sync: firing trigger: WAITING_FOR_CHANGES
01-21 11:40:35.521 19166-19179/? D/Sync: com.couchbase.lite.replicator.PullerInternal@42ba0308: saveLastSequence() called. lastSequence: 17429 remoteCheckpoint: {_rev=0-28, lastSequence=17040}

@sethrosetter ,
Can you provide device information you used?

Nexus 5 running Kit Kat - Android 4.4.4

2016/01/26

Nexus 6  (Android 6.0.1) Successfully pulled all revisions twice without this error
Nexus 9 (Android 6.0.1) Successfully pulled all revisions without this error
Samsung S3 (Android ) - testing

Using b733898d1f9441b682e605ab478fb207820befe3 and Nexus 5 - Android 4.4.4,
Successfully pulled all revisions twice.

Misc notes:
Smells like a race condition, so I started back-tracking from the location of the exception. I noticed that the call to setVersion isn't wrapped in a RunInTransaction block. Any chance there's a race condition here, e.g. multiple HTTP responses interleaving? If so, this block could result in two threads trying to create the view at the same time.
There are some scenarios in Activity-based Android apps where the onCreate will fire twice, such as screen rotation and low-memory. We could be leaking by holding the activity context instead of the application context in Grocery Sync.

@zgramana you are correct. I was able to replicate this issue by rotating during a long pull - https://github.com/couchbaselabs/GrocerySync-Android/issues/41

this is caused by GrocerySync Activity handling.  So I will close this.


FOUC on pages

Experiencing FOUC on some pages.

As discussed here, this seems to be a sidekick issue. @jindaliiita , could you please open an issue in https://github.com/adobe/helix-sidekick-extension/issues

Yes
Opened one https://github.com/adobe/helix-sidekick-extension/issues/607


How to get snapshot diffs in Mochawesome Reporter

Hi, I'm trying to add the snapshot diff to the test context so it'll appear in my Mochawesome Report.
Is there a way for me to get the diffOutputPath in the on:after:test callback so I can add it to the test context?
I saw that you write test result metadata to a file cache so that your reporter can generate it's report, but I'm unable to access this file cache in that callback as I believe it's client side.
Thanks!

Any updates on this please?

@jrhone @lukasmatiasko Are you guys able to add the snapshot diff to the test context to show in Mochawesome Report?

Hi, I found a solution and I posted it on stackoverflow : https://stackoverflow.com/q/62141050/9540653

How can we get the value of "diffOutputPath"? change to use relative path instead of absolute path


Postgres v15 migration

Bug report
Describe the bug
New projects with postgres v15 conflicts with config.toml. Previous versions were working correctly.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:

Create new supabase project (new projects use postgres-15 instance).
Get server major_version by running SHOW server_version in remote instance.
Set db major_version = 15 in config.toml.

Expected behavior
Migration should work as expected.
Screenshots
v14 related images

v15 related images

github-actions workflow:

System information

OS: ubuntu 22.04
Version of supabase-js: "@supabase/supabase-js": "^2.2.0"
Version of Node.js: v18.12.1

Hi, in your setup-cli action, you can change the version from 1.0.0 to latest cli 1.26.9 to resolve this issue.

Hi @sweatybridge great catch! My bad.
Thank you. Closing this now.
Awesome blazingly fast reply! 🔥 ⚡


MySQLnd?

"Please install mysqlnd!
Terminating for security reasons"
What should I do to fix this?
I understand the module has to be installed, and my web server is running on CentOS 6.5, but I just don't know how to do it...
Your instructions only include the Debian method, and the package name isn't the same for CentOS.

http://stackoverflow.com/questions/13159518/how-to-enable-mysqlnd-for-php

"yum install php-mysqlnd is only available on CentALT and maybe remi repos. Webtatic also has some good php repos as well. It is NOT on the default ones (I was using CentOS)."
None of the solutions on that page work for me.

As far as I know centALT doesnt exist anymore. yum is the package manager centos uses. Remember to uninstall the mysql extension first

Are you using a php mysql stack such as xampp or are you using a lamp setup?

I'm actually using the stack that comes with VestaCP (web control panel)
Attempting to "yum install php-mysqlnd" just results in "no package found"

Your on your own, I have never used centOS. If you use a paid linux host, they might use their own repo so use the default centOS one.

"yum install php-mysqlnd is only available on CentALT and maybe remi repos"
Have you tried:
yum --enablerepo=remi,remi-test remove php-mysql
yum --enablerepo=remi,remi-test install php-mysqlnd


The table displayed by pandas::DataFrame::sort_value() method is not sorted by the specified column

In the image, the second table shown should be sorted by column 'A'.
>>> import pandas as pd
>>> import numpy as np
>>> df = pd.DataFrame(np.array([[2, 3, 4], [1, 1, 1], [4, 1, 0]]), columns=['A', 'B', 'C'])
>>> df
   A  B  C
0  2  3  4
1  1  1  1
2  4  1  0
>>> df.sort_values('A')
   A  B  C
1  1  1  1
0  2  3  4
2  4  1  0
>>>

This bug is related to issue #2753

Thanks for the bug report.  I think the solution to both of these is in the ability to deliver formatting info to the client.  We are adding this now for JVM languages (https://github.com/twosigma/beaker-notebook/issues/3596), and it's the same idea to add it to the serializer for Pandas as well.

In core/src/main/web/outputdisplay/bko-tabledisplay/bko-tabledisplay.js we have
if (!scope.colorder) {   scope.colorder = _.range(scope.columnNames.length + 1); } ... scope.refreshCells(); ... for (i = 1; i < $scope.columns.length; i++) {   $scope.getCellIdx.push(i - 1);   var order = $scope.colorder[i]; ... }
That means that default ordering should be set and is set to sequence from 0 to columns count + 1.
Determine ordering by data is not possible - for this case we have [[4, 1, 0], [2, 3, 4], [1, 1, 1]] - server ordering and no hint by which column and direction.

https://github.com/twosigma/beaker-notebook/commit/41314c42db6d5e0f2894c8bbe81c6d7251395a46


[KeyVault] Use @azure/core-http in keyvault-* to enable @azure/identity use

This change enables the use of @azure/identity in @azure/keyvault-keys and @azure/keyvault-secrets by switching the dependency of @azure/ms-rest-js to @azure/core-http.  It proves the integration works by using @azure/identity's EnvironmentCredential inside of the unit tests of both libraries instead of the credential from @azure/ms-rest-nodeauth.
To make this integration work, I had to hand-edit the code generated by AutoRest to remove the types specific to @azure/ms-rest-azure-js since we don't have an Azure.Core library for that yet (it's coming in #3584).  This hand-edited integration will be used as the basis for updating autorest.typescript to add an option for generating output source with the appropriate Azure.Core references.
An important thing to note is that the AAD_* environment variables that were previously used for KeyVault tests have now been renamed with an AZURE_* prefix since that's what EnvironmentCredential expects.

@daviwil - Looks good from my side. Eager to get the code autogenerated once this lands.

Yep, I'll be updating the autorest.typescript library this week and I'll regenerate this code from that once it works! Just wanted to get this PR out to start the integration process since we're tight on time.

I've got autorest.typescript updated (https://github.com/Azure/autorest.typescript/pull/447) to output code using @azure/core-http and @azure/core-lro (coming in #3584).  I've updated keyvault-keys and keyvault-secrets to have code that's been generated by these changes with some Prettier formatting after the fact.  CI will on this PR will fail until the aforementioned PR is merged (I'll get that done Tuesday).

Fixed up the code to get it closer to what it was before I hand-edited the generated parts so we now have the most minimal set of changes possible.  If there are no objections, my plan is to rebase this PR after #3584 gets merged, wait for CI to go green, and then merge it.
Please let me know if you have any other thoughts or concerns about the changes here!

Quick update on this: since @bterlson and I weren't sure whether it was a good time to migrate over @azure/ms-rest-azure-js I decided to try and generate the keyvault-keys code using AutoRest without the --azure-arm flag applied (this removes the dependency on ms-rest-azure-js).  It turns out that keyvault-keys actually does use something from that library: the support for paged API requests.
Tomorrow I'll start looking into how we can migrate over ms-rest-azure-js in a way that better fits into our long-term plans so that we can make progress with this PR.

OK, I've finally got all 3 keyvault libraries updated with newly generated ServiceClient code that supports paged results without the need for @azure/ms-rest-azure-js.  @jonathandturner, do you mind looking over the changes I made to the sample files and index.ts files of all 3 libraries to see if the changes look good?
Most of the changes in the generated code files are from renaming msRest to coreHttp, but there are some removals in places because we're not using the full "azure-arm" code generation setting anymore (it's not needed for these libraries).  Feel free to scan over those as well but prepare for a mind-numbing experience :)
Would love to get this merged around midday today!

@daviwil - Looks good. Let's ship it!

Merging it, thanks all!


I can't run the script on the second run. Worked fine the first time!

Was working fine on the first run. I closed it (pressed x close button on terminal). Next time I run it, it gives me the error attached.
Other Information
OS: Ubuntu 16.04 LTS x64

did you do the virtualenv version before? If so you have to do it every time before starting the bot

Can't believe I missed that - multiple times! Thanks.


Add bzl_library targets

These are useful for stardoc from other rules repos

CI failing until https://github.com/bazelbuild/rules_proto/pull/64 is merged

CI failing until #64 is merged

Done.

Updated!


(Question) Can we specify backend=false

I see options for passing backend configuration to terraform init.
BackendConfig            map[string]interface{} // The vars to pass to the terraform init command for extra configuration for the backend

However, cannot figure out how to suppress backend configuration. This would be equivalent to terraform init -backend=false.
Thanks

The -backend param is not currently exposed in terraform.Options. PR to add it is welcome!

Is this issue resolved?

The -backend param is not currently exposed in terraform.Options. PR to add it is welcome!

@brikis98  - I need this too - submitting a PR in the next 10mins.
Also to avoid any future holdups like this we should extend the options with an arbitrary flags that get appended to the TF commands.


Support "alias" data type for fields

Elasticsearch 6.4 now supports adding field aliases to an index, say to map "familyName" to "family_name" in mappings.  This feature would make working with Spring Boot Elasticsearch much easier.

This would be available as soon as the elassandra 6.4.x.x will be released

Elassandra <IP_ADDRESS> is out, with support for field alias.
Thanks in advance for your feed back.


[th175] Translating a image could crash the game

th175/data/sprite/player_murasa/water_use_font.gif ←this one
When the translated image is displayed in the game, the game would freeze and then crash,
making Murasa's tutorial stage impossible to complete.

↑Where the crash happens

For both lang_en and lang_zh-hans you uploaded PNGs for th175-data-sprite-player_murasa-water_use_font.gif, what if you uploaded actual GIFs instead? I see lang_hu did that and I don't remember their crew mentioning a crash. You can create GIFs with something like ezgif

wow it worked! thank you!
I'll update those images now

Fixed.
Solution: Use actual GIFs instead.

Fixed.
Solution: Use actual GIFs instead.


Add a contentType parameter for uploadFile and uploadFileMultipart

Hello,
Would you be open to adding a contentType parameter for uploadFile and uploadFileMultipart ?
It would then need to be passed through:

CreateMultipartUploadRequest
PutObjectRequest

I believe that the default value is binary/octet-stream.
Happy to open a PR if that works for you!
Thanks,
Max

I actually took a closer look at the code and realized that using AwsRequestModifier.Upload1 and AwsRequestModifier.MultipartUpload might be the preferred way, is that correct?


Holding the grip button causes the player to walk slowly, and slow down to almost a standstill at edges.

The issue is caused by the "roll" bind, which is also bound to a walk in code.
This behavior is present in the base game, but it is a bigger issue in NomaiVR, where certain puzzles require you to have your scout launcher equipped by pressing the grip button, which is also bound to roll.
Video demonstration of the bug here:
https://user-images.githubusercontent.com/63358288/175876105-b99de8cd-82e9-4d7c-aa52-cbf59688acdc.mp4
A comparison between a hand with roll unbinded and one with roll bound to grip.
https://user-images.githubusercontent.com/63358288/175876445-0419f6f5-00a5-44ad-9ae2-a65bf406438d.mp4
Potential Fix: Disable the roll bind on the hand that is currently holding a tool.

Forgot to close this, it was fixed in 2.7.0


Stackoverflow

With points (1.01, 101.01),(1.01, 101.5),(1.5, 101.5),(1.5, 101.01), it gets stackoverflow.  Please check it.

Same issue here. Will try @josdejong solution.

Since this is a self-calling method (inside a while loop, no less) adding bounds-tests around
https://github.com/Merowech/java-concave-hull/blob/master/ConcaveHull.java#L250
and
https://github.com/Merowech/java-concave-hull/blob/master/ConcaveHull.java#L276
could prevent the overflow, but doesn't solve the fact that the algorithm isn't converging on a solution in iteration at these cases. Investigating line-segment intersection and in-polygon tests.


Be more intelligent on the continuous attack

Find a way to retreat if we are sure to lose the battle. 2-3 marines vs 2-3 stalkers.
This is complex and relative.

Search for : bool Squad::needsToRegroup() const    in Squad.cpp         We only need to find a condition for regrouping.

I did just a minimum regroup condition.

To evaluate if we should retreat, we could count the known enemy army supply vs ours.

We can at least have a minimum number of units the enemy has (based on what we saw). And when we kill units, we deleted them from the minimum number.

I added MicroManager::getUnitPower() that allow us to calculate the power a our units vs enemy units so be can back when it's too dangerous.


No way to attach ssl_certificate_id from module output- work only with plain-text based input

Hello,
How I can attach ssl_certificate_id from another module output? Now module accept only plain-text based attach.
Example of ssl_certificate_id attachment
listener = [       {         instance_port     = 80         instance_protocol = "HTTP"         lb_port           = 80         lb_protocol       = "HTTP"       },       {         instance_port     = 443         instance_protocol = "HTTPS"         lb_port           = 443         lb_protocol       = "HTTPS"         ssl_certificate_id = "${module.certificate1.cert_arn}"       },     ]
And effect in apply
+ listener {           + instance_port     = 443           + instance_protocol = "HTTPS"           + lb_port           = 443           + lb_protocol       = "HTTPS"         }       + listener {           + instance_port     = 80           + instance_protocol = "HTTP"           + lb_port           = 80           + lb_protocol       = "HTTP"         }
But when I type any plain-text based arn in ssl_certificate_id it's look like working.

Hi,
Make sure you create a certificate before calling this module, for eg:
terraform apply -target=module.certificate1
terraform apply

Okay, I define wrong cert for not correct environment...


[$250] Web - Search - Empty state page skeleton is cut off from the right

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 9.0.68-0
Reproducible in staging?: Y
Reproducible in production?: Y
Issue was found when executing this PR: https://github.com/Expensify/App/pull/51913
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Issue reported by: Applause Internal Team
Action Performed:

Navigate to staging.new.expensify.com
Navigate to Search
Observe the background skeleton empty state on the right side

Expected Result:
The oval skeleton doesn't get cut off from the right
Actual Result:
The oval skeleton gets cut off from the right when there is a scroll bar on the right
Workaround:
Unknown
Platforms:

[ ] Android: Standalone
[ ] Android: HybridApp
[ ] Android: mWeb Chrome
[ ] iOS: Standalone
[ ] iOS: HybridApp
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~021865178692528155887
Upwork Job ID:<PHONE_NUMBER>528155887
Last Price Increase: 2024-12-06

Issue OwnerCurrent Issue Owner: @

Proposal
Please re-state the problem that we are trying to solve in this issue.
The search page skeleton right side is cut off when there is a scrollbar.
What is the root cause of that problem?
This is how the calculation looks to decide the position of the right-most skeleton. We want to right-aligned the skeleton.
https://github.com/Expensify/App/blob/64eaf2fdd357bd06008adfb9c0c049e09cd375b9/src/components/Skeletons/SearchRowSkeleton.tsx#L178-L180
The problem here is that when there is a scrollbar, the width of the search central pane is reduced, but since we used the windowWidth - lhn width to get the central pane width, the value is the same because windowWidth isn't reduced when there is a scrollbar. So, the skeleton position doesn't change either, thus getting cut off.
What changes do you think we should make in order to solve the problem?

To solve it, first, we can get the width of the skeleton container from onLayout
https://github.com/Expensify/App/blob/64eaf2fdd357bd06008adfb9c0c049e09cd375b9/src/components/Skeletons/SearchRowSkeleton.tsx#L124
const [containerWidth, setContainerWidth] = useState(0);

<View style={[styles.flex1, containerStyle]} onLayout={(e) => setContainerWidth(e.nativeEvent.layout.width)}>

Then, use the containerWidth on the calculation like this:
x={containerWidth - rightSideElementWidth - gapWidth - centralPanePadding}

We need to do the same for this skeleton
https://github.com/Expensify/App/blob/64eaf2fdd357bd06008adfb9c0c049e09cd375b9/src/components/Skeletons/SearchRowSkeleton.tsx#L170-L172
x={containerWidth - rightButtonWidth - gapWidth - centralPanePadding - gapWidth - rightSideElementWidth}

What alternative solutions did you explore? (Optional)
Since we don't show scroll indicator for scroll page,
https://github.com/Expensify/App/blob/64eaf2fdd357bd06008adfb9c0c049e09cd375b9/src/components/Search/index.tsx#L491
we can just hide it for the skeleton too by passing the showsVerticalScrollIndicator to EmptyStateComponent.
https://github.com/Expensify/App/blob/64eaf2fdd357bd06008adfb9c0c049e09cd375b9/src/pages/Search/EmptySearchView.tsx#L200-L211
and then use it here.
https://github.com/Expensify/App/blob/64eaf2fdd357bd06008adfb9c0c049e09cd375b9/src/components/EmptyStateComponent/index.tsx#L85-L88

Hi @deetergp and @Pujan92 - this is related to https://github.com/Expensify/App/pull/51913, so assigning you to review.

Waiting on @deetergp and @Pujan92 to weigh in

@bernhardoj's proposal sounds reasonable to me. What do you think @Pujan92?

Yes @deetergp but I am not able to reproduce it in my system.
https://github.com/user-attachments/assets/259acb8a-39b2-4b0a-a7ac-d527b416f874

@Pujan92 please try to always show the scrollbar

I am 👍 with the @bernhardoj's alternative solution of passing showsVerticalScrollIndicator prop to the ScrollView.
🎀👀🎀 C+ reviewed

Please disregard @shawnborton — I accidentally clicked the wrong tag :ohnothing:

PR is ready
cc: @Pujan92

Is this some kind of regression or was it always set up this way? cc @filip-solecki

Tbh it's hard to say, maybe there were some changes that broke up the calculations or it is uncovered scenario.

@kadiealexander the payment date for this falls for when I am OOO, but before I go, I'll prep the summary - can you pay it please?

Payment Summary

C: @bernhardoj $250 (to be paid via ND)

@deetergp @Pujan92 this is the only payment, correct?

@jliexpensify this isn't a regression of the mentioned PR, and it is a new fresh issue. So I am also eligible for the payment.

Cool, thanks for letting me know - will add you in.

Hi @deetergp - I'm headed OOO from the 18th - 29th, do you mind closing this GH when the payment date passes?
Payment Summary is here.
@Pujan92 - is there a need for a checklist?

Hi @deetergp - I'm headed OOO from the 18th - 29th, do you mind closing this GH when the payment date passes?

Will do @jliexpensify! Enjoy our OOO time 🎉

Thanks Scott, have a great Holiday Break!
@Pujan92 since it's my last day today, I want to confirm that there's no checklist?

@jliexpensify I think checklist isn't needed here.

Great, thanks - in that case, Scott can simply close this on the 19th if there are no regressions.

$250 approved for @Pujan92

Requested in ND.

$250 approved for @bernhardoj based on this summary.


Fixed Issues regarding Filter, There were issues in dictionary search

Fixed Issues regarding Filter, There were issues in dictionary search  for range filters if filter members contains Null.
Also handled the scenario where unsupported data type is been returned by Spark

retest this please

Handled review comments from ravindra.

@sujith71955 Please don't do many changes for throwing FilterUnsupportedException, we already throwing checked exception QueryExecutionException it is good to enough to be generic for all types of exceptions. Any other new exception like FilterUnsupportedException can be wrapped by QueryExecutionException and throw

retest this please

retest this please


Add DTS support for winc1500

Added support for using DTS for the winc1500 driver.

@tbursztyka wanted to push this for your comments, still working on it.

@tbursztyka can you review now, should be complete.

@nashif take another look when you have a chance


Where can I get the BOM list？

I have order the PCB from booth,where can I get the BOM list?

Thank you!
There are no BOM list.
Please read from the sch.

Thank you! There are no BOM list. Please read from the sch.

Thank you very much. Could you share me the link of OLED

https://akizukidenshi.com/catalog/g/gP-08278/
Any OLED which has US2066 as an Controller IC may available.


[Bug] Unable to reconcile Grafana(Dashboard|Datasource) resources - tls: failed to verify certificate: x509: certificate signed by unknown authority

Describe the bug
Unable to import Grafana(Dashboard|Datasource) resources

As reported by the ODF QE team, dashboard import is failing for a recent OCP nightly version.
https://github.com/redhat-performance/odf-grafana/issues/28

Also seen on OCP v4.17.2:
from grafana controller v5: (grafana v5.14.0)
ERROR GrafanaDashboardReconciler error reconciling dashboard {"controller": "grafanadashboard", "controllerGroup": "grafana.integreatly.org", "controllerKind": "GrafanaDashboard", "GrafanaDashboard": {"name":"odf-performance-analysis","namespace":"perfscale"}, "namespace": "perfscale", "name": "odf-performance-analysis", "reconcileID": "{uuid}", "dashboard": "odf-performance-analysis", "grafana": "grafana", "error": "Get \"https://grafana-route-perfscale.apps.{CLUSTER}/api/folders?limit=1000&page=1\": tls: failed to verify certificate: x509: certificate signed by unknown authority"}

Version
Full semver version of the operator being used e.g. v4.10.0, v5.0.0-rc0
v5.14.0
To Reproduce
Steps to reproduce the behavior:

Install grafana-operator v5.14.0
Create GrafanaDashboard or datasource to be discovered by grafana
Check grafana controller logs for error

Expected behavior
Dashboards and datasources imported to grafana
Suspect component/Location where the bug might be occurring
Controller-v5
Screenshots
n/a
Runtime (please complete the following information):

OS: [e.g. Linux,Fedora,Mac] RHEL9
Grafana Operator Version [e.g. v5.0.0] v5.14.0
Environment: [e.g Openshift,Kubernetes,minikube etc. please specify versions] OpenShift v4.16.14 & v4.17.2
Deployment type: [e.g Openshift OLM/Helm/kustomize] OLM
Other: [Other variables/things that might be relevant to this bug, versions of other services e.g. operator-sdk]

Additional context
https://github.com/redhat-performance/odf-grafana/issues/28

Thanks for the report. This is due to us fixing a longstanding security issue in which we did not verify TLS certificates. With the newest version we just released, you can configure TLS settings in .spec.client.tls. To solve for this specific use case, either add a matching CA bundle or disable TLS verification to return to the old behavior.
See these issues for more details:
#1683
#1675


Catching up with kickstart

NOTE
Please verify that the base repository above has the intended destination!
Github by default opens Pull Requests against the parent of a forked repository.
If this is your personal fork and you didn't intend to open a PR for contribution
to the original project then adjust the base repository accordingly.

This was a mistake, I wanted to sync yours to mine, sorry


Ability to clear the logs

currently i don't see a way to clear the logs
would be good to have a way to clear the logs

This has a massive performance impact on applications which creates a log of log data in the terminal. Kitematic will become unresponsive after a while. My favorited option is to disable the interactive logging until it's enabled.
We are using it on several Developer workstations at the moment.

+1 @DominicBoettger

This should be fixed in the next release, by #372
Closing for now :-) Thanks!

I understand that this has been in kitematic since v0.5.14 , but I'm unclear on the usage.  Is there a command or button to press and clear the logs?

@b-long I believe we only get the last x lines of logs instead of everything.

Ah, I see.  Thanks @FrenchBen ! Might be worth a feature request, but I'll workaround this for the time being 👍


Add Generate OG image to list of Utilities

https://github.com/BoyWithSilverWings/generate-og-image

@BoyWithSilverWings your changes have been merged, thanks for your contribution 👍


Add typings: Data service

This PR adds typings to the data service. It's part of a series of typing improvements as mentioned in #116.

Hi @dotcs This PR is really nice but need some more work 😇🙏🙏👍
In fact, my main issue is that by replacing the type Feature from type.ts by Feature from GeoJSON node module, we are losing all precious typing defined in FeatureProperties (from type.ts). Can you please find a way to keep custom types: Feature and FeatureProperties, and maybe make them inherit from the Feature type from GeoJSON ???

Other minor issues:

Can you please write import { Feature } from 'GeoJSON'; instead of import { Feature } from 'geojson';
Replace setGeojsonBbox(geojsonBbox): void { by setGeojsonBbox(geojsonBbox: FeatureCollection): void {
Why not delaring the function makeEmptyGeoJsonFC inside the class DataService ?

Thanks @Binnette for your review and your comments! I've added the types OsmGoFeatureCollection and OsmGoFeature which use the FeatureCollection/Feature interfaces of the geojson package and set explicit feature properties. I guess that should be good enough to work with. Also I've included changes that fix point 2 and 3 of your comment.
I'm not sure about your first point though. Import statements are auto-generated by Visual Studio Code in my Case and I wonder why the case matters. Those types are located in node_modules/@types/geojson, so I guess the canonical import path should be geojson instead of GeoJSON. 🤔

@DoFabien Now that ids are numeric, is there anything I should add to this PR? From my side it should be ready to be merged.

Sorry for the delay... Thank you!


Simplify CI/CD

There have been multiple unrelated PRs making small tweaks to CI/CD
We should take some time (after getting more exercises etc) to revisit it and see if there's a way to simplify it or make it less fragile

Simplifying CI in #207


Custom Test Case Report Format and Vendor JSON

Hello,
I want to integrate Sonarqube and Snyk.io for code quality and dependency check for my Go Project.
Sonarqube Requirement
With gogradle, we are only getting test case report in HTML format. Is that a way to get it in json format required by sonarqube ?
Refer : https://docs.sonarqube.org/display/PLUG/Unit+Tests+Results+Import
Snyk.io for Dependency Check
To do dependency scan with snyk.io, it requires Gopkg.lock or vendor/vendor.json.
gogradle generates dependencies in its own format of gogradle.lock. How to generate lock files required by snyk ?
https://snyk.io/docs/snyk-for-golang
Regards,
Mayur

@blindpirate do you have any idea about this ?

Ah, sorry for the delay. No out-of-box solution. At the time I started to write gogradle, go test -json was not available - I had to parse standard output from go test output. I'm considering reading JSON results from Go 1.10 (if my memory is correct) but haven't finished yet. Maybe I can put the result json somewhere during the test process.
If you really want json output, you have to write some custom task, for example iterate on the go packages and run go test -json manually.

Ahha, Thanks for the update.
What about Gopkg.lock or vendor/vendor.json which is required for third party component scanning ?

What about Gopkg.lock or vendor/vendor.json which is required for third party component scanning ?

I'm sorry I don't quite understand this question, can you please elaborate on it?

To do third party component scanning using tools like Snyk.io, we need to generate Gopkg.lock or vendor/vendor.json file (refer : https://github.com/golang/dep).
Currently gogradle generates it's own gogradle.lock file which is not supported by any of these tool.
Is there a way to generate this file with gogradle ?

Unfortunately no... gogradle is not popular enough to make others support it... you have to write an adapter to convert gogradle.lock to other files. :-(

Okay, Thanks @blindpirate.


CLN: Drop support for Python 2.

The 0.10.0 package will be the latest version to support Python 2. This
aligns pandas-gbq with pandas, which dropped support for Python 2 at the
end of 2019.
Closes #268

🙌
Thanks @tswast !


dead keys / compose keys

Is it possible to have dead and compose keys (e.g. AltGr+[ for ¨ to create characters like ü etc.) with keyd? The compose option does not seem to do this.
(I could probably create a new layer, but then I think that such characters are not available?!)

The AltGr modifier is represented as G. It should as simple as assigning the desired key to G-u.

I could probably create a new layer, but then I think that such characters are not available?!

You shouldn't need to create another layer. I'm not sure what you mean by your last remark.

Thanks for the response!

I'm not sure what you mean by your last remark.

I'm referring to using AltGr + [ as a combined modifier which allows me to create ö, ï, ü, and so on, so I'd think of using oneshot(G-[) or something alike instead if I wanted to keep the full functionality of xkb. Then I'd probably put something like [ = f13 and then again map f13 to the compose key. (While this is a new layer of indirection for  me and mapping is tedious, I understand the benefits of keyd and don't want to take the design decisions into question before I have really grasped what I'm dealing with).
[G-u itself is mapped to ↓ for my xkb, and while I don't use that character often, I feel that the same answer applies here that you have given here - that I would have to somehow modify setxkbmap in order to have a compose key.]

I'm referring to using AltGr + [ as a combined modifier which allows me to create ö, ï, ü

You can achieve this by creating a key which toggles the desired layer inside.
E.G

[altgr:G]

[ = layer(symbols)

[symbols]

a = G-b b = G-a ...

personally I would do something like

a = G-b b = G-a ```

instead of nesting the layers, but it should be possible to achieve what you want.

> ... xkb ...

My advice would be to use setxkb only to set the default layout and do the rest of the remapping in keyd. Trying to combine xkb layering and keyd layering is a bad idea. Ideally you should have a keyd config that produces identical results on the virual console and the X server assuming that they both use the same layout for your language.

I believe that this issue is basically solved for me as I have found the virtual keyboard of keyd and don't need to assign all those keys any more but can actually do it. with xkb.

I toyed with this a little bit and think the best solution is to use compose key macros since it requires minimal configuration on the X side and doesn't depend on the layout. See #33.

There is now first class support for this, so you can do o = ö directly in the config file (provided the xkb option compose:menu is set. See the man page for details.


iTextSharp<IP_ADDRESS>

Type: Incomplete
Summary:
iTextSharp<IP_ADDRESS>
Details:
Adding AGPL-3.0-only to Declared License
Resolution:
https://www.gnu.org/licenses/agpl-3.0.html
Affected definitions:

iTextSharp <IP_ADDRESS>

@AE49 The included license file also states that a commercial license can be purchased.

You can be released from the requirements of the license by purchasing a commercial license. Buying such a license is mandatory as soon as you develop commercial activities involving the iText software without disclosing the source code of your own applications.
These activities include: offering paid services to customers as an ASP, serving PDFs on the fly in a web application, shipping iText with a closed source product.

I think this should have OR OTHER as well. Do you agree?
https://clearlydefined.io/file/abf00687d6482774348535c0b24f758bc6ca8d2ff6660d349b06a8f28f1ab41f


Start and End Date click behaviour could be enhanced

Currently In DatePicker the order of start and end date is fixed.
I mean, first you have to select Start Date and then End Date.
There is an alternate behaviour too. Just click on 2 Dates and automatically one will become startDate and Other will become endDate.
You can view this behaviour at my old project -
http://nsisodiya.github.io/x-daterange/
Please adopt, if you like it.

I think that unfortunately this doesn't make as much sense given that we have definite inputs with set focus states. If we were to have a wrapper on the DayPicker component with no input fields, this behavior would make sense but as is... I don't see us moving towards this. Thanks for the suggestion though! If you would like to PR a wrapper for the DayPicker component with this behavior, we'd def consider it.


Cannot connect

Cannot connect to my ha---check network or connection settings code 1-- Ha is working and I can connect remotely just fine.  Using duckdns.

Please provide logs. Thanks

0617 12:25:53 [Debug] :  <!!!> Creating new HomeAssistant instance
0617 12:25:53 [Debug] :  AppLifecycleState.inactive
0617 12:25:53 [Debug] :  AppLifecycleState.resumed
0617 12:25:54 [Debug] :  Use lovelace is true
0617 12:25:54 [Debug] :  Socket connecting...
0617 12:25:54 [Error] :  Socket stream Error: WebSocketChannelException: WebSocketChannelException: SocketException: OS Error: Connection refused, errno = 111, address = avellanet.duckdns.org, port = 41648
0617 12:25:54 [Debug] :  Automatic reconnect is false
0617 12:25:57 [Debug] :  Socket sink closed
0617 12:25:59 [Debug] :  Use lovelace is true
0617 12:25:59 [Debug] :  Socket connecting...
0617 12:25:59 [Error] :  Socket stream Error: WebSocketChannelException: WebSocketChannelException: SocketException: OS Error: Connection refused, errno = 111, address = avellanet.duckdns.org, port = 41652
0617 12:25:59 [Debug] :  Automatic reconnect is false
0617 12:26:02 [Debug] :  Socket sink closed
0617 12:26:40 [Debug] :  AppLifecycleState.inactive
0617 12:26:42 [Debug] :  AppLifecycleState.paused
0617 12:28:29 [Debug] :  AppLifecycleState.inactive
0617 12:28:29 [Debug] :  AppLifecycleState.resumed
0617 12:28:29 [Debug] :  Use lovelace is true
0617 12:28:29 [Debug] :  Socket connecting...
0617 12:28:29 [Error] :  Socket stream Error: WebSocketChannelException: WebSocketChannelException: SocketException: OS Error: Connection refused, errno = 111, address = avellanet.duckdns.org, port = 41950
0617 12:28:29 [Debug] :  Automatic reconnect is false

Is the port supposed to change with each connect?  I was expecting to see 8123 in the log.

Do you use port when opening web UI? It should be the same as for web UI. If you are opening web UI wth no port specified, you need to use "80" or "443" in app.

Closing due to inactivity. Feel free to report another issue if still actual