Generate customize-manifest.json from the app setting

Something like this?
kintone-customize-uploader --import customize-manifest.json

or
kintone-customize-importer customize-manifest.json

?

kintone-customize-uploader --import customize-manifest.json

This seems better to me because users don't need to install additional command kintone-customize-importer locally or globally.


Packaging

Hey,
First of all - thanks for the awesome work with awesome aligner. I am currently working on a small annotation projection project, which makes use of awesome-align. However, it would great if you scope at last the auxiliary files (like modeling.py) into a dedicated folder such as awesomealign. Thanks!

By the way...I made already a fork which contains the necessary changes. Probably the setup.py needs some polishing, but I could make a PR out of it, if you like.

sure, contributions are welcome :)

Sure, please have look before on the setup.py - if you want to leave it out or not. I need to make sure, that my dependencies do not break.

Thanks! That looks good (except maybe I'd name it awesome_align instead of awesomealign) and I'll take a close look at it once you make the PR.


Add sample for using blob storage like a filesystem

Can one of the admins verify this patch?

Did you intend to include the zip file as part of this change?

Did you intend to include the zip file as part of this change?

Yes, it lays down the example file/directory structure that is used by the sample. Kind of hate committing zips to the repo, so I am very much open to other suggestions.

Hi @bsiegel
Thanks a lot.
Could you change the base branch to https://github.com/Azure/azure-sdk-for-python/tree/storage-samples-readme

Done. Also since it sounds like we want these samples to be runnable from PyTest, this zip file thing obviously won't work. I can just lay down the file structure in a setup method before the tests run, and delete them.


Fix the color of the quotes on the home page

It looks like the quote cut off has been fixed (yay!) but the quote color has changed to a near impossible to read blue. Just needs to get changed back to white.

I believe the quote colour has occurred after your commits, not mine.
Because there is presumably an error further up the page where the content
alignment is being thrown off, this could potentially also be affecting any
content below it, by allowing css definitions to cascade to parts of the
page where they should not be. Please check the edits made to the content,
and once those are fixed I can then check the code if there is still a
colour issue.
On Thu, Oct 13, 2016 at 5:01 PM, chealsye<EMAIL_ADDRESS>wrote:

Assigned #278 https://github.com/OAButton/backend/issues/278 to
@markmacgillivray https://github.com/markmacgillivray.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/OAButton/backend/issues/278#event-822722849, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAuXCPTeS3_dFWAVO11kfc04sbP3aU8Rks5qzlXggaJpZM4KWES4
.

Fixed this, was indeed an issue above.


[MBL-1517] Reward Cards On Manage Pledge Should Display Correct Amounts

📲 What
Uses the newly exposed properties from https://github.com/kickstarter/ios-oss/pull/2067 (not yet merged) to display the correct reward amounts on the reward cards in our manage pledge view controller.
Essentially moving from reward.minimum (most current) to reward.latePledgeAmount (late pledge) or reward.pledgeAmount (crowdfunding)
🤔 Why
If, for instance, a user pledged while the campaign was ongoing and then went to manage their pledge to, say, fix their payment method, they would see the most current reward amounts on those reward cards regardless of whether the current amounts reflect late pledge-specific pricing.
If the campaign had entered a late pledge state since it ended, with the chosen reward now having different late pledge-specific pricing, the user would see the late pledge amount instead of the amount at the time of their pledge.
Users should see the amounts that they chose at the time that they pledged.
🛠 How

Updates the formattedAmountForRewardOrBacking SharedFunction to use either the reward.latePledgeAmount if the Backing was made in a late pledge state or reward.pledgeAmount if the Backing was made in a normal crowdfunding state.

I also cleaned up/removed the backing-specific logic in this method because we aren't using it anywhere but in the tests for that function.

Also
The use case for the minAndMaxPledgeAmount() helper method used in this flow isn't super clear to me. Currently, it uses reward.minimum, which represents the most current reward amount. I updated this to use the condition/properties mentioned above to represent the most current reward amount at the time of the Backing.
👀 See
The card will now display the reward amount that was originally pledged. In this case, the pledge was made during the normal crowdfunding state, with a reward of $1. The late pledge amount is $5.

Fixed Card Displaying The Correct (Crowdfunding) Amount
Fix Payment Flow Still Works

♿ Accessibility
No changes
✅ Acceptance criteria

[x] Users see the reward amount they chose when they pledged on the Reward Cards in Manage Pledge.
[x] Fixing an errored payment method flow still works
[x] Entire pledge summary is accurate, and the pledge is processed after the payment method is fixed.

          1 Warning

:warning:
Big PR

  Generated by :no_entry_sign: Danger

          1 Warning

:warning:
Big PR

  Generated by :no_entry_sign: Danger


Update README.md to mention Python

Python 2.7 is required on Windows to install dependencies. I am assuming it is required on other platforms too, but since npm itself requires it on Linux, and I don't have a spare Mac to verify, I can't say for sure.

Good to know. Is it worth checking this in then? Or will it be a little while still before the TextMate grammer is moved over?

Fine by me. I'll roll it back when we close #877


[SPARK-40436][BUILD] Upgrade Scala to 2.12.17

What changes were proposed in this pull request?
This PR aims to upgrade Scala to 2.12.17
Why are the changes needed?
Will add
Does this PR introduce any user-facing change?
Yes, this is a Scala version change.
How was this patch tested?
Existing Test

Test first

wait https://github.com/ghik/silencer/pull/75 and new version of silencer

86571e9

86571e9 bump silencer to 1.7.10

All test passed, issues with release-notes tags as follows:
https://github.com/scala/scala/pulls?q=is%3Apr+sort%3Aupdated-desc+milestone%3A2.12.17+is%3Amerged+label%3Arelease-notes
Waiting for the official release notes


[DO NOT MERGE]Run Python RC Validation Tests   Run Python ReleaseCandidate

Please add a meaningful description for your change here

Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.
Post-Commit Tests Status (on master branch)

Lang
SDK
Apex
Dataflow
Flink
Gearpump
Samza
Spark

Go

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

Java

Python

---

---
---
---

Run Python RC Validation Tests

Run Python ReleaseCandidate

Failed on missing hash file, quick start mobile game succeeded.


Garage door always displays « opening » status

Describe the Bug
I set up a bot as garage door on iOS 18.0 latest dev beta. Homebridge v1.8.4 - Plugin v3.7.0
The bot is correctly configured in Homebridge and I see no error in the debug log. The accessory shows up as closed in Homebridge UI.
But in Home app, the garage door is displayed as « opening » and does not work.
To Reproduce
Configure bot and observe in Home App.
Expected Behavior
Garage door shows up as closed in Home app.
Relevant Log Output
[8/31/2024, 5:48:43 PM] [HB Supervisor] Starting Homebridge with extra flags: -I -P /var/lib/homebridge/node_modules --strict-plugin-resolution
[8/31/2024, 5:48:43 PM] [HB Supervisor] Started Homebridge v1.8.4 with PID: 8836
[8/31/2024, 5:48:45 PM] Loaded config.json with 0 accessories and 6 platforms.
[8/31/2024, 5:48:45 PM] Loaded 1 cached accessories from cachedAccessories.
[8/31/2024, 5:48:45 PM] ---
[8/31/2024, 5:48:45 PM] Disabled plugin<EMAIL_ADDRESS>[8/31/2024, 5:48:45 PM] ---
[8/31/2024, 5:48:45 PM] Loaded plugin<EMAIL_ADDRESS>[8/31/2024, 5:48:45 PM] Registering platform 'homebridge-people-guest-mode.People'
[8/31/2024, 5:48:45 PM] Registering accessory 'homebridge-people-guest-mode.PeopleAccessory'
[8/31/2024, 5:48:45 PM] Registering accessory 'homebridge-people-guest-mode.PeopleAllAccessory'
[8/31/2024, 5:48:45 PM] Registering accessory 'homebridge-people-guest-mode.GuestModeSwitch'
[8/31/2024, 5:48:45 PM] ---
[8/31/2024, 5:48:46 PM] Disabled plugin<EMAIL_ADDRESS>[8/31/2024, 5:48:46 PM] ---
[8/31/2024, 5:48:46 PM] Loaded plugin<EMAIL_ADDRESS>[8/31/2024, 5:48:46 PM] Registering platform 'homebridge-tahoma.Tahoma'
[8/31/2024, 5:48:46 PM] ---
[8/31/2024, 5:48:46 PM] Disabled plugin<EMAIL_ADDRESS>[8/31/2024, 5:48:46 PM] ---
[8/31/2024, 5:48:46 PM] Disabled plugin<EMAIL_ADDRESS>[8/31/2024, 5:48:46 PM] ---
[8/31/2024, 5:48:49 PM] Loaded plugin<EMAIL_ADDRESS>[8/31/2024, 5:48:49 PM] Registering platform<EMAIL_ADDRESS>[8/31/2024, 5:48:49 PM] ---
[8/31/2024, 5:48:49 PM] Loading 6 platforms...
[8/31/2024, 5:48:49 PM] [Cozytouch] Initializing Tahoma platform...
[8/31/2024, 5:48:49 PM] [Cozytouch] Initializing child bridge 0E:8E:03:53:33:29
[8/31/2024, 5:48:49 PM] Ignoring config for the platform "HomeConnect" in your config.json as the plugin "homebridge-homeconnect" has been disabled.
[8/31/2024, 5:48:49 PM] Ignoring config for the platform "TadoAC" in your config.json as the plugin "homebridge-tado-ac" has been disabled.
[8/31/2024, 5:48:49 PM] [Homebridge People Guest Mode] Initializing People platform...
[8/31/2024, 5:48:49 PM] Initializing platform accessory 'XXX'...
[8/31/2024, 5:48:49 PM] Initializing platform accessory 'XXX'...
[8/31/2024, 5:48:49 PM] Initializing platform accessory 'Guest Mode'...
[8/31/2024, 5:48:49 PM] Initializing platform accessory 'Anyone'...
[8/31/2024, 5:48:49 PM] [Homebridge People Guest Mode] WebHook: Started server on port '51828'.
[8/31/2024, 5:48:49 PM] [SwitchBot] Initializing SwitchBot platform...
Setup Payload:
X-HM://0024I6K0QCWCQ
Enter this code with your HomeKit app on your iOS device to pair with Homebridge:

    ââââââââââââââ
    â XXX-XX-XXX â
    ââââââââââââââ

[8/31/2024, 5:48:49 PM] Homebridge v1.8.4 (HAP v0.12.2) (Homebridge B3B1) is running on port 51813.
[8/31/2024, 5:48:49 PM]

NOTICE TO USERS AND PLUGIN DEVELOPERS
> Homebridge 2.0 is on the way and brings some breaking changes to existing plugins.
> Please visit the following link to learn more about the changes and how to prepare:
> https://github.com/homebridge/homebridge/wiki/Updating-To-Homebridge-v2.0

[8/31/2024, 5:48:50 PM] [Cozytouch] Launched child bridge with PID 8852
[8/31/2024, 5:48:50 PM] Registering platform 'homebridge-tahoma.Tahoma'
[8/31/2024, 5:48:50 PM] [Cozytouch] Loaded homebridge-tahoma v2.2.56 child bridge successfully
[8/31/2024, 5:48:50 PM] Loaded 2 cached accessories from cachedAccessories.0E8E03533329.
[8/31/2024, 5:48:50 PM] [SwitchBot] Total SwitchBot Devices Found: 2
[8/31/2024, 5:48:51 PM] [SwitchBot] Restoring existing accessory from cache: Portail deviceId: XXX
[8/31/2024, 5:48:51 PM] [SwitchBot] [DEBUG] Bot: Portail Using Device Config Logging: debug
[8/31/2024, 5:48:51 PM] [SwitchBot] [DEBUG] Bot: Portail Using Platform Config refreshRate: 120, Default updateRate: 5, Platform Config pushRate: 0.1
[8/31/2024, 5:48:51 PM] [SwitchBot] [DEBUG] Bot: Portail Using Default Max Retries: 5, Default Delay Between Retries: 3000
[8/31/2024, 5:48:51 PM] [SwitchBot] [DEBUG] Bot: Portail Model: SwitchBot S1, BLE Model: H, BLE Model Name: WoHand, BLE Model Friendly Name: Bot
[8/31/2024, 5:48:51 PM] [SwitchBot] [DEBUG] Bot: Portail Using Default MQTT URL: , Default mqttOptions: {}, Default mqttPubOptions: {}
[8/31/2024, 5:48:51 PM] [SwitchBot] [DEBUG] Bot: Portail Displaying as Garage Door Opener
[8/31/2024, 5:48:51 PM] [SwitchBot] Bot: Portail Removing any leftover Fan Service
[8/31/2024, 5:48:51 PM] [SwitchBot] Bot: Portail Removing any leftover Lock Service
[8/31/2024, 5:48:51 PM] [SwitchBot] Bot: Portail Removing any leftover Door Service
[8/31/2024, 5:48:51 PM] [SwitchBot] Bot: Portail Removing any leftover Faucet Service
[8/31/2024, 5:48:51 PM] [SwitchBot] Bot: Portail Removing any leftover Outlet Service
[8/31/2024, 5:48:51 PM] [SwitchBot] Bot: Portail Removing any leftover Switch Service
[8/31/2024, 5:48:51 PM] [SwitchBot] Bot: Portail Removing any leftover Window Service
[8/31/2024, 5:48:51 PM] [SwitchBot] Bot: Portail Removing any leftover Window Covering Service
[8/31/2024, 5:48:51 PM] [SwitchBot] Bot: Portail Removing any leftover Stateful Programmable Switch Service
[8/31/2024, 5:48:51 PM] [SwitchBot] [DEBUG] Bot: Portail Retrieve initial values and update Homekit
[8/31/2024, 5:48:51 PM] [SwitchBot] [DEBUG] Bot: Portail openAPIRefreshStatus
[8/31/2024, 5:48:51 PM] [SwitchBot] [DEBUG] Bot: Portail Registering Webhook Event Handler
[8/31/2024, 5:48:51 PM] [SwitchBot] [DEBUG] Bot: Portail is not listening webhook.
[8/31/2024, 5:48:51 PM] [SwitchBot] [DEBUG] Bot: Portail Config: {"logging":"debug","connectionType":"OpenAPI","mode":"press","deviceType":"garagedoor"}
[8/31/2024, 5:48:51 PM] [SwitchBot] [DEBUG] Bot: Portail Using Device Type: garagedoor, from Accessory Cache.
[8/31/2024, 5:48:51 PM] [SwitchBot] [DEBUG] Bot: Portail Firmware Version: 3.7.0
[8/31/2024, 5:48:51 PM] [SwitchBot] [DEBUG] Bot: Portail version: 3.7.0
[8/31/2024, 5:48:51 PM] [SwitchBot] [DEBUG] Bot: Portail Using Bot Mode: press, from Accessory Cache.
[8/31/2024, 5:48:51 PM] [SwitchBot] [DEBUG] Bot: Portail Using Double Press: 1, from Accessory Cache.
[8/31/2024, 5:48:51 PM] [SwitchBot] [DEBUG] Bot: Portail Using Push Rate Press: 15, from Accessory Cache.
[8/31/2024, 5:48:51 PM] [SwitchBot] [DEBUG] Bot: Portail No Allow Push Set, Using default Allow Push: false
[8/31/2024, 5:48:51 PM] [SwitchBot] [DEBUG] Bot: Portail Multi Press Count: 0
[8/31/2024, 5:48:50 PM] [Cozytouch] WARNING: Setting pollingPeriod higher than 60 seconds can generate session timeout errors.
[8/31/2024, 5:48:51 PM] Homebridge v1.8.4 (HAP v0.12.2) (Cozytouch) is running on port 50522.
[8/31/2024, 5:48:51 PM]

NOTICE TO USERS AND PLUGIN DEVELOPERS
> Homebridge 2.0 is on the way and brings some breaking changes to existing plugins.
> Please visit the following link to learn more about the changes and how to prepare:
> https://github.com/homebridge/homebridge/wiki/Updating-To-Homebridge-v2.0

[8/31/2024, 5:48:51 PM] [Cozytouch] Configure device Chauffe-eau
[8/31/2024, 5:48:51 PM] [Cozytouch]   WaterHeatingSystem > DomesticHotWaterProduction
[8/31/2024, 5:48:51 PM] [Cozytouch] Configure device MODBUSLINK (1#2)
[8/31/2024, 5:48:51 PM] [Cozytouch]   ElectricitySensor > CumulativeElectricPowerConsumptionSensor
[8/31/2024, 5:48:52 PM] [SwitchBot] [DEBUG] Bot: Portail statusCode: 200, deviceStatus: {"statusCode":100,"body":{"deviceId":"XXXXXX","deviceType":"Bot","hubDeviceId":"EA9B61FEFEB4","version":"V6.6","power":"on","battery":99,"deviceMode":"pressMode"},"message":"success"}
[8/31/2024, 5:48:52 PM] [SwitchBot] [DEBUG] Bot: Portail statusCode: 200, deviceStatus: {"statusCode":100,"body":{"deviceId":"XXXXXX","deviceType":"Bot","hubDeviceId":"EA9B61FEFEB4","version":"V6.6","power":"on","battery":99,"deviceMode":"pressMode"},"message":"success"}
[8/31/2024, 5:48:52 PM] [SwitchBot] [DEBUG] Bot: Portail openAPIparseStatus
[8/31/2024, 5:48:52 PM] [SwitchBot] [DEBUG] Bot: Portail (power, battery, deviceMode) = API:(on, 99, press), current:(false, 99, press)
[8/31/2024, 5:48:52 PM] [SwitchBot] [DEBUG] Bot: Portail On: false
[8/31/2024, 5:48:52 PM] [SwitchBot] [DEBUG] Bot: Portail BatteryLevel: 99
[8/31/2024, 5:48:52 PM] [SwitchBot] [DEBUG] Bot: Portail StatusLowBattery: 0
[8/31/2024, 5:48:52 PM] [SwitchBot] [DEBUG] Bot: Portail Firmware Version: 6.6
[8/31/2024, 5:48:52 PM] [SwitchBot] [DEBUG] Bot: Portail version: 6.6
[8/31/2024, 5:48:52 PM] [SwitchBot] [DEBUG] Bot: Portail updateHomeKitCharacteristics
[8/31/2024, 5:48:52 PM] [SwitchBot] [DEBUG] Bot: Portail updateCharacteristic BatteryLevel: 99
[8/31/2024, 5:48:52 PM] [SwitchBot] [DEBUG] Bot: Portail updateCharacteristic StatusLowBattery: 0
[8/31/2024, 5:48:52 PM] [SwitchBot] [DEBUG] Bot: Portail updateCharacteristicc TargetDoorState: Closed, CurrentDoorState: Closed (false)
[8/31/2024, 5:48:52 PM] [SwitchBot] [DEBUG] Bot: Portail Garage Door On: false

Config for homebridge-switchbot
{
            "name": "SwitchBot",
            "credentials": {
                "token": "xxxx",
                "secret": "xxxx",
                "notice": "Keep your Token & Secret a secret!"
            },
            "options": {
                "devices": [
                    {
                        "deviceId": "xxxxx",
                        "configDeviceType": "Bot",
                        "connectionType": "OpenAPI",
                        "bot": {
                            "mode": "press",
                            "deviceType": "garagedoor"
                        },
                        "logging": "debug"
                    }
                ],
                "logging": "standard"
            },
            "platform": "SwitchBot"
        }

Screenshots
No response
Device and Model
Raspberry Pi docker
Node.js Version
20.17.0
NPM Version
10.8.2
Homebridge Version
1.8.4
Homebridge Switchbot Plugin Version
3.7.0
Homebridge Config UI X Plugin Version
No response
Operating System
Raspbian

Can you try the latest beta:
![npm version](https://badgen.net/badge/homebridge-switchbot@beta/>= 3.7.1-beta.18/orange)
Click here to find out how to install Beta

Just installed v3.7.1 beta and I don’t observe any change in the behavior. The gate is still displayed as « opening » and I see no difference in the logs.

Can you try the latest beta:

Click here to find out how to install Beta

@donavanbecker tried with beta 19 and 23 which was out when I saw your message. Behaviour remains quite the same unfortunately.

Closing all issues now that v4.0.0 is out. If you are still having an issue after trying v4.0.0, please open a new issue. Keep in mind v4.0.0 has some breaking changes with the config. You will need to re set your config up, however there are some nice added bonuses since you can set settings at a deviceType level or individual level.


chore(release): v1.0.1 🎉

:robot: I have created a release beep boop
1.0.1 (2024-09-14)
Bug Fixes

types: allow pick any range filters, rather than just one (3dfa7fc)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/ehmpathy/pagination-fns/releases/tag/v1.0.1 :sunflower:


[TreeView] Correct visibleNodes on re-render

[x] I have followed (at least) the PR section of the contributing guide.

Closes #20140

@tonyhallett Nice work, thanks!


There is no string 'New name:' on the 'Clone File Share with New Name' dialog

Storage Explorer Version: 1.27.0-dev
Build Number: 20221017.1
Branch: main
Platform/OS: Windows 10/Linux Ubuntu 22.04/MacOS Monterey 12.6 (Apple M1 Pro)
Architecture: ia32/x64
How Found: Ad-hoc testing
Regression From: Not a regression
Steps to Reproduce

Expand one storage account -> File Shares.
Right click one file share -> Click 'Clone...'.
There is a 'Clone File Share with New Name' dialog.
Check whether there is a string 'New name:' on the dialog.

Expected Experience
There is a string 'New name:' on the dialog.
Here is the screenshot for blob containers:

Actual Experience
There is no 'New name:' on the dialog.

Verified this issue on the main build 20221020.1. Fixed. So, we are going to close it.


NSCLC Labels

Hello,Nice work. I have a question.TCGA-NSCLC is a subtyping task for LUAD and LUSC.There is no concept of positive and negative like it in Camelyon-Dataset. So may be the DGR-MIL is more suitable for the normal/tumor task but not the subtyping task.

Thanks for your interest in our work, we had a discussion here  #3, please refer to


Bug side avoidance

Solves and closes #45

There is now a method that returns a boolean for any given sensor (adapted from an already existing method for the front).
After fixing, we could not reproduce the bug #45 anymore. Please try the code of this branch on your computer to see if it works on other machines, since it was supposed to be solved before.

Good catch, I make the changes and commit again =)


Adapter crash at value change for dimmer

When changing value of dimmer adapter crashes:
 openhab.0	2017-07-02 23:04:43.342	info	connected openhab.0	2017-07-02 23:04:43.256	info	starting. Version 0.1.3 in /opt/iobroker/node_modules/iobroker.openhab, node: v4.8.3 host.HomeControl	2017-07-02 23:04:42.308	info	instance system.adapter.openhab.0 started with pid 118386 host.HomeControl	2017-07-02 23:04:12.270	info	Restart adapter system.adapter.openhab.0 because enabled host.HomeControl	2017-07-02 23:04:12.269	error	instance system.adapter.openhab.0 terminated with code 0 (OK) openhab.0	2017-07-02 23:04:12.246	info	terminating openhab.0	2017-07-02 23:04:12.221	info	cleaned everything up... openhab.0	2017-07-02 23:04:12.219	error	at processImmediate [as _immediateCallback] (timers.js:396:17) openhab.0	2017-07-02 23:04:12.219	error	at Immediate._onImmediate (/opt/iobroker/node_modules/iobroker.openhab/node_modules/request/request.js:581:7) openhab.0	2017-07-02 23:04:12.219	error	at end (/opt/iobroker/node_modules/iobroker.openhab/node_modules/request/request.js:552:18) openhab.0	2017-07-02 23:04:12.219	error	at Request.write (/opt/iobroker/node_modules/iobroker.openhab/node_modules/request/request.js:1514:27) openhab.0	2017-07-02 23:04:12.219	error	at ClientRequest.OutgoingMessage.write (_http_outgoing.js:459:11) openhab.0	2017-07-02 23:04:12.219	error	TypeError: first argument must be a string or Buffer openhab.0	2017-07-02 23:04:12.216	error	uncaught exception: first argument must be a string or Buffer openhab.0	2017-07-02 23:04:12.190	warn	Cannot write "openhab.0.items.Dimmer_Test": Error: Argument error, options.body.

solved with 1.0.4, thank you Bluefox !


unacceptableStatusCode(401)

Hi all!
I'm trying connect to Geth with this config:
let configuration = Configuration(
  network: .kovan,
  nodeEndpoint: "https://kovan.infura.io/v3/MYTOKEN",
  etherscanAPIKey: "MYTOKEN",
  debugPrints: true
)

But when y debug inside xCode, I get:
responseError(EthereumKit.EthereumKitError.ResponseError.unacceptableStatusCode(401))
Anybody got the same response?

The problem was the endpoint URL I used!


Column-major support for sprite data

Since convimg already supports row-major sprite data output, it would be useful to also support a data output useful for column-major mode. Essentially, the current output is convenient for programs working in row-major mode but is difficult to work with when the display is in column-major.

Can you not use the rotate and flip options to get what you want?

I'm pretty sure you can just do flip-x: true and rotate: 90 to get the desired effect, so I'm just going to close this issue.


feature: static initial page

Description
When user starts static wrappid-app, we need a page that will help them use our framework

this issue got resolved with cleanup and new layout structure


Keep RAM routines in separate files

While we don't know yet what the license for the RAM routines will be, it might not be APL or APL-compatible. In that case, those RAM routines should not be linked into the program binary, but read at runtime from their files.
This would also allow distributions to not ship them, should the license turn out to be non-free.
Philipp

yeah, that's of course possible. However, it would make installation of the tool more troublesome, because the user needs to download and install the STM "Flash Loader Demonstrator" first, just to copy a few S19 files :-(
I propose to see how issue #1 is resolved. If STM frees the RAM code (which I believe will be the case), I see no benefit in reading them at runtime...?

Well, if the license allows redistribution, we could still have RAM routines files in the repository, and install them somewhere via "make install". But distributions that consider the license ínacceptable could still ship the program without the RAM routines.
E.g. Debian does package SDCC, but they do not include the files in device/non-free (currently just some headers for Microchip pic devices).
Philipp

obsolete after confirmation by ST support that now ultimate-liberty-v2 license applies (http://www.st.com/software_license_agreement_liberty_v2), which allows re-distribution


Combine SkyDNS bits into one manifest

This change is

Reviewed 13 of 17 files at r1.
Review status: 11 of 15 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Reviewed 1 of 17 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


103: updated testdb for regulation and compara

Requirements

Filling out the template is required. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion;
Review the contributing guidelines for this repository; remember in particular:

do not modify code without testing for regression
provide simple unit tests to test the changes
the PR must not fail unit testing
if you're adding/updating documentation of an endpoint, make sure you add/update the necessary parameters to the (template) configuration files in the ensembl-rest_private repo

Description
Test db updated for 103: funcgen/regulation and compara
Use case
Part of release SOP
Benefits
Updated test db for the release
Possible Drawbacks
NA
Testing
No change in test cases.
If so, do the tests pass/fail?
NA
Changelog
No change in functionality

Coverage remained the same at 44.382% when pulling 87ba103b5834d05618a4663ea27d3086af5d0a23 on 103_testdbpatch into 720fb02652710777e6dcbc02574682658bb34590 on release/103.


Change from deprecated build_sphinx to new build_docs

The build_sphinx command has been deprecated in astropy-helpers.
This PR changes to the new equivalent command (that has existed for a long time) of build_docs.

There's a conda install error on Appveyor:
https://ci.appveyor.com/project/Astropy/regions/build/1.0.117/job/f91g3r6xyr2k309e
It seems unrelated, I'm merging this now.
If the error appears again in the build triggered by the merge, I'll file a separate issue.


Mongoid 4.0

i get this error when i try to run my specs
i'm using mongoid 4.0
/home/sebi/.rvm/gems/ruby-2.2.0/bundler/gems/database_cleaner-bb608dd3ac6b/lib/database_cleaner/mongoid/truncation.rb:30:in `session': undefined method `default_session' for Mongoid:Module (NoMethodError)

from /home/sebi/.rvm/gems/ruby-2.2.0/bundler/gems/database_cleaner-bb608dd3ac6b/lib/database_cleaner/moped/truncation_base.rb:26:in `collections'

from /home/sebi/.rvm/gems/ruby-2.2.0/bundler/gems/database_cleaner-bb608dd3ac6b/lib/database_cleaner/moped/truncation_base.rb:14:in `clean'

from /home/sebi/.rvm/gems/ruby-2.2.0/bundler/gems/database_cleaner-bb608dd3ac6b/lib/database_cleaner/base.rb:40:in `clean_with'

Database-cleaner work for me with Mongoid 4 (4.0.0 and 4.0.2) as at 1.4.1 and as 1.3.0.
Are you using master branch?

thanks, it works now


unread: Add check to debug missing unreads in combined feed.

This will help us know which messages are missing in combined feed when there is a mismatch between unread counts and the messages in the combined feed.
discussion: https://chat.zulip.org/#narrow/channel/9-issues/topic/.F0.9F.8E.AF.20.E2.9D.93combined.20feed.20missing.20messages

I can deploy this but I think it needs some naming improvements/refactoring before we can merge it.

I was thinking we don't need to merge this but just use it to debug the current case.

yes I like aall bugs to be debugged into a fiwall then all bugs not
firewall but if someone attacks then they yet bugged IG possible my theory
but I know little...:)
On Tue, Dec 17, 2024, 10:24 PM Aman Agrawal @.***>
wrote:

I was thinking we don't need to merge this but just use it to debug the
current case.
—
Reply to this email directly, view it on GitHub
https://github.com/zulip/zulip/pull/32727#issuecomment-2550228450, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/BMY32AQNLWQ5R5VXHY7T5BD2GDTFFAVCNFSM6AAAAABTVRYLAOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJQGIZDQNBVGA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Update ActiveMQ to 5.16.4, minor version increment with security fixes

This version includes updated dependencies to reference reload4j instead of log4j 1.2.x, to address several recently uncovered vulnerabilities. None of these vulnerabilities impacts the normal usage of the transport with a typical tcp: or failover: ActiveMQ connection URI.
ActiveMQ for GeoEvent was already running an earlier 5.16.x release, so updating to this version is not likely to have any impact on previously configured GeoEvent inputs / outputs, but as always, it is recommended to take a backup of the current config before updating the transport.

Duplicate - I had forgotten that I already opened this pull request, although the initial commit did not fully address the potential log4j 1.2.x vulnerabilities; only updated the ActiveMQ client library. It is superseded by #15.


Fix share menu conversations

Brandon, you keep not including recent conversations at the top of the share menu. Quit it. They MUST be at the top.

They are there now... just when the user types nothing

This is legit not a bug, the way you were doing it before made it so that there were dupe contacts... why would we do it like that, it's just confusing


BindingOperations.ForceUnwrapping crash

Reported via TestFlight. Supposedly occurs on startup. Unsure what specifically is causing it.

Resolved by 27926a7824879195417aed97942430d60eb3fb46


Add country select

This adds a very basic country select that wraps the country_select with the correct markup.
I'm sure there is something that could make it better, but for my use (default, no options) it works just fine.
Also it is nicer then getting an exception since the builder has nothing when you have a field called country.

I'd like to see this merged!

Trying your master with carmen and
<%= f.input :home, :as => :country %>

gives me Formtastic::UnknownInputError. What's the API for this?


fix: safe area color different from background in dark mode

Description

iPhone safe area color different from background in dark mode.
It looks weird in dark mode.

before
after

Linked Issues
Additional context

Thanks!


GET https://grtp.co/v1/api.js net::ERR_INSECURE_RESPONSE

My Gratipay widget suddenly disappeared, and I found the following error in my Chrome console:
GET https://grtp.co/v1/api.js net::ERR_INSECURE_RESPONSE

So I tried accessed https://grtp.co/v1/api.js directly, and found a "Your connection is not private".
Has there been configurations with the Gratipay certificate recently, or might this a temporary or local issue?

@e9t Thanks for the report. I'm not able to reproduce the "Your connection is not private" message in Chrome 44.0.2403.130. Perhaps this is parallel to https://github.com/gratipay/gratipay.com/issues/3278?

Yes, I believe that's the same issue!
Since my widget is displaying properly now, and you already have a duplicate issue, I'll close this one. Thanks for the reply.

Cool. Sorry for the trouble. :-/


Random port will cause service ID to be duplicated

I am a newbie and found problems during the learning process. When I set server.port=0, the id of the registration service is always ${spring.application.name}-0,
for example: spring-cloud-demo-consul-provider-0

I looked at the source code, the priority service id is set first, prot is after, but the port is not considered when the service id is assembled and not reformatted.

version

spring-cloud-consul-discovery-2.1.3.RELEASE

see todo:

org.springframework.cloud.consul.serviceregistry.ConsulAutoRegistration#initializePort

public void initializePort(int knownPort) {
	if (getService().getPort() == null) {
		// not set by properties
		getService().setPort(knownPort);

		// todo ...
		// I think this should reformat the service id
	}
	// we might not have a port until now, so this is the earliest we
	// can create a check
	setCheck(getService(), this.autoServiceRegistrationProperties, getProperties(),
			this.context, this.heartbeatProperties);
}

Submit lssue for the first time, write bad, please forgive me

I'm not keen on adding more support for random ports. You can set the service id yourself.


Refactor: fold get_vc_data_by_mor into get_vc_data

Purpose or Intent
get_vc_data_ and get_vc_data_by_mor shares most of the logic already.
(Seems a bunch code being used by reconfig_vm* logic can be shared with the general logic. Hopefully this is the beginning to eliminate more code.)

@miq-bot add_labels refactoring, providers/vmware/infra

@jameswnl good idea looks like lots of duplication


angular-ui-bootstrap build

Once bower install && npm install was ran, now in bower_components/ all of the needed components where installed, ready to be used.
There was a small problem, though:
When running grunt dev, this was in the output:

Running "bowercopy:dev" (bowercopy) task
bower_components/angular/angular.js -> dist/dev/js/lib/angular.js
bower_components/angular-animate/angular-animate.js -> dist/dev/js/lib/angular-animate.js
bower_components/angular-resource/angular-resource.js -> dist/dev/js/lib/angular-resource.js
bower_components/angular-route/angular-route.js -> dist/dev/js/lib/angular-route.js
bower_components/angular-sanitize/angular-sanitize.js -> dist/dev/js/lib/angular-sanitize.js

bower_components/angular-ui-bootstrap/dist/ui-bootstrap-0.11.0.js was not found
bower_components/angular-ui-bootstrap/dist/ui-bootstrap-tpls-0.11.0.js was not found

The problem was that angular-ui-bootstrap did not have the dist/ folder.
I managed to solve this by running the following commands:

cd bower_components/angular-ui-bootstrap
npm install
grunt --force
cd ../../

Is there a better way of solving this problem?
Why did this not happen before? We are using the same versions of the library!

Hi @miguelemosreverte
Thanks for checking out the repo, and describing the issues you have had.
Firstly, it's important to note that I haven't really added any functionality to this repo in about 3 years, and it's using an old version of Angular 1.x.
I just did a fresh clone and bower install && npm install, and then ran grunt dev... I got different errors from you:
❯ grunt dev
Running "clean:dev" (clean) task

Running "jshint:files" (jshint) task
Warning: Path must be a string. Received null Use --force to continue.

Aborted due to warnings.

I'm guessing that the errors are related to the original code using an earlier version of npm, bower, or grunt – or several of those.
For reference, I am using macOS Sierra (10.12.6), and the following versions of the above utilities:
❯ npm --version
3.10.10

❯ bower --version
(node:73287) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
1.4.1

❯ grunt --version
grunt-cli v0.1.13
grunt v0.4.5

Unfortunately at this time I don't have the time to investigate further. I'd also guess that there are many other boilerplate repos for Angular 1.x.
Have you tried out Angular (2)? It's a steep learning curve, but worth the time investment IMO.
Matt


need headless monitors

Description
On sway, there's some thing like this, and it can create a virtual monitor
output HEADLESS-1 {
pos 1200,0
mode 2048x1536
bg ~/tausta_kuva fill #002633
transform 90
}
this virtual monitor can be used like this
wayvnc --output=HEADLESS-1 <IP_ADDRESS> 5900
so then an ipad could be used as a second monitor
My schoon have just banned me from using monitors other than the built-in monitor, but I'm addicted to dual screens, so I hope this feature could be added in the future

you can use hyprctl output, refer to the wiki. Doesn't that do the same?

oh sorry I miss that


Deployment docs - update wagtail getting started

existing link does not work, just redirects to div.io home page
New link https://docs.divio.com/en/latest/introduction/wagtail/

Thanks @zerolab


merge from template-coveralls

package.json

chore(deps): add ^13.0.2 remove ^13.0.1 (devDependencies.npm-pkgbuild)

.github/workflows/update_package_lock.yml

chore: add Regenerate package lock (jobs.update_package_lock.steps.with.title)

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

npm package (@latest dist-tag)
v6.4.6
GitHub release

Your semantic-release bot :package::rocket:


Review Session https://www.livecoding.tv/sehe/

Nothing spectacular, just the fruits of our discussions :)
I learned a thing or two (I think).
NOTE
None of this was tested, since my compiler doesn't quite keep up with c++14 and experimental standard library features well enough...
Be prepared to find elementary bugs needing ironing-out before you can test the new game-logic in keyboard_event_loop. But, as discussed, after that, you shouldn't expect to see edges cases fail in quite such interesting ways as we saw earlier :)
Cheers

Now it should be relatively safe to pull. I can't /see/ that the "irrelevant changes" commit has been dropped, but I did drop it. Shall I create a new pull request instead?

The new PR is here: https://github.com/Skorezore/Gaem/pull/21
Please close this one


Feature/zxc aws mon

这个 PR 实现什么功能/修复什么问题:
aws监控信息获取
是否需要 backport 到之前的 release 分支:

release/2.13
release/2.14
release/3.0

/area region
/cc @swordqiu
/cc @yousong

Codecov Report

Merging #4775 into master will decrease coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master   #4775      +/-   ##
=========================================
- Coverage    6.78%   6.78%   -0.01%
=========================================
  Files         524     525       +1
  Lines       89719   89767      +48
=========================================
+ Hits         6091    6093       +2
- Misses      83120   83167      +47
+ Partials      508     507       -1

Flag
Coverage Δ

#aFlag
6.78% <0%> (-0.01%)
:arrow_down:

Impacted Files
Coverage Δ

pkg/multicloud/aws/aws.go
0% <0%> (ø)
:arrow_up:

pkg/multicloud/aws/monitor.go
0% <0%> (ø)

pkg/multicloud/aws/region.go
0% <0%> (ø)
:arrow_up:

pkg/appsrv/response.go
69.23% <0%> (+3.07%)
:arrow_up:

Continue to review full report at Codecov.

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

/lgtm


Upgrading dependencies to v0.6 LNP/BP stack

Codecov Report

Merging #5 (a8983e1) into master (0c2a1a8) will increase coverage by 0.6%.
The diff coverage is 18.6%.

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

@@           Coverage Diff            @@
##           master      #5     +/-   ##
========================================
+ Coverage    60.6%   61.2%   +0.6%
========================================
  Files          24      24
  Lines        3245    3334     +89
========================================
+ Hits         1967    2042     +75
- Misses       1278    1292     +14

Impacted Files
Coverage Δ

src/session/init.rs
0.0% <0.0%> (ø)

src/session/local_node.rs
0.0% <0.0%> (ø)

src/session/noise/conduit.rs
92.2% <0.0%> (-3.8%)
:arrow_down:

src/session/session.rs
31.9% <0.0%> (-15.0%)
:arrow_down:

src/session/transcoders.rs
86.0% <ø> (ø)

src/transport/mod.rs
3.1% <33.3%> (-0.2%)
:arrow_down:

src/session/node_addr.rs
70.3% <100.0%> (+1.6%)
:arrow_up:

src/session/noise/handshake.rs
96.0% <100.0%> (ø)

src/lib.rs
53.9% <0.0%> (-0.3%)
:arrow_down:

... and 5 more

Continue to review full report at Codecov.

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


[WIP] drop Spark <2.3 support and build against Keras 2.2.2 and TF 1.10.0

Still a WIP.

Drop support for Spark <2.3 and hence Scala 2.10.
Update Keras version to 2.2.2 and TF version to 1.10.0.
TODO: Update README

We will add Spark 2.4 support after RC is out.

Codecov Report

Merging #149 into master will decrease coverage by 12.1%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master     #149       +/-   ##
===========================================
- Coverage   85.37%   73.27%   -12.11%
===========================================
  Files          34       11       -23
  Lines        1922      494     -1428
  Branches       41       41
===========================================
- Hits         1641      362     -1279
+ Misses        281      132      -149

Impacted Files
Coverage Δ

python/sparkdl/transformers/keras_utils.py

python/sparkdl/utils/keras_model.py

python/sparkdl/graph/tensorframes_udf.py

python/sparkdl/param/__init__.py

python/sparkdl/graph/builder.py

python/sparkdl/param/image_params.py

python/sparkdl/udf/keras_image_model.py

python/sparkdl/param/converters.py

python/sparkdl/graph/input.py

python/sparkdl/image/imageIO.py

... and 13 more

Continue to review full report at Codecov.

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

Shall we close this since it has been subsumed by https://github.com/databricks/spark-deep-learning/pull/151 ?  (I checked the newer one vs. this one.)

closed!


Main window default size unreasonable

I think this was caused by the removal of the default wallet:

Is #104 the same?

Probably, but it's not HiDPI-related.

Fixed in #116.

Unfortunately, on master (02cf20b9f571474c939d18a8b9d6b5d22479a222) I can seem a similar (the same?) issue on Fedora 33 + Qt 5.15.2:
$ src/qt/bitcoin-qt -regtest -printtoconsole
QSocketNotifier: Can only be used with threads started with QThread
2020-12-26T22:34:10Z Bitcoin Core version v21.99.0-02cf20b9f (release build)
2020-12-26T22:34:10Z Qt 5.15.2 (dynamic), plugin=wayland (dynamic)
2020-12-26T22:34:10Z System: Fedora 33 (Workstation Edition), x86_64-little_endian-lp64
2020-12-26T22:34:10Z Screen: Virtual-1 1920x1200, pixel ratio=1.0
...

The Bitcoin Core GUI (Qt) stores the window size and position. So I guess it could have been the problem in your case (@hebasto).

The Bitcoin Core GUI (Qt) stores the window size and position. So I guess it could have been the problem in your case (@hebasto).

I suspect that that were old Qt settings in my test VM.

Opend this issue on to day


Improve German translation

I have partially corrected existing translations and added new translations.

Hi @Atalanttore ,
thank for the PR! LGTM.


[Fix #21022] Improve performance by reducing re-renders SidebarLinks

Details

Improve the performance by reducing unnecessary re-renders of the SidebarLinks component.
Fixed Issues

$ https://github.com/Expensify/app/issues/21022
PROPOSAL: https://github.com/expensify/app/issues/21022#issuecomment-1600631095
Tests

[ ] Verify that no errors appear in the JS console
[ ] Open a report, verify that the highlight of the items still work
[ ] Send a message from user A to user B and verify that the reports are resorting accordingly

Offline tests

n/a
QA Steps

[ ] Verify that no errors appear in the JS console
[ ] Open a report, verify that the highlight of the items still work
[ ] Send a message from user A to user B and verify that the reports are resorting accordingly

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

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

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

How about css optimization?

Sorry, what do you mean by that @venture1981

@0xmiroslav I think I did it correctly, no?

Also thx for the review, I wasn't pushing the latest changes 😅 now everything looks correct to me

@hannojg could we get back to this one soon? thanks 🙇

@hannojg is this ready for review?

No not yet, sorry, the tests are still failing. Working on it right now

Okay, this needed a bit of a larger rework, as we do still need the currentReportID. Without it we'd cause a regression in GSD mode (which I was overlooking previously).
I am however very happy with the rework, as I can already feel how the code gets cleaner, easier to understand and more efficient.
Will share details when finishing this tomorrow ✌

Okay, this is good for review again. Let me explain the changes I made on a high level to help with the code review:
Splitting OptionRowLHN and SidebarLinks into UI and data components
There were two new components introduced:

<SidebarLinksData />
<OptionRowLHNData />

The corresponding none-data-components are now memoized, and are only expecting to receive derived values that are necessary for displaying the UI (and nothing more).
So, for example, SidebarLinksData calculates the list of report IDs we want to display given all the onyx data. Only when the calculated array really changed in its content (e.g. item order as in one report a new unread message arrived) it will pass the updated value to SidebarLinks causing an update.
The same goes for OptionRowLHN and its optionItem it wants to render.
Passing data from the components to onyx
Before, we were loading all the data needed for calculating the derived values for the components manually with Onyx.connect in e.g. SidebarUtils.
We also still had to connect the component to the onyx keys, to cause a re-render, which would then call the function to calculate the derived value (see e.g. SidebarUtils.getOrderedReportIDs).
This structure has its flaws, for example we were often missing to connect the right keys to the component, which would cause us to show stale data (See for example this issue)
We now connect all data needed to the component, and the component then calls the function with the data from the props. This is a transparent process that is easy to understand and reason about.
As this happens in the data component, we don't need to worry about unnecessary UI updates, as the underlaying UI component won't re-render unless the derived data really changed and we'd need to re-render.
Future Considerations
The end game would be to not call the calculation function for derived data from the component using props, but from an onyx selector. In onyx we currently lack the functionality to have "dependent selectors".
For getting the user's personal data, we first need to load the session from onyx to get the user's accountID and then look into personalDetailsList (for this example, we currently have the withCurrentUserPersonalDetails hoc, which loads the session and personalDetailsList separately.)
Imagine we'd have the following in onyx:
withOnyx({
   currentUserPersonalDetails: {
     keys: [ONYXKEYS.SESSION, ONYXKEYS.PERSONAL_DETAILS_LIST],
     selector: (session, personalDetails) => personalDetails[session.accountID]
   }
})

or another API could look like this:
const currentUserPersonalDetailsSelector = createSelector(
   selectSessionAccountID,
   selectPersonalDetailsList,
   (accountID, personalDetails) => personalDetails[session.accountID]
)

withOnyx({
   currentUserPersonalDetails: currentUserPersonalDetailsSelector
})

The last example would even be better, as we don't rerun the selector when anything on the session changes, but just when the account ID changes.
I will try to make a proposal for this soon and then revisit.
Utility onyxSubscribe
We want to avoid re-rendering our components for getting a new prop value, that is not needed for the UI output.
Earlier, we were connecting the SidebarLinks component to the modal key to get willAlertModalBecomeVisible which we needed for some keyboard shortcuts.
onyxSubscribe is a convenience wrapper around Onyx.connect so we can read from onyx and receives updates, but not in the react state to avoid re-renders.

@fedirjh This is another one which could be higher on your list.
thanks @hannojg for pushing this forwards and great write up ❤

I incorporated the latest feedback and resolved conflicts. Eagerly waiting for your reviews 😊

Thanks for the review @fedirjh will address all points/bugs shortly

@fedirjh I addressed your comments and fixed all named bugs! Good for testing again

Hey, I added one other performance improvement. Instead of checking for the navigation focus to disable accessibility elements in SidebarLinks, I am doing that now in SidebarLinksData. With this change we prevent re-rendering the whole FlatList just because the isFocused prop changed (the propagation will stop at SidebarLinks and only SidebarLinksData will re-render)

Thanks Hanno!
@fedirjh seems like this is ready for another look 🚀

@hannojg I think we can remove accessibilityElementsHidden prop since it was needed when we did not have stack based navigation and now it is used only for tests (so we'd have to use something else there), but I am not 100% sure.  Code in stack for it: https://github.com/react-navigation/react-navigation/blob/24c03924397a6e59aba9f6b74a9c5cb4b939d9e1/packages/stack/src/views/Stack/CardContainer.tsx#L242.

Oh, would be even better to get rid of it completely @WoLewicki! Can you somehow confirm whether it can be removed or not?
@fedirjh You're the best tester, thank you so much for catching these! Will fix it shortly!

@fedirjh The @expensify.sms seems to be a general bug, I also have it on staging 👀

Once refreshed its gone

@fedirjh Would appreciate another review 🙏 (Sorry if there are still bugs, there are many conditions to the LHN and I really hope we catch them all! In my testings everything looks good, curious about yours)

I might be wrong but i think localhost is using the development code version, which is less optimized and slower, while staging already uses an optimized build, that is closer to the final release build.
But it might be that it caused a performance regression in that sense, will look into it today!

@fedirjh Hey, this is a bit hard to reproduce for me. However, I have a theory of why this might be happening.
I added a patch for onyx, from this PR:

https://github.com/Expensify/react-native-onyx/pull/280

it removes the blocking behaviour from withOnyx.
Can you please pull, run npc patch-package, make sure the onyx patch got applied, and try testing for performance again?
In addition it'd be cool if you could run npm run build-staging and then test with the release build.
Thank you so much in advance!

You can, or i think you can run the build command and then use something like npx serve to try out the build

Okay, i reverted the patch!

I pushed two little last changes. I think we should be good now

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

Thanks was not sure if you are reviewing, sorry

@0xmiroslav looking into it now!

@0xmiroslav Oh, I have seen this as well and thought I'd be a bug! but its on staging as well. Pinned rooms are only sorted by their name. When two workspaces have the same name their order will always be random (often times its by luck that its the same, but its really random) 😅

https://github.com/Expensify/App/assets/16821682/91462cf2-c974-4616-9816-d5cabe798c44
Proof that I am no liar 😄

@mountiny is it possible that something broke during merge?
@0xmiroslav are you on the latest version of the perf branch?

🚀 Deployed to staging by https://github.com/mountiny in version: 1.3.43-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

@hannojg it is possible

This PR has caused a number of regressions:
https://github.com/Expensify/App/issues/23189
https://github.com/Expensify/App/issues/23195
https://github.com/Expensify/App/issues/23202
I'm going to revert it

🚀 Deployed to staging by https://github.com/mountiny in version: 1.3.43-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to staging by https://github.com/mountiny in version: 1.3.44-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/jasperhuangg in version: 1.3.43-7 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

This PR Causes this regression more details here


file_list errors on invalid string index check

From @tzarebczan on May 26, 2017 5:0

The Issue
file_list fails with:
2017-05-30 20:42:15,138 ERROR lbrynet.lbrynet_daemon.auth.server:346: Failed to process file_list: string indices must be integers
Traceback (most recent call last):
File "site-packages\twisted\internet\defer.py", line 1299, in _inlineCallbacks
File "site-packages\lbrynet\core\Wallet.py", line 770, in _handle_claim_result
File "site-packages\lbryschema\claim.py", line 140, in load_dict
File "site-packages\lbryschema\encoding.py", line 33, in decode_fields
TypeError: string indices must be integers
Steps to reproduce

Run the file_list API command from my install

Expected behaviour

Return properly

Actual behaviour
See above.
System Configuration

LBRY Daemon version:
LBRY App version: v11
LBRY Installation ID:
Operating system: Win

Anything Else

Screenshots

Copied from original issue: lbryio/lbry-app#139

From @maximumplank on May 26, 2017 5:2
I'm having this same issue. Uploaded some content on an old version of the 0.10 browser, before I began having problems with the client. Now content that I've published is not showing up in the 'published' tab.

From @tzarebczan on May 26, 2017 13:29
Never came back for me. It was reported by kevdev and others on slack too.

Will look into this.
@tzarebczan did it sit at loading forever or eventually come back? file_list has some big performance issues atm, especially with large numbers of downloads/publishes (we're working on it).

Sitting at "loading" forever vs. coming back with "looks like you haven't
published anything" are possibly two different issues, but will be looking
into it either way.
On Fri, May 26, 2017 at 9:31 AM, maximumplank<EMAIL_ADDRESS>wrote:

Same here, published tab just shows "looks like you havent published
anything yet!" Or something like that.
On May 26, 2017 6:29 AM, "Thomas Zarebczan"<EMAIL_ADDRESS>wrote:

Never came back for me. It was reported by kevdev and others on slack
too.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/lbryio/lbry-app/issues/139#issuecomment-304282735,
or mute the thread
<https://github.com/notifications/unsubscribe-
auth/AVNFwd7hHfAb1sbeOjFrn66-I3s0XvFoks5r9tPPgaJpZM4NnLNX>

.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/lbryio/lbry-app/issues/139#issuecomment-304283030,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAgZVkkh8Gfhj8OoTS-b7yhRblJfJ4zaks5r9tQigaJpZM4NnLNX
.

--
Jeremy Kauffman, Founder, LBRY http://lbry.io/
(267) 210-4292
Build LBRY: get https://lbry.io/get, follow https://twitter.com/lbryio,
like https://facebook.com/lbryio

From @maximumplank on May 26, 2017 13:31
Same here, published tab just shows "looks like you havent published
anything yet!" Or something like that.
On May 26, 2017 6:29 AM, "Thomas Zarebczan"<EMAIL_ADDRESS>wrote:

Never came back for me. It was reported by kevdev and others on slack too.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/lbryio/lbry-app/issues/139#issuecomment-304282735,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AVNFwd7hHfAb1sbeOjFrn66-I3s0XvFoks5r9tPPgaJpZM4NnLNX
.

From @tzarebczan on May 26, 2017 13:38
Yup, sounds like different issues. Thanks Jeremy!

From @maximumplank on May 26, 2017 13:42
Sorry, must have misunderstood Thomas' issue. I'll file a new one.
On May 26, 2017 6:38 AM, "Thomas Zarebczan"<EMAIL_ADDRESS>wrote:
Yup, sounds like different issues. Thanks Jeremy!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/lbryio/lbry-app/issues/139#issuecomment-304284584, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AVNFwYaUAJmM9ntZU9dhcbZg7oA8f3I5ks5r9tW_gaJpZM4NnLNX
.

From @maximumplank on May 27, 2017 1:10
filed https://github.com/lbryio/lbry-app/issues/146 for the "looks like you haven't published anything" issue

From @tzarebczan on May 29, 2017 20:15
Also noticed today on a VM that the Downloaded page showed lbry://undefined in the downloaded page.  It's not a real claim..so probably related to this issue of the Downloaded page not showing.

From @tzarebczan on May 31, 2017 0:44
I did notice this today in my logs, not sure if its related:
2017-05-30 20:42:15,138 ERROR    lbrynet.lbrynet_daemon.auth.server:346: Failed to process file_list: string indices must be integers
Traceback (most recent call last):
File "site-packages\twisted\internet\defer.py", line 1299, in _inlineCallbacks
File "site-packages\lbrynet\core\Wallet.py", line 770, in _handle_claim_result
File "site-packages\lbryschema\claim.py", line 140, in load_dict
File "site-packages\lbryschema\encoding.py", line 33, in decode_fields
TypeError: string indices must be integers

From @finer9 on May 30, 2017 0:32
On 0.11.5 my Downloads/Publishes never resolves, it just says Loading...I suspect maybe this wouldnt happen on a fresh install

@finer9 does it actually never return or does it just return after a long time?
@tzarebczan that sounds like the root cause of the issue. Moving this to the daemon.

I literally left it overnight so it never returned.  But it worked fine
after deleting that metadata cache stuff jack/kay were working on recently
On Wed, May 31, 2017 at 12:56 PM, Jeremy Kauffman<EMAIL_ADDRESS>wrote:

@finer9 https://github.com/finer9 does it actually never return or does
it just return after a long time?
@tzarebczan https://github.com/tzarebczan that sounds like the root
cause of the issue. Moving this to the daemon.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lbryio/lbry/issues/661#issuecomment-305250202, or mute
the thread
https://github.com/notifications/unsubscribe-auth/APoYDEgPJzbcUp01i73eg9oDSWrhNkkuks5r_ZvDgaJpZM4Nr6bM
.

--
Josh Finer
COO/LBRY

@kauffj any updates on this one?

This is one for @jackrobison.

@jackrobison any idea what this is? It may be similar to this issue:
https://github.com/lbryio/lbry-app/issues/174
I still see the below in my logs and I'm not able to go into Downloads/Publishes section - just hangs on "loading..." - can't tell if its related to this error or not.  I believe @finer9 has the same issue with "loading..." but he cleared his up by deleted a bunch of files in lbrynet - I'd really wanna get to the root cause.
017-06-12 18:43:13,517 ERROR    lbrynet.lbrynet_daemon.auth.server:346: Failed to process file_list: 'ascii' codec can't decode byte 0xe2 in position 10: ordinal not in range(128)
Traceback (most recent call last):
File "site-packages\twisted\internet\defer.py", line 1299, in _inlineCallbacks
File "site-packages\lbrynet\lbrynet_daemon\Daemon.py", line 866, in _get_lbry_file_dict
File "ntpath.py", line 85, in join
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 10: ordinal not in range(128)

@jackrobison happens reliably when downloading lbry://casually-successful
017-06-14 08:51:55,726 INFO     lbrynet.lbrynet_daemon.Downloader:101: Download lbry://casually-successful status changed to initializing
2017-06-14 08:51:55,728 INFO     lbrynet.lbrynet_daemon.Downloader:101: Download lbry://casually-successful status changed to downloading_metadata
2017-06-14 08:51:55,728 INFO     lbrynet.core.client.ConnectionManager:38: Connection Manager 8d20e99a127c90c7b67641fefbe23609346058ab55ed878c4f3b66555c120ba65dcfdaf648410d171be6d027d53bc4b1 initialized
2017-06-14 08:51:55,754 INFO     lbrynet.lbryfile.EncryptedFileMetadataManager:246: Saved sd blob hash 8d20e99a127c90c7b67641fefbe23609346058ab55ed878c4f3b66555c120ba65dcfdaf648410d171be6d027d53bc4b1 to stream hash 9dba62280f52ecb18c8c675e9128b8e0b3ebe9e68e8357e8bbeb3f85c9ba5867802dab08efe70818f048035082ebba10
2017-06-14 08:51:55,765 INFO     lbrynet.lbrynet_daemon.Downloader:101: Download lbry://casually-successful status changed to running
Traceback (most recent call last):
  File "logging/handlers.py", line 76, in emit
  File "logging/handlers.py", line 156, in shouldRollover
  File "logging/__init__.py", line 734, in format
  File "logging/__init__.py", line 465, in format
  File "logging/__init__.py", line 329, in getMessage
UnicodeDecodeError: 'ascii' codec can't decode byte 0xcc in position 62: ordinal not in range(128)

Another user (https://github.com/lbryio/lbry/issues/706) reporting same issue of not being able to show downloads and published (stuck on loading) . That was the orignal subject of the ticket that was reopened here. Not sure if its intent was lost due to the said file list error.


Test coverage to 100%

Do the sloggy function by function test building.

All of the adts have tests, most are at 100% coverage but a few are in the 90s. After buttoning up tests for schemable and optics I'll come back around to bring all the branch coverage to 100% too.


Bug in Zulip Client - Right Click in Text Field

Hello,
if you open the context menu (in the textbox where you can send new messages)
There are two entries with "Direction".
See Screenshot for more details:

To Reproduce:
Install the latest Windows Client (0.5.1)... I've test it on Windows 7 x64 Pro
Greetings

I think this is a bug in the desktop client -- please reopen against https://github.com/zulip/zulip-desktop


feat: Update default backend weight to blue

Is my understanding (of the context around this pull-request) correct:

In the initial deployment of this Jump Start Solution (JSS), the frontend should only be using the blue backend service.
At some point in the Neos tutorial(s) of the JSS, the user will make the frontend aware of the green backend service.
Because of this, this pull-request removes the frontend's awareness of the green backend service.

That is correct! Thank you for documenting this.  The default configuration was a 50-50 split.  The tutorial also includes a step to introduce a 50-50 split, but it makes more sense to start from the all-blue configuration like you mentioned.


remove double closing tags in inline create button

Not much to say, about this, maybe some poem ?
//Roses are red
//Violets are blue
abstract class Poem {
//TODO

(picked online from some sub-reddit)

A new inspection was created.

The inspection completed: No new issues


fix: Add generated type test changes

This runs pnpm run typetests:gen to generate type test changes that are causing the publish pipeline to fail for this release branch.

Other than the pnpm version vs node version blocking CI, this seems fine. I'm not clear on why this change would be needed, but the version of type test tooling on this branch is old and known to do strange things like this, and the change doesn't do any harm, so if it makes it work, its fine.


Vulnerability roundup 85: xerces-c-3.2.2: 1 advisory [8.1]

search, files

[ ] CVE-2018-1311 CVSSv3=8.1 (nixos-20.03)

Scanned versions: nixos-20.03: a84b797b28e. May contain false positives.

20.03 is Frozen and EOL.
As such, issue is closed.


Fix #75

Improve error message when docker isn't connected correctly.
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[X] No

Creating a new PR with a different branch


Add output of which MapRegressionTest is started

For me it is not clear which test is running before a crash happens. So I added a log entry with the name of the test.

Added a log entry before and after the test.
This PR is in conjunction with #2402. For me it is not clear, if the crash happens while running th GeoTiff sample or a sample later. The crash occurs when a SymbolStyle should be drawn. But there isn't a SmbolStyle in the GeoTiff sample. So I added a start and end flag for each sample that runs to make it easier to find the right sample. If I have overseen this information and this PR is useless, then we can close it.

It crashed after "End MapRegressionTest MbTilesSample"
The next test would have been "Start MapRegressionTest RasterizingTileLayerGeoJsonSample"
So there are two possible Areas.

A Memory Leak/Corruption in Sqlite (Because of MbTiles)
A Memory Leak/Corruption in RasterizingTileLayer

@inforithmics Where did you see this? Could you reproduce this locally or do you have a protocol where it could be seen?

I saw this on the last GitHub action build. I couldn‘t reproduce locally. I‘m thinking about running the tests locally 10 times or more so if there is a problem in one test it should sow up

Ok, I got the error locally by running test "RasterizingTileLayerGeoJsonSample" in debug mode.

I would say, that the line 168 of file "SymbolStyleRenderer.cs", which is
    var path = vectorCache.GetOrCreatePath(symbolStyle.SymbolType, CreatePath);

make the trouble. All could be expected except path when the test crashes.

Ok, seems to me as a racing condition. From 10 times to run, it fails around 6 times.

I tried this branch and made a loop with 100 calls and it didn't crash on my computer. I tested it after I merged main into this branch. So it is using now SkiaSharp 2.88.7.

I run only this test in debug mode. Will try it again with the new version.

I run it 7 times with no problems. The 8th crashed.

Run it in debug mode and do something beside this. When I close the test tree after I start the test, then it crashes.

I could now reproduce it. Open the Editing Sample in Avalonia and move the Shape around then it crashes. So I can fix it from there.

How can I help?

I found out why it doesn't work every drawn Element in SkiaSharp should have it's own skpath.

Because of caching the All Symbols had the same SkPath so giving every symbol it's own skpath improved things considerably.
Clipping shouldn't be done on a cached path, but the clipped path should be cached.

               canvas.ClipPath(linePath);

Great you are looking into these hard to reproduce issues and not giving up on it. The bugs that are the hardest to find cause the most problems in the long run. Often people tend to ignore them because they don't happen very often.

@pauldendulk in our case they happen very often.
@inforithmics When you look into SkPath of the Skia documentation, go down to the "Detail description". The last line suggest that SkPath is threadbare if you call SkPath::updateBoundsCache (read also this). Perhaps we should try this when writing the SKPath to the cache?

Ok, looked into SkiaSharp implementation, but couldn't find the UpdateBoundsCache function. So it isn't there and if we like to have it, we must create it. Perhaps a PR?
By investigating further, the SkPath::updateBoundsCache() is internal only a SkPath->getBounds() call (see here). So it would be enough to add a call like this
    if (path is SKPath p) _ = p.Bounds;

after creating the path. But it doesn't work.
Perhaps related with this? And an message (quite old) or this or this about thread safeness of Skia.
I would say, caching for same pathes to one path isn't a good idea.

Pull request with my learnings and Bugfixes (does not work yet 100%)
https://github.com/Mapsui/Mapsui/pull/2425

I am going to merge this PR which just adds console logging. We might want to go back to this thread to see what is discussed.


Better GraphQL error handling

Summary of changes

Reference issue to close (if applicable)

Closes #620

Code Checklist

[ ] Tested
[ ] Documented

What's the status of this @AhmedKorim ?


Remove hashie

From @schneems article http://www.schneems.com/2014/12/15/hashie-considered-harmful.html
I really don't have a good argument for keeping around hashie. I seriously doubt anyone is using harvested as heavily as a project like omniauth, but we can be a good citizen.
I don't have a strong preference between returning Hashes vs OpenStructs. I think either will require a major version bump. (I haven't verified but I doubt we can get away with minor version bump if we choose OpenStruct).
I'd rather not go with Struct or our own Poros. I went that route early on and it caused way too much maintenance churn as things were added to the Harvest API.

No sense in keeping this issue alive for 3 more years. Closing.


How to use with swift3.0 & iOS9

CameraEngine swift 3 uses a lot of only iOS 10 apple api so I don't think it's possible.


Fix additional callbacks

Description of the change
Fixes a small bug in the method of train() sft_trainer.py where trainer_callbacks would append an array of user provided callbacks instead of concatenating the 2 arrays.
Without this change you get this exception:
self = <transformers.trainer_callback.CallbackHandler object at 0x32b558fa0>
event = 'on_init_end'
args = TrainingArguments(output_dir='/var/folders/p_/lhp3_gn503l7djn80tdzkf3h0000gn/T/tmpu2qek8_i', overwrite_output_dir=Fals...t_modules=None, batch_eval_metrics=False, cache_dir=None, max_seq_length=4096, packing=False, trackers=['file_logger'])
state = TrainerState(epoch=None, global_step=0, max_steps=0, logging_steps=500, eval_steps=500, save_steps=500, train_batch_si..., 'should_epoch_stop': False, 'should_save': False, 'should_evaluate': False, 'should_log': False}, 'attributes': {}}})
control = TrainerControl(should_training_stop=False, should_epoch_stop=False, should_save=False, should_evaluate=False, should_log=False)
kwargs = {}
callback = [<transformers.trainer_callback.TrainerCallback object at 0x30f3508e0>]
result = None

    def call_event(self, event, args, state, control, **kwargs):
        for callback in self.callbacks:
>           result = getattr(callback, event)(
                args,
                state,
                control,
                model=self.model,
                tokenizer=self.tokenizer,
                optimizer=self.optimizer,
                lr_scheduler=self.lr_scheduler,
                train_dataloader=self.train_dataloader,
                eval_dataloader=self.eval_dataloader,
                **kwargs,
            )
E           AttributeError: 'list' object has no attribute 'on_init_end'

../venv/lib/python3.10/site-packages/transformers/trainer_callback.py:498: AttributeError

Related issue number
Contributes to #142
How to verify the PR

Invoke the train() method with an additional_callbacks parameter that's an array containing at least 1 callback.
Was the PR tested

[x] I have added >=1 unit test(s) for every new method I have added.
[x] I have ensured all unit tests pass

@Ssukriti @anhuong This fix would really help the benchmarking effort as it removes the need for us to maintain a fork to work around it (and hence falling out of synch). Any help in getting it merged appreciated. :-)

LGTM. Thanks @VassilisVassiliadis I missed this check in my unit testing PR.

No problem!

@anhuong @Ssukriti @alex-jw-brooks Just a bump on this as we'd like to get rid of the need for a fork ASAP and this is just a single line change :-)


Shutdown CTRL+C

It seems that the console is not responding to the regular CTRL+C event(both System.console and swing terminal ), this is a limitation?

Currently, text-io expects only regular text as input. For key combinations such as Ctrl+C the behavior is unspecified and it depends on the underlying TextTerminal implementation.
For Swing, Ctrl+C is by default associated with "copy".
Using Ctrl+C with a SystemTextTerminal or a ConsoleTextTerminal will shut down the JVM.
Note however, that (since version 1.5.0) TextIoFactory usually returns a JLineTextTerminal if System.console() is not null. JLineTextTerminal currently ignores the Ctrl+C, but this behavior can be easily changed by executing: reader.setHandleUserInterrupt(true); I should probably insert this statement in the JLineTextTerminal constructor.

Thanks for explanation, make sense. Although maybe would be nice to have some generic key listener I know that it would be hard for non-GUI console without jna.
For SwingTextTerminal instance for now probably I can just add custom event dispatcher

btw, why the console would forbid closing the window, I would expect that terminal should have common or similar behavior for all implementations ?
https://github.com/beryx/text-io/blob/master/text-io/src/main/java/org/beryx/textio/swing/SwingTextTerminal.java#L139

I added support for handling user interrupts. For the Swing and the Web text terminal, Ctrl+Q is used by default to trigger a user interrupt. (I didn't use Ctrl+C, because it is usually associated with copy in these environments.) The  key combination that triggers a user interrupt can be changed programmatically.
Closing the Swing window will also trigger a user interrupt.
The default user interrupt handler shuts down the JVM. A different handler can be configured by calling registerUserInterruptHandler(). See the commented lines in  TextIoDemo for examples.

Implemented in 1.9.0.
Configuration improvements (using terminal properties) in 2.0.0.


Contrib-pointers for additional Services and techniques

I recently tested the proposed integration of Elastic Search (#1320), which was not adopted due to the lack of a wider community interest.
But for some developers, like myself, this would be very handy.
I understand, that ddev cannot support every service out there. But what about creating a contrib-repository, where additional services can be contributed and managed by the community.
That way, there would be a central place, to look for additional services.
I got this idea from Symfony Flex. The core-recipies (https://github.com/symfony/recipes) for flex are maintained by the Symfony project, but theres also a contrib-repository (https://github.com/symfony/recipes-contrib) which is manage by the community.

Thanks for this good idea. We'll take a look at those other examples. I'm not sure how a free-form contrib repo could be organized though.

I find myself regularly pointing people to a small set of articles and Stack Overflow articles. I'm thinking that we just need a good (and maintained) list of pointers. Not sure whether it should be a repo or something else. Maybe it should be a docs page.

Of course, that would also help a lot! But let me point out some advantages, if people can provide their recipies for services directly in a git-repo:
Not everyone who implements custom services for ddev publishes them on SO or anywhere else. With a Contrib-Repo, we would have that single place anyone could contribute their hacks. And it may encourage people to publish.
Also if one solution is outdated or has issues, the community could work on that. This would be complicated with links to SO or any other websites.
Like I said, a maintained list of links would also help, but I would love to see a repo.

Added awesome-ddev for external resources.
Created ddev-contrib for exactly this use-case.

ddev-contrib and awesome-ddev are open for business. @mkrauser how about a PR (sorry for the do-over) for elasticsearch there?


<EMAIL_ADDRESS>Regular Expression Denial of Service vulnerability

What are you trying to achieve?
Clean up the codebase security / performance alerts
We recently implemented Snyk and are going through a cleanup process to see where we can tidy up things in the system. Our only outlier seems to be this alert that doesn't seem to be high priority but would be nice to clean up as well.
I do see this package has not been updated in a while, is there a more maintained alternative that can be put in place to address this?
What do you see
https://cwe.mitre.org/data/definitions/1333.html

Details

CodeceptJS version: 3.5.3

Thanks, this will be fixed in next release by replacing package to html-minifier-terser


It seems that animated charts shrink on Chrome on mobile devices since V4

Expected behavior
The animation should work as on desktop and IOS devices.
Current behavior
On mobile all sample charts with an animation included shrink to a bare minimum over time.
e.g. https://www.chartjs.org/docs/latest/samples/animations/delay.html
Reproducible sample
https://www.chartjs.org/docs/latest/samples/animations/delay.html
Optional extra steps/info to reproduce
No response
Possible solution
Seems to work in the last v3 scripts.
Context
No response
chart.js version
v4.2.1
Browser name and version
Chrome 110.0.5481.64
Link to your project
No response

What device are you using?
Tested with a iphone 11 and it seemed to work fine

I tested it on an Pixel 7 (Android 13).
I can confirm that on an iphone (Safari and Chrome) everything just works fine.

I replicated it on a friends Pixel 7 Pro

Same for me on Android 13, but only in Chrome
Chrome 114.0.5735.61
Android 13; M2012K11AG Build/TKQ1.220829.002

Also getting this on:
Android 13; Pixel 7 Build/TQ3A.230705.001
Chrome 114.0.5735.226

Can confirm the same on
Android 13; Samsung Galaxy A53 Build/TP1A.220624.014
Chrome 119.0.6045.66
Chart.js version: 4.4.0

Can't replicate it on the same device when rendering the page using the system WebView (through a Capacitor app)


onError is called every time

https://github.com/mui-org/material-ui-pickers/blob/689d7d33bdac5e649d4e5c6ca37f9f523c80b8cf/lib/src/_shared/hooks/usePickerState.ts#L94-L98
Shouldn't it also consider the validationError to be set before calling it? this useEffect will trigger when the value changes
https://codesandbox.io/s/nifty-hofstadter-mk285?fontsize=14&hidenavigation=1&theme=dark

I ran into this as well from a different angle. We add server validation errors from formik using formik.setFieldError("fieldName", serverError)
These errors quickly gets reset by pickers since they seem to call onError quite often. We worked around it by having a cache of last error and last value - if value doesn't change we don't clear the error.
Seems a bit silly though, is there a better way? Could MUI pickers possibly stop clearing errors unless something actually changed?

@SweVictor Try v4 (https://next.material-ui-pickers.dev/guides/forms).
We reworked validation from scratch to be more useful with formik and other form helpers.

@dmtrKovalenko Oh, nice, and thanks for the quick reply!
I'll absolutely try that out. Alpha seems to signify it's maybe not ready for production use yet? Either way, hopefully a RC will soon be here.
Thanks either way and great work on a nice library!


How to set up the radius for streetview? There are some coordinates have no streetviews available.

Radius prop is now available 2efcf8fae318ade5ff72b94a067b411d2f0126db
See Readme for more info


Correction for raw affiliation AGAP, Univ. Montpellier, CIRAD, INRAE, L'Institut Agro, Montpellier, France

Correction needed for raw affiliation AGAP, Univ. Montpellier, CIRAD, INRAE, L'Institut Agro, Montpellier, France
raw_affiliation_name: AGAP, Univ. Montpellier, CIRAD, INRAE, L'Institut Agro, Montpellier, France
new_rors: 03rnk6m14;003vg9w96;05kpkpg04;051escj72;02w4exq36
previous_rors: 03rnk6m14;003vg9w96;05kpkpg04;051escj72
works_examples: W4393803902;W3215373548
contact: 81ce69dba17af5bc570f0620c6db9a61:673e485ec352ee6c0ca53a6eedc4706eec6e @ inrae.fr

This issue was accepted and ingested by the OpenAlex team on 2024-11-18. The new affiliations should be visible within the next 7 days.


cloak: 0.2.0 -> 0.3.0

Motivation for this change
New upstream release: https://github.com/evansmurithi/cloak/releases/tag/v0.3.0
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
~22.05 Release Notes (or backporting 21.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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

@smancill Can you confirm that it still builds on Darwin?

Result of nixpkgs-review pr 157432 run on x86_64-darwin 1

1 package built:

cloak


Correct screen aspect ratio

It's currently at 1:1.8, must change to 1:2.
When this is done, I'll see if it corrects moiré. If not, I'll make a new issue for that specifically.

Corrected. New skins were made to fix the moiré issue.


[Incremental] Fix race on finishedJobResults

The build engine can exit before all jobs have registered their results in finishedJobResults. Then when the build record is written, the read of these results races with the writes. Protect these with a semaphore.

rdar://problem/72341819

@swift-ci please test

This fixes the data race. Does it guarantee that build records will be written after all Job finishes?

This fixes the data race. Does it guarantee that build records will be written after all Job finishes?

Not sure I follow the question. Are you worried that the build record might never be written?

The driver passes the XC tests, some of which count on the build record getting written, so I think it should work in that respect. Are you seeing something I'm not seeing?


Support libpurple?

Description
Would it be feasible to implement the protocol that you are using to communicate into libpurple (pidgin)? Pidgin supports almost all other instant messaging protocols, and has a vast majority of users.
Specifications

OS: multiplatform

Probably will consider in long run...


Allow Indentation check to handle "align when multiline" option

https://github.com/arturbosch/detekt/blob/master/detekt-formatting/src/main/kotlin/io/gitlab/arturbosch/detekt/formatting/Indentation.kt seems to assume every line will be indented by some multiple of 4 spaces.
In Android Studio, I have these options checked:

The result is code that looks like:
fun example(arg0: String, arg1: String,
                      arg2: String) {

This is not a multiple of 4 spaces.
In general, I want to ensure that all code is indented properly, but it's not always going to be a multiple of 4 spaces.

I think I will rework the formatting part in M11, after the gradle plugin and jcenter publishing in M10 is out. Thx!

Indentation check was enhanced a bit but will not be so powerful as idea. I integrated idea formatting and inspections as gradletasks. The recommend way is to use the new detektIdeaFormat task as of M11


[Feature] correct name when generating category/page with schematics

Description
At the moment, when I create a category/page using some /, the generated exported const name is wrong.
For example:
nx generate @ng-doc/builder:category --title=04-one/theme --order=0 --path=apps/public-doc/src --route=one-theme
will create a category with name:
const 04One/themeCategory
Proposed solution
In such cases, it could be interesting to only keep the last fragment of the title, so the directories still get correctly generated and the title will be corrected also
Alternatives considered
No use of / but if we can have an easier life... :)

Actually, I think the working principle of the title parameter is not entirely correct at the moment. The schematic generates the variable name based on the title, but this won't work for all cases. For example, in your case or if the title contains non-Latin letters, such as Cyrillic or other forbidden characters in variable names. That's why I would probably consider how to eliminate this issue.
I have a couple of ideas. The first one is a solution for your problem and the one I described earlier. I could add an additional parameter for the variable name so that you can invoke the schematic like this:
nx generate @ng-doc/builder:category --name=theme --title=04-one/theme --order=0 --path=apps/public-doc/src --route=one-theme

However, I'm not happy with it as it looks complicated.
The second solution, which I started thinking about a couple of weeks ago, involves using special functions. In fact, they will be empty and return the configuration object as is. They will only be needed for type checking. With this solution, the generated page file would look like this:
import { page } from '@ng-doc/core';

export default page({
  title: 'my-title',
  mdFile: './index.md',
});

It looks simpler to me, without additional variables, and it won't cause any breaking changes. Meanwhile, you will be able to use the schematic command like this:
nx generate @ng-doc/builder:category --title=theme --order=0 --path=apps/public-doc/src/04-one --route=one-theme

In one of our libraries, we also started using object like you, but we will also switch to function for efficiency. So I will agree with the principle of your second solution.
So, if I summarize your point:

Switch exported configuration object to exported default function
Separate the behavior of the property title so it is used only for the configuration of NgDoc and not for creating the whole path with sub-directories
The path property provisioned inside the CLI will generate all directories and sub-directories correctly

I completely agree 👍

Yes, this pattern will be applied to all types of files you listed. I will also add a migration to transition existing code to the new format. While this feature won't break anything, I believe nobody wants to manually update old configurations to the new format. 😄

@Nxtivision I encountered a problem when trying to build the application in production mode. It appears that I cannot use this pattern of exporting a function call because the Angular compiler cannot analyze the components and modules that you are using as targets for playgrounds, demos, and in the imports field. This is because the compiler expects static values, while a function call returns a dynamic value. Attempts to make the accepted configuration static using as const or readonly did not succeed.
I could reimport these entities into the generated files, but I'm concerned that it might cause problems in the future. Therefore, I have to roll back these changes and possibly use transliteration because even the approach with satisfies does not work. It seems that the Angular compiler does not support it:
import { NgDocPage } from '@ng-doc/core';
import { NgDocTagComponent } from '@ng-doc/ui-kit';

export default {
	title: `Page`,
	mdFile: './index.md',
	playgrounds: {
		TagPlayground: {
			target: NgDocTagComponent,
			template: `<ng-doc-selector>Tag</ng-doc-selector>`,
		},
	},
} satisfies NgDocPage;

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

v16.8.0
GitHub release

Your semantic-release bot :package::rocket:


Error sequelize db:migrate

when I try to run $ npx sequelize db:migrate
Sequelize CLI [Node: 16.15.0, CLI: 5.5.1, ORM: 5.22.5]
ERROR: Error reading "dist/config/database.js". Error: SyntaxError: Unexpected token ':'
I am using Amazon Linux 2 instead of Ubuntu because I already have an instance with Puppeteer installed. Is it because I use a different OS that causes this, or is there anything I missed?

I don't think this is due to your OS, apparently it's something in the file, build, or even a lack of defined parameters in the .env. How is your .env file?

I don't think this is due to your OS, apparently it's something in the file, build, or even a lack of defined parameters in the .env. How is your .env file?

NODE_ENV=DEVELOPMENT
BACKEND_URL=https://backend.domain.com
FRONTEND_URL=https://ticket.domain.com
PROXY_PORT=443
PORT=8080

DB_HOST=localhost
DB_DIALECT=mysql
DB_USER=
DB_PASS=
DB_NAME=whaticket

JWT_SECRET=3123123213123
JWT_REFRESH_SECRET=75756756756

I am also using MariaDB as a database server

you need to define the DB_USER, DB_PASS, and as your DB is MariaDB, set the DB_DIALECT to mariadb.


Hi anyone knows how we can save the solution as a pdf file?

I need to replace puzzle.show() with a something like solution.save()

@tomahocbc, I'm working on this for issue #14. I should have a new version released next week and will update here so you are aware. Thanks!

@tomahocbc, I've got a working PR #16 that I think provides the functionality you are looking for.
You can call the save() method with solution=True to have the solution exported within the same file as the puzzle.
p = WordSearch("dog cat pig")
p.save("test.pdf", solution=True)

...result in the pdf file linked below. The "solution" is added as a second page with the words highlighted in red just as you get with the show(solution=True) method.
TestWithSolution.pdf
p = WordSearch("dog cat pig")
p.save("test.csv", solution=True)

...result in the csv file linked below. The "solution" is added at the bottom of the csv file with only the puzzle words visible. All other characters are represented as a blank space " ".
TestWithSolution.csv
Have a look and let me know what you think. Thanks!


IDVA3-1660 Updated service start screen to v9 of prototype

CI: No security warnings found

Looks good


md-checkbox-column should have a set width

When a table only has a column or two but the table is wide (i.e. full width on 1080p), the md-checkbox-column grows like so:

I think the checkbox column should have fixed with no matter the number of columns and the contents of cells.
The image above can be recreated by simply deleting all but one column in the codepen demo.

Should be fixed now. Instead of creating a new patch I just moved the last tag v0.9.7 to the latest comment.

It's in the lines by what I meant, but with this solution it not cuts off the ink ripple effect of Angular Material.


Question: Can I specify the snapshot/report name?

Hi,
Is it possible to specify a name for the report issued? The snapshot is saved as report-tags-date-12hTime.png, I would like to be able to name it something like report-HumanFriendlyTags-date-24hTime.png
Thanks

Now there is no such possibility. It will be added as soon as possible.

Great. :-)
Thanks for taking the time to answer.

@smoreaud Now, in Sentinl 5.5.X and Sentinl 5.6.X you can specify name for the report file. Download .zip according to your Kibana version.

Nice !
Thanks @sergibondarenko !

Thank you so much! :-)


(feature request) option to load a random background image from folder

Sorry if this is not the correct place for this
I just wanted to suggest an option to select a random background image from my collection due to having so many more backgrounds than screens on the deck.

Cssloader itself cannot do this, and it's not a planned feature to implement it


Integrate persistent active job backend

Closes #374
Installed sidekiq gem. Works fine in development, will need extra work in production. Both sidekiq and redis need to be running alongside the app. There are a number of ways to achieve this including the capistrano gem or making our own scripts on the production server.
Useful link

Is this good to go?
Did you finish the "extra work in production"

The code is good is to go, I'll set up the production side stuff and then ping here when that's complete

What kind of stuff needs to be done on the server? Please make sure you document what you did / are doing so more than one person knows how the server is configured. :)
Also, you may want to add the capistrano sidekiq gem if you want capistrano to restart sidekiq.

https://blog.sensible.io/2013/08/20/setting-up-redis-for-production-environment.html


Update postcss.md

when in Vue CLI ，Vue CLI has preseted  postcss，the file named ’postcss.config.mjs‘ can't be identified，should use ’postcss.config.js‘，then mjs will be more widely-used

Vue CLI is no longer recommended. This is due to it using the legacy PostCSS version - we should put our best effort into moving to ESM, not instead recommanding doing the backward.