text:
Deprecated feature used, fix before chef 13

In testing the chef-client 12.8.0 prerelease (12.7.2 is the current latest stable), I'm getting the following warnings about deprecated features.
Running handlers:
Running handlers complete

Deprecated features used!
  An attempt was made to change application_name from "NetDocuments/neweb2" to nil by calling application_name(nil). In Chef 12, this does a get rather than a set. In Chef 13, this will change to set the value to nil. at 1 location:
    - c:/chef/local-mode-cache/cache/cookbooks/iis/providers/vdir.rb:123:in `load_current_resource'����������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������

The offending line is here:
https://github.com/chef-cookbooks/iis/blob/master/providers/vdir.rb#L123
And the line in chef is here:
https://github.com/chef/chef/blob/a030711a57e126f58b2e897c915d430e67cb7d13/lib/chef/property.rb#L276
I've spent a few minutes trying to figure out how to fix this, but it is a little above my ruby abilities.

it appears that application_name is a reserved keyword in chef 13.  the fix
would be simply to change this property name to name or something else
On Tue, Mar 1, 2016 at 12:59 PM, Spencer Owen notifications@github.com
wrote:

In testing the chef-client 12.8.0 prerelease (12.7.2 is the current latest
stable), I'm getting the following warnings about deprecated features.
Running handlers:Running handlers complete
Deprecated features used!
An attempt was made to change application_name from "NetDocuments/neweb2" to nil by calling application_name(nil). In Chef 12, this does a get rather than a set. In Chef 13, this will change to set the value to nil. at 1 location:
- c:/chef/local-mode-cache/cache/cookbooks/iis/providers/vdir.rb:123:in `load_current_resource'
The offending line is here:
https://github.com/chef-cookbooks/iis/blob/master/providers/vdir.rb#L123
And the line in chef is here:
https://github.com/chef/chef/blob/a030711a57e126f58b2e897c915d430e67cb7d13/lib/chef/property.rb#L276
I've spent a few minutes trying to figure out how to fix this, but it is a
little above my ruby abilities.
—
Reply to this email directly or view it on GitHub
https://github.com/chef-cookbooks/iis/issues/253.

From my testing, it appears that more than a simple rename is needed.
I changed all instances of application_name to derp_name with the same results.

