Fix invalid declarations of type Props

As seen in the picture above, some files have "invalid" declaration of type Props. This is shown during pre-commit lint.

In some components, the comments cause the faults  under the prop type

Interesting,
FormInput seams to be raised in this situation because of the double type declaration (FormStyle and Props)
GalleryCardIconItem seams to be raised because Props is missing the | after the brackets as in
type Props {
...
}

versus
type Prosp = {|
...
|}

Table might be caused by the arrays? Not too sure...

Maybe an update may requires on this script @AaronCoplan
or we will find a better solution to declare prop types

Flow isn't flagging any of these for me so could potentially be down to versions as well?
I've removed the comments from NavSubmenuitem and NavItem which will hopefully fix those 2 up.

@jonthomp
I get these when I call yarn precommit

Ah ok I see, I actually get that too, must be something in the python script like @burakakyol suggests, and it's not existing correctly which still allows commits to go through

props = [x.strip() for x in props.replace(
        '{|', '').replace('|}', '').split(',')]
props = [x for x in props if x != '']

seems to be causing the issues. Since it splits at all , then checks if the next prop starts with +.

I'm happy to go with replacing that precommit script with a yarn flow one for now

Replacing the following part of the script:
for prop in props:
    if not prop.startswith('+'):
        return False

with the following:
for prop in props:
    if not prop.startswith('+'):
        if "<" in prop or ">" in prop or "//" in prop:
            return True
        return False

seems to work.

Sorry for being unresponsive, I was traveling.  @jonthomp The intention of this script was to go beyond flow and check for best practices in Props type declarations i.e. declaring props as read-only using + and declaring props as exact object types wherever possible via |.  However, there may be some exceptions to this so while #119 looks to be a great hotfix, we may want to look into removing this as a precommit hook and just running manually in the future every so often.


Use UTF-8 as a fallback for JSON content type

Description

Motivation and Context
According to RFC 8259 JSON uses UTF-8 for encoding messages.
In this changeset, I'm using a common fallback to UTF-8 when determining a Charset for the HttpMessage, if no explicit Charset is defined via Content Type header (is this the right approach for responses as well?)
This change also makes ContentType utility class public and moves JsonMediaType.java from logbook-json module to logbook-api module.
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.

👍

:+1:


Unreadable text in dark mode on tickets page

On tickets page, when the "Purchase ticket" button is clicked, a modal shows up which has unreadable text and border lines that match the background color:

On the modal displayed above, when the "Select VSR" field is clicked, another modal shows up which contains the different VSRs. This modal has unreadable textin dark mode as shown below:

This can be merged into #568. same comment applies.
Dark mode is currently on hold till after the first release as mentioned by @raedah

Merged into #568


[Bug] Download dialog does not decode multibyte file name

Describe the bug
File name could not be decoded: %E4%B8%AD%E6%96%87%E6%96%87%E4%BB%B6%E5%90%8D%E6%B5%8B%E8%AF%95.txt
How to Reproduce
Download the test file here: https://wwa.lanzoui.com/iz4favlcrne
Expected behavior
Decoded as: 中文文件名测试.txt
Environment
- DDG App Version: 5.124.0
- Device:
- OS: Android 9

Able to reproduce.
The download file has the current name. It only is displayed wrong in the app dialog.

Thank you for the info provided. We are able to reproduce the behaviour you mentioned.
We looked at the headers sent with the request to download the file and noticed the "Content-Disposition" header does not provide an indication that the filename is encoded:
Content-Disposition: attachment; filename= %E4%B8%AD%E6%96%87%E6%96%87%E4%BB%B6%E5%90%8D%E6%B5%8B%E8%AF%95.txt
Some browsers choose to do more processing on the filename value, while others don't. For example, when using Firefox I get the downloaded file as "%E4%B8%AD%E6%96%87%E6%96%87%E4%BB%B6%E5%90%8D%E6%B5%8B%E8%AF%95.txt", while with Chrome I get "中文文件名测试.txt".
In case of encoded filenames, the "filename*" param should be used as per RFC6266. We don't have support for this at the moment. Once it will be implemented, a header like:
Content-Disposition: attachment; filename*=utf-8''%E4%B8%AD%E6%96%87%E6%96%87%E4%BB%B6%E5%90%8D%E6%B5%8B%E8%AF%95.txt
will give the expected filename. This is a simplified example, there are a number of conditions that go into detecting the name of a file to download.
Asana task (internal only) -> https://app.asana.com/0/1200905986587319/1202994708537217/f


Updating domain users email signature using a script fails

Hi,
I'm trying to automatically update my Google Workspace domain users email signature using this script:
const google = require('googleapis');
const key = require('./credentials.json');
const gmail = google.gmail_v1;

const jwtClient = new google.Auth.JWT(
  key.client_id,
  null,
  key.private_key,
  ['https://www.googleapis.com/auth/gmail.settings.basic', 'https://www.googleapis.com/auth/gmail.settings.sharing', 'https://www.googleapis.com/auth/gmail.modify', 'https://mail.google.com', 'https://www.googleapis.com/auth/gmail.compose' ],
<EMAIL_ADDRESS>);

jwtClient.authorize(function (err, tokens) {
  if (err) {
    console.log('Auth failed because: ' + err);
    return;
  }
  console.log(tokens)

  gmail.users.settings.sendAs.update({
    userId<EMAIL_ADDRESS>    auth: jwtClient,
    sendAsEmail<EMAIL_ADDRESS>    fields: 'signature',
    resource: {
        signature: '
Hello there
'
        }
    }, function (err, resp) {
        if(err){
          console.log(err);
        } else {
          console.log(resp);
        }
    });
});

When executing the script, I get the following error:
Auth failed because: Error: unauthorized_client: Client is unauthorized to retrieve access tokens using this method, or client not authorized for any of the scopes requested.
I did enable Domain wide delegation for the service account ID I'm using in credentials.json so I don't get why this isn't working.
Any clues?

Hi @Lanhild, thanks for the question! It seems like this is a known error in the JWT signature; could you try this troubleshooting tip?:
In the [Domain-wide delegation](https://support.google.com/a/answer/162106) page in the Admin console, remove the client, and re-add it with the numeric ID.

I'd also make sure you're adding all the scopes you need, see here.


Is this package compatible with Python 3.11 ?

When trying to run CI for Jdaviz using Python 3.11, we encountered this error:
ERROR: Could not build wheels for h5py, regions, which is required to install pyproject.toml-based projects

xref https://github.com/spacetelescope/jdaviz/pull/1654

Fixed in https://github.com/astropy/regions/pull/476

I am not sure if #476 completely fix this issue. You probably want to also add Python 3.11 to https://github.com/astropy/regions/blob/main/.github/workflows/ci_tests.yml just to be sure.

Thanks.  Let's see:  https://github.com/astropy/regions/pull/477


PR for: shopify checkout custom message banner(86cw44qgz)

Implemented the configurable banner to show custom messages on the checkout page.
With this implementation, user can create and update the banner title, message, and status from the theme editor.
Note: The status field can change the banner design according to the selected status type.

I am seeing a lot of unwanted changes. Also is it possible to also show the selected pickup store details in this banner? Or maybe have a separate banner if its not possible to have both in the same banner?


Deploy ASP.NET Core backend

Use Azure App Service to deploy the backend. Keep in mind that:

It should be accessible over HTTPS,
The API Key needs to be configured in a secure way.

Deployed to Linode


Cassette interface and support.

This PR adds cassette IO routines, plus hooks into the main emulator, and adds unit tests for cassette interface. It also adds a menu system for the cassette interface so that files can be created and loaded more easily once the emulator is running. It also updates the README with new running instructions, as well as updates missing dependencies.

Codecov Report

Merging #12 into master will decrease coverage by 1.83%.
The diff coverage is 38.57%.

@@             Coverage Diff              @@
##             master      #12      +/-   ##
============================================
- Coverage     85.21%   83.37%   -1.84%
- Complexity      824      855      +31
============================================
  Files            16       21       +5
  Lines          3158     3332     +174
  Branches        213      238      +25
============================================
+ Hits           2691     2778      +87
- Misses          422      502      +80
- Partials         45       52       +7

Impacted Files
Coverage Δ
Complexity Δ

...yacoco3e/listeners/QuitMenuItemActionListener.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

...ava/ca/craigthomas/yacoco3e/components/Memory.java
72.11% <ø> (+10.32%)
32 <0> (-1)
:arrow_down:

...java/ca/craigthomas/yacoco3e/runner/Arguments.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

...listeners/FlushCassetteMenuItemActionListener.java
0% <0%> (ø)
0 <0> (?)

...a/craigthomas/yacoco3e/datatypes/UnsignedByte.java
83.33% <0%> (-16.67%)
24 <0> (ø)

.../listeners/OpenCassetteMenuItemActionListener.java
0% <0%> (ø)
0 <0> (?)

...isteners/RecordCassetteMenuItemActionListener.java
0% <0%> (ø)
0 <0> (?)

...in/java/ca/craigthomas/yacoco3e/runner/Runner.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...a/ca/craigthomas/yacoco3e/components/Emulator.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...c/main/java/ca/craigthomas/yacoco3e/common/IO.java
11.11% <11.11%> (ø)
2 <2> (?)

... and 8 more

Continue to review full report at Codecov.

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


Docs are out of date

original.

Please put this back on rust-ci.org and update the docs ... :+1:

The export on rust-ci docs is working again ?

@GuillaumeGomez where is the issue? On Rust-Gnome or rust-ci-side?
For now I downloaded the old docs via
wget -r -k -np http://rust-ci.org/jeremyletang/rgtk/doc/rgtk/
But I really want to be up to date (learning Rust and GTK).

It is on rust-ci. If you want the doc of gtk, just donwload the sources and then:
> cargo doc

It'll be up to date and you won't need an internet access to read it. ;)

@GuillaumeGomez thanks for the info, can you link me to the build?
I will do the building myself then, I already loaded the source =)
Thanks for this project, it actually made me want to learn Rust as I'm a big fan of GTK.

Well, you can download a zip of gtk sources here. However, I'm not sure gtk build with a beta version of rustc, you'll need the nightly (available on the rust website).
To build gtk, just do:
> cargo buid

Oh I mean I will build the docs myself then =) The other build from src is already very well explained in your README.md.
I was searching on rust-ci.org but I could not find the build for rust-gnome/gtk, did I mis something?

