Keeping crop aspect ratio constant even when resizing the crop frame

Assume we give a Constrain value 16*9. How can we keep that ratio all the time till editing complete? In current version, if we resize the cropping frame, the selected aspect ratio is changing. I need to keep ratio value constant once we select it till we done editing.

I'm interested in this as well. Or disabling resize of the cropping frame altogether.

In the openEditor method, have you tried this:
controller.keepingCropAspectRatio = YES;     controller.cropAspectRatio = 16.0f / 9.0f;

Inside viewDidAppear for PECropViewController, insert:
self.cropView.cropAspectRatio = 16.0f / 9.0f;
self.keepingCropAspectRatio = YES;

I set aspect ratio to self.cropView.cropAspectRatio = 3.2 but getting change when applying zoom in/zoom out move.


Pathmuncher Doesn't Work with Basic Test with New Character

Importing JSON ID: 179798
logger.js:53 pathmuncher | WARN > Unable to find parsed feature match for granted feature Shield Block. This might not be an issue, but might indicate feature duplication. {document: {…}, parent: {…}}
log @ logger.js:53
warn @ logger.js:79
#createGrantedItem @ Pathmuncher.js:612
#addGrantedRules @ Pathmuncher.js:927
await in #addGrantedRules (async)
#addGrantedItems @ Pathmuncher.js:1039
#addGrantedItems @ Pathmuncher.js:1033
await in #addGrantedItems (async)
#processGenericCompendiumLookup @ Pathmuncher.js:479
await in #processGenericCompendiumLookup (async)
processCharacter @ Pathmuncher.js:2030
await in processCharacter (async)
_updateObject @ PathmuncherImporter.js:104
await in _updateObject (async)
_onSubmit @ foundry.js:5916
commons.js:6946 Foundry VTT | Created Actor with id [B1FB59P5uPAYlTjL]
commons.js:6946 Foundry VTT | Created 3 Item documents with ids: [ZTd4pjcORKKsD27Y,TjJZjxDoDZ5eQSUp,VLFoaFLw7upnQxVt] in parent Actor [B1FB59P5uPAYlTjL]
commons.js:6946 Foundry VTT | Deleted Actor with id [B1FB59P5uPAYlTjL]
foundry.js:5919 TypeError: Cannot convert undefined or null to object
at Function.entries ()
at #generateEquipmentItems (Pathmuncher.js:1336:1)
at async #processEquipment (Pathmuncher.js:1845:1)
at async Pathmuncher.processCharacter (Pathmuncher.js:2043:1)
at async PathmuncherImporter._updateObject (PathmuncherImporter.js:104:1)
at async PathmuncherImporter._onSubmit (foundry.js:5916:7)

The bug report template asks for a number of things which you haven't included which I will need to reproduce and understand the bug:
Environment:

Browser [e.g. chrome]
Foundry Version [e.g. 10.288]
Pathfinder System Version [e.g 2.0.3]
Module Version [e.g 3.1.21]
Does this behaviour occur with other modules disabled: Yes/No (Find The Culprit module can help with this)

Additional context
Add any other context about the problem here.

In Pathbuilder please got to Export -> "Share Copy of Character" and provide the link.
Details of any errors in the browser console (press F12).

It might also be that this character was exported with an older version of Pathbuilder and the JSON is not longer accepted by Pathbuilder. Please try exporting the JSON again.


3.deep_model/train_model.py - Request for Documentation

Thank you for sharing this project! I am interested in utilizing the framework you have created, but I would appreciate some more information about the expected input format for train_model.py. Specifically:

Since the dataset used in your project cannot be shared, could you provide guidance on how to create a custom dataset?
What is the expected folder structure for the dataset?
What format should the mmWave data and Ground Truth be in?

This information would be incredibly helpful for those of us who wish to adapt the framework for our own datasets. It would make the framework much more accessible to the research community!

Related to Issue #14, Issue #15, and Issue #17


Halt Request Lifecycle

Issue: https://github.com/amber-crystal/amber/issues/156
Requirements

If redirect_to or render is called in before_action, the action
should not run, but it does run currently. redirect_to or render
in action is fine since we can simply return. However, if they
can cancel the action in before_action, before_action can be
more useful and easy to do lots of things like authentication.

Exits request action lifecycle by returning false from anywhere
in the controller including redirect_to, before/after filters and
actions.

As soon the request Lifecycle is halted it will begin to unfold
the response.

Alternatively you can use return halt(status_code, content) to
halt the request, this method sets status_code and content for the
response, and returns false.

Description of the Change

Introduces halt! controller method which cancels a request lifecycle
redirect_to now halts the request

Alternate Designs

class FakeController < Amber::Controller::Base
  before_action do
    only :halt_action { halt!(900) }
  end

  def halt_action
    raise "Should not reach this action"
    ""
  end

end

class FakeRedirectController < Amber::Controller::Base

  def redirect_action
    redirect_to "/"
    ""
  end
end

Benefits
Avoids extra processing when calling halt!

@elorest updated the halt! method to write to headers also added content.to_s


Add RMF deep link navigation

Task/Issue URL: https://app.asana.com/0/488551667048375/1206596674293772/f
Description
Steps to test this PR
Feature 1

[ ]
[ ]

UI changes

Before
After

!(Upload before screenshot)
(Upload after screenshot)

#4393  👈
develop

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

Join @joshliebe and the rest of your teammates on  Graphite


Large Types IRGen Pass: Fix runtime crash for large enums

radar rdar://problem/32094543
Fixes a runtime crash caused by the new large loadable types pass: when encountering a large enum, for which we change the switch-case into their address variant, unchecked_take_enum_data_addr can be destructive to the enum. as such, we need to create a copy of the enum and perform the unchecked_take_enum_data_addr on said copy

@swift-ci Please smoke test

@swift-ci Please smoke test

@swift-ci Please smoke test


Remove useless dev menu

In previous versions i had to use one click to change dev panel position. Now i must use two annoying  clicks. Why?

Hi @littleguga - Looks like this is an issue with Chrome, not our docs. Please file it at https://crbug.com


Update TF Lite Android example

update to work in actual Android Studio

Thanks for PR. What Android devices has this been tested on?

@achowdhery Samsung S8

FWIW I just had to do the same changes for the TFLite Android example to compile. Tested on macOS 10.13.6 and Android Studio 3.0

Nagging Reviewer @shashishekhar: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 29 days with no activity and the awaiting review label has been applied.


Adapter for minispade

Is it possible to use minispade with karma? Is there any specific adapter supported?

Closing due to inactivity. Please feel free to open a new issue or submit a PR if you still need help. Thanks.


Math Magicians: setup

💯 Achievements

Make sure that there are no linter errors.
Used correct Gitflow.
Documented my project README in a professional way.
Set up full react project with linters and run it smoothly.

Thank you @rloterh for the optional suggestions. Given that the create react app creates these files for us including README and license, I saw a tutorial that recommended initializing an empty repo. I'll work on them before merging the branch.


Options for profile status bar item

Personally, I'd love to see:

An option to hide the status bar item or text for default profiles (I only want to know when I am in another profile)
An option to use an icon instead of text for the profile

@daviddossett May I know if we have an icon for this already?

Changed the profiles icon to following (same as the one @misolori used in his previous screenshots)

Closing this as I think there is no further action needed here.


Open RDLC File in Visual Studio

When I open the RDLC from Visual Code, the Visual Studio opens the file and shows the layout.
But, I am missing the possibility to build the file, to check the layout against the dataset.
In NAV 2018, the visual studio was opened differently:
There where several files created, and the visual studio was opened with 3 files:
First a sln-file, then a xsd-file, then the rdlc file.
Is there a possibility to add this behaviour to visual studio, or create it in the background automatically?
Without a possibility to validate a layout, developing gets very frustrating.
the al compilier itself does not check the layout.
Or is there any other possibility to check the layout before publishing and running?

This issue is a question. Please submit your questions on business central community  or on BC development yammer groups.


Click on div inside draggable div on Mobile Not Working

I have a horizontal dragging menu that when on mobile, none of the links in the draggable div are clickable. I see there is a staticClick event but the documentation around how to use it is sparse. Is there no way to just say staticClick:true , and then static clicks work normally? My links all do different things and call different JS functions, so how can staticClick allow this?

I recommend you try the back handle technique so that inner elements are still interactable, but the element itself is still draggable.

Hi ,
i have a problem which is similar to this in ios devices . i have a Bootstrap modal which is draggable but onclick events are not working for inside elements like close button . i have tried above " back handle technique ". but found no results can you help how can i allow onclick events inside draggable model?


changed the documentation of the website to enhance it

You didn't follow the PR template ??

im sorry, i'll edit it and make a pr again


CONTRIBUTING.md: Introduce doc.

This is a base document for contribution guidelines that can be
extended as needed with information specific to this repo.

Build SUCCESS, see build http://<IP_ADDRESS>:8080/job/dev-tools/241/


Provide spreadsheet in flattened form - to follow from the one for submission

Hey @amnonkhen
@Wkt8 has already supplied a metadata spreadsheet for the first Visium dataset.
Would it be possible to create a flattened version for this file?
https://docs.google.com/spreadsheets/d/1fBm89rJvvfHODg1u3vtmnRth4VftGqSi/edit?usp=sharing&ouid=114069941208994528669&rtpof=true&sd=true
(FYI - this is a real spreadsheet for a real project)
cc @Wkt8 @ipediez if you guys need to advise on how we can show the linking with the new metadata entities (what you consider makes sense)
Let me know if questions. Ideally I would need this by end of today as a first version @amnonkhen  (sorry!)
Gabs

Hey @amnonkhen - spreadsheet is above. Imaging information is in the last 4 tabs. They more or less link the imaged specimens back to a specimen, to a protocol and a file. @Wkt8 can provide more info :) to your other questions.

@gabsie @Wkt8 please review
https://app.zenhub.com/files/299258791/9330eb69-8da3-4883-af08-02ee6921e839/download

Amnon to schedule a mtg with Wei.

Gave some feedback to amnon (coordinates file not there, some of the analysis_protocol fields are showing information that isn't 100% accurate). Will have another catchup later!

Amnon to try and find some capacity for this.

v0.4 - image files and analylsis files, hidden empty columns
(https://app.zenhub.com/files/299258791/07201c29-3d3f-4ddf-bd08-c66177112a72/download)

@gabs needs to email (people) regarding this.


Clear SSH server keys when creating new clusters

This change executes ssh-keygen -R for the public IP addresses of newly-created
VMs.  This prevents SSH from complaining when an IP address is recycled.
Resolves #32

This change is

This has been annoying me recently. Thanks!

Review status: 0 of 1 files reviewed at latest revision, 1 unresolved discussion.

main.go, line 271 at r1 (raw file):

				// Run ssh-keygen -R serially on each new VM in case an IP address has been recycled
				for _, v := range c.VMs {
					cmd := exec.Command("ssh-keygen", "-R", v.PublicIP)

Can this be done in one command by putting all of the IP addresses on the command line?

Comments from Reviewable

Review status: 0 of 1 files reviewed at latest revision, 1 unresolved discussion.

main.go, line 271 at r1 (raw file):
Previously, petermattis (Peter Mattis) wrote…
Can this be done in one command by putting all of the IP addresses on the command line?

Unfortunately, no.  ssh-keygen (at least on OS X) only accepts a single hostname per invocation.

Comments from Reviewable


[bug]: invokeai-rocm container doesn't support gpus

Is there an existing issue for this problem?

[X] I have searched the existing issues

Operating system
Linux
GPU vendor
AMD (ROCm)
GPU model
RX 7900 XTX, RX 7700S
GPU VRAM
26GB, 8GB
Version number
invokeai-rocm
Browser
firefox
Python dependencies
No response
What happened
I am trying to use the container version like this:
--device /dev/kfd --device /dev/dri --volume ./:/invokeai -p 9090:9090 --name invokeai ghcr.io/invoke-ai/invokeai:main-rocm

However it doesn't seem to detect either of my amd GPUs and falls back to CPU. It also says bitsandbytes doesn't have GPU support.
The installed version of bitsandbytes was compiled without GPU support. 8-bit optimizers, 8-bit multiplication, and GPU quantization are unavailable.
[2024-10-02 05:54:19,891]::[InvokeAI]::INFO --> Patchmatch initialized
[2024-10-02 05:54:20,552]::[InvokeAI]::INFO --> Using torch device: CPU

ollama works fine with rocm I am not sure why this doesn't or how I can get it working?
What you expected to happen
I expect the container to start utilizing rocm and detecting the gpu
How to reproduce the problem
No response
Additional context
No response
Discord username
No response

Bare-metal affected too
Using Installer with rocm option - RX 6700 XT GPU
Works fine on < 5.0.2, but starting > 5.1 getting error
The installed version of bitsandbytes was compiled without GPU support. 8-bit optimizers, 8-bit multiplication, and GPU quantization are unavailable.
Made systemd service
[Unit]
Description=InvokeAI

[Service]
ExecStart=/home/user/.local/invokeai/.venv/bin/invokeai-web
Environment="HSA_OVERRIDE_GFX_VERSION=10.3.0"
Environment="PYTORCH_HIP_ALLOC_CONF=garbage_collection_threshold:0.95,max_split_size_mb:512"
Environment="INVOKEAI_ROOT=/home/user/.local/invokeai"
Restart=on-failure
RestartSec=5s

[Install]
WantedBy=default.target

Same result on bare metal.
5.1.1 doesn't use/detect the ROCm device. An in-place install of 5.0.2 restores AMD support.

None of [version]-rocm containers work for me, even before version 5.0.2. Im using podman with the proper arguments (I know podman is not directly supported, but I have ollama running via this same configuration and I also run the bare metal installer via a rootless distrobox container and that has worked fine).
Here are my arguments.
Image=ghcr.io/invoke-ai/invokeai:main-rocm
ContainerName=invokeai
AutoUpdate=registry
Environment=INVOKEAI_ROOT=/var/lib/invokeai
PublishPort=9091:9090
Volume=/var/home/user/.local/share/invokeai:/var/lib/invokeai
SecurityLabelDisable=true
AddDevice=/dev/dri
AddDevice=/dev/kfd

Using the 5.1.1 bare metal installer also defaults to using the CPU. But using the 5.0.2 bare metal installer (again under a rootless distrobox container) detects my AMD GPU and works as intended.

This is caused by an incorrect ROCm version, see #7146. I'm not familiar with docker but I assume changing the URL in line 41 of the dockerfile to "https://download.pytorch.org/whl/rocm6.1" should fix the issue.


Update to unbound 1.19.0

https://github.com/NLnetLabs/unbound/releases/tag/release-1.19.0

Done!


Pull request with type [UPDATE] for user [jonasatgit] and object type [Script] - titled [Test-ConfigMgrTlsConfiguration]

Automated pull request from the Endpoint Configuration Manager Community hub.

This is the update for the failed pull request: https://github.com/microsoft/configmgr-hub/pull/80


Problem with hosted zones

Prerequisites

[x] I am running the latest version. (up upgrade)
[x] I searched to see if the issue already exists.
[x] I inspected the verbose debug output with the -v, --verbose flag.

Description
At the moment with the following config two hosted zone are created and i think i can only add one name servers group.

Steps to Reproduce
{
	"name": "balance-saldotuc-com",
	"profile": "saldotuc",
	"dns": {
    "saldotuc.com": [
      {
        "name": "saldotuc.com",
        "type": "MX",
        "value": [
          "1 ASPMX.L.GOOGLE.COM",
          "5 ALT1.ASPMX.L.GOOGLE.COM",
          "5 ALT2.ASPMX.L.GOOGLE.COM",
          "10 ALT3.ASPMX.L.GOOGLE.COM",
          "10 ALT4.ASPMX.L.GOOGLE.COM"
        ]
      }
    ]
  },
  "environment": {
    "NODE_ENV": "production"
  },
  "hooks": {
    "build": "make"
  },
	"lambda": {
		"memory": 128
  },
  "proxy": {
    "command": "./node-v8.9.1-linux-x64/bin/node index.js"
  },
  "stages": {
    "production": {
      "domain": "balance.saldotuc.com"
    }
  }
}

hmm yea looks like a bug, thanks for reporting I'll check this out today hopefully

I'll do some more QA before the next release but this should be fine now

Thank you. This release is included in the pro version ?

yep! I just pushed 0.1.11 pro with the fix


Feature: Math Extensions

Math extensions for #39 :

Addition
Subtraction
Addition Tests
Subtraction Tests

Reasons provided.

Sounds good, thanks!


[terraform-ibm-event-streams] Expose provider visibility in the DA

The IBM provider supports passing a value for visibility. The default is "public" which means public endpoint is always used for api calls.
We should probably expose this value as a variable, and possibly default it to "private", especially since there may be CBR rules in place that only allow services to be talked to via the private network.

https://github.com/terraform-ibm-modules/terraform-ibm-event-streams/pull/351


Update hybrid testing blog post

I want to add clarifications that I mentioned in the GSA talk.

@lpgoldstein
I made updates to the intro (page 1) and Step 3 (page 5). New text is in track changes. Do you have time to review this sprint?
https://doimspp.sharepoint.com/:w:/r/sites/NRRD/Shared Documents/General/Blog/In Progress/onrr.gov accessibility testing - blog post.docx?d=w0bfbd123ecbf42cca8e032ab2ad06608&csf=1&web=1&e=a7oJuY

@cthomasONRR I like your additions. I also like you used screen reader user instead of assistive tech user. It's clearer.

@Maroyafaied I'm ready to make these updates... can I go in dev and modify the text? We can discuss next week. I believe Shannon made some blog updates when they were in dev before so I don't think it needs to be removed.

These updates are now in dev: https://dev-blog-nrrd.app.cloud.gov/four-part-hybrid-testing/


hide-on-XXX-only and .prefix icons

Currently hiding prefix icons on small screen does not affect input sizes.
What you think about, should input grows when prefix icon is hidden?

I think it is very easy to have the developer code this themselves, whereas having the framework code in small edge cases is less clean.


Don't Merge! Regression pull request test

Docs Build status updates of commit af712da:
:clock10: Pending: waiting for processors (7 builds ahead of you)
:warning: Docs Build is busy, currently there are 7 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit af712da:
:clock10: Full build: the average full build time is 6 min(s) 2 sec(s), this is based on the last 542 build(s) for this repository.

Docs Build status updates of commit af712da:
:warning: Validation status: warnings

File
Status
Preview URL
Details
Dependent Files

docs-ref-conceptual/TestingPullRequest.md
:warning:Warning
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)
Details

docs-ref-conceptual/TestingPullRequest.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: content_type. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: content_type. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: content_type. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
[Warning] the value invalid_type is undefined for metadata content_type
[Warning] the value invalid_type is undefined for metadata content_type
[Warning] the value invalid_type is undefined for metadata content_type
Line 7: [Warning] Invalid file link:(~/nonexisted1.md).
Line 7: [Warning] Invalid file link:(~/nonexisted1.md).
Line 7: [Warning] Invalid file link:(~/nonexisted1.md).
Line 8: [Warning] Invalid file link:(~/nonexisted2.md).
Line 8: [Warning] Invalid file link:(~/nonexisted2.md).
Line 8: [Warning] Invalid file link:(~/nonexisted2.md).
Line 9: [Warning] Invalid file link:(~/nonexisted3.md).
Line 9: [Warning] Invalid file link:(~/nonexisted3.md).
Line 9: [Warning] Invalid file link:(~/nonexisted3.md).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


unfrobulate

Seems like this is going to be a new reality. Rather than reopening #5419 I'm going to open a new ticket for this week's unfrobulations.

This morning's first frobulation: I can't upload files because Elasticsearch is not running ... but it is.

$ ps|grep elastic
76087 ttys005    0:00.00 grep elastic
75822 ttys009    0:14.15 /usr/bin/java -Xms256m -Xmx1g -Xss256k -Djava.awt.headless=true -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError -Delasticsearch -Des.foreground=yes -Des.path.home=/Users/whit537/src/elasticsearch-1.2.1 -cp :/Users/whit537/src/elasticsearch-1.2.1/lib/elasticsearch-1.2.1.jar:/Users/whit537/src/elasticsearch-1.2.1/lib/*:/Users/whit537/src/elasticsearch-1.2.1/lib/sigar/* org.elasticsearch.bootstrap.Elasticsearch
$ curl http://localhost:7777
<title>404: Not Found</title>404: Not Found$

Alright, fixed itself. 😳


Is the Kill command sending hard Termination?

I tryed the tool, booting up my docker-compose stack was no problem.
However the only logical way to stop my stack seems to be "kill", which sounds a bit hard.
When terminating a Docker-Compose setup, you can sigterm it one to allow him shutdown or sigterm him twice to force hard shutdown.
What is this tool using?
Also why not add the start/stop commands in the case you cont want to build the stack with "up"?

Hi Florian,
when you kill a project there is no custom signal passed to the remote Docker API, so according to the official documentation "SIGKILL is assumed and the call will wait for the container to exit."
I agree with you: start/stop commands could be really useful and I will add them as actions in the next release.

I usualy let my Containers run in active mode with plain "docker-compose up".
I assume if you press Ctrl+C it will first try to stop them.

Start/Stop should fix this issue. :)
Looking forward to it.


UnixFs Stat Command Returns Invalid Data

When using stat, it does not return the correct dagSize values for non-empty directories. It appears that this line is using the byteLength of the UnixFS data in the directory block. This causes stat commands on non-empty directories to return an invalid value that does not match the Kubo value.

unixfs entry should have a metadata block that contains sizes of their children, so we should be able to use what is in that metadata directly, or sum sizes of children's metadata

I think the API has some rough edges here.
Of note:

fileSize/localFileSize doesn't apply to directories
dagSize/localDagSize this is impossible to calculate for directories unless all blocks are present in the block store, since the size of a directory is not stored in the root DAG node for that directory - you have to traverse the DAG, calculating block sizes as you go which can be expensive
blocks In the equivalent Kubo API call, it seems to treat this as the number of Links in the root dag-pb node that resolve to files (sub dirs are ignored).  If the directory is large enough to become sharded, this number is the number of sub-shards, so it's not terribly useful - Helia just returns 1 for directories since there's only ever one root block, though there could be plenty of sub-shards in a sharded directory, again not terribly useful

Perhaps we should break up the UnixFSStats interface?
// these involve traversing a DAG so are expensive to calculate
interface UnixFSDAGStats {
  // if all blocks for this DAG are in the blockstore
  complete: boolean

  // how many blocks make up the DAG - directories, sub-shards, files, leaf nodes, etc
  // - only accurate if `complete` is `true`
  blocks: bigint

  // how many bytes of the DAG are in the blockstore
  localDagSize: bigint

  // how many bytes of the file/directory are in the blockstore
  localSize: bigint
}

// a file is a DAG-PB node with one or more linked nodes that contain file data or links to other nodes
interface UnixFSFileStats {
  type: 'file'
  cid: CID

  // how big the DAG that holds the file is in bytes (e.g. the sum of all dag-link Tsize fields plus the
  // serialized size of the root node)
  dagSize: bigint

  // UnixFS metadata (has mtime/mode/block count/file size)
  unixfs: UnixFS
}

interface ExtendedUnixFSFileStats extends UnixFSFileStats, UnixFSDAGStats {
}

// a directory is a DAG-PB node with links to other DAG-PB or raw nodes
// if the unixfs type is `directory`, each linked node is a file, a raw block or a directory
// if the type is `hamt-sharded-directory`, each linked node is a file, a raw block or a directory
interface UnixFSDirectoryStats {
  type: 'directory'
  cid: CID

  // UnixFS metadata (has mtime/mode)
  unixfs: UnixFS
}

// these involve traversing the DAG so are expensive to calculate
interface ExtendedUnixFSDirectoryStats extends UnixFSDirectoryStats, UnixFSDAGStats {
  // the size of all files in the directory including in subdirectories
  size: bigint
}

// a raw entry is a bare block that contains file data
interface UnixFSRawStats {
  type: 'raw'
  cid: CID

  // how big the block is
  size: bigint
}

type UnixFSStats = UnixFSFileStats | UnixFSDirectoryStats | UnixFSRawStats
type ExtendedUnixFSStats = ExtendedUnixFSFileStats | ExtendedUnixFSDirectoryStats | UnixFSRawStats

The @helia/unixfs interface would end up changing to something like:
interface StatOptions {
  offline?: boolean
  // ...same as currently
}

interface ExtendedStatOptions {
  extended: true // not sure if this is the right name
  // ...same as currently
}

fs.stat(cid, options?: StatOptions): Promise<UnixFSStats>
fs.stat(cid, options?: ExtendedStatOptions): Promise<ExtendedUnixFSStats>


ARROW-10247: [C++][Dataset] Support writing datasets partitioned on dictionary columns

Enables usage of dictionary columns as partition columns on write.
Additionally resolves some partition-related follow ups from #8894 (@pitrou):

raise an error status instead of aborting for overflowing maximum group count
handle dictionary index types other than int32
don't build an unused null bitmap in CountsToOffsets
improve docstrings for MakeGroupings, ApplyGroupings

non apache CI: https://github.com/bkietz/arrow/runs/1664709650

non apache CI: https://github.com/bkietz/arrow/runs/1664709650

non apache CI: https://github.com/bkietz/arrow/runs/1682804367

non apache CI: https://github.com/bkietz/arrow/runs/1682804367

@jorisvandenbossche @pitrou addressed comments, PTAL

@jorisvandenbossche @pitrou addressed comments, PTAL

@bkietz Thanks for the updates! I added one more test with the example from the JIRA, so to also have a test that ensures writing a table also works without specifying the dictionaries.
Is it possible to specify the max_partitions option from python?

@bkietz Thanks for the updates! I added one more test with the example from the JIRA, so to also have a test that ensures writing a table also works without specifying the dictionaries.
Is it possible to specify the max_partitions option from python?

While it's not a blocker, I admit I don't understand why it's necessary to pass dictionary values, and in which case (only for writing?).

While it's not a blocker, I admit I don't understand why it's necessary to pass dictionary values, and in which case (only for writing?).

@pitrou The dictionaries are a feature inspired by ParquetDataset: it's useful for each partition expression to contain the dictionary of all unique values that field could take. They are only required when parsing paths. When constructing a Partitioning from a factory (inferring fields from a vector of paths) the dictionaries are assembled automatically. However if the Partitioning is being directly constructed then the dictionaries must be explicitly specified.
@jorisvandenbossche I'll add a binding for max_partitions to python

@pitrou The dictionaries are a feature inspired by ParquetDataset: it's useful for each partition expression to contain the dictionary of all unique values that field could take. They are only required when parsing paths. When constructing a Partitioning from a factory (inferring fields from a vector of paths) the dictionaries are assembled automatically. However if the Partitioning is being directly constructed then the dictionaries must be explicitly specified.
@jorisvandenbossche I'll add a binding for max_partitions to python

Since both @pitrou and I got a bit confused about this dictionaries, we should maybe try to further clarify the documentation around it. A more explicit test could maybe also help (although I didn't check the C++ tests).
(can be a follow-up, since I think needs to get in for the release?)
As I understand it now:

It's only needed in ds.dataset(..) when passing a schema, i.e. which creates an actual Partitioning object, and not a PartitioningFactory (which will infer the schema (and the dictionary values) from the file paths)
In addition, it's only needed to specify it when reading, and not when writing with a Partitioning (so can create and use a schema-based Partitioning object without specifying the dictionaries).
This is the "only required when parsing paths" (the docstring says "or an error will be raised in parsing"), since we don't need to parse paths when writing. But for a user the "parsing paths" == "reading" (in practice) might not necessarily be clear.

This behaviour of requiring explicit dictionaries when reading a dataset with a Partitioning object with a schema including dictionary fields already exists in 1.0 and 2.0 (only without any way to get around the error "No dictionary provided for dictionary field", except by letting the partitioning be discovered instead of specifying a schema). So that's certainly fine for 3.0.0 as well.
But, I am personally still wondering if we can't allow this for reading as well to have those dictionaries unspecified but discovered, even when specifying an explicit schema (eg it allows to have mixed dictionary / non-dictionary partition fields). This actually also worked in pyarrow 0.17.0 (and I added a test about that in the PR fixing it (https://github.com/apache/arrow/pull/6641#issuecomment-600746259), but that got apparently lost in a rebase ;)), but I suppose this was changed after ensuring that the dictionary-typed partition fields "know" the full dictionary of all possible values the dataset (https://github.com/apache/arrow/pull/7536#issuecomment-649500017).
I can open a JIRA about this to discuss further.

Since both @pitrou and I got a bit confused about this dictionaries, we should maybe try to further clarify the documentation around it. A more explicit test could maybe also help (although I didn't check the C++ tests).
(can be a follow-up, since I think needs to get in for the release?)
As I understand it now:

It's only needed in ds.dataset(..) when passing a schema, i.e. which creates an actual Partitioning object, and not a PartitioningFactory (which will infer the schema (and the dictionary values) from the file paths)
In addition, it's only needed to specify it when reading, and not when writing with a Partitioning (so can create and use a schema-based Partitioning object without specifying the dictionaries).
This is the "only required when parsing paths" (the docstring says "or an error will be raised in parsing"), since we don't need to parse paths when writing. But for a user the "parsing paths" == "reading" (in practice) might not necessarily be clear.

This behaviour of requiring explicit dictionaries when reading a dataset with a Partitioning object with a schema including dictionary fields already exists in 1.0 and 2.0 (only without any way to get around the error "No dictionary provided for dictionary field", except by letting the partitioning be discovered instead of specifying a schema). So that's certainly fine for 3.0.0 as well.
But, I am personally still wondering if we can't allow this for reading as well to have those dictionaries unspecified but discovered, even when specifying an explicit schema (eg it allows to have mixed dictionary / non-dictionary partition fields). This actually also worked in pyarrow 0.17.0 (and I added a test about that in the PR fixing it (https://github.com/apache/arrow/pull/6641#issuecomment-600746259), but that got apparently lost in a rebase ;)), but I suppose this was changed after ensuring that the dictionary-typed partition fields "know" the full dictionary of all possible values the dataset (https://github.com/apache/arrow/pull/7536#issuecomment-649500017).
I can open a JIRA about this to discuss further.

I opened https://issues.apache.org/jira/browse/ARROW-11260 for the "require dictionaries or not" question

I opened https://issues.apache.org/jira/browse/ARROW-11260 for the "require dictionaries or not" question


Unable to access the pods after setting up NAT

I used the terraform NAT example to setup a NAT gateway for all egress from my GKE cluster. I tried the following ssh command that was given in the readme and it works:
gcloud compute ssh $(gcloud compute instances list --filter=name~nat-gateway-${REGION} --uri) --ssh-flag="-A" -- ssh $(gcloud compute instances list --filter=name~gke-${CLUSTER_NAME}- --limit=1 --format='value(name)') -o StrictHostKeyChecking=no
However, when In try to access the pods using kubectl exec or kubectl attach or kubectl logs , I get the following error:
Get https://<IP_ADDRESS>:10250/containerLogs/default/mypod-1538082480-2j4m5/mypod: No SSH tunnels currently open. Were the targets able to accept an ssh-key for user "gke-0d30f9eca605b3f9accd"

I already checked that the ssh forward firewall rule from GKE cluster master IP to to the nodes exists and seems correct. What am I doing wrong here?

That usually happens when the static route to the master IPs has not been created. The example creates this route to preserve behavior like kubectl exec and logs.

@brandentimm, the example works with zonal, regional and private clusters. There is a step in the README.md where it pulls the endpoint IPs from the firewall rule.


New documentation needed

The directions for how to 'Manage Gateways' is now obsolete. The 'gear' graphic no longer exists in the latest released version of PowerBI.
Version: 2.65.5313.1381 64-bit (December 2018)

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

ID: 87176394-a2d4-7e3d-922e-d124d59fe9c5
Version Independent ID: 99c3109b-b094-1300-86e2-0cebb4475169
Content: Manage a Power BI on-premises gateway - Power BI
Content Source: powerbi-docs/service-gateway-manage.md
Service: powerbi
GitHub Login: @mgblythe
Microsoft Alias: mblythe

@mtzupan -- the intro to the doc has the following:
You can manage a gateway through the Manage gateways area of the Power BI service, in the gateway app on your local computer, and with PowerShell scripts. This article focuses on the Power BI service.
The first set of steps has this:
In the upper-right corner of the Power BI service, select the gear icon
I'll close for now, but feel free to re-open and let me know if you have any suggestions.


Improve accuracy of detection and tracking on IR camera output.

Please make sure that this is a feature request.
System information (Please provide as much relevant information as possible)

MediaPipe Solution (you are using): MediaPipe Hands
Programming language : Python/Android Java
Are you willing to contribute it (Yes/No): Yes

Describe the feature and the current behavior/state: Currently the hand tracking solution is unusable on IR camera output. An updated model will greatly improve the performance.
Will this change the current api? How? Not sure. But most probably not.
Who will benefit with this feature? Any application area where performance on low light conditions is a necessity.
Please specify the use cases for this feature: Most products are expected to be deployed in the wild and low light conditions are no rarity.
Any Other info:
The IR fails to preserve the shape of the hand and fingers are not easily distinguishable. Tracking fails frequently. A lot of glare is also observed.

Thank you for reaching us regarding the above query. What is unusable on IR camera output.Could you please elaborate your query with more details. Did you see any errors with hands solution on IR camera, and yes can you share the error details to investigate the above issue.

Actually, it can detect hands in a feed from the IR camera. But it's failing frequently. This frequent lack of prediction from the model makes it unreliable.
I'll share some recordings once I have access to the IR camera.

Hi @Sreerag-ibtl, Your recordings will be helpful for further investigation. Thanks!

I am using the mediapipe for Hospitals use on Patient's landmarks detection. When the amount of light is low or not directly to the face of the patient, if the patient is facing against the light, then amount of noise is increasing too much and declaring a static threshold is becoming a huge problem.
If anyone can help me through this, please. Thankyou.


Broken Link in README + Recommended Fix

The README's introductory paragraph has a link:
"Our quickstart guide can be used to get running quickly. This notebook will show how to instantiate a simple agent and run it on an environment. You can also take a look at our tutorial, which takes a more in-depth look at the construction of the D4PG agent. This also highlights the general structure of most Acme agents which applies more broadly to all agents implemented in Acme."
That quickstart guide link is broken. It is currently https://github.com/deepmind/acme/blob/master/examples/quickstart but it should be https://github.com/deepmind/acme/blob/master/examples/quickstart.ipynb

Hi @RylanSchaeffer, thanks for reporting this issue. The link appears to be working correctly, is it still an issue for you?

Hi! I posted this issue before realizing I could message you internally on the Acme slack channel. Old habits, I suppose :)


Cannot read properties of undefined (reading 'fallthrough')

Describe the bug
I implemented a Promise.all() in a shadow endpoint that hits 2 different external API endpoints before it combines and returns the data. While the app doesn't seem to be breaking, I am getting the following error in my console when running in development.
Cannot read properties of undefined (reading 'fallthrough')
TypeError: Cannot read properties of undefined (reading 'fallthrough')
    at validate_shadow_output (file:///E:/LocalDevelopmentFiles/viu-fe/svelte/.svelte-kit/runtime/server/index.js:2759:13)
    at load_shadow_data (file:///E:/LocalDevelopmentFiles/viu-fe/svelte/.svelte-kit/runtime/server/index.js:2694:38)
    at async load_node (file:///E:/LocalDevelopmentFiles/viu-fe/svelte/.svelte-kit/runtime/server/index.js:2285:5)
    at async respond$1 (file:///E:/LocalDevelopmentFiles/viu-fe/svelte/.svelte-kit/runtime/server/index.js:2986:15)
    at async resolve (file:///E:/LocalDevelopmentFiles/viu-fe/svelte/.svelte-kit/runtime/server/index.js:3456:11)
    at async respond (file:///E:/LocalDevelopmentFiles/viu-fe/svelte/.svelte-kit/runtime/server/index.js:3392:20)
    at async file:///E:/LocalDevelopmentFiles/viu-fe/svelte/node_modules/@sveltejs/kit/dist/vite.js:1555:22

Reproduction
https://github.com/rogadev/viu-fe/tree/for-svelte-bug
Logs
Cannot read properties of undefined (reading 'fallthrough')
TypeError: Cannot read properties of undefined (reading 'fallthrough')
    at validate_shadow_output (file:///E:/LocalDevelopmentFiles/viu-fe/svelte/.svelte-kit/runtime/server/index.js:2759:13)
    at load_shadow_data (file:///E:/LocalDevelopmentFiles/viu-fe/svelte/.svelte-kit/runtime/server/index.js:2694:38)
    at async load_node (file:///E:/LocalDevelopmentFiles/viu-fe/svelte/.svelte-kit/runtime/server/index.js:2285:5)
    at async respond$1 (file:///E:/LocalDevelopmentFiles/viu-fe/svelte/.svelte-kit/runtime/server/index.js:2986:15)
    at async resolve (file:///E:/LocalDevelopmentFiles/viu-fe/svelte/.svelte-kit/runtime/server/index.js:3456:11)
    at async respond (file:///E:/LocalDevelopmentFiles/viu-fe/svelte/.svelte-kit/runtime/server/index.js:3392:20)
    at async file:///E:/LocalDevelopmentFiles/viu-fe/svelte/node_modules/@sveltejs/kit/dist/vite.js:1555:22

System Info
System:
    OS: Windows 10 10.0.19044
    CPU: (8) x64 Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz
    Memory: 67.12 GB / 79.94 GB
  Binaries:
    Node: 18.3.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.5 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
    npm: 8.5.5 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 103.0.5060.134
    Edge: Spartan (44.19041.1266.0), Chromium (103.0.1264.71)
    Internet Explorer: 11.0.19041.1566
  npmPackages:
    @sveltejs/adapter-auto: next => 1.0.0-next.64
    @sveltejs/kit: next => 1.0.0-next.396
    svelte: ^3.44.0 => 3.49.0
    vite: ^3.0.0 => 3.0.3

Severity
annoyance
Additional Information
No response

@rogadev I cannot access your repository. Please check that it's accessible in an incognito window

Apologies. Give it a go, now.
On the main branch, I added the JSDoc voodoo magic and that seemed to do something, however there is no data being spat back to my page. I've also never seen a JSDoc like that before. It's completely unclear to me what this is doing...

I haven't had my coffee - I didn't mean to close that. 🤦♂

Here it is.
I made a noob error and didn't actually do anything with the object I created inside the Promise.all(). This makes it work as intended:
return await Promise.all([p1, p2]).then((results) => {
    return {
      status: 200,
      body: {
        noc,
        title: results[1].title,
        jobs: results[1].jobs,
        requirements: results[1].requirements,
        duties: results[1].duties,
        outlook: results[0].outlook,
        outlook_verbose: results[0].outlook_verbose,
        trends: results[0].trends,
        province: 'British Columbia',
        eruid: 5900,
      },
    }
  })

HOWEVER, I would still argue that the error messaging needs work. The way I finally figured out what was going on was this little squiggle at the top of my file which I never even noticed.

This finally nudged me to realize that I was just resolving all the promises and then doing absolutely nothing with what that Promise.all() returned.
I hope this is somewhat helpful feedback... 🤷♂


kirc: bump to 0.2.7

Existing package

[x] I am the maintainer of this package.

This PR includes some extraneous commits :o

woops… my bad. will fix it shortly =P


fix: bump client-go and apimachinery in abe2e gomod for CVE fix

What type of PR is this?

What this PR does / why we need it:
fixes CVE https://nvd.nist.gov/vuln/detail/CVE-2023-37788
Which issue(s) this PR fixes:

Fixes #
Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 79.051%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2415

Relevant Lines:
3055

💛  - Coveralls


A more complete example of authors

Documentation doesn't show how to specify author names or how to specify multiple authors.

r? @steveklabnik
(rust_highfive has picked a reviewer for you, use r? to override)

@bors r+
It's interesting that you can leave the authors field empty. I actually wonder why we require this field at all?

:pushpin: Commit 59f35af has been approved by matklad

:hourglass: Testing commit 59f35af8d1e80fa12ce61e986aea4f56e8b45a87 with merge f9255c7097d3d0469f84e86c3f5d4cfb03aeba94...

:sunny: Test successful - status-appveyor, status-travis
Approved by: matklad
Pushing f9255c7097d3d0469f84e86c3f5d4cfb03aeba94 to master...


JDK11 build for Windows is quite different from the java.net build

Maybe this is not an issue but I didn't find another place to ask/report it.
When looking at the OpenJDK 11 builds for Windows from AdoptOpenJDK and jdk.java.net they look quite different.
First, the build from AdoptOpenJDK is about 45% larger then the one from java.net (415MB vs. 287MB):
$ du -hs adoptopenjdk-11/
415M    adoptopenjdk-11/

$ du -hs openjdk-11/
287M    openjdk-11/

Second, when looking at the bin/ directory the AdoptOpenJDK build seems to use different DLLs than the java.net build, e.g. VC-Runtime version 12 in AdoptOpenJDK and version 14 in java.net.
Third, the AdoptOpenJDK build contains debugging information in .pdb and .map files where the one from java.net does not.
I would be interested to understand why the two builds are so different. I would have expected them to be quite similar.

Hi @ferstl - Great questions!
1.) The alternative DLLs are just a reflection of the toolchain that Adopt uses to build OpenJDK.  This happens to be different to Oracle's OpenJDK build and is likely different to OpenJDK builds by other vendors as well.
2.) We have deliberately left in the debug information as of when we started AdoptOpenJDK our primary audience was developers.
We do need to document these choices and probably remove debug as a default now.
I'll keep this open so we can track that.

Hi,
I just downloaded the AdoptOpenJDK java 8 build, and it doesn't seem to contain any PDB files.
Please make a debug build available for us poor developers who were actually using those :(
Cheers,
Will

We will, it's just a bit behind in the queue at the minute.  If you'd like to help out then you can join the us at adoptopenjdk.net/slack

@ferstl can this be closed now?

This is effectively now a duplicate of #146 - so closing in favour of that one.


Realm library is missing when signing archive for enterprise distribution

There seems to be an issue when exporting archive for Enterprise distribution.
I am using Realm and RealmSwift 1.1.0 with Xcode8.
Here is the stack trace:
Termination Description: DYLD, Library not loaded: @rpath/Realm.framework/Realm | Referenced from: /var/containers/Bundle/Application/DF539C48-5B15-4E10-8498-E2F8FE13A1B9/xxxx.app/xxxx | Reason: no suitable image found. Did find: | /private/var/containers/Bundle/Application/DF539C48-5B15-4E10-8498-E2F8FE13A1B9/xxxx.app/Frameworks/Realm.framework/Realm: code signing blocked mmap() of '/private/var/containers/Bundle/Application/DF539C48-5B15-4E10-8498-E2F8FE13A1B9/xxxx.app/Frameworks/Realm.framework/Realm' | /private/var/containers/Bundle/Application/DF539C48-5B15-4E10-8498-E2F8FE13A1B9/xxxxx.app/Frameworks/Realm.framework/Realm: code signing blocked mmap() of '/private/var/containers/Bundle/Application/DF539C48-5B15-4E10-8498-E2F8FE13A1B9/xxxx.app/Frameworks/Realm.framework/Realm' | /private/var/containers/Bundle/Application/DF539C48-5B15-4E10-8498-E2F8FE13A1B9/xxxx.app/Frameworks/Realm.framework/Realm: code signing blocked mmap() of '/private/var/containers/Bundle/Application/DF539C48-5
Triggered by Thread: 0

@kljajo could you please share more information? How are you building Realm? If you're using CocoaPods/Carthage/Xcode, what versions of everything are you using? What steps can we take to reproduce this?
There's a reason this information is requested in the new issue template. It's difficult for us to help you without that information.

@jpsim I am using CocoaPods version 0.39.0 with Xcode 8.
Just add realm via CocoaPods in your Swift 3 project. Build it, create an archive, export it for In-House distribution and put it on the device. App will crash on start with above stack trace.
Note that this does not happen with AppStore and AdHoc distributions.

Thanks for sharing that info, @kljajo. I think I have enough information to help you, now I just have to take the time to attempt to reproduce the problem so I can investigate further.
How critical is it for this to be fixed as soon as possible? Do you have a workaround?

Hi @jpsim . Unfortunately I don't have workaround. I am in the middle of the project which has to be delivered to the client before end of a month. I will have to convert the code without Realm if you perhaps don't have some workaround? Thanks.

Understood. Not I don't have a workaround to suggest to you because I'm not sure why this is happening and haven't reproduced it myself yet.
If you do want to accelerate the process of us looking into this, a full reproducible sample Xcode project and steps to trigger the issue would greatly help.

hi @jpsim,
I have resolved the issue. The problem was with enterprise certificate not being properly generated by Developer portal. After I've revoked it and regenerated it, app can be started now with realm libraries included in the project.

Glad to hear it, thanks!


Update elastic-apm-node dependency to v3.5.0

I'll merge it - but could you check why we need a reference in the package.json file as well? Usually that shouldn't be needed because everything in the package.json should only be dev-dependencies and all the real dependencies for using the package should only be in the package.js file.


Audit: Bid1155 missing zero check

NFTFactory contract has a missing zero address check in sellNFT_buyBid.

duplicate.. we can close it


Comment based help does not work for scripts that start with a shebang

PowerShell does not parse comment based help for a script unless the help comment starts on the first line of the script. This prevents scripts employing a shebang from being helpful via Get-Help.
PowerShell should skip the first line of a script file if it starts with #!.
Steps to reproduce
Create a new script called thing.ps1 with a shebang:
#!/usr/bin/env pwsh
<#
.SYNOPSIS
This does a thing
#>

Expected behavior
PS> Get-Help thing.ps1

NAME
    /Users/aaron/src/thing.ps1

SYNOPSIS
    This does a thing

…

Actual behavior
PS> Get-Help thing.ps1
thing.ps1
…

Environment data

PS> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      6.0.0-beta.9
PSEdition                      Core
GitCommitId                    v6.0.0-beta.9
OS                             Darwin 16.7.0 Darwin Kernel Version 16.7.0: Thu Jun 15 17:36:27 PDT 2017; root:xnu...
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Note, this is an issue with both syntaxes:
#!/usr/bin/env pwsh
# .SYNOPSIS
# This does a thing

This is definitely a bug. However ...
You just need a blank line between the shebang and the help to work around it.


12 threshold window example

This PR creates adds an example for the threshold window operator.
A number of features are still not supported. These are documented in the file ThresholdWindowExample.
The threshold window relies on the new Nautilus query compiler. However, the inferModel example requires the old query compiler. Therefore, I have split the worker into two workers, which have different query compilers configured.
Closes #12.

@he-sk should we close this?

We can close this


(PUP-3809) Separate code and config directories

This PR introduces the new $puppetdir directory setting that will be the parent of the existing $confdir and the new $codedir.
The following settings have moved out from under $confdir entirely and are now under $codedir:

$environmentpath (note that manifests and modules are rooted at this, so they've effectively moved)
$hiera_config
$basemodulepath

In addition, the $ssldir has been moved out from under $confdir and is now directly under $puppetdir.
The directory structure now looks like:
$puppetdir
  $codedir
  $confdir
  $ssldir

These changes pass spec tests, but I have not ran acceptance tests yet.
Happy to squash commits if desired.

Pinging @kylog, @joshcooper, @hlindberg, @haus, @jpartlow, @cprice404, and @jeffmccune.
CC @pcarlisle and @kbarber - FYI this is the work that I pinged you about on the sub-tasks of PUP-3809.

CLA signed by all contributors.

This PR is based on @whopper's PUP-3632 AIO changes and will need to be rebased once the fallout from those changes is addressed.

CLA signed by all contributors.

While looking into an erroring acceptance test, I noticed that confdir is now /etc/puppetlabs/agent/config and puppetdir is /etc/puppetlabs/agent, but puppet.conf was still under /etc/puppetlabs/agent:
root@pjeqlxxyc4m8t9l:/tmp/file_source_attr.idQs4e# puppet config print confdir -- environment=production
/etc/puppetlabs/agent/config
root@pjeqlxxyc4m8t9l:/tmp/file_source_attr.idQs4e# puppet config print puppetdir --environment=production
/etc/puppetlabs/agent
root@pjeqlxxyc4m8t9l:/tmp/file_source_attr.idQs4e# ls /etc/puppetlabs/agent/
auth.conf  code  config  puppet.conf  ssl

$puppetdir does not get expanded:
strace -e trace=file /opt/puppetlabs/agent/bin/puppet agent --test --server localhost 2>&1|grep puppet\.conf
stat("$puppetdir/config/puppet.conf", 0x7fff13614080) = -1 ENOENT (No such file or directory)
EL7, puppet-agent-0.2.2-1.rpm

@roidelapluie Aha! Thanks a ton for catching that - hugely helpful! @nwolfe now we just need to figure out why puppet.conf isn't ending up in the new config directory.

I've functionally reviewed @nwolfe's commits and have verified they're working.

It is my understanding that some of the Windows pathing changes are not quite ironed out yet, is that right?

Yes, testing Puppet acceptance runs through Beaker via git does not work.
Firstly, it dies on the master as Puppet is not in the PATH.  I've hacked a temporary fix into my fork of Puppet to tackle the PATH issue.  Note I am running against Beaker 2.3.0.
https://github.com/Iristyle/puppet/commit/b140fd9f22049f83c9eabe24c5b416726e333909
After that change is made, it dies in setup/git/pre-suite/020_PuppetUserAndGroup.rb on Windows with
cmd.exe /c puppet resource user puppet ensure=present
Last 10 lines of output were:
	Error: /File[C:/opt/puppetlabs/agent/cache]/ensure: change from absent to directory failed: Cannot create C:/opt/puppetlabs/agent/cache; parent directory C:/opt/puppetlabs/agent does not exist
	Error: Cannot create C:/var/log/puppetlabs/agent; parent directory C:/var/log/puppetlabs does not exist
	Error: /File[C:/var/log/puppetlabs/agent]/ensure: change from absent to directory failed: Cannot create C:/var/log/puppetlabs/agent; parent directory C:/var/log/puppetlabs does not exist
	Warning: /File[C:/opt/puppetlabs/agent/cache/state]: Skipping because of failed dependencies
	Error: Cannot create C:/var/run/puppetlabs; parent directory C:/var/run does not exist
	Error: /File[C:/var/run/puppetlabs]/ensure: change from absent to directory failed: Cannot create C:/var/run/puppetlabs; parent directory C:/var/run does not exist
	Warning: /File[C:/opt/puppetlabs/agent/cache/lib]: Skipping because of failed dependencies
	Notice: /File[C:/opt/puppetlabs/agent/cache/facts.d]: Dependency File[C:/opt/puppetlabs/agent/cache] has failures: true
	Warning: /File[C:/opt/puppetlabs/agent/cache/facts.d]: Skipping because of failed dependencies
	Error: Could not run: Got 3 failure(s) while initializing: File[C:/opt/puppetlabs/agent/cache]: change from absent to directory failed: Cannot create C:/opt/puppetlabs/agent/cache; parent directory C:/opt/puppetlabs/agent does not exist; File[C:/var/log/puppetlabs/agent]: change from absent to directory failed: Cannot create C:/var/log/puppetlabs/agent; parent directory C:/var/log/puppetlabs does not exist; File[C:/var/run/puppetlabs]: change from absent to directory failed: Cannot create C:/var/run/puppetlabs; parent directory C:/var/run does not exist>

Some settings are mangled on the Windows machine - currently investigating.
cmd.exe /c puppet agent --configprint vardir
DL is deprecated, please use Fiddle
C:/opt/puppetlabs/agent/cache

Administrator@dmiyp7sx7q0zbhu ~
$ cmd.exe /c puppet agent --configprint codedir
DL is deprecated, please use Fiddle
C:/ProgramData/PuppetLabs/puppet/etc/code

Administrator@dmiyp7sx7q0zbhu ~
$ cmd.exe /c puppet agent --configprint puppetdir
DL is deprecated, please use Fiddle
C:/ProgramData/PuppetLabs/puppet/etc

Administrator@dmiyp7sx7q0zbhu ~
$ cmd.exe /c puppet agent --configprint rundir
DL is deprecated, please use Fiddle
C:/var/run/puppetlabs

Administrator@dmiyp7sx7q0zbhu ~
$ cmd.exe /c puppet agent --configprint configdir
DL is deprecated, please use Fiddle
invalid setting: configdir

Administrator@dmiyp7sx7q0zbhu ~
$ cmd.exe /c puppet agent --configprint logdir
DL is deprecated, please use Fiddle
C:/var/log/puppetlabs/agent

Administrator@dmiyp7sx7q0zbhu ~
$ cmd.exe /c puppet agent --configprint bindir
DL is deprecated, please use Fiddle
invalid setting: bindir

@Iristyle - Will (@whopper) had hit me up about this having some fun with Windows and changes. I just wanted to drop a note here so this didn't get merged in until those changes were also validated against Windows.

CLA signed by all contributors.

CLA signed by all contributors.

Sorry for the force-push updates - trying to stay on top of origin/master like a hawk

I have pushed the commits in this PR to the https://github.com/puppetlabs/puppet/tree/aio branch and we'll be running the pipeline against it. Going to close this PR and resubmit once it passes on rhel7.


Edited the PPP

Pull Request Test Coverage Report for Build 296

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 86.567%

Totals

Change from base Build 295:
0.0%

Covered Lines:
2726

Relevant Lines:
3149

💛  - Coveralls


create a card_template.html to reduce the code repetition

Fixes #40
Description of the Change
I create a new template html file named card_template.html. After that, I change the design of all card.html files and follow the style of card_templates to reduce the code repetition.
Checklist
Please check all that apply to your proposed changes

[x] HTML code change
[ ] Added package dependency
[ ] Added data
[ ] Changed django model
[ ] Documentation change
[ ] Added or changed TaskRunner

Additional context

extra css and old code are removed.


Refactor SpecEasy.Specs so all tests pass; easier to add meta tests, etc.

introduces SpecRunner.Run to make writing meta tests (tests that assert the
results of Specs) easier and less brittle (uses types rather than strings for
identifying which spec to run)
introduces SupportingExampleAttribute which inherits from NUnit's
ExplicitAttribute (http://www.nunit.org/index.php?p=explicit&r=2.6.4)
This allows us to mark supporting Specs and NUnit TestFixtures so that they
will not be included when running all tests in SpecEasy.Specs. This keeps
intentionally failing specs/tests out of the output window
reorganize ExceptionReporting for better clarity

ExceptionReporting meta tests => ExceptionReportingTests
BrokenClassSpec & NUnitBrokenClassTests are marked as [SupportingExample]s

@rockhymas @appakz @ronrat @mmertsock Please review (and please let me know if there are additional folks I should have pinged)

Looks good to me.

:+1:

:+1:
@jsternal

Very nice, I think we ought to merge.

@jsternal @ronrat Awesome. Once this gets merged, I'll squash and rebase #39 so it'll be ready to merge as well.


LSP (Language Server Protocol) Support

In an ideal world rye gains a new lsp command that serves up an LSP composed of at the very least the ruff LSP so that linting and formatting works and can be served up to a vscode extension or similar #556.

Also, good discussion is here: https://github.com/astral-sh/ruff/pull/7262


WIP: Fix 0.9.6 build

Attempt to fix https://github.com/conda-forge/sourmash_plugin_branchwater-feedstock/pull/14
First idea: update to MACOSX_SDK_VERSION 10.15 per docs.

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

ok, if https://github.com/conda-forge/sourmash_plugin_branchwater-feedstock/pull/15/commits/3d5cc7db67a47836b2358a8e2deeb1ab9da2e741 causes breakage again, then we know it's -D_LIBCPP_DISABLE_AVAILABILITY.
Once that works, maybe try resetting the maturin versions to < 2, as well.

@conda-forge-admin, please rerender
(probably not needed)


[suggestion] is it possible to add feature of provider api

provider api means that not only we can get host from location ssh config file, but also from a rest api, the rest api should have some restriction, like data restriction.

It is technically possible, but there may be some security risks.
It will be more complicated, and the requirements for users will be very high.

or may a plugin of trzsa-ssh.

It is technically possible, but there may be some security risks. It will be more complicated, and the requirements for users will be very high.

indeed.  tssh provide a open-box options for most of users.  If supported this feature,  for advanced user, we can provide spec to let them to implemented, for common user, we can provide a subproject in form of docker to reduce the complexity of provide api.

It is technically possible, but there may be some security risks.

can agree with this point any more, so we need to have a full consideration.

Is it possible for users to implement a client themselves, write a custom configuration file after obtaining the informations, and then specify the default configuration file in ~/.tssh.conf?

sounds feasible 👍

Now you can get the host information from anywhere you want, convert it into ssh command line arguments, and call tssh to log in.
Before v0.1.22 is released, you can go get github.com/trzsz/trzsz-ssh@main, and then call tssh to log in like:
package main

import (
	"os"
	"github.com/trzsz/trzsz-ssh/tssh"
)

func main() {
	code := tssh.TsshMain([]string{"-t"<EMAIL_ADDRESS>	os.Exit(code)
}


Unique indexes

Huge PR.
Adds a way to create unique indexes, and use this new method for ensuring that usernames and emails are unique. But, some people might already have non-unique emails and username, so if the index build fails, we fall back on the previous method. This is going to be super slow in that case, as we will attempt to build an index every time someone signs up. For that reason, I think I'll make this trigger 2.3.0 and encourage people to build their unique indexes before upgrading.
For behaviour around nulls: Unique indexes are required to ignore undefined/unset fields for the purposes of uniqueness. This is why we use sparse indexes. For null, the plan is to not allow unique indexes on nullable fields. Since we don't currently have a way to specify that a field is non-nullable, we basically aren't going to expose this interface to users yet.
We already require unique emails, but both null and undefined don't count towards uniqueness, somehow, on Parse.com. I think if anyone actually has null for multiple emails, we'll tell them to make sure to clean up their data before upgrading to 2.3.0.

[Current coverage][cc-pull] is 91.93%

Merging [#1971][cc-pull] into [master][cc-base-branch] will increase coverage by <.01%

File ...go/MongoTransform.js (not in diff) was modified. more

Misses -1
Partials 0
Hits +1

@@             master      #1971   diff @@
==========================================
  Files            91         91
  Lines          6406       6430    +24
  Methods        1094       1107    +13
  Messages          0          0
  Branches       1345       1352     +7
==========================================
+ Hits           5886       5911    +25
+ Misses          520        519     -1
  Partials          0          0

Powered by Codecov. Last updated by [abeecad...23b120c][cc-compare]
[cc-base-branch]: https://codecov.io/gh/ParsePlatform/parse-server/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/ParsePlatform/parse-server/compare/abeecad907138c12ab33e0ed0e23b523ae4897cd...23b120c6b8d55766c24859891448d1e7ee0b3c03
[cc-pull]: https://codecov.io/gh/ParsePlatform/parse-server/pull/1971?src=pr

@drewgross if we go for 2.3.0 let's put the upgrade guide in that PR, maybe in a 2.3.0.md and move it to the README.md when releasing?

Good idea. I was going to put it in the Parse Blog, but having it in the repo sounds like a good idea too.

@drew-gross updated the pull request.

At least 2 changes are coming: Don't attempt to create the index every time a user signs up, and don't delete null emails if the index build fails.

@drew-gross updated the pull request.

@drew-gross updated the pull request.

@drew-gross updated the pull request.

@drew-gross updated the pull request.

@drew-gross updated the pull request.

@drew-gross updated the pull request.

@drew-gross updated the pull request.

@drew-gross updated the pull request.

@drew-gross updated the pull request.

@drew-gross updated the pull request.

@drew-gross updated the pull request.

@drew-gross updated the pull request.

@drew-gross updated the pull request.

@drew-gross updated the pull request.

@drew-gross updated the pull request.

@drew-gross updated the pull request.

@drew-gross updated the pull request.

@drew-gross updated the pull request.

@drew-gross updated the pull request.

@drew-gross updated the pull request.

@drew-gross updated the pull request.

@drew-gross updated the pull request.

@drew-gross updated the pull request.

I just had a look at the new readme file + the new code directly dealing with creating those indexes and it looks good to me. I'd look into why the tests are failing (seems just flaky?) and maybe have someone how knows what they're doing with JS check the rest of the changes.
For the unique index creation part, LGTM.

One of the other changes in here causes tests to fail if there are any open connections to the server left after the test finishes. This was really helpful for debugging, but a lot of our other tests leave connections open so until we can clean them up, they will be flaky. Fortunately it's easy to detect and fix the flakiness now.


Improved concurrent safety in PeerNode message handling

Codecov Report

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

@@          Coverage Diff           @@
##           master     #72   +/-   ##
======================================
  Coverage    35.3%   35.3%
======================================
  Files          24      24
  Lines        3487    3487
======================================
  Hits         1231    1231
  Misses       2120    2120
  Partials      136     136

Continue to review full report at Codecov.

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

Made some comments. Can you please review? @wqking


Nested Utilities

Allow utilities to be nested within other utilities
from arc import CLI, Utility
animals = Utilites("animals)
converse = Utility("converse", utilities=[animals])
cli = CLI(utilities=[converse])
# can also use cli.install_utilities(converse) for the same effect

# regular cli command
@cli.script("greet")
def cli_greet(name="Joseph Joestar"):
    """Command that greets someone CLI command"""
    print(f"Hello, {name}!")
    print("This command is associated with the global CLI")

# utility command
@converse.script("greet")
def utility_greet(name="Jotaro Kujo"):
    """Command that greets someone utility command"""
    print(f"Howdy, {name}!")
    print("This command is associated with the 'converse' utility")

# nested utility command
@animals.script("greet")
def nested_greet(call="Bark bark"):
   print(call)
   print(call)

if __name__ == "__main__":
    cli()

$ python example.py greet
Hello, Joseph Joestar!
$ python example.py converse:greet
Howdy, Jotaro Kujo
$ python example.py converse:animals:greet
Bark bark
Bark bark

2.0's Subcommand rework will handle nesting scripts like this

2.0's Subcommand rework will handle nesting scripts like this


2D extra example

Hello! I tried the other 2D example on Jupyter notebook and there is a positional argument missing that is suppose to be there. Not sure whether this is Github issue worthy, but I am not sure from the code on StardistData2D what to fill in. Already tried length = 1 and length = 100*400

Hi, thanks for letting us know and sorry for the late reply!
I've just updated the notebooks (some additional things also needed fixing).
Best,
Uwe


Fix Gradle metadata serialization in module cache

This pull request fixes #3712 and https://github.com/gradle/gradle-native/issues/329 , by making sure Named attributes are properly serialized, as well as dependency constraints.
To reduce the risks of this happening again, the pull request introduces a new test which makes sure that we can serialize parsed metadata, then read it, and that the deserialized version is the same. This mimics what cached module metadata would do.
Now both the serializer and the parser are generic and have no special case handling of attributes.

@bigdaz Changes implemented, ready for review!


Kulfy: Watch fakazamusic.co

Kulfy requests the watch of the watch_keyword fakazamusic\.co. See the MS search here and the Stack Exchange search here.

fakazamusic\.co has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Andy in Charcoal HQ


How to reference a formatFn outsite the component?

Issue Type (delete the irrelevant ones)

[x] Question

Specs
What version are you using?
v2.21.11
What browser?
Brave [Version 1.35.100 Chromium: 98.0.4758.87 (Official Build)
I'm using the vue-good-table to show different kinds of data from an API, and I have a function that generates the "column options" based on the results the came from that API,  now I want to use the formatFn for some columns and I'm having some problems.
I don't think the problem is with the vue-good-table, but rather how to correctly pass this function to the formatFn property. The function that generates the "column options" array is kind of global, I'm not using vue-cli, this is an old panel that uses vue in some features, and the function that generates the array of  "column options" is accessible from all the components that uses vue-good-table.
I tried some ways to pass the function reference in the type property but none worked.
if(columnType === 'number'){
    columnType = formatNumericValue()
}

const column = {
    label: columnlabel,
    field: key,
    type: columnType,
    sortable: false,
}

columns.push(column)

function formatNumericValue(value) {
    console.log(value);
    return value.toString().replace(/\B(?=(\d{3})+(?!\d))/g, ".");
}

With this code the function formatNumericValue receives no value "TypeError: Cannot read properties of undefined (reading 'toString')"
I also tried to add the formatNumericValue function in the methods of the component, but that also didn't work
 // in methods
formatNumericValue: function(value) {
    console.log(value);
    return value.toString().replace(/\B(?=(\d{3})+(?!\d))/g, ".");
}

What can I do?

Found my error, I was trying to pass the function to the type parameter and not to the formatFn.


Writing StoreFindToken and BlobReadOptions in new formats

This commit writes StoreFindToken and BlobReadOptions in the new formats and thus enables log segmentation end to end
Moved StoreFindToken into its own file to make it public so that it can be used in the server integration tests.
./gradlew build && ./gradlew test passed successfully on both OSx and Linux.
Primary reviewers : @pnarayanan, @nsivabalan
Expected time to review : 15 mins

Looks good to me.

@pnarayanan addressed comments. Formatted and build + test passed on OSX and Linux

LGTM, merging.


Unable to delete files and folders

Storage Explorer Version: 1.15.1
Build Number: 20200902.9
Platform/OS: Windows 10
Architecture: x64?
Regression From:
Bug Description
After uploading folders using AzCopy, I am unable to delete them.  Error message is
{
"message": ""Authentication Failed. The SAS is not correct or expired or does not have the correct permission -> github.com/Azure/azure-storage-blob-go/azblob.newStorageError, /home/vsts/go/pkg/mod/github.com/!azure/azure-storage-blob-go@v0.10.1-0.20200812020820-59b3010ad575/azblob/zc_storage_error.go:42\n===== RESPONSE ERROR (ServiceCode=AuthorizationPermissionMismatch) =====\nDescription=This request is not authorized to perform this operation using this permission.\nRequestId:9409ebf7-501e-0068-5402-980df8000000\nTime:2020-10-01T14:52:05.0399139Z, Details: \n   Code: AuthorizationPermissionMismatch\n   DELETE https://df9f4bfffd684d4cbc84f60.blob.core.windows.net/ingestiondata/aagular/archive2.pst?se=2020-10-31t14%3A51%3A36z&si=ingestionsasforazcopy202008281621210729&sig=-REDACTED-&sr=c&sv=2015-04-05&timeout=901\n   User-Agent: [Microsoft Azure Storage Explorer, 1.15.1, win32,  AzCopy/10.6.0 Azure-Storage/0.10 (go1.13; Windows_NT)]\n   X-Ms-Client-Request-Id: [66b6fc0c-3bf7-4d2b-4e9f-a4412aac0d75]\n   X-Ms-Version: [2019-12-12]\n   --------------------------------------------------------------------------------\n   RESPONSE Status: 403 This request is not authorized to perform this operation using this permission.\n   Content-Length: [279]\n   Content-Type: [application/xml]\n   Date: [Thu, 01 Oct 2020 14:52:04 GMT]\n   Server: [Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0]\n   X-Ms-Client-Request-Id: [66b6fc0c-3bf7-4d2b-4e9f-a4412aac0d75]\n   X-Ms-Error-Code: [AuthorizationPermissionMismatch]\n   X-Ms-Request-Id: [9409ebf7-501e-0068-5402-980df8000000]\n   X-Ms-Version: [2019-12-12]\n\n\n""
}
Steps to Reproduce

Upload folders with AzCopy
Use SAS URL from Office 365 Info Governance\Import to connect in Azure Storage Explorer
Try to delete folders uploaded.

Expected Experience
I expect files/folders to be removed when deleted
Actual Experience
Receive error message.
Additional Context

@Canis-Lupis How do you connect to the blob container? Are you signed-in, attaching with Azure AD or attaching with SAS?
The error message says you are missing the delete permission. There should be a "sp=rdl" parameter in the url "https://df9f4bfffd684d4cbc84f60.blob.core.windows.net/ingestiondata/aagular/archive2.pst?se=2020-10-31t14%3A51%3A36z&si=ingestionsasforazcopy202008281621210729&sig=-REDACTED-&sr=c&sv=2015-04-05&timeout=901". Could you check if it exists and if a "d" exists in the parameter?

Attaching with SAS per the instructions on importing psts:  https://docs.microsoft.com/en-us/microsoft-365/compliance/use-network-upload-to-import-pst-files?view=o365-worldwide
[https://docs.microsoft.com/en-us/media/logos/logo-ms-social.png]https://docs.microsoft.com/en-us/microsoft-365/compliance/use-network-upload-to-import-pst-files?view=o365-worldwide
Use network upload to import your organization's PST files - Microsoft 365 Compliance | Microsoft Docshttps://docs.microsoft.com/en-us/microsoft-365/compliance/use-network-upload-to-import-pst-files?view=o365-worldwide
For a high-level overview of the PST Import process, see How the import process works section in this article.. Step 1: Copy the SAS URL and install AzCopy. The first step is to download and install the AzCopy tool, which is the tool that you run in Step 2 to upload PST files to Office 365.
docs.microsoft.com

From: JasonYeMSFT<EMAIL_ADDRESS>Sent: Thursday, October 1, 2020 4:00 PM
To: microsoft/AzureStorageExplorer<EMAIL_ADDRESS>Cc: David Tessmann<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [microsoft/AzureStorageExplorer] Unable to delete files and folders (#3634)
@Canis-Lupishttps://github.com/Canis-Lupis How do you connect to the blob container? Are you signed-in, attaching with Azure AD or attaching with SAS?
The error message says you are missing the delete permission. There should be a "sp=rdl" parameter in the url "https://df9f4bfffd684d4cbc84f60.blob.core.windows.net/ingestiondata/aagular/archive2.pst?se=2020-10-31t14%3A51%3A36z&si=ingestionsasforazcopy202008281621210729&sig=-REDACTED-&sr=c&sv=2015-04-05&timeout=901". Could you check if it exists and if a "d" exists in the parameter?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/AzureStorageExplorer/issues/3634#issuecomment-702394980, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMUD2TDJ5AA4QMQNZEK3YTLSITUXZANCNFSM4SARNR2Q.

Oh, I see. Your SAS is using an access policy which specifies your permissions (in the 'si=ingestionsasforazcopy202008281621210729'). It is possible that the access policy didn't grant you delete permission, could you check with the provider of the SAS to see if delete permission is granted?

Microsoft is the provider.  There's nothing listed about what the permissions are.  Please see link I sent previously.  Also, below is a screenshot from protection.office.com where I'm getting the SAS:
[cid:7b2325cd-a033-4606-9781-72235c137a97]

From: JasonYeMSFT<EMAIL_ADDRESS>Sent: Thursday, October 1, 2020 4:33 PM
To: microsoft/AzureStorageExplorer<EMAIL_ADDRESS>Cc: David Tessmann<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [microsoft/AzureStorageExplorer] Unable to delete files and folders (#3634)
Oh, I see. Your SAS is using an access policy which specifies your permissions (in the 'si=ingestionsasforazcopy202008281621210729'). It is possible that the access policy didn't grant you delete permission, could you check with the provider of the SAS to see if delete permission is granted?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/AzureStorageExplorer/issues/3634#issuecomment-702409897, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMUD2TARIAH75WLIZJKYXJTSITYRTANCNFSM4SARNR2Q.

The instruction says the SAS "provides you with the necessary permissions to upload PST files to your Azure Storage location". Delete permission is not needed for upload. If you want to delete those files/folders in Storage Explorer, you'll need to either

sign-in to get the subscription of the blob container "df9f4bfffd684d4cbc84f60"
Attach to the blob container with Azure AD
Find the container owner who can generate a SAS with delete permission for you

In the 1st and the 2nd approach, it also requires you to have the role that grants you delete permission (e.g. https://docs.microsoft.com/en-us/azure/role-based-access-control/built-in-roles#storage-blob-data-contributor).
Let me know if you still have any questions.

Closing due to lack of response. If you're still encountering this problem, please open a new issue. Thanks!


Sync command inconsistent branch quoting

I've noticed that the sync command has inconsistent quotes when displaying warnings about certain branches. For example, I got this output:
git sync
warning: `issue_173' seems to contain unpushed commits

Note that the branch is preceded by a backtick and followed by a single quote. I believe that the types of quotes should be the same before and after the branch name.
Here's one of the relevant portions of the code:
https://github.com/github/hub/blob/3edbd86fab2028aa997eb51a812d14afe1899f05/commands/sync.go#L116-L118
For consistency with Git itself, I think single quotes should be used. Here's the output from git checkout, which uses single quotes around the branch name:
Switched to branch 'issue_173'
Your branch is ahead of 'origin/issue_173' by 3 commits.
  (use "git push" to publish your local commits)

Good catch! I agree that we should strive to match git's formatting.


Support MySQL with MariaDB engine

MariaDB engine supports JSON fields and operations with JSON values. But instead of JSON, it uses the LONGTEXT alias. As result, the ORM can't determine from the DB metadata for which fields we use JSON. We need to add a metadata table to provide additional information about JSON fields. The table should have the name: INFORMATION_SCHEMA_COLUMNS. Required columns are: TABLE_NAME, COLUMN_NAME, COLUMN_TYPE, IS_NULLABLE. Information about column types we can take from the execution result SELECT * FROM information_schema.columns

@mbaser Can you open similar issues in setup?

Implemented


Misaligned menuitems

Hi.
I'm using setMenuItemIcon to add menu items using fontFamily: 'MaterialIcons-Regular' (https://www.google.com/design/icons/index.html), but the icons are not vertically centered, they are sticked to the top of toolbar.
There is a way to center or set a top value for menu items?
As a side question: Can I use setMenuItemIcon from Alloy xml so I can use class styles on it?
Thank you.

Hi @EthraZa
can you please help me debugging this. I've just tried this material icons font but I'm not getting an icon at all. This is the code I'm using to test this:
abx.setMenuItemIcon({
  menu: e.menu,
  menuItem: settingsItem,
  fontFamily: 'MaterialIcons-Regular',
  icon: 0xe86a,
  color: "#333333",
  size: 30
});

(I've downloaded the MaterialIcons-Regular.ttf into the fonts directory)

@manumaticx   icon: '0xe86a',   should be a string?

I put the font there too and I'm just using this code:
function doOpen(e) {
	try {
		var activity = $.win.activity,
		actionBar = activity.actionBar;
		actionBar.title = args.name;
		actionBar.setDisplayHomeAsUp(true);
		actionBar.onHomeIconItemSelected = closeWindow;

		activity.onCreateOptionsMenu = function(e) {
			e.menu.clear();

			var menuItems = [{
				itemId: 201,
				title: L('ok'),
				icon: 'note_add',
				cb: 'saveEvent',
				showAsAction: Ti.Android.SHOW_AS_ACTION_ALWAYS
			}];

			_.each(menuItems, function(i){
				var item = e.menu.add({
					itemId: i.itemId,
					title: i.title,
					showAsAction: i.showAsAction || Ti.Android.SHOW_AS_ACTION_NEVER
				});

				abx.setMenuItemIcon({
					menu: e.menu,
					menuItem: item,
					fontFamily: 'MaterialIcons-Regular',
					icon: i.icon,
					//size: 24,
					color: '#fff'
				});

				item.addEventListener('click', eval(i.cb));
			});
		};

		activity.invalidateOptionsMenu();
	} catch(er) {
	}
}

same problem here. Using MaterialIcons-Regular, the icons are not centered vertically.

FontAwsome and this one (Material) works well though: http://zavoloklom.github.io/material-design-iconic-font/icons.html :)

@EthraZa @shawnlan
Hey guys, can you give me some more information about your environment? I've tested this and it works fine for me with MaterialIcons-Regular font (thanks @nuno - icon has to be a string of course).
This is my updated code:
abx.setMenuItemIcon({
  menu: e.menu,
  menuItem: settingsItem,
  fontFamily: 'MaterialIcons-Regular',
  icon: String.fromCharCode(0xe86a),
  color: "#333333",
  size: 30
});

Try to use default size (24) and see what you'll get.

Btw, I'm using ttf version.

I'm using .ttf too. Size 24 looks good, perfectly vertical aligned.

Please try the example. If this does not work for you, please let me know which Titanium version you are using and maybe a screenshot.

Okay, I've now tested this with the example code include here with 3.5.1.GA, 4.0.0.GA and 4.1.0.GA and it just works fine. Please try my example code and let me know if you still face this issue. If that's the case, please add a screenshot and as much information as possible.
I'm closing this for now as it it not reproducible but feel free to reopen.

@manumaticx ,
The problem was the way I was using the icon property.
Instead of
icon: 'note_add'

it needs to be
icon: String.fromCharCode(0xE89C)

Thank you so much for this great module and help. :+1:

Yes I did the same thing. But why something like 'note_add' causes such issue?

Well you could use TiIconicFont or (maybe) IconFont to support usage by icon name. You just have to create a map for icon names and its hex values as seen here: https://github.com/google/material-design-icons/blob/master/iconfont/codepoints (Should look like this).
Anyway, I'm glad I could help.

Hey, I've done that quickly ;)
https://github.com/k0sukey/TiIconicFont/pull/13

Wow. That was quick!
Awesome.
Atte.
--
Allan Brazute Alves
+55 (11) 96347-5063
<EMAIL_ADDRESS>/ www.ghsix.com.br/allan
2015-08-17 6:15 GMT-03:00 Manuel Lehner<EMAIL_ADDRESS>
Hey, I've done that quickly ;)
k0sukey/TiIconicFont#13 https://github.com/k0sukey/TiIconicFont/pull/13
—
Reply to this email directly or view it on GitHub
https://github.com/ricardoalcocer/actionbarextras/issues/82#issuecomment-131740392
.


Update scalafmt-core to 2.6.3

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

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

labels: library-update, semver-patch

Codecov Report

Merging #1503 into master will increase coverage by 0.13%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1503      +/-   ##
==========================================
+ Coverage   85.79%   85.93%   +0.13%
==========================================
  Files          58       58
  Lines        2197     2197
  Branches      107      107
==========================================
+ Hits         1885     1888       +3
+ Misses        312      309       -3

Impacted Files
Coverage Δ

...rc/main/scala/io/circe/numbers/BiggerDecimal.scala
85.38% <0.00%> (-0.59%)
:arrow_down:

.../core/shared/src/main/scala/io/circe/Decoder.scala
85.32% <0.00%> (-0.28%)
:arrow_down:

...les/core/shared/src/main/scala/io/circe/Json.scala
79.88% <0.00%> (+0.55%)
:arrow_up:

...re/shared/src/main/scala/io/circe/KeyDecoder.scala
97.29% <0.00%> (+2.70%)
:arrow_up:

...scala/io/circe/shapes/LabelledHListInstances.scala
96.29% <0.00%> (+3.70%)
:arrow_up:

...rc/main/scala/io/circe/shapes/SizedInstances.scala
92.85% <0.00%> (+14.28%)
:arrow_up:

Continue to review full report at Codecov.

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


Promise type annotations

I want to update the annotations with Promises to take a type parameter (like you're doing with Array).
Example:
https://github.com/AnalyticalGraphicsInc/cesium/blob/d880e17464355679f7ca39dde0fc0c8b80f5338f/Source/Core/TerrainData.js#L73
@returns {Promise|TerrainMesh}

Would be:
@returns {Promise.<TerrainMesh>}

Would this be accepted?
EDIT: I need this for the TS definition files I'm writing
EDIT 2: is this a better question for the mailing list?

As long as the documentation still builds, I don't see a problem with this change

TS definition file looks cool, are you generating that from the jsDoc or writing it by hand?  I unfortunately haven't had a lot of time to explore typescript, but I'm sure something like that would definitely be useful for many people.

@mramato I wrote a (very ugly) node.js script that generates it from the JSON output of jsdoc -X. Once I'm able to generate it without the compiler yelling at me (almost there) I want to run it against your tests. After that I'll add it to https://github.com/borisyankov/DefinitelyTyped

@icholy this seems cool.  Do you think this could / should eventually be added to Cesium's build/combine script, so that TypeScript definitions always keep up with new features?  I haven't played with TypeScript yet, I keep meaning to find time to look into it.

@emackey I wouldn't be against it (once it's fully automated). It could even be used as a way to enforce correct type annotations in the comments (to some extent at least).

@icholy Ah, I see someone else is also trying to make a (sorely needed) TypeScript definition for Cesium
I'm currently developing a JSDoc plugin to generate TypeScript definition files from parsed JSDoc doclets.
https://github.com/jumpinjackie/jsdoc-typescript-plugin
Initial focus is currently to automatically generate working TSD files for OpenLayers, but Cesium is also in my crosshairs.
Perhaps we could pool our efforts and knowledge together?

@icholy and @jumpinjackie I'm sure we'd be happy to ship an official TS definition file with Cesium if there's an easy way to automatically generate and validate it as part of our build process, so I'm all for this effort.

@mramato @jumpinjackie #2879 is my blocker

@mramato Do you have any new updates on Typescript definition file for Cesium?

André Staltz - All JS libraries should be authored in TypeScript
Check this Cesium Typescript generator made in C# 6.0... maybe you guys can use this as a base?

André Staltz - All JS libraries should be authored in TypeScript
@emackey @mramato Check this Cesium Typescript generator made in C# 6.0... maybe you guys can use this as a base?

Also looking to use Cesium with our Typescript project.  Having defined types for Cesium would be very useful.


OPEN PR - PLEASE DON'T MERGE TO MAIN YET

Restructured backend code following layered architecture

Closing PR


How are (x, y, z) coordinates of irises calculated when refine_landmarks = True?

Hi, thank you so much for maintaining this wonderful library :)
As the documentation says, we can use the attention mesh model by setting refine_landmarks = True. Moreover, when using the attention mesh model, we can obtain additional 10 points that represent (x, y, z) coordinates of irises as output. This means the shape of the final output is (468 + 10, 3).
However, it is unclear how (x, y, z) coordinates of the irises are calculated. I checked the output details of face_landmark_with_attention.tflite, but it contained only 20 values, although 10 * 3 = 30 values are required to calculate (x, y, z) coordinates of these 10 points.
These are the outputs of face_landmark_with_attention.tflite.  As you can see, Only 10 + 10 = 20 values are present.
{'name': 'output_left_iris',
  'index': 722,
  'shape': array([ 1,  1,  1, 10], dtype=int32),
  'shape_signature': array([ 1,  1,  1, 10], dtype=int32),
  'dtype': numpy.float32,
  'quantization': (0.0, 0),
  'quantization_parameters': {'scales': array([], dtype=float32),
   'zero_points': array([], dtype=int32),
   'quantized_dimension': 0},
  'sparsity_parameters': {}},
 {'name': 'output_right_iris',
  'index': 724,
  'shape': array([ 1,  1,  1, 10], dtype=int32),
  'shape_signature': array([ 1,  1,  1, 10], dtype=int32),
  'dtype': numpy.float32,
  'quantization': (0.0, 0),
  'quantization_parameters': {'scales': array([], dtype=float32),
   'zero_points': array([], dtype=int32),
   'quantized_dimension': 0},
  'sparsity_parameters': {}},

Is there anything I miss? I would be very happy if you could tell me the logic behind it. Thank you :)

I solved this issue by myself.
These 20 values represents (x, y) coordinates of irises.
z can be obtained by taking the average of z values of the landmarks that are present in mp.solutions.face_mesh.FACEMESH_LEFT_EYE and mp.solutions.face_mesh.FACEMESH_RIGHT_EYE.


Typo in recipe_ocean_Landschuetzer2016

Describe the bug
The standard recipe_ocean_Landschuetzer2016.yml has a typo in a file name that prevents running a model vs OBS diagnostics:' We should replace Landschutzer2016 with Landshuetzer2016 in the following line:
https://github.com/ESMValGroup/ESMValTool/blob/13b3c34c5e47c7feaf50d217cda993f8cc57268f/esmvaltool/recipes/recipe_ocean_Landschuetzer2016.yml#L133

thanks very much for raising this, and for fixing it so fast @TomasTorsvik - I have approved your PR and will merge as soon as the last test finishes running :+1:


After rejecting account address from ledger you have to reload the page to connect ledger

Add Button to ConnectGuide to restart ledger connection.

Introduced in #813


Missing test case coverage for include/misc/byteorder.h functions

According to LCOV, for include/misc/byteorder.h we only have 58.1% line coverage for this header file.
Need to create a testcase for these functions that prove that each one of them works with all conditional branches taken.

According to LCOV, for include/misc/byteorder.h we only have 58.1% line coverage for this header file.

this number is misleading, probably applies to usage coverage, not test coverage. I can only see two functions with tests.

Yeah, we don't have any explicit tests to prove that these APIs work.

afaik covered in tests/kernel/common/src/byteorder.c


Add the usernames of the service's creators

Currently we can't see who created a service. It would be better to include the service's creator too so people can see who created it without clicking the forum topic linked to it.

Good idea, I'll see what I can do. :)

Done on 2d12296.


Drop Emacs 25 support?

This version is currently available on stable Debian (buster). Furthermore there is also an official 27.1 backport now available in buster-backports. Both Consult and Embark already require 26.1. Some of the popular distributions like Doom even seem to move away from 26. See also https://www.gnu.org/software/emacs/history.html.

I also see no problems to drop it as soon as we have code which would need backward compatibility checks, for now it doesn't seem to harm to keep it or do you have something in mind?

Is Doom considering using Selectrum?

I also see no problems to drop it as soon as we have code which would need backward compatibility checks, for now it doesn't seem to harm to keep it or do you have something in mind?

Well, I drop support as soon as I cannot test it anymore without major effort. But I am not very conservative here, maybe @raxod502 wants to keep longer backward compatibility. I noticed when editing the Selectrum code, that I could not write certain things, e.g, when-let*. I am unsure which other incompatibilities are lurking somewhere else. In Consult I also had Emacs 26 related bugs (https://github.com/minad/consult/blob/9b078f5c981feefb3eab8648baf3047bf8aab33c/consult.el#L542). This particular bug I consider to be rather severe, even if the reason for the bug is trivial. If I find bugs like this I somehow lose the trust in the given version and have the urge to move on more quickly. Emacs 27 in contrast seems to be rock solid. I have found no problems with it, except this hook memory issue. But to be fair, this is not yet fixed in 28 and the bug has been present for a very long time.

Do you know if Doom is considering using Selectrum? I have heard there is some interest but I have no details.

Yes it is. See https://github.com/hlissner/doom-emacs/pull/4664. I am unsure about the opinion of the maintainers, but there are some interested folks, who already seem to be using it. I personally have not tried. But I am using my own config. I would still find it interesting how well everything works out in a more involved setting with many packages.

Great, I also haven't tried Doom but it seems certainly like a nice distribution. I also noticed the problem with when-let* in the past I agree that it would be nice to be able to use it.

I am unsure about the opinion of the maintainers ...

FWIW, he weighed in here, and so certainly seems open to it:
https://github.com/hlissner/doom-emacs/pull/4519#pullrequestreview-569776478

Regarding the Emacs 25 issue, I think it makes sense drop 25 as soon as we go on with the removal of the deprecated functionality present in 3.1. I am unsure when you want to make this cut in the master branch, maybe in a month or two to give people using Selectrum master time to adapt. Note that I did this superficial search on github for selectrum-read usage (#443) and fortunately not much turned up. The most serious one being amx probably, but I suppose the fix there will be merged soon.

Doom only supports 26.3+, so I don't think there is any trouble with that for dropping support for Emacs 25. I have no hard rule for when to drop support for an old version, although I think it is important to maintain support at least for the version of Emacs that is shipped with the most recent Ubuntu LTS release. Dropping support when it becomes inconvenient to maintain for whatever reason is reasonable.


Feat/frontierstiching

Add the "Frontier Stiching" watermark technique for PyTorch

Hello @sofianelounici! Thanks for opening this PR.

In the file mlmodelwatermarking/marktorch.py:

Line 257:40: E226 missing whitespace around arithmetic operator
Line 264:47: W291 trailing whitespace

Do see the Hitchhiker's guide to code style