sysctl file should be in defaults so that it can be overriden

sysctl_file_path is currently set with set_fact in a task of /kubernetes/preinstall role
sysctl file is the default (/etc/sysctl.conf) in the /kubernetes/node role
sysctl_file_path as a default of each role (respectively set to their current value) could enable overriding through group_vars (not sure that a different name would be required...)

Just wondering when this have ever been needed? :)

What do you mean? To set sysctl configuration?

No sorry. When do you define another sysctl than /etc/sysctl.conf ? Was just wondering :)

In a file stored /etc/sysctl.d like /etc/sysctld./99-sysctl.conf in kubernetes/preinstall role.
On some(most?) systems, /etc/sysctld./99-sysctl.conf a symlink to /etc/sysctl.conf but it can be useful to have separate file in need be I guess (I actually would like to store it in a different file to avoid interfering with the settings from /etc/sysctl.conf)

@woopstar did I ruin the atmosphere with my comment? ;-)

ci check this


Is it possible to redirect from one page to another?

Hi there,
I work on the documentation team at Miracl.com. We're thinking of moving our documentation to Hugo but have a requirement for redirects to be set up from chapter pages, so users don't have to read perfunctory intro. text. Is this technically possible? If so, how would I go about doing it?
To be more specific, if say a visitor clicks on a chapter named "Registering" containing two sub-pages, one with Android instructions and one with iOS instructions, the visitor should be taken directly to the first sub-page, /registering/registering-android rather than its parent, /registering. Hope that makes sense!
Thanks,
Matt

A quick & dirty solution is:

Overriding meta.html partial in your project by creating a meta.html in your layouts/partials folder
Then, add a redirect meta tag <meta http-equiv="refresh" content="0; url=http://example.com/"/> only when the current page is a chapter.

In my opinion, creating this partial requires you to have understanding of Hugo, Go templates and this theme. For the first two, go to the official Hugo documentation, and for the third one you could check the  menu partial to see how the left menu is built.
So, it's technically possible with some tweaking, buts it's not something that will be supported in the future.
Have fun :sweat_smile:

just leaving for anyone else who finds this in a search:  seems like hugo supports aliases for this use-case: https://gohugo.io/content-management/urls/#aliases


React 17 in peerDependencies

Just a simple change to resolve warning in #139

Thank you!

@pablosichert Any chance to have this on NPM?

@pablosichert can we get this release? If you try installing the latest version with react 17 and npm@7 strict mode, you will get an invalid dependency version error. :slightly_smiling_face:

@pablosichert any chance you can release this change?


Do not crash applicatoin due to un-implemented features

ignore those events wih proper warning message

superseded by neovim/python-gui#2


How to delete account?

I want to delete employee-pulse.vercel.app account.

Hello,
As of now, we do not have the ability to delete an account by a user.
I created an assignment for this: #51
Your account will be deleted by us manually :)


Update readme

first, i switched from .md to .rst. While .md is simpler to write, I find rst worth the extra effort and it is more powerful. i am open to you disliking it @mbhall88  though, let's see!
Then, added install, usage, design and example sections,

Hmmm, let's have a discussion.
What is more "powerful" about RST? I really dislike RST. I have tried very hard in the past to use it but never found it intuitive. Markdown has always allowed me to do everything I wanted to do in the documentation.
At the same time, I am mindful that you've already written a lot in RST and don't want to make you have to rewrite it...

Yep, .md it is then


Update publishing_policy.md

updated link to Youtube channel
Signed-off-by: Paul Pindell<EMAIL_ADDRESS>

@opiproject/opi-maintainers Simple PR to update the link to the YouTube location for our videos.

@pdp2shirts please adjust the commit header according to the conventioanl commit format
config: ./.github/commitlintrc.yml
22c1418: Update publishing_policy.md

updated link to Youtube channel
Signed-off-by: Paul Pindell<EMAIL_ADDRESS>
Signed-off-by: Paul Pindell<EMAIL_ADDRESS>Error: ✖ subject may not be empty
Error: ✖ type may not be empty
Error: commitlint **failed**

Maybe fix: update publishing_policy.md?

@artek-koltun I'm not certain what you are asking for here. I'm not seeing where this should be done. there was no subject field that I remember when I created this PR.

@pdp2shirts You need to update the commit message, so it is compliant with commitlint rules.
Here's what you need to do:

Open up your terminal and navigate to the opi repo.
Run git commit --amend. This will allow to edit the commit message in your text editor.
 Here's an example of how you could rephrase it:

fix: update publishing_policy.md

updated link to Youtube channel

Signed-off-by: Paul Pindell<EMAIL_ADDRESS>

Save and close the editor. This will update the commit message.
Force push the amended commit with git push --force.

@pdp2shirts Would you like to update the commit message yourself, or would you prefer if I handle it?

I started down path to update it. But I had only used the web gui to make this PR. So I don’t have on my system the commit to be able to amend it. And I do not see an option in web gui to amend the commit. I would take instruction on how to do this, but also understand it might be simpler and faster for you to update the commit message. Paul On Jan 11, 2024, at 1:38 AM, Artek Koltun @.***> wrote:
@pdp2shirts Would you like to update the commit message yourself, or would you prefer if I handle it?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

I started down path to update it. But I had only used the web gui to make this PR. So I don’t have on my system the commit to be able to amend it. And I do not see an option in web gui to amend the commit. I would take instruction on how to do this, but also understand it might be simpler and faster for you to update the commit message. Paul On Jan 11, 2024, at 1:38 AM, Artek Koltun @.> wrote: @pdp2shirts Would you like to update the commit message yourself, or would you prefer if I handle it? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.>

@pdp2shirts please see https://github.com/opiproject/opi/pull/79

Closing as #79 covers this.


Add the ability to "inject" location into /fides.js bundles and cache responses for one hour

Closes #3170, plus unticketed work to support injecting location 👍
Code Changes

[X] Add cache-control headers to the /fides.js bundle to instruct browsers/CDNs to cache for ~1 hour
[X] Add /fides.js?location= query param to inject a given location to the bundle
[X] Add support for CloudFront location headers (e.g. CloudFront-Viewer-Country) to inject a given location to the bundle
[X] Include the injected location in the ETag for caching /fides.js bundle
[X] Add lots of tests

Steps to Confirm

[X] Run all Cypress tests
[ ] Run nox -s "fides_env(test)", load the cookie house sample app, and confirm that /fides.js bundle is cached across page refreshes

Pre-Merge Checklist

[ ] All CI Pipelines Succeeded
Documentation:

[X] documentation complete, PR opened in fidesdocs
[X] documentation issue created in fidesdocs

[X] Issue Requirements are Met
[ ] Relevant Follow-Up Issues Created:

[ ] Create issue to add API documentation for location, etc.

[ ] Update CHANGELOG.md
[X] For API changes, the Postman collection has been updated

Description Of Changes
This adds an (important!) optimization to the /fides.js route that will enable HTTP clients/CDNs/etc. to cache the results, so we don't unnecessarily hammer the Privacy Center with requests. This part was fairly easy to do, but I realized while doing this that we should bake in support for generating different bundles for different locations as early as possible- since those cache semantics are kinda hard to reason about...
So this PR also proactively adds the ability to request a fides.js bundle with an explicit location, e.g.: https://localhost:3000/fides.js?location=US-CA
☝ This will parse the query param out, and add a location property to the config object passed into the bundled initialization of Fides.js, ie. window.Fides.init({ consent, location })
This'll should enable us to set up test harnesses to exercise different locations without resorting to a lot of VPN chicanery 😄

I definitely didn't realize I had some mixing of fides.js builds from local branches! I think I fixed that now, but CI is still mysteriously cancelling/failing... hmm.


Deployment fix

Description
Please include a summary of the changes and the related issue. Please also include relevant motivation and context.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

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

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Test A
[ ] Test B

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

Legal
This project is available under the Apache 2.0 License.

just making sure the deployment AWS creds is federating https://github.com/awslabs/iot-application/actions/runs/5660904180/job/15337649064?pr=902


Mapping interface to class

Is it possible to add mapping from interface to class? For example this throws error "[NGM025] Mapping from IA1 to A2 not supported":
public class A1 : IA1
{
     public string P1 { get; set; }
}

 public interface IA1
{
     public string P1 { get; set; }
}

public class A2
{
     public string P1 { get; set; }
}

/////////////////////////////////////////////

IA1 a1 = new A1() { P1 = "P1" };
A2 a2 = a1.Map<A2>();

This is theoretically possible, but will require significant changes to the code. I will add this task to the backlog, but I cannot say that this will be done in the near future. At the moment there is almost no development going on due to my being busy at my main job.


[OpenSSL] Update 1.1.1

https://www.openssl.org/news/cl111.txt

@Evernow LGTM but if you have time could you also add missing latestReleaseDate tags for each cycle ?

Merged this, since this is a security fix release. We can add dates separately.


dupe_edge_should_err from bool to enum

Follow up to #1095.
(enum class seems to be disabled by build settings.)

Thanks! Yes, no c++11 for ninja – else it'll require c++11-compatible standard libraries, and I feel it's nice if build tools can run on older systems (unless it gets in the way too much).

This broke compilation of some perftest sources.  I've included a fix in #1060.


Apache update 6.6.0 RC1

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@fb002d8). Click here to learn what that means.
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##             master       #7   +/-   ##
=========================================
  Coverage          ?   44.45%
  Complexity        ?     2518
=========================================
  Files             ?      362
  Lines             ?    15835
  Branches          ?     1988
=========================================
  Hits              ?     7040
  Misses            ?     8090
  Partials          ?      705

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

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


Replace use of binaries for getting node information

Replaced the use of lscpu and free with reading from files of the procfs and sysfs subsystems
Tidied up the docker-networks.py file
Made compiled regex objects in load.py private to class NodeDetails and deleted debug print statements
Ran code through black

TODO:

[x] Need to figure out how to replace uptime binary.

Fix #10

This looks great!
Just a small thing. Since current CPU freq and max freq are in different, independent files and their parsing is also independent maybe they could be split into two different functions? This will also prevent the len//2 trick which seemed a bit confusing at the first look and requires too much explanation for a trivial thing. What do you think?
Also, if you found any of the API weird or confusing, feel free to let us know lol. One thing I could think of was that the get... and parse... functions are public but it does not make sense to call them separately. The only function currently being used publicly is getDetails.

That makes sense, I think if we need only max cpu freq then we won't need to read the other set of files and the whole //2 trick won't be required then.
As per the API, I could make those functions private except the getDetails. I'll raise an issue or ping on slack if there's anything else I can think of :smile:

@Samyak2 @psiayn any blockers on this?

Hi,
Sorry, I was going to test it but lost track. I'll test it and approve/merge by tonight.

