Material button update

Revised ButtonTheme, added a buttonTheme to ThemeData.
Rewrote the implementations of MaterialButton, RaisedButton and FlatButton in terms of a new ShapedMaterialButton widget.
ButtonTheme, RaisedButton, and FlatButton now have a ShapeBorder shape parameter.
The ButtonTheme inherited Widget is now defined, like Theme, in terms of ButtonThemeData. The value of ThemeData.buttonTheme is a ButtonThemeData object.
Added a ButtonTextTheme (enum) value: ButtonTextTheme.primary. When the button theme is configured with ButtonTextTheme.primary the appearance and geometry or RaisedButton and FlatButton change slightly, in terms of shape, padding, and colors. The name "primary" stems from the fact that the button's dominant color is the theme's primary color. I think it's an improvement :-).
FlatButton had textTheme (a ButtonTextTheme), textColor, and disabledTextColor properties. Now both RaisedButton does too.
FlatButton and RaisedButton have new shape and padding properties which default to the ButtonTheme's values.
Added FlatButton.icon() and RaisedButton.icon() constructors which create a properly padded and Directionality-sensitive button that has both a label and an icon.
Here's a screenshot of raised and flat buttons using ButtonTextTheme.normal:

Here's a screenshot for ButtonTextTheme.primary.:

There are two incompatible changes here:

ButtonTheme no longer has a const constructor.
ButtonTheme.of(context) returns a ButtonThemeData, not a ButtonTheme widget.

I don't think either of these changes will affect most applications. The odd ButtonTheme lookup, like:
ButtonTheme.of(context).padding.horizontal / 4.0;

will continue to work as it did before.

Some high-level comments:

There's a lot of code duplication that we can probably improve, maybe by having FlatButton and RaisedButton share a (private) base class, or moving their common logic into MaterialButton/ShapedMaterialButton.
I'd like to understand more about ShapeMaterialButton vs MaterialButton. Intuitively, I would have expected us to just have one general "button" class, used by Flat and Raised. I'm worried that just as before when we had Flat and Raised people used MaterialButton directly, we're just going to end up with people using all four more or less at random instead.

I'm having trouble justifying the existence of MaterialButton in this model, and I'm still uncomfortable with the way very similar code is in three places in some instances. I think we could solve both problems with some rearranging of the code so that RaisedButton and FlatButton both leverage MaterialButton more (either through inheritance, which would reduce the duplication of docs substantially too, or via composition or just calling shared static methods on MaterialButton). I don't think we have to solve that in this PR, if you don't want to, but I do think it's worth doing.
My only real concern with this PR is that FlatButton now generates a Material widget. FlatButton is very much intended to not generate a Material, that's what it means for it to be flat. The simplest fix is probably just a boolean on RawMaterialButton (create material; if the boolean is false, then the elevations must be false, and the shape is drawn with an Ink instead; the clip region for the InkWell might need to be propagated through somehow too though this can be something we deal with later).

Currently InkWell doesn't support a shape parameter, so it's not possible to configure a FlatButton's clip correctly without an underlyiing Material widget.  I don't think there's any harm in creating flat buttons with an elevation=0 Material widget and it's simpler that way.

The harm would mostly be that if you also overlaid an Ink widget on top of the FlatButton widget, the picture would go under the button instead of on top.


Required for pen test

:+1:


install 'riff' binary instead of 'riff-cli'

Is there a way to coerce go to use riff as the binary name?
~/go/src/github.com/projectriff/riff-cli (master)$ go install -v
github.com/projectriff/riff-cli

This worked for me:
go install $GOPATH/src/github.com/projectriff/riff-cli/riff.go

I think the more idiomatic way is to have the main go package inside a riff directory, either in this repo or in the future monorepo.
The
go get github.com/projectriff/riff-cli/riff

@ericbottard asked me to implement the idiomatic approach. Please see PR https://github.com/projectriff/riff-cli/pull/47.


perf: eliminate small allocation on remote calls

Eliminate this allocation that happens in every remote method call:

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


Any support for Opennebula 5+?

The Gem dependencies for version 0.4.8 of the chef-provisioning-opennebula gem list opennebula < 5.    Is there any support for more recent Opennebula releases greater than 5 (we have recently upgrade to 5.2.1)?
We have tried provisioning with older versions (4.14.2) of the opennebula gem but generate a gem dependency error.
Gem::MissingSpecVersionError
----------------------------
Could not find 'opennebula' (~> 5.2.1) - did find: [opennebula-4.14.2]
Running with opennebula gem 5.2.1 generates a different error:
NameError
---------
uninitialized constant OpenNebula::Document

FYI ... this was open sourced by BlackBerry and a lot of things have changed at BlackBerry since this was released.  One of those things is that I am no longer with the company; I wrote 90% of the initial code.  I would be more than happy to update the driver if I had access to OpenNebula 5+.  Right now I can't tell you when or if there would be an update to support OpenNebula 5+, because I am no longer with the company.  To be on the safe side I'd say "You're on your own".

@thebrooder  - Opennebula 5.x is supported (and tested) with version 0.4.9 of the gem. It also provides backwards compatibility with ONE <5.
There is a known issue with the driver when running chef provisioning against different ONE versions in the same recipe, the driver tries to overload a new opennebula gem version and it's denied by the ruby kernel. This can happen mostly in an upgrade scenario where you run multiple versions of Opennebula in different environments. I'm working on a fix soon to be released.


#58: Перехват исключений

Job gh:dronmdf/telebot#69 is in scope.

Job gh:dronmdf/telebot#69 assigned to @1640max, please go ahead (policy).

@0crat out

Are you speaking to me or about me? You must always start your message with my name if you want to address it to me.

@0crat out

@0crat out (here)

@DronMDF @1640max resigned from gh:dronmdf/telebot#69, since the job is not in scope anymore.

@0crat out (here)

@DronMDF Job gh:dronmdf/telebot#69 is now out of scope.


Fetch rows in JSON format

Summary
This is a draft PR which adds the support for fetching rows in JSON format.
The current Query::fetch fetches the results using FORMAT RowBinary only which requires a strict 1:1 mapping between the query schema and the deserialized type.
And that has a lot of limitations:

#10
#101
#53
etc

This PR allows the row deserialization into a T: Deserialize which eliminates the limitations of Query::fetch:

when the table schema is not known: SELECT * from ?
when the table schema is not specified: DESCRIBE TABLE ?
when we read less columns than we select

Unresolved questions

am aware (well, now) of https://github.com/suharev7/clickhouse-rs but while that library lifts some of the limitations, it's very different from this one and I'd rather stick to this in hope that #10 will eventually be supported
the naming Query::json, Query::json_one, Query::json_all is very unfortunate

maybe, Query::fetch_json, Query::fetch_json_one would be better albeit verbose

Query::json requires the watch feature which is a bit misleading - we can improve this

Checklist
Delete items not relevant to your PR:

[x] Unit and integration tests covering the common scenarios were added
[ ] A human-readable description of the changes was provided so that we can include it in CHANGELOG later
[ ] For significant changes, documentation in README and https://github.com/ClickHouse/clickhouse-docs was updated with further explanations or tutorials

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

Let's extract Debug impl for Query as a separate PR as it addresses https://github.com/ClickHouse/clickhouse-rs/issues/146 (thank you!), so that it can be merged quickly, while we are discussing the rest.

+1 on naming json fetch_json etc

Could it be a more flexible approach to provide a "raw" method such as

@slvrtrn That would be useful on its own as well - see #154, #60, etc.

First of all, the only reason why this crate already contains (conditionally!) serde-json is only WA for WATCH, which will go away with moving to the Native format.
Secondly, the initial problem is the absence of dynamic schemas, not the "I want exactly JSON" problem.
Thus, we should avoid any additional formats that should be covered by basic cursor-like API (Apache Arrow can have another column-based API, for instance). I want to remember that the semantics of the current query() API is not "give me RowBinary". It's about providing Rust structures. RowJsonCursor<T> seems very unobvious to me. JSON is a string in some predefined format and it isn't related to any T.
By providing such specific interfaces, we're opening a black hole: the next request will be "I want CSV format", "I want Vertical (lol) format", and so on. All these formats will be difficult to support later, because Bytes -> T deserialization can be very differently implemented (think about Native or any other column-based formats). So, I think that Cursor<T> should have only one possible implementation (or several ones if it's required for some sort of WA), but only as implementation details. Yep, it can even use JSON internally if the user wants schemas not supported by RowBinary, but it's not "I want JSON"; it's "I want dynamic schemas" flag/inference.
@slvrtrn's suggestion about query_raw seems much more flexible and doesn't lead to new dependencies. But, again, it doesn't provide any -> T deserialization, only async iterator over chunks. And it's great: if a user wants to parse it on his own, it's okay.

Secondly, the initial problem is the absence of dynamic schemas

Correct. I stated the original problem: it's impossible right now to get the result of DESCRIBE TABLE using clickhouse-rs. And https://github.com/ClickHouse/clickhouse-rs/issues/10 is 3 years old already.
Of course, query_raw could also cover this issue (even if everybody will be forced to write their own deserializer) - but when? If another 3 years, then it's better to have at least something that unblocks use cases similar to #10.
If only we had a working PostgreSQL interface, we'd stick with sqlx. Or a native sqlx-clickhouse driver would be even more perfect.

query_raw could also cover this issue (even if everybody will be forced to write their own deserializer) - but when?

Actually, I think we can implement query_raw pretty fast. At least, I don't see any issues with it now.

If another 3 years

I totally understand your displeasure. There are several points why it wasn't resolved in time:

This crate was a personal initiative during my free time so that I couldn't solve any more-than-trivial issues unrelated to my needs.
Moving to RowBinaryWithNamesAndTypes seems to result in a performance penalty or unmaintainable code. Native could potentially solve these problems, but it's undocumented and, formally, unstable.

I hope both reasons become irrelevant now that ClickHouse's team members have begun working on this crate.

Or a native sqlx-clickhouse driver would be even more perfect.

Maybe yes, maybe not. It's not a simple statement. I liked the SQLx-like approach much more until we (I mean, in my team) started actively using it (for PostgreSQL), and.. ok, let's say that it's full of pain for multiple nontrivial tasks. But I don't want to delve into this topic here, it's worth considering after the sqlx support by detailed comparison and benchmarking. I'll be totally fine if CH env team decides to focus on sqlx instead of this crate as the official approach.

So, query_raw()?

So, query_raw()?

@loyd All right. Thanks for the very detailed explanation about the background of this!

@pravic, do you think something like this could work instead? (there are also examples) https://github.com/ClickHouse/clickhouse-rs/pull/182


plural expressions can brake syntax highlighting

