cmd/go: broken go.mod resolution across modules

What version of Go are you using (go version)?

% go version
go version go1.12.2 linux/amd64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
% go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/cy/.cache/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/cy/go"
GOPROXY=""
GORACE=""
GOROOT="/home/cy/go/go1.12.2"
GOTMPDIR=""
GOTOOLDIR="/home/cy/go/go1.12.2/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/cy/tmp/relmods/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build084314890=/tmp/go-build -gno-record-gcc-switches"

What did you do?
I am experimenting with a multi-module project setup where one module is located in a sub-directory of another module. When executing a build/run/test command for the child directory from the parent directory, it updates the go.mod in the parent. It's not totally clear to me if this is expected behavior. At the very least it is unintuitive and makes managing a multi module repository a bit tricky.

% ls -R
.:
go.mod  submod

./submod:
go.mod  go.sum  main.go

% cat go.mod
module relmods

go 1.12

% cat submod/main.go
package main

import log "github.com/sirupsen/logrus"

func main() {
        log.Info("hello")
}

)% cat submod/go.mod
module submod

go 1.12

require github.com/sirupsen/logrus v1.4.1 // indirect

% cd submod && go run main.go && cd ../
INFO[0000] hello

% cat go.mod
module relmods

go 1.12

% go run submod/main.go
INFO[0000] hello

% cat go.mod
module relmods

go 1.12

require github.com/sirupsen/logrus v1.4.1 // indirect

What did you expect to see?
The go.mod of the parent is untouched, and the go.mod of the child is used to calculate dependencies.
What did you see instead?
The go.mod of the parent is modified.

If you put multiple modules in a repository they are considered completely unrelated as far as requirements. The repo ends up just being a container for two independent things. In particular, when the "parent" imports something from the "child", it imports a fresh copy downloaded as any other module; it does not care that there is a working copy in a subdirectory.
Similarly, when you run go run anything.go from a particular module (in your example, the parent), what matters is the working directory of the go run command, not where the source file was found. The fact that it is in a directory with a different go.mod is not relevant.
I am skeptical that you really want to be using multiple modules in the repo. You probably don't.

Switching to vscode helped me work around this issue, since it takes directory into account when running tools.
I also use Repos as containers for multiple modules.  This allows me to break down a large module/package into a few smaller modules/packages, each with it's own set of dependencies clearly documented in each go.mod.
A parent module is then just referencing sub modules for it's own dependencies.  (using the go.mod 'replace' directive during development makes this a lot easier to work on the submodules at development time, but it would be nice if this work-around wasn't required).
But maybe the tools could be a bit more verbose about what they are assuming and doing.  eg I had another situation where the tools were trying to download a dependency that was local only (using the 'replace' directive), and strange error messages after a module rename, when the tools were still searching for the old name.  Both with multi-module projects.
Maybe I have just spent too many years working with dependency tools like Maven where parent modules is a very common pattern.

For context I am experimenting with golang 'monorepo' repository structures.
Multi-module seemed to allow owners of a service/project/component to have more control over their dependency versioning, but seems confusing and unadvised as evidenced by this bug.
A single module repo is workable for us. I think we can even achieve allowing different components to run different versions of third party dependencies by using 'replace' directives. The only annoyance is that we must manage all of this from a single file at the root of a repo, there does not seem to be a clean way to create a hierarchy that works well with an OWNERs file system.

@y3llowcake, this seems to be working as designed.
The main module is always the module containing the working directory of the go command invocation. When you pass a list of .go files explicitly on the command line, those files should be compiled as if they are a distinct package within the main module, and the main module's dependencies are updated such that the command you just invoked will be reproducible.
In contrast, you should find that go run ./submod produces an error due to crossing a module boundary.


Resolve #4: Pretty print JSON API definition

Coverage remained the same at 100.0% when pulling ffb580c3e7761920098dade861c41a7a5e66564b on feature/4-prettyprint-json into 5f13b9491f7f4f07f7d7ab777dafc1d2c4f3fd58 on master.

:+1:


New Project : A Voice Powered React App - Budget Tracker

A voice-powered budget tracker React app that will allow users to track their expenses and manage their budget using voice commands. The app will leverage the power of React and speech recognition technology to provide a seamless and intuitive user experience.
By developing a voice-powered React app for budget tracking, I aim to provide users with a convenient and efficient way to manage their finances. The app will leverage React's flexibility and the power of voice recognition technology to deliver an intuitive and user-friendly experience. I am confident that this app will greatly benefit users in tracking their expenses and achieving their financial goals.
Please assign me this project under Gssoc 23

@Dharmesh17 @artimanputra @Shreyaar12

A voice-powered budget tracker React app that will allow users to track their expenses and manage their budget using voice commands. The app will leverage the power of React and speech recognition technology to provide a seamless and intuitive user experience.
By developing a voice-powered React app for budget tracking, I aim to provide users with a convenient and efficient way to manage their finances. The app will leverage React's flexibility and the power of voice recognition technology to deliver an intuitive and user-friendly experience. I am confident that this app will greatly benefit users in tracking their expenses and achieving their financial goals.
Please assign me this project under Gssoc 23

assigned to @MohnishK7
Complete this within 1 week and
Include a screenshot or deploy link to assess your project and thereafter include your project in the main code with following the contributing.md guidelines

Thanks . Sure I'll be back in a week.


Getting Authorization Error on browser

When I run project with specified command:   python main.py --project_id='my-proj-id'
It spits out a url to paste to in browser for authentication. When I paste the URL on browser, I get following error:
Error 400: redirect_uri_mismatch
The redirect URI in the request, urn:ietf:wg:oauth:2.0:oob, can only be used by a Client ID for native application. It is not allowed for the WEB client type. You can create a Client ID for native application at https://console.developers.google.com/apis/credentials/oauthclient

I generated the oAuth credentials for web application. Can you please tell what do I need to setup to make this code work?

Please generate the OAuth Credentials for a "Desktop app" instead. Refer to this Support page for more information.

Please generate the OAuth Credentials for a "Desktop app" instead. Refer to this Support page for more information.


How to generate a 204 no content response?

Hi,
How is it possible to document a 204 status no content response using @success, e.g // @Success  204  object  nil "No response"?
Is this functionality possible?

@dcs3spp yes use the following comment
// @Success 204 "No Response"

@parvez3019 many thanks :)


IntelliJ's import order overrides plugin's order when "Optimize imports on the fly" is set

When organizing imports automatically with option "Optimize imports on the fly" the plugin seems to handle the correct order, but after a ~ second the order gets overridden by the IntelliJ import order settings.
IntelliJ IDEA 2016.2
Build #IC-162.1121.32, built on July 9, 2016
JRE: 1.8.0_76-release-b216 x86
JVM: OpenJDK Server VM by JetBrains s.r.o
Plugin <IP_ADDRESS>7.0

Known issue.

any update on this?


improve Add config ignore_backup_tmp_partitions

What problem does this PR solve?
Issue Number: close #xxx
Related PR: #xxx
Problem Summary:
To filter tmp partitions, instead of report exception.
Release note
None
Check List (For Author)

Test

[x] Regression test
[ ] Unit Test
[ ] Manual test (add detailed scripts or steps below)
[ ] No need to test or manual test. Explain why:

[ ] This is a refactor/code format and no logic has been changed.
[ ] Previous test can cover this change.
[ ] No code files have been changed.
[ ] Other reason

Behavior changed:

[x] No.
[ ] Yes.

Does this need documentation?

[ ] No.
[ ] Yes.

Check List (For Reviewer who merge this PR)

[ ] Confirm the release note
[ ] Confirm test cases
[ ] Confirm document
[ ] Add branch pick label

run buildall

run buildall

run buildall


Governance / Permissioning Tracking Issue

Summary
This is a general tracking issue for all the work around governance control of smart contracts
to make a "permissioned" smart contract system possible.
Problem Definition
The requirements are set forth in the Cosmos Hub Proposal 25 which passed, and which we need to implement
Some additional context may be present in the forum discussion
Proposal
Exact steps will be defining in smaller issues. This defines the architecture for the whole project. Issues:

[ ] Add Governance Proposals #162
[ ] Control who can instantiate code #163
[ ]  Control who can upload code #164

We will add three new governance proposal types to handle the contract lifetime and some more metadata to control the permissioning. Note this does not affect executing contracts, but rather the larger "privileged" lifecycle: upload, instantiate, migrate, which often restricted to an owner.
You should consider the hub governance as root. It can execute any privileged operation on any contract. If you do not want this, then disable those governance proposal types in the binary, so the governance oversight / backdoor (depending on your view) doesn't exist. This means that governance can migrate/burn a contract even if it is marked "immutable". We will add at least three new proposal "content" types. The basics would be UploadCodeProposal, InstantiateContractProposal, MigrateContractProposal. We would also likely want to add an UpdateAdministratorProposal, as hub governance may not want to migrate directly but appoint a new committee as administrator to some contested contract after the instantiation (or change the committee responsible).
Beyond the root control, we also want to allow delegating to a subcommittee for quicker oversight. This ends up with upload and instantiate having a permission of Nobody | Somebody(Address) | Anybody and migrate of Nobody | Somebody(Address). The permissions for upload can be stored in module-level Params, which the permission level for instantiate can be stored on the CodeInfo. The Params should list the permission required for uploading and the default permission for instantiating (likely Anybody or Nobody depending on the chain). The CodeInfo permission level can also be set when uploading (overriding Params default).
I believe there is already a generic governance proposal type that can make params changes in the module to update that when needed. If we want to get very extensive, we can also add a message and proposal type to change the permission level of an existing CodeInfo, but that is really quite unnecessary as we could just upload the same wasm again as another CodeInfo but with the desired permissions (this assumes we want to loosen them up).

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

Very good summary.

The Params should list the permission required for uploading and the default permission for instantiating (likely Anybody or Nobody depending on the chain).

My first thought was default should be "owner". Somebody invested time and resources to create and upload the contract. We should protect this effort.

If we want to get very extensive, we can also add a message and proposal type to change the permission level of an existing CodeInfo, but that is really quite unnecessary...

There may be the use case where access to the contract's account needs to be granted this way. It is not about the (byte) code only.
A general permission system would make the administrator field obsolete as this would be a permission now. I like it.

My first thought was default should be "owner". Somebody invested time and resources to create and upload the contract. We should protect this effort.

Sounds fair. If unset, only owner (like a custom uniswap module). But they can set to let anyone use it. (Like a generic cw20 module).

This is what I you also had in mind, I guess. There could be odd settings like "migrate" set to Somebody with ContractInfo.Admin = nil stored that we should prevent

