To make the ApprovingApplicationCausesConnectingWith sequence backward compatible

In the version 2.1.0 of RegistryOffice, there is an ApprovingApplicationCausesConnectingWith sequence.
This ApprovingApplicationCausesConnectingWith sequence will work fine if all the TAC applications are >= version 2.1.0 and their /v1/regard-application API produces a response-body that consists of attribute "successfully-connected" that indicates the status of the connection.
This ApprovingApplicationCausesConnectingWith sequence will not work , if any one of the TAC application is not < 2.1.0.
Proposal :
Proposing the following to make this ApprovingApplicationCausesConnectingWith sequence backward compatible ,

If the response of /v1/regard-application is 204 , that means , the serving application is < 2.1.0.
So , for this RegistryOffice version 2.1.0 , we shall skip the steps in validating the response of /v1/regard-application if the response-code is 204 and move to the next sequence.
Later in RegistryOffice version 3.0.0 , we shall remove this exceptions.

I would rather prefer to keep the period of TAC applications being on different releases as short as possible (respectively, not to register any other new application during that period) than to introduce another if-then-else that later has to be removed again.
Would you see any significant disadvantage from this ignorant position?

Similar to the decision made in https://github.com/openBackhaul/RegistryOffice/issues/541#issuecomment-1908091299 , if there is a problem in the ApprovingApplicationCausesConnectingWith sequence , then that problem will be reported to TypeApprovalRegistry. After manually resolving the problem , manually the embedding status shall be updated by an administrator by using the new feature defined in the TAR issue openBackhaul/TypeApprovalRegister#299.
Hence closing this issue.
From: Thorsten Heinze @.>
Sent: Wednesday, January 24, 2024 2:44 PM
To: openBackhaul/RegistryOffice @.>
Cc: Prathiba Jeevan (External) @.>; Assign @.>
Subject: Re: [openBackhaul/RegistryOffice] To make the ApprovingApplicationCausesConnectingWith sequence backward compatible (Issue #540)
The TAC applications are together to be put into operation within a short period of time.
In the period between the commissioning of the first and the last application of the TAC, no other applications should be put into operation.
—
Reply to this email directly, view it on GitHubhttps://github.com/openBackhaul/RegistryOffice/issues/540#issuecomment-1908151223, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AO3U24WSMEOA7LDKR6TTWQ3YQEF2XAVCNFSM6AAAAABA4UX5QWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBYGE2TCMRSGM.
You are receiving this because you were assigned.Message ID: @.***>

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.
The information contained in this transmission is confidential and privileged information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.
Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição


Reenable CI for Windows

CI on Windows is currently disabled because of the following issue: https://github.com/40ants/setup-lisp/issues/7

Applied workaround for setting up ultralisp on windows


hofx answers have changed

Description
answers have suddenly changed for hofx in soca
It might be due to https://github.com/JCSDA/oops/pull/4, eventhough i could have sworn that i tested to make sure answers wouldnt change with that pr. (oops!)
kdtree answers are finicky when retrieving N closest points but there happen to be > N points that are equidistant. perhaps calling reserve() first changes the way the tree happens to be partitioned at nodes with all equidistant points??
anyway, @danholdaway this might slightly impact your answers as well, if that pr is indeed the cause.

@travissluka I hope it doesn't count as jedi breaking soca when it was your own PR!!!

@travissluka I hope it doesn't count as jedi breaking soca when it was your own PR!!!

@ytremolet it sure does!


IntelliSense for Search Paths doesn't work when import folder outside the workspace.

Steps to Reproduce
1.Open a folder as workspace in SE.
2.Add new python file in SE named WholsRunningMe.py.
3.Select a python environment from the python toolbar to open PythonSettings.json and you can check “Show All Files” on the toolbar to reveal local settings.
4.Create a folder named folder1 in your local, such like : C:\project\Temp\searchpath\folder1
5.Add __init__.py in folder1 and type some code in __init__.py
def FOLDER1_MSG():      print("hello world!")
6.Add searchpaths in PythonSettings.json.

7.Type code below in WholsRunningMe.py
import folder1  folder1.FOLDER1_MSG()
7.Press F5 the output is :hello world!
8.Change using the incorrect SearchPaths to import a module that doesn’t exist in one of your environments.

9.You should see IntelliSense show squiggles on the import statement and if change to correct SearchPaths the squiggles should go away.
Expected behavior
after change to the incorrect search path outside the workspace, the IntelliSense should show squiggles on the import statement and if change to correct SearchPaths the squiggles should go away.
Actual behavior
after change to the incorrect search path outside the workspace, the IntelliSense does not show squiggles on the import statement and if change to correct SearchPaths the squiggles should go away.

duplicate as https://github.com/Microsoft/PTVS/issues/7771


Problem: Upload activity error

Describe the bug
The upload activity is failing with a cryptic error: "cannot perform operation".
To Reproduce
Steps to reproduce the behavior:

Start processing a new transfer by adding it to the Minio SIP bucket
The "upload-activity" fails with the error message "cannot perform operation".

Expected behavior
The AIP should successfully upload to the Minio "aips" bucket, and the workflow should complete successfully.


Improve diagnostics to explain why an identifier isn't a valid

This is a WIP, just changed the test cases to gauge the interest.
This spawned from my confusion in https://forums.swift.org/t/is-this-a-swiftc-bug-error-module-name-foo-is-not-a-valid-identifier/53119/5
I think we should offer more detail as to what exactly makes an identifier invalid.
Thoughts?

@amomchilov, I think this would be a really great addition.
Do you know of which code in the compiler does similar verification that we can be consistent with?

@artemcm No clue! This is my first time ever making a contribution to the Swift projects. I didn't dive much on the implementation side yet, uncertain if this is something people would ever want


PhantomJS + rejected promise + finally - test failures with assert.deepEqual

There is an issue with PhantomJS + complex promise chain with multiple catches + finally would fail unit test.
Whenever finallys are removed, tests will pass - only with finallys it breaks, because PhantomJS adds stack + other information on the thrown user error object.
https://github.com/tildeio/rsvp.js/blob/master/lib/rsvp/promise.js#L447
https://github.com/tildeio/rsvp.js/blob/v3.1.0/lib/rsvp/promise.js#L492
I have reproduction of this here - https://github.com/raido/rsvp-phatomjs-bug - look app/services/break-me.js and related unit test.
@stefanpenner

It actually fails with simple new RSVP.reject(errorObject).finally(...) - does not need complex promise chain at all.

@raido interesting, will take a look

@domenic I'm curious if you have thoughts on this.
I believe per proposed spec, finally should be implemented more or less like:
    var promise = this;
    var constructor = promise.constructor;

    return promise.then(function(value) {
      return constructor.resolve(callback()).then(function(){
        return value;
      });
    }, function(reason) {
      return constructor.resolve(callback()).then(function(){
        throw reason;
      });
    });
  }

Unfortunately, phantomjs does bad things, the throw in the failure scenario adds additional information onto the reason, causing downstream deepEquals to fail, but only in this broken browser. My gut feeling is to say throw is the right approach, and its to bad that phantom does the wrong thing. Would you agree?

Yes, that sounds right to me.

Yes, that's what I thought too.
assert.equal(errorObject.property, expectedError.property) - is way to go with such use case.


How to get/output the distance a person is away from the Kinect once their body is detected?

I'm pretty new to developing with the Kinect and I'm using the Kinect to extract data a person's movements in a room.
Firstly, I want to get the distance a person is away from the Kinect after their body has been detected using the body tracking SDK.
I'm looking to achieve something similar to the Cognitive Services example where a distance in mm is output when a person is detected.
Any suggestions are appreciated! Thanks.

My guess would be choosing a position from the body (i.e. head) and just calculate the euclidean distance to 0|0|0 because thats the position of the depth camera.
Example:
Head Position is at 2|1|1:
Distance = sqrt((2-0)²+(1-0)²+(1-0)²)

can you give me the source code please if you have.

Sorry I don't have an working example at hand, but you could check out this example on how to get all the joint positions:
https://github.com/microsoft/Azure-Kinect-Samples/blob/master/body-tracking-samples/simple_cpp_sample/main.cpp#L15
So after line 15 you would calculate the joints distance to the camera like this:
sqrt(position.v[0]*position.v[0] + position.v[1] * position.v[1] + position.v[2] + position.v[2])
For the "sqrt" function you would need to include "math.h"

Thank you.
On Wed, Feb 12, 2020 at 10:04 AM Stephan Mävers<EMAIL_ADDRESS>wrote:

Sorry I don't have an working example at hand, but you could check out
this example on how to get all the joint positions:
https://github.com/microsoft/Azure-Kinect-Samples/blob/master/body-tracking-samples/simple_cpp_sample/main.cpp#L15
So after line 15 you would calculate the joints distance to the camera
like this:
sqrt(position.v[0]*position.v[0] + position.v[1] * position.v[1] +
position.v[2] + position.v[2])
For the "sqrt" function you would need to include "math.h"
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/Azure-Kinect-Sensor-SDK/issues/1042?email_source=notifications&email_token=AIU3RCLHB5XYVPKJUMATKOTRCNDKLA5CNFSM4KJGFRSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELO4PUA#issuecomment-584959952,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIU3RCK7WJAONZ5FIP6SNGTRCNDKLANCNFSM4KJGFRSA
.

Piggy backing on this comment, is there a way to get the distance of a segmented body that does not have body tracker active on it?


Dashboard: Manual testing using keyboard and screen reader

Task Description
The editor and the dashboard need to be usable via keyboard and have sufficient screen reader support. In a first step, we need to thoroughly test the current behavior. This way, we can uncover many low-hanging fruits that we can subsequently address.
We want to fix the biggest issues in this area so that we can kick-off a full accessibility review afterwards that will actually result in useful feedback. As long as we have many well-known issues, such a review does not make sense though.
Note: Testing should be done by engineers as they have the necessary context for how the app is built and which issues are to be expected.

Some resources from the doc:
VoiceOver user guide (macOS)
ChromeVox user guide (Chromebook)
ChromeVox Classic browser extension (Google Chrome)
Web Content Accessibility Guidelines (WCAG) 2.1
Accessibility Developer Guide
Lighthouse Accessibility Audit

Refer to #4018 for resources and more infos on screen reader usage

@BrittanyIRL has started work on the keyboard audit of implemented views on Dashboard.
https://docs.google.com/spreadsheets/d/1C4rpIt9KjFDGbdJHzE7xVdBXeAejHwu4ST_-6G2glJU/edit#gid=0

@carlos-kelly @BrittanyIRL I see a number of A11y tickets have been created for dashboard. Does that mean all testing using keyboard and screen reader has been completed?
Also, mind adding them to the #117 epic so we have a clearer picture of a11y-related workload?
Thanks!

Hey, @swissspidy - the tickets made are to address p0 keyboard usability. Once that's squared away we'll do a more detail run through for screen readers. We wanted to silence any redundant noise from auditing with the known keyboard issues surrounding the grids.

Compiled findings from auditing with chrome vox, Mac voice over, axe and lighthouse. We will create new tickets for findings. Got a 100% score on lighthouse for accessibility though! Closing since testing is complete.


[WIP]Add blockNumber info for failed transactions

:x: Build AElf <IP_ADDRESS>19 failed (commit https://github.com/AElfProject/AElf/commit/54f895a7d3 by @xiangxingxing)

:white_check_mark: Build AElf <IP_ADDRESS>20 completed (commit https://github.com/AElfProject/AElf/commit/6e6d62bf1a by @xiangxingxing)

:white_check_mark: Build AElf <IP_ADDRESS>26 completed (commit https://github.com/AElfProject/AElf/commit/fff8d60c8d by @xiangxingxing)


wip Simplify state management

Summary

How did you test your changes?

https://github.com/coinbase/coinbase-wallet-sdk/pull/1331


We were writing SAM as .bam.

Feel free to squash this commit down into yours.

Thanks, nice catch!


How can I set default year to buddha year ?

https://jsfiddle.net/tj2Lo4z7/
Your Environment

flatpickr version used:
Browser name and version:
OS and version:

Hello,
I would advise taking a deep look at the documentation, which likely will contain a way to achieve what you want. These sorts of questions best belong on websites like stack overflow as the flatpickr team does not have the time to investigate each question, check for duplicates, point you to the documentation, etc.
And since this is neither a bug report nor exactly a feature request, I am closing the issue.


Use as service

Hello
Is it possible to explain how to use in service ?
thanks

What do you mean?


Close authorization tab when authorization completed.

I am not sure if this makes sense or not to do. But want to bring it up anyway.
Currently my endpoint does not answer to ?=syndicate-to, and there is no MUST for supporting such queries in the current Micropub spec. This is not an issue for Omnibear and just means it should not offer syndication options.
However, this throws an error from the micropub-helper in fetchSyndicationTargets. The browser then skip the .then() for closing the tab and goes straight into error reporting: https://github.com/keithjgrant/omnibear/blob/49e839146aef715f754837fa0a15901c73544b40/src/background.js#L65-L75
This confused me at first when I was debugging authorisation. All authorisation actions succeeded and Omnibear was usable, the tab just didn’t close.
Either chrome.tabs.remove should trigger in the catch(), or it should be moved up so the tab is closed prior to querying syndication targets.

Should be easy enough to do in conjunction with #54

Version 1.1.0 is publishing now to Chrome & Firefox stores. This should resolve this issue.


Update Spark dependencies + netty dependency on mongo side

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1908   +/-   ##
=======================================
  Coverage   65.46%   65.46%
=======================================
  Files         373      373
  Lines       18453    18453
  Branches      225      225
=======================================
  Hits        12081    12081
  Misses       6372     6372

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 ace028d...310d4c3. Read the comment docs.

@jedesah should I merge that on my own?

Thx for pointing this out, forgot to look back and see Travis had passed

Thx, I was not sure if we changed something and maybe I was suppose to do this.


refactor: upgrade go version to 1.18.6

This PR updates the go to 1.18.6.
Also updates k8s to v0.22.15.
And the linter.sh need to be updated.
related to: https://github.com/jenkins-x/jx/issues/8283

[x] Change the version in go.mod file.
[x] Run go mod tidy and ensure that it does not error out.
[x] Change GO_VERSION in makefile to the version you are upgrading.
[x] Check if there are any references to an older version and replace those.
[x] Verify that

[x] The build works by running make build.
[x] Tests are working, by running make test.
[x] Linting checks are working by running make lint.

/cc ankitm123


Color index lookup is using a deprecated enum class

The private getColorIndex() method inherited from the old Railo extension is using an apparently deprecated enum: org.apache.poi.ss.usermodel.IndexedColors. This needs replacing with org.apache.poi.hssf.util.HSSFColor.HSSFColorPredefined.
The lists are the same except for 9 additional variants in org.apache.poi.ss.usermodel.IndexedColors suffixed with the number 1:
BLACK1, WHITE1, RED1, BRIGHT_GREEN1, BLUE1, YELLOW1, PINK1, TURQUOISE1, LIGHT_TURQUOISE1
The documentation has always pointed to the correct HSSFColorPredefined class so I don't consider this to be a breaking change. Any colours ending in 1 can be mapped to the corresponding value to avoid potential "invalid" errors.

Thanks for this... I couldn't get this to work when I isolated the code and tested it.  (I thought it was just me.)  This probably contributed to my inability to pass generic color names.


Added PnP PowerShell sample to SPO-Remove-Custom-Themes

Hello
Just added PnP PowerShell sample to SPO-Remove-Custom-Themes as noticed it was missing.
Thanks
Leon

@LeonArmston thanks for the contribution, sorry for the delay in processing, this will be live shortly 😊🎉


Add ability to black/whitelist user from form

Add a button to allow for the black or whitelisting categorization on the bottom of the form.  "Are you sure?"

Done.


Use a string extension and humanizer to do a title case for first and…

… last names.

FYI, same as with textInfo.TitleCase, it looks like this doesn't do all upper case to avoid changing acronyms


Support for Single-quotes

Great module, works really well with double quoted imports, however it doesn't seem to work at all with single-quote imports.
Happy case:
import React from "react"; works.
Sad case:
import React from 'react' does not work.
Maybe it's my environment, but I don't think so. This support would be great as some linters are quite strong about single quoting!

Please disregard the above...it was my linter!


Failed to get resource

Hi,
Every time that I build or clean my application, I see a lot of "Failed to get resource" messages in the build log. My application is working fine, so far. But any idea how to solve it or should I ignore it?
Sample log:
Failed to get resource: HEAD. [HTTP HTTP/1.1 409 Conflict: http://oss.jfrog.org/artifactory/oss-snapshot-local/org/akhikhl/gradle-onejar/gradle-onejar/0.0.11/gradle-onejar-0.0.11.pom]
Failed to get resource: HEAD. [HTTP HTTP/1.1 409 Conflict: http://oss.jfrog.org/artifactory/oss-snapshot-local/commons-io/commons-io/2.4/commons-io-2.4.pom]
The reason behind the log is because the artifact does not exists in the repository. Is it expected ?
Number of fails:
$ ./gradlew build --info | grep "Conflict:" | wc -l
137

Hello,
It looks like you don't have the jcenter() repository declared in your script. Could you post the contents of your build.gradle?
It should contain both snapshot-local and jcenter(). Something like this:
buildscript {
  repositories {
    jcenter()
    maven { url 'http://oss.jfrog.org/artifactory/oss-snapshot-local' }
  }

  dependencies {
    classpath 'org.akhikhl.wuff:wuff-plugin:0.0.13-SNAPSHOT'
  }
}

repositories {
  jcenter()
  maven { url 'http://oss.jfrog.org/artifactory/oss-snapshot-local' }
}

I was able to get the same errors by removing jcenter() from the script above.

I do have Jcenter in my repositories list. This is my build.gradle
buildscript {
  repositories {
    jcenter()
    maven { url 'http://oss.jfrog.org/artifactory/oss-snapshot-local' }
  }

  dependencies {
    classpath 'org.akhikhl.wuff:wuff-plugin:0.0.13-SNAPSHOT'
  }
}

repositories {
  jcenter()
  maven { url 'http://oss.jfrog.org/artifactory/oss-snapshot-local' }
}

apply plugin: 'java'
apply plugin: 'org.akhikhl.wuff.eclipse-rcp-app'

products {
  product platform: 'linux', arch: 'x86_32'
  product platform: 'linux', arch: 'x86_64'
  product platform: 'windows', arch: 'x86_32'
  product platform: 'windows', arch: 'x86_64'
  product platform: 'macosx', arch: 'x86_64'
//  archiveProducts = true
}

run {
    if (project.hasProperty('s') && project.hasProperty('cp') ) {
        args = [
                "-s", project.s,
                "-cp", project.cp
        ]
    }
}

dependencies {
  runtime "${eclipseMavenGroup}:org.eclipse.equinox.p2.repository:+"
  runtime "${eclipseMavenGroup}:org.eclipse.equinox.p2.metadata.repository:+"
}

based on mcmill input. I realized that this issue was caused because gradle was looking for resources in  jcenter and jfrog before going to local maven repository. I've added mavenLocal() as my first repository and the issues are gone now.
my build.gradle:
buildscript {
  repositories {
    mavenLocal()
    jcenter()
    maven { url 'http://oss.jfrog.org/artifactory/oss-snapshot-local' }
  }

  dependencies {
    classpath 'org.akhikhl.wuff:wuff-plugin:0.0.13-SNAPSHOT'
  }
}

repositories {
  mavenLocal()
  jcenter()
  maven { url 'http://oss.jfrog.org/artifactory/oss-snapshot-local' }
}

apply plugin: 'java'
apply plugin: 'org.akhikhl.wuff.eclipse-rcp-app'

products {
  product platform: 'linux', arch: 'x86_32'
  product platform: 'linux', arch: 'x86_64'
  product platform: 'windows', arch: 'x86_32'
  product platform: 'windows', arch: 'x86_64'
  product platform: 'macosx', arch: 'x86_64'
//  archiveProducts = true
}

run {
    if (project.hasProperty('s') && project.hasProperty('cp') ) {
        args = [
                "-s", project.s,
                "-cp", project.cp
        ]
    }
}

dependencies {
  runtime "${eclipseMavenGroup}:org.eclipse.equinox.p2.repository:+"
  runtime "${eclipseMavenGroup}:org.eclipse.equinox.p2.metadata.repository:+"
}


Activate on scroll rather then on load

If I enter AOS.init() then this will cause the library to start on page. I have adjusted the call to only load on the scroll event. However, I noticed it is still being initialized on page load.
The reason I would like to do this onscroll is because search engines bots don't use the scroll event and I would like all elements to be visible to them. For SEO purposes, anything that is hidden is given a lower weight even though it is still visible.
Questions

Am I missing something here?
How can I be sure the library is only initialized on scroll?

This is:

Question

Specifications

AOS version: 2.3.4
OS: Windows 10
Browser: Chrome 76.0.3809.132

Expected Behavior
Only initialized AOS when the scroll event occurs.
Actual Behavior
AOS is initialized on page load.
Steps to Reproduce the Problem

Add aos.css using CDN to the <head>
Add aos.js to the end of the <body>
Using jQuery detect if scroll event occurs, if so then initialized AOS else don't.

Detailed Description

Possible Solution

AOS.init() should only be initialized on scroll event.
Add a setting to detect scroll event so it can be passed into the .init()

Code used to load on scroll (assumes latest jquery version is used)
$(function() {     $(window).on('scroll', function() {        AOS.init();    }); });

@rruprai have you found a solution to this?

@molerat619
No, the possible solution didn't work. Any help on this would be appreciated.

This worked for me :) https://github.com/michalsnik/aos/issues/635

I ended up going for this appraoch:
npm install is-web-crawler

And in the application, simply initialising AOS with the disable flag when the current user agent represents a "known" crawler.
import { isCrawlerUserAgent } from 'is-web-crawler';

AOS.init({
    disable: isCrawlerUserAgent(),
});

Disclaimer: I created the is-web-crawler library, but simply for the purpose of this use case.


1.0.3: failure on creating environment via python3 version not from PATH

Describe the bug
Plugin uses python3 path from PATH not from 'create poetry dialog' and could fail on multiple Python3 version installed.
To Reproduce
Steps to reproduce the behavior:

macos
have three versions of Python3 installed on machine: 3.6, 3.7, 3.8 with 3.7 as default:

$ which python3
/usr/local/bin/python3

$ /usr/local/bin/python3 -V
Python 3.7.9

$ which -a python3
/usr/local/bin/python3
/Library/Frameworks/Python.framework/Versions/3.7/bin/python3
/Library/Frameworks/Python.framework/Versions/3.6/bin/python3
/Library/Frameworks/Python.framework/Versions/3.8/bin/python3

install poetry on every Python3 version via 'path/../python3 -m pip install poetry==1.1.4'
open project with python version required as "^3.8" in Pycharm 2020.3.3 with Poetry plugin v1.0.3

Expected behavior
created poetry environment
Screenshots

If applicable, add screenshots to help explain your problem.
Environments (please complete the following information):
Already done above.
It might be helpful to move this section to the top of the form.
Additional context
Full text from error window:
executed command

/Library/Frameworks/Python.framework/Versions/3.8/bin/poetry env use /usr/local/bin/python3

  NoCompatiblePythonVersionFound

  The specified Python version (3.7.9) is not supported by the project (^3.8).
  Please choose a compatible version or loosen the python constraint specified in the pyproject.toml file.

  at /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/poetry/utils/env.py:675 in create_venv
       671│             # If an executable has been specified, we stop there
       672│             # and notify the user of the incompatibility.
       673│             # Otherwise, we try to find a compatible Python version.
       674│             if executable:
    →  675│                 raise NoCompatiblePythonVersionFound(
       676│                     self._poetry.package.python_versions, python_patch
       677│                 )
       678│
       679│             io.write_line(

@abcdenis
Thank you for creating this issue.
I can see you selected /usr/local/bin/python3  for a project with python version required as "^3.8"
But, you show me /usr/local/bin/python3 is Python 3.7.9.
I guess the error is correct.
$ /usr/local/bin/python3 -V
Python 3.7.9

However, PyCharm displays Python version 3.8 in the list. It's interesting.
The version may be wrong. 🤔

I used to see this bug in PyCharm. I will check and notify PyCharm developers if need. Thank you for suggestion.


bcachefs-tools: 1.3.3 -> 1.3.5

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for bcachefs-tools is: Tool for managing bcachefs filesystems
meta.homepage for bcachefs-tools is: https://bcachefs.org/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 1.3.5 with grep in /nix/store/p5fywnivf478sc3d2w8sp32gj7nsk372-bcachefs-tools-1.3.5
found 1.3.5 in filename of file in /nix/store/p5fywnivf478sc3d2w8sp32gj7nsk372-bcachefs-tools-1.3.5

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
bcachefs-tools

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/p5fywnivf478sc3d2w8sp32gj7nsk372-bcachefs-tools-1.3.5 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A bcachefs-tools https://github.com/r-ryantm/nixpkgs/archive/8d76f5ce4d152e24e2790afefd71146614ef84dc.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/8d76f5ce4d152e24e2790afefd71146614ef84dc#bcachefs-tools

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/p5fywnivf478sc3d2w8sp32gj7nsk372-bcachefs-tools-1.3.5
ls -la /nix/store/p5fywnivf478sc3d2w8sp32gj7nsk372-bcachefs-tools-1.3.5/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

bcachefs-tools

Maintainer pings
cc @davidak @Madouura for testing.

bcachefs kernel is failing on master AFAIK currently, so there's no way to test this PR.
#268394 addresses this and includes this version bump already.

On second thought, this PR CAN be somewhat tested using bcachefsLinuxTesting.
Unfortunately the rest of the tests are broken due to the broken old bcachefs kernel.
Honestly, we can merge this as-is as long as we test at least bcachefsLinuxTesting.


Excessive logging

I'm seeing cases with excessive logging, eg:
This seems to be impacting the way the system responds, perhaps there's some issue being raised here in the trasnfer of these domains from this server?
Sep  3 20:46:30 puck nsd[852]: [2019-09-03 20:46:30.543] nsd[852]: error: xfrd: zone fleischer.hu received error code NOT IMPL from <IP_ADDRESS>
Sep  3 20:46:30 puck nsd[852]: xfrd: zone fleischer.hu received error code NOT IMPL from <IP_ADDRESS>
Sep  3 20:46:30 puck nsd[852]: [2019-09-03 20:46:30.545] nsd[852]: error: xfrd: zone fleischer.hu received error code NOT IMPL from <IP_ADDRESS>
Sep  3 20:46:30 puck nsd[852]: xfrd: zone fleischer.hu received error code NOT IMPL from <IP_ADDRESS>
Sep  3 20:46:30 puck nsd[852]: [2019-09-03 20:46:30.548] nsd[852]: error: xfrd: zone fleischer.hu received error code NOT IMPL from <IP_ADDRESS>
Sep  3 20:46:30 puck nsd[852]: xfrd: zone fleischer.hu received error code NOT IMPL from <IP_ADDRESS>
Sep  3 20:46:30 puck nsd[852]: [2019-09-03 20:46:30.550] nsd[852]: error: xfrd: zone fleischer.hu received error code NOT IMPL from <IP_ADDRESS>
Sep  3 20:46:30 puck nsd[852]: xfrd: zone fleischer.hu received error code NOT IMPL from <IP_ADDRESS>
Sep  3 20:46:30 puck nsd[852]: [2019-09-03 20:46:30.551] nsd[852]: error: xfrd: zone fleischer.hu received error code NOT IMPL from <IP_ADDRESS>
Sep  3 20:46:30 puck nsd[852]: xfrd: zone fleischer.hu received error code NOT IMPL from <IP_ADDRESS>
Sep  3 20:46:30 puck nsd[852]: [2019-09-03 20:46:30.554] nsd[852]: error: xfrd: zone fleischer.hu received error code NOT IMPL from <IP_ADDRESS>
Sep  3 20:46:30 puck nsd[852]: xfrd: zone fleischer.hu received error code NOT IMPL from <IP_ADDRESS>
Sep  3 20:46:30 puck nsd[852]: [2019-09-03 20:46:30.555] nsd[852]: error: xfrd: zone fleischer.hu received error code NOT IMPL from <IP_ADDRESS>
Sep  3 20:46:30 puck nsd[852]: xfrd: zone fleischer.hu received error code NOT IMPL from <IP_ADDRESS>
Sep  3 20:46:30 puck nsd[852]: [2019-09-03 20:46:30.557] nsd[852]: error: xfrd: zone fleischer.hu received error code NOT IMPL from <IP_ADDRESS>
Sep  3 20:46:30 puck nsd[852]: xfrd: zone fleischer.hu received error code NOT IMPL from <IP_ADDRESS>
Sep  3 20:46:30 puck nsd[852]: [2019-09-03 20:46:30.560] nsd[852]: error: xfrd: zone fleischer.hu received error code NOT IMPL from <IP_ADDRESS>
Sep  3 20:46:30 puck nsd[852]: xfrd: zone fleischer.hu received error code NOT IMPL from <IP_ADDRESS>
Sep  3 20:46:30 puck nsd[852]: [2019-09-03 20:46:30.562] nsd[852]: error: xfrd: zone fleischer.hu received error code NOT IMPL from <IP_ADDRESS>
Sep  3 20:46:30 puck nsd[852]: xfrd: zone fleischer.hu received error code NOT IMPL from <IP_ADDRESS>
Sep  3 20:46:30 puck nsd[852]: [2019-09-03 20:46:30.565] nsd[852]: error: xfrd: zone fleischer.hu received error code NOT IMPL from <IP_ADDRESS>
Sep  3 20:46:30 puck nsd[852]: xfrd: zone fleischer.hu received error code NOT IMPL from <IP_ADDRESS>
Sep  3 20:46:30 puck nsd[852]: [2019-09-03 20:46:30.568] nsd[852]: error: xfrd: zone fleischer.hu received error code NOT IMPL from <IP_ADDRESS>
Sep  3 20:46:30 puck nsd[852]: xfrd: zone fleischer.hu received error code NOT IMPL from <IP_ADDRESS>
Sep  3 20:46:30 puck nsd[852]: [2019-09-03 20:46:30.570] nsd[852]: error: xfrd: zone fleischer.hu received error code NOT IMPL from <IP_ADDRESS>
Sep  3 20:46:30 puck nsd[852]: xfrd: zone fleischer.hu received error code NOT IMPL from <IP_ADDRESS>
Sep  3 20:46:30 puck nsd[852]: [2019-09-03 20:46:30.573] nsd[852]: error: xfrd: zone fleischer.hu received error code NOT IMPL from <IP_ADDRESS>
Sep  3 20:46:30 puck nsd[852]: xfrd: zone fleischer.hu received error code NOT IMPL from <IP_ADDRESS>
Sep  3 20:46:30 puck nsd[852]: [2019-09-03 20:46:30.575] nsd[852]: error: xfrd: zone fleischer.hu received error code NOT IMPL from <IP_ADDRESS>
Sep  3 20:46:30 puck nsd[852]: xfrd: zone fleischer.hu received error code NOT IMPL from <IP_ADDRESS>
Sep  3 20:46:30 puck nsd[852]: [2019-09-03 20:46:30.578] nsd[852]: error: xfrd: zone fleischer.hu received error code NOT IMPL from <IP_ADDRESS>
Sep  3 20:46:30 puck nsd[852]: xfrd: zone fleischer.hu received error code NOT IMPL from <IP_ADDRESS>
Sep  3 20:46:30 puck nsd[852]: [2019-09-03 20:46:30.580] nsd[852]: error: xfrd: zone fleischer.hu received error code NOT IMPL from <IP_ADDRESS>
Sep  3 20:46:30 puck nsd[852]: xfrd: zone fleischer.hu received error code NOT IMPL from <IP_ADDRESS>

The fix stops the logs unless you set high verbosity.
The log is stopped when an axfr fallback is possible.  The reason you see these logs is that that server does not respond to IXFR queries.  You could configure it with AXFR in the request-xfr line in nsd.conf and then it only sends AXFR requests to it.

The config explicitly says AXFR, eg:
    request-xfr: AXFR <IP_ADDRESS> NOKEY

I'm guessing that hint isn't enough to avoid IXFR?

It should be, and then the patch does not remove the log lines either.  The upstream server does not support AXFR, it seems.

Eg. a server like unbound would respond that way.

I swear my free dns service i run is like EFT for DNS software .. found so many interesting server behaviors.


Allow direct connections

OP#505

Code Review Checklist

[ ] Description accurately reflects what changes are being made.
[ ] Description explains why the changes are being made (or references an issue containing one).
[ ] The PR appropriately sized.
[ ] New code has enough tests.
[ ] New code has enough documentation to answer "how do I use it?" and "what does it do?".
[ ] Existing documentation is up-to-date, if impacted.

I think we have to merge this together with https://github.com/LeastAuthority/wormhole-william/pull/84. As current w-w version doesn't work correctly and thats why in some case hanging (hanging because sender and receiver looks at different relay services)


Missing Android example

The readme says "We have a similar pattern available for Android, as well!" however that link (https://github.com/IBM/weather-forecasting-android) doesn't seem to exists. Searching all of the repos in the IBM org don't seem to show the proper example.

eek, that was done preemptively when we were porting the android starter kit over, but noticed issued while running it, i'll remove that mention.

there's going to be a similar mention in every starter kit that was
supposed to be published with an Android version (4 total?)
On Sun, Apr 21, 2019, 9:54 PM Steve Martinelli<EMAIL_ADDRESS>wrote:

eek, that was done preemptively when we were porting the android starter
kit over, but noticed issued while running it, i'll remove that mention.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/IBM/weather-forecasting-ios/issues/7#issuecomment-485309317,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAF7OO3X4L46RII74TSYSQ3PRUSETANCNFSM4HHM2LAA
.

@dolph i'm cleaning those up as well.
@derekteay i removed the mention just now. sorry about the confusion.


RouteMagic on Mono

I'm using the default project for Nuget.Server package, that uses routemagic.
When I click at "nuget/Packages" link, i got a 404.
Using nginx with mono framework 4.

Seems that the problem is that WebActivatorEx not calling Start on Mono. Moved things to GlobalAsax.


serverobj failed to link librt when cross compiling using ubuntu 20.04

I'm trying to cross compile netopeer2 for arm using compiler aarch64-linux-gnu-gcc-10 on a docker ubuntu 20.04.
Netopeer2 is failing to complete build due to the error below.
>>> Building netopeer2-2.2.31
[  5%] Building C object CMakeFiles/serverobj.dir/src/common.c.o
[ 11%] Building C object CMakeFiles/serverobj.dir/src/netconf.c.o
[ 16%] Building C object CMakeFiles/serverobj.dir/src/netconf_monitoring.c.o
[ 22%] Building C object CMakeFiles/serverobj.dir/src/netconf_nmda.c.o
[ 27%] Building C object CMakeFiles/serverobj.dir/src/netconf_subscribed_notifications.c.o
[ 33%] Building C object CMakeFiles/serverobj.dir/src/netconf_confirmed_commit.c.o
[ 38%] Building C object CMakeFiles/serverobj.dir/src/log.c.o
[ 44%] Building C object CMakeFiles/serverobj.dir/src/err_netconf.c.o
[ 44%] Built target serverobj
[ 50%] Building C object CMakeFiles/netopeer2-server.dir/src/main.c.o
[ 55%] Building C object CMakeFiles/netopeer2-server.dir/compat/compat.c.o
[ 61%] Linking C executable netopeer2-server
/usr/lib/gcc-cross/aarch64-linux-gnu/10/../../../../aarch64-linux-gnu/bin/ld: CMakeFiles/serverobj.dir/src/netconf_confirmed_commit.c.o: in function `ncc_commit_confirmed':
netconf_confirmed_commit.c:(.text+0x164): undefined reference to `timer_delete'
/usr/lib/gcc-cross/aarch64-linux-gnu/10/../../../../aarch64-linux-gnu/bin/ld: CMakeFiles/serverobj.dir/src/netconf_confirmed_commit.c.o: in function `ncc_commit_ctx_destroy':
netconf_confirmed_commit.c:(.text+0xc0c): undefined reference to `timer_delete'
/usr/lib/gcc-cross/aarch64-linux-gnu/10/../../../../aarch64-linux-gnu/bin/ld: CMakeFiles/serverobj.dir/src/netconf_confirmed_commit.c.o: in function `np2srv_rpc_commit_cb':
netconf_confirmed_commit.c:(.text+0x121c): undefined reference to `timer_delete'
/usr/lib/gcc-cross/aarch64-linux-gnu/10/../../../../aarch64-linux-gnu/bin/ld: netconf_confirmed_commit.c:(.text+0x147c): undefined reference to `timer_create'
/usr/lib/gcc-cross/aarch64-linux-gnu/10/../../../../aarch64-linux-gnu/bin/ld: netconf_confirmed_commit.c:(.text+0x1498): undefined reference to `timer_settime'
collect2: error: ld returned 1 exit status
make[2]: *** [CMakeFiles/netopeer2-server.dir/build.make:134: netopeer2-server] Error 1
make[1]: *** [CMakeFiles/Makefile2:130: CMakeFiles/netopeer2-server.dir/all] Error 2
make: *** [Makefile:136: all] Error 2

I could complete the build by manually including "rt" to target_link_libraries in the main CMakeLists.txt , but I'm wondering if that's an issue that can be fixed or is there any way I can pass in that dependency to cmake.
# install the binary, required modules, and default configuration
if(BUILD_SERVER)
    target_link_libraries(netopeer2-server rt ${serverlibs})
    install(TARGETS netopeer2-server DESTINATION ${CMAKE_INSTALL_SBINDIR})
    install(FILES ${PROJECT_SOURCE_DIR}/doc/netopeer2-server.8 DESTINATION ${CMAKE_INSTALL_MANDIR}/man8)
    if(NP2SRV_HAVE_SYSTEMD)
        install(FILES ${PROJECT_BINARY_DIR}/netopeer2-server.service DESTINATION ${SYSTEMD_UNIT_DIR})
    endif()
endif()

Thanks

It should be linked by default. But it likely the library is not properly found when cross-compiling so just manually set LIBRT when executing cmake and it should be linked.

That worked indeed. Many thanks!


Support legacy _links LFS batch responses

Support legacy _links LFS batch response.
Fixes #31512.
This is backwards-compatible change to the LFS client so that, upon mirroring from an upstream which has a batch api, it can download objects whether the responses contain the _links field or its successor the actions field. When Gitea must fallback to the legacy _links field a logline is emitted at INFO level which looks like this:
...s/lfs/http_client.go:188:performOperation() [I] <LFSPointer ee95d0a27ccdfc7c12516d4f80dcf144a5eaf10d0461d282a7206390635cdbee:160> is using a deprecated batch schema response!

I've only run test-backend with this code, but added a new test to cover this case. Additionally I have a fork with this change deployed which I've confirmed syncs LFS from Gitea<-Artifactory (which has legacy _links) as well as from Gitea<-Gitea (which has the modern actions).

thanks for the review @wxiaoguang , updated with your suggestions and force pushed

@rremer please fix the merge conflicts. :tea:


Disable randomly failing HA tests

TestHARead and TestHAFileCreationMultipleNNFailure are randomly failing. Probably because of race conditions. The test will be disabled for now. A second issue for revising these test cases was created.

Jenkins, retest this please.


ruby host profile was missing in 3.4.1 LLNL CZ install

Describe the bug
Not sure why, it is in our repo.
I added it back manually for 3.4.1.

The visit-install script explicitly copies individual host profiles when doing "llnl_open_cz" to avoid installing RZ host profiles. Ruby isn't one of the listed host profiles.
Here is the code:
# Copy the files explicitly to avoid the rz hosts. We're most likely installing on a cz machine.
   cp "$dir"/$version+/$platformDir/resources/hosts/llnl/host_llnl_ansel.xml    "$dir"/$version+/.visit/hosts/
   cp "$dir"/$version+/$platformDir/resources/hosts/llnl/host_llnl_borax.xml    "$dir"/$version+/.visit/hosts/
   cp "$dir"/$version+/$platformDir/resources/hosts/llnl/host_llnl_lassen.xml   "$dir"/$version+/.visit/hosts/
   cp "$dir"/$version+/$platformDir/resources/hosts/llnl/host_llnl_oslic.xml    "$dir"/$version+/.visit/hosts/
   cp "$dir"/$version+/$platformDir/resources/hosts/llnl/host_llnl_pascal.xml   "$dir"/$version+/.visit/hosts/
   cp "$dir"/$version+/$platformDir/resources/hosts/llnl/host_llnl_poodle.xml   "$dir"/$version+/.visit/hosts/
   cp "$dir"/$version+/$platformDir/resources/hosts/llnl/host_llnl_quartz.xml   "$dir"/$version+/.visit/hosts/
   cp "$dir"/$version+/$platformDir/resources/hosts/llnl/host_llnl_surface.xml  "$dir"/$version+/.visit/hosts/
   cp "$dir"/$version+/$platformDir/resources/hosts/llnl/host_llnl_syrah.xml    "$dir"/$version+/.visit/hosts/
   cp "$dir"/$version+/$platformDir/resources/hosts/llnl/host_llnl_vulcan.xml   "$dir"/$version+/.visit/hosts/
   cp "$dir"/$version+/$platformDir/resources/hosts/llnl/host_slac_red.xml      "$dir"/$version+/.visit/hosts/

Here are the host profiles in the llnl directory:
config		      host_llnl_pascal.xml   host_llnl_rztrona.xml
customlauncher	      host_llnl_poodle.xml   host_llnl_rzwhippet.xml
host_llnl_ansel.xml   host_llnl_quartz.xml   host_llnl_surface.xml
host_llnl_boraxo.xml  host_llnl_ruby.xml     host_llnl_syrah.xml
host_llnl_borax.xml   host_llnl_rzansel.xml  host_llnl_vulcan.xml
host_llnl_dane.xml    host_llnl_rzgenie.xml  host_slac_red.xml
host_llnl_lassen.xml  host_llnl_rzhound.xml
host_llnl_oslic.xml   host_llnl_rztopaz.xml

Looks like we should add boraxo, dane, and ruby. Probably can remove rztopaz, surface and vulcan. I'm not sure about slac_red, it's been there forever.

This is a duplicate of #18722.


Video block has an aria-label on the div

Apparently div's aren't supposed to have aria labels.   Giving the following accessibility issue in site improve:
An ARIA attribute has been specified that is either not supported or is prohibited, on this type of element.

according to https://www.davidmacd.com/blog/does-aria-label-override-static-text.html#:~:text=By design%2C aria-label or,ignored by VoiceOver on iOS).
DIVs should only have aria labels if they have role=navigation, search, main, img
Based on this, the aria-label on the video embed div should be removed.


[DO NOT MERGE][waiting Google Colab updates] change argument method_whitelist to allowed_methods

WHAT
The argument method_whitelist will be deprecated in v1.26.0, therefore change to allowed_methods.
WHY

https://urllib3.readthedocs.io/en/stable/reference/urllib3.util.html?highlight=retry#urllib3.util.Retry
Previously this parameter was named method_whitelist, that usage is deprecated in v1.26.0 and will be removed in v2.0.

@drillan
Thank you for this PR.
Please let me keep this PR until Google Colab updates the version of urllib3 into 1.26.0+.
The jquants-api-client-python supports Google Colab and the version of urllib3 is 1.24.3 in Google Cola [*1].
The urllib3 version of 1.24.3 unfortunately does not support allowed_methods. The allowed_methods is introduced at 1.26.0 of urllib3. [*2]
Currently, we also freeze the version in the project.toml file in jquants-api-client currently. [*3]
*1 Google Colab's urlib3 version as of 2022-10-29
! python3 -m pip freeze | grep -e urllib
urllib3==1.24.3

*2 urllib3's changelog to introduce allowed_methods
https://github.com/urllib3/urllib3/blob/main/CHANGES.rst#1260-2020-11-10
*3 freezing the version of urllib3 in project.toml at v0.1.5 of jquants-api-client-python
https://github.com/J-Quants/jquants-api-client-python/blob/v0.1.5/pyproject.toml#L41

fyi. v2 of requests also freeze the version of urllib3 as urllib3>=1.21.1,<1.27.
https://github.com/psf/requests/blob/v2.28.1/setup.cfg#L10

Google Colab's urlib3 version as of 2022-12-13
still not ready to merge this PR (urllib3 should be >=1.26.0). Let me please keep eye on it.
! python3 --version
! python3 -m pip freeze | grep -e urllib
Python 3.8.16
urllib3==1.24.3

urllib3 in colab is updated to 1.26.14.
https://github.com/googlecolab/backend-info/commit/0ff69153bebe4d76e04fd2ab71b339c4a05c4477#diff-50ad98ca28a70b8ef1f29b98c8f9a8166c902329a68d2abe996105cb0ee911afR400

TODO:

update required version for urllib3 = "^1.26.0"

https://github.com/J-Quants/jquants-api-client-python/blob/v0.1.5/pyproject.toml#L41


Update protobuf compiler, move to new/correct path for golang protobufs, enable tests for protobuf changes.

After this change is released, I can update dovesnap to use the new path, then remove the "faucetconfrpc" directory.


timeline / isMediaPlaying giving parse error

When trying to use the timeline and isMediaPlaying options I get the following parse error:
requests.exceptions.InvalidURL: Failed to parse: 192-168-1-134.longstingoflettersnumberhere.plex.direct:32400timeline
I'm trying it as follows from a python console:
from plexapi.myplex import MyPlexUser
user = MyPlexUser.signin(PLEXUN, PLEXPW)
plex = user.getResource(PLEXSVR).connect()
client = plex.client(CLIENT)
client.isPlayingMedia()
(OR)
client.timeline()
and then I get the above error.
Am I doing something wrong to cause that parse error?

Thanks for the bug. Looks like there is a missing slash before the word timeline in the url. Are you using the version from pip or the most current version from github?

I have been using the version off pip.

I think this bug may be invalid then. I'll retest the current master to double check before closing the bug.  A new version of this library should hit pip within a week or two.
There are a few api changes, but you are welcome to try this version in your project if you're OK with a few changes before I release to pip.
pip install -U git+git://github.com/mjs7231/python-plexapi.git

Thanks for the followup. I'll give that version a try tonight.

Using that version I was able to successfully use both actions. Thanks again for the followup.

Is it possible to add in the isMediaPlaying function a second condition so paused content is not treated the same as stopped? I now use this to determine when something is playing vs stopped, and I don't want to react to paused content like it were stopped. In my local copy I the following to that function:
elif mediatype.get('state') == 'paused':
return True
Thought others might want to use it the same way and might find that useful.

Seems reasonable.
commit 0c8587ceac3186767ac06681ef7372d8e43e85a5
Author: Michael Shepanski<EMAIL_ADDRESS>Date:   Mon May 23 19:33:56 2016 -0400
Option to include paused content when requesting is media is playing.


⚠ Mobitopup has degraded performance

In e986949, Mobitopup (https://napcard.voz.tech) experienced degraded performance:

HTTP code: 200
Response time: 11498 ms

Resolved: Mobitopup performance has improved in e423f97.


Demo/initial-setup

I am now confident enough with this project to pursue the merge of the main and demo-initial-setup branches. The project has reached a stable state with implemented session-based conversations for chatbot clients and authentication and authorization for corporations. All key tasks, including database and API integrations, have been completed, and the README has been updated accordingly. This merge will consolidate the progress made and prepare the project for further development.

Merged demo-initial-setup branch into main
Successfully merged the demo-initial-setup branch into the main branch. This merge consolidates key features and setups with a current status "done" in README.md.


Error: "cmd/search/search: Bad CPU type in executable"

Hello,
Problem: When trying to search using this workflow, I type in "bs test". The workflow disappears after I start typing "test" and Alfred falls back to my default searches. This happens regardless of my search term; this is just what I was testing with today.
The debug log shows errors like this every time:
[13:00:07.332] Logging Started...
[13:00:57.506] Bear[Script Filter] Queuing argument 'test'
[13:00:57.526] Bear[Script Filter] Script with argv 'test' finished
[13:00:57.532] ERROR: Bear[Script Filter] Code 126: /Users/james_simas/Library/Caches/com.runningwithcrayons.Alfred/Workflow Scripts/0E686738-AF36-4F1A-9B8E-5BC579ED706A: line 1: cmd/search/search: Bad CPU type in executable

I'm running a MacBook Pro with an M1. Is this architecture supported?
Let me know if you need any additional info.
Thanks!
Versions:

macOS: 13.5.1
Alfred: 5.1.2 [2145]
alfred-bear: v1.2.1

I have the exact same specs as you do, down to the software versions and M1 MacBook Pro. It's the primary development environment.
Have you installed Rosetta? This is executable type is necessary to keep the workflow compatible with Intel Macs:
https://github.com/drgrib/alfred-bear#-apple-silicon-macs

Ah, no, I haven't installed Rosetta. That would do it.
Thanks and apologies for missing that in the README.


[test me] compile_time works with Chef 11/12 including chef-sugar

The test recipe is the following (please note that this is the patched aws from this PR, with a little difference to trigger warning, see below):
include_recipe 'chef-sugar'
include_recipe 'aws'

chef_gem patched code (compile_time is not set to anything to trigger the warning):
chef_gem 'aws-sdk' do
  version node['aws']['aws_sdk_version']
  if Chef::Resource::ChefGem.instance_methods(false).include?(:compile_time)
    compile_time
  end
  action :install
end

Here are my results:
Chef 12.1.0.dev.0, without specifying true, just compile_time to show the warning :
==> zs1: [2015-02-19T06:47:57+00:00] INFO: Forking chef instance to converge...
==> zs1: [2015-02-19T06:47:57+00:00] INFO: *** Chef 12.1.0.dev.0 ***
==> zs1: [2015-02-19T06:47:57+00:00] INFO: Chef-client pid: 14440
==> zs1: [2015-02-19T06:48:15+00:00] WARN: chef_gem[chef-sugar] chef_gem compile_time installation is deprecated
==> zs1: [2015-02-19T06:48:15+00:00] WARN: chef_gem[chef-sugar] Please set `compile_time false` on the resource to use the new behavior.
==> zs1: [2015-02-19T06:48:15+00:00] WARN: chef_gem[chef-sugar] or set `compile_time true` on the resource if compile_time behavior is required.
==> zs1: [2015-02-19T06:48:23+00:00] INFO: chef_gem[chef-sugar] installed chef-sugar at 2.5.0
==> zs1: [2015-02-19T06:48:23+00:00] WARN: chef_gem[aws-sdk] chef_gem compile_time installation is deprecated
==> zs1: [2015-02-19T06:48:23+00:00] WARN: chef_gem[aws-sdk] Please set `compile_time false` on the resource to use the new behavior.
==> zs1: [2015-02-19T06:48:23+00:00] WARN: chef_gem[aws-sdk] or set `compile_time true` on the resource if compile_time behavior is required.
==> zs1: [2015-02-19T06:48:31+00:00] INFO: chef_gem[aws-sdk] installed aws-sdk at ~> 2.0.22
==> zs1: [2015-02-19T06:48:32+00:00] INFO: Chef Run complete in 28.265871351 seconds

Chef 12.0.3, don't see any log, but both gems are installed:
==> zs1: [2015-02-19T06:53:56+00:00] INFO: *** Chef 12.0.3 ***
==> zs1: [2015-02-19T06:53:56+00:00] INFO: Chef-client pid: 14938
==> zs1: [2015-02-19T06:54:24+00:00] INFO: Chef Run complete in 20.955133524 seconds

root@mesosphere-scalp-vagrant-vbox-1:~# /opt/chef/embedded/bin/gem list | grep chef
chef (12.0.3)
chef-sugar (2.5.0)
chef-zero (3.2.1)
root@mesosphere-scalp-vagrant-vbox-1:~# /opt/chef/embedded/bin/gem list | grep aws
aws-sdk (2.0.26)
aws-sdk-core (2.0.26)
aws-sdk-resources (2.0.26)

Chef 11.16.4, don't see any log, but both gems are installed:
==> zs1: [2015-02-19T06:56:38+00:00] INFO: *** Chef 11.16.4 ***
==> zs1: [2015-02-19T06:56:38+00:00] INFO: Chef-client pid: 15433
==> zs1: /var/chef/cache/cookbooks/homebrew/libraries/homebrew_package.rb:26: warning: toplevel constant Homebrew referenced by Chef::Provider::Package::Homebrew
==> zs1: [2015-02-19T06:57:47+00:00] INFO: Chef Run complete in 25.402963436 seconds

root@mesosphere-scalp-vagrant-vbox-1:~# /opt/chef/embedded/bin/gem list | grep chef
chef (11.16.4)
chef-sugar (2.5.0)
chef-zero (2.2)
root@mesosphere-scalp-vagrant-vbox-1:~# /opt/chef/embedded/bin/gem list | grep aws
aws-sdk (2.0.26)
aws-sdk-core (2.0.26)
aws-sdk-resources (2.0.26)

Chef 11.18.6, don't see any log, but both gems are installed:
==> zs1: [2015-02-19T06:58:47+00:00] INFO: *** Chef 11.18.6 ***
==> zs1: [2015-02-19T06:58:47+00:00] INFO: Chef-client pid: 16297
==> zs1: /var/chef/cache/cookbooks/homebrew/libraries/homebrew_package.rb:26: warning: toplevel constant Homebrew referenced by Chef::Provider::Package::Homebrew
==> zs1: [2015-02-19T06:59:22+00:00] INFO: Chef Run complete in 27.925290915 seconds

root@mesosphere-scalp-vagrant-vbox-1:~# /opt/chef/embedded/bin/gem list | grep chef
chef (11.18.6)
chef-sugar (2.5.0)
chef-zero (2.2.1)
root@mesosphere-scalp-vagrant-vbox-1:~# /opt/chef/embedded/bin/gem list | grep aws
aws-sdk (2.0.26)
aws-sdk-core (2.0.26)
aws-sdk-resources (2.0.26)

I also tried with chef_12.2.0-alpha.0-1_amd64.deb (which does not support compile_time):
==> zs1: [2015-02-19T07:00:55+00:00] INFO: *** Chef 12.2.0.alpha.0 ***
==> zs1: [2015-02-19T07:00:55+00:00] INFO: Chef-client pid: 16759
==> zs1: [2015-02-19T07:01:41+00:00] INFO: Starting audit phase
==> zs1: [2015-02-19T07:01:42+00:00] INFO: Successfully executed all controls blocks and contained examples
==> zs1:
==> zs1: Finished in 0.00018 seconds (files took 0.35235 seconds to load)
==> zs1: 0 examples, 0 failures
==> zs1: [2015-02-19T07:01:42+00:00] INFO: Chef Run complete in 39.759534584 seconds

root@mesosphere-scalp-vagrant-vbox-1:~# /opt/chef/embedded/bin/gem list | grep chef
chef (12.2.0.alpha.0)
chef-sugar (2.5.0)
chef-zero (3.2)
root@mesosphere-scalp-vagrant-vbox-1:~# /opt/chef/embedded/bin/gem list | grep aws
aws-sdk (2.0.26)
aws-sdk-core (2.0.26)
aws-sdk-resources (2.0.26)

I'm mostly breaking "something" as I don't see the resource being listed in the log but hopefully it helps.

@scalp42 you need to provide a value for compile_time I think

@sethvargo it doesn't work though.

@scalp42 as @sethvargo mentioned you need to provide true to compile_time as an argument there.

This is essentially the same fix as https://github.com/opscode-cookbooks/chef-vault/commit/4739a6561a28f7ac7ea638dfef9c5634ef4171f8 - because I stole this for that one (thanks @scalp42!).

For the record, I have renamed the function in Chef Sugar v3.0.1 to at_compile_time to avoid the conflict.

Thanks @sethvargo for reconsidering it.


Validators queryRules maximum results value throwing exception

Reproduction steps:

Create a Validator.php file for the resourse. E.g. app/JsonApi/Item/Validators.php

Change the queryRules() method to:
/**
 * @return array
 */
protected function queryRules(): array
{
    return [
        'page.number' => 'filled|numeric|min:1',
        'page.size' => 'filled|numeric|between:1,50',
    ];
}

Send a GET request to the resource endpoint with a page.size value greater than the maximum value set in the queryRules(), e.g. http://api.example.test/api/v1/item?page[number]=1&page[size]=51

Result:
CloudCreativity\LaravelJsonApi\Exceptions\ValidationException: JSON API error in file /home/vagrant/code/example-api/vendor/cloudcreativity/laravel-json-api/src/Exceptions/ValidationException.php on line 49

Hi! Have you followed the installation instructions for what you need to add to your Exception handler?
https://laravel-json-api.readthedocs.io/en/latest/installation/

Hi @lindyhopchris , thanks for your response. Yes, I already have it however it is not handling the exception in this case. Aren't you managing to reproduce it?

No, if this wasn't working a lot of the tests would be failing and the production apps we've got this running in wouldn't be working.
Can you copy and paste your exception handler code?

Also can you copy and paste the full stack trace for the exception as the snippet you've provided above doesn't give me enough to go on. Thanks!

Hi @lindyhopchris ,
it must surely be my mistake but I was unable to find where I followed the instructions in the wrong way.
This is my app/Exceptions/Handler.php file content:
<?php

namespace App\Exceptions;

use CloudCreativity\LaravelJsonApi\Exceptions\HandlesErrors;
use Exception;
use Illuminate\Foundation\Exceptions\Handler as ExceptionHandler;
use Neomerx\JsonApi\Exceptions\JsonApiException;

class Handler extends ExceptionHandler
{

    use HandlesErrors;

    /**
     * A list of the exception types that are not reported.
     *
     * @var array
     */
    protected $dontReport = [
        JsonApiException::class,
    ];

    /**
     * A list of the inputs that are never flashed for validation exceptions.
     *
     * @var array
     */
    protected $dontFlash = [
        'password',
        'password_confirmation',
    ];

    /**
     * Report or log an exception.
     *
     * @param  \Exception  $exception
     * @return void
     */
    public function report(Exception $exception)
    {
        parent::report($exception);
    }

    /**
     * Render an exception into an HTTP response.
     *
     * @param  \Illuminate\Http\Request  $request
     * @param  \Exception  $exception
     * @return \Illuminate\Http\Response
     */
    public function render($request, Exception $exception)
    {
        if ($this->isJsonApi($request, $exception)) {
            return $this->renderJsonApi($request, $exception);
        }

        return parent::render($request, $exception);
    }
}

and the full stack trace of the exception is:
CloudCreativity\LaravelJsonApi\Exceptions\ValidationException: JSON API error in file /home/vagrant/code/example-api/vendor/cloudcreativity/laravel-json-api/src/Exceptions/ValidationException.php on line 49
Stack trace:
  1. CloudCreativity\LaravelJsonApi\Exceptions\ValidationException->() /home/vagrant/code/example-api/vendor/cloudcreativity/laravel-json-api/src/Exceptions/ValidationException.php:49
  2. CloudCreativity\LaravelJsonApi\Exceptions\ValidationException->create() /home/vagrant/code/example-api/vendor/cloudcreativity/laravel-json-api/src/Http/Requests/ValidatedRequest.php:308
  3. CloudCreativity\LaravelJsonApi\Http\Requests\ValidatedRequest->failedValidation() /home/vagrant/code/example-api/vendor/cloudcreativity/laravel-json-api/src/Http/Requests/ValidatedRequest.php:297
  4. CloudCreativity\LaravelJsonApi\Http\Requests\ValidatedRequest->passes() /home/vagrant/code/example-api/vendor/cloudcreativity/laravel-json-api/src/Http/Requests/FetchResources.php:59
  5. CloudCreativity\LaravelJsonApi\Http\Requests\FetchResources->validateQuery() /home/vagrant/code/example-api/vendor/cloudcreativity/laravel-json-api/src/Http/Requests/ValidatedRequest.php:265
  6. CloudCreativity\LaravelJsonApi\Http\Requests\ValidatedRequest->validateResolved() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Foundation/Providers/FormRequestServiceProvider.php:30
  7. Illuminate\Foundation\Providers\FormRequestServiceProvider->Illuminate\Foundation\Providers\{closure}() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Container/Container.php:1069
  8. Illuminate\Container\Container->fireCallbackArray() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Container/Container.php:1033
  9. Illuminate\Container\Container->fireAfterResolvingCallbacks() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Container/Container.php:1018
 10. Illuminate\Container\Container->fireResolvingCallbacks() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Container/Container.php:677
 11. Illuminate\Container\Container->resolve() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Container/Container.php:609
 12. Illuminate\Container\Container->make() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Foundation/Application.php:759
 13. Illuminate\Foundation\Application->make() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Routing/RouteDependencyResolverTrait.php:79
 14. Illuminate\Routing\ControllerDispatcher->transformDependency() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Routing/RouteDependencyResolverTrait.php:46
 15. Illuminate\Routing\ControllerDispatcher->resolveMethodDependencies() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Routing/RouteDependencyResolverTrait.php:27
 16. Illuminate\Routing\ControllerDispatcher->resolveClassMethodDependencies() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Routing/ControllerDispatcher.php:41
 17. Illuminate\Routing\ControllerDispatcher->dispatch() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Routing/Route.php:219
 18. Illuminate\Routing\Route->runController() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Routing/Route.php:176
 19. Illuminate\Routing\Route->run() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Routing/Router.php:682
 20. Illuminate\Routing\Router->Illuminate\Routing\{closure}() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php:30
 21. Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}() /home/vagrant/code/example-api/vendor/cloudcreativity/laravel-json-api/src/Http/Middleware/NegotiateContent.php:102
 22. CloudCreativity\LaravelJsonApi\Http\Middleware\NegotiateContent->handle() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:163
 23. Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php:53
 24. Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}() /home/vagrant/code/example-api/vendor/cloudcreativity/laravel-json-api/src/Http/Middleware/Authorize.php:87
 25. CloudCreativity\LaravelJsonApi\Http\Middleware\Authorize->handle() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:163
 26. Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php:53
 27. Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}() /home/vagrant/code/example-api/vendor/cloudcreativity/laravel-json-api/src/Http/Middleware/BootJsonApi.php:78
 28. CloudCreativity\LaravelJsonApi\Http\Middleware\BootJsonApi->handle() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:163
 29. Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php:53
 30. Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Routing/Middleware/SubstituteBindings.php:41
 31. Illuminate\Routing\Middleware\SubstituteBindings->handle() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:163
 32. Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php:53
 33. Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Auth/Middleware/Authenticate.php:43
 34. Illuminate\Auth\Middleware\Authenticate->handle() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:163
 35. Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php:53
 36. Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Routing/Middleware/ThrottleRequests.php:58
 37. Illuminate\Routing\Middleware\ThrottleRequests->handle() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:163
 38. Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php:53
 39. Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:104
 40. Illuminate\Pipeline\Pipeline->then() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Routing/Router.php:684
 41. Illuminate\Routing\Router->runRouteWithinStack() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Routing/Router.php:659
 42. Illuminate\Routing\Router->runRoute() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Routing/Router.php:625
 43. Illuminate\Routing\Router->dispatchToRoute() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Routing/Router.php:614
 44. Illuminate\Routing\Router->dispatch() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php:176
 45. Illuminate\Foundation\Http\Kernel->Illuminate\Foundation\Http\{closure}() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php:30
 46. Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}() /home/vagrant/code/example-api/vendor/barryvdh/laravel-debugbar/src/Middleware/InjectDebugbar.php:65
 47. Barryvdh\Debugbar\Middleware\InjectDebugbar->handle() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:163
 48. Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php:53
 49. Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}() /home/vagrant/code/example-api/vendor/fideloper/proxy/src/TrustProxies.php:57
 50. Fideloper\Proxy\TrustProxies->handle() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:163
 51. Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php:53
 52. Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TransformsRequest.php:31
 53. Illuminate\Foundation\Http\Middleware\TransformsRequest->handle() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:163
 54. Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php:53
 55. Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/ValidatePostSize.php:27
 56. Illuminate\Foundation\Http\Middleware\ValidatePostSize->handle() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:163
 57. Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php:53
 58. Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/CheckForMaintenanceMode.php:62
 59. Illuminate\Foundation\Http\Middleware\CheckForMaintenanceMode->handle() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:163
 60. Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php:53
 61. Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:104
 62. Illuminate\Pipeline\Pipeline->then() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php:151
 63. Illuminate\Foundation\Http\Kernel->sendRequestThroughRouter() /home/vagrant/code/example-api/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php:116
 64. Illuminate\Foundation\Http\Kernel->handle() /home/vagrant/code/example-api/public/index.php:55

When you send the GET request, are you sending an Accept: application/vnd.api+json header?

No, I wasn't :-(
Adding this header to the request (as per all the other requests, that instead contained it) solved my issue.
Thanks, @lindyhopchris !

Ah great. Yeah I think this shows up a different issue though... which is to do with JSON API Exceptions being thrown when the client has not requested a JSON API response. Which I think I've spotted before but never made a note of it. I'll create a separate issue for that so I don't forget.


Add API to pull value to top of stack

In JSAL I created a function, jsal_pull(), that does the following:
int
jsal_pull(int from_index)
{
	JsValueRef value;

	value = get_value(from_index);
	jsal_remove(from_index);
	return push_value(value);
}

It does the opposite of duk_insert(): Instead of popping a value off the top of value stack and inserting it elsewhere, it takes a value from elsewhere and moves it to the top.  For example, here's a use case:
jsal_push_function(constructor, name, 0);

jsal_push_new_object();
jsal_dup(-3);
jsal_set_named_property(-2, "value");
jsal_def_named_property(-2, "prototype");

jsal_push_global_object();
jsal_push_eval("({ writable: true, configurable: true })");
jsal_pull(-3);
jsal_set_named_property(-2, "value");
jsal_def_named_property(-2, name);
jsal_pop(1);

Which avoids an extra pop and IMO makes the stack balancing easier to understand.
I propose that Duktape implements a similar function in its C API.

In case it wasn't clear from the example, the use case is:

Push an object or function
Set properties on it
During setup for a call, pull it into position
No need to pop (or duk_remove(-2)) afterwards!

Sounds pretty useful to me, this pattern comes across in internals quite a bit.


Better exceptions from view files.

Currently the exception message is helpful, but the trace is very unhelpful.
Something custom to wrap around the standard exception, and give a more transparent stack trace would be great.
Exception messages to focus on, is exceptions from the render part, and exceptions from errors in components when loaded (syntax errors for example).

https://github.com/genius257/view/blob/358a1a3591fa6b27e0f17ebab59c2b586d3ced1a/src/View.php#L11


Applying KeyPair by subdividing #888

#888 적용 범위가 넓어 자원별로 세부화한 반영 필요
KeyPair 적용 필요

completed by https://github.com/cloud-barista/cb-spider/commit/32ca301986f3fa90329c00b0a3635df4206fd123


Cubic Line chart broken

Like the picture, broken sometimes, anyone can help?
set1 = [[LineChartDataSet alloc] initWithYVals:yVals label:@"DataSet 1"];
set1.drawCubicEnabled = YES;
set1.cubicIntensity = 0.5;
When I set drawCubicEnabled is NO, The chart seems ok.

have you set any customAxisMax/Min? It seems it is being clipped?

No set any max/min.
Test code:
    _lineChartView.delegate = self;
    //_lineChartView.backgroundColor = [UIColor yellowColor];

    _lineChartView.descriptionText = @"";
    _lineChartView.noDataTextDescription = @"You need to provide data for the chart.";

    _lineChartView.drawGridBackgroundEnabled = YES;
    _lineChartView.dragEnabled = NO;
    [_lineChartView setScaleEnabled:NO];
    _lineChartView.pinchZoomEnabled = NO;
    //[_lineChartView setViewPortOffsetsWithLeft:10.0 top:0.0 right:10.0 bottom:0.0];

    _lineChartView.legend.enabled = NO;

    _lineChartView.leftAxis.enabled = NO;
    _lineChartView.rightAxis.enabled = NO;
    _lineChartView.xAxis.enabled = NO;

    NSMutableArray *xVals = [[NSMutableArray alloc] init];

    [xVals addObject:@"1442246400000"];
    [xVals addObject:@"1442419200000"];
    [xVals addObject:@"1442505600000"];
    [xVals addObject:@"1442764800000"];
    [xVals addObject:@"1442851200000"];

    NSMutableArray *yVals = [[NSMutableArray alloc] init];

    [yVals addObject:[[ChartDataEntry alloc] initWithValue:0 xIndex:0]];
    [yVals addObject:[[ChartDataEntry alloc] initWithValue:-1 xIndex:1]];
    [yVals addObject:[[ChartDataEntry alloc] initWithValue:0.01170003414154053 xIndex:2]];
    [yVals addObject:[[ChartDataEntry alloc] initWithValue:0.04190003871917725 xIndex:3]];
    [yVals addObject:[[ChartDataEntry alloc] initWithValue:0.05540001392364502 xIndex:4]];

    LineChartDataSet *set1 = [[LineChartDataSet alloc] initWithYVals:yVals label:@"DataSet 1"];

    set1.lineWidth = 1.75;
    set1.circleRadius = 3.0;
    [set1 setColor:[UIColor orangeColor]];
    [set1 setCircleColor:UIColor.whiteColor];
    set1.highlightColor = UIColor.whiteColor;
    set1.drawValuesEnabled = NO;
    set1.drawCubicEnabled = YES;
    set1.cubicIntensity = 0.5;

    _lineChartView.data = [[LineChartData alloc] initWithXVals:xVals dataSet:set1];

Result:

I just saw a very flat line with your data, what did I miss

It looks like a dashed line...

BTW, #330 is also talking about missing data points, though it is for drawLinear. Will it be same issue?

@zxy198717 any new info?

@danielgindi @liuxuan30 I created one test project(https://github.com/zxy198717/iOS-Chart-Test), maybe it can help you find the root cause.

OK But I guess no one is spare to look into it right now.. Mark as bug

I have the same problem here.
Here's the same graph with cubic lines disabled and enabled:

At first I thought this was just a matter of changing the padding of the chart or something like that, it's like the cubic rendering makes some bits of the line dip below the visible part of the graph, but I couldn't find anything that helped me solve this, and then I ran into this post.

Why not set a custom y minimum for the chart, to avoid the clipping?

That was fast, thanks. I'm new at this, I'll try to figure out how to do that then… but to avoid a lot of white space below the graph depending on the users' data I'll have to find the minimum value in their data set and always set that custom Y minimum a little bellow that, right? It'll do for now if I can get it to work, but it's not very elegant.

Argh, I can't find out how to do it. I tried changing chartView.leftAxis.customAxisMin and chartView.leftAxis.axisMinimum to no effect, for the left axis, the right axis and both. Isn't this how it's done? I can't find anything else at the documentation.

Ok, that solved the first problem, but now I have another:

It looks like the data dips below zero sometimes, which doesn't make sense for my app… or maybe it seems like the data is more than zero with those bumps down there when they should actually be straight lines.

Well that's because it's a Cubic Bezier line, not a straight line. That's
how Beziers works...
Maybe someone with more expertise in charts with bezier lines could offer
some insight here.
On Wed, Nov 18, 2015 at 8:24 AM, danielbmarques<EMAIL_ADDRESS>wrote:

Ok, that solved the first problem, but now I have another:
[image: captura de tela 2015-11-18 as 04 20 02]
https://cloud.githubusercontent.com/assets/15813674/11234080/b4dba5b8-8dab-11e5-9619-6b5a12b68bc8.png
It looks like the data dips below zero sometimes, which doesn't make sense
for my app… or maybe it seems like the data is more than zero with those
bumps down there when they should actually be straight lines.
—
Reply to this email directly or view it on GitHub
https://github.com/danielgindi/ios-charts/issues/407#issuecomment-157616020
.

I also tried this library and the bezier lines look great, so it's certainly possible:

I'd rather use your library for the features, though. :(

We'll look into it
@PhilJay ?

Thanks a lot!
Great work, by the way. :)

Well this looks like zero values are simply rendered as normal lines?

Yes, like when the values reach the real minimum value (not custom min value) - we need to trim them to straight lines.
But then we have a problem with the line being part bezier part straight...
I'm assuming there's some kind of trick, maybe duplicating points to force the bezier to draw straight?

I think that's probably the case, duplicating points.
If you compare the two examples I posted you can see that in the last one the line is more curved at its extremes… like if it were coming from a straight line and going to a straight line, and we can see the curves in the chart prepare to do that. So it's not just that zero values are normal lines, the rest of the graph also adjusts to make up for that.
And that shouldn't happen just when points are close to the minimum… if you have a curved line between two points, the curve should never go above or below either of those two points, it doesn't matter what their values are.

Look at this example from that other library:

The line between "sab" and "dom" doesn't go above nor below the values for "sab" and "dom", even though the huge bump at "sex" should make it do that. So some points must be duplicated to account for this, regardless of whether it's at the minimum or maximum value or neither.

Anyone solve this issue? My chart is dipping below zero too, and it's so ugly. @danielbmarques did you end up using a better library?

We will solve it soon. We are working hard on other things.
You are most welcome to try to solve it and create a PR too!
On Tue, Nov 24, 2015 at 1:34 PM, Hannah Carney<EMAIL_ADDRESS>wrote:

Anyone solve this issue? My chart is dipping below zero too, and it's so
ugly. @danielbmarques https://github.com/danielbmarques did you end up
using a better library?
—
Reply to this email directly or view it on GitHub
https://github.com/danielgindi/ios-charts/issues/407#issuecomment-159237756
.

@HannahCarney If all you're interested in is the line itself, I think the best option is this, but you won't even get labels for the axes, you have to set them up yourself. For now I just resorted to doing this:

@danielgindi Apparently duplicating points isn't the best way to do this after all. I think the way to go is to use UIBezierPath and control points instead of CGPathCreateMutable. It seems pretty straightforward, but I won't have the time to figure out how to add it to the rest of the code for now.

@danielbmarques IMHO UIBezierPath is not relevant, it works almost exactly like the CGPathCreateMutable. The problem is that there is no (at least i don't know any) spline interpolation method which takes into consideration the relevant constraints. I haven't studied the JBChartView approach, but the BEMSimpleLineGraph library mitigates the error by not using any interpolation, it simply draws bezier curves between points. It works for very simple data, but in most cases it creates ugly "bumpy" plots.
Can anyone confirm that JBChartView doesn't have the same problem? I will test in my free time, but AFAIK it should have exactly the same issues.

@mslazynski Whether it's using CGPathCreateMutable or UIBezierPath, I think the main point is to use control points. I don't really know much about anything like this, though, so I may be completely off the mark. I barely know what interpolation is for instance, haha… but from what I gathered I don't think JBChartView uses independent discrete segments, if that's what you mean. The link I posted before was broken, I think the relevant part is this.
Apple's iTunes Connect app has charts that don't have this problem, I wonder how they do it:

@danielbmarques BEMSimpleLineGraph uses separate segments. JBChartView use some kind of interpolation for sure (it's enough to look at the code you've linked to), however I didn't have time to test whether their interpolation method mitigates the problem. If it is confirmed that JBCharView solved the problem, porting their code should be a 1h piece of work :) I'm sure that there exists the proper way of choosing control points -> I've tried some naive methods, however the resulting plot was always ugly :(

@mslazynski A while ago, when I first mentioned JBChartView, I tried it with my code and it did fix the problem. I didn't test it really extensively, though; my charts are relatively simple.

Okay so I went through the code of the other libaries - and it seems like they do a lot of weird and unnecessary calculations. I've managed to deduce the core algorithm for control points, and create a CodePen:
http://codepen.io/danielgindi/pen/eZGxzr
The code contains both quad and cubic bezier methods, as I had to simplify and then build to cubic control points.
This seems sufficient, though this removes the option to control the intensity of the bezier.
So I guess what I'll do is introduce an enum for the way that the line chart will draw it's line (linear, stepped, bezier, trimmed bezier).
@PhilJay what do you think?

Looks good. How about performance? Does this new way of drawing e.g. cubic improve performance as well? (it kind of looks like it does)
I don't think its too bad if you cannot control intensity anymore, but if we still want that feature, an enum or flag could be sufficient.

From my tests- it does. If I use the final cubic method- then I'm making the same amount of AddCurveTo calls but with less mathmatics.
I think that the cubicIntensity is a nice property to have, and some people might actually want to draw a real cubic, not a trimmed one :)

@danielgindi Awesome, thank you!

Awesome, thanks a lot!


Update needed to button documentation

Bug, feature request, or proposal:
Bug in the docs perhaps
What is the expected behavior?
https://material.angular.io/components/component/button is showing an example of a button where the text is transformed to uppercase however if you click on "Edit in Plunker" the text is not transformed. Assuming the behavior in plunker is correct then it would be helpful to indicate in the CSS tab that you are styling it.
What is the current behavior?
Currently in the docs it says..
/** No CSS for this example */

Will be fixed in https://github.com/angular/material.angular.io/pull/132

Closing issue as fix is merged


Next Release / 3.1 Support

I was looking forward to a new release since the 3.1 support for JSONField was added in.
When can we expect a new version to be cut? Does anything else need to be done before that can happen?

just changelog and release. allow me till tomorrow or ping me if I forget

just changelog and release. allow me till tomorrow or ping me if I forget

Awesome, thank you!

Awesome, thank you!

@auvipy ping 😄

@auvipy ping 😄

releaseing in an hour :D

releaseing in an hour :D

https://pypi.org/project/django-activity-stream/0.10.0/

https://pypi.org/project/django-activity-stream/0.10.0/


parser error in MESSAGE RAISING statement (dash in exception name)

MESSAGE e019 RAISING tree_not-allowed.

@FreHu try again, 2.48.1 published


updated querious (2.0)

Why the close?

I did not set up my forked branch to use my correct github account.  I am
redoing the repair, and will be resubmitting the pull request from the
proper account.  Sorry for the confusion.
On Fri, Feb 12, 2016 at 12:40 PM Vítor Galvão<EMAIL_ADDRESS>wrote:

Why the close?
—
Reply to this email directly or view it on GitHub
https://github.com/caskroom/homebrew-cask/pull/18792#issuecomment-183425262
.

I did not set up my forked branch to use my correct github account.  I am redoing the repair, and will be resubmitting the pull request from the proper account.  Sorry for the confusion.


Add --no-color option

I'd like to save the contents of a solidarity report to a log file but it's saving the ansi color codes too. I've worked around the problem by piping it through strip-ansi-cli but adding a --no-color option to solidarity would be perfect.

Awesome, would this be something you're willing to PR?

Following the this down the rabbit hole it turns out to be already supported!
solidarity uses GlueGunPrint which uses colors which supports passing --no-color as a command line parameter.
It's great that this already works but it does feel fragile that a library a couple layers deep is parsing command line parameters. But, hey, the feature is there so thanks!


Installing brew changed my XCode path

brew doctor output
Your system is ready to brew.

Verification

[X] My "brew doctor output" above says Your system is ready to brew. and am still able to reproduce my issue.
[X] I ran brew update twice and am still able to reproduce my issue.
[X] This issue's title and/or description do not reference a single formula e.g. brew install wget. If they do, open an issue at https://github.com/Homebrew/homebrew-core/issues/new/choose instead.

brew config output
HOMEBREW_VERSION: 4.0.14
ORIGIN: https://github.com/Homebrew/brew
HEAD: ac0663ae5d2d4c76bb62363592d77dbad49ac30c
Last commit: 32 hours ago
Core tap JSON: 17 Apr 17:43 UTC
HOMEBREW_PREFIX: /opt/homebrew
HOMEBREW_CASK_OPTS: []
HOMEBREW_MAKE_JOBS: 12
Homebrew Ruby: 2.6.10 => /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby
CPU: dodeca-core 64-bit arm_blizzard_avalanche
Clang: 14.0.3 build 1403
Git: 2.39.2 => /Library/Developer/CommandLineTools/usr/bin/git
Curl: 7.86.0 => /usr/bin/curl
macOS: 13.2.1-arm64
CLT: <IP_ADDRESS>.1.1679647830
Xcode: 14.3
Rosetta 2: false

What were you trying to do (and why)?
I installed brew this morning and installed one package bundletool.  Before that, xcodebuild worked.  After it doesn't.  I read through the bundletool.rb code and it doesn't look like it does anything with xcode-select, but brew does. :)
Now xcodebuild says:
xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance
What happened (include all command output)?
See above.
What did you expect to happen?
I expected xcodebuild to still work after installing brew.
Step-by-step reproduction instructions (by running brew commands)
Would require installing on a fresh machine, I suspect.

I fixed my install with sudo xcode-select -s /Applications/Xcode.app/Contents/Developer, but if this was really brew's fault (which I don't see how anything else could have caused this?) then filing this since many other developers may not be so familiar with xcode-select.

Actually sudo xcode-select -r would have been better for me to have used.


Test adding new file to new branch.

Merged from a new branch that I created. This demonstrates making a new branch, checking out a branch, and merging new files / changes to the remote.
erikamaker@erikas-computer:~/war-paint$ git status
On branch test
nothing to commit, working tree clean
erikamaker@erikas-computer:~/war-paint$ git checkout -b erikas_test_branch
Switched to a new branch 'erikas_test_branch'
erikamaker@erikas-computer:~/war-paint$ git remote add upstream git@github.com:erikamaker/war-paint.git
erikamaker@erikas-computer:~/war-paint$ git branch
  chore/gitignore
  chore/ruby-version
* erikas_test_branch
  main
  play/board
  test
erikamaker@erikas-computer:~/war-paint$ echo "some test file" > ex1
erikamaker@erikas-computer:~/war-paint$ cat ex1
some test file
erikamaker@erikas-computer:~/war-paint$ git status
On branch erikas_test_branch
Untracked files:
  (use "git add <file>..." to include in what will be committed)
	ex1

nothing added to commit but untracked files present (use "git add" to track)
erikamaker@erikas-computer:~/war-paint$ git add ex1
erikamaker@erikas-computer:~/war-paint$ git commit -m "Test adding new file to new branch."
[erikas_test_branch cef778f] Test adding new file to new branch.
 1 file changed, 1 insertion(+)
 create mode 100644 ex1
erikamaker@erikas-computer:~/war-paint$ git push -u origin erikas_test_branch
Enumerating objects: 4, done.
Counting objects: 100% (4/4), done.
Delta compression using up to 8 threads
Compressing objects: 100% (2/2), done.
Writing objects: 100% (3/3), 305 bytes | 305.00 KiB/s, done.
Total 3 (delta 1), reused 0 (delta 0), pack-reused 0
remote: Resolving deltas: 100% (1/1), completed with 1 local object.
remote:
remote: Create a pull request for 'erikas_test_branch' on GitHub by visiting:
remote:      https://github.com/erikamaker/war-paint/pull/new/erikas_test_branch
remote:
To github.com:erikamaker/war-paint.git
 * [new branch]      erikas_test_branch -> erikas_test_branch
branch 'erikas_test_branch' set up to track 'origin/erikas_test_branch'.

Onto creating the pull request by clicking the "create pull request" button below.

Received pull request test. Merged and closed.


Filters are now optional.

Codecov Report

Merging #302 into develop will decrease coverage by 0.02%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop     #302      +/-   ##
===========================================
- Coverage    92.94%   92.92%   -0.03%
===========================================
  Files           63       63
  Lines         2466     2459       -7
  Branches       218      215       -3
===========================================
- Hits          2292     2285       -7
  Misses         146      146
  Partials        28       28

Impacted Files
Coverage Δ

datahub/search/views.py
98.41% <ø> (-0.16%)
:arrow_down:

Continue to review full report at Codecov.

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


allow fast forward pushes

:hammer: early returns to allow for more checks
allow fast forward merges for restrict-master-to-gui-merges in the event that there are more than one core branches (e.g. master, develop, release)

@chernjie: the hook script is currently called "restrict-master-to-gui-merges", can the GUI be used to perform fast forward merges?

@jonico Good question, I have not attempted it. https://help.github.com/en/articles/about-merge-methods-on-github#squashing-your-merge-commits shows that there are some potential fast-forward scenarios with pull requests.
One more thing, this hook name may mention GUI, but it also restricts regular branch pushes.
e.g.
git push origin master:develop

One more thing, this hook name may mention GUI, but it also restricts regular branch pushes.

@chernjie: I believe the intention of this sample was to only allow merges over the Web UI and the merge API, wasn't it?

@jonico ideally this tool should not block fast-forward merges when the two heads are the same.