@Component(/* */)
export class SomeComponent {
  public list: string[];
}

  {list.length, plural, =1 {One Item} other {{{list.length}} Items}}

some mor text

will look like this:

everything after the expression looses highlighting

Ah, this is the ICU expression format. It is currently not supported.
I will look into this when I have time.

@dlvandenberg I have opened PR #18 to solve this, comments and suggestions will be much appreciated


Update the right method to substr

Hello man I think substr is better fit for here but its your decision. Thanks for this kind of repo.

Either solution is fine.


Copy room link on click

Hello,
As earlier there was no option to copy video chat link on click. Now instead of making an another button,
i added the copyLink function to Label onClick event listener, also made the label cursor pointer.

Hey @yahya-cloud,
Your work looks good to me. Can you add a snackbar notification that pops up when the link is copied?
You can look at MUI Snackbar to see how snackbars work.

Hello @Rishabh-malhotraa , yes sure i will add it and can  you please add GGSOC label to this pull request.

hello @Sahaj-Srivastava24, as i saw react-toastify was used in this project so added the toast function inside copy link function, instead of using mui snackbar. Now when we copy the link a toast appears of type success with text "Link copied" .

Sorry @yahya-cloud we decided to move Vita-Meet outside from our main app. So we couldn't merge this PR Hope you will understand! 😔
Though thanks for giving us your valuable time, we will look forward to see successful contributions from you!


click_man traceback

python3 setup.py --command-packages=click_man.commands man_pages
running man_pages
Load entry point packit
Generate man pages for packit
Traceback (most recent call last):
  File "setup.py", line 27, in <module>
    setup(use_scm_version=True)
  File "/usr/lib/python3.7/site-packages/setuptools/__init__.py", line 145, in setup
    return distutils.core.setup(**attrs)
  File "/usr/lib64/python3.7/distutils/core.py", line 148, in setup
    dist.run_commands()
  File "/usr/lib64/python3.7/distutils/dist.py", line 966, in run_commands
    self.run_command(cmd)
  File "/usr/lib64/python3.7/distutils/dist.py", line 985, in run_command
    cmd_obj.run()
  File "/usr/lib/python3.7/site-packages/click_man/commands/man_pages.py", line 69, in run
    write_man_pages(name, cli, version=self.version, target_dir=self.target)
  File "/usr/lib/python3.7/site-packages/click_man/core.py", line 56, in write_man_pages
    man_page = generate_man_page(ctx, version)
  File "/usr/lib/python3.7/site-packages/click_man/core.py", line 40, in generate_man_page
    return str(man_page)
  File "/usr/lib/python3.7/site-packages/click_man/man.py", line 102, in __str__
    lines.append('  ' + self.replace_blank_lines(description))
  File "/usr/lib/python3.7/site-packages/click_man/man.py", line 59, in replace_blank_lines
    s.split('\n'))
AttributeError: 'NoneType' object has no attribute 'split'

I've checked that all @click.option have help defined.
Originally posted by @jpopelka in https://github.com/packit-service/packit/pull/256#issuecomment-492292887

While debugging I realized that it's a short_help, not help that click_man (the version in Fedora30) tries to split, so I'm wondering how your #256 could have worked.
It was fixed upstream in https://github.com/click-contrib/click-man/pull/24 but we still use old version in Fedora.

so I'm wondering how your #256 could have worked.

because I'm the best!
so what do we need to do here? should setting the short_help be enough?

The thing is that you can't directly set short_help. Click generates it from help, but click_man has to use the correct function, which the click_man version in Fedora does not.
The only way I see is to wait until click_man-0.3.0 gets into Fedora. Therefore I've commented the man pages generation from spec for now. Sorry.

we can file it as an issue, build it and update, I'm a proven packager so I should be able to do all of those


[RFC]: Continuous Integration Design

This issue is an extension of #428 and it is an RFC to verify if there is a consensus with this new design
Feature description
A new design for continuous integration might be the following one:

One job for code formatting and linting issues
One job that runs all std tests on Linux
One job that runs all std tests on MacOs
One job that runs all std tests on Windows
One job that runs all no-std tests

Let's try to tackle each point one-by-one

(1) Some GitHub actions allow to visualize clippy lints and bad formatting as messages in a PR or in a report. This approach reduces the time spent in detecting these problems because they are immediately viewable. A contributor, especially a new one, does not have to scrape through CI logs in order to find them. This job could run only on a Linux operating system. Running this job on more operating system could be a waste of resources.

(2, 3, 4) Run all current checks and tests on the specific operating system using a script. The run-checks.sh script could be rewritten in Rust language in order to be cross-platform and less error-prone. Collect code coverage data through Rust source code coverage and then aggregate the results using grcov, finally publish this data on codecov in order to immediately visualize which lines of code are not covered by tests.

(5) Maintain the same checks which are already performed. Even this job will benefit from run-checks.sh rewriting in Rust.

Feature motivation
Having a Continuous Integration that implements the points described above, in my opinion, reduces the effort in code maintainability, making the development more interesting, also decreases the possibility to have problems in the future.

What we still have to implement :

[ ] Use GitHub Actions filters to avoid running CI for nothing
[ ] Implement Grcov checks ONLY on CI
[ ] Try another strategy to run clippy on CI
[ ] Add MacOS and Windows configurations through matrix

@Luni-4  I have 2 points to consider:

Should we run Rust Doc just once on the same job as Rust Clippy?
Can we minimize running coverage? Maybe run coverage in Linux jobs and then run coverage for specific packages on other OS?

Yeah, I just meant to keep like that. I think I misread the first post because I thought the doc was going to run for windows/mac/linux. :+1:

Besides, should I close this PR https://github.com/burn-rs/burn/pull/797 , so to implement this RFC in a new PR ?

@gonzalesMK
Perhaps we can transform each bullet point into a PR, in this way it would be simpler to review. What do you think?

@nathanielsimard
Yep, the mold idea is contained in the link provided by @gonzalesMK

Perhaps we can transform each bullet point into a PR, in this way it would be simpler to review. What do you think?

Sounds good to me.

Thanks to @gonzalesMK, @dcvz, and @syl20bnr this issue can be closed! Congrats to everyone for your work and help!


remove report outputs from version control or have them in separate branches?

If model is to support runs with different parameters I don't think it makes much sense to include the output report csv files in the main branch of repo, this would get confusing fast.
Having outputs csv summaries (and associated parameters) in separate branches may be helpful? May not be worth the effort, just managing multiple model runs (parameters and outputs) locally might be good enough - the db has to be managed anyway if the same user is running the different scenarios.

closing for now, sort of fixed with https://github.com/smnorris/bcfishpass/commit/c98e42909189bba49b6121678ebd21b71756086f (commit message noted wrong issue).


SAMZA-1890: Fix the creation of MapFunction in TestExecutionPlanner.

@dnishimura Kindly take a look.

Can't believe m -> m and m -> { return m; } aren't the same and the former causes compilation error, but oh well 🤣. LGTM.

Fixed.


Handle truncation in get_docids_for_value_range

DateTime values can be truncated via DatePrecision. The same truncation needs to be applied to get_docids_for_value_range calls.
If we hit or not depends on the truncation setting, depending if we truncate 123  to 100 or 120, a call to  get_docids_for_value_range with 110 would hit or not.

As discussed we will choose 3, since this issue is rather unusual


Typo in shortlink included

Hi,
There's a typo in the shortlink aka.ms/domainshringpreview causing to not land on the proper Forms page.
Should be updated to aka.ms/domainsharingpreview
Thank you,
Corina
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: c61c960c-f5c3-76f7-ac18-dfeaf30230e4
Version Independent ID: 3dc607b2-869e-976f-80da-d73cfb1210e5
Content: Cross-tenant mailbox migration - Microsoft 365 Enterprise
Content Source: microsoft-365/enterprise/cross-tenant-mailbox-migration.md
Service: microsoft-365-enterprise
GitHub Login: @kelleyvice-msft
Microsoft Alias: kvice

@Corina-github Thank you for your feedback. We have made changes to the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/9789
Once the author approves, the changes will be live.
Thanks
Sri

@msbemba Thank you very much for the contribution and updating the documentation with PR. @Corina-github Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


panic in glx makeCurrent()

Starting from somewhere between 28a30dc and 2e84aca, glutin panics upon initialization using Xinerama.
Proof of concept code:
extern crate glutin_window;
extern crate window;

fn main() {
    let settings = ::window::WindowSettings::new("Test", [100, 100]);
    let settings = settings.srgb(true);
    let mut window: ::glutin_window::GlutinWindow =
        settings.build().unwrap();
}

Dependencies:
pistoncore-glutin_window = "0.24.0"
pistoncore-window = "0.17.0"

System info:
OS: Arch Linux
Kernel: x86_64 Linux 4.8.11-1-ARCH
Shell: bash 4.4.5
Resolution: 5120x1080
WM: OpenBox
WM Theme: Static
CPU: Intel Core i7-4790K CPU @ 4.4GHz
GPU: GeForce GTX TITAN, GeForce GTX 660
RAM: 12152MiB / 15993MiB
NVIDIA Driver Version: 375.20