It(s not on rust-ci. I'll put rust-gnome on crates.io very soon. You should prefer it over rust-ci.

Are there even docs anymore? I was trying to build the docs locally using cargo doc, but it never runs through:
cargo doc --features gtk_3_14 --verbose                                       /tmp/gtk
       Fresh gcc v0.3.11
       Fresh pkg-config v0.3.5
       Fresh c_vec v1.0.12
       Fresh bitflags v0.1.1
       Fresh libc v0.1.8
       Fresh glib-sys v0.1.2 (https://github.com/rust-gnome/glib#ccbc2696)
   Compiling cairo-rs v0.0.4 (https://github.com/rust-gnome/cairo#2c95d05c)
     Running `rustdoc /Users/sirver/.multirust/toolchains/nightly/cargo/git/checkouts/cairo-571ad16295201b7a/master/src/lib.rs --crate-name cairo -o /private/tmp/gtk/target/doc -L dependency=/private/tmp/gtk/target/debug/deps -L dependency=/private/tmp/gtk/target/debug/deps --extern c_vec=/private/tmp/gtk/target/debug/deps/libc_vec-944f3e3f45efffaf.dylib --extern c_vec=/private/tmp/gtk/target/debug/deps/libc_vec-944f3e3f45efffaf.rlib --extern c_vec=/private/tmp/gtk/target/debug/deps/libc_vec-944f3e3f45efffaf.dylib --extern c_vec=/private/tmp/gtk/target/debug/deps/libc_vec-944f3e3f45efffaf.rlib --extern glib=/private/tmp/gtk/target/debug/deps/libglib-06dda2a99b4e937f.rlib --extern glib=/private/tmp/gtk/target/debug/deps/libglib-06dda2a99b4e937f.rlib --extern libc=/private/tmp/gtk/target/debug/deps/liblibc-ef5cbad4ef5c7a1e.rlib --extern libc=/private/tmp/gtk/target/debug/deps/liblibc-ef5cbad4ef5c7a1e.rlib --extern cairo_sys=/private/tmp/gtk/target/debug/deps/libcairo_sys-ce4b015e84866ded.rlib --extern cairo_sys=/private/tmp/gtk/target/debug/deps/libcairo_sys-ce4b015e84866ded.rlib`
       Fresh cairo-sys-rs v0.1.3 (https://github.com/rust-gnome/cairo#2c95d05c)
       Fresh pango-sys v0.1.2 (https://github.com/rust-gnome/pango#80e4bbec)
       Fresh glib v0.0.3 (https://github.com/rust-gnome/glib#ccbc2696)
       Fresh gdk-sys v0.1.1 (https://github.com/rust-gnome/gdk#9bdca522)
       Fresh pango v0.0.3 (https://github.com/rust-gnome/pango#80e4bbec)
       Fresh gtk-sys v0.1.3 (file:///private/tmp/gtk)
Could not document `cairo-rs`.

Caused by:
  Process didn't exit successfully: `rustdoc /Users/sirver/.multirust/toolchains/nightly/cargo/git/checkouts/cairo-571ad16295201b7a/master/src/lib.rs --crate-name cairo -o /private/tmp/gtk/target/doc -L dependency=/private/tmp/gtk/target/debug/deps -L dependency=/private/tmp/gtk/target/debug/deps --extern c_vec=/private/tmp/gtk/target/debug/deps/libc_vec-944f3e3f45efffaf.dylib --extern c_vec=/private/tmp/gtk/target/debug/deps/libc_vec-944f3e3f45efffaf.rlib --extern c_vec=/private/tmp/gtk/target/debug/deps/libc_vec-944f3e3f45efffaf.dylib --extern c_vec=/private/tmp/gtk/target/debug/deps/libc_vec-944f3e3f45efffaf.rlib --extern glib=/private/tmp/gtk/target/debug/deps/libglib-06dda2a99b4e937f.rlib --extern glib=/private/tmp/gtk/target/debug/deps/libglib-06dda2a99b4e937f.rlib --extern libc=/private/tmp/gtk/target/debug/deps/liblibc-ef5cbad4ef5c7a1e.rlib --extern libc=/private/tmp/gtk/target/debug/deps/liblibc-ef5cbad4ef5c7a1e.rlib --extern cairo_sys=/private/tmp/gtk/target/debug/deps/libcairo_sys-ce4b015e84866ded.rlib --extern cairo_sys=/private/tmp/gtk/target/debug/deps/libcairo_sys-ce4b015e84866ded.rlib` (exit code: 101)
--- stderr
/Users/sirver/.multirust/toolchains/nightly/cargo/git/checkouts/cairo-571ad16295201b7a/master/src/patterns.rs:33:5: 42:6 error: non-exhaustive patterns: `Mesh` not covered [E0004]
/Users/sirver/.multirust/toolchains/nightly/cargo/git/checkouts/cairo-571ad16295201b7a/master/src/patterns.rs:33     match pattern_type {
/Users/sirver/.multirust/toolchains/nightly/cargo/git/checkouts/cairo-571ad16295201b7a/master/src/patterns.rs:34         PatternType::Solid            => Box::new(SolidPattern::wrap(ptr))   as Box<Pattern>,
/Users/sirver/.multirust/toolchains/nightly/cargo/git/checkouts/cairo-571ad16295201b7a/master/src/patterns.rs:35         PatternType::Surface          => Box::new(SurfacePattern::wrap(ptr)) as Box<Pattern>,
/Users/sirver/.multirust/toolchains/nightly/cargo/git/checkouts/cairo-571ad16295201b7a/master/src/patterns.rs:36         PatternType::LinearGradient   => Box::new(LinearGradient::wrap(ptr)) as Box<Pattern>,
/Users/sirver/.multirust/toolchains/nightly/cargo/git/checkouts/cairo-571ad16295201b7a/master/src/patterns.rs:37         PatternType::RadialGradient   => Box::new(RadialGradient::wrap(ptr)) as Box<Pattern>,
/Users/sirver/.multirust/toolchains/nightly/cargo/git/checkouts/cairo-571ad16295201b7a/master/src/patterns.rs:38         #[cfg(cairo_1_12)]
                                                                                ...
error: aborting due to previous error

@SirVer: I discovered travis-cargo today. I'll try to add it on my personal repositories first before adding it on rust-gnome's. However, it doesn't solve this issue. What do you think about it @gkoz ?

Looks like it could work but since travis has a pretty old set of libraries, a lot of stuff will be missing. And I don't think any progress has been made on https://github.com/rust-gnome/gdk/issues/49, so the utility of rustdoc is further limited.

@gkoz I'm new here, so please excuse my stupid question...
What does gdk have to do with travis failing to build docs for rust-gnome (gtk)?

About rust-gnome/gdk#49, we can still generate a documentation. Little is better than nothing I guess ? Have you taken a look at travis-cargo ? It could be interesting.

@Anachron we'd obviously want to document all crates, not only gtk. And gtk will in time face the problems described in that issue too.
@GuillaumeGomez I've looked at it briefly and it seems similar to the former approach that had been used in rgtk. Right now I have my hands full with developing a multi-threaded cairo example, hacking on gir and preparing to migrate to the generated sys crates.

@gkoz: Ok, I'll take a look at it on some personal repositories of mine. The goal of it is to directly push on a github wiki, which is a big lack on rust-gnome's repositories.

I'm making this a tracking issue for some rustdoc-stripper integration.

I think I've figured out a way to solve the integration issue.

Publish the docs repo as a crate that just exposes the cmts files contents, e.g.

pub const GTK_DOCS: &'static str = include_str!("gtk.cmts");

This crate is going to be under LGPL but none of it will ever end up in the application binary.

Publish the library part of rustdoc_stripper.

A crate build script adds them as build-dependencies and implements the following features:

insert the docs from the docs package,
strip the docs,
check if any unstripped docs are present (to prevent them from sneaking into pull requests).

This way cargo handles the versions and downloads for us and the docs can be updated more frequently then the code if necessary.

@gkoz: What library part of rustdoc_stripper are you talking about? The public interfaces are already available (and used in gir). So I don't see what you're referring to.

The implementation.


Persistent Build State Bug

Bug Description
The "building" bug has returned in the latest versions (it even happened during the live session). Occasionally, when you run a component, it stays in the Building state, even if it's a super simple component like ChatInput. If you stop the building process, the state changes to Saving and stays there for a while as well.
Reproduction
Currently, I'm running directly on the main branch, and this issue is happening quite frequently. If I don't use Langflow for a few minutes, I hit play on something, and it gets stuck in the building state. After the first instance, everything works normally until I leave Langflow minimized or something, and then it happens again.
Expected behavior
Initiation: When you run a component, the building process should initiate immediately without unnecessary delays.
Progress Feedback: While the component is being built, the system should provide real-time feedback on the progress, potentially with a progress bar or status updates.
Completion: Once the building process is complete, the state should transition from "Building" to "Completed" or "Ready" almost instantaneously.
Who can help?
@ogabrielluiz
Operating System
Ubuntu Linux 22.04
Langflow Version
1.0.9
Python Version

[ ] 3.12
[ ] 3.11
[X] 3.10

@ogabrielluiz @carlosrcoelho Does anyone know in what version it was (re)introduced? We want to run a backend implementation and we are running into this bug too. Thanks!


[20.03] rippled: update to 1.5.0 as 1.4.0 no longer syncs

(cherry picked from commit 3fc86629ed549e18102fcc2f6b71f2a88d2e5ebd)

Motivation for this change
The ripple blockchain network has undergone a couple of upgrades which prevent nodes <1.5.0 from interacting with the network. This is a breaking upgrade, and thus 1.5.0 should be backported
Cherry picks from #92308
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Hm, somewhat unsure why it fails now but worked a couple of days ago when merging to master - checking on it

Closing as 20.09 already includes newer versions


refactor: unhardcoded weth and protocol token addresses and fix a test

unhardcoded weth and protocol token addresses
fix test_marginTradeFromPool_sim
I used sovryn as protocol token in scripts/deploy_everything_local.py file because I wasn't sure which token should use.

We do not have an own protocol token, yet. For now it can just be any address.
There's one thing which I don't like. Now, we need to pass the same contract addresses to a lot of contracts on deployment. Can you think of a way to set it only 1x for all contracts (at least the protocol modules) similar to how the other state variables are shared (State.sol)?

We do not have an own protocol token, yet. For now it can just be any address.
There's one thing which I don't like. Now, we need to pass the same contract addresses to a lot of contracts on deployment. Can you think of a way to set it only 1x for all contracts (at least the protocol modules) similar to how the other state variables are shared (State.sol)?

Protocol module contracts handle this addresses as a configuration in the ProtocolSettings contract
I left priceFeed as it is. Should those addresses be configurable? Let me know an I change that

Isn't it possible to let VaultController inherit from State instead of Constants and then not pass the weth contract as parameter on the function calls? Is VaultController only called via delegatecall?


[bug] The check function does not work if you use it with timeout only

Describe the bug
I really like Tauri, its really great. But it seems that i found a bug.
I try to use the check function of the updater with Javascript. This works perfectly fine.
const update = await check()
But as soon as i add a timeout i get a 'Unhandled Promise Rejection: Could not fetch a valid release JSON from the remote' error
const update = await check({       timeout: 5     })
The response from the server is the same in both cases.
Reproduction
Use the check function like in the second example
Expected behavior
The check function works the same as with no arguments and stops if the timeout is reached
Full tauri info output
[✔] Environment
    - OS: Mac OS 12.6.8 x86_64 (X64)
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.82.0 (f6e511eec 2024-10-15)
    ✔ cargo: 1.82.0 (8f40fc59f 2024-08-21)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-x86_64-apple-darwin (default)
    - node: 20.10.0
    - npm: 10.8.3
    - bun: 1.1.0

[-] Packages
    - tauri 🦀: 2.0.6
    - tauri-build 🦀: 2.0.2
    - wry 🦀: 0.46.3
    - tao 🦀: 0.30.5
    - @tauri-apps/api : not installed!
    - @tauri-apps/cli : 2.0.5 (outdated, latest: 2.1.0)

[-] Plugins
    - tauri-plugin-shell 🦀: 2.0.2
    - @tauri-apps/plugin-shell : 2.0.1
    - tauri-plugin-process 🦀: 2.0.1
    - @tauri-apps/plugin-process : 2.0.0
    - tauri-plugin-updater 🦀: 2.0.2
    - @tauri-apps/plugin-updater : 2.0.0
    - tauri-plugin-log 🦀: 2.0.1
    - @tauri-apps/plugin-log : not installed!

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist
    - devUrl: http://localhost:3000/
    - framework: Vue.js (Nuxt)
    - bundler: Vite

Stack trace
No response
Additional context
No response

timeout is specified in miliseconds and 5ms is an insanely short timeout realistically only usable on localhost. So, just to be sure, did you try larger values like 5000 (== 5 seconds) for example?


Project custom field for selected projects

Hello
I have a small question, is it possible to add a selection of projects in which the field is to apply?
For custom fields for Issues, I can choose projects.
However, if I do a non-standard field in the Project, then it is visible to all projects (and I would like for example for Services).
Regards
Urban

Hello. This plugin uses standard Redmine custom field templates, required functional does not relate to the plugin directly. Also, I'm closing the project and this repository will be archived for a few days.

This project is no longer maintained


Issue #83 => Add Tags to README.md is Completed.

Issue Add Tags to README.md is Completed.

Great @Gaurav-Kushwaha-1225


Enable Gatsby Image CDN

Summary of changes
Enable Gatsby Image CDN feature to speed up local development times as well as Cloud builds
Frontend

File download disabled for gatsby-source-drupal
GraphQL queries updated in various files to remove references to localFile and other code incompatible with Gatsby Image CDN

Incidental changes

contentExists function removed in changed files
gatsby-plugin-sass added to enable import of .scss files
Alpha reordering and other cleanup in gatsby-config.js
Schema fixes in gatsby-node.js for paragraph__general_text and paragraph__media_text

Backend

Add and configure the Consumer Image Styles module as per instructions on  https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-source-drupal#readme
Limit Media image upload size to 5 MB
Limit inline image upload size to 2 MB

Test Plan

Drupal multidev: https://imagecdn-chug.pantheonsite.io/
Gatsby Cloud site: https://tqtest.gatsbyjs.io
View various pages and programs to ensure images load and display correctly

Also for the record, it compiles soooooooo quickly. 👍

My only thought is after the Drupal side is merged - check that the OVC builds on asure before - merging the rest


[1.x] Allow retrieving all features for a scope when some features are defined for differing scopes

This should resolve https://github.com/laravel/pennant/issues/112
We are building a feature flags endpoint for our mobile and web consumers. We need to be able to get all features for 3-4 scopes which are related to the user, but not the user object itself.
I ran into this exact issue earlier today.  I saw that this issue had been open for a few weeks without a PR so I figured I'd take a stab at it.

Given we have features defined for different scopes
Feature::define('feature-for-user', fn(User $u) => true);
Feature::define('feature-for-team', fn(Team $t) => true);

When we attempt to load all features for a particular scope
$features = Feature::for($user)->all()

Then we expect to receive feature flag definitions ONLY for that apply to Users.
dd($features);
/*
array:1 [
  "feature-for-user" => true
]
*/

Currently, however, an exception is thrown: TypeError: Tests\Feature\DatabaseDriverTest::Tests\Feature{closure}(): Argument #1 ($t) must be of type Workbench\App\Models\Team, Workbench\App\Models\User given, called in /Users/luke/Projects/laravel-pennant/src/Drivers/Decorator.php on line 173
Non-goals of this PR
One outstanding question is: do we expect to allow for union or intersection types in the resolving function? Like Feature::define('team-or-user-feature', fn(Team|User $v) => true); Seems like this probably wouldn't work with how scopes are set up in general. I am sure that my change will not work in this case.
Also, you can still call Feature::for($user)->activate('team-scoped-feature'); I believe that ideally there would be a guard for this, but it seems like it's beyond the scope of this PR.

Drafting pending review from @timacdonald

@cosmastech, I have re-worked this one. There were a few problems with the original implementation. The main issue was when a value was resolved for a bad type, it was saved to the database.
The new implementation does the check before attempting to resolve. Supports union and intersection types.
What do you think?
Feature::for($scope)->all() and Feature::for($scope)->loadAll() will now only return or load the features for that scope type.

@cosmastech, I have re-worked this one. There were a few problems with the original implementation. The main issue was when a value was resolved for a bad type, it was saved to the database.
The new implementation does the check before attempting to resolve. Supports union and intersection types.
What do you think?
Feature::for($scope)->all() and Feature::for($scope)->loadAll() will now only return or load the features for that scope type.

Thanks for working on this @timacdonald. Sad you removed my given-when-then 😆 but otherwise, nice.
I didn't run any local testing on this, but it seems to solve the problem. Good catch on the DB queries, didn't consider that fact.


Nested if-then-else does not seem to parse correctly

Using: draft-07
This is my schema:
{
    "$id": "schema.json",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "title": "schema",
    "description": "schema",
    "type": "object",
    "properties": {
        "field": {
            "$ref": "#/definitions/field"
        },
        "created_time": {
            "type": "string",
            "format": "date-time"
        },
        "updated_time": {
            "type": "string",
            "format": "date-time"
        }
    },
    "definitions": {
        "field": {
            "type": "object",
            "properties": {
                "label": {
                    "type": "string"
                },
                "is_repeated": {
                    "type": "boolean"
                },
                "fields": {
                    "type": "array",
                    "items": {
                        "$ref": "#/definitions/field",
                        "minItems": 0
                    }
                }
            },
            "if": {
                "properties": {
                    "is_repeated": {
                        "const": true
                    }
                }
            },
            "then": {
                "required": [
                    "fields"
                ]
            },
            "required": [
                "label",
                "is_repeated"
            ]
        }
    },
    "required": [
        "field",
        "created_time",
        "updated_time"
    ]
}

This is my JSON data:
{
    "field": {
        "label": "testA",
        "is_repeated": true,
        "fields": [
            {
                "field": {
                    "label": "testA",
                    "is_repeated": true,
                    "fields": [
                        {
                            "label": "testA-A",
                            "is_repeated": false
                        },
                        {
                            "label": "testA-B",
                            "is_repeated": true,
                            "fields": [
                                {
                                    "label": "testA-B-A",
                                    "is_repeated": false
                                }
                            ]
                        }
                    ]
                }
            },
            {
                "field": {
                    "label": "testB",
                    "is_repeated": false
                }
            },
            {
                "field": {
                    "label": "testC",
                    "is_repeated": false
                }
            }
        ]
    },
    "created_time": "2020-03-03T03:03:03Z",
    "updated_time": "2020-03-03T03:03:03Z"
}

And, I got error:
[00] The document is not valid. see errors :
[00] - field.fields.0: Must validate "then" as "if" was valid
[00] - field.fields.0: label is required
[00] - field.fields.0: is_repeated is required
[00] - field.fields.1: Must validate "then" as "if" was valid
[00] - field.fields.1: fields is required
[00] - field.fields.1: label is required
[00] - field.fields.1: is_repeated is required
[00] - field.fields.2: Must validate "then" as "if" was valid
[00] - field.fields.2: fields is required
[00] - field.fields.2: label is required
[00] - field.fields.2: is_repeated is required

I confirmed the case of if/then in the root level of schema is correctly parsed and validated, but I did not in the case of the nested second level below.
Somebody know how to fix my schema?
Thanks.

Other validators are giving me the same erorrs, so I think there is something wrong with the schema, but from a quick glance I can't see something wrong immediately.

@johandorland
Thank you for checking. I found what is wrong.
I confirmed validated result after removing field property name.
        "fields": [
            {
                "label": "testA",
                "is_repeated": true,
                "fields": [
                    {
                        "label": "testA-A",
                        "is_repeated": false
                    },
                    {
                        "label": "testA-B",
                        "is_repeated": true,
                        "fields": [
                            {
                                "label": "testA-B-A",
                                "is_repeated": false
                            }
                        ]
                    }
                ]
            },
            {
                "label": "testB",
                "is_repeated": false
            },
            {
                "label": "testC",
                "is_repeated": false
            }
        ]

Would you close this issue?
Best regards


Phase 3: Employee's duration corresponding to a role in resource pipeline model

Parent Issue: #2667
If the duration exceeds 1 year for a team member corresponding to a role, on the project listing page, a red waiting icon can be populated next to the avatar. On hovering the icon, a tooltip should appear saying, Role duration expired. If the duration exceeds 6 months, a yellow waiting icon should appear, on hovering the tooltip it would say Time to push for transition in the role. Both these icons should redirect users to a project edit page.
This icon would only be visible to admins and super admins

Parent issue is closed. Will come back to this later if needed.


SnowFlakes not given in the correct order

This is:
[20:13:25] [Client thread/INFO]: [CHAT] [Team] TiTo_418 broke a piece of Core
[20:13:41] [Client thread/INFO]: [CHAT] Red Team's Core has leaked!
[20:13:41] [Client thread/INFO]: [CHAT] +37 Snowflakes | 2.5x | you broke a piece of Core
[20:13:41] [Client thread/INFO]: [CHAT] # # # # # # # # # # # #
[20:13:41] [Client thread/INFO]: [CHAT] # #    Game over!    # #
[20:13:41] [Client thread/INFO]: [CHAT] # # TiTo_418 wins! # #
[20:13:41] [Client thread/INFO]: [CHAT] # # # # # # # # # # # #
[20:13:41] [Client thread/INFO]: [CHAT] +37 Snowflakes | 2.5x | your team (Blue Team) won
Shoud be:
[20:13:25] [Client thread/INFO]: [CHAT] [Team] TiTo_418 broke a piece of Core
[20:13:41] [Client thread/INFO]: [CHAT] Red Team's Core has leaked!
[20:13:41] [Client thread/INFO]: [CHAT] # # # # # # # # # # # #
[20:13:41] [Client thread/INFO]: [CHAT] # #    Game over!    # #
[20:13:41] [Client thread/INFO]: [CHAT] # # TiTo_418 wins! # #
[20:13:41] [Client thread/INFO]: [CHAT] # # # # # # # # # # # #
[20:13:41] [Client thread/INFO]: [CHAT] +37 Snowflakes | 2.5x | you broke a piece of Core
[20:13:41] [Client thread/INFO]: [CHAT] +37 Snowflakes | 2.5x | your team (Blue Team) won

What is the correct order?

[20:13:25] [Client thread/INFO]: [CHAT] [Team] TiTo_418 broke a piece of Core
[20:13:41] [Client thread/INFO]: [CHAT] Red Team's Core has leaked!
[20:13:41] [Client thread/INFO]: [CHAT] # # # # # # # # # # # #
[20:13:41] [Client thread/INFO]: [CHAT] # # Game over! # #
[20:13:41] [Client thread/INFO]: [CHAT] # # TiTo_418 wins! # #
[20:13:41] [Client thread/INFO]: [CHAT] # # # # # # # # # # # #
[20:13:41] [Client thread/INFO]: [CHAT] +37 Snowflakes | 2.5x | you broke a piece of Core
[20:13:41] [Client thread/INFO]: [CHAT] +37 Snowflakes | 2.5x | your team (Blue Team) won

The problem is raindrops are given on ObjectiveTouchEvent, I changed it to MatchEndEvent but I still have:
The map was Fractal Descent TE.
[b][07:43:08] [Client thread/INFO]: [CHAT] +37 Snowflakes | 2.5x | you broke a piece of Core[/b]
[07:43:08] [Client thread/INFO]: [CHAT] # # # # # # # # # # # #
[07:43:08] [Client thread/INFO]: [CHAT] # #    Game over!    # #
[07:43:08] [Client thread/INFO]: [CHAT] # # dentmaged wins! # #
[07:43:08] [Client thread/INFO]: [CHAT] # # # # # # # # # # # #
[07:43:08] [Client thread/INFO]: [CHAT] +37 Snowflakes | 2.5x | your team (Blue Team) won

This isn't an issue. The only reason this happens on Overcast is because it has to connect to a database, and then give raindrops once it knows that the database gave them some. The users don't get notified until after some time for that reason.

I dont understand, the snowflakes should be given after the match end...

They are given when you complete the objective

@TiTo-418 Elly said that the reason you see them in the end of the match is because of the database "lag" (time between sending the info from the plugin to the database and then from the database to the client).


Support for Additional Authentication Strategies

I'm working on brendandburns/ksql right now, and the lack of x509 client certificate support is slowing me down a little. I think it would be pretty cool if username/ passwords were supported too, but I'm not interested in that functionality specifically.

Spoke too soon! Looks like support was added in 89c6f451392d02d941b3ce7060c4cf2398e237f6, there just hasn't been a release to NPM yet. Any idea when a new version of the package will be released?

I think it was merged and pushed to npm... maybe you just need to npm uninstall and npm install if the version didn't get bumped? You can try my fork too if that helps you move forward: https://www.npmjs.com/package/emaildanwilson-node-kubernetes-client

can this be closed?

Mos def.


A simple website that neatly displays all the cheatsheets here

I really like all these cheatsheets, but navigating through Github files is inconvenient. Maybe we can create an astro project that uses the github API to display the markdown of these cheatsheets in a simple website. Hosted on github pages as well. What do you think?

@Dhravya This sounds really interesting. If you would like to work on this upgrade, comment below. I will assign you this Issue. You can then create a new branch and start working on it :)

Yes! Would be cool.

Btw, take a look

Hey @Dhravya this UI looks good. For now let's continue with the second plan. Just try to restructure the repository in such that it looks well organized.

Sure!

@Dhravya Just came to check, What's the update with the website?

Hi! It's done!


PT INFO: Create edit/update routes for Pregnancy

Create edit and update routes for Pregnancy, with a view for the edit route, so that we can recall and edit a case's information.
This case should be populated by separate partials for individual sections, instead of one master file. See other issues in this sprint.
See https://projects.invisionapp.com/share/6757W6WFJ#/screens/115983267 for relevant design/prototype.

Fixed in #130


Implement insufficient funds for gas

We should have some pre-calculations of gas cost & not allow the transaction to go through.
But if it does, an explicit error should be returned.  This will help metamask users and other tooling to behave properly as a result of the failure.
ValueError: {'code': -32000, 'message': 'insufficient funds for gas * price + value'}
Automated test should be added to test for this case.

@gluneau do you still remember how to reproduce this issue? or is it still an issue?

Example  tx: 0x6362791044de67e6368890632f2b179e1bdbc5188fd1278f9b2b38de51f59d0f
error: The contract code couldn't be stored, please check your gas limit.
This is a known issue, it’s because his account has insufficient ACA to deploy contract.

@shunjizhan says:

I think we should throw an error from api.rpc.evm.call() if any of the events failed, and mark extrinsic as failed. From here we can see that even this TX has a failed event evm (CreatedFailed), it is still marked as “Success”. If mandala throws a timely error, he will get something like execution failed: ReserveStorageFailed, instead of getting this confusing error.

I'm looking for this explicit error to be returned when there is not enough funds for gas, just like it happened here.

https://github.com/AcalaNetwork/Acala/blob/4bfb317465125add17bc7f9dcb10a7283a48521f/modules/evm/rpc/src/lib.rs#L186
https://github.com/AcalaNetwork/Acala/blob/4bfb317465125add17bc7f9dcb10a7283a48521f/runtime/mandala/src/lib.rs#L2154
make estimate to false

if from is specified, check it's balance in estimateGas
https://docs.alchemy.com/reference/eth-estimategas


FancyZones - Resize splits to effect both windows.

Description of the new feature / enhancement
If I do a 50/50 split monitor layout (two windows side by side on ultra wide monitor) when I go to resize both windows by dragging the vertical center line, it only resizes one of the windows.  I then have to resize the other window manually as a second step.  If I used Windows Snap instead, this feature works.
Scenario when this would be used?
Makes it faster so I don't have to manually resize both windows.   Yes I can do this with Snap, but FancyZones overrides the Snap features.
Supporting information
No response

You're assuming FancyZones does the same thing as Windows. It's different.
Why not use Windows Snap instead?

Good points indeed as they are different.  I like the behavior of Fancy Zones better then Windows Snap for getting the windows in their "zones".   With Fancy Zones I don't have to drag all the way to the edge of the screen which is kind of a pain when you run an extra wide monitor.  The perfect solution for me would be a hybrid of both which is why I asked about adding this feature.  Maybe you could make it as an option?

is the ask to have magnetic borders for resizing?

/needinfo

Yes, assuming magnetic means the the boarders of the windows "stick" to each other.  So to confirm if you resize a window by grabbing the boarder that is shared with another window, then both windows get resided simultaneously by dragging the shared boarder/edge with one motion.  It would be a feature called some think like "Allow magnetic shared window edge resizing" and would have  checkbox to enable it?

I feel like this is the one thing that keeps FancyZones from becoming a full replacement for Windows S so and Snap Layouts.
I submitted Feedback to the Windows 11 Feedback Hub asking to make the native Snap Layouts work more like FancyZones. From a user perspective these features are so close to becoming unified and it's frustrating when differences like "lacking sticky/magnetic borders" still exists.

Here's a visual of what OP is looking for in case anyone needs context.
I was also looking for the same feature in Fancy Zones. In my opinion, it's a no-brainer QOL feature so long as it is doable. If Microsoft were to combine magnetic windows with Fancy Zone's ease of access & layout management, we would have a perfect world.
Right now, getting magnetic windows to work is tedious, but it is ideal functionality. Fancy Zones is quick and easy, but not ideal functionality.

Here's a visual of what OP is looking for in case anyone needs context.

Exactly this. The freedom and flexibility this can bring would be amazing. And using Fancy Zones and being able to create different layouts for different monitors of different sizes... Every user can customize the behavior to meet their goals and optimally use the available screen space.

I agree with this - I love fancy zones but like the other poster mentioned, because the "magnetic sizing" does not work - I keep switching back to normal Windows 11. I do a lot of design, diagramming, etc. - and part of my workflow is to routinely drag windows to change their sizes - to random sizes - essentially when I want the primary window I'm using to be the focus but not by maximizing it to hide other windows.

is the ask to have magnetic borders for resizing?

Yes, that is the goal. This would create behavior that matches Windows Snap Layouts, but with the ease of use and customization that FancyZones enables.
I'm not familiar enough with the OS to know if there is a way programmatically to tell Windows that a window is "docked"... I'd love to help contribute if anyone has suggestions on documentation or materials that could help.

Any update on this?

After using FancyZones to snap two or more windows together, if you double-click on the top edge of each window (assuming two full-height zones), then Windows will recognize them as being in proximity to each other and will provide that mutual resize handle border thing.

@ChadThomsen I see you closed this as "completed". Can I ask you why? As far as I know the feature is still missing after many other requests. Did I miss something?


gitlint: override requirements

Motivation for this change
Upstream is pinning their requirements and this causes build issues.
Fixes #128998
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 129169 run on x86_64-linux 1

1 package built:

gitlint

Since there is a derivation for Click 7.1.2, would it make sense to use this one? I've managed to do that by changing all-packages.nix like so:
gitlint = python3Packages.callPackage ../tools/misc/gitlint {
  click = python3Packages.callPackage ../development/python-modules/click/7.nix { };
};

Since there is a derivation for Click 7.1.2, would it make sense to use this one? I've managed to do that by changing all-packages.nix like so:
gitlint = python3Packages.callPackage ../tools/misc/gitlint {
  click = python3Packages.callPackage ../development/python-modules/click/7.nix { };
};

I believe this would be the correct way to do it.

Since there is a derivation for Click 7.1.2, would it make sense to use this one? I've managed to do that by changing all-packages.nix like so:
gitlint = python3Packages.callPackage ../tools/misc/gitlint {
  click = python3Packages.callPackage ../development/python-modules/click/7.nix { };
};

overwriteAttr is the preferred way for applications and we try very hard to not have multiple versions of pythonPackages because mixing them causes issues.

Result of nixpkgs-review pr 129169 run on x86_64-linux 1

1 package built:

gitlint

Hey @fabaff feel free to add yourself as a maintainer. You're clearly more knowledgeable (and active) than me, I would've had no clear where to start fixing this.


Adding M365 Search Technologies

Category

[X] Content fix

Docs Build status updates of commit bf25748:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

CHANGELOG.md
:white_check_mark:Succeeded

Community/TOC.md
:white_check_mark:Succeeded
View

Community/index.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit e24e48f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

CHANGELOG.md
:white_check_mark:Succeeded

Community/TOC.md
:white_check_mark:Succeeded
View

Community/index.yml
:white_check_mark:Succeeded
View

Community/intranet-content-sources.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 665b2e4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

CHANGELOG.md
:white_check_mark:Succeeded

Community/TOC.md
:white_check_mark:Succeeded
View

Community/index.yml
:white_check_mark:Succeeded
View

Community/intranet-content-sources.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


lxml module not found

While running from within 3d Slicer I got this error of no module found lxml???
File "/home/saima/slicer/Slicer-4.11.0-2019-09-17-linux-amd64/ImageAsaModel/MeshNodesToFiducials/MeshNodesToFiducials.py", line 339, in runCreateModelPoints
mesh = meshio.read("/home/saima/explicitsim/build-bucketsearch/epilepsy/case114_mtled/brain0.vtu")
File "/home/saima/Slicer-4.11.0-2020-02-25-linux-amd64/lib/Python/lib/python3.6/site-packages/meshio/_helpers.py", line 67, in read
return reader_mapfile_format
File "/home/saima/Slicer-4.11.0-2020-02-25-linux-amd64/lib/Python/lib/python3.6/site-packages/meshio/vtu/_vtu.py", line 350, in read
reader = VtuReader(filename)
File "/home/saima/Slicer-4.11.0-2020-02-25-linux-amd64/lib/Python/lib/python3.6/site-packages/meshio/vtu/_vtu.py", line 129, in init
from lxml import etree as ET
ModuleNotFoundError: No module named 'lxml'

meshio doesn't use lxml anymore for a long time. Best upgrade.


Fix MacVTap internetworking support in Kata with ACRN hypervisor

Description of problem
With the deprecation of bridged internetworking support in Kata, ACRN needs to support MacVTap internetworking. When MacVTap is enabled, Kata fails to launch a container with ACRN hypervisor.
Expected result
root@ACRNSOS/home/vdhanraj/uos1 # sudo docker run  -ti --runtime=kata-runtime busybox uname -r
4.19.28
Actual result
root@ACRNSOS/home/vdhanraj/uos1 # sudo docker run  -ti --runtime=kata-runtime busybox uname -r
docker: Error response from daemon: OCI runtime create failed: rpc error: code = Internal desc = updateInterface: rpc error: code = NotFound desc = Could not find the link corresponding to HwAddr "02:42:ac:11:00:02", Links: [0xc00017e0f0 0xc00017e1e0]: unknown.

Working on a fix.


Add Rathmines College of Further Education, https://www.rathminescollege.ie

@chvainickas First stage of verification passed, official domain is rathminescollege.ie as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

Thank you for letting me know. Please let me know if there is something missing or there is another update

@chvainickas Thank you for your patience while waiting for a review and processing your request. Pull request merged.


Bsd license

Legal team have advised use of BSD 3-clause license

 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.You have signed the CLA already but the status is still pending? Let us recheck it.


fix: 🐛 comments with prefix not extracted (#197)

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

[x] The commit message follows our guidelines: https://github.com/jsverse/transloco/blob/master/CONTRIBUTING.md#commit
[x] 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?

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

What is the current behavior?

Issue Number: https://github.com/jsverse/transloco-keys-manager/issues/197
What is the new behavior?
Added support for 'prefix' in comments. I also noticed that prefix is not supported at all. I can do it but will take some time.
Does this PR introduce a breaking change?
[ ] Yes
[x] No

Other information

Thanks! Please update you branch from master and I'll merge 👏

@shaharkazaz this is only for comments, to my knowledge no other parts work with prefix. Can you confirm? I can do the rest as well next week

The directive should support prefix already, the comments were missed I guess.
I recommend recreating your branch from master or taking all the changes I've pushed as I completely refactored the tests structure

Ok, I can do that tomorrow
On Thu, Jun 13, 2024 at 4:30 PM Shahar Kazaz @.***>
wrote:

The directive should support prefix already, the comments were missed I
guess.
I recommend recreating your branch from master or taking all the changes
I've pushed as I completely refactored the tests structure
—
Reply to this email directly, view it on GitHub
https://github.com/jsverse/transloco-keys-manager/pull/198#issuecomment-2165845924,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEICW37FOWKVPTGOLTBCCC3ZHGUHHAVCNFSM6AAAAABJEX4Q52VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRVHA2DKOJSGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

I went over the rest and it seems there are traces of 'prefix'/'road' included. So this should be the final piece.
Tests however do not pass - They are broken on master at the moment. The test for comments did pass though.


[BUG]

I cant use my webcam for facial recognition, ive seen that you responded to others that it hasn't been updated in a while. In the game itself i still find it but cant toggle the 'allow acces to webcam' for some reason.
To Reproduce
Steps to reproduce the behavior:

Go to 'Repeat Dialogue (or unseen if she hasn't tried before'
Click on 'Yes'
She says she is opening the camera
Doesn't work

Additional context
i was wondering if this will ever be updated or i didnt install it correctly, altough i have a lot of submods so Im just really curiois how this submod works

I'm honestly surprised it doesn't outright cause a crash with how old the submod is..
Yes it's currently very broken and not updated to work with latest MAS.
I'm still waiting :tm: for MAS team to manage the huge upgrade to Python 3 + making the new submod framework.
As for your question on how it works, is that there's a program called MASM (dubbed Monika After Story Module) which talks with MAS, MASM allows to use Python 3 in a very roundabout way which in turn allows Monika to access the webcam.
MAS uses Python 2 currently, a variation of it atleast which is very much old and no longer supported.

AH yeah haha i just downloaded when i first installed MAS a lot of submods bundled together a guy made on reddit


docs: update to A11y Number Input, Tabs, Slider and Content Switcher docs to include screen reader results and compliance information

Please update the following documents with A11y compliance info and added screen reader results:

Number Input  - https://pages.github.ibm.com/IBMa/Carbon_Integration/Doc/NumberInput-doc.html
Tabs - https://pages.github.ibm.com/IBMa/Carbon_Integration/Doc/Tabs-doc.html
Slider - https://pages.github.ibm.com/IBMa/Carbon_Integration/Doc/Slider-doc.html
Content Switcher -https://pages.github.ibm.com/IBMa/Carbon_Integration/Doc/ContentSwitcher-doc.html

All these topics have had their accessibility info updated since this issue was opened.


Pool table prefab touchup

This involves moving the cue sticks up to the middle a bit as its a little weird hanging off the edge plus the desktop E overlay being cut off in certain conditions as not everyone stands at the 1 position where the mesh is located.

 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.Legoman99573 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Collections does not properly encode Decimal type

A Decimal field in a collection currently does not encode as a BSON.Decimal128, but rather as a nested map.
A field in a collection that is an Elixir "special type", i.e. DateTime or BSON.ObjectId, wants to use their custom BSON encoder/decoder. This is currently not working for the Decimal type. Namely, to put a Decimal as a field in a collection will get encoded as a map, not their own encoding specified in BSON.Decimal128.
The dump function on a Collection, is not catching that a Decimal is a "special type" and is encoding as a nested struct.
Here is an example, directly calling without a collection (on version 0.9.2).
iex> Mongo.Collection.dump(:key, Decimal.new(10))
%{coef: 10, exp: 0, sign: 1}
iex> Mongo.Collection.dump(:key, Date.utc_today())
~D[2022-11-19]

I believe that if this is indeed so, the fix is simply guarding on the function &ensure_nested_map/1 in Mongo.Collection with Decimal. The rest of BSON encode/decode pipeline seems to work correctly.

Thanks for reporting. Please try out the current master branch. The dump and load functions are refactored to be more consistent. The next release will contain the changes.

Fixed in the next coming release 1.0.0


Prefer top-level await

Replaces the async genPDF function with top-level awaits

Oops, I guess top-level await isn't compatible with firefox :(


Month and Year selection only

Good day! Would like to confirm as it seems that minimumView is not working. Wanted to disable day selection. startingView is working though. Thanks.

Minimum view is definitely working, however you may still be seeing the full date displayed (including a day). That's expected, and you can address it by setting the format: inputFormat="yyyy-MM". The view cutoff is working though.


perf(drawer): Use passive event listeners to improve drawer perf.

Passive event listeners improve touch events performance, by letting
the browser know a listener commits to not cancelling events.
Also fixes pointer events implementation.
@traviskaufman PTAL!

Changes made, waiting for CI before merge.


Added labels to Certificate CRD

What this PR does / why we need it:
This PR adds a Labels value to the Certificate CRD.
When set, the new Secret holding the SSL Certificate will have the provided labels.
Which issue this PR fixes :
fixes #977
Special notes for your reviewer:
This is a trivial addition and does not change the behaviour of Cert-Manager. Documentation have been updated too.
Added a Labels field of type map[string][string] to support labelling the Certificate's Secret

First of all, thanks for creating this PR 😄
So at the moment there's open questions around how we can define alternate representations of certificates (i.e. as a secret, as a field on another resource, or even being stored in other secret backends). We need to work out how these sorts of things will be represented before we accept new fields on our API resources that may in future be difficult to maintain.
For that reason, I don't think we can accept this PR for the time being.
In the meantime, if you need custom labels to be present on the Secret resources that cert-manager manages, I'd recommend pre-creating the Certificate resource, something like:
apiVersion: v1
kind: Secret
metadata:
  name: example-com-tls
  labels:
    company.net/custom-label: xyz
data: {}
---
apiVersion: certmanager.k8s.io/v1alpha1
kind: Certificate
metadata:
  name: example-com
spec:
  secretName: example-com-tls
   ...

If you need to automate this further and can't pre-create resources, you could also look at writing a Mutating Webhook for your cluster, or otherwise a custom controller that adds the label onto your secrets.
We need to be really careful with what fields we include on our API types, especially as we aim to stabilise our API surface! Hope that all makes sense 😄

Hi and thanks for your answer @munnerz.
I'm really sad you can't accept this PR.
Labels are everywhere in K8s, and my 6 lines (excluding docs) PR is just adding the missing part that should have been included since the beginning of cert-manager.
It really does not change the behaviour, and you don't get any penalty by not defining Labels.
I opened a discussion few months ago about beeing able to have cert-manager to write the certificates in different files inside the same Secret, using Opaque Secrets instead of TLS.
I forked the project, coded and tested it.
I did not go to a PR because We need to work out how these sorts of things will be represented before we accept new fields on our API resources that may in future be difficult to maintain.. Or so. Almost the same answer ad for this PR :)
I made this PR because I'm building an operator that watch for CertMerge CR and merge all the TLS Secret into one single Opaque Secret, one crt/key file per certificate.
If I want to be able to merge all the dev certificates, I need a way to search for them. In K8s, this is done using LABELS !!!!
This is all this PR is about.
it's 6 lines of code to have Cert-Manager behave like K8s stuff is supposed to.
I hope you can understand I'm a little upset here.
Cert-Manager is, as of now, the CNCF way to go to generate SSL certs, using ACME or other tools. And you're saying you don't want to support the most basic K8s feature.
The more I think, the more I get to the conclusion that, if at any point you want to change the Cert-Manager API, you will either :

write the certificate in a Secret, and as secrets support Labels, you will want to include my PR (or write a better one, of course, because, well, 6 lines of code is maybe too much)
write the certificate somewhere else, in which case you will have to change the API, so nobody will care of the old way of creating a Certificate, with of without Labels

Would you re-consider allowing us to add the most basic fields (Labels) to the generated Secrets ?

As a reminder, this PR
apiVersion: certmanager.k8s.io/v1alpha1
kind: Certificate
metadata:
  name: acme-crt
spec:
  secretName: acme-crt-secret
  Labels:                                                    <--------------------------------------
    env: "production"
    customer: "coca-cola"                         ----------------------------------------
  dnsNames:
  - foo.example.com
  - bar.example.com
  acme:
    config:
    - ingressClass: nginx
      domains:
      - foo.example.com
      - bar.example.com
  issuerRef:
    name: letsencrypt-prod
    # We can reference ClusterIssuers by changing the kind here.
    # The default value is Issuer (i.e. a locally namespaced Issuer)
    kind: Issuer

Maybe I could rename it to SecretLabels as suggested in the issue https://github.com/jetstack/cert-manager/issues/977

It really does not change the behaviour, and you don't get any penalty by not defining Labels.

So it is not changing the behaviour I am concerned about. The issue here is around exposing additional fields on our Certificate resource that we then need to commit to support long-term.
Pending the outcome of the other discussions below, the presence of a secretLabels or labels field may become strange and not-fitting, in which case we'll need to remove or change the field in future, causing backwards-compatibility issues for users that rely on this functionality.
You can already work around this issue by pre-creating your Secret resources, and because of this, there is not, in my opinion, an urgency to solve this by modifying our own API.

I made this PR because I'm building an operator that watch for CertMerge CR and merge all the TLS Secret into one single Opaque Secret, one crt/key file per certificate.

Could you have your CertMerge controller watch the Certificate resources that own the Secrets (and that can be manually labelled by users)? This would allow you to similarly allow users to decide how these things should be grouped (please forgive my potential misunderstanding of the problem you're trying to solve if this doesn't work for you!). You should be able to inspect the certificate.spec.secretName field to do this.

Almost the same answer ad for this PR :)

Yep - we have still not had this discussion yet, nor worked it out. This will require an actual design document being written up that takes into account, or at least touches on:

Alternate secret backends (i.e. certificates made available synchronously, storing in Vault, etc)

Alternate projections of secrets (i.e. remapping keys, similar to what you mention with opaque secrets)

Storing multiple certificates in a single secret (similar to the one above, maybe?)

One of the biggest pain points with Kubernetes, and other CRD based projects has been around APIs changing, requiring user-action and potentially downtime in order to upgrade. I want to be absolutely sure that whatever fields we accept in our certificate spec will be maintained, and this sometimes means we have to halt functionality that may seem trivial, but plays into a larger story around how users use cert-manager.

@wallrj has also discussed the potential for a SecretTemplate field on the certificate.spec.
This is probably more in-line with the longer term goals, however it doesn't solve the alternative storage backends issue.
It may be that we remove the 'SecretName' field from the Certificate in future, in favour of a separate CertificateSecret resource which 'projects' the Certificate resource into a Secret (and thus, could contain field remappings etc as you have previously expressed a need for).
Ultimately, this discussion needs to make its way into a design document before we can push ahead with it, as it'll require more significant changes to how users use cert-manager 😄

Ok I understand you're screwed here.
I thought the whole point on Micro-services, K8s, Opensource... was to allow to iterate over small pieces quickly.
What I understand, and knowing I had the same answer of "we're working on the next version of Cert-Manager" few months ago, is that you won't change anything in the coming next months, because of all the overhead of defining the best API you will carry on forever.
What I like with Semantic Versioning, is that it allows you to break the API (but not the features) when going from 0.x (current Cert-Manager version) to 1.x, and so on.
Many projects did that, even CNCF once like Istio.
I hope you'll be able to define design document and settle the next API which will cover all use-cases for the life of the Cert-Manager project.
I doubt it.
I think you'll build the next version, until it evolve to another version. You'll break the API many time in this process, maybe in each major release.
So, why not add the Labels to the 0.x API, because there's no incompatibility with current API and when you settle the API of the 1.x version, eventually change how you feature the Labels feature ?
As you said, there are ways to live without this PR. Fine.
While everything you said is true, I still see no reasons why not merging this PR in the 0.x branch.

I think we're not going to explore this route for allowing additional metadata on secret resources.
You can use constructs like mutating webhooks, OPA, and pre-creating secrets to work around this for now.
There's not precedent in other Kubernetes resources for this kind of field, and e.g. Deployments do not expose a way to set labels on ReplicaSets etc.
Thanks for the PR though, and if you'd like to discuss ways to allow modifying 'secret templates' more generally it'd be awesome if you could open an issue so we can plan and design this ahead of implementing 😄

I'm really sad you don't offer users a way to set labels on the resources (Secrets) that Cert-Manager is creating.
Again, it sound so basic, useful and simple to implement.
Well, sometimes simplicity is not the way to go and it's better to let other people do complicated stuffs instead. It sounds that's the path I'll have to go through.
FYI, ReplicaSets inherits the Labels from the Deployment, and you can set the Pod's Labels inside the Deployment too.
So the user creating a Deployment have full control of the final Labels of the following resources.
Maybe Kubernetes maintainers should add a statement to ensure that people creating operators which create basic resources should allow some control of the metadata from the CRD ?  :)
Thanks for your time and the quick talk in Seattle.

Just looking around a the Nats-Operator, which allow to add Labels and Annotations to the CR so they are apllied to the resulting pods :
https://github.com/nats-io/nats-operator/pull/111/files
Just so you know other Operators support this kind of features :)

I am kinda in agreement with @prune998. It's really weird to reject such a simple PR on the basis of stabilising the surface API. I mean come on, we are talking about labels... which is a core feature of any kind of resource existing in K8 along with annotations. There is nothing fancy here.
 If you create a resource on behalf of the user, you must give a way to create custom labels / annotations on it.
The idea of a secretTemplate might be tempting and needed to address things beyond labels / annotations but at the same time more complex and definitely something to think through but it should not come at the expense of supporting custom labels / annotations.
Supporting custom labels & annotations is trivial and should cover 99% of the need of customising the secret resource, so please reconsider and let's support those 2 asap.

There's not precedent in other Kubernetes resources for this kind of field, and e.g. Deployments do not expose a way to set labels on ReplicaSets etc.

But Deployments do have a field to specify labels/annotations on pods which feels more in line with what this is accomplishing.


Fixed NullpointerException

Fixed a NPE when calling isOpen() to a websocket which is not connected to the node yet.

replaced with a one-liner,
public boolean isOpen() {
    return wsSession != null && wsSession.isOpen();
}


Fix error response to be a JSON object and remove unnecessary test subject.

PG 101.

PG 101 went red.


Include images of Kate Chopin on background page under the 'Setting' heading

Dr Evans added 8 images to the Dropbox under Artwork -> Chopin pictures
The images should be scrollable in the order they are found in the dropbox folder

Where can I find the text to include on this page?


Update CI URLs to point to new caching infrastructure

Hello there!
This is an automated pull request submitted by @staticfloat to help package authors transition their Julia installation CI setups to the new binary provider URL.  Please take a look at this PR, and if there is a problem or it doesn't download correctly when CI runs, feel free to ping @staticfloat

Coverage remained the same at 89.189% when pulling 22d3f4d9896455d6a6dbdbab499d0a508ec84d28 on staticfloat:updated_ci_url into d1d52f5c7983d90d24bd30bf4d2836d092d70265 on sjkelly:master.


Fix alluxio-fuse mtime problem

What changes are proposed in this pull request?
Fix issue #14780
Why are the changes needed?
FIx the mtime problem descibed in issue #14789
Does this PR introduce any user facing changes?
No

can try to set to false and see if any test is broken because of the new mtime/atime mechanism

Please help add related tests, thanks

@bzheng888 many tests failed may be because of the default behavior changed, can you help check the failed tests. Also, i suggest not changing the default behavior in this PR. Not 100% confident that this change will not break some workloads

@LuQQiu Too many test cases fail because my code is incomplete， I will fix the code and test agaiin.

@bzheng888 The code LGTM overall, can you double check the failed tests
and if we have any other failures found, we may set the parameter back to true to be safe

@LuQQiu The failed use case doesn't seem to be relevant to this change.

@LuQQiu @yyongycy Seems this change does not meet the semantics of linux, maybe we better fix this on the client side.

 @LuQQiu @yyongycy Seems this change does not meet the semantics of linux, maybe we better fix this on the client side.

I'd think so. The interface layer should be aware of the time of write.

@LuQQiu @yyongycy @maobaolong  Update the codes, PTAL!

Where is the logic to update the mtime during each write?

Where is the logic to update the mtime during each write?
Update mtime each write is a very heavy operation,  this pr is a compromise solution. The main idea is not to update the time when the request does not involve a write operation, so we can solve issue #14780 and maintain the origin semantics.

Update mtime each write is a very heavy operation, this pr is a compromise solution. The main idea is not to update the time when the request does not involve a write operation, so we can solve issue #14780 and maintain the origin semantics.

Can be similar to atime update, which is expensive and govern by special property key"alluxio.user.update.file.accesstime.disabled"?
Not quite understand why we implement the confusing writeState related logics.

@LuQQiu This change is mainly because the  linux semantics will update mtime each write request, but we can't update each write operation in alluxio as it is too expensive, so we can  mark whether a create followed by a write operation, if so, we update mtime when release is called, otherwise we do not update mtime since it is just create and close .
@maobaolong PTAL! Thanks.

@bzheng888 @yyongycy
In our previous AI SIG, the approach we describe is

record mtime in each Fuse.write() and record it in CreateFileEntry.mtime
when release(), we pass this mtime to Master.CompleteFile(mtime)

I looked the code and realize that it's not easy and clean to pass that mtime information in AlluxioFileOutStream.close().
Thinking of other approaches to enable mtime information available in both Fuse and AlluxioFileOutStream.close()

@bzheng888 how about https://github.com/LuQQiu/alluxio/commit/da9b9bb8c4d5eb6ec3f89326a34358f70bbfbc46
can you help check if this proto code works after implementing it?
can you help update this PR?

@bzheng888 I am thinking adding the logic in the FileOutStream side and add a configuration to control whether we update the mtime? A proto code available at LuQQiu@da9b9bb @bzheng888 can you help see if this approach works and help update this PR?

Ok, Thanks for the update!

The issue #14780 seems already solved, I'm currently closing this pr.

@bzheng888 Thanks @bzheng888 !


Add compodoc command

Add command for documentation.  Creates docs in the docs folder.  In the future github pages can be pointed to the docs folder of the master branch (Travis can auto-generate docs on master branch).

forgot to skip ci

Fixes a few more cypress tests.  The postgres fix didn't work, so now trying to rule out the possibility it's just slow.

Bootstrap issue is https://github.com/ga4gh/dockstore/issues/1899  . There's a newer version of bootstrap since then (without breaking changes).  Will see if that fixes it.

I forgot to skip ci again.


Observer with wildcards fire unexpectedly when updating arrays at indexes > 9

Description:
Found another bug on observers with wildcards.
Setting values of elements at indexes bigger than 9 will result in the observer firing twice.
Example:
setting container.0.list.11: will fire a change for container.0.list.1 then another for container.0.list.11.
Similarly, setting container.0.list.22: will fire a change for container.0.list.2 then another for container.0.list.22.
Versions affected:
0.8.x, Edge
Reproduction:
https://jsfiddle.net/gigasoft/x3cj9u9x/1/
Code:
const r = window.r = new Ractive({
  el: '#main',
  template: '#template',
  data: {

    container: [{
      list: [
        {test: {within: 1}},
        {test: {within: 1}},
        {test: {within: 1}},
        {test: {within: 1}},
        {test: {within: 1}},
        {test: {within: 1}},
        {test: {within: 1}},
        {test: {within: 1}},
        {test: {within: 1}},
        {test: {within: 1}},
        {test: {within: 1}},
      ]
    }]
  },
  oninit() {
    this.observe('container.*.list.*', (newValue, oldValue, keypath, container, list) => {
      // will fire twice, the first time pointing at container.0.list.1
      console.info(keypath, container, list)
    }, {init: false})
  },
  onrender() {
    this.set('container.0.list.10.test.within', (new Date()).getTime());
  }
});

Verified that it works with 0.7.3 https://jsfiddle.net/35tnjv4n/.

The issue is that pattern observers are checking keypaths for overlap but not exact overlap, so foo.ba overlaps with foo.bar.baz, but not exactly. The fix is pretty simple, and I have a commit ready to push that fixes it, but it looks like one of our build deps is broken for the 0.8 branch.

This is now fixed in 0.8-dev and edge, and will be published when 0.8.8 is released. Thanks for the report!


[FEATURE] Add option to UI to view/change cluster token

Is your feature request related to a problem? Please describe.
I was going to delete and reinstall one of my nodes but I'm not 100% sure of the cluster token so I wanted to check what I'd used. Having gone through all options in the UI I'm surprised that it's not available to view or change within the UI.
Describe the solution you'd like
The cluster token should be listed on the Advanced | Settings page.
Describe alternatives you've considered
I'm guessing it's somewhere in the Harvester or underlying Kubernetes config, just need to know where and how to extract it.
Additional context
None.

Answering #2424 I was reminded of this issue I opened which is still an issue but I should answer my question about where the cluster token can be found post-install:
$ ssh rancher@
$ sudo cat /var/lib/rancher/rke2/server/node-token
$ sudo cat /etc/rancher/rancherd/config.yaml

Note latter file is created via /oem/99_custom.yaml so cluster token is also in there.


Bumping up version

5.34.36 -> 5.34.38

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


Can matterbridge be used to migrate Mattermost to Matrix?

Hi! I would like to migrate from one platform to another, but I don't see a way to export all data and then import it into the new platform.
Since Matterbridge can interact with both platforms, is there a way to move old posts and attachments from one to the other? Or is Matterbridge designed in a way that only new posts can be bridged?

as far as i know, matterbridge is only for live syncing (bridging) of chat messages, and not a chat migration service.
you might be able to extend the code or use matterbridge's API to add migration features, but i don't think anything like this is inbuilt

@qaisjp is correct, we don't have support for this and it's not in scope for this project.


Add set-json-class method

Add set-json-class method
Make role parameter optional
Use Cro::HTTP::Test

I wanted to open an issue, but I created a PR instead. I may also have gone a little bit overboard.
I was using Cro::HTTP::BodyParser::JSONClass with Cro::HTTP::Client and I realized I have to pass the body parser to the class and can't set it when using the get method.
Maybe there is another way or a better way that I'm unaware of, but I made the role parameter optional and added a set-json-class method which can change the JSON::Class class after instanciating Cro::HTTP::Client (before using .get for example).

Hi,
Thanks!  This looks somewhat like the right direction.  I'll merge but I may not release immediately as I'm going to need to test with the things that use this.
On reflection I think there may be a third thing that may be useful, that a method can be supplied that can choose which class should be used to deserialize to. This may be something for the future.


Feature/eslint

Looks solid! Only thing I ask is if you can add eslint-friendly-formatter to the lint command. (Also, sorry for the late reply.)

Got some free time. I'll go ahead and make the changes. Thanks again @sqlwwx


MINOR: doc change for minisr to clarify replicas in Kafka Config

This is a minor doc change to MinInSyncReplicasDoc to clarify what is a replica and further help users understand the importance of this configuration in relation to their producer configuration.
It didn't seem like a Jira was necessary but I am open to creating one if needed. I did not compile from source to test, no other code was changed.
This contribution is my original work and I license the work to the project under the project's open source license.
Thanks!
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

LGTM, had one comment


A question about generator model in MATLAB simulation model

Hello everyone，
In the process of using the MATLAB simulation model provided by openfast (i.e. Test01_SIG.mdl), I am a little confused about the generator model. May I ask how the generator model is built? Is this generator model an asynchronous generator model, a doubly-fed generator model, or some other type of generator model?
Thanks.

Dear @Tomedssa,
The simple induction generator (SIG) model of Test01_SIG.mdl is a model of the same SIG model available within ServoDyn via VSContrl = 0, GenModel = 1.  The SIG model is a very simple representation of an induction (asynchronous) generator.  See the old FAST v6 User's Guide for more information: https://openfast.readthedocs.io/en/main/_downloads/d8bd014121d6505cb25cf49bee5eaa80/Old_FAST6_UsersGuide.pdf.
Best regards,

Dear @jjonkman，
Thank you for your reply.When running the Test01_SIG.mdl model, I also encountered another problem, that is, when the pitch angle is changed, the electromagnetic torque and generator power generated  by the Test01_SIG.mdl model is negative.Do you know what caused it?The result is shown in the file.
picture.docx
Thanks.

Dear @Tomedssa,
It looks like your pitch controller has driven the rotor to near synchronous speed, where the power is close to zero.
FYI: The AWT-27CR2 wind turbine you are simulating by default has fixed pitch.
Best regards,

Dear @jjonkman，
Thank you for your reply.The type of wind turbine I use is 5MW_OC4Semi_WSt_WavesWN.

When I used the simple induction generator that came with Test01_SIG.mdl, I could not solve the problem of negative torque, so I used the torque control of the PI-controlled progressive generator, but the power was stable at about 4 MW.I think it may be caused by the random value of my PI parameter. So I would like to ask, when the torque control adopts PI control, is the determination of PI parameters obtained by progressive linearization near a certain operating point?
Thanks.

Dear @Tomedssa,
It sounds like you posted a similar question about PI parameters on the ROSCO GitHub site: https://github.com/NREL/ROSCO/issues/340.  I'll go ahead and close this issue and you can continue the discussion there.
Best regards,


Feature Request: Different Font for Extra Message and Clock

I would like to set the clock to a monospaced font but not the extra message under it.

hi @admiral-ackbar
Bit late of a response but this is something that should come with the rework on text displaying at some point.

Hi @admiral-ackbar
I have that feature now in beta2, you can now set a different font for every different "Info" :

Check the beta here : https://github.com/JohnCoates/Aerial/releases/tag/v1.6.5beta2

I've installed the beta and it works really well. I did find an issue however, the order of the message, clock, and location is the reverse of what is set in the settings. I'm sorry to send this to you directly instead of putting it on Github, but I don't normally work with Github so I don't know where to post an issue for a beta.
On Dec 18, 2019, 1:18 PM -0500, Guillaume Louel<EMAIL_ADDRESS>wrote:

No worries, if you reply to the email it gets posted on the website too. Thanks for the feedback!
So the order thing, here's how it works right now, the order you put them in the column (you can reorder) is the order they are drawn, from the corner then outwards of it.
So if you put location, message, then clock in the top left corner, they will appear in that order.
If you put the same thing in the bottom left corner, the order you see them is reversed (location is drawn first so it's closer to the corner, then the next one, etc).
That's not super intuitive, I'll see if I can make it reverse the order for the bottom positions.
Hope that makes sense ;)

@admiral-ackbar that bug is fixed in beta3, it also includes the battery thing (text only, no icons for now) : https://github.com/JohnCoates/Aerial/releases/tag/v1.6.5beta3


href for codeblock.css looks into post folder rather than root folder

in your reference to css and js files your refer to assets instead of /assets.
Therefore when building the site, jekyll look for css and js files in the post folder and not in the root.
When I correct locally it works fine, I will submit a pull request soon.
Sorry, my description of the problem might be a bit unclear, I will try to improve it.

@jdvp , sorry for the late answer, it works fine now thanks!
(I realize my fix was sloppy now!)

@AntoineGlacet Perfect!! Thank you.
Also no worries, the fact that you brought it up at all and pointed me in the direction of the fix was incredibly helpful!!


Composing non_zero function with injective fun is non_zero

Some basic missing lemmas about injective function composition.  See this Zulip thread

This is surely the most corrections that I have suggested on any single line of code!  :smile:

Hahaha I'm sorry! I really didn't look at it very closely since most of it was written by people that know more than me!

Ok this should be ready to go I think.

Thanks!
bors merge

I don't think there is ever a reason to write OfNat T 0 in mathlib over Zero T; and once you use the latter, to_additive works!
I pushed a change to that effect; please merge if you're happy with it
bors d+

bors r+

I don't think there is ever a reason to write OfNat T 0 in mathlib over Zero T; and once you use the latter, to_additive works!
I pushed a change to that effect; please merge if you're happy with it

Ah yes much better! I had only used OfNat as it was the minimal think it was asking to state and prove the lemmas. But Zero T is definitely better.


Android error - Table has no column named

Hi, i`m having a problem that only occours on some android devices. On most devices this problem doesnt occour.
I create this class:

i save the object here:

but on some devices, i get this error:
Fatal Exception: android.database.sqlite.SQLiteException
table PROFILE has no column named TYPE (code 1): , while compiling: INSERT OR REPLACE INTO PROFILE(EMAIL,AVATAR_KEY,PHONE,TYPE,ID,NAME,PROFILE_USER,PASSWORD,AVATAR_URL,PASSWORD_TEXT,GUID,AREA_GUID,DETAILED_POSITION,CHAT_ENABLE,COMPANY,POSITION_GUID) VALUES (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)

Can anybody help me please?
Thanks.

Can someone help me please?

if you check the error log, it say " table PROFILE has no column named TYPE " . it mean in database creation you still doesn't have created your columns properly. check if already your DB have that column " TYPE " , it's it's your table name it's wrong and must start with lowercase for tables instead of TYPE with uppercase.

Thanks,
But i already discovered the problem. Was the database version.
2018-06-04 12:38 GMT-03:00 Amin<EMAIL_ADDRESS>
if you check the error log, it say " table PROFILE has no column named
TYPE " . it mean in database creation you still doesn't have created your
columns properly. check if already your DB have that column " TYPE " , it's
it's your table name it's wrong and must start with lowercase for tables
instead of TYPE with uppercase.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/chennaione/sugar/issues/778#issuecomment-394400241,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYWKnqtNimrsrfEYvI4jxio3gZwfCZCIks5t5VSCgaJpZM4RLbfi
.

can you give me the solution for this TT i'm have the same problem

hi,
Yes, the problem was the db number version on manifest.xml
Em sáb, 8 de dez de 2018 05:46, ducvdps06156<EMAIL_ADDRESS>escreveu:

can you give me the solution for this TT i'm have the same problem
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/chennaione/sugar/issues/778#issuecomment-445440020,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYWKnn_WSrL2RNuQWruY9_WFcurtCezuks5u225wgaJpZM4RLbfi
.

Thanks you very much man
Vào 16:06, Th 7, ngày 08 tháng 12 năm 2018 dmaia17<EMAIL_ADDRESS>đã viết:

hi,
Yes, the problem was the db number version on manifest.xml
Em sáb, 8 de dez de 2018 05:46, ducvdps06156<EMAIL_ADDRESS>escreveu:

can you give me the solution for this TT i'm have the same problem
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/chennaione/sugar/issues/778#issuecomment-445440020,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AYWKnn_WSrL2RNuQWruY9_WFcurtCezuks5u225wgaJpZM4RLbfi
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/chennaione/sugar/issues/778#issuecomment-445444407,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AdTDc-ZGlmvS_1BzzCcioTzBpf-rTBCkks5u24EogaJpZM4RLbfi
.


[CGP-438] Log text messages in WalletAPI

Add LoggingWallet type with the ability to log messages and throw
errors

Nice.


error when use go get golang.org/x/sys/windows

kail linux 2019
[!] File not found! There's a problem with compiling. ../go/src/github.com/lxn/win/advapi32.go:10:2: cannot find package "golang.org/x/sys/windows" in any of:
/usr/lib/go-1.11/src/golang.org/x/sys/windows (from $GOROOT)
/root/go/src/golang.org/x/sys/windows (from $GOPATH)
https://imgur.com/a/wI4CMwk

please help me

Hello,
Do you have installed all dependencies described in readme?
Probably are missing golang.org/x/sys/windows.
Run: go get golang.org/x/sys/windows

i use this code  go get golang.org/x/sys/windows and i have error  package golang.org/x/sys/windows: unrecognized import path "golang.org/x/sys/windows" (parse https://golang.org/x/sys/windows?go-get=1: no go-import meta tags ())

Hello,
I've updated the dependencies manager. Could you try again using the new way?
Follow all steps described in readme (the package dependencies are been changed). https://github.com/tiagorlampert/CHAOS#how-to-install
Maybe, you could try updated you OS to the last version. I think it should be an issue with your OS.

when i use the code dep ensure error message  grouped write of manifest, lock and vendor: error while writing out vendor tree: failed to write dep tree: failed to export golang.org/x/sys: unable to deduce repository and source type for "golang.org/x/sys": unable to read metadata: unable to parse go-import metadata: XML syntax error on line 9: expected /> in element

Have you tried to reinstall your golang?

i get the same error wih dep ensure

I get that error too, but only on one of my computer. The other
one works fine, so I copy the file golang.org/x/sys to the location which could be any of the paths where your compiler couldn't find the package. Here is the golang package. Maybe this could work.
golang.org.zip

I get that error too, but only on one of my computer. The other
one works fine, so I copy the file golang.org/x/sys to the location which could be any of the paths where your compiler couldn't find the package. Here is the golang package. Maybe this could work.
golang.org.zip

Thanks very much for you .zip. It works!

I'm closing this old issue.
If the problem persist, please open a new issue.


Need testers for new reply and sentiment functionality

I added two new pieces of functionality that others might be interested in using.

The code will now collect data that lets you train an AI that can not only generate tweets, but also generate replies to existing tweets.
Second, the code can also measure the sentiment of tweets, so you can generate positive/neutral/negative tweets programmatically.

I've been testing it with my Data Journalist twitter bot account, and it's been surprisingly good at responding to some tweets.
You can find the code with the new functionality in the development branch of this repo below:
https://github.com/sdelgadoc/download-tweets-ai-text-gen-plus/tree/development
You can clone the repo with the following command:
git clone -b development https://github.com/sdelgadoc/download-tweets-ai-text-gen-plus.git

Although the repo's README explains what you need to do in detail to use the new functionality, below is a quick summary:

Install two new Python libraries (textblob: for sentiment analysis, tweepy: for access to the Twitter API)
Create a Twitter App to gain access to the Twitter API, which will be used to traverse reply trees because the twint library doesn't support the functionality
Input your Twitter API credentials into the new keys.py file

You can then run the script with the command below to generate text that can train an AI to reply, and includes sentiment information:
python3 download_tweets.py <twitter_username> None True False False False 3 reply

Let me know if you have any questions.
Below I am tagging folks that have used this repo, or that I have helped with issues in the past, in case they are interested:
@arceusisafish. @DeFiDude, @wradd, @RalphORama, @minimaxir, @YazzyYaz, @antherknee, @dmccaffrey12, @zhermi, @rewinded, @luisgabriel53, @faizankshaikh

Thank you to everyone who has tried the code.  I just updated to code to fix a corner case.
In commit https://github.com/sdelgadoc/download-tweets-ai-text-gen-plus/commit/e6b4d22d8bd8985f6ef03fdf5b9529465b29e0d1 I added code to turn REPLY tweets to ORIGINAL tweets if the parent tweet can't be found.
Previously, if the parent tweet of a REPLY tweet couldn't be found, the REPLY tweet's text was used as the parent tweet's text.
There are enough cases where the parent tweet can't be found, that the trained model responds often with  the parent tweet as the generated tweet

Thank you everyone for your feedback.  Folks have been running the new version of the script for about 3 weeks now, and it seems to be working fine.
I'm going to push merge this into the main branch.


downloads failed

Its probably me but I'd appreciate if someone could take a look at the log file and see what I am doing wrong or need to fix to make this work.  Thank you
instascrape.log

@swamped15 Emmm... I tried this on my Windows machine. Seems this bug occurs on Windows only. I will fix this very soon. Thanks for the bug report though!

@swamped15 ok I've already found the cause. It's the problem of the filename format. : is not allowed in filenames on Windows.

thanks for taking a look! much appreciated