Update: I tried testing but ran into a few issues with termux.
The cat command exited with SIGABRT everytime:
04/01/2021 07:15:41 PM INFO: [conn=0] Auth for user u0_a324 succeeded
04/01/2021 07:15:41 PM INFO: [conn=0, chan=0] Requesting new SSH session
04/01/2021 07:15:41 PM INFO: [conn=0, chan=0]   Command: cat "/proc/meminfo"
04/01/2021 07:15:41 PM INFO: [conn=0, chan=0] Received exit signal ABRT
04/01/2021 07:15:41 PM INFO: [conn=0, chan=0] Received channel close

Though it ran without errors in an interactive shell through SSH. I wasn't able to reproduce it until I tried running the command in an non-interactive manner like ssh -p 8022<EMAIL_ADDRESS>cat /proc/meminfo (user and IP changed):
❯ ssh -p 8022<EMAIL_ADDRESS>cat /proc/meminfo
<EMAIL_ADDRESS>password:
fdsan: attempted to close file descriptor 10, expected to be unowned, actually owned by FILE* 0x7a2ce9ed18

Looks like an issue with Termux on Android 11 [1] [2].
I'll try with a different device tomorrow.
[1] https://github.com/termux/termux-packages/issues/5790
[2] Interesting addition to Android 11: https://developer.android.com/about/versions/11/behavior-changes-all#fdsan


TopalaSoftwareSolutions.SIW version 2<IP_ADDRESS>

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

[x] Does your manifest conform to the 1.5 schema?

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

Microsoft Reviewers: Open in CodeFlow

Hi @gtopala,
This manifest adds Apps and Featues entries that aren't present in previous PR versions. Should these entries be added to the previous versions also?


Animatied transition launch render() multiple time FIX

Hello to all!
I have tried to implement your animated transitions example . It works fine, but I noticed that components from <Route exact path="/rgb/:r/:g/:b" component={RGB} /> launch render() 4 times on enter. I believe it isn't very good. I have solved this problem by adding small imporvement.
...
import { Component } from 'react';
class PreventUnexpectedReRender extends Component {
    shouldComponentUpdate = ( nextProps ) => false;

    render() {
        return this.props.children;
    }
}
...
        <TransitionGroup>
              {/* no different than other usage of
                CSSTransition, just make sure to pass
                `location` to `Switch` so it can match
                the old location as it animates out
            */}
              <CSSTransition key={location.key} classNames="fade" timeout={300}>
                <PreventUnexpectedReRender>
                  <Switch location={location}>
                    <Route exact path="/hsl/:h/:s/:l" component={HSL} />
                    <Route exact path="/rgb/:r/:g/:b" component={RGB} />
                    {/* Without this `Route`, we would get errors during
                      the initial transition from `/` to `/hsl/10/90/50`
                  */}
                    <Route render={() =>
Not Found
} />
                  </Switch>
                </PreventUnexpectedReRender>
              </CSSTransition>
            </TransitionGroup>

This will prevent it from ever re-rendering, even for legitimate reasons, which is not what we want. The extra renders are expected, as they're just how react-transition-group works.

Hello, @timdorr!
No. It will not :)
Here is test repo, sorry for not providing it right away.
As usual you should do
npm i
npm run dev
go to http://localhost:8090/
check console from History page while moving between pages.
Then remove <PreventUnexpectedReRender> from MainComponent and check console again.


CMake fails with library that uses cuda and object library

  blt_add_library(         NAME        vtkh_par         SOURCES     ${vtkh_sources} ${vtkh_par_sources} $<TARGET_OBJECTS:lodepng>         HEADERS     ${vtkh_par_headers}         DEPENDS_ON  ${vtkh_thirdparty_libs} mpi icet)
This works without CUDA, but fails when one of the thirdparty_libs is CUDA.
Call Stack (most recent call first):   blt/cmake/thirdparty/FindCUDA.cmake:1723 (CUDA_WRAP_SRCS)   blt/cmake/BLTMacros.cmake:332 (cuda_add_library)   vtk-h/CMakeLists.txt:96 (blt_add_library)
CMake Error at blt/cmake/BLTMacros.cmake:392 (get_source_file_property):   Cannot find source file:
`$<TARGET_OBJECTS:lodepng>`

Tried extensions .c .C .c++ .cc .cpp .cxx .m .M .mm .h .hh .h++ .hm .hpp   .hxx .in .txx
Call Stack (most recent call first):
vtk-h/CMakeLists.txt:96 (blt_add_library)
CMake Error at blt/cmake/thirdparty/FindCUDA.cmake:1548 (add_custom_command):   add_custom_command called with OUTPUT containing a "<".  This character is   not allowed.
Call Stack (most recent call first):   blt/cmake/thirdparty/FindCUDA.cmake:1723 (CUDA_WRAP_SRCS)   blt/cmake/BLTMacros.cmake:332 (cuda_add_library)   vtk-h/CMakeLists.txt:130 (blt_add_library)

I am pretty sure this is solved in the new object library support or is at least not necessary to do.


nzbhydra2: 7.5.0 -> 7.6.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/theotherp/nzbhydra2/releases.
meta.description for nzbhydra2 is: Usenet meta search
meta.homepage for nzbhydra2 is: https://github.com/theotherp/nzbhydra2
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 7.6.0 with grep in /nix/store/mggkmw8w5ms6y9jh8m961jmh4jivlqsz-nzbhydra2-7.6.0
found 7.6.0 in filename of file in /nix/store/mggkmw8w5ms6y9jh8m961jmh4jivlqsz-nzbhydra2-7.6.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

nzbhydra2

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/mggkmw8w5ms6y9jh8m961jmh4jivlqsz-nzbhydra2-7.6.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A nzbhydra2 https://github.com/r-ryantm/nixpkgs/archive/0592e2c9ad10433d908639e9c8f7bedaeb4bc0f9.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/0592e2c9ad10433d908639e9c8f7bedaeb4bc0f9#nzbhydra2

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/mggkmw8w5ms6y9jh8m961jmh4jivlqsz-nzbhydra2-7.6.0
ls -la /nix/store/mggkmw8w5ms6y9jh8m961jmh4jivlqsz-nzbhydra2-7.6.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

nzbhydra2

Maintainer pings
cc @matteo-pacini for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

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

@NixOS/nixpkgs-merge-bot merge


CRL support

As suggested in https://github.com/notaryproject/notation-core-go/issues/125, CRL support is required.
Here is the plan to complete CRL support based on priority:

Basic CRL support  (v1.3.0): This includes base CRL downloading and validation, with a fallback rule to automatically choose OCSP and fallback to CRL.
CRL cache support  (v1.3.0): Since CRL is a static file with relatively long-term validity, and a well-known CA's CRL is usually greater than 600KiB, a cache mechanism can significantly improve performance.
Revocation mode control  (Future): Many users may prefer to use CRL due to network or OCSP server issues. Therefore, we need to provide a way to choose the preferred revocation solution rather than a fixed rule.
Revocation network request timeout threshold control, CRL cache TTL control, and CRL cache cleaning. (Future)
Delta CRL support (Future)

@JeyJeyGao Could you move this issue to notation-go? As it's more a library issue than an external user facing one.


add support for react-strict-dom as stylex soucre

configuring the plugin as shown below doesn't seem to be sufficient.
importSources: [{ from: 'react-strict-dom', as: 'css '}]

I'm not sure what else is required to make it work.

I see what is the issue styleXTransform is not passing the importSources to  stylexBabelPlugin.
Simply forwarding the importSource and adding optimizedDeps: ["react-strict-dom"] in the config can make it work.

Thank for you report. A fix patch is pushed.

@advancedtw  v0.4.1 has been released.


Integrate Sprint #4 of Team #1

This is the pull request for the work of Team #1 in Sprint #4.
Closes: #77 #81 #114 #115 #116 #117 #118 #119 #121.

Hey I just pinned the ART version to 1.6.2 in setup.py because a new version came out in the last 24 hours which broke our notebooks. The shape of the output from attack method of the MIA attacks changed.
Once the bug with shuffling is fixed we can pin it to 1.7.1 and make sure that everything works with the new shapes.

Oh wow, thanks. Did not expect a patch version update to break code :)


Fix for checking isHexPrefixed, fixed parsing list value

