[compatibility] libusbx replaced by libusb-1.0 in most distros

As of March 2020 on most distros libusbx has been replaced by the maintained libusb-1.0.
This reflects the re-merging of the libusbx-project-fork back into the libusb-project (see https://github.com/libusb/libusb/wiki/FAQ#libusborg_libusbxorg_and_libusbinfo) as referenced by  @slyshykO in #782. As mentioned in PR #895, I did some small research on this topic to find out about the current state of support by various distributions currently maintained.
Here is the result from https://pkgs.org/search/?q=libusb (as of Mar 2020):
1.0.23

Alpine Edge
Alpine 3.11
ALT Linux Sisyphus
Arch Linux
Debian Sid
Fedora Rawhide --> libusbx, but compatible, as libusb-codebase is used
KaOS
OpenMandriva Cooker
OpenMandriva Lx 4.1
openSUSE Tumbleweed
Slackware Current
Solus
Ubuntu 20.04 LTS
Ubuntu 19.10

1.0.22

Alpine 3.10
Alpine 3.9
CentOS 8 --> libusbx, but compatible, as libusb-codebase is used
Debian 10 (Buster)
Fedora 31 --> libusbx, but compatible, as libusb-codebase is used
Fedora 30 --> libusbx, but compatible, as libusb-codebase is used
Mageia Cauldron
Mageia 7.1
NetBSD 9.0
NetBSD 8.1
NetBSD 7.2
OpenWrt 19.07
OpenWrt 18.06

1.0.21

CentOS 7 --> libusbx, but compatible, as libusb-codebase is used
Debian 9 (Stretch)
openSUSE Leap 15.2
openSUSE Leap 15.1
Ubuntu 18.04 LTS

1.0.20

OpenMandriva Lx 3.0
Slackware 14.2
Ubuntu 16.04 LTS

... older libusb versions --> would no longer be supported

Debian 8 (Jessie) - 1.0.19
Ubuntu 14.04 LTS - 1.0.17
CentOS 6 - 1.0.9
Slackware 14.1 - 1.0.9

FreeBSD 13 - linux_libusb-13.0r358841 --> compatible (?)
FreeBSD 12 - linux_libusb-11.0r261448_4 --> compatible (?)
FreeBSD 11 - linux_libusb-11.0r261448_4 --> compatible (?)
Looking at this may go to libusb 1.0.20 to ensure widespread compatibility.

This initiated a ongoing discussion in PR #895 which shall be continued here, as the related PR should solely focus on (direct) changes in the code. The beginning of this discussion is now posted here:
Nightwalker-87:
@Vascom: You are on Fedora right? What do you think about this? Why does Fedora still use libusbx BTW? Is your library that outdated as well?
Reply by Vascom:

@Nightwalker-87 I don't know why it still not updated in rawhide. Need to ask maintainer.
But even if this update will be done it will be never updated for current releases of Fedora and RHEL/CentOS.

Reply by slyshykO:

Looks like starting from this commit https://src.fedoraproject.org/rpms/libusbx/commits/master Fedora switched from libusbx to libusb but don't change the package name.

Reply by Vascom:

No.
libusb - for compatibility with 0.1 API.
libusbx - main libusb as I know.

Reply by slyshykO:

@Vascom Yes. My point is they (Fedora) use sources from libusb-project for libusbx-package.

Reply by Vascom:

upstream libusbx has merged back with libusb and is now called libusb again, but we already have a libusb package for the old libusb-compat-0.1, renaming that to libusb-compat while at the same time giving this its name is a bit tricky, lets stick with the libusbx name for now

@Vascom: There are three relevant things:

As @slyshykO mentioned before: the package name is not the relevant thing, but if LIBUSBX_API_VERSION is used by the package which then remains from the libusbx-codebase
Nobody cares about libusb-compat, libusb-0.1 or whatever the older packages for libusb 0.1 compatibility versions are called. These are neither addressed by this issue, nor relevant.
¯\ _(ツ) _/¯
Please test the current development branch with your fedora environment as it comes without any reference to LIBUSBX_API_VERSION. If it works we are fine here, if not, the incompatibility with fedora is present for quite a long time, as previously LIBUSBX_API_VERSION could only be called on FreeBSD systems anyway (where it was not needed anymore, as we found out in #782 previously).

1.0.23 pushed to Fedora rawhide now https://src.fedoraproject.org/rpms/libusbx/c/5684853d449b7fe3a81112cd59f9336fbc274319?branch=master

That's good news for us.

Similar result for Fedora 30 (oldest supported version):
Here it is libusb 1.0.22 despite the (false) package name: https://src.fedoraproject.org/rpms/libusbx/c/cbd5348ee14638264fe3bb79c3b27a5ed34271ed?branch=f30
One can conclude that this is done equally in Fedora 31, so we are fine here. That's the reason why it works even without any LIBUSBX_API_VERSION remnants currently. :+1:

@lhondareyte @DanielO: It appears you both use (or used) FreeBSD. Can you provide us some information regarding the libusb versions present on recent releases (11, 12, 13)? pkgs.org was not very helpful in this aspect.

Hi,
For FreeBSD, libusb is in the base system, it's not a package. It's compatible with libusb1 & 2 . You get more informations with "pkconf":
pkgconf --libs  --cflags libusb-1.0
pkgconf --libs  --cflags libusb-2.0
pkgconf is, as far I know, specific to FreeBSD.
Hope this help.
Regards

@lhondareyte: Thx for the useful feedback. What FreeBSD-Version/Release are you on? Can you also checkout the develop branch and test-compile the stlink-tools? With this we could rule out possible regression when we merge the related PR. By now current FreeBSD Releases seem to be the only left "unknowns" (see list above).

I am running the latest stable version (12.1p1) (almost). I tried to compile the latest snapshot and it actually failed:
/usr/home/luc/stlink/src/usb.c:34:22: error: use of undeclared identifier 'INT_MAX'
The compilation works with
// src/usb.c
#if defined (__FreeBSD__)
#include <sys/limits.h>
#endif

Which commit/branch do you want to try exactly?
About FreeBSD current (latest dev branch), I only use it on ARM platform. I'll give it a try this week-end: just try to compile only USB support can be tricky

The latest develop would just be fine, as we still have to decide on, which codelines have to be added in order to make it compile in FreeBSD environments. Thx for helping out with this. :+1:
To me it looks like that nobody really bothered about FreeBSD too much before, apart from very few single contributions. Beginning with v1.6.1, I want to make sure which distributions (incl. versions) work and have that put into our documentation as well to reduce continuous "cannot compile on xyz-system" issues here. I'm fed up seeing these.

I understand but don't be worried about FreeBSD: stlink is in the ports tree (well, not the latest release)  with an active maintainer. And most FreeBSD users use ports  ;)
And I regulary check the latest snapshot on FreeBSD and macOS (via rudix)
However, I'll give it a try on FreeBSD 13

... well it does make sense to distribute recent fixes and features to this usergroup as well, doesn't it? Old packages are no help here, especially not for available maintainers on that platform.

Note: By setting the minimum version requirement for libusb to 1.0.20, we could make this equal for all supported systems (Windows, macOS and even most of the oldest supported linux/unix distributions), thus keeping it simple and memorable.

Hi,
For FreeBSD, libusb is in the base system, it's not a package. It's compatible with libusb1 & 2 . You can get more informations with "pkconf":
pkgconf --libs --cflags libusb-1.0
pkgconf --libs --cflags libusb-2.0
pkgconf is, as far I know, specific to FreeBSD.

FreeBSD ships with pkg-config files for libusb-0.1, libusb-1.0 and libusb-2.0 (2.0 is a FreeBSD specific one).
eg..
[delamerelts 1:44] ~> pkg-config --cflags --libs libusb-0.1
-lusb
[delamerelts 1:44] ~> pkg-config --cflags --libs libusb-1.0
-lusb
[delamerelts 1:45] ~> pkg-config --cflags --libs libusb-2.0
-lusb

This works on Linux too (for me)
[ubuntu 12:17] ~ >pkg-config --cflags --libs libusb-1.0
-I/usr/include/libusb-1.0 -lusb-1.0

I think we should use the newest libusb that we can. On all platforms.

Note: There is a difference between working versions and the minimum required version .
This does not rule out that users should be encouraged (by a note in the documentation) to install the latest available version on their respective system. It only denotes that the tools would be still be capable to compile and run with the oldest version defined. On Ubuntu 16.04 LTS for example 1.0.20 is the newest version available as you can see in the list (and there will be no newer version for this release anymore).

@DanielO: What are the exact version strings (e.g. 1.0.22, etc.)? That would be the relevant point here...

@DanielO : yes, you're right : pkg-config is a link to pkgconf
@Nightwalker-87 :
libusb_get_version() return <IP_ADDRESS>6 with this code:
version = libusb_get_version();
printf("%d.%d.%d.%d\n", version->major, \
                        version->minor, \
                        version->micro, \
                        version->nano);

@lhondareyte: o.O That is what I asked for, but it does not seem to help at all. I did not expect a different versioning scheme compared to the one the libusb-project uses...

libusb define LIB_API_VERSION  since v1.0.13 which describe features that are include. All OSs that you list have this definition. So why do you want to deal with lib version instead of API version?
Currently all supported FreeBSD versions (11,12) and current define this
#define LIBUSB_API_VERSION 0x01000102
Perhaps, I miss something, if so, let me know.
Best regards

The LIB_API_VERSION is not the relevant point here as it is used in the stlink-tools codebase already. We have dealt with this in #782. Now we are solely on about how recent we require the package libusb to be at least. We can't help it that FreeBSD has libusb integrated and uses a different versioning scheme than the libusb-project, what makes it hard to compare both codebases with each other. So we can not say anything like libusb <IP_ADDRESS>6 on FreeBSD derives from the e.g. libusb-1.0.20 package from the libusb-project or alike. We can do so for all other operating systems.

In this issue, this is LIBUSBX_API_VERSION the problem. LIBUSBX_API_VERSION is almost marked as deprecated in libusb :
/* The following is kept for compatibility, but will be deprecated in the future */
#define LIBUSBX_API_VERSION LIBUSB_API_VERSION

It has nothing to do with FreeBSD, I think

So what would be a solution to this (apart from trusting on that it will run and without tracking a version on FreeBSD)? I feel uncomfortable with this as one would have to look at this special case every time a new version is published on FreeBSD and test it manually.

I'll take a look. But it looks strange to me that you spend  so much time for Ubuntu 12.04 that is no more supported since 2017

I'll take a look. For short, any reference to LIBUSBX_API_VERSION should be remove from stlink code.

This is already the case in the develop branch, as I wanted to get rid of this deprecated stuff.

Do you know the minimal API_VERSION to works with stlink? In fact, wihch features do you need?

No, I don't, but that is what I am looking for. If we can find out the LIBUSB_API_VERSION of the 1.0.20 package, we can compare it to the one in FreeBSD. Maybe that is another approach to determine where the codebase derived from.
I would no longer like to see all these unknowns we have been dealing with up to now. As we have several tickets related to libusb issues, not having this defined clearly does not help. I feel like this is hindering maintenance in this project.

I have made an inventory on latest officials releases:

1.0.12 and above dont define *API_VERSION
1.0.13 to 1.0.17 define LIBUSBX_API_VERSION only
since 1.0.18 both LIBUSB_API_VERSION and LIBUSBX_API_VERSION are defined as follow

define LIBUSB_API_VERSION 0x01000103
define LIBUSBX_API_VERSION LIBUSB_API_VERSION

LIBUSBX_API_VERSION appeared in 1.0.13 and LIBUSB_API_VERSION in 1.0.18
A simple solution could be, for every OSes:
#include <libusb.h>

#if !defined ( LIBUSBX_API_VERSION )
 #if defined (__FreeBSD__)
   #define LIBUSBX_API_VVERSION LIBUSB_API_VERSION
 #elif !defined (LIBUSB_API_VERSION)
   #error unsupported libusb version
 #endif
#endif

#define MINIMAL_API_VERSION 0x01000101

#if ( LIBUSB_API_VERSION <= MINIMAL_API_VERSION )
 #error unsupported libusb version
#endif

About LIBUSBX_API_VERSION/LIBUSB_API_VERSION :
v1.0.13 : 0x01000100
v1.0.14 : 0x010000FF
v1.0.15 : 0x01000101
v1.0.16 : 0x01000102
v1.0.17 : 0x01000102
v1.0.18 : 0x01000102
v1.0.19 : 0x01000103
v1.0.20 : 0x01000104

@lhondareyte: Excellent, and what is the LIBUSB_API_VERSION string is present on each FreeBSD 11, 12, 13? Can one look that up somewhere on the web? By this, we are finally able to gain this information via the laborious route... I can then complete the listing above and a final decision can be made.

They're all 0x01000102:
11.0.0 - https://svnweb.freebsd.org/base/release/11.0.0/lib/libusb/libusb.h?revision=354337&view=markup#l38
12.1.0 - https://svnweb.freebsd.org/base/release/12.1.0/lib/libusb/libusb.h?revision=354337&view=markup#l38
Head - https://svnweb.freebsd.org/base/head/lib/libusb/libusb.h?revision=326219&view=markup#l38
It hasn't changed since that #define was added in r301957
https://svnweb.freebsd.org/base/head/lib/libusb/libusb.h?revision=301957&view=markup

@DanielO: Thx for checking! Please let us know if this changes someday.
ok, so we actually have to stay on libusb 1.0.16 ... 1.0.18 codebase then for FreeBSD for compatibility reasons. In terms of implementation we will likely check for the 0x01000102 in cmake here.
I'll do a new table for our documentation that is going to list all what we have found out by now.
@slyshykO: Can you extend you PR #895 with the discussed check for windows and maybe also update the cmake routine for FreeBSD?

I've updated the #895. Please, take a look.

@slyshykO: I've had a look through it.
I'm not sure about the present state in macOS yet and how we can deal with it there, but I have a VM where I could possibly test version 10.14 and may setup one for 10.15 as well.


Bug/compatibility plugins new view

Description of the Change
This change  ensures compatibility with other plugins that might open new tabs as well (e.g. marcusolsson/obsidian-projects).
Bug report: https://github.com/chrisgrieser/new-tab-default-page/issues/14
Checklist

[x] Used the provided eslint configuration, as explained in the Readme.
[x] Did not use prettier.
[x] Used expressive variable names.
[x] Code is commented well.

thx!

🙏


Jacobian producing unexpected results

Hello again,
In trying to produce the pushforward, I tried this approach to take advantage of the jacobian
function dbla2(d,c,dc)
    inner(e) = (c.+e.*dc).^2
    Enzyme.jacobian(Enzyme.ForwardMode(),inner,[0.])
end
dbla2(ddd,ones(3),2*ones(3))
3-element Vector{Float64}:
 6.0
 6.0
 6.0

Which is wrong, 2*c*dc = 4*ones(3). Is this a bug, or am I doing something wrong, again :)

Debugging:
using Enzyme

Enzyme.API.runtimeActivity!(true)
Enzyme.API.printall!(true)
Enzyme.API.printactivity!(true)
function dbla()
        c = ones(3)
        inner(e) = c .+ e
        Enzyme.autodiff(Enzyme.Forward, inner, Duplicated([0.], [1.]))
end

@show dbla()

In essence the bug comes from the fact that the outside variable comes from the closure hits a runtime activity analysis issue.

With the jll bump on main this should be fixed, even without runtime activity. Please reopen if that is not the case.


Replace isPlaying with isRunning

It seems that there are some changes in the latest Flutter (see: https://github.com/n-bernat/kanjivg/pull/5)
It would be a good idea to replace the current isPlaying with isRunning from the framework to avoid duplicating functionality.

The package now uses isAnimating instead.


Separate variables and/or config files to reduce complexity of the config file

Related: #311

I think this is one we should tackle first, there are a few other issues that depend on this working well.

An idea where we can use multiple config files, and with the following rule of thumb:

each file should be able to be run with the -c this means some duplication of some keys (variables, workspace, system)

config.yml (toplevel):
create: create.yml
submit:
  system: jetto-duqtools
  workspace: /pfs/work/<user>/jetto/runs
merge: merge.yml

I did not put submit: in its own file, because it contains very little information.
A self-contained create.yml, that can also be used with the -c option, notably it now contains the workspace, system and variables key:
create:
  system: jetto-pythontools
  workspace: /pfs/work/<user>/jetto/runs
  dimensions:
  - values: [ 1.1, 1.2, 1.3 ]
    operator: multiply
    scale_to_error: false
    variable: t_i_average
  variables: variables.yaml

It might be easier to put variables, workspace, system at toplevel so it matches better with what we already have.
A self-contained variables.yaml:
- name: rho_tor_norm
  type: IDS-variable
  ids: core_profiles
  path: profiles_1d/*/grid/rho_tor_norm
  dims: [ time, x]
- name: major_radius
  type: jetto-variable
  lookup:
    doc: Reference major radius (R0)
    name: major_radius
    type: float
    keys:
    - file: jetto.jset
      field: EquilEscoRefPanel.refMajorRadius
    - file: jetto.in
      field: RMJ
      section: NLIST1

other seperated out config  files can be created in the same manner (merge, plot)


Import on demand install fails without first preparing babel-plugin-import

vue create antsy
> default (babel, eslint)
cd antsy
vue add ant-design
> Import on demand
> en_US

This fails for me in postinstall. (Fully import works.) Fixed with as per advanced guides from ant docs (npm i babel-plugin-import -D and modify babel.config.js before adding plugin).
EDIT: And furthermore, still needed to remove LocaleProvider from src/plugins/ though the install was was without errors (errors shown in dev tools console). 😕
Would you kindly update deps so it's not manual.
(Also, there are some prototype pollution warnings on npm audit)
Full error print out below (cleared funding and vulnerabilities notes).
Cheers :)
> vue add ant-design

📦  Installing vue-cli-plugin-ant-design...

+<EMAIL_ADDRESS>added 1 package from 1 contributor and audited 25497 packages in 4.97s

(fund and vulnerabilities notes)

✔  Successfully installed plugin: vue-cli-plugin-ant-design

? How do you want to import Ant-Design-Vue? Import on demand
? Choose the locale you want to load en_US

🚀  Invoking generator for vue-cli-plugin-ant-design...
📦  Installing additional dependencies...

><EMAIL_ADDRESS>postinstall /Users/Nikola/dev/antsy/node_modules/babel-runtime/node_modules/core-js
> node -e "try{require('./postinstall')}catch(e){}"

><EMAIL_ADDRESS>postinstall /Users/Nikola/dev/antsy/node_modules/ant-design-vue
> node scripts/postinstall || echo "ignore"

added 68 packages from 93 contributors and audited 25642 packages in 5.029s

42 packages are looking for funding
  run `npm fund` for details

found 5 vulnerabilities (4 moderate, 1 high)
  run `npm audit fix` to fix them, or `npm audit` for details
⠋  Running completion hooks...error: 'LocaleProvider' is not defined (no-undef) at src/plugins/ant-design-vue.js:3:15:
  1 | import Vue from 'vue'
  2 | import { Pagination, Button } from 'ant-design-vue'
> 3 | Vue.component(LocaleProvider.name, LocaleProvider)
    |               ^
  4 | Vue.component(Pagination.name, Pagination)
  5 | Vue.component(Button.name, Button)
  6 |

error: 'LocaleProvider' is not defined (no-undef) at src/plugins/ant-design-vue.js:3:36:
  1 | import Vue from 'vue'
  2 | import { Pagination, Button } from 'ant-design-vue'
> 3 | Vue.component(LocaleProvider.name, LocaleProvider)
    |                                    ^
  4 | Vue.component(Pagination.name, Pagination)
  5 | Vue.component(Button.name, Button)
  6 |

2 errors found.

Please try again，tks


feat: 新增对行末换行符、git大小写敏感配置的检查

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/xun082/create-neat/blob/master/CONTRIBUTING.md
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

What is the current behavior?

Closes #107
Related to #107

What is the new behavior?

Does this PR introduce a breaking change?
[ ] Yes
[x] No

Other information

提交到release1.2吧，

提交到release1.2吧，

好的，已经修改完毕


Allow creating new organization

Q
A

Bug fix?
no

New feature?
yes

BC breaks?
no

Deprecations?
no

Tests pass?
yes

Fixed tickets
no

License
MIT

Doc PR
no

@gorkalaucirica yo need to rebase this branch


fix: README prop desc

Fix

README.md

The name and default value for prop wrapperColor was wrong.

Closing since this is not the only prop that's not relevant.


Test ALU Operations

Testing of ALU Operations
Description:
Implements Mocha testing of all the operations of the ALU.
Content

Adds a Makefile for generating test data for the different ALU operations
Adds 3 python files which generate random test data to test the ALU against
Unit testing of Adding.subtracting, shifter/rotate, and Fblock operations added to the alu testing file

Related issues

Will close #3
Will close #22

Todo

[x] Ensure CodeCov checks show on PR
[x] Add CodeCov Enforcement at 90%
[x] Remove the test data CSV files from the repo and have them automatically generated by running the test generation scripts on push
[ ] Add Fblock tests

Codecov Report

Merging #23 (ff3f942) into main (95c7750) will increase coverage by 34.64%.
The diff coverage is 100.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@             Coverage Diff             @@
##             main      #23       +/-   ##
===========================================
+ Coverage   61.01%   95.66%   +34.64%
===========================================
  Files          13       13
  Lines        1162     1176       +14
  Branches        1        1
===========================================
+ Hits          709     1125      +416
+ Misses        453       51      -402

Files Changed
Coverage Δ

src/CPU/cpu.js
100.00% <ø> (+55.88%)
:arrow_up:

src/CPU/adder.js
100.00% <100.00%> (+32.25%)
:arrow_up:

src/CPU/alu.js
100.00% <100.00%> (+71.73%)
:arrow_up:

src/TriArithmetic/shiftRot.js
100.00% <100.00%> (+33.33%)
:arrow_up:

... and 5 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Going to go ahead and merge. Will create issue as a reminder to add FBlock operation testing, but for now, it is enough to be adding the code coverage requirements, advancing repo coverage to over 95%, and building a structure for automatically generating testing data.


Let 165 sign up form

Add sign-up form page
Testing instructions

Respects the visual design

Contains fields for: first name, last name, email, password, confirm password, accepting the terms and conditions and privacy policy (all mandatory)

The fields are validated:

required fields are not empty

email is valid

passwords match

Errors are displayed if:

the validation does not pass

the user already exists

The user’s locale is sent to the API (this is necessary to send the email verification in the correct language)

Accessible by WCAG 2.1 standards

The fields are part of a form

Input and form errors are correctly presented to assistive technologies (AT) (see this guide on form validation)

Available for translation in Spanish, Portuguese and English

Page works well on mobile devices (down to iPhone 5)

Tracking
LET-165

I forgot to add another piece of feedback: the form should be responsive. It's one of the acceptance criteria.


Remove: Google.AndroidStudio 2<IP_ADDRESS> for 2<IP_ADDRESS>

Checklist for Pull Requests

[X] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[X] Have you checked that there aren't other open pull requests for the same manifest update/change?
[X] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[X] Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Removing for:

#174517

Microsoft Reviewers: Open in CodeFlow

URL: https://redirector.gvt1.com/edgedl/android/studio/install/2<IP_ADDRESS>/android-studio-2<IP_ADDRESS>-windows.exe
OK
(Automated message - build 923)

Hi @aisgbnok,
This manifest has the highest version number for this package. Is it available from another location? (This might be in error if the version is switching from semantic to string, or string to semantic.)
(Automated response - build 896.)

@stephengillie, unfortunately this is how Google.AndroidStudio get's updated in winget-pkgs repo. Google uses MAJOR.MINOR DisplayVersion so the previous version needs to be removed from the index to free up the DisplayVersion so patches like #174517 can then go through.

Please approve this PR (#174516), then #174517 will pass validation and can be approved. Thank you.

Sorry to miss these messages for so long. I'm not sure why they didn't show up in GitHub notifications.


React dependency uses incorrect notation to allow React 17

I see in v1.0.8 that the react dependency was changed to ^16.8.0 but I believe this was done in error since the package does not support projects that use v17+. I believe this can be fixed with an easy change:
"dependencies": {
  "react": ">=16.8.0",
},
"peerDependencies": {
  "react": ">=16.8.0",
}

Let me know if you'd like me to submit a PR for this

Fixed in<EMAIL_ADDRESS>Thanks again 👍

thanks so much!


Unable to contribute as guest to Collective whose Host has only bank transfer

This was reported by a user:
I have a contributor who would like to make a contribution to our collective.
He was trying to do that without being registered with his email.
Curiously, he can not see frequency flexibility: One Time, Monthly, Yearly
He sees the same as on one of screenshots joint with the email.
Finally, on the 3rd step "Payment Info", he sees "No payment method available".
However, I already entered a bank account info to our fiscal host.
Seems like UI behaviour is different for registered users. For example, if I try to make a contribution from my personal account I see the frequency options and the payment as bank transfer.
I think I understand the issue we are facing. As for registered user we can see the frequency:

choosing "one-time", we have "bank transfer" available
choosing "monthly", we see "no payment methods available"
For non registered users, as we can not see frequency option, it seems like by default "monthly" option is taken and thus we see "no payment methods available".

I have tested this by setting up this collective under a test host with only bank account payment method active. I went through the flow once and hit the same issue as the user -  it did not give me frequency options but then said 'no payment method available'. But then I tried again and now it's working, seeming to default to one-time and showing the bank transfer option. I can't figure out what I did. But this user seems to have tested it thoroughly so I think we should investigate.

Related to https://github.com/opencollective/opencollective/issues/4669. We made some improvements in https://github.com/opencollective/opencollective-frontend/pull/7270 and https://github.com/opencollective/opencollective-frontend/pull/7271 that possibly address this, but it needs to be tested.

After reviewing this issue today, we were not able to reproduce. We need to invest more time in QA to understand properly.

Ty https://github.com/community/community/pull/28585#issue-1330778894

Closing as stale.


Set the terraform-provider-honeycombio client's UserAgent to "pulumi-honeycomb"

I'm not quite sure how to do this yet, but the TF provider has a client structure here that accepts a UserAgent field. However, none of the pulumi-tfbridge codegenerated stuff supports that, as far as I can see.
This might need a configuration variable for the tf provider, which we'd expose as a configuration thing with an appropriate default.

Seems like the client is unconditionally set to report terraform-provider-honeycombio; we'll need a configuration hook in the tf provider to set this.

I think we now set this in 0.0.11!


Laser namechange and some buffs

About the PR
Renamed all laser "guns" to make it easier to tell what they actually are
We now have laser pistols and rifles (and the "retro laser blaster" which is technically a sidearm/pistol too but blaster just sounded more on-brand for retro)
Changed the practice laser gun/rifle description because terminator reference, and the advanced laser gun/pistol's description to hint that it does higher damage than the common laser weapons
No ids were changed
Captain's pistol and Behonker Eye were reduced to size 10 as other pistols
Laser Crate now contains standard lasers instead of retro lasers
Retro lasers were buffed to the slightly higher damage of premium lasers due to their new rarity and so they are no longer exactly the same as normal laser rifles
Media

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

Changelog
:cl: Errant

tweak: The various laser guns are now called rifles or pistols.
tweak: Retro laser blasters deal more damage, but can no longer be ordered by Cargo. Standard laser rifles are available instead.

antique laser pistol
weighs 30

im fine with weight being lowered on caps laser, its high risk afterall

im fine with weight being lowered on caps laser, its high risk afterall

Ok I will lower that, should I leave the size at 30 on the advanced laser pistol, though? I assume it was only (just today) fixed to 30 from 50 because the Antique is 30, but there is valid concern that one could carry a pile of advanced laser pistols (then again that's the battery weapon you LEAST need to amass).
Should the laser pistol be parented to rifle size instead with size 50? Or leave it at 30

leave advanced at 30

The Behonker Eye is also size 30, it's essentially a faster-firing antique laser pistol but can't readily be acquired once, let alone multiple times. Should that go to 10 too?

After staring at laser rifle and retro laser blaster for a while and wondering why there are even two of these if they are completely identical, I have changed retro laser damage to the +20% prototype and replaced them with standard rifles in the orderable crate. Now retro blasters are a rare upgrade


NuxtLink Support with custom route rules

Version
<EMAIL_ADDRESS>
------------------------------
- Operating System: Darwin
- Node Version:     v20.5.1
- Nuxt Version:     3.13.2
- CLI Version:      3.13.2
- Nitro Version:    2.9.7
- Package Manager<EMAIL_ADDRESS>- Builder:          -
- User Config:      future, app, hooks, routeRules, runtimeConfig, swiper, css, components, modules, image, security, postcss, vite, extends, compatibilityDate, formkit, plausible, cookieFirst, shopware
- Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>- Build Modules:    -
------------------------------

Steps to Reproduce:

Set up custom route rules (e.g., configure specific security headers for PayPal on a checkout route).
Reload the page where the custom route rules are applied (e.g., the checkout route) and verify that the custom security headers are correctly applied.
From a different page, use <nuxt-link> to navigate internally to the page where custom route rules were set.
Upon navigating to the page via <nuxt-link>, observe that the custom security headers are no longer applied.

Expected Behavior:
Custom route rules should persist and be applied correctly, even when navigating internally via <nuxt-link>. The custom headers (e.g., for PayPal on the checkout route) should still be present, ensuring consistent security behavior.
Actual Behavior:
The custom route-specific security headers are not applied when navigating internally using <nuxt-link>. Instead, the default global nuxt-security settings are applied, overwriting/not applying the expected custom route headers.
Additional Information:

The issue seems to occur only during internal navigation using <nuxt-link>. When directly accessing the route (e.g., via a page reload), the custom headers are correctly applied.
The problem may be related to the way Nuxt handles client-side navigation and applies route-specific rules during internal transitions.

Hi @markus-gx
I was going to give you the all-frustrating "it's not a bug, it's a feature" but I do have to say it's an issue.
Unfortunately this is completely outside our control, and it all relies on Nuxt having its roots in client-side Single-Page Applications, while CSP is a server-side specification defined at page-level.
The issue that you are facing is that when you navigate on the client-side, your application is not hitting the server again. Everything happens in the browser, so the headers are not refreshed.
We have an extensive write-up about this issue in our docs here: https://nuxt-security.vercel.app/documentation/advanced/strict-csp#per-route-csp
Our recommendation is to not use routeRules for headers if you can. Instead, try to define a single policy that will cover your entire application.
If you absolutely need to enforce route-level security rules, our recommendation is to force a page-reload upon entering and leaving the specific route.
We discussed internally whether we would drop the routeRules feature and decided to keep it for some advanced use cases.
Maybe we should rewrite the docs to hide it somewhere deep in the documentation, and surround it with big warnings...

Thanks for the answer! Totally understand that - hiding is always great :P

I would be up for hiding it as well but not removing it as someone might need it. Thanks for the answer and comments! :)

@markus-gx
Would you be interested in contributing this documentation change? We can provide all help needed :)

Sure count me in ;)


Seal Ext / ImplExt traits

We should look at which traits must be sealed other then the ones mentioned in the issue title.

Here is a list of glib traits that are not sealed and not implemented by any macro:

:seal: Cast
:seal: CastNone
FromGlibContainer
FromGlibPtrContainer
:seal: InterfaceList
:seal: IntoClosureReturnValue
IntoGStr
IntoOptionalGStr
IntoPtrSlice
IntoStrV
:seal: IsSubclassableDefault
:seal: MayDowncastTo
OptionIntoGlib
:seal: PrerequisiteList
Property
PropertyGet
PropertySet
PropertySetNested
:seal: Ptr
:seal: ToSendValue
:seal: TryFromClosureReturnValue
:seal: Watchable

I put :seal: next to the ones I think should probably be sealed

Seems simple enough for gtk3: https://github.com/gtk-rs/gtk3-rs/pull/821
Now to add it to gir?

Sealing approach from that PR looks good to me. I'll look at the list of traits above next week :)

Does docs embedding works fine for those sealed traits?

Seems to work here

This is now done


⚠ Bofrost.lu has degraded performance

In 7a9d760, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 833 ms

Resolved: Bofrost.lu performance has improved in c1c856a after 6 minutes.


[HOLD for payment 2023-10-12] [$500] Request Money - The gap between error message and 'Next' button is much larger for Request Money's Manual Page

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

Action Performed:

Login to ND
Click on FAB > Request Money > Manual tab
Enter '0' if not already there in the amount
Click on Next

Expected Result:
The gap between the error messages is consistent, just like on other pages, such as Home Address, Legal Name, Date of Birth, etc
Actual Result:
The gap is much larger than the gap between error message and CTA button on any other page.
Workaround:
Unknown
Platforms:

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

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

Version Number: <IP_ADDRESS>
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

https://github.com/Expensify/App/assets/93399543/eac55810-1ef6-46c7-abe9-960df1ee862a
Expensify/Expensify Issue URL:
Issue reported by: @aman-atg
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1695942566946709
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01c93d7659514ccde7
Upwork Job ID:<PHONE_NUMBER>882224128
Last Price Increase: 2023-09-29
Automatic offers:

aman-atg | Contributor | 26975517
aman-atg | Reporter | 26975520

Proposal by: @aman-atg
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1695942566946709
Proposal
Please re-state the problem that we are trying to solve in this issue.
The gap between error message and 'Next' button is much larger for Request Money's Manual Page
What is the root cause of that problem?
We are using styles.mt5 here which works for platforms where BigNumberPad component is visible but for other platforms this much gap is unnecessary. And FormHelpMessage itself has marginBottom values which further increases the gap between the error message and the button.
What changes do you think we should make in order to solve the problem?

We can define a variable like canUseTouchScreen and use it to determine which value to use for the top margin.
Example:

                {canUseTouchScreen ? (
                    <BigNumberPad
                      // ...other props
                    />
                ) : null}
                <Button
                    // ...other props
                    style={[styles.w100, canUseTouchScreen ? styles.mt5 : styles.mt2]}
                />

Here, I've used styles.mt2 but we can use any other value as well as per design team's suggestion.
With this, the total gap between will be 12px, considering styles.mt2 from the Button and styles.mb1 from the FormHelpMessage
What alternative solutions did you explore? (Optional)
We can use various margin spacing combinations for the FormHelpMessage and Button components, such as using styles.mb0 and styles.mt3 respectively when canUseTouchScreen is false.
However, changing FormHelpMessage's style will also have an effect when canUseTouchScreen is true and BigNumberPad is visible so it needs to be validated by the design team if we choose to do so.

Proposal
Please re-state the problem that we are trying to solve in this issue.
Error message have different space in some places
What is the root cause of that problem?
Due to extra styles passed as props, we are getting this error.
What changes do you think we should make in order to solve the problem?
https://github.com/Expensify/App/blob/67d4a7acebf613dc8fac9fd1423a7a23d1583e59/src/pages/iou/steps/MoneyRequestAmountForm.js#L260-L274
Just need to replace mt5 with mt3 like this
  <Button
                    success
                    medium={isExtraSmallScreenHeight}
                    style={[styles.w100, styles.mt2]}
                    onPress={submitAndNavigateToNextPage}
                    pressOnEnter
                    text={buttonText}
                />

no need to change it with respect to devices as there is already a condition based on DeviceCapabilities.canUseTouchScreen() on top
What alternative solutions did you explore? (Optional)
N/A

Sounds good to me! @aman-atg, can you comment in this GH? It won't let me assign you otherwise 😁

Assigned!

@allroundexperts can you please respond to the above comment so that I can issue payment? Thanks!

Bump @allroundexperts I'm no longer in BZ team but should action this as it was due last week. Thanks!

Payment Summary:

For reference, here are some details about the assignees on this issue:
@aman-atg requires payment offer (Contributor)
@allroundexperts does not require payment (Eligible for Manual Requests)
@aman-atg requires payment offer (Contributor)

@aman-atg - $500 + $250 (50% bonus) + $50 (reporting bonus) = $800
@allroundexperts - $500 + $250 (50% bonus) = $750

@allroundexperts, @NicMendonca misinterpreted the internal documentation - we just clarified this internally. There's no additional bonus for reporting and fixing their own bug. They simply get paid the reporting bonus on top of what they get for fixing the bug. So $800 is the correct amount.

@aman-atg you've been paid so closing this GH.

$750 payment approved for @allroundexperts based on BZ summary.


How about supporting jsx/tsx layout?

Layouts are just vue components that require a . If you set up your vite to work with jsx there is no reason it shouldn't work.

Going to close this; if it doesn't work as @ctholho described, please provide a repo and we will see what we can do.


Services in container keeps stopping

Specifications

Image hash or version: Latest sha256:74f48478bed7b28e7e236bfe50515bac9800d0ea2132f10e41731f286c81e971
Platform: Rocky Linux 9 + Docker CE 25.0.3
Subsystem: x86_64

Expected Behavior
Services should start without stopping right after.
Actual Behavior
Services keeps stopping during container start.
Steps to Reproduce the Problem

Docker command:

docker run  --name=fr24feed  \
		--hostname=fr24feed  \
		--env=MLAT_ALTITUDE_MSL_METERS=xxx  \
		--env=FR24FEED_FR24KEY=xxx  \
		--env=PIAWARE_FEEDER_DASH_ID=xxx  \
		--env=MLAT_EXACT_LON=xxx  \
		--env=HTML_SITE_LON=xxx  \
		--env=MLAT_EXACT_LAT=xxx  \
		--env=HTML_SITE_NAME=Home  \
		--env=HTML_SITE_LAT=xxx  \
		--env=TZ=Etc/GMT+0 \
		--volume=/etc/localtime:/etc/localtime:ro  \
		--tmpfs /run:exec,size=32M \
		--tmpfs /planefinder/log:exec,size=32M \
		--tmpfs /usr/lib/fr24/public_html/data:size=32M \
		-p 8083:8080  \
		-p 8754:8754  \
		--restart=unless-stopped  \
		--device /dev/bus/usb:/dev/bus/usb  \
		--log-driver=syslog  \
		--log-opt tag={{.Name}}  \
		--log-opt syslog-address=udp://<IP_ADDRESS>:514  \
		--runtime=runc  \
		--detach=true  \
		docker.io/thomx/fr24feed-piaware:latest

Check logs:

[fr24feed] 2024-03-08 09:00:23 | [main][i]Local IP(s): xxx
[fr24feed] 2024-03-08 09:00:23 | [main][i]Copyright 2012-2023 Flightradar24 AB
[fr24feed] 2024-03-08 09:00:23 | [main][i]https://www.flightradar24.com
[fr24feed] 2024-03-08 09:00:23 | [main][i]DNS mode: PING
[fr24feed] 2024-03-08 09:00:23 | [main][i]Automatic updates are DISABLED
[fr24feed] 2024-03-08 09:00:23 | 24-03-08 09:00:23.008 [I][http-server.cpp:246] [httpd]Server started, listening on :::8754
[dump1090] rtlsdr: using device #0: Generic RTL2832U OEM (Realtek, RTL2832UHIDIR, SN 00000001)
[piaware] ****************************************************
[piaware] piaware version 9.0.1 is running, process ID 171
[piaware] your system info is: Linux fr24feed 5.14.0-362.18.1.el9_3.0.1.x86_64 #1 SMP PREEMPT_DYNAMIC Sun Feb 11 13:49:23 UTC 2024 x86_64 GNU/Linux
[fr24feed] 2024-03-08 09:00:23 | [i]PacketSenderConfiguration::fetch_config(): Yoda configuration for this receiver is disabled
[fr24feed] 2024-03-08 09:00:23 | [d]TLSConnection::ctor(): Enable verify_peer in production code!
[fr24feed] 2024-03-08 09:00:23 | [main][i]Reader thread started
[fr24feed] 2024-03-08 09:00:23 | [master][i]Starting processing thread
[fr24feed] 2024-03-08 09:00:23 | [reader][i]Initializing reader
[fr24feed] 2024-03-08 09:00:23 | [reader][i]Connecting to unknown receiver via (tcp://<IP_ADDRESS>:30005)
[fr24feed] 2024-03-08 09:00:23 | BeastBase::connectTcp(): Unable go connect, error: Connection refused[reader][e]Could not connect to tcp://<IP_ADDRESS>:30005
[fr24feed] 2024-03-08 09:00:23 | [time][i]Synchronizing time via NTP
[dump1090] Found Rafael Micro R820T tuner
[fr24feed] 2024-03-08 08:59:56 | [time][i]Time synchronized correctly, offset -26.497 seconds
[fr24feed] 2024-03-08 08:59:56 | [main][i]Feed Network client started
[fr24feed] 2024-03-08 08:59:56 | [feed][i]Downloading configuration
[fr24feed] 2024-03-08 08:59:56 | [feed][d]Fetching configuration
[fr24feed] 2024-03-08 08:59:56 | [feed][i]configuring decoder
[fr24feed] 2024-03-08 08:59:56 | [feed][c]Max range AIR: 350.0nm
[fr24feed] 2024-03-08 08:59:56 | [feed][c]Max range GND: 80.0nm
[fr24feed] 2024-03-08 08:59:56 | [feed][i]configuration changed
[fr24feed] 2024-03-08 08:59:56 | [feed][i]defined 3 servers
[fr24feed] 2024-03-08 08:59:56 | [feed][c]Timestamps: optional
[fr24feed] 2024-03-08 08:59:56 | 24-03-08 09:00:23.406 [I][receiver_ac_sender.cpp:137] Stopping ReceiverACSender threads for feed
[fr24feed] 2024-03-08 08:59:56 | 24-03-08 09:00:23.406 [D][receiver_ac_sender.cpp:141] Stop called on non-running network thread for feed
[fr24feed] 2024-03-08 08:59:56 | 24-03-08 09:00:23.406 [I][receiver_ac_sender.cpp:96] Configured ReceiverACSender: xxx:8099,xxx:8099,xxx:8099, feed: xxx, send_interval: 5s/1s, max age: 15s, send metadata: true, mode: 1, filtering: true
[fr24feed] 2024-03-08 08:59:56 | 24-03-08 09:00:23.406 [I][crxstats.cpp:588] [stats]Stats thread started
[fr24feed] 2024-03-08 08:59:56 | 24-03-08 09:00:23.406 [I][receiver_ac_sender.cpp:36] Network thread connecting to xxx:8099 for feed xxx
[fr24feed] 2024-03-08 08:59:56 | [feed][n]xxx@xxx:8099/UDP
[fr24feed] 2024-03-08 08:59:56 | [feed][n]connecting
[fr24feed] 2024-03-08 08:59:56 | [feed][n]connected via UDP (fd 23)
[fr24feed] 2024-03-08 08:59:56 | [feed][n]working
[dump1090] rtlsdr: tuner gain set to 49.6 dB (gain step 28)
[dump1090] Allocating 4 zero-copy buffers
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service radarbox: stopping
s6-rc: info: service planefinder-log: stopping
s6-rc: info: service piaware: stopping
s6-rc: info: service opensky: stopping
s6-rc: info: service netcat: stopping
s6-rc: info: service http: stopping
s6-rc: info: service fr24feed: stopping
s6-rc: info: service adsbhub: stopping
s6-rc: info: service adsbfi-mlat: stopping
s6-rc: info: service adsbexchange-stats: stopping
s6-rc: info: service adsbexchange-mlat: stopping
s6-rc: info: service planefinder-log successfully stopped
s6-rc: info: service planefinder: stopping
s6-rc: info: service http successfully stopped
s6-rc: info: service init-upintheair: stopping
s6-rc: info: service confd-layers: stopping
s6-rc: info: service confd-html: stopping
s6-rc: info: service init-upintheair successfully stopped
s6-rc: info: service confd-html successfully stopped
s6-rc: info: service radarbox successfully stopped
s6-rc: info: service conf-radarbox: stopping
s6-rc: info: service opensky successfully stopped
s6-rc: info: service conf-opensky: stopping
s6-rc: info: service piaware successfully stopped
s6-rc: info: service confd-piaware: stopping
s6-rc: info: service netcat successfully stopped
s6-rc: info: service fr24feed successfully stopped
s6-rc: info: service confd-fr24feed: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service adsbhub successfully stopped
s6-rc: info: service conf-adsbhub: stopping
s6-rc: info: service adsbfi-mlat successfully stopped
s6-rc: info: service adsbfi-feed: stopping
s6-rc: info: service adsbexchange-mlat successfully stopped
s6-rc: info: service planefinder successfully stopped
s6-rc: info: service conf-planefinder: stopping
s6-rc: info: service confd-layers successfully stopped
s6-rc: info: service conf-radarbox successfully stopped
s6-rc: info: service conf-opensky successfully stopped
s6-rc: info: service confd-piaware successfully stopped
s6-rc: info: service confd-fr24feed successfully stopped
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service conf-adsbhub successfully stopped
s6-rc: info: service adsbexchange-stats successfully stopped
s6-rc: info: service adsbexchange-feed: stopping
s6-rc: info: service conf-planefinder successfully stopped
s6-rc: info: service adsbfi-feed successfully stopped
s6-rc: info: service conf-adsbfi: stopping
s6-rc: info: service adsbexchange-feed successfully stopped
s6-rc: info: service conf-adsbexchange: stopping
s6-rc: info: service dump1090: stopping
s6-rc: info: service conf-adsbfi successfully stopped
s6-rc: info: service conf-adsbexchange successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service dump1090 successfully stopped

Is it only with the latest release or 1.30.0 is OK ?
Could you try running only one service at a time to find the culprit ? https://github.com/Thom-x/docker-fr24feed-piaware-dump1090/blob/master/README.md#common

Hi Thomas,
I'm using the 1.32.0. It seems to work as soon as I set SERVICE_ENABLE_HTTP to false.
It seems to be the same behaviour as my previous issue #107

Can you try with https://github.com/Thom-x/docker-fr24feed-piaware-dump1090/issues/107#issuecomment-1516311871 ?

It works, thank you!


Setup testing

Write unit test

For train, predict and model (i guess...)
Calculate coverage

to test models from wandb, we need a way of logging in

I have made a test that uses wandb log in with a secret repository token, so we can now do more wandb testing. Havent made logging as I didn't wanna log something in wandb everytime we push to git.


Warnings and errors about ignored packages.

Hello. I've searched around, but sadly can't find a resolution.
I am ignoring packages/files using the ignore plugin but I'm getting a warning for every import
My code:
await build({
 ...otherConfig,
 plugins: [
    ignore([
      { resourceRegExp: /Redacted/ },
   ]),
  ]
);

▲ [WARNING] Import "Redacted" will always be undefined because the file "ignore:../path/to/Redacted" has no exports [import-is-undefined]

Which is the behavior I'm expecting. How do I silence this warning? In my project this causes thousands of them.

Nevermind. Found the config:
  logOverride: {
    'import-is-undefined': 'info', // Or whatever level you want.
  },


question about def for: aplasia cutis myopia'

This term is in gard_rare subset: MONDO_0021910 aplasia cutis myopia and lacks a text def, but this term is in Orphanet: http://www.orpha.net/consor/cgi-bin/OC_Exp.php?lng=EN&Expert=1117
Should I add a text def and xref to Orphanet, or will this be done on the import?

this def and xref are on 'aplasia cutis-myopia syndrome'.
these terms should be merged.


statusCode=

This is my event. statusCode="closed". But no 'endTime' in event
"messagegenerator.py line 65, in get_message_for_slack" should be modified.

Can I fix this?


Bump @huggingface/jinja to v0.3.0

This is a PR relating to this issue, which is a request for an upgrade to Jinja v0.3.0

Closing, as this the requested feature was implemented in @huggingface/transformers v0.3.0


Filter responses based on content-type

Idea was proposed by Pablo in https://github.com/scrapinghub/splash/issues/68#issuecomment-32474061.

Fixed by #225 and #246.


Broken pipe trying to run the PPO example

So I tried running
python -m retro.examples.ppo --game Airstriker-Genesis, and it gave me a broken pipe. What can I do to fix this?
found here: https://retro.readthedocs.io/en/latest/getting_started.html

System information

Operating system: windows
Python version :3.7
Gym Retro version: 0.7

What version of tensorflow do you have installed?  The docs for baselines say you need 1.4 to 1.14: https://github.com/openai/baselines#tensorflow-versions

I see, thanks for the help man


'Run Symbol Organizer' crashes upon initiating command

Sketch Version 54.1

Probably a duplicate to #124


2.2.1 is not tagged in git and versions >2.2.0 are not listed on your homepage

Just to let you know, in Drupal 8 we use version 2.2.1 of picturefill, but there is no git tag for this release.
Could you tag this? Or alternatively could you explain how 2.3.0 differs from 2.2.1?
Lastly just to clarify, is there a reason 2.2.1/2.3.0 are not listed on your homepage (http://scottjehl.github.com/picturefill/)

Hey @stefanruijsenaars, thanks for reporting this!
I think 2.2.1 was short-lived as 2.3.0 was scheduled for an imminent release. I've created two pull requests to update the site to reflect that 2.3.0 is the recommended stable version.
2.3.0 fixes a range of bugs and has some performance improvements, as well as adding support for newer image formats, intrinsic image dimensions, and commonJS exports. More details here: https://github.com/scottjehl/picturefill/releases
Basically, we heartily recommend you upgrade to 2.3.0. It's the bee's knees. 🐝

Thanks!


Local Functions Not Working with Node 17+

Describe the bug
When running netlify dev, local functions are not accessible on port 8888 when using Node.js version 17.
To Reproduce
Steps to reproduce the behavior:

Create a new hello world function inside of a functions directory
Install Node.js 17+
Run netlify dev in the project and try to access in the browser at http://localhost:8888/.netlify/functions/helloWorld

Expected behavior
Should return back hello world from the browser.

Check out #3617. The issue has been reported for different frameworks. Had the same issue after updating to Node.js 17+. Going back to an older version of Node solved the issue for now.


[spike] Choose CSS framework that easily integrates with project

We're already using mdb vue for some components, and after having a look at what they offer - it seems to meet our requirements.


Revert "Revert "WFLY-5489 Fix and and add missing transformations for…

… EAP in modcluster subsystem""
This reverts commit df351c859609841f8837144d016e4f1cee7070ca.
Resubmit of https://github.com/wildfly/wildfly/pull/8250 which was accidentally merged.
Jira
https://issues.jboss.org/browse/WFLY-5489
adds eap transformer + rejection tests
splits single test file into parsing and transformation tests
cleanup xml files used for tests

@kabir I'll leave this one to you since you were familiar with #8250


Angry Birds Trilogy [PCSE00322]

App summary

App name: Angry Birds Trilogy
App serial: PCSE00322
App version: 1.00

Vita3K summary

Version: v0.1
Build number: 1827
Commit hash: https://github.com/Vita3K/Vita3K/commit/0f2aabb900ddd27078df540bfe8f1d177ff0445d

Test environment summary

Tested by: Arnold Secret
OS: Windows 10
CPU: Intel Core i7-4500U
GPU: NVIDIA Geforce GT 740M
RAM: 8 GB

Issues
Shows seizure warning and a bit of glitched graphics before it's stuck on black screen.
Screenshots

Log
vita3k.log

Vita3K v0.1.5 2601-f803e615
goes ingame now
graphics are glitchy
gameplay is slow
music is static
vita3k.log

FPS Seams Better On My PC though bad slow and audio its okay for a early emulator

Download link

Attached this, it looks better than it used to be and the audio and FPS is fixed

Download link

Download link to what?

as of https://github.com/Vita3K/Vita3K/commit/0b48dc9b2794a167150f2e438e8d917d21bd99b3, the game's graphical bugs is fixed although there's still some graphical glitches but they only is noticeable in the menus and less noticeable in-game. Audio is fixed as well.
Screenshots

Log
vita3k.log
Recommended Labels

Playable
audio quality

For Some reason why try to play it and star wars version it keeps crashing did I do something wrong?

On android the game always crashed after playing 2 level, how can I fix this?

Download link

Download link to what?
The download link to the game, of course


Allow Azure client to set linked work item

This PR adds the ability to link work items when create a pull request in Azure DevOps.
The API is pretty forgiving, and allows the JSON "workItemRefs": [{"id": null}]
API docs: https://docs.microsoft.com/en-us/rest/api/azure/devops/git/pull requests/create?view=azure-devops-rest-5.0

Hi @jurre, another PR for you to review :smile:


registry/storage: buffered wrapper for fileWriter

Resolves https://github.com/docker/distribution/issues/148
Tests included to confirm buffer is working. Cover all new code except the inside of some err conditionals.
I believe the only place bfw.Close needed to be added was in LayerUpload.Finish

Still tracking down users of fileWriter (and now bufferedFileWriter) to add Flush/Close calls.

You're going to be looking for instances of LayerUpload.

This looks functionally correct. Test this by commenting out ReaderFrom on Layer interface and ensure that performance doesn't drop. Ask @BrianBland for confirmation on fix.

Benchmarks now included that demonstrate ~5x speedup (on my hardware) from the buffered version. The 2 benchmarks instantiate the fileWriter and bufferedFileWriter respectively, then attempt to write 100MB in 1MB segments, and finally close the writer. The benchmark timer is stopped and started such as to only time the Write calls.

LGTM!
Great job!

LGTM!


Town Commands not functioning

/t info shows no permission even with husktowns.player, only works for those with administrator perms
/t invite shows error_invalid_subcommand and only works with /invite
Only appeared after upgrade to HuskTowns 1.8

For reference @WiIIiam278 the /t invite isnt even shown in /t help like its not registering properly.

/t invite should be a shortcut command -- and it looks like I just forgot to add it.
https://github.com/WiIIiam278/HuskTowns/blob/75068f986ca9a7cc89e51bc8d469a3da0ac9c9f1/bukkit/src/main/java/net/william278/husktowns/command/TownCommand.java#L67-L78
Should be an easy fix.
As for the permission issue with /t info, that's caused by the husktowns.player node, which ultimately references husktowns.commands.town.* not containing husktowns.command.town.info
https://github.com/WiIIiam278/HuskTowns/blob/75068f986ca9a7cc89e51bc8d469a3da0ac9c9f1/bukkit/src/main/resources/plugin.yml#L184-L201
Also should be an easy fix when I have a sec, or feel free to PR.


Rename the Info proto to Description

Description
Rename the Info proto message to Description in the hopes that it's a bite better of a name.

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[x] Targeted PR against correct branch (see CONTRIBUTING.md)
[x] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Wrote unit and integration tests n/a - just a data structure name change.
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[x] Added relevant godoc comments.
[x] Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
[x] Re-reviewed Files changed in the Github PR explorer
[ ] Review Codecov Report in the comment section below once CI passes

Codecov Report

Merging #77 (6dde7fb) into main (248461e) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #77   +/-   ##
=======================================
  Coverage   32.40%   32.40%
=======================================
  Files          87       87
  Lines        5536     5536
=======================================
  Hits         1794     1794
  Misses       3500     3500
  Partials      242      242

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 248461e...6dde7fb. Read the comment docs.


Changes that are needed to slipping

Description

[] A cooldown that begins just as an item is placed down so you don’t slip while walking by
[] You need to move a minimum distance while running to slip
[] A percentage chance to drop the item in your hand instead of being 100% of the time

This is to make slipping less harsh, especially for people with high ping
Additional context

Further discussion on the discord can be seen here:
https://discord.com/channels/310555209753690112/770682801607278632/1239405469911744583

I was wondering, does walking have to cut our speed down to 50% or it would be fine to simply make it reduce down to slip speed(75% or less is safe to walk if not lube), that way antags engaging in loud slip warfare do not have such opressive home turf advantage as magboots are not that much different to walking anymore, unless its the dreaded lube of course.

i dont think any of these changes are agreed upon enough that we need an issue for it


 The same is of course true when changing TFM to simply net7.0 or similar.
After some project.assets.json detective work, I figured out why:
https://github.com/dotnet/reactive/blob/85f1eb7c53e27cccdbeee3e0b044916168843fcc/Rx.NET/Source/src/System.Reactive/System.Reactive.csproj#L3-L21
As you can see, System.Reactive is multitargeted for net5.0 and net5.0-windows10.0.19041, with the latter TFM pulling in all of WPF/SWF. 🤦
In an ideal world, the fix here would be for System.Reactive to not assume that a windows TFM necessarily implies UseWPF=true and UseWindowsForms=true. But judging by this upstream issue, it doesn't seem like anything is likely to change here anytime soon, despite this assumption being obviously wrong. I'm not sure what, if anything, can be done on the Avalonia side.

Yes, that's a problem with the System.Reactive, and we can't do much about it, unfortunately.
Developers can exclude some references from being copied to the output directory, something like <Reference Exclude="PresentationFramework.dll" />, but that isn't really user friendly.
The best I can advice - make more noise in the System.Reactive repository, bringing up seriousness of this problem.

Or we might actually try to remove this dependency at all. I will try and see this week. Hopefully, it won't affect any public API.

Well, we use ISubject in the public API unfortunately. It should be considered when bindings API cleanup is done: https://github.com/AvaloniaUI/Avalonia/issues/9512.

@idg10 it could work, yes. But as for now, there is very little need for System.Reactive in the framework itself. As we mostly have custom IObservable implementations, and only had to reimplement a small surface of observable extensions: https://github.com/AvaloniaUI/Avalonia/blob/master/src/Avalonia.Base/Reactive/Observable.cs.
Not to mention, size improvements we got by avoiding additional dependencies. I am afraid, we don't see reasons for us to add System.Reactive as a dependency back. Except maybe only for user code, or part of our templates.


NSelect: empty options menu when theme common > heightMedium is "2.5rem"

TuSimple/naive-ui version (版本)
2.33.4
Vue version (Vue 版本)
3.2.40
Browser and its version (浏览器及其版本)
Chrome/<IP_ADDRESS>
System and its version (系统及其版本)
Archlinux
Node version (Node 版本)
Reappearance link (重现链接)
https://www.naiveui.com/en-US/light/components/select
Reappearance steps (重现步骤)
Open theme editor, expand "Common" section and fill heightMedium with 2.5rem.
Try to open any NSelect menu
Expected results (期望的结果)
NSelect menu present options
Actual results (实际的结果)
NSelect menu is empty (at least it seems empty):

Remarks (补充说明)

Rem is expected to not work in virtual list. If you must use it you need to set virtual-scroll to false.

Good to know, thanks.


Pass subnets into metrics stack, fixes #42

Previously the created VPC or specified existing subnets weren't being passed down to the metrics stack, leading to failures like #42.

Ah nice! If you're looking for someone to test @ryanbigg may be able to for us!

I'll give this a go now :)

I uploaded the template to AWS using their upload functionality, entered all the details and now I get this error when I try to create the stack:

Apologies, this is still WIP, but I'm close.

@radar you'll need to use make create-stack and have a config.json if you are doing it from the console.

Ah sorry, that was my fault @radar - I got too excited about the fix :)


refactor: Chainable -> Node

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)

There's also a small fix: find_if_bodies wasn't returning valid Nodes. Now it is.

Thanks for catching that, I'll do that in a followup.

I want the record to show I suggested many better names (e.g. Pasty)

:pie:


limit the concurrency of integration test

the integration test will run in parallel and not stable now. we should limit the concurrency of the test execution.

Closes since #1796 has been merged.


Error during compilation

Hi,
I tried to compile newest version, but I'm getting the following error:
make[2]: *** No rule to make target '../assets/webconfig/lang/de.json', needed by 'libsrc/webconfig/qrc_WebConfig.cpp'.  Stop.
CMakeFiles/Makefile2:1297: recipe for target 'libsrc/webconfig/CMakeFiles/webconfig.dir/all' failed
make[1]: *** [libsrc/webconfig/CMakeFiles/webconfig.dir/all] Error 2
Any help would be highly appreciated :)

I had this - I can't remember if rerunning cmake  fixed it or blowing the build for away fixed it

cd build
rm *.qrc

that worked
thanks!


hoodie.account.signUp should sign out any existing session

Currently it gives you an error, but I don't really see why you'd want it to do anything other than sign-up and login as the new user.

no longer relevant with new Hoodie, as hoodie.account.signUp() does no longer sign in the user automatically, hoodie.account.signIn() has to be called separately


Project isn't compatible with .NET Framework that uses C# 7.3

In Messenger.cs, this line has a problem.
https://github.com/BlueMystical/Dark-Mode-Forms/blob/48e6c57b186227a04f7da6b123e592a4c6c6d04c/Messenger.cs#L21
Visual Studio reports that nullable reference types is available above C# 8.0 which is higher version that .NET Framework uses(C# 7.3).
Thus, that line should be changed to be like this:
private static Action<object, ValidateEventArgs> ValidateControlsHandler;

Here are other lines that uses nullable reference types.
https://github.com/BlueMystical/Dark-Mode-Forms/blob/48e6c57b186227a04f7da6b123e592a4c6c6d04c/DarkModeCS.cs#L393
https://github.com/BlueMystical/Dark-Mode-Forms/blob/48e6c57b186227a04f7da6b123e592a4c6c6d04c/DarkModeCS.cs#L562

This suggestion is irrelevant to this issue.
Since Messenger.cs depends on FlatComboBox.cs, shouldn't FlatComboBox.cs be put at the same level of Messenger.cs?
https://github.com/BlueMystical/Dark-Mode-Forms/blob/48e6c57b186227a04f7da6b123e592a4c6c6d04c/Messenger.cs#L715
DarkModeCS.cs also depends on FlatTabControl.cs, but since it is inside of if statement, I think it is fine.
https://github.com/BlueMystical/Dark-Mode-Forms/blob/48e6c57b186227a04f7da6b123e592a4c6c6d04c/DarkModeCS.cs#L373

i'm gonna need to test this out.


Laravel Pennant performance spans & breadcrumbs

Laravel Pennant is a new feature flagging library for Laravel.
There are currently two events dispatched, FeatureRetrieved and FeatureResolved.
We could try contributing new FeatureRetrieve and FeatureResolve events upstream, or use decorators, so we are able to wrap the code or DB query executed into a span, containing the feature identifier and result.

@cleptric I’m happy to create the code and PR for this if you would like?

@martinbean Hey, thanks a lot!
In order to create meaningful spans & breadcrumbs, we would need new events added to pennant, that fire before a feature is retrieved, see https://github.com/laravel/pennant/issues/41.

@cleptric Why would Sentry need an event before a feature is retrieved? Would you not want to add a breadcrumb after a feature and its value has been resolved?

We already trace all DB queries related to retrieving a feature, so the only addition here would be to wrap these queries into a new span and create a breadcrumb before the DB queries are run. This is mostly about better UX in the product.

In addition to @cleptric their comments, having an event before & after means we know when the framework started and finished resolving the feature flag, meaning we know how long it took and which (if any) database queries or other expensive operations took place while resolving the flag. This gives much insights in the timing. So for just breadcrumbs the "after" is enough but for the performance spans the "before" is a must.

We can revisit this once we have the required events implemented in Pennant or other metadata available that tells us how long it took to resolve a feature.


What about scaffolding database stored procedures and functions - especially table-functions

I've read the article about scaffolding entities from the database and while it sure seems useful, why dont include stored procedures and functions? I mainly interact with our database through functions and stored procedures because when entering data those need to be cross checked and validated. How do I include those? Also I may add .. not being able to use edmx diagrams is a huge drawback.

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

ID: e1601c3e-3f29-5d84-6350-2b38eeaf6adc
Version Independent ID: 92a856d6-c5da-e215-46ac-d67c411f3ff9
Content: Reverse Engineering - EF Core
Content Source: entity-framework/core/managing-schemas/scaffolding.md
Product: entity-framework
Technology: entity-framework-core
GitHub Login: @bricelam
Microsoft Alias: avickers

@eagle275 EF Core Power Tools allows you to reverse engineer stored procedures and functions.


Refactoring Attribute class.

Attribute class currently describes all attributes :

the ones used for WriteAttribute Request
the ones used in Discover response and Register request.

But currently in the code, Attribute/AttributeSet is only used for WriteAttribute Request.
So we need to either :
1.1) use those classes for all use cases.
1.2) ensure that only valid (writable?) attribute is used on WriteAttribute Request.
Or
2) Limit the scope of Attribute/AttributeSet to WriteAttribute Request.

With #1197, LwM2mAttribute (which was Attribute) is now used for WriteAttribute / Discover and Register request.
Lot of validation was added (I hope this will not frustrate too many old devices :grimacing:)


Enable ALT + RMB to list select only on the select tool matching 2D and tooltips

Fixes: #87924

I'd say that matching the existing (and seemingly old) behaviour with the tooltip is the wrong way to go, I'd say the tooltips should be improved instead

Superseded by #87989.


JExcel ISSUE in POPUP Window | Edge Browser

Hi Team,
We are trying to open the JExcel in the popup window, its working perfectly in chrome, Firefox.
Eg:  window.open(windowURL, windowId,'height=' + ((screen.height/100)*75) + ',width=' + ((screen.width/100)*75) + ',resizable=yes,scrollbars=yes,toolbar=yes,menubar=yes,location=yes');
But in edge browser, it's failing when I open for the second time and it's failing with the below error.
Opening second time causes:: The remote server machine does not exist or is unavailable jexcel.js (1550,24).
Lib Used

Regards,
Khuthbudin T.
<EMAIL_ADDRESS>

I am not sure, but I would say try to follow one of the examples in the website or create a jsfiddle with the code you have problems.


How to deploy Production mode on Mac

I tried to run Huginn inside Docker but it's using too much memory and decided to run in natively on my Mac. I managed to install and run Huginn in development mode on my Mac Mini (OS X El Capitan) by following the instruction on this page: Novice Setup Guide for Mac
To run in production mode, I tried to roughly follow this guide but it seems that the source code contain a hardcoded path for the working directory pointing to /home/huginn/huginn.
Is it possible to run Huginn on production mode on Mac? And does production mode use less memory than development mode?

Hi @mdazmir,
I don't think running in production mode will reduce the RAM usage by a lot. You can try it by switching your local development to production like this:
Add these to your .env file:
RAILS_SERVE_STATIC_FILES=true
RAILS_ENV=production

Bundle to remove the unneeded development and test gems.
RAILS_ENV=production bundle install

Precompile the assets
bundle exec rake assets:precompile RAILS_ENV=production

then (re)start foreman.


Performance improvement to the csharp kernel language services

Partially fixes #1391
The performance of the language services (RequestCompletions, RequestDiagnostics, etc.) for the C# kernel degrades the more submission the kernel receives. This causes the kernel to be almost unusable after a while because it becomes so slow.
The performance degradation is caused because of the way the language services are implemented. Normally, when you do any language service request (eg. CompletionService.GetCompletionsAsync) on the current solution, the solution would cache some information like the compilation of the projects on that solution. The problem is that each time the C# kernel ask a language service question, it forks the current solution (InteractiveWorkspace.ForkDocumentForLanguageServices). Therefore, the cached information is discarded at the end of language service question request.
The changes in this PR forces the creation of a compilation object every time code is submitted, so the language service doesn't need to create a new compilation for the entire project each time a language service question is asked.
Disclaimer: this is my first pull request on GitHub, so let me know if did anything incorrectly.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: Lawlzee sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


onFileRemoved callback

Hi!
I have enjoyed using this file picker but ran into some issues with wanting to do things when a file is removed.
Would it be possible to add an onFileRemoved callback that allows us to specify what happens when we remove a file by index or by reference?
Thank you!

Hi @dianeshan,
There already is a function called onFileRemoved that is used in useImperativeFilePicker. However, I see now that I forgot to add it as a prop to the hook, so I'll add that in the next release.
If you're really on a clock and need this feature right now, you can hook to it by creating a custom validator and adding your logic there:
https://github.com/Jaaneek/useFilePicker#custom-validation
onFileRemoved is available since v2.0.
Example:
import { Validator } from "use-file-picker/validators";
import { useImperativeFilePicker } from "use-file-picker";

class OnFileRemovedCallback extends Validator {
  validateBeforeParsing(
    _config: UseFilePickerConfig<any>,
    _plainFiles: File[]
  ): Promise<void> {
    return Promise.resolve();
  }

  validateAfterParsing(
    _config: UseFilePickerConfig<any>,
    _file: FileWithPath,
    _reader: FileReader
  ): Promise<void> {
    return Promise.resolve();
  }

  onFileRemoved(removedIndex: number): void | Promise<void> {
    // add your logic here
  }
}

function App() {
 const {
    openFilePicker,
    errors,
    plainFiles,
    filesContent,
    removeFileByIndex,
  } = useImperativeFilePicker({
    validators: [
      new OnFileRemovedCallback(),
    ],
  });
  ...
}

There's currently no distinction if the file was removed by reference or by index, it always gets the index of a removed file in the files array. If you want, we can add a reference to the deleted file as a second argument.

Hi! Thank you so much for getting back to me so quickly! I do think adding a reference to the deleted file as a second argument would be good too.
Also do you have an estimate of when the next release will be?

I've just created a PR #80, I'm waiting for an approval from the co-author @Jaaneek. When he approves, I'll release a version 2.1.0. It shouldn't take long, like a few days at max.

PR has been quickly approved, I've just released version 2.1.0! I'm closing this issue for now, but feel free to comment.

Thank you very much! I think it would also actually be helpful to have another argument that is the result of filesContent when the file is removed. So we can do something with what is leftover after we remove a file.


Stop running everything through serde

We could probably save considerable codegen/compile time by only running the code that deals with JSON through serde.  Right now everything gets that step.

Some numbers from my desktop Linux machine with Rust 1.14.0:
serde_generate took 174ms for marketplacecommerceanalytics
serde_generate took 625ms for acm
serde_generate took 742ms for cloudwatch
serde_generate took 781ms for dynamodbstreams
serde_generate took 684ms for sqs
serde_generate took 683ms for workspaces
serde_generate took 791ms for events
serde_generate took 890ms for cloudhsm
serde_generate took 1111ms for cloudformation
serde_generate took 1060ms for ecr
serde_generate took 1205ms for cognito-identity
serde_generate took 1357ms for codecommit
serde_generate took 1233ms for directconnect
serde_generate took 1233ms for firehose
serde_generate took 1272ms for logs
serde_generate took 1344ms for cloudtrail
serde_generate took 1267ms for route53domains
serde_generate took 1522ms for ds
serde_generate took 1399ms for kms
serde_generate took 1538ms for config
serde_generate took 1498ms for kinesis
serde_generate took 1517ms for ssm
serde_generate took 1725ms for datapipeline
serde_generate took 1888ms for codepipeline
serde_generate took 1720ms for inspector
serde_generate took 1837ms for ecs
serde_generate took 1804ms for elastictranscoder
serde_generate took 1945ms for devicefarm
serde_generate took 1864ms for iot
serde_generate took 1954ms for dynamodb
serde_generate took 1961ms for emr
serde_generate took 2051ms for codedeploy
serde_generate took 1914ms for waf
serde_generate took 1944ms for s3
serde_generate took 2008ms for machinelearning
serde_generate took 2031ms for opsworks
serde_generate took 1966ms for iam
serde_generate took 2134ms for storagegateway
serde_generate took 2116ms for swf
serde_generate took 1763ms for ec2

Numbers from making a small code change to pub fn generate in codegen/src/lib.rs:
let sw = Stopwatch::start_new();
serde_generate(botocore_destination_path.as_path(),
   serde_destination_path.as_path());
println!("\nserde_generate took {}ms for {}\n", sw.elapsed_ms(), service.name);

@adimarco is this completed in https://github.com/rusoto/rusoto/pull/541 ?

Ayuh.


App crashes if a different documentsui package name is used on system.

Description
Some firmware uses a different package name for the files app.
Namely com.android.documentsui instead of com.google.android.documentsui.
Trying to find such an application causes the app to crash on startup.
09-04 23:48:01.714 E/AndroidRuntime(32063): Caused by: android.content.pm.PackageManager$NameNotFoundException: com.google.android.documentsui
Solution
Use additional check with a different package name.

Thanks for the report, with https://github.com/aliernfrog/lac-tool/commit/c945f1040c2b728a36c94223d92d522642753b41, the app should now check for com.android.documentsui if the other one fails, and skip the check if com.android.documentsui also fails.
Can you try and check if picking files/folders work fine with the latest commit? You can get the build from artifacts: https://github.com/aliernfrog/lac-tool/actions/runs/10715440236/artifacts/1894818410

Thanks for the report, with the fix/documentsui branch, the app should now check for both com.google.android.documentsui and com.android.documentsui, if both those checks fail it simply skips the files app restrictions check.
Can you try and check if picking files/folders work fine with this fix? You can get the build from artifacts: https://github.com/aliernfrog/lac-tool/actions/runs/10725127525/artifacts/1897540829

Great! App works great now, both normally and with shizuku.

Thanks for testing, will release a new version shortly.


Issue with k8s.io/docs/tutorials/kubernetes-basics/expose-intro/

This is a...

[ ] Feature Request
[x] Bug Report

Problem:
this module assumes that reader knows what a "selector" is and doesn't flow as well as previous modules
Proposed Solution:
have a module 3.5 to teach new concepts used in module 4
Page to Update:
https://kubernetes.io/...

/reopen


A Simpler Configuration for Searing Spotlights

Hi,
I absolutely love this benchmark and I'm planning to use this in a paper I am writing.
I had a question regarding the Searing Spotlights environments. The other two environments, Mortar Mayhem and Mystery Path seems to be solvable by current memory based agents by providing dense reward signals or through grid like movements. However, there was no simpler configuration listed for Searing Spotlights. Is there a configuration available for Searing Spotlights available where a memory-based agent could achieve a decent level performance (which a memory-less agent wouldn't)?
My goal is to use these environments to compare the memory capabilities of different architectures. In Mystery Path and Mortar Mayhem I am able to do so with the simpler variations of these environments. The differences in performance between different memory agents are becoming apparent. But in Searing Spotlights, it seems none of the agents even get to a point where they can leverage their memory, and all agents seem to perform the same. Is there a way to make this environment easier?

Hi @subho406,
Great to hear that you enjoy this project!
Searing Spotlights is a tricky one. In the ICLR paper, the recurrent PPO agent was unsuccessful even under ground truth. The good news is, I finally found the culprit for failing at this task. Normalizing the advantages, as part of PPO's objective, makes training highly unstable. If you are training a PPO agent, don't normalize advantages.
Another aid to the agent is to add a reconstruction loss to the agent. This way, the agent needs to adopt an autoencoder target by reconstructing the fed observation.
Concerning simplifying Searing Spotlights, I can't think of any suitable simplification that would maintain the memory dependence as well as the task itself.
Here is a website showing multiple agent behaviors on all environments:
https://marcometer.github.io/
The website is still being developed, and a related journal paper is also in progress. I hope to have it ready in two weeks.

I'm closing this now. Let me know if you have further questions.
The mentioned journal paper is finally available as preprint.
https://arxiv.org/abs/2309.17207


The last four digits of the excessively long orderId were incorrectly rounded.

const { USDMClient, DefaultLogger} = require('binance');
const param = {
  symbol:'ETHUSDT',
  side:'SELL,
  quantity:1,
  type:'LIMIT',
  price:1850,
  timeInForce:'GTC'
}
const order = await client.submitNewOrder(param);
console.log(order);

The returned orderId should be a number like<PHONE_NUMBER>825190229, but the current returned orderId has its last three digits rounded, resulting in<PHONE_NUMBER>825190000.
The orderId for some trading pairs may exceed the maximum integer value that JavaScript's built-in Number type can accurately represent. It is necessary to use the string type or BigInt instead of the Number type.
https://github.com/tiagosiebler/binance/blob/6476fcf365f9c00325d2c070e71efe8a14703241/src/types/futures.ts#L407C19-L407C19

Totally agree this should be a string type. Unfortunately the JSON returned by binance's API is using a number type for this property.
There's no simple fix for the order ID value without pre-processing the JSON response before attempting to parse it into an object:
https://binance-docs.github.io/apidocs/futures/en/#new-order-trade
The suggested workaround commonly used by others, is to instead use a custom order ID before sending the order, and using that for tracking instead - take a look at this thread:
https://github.com/tiagosiebler/binance/issues/208#issuecomment-1128681717

Using custom order ID can be a compromise solution. Thank you very much.


[Proposal] Simplify SAE IDs for Gemma Scope Canonical SAEs

Proposal
Inotice that in
from sae_lens import SAE  # pip install sae-lens

sae, cfg_dict, sparsity = SAE.from_pretrained(
    release = "gemma-scope-2b-pt-res-canonical",
    sae_id = "layer_0/width_16k/canonical",
)

canonical in the sae_id is redundant and I suggest removing.
(I skipped the rest of the issue boilerplate)

My personal vibe is this could introduce confusion this late in the game and that leaving it as is isn't terrible.

Seems completely reasonable 👍


Stop indexing v2.0.0 in search

I've excluded all urls matching /docs/2.0.0/ from the indexing, so
those docs should not be displayed in the searchbar.

Sorry, bad merge. I'll reopen a new one.


research robot karol resources

the handbook is still one of the best references

otherwise, most content is about rebuilding specifiy levels


prepare release 0.31.0

cc @baszalmstra looking at the changes I had to made I was wondering if there should be a constructor for Channel::from_url that takes a ChannelUrl?
Can you check that the usage of ChannelUrl makes sense?
Also I am enabling sharded, because, why not!?

@hadim anything else you need?! :) I updated rattler.

All good thanks!

@wolfv Do you think we should always serialize the URL without the trailing slash?

https://github.com/baszalmstra/rattler/pull/new/feat/expose_url_without_trailing_slash

https://github.com/conda/rattler/pull/948

@baszalmstra works for me. I'll be waiting for one more rattler release then. It'll probably make things more rebuildable as well :)

Just created a new release that contains https://github.com/conda/rattler/pull/948


How to add new source of data?

I have a source of live data I connect to through websockets. I have the python program that connects and starts streaming the data, but I am unsure on the best way to connect it to qstrader. I want the data to be passed live to qstrader as an event, but also for the data to be logged into a database for future testing.
So I would appreciate any direction or even better examples on the best way to proceed. I am unsure if it would be better to integrate the code as a qstrader module (the network part of the data source code runs on a different thread and the info pops into the main thread with a callback so it should be alright) or to run it as its own daemon and send the data to qstrader through a localhost socket or even using a message broker.
Any advice from someone that has tried it or has experience with qstrader structure would be apreciated.

Hey @subiol, sorry this hasn't been replied to yet.
I suggest having a look at the Yahoo PriceHandler for inspiration. You'll have to create your own PriceHandler module which extends from the same base class and provides the same external-facing methods.
Basically, as long as the rest of QSTrader can call the methods that you can see in the Yahoo PriceHandler, you can do literally whatever you like.
Use cases like this are, I think, a good showcase of how easy extending qstrader is. We just totally lack any documentation at the moment as it's still pretty early stages.
Let us know how you go

Hi @ryankennedyio, I assume you mean this?
YahooDailyCsvBarPriceHandler(AbstractBarPriceHandler)
I am using a securities database, so I'd like to grab it from MySQL


feat: Support testnet

Revamp configuration to pass NETWORK env variable from command line (both for
taker and maker).
In case it's not set, or it's invalid, it defaults to testnet.
Move all the config values to a dedicated module to clear the code.
For local development, I recommend to set export NETWORK=regtest in your
bashrc to preserve previous behaviour.

bors r+

resolves #336


Typescript 5.1.3 type issue

Hi! 👋
Firstly, thanks for your work on this project! 🙂
Today I used patch-package to patch<EMAIL_ADDRESS>for the project I'm working on.

Here is the diff that solved my problem:
diff --git a/node_modules/react-native-svg/src/lib/extract/extractTransform.ts b/node_modules/react-native-svg/src/lib/extract/extractTransform.ts
index 3961868..1792413 100644
--- a/node_modules/react-native-svg/src/lib/extract/extractTransform.ts
+++ b/node_modules/react-native-svg/src/lib/extract/extractTransform.ts
@@ -68,17 +68,19 @@ export function transformsArrayToProps(
   transformObjectsArray: TransformsStyle['transform'],
 ) {
   const props: TransformProps = {};
-  transformObjectsArray?.forEach((transformObject) => {
-    const keys = Object.keys(transformObject);
-    if (keys.length !== 1) {
-      console.error(
-        'You must specify exactly one property per transform object.',
-      );
-    }
-    const key = keys[0] as keyof TransformProps;
-    const value = transformObject[key as keyof typeof transformObject];
-    props[key] = value;
-  });
+  if(Array.isArray(transformObjectsArray)) {
+    transformObjectsArray?.forEach((transformObject) => {
+      const keys = Object.keys(transformObject);
+      if (keys.length !== 1) {
+        console.error(
+          'You must specify exactly one property per transform object.',
+        );
+      }
+      const key = keys[0] as keyof TransformProps;
+      const value = transformObject[key as keyof typeof transformObject];
+      props[key] = value;
+    });
+  }
   return props;
 }

This issue body was partially generated by patch-package.

Just hit this exact issue as well. It seems from React Native 0.71.9, string is added to TransformsStyle['transform'] which breaks the function above.
However, it seems to me that the logic here is somewhat broken outside this function:
export function props2transform(
  props: TransformProps | undefined,
): TransformedProps | null {
  if (!props) {
    return null;
  }
  const extractedProps = Array.isArray(props)
    ? transformsArrayToProps(props)
    : props;
 ...

TransformProps is an object and will never be true for Array.isArray(props).
It is used in transformToMatrix though, where the usage is properly type scoped.

Still seeing this issue on the latest.

This hasn't been released yet so that might be the cause of it. Or are you using version from main @mankybansal ?

Oh whoops, didn't see there hasn't been a release yet. Is there an ETA for the next release?

Not really, but I think I'll do it next week. Is it alright?

@WoLewicki, can you release this?


[DDW-197] create flex layout component

This PR adds layout components Flex and FlexItem. This abstracts layout into composable, compound components that facilitate a more uniform and reusable layout solution. Enables third party developers using react-polymorph to craft applications with uniformity of layout specs and style more easily with most of the Flexbox API.

@MarcusHurney i will still merge this PR since the problem with withTheme helper hasn't been introduce here but much earlier and should be fixed in a separate work stream.


Match ex-command does not work with visual or visual block selection

Steps to reproduce

vim -u NONE
enter arbitrary multi line text sample in the buffer
visual select or visual block select some text
type :'<,'>match Search /existing-valid-pattern/
command produces invalid range error e16

Expected behaviour
Visual match must also be supported. Note that normal range match works just fine, like that 1,2match Group /pattern/ - which respects the match range correctly
Version of Vim
9.0
Environment
Ubuntu / WSL
Logs and stack traces
VIM - Vi IMproved 9.0 (2022 Jun 28, compiled Jun 23 2023 15:15:13)
Included patches: 1-1650
Compiled by Homebrew
Huge version without GUI.   Besides, what exactly should the range specify? Match by itself does not work on the current line, but finds the next search pattern (anywhere in the buffer) and highlights so restricting it by a range doesn't really make sense.

Yeah, seems like even with regular line numbers the range does apply over the entire buffer, i had misunderstood the match command then, having expected us to be able to restrict the matching scope. Are there any alternatives to doing that? What i am trying to do is implement a substitute like interactive highlight of a pattern within a range.

Seems like i have misinterpreted what match is supposed to do. What i was trying to do was to incrementally match a pattern in the buffer bit to constrain it to a specific region, not the entire buffer. I'm looking for an alternative, but what i wanted to do is something like how the incremental highlight works in :substitute, for example.

You mean like the incsearch setting? You should be able to limit the matches using the \%l regexp pattern. So you could limit it to only the current viewport.
In general you probably want to use matchadd()- family of functions instead of using the match ex commands, since it is more flexible.

Yeah like inc search, for my use case even realized that there was a use case where i would have to use matchaddpos, and pull the range / lines i want to highlight loop over them and use match and matchend, to pull the start/end of the match and then matchaddpos. But yes matchadd and match* family are indeed the way to go.


Added LibraryCharges for monatomic ions in 1.0.1

This addresses #5.
I have added the monatomic ion LibraryCharges added in openforcefield/openforcefield#563 in openff-1.0.1.offxml. I have also added appropriate entries under Versions in the README, and attempted to give a tree-like structure showing our version history.
There is another PR like this for adding monatomic ion LibraryCharges in openff-1.1.1.offxml: #10

I'll review this one first. Just need to fix a bug with the testing infrastructure.


JBDS-4282 Deselect requirements for product when unselected

Codecov Report

:exclamation: No coverage uploaded for pull request base (1.3.0@ed5ffab). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff            @@
##             1.3.0     #566   +/-   ##
========================================
  Coverage         ?   79.29%
========================================
  Files            ?       18
  Lines            ?     2285
  Branches         ?      188
========================================
  Hits             ?     1812
  Misses           ?      473
  Partials         ?        0

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 ed5ffab...7683196. Read the comment docs.


New version: TechSmith.Snagit.2024 version 24.1.1

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.6 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Hi @PckgrBot,

This PR's version number 24.1.1 has 3 parameters (sets of numbers between dots - major, minor, etc), which is less than the current manifest's version <IP_ADDRESS>4, which has 4 parameters.

Does this PR's version number exactly match the version reported in the Apps & features Settings page? (Feel free to attach a screenshot.)
(Automated response - build 870)


NativeConstantInvocationFixer - add "strict" flag

@nicolas-grekas is it OK to add it to @Symfony rule set (I did it as it is very similar "strict" as for NativeFunctionInvocationFixer)?

Im very much :+1:  for adding to the SF set

Me too: \ should be removed on constants that don't need it.

Thank you @kubawerlos.


Create BucketSort.cpp

IMPORTANT: Please do not create a Pull Request without creating an issue first.
Any change needs to be discussed before proceeding.
Description
Please describe what changes you have made.
For Example:

Added a file(s) named '...' that implements '...'.

Changed the algorithm for performance/readablity/bugs.

Added documentation to the algorithm

Related Issue
This project only accepts pull requests related to open issues.
If suggesting a new feature or change, please discuss it in an issue first.
If fixing a bug, there should be an issue describing it with steps to reproduce.
Please link to the issue here:
How Has This Been Tested? (Optional)
Please describe in detail how you tested your changes.
You can skip this if you have not added any tests.
Screenshots (Optional)
Types of changes
What types of changes does your code introduce? Put an x in all the boxes that apply:

[ ] Bug fix (change which fixes an issue with the algorithm)

[ ] New Algorithm (non-breaking change which adds functionality)

[ ] Documentation

Checklist:
Go over all the following points, and put an x in all the boxes that apply.
If you're unsure about any of these, don't hesitate to ask. We're here to help!

[ ] My code follows the code style of this project.

[ ] My change requires a change to the documentation.

[ ] I have updated the documentation accordingly.

[ ] I have read the CONTRIBUTING document.

@tstreamDOTh, I guess we can close this pull request since other one related to same algorithm is open.


Add truffleruby support

Certain implementation details will differ on truffleruby, so we should always bind to the C API.
closes https://github.com/oxidize-rb/rb-sys/issues/424

Ok so I got basic gems building and the test suite passing on my mac. I had to skip the cargo test suite of tests since I got stuck on linking issues (missing symbols for things like rb_cBasicObject etc) but that's OK for now.

released in v0.9.103


Add support for 7z ARM64 and RISCV filters

This allows sharpcompress to extract 7z archives that use ARM64 and RISCV filters, added in 7zip 23.01 and 24.03 respectively. This is related to #822

Thank you!


number.sqrt object

There is a separate function of sqrt in defferent languages. For instance Math.sqrt in java. I think it would be useful to have this object too. We can use Heron's iterative formula instead of calculating method in number.power because the formula has a good convergence rate:
$$\sqrt{S} = \lim\limits_{k \to \infty} x_{k}$$
$$x_{k+1} = \frac{1}{2} * (x_{k} + \frac{S}{x_{k}}) $$
@Graur @EugeneDar WDYT?

@levBagryansky I don't mind

@maxonfjvipon WDYT?

@levBagryansky @Graur I like the idea about the Heron's formula. I have just a question: will we have an object to calculate a root of a n'th degree (n can be float as well)?

If yes then I think maybe we should introduce some universal object to calculate the root and make a special algorithm (Neron's) for n = 2 (or even for n = 2, 4, 8, 16, 32, ... 2^x)?
If no then sqrt fits good here

@maxonfjvipon may be it is better to use the method in number.power if x is less than 1.0? Otherwise we would have 2 almost same objects: power and root. So I guess it is better to have just sqrt

@levBagryansky ok, I agree

@levBagryansky the puzzle #92 is still not solved.