cephadm_custom_repos: true prevents installation of Reef on Ubuntu 22.04

Turns out setting 'cephadm_custom_repos' as true installs quincy... the default version on Ubuntu 22.04! But this causes the playbook to ignore cephadm_ceph_release:
cephadm_ceph_release: "reef"
cephadm_custom_repos: true  # Should be enabled for Ubuntu 22.04

Results in:
root@storage-13-09002:/# ceph version
ceph version 17.2.7 (b12291d110049b2f35e32e0de30d70e9a4c060d2) quincy (stable)

On this page we're told "If using Ubuntu 22.04 this should be set to true." for cephadm_custom_repos: https://github.com/stackhpc/ansible-collection-cephadm/blob/083dcea047f477d7a44da40c34d7c216b1026a44/roles/cephadm/README.md
But why is that? Is there any problem with using the custom repos for Ubuntu 22.04?

I believe cephadm_custom_repos variable existed before Reef was released. The problem at that time was that Quincy packages were not available for Jammy, as a workaround Focal packages could have been used and it worked just fine. There is the same situation right now with Noble vs. Jammy.

Turns out setting 'cephadm_custom_repos' as true installs quincy... the default version on Ubuntu 22.04! But this causes the playbook to ignore cephadm_ceph_release:

The variable does precisely that, if set - overrides the official repositories to arbitrary ones, so it's possible to mix & match distros & Ceph releases and ignore the contents of cephadm_ceph_release. I'll try to correct the docs to emphasise that.
Note that the above applies just for the cephadm package installation, it's still possible to have e.g. Quincy's cephadm installed but the actual version of Ceph in the containers set to Reef. This is not recommended though.


feat: Add externalParameters.source for v1 specs for BYOB

closes https://github.com/slsa-framework/slsa-github-generator/issues/2186

We had a discussion about adding an identifier for the source repo to the annotations field in resolvedDependencies? What do you think about that idea?

We had a discussion about adding an identifier for the source repo to the annotations field in resolvedDependencies?

I think if we do, it'd be great to have a universal annotation that's agreed upon between multiple builders, so that parsing the arbitrary object can be shared logic.
Since annotations are maps of strings to objects, maybe it can be usage: <some-source-type-uri>?

I think if we do, it'd be great to have a universal annotation that's agreed upon between multiple builders, so that parsing the arbitrary object can be shared logic.

Yeah, I agree. It should probably get into the https://github.com/slsa-framework/github-actions-buildtypes repo at the very least.

Since annotations are maps of strings to objects, maybe it can be usage: <some-source-type-uri>?

For reference, Kubernetes has a similar type of annotations (though string: string) and they use URIs in the keys with "official" annotations starting with using a kubernetes.io domain.
https://kubernetes.io/docs/reference/labels-annotations-taints/

Maybe SLSA needs a few of these well known annotations.

I'm curious what's the point of these annotation in practice. iiuc, the verification is only required to look at externalParameters.source, and anything in material is to do recursive verification of dependencies...

There is WIP for specs to resolve this, so closing for now


Proper descriptions / cleanup?

Hi,
first thank you so much for maintaining this, much appreciated.
My question though: could you please clean up the cheats and possibly add better descriptions?
I don't understand why there's Jump codes with #7, 8, 9 and 10 - and what they do or how they differ, if at all. I found #7 to support 1.0.0 and 1.1.0 while 8, 9 and 10 only cover one version each.
Also, why are the Item multiplier cheats spread accross #6, 7, 8 and 9, and why is one version marked with a star?
Thank you :)

I was wondering the same things, I pretty much just went and looked at the modified date on the folders and used the most recent modified one because I had no idea what each folder was for or how they are different.

Hi, the emulator support is just because I can do it -- I don't support it though, it's generated off of the Switch version of the cheats.
There are multiple versions of said cheats because they do the "same" thing with just a different multiplier, i.e one does 2 times, 4 times, 10 times, etc etc -- to give player different options instead of saying, hey can you make it do 10x instead of 2x.
The star beside the cheat is "preferred/suggested" as in that's the option I would suggest using, as in that's what I would use.


correct the typos: Availalble -> Available, you -> your

What's the issue?

There are typos in README.md

Definition of Done

correct the typos: Availalble -> Available, you -> your

I'll provide, thank you

Thanks!

The PR was merged.


Fix Portal user info sample

Description
This PR is to fix OAuth window dismiss functionality in Portal user info sample. The window can be closed now and a button is added to authenticate portal to retry login after closing
Type of change

[x] Bug fix
[ ] New sample implementation
[ ] Sample viewer enhancement
[ ] Other enhancement

Platforms tested on:

[x] Windows
[x] Android
[ ] Linux
[ ] macOS
[ ] iOS

Done changes as per suggestions. By closed I meant about dismissing login window. Updated the name accordingly


Move source-build-reference-packages tooling into the repo

There is some external tooling to generate the projects that we put into source-build-reference-packages (IL, text-only, and GenAPI-based). These tools should be put in the repo itself for better maintainability.

I believe this was fixed with https://github.com/dotnet/source-build-reference-packages/pull/294 ?
Also, this issue seems like a duplicate of https://github.com/dotnet/source-build/issues/2609 ?

The one piece of tooling that was not ported is the IL source generator used to generate the targeting packs.  This issue should either be repurposed for that or a new issue should be opened.

Opened https://github.com/dotnet/source-build/issues/3091 to move the targeting pack tooling.


composer

Can you add composer to your json database?
It will be much more practical.
https://getcomposer.org/

I don't really like composer. It's just one more thing to manage. just git clone url jsondatabase instead. it's simpler IMO.

In 2018, do not use composer is a big drag ...
If I want create a project whith composer, in readme, I write :

#installation :
composer install my/app
and
git clone jsondatabase
?
It’s not a good solution

Alright I made the composer package and added a license. Make sure to git pull any changes to current projects.

Make sure to git pull any changes to current projects.

Compose update automatically,
 The requested package mitchellurgero/jsondatabase master is satisfiable by mitchellurgero/j sondatabase[dev-master] but these conflict with your requirements or minimum-stability.
JSONDatabase dosen’t work in php 7.2.4 ?

It should, I might have did the regex wrong for PHP required versions, it works with 56.+ and 7.0+

Try now I just removed the PHP dependency until I better understand composer regeex.


Rework assistant usage to match newly defined business rules

A usage sentence is already present (initialy coded by @lasryaric ) but the definition of what product wants as 'usage' has been clarified, and may thus differ with the existant
This task consists in updating what's been coded to match the new business logic, described below (see the related framing for all context)
The Activity Sentence
When we want to explain how much an assistant is used, we use the activity sentence:
"This assistant is active for X members, has sent Y messages in the last 30 days."

Active for X members means that is in the my assistant list of X members. If it's a shared assistant it means how many people have added it to there list. If it's a company assistant, it means all the members.
Messages is the number of posted messages by the assistant (not number of threads)

@philipperolet I think there is an updated version of it:
X: Number of workspace members having the assistant in their My assistant list. If it's a shared assistant it means how many people have added it to there list. If it's a company assistant, it means all the members.
Y: Number of posted messages by the assistant (not number of threads)
Z: Members having mentioned the assistant in the last 30 days

The Activity Sentence
When we want to explain how much an assistant is used, we use the activity sentence:
"@xxx is active for X members and has been used Y times by Z members in the last 30 days."

X: Number of workspace members having the assistant in their My assistant list. If it's a shared assistant it means how many people have added it to there list. If it's a company assistant, it means all the members.
Y: Number of posted messages by the assistant (not number of threads)
Z: Members having mentioned the assistant in the last 30 days

The Assistant Details phrase, a bit different, is not affected by this change


Delete method not allowed on indicators

Story
Trying to delete an indicator as a ProgramAdmin returns the following response:
{     "detail": "Method \"DELETE\" not allowed." }
Acceptance criteria
GIVEN I am ProgramAdmin
AND I try to send a delete request for an indicator in my program
THEN the indicator should be deleted with 204 no content response back

It happens only with generated data, not with new data.

We find out that this is data related issue


[Bug]: Example04_Dynamic_GroupChat_Coding_Task doesn't run code

Describe the bug
Actual behaviour:
The runner agent never gets actioned.
Steps to reproduce
Run Example04_Dynamic_GroupChat_Coding_Task
Model Used
OpenAI GPT3.5
Expected Behavior
When running the dotnet example Example04_Dynamic_GroupChat_Coding_Task the runner agent run the code provided by the coder agent.
Screenshots and logs

> TextMessage from admin
> --------------------
> ```task
> {
>     "to": "coder",
>     "task": "Write a .NET code to retrieve the most recent pull request from mlnet and save it in result.txt",
>     "context": ""
> }
> ```
> --------------------
>
> from: coder
> ```csharp
> var httpClient = new HttpClient();
> httpClient.DefaultRequestHeaders.Add("User-Agent", "C# HttpClient");
>
> var response = await httpClient.GetAsync("https://api.github.com/repos/dotnet/machinelearning/pulls");
> response.EnsureSuccessStatusCode();
>
> var content = await response.Content.ReadAsStringAsync();
> var pullRequests = JsonSerializer.Deserialize<List<Dictionary<string, object>>>(content);
>
> var mostRecentPR = pullRequests.FirstOrDefault();
> if (mostRecentPR != null)
> {
>     var prTitle = mostRecentPR["title"];
>     var prUrl = mostRecentPR["html_url"];
>
>     await File.WriteAllTextAsync("result.txt", $"Title: {prTitle}\nURL: {prUrl}");
>     Console.WriteLine("Most recent pull request saved in result.txt");
> }
> else
> {
>     Console.WriteLine("No pull requests found.");
> }
> ```
> from: reviewer
> ```review
> comment: The code satisfies all conditions.
> result: APPROVED
> ```
> TextMessage from admin
> --------------------
> ```summary
> {
>     "problem": "Retrieve the most recent pr from mlnet and save it in result.txt",
>     "steps": [
>         {
>             "step": "Write a .NET code to retrieve the most recent pull request from mlnet and save it in result.txt",
>             "result": "Code has been approved and successfully saves the most recent pull request in result.txt"
>         }
>     ]
> }
> ```
> --------------------
>
> TextMessage from user
> --------------------
> [GROUPCHAT_TERMINATE]
> --------------------

Additional Information

dotnet
OS: Windows
latest code in dotnet branch

@sebandres Can you try this example with gpt-4 and see if the error gone?