Now if string is less then 2 chars - library crashed (exception), because of trying to substring of 2 characters (but string could be like "0", or "1". Proposed solution is replace it with: str.startsWith('0x');
Also, added checking for String and added possibility to parse list value to exclude exception when 'bytes' contains list.

Hmm, thank you @fedser , my mistake from re-using old lib for that function.
Regarding to the validation, bytes32 from solidity always returns as string value afaik, don't it?

@fedser anyway, it's safe 100% from now, let's rebase all to one commit to let me merge this PR, thank you so much

hi @fedser , i have not received any mess from you but there is a small issue happened, i have combined issue fix with your works into my commit, let's checkout stable version 0.0.3, thank you so much for your effort <3


no way to download a vClusters Kubeconfig using the terraform provider.

no way to download a vClusters Kubeconfig using the terraform provider.

This is a late response, but this repository is no longer maintained.
In our latest versions of vcluster, there are ways to set up your vcluster.yaml to export the kube config as well.
https://www.vcluster.com/docs/vcluster/configure/vcluster-yaml/export-kube-config


Is there any example for new network models?

Hi.
I found that the new models like face_landmark or plate detection/recognition are released in vitis ai v1.2 model zoo.
So, I want to use these models but I can't find any example for new models.
How can I use these models?
Do you have plans for updating new examples?
Thanks.

Hi @lllkiller-jlll
Please find the samples under https://github.com/Xilinx/Vitis-AI/tree/master/Vitis-AI-Library/overview/samples/


Why is the tutorial tut.c so slow?

Hi there,
I just came across this project, and started watching the tutorial video, and built all the required libraries and tut.c, and once I got it working, decided to do some simple timing tests, and it seems really slow:
[root@324dfa1f2214 lsquic-tutorial]# ./tut -c mycert-cert.pem -k mycert-key.pem <IP_ADDRESS> 12345 &
[root@324dfa1f2214 lsquic-tutorial]# time echo hi | ./tut <IP_ADDRESS> 12345 >& /dev/null

real	0m0.068s
user	0m0.007s
sys	0m0.003s

[root@324dfa1f2214 lsquic-tutorial]# time cat tut.c | ./tut <IP_ADDRESS> 12345 >& /dev/null

real	0m0.578s
user	0m0.203s
sys	0m0.252s

Is this to be expected, or am I doing something wrong here?

I'd expect it to be slow due to this code:
/* Read one byte at a time -- when user hits enter, send line to server */
static void
tut_read_stdin (EV_P_ ev_io *w, int revents)

In addition, you will notice that each line is a request to the server.  You're making 1418 requests to the server in the second example.  I'd say finishing in under 600ms is not too bad.  :slightly_smiling_face:


closing channel stuck in waiting_close status

perhaps related to https://github.com/lightningnetwork/lnd/issues/4608
I opened several channels with no issue. After some time, I decided to do some closing, but, after running
lncli closechannel chanpoint
terminal command got stuck, I mean prompt never returned, so after a while I had to ctrl C the terminal.
Now the channel is showing in
lncli pendingchannels
as waiting_close for days
tried restarting lnd several times but the issue persist
also, I tried to close another channel via
lncli closechannel chanpoint
and the prompt is stuck again
Your environment
v0.11.0-beta
4.15.0-112-generic #113-Ubuntu x86_64 x86_64 x86_64 GNU/Linux
NEUTRINO
Steps to reproduce
just lncli closechannel any channel
Expected behaviour
channel should close
Actual behaviour
terminal prompt stucked, channel stucked in waiting close state
edit: I can only close channels via --force

I think this is actually a noob mistake ... I don't remember if I had enough wallet balance  for the closing tx


cannot delete addresses in manage profile

reproduce: delete the address -> check button -> go back, it's still there

mis-report


“JAVA_HOME”  "  different quote

I have been following the C# storm topology github https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/hdinsight/storm/apache-storm-develop-csharp-visual-studio-topology.md
The quotation symbol really trapped me for hours - you can now see they are NOT left or right curled and NOT the regular " ==>
string javaHome = Environment.GetEnvironmentVariable(“JAVA_HOME”);
Visual studio kept give me JAVA_HOME not found in my context errors.
I never realised those exists and they kept give me JAVA_HOME can't be found... until i tried to replace to single ' and then " .
It really took me hours to fix this.
Azure documentation issue guidance
Thanks for opening an issue in the Azure technical documentation repository.
We use GitHub issues as the primary channel for customer and community feedback about the Azure documentation.
Creating an issue
We prefer that you create documentation feedback issues using the Feedback link on the published article - the feedback control on the doc page creates an issue that contains all the article details so you can focus on the feedback part.
You can also create a feedback issue here in the repo. If you do this, please make sure your issue lists:

[ ] The relevant Azure service or technology.
[ ] A link to the published documentation article that you have feedback about.
[ ] Clear, specific feedback that the author can act on.

Pull requests and article contributions
If you know the change that is needed in an article, we encourage you to submit the changes directly using a pull request. If the change is large, or if you want to contribute an entire article, follow these guidelines:

[ ] Don't surprise us with a big pull request or a pull request with a new article! Submit an issue that describes the details of the proposed large change or new article.
[ ] Include the service or technology area.

We'll route the issue to the appropriate content team for review and discussion.
Tech support and product feedback
If you would like to contact Microsoft about other things, such as product feedback or tech support, please review these guidelines:

If you need technical support using Azure, the paid and free support options are described here: https://azure.microsoft.com/support/options/.

Each article in the Azure technical documentation contains a product feedback button - it's best to submit product feedback directly from a relevant article. Otherwise, you can submit product feedback for most Azure products in the following product feedback forum: https://feedback.azure.com/forums/34192--general-feedback.

@rhpoon Sorry for the hours of troubleshooting.
I have updated the smart quotes “xyz” and replaced with straight quotes "xyz". Hope that is the right fix. I expect it will publish this afternoon.
Thanks, Jason


Used the instructions from this repo but can't run docker in workspace

Bug description
hello i followed the instructions on installing on eks using this repo,
everything works as it's supposed to be but when i try custom image on .gitpod.yml or simply run a "docker run -ti ubuntu" on the workspace terminal, i got this error :
docker: Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: rootfs_linux.go:76: mounting "proc" to rootfs at "/proc" caused: mount through procfd: operation not permitted: unknown.
ERRO[0004] error waiting for container: context canceled
i tried rebuilding the builder image with different tags but can't make it work :'(
Steps to reproduce
make install this repository then create a workspace and try to run a container
Expected behavior
container starts and can use custom images on workspace
Example repository
have the issue with this repo:
https://github.com/gitpod-io/template-docker-compose
Anything else?
No response

I am having similar issues running anything in Docker after deployment (installed 2 days ago at 442119fca4c2ee7cefe57e2057be5ffee6256fdf using the west-2 region's AMI "ami-0a9aa973650d0c831"). Tried with both the latest workspace-full base having Docker v20.* and older tags having Docker v19.*.
Here is my comment with the exact outputs on the Docker v20 issue, https://github.com/gitpod-io/gitpod/issues/3051#issuecomment-932460520

@szab100 I need to release a new version of the AMI and gitpod images. The procfd mount issue is already fixed in main.
I hope I can release an update next week. (I am swamped right now)

@aledbf Thank you for the quick reply! Next week would be awesome, but sure I understand you are super busy. One additional note for this is that I have also tried to run minikube / k3s / kind inside the workspace (on saas gitpod.io as docker doesn't work on my aws install), and those are failing with mount issues similar to the procfd with podman above:
mounting "cgroup" to rootfs at "/sys/fs/cgroup" caused: operation not permitted: unknown.
Can this be because of some missing securityContext capabilities on the ws-<..> pod, eg SYS_ADMIN? I know it is a whole different story than what this bug is about.. one of our projects has argo workfows as a dependency and my colleague is going to give a speech on KubeCon about it.. It would be nice to give the project GitPod support (on gitpod.io, not our aws deployment), so interested developers could quickly have a dev environment up & running.. but most probably this can't happen as KubeCon is less than 2 weeks away..
Either way, we need this to get fixed regardless of KubeCon, and even if local k8s support won't be possible, this docker issue is blocking us from proposing gitpod as a (self-hosted) cloud-ide solution at the company.

One additional note for this is that I have also tried to run minikube / k3s / kind inside the workspace

This is still not possible. Please follow https://github.com/gitpod-io/gitpod/issues/4889
Some of the restrictions are related to the user namespace where the workspace run. Please check the feature description

and those are failing with mount issues similar to the procfd with podman above:

Right now containerd is a hard requirement and there is no support for podman.

Thank you @aledbf, Lorenzo's workaround from this issue helped me a lot! I made a fork where the initial workspace build time is greatly reduced by using a pre-baked middle-layer workspace image that has QEMU installed and the initial VM root filesystem fully baked.
Certainly not perfect, mostly b/c qemu is slow to start and has quite a big overhead (it can only run in full sw-emulation mode, it would need '/dev/kvm' passthrough from the node), but seems to be a great workaround for running a local k8s cluster, until we can get full support for 'kind'.
Hope to see your fixes for Docker on the AWS deployment soon. Thanks!

Do you mean traffic from inside the VPC?

Yes, the internal LB / ingress is having assgined IPs from the cluster's VPC subnets of each AZs. I needed to add the VPC's overall CIDR (<IP_ADDRESS>/16 in my case) into LoadBalancerSourceRanges or directly to its SecurityGroup to let the pods reach it.
OK sure I understand if websockets have issues through LBs, while I personally had no such issues. If the connection drops are limited to Ingress changes, I think that's normal and should be expected, providing reasonable client-side resiliency should be enough to handle those. But I understand there could be various issues with other providers' exotic ingress controllers that can cause bigger disruptions.
Still, even just mentioning this alternative deployment option as a less- or not-supported one might help increasing adoption, in case people are not allowed to expose NodePorts on their clusters directly due to internal policies. So far everyone else I have seen from the community experimenting with ingresses with Gitpod eventually gave up and it took me several days to come up with this workaround. So let me know if you guys need any more details, I am happy to share more details or contribute with a howto (even the CoreDNS part is very simple, just editing a configmap).

Hi @aledbf, going back to the original topic in this issue, can we have a fix for this? I track the new installer's milestone, but it progresses slowly.. which is fine for something new, but this is an important feature that is currently broken on AWS installs.. and if I understood correctly, it has nothing to do with the installer itself, but the used AMI images & possibly ws pods configuration instead. I was planning to showcase Gitpod self-hosted on our bi-annual hackathon week and push for company-wide adoption, but this seems to be a major blocker. I see others are waiting for this as well.

@szab100 last week we merged the refactoring I mentioned in a previous comment https://github.com/gitpod-io/gitpod/pull/6462
With this change, we reduced the median startup time by half and got instant port exposure (no more waiting because “port was not found”) and massively reduced load on the API server.
About the original issue, we need to release a new version. That's it. The problem is the self-hosted release implies too apply too many changes, and the reason why we need to wait for the installer. Right now, the installer is running for GKE with internal dependencies. By the end of the week will be ready for external ones (registry and DB). With that done, the idea is to update the EKS and AKS guides.
I am sorry for the delay. We cannot tackle all the fronts simultaneously.

@aledbf Awesome, no worries, thank you for the quick update! I love to see there is progress, sorry I just could not connect these pieces like you just did, it makes complete sense now and I cant wait to see these performance improvements as well. So you are saying GCP might be completed this week. Hope it's relatively quick to adapt it to EKS thereafter.


Can't call source from submap correctly

Hyprland Version
 System/Version info
Hyprland, built from branch main at commit 94d6b2d2c12663efe90f6d0410528b0d7bcc671e dirty (deco: fix missing border on togglefloating (4305)).
Date: Sat Dec 30 09:59:01 2023
Tag: v0.33.1-117-g94d6b2d2

Bug or Regression?
Bug
Description
I am trying to do nested submaps while also calling source from within said submaps, but it seems that the source lines get called at runtime and don't live within the submaps. At first I tried doing nested submaps where I had one submap, "layout", that then had three submaps in it, one for setting dwindle, one for master, and another for hy3- each with their own set of keybinds for each layout. I tried putting the source line inside that submap with the thinking being that it would just be called when the submap was entered, but I guess that's not how it works. I also tried to see if I could call the source with a hyprctl and exec but I'm obviously missing something here.
tl;dr- I'm trying to be able to switch between layouts using keybinds and submaps, as well as loading a set of keybinds with each layout switch, but can't figure it out.
How to reproduce
Here's the relevant part of my config:
(simplified with just a dwindle example)
bind = $mainMod SHIFT, code:59, exec, hyprctl notify 0 3000 0 "submap:layout"
bind = $mainMod SHIFT, code:59, submap, layout
submap = layout

bind = , D, exec, hyprctl --batch "notify 0 3000 0 "submap:dwindle"; keyword general:layout dwindle; dispatch source ./conf/hy3.conf"
>>>>> I tried doing many variations of the following lines without success:
>>>source ./conf/dwindle.conf
>>>exec source ./conf/dwindle.conf
>>>exec source = ./conf/dwindle.conf
bind = , D, submap, reset

# bind = , escape, exec, hyprctl notify 1 3000 0 "submap: return to normal"
bind = , escape, submap, reset
submap = reset

Crash reports, logs, images, videos
No response

source is evaluated at parse and this cannot be changed. Your option is to dynamically call hyprctl dispatch source ... or modify the files themselves

hypdrctl dispatch source returns "Invalid dispatcher". Is it possible to pass a keybind using hyprctl?

or is it possible to have arguments passed within hyprland.conf?

Try hyprctl keyword source 'path/to/be/sourced'.

That worked! Here's what I ended up with:
general {
    gaps_in = 5
    gaps_out = 15
    border_size = 3
    col.active_border = $color11
    col.inactive_border = rgba(ffffffff)
    col.active_border = rgba(33ccffee) rgba(00ff99ee) 45deg
    col.inactive_border = rgba(595959aa)
    layout = dwindle
}
source = ./conf/dwindle.conf

bind = $mainMod SHIFT, code:59, exec, hyprctl notify 0 3000 0 "submap:layout"
bind = $mainMod SHIFT, code:59, submap, layout
submap = layout

bind = , D, exec, hyprctl --batch "notify 0 3000 0 "submap:dwindle"; keyword general:layout dwindle; keyword source ./conf/dwindle.conf"
bind = , D, submap, reset
bind = , M, exec, hyprctl --batch "notify 0 3000 0 "submap:Master"; keyword general:layout master; keyword source ./conf/master.conf"
bind = , M, submap, reset
bind = , N, exec, hyprctl --batch "notify 0 3000 0 "submap:hy3"; keyword general:layout hy3; keyword source ./conf/hy3.conf"
bind = , N, submap, reset

bind = , escape, exec, hyprctl notify 1 3000 0 "submap: cancel"
bind = , escape, submap, reset

submap = reset

And that lets me hop around the layouts with their own separate configs. Now if only we could have separate layouts per monitor lol

just kidding now I've actually tested it and this is what worked:
bind = $mainMod SHIFT, code:59, exec, hyprctl notify 0 3000 0 "submap:layout"
bind = $mainMod SHIFT, code:59, submap, layout
submap = layout

bind = , D, exec, hyprctl --batch "notify 0 3000 0 "submap:dwindle"; keyword general:layout dwindle"
bind = , D, exec, hyprctl keyword source ~/dotfiles/hypr/conf/dwindle.conf
bind = , D, submap, reset
bind = , M, exec, hyprctl --batch "notify 0 3000 0 "submap:Master"; keyword general:layout master"
bind = , M, exec, hyprctl keyword source ~/dotfiles/hypr/conf/master.conf
bind = , M, submap, reset
bind = , N, exec, hyprctl --batch "notify 0 3000 0 "submap:hy3"; keyword general:layout hy3"
bind = , N, exec, hyprctl keyword source ~/dotfiles/hypr/conf/hy3.conf
bind = , N, submap, reset

bind = , escape, exec, hyprctl notify 1 3000 0 "submap: cancel"
bind = , escape, submap, reset

submap = reset

hyprctl didn't want to call the file inside the batch operation so I just added an additional bind to each key.


Fix readme headers and article link on npmjs.com

Fixes the issue described here: https://stackoverflow.com/questions/31907314/markdown-headers-not-displayed-correctly-in-npm
Old:

New should match they way Github renders Markdown headers:

@dsernst Thanks for the pull request to fix the doc's.   I appreciate it; and I learned something new.  Must have a space between the # and the text...

:smile:


Introduce general auth abstraction

This PR implements a general auth abstraction so that the hypercore's sign and verify operations may be redefined.
This allows various auth structures, some examples being:

Multisignature cores
Proof-of-Work cores

Looks great

@chm-diederichs i think you're missing a b4a require, looking at ci

New to hypercore and I'm wondering if using multisignature would be a better alternative to autobase for achieving multiwriter support.
My access control would be:

Use block encryption to control read access
Use key pairs to control write access, and only the owner can issue a new key pair

So I only have to manage the key pairs that are allowed to write to each core instead of so many hypercores for each writer. For example, I can use a master hyberbee to store all the user's hypercores and the public keys that can sign them. This seems much easier than using autobase and having to manage separate hypercores for each peer/device.
What would be the downside of doing it this way?

@omarbadran You would end up with the conflicts, since writers could independently append to the same core, resulting in two separate merkle trees for the same core. (eg. if writers append while being offline).
This would cause replication to fail unless you implemented additional logic to coordinate/resolve these conflicts. Autobase was designed to solve this problem, by automatically rebasing writers' cores to linearise them. Using autobase patterns for multiwriter would save you a lot of complexity in the long run.
This PR is more useful for specific use cases, eg. N-of-N multisignature cores (this ensures that consensus is reached before an append is even possible, mitigating the risk of forks).

@chm-diederichs Yeah that makes sense. I did not think about the conflicts in a more complex setup.
Thanks for working on this, I have never been motivated to learn about something like this before. Hypercore have so much potential and I'm sure it will reshape our future.


Discriminated Union inside Discriminated Union

I am trying to write a schema for the below type

type Bill = {
  billDate: string;
  billId: number;
  name: string;
  balance: number;
};

type MonthType = 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12;

type InvoiceDateType =
  | { isPartial: 0; invoiceMonth: 0; invoiceYear: 0 }
  | { isPartial: 1; invoiceMonth: MonthType; invoiceYear: number };

export type InvoiceType = Bill &
  (
    | ({ type: "Invoice"; invoices: number } & InvoiceDateType)
    | {
        type: "Payment";
        paymentsAndCredits: number;
        isPartial: 0 | 1;
        invoiceMonth: MonthType;
        invoiceYear: number;
      }
  );

I am stuck here.
const billSchema = z.object({
  billDate: z.string(),
  billId: z.number(),
  name: z.string(),
  balance: z.number(),
});

const monthSchema = z.union([
  z.literal(1),
  z.literal(2),
  z.literal(3),
  z.literal(4),
  z.literal(5),
  z.literal(6),
  z.literal(7),
  z.literal(8),
  z.literal(9),
  z.literal(10),
  z.literal(11),
  z.literal(12),
]);

const invoiceDateSchema = z.discriminatedUnion("isPartial", [
  z.object({
    isPartial: z.literal(0),
    invoiceMonth: z.literal(0),
    invoiceYear: z.literal(0),
  }),
  z.object({
    isPartial: z.literal(1),
    invoiceMonth: monthSchema,
    invoiceYear: z.number(),
  }),
]);

const invTypeSchema = z.intersection( // I tried .and operator also
  z.object({
    type: z.literal("Invoice"),
    invoices: z.number(),
  }),
  invoiceDateSchema,
);

const invoiceTypeSchema = z.discriminatedUnion("type", [
  invTypeSchema, // this always gives me error
  z.object({
    type: z.literal("Payment"),
    paymentsAndCredits: z.number(),
    isPartial: z.union([z.literal(0), z.literal(1)]),
    invoiceMonth: monthSchema,
    invoiceYear: z.number(),
  }),
]);

export const invoiceSchema = billSchema.extend(invoiceTypeSchema); // still gives error

Unfortunately, discriminatedUnion only supports 1 discriminator. You could try using a regular union instead. Or perhaps trying something like this:
const schema = z.discriminatedUnion( 'type', [
    z.object( {
        type: z.literal( 'PartialInvoice' ),
    } ),
    z.object( {
        type: z.literal( 'Invoice' ),
    } ),
    z.object( {
        type: z.literal( 'PartialPayment' ),
    } ),
    z.object( {
        type: z.literal( 'Payment' ),
    } ),
] )

If you found my answer satisfactory, please consider supporting me. Even a small amount is greatly appreciated. Thanks friend! 🙏
https://github.com/sponsors/JacobWeisenburger


Feature print edit file

Editing hello.py

Build Succeded :)
You can proceed to merge the branch now


Add a deserialization warning about Pickle in vocab files in some models to the security guide

https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md
have no any mentions that models often have Pickle files attached like vocabs.
These files should be validated before running. An exploit example is available here: https://gist.github.com/mgeeky/cbc7017986b2ec3e247aab0b01a9edcd

This has too many conflicts. Please resolve and merge to master.


Updates for MariaDB 10.3 Series

I see the docs state MariaDB 10.3.23 as the supported version. Aaccording to https://mariadb.com/kb/en/release-notes-mariadb-103-series/ that was released two years ago and the current patch is 10.3.34.
When will the latest MariaDB version be supported by Azure?

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

ID: 2f5e4798-d1ea-e82b-0459-2e268387152d
Version Independent ID: 1bb7d77d-0b97-3190-ea91-9a10a014eefc
Content: Supported versions - Azure Database for MariaDB
Content Source: articles/mariadb/concepts-supported-versions.md
Service: mariadb
GitHub Login: @savjani
Microsoft Alias: pariks

The past several patches in the 10.3.x series have contained fixes for known security vulnerabilities, and the upcoming 10.3.35 contains even more. Not to mention bugfixes over the past 2 years.

Thanks for reporting this. I have assigned the issue to the content author to investigate further and update the document as appropriate.

Any update on this?

#reassign: @markingmyname

Hi, @dylemma.
First, we apologize for the delay in response.
We appreciate your interest in using a Maria DB server deployed in Azure.
However, one of the reasons for the delay is that we discussed the plan for when new patches would be applied.
As of today, the article is still current. The latest patch we support is 10.3.23. We are aware that there are later patches and the request to apply the new patches to the Azure Database for the Maria DB service has been a common ask. Unfortunately, due to other priorities, there will be a delay in applying later patches.

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion, and we will reopen the issue. To ask a question directly to our Q&A environment, please visit https://docs.microsoft.com/en-us/answers/support/ for more information on asking questions about the product or service.
Thank you.
#please-close


Token doesn't match specifier '%d'

I am not able to parse the custom logs using goaccess and I am getting following error while parsing.
Token<EMAIL_ADDRESS>207 repo' doesn't match specifier '%d'
Command I have used.
goaccess /home/ubuntu/load-analysis_svn-cache-svn.log -o /home/report.html --log-format='COMBINED'
Log File:
[2022-09-29 10:53:21.353073 +0200]<EMAIL_ADDRESS>207 repo:/var/www/repos/gtup get-inherited-props /libs/JC6_HMI/tags/BLD-JC6_HMI-1.0.0-025/out r32395 (216 Bytes in 0 Sec)
[2022-09-29 10:53:21.357983 +0200]<EMAIL_ADDRESS>207 repo:/var/www/repos/gtup checkout-or-export /libs/JC6_HMI/tags/BLD-JC6_HMI-1.0.0-025/out r32395 (600 Bytes in 0 Sec)

Could you please specify what’s the client ip? Also, I assume no user agent nor referrer…

Following client IP
<EMAIL_ADDRESS>207 which tying to checkout the repository code.

Hello, Could you please provide the information how can I parse the custom logs  ?

Untested but please try this:
goaccess access.log log-format=‘[%d %t.%^] %e@%h %s %^ %U %^ %v %M (%b %^ %^ %T%^)’ date-format=%Y-%m-%d time-format=%T

Closing this. Feel free to reopen it if needed.


Using Proper MariaDB Versions

Supported MariaDB versions are 10.2 and 10.3 : https://docs.microsoft.com/en-us/azure/mariadb/concepts-supported-versions. But the files contain MySQL versions 5.6 and 5.7 - hence replacing with the right versions for MariaDB.
Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[x] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

/azp run automation - sdk

Can one of the admins verify this patch?

/azp run automation - sdk

/azp run automation - sdk


Document database usage

Write a small paragraph/bullet points on how the chat has been used so far.
Use the database to look for information. Send this to Hera by 11/4

relates #182

Add useful queries when doing this to the readme to save further work in the future

Document created in sheets.
Queries used are nothing special so not adding to README.
select * from messages;
select * from conversations; /* shows number of conversations */
select * from messages where conversation_id = numberHere; /* useful to read individual conversations */


Request to add support for tiling presets

Note - Need to add GET /libraries/tiling to properties, then add logic to add that result to POST /projects/{projectid}/products/tiled request when creating tiled products.

Added in https://github.com/tilialabs/tilia-phoenix-connect/commit/ed61d7f02d5d649973b21c9fcf2a0253078118b8


Mirrors config migration should not modify user's file

Motivation:
The migration from .swiftpm/config to .swiftpm/configuration/mirrors.json moves .swiftpm/config and leads user to think that the file gets deleted. (rdar://85917746)
Modifications:

Copy .swiftpm/config to .swiftpm/configuration/mirrors.json instead of moving it.
Emit warning that .swiftpm/config has been deprecated.
Don't perform the migration if .swiftpm/configuration/mirrors.json already exists to prevent error. (rdar://85917836)

@swift-ci please smoke test


Accessing session scope?

I really can't wait until they enable discussions in this repo.
This is just a question. Is there a preferred way of accessing and setting session information in components? Reason being is that while porting over some partials, we had some logic in the partial for keeping tracking of rendering that we would keep in the session of the user. This made it very easy to reuse the partials in other areas of the site. When accessing the session from a component, it will throw an error. Any ideas or is this something that components shouldn't do?

@ultrawebmarketing for our internal components, we generally try to avoid having components use state that is not explicitly passed into them. Doing so makes them easier to unit test and to reuse in different views / outside the request path.
You may be able to get the behavior you want using the helpers. escape hatch, which allows you to make a method call in the containing view context.
But I'm not sure if this helps or not, as I'm having a hard time imaging the code you're describing. Perhaps you could provide and example?

An example... We have a component that displays a set of tabs. This component can be used in multiple areas of the site. Now what we want to do is save which tab is active so that if the user comes back to that page, the tab that was active, is active again and not the default tab, thus we store the active tab in a session. Yeah, we probably could do this stuff in the controller and pass the active_tab as a parameter to the component, it just makes using the easier when you don't have to think about that :)

@ultrawebmarketing you're correct that you could pass that in from the controller. What if you instead had it at the callsite?
Something like:
render(MyTabNav.new(current_tab: session[:current_tab])
That way, you are reducing your coupling to the potential values of session[:current_tab], not all of session.

while that will work for retrieving, it's the setting which is the main part. for instance, in the partial i have:
session['active_tabs'] ||= {}
session['active_tabs'][ params[:customer_id] ] = ''
if params[:active_tab].present?
  session['active_tabs'][ params[:customer_id] ] = params[:active_tab]
end
active_tab = session['active_tabs'][ params[:customer_id] ]

so now I can not only get the active_tab but also set it without having any external code.

@ultrawebmarketing I see. That's generally the kind of logic we'd put in a controller.
But for the sake of migrating, you should be able to use helpers.session and helpers.params to make this work. It will just be tricky to unit test.

Closing.


refactor: Message class

This pull request refactors the Message class to use the RESTPostAPIChannelMessageJSONBody type when replying and instead of taking id, content, guild, channel etc in the constructor it now takes a data argument of  APIMessage and the client.

Are we sure we want to take a raw JSON body for the reply parameter instead of any further abstraction?

Are we sure we want to take a raw JSON body for the reply parameter instead of any further abstraction?

That's kind of out of the scope of this.

Are we sure we want to take a raw JSON body for the reply parameter instead of any further abstraction?

That's kind of out of the scope of this.

- public async reply(content: string) {
+ public async reply(payload: RESTPostAPIChannelMessageJSONBody) {

Is it?

Are we sure we want to take a raw JSON body for the reply parameter instead of any further abstraction?

That's kind of out of the scope of this.

- public async reply(content: string) {
+ public async reply(payload: RESTPostAPIChannelMessageJSONBody) {

Is it?

We would need to make a new class for it, maybe MessageResponse?

Are we sure we want to take a raw JSON body for the reply parameter instead of any further abstraction?

That's kind of out of the scope of this.

- public async reply(content: string) {
+ public async reply(payload: RESTPostAPIChannelMessageJSONBody) {

Is it?

We would need to make a new class for it, maybe MessageResponse? Though to reply we would need to use <Message>.reply(new MessageResponse()) Or we could make an interface for it.
Without abstraction it looks like this
client.on('message', (message: Message) => {
	if (message.content === 'test message')
		void message.reply({
			content: 'pong!'
		});

	if (message.content === 'test embed')
		void message.reply({
			embeds: [
				{
					description: 'hey an embed'
				}
			]
		});
});

Interface feels a lot more rational then dedicating a class to it (Imagine how much extra overhead we'd have to add for all of the methods!)
I'm wondering if we want to follow the api's snake_case conventions considering this is a JS library or if we want to further abstract it and handle converting the properties ourselves. Just a thought though because using the raw API does make this a lot simpler.


Linux 4.14 breakage tracking issue

Here is the list of packages that broke after the switch to 4.14 (https://github.com/NixOS/nixpkgs/commit/bfe9c928c18583d3adfb5978a55b48c392649ef5), which was reverted back to 4.9 in eb85eb5c738701f7c2b0ce32250d09bf0ff00325.

[ ] linuxPackages_4_14.amdgpu-pro
[x] linuxPackages_4_14.mwprocapture (ce8dea6bdd18846579d32d0bcec94717bf616b41)
[ ] linuxPackages_4_14.nvidia_x11 (#31148)
[ ] linuxPackages_4_14.nvidia_x11_beta
[ ] linuxPackages_4_14.nvidia_x11_legacy304
[ ] linuxPackages_4_14.nvidia_x11_legacy340
[ ] linuxPackages_4_14.openafsClient
[ ] linuxPackages_4_14.virtualbox (#31037)
[ ] linuxPackages_4_14.virtualboxGuestAdditions
[ ] ZFS test nix-build nixos/tests/installer.nix -A zfsroot after setting linuxPackages = linuxPackages_4_14 in all-packages.nix (see #31615)

Probably the two legacy packages may be restricted to older kernels, and the others should be fixed.

I need help in #31037, that should take care of VirtualBox

I have been trying to get amdgpu-pro fixed for a little while now but I think it does require an update from AMD's side for kernel 4.14.x
Or it's because I don't know make too well, the build errors out like so:
  CC [M]  /tmp/nix-build-amdgpu-pro-17.40-4.14.drv-0/amdgpu-pro-17.40-492261/root/usr/src/amdgpu-17.40-492261/amd/amdkfd/kfd_crat.o
  CC [M]  /tmp/nix-build-amdgpu-pro-17.40-4.14.drv-0/amdgpu-pro-17.40-492261/root/usr/src/amdgpu-17.40-492261/amd/amdkfd/kfd_rdma.o
  CC [M]  /tmp/nix-build-amdgpu-pro-17.40-4.14.drv-0/amdgpu-pro-17.40-492261/root/usr/src/amdgpu-17.40-492261/amd/amdkfd/kfd_peerdirect.o
  CC [M]  /tmp/nix-build-amdgpu-pro-17.40-4.14.drv-0/amdgpu-pro-17.40-492261/root/usr/src/amdgpu-17.40-492261/amd/amdkfd/kfd_ipc.o
  CC [M]  /tmp/nix-build-amdgpu-pro-17.40-4.14.drv-0/amdgpu-pro-17.40-492261/root/usr/src/amdgpu-17.40-492261/amd/amdkfd/kfd_debugfs.o
  LD [M]  /tmp/nix-build-amdgpu-pro-17.40-4.14.drv-0/amdgpu-pro-17.40-492261/root/usr/src/amdgpu-17.40-492261/amd/amdkfd/amdkfd.o
make[2]: *** [/nix/store/prk1nwg5s1619jbrpp67v5jr3xpv7347-linux-4.14-dev/lib/modules/4.14.0/source/Makefile:1503: _module_/tmp/nix-build-amdgpu-pro-17.40-4.14.drv-0/amdgpu-pro-17.40-492261/root/usr/src/amdgpu-17.40-492261] Error 2
make[1]: *** [Makefile:146: sub-make] Error 2
make: *** [Makefile:24: __sub-make] Error 2
make: Leaving directory '/nix/store/prk1nwg5s1619jbrpp67v5jr3xpv7347-linux-4.14-dev/lib/modules/4.14.0/build'
note: keeping build directory ‘/tmp/nix-build-amdgpu-pro-17.40-4.14.drv-1’
builder for ‘/nix/store/z5q0c0q0gqd02skgxh94wgiccpx3jsc8-amdgpu-pro-17.40-4.14.drv’ failed with exit code 2
error: build of ‘/nix/store/z5q0c0q0gqd02skgxh94wgiccpx3jsc8-amdgpu-pro-17.40-4.14.drv’ failed

Re. make you have posted Error 2, a secondary error. The actual cause of the failure is Error 1 somewhere above.

Working on mwprocapture now
Also, with PR #31148 nvidia_x11 builds and works successfully, on my end

@orivej Ah, I had to scroll WAY up :)
It looks bad (to the untrained eye :D)...
/tmp/nix-build-amdgpu-pro-17.40-4.14.drv-0/amdgpu-pro-17.40-492261/root/usr/src/amdgpu-17.40-492261/include/kcl/kcl_drm.h:271:29: error: incompatible type for argument 7 of 'drm_universal_plane_init'
      formats, format_count, type, name);
                             ^~~~
In file included from /nix/store/prk1nwg5s1619jbrpp67v5jr3xpv7347-linux-4.14-dev/lib/modules/4.14.0/source/include/drm/drm_crtc.h:45:0,
                 from /nix/store/prk1nwg5s1619jbrpp67v5jr3xpv7347-linux-4.14-dev/lib/modules/4.14.0/source/include/drm/drmP.h:69,
                 from /tmp/nix-build-amdgpu-pro-17.40-4.14.drv-0/amdgpu-pro-17.40-492261/root/usr/src/amdgpu-17.40-492261/include/kcl/kcl_drm.h:6,
                 from /tmp/nix-build-amdgpu-pro-17.40-4.14.drv-0/amdgpu-pro-17.40-492261/root/usr/src/amdgpu-17.40-492261/amd/amdkcl/kcl_drm.c:1:
/nix/store/prk1nwg5s1619jbrpp67v5jr3xpv7347-linux-4.14-dev/lib/modules/4.14.0/source/include/drm/drm_plane.h:548:5: note: expected 'const uint64_t * {aka const long long unsigned int *}' but argument is of type 'enum drm_plane_type'
 int drm_universal_plane_init(struct drm_device *dev,
     ^~~~~~~~~~~~~~~~~~~~~~~~
In file included from /tmp/nix-build-amdgpu-pro-17.40-4.14.drv-0/amdgpu-pro-17.40-492261/root/usr/src/amdgpu-17.40-492261/amd/amdkcl/kcl_drm.c:1:0:
/tmp/nix-build-amdgpu-pro-17.40-4.14.drv-0/amdgpu-pro-17.40-492261/root/usr/src/amdgpu-17.40-492261/include/kcl/kcl_drm.h:271:35: error: incompatible type for argument 8 of 'drm_universal_plane_init'
      formats, format_count, type, name);
                                   ^~~~
In file included from /nix/store/prk1nwg5s1619jbrpp67v5jr3xpv7347-linux-4.14-dev/lib/modules/4.14.0/source/include/drm/drm_crtc.h:45:0,
                 from /nix/store/prk1nwg5s1619jbrpp67v5jr3xpv7347-linux-4.14-dev/lib/modules/4.14.0/source/include/drm/drmP.h:69,
                 from /tmp/nix-build-amdgpu-pro-17.40-4.14.drv-0/amdgpu-pro-17.40-492261/root/usr/src/amdgpu-17.40-492261/include/kcl/kcl_drm.h:6,
                 from /tmp/nix-build-amdgpu-pro-17.40-4.14.drv-0/amdgpu-pro-17.40-492261/root/usr/src/amdgpu-17.40-492261/amd/amdkcl/kcl_drm.c:1:
/nix/store/prk1nwg5s1619jbrpp67v5jr3xpv7347-linux-4.14-dev/lib/modules/4.14.0/source/include/drm/drm_plane.h:548:5: note: expected 'enum drm_plane_type' but argument is of type 'const char *'
 int drm_universal_plane_init(struct drm_device *dev,
     ^~~~~~~~~~~~~~~~~~~~~~~~
In file included from /tmp/nix-build-amdgpu-pro-17.40-4.14.drv-0/amdgpu-pro-17.40-492261/root/usr/src/amdgpu-17.40-492261/amd/amdkcl/kcl_drm.c:1:0:
/tmp/nix-build-amdgpu-pro-17.40-4.14.drv-0/amdgpu-pro-17.40-492261/root/usr/src/amdgpu-17.40-492261/include/kcl/kcl_drm.h:270:10: error: too few arguments to function 'drm_universal_plane_init'
   return drm_universal_plane_init(dev, plane, possible_crtcs, funcs,
          ^~~~~~~~~~~~~~~~~~~~~~~~
In file included from /nix/store/prk1nwg5s1619jbrpp67v5jr3xpv7347-linux-4.14-dev/lib/modules/4.14.0/source/include/drm/drm_crtc.h:45:0,
                 from /nix/store/prk1nwg5s1619jbrpp67v5jr3xpv7347-linux-4.14-dev/lib/modules/4.14.0/source/include/drm/drmP.h:69,
                 from /tmp/nix-build-amdgpu-pro-17.40-4.14.drv-0/amdgpu-pro-17.40-492261/root/usr/src/amdgpu-17.40-492261/include/kcl/kcl_drm.h:6,
                 from /tmp/nix-build-amdgpu-pro-17.40-4.14.drv-0/amdgpu-pro-17.40-492261/root/usr/src/amdgpu-17.40-492261/amd/amdkcl/kcl_drm.c:1:
/nix/store/prk1nwg5s1619jbrpp67v5jr3xpv7347-linux-4.14-dev/lib/modules/4.14.0/source/include/drm/drm_plane.h:548:5: note: declared here
 int drm_universal_plane_init(struct drm_device *dev,
     ^~~~~~~~~~~~~~~~~~~~~~~~
In file included from /tmp/nix-build-amdgpu-pro-17.40-4.14.drv-0/amdgpu-pro-17.40-492261/root/usr/src/amdgpu-17.40-492261/amd/amdkcl/kcl_drm.c:1:0:
/tmp/nix-build-amdgpu-pro-17.40-4.14.drv-0/amdgpu-pro-17.40-492261/root/usr/src/amdgpu-17.40-492261/include/kcl/kcl_drm.h: In function 'kcl_drm_calc_vbltimestamp_from_scanoutpos':
/tmp/nix-build-amdgpu-pro-17.40-4.14.drv-0/amdgpu-pro-17.40-492261/root/usr/src/amdgpu-17.40-492261/include/kcl/kcl_drm.h:332:9: error: too many arguments to function 'drm_calc_vbltimestamp_from_scanoutpos'
  return drm_calc_vbltimestamp_from_scanoutpos(dev, pipe, max_error, vblank_time,
         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /nix/store/prk1nwg5s1619jbrpp67v5jr3xpv7347-linux-4.14-dev/lib/modules/4.14.0/source/include/drm/drmP.h:83:0,
                 from /tmp/nix-build-amdgpu-pro-17.40-4.14.drv-0/amdgpu-pro-17.40-492261/root/usr/src/amdgpu-17.40-492261/include/kcl/kcl_drm.h:6,
                 from /tmp/nix-build-amdgpu-pro-17.40-4.14.drv-0/amdgpu-pro-17.40-492261/root/usr/src/amdgpu-17.40-492261/amd/amdkcl/kcl_drm.c:1:
/nix/store/prk1nwg5s1619jbrpp67v5jr3xpv7347-linux-4.14-dev/lib/modules/4.14.0/source/include/drm/drm_vblank.h:173:6: note: declared here
 bool drm_calc_vbltimestamp_from_scanoutpos(struct drm_device *dev,
      ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
make[4]: *** [/nix/store/prk1nwg5s1619jbrpp67v5jr3xpv7347-linux-4.14-dev/lib/modules/4.14.0/source/scripts/Makefile.build:314: /tmp/nix-build-amdgpu-pro-17.40-4.14.drv-0/amdgpu-pro-17.40-492261/root/usr/src/amdgpu-17.40-492261/amd/amdkcl/kcl_drm.o] Error 1
make[3]: *** [/nix/store/prk1nwg5s1619jbrpp67v5jr3xpv7347-linux-4.14-dev/lib/modules/4.14.0/source/scripts/Makefile.build:573: /tmp/nix-build-amdgpu-pro-17.40-4.14.drv-0/amdgpu-pro-17.40-492261/root/usr/src/amdgpu-17.40-492261/amd/amdkcl] Error 2

Maybe we should just undo declaring 4.14 the new default for the moment, so we unblock the channel?!

Fixed mwprocapture as of ce8dea6bdd18846579d32d0bcec94717bf616b41 !

@MP2E This may or may not be quite correct, see what ZFS developers did: https://github.com/zfsonlinux/spl/pull/666/files#diff-fc21f15a0f248a8ac8af4d3a06d86a89

@NeQuissimus I think so, let's fix this issue and retry.

Thanks for the pointer, after looking through the source a lot more carefully, it seems that it works as-is, but I noticed that one of the types was wrong, so I fixed it and updated the patch

Virtualbox will work with 4.14 once 5.2.1 is out: https://www.virtualbox.org/ticket/17080

Worth noting that Linux 4.9 doesn't work properly with Threadripper CPUs, specifically throwing a lot of bus errors due to a problematic ASPM implementation.
4.13.11 seems to be fine. Maybe we could use that?

zfsUnstable resolved in https://github.com/NixOS/nixpkgs/pull/31729

@Baughn: 4.13 is going away very soon.  On the other hand, GKG will be maintaining 4.14 for years.

@vcunat Yeah, I didn't mean permanently. :)
For the moment I've pinned my workstation to 4.13, but I'll be tracking the latest kernel for a while anyway; there are hardware features that won't be supported until at least 4.15, such as the CPU temperature sensors.

VirtualBox done in e5c24abf3b7f12232b7d2ae08415537d54d75c91.

This should fix nvidiaLegacy340:
https://github.com/MilhouseVH/LibreELEC.tv/blob/b5d2d6a171b6cc2fa00ff282bc08f63d8af121ec/packages/x11/driver/xf86-video-nvidia-legacy/patches/xf86-video-nvidia-legacy-0010-kernel-4.14.patch

Thanks, pushed.

@Vcunat if you look here https://pastebin.com/raw/tVL4DSdL
this fix two files for kernel 4.14.
I think kernel/nv-drm.c file should be patched too.
(According to https://devtalk.nvidia.com/default/topic/1025051/fully-working-patches-2-of-them-for-nvidia-driver-340-104-compiler-installer-file-and-linux-kernels-4-13-amp-4-14/?offset=5)
Previously this file always needed similar patch in order to get it work with latest kernel releases.
Problems may arise if different patches was already applied.
These should be applied always to vanilla installer files then it should I work.

I'm successfully running nvidiaLegacy340.
I have succefully built NVIDIA-Linux-x86_64-340.104.
With this patch only:
https://gist.githubusercontent.com/anonymous/46c78d06d9444c6ea574a1c77def3e42/raw/de58e60175cde2ca920efa56f71198f03987d1a5/nv_patch_340.104_linux_kernel_4.13
$ uname -a
Linux nixOs 4.13.16 #1-NixOS SMP Fri Nov 24 07:35:59 UTC 2017 x86_64 GNU/Linux
$ nixos-version
17.09.git.7f6f0c4 (Hummingbird)

Someone ticked off the ZFS box, this is in fact not working yet.
Only zfsunstable works on 4.14.
I expect a new ZFS release pretty soon.

Looking at the ArchLinux package for NVIDIA 304.137, it can be seen that they use the same patch for 304 as for 340.

Thanks, fixed up the build that way.  I'm not sure if anyone uses 304 on NixOS anymore, as .settings didn't (and still doesn't) link on x86_64-linux.

@yellowgh0st: right, patching nvidia_uvm_lite.c it's not done yet, but curiously it builds with 4.14 without patching it.  I hope I will look into it soon.  nixos-unstable doesn't yet contain the nvidia driver patches, but everything else should be there already.

Well, I patched the file anyway in e9550f290c.

@vcunat thank you for your work.

Do you think anything is blocking update of default to 4.14 (now)?  For amdgpu-pro we can add an assertion advising users to switch to 4.9 manually.  Nixpkgs 18.03 is to be forked in about two weeks.

I've been running 4.14.x and 4.15.x for quite a while now, I have had no issues. (albeit Intel GPU)

For the record, during the last two weeks I've been using 4.14 only.  It was mostly on a pure Intel system (Skylake-S) without any problems, and also on Ryzen + Nvidia with just those Ryzen bugs (probably).

We have not experienced problems with current 4.14 kernels on servers, VMs and laptops so far. As 4.14 also has long-term support, I also think we should default to that version for 18.03.

With 4.14 I have a boot-time kernel panic in ipmi_probe module on quite a new Supermicro server.
It should be ok to change default to 4.14 so far as 4.9 and 4.4 are still around and it is possible to write
boot.kernelPackages = lib.mkForce pkgs.linuxPackages_4_9

Yes, we keep all kernels supported upstream, i.e. six longterm branches now from which two are to be dropped soon.  4.14 is default in master now.

It should be ok to change default to 4.14 as long as 4.9 and 4.4 are still around
4.14 is supported until January 2019 and 4.4 until February 2022 so I see no reason we should drop these. :)

(triage) 4.14 is currently the default on 18.03, so I assume it has been for quite a while. If no issue has been reported… maybe this issue should be closed?

Yeah, we can close this. Just checked the remaining issues: the amdgpu PR was merged and the Intel 3D issues were fixed upstream.

amdgpu-pro bump was merged.  It doesn't build now with 4.14, but that's probably just a minor libelf issue.  On the whole it seems like it has few users if any.

Hmm, no, the obvious fix isn't enough:
--- a/pkgs/os-specific/linux/amdgpu-pro/default.nix
+++ b/pkgs/os-specific/linux/amdgpu-pro/default.nix
@@ -164,7 +164,7 @@ in stdenv.mkDerivation rec {
     done
   '';

-  buildInputs = [
+  nativeBuildInputs = kernel.moduleBuildDependencies ++ [
     patchelf
     perl
   ];

It fixes the ORC problem but fails later on some incompatibilities – it's apparently too new kernel for that driver version.


SAK-40287 Library: Made the footer positioning more efficient on every page load

https://jira.sakaiproject.org/browse/SAK-40287
Every time a page in Sakai loads, there is a JavaScript function that runs to resize the page and push the footer to the bottom. This function produces page jitter as the page is being resized and the footer is moved to the bottom. This makes every page seem slow or laggy.
This Javascript function has been replaced with CSS that positions the footer properly on page load and eliminates the page jitter.
I have also cleaned up scrolling in Resources and in the mobile view by reducing excess page length caused by the hidden tool menu still taking up room.

Have you tested this with really long pages (like lessons pages with lots of content)?
Since lessons pages embed other tools as iframes still,testing with (for instance) a samigo assessment delivered all on one page that is long would be a good test for this.
Thanks

Yes, I tested my change with pages and tools of a variety of different lengths, and sites with different lengths of tool menus.
Yes, I tested my change with Lessons containing text, links, subpages, student content pages, embedded YouTube videos, and linked quizzes. Long quizzes with all questions on one page shows in an iframe with a set height, so double scrollbars appear in the Lesson. This is the same before and after this change.

PR code updated to reflect comments from @bjones86

I've just uploaded a quick video to the JIRA ticket showing the before and after of my changes by comparing a few tools from the Home site on nightly master (the "before") during the first half of the video and my local host with the changes (the "after") during the second half.
You should notice the footer is positioned after the content and then jumps to the bottom of the page when the JavaScript re-positions it (the before) compared to the footer already being at the bottom of the page when the page loads (the after).
Also notice that the after state contains no scroll bars because the page is the exact height of the screen (when the content is less than the screen height).

For this fix, I had to add a magic number of 1px to the height calculation because I couldn't find where the 1px was coming from. This bothered me. I have finally found it: it was coming from the height of the #Mrphs-viewport-helpers children.
Since this PR was merged last night, I created SAK-40294. I've removed the 1px height from these children and removed the magic number from my #toolMenuWrap calculation.
I have submitted #5779 just now to remove the pixel. @jonespm and @bjones86, would you mind reviewing #5779  please? Thanks.


Cryptographed Fields

Is your feature request related to a problem? Please describe.
Some fields like address, ssn/cpf, password and others should be cryptographed in database. Some of them shouldn't be visible at any time.
Describe the solution you'd like
Passwords should be a hash, while other fields should be decryptable.
Describe alternatives you've considered
Add "password" and "crypt" to metadata
Additional context
#21 could have some nice insights into this. Possibly encrypt fields in __setattr__ and have a function __get_decrypted__ to ensure accessibility to field.

not


[DS-3456] 6x Fix Command Line Parameters for statistics import/export tools

Addresses the following

https://jira.duraspace.org/browse/DS-3456
https://jira.duraspace.org/browse/DS-3464
https://jira.duraspace.org/browse/DS-3437

The context for this PR and a suggested test plan is documented here: https://wiki.duraspace.org/display/~terrywbrady/Statistics+Import+Export+Issues

@kshepherd , I migrated the latest changes to the 6x branch

+1 by review


Max-width not working

<Flex>
  <Box maxWidth={600}>
    Some text
  </Box>
</Flex>

generates something like this:

which will not prevent children from expanding over 600 pixels in width.

Did you add the maxWidth function to your definition for Box? That prop is not included in grid-styled fwiw

I wanted to use rebass but then I decided to write my own components because it just seemed like an overkill to use UI library with many dependencies when I have to extend every component anyway.


Vertically center table contents

Fixes #479
This is overriding a bad bootstrap style

Before:

After:

Was just wondering, any reason you used baseline for the vertical-align instead of middle?

Was just wondering, any reason you used baseline for the vertical-align instead of middle?

I checked and you're right, middle looks slightly better I think. Changed it here: #534


Paradox in populating select box from directive

I'm trying to select options of select box after clicking an d3js chart element. D3js chart is built up inside the link function of a directive and has a action listener attached on all sectors of chart where action is a function defined in the controller wrapping the directive where I'm currently assigning desired values in ng-model of selectBox but its doesn't make selectBox to display selected options.
As a corollary I'm able to select options of selectBox through a click on a div that has action as same function which d3js chart listener had and that div too lives under the same parent as d3js chart.
Have a look at this plunk http://goo.gl/qCwqBo
Tab1: Why it doesn't populates ng-model -- currentVendors present in filterController when selecting one of the option in selectBox.
Tab2: populates it
But
After Clicking aqua colored square just above pie chart performs auto selection of select box.
While clicking any of the sectors of the pie chart supposed to perform the same action fails to do so while both of them execute same effective line of code at line 50 of filterController.js. which populates currentVendors array used as model of select-box.

@pulkitnandan please provide a minimal reproduce scenario using http://plnkr.co/ or similar. We can't debug full application code, I'm afraid.

For tab1 I need to attach filterController inside the template of ng-include directive so this means I can't set an array inside a controller which is wrapping ng-include directive which includes a html template that has element which uses the array model present controller but how the function is accesible inside the html template that is attached as ng-change?
Issue in tab2 is resolved if I call $rootscope.$digest() after assigning values to model.

I need put this array inside a object and then use this array as element of the object. Then tab1 works..


Codeunit 431 "IC Outbox Export": ICOutboxTransaction loses the filters in OnBeforeExportOutboxTransaction() event

BaseApp Version: 22.0.54157.54917
codeunit 431 "IC Outbox Export"
{
...
    local procedure ExportOutboxTransaction(var ICOutboxTransaction: Record "IC Outbox Transaction"; var FileName: Text)
    var
        ICOutboxImpExpXML: XMLport "IC Outbox Imp/Exp";
        OFile: File;
        OStr: OutStream;
        IsHandled: Boolean;
    begin
        OFile.Create(FileName);
        OFile.CreateOutStream(OStr);

        IsHandled := false;
        OnBeforeExportOutboxTransaction(ICOutboxTransaction, OStr, IsHandled);  /* ICOutboxTransaction here loses the filters it comes with! */
        if IsHandled then
            exit;

        ICOutboxImpExpXML.SetICOutboxTrans(ICOutboxTransaction);
        ICOutboxImpExpXML.SetDestination(OStr);
        ICOutboxImpExpXML.Export();

        OFile.Close();
        Clear(OStr);
        Clear(ICOutboxImpExpXML);
    end;
...
    /* ICOutboxTransaction here loses the filters it comes with! */
    [IntegrationEvent(false, false)]
    local procedure OnBeforeExportOutboxTransaction(ICOutboxTransaction: Record "IC Outbox Transaction"; OutStr: OutStream; var IsHandled: Boolean)
    begin
    end;
...
}

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 10881.


Fetch signer info from client response

All responses have verification header with public key and the signature of the remote node. We might want to use in the neofs-node to check if the remote node is not malicious. However API client does not return any transport layer information. Maybe we can change it somehow.

One of the options is to offload public key check right into client side rather than neofs-node side.
For example:

you provide both address and optional public key to the client,
client saves it and checks if the last verification header signer has provided public key.


Bug: Unable to get local plugins.json

After the monorepo migration, the location of the plugins.json is changed and all its references need to be updated.

Can you let me know what problems exactly this is CAUSING? I had no problem spinning up a project using the CLI

The clone-api-plugins was trying to get the remote plugins.json from the old location. I extracted the getFileFromCore function and I used it in the create-api-plugins action

Are you sure you tested with the latest version because that's already been fixed?

:tada: This issue has been resolved in version 1.3.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Create club info pages

pinpoint.com/${CLUBNAME}

not including application information pages, just the high level club info pages.


open_buy_order_time_out

How to use the the open buy order time out?
i dont know how to use this parameter......or whats the time format to use this option

https://github.com/tudorelu/pyjuque/issues/19#issuecomment-943543859


App URL leads to "Your app will appear here once you complete your first deployment."

That’s the default Amplify page. Has Amplify done at least one successful build?

Thanks! that was the issue. Manually running the build fixed it.


[Suggestion] Tinkers' Construct Integration for alloys

Would be awesome to add the alloys to Tinkers' - I asked there but they said it was best to ask here
https://github.com/SlimeKnights/TinkersConstruct/issues/2178
Thanks

Alice
DragonTechMC

I had a quick look. I see two problems: (a) We don't yet have the recipes in pre-init, (b) we have no way of looking up the fluid names for our input items (aside from our own metals), and (c) all I get from Tinkers in my development environment is crashes.

This would be great but, being realistic, I cant see us implementing this in the near future due to time constraints.


Bug in godep restore

https://github.com/tools/godep/commit/bd1a5cd1a59bff09fa53022436490eb03fb0dc4c
Above commit has some issue. 'go dep restore' is giving me following error : "godep: error restoring dep (github.com/chai2010/webp): found packages webp (bench_test.go) and main (gen_helper.go) in /go/src/github.com/chai2010/webp"
Before that commit it was working properly.

I tried to fix this, but it is usually the package that needs to be fixed actually. Normally, you should not have two files in a directory with two different package names (like bench_test.go has a package webp and gen_helper.go has a package main).
This is a fallout from moving away from go list in favor of go/build package.
Usually, this kind of bug is because that often helper binaries have "main" package and a // +build ignore constraint. The constraint was enough for go list to ignore the file alright. But after the switch, the UseAllFiles field is set to true by default, so it takes all the files, not taking // +build constraints into account at all.
Probably the proper solution would be to fix the offending package, but I tried to somehow work it around and failed.

"Fixed" in #352 as we'll also ignore the "ignore" build tag, at least for now. I think that's the path of least surprise.


⚠ Bofrost.lu has degraded performance

In 809a2ac, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1327 ms

Resolved: Bofrost.lu performance has improved in a9e5e68 after 14 minutes.


[WIP] Add Buildah buildstep plugin

WIP

@twaugh, thanks!
I just got back from PTO and we are pretty busy over at the MCO at the moment, so I don't really know when I'll be able to tackle this again.
If this is a priority now, do you think someone from CBS team can pick it up?

@LorbusChris will you have time to address those comments from @twaugh  ? if not I can create new PR, include your commit and address comments myself

@rcerven that would be great. Thank you!

@LorbusChris commit used in https://github.com/containerbuildsystem/atomic-reactor/pull/1246


[Event Request] Table 349 "Dimension  Value", OnDelete Trigger, OnDeleteBeforeDimValueUsed

Hi,
We need a new event in Table 349, "Dimension  Value" in the OnDelete Trigger.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Deno 1.0.3 - bundler doesn’t work properly with private # fields

https://github.com/denoland/deno/issues/5960
Recommend staying on Deno 1.0.2.

It seems denofunc on 1.0.4 works well.
https://github.com/denoland/deno/releases/tag/v1.0.4


How to ignore require with expression replacement?

I'm trying to bundle node_modules for nodejs application to decrease size of application image and save some essential space.
There is an issue with tricky library that is needed for application.
It has a few require with expression like:
const manifest = require(path.join(this.distDir, constants.PRERENDER_MANIFEST));

and I got
const manifest = __webpack_require__(1)(path_1.join(this.distDir, constants_1.PRERENDER_MANIFEST));

This doesn't work at all because __webpack_require__(1) function doesn't lead to original require.
How to tell webpack that expression requires should be touched?
How to manage it? Could you please help me?

It looks like you just deleted our lovely crafted issue template. It was there for good reasons. Please help us solving your issue by answering the questions asked in this template. I'm closing this. Please either update the issue with the template and reopen, or open a new issue.
Please respect time other developers, thanks


FlushTriggerWrapper is implemented

I needed a way to automatically flushing to a File target(autoflush=false, keepOpen=true, concurrentWrites=false), only for special LogLevels(>=Warn).
After some research i have found this idea of FlushTriggerWrapper and implemented this wrapper.
fixes #1712

This change is

I'm not sure, but we could add Condition property (not required) to AutoFlushTargetWrapper. Or it's better to be separate wrapper?

Cool ! Looks good!

I'm not sure, but we could add Condition property (not required) to AutoFlushTargetWrapper. Or it's better to be separate wrapper?

I think that's even a better option! What do you think @snakefoot ?

Current coverage is 81% (diff: 100%)

No coverage report found for master at 6b197e5.

Powered by Codecov. Last update 6b197e5...4ae7c96

As long the flush-triger-logic is not located on the BufferingTargetWrapper, then I'm good :)
But yes adding a condition-filter on the AutoFlushTargetWrapper would also work.

Would also work

not better?

Ps. Rebuild for codecov.

It will probably be better for the NLog users to have just one wrapper, that is dedicated to flushing.

Ok, i'll move code to AutoFlushTargetWrapper this weekend

👍
please open a new PR then, thanks!


More cleanups

This is halfway what's needed to have slice-threading going, the next step is to store in the slice the offsets

Command
Mean [s]
Min [s]
Max [s]
Relative

builds/c-ffv1 ../data/ffv1_v3.mkv
1.652 ± 0.001
1.652
1.653
1.00

builds/go-ffv1 ../data/ffv1_v3.mkv
4.265 ± 0.069
4.216
4.314
2.58 ± 0.04

builds/rust-ffv1 ../data/ffv1_v3.mkv
5.576 ± 0.001
5.575
5.577
3.37 ± 0.00

I'd land it soon if nobody is against it.


Promise Polyfill finally not there in IE11/EDGE using open-wc/building

I am getting errors in my web component when running in IE/EDGE when the finally block for a promise runs. I thought core-js included that but am not sure anymore. I have the latest version of core js installed.
Note: I'm using es-dev-server in compatibility mode.

We load the core-js polyfills only on IE11 due to the large size, so promise finally should work there. This means we miss out on some features like promise finally and array flat on browsers that do support modules but don't implement them. But they're not worth loading 150kb (non-gzip) polyfills in my opinion. We haven't figured out a good more fine grained polyfill loading strategy for this yet.
You could include the polyfills yourself on the page if you want though.


Bugfix/club members pagination

attempts to fix #472
I think this is caused by a warning thrown due to a non existent array index when there's no pagination (just one page) on the club members listing page.

One note here: all the bits should be tested with php 8.1 to find similar problems for the other areas of the codebase as we are moving to that php version in the rest api.

@pushrbx Noted. Tested with PHP 8.1.2


NaN next to rating

I'm not sure what it's supposed to be, but I'm not a fan. Suggest hiding that part of the component until whatever it is can be calculated.

Where do you see this? It's supposed to be zero (like the result of a division by zero).

It was https://ldjam.com/events/ludum-dare/42/everyone-chess but now it shows zeros, so I suppose there was some strangeness going on.

Ah, it could have been a moment before some "magic" data was available (i.e. populated by the cron job). Will have to take a look at the code that generates those and see if I'm expecting something to exist that may not exist.

Or I could check the render and just say 0 on NaN

I've seen NaN before as well, after refreshing it showed the actual ratings I made previously

Alright that probably means a request times out or there's a unlikely race condition between requests that sometimes goes the wrong way.


Can't move a folder icon in editing mode

Hi, I started to like this tweak as I found this as an upgrade of TapTapFolder.
Is it possible to move a folder icon in editing mode without disabling the tweak and respringing?
I seem to be unable to move a folder icon by holding it a while.
Thanks for the great tweak!

Yup, that is an issue I'm working on. Currently in v1.2.1-44 (not available on Cydia yet, but can be downloaded here):  you should be able to move folders, after you invoke editing mode on a normal icon. Can you report if that is working? Thanks!

Yes, it fixed the problem.  Thanks!

It might be a problem finding out which is a normal icon when you turn "Hide grey Folder Background" on, but in any case, even if you only see folder icons near your finger you can open one of them and then invoke editing mode on a normal icon inside.


Dylanhamersztein generate random emojis

This is #599 again, but with the addition of a rebase against master which should pull in the fixes added in #600

Well, good news the tests now actually run in CI which is an improvement over #599 where they didn't
However they don't pass
I think the problem stems from the way JavaScript handles string length with emoji -- they count as 2 because they are unicode characters so for example see below:
> "😊".length
2

Here's a screenshot of it running in my console

Nice 🚀  we are getting after it today 🤣 Are you open to another PR where I remove some unused files and dependencies?


Cant mining any Brain Tree Blocks

Cant mining Copper Brain Tree Block，Gold Brain Tree Block，Iron Brain Tree Block，Copper Framed Brain Tree Log，Gold Framed Brain Tree Log，Iron Framed Brain Tree Log.
I've tried using  pickaxe,axe,hoe,shovel,even sword.but it not working.

I already said this bug will be fixed in 21.0.0


Remove unused reporting code

Pull Request Test Coverage Report for Build 821

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.2%) to 94.533%

Totals

Change from base Build 819:
0.2%

Covered Lines:
4686

Relevant Lines:
4957

💛  - Coveralls


Make download and unpack steps idempotent

For now theses two task:

download prometheus binary to local folder
unpack prometheus binaries
aren't indempotent.

They randomly are in changed state because theses steps are executed locally (delegate_to: localhost).
With the changed_when: false they will no longer be in changed state (they still can be in fail mode, if anything goes wrong)

Those tasks are idempotent without changed_when: false. If they wouldn't be, molecule tests would fail every time as tests check for idempotency.
However, idempotency of those tasks depends on the availability of /tmp/prometheus-{{ prometheus_version }}.linux-{{ go_arch }}.tar.gz and /tmp/prometheus-{{ prometheus_version }}.linux-{{ go_arch }}/prometheus files. Lack of those files makes the task not idempotent, but I don't see any huge negative implications.

Yes, but by definition files in /tmp can be deleted, we use this role in our stack and it always show changed because we execute this role on an ephemeral worker (so /tmp is always empty when we run the role)
And so, it breaks our idempotency tests..
I really think that putting changed_when: false is good because theses files don't need to be present, if they are not ansible will download them anyway.


Fix document in NStepLSTM/GRU/RNN

I fixed typo in NStepLSTM/GRU/RNN functions.
I also fix document in NStepLSTM/RNN links to contain return variable in call.
This PR is related to #3903.

I fix documentation only Links.
Please review it.

jenkins test this please

LGTM


pysigma docker

Status
In Progress
Description
A pysigma docker with backends for qradar, splunk, sentinelone and Cortex XDR

WIP

Still needed


Unable to install from Debian meta-package

In Installation from Debian package, the script downloads a meta-package. Installing the package will have dependency error:
sudo dpkg -i linux-image-rt-amd64_6.12.6-1_amd64.deb
Preparing to unpack linux-image-rt-amd64_6.12.6-1_amd64.deb ...
Unpacking linux-image-rt-amd64 (6.12.6-1) over (6.12.6-1) ...
dpkg: dependency problems prevent configuration of linux-image-rt-amd64:
 linux-image-rt-amd64 depends on linux-image-6.12.6-rt-amd64 (= 6.12.6-1); however:
  Package linux-image-6.12.6-rt-amd64 is not installed.

dpkg: error processing package linux-image-rt-amd64 (--install):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 linux-image-rt-amd64

 sudo apt-get install -f will remove the linux-image-rt-amd64 package.
The following packages will be REMOVED:
  linux-image-rt-amd64

Instead of using the meta-package, I successfully downloaded and installed the patched kernel package from here.

Hi @tony2guo,
Thanks for bringing this to my attention. I changed the script now to download the patched kernel package that the meta-package points to instead (perhaps I should also make it download the kernel headers as well). I just tested it and it seems to work fine now. Let me know if it works for you too.
Thanks again!

Thank you for the fix! I tested it, and it works for me.


Fix a copy of a fixed length, possibly non-nul terminated, string

into a std::string so we don't run off the end of the array when
there is no nul byte in ProcessElfCore::parseLinuxNotes.
Found with ASAN testing.
rdar://problem/37134319
Differential revision: https://reviews.llvm.org/D42828
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@324156 91177308-0d34-0410-b5e6-96231b3b80d8
(cherry picked from commit 01cf28c211cd32c850bbe8f8110bf28d221fc54b)

@swift-ci test


Detect RapidSpike

Example site - https://www.matalan.co.uk/
Vendor site - https://www.rapidspike.com/
Category to be used - RUM
Detection - Look for https://cdn-assets.rapidspike.com/static/js/timingpcg.min.js

Hey there , added

@nurbek91  - I see that you added this under category 13 and 16. I think we should explicitly check for timingpcg.min.js and add this under category 'RUM'

Ok, i will take a look!

Hey there , updated