Rename columns in Admin area

In the "List of Drains" section of the Admin area there are several columns we would like to rename to make them more clear:

"Created at:" If this represents the date the drain was imported into the system, can we call it "Drain Import Date"? They all say 12/8/2015 so i assume that's what this means. If not, please clarify.
"Updated at:" Does this represent the date the drain was adopted? or renamed? ore either one? the dates range from 1/13/16 to the present. Maybe we can name this something more clear if at all possible. (on a side note, what date will be shown if the date is not adopted? Maybe that can say N/A)

In the "Users" section:

"Created at": does this mean the date the user account was created? If so, let's rename "Account Creation Date" or "User Account Created" or something.
"Updated at" seems to mean last user log in date. If so, let's rename "Last Log In".

PS, tagging this UX because Admins are users too! :)

:+1: admins are definitely also users :)
Unfortunately the admin side is using a generic Rails admin plugin so created_at/updated_at fields map directly to "record" terminology, but I think we should be able to make some labeling adjustments.
To answer your questions:

"Created at:" If this represents the date the drain was imported into the system, can we call it "Drain Import Date"? They all say 12/8/2015 so i assume that's what this means. If not, please clarify.

Correct, this is when the record was created in the database (which is generally only during the import).

"Updated at:" Does this represent the date the drain was adopted? or renamed? ore either one? the dates range from 1/13/16 to the present. Maybe we can name this something more clear if at all possible. (on a side note, what date will be shown if the date is not adopted? Maybe that can say N/A)
In the "Users" section:

This is the last time any field on the record was modified. Typically this happens during adoption, when the user_id field is populated, but would also likely happen during any future imports.

"Created at": does this mean the date the user account was created? If so, let's rename "Account Creation Date" or "User Account Created" or something.

Indeed, this is when the user record was created (which generally only happens during registration, but you can also add users manually in the admin area).

"Updated at" seems to mean last user log in date. If so, let's rename "Last Log In".

Similar to above, this is when any field on the user is modified (this does happen during login, where the current_sign_in_at field is updated), but can also happen if the user modifies their name or other elements of their profile. However, to determine their last login, you can use current_sign_in_at field (which you can see if you click to view the details of a given user).
Outside of these fields, if there is anything in particular you'd like to capture about users and drains that is currently being captured, we can certainly add fields to hold that information, but does the above information change how you might like to see these fields labeled?

Thanks, @jszwedko!
i think we should relabel if possible.