Hi @LittleLittleCloud, it worked with gpt-4.
I noticed with 3.5 that it also fails on the admin side towards the end once the task is done. These issues seem to be more related to the prompt engineering side rather than the code itself.
Given the LLM chosen impacts the outcome, I wonder if there is a way to abstract the prompt engineering from the framework (rather than just the LLM engine) in order for these to be swapped more seamlessly as each LLM requires different prompt structuring in order to obtain the same expected result reliably (for example, with Claude you might make heavy use of tags to instruct the LLM to focus on different areas of the prompt).


[FEATURE] Parallel testing

Set up unittest to be run in parallel.

Merged https://github.com/credmark/credmark-models-py/pull/157


lib/container: Use "encapsulate" terminology for module names too

Previously in https://github.com/ostreedev/ostree-rs-ext/pull/113
we changed the CLI entrypoints with this rationale:

Since we're moving towards more "native" support for container
images, we need to very clearly differentiate between the code
that currently uses the terms "import" and "export" which are
somewhat ambiguous.

To elaborate, the term "import" is ambiguous with respect to our
container "store" path, which generates a new ostree commit and
operates on arbitrary container images.
Let's take the next step now and rename the modules too.

(rebased :surfer: )


Support Running NPM Scripts

It would be convenient to have a shorthand for npm run my-script, like concurrently has:

concurrently "npm:watch-js" "npm:watch-css" "npm:watch-node"

I think the npm:script syntax is good as-is.
concurrently also supports wild cards and negations. matcher could be used for this.

This should also support resolving pre-  and post- scripts.

If the task is unnamed, the name should come from the script:
> listr yarn:lint tests::pnpm:test 'npm:build-*'
⠼ lint
◼ tests
◼ build-ts
◼ build-scss

The documentation should also mention quoting globs to escape them.

concurrently references: expand-npm-shortcut, expand-npm-wildcard

Potential matcher blocker: https://github.com/sindresorhus/matcher/issues/35


Adding Search

I would like to be able to search the documentation on the site.

I would really love that feature too.

I'll paste what I has as a local message -
"
M
i'm just thinking about adding a search to the upcoming xxx-docs docusaurus. unfortunately the easiest way is a free third party service called algolia. from a privacy perspective this seems suspicious.
have you decided consciously not to include search in the polkadot-js docs for this reason?
"
"
Jaco
Yes.
However, there is a local-only option https://github.com/daldridge/docusaurus-plugin-lunr
And this one, https://github.com/lelouch77/docusaurus-lunr-search
Now sure which is which and how any of it works. But that won't happen anytime soon.
But, there may be server-less options.
"
PRs for anything local-only welcome as a test.

@jacogr isn't the text search as mentioned here useful?

The above looks like docsify, not docusaurus.

I would really love that feature too.

Hey guys, I am integrating algolia's docsearch into this site.

Closing, we have it in after https://github.com/polkadot-js/docs/pull/310 (Thanks to @SaltyCucumber)


Can not generate svg sprite?

I used this plugin to generate svg sprite when it appeared, the following question. Some values can not be generated and become NaN. I can not find what is the reason, can you solve this problem?
<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
    <defs>
        <symbol id="icon-loading-7726d"></symbol>
        <symbol id="icon-error-b67ed"></symbol>
        <symbol id="icon-logo-b2031"></symbol>
        <symbol id="icon-chat-e3544"></symbol>
        <symbol id="icon-check-circle-o-71bb6"></symbol>
        <symbol id="icon-check-circle-25051"></symbol>
    </defs>
    <view id="view-icon-loading-7726d" viewBox="0 0 NaN 50"></view>
    <view id="view-icon-error-b67ed" viewBox="NaN 0 NaN 50"></view>
    <view id="view-icon-logo-b2031" viewBox="NaN 0 NaN 50"></view>
    <view id="view-icon-chat-e3544" viewBox="NaN 0 NaN 50"></view>
    <view id="view-icon-check-circle-o-71bb6" viewBox="NaN 0 NaN 50"></view>
    <view id="view-icon-check-circle-25051" viewBox="NaN 0 NaN 50"></view>
    <use id="icon-loading-7726d" xlink:href="#icon-loading-7726d" width="NaN" height="50" x="0" y="0"></use>
    <use id="icon-error-b67ed" xlink:href="#icon-error-b67ed" width="NaN" height="50" x="NaN" y="0"></use>
    <use id="icon-logo-b2031" xlink:href="#icon-logo-b2031" width="NaN" height="50" x="NaN" y="0"></use>
    <use id="icon-chat-e3544" xlink:href="#icon-chat-e3544" width="NaN" height="50" x="NaN" y="0"></use>
    <use id="icon-check-circle-o-71bb6" xlink:href="#icon-check-circle-o-71bb6" width="NaN" height="50" x="NaN" y="0"></use>
    <use id="icon-check-circle-25051" xlink:href="#icon-check-circle-25051" width="NaN" height="50" x="NaN" y="0"></use>
</svg>

I'm seeing the same issue.
I load svg from scss file, and the exported sprite.svg contains viewboxes with "NaN" and "50", even though each sprite has a viewbox of "0 0 16 16".

I am facing same issue, at many places in generated sprite viewboxes contains "NAN" through all svg icons are properly defined.

Can you guys let me know which version of this loader / plugin you are using and can you share one of those SVGs with this problem? There was a similar problem before which was recently fixed.

I'm closing this due to inactivity, feel free to reopen.


How to use RDLC in .Net core 2.0 to export report.

Before you open an issue
If the issue is:

A simple typo or similar correction, you can submit a PR. See the contributor guide for instructions.
A general support question, consider asking on a support forum site.
A site design concern, create an issue at MicrosoftDocs/feedback.
A problem completing a tutorial, compare your code with the completed sample.
A duplicate of an open or closed issue, leave a comment on that issue.

Issue description
<include description here>
Target framework
Check the .NET target framework(s) being used, and include the version number(s).

[x] .NET Core
[ ] .NET Framework
[ ] .NET Standard

If using the .NET Core SDK, include dotnet --info output. If using .NET Framework without the .NET Core SDK, include info from Visual Studio's Help > About Microsoft Visual Studio dialog.

dotnet --info output or About VS info
<replace>

Thanks for the new topic suggestion, @pappukr. We've added it to our backlog, as well as to our community contributor's project.

Actually, I'm closing this one as a duplicate of #9607.


change the mode of tee file to rw-rw-r after creation

to solve issue #73 , change the permission so the other users can also edit the file tmpdir/magnitude.install

As described in the doc, they use GitLab for code maintenance and PR https://gitlab.com/Plasticity/magnitude.


The dataset is currently empty. Upload or create new data files. Then, you will be able to explore them in the Dataset Viewer.

Describe the bug
https://huggingface.co/datasets/Muennighoff/xP3x
This dataset can be loaded & works just fine, however, the hub displays: The dataset is currently empty. Upload or create new data files. Then, you will be able to explore them in the Dataset Viewer.
Not sure if this is a datasets or hub bug
Steps to reproduce the bug
Go to https://huggingface.co/datasets/Muennighoff/xP3x
Expected behavior
Should show preview
Environment info
Chrome

Thanks for reporting.
This is an issue with the datasets viewer. I'm transferring the issue to the corresponding repo: https://github.com/huggingface/datasets-server


Move 'tests/contrib/operators/test_dataproc_operator_system_helper.py' to core

The file is already in tests.providers.google.cloud.operators


bug: the CI has failed

See: https://github.com/casbin/casbin-website-v2/runs/6842708416?check_suite_focus=true

@EmperorYP7

On it

Already fixed by: https://github.com/casbin/casbin-website-v2/commits/master


breaking: switch to JDK17 for agent processes

Related to https://github.com/jenkins-infra/helpdesk/issues/3072, this PR switches the agents to JDK17.
Please note that is a breaking change!

Merging as the only failure is the updatecli check


New release of gl_generator?

Hi @brendanzab could there be a new release of gl_generator that generates code with presence of the dyn keyword? Prefferably a new major release as it increases the MSRV of the generated code.

Thanks for the ping! ❤
Doing it right now.

Done! Published - should be on crates.io now.


Use NonNull in ReleasePool and add bench_dict

1st step to #271

@konstin
Travis fails with
running 5 tests
test binary_arithmetic ... ok
test inplace_operations ... FAILED
test rich_comparisons ... ok
test rich_comparisons_python_3_type_error ... ok
test unary_arithmetic ... ok
failures:
---- inplace_operations stdout ----
thread 'inplace_operations' panicked at 'attempt to subtract with overflow', tests/test_arithmetics.rs:76:9
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
stack backtrace:
   0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
             at libstd/sys/unix/backtrace/tracing/gcc_s.rs:49
   1: std::sys_common::backtrace::_print
             at libstd/sys_common/backtrace.rs:71
   2: std::panicking::default_hook::{{closure}}
             at libstd/sys_common/backtrace.rs:59
             at libstd/panicking.rs:211
   3: std::panicking::default_hook
             at libstd/panicking.rs:221
   4: std::panicking::rust_panic_with_hook
             at libstd/panicking.rs:476
   5: std::panicking::continue_panic_fmt
             at libstd/panicking.rs:390
   6: rust_begin_unwind
             at libstd/panicking.rs:325
   7: core::panicking::panic_fmt
             at libcore/panicking.rs:77
   8: core::panicking::panic
             at libcore/panicking.rs:52
   9: <test_arithmetics::InPlaceOperations as pyo3::class::number::PyNumberProtocol<'p>>::__isub__
             at tests/test_arithmetics.rs:76
  10: <T as pyo3::class::number::PyNumberISubProtocolImpl>::nb_inplace_subtract::wrap
             at ./src/class/macros.rs:153
  11: PyNumber_InPlaceSubtract
             at Objects/abstract.c:1054
             at Objects/abstract.c:1068
             at Objects/abstract.c:1087
  12: _PyEval_EvalFrameDefault
             at Python/ceval.c:1491
  13: _PyEval_EvalCodeWithName
             at Python/ceval.c:3971
  14: PyEval_EvalCodeEx
             at Python/ceval.c:4000
  15: PyEval_EvalCode
             at Python/ceval.c:522
  16: PyRun_StringFlags
             at Python/pythonrun.c:1035
             at Python/pythonrun.c:959
  17: pyo3::python::Python::run_code
             at src/python.rs:197
  18: pyo3::python::Python::run
             at src/python.rs:168
  19: test_arithmetics::inplace_operations::{{closure}}
             at tests/test_arithmetics.rs:118
  20: test_arithmetics::inplace_operations
             at tests/test_arithmetics.rs:122
  21: test_arithmetics::inplace_operations::{{closure}}
             at tests/test_arithmetics.rs:112
  22: core::ops::function::FnOnce::call_once
             at /rustc/6f93e93af6f823948cc13d2938957757c6486d88/src/libcore/ops/function.rs:238
  23: <F as alloc::boxed::FnBox<A>>::call_box
             at libtest/lib.rs:1471
             at /rustc/6f93e93af6f823948cc13d2938957757c6486d88/src/libcore/ops/function.rs:238
             at /rustc/6f93e93af6f823948cc13d2938957757c6486d88/src/liballoc/boxed.rs:673
  24: __rust_maybe_catch_panic
             at libpanic_unwind/lib.rs:102