Backtrace:
thread 'main' panicked at 'glx::MakeCurrent failed', glutin/src/api/glx/mod.rs:112
stack backtrace:
   1:     0x55b3b5fd260f - std::sys::backtrace::tracing::imp::write::h6f1d53a70916b90d
   2:     0x55b3b5fd635d - std::panicking::default_hook::{{closure}}::h137e876f7d3b5850
   3:     0x55b3b5fd5280 - std::panicking::default_hook::h0ac3811ec7cee78c
   4:     0x55b3b5fd5888 - std::panicking::rust_panic_with_hook::hc303199e04562edf
   5:     0x55b3b5ea9053 - std::panicking::begin_panic::h341b039f84d0b176
                        at /build/rust/src/rustc-1.13.0/src/libstd/panicking.rs:413
   6:     0x55b3b5ebd8b1 - <glutin::api::glx::Context as glutin::GlContext>::make_current::hf6af1578880cc462
                        at /home/static/projects/rust/test/glutin/src/api/glx/mod.rs:112
   7:     0x55b3b5e86d5a - <glutin::platform::platform::x11::Window as glutin::GlContext>::make_current::h4c1fad5693b1d96e
                        at /home/static/projects/rust/test/glutin/src/platform/linux/x11.rs:224
   8:     0x55b3b5e870d5 - <glutin::platform::platform::api_dispatch::Window as glutin::GlContext>::make_current::hc2a3ea556c579ca6
                        at /home/static/projects/rust/test/glutin/src/platform/linux/api_dispatch.rs:204
   9:     0x55b3b5e854fb - glutin::window::<impl glutin::Window>::make_current::hde6baf522c383c98
                        at /home/static/projects/rust/test/glutin/src/window.rs:421
  10:     0x55b3b5e88105 - glutin_window::GlutinWindow::new::h41a7b7b17fb6e178
                        at /home/static/.cargo/registry/src/github.com-1ecc6299db9ec823/pistoncore-glutin_window-0.32.0/src/lib.rs:101
  11:     0x55b3b5e8a54b - <glutin_window::GlutinWindow as window::BuildFromWindowSettings>::build_from_window_settings::h1674704533958661
                        at /home/static/.cargo/registry/src/github.com-1ecc6299db9ec823/pistoncore-glutin_window-0.32.0/src/lib.rs:361
  12:     0x55b3b5d549bb - window::WindowSettings::build::he9ad6f90d683233c
                        at /home/static/.cargo/registry/src/github.com-1ecc6299db9ec823/pistoncore-window-0.23.0/src/lib.rs:367
  13:     0x55b3b5ccb789 - <conrod::backend::piston::window::Window<W> as window::BuildFromWindowSettings>::build_from_window_settings::h069ab87861de0e69
                        at /home/static/.cargo/registry/src/github.com-1ecc6299db9ec823/conrod-0.47.1/./src/backend/piston/window.rs:107
  14:     0x55b3b5d5497b - window::WindowSettings::build::h7ac822fee94b4727
                        at /home/static/.cargo/registry/src/github.com-1ecc6299db9ec823/pistoncore-window-0.23.0/src/lib.rs:367
  15:     0x55b3b5d7f8a7 - test::main::h54409382dcf76ebd
                        at /home/static/projects/rust/test/src/main.rs:33
  16:     0x55b3b5fddcb6 - __rust_maybe_catch_panic
  17:     0x55b3b5fd4af1 - std::rt::lang_start::h538f8960e7644c80
  18:     0x55b3b5d84b73 - main
  19:     0x7f260d1ae290 - __libc_start_main
  20:     0x55b3b5ccb5d9 - _start
  21:                0x0 - <unknown>

I'm not sure if this is the correct repository for the report, as I notice a lot of code was shifted over to winit during that time, please let me know if you need anything else. Thanks ^^

Just to verify that this is a pure glutin thing, since it just dawned on me that I did run this off of piston in the initial report, I went ahead and ran the example from the readme with the same results.
thread 'main' panicked at 'glx::MakeCurrent failed', /home/static/.cargo/registry/src/github.com-1ecc6299db9ec823/glutin-0.7.0/src/api/glx/mod.rs:112
stack backtrace:
   1:     0x560a1ea09e6f - std::sys::backtrace::tracing::imp::write::h6f1d53a70916b90d
   2:     0x560a1ea0cf9d - std::panicking::default_hook::{{closure}}::h137e876f7d3b5850
   3:     0x560a1ea0c290 - std::panicking::default_hook::h0ac3811ec7cee78c
   4:     0x560a1ea0c898 - std::panicking::rust_panic_with_hook::hc303199e04562edf
   5:     0x560a1e8e2de3 - std::panicking::begin_panic::h341b039f84d0b176
                        at /build/rust/src/rustc-1.13.0/src/libstd/panicking.rs:413
   6:     0x560a1e8f7521 - <glutin::api::glx::Context as glutin::GlContext>::make_current::hc6c39b249ef78dcd
                        at /home/static/.cargo/registry/src/github.com-1ecc6299db9ec823/glutin-0.7.0/src/api/glx/mod.rs:112
   7:     0x560a1e8c4f9a - <glutin::platform::platform::x11::Window as glutin::GlContext>::make_current::hcad1cbabbbbb24f3
                        at /home/static/.cargo/registry/src/github.com-1ecc6299db9ec823/glutin-0.7.0/src/platform/linux/x11.rs:224
   8:     0x560a1e8c5295 - <glutin::platform::platform::api_dispatch::Window as glutin::GlContext>::make_current::h02589fa8810a419e
                        at /home/static/.cargo/registry/src/github.com-1ecc6299db9ec823/glutin-0.7.0/src/platform/linux/api_dispatch.rs:204
   9:     0x560a1e8c494b - glutin::window::<impl glutin::Window>::make_current::h91be540734613e78
                        at /home/static/.cargo/registry/src/github.com-1ecc6299db9ec823/glutin-0.7.0/src/window.rs:416
  10:     0x560a1e8c5613 - gtest::main::h465153c8042fa903
                        at /home/static/projects/rust/gtest/src/main.rs:8
  11:     0x560a1ea148f6 - __rust_maybe_catch_panic
  12:     0x560a1ea0bb01 - std::rt::lang_start::h538f8960e7644c80
  13:     0x560a1e8de123 - main
  14:     0x7f2a9eaf5290 - __libc_start_main
  15:     0x560a1e89df89 - _start
  16:                0x0 - <unknown>

Update: Apparently it has nothing to do with Xinerama. I just removed Xinerama and it still continues to panic. Tried with the nouveau driver and it worked fine, switched back to the proprietary nvidia driver and it broke again.
$ grep -RIi 'xinerama' /etc/X11/
$
Also tried both scenarios in xfce4, so not related to openbox either.

Another update, set an X11 error handler in context, which returns error code 8 (BadMatch)

I have the same error message when trying to run the example  (cargo run --example window)
I'm on opensuse 13.1 if it helps

Having the same issue here, running arch linux with an nvidia gpu on X11.

I'm also experiencing this issue, it does not occur on my Macbook using Intel graphics, nor does it occur with Nouveau, but it does occur using the proprietary Nvidia drivers on Archlinux.  I've determined that I can in fact run the examples if I set RGB depth to 8 bits each, but alpha to 0.  If alpha is set to 8 bits, the panic occurs.  Other OpenGL applications appear to work fine (glxgears, glmark2, Steam games, etc.).  My guess is that some additional logic needs to be added to the choose_fbconfig function in api/glx, but I haven't been able to determine which parameter is incorrect in this case.

Same issue here, linux mint 18, using nvidia drivers.
I can confirm what @tanderegg is saying.
Running the window example, the frame buffer config returned from choose_fbconfig matches a visual on my system with 32bit buffer size and each rgba bit of size 8, and the winit window uses one with alpha set to zero.

I just checked, and it seems that window and context are created with different visuals now. I'm not an expert in glX, but this reference states that such beheviour causes a Bad match error, and thats exactly what happens when using nvidia driver.
The way winit currently works is that it creates its window with visual alway inherited from its parent, that is root window. On nouveau, this visual in my case has buffer size of 32 bits and even when creating context with alpha bit set to 0, glx::Make_current works fine, so it seems to me that maybe it works if context's visual buffers are bigger then drawable's. That makes sense considering the direction data travels between context and drawable. Using nvidia driver on the the other hand, root's visual is set to one with 24 bit buffer, and so is windows', causing panic.

@rerion - I've confirmed that this is the problem - I modified winit to use the same visual ID as GLX, make_current succeeded.  I had to make another change as well - apparently, in order for a window to use a different buffer bit depth than its parent, it must have a colormap defined (see this SO: http://stackoverflow.com/questions/3645632/how-to-create-a-window-with-a-bit-depth-of-32).  At first I was receiving new BadWindow errors that were quite unclear, but adding a call to XCreateColormap fixed the problem.
@tomaka - It seems to me that the best way to handle this would be to allow the user to send a specific Visual ID to winit's window_builder, which would override the default behavior of inheriting the visual from the root window.  Then Glutin would have to be modified to pass the Visual ID of the context to winit after it has been determined via GLX.  Does that sound reasonable?

Does that sound reasonable?

Yes. The Visual ID could be passed with the platform-specific window builder stuff.

@tomaka Cool, I'll try and put together PR's for winit and glutin that implement this, may be a few days though.  Thanks!

Any other info on this issue?

What needs to be done:

[ ] Rework this function: https://github.com/tomaka/glutin/blob/6c469bfb4641ca3094862a45a80331f6f6ded400/src/platform/linux/api_dispatch.rs#L78-L104. Don't build the winit window directly in this function, but instead pass the window builder to either x11::Window::new or wayland::Window::new.
[ ] Add freestanding functions here to query the X11 connection: https://github.com/tomaka/winit/blob/bc0dd0f854bca9d3a526814b53508dcfd25a74e2/src/os/unix.rs
[ ] Add a method in this trait to allow passing a XVisualInfo: https://github.com/tomaka/winit/blob/bc0dd0f854bca9d3a526814b53508dcfd25a74e2/src/os/unix.rs#L145. Use a raw pointer or a raw integer (depending on the actual type of XVisualInfo), do not reexport the type directly from the bindings. You can take inspiration here: https://github.com/tomaka/winit/blob/bc0dd0f854bca9d3a526814b53508dcfd25a74e2/src/os/windows.rs#L27
[ ] Do the same for the screen id (with another method).
[ ] Copy-paste this code to glutin and pass the screen id to the winit window builder: https://github.com/tomaka/winit/blob/bc0dd0f854bca9d3a526814b53508dcfd25a74e2/src/api/x11/window.rs#L306-L309
[ ] Modify this function to create the context prototype, then query the XVisualInfo, then pass it to the winit builder, then build the window: https://github.com/tomaka/glutin/blob/6c469bfb4641ca3094862a45a80331f6f6ded400/src/platform/linux/x11.rs#L113
[ ] The XVisualInfo is passed here: https://github.com/tomaka/winit/blob/bc0dd0f854bca9d3a526814b53508dcfd25a74e2/src/api/x11/window.rs#L373 instead of ffi::CopyFromParent as *mut _

@tomaka Yep, it's fixed now. Thanks @rerion!

I have same issue in glium 0.16.0 (glutin 0.7.1). Replacing glutin dependency with master branch fixed the issue.

I can confirm that this issue is resolved for me as well.  Thanks @rerion!

I was just reading through some open issues, ping to everyone in the thread, can this be closed?

It now works for me, so I believe the issue is resolved.
On Mon, Jun 12, 2017 at 3:27 PM Benjamin Adamson<EMAIL_ADDRESS>wrote:

I was just reading through some open issues, ping to everyone in the
thread, can this be closed?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tomaka/glutin/issues/834#issuecomment-307889590, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAGGvZxHCIluWV8q_-ebCnGBELuSUJTwks5sDYymgaJpZM4LDkzj
.

Thanks


i18n(fr): Update basics/* from #9240

Description (required)
i18n(fr): Update basics/* from #9240 :

[x] astro-components (Err link : (waiting for reference/directives-reference waupdated))
[x] astro-pages
[x] layouts
[x] project-structure

[!NOTE]
Err link at L23 astro-components, waiting for reference/directives-reference

Related issues & labels (optional)

Closes #
Suggested label: i18n

LGTM, just two tiny nits... And the two broken links... but that will have to wait... I have a feeling Yan is going to have fun merging the PRs... 😅

Thanks you for your review!

The broken link in directives-reference.mdx should be fixed with #10195 but there's still a broken link in layout.mdx.

Haven't looked into this PR, but wanted to mention that it would be very appreciated if the changes from #10327 could be translated as well... 🙏🥺

Haven't looked into this PR, but wanted to mention that it would be very appreciated if the changes from #10327 could be translated as well... 🙏🥺

Hello! Thanks for your head up about the recent modification from #10327! I just added modifcations with ebf9316 (#10133)


Add Funnel data

Proposed changes
Types of changes

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update

Checklist

[ ] I have read the CONTRIBUTING doc
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)
[ ] I have added proper type definitions for new commands (if appropriate)

Further comments
Reviewers: @webdriverio/project-committers

WebdriverIO is using fork to spawn workers, and to listen to the messages from workers we need to have access to the child object, but wdio doesn't give child process access (checked onWorkerStart and onWorkerEnd hooks). So we need to resort to saving data in the files itself.

https://webdriver.io/docs/flowcharts/createlocalworkerprocess/
https://github.com/webdriverio/webdriverio/blob/b8ced593d9674d1aaea350c86f6d132564a8b9ae/packages/wdio-local-runner/src/worker.ts#L139

cc @samarsault


Gazetteer search for numbers only.

Fixed.
This did not work previously since XYZ tried to create a lat long position for search term.
A valid lat long position will now cancel the search to backend / 3rd party service.

Please close once added to release notes.

Added to release notes


the Export path not works when Export PCK/Zip

Godot version:

3.2.1
OS/device including version:

macOS 10.15.5
Issue description:

When click Export PCK/ZIP, the default directory is the project root directory, not the Export Path.
And the Export with Debug Checkbox is always checked on.
Steps to reproduce:
Create a project
do export for any platform
close the project
reopen the same project
click Export PCK/ZIP
the default directory is not the export path and the Export with Debug  is always on.
Without restarting the project,these options are recorded on export.
Minimal reproduction project:

The following change would fix the issue:
--- a/editor/project_export.cpp
+++ b/editor/project_export.cpp
@@ -876,6 +876,18 @@ void ProjectExportDialog::_tree_changed() {
 }

 void ProjectExportDialog::_export_pck_zip() {
+       Ref<EditorExportPreset> current = get_current_preset();
+       ERR_FAIL_COND(current.is_null());
+
+       String p_path = current->get_export_path();
+       if (p_path != "") {
+               int pos = MAX(p_path.find_last("/"), p_path.find_last("\\"));
+               if (pos != -1) {
+                       String dir = p_path.substr(0, pos);
+                       export_pck_zip->set_current_dir(dir);
+               }
+       }
        export_pck_zip->popup_centered_ratio();
 }

Before submitting a PR, I wanted to confirm what the expected behavior should be. Right now the code seems to explicitly use the export path only for the general Export case,  and intentionally ignores the path for the Export PCK/ZIP case. Is there a reason for this?
In fact, currently the Export Path is not a directory, but must be a specific file ending with the appropriate extension, e.g. .x86-64. To show the same folder when exporting as PCK/ZIP requires a slightly-hackish behavior to parse the file directory out from the entire path as shown above.

Take iOS export for example,
the work flow would be:
1.export the Xcode project
2.do some custom settings to the project
3.run the Xcode  project on device
4.do some modification in Godot Project
5.export  PCK/ZIP to update the Xcode project
then loop 3 - 4- 5
It would be expect the PCK/ZIP export path alway the same as the Xcode project root directory.

@mrushyendra
How about this issue?
It's quite time consuming to reselect the directory each time when update the PCK file.

@mrushyendra
I have tested the above code, it works, please commit it. Thanks.

@mrushyendra
I have tested the above code, it works, please commit it. Thanks.


CocoaPods could not find compatible versions for pod "auth0_flutter"

Checklist

[X] The issue can be reproduced in the auth0_flutter sample app (or N/A).
[X] I have looked into the README and have not found a suitable solution or answer.
[X] I have looked into the API documentation and have not found a suitable solution or answer.
[X] I have searched the issues and have not found a suitable solution or answer.
[X] I have searched the Auth0 Community forums and have not found a suitable solution or answer.
[X] I agree to the terms within the Auth0 Code of Conduct.

Description
I'm getting the following error after trying to install auth0_flutter
flutter run lib/main.dart
Running "flutter pub get" in mobile-1...                         1,481ms
Launching lib/main.dart on iPhone 14 Pro Max in debug mode...
Upgrading contents.xcworkspacedata
Updating minimum iOS deployment target to 11.0.
Upgrading project.pbxproj
Upgrading AppFrameworkInfo.plist
Upgrading Podfile
Updating project for Xcode compatibility.
Upgrading project.pbxproj
Upgrading Runner.xcscheme
Upgrading Info.plist
Running pod install...                                             508ms
CocoaPods' output:
↳
      Preparing

    Analyzing dependencies

    Inspecting targets to integrate
      Using `ARCHS` setting to build architectures of target `Pods-Runner`: (``)

    Fetching external sources
    -> Fetching podspec for `Flutter` from `Flutter`
    -> Fetching podspec for `auth0_flutter` from `.symlinks/plugins/auth0_flutter/ios`
    -> Fetching podspec for `image_picker_ios` from `.symlinks/plugins/image_picker_ios/ios`
    -> Fetching podspec for `path_provider_ios` from `.symlinks/plugins/path_provider_ios/ios`
    -> Fetching podspec for `shared_preferences_ios` from `.symlinks/plugins/shared_preferences_ios/ios`
    -> Fetching podspec for `url_launcher_ios` from `.symlinks/plugins/url_launcher_ios/ios`
    -> Fetching podspec for `video_player_avfoundation` from `.symlinks/plugins/video_player_avfoundation/ios`
    -> Fetching podspec for `wakelock` from `.symlinks/plugins/wakelock/ios`
    -> Fetching podspec for `webview_flutter_wkwebview` from `.symlinks/plugins/webview_flutter_wkwebview/ios`

    Resolving dependencies of `Podfile`
      CDN: trunk Relative path: CocoaPods-version.yml exists! Returning local because checking is only performed in repo update
    [!] CocoaPods could not find compatible versions for pod "auth0_flutter":
      In Podfile:
        auth0_flutter (from `.symlinks/plugins/auth0_flutter/ios`)

    Specs satisfying the `auth0_flutter (from `.symlinks/plugins/auth0_flutter/ios`)` dependency were found, but they required
    a higher minimum deployment target.

    /Library/Ruby/Gems/2.6.0/gems/molinillo-0.8.0/lib/molinillo/resolution.rb:317:in `raise_error_unless_state'
    /Library/Ruby/Gems/2.6.0/gems/molinillo-0.8.0/lib/molinillo/resolution.rb:299:in `block in unwind_for_conflict'
    /Library/Ruby/Gems/2.6.0/gems/molinillo-0.8.0/lib/molinillo/resolution.rb:297:in `tap'
    /Library/Ruby/Gems/2.6.0/gems/molinillo-0.8.0/lib/molinillo/resolution.rb:297:in `unwind_for_conflict'
    /Library/Ruby/Gems/2.6.0/gems/molinillo-0.8.0/lib/molinillo/resolution.rb:682:in `attempt_to_activate'
    /Library/Ruby/Gems/2.6.0/gems/molinillo-0.8.0/lib/molinillo/resolution.rb:254:in `process_topmost_state'
    /Library/Ruby/Gems/2.6.0/gems/molinillo-0.8.0/lib/molinillo/resolution.rb:182:in `resolve'
    /Library/Ruby/Gems/2.6.0/gems/molinillo-0.8.0/lib/molinillo/resolver.rb:43:in `resolve'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.3/lib/cocoapods/resolver.rb:94:in `resolve'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.3/lib/cocoapods/installer/analyzer.rb:1078:in `block in resolve_dependencies'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.3/lib/cocoapods/user_interface.rb:64:in `section'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.3/lib/cocoapods/installer/analyzer.rb:1076:in `resolve_dependencies'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.3/lib/cocoapods/installer/analyzer.rb:124:in `analyze'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.3/lib/cocoapods/installer.rb:416:in `analyze'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.3/lib/cocoapods/installer.rb:241:in `block in resolve_dependencies'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.3/lib/cocoapods/user_interface.rb:64:in `section'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.3/lib/cocoapods/installer.rb:240:in `resolve_dependencies'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.3/lib/cocoapods/installer.rb:161:in `install!'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.3/lib/cocoapods/command/install.rb:52:in `run'
    /Library/Ruby/Gems/2.6.0/gems/claide-1.1.0/lib/claide/command.rb:334:in `run'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.3/lib/cocoapods/command.rb:52:in `run'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.3/bin/pod:55:in `<top (required)>'
    /usr/local/bin/pod:23:in `load'
    /usr/local/bin/pod:23:in `<main>'

Error output from CocoaPods:
↳

    [!] Automatically assigning platform `iOS` with version `11.0` on target `Runner` because no platform was specified. Please
    specify a platform for this target in your Podfile. See `https://guides.cocoapods.org/syntax/podfile.html#platform`.

Error running pod install
Error launching application on iPhone 14 Pro Max.

Reproduction
Steps followed on this tutorial by Auth0
auth0_flutter version
1.0.2
Flutter version
3.3.9
Platform
iOS
Platform version(s)
iPhone 14 Pro Max

Facing same issue

I have same problem

@alexboulay Are you have Apple M1 as well?

@alexboulay @WickedBrat Please check your ios version in parameter of minimum deployments in general config. I had 11. After rising to 12, the project began to assemble.

Updating it to 12 worked for me! Thanks!


[MINOR] Fix some typos in QueryExecution and TaskSchedulerImpl

What changes were proposed in this pull request?

Fix some typos in QueryExecution and TaskSchedulerImpl.
Why are the changes needed?

The typos confuse users.
Does this PR introduce any user-facing change?

No.
How was this patch tested?

No need to test.

Can one of the admins verify this patch?

Merged to master.


Remove reference potential energy calculation for 3D

We remove the peref calculation for 3D as the result is too inaccurate and the calculation involves a global sort across all MPI ranks which we do not want to do.
Closes #370.

@sjboeing Thanks!


Run formatter during maven build

Use formatter-maven-plugin to ensure that the .java files are always formatted correctly. The definition about how the formatting should be done is contained in formatter-settings.java.
After merging this PR, the master should be compiled and then the newly formatted files should be committed (I didn't want to mix this with this PR).

Cool I'll take a look.


Add methods and props to input element

Fixes #659

Thanks!
@facebook-github-bot import

Thanks for importing.If you are an FB employee go to Phabricator to review internal test results.


DrizzlePac HTML previews not loading

We have new notebooks which are merged but are not generating HTML files (and/or still showing old verions). I was advised to file a new PR to address these.  Thanks in advance!
Merged code:
https://github.com/spacetelescope/hst_notebooks/blob/main/notebooks/DrizzlePac/use_ds9_regions_in_tweakreg/use_ds9_regions_in_tweakreg.ipynb
Old HTML file:
https://spacetelescope.github.io/hst_notebooks/notebooks/DrizzlePac/use_ds9_regions_in_tweakreg/use_ds9_regions_in_tweakreg.html
Merged code:
https://github.com/spacetelescope/hst_notebooks/blob/main/notebooks/DrizzlePac/mask_satellite/mask_satellite.ipynb
Old HTML file
https://spacetelescope.github.io/hst_notebooks/notebooks/DrizzlePac/mask_satellite/mask_satellite.html
Merged code:
https://github.com/spacetelescope/hst_notebooks/blob/main/notebooks/DrizzlePac/align_mosaics/align_mosaics.ipynb
(no HTML file)

@mackjenn Thank you for reporting this issue. I have created #280; once it's merged, it should fix the HTML not rendering the proper state of the main branch. Thanks!

@mackjenn The notebooks are now live.


yandex.music:playlist

paco@asus:~$ youtube-dl --verbose https://music.yandex.ru/users/mylogin/playlists/1000
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'--verbose', u'https://music.yandex.ru/users/beef.myaso/playlists/1000']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2015.09.03
[debug] Python version 2.7.9 - Linux-3.16.0-4-amd64-x86_64-with-debian-8.2
[debug] exe versions: avconv 11.4-6, avprobe 11.4-6, rtmpdump 2.4
[debug] Proxy map: {}
[yandexmusic:playlist] 1000: Downloading webpage
ERROR: An extractor error has occured. (caused by KeyError(u'pageData',)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 287, in extract
return self._real_extract(url)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/yandexmusic.py", line 142, in _real_extract
playlist = mu['pageData']['playlist']
KeyError: u'pageData'
Traceback (most recent call last):
File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 655, in extract_info
ie_result = ie.extract(url)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 293, in extract
raise ExtractorError('An extractor error has occured.', cause=e)
ExtractorError: An extractor error has occured. (caused by KeyError(u'pageData',)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

404 not found.

I removed my login name in the link. Original link: https://music.yandex.ru/users/beef.myaso/playlists/1000

I'm aware of that, 404 with both.

It is most likely region blocked ..

No, I don't think so. All other URLs work fine, e.g. http://music.yandex.ru/users/music.partners/playlists/1245.


Date function supports in PQL

In MySQL, to query the data since the past 1 hour, I can use SQL like:
select count(*) as cnt from  log where date >= DATE_SUB(NOW(),INTERVAL 1 HOUR);

How can I do the same in PQL? Will the date functions be added into PQL?

Hi,
We don't have support for transforms/udf's on filter predicates currently,
but might be able to support it around Q2.
We do support transforms on group-by's, and will do the same for
aggregations next.
You can refer to the following design doc:
https://github.com/linkedin/pinot/wiki/Expressions-&-UDF-support
Thanks,
Mayank
On Fri, Feb 10, 2017 at 7:30 PM, Shadow Walker<EMAIL_ADDRESS>wrote:

In MySQL, to query the data since the past 1 hour, I can use SQL like:
select count(*) as cnt from  log where date >= DATE_SUB(NOW(),INTERVAL 1 HOUR);
How can I do the same in PQL? Will the date functions be added into PQL?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/linkedin/pinot/issues/1051, or mute the thread
https://github.com/notifications/unsubscribe-auth/AMCAzV1McosN3cXC0s69pag5XPxxd-WBks5rbStYgaJpZM4L-D7c
.

@mayankshriv Can we support this now?

This is supported now, please refer to the datetime functions:
https://docs.pinot.apache.org/users/user-guide-query/supported-transformations#datetime-functions

Assume date is a TIMESTAMP type, you can do
select count(*) as cnt from log where date >= now() - fromEpochHours(1)


feat(agent): container builder network aliases

Support custom networks and network aliases for containers.
WithNetworkMode creates a network if the mode is not "" or "none". WithNetworkAliases can be used to set network aliases.

Codecov Report

Merging #99 (8243969) into develop (98d18b4) will decrease coverage by 0.08%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           develop     #99      +/-   ##
==========================================
- Coverage     6.37%   6.29%   -0.09%
==========================================
  Files           62      62
  Lines         4394    4450      +56
==========================================
  Hits           280     280
- Misses        4110    4166      +56
  Partials         4       4

Impacted Files
Coverage Δ

agent/pkg/builder/container/container_builder.go
0.00% <0.00%> (ø)

agent/pkg/builder/container/utils.go
8.26% <0.00%> (-0.36%)
:arrow_down:

agent/pkg/dagent/utils/docker.go
12.66% <0.00%> (-0.03%)
:arrow_down:

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


docs(contributing): Tweak CONTRIBUTING.md

Pre-Submission Checklist

[x] Your pull request targets the staging branch of freeCodeCamp.
[x] Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
[x] You have only one commit (if not, squash them into one commit).
[x] All new and existing tests pass the command npm test. Use git commit --amend to amend any fixes.

Type of Change

[x] Small bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would change existing functionality)
[ ] Add new translation (feature adding new translations)

Checklist:

[x] Tested changes locally.
[ ] Addressed currently open issue (replace XXXXX with an issue no in next line)

Description

The MailHog section was in the middle of the "Set Up freeCodeCamp" section. That made it difficult to skim over the section that was not relevant to your OS. I moved it out into its own section and added titles to it.
There were duplicate sections about naming and squashing commits. I kept the ones that were necessary in the step-by-step PR guide.
Most titles used Title Case, but not all of them did. I made them more consistent.
I added instructions for the cp sample.env .env command on Windows. With this change, I believe it's finally possible to follow this guide on Windows and end up with a working installation 🙌
I changed all instances of "FCC" to "freeCodeCamp". https://twitter.com/ossia/status/941412790325141506

P.S: The PR title is too long.. again nitpicking, but here is why http://conventionalcommits.org/ 😄

Thanks for the thorough review @raisedadead!


How to generate TileConfiguration.txt.

I am working on digital microscopy for whole slide imaging. i am capturing lots of images and at last i need to stitch all of them to create a single image. i was trying your python example but dont know how to create TileConfiguration.txt. Can you help me in that case.

This is somewhat a duplicate of #208. If you don't want to create TileConfiguration.txt by hand, you could use  Image Stitching Plugin for Fiji to create it.

the origin is at the top-left corner, suppose the motor moves like this
↓  ↑→ ↓
↓  ↑  ↓
↓→ ↑  ↓

got pictures like below
000_000.jpg  001_002.jpg  002_000.jpg
000_001.jpg  001_001.jpg  002_001.jpg
000_002.jpg  001_000.jpg  002_002.jpg

(1-overlap_ratio)*height=h_offset is vertical expect offset
(1-overlap_ratio)*width=w_offset is horizontal expect offset
the TileConfiguration.txt should be like this
dim = 2
000_000.jpg;;(0, 0)
001_002.jpg;;(1*w_offset , 0)
002_000.jpg;;(2*w_offset , 0)
000_001.jpg;;(0, 1*h_offset )
001_001.jpg;;(1*w_offset, 1*h_offset )
002_001.jpg;;(2*w_offset, 1*h_offset )
000_002.jpg;;(0, 2*h_offset )
001_000.jpg;;(1*w_offset, 2*h_offset )
002_002.jpg;;(2*w_offset, 2*h_offset )

For 2D stitching, if you have the starting XY positions for the tiles, I think the following code should arrange them as needed for TileConfiguration.txt
x_positions = xy_positions[:,0]
y_positions = xy_positions[:,1]

sorted_indices = np.lexsort((x_positions, y_positions))
xy_positions_sorted = xy_positions.take(tuple(sorted_indices), axis=0)

Reopen the issue if there are further details.


Renderdoc leaks file descriptors

Description
Renderdoc opens a new pipe every few seconds but does not close it.  Eventually I get messages like this on the console:
Error   - Could not create AF_NETLINK socket (Too many open files)
Error   - Could not create stdout pipe
Error   - Could not create stderr pipe
This does not seem to be immediately fatal, but trying to start a process in this state will crash renderdoc as it can't open the pipes needed to communicate with the process.
The rate seems to be about one fd every 3.75 seconds, and the granularity is two fds at once, so most likely renderdoc tries to open one pipe (two fds) every 7.5 seconds.
Repro steps

Start renderdoc
Observe /proc/pidof qrenderdoc/fd and see the number of fds increasing
After some time, the fd limit will be reached and messages will be printed (this could take upwards of an hour with typical ulimit values)

Environment

Renderdoc v1.x 38f0d27 (self-compiled)
Debian unstable (mostly up-to-date)
RTX 2070
Nvidia driver 418.74

Thanks for the report! When opening pipes to communicate with a child process I wasn't properly closing the pipes if the process failed to run. adb is run intermittently to watch for android devices being connected or disconnected, and that was what was leaking here.


nuxt bug   Cannot read properties of undefined (reading 'sessionStorage')

nuxt bug   Cannot read properties of undefined (reading 'sessionStorage')

Please provide a proper reproduction.


Where are the animation options?

Is there a way to define animations? The only option in the docs seem to be transition timing.
I'm looking for ways of setting tween or easing.
I would like my charts to load like this:
http://gionkunz.github.io/chartist-js/examples.html#svg-path-animation
It may be nice default for C3.

@aendrew
Can you give me some input here? Thanks for the fast responses on my other issues.

Currently c3 does not have this kind of feature. Let me mark as enhancement at the moment.

Can this please be added now?
Maybe an animateFromZero option, since the animation itself is already coded and setting initial y values as 0 seems to be one (awkward) way to get animated builds.


[Syntax] Parse invalid characters as trivia

This PR update Lexer to parse invalid characters as trivia.
Invalid chars means here is invalid UTF-8 byte sequence and unicode code point which is invalid in Swift source.
They are just skipped in lexImpl before.
By this PR, libSyntax get perfect round trip with source code which has arbitrary binary even if it contains broken UTF-8 byte sequence.
This is my third retry for same purpose.
First is https://github.com/apple/swift/pull/14967.
Second is https://github.com/apple/swift/pull/14979.
In this time, I covered all considerations and retrieved review.
I rearranged concepts around here.
There are 2 kind of things.
First is unknown token.
There are some rules to lex unknown token in Lexer.
When hit these tokens in lexImpl, Lexer need to stop reading and position start of token.
Second is garbage text trivia.
They come from invalid byte sequences and unicode codepoint which is invalid in Swift source.
To detect both cases in lexTrivia,
I added some new case branches and I minimize them.
Specifically, to minimize,
case below are handled in advanceIfValidStartOfIdentifier in default branch.
case 'A': case 'B': case 'C': case 'D': case 'E': case 'F': case 'G':
case 'H': case 'I': case 'J': case 'K': case 'L': case 'M': case 'N':
case 'O': case 'P': case 'Q': case 'R': case 'S': case 'T': case 'U':
case 'V': case 'W': case 'X': case 'Y': case 'Z':
case 'a': case 'b': case 'c': case 'd': case 'e': case 'f': case 'g':
case 'h': case 'i': case 'j': case 'k': case 'l': case 'm': case 'n':
case 'o': case 'p': case 'q': case 'r': case 's': case 't': case 'u':
case 'v': case 'w': case 'x': case 'y': case 'z':
case '_':

case below are handled in advanceIfValidStartOfOperator in default branch too.
case '%': case '!': case '?':case '=':
case '-': case '+': case '*':
case '&': case '|': case '^': case '~': case '.':

First 4 commits does not change behavior of Lexer.
They are step by step refactoring to prepare new function.
Last commit implement lexing and adding test cases.
Please review this. @rintaro @harlanhaskins @nkcsgexi

I added some new case branches and I minimize them.

For performance reasons, I think we should handle both isValidIdentifierStartCodePoint and isOperatorStartCodePoint cases in switch in lexTrivia.
Since this switch is super-hot path, we want to avoid performance regressions at all costs.

Since this switch is super-hot path, we want to avoid performance regressions (especially in normal scenario) at all costs.
Ok, I expanded these character cases.

Updated.

Thanks!
@swift-ci Please smoke test

@nkcsgexi Please merge this if you are OK.

LGTM! 🚢

Thank you all 😄


IE11: onGridReady callback invoked when ag-grid is not so ready still.

Hi Niall,
I got a next issue:
In Chrome and FF the next code works fine:
private onGridReady: Function = () => {
    // resize the grid to fit the page
    this.gridOptions.api.sizeColumnsToFit();
...
}

But in IE11 I should to use delay like
this.$timeout(() => this.gridOptions.api.sizeColumnsToFit(), 500, true);

tested with ag-grid 4.2.5 and 4.2.7

In IE log you can find the next warning:
ag-Grid: tried to call sizeColumnsToFit() but the grid is coming back with zero width, maybe the grid is not visible yet on the screen?

that's exactly what it says - IE is reporting back the grid with zero width - if I cannot find out the width of the grid at this point, then cannot work out the width the columns need to be.

this seams fine to me:
this.$timeout(() => this.gridOptions.api.sizeColumnsToFit(), 500, true);
however i'd just do:

Dear Niall,
If setTimeout( ()=> this.gridOptions.api.sizeColumnsToFit(), 0 ); was working, I would prefer
this.$scope.$applyAsync(() => this.gridOptions.api.sizeColumnsToFit()); And that is what I've used till latest IE upgrade, but unfortunately the 0ms - 300ms time range is not enough to latest IE11 to make ag-grid ready to fit, so I use 500ms as workaround.
From other side, according to ag-grid documentation:

so as an ag-grid user I expect that grid is READY to be resized on that event ("gridReady")
:)

not really true - the grid IS ready - but the DOM is not - is there anything else in your app that is stopping the grid from been displayed? maybe it is in a tab that is not yet visible?

Agree - that is the reason I think the "gridReady" event need to be sync with DOM as well. Your grid is too quick for IE! :) The issue could be related to flex layout implementation in IE11...
And adding to the grid style min-height: 100px; min-width: 100px; fix that behavior too!

Yep. I agree with you. The grid shouldn't care of the parent size but it
may be useful to have an event when grid are rendered and have non zero
size.
Also, have you a plan to add "autofit" option for grid?

Thanks,
Dmitry
On Jun 30, 2016 8:27 PM, "Niall Crosby"<EMAIL_ADDRESS>wrote:

we are almost in agreement . . . . if there is something else in your app
that needs to be initialised, then you should listen for that instead of
listening to the grid onReady() event.
the grid onReady() event gets called when all the grids javascript
initialisation code has finished executing. it is not an indication as to
the readness of the browser or any other framework you might have.
if it was flex, then getting the grid to 'wait' would put a dependency of
flex into the grid which wouldn't be good!!!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ceolter/ag-grid/issues/997#issuecomment-229729746,
or mute the thread
https://github.com/notifications/unsubscribe/AHWKiPbiabmYbgfbW19zYtlW6qn9YBxUks5qQ_xtgaJpZM4JBB8U
.

Also, have you a plan to add "autofit" option for grid?
=> yes, it's on my long list. however it's not something someone who pays me is looking for, so it's not near the top of the list. something to consider when i have spare time.


Add a link to a zsh plugin for auto-refreshing the okta_aws

Signed-off-by: Irving Popovetsky<EMAIL_ADDRESS>

this is awesome, thanks for it!


Static pages styling

Since I have access/permissions to this repo now, I've move the branch from my forked repo to a normal branch in this repo, so it can be more visibly tracked.

LGTM just that one missing "the". Also, the 'completed puzzle' page doesn't get shown. other than that, this looks pretty nice!

Actually, I'm not sure how this is hooked up to work, I just assumed there's some logic in there, we should confirm with @portrain !

Looking uh-may-zing. Just a couple of comment to work though.


Swap OSM Geocoder for internal.

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

Comments from the review on Reviewable.io


refactor(build): make code more modern and idiomatic

Note: some of old code should show warnings when it's checked by clippy. However, currently running cargo clippy doesn't check build.rs file.

TODO

[x] Use cargo fmt
[ ] Add necessary tests
[ ] Add changelog entry
[ ] Update default config/theme in README (if applicable)
[ ] Update man page at lsd/doc/lsd.md (if applicable)

Codecov Report

Merging #719 (3cf315d) into master (31d3701) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #719   +/-   ##
=======================================
  Coverage   88.32%   88.32%
=======================================
  Files          41       41
  Lines        4505     4505
=======================================
  Hits         3979     3979
  Misses        526      526

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Appstudio update rhtap-demo-component-jnhd

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI has failed.There was an error creating the PipelineRun: rhtap-demo-component-jnhd-on-pull-request-
creating pipelinerun rhtap-demo-component-jnhd-on-pull-request- in namespace rhtap-demo-dev-wyws-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: rhtap-demo-component-jnhd-on-pull-request-
creating pipelinerun rhtap-demo-component-jnhd-on-pull-request- in namespace rhtap-demo-dev-rhxz-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: rhtap-demo-component-jnhd-on-pull-request-
creating pipelinerun rhtap-demo-component-jnhd-on-pull-request- in namespace rhtap-demo-dev-vkyt-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: rhtap-demo-component-jnhd-on-pull-request-
creating pipelinerun rhtap-demo-component-jnhd-on-pull-request- in namespace rhtap-demo-dev-midt-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: rhtap-demo-component-jnhd-on-pull-request-
creating pipelinerun rhtap-demo-component-jnhd-on-pull-request- in namespace rhtap-demo-dev-yseb-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request


mat-label overflows matSuffix content

Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
When a text is longer than the input field it overflows the matSuffix content (icons etc.):
Reproduction
<mat-form-field style="width:100px">
  <mat-label>Very very very very long text</mat-label>
  <input matInput />
  <span matSuffix>
    <mat-icon>cancel</mat-icon>
  </span>
</mat-form-field>

Expected Behavior
ellipsis are displayed when overflowing the matSuffix content.
Actual Behavior
The input field label overflows the matSuffix content (icons etc.):
Environment

Angular: 18.2.14
CDK/Material: 18.2.14
Browser(s): Chrome
Operating System (e.g. Windows, macOS, Ubuntu): Windows 11

Duplicate of #28743


[bug] When data cannot fit onto any sizes, a blank page is left behind

Fixed in 5908186e332cb56cfa3bdecfa0241e891e4afaab


Create release upon each build and standardize version numbers

Each push to a PR will create builds (as artifacts only) with the
version number of X.Y.Z and a stamp of gABCDEFA, where X.Y is the last
tag in the main repo of the form vX.Y, Z is the number of commits since
then, and ABCDEFA is the git hash of the tip of PR
Each push to main (icosa-gallery only) will create artifacts of the form
X.Y.Z (same meaning as above), as well as an easier to use 'pre-release'
release on the github releases page. It will also tag the commit with
X.Y.Z (no 'v') to make it easier to cross-reference.
Each push of a tag of the format vX.Y to main will create an official release named X.Y.0.
Both of these releases include the same 4 files; Windows + Oculus, regular +
Experimental. The other artifacts (Mac OS X, Linux, Windows Monoscopic)
remain available from the Artifacts page, but are not exposed on the
'releases' link.
All Oculus builds are signed, and the android-specific bundleVersionCode
is now updated automatically (1000000X+1000Y+Z) (this is also new here)
Creating a new formal release requires two steps:

Update the following three files, create a PR as usual, and merge it:

  Assets/Scenes/Main.unity:  m_VersionNumber: X.Y.0
  ProjectSettings/ProjectSettings.asset:  bundleVersion: X.Y.0
  README.md:## Current Version: `X.Y.0`

Tag the merge commit with vX.Y (do not include the .0), and push the
tag to trigger the actual build of X.Y.0.

FYI @andybak

Ignore the commit names, but you can see a sample pre-release at https://github.com/mikeage/open-brush-actions/releases/tag/0.2.12, a sample release at https://github.com/mikeage/open-brush-actions/releases/tag/0.3.0, and their jobs are https://github.com/mikeage/open-brush-actions/runs/2220637479?check_suite_focus=true and https://github.com/mikeage/open-brush-actions/runs/2220920088?check_suite_focus=true respectively

P.S., I know this looks a bit scary, and I won't lie... it is a bit scary, but I think we're getting to something that will last for quite a long time without needing any tweaks and will greatly simplify both beta testing and actual releases by removing a lot of manual steps, so I hope it's worth it :-)

The Oculus build from this PR:
$ apkparser -apk ~/Downloads/Android-Oculus/com.Icosa.OpenBrushgithub.apk | jq '.versionName'
"0.2.12-g7430d43"

Converting this to a draft for a few minutes; testing one more thing locally first. We should not be using -btb-github, I think, if it's a formal build -- those should have the same name and package name as the "official" builds, since I want them to become the official builds!

One more note; to get this to work, I pushed a new tag v0.2 to the same commit that has v0.2.0, to match the (new) convention. If we decide to refactor / reject this, I can delete v0.2

One open issue -- this doesn't (yet) support creating builds for hotfixes / maintenance releases. TBD, but not, I think, on this PR.

The updated format for the zip files for the release can be seen at this release: https://github.com/mikeage/open-brush-actions/releases/tag/0.4.2

Moving to draft while I check the addition of secrets for formal and pre-release (but not PR) builds


Plex Auth Issue

I read this https://github.com/Hellowlol/HTPC-Manager/issues/372 thread and the one linked in the first post and have gotten the following:
I know Plex Home requires entering the myPlex creds which i have entered and yet i still get this error:
Unable to contact Plex via http://<IP_ADDRESS>:32400 error HTTP Error 401: Unauthorized
I verified the values in the settings table and plex_username/plex_pass show the correct value which allows me to log into plex.tv, also the plex_authtoken field has a valid token and i can see the HTPCManager in my plex devices.
the log just states this
Unable to contact Plex via http://<IP_ADDRESS>:32400 error HTTP Error 401: Unauthorized
I manually deleted user/pass/authtoken from the db and after entering everything back in it started working, then after i restarted, failure again.
oh and hitting clear + save doesn't remove the values from the DB, not a big deal to me but figured you'd like to know.

I forgot to add my password does have * in it, not sure if that would also affect things

Thanks for reporting this, i don't understand why this does not work but ill see if i can recreate your issue and find a solution.


[Addition]: Please block these cheaters

Hotspot b58 Addresses
1137pAUKf71hRPJQXjGU9ndxaPeT5rsS9fnXFSYp664FgCVsspN
11zDCshkMCjcRPVVBA5AZeCsTytwo4qL733vhvD2qh1HAMunBmD
112pvQRT6dtB8CSVx9Mv3uSiSECw9LcyyAUxnyegHbzowv92s2Y
118Xejp24P2LSxyD3vAWzKmjrNR1yV3cHgHLmF7ArUqU85CwK2V
112m4g7CK531pMiq7zMtXf31QBmJpxHDzVnXHePyNCrqEp1badUj
11q22a5YDj82zYqzcQBASHqoE7nSouW2tsg49vAg6UwBigkF6yD
1121kptBA4pmXd3y1Zer9wiPbeb3SDKZghfed5x62BdqqkU1brHS
11sGkMmJZ1yx67rtktKjyweaatfUzg5D87R64pazoNksuML3GZU
11vEcEau6cPa5a1j4nujj4LLk8sDfcwr1yG4X2H464kMKWmxqS5
116bjhZskMeBhCqwismagxvi7c5DQcBYwfQcpHEwhvEvn6JpYvV
11CxX9rqMMDP6yyVQAU1apFdtrDoB5x2QgeRSnzzALjYwvP6Wr2
11UPi23F8ZN6cbz8v1a9Q96ZB8zicDdjrXRPiFn6RpvXttUvdg6
11czeL1rToCBu9MMWWveGS2f3orX8E9ZYN81pCPHuWhjXF7To3J
119DMEfp6T6ZBtX1eov1vnUSE8ZJhUcAeU1KH3F1c7o59j452Ps
112hL2SwV1zpfUnMibCJyvYKhvEMcnGV5bKoMiAq7a8u8QBJ7YUa
112CkJmEZ5yQZZWxWCQrvuaiAXL4N3QA2wsC8QAmdncLtBPQjCzZ
112XkcQfHAqikLj2Q8vuutNpn7JQf44agG6jmMkAUoPju2b1gcL9
Discord Handle
No response
Reason(s)
These machines belong to different countries and frequency bands, but they transfer money to each other, pass through the same wallet, and there is a remote witness. Some machines are located in the river, without antennas, and they are all cheaters!

.jpg…]()

Please close these cheaters!

My machine was not in the river, it was by the river
112HSBksagpT3vqqBhFZaUvcGNMgm8J94f4wPkjcum53PodSqiau

My machine was not in the river, it was by the river
112HSBksagpT3vqqBhFZaUvcGNMgm8J94f4wPkjcum53PodSqiau

Could you tell me how you have witnessed more than 1140km?


Help Page

Added a contact form where users can submit bug reports, or general inquiries.  It has been tested and is working properly


kubeadm: fix links in kubeadm-alpha page

fixes https://github.com/kubernetes/website/issues/15668
/assign @sftim
/sig cluster-lifecycle
/kind bug
/priority backlog

/retest

the preview CI is not running for some reason.

/lgtm

/LGTM
/approve


GRU replace fc7

I try to use GRUCell(step=2) replace fc7, but I only get 62.7% mAP, I try my best, but I can't get better mAP, Does anyone know how to train GRU?or Can someone can explain why fc7 is better than gru?

It depends on the usecase, a GRU is probably better at classifying time series than a fully connected layer. A GRU does introduce more trainable variables though, so it's harder to train.


extend=hourly chnaged?

Starting this morning, I haven't changed anything, but it's only retrieving 48 hours of forecast instead of 168.

Apologies for this! Same issue as #108, with the root cause being how my fallback proxy parsed the URL when my main AWS region went down. Fix has been deployed (despite AWS still not working), but let me know if the issue is still happeing


how to store and restore the current projection matrix ?

i want to get the current projection matrix and store it to a variable so that later i can reuse it ,
i can try this :
float * matrix;
GPU_PushMatrix();
matrix = GPU_GetProjection();
...
//here i want to set the projection matrix to "matrix"

how to do that ?
i mean i looking for an equivalent to "glLoadMatrixf(matrix);"

GPU_GetProjection() returns a pointer to the current projection matrix.  If SDL_gpu changes that matrix, it'll affect your pointer.  If you really want to store the matrix for later, copy it into your own 16-element float array.  GPU_MatrixCopy() will help.  To restore it, you can copy it back onto the result of GPU_GetProjection().  GPU_MatrixCopy() is a more generic equivalent to glLoadMatrix().  You might also look at GPU_LoadIdentity() and GPU_MultMatrix().
Most of the time, however, you are temporarily changing the matrix and want to reset it back to how it was before.  It might be cleaner and clearer if you use GPU_PushMatrix() to store the matrix, then GPU_PopMatrix() to restore it.  It works very similarly to glPushMatrix() and glPopMatrix().

thanks , im asking because  i have a problem mixing sdl_gpu camera with GPU_Translate() ill tell you in short what it is :
I am using sdl_gpu camera to navigate on the level's world and follow an object , but when i try to apply rotation on the camera , it appears that the rotaion center is not the screen's center point as expected but it is the top left cornner of the screen , one possible solution is to rotate first then translate ( as i did in allegro 5 ) , but that is impossible with sdl_gpu , because it handles the camera control at once using GPU_SetCamera() and it does it in it's one only own way .
i left the camera methods and i thought that i can use SDL_Translate() , it is working as expected with some exceptions :

when rotating : the shapes are scaled because the screen ratio is not 1:1
and something you peobably didn't know about , or didn't think of , the Blit functions  are not responding to the translation as the shapes does .
now i think i should leave the camera rotation thing all together
, and make my game without cool effects :/ or i thing i should use shaders for the rotation , or do you thing i can fix this whole problem with sdl gpu itself ?

This sounds like something that needs to be fixed, but I don't have the time right now to dig into it.  If you do look into it further, you can send a pull request or a patch and I'll take it in.

i think i will make some changes on sdl gpu for the engine im working on , ill back to this later when i need a camera rotation , whenever i add something or fix something ill let you know , im sure that  after few months ill have to back to work on the engine's guts and basics but for the moment i don't have to loose time i prefer to move on


Client should gracefully handle connection resets

When a server due to inactivity closes its connection, a socket error is raised when the client tries to use the connection - this is expected behaviour, however the crate client removes the given server from its active server lists as if it was down, which is wrong. This leads to no remaining servers exceptions if only one server is used in the connection. In conjunction with #302 this leads to sporadic exceptions which could be handled gracefully on the http level.
example traceback:
Traceback (most recent call last):
File "/usr/local/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1193, in _execute_context
data_sent += socket.send(chunk, flags)
File "/usr/local/lib/python3.6/site-packages/gevent/_socket3.py", line 440, in send
return _socket.socket.send(self._sock, data, flags)
urllib3.exceptions.ProtocolError: ('Connection aborted.', ConnectionResetError(104, 'Connection reset by peer'))

@dobe Released with 0.22.1. Thanks


Test item range is wrong when workspace edit is applied

Does this issue occur when all extensions are disabled?: Yes/No

Version: 1.66.1 (user setup)
Commit: 8dfae7a5cd50421d10cd99cb873990460525a898
Date: 2022-04-06T14:50:12.141Z
Electron: 17.2.0
Chromium: 98.0.4758.109
Node.js: 16.13.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22000
Steps to Reproduce:

Clone the repository: https://github.com/jdneo/test-api-issue.
Setup the extension and launch it.
Open test.txt
Trigger command Hello World, which will apply a workspace edit.
One test item disappear and the range is different from that set via api.

https://user-images.githubusercontent.com/6193897/162564176-84c73b2e-ef0a-4031-8000-eb67878ac57d.mp4
Note: From my observation, this error relates with how many lines between the 'parent' and 'child' item. When the lines added by the workspace edit is the same as the lines between the parent and child, then this will happen. If they are different, then everything works fine:
https://user-images.githubusercontent.com/6193897/162564220-bbcd9564-5b6d-445f-a6f9-c1b56d4c2ea7.mp4

Fixed this in https://github.com/microsoft/vscode/pull/161446

Confirmed that it is fixed in
Version: 1.72.2 (user setup)
Commit: d045a5eda657f4d7b676dedbfa7aab8207f8a075
Date: 2022-10-12T22:15:18.074Z
Electron: 19.0.17
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19044
Sandboxed: No


Catalog end-points

Summary
This PR pretends to enable catalog end-points for our integration in IQP. For this integration we are creating two new end-points:

/api/v1/catalog: that returns all the public qiskit functions
/api/v1/catalog/:id: that returns a specific public qiskit functions

Details about the implementation

What is a "Public Qiskit Function"?

Basically a Public Qiskit Function it's a Qiskit Function that everyone should have access to view (but not run specifically), even not authenticated users.
For this we synced that all Qiskit Functions with the group "ibm-q/open/main" will be considered Public Qiskit Functions.
Due to this there some considerations to take into account:

These end-points are public, so no-authenticated users are able to call to them too.
There are 4 new fields:

serializer only available: it will say to the catalog if the user (if exists in the request) has access or not
type: it will identify the type of the function: Generic, Application or Circuit.
icon_ulr, documentation_url are basically fields that will contain URLs specific for the function
additional_info: contains a JSON structure with information for the catalog. Happy to discuss this approach, the decision behind it was that if the front-end requires a change we could easily change it without a new release or any change in the model.

We didn't introduce yet how to populate these fields. The idea is try to have for the next week the admin panel and populate the info there.

For the rest of the things there are no more news: this PR introduces a new view, serializers, tests and swagger documentation for the new end-points.

These end-points are public, so no-authenticated users are able to call to them too.

Do we anticipate endusers calling these APIs, or are they solely for the catalog? If it's the latter, we should probably restrict their usage somehow (either authentication or network policy restrictions or ...)

Do we anticipate endusers calling these APIs, or are they solely for the catalog? If it's the latter, we should probably restrict their usage somehow (either authentication or network policy restrictions or ...)

Initially they are only designed for the catalog. There is a use case where a non-authenticated user in IQP could enter in the catalog page and it should be able to check the different public functions (in this case availability is set to False automatically).
I don't see probably the authentication but network policy restriction can have a lot of sense to be honest. We could take a look later, agree.

Thanks @akihikokuroda , I'm just validating the format of the response before merge it and I'm almost have everything for the admin panel.

It seems everything looks so I'm going to merge to move forward with the admin-panel 👍


preg_quote

https://github.com/baryshev/TreeRoute/blob/master/src/Router.php#L27 should be preg_quote not addclashes.

No, we need to escape only delimiter here. If we change addclashes to preg_quote , the route /news/{id:[0-9]+} will be match exact /news/[0-9]+ url, but we except all urls like /news/123.


Link to default.yaml wrong in README.md

The custom configuration section links to config_template.yaml which no longer exists. I am guessing this has become default.yaml?

Yes updated now.


move process utilities from jupyterlab to jupyterlab_launcher

Though strictly speaking this PR only add functionality to the jupyterlab_launcher package, it's easier to think of it as a major change for the downstream dependency in jupyterlab,. /cc @jasongrout

Since it is a bit of a pain to do major releases of jupyterlab_launcher, I think I'd rather still call this 0.10.6 (which it technically should be) and just make jupyterlab depend on something 0.10.6 or later.


Dealing with multimedia

How does multicodec deal with multimedia?
Consider mp4 files or mts files. They are container formats. Within each there are choices of audio and video codecs that can be used.
It seems multicodec simply identifying the container format is not powerful enough to describe such files with composite codecs.

The container format internally records the chosen codecs. Multicodec is enough to remove the initial ambiguity and let us decode the container.

Has anybody started recording all the multimedia formats into multicodec?
On 14/04/2020 7:11 am, Steven Allen wrote:

The container format internally records the chosen codecs. Multicodec
is enough to remove the initial ambiguity and let us decode the container.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/multiformats/multicodec/issues/168#issuecomment-613100179,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAE4OHJLBUMGNGTKGRZLRGTRMN5ZNANCNFSM4MG7QW7A.

https://github.com/multiformats/multicodec/pull/159

(please close this issue if you considered answered @CMCDragonkai )

That PR hasn't been merged yet!

That PR is tracked in #4.

Tracking in #4.


Pressing the keybinds to hide Monika will make her say our default name ("User" in my case)

When pressing Ctrl+Shift+F11, she'll say, "See you later User." Even after changing name.

var expression =                                    new Expression(                                         "Okay, see you later " + Environment.UserName +                                         "! (Press again for me to return)", "b");
paging Pi for this bug.

Fixed.


"to Top Button" design

As mentioned on the channel by @smaranjitghose I'd like to work on improving the "to top button" design and position.

Is there any design you'd like for me to implement here? Also, where do you want it to be positioned?

Is there any design you'd like for me to implement here? Also, where do you want it to be positioned?

Sure you can try a new design. Well, the issue is not with the horizontal position on the webpage but with the vertical position on the web page till which it appears. For example for the Home Page, we actually do not require it


Add TIP4P-EW

Resolves #73
Based on https://github.com/openmm/openmm/blob/116aed3927066b0a53eba929110d73f3dafb64bd/wrappers/python/openmm/app/data/tip4pew.xml

Codecov Report

Merging #76 (3692ce6) into main (19d29a8) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

Thanks!


Rat crashed during execution of PowerView commands

I'm running into an issue where the Rat crashes during the execution of PowerView commands:
"function": "execute",
        "parameters": {
          "command_line": "powershell -command -",
          "stdin": "[[powerview]] Get-DomainComputer"
        }
      },
      "error": "Rat crashed during execution"
    },
    "create_time": "2018-11-29T01:19:36.725Z",
    "status": "failed"

From the command line, I'm also noticing the following output:
WARNING: The rat started as a local user. In order to function properly, Caldera requires domain users. Please verify that the starting rat is operating under a Domain Account if full functionality is desired.

For reference, I'm running CALDERA under the following architecture:

CALDERA Server: Ubuntu 16.04.5. LTS using Docker-CE + Docker Compose
CALDERA Agents: Windows 7 SP1 Enterprise x64

I've made sure to setup docker-compose.yaml to include the following advanced configuration:
args: “crater=https://github.com/mitre/caldera-crater/releases/download/v0.1.0/CraterMain7.exe”

I've essentially followed the documentation verbatim. I don't seem to have any issues when running tasks that involve native Windows commands.
Any thoughts on what might be causing this issue? I'm happy to provide more information to help troubleshoot and improve this project's documentation.
Thanks!

This appears to have been encountered while using an older variant of Caldera. If the issue persists when upgrading to the most recent version, feel free to re-open this issue, and we'll try to help debug the root cause and potential solutions further.


Variables are not reflected in stack export

when adding variables, i am able to see those variables in the terraform export variables.tf.
However, they are not reported in the variables.tf  script when exported to  Resources Manager.

Fixed in 0.44.0 Release


feat(designer): Added Node Copy/Paste Functionality

Feature Request - https://github.com/Azure/LogicAppsUX/discussions/3310

There is a todo of preventing the paste of a copied node where the node dependencies are invalid

How do scope nodes deal with copy / paste?  Do we include all contained nodes when pasting or does it paste empty?

How do scope nodes deal with copy / paste? Do we include all contained nodes when pasting or does it paste empty?

currently, we don't handle any scope nodes, I only added the copy functionality on operation card nodes, as I felt like doing the subgraph stuff might need to be much more extensive


Generate additional dark themes

I hacked together a script to generate these templates programmatically. I'll need to do some manual QA and I am quite sure that my methodology here could be improved but I hacked this taken in an hour or so, hopefully its helpful.
The end result looks pretty close to my eye, however a more keen observer will likely find some discrepancies between the canonical theme and these generated ones.
To further improve this, I could use the same methodology to generate an real template that is able to take the values from lua and map them directly into the vscode theme (without using the gsub hack). This would also highlight places where colors may not match 1:1 between the nvim theme an vscode theme which the gsub method I used would miss entirely.
Methodology
Basically I took all of the colors that are defined for each of the themes from https://github.com/EdenEast/nightfox.nvim/tree/main/lua/nightfox/precompiled/nvim and using nightfox-dark-theme.json I was able to take all of the colors defined in nightfox_compiled.lua and substitute them for colors in other themes. This approach gave me a new *-dark-theme.json that could be used in vscode. It looks like there were a few colors missed for the light theme, most notably the search bar background was still dark, so I'll need to go over those more carefully.
This was the ruby script I hacked together to do the substitution, this was a quick hackjob so there's probably a better way to automate this but I'll post it here for posterity for those interested.
template_theme = { :name => "nightfox", :type => "dark" }

themes = [
  { :name => "dawnfox", :type => "light" },
  { :name => "dayfox", :type => "light" },
  { :name => "duskfox", :type => "dark" },
  { :name => "nightfox", :type => "dark" },
  { :name => "nordfox", :type => "dark" },
  { :name => "terafox", :type => "dark" },
  { :name => "carbonfox", :type => "dark" },
]

def compiled_theme_filename(theme)
  "#{theme[:name]}_compiled.lua"
end

def extract_colors(theme)
  filename = compiled_theme_filename(theme)
  data = File.read(filename)
  return data.scan(/"(#.*?)"/).flatten
end

def template_filename(theme)
  "#{theme[:name]}-#{theme[:type]}-theme.json"
end

themes.each do |theme|
  template_colors = extract_colors(template_theme)
  theme_colors = extract_colors(theme)

  from_filename = template_filename(template_theme)
  to_filename = template_filename(theme)

  data = File.read(from_filename)

  template_colors.each_with_index do |from_color, idx|
    to_color = theme_colors[idx]

    data = data.gsub(from_color, to_color)
  end

  File.open("./themes/#{to_filename}", 'w') { |file| file.write(data) }
end

@keifererikson any update on this?

I've been dying to have terrafox ported over because I recently switched off of nvim and that was my favorite theme.

Any update?

@keifererikson would you merge this PR? I'm keen to have all the *fox themes available for VS Code

🔥 🔥

My favorite theme is back from the dead 🥺


chore: add and ignore ip.txt in ios

Description
This one have been making me crazy since day 1: I never was able to run the app on ios simulator without hardcoding my IP in AppDelegate.m like this:
- jsCodeLocation = [[RCTBundleURLProvider jsBundleURLForBundleRoot:@ sharedSettings] "index.ios" fallbackResource:nil];
+ jsCodeLocation = [NSURL URLWithString:@"http://<IP_ADDRESS>:8081/index.ios.bundle"];

I discovered today that you can provide a file named ip.txt in Xcode and put the IP there instead:
https://github.com/facebook/react-native/blob/master/React/Base/RCTBundleURLProvider.m#L86
This PR add this empty file to Xcode and to gitignore at the same time, so you are free to put any IP there if needed.
I still need someone with a working setup without hardening the IP to give this a go.
 I can run the app easily on my iPhone 6Plus. I just need:

clone the repo and open by Xcode 9.2
change the bundle identifier and select my personal sign, as well as RN tutorial says
build and run

change the bundle identifier and select my personal sign, as well as RN tutorial says

can you give me a link to read? also, won't changing the bundle id generate modifications that shouldn't be commited?

Sorry, the tutorial is not an official document and is written by Chinese. And yes, don't commit these modifications. I also left some messages for you in Gitter. Hope you can find the root reason.

@chinesedfan I tried a lot of things over the past few days, the only thing that allows me to have a clean working copy (nothing to avoid commiting) is this PR.
Any blockers on your side to merge this in?

@machour I am not sure. Because I didn't face this problem.
@gitpoint/maintainers What about you guys think?

@chinesedfan, I meant, if you apply this PR locally and try to run the project as you usually do, does it still work for you?

@machour No problem. I can both work normally.

Really magic localhost for @machour. Following links are able to be visited when running the simulator,

http://<IP_ADDRESS>/status
http://<IP_ADDRESS>/status
http://mbp.local:8081/status

Except this,

http://localhost:8081/status

Let me merge it to save him. And revert in one day we found the real reason.

Thank you!!!! 😭 ❤