in the Drains section RENAME "Created at:" to "Drain Import Date"
in the Drains section LEAVE AS IS "Updated at"
In the Users section RENAME "Created at" to "Account Creation Date"
in the Users section RENAME "Updated at" to "Last Log In". (Since any change made by the user would require the user to log in, that's in fact what this column means)

otherwise it's not at all intuitive what "created at" and "updated at" mean, and it's different depending on whether you're in the Drains or Users section. This will make it much more clear to an admin what they are looking at.
however, is it even possible to relabel these things in Ruby?
thanks again!

this is awesome! so much easier on the admin end. i think we can close this. thanks @jafowler49 and @jszwedko!


Arduino Nano RP2040 Connect Support Request

It looks like at the core of this project, it should be able to drop directly into the RP2040 ecosystem, specifically around the connect since it also utilizes a build in microphone using the same PDM libraries the 33 BLE Sense uses.
As a compile test only (don't have a RP2040 connect currently), I was able to add the define headers to support both the open source and the official RP2040 board referenced from here: https://forum.arduino.cc/t/raspberry-pi-pico-variant-name/866778
#if defined(ARDUINO_ARDUINO_NANO33BLE) || defined(ARDUINO_ARCH_SAMD) || defined(ARDUINO_ARCH_MBED_RP2040) || defined(ARDUINO_ARCH_RP2040)
This opens the code to compile against the RP2040 boards but still hit an issue on the pre-compiled library.
To further test this, I just created a folder for the expected location for the RP2040 architecture by copying the existing compiled library src/cortex-m4 to src/cortex-m0plus.  This allows compiling against the RP2040 connect board in the Arduino IDE without issue.  I know this is likely to fail if I had a board to upload to because I tricked the IDE to use a pre-compiled library for a wrong architecture but it was more of a "let's see what happens" situation.
If it's possible to pre-compile the libpicovoice code for the cortex-m0plus architecture, this should be all it takes to make it compatible which would then add direct IoT capability to the Arduino and picovoice world.

You are right about the compilation and the whole Arduino ecosystem, but the Picovoice engine is not suitable for RP2040 as is, and needs some engineering effort to optimize it for this architecture.
Let's keep this open and see what kind of traction we get from the community.


Copy and Publish Build Artifacts - Always finds zero files on Mac agent.

Hi.
I am having troubles with the "Copy and Publish Build Artifacts" task, when it is running on a Mac agent. It seems that it never finds any files. The same task runs fine on VSTS hosted agent.
I get the following output from the log:
2016-10-11T17:50:15.7669480Z ##[section]Starting: Copy Publish Artifact: drop
2016-10-11T17:50:16.0421920Z Cleaning staging folder: /Users/vso123456/vsts-agent/_work/2/a/drop
2016-10-11T17:50:16.0470280Z found 0 files
2016-10-11T17:50:16.0690400Z ##[section]Finishing: Copy Publish Artifact: drop
Steps to reproduce:

Create a new Git repository or just use an existing.
Create a new build definition with "Copy and Publish Artifacts" as the only build step.
Set "Copy Root" to $(Agent.BuildDirectory)
Set "Contents" to **\*
Set "Artifact Name" to drop
Set "Artifact Type" to Server
Now run the build on the VSTS Hosted agent.
Verify that an artifact named "drop" is created.
Now run the build on a Mac agent. (I am using the Macincloud VSTS Agent linked below).
Verify that an artifact is not created. (The error!)

Does the  "Copy and Publish Build Artifacts" not support Mac agents?
Macincloud VSTS Agent link:
https://support.macincloud.com/support/solutions/articles/8000023177-versions-of-tools-and-applications-on-vsts-agent-plan-servers-

Does it work with **/* instead?

Unfortunately no.
I have even tried just using $(Build.SourcesDirectory) as Copy Root, and then in Contents I have added a complete path to a file I know exists in the source repository.

Are you using forward slashes and case-sensitive?
I'm not able to repro. Can you please provide some sample inputs?

...i mean sample inputs for the case where you are specifying the complete path to the file.

Hi.
To ensure we are testing at the same I have created a repository:
https://github.com/janniklind/vsts-copy-publish
I have created a build definition with just a single "Copy and Publish Build Artifacts" task:

When I run it on the hosted Microsoft Agent in VSTS it copies all the files without any problems: hosted-build-log.txt
However when I run on the MacinCloud Agent it always find zero files:
macincloud-build-log.txt

Can you try with **/* instead of **\*?

fyi - **/* (forward slash) works for me on OSX using your repository. The approach we generally try to take in the tasks and agent is: the tasks and agent should not convert backslash to forward slash on Linux/OSX, since backslash is a valid file name character. On Windows, in certain places, we take the opposite approach since forward slash is not a valid file name character.
For path pattern matching, use forward slash if your definition runs on Windows and OSX/Linux. If it runs on Windows only, then backslash is OK as well.

Today I tried with the **/* in the sample project and it worked. Don't know why I didn't test that in the sample project. I thought I had, but I must be wrong.
I still had trouble in my original project, but after removing the build step and adding it again, it now seems to work. I have no idea what it was.
Anyway, this can be closed, thanks for your help! :)


When I use a template created after following this tutorial, the projects are always created in a /template subfolder and not where I ran the dotnet new command

the template package csproj file says that the projects go into the /working/templates folder as subfolders, so when I run dotnet new to use the template a /templates subfolder is created in the folder where I ran the command, and the project folders in that as subfolders.
I looked at a few of the examples in the https://github.com/dotnet/dotnet-template-samples/ repo but those dont look like this tutorial.
if I unzip the nuget package created it looks like this.

If I install that nuget package by using dotnet new -i \<path to nupkg file\>, and then run the dotnet new \<alias\> command to create the project set from the template in the C:\temp\TemplateTests\MyNewProject\ folder, it executes without error but all of the projects are at C:\temp\TemplateTests\MyNewProject\templates instead of the C:\temp\TemplateTests\MyNewProject\ folder

How do I avoid having the extra /template directory in the created project's path?

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

ID: 64d0e779-2a93-d2b8-3fb0-8c88812a4fc7
Version Independent ID: 2e4ef5da-1b4b-a1d7-7ec8-6169360bf315
Content: Create a template pack for dotnet new - .NET
Content Source: docs/core/tutorials/cli-templates-create-template-pack.md
Product: dotnet-fundamentals
GitHub Login: @adegeo
Microsoft Alias: adegeo

Hi @StingyJack I'll run through the docs and see what happens. Which SDK are you using?

The projects all target 3.1. This is the template packaging project's csproj and template json
<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <PackageType>Template</PackageType>
    <!--Do not set a project version here as it will override the one specified when dotnet pack is executed -->
    <!--<PackageVersion>0.1.0</PackageVersion>-->
    <PackageId>Redacted.Template.ApiProjects</PackageId>
    <Title>Redacted templates for WebApi based service projects</Title>
    <Authors>Redacted</Authors>
    <Description>Redacted project templates to use when creating a new project set that uses Web API</Description>
    <PackageTags>dotnet-new;templates;redacted</PackageTags>
    <TargetFramework>netstandard2.0</TargetFramework>
    <IncludeContentInPack>true</IncludeContentInPack>
    <IncludeBuildOutput>false</IncludeBuildOutput>
    <ContentTargetFolders>content</ContentTargetFolders>
    <NoWarn>$(NoWarn);NU5128</NoWarn>
    <PackageOutputPath>.\Packaged</PackageOutputPath>
    <NoDefaultExcludes>true</NoDefaultExcludes> <!--  I added this to allow for including .editorconfig and .gitignore files, This settings presence didnt change the subfoldering-->
  </PropertyGroup>
  <ItemGroup>
    <Content Include="templates\**\*" Exclude="templates\**\bin\**;templates\**\obj\**" Link=".\"/>
    <Compile Remove="**\*" />
  </ItemGroup>
  <ItemGroup>
    <Content Include=".template.config\template.json" />
  </ItemGroup>
</Project>

{
  "$schema": "http://json.schemastore.org/template",
  "author": "Redacted",
  "classifications": [ "Redacted", "WebApi" ],
  "identity": "Redacted.Template.Api",
  "name": "Redacted project template for Web Api project types",
  "shortName": "redacted",
  "tags": {
    "language": "C#",
    "type": "project"
  },
  "sourceName": "$safeprojectname$"
}

Hi! Sorry I was in the middle of appending my comment with more information after running through the template article. I was going to ask for the info you just provided. I'll check it out.

How many ./template.config/template.json items do you have? I see that you have loose .sln and .md files in the template folder. Are you trying to do one giant single template that outputs all the individual folders+projects?

Just the one templateconfig/template.json referenced in the package csproj.
This first template is a "half stack" with DAL, WebApi, and a few other projects. When we onboard a new customer project this would be the starting point that takes care of most of the boilerplate and making sure that some the usual controls are in place. We have a few other variations with different project types, but this has to work first.
There are also item templates that will get built from the same sources. If I can't get this new template format to work, we revert to using the Export Template (previous style) project templates (for which there is little to no possible automation with VS in the toolchain).

Ahhhhh OK that is your problem. You need to move that \.template.config\ folder into the templates directory. That folder should be at the level of your template content itself.

@adegeo - that was it.  Since the tutorials didnt actually cover the multiple project packing, I had been basing the folder structure off of the multi project sample   which has...
package.csproj
---.template.config
------template.json
---templates
------project1
------project2

... like I had been trying to do.
Thanks for the assistance and the extra set of eyes.

Sure thing! It might be good in this article to showcase the folder structure with the two templates created in the previous tutorial steps.

... or get those samples fixed. =D

I believe the template should be OK. If you take that 05-multi-project folder and put it in the templates folder for the tutorial project, everything works fine.


feat(ripple): add way to globally disable ripples

Currently ripples can be only disable component-wise. This isn't very elegant if users want to disable ripples for all components.

This PR introduces a new OpaqueToken/ InjectionToken that can be used to globally disable all ripples.
Also makes the tab-nav-bar ripple directive more clean. Since Angular v2.3.0 (as we recently upgraded) the inherited metadata can be used.

Note: For upcoming accessibility features (focus indicators) we don't want to allow developers to disable programmatic ripples.

Not really sure. I feel like this could be a useful feature when not dispatching ripples (that are not required for a11y), but this would need a good design.

LGTM

@DevVersion  Can you rebase this?

@kara Done!


Add support for custom HTTP host header.

Thank you for a nice tool. I need to set a custom host header, so I introduced the -H parameter for this in my fork. Hopefully it will be useful for others.
Please note that the import path github.com/espebra/boom/boomer in boom.go must be changed back to github.com/rakyll/boom/boomer if pulled. Fixes #76.

I'm closing this to create a new pull request from a feature branch instead of master.


[Migration] : Upgrade Carousel Component to Embla Carousel React Library

We are planning to upgrade our carousel component in Keep React from "react-indiana-drag-scroll" to "embla-carousel-react" library. This upgrade will provide us with more features, better performance, and improved user experience.
Proposed Changes:

Replace the existing carousel component with the "embla-carousel-react" library.
Update the implementation to utilize features provided by the Embla Carousel library.
Ensure backward compatibility with existing code where possible.
Update documentation and examples accordingly.

Benefits:

Improved performance and smoother carousel transitions.
More features and customization options available.
Better compatibility with modern web standards.

Contribution Opportunity:
We are looking for contributors who can help with:

Implementing the migration to the Embla Carousel library.
Testing the new carousel component thoroughly.
Updating documentation and examples.
Reviewing and merging pull requests related to this upgrade.

If you are interested in contributing to this upgrade, feel free to take on this issue and submit a pull request. Let us know if you have any questions or need assistance with the migration process.
Note: Make sure to follow the guidelines outlined in our CONTRIBUTING.md file.
Thank you for your interest and contribution to Keep React!

Dear @shuvo-me, You can continue with this task.


fix: Fixed an issue where the type definition file url had no relativ…

…e path

Description 描述
uni-pages.d.ts文件内的url不是以/开头的绝对路径

Linked Issues 关联的 Issues
Additional context 额外上下文

Summary by CodeRabbit

Refactor

Updated path handling in the getDeclaration function for consistency and clarity.

Documentation

Adjusted the NavigateToOptions interface to ensure navigation paths are absolute, enhancing compatibility and predictability of routing behavior.

Thanks!


Kong Proxy SHM issues with kong events processor

Summary
We recently upgraded our ingress-controller from 0.9.1 to 1.1.1, and our kong-proxy from 2.2.4 to 2.3.1  and started to see the following errors in our proxy logs since:
2021/02/01 16:59:56 [warn] 22#0: *12415095 [lua] events.lua:155: post_event(): worker-events: could not write to shm after 6 tries (no memory), it is either fragmented or cannot allocate more memory, consider increasing 'opts.shm_retries' or increasing the shm size, client: <IP_ADDRESS>, server: kong_admin, request: "PUT /upstreams/071e7eb8-f1c2-49d8-948f-02a746bdc614 HTTP/1.1", host: "<IP_ADDRESS>:8444"
2021/02/01 16:59:56 [error] 22#0: *12415095 [lua] events.lua:273: post(): worker-events: failed posting event "upstreams" by "balancer"; no memory, client: <IP_ADDRESS>, server: kong_admin, request: "PUT /upstreams/071e7eb8-f1c2-49d8-948f-02a746bdc614 HTTP/1.1", host: "<IP_ADDRESS>:8444"
2021/02/01 17:00:07 [warn] 22#0: *12416220 [lua] events.lua:155: post_event(): worker-events: could not write to shm after 6 tries (no memory), it is either fragmented or cannot allocate more memory, consider increasing 'opts.shm_retries' or increasing the shm size, client: <IP_ADDRESS>, server: kong_admin, request: "PUT /upstreams/01f8580b-a04f-4cb8-b4a0-6c71d40bcbef HTTP/1.1", host: "<IP_ADDRESS>:8444"
2021/02/01 17:00:07 [error] 22#0: *12416220 [lua] events.lua:273: post(): worker-events: failed posting event "upstreams" by "balancer"; no memory, client: <IP_ADDRESS>, server: kong_admin, request: "PUT /upstreams/01f8580b-a04f-4cb8-b4a0-6c71d40bcbef HTTP/1.1", host: "<IP_ADDRESS>:8444"
Kong Version: 2.3.1
Ingress Controller: 1.1.1
PostgreSQL: 9.6
Kubernetes: 1.15.12 GKE
We have the following configurations in place but are still seeing the issue:
increasing memory available to the pods
setting KONG_NGINX_WORKER_PROCESSES to 2 (2 CPU x Pods)
bumping KONG_MEM_CACHE_SIZE to 512m (definitely appears to be overkill)
The main thing we see is "kong_process_events appears to fill up quickly and I am not sure how to purge it or ensure there is enough memory.
  "kong_process_events": {
    "allocated_slabs": "5.00 MiB",
    "capacity": "5.00 MiB"
  },

I have tried to increase this via NGINX directives but the pod just crashes when moving it to 10m
Here is the information from the /status endpoint:
{
"database": {
"reachable": true
},
"memory": {
"workers_lua_vms": [
{
"http_allocated_gc": "36.73 MiB",
"pid": 22
}
],
"lua_shared_dicts": {
"kong_locks": {
"allocated_slabs": "0.06 MiB",
"capacity": "8.00 MiB"
},
"kong": {
"allocated_slabs": "0.04 MiB",
"capacity": "5.00 MiB"
},
"kong_process_events": {
"allocated_slabs": "5.00 MiB",
"capacity": "5.00 MiB"
},
"kong_db_cache_miss": {
"allocated_slabs": "0.08 MiB",
"capacity": "12.00 MiB"
},
"kong_healthchecks": {
"allocated_slabs": "0.34 MiB",
"capacity": "5.00 MiB"
},
"kong_cluster_events": {
"allocated_slabs": "0.11 MiB",
"capacity": "5.00 MiB"
},
"kong_core_db_cache_miss": {
"allocated_slabs": "0.08 MiB",
"capacity": "12.00 MiB"
},
"kong_core_db_cache": {
"allocated_slabs": "4.93 MiB",
"capacity": "512.00 MiB"
},
"prometheus_metrics": {
"allocated_slabs": "0.04 MiB",
"capacity": "5.00 MiB"
},
"kong_db_cache": {
"allocated_slabs": "2.99 MiB",
"capacity": "512.00 MiB"
},
"kong_rate_limiting_counters": {
"allocated_slabs": "0.08 MiB",
"capacity": "12.00 MiB"
}
}
},
"server": {
"connections_writing": 1,
"total_requests": 1219469,
"connections_handled": 195468,
"connections_accepted": 195468,
"connections_reading": 0,
"connections_active": 1,
"connections_waiting": 0
}
}
Additional Details & Logs
This is constantly logging this error and we are not sure on how to fix it. Is it possible this is a memory leak?

you can edit /usr/local/share/lua/5.1/kong/templates/nginx_kong.lua to change kong_process_events value, I set the value 512m

Dear contributor,
We're closing this issue as there hasn't been any update to it for a long time. If the issue is still relevant in the latest version, please feel free to reopen it. We're more than happy to revisit it again.
Please have a look at our pledge to the community for more information.
Sincerely,
Kong Gateway Team


[Workspaces] launch same apps sequentially

Summary of the Pull Request
If there are multiple instances of the same app, Workspaces will launch them sequentially, waiting for each new instance to appear befor launching a new instance. It is needed for example for MS Outlook

PR Checklist

[ ] Closes: #xxx
[ ] Communication: I've discussed this with core contributors already. If work hasn't been agreed, this work might be rejected
[ ] Tests: Added/updated and all pass
[ ] Localization: All end user facing strings can be localized
[ ] Dev docs: Added/updated
[ ] New binaries: Added on the required places

[ ] JSON for signing for new binaries
[ ] WXS for installer for new binaries and localization folder
[ ] YML for CI pipeline for new test projects
[ ] YML for signed pipeline

[ ] Documentation updated: If checked, please file a pull request on our docs repo and link it here: #xxx

Detailed Description of the Pull Request / Additional comments

Validation Steps Performed
Tested locally

Closing in favor of https://github.com/microsoft/PowerToys/pull/35297


Timeout error during initial chef-client run in AWS Centos 7 image

I get a timeout error in AWS in the initial chef-client run while building a new server. Any ideas ?
While chef-client was waiting to run the command, I was able to run it manually
[root@ip-10-42-110-240 centos]# firewall-cmd --permanent  --query-service=http
no
[root@ip-10-42-110-240 centos]# firewall-cmd --permanent  --add-service=http
success
[root@ip-10-42-110-240 centos]# firewall-cmd --permanent  --query-service=http
yes

Here is the log.
Log:
[2015-04-03T17:36:58+00:00] INFO: Processing package[firewalld] action install (firewalld::default line 7)
[2015-04-03T17:36:59+00:00] INFO: package[firewalld] installing firewalld-0.3.9-11.el7 from base repository
[2015-04-03T17:37:16+00:00] INFO: Processing service[firewalld] action enable (firewalld::default line 9)
[2015-04-03T17:37:16+00:00] INFO: Processing service[firewalld] action start (firewalld::default line 9)
[2015-04-03T17:37:16+00:00] INFO: service[firewalld] started
[2015-04-03T17:37:16+00:00] INFO: Processing firewalld_port[8000/tcp] action add (app-ca-ppp::app line 12)
**[2015-04-03T17:37:16+00:00] INFO: Processing execute[add port 8000/tcp to zone] action run (/var/chef/cache/cookbooks/firewalld/providers/port.rb line 8)**

================================================================================
Error executing action `run` on resource 'execute[add port 8000/tcp to zone]'
================================================================================

Mixlib::ShellOut::CommandTimeout
--------------------------------
Command timed out after 600s:
Command exceeded allowed execution time, process terminated
---- Begin output of firewall-cmd --permanent  --query-port=8000/tcp ----
STDOUT:
STDERR: ERROR:dbus.proxies:Introspect error on :1.7:/org/fedoraproject/FirewallD1: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
---- End output of firewall-cmd --permanent  --query-port=8000/tcp ----
Ran firewall-cmd --permanent  --query-port=8000/tcp returned

Resource Declaration:
---------------------
# In /var/chef/cache/cookbooks/firewalld/providers/port.rb

  8:   e = execute "add port #{new_resource.port} to zone" do
  9:     not_if "firewall-cmd --permanent #{zone} --query-port=#{new_resource.port}"
 10:     command(<<-EOC)
 11:       firewall-cmd #{zone} --add-port=#{new_resource.port}
 12:       firewall-cmd --permanent #{zone} --add-port=#{new_resource.port}
 13:     EOC
 14:   end
 15:   new_resource.updated_by_last_action(e.updated_by_last_action?)

Compiled Resource:
------------------
# Declared in /var/chef/cache/cookbooks/firewalld/providers/port.rb:8:in `block in class_from_file'

execute("add port 8000/tcp to zone") do
  action "run"
  retries 0
  retry_delay 2
  guard_interpreter :default
  command "      firewall-cmd  --add-port=8000/tcp\n      firewall-cmd --permanent  --add-port=8000/tcp\n"
  backup 5
  returns 0
  cookbook_name "app-ca-ppp"
  not_if "firewall-cmd --permanent  --query-port=8000/tcp"
end

[2015-04-03T17:47:27+00:00] INFO: Running queued delayed notifications before re-raising exception

I have a feeling that my issue might be the same as this.


Add MagentA11y to the W3C tools list

I am content manager of the W3C Accessibility Evaluation Tools list.. We have received a request  to include Magenta11y in the list. According to the list management policy, we can only include the tool if the vendor agrees. Do you agree that we include it? In this case I need a contact email address to comment on some details.

Of course — MagentaA11y is an open source tool and T-Mobile is happy to see it shared.
Can I contact you via your uah.es email address?


cmake: command not found

./build: line 3: cmake: command not found
I'm getting this error on this command: "cmake . || exit 1".
I don't have an idea why.
OS: Linux Mint

You need to install cmake.

Thank you for the help, I think I uninstalled it while trying to install it.
But anyways now when I try to compile it is giving me a couple of errors. I would be happy if you could help me with that and thank you for your time by the way.
./build
-- Configuring done
-- Generating done
-- Build files have been written to: /home/estang/Downloads/csgo-champion-master
[ 11%] Building CXX object CMakeFiles/champion.dir/src/keylistener.cpp.o
[ 22%] Building CXX object CMakeFiles/champion.dir/src/musickit_changer.cpp.o
[ 33%] Building CXX object CMakeFiles/champion.dir/src/main.cpp.o
[ 44%] Building CXX object CMakeFiles/champion.dir/src/cheat.cpp.o
In file included from /home/estang/Downloads/csgo-champion-master/src/keylistener.h:12:0,
from /home/estang/Downloads/csgo-champion-master/src/keylistener.cpp:1:
/home/estang/Downloads/csgo-champion-master/src/remote.h:90:22: error: enclosing class of constexpr non-static member function ‘pid_t remote::Handle::GetPid()’ is not a literal type
constexpr pid_t GetPid(){ return pid; }
^
/home/estang/Downloads/csgo-champion-master/src/remote.h:50:8: note: ‘remote::Handle’ is not literal because:
class Handle {
^
/home/estang/Downloads/csgo-champion-master/src/remote.h:50:8: note:   ‘remote::Handle’ has a non-trivial destructor
/home/estang/Downloads/csgo-champion-master/src/remote.h:94:21: error: enclosing class of constexpr non-static member function ‘bool remote::Handle::IsValid()’ is not a literal type
constexpr bool IsValid();
^
In file included from /home/estang/Downloads/csgo-champion-master/src/cheat.h:16:0,
from /home/estang/Downloads/csgo-champion-master/src/musickit_changer.h:4,
from /home/estang/Downloads/csgo-champion-master/src/musickit_changer.cpp:1:
/home/estang/Downloads/csgo-champion-master/src/remote.h:90:22: error: enclosing class of constexpr non-static member function ‘pid_t remote::Handle::GetPid()’ is not a literal type
constexpr pid_t GetPid(){ return pid; }
^
In file included from /home/estang/Downloads/csgo-champion-master/src/keylistener.h:12:0,
from /home/estang/Downloads/csgo-champion-master/src/main.cpp:11:
/home/estang/Downloads/csgo-champion-master/src/remote.h:90:22: error: enclosing class of constexpr non-static member function ‘pid_t remote::Handle::GetPid()’ is not a literal type
constexpr pid_t GetPid(){ return pid; }
^
/home/estang/Downloads/csgo-champion-master/src/remote.h:50:8: note: ‘remote::Handle’ is not literal because:
class Handle {
^
/home/estang/Downloads/csgo-champion-master/src/remote.h:50:8: note:   ‘remote::Handle’ has a non-trivial destructor
/home/estang/Downloads/csgo-champion-master/src/remote.h:94:21: error: enclosing class of constexpr non-static member function ‘bool remote::Handle::IsValid()’ is not a literal type
constexpr bool IsValid();
^
/home/estang/Downloads/csgo-champion-master/src/remote.h:50:8: note: ‘remote::Handle’ is not literal because:
class Handle {
^
/home/estang/Downloads/csgo-champion-master/src/remote.h:50:8: note:   ‘remote::Handle’ has a non-trivial destructor
/home/estang/Downloads/csgo-champion-master/src/remote.h:94:21: error: enclosing class of constexpr non-static member function ‘bool remote::Handle::IsValid()’ is not a literal type
constexpr bool IsValid();
^
In file included from /home/estang/Downloads/csgo-champion-master/src/cheat.h:16:0,
from /home/estang/Downloads/csgo-champion-master/src/cheat.cpp:1:
/home/estang/Downloads/csgo-champion-master/src/remote.h:90:22: error: enclosing class of constexpr non-static member function ‘pid_t remote::Handle::GetPid()’ is not a literal type
constexpr pid_t GetPid(){ return pid; }
^
/home/estang/Downloads/csgo-champion-master/src/remote.h:50:8: note: ‘remote::Handle’ is not literal because:
class Handle {
^
/home/estang/Downloads/csgo-champion-master/src/remote.h:50:8: note:   ‘remote::Handle’ has a non-trivial destructor
/home/estang/Downloads/csgo-champion-master/src/remote.h:94:21: error: enclosing class of constexpr non-static member function ‘bool remote::Handle::IsValid()’ is not a literal type
constexpr bool IsValid();
^
CMakeFiles/champion.dir/build.make:182: recipe for target 'CMakeFiles/champion.dir/src/musickit_changer.cpp.o' failed
make[2]: *** [CMakeFiles/champion.dir/src/musickit_changer.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....

The compiler you mean gcc right?
And I cant thank you enough for your patience with me

Yes, I mean gcc. You should update it to version 7.2 or 7.3. To check current version you can type in terminal
g++ --version

I'm not being able to to update gcc but thank you for your time anyway.


Fix command for adding new networks.

Preview is available here:http://developers-pr667.previews.kube001.services.stellar-ops.com


Block calendar date

Is there any way to leave the calendar locked so the user cannot select dates in the future? Example: maxDate={new Date()}

Thanks


Dev next

Current coverage is 54.37%

Merging #1470 into develop will increase coverage by +0.18% as of fb08f1a

@@            develop   #1470   diff @@
=======================================
  Files           965     968     +3
  Stmts         67374   67455    +81
  Branches          0       0
  Methods           0       0
=======================================
+ Hit           36514   36677   +163
  Partial           0       0
+ Missed        30860   30778    -82

Review entire Coverage Diff as of fb08f1a

Powered by Codecov. Updated on successful CI builds.


Memory usage about 12G,it is normal?

I use Vmware test this project,and system is ubunut 17.04,allocate 8G ram,run this project a later that system be stuck. any operation is invaild.

when i put this project in tencent cloud with 16G ram，I use top to see the java process ram usage about 12G.the project can be start normal.

if you are running all projects then it might take up memory, I can run them on Mac with 16 GB RAM without any issues. I would suggest you use the -Xmx flag to limit the memory to 1 GB for all the servers when you start them.

I know that ,but I just don't know that the other guys have seem problem。I was slove the problem,however，thanks your reply


[pai-build] add pai-build doc.

Coverage decreased (-21.0%) to 51.057% when pulling 29220da5fda7523e9dfa464247ee21415b1b7111 on canwan/paibuild-doc into 4c1a3589591fec36befa91e0c50a28ab2ffc35a7 on master.

PAI build is a special component of PAI compared with those dockerized micro-service modules. So it is neither necessary nor correct to follow the same document structure as they do. I suggest you re-organize the doc to make the following items clear:

What is PAI's process of building docker images?
What standard a module should follow to integrate with PAI's build mechanism?
How to configure the behavior of PAI build? (For example, using a build-level configuration file.)
What is the future plan?

Btw, if you remove this functionality from paictl, please find somewhere to place the usage of 'build' that end-users can follow.

I agree we can add a section to describe "What is PAI's process of building docker images?". But I think this document aims to describe what is current  PAI build process, not a design doc for future build process.
I think this document should match our current implementation, actually we don't have build-level configuration file and have not removed build from pai-management. The document will be updated continuously when we refine our process, or have new features.


Pinned keystoneclient version causes dependency resolution issues

EOM's requirements.txt specifies python-keystoneclient==1.6.0 (current version: 3.13.0). KSC 1.6.0 depends on pbr >=0.11,<2.0. Most other packages in eom and KSC's dependency trees depend on pbr>2.1 or so.
For some reason eom installs anyway if installed alone, but it's breaking RSE2's dep resolution (RSE2 depends on EOM).
To reproduce:
$ virtualenv venv
$ . venv/bin/activate
$ pip install eom pipdeptree
$ pipdeptree

pipdeptree should note the dependency conflict at the beginning of the output. Probably the eom deps should instead specify keystoneclient>=1.6.0,<2.0.

@andrew-vant thanks for bringing this to my attention. Not sure if I'll be able to get to it today; PRs are welcome. It'd probably be good to get requires.io setup on this repo and then pin all targets.

Okay, done. I'm not familiar with requires.io, so this just fixes the problem at hand.


[BUG] [op-main] Gravity batch is stuck in redelivery

The problem seems to derive from the use of multiple nonces throughout the gravity module. Most importantly, there are 2 different kinds of nonces: BatchNonce and EventNonce. While the former is used to identify a specific version of the batch being relayed, the second one is a bit more nebulous.
The design behind it seems to originate right from the gravity contract, that would emit a nonce as part of its observation events. Our contract doesn't do that. Instead, each Pigeon is using its own, dedicated nonce for relaying gravity batches, and only for that.
In addition to that, Paloma keeps track of the latest observed event nonce it received from the Pigeons, which is in line with a universal source of truth, where the nonce would originate directly from the smart contract. But for us, it doesn't. It's just an arbitrary nonce that's increased every time a Pigeon calls in with a gravity update.
Since Paloma keeps track of the latest nonces, it assumes all older nonces to be replays of older events and discards them. However, there seems to be absolutely 0 reconciliation or synching in place between nonces. Meaning, if Pigeons don't relay and observe, i.e. because they're jailed, offline, RPC issues, whatever ... they might not see certain batches on the target chain. Since they're not around to attest those events, they won't increase their nonce.
The more often this happens, the more out of sync nonces becomes. Take a look at this example block:
https://testnet.paloma.explorers.guru/block/7521077
It contains 2 transactions, both are attest messages to an observed event. The event observed is identical (notice the identical batch ID and eth block height), but the event nonce is almost 100 units apart! This means Paloma will not treat those as attests to the same event. Instead, it will likely just completely ignore them, as the event nonce around that time was well over 1000 already.

Proposed solution
Needs some brain storming, but I would suggest that the nonce in question needs to be synched against the latest observed nonce ever so often.

@byte-bandit what are the next steps for this ticket to close?

@taariq After we release 1.10.1 and the network has recovered with most validators being unjailed, we need to confirm that the batch is indeed being removed.
I will do that as part of recovering the test net. Once it's done, I will update this ticket and close.

@taariq Batch is still stuck because it hasn't yet been redelivered since the compass was upgraded: https://optimistic.etherscan.io/address/0xC137433e767bdDE473511B84df834e5D13389015
Likely most validators are lacking the funds, including ourselves.

There's also this one that might prevent Pigeons from seeing the event in question: https://github.com/VolumeFi/paloma/issues/1023 (though it might reach optimistic consistency and just cause a lot of log noise)

Batch still not removed, but also no attempted relay yet. Going to keep an eye on the assignment.

@taariq @verabehr
So, there's another bug in the gravity bridge that became apparent after we're double checking the target chain valset ID before we send a transaction to it.
For SLC, we always create a JIT valset update along with the SLC call and make sure that is processed successfully BEFORE we publish the SLC.
For gravity batches, this doesn't happen (yet). We will need to change how messages are emitted and handled on Paloma side for this.
I think we can do it similar to the SLC solution. Publish JIT update alongside, then "hide" any outgoing batches from relayers until the chain has no pending valset update messages in the queue any longer.
The change shouldn't be large, but I haven't worked with that side of the code a lot recently and will need to familiarise myself with it again.

Thanks for the update on this. Okay to reflect: New bug in Gravity Bridge detected.

We create JIT valsets with the SLC call to make sure that we are able to do the SLC.
We did not create the feature for Gravity Batch calls
We need to make this update.

Did I get that? Agreed and aligned. @verabehr will you create a ticket for this and put that ticket in TO-DO under Gravity? We'll get to it after Pigeon Feed.
@byte-bandit any objections to closing this ticket?

@taariq Batch is still stuck. I'd leave it open for now. Maybe move to blocked until we solve the bug I outlined.
Also, we're going to need to address this before or along with Pigeon feed, as that will require a working bridge I think.

@byte-bandit moving this back into Progress while we wait on compass upgrade.

@byte-bandit status on this?

I have not started looking into this again, will update once I finish with this attestation enforcement epic.

Closing this as it's no longer relevant with new test net.


Truncate stack trace from error output

I'm always frustrated when scrolling throw stack trace to my actual errors in database.
Solution
Remove stack trace and keep only database errors.
Before
clickhouse adapter: ClickHouse server does not support exchange tables Database Error
  Code: 1.
  DB::Exception: System call renameat2() is not supported. Stack trace:

  0. DB::Exception::Exception(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, int, bool) @ 0xce3f35a in /usr/bin/clickhouse
  1. DB::renameExchange(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) @ 0x11a385a5 in /usr/bin/clickhouse
  2. DB::DatabaseAtomic::renameTable(std::__1::shared_ptr<DB::Context const>, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, DB::IDatabase&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, bool, bool) @ 0x11a2f0dd in /usr/bin/clickhouse
  3. DB::InterpreterRenameQuery::executeToTables(DB::ASTRenameQuery const&, std::__1::vector<DB::RenameDescription, std::__1::allocator<DB::RenameDescription> > const&, std::__1::map<DB::UniqueTableName, std::__1::unique_ptr<DB::DDLGuard, std::__1::default_delete<DB::DDLGuard> >, std::__1::less<DB::UniqueTableName>, std::__1::allocator<std::__1::pair<DB::UniqueTableName const, std::__1::unique_ptr<DB::DDLGuard, std::__1::default_delete<DB::DDLGuard> > > > >&) @ 0x125ca713 in /usr/bin/clickhouse
  4. DB::InterpreterRenameQuery::execute() @ 0x125c9608 in /usr/bin/clickhouse
  5. ? @ 0x1297956b in /usr/bin/clickhouse
  6. DB::executeQuery(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, std::__1::shared_ptr<DB::Context>, bool, DB::QueryProcessingStage::Enum) @ 0x1297682d in /usr/bin/clickhouse
  7. DB::TCPHandler::runImpl() @ 0x1353d924 in /usr/bin/clickhouse
  8. DB::TCPHandler::run() @ 0x13551919 in /usr/bin/clickhouse
  9. Poco::Net::TCPServerConnection::start() @ 0x1636236f in /usr/bin/clickhouse
  10. Poco::Net::TCPServerDispatcher::run() @ 0x163646fb in /usr/bin/clickhouse
  11. Poco::PooledThread::run() @ 0x1651ff92 in /usr/bin/clickhouse
  12. Poco::ThreadImpl::runnableEntry(void*) @ 0x1651d71d in /usr/bin/clickhouse
  13. ? @ 0x7fd8e7797609 in ?
  14. clone @ 0x7fd8e76bc133 in ?

After
clickhouse adapter: ClickHouse server does not support exchange tables Database Error
  Code: 1.
  DB::Exception: System call renameat2() is not supported.

Hi @3fonov
Thank you for your contribution.
The error appears in the first line of the stack trace so most of the time there is no need to scroll until you find it.
In addition, and most importantly, we use this stack trace to investigate things on the ClickHouse side, therefore, this suggestion is problematic.
Thanks again, we would love to get your help with other urgent issues.

@BentsiLeviav from my point of view at day to day work i have following output in model with errors:

And for me relevant only upper half of the output. Some times terminal window not so big and actual error hidden behind the fold. So stack trace in 99.9% of times is not relevant to me. Same thing made at dbt-bigquery adapter. Maybe we can introduce env variable HIDE_STACK_TRACE to hide stack trace?

Maybe we can introduce env variable HIDE_STACK_TRACE to hide stack trace
Sounds good. Let's disable it by default.


mathematica: enable installation of localized editions

Motivation for this change
Mathematica has many localized editions, e.g. Japanese edition, which I want to install.
This PR aims to make it easier to add such localized editions.
For now English (default) and Japanese editions only.
Fill out information in l10ns.nix to add the other localized editions.
Example usage: mathematica.override { lang = "ja"; } derives Japanese edition.
Things done

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

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

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

In the future it would be useful to standardize this. Something like config.locale maybe even defaulting to $LANG.


COP is used wrong in cooling for both Households and Buildings

The definitions for heating and cooling COP's are as follows (wikipedia):
When one is interested in how well a machine cools, the COP is the ratio of the heat removed from the cold reservoir to input work. However, for heating, the COP is the ratio to input work of the heat removed from the cold reservoir plus the heat added to the hot reservoir by the input work.
Currently the COP definition for heating is used for cooling as well which leads to an underestimation of 1/3 of the energy needed for cooling. Fixing this problem will have quite a big impact on charts (as their values will change and their format will be outdated) and I guess on many other things as well, but I cannot oversee the entire impact this will have. Nor have I got a clue where is the best possibility for a quick fix.
The problem of using the wrong COP:

The COP for airconditioning as found in InputExcel --> cost heat pumps --> row K:

Useful demand as found in the graph:

@AlexanderWirtz , as you are looking into the specs of heat pumps, could you advice me on the COP of heat pumps when it comes to cooling (both numbers and definitions)?
The ETDataset, ETSource and ETEngine code has changed significantly since @lodykuling wrote this issue, so I propose to start from the data and make sure that this ends up correctly in ETSource.

This has been nagging at me for a long while as I am not sure if there is a real problem.
@mabijkerk could you look into this and see if it is still an issue? Refer to @michieldenhaan with your questions. If needed, we can discuss this in a broader group.

Theory for documentation/background
The diagram below shows the heating and cooling mode for a sample heat pump (air):

The difference is that in heating mode, the house is the heat sink (the heat needs to go to the house), while in cooling mode the house is the heat source (the heat needs to be removed from the house). In heating mode this means that the input electricity W_net adds useful heat as it increases the heat supplied to the house. In cooling mode the input electricity does not add useful heat, because it increases the heat supplied to the air, not the heat extracted from the house. Because COP = Q_useful / W_net applies for both heating and cooling mode, the COP for this sample heat pump is higher in heating mode than in cooling mode.
The issue in the ETM
The problem now is that in the ETM, for example for the nodehouseholds_cooling_heatpump_air_water_electricity, the input electricity W_net does contribute to the cooling output. This is visible in the screenshot below, for a blank nl2019 scenario. The electricity input and cooling output are based on source_analyses in ETDataset, so the result is that the ambient cold input is underestimated.

The solution
A straightforward way to solve this, is to add a loss, which is should be equal to the input electricity because the input electricity does not contribute to the useful demand for cooling. This approach requires minimal changes to the graph. In the example for nl2019 above the loss would become 0.31415 PJ and the ambient cold 1.41 PJ.
It is important to note that this means we assume the ambient cold extracted from the air to be equal to the cooling supplied to the house. This means that ambient cold extracted does not equal the heat that is actually supplied to the air, which would be Q_hot in the diagram for the sample heat pump in cooling mode. The distinction is that the ETM uses cooling, while in reality it is heat with a lower temperature.
To do

[ ] Update cooling heat pump nodes to include a loss which is equal to the input electricity
[ ] Update input electricity and input ambient cooling to be in line with this new approach. The node source analysis for these inputs seems to be quite outdated and lacks documentation, therefore it is better to research new data from the ECW and energy.nl (this can be done in parallel with https://github.com/quintel/etdataset/issues/900)
[ ] Review charts that show cooling
[ ] Review the calculation of the COP in the "Technical and financial properties" (this is calculated here https://github.com/quintel/etengine/blob/master/app/models/qernel/node_api/capacity_production.rb#L267-L280 where efficiency_based_on is the primary carrier, typically electricity and efficiency_balanced_with is typically ambient heat.)
[ ] Write documentation for heat pump cooling


Syncfusion grid are identified as Custom type.

Application am testing is using Sync fusion control, it is resolved as Custom type.
Is there any way to resolve it based on the control.

Any update on this issue?


Feature/diagAandB

5x2( fcst & ana)  diag variables are collected into a HISTORY.rc collection :catch_diag_aup.
the system is based on develop branch as 4/30/2017.

we certainly can skip "fcst" part and only get "ana" set in this "aup" collection.   In that way we rely on the inst  03h lnd collection for "fcst" values.  It probably is desirable to have sort of instruction to users in generating History.rc that if the analysis "aup" collection is selected, then inst 03h lnd should be selected as well.

@saraqzhang : I think you misunderstood, probably because I had a typo in one of my comments, sorry.  The following lines would be in the same collection ("inst3_1d_lndfcstana_Nt") in HISTORY.rc:
'WCSF' , 'ENSAVG' , 'SFMC_FCST'
'WCSF_ANA' , 'LANDASSIM' , 'SFMC_ANA'
So if the user selects the "inst3_1d_lndfcstana_Nt", both the FCST and ANA variables will be included in the same file.  The trick is that the FCST variables can just be pulled from the Ens Grid Comp.  They don't need to be recomputed in the LandAssim Grid Comp.

yes that will do.  it will be a ldas analysis-specific inst collection,  not the general inst lnd collection that is more GCM general collection.

@gmao-rreichle :  I made modifications ( lndfcstana collection)  according to the discussion last week and pushed to the branch Feature/diagAandB,  the modification passed test run.

addressed with pull request #240 (after starting a different branch and pull request)


(QENG-1562) All-In-One Agent Beaker usage added

Waiting for CLA signature by @kevpl
@kevpl - We require a Contributor License Agreement (CLA) for people who contribute to Puppet, but we have an easy click-through license with instructions, which is available at https://cla.puppetlabs.com/
Note: if your contribution is trivial and you think it may be exempt from the CLA, please post a short reply to this comment with details. http://docs.puppetlabs.com/community/trivial_patch_exemption.html

@kevpl There are repos available for the AIO just like for puppet or facter, so we shouldn't need to resort to using rpm or dpkg directly (apt-get and yum should be just fine). The repos live at http://builds.puppetlabs.lan/puppet-agent/e5922492cce4c236e1d850c8a9a4649f3b367e47/repos/ and repo configs live at http://builds.puppetlabs.lan/puppet-agent/e5922492cce4c236e1d850c8a9a4649f3b367e47/repo_configs/.
I would expect beaker to already have methods for adding a builds.pl.lan repo to the test machine and installing a package from it, but I could be crazy.

CLA signed by all contributors.

@kylog to your comment, yes.  It requires Beaker 2.2.0 to get the new paths required for the All-In-One agent, even if we were able to use install_packages_on.  Let me know if because of this I should be doing something differently here.  I'm not familiar with who I should be talking to about which version of Beaker you guys use, would that be Roger?
@haus, install_packages_on doesn't do any package proxying that I'm aware of, so unless sudo apt-get install puppet-agent will work, we'll need to use something else.  Now that you have the hash directories on the build server, we can switch over to using install_puppetlabs_dev_repo, which did already exist though.  I've done this in my latest version of the change.
Let me know if you guys have any questions about this, or need me to do anything for you to get this moving.
Thanks,
Kevin

@kevpl sorry, lost track of this PR. Is this still live or has it been overtaken by @justinstoller's work?
If still live, it looks like it needs a rebase, but otherwise I'm :+1:
/cc @haus

Ping @kevpl on questions above.

sorry @kylog about not getting back to you sooner on this.  I've spoken with Justin about it, and we're actually coming at these as separate passes.
He's doing what he can to make AIO work in the Jenkins environments with what he has in the projects as a quick & dirty solution, and I'm coming around as a second pass with the Beaker supported way of installing these packages from the dev repos.
Unfortunately due to new work for AIO issues that have come up in testing, this code needs something that has been merged but not released in Beaker yet (#638).  Would you rather I just close this PR until I have something released and can have the conversation with Justin and Roger about getting that version of Beaker into testing for this project?

@kevpl sounds great and thanks for the update.
Yeah I'd close it for now and re-open it once the dependencies are resolved and it's ready for review.
Thanks!


Invalid port and invalid path for Git in Win 7

Receiving invalid port for running Plex Server on a Synology NAS. Also Git Path is not recognized (when placed in HTPC Man. settings) operating in Win 7 due to space in path (Program Files) even when quotes (" "or ' ')are placed around the full path. Git path is loaded in the regular Win 7 environment path.
htpcmanager.log

If i'm reading the log correctly, you are not using this version of HTPC-Manager, but a fork instead.


Provide default request-format

Same as #4 except for :format instead of :response-format.
If not provided when doing a POST (for example) get a 'unrecognized request format nil' exception.

You need to use :body if you dont include a :format.  The request ends up as edn, so I also stick this in. :headers         {:content-type "application/edn"}


Allows SELINUX hosts to share content on mounts with the container

Changelog
Fill this in and update CHANGELOG.md
Issues fixed or closed
Questions (open the PR then click the check boxes)
Did you update the documentation related to your changes?

[ ] Yes
[ ] My changes were not already documented

Did you run make before committing code and opening this PR?

[ ] Yes
[ ] I didn't change any code

Did you run porter create-stack and porter sync-stack to verify provisioning
works?

[ ] Yes
[ ] N/A

👍

I've confirmed this fix with Background Removal.

@vsandeepsrivastav You can check the yes boxes above. Or someone else with write privileges can.

Version 4.8.1:
Running deployment hook START
=============================
Traceback (most recent call last):
  File "/BuildCustomVPCStack.py", line 83, in <module>
    logging.basicConfig(level=logging.INFO, filename="buildcustomvpcstack.log")
  File "/usr/lib/python2.7/logging/__init__.py", line 1547, in basicConfig
    hdlr = FileHandler(filename, mode)
  File "/usr/lib/python2.7/logging/__init__.py", line 913, in __init__
    StreamHandler.__init__(self, self._open())
  File "/usr/lib/python2.7/logging/__init__.py", line 943, in _open
    stream = open(self.baseFilename, self.mode)
IOError: [Errno 13] Permission denied: '/repo_root/buildcustomvpcstack.log'

With change:
Running deployment hook START
=============================
===========================
Running deployment hook END
t=2017-06-07T21:51:54+0000 lvl=dbug msg="buildAndRun() END" porter_version=vCOLMURPH cmd=pack HookName=pre_pack HookIndex=0 Concurrent=false Repo=git@git.corp.adobe.com:EchoSign/BuildCustomVPCStack.git Ref=0.1 RunCondition=pass Dockerfile=.porter-tmp/pre_pack_clone_0_1/pre-pack ImageName=backgroundremoval-pre_pack-0-1

@davepersing can you take a look too?

👍


gitlab-runner: 14.8.0 -> 14.8.2

Motivation for this change
https://gitlab.com/gitlab-org/gitlab-runner/blob/v14.8.2/CHANGELOG.md
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Adding a backport relase-21.11 label because the 14.4.2 security release is missing on 21.11 and 14.4.x is about to be EOL anyway.


Support npm module oortcloud/node-ddp-client

https://github.com/oortcloud/node-ddp-client
can you help to support this npm module? thanks..

Yeah I need this too, Meteor is awesome FW out there. I think Tabris should support this ASAP. I got error when installing npm module which is having module dependencies. For example:
MyApps
-node_modules
---underscore (this npm module works fine, because it has no node_modules dependencies)
---ddp (this npm module not working because it has node_modules dependencies)
-----node_modules (node_modules by the ddp npm module)
Please answer, thanks

We will look into this for the next 1.0.1 release.
It would also help if you could provide a clear description of the problem (i.e. warnings/errors on the console). It would also help if you could provide clear steps to reproduce the problem.

A more specific error description can be found in #470.

This module requires the built-in node module events that is not yet available for Tabris.js.

So this will be supported or not?

The ddp module also has a dependency to a websocket implementation, that will also not work out of the box, as it in turn depends on the node net module.
Chances are that it will be supported at some point, but it won't happen in the next weeks.

Hi!
So, fetching from server via http ajax is the only option for now?

Hope it will be realized ASAP. As I said before, meteor is very good, promising, and have very high github stars. Automatically if tabris able to support this, tabris name will be gained popularity more and more.


Quick Tile

Show weather in quick tile this will reduce home screen space it will be handy for users without adding anything on the home screen

@Leonavichus are you working on this feature?


Add Prometheus-readable metrics endpoint

Fixes part of https://github.com/channable/hoff/issues/99 by showing Prometheus-readable metrics on a configurable port, only showing one metric (number of PRs merged) at the moment. Other metrics will be easier to add now, but they should be described in new issues, in more specific detail, when the need arises.

I don't read Haskell very well so I can't comment too much, but I have one suggestion
Right now we have a single counter for the number of PRs merged. This is not that helpful if you have many projects in a single instance like we do. Perhaps we could add a project label to the counter and track the metric by project?

Sorry for the lack of clarity, that's what it already does!

@OpsBotPrime merge

Pull request approved for merge by @DiegoDiverio, rebasing now.

CI job :yellow_circle: started.


Edit Widget

Hi,
I have some problems to edit the widget. If I have a picture and text in one column its almost impossible to click at them seperately.
Is there a trick?

Could you post the version of CKEditor you're using and a screenshot of the issue?  Thanks!

Thank you for your reply!
I am using CKEditor 4.
It's impossible for me to select a word and edit it. When I try to click on it it marks the whole content, the widget or one column. And the mousecursor doesn't work in the widget like in normal text.
Thank you for your help!

I installed Firefox again and since then its working perfectly.
I guess something went wrong there (or with firebug)!

Hmm. Thanks for following up!


Support specifying a list of regions to run on

Rename the '_experimental_scheduler_placement' proto field to just 'scheduler_placement'.
Disallow specifying both 'region=' and '_experimental_scheduler_placement='.
Make things backwards compatible, with '_experimental_scheduler_placement=...' and 'SchedulerPlacement(region=...)', both at the API level and at the proto level. For the latter, the field is marked as deprecated and will be normalized away on the server.
Support specifying regions for 'modal shell'.

@prbot approve

@prbot automerge


command not found: howdy

My distribution: ubuntu 22.02.2 LTS
I install it by following the introduction of README.md: adds ppa source and install it. (but when installing the three data pack, I download then manually instead.)
I have tried to list files of howdy, and also didn't find a excutable file
➜  ~ dpkg  -L howdy
/.
/lib
/lib/security
/lib/security/howdy
/lib/security/howdy/recorders
/lib/security/howdy/recorders/ffmpeg_reader.py
/lib/security/howdy/recorders/pyv4l2_reader.py
/lib/security/howdy/recorders/v4l2.py
/lib/security/howdy/recorders/video_capture.py
/lib/security/howdy/recorders/__init__.py
/lib/security/howdy/pam.py
/lib/security/howdy/logo.png
/lib/security/howdy/cli.py
/lib/security/howdy/dlib-data
/lib/security/howdy/dlib-data/Readme.md
/lib/security/howdy/dlib-data/install.sh
/lib/security/howdy/compare.py
/lib/security/howdy/cli
/lib/security/howdy/cli/add.py
/lib/security/howdy/cli/test.py
/lib/security/howdy/cli/list.py
/lib/security/howdy/cli/disable.py
/lib/security/howdy/cli/__init__.py
/lib/security/howdy/cli/config.py
/lib/security/howdy/cli/snap.py
/lib/security/howdy/cli/clear.py
/lib/security/howdy/cli/remove.py
/lib/security/howdy/snapshot.py
/lib/security/howdy/pam-config
/lib/security/howdy/pam-config/howdy
/lib/security/howdy/config.ini
/usr
/usr/share
/usr/share/doc
/usr/share/doc/howdy
/usr/share/doc/howdy/changelog.gz
/usr/share/doc/howdy/copyright
/usr/share/man
/usr/share/man/man1
/usr/share/man/man1/howdy.1.gz
/usr/share/bash-completion
/usr/share/bash-completion/completions
/usr/share/bash-completion/completions/howdy
/usr/share/pam-configs
/usr/share/pam-configs/howdy
/usr/share/lintian
/usr/share/lintian/overrides
/usr/share/lintian/overrides/howdy

So what the problem with my installation?

The executable howdy is a link to the python file located in /lib/security/howdy/cli.py
$ where howdy
/usr/local/bin/howdy

$ ls -lah /usr/local/bin/howdy
lrwxrwxrwx  1 root root   26 Nov 13 09:40 howdy -> /lib/security/howdy/cli.py*

Try running the ln command to create that link.
sudo ln /lib/security/howdy/cli.py /usr/local/bin/howdy

I have also same problem, just create a symlink, your suggestion @Ozy-Viking is the way but for me do not work without use the -s option
sudo ln -s /lib/security/howdy/cli.py /usr/local/bin/howdy
Thanks for the tips!

I have the same problem, I found /lib/security/howdy/cli.py but could not find /usr/local/bin/howdy
or /usr/bin/howdy , I started my problem in #923


when enabled battery limit and ac adapter and external monitor connected, mac go sleeping when lid closed

Closed by release v1.1.4. Please reopen if you have the same issue with that release (with debug info).

thx, working


Readme: add needed django.contribe.sites to INSTALLED_APPS

dj-stripe depends on it and won't work (at least on django 1.10) without it.

Current coverage is 100% (diff: 100%)

Merging #410 into 1.0.0 will not change coverage

@@           1.0.0   #410   diff @@
===================================
  Files         23     23
  Lines       1554   1554
  Methods        0      0
  Messages       0      0
  Branches     184    184
===================================
  Hits        1554   1554
  Misses         0      0
  Partials       0      0

Powered by Codecov. Last update c859b23...a4428c8

Right. I'd like to find a good way to make the readme and docs more DRY... See #389.


Fix CircleCi build format

It looks like when we updated the build to CircleCi 2.x format, we didn't properly update the release portion. So while tests were correctly running on branches, on release tags (e.g., v0.x.y), no build was running at all, and therefore, we were not publishing new AMIs. We also weren't running the terraform fmt validation, so I'm guessing lots of issues will be flushed out with that too.
I've copied the CircleCi config from the Consul repo here, which I believe has the proper structure to publish AMIs on release.
This hopefully fixes #216.

Tests all passed on this branch. Now using a pre-release tag to check the AMI publishing: https://github.com/hashicorp/terraform-aws-vault/releases/tag/v0.13.12-test.

Hm, WTH... Why  did gruntwork-ci magically merge this PR?

OK...  I'm still not sure why my PR was auto merged... Just created another release to test if the release process actually works fully: https://github.com/hashicorp/terraform-aws-vault/releases/tag/v0.13.12-test.

OK, the release worked, and new artifacts were published. No idea what happened with the magical auto merge, but I believe this issue is now resolved.


Add tests to mapIterators

I added some tests to mapIterators and the result in my enviroment was:
map.forEach(cb) x 3,931 ops/sec ±3.24% (86 runs sampled)
for (let item of map) cb(item) x 4,256 ops/sec ±1.02% (88 runs sampled)
iterator x 4,279 ops/sec ±1.89% (86 runs sampled)
yield * x 1,389 ops/sec ±0.84% (91 runs sampled)
entriesForOfLoop x 4,527 ops/sec ±0.64% (89 runs sampled)
entriesForOfLoopKV x 2,730 ops/sec ±2.92% (83 runs sampled)
valuesForOfLoop x 6,085 ops/sec ±1.84% (90 runs sampled)
Fastest is valuesForOfLoop

Using for (let item of map.entries()) seems to be slightly faster than for (let item of map), and using map.values() is definitely the fastest - of course it is useful if you only need the values.
Using array destructuring in the callback (([k,v]) =>), which is pretty used these days, caused a huge drop of performance.

Very interesting! Thank you for sharing. Which version of node have you used?


Unable to use DSR mode with Geneve

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
When running using DSR mode with Geneve, I encounter some errors in my logs. Initially, my cluster never lost all load balancing ability, it seemed to rollback to SNAT mode. However, now it seems to have lost connectivity and I haven't been able to replicate the SNAT thing again.
Cilium Version
1.14.0-snapshot.2
Kernel Version
Linux rn6-k8s.va.internal.rocketnode.net 5.14.15-1.el8.elrepo.x86_64 #1 SMP Tue Oct 26 11:45:20 EDT 2021 x86_64 x86_64 x86_64 GNU/Linux
Kubernetes Version
Server Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.10", GitCommit:"5c1d2d4295f9b4eb12bfbf6429fdf989f2ca8a02", GitTreeState:"clean", BuildDate:"2023-01-18T19:08:10Z", GoVersion:"go1.19.5", Compiler:"gc", Platform:"linux/amd64"}
Sysdump
No response
Relevant log output
level=warning msg="JoinEP: Failed to compile" debug=true error="Failed to compile bpf_host.o: exit status 1" params="&{Source:bpf_host.c Output:bpf_host.o OutputType:obj Options:[]}" subsys=datapath-loader
level=error msg="BPF template object creation failed" bpfHeaderfileHash=8e852bc9424a68c770fa41787b003eaeaf1f7e6be6bd7ce7e533c197eaf71aea error="failed to compile template program /var/run/cilium/state/templates/8e852bc9424a68c770fa41787b003eaeaf1f7e6be6bd7ce7e533c197eaf71aea: Failed to compile bpf_host.o: exit status 1" subsys=datapath-loader
level=error msg="Error while rewriting endpoint BPF program" containerID= datapathPolicyRevision=0 desiredPolicyRevision=4 endpointID=1441 error="BPF template compilation failed: failed to compile template program /var/run/cilium/state/templates/8e852bc9424a68c770fa41787b003eaeaf1f7e6be6bd7ce7e533c197eaf71aea: Failed to compile bpf_host.o: exit status 1" identity=1 ipv4= ipv6= k8sPodName=/ subsys=endpoint
level=info msg="generating BPF for endpoint failed, keeping stale directory" containerID= datapathPolicyRevision=0 desiredPolicyRevision=4 endpointID=1441 error="BPF template compilation failed: failed to compile template program /var/run/cilium/state/templates/8e852bc9424a68c770fa41787b003eaeaf1f7e6be6bd7ce7e533c197eaf71aea: Failed to compile bpf_host.o: exit status 1" file-path=1441_next_fail identity=1 ipv4= ipv6= k8sPodName=/ subsys=endpoint
level=warning msg="Regeneration of endpoint failed" bpfCompilation=59.82442ms bpfLoadProg=0s bpfWaitForELF=60.000979ms bpfWriteELF=0s containerID= datapathPolicyRevision=0 desiredPolicyRevision=4 endpointID=1441 error="BPF template compilation failed: failed to compile template program /var/run/cilium/state/templates/8e852bc9424a68c770fa41787b003eaeaf1f7e6be6bd7ce7e533c197eaf71aea: Failed to compile bpf_host.o: exit status 1" identity=1 ipv4= ipv6= k8sPodName=/ mapSync="4.26µs" policyCalculation="22.14µs" prepareBuild="467.938µs" proxyConfiguration="8.521µs" proxyPolicyCalculation="2.794µs" proxyWaitForAck=0s reason="one or more identities created or deleted" subsys=endpoint total=60.709101ms waitingForCTClean="2.374µs" waitingForLock="7.473µs"
level=error msg="endpoint regeneration failed" containerID= datapathPolicyRevision=0 desiredPolicyRevision=4 endpointID=1441 error="BPF template compilation failed: failed to compile template program /var/run/cilium/state/templates/8e852bc9424a68c770fa41787b003eaeaf1f7e6be6bd7ce7e533c197eaf71aea: Failed to compile bpf_host.o: exit status 1" identity=1 ipv4= ipv6= k8sPodName=/ subsys=endpoint
level=info msg="regenerating all endpoints" reason="one or more identities created or deleted" subsys=endpoint-manager
level=error msg="Failed to compile bpf_host.o: exit status 1" compiler-pid=2028 linker-pid=2029 subsys=datapath-loader
level=warning msg="In file included from /var/lib/cilium/bpf/bpf_host.c:50:" subsys=datapath-loader
level=warning msg="/var/lib/cilium/bpf/lib/nodeport.h:1518:28: error: implicit conversion loses integer precision: 'unsigned long' to '__u16' (aka 'unsigned short') [-Werror,-Wimplicit-int-conversion]" subsys=datapath-loader
level=warning msg="                sizeof(struct genevehdr) + ETH_HLEN;" subsys=datapath-loader
level=warning msg="                ~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~" subsys=datapath-loader
level=warning msg="1 error generated." subsys=datapath-loader

Anything else?
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

I think this issue is caused by L2-less device. ETH_HLEN is explicitly defined as uint32 if there's any L2-less device, and it causes implicit conversion loses integer precision when we calculate encap_len using ETH_HLEN. We need to explicitly convert ETH_LEN uint16 in encap_geneve_dsr_opt[4,6]
If there's any L2-less device, ETH_HLEN is explicitly defined as uint32 here.
https://github.com/cilium/cilium/blob/550aafcac9db96dc25d63b62f5db4c1535cbfbe2/pkg/datapath/linux/config/config.go#L820
And is replaced with "0" here
https://github.com/cilium/cilium/blob/d38dda49ef835309a4760d1577467973d2496d41/pkg/datapath/loader/loader.go#L154
context:
https://cilium.slack.com/archives/C1MATJ5U5/p1683001819943969


Make Music Not Restart When Going To A Sublevel (Please)

If you use the same music in different sublevels, it will restart when you go from one area to another. It would be nice if there was a way to make the music not restart, maybe a tick box after the music or even a word in the music's name.
(e.g.: "underground-norestart") and you put it in every map that uses it.

d42d680564af4104fb8bee8971aa2729ba803d68


[ObjectStore] MultipartUpload::complete fails on WSL when writing to /mnt/

Describe the bug
Using LocalFileSystem on WSL + BufWriter I get the following error:
file.metadata() fails after std::fs::rename with FileNotFound but is reported as an aborted upload
To Reproduce
Use object_store::buffered::BufWriter to write a big enough file to the windows filesystem when running though WSL.
Expected behavior
File write succeeds.
Additional context
Using object_store-0.11.0.
Our services are actually writing to S3, but the local dev environment writes to the local filesystem. I could not reproduce the bug when writing to the linux filesystem, but it happens every time I write a 50MB+ file to the windows file system with the exe running on the linux side.

Possibly related to https://github.com/apache/arrow-rs/pull/5094
My guess is that the WSL bind mounts don't quite match standard filesystem semantics, much like blobfuse, and so issues like this arise. It may be that a similar workaround to #5094 is possible for multipart uploads. An interesting data point might be to confirm that this always occurs with the multipart codepath, e.g. by using ObjectStore::put_multipart manually.


Content height jumping during SSR with React

If you wrap something in  during SSR it will be rendered with height: 0 and only on client side it will calculate the height of the content that is inside and render it properly which results in a lot of jumping content during renders. By reading the source code it seems like it is intended:
init() {
    // Save a reference to the instance, so we know this DOM node has already been instancied
    SimpleBar.instances.set(this.el, this);
    // We stop here on server-side
    if (canUseDOM) {
      this.initDOM();
      this.scrollbarWidth = this.getScrollbarWidth();
      this.recalculate();
      this.initListeners();
    }
  }

But I find it very wierd that nobody is bothered by it, so I thought I am missing something? So I guess my only questions are: Is it intended and it is just the limitation of the library or am doing something wrong and I am the only dumbass with this issue?

Hi,
To avoid this to happen you need to make sure the element you're applying SimpleBar to is behaving well before applying SimpleBar to it. There is no "one solution fits them all" for this since it depends of your layout/css but what you need to do is have your parent element have a defined height.
Keep in mind that it's not only for SSR but if Javascript is disabled, your layout would be broken as well


Clear Content By click Button

how clear all content by click on one button?
is there any commend?

var text = $('#editordiv');
text.html('');


ByteString literals fail to compile

Area
[] Plutus Foundation Related to the GHC plugin, Haskell-to-Plutus compiler, on-chain code
[X] Plutus Application Framework Related to the Plutus application backend (PAB), emulator, Plutus libraries
[] Marlowe Related to Marlowe
[] Other Any other topic (Playgrounds, etc.)
Summary
ByteString literals do not compile. For example, this will fail to compile:
test :: CompiledCode ByteString
test = $$(compile [|| "snacks" ||])

Steps to reproduce
Steps to reproduce the behavior:

Put the above example into a source file.
Try to compile it.
Watch the errors appear.
Lament your woes.

Expected behavior
The ByteString literal should compile.
System info (please complete the following information):

OS: Arch
Plutus version or commit hash: According to cabal freeze file:

any.plutus-contract ==<IP_ADDRESS>,
any.plutus-core ==<IP_ADDRESS>,
any.plutus-ledger ==<IP_ADDRESS>,
any.plutus-ledger-api ==<IP_ADDRESS>,
any.plutus-pab ==<IP_ADDRESS>,
any.plutus-tx ==<IP_ADDRESS>,
any.plutus-tx-plugin ==<IP_ADDRESS>,
any.plutus-use-cases ==<IP_ADDRESS>,

Hi! Thanks for the issue! Yeah, it's a known problem (#3156). Should be fixed soon.
I'm closing this one as a duplicate.


Adding documentation for control plane / data plane split, and completing airflow helpers migration

Summary
Adding docs on control plane, and filling a gap in the airflow oss migration.
Why / Goal
Improving documentation.
Reviewers
@nikhilsimha @hzding621

merge it as is


🐛 搜索页面仅有一个用户时，右导航按钮错位

如图：

搜索页面左右导航条到最后一条时随机不消失。

这是由于没有注意到CSS标识符不能以数字开头，而用户卡片id直接赋为UUID，UUID可能会以数字开头，导致报错。

In CSS, identifiers (including element names, classes, and IDs in selectors) can contain only the characters [a-zA-Z0-9] and ISO 10646 characters U+00A0 and higher, plus the hyphen (-) and the underscore (_); they cannot start with a digit, two hyphens, or a hyphen followed by a digit. Identifiers can also contain escaped characters and any ISO 10646 character as a numeric code (see next item). For instance, the identifier "B&W?" may be written as "B&W?" or "B\26 W\3F".

参见：https://www.w3.org/TR/CSS21/syndata.html#value-def-identifier


Feat(.github): Updated Github Action for Issue and Bug Reporting Templates

[ ] Have you renamed the PR title to something meaningful?

yes

Related Issue

Closes #156

Description
This PR enhances both the issue and feature templates to improve clarity, user experience, and streamline the process for contributors. The updated templates now feature more structured sections, clear instructions, and specific input fields that help ensure thorough bug reports and feature requests.

How Has This Been Tested?

Tested Locally

Screenshots (if applicable)

Type of Change

[ ] Bug fix
[x] New feature
[ ] Code style update
[ ] Breaking change
[x] Documentation update

Ok we can do this!


adding sample projects - http appender, deployer for deploying text files, custom converter pattern to read host details

This was sent to try out a POC to write an http-appender to get the deployment logs for dep-sync support to c5. The changes go to hamming-release-poc branch. Closing as we don't maintain this anymore


Create zjut

ZheJiang University of Technology
Here is the official link:http://www.wsc.zjut.edu.cn/zjuten/index.jsp
You can see a description of an IT-related long-term (> 1 year) course offered by the university here:
http://www.wsc.zjut.edu.cn/zjuten/newsDetail.jsp?id=2687&bigclassid=1&bigclassid=71&sid=71

You can see the four years  IT courses here
http://www.wsc.zjut.edu.cn/zjuten/BigClass.jsp?bigclassid=5&sid=41

@Ereebay Pull request merged. Thank you!


FIx pyqt5 build

Can you please rebase, so that there is just one commit to merge?
@balister Please review and test.

Are you sure that moving inherit  python3native python3-dir to common python-pyqt5.inc does not make python-pyqt5 same as python3-pyqt5?

Yes native dependencies are just for building they don’t have any bearing on runtime

I checked and this is wrong: sys.hexversion (the version of python running) is the a way pyqt decides to build for python2 or 3 variant. Just grep for sys.hexversion there are lot of 'if sys.hexversion >= 0x03000000:'. Your patch breaks python-pyqt5.

Ok this change is not necessary but rather a cleanup I will send a v2 without it


Fix destroyed fork backpressure.

See https://github.com/caolan/highland/issues/179#issuecomment-160243577 for description.

Very nice implementation.


Detect ksh

Description
Relates to PFK4711C
Associated issue: #2720

This PR:

adds ksh to the "Unix direct remote command execution" rule 932150
adds a corresponding test for rule 932150 to detect ksh

Merge conflicts. Rebasing.


Add A New Generative Model

Hi RewardBench Team 👋,
We have updated a 70B version generative model:
SF-Foundation/TextEval-Llama3.1-70B
Our local evaluation metrics for the model is listed as bellow:
{'Chat': 0.946927374301676, 'Chat Hard': 0.9035087719298246, 'Safety': 0.9318428922428922, 'Reasoning': 0.9646321001800622}
How to Run Evaluation Script
For this generative model, it's okay to evaluate it with the default scripts/run_generative.py script. Please notice that we need at least 8 gpus to run run_generative.py script, and export VLLM_WORKER_MULTIPROC_METHOD=spawn is required for vLLM multi-gpu inference.
export VLLM_WORKER_MULTIPROC_METHOD=spawn
cd reward-bench
python scripts/run_generative.py --model=SF-Foundation/TextEval-Llama3.1-70B --num_gpus 8

We would like to add this new generative model to the RewardBench LeaderBoard.
Thank you!

@ZhichaoWang970201 will be updated upon restart.


Qemu: -redir deprecation warning

QEmu's -redir option is deprecated, we should use -net or -netdev instead
$qemu-system-x86_64: -redir tcp:50080::80: The -redir option is deprecated. Please use '-netdev user,hostfwd=...' instead.
$qemu-system-x86_64: -redir tcp:50443::443: The -redir option is deprecated. Please use '-netdev user,hostfwd=...' instead.

Do you know what's the exact alternative? If so, I would merge a pull-request for that.

Do you know what's the exact alternative? If so, I would merge a pull-request for that.

Well the net commands are obsolete but they're working

It should be easy to do, just only didn't have time to work on it.


[Rust docs/SE] Broken Link

https://docs.substrate.io/rustdocs/latest/sc_rpc_api/offchain/trait.OffchainApi.html

Latest has been deprecated, we use master only , and only the github docs directly throughout now. Anything mussing that is an error in the docs here. Where did you discover thus link?
Should be in here now https://paritytech.github.io/substrate/master/sc_rpc_api/offchain/index.html

I discovered it here - https://substrate.stackexchange.com/questions/1320/how-to-extend-a-custom-rpc-service-to-query-the-off-chain-storage

Thanks for the report here, I will update that post.
Please do us a great favor moving forward & update the SE when you spot things like this, anyone can edit  a post and help get links updated. AFAIK there are no plans to try and update all links in our ecosystem with #1132 in place, and many existing links need to be updated by the authors and community of such content.


/Media dir missing most images required.

All labs, all instructions:  references images that are not present in the /media dir, leading to nearly all instructions have multiple broken images.

Hello contributor,
Thank you for your contribution! We are processing your suggestions and we will update you shortly.
Kind regards,
Microsoft Worldwide Learning Team

Fixed.
https://github.com/MicrosoftLearning/AZ-204-DevelopingSolutionsforMicrosoftAzure.fr-fr/tree/OLPRODLOC/Instructions/Labs/media


feat: add faq from 22jul - 28jul 2023 for CD

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the maintainers.
The following screenshot shows the questions added:

What Type of PR is This?

[ ] Issue
[x] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[x] Optional Screen Shoot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app


Add a new Cypress E2E test runner that executes against a fully configured environment

Description
In some previous releases, we worked on building out test setup scripts (#1291) and a local manual test environment (#1292), which gives us the ability to do true E2E manual tests to confirm all features are working as expected when running together.
Our existing Cypress suites for the admin-ui and privacy-center are great, but they are isolated to their specific applications and tend to stub out their backends for performance. Therefore, there's still an open need for an E2E test runner to use for regression tests on an ongoing basis.
Once the runner is configured, let's put it to work by defining a core smoke test for releases. We should ensure this can run against our local test env first, but I want to immediately start using this against some hosted staging & demo environments in the short-term, so let's ensure that any URLs are easy to configure and override (e.g. http://localhost:3000 will quickly become something like https://fides.fides-staging.ethyca.com/)
In addition, let's signup for Cypress Cloud and publish results there, it's a great product!
Acceptance Criteria

MUST implement a new Cypress runner to run E2E tests, targeting the local "manual test" environment (see #1292)
MUST support targeting different hosts via environment variables, so we can run against staging / demo / etc.
MUST have a nox session (e.g. nox -s e2e_test) that runs the Cypress suite in headless mode
MUST configure the test reporter to publish results to our Cypress Cloud account
MUST write a single Cypress E2E test that runs a simple smoke test covering:

Confirm can login to the Admin UI
Confirm that the Postgres & Mongo connectors are configured
Confirm that the Privacy Center can be accessed
Submit an access request via the Privacy Center
Approve the access request via the Admin UI
Confirm the access request succeeds

One note from this convo:

not running against the live backend in those E2E tests is a bug, not a feature. we’ve scoped out work to fix that here

I am a fan of FE+BE integrated regression test. However, I would say the 80/20 rule for cypress tests is that 80% should be using stubbed endpoints. Developers should be live-running the Cypress tests for a feature when changing it. An actual BE is usually bad for this because:

It will be slow
Create/Deletes are going to get out of sync
The data that is useful for regressions is a separate concern from what is useful for covering a UI feature
The BE might not even be updated yet (developing features in tandem like Classify UI).

I think this ticket is pointing in the right direction: we should have a distinct subset of test that don't stub anything. I just want to make it clear the goal isn't to convert all cypress tests to run against a live API.

@ssangervasi totally fair - I've updated the title & description here to be more appropriate - you're right that we shouldn't need to replace the existing suites, and in fact an E2E runner is really just one more to add.

Commenting to flag that this work is blocked by https://github.com/ethyca/fides/issues/2385

Closed by https://github.com/ethyca/fides/pull/2241


release eks go 1.20.8

Issue #, if available:
#1142
Description of changes:
Bump 1.20 git_tag for latest security release
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve


create collection to parse and detect auth fail on promox api

following this thread, we need to create a parser and scenario to detect auth failure on promox api parser example.

Attention, there are 2 different Proxmox products on the market:
Proxmox PVE (Virtualization) seems to log to 2 different log files:
/var/log/daemon.log
/var/log/syslog
sample log entry:
Jan 22 10:26:53 nas proxmox-backup-api[3382]: authentication failure; rhost=::ffff:<IP_ADDRESS> user=aasfas@pam msg=user account disabled or expired.
Proxmox PBS (Backup Server) => /var/log/proxmox-backup/api/auth.log
sample log entries:
2021-01-22T10:24:58+01:00: authentication failure; rhost=::ffff:217.xxx.xxx.168 user=root@pam msg=AUTH_ERR (7)
2021-01-22T10:24:58+01:00: successful auth for user 'root@pam'

Attention, there are 2 different Proxmox products on the market:
Proxmox PVE (Virtualization) seems to log to 2 different log files:
/var/log/daemon.log
/var/log/syslog
sample log entry:
Jan 22 10:26:53 nas proxmox-backup-api[3382]: authentication failure; rhost=::ffff:<IP_ADDRESS> user=aasfas@pam msg=user account disabled or expired.
Proxmox PBS (Backup Server) => /var/log/proxmox-backup/api/auth.log
sample log entries:
2021-01-22T10:24:58+01:00: authentication failure; rhost=::ffff:217.xxx.xxx.168 user=root@pam msg=AUTH_ERR (7)
2021-01-22T10:24:58+01:00: successful auth for user 'root@pam'

proxmox has been added by: https://hub.crowdsec.net/author/fulljackz/collections/proxmox


ts-node-dev doesn't allow graceful shutdowns when managed by external processes

Issue description
If ts-node-dev is running a process that has graceful shutdowns, those graceful shutdowns will not be honored in situations such as a kubernetes rollout restart, where another process above ts-node-dev is managing the execution.
Context
Some of the context is on this pull request that attempted to fix the issue: https://github.com/wclr/ts-node-dev/pull/269
Our current codebase does not wait for a graceful shutdown when managed by another external process.
Did you try to run with ts-node?
Yes, this works with ts-node. The fix was merged here: https://github.com/TypeStrong/ts-node/pull/419
Example
Here is an example. I created a simple express server that has the following graceful shutdown logic:
async function shutdown(signal: string, server: Server) {
  console.log(`${signal} received, stopping incoming requests`);

  server.close(() => {
    console.log('incoming requests stopped, waiting for existing connections to finish');

    setTimeout(() => {
      console.log('closing mongodb connection');
      mongoose.connection.close(() => {
        console.log('mongoDB connection closed');
        console.log('exiting successfully');
        process.exit(0);
      });
    }, WAIT_EXISTING_REQS_MILLIS);
  });

  setTimeout(() => {
    console.log('graceful shutdown timed out, forcefully shutting down');
    process.exit(1);
  }, SHUTDOWN_TIMEOUT_MILLIS);
}

The server is being started via ts-node-dev inside a docker container managed by kubernetes.
When ts-node-dev detects a change within the container, it successfully goes through the shutdown logic:
[server] connected to mongodb
[server] Listening on port 3000
Syncing 1 files for anthonyalayo/server:1ccaf904e3c28daaf2e77093a18ccea816264ea597f9d64baee8e1d5eb8fd4cb
Watching for changes...
[server] [INFO] 04:09:57 Restarting: /app/server/src/index.ts has been modified
[server] SIGTERM received, stopping incoming requests
[server] incoming requests stopped, waiting for existing connections to finish
[server] closing mongodb connection
[server] mongoDB connection closed
[server] exiting successfully
[server] connected to mongodb
[server] Listening on port 3000

You can see that the shutdown logic completes entirely and the server starts back up.
Now when attempting to delete a pod via kubectl to mimic a rollout:
kubectl delete pod server-depl-d98998677-7s2nt

The following is output:
[server] SIGTERM received, stopping incoming requests
[server] incoming requests stopped, waiting for existing connections to finish
[server] yarn run v1.22.5
[server] $ ts-node-dev --poll src/index.ts
[server] [INFO] 04:10:27 ts-node-dev ver. 1.1.8 (using ts-node ver. 9.1.1, typescript ver. 4.3.5)
[server] connected to mongodb
[server] Listening on port 3000

While the PR I created fixed the issue when trying it out in practice, I am not able to get our test suite passing. Attempting to debug the test suite has been unfruitful, as there is extremely limited debuggability for either printing or breakpoints with these child processes.
If anyone can tackle it, that would be appreciated.

I have published my fork as a scoped package as a workaround in the meantime:
https://www.npmjs.com/package/@anthonyalayo/ts-node-dev

I spent two hours struggling with this until I narrowed it down to ts-node-dev not waiting for the graceful shutdown. Thanks for your attempt at fixing this, @anthonyalayo. I tried your fork and can confirm it works for me as well.
Any chance this can be fixed?

@thodoo thanks for the issue validation!
Honestly, I need some help from the maintainer who wrote the unit tests. I spent hours debugging them to get them working

any updates regarding this issue?

any updates?