But I can't reproduce this failure in my local machine.
Do you have any idea?

I broke the build because I didn't realize that (self.ptr as *mut u8) to self.ptr when applying an offset. Should hopefully be fixed now.


runtime(debcontrol): add Static-Built-Using field

From man 5 deb-control:
 Static-Built-Using: package-list
           This dependency field lists  extra  source  packages  that
           were  used  during  the  build of this binary package, for
           static building  purposes  (for  example  linking  against
           static  libraries,  builds  for  source-centered languages
           such as Go or Rust, usage of header-only C/C++  libraries,
           injecting  data blobs into code, etc.).  This is useful to
           track whether this package might need to be  rebuilt  when
           source packages listed here have been updated, for example
           due  to  security  updates.   This  field must be a comma-
           separated list of source package  names  with  strict  ‘=’
           version relationships enclosed within parenthesis.

           Supported since dpkg 1.21.3.

Thanks! Did you check with the Debian Team? ping @jamessan

My bad, didn't realize that the file is maintained by the Debian Team.

thanks, I'll include it then.


Trying to connect to Steam Deck running Bazzite 3.5.0 with Steam Link it doesn't show any video in desktop mode

Describe the bug
Trying to connect from my PC running bazzite:stable to the Steam Deck running bazzite-deck:stable with the Steam Link flatpak, it doesn't show any video (it works if the SD is on Gaming Mode).
I can use the application if I have the SD by my side looking at its screen. So, it connects, but it doesn't show anything on my PC.
Previously, using the same PC with the same Steam Link Flatpak, I could use the application correctly when the Steam Deck was running SteamOS.
Maybe it's related to the fact that the desktop session is running on Wayland on bazzite-deck vs X11 on SteamOS?
What did you expect to happen?
I expected to use Steam Link with both video and controls on the SD while on the desktop.
Output of rpm-ostree status
State: idle
Deployments:
ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
Version: 40.20240630.0 (2024-06-30T20:42:59Z)

Hardware
Galileo
Extra information or context
No response

with the Steam Link flatpak

That's strange.. I thought the steam link flatpak was for connecting not hosting. What I thought you're supposed to do is setup steam link in the steam app itself for the host, and then use the steam link flatpak to connect. Maybe that's why it only works when you're in game mode? because steam is open?
If you still haven't gotten it to work, have you considered trying sunshine?
ujust setup-sunshine

I'm running the Steam Link application on my desktop PC (running Bazzite too), not on the Deck.
I did try Sunshine, but the screen was rotated to the right and I couldn't find a way to fix that.


Be able to Disable all logging for a given Lib

"I want to just disable console logging, actually all logging, in tests. I'd like Console logger to remain in use in shipped assembly.", paraphrased from @leastprivilege
I propose a public static void LogProvider.Disable() and that will mean for every subsequent call to GetLogger() a Noop logger is returned. I can see this being of use to Lib consumers who may just want to turn off logging for a lib they are consuming.
Point of note - this will be static mutable state. This needs to be considered when leveraging parallel testing.
A corresponding public static void LogProvider.Enable() would be needed also.

maybe also have a env var - e.g. "LibLog_Disable" - which instructs liblog to always to Noop logger.

I think thats too noisy for automated builds
https://ci.appveyor.com/project/leastprivilege/thinktecture/build/2.0.9

Backwards compatible API change, so this is moving to v4.1.0

@leastprivilege are you still using this feature?

no


add 0rigin-c0de

add my name in the readme file
this is my first contribution and thanks for guidance

Hey @0rigin-c0de , closing the PR due to lack of response. Feel free to create a new PR with the suggested changes. Thank you! Please let us know if you need any help regarding this.


Convert Section trait to use Reader

I tried to keep the From<&[u8]>, but couldn't get it to work, eg something like:
// error[E0207]: the type parameter `Endian` is not constrained by the impl trait, self type, or predicates
impl<'input, Endian, T> From<&'input [u8]> for T
    where T: Section<EndianBuf<'input, Endian>>,
          Endian: Endianity
{
    fn from(v: &'input [u8]) -> Self {
        Self::from(EndianBuf::new(v))
    }
}

Coverage decreased (-0.3%) to 93.393% when pulling ab3d9e03904324023bce2b12a760563f27624f68 on philipc:section into fdd6feb5b652d69428db488b3854b4f94b0d8692 on gimli-rs:master.

Coverage decreased (-0.3%) to 93.393% when pulling de2f1bd9833cbc92f3a43cfddc2fed8d468d2cbc on philipc:section into fdd6feb5b652d69428db488b3854b4f94b0d8692 on gimli-rs:master.


updates:

Added type hints throughout the code for better readability and IDE support
Moved constants to the top of the file for easier maintenance
Enhanced error handling with more specific exception catches
Improved code organization and modularity
Added comprehensive comments explaining complex operations
Simplified some nested conditionals
Made the config validation more robust
Improved logging messages for better debugging
Standardized error handling and user feedback
Added docstrings to all functions for better documentation

@kasinadhsarma  please rewiew and add a label "hacktoberfest-accepted"


Upgrade dependencies v13

This pull request updates several dependencies at once.

Bors merge bot cheat sheet
We are using bors-ng to automate merging of our pull requests. The following table provides a summary of commands that are available to reviewers (members of this repository with push access) and delegates (in case of bors delegate+ or bors delegate=[list]).

Syntax
Description

bors merge
Run the test suite and push to master if it passes. Short for "reviewed: looks good."

bors merge-
Cancel an r+, r=, merge, or merge=

bors try
Run the test suite without pushing to master.

bors try-
Cancel a try

bors delegate+
Allow the pull request author to merge their changes.

bors delegate=[list]
Allow the listed users to r+ this pull request's changes.

bors retry
Run the previous command a second time.

This is a short collection of opinionated commands. For a full list of the commands read the bors reference.

bors retry

bors retry

bors retry

bors retry

bors retry

bors retry


RSpec upgrade

Upgrade RSpec dependency to at least 3.1, fix deprecation warnings, and switch to the new expect() syntax.
Fixes #19.

Coverage increased (+0.04%) when pulling 3c0692dfac65e5e1d9d9ef08511189f0e66aa580 on threedaymonk:rspec-upgrade into be3c4769451dac55565da7c6416bbb566d7544ff on damian:master.

Your the man!


CTADetector is failing to run

$ bazel-bin/shipshape/cli/shipshape --analyzer_images yulin2/ctadetector -categories CTADetector --stderrthreshold=INFO .
I1008 16:53:55.347716   11643 shipshape_lib.go:78] Starting shipshape...
[...]
I1008 16:54:01.766097   11643 shipshape_lib.go:157] Calling with request shipshape_context:<repo_root:"/shipshape-workspace" > triggered_category:"CTADetector" event:"manual" stage:PRE_BUILD
I1008 16:54:01.766432   11643 shipshape_lib.go:248] Calling to the shipshape service with shipshape_context:<repo_root:"/shipshape-workspace" > triggered_category:"CTADetector" event:"manual" stage:PRE_BUILD
WARNING: Analyzer CTADetector failed to run: The triggered category "CTADetector" could not be found at the locations [localhost:10005 localhost:10006 localhost:10008]
I1008 16:54:01.819013   11643 shipshape_lib.go:200] End of Results.

It might be something wrong with the image itself:
$ docker pull yulin2/ctadetector
[...]
Status: Downloaded newer image for yulin2/ctadetector:latest
$ docker run -it yulin2/ctadetector /bin/bash
/endpoint.sh: line 7: /shipshape-output/shipshape.CTADetector.log: No such file or directory

I think I know what the issue is now. I'm having this problem when any other analyzer image was previously run, but now is not being run. The problem is that the old image is still bound to the ports that we want to use. I'm having this happen for not just the CTA Detector, but any image after I already have android lint running. Docker inspect on the container will confirm if it is the same issue.
The right way to do this is to properly shut down old containers. For now, I may just have all external analyzers go down every time, just to get this working for the tutorial

I put in a hack fix for this (see commit above). This now takes up and down the external analyzers every time. This should be modified to take down existing ones only if they are unused.


Error updating password in 0.59 "E-mail already Used"

Logs are below. I was logged in as user account and went to change my password. Met with big 500 page and the logs showed the following:
[Macaron] Started GET /user/settings/password for <IP_ADDRESS>
[Macaron] Completed /user/settings/password 200 OK in 5.370756ms
[Macaron] Started POST /user/settings/password for <IP_ADDRESS>
2014/12/17 22:49:12 [setting.go:160 SettingsPasswordPost()] [E] UpdateUser: E-mail already used
[Macaron] Completed /user/settings/password 500 Internal Server Error in 88.931019ms

Close for now, feel free to reopen if you want to continue discussing. :wink:


Broken link in ReadMe

The releases page -link mentioned in ReadMe doesn't work.

Thanks for the feedback!
Fixed in e725f23.


External handler for RabbitMQ

Implement an external handler for Rabbit like the one described in #39

First rendition here: 17deb21


Add happy path test on ContainerExport

Everything is in the title, complete coverage on ContainerExport 🐧.
🐸
Signed-off-by: Vincent Demeester<EMAIL_ADDRESS>

LGTM

LGTM


Html in string in dataSource?

I read the docs and it says datasource support array and object but i want html string in datasource and render as it is on screen, but that not working,
how to make it work?

is this what you want?
$('#demo').pagination({
    dataSource: [1, 2, 3, 4, 5, 6, 7, ... , 195],
    callback: function(data, pagination) {
        if (pagination.pageNumber === 2) {
           dataContainer.html(YOUR_HTML_OF_FIRST_PAGE)
        }
    }
})


formulary: fix git clone handling for API formulae

Fixes #14626.

Review period skipped due to critical label.

Thanks @Bo98


Correct unidiomatic sentence about ignore()

Slight English correction. 'to take care of' == 'to look after', in the sense of looking after a child. 'to pay attention to' is better.

Thank you for this pull request! Please check this document for how the Jenkins project handles pull requests.


feat(db): allow swagger path parameters

