PLDCorrector: priors restrict background fitting

Problem description

There seems to be an issue with how the background_model design matrix is being generated. With the current default priors on background_model (line #231-232 of pldcorrector.py), the background model is flat for seemingly all targets, forcing the pixel_series to pick up the background noise. This has detrimental effects on its ability to fully capture the systematic trends.
Example
With current priors:

However, removing these priors causes an unwanted tradeoff between background_model and pixel_series.
Without current priors:

Expected behavior

background_model and pixel_series should capture distinct sources of noise. This appears to work more consistently for K2, where the dominant source of noise is the pixel_series, but for TESS, the tradeoff is problematic.
This issue, combined with #822, indicate that there are remaining necessary changes to our PLDCorrector.
Possible solution
If parameterized carefully, the pixel series, in combination with a spline (or GP) should be able to capture all sources of noise (as demonstrated by EVEREST and our previous implementation). My worry is that by introducing a third design matrix, we've overcomplicated the problem. Evidence of this can be seen in the above plots, showing that the restricted, flat background actually returns a higher precision corrected light curve.
I'll experiment with simplifying our solution, but will not make this a huge priority, as the pixel series tends to do a decent job even without much contribution from the background model.
Environment

platform: OSX
lightkurve version: 2.0a2.dev
installation method: source

First reaction: we may want to have a close look at the pixel data near e.g. BTJD 1379, to understand exactly what the data looks like in those problematic cadences.

@nksaunders It looks to me like the prior is too strict in the first example, and too loose in the second example.  Is the solution simply to have a less-strict prior?  Are we confident that our initialization of the prior is correct, cf. line 230:
https://github.com/KeplerGO/lightkurve/blob/cf5794f3f83bdddcd49d0e4c9456bc273b4f45b4/lightkurve/correctors/pldcorrector.py#L227-L232

I propose closing this issue and use #847 to discuss the topic.


Compare region view-selected gene not shown

Brucelles suis 1330 wbkB gene on the beta site.  When I click on the compare region view, 5 genomes appear, but not suit 1330

Harry, when I display only 5 genomes, the Brucella suis 1330 do not appear. However, when I select 10 or more genomes, it appears at the top. Can you please check if the problem is because of the parsing on your side or related to API?

Another related issue: for some tracks, I am getting errors. My guess is that, most likely, it because those genomes are not available in PATRIC?!

That first track in error, for Brucella melitensis bv. 1 str. M111, is a genome in patric. I ran the query programmatically and it appears to be returning valid data.
—bob
On Jun 9, 2015, at 11:14 AM, mshukla1 <notifications<EMAIL_ADDRESS>wrote:
Another related issue: for some tracks, I am getting errors. My guess is that, most likely, it because those genomes are not available in PATRIC?!
[screen shot 2015-06-09 at 12 14 03 pm]https://cloud.githubusercontent.com/assets/1236463/8063131/23833a10-0ea1-11e5-8bba-b0097057f2b7.png
—
Reply to this email directly or view it on GitHubhttps://github.com/PATRIC3/patric3_website/issues/257#issuecomment-110418918.

Bob, it seems like, SAP does not return any feature for these three genomes.
Here is a part of raw result from SAP,
...
"features": [],
"genome_id": "1004955.3",
"genome_name": "Brucella melitensis bv. 1 str. M111",
"pin": "fig|1004955.3.peg.3335",
"row_id": 14
},
{
"features": [],
"genome_id": "1004956.3",
"genome_name": "Brucella melitensis bv. 1 str. M28-12",
"pin": "fig|1004956.3.peg.3335",
"row_id": 15
},
{
"features": [],
"genome_id": "1004957.3",
"genome_name": "Brucella melitensis bv. 1 str. M5",
"pin": "fig|1004957.3.peg.3339",
"row_id": 16
},
...

anyway, I have added a check to skip genomes that do not have any feature.
fixed and available on beta.

Can you send me the corresponding sap query ? When I ran one against a different peg I was getting feature data.

From: Harry Yoo<EMAIL_ADDRESS>Sent: Tuesday, June 09, 2015 4:44 PM
To: PATRIC3/patric3_website
Cc: Olson, Robert D.
Subject: Re: [patric3_website] Compare region view-selected gene not shown (#257)
Bob, it seems like, SAP does not return any feature for these three genomes.
Here is a part of raw result from SAP,
...
"features": [],
"genome_id": "1004955.3",
"genome_name": "Brucella melitensis bv. 1 str. M111",
"pin": "fig|1004955.3.peg.3335",
"row_id": 14
},
{
"features": [],
"genome_id": "1004956.3",
"genome_name": "Brucella melitensis bv. 1 str. M28-12",
"pin": "fig|1004956.3.peg.3335",
"row_id": 15
},
{
"features": [],
"genome_id": "1004957.3",
"genome_name": "Brucella melitensis bv. 1 str. M5",
"pin": "fig|1004957.3.peg.3339",
"row_id": 16
},
...
—
Reply to this email directly or view it on GitHubhttps://github.com/PATRIC3/patric3_website/issues/257#issuecomment-110513571.

Harry, for the same gene, I don't see anything in compare region view now!!!
https://www.beta.patricbrc.org/portal/portal/patric/CompareRegionViewer?cType=feature&cId=PATRIC.204722.5.NC_004310.CDS.517393.518247.rev&tracks=&regions=5&window=10000&loc=1..10000

Checked, again. It is working now and suis 1330 is at the top. Thanks.


Create table name to table id map in zookeeper

Tables in zookeeper are conceptually organized as a Map<TableId, TableName>.  A lot of code in the Accumulo client needs the inverse Map< TableName, TableId>.  There is complex code in the Accumulo client related to inverting the map in zookeeper and keeping it up to date.  If an index were built in zookeeper of the form Map< TableName, TableId> then the complex code in the client could possibly be removed.  Also mapping a table name to table id could be more efficient, avoiding always reading all tables to map a single table name to a table id. This would reduce the load on zookeeper server for the case of lots of client and lots of tables.  For more details see the comments on #4684.

I think the best way to do this would be to remove all the names from under each table, and create a new single node (maybe per namespace?) that retains the table name mapping for all tables. Otherwise, it would be a nightmare to try to maintain consistency between the locations. I might be interested in working on this or helping direct somebody else. @meatballspaghetti recently asked me for ideas of what issues to work on, and might be interested in this.

I can look into this.


feat: add exam boards to programme page - LESQ-57

Description

Adds exam boards to programme page
Lists tiers above exam board if there are exam board tiers

How to test

Go to ks4 - combined science or history (subject listing page needs to include unit Variant tiers so you need to manually set the url atm)

beta/teachers-2023/key-stages/ks4/subjects/history/programmes
beta/teachers-2023/key-stages/ks4/subjects/combined-science/programmes
Checklist

[ ] Added or updated tests where appropriate
[ ] Manually tested across browsers / devices
[ ] Considered impact on accessibility
[ ] Design sign-off
[ ] Approved by product owner

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


bluemediafile.sbs not working like it used to

Domain
bluemediafile.sbs
Link
https://bluemediafile.sbs/url-generator.php?url=+F30sKVGya5zG++539sIDeknUvP7uCWirMMYS0undWjwizvZTIxdeCQywNXUvAupkYoMa6QvLZJo07Fpj9DKtRJs64+8n32yBxvXjAdzH08=
Version
Version 0.2086
What browsers are you seeing the problem on?
Microsoft Edge
What OS are you seeing the problem on?
Windows
Anything else?
there is a 5 second countdown, to the download button
but after that, even clicking the download button doesn't go to the destination , you have to click it about 5-6 times (that opens new AD tabs) THEN it finally goes to the destination site/page

Should be fixed in #876.


Update sbt-avrohugger to 2.6.0

About this PR
📦 Updates com.julianpeeters:sbt-avrohugger from 2.0.0-RC22 to 2.6.0
📜 GitHub Release Notes
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.julianpeeters", artifactId = "sbt-avrohugger" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.julianpeeters", artifactId = "sbt-avrohugger" }
}]

labels: sbt-plugin-update, early-semver-minor, semver-spec-minor, version-scheme:semver-spec, commit-count:1

Superseded by #135.


[FEATURES] Build docker image for alluxio 2.7.2

What feature you'd like to add:
Why is this feature needed:

fixed by #1336


Fix python3 syntax errors

Retains python2.7 compatibility for all files. Fixes only syntax errors,
tests still fail on python3 for various reasons.

Rebased on top of your fixes. I am out for a while, next week is the OpenStack summit, so I may find some time to work on the patches some more. I've got it down to 39 fails and 32 errors in this branch with python3.4. There is at least one str method returning bytes that will fix many of those, and then the rest may be delicate strings/bytes problems.


Mc fix index route

Fixed typo in Index#setupController which results in none of the setup running.

:octocat:


Failed to load store key

Key store error
Failed to load keystore
Please try again later
Have to keep recovering my wallet.

Hey wanted to provide you an update on a trial I am doing.
I remove bread wallet from my phone and have repeatedly open and close the app force quit the app and not lost the stored keys yet I will let you know if I have any more problems but the problem. May be the storage location of the loaf wallet keys and bread wallet unsure just something I am trying.

Did you install LoafWallet onto your SD card? Or enable encryption on your device/sd card.

Just checked installed on phone sd card not showing any loaf info
On Nov 28, 2017 7:56 AM, "Loshan T"<EMAIL_ADDRESS>wrote:

Did you install LoafWallet onto your SD card? Or enable encryption on your
device/sd card.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/litecoin-foundation/loafwallet-android/issues/18#issuecomment-347569077,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Agd-0vB0FTtXBwxko-FIjLMNltZYcwvHks5s7C0zgaJpZM4Qsedw
.

3 years no activity . closing


Admin Access required every day

I work at a place where you have to go through many layers of red tape to get admin access to my workstation. Even after getting that access and adding whatever helper this is .... I get this pop up every day.

Redownload VS Code, place it into your User's Applications folder. Make sure it's not quarantined. It should never ask you for credentials any more.


{MISE_CONFIG_DIR}/mise.{MISE_ENV}.toml not used by mise

Describe the bug
I have a mise config file, located in $MISE_CONFIG_DIR, mise.toml.
I am using mise.toml to store global mise settings that I do not want to track with git

I am trying to use this file as a workaround, until there is a fix for https://github.com/jdx/mise/issues/2773

However, I see that the env vars I am setting in mise.toml are not getting loaded into my shell, and that when I run mise doctor, this config file isn't listed as having been loaded.
To Reproduce