I am not fully sure I get it.  You want to store the Everybody / Somebody / Nobody enum where? I assume it would be in the same object as (and next to) the field that stores "Somebody" value - those fit together, either in one struct or two fields.


Markdown preview often displays wrong file

VSCode Version:1.5.2
OS Version:Windows 10

I don't have a consistent repro for this but it happens at least once a day to me. I'm working on one Markdown file and then use the title bar preview button to display the Markdown preview. VS Code displays Markdown preview for a different file, not my active editor.

The behavior seems to be to preview the first file in the editor group even when the file doesn't have focus. After closing the preview, the next preview correctly previews the active editor.

This seems to happen pretty frequently when using the menu bar button. Repo steps for me:

Launch VSCode with a clean workspace with two markdown files.
Open one file and then the other.
Click the markdown preview button in the menu bar. This shows a preview of the first opened filed instead of the second.

From debugging, it seems that the markdown.showPreview event for the menu button click is sending us the wrong document, even if you change the focus to the second markdown document by clicking on it. I'll investigate this further.

I have this happen to me all the time in v1.5.3. The preview button creates a preview of a previously opened file. The file can be one of the open editors or it can be closed. I have had it happen when I only had one file open in the editor, then click the Preview button. It opens a previously edited file.

Solved? still in 1.6

Just upgraded VS Code and still have this problem.
Version 1.6.1
Commit 9e4e44c19e393803e2b05fe2323cf4ed7e36880e
Date 2016-10-13T16:21:53.542Z
Shell 1.3.7
Renderer 52.0.2743.82
Node 6.5.0

Closing as duplicate of #12837, which seems to be the root cause of this problem and is not specific to markdown


[BUG] Nvidia mode not fully working in Wayland

Describe the bug
When using Nvidia mode, I expect every piece of software to only see and use the Nvidia GPU. However, many pieces of software, such as Blender (!), GPU Screen Recorder, Firefox, etc, as well as Wayland itself, run on the Intel GPU unless I launch them with the __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia env vars. I wouldn't expect these env vars to ever be necessary when using Nvidia mode. This doesn't seem to be the case in X11.
To Reproduce
Steps to reproduce the behavior:

Use Nvidia mode on Wayland
Launch Blender or any other non-game app where you still want to use the Nvidia GPU.

Expected behavior
All software should be running on the Nvidia GPU
Screenshots
Not applicable
System Information:

Model: MSI GE65 Raider 9SF
Distro: EndeavourOS
Kernel: 6.10.2-arch1-1
DE/WM and Display Manager (if applicable): KDE Plasma 6.1 / KWin 6.1
EnvyControl version: 3.4.0-1
Nvidia driver version: 555.58.02
lspci output:

00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers (rev 0d)
00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) (rev 0d)
00:02.0 VGA compatible controller: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] (rev 02)
00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH Thermal Controller (rev 10)
00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10)
00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10)
00:15.0 Serial bus controller: Intel Corporation Cannon Lake PCH Serial IO I2C Controller #0 (rev 10)
00:15.2 Serial bus controller: Intel Corporation Cannon Lake PCH Serial IO I2C Controller #2 (rev 10)
00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI Controller (rev 10)
00:17.0 SATA controller: Intel Corporation Cannon Lake Mobile PCH SATA AHCI Controller (rev 10)
00:1b.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #17 (rev f0)
00:1b.2 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #19 (rev f0)
00:1b.4 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #21 (rev f0)
00:1d.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #9 (rev f0)
00:1d.6 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #15 (rev f0)
00:1f.0 ISA bridge: Intel Corporation HM470 Chipset LPC/eSPI Controller (rev 10)
00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10)
00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10)
00:1f.5 Serial bus controller: Intel Corporation Cannon Lake PCH SPI Controller (rev 10)
01:00.0 VGA compatible controller: NVIDIA Corporation TU106M [GeForce RTX 2070 Mobile] (rev a1)
01:00.1 Audio device: NVIDIA Corporation TU106 High Definition Audio Controller (rev a1)
01:00.2 USB controller: NVIDIA Corporation TU106 USB 3.1 Host Controller (rev a1)
01:00.3 Serial bus controller: NVIDIA Corporation TU106 USB Type-C UCSI Controller (rev a1)
03:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a)
04:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983
06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. Killer E2600 GbE Controller (rev 21)

I've been looking at other issues and it seems that the reason Nvidia mode is not supported on Wayland is Nvidia not having proper Wayland support? This is no longer the case however, as Nvidia drivers starting from driver versions 555 have proper Wayland support now. So could this be reconsidered? Is it possible to add Nvidia mode support now?

I have the same problem, version 555 driver, I use wayland and envycontrol, but the applications use embedded graphics, although nvidia mode is set

Wayland is not supported as it requires a DE/WM specific logic to override the primary GPU.
I remember GNOME has a setting for that but at the time I tested Nvidia had completely broken Wayland support (only external screens worked and it was prone to crashes). For KDE I’m not sure.

On kde plasma wayland you can choose which device to use as the primary device by using the KWIN_DRM_DEVICES environment variable. You do it like this KWIN_DRM_DEVICES=/dev/dri/card1:/dev/dri/card0 and it will prioritize card1 over card0. I tested it on an intel laptop with dedicated nvidia gpu and it works and it can display both the laptops monitor (powered by the intel iGPU) and the external monitor (powered by the nvidia dedicated gpu)

FWIW, I have successfully added GPU preference using the freedesktop.org .desktop file configuration. I did this for the kitty terminal for example.
I copied the kitty.desktop file into ~/.local/share/applications/kitty.desktop and added the following line:
PrefersNonDefaultGPU=true
Setting it to false does not preclude it from using the discrete GPU, but certain apps (like VS Code) will switch to the integrated GPU when set to false (at least in my experience).
Be aware that, as the docs linked above suggests, support for this hint is WM/DE (as @bayasdev said above) and app specific.
FYI - here is my setup:
Fedora WS 41
GNOME 47.1 using mutter (Wayland) WM
rpmfusion nvidia 565 driver (akmod)
Acer Nitro 5 with RTX 3050 Ti Mobile


Use LLVM

LLVM provides better optimizations in the backend.  It already has GC support via statepoints.

That's a really good idea, however, it would be incredibly hard to do this since the code is not made to be adaptable to other architectures easily.


feat: add support for custom attribute types

A fork of #23, so that should probably be merged first. Please don't look at this before that has been merged, as that gives a bad impression diff-wise.
This feature adds strong-typing of attributes, their labels and names, but also allows runtime introspection of such attributes. This can be helpful for adding validation (making sure a particular field is actually a valid custom attribute name) etc. The opportunities are huge for this.
The actual runtime information is behind an emitted function (getAttributeConfigurations) on purpose. This is because it is then tree-shakeable, so it doesn't become part of the compiled bundle of most web apps today, if not used. If you do not like this, I can make a version that only has the types. However, we have several use-cases where we'd love to have the information readily available at runtime as well.
CC @gismya.

[x] I have added automatic tests where applicable
[x] The PR title is suitable as a release note
[x] The PR contains a description of what has been changed
[ ] The description contains manual test instructions

Changes

Test

@gismya if you want a clean diff of this before the other one is merged, I made a draft PR here:
https://github.com/ffMathy/ftrack-ts-schema-generator/pull/1/files

I forgot to mention that this fixes #16.

Conflicts resolved!


Generate HTML5 date/time inputs by default

It's a long time ago since HTML5 date/time support was included in simple_form https://github.com/heartcombo/simple_form/pull/935 and since then as the docs describe by default they are disabled https://github.com/heartcombo/simple_form/pull/1150 because at the time the browsers weren't ready for them, but I think now 8 years after, the browsers are ready as mdn browser compatibility suggests https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/date#browser_compatibility, what do you think about simple_form turn on the generation of these html5 inputs by default?
This probably would be a breaking change and would require a major release, I suppose

This can be implemented without breaking change, but just add another config option which is false by default:
# initializer
SimpleForm.setup do |config|
  config.default_html5_date_time = false
end

# input helper (simple_form/inputs/date_time_input.rb#L34)
def use_html5_inputs?
  input_options.fetch(:html5, SimpleForm.default_html5_date_time || false)
end

It looks like a bug to be honest. https://github.com/heartcombo/simple_form/blob/main/lib/simple_form/inputs/date_time_input.rb#L35 it doesn't use html5 config from the wrapper but uses html5 option from the input options. @carlosantoniodasilva do you thing we should make it work the same as e.g NumericInput works?

@nashby yes. I think we should match the behavior.

I just experienced this. For anyone reading, you have explicitly set html5: true, as: :date on the field to have it render correctly.

I opened a PR for this. It's not a breaking change, but it's definitely a change to the default behavior since the generated default wrapper is using the html5 component.


Changing the velocity root-finding

Changing the velocity root-finding, line 13 of algorithm 1 in the tandem paper.
Instead of searching for $V$ S.T
$\sigma_n F(V, \psi_{k}^{e}) + \eta V - T = 0$
searching for $\xi$ S.T
$V = 10^{\xi}$
It was tested against bp1 bp3, and my own SSEs simulations and it shows ~40% improvement in run time when running with green functions.
bp1:
new root-finding run time: 554.237
main run time: 888.816

bp3:
new root-finding run time: 4099.94
main run time: 6373.47

Is more testing needed before merging into main? If so, what would you like to test?

@dmay23
@AliceGabriel

In the vast majority of cases, we are performing just the first iteration of the for loop with xi=5. This saves time in the root-finding (searching on shorter intervals).

The new profiling report was running during the night and done more robustly, with a comparison of 10 runs of the new root-finding and the main branch version.

bp1:
New root-finding run time: 371.4818
Main run time: 757.6242
bp3:
New root-finding run time: 2179.287
Main run time: 4531.09
Overall, 51% and 52% for bp1 and bp3, respectively, improvement over the main branch and ~10% improvement over the hardcoded very small number version.

An alternative approach to the for loop will be to try xi=5, and if this fails, to go immediately to std::nextafter(0, INFINITY).

@yohaimagen Could you please implement your suggested option 3?  I really like this idea.

For what it is worth, I re-run clang-format over all the files changed in
each branch before I merge them. If people do this themselves this does
reduce work on my side.
On Sun, 3 Nov 2024 at 23:59, Thomas-Ulrich @.***> wrote:

@.**** commented on this pull request.
In app/localoperator/DieterichRuinaAgeing.h
https://github.com/TEAR-ERC/tandem/pull/78#discussion_r1827316091:

     auto eta = p_[index].get<Eta>();

     auto tauAbsVec = tau + p_[index].get<TauPre>();
     double snAbs = -sn + p_[index].get<SnPre>();
     double tauAbs = norm(tauAbsVec);
     double V = 0.0;

   if (eta == 0.0) {

   double a = -32;

   double a_min = std::log10(std::nextafter(0, INFINITY));

   double b;

   if (eta == 0.0)

[minor suggestion]
to adhere the format of the initial code, you can use clang-format on your
file:
clang-format -i app/localoperator/DieterichRuinaAgeing.h
—
Reply to this email directly, view it on GitHub
https://github.com/TEAR-ERC/tandem/pull/78#pullrequestreview-2412374248,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADO6RJZG2OMM27LMFRNXH7DZ64SOXAVCNFSM6AAAAABPGQ4AKKVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDIMJSGM3TIMRUHA
.
You are receiving this because you were mentioned.Message ID:
@.***>


S3 Bucket data sharing

Is your feature request related to a problem? Please describe.
When I use tools in my ETL or data consumption applications, I often need direct access to the source data S3 Bucket. Lake Formation in some cases does not perform sufficiently fast and S3 access points do not integrate with some of the used tools. At the moment we solve this challenge by manually providing permission in the Bucket policy of the source Bucket.
Describe the solution you'd like
For this particular cases we would like an automated way to manage access to S3 Buckets.

We want a self-service workflow with sharing request and approval and at the same time
we want to use S3 Bucket policies under-the-hood.

Describe alternatives you've considered
We can re-use data.all sharing workflow and include a new type of sharing, S3 Bucket. To not over-complicate the resulting bucket policy we would not require a prefix-level grained access, granting access grants access to the whole S3 Bucket.
Changes needed:
(see comments below)
Question

How should we manage imported Datasets? When we import a Dataset, we are importing an existing S3 Bucket with its corresponding bucket policy which might be managed by other processes outside data.all. We need to define if data.all a) will ignore these buckets, b) can overwrite the bucket policy (I am not sure how) or c) if it will re-create it and manage it.
How do we define that a dataset is s3-bucket-shareable? We need to clarify what is the user process to categorize a dataset as S3-bucket-shareable.
Can a dataset be shared with LF-tables, Access points-folders and S3-Bucket mechanisms simultaneously? What are the limitations?
How do we handle KMS keys for imported buckets? and in sharing how do we specify CMK keys?

Design decisions and assumptions – We should write ADRs in the development fork

We will first implement the feature on data.all created datasets and then we will deal with imported datasets.
Users can choose between 2 sharing models, granular-share and full-share. Dataset owners decide which model applies to their Dataset and shares will follow the chosen model. In the granular-share model, we share Tables (Glue tables) using Lake Formation and Folders (S3 prefixes) using S3 Access points, this is what is currently implemented. In the full-share model, the whole S3 Bucket is shared using Bucket policies and the whole Glue database is shared using Lake Formation. We will first implement the full S3 Bucket share and as optional the full database share.

I have created a branch to include the S3 Bucket policy changes (step 4 in the changes needed). However it is only for visibility, this branch should be rebased as V1.4.0 includes significant changes in the sharing workflow implementation.

In the feature branch I started drafting the solution. To avoid conflicts with other sharing mechanisms we assume that S3 Bucket sharing will only be used in certain datasets. The sharing mechanism will be decided at dataset creation and can be modified if there are no existing share objects:

I created a new branch from V1.5 so that we start from the latest version and we do not need to rebase. The instructions listed above match the different commits in the branch. In most cases I just added TODOs wherever changes are needed.

Hi @zsaltys I had the same dilemma when designing the feature. We have 2 options, for full-share datasets we either a) index the S3 bucket instead of the tables and folders b) we index tables and folders as we do now and manage the pre-existing shares with messages and UI changes.
I went on with option b) because it adds more visibility on the content of the dataset. Users often search for a table that they know in the catalog in other words I did not want to decrease the discoverability of tables in the Catalog. But this is not set on stone and we are open to changes or new solutions

@dlpzx Thanks for your reply. I reviewed again the task but I don't think we currently explain what will happen in this scenario:

we create a bucket with s3 bucket policy sharing
we create 2 tables X and Y
a user from team A will request to share table X and get it approved
a different user from team A will see table Y in the catalog. They can request to share this table. However this is meaningless. The table would be already shared with them from step 3. This is confusing to the user.

My proposal would be that if we want to keep showing individual tables then we would need to show an indicator on the UI that the table is already shared with the environment and role that is requesting access.

Update on Task G.3 - KMS keys handling and CMK keys - > when implementing imported Dataset
Problem statement
At the moment KMS keys are not imported alongside the S3 Bucket when we import a Dataset. But when we share a dataset through S3 Bucket sharing, we will also need to grant permissions to the requester to the target dataset KMS key.

Give permissions (encrypt/decrypt) in the IAM policy of the requester to the KMS key id
Give permissions in the KMS policy to the requester IAM role

Solution
Data.all release v1.6.0 is focused on security hardening and one of the task is hardening the IAM policies of all roles in data.all. As part of this task it has been necessary to add the KMS key as input when importing a dataset. See https://github.com/awslabs/aws-dataall/pull/515
How does that affect us?

For giving permissions (encrypt/decrypt) in the IAM policy of the requester to the KMS key id we can use the same methods that we would use with a created dataset
Give permissions in the KMS policy - very similar to giving permissions in the S3 Bucket policy - we need to decide on how to manage pre-existing policies that are created outside of data.all. Should we append new policies? What are the permissions that the pivotRole needs?


[BUG] QuickAdd: (ERROR) unable to find insert after line in file.

I'm using the goals/projects template (thanks!) and trying to trial it. However, I have noticed an issue with adding to the Kanban board; specifically when choosing "Quick Add > Goal".
I can add to the "Professional" okay but there rest don't work.
I suspect it has something to do with this line in quick add:
{{VALUE:Professional, Physical, Knowledge, Wealth, Life}}
As "Professional" is first, it works, But "Life" or "Knowledge" return the following error:
QuickAdd: (ERROR) unable to find insert after line in file.
Is it something to do with spaces? Or more likely a conflicting plugin on my system?
To Reproduce
I can only successfully add Professional. The others, no. I have narrowed it down to the above syntax.

OS macOS Monterey
Obsidian v 0.15.9
QuickAdd v 0.5.5

Same issue here.

Actually I just found a simple fix. Get rid of the spaces in the string above so its:
{{VALUE:Professional,Physical,Knowledge,Wealth,Life}}

I also ran into this problem and I understood the reason by looking at the source code, this is because, here the value in the Insert after has to be present in the target file and then the Capture format value is inserted after this string. That's the logic. This is not a bug, it is easy to misinterpret it as inserting after the document.
Source code address: https://github.com/chhoumann/quickadd/blob/e1d4a14cc883d9aed5f123cecf1798ce32b69191/src/formatters/captureChoiceFormatter.ts#L93
So, assuming the target document is
xxxxx
## hello
yyyyy
Then just set the following in Capture

After execution, it will be
xxxxx
## hello
world
yyyyy


Fix(#minor); Breakdown open interest into Long and short open interest in Perp schema

broke down open interest into Long Open interest and short open interest. The granular breakdown of the metrics makes it more useful for research.
Open to discussion, will tag on GMX pull request and SDK pull request.

re added PCV as removing it may cause errors in deployment

re added PCV as removing it may cause errors in deployment

I don't see PCV added in this PR. I don't necessarily think we should add it if it is just to prevent errors. Do perp protocols have PCV and do we want to track it?

re added PCV as removing it may cause errors in deployment

I don't see PCV added in this PR. I don't necessarily think we should add it if it is just to prevent errors. Do perp protocols have PCV and do we want to track it?

they don't i removed it from the schema in this PR. hopefully no issues, but if anything comes up we can make short fixes. @dmelotik feel free to suggest changes, and once done i can merge. Thanks for the input!


YubiHSM device password required when starting Web3Signer

The YubiHSM device password is currently set in the key config file. However, when running Web3Signer using the following:
~/web3signer/build/distributions/web3signer-0.1.1-SNAPSHOT/bin/web3signer --key-store-path=<blah> --logging=TRACE eth2
I'm prompted to reenter the password on the command line. Additionally, the private key is displayed in the trace output. The private key should probably be hidden.

This particular implementation of YubiHSM integration (via yubihsm-shell) has been removed from web3signer. An upcoming PR will integrate YubiHSM via PKCS11 module.


Increase FD_SETSIZE

On Windows, FD_SETSIZE (the maximum number of allowed entries in the fd_set structure) is limited to 64 which is quite low. So when doing a select() with more than 64 you run into trouble.
One could either create groups with FD_SETSIZE entries and call select() multiple times or increase FD_SETSIZE by defining the macro before Winsock2.h is included.
On Linux the default is 1024.
More info: http://msdn.microsoft.com/en-us/library/windows/desktop/ms740141(v=vs.85).aspx

Do you already have an idea? I'm just thinking about that too any ask myself if

calling select() multiple times or
calling select() once and iterating over all possible sockets

is faster.

How can you call select() multiple times? The first call will block the others.

Okay, should think before posting. ;) However it still applies for a zero timeout and/or multiple threads, but that only complicates things.
So probably increasing FD_SETSIZE manually is a good choice then.

Yep :)

I investigated a little bit further: It seems that redefining FD_SETSIZE on Windows may have serious side-effects, it's really not recommended. Therefore we end up with a 64 sockets limit. There're actually two ways I encountered that solve the problem:

Use multiple threads for multiple select()s and use a maximum of 64 sockets per thread for the fd_set.
Use WSAPoll(), however that one has been added in Windows Vista and is therefore not available in XP, which might be a real showstopper.

Seems like wrapping the sockets API isn't enough. SFML Network probably needs another layer of abstraction if you want to keep it simple to use without annoying limitations.

So far nobody complained about the limitation, I guess that 64 sockets is enough for most applications.
Since it's potentially a complicated problem, and I have other priorities for the near future, I'll leave the implementation as it is with its limitations, and wait until more feedback with real use cases.
Thank you very much for your feedback and investigations!

You're welcome, but please at least add an assert() or debug message to Selector::add() that warns the user when a file descriptor with an ID >= FD_SETSIZE is being added (+ documentation). I think debugging such a bug is not so much fun.

please at least add an assert() or debug message to Selector::add() that warns the user when a file descriptor with an ID >= FD_SETSIZE is being added (+ documentation)

Sure.


Adding useragent to cosmos client

Why make this change?
Fixes #1485
Adds user agent to cosmos client.
What is this change?
Adding  user agent to cosmos client.
How was this tested?

[x] Integration Tests
[ ] Unit Tests

    public const string DEFAULT_VERSION = "1.0.0";

nit: this const string DEFAULT_VERSION not being used anywhere in this file any more...

Refers to: src/Cli/Utils.cs:29 in 98bd1f9. [](commit_id = 98bd1f9291f112f945909fd5bad309547dcdf7f6, deletion_comment = False)

removed


NIFI-6057 allow request body to come from an expression

Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[X] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[X] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

[x] Is your initial contribution a single, squashed commit?

For code changes:

[x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[x] Have you written or updated unit tests to verify your changes?
[x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[x] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[x] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[x] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[x] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

Hi @SavtechSolutions - can you elaborate on the use case? do you have a situation where you want to send a request with a body which is not the content of the flow file? can't you just replace the content of the flow file before the InvokeHTTP processor?

Not if you want to retain the flowfile content for further processing. Consider, for example, a case of writing a confluent-encoded record set, if you want to account for the cases when the schema might not have been registered yet. You'd want to issue a POST against the schema registry, with the schema as body, but you'd also want to keep the record set for subsequent writing.

Sounds like a similar use case to PutSQL where we added a property to use instead of the content (NIFI-4522), the user would want to issue a statement based on receiving the flow file, but retain the contents for further downstream processing.
I haven't reviewed this PR, but I mention the above to recommend we handle such things in a consistent manner across components, for best practices and patterns with a friendly user experience.

closing due to inactivity


Formatting Ruby with Prettier

Greetings and thank you for the good work :)
Our team uses prettier to format ruby; I've hacked my local copy of the format all code to add Ruby to the list of prettier languages, though I'm sure there must be a better and more persistent way to accomplish this. Any ideas?

Thanks for the kind words!
So far, format-all has only been able to support one formatter per language. Our formatter of choice for Ruby was rufo which is quite reliable and has good defaults. A moment ago, I finally committed multi-formatter and custom-args support into the multi-formatter branch. With multi-formatter support, we can add any number of alternative formatters for the same language, so adding support for prettier's Ruby plugin is not a problem anymore.
Please check the end of issue #27 and the multi-formatter branch. You should be able to enable Prettier's Ruby support simply by adding "Ruby" to the :languages list in format-all's prettier definition.

Once we've ironed out the problems from the multi-formatter support, I'll push it to MELPA for everyone to use so you don't need to have a customized copy of format-all.

Great stuff! It looks like my timing for wanting this feature is pretty good :) I'll check out the branch later today and give it a try. Thanks!


Suggest to loosen the dependency on nameko

Hi, your project nameko-structlog-experiment(commit id: 64a8cacbbbbdc35eaca786ea6c3c432ac9cd7956) requires "nameko==2.14.1" in its dependency. After analyzing the source code, we found that the following versions of nameko can also be suitable, i.e., nameko 2.6.0, 2.7.0, 2.8.0, 2.8.1, 2.8.2, 2.8.3, 2.8.4, 2.8.5, 2.9.0rc0, 2.9.0, 2.9.0-rc0, 2.9.1rc0, 2.9.1, 2.9.1-rc0, 2.10.0, 2.11.0, 2.12.0, 2.13.0, 2.14.0, 3.0.0rc11, 3.0.0rc10, 3.0.0rc9, 3.0.0rc8, 3.0.0rc7, 3.0.0rc6, 3.0.0rc5, 3.0.0rc4, 3.0.0rc3, 3.0.0rc2, 3.0.0rc1, 3.0.0rc0, 3.0.0-rc11, 3.0.0-rc10, 3.0.0-rc9, 3.0.0-rc8, 3.0.0-rc7, 3.0.0-rc6, 3.0.0-rc5, 3.0.0-rc4, 3.0.0-rc3, 3.0.0-rc2, 3.0.0-rc1, 3.0.0-rc0, since all functions that you directly (2 APIs: nameko.extensions.Entrypoint.decorator, nameko.extensions.DependencyProvider.init) or indirectly (propagate to 0 nameko's internal APIs and 1 outsider APIs) used from the package have not been changed in these versions, thus not affecting your usage.
Therefore, we believe that it is quite safe to loose your dependency on nameko from "nameko==2.14.1" to "nameko>=2.6.0,<=3.0.0-rc11". This will improve the applicability of nameko-structlog-experiment and reduce the possibility of any further dependency conflict with other projects.
May I pull a request to further loosen the dependency on nameko?
By the way, could you please tell us whether such an automatic tool for dependency analysis may be potentially helpful for maintaining dependencies easier during your development?

Nope, that was a one-time experiment with no reason to maintain the dependencies anymore. Please, at least do your research before running an automated bot on Github.


settings: Move LDAP configuration together, in the same order.

Match the order of the variables between default_settings.py and
settings.py, and move the defaults into default_settings.py so
the section does not require any uncommented lines in settings.py if
LDAP is not in use.
Testing plan: Existing tests.

I'd love to remove the import ldap from there, as well.  Does anything prevent moving the AUTH_LDAP_USER_SEARCH = LDAPSearch(...) into defaults?

I'd love to remove the import ldap from there, as well.  Does anything prevent moving the AUTH_LDAP_USER_SEARCH = LDAPSearch(...) into defaults?

@mateuszmandera @andersk FYI.  Structurally, I would love to be able to remove import ldap from settings files.  However, it's a bit tricky -- unfortunately AUTH_LDAP_USER_SEARCH is something one needs to customize depending on how LDAP is setup at the organization; see the examples here: https://zulip.readthedocs.io/en/latest/production/authentication-methods.html#ldap-including-active-directory.

@mateuszmandera @andersk FYI.  Structurally, I would love to be able to remove import ldap from settings files.  However, it's a bit tricky -- unfortunately AUTH_LDAP_USER_SEARCH is something one needs to customize depending on how LDAP is setup at the organization; see the examples here: https://zulip.readthedocs.io/en/latest/production/authentication-methods.html#ldap-including-active-directory.

Is there anything that would prevent moving that line (and the import) into defaults, and making all of them commented-out in the default production settings.py?

Is there anything that would prevent moving that line (and the import) into defaults, and making all of them commented-out in the default production settings.py?

Is there anything that would prevent moving that line (and the import) into defaults, and making all of them commented-out in the default production settings.py?

Is there anything that would prevent moving that line (and the import) into defaults, and making all of them commented-out in the default production settings.py?

Just a ping on this, since there's I think this should be quick to finish and integrate.


Missing 0x80090010

Missing 0x80090010 error code for pin creation...

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

ID: 6b4f9133-887f-17a6-95fc-3712de8a3fa1
Version Independent ID: 09d34ce8-1590-8202-3e70-e6299dadbb65
Content: Windows Hello errors during PIN creation (Windows 10)
Content Source: windows/security/identity-protection/hello-for-business/hello-errors-during-pin-creation.md
Product: w10
Technology: windows
GitHub Login: @DaniHalfin
Microsoft Alias: daniha

As you can see in the Closed part of the Feedback section, there are already 10 similar issues closed with the almost the same explanation.
List of closed issues:

0x801c0541 Not listed #3123 opened 3 weeks ago by WagoL
LOCKSCREEN PIN ERROR #3092 opened 3 weeks ago by crystalh3
0x801c0451 not listed #2941 opened a month ago by jonnydcakes
0x801c004d Not Listed #2900 opened a month ago by GenericUser321
Unlisted: 0x80070490 #2804 opened 2 months ago by SnakeMind
Unlisted error code: 0x80070520 #2685 opened 2 months ago by wireznak
0x801c044f not listed #2684 opened 2 months ago by spankin
0xc0290904 not listed #2676 opened 2 months ago by juanheraclio
0xc0290101 not listed #2421 opened on Jan 5, 2019 by ikonane
0x80070490 not listed #2409 opened on Jan 2, 2019 by demialucard

A couple of reply alternatives for this type of issue (like yours):

DaniHalfin wrote:

For error codes unlisted here, in most cases those are transient error codes being surfaced by other services in the Windows Hello dependency chain.
We are working on something to improve the user experience in that regard, but that will not solve the issues you are experiencing.
If we find a reoccurring error codes that isn't covered here and should be (meaning, in most cases, it is coming from Windows Hello and not other components) we'll make sure to add it to this page.
For any issue you're seeing, please either file a problem through Feedback Hub, or reach out through our various support channels. Both avenues allow us to properly investigate the issue in ways we could never do through a comments section on a GitHub issue.
The feedback section in the topic is generally meant for feedback on the content, and we can't really use it for in-depth troubleshooting.
We thank you for taking the time to reach out, but we also want you to have the best time to resolution of the issue, and going through this feedback channel won't get us there.

Joyce Y. wrote:

Thank you for submitting feedback.
I think the best way forward is if you can open a service ticket so this can get resolved ASAP. Based on outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for Windows 10 products: https://support.microsoft.com/en-us/hub/4338813/windows-help?os=windows-10
If you don't mind please keep us posted here on the resolution and I really want to get this information you are discovering back into the docs.

From my own point of view, I recommend checking out the other 10 issue tickets to see if any of the other users have posted helpful comments, like "broken file, replaced, fixed" or "timeout problem" or "user interrupted".

Ok, thank you for the answer, however still think that Microsoft should provide documentation, in mean of list of all possible codes (that are in programmed into software) and provide at least some explanation for the start. That way, you will lower the number for support ticket requests, and educate Microsoft 1st level support and other IT Pro and be more open. Putting info on feedback hub is just community with no reply very often or long wait for more information on specific issue.

Fair point. I can only hope for progress in documentation production for this section
and reference one of the important parts of Dani Halfin's post:

We are working on something to improve the user experience in that regard, but that will not solve the issues you are experiencing.
If we find a reoccurring error codes that isn't covered here and should be (meaning, in most cases, it is coming from Windows Hello and not other components) we'll make sure to add it to this page.


Porunhub and Xhamster video download didn'nt work.

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like this: [x])
Use the Preview tab to see what your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2018.06.18. If it's not, read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2018.06.18

Before submitting an issue make sure you have:

[x] At least skimmed through the README, most notably the FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones
[x] Checked that provided video/audio/playlist URLs (if any) are alive and playable in a browser

What is the purpose of your issue?

[x] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add the -v flag to your command line you run youtube-dl with (youtube-dl -v <your command line>), copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):
pornhub:

[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'-v', u'https://jp.pornhub.com/view_video.php?viewkey=ph59b65deb6746b']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2018.06.18
[debug] Python version 2.7.12 (CPython) - Darwin-17.6.0-x86_64-i386-64bit
[debug] exe versions: none
[debug] Proxy map: {}
[PornHub] ph59b65deb6746b: Downloading webpage
[PornHub] ph59b65deb6746b: Downloading webpage
WARNING: unable to extract uploader; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
WARNING: unable to extract view count; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
WARNING: unable to extract like count; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
WARNING: unable to extract dislike count; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
WARNING: unable to extract comment count; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
[debug] Default format spec: best/bestvideo+bestaudio
Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/runpy.py", line 174, in _run_module_as_main
    "__main__", fname, loader, pkg_name)
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/runpy.py", line 72, in _run_code
    exec code in run_globals
  File "/usr/local/bin/youtube-dl/__main__.py", line 19, in <module>
  File "/usr/local/bin/youtube-dl/youtube_dl/__init__.py", line 472, in main
  File "/usr/local/bin/youtube-dl/youtube_dl/__init__.py", line 462, in _real_main
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 2001, in download
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 803, in extract_info
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 857, in process_ie_result
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 1635, in process_video_result
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 1700, in process_info
TypeError: object of type 'NoneType' has no len()

...
<end of log>

xhamster:

[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'-v', u'https://jp.xhamster.com/videos/sdt-bondage-chie-satonaka-persona-4-2382334']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2018.06.18
[debug] Python version 2.7.12 (CPython) - Darwin-17.6.0-x86_64-i386-64bit
[debug] exe versions: none
[debug] Proxy map: {}
[XHamster] 2382334: Downloading webpage
ERROR: Unable to download webpage: <urlopen error [SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure (_ssl.c:590)> (caused by URLError(SSLError(1, u'[SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure (_ssl.c:590)'),))
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 579, in _request_webpage
    return self._downloader.urlopen(url_or_request)
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 2211, in urlopen
    return self._opener.open(req, timeout=self._socket_timeout)
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 429, in open
    response = self._open(req, data)
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 447, in _open
    '_open', req)
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 407, in _call_chain
    result = func(*args)
  File "/usr/local/bin/youtube-dl/youtube_dl/utils.py", line 1101, in https_open
    req, **kwargs)
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 1198, in do_open
    raise URLError(err)

If the purpose of this issue is a site support request please provide all kinds of example URLs support for which should be included (replace following example URLs by yours):

Single video: https://jp.pornhub.com/view_video.php?viewkey=ph599b1e7f5d5f8
Single video: https://jp.xhamster.com/videos/sdt-bondage-chie-satonaka-persona-4-2382334

Note that youtube-dl does not support sites dedicated to copyright infringement. In order for site support request to be accepted all provided example URLs should not violate any copyrights.

Description of your issue, suggested solution and other information
On June 18th, the above error will appear after probably upgrading to ver.2018.06.18.

I want to install older version.

Is this due to my computer environment?

Is openssl or equivalent updated. Looks like ssl is failing to handshake properly aka ssl cerificate validation has failed.
What`s your mac enviroment ?

Yeah, try it with a more recent version of Python, best a recent Python 3.

@siddht4 My Mac environment : macOS High Sierra,  LibreSSL 2.2.7 and Python 2.7.12.
I installed OpenSSL 1.0.2o and I made it the default,but the results were the same.
Thanks for your advice.

@Hrxn Mac has Python 2.7.12 pre-installed.
I installed Python 3.6.5, andI defaulted Phython 3 using Pyenv, but the results did not change.
Thanks for your advice.

@siddht4
@Hrxn
All went well. It is bingo.
I am sorry for you. The reason for not seeing improvement was that I had forgotten to restart the terminal after completing all the procedures.
I was saved. Thank you.

@noname774    If your problem is fixed then you can close this issue

yes, I will.


[ktx] Update to 4.1.0-rc3.

This also fixes a compilation error with the previous port version (4.1.0-rc2) when using feature ktx[tools].

linux build error seems to be about missing libtool
Is this a known issue on the CI?

linux build error seems to be about missing libtool Is this a known issue on the CI?

FAILED: libktx.a
: && /mnt/vcpkg-ci/downloads/tools/cmake-3.24.0-linux/cmake-3.24.0-linux-x86_64/bin/cmake -E rm -f libktx.a && /usr/bin/ar qc libktx.a  CMakeFiles/ktx.dir/lib/basis_transcode.cpp.o CMakeFiles/ktx.dir/lib/basisu/transcoder/basisu_transcoder.cpp.o CMakeFiles/ktx.dir/lib/checkheader.c.o CMakeFiles/ktx.dir/lib/dfdutils/createdfd.c.o CMakeFiles/ktx.dir/lib/dfdutils/colourspaces.c.o CMakeFiles/ktx.dir/lib/dfdutils/interpretdfd.c.o CMakeFiles/ktx.dir/lib/dfdutils/printdfd.c.o CMakeFiles/ktx.dir/lib/dfdutils/queries.c.o CMakeFiles/ktx.dir/lib/dfdutils/vk2dfd.c.o CMakeFiles/ktx.dir/lib/etcdec.cxx.o CMakeFiles/ktx.dir/lib/etcunpack.cxx.o CMakeFiles/ktx.dir/lib/filestream.c.o CMakeFiles/ktx.dir/lib/hashlist.c.o CMakeFiles/ktx.dir/lib/info.c.o CMakeFiles/ktx.dir/lib/memstream.c.o CMakeFiles/ktx.dir/lib/strings.c.o CMakeFiles/ktx.dir/lib/swap.c.o CMakeFiles/ktx.dir/lib/texture.c.o CMakeFiles/ktx.dir/lib/texture2.c.o CMakeFiles/ktx.dir/lib/vkformat_check.c.o CMakeFiles/ktx.dir/lib/vkformat_str.c.o CMakeFiles/ktx.dir/lib/gl_funcs.c.o CMakeFiles/ktx.dir/lib/glloader.c.o CMakeFiles/ktx.dir/lib/texture1.c.o CMakeFiles/ktx.dir/lib/basis_encode.cpp.o CMakeFiles/ktx.dir/lib/astc_encode.cpp.o CMakeFiles/ktx.dir/lib/basisu/encoder/basisu_backend.cpp.o CMakeFiles/ktx.dir/lib/basisu/encoder/basisu_basis_file.cpp.o CMakeFiles/ktx.dir/lib/basisu/encoder/basisu_bc7enc.cpp.o CMakeFiles/ktx.dir/lib/basisu/encoder/basisu_comp.cpp.o CMakeFiles/ktx.dir/lib/basisu/encoder/basisu_enc.cpp.o CMakeFiles/ktx.dir/lib/basisu/encoder/basisu_etc.cpp.o CMakeFiles/ktx.dir/lib/basisu/encoder/basisu_frontend.cpp.o CMakeFiles/ktx.dir/lib/basisu/encoder/basisu_gpu_texture.cpp.o CMakeFiles/ktx.dir/lib/basisu/encoder/basisu_kernels_sse.cpp.o CMakeFiles/ktx.dir/lib/basisu/encoder/basisu_opencl.cpp.o CMakeFiles/ktx.dir/lib/basisu/encoder/basisu_pvrtc1_4.cpp.o CMakeFiles/ktx.dir/lib/basisu/encoder/basisu_resample_filters.cpp.o CMakeFiles/ktx.dir/lib/basisu/encoder/basisu_resampler.cpp.o CMakeFiles/ktx.dir/lib/basisu/encoder/basisu_ssim.cpp.o CMakeFiles/ktx.dir/lib/basisu/encoder/basisu_uastc_enc.cpp.o CMakeFiles/ktx.dir/lib/writer1.c.o CMakeFiles/ktx.dir/lib/writer2.c.o && /usr/bin/ranlib libktx.a && cd /mnt/vcpkg-ci/buildtrees/ktx/x64-linux-dbg && libtool -static -o /mnt/vcpkg-ci/buildtrees/ktx/x64-linux-dbg/libktx.a /mnt/vcpkg-ci/buildtrees/ktx/x64-linux-dbg/libktx.a /mnt/vcpkg-ci/buildtrees/ktx/x64-linux-dbg/lib/astc-encoder/Source/libastcenc-avx2-static.a
/bin/sh: 1: libtool: not found
ninja: build stopped: subcommand failed.

From the error log, It seems not ci issue, I will rerun the ci and look the result

linux build error seems to be about missing libtool

It is quite unusual that CMake projects use libtool. And ktx doesn't apply the same steps for Windows.
But libtool is installed in CI:
https://github.com/microsoft/vcpkg/blob/86eb754bce1ac2087cbf8351a11015a9df7ca8dd/scripts/azure-pipelines/linux/provision-image.sh#L19

But libtool is installed in CI:

Wait, this package brings only libtoolize. And autotools packages create a local tool. That's why the are not affected.
The global /usr/bin/libtool is in Ubuntu package libtoolize which is not installed in CI. CC @BillyONeal.

VM update queued with this added. Will keep you posted.

VM update landed. Pushed merge with master to pick that up.

All features are tested successfully in the following triplet:

x64-windows
x64-windows-static

@maoliver-amd , Please sign in the CLA.

@maoliver-amd , Please sign in the CLA.

I have signed the CLA as I have contributed previously. Im not sure why the license/cla check is no longer working as my last PR was fine.

@microsoft-github-policy-service agree [company="AMD"]

@microsoft-github-policy-service agree company="AMD"

Thanks!


Upgrade GraalVM

Problem Description
Upgrade GraalVM to 20.1.1 or newer.

Check if 20.2.0 is backward compatible with 20.1.x release. If so, use 20.2, otherwise use 20.1.x latest.

Found some issues with 20.2.0 and our quickstart-mp on Mac. Someone else should double check this.


If compute <-> pageserver connection is lost, reconnect

Steps to reproduce
-- Create a table that's larger than shared_buffers
postgres=# show shared_buffers ;
 shared_buffers
----------------
 1MB
(1 row)

postgres=# create table foo as select g from generate_series(1, 1000000) g;
SELECT 1000000

-- Run a query on it
postgres=# select count(*) from foo;
  count
---------
 1000000
(1 row)

-- In another terminal, stop and restart pageserver:
/*
$ ./target/debug/neon_local pageserver stop
Stopping pageserver with pid 2439701 gracefully...
pageserver stopped
$ ./target/debug/neon_local pageserver start
Starting pageserver at '<IP_ADDRESS>:64000' in '.neon'
.
pageserver started, pid: 2439914
*/

-- Then run the query again:
postgres=# select count(*) from foo;
ERROR:  [NEON_SMGR] end of COPY

-- When you try it again, it works:
postgres=# select count(*) from foo;
  count
---------
 1000000
(1 row)

Expected result
No ERROR. It should reconnect automatically if the connection is lost, and just work.

Hi @hlinnaka are you on this or do you mind if i tackle it?

Thanks @knizhnik! That was actually harder than i thought, initially i was thinking about playing around WL_SOCKET_CLOSED to reconnect... Anyway, i will keep an eye on your PR!

This hasn't been fixed, can still reproduce. Reopening.

Works now, closing.


Updated alignment of footer for responsive

#128

@ChetanSingh14 ,
the footer is still white.why?

@Yash-Ainapure raising another pr for it ?
bcoz of sync fork and git pull

@Yash-Ainapure raising another pr for it ! bcoz of sync fork and git pull

ok

@Yash-Ainapure have u merged first alignment pr ? bcoz i have to remove code and then add !

@Yash-Ainapure have u merged first alignment pr ? bcoz i have to remove code and then add !

Its not merged

@Yash-Ainapure please review now !

@Yash-Ainapure please review it

@Yash-Ainapure sir please put label on this issue

@Yash-Ainapure

@Yash-Ainapure Thank you


new playbook for the existing MDTI solution

1 folder that include azuredeploy.json and a readme file
Required items, please complete.
Change(s):

See guidance below

Reason for Change(s):

See guidance below

Version Updated:

Required only for Detections/Analytic Rule templates
See guidance below

Testing Completed:

See guidance below

Checked that the validations are passing and have addressed any issues that are present:

See guidance below

Guidance <- remove section before submitting

Before submitting this PR please ensure that you have read the following sections and filled out the changes, reason for change and testing complete sections:
Thank you for your contribution to the Microsoft Sentinel Github repo.

Details of the code changes in your submitted PR.  Providing descriptions for pull requests ensures there is context to changes being made and greatly enhances the code review process.  Providing associated Issues that this resolves also easily connects the reason.

Change(s):

Updated syntax for XYZ.yaml

Reason for Change(s):

New schema used for XYZ.yaml
Resolves ISSUE #1234

Version updated:

Yes
Detections/Analytic Rule templates are required to have the version updated

The code should have been tested in a Microsoft Sentinel environment that does not have any custom parsers, functions or tables, so that you validate no incorrect syntax and execution functions properly.  If your submission requires a custom parser or function, it must be submitted with the PR.

Testing Completed:

Yes/No/Need Help

Note: If updating a detection, you must update the version field.

Before the submission has been made, please look at running the KQL and Yaml Validation Checks locally.
https://github.com/Azure/Azure-Sentinel#run-kql-validation-locally

Checked that the validations are passing and have addressed any issues that are present:

Yes/No/Need Help

Note: Let us know if you have tried fixing the validation error and need help.

References:

Guidance for Detection checks
General contribution guidance
PR validation troubleshooting

Hi @manishkumar1991 @rahul0216,
Could you please provide your feedback on this.
Thanks

Kindly consider standard, Rename the file from AzureDeploy.json to azuredeploy.json .

@manishkumar1991 please review my chanags

Hi @manishkumar1991, please review changes. Thanks

Hi @manishkumar1991, please review changes. Thanks

Reviewing changes

Kindly consider standard, Rename the file from AzureDeploy.json to azuredeploy.json .

Hello @Yaniv-Shasha
Please check on this comment as well

@Yaniv-Shasha , We are seeing that this playbook requires MDTI-base playbook to be installed as a pre requisite .
But MDTI-base playbook, creating a new key vault resource, which is not allowed, as currently our solution packaging doesn't support it , so requesting you to change it and try to use the existing key vault resources .
Kindly refer to the playbook provided below.
https://github.com/Azure/Azure-Sentinel/blob/master/Solutions/ThreatXCloud/Playbooks/ThreatXPlaybooks/ThreatX-BlockIP-URL/azuredeploy.json

Hi @Yaniv-Shasha, please check comment from @manishkumar1991. Thanks


[BUG] - Card shadow not working in latest Safari on Mac

Describe the bug
The default variant shadow is not working on the latest Safari browser on Mac

everything seems fine on Chrome

Your Example Website or App
No response
Steps to Reproduce the Bug or Issue
Go on the NextUI documentation https://nextui.org/docs/components/card
Expected behavior
The card shadown should be visible
Screenshots or Videos
No response
Operating System Version
macOS
Browser
Safari

+1
I has the same bug on Safari 16.0

This bug is shown on Safari mobile too.

Still happening, the cards look really bad in safari...
In Brave, the cards have a greyish color while on chrome they are white (light theme)
Also the switch button looks on in Brave with the dark theme.

Hey guys sorry for the delay please upgrade to V2 and test this again.
All components have been written from scratch
https://nextui.org/docs/components/card


Df-339: Modify JUnit test for Df-298 Building a static graphql query

This PR resolves #339.

Create an object from the test utility's "wellboreOpenQuery" resource that is comparable to the one created by the code-under-test. As with the tested code, dynamically check how to build the correct query fields within this object.
Get the code-under-test's open query object, and compare it to the one just created using the test utility's resource. Perform a deep comparison of the JSON values.

Thank you, Randy. I really appreciate your confidence in me! It encourages
me to be my best!!
Thank you,
Theresa Stewart
281.723.7108
On Tue, Mar 12, 2019 at 4:36 PM Randy<EMAIL_ADDRESS>wrote:

@randypitcherii approved this pull request.
Excellent commit, Theresa. Clear, clean code and impeccable commenting.
It's really encouraging to see code that's so professionally done.
Please feel empowered to take ownership of this repo. If anything you see
doesn't look right or any approach concerns you, I want you to change it to
be better or bring it up to the team so we can discuss. We can really
benefit from your eye now that you're gaining some confidence with the code
base.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/hashmapinc/Drillflow/pull/342#pullrequestreview-213663743,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Atzvze1UvTbnxsMR2qZbCvYwFwHwsiTaks5vWB3ygaJpZM4brqhM
.


missing FindVTK.cmake on drake001 (mac)

[ 78%] Performing configure step for 'ddapp'
loading initial cache file /tmp/drake-distro/director/distro/pods/drake-distro/pod-build/tmp/ddapp-cache.cmake
CMake Error at src/vtk/CMakeLists.txt:1 (find_package):
  By not providing "FindVTK.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "VTK", but
  CMake did not find one.

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

    VTKConfig.cmake
    vtk-config.cmake

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

-- Configuring incomplete, errors occurred!

drake001% cmake --version
cmake version 3.2.3

looks like vtk might not have been installed properly.  (remember I started it at the conference, then shut my laptop? :)  will reopen if it's still a problem after this.

Im having identical issues on a linux build
[ 78%] Performing configure step for 'ddapp'
loading initial cache file /home/naveenoid/Workspace/Drake/drake-distro/externals/director/distro/pods/drake-distro/pod-build/tmp/ddapp-cache.cmake
CMake Error at /usr/share/cmake-2.8/Modules/FindVTK.cmake:135 (message):
VTK not found.  Set the VTK_DIR cmake cache entry to the directory
containing VTKConfig.cmake.  This is either the root of the build tree, or
PREFIX/lib/vtk for an installation.  For VTK 4.0, this is the location of
UseVTK.cmake.  This is either the root of the build tree or
PREFIX/include/vtk for an installation.
Call Stack (most recent call first):
src/vtk/CMakeLists.txt:1 (find_package)
Am I missing something fundamental in my make options? I used the default set and then I switched to using  WITH_ALL_PUBLIC_EXTERNALS as ON

Can you confirm you have vtk installed?  Try these:
sudo apt-get install libqt4-dev libvtk5-dev libvtk5-qt4-dev python-vtk python-numpy
If those are installed and you still get the error message, can you confirm this file exists:
/usr/lib/vtk-5.8/VTKConfig.cmake
And what OS version do you have?

I can confirm that file exists (VTKConfig.cmake). My OS is a Linux Mint 17 (kernel : 3.13.0-24-generic x86_64 (64 bit)). I had manually installed vtk6 after the first failure and your instruction corrected that. However I have another build error now :
5%] Performing build step for 'cdd_project'
Making all in lib-src
Making all in src
Making all in lib-src-gmp
libtool: compile:  gcc -DPACKAGE_NAME="" -DPACKAGE_TARNAME="" -DPACKAGE_VERSION="" -DPACKAGE_STRING="" -DPACKAGE_BUGREPORT="" -DPACKAGE="cddlib" -DVERSION="0.94" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=".libs/" -DSTDC_HEADERS=1 -I. -I/usr/local/include -DGMPRATIONAL -g -O2 -MT cddcore.lo -MD -MP -MF .deps/cddcore.Tpo -c cddcore.c  -fPIC -DPIC -o .libs/cddcore.o
In file included from cdd.h:18:0,
from cddcore.c:14:
cddmp.h:31:18: fatal error: gmp.h: No such file or directory
#include "gmp.h"
^
FYI from related issue discussions, I think this info is also relevant, my Cmake version is <IP_ADDRESS>


Bug in interaction of OPTIONAL and SET OF

EdgeDB Version: 1.0-alpha.4+dev.92.g20b0bd7f
OS Version: Linux

Steps to Reproduce:
victor> CREATE TYPE Foo;
OK: CREATE
victor> SELECT (<str>Foo.id) ?? (<str>count(Foo));
{}

The expected result is {'0'}, since we expect the count of an empty set be called.

Another example is SELECT (<str>Foo.id ?= <str>count(Foo));, which returns {} instead of {false}.
There seems to be some trickiness, here, though, since we do want those sides to be correlated. If we add a num field to Foo, we want SELECT (Foo.num ?= count(Foo)); to only be true for objects where num = 1, I think.

since we do want those sides to be correlated. If we add a num field to Foo, we want SELECT (Foo.num ?= count(Foo)); to only be true for objects where num = 1,

That's correct.

A related issue, albeit in the other direction, that probably needs to be tackled together with this:
sully> SELECT (Foo ?= Foo, Foo);
{(true, Object {id: {}})}


feat(release-please): add default token input option

set the ${{ secrets.GITHUB_TOKEN }} as the default input of token.
The ${{ github.token }} can access to it.
Close #211

@googlebot I signed it!

It might be worth adding an example of using a custom token instead of GITHUB_TOKEN as it's still a valid input.

@pragmaticivan I tried to add an example usage for the personal access token. 😃

Hey @bcoe, I have been using this feature (use default token for action) in my actions for a long time. e.g., yi-Xu-0100/repo-list-generator and yi-Xu-0100/traffic-to-badge. What else do I need to do to merge this PR?

@yi-Xu-0100 I'm slightly surprised by this feature, because it means that an upstream action can get the GITHUB_TOKEN, without it explicitly being set as inputs.
Is there a step where an action needs to opt in? this is interesting from a security perspective for actions.

@bcoe
github.token used as the default input value of the token in the official actions(checkout, stale, github-script) is also very common. I think that the reasons are as follows:

The permission of secret.GITHUB_TOKEN is very limitation, and it is restricted to be used in workflows, and does not have the permission to obtain special data in the repository or the data in other repositories of the owner. (Reference permissions-for-the-github_token)
There are steps that must use token in the current action. Token is a required item, and secret.GITHUB_TOKEN with the least authority is used as the default input, which may reduce repeated configuration.
The github.token can be used to obtain the same permissions as secret.GITHUB_TOKEN. (Reference github-context)

@yi-Xu-0100 @pragmaticivan if we want to keep the section about a custom token, I might just make it a short blurb, about the fact that you can use an alternate token, perhaps pointing out the fork option.
I don't think we need a fully fleshed out example, folks will understand they can just pass an alternate token.

@bcoe I tried to reduce the example section, hoping it could be better. 😀

@bcoe When I test for my own repository, I find the token of secret.GITHUB_TOKEN can be used for both the fork and private repository.
At first, I test the fork repository, and it does well. See in https://github.com/yi-xu-test-organization/test-repo-1/pull/1 (the input value of fork is true because of the boolean input issue)
Then I set the origin repository (https://github.com/yi-Xu-0100/test-repo) was setting to be private to test the action and also got the success result.
So I delete the example section and only keep the description of the token.  😅


perf(p2p): do not remarshal envelope message within broadcast

Closes #4615
This avoids multiple marshal of the Envelope Message when broadcasting.
PR checklist

[X] Tests written/updated
[ ] Changelog entry added in .changelog (we use unclog to manage our changelog)
[ ] Updated relevant documentation (docs/ or spec/) and code comments

Could you add a changelog entry? .changelog/unreleased/improvements/...?

@melekes changelog entry has been added. One test is failing now but it may come from a flaky test as nothing has changed except the new entry.


mining success ，but get_mint_info not info

There could be many scenarios that could lead to such a problem, and it could be a result of some of the following:

It is possible that the mint transaction constructed because of the network problem at that time was not successfully broadcast to the blockchain's block-producing node, so it resulted in the transaction not being successfully packaged into the block of the blockchain.
Or the mint transaction did not pass the difficulty check of the blockchain node because it was at the threshold of difficulty adjustment, and so on.

Really appreciate with you for this issue, Thank a lot.


Change the port number in ContainerPort

The ContainerPort  should be 8080 for todo-api and 80 for todo-ui as defined on docker-compose.yaml.

thanks for fixing this! 🎉


use React to sortable, after the data was lost

Try dev-branch, perhaps the problem has been solved;
Use the search, maybe already have an answer;
If not found, create example on jsbin.com (draft) and describe the problem.


Parallel version of runiface()

A parallel version of the runiface() function could possibly be implemented relatively straightforwardly. One would want to utilize that subprocess.Popen() launches processes in the background and would allow us to launch multiple processes simultaneously.
By constructing two lists: one for the DREAMSettings objects yet to be run, and one list for the processes currently executing. In a loop we would make sure that the latter list always contains a set number of elements (as long as their are DREAMSettings remaining in the queue). Within the loop we would also call p.communicate() on each of the executing processes with a short timeout. Once a process finishes, we remove it from the list of executing processes and replaces it with a new.

Hi, I started working on this issue and created first implementation (https://github.com/Pinfar/DREAM/tree/parallel-runiface). I have a little problem with creating a test case for parallel processing. Do you maybe have an idea about experiment that takes very little code to set up and verify? I'd like to create about 10-20 similar experiments and run them in parallel.

Probably the most convenient example is examples/runaway/basic.py. You'll just want to replace the last line (ds.save(...)) with a call to runiface() (needs to be imported as from DREAM import runiface).

Ok, I created test here: https://github.com/Pinfar/DREAM/blob/f254f28aee55c227980ad0c51d15530ea05261e4/tests/physics/runiface_parallel/runiface_parallel.py . But now I am still not checking if the results I receive are not corrupted in some way. Maybe I can only run experiments via regular runiface and compare results with the parallel one? Which parameters should I compare?

Sorry for the long silence! I've been moving from Switzerland to Sweden and have had some very busy weeks :P I should hopefully be more responsive from now on.
Nicely done! This looks pretty much like I imagined. For the last pieces of the test, comparing to a single run with runiface() could be a good idea. I would compare either do.eqsys.n_re[-1,0] or ds.other.fluid.runawayRate[-1,0]. The latter is a numerical derivative of the former so checking just one should be fine.

Hey, thanks for your response. I'll implement checks after the weekend and let you know. I also need to implement timeout parameter support. Do you think that this should be timeout for one operation or whole process?

Great, thanks! The timeout parameter is something we use as a an upper limit on simulations to tell when a simulation is non-convergent. So it should be applied to individual simulations/processes (so, for each DREAMTask, I guess you'll want to accumulate the timeout given to self.p.communicate() and add a check for when the accumulated timeout for that task exceeds the user-imposed timeout).

Ok, I added implementation of timeout and comparison between serial and parallel runiface results. I am thinking about changing one more thing. Now, If any of executed experiments timeouts, then whole runiface execution throws an error. Maybe we can return other object instead of DREAMOutput?

Yes, that's a good idea! Generally, I think the application of this would be to run massive scans, and then if one simulation fails, it would be better to keep the others running and just eventually return an error for the failed simulation.
One idea could be to return a DREAMException (or perhaps a new type of exception, derived from DREAMException) instead of a DREAMOutput object. The exception object could contain the DREAMSettings object which resulted in the failure as well as maybe an error code and whatever was read from stdout/stderr of the failing process?

Hey, I pushed new changes. Have a look and If you don't have any additional ideas, I will create Pull Request.

I've had quick look, and spontaneously I think everything is there (great job!). If you do the pull request it will be easier for to check in detail though.

Ok, I created https://github.com/chalmersplasmatheory/DREAM/pull/222

Merged to master in #222

If you have any other issues to solve, in this or other project, just let me know :)

Thanks! Your help is really appreciated! :) I might have another idea in mind which you could probably help with (a testing framework for full simulations), but I think I need to think through the structure a bit first. I'll try to open an issue soon to gather ideas, and then your welcome to join and contribute


pls help reveiwe and merge

done with the C and the python version

Hi @Mubarak1A.
Thank you for implementing the calculator in both C and Python 😀.
Truly appreciated.
Your pull request will be merged, but please, take note that I shall be removing the pycache directory. That is the executable for the Python implementation.
Thank you.


[Bug] Repo won't refresh to progress to Step 1

Summary
After cloning the repo, the action to progress to Step 1 doesn't happen, even after several refreshes.
How to reproduce

Go to review-pull-requests
Click on "Start Course"
Wait some time
No refresh, page is stuck at Welcome.

Issue fixed after deleting repo and re-cloning.


TorXakis language design principles

What are the language design principles?
Why is a channel definition a first class primitive?
Why not model? And refer in connect definition to the channels of the model?

related to #336 and #466


Improve interaction_in_progress reliability

Throws interaction_in_progress error at time of attempting to set the temporary cache value to minimize the gap between checking/setting cache and reduce occurence of race conditions
Moves this step to the top of interactive APIs so that events are not emitted when this is thrown
Fixes a recent regression that made the synchronous part of acquireTokenPopup asynchronous

Codecov Report

Merging #4460 (bda7b1f) into dev (4c7418a) will increase coverage by 0.00%.
The diff coverage is 100.00%.

Flag
Coverage Δ

*Carryforward flag

msal-angular
96.39% <ø> (ø)

Carriedforward from dc27ea9

msal-browser
87.50% <100.00%> (-0.01%)
:arrow_down:
Carriedforward from dc27ea9

msal-common
85.37% <ø> (+0.04%)
:arrow_up:
Carriedforward from dc27ea9

msal-core
82.65% <ø> (ø)

Carriedforward from dc27ea9

msal-node
82.97% <ø> (ø)

Carriedforward from dc27ea9

msal-node-extensions
76.03% <ø> (ø)

Carriedforward from dc27ea9

msal-react
92.70% <ø> (ø)

*This pull request uses carry forward flags. Click here to find out more.

Impacted Files
Coverage Δ

...rc/interaction_client/StandardInteractionClient.ts
98.87% <ø> (+1.68%)
:arrow_up:

...al-browser/src/interaction_handler/PopupHandler.ts
84.61% <ø> (ø)

...browser/src/interaction_handler/RedirectHandler.ts
90.00% <ø> (ø)

lib/msal-browser/src/app/ClientApplication.ts
96.29% <100.00%> (ø)

lib/msal-browser/src/cache/BrowserCacheManager.ts
93.03% <100.00%> (ø)

...msal-browser/src/interaction_client/PopupClient.ts
100.00% <100.00%> (ø)

...l-browser/src/interaction_client/RedirectClient.ts
100.00% <100.00%> (ø)

lib/msal-browser/src/utils/PopupUtils.ts
92.50% <100.00%> (ø)

...msal-common/src/request/RequestParameterBuilder.ts
92.56% <0.00%> (-0.13%)
:arrow_down:

... and 9 more


Update redisson proxy manager to support redisson 3.21.0

The synchronous command executor has been removed from Redisson in version 3.21.0.

Good, I will look tomorrow.

@vladimir-bukhtoyarov cool, I've already rebased the changes on the 8.3 branch

Released with version 8.3.0

Had to find out about the new group id because 8.3.0 isn't available on com.github.vladimir-bukhtoyarov; would it be an idea to release a final version update on the old group id which then deprecates the code and suggests changing the group?
This would really help people using dependabot to keep there dependencies up to date.

GroupId is "com.bucket4j". It was changed about 1 year ago. New groupId is mentioned on github project page.

I understand.
But if someone doesn't visit the GitHub page they won't know. And gradle or maven doesn't know about this name change either, so it was just something to consider.


Better name for "N"

The pointer masking extension defines the number of masked bits as N.  In this extension and elsewhere we have parameters with descriptive names like VBITS, XLEN, ASIDLEN, IALIGN, SEW, etc.  I think that N should be renamed to something that is more descriptive like MBITS, MASKBITS, MLEN, MASKLEN, etc.
Other (better) names that people sent to me on or off the list: NONABITS (non-address bits), HWALEN (HWASan), PMBITS, PMLEN.
For what it's worth, I think that *LEN is more RISC-V-like than *BITS.  (XLEN, FLEN, VLEN, ELEN, ILEN, ASIDLEN, VMIDLEN, etc.)

I would also add "PMASK" as a suggested prefix, as "PM" is overloaded with other interpretations (e.g. power management).
As for "BITS" vs "LEN", I don't see a clear winner. "LEN" is more popular, but the most closely related parameters (VBITS, NVBITS) use "BITS".

I picked PMLEN and updated the spec in 92a88a2. The reason I decided against *BITS is that we consistently use LEN for scalars and BITS for ranges. "The PMBITS+1st bit from the top" would therefore be contradictory. Feedback welcome!

That makes sense to me!

Sounds good.


locale change causes .zcomdump* being deleted

if the locale changes, e.g. from en_US.UTF-8 to C.UTF-8, e.g. ssh from archlinux and then ssh from alpine to the same machine, then https://github.com/zimfw/completion/blob/8e20c7b81f4b20cd1907d475716d7093be95d3ef/init.zsh#L24 will return 1, and the .zcomdump* got deleted, and then https://github.com/zimfw/completion/blob/8e20c7b81f4b20cd1907d475716d7093be95d3ef/init.zsh#L31 got run, which will be slow.
after https://github.com/zimfw/completion/blob/8e20c7b81f4b20cd1907d475716d7093be95d3ef/init.zsh#L23
the debug (set -x) shows
# log for [[ ${zold_dat} == ${znew_dat} ]]

[[ $'5.9\C-<EMAIL_ADDRESS>== 5.9/home/user/.zim/modules/zsh-completions/src/_afew... ]]

# the log is huge, so i use ... to replace the rest of all

as you can see the difference is \C-@ in there...
note: why locale changes sometimes via ssh? because 1) ssh is set to send locale and accept locale 2) alpine uses musl which uses C.UTF-8 and other OSes uses something else other than C.UTF-8

Hi. Thanks for reporting this.
I've tried exporting LANG to different values in my machine and in an archlinux docker container and the .dat file didn't change. Can you try applying the patch below?
diff --git a/init.zsh b/init.zsh
index d7eb682..3ae58ae 100644
--- a/init.zsh
+++ b/init.zsh
@@ -20,15 +20,15 @@
   local -r znew_dat=${ZSH_VERSION}$'\0'${(pj:\0:)zcomps}$'\0'${(pj:\0:)zstats}
   if [[ -e ${zdumpfile}.dat ]]; then
     zmodload -F zsh/system b:sysread
-    sysread -s ${#znew_dat} zold_dat <${zdumpfile}.dat
     [[ ${zold_dat} == ${znew_dat} ]]; zdump_dat=${?}
+    LC_CTYPE=C sysread -s ${#znew_dat} zold_dat <${zdumpfile}.dat
   fi
   if (( zdump_dat )) command rm -f ${zdumpfile}(|.dat|.zwc(|.old))(N)

   autoload -Uz compinit && compinit -C -d ${zdumpfile}

   if [[ ! ${zdumpfile}.dat -nt ${zdumpfile} ]]; then
-    >! ${zdumpfile}.dat <<<${znew_dat}
+    LC_CTYPE=C >! ${zdumpfile}.dat <<<${znew_dat}
   fi
   # Compile the completion dumpfile; significant speedup
   if [[ ! ${zdumpfile}.zwc -nt ${zdumpfile} ]] zcompile ${zdumpfile}

Not even sure these commands would recognize the LC_CTYPE=C prefix.  :- )

I've updated the patch above. Writing was not working. Can you please try again with the updated patch?

The \C-@ is equivalent to the $'\0' (null) character:
% xxd .zcompdump.dat
00000000: 352e 3900 2f68 6f6d 652f 7573 6572 2f2e  5.9./home/user/.
00000010: 7a69 6d2f 6d6f 6475 6c65 732f 7a73 682d  zim/modules/zsh-
00000020: 636f 6d70 6c65 7469 6f6e 732f 7372 632f  completions/src/
00000030: 5f61 6665 7700                           _afew.

I still didn't setup a ssh machine to try to reproduce the issue. Great to know you found a workaround and are very close to the solution. I wonder if the issue is when the file is read, when it's written, something else, or both...


Add basic Dockerfile for multistage build

Multstage build of rewrite code. Docker-compose file is in-work for submission.

Thank you! Sorry for the delay. I've noticed that meanwhile there was another contribution adding support for Docker: https://github.com/solusipse/fiche/pull/75. Could you please take a look at it and let me know which one, in your opinion, should I merge in?

No problem, the changes could be merged in to #75. My changes are mostly to using the Docker build stage pattern and that can be added to any options. If @M0nsieurChat is open to it, I can merge my changes in to his PR. He's got the documentation done and the added docker-compose file with nginx support so that feels like a better fit.

Looking over #75, it would fit right in, my multistage build would handle building the binary in a cleanroom environment, and then copy over the binary to the final stage. This leads to a lighter image and the final image doesn't have the added collateral that the build stage imports.

Hello,
No problem for me as well !
Regards,

Great! I know staged builds requires a more recent Docker version, but I'm pretty confident that it's mainstream now, even Travis has the required version in their build structure. I'm more of a CircleCI and Drone user, they are covered as well.

Closing for a new PR with updated changes on a new PR.

I was going to just add my changes to the existing PR, but looking that over, I think it may be over complicated for a docker container. It's set up for docker-compose and orchestration and while that is nice, just a simple docker image with the existing default port 9999 exposed and the default ./code directory is fine. The users can map their desired ports to 9999 and volume mount via their preferred methods to ./code for the storage directory. No need for an additional nginx configuration for just a base image, that can be added but a vast majority of users aren't going to need a load balancer or orchestration manager for just use of Fiche.

The aim was to provide a quick mean of testing / deploying fiche with all the dependencies (webserver included) as this is what docker does best.
I think both of our visions can be provided in a future PR with :

a Dockerfile + README explaining how to run just fiche by itself with or without host mounts (as you suggested)
a docker-compose + README explaining how to run a ready-to-use fiche+nginx on your local machine or remote server

The fiche docker image being used by the docker-compose needs to be the same as the one generated by the Dockerfile.

Thanks for the comments, I agree with everything you said. For now, I'm running the following Dockerfile

RUN apk update && apk add \
    curl \
    gcc \
    make \
    musl-dev

WORKDIR /usr/src/fiche

COPY * ./

RUN make -f Makefile clean \
    && make -f Makefile \
    && make -f Makefile install

FROM alpine:3.7

COPY --from=build /usr/local/bin/fiche /usr/local/bin

RUN apk add --no-cache tini

RUN addgroup -g 901 fiche \
    && adduser -G fiche -D -u 901 fiche \
    && mkdir /code \
    && chown fiche:fiche /code

USER fiche

EXPOSE 9999

VOLUME ["/data"]

ENTRYPOINT ["/sbin/tini", "--", "/usr/local/bin/fiche", "-l", "/dev/stdout"]

Invocation is:
docker run -d --rm -p 9999:9999 -v fiche:/data --name fiche <image> -S -s 8 -d example.com
That runs the fiche server as a daemon, maps the external port of your choice to 9999 internally and then your choice of mounts, in this case a named volume, to /data as exported. If you chose to bind mount, there is the caveat of requiring the mount point to be owned by UID 901, as the original version just used the fiche user, and that could end up being undetermined at container runtime.
I've chosen to use tini as the init system so it reaps the process, I was finding that when running as daemon the fiche process was not hearing the HUP and not terminating nicely. I also appended the flag to redirect logfiles to /dev/stdout so that you can run docker logs -f fiche and see the logs. Makes it easy to manage the logfiles with your choice of orchestration management.
Any other flags can be passed on the command line and they are honoured. I didn't think it would require an entrypoint script, everything is nicely handled.

@dschaper @M0nsieurChat many thanks for your work guys! Should we merge in https://github.com/solusipse/fiche/pull/75 or are you planning to open a new pull request? This time I'll be more responsive, I promise. And sorry for the delay, again!


Fixed 'add new event' view height not being calculated correctly

The 'addNewDurationMins' property for the 'add new event' height calculation is being cast to CGFloat too late, resulting in incorrect height for fractional duration hours.

You are correct, I've merged it.
Thanks for helping me to improve this project.


Handling Errors

I have my model configured to backup multiple servers in one go round.  Only problem is if one fails, the entire model fails.  Ive tried using begin rescue blocks, still no luck.  Is there another way of doing this within the model?

@txssseal would PR #676 fix your problem?

@txssseal version 4.1.11 has been released to fix this issue.

@tombruijn works like a charm, thank you!


[cherry-pick][branch-3.2][Feature] support snappy stream compression (#30604)

Fixes #issue
What type of PR is this:

[ ] BugFix
[x] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.2
[ ] 3.1
[ ] 3.0
[ ] 2.5

[FE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

[BE Incremental Coverage Report]
:disappointed: fail : 22 / 37 (59.46%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
src/util/compression/stream_compression.cpp
11
25
44.00%
[428, 429, 430, 434, 435, 436, 437, 438, 439, 443, 444, 445, 446, 447]

:large_blue_circle:
src/exec/hdfs_scanner_text.cpp
5
6
83.33%
[388]

:large_blue_circle:
src/util/coding.h
4
4
100.00%
[]

:large_blue_circle:
src/io/compressed_input_stream.cpp
2
2
100.00%
[]


Fix duplicate tag names

Iterating through the resources with versioning enabled causes duplicate tag names because the resource people and people_versions both have the same item_title.
This PR fixes that by ignoring disabled_resources and resources that end in _versions.

@otibsa do you have any more incoming PRs? If not I'm releasing 0.0.5 this week.

Nope, nothing lined up at the moment. :)


New version: MartiCliment.UniGetUI.Pre-Release version 3.1.2-beta4

Pull request has been created with WinGet Releaser v2 :rocket:
Microsoft Reviewers: Open in CodeFlow

@wingetbot run

Hi @marticliment,
Does this package require VCRedist as a dependency?

This package installs and launches normally in a Windows 10 VM.

@stephengillie, isn't winget supposed to install VCRedist it if I declare it as a dependency?

It is. It might be an artifact of the scan step, when all EXEs are launched. But that should be after the dependency installation. I'm not sure what happened to cause the error.