sndfile not found on os x

yosemite 10.10.2
$ python
Python 2.7.9 |Continuum Analytics, Inc.| (default, Dec 15 2014, 10:37:34)
[GCC 4.2.1 (Apple Inc. build 5577)] on darwin
>>> import pysoundfile as sf
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/software/anaconda/envs/devpype/lib/python2.7/site-packages/pysoundfile.py", line 240, in <module>
    _snd = _ffi.dlopen('sndfile')
  File "/software/anaconda/envs/devpype/lib/python2.7/site-packages/cffi/api.py", line 121, in dlopen
    lib, function_cache = _make_ffi_library(self, name, flags)
  File "/software/anaconda/envs/devpype/lib/python2.7/site-packages/cffi/api.py", line 493, in _make_ffi_library
    backendlib = _load_backend_lib(backend, libname, flags)
  File "/software/anaconda/envs/devpype/lib/python2.7/site-packages/cffi/api.py", line 481, in _load_backend_lib
    raise OSError("library not found: %r" % (name,))
OSError: library not found: 'sndfile'

and the sndfile binaries and libraries are all available.
$ snd<TAB>
sndfile-cmp           sndfile-deinterleave  sndfile-metadata-get  sndfile-regtest
sndfile-concat        sndfile-info          sndfile-metadata-set  sndfile-salvage
sndfile-convert       sndfile-interleave    sndfile-play

and
$ ls /usr/local/Cellar/libsndfile/1.0.25/
AUTHORS			INSTALL_RECEIPT.json	bin			share
COPYING			NEWS			include
ChangeLog		README			lib

Did you use homebrew to install libsndfile?
Can you please show the contents of /usr/local/Cellar/libsndfile/1.0.25/lib/?
I don't know how this works on OSX, but on Linux, you can add additional search paths for libraries to /etc/ld.so.conf and afterwards run the command ldconfig as root (or with sudo).
Probably there is something similar for OSX?
Alternatively, as a quick work-around, you can try to copy (or symlink) the libsndfile.dylib to /usr/local/lib/, then it should be found automatically.

i did use homebrew.
$ ls /usr/local/Cellar/libsndfile/1.0.25/lib/
libsndfile.1.dylib	libsndfile.a		libsndfile.dylib	pkgconfig

i thought homebrew would take care of dynamic libraries in the path. i'll try it more explicitly.

Yes, as far as I understand, homebrew should automatically create a symbolic link to libsndfile.dylib in /usr/local/lib/.
Can you please check if it's there?

it's there. it might be one of those weird situations, where i might need to log out and log back in for brew's changes to have an effect.
$ ls -al /usr/local/lib/libsndfile.*
lrwxr-xr-x  1 satra  admin  50 Mar 15 11:48 /usr/local/lib/libsndfile.1.dylib -> ../Cellar/libsndfile/1.0.25/lib/libsndfile.1.dylib
lrwxr-xr-x  1 satra  admin  44 Mar 15 11:48 /usr/local/lib/libsndfile.a -> ../Cellar/libsndfile/1.0.25/lib/libsndfile.a
lrwxr-xr-x  1 satra  admin  48 Mar 15 11:48 /usr/local/lib/libsndfile.dylib -> ../Cellar/libsndfile/1.0.25/lib/libsndfile.dylib

I've seen a few weird issues with library names lately. Try renaming (or linking) the dylib to sndfile.dylib (no lib). I'm not sure if this changes anything, but it might be worth a shot.

Hey all - I had the same issue. Tried symlinking libsndfile.dylib from the homebrew directory to /usr/local/lib/ and it worked.

@satra and @choldgraf: did you try our latest 0.7.0 release?
Now we're shipping our own libsndfile.dylib, so the problem is hopefully gone!?!

Is it on pip? I can unlink my own libsndfile and upgrade to see if that works if it'd be useful.

Yes and yes, please!

Just tried it. Unlinking the sound library breaks pysoundfile v.6, and upgrading to v.7 fixes the issue, so I think we're good on this issue!

Great, thanks a lot!
I'm closing this ...

install this
sudo apt-get install libsndfile1


Feedback on GeoTagging project from GISCorps

See following feedback

Geo Tag - location tag is very time consuming to do each individual photo and the polygon shape for area wouldn't line up. It would be great if the photos that were taken at the same location be added together as album and tag location only once.
(feedback by Nattawadee Panikom<EMAIL_ADDRESS>from Shoreh’s list)
Geo tagging photos for the shelter project is overly time consuming. It seems like if you were to import a flickr album where all of the photos come from the same camp, it would be possible to tag all of these photos at once. Also, if there is already a searchable point or outline of the area (i.e. Iraq or Al Zaatari refugee camp) in the map, I should be able to select that rather than outlining it over and over again.
(feedback by Emily Hultman<EMAIL_ADDRESS>from Shoreh’s list)
Geo tagging photos for the shelter project was tedious. I feel like if there is already a searchable point or outline of the area in the map, then I should be able to select it rather than have to outline it over and over again. Also to draw an outline or place a point should be options when geotagging, the tool was unreliable, sometimes allowing to place a point, other times allowing me to place a polygon.
(feedback by Melanie Harris<EMAIL_ADDRESS>from Shoreh’s list)

ellie to write description for why we use polygons, Jeremy to write help/tutorial for geotagging

to be done before GISCorps data sprint weekend 29th august

This is complete, closing this issue


Lyrics of Russian songs will not download even though they are in Spotify.

Command prompt outputs:  Skipping lyrics for УННВ - Убиты но не вами: lyrics not available
The song has lyrics when you click on it on Spotify. I tested and it worked on songs with English lyrics. Each song does have a .lrc file with it but it only shows the time of the first lyric.

I believe this is related to https://github.com/zotify-dev/zotify/commit/8cfd27407e8bacc50d43c8983a97443b29a2b7cf. Please ensure you have the latest version of Zotify installed.
If this is still occurring on the latest version please supply your OS and system locale.

All working fine now. Thanks.


Add "Remember me" checkbox

Add optional username and/or password persistency for login.

@saientzg I see that you've closed this issue, but could you share any more info on your original thinking?

I'm sorry. I created this issue by mistake (wrong project) so I closed it immediately. Someone with enough permissions should probably delete it.

@saientzg no worries


⚠ Bofrost.com has degraded performance

In 0c8bd23, Bofrost.com (https://www.bofrost.com) experienced degraded performance:

HTTP code: 200
Response time: 1040 ms

Resolved: Bofrost.com performance has improved in 98fdd94 after 6 minutes.


CI: Add configuration for pre-commit-ci

regarding the issue stated in PR #134
pre-commit-ci now won't run flake8 and mypy as this is already handled in a separate job by GitHub workflows.

Codecov Report
Base: 53.22% // Head: 53.22% // No change to project coverage :thumbsup:

Coverage data is based on head (1c4bb82) compared to base (008fc2d).
Patch has no changes to coverable lines.

:exclamation: Current head 1c4bb82 differs from pull request most recent head 19149e0. Consider uploading reports for the commit 19149e0 to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #135   +/-   ##
=======================================
  Coverage   53.22%   53.22%
=======================================
  Files          18       18
  Lines         635      635
  Branches      150      141    -9
=======================================
  Hits          338      338
  Misses        284      284
  Partials       13       13

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

we decided to run both in parallel


Update link to Monax blog post

Hello @lanzafame - the readme is generated automatically after recent changes so you need to change the data on data/articles.yml and then run yarn build:readme 😄

@hacdias I have made that change. Not sure why jenkins is complaining though, any ideas?

@lanzafame thanks! The Jenkins failure isn't related to your update so I'll merge it.
/cc @VictorBjelkholm


⚠ Fox Sports has degraded performance

In bf802e4, Fox Sports (https://foxsports.com) experienced degraded performance:

HTTP code: 200
Response time: 1370 ms

Resolved: Fox Sports performance has improved in c204163.


SUPER SLOW HTTP GET

Gogs version (or commit ref): https://hub.docker.com/r/freenas/gogs/
Operating system: FreeNAS
Database (use [x]):

[ ] PostgreSQL
[ ] MySQL
[ ] MSSQL
[X] SQLite

Can you reproduce the bug at https://try.gogs.io:

[ ] Yes (provide example URL)
[ ] No
[X] Not relevant

Description
Since yesterday everything goes fine. Now:
[Macaron] 2017-03-27 21:14:47: Started GET /pulls for <IP_ADDRESS>
[Macaron] 2017-03-27 21:15:17: Completed GET /pulls 200 OK in 30.026839791s
I have already reinstalled everything but nothing...

Not enough information to understand what you're saying...

I think that 30s for retrieving a page in a local ethernet gigabit LAN are a problem! 😅

Based on the information you provide:

You're using on NAS and such devices could be busy at the time you visit Gogs page
Can't prove this is a general problem of Gogs
Looks like random report with dead ending...

Ok, but i'm the admin of the system:

The system wasn't busy, are 2 days that i'm trying to use my Gogs.
I'm running 6 docker without problem since 2 years and this is the first problem.
2 days of try are not random report...

I have never experienced anything like this on a VPS. FreeNAS runs FreeBSD, maybe related @Unknwon?

@Fastidious that's what I think.
@Jacopx

at very basic, no Gogs version info.
Can't prove this is a general problem of Gogs
Speaking of time, I've been using Gogs for 3 years slow page loading time always relates to my VPS CPU is busy doing something else.

The version is: <IP_ADDRESS>7
I'm sure that my CPU isn't busy.

Should have more insights once we have https://github.com/gogits/gogs/issues/4141.


[LiveComponent] No selected  treated differently when submitted from a Live Component

This is a bit of a weird one. If I for example use an EntityType or a ChoiceType to generate a <select> element, and I do not use a placeholder value, we will get HTML such as:
<select>
  <option value="1">Option One</option>
  <option value="2">Option Two</option>
</select>

When this is rendered by the browser, if no option is selected, and there is no placeholder option, the first option "Option One" will be shown, but without a selected attribute.
In a normal Symfony form in a standard POST submission, the browser seems to send the "Option One" as though the user had physically selected it. For example, a NotBlank() validation would PASS.
The Problem
If you then move this form into a LiveComponent, the behaviour changes.
Submitting the form without touching the select element does NOT assume that the first element is implicitly selected, and null is sent as the select field's value.
This means any NotBlank() validation FAILS, even though as far as the user is concerned, the "Option One" was selected (it was shown as the selected entry in the form field, even though they didn't physically click on it).
This then makes a mess when submitting the form, as you get a validation error, and you have to go and click and select the option that is already, as far as you the user is concerned, selected.
I'm guessing this is to do with the way that the Live Component's JS submits the form, and that this is differing in this case with a standard browser form submit.

For the moment I have managed to get around this problem by automatically selecting the first <option> if there is no placeholder or existing selected option:
export default class extends Controller {

    connect () {
        const selects = this.element.querySelectorAll('select');

        selects.forEach((select) => {
            if (select.querySelector('[value=""]') === null && select.querySelector('[selected]') === null) {
                select.querySelector('option:first-child').setAttribute('selected', 'selected');
                select.dispatchEvent(new Event('change', { bubbles: true }));
            }
        })
    }
}

As far as I am aware this issue is still outstanding.

I have not tested with the latest release yet, so do not know if it's still an issue. Please keep the issue open for now.

I don't believe this has been addressed yet, as we've encountered several issues related to it. Would you be interested in submitting a PR?


Federation schema throws error while using multiple Option inputs

When start Apollo gateway server, I got error:
Encountered error when loading schema at http://localhost:4002: Syntax Error: Expected Name, found :

with 2 inputs (Option type) on top_products fn in examples package, as follow:
#[Object(extends)]
impl Query {
    async fn top_products<'a>(
        &self,
        ctx: &'a Context<'_>,
        from: Option<i32>,
        to: Option<i32>,
    ) -> &'a Vec<Product> {
        ctx.data_unchecked::<Vec<Product>>()
    }
}

But remove one Option, this is Ok:
#[Object(extends)]
impl Query {
    async fn top_products<'a>(
        &self,
        ctx: &'a Context<'_>,
        from: i32,
        to: Option<i32>,
    ) -> &'a Vec<Product> {
        ctx.data_unchecked::<Vec<Product>>()
    }
}