Set the MISE_CONFIG_DIR env  to a local directory in your shell profile (I'm using zsh)
Create a mise.toml in the MISE_CONFIG_DIR with some settings, env vars, etc

Expected behavior
I see that {MISE_CONFIG_DIR}/mise.{MISE_ENV}.toml is listed as on the file lookup path for mise profiles based on the docs, but it looks like this file is not getting loaded for some reason.
mise doctor output
❯ mise doctor
version: 2024.10.7 macos-arm64 (2024-10-14)
activated: yes
shims_on_path: no

build_info:
  Target: aarch64-apple-darwin
  Features: DEFAULT, NATIVE_TLS
  Built: Mon, 14 Oct 2024 22:13:17 +0000
  Rust Version: rustc 1.81.0 (eeb90cda1 2024-09-04) (Homebrew)
  Profile: release

shell:
  fish
  fish, version 3.7.1

dirs:
  data: ~/.local/share/mise
  config: ~/projects/dotfiles/mise
  cache: ~/Library/Caches/mise
  state: ~/.local/state/mise
  shims: ~/.local/share/mise/shims

config_files:

backends:
  cargo
  core
  go
  npm
  pipx
  spm
  ubi
  vfox

plugins:
  node  https://github.com/asdf-vm/asdf-nodejs#c36e6f0

toolset:

env_vars:
  MISE_PYTHON_DEFAULT_PACKAGES_FILE=~/projects/dotfiles/mise/default-python-packages
  MISE_NODE_DEFAULT_PACKAGES_FILE=~/projects/dotfiles/mise/default-npm-packages
  MISE_CONFIG_DIR=~/projects/dotfiles/mise
  MISE_ENV=development
  MISE_RUBY_DEFAULT_PACKAGES_FILE=~/projects/dotfiles/mise/default-gems
  MISE_SHELL=fish

settings:
  activate_aggressive = false
  all_compile = false
  always_keep_download = false
  always_keep_install = false
  asdf_compat = false
  cache_prune_age = "30d"
  ci = false
  color = true
  debug = false
  disable_backends = []
  disable_default_registry = false
  disable_hints = []
  disable_tools = []
  experimental = false
  fetch_remote_versions_cache = "1h"
  fetch_remote_versions_timeout = "10s"
  go_default_packages_file = "~/.default-go-packages"
  go_download_mirror = "https://dl.google.com/go"
  go_repo = "https://github.com/golang/go"
  go_set_gopath = false
  go_set_goroot = true
  go_skip_checksum = false
  http_timeout = "30s"
  jobs = 4
  legacy_version_file = true
  legacy_version_file_disable_tools = []
  libgit2 = true
  log_level = "info"
  not_found_auto_install = true
  paranoid = false
  pin = false
  plugin_autoupdate_last_check_duration = "7d"
  python_default_packages_file = "~/.default-python-packages"
  quiet = false
  raw = false
  trace = false
  trusted_config_paths = []
  use_versions_host = true
  verbose = false
  yes = false

  [cargo]
  binstall = true

  [node]

  [pipx]
  uvx = false

  [python]
  default_packages_file = "~/.default-python-packages"
  pyenv_repo = "https://github.com/pyenv/pyenv.git"
  venv_auto_create = false
  venv_stdlib = false

  [ruby]
  default_packages_file = "~/projects/dotfiles/mise/default-gems"
  ruby_build_repo = "https://github.com/rbenv/ruby-build.git"
  ruby_install = false
  ruby_install_repo = "https://github.com/postmodern/ruby-install.git"

  [status]
  missing_tools = "if_other_versions_installed"
  show_env = false
  show_tools = false
1 warning found:

1. plugin node overrides a core plugin

1 problem found:

1. shims are missing, run mise reshim to create them
   Missing shims: ks

Additional context
.zshrc:
export XDG_CONFIG_HOME=~/projects/dotfiles

# mise
export MISE_CONFIG_DIR="$XDG_CONFIG_HOME/mise"
# development, testing, production
export MISE_ENV="development"
eval "$(/opt/homebrew/opt/mise/bin/mise activate zsh)"

export MISE_RUBY_DEFAULT_PACKAGES_FILE="$XDG_CONFIG_HOME/mise/.default-gems"
export MISE_NODE_DEFAULT_PACKAGES_FILE="$XDG_CONFIG_HOME/mise/.default-npm-packages"
export MISE_PYTHON_DEFAULT_PACKAGES_FILE="$XDG_CONFIG_HOME/mise/.default-python-packages"

$MISE_CONFIG_HOME/mise.toml:
[env]
MACHINE='work'

TLDR
mise can find $MISE_CONFIG_DIR/config.{MISE_ENV}.toml but not $MISE_CONFIG_DIR/mise.{MISE_ENV}.toml

The docs mention $MISE_CONFIG_DIR/mise.{MISE_ENV}.toml, with MISE_ENV="development" that translates to a file named $MISE_CONFIG_DIR/mise.development.toml. A file $MISE_CONFIG_DIR/mise.toml is currently not supported in this location.

I see thanks for clarifying that for me, I'll close this since I thought the {MISE_ENV} in the filename was optional


Delete or Archive Original Upon Completion

Forgive me if this has been answered already, I’ve looked thru the Issues both open and closed and haven’t found an answer.
Is there an option to remove the original file(s) or move them to an archive folder upon successful transcoding or must this be done manually?
Thanks in advance!

@sixshooterz I believe there might have been a discussion about this in an unrelated issue. But I can't find it either. :)
There is no option to delete original files and there never will be. Sorry. This is an idea fraught with danger, not to mention having security implications.
There is no option to archive original files because "archive" has too many meanings to engineer a one-size-fits-all solution. Sorry.
Really, both of these tasks are best taken care of in your batch file. And that is a file that I intentionally do not provide. :) Although I do show you how to make one:
https://github.com/donmelton/video_transcoding#batch-control-for-transcode-video
Does this answer your question sufficiently?

It absolutely does and makes 100% sense! I thought as much but it never hurts to ask.
My mention of archive was a temporary holding place for the original file(s) in case upon inspection of the transcoded version there was an issue the original could simply be copied back. I’ll take a look at the batch control page.
Thank you for such a speedy reply!

@sixshooterz You are very welcome! And feel free to comment here or open another issue if you have questions about modifying the batch file.


#3193 - New OCP Routes

Main changes

Added certificate, key, and caCertificate to routes.
Added the proposed annotations to the same routes. Information about the route annotations and its intentions can be found in route-specific-annotations_route-configuration.
Renamed the routes (now sims.studentaidbc.ca) to allow both routes to exist at the same time for now.
Only the certificate contents are provided as parameters to allow the correct line-breaking.

Additional Steps

Change Keycloak properties for: aest, institution, student, and supporting-users.

Valid Redirect URIs: https://dev.sims.studentaidbc.ca/*
Web Origins: https://dev.sims.studentaidbc.ca

Created a new GitHub variable DOMAIN_PREFIX (created as a regular var because it is not sensitive).
Create the new variables TLS_CERTIFICATE, TLS_KEY, TLS_CA_CERTIFICATE. These were not added to the sample config because there is no reason for them to exist in the local environment.

Non-directly related change

FORMIO_ROOT_EMAIL and FORMIO_ROOT_PASSWORD are no longer regenerated at every form.io server deployment to avoid credentials reconfigurations along the applications. The credentials should be changed due to a password rotation process and not during the server update.

TODO

Ensure release instructions for the Additional Steps above.

@andrewsignori-aot
E2E test seems failed in this PR, it needs to pass all E2E test?

The failed tests are intermittent issues that also exist in other PRs.
The ticket #3652 was created a few days ago to investigate those.


java.lang.NoSuchMethodError: it.unimi.dsi.fastutil.longs.LongOpenHashSet.clone()

I've found a condition where a NoSuchMethodError can be thrown.  Below is what I do to get it to trigger (I hope you don't mind that it's in scala).  I am using hll version 1.6.0 out of maven.
val h1 = new HLL(13, 5)
val h2 = new HLL(13, 5)
h2.addRaw(2)
h1.union(h2) // <-- exception here

results in:
Exception in thread "main" java.lang.NoSuchMethodError: it.unimi.dsi.fastutil.longs.LongOpenHashSet.clone()Lit/unimi/dsi/fastutil/longs/LongOpenHashSet;
	at net.agkn.hll.HLL.heterogenousUnion(HLL.java:679)
	at net.agkn.hll.HLL.union(HLL.java:639)

Is anyone else running into this issue?

I attempted to reproduce this problem via a patch to SparseHLLTest.java (not really sure if this is the optimal test class, but i noticed some existing EMPTY union tests there) and was unable to reproduce the described bug.
I suspect the initial bug report was due to a classpath issue (ie: multiple versions of the same depedent jar containing it.unimi.dsi.fastutil.longs.LongOpenHashSet)
https://gist.github.com/hossman/eda007700e0f6183654e


Use JSON array instead of Postgres ARRAY

Using the ARRAY type in the database requires using Postgres. Switching this type to JSON (and always putting an array there) would allow using also MySQL and SQLite. SQLite especially would be nice for a better standalone program experience.

Thanks for your suggestion @jawahar273 . I ended up going with the JSONType from the SQLAlchemy-Utils package https://sqlalchemy-utils.readthedocs.io/en/latest/data_types.html which I presume is based on a similar idea.


fast_hist

Hi, I don't quite understand the function fast_hist(), could help explain it? Especially "n * label[k].astype(int) + pred[k]"

Sorry for the late reply;
For the metric, you can refer to this URL


missing helm chart for application version 3.4.0

I can't say that I understand the version schema in use by this repository, but there is a release for 3.3.5-3.4.0 so I expected to find corresponding helm charts for 3.3.5 and 3.4.0. The latest published helm chart release appears to be for 3.3.1.
$ helm repo list
NAME             	URL
aws-eks          	https://aws.github.io/eks-charts
gpu-helm-charts  	https://nvidia.github.io/dcgm-exporter/helm-charts
k8s-device-plugin	https://nvidia.github.io/k8s-device-plugin
$ helm search repo gpu-helm-charts -l
NAME                         	CHART VERSION	APP VERSION	DESCRIPTION
gpu-helm-charts/dcgm-exporter	3.3.1        	3.3.1      	A Helm chart for DCGM exporter
gpu-helm-charts/dcgm-exporter	3.3.0        	3.3.0      	A Helm chart for DCGM exporter
gpu-helm-charts/dcgm-exporter	3.2.0        	3.2.0      	A Helm chart for DCGM exporter
gpu-helm-charts/dcgm-exporter	3.1.7        	3.1.7      	A Helm chart for DCGM exporter
gpu-helm-charts/dcgm-exporter	3.1.5        	3.1.5      	A Helm chart for DCGM exporter
gpu-helm-charts/dcgm-exporter	3.1.4        	3.1.4      	A Helm chart for DCGM exporter

The helm charts have just been updated for 3.4.0.

Confirmed, thank you!
 $ helm repo update gpu-helm-charts
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "gpu-helm-charts" chart repository
Update Complete. ⎈Happy Helming!⎈
$ helm search repo gpu-helm-charts -l
NAME                         	CHART VERSION	APP VERSION	DESCRIPTION
gpu-helm-charts/dcgm-exporter	3.4.0        	3.4.0      	A Helm chart for DCGM exporter
gpu-helm-charts/dcgm-exporter	3.3.1        	3.3.1      	A Helm chart for DCGM exporter


The Imgui widget show in Scene!

The Imgui widget show in Scene!
The scene object Occlude by it.
can i remove it from scene view?

Do you have a screenshot?


Eliminate 3rd party tools from code coverage report

The code coverage report currently covers all of the 3rd party tools that we use which adds noise visually to the reports that we have to sift out.  The code coverage report should focus on our code only. Eliminating the boost and wasm related directories alone would get us much of the way to our goal.  The directories that are important for us are libraries/chain and libraries/chainbase.  Once we have nodes fully running on slim we will pick up appbase, etc as well.

This is complete as can be seen in the latest code coverage report.


Select dropdown is positioned incorrectly when scrolling

🐛 Bug Report
On web, when the page is scrolled to the top, the Dropdown component works as expected. However, when the dropdown is opened while the page is scrolled down a bit, the items appear in the wrong place; they're positioned too high on the page. There's also a similar bug with the Tooltip component.
To Reproduce
See example here: https://snack.expo.io/rrdVu5obV
When you click the dropdown while scrolled to the top, it works properly. However, if you scroll down a little and then click it, the items will appear way above where they're supposed to.
Expected behavior
Dropdown items should appear just below the main UI element.
Link to runnable example or repository (highly encouraged)
https://snack.expo.io/rrdVu5obV

UI Kitten and Eva version

Package
Version

@eva-design/eva
2.0.0-alpha.1

@ui-kitten/components
5.0.0-alpha.1

Environment information

 System:
    OS: macOS 10.15.3
    CPU: (8) x64 Intel(R) Core(TM) i5-8257U CPU @ 1.40GHz
  Binaries:
    Node: 12.13.0 - /usr/local/bin/node
    Yarn: 1.22.4 - ~/.yarn/bin/yarn
    npm: 6.12.0 - /usr/local/bin/npm
  SDKs:
    iOS SDK:
      Platforms: iOS 13.4, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
  IDEs:
    Android Studio: 3.6 AI-192.7<IP_ADDRESS>92135
    Xcode: 11.4.1/11E503a - /usr/bin/xcodebuild
  npmPackages:
    react: ~16.9.0 => 16.9.0
    react-native: https://github.com/expo/react-native/archive/sdk-37.0.1.tar.gz => 0.61.4

@colinhostetter works as expected on mobile. And worked same way on previous RNW versions. Could it be RNW issue?

Hey @artyorsh thanks for replying! I'm not sure if it's a RNW thing -- when I switch to the previous version of Expo in the link I gave, it is still broken. (Not sure if that would switch it to a previous RN version or not.)
Any idea whether someone will be able to look into this? Unfortunately it does make the Dropdown and Tooltip components unusable for projects that are using web.

@colinhostetter
We have a demo app running RNW. Please see Select component examples in the Components tab. It runs Expo SDK 36 + RNW 0.11.7, so I can definitely say this is an issue on the other side (or the change that we could miss)

@artyorsh I'm also using RNW 0.11.7, which makes me think it's not an RNW issue. Maybe something differing in our setups?

After noticing that your example is within a ScrollView or some other kind of scrollable container, I tried moving mine into one, and it seems to work there: https://snack.expo.io/tkV3YMQ2x
So this appears to be a ui-kitten bug when this component is rendered outside of a ScrollView.

@colinhostetter in your example still look good when I remove ScrollView tag :)

@colinhostetter any purpose of using flex: 1 there?

Ok, I guess it's not specific to ScrollView, but it's rather that the bug happens when the actual document itself is scrolled (as in my original example) rather than scrolling within an element (as in your example and my second example).

I guess the flex: 1 is not necessary, no

@colinhostetter we focus mobile-first, where is no option to scroll without putting contents somewhere else besides ScrollView. Could you please describe your use-case (without having a ScrollView) in more details?

Yep, makes sense. I'm actually pretty new to mobile development and was prototyping this stuff on web and hadn't built out how things like scrolling should work in my app on mobile, and there was no obvious reason to think that that had anything to do with this problem. It seems like just using ScrollViews should resolve the problem, although it is very confusing, so it might be worth fixing for future newcomers like me.

I have the same problem on android

I have the same problem on android

<EMAIL_ADDRESS>

<EMAIL_ADDRESS>popover: {                     maxHeight: popoverMaxHeight,                     borderRadius: popoverBorderRadius,                     borderWidth: popoverBorderWidth,                     borderColor: popoverBorderColor,                     marginTop: react_native_1.StatusBar.currentHeight                 }  Can be solved

@1ET #743

I just found this bug while developing an application for both mobile and web, and it's quite annoying. On web, scrolling the document body instead of a ScrollView is a really good practice, as is what most browsers will expect and behave accordingly, especially mobile browsers like Safari on iOS, which will hide the URL bar and the bottom action buttons to give more space to the user when scrolling down the page, and show them again when scrolling up. If we build our web applications using a ScrollView instead of letting the document body scroll, the browser won't be able to detect scroll interactions, resulting in a weird user experience. Other weird bugs will happen as well, like accidental scrolling of the document instead of the inner ScrollView which will make the user think the page cannot be scrolled further, when in reality it can.
Although UI Kitten is mobile first, it's the UI kit for RN with the best web support out there, so it pains me to see document body scrolling not supported. Is there any chance this could be worked on, or could I be pointed in the right direction if I have the time to contribute with a fix myself?

@artyorsh could you comment on this? Thanks


[FR] Allow for on-the-fly eval of code blocks + relative paths improvements

See https://github.com/tlienart/JuDoc.jl/issues/147
With respect to scripts, I think a simple solution to keep things organised would be to allow
code (executed):
```julia:phys/script1
println(exp(1im*pi))
```
input:
\input{output}{phys/script1}

code (non-executed):
```julia
println("hello")
```

The second one would amount to the "no-eval" option you're mentioning and doesn't create a file. The first one would indicate a relative path in assets/scripts so that things stay well organised within the assets folder:
.
├── infra
│   ├── favicon.png
│   └── ...
└── scripts
    ├── output
    │   ├── phys
    │       └── script1.txt
    ├── phys
        └── script1.jl

I'm more in favour of all this happening in the assets/ folder but I guess an extra syntax like
code (executed):
```julia:./code/script1
println(exp(1im*pi))
```
input:
\input{output}{./code/script1}

could indicate that script1 is contained in a local subfolder (which seems to be what you want) i.e. the structure would be
src
└── pages
    └── phys
        ├── page1.md
        ├── code
        │  └── script1.jl
        └── output              # generated
            └── script1.txt

First, thanks for clarifying the copy mechanism when putting assets into webpage/src/pages instead of webpage/assets/ it is now clear that it is much more sensible to put images, pdfs, etc. into webpage/assets/.
Now that I thought about reorganizing my webpage for a bit I came up with the following solution influenced by my own experiences.
Usually single webpages do not have that many images, code or maybe PDFs attached to them. When the webpage gets too long one tends to split logical parts into separate webpages. Let me show this with my specific example:
src/
├── index.md
├── config.md
├── _css/
│   └── ..
├── _html_parts/
│   └── ..
└── pages/
    ├── julia.md
    ├── judoc.md
    ├── physics.md
    ├── rpg.md
    ├── julia/
    │   └── tips_tricks.md
    ├── physics/
    │   ├── math/
    │   │   └── statistics.md
    │   ├── tests/
    │   │   ├── hubbard_model.md
    │   │   └── interacting_dot.md
    │   └── theory/
    │       ├── cdw.md
    │       ├── hartree_fock.md
    │       └── tdhf.md
    └── rpg/
        └── broken_hope.md

To keep the logic in the webpage/assets/ folder I would propose a structure that reflects everything happening below src/ i.e. compared to the above folder structure the structure in webpage/assets/ would look like this:
assets/
├── index/
│   └── .. (All images, pdfs, scripts in index.md)
└── pages/
    ├── assets/
    │   ├── judoc/
    │   │   └── .. (.. in judoc.md)
    │   ├── julia/
    │   │   └── .. (.. in julia.md)
    │   ├── physics/
    │   │   └── .. (.. in physics.md)
    │   └── rpg/
    │       └── .. (.. in rpg.md  )
    ├── julia/
    │   └── assets/
    │       └── tips_tricks/
    │           └── .. (.. in tips_tricks.md)
    ├── physics/
    │   ├── assets/
    │   │   └── (empty)
    │   ├── math/
    │   │   └── assets/
    │   │       └── statistics/
    │   │           └── .. (.. in statistics.md)
    │   ├── tests/
    │   │   └── assets/
    │   │       ├── hubbard_model/
    │   │       │   └── .. (.. in hubbard_model.md)
    │   │       └── interacting_dot/
    │   │           └── .. (.. in interacting_dot.md)
    │   └── theory/
    │       └── assets/
    │           ├── cdw/
    │           │   └── .. (.. in cdw.md)
    │           ├── hartree_fock/
    │           │   └── .. (.. in hatree_fock.md)
    │           └── tdhf/
    │               └── .. (.. in tdhf.md)
    └── rpg/
        └── assets/
                └── broken_hope/
                    └── .. (.. in broken_hope.md)

So basically every markdown page in the src/ folder gets its own subfolder in the assets/ folder and with this one can reconstruct the layout of the src/ folder.
Now I believe that having this per page ordering negates the need for specific scripts/ img/ etc. folders in assets and also follows the logic of the src/ tree. So now one can just dump everything related to the markdown page into the specific folder and if needed can still create a substructure inside the per page folder (if one needs to further split between scripts, images etc.).
The only problem I see with this approach is that the links to files inside the markdown document could become quite long. This could be circumvented if every link in the markdown document (to scripts, images etc.) would point to its respective subfolder.
E.g. if i write ![Charge density wave](peierls.png) in cdw.md it automagically resolves to webpage/assets/physics/theory/assets/cdw/peierls.png.
The same approach could be applied to scripts.
I hope this post was not too long, I wanted to make sure to cover weird corner cases with subfolders.

Ok thanks for the insight, what you're suggesting makes sense but I'll need to think a bit about how to do this best. Ideally I'd like to not impose a folder structure too much onto people as some people (e.g. you, possibly me) like a lot of logic in their folders and others might not want to bother.
One thing as well is that two pages may call the same assets and this should be easy to do.
Maybe one approach could be to keep things as they are but offer a slightly different syntax for "relative paths" that would correspond precisely to what you suggest so you could have something like:
![Charge density wave](/assets/physics/theory/cdw/peierls.png)  <!-- the current way -->

![Charge density wave](./peierls.png)

in the second case, there would be the assumption that you have assets/[subpath]/peierls.png where subpath would match the subpath in pages/[subpath]/cdw.md.
So to make things explicit:
.
├── assets
│   └── physics
│       ├── maths
│       └── theory
│           └── peierls.png
└── src
    ├── _css
    ├── _html_parts
    └── pages
        ├── index.md
        └── physics
            ├── maths
            └── theory
                └── cdw.md

If you wanted to further nest things in assets so that they're in their own cdw folder, you would write ![Charge density wave](./cdw/peierls.png) with this tree:
.
├── assets
│   └── physics
│       ├── maths
│       └── theory
│           └── cdw
│               └── peierls.png
└── src
    ├── _css
    ├── _html_parts
    └── pages
        ├── index.md
        └── physics
            ├── maths
            └── theory
                └── cdw.md

What do you think?

I think the "dot" syntax i.e. ![Charge density wave](./cdw/peierls.png) is an excellent solution that would keep the freedom of structuring the assets/ folder and still offer the convenience of using the "logical" approach.
However, there is one small problem. I believe that one has to create sub assets/ folders to avoid name clashes between markdown page names and subfolder names in the src/ tree.
E.g. in the folder tree I have posted above I have a pages/physics.md webpage and a subfolder called pages/physics/ where physics.md is basically the "sub landing page" for that particular folder.
That is why, for every subfolder below src/, I create an additional assets/ folder in webpage/assets/ where I then create folders for every markdown page.
E. g. for the physics problem I have its markdown page data in webpage/assets/page/assets/physics/ whereas the subfolder src/pages/physics/ is related to webpage/assets/page/physics/ .

E.g. in the folder tree I have posted above I have a pages/physics.md webpage and a subfolder called pages/physics/ where physics.md is basically the "sub landing page" for that particular folder.

Ok so if I understand your context properly, you could have:
.
├── assets
│   ├── im_index_1.png
│   └── pages
│       ├── im_phys_1.png
│       └── phys
│           └── math
│               └── im_noether_1.png
└── src
    └── pages
        ├── phys
        │   └── math
        │       └── noether.md
        ├── phys.md
        └── rpg

And with the dot syntax you'd do:
In `index.md`
![](./im_index_1.png)
![](./pages/im_phys_1.png)

In `phys.md`
![](./im_phys_1.png)
![](./phys/math/im_noether_1.png)

In `noether.md`
![](./im_noether_1.png)

If you wanted something "higher up" you'd have to write the full path
(we could allow `..` but I doubt it would be clear)

![](/assets/pages/im_phys_1.png)

And if you want even more structure in assets, well you can always add subfolders; the dot syntax would just amount to mimicking the path to the original .md file and you could add whatever path you wanted after that. So for instance you could alternatively use
.
├── assets
│   ├── im_index_1.png
│   └── pages
│       └── phys
│           ├── im_phys_1.png
│           └── math
│               └── noether
│                   └── im_noether_1.png

and then you'd do
In `phys.md`
![](./phys/im_phys_1.png)

In `noether.md`
![](./noether/im_noether_1.png)

I think both approaches are reasonable as long as one stays consistent with one or the other? what do you think? I'll try to work on this soonish

Thanks for the side note, I did not think of using LaTeX to partly solve this problem, I will certainly use it. :)

The idea for allowing the definition of LaTeX-like was precisely to allow people to basically write whatever shortcuts they would see helpful towards writing their website focusing on the content :-)

So before I go on, thanks again for the fast replies and active development of the package. I think this is getting better everyday :).
To come to your answer: It is not quite what I had in mind but I think we could discuss the pro and contras of the approach you offered and mine.
So let me start with the problem I see with your approach and let me take your folder tree as an example and add a second page into pages and remove the empty rpg folder:
├── assets
│   ├── im_index_1.png
│   └── pages
│       ├── im_phys_1.png
│       ├── im_julia_1.png
│       └── phys
│           └── math
│               └── im_noether_1.png
└── src
    ├── index.md
    └── pages
        ├── phys
        │   └── math
        │       └── noether.md
        ├── phys.md
        └── julia.md

The only problem I have with doing this directly is that page content and the subfolders mimicking the structure in src/ get mixed up. The proposal I made created one more folder for all the content:
├── assets
│   ├── im_index_1.png
│   └── pages
│       ├── content
│       │   ├── im_phys_1.png
│       │   └── im_julia_1.png
│       └── phys
│           └── math
│               └── content
│                      └── im_noether_1.png
└── src
    ├── index.md
    └── pages
        ├── phys
        │   └── math
        │       └── noether.md
        ├── phys.md
        └── julia.md

So if you e.g. write ![](./im_phys_1.png) in phys.md it points to /assets/pages/phys/content/im_phys_1.png instead of /assets/pages/phys/im_phys_1.png.
In the end this boils down to a more or less stylistic choice on the order in the /assets/ folder.
With your syntax I could still write ![](./content/im_phys_1.png) which would not make the relative path to type much longer but, as mentionend, content and subfolders would get mixed by default.
I think you need to decide what suits your package best. :)

We're on the same page it seems (and thanks too for the back and forth, it's very helpful).
Right so we have two possible approaches: first is that the dot syntax called from a page [subpath]/page.md would map to
/assets/[subpath]/

second is that it maps to
/assets/[subpath]/page_assets/

where the added _assets would avoid the name clash you raised earlier.
I think I'm leaning towards the first one just because it seems (to me) that suggesting identical structure for the source folder and the assets folder is appealing.
One way to have our cake and eat it: I understand what you're saying with "get mixed as a default", but users who do not want this to happen could do one thing that's not far from the reverse of what you were suggesting but that, I think, is more consistent: just put noether.md in its own folder.
├── assets
│   ├── im_index_1.png
│   └── pages
│       ├── im_phys_1.png
│       ├── im_julia_1.png
│       └── phys
│           └── math
│                └── noether
│                   └── im_noether_1.png
└── src
    ├── index.md
    └── pages
        ├── phys
        │   └── math
        │       └── noether
        |            └── noether.md
        ├── phys.md
        └── julia.md

what do you think?
PS: I've started work on the eval of code blocks, will probably split this into another issue or whatever but there will be news soon.

Since the drawbacks of your approach are very, very minor and your approach offers more flexibility I would also lean towards your suggestion to map [subpath]/page.md to /assets/[subpath]/. From this point onward the user, depending on his demands, can order files in [subpath]as they wish and create subfolders. As you said, the landing page issue can also be solved by the user; adding an additional subfolder in/assets/[subpath]`.
I am really looking forward to the evaluation feature, this will also draw interest by all the Julia Bloggers that somehow try to integrate Weave.jl with Jekyll, Hugo etc. .
I am especially referring to this thread:
Blogging with Julia code blocks

I'm excited to announce that this is now available on branch #eval. It's probably a bit rough around the edge still so feedback would be super welcome.
I'll merge after a bit more testing, fixing any comments, fixing the JuDocTemplates to use the new syntax and add an entry in the doc
Here is a small example that can be tested on that branch:
@def title = "Title"
@def hascode = true

# Eval'ing code blocks

We can write a code block like so (note the naming)

```julia:./code/ex1
f(x) = x^5
print(f(7))

This will be executed on the fly unless it's already been executed (and the content hasn't changed) and an output file exists. We can show the output like so:
\input{output}{./code/ex1}
I've also added a shortcut for plain output (syntactic sugar for the above command):
\output{./code/ex1}