Summary
Allow '$', '{' and '}' as allowed characters in upstream paths as they are used in swagger
to represent path variables.
This is not agains RFC 3986 and allow the use of swagger syntax for defining routers
Full changelog

[Feat] - Allow swagger path variables when defining upstreams in routes

I do not understand the purpose of this change. I do understand Swagger syntax and path variables, but defining a Route with a path such as /foo/{var}, means that you would have to send a request with the following URL to match it: /foo/%7Bvar%7D (at least, that is how most clients would encode it), and I doubt that this is the intent you had in mind. Were you attempting to perform path parameter extraction maybe?
As for the specifics of the validation rules regarding this property: it currently only accepts "unreserved" characters from RFC 3986:
unreserved  = ALPHA / DIGIT / "-" / "." / "_" / "~"

{ and } are considered "unwise" characters as per RFC 2996, and as such, must be escaped. As for $, it is considered a reserved character (sub-delim) by RFC 3986 2.2, and may be found in application specific use-cases, although I've never encountered one.
That said, we could make the validation rules more lenient, and support matching on a wider character-set (regardless of their percent-encoded representation in the HTTP request). But that is another topic, as it appears this PR's intent is something else, which is still obscure to me.
A good way to show the intent of your PR (and a requirement to see it merged) is to write test cases for it :)

@thibaultcha I will try writing some test to ilustrate the use of this.
E.G: you may add a route with this path /user/${user_id}/data and some plugin or even the upstream may understand user_id as a path variable that should be replaced with appropiate data (e.g, a header value or the claim of a JWT)
Give me tiem to write tests

Hi, I am closing this issue because of lack of activity. If you think it is still unresolved, please reopen with the requested information. Thanks!

@ealogar if you can give this another spin, I'd be interested in this as well


Use relative paths for the grammar input files

https://github.com/marcohu/rules_antlr/issues/12
https://github.com/marcohu/rules_antlr/pull/15#issue-891519520

The file paths that are passed to ANTLR end up in the generated output so using absolute paths breaks caching.
This PR makes it so that the relative paths to the grammar files that we get from Bazel are passed straight through to ANTLR.
To keep ANTLR from trying to recreate the directory structure containing the grammar files within the output directory I had to add -Xexact-output-dir for ANTLR4 and -fo for ANTLR3. ANTLR2 doesn't seem to have an equivalent flag and doesn't seem to have the same behavior for relative grammar file input paths.
Fixes #12.

re-opened at https://github.com/albertocavalcante/rules_antlr/pull/30


Update Fugue Tutorials to 0.8.0

Fugue 0.8.0 favors the Fugue API and Engine Context instead of FugueWorkflow. We need to update all of the places where FugueWorkflow appears. There will be less of an emphasis on the DAG.
There are also new SQL functions that need to be added.

The new list of tasks for this refactor:

[ ] document transform() IO capabilities in the Beginner section
[ ] document engine inference enabled by 0.8.0
[ ] document fugue_sql_flow and fugue_sql in beginner section
[ ] document raw_sql()
[ ] remove DAG in advanced concepts
[ ] remove the tutorial for FugueWorkflow in the beginner section
[ ] update join, distributed computing to use fugue.api
[ ] show fugue.api in 10 minutes
[ ] update FugueSQL in 10 minutes to show new functions
[ ] document out_transform() in beginner section
[ ] update useful_config
[ ] add this article to docs under Best Practices: https://towardsdatascience.com/why-pandas-like-interfaces-are-sub-optimal-for-distributed-computing-322dacbce43
[ ] bring up cloudprovider earlier in the docs
[ ] jupyter lab integration documentation
[ ] tune section has notebooks not included in build


python312Packages.mypy-boto3-*: updates

Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

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

30 packages built:

aws-sam-cli
aws-sam-cli.dist
python311Packages.mypy-boto3-budgets
python311Packages.mypy-boto3-budgets.dist
python311Packages.mypy-boto3-cloudtrail
python311Packages.mypy-boto3-cloudtrail.dist
python311Packages.mypy-boto3-ec2
python311Packages.mypy-boto3-ec2.dist
python311Packages.mypy-boto3-fsx
python311Packages.mypy-boto3-fsx.dist
python311Packages.mypy-boto3-kinesis
python311Packages.mypy-boto3-kinesis.dist
python311Packages.mypy-boto3-pinpoint-sms-voice-v2
python311Packages.mypy-boto3-pinpoint-sms-voice-v2.dist
python311Packages.mypy-boto3-sagemaker
python311Packages.mypy-boto3-sagemaker.dist
python312Packages.mypy-boto3-budgets
python312Packages.mypy-boto3-budgets.dist
python312Packages.mypy-boto3-cloudtrail
python312Packages.mypy-boto3-cloudtrail.dist
python312Packages.mypy-boto3-ec2
python312Packages.mypy-boto3-ec2.dist
python312Packages.mypy-boto3-fsx
python312Packages.mypy-boto3-fsx.dist
python312Packages.mypy-boto3-kinesis
python312Packages.mypy-boto3-kinesis.dist
python312Packages.mypy-boto3-pinpoint-sms-voice-v2
python312Packages.mypy-boto3-pinpoint-sms-voice-v2.dist
python312Packages.mypy-boto3-sagemaker
python312Packages.mypy-boto3-sagemaker.dist


fix: support keep-alive

The issue #61 is caused by the fact that insertBefore/appendChild methods are called twice on inserting reactivated components.
The solution I came to was to skip the second insert. These "expected" and "non-expected" (reactivated) nodes are almost similar, except the parentElement property, which is null for the first inserted node and defined for the reactivated one. The rest part of the expression prevents skipping text and comment nodes which seem to be always connected to a document.

:tada: This PR is included in version 1.4.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


drag with the upload image cannot be published

drag with the upload image will report an error and cannot be published?

sorry but can't you just provide more information about that?


Any idea of using CLI to delete the project?

I would like to use the railway command to delete the specific project, any idea to do this?

Definitely possible. If you wanna add it to the CLI, it’s just deleteProject(Id) in our GraphQL API

I add delete.go document in cmd/ folder and the content as follow:
package cmd

import (
	"context"
	"fmt"

	"github.com/railwayapp/cli/entity"
	"github.com/railwayapp/cli/ui"
	"github.com/railwayapp/cli/uuid"
)

func(h *Handler)Delete(ctx context.Context, req *entity.CommandRequest)error{
	if len(req.Args) > 0 {
		// projectID provided as argument
		arg := req.Args[0]

		if (uuid.IsValidUUID(arg)) {
			project, err := h.ctrl.GetProject(ctx, arg)
			if (err != nil) {
				return err
			}

			return h.ctrl.DeleteProject(ctx, project.Id)
		}

		project, err := h.ctrl.GetProjectByName(ctx, arg)
		if (err != nil) {
			return err
		}

		return h.ctrl.DeleteProject(ctx, project.Id)
	}

	h.Unlink(ctx, req)

	isLoggedIn, err := h.ctrl.IsLoggedIn(ctx)
	if err != nil {
		return err
	}

	if isLoggedIn {
		return h.deleteFromAccount(ctx, req)
	} else {
		return h.deleteFromID(ctx, req)
	}

}

func (h *Handler) deleteFromAccount(ctx context.Context, req *entity.CommandRequest) error {
	projects, err := h.ctrl.GetProjects(ctx)
	if err != nil {
		return err
	}

	if len(projects) == 0 {
		fmt.Printf("No Projects could be deleted.")
		return nil
	}

	project, err := ui.PromptProjects(projects)
	if err != nil {
		return err
	}

	return h.ctrl.DeleteProject(ctx, project.Id)
}

func (h *Handler) deleteFromID(ctx context.Context, req *entity.CommandRequest) error {
	projectID, err := ui.PromptText("Enter your project id")
	if err != nil {
		return err
	}

	project, err := h.ctrl.GetProject(ctx, projectID)
	if (err != nil) {
		return err
	}

	return h.ctrl.DeleteProject(ctx, project.Id)
}

append DeleteProject function in controller/project.go
func (c *Controller) DeleteProject(ctx context.Context, projectID string) error {
	return c.gtwy.DeleteProject(ctx, projectID)
}

and append addRootCmd execution about deleting project operation in init function which in project's main.go as follow
	addRootCmd(&cobra.Command{
		Use:   "delete",
		Short: "Delete Project, may specify projectId as an argument",
		RunE:  contextualize(handler.Delete, handler.Panic),
	})

the result as follow

the delete operation seems to unsuccessful, any idea?

Hey! @TaroballzChen I will be reviewing this once I wake up and working through on why it might not be working. The good news is that the CLI is using all of the same gQL mutations as our front-end so I can check that out and try it against your changes.

Hi! @ndneighbor I'm grateful to hear that.  If any good news during checking, plz guide me how to do that!

Alright, got some news for you- I looked into deleteProject in the controller of the project and it matches the front-end call. I am going to review with the team to see if there is something else that might cause the 400.
(I also noticed that if you try to delete a project with an id that doesn't exist it errors out too, so I want to clean up that flow for you as well.)
Thank you for your patience.


RmRegisterResources LPCWSTR [] parameter is projected as PWSTR**

I think it should be projected as PCWSTR* rather than PWSTR**. The triple pointer part surprises me. The loss of the constant part may be partly related to https://github.com/microsoft/win32metadata/issues/487.
https://docs.microsoft.com/en-us/windows/win32/api/restartmanager/nf-restartmanager-rmregisterresources
(Version used: 10.0.19041.5-preview.68)
@AArnott After the metadata is correct, it would nice to have the friendly overload accept ReadOnlySpan<string> like my working handwritten DllImport did. What I have is string[] coming from a params API, and I really liked that the marshaler took on the burden of looping over this and pinning so that I didn't have to do that.

This seems to have been resolved. 0.1.506:


SASL Type Error

Describe the bug
While using TypeScript, an error was provided by ts-server, informing that plain can't be used as mechanism for SALS.
This is probably a problem with the type definition for SASL.
To Reproduce
This repo contains the code that I am working on and that resulted on this problem. Cloning it and following the README should lead to the same bug.
The error provided is the following:

Expected behavior
It should be possible to use the value 'plain' as 'mechanism' for Kafka configuration.
Observed behavior
The TypeScript server cannot compile the code when the string 'plain' is being used as mechanism.
Environment:

OS: [Linux 5.13.19-2]
NodeJS version [16.8.0]
TypeScript version [4.6.2]

Additional context
The problem has probably been reported before on this issue but it was not properly fixed because it became inactive.
I've had some time to dig deeper and found that the problem lies on the SASLOptions type. The code bellow is probably the part that is causing trouble.
type SASLMechanismOptionsMap = {
   plain: { username: string; password: string };
   "scram-sha-256": { username: string; password: string };
   "scram-sha-512": { username: string; password: string };
   aws: {
     authorizationIdentity: string;
     accessKeyId: string;
     secretAccessKey: string;
     sessionToken?: string;
   };
   oauthbearer: {
   oauthBearerProvider: () => Promise<OauthbearerProviderResponse>;
   };
 };
 export type SASLMechanism = keyof SASLMechanismOptionsMap;
 type SASLMechanismOptions<T> = T extends SASLMechanism
   ? { mechanism: T } & SASLMechanismOptionsMap[T]
   : never;
   export type SASLOptions = SASLMechanismOptions<SASLMechanism>;

The problem here is that SASLOption gets SASLMechanismOptions using SASLMechanism as it's generic type (last line). When 'plain' is provided as 'mechanism', it's type is 'string', which results in this error.
This hypothesis is confirmed by using Literal types for mechanism, that make it work as expected, like in the code bellow.
       const mechanism: "plain" = "plain";
       const sasl = {
         username: env.KAFKA_KEY,
         password: env.KAFKA_SECRET,
         mechanism: mechanism,
       };

If I understand the issue correctly, this is intentional behavior. The type of mechanism is a string literal union - meaning we only accept these specific values. Otherwise you could pass whatever string in there and it'd fail at runtime. If you pass a string, that's a wider type that isn't guaranteed at build-time to be one of the accepted values.
In your example code, the type of sasl is going to be:
{
  username: string;
  password: string;
  mechanism: string;
}

That's not the same thing as SASLOptions. If you tell the compiler that sasl is a SASLOptions, it'll work:
const sasl: SASLOptions = {
         username: env.KAFKA_KEY,
         password: env.KAFKA_SECRET,
         mechanism: 'plain',
};

As a benefit, it'll also tell you if you messed up:

Thanks @Nevon!
I'll use it with it's proper type declaration then.
Do you think there's another way of implementing these types to make the compiler infer SASL type's without explicitly declaring it?
I'm asking this because I couldn'f find any example of this case and, at the same time had to spend some time to make it work.
If it can be easier, I'd be glad to help and send a PR.

With the way Typescript works currently, I don't believe so. To be clear, the compiler checking forcing you to verify that the value you're providing is actually a member of the desired type is a good thing. If we changed it so that the mechanism was just a string you wouldn't get a compile time warning, and instead the code would crash at runtime if you provided an invalid mechanism. What you're after is some kind of automatic narrowing based on the context, so that you don't have to tell the compiler that this string is actually not just a random string, but actually a member of a specific string literal union. There is a proposal for something like this here: https://github.com/microsoft/TypeScript/issues/16896

With the way Typescript works currently, I don't believe so. To be clear, the compiler checking forcing you to verify that the value you're providing is actually a member of the desired type is a good thing. If we changed it so that the mechanism was just a string you wouldn't get a compile time warning, and instead the code would crash at runtime if you provided an invalid mechanism. What you're after is some kind of automatic narrowing based on the context, so that you don't have to tell the compiler that this string is actually not just a random string, but actually a member of a specific string literal union. There is a proposal for something like this here: microsoft/TypeScript#16896

Thanks for clarifying. That is exactly it. I've seen this before on other languages and thought that it could be possible on Typescript as well.


Always use $Default LT version

Issue, if available:
https://github.com/awslabs/karpenter/issues/434
Description of changes:
WIP to hard-code to $Default launch template version rather than allow specifying it (which runs in to a whole host of problems).
Tested that nodes come up properly with and without the node selector on the Provisioner.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

May I label this with docs to make sure the docs get updated when this lands? /gdc

May I label this with docs to make sure the docs get updated when this lands? /gdc

Sure!


Untrusted root cert

I followed the steps in the tutorial. After that when I try to access the cluster through the ingress controller via HTTPS, my browser complains the site cannot be trusted because the root cert is not trusted. Not sure what went wrong.

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

ID: ada58160-dc50-b977-d3bc-65f92406e16d
Version Independent ID: 5c596e04-fddb-effe-3b72-575f4df42d4e
Content: Configure ingress with Azure Kubernetes Service (AKS) cluster
Content Source: articles/aks/ingress.md
Service: container-service
GitHub Login: @iainfoulds
Microsoft Alias: iainfou

Thanks for the question. We are currently investigating and will update you shortly.

@miaojiang as the instructions point out this is expected behavior
https://docs.microsoft.com/en-us/azure/aks/ingress#test-the-ingress-configuration

Thanks @MicahMcKittrick-MSFT, I missed that part. I am new to LetsEncrpt and AKS. How many places do I need to change from letsencrypt-staging to prod?

@miaojiang if you go back to this doc and do a Control + F on this page you can search for "Staging". Everywhere you see that word in the code is where you should replace it with "Prod".
Looks like 3-4 places total.

Thanks @MicahMcKittrick-MSFT, I tried it but it didnt work. A few more detailed questions:

Do I need to install another cert-manager using helm, with issuer-name = letsencrypt-prod?
In the cluster-issuer.yaml, what's the server URL for prod letsencrypt?

Yes

Thanks @MicahMcKittrick-MSFT. I deleted the cert-manager and reinstalled it using helm, also replaced everything with prod. I am still facing the same issue. any thoughts?

I followed the tutorial again from scratch and it worked. Thanks for all the help.


add Pokémon style

I think an old version had the option to generate Pokémons as icons like this i.e.:

I loved those and most of my contacts have those icons savers in the vcard , but I cannot find the generator any more.
Could you add this style please?

Identiconizer never had this option, it might've been a different app.
On Sat, Dec 7, 2019, 04:40 Ruben Barkow-Kuder<EMAIL_ADDRESS>wrote:

I think an old version had the option tree generate Pokémons as icons like
this i.e.:
[image: 20191207_040317]
https://user-images.githubusercontent.com/1591563/70368494-82bb2b00-18ab-11ea-8c6f-bef1b9cea105.jpg
I loved those and most of my contacts have those icons savers in the vcard
, but I cannot find the generator any more.
Could you add this style please?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/GermainZ/Identiconizer/issues/26?email_source=notifications&email_token=AAWFDFNBS6MBKDGXYQ7O253QXMLLNA5CNFSM4JXG7XPKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4H6ZQFHQ,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAWFDFNZDVS3ADN6FEO4JPDQXMLLNANCNFSM4JXG7XPA
.

Anyway, or would be great to have more styles added, for example vanillicon and Unicornify!


Command line options for project manager should be passed to edited project

Godot 3.0.2
Fedora 28,  Iris Graphics 540
If I start Godot with the -f option, the project manager comes up full-screen but when I load a project, the editor comes up simply maximized. This is exactly the opposite of what I want. I don't see an option to always bring up the editor as full-screen.
Please add an option to bring up the editor as full-screen (or have it persist the full-screen state).

I guess you're talking about the -f option, not -e?
The options passed work only for the current instance, and when you open a project in the project manager, it spawns a new instance. So to edit a project in fullscreen, you should run godot -e -f directly in the project's folder (or godot -e -f --path path/to/project).

@akien-mga
Yes, sorry, I meant the -f option. Is there any way to launch the editor from the project manager as full-screen?

Feature and improvement proposals for the Godot Engine are now being discussed and reviewed in a dedicated Godot Improvement Proposals (GIP) (godotengine/godot-proposals) issue tracker. The GIP tracker has a detailed issue template designed so that proposals include all the relevant information to start a productive discussion and help the community assess the validity of the proposal for the engine.
The main (godotengine/godot) tracker is now solely dedicated to bug reports and Pull Requests, enabling contributors to have a better focus on bug fixing work. Therefore, we are now closing all older feature proposals on the main issue tracker.
If you are interested in this feature proposal, please open a new proposal on the GIP tracker following the given issue template (after checking that it doesn't exist already). Be sure to reference this closed issue if it includes any relevant discussion (which you are also encouraged to summarize in the new proposal). Thanks in advance!


debian/control: build packages on ubuntu 22.04

Description
This PR supports cloudstack packaging on ubuntu 22.04
Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[x] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[x] Minor

Screenshots (if appropriate):
How Has This Been Tested?

Hi @weizhouapache
Can you make nodejs (>= 14)
Since nodejs 12 is not supported by ubuntu 22.04 release and is deprecated
https://deb.nodesource.com/node_12.x/dists/
There is ubuntu 22.04 -Jammy in node_14.x which is LTS
https://deb.nodesource.com/node_14.x/dists/
Also is "dh-systemd" required for a successful build ?
As per https://bugs.debian.org/822670, the dh-systemd package has been merged with the main debhelper package since version 9.20160709
On Ubuntu 22.04 (Jammy) the dh-systemd package has been completely removed,

@kiranchavala
thanks for your review.
since debian/control is also used when build package on ubuntu 20.04, it should be compatible with ubuntu 20.04 as well 22.04
for example, dh-systemd | debhelper (>= 13) means both dh-systemd (on ubuntu 20.04) and debhelper (>=13) on ubuntu 22.04 work.
The change for nodejs makes sense. The version has been update in PR #6956
https://github.com/apache/cloudstack/pull/6956/files#diff-6e8c08cff231f603dfa7a4d5f873a6fee6e5c730d431c113bbf5b1180c6983e4
However, I need to check if nodejs verison has been changed in our container for deb packaging.
If it still uses nodejs12, the packaging jobs will fail if this is merged.

Code LGTM

@blueorangutan package

@rohityadavcloud a Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

@rohityadavcloud a Jenkins job has been kicked to build packages. It will be bundled with
SystemVM template(s). I'll keep you posted as I make progress.


Not working with Episerver 11

Hey,
There are some breaking changes in Episerver 11 so when implementing this while on Episerver 11 it gives an error saying that is cannot find InitializationModule.
Together with a colleague we copied this whole git in our existing project and we got it to work. I've cloned this git locally and applied the changes in the epi11 branch. However, with us this caused an error when logging in on /episerver/cms with AD.
Would you mind having a look at my pull request and check whether you also get that error when logging in?
Cheers,
Lindy

Update: I can't commit because I don't have access. So basically what I did  was branch from epi10,  change the TargetFrameworkVersion to 4.6.1 and update all packages to the latest.

Hi,
You can definitely do all the commits in your private fork and then can do pull request to the origin.
It will be easier to maintain and test.
Think I don't have proper AD at hand to test it out..
What errors you see?
Get Outlook for Android

From: Lindy<EMAIL_ADDRESS>Sent: Tuesday, February 13, 2018 5:32:11 PM
To: valdisiljuconoks/MvcAreasForEPiServer
Cc: Subscribed
Subject: Re: [valdisiljuconoks/MvcAreasForEPiServer] Not working with Episerver 11 (#2)
Update: I can't commit because I don't have access. So basically what I did was branch from epi10, change the TargetFrameworkVersion to 4.6.1 and update all packages to the latest.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fvaldisiljuconoks%2FMvcAreasForEPiServer%2Fissues%2F2%23issuecomment-365302143&data=02|01||f14c77be479941f921b508d572f6f46a|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636541327336520166&sdata=2LBt%2Fo3Mjjwt8%2FkCtZvsjClKr%2FsfE697lNW%2FeP0NMS8%3D&reserved=0, or mute the threadhttps://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABr3C03q_rXrKv3T4lVdxCq2MbhoRqNfks5tUar7gaJpZM4SD7Qd&data=02|01||f14c77be479941f921b508d572f6f46a|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636541327336520166&sdata=2YaZeZi%2B1IXlSLwuNAg%2FOTUS0Aa6krwfzuvA7tHXPWc%3D&reserved=0.

Okay, done!
My colleague got an error when he tried logging in to "/episerver" with his Windows credentials. It said that the user could not be found.

Hi,
You sure that it's related to Mvc areas?
Get Outlook for Android

From: Lindy<EMAIL_ADDRESS>Sent: Wednesday, February 14, 2018 2:19:00 PM
To: valdisiljuconoks/MvcAreasForEPiServer
Cc: wałdis iljuczonok; Comment
Subject: Re: [valdisiljuconoks/MvcAreasForEPiServer] Not working with Episerver 11 (#2)
Okay, done!
My colleague got an error when he tried logging in to "/episerver" with his Windows credentials. It said that the user could not be found.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fvaldisiljuconoks%2FMvcAreasForEPiServer%2Fissues%2F2%23issuecomment-365590635&data=02|01||026628014e2a42335c1c08d573a521d7|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636542075426861299&sdata=PBtUiVxqNmZ8rxyVN5w8HW%2Bc4o1d4ojQUJooPyMZ0xM%3D&reserved=0, or mute the threadhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABr3C3lavFaakmdK4dEAsA90SPSdp4ahks5tUs8zgaJpZM4SD7Qd&data=02|01||026628014e2a42335c1c08d573a521d7|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636542075426861299&sdata=rJyXraXjL%2FXt6HGB%2F8XugGsBNCL0pddXDcoC1TUBUtc%3D&reserved=0.

My colleague got that error. I just tried it out myself and I cannot reproduce. Added a minor change and it works like a charm now 😄

Wait for 4.0 version of the package

Awesome 😎


Todos API Endpoints

See the documentation for Todos.
We'd need:

get_todos: GET /todos
mark_todo_as_done: DELETE /todos/:id
mark_all_todos_as_done: DELETE /todos

It'd also be nice to have add_todo and mark_todo_as_done methods for issues/MRs, see http://docs.gitlab.com/ce/api/merge_requests.html#create-a-todo and http://docs.gitlab.com/ce/api/issues.html#create-a-todo for creating Todos for an Issue/MR.
Marking an Issue/MR as done isn't as easy since there isn't an endpoint for that, it's expected that you use the DELETE /todos/:id endpoint (maybe that should be added to the API in GitLab itself?).

#290 Should have closed it.

@akkee - For future reference: https://github.com/blog/1506-closing-issues-via-pull-requests


New version: AdventOfCode v1.1.1

Registering package: AdventOfCode
Repository: https://github.com/SebRollen/AdventOfCode.jl
Created by: @SebRollen
Version: v1.1.1
Commit: 9f8234708793d0ab220f58bd157ae1b2a96c462e
Reviewed by: @SebRollen
Reference: https://github.com/SebRollen/AdventOfCode.jl/issues/31#issuecomment-1333824716
Description: Helper library for working with Advent of Code in Julia

This PR should be closed in favor of #73250, I goofed on the version number


Requirement is pinned for pyskyqhub 0.1.0: aiohttp==3.6.2

This library supports an integration in Home Assistant.
The upcoming pip resolver will be more strict in resolving package version conflicts:
http://pyfound.blogspot.com/2020/03/new-pip-resolver-to-roll-out-this-year.html#what-will-change
To avoid future issues it would be good if this library would change its pinning to allow any higher version and just set a minimum version.

Thanks for your support of Home Assistant!

I'm working towards changing this to >=3.6.2. Just testing out an updated version of the module before putting a PR into HA.

Close with the PR submitted to HA core


Optionally support Docker 18.03 and 18.06

What this PR does / why we need it:
Allows users to optionally select Docker 18.03 or 18.06
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
https://github.com/Azure/acs-engine/issues/4029

Ah - I may need to abandon this.  Per @CecileRobertMichon in the tracking issue, there are some licensing restrictions that prevent me from making this change.

Can't do this due to licensing issues. moby support is in-progress


full train fixes

change LR to 2e-5 (learns better)
honor the gradient accumulation given by the multipack sampler

the LR is the big change here. The previous version of full train has little to no improvement after 8 epochs. This version knows about the new information after as little as 1 epoch.
This is a major improvement.
Also add logging to print information about the data

Checklist:

[ ] Commit Message Formatting: Commit titles and messages follow guidelines in the
conventional commits.
[ ] Changelog updated with breaking and/or notable changes for the next minor release.
[ ] Documentation has been updated, if necessary.
[ ] Unit tests have been added, if necessary.
[ ] Functional tests have been added, if necessary.
[ ] E2E Workflow tests have been added, if necessary.

@Mergifyio backport release-v0.19


[Feature]: Button macros in the sortable table in form option

What feature would you like to add to the ONS Design System?
Add more options for the button, instead of using classes
Also, add an example of using the form option with a button on the sortable table
Why should this new feature be added to the Design System?
It's macro options that the button already has and since we reference it in the documentation it becomes confusing. I tried to use  "variant" and it wasn't modifying the button. I had to look into the code to discover it wasn't set up. I appreciate that we could use classes to get the same results, but then it would be worth mentioning that.
See form object
Supporting material
https://github.com/ONSdigital/design-system/pull/2211
Contacts
Alexandra Whitham DST SPP Shared Services team

I managed to use value with onsButton instead to get the arrow symbol on the button right, but this might be a good option to put in documentation as an example of how to use it within a table.
The odd thing is that in documentation for the data in the row options name and data are not required, but it wouldn't work if I don't provide those:

Name
Type
Required
Description

name
string
false
Name to add to the td element

data
string
false
The corresponding th for the td for responsive tables

value
string
false
The content for the td cell

{% for dataset in datasets %}
                    {% do table_rows.append(
                        {
                            "tds": [
                                {
                                    "form": {
                                        "method": "Get",
                                        "button": {
                                            "type": "button",
                                            "text": "View details",
                                            "classes": "ons-btn--secondary ons-btn--small",
                                            "url": dataset
                                        }
                                    }
                                },
                                {
                                    "value": onsButton({
                                        "text": "View details",
                                        "classes": 'ons-u-mb-m',
                                        "iconType": 'arrow-next',
                                        "iconPosition": 'after',
                                        "url": dataset,
                                        "variants": ['secondary', 'small']
                                    }),
                                    "data": "View details",
                                    "name": "tbl-details"
                                }
                            ]
                        }
                    ) %}
                {% endfor %}


Fix/gazebo simulator CI

Status
PRODUCTION / DEVELOPMENT
Description
The metapackage velodyne_simulator should not be included as a dependency.
Pipeline: https://gitlab.com/ServandoGS/Autoware/pipelines/47501619
Related PRs
#1930

This PR is merged.


Cleanup makefile and docs

Motivation and Context
Fix some inconsistencies, and remove dead docs and config.
Description

update the Makefile targets to be more consistent in order and pluralization
remove the need to mkdir outside of the Makefile
remove dead docs and config related to inference

@dnephin Can you rebase? :}


[Playwright] Flaky test in multifile-editor.spec.ts

Describe the bug
This test case appears to be flaky:
https://github.com/freeCodeCamp/freeCodeCamp/blob/c7a3677282834c813c75e60781c5097e33917e05/e2e/multifile-editor.spec.ts#L10
I first found it in CI, but I was able to reproduce the issue locally as well.
Build log: https://github.com/freeCodeCamp/freeCodeCamp/actions/runs/7331463113/job/19964264099?pr=52577
Steps to reproduce
Run npx playwright test multifile-editor.spec.ts multiple times.
Screenshots
CI
Notes:

The failure of the test in reset-modal.spec.ts was expected as I was changing the implementation code
The failure of the test in learn.spec.ts was not expected. This is also a flaky test and the issue is tracked in #52605

Local

Can I work on this? It is assigned to you though.

@huyenltnguyen
I've investigated this issue and found places that need to be fixed, and created a pull request: https://github.com/freeCodeCamp/freeCodeCamp/pull/53031.
The first is related to the editors variable and playwright .all() method. According to their documentation:

NOTE
locator.all() does not wait for elements to match the locator, and instead immediately returns whatever is present in the page. When the list of elements changes dynamically, locator.all() will produce unpredictable and flaky results. When the list of elements is stable, but loaded dynamically, wait for the full list to finish loading before calling locator.all().

So the current usage is a bit incorrect and the .all() method does not wait for all editors to be dynamically added to the page.
And, the second one is related to the click event in the loop with the following error:
waiting for element to be visible, enabled and stable
element is visible, enabled and stable
scrolling into view if needed
done scrolling

 intercepts pointer events

For this cases Forcing the click could be used.
Related issues in the playwright repo:

https://github.com/microsoft/playwright/issues/12298
https://github.com/microsoft/playwright/issues/13576

Could, you, take a look, please?


"Restart Kernel and Run All Cells" doesn't run any cells

This seems to happen when notebook >= 6.1.0 is installed. notebook up to 6.0.3 seems fine. The cells are marked as waiting, but the kernel is not. Making almond log each message it receives, it seems no execute_request message is received by almond for these cells.

To test that locally, if you're using conda, force specific notebook versions with
$ conda install -c conda-forge notebook=6.1.0

for example.

The 6.0.3...6.1.0 diff of notebook is quite large. Not sure what changed that could have caused this.

This happens to me on macOS. I didn't try on Linux or Windows.


translation into indonesia Update LICENSE

Thank you for providing this translation.
Could you amend the PR to add this translation as LICENSE_id_ID instead of replacing the English one?
We need to keep the English version as its this one which is legally binding: https://www.apache.org/foundation/license-faq.html#Translation

Closing, lets say, superseded by #2.


Added RSS:0 Bug

Here is a bug when trying to import a file:

As per what I mentioned in other issue please explain properly what happened. based on the log file Im gonna asume you are trying to import OPML file. but you are not giving in full details such as where is the OPML file come from and the OPML file content.

I don't know what else to say and explain. The file is on my SD card and not on the device itself. But that shouldn't be the issue.

The OPML file wouldn't magically appear at your SD card isn't it? also if please share the OPML file.


added inorder.cpp

Description of Change

added a new file inorder.cpp which contains the code for algorithmic implementation of inorder traversal of trees using cpp
Checklist

[x ] Added description of change
[x ] Added file name matches File name guidelines
[ x] Added documentation so that the program is self-explanatory and educational - Doxygen guidelines
[x ] Relevant documentation/comments is changed or added
[ x] PR title follows semantic commit guidelines
[x ] Search previous suggestions before making a new one, as yours may be a duplicate.
[x ] I acknowledge that all my contributions will be made under the project's license.

Notes:
added implementation of inorder traversal of trees in cpp
solved issue "#2014"

@mishraabhinn if this issue is still open can you please assign it to me ?

hello sir can you assign this issue to me?

Please assign me this


Stopped working after latest patch

The hack has stopped working after the latest patch.

Yeah, that won't be working after the patch, cause the addresses of instructions changed. Is there even an interest in having Y axis mouse look still (considering they have fixed the damage values for Hell Knight?

For me, yes. Without Y look I'd rather switch to a source port.

Very well - will try and get it restored (again, it's just a look, not actually aiming). Thankfully they fixed other major issues in this patch.

Welp, I've just spent like 2 hours trying to find it camera rotation and I just can't. Need smarter people (or people with more time on their hands) to look into it :(

Well drat. Guess that's the end of that

I guess there is not much point in working on it now:
https://steamcommunity.com/app/1148590/discussions/0/3193619419610701034/
Yeah, I also noticed FPS issues on my PC.

Apparently they are working on a new patch to fix the issues. And the 91 fps cap is apparently a leftover from the stadia version... an oopsie doopsie from the devs i guess haha...


Restrict access to some parts of external deployer for non-superadmins

Prior to the public beta launch (~400 emails), we should hide the following from non-superadmins:

[ ] Printful app
[ ] Uphold app
[ ] Server tab (under settings)
[ ] Console tab (under settings)

Will be in next deploy...


Add a label for a11y

Fixes

Fixes #59 by @zackkrida
Description

This PR adds a label for accessibity. This will ideally be used for issues that point out problems and shortcomings with accessibility of our components and PRs that help to improve them.
Technical details

This makes the most sense for the frontend and extension repos, which are the primary user-facing codebases.
Additional context
The proper a11y icon (see image) is not an emoji (yet; unfortunately).

The ♿ wheel chair symbol is the next best alternative based on the Emojipedia description.
Checklist

[x] My pull request has a descriptive title (not a vague title like Update index.md).
[x] My pull request targets the default branch of the repository (main or master).
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[ ] I added or updated tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[ ] I tried running the project locally and verified that there are no visible errors.

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

Great!

Force pushed to fix a typo

Thanks @dhruvkb !


fix CellBookmark typings

https://github.com/ProseMirror/prosemirror-tables/pull/160
The CellBookmark type added here was incorrect and the following error is fixed.
index.ts:25:43 - error TS2322: Type 'CellSelection' is not assignable to type 'Selection'.
  The types of 'getBookmark().map' are incompatible between these types.
    Type '(mapping: Mapping) => CellBookmark' is not assignable to type '(mapping: Mappable) => SelectionBookmark'.
      Types of parameters 'mapping' and 'mapping' are incompatible.
        Type 'Mappable' is missing the following properties from type 'Mapping': maps, from, to, slice, and 5 more.

1      let state = EditorState.create({ doc, selection: CellSelection.create(table, 0) });

@ocavue sorry, I would like to request a review of the corrections made in the last PR https://github.com/ProseMirror/prosemirror-tables/pull/160 , as they were incorrect.


WorK In Progress : Copy nonempty dirs

I am using Jenkins with build using .travis.yml option on Solaris.
Problem#1) When we invoke "dist" or "tar" target in Makefile, it is failing when it tries to copy empty directory as shown below :
    $ cp boringssl /var/tmp/openssl-copy.2972/openssl-1.1.1-dev/boringssl
    cp: boringssl: is a directory

Fix : Do not copy an empty directories.
Problem#2) It was failing with error "Can't open perl script "./Configure": No such file or directory. The problem was  Configure script is present in /var/tmp/openssl-copy.15468/openssl-1.1.1-dev/ and not in /var/tmp/openssl-copy.15468/.
Problem#3) tar in Solars doesn't have --owner and --group option.
Problem#4) It creates openssl-1.1.1-dev.tar.gz  but is looking for _srcdist.tar.gz as shown below
	cd .; ls -l ../openssl-1.1.1-dev.tar.gz
        -rw-r--r--   1 mevyas   staff    6150045 Aug  8 10:37 ../openssl-1.1.1-dev.tar.gz
        tar: _srcdist.tar.gz: No such file or directory

Suggested Fix:
diff --git a/Configurations/unix-Makefile.tmpl b/Configurations/unix-Makefile.tmpl
index 9412ac6..e64f60a 100644
--- a/Configurations/unix-Makefile.tmpl
+++ b/Configurations/unix-Makefile.tmpl
@@ -727,7 +727,7 @@ tar:
        cd $(SRCDIR); ls -l $(TARFILE).gz

 dist:
-       @$(MAKE) PREPARE_CMD='$(PERL) ./Configure dist' tar
+       @$(MAKE) PREPARE_CMD='$(PERL) ./Configure dist' TARFILE=$(TARFILE) NAME=$(NAME) tar

 # Helper targets #####################################################

Problem# 5) Move the following osx if condition to appropriate configuration file
if [ "$1" == osx ]; then
    make NAME='_srcdist' TARFILE='_srcdist.tar' \
         TAR_COMMAND='$(TAR) $(TARFLAGS) -cvf -' tar
else
    make TARFILE='_srcdist.tar' NAME='_srcdist' dist
fi

Hmmm, I'm dubious about some of the changes here. Directories aren't first class objects in git, so they should never appear, with the exception for submodules (such as boringssl). There should be a simpler way to filter those away.
I'm not really working this week, so if you guys can have some patience to next week, I'll be happy to join the fun.

I can change it to  git ls-tree -r --name-only --full-tree HEAD | grep -v '^fuzz/corpora' | grep -v '^boringssl$' it is cleaner but it is not a generic solution.
Will wait till perfection.

#4178 is a simpler alternative that achieves the same thing.

Sorry, I wrote too fast.  #4178 solves the submodule issue (which were the cause of the "copying directory" issue), not the tar issue.
It's true that our tar target assumes a tar that understands --owner and --group.  GNU tar understands those options, so it may be argued that GNU tar should be used.

I am closing this pull request since it is fixed in commit https://github.com/openssl/openssl/pull/4178

I am closing this pull request...

Okie. Thank you all the same, this did make some issues clear


[Guide] Add guide to set up CLion for compiler development

Added information how to set up CLion for compiler development.
Adding upon request from @shahmishal, since some other people may be wanting to work on Swift on platforms where there is no Xcode etc. :-)

Thanks

@swift-ci please smoke test

The way I use CLion with this project is building the compiler using Ninja first, then open the build directory directly in CLion. CMake options are automatically set to only -G "Ninja", which is much fewer than what's suggested in the guide. With my limited experience, this works fine. Can this be added to the guide as an alternative approach to first-time setup?

I got to this working a while ago and never poked at it anymore since -- feel free to edit the guide and suggest changes! 👍

@swift-ci please smoke test


Does not work with laravel 5.6

I recently upgraded my laravel to 5.6, and my favorite tool, laravel-id-helper, which I have used on every major laravel project no longer is working, hopefully this get resolved sooner than later.
our requirements could not be resolved to an installable set of packages.

  Problem 1
    - Conclusion: remove laravel/framework 5.6.x-dev
    - Conclusion: don't install laravel/framework 5.6.x-dev
    - barryvdh/laravel-ide-helper v2.4.0 requires illuminate/support ^5.0,<5.6 -> satisfiable by illuminate/support[5.0.x-dev, 5.1.x-dev, 5.2.x-dev, 5.3.x-dev, 5.4.x-dev, 5.5.x-dev, v5.0.0, v5.0.22, v5.0.25, v5.0.26, v5.0.28, v5.0.33, v5.0.4, v5.1.1, v5.1.13, v5.1.16, v5.1.2, v5.1.20, v5.1.22, v5.1.25, v5.1.28, v5.1.30, v5.1.31, v5.1.41, v5.1.6, v5.1.8, v5.2.0, v5.2.19, v5.2.21, v5.2.24, v5.2.25, v5.2.26, v5.2.27, v5.2.28, v5.2.31, v5.2.32, v5.2.37, v5.2.43, v5.2.45, v5.2.6, v5.2.7, v5.3.0, v5.3.16, v5.3.23, v5.3.4, v5.4.0, v5.4.13, v5.4.17, v5.4.19, v5.4.27, v5.4.36, v5.4.9, v5.5.0, v5.5.16, v5.5.17, v5.5.2, v5.5.28, v5.5.33].
    - barryvdh/laravel-ide-helper v2.4.1 requires illuminate/support ^5.0,<5.6 -> satisfiable by illuminate/support[5.0.x-dev, 5.1.x-dev, 5.2.x-dev, 5.3.x-dev, 5.4.x-dev, 5.5.x-dev, v5.0.0, v5.0.22, v5.0.25, v5.0.26, v5.0.28, v5.0.33, v5.0.4, v5.1.1, v5.1.13, v5.1.16, v5.1.2, v5.1.20, v5.1.22, v5.1.25, v5.1.28, v5.1.30, v5.1.31, v5.1.41, v5.1.6, v5.1.8, v5.2.0, v5.2.19, v5.2.21, v5.2.24, v5.2.25, v5.2.26, v5.2.27, v5.2.28, v5.2.31, v5.2.32, v5.2.37, v5.2.43, v5.2.45, v5.2.6, v5.2.7, v5.3.0, v5.3.16, v5.3.23, v5.3.4, v5.4.0, v5.4.13, v5.4.17, v5.4.19, v5.4.27, v5.4.36, v5.4.9, v5.5.0, v5.5.16, v5.5.17, v5.5.2, v5.5.28, v5.5.33].
    - don't install illuminate/support 5.3.x-dev|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support 5.4.x-dev|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support 5.5.x-dev|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.3.0|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.3.16|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.3.23|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.3.4|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.4.0|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.4.13|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.4.17|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.4.19|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.4.27|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.4.36|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.4.9|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.5.0|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.5.16|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.5.17|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.5.2|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.5.28|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.5.33|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support 5.1.x-dev|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support 5.2.x-dev|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.1.1|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.1.13|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.1.16|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.1.2|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.1.20|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.1.22|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.1.25|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.1.28|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.1.30|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.1.31|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.1.41|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.1.6|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.1.8|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.2.0|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.2.19|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.2.21|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.2.24|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.2.25|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.2.26|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.2.27|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.2.28|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.2.31|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.2.32|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.2.37|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.2.43|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.2.45|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.2.6|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.2.7|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support 5.0.x-dev|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.0.0|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.0.22|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.0.25|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.0.26|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.0.28|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.0.33|don't install laravel/framework 5.6.x-dev
    - don't install illuminate/support v5.0.4|don't install laravel/framework 5.6.x-dev
    - Installation request for laravel/framework 5.6.* -> satisfiable by laravel/framework[5.6.x-dev].
    - Installation request for barryvdh/laravel-ide-helper ^2.4 -> satisfiable by barryvdh/laravel-ide-helper[v2.4.0, v2.4.1].

Current composer.json file
{
    "name": "laravel/laravel",
    "description": "The Laravel Framework.",
    "keywords": ["framework", "laravel"],
    "license": "MIT",
    "type": "project",
    "require": {
        "php": ">=7.1.0",
        "aws/aws-sdk-php": "^3.52",
        "barryvdh/laravel-cors": "^0.11.0",
        "doctrine/dbal": "^2.6",
        "fideloper/proxy": "~4.0",
        "hashids/hashids": "^2.0",
        "laravel/framework": "5.6.*",
        "laravel/horizon": "^1.1",
        "laravel/tinker": "~1.0",
        "league/flysystem-aws-s3-v3": "^1.0",
        "league/fractal": "^0.17.0",
        "nategood/httpful": "^0.2.20",
        "pda/pheanstalk": "^3.1",
        "predis/predis": "^1.1",
        "ramsey/uuid": "^3.7"
    },
    "require-dev": {
        "filp/whoops": "~2.0",
        "nunomaduro/collision": "~1.1",
        "fzaninotto/faker": "~1.4",
        "mockery/mockery": "~1.0",
        "phpunit/phpunit": "~6.0",
        "symfony/thanks": "^1.0"
    },
    "autoload": {
        "classmap": [
            "database/seeds",
            "database/factories"
        ],
        "psr-4": {
            "App\\": "app/"
        }
    },
    "autoload-dev": {
        "psr-4": {
            "Tests\\": "tests/"
        }
    },
    "extra": {
        "laravel": {
            "dont-discover": [
            ]
        }
    },
    "scripts": {
        "post-root-package-install": [
            "@php -r \"file_exists('.env') || copy('.env.example', '.env');\""
        ],
        "post-create-project-cmd": [
            "@php artisan key:generate"
        ],
        "post-autoload-dump": [
            "Illuminate\\Foundation\\ComposerScripts::postAutoloadDump",
            "@php artisan package:discover"
        ],
        "post-install-cmd": [
            "php artisan config:cache",
            "php artisan clear-compiled",
            "php artisan migrate"
        ]
    },
    "config": {
        "preferred-install": "dist",
        "sort-packages": true,
        "optimize-autoloader": true
    },
    "minimum-stability": "dev",
    "prefer-stable": true
}

Seems like it's fixed in 2.4.2


Discord bot fails to search documentation

Documentation commands are breaking with the error message:
Something went very wrong, me.piggypiglet.docdex.documentation.IndexURLBuilder@<hashcode>
Some other commands are failing with no error message, with the command message just being deleted, not sure if that's related, though.
Tested in the Java Community server.

Resolved


Handle SIGPIPE correctly and autogenerate main() for each util

This should prevent the SIGPIPE problem in #374, although we will still need to check for usages of unwrap() which should actually be returning a Result to completely prevent printing to stderr incorrectly.

@mpkh this should be ready now


152 simple minvar experiment

@kasperjo @phschiele
I am working on a l little talk about new cvxpy. I came across a few issues

Is this still a thing?
/Users/a13069q/github/cvxmarkowitz/.venv/lib/python3.10/site-packages/cvxpy/reductions/solvers/solving_chain.py:235: UserWarning: Your problem has too many parameters for efficient DPP compilation. We suggest setting 'ignore_dpp = True'.

        x = cp.Variable(n)
        L = cp.Parameter((n, n))

        objective = cp.Minimize(cp.norm2(L.T @ x))
        constraints = [cp.sum(x) == 1, x >= 0]

        prob = cp.Problem(objective, constraints)

How would I compile the problem now?

Ok, diving deeper into cvxpy:
def f2():
    U = uu
    x = cp.Variable(n)

    objective = cp.Minimize(cp.norm2(U @ x))
    constraints = [cp.sum(x) == 1, x >= 0]
    prob = cp.Problem(objective, constraints)

    data, solving_chain, inverse_data = prob.get_problem_data(
        solver
    )
    print(data)

    solution = solving_chain.solve_via_data(
        prob, data)

    prob.unpack_results(solution, solving_chain, inverse_data)
    return prob.value

I wonder how can I update data without calling prob.get_problem_data. I update values for one or all parameters. But when hitting solve it still runs self.get_problem_data?

@tschm We did not remove the warning for a large number of parameters (yet)
You can call
    data, solving_chain, inverse_data = prob.get_problem_data(
        solver
    )

to canonicalise the problem ahead of time.
Then you just update the parameters and call solve. It will automatically use the cached canonicalisation map.

How can I change the backend to RUST? It tells me it is still using CPP backend...
@phschiele Time for Zoom call today or tomorrow?


Different problems on stopping and restart the player

There are different problems on stopping and restarting the player doing this:
await this.wsPlayer.destroy();
this.wsPlayer = null;
this.wsPlayer = new WSPlayer(.....)

On doing this we have different problems, one of  exception we are running into is this:
console.js:26 Unhandled Promise rejection: Failed to execute 'remove' on 'SourceBuffer': This SourceBuffer is still processing an 'appendBuffer' or 'remove' operation.
Error: Failed to execute 'remove' on 'SourceBuffer': This SourceBuffer is still processing an 'appendBuffer' or 'remove' operation.
    at promises.push.Promise (rtsp_player.js:1006)
    at new t (polyfills.js:3)
    at MSEBuffer.clear (rtsp_player.js:1004)
    at MSEBuffer.destroy (rtsp_player.js:993)
    at MSE.reset (rtsp_player.js:1236)
    at MSE.destroy (rtsp_player.js:1165)
    at Remuxer.destroy (rtsp_player.js:2334)
    at WSPlayer.destroy (rtsp_player.js:4776)
    at <anonymous>
    at promises.push.Promise (rtsp_player.js:1006)
    at new t (polyfills.js:3)
    at MSEBuffer.clear (rtsp_player.js:1004)
    at MSEBuffer.destroy (rtsp_player.js:993)
    at MSE.reset (rtsp_player.js:1236)
    at MSE.destroy (rtsp_player.js:1165)
    at Remuxer.destroy (rtsp_player.js:2334)
    at WSPlayer.destroy (rtsp_player.js:4776)
    at <anonymous>
    at c (polyfills.js:3)
    at polyfills.js:3
    at t.invoke (polyfills.js:3)
    at r.run (polyfills.js:3)
    at polyfills.js:3
    at t.invokeTask (polyfills.js:3)
    at r.runTask (polyfills.js:3)
    at o (polyfills.js:3)
    at <anonymous>

On doing this we have different problems,

Does this happen to any source or one of some kind?


No .htaccess

There is currently no .htaccess file in place with rewrites that remove index.php, so out of the box, the demo doesn't work beyond the first page. Is that intentional?

Commiting .htaccess is a bad practice, because it complicates deploy. However, it would be nice to have example config files for the most used web servers in the documentation.

@dzuelke - as per @jkufner comment this is considered as a bad practise.
Check Configuring a Web Server documentation section for an explanation and information on how you should configure your web server.
Nevertheless you can use apache-pack recipe for adding .htaccess to you public folder by executing
composer require apache-pack.
Hope this helps and answers you concern.

Actually a good point. As far as we have a "Deploy to Heroku" button in README, we should have a proper .htaccess for it as well to make it working out of the box

Yeah I'm mostly interested in having it work out of the box on as many setups as possible, as it's a demo app. I could easily do a PR with a Heroku specific config or something, but would rather not clutter the repo with a vendor specific thing (the demo right now is not working on Heroku, for other reasons as well, such as SensioDistributionBundle being gone which used to write the Procfile).

It's true that we don't care about .htaccess in this demo app because we recommend to use the Symfony server (bin/console server:start command) to browse the app.
However, I agree that this should work out-of-the-box on Heroku (unless that requires us to change our code). We already have an app.json with Heroku config and stuff (https://github.com/symfony/demo/blob/master/app.json). Could we make more changes in that file to fix this issue? Thanks!

For that we'd need a separate Procfile, but I think I'll add support for automatic detection of Symfony to Heroku's PHP support. For that I need a definitive answer to https://github.com/symfony/symfony-docs/issues/8766 though.


Declarative containers: more veth interfaces

With these changes, a container can have more then one veth-pair. This allows for example to have LAN and DMZ as bridges on the host and add dedicated containers for proxies, ipv4-firewall and ipv6-firewall. Or to have a bridge for normal WAN, one bridge for administration and one bridge for customer-internal communication. So that web-server containers can be reached from outside per http, from the management via ssh and can talk to their database via the customer network.
The scripts to set up the containers are now rendered several times instead of just one template. The scripts now contain per-container code to configure the extra veth interfaces. The default template without support for extra-veths is still rendered for the imperative containers.
Also a test is there to see if extra veths can be placed into host-bridges or can be reached via routing.
cc @edolstra @fpletz

Things done

Built on platform(s)

[ ] NixOS
[ ] OS X
[x] Linux

[x] Fits CONTRIBUTING.md.

I would rebase this PR to the current master (and have done so locally) with its updated systemd, but current master has broken containers…

@fpletz anything we can do to help move this along?

@fpletz ping?
Would be nice to get that into master before 16.09 is branched off…

Sorry for the long wait. I just had another look, let's merge this! :+1: