Reintroduce fallback support for any POSIX-compatible shell

This was originally merged to main in @jhuntwork's PR #389, however for some reason it caused some of our GitHub Actions tests to fail. I've reverted the PR temporarily and am introducing it again on this branch to evaluate why the tests were failing.

Add fallback support for any POSIX-compatible shell

As a last resort before erroring, try to determine a 'config' or 'profile' file to use via a POSIX-specific test.
POSIX states regarding the ENV variable:

This variable, when and only when an interactive shell is invoked, shall be
subjected to parameter expansion (see Parameter Expansion) by the shell, and
the resulting value shall be used as a pathname of a file containing shell
commands to execute in the current environment. The file need not be
executable.

Motivation
My main shell is typically mksh. Even though it lacks many of the bells and whistles of bash and zsh, it is an adequate and comfortable interactive shell. By making all the common pieces POSIX-compliant, all the currently supported shells should continue to work and any additional shell that is POSIX-compliant should work as well.
This also requires some changes in the assume shim script. Even though some parts are zsh-specific and warnings can be ignored, the whole thing is sourced and so needs to be syntactically correct:

Replace '<<<' with a simple heredoc.
Replace the 'source' command with '.'
Use parameter substitution for testing the existence of substrings
Remove some other unnecessary bashisms
Minor tweak, but replace uses of echo with printf since that tends to be safer and more explicit in formatting. A good summary of the difference is here

change 'return' to 'exit'

Any chance this is because of the 'exit' instead of the 'return' ? As I understand it, the script is being sourced, which means if you call 'exit', you are actually exiting the parent shell that sources the script.
If you have any guidance on replicating these tests locally, I'd be happy to dig into the failure a bit too.

Any chance this is because of the 'exit' instead of the 'return' ? As I understand it, the script is being sourced, which means if you call 'exit', you are actually exiting the parent shell that sources the script.
If you have any guidance on replicating these tests locally, I'd be happy to dig into the failure a bit too.

Hmm, nope, nevermind, that would apply to functions. In the main body of a script that you source it would be effectively the same.

Here's a print of the relevant logs from GitHub Actions:
Run SHELL=/bin/bash dassume -auto-configure-shell
  SHELL=/bin/bash dassume -auto-configure-shell
  shell: /usr/bin/bash -e {0}
  env:
    TEST_ACCESS_KEY_ID: 1[2](https://github.com/common-fate/granted/actions/runs/4670007054/jobs/8269271951?pr=400#step:8:2)[3](https://github.com/common-fate/granted/actions/runs/4670007054/jobs/8269271951?pr=400#step:8:3)[4](https://github.com/common-fate/granted/actions/runs/4670007054/jobs/8269271951?pr=400#step:8:4)[5](https://github.com/common-fate/granted/actions/runs/4670007054/jobs/8269271951?pr=400#step:8:5)78910abcdefghij
    TEST_ACCESS_KEY:<PHONE_NUMBER>abcdefghijklmnopqrstuvwxyz1234
    TEST_REGION: ap-southeast-2

25l? Please select the profile you would like to assume:  [Use arrows to move, type to filter]
> test
25h[✘] EOF
Error: Process completed with exit code 1.

Usually the command assume -auto-configure-shell does not cause the interactive prompt to open. I am wondering if the changes in this PR caused the arguments to not be parsed properly anymore, so that the Go program is just receiving assume rather than assume -auto-configure-shell?

So I believe this is to do with my misreading of the initial code and not understanding the goal of the alias. The challenge is that POSIX doesn't define a way to determine if a script is being sourced or executed directly. bash provides the extra BASH_SOURCE variable as was used here before. And other shells have other mechanisms. It seems the easiest quasi-portable method is to account for how $0 is treated in different shells when the script is sourced.
Here's how that breaks down for 4 different shells:
Save this scriptlet as /usr/local/bin/dassume:
#!/bin/sh
# Check the type of the basename of "$0"
printf 'type of $0: %s\n' "$(type -- "${0##*/}")"
printf '$0: %s\n' "$0"

Then without the alias set up, notice the output in each of the following
bash
$ dassume
type of $0: dassume is /usr/local/bin/dassume
$0: /usr/local/bin/dassume

zsh
% dassume
type of $0: dassume is /usr/local/bin/dassume
$0: /usr/local/bin/dassume

mksh
$ dassume
type of $0: dassume is /usr/local/bin/dassume
$0: /usr/local/bin/dassume

dash
$ dassume
type of $0: dassume is /usr/local/bin/dassume
$0: /usr/local/bin/dassume

So far so good, all treat the direct script the same. Now let's set up the alias on each, running alias dassume='. /usr/local/bin/dassume' and then run the alias.
bash
$ dassume
-bash: type: -bash: not found
type of $0:
$0: -bash

zsh
% dassume
type of $0: dassume is an alias for . /usr/local/bin/dassume
$0: /usr/local/bin/dassume

mksh
$ dassume
type of $0: -mksh not found
$0: -mksh

dash
$ dassume
type of $0: --: not found
-dash: not found
$0: -dash

They all handle it slightly differently, but one thing to note is that $0 is usually the name of the login shell and the type command fails. Except for zsh. But in that case, the type command shows that the command is definitely an alias. I think the way to go is to either test for failure of the type command, or that the 'alias' keyword is present.
The following code catches the case correctly for all 4 shells:
#!/bin/sh
_this_type=$(type -- "${0##*/}" 2>&1)

# If the type test failed, this is probably a sourced
# file because $0 will be the login shell, e.g., -bash,
# and the output will typically contain 'not found'
# In the case of zsh, the output will contain the word 'alias'.

if [ "${_this_type#*not found}" != "$_this_type" ] ||
        [ "${_this_type#*alias}" != "$_this_type" ]; then
    printf 'This file was sourced\n'
else
    printf 'This file was executed directly\n'
fi

I think https://github.com/common-fate/granted/pull/438 fixes the issues with this code. I see that this also needs to be rebased and have its conflicts fixed. Would you like me to do that or how do you want to proceed?

I ended up rebasing #438. I think that has everything needed there, and if we accept that one, this one can be closed.


Container doesn't resolve properties of already built instances after their state reset

What steps will reproduce the problem?
Run yiisoft/demo via RR(yiisoft/yii-runner-roadrunner)
1st request is handled properly, after which StateResetter::reset() is invoked
in subsequent requests container returns instances with unresolved properties
Example for subsequent requests:
What is the expected result?

What do you get instead?

Additional info

Q
A

Version
1.1.0

PHP version
8.1.2

Operating system
Ubuntu 22.04

Seems, problem here.
On first request container parse definitions and convert their to objects, but on reset this is not happening.

as a temporary solution for anyone who's running demo app on RR, amend reset:
'reset' => function (\Psr\Container\ContainerInterface $container) use ($params) {
    /** @var WebView $this */
    $this->clear();

    $resolvedParams = [];
    foreach ($params['yiisoft/view']['parameters'] as $id => $value) {
        $resolvedParams[$id] = $value instanceof \Yiisoft\Definitions\Reference ? $value->resolve($container) : $value;
    }
    $this->setParameters($resolvedParams);
}


flit-core: add comment explaining where deps are listed

Closes #482
@takluyver @pradyunsg

Thanks! Just to be clear, the requires list under [build-system] is a list of build dependencies, which should be empty - flit_core builds itself with no dependencies. It's the [project] table, which would contain runtime dependencies, which is completely absent.


Change: Loading State & Error Handling for TimeRangeSelect

Description
Allows the <TimeRangeSelect /> component to listen in on errors and report whether or not a successful Longview stats request happened.
What's New?

The handleStatsChange prop is now typed as a function that returns a Promise. a la (start: number, end: number) => Promise<any>

This will let it hook into the .catch and revert back to the original select option if the request fails

New handleFetchError prop which is a function that returns an error. The parent component then can decide what it wants to do with it (show a toast, swallow the error, etc.)
Select value is now loading... and disabled when the request is in-flight
All stats are coming from 1 request once again 😢

Type of Change

Non breaking change ('update', 'change')

What's the Alternative To This Approach?
If we don't want to go with this option, the other approach would be just to add error handling to each graph and toast for any failed errors.
The drawback here is that the select value might not accurately reflect what data is being shown in the graphs, but we get more simplicity and no need to make one batch request as a pro - we can continue making individual requests per graph.

Closing in favor of https://github.com/linode/manager/pull/5970.


[CI] Use inputs for actions to enforce correct use

[x] First merge #368

setup action:
Making the inputs optional and checking if they are set before using them allows to set up less when not needed.
An example is the compilation test.

summary action:
Using env was hard to follow and required comments in the action what was required for that action to work.

delivery workflow:
Split up delivery workflow into 2 jobs.
Using jobs for controling the flow is better GitHub Actions practice than constant if checks.

Solved the conflicts, not significant at all. Nothing different now, no need for you to check everything again.


Web-ui: favicon is absent.

As Zally user
I want to see pretty favicon in my browser while checking my API with Zally

Implemented in #517 , thanks @topicus


Add Backend Protocol Section to implementators guide

Comment: https://github.com/kubernetes-sigs/gateway-api/pull/2444#discussion_r1346610836

/assign @youngnick

Hmm, I had forgotten about this. The implementer's guide has now been, well, implemented, and is ready for someone to take the table that's currently in GEP-1911 (at https://gateway-api.sigs.k8s.io/geps/gep-1911/#supporting-protocols) and add a section that:

explains that backend protocol selection exists
links to the user guide (https://gateway-api.sigs.k8s.io/guides/backend-protocol/)
includes the table from https://gateway-api.sigs.k8s.io/geps/gep-1911/#supporting-protocols with the expected support for backend protocol selection.

This is a reasonably straightforward documentation fix that is suitable for a new contributor.
/help
/good-first-issue
/remove-lifecycle stale

/unassign

/assign @dprotaso

/assign @joerober

/assign @joerober


rtmpdump exited with code 1 when downloading canvas.be

Please follow the guide below

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

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

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

Before submitting an issue make sure you have:

[x] At least skimmed through README and most notably FAQ and BUGS sections
[x ] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

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

youtube-dl -v -fmp4 https://www.canvas.be/video/get-ripped-12
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'-v', u'-fmp4', u'https://www.canvas.be/video/get-ripped-12']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2016.12.12
[debug] Python version 2.7.1 - Darwin-11.4.2-x86_64-i386-64bit
[debug] exe versions: ffmpeg 2.8.3, ffprobe 2.8.3, rtmpdump 2.4
[debug] Proxy map: {}
[Canvas] get-ripped-12: Downloading webpage
[Canvas] get-ripped-12: Downloading JSON metadata
[Canvas] get-ripped-12: Downloading m3u8 information
WARNING: Failed to download m3u8 information: <urlopen error [Errno 1] _ssl.c:499: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol>
[Canvas] get-ripped-12: Downloading f4m manifest
[debug] Invoking downloader on u'rtmp://vod.stream.vrt.be/mediazone_canvas_geo/_definst_/mp4:2016/12/mz-ast-f508fec3-47c2-487e-b801-491013dded3d-2/video_1296.mp4'
[download] Destination: Get ripped-mz-ast-f508fec3-47c2-487e-b801-491013dded3d.mp4
[debug] rtmpdump command line: rtmpdump --verbose -r rtmp://vod.stream.vrt.be/mediazone_canvas_geo/_definst_/mp4:2016/12/mz-ast-f508fec3-47c2-487e-b801-491013dded3d-2/video_1296.mp4 -o 'Get ripped-mz-ast-f508fec3-47c2-487e-b801-491013dded3d.mp4.part' --resume --skip 1
[rtmpdump] RTMPDump v2.4
[rtmpdump] (c) 2010 Andrej Stepanchuk, Howard Chu, The Flvstreamer Team; license: GPL
[rtmpdump] DEBUG: Parsing...
[rtmpdump] DEBUG: Parsed protocol: 0
[rtmpdump] DEBUG: Parsed host    : vod.stream.vrt.be
[rtmpdump] DEBUG: Parsed app     : mediazone_canvas_geo/_definst_/mp4:2016
[rtmpdump] DEBUG: Number of skipped key frames for resume: 1
[rtmpdump] DEBUG: Protocol : RTMP
[rtmpdump] DEBUG: Hostname : vod.stream.vrt.be
[rtmpdump] DEBUG: Port     : 1935
[rtmpdump] DEBUG: Playpath : mp4:12/mz-ast-f508fec3-47c2-487e-b801-491013dded3d-2/video_1296
[rtmpdump] DEBUG: tcUrl    : rtmp://vod.stream.vrt.be:1935/mediazone_canvas_geo/_definst_/mp4:2016
[rtmpdump] DEBUG: app      : mediazone_canvas_geo/_definst_/mp4:2016
[rtmpdump] DEBUG: live     : no
[rtmpdump] DEBUG: timeout  : 30 sec
[rtmpdump] DEBUG: Failed to get last keyframe.
[rtmpdump] DEBUG: Closing connection.
[rtmpdump] 0 bytes
[rtmpdump] RTMPDump v2.4
[rtmpdump] (c) 2010 Andrej Stepanchuk, Howard Chu, The Flvstreamer Team; license: GPL
[rtmpdump] DEBUG: Parsing...
[rtmpdump] DEBUG: Parsed protocol: 0
[rtmpdump] DEBUG: Parsed host    : vod.stream.vrt.be
[rtmpdump] DEBUG: Parsed app     : mediazone_canvas_geo/_definst_/mp4:2016
[rtmpdump] DEBUG: Number of skipped key frames for resume: 1
[rtmpdump] DEBUG: Number of skipped key frames for resume: 1
[rtmpdump] DEBUG: Protocol : RTMP
[rtmpdump] DEBUG: Hostname : vod.stream.vrt.be
[rtmpdump] DEBUG: Port     : 1935
[rtmpdump] DEBUG: Playpath : mp4:12/mz-ast-f508fec3-47c2-487e-b801-491013dded3d-2/video_1296
[rtmpdump] DEBUG: tcUrl    : rtmp://vod.stream.vrt.be:1935/mediazone_canvas_geo/_definst_/mp4:2016
[rtmpdump] DEBUG: app      : mediazone_canvas_geo/_definst_/mp4:2016
[rtmpdump] DEBUG: live     : no
[rtmpdump] DEBUG: timeout  : 30 sec
[rtmpdump] DEBUG: Failed to get last keyframe.
[rtmpdump] DEBUG: Closing connection.

ERROR: rtmpdump exited with code 1
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/runpy.py", line 162, in _run_module_as_main
    "__main__", fname, loader, pkg_name)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/runpy.py", line 72, in _run_code
    exec code in run_globals
  File "/usr/local/bin/youtube-dl/__main__.py", line 19, in <module>
    youtube_dl.main()
  File "/usr/local/bin/youtube-dl/youtube_dl/__init__.py", line 444, in main
    _real_main(argv)
  File "/usr/local/bin/youtube-dl/youtube_dl/__init__.py", line 434, in _real_main
    retcode = ydl.download(all_urls)
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 1791, in download
    url, force_generic_extractor=self.params.get('force_generic_extractor', False))
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 705, in extract_info
    return self.process_ie_result(ie_result, download, extra_info)
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 751, in process_ie_result
    return self.process_video_result(ie_result, download=download)
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 1435, in process_video_result
    self.process_info(new_info)
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 1699, in process_info
    success = dl(filename, info_dict)
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 1641, in dl
    return fd.download(name, info)
  File "/usr/local/bin/youtube-dl/youtube_dl/downloader/common.py", line 353, in download
    return self.real_download(filename, info_dict)
  File "/usr/local/bin/youtube-dl/youtube_dl/downloader/rtmp.py", line 202, in real_download
    self.report_error('rtmpdump exited with code %d' % retval)
  File "/usr/local/bin/youtube-dl/youtube_dl/downloader/common.py", line 162, in report_error
    self.ydl.report_error(*args, **kargs)
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 568, in report_error
    self.trouble(error_message, tb)
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 530, in trouble
    tb_data = traceback.format_list(traceback.extract_stack())

error message 'rtmpdump exited with code 1' when downloading https://www.canvas.be/video/get-ripped-12. Same error with other canvas urls, but not all. Please note I'm not very familiar with Terminal.
 $ youtube-dl -fmp4 https://www.canvas.be/video/get-ripped-12
[Canvas] get-ripped-12: Downloading webpage
[Canvas] get-ripped-12: Downloading JSON metadata
[Canvas] get-ripped-12: Downloading m3u8 information
WARNING: Failed to download m3u8 information: <urlopen error [Errno 1] _ssl.c:499: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol>
[Canvas] get-ripped-12: Downloading f4m manifest
[download] Destination: Get ripped-mz-ast-f508fec3-47c2-487e-b801-491013dded3d.mp4
[rtmpdump] 0 bytes

ERROR: rtmpdump exited with code 1

The proposed URL https://www.canvas.be/video/get-ripped-12 is no longer available, so it will be impossible to reproduce this error. I suggest to close this report.


Allow facilities with inactive matches to be deleted

Overview
When adding the ability to remove a FacilityListItem, which makes its related
FacilityMatch row inactive, we accidentally broke the ability to delete
facilities created from these inactive items.
Connects #628
Testing Instructions

Reset the database

./scripts/manage resetdb
./scripts/manage loadfixtures
./scripts/manage processfixtures

Log in as<EMAIL_ADDRESS>Browse http://localhost:6543/lists/8
Search for atlantis and remove the item
Browse localhost:6543, search for atlantis and copy the OAR ID.
Log in as<EMAIL_ADDRESS>browse https://localhost:6543/dashboard/deletefacility, and verify that you can successfully delete the facility

Checklist

[x] fixup! commits have been squashed
[x] CI passes after rebase
[x] ~CHANGELOG.md updated with summary of features or fixes, following Keep a Changelog guidelines~ Skipped because this is a fix to a new unreleased feature

Thanks for the review.


Simplify type system

Sum types - OR
there is ONE way how to define:
type
Product types - AND
there are MANY ways:
()
(a, b)
(a, b, c)
{ x: a, y: b }
type A = A a b
Let's simplify it
If I want OR I use type and |.

So
remove tuples
unit is {}
variant has only one argument
{ model, Cmd.none } is the same as { a: model, b: Cmd.none }

Sorry, 👎 to breaking changes from me.

why would we do this and break practically every elm package.


Links to external socials

We should probably include links and CTAs for joining the discord and the maillist

A homepage section for this could be cool, titled "Get Involved" or similar with pretty CTAs for Discord, mailing list etc


Bag broken

Addon Version
v0.3.9
World of Warcraft Version
Retail
Describe the bug
Bag shows no items, and it is compressed. All I can see is the currency but they're on top of each other.
6x BetterBags/core/async.lua:49: Blizzard_ObjectAPI/Mainline/Item.lua:121: bad argument #1 to 'GetItemGUID' (Usage: local itemGUID = C_Item.GetItemGUID(itemLocation))
[string "=[C]"]: in function error' [string "@BetterBags/core/async.lua"]:49: in function worker'
[string "@BetterBags/core/async.lua"]:65: in function DoWithDelay' [string "@BetterBags/core/async.lua"]:74: in function Do'
[string "@BetterBags/core/async.lua"]:102: in function Batch' [string "@BetterBags/data/loader.lua"]:111: in function Load'
[string "@BetterBags/data/items.lua"]:799: in function ProcessContainer' [string "@BetterBags/data/items.lua"]:515: in function RefreshBackpack'
[string "@BetterBags/data/refresh.lua"]:144: in function StartUpdate' [string "@BetterBags/data/refresh.lua"]:227: in function cb'
[string "@BetterBags/core/events.lua"]:49: in function <BetterBags/core/events.lua:47>
[string "=[C]"]: ?
Steps to reproduce
Just opening the bag

This is a known issue currently. Revert to v0.3.7 for now.


feat(all): Test doc upload with travis

Coverage decreased (-20.4%) to 64.144% when pulling 9ecfca17f292725c89a88085852f303d4aaff27b on amousset:test-travis into d967bbb12638f8dc5ad9c2df5c55b6d003eff817 on lettre:master.

Coverage decreased (-20.4%) to 64.144% when pulling f57279bdb70f22e3bee9e2a3f12d3e32a8903637 on amousset:test-travis into d967bbb12638f8dc5ad9c2df5c55b6d003eff817 on lettre:master.


Navigation between assets using browser buttons

This pull requests adds the ability to navigate through the M365 learning pathways viewer webpart using the browser's navigation buttons (Back and Forward buttons).
It adds two new properties to the property pane:

Change browser URL when navigating between assets - toggle, this property is off by default. When disabled, the behaviour of M365 Learning Pathways doesn't change. When enabled, navigating between categories, playlists and assets will change the URL in the browser and make the Back and Forward buttons functional.
URL of the default viewer page - text, this property is empty by default. As of now, when generating links to pages, it is assumed that the viewer page is located on the page under the URL of {M365LPPortal}/SitePages/CustomLearningViewer.aspx. This property allows administrators to provide a different URL, effectively enabling them to rename the page without breaking the portal.

Providing the ability to both rename the viewer page (e.g. to simpler names such as Learning.aspx) and to navigate through the portal using the browser's navigation buttons greatly improves the end-user experience, eliminating the problem of navigating off the page by mistake.

@juliemturner @dcashpeterson Hi! When you have a moment, could you please look at the changes I proposed? I think they greatly improve the experience of navigating between the articles in the Learning Pathways.

@Szab I will look at this when I have time to process PRs. Thank you for the submission.

@dcashpeterson Sorry for pinging but can I ask for a review sometime?

@Szab sorry for the delay on this. We are actually in process of updating the HTML and CSS on the webpart to make it more accessible. I will let the development team know about this PR.


Fix spelling

have to test cod -> code

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

ID: 59d3d423-7069-b03e-cc30-0facb8ab8a9f
Version Independent ID: e00f9545-4c96-7e52-915a-b1bd5cdbcfdc
Content: Progressive Experimentation with Feature Flags - Azure DevOps
Content Source: https://mseng.visualstudio.com/DefaultCollection/TechnicalContent/_git/devops-learn-pr?path=%2fdocs%2fdevops-at-microsoft%2fprogressive-experimentation-feature-flags.md&version=GBlive&_a=contents
Product: devops
Git Login: samgu
Microsoft Alias: buckh

@jawn Thanks for letting us know, I'm fixing this right now and it should be live soon.


replicate.gr fails with unbound variable error

Running gr -t frontend/tests/regression/good/replicate.gr fails with an unbound variable error (succ is not in scope).
Are we supposed to be importing succ from somewhere, or should we just define it in the module?

I've noticed and fixed this in my PR, which should be merged tonight.


Addinng NodeJS tutorial for code-interpreter sessions

Addinng NodeJS tutorial for code-interpreter sessions

@v-jaswel @craigshoemaker - can one of you take a look at this new article submission and review it?
@IshitaAsthana - for a new article to be accepted, a Microsoft content professional must take ownership and work with you to get it published on the Learn site.
NOTE: if this is approved / accepted, the commits from this PR will need to be moved to the private repo for a full review with staging and Acrolinx. @craigshoemaker @v-jaswel - can you do this?  let us know if you'd like our assitance.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@IshitaAsthana Thank you very much for your contribution! I've created a work item to track this and we will try to review it as soon as we can.


Update Kubernetes image

This pulls in some new OS packages that Shameema had me install for some newer versions of modules that will be needed to run those modules, I think mostly RStudio.

Forgot to add that the image has been pre-pulled to all worker nodes in test and production clusters so there won't be a pod delay for first user to use each image on a node.

I take it this needs to be released soon (today?).

This might not be needed depending on if Shameema needs the new OS packages for new RStudio installs.

So I had to add a new bug fix to the images where the UID/GID of slurm user was incorrect, so the version now in this PR incorporates that bug fix.  I think the incorrect UID/GID would likely just cause issues interacting with SLURM (ie submit job) from within the pod.  That was at least the issue ZQ was having when using this image with Singularity.
Same change was made to https://github.com/OSC/bc_osc_rstudio_server/pull/81

So is this ready to be pulled in then?

Not yet, the image itself is still building (takes a couple hours) and I would like ZQ to verify the bug fix works for him.  Once the image is built and ZQ verifies I would also need to pre-pull the image on worker nodes, but that can just be done before we tag a new release but will likely be done today I hope.

ZQ confirmed this latest image solved his problems, and I've pulled this latest image down to all Kubernetes worker nodes.  So I think this and https://github.com/OSC/bc_osc_rstudio_server/pull/81 are ready.

cool, when do you want it released? ++@ZQyou

I am not using this image for classroom. It can be released anytime.


Added pkgbuild for v1.0.0

Added an AUR package here and created PKGBUILD. Adding it here for upstream tracking as well.

Just FYI, there's no formal release process so it might be an idea to track master rather than specific versions. v1.0 was more a way of saying 'this interface should not change' rather than any kind of feature completeness.
Release schedule etc. is completely up for discussion, just raise an issue if the current way of doing things doesn't work for packaging etc..

Thanks for your inputs Nat, I thought of hooking up straight from master but in that case, the SHA sum would have to get updated by every contributor. That's bit of an overhead and introduces extra complexity.
Also, it's a common pattern to have AUR PKGBUDs targeting released tarballs.


Tune job locking period

increased job locked time as error count increases
don't force retry failed jobs on each startup

Updated with further tuning, PTAL. Deploying in staging for further monitoring.


Not bundled all the javascript in one binary file distribution

I think that it's a good idea to have 2 kind of distributions.  The current distribution: all bundled in one  binary file. And the not bundled all distribution: the binary file for execution separated from the javascript  files  used by phantomjs (not all is bundled in the same binary). With this other approach is much more easy to hack phantomjs without any compilation step. On linux it's very easy to compile. But on windows is very painful. And at the same time its much more easy to test new ideas and get a feedback because the compilation is very long.

Implementing this is a major undertaking and currently beyond the scope of the project.
You are however free to work on it on your own or sponsor someone to implement it. Once it is in a state where we can consider it for inclusion, please reopen this issue and submit a pull request of the implementation. Thank you!


On deselcting element from drodown removing it from actual option array.

I tried to make a plunkr from the demo page. It doesn't looks working. On deselecting array it removes that array element from the actual array of controller scope variable.
Plunkr Here

In your plunker selected-model and options are the same array


Protect numbering of the agenda

Looks good. One remark. And add Changelog entry please.

rebased

Ok, but this is also something that might be solved with a settings variable to spare some cockpit config buttons.


[discussion] feat: configuration trait

This draft PR serves as an helper to discuss the changes required to develop feature #2320.

Right now a property file or other resources attached to an Integration, are materialized via deployment, cron or knative_service traits. If we introduce the configuration trait we can let this take care of this aspect, although I am not entirely sure if this will have some drawback I am not able to see at the moment (see the changes proposed). It basically means moving the logic that is taking care of it (e.computeConfigmaps()) from the 3 trait into the other one. We are introducing some trait dependency (to configuration trait), but I don't see this a big concern.

If we're happy with point 1, then we'll need to start moving the logic that is happening now in the e.computeConfigmaps() directly in the configuration trait. As an example, in this PR you will see I've done this with the Properties parameter which is going to take care of the user properties.

What was done here with Properties will have to be extended with all the other user configuration such as config, resource, ... It seems doable with no big concerns either.

ConfigurationSpec is widely used in Integration, IntegrationKit and only in one case in IntegrationPlatform. If we proceed with this design change we may be in the situation to extend the trait to the kit as well. Or we can keep it in the kit and the platform and just remove from the integration spec only.

The backward compatibility is something we will have to take case as well. I think we can find some way to let both approach (integration.spec.configspec and configuration trait) coexist, deprecating the first and eventually remove it.

It does not look an easy development as there are several dependencies to the ConfigurationSpec. In any case, with the approach proposed we will be able to have all in a unique place, although it means we will depends on a trait. With the changes proposed here I manage to make an integration work seamlessly.
@astefanutti, @lburgazzoli you were involved in the past in this discussion, I'll gladly receive your feedback to confirm if the approach is fine and it's worth to keep ahead with this.
CC @nicolaferraro @oscerd @doru1004 @jamesnetherton @johnpoth @tadayosi @orpiske @davsclaus, happy if you can have a look as well.

Release Note
NONE

1. Right now a property file or other resources attached to an `Integration`, are materialized via `deployment`, `cron` or `knative_service` traits. If we introduce the `configuration` trait we can let this take care of this aspect, although I am not entirely sure if this will have some drawback I am not able to see at the moment (see the changes proposed). It basically means moving the logic that is taking care of it (`e.computeConfigmaps()`) from the 3 trait into the other one. We are introducing some trait dependency (to `configuration` trait), but I don't see this a big concern.

2. If we're happy with point 1, then we'll need to start moving the logic that is happening now in the `e.computeConfigmaps()` directly in the configuration trait. As an example, in this PR you will see I've done this with the `Properties` parameter which is going to take care of the user properties.

3. What was done here with `Properties` will have to be extended with all the other user configuration such as `config`, `resource`, ... It seems doable with no big concerns either.

I think that implementing those points is a good opportunity to cleanup the code and make it more consistent so +1 with me

4. `ConfigurationSpec` is widely used in `Integration`, `IntegrationKit` and only in one case in `IntegrationPlatform`. If we proceed with this design change we may be in the situation to extend the trait to the kit as well. Or we can keep it in the kit and the platform and just remove from the integration spec only.

This point is not super clear to me, in particular the reason to remove the trait from the integration.

5. The backward compatibility is something we will have to take case as well. I think we can find some way to let both approach (`integration.spec.configspec` and `configuration` trait) coexist, deprecating the first and eventually remove it.

I think that trait.Configure for the configuration trait, should by default attempt to converting the .spec.config to its own structure so we can support the two mode for some time but we would swich to the trait internally

Thanks Luca, some clarification inline:

1. Right now a property file or other resources attached to an `Integration`, are materialized via `deployment`, `cron` or `knative_service` traits. If we introduce the `configuration` trait we can let this take care of this aspect, although I am not entirely sure if this will have some drawback I am not able to see at the moment (see the changes proposed). It basically means moving the logic that is taking care of it (`e.computeConfigmaps()`) from the 3 trait into the other one. We are introducing some trait dependency (to `configuration` trait), but I don't see this a big concern.

2. If we're happy with point 1, then we'll need to start moving the logic that is happening now in the `e.computeConfigmaps()` directly in the configuration trait. As an example, in this PR you will see I've done this with the `Properties` parameter which is going to take care of the user properties.

3. What was done here with `Properties` will have to be extended with all the other user configuration such as `config`, `resource`, ... It seems doable with no big concerns either.

I think that implementing those points is a good opportunity to cleanup the code and make it more consistent so +1 with me

4. `ConfigurationSpec` is widely used in `Integration`, `IntegrationKit` and only in one case in `IntegrationPlatform`. If we proceed with this design change we may be in the situation to extend the trait to the kit as well. Or we can keep it in the kit and the platform and just remove from the integration spec only.

This point is not super clear to me, in particular the reason to remove the trait from the integration.

I did not explain properly. I was meaning that, as soon as we go deep in the development, we may be in the opportunity to apply the same mechanics used in the new configuration trait also for the ConfigurationSpec now hold by the IntegrationKit. In any case it's too early to say. I will come back on this point if it needs further discussion.

5. The backward compatibility is something we will have to take case as well. I think we can find some way to let both approach (`integration.spec.configspec` and `configuration` trait) coexist, deprecating the first and eventually remove it.

I think that trait.Configure for the configuration trait, should by default attempt to converting the .spec.config to its own structure so we can support the two mode for some time but we would swich to the trait internally

It's a good approach. I was thinking about maintaining temporarily the repeated logic (ie, e.computeConfigmaps() + the new logic), though I don't like repeated code. I will apply your suggestion as it looks cleaner.

I think those are good points and I don't really have anything to add to them right now. I do have a comment about the following:

5. The backward compatibility is something we will have to take case as well. I think we can find some way to let both approach (`integration.spec.configspec` and `configuration` trait) coexist, deprecating the first and eventually remove it.

I think that trait.Configure for the configuration trait, should by default attempt to converting the .spec.config to its own structure so we can support the two mode for some time but we would swich to the trait internally

+1. I don't really worry with the specifics of the technical implementation at this point, but I think we should aim for a solution that allows seamless migration from one to another from the user perspective.

Superseded by #2635


Feat UI reborn

一些样式调整和增加了一个文档站，作为后期组件统一维护和沟通的起点，替代原先的demo站
后期todo:

会和原先的go docs的docs整合在一起，并且提供现成的例子，让go这边直接可以拷贝可用代码
为每个组件提供详细的配置和demo演示
增加playground,可以实时预览和调试
与设计稿同步

PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.


Translate: Custom PhysicsMaterial properties

Unity-Mithril : SurfaceFilter
Not sure if this needs translation. I can't easily determine if Godot does or does not support customizable PhysicsMaterials. Please conduct further research.

Step One: Learn how to create custom resources in C#

Godot does support custom PhysicsMaterials in the same way that Unreal does. Good job!


Cannot use multiple instances of the editor

Hi!
When you click on a toolbar button, it impacts the content of all editors instead of only doing it on the corresponding editor.
<template>
  <md-editor v-model="text" />
  <md-editor v-model="text2" />
  <md-editor v-model="text3"  />
  <md-editor v-model="text4" />
</template>

<script>
import { defineComponent } from "vue";
import MdEditor from "md-editor-v3";
import "md-editor-v3/lib/style.css";

export default defineComponent({
  name: "App",
  components: {
    MdEditor,
  },
  data() {
    return {
      text:
        "Select me and click on the button to put me in bold. All other editors are also impacted. For me the button is invisible on codesandbox.io: it is the one in 1st position",
      text2: "2",
      text3: "3",
      text4: "4",
    };
  }
});
</script>

Demo:
https://codesandbox.io/s/example-of-md-editor-v3-forked-2nbd8p?from-embed=&file=/src/App.vue

To fix it, set different editorId for editor

It works
Could we have a clearer indication in the docs that this property MUST be filled in (and can be indicated at the top of the list of props or in the Usage part)?
Thank you for the quick reply

I'm thinking about how to show analogous problems, intuitively.
Thanks for your suggestion.


Add flow config, flow definitions for Emitter and Utils

Adds Flow. Starts preliminary flow types for Emitter and the utilities.

Codecov Report

Merging #315 into master will not change coverage.
The diff coverage is 100%.

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

I'm going to close this out for now. Let's get jsdoc in place, then let's take a pass with flow.


Bicep.Core.Syntax.SkippedTriviaSyntax when referencing inside a bicepparam file

Bicep version
0.23.1
Describe the bug
When referencing a parameter in another parameter in a bicepparam file i get the following error:
Bicep.Core.Syntax.SkippedTriviaSyntax
To Reproduce

I have a file main.bicep with the following content:

param rgs  { *: rg }

param vnets {*: vnet}

type rg = {
  name: string
  location: string
  tags: {}?
}

type vnet = {
  name: string
  resourceGroupName: string
  tags: {}?
}

I have a file params.bicepparam with the following content:

using 'main.bicep'

param rgs = {
    '0': {
      name: 'rg-test-1'
      location:'westeurope'
    }
    '1': {
      name: 'rg-test-2'
      location:'westeurope'
    }
}

param vnets = {
    0: {
      resourceGroupName: rgs['0'].name
    }
    1: {
      resourceGroupName: rgs['1'].name
    }
}

This gives me the error
Failed to convert syntax of type Bicep.Core.Syntax.SkippedTriviaSyntax(Fatal)

If I however remove the reference in the vnets param and declare it as a hardcoded string, it works.
I have also noticed in this case that the autocomplete only works partly:

If I reference using rgs.0. I only get name and tags.
If i reference using rgs['0']. I get name, tags and location

PS: Is there any way to reference the key of a hashtable/dictionary inside the bicepparam file, then I can move the "name" property to the key instead of a value. However if I use items (which clutters the file a lot), there's no autocomplete.
Say I want to reference the rg-test-1 value in a resource, is there any other way except items(rgs)[0].key
param rgs = {
    'rg-test-1': {
      location:'westeurope'
    }
}

Generally, the other question I have is - have you looked into using an array rather than a dictionary? Given that you're using integers for the keys, it feels like an array would simplify the code - e.g.:
using 'main.bicep'

param rgs = [
  {
    name: 'rg-test-1'
    location: 'westeurope'
  }
  {
    name: 'rg-test-2'
    location: 'westeurope'
  }
]

param vnets = [
  {
    resourceGroupName: rgs[0].name
  }
  {
    resourceGroupName: rgs[1].name
  }
]

Bicep file:
param rgs rg[]

param vnets vnet[]
...

using 'main.bicep'

param rgs = {
    'rg-test-1': {
      location:'westeurope'
    }
    'rg-test-2': {
      location:'westeurope'
    }
}

param vnets = {
    'vnet-test-1': {
      resourceGroupName: items(rgs)[0].key
    }
    'vnet-test-2': {
      resourceGroupName:  items(rgs)[1].key
    }
}

Is there any prettier way to solve referencing the key of the hashmap?
In an ideal world what I would love to be able to do is the following:
using 'main.bicep'

param rgs = {
  'rg-test-1': {
      location:'westeurope'
    }
    'rg-test-2': {
      location:'westeurope'
    }
}

param vnets = {
    'vnet-test-1': {
      resourceGroupName: rgs['rg-test-1'].key
      location: rgs['rg-test-1'].location
    }
    'vnet-test-2': {
      resourceGroupName: rgs['rg-test-2'].key
      location: rgs['rg-test-2'].location
    }
}

And if possible have autocomplete to show the available keys, because at the moment autocomplete doesn't work in this case (to select the correct key, so suggest 'rg-test-1' and 'rg-test-2' in this case)

Is there any prettier way to solve referencing the key of the hashmap?

I don't believe so. I would also be extremely careful using items() there - hashmaps are unordered, so there's no guarantee that [0] or [1] will actually return the item you expect it to.
If you're using arrays, this becomes simpler:
param rgs = [
  {
    name: 'rg-test-1'
    location: 'westeurope'
  }
  {
    name: 'rg-test-2'
    location: 'westeurope'
  }
]

param vnets = [
  {
    name: 'vnet-test-1'
    resourceGroupName: rgs[0].name
    location: rgs[0].location
  }
  {
    name: 'vnet-test-2'
    resourceGroupName: rgs[1].name
    location: rgs[1].location
  }
]

Or you could potentially refactor to:
var rgTest1 = {
  name: 'rg-test-1'
  location: 'westeurope'
}

var rgTest2 = {
  name: 'rg-test-2'
  location: 'westeurope'
}

param rgs = [ rgTest1, rgTest2 ]

param vnets = [
  {
    name: 'vnet-test-1'
    resourceGroupName: rgTest1.name
    location: rgTest1.location
  }
  {
    name: 'vnet-test-2'
    resourceGroupName: rgTest2.name
    location: rgTest2.location
  }
]

Should I make a feature request to be able to refernece the key of the hashtable, or is this simply impossible to implement this?


[Typo]: In code example of server actions

Summary
In Composing Server Actions with Actions:

"use client";

import {updateName} from './actions';

function UpdateName() {
  const [name, setName] = useState('');
  const [error, setError] = useState(null);

  const [isPending, startTransition] = useTransition();

  const submitAction = async () => {
    startTransition(async () => {
      const {error} = await updateName(name);
      if (!error) {
        setError(error);
      } else {
        setName('');
      }
    })
  }

  return (
    <form action={submitAction}>
      <input type="text" name="name" disabled={isPending}/>
      {state.error && Failed: {state.error}}
    </form>
  )
}

There is no state variable here.
It should be this
    <form action={submitAction}>
      <input type="text" name="name" disabled={isPending}/>
      {error && Failed: {error}}
    </form>

Page
https://react.dev/reference/rsc/server-actions#composing-server-actions-with-actions
Details
No response

hello,
is it valid?

I came here to create an issue for the same code, but we already have one. I know the example is kind of pseudo-code (we are not controlling the input, there is no submit button, etc.), but even with this, it should be error-free, I guess. There is one more mistake apart from state.error, which is
if (!error) {
  setError(error);
...

it should be
if (error) {
  setError(error);
...


Example::class results in mis-parsing

fun foo() {
    val x  = Bar::class
    val y = hello
}

See that the second line of foo() is mis-highlighted.

This hopefully fixed in #20.


git-get: init at version 0.5.0

Description of changes

Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 198411 run on x86_64-linux 1

1 package built:

git-get

Superseded by https://github.com/NixOS/nixpkgs/pull/216516


How to host web client as website not in local host

Version of the software
Nill
Operating system
Nill
Browser / Native
Nilll
What happened?
How to host web client as website not in local host
Relevant LoliCode if needed
No response

Use the OB2 docker (check this post) and just follow any guide that shows you how to set up a linux server to host a website. You will need a domain, a server, apache/nginx as reverse proxy flipping your traffic to your docker container, and a TLS certificate (use certbot). You can find all of this information online.


[QA] Check command-line arguments for test runner

Before this change, if you made a typo such as -parellel-8 when trying to run tests, you'd get a backtrace that's difficult to interpret. With this change, you'll get a better error message and a non-zero exit code.

Works for me.
Before:
~/Downloads/dogecoin/qa/pull-tester$ python rpc-tests.py -parellel=10
Traceback (most recent call last):
  File "/home/anthony/Downloads/dogecoin/qa/pull-tester/rpc-tests.py", line 390, in <module>
    runtests()
  File "/home/anthony/Downloads/dogecoin/qa/pull-tester/rpc-tests.py", line 242, in runtests
    max_len_name = len(max(test_list, key=len))
ValueError: max() arg is an empty sequence

After:
~/Downloads/dogecoin/qa/pull-tester$ python rpc-tests.py -parellel=10
No tests selected; do you have a typo in {'-parellel=10'}?

dogecoin-qt-translations-fr.zip

Jody78


Create Authors “hector-pina”

Automatically generated by Netlify CMS

👷 Deploy Preview for yanipaper processing.

Name
Link

🔨 Latest commit
e766d0b511c7ba1e7eb8e739b894b0769bc4714c

🔍 Latest deploy log
https://app.netlify.com/sites/yanipaper/deploys/658bac382298f50008067a02


[Feature request] add tar.gz binaries for pi2

Most Rasberry pi are under Rasbian which hasn't got an unziper by default  but have the tar command.
So that's why I ask if it is possible to add tar.gz binaries format for pi2 architecture.
PS: Can you precise the version of ARM use to compile gogs ? It look like this one is not compatible with ARMv6l (Raspberry B+)

The file command will tell you everything you need to know. Ex:
$  file /bin/ls
/bin/ls: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked,
  interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32,
  BuildID[sha1]=87efec13ca0b4ffa75dda873cad8a8db7ae22def, stripped


Maps should be made for regions of interest instead bounding boxes

Context: The inference colab notebook uses a bounding box to determine which area to export data for (and thereby make a map for).
Issue: The bounding box limitation means that predictions are made for pixels not necessarily inside the region of interest and these predictions are not useful.
Potential solution: A shapefile or something similar could be used to determine which area to export data for and ensure useless predictions are not made.
See: https://developers.google.com/earth-engine/apidocs/export-table-tocloudstorage
Potential gain: A solution to this issue could result in a significant speed up and cost saving for map creation.

@adebowaledaniel FYI, there is a lot of nuance involved with this task. If you are interested in tackling we can schedule a discussion at some point in the future.

Okay, @ivanzvonkov, I will drop some notes on this later.


Entry interface bug if switched between landscape and portrait mode

Steps to reproduce

Open an entry
Switch to landscape mode, wait 3 sec
Switch to portrait mode

Expected behavior
Interface not blocked and expected normal behaviour
Actual behavior
https://github.com/LNReader/lnreader/assets/75091899/ebe0a066-b056-40c0-a469-1f091f688047
LNReader version
1.1.18
Android version
Android 8
Device
Huawei p8 lite 2017
Other details
Once the bug in "actual behaviour" is triggered to exit that, one needs to restart the app
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with a source, I should be opening an issue in the sources repository.
[X] I have updated the app to version 1.1.18.
[X] I will fill out all of the requested information in this form.

Not able to reproduce this. Could be a device specific issue.
https://github.com/LNReader/lnreader/assets/57822170/10f125a4-7bca-4695-9e5f-6091ed1a6b39


Sync Mandates

Get and sync all business mandates  and store in the cashier database

After a discussion with Vandar Direct Debit Development Team, it has been deemed for cashier not to be able to sync all mandates at once as this will put a large amount of pressure on our APIs, solutions will instead be released on the API side to make sure our merchants receive updates on mandates.
This should be considered in the future development of Cashier and Vandar product development.


LUNE template

Hey guys,
Submitting PR for initial review of WIP LUNE template.
Preview can be found here:
https://gweb-amp-template-lune.firebaseapp.com/templates/lune/lune.amp
Contains 4 pages:

Landing page
Product - Blanc
Product - Noir
Store

@WillDonohoe - this PR is HUGE - i cant possibly review a PR of this size and help you merge it within the next 2 weeks. This will take a lot of back and forth
Other points

Too much CSS
Dont add utility classes like BASS even if it is only for your template - we will not write any documentation for other utility classes (high maintenance)
Create readable meaningful classes where required only
Try to do css with BASS whereever it makes sense
override variables to get benefits out of the box (even spacing)
You don't have to create new css vars unless you use it in a computation or there is a lot of redundancy
The choice of units in the PR is confusing , there is a lot of PX , ems and %s while ampstart uses a lot of rems.
Try to make your markup as semantic as possible.

I have not reviewed the entire PR - just this took me a lot of time.  Please try to split them up.

Hi @camelburrito. Thank you for your time on reviewing this. I understand it's a large PR. What we're going to do is split this up into separate PRs for you to review. We've also taken into account your other comments and will be addressed, along with applying the same style across the rest of the site in the upcoming PRs.

Closing this pull request in favour of splitting them up.


grammarly:null

The extension is not working it seems it cannot connect to Grammarly's servers or something
output:
020-04-29T20:31:25.648Z grammarly:host 🔻 {
scores: {
Engagement: 1,
GeneralScore: 1,
Correctness: 1,
Tone: 1,
Clarity: 1
},
action: 'feedback',
id: 4
}
2020-04-29T20:31:25.648Z grammarly:host status: queue=0, pending=0
2020-04-29T20:31:29.091Z grammarly:host status: queue=0, pending=0
2020-04-29T20:31:29.158Z grammarly:host status: queue=0, pending=0
2020-04-29T20:31:29.568Z grammarly:host 🔻 {
sid: 1,
rev: 54,
score: 100,
outcomeScores: {
Engagement: 1,
GeneralScore: 1,
Correctness: 1,
Tone: 1,
Clarity: 1
},
generalScore: 100,
removed: [],
dialect: 'american',
foreign: false,
action: 'finished'
}
2020-04-29T20:33:09.170Z Grammarly:host status: queue=0, pending=0

Same issue.

Slightly more output to help debugging:
2020-06-13T13:05:07.900Z grammarly:host status: queue=0, pending=0
2020-06-13T13:05:07.900Z grammarly:host Expecting: 22 Got: 57
2020-06-13T13:05:07.900Z grammarly:host Expecting: 64 Got: 57
2020-06-13T13:05:07.900Z grammarly:host Expecting: 56 Got: 57
2020-06-13T13:05:07.900Z grammarly:host Expecting: 143 Got: 57
2020-06-13T13:05:07.900Z grammarly:host Expecting: 17 Got: 57
2020-06-13T13:05:07.900Z grammarly:host Expecting: 80 Got: 57
2020-06-13T13:05:07.900Z grammarly:host Expecting: 11 Got: 57
2020-06-13T13:05:07.900Z grammarly:host Expecting: 11 Got: 57
2020-06-13T13:05:07.900Z grammarly:host Expecting: 74 Got: 57
2020-06-13T13:05:07.900Z grammarly:host Expecting: 54 Got: 57
2020-06-13T13:05:07.900Z grammarly:host Expecting: 60 Got: 57
2020-06-13T13:05:07.900Z grammarly:host Expecting: 64 Got: 57
2020-06-13T13:05:07.900Z grammarly:host Expecting: 71 Got: 57
2020-06-13T13:05:07.900Z grammarly:host Expecting: 17 Got: 57
2020-06-13T13:05:07.900Z grammarly:host Expecting: 46 Got: 57
2020-06-13T13:05:07.900Z grammarly:host Expecting: 37 Got: 57
2020-06-13T13:05:07.900Z grammarly:host Expecting: 22 Got: 57
2020-06-13T13:05:07.900Z grammarly:host Expecting: 41 Got: 57
2020-06-13T13:05:07.900Z grammarly:host Expecting: 11 Got: 57
2020-06-13T13:05:07.900Z grammarly:host Expecting: 54 Got: 57
2020-06-13T13:05:07.900Z grammarly:host Expecting: 52 Got: 57
2020-06-13T13:05:07.900Z grammarly:host Expecting: 53 Got: 57
2020-06-13T13:05:07.900Z grammarly:host Expecting: 10 Got: 57
2020-06-13T13:05:07.900Z grammarly:host Expecting: 11 Got: 57
2020-06-13T13:05:07.900Z grammarly:host Expecting: 57 Got: 57
[Error - 2:05:07 PM] Request textDocument/codeAction failed.
  Message: Request textDocument/codeAction failed unexpectedly without providing any details.
  Code: -32603
2020-06-13T13:05:09.334Z grammarly:host status: queue=0, pending=0

Same issue here. Whenever I double click something inside backticks on a .md file I get this:
2020-07-10T00:27:41.713Z grammarly:host status: queue=0, pending=0
2020-07-10T00:27:41.714Z grammarly:host Expecting: 69 Got: 69
[Error - 5:27:41 AM] Request textDocument/codeAction failed.
  Message: Request textDocument/codeAction failed unexpectedly without providing any details.
  Code: -32603
2020-07-10T00:27:44.646Z grammarly:host status: queue=0, pending=0
2020-07-10T00:27:44.921Z grammarly:host status: queue=0, pending=0
2020-07-10T00:27:46.484Z grammarly:host Schedule a handler for: synonyms
2020-07-10T00:27:46.484Z grammarly:host 🔺 { action: 'synonyms', begin: 24, token: 'template', id: 71 }
2020-07-10T00:27:46.484Z grammarly:host status: queue=0, pending=0
2020-07-10T00:27:46.774Z grammarly:host 🔻 {
  error: 'cannot_find_synonym',
  severity: 'info',
  action: 'error',
  id: 71
}
2020-07-10T00:27:46.775Z grammarly:host status: queue=0, pending=0
2020-07-10T00:27:46.775Z grammarly:host Expecting: 71 Got: 71
[Error - 5:27:46 AM] Request textDocument/codeAction failed.
  Message: Request textDocument/codeAction failed unexpectedly without providing any details.
  Code: -32603
2020-07-10T00:27:54.647Z grammarly:host status: queue=0, pending=0
2020-07-10T00:27:54.942Z grammarly:host status: queue=0, pending=0
2020-07-10T00:27:57.938Z grammarly:host Schedule a handler for: synonyms
2020-07-10T00:27:57.938Z grammarly:host 🔺 { action: 'synonyms', begin: 24, token: 'template', id: 73 }
2020-07-10T00:27:57.938Z grammarly:host status: queue=0, pending=0
2020-07-10T00:27:58.322Z grammarly:host 🔻 {
  error: 'cannot_find_synonym',
  severity: 'info',
  action: 'error',
  id: 73
}
2020-07-10T00:27:58.322Z grammarly:host status: queue=0, pending=0
2020-07-10T00:27:58.322Z grammarly:host Expecting: 73 Got: 73
[Error - 5:27:58 AM] Request textDocument/codeAction failed.
  Message: Request textDocument/codeAction failed unexpectedly without providing any details.
  Code: -32603
2020-07-10T00:28:04.650Z grammarly:host status: queue=0, pending=0
2020-07-10T00:28:04.933Z grammarly:host status: queue=0, pending=0
2020-07-10T00:28:14.655Z grammarly:host status: queue=0, pending=0
2020-07-10T00:28:15.020Z grammarly:host status: queue=0, pending=0
2020-07-10T00:28:24.655Z grammarly:host status: queue=0, pending=0
2020-07-10T00:28:25.081Z grammarly:host status: queue=0, pending=0
2020-07-10T00:28:34.657Z grammarly:host status: queue=0, pending=0
2020-07-10T00:28:34.932Z grammarly:host status: queue=0, pending=0
2020-07-10T00:28:44.656Z grammarly:host status: queue=0, pending=0
2020-07-10T00:28:45.016Z grammarly:host status: queue=0, pending=0
2020-07-10T00:28:54.660Z grammarly:host status: queue=0, pending=0
2020-07-10T00:28:54.936Z grammarly:host status: queue=0, pending=0
2020-07-10T00:29:04.664Z grammarly:host status: queue=0, pending=0
2020-07-10T00:29:05.000Z grammarly:host status: queue=0, pending=0

Same thing with package.json files. And there's no way to stop it. Send help!


GH-43114: [Archery][Dev] Support setuptools-scm >= 8.0.0

Rationale for this change
The update to setuptools-scm version 8.0.0 or higher ensures compatibility for Archery.

What changes are included in this PR?

Added Configuration objects to handle necessary parameters (get_describe_command)
Fixed the parse_git_version function to align with the new version of setuptools_scm
Updated setuptools_scm requirement to version 8.0.0 or higher

Are these changes tested?
Yes, tested by CI.

Are there any user-facing changes?
No.

GitHub Issue: #43114

@raulcd @kou Could you review this when your free time? Thank you.


Open AI Configuration is not valid (Unknown)

Any key won't work

Any key won't work

The same

Did it work previously or have you just started using the plugin?

Did it work previously or have you just started using the plugin?

I've just installed the plugin. I've tried to restart Android Studio a couple of times and generate new token. Nothing helped. But I've just checked again and it started to work now.
Not sure what was the problem but seems I wasn't the only one.
Thanks for quick response, btw!


Breaks due to changes in graphql 2.3.5

After updating dependencies in a project using this gem we have begun to see failures during query parsing:

Caused by NoMethodError: undefined method 'map' for nil
from...gems/graphql-client-0.22.0/lib/graphql/client/schema/interface_type.rb:24:in `define_class'

At a(n uninformed) glance, this appears to be somehow related to graphql 2.3.5 switching from string-based to class-based keys here:
Using graphql 2.3.4
[3] pry(#<Module:0x00000001363208c0>::Actor)> definition.client.possible_types
=> {"__Schema"=>[#<Class:0x000000012ff71680>],
   "__Type"=>[#<Class:0x000000012ff71360>],
   "__Field"=>[#<Class:0x000000012ff71040>],
   "__Directive"=>[#<Class:0x000000012ff70d20>],
   ...

Using graphql 2.3.5:
[2] pry(#<Module:0x00000001363208c0>::Actor)> definition.client.possible_types
=> {#<Class:0x0000000136325640>=>[#<Class:0x0000000136325640>],
 #<Class:0x0000000136325280>=>[#<Class:0x0000000136325280>],
 #<Class:0x0000000136324f60>=>[#<Class:0x0000000136324f60>],
 #<Class:0x0000000136324c40>=>[#<Class:0x0000000136324c40>],
 #<Class:0x0000000136324920>=>[#<Class:0x0000000136324920>],

Hey, thanks for reporting this! Yes, I bet you're right about the cause. I forgot about the possibility of outside callers of this method 😖
I worked up a patch in #28 and I'm going to update the GraphQL-Ruby changelog to mention this as a breaking change.

Cool - we'll pin the dependency in our gemfile until that fix releases. Didn't expect a super-fast turnaround, but I'm certainly grateful for it!

v0.23.0 is on Rubygems with this fix -- please let me know if you have any more trouble with it!

@rmosolgo - fix is worky in our app. Thanks again! 🙇♂


[WIP] Release notifications

Only thing I can't quite figure out is how to link to it... We get an API path that we can extract the id from, like this:
https://api.github.com/repos/facebook/Docusaurus/releases/9721470
Where 9721470 is the ID. But I'm not sure how to link it to the actual release.
Any ideas?
Shot of it working:

if we can get the tag name, then we can do something like below
https://github.com/facebook/Docusaurus/releases/tag/v1.0.7 to link to it

Totally misread this as you wanted to do push notifications for releases 🤦♂

@rizwankce nice! Tag name exists, we can use that.
Sent with GitHawk

I’m just gonna cheat and do an extra network request to get the tag name.
Sent with GitHawk


Update system level message-receiver initialization logic

Description:

$subject

Completed with following PR:

https://github.com/wso2-enterprise/azure-websubhub/pull/67


echo.websocket.org was shutdown

https://github.com/EagleAglow/vba-websocket-class/blob/c1447345287abee39a852f912ac2930edaf969c6/Main.bas#L26
As echo.websocket.org was shutdown it may be worthwhile to change to another example echo server such as echo.websocket.events as mentioned here https://www.lob.com/blog/websocket-org-is-down-here-is-an-alternative

Excellent suggestion! Implemented...


Set start day of the week

Hi
Is it possible to edit the first day of the week?
Thanks¡¡

Start of the week is based on the locale provided. This is defined by moment's locales. If you want to change it, create your own locale file or override. See moment's docs.
Duplicate of #1013, #518, #345 and #670

Perfect, solved, thank you


concatenate multiple array matches in a single cell

Hi,  thx a lot for the function, works great !
I d like to be able to display a concatenated list in a single cell .
I have a feed with arrays of tags for each item, and I would like to concatenate all item tags in a single column
For example, I would target each item, and use columns: tags[].slug, and I would like it to return "gouvernement, remaniement,..."
Currently I can only think of creating multiple columns tags[0].slug,tags[1].slug,... and concatenate them in Sheet, but that relies on knowing the maximum number of tags
"tags": [
               {
           "slug": "gouvernement",
           "nodeId": "null"
       }
       ,                {
           "slug": "remaniement",
           "nodeId": "null"
       }
       ,                {
           "slug": "ministre-de-l-interieur",
           "nodeId": "null"
       }
       ,                {
           "slug": "tensions",
           "nodeId": "null"
       }
                   ],

+1


No zip file created

Looks like a great tool. Unfortunately when I click Generate Images a new tab opens in Safari but the zip file is never downloaded. Any ideas?

Thanks for letting me know. After looking into this, it seems to be a Safari issue. I am using Filesaver.js to save the images and many folks are having this issue: https://github.com/eligrey/FileSaver.js/issues/12. It seems to work fine in Chrome and Firefox.

Until these Safari issues are fixed, I have added an alert to inform Safari users that the recommended browsers are Chrome and Firefox.

And I'll leave the issue open until then.

i got the same problem but with Chrome it's works perfect !

Agree with BR, it works on Chrome.


Add Prow E2E Tests to main branch

Copy Prow E2E test updates to main branch
Part of issue https://issues.redhat.com/browse/CMCS-117

Withdrawing this PR so I can do some more stuff in test branch before pulling into main branch


Bogus 15.1.0 release

When trying to install latest 15.1.0 1npm i -g now`
I get this error when running on macOS X.
Downloading Now CLI 15.1.0 [                    ] 0%
Error: Not Found https://github.com/zeit/now-cli/releases/download/15.1.0/now-macos.gz
It looks like the release 15.1.0 is bogus

Sorry about that, can you try it again? The asset has been uploaded at this point.

All good now


Added --auto-correct and --no-auto-correct options to Detekt task

Adds Gradle's task option support for fast enabling/disabling auto correct feature.
The goal is to have this lightweight switch to avoid extra logic in the build script to support it.
./gradlew detetkt --auto-correct

or
./gradlew detetkt --no-auto-correct

Our use case is to have this command in our CI pipeline.

Thanks for your PR

The goal is to have this lightweight switch to avoid extra logic in the build script to support it.

I'm not necessarily against this, but I think merging this will be awkward in some ways:

First we will have to maintain a "CLI-like" API for the Gradle tasks, and this should be aligned with the Detekt CLI. In this case Detekt CLI has --auto-correct (but also -ac that here is not supported), but doesn't have --no-auto-correct.

It feels odd to have just one feature that allows to be configured via Gradle CLI, while all the others are not.

I'm against having both --auto-correct and --no-auto-correct. When designing CLI we try to offer defaults for all the values and offers flags that mutate those defaults. In this case we should probably offer only the --auto-correct flag.

Happy to discuss what's your view on this @gmazzo. Specifically is this PR coming from your own personal experience? Were you not able to achieve something similar with Gradle Properties?

Thanks for your PR

The goal is to have this lightweight switch to avoid extra logic in the build script to support it.

I'm not necessarily against this, but I think merging this will be awkward in some ways:

First we will have to maintain a "CLI-like" API for the Gradle tasks, and this should be aligned with the Detekt CLI. In this case Detekt CLI has --auto-correct (but also -ac that here is not supported), but doesn't have --no-auto-correct.
It feels odd to have just one feature that allows to be configured via Gradle CLI, while all the others are not.
I'm against having both --auto-correct and --no-auto-correct. When designing CLI we try to offer defaults for all the values and offers flags that mutate those defaults. In this case we should probably offer only the --auto-correct flag.

Happy to discuss what's your view on this @gmazzo. Specifically is this PR coming from your own personal experience? Were you not able to achieve something similar with Gradle Properties?

Let me dig further into our use-case and I'll let the API design decision to you.
One of our engineers decided to support this auto-update feature in our core libs. As changing the code can be invasive we decided to let it to each developer's personal criteria to turn it on.
To support this, our engineer added autoCorrect = project.hasProperty("autoCorrect") to the DSL configuration. So this will be an opt-in feature either through Gradle user defaults or by command line, but not for the whole project.
That's when I remember Gradle has applied this same pattern in their API and decided to open the PR. For instance, Build Cache can be enabled by org.gradle.caching.enabled=true or with --build-cache option. They also have the --no-build-cache as an opt-out (in case it generally enabled).
Finally, --no-auto-correct has a justification too. Imagine you have enabled this to the general project, in the standard way trough the DSL. Now you can to run an extra check on the CI but you don't want file to get modified in there, so you can use this option to turn it off.
That's all, feel free to reject if it doesn't fit your API design guidelines ;)

Thanks for your explanation @gmazzo 🙏

That's all, feel free to reject if it doesn't fit your API design guidelines ;)

I'd like to have the other maintainers opinion on this as well.

I agree with Nico. We handled such cases in the past as you described, since the same can be achieved in Gradle scripts  with a litte bit more effort but without touching detekt's API.

I agree with Nico. We handled such cases in the past as you described, since the same can be achieved in Gradle scripts with a litte bit more effort but without touching detekt's API.

Ok then! I'm closing the PR

@gmazzo The other alternative is to define two tasks separately:

./gradlew detektCheck to only check for violations (autoCorrect = false)
./gradlew detektFormat to autocorrect violations (autoCorrect = true)

Meanwhile, there are still limitations of Gradle task options (https://docs.gradle.org/current/userguide/custom_tasks.html#limitations):
Options cannot be declared globally e.g. on a project-level or as part of a plugin.
When assigning an option on the command line then the task exposing the option needs to be spelled out explicitly
If you are using Detekt's Jvm, Android, or KMM with type resolution, running ./gradlew detekt --auto-correct it won't work, because we need to specify the explicit task name (such as :detektMain)


Docs out of date for "Publishing to Apple App Store"

Old Version
0.73
New Version
0.74
Description
In https://github.com/facebook/react-native/pull/37923 we changed Info.plist to add NSAllowsArbitraryLoads=false and NSAllowsLocalNetworking=true.
That means, this section of the React Native docs are now out of date:

Steps to reproduce

install new project
follow guide to publish to app store
see inconsistency

Affected Platforms
Runtime - iOS
Output of npx react-native info
no

Stacktrace or Logs
no

Reproducer
no
Screenshots and Videos
Above

bad bot, no

cc @philIip @lunaleaps


Why do I always have an unread Notification

As shown in the picture

Dude, you always Tran to Automatically code.....


226-1-7 add testing criSandBox

Signed-off-by: MangoDai<EMAIL_ADDRESS>
Ⅰ. Describe what this PR did
Ⅱ. Does this pull request fix one issue?

fixes #1915
Ⅲ. Describe how you did it
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

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

@@            Coverage Diff            @@
##           master   #2005      +/-   ##
=========================================
- Coverage   63.31%     58%   -5.31%
=========================================
  Files         200     200
  Lines       15522   15522
=========================================
- Hits         9828    9004     -824
- Misses       4455    5191     +736
- Partials     1239    1327      +88

Flag
Coverage Δ

#criv1alpha1test
33.82% <ø> (-0.03%)
:arrow_down:

#criv1alpha2test
34.24% <ø> (-0.04%)
:arrow_down:

#integrationtest
38.4% <ø> (-0.03%)
:arrow_down:

#unittest
25.26% <ø> (+4.4%)
:arrow_up:

Impacted Files
Coverage Δ

pkg/multierror/def.go
15.38% <0%> (-84.62%)
:arrow_down:

daemon/logger/loggerutils/tag.go
0% <0%> (-81.82%)
:arrow_down:

pkg/utils/utils.go
25.64% <0%> (-64.53%)
:arrow_down:

pkg/bytefmt/bytefmt.go
28.81% <0%> (-64.41%)
:arrow_down:

ctrd/image_proxy_util.go
7.81% <0%> (-59.38%)
:arrow_down:

daemon/mgr/container_envs.go
11.76% <0%> (-54.91%)
:arrow_down:

daemon/logger/info.go
0% <0%> (-53.66%)
:arrow_down:

daemon/logger/syslog/validate.go
0% <0%> (-52.64%)
:arrow_down:

pkg/utils/filters/filter.go
22.5% <0%> (-50%)
:arrow_down:

pkg/utils/templates/templates.go
0% <0%> (-50%)
:arrow_down:

... and 29 more


Can't select MetaMask wallet on Mac desktop app

What happened?
When I try to select MetaMask on the Decentraland's Mac desktop app it acts as if I selected WalletConnect, WalletConnect and Coinbase Wallet both seem to be working
Steps to reproduce
Launch Mac desktop app
Select MetaMask wallet to connect
acts as if I selected WalletConnect
Operating System
Opera
Wallet
Metamask
CPU
Apple M1 Max
GPU
Apple M1 Max
RAM
32GB
Kernel Version

Unity Version

Realm
No response
NameTag
No response

hello! this is an expected behaviour, but we will analyze it to see if we can improve it

https://user-images.githubusercontent.com/90054458/179527269-373de044-22df-427f-8d35-69328edcbc4e.mov


Display metadata tags on Info sidebar

It would be helpful to list metadata tags in the Info sidebar on the fullscreen viewer.
The metadata tags currently display when hovering over items in the thumbnail view, but when in the single item view mode there is no where to see the tags. The Info sidebar would be a good place to list them - and they could be hyperlinked to the tag searches.
This is especially useful for the mobile viewer where there is no 'hover' for touchscreens and thumbnail sized tags display are often too small to see all the tags.

This would be very helpful indeed.

Hi, I've implemented this. It should be included in the next release.


Axon eval(hisClear) requires POST, not GET with skyspark

session.get_eval( 'hisClear(parseRef("p:dataCenter50B:r:282c63c3-f1e7d0c0"), 2021)' )

results in
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/site-packages/pyhaystack-3.0.0-py3.8.egg/pyhaystack/client/http/sync.py", line 78, in _request
  File "/usr/local/lib/python3.8/site-packages/requests-2.25.1-py3.8.egg/requests/models.py", line 943, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 405 Client Error: GET not allowed for op 'eval' for url: https://skysparkhost.xxx.yyy/api/dataCenter50B/eval?expr=hisClear(parseRef(%22p:dataCenter50B:r:282c63c3-8655c4e7%22),%202021)

with fix of using _post_grid:
class EvalOpsMixin(object):
    def post_eval(self, arg_expr):
        url = "eval"
        eval_grid = hszinc.Grid()
        eval_grid.column["expr"] = {}
        eval_grid.append({"expr": arg_expr})
        return self._post_grid(url, eval_grid, callback=lambda *a, **k: None)

results in
<Grid>
        Version: 3.0
        Columns:
                id
                dis
                numRemoved
        Row    0:
        id=Ref('p:dataCenter50B:r:282c63c3-f1e7d0c0', '91 onicon  Return Temperature', True)
        dis='91 onicon  Return Temperature'
        numRemoved=1918.0
</Grid>

if this looks acceptable, i can submit a PR...

Can you try develop branch ? We've made a post_eval version few months ago

@ChristianTremblay I see the code is still in the develop branch.    @clarsen can you submit the PR?
Thanks!

Are there any updates on this issue? I am still having the above mentioned 405 errors using pyhaystack 3.0.0?


Problem spinning up cluster

Greetings!
I'm using docker 1.12 and docker-compose 1.8.  When I spin up the cluster, I am getting the following errors in the database docker log (sampling of errors):
ERROR:  relation "systems" does not exist at character 19
STATEMENT:  SELECT Value FROM Systems WHERE Name='Version'
ERROR:  relation "idx_teams_name" does not exist
STATEMENT:  SELECT $1::regclass
ERROR:  relation "idx_teams_invite_id" does not exist
STATEMENT:  SELECT $1::regclass
ERROR:  relation "idx_teammembers_team_id" does not exist
STATEMENT:  SELECT $1::regclass
ERROR:  relation "idx_teammembers_user_id" does not exist
STATEMENT:  SELECT $1::regclass
ERROR:  relation "idx_channels_team_id" does not exist
STATEMENT:  SELECT $1::regclass
ERROR:  relation "idx_channels_name" does not exist
STATEMENT:  SELECT $1::regclass
ERROR:  relation "idx_channelmembers_channel_id" does not exist
STATEMENT:  SELECT $1::regclass
ERROR:  relation "idx_channelmembers_user_id" does not exist

I get this both by using docker compose and building locally, as well as pulling down the mattermost/mattermost-prod images and manually building run commands.
It appears as though the expected tables do not exist.
For grins, I'm testing on a different host (the one giving the error is on aws) to compare.

I've seen the error mesages but ignored because anyway mattermost works well. I'm not sure why the errors occur.
Does anyone have seen this error? @it33

Sorry, just seeing this now not sure, @aetherical could I ask your help to post this to https://www.mattermost.org/troubleshoot/?

Closing this issue due to lack of activity. If this is still unresolved please consider submitting to the Troubleshooting Forum where members of the community might be able to help!


[Multi Hub] Interact with the Calendar, Mail, Profile from personal tabs app

…bs app

Build Pipeline -

https://github.com/OfficeDev/Microsoft-Teams-Samples/actions/runs/5445234420

Duplicate of: https://github.com/OfficeDev/Microsoft-Teams-Samples/pull/852


Better readability and efficiency.

Implement more efficient checks for file extensions and improve handling of file name lengths. Introduce options such as -h for help, -l for a detailed list, and -lh for a human-readable detailed list. Also, include functionality to list files in other directories.

Made significant improvements to enhance its quality.

files with binary extensions don't have to be executable, it's better to check files permissions instead of checking extension. on example all files in /bin are executable, but without extensions

I added it but not through merging due to file conflicts. additionally, I added the -s flag


Upgraded Go 1.20 -> 1.21

Fixes: #569

Thanks for the contribution @prady0t .
I think that bumping the go version should be OK for the project.
Did you build and run it on a test cluster after the change to verify everything still works as expected?
I would also suggest quickly browsing the release notes to make sure that we are not affected by anything introduced in the new version.
Thanks!

Ah yes I did! It was working fine with all it's cli commands working. The reason the above build failed is because starting from go 1.21 the way versions were numbered has slightly changed (as per the release note https://tip.golang.org/doc/go1.21#:~:text=Go 1.21 introduces,new version numbering.)
So in this line :
https://github.com/keyval-dev/odigos/blob/d20861bb1429e6160b27200a1278bcc4f61899d4/odiglet/Dockerfile#L20
go1.20 should be replaced by something like 1.21.0 (or maybe higher). But I'm not sure if I should keep 1.21 elsewhere as it is or change there too.


[JetBrains Toolbox Recent Projects] ...

Extension
https://www.raycast.com/gdsmith/jetbrains
Description
Reason: Code: 14 (Timeout)
Domain: commands
Time: 04:06:57.088
Steps To Reproduce
No response
Current Behaviour
No response
Expected Behaviour
No response

Reason: Code: 14 (Timeout)
Domain: commands
Time: 04:06:57.088

@linpan
You can execute find ~/Library/Application\ Support/JetBrains/Toolbox/apps -type f -name .history.json ,If the output is {},
You can try installing from Toolbox or update  using toolbox?.

I'm having the same issue, installed and copied the paths from toolbox but all I get is a timeout:
Reason: Code: 14 (Timeout)
Domain: commands
Time: 11:47:43.162


New release soon?

Is there a new release of React-Trello coming soon on npm?
I found a bug but it looks like it's already been fixed in the latest code.

Is this library still being maintained?


Thoughts after reading paper

Not quite understand why we can't simply apply an anti-diagonal pattern to dp non-recrusive version of DTW. This will allow us to get linear space usage and easy parallelization on GPU?
Have I missed something?

Thanks for asking this. That will work fine for computing the optimal cost.
But unless you store all of the backpointers in memory, it's not possible
to figure out an optimal alignment path. So the divide and conquer
technique gets around this by extracting parts of an alignment path by
looking at cost only. Does that make sense?
On Thu, Nov 12, 2020, 7:46 AM Nikita<EMAIL_ADDRESS>wrote:

Not quite understand why we can't simply apply an anti-diagonal pattern to
dp non-recrusive version of DTW
https://en.wikipedia.org/wiki/Dynamic_time_warping#:~:text=In time series analysis%2C dynamic,which may vary in speed.&text=A well known application has,cope with different speaking speeds..
This will allow us to get linear space usage and easy parallelization on
GPU?
Have I missed something?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ctralie/linmdtw/issues/5, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJWDZQ3JEAYHEIOKRVARKDSPPKJ5ANCNFSM4TTHXKKQ
.

Yep, now get it, thanks!)

Glad I could clear it up!  I honestly started this project with your exact
thoughts, but then realized pretty quickly that I wouldn't be able to get
an alignment after throwing out all of the backpointers.
On Thu, Nov 12, 2020 at 9:04 AM Nikita<EMAIL_ADDRESS>wrote:

Closed #5 https://github.com/ctralie/linmdtw/issues/5.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ctralie/linmdtw/issues/5#event-3988835570, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJWDZWEIYGEEPOT4FVXKTDSPPTPDANCNFSM4TTHXKKQ
.


Synonym policies and implementation

If you realize that two OTUs are the same and then create a synonym relationship between them, what happens next, beyond of course that you can now view the synonym on the OTU results page? Currently, nothing, correct? The specimens stay under the original OTU, as do the associated descriptions and images. So, it is on the user to decide which name has priority and reassign all the specimens to that OTU? And make updates to which specimens are exemplars such that the range of characters would be captured in the merged OTU description? We should talk through how to do this and whether there are functions that could be implemented in PBot to make this easier.

I am closing this. There's is no way we can do anything about it now. It will have to be rolled into the PBDB 2.0 upgrades.


rustic-format-file hangs on Windows

On Emacs-28.1 for Windows (emacs-version : Emacs 28.1 (build 2, x86_64-w64-mingw32) of 2022-04-21) when running M-x rustic
-format-file the command does not terminate until C-c is pressed.
Some debugging learned that the process-status keeps in the 'run state. I could not repeat it when experimenting running rustfmt with the same arguments in the scratch buffer.
It smells like rustfmt detects the input file is opened and waiting for input, but it could be another reason why it decides to hang around till I press C-c. (and that does not explain why on Linux in WSL2 it works fine).

Does rustic-format-buffer work ?

Yes, that works fine. I should have  mentioned that. That's what I found puzzling prompting me to dig a bit deeper but I got stuck because ert-runner does not work properly either, got sidetracked and then my time ran out.

I just tried it on my windows machine and it works for me. Did you try it in different projects ?

You could comment the code in rustic-format-file step by step and see what's actually causing the problem. I'm sorry but as I can't reproduce I don't know how to help.

Same issue on the same OS and version of Emacs.
To me it looks like rustfmt processes Emacs processes endlessly run even though  the rustfmt.exe command exits immediately. I believe this is because rustic-make-process is setting the process coding system to 'utf-8-emacs-unix which then causes mismatches for signals on non-unix systems.
Unless I'm missing something setting this to default-process-coding-system should more reliably ensure that the appropriate coding system gets used here across different environments.
Opened a PR with that change. #426
@ptillemans Can you try that on your end as well?

Hi, I'm experiencing this issue on Windows as well. The fix PR that was merged only adds to the problem, since when I try to call rust-cargo-run (as well as potentially other rustic functions) with the current code (as of the PR), the command seems to run but I get an error saying that the wrong type argument was passed to the set-process-coding-system function. Following this error message, every attempt to call rust-cargo-run fails.
I've tried fixing the issue and found that changing the DECODING argument to a symbol but leaving the ENCODING argument causes this error to disappear. However, this change causes the original problem, which is rustic-format-file hanging, to resurface. I'm curious what you guys had as the value of default-process-coding-system - my setup has this variable set to (utf-8-dos . utf-8-unix), which I think is due to some settings I have to prefer utf-8 encoding. Running an unconfigured instance with emacs -Q gives (undecided-dos . undecided-unix).

It was probably premature to introduce a 'fix' since I don't think we fully understand what's causing this problem and I was acting on a hunch. Sorry about that.
I had similar behavior and circumstances as what you are reporting: when using emacs 28.2 (on Windows 11 - 10.0.25201 Build 25201) from the main GNU FTP server with Rustic prior to the change in #426 I was experiencing the hang and the PR did fix the issue for me (I'm also able to run rustic-cargo-run without any issues). The value of default-process-coding-system for me on there has been (utf-8-dos . utf-8-unix) and still is although I experimented with others without much success.
However, I recently tried a fresh install of emacs on a fresh copy of the same OS and found I encountered the same behavior as yourself (wrong argument type error). After using (set-process-coding-system process (car default-process-coding-system) (cdr default-process-coding-system)) in place of the previous change in rustic-make-process the issue was resolved and I also no longer had the hanging behavior. In fact, using the pre #426 line of (set-process-coding-system process 'utf-8-emacs-unix 'utf-8-emacs-unix) also no longer results in hanging for me in this case.
It might be useful to gather more information across our environments to get a better idea of what we might be able to attribute the differences to. Here are the relevant parts of M-x report-emacs-bug on my end (executing in the emacs session where I am no longer experiencing the hanging issue):
`In GNU Emacs 28.2 (build 2, x86_64-w64-mingw32)
of 2022-09-13 built on AVALON
Windowing system distributor 'Microsoft Corp.', version 10.0.25201
System Description: Microsoft Windows 10 Pro (v10.0.2009.25201.1000)
Configured using:
'configure --with-modules --without-dbus --with-native-compilation
--without-compress-install CFLAGS=-O2'
Configured features:
ACL GIF GMP GNUTLS HARFBUZZ JPEG JSON LCMS2 LIBXML2 MODULES NATIVE_COMP
NOTIFY W32NOTIFY PDUMPER PNG RSVG SOUND THREADS TIFF TOOLKIT_SCROLL_BARS
XPM ZLIB
(NATIVE_COMP present but libgccjit not available)
Important settings:
value of $LANG: ENU
locale-coding-system: utf-8
Major mode: ELisp/l
Minor modes in effect:
recentf-mode: t
persp-mode: t
treemacs-filewatch-mode: t
treemacs-follow-mode: t
treemacs-git-mode: t
treemacs-fringe-indicator-mode: t
org-super-agenda-mode: t
highlight-indentation-current-column-mode: t
highlight-indentation-mode: t
rainbow-delimiters-mode: t
which-key-mode: t
gcmh-mode: t
windmove-mode: t
show-smartparens-global-mode: t
show-smartparens-mode: t
smartparens-global-strict-mode: t
smartparens-strict-mode: t
smartparens-mode: t
poetry-tracking-mode: t
global-origami-mode: t
origami-mode: t
global-git-commit-mode: t
magit-auto-revert-mode: t
global-flycheck-mode: t
flycheck-mode: t
shell-dirtrack-mode: t
yas-global-mode: t
yas-minor-mode: t
all-the-icons-ivy-rich-mode: t
counsel-projectile-mode: t
projectile-mode: t
counsel-mode: t
ivy-rich-mode: t
minibuffer-depth-indicate-mode: t
ivy-mode: t
global-company-mode: t
company-mode: t
popwin-mode: t
global-hl-line-mode: t
display-time-mode: t
auto-image-file-mode: t
save-place-mode: t
savehist-mode: t
override-global-mode: t
tooltip-mode: t
global-eldoc-mode: t
eldoc-mode: t
show-paren-mode: t
electric-indent-mode: t
mouse-wheel-mode: t
file-name-shadow-mode: t
global-font-lock-mode: t
font-lock-mode: t
blink-cursor-mode: t
auto-composition-mode: t
auto-encryption-mode: t
auto-compression-mode: t
column-number-mode: 1
line-number-mode: t
transient-mark-mode: t
Load-path shadows:
~/.emacs.d/elpa/transient-20221028.1430/transient hides c:/Program Files/Emacs/emacs-28.2/share/emacs/28.2/lisp/transient
Features:
(shadow sort mail-extr emacsbug sendmail help-fns radix-tree cl-print
debug backtrace term ehelp pcmpl-unix vc-mtn vc-hg vc-bzr vc-src vc-sccs
vc-svn vc-cvs vc-rcs vc corfu recentf treemacs-bookmarks treemacs-tags
magit-bookmark bookmark pp perspective ido lsp-diagnostics
lsp-headerline lsp-icons lsp-lens vc-git vc-dispatcher hideshow lsp-ui
lsp-ui-flycheck lsp-ui-doc goto-addr lsp-ui-imenu lsp-ui-peek
lsp-ui-sideline lsp-ui-util view lsp-zig lsp-steep lsp-svelte lsp-sqls
lsp-ruby-syntax-tree lsp-yaml lsp-xml lsp-vimscript lsp-vhdl lsp-volar
lsp-vetur lsp-html lsp-verilog lsp-vala lsp-v lsp-typeprof lsp-ttcn3
lsp-toml lsp-terraform lsp-tex lsp-sorbet lsp-solargraph lsp-rf
lsp-remark lsp-racket lsp-r lsp-purescript lsp-pylsp lsp-pyls lsp-pwsh
lsp-php lsp-pls lsp-perlnavigator lsp-perl lsp-openscad lsp-ocaml
lsp-magik lsp-nix lsp-nim lsp-nginx lsp-mint lsp-marksman lsp-markdown
lsp-lua lsp-kotlin lsp-json lsp-javascript lsp-idris lsp-haxe lsp-groovy
lsp-hack lsp-graphql lsp-gleam lsp-go lsp-completion lsp-gdscript
lsp-fsharp lsp-fortran lsp-eslint lsp-erlang lsp-emmet lsp-elixir
lsp-elm lsp-dockerfile lsp-dhall lsp-d lsp-css lsp-csharp gnutls
lsp-crystal lsp-cmake lsp-clojure lsp-treemacs lsp-treemacs-generic
lsp-treemacs-themes treemacs-treelib treemacs treemacs-header-line
treemacs-compatibility treemacs-mode treemacs-interface
treemacs-persistence treemacs-filewatch-mode treemacs-follow-mode
treemacs-rendering treemacs-annotations treemacs-async
treemacs-workspaces treemacs-dom treemacs-visuals
treemacs-fringe-indicator treemacs-scope pulse treemacs-faces
treemacs-icons treemacs-themes treemacs-core-utils pfuture
treemacs-logging treemacs-customization treemacs-macros lsp-clangd dom
lsp-beancount lsp-bash lsp-ansible lsp-angular lsp-ada lsp-actionscript
lsp-modeline lsp-rust lsp-semantic-tokens flymake-proc flymake
rustic-flycheck rustic-spellcheck rustic-expand rustic-lsp
rustic-playpen rustic-rustfix rustic-racer rustic-babel rustic-rustfmt
rustic-comint rustic-clippy rustic-doc rustic-popup rustic-cargo
rustic-compile xterm-color rustic-interaction rustic smartparens-rust
rust-utils rust-mode mule-util ox-reveal ox-odt rng-loc rng-uri
rng-parse rng-match rng-dt rng-util rng-pttrn nxml-parse nxml-ns
nxml-enc xmltok nxml-util ox-latex ox-icalendar ox-ascii ox-hugo
ox-hugo-deprecated ol-info org-id ffap ox-blackfriday ox-md ox-html
table ox-publish tomelr ox smartparens-org org-super-agenda ts org-habit
org-element org-agenda org-refile org ob ob-tangle ob-ref ob-lob
ob-table org-macro org-footnote org-src ob-comint org-pcomplete org-list
org-faces org-entities org-version ob-emacs-lisp org-table org-keys
org-loaddefs cal-menu calendar cal-loaddefs avl-tree ol oc-basic bibtex
oc ob-exp ob-core org-compat ob-eval org-macs git-gutter+ tramp
tramp-loaddefs trampver tramp-integration files-x tramp-compat
parse-time iso8601 highlight-indentation rainbow-delimiters
company-oddmuse company-keywords company-etags etags fileloop generator
company-gtags company-dabbrev-code company-dabbrev company-files
company-clang company-capf company-cmake company-semantic company-bbdb
which-key init gcmh 60-yasnippet 60-yaml 60-windsize windsize windmove
60-whichkey 60-vterm 60-typescript smartparens-config
smartparens-markdown smartparens-text smartparens-lua smartparens
60-saveplace 60-rust 60-restclient 60-read-aloud 60-rainbow-delimiters
60-python lsp-pyright lsp-mode lsp-protocol tree-widget wid-edit spinner
network-stream nsm markdown-mode noutline outline inline ht ewoc poetry
pyvenv 60-powerline powerline powerline-separators powerline-themes
60-origami origami origami-parsers cl 60-org 60-nov 60-neotree neotree
60-multiple-cursors 60-markdown-mode 60-highlight-indentation 60-git
magit-find-file magit-submodule magit-obsolete magit-blame magit-stash
magit-reflog magit-bisect magit-push magit-pull magit-fetch magit-clone
magit-remote magit-commit magit-sequence magit-notes magit-worktree
magit-tag magit-merge magit-branch magit-reset magit-files magit-refs
magit-status magit magit-repos magit-apply magit-wip magit-log
which-func imenu magit-diff smerge-mode diff diff-mode git-commit
log-edit message rmc puny rfc822 mml mml-sec epa derived epg rfc6068
epg-config gnus-util rmail rmail-loaddefs mm-decode mm-bodies mm-encode
mailabbrev mail-utils gmm-utils mailheader pcvs-util add-log magit-core
magit-autorevert autorevert filenotify magit-margin magit-transient
magit-process magit-mode transient magit-git magit-base magit-section
format-spec crm compat-27 compat-26 60-flycheck flycheck find-func
60-expand-region 60-eshell eshell esh-cmd esh-ext esh-opt esh-proc
esh-io esh-arg esh-module esh-groups esh-util 60-emacs-ipython-notebook
dired-x 40-perspective 40-lsp lazy-set-key 40-ivy ivy-pass
password-store auth-source-pass with-editor shell pcomplete server
compat compat-macs ivy-yasnippet yasnippet-snippets yasnippet comp
comp-cstr warnings all-the-icons-ivy-rich counsel-projectile projectile
lisp-mnt mail-parse rfc2231 rfc2047 rfc2045 mm-util ietf-drums
mail-prsvr grep ibuf-ext ibuffer ibuffer-loaddefs thingatpt avy
ivy-hydra hydra lv counsel xdg xref project dired dired-loaddefs compile
swiper ivy-rich mb-depth ivy delsel ivy-faces ivy-overlay colir color
40-corfu company-terraform company-terraform-data terraform-mode
hcl-mode company-lua f f-shortdoc shortdoc text-property-search dash
lua-mode advice comint ansi-color company-jedi jedi-core
python-environment epc ctable concurrent deferred ring company-irony
company-template irony-completion irony-snippet irony irony-iotask
company-c-headers rx company-ansible company-ansible-keywords company
pcase 30-popwin popwin 20-theme all-the-icons all-the-icons-faces
data-material data-weathericons data-octicons data-fileicons
data-faicons data-alltheicons hl-line doom-themes-ext-org
doom-themes-ext-treemacs doom-themes-ext-neotree
doom-themes-ext-visual-bell face-remap doom-one-theme doom-themes
doom-themes-base 20-font 20-fill-column-indicator fill-column-indicator
05-ugly-workarounds 01-custom-keys time-date time image-file
image-converter avoid saveplace savehist init-loader benchmark s
cl-extra help-mode finder-inf use-package use-package-ensure
use-package-delight use-package-diminish use-package-bind-key bind-key
easy-mmode use-package-core edmacro kmacro info package browse-url url
url-proxy url-privacy url-expand url-methods url-history url-cookie
url-domsuf url-util mailcap url-handlers url-parse auth-source cl-seq
eieio eieio-core cl-macs eieio-loaddefs password-cache json subr-x map
url-vars seq byte-opt gv bytecomp byte-compile cconv cl-loaddefs cl-lib
iso-transl tooltip eldoc paren electric uniquify ediff-hook vc-hooks
lisp-float-type elisp-mode mwheel dos-w32 ls-lisp disp-table
term/w32-win w32-win w32-vars term/common-win tool-bar dnd fontset image
regexp-opt fringe tabulated-list replace newcomment text-mode lisp-mode
prog-mode register page tab-bar menu-bar rfn-eshadow isearch easymenu
timer select scroll-bar mouse jit-lock font-lock syntax font-core
term/tty-colors frame minibuffer cl-generic cham georgian utf-8-lang
misc-lang vietnamese tibetan thai tai-viet lao korean japanese eucjp-ms
cp51932 hebrew greek romanian slovak czech european ethiopic indian
cyrillic chinese composite emoji-zwj charscript charprop case-table
epa-hook jka-cmpr-hook help simple abbrev obarray cl-preloaded nadvice
button loaddefs faces cus-face macroexp files window text-properties
overlay sha1 md5 base64 format env code-pages mule custom widget
hashtable-print-readable backquote threads w32notify w32 lcms2 multi-tty
make-network-process native-compile emacs)
Memory information:
((conses 16<PHONE_NUMBER>08)
(symbols 48 61029 6)
(strings 32<PHONE_NUMBER>7)
(string-bytes 1 10009608)
(vectors 16 124438)
(vector-slots 8 1838245 213710)
(floats 8 2064 4752)
(intervals 56 4245 5522)
(buffers 992 22))
`

I've also opened up a PR to revert #426  since it's now known to cause issues:  #457

I was using Emacs 28.1 and updated to Emacs 28.2, still same problem. Here is my bug report (using (set-process-coding-system process 'utf-8-emacs-unix 'utf-8-emacs-unix)).
rustic-bug-report.txt

Hi,
I am currently having the hanging issue. But, as a note, for me only happens when the lsp server is up and running. If the server is shutdown, I don't have the issue. The change mentioned above by @ns-mkusper of (set-process-coding-system ...) doesn't seem to make a difference.
With debug-on-entry it runs to completion.