I fixed this in v1.16.10. 😁

Thanks,
The latest version seems not work for me, I built with rustc 1.44.1.
error[E0599]: no method named `to_json` found for reference `&context::QueryPathNode<'_>` in the current scope
  --> /Users/annihilus/.cargo/registry/src/github.com-1ecc6299db9ec823/async-graphql-1.16.11/src/model/directive.rs:76:1
   |
76 | #[Object(internal)]
   | ^^^^^^^^^^^^^^^^^^^ method not found in `&context::QueryPathNode<'_>`
   |
   = note: this error originates in an attribute macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `to_json` found for reference `&context::QueryPathNode<'_>` in the current scope
  --> /Users/annihilus/.cargo/registry/src/github.com-1ecc6299db9ec823/async-graphql-1.16.11/src/model/enum_value.rs:10:1
   |
10 | #[Object(internal)]
   | ^^^^^^^^^^^^^^^^^^^ method not found in `&context::QueryPathNode<'_>`
   |
   = note: this error originates in an attribute macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `to_json` found for reference `&context::QueryPathNode<'_>` in the current scope
  --> /Users/annihilus/.cargo/registry/src/github.com-1ecc6299db9ec823/async-graphql-1.16.11/src/model/field.rs:12:1
   |
12 | #[Object(internal)]
   | ^^^^^^^^^^^^^^^^^^^ method not found in `&context::QueryPathNode<'_>`
   |
   = note: this error originates in an attribute macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `to_json` found for reference `&context::QueryPathNode<'_>` in the current scope
  --> /Users/annihilus/.cargo/registry/src/github.com-1ecc6299db9ec823/async-graphql-1.16.11/src/model/input_value.rs:11:1
   |
11 | #[Object(internal)]
   | ^^^^^^^^^^^^^^^^^^^ method not found in `&context::QueryPathNode<'_>`
   |
   = note: this error originates in an attribute macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `to_json` found for reference `&context::QueryPathNode<'_>` in the current scope
  --> /Users/annihilus/.cargo/registry/src/github.com-1ecc6299db9ec823/async-graphql-1.16.11/src/model/schema.rs:11:1
   |
11 | #[Object(internal)]
   | ^^^^^^^^^^^^^^^^^^^ method not found in `&context::QueryPathNode<'_>`
   |
   = note: this error originates in an attribute macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `to_json` found for reference `&context::QueryPathNode<'_>` in the current scope
  --> /Users/annihilus/.cargo/registry/src/github.com-1ecc6299db9ec823/async-graphql-1.16.11/src/model/type.rs:46:1
   |
46 | #[Object(internal)]
   | ^^^^^^^^^^^^^^^^^^^ method not found in `&context::QueryPathNode<'_>`
   |
   = note: this error originates in an attribute macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `to_json` found for reference `&context::QueryPathNode<'_>` in the current scope
 --> /Users/annihilus/.cargo/registry/src/github.com-1ecc6299db9ec823/async-graphql-1.16.11/src/types/connection/page_info.rs:4:1
  |
4 | #[SimpleObject(internal)]
  | ^^^^^^^^^^^^^^^^^^^^^^^^^ method not found in `&context::QueryPathNode<'_>`
  |
  = note: this error originates in a derive macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `to_json` found for reference `&context::QueryPathNode<'_>` in the current scope
  --> /Users/annihilus/.cargo/registry/src/github.com-1ecc6299db9ec823/async-graphql-1.16.11/src/types/query_root.rs:13:1
   |
13 | #[SimpleObject(internal, name = "_Service")]
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ method not found in `&context::QueryPathNode<'_>`
   |
   = note: this error originates in a derive macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0277]: the trait bound `async_graphql_parser::value::Value: context::_IMPL_SERIALIZE_FOR_Variables::_serde::Serialize` is not satisfied
  --> /Users/annihilus/.cargo/registry/src/github.com-1ecc6299db9ec823/async-graphql-1.16.11/src/context.rs:26:22
   |
26 | pub struct Variables(Value);
   |                      ^^^^^ the trait `context::_IMPL_SERIALIZE_FOR_Variables::_serde::Serialize` is not implemented for `async_graphql_parser::value::Value`
   |
   = note: required by `context::_IMPL_SERIALIZE_FOR_Variables::_serde::Serializer::serialize_newtype_struct`

error[E0277]: the trait bound `async_graphql_parser::pos::Pos: context::_IMPL_SERIALIZE_FOR_Variables::_serde::Serialize` is not satisfied
   --> /Users/annihilus/.cargo/registry/src/github.com-1ecc6299db9ec823/async-graphql-1.16.11/src/extensions/logger.rs:98:17
    |
98  | /                 error!(
99  | |                     target = "async-graphql",
100 | |                     "Parse error",
101 | |                     id = self.id,
...   |
105 | |                     message = err.message
106 | |                 );
    | |__________________^ the trait `context::_IMPL_SERIALIZE_FOR_Variables::_serde::Serialize` is not implemented for `async_graphql_parser::pos::Pos`
    |
   ::: /Users/annihilus/.cargo/registry/src/github.com-1ecc6299db9ec823/serde_json-1.0.52/src/value/mod.rs:954:8
    |
954 |       T: Serialize,
    |          --------- required by this bound in `xlog::serde_json::to_value`
    |
    = note: required because of the requirements on the impl of `context::_IMPL_SERIALIZE_FOR_Variables::_serde::Serialize` for `&async_graphql_parser::pos::Pos`
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0277]: the trait bound `async_graphql_parser::pos::Pos: context::_IMPL_SERIALIZE_FOR_Variables::_serde::Serialize` is not satisfied
   --> /Users/annihilus/.cargo/registry/src/github.com-1ecc6299db9ec823/async-graphql-1.16.11/src/extensions/logger.rs:109:17
    |
109 | /                 error!(
110 | |                     target = "async-graphql",
111 | |                     "Query error",
112 | |                     id = self.id,
...   |
117 | |                     error = err,
118 | |                 );
    | |__________________^ the trait `context::_IMPL_SERIALIZE_FOR_Variables::_serde::Serialize` is not implemented for `async_graphql_parser::pos::Pos`
    |
   ::: /Users/annihilus/.cargo/registry/src/github.com-1ecc6299db9ec823/serde_json-1.0.52/src/value/mod.rs:954:8
    |
954 |       T: Serialize,
    |          --------- required by this bound in `xlog::serde_json::to_value`
    |
    = note: required because of the requirements on the impl of `context::_IMPL_SERIALIZE_FOR_Variables::_serde::Serialize` for `&async_graphql_parser::pos::Pos`
    = note: required because of the requirements on the impl of `context::_IMPL_SERIALIZE_FOR_Variables::_serde::Serialize` for `&&async_graphql_parser::pos::Pos`
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0277]: the trait bound `async_graphql_parser::pos::Pos: context::_IMPL_SERIALIZE_FOR_Variables::_serde::Serialize` is not satisfied
   --> /Users/annihilus/.cargo/registry/src/github.com-1ecc6299db9ec823/async-graphql-1.16.11/src/extensions/logger.rs:122:21
    |
122 | /                     error!(
123 | |                         target = "async-graphql",
124 | |                         "Validation error",
125 | |                         id = self.id,
...   |
129 | |                         error = err.message,
130 | |                     );
    | |______________________^ the trait `context::_IMPL_SERIALIZE_FOR_Variables::_serde::Serialize` is not implemented for `async_graphql_parser::pos::Pos`
    |
   ::: /Users/annihilus/.cargo/registry/src/github.com-1ecc6299db9ec823/serde_json-1.0.52/src/value/mod.rs:954:8
    |
954 |       T: Serialize,
    |          --------- required by this bound in `xlog::serde_json::to_value`
    |
    = note: required because of the requirements on the impl of `context::_IMPL_SERIALIZE_FOR_Variables::_serde::Serialize` for `std::vec::Vec<async_graphql_parser::pos::Pos>`
    = note: required because of the requirements on the impl of `context::_IMPL_SERIALIZE_FOR_Variables::_serde::Serialize` for `&std::vec::Vec<async_graphql_parser::pos::Pos>`
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

Cargo files as follow:
[dependencies]
actix-web = "2.0.0"
actix-rt = "1.1.1"
async-graphql = "1.16.11"
async-graphql-actix-web = "1.16.10"
bigdecimal = { version = "0.1.0", features = ["serde"] }
elasticsearch = "7.7.1-alpha.1"
diesel = { version = "1.4.5", features = ["postgres", "serde_json", "numeric" ] }
num-traits = "0.2.12"
serde = { version = "1.0", features = ["derive"] }
serde_json = "1.0"

Cargo update

It works.
Thank you :D. This issue should be closed.


Terminal Font

Hi, I was trying to use this repository I am very fascinated by it, so kudos for this project, however the thing I didn't understand how to do was to put the "real" terminal font on the one in the web page also trying with "font-family" and importing the font doesn't work, I wanted to know if it was possible, either to have the font imported by itself automatically in the web page or even importing the font file set it to the one you see in the web page. Thanks and again congratulations on this project! 😋

@HirAvanCniK Thanks!, At the moment the font from the "real" terminal does not automatically get used with the terminal in your browser.
You can however set up the font of xtermJS https://github.com/xtermjs/xterm.js/issues/1534#issuecomment-404125484
Which means if you know the font used on the "real" terminal you can set it for the xtermJS


Mock Node ExpressJs function always returns null

event object = {
"httpMethod": "GET",
"body": "{"name": "Amplify"}",
"path": "/test",
"resource": "/{proxy+}",
"queryStringParameters": {}
}
app.js get method =
/**********************

Example get method *
**********************/

app.get("/test", function (req, res) {
// Add your code here
console.log("test");
res.json({ success: "get call succeed!", url: req.url });
});
Which Category is your question related to?
Amplify invoke function (mock functino)
Amplify CLI Version
4.18.0
What AWS Services are you utilizing?
Amplify mock function to locally host a nodejs based lambda function for testing.
Provide additional details e.g. code snippets
Mocking the function always returns null, no matter what event is used whether its valid or not.
PS C:\Users\User\Desktop\Startup\amplify_sandbox> amplify mock function testFunction
? Provide the path to the event JSON object relative to
C:\Users\User\Desktop\Startup\amplify_sandbox\amplify\backend\function\testFunction src/event.json
Starting execution...
EVENT: "{"httpMethod":"GET","body":"{\"name\": \"Amplify\"}","path":"/test","resource":"/{proxy+}","queryStringParameters":{}}"
Result:
null
Finished execution.

Any help would appreciated!

I've found a workaround to locally test my express js function. using nodemon to invoke the app.js and using dotenv to locally store my env variables, but this is very tedious. Maybe a feature that uses nodemon to host a local server (supports hot reload) and pass env variables in the process would be beneficial!

This broke recently - the awsServerlessExpress doesn't even appear to boot up before returning a response.

Looks like the serverless template that comes out of the box uses the deprecated context.succeed() lambda operation. Until we can get a release out with an update to the template, you'll need to update the last line of the handler in index.js to return awsServerlessExpress.proxy(server, event, context, 'PROMISE').promise; That will allow mock to work with the handler.
As for the additional environment variable support, we are actively working on a more comprehensive solution to that problem

You may also want to follow #4019 regarding issues with mock not working with the callback function. @bboure is working on a fix there

This should be fixed in the latest release of the CLI (4.20.0) thanks to @bboure!


Add .TextControl--currency modifier

Unlike .TextControl--search, this field requires validation so is more complex.

Uses CSS multiple backgrounds.
Creates variables for common backgrounds and position patterns used in no-modifier version.
Creates new .is-populated state that should be set on fields by Angular, as this can't be done via CSS.

Can be used as a template for similar types in future.

 Just needs demo sorting out @ohskylab

@chrisvxd Updated demo to match the structure I've used for rb-page-title i.e. breaking Angular and Static parts out into separate sections, Angular first. OK?


Converting a MOS object with a circular structure

I'm submitting a ...
[x] bug report
[ ] feature request
[ ] question about the decisions made in the repository
[ ] question about how to use this project

I'm doing some tests with an iNews Mos Gateway. When there is no MOS object in the stories, everything works fine. When I add a MOS object to a story, I get this error while it converts XML to JSON  :
TypeError: Converting circular structure to JSON\n    --> starting at object with constructor 'Object'\n    |     property 'mos' -> object with constructor 'Object'\n    --- property 'parent' closes the circle
The problem seems to be that the iNews MOS object starts with the same <mos> root tag than the iNews story itself :
<mos>
  ...
    <roStorySend>
    ...
      <mosExternalMetadata>
        <mosPayload>
        ...
          <nsml xmlns:nsml="http://www.avid.com">
          ...
            <aeset-atts>
              <attachment id="1">
                <AttachmentContent>
                  <mos>
                    <mosID>
		         VIZRT
	            </mosID>
                     ...
                  </mos>
                </AttachmentContent>
              </attachment>
            </aeset-atts>
         </nsml>
      </mosPayload>
    </mosExternalMetadata>
  </roStorySend>
</mos>

When I replace the MOS object first tag (<mos>) by a modified tag (<_mos>), it fixes the problem :
<mos>
  ...
    <roStorySend>
    ...
      <mosExternalMetadata>
        <mosPayload>
        ...
          <nsml xmlns:nsml="http://www.avid.com">
          ...
            <aeset-atts>
              <attachment id="1">
                <AttachmentContent>
                  <_mos>
                    <mosID>
		         VIZRT
	            </mosID>
                     ...
                  </_mos>
                </AttachmentContent>
              </attachment>
            </aeset-atts>
         </nsml>
      </mosPayload>
    </mosExternalMetadata>
  </roStorySend>
</mos>

If you want me to submit a pull request with the code I used to fix the problem, let me know !

hmm, that's a strange bug indeed!
I did a little digging and it seems like there is a bug in the code that deals with reading the incoming message chunks. I think I've found the root cause and have implemented a fix in the PR #85.
@PascalViauRC would you be able to give that a spin (npm install mos-connection@3.0.5-nightly-fix-multiple-mos-tags-20231214-120351-59cacb2.0), to see if it helps?

@nytamin It fixes the problem, thanks !


podman denies opening a file for writing as root owned by a different user on /tmp

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
podman denies opening a file for writing as root owned by a different user on /tmp
(2500661 4 drwxrwxrwt 1 root root 4096 Dec  5 16:56 /tmp)
Steps to reproduce the issue:

start container as root: podman run --rm -it centos:centos8 /bin/bash

create a file on /tmp, change ownership, open file for writing

touch /tmp/a && chown mail:mail /tmp/a && vi /tmp/a (actually write something to it in vi and exit :x) - fails
or
touch /tmp/a && chown mail:mail /tmp/a && python3 -c "open('/tmp/a', 'w')" - fails
(but requires installing python3 beforehand: dnf install -y python3
whereas shell redirection works
touch /tmp/a && chown mail:mail /tmp/a && echo "foo" > /tmp/a - succeeds

do the same steps on docker - succeeds

Describe the results you received:
PermissionError: [Errno 13] Permission denied: '/tmp/a'
Describe the results you expected:
changed file contents
Additional information you deem important (e.g. issue happens only occasionally):

selinux on fedora-30 Podman host is disabled

[root@fedora-30 ~]# getenforce
Disabled

disabling seccomp doesn't resolve this issue

podman run --security-opt aaseccomp=unconfined --rm -it centos:centos8 /bin/bash

Output of podman version:
Version:            1.6.2
RemoteAPI Version:  1
Go Version:         go1.12.10
OS/Arch:            linux/amd64

Output of podman info --debug:
debug:
  compiler: gc
  git commit: ""
  go version: go1.12.10
  podman version: 1.6.2
host:
  BuildahVersion: 1.11.3
  CgroupVersion: v1
  Conmon:
    package: conmon-2.0.2-1.fc30.x86_64
    path: /usr/bin/conmon
    version: 'conmon version 2.0.2, commit: a89d21975ee86e84e0b0e1c0f887687582f4b0e3'
  Distribution:
    distribution: fedora
    version: "30"
  MemFree: 243286016
  MemTotal:<PHONE_NUMBER>
  OCIRuntime:
    name: runc
    package: runc-1.0.0-95.rc9.gitc1485a1.fc30.x86_64
    path: /usr/bin/runc
    version: |-
      runc version 1.0.0-rc9+dev
      commit: 0840802d505e28d3adcbc7a275cbeadbdf64ddec
      spec: 1.0.1-dev
  SwapFree:<PHONE_NUMBER>
  SwapTotal:<PHONE_NUMBER>
  arch: amd64
  cpus: 2
  eventlogger: journald
  hostname: fedora-30
  kernel: 5.3.11-200.fc30.x86_64
  os: linux
  rootless: false
  uptime: 242h 25m 39.11s (Approximately 10.08 days)
registries:
  blocked: null
  insecure:
  - jenkinsng.admin.frm2
  search:
  - docker.io
  - registry.fedoraproject.org
  - quay.io
  - registry.access.redhat.com
  - registry.centos.org
  - registry.redhat.io
store:
  ConfigFile: /etc/containers/storage.conf
  ContainerStore:
    number: 1
  GraphDriverName: overlay
  GraphOptions:
    overlay.mountopt: nodev,metacopy=on
  GraphRoot: /var/lib/containers/storage
  GraphStatus:
    Backing Filesystem: extfs
    Native Overlay Diff: "false"
    Supports d_type: "true"
    Using metacopy: "true"
  ImageStore:
    number: 10
  RunRoot: /var/run/containers/storage
  VolumePath: /var/lib/containers/storage/volumes

Package info (e.g. output of rpm -q podman or apt list podman):
podman-1.6.2-2.fc30.x86_64

Additional environment details (AWS, VirtualBox, physical, etc.):
fedora-30 VM is running on macOS Parallels host system

@rhatdan @baude @vrothberg @giuseppe PTAL - looked at this one for a while in IRC, came away stumped

do the same steps on docker - succeeds

I just installed docker on my f30 VM and tried again and it fails as well whereas it doesn't fail in my docker environment on my macOS host. Must be an issue with the configuration of the host system though.

Just to double check: it only fails in vi when trying to write? Opening works?

Yes and shell redirection does:
openat(AT_FDCWD, "a", O_WRONLY|O_CREAT|O_TRUNC, 0666) = -1 EACCES (Permission denied)
openat(AT_FDCWD, "a", O_WRONLY|O_TRUNC) = 3

apparently this fails on the fedora-30 host in general
touch /tmp/a && chown mail:mail /tmp/a && vi /tmp/a
or
touch /tmp/a && chown mail:mail /tmp/a && python3 -c "open('/tmp/a', 'w')"

that is controlled by the fs.protected_regular sysctl.
Can you try sysctl fs.protected_regular=0 and see if it changes the result you get?

@giuseppe This resolves the issue on the host as well as on the container. Thanks.

This is not a podman issue.


Navbar +Fixed all issue .

Navbar + Carousel issues fixed. Kindly see and merge it

@user23ayush I have begun reviewing this PR.
Be in touch soon.


update for support of React v16 please

ReactReconciler
ReactUpdates
createClass

please update

update please

think this project is dead.

*- justin *| @framerate http://twitter.com/framerate | framerate.io
On Thu, Feb 8, 2018 at 4:38 AM, Bryan Yang<EMAIL_ADDRESS>wrote:

update please
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Flipboard/react-canvas/issues/169#issuecomment-364099397,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAEiM4zB4OsaPxE0qzaifz-LjRJihzIiks5tSurRgaJpZM4Q74Ta
.

Any news there?

Any news?

I have a fork that looks like it's starting to work with React 16 here: http://github.com/gfodor/react-canvas

npm i @craigmorton/react-canvas tried
but got this
<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
why?

update please!!

@rardoz But react-konva can't draw DOM primitives, it only draw Canvas primitives.

try revas: https://github.com/pinqy520/revas , React v16 + Yoga


Updates to bdist_nuitka

I'm really excited about this usage of nuitka, it provides a very clean and controlled output being able to produce fully compiled wheels ready to distribute and install.
I'd actually started making my own module to integrate nuitka into setuptools before I found what you already had built in.
I've been testing/using this on windows, however this PR doesn't work as is on windows due to getExecutablePath("nuitka") failing in my virtualenv. I've been using this branch rebased on #36 where it all works perfectly.
Contents of PR:

My initial tests of bdist_nuitka resulted in broken wheels with incorrect paths inside the wheel package.
For example, on my pc the package I'm compiling is C:\Users\anl\src\example_package\setup.py
When I built the wheel and then open is as a zip there was a deep folder structure inside it like
zip:\Users\anl\src\example_package\.venv\lib\site-packages\example_package.pyd.
I found all the stuff starting at line 96 in the install phase was unnecessary once the wheel class was pre-informed of it being a binary module and self._buildPackage was called with an absolute path.

I regularly find issues compiling packages with python files not being included due to them not being explicitly imported by other files in the package.
The changes starting with recurse_packages is designed to get around this by compiling and including all python files in the wheel. The actual nuitka compiling is done against the files that have been staged for building the wheel so the normal methods of setuptools to include the correct files in the wheel are observed.
This doesn't yet do anything to work around the issues with other resources/files that would have been included in the wheel, these are still deleted along with the source. I'd like to resolve this but that will be a follow up pr.

The final change in setup.py registers the bdist_nuitka command when nuitka is installed so you no longer need to explicitly reference the module when running.
old: python setup.py --command-packages=nuitka.distutils clean -a bdist_nuitka
new: python setup.py bdist_nuitka

Great stuff. Regarding the recursion, I was going to add a --include-module/package option. Right now the --recurse options only allows to go there, but not force it, in fact only recurse-directory with --recurse-to combined does, which requires to find that directory manually. However I have not done anything to that end yet for real. Depending on how complex your package is, you might not find that necessary.
The others things read great. Going to look at this before next release definitely.

Having looked at it, basically what you do, is you try to make it include every Python file that was copied there by distutils, rather than my idea of relying on the "PACKAGES" selector from the setup arguments, which as I pointed out, is not yet even implemented.
Having "distutils" do the heavy lifting seems very fit. I think we ought to have a better command line option to tell Nuitka those things, or else it will get very long.
I am going to try it out later this week. Thanks a lot and let me know when you think it is ready.

I just added some fairly major changes to the bdist_nuitka handing.
python setup.py bdist_nuitka still creates a compiled wheel the same as previously, however now if there are any other files in the wheel (project assets/images/libraries) these are kept in the existing folder structure and the raw python files deleted. You get the compiled pyd at the top level and the original folder sitting next to it, all in the wheel.
I've also added a new setup.py option to use nuitka for all builds; build_with_nuitka=True
For eample, in your package you want compiled with nuitka, you add this to setup.py:
from setuptools import setup
setup(
    name='example',
    packages=['example'],
    description='test package',
    setup_requires=['nuitka'],
    build_with_nuitka=True
)

With this setting, any setuptools operation which should build your package will run it though nuitka, such as python setup.py bdist_wheel, python setup.py install or pip install ./example
ps. This allows easy integration with briefcase (https://github.com/pybee/briefcase) to allow your python application to be compiled by nuitka and packaged into a distributable installer/application all in one operation.

Merging this for coming pre-release, expect rebases potentially


Query should be sign-able

Discussed in https://github.com/hashgraph/hedera-sdk-java/discussions/578

Originally posted by danielakhterov January 19, 2021
Currently queries and transactions are mostly distinct on the fact a transaction is sign-able, while a query is not. This doesn't make sense as a query has a payment transaction within it, and should allow those payment transactions to be signed by multiple keys if necessary.
If both transactions and queries are to now going to be sign-able, perhaps this code could be abstracted away into a new private type called Request, or we could shove this into Executable like we did for nodeAccountIds, but I'm not a big fan of  that.
This is what I have in mind
abstract class Request<SdkRequestT extends Request<SdkRequestT, ProtoRequestT, ResponseT, O>, ProtoRequestT, ResponseT, O>
    extends Executable<SdkRequestT, ProtoRequestT, ResponseT, O> {

    public abstract SdkRequestT freezeWith(@Nullable Client client);

    public SdkRequestT freeze() {
        ...
    }

    public final SdkRequestT sign(PrivateKey privateKey) {
        ...
    }

    public SdkRequestT signWith(PublicKey publicKey, Function<byte[], byte[]> transactionSigner) {
        ...
    }

    public SdkRequestT signWithOperator(Client client) {
        ...
    }

    public SdkRequestT addSignature(PublicKey publicKey, byte[] signature) {
        ...
    }

    public Map<AccountId, Map<PublicKey, byte[]>> getSignatures() {
        ...
    }
}

We could move most of the functionality from Transaction into this new Request type which would simply both Transaction and Query. For instance currently Transaction has these fields
    protected List<com.hedera.hashgraph.sdk.proto.Transaction> transactions = Collections.emptyList();
    protected List<com.hedera.hashgraph.sdk.proto.SignedTransaction.Builder> signedTransactions = Collections.emptyList();
    protected List<SignatureMap.Builder> signatures = Collections.emptyList();

If we move these fields into Request then Query can treat transactions as the payment transactions, while Transaction continues treating these fields as normally does.

Moved: https://github.com/hashgraph/hedera-sdk/issues/60


Roll engine 1a8534cb9304..e44c5d99c9f3 (1 commits)

https://github.com/flutter/engine/compare/1a8534cb9304...e44c5d99c9f3
git log 1a8534cb9304dd7d5f2c202f8abf422499f4b724..e44c5d99c9f3991afb73d55447725665e9dc236b --no-merges --oneline
e44c5d99c Roll src/third_party/skia 2444c0e9aa23..10d172169f2d (1 commits) (flutter/engine#8740)
The AutoRoll server is located here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
If the roll is causing failures, please contact the current sheriff (liyuqian@google.com), and stop
the roller if necessary.

Auto-roller completed checks. About to merge.


Streaming results for List Keys/Buckets, 2i, and MR

This PR adds support for streaming results in:

List Keys Command + Operation
List Buckets Command + Operation
Secondary Index Commands + Operation
Map Reduce Commands + Operation

This was a very interesting exercise in creating a new results return method from top-to-bottom, while not breaking/changing existing APIs.

[ ] Unit tests for your change
[X] Integration tests
[ ] Documentation in code
[X] A docs.basho.com PR for public api changes: basho/basho_docs#2270

Looks like a a good first step. IMO it would be good to have as an overall goal to make more use of lambdas, not just as callbacks for asynchronous functions but as a tool in the quiver to reduce garbage. If you follow the code path through a request you see a lot of objects being created to support a single operation. Some of that can't be avoided but there are places I think a lambda-centric approach (versus creating a concrete implementation of some abstract class and instantiating it) would be more efficient.
That said, we're probably not at a level where heap usage, GC, and those other considerations are very high priority.

Indeed, I was lucky to get away with only 4 new class files, and I think I
did a fairly good job about reuse, but there is always room to improve.
On Thu, Oct 20, 2016 at 9:18 AM, Jon Brisbin<EMAIL_ADDRESS>wrote:

Looks like a a good first step. IMO it would be good to have as an overall
goal to make more use of lambdas, not just as callbacks for asynchronous
functions but as a tool in the quiver to reduce garbage. If you follow the
code path through a request you see a lot of objects being created to
support a single operation. Some of that can't be avoided but there are
places I think a lambda-centric approach (versus creating a concrete
implementation of some abstract class and instantiating it) would be more
efficient.
That said, we're probably not at a level where heap usage, GC, and those
other considerations are very high priority.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/basho/riak-java-client/pull/677#issuecomment-255103163,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAFnomhF4vXxMnhl1wJtVbqoswJi1u7ks5q12o8gaJpZM4KbNBC
.

This all seems fine to a non-Java dev. While I know why the queue and .poll() is used, it seems hacky. Feeble searching for information about netty brought up this SO post which talks about methods to execute callbacks on threads that don't block the IO thread. Maybe something to look into for the future?

@jbrisbin @srgg One other thing I hoped you pick on was the unbounded queue we use, and the way I pass in the poll timeout from the outside.  What do you think about these two designs?
If we used a bounded queue, it would limit Java memory usage if the user isn't consuming the iterator, but then the network buffers would bulge instead, since Riak just sends data like a firehose.
With passing the poll timeout, I was thinking we might also be able to do some sort of devolving timeout based on success rate of the last few polls and their timeouts, but not sure how much extra work that would be.

@a1 We could have a variant where you pass in the Queue to use, which could be any implementation, including one with blocking publish semantics to back up the TCP end in case the queue is not being emptied fast enough.
The read timeout should still probably be configured externally since that's a consideration that takes place inside our code.

@jbrisbin Actually now I remember why I made it unbounded. If we block on the Netty thread for any reason it will throw a BlockingOperationException, which will kill the whole operation. Very bad for large streaming ops because it'll then retry, and fail, and retry and fail, and Riak will then have 3 listing operations running.

Ok, that should be all the gold plating I can think of.

@srgg FullBucketRead tests pass locally, +1 to 51bff20.  Going to review the rest of it now to see if anything jumps out.

+1 to any changes I didn't do.

Looks like more code was deleted than written, always a good sign. Tests pass with Riak 2.2.0, 2.1.4, and 2.0.7 (except one YZ test there). 👍


SNOW-871306: Fix test failures on Windows for tests in test_packaging.py

Please answer these questions before submitting your pull requests. Thanks!

What GitHub issue is this PR addressing? Make sure that there is an accompanying issue to your PR.
Fixes #NNNN

Fill out the following pre-review checklist:

[ ] I am adding a new automated test(s) to verify correctness of my new code
[ ] I am adding new logging messages
[ ] I am adding a new telemetry message
[ ] I am adding new credentials
[ ] I am adding a new dependency

Please describe how your code solves the related issue.
Please write a short description of how your code change solves the related issue.

The standard output (stdout) and standard error (stderr) are captured with subprocess.PIPE. However, the Popen call was earlier followed by process.wait(), which waits for the process to complete, but does not read the output. If the child process generates enough output to fill the OS pipe buffer, the child process will block waiting for the OS to make room in the pipe buffer. This will never occur because the parent process is waiting for the child process to exit before it reads the output.
This can be resolved by using process.communicate() instead of process.wait(). The communicate() function waits for the process to terminate and also reads all output, thereby avoiding the deadlock situation.
See details at https://docs.python.org/3/library/subprocess.html#subprocess.Popen.wait


1.2.9 update broke the whole plugin

Describe the bug
Spigot 1.20.6
Latest dev version of ProtocolLib.
No errors, but I'm just getting:
[Server thread/INFO]: [AdvancedSeasons] Disabling AdvancedSeasons v1.2.9

When the server has finished starting up. No clues anywhere why this might be happening.
Honestly, ramp up your game. I paid 20$ for this plugin and I haven't yet had a single chance to use it because it's so broken on Spigot. All my times goes into filing bug reports. You should test your software before releasing new versions.
How to reproduce
Install Spigot 1.20.6 and AdvancedSeasons 1.2.9. I guess. That's the only thing I did.
Screenshots / Videos
No response
Server Log
No response

same thing here

same thing

Describe the bug
Spigot 1.20.6 Latest dev version of ProtocolLib.
No errors, but I'm just getting:
[Server thread/INFO]: [AdvancedSeasons] Disabling AdvancedSeasons v1.2.9

When the server has finished starting up. No clues anywhere why this might be happening.
Honestly, ramp up your game. I paid 20$ for this plugin and I haven't yet had a single chance to use it because it's so broken on Spigot. All my times goes into filing bug reports. You should test your software before releasing new versions.
How to reproduce
Install Spigot 1.20.6 and AdvancedSeasons 1.2.9. I guess. That's the only thing I did.
Screenshots / Videos
No response
Server Log
No response

Hey Pilvinen, I feel you, man. It's such a bummer that I spent money and can't even use it for 1.20.6. Hopefully, they fix it real soon.

I'm a bit behind, but I'm encountering the same problem with version 1.20.6. I tend to be cautious about purchasing plugins because, inevitably, they never seem to work right off the bat (as expected by now).

I'm a bit behind, but I'm encountering the same problem with version 1.20.6. I tend to be cautious about purchasing plugins because, inevitably, they never seem to work right off the bat (as expected by now).

How can a developer release an update without testing it first lol?

I'm a bit behind, but I'm encountering the same problem with version 1.20.6. I tend to be cautious about purchasing plugins because, inevitably, they never seem to work right off the bat (as expected by now).

How can a developer release an update without testing it first lol?

I'm certain they did, but apparently not thoroughly enough.

Seems to be mostly fixed in 1.3.0.  I still get sometimes some kind of ... authentication server ? issue where AdvancedSeasons unloads itself. But that has happened only once so far.

I'm a bit behind, but I'm encountering the same problem with version 1.20.6. I tend to be cautious about purchasing plugins because, inevitably, they never seem to work right off the bat (as expected by now).

How can a developer release an update without testing it first lol?

We test each and every update, the problem was caused after with the publishing system in place rather than the actual plugin. We've put changes in place to make sure problems like these do not happen again.

Seems to be mostly fixed in 1.3.0.  I still get sometimes some kind of ... authentication server ? issue where AdvancedSeasons unloads itself. But that has happened only once so far.

That may happen if your server loses internet connection for a longer period of time.
This issue is now solved with latest update. My apologies everyone!


Reflex on form submit does not get parameter from input[type="file"]

Bug Report
First of all, thanks for building this, Reflex looks very (very) promising to me.
Describe the bug
I am building a form based on the Working with HTML Forms from the StimulusReflex docs. This form should accept a file input on the parameter file_data for further file uploading. The form triggers a reflex called submit in UploadReflex which should take care of building or updating, and saving the record.
When the reflex receives the params from the form, the file_data parameter which was set by a file_field is always empty. When the file_data parameter is provided by a text_field instead of file_field, the file_data in the reflex' params is not empty. Equally, when the form is submitted to the corresponding controller without using a reflex, the file_data parameter in params corresponds to the file_field input.
Thus it seems, the reflex is ignoring parameters provided by a file input.
To Reproduce
# app/reflexes/upload_reflex.rb
class UploadReflex < ApplicationReflex
  before_reflex :set_upload

  def submit
    byebug
    @upload.assign_attributes(upload_params)
    @upload.save
  end

  private

    def set_upload
      if element.dataset.signed_id.nil?
        @upload = Upload.new
      else
        @upload = GlobalID::Locator.locate_signed(element.dataset.signed_id)
      end
    end

    def upload_params
      params.require(:upload).permit(:caption, :file_data)
    end
end

# app/controllers/uploads_controller.rb
class UploadsController < ApplicationController
  before_action :set_upload, only: [:show, :edit, :update, :destroy]

  def new
    @upload ||= Upload.new
  end

  def edit
  end

  def create
    byebug
    @upload = Upload.new(upload_params)

    respond_to do |format|
      if @upload.save
        redirect_to @upload
      else
        render :new
      end
  end

  def update
      if @upload.update(upload_params)
        redirect_to @upload
      else
        render :edit
      end
  end

  private
    def set_upload
      @upload ||= Upload.find(params[:id])
    end

    def upload_params
      params.require(:upload).permit(:caption, :file_data)
    end
end

# app/views/uploads/_form.html.erb
<%= form_with(model: upload, local: true, multipart: true, data: { reflex: "submit->UploadReflex#submit", signed_id: upload.persisted? ? upload.to_sgid.to_s : nil }) do |form| %>

  <% if upload.errors.any? %>
    <%= pluralize(upload.errors.count, "error") %> prohibited this upload from being saved:

      <% upload.errors.full_messages.each do |message| %>

<%= message %>

      <% end %>

  <% end %>

  <%= form.label :file_data, "file_data" %>
  <%= form.file_field :file_data %>

  <%= form.label :caption, "Caption" %>
  <%= form.text_field :caption %>

  <%= form.submit %>
<% end %>

When the form is submitted using submit->UploadReflex#submit the method upload_params in UploadReflex#submit returns:
<ActionController::Parameters {"caption"=>"This is a caption…"} permitted: true>

When the same form is submitted without the reflex, the method upload_params in UploadsController#create returns:
<ActionController::Parameters {"caption"=>"This is a caption…", "file_data"=>#<ActionDispatch::Http::UploadedFile:0x00007f9e484b3348 @tempfile=#<Tempfile:/var/folders/zj/x1_t9wss5mlcsj62qcj35js40000gn/T/RackMultipart20200720-13302-ldvz0s.jpg>, @original_filename="IMG-20191231-WA0015.jpg", @content_type="image/jpeg", @headers="Content-Disposition: form-data; name=\"upload[file_data]\"; filename=\"IMG-20191231-WA0015.jpg\"\r\nContent-Type: image/jpeg\r\n">} permitted: true>

Expected behavior
The upload_params in UploadReflex#submit should read the file_data parameter provided by a input[type="file"].
Versions
StimulusReflex

Gem: 3.2.3
Node package: ^3.3.0-pre2

External tools

Ruby: 2.7.1
Rails: <IP_ADDRESS>
Node: 12.16.1

Browser

Browser Firefox 78.0.2

We'll need to dive deeper into possibly adding support for file inputs.
For the time being, I think the best course of action is to consider this file input types unsupported and mark them as data-reflex-permanent so you don't lose any state when reflexes are triggered.

Hi and thanks for the response, i am looking forward to hear and see more of StimulusReflex.
It might not be a solution to the actual "problem" of Stimulus Reflex not supporting file inputs, but for the people using the Shrine gem to handle file uploads, there might be a "frontend workaround":
Shrine provides a Upload Endpoint plugin in order to use JS upload libraries (e.g. Uppy). This endpoint accepts a post request with the uploaded file and returns a JSON response.
Using a JS uploader and the upload endpoint we can avoid using a input[type="file"], instead populate a input[type="hidden"] with the necessary JSON data and pass it to a reflex.
An example implementation of Uppy with Shrine and the Upload endpoint can be found here: Better File Uploads with Shrine: Direct Uploads.

Hey Paul! (Are you on Discord? If not, please consider joining us!)
This sounds like a potentially viable workaround, at least for Shrine users. If you are able to try this out, verify it and help extract the important bits, I'd love to work with you to add an example of this into the documentation because you're probably not the last person to ask about uploads.

Yeah running into the same issue here! I'll try shrine or some other things. Following thread

Hey @leastbad, i am sorry for the delayed answer. I already made a first tryout which worked and i could work out an example. Right now i am too occupied to do this but i will have to work further with async file uploads in an upcoming project and i am planning to hook them to Stimulus Reflex. For anybody in need right now, i think the approach described above (https://github.com/hopsoft/stimulus_reflex/issues/277#issuecomment-661726137) is a good start.
As soon as i'd have something to share, i'll post it here as i am not on Discord.

Hi ( @leastbad ), following the question to circumvent the problem of using input type="file" fields in order to submit files through forms using StimulusReflex, i just wrote a small dummy app which makes use of StimulusReflex in combination with Shrine which can be found here: https://gitlab.com/swrs/stimulus-reflex-shrine.
The application is obviously rough and uses Shrine's Upload endpoint together with the frontend Uppy uploader, submitting a form upon file upload. I included some file validations for mime-types (image/jpeg image/jpg image/png image/gif application/pdf) and file size (< 3MB) in order to test error behaviour. As the form is submitted after every file upload, it is possible to do batch uploads of multiple files.
The docs mention: if you're thinking of replacing UJS remote forms with StimulusReflex form handling without a specific reason for doing so... just stick with Rails! which seems to be quite true, but for file uploads it could make sense to pass a form through a reflex in order to facilitate validations, a file thumb partial, … .
Some short notes on how it works:
– uploader_controller.js initializes the Uppy dashboard by clicking data-target="uploader.button".
– Upon selecting a file, Uppy uploads files to Shrine's upload endpoint which responds with the data to populate the record's file attribute.
– Upon a successful upload, the response is stored in an input type="hidden" and the form is submitted via the reflex Upload#submit.


[monitor] Type error when using a resource in AzureMonitorOpenTelemetryOptions

Package Name: @azure/monitor-opentelemetry
Package Version: 1.2.0
nodejs

version: 18.15.0

typescript

version: 5.1.3

Describe the bug
Using a custom resource in the AzureMonitorOpenTelemetryOptions is prevented due to a type error
To Reproduce

Create a new resource using @opentelemetry/resources

import { AzureMonitorOpenTelemetryOptions, useAzureMonitor } from '@azure/monitor-opentelemetry';
import { SemanticResourceAttributes } from '@opentelemetry/semantic-conventions';
import { Resource } from '@opentelemetry/resources';

const customResource = new Resource({
  [SemanticResourceAttributes.SERVICE_NAMESPACE]: 'Service_Namespace',
  [SemanticResourceAttributes.SERVICE_NAME]: 'Service_Name',
  [SemanticResourceAttributes.SERVICE_INSTANCE_ID]: 'Instance_Id',
});

Initialize a new Azure Monitor instance using the custom resource

const config: AzureMonitorOpenTelemetryOptions = {
  azureMonitorExporterOptions: {
    connectionString: process.env.APPLICATIONINSIGHTS_CONNECTION_STRING,
  },
  resource: customResource,
};

useAzureMonitor(config);

An error will be shown either by the IDE or when trying to run the program

Expected Behavior
The resource should be able to be added without the error appearing
Screenshots

Additional context
The relevant packages in my package.json are
"@azure/monitor-opentelemetry": "^1.2.0",
"@opentelemetry/resources": "^1.21.0",
"@opentelemetry/semantic-conventions": "^1.21.0",

Using a resource also works if you use import { Resource } from '@azure/monitor-opentelemetry-exporter/node_modules/@opentelemetry/resources'; instead of import { Resource } from '@opentelemetry/resources';, but I doubt this is the intended import method.

@TheIceCreamTroll I've tested your example in a sample app using the same dependencies, typescript version, and node version. Using the same code to initialize Azure Monitor I'm not seeing any type errors when ts compiling the project or running the generated js file. Can I take a look at your tsconfig.json and package.json to better recreate your environment?

tsconfig.json
{
  "compilerOptions": {
    "module": "commonjs",
    "target": "es6",
    "outDir": "dist",
    "rootDir": ".",
    "sourceMap": true,
    "strict": false,
    "esModuleInterop": true,
    "resolveJsonModule": true,
    "skipLibCheck": true
  }
}

package.json
{
  "name": "",
  "version": "",
  "scripts": {
    "build": "tsc",
    "build:production": "npm run prestart && npm prune --production",
    "watch": "tsc --w",
    "prestart": "npm run build && func extensions install",
    "start:host": "func start",
    "start": "npm-run-all --parallel start:host watch",
    "test": "npx jest --watchAll=true",
    "gen": "graphql-codegen --config codegen.yml",
    "gen:watch": "graphql-codegen --config codegen.yml --watch  --silent=false"
  },
  "description": "",
  "devDependencies": {
    "@graphql-codegen/cli": "^3.3.0",
    "@graphql-codegen/introspection": "^3.0.1",
    "@graphql-codegen/typed-document-node": "^4.0.0",
    "@graphql-codegen/typescript": "^3.0.3",
    "@graphql-codegen/typescript-operations": "^3.0.3",
    "@graphql-codegen/typescript-resolvers": "^3.2.0",
    "@types/jest": "^27.4.0",
    "@types/node": "^18.16.0",
    "jest": "^27.5.1",
    "jest-html-reporter": "^3.6.0",
    "mongodb-memory-server": "^8.3.0",
    "npm-run-all": "^4.1.5",
    "typescript": "^5.1.3"
  },
  "dependencies": {
    "@apollo/cache-control-types": "^1.0.2",
    "@apollo/server": "^4.6.0",
    "@apollo/server-plugin-response-cache": "^4.1.2",
<EMAIL_ADDRESS>"^3.0.0",
    "@as-integrations/azure-functions": "^0.1.3",
    "@azure/arm-maps": "^3.1.0-beta.1",
    "@azure/cognitiveservices-contentmoderator": "^5.0.1",
    "@azure/functions": "^3.5.1",
    "@azure/identity": "^2.0.4",
    "@azure/monitor-opentelemetry": "^1.2.0",
    "@azure/monitor-opentelemetry-exporter": "^1.0.0-beta.17",
    "@azure/ms-rest-azure-js": "^2.1.0",
    "@azure/search-documents": "^11.2.1",
    "@azure/storage-blob": "^12.8.0",
    "@graphql-tools/graphql-file-loader": "^7.3.3",
    "@graphql-tools/load": "^7.5.1",
    "@graphql-tools/load-files": "^6.5.3",
    "@graphql-tools/schema": "^8.3.1",
    "@graphql-tools/stitch": "^8.4.3",
    "@lucaspaganini/value-objects": "^1.3.1",
    "@opentelemetry/api": "^1.7.0",
    "@opentelemetry/api-logs": "^0.48.0",
    "@opentelemetry/instrumentation": "^0.48.0",
    "@opentelemetry/instrumentation-bunyan": "^0.35.0",
    "@opentelemetry/instrumentation-dataloader": "^0.5.4",
    "@opentelemetry/instrumentation-graphql": "^0.36.1",
    "@opentelemetry/instrumentation-http": "^0.48.0",
    "@opentelemetry/instrumentation-mongodb": "^0.38.1",
    "@opentelemetry/resources": "^1.21.0",
    "@opentelemetry/sdk-logs": "^0.48.0",
    "@opentelemetry/sdk-trace-base": "^1.21.0",
    "@opentelemetry/semantic-conventions": "^1.21.0",
    "@types/archiver": "^5.3.1",
    "apollo-datasource-mongodb": "^0.6.0",
    "archiver": "^5.3.1",
    "async-retry": "^1.3.3",
    "axios": "^1.3.6",
    "bunyan": "^1.8.15",
    "dayjs": "^1.11.3",
    "graphql": "^16.6.0",
    "graphql-fields": "^2.0.3",
    "graphql-middleware": "^6.1.33",
    "graphql-mongo-fields": "^1.0.6",
    "graphql-scalars": "^1.14.1",
    "graphql-shield": "^7.6.5",
    "jose": "^4.5.0",
    "moment": "^2.29.1",
    "mongoose": "^6.2.1",
    "nanoid": "^3.3.2",
    "openid-client": "^5.1.3",
    "retry": "^0.13.1"
  }
}

@TheIceCreamTroll The types issue should be resolved by #28459 and will be available in the next Azure Monitor OpenTelemetry release. Thank you again for your issue report!


Need to move CI tests to GitHub actions

Issue Overview
CircleCI seems unusable now. We should switch to using GitHub actions.

I think the Circle needs some permission settings when integrating with Github.

Try to reinstall Circle App from Github Marketplace and follow the guide to fix it.


Add scaffolding to enable snap build of commento

Thanks to @evandandrea for the frontend part.

Original PR by @popey - https://github.com/adtac/commento/pull/38
@popey: I've cherry-picked your commit, rebased it, made a couple of modifications, added in @evandandrea 's frontend stuff and tested that it works. It does! :) You're still the commit author (I could only thank @evandandrea in the commit body).


Sort types for display

Pushing to a PR for performance testing. This initial cut looks extremely slow.
Fixes #32224

@typescript-bot perf test this

Do we have declaration emit captured in the perf tests?
https://github.com/microsoft/TypeScript/issues/44033

@amcasey seemed to think not, so on his recommendation I have been testing by compiling tinymce instead. However, it has around 1000 unions, which may not be enough to detect a worst-case slowdown. Maybe I should find a gnarly DT package, read it, then print it out and see how long printing it takes.

Notes from discussion in our team meeting:

typeToString already puts null/undefined at end, need to dedupe this code
enums should probably maintain order
true | false collapses to boolean
should maintain order of properties dumped via keyof
decide what to do with origin types from denormalised unions

Well, this was an interesting experiment, but after finishing the sort code, I found the best performance test is our type baselines. I just ran time gulp runtests-parallel and looked at the amount of CPU time spent. It's 10% slower even skipping the less-important-to-sort types. So I don't think this is a viable approach. Probably the only thing that would work is to sort during union creation.


NixOS Instructions are needed

Hi I should probably know how to do this, however I still think that there should be instructions on how to install this on NixOS. Given that BizHawks DLL folder is within the Nix Store and is read only. Could probably come up with a solution using overlays, but I have yet to grasp the concept.

I tried to install NixOS myself earlier today in order to try it out for myself, but unfortunately it did not add itself to GRUB. I might try again later at some point, or maybe someone has an idea on why this happens, or maybe someone can contribute a way to package this project for NixOS.


5.9: [AllocBoxToStack] Specialize moved PAIs.

Cherry-pick of https://github.com/apple/swift/pull/65359 .
Added move_value to the list of instructions looked through when determining whether a partial_apply instruction escapes.
rdar://108376960

@swift-ci please test


Fail to reproduce the reconstruction result

Thank you for the excellent open-source work.

reproduce the reconstruction result （ImageNet dataset） （refer to Table 2 from https://arxiv.org/pdf/2312.03511.pdf ）

FID ↓
SSIM ↑
PSNR ↑

from paper
0.686
0.741
27.04

reproduce
1.19
0.76
24.8

Is this kind of accuracy difference as expected?

I found that there are some difference between https://github.com/ai-forever/MoVQGAN/blob/main/movqgan/models/vqgan.py and this repo

movq of this repo did not implement vector quantize in https://github.com/ai-forever/Kandinsky-3/blob/main/kandinsky3/movq.py#L402
some norm layer in encoder have different weight and bias

so I inference the movq from https://github.com/ai-forever/MoVQGAN

FID ↓
SSIM ↑
PSNR ↑

from paper
0.686
0.741
27.04

reproduce movqgan_270M (256x256)
1.08
0.75
27.42

reproduce movqgan_270M (512x512)
0.695
0.792
26.32

when inference with 512x512, The result looks somewhat closer to the paper


Fix #314, weave assemblies built before weaver

This PR weaves all assemblies built before and after the weaver.
This resolves issue #314

Notice this PR currently has a problem with  #314

what problem does it have with #314 ?

you can ignore the last comment,  I could not reproduce the issue with unity 2018.2

for future reference: apparently this works now because of Unity 2018.2.

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


The fastmath SVML option has been broken since somewhere between 0.43.1 and 0.44

Reporting a bug

[x] I am using the latest released version of Numba (most recent is visible in
the change log (https://github.com/numba/numba/blob/master/CHANGE_LOG).
[x] I have included below a minimal working reproducer (if you are unsure how
to write one see http://matthewrocklin.com/blog/work/2018/02/28/minimal-bug-reports).

Numba 0.43.1 was the last version of Numba with a working SVML option accessible via the standard JIT decorators. The patch 310b3cbb1 broke SVML working, but it's not especially the fault of that patch. The issue seems to be caused by decorating a function with njit ahead of setting the vector library option to LLVM via the llvmlite bindings.
This is broken:
from llvmlite import binding

# import before set
from numba import njit
binding.set_option('SVML', '-vector-library=SVML')

import numpy as np
import math

@njit(fastmath={'fast'})
def foo(n):
    x   = np.empty(n*8, dtype=np.float64)
    ret = np.empty_like(x)
    for i in range(ret.size):
            ret[i] += math.cosh(x[i])
    return ret

foo(1000)

if 'intel_svmlcc' in foo.inspect_llvm(foo.signatures[0]):
    print("found")
    exit(0)
else:
    print("not found")
    exit(1)

whereas this works as expected:
from llvmlite import binding

# set before import
binding.set_option('SVML', '-vector-library=SVML')
from numba import njit

import numpy as np
import math

@njit(fastmath={'fast'})
def foo(n):
    x   = np.empty(n*8, dtype=np.float64)
    ret = np.empty_like(x)
    for i in range(ret.size):
            ret[i] += math.cosh(x[i])
    return ret

foo(1000)

if 'intel_svmlcc' in foo.inspect_llvm(foo.signatures[0]):
    print("found")
    exit(0)
else:
    print("not found")
    exit(1)

The issue manifests in the Numba code base during init as there's now all this:
https://github.com/numba/numba/blob/bdd8e312a24c5b76ee4fe480abe553cff349aa51/numba/__init__.py#L46-L52
which are imports of modules that somewhere in their import tree import njit and then decorate one or more functions with it, this prior to setting the vector-library option in the llvmlite DSO to SVML.
This is most likely an issue with internal state of the llvmlite DSO. Fixing options:

Trace the use of njit on the __init__ import path and replace with register_jitable.
Move anything that uses njit on the __init__ import path to occur logically after setting the vector-library option on the DSO.
Work out what the actual problem is and then fix that opposed to applying sequence based ducktape :)

This bug does not impact the use of compile_isolated as the SVML tests in the test suite continue to pass.

The use of njit in numba/charseq.py instead of register_jitable is preventing overload resolution on charseq types which breaks this PR https://github.com/numba/numba/pull/4715.


Eraser not working properly with enabling scanner

What steps did you take and what happened:
I took alpine in quickstart.md for example.
> cat <<EOF | kubectl apply -f -
apiVersion: apps/v1
kind: DaemonSet
metadata:
  name: alpine
spec:
  selector:
    matchLabels:
      app: alpine
  template:
    metadata:
      labels:
        app: alpine
    spec:
      containers:
      - name: alpine
        image: docker.io/library/alpine:3.7.3
EOF

# delete daemonset
> kdelds alpine

# install eraser
# args mentioned in environment
> kaf eraser.yaml

Then lots of scanner job/pod were scheduled and actually they were doing the same things.
> kgpn eraser-system --sort-by=.metadata.creationTimestamp
NAME                                         READY   STATUS      RESTARTS   AGE
eraser-controller-manager-76c5fc44f6-xpskl   1/1     Running     0          31m
...
eraser-scanner-bwrl6--1-cqdw6                0/1     Completed   0          23m
eraser-scanner-hkw57--1-hvh8m                0/1     Completed   0          22m
eraser-scanner-jl9r2--1-ws9fn                0/1     Completed   0          22m
eraser-scanner-62cg6--1-c6j6q                0/1     Completed   0          22m
eraser-scanner-khg6h--1-8xljn                0/1     Completed   0          22m
eraser-scanner-99wjv--1-sqqzt                0/1     Completed   0          22m
eraser-scanner-mg5rx--1-fwxcx                0/1     Completed   0          22m

> kl -n eraser-system eraser-scanner-99wjv--1-sqqzt
{"level":"info","ts":1657177455.2575624,"logger":"scanner","msg":"scanning image","provider":"trivy","imageRef":"docker.io/library/alpine:3.7.3"}
2022-07-07T07:04:16.597Z        INFO    Detected OS: alpine
2022-07-07T07:04:16.597Z        INFO    Detecting Alpine vulnerabilities...
2022-07-07T07:04:16.597Z        INFO    Number of language-specific files: 0
2022-07-07T07:04:16.597Z        WARN    This OS version is no longer supported by the distribution: alpine 3.7.3
2022-07-07T07:04:16.597Z        WARN    The vulnerability detection may be insufficient because security updates are not provided
{"level":"info","ts":1657177456.597751,"logger":"scanner","msg":"scanning image","provider":"trivy","imageRef":"mcr.microsoft.com/oss/kubernetes/pause:3.6"}
{"level":"info","ts":1657177456.7777555,"logger":"scanner","msg":"scanning image","provider":"trivy","imageRef":"ghcr.io/azure/eraser-trivy-scanner:v0.2.1"}
2022-07-07T07:04:16.777Z        INFO    Number of language-specific files: 0
2022-07-07T07:04:19.047Z        INFO    Detected OS: debian
2022-07-07T07:04:19.047Z        INFO    Detecting Debian vulnerabilities...
2022-07-07T07:04:19.047Z        INFO    Number of language-specific files: 1
2022-07-07T07:04:19.047Z        INFO    Detecting gobinary vulnerabilities...
{"level":"info","ts":1657177459.1253657,"logger":"scanner","msg":"scanning complete, exiting","provider":"trivy"}

> kl -n eraser-system eraser-scanner-mg5rx--1-fwxcx
{"level":"info","ts":1657177458.6709077,"logger":"scanner","msg":"scanning image","provider":"trivy","imageRef":"docker.io/library/alpine:3.7.3"}
2022-07-07T07:04:20.092Z        INFO    Detected OS: alpine
2022-07-07T07:04:20.092Z        INFO    Detecting Alpine vulnerabilities...
2022-07-07T07:04:20.092Z        INFO    Number of language-specific files: 0
2022-07-07T07:04:20.092Z        WARN    This OS version is no longer supported by the distribution: alpine 3.7.3
2022-07-07T07:04:20.092Z        WARN    The vulnerability detection may be insufficient because security updates are not provided
{"level":"info","ts":1657177460.0926607,"logger":"scanner","msg":"scanning image","provider":"trivy","imageRef":"mcr.microsoft.com/oss/kubernetes/pause:3.6"}
{"level":"info","ts":1657177460.2555983,"logger":"scanner","msg":"scanning image","provider":"trivy","imageRef":"ghcr.io/azure/eraser-trivy-scanner:v0.2.1"}
2022-07-07T07:04:20.255Z        INFO    Number of language-specific files: 0
2022-07-07T07:04:22.277Z        INFO    Detected OS: debian
2022-07-07T07:04:22.277Z        INFO    Detecting Debian vulnerabilities...
2022-07-07T07:04:22.277Z        INFO    Number of language-specific files: 1
2022-07-07T07:04:22.277Z        INFO    Detecting gobinary vulnerabilities...
{"level":"info","ts":1657177462.3675733,"logger":"scanner","msg":"scanning complete, exiting","provider":"trivy"}

Check events.
> k get events --sort-by=.metadata.creationTimestamp -n eraser-system | tail
25m         Normal   Started             pod/eraser-scanner-99wjv--1-sqqzt                 Started container trivy-scanner
25m         Normal   Created             pod/eraser-scanner-99wjv--1-sqqzt                 Created container trivy-scanner
25m         Normal   Pulled              pod/eraser-scanner-99wjv--1-sqqzt                 Container image "ghcr.io/azure/eraser-trivy-scanner:v0.2.1" already present on machine
25m         Normal   Started             pod/eraser-scanner-mg5rx--1-fwxcx                 Started container trivy-scanner
25m         Normal   Created             pod/eraser-scanner-mg5rx--1-fwxcx                 Created container trivy-scanner
25m         Normal   Pulled              pod/eraser-scanner-mg5rx--1-fwxcx                 Container image "ghcr.io/azure/eraser-trivy-scanner:v0.2.1" already present on machine
25m         Normal   Scheduled           pod/eraser-scanner-mg5rx--1-fwxcx                 Successfully assigned eraser-system/eraser-scanner-mg5rx--1-fwxcx to aks-nodes-38266006-vmss000000
25m         Normal   SuccessfulCreate    job/eraser-scanner-mg5rx                          Created pod: eraser-scanner-mg5rx--1-fwxcx
25m         Normal   Completed           job/eraser-scanner-99wjv                          Job completed
25m         Normal   Completed           job/eraser-scanner-mg5rx                          Job completed

Okay, the eraser controller manager was not going forward any more, based on my understanding, once collector/scanner finished, the imagelist should be upserted.
But it was not found like below either the imagejob.
> kd imagelist
No resources found in default namespace.

> kd imagejob
No resources found in default namespace.

Obviously the vulnerable image was still there,
> az vmss run-command invoke \
  ...
  --scripts "ctr -n k8s.io images list | grep alpine"
{
  "value": [
    {
      "code": "ProvisioningState/succeeded",
      "displayStatus": "Provisioning succeeded",
      "level": "Info",
      "message": "Enable succeeded: \n[stdout]\ndocker.io/library/alpine:3.7.3                                                                                application/vnd.docker.distribution.manifest.list.v2+json sha256:8421d9a84432575381bfabd248f1eb56f3aa21d9d7cd2511583c68c9b7511d10 2.0 MiB   linux/386,li
nux/amd64,linux/arm/v6,linux/arm64/v8,linux/ppc64le,linux/s390x io.cri-containerd.image=managed \ndocker.io/library/alpine@sha256:8421d9a84432575381bfabd248f1eb56f3aa21d9d7cd2511583c68c9b7511d10                    application/vnd.docker.distribution.manifest.list.v2+json sha256:8421d9a84432575381bfabd248f1eb56f3aa2
1d9d7cd2511583c68c9b7511d10 2.0 MiB   linux/386,linux/amd64,linux/arm/v6,linux/arm64/v8,linux/ppc64le,linux/s390x io.cri-containerd.image=managed \n\n[stderr]\n",
      "time": null
    }
  ]
}

Summary - two issue:

scanner was set up again and again
eraser not working properly with scanner (works if I disable scanner)

Environment:
eraser args:
- --leader-elect=false
- --eraser-image=ghcr.io/azure/eraser:v0.2.1
- --collector-image=ghcr.io/azure/collector:v0.2.1
- --scanner-image=ghcr.io/azure/eraser-trivy-scanner:v0.2.1
- --repeat-period=30m
- --job-cleanup-on-success-delay=300

Eraser version: v0.2.1
Kubernetes version: Client Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.0", GitCommit:"4ce5a8954017644c5420bae81d72b09b735c21f0", GitTreeState:"clean", BuildDate:"2022-05-03T13:46:05Z", GoVersion:"go1.18.1", Compiler:"gc", Platform:"linux/amd64"}

@jiashun0011 did you had job-cleanup-on-success-delay flag set to non-zero?


Helmfile integration with helm-secrets

Any recommendations for integration Helmfile with helm-secrets
https://github.com/roboll/helmfile/issues/41

Thx. Looks like you integrate it helmfile now.


API proposal/discussion for touch platform interactions

Little bit of background: For a touch platform only web app we're building we're using Capybara for acceptance tests, along with a js driver that is touch capable (now poltergeist, before capybara-webkit - basically any recent webkit based driver supporting touch events could be used). We're not using any click interactions at all, thus I needed to make the capybara js driver touch capable.
Here's a pull request I sent to poltergeist
https://github.com/jonleighton/poltergeist/pull/135/files
which contains an initial implementation, so far only for simple, single taps:
Element#single_tap

e.g.
find('.tap-me').single_tap

@jonleighton in response asked me to start a discussion here as to (hopefully) agree on an API that could be implemented by any capable driver.  See https://github.com/jonleighton/poltergeist/issues/141
I had further methods in mind to be implement later, just as a proposal:
single_tap
double_tap
long_tap
swipe_left
swipe_right
swipe_up
swipe_down
(The names follow what Zepto.js provides for touch event abstractions.) There are also gesture events I didn't yet think about.
I'd be glad if we could get a discussion going about this and happily help with the implementation whenever required.
[Edit: swipe_bottom -> swipe_down]

Hey, there's this gem I have developed that adds touch gestures support to Capybara. Take a look at https://github.com/Ricardonacif/touch_action .
Thanks,


Catch HitTestResult NullPointerException

Task/Issue URL: https://app.asana.com/0/1200204095367872/1207702094588632/f
Description
Steps to test this PR
Feature 1

[ ]
[ ]

UI changes

Before
After

!(Upload before screenshot)
(Upload after screenshot)

#4710  👈
develop

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @joshliebe and the rest of your teammates on  Graphite


Remove Python 2.7 Support from Docs

The documentation currently still says we support python 2.7 on the installation page. We should also make sure the python 2.7 support is removed everywhere else such as pypi and conda-forge.
https://docs.featuretools.com/getting_started/install.html

removed from the main file mentioned in the issue.
let me know where should I look further, and assign me the issue.

both https://anaconda.org/conda-forge/featuretools and  https://pypi.org/project/featuretools/ do not mention 2.7

The following comment mentions python 2.7.
But this should be in a different issue to change the code base, not documentation.
https://github.com/FeatureLabs/featuretools/blob/8ba9423782691df5aea2e363a562c8d0296f6efe/featuretools/entityset/serialize.py#L95-L99


Can't build for ios

Hello. Big thx for this project.
I try to compil project for ios
My steps:
git reset --hard v2.0.0-beta09
npm install
npm run restore
npm run ios

and i catch this errors:
** BUILD FAILED **
The following build commands failed:
	CompileC build/YourAppName.build/Debug-iphoneos/YourAppName.build/Objects-normal/armv7/NativePageTransitions.o YourAppName/Plugins/com.telerik.plugins.nativepagetransitions/NativePageTransitions.m normal armv7 objective-c com.apple.compilers.llvm.clang.1_0.compiler

I try to upper version NativePageTransitions, but it did not help :(
xcodebuild -version
Xcode 7.3.1
Build version 7D1014

ionic -v
1.7.14

node  -v
v5.8.0

In Google Chrome everything is fine
Have any ideas ? Thx

Remove the plugin and let me know
On May 20, 2016 4:20 AM, "F1NaL"<EMAIL_ADDRESS>wrote:

Hello. Big thx for this project.
I try to compil project for ios
My steps:
git reset --hard v2.0.0-beta09
npm install
npm run restore
npm run ios
and i catch this errors:
** BUILD FAILED **
The following build commands failed:
CompileC build/YourAppName.build/Debug-iphoneos/YourAppName.build/Objects-normal/armv7/NativePageTransitions.o YourAppName/Plugins/com.telerik.plugins.nativepagetransitions/NativePageTransitions.m normal armv7 objective-c com.apple.compilers.llvm.clang.1_0.compiler
I try to upper version NativePageTransitions, but it did not help :(
xcodebuild -version
Xcode 7.3.1
Build version 7D1014
ionic -v
1.7.14
node  -v
v5.8.0
In Google Chrome everything is fine
Have any ideas ? Thx
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/shprink/wordpress-hybrid-client/issues/224

I think it's plugin cache, from v2.0.8
Solution for me:
rm -rf plugins/
rm -rf platforms/
npm run restore

I'm sorry to trouble you


Auth0 infra: add custom claims to id token

Adds action that adds user data from the user metadata to the id token post login.

I took a look at the documentation and I think we should avoid storing attributes in user metadata that can be stored as root attributes. I removed these claims.
I'm not sure if we should store the phone_number claim in metadata or not. https://community.auth0.com/t/why-can-we-not-set-a-users-phone-number/48574

I'm not sure if we should store the phone_number claim in metadata or not. This forum post is from 2020 but states that the root phone_number attribute is reserved for sms users, whatever that means. https://community.auth0.com/t/why-can-we-not-set-a-users-phone-number/48574.

As far as I understood it is only allowed to be used for users that have passwordless log in with a phone number. We do not have such users, so the root phone_number is not relevant to us (yes that is a bit weird, but w/e), and we need to store it in app/user_metadata

I think we only need studyYear and ow_user_id in custom claims. Let's fetch the other ones if they are needed.


add a configuration/enricher to make it easy to add a ServiceAccount to an application

Right now its a little bit involved to add a ServiceAccount; you need to

create a sa.yml file
create a deployment.yml file if you have not already and add the spec.serviceAccountName: xyz entry

For folks who have a deployment.yml already its not a biggie; but maybe it should just be flag thats enabled which would then generate an SA if its not already created (for the same name as the deployment) along with adding the serviceAccountName to the deployment spec

This could be easily done by a specific enricher, which

Checks every deployment for references to SAs
Checks whether the SA already exists in the resource list.
If not, create the SA on the fly.

We could also a config option to the DefaultControllerEnricher for SA.

Agreed. It does feel like we should just have an enricher flag we could enable in the pom.xml to enable the SA stuff.
I wonder if by default if you add an sa.yml we should by default use it in the Deployment (if there's only 1 Deployment) as its probably what folks mean and avoids them having to write the deployment.yml and remember the right level of indentation to add the serviceAccountName?

I wonder if by default if you add an sa.yml we should by default use it in the Deployment (if there's only 1 Deployment) as its probably what folks mean and avoids them having to write the deployment.yml and remember the right level of indentation to add the serviceAccountName?

This should be also no problem by adding to the DefaultControllerEnricher which does this if it detects a given SA in the list to enrich, and adds the proper field to either an existing Deployment object or to the one which this enricher creates by default.
However it makes more sense to allow the configuration of an SA directly in the config like in
<enricher>
   <config>
      <fmp-controller>
           <service-account>....</service-account>
      </fmp-controller>
   </config>
</enricher>

or by setting a property
fabric8.enricher.fmp-controller.service-account

or (when we finally give our XML configuration some love ;-) in XML config
<resources>
   ....
   <service-accounts>
       <sa>...</sa>
       <sa>...</sa>
    <service-accounts>
</resources>

Not yet sure about the proper XML syntax has we could combine it directly with allowing role bindings in the declaration, so that we might have a top-level XML config <authorization>...</authorization> which groups together such kind of things.


⚠ BCR Bot has degraded performance

In a458a2a, BCR Bot (https://bcr.alternativasinteligentes.com/BCRApi/web/chatbot) experienced degraded performance:

HTTP code: 200
Response time: 973 ms

Resolved: BCR Bot performance has improved in ed586df.


Bulkupdate can't remove permission when user only has 1 permission

Hello,
I can't seem to bulk remove a permission when a user has only 1 permission.
Tried it on 4.4.27
Regards,
Glenn R.

This doesn't help us at all.
You have to tell us what you tried and what the results are.

@Andre601
Talked about it in the discord channel today, anyway here is what we did.
lp bulkupdate all update permission all.permission.nodes "permission ~~ permission.node.%"
lp bulkupdate all update permission all.permission.nodes "permission ~~ node.%"
lp bulkupdate users delete "permission == all.permission.nodes"

The wanted permission nodes will change to all.permission.nodes which is expected, then I would like to delete all.permission.nodes with the 3rd command.
It will delete that permission for all users that have other permission aswell. The permission won't get delete if the user has only that permission left.

Fixed in the latest version.


💥 KotlinFrontEndException - Recursion detected on input

Hi there!
I'm trying to implement both Realm Kotlin SDK and MVI Kotlin library in the same project. I ran into problems with the compiler when the Realm plugin was enabled.
Here's the step to reproduce (Sample repo here):

Init a multiplatform project with Realm and MVI Kotlin dependency
Setup a simple MVI Kotlin Store. See code below.
Build! See the exception stack below.

Here's the code that the compiler is throwing exception: https://github.com/thipokch/TestKotlinLibraries/blob/8101de59ad0174a246ba610ffeaccf3cffb9e8cf/shared/src/commonMain/kotlin/com/example/myapplication/GhostStore.kt#L10-L21

Hi @thipokch. Thanks for the report. This seems like a duplicate of #339, so will close this. We are investigating how to work around this issue.


add custom ready event callback

I need exec some code when custom dom load ready

Implemented in 87bea7c.


HV-948 Make French DecimalMin and Max messages use the inclusive flag

Ah French.

HV-5-MASTER #674 SUCCESS
This pull request looks good

Rebased and merged. Merci beaucoup!


Introducing menu types

This is the PR #24 integrated into 2.0 as well as some minor fixes to it.

Pending issues:

[ ] if an item had a parent, which generated a URI like page1/menu_item, setting it as root, doesn't update URI

Update uris on page slug change (all translations)
Double check all possible combinations of parent/child
Update drag&drop to use new uri things
Don't load items in parent dropdown that are already parent of current menuItem


Add sphere-capsule collision.

Implements sphere-capsule collision as collision between a sphere and the two spheres of the capsule.

Thanks! So this would be an approximation, not taking collisions in between the capsule end points into account?


Reduce code churn when custom_build_prompt parameters are changed.

I don't know about you, but I got tired of small changes to the parameter count causing a headache.  If you're happy with this then I have a patch for adding a "condensed mode" to follow shortly thereafter ;)

i'm on vacation until next week, ill get back to you. (i like this, but i havent checked out/tested )


I think this is everywhere that same-origin is required.

Not sure about the behavior of d3-requests.
I was a little confused by worker.js, but this looks like the appropriate translation if we're adding more to the init: (Request and fetch have the same signature.)
headers = {'content-type': 'application/json'};
r = new Request('http://example.com', {headers});
console.log('Headers:', Array.from(r.headers.keys()));
console.log('Credentials:', r.credentials);
// Headers: Array [ "content-type" ]
// Credentials: omit

headers = {'content-type': 'application/json'};
r = new Request('http://example.com', {'headers': headers, 'credentials': 'same-origin'});
console.log('Headers:', Array.from(r.headers.keys()));
console.log('Credentials:', r.credentials);
// Headers: Array [ "content-type" ]
// Credentials: same-origin

ping @pkerpedjiev: Could this be merged? Background: I'm not sure why things seemed to work in the past, but I'm pretty confident that going forward this is what is required for higlass to work inside refinery.
(cc @scottx611x)

Isn't same-origin the default value for credentials? https://developer.mozilla.org/en-US/docs/Web/API/Request/credentials
Have you tried building a local version of HiGlass and seeing if this PR solves the issue you have?

(Copying thread from slack for reference:)
huh: I’m trying to re-run the experiment in the PR, but now it looks like this:
headers = {'content-type': 'application/json'};
// Object { "content-type": "application/json" }
r = new Request('http://example.com', {headers});
// Request { method: "GET", url: "http://example.com/", headers: Headers, destination: "", referrer: "about:client", referrerPolicy: "", mode: "cors", credentials: "same-origin", cache: "default", redirect: "follow" }
r.credentials
// "same-origin"

I’m wondering if I misread some part of the docs once, and then never checked that belief? … but I’m also pretty sure cookies were being dropped. Let me look into this again and get back to you.

browser might make a difference:
Chrome 67.0.3396.99:
headers = {'content-type': 'application/json'};
r = new Request('http://example.com', {headers});
console.log('Headers:', Array.from(r.headers.keys()));
console.log('Credentials:', r.credentials);
// Headers: ["content-type"]
// Credentials: omit

FF 61.0:
headers = {'content-type': 'application/json'};
r = new Request('http://example.com', {headers});
console.log('Headers:', Array.from(r.headers.keys()));
console.log('Credentials:', r.credentials);
// Headers: Array [ "content-type" ]
// Credentials: same-origin

I think this is the issue in Chrome to fix this behavior, and this is the change in the spec they refer to.
Let me:

See if I can find a corresponding recent change in FF.
Run a local demo, which I believe would show the right behavior in FF, but the wrong behavior in Chrome.

... or, actually, that would be a bit of a pain... Locally edit this repo, and then build gehlenborglab/higlass pointing to local edits, and then build the refinery wrapper, modified to point to the local base image... What do you think? Is this a scenario we should find a way to simplify?


Bump sbt to 1.3.12

Contributor Checklist

[ ] Did you add Scaladoc to every public function/method?
[ ] Did you update the FIRRTL spec to include every new feature/behavior?
[ ] Did you add at least one test demonstrating the PR?
[x] Did you delete any extraneous printlns/debugging code?
[x] Did you specify the type of improvement?
[x] Did you state the API impact?
[x] Did you specify the code generation impact?
[x] Did you request a desired merge strategy?
[ ] Did you add text to be included in the Release Notes for this change?

Type of Improvement

code cleanup

API Impact
No API impact.
Backend Code Generation Impact
No change to backend code generation.
Desired Merge Strategy

Squash: The PR will be squashed and merged (choose this if you have no preference.

Reviewer Checklist (only modified by reviewer)

[ ] Did you add the appropriate labels?
[ ] Did you mark the proper milestone (1.2.x, 1.3.0, 1.4.0) ?
[ ] Did you review?
[ ] Did you check whether all relevant Contributor checkboxes have been checked?
[ ] Did you mark as Please Merge?

This fails with:
sbt +clean +test +publishLocal
 ...
[info] Tests: succeeded 1533, failed 0, canceled 0, ignored 9, pending 0
[info] All tests passed.
[info] Passed: Total 1533, Failed 0, Errors 0, Passed 1533, Ignored 9
[success] Total time: 543 s (09:03), completed Jun 8, 2020 6:04:41 PM
[info] Reapplying settings...
[info] set current project to firrtl (in build file:.../firrtl/)
[info] Setting Scala version to 2.11.12 on 1 projects.
[info] Excluded 1 projects, run ++ 2.11.12 -v for more details.
[info] Reapplying settings...
[info] set current project to firrtl (in build file:.../firrtl/)
[info] Wrote .../firrtl/target/scala-2.11/firrtl_2.11-1.4-SNAPSHOT.pom
[error] Modules were resolved with conflicting cross-version suffixes in ProjectRef(uri("file:.../firrtl/"), "benchmark"):
[error]    edu.berkeley.cs:firrtl _2.12, _2.11
[warn] Multiple main classes detected.  Run 'show discoveredMainClasses' to see the list
[error] java.lang.RuntimeException: Conflicting cross-version suffixes in: edu.berkeley.cs:firrtl
[error] 	at scala.sys.package$.error(package.scala:30)
[error] 	at sbt.librarymanagement.ConflictWarning$.processCrossVersioned(ConflictWarning.scala:39)
[error] 	at sbt.librarymanagement.ConflictWarning$.apply(ConflictWarning

That is, it compiles and passes the tests for Scala 2.11.12, but fails when it tries to run the tests for 2.12.11.

sbt +clean +test works.
sbt +publishLocal and sbt publishLocal fail.

This does seem to depend on history.
Running sbt publishLocal && sbt +publishLocal works.


Issue #876: Fix integer overflow on slice_count

If the slice count doesn't fit into uint32_t, consider that the memory allocation failed.
On Linux s390x, allocating around 8,589,934,592 GiB with mmap() works thanks to overcommit on a machine with 8 GiB of memory:
mmap(NULL,
     0x8000000000400000,
     PROT_READ | PROT_WRITE,
     MAP_PRIVATE | MAP_ANONYMOUS | MAP_NORESERVE,
     -1, 0)

microsoft.mimalloc Failing after 3m — Build #20240415.2 failed
Hum, it doesn't seem to be related to my change:
1: =================================================================
1: ==1864==ERROR: LeakSanitizer: detected memory leaks
1:
1: Direct leak of 4097 byte(s) in 1 object(s) allocated from:
1:     #0 0x56446f10728e in __interceptor_malloc (/home/vsts/work/1/s/debug-asan-clang/mimalloc-test-api+0xa228e) (BuildId: f63f94b5f9da6b5b7cc6c667411035f8024a4297)
1:     #1 0x56446f0bb0f6 in __interceptor_realpath (/home/vsts/work/1/s/debug-asan-clang/mimalloc-test-api+0x560f6) (BuildId: f63f94b5f9da6b5b7cc6c667411035f8024a4297)
1:     #2 0x7f8fd7c0f4c1 in mi_heap_realpath /home/vsts/work/1/s/src/alloc.c:396:19
1:     #3 0x7f8fd7c0f544 in mi_realpath /home/vsts/work/1/s/src/alloc.c:420:10
1:     #4 0x56446f1458f9 in main /home/vsts/work/1/s/test/test-api.c:299:15
1:     #5 0x7f8fd7829d8f  (/lib/x86_64-linux-gnu/libc.so.6+0x29d8f) (BuildId: c289da5071a3399de893d2af81d6a30c62646e1e)
1:
1: SUMMARY: AddressSanitizer: 4097 byte(s) leaked in 1 allocation(s).

Thanks so much for spotting this! I fixed it differently by defining a MI_MAX_ALLOC_SIZE and limiting it to at most MI_SEGMENT_SLICE_SIZE * (UINT32_MAX-1) (and adding assertions).  If you can, can you verify this works for your tests?

I fixed it differently by defining a MI_MAX_ALLOC_SIZE and limiting it to at most MI_SEGMENT_SLICE_SIZE * (UINT32_MAX-1) (and adding assertions).

Do you have a link to the fix? https://github.com/microsoft/mimalloc/commit/5050b630389bb4d2013d1e82cc1b2c2d9b65b963 only defines MI_MAX_ALLOC_SIZE as PTRDIFF_MAX. Is it the same fix?

Ah, for dev PTRDIFF_MAX is still the limit as it has no "slices". (dev = v1.x),
but for the  dev-slice branch the new limit is UINT32_MAX as in the commit 78418b3. (dev-slice == v2.x).

If you can, can you verify this works for your tests?

Sorry, but it's quite complicated to set up the test :-/  Thanks for the fix anyway!


Siri not Recognizing turn off mode

Hey 👋🏻
I’ve encountered a problem since the latest iOS update. I can normally turn on my units but when I want to turn it off it says the same message as when it turns it on and won’t turn the units off.
is it linked to the plug-in ?
Thanks

Hi! I can't tell but a way to find out is through pressing the buttons in the Home app instead of asking Siri. If the buttons work as intended, then it's a Siri-related issue which is beyond the scope of this plugin as it's abstracted away from us.