An attempt was made to change derp_name from "NetDocuments/neweb2" to nil by calling derp_name(nil). In Chef 12, this does a get rather than a set. In Chef 13, this will change to set the value to nil. at 1 location:
- c:/chef/local-mode-cache/cache/cookbooks/iis/providers/vdir.rb:123:in `load_current_resource'�����

This will take more investigation.

Ah this is because we are calling:
@current_resource.application_name(application_name_check)
which could end up being
@current_resource.application_name(nil)
which changes the type of
@current_resource.application_name
however it appears it is detecting the type wrong since it is actually just a string.

Adding a final else eliminates the error
def application_name_check
  if !new_resource.derp_name.include?('/') && !new_resource.derp_name.end_with?('/')
    new_resource.derp_name("#{new_resource.derp_name}/").to_s
  elsif new_resource.derp_name.chomp('/').include?('/') && new_resource.derp_name.end_with?('/')
    new_resource.derp_name("#{new_resource.derp_name}".chomp('/')).to_s
  else
    new_resource.derp_name("#{new_resource.derp_name}").to_s
  end
end

Looks good to me, I think all we need is the else not the name change.  Put in a pull request whenever you verify.

repo: chef-cookbooks/iis


text:
Use chef-table Angular component for all auth tables

PR #2153 introduced an Angular equivalent of the StencilJS <chef-table> and applied it to the token list page. Temporarily, this Angular component uses <chef-table-new> as its root-level element, which is necessary until the UI team is ready to examine all the call sites of <chef-table> and drop the StencilJS version.
In the meantime, auth team decided to swap in the Angular component for all Auth tables (Token list already complete):

Policy list
Project list
Role list
User list
Team list
Policy member list
Team users list
Project rule list

To swap in the Angular component, change the tags in each template per this table:

StencilJS
Angular

chef-table
chef-table-new

chef-thead
chef-table-header

chef-tbody
chef-table-body

chef-tr
chef-table-row

chef-th
chef-table-header-cell

chef-td
chef-table-cell

Check the corresponding Cypress test file for the same substitutions.

closed by https://github.com/chef/automate/pull/2196

source: gharchive/issue

authors: blakestier sdelano

repo: chef/automate

license_type: permissive

license_source: github-api


text:
inspec report size reduction: part two

Definition of Done
follow up to: https://github.com/chef/automate/issues/3087

create change in audit cookbook that coincides with profile metadata api that was added in automate
audit cb, scan jobs: limit inspec result messages to 2k characters, include note in control results that full result was truncated for size
audit cb, scan jobs: limit array of results to  : include message that array results were truncated on the control level

https://github.com/chef-cookbooks/audit/issues/422

This can be closed now as https://github.com/chef-cookbooks/audit/issues/422 has been shipped along with the changes in automate for the scan jobs initiated inspec execs. Cheers!

authors: alexpop vjeffrey


text:
Describe how to install Chef Infra Server using Chef Automate

:nut_and_bolt: Description: What code changed, and why?
Describe how to use the chef-automate command line tool to install Chef Infra Server, with or without Chef Automate itself.
Fixes #2814
:chains: Related Resources
:+1: Definition of Done
:athletic_shoe: How to Build and Test the Change
:white_check_mark: Checklist

[x] I have read the CONTRIBUTING document.
[ ] Tests added/updated?
[x] Docs added/updated?
[x] All commits have been signed-off for the Developer Certification of Origin.

:camera: Screenshots, if applicable

@mjingle I believe I've addressed your comments so far; let me know if you have others.

source: gharchive/pull-request


text:
SSH backend / Readme error?

Hi,
I'm a bit confused. The Readme still links to the old chef-metal-ssh project at https://github.com/chef/chef-provisioning/blame/master/README.md#L154 while the CI and gem buttons at the top link to the https://github.com/chef/chef-provisioning-ssh project.
Together with the warning in Line 154 it's easy to come to the conclusion that there is no working SSH backend available and drive people to e.g. terraform instead.

I'm looking for a way to automation the configuration of network devices which only have a ssh interface.  Did you manage to move forward at all?  either with chef-provisioning or terraform?
TIA

authors: digitalGaz rmoriz

repo: chef/chef-provisioning

license_source: bigquery


text:
Fix for issue #2666

Added method to path_helper.rb to convert Linux-style absolute paths to Windows-style absolute paths that begin with a drive letter
Moved methods that finds roles files into a separate method and then added call to new path_helper method to fix Windows issue #2666
Added unit tests
Tried with Vagrant script against Windows VM (Virtualbox), checking that add_role and add_recipe work

Hi. I am an automated pull request bot named Curry. There are commits in this pull request whose authors are not yet authorized to contribute to Chef Software, Inc. projects or are using a non-GitHub verified email address. To become authorized to contribute, you will need to sign the Contributor License Agreement (CLA) as an individual or on behalf of your company. You can read more on Chef's blog.
GitHub Users Who Are Not Authorized To Contribute
The following GitHub users do not appear to have signed a CLA:

@NickMRamirez

Please sign the CLA here.

Hi. Your friendly Curry bot here. Just letting you know that all commit authors have become authorized to contribute. I have added the "Signed CLA" label to this issue so it can easily be found in the future.

In other parts of the code, I've seen the use of env['SYSTEMDRIVE'] when figuring out paths. If we don't use absolute_path, then possibly that?

I am now wondering if this is an issue with Vagrant when using a Windows guest and not an issue with Chef. There's a Vagrant config option called provisioning_path.
Shared Chef Options:

provisioning_path (string) - The path on the remote machine where Vagrant will store all necessary
files for provisioning such as cookbooks, configurations, etc. This path must be world writable. By
default this is /tmp/vagrant-chef-# where "#" is replaced by a unique counter.

Given that, in my experiments, the path /tmp/vagrant-chef is being used on a Windows guest, maybe Vagrant should have a check for Windows and use a different path by default when on Windows?
I will experiment some more.

authors: NickMRamirez chef-supermarket

repo: chef/chef


text:
MSYS-807 fix mount point error windows

Description
According to mount resource documentation for mount_type, "The directory (or path) in which the device is to be mounted. Default value: the name of the resource block. A customer had tried this and was getting errors when the name was anything but the mount_point. Looking at lib/chef/provider/mount/windows.rb, it shows that net_use is hard-wired to use only the resource name, which conflicts with the documentation. If we change it from name to mount_point, then it will work according to how the documentation specifies.
Windows mount uses new_resource.name instead of new_resource.mount_point when connecting to a CIFS share
Resolved issue
https://getchef.zendesk.com/agent/tickets/18684

obviously the change itself is simple enough that I'm fine with it.
Can we have a unit or integration test here?

authors: btm dheerajd-msys


text:
🛑 tt is down

In 5309ac2, tt (https://telebot-app-serverless-i7z8-chenhaonanniubi.vercel.app/checkhealth) was down:

HTTP code: 500
Response time: 2810 ms

Resolved: tt is back up in e8b0141 after 11 minutes.

repo: chenhaonanniubi/upptime

license: MIT


text:
🛑 tt is down

In 932c0a0, tt (https://telebot-app-serverless-i7z8-chenhaonanniubi.vercel.app/checkhealth) was down:

HTTP code: 500
Response time: 3003 ms

Resolved: tt is back up in 6e300b0 after 11 minutes.


text:
fix: Fix problem with 'verifyStatus=true' parameter in '/credential/verify' API [DEV-3170]

[x] Fix decodeCredentialJWT function in cheqd-did-provider
[x] Bump @cheqd/did-provider-cheqd version package.

Task linked: DEV-3170 Credential-Service: Fix problem with 'verifyStatus=true' parameter in '/credential/verify' API

authors: abdulla-ashurov ankurdotb

repo: cheqd/credential-service


text:
🛑 Chequeado is down

In d572e85, Chequeado (https://chequeado.com) was down:

HTTP code: 502
Response time: 9084 ms

Resolved: Chequeado is back up in 388d5b8.

repo: chequeado/status


text:
Allow setting access token in the app

Fixes #44 by adding a form in the app where the user can set their GitHub access token.

/cc @probablycorey

Opened #52 as a way to further enhance this.

license: mit


text:
Fix triggers on angular strap drop down menu items

passed in raw DOM element reference instead of id to UserVoice.push()
avoided JS error if UserVoice init fails and identify param is specified
removed UserVoice trigger if DOM element is destroyed

More detailed explanations may be found in the commit descriptions, but in general the changes done here allow us to apply UserVoice triggers to angular-strap drop-down menu items which otherwise have the following issues:

their DOM gets constructed before getting attached to the main DOM
we want the UserVoice dialog to close automatically in case the drop-down menu closes

Nice. Looks good. 👍

This has been published as 5.1.0.

authors: chesleybrown jurko-gospodnetic


text:
Console formatter calculates root path incorrectly, and there's no clean way to change it

I have a somewhat oddball project that pulls in some Rails engines as gems without actually being a Rails application. When I run the tests under Simplecov, the console formatter is producing output of the form:
| 90.91% | Usersmynameproject-dirlibmodule... | 11 | 1 | 15                 |

Running the rake task in the debugger, it seems as though the problem is in how Simplecov::Formatter::Console calculates the root path used for simplifying filenames in the output.
Because my project isn't actually a Rails app, but has the Rails constant defined, Simplecov::Formatter::Console tries to use Rails.root, which is nil, and ends up stripping all / from the filenames.
From the source, it seems as though I should be able to use the :ROOT constant to set the root path used for simplifying filenames in the console output. However, this doesn't work.
If I set Simplecov::Formatter::Console::ROOT = Dir.pwd in my spec_helper.rb, Module.const_defined? :ROOT returns false, and it's ignored.
If I set Module::ROOT = Dir.pwd, Module.const_defined? returns true, but Simplecov::Formatter::Console::ROOT is undefined, and I get NameError: uninitialized constant.
I can work around this by setting both constants, but I don't think this is what the code intends.

What about implementing Rails.root to return the correct path, since you have that defined? Is that an option for you?

I think that should do it either way. Just pushed 0.3.1. Let me know if you still have trouble.

I think that'll fix it, but I still don't think Module.const_defined? is doing what you meant it to.

Yeah, you're probably right about that. I'm not actively using this now, so don't want to break any other existing stuff.

repo: chetan/simplecov-console


text:
What is the status of StaticBitsets?

Hi @chethega
I happen to need an isbits bitset. I thought about starting up developing one starting up with  your code from https://github.com/chethega/StaticArrays.jl/ , I also noticed you've mentioned an intention to develop a stand-alone package in https://github.com/JuliaArrays/StaticArrays.jl/pull/647.
What is the currently most-recent version of your effort in developing the Static versionof Bitsets?
Is there an important technical reason you ceased the development (or was it just lack of time/motivation)?

I happen to be interested in static sets, too :)

Hi!
Can I use your code for research purposes? If yes, under which license?
Sasha

Hi!
Can I use your code for research purposes? If yes, under which license?
Sasha

authors: Luapulu adamryczkowski sashakolpakov


text:
Add support for alternative response_types

A number of OAuth providers prefer response_type=code instead of
response_type=token (discovered following the links provided in the main page -
https://code.google.com/p/gwt-oauth2/), and one provider (Clever -
https://clever.com/developers/docs#identity-api-sso-oauth2-flow-section)
requires response_type=code - it fails when set to token.

Unfortunately, token is hardcoded into the AuthRequest, so there is no way for
me to change the type dynamically, which means that I'll have to grab the code,
modify one word, and include the modified code in our project.  This is clearly
not the optimal method.

Thank you!

Original issue reported on code.google.com by rhar...@classworks.com on 29 Sep 2014 at 1:37

Bluesky010946454@gmail.com

authors: GoogleCodeExporter chetsmartboy


text:
Cannot run examples in Go 1.8

import error, missing definitions.
run auto encoder:
go run main.go
command-line-arguments
./main.go:46: undefined: Label
./main.go:47: undefined: RawImage
./main.go:62: undefined: readLabelFile
./main.go:62: undefined: open
./main.go:66: undefined: readImageFile
./main.go:66: undefined: open
./main.go:70: undefined: prepareX
./main.go:71: undefined: prepareY
./main.go:154: undefined: NewStackedDA
./main.go:202: undefined: visualizeRow
./main.go:202: too many errors

try go run *.go
The program is split into multiple files

Note you will also need the files from Yann LeCun's website for the MNIST data (I'm on my way out right now so if you haven't found it by the time I get back in 5 hrs I'll find it for you)

Also the stackedDA example is quite stale. Probably hasn't kept up with all the changes. It'll be fixed in the upcoming merge

go run *.go
is ok.
Go 1.8's import is changed. It will not search go-files in the same folder.
Move all other-files to other packages then main-package may solve the problem.

Oh I've always run go run *.go. I didn't know you could run go run main.go
Xuanyi Chew
@chewxy on Twitter
Read: my blog http://blog.chewxy.com
+61403928398
On Wed, Apr 19, 2017 at 5:36 PM, Linker Lin notifications@github.com
wrote:

go run *.go
is ok.
Go 1.8's import is changed. It will not search go-files in the same folder.
Move all other-files to other packages then main-package may solve the
problem.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/chewxy/gorgonia/issues/108#issuecomment-295140896,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAczUqPWy4BW-jwyuKZAAbRnBwaNhOXqks5rxbl1gaJpZM4NBSbY
.

authors: chewxy linkerlin

repo: chewxy/gorgonia


text:
[BUG] Capture QuickAdd with "Add Command" doesn't respect the "Open" setting

Describe the bug
A capture that has been added as a command, does not respect the "Open" setting.
If you trigger the capture via "Run QuickAdd", it works as expected.
To Reproduce
Steps to reproduce the behavior:

Create a capture with "Open" toggled on
Enable "Add command" lightning bolt
Trigger command via QuickAdd: [the name of your capture]
File is written to, but not opened.
Trigger command via QuickAdd: Run QuickAdd
File is opened as expected

Screenshots

Desktop (please complete the following information):

OS: MacOS Big Sur

Hey! Thanks for reporting this.
Does it work if you restart Obsidian?

It does! 👯

authors: chhoumann timkelty

repo: chhoumann/quickadd


text:
🛑 36kr -实时快讯(newsflashes) is down

In eb99189, 36kr -实时快讯(newsflashes) (https://rssinn.com/36kr/newsflashes/) was down:

HTTP code: 502
Response time: 119 ms

Resolved: 36kr -实时快讯(newsflashes) is back up in 229875d.

repo: chinobing/upptime-rssinn


text:
🛑 36kr -实时快讯(newsflashes) is down

In 61bb697, 36kr -实时快讯(newsflashes) (https://rssinn.com/36kr/newsflashes) was down:

HTTP code: 404
Response time: 10192 ms

Resolved: 36kr -实时快讯(newsflashes) is back up in 654d519.


text:
🛑 36kr -最新文章(latest) is down

In d5e4a46, 36kr -最新文章(latest) (https://rssinn.com/36kr/latest) was down:

HTTP code: 404
Response time: 21194 ms

Resolved: 36kr -最新文章(latest) is back up in 0381164.


text:
Wrong position of expressions in assignment pattern

According to standard (37.57 Expressions 5)):
For an operation of type vpiAssignmentPatternOp, the operand iteration shall return the expressions as if the
assignment pattern were written with the positional notation. Nesting of assignment patterns shall be preserved.
Example 1:
struct {
  int A;
  struct {
    logic B;
    real C;
  } BC1, BC2;
} ABC = '{BC1: '{1'b1, 1.0}, int: 0, BC2: '{default: 0}};
The assignment pattern that initializes the struct variable ABC uses member, type, and default keys. The
vpiOperand traversal would represent this assignment pattern expression as:
'{0, '{1'b1, 1.0}, '{0, 0}}
or some other equivalent positional assignment pattern.

Surelog doesn't return expressions as if the assignment pattern were written with the positional notation:
   |vpiVariables:
   \_struct_var: (work@dut.ABC), line:8:3, endln:8:6, parent:work@dut
     |vpiName:ABC
     |vpiFullName:work@dut.ABC
     |vpiAutomatic:1
     |vpiVisibility:1
     |vpiExpr:
     \_operation: , line:8:9, endln:8:55
       |vpiOpType:75
       |vpiOperand:
       \_tagged_pattern:
         |vpiPattern:
         \_operation: , line:8:16, endln:8:26
           |vpiOpType:75
           |vpiOperand:
           \_constant: , line:8:18, endln:8:22
             |vpiConstType:3
             |vpiDecompile:1'b1
             |vpiSize:1
             |BIN:1
           |vpiOperand:
           \_constant: , line:8:24, endln:8:25
             |vpiConstType:9
             |vpiDecompile:1
             |vpiSize:64
             |UINT:1
         |vpiTypespec:
         \_string_typespec: (BC1), line:8:11, endln:8:14
           |vpiName:BC1
       |vpiOperand:
       \_tagged_pattern:
         |vpiPattern:
         \_constant: , line:8:33, endln:8:34
           |vpiConstType:9
           |vpiDecompile:0
           |vpiSize:64
           |UINT:0
         |vpiTypespec:
         \_int_typespec: , line:8:28, endln:8:31
       |vpiOperand:
       \_tagged_pattern:
         |vpiPattern:
         \_operation: , line:8:41, endln:8:54
           |vpiOpType:75
           |vpiOperand:
           \_tagged_pattern:
             |vpiPattern:
             \_constant: , line:8:52, endln:8:53
               |vpiConstType:9
               |vpiDecompile:0
               |vpiSize:64
               |UINT:0
             |vpiTypespec:
             \_string_typespec: (default), line:8:43, endln:8:50
               |vpiName:default
         |vpiTypespec:
         \_string_typespec: (BC2), line:8:36, endln:8:39
           |vpiName:BC2
     |vpiTypespec:
     \_struct_typespec: , line:2:1, endln:2:7
       |vpiTypespecMember:
       \_typespec_member: (A), line:3:7, endln:3:8
         |vpiName:A
         |vpiTypespec:
         \_int_typespec: , line:3:3, endln:3:6
       |vpiTypespecMember:
       \_typespec_member: (BC1), line:7:5, endln:7:8
         |vpiName:BC1
         |vpiTypespec:
         \_struct_typespec: , line:4:3, endln:4:9
           |vpiTypespecMember:
           \_typespec_member: (B), line:5:11, endln:5:12
             |vpiName:B
             |vpiTypespec:
             \_logic_typespec: , line:5:5, endln:5:10
           |vpiTypespecMember:
           \_typespec_member: (C), line:6:9, endln:6:10
             |vpiName:C
             |vpiTypespec:
             \_int_typespec: , line:6:5, endln:6:8
       |vpiTypespecMember:
       \_typespec_member: (BC2), line:7:10, endln:7:13
         |vpiName:BC2
         |vpiTypespec:
         \_struct_typespec: , line:4:3, endln:4:9
           |vpiTypespecMember:
           \_typespec_member: (B), line:5:11, endln:5:12
             |vpiName:B
             |vpiTypespec:
             \_logic_typespec: , line:5:5, endln:5:10
           |vpiTypespecMember:
           \_typespec_member: (C), line:6:9, endln:6:10
             |vpiName:C
             |vpiTypespec:
             \_int_typespec: , line:6:5, endln:6:8

Also according to 37.70 Case, pattern there are 3 types of patterns:

any pattern
tagged pattern
struct pattern
In above example we are assigning to the struct, so I think Surelog should return vpiStructPattern instead of vpiTaggedPattern

Which testcase is blocked by this?

Real testcase:
package aes_pkg;
typedef enum logic {
  AES_ENC = 1'b0,
  AES_DEC = 1'b1
} aes_op_e;

typedef enum logic [3:0] {
  AES_ECB  = 4'b0001,
  AES_CBC  = 4'b0010,
  AES_CTR  = 4'b0100,
  AES_NONE = 4'b1000
} aes_mode_e;

typedef enum logic [2:0] {
  AES_128 = 3'b001,
  AES_192 = 3'b010,
  AES_256 = 3'b100
} key_len_e;

typedef struct packed {
  aes_op_e   operation;
  aes_mode_e mode;
  key_len_e  key_len;
  logic      manual_operation;
} ctrl_reg_t;

parameter ctrl_reg_t CTRL_RESET = '{
  operation:        AES_ENC,
  mode:             AES_NONE,
  key_len:          AES_128,
  manual_operation: '0
};
endpackage

module test #(
parameter int DW = 32,
parameter logic [DW-1:0] TEST = '0
) ();

endmodule

module not_top ();

import aes_pkg::*;

test #(
  .DW($bits(ctrl_reg_t)),
  .TEST(CTRL_RESET)
) t ();

endmodule

module dut();

not_top m();

endmodule

UHDM:
...
|vpiParamAssign:
\_param_assign: , line:37:26, endln:37:35, parent:work@dut.m.t
  |vpiRhs:
  \_operation: , line:48:9, endln:48:19
    |vpiOpType:75
    |vpiOperand:
    \_tagged_pattern:
      |vpiPattern:
      \_constant: , line:28:21, endln:28:28
        |vpiConstType:17
        |vpiDecompile:0
        |vpiSize:1
        |SCAL:0
      |vpiTypespec:
      \_string_typespec: (operation), line:28:3, endln:28:12
        |vpiName:operation
    |vpiOperand:
    \_tagged_pattern:
      |vpiPattern:
      \_constant: , line:29:21, endln:29:29
        |vpiConstType:9
        |vpiDecompile:8
        |vpiSize:4
        |UINT:8
      |vpiTypespec:
      \_string_typespec: (mode), line:29:3, endln:29:7
        |vpiName:mode
    |vpiOperand:
    \_tagged_pattern:
      |vpiPattern:
      \_constant: , line:30:21, endln:30:28
        |vpiConstType:9
        |vpiDecompile:1
        |vpiSize:3
        |UINT:1
      |vpiTypespec:
      \_string_typespec: (key_len), line:30:3, endln:30:10
        |vpiName:key_len
    |vpiOperand:
    \_tagged_pattern:
      |vpiPattern:
      \_constant: , line:31:21, endln:31:23
        |vpiConstType:3
        |vpiDecompile:'0
        |vpiSize:-1
        |BIN:0
      |vpiTypespec:
      \_string_typespec: (manual_operation), line:31:3, endln:31:19
        |vpiName:manual_operation
    |vpiTypespec:
    \_struct_typespec: (aes_pkg::ctrl_reg_t), line:20:9, endln:20:15
      |vpiPacked:1
      |vpiName:aes_pkg::ctrl_reg_t
      |vpiTypespecMember:
      \_typespec_member: (operation), line:21:14, endln:21:23, parent:aes_pkg::ctrl_reg_t
        |vpiName:operation
        |vpiTypespec:
        \_enum_typespec: (aes_pkg::aes_op_e), line:5:3, endln:5:11, parent:operation
          |vpiName:aes_pkg::aes_op_e
          |vpiBaseTypespec:
          \_logic_typespec: , line:2:14, endln:2:19, parent:aes_pkg::aes_op_e
            |vpiInstance:
            \_package: aes_pkg (aes_pkg::) dut.sv:1:1: , endln:33:11, parent:work@dut
          |vpiEnumConst:
          \_enum_const: (AES_ENC), line:3:3, endln:3:10, parent:aes_pkg::aes_op_e
            |vpiName:AES_ENC
            |SCAL:0
            |vpiSize:1
          |vpiEnumConst:
          \_enum_const: (AES_DEC), line:4:3, endln:4:10, parent:aes_pkg::aes_op_e
            |vpiName:AES_DEC
            |SCAL:1
            |vpiSize:1
          |vpiInstance:
          \_package: aes_pkg (aes_pkg::) dut.sv:1:1: , endln:33:11, parent:work@dut
      |vpiTypespecMember:
      \_typespec_member: (mode), line:22:14, endln:22:18, parent:aes_pkg::ctrl_reg_t
        |vpiName:mode
        |vpiTypespec:
        \_enum_typespec: (aes_pkg::aes_mode_e), line:12:3, endln:12:13, parent:mode
          |vpiName:aes_pkg::aes_mode_e
          |vpiBaseTypespec:
          \_logic_typespec: , line:7:14, endln:7:19, parent:aes_pkg::aes_mode_e
            |vpiRange:
            \_range: , line:7:21, endln:7:24
              |vpiLeftRange:
              \_constant: , line:7:21, endln:7:22
                |vpiConstType:9
                |vpiDecompile:3
                |vpiSize:64
                |UINT:3
              |vpiRightRange:
              \_constant: , line:7:23, endln:7:24
                |vpiConstType:9
                |vpiDecompile:0
                |vpiSize:64
                |UINT:0
            |vpiInstance:
            \_package: aes_pkg (aes_pkg::) dut.sv:1:1: , endln:33:11, parent:work@dut
                      |vpiEnumConst:
          \_enum_const: (AES_ECB), line:8:3, endln:8:10, parent:aes_pkg::aes_mode_e
            |vpiName:AES_ECB
            |vpiDecompile:4'b0001
            |UINT:1
            |vpiSize:4
          |vpiEnumConst:
          \_enum_const: (AES_CBC), line:9:3, endln:9:10, parent:aes_pkg::aes_mode_e
            |vpiName:AES_CBC
            |vpiDecompile:4'b0010
            |UINT:2
            |vpiSize:4
          |vpiEnumConst:
          \_enum_const: (AES_CTR), line:10:3, endln:10:10, parent:aes_pkg::aes_mode_e
            |vpiName:AES_CTR
            |vpiDecompile:4'b0100
            |UINT:4
            |vpiSize:4
          |vpiEnumConst:
          \_enum_const: (AES_NONE), line:11:3, endln:11:11, parent:aes_pkg::aes_mode_e
            |vpiName:AES_NONE
            |vpiDecompile:4'b1000
            |UINT:8
            |vpiSize:4
          |vpiInstance:
          \_package: aes_pkg (aes_pkg::) dut.sv:1:1: , endln:33:11, parent:work@dut
      |vpiTypespecMember:
      \_typespec_member: (key_len), line:23:14, endln:23:21, parent:aes_pkg::ctrl_reg_t
        |vpiName:key_len
        |vpiTypespec:
        \_enum_typespec: (aes_pkg::key_len_e), line:18:3, endln:18:12, parent:key_len
          |vpiName:aes_pkg::key_len_e
          |vpiBaseTypespec:
          \_logic_typespec: , line:14:14, endln:14:19, parent:aes_pkg::key_len_e
            |vpiRange:
            \_range: , line:14:21, endln:14:24
              |vpiLeftRange:
              \_constant: , line:14:21, endln:14:22
                |vpiConstType:9
                |vpiDecompile:2
                |vpiSize:64
                |UINT:2
              |vpiRightRange:
              \_constant: , line:14:23, endln:14:24
                |vpiConstType:9
                |vpiDecompile:0
                |vpiSize:64
                |UINT:0
            |vpiInstance:
            \_package: aes_pkg (aes_pkg::) dut.sv:1:1: , endln:33:11, parent:work@dut
          |vpiEnumConst:
          \_enum_const: (AES_128), line:15:3, endln:15:10, parent:aes_pkg::key_len_e
            |vpiName:AES_128
            |vpiDecompile:3'b001
            |UINT:1
            |vpiSize:3
          |vpiEnumConst:
          \_enum_const: (AES_192), line:16:3, endln:16:10, parent:aes_pkg::key_len_e
            |vpiName:AES_192
            |vpiDecompile:3'b010
            |UINT:2
            |vpiSize:3
          |vpiEnumConst:
          \_enum_const: (AES_256), line:17:3, endln:17:10, parent:aes_pkg::key_len_e
            |vpiName:AES_256
            |vpiDecompile:3'b100
            |UINT:4
            |vpiSize:3
          |vpiInstance:
          \_package: aes_pkg (aes_pkg::) dut.sv:1:1: , endln:33:11, parent:work@dut
      |vpiTypespecMember:
      \_typespec_member: (manual_operation), line:24:14, endln:24:30, parent:aes_pkg::ctrl_reg_t
        |vpiName:manual_operation
        |vpiTypespec:
        \_logic_typespec: , line:24:3, endln:24:8, parent:manual_operation
          |vpiInstance:
          \_package: aes_pkg (aes_pkg::) dut.sv:1:1: , endln:33:11, parent:work@dut
      |vpiInstance:
      \_package: aes_pkg (aes_pkg::) dut.sv:1:1: , endln:33:11, parent:work@dut
  |vpiLhs:
  \_parameter: (work@dut.m.t.TEST), line:37:26, endln:37:35, parent:work@dut.m.t
  ...

We are getting assignment pattern on Rhs with Lhs that is just array.

We consider it a blocker because it is a case found in OpenTitan.
Verilator is able to handle this using the typespec provided with the assignment pattern, but Yosys has no concept of assignment patterns.
Thus we'd have to implement in Yosys pretty much the same thing you're working on here. As this is needed anyway to support the standard, it would be smarter to do it once in Surelog and avoid duplicate work.

OK, I keep working on it.
On Tue, Sep 21, 2021 at 10:01 AM Krzysztof Bieganski <
@.***> wrote:

We consider it a blocker because it is a case found in OpenTitan.
Verilator is able to handle this using the typespec provided with the
assignment pattern, but Yosys has no concept of assignment patterns.
Thus we'd have to implement in Yosys pretty much the same thing you're
working on here. As this is needed anyway to support the standard, it would
be smarter to do it once in Surelog and avoid duplicate work.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/chipsalliance/Surelog/issues/1865#issuecomment-924178922,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APFYJ5AFM63JAUHOORL2ZJLUDC265ANCNFSM5EB2CTHQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Fixed by #2229

Thank you for working this.
Example from the standard is now working as expected, but when we instead of assigning struct when it is created, we create typedef and then assign to variable of this typedef, it is still returning vpiTaggedPattern without positional notation.
Example:
module dut();
typedef struct {
  int A;
  struct {
    logic B;
    int C;
  } BC1, BC2;
} ABC;

ABC test;

assign test = '{BC1: '{1'b1, 1}, int: 0, BC2: '{default: 0}};
endmodule

UHDM:
|vpiContAssign:
   \_cont_assign: , line:12:8, endln:12:61, parent:work@dut
     |vpiRhs:
     \_operation: , line:12:15, endln:12:61
       |vpiOpType:75
       |vpiOperand:
       \_tagged_pattern:
         |vpiPattern:
         \_operation: , line:12:22, endln:12:32
           |vpiOpType:75
           |vpiOperand:
           \_constant: , line:12:24, endln:12:28
             |vpiConstType:3
             |vpiDecompile:1'b1
             |vpiSize:1
             |BIN:1
           |vpiOperand:
           \_constant: , line:12:30, endln:12:31
             |vpiConstType:9
             |vpiDecompile:1
             |vpiSize:64
             |UINT:1
         |vpiTypespec:
         \_string_typespec: (BC1), line:12:17, endln:12:20
           |vpiName:BC1
       |vpiOperand:
       \_tagged_pattern:
         |vpiPattern:
         \_constant: , line:12:39, endln:12:40
           |vpiConstType:9
           |vpiDecompile:0
           |vpiSize:64
           |UINT:0
         |vpiTypespec:
         \_int_typespec: , line:12:34, endln:12:37
       |vpiOperand:
       \_tagged_pattern:
         |vpiPattern:
         \_operation: , line:12:47, endln:12:60
           |vpiOpType:75
           |vpiOperand:
           \_tagged_pattern:
             |vpiPattern:
             \_constant: , line:12:58, endln:12:59
               |vpiConstType:9
               |vpiDecompile:0
               |vpiSize:64
               |UINT:0
             |vpiTypespec:
             \_string_typespec: (default), line:12:49, endln:12:56
               |vpiName:default
         |vpiTypespec:
         \_string_typespec: (BC2), line:12:42, endln:12:45
           |vpiName:BC2
     |vpiLhs:
     \_ref_obj: (work@dut.test), line:12:8, endln:12:12
       |vpiName:test
       |vpiFullName:work@dut.test

Open a different issue, code change will be different, test case is different. Do not reopen issues please

authors: alaindargelas kamilrakoczy kbieganski

repo: chipsalliance/Surelog


text:
In sign up page :- Contact validation of 10 digit

In sign up form there should be  validation of 10 digit number . I want to work on this issue as a participate of gssoc21 .

Issue assigned.

@amanjha8100 Can I work on this issue and solve it

If shalini is not able to solve the isuue @435akashjha . I will assign to it you.

Sir I am working on it , the thing is I am busy in clg
I will send you by today

Sorry @435akashjha but I am working on it

@amanjha8100 i have send PR please check it

repo: chiraag-kakar/sharenlearn


text:
Week abbreviation "Wk" not localizable

Hi,
when week numbers are displayed in a calendar, the abbreviation "Wk" is shown to the left of the weekday names. This is a hardcoded string and i didn't find an easy way to localize it without changing the .js source.
Would it be possible to add this to the list of localizable strings, so that we could e.g. just do the following?
flatpickr.init.prototype.l10n.weekAbbrev = "KW";

Fixed by https://github.com/chmln/flatpickr/commit/27106f32a1e770114ca4a3c1be70beffae0b79dc

Perfect. Thanks.

authors: chmln seiz

repo: chmln/flatpickr


text:
smartftp: no more bugtracker

There is no longer a public bug tracker for SmartFTP

Description

Motivation and Context

How Has this Been Tested?

Screenshot (if appropriate, usually isn't needed):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Migrated package (a package has been migrated from another repository)

Checklist:

[ ] My code follows the code style of this repository.
[ ] My change requires a change to documentation (this usually means the notes in the description of a package).
[ ] I have updated the documentation accordingly (this usually means the notes in the description of a package).
[ ] All files are up to date with the latest Contributing Guidelines
[ ] The added/modified package passed install/uninstall in the chocolatey test environment.
[ ] The changes only affect a single package (not including meta package).

Original Location

Original Repository
Open Issues Add the different issues underneath, and tick those that are fixed in this PR

[ ] Issue 1 link
[ ] Issue 2 Link

[ ] Include the link to the opened PR that removes the package from the original location
[ ] The migration guidelines have been followed

Duplicate of #1407?

Yes. Thanks.

authors: matbech mkevenaar


text:
RFM - mediathekview

Current Maintainer

[x] I am the maintainer of the package and wish to pass it to someone else;

Checklist

[x] Issue title starts with 'RFM - '

Existing Package Details

Package URL: https://community.chocolatey.org/packages/mediathekview
Package source URL: https://github.com/AdmiringWorm/chocolatey-packages/tree/ac03f7e22630221b951374e1f5a3d089ac74841d/automatic/mediathekview

Hello @AdmiringWorm , i'll take it, it's ready on my repo.
Can you add me as maintainer ? (tunisiano)
Thank you.

@tunisiano187 I have added you as a maintainer (that you need to accept), thanks for taking over the package.
Do note that the trusted status has temporarily been removed, but if approved by a moderator for the first package version you submit we can re-instate that again.


text:
[Enhancement] Make the main helpers work with files not coming over HTTP.

Refer to this chocolatey group discussion: How do I use Chocolatey with a private corporate network share based source?

This command
Install-ChocolateyPackage 'mypackage' 'EXE' '/S' '\\mylocalnas\gallery\myproduct.exe'

produces this error
Write-Error : acrview did not finish successfully. Boo to the chocolatey gods!
-----------------------
[ERROR] Property 'CookieContainer' cannot be found on this object; make sure it exists and is settable.
-----------------------
At D:\packages\chocolateyInstall\helpers\chocolateyInstaller.psm1:373 char:13
+     Write-Error <<<<  $errorMessage
	+ CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
	+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Write-Error

Property 'CookieContainer' cannot be found on this object; make sure it exists and is settable.
At D:\packages\chocolateyInstall\helpers\chocolateyInstaller.psm1:510 char:8
+   $req. <<<< CookieContainer = New-Object System.Net.CookieContainer
	+ CategoryInfo          : InvalidOperation: (:) [], ParentContainsErrorRecordException
	+ FullyQualifiedErrorId : PropertyAssignmentException

This command does work and might be a work-around.
Install-ChocolateyInstallPackage 'mypackage' 'EXE' '/S' ' file:///mylocalnetwork/gallery/myproduct.exe '

Relevant comment from @ferventcoder on the discussion:

We could probably put some code in to make it work with files not coming over HTTP. In the meantime, Install-ChocolateyInstallPackage will work for things as long as the installer doesn't require being installed from a local drive. In those cases you could copy the installer to a temp directory and then call Install-ChocolateyInstallPackage. Would this work for you for now?

This shouldn't be too hard,  I just did something similar for the cinst all command

Fixed in 59e71754bb726bddec5ee6dd601ac414c5ff2471

authors: AnthonyMastrean ferventcoder

repo: chocolatey/chocolatey


text:
Enable configuration JSON to specify api_url

Currently, we use the default api_url, which corresponds to a non-existent server.
We should instead support specifying this from the local analysis configuration JSON.

We can at least change this to mskcc1.foldingathome.org for now.

repo: choderalab/fah-xchem


text:
Getting wrong annotation count on click of cluster in swift 3

When I click on a particular cluster then not getting a exact annotation count that I showed over label In swift 3.I am showing this label over image in swift 3.
Can anybody help me

Hey! It's hard to tell exactly what you're seeing based on this brief bug report, but: I was seeing a similar issue for a bit in my code, and found a fix for my issue. I needed to implement mapClusterController(_:willReuse:) — and in my implementation, I need to re-set the counter label I had on my little badge view.
Hope that helps!
    public func mapClusterController(_ mapClusterController: CCHMapClusterController!, willReuse mapClusterAnnotation: CCHMapClusterAnnotation!) {
        let annotationView = mapView.view(for: mapClusterAnnotation) as! PhotoClusterAnnotationView
        self.update(annotationView: annotationView, withAnnotation: mapClusterAnnotation)
        annotationView.prepareForReuse()
    }

authors: bryanjclark wamobileapps

repo: choefele/CCHMapClusterController


text:
Style and transitions + state management

Styling is basically done, with some of gentle transitions.
I've hit on an interesting way to store theme and language during navigation, by dynamically adding url parameters to the nav links. It's a progressive enhancement, so without JS pages just default to dark HTML. I also like the idea that the theme and language become part of the shareable URL.
I slightly messed up my git history, so it's probably best to squash during merge.

Heyyyyy this looks AWESOME

authors: chriscoyier landjonathan

repo: chriscoyier/coding-fonts


text:
How do you use Calligraphy on DatePicker?

I want to change the fonts on a DatePickerView

If it's created from inside your Activity and that Dialog inflates views, then it should work otherwise you'd have to do it by hand regarless of using this or AndroidX solution.

repo: chrisjenx/Calligraphy


text:
Warpgate requirement?

Why does it list Warpgate as requirement? The Module is dead. Or is there something else?

Warpgate is only a requirement for V11 CPR which warpgate still functions in.

@InconspicuousBear did you get a resolution? If not I recommend joining the discord for better support.

All is good, I am glad I have to use one module less!

authors: InconspicuousBear Sayshal


text:
frontend and backend Dockerfile for production not working

frontend build success but not working, the logs:
/usr/local/bin/docker-entrypoint.sh: line 4: nginx: not found

backend build error:
Service 'backend' failed to build : The command '/bin/sh -c npm install' returned a non-zero code: 228

@forecho the issue has been resolved
https://github.com/chrisleekr/yii2-angular-boilerplate/pull/48

authors: chrisleekr forecho


text:
Adding PostgreSQL Filer Support

Hello - I've been working on a PostgreSQL filer store. It is based on the existing mysql implementation.
To use it, you use the same filer.confFile configuration file, and add a "postgres" section instead of a "mysql" section.
My golang experience is still weak, but it seems to be working fine.

Thanks!

authors: chrislusf mtolman

repo: chrislusf/seaweedfs


text:
Calliope parse error does not show file name

Showing file name on parse error would be very helpful. I'm raising this issue here since the file name is not passed to Calliope.
I propose we catch the exception here, pretend the file name and reraise.
I can submit a pull request.

Thanks for merging the pull request Chris.


text:
Controller not detected

After flash arkos firmware final on my RG351p, it won't pass hit A button. Then I tried to force reset, pop up shown said gamepad not detected. Im using sandisk A1 microsd as per suggestion.

Yep, typical issue for this device.  All you can do is reboot and try again to see if the controller comes back.  Otherwise, the usb controller chip needs to be replaced.  It's the main reason why I decided to no longer to continue support for this device.  Good luck.

repo: christianhaitian/arkos


text:
Android high battery consumption

Hi,
I have implemented the plugin in an app running on both iOS and Android. While iOS performs very well, on Android I always see very high battery usage when the location tracking is enabled. It is mostly noticeable inside a building (no GPS), as it tries to get GPS coordinates for about 60 seconds each time. BTW, no reporting is performed inside a building (event not coarse).
I would suggest adding options for less accurate location tracking, using low power and low accuracy. Also, location detection timeout can be decreased and add getting coarse location if GPS not found within X seconds.
Thanks and great job!

Android refactored in Premium Version.  Battery performance has been vastly improved.
http://christocracy.github.io/cordova-background-geolocation/

authors: christocracy ochakov


text:
Add relevance/importance measurements of predictors

(see p. 12, equations 28 and 29 of the paper (PDF))

Also add option in get_rules() method to sort by importance

repo: christophM/rulefit


text:
Image icon over date?

In case of a special event, i want to show an image icon over a date. How can i go about this?

Currently we don't support this functionality, we will be grateful if you would like to give it a try.

authors: hejiaji irfanayazfm

repo: christopherdro/react-native-calendar


text:
Building and installation of CADMesh in macOS sierra

Greetings.
I am trying to install CADMesh on a mac with OS Sierra, but when doing the building process the following error messages appear:
-- The C compiler identification is AppleClang 9.0.0.9000039
-- The CXX compiler identification is AppleClang 9.0.0.9000039
-- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc
-- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++
-- Check for working CXX compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found PkgConfig: /opt/local/bin/pkg-config (found version "0.29.2")
CMake Warning at examples/template/CMakeLists.txt:10 (find_package):
  By not providing "Findcadmesh.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "cadmesh", but
  CMake did not find one.

  Could not find a package configuration file provided by "cadmesh" with any
  of the following names:

    cadmeshConfig.cmake
    cadmesh-config.cmake

  Add the installation prefix of "cadmesh" to CMAKE_PREFIX_PATH or set
  "cadmesh_DIR" to a directory containing one of the above files.  If
  "cadmesh" provides a separate development package or SDK, be sure it has
  been installed.

-- Configuring done
CMake Warning (dev):
  Policy CMP0042 is not set: MACOSX_RPATH is enabled by default.  Run "cmake
  --help-policy CMP0042" for policy details.  Use the cmake_policy command to
  set the policy and suppress this warning.

  MACOSX_RPATH is not specified for the following targets:

   cadmesh

This warning is for project developers.  Use -Wno-dev to suppress it.

-- Generating done
-- Build files have been written to: /Users/gustavoalcala/CADMesh/build

And even though it tells me the configuration was set and the installation can be done, when doing the installation (executing make command) problems start to arise and the installing process cancels itself.
This may be caused because during the building I am obtaing these problems:
First, it tells me there are problems in the file examples/template/CMakeLists.txt, and the line with the issue reads "find_package(cadmesh)". Here I do not know if I have to add something when doing the build instead of just doing it with "cmake .." command inside the build directory.
Them it tells me the is a problem with the CMake's Policy CMP004. And regarding this, I have added such policy to the CMakeList but that does not seem to solve my problem.
Thank you very much.

Please try the latest version of CADMesh. Version 2.

authors: christopherpoole gustavoaae

repo: christopherpoole/CADMesh


text:
fix(sticky): handle the null locals when exiting inactiveState

Fixes #258
Under some weird circumstances on the application the locals of a state are null triggering an exception inside ui-router-extras.
A workaround was to wrap some call to $state.go in a $timeout but this is not very elegant.
I have added a test that demonstrates that even with a null locals the code is smooth.

+1 This solves the problem for me. @christopherthielen worth a look. Thanks!

I understand that this stops the error from appearing in the console.  However, this PR only masks a problem.  An onEnter/Exit/etc hook that requires resolve data will still be broken.  That is why I haven't merged this PR.  Also, the release files should not be included in the PR.

Should be fixed in e401776b480f8fd29fca049aa9f42df0732f6443
Please try 0.1.1 version

repo: christopherthielen/ui-router-extras


text:
[CLN] Make log use enum not dyn

Description of changes
Summarize the changes made by this PR.

Improvements & Bug fixes

Same reasoning as #2350

New functionality

None

Test plan
How are these changes tested?
existing

[x] Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Documentation Changes
None

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#2351  👈
#2350
main

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

Join @HammadB and the rest of your teammates on  Graphite

repo: chroma-core/chroma


text:
🛑 91家纺 is down

In 164a2ac, 91家纺 (https://www.91jf.com/) was down:

HTTP code: 403
Response time: 1308 ms

Resolved: 找家纺网 is back up in fd6eb81 after .

repo: chwang-team/status-hao


text:
🛑 17货源 is down

In d2946f4, 17货源 (https://www.17zwd.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 衣联 is back up in d917edd after .


text:
Login failure : HTTP 401 Unauthorized

I/System.out(12879): [ZendeskMessaging] - Login failure : HTTP 401 Unauthorized
I/System.out(12879): retrofit2.HttpException: HTTP 401 Unauthorized

Hi @Paulika855
Please provide more informations. Give us your code.
How do you try to use authentication ? You need to setup a server endpoint (http) and generate a custom JWT token for use authentication. Please follow the Zendesk Documentation for this : https://developer.zendesk.com/documentation/zendesk-web-widget-sdks/sdks/web/enabling_auth_visitors/

HI @tspoke ,
Thank you for your response.
For JWT token I just generate from  https://jwt.io/  with bellow Info:


text:
Focus event ordering is incorrect.

Demo: https://output.jsbin.com/vilumo
    let element = document.createElement('input');

    ['mousedown', 'mouseup', 'click', 'focus', 'focusin'].forEach(type => {
      element.addEventListener(type, () => {
        console.log('event:', type);
      });
    });

    document.body.appendChild(element);

Tested on FireFox, Chrome, and Safari the output is:
event: mousedown
event: focus
event: focusin
event: mouseup
event: click

However, our utility function fires them as mousedown, focusin, focus, mouseup, click.  I noticed this while migrating the implementation to @ember/test-helpers and writing unit tests for the behavior of click.

TBH, I believe this discrepancy has always existed. I only created an issue because I'd like for this library to match the behavior as much as possible with @ember/test-helpers.

repo: cibernox/ember-native-dom-helpers


text:
:package: :heavy_plus_sign: Dockerfile: Install asciidoctor package

This commit adds the asciidoctor package from the official Ubuntu
20.04 repositories. Hugo supports rendering AsciiDoc content, but
requires the asciidoctor binary to be in the $PATH in order to fully
render AsciiDoc to HTML.
By including asciidoctor upstream in the base image, it makes it
easier for downstream implementations to have AsciiDoc support enabled
in Hugo by default.

Looks good. Thank you.

authors: felicianotech jwflory

repo: cibuilds/hugo


text:
CFP:  Forward to endpoints ICMP Errors for service NodePort

Certain issues regarding how packets can be handled may happen when dealing with networks, In the case of fragmentation, a networking equipment in the path may accept a smaller packet size than the interface from where the packet is coming from.
Usually that networking equipment will reply using ICMP Error message to inform the sender (in the case of fragmentation) what maximum MTU can be accepted since fragmentation is denied by the DF bit on the ethernet frame.
ICMP Error type 3 is specified by the RFC 792 as follow:
Destination Unreachable Message

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Type      |     Code      |          Checksum             |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                             unused                            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      Internet Header + 64 bits of Original Data Datagram      |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Given an endpoint running an http server exposed to the world using a service type NodePort. A client from the world trying to connect to download content from it.
Assuming that, After the TCP connection gets initiated, data gets transferred from the endpoint to the client. Endpoint is sending  packets with maximum size configured by its device. In the path a networking equipment is configured to use a smaller MTU. That networking equipment will reply with an ICMP error type 3 code 4 (fragmentation needed and DF set).
The purpose of this RFE is to implement the support which will make the packet to get forwarded to the endpoint.
The implementation consists of extending extract_l4_port to support ICMP Error type 3. Extracting the key of the service will be achieved by reading the source port of the UDP or TCP packet embedded in the payload of the ICMP message.
A prototype of the implementation can be seen:

https://github.com/cilium/cilium/commit/1c6ae94375c3fe768ac067f73d9d7763fabd9191

It looks like forwarding the ICMP Error packet to the endpoint is not an option as Cilium’s eBPF NodePort implementation operates in SNAT mode.
Two cases are supportable:

Using DSR mode, adding the support of forwarding the ICMP Error packet when Cilium is configured to use loadbalancer.mode=dsr. As in this DSR mode the backend replies directly to the external client.
The TCP SYN will be joining the endpoint on the remote backend from the node-external using SNAT, then next packets will be using direct access from backend to the external client. It is expected that the packet which exceeds the MTU will happen during payload transfert.
Having node-external handling ICMP Error. Using the node-external where the traffic arrives could handle the ICMP Error. For the case of a need to fragment, the route table of the node may be updated and fragment the packet to the external client.

It seems that both of the cases are valuables but I would appreciate any advice as there may exist blockers, work in-progress or better solutions.

It looks like forwarding the ICMP Error packet to the endpoint is not an option as Cilium’s eBPF NodePort implementation operates in SNAT mode.

Could you explain a bit why SNATing is an issue here?

The TCP SYN will be joining the endpoint on the remote backend from the node-external using SNAT, then next packets will be using direct access from backend to the external client.

Is that part of your first proposed approach? So in DSR mode we would still SNAT some packets? I don't think that's an acceptable solution for users given SNAT mode is often used to preserve the source IP.

It looks like forwarding the ICMP Error packet to the endpoint is not an option as Cilium’s eBPF NodePort implementation operates in SNAT mode.

Could you explain a bit why SNATing is an issue here?

For a given packet initiated by a external client arriving to a service nodeport, it will be SNATed to the remote backend that handles the targeted endpoint.
The source addr of the packet arriving to endpoint will be the addr of the node. If we let endpoint handling the ICMP Error it will consider it for the path node -> endpoint in opposite to client -> endpoint.
If we consider a need to fragment error reported, the MTU will be reduced for all the traffic that is passing through this path.
  client:         10.1.0.100
  router:         192.168.63.1
  nodeport:       192.168.63.100
  node:           10.0.128.10
  remote backend: 10.0.128.20
  endpoint:       10.0.90.12

  The client (10.1.0.100) is initiating a 3-way handshake going
  through service NodePort (192.168.63.100), then data are sent from
  endpoint to client but a networking equipement (192.168.63.1) in the
  networking path is repporting an ICMP Error need to frag.

  The networking equipment (192.168.63.1) is responding with an ICMP
  Error need to frag for a packet trying to join client at
  (10.1.0.100)

  192.168.63.1 -> 192.168.63.100        a)
       10.0.128.10 -> 10.0.128.20       b)
            10.0.128.10 -> 10.0.90.12   c)

 a) Networking equipement (192.168.63.1) reply an ICMP Error to 192.168.63.100
 b) Node (10.0.128.10) SNAT and DNAT the packet to join remote backend (10.0.128.20)
 c) Remote backend (10.0.128.20) route the packet to endpoint (10.0.90.12)

The ICMP Error received for a reply to client 10.1.0.100 by endpoint will be for 10.0.128.10 in opposite to 192.168.63.1.

The aim would be for SNAT mode to remove the (b) step by having the node handling the ICMP Error by itself. For DSR mode, adding support of xlateing the ICMP Error to endpoint.

in DSR mode we only SNAT the SYN packet from node to remote backend

In DSR mode, we don't SNAT anything AFAIK. The SYN packet can be a bit different because it carries the service IP & port in the IP options but it is not SNATed.

Right my mistake, not sure why I had stick this in my head. The point is to have the remote backend replying and the ICMP error directed to it when generated from the networking equipment.

Thinking out loud, for the native SNAT mode (opposite to any DSR mode), we could certainly just skip SNATing the ICMP Error packet arriving as no reply is expected, that would certainly be better than the original proposal to make the node itself handling it.

authors: pchaigno sahid

repo: cilium/cilium


text:
datapath/loader: always set all args to bpf/init.sh

Passing empty strings to bpf/init.sh will lead to arguments being
misinterpreted as their index is no longer correct. This can e.g. lead
to the MTU not being set in vxlan mode as seen in #10228. Thus, always
set all 17 (current value initArgMax) arguments top non-empty values.
Use <nil> as a default empty value if the arg is not used by
bpf/init.sh.
Fixes #10228
Signed-off-by: Tobias Klauser tklauser@distanz.ch

This change is

test-me-please

test-me-please

Coverage increased (+0.01%) to 44.483% when pulling e8a475f9cbc37417413fc4750feb98504fe79829 on pr/tklauser/fix-bpf-init.sh-args into b6f2e75d5b98bc200817da41f96c6522866cdd4a on master.

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

authors: aanm coveralls tklauser


text:
k8s: Consider session affinity parameters when comparing Services

Previously, if the sessionAffinity or sessionAffinityTimeoutSec of a Service changed, cilium would ignore the change. This meant that even though cilium correctly handles sessionAffinity, changing the sessionAffinity of a service without any other changes did not cause cilium to change its handling.
Add sessionAffinity and sessionAffinityTimeoutSec handling to the comparator for services, so that cilium will notice affinity changes.
Fixes: #12489
Fix handling of changes to session affinity configuration for Kubernetes services.

test-net-next

retest-net-next

retest-4.19

retest-4.9

retest-runtime

retest-gke

authors: adamwg borkmann nathanjsweet tklauser


text:
v1.9 backports 2021-04-16

#15748 -- test: ensure kubectl version is available for test run (@nebril)

Once this PR is merged, you can update the PR labels via:
$ for pr in 15748; do contrib/backporting/set-labels.py $pr done 1.9; done

test-backport-1.9

test-gke

authors: aanm joestringer


text:
endpoint, proxy: Fix deadlock with ipcache and K8s watcher

endpoint, proxy: Fix deadlock with ipcache and K8s watcher
proxy: Refactor dnsRedirect to prevent regressions
proxy: Remove unused dnsConfiguration type

Fixes: https://github.com/cilium/cilium/issues/20915
Fix deadlock when EKS kube-apiservers scale down causing network connectivity outages

/test

/test

Given the nature of the k8s-1.16-kernel-4.19 failures, we'll need to dig closely through to understand whether there could be a DNS availability impact with these new changes. At a glance I'm not really sure.

Looks like shifting the contested code block to a finalizer would be the right thing to do.

@christarazi Or is the issue that DefaultDNSProxy.GetRules() should not be called while the endpoint is locked?

Looks like shifting the contested code block to a finalizer would be the right thing to do.

@christarazi Or is the issue that DefaultDNSProxy.GetRules() should not be called while the endpoint is locked?

@jrajahalme Yes I believe the issue is calling DefaultDNSProxy.GetRules() while the endpoint is locked is the main issue, as that issues invokes an ipcache read operation. Given that the ipcache is already locked 1 while handling removeLabelsFromIPs, these are the 3 actors involved in the deadlock.

Given the nature of the k8s-1.16-kernel-4.19 failures, we'll need to dig closely through to understand whether there could be a DNS availability impact with these new changes. At a glance I'm not really sure.

I took a look at the failures and they seem to be unrelated as the DNS look (dig +short kubernetes.default.svc.cluster.local @10.96.0.10) was failed for some reason. I could not find any info on why it was failing; the CEP existed, ipcache entry plumbed, service backends plumbed into Cilium, etc. The root issue seems to boil down to this flake, but can't tell why it occurred.

/test-1.16-4.19

/test-1.16-4.19

Marking as ready for review, as this seems to have reached consensus (and tests are passing). Plus Chris is out.

GKE failed on deleting the cilium-test namespace, which shouldn't have been caused by this PR. The pods were successfully deleted; just the Namespace object itself was the issue.

I've reassessed the affected branches and traced the bug introduction to https://github.com/cilium/cilium/pull/18996 .

@squeed Can you link to the known flake?

Sure, done. (I've been on previous projects that preferred not to create the breadcrumbs b/c it "spams" the flake issue).

to summarize: test-1.16-4.19 flake is #23845. gke flake is #22368. Marking this as ready-to-merge.

authors: aanm christarazi joestringer jrajahalme squeed


text:
Test upgrade/downgrade to patch release for IPsec

WIP

/ci-ipsec-upgrade


text:
gha: test certificate generation methods in conformance clustermesh

Make sure to test all the three supported certificate generation methods (i.e., helm, cronJob and cert-manager) to prevent possible regressions affecting only one of them.

/ci-clustermesh

/ci-clustermesh

/ci-clustermesh

/test

@YutaroHayakawa Gentle ping :pray:


text:
Test: Cleanup CIDR test on AfterEach

At the moment the cleanup of the interfaces are made in a defer, and
AfterFailed can't retrieve all the info correctly.
With this change the cleanup will happens on the AfterEach function.
Signed-off-by: Eloy Coto eloy.coto@gmail.com

This change is

test-me-please


text:
bpf: daemon: Use bpftool for kernel parameter checks

bpftool and libbpf have feature checks, which have similar goals to BPF
feature checks in Cilium. This commits makes use of bpftool checks for
kernel parameters, but it also introduces the general use of bpftool
feature checks, so in future all of them can be used.
Ref: #7830
Signed-off-by: Michal Rostecki mrostecki@opensuse.org

This change is

test-me-please

Coverage decreased (-0.08%) to 41.406% when pulling 6f40070aae25ec856e3d5d8178e038ee810ab6f0 on mrostecki:bpftool-checks into dd7c78d67a0ea4dfcc018942814c668afea15b5d on cilium:master.

test-me-please

Is bpftool is readily available in all distos ? Quick search gives result only for fedora.

@nirmoy

Is bpftool readily available in all distos ? Quick search gives result only for fedora.

No, but I'm going to package it in openSUSE and include you in review, don't worry. ;) We need to add bpftool to the kernel package spec in https://github.com/openSUSE/kernel-source.
@joestringer

I think we should be able to get rid of probe_run_ll() as well?

Yes. And if there are some simple probe checks which are in Cilium, but not in bpftool, let's maybe send them as patches to bpftool? Porting all *.t files we have to libbpf probes should be quite easy.

@nirmoy I thought about your question once again and I realized that maybe building bpftool in the same spec as the kernel is not the best idea... We need to be able to ship bpftool for already existing versions of SLE and openSUSE Leap without depending on the newest kernel.
The good thing is that libbpf and bpftool don't really depend on the kernel itself, they are just developed together with the kernel. But running libbpf and bpftool from the newest tag (or even from net-next or bpf-next) should be possible on systems which have i.e. kernel 4.18.x.
There is already a standalone build for libbpf: https://github.com/libbpf/libbpf
Maybe it would be a good idea to have a similar repo, for example libbpf/bpftool? @borkmann, what do you think, can we do that?

test-me-please

Is bpftool readily available in all distos ? Quick search gives result only for fedora.

Perhaps not, but we already have a dependency on this and in most cases, Cilium is distributed/deployed as a container with bpftool already available. We should make sure this is documented.

@nirmoy I thought about your question once again and I realized that maybe building bpftool in the same spec as the kernel is not the best idea... We need to be able to ship bpftool for already existing versions of SLE and openSUSE Leap without depending on the newest kernel.
The good thing is that libbpf and bpftool don't really depend on the kernel itself, they are just developed together with the kernel. But running libbpf and bpftool from the newest tag (or even from net-next or bpf-next) should be possible on systems which have i.e. kernel 4.18.x.
There is already a standalone build for libbpf: https://github.com/libbpf/libbpf
Maybe it would be a good idea to have a similar repo, for example libbpf/bpftool? @borkmann, what do you think, can we do that?

I think best might be to have a package that builds bpftool from e.g. net or net-next kernel (which does not rebase its tree anyway). That way you always have the latest features available. We do that in our container image as well. I don't think extra libbpf/bpftool is needed here since all is self-contained in the kernel. We created the libbpf/libbpf for two reasons: 1) to have a pure BSD compatible libbpf lib available and 2) to not having to clone the whole tree if one only wants to build libbpf as a developer. For packaging bpftool these concerns shouldn't matter.

@borkmann Great, thanks for your advice! We will most probably build bpftool package from net-next then.

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

I realized that the way I used bpftool here is completely wrong. bpftool has a functionality of generating feature headers file which can be used directly in BPF programs.

authors: borkmann coveralls joestringer mrostecki nirmoy


text:
Add repo for Cilium Developer Summits

Repository Name
dev-summits
Type
New
Repository URL
No response
Proposed Scope
Ecosystem
Motivation for Request
We should have a public location for storing notes from Cilium Developer Summits. I think it makes sense to have a separate repo for this, with a folder for each summit (we have now held two, at Paris and SLC 2024).

README
https://hackmd.io/@e_RzxKt4QymdRWfhzrzFzQ/HJs3P53MJl

License
Apache 2.0
Code of Conduct

[x] I agree to follow Cilium's Code of Conduct

To be filled by a Cilium committer

[x] README describes the intent of the repository and has usage examples
[x] Adheres to one of the approved licenses
[x] Approved new repository is added into the appropriate list in REPOSITORIES.md

added to repositories.md with #175

authors: lizrice xmulligan

repo: cilium/community


text:
sensor pinning fixes (and misc updates)

This PR aims to sanitize pinning and meant as an intermediate step towards https://github.com/cilium/tetragon/issues/408. It also includes some simple (first 3) patches.
One of the immediate effects of this PR is that generic tracepoints have unique map names and collisions that may  cause problems are avoided.
See patches for more information.

LGTM!
nit: typo "hiearachy" -> "hierarchy" in the description of 68fae5b

Thanks! Pushed a new version with above fixed, as well as the rest of the comments.

repo: cilium/tetragon


text:
🛑 Cioos National CKAN Sitemap is down

In a90f73d, Cioos National CKAN Sitemap (https://catalogue.cioos.ca/sitemap/sitemap-1.xml) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Cioos National CKAN Sitemap is back up in 488a291 after 1 hour, 58 minutes.

repo: cioos-siooc/cwatch-upptime


text:
企业微信应用中，PickerService不能打开datePicker

项目中需要通过picker3修改每条记录的时间，是通过PickerService触发的，下面是我的代码

在pc端用chrome模拟器看的时候是正常的，但是在手机端测试的时候，进入了click的这个方法，但是通过pickerservice没有打开选择弹框。于是我写了picker1和picker2做测试，发现picker1可以弹出选择，但是超出屏幕宽度，picker2还是通过pickerService触发的，只传入了一个Type是date，手机端点击无反应。
下面是picker2的方法
 showDate() {     this.ps.showDateTime('date').subscribe((res: any) => {       alert('success');     });   }

麻烦提供一个可重现在线示例。

这个在pc看是正常的，在手机企业微信应用中看是不正常的，所以我也不太清楚这个我应该怎么提供给你呢？

我需要一个可重现在线示例，哪怕在PC上是正常的，但能确保企业微信下有问题的。否则我无法定位问题根源。

我可以提供外网地址，但是可能在调试器里无法查看资源，这样也可以吗？

建议在 Stackblitz 提供一个完整的示例。

建议从自身找问题：

感谢你的回复，我想问下你的测试机是iPhone还是安卓？并且还有点不一样是，我在click事件中调用了stopPropagation方法，其他我能想到的影响的地方，好像没有了， 我会再看看的

谢谢你的回复和帮助，已经找到原因。

authors: RookieLittleFatty cipchk

repo: cipchk/ngx-weui


text:
Update scalatest to 3.2.13

Updates org.scalatest:scalatest from 3.2.11 to 3.2.13.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Files still referring to the old version number
The following files still refer to the old version number (3.2.11).
You might want to review and update them manually.
build.sbt

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalatest", artifactId = "scalatest" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "org.scalatest", artifactId = "scalatest" }
}]

labels: test-library-update, early-semver-patch, semver-spec-patch, old-version-remains, commit-count:1

Codecov Report

Merging #333 (d958f1c) into master (9d4c9f3) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #333   +/-   ##
=======================================
  Coverage   95.31%   95.31%
=======================================
  Files           6        6
  Lines          64       64
=======================================
  Hits           61       61
  Misses          3        3

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9d4c9f3...d958f1c. Read the comment docs.

Superseded by #344.

authors: codecov-commenter scala-steward

repo: circe/circe-config


text:
Update scalafmt-core to 2.6.1

Updates org.scalameta:scalafmt-core from 2.6.0 to 2.6.1.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "scalafmt-core" } ]

labels: library-update, semver-patch

Codecov Report

Merging #187 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #187   +/-   ##
=======================================
  Coverage   90.98%   90.98%
=======================================
  Files           8        8
  Lines         122      122
  Branches        6        6
=======================================
  Hits          111      111
  Misses         11       11

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8d2dc5d...f8e9f02. Read the comment docs.

repo: circe/circe-jackson


text:
Update scalatest to 3.2.0

Updates org.scalatest:scalatest from 3.1.2 to 3.2.0.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalatest", artifactId = "scalatest" } ]

labels: test-library-update, semver-minor

Codecov Report

Merging #124 into master will decrease coverage by 0.98%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #124      +/-   ##
==========================================
- Coverage   96.07%   95.09%   -0.99%
==========================================
  Files           4        4
  Lines         102      102
  Branches        4        5       +1
==========================================
- Hits           98       97       -1
- Misses          4        5       +1

Impacted Files
Coverage Δ

src/main/scala/io/circe/yaml/Printer.scala
97.91% <0.00%> (-2.09%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7ac3bc0...994aef2. Read the comment docs.

repo: circe/circe-yaml


text:
Updated header (Nav Bar) for hiding reports page

Hiding Reports page
due to no current data being presented needed to hide this page until it gets updated.
frontend/src/components/Header.tsx
commented out line 250-255 to hide page.

🗣 Description
frontend/src/components/Header.tsx
comment out line 250-255 to hide the page.
Will need to uncomment when reports page is finished.
💭 Motivation and context

Clients get confused on reports page when nothing is presented currently.

gives dev team a chance to update the reports page
🧪 Testing

used local crossed to verify changes

before when reports page was present to

reports page hide on the nav bar.

@epicfaace Rachel asked Courtney to hide this page until it is functional. I'd like your input as to whether we should comment it out or remove it (based on how we typically handle unused code).

I would check with P&E team / Andy / Lamar before removing it. I know the page does include reports for federal agencies enrolled in P&E. If we need to use it for P&E, I’d suggest showing it only for govt agencies organizations and hiding it elsewhere.
@aloftus23 @stewartl97

(The reports are only visible if you select a fed agency in the organization dropdown).

We spoke about it in the meeting today. It looks like it isn't being used on either site at the moment. The consensus was commenting out the code until we add reports functionality.

Yes, in that case, let's comment it out. Good to comment it out as we might need to re-add it in the future.

I fixed the linting errors and replaced the header snapshot (the snapshot caused failure of the "Header matches snapshot" test. Additionally I fixed a type error related to the Organization interface used for testing by adding pendingDomains to testOrganization.

updated typo/ commit from Ashwin's suggestion. Updated the branch since master had some changes since then. All changes approve and branch has no conflicts. Merged to master.

authors: Matthew-Grayson courtneyc1 epicfaace

repo: cisagov/crossfeed


text:
Upgrade to Guacamole 1.5.0

🗣 Description
This pull request upgrades the Docker composition to use the recently-released  guacamole/guacd:1.5.0 and guacamole/guacamole:1.5.0 Docker images.
💭 Motivation and context
Guacamole 1.5.0 is the latest release, and is therefore likely to be more performant and secure.  Also, Guacamole 1.5.0 resolves a few issue for us...
🧪 Testing
I deployed these changes to our COOL staging environment and verified that they functioned as expected.
✅ Pre-approval checklist

[x] This PR has an informative and human-readable title.
[x] Changes are limited to a single goal - eschew scope creep!
[ ] All future TODOs are captured in issues, which are referenced in code comments.
[x] All relevant type-of-change labels have been added.
[x] I have read the CONTRIBUTING document.
[x] These code changes follow cisagov code standards.
[ ] All relevant repo and/or project documentation has been updated to reflect the changes in this PR.
[ ] Tests have been added and/or modified to cover the changes in this PR.
[ ] All new and existing tests pass.

✅ Pre-merge checklist

[ ] Revert dependencies to default branches.
[ ] Finalize version.

✅ Post-merge checklist

[ ] Create a release.

We will need to wait for the release of version 1.5.1 because we are encountering this bug.  It appears that version 1.5.1 should be released any day now.

repo: cisagov/guacamole-composition


text:
spreadsheet_tools.py line 299 had attribute .name on dns_data which d…

…idn't exist. Removed .name and resolved bug.

🗣 Description

💭 Motivation and context

🧪 Testing

✅ Pre-approval checklist

[ ] This PR has an informative and human-readable title.
[ ] Changes are limited to a single goal - eschew scope creep!
[ ] All future TODOs are captured in issues, which are referenced
in code comments.
[ ] All relevant type-of-change labels have been added.
[ ] I have read the CONTRIBUTING document.
[ ] These code changes follow cisagov code standards.
[ ] All relevant repo and/or project documentation has been updated
to reflect the changes in this PR.
[ ] Tests have been added and/or modified to cover the changes in this PR.
[ ] All new and existing tests pass.

✅ Pre-merge checklist

[ ] Revert dependencies to default branches.
[ ] Finalize version.

✅ Post-merge checklist

[ ] Create a release.

Hotfix for DNS bug

Fix DNS bug when running second pass in NAVV


text:
[Feature Template] Cannot edit "vpn ethernet interface"

Summary
N/A
Logs and external information
No response
Reproduction script
N/A
On what platform(s) does it occur?
Not Applicable
Issue Severity
Medium: There is a workaround

This issue was migrated from an old repository: https://github.com/CiscoDevNet/catalystwan/issues/158

repo: cisco-open/cisco-catalyst-wan-sdk


text:
adding --all to solution check to validate all fmm related components…

… in the solution
Description
Please provide a meaningful description of what this change will do, or is for. Bonus points for including links to
related issues, other PRs, or technical references.
Note that by not including a description, you are asking reviewers to do extra work to understand the context of this
change, which may lead to your PR taking much longer to review, or result in it not being reviewed at all.
Type of Change

[ ] Bug Fix
[ ] New Feature
[ ] Breaking Change
[ ] Refactor
[ ] Documentation
[ ] Other (please describe)

Checklist

[ ] I have read the contributing guidelines
[ ] Existing issues have been referenced (where applicable)
[ ] I have verified this change is not present in other open pull requests
[ ] Functionality is documented
[ ] All code style checks pass
[ ] New code contribution is covered by automated tests
[ ] All new and existing tests pass

Codecov Report

Merging #33 (52d28d2) into main (abe6d91) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##             main      #33   +/-   ##
=======================================
  Coverage   30.26%   30.26%
=======================================
  Files          23       23
  Lines        3000     3000
=======================================
  Hits          908      908
  Misses       2023     2023
  Partials       69       69

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

authors: codecov-commenter rquedas

repo: cisco-open/fsoc


text:
Re-check consistency of schema.json

Once #198 has been fixed, we need to re-check against schema.yaml to ensure consistency.
Fixing this issue will include

a full check against schema.yaml and past merges (done in #205)
the fixes originally made in #192, which will now be closed (this is done in PR #203)
removing schema.yaml (done in #205)

Done, and merged.


text:
[New Tool] cffreference:  Cite Existing CITATION.cffs in Yours

Who needs the new tool?
Any people who would like to automate the citing of other projects by their CITATION.cffs.  Hence, it is also great for build routines.
What should the new tool enable users to do?
People who would like to use cffreference can give it the path to an existing, readable and valid input CITATION.cff which will then be analysed regarding the lines to add to their own CITATION.cff.  If there is a preferred-reference configured, it will be used, by default.  If the output file is omitted, the results will be written to stdout, otherwise, the output will be appended to the given readable and writable output file (if it does not already exist, it will be created that way).
For instance, when having a local copy of this repository in order to provide the input file, one can cite it in the own repository using:
cffreference ../path/to/citation-file-format/CITATION.cff ../path/to/my-project/CITATION.cff

What benefit would the new tool add?
Users will be able to automatically cite other projects in theirs.
Implementation suggestions
My implementation suggestion can be found here:  https://github.com/kevinmatthes/cffreference.  It is written in Haskell (according to Haskell2010) and has a GNU Octave-based build routine.  The license is GPL 2.0.
It is just a draft (or "rapid prototype" in the terms of software engineering) but it sufficed to create a valid CITATION.cff for its own repository.
Can you help?

[x] Yes
[ ] No

About an hour ago, I released version 0.2.

Version 0.4 fixes the citation of preferred-citation sections.  Furthermore, it applies the configured type of a preferred citation automatically and assumes the input file to be of type: software, by default.

Version 0.5 introduces two new placeholders to place in a CITATION.cff, at option:  --- and ....  They are considered comments and will, hence, be skipped.

@kevinmatthes Thanks! As mentioned in #375, this is really helpful. Should we add it to the list of tools?

Yes, you are free to do so!
Please note that I am about to refactor the application in Rust, at the moment.  The original Haskell prototype still works, just the Rust version is not completely stable, yet.  When I finish the work on the Rust version, the Haskell prototype would become deprecated and is going to be replaced by the Rust executable in future releases.
I begun to refactor the prototype in Rust since it is easier to add command line option parsing in Rust than in Haskell.  In future releases, I plan to add some features using options, so the maintenance overhead would decrease.  Furthermore, the installation procedure is easier and the portability higher; the Haskell Platform appears to have different default content on multiple platforms what would disadvantage their users since they would need to install the respective missing libraries by hand using Cabal.
Anyway, you can add it as Haskell application since the Rust version is not finished, yet.  The Haskell version does not need any exotic libraries, so it is expected to work on multiple platforms.

Thanks @kevinmatthes! I've opened #384 to add this as a Haskell tool for now.
I'll let the PR auto-close this issue, but please reopen (or create a new one) when the Rust tool is implemented, and I'll make the necessary changes to the tools table then.

Okay, I will open a new issue, then. :+1:

authors: kevinmatthes sdruskat


text:
feat: add no-js support

Adds no-js support to the docs site, based on the same model as public website:

add html.no-js to the default layout
remove it again in a script block in the head
add some error handling in the main js file

Nice! A side question - does the component_example.erb also need no-js support (not sure how this works when it's an iframe)

I think we're ok, because:

the components are rendered in the iframe view and they should be build to handle the absence of JS anyway, if they need to (eg target content and disclosure just appear open
the ComponentExample component is OK because it uses components (🤯) that are already fine without JS

LMK if I've misunderstood tho and we can have a chat - I'll wait till you get back to me 🙂

I think we need to check this for every component that uses js - I just found that on-this-page with nested links doesn't show the nested links if js is disabled. Targeted content is a nice example as it doesn't rely on .no-js in the scss. The ones that do, if added as an iframe (which I don't know how much we'll do) or when open in a new tab will not work so smoothly without .no-js.

For the component iframe / new window I think mirroring the same no-js scripts in https://github.com/citizensadvice/design-system/blob/72188ce0f0c5194b7096252621a6604d73e34c10/design-system-docs/src/_layouts/component_example.erb would cover us there.

I think we need to check this for every component that uses js - I just found that on-this-page with nested links doesn't show the nested links if js is disabled. Targeted content is a nice example as it doesn't rely on .no-js in the scss. The ones that do, if added as an iframe (which I don't know how much we'll do) or when open in a new tab will not work so smoothly without .no-js.

Ah - gotcha! Yup I'll add no-js to the layout for the iframe view as @davidrapson suggests.
For on this page, my recollection is that not showing the nested links was a conscious decision since:

they are displayed hidden by default
showing all of them at the same time would be too much
the core behaviour is seeing the main links and the show/hide is a nice sprinkle of prog enhancement on top

repo: citizensadvice/design-system


text:
Adds tests for apps.get_model

In issues #99 and #138, we had some problems when getting tenant column, when getting class with apps.get_model
Problem fixed wirh previous developments. I added a test to test the case

there's a skipped test in the check details. As discussed offline, we'll create another issue for it. It's unrelated to this pr

Two questions:

The migration reverse_func() is uncovered by tests. While that seems potentially harmless, is it typical for the other test migrations? Or do we cover them by tests in some way?
You're adding the test after the fix. Have you verified that the test fails prior to applying the fix? (Just want to be sure it's an effective test.)

Removed reverse_func,
Yes always verifying. When I'm working tests always fails, at the end I succeed to make them pass

authors: agedemenli gurkanindibay

repo: citusdata/django-multitenant


text:
Provide a mechanism to change the tile colors with Citizens/Builder lenses

I am not positive it's possible to do in-code (because it may require using values that are statically set in the XML only), but being able to customize the lens colors would be nice.  I've wanted this kind of thing for a while, and at least one other person is asking about it on the Steam support page.
I'll add screenshots later, perhaps... otherwise this is just getting this written down.

(note: pinning this as the current thing I'm working on and I want it to get visibility incase any of y'all wander by)
I've been thinking about this one a while and I decided to start giving it a shot.  I have the beginnings of something together, after updating the MoreLenses integrated code, as these changes are in MoreLenses directly.
Still a fair bit of work to do (there are many more lenses to color, it'd be nice if it applied immediately once the settings menu was closed, it'd be nice if there was a way to easily save these off in the settings file or whatever...), but here's at least a proof of concept:

Lens are mostly handled by the game engine. There's really a few only that can be used at all for modding purposes.
So, those that are handled internally - probably nothing can be done about it.
The ones used by modders - yes, you can. Your example is actually the specific lens that allows for coloring the tiles with a given color. That is why it used very often but also that is why you can only have one such lens active - because there is actually only one available.

welcome back!  Yep, this work has an interesting exercise on the lenses stuff.  All of the modlenses use the same "hex appeal" lens, and the idea has been to at least provide the ability to change the color for the modded lenses.  The branch from my draft PR ( #300 ) has this added for all of the modded lenses except for the city overlap one (and maybe one other), though there's something not quite right with the Resources lens updating the Key for the modal panel.  Otherwise it's code cleanup, adding the localized strings for new items and making sure I didn't make more changes than necessary.


text:
Status Tracking: When a status is selected present confirmation dialog

When the program admin selects a new status show the confirmation dialog.

@shanemc-goog / @rahaghas
Were there any mocks indicating what the confirmation dialog would say? I'm also happy to just propose text and address it in the PR review.

Presumably, we want the behavior when the user cancels the confirm dialog to be to restore the previously selected status and do nothing. We likely also want the confirmation message to include the previous and to-be-set status as well.
Typically, we do all of this through a modal. However, modals have preset static content for the most part. We could do some tricks to adjust modal content. In this case, though, it feels like we might be able to get away with using the standard Javascript confirmation API. It's not as pretty as a modal, but we can dynamically build the content and it makes for a better flow for preventing updates. We have precedent for using this in the applicant-facing experience when removing an enumerated entity.
For expediency, I plan to start there and we can adjust if we think this is too divergent from the experience we want.

Mocks are here

I'm also recalling that Status and Notes are set differently, so will need a path for each, changing status is priority though.

Thanks for the mocks. I think "Notes" aren't in scope for V1, correct?

I had it in the V1 mocks, but idk. @cassandralfernandes ?

Regarding the confirmation modal shown. I'll scrap my idea from https://github.com/civiform/civiform/issues/2912#issuecomment-1217053343 since I'd forgotten that we wanted to allow triggering / not triggering the email.
We don't create dynamic modals throughout the codebase, so we'll need to come up with a solution. The simplest would be to create a modal for each status and show the correct one depending on the selection. That's a little bit wasteful but is also consistent with what we do elsewhere.
In an ideal world, we'd create a template for the modal with dynamically configurable attributes for each of the things that change (e.g. new status name, email configured, etc). Our current modal framework wouldn't really support this without additional custom JavaScript. That said, we'll need to add custom JavaScript anyway in order to pop the modal when the selection changes anyway.
Given that, I'm going to start by trying to develop the dynamic solution. If it becomes a timesink, I'll fallback on the modal-per-status approach.

@rahaghas I may have just misunderstood.
One thing we're going to need to figure out is where to display the "list of previous statuses" and "list of notes" within the existing Program Admin UI. Do you have suggestions for that once @shanemc-goog 's data modeling change is available?

Can we treat rendering the historical info as a V2?

That would work for me. In that case, the status selector would be the place we'd always show the current status, so there'd be no problem and we could tack on status history in V2.
In my opinion, if we didn't display the history for notes, there wouldn't be much use in having an "Add note" button in V1.

Why's that? Users can still keep a log of notes but just editing the note and keeping the previous string as part of it. But regardless I see value in being able to append a note.

Gotcha. I'd forgotten about that. In the mocks I saw the dialog title being "Add a note" and extrapolated from there. We can use the "Edit note" trigger to show the existing note for now.

Sounds good!

authors: clouser2 rahaghas shanemc-goog

repo: civiform/civiform


text:
Add application lifecycle stage to the API

This will need a small design doc to ensure we're on the same page about how to expose enums via the API

I see that we already have a method called Application.getLatestStatus(). Is this related to application lifecycle? I checked my dev db and see a sample value of "Pending Review" (though I think that value was set by the seeding process).

authors: avaleske yotommy


text:
ghost : add new how to in post-install

Add step to :

Create admin user.
Delete default user created by ghost.
Create your first blog.

lgtm

repo: civo/kubernetes-marketplace


text:
🛑 Homepage is down

In 2adeb79, Homepage (https://cjthedj97.me) was down:

HTTP code: 403
Response time: 39 ms

Resolved: Homepage is back up in 34d8b1b.


text:
🛑 GitLab is down

In 6a464a6, GitLab ($GIT) was down:

HTTP code: 502
Response time: 208 ms

Resolved: GitLab is back up in c0cee78.


text:
feat(config-manager):add xudt config

Description

Adding XUDT config required for the nervos docs site

xUDT config info comes from https://github.com/Magickbase/ckb-explorer-public-issues/issues/510

authors: Keith-CY sunchengzhu

repo: ckb-js/lumos