![Screen Shot 2019-05-28 at 6 58 35 pm](https://user-images.githubusercontent.com/10897531/58465305-bd187280-817a-11e9-83eb-4c85fb7cc5fc.png)

You can change for instance the `7` into a `4` and see it being live-updated. Here since the code is very simple this is all very fast.

In terms of folders, the page was `src/pages/pg1.md` and this generates

.
├── assets
│   ├── pages
│   │   └── code
│   │       ├── ex1.jl
│   │       └── output
│   │           └── ex1.out

note the matching hierarchy with the added `/code/` that was specified in the markdown.

this is now implemented #156 and documented.


Marker Files are Different from those provided with Orbiter 2016

I have created a waypoint autopilot in Lua that refers to the marker files (*.mkr) found in Config/Earth/Markers. I discovered that the multiple marker files provided in Orbiter 2016 (listed below) are not found in OpenOrbiter (as of build 240105):
Antarctic Stations.mkr
Cities.mkr
Islands.mkr
Impact Features.mkr
Miscellaneous.mkr
Mountains and Volcanos.mkr
Tracking Stations.mkr
In OpenOrbiter 240105 there is only one marker file, and it does not match the name of any of the 2016 marker files:
City.mkr (note Orbiter 2016 has Cities.mkr)
This may not be a bug per se, but I wanted to inquire what was the necessity to altering these files? These marker files resources are the only way to my knowledge to access these station locations within Lua. It will either require Orbiter version checking in the Lua script (not currently available, see Issue #415) or checking of file names and the number of files within the directory (potentially possible but not simple to do in Lua).

Generic file i/o should be possible in Lua (at least for OpenOrbiter):
Input and Output Facilities
Operating System Facilities
Whether that's enough is a different question 😉

I am aware of Lua file i/o capabilities. The challenge is identifying what files are in a given directory from within Lua. That currently cannot be done in pure Lua without external libraries.
More fundamentally, I'd like to know why this marker file is different from the one provided in Orbiter 2016, and why the other marker files were not included. To my knowledge, these marker files are only utilized to identify bases in the Map MFD function. Did something change in OpenOrbiter with regard to their use?

As far as I can remember (long time ago) the Markers have been incorporated into the binary, packed, "Archive" structure in the Textures Folder (for example .\Textures\Earth\Archive\Label.tree)
That "new" format should be explained in a technical documentation somewhere.
This has to do with performance considerations as reading those Text-files is not the fastest way to do.
And just before you ask... I will not provide a Lua interface for that 😉


neon/st1{,q}_*_x{2,3,4}: initial implementation

This PR implements st1{,q}_*_x{2,3,4}. It includes tests, whose values were generated on a Raspberry Pi 4 (Cortex-A72 core).

@dgazzoni I think there is an include missing?
https://github.com/simd-everywhere/simde/actions/runs/6348516960/job/17245284887#step:9:1068

@dgazzoni I think there is an include missing?
https://github.com/simd-everywhere/simde/actions/runs/6348516960/job/17245284887#step:9:1072

Looks like you figured it out later, these functions are AArch64-only.

@dgazzoni I think there is an include missing?
https://github.com/simd-everywhere/simde/actions/runs/6348516960/job/17245284887#step:9:1072

Looks like you figured it out later, these functions are AArch64-only.

vst1_f32_x2, vst1_s8_x2, vst1_s16_x2, vst1_s32_x2, vst1_s64_x2 (etc.) don't seem to be aarch64-only as per https://documentation-service.arm.com/static/5f7b5205bcda971b14568107?token=
https://github.com/simd-everywhere/simde/actions/runs/6350853438/job/17251163558?pr=922#step:9:1076

@yyctw Since your PR overlaps with this earlier one, can you help me finish this one first? Maybe you can suggest fixes from your PR for the few compiler errors we saw here

@yyctw Since your PR overlaps with this earlier one, can you help me finish this one first? Maybe you can suggest fixes from your PR for the few compiler errors we saw here

Yes, I can help finish this PR first.

Merged as https://github.com/simd-everywhere/simde/pull/1082 ; thank you @dgazzoni and @yyctw !


Login via social login button in screenset doesn't close screenset after login

Hi,
I am running into the issue where:

a regular login (using e-mail & password) via the login form, performed inside a web screenset, correctly closes the screenset after successful login
a social login via one of the social login buttons, performed inside a web screenset, does't close the screenset

The user is left staring at the login screen, although, aftermanually dismissing the screenset, the SDK correctly indicates that the user is logged in.
Am I, as the developer, supposed the close this screenset manually. If so, how is this supposed to be done, I can't seem to find any documentation?
Or is this due to lack of some events/actions being sent out in the screenset?
It's my impression that upon clicking the social login button, the social login flow (as if you would call await Gigya.socialLogin('apple') directly for instance) is executed, but the result is never communicated back to the screenset flow?

Anyone? I would expect the web flow to continue with any next steps (e.g. profile completeness, ...) after the social login flow was exected.


rename writer.py to translator.py

The practice in sphinx/docutils seems to have a single file for both the writer and the translator, and this file lives within the writers/ directory. So we don't need to rename this.


Have a many conflicts in js file

// Set up namespace to which we'll bind functions
<<<<<<< HEAD
<<<<<<< HEAD

joebain-master
window.Humanize = {}

/*!


Which version to use for iphone 13 pro iOS 15.1?

I am jailbroken with fugumax iOS 15.1, which rootless package should I use?

There is only one rootless package on each release.


Modify Error.Error() to add Detail field from HTTP response

If present, 'detail' in the JSON response contains what may be
critical information for the user to resolve the problem.
See https://github.com/containers/image/issues/1234 for the
details in the context of podman.
Signed-off-by: Dan Mick<EMAIL_ADDRESS>

Codecov Report

Merging #3447 (1c1be4f) into main (ad8f5ca) will increase coverage by 0.00%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #3447   +/-   ##
=======================================
  Coverage   56.38%   56.39%
=======================================
  Files         102      102
  Lines        7324     7329    +5
=======================================
+ Hits         4130     4133    +3
- Misses       2541     2542    +1
- Partials      653      654    +1

Impacted Files
Coverage Δ

...bution/distribution/registry/api/errcode/errors.go
64.36% <0.00%> (-0.27%)
:arrow_down:

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 ad8f5ca...1c1be4f. Read the comment docs.


Updated use of Postgres/S3 credentials from Secrets.

test-infra is PASSING:
http://<IP_ADDRESS>:8080/job/test-infra/2252/console


Update README.md to use charsets instead of use_symbols

I've opened https://github.com/secrethub/terraform-provider-secrethub/pull/84 to merge the docs to develop.


Add missing property redirected to VisitResponse

Turbo-iOS PR: https://github.com/hotwired/turbo-ios/pull/225

When a redirection with a responseHTML would happen (e.g. a form submission), Turbo Native receives something like the following:
← visitProposed [
    "location": http://localhost:45678/submit_redirected,
    "timestamp":<PHONE_NUMBER>593,
    "options": {
        action = replace;
        response =     {
            redirected = 1;
            responseHTML = "{HTML with flash notice}";
            statusCode = 200;
        };
        shouldCacheSnapshot = 0;
    }
]

This usually gets turned into a JavaScript visit and then handed over to the bridge, which begins the visit by calling visitLocationWithOptionsAndRestorationIdentifier.
However, when transforming this proposal JS -> Swift (for processing) and back to JS (for bridge consumption), visitProposed["options"]["response"]["redirected"] was being lost. This caused responseHTML to be ignored and a replace visit to be proposed instead.
By adding redirected to VisitResponse the behavior is now correct.

Closing this in favor of: https://github.com/hotwired/hotwire-native-ios/pull/60


[CodeCompletion] Inherit options when parsing new buffer

for fast completions. Options may affect the parsing result.
Also, don't collect interface hash tokens inside inactive blocks.

@swift-ci Please smoke test

For canImport, would it be possible to take the canImport result from the original AST (just assume it's the same)?

An idea is setting up a proxy module loader which delegates 'canImportModule()' to original AST
context.

@swift-ci Please test

Build failed
Swift Test OS X Platform
Git Sha - ec0c9484abbe6a561011f3bce8f16a270e09df88

Build failed
Swift Test Linux Platform
Git Sha - ec0c9484abbe6a561011f3bce8f16a270e09df88

@swift-ci Please test


Rule to disable usage of any class from specified package.... Example disable java.time.* in order to use kotlinx.datetime instead.

Expected Rule behavior
Many times because the inherited nature of kotlin from JDK there are some java and kotlin packages that are using same class naming.
These namings creates confusion in the project which types developer should use... Company would want to enforce the use of only
packages that team leaders agree upon and pass this decision down the hierarchy.
Rule should be able to prevent developer to use any class from the specified package, for example java.time.*

Thanks for your idea.
I don't think this fits the use case for the rules provided by Ktlint. Prohibiting unwanted imports has nothing to do with the way the code in a file is formatted. It is about forbidding the usage of certain imports. Next to that the list of unwanted imports varies per situation (e.g. project, company, or something else). It would mean that the list of unwanted imports would need to be configured somewhere outside of Ktlint code.
It will however not be that difficult to develop a custom rule (in a custom ruleset) and apply that ruleset within your company. Additional benefit is that the list of unwanted imports can be coded inside the rule. Of course all projects in your company would need to use this ruleset. Please see https://pinterest.github.io/ktlint/latest/api/custom-rule-set/ for some references to create a custom rule (set).

Thank you for your feedback, it's much appreciated! I agree with your view.


made file paths absolute

Short Description:
This fix will enable users to  call script anywhere from their home directory. Also this change will let you to run this script as a daemon on linux machine.  ! You will probably get an IOError on linux, therefore you need to change project folder permissions

chmod -R 777 project_folder

Fixes:

Made file paths absolute and relative to  the project folder at pokemon_bot/init.py file
Made file paths absolute relative to pokecli.py

I believe we made these changes as part of another PR. Thanks for contributing!


Add miniature golf preset

Not sure why it's also submitting my previous edit in this pull request - no idea how to get rid of it.

Not sure why it's also submitting my previous edit in this pull request - no idea how to get rid of it.

That's because your master branch is behind the main master branch.. When you make a branch, the "where it branched off from" pointer never changes unless you rebase the branch.
Github is just trying to collect all the things in your master branch that have changed since that branch was created.  So a good workflow to avoid this is:
Set your remotes up like this
git remote set origin git@github.com:boothym/iD.git           # probably already there
git remote add upstream git@github.com:openstreetmap/iD.git

Then, sometimes you'll want to keep your master in sync with ours (to avoid the problem you're seeing):
git checkout master                # make sure you are on the master branch to start
git fetch --all                    # so git knows what is new
git reset --hard upstream/master   # makes your master exactly like upstream master

Then when you want to work on something:
git checkout -b <work-branch>      # start a new branch just for the work you're doing
... do work...
git push origin                    # pushes work-branch to your github
... go to github and open pull request from work-branch back to upstream/master...

Some more info here:  http://stackoverflow.com/questions/16329776/how-to-keep-a-git-branch-in-sync-with-master

Anyway, everything else about your PR was totally great except for the missing commas, so I just merged it as:
ad11770 2016-07-27 Create miniature_golf.json
5de925b 2016-07-27 Fix commas, run make
Let me know if you have any other questions, happy to help people work with git..

Whoops, thanks for fixing the commas! I don't actually have git installed (yet) so I've just used the website to make the edits. Currently trying to find out how to keep the fork in sync via the web UI.


Add component enhanced print

Description

Related Issues

Checklist

[ ] Is this code covered by new or existing unit tests or integration tests?
[ ] Did you run make unit_testing and make integration-testing successfully?
[ ] Do new classes, functions, methods and parameters all have docstrings?
[ ] Were existing docstrings updated, if necessary?
[ ] Was external documentation updated, if necessary?

Additional Notes or Comments

I added this to #2140 so closing.


Move cert/perform/q/sasl below the network info.

I don't like seeing the cert/perform/q/sasl modules clogging up the left/right (depending on the theme) side of webadmin when they are loaded as a network module. I think they should be shown under the Network Info for the specific network they are loaded in. I have created an extremely crude picture in MS Paint as an example of what I would think would be better than having them on the left/right side when loaded as network modules.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/26972437-move-cert-perform-q-sasl-below-the-network-info?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github).

I honestly like it in the sidebar, it gives me a way to quickly find it and doesn't make the existing page super long either.
Perhaps a compromise is to make a modules page for all module configuration options?

blockuser, lastseen, stickychan already add some info to user and channel pages.
But what happens if webadmin is not loaded?

How about a drop down menu of some sort?  When collapsed, it would only add a little bit of length to the network settings page.  When expanded, it could look similarly to the example picture.
As far as when WebAdmin isn't loaded... then what would it matter?
Ben (MrC @ Freenode)


Initial Commit

This is an initial version of the PR handler. I did a simple round of testing with a fakePayload, but it definitely requires more end to end testing. I'll work on that later.

@erwinmombay Friendly Ping : )

@zhouyx woops. i missed the notification on this. LGTM!


Fixed calculation in SQL query if there are no refunds

Questions
Answers

Description?
Fixed calculation in SQL query if there are no refunds

Type?
bug fix

BC breaks?
no

Deprecations?
no

Fixed ticket?
Relative to #22 (Detected by @florine2623)

How to test?
Please indicate how to best verify that this PR is correct.

Hello @Progi1984 ,
I'm having an issue in the total Sales in Sales and Orders stats page.
In this example I should have €42.60 instead of €39.80

Could you check please ?
Thanks!

I check it in the next week ;)

@florine2623 It's logical as the calculation is based on total paid real (so that counts on payments)

Hello @Progi1984 ,
I'm not sure I understand your answer.
There's always a 2.80€ difference between the displayed total Sales and the amount in the table : NOK
Here are a few examples :

Also, there is a lot a number after the comma, the amount is not completely visible.

@Progi1984 Sorry. I don't understand how this PR went off the radar for so long.

Thanks @Progi1984 @florine2623


M1 unit-tests fail on main branch

🐛 Describe the bug
The M1 unit-tests are failing on latest main branch. It looks like dependency issues:
Original error was: dlopen(/Users/ec2-user/runner/_work/vision/vision/conda-env-3226180661/lib/python3.8/site-packages/numpy/core/_multiarray_umath.cpython-38-darwin.so, 0x0002): Library not loaded: @rpath/libquadmath.0.dylib
  Referenced from: /Users/ec2-user/runner/_work/vision/vision/conda-env-3226180661/lib/libgfortran.5.dylib
  Reason: tried: '/Users/ec2-user/runner/_work/vision/vision/conda-env-3226180661/lib/libquadmath.0.dylib' (no such file), '/Users/ec2-user/runner/_work/vision/vision/conda-env-3226180661/lib/libquadmath.0.dylib' (no such file), '/private/var/folders/nz/j6p8yfhx1mv_0grj5xl4650h0000gp/T/abs_ac4kid1385/croot/gfortran_impl_osx-arm64_1665476549639/work/build_conda/gcc/libquadmath.0.dylib' (no such file), '/Users/ec2-user/runner/_work/vision/vision/conda-env-3226180661/lib/libquadmath.0.dylib' (no such file), '/Users/ec2-user/runner/_work/vision/vision/conda-env-3226180661/lib/libquadmath.0.dylib' (no such file), '/Users/ec2-user/runner/_work/vision/vision/conda-env-3226180661/lib/libquadmath.0.dylib' (no such file), '/Users/ec2-user/runner/_work/vision/vision/conda-env-3226180661/lib/python3.8/site-packages/numpy/core/../../../../libquadmath.0.dylib' (no such file), '/Users/ec2-user/runner/_work/vision/vision/conda-env-3226180661/lib/libquadmath.0.dylib' (no such file), '/Users/ec2-user/runner/_work/vision/vision/conda-env-3226180661/lib/libquadmath.0.dylib' (no such file), '/Users/ec2-user/runner/_work/vision/vision/conda-env-3226180661/lib/python3.8/site-packages/numpy/core/../../../../libquadmath.0.dylib' (no such file), '/Users/ec2-user/runner/_work/vision/vision/conda-env-3226180661/lib/libquadmath.0.dylib' (no such file), '/Users/ec2-user/runner/_work/vision/vision/conda-env-3226180661/bin/../lib/libquadmath.0.dylib' (no such file), '/Users/ec2-user/runner/_work/vision/vision/conda-env-3226180661/lib/libquadmath.0.dylib' (no such file), '/Users/ec2-user/runner/_work/vision/vision/conda-env-3226180661/bin/../lib/libquadmath.0.dylib' (no such file), '/usr/local/lib/libquadmath.0.dylib' (no such file), '/usr/lib/libquadmath.0.dylib' (no such file)

Versions
Latest main branch
cc @seemethere

Fixed by @atalman by rerunning the nightly for M1. Closing.


transforms: add Random Erasing an image

Random Erasing randomly selects a rectangle region in an image and erases its pixels with random values. It can reduce the risk of overfitting, and improves CNN baselines in image classification, object detection and person reidentification.
'Random Erasing Data Augmentation' by Zhong et.al.
https://arxiv.org/pdf/1708.04896.pdf

I'm not a maintainer but I think that it would be nice if you adapt the transform to follow the functional API (https://github.com/pytorch/vision/blob/master/torchvision/transforms/functional.py) for consistence with the rest of transforms. It should be trivial to move the code where the transformation actually happens to an independent function (i.e F.erase())

@daavoo Thanks for your advice, I have modified it.

@alykhantejani Thanks for your review, I have updated it following your advice.

Hi, I found that this random erasing is now widely used in image classification (CIFAR-10 and CIFAR-100) and person re-identification. Could you consider adding it to "transforms"? @fmassa

Codecov Report

Merging #335 into master will decrease coverage by 0.5%.
The diff coverage is 17.64%.

@@            Coverage Diff             @@
##           master     #335      +/-   ##
==========================================
- Coverage    57.9%   57.39%   -0.51%
==========================================
  Files          46       46
  Lines        3696     3730      +34
  Branches      561      566       +5
==========================================
+ Hits         2140     2141       +1
- Misses       1429     1460      +31
- Partials      127      129       +2

Impacted Files
Coverage Δ

torchvision/transforms/transforms.py
77.57% <16.12%> (-4.33%)
:arrow_down:

torchvision/transforms/functional.py
69.57% <33.33%> (-1.55%)
:arrow_down:

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 9077164...ed3ff00. Read the comment docs.

New pull request at #909


@conda-forge-admin,please add bot automerge

As per title.

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added bot automerge in conda-forge/whos-there-feedstock#5.


GitHub Actions automatically upload build to internal testing

I modified deploy script (Android Release Bundle Deploy) to automatically increment current version (for example 2.9.6 will be incremented to 2.9.7), then script will commit and push incremented version back to repo and then will deploy new build to internal testing. Currently working only for milestone 2.9 branch. With this script Marko will be able to build and deploy new version without my help (in case when strings need to be changed)


[Bug] Quality is not propagated

Description
Quality information is not properly propagated to ImageProcessor, therefore the resulting images are all set with Quality 100

done with 1.5.1


Just sits on "Loading" when no apps exist

I tried this just now and it works for me. I see "No Apps":

So perhaps it's been fixed.
(You can get stuck in a "Loading" state if an error occurs, such as the Fn server is not running. But if that happens you should see an error message popup at the top right)
Closing as either fixed or not reproduceable.


Threadpool refactor generics

Change ThreadDatastore to be generic.

Merged into https://github.com/codex-storage/nim-datastore/pull/55


Recurcively creates directories copying single file

copy.one("public/assets/tmp/font-awesome-4.7.0/css/font-awesome.min.css", "public/assets/css");

This ends up creating the folders
public/assets/tmp/font-awesome-4.7.0/css
inside of:
public/assets/css
I just want to put the file into this directory without all the other dirs.

try passing an options object with {flatten: true} after the dest. Also, make sure you add a callback so you're notified of any errors:
(I usually try to commit first before doing new copy operations, might be a good idea here)
var src = "public/assets/tmp/font-awesome-4.7.0/css/font-awesome.min.css",
copy.one(src, "public/assets/css", {flatten: true}, function(err) {
  if (err) return console.log(err);
});

Thanks! This is what I was looking for, maybe a suggestion to mention the possible settings of options in the documentation. I couldn't find them there!

This is what I was looking for here, too. Updating to include what to pass as options would help. I was about to dig into the source to find if this was possible

Updating to include what to pass as options would help. I was about to dig into the source to find if this was possible

I'll make a note on the readme! thanks for the tip.
I'll keep this open as a reminder...

Helped me too.


API: compute_features should be more flexible

What features are computed should be up to the user. If someone only wants covariances, it is silly to compute all the other features too.

We could have a parameter like compute_features(epochs, features=('psds', 'freqs', 'covs'))
And then inside the function loop over the features lists to compute only those asked for.
Checking can be done to throw errors if an unknown feature type is asked for.
The return value would always be a dictionary but its size would depend on the length of features.
Finally compute_features(epochs, features='covs') should also work.

very good idea
Le jeu. 22 avr. 2021 à 16:32, Denis A. Engemann @.***>
a écrit :

We could have a parameter like compute_features(epochs, features=('psds',
'freqs', 'covs'))
And then inside the function loop over the features lists to compute only
those asked for.
Checking can be done to throw errors if an unknown feature type is asked
for.
The return value would always be a dictionary but its size would depend on
the length of features.
Finally compute_features(epochs, features='covs') should also work.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/DavidSabbagh/meegpowreg/issues/15#issuecomment-824893982,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIC2QGQHRPDSUHYXLDHFPS3TKAXODANCNFSM43L4FLSQ
.


RFC: Data source connectors

Summary

Allow quick adding of nodes that are backed by REST, gRPC, and/or other data sources. (unsure about dbs)
Proposed Solution

TODO

Hi there,
I've come across this issue about allowing quick adding of nodes backed by various data sources like REST, gRPC, etc., and I find it incredibly interesting and aligned with some of the challenges I'm facing.
I'm particularly interested in the potential to create specific connectors for common services like CMS or e-commerce platforms. The idea would be to develop generic wrappers around the specific SDKs of these services, making them open-source for broader use and adaptation.
A key feature I believe would be invaluable is the composability of these nodes. It would be great if we could import a node and then have the flexibility to redefine or add new properties according to our specific needs. This approach would significantly streamline the process of integrating multiple APIs by reducing the complexity involved in mapping and transforming data for the frontend.
One practical use case I envision is in scenarios where there's a need to integrate a multitude of APIs. A composable node system would simplify this process, making it more manageable and efficient for frontend teams.
The idea of open-source nodes that can be customized and extended fits perfectly with the needs of many developers looking to simplify API integrations.

Hey @b-barry
Thank you for the thoughtful reply! I agree with you on datasources in a very early draft of this library I actually used the datasource concept.
I find the idea of creating an ecosystem of datasources quite appealing, I however personally am not a big fan of exporting node as part of it 😅 the main thing you highlight there is my reason why, the properties should need to be altered which is going to be very hard from both a TypeScript and GraphQL.js point of view as the type is stored and "just works".
That being said, I still like the idea and would encourage a slightly different paradigm where the SDK-Ecosystem exports an interface which can be used in node({ interfaces: [] }) that can already give you a minimal working interface of what's possible with the type and additionally to that the TypeScript type that is exported (or used with the datasource). The reason behind the above is that in t.expose() we'll give you all the options that are present in the type passed to the datasource or node.
How does that resonate with you?

Hey @JoviDeCroock
If I get it, we will have datasource that will be a wrapper around the SDK like you do in your example then you will have also exported interface for common field. Hovewer, I don't think the interface will be needed if we have a good typing from the datasource.
Like you said, we have technically everything to make the mapping. The complexity is mostly in the mapping.
What do you think?

I agree, so basically the package exports
type ShopifyProduct = { id: string; name: string; price: number }
export type ShopifyProductDatasource = Datasource<ShopifyProduct>;

Now when that is used in a node it automatically does datasource.getOne or datasource.getMany for the load function. The type is automatically derived as it's part of the generic passed to the Datasource type. That means that when you do
node({
  name: 'Product',
  datasource: new ShopifyDatasource(yourEnv),
  fields: t => ({
    title: t.exposeString('name') // automatically suggests fields from the ShopifyProduct type
  })
})

I like it, it is interesting ! Another suggestion below
node({
  name: 'Product',
  datasource: new ShopifyDatasource(yourEnv),
  fields: t => ({
    title: t.exposeString('price.value') // could we have multi level mapping ?
  })
})

Concluded in https://github.com/StellateHQ/fuse.js/pull/103#issuecomment-1883657166


Support using env vars for macOS notarization even if a macOS config exists

Thanks for this fantastic crate! We're starting to use it for packaging up some Project Robius applications.
This PR fixes a minor mistake where the notarization credentials specified via environment variables are not used if a macos-specific config ([package.metadata.packager.macos]) has been specified in the Cargo.toml, but that config section doesn't include the notification_credentials field.
Currently there is another related bug in the schema parsing that doesn't actually allow you to provide the notarization_credentials in the package metadata of Cargo.toml, so this change is actually the only way to currently use the notarization features on macOS, as far as I can tell.
More specifically, when I attempt to specify the notarization_credentials field in [package.metadata.packager.macos], I get an error about that field not existing in the schema. I'm not personally sure how to fix that, though.
However, even when that has been fixed, I still think it's beneficial to be able to specify secrets like this via env vars on the command line, instead of being required to place it in the Cargo.toml file, for security purposes.

Thanks for approving the CI checks. I took a look at the clippy logs and the failures do not appear to be related to this PR's small changeset.

Currently there is another related bug in the schema parsing that doesn't actually allow you to provide the notarization_credentials in the package metadata of Cargo.toml, so this change is actually the only way to currently use the notarization features on macOS, as far as I can tell.
More specifically, when I attempt to specify the notarization_credentials field in [package.metadata.packager.macos], I get an error about that field not existing in the schema. I'm not personally sure how to fix that, though. However, even when that has been fixed, I still think it's beneficial to be able to specify secrets like this via env vars on the command line, instead of being required to place it in the Cargo.toml file, for security purposes.

This is intentional for security, as passwords shouldn't be specified in command line and notarization_credentials field can only be set programmatically when using cargo-packager as a library not a CLI.

This is intentional for security, as passwords shouldn't be specified in command line and notarization_credentials field can only be set programmatically when using cargo-packager as a library not a CLI.

Ah I see, thanks for clarifying. Makes sense. As a new user of this crate, I figured it was just an accidental oversight or a mismatch between the schema and Rust-level struct defs.
Given that this is intentional, I think it'd be helpful to specify that design choice via a notice/warning in the doc comments of that notarization_credentials field. If you're open to that, I'm happy to do so (as part of a separate PR), and if you can link me to a list of all the fields that have that restriction, I can even apply that change to all of the "restricted" fields in other parts of Config.

Also, while we're on this topic, I do have a couple of other questions about that design philosophy, i.e., what is and is not exposed via .toml package metadata fields vs. CLI args vs. env vars vs. programmatic access only.

The signing_identity on macOS is also somewhat of a sensitive field that ideally wouldn't be committed to a public git repo, but currently, it can only be specified in the .toml package metadata (unless I'm missing another way to do it). Seems like it'd be a good idea to support providing that on the command line, either via env vars or traditional CLI args.

(I'm not actually 100% sure if this qualifies as "sensitive" data, but I have been instructed not to share/expose it to others.

In general, is there something inherently bad about accepting secrets via CLI args as opposed to env vars? In multi-platform setups, it's much simpler to use and define CLI args (which can always use the same structure) than it is to define env vars, which often differ across host OSes and may be cleared by various runtime environments. Not a big deal either way -- I'm just asking for future reference such that I don't waste your time by creating a PR that supports providing secrets via CLI args, if that is not desired.
If certain fields can only be set programmatically, that implies that we must effectively create another meta-level packaging tool that builds atop cargo-packager. I had been trying to avoid doing this, since I feel it'd lead to more ecosystem fragmentation and reduce the likelihood of us contributing features back into cargo-packager. Either way, our higher-level tool would have to accept similar parameters via files, CLI args, env vars, etc, so someone at some level of the tooling stack would be facing the exact same problem.

My thinking is that we might as well solve that here, such that other tools that depend on cargo-packager don't accidentally mess this up and accidentally expose secrets.
I do understand if you don't want to expand the scope of cargo-pacakger to support this, though.

Perhaps a good solution would be to accept a path to a file that defines certain security-sensitive fields (notarization creds, signing details, etc)? My rationale here is that by having all those details provided in a separate file, we can easily exclude it from git commits via .gitignore and/or a CI check.

Finished all requested changes. Thanks for the feedback!

Given that this is intentional, I think it'd be helpful to specify that design choice via a notice/warning in the doc comments of that notarization_credentials field. If you're open to that, I'm happy to do so (as part of a separate PR), and if you can link me to a list of all the fields that have that restriction, I can even apply that change to all of the "restricted" fields in other parts of Config.

Yeah, that would be nice, there is not many fields that are ignored when parsing config file but those can be easily found which will have #[serde(skip] attribute on them

The signing_identity on macOS is also somewhat of a sensitive field that ideally wouldn't be committed to a public git repo, but currently, it can only be specified in the .toml package metadata (unless I'm missing another way to do it). Seems like it'd be a good idea to support providing that on the command line, either via env vars or traditional CLI args.

(I'm not actually 100% sure if this qualifies as "sensitive" data, but I have been instructed not to share/expose it to others.)

I am not a macOS developer, so can't really say whether it is sensitive or not, so I'd rather leave this to @lucasfernog-crabnebula to answer, but having it as a CLI arg seems fine to me.

In general, is there something inherently bad about accepting secrets via CLI args as opposed to env vars? In multi-platform setups, it's much simpler to use and define CLI args (which can always use the same structure) than it is to define env vars, which often differ across host OSes and may be cleared by various runtime environments. Not a big deal either way -- I'm just asking for future reference such that I don't waste your time by creating a PR that supports providing secrets via CLI args, if that is not desired.

There is nothing bad about using CLI args or env vars, both should be acceptable. I usually see secrets stored in env vars and then passed to CLI args, for example cli --arg1 $SECRET_ARG --arg2 $SECRET_ARG2 so I skipped the CLI options, but we can add these if desired. This could be a positive refactor as it would cleanup some manual std::env::vars calls and rely on env feature.

If certain fields can only be set programmatically, that implies that we must effectively create another meta-level packaging tool that builds atop cargo-packager. I had been trying to avoid doing this, since I feel it'd lead to more ecosystem fragmentation and reduce the likelihood of us contributing features back into cargo-packager. Either way, our higher-level tool would have to accept similar parameters via files, CLI args, env vars, etc, so someone at some level of the tooling stack would be facing the exact same problem.

These fields can be set programmatically when using cargo-packager as a library but when cargo-packager is used as a CLI, either through cargo packager, a prebuilt binary of it or the JS CLI, these fields will usually be set only through environment variables (and soon CLI arguments, based on discussion above)

those can be easily found which will have #[serde(skip] attribute on them

Excellent, thanks for the tip.

The reasons why I wouldn't want these be explicitly managed here is to allow flexibility for a higher tool atop of cargo-packager, namely tauri-bundler or tauri-cli which could use different environment variables names for these secrets.

Sounds good to me, thanks for sharing your view here.

I wouldn't say this would fragment the ecosystem at all, since it is the CLI frontend that would need to be implemented atop of cargo-packager which only does:

By this, I merely meant that we (Project Robius) are trying to avoid creating tools that duplicate functionality that already exists in the ecosystem. I've also discussed this goal at length with the Linebender project, though not relevant to this packaging concern specifically. Either way, it's okay with me --- we'll continue on the path to creating a frontend wrapper around cargo-packager, and I can then periodically submit PRs here for features that I consider worthy of including in cargo-packager itself.

Thanks for your contributions

Thanks, and thank you for all the additional information about this crate!

I am not a macOS developer, so can't really say whether it is sensitive or not, so I'd rather leave this to @lucasfernog-crabnebula to answer, but having it as a CLI arg seems fine to me.

Turns out that whether the signing_identity is considered a secret is a bit of a controversial opinion. Prior to 2014, there was an Apple bug that caused a lot of people to keep their signing identity secrets, but now there is technically no reason not to do it. Given that I've been asked to keep it private, I think I'll still proceed with adding a feature that accepts the signing_identity via a command-line arg or env var.


docker stop showing 'errors' in runtime log

Distro: Ubuntu 16.04.2 LTS server
cc-runtime: 3.0.0-beta1 (from OBS install)
Running:
docker run -tid busybox sh
docker stop XXXXXX
docker rm XXXXXXX

where XXXXXX is the container ID from the first step, is producing two errors for me in the runtime log (that I enabled by uncommenting the relevant section of the /etc... config file):
2017-08-25 15:41:29.834518887 +0100 BST:2952:cc-runtime:error:Container cc80658aae0bad16ad5c1be722b0d06dc54c8b5d6978455a0f14a684bc9b65bd not ready or running, cannot send a signal
2017-08-25 15:41:32.750079653 +0100 BST:2968:cc-runtime:error:Container ID does not exist

The ID there matches the XXXXXX above.
afaict, the error lines appear during the docker rm phase - but, I am not wholly convinced that is right.
I would post the whole/rest of the relevant bits of the log, but it is about 800 long lines, so perhaps I'll not do that yet.

@grahamwhaley -- I see the same thing when doing:
docker run -it alpine sh
exit
This is a bit concerning, especially given some of the other life cycle bugs we have open.

Closing as this isn't a bug in the runtime, it's a bug in containerd afaik:

https://github.com/01org/cc-oci-runtime/blob/master/src/oci.c#L1102

And here's the relevant snippets from a debug log showing how the runtime was called for a single container lifecycle:
$ sudo grep "called as" /var/lib/clear-containers/runtime/runtime.log|cut -d\) -f2-|tr -d :|tr -d \[|awk '{print $1,$2,$3}'
called as create
called as start
called as kill
called as delete
called as delete

So @jodh-intel , should we be changing our error to a warning, to match cc-oci-runtime better (and cause less concerning messages in the logs) ?
If so, we might want to re-open this or a new Issue.

It's very debatable. The runtime has detected that it has been called incorrectly, so that is an error. I'm easy either way though as long as we log at atleast the warning level.

OK, after irc chatter and input from @egernst I'm going to re-open this asking that we downgrade those errors to info/warnings - given that the double delete is, I believe, benign, correct @jodh-intel ?

It's benign in that the runtime catches the incorrect call from containerd and handles it, yes.
@egernst - please can you reference this bug when you raise an issue on containerd.


Adds conformance tests for floats

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

My suggestions are all more minimal expressions of the same float value. There's no point in presenting precision that the type does not actually allow.

All of the tests where you have made these suggestions are tests for subnormal numbers, so this is not actually an excess of precision.


Proposal: ViewHelpers for components

Proposal for https://github.com/primer/view_components/issues/259
This PR provides a simpler way to render PVC components, providing a primer(:name, **kwargs) { block } view helper.
How it works
Created a DSL Primer::DSL::ViewHelper that enables components to register their own helpers using:
view_helper :my_helper

Also provides Primer::ViewHelper that creates the primer(name, **kwargs, &block). The helper will look for registered helpers and raise an error if not found. This is the module needs to be manually included to be used outside of Primer::Component

I did consider both! The difference is how we would register the components in each option
To have helpers like primer_octicon I'd need a static mapping of helper -> component like
MAPPNGS = {
  octicon: Primer::OcticonComponent
}

And then, when the ViewHelper module was included, I could define methods for each helper using define_method and so on.
On the other hand, primer(:octicon) allowed the creation of a DSL so each component could register itself instead of creating yet another static list that I have to keep adding components.
From a user point of view, calling primer_octicon icon: :some_icon vs primer :octicon, icon: :some_icon is the same thing. So I opted for building the solution with the DSL


fix(button -> negative): corrects interior label background color to align with parent

Description

Apples forced-color-adjust: none to align the rendered background of the child label for negative button varient with the enclosing button's background color.

How and where has this been tested?
Verified in Assistiv Labs high contrast mode-enabled Windows VM.
Validation steps

Run Storybook locally (or reference the link for this PR).
Navigate to Assistiv Labs and start a Windows High Contrast Mode VM (if running the branch locally, you'll need to enable the Assistiv Labs tunnel to access Storybook).
Enable Windows High Contrast Mode.
Navigate to the Button component in Storybook.
Select the negative variant.
Zoom in and verify that the there is no background (the button background should be a uniform color).

Regression testing
Validate:

The documentation pages for at least two other components are still loading, including:

[x] The pages render correctly, are accessible, and are responsive.

If components have been modified, VRTs have been run on this branch:

[ ] VRTs have been run and looked at.
[ ] Any VRT changes have been accepted (by reviewer and/or PR author), or there are no changes.

Screenshots

To-do list

[x] I have read the contribution guidelines.
[x] I have updated relevant storybook stories and templates.
[x] I have tested these changes in Windows High Contrast mode.
[ ] If my change impacts other components, I have tested to make sure they don't break.
[ ] If my change impacts documentation, I have updated the documentation accordingly.
[x] ✨ This pull request is ready to merge. ✨

Do we need to ensure that this looks consistent in light mode as well? I'm seeing some introduced issues here that might need to be taken care of if so:
(In AssistivTunnel, with the High Contrast White theme):
(In Chrome, emulating forced colors and prefers-color-scheme: light):

Do we need to ensure that this looks consistent in light mode as well? I'm seeing some introduced issues here that might need to be taken care of if so:
(In AssistivTunnel, with the High Contrast White theme):
(In Chrome, emulating forced colors and prefers-color-scheme: light):

✨ Huh — it looks like the button-content-color tokens are getting set in the button's index.css file but not defined. Setting them on .spectrum-Button looks good (and they can be updated by subsequent declarations specific to different states):
.spectrum-Button {
  --highcontrast-button-content-color-default: ButtonText;
  --highcontrast-button-content-color-hover: ButtonText;
  --highcontrast-button-content-color-focus: ButtonText;
  --highcontrast-button-content-color-down: ButtonText;
}

The styles aren't terribly distinct, but I imagine the available colors don't allow them to be.


Grpc.Tools: Use x86 protoc binaries on arm64 Windows

A workaround for https://github.com/grpc/grpc/issues/31975 - use x86 protoc binaries on Windows arm64.
Unable to test as I don't have access to Windows-arm64.
Also not sure how NUnit PlatformAttribute handles arm64 (could not find any information).  It is possible that tests will fail if run on Windows-arm64 with full .NET framework if NUnit doesn't distinguish between x64 and arm64 (just identifies a 64 bit platform). Not sure that we run tests on Windows-arm64.

Within the next 24 hours after merging, a Grpc.Tools nuget with the fix should show up in https://packages.grpc.io/ (and also the daily nuget feed: https://github.com/grpc/grpc-dotnet#grpc-nuget-feed).
It would be good to get a verification from the user.

@jtattermusch the Grpc.Tools nuget in the nightly builds has dummy binaries (zero length) for most platforms so cannot be used for testing.

@jtattermusch the Grpc.Tools nuget in the nightly builds has dummy binaries (zero length) for most platforms so cannot be used for testing.

Filed https://github.com/grpc/grpc/issues/32179


Gateway upgrade docs

Realized we need a small script to upgrade Docker-based gateways reliably.

@AndrewDryga Going to merge this to get a new release out for beta customers. We can tweak / improve the upgrade script after if that's alright.


Enable hardware acceleration in mpv

How do I enable HW video decoding when watching a video? There's an option --hwdec=vaapi for this purpose in mpv, but how do I make the script pass it to mpv? There's another problem involved - acceleration works on my GPU, but not for VP9 codec used by youtube by default. In the browser I have h264ify, which disables VP9 in favor of H264, but it acts only when watching a video in the browser directly, and the script obviously brings communication with youtube outside of the browser and VP9 is used (I see it in the console).

Now I enabled an option for yt-dlp which chooses the h264 codec both in yt-dlp.conf and in mpv.conf. And when I play the video with plain mpv, it works - the h264 stream is chosen. But it doesn't work when I press the Play in MPV button! What the?

Now I enabled an option for yt-dlp which chooses the h264 codec both in yt-dlp.conf and in mpv.conf. And when I play the video with plain mpv, it works - the h264 stream is chosen. But it doesn't work when I press the Play in MPV button! What the?

Can you tell me what option you are using?

In mpv.conf it looks like
ytdl-format="(bv*[vcodec~='^((he|a)vc|h26[45])']+ba) / (bv*+ba/b)"

In mpv.conf it looks like ytdl-format="(bv*[vcodec~='^((he|a)vc|h26[45])']+ba) / (bv*+ba/b)"

Emm, because these options are overridden by https://github.com/akiirui/mpv-handler/blob/main/src/plugins/play.rs#L51-L62
Let me think about how to solve this problem.

I think you can use -S (Sorting Formats) to prefer h265/h264.

Fixed in https://github.com/akiirui/userscript/commit/ce2224b5055eba1cf55d40187d48ac5c4fcb5bfc & https://github.com/akiirui/mpv-handler/commit/1d2ece3cd22f32cefc64bf49224e4f67d754485a
Now, you can select video codec in play-with-mpv!

Thanks, this is very kind of you! So I need to download the latest release in order for it to work, right?

I performed the installation again, deleted the configs and now something is broken. I can select the codec, but the player won't open now (even when codec is not selected). That is it opens the window for a moment and immediately closes.

I don't know how to troubleshoot this.

Does mpv-handler output any info/errors？

It says:
mpv-handler: /lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.32' not found (required by mpv-handler)`
So it does 3 times.

It says: mpv-handler: /lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.32 not found (required by mpv-handler) So it does 3 times.

Emm, what version is your glibc?

Okay, https://github.com/actions/runner-images/issues/6699 ubuntu-latest (a.k.a. ubuntu-22.04) has new version glibc...

After the Github Actions build is complete, you can download the new version and it should work.

My system says it has version 2.31-13, which is older.
Some things you said I didn't understand and maybe I don't need to, but what is Github actions? Will this build be in the same place as usually (in releases) or in some other place?

what is Github actions?

https://docs.github.com/en/actions/learn-github-actions/understanding-github-actions

Will this build be in the same place as usually (in releases) or in some other place?

It's done, see https://github.com/akiirui/mpv-handler/releases/tag/v0.3.2-rebuild

Finally, thank you for catching the problem of Linux binary not working on the older glibc systems.

If I add --hwdec=vaapi option to mpv.conf now, will HW acceleration work

Yes, if your gpu suppors vappi and these codec.

it does in SMplayer which uses mpv as well

Sorry, I don't know, I've never used it.

Yoohoo, it works! This is the perfect ending of my day.
But please write what glibc version is required on the readme page so that someone who has older version than required could understand why it's not working for him. Dependency check is not done here, so it's necessary.

It no longer requires an exorbitant glibc version.  The current required version is minimum 2.17 as of rust 1.64

They may have their reasons. And even if there are no such users everyone who wants to install the app must know what this app requires in order to know that it will work for him. When installing from package or compiling from source the check is done automatically, but it is not so here.

Hmm, maybe I can use musl to build binary for Linux users downloaded from github, it doesn't link any dynamic libraries.

For now you can simply write in the README that the program requires certain version of certain library. Thus everyone can understand whether it works for their system.

It does not depend on any dynamic libraries, it's a completely static binary now. 😀


Fix Debug issue

Fix debug issue caused by CMAKE_BUILD_TYPE=Release

Codecov Report

Merging #639 into develop will decrease coverage by 4.77%.
The diff coverage is 100%.

@@             Coverage Diff             @@
##           develop     #639      +/-   ##
===========================================
- Coverage    48.01%   43.24%   -4.78%
===========================================
  Files          304      304
  Lines        11025    12035    +1010
  Branches      5652     6625     +973
===========================================
- Hits          5294     5204      -90
- Misses         489      714     +225
- Partials      5242     6117     +875

Impacted Files
Coverage Δ

irohad/main/config/config.hpp
83.87% <100%> (-2.34%)
:arrow_down:

irohad/consensus/yac/impl/yac_gate_impl.hpp
0% <0%> (-100%)
:arrow_down:

irohad/ametsuchi/impl/test_storage_impl.hpp
0% <0%> (-100%)
:arrow_down:

...ad/consensus/yac/impl/yac_crypto_provider_impl.hpp
0% <0%> (-100%)
:arrow_down:

irohad/ametsuchi/impl/flat_file_block_query.hpp
0% <0%> (-100%)
:arrow_down:

irohad/validation/impl/stateful_validator_impl.hpp
0% <0%> (-100%)
:arrow_down:

irohad/network/ordering_service.hpp
0% <0%> (-100%)
:arrow_down:

irohad/ametsuchi/impl/redis_flat_block_query.hpp
0% <0%> (-100%)
:arrow_down:

...d/network/impl/peer_communication_service_impl.hpp
0% <0%> (-100%)
:arrow_down:

irohad/network/impl/block_loader_service.hpp
0% <0%> (-100%)
:arrow_down:

... and 135 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 98c0d22...b1dc956. Read the comment docs.


useScroll doesn't return direction, distance etc.

Describe the bug
When using useScroll, direction and distance aren't returned. However when using useWheel they are.
Sandbox or Video
Issue can be seen in the dev console
https://codesandbox.io/s/cranky-tu-pl0lq?file=/src/App.js

Hi @mattmuirhead thanks for the sandbox. Note that it's not using the last version of the lib. Is there any reason why you're using document instead of window?

Hi @dbismut, sorry have updated the sandbox now. Also updated the sandbox to be more reflective of what we're trying to achieve. We're not scrolling the main document, we're scrolling a div inside the document. However, we don't have access to bind the useScroll to the div. https://codesandbox.io/s/cranky-tu-pl0lq?file=/src/App.js

You mean you can't do this?
https://codesandbox.io/s/recursing-star-6ivzm?file=/src/App.js

Unfortunately not. The component we're using passes the ref to the inner div rather than the div that scrolls

Would this be an acceptable solution: https://codesandbox.io/s/recursing-star-6ivzm?
Unfortunately, the only fix that I could make is to change the target for scroll events from currentTaget to target. But that would probably lead to unwanted behavior in some circumstances.
Note that we've diverted from the original issue, which is now that you'd want useScroll to intercept scroll events attached to any children of the domTarget (which doesn't feel right imo).

Thanks for the reply. I'll look into your solution.
Is there a reason though why useWheel returns the correct data but useScroll doesn't when targeting the document?

Yes. Elements intercept wheel events more or less the same way they do for pointer events. scroll events only happen when an element actually scroll. In your case window will intercept all wheel events that propagates down to it. But if the window doesn’t scroll it won’t fire any scroll events.


Validate segment/analytics working as expected after treq PR

The Issue
Test segment/metabase data collection after https://github.com/lbryio/lbry/pull/1191
System Configuration

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

Anything Else

Screenshots

Working as expected.


[v9] Dashboard > Blocks > Permissions - Info Icon Popup Issues

When clicking either Add Block or Add Stack, the Info Icon in the upper right, when clicked, creates the popup behind the permission modal and it's not fully visible.
Also after adding a permission and coming back to the permission modal there will be 2 Info Icons, both hidden behind the modal.

This is fixed in 9.0.0RC4


On multiple clicks on moveup toast message is displayed

Screenshot

Expected Behaviour
Toast Message should be displayed only if there is no toast message being displayed.

@arteevraina can you fix it?
/cc @BetaCat0 @GopherJ @438561537

@arteevraina can you fix it?
/cc @BetaCat0 @GopherJ @438561537

Sure thing!