Support for cpu-quota option

Actually docker-client doesn't support cpu-quota option for container creation

We are open to PRs :)

Ok :-)

Hi bit of a noob willing to look into this as I need support for cpuset and memory. Am I correct in thinking that these are not implemented yet either? After glancing through the code and playing with the api, I could not get it to work.
I was creating ContainerConfig like so:
final ContainerConfig containerConfig = ContainerConfig.builder()             .image(imageName)             .hostConfig(hostConfig)             .exposedPorts(ports)             .cmd(cmd)             .cpuset("0")             .memory((long)512)             .build();
Anyway. I believe @JsonProperty needs to be added for each of these options we want to implement. Can anyone tell me if I'm looking in the right direction.
Thank you.

@lemz90 I believe it's been done here https://github.com/spotify/docker-client/pull/286

Because of a Docker Remote API change, issue #286 moved some of these to the HostConfig. It looks like they're still in the ContainerConfig Builder, but -- as @lemz90 noted -- they're no longer @JsonPropertys. Seems like they should be completely removed from the ContainerConfig.Builder inner class so as not to mislead folks.

@tedyoung @davidxia Wow thanks for pointing that out! I might work on a pull request to remove these options from ContainerConfig >:)
Otherwise it seems like this issue could be closed.


Tweak migration

Made a tweak and did a PR this time so we could discuss / tweak further. Here's the output at present:
scramble:credstash dom-at-luminal$ ./credstash put foo bar
foo has been stored
scramble:credstash dom-at-luminal$ ./credstash put foo baz
foo version 1 is already in the credential store. Use the -v flag to specify a new version
scramble:credstash dom-at-luminal$ ./credstash put foo baz -a
foo has been stored
scramble:credstash dom-at-luminal$ ./credstash put vers bar -v 1.1.9
vers has been stored
scramble:credstash dom-at-luminal$ ./credstash put vers baz -v 1.2.0
vers has been stored
scramble:credstash dom-at-luminal$ ./credstash put dttm bar -v 20151105
dttm has been stored
scramble:credstash dom-at-luminal$ ./credstash put dttm baz -v 20151106
dttm has been stored
scramble:credstash dom-at-luminal$ ./credstash put dttmb bar -v 2015-11-06
dttmb has been stored
scramble:credstash dom-at-luminal$ git checkout tweak-migration
Switched to branch 'tweak-migration'
Your branch is up-to-date with 'origin/tweak-migration'.
scramble:credstash dom-at-luminal$ ./credstash list
dttm  -- version 20151105
dttm  -- version 20151106
dttmb -- version 2015-11-06
foo   -- version 1
foo   -- version 2
vers  -- version 1.1.9
vers  -- version 1.2.0
scramble:credstash dom-at-luminal$ python ./credstash-migrate-autoversion.py
Skipping item: dttmb, 2015-11-06
Skipping item: vers, 1.1.9
Skipping item: vers, 1.2.0
scramble:credstash dom-at-luminal$ ./credstash list
dttm  -- version<PHONE_NUMBER>020151105
dttm  -- version<PHONE_NUMBER>020151106
dttmb -- version 2015-11-06
foo   -- version<PHONE_NUMBER>000000001
foo   -- version<PHONE_NUMBER>000000002
vers  -- version 1.1.9
vers  -- version 1.2.0

I think we have to advise people not to use if they used the -v flag for custom versioning.

Wrong target branch.


Optimize has()

O(n) -> O(1) for route checks.
In our application, the has method came out on the top in our profiling. It may be that we are calling it too often for some reason, but it prompted this PR to optimize the method.
Note - got the tests running after patching one FolioTest to ignore ordering of the routes array. Don't know if this is ok or not.

Thanks! Just for reference (I had to look it up), O(n)→O(1) means that currently this operation's performance depends on the size of the routes object, so with thousands of routes it would take longer to make a has() check, whereas after this PR that won't matter, checking for a route will take the same amount of time no matter how many routes there are—right?

Thanks! Just for reference (I had to look it up), O(n)→O(1) means that currently this operation's performance depends on the size of the routes object, so with thousands of routes it would take longer to make a has() check, whereas after this PR that won't matter, checking for a route will take the same amount of time no matter how many routes there are—right?

Thanks @bakerkretzmar, that is a perfect explanation :) Sorry for being so cryptic in my description.
Your work with ziggy is much appreciated 🏅


Simplified Package Loading API

This is a re‐working of #2166, but branched from the tip of master.

One static function each has been added to Manifest, Package and PackageGraph that allows them to be loaded by supplying only the location of swift and the location of the package to load.

This necessitated some minor refactoring of Workspace internals, so that code could be shared instead of duplicated.

The package-info example has been updated to use the simpler APIs.

For package clients, this amounts to an ergonomic reduction of about 45 lines down to 1, whenever no customization is needed.
@aciidb0mb3r

Made all the changes you requested, pushed them and went over the difference again.
It think it’s ready for another look, @aciidb0mb3r.

@swift-ci smoke test

Thanks a lot for your work on this!

Lovely... the test failed. Whatever it is it doesn’t happen locally.
My only guess is that this line in the test set‐up isn’t reliable. I don’t know what to do instead. 🙁

Ironically, I have been working from macOS not Linux, so would have expected the reverse test results.

...I cannot find any of the tests from WorkspaceTests/XCTestManifests.swift in the Linux log. Is anything actually being tested?

For reference, this is what I see locally:
$ swift test --filter ./testSimpleAPI
[36/36] Linking ./.build/x86_64-apple-macosx/debug/SwiftPMPackageTests.xctest…
Test Suite 'Selected tests' started at 2019-06-27 15:23:12.153
Test Suite 'SwiftPMPackageTests.xctest' started at 2019-06-27 15:23:12.154
Test Suite 'WorkspaceTests' started at 2019-06-27 15:23:12.154
Test Case '-[WorkspaceTests.WorkspaceTests testSimpleAPI]' started.
Test Case '-[WorkspaceTests.WorkspaceTests testSimpleAPI]' passed (2.414 seconds).
Test Suite 'WorkspaceTests' passed at 2019-06-27 15:23:14.568.
	 Executed 1 test, with 0 failures (0 unexpected) in 2.414 (2.414) seconds
Test Suite 'SwiftPMPackageTests.xctest' passed at 2019-06-27 15:23:14.568.
	 Executed 1 test, with 0 failures (0 unexpected) in 2.414 (2.414) seconds
Test Suite 'Selected tests' passed at 2019-06-27 15:23:14.568.
	 Executed 1 test, with 0 failures (0 unexpected) in 2.414 (2.414) seconds

I spent the last 7 hours trying to make my set‐up more like CI to reproduce the problem. I managed to finally get the latest trunk snapshot (June 23) onto my Linux machine and SwiftPM Utilities/bootstraped with it (which required jumping through a lot of hoops like building cmake from source). Unfortunately, .build/x86_64-unknown-linux/debug/spm test --filter ./testSimpleAPI still succeeded. 😓
I just told it to Utilities/bootstrap test --test-parallel, so we’ll see if it does anything different.
I’ve been trying to do the same on my Mac, but so far I haven’t managed to get Xcode 11 beta 2 to download successfully; it keeps failing several hours in.

@SDGGiesbrecht Thanks for all of your work. I can take over and figure out this CI failure. It is night time here so I'll probably take a look tomorrow.

Getting to be night time here too. Final thing to report for now is that Utilities/bootstrap test --test-parallel seemed to succeed. (Technically there were 5 seemingly unrelated failures: 4 in testPassExactDependenciesToBuildCommand and 1 in testFileDeprecation. But since it also says “[576/576]”, I assume it didn’t abort the entire suite when those failed, so it must have run and passed testSimpleAPI somewhere in there?)

I was out sick for a couple of days. I fixed the CI issue and made some minor changes here: https://github.com/apple/swift-package-manager/pull/2201

I hope you are feeling better. (I hadn’t even noticed the delay. It was Canada Day weekend here, so everything was shut down anyway.)

Closing. Superseded by #2201.


Feature/jenkinsfile standardization

Adding Makefile and Jenkinsfile

@n0mn0m I added a VERSION file in the top-level directory. I'm not sure if there's a better location where that info should be tracked within the repo?

What are your thoughts on https://github.com/helxplatform/appstore/pull/101

I think that's great, I can rebase this branch off of that one to add the Jenkinsfile using the existing Makefile in there

@cschreep this won't work without the -e due to how Django introspects INSTALLED_APPS and expects them to be available. Happy to walkthrough that further, but it was a pain point when working on this and something I would want to work on over time, or look at better ways to handle this.

@cschreep you may want to rebase one more time, but this should be good to go now.


Cannot read property 'lat' of null on leaflet polyline drag

Hi,
I am trying to implement draggable polyline using react leaflet. Added draggable: true while creating a polyline. Added that polyline to the featuregroup. And the feature group is added to the map. So while dragging the polyline I'm getting the below error.
Projection.SphericalMercator.js:22 Uncaught TypeError: Cannot read property 'lat' of null
at Object.project (Projection.SphericalMercator.js:22)
at Object.latLngToPoint (CRS.js:28)
at NewClass.project (Map.js:992)
at NewClass.latLngToLayerPoint (Map.js:1014)
at NewClass.latLngToContainerPoint (Map.js:1071)
at NewClass._fireDOMEvent (Map.js:1432)
at NewClass._handleDOMEvent (Map.js:1396)
at HTMLDivElement.handler (DomEvent.js:79)

You should not dismiss bugreport template. Pay attention, that this bugtracker is not for general support, and you should be sure that you are reporting leaflet bug.


add LSP Linux Web Shell to nix container

[ ] can access nix container

https://makoserver.net/articles/Linux-Web-Shell
https://github.com/RealTimeLogic/LSP-Examples/tree/master/Web-Shell

In order to work the UI provider needs to be run as a service.
What is the link between LSP, Mako Server and BAS?
nix means I need to build everything from the sources.
It looks like the simplest to test is actually BAS: Barracuda App Server
but there is a manual on building Mako Server with Make, so maybe I can replicate the process in nix and not test BAS?

I can build a package from an open source repo, right?

alright what I need to do is to build Mako and run a shell script that will call this command from the directory that I need.
a shell script can be nix run.

Yeah, this is better asked live in a meeting...

https://github.com/GoogleChromeLabs/wasi-fs-access

https://en.wikipedia.org/wiki/Text-based_user_interface
https://github.com/ratatui-org/templates


minimum viable product

It does:

create schema (static)
insert random values with incremented pk's into test cluster and oracle
(10000 values hardcoded)
read values and validate it with oracle (prints errors)
(hardcoded test cluster / oracle)

@soyacz , start looking on it


RFC (Vue): Support usage in vue based web components with defineCustomElement

Summary
We have a micro app architecture relying on web components build with Vue's defineCustomElements function.
Therefor we have no app instance an no way to add urql as a plugin or use provide/inject.
A workaround would be of course not to use defineCustomelement and create the web components manually with an app instance, but we want to use defineCustomElement and reduce the manual work per web component (we will have probably 100+ web components in our mono repo).
Proposed Solution
To enable this use case there are 2 possible changes that can achieve this:
1. Add an optional client parameter to useClientHandle
We could then use this parameter instead of useClient to get the client:
export function useClientHandle(clientArg?: Client): ClientHandle {
  const client = clientArg ?? useClient();
  //[...]
}

2. Export all callUse* functions
If callUseQuery, callUseMutation, etc. functions are exported, we could build our own useClientHandle function based on those functions.
Solution 1 is the best solution if this should be an officially supported use case by @urql/vue. If not then solution 2 would allow a manual reuse of the vue functions for building a custom workaround. Both changes can also be implemented together of course.
If one (or both) of the proposed changes are welcome, I can provide a PR.

So, if I'm reading this correctly it does say,

The Provide / Inject API and its Composition API equivalent also work between Vue-defined custom elements.

This is basically our mechanism to enforce that the Provide API is used to deliver a client to these APIs in a targeted manner. Bypassing this is of course possible — although, I will rule out option two here for you, sorry, it's simply not something we're keen on doing (a library, in our view, is not a set of tools to recompose said library, to us; this would diverge different usecases and happy paths too far between users)
Option 1 — providing a client ref or a client directly is of course possible. But, I want to make sure that this is necessary.
I haven't tested this myself yet, but could you validate for me please whether using provideClient in the same or a wrapping custom element that uses the query APIs really doesn't work? I think the docs imply it should 🤔 https://github.com/urql-graphql/urql/blob/9abce5d7b1f125d9edd666994e15ca8ae0dec7a6/packages/vue-urql/src/useClient.ts#L4

Thanks for your reply :-)
The problem with web components in vue is, that we don't have a parent/child component. We cannot provide and inject the same variable in the same component.

I haven't tested this myself yet, but could you validate for me please whether using provideClient in the same or a wrapping custom element that uses the query APIs really doesn't work? I think the docs imply it should 🤔

I tested it. It works if I have a parent and a child component. But it doesn't work if I use provideClient in the same component. The behaviour is the same wether I use plain vue or web components with defineCustomElements.
For our use case I need something like this to work in a single component:
<script setup lang="ts">
import { useQuery, provideClient, createClient } from '@urql/vue';
import gql from 'graphql-tag';

const client = createClient({  url: `path/to/graphql` });
provideClient(client);

const { data } = useQuery({
  query: gql`
    query Customers {
      customers {
        id
        name
      }
    }
  `,
});
</script>

<template>
    <div>{{ data }}</div>
</template>

Currently we use vue-apollo in our architecture and it works. But we want to switch to urql. The provideApolloClient method from vue-apollo solved this issue by using a cache object instead of provide/inject: https://github.com/vuejs/apollo/blob/372892855d76622128ac560e8fadc689c50675bc/packages/vue-apollo-composable/src/useApolloClient.ts#L85
If provideClient stays the way it is, an extra client parameter to useClientHandle would allow us to build something like this for our project:
const { useQuery, useMutation, useSubscription, client } = createUrqlClient(`path/to/graphql` )

Where createUrqlClient is a wrapper for creating the client and returns the result of useClientHandle.

Sorry for forgetting about this!
I pushed a fix for this here: #3018. Very simple solution, but it'll allow for what you posted above.


Style stderr and stdout logs differently

Don't do this if causes too much flickering

Closed by 379b046d8f481ffa6fe4c624919e54d52e59fb2e


Making installation script more robust:

Updated script SHEBANG to point to env instead of directly to bash. This allows end systems to start with the appropriate bash installation (in case a different version is installed to a different location)
Script creates virtual environment for python3, this mitigates the need to manually check for python3 and safely isolates the installation of packages from the system's packages
Changed the way the installer detects package managers. Prior way checked for a the presence of a folder and assumed the os, which then assumed the installation command. If we check for the installation command directly, we make fewer asumptions and have the flexibility to check for different package managers in a miriade of ways (some OSes can have different package managers. EG: osx can have homebrew or macports.)
Added shebangs to python scripts, they can utilize the appropriate python. When the venv python is activate, env will use it.

This looks really good. The one problem is that I think tensorflow v1.15 can only run up to python 3.6 (isn't that true?). If so, can you somehow preserve the message that checks for that and explains what to do if the version is incompatible?

It works for me using python 3.7.5 with tensorflow 1.15 on Linux.

@paul-nelson-baker hey I may have merged this prematurely, because at https://colab.research.google.com/github/AIDungeon/AIDungeon/blob/develop/AIDungeon_2.ipynb when I replace --branch master with --branch develop, I get this:
Cloning into 'AIDungeon'...
remote: Enumerating objects: 54, done.
remote: Counting objects: 100% (54/54), done.
remote: Compressing objects: 100% (48/48), done.
remote: Total 54 (delta 2), reused 18 (delta 0), pack-reused 0
Unpacking objects: 100% (54/54), done.
/content/AIDungeon
The virtual environment was not created successfully because ensurepip is not
available.  On Debian/Ubuntu systems, you need to install the python3-venv
package using the following command.

    apt-get install python3-venv

You may need to use sudo with that command.  After installing the python3-venv
package, recreate your virtual environment.

Failing command: ['/content/AIDungeon/venv/bin/python3', '-Im', 'ensurepip', '--upgrade', '--default-pip']

Installation Complete!

Any idea why?

@ben-bay Apologies, after your first comment I set out to see if I could do what you asked me before the merge. Lemme try and see what happened, because that's a strange error

@ben-bay Can you try again? I'm succeeding under those conditions. Has this been un-merged?

@paul-nelson-baker I think that was a mistake. Working on getting this back up, sorry

@paul-nelson-baker Can you remove the clear_output() and try again? Your colab notebook is not the latest so it clear all of the error :p


Review and refactor function StructsFromRows()...

...
for better readability/maintainability and to confirm to gocyclo complexity

In most cases, callers should call db.QueryStructs instead of calling StructsFromRows directly.  However, it's useful in the cases that the caller is not using apid.Db.
I can provide examples on the usage of that function. Do you have specific improvements in mind?


change so editor can have options (eg subl -nw)

with quotes, bash will assume the string is one command, where one might want more than that
eg EDITOR=subl -nw
Without it should work.

Gnouc: I apologize but I do not understand the code in this PR.  I am uncomfortable accepting code that I do not understand how it works.  Could you add comments?
How is this better than simply removing the quotes from $EDITOR in blackbox_edit?  What is an example of an attack that is defeated in this code that isn't avoided simply unquoting $EDITOR?

@tlimoncelli Like the issue I raised before, if EDITOR was set to somethinglike '/*/*/*/*../../../../*/*/*/*../../../../*/*/*/*' can push machine to heavy load.
The approach of this PR is push all options in an array EDITOR_OPTS, then using it safe way "${EDITOR[@]". I will go line by line:
: "Empty array to hold editor options"
EDITOR_OPTS=()
: " ${EDITOR#* } remove everything before the first whitspace in EDITOR"
: "Meaning extract options part if EDITOR was set with options, eg: EDITOR='vim -R -g', we got '-R -g'"
: "If no options were set, ${EDITOR#* } expanded to $EDITOR itself"
: "Purpose of if condition: If EDITOR was set with options"
if [ "$EDITOR" != "${EDITOR#* }" ]; then
  : "We got the options part, save to EDITOR_OPT"
  EDITOR_OPT=${EDITOR#* }
  : "Infinitive loop for processing options"
  while true; do
   : "${EDITOR_OPT%% *} remove all thing after the first white space"
   : "eg: in '-R -g', we got 'R'"
    opt=${EDITOR_OPT%% *}
   : "We push option to array"
    EDITOR_OPTS+=("$opt")
   : "We check  if current opt is the last option, quit the loop"
    if [ "$opt" = "$EDITOR_OPT" ]; then
      break
    fi
    : "We remove the option after pushing it to array"
    : "eg: Before, options was '-R -g', after pushing '-R', we set $EDITOR_OPT to 'g'"
    EDITOR_OPT=${EDITOR_OPT#* }
  done
fi

I think this is not the best solution so far, but leaving variable unquote is completely bad practice, especially that's variable came from environment.
If you think it' too complicated, we can make it easier by disable the globbing with set -f.

@tlimoncelli Did you take a look at this issue?

Gnouc, thank you for the explanation.
I have written up my thoughts here: https://github.com/StackExchange/blackbox/issues/72


Deploy fails: ValueError: embedded null byte

When I try to deploy I get an "embedded null byte" error. It appears null bytes are inserted when the serverless-python-requirements plugin copies the requirements.txt file to the .serverless directory.

Serverless: Docker Image: lambci/lambda:build-python3.6
Serverless: Trying bindPath C:/Users/me/projects/playground/sls/with_rds (run,--rm,-v,C:/Users/me/Dropbox/projects/playground/sls/with_rds:/test,alpine,ls,/test/serverless.yml)
Serverless: /test/serverless.yml

  Error --------------------------------------------------

  Exception:
Traceback (most recent call last):
  File "/var/lang/lib/python3.6/site-packages/pip/_internal/basecommand.py", line 228, in main
    status = self.run(options, args)
  File "/var/lang/lib/python3.6/site-packages/pip/_internal/commands/install.py", line 267, in run
    self.name, wheel_cache
  File "/var/lang/lib/python3.6/site-packages/pip/_internal/basecommand.py", line 314, in populate_requirement_set
    wheel_cache=wheel_cache):
  File "/var/lang/lib/python3.6/site-packages/pip/_internal/req/req_file.py", line 89, in parse_requirements
    for req in req_iter:
  File "/var/lang/lib/python3.6/site-packages/pip/_internal/req/req_file.py", line 156, in process_line
    isolated=isolated, options=req_options, wheel_cache=wheel_cache
  File "/var/lang/lib/python3.6/site-packages/pip/_internal/req/req_install.py", line 206, in from_line
    looks_like_dir = os.path.isdir(p) and (
  File "/var/lang/lib/python3.6/genericpath.py", line 42, in isdir
    st = os.stat(s)
ValueError: embedded null byte
You are using pip version 10.0.1, however version 18.0 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.

     For debugging logs, run again after setting the "SLS_DEBUG=*" environment variable.

  Stack Trace --------------------------------------------

Error: Exception:
Traceback (most recent call last):
  File "/var/lang/lib/python3.6/site-packages/pip/_internal/basecommand.py", line 228, in main
    status = self.run(options, args)
  File "/var/lang/lib/python3.6/site-packages/pip/_internal/commands/install.py", line 267, in run
    self.name, wheel_cache
  File "/var/lang/lib/python3.6/site-packages/pip/_internal/basecommand.py", line 314, in populate_requirement_set
    wheel_cache=wheel_cache):
  File "/var/lang/lib/python3.6/site-packages/pip/_internal/req/req_file.py", line 89, in parse_requirements
    for req in req_iter:
  File "/var/lang/lib/python3.6/site-packages/pip/_internal/req/req_file.py", line 156, in process_line
    isolated=isolated, options=req_options, wheel_cache=wheel_cache
  File "/var/lang/lib/python3.6/site-packages/pip/_internal/req/req_install.py", line 206, in from_line
    looks_like_dir = os.path.isdir(p) and (
  File "/var/lang/lib/python3.6/genericpath.py", line 42, in isdir
    st = os.stat(s)
ValueError: embedded null byte
You are using pip version 10.0.1, however version 18.0 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.

    at installRequirements (C:\Users\me\Dropbox\projects\playground\sls\with_rds\node_modules\serverless-python-requirements\lib\pip.js:146:11)
    at ServerlessPythonRequirements.installAllRequirements (C:\Users\me\Dropbox\projects\playground\sls\with_rds\node_modules\serverless-python-requirements\lib\pip.js:242:5)
From previous event:
    at PluginManager.invoke (C:\Users\me\AppData\Roaming\npm\node_modules\serverless\lib\classes\PluginManager.js:390:22)
    at PluginManager.spawn (C:\Users\me\AppData\Roaming\npm\node_modules\serverless\lib\classes\PluginManager.js:408:17)
    at Deploy.BbPromise.bind.then.then (C:\Users\me\AppData\Roaming\npm\node_modules\serverless\lib\plugins\deploy\deploy.js:123:50)
From previous event:
    at Object.before:deploy:deploy [as hook] (C:\Users\me\AppData\Roaming\npm\node_modules\serverless\lib\plugins\deploy\deploy.js:113:10)
    at BbPromise.reduce (C:\Users\me\AppData\Roaming\npm\node_modules\serverless\lib\classes\PluginManager.js:390:55)From previous event:
    at PluginManager.invoke (C:\Users\me\AppData\Roaming\npm\node_modules\serverless\lib\classes\PluginManager.js:390:22)
    at PluginManager.run (C:\Users\me\AppData\Roaming\npm\node_modules\serverless\lib\classes\PluginManager.js:421:17)
    at variables.populateService.then.then (C:\Users\me\AppData\Roaming\npm\node_modules\serverless\lib\Serverless.js:157:33)
    at runCallback (timers.js:810:20)
    at tryOnImmediate (timers.js:768:5)
    at processImmediate [as _immediateCallback] (timers.js:745:5)
From previous event:
    at Serverless.run (C:\Users\me\AppData\Roaming\npm\node_modules\serverless\lib\Serverless.js:144:8)
    at serverless.init.then (C:\Users\me\AppData\Roaming\npm\node_modules\serverless\bin\serverless:43:50)
    at <anonymous>

  Get Support --------------------------------------------
     Docs:          docs.serverless.com
     Bugs:          github.com/serverless/serverless/issues
     Issues:        forum.serverless.com

  Your Environment Information -----------------------------
     OS:                     win32
     Node Version:           8.11.3
     Serverless Version:     1.29.2

I'm running the latest version of the serverless-python-requirements plugin.
Docker version 18.06.0-ce, build 0ffa825
Contents of ./.serverless/requirements.txt

Contents of ./requirements.txt
asn1crypto==0.24.0
cffi==1.11.5
cryptography==2.3
idna==2.7
pycparser==2.18
PyMySQL==0.9.2
six==1.11.0

I get the same error on my macos box too. The function works when invoked locally.
I'd appreciate help getting to the bottom of this.

We don't have any Windows dev boxes, but I wasn't able to recreate this on linux or mac. Here's what I ran:
[:wat] $ sls create -t aws-python3
Serverless: Generating boilerplate...
 _______                             __
|   _   .-----.----.--.--.-----.----|  .-----.-----.-----.
|   |___|  -__|   _|  |  |  -__|   _|  |  -__|__ --|__ --|
|____   |_____|__|  \___/|_____|__| |__|_____|_____|_____|
|   |   |             The Serverless Application Framework
|       |                           serverless.com, v1.29.0
 -------'

Serverless: Successfully generated boilerplate for template: "aws-python3"
Serverless: NOTE: Please update the "service" property in serverless.yml with your service name
[:wat] $ sls plugin install -n serverless-python-requirements
Serverless: Creating an empty package.json file in your service directory
Serverless: Installing plugin "serverless-python-requirements@latest" (this might take a few seconds...)
Serverless: Successfully installed "serverless-python-requirements@latest"
[:wat] $ cat > requirements.txt << EOF
asn1crypto==0.24.0
cffi==1.11.5
cryptography==2.3
idna==2.7
pycparser==2.18
PyMySQL==0.9.2
six==1.11.0
EOF
[:wat] $ cat >> serverless.yml << EOF
custom:
  pythonRequirements:
    dockerizePip: true
EOF
[:wat] $ sls package
Serverless: Installing requirements of requirements.txt in .serverless...
Serverless: Docker Image: lambci/lambda:build-python3.6
Serverless: Packaging service...
Serverless: Excluding development dependencies...
Serverless: Injecting required Python packages to package...

Thanks. Following your steps I successfully packaged a new project. I copied the cat created requirements.txt to the original project and successfully packaged that project.

Glad you got it working! :+1:

I had this same problem today. After spending a lot of time trying to understand what was really happening I finally found out that the requirements.txt was been saved with UTF16 encoding (probably due to me running pip freeze > requirements.txt). The solution was to use a text editor to save the file with UTF8 encoding.
Hope this information can help the next person that stumbles into this problem.

I had this same problem today. After spending a lot of time trying to understand what was really happening I finally found out that the requirements.txt was been saved with UTF16 encoding (probably due to me running pip freeze > requirements.txt). The solution was to use a text editor to save the file with UTF8 encoding.
Hope this information can help the next person that stumbles into this problem.

Works perfectly! Thanks.

I had this same problem today. After spending a lot of time trying to understand what was really happening I finally found out that the requirements.txt was been saved with UTF16 encoding (probably due to me running pip freeze > requirements.txt). The solution was to use a text editor to save the file with UTF8 encoding.
Hope this information can help the next person that stumbles into this problem.

When I saved with UTF8 this way from powershell in my virtualenv
pip freeze | Out-File -Encoding UTF8 requirements.tx
it saved as UTF8 with BOM and then I would get following error when deploying with AWS codebuild on standard ubuntu 2.0 image:
ERROR: Invalid requirement: '·appdirs==1.4.3'
I put cat requirements.txt into my codebuild project and then realized it was saving with a BOM of · from powershell
I was able to resolve this error by opening the requirements.txt file and using vscode with save as encoding: utf8 (without bom)

I got this error because my requirements.txt had corrupted values, try checking its contents.


Does Gateway API support client settings policy

how we implement https://docs.nginx.com/nginx-gateway-fabric/how-to/traffic-management/client-settings/ using Gateway API . I dont see any example . Is it even possible ?

Hi @Coder63, if your question revolves around how to use those said options with NGINX Gateway Fabric, then perhaps https://github.com/nginxinc/nginx-gateway-fabric might be the right avenue for such questions. (CC: @kate-osborn in case you are the right person for this). Though the page that you linked does infact explain how to use the defined ClientSettingsPolicy together with other Gateway API resources.
On the other hand, if by "implement" you meant something else, it would be nice if you can provide more context and details.

@gauravkghildiyal : My POC use case  is move away from nginx-ingress/ Nginx-gateway fabric , individual LB for services on GKE to Gateway API . With gateway.networking.k8s.io CRD's v1.0.0 alone can we do any of the client-settings mainly client_max_body_size.   Thanks

@Coder63 the ClientSettingsPolicy you mention is specific to NGINX Gateway Fabric. If you start a discussion in the NGINX Gateway Fabric here we will be happy to help you out. Thanks!

Is Gateway API v1.1.0 & Nginx Gateway fabric v1.3.0 CRD's extendable like below example ?
apiVersion: gateway.networking.k8s.io/v1
kind: Gateway
metadata:
  name: gateway
spec:
  gatewayClassName: gke-l7-rilb
  listeners:
  - name: http
    port: 80
    protocol: HTTP
    hostname: "*.example.com"
---
apiVersion: gateway.nginx.org/v1alpha1
kind: ClientSettingsPolicy
metadata:
  name: gateway-client-settings
spec:
  targetRef:
    group: gateway.networking.k8s.io
    kind: Gateway
    name: gateway
  body:
    maxSize: "10" # sizes without a unit are bytes.

@Coder63, I've responded to your posted discussion in #3228, but for other people finding this, as @kate-osborn said above, ClientSettingsPolicy is an implementation-specific object from Nginx Gateway Fabric. It is not part of upstream Gateway API and will not work with any other GatewayClass than one implemented by Nginx Gateway Fabric.
In the future @Coder63, I'd encourage you to only ask this sort of question in one place in the repository, so that we don't run the risk of duplicating discussion. I'll close this issue out however, as the question is answered, and further discussion should take place on #3228.


Font Does not apply for "PagerTabStrip"

Hi,
It seems that the font does not apply to the "PagerTabStrip" tab texts.
I have applied the Font on Application level, and inject the font in every Activity of my app.
Font of every elements have changed except text for "PagerTabStrip" Tabs!
Is that correct or I missed something?

See #171 #180, The PaperTabStrip creates views and doesn't inflate them. Basically don't use it. It's super old and will probably be depreciated anyway. Use the https://developer.android.com/reference/android/support/design/widget/TabLayout.html you can set a customViewId on the Tab which will get inflated.

Hello my friend and thanks for your advise.
I have changed that to TabLayout and I still can see that the Font does not apply!
Do I need to implement anythings or just change it to LayoutTab?
The post #170 1nd #180 are to busy and I don't know which one is the FIX!

@elar-systems https://github.com/chrisjenx/Calligraphy/issues/180#issuecomment-198298812


Stuck at "Bot is cooking...  It may take some time"

I had no problem creating new bots on the 0.0.3 version , but on the 1.0.0 Version , i get stuck at "Bot is cooking...  It may take some time" , noting that i tired using all-Mini and OpenAI embedding models and its the same issue .

Are you running the application locally or on railway.app ?

Hey, sorry, but it looks like a migration issue :/ q_13. The only way to fix this is by deleting the existing PostgreSQL folder and Redis, and then restarting the server:
sudo rm -rf .redis
sudo rm -rf .postgres

Idk why your PostgreSQL database has a migration issue since all my new changes won't cause any issues to the existing database. I will look into it

root@PD-OMARMJ:~/dialoqbase/docker# sudo rm -rf .redis
root@PD-OMARMJ:~/dialoqbase/docker# sudo rm -rf .postgres
root@PD-OMARMJ:~/dialoqbase/docker# sudo docker-compose up
Starting redis               ... done
Starting dialoqbase-postgres ... done
Starting dialoqbase          ... done
Attaching to dialoqbase-postgres, redis, dialoqbase
dialoqbase-postgres | The files belonging to this database system will be owned by user "postgres".
dialoqbase-postgres | This user must also own the server process.
dialoqbase-postgres |
dialoqbase-postgres | The database cluster will be initialized with locale "en_US.utf8".
dialoqbase-postgres | The default database encoding has accordingly been set to "UTF8".
dialoqbase-postgres | The default text search configuration will be set to "english".
dialoqbase-postgres |
dialoqbase-postgres | Data page checksums are disabled.
dialoqbase-postgres |
redis            | 1:C 03 Oct 2023 11:32:22.980 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
redis            | 1:C 03 Oct 2023 11:32:22.980 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis            | 1:C 03 Oct 2023 11:32:22.980 * Redis version=7.2.1, bits=64, commit=00000000, modified=0, pid=1, just started
redis            | 1:C 03 Oct 2023 11:32:22.980 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
dialoqbase-postgres | fixing permissions on existing directory /var/lib/postgresql/data ... ok
redis            | 1:M 03 Oct 2023 11:32:22.980 * monotonic clock: POSIX clock_gettime
dialoqbase-postgres | creating subdirectories ... ok
dialoqbase-postgres | selecting dynamic shared memory implementation ... posix
dialoqbase-postgres | selecting default max_connections ... 100
redis            | 1:M 03 Oct 2023 11:32:22.981 * Running mode=standalone, port=6379.
dialoqbase-postgres | selecting default shared_buffers ... 128MB
dialoqbase-postgres | selecting default time zone ... Etc/UTC
redis            | 1:M 03 Oct 2023 11:32:22.981 * Server initialized
redis            | 1:M 03 Oct 2023 11:32:22.981 * Ready to accept connections tcp
dialoqbase-postgres | creating configuration files ... ok
dialoqbase-postgres | running bootstrap script ... ok
dialoqbase-postgres | performing post-bootstrap initialization ... ok
dialoqbase       | yarn run v1.22.19
dialoqbase       | $ npx prisma migrate deploy && fastify start  app.js
dialoqbase-postgres | syncing data to disk ... ok
dialoqbase-postgres |
dialoqbase-postgres |
dialoqbase-postgres | Success. You can now start the database server using:
dialoqbase-postgres |
dialoqbase-postgres |     pg_ctl -D /var/lib/postgresql/data -l logfile start
dialoqbase-postgres |
dialoqbase-postgres | initdb: warning: enabling "trust" authentication for local connections
dialoqbase-postgres | initdb: hint: You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb.
dialoqbase-postgres | waiting for server to start....2023-10-03 11:32:23.616 UTC [49] LOG:  starting PostgreSQL 15.4 (Debian 15.4-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
dialoqbase-postgres | 2023-10-03 11:32:23.620 UTC [49] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
dialoqbase-postgres | 2023-10-03 11:32:23.629 UTC [52] LOG:  database system was shut down at 2023-10-03 11:32:23 UTC
dialoqbase-postgres | 2023-10-03 11:32:23.634 UTC [49] LOG:  database system is ready to accept connections
dialoqbase-postgres |  done
dialoqbase-postgres | server started
dialoqbase-postgres | CREATE DATABASE
dialoqbase-postgres |
dialoqbase-postgres |
dialoqbase-postgres | /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*
dialoqbase-postgres |
dialoqbase-postgres | waiting for server to shut down...2023-10-03 11:32:23.795 UTC [49] LOG:  received fast shutdown request
dialoqbase-postgres | .2023-10-03 11:32:23.799 UTC [49] LOG:  aborting any active transactions
dialoqbase-postgres | 2023-10-03 11:32:23.801 UTC [49] LOG:  background worker "logical replication launcher" (PID 55) exited with exit code 1
dialoqbase-postgres | 2023-10-03 11:32:23.801 UTC [50] LOG:  shutting down
dialoqbase-postgres | 2023-10-03 11:32:23.804 UTC [50] LOG:  checkpoint starting: shutdown immediate
dialoqbase-postgres | 2023-10-03 11:32:23.888 UTC [50] LOG:  checkpoint complete: wrote 918 buffers (5.6%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.013 s, sync=0.065 s, total=0.088 s; sync files=301, longest=0.026 s, average=0.001 s; distance=4223 kB, estimate=4223 kB
dialoqbase-postgres | 2023-10-03 11:32:23.893 UTC [49] LOG:  database system is shut down
dialoqbase-postgres |  done
dialoqbase-postgres | server stopped
dialoqbase-postgres |
dialoqbase-postgres | PostgreSQL init process complete; ready for start up.
dialoqbase-postgres |
dialoqbase-postgres | 2023-10-03 11:32:23.914 UTC [1] LOG:  starting PostgreSQL 15.4 (Debian 15.4-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
dialoqbase-postgres | 2023-10-03 11:32:23.914 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
dialoqbase-postgres | 2023-10-03 11:32:23.914 UTC [1] LOG:  listening on IPv6 address "::", port 5432
dialoqbase-postgres | 2023-10-03 11:32:23.918 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
dialoqbase-postgres | 2023-10-03 11:32:23.922 UTC [65] LOG:  database system was shut down at 2023-10-03 11:32:23 UTC
dialoqbase-postgres | 2023-10-03 11:32:23.927 UTC [1] LOG:  database system is ready to accept connections
dialoqbase       | Prisma schema loaded from prisma/schema.prisma
dialoqbase       | Datasource "db": PostgreSQL database "dialoqbase", schema "public" at "dialoqbase-pg:5432"
dialoqbase-postgres | 2023-10-03 11:32:24.365 UTC [69] LOG:  could not receive data from client: Connection reset by peer
dialoqbase       |
dialoqbase       | 14 migrations found in prisma/migrations
dialoqbase       |
dialoqbase       | Applying migration init
dialoqbase       | Applying migration q_10
dialoqbase       | Applying migration q_11
dialoqbase       | Applying migration q_12
dialoqbase       | Applying migration q_13
dialoqbase-postgres | 2023-10-03 11:32:24.512 UTC [70] ERROR:  relation "BotTelegramHistory" does not exist
dialoqbase-postgres | 2023-10-03 11:32:24.512 UTC [70] STATEMENT:  -- AlterTable
dialoqbase-postgres |   ALTER TABLE "BotTelegramHistory" ADD COLUMN     "new_chat_id" TEXT;
dialoqbase-postgres |
dialoqbase       | Error: P3018
dialoqbase       |
dialoqbase       | A migration failed to apply. New migrations cannot be applied before the error is recovered from. Read more about how to resolve migration issues in a production database: https://pris.ly/d/migrate-resolve
dialoqbase       |
dialoqbase       | Migration name: q_13
dialoqbase       |
dialoqbase       | Database error code: 42P01
dialoqbase       |
dialoqbase       | Database error:
dialoqbase       | ERROR: relation "BotTelegramHistory" does not exist
dialoqbase       |
dialoqbase       | DbError { severity: "ERROR", parsed_severity: Some(Error), code: SqlState(E42P01), message: "relation "BotTelegramHistory" does not exist", detail: None, hint: None, position: None, where_: None, schema: None, table: None, column: None, datatype: None, constraint: None, file: Some("namespace.c"), line: Some(433), routine: Some("RangeVarGetRelidExtended") }
dialoqbase       |
dialoqbase       |
dialoqbase       | error Command failed with exit code 1.
dialoqbase       | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
dialoqbase       | yarn run v1.22.19
dialoqbase       | $ npx prisma migrate deploy && fastify start  app.js
dialoqbase       | Prisma schema loaded from prisma/schema.prisma
dialoqbase       | Datasource "db": PostgreSQL database "dialoqbase", schema "public" at "dialoqbase-pg:5432"
dialoqbase-postgres | 2023-10-03 11:32:26.274 UTC [71] LOG:  could not receive data from client: Connection reset by peer
dialoqbase       |
dialoqbase       | 14 migrations found in prisma/migrations
dialoqbase       |
dialoqbase       | Error: P3009
dialoqbase       |
dialoqbase       | migrate found failed migrations in the target database, new migrations will not be applied. Read more about how to resolve migration issues in a production database: https://pris.ly/d/migrate-resolve
dialoqbase       | The q_13 migration started at 2023-10-03 11:32:24.510138 UTC failed
dialoqbase       |
dialoqbase       |
dialoqbase       | error Command failed with exit code 1.
dialoqbase       | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
dialoqbase exited with code 1
dialoqbase       | yarn run v1.22.19
dialoqbase       | $ npx prisma migrate deploy && fastify start  app.js
dialoqbase       | Prisma schema loaded from prisma/schema.prisma
dialoqbase       | Datasource "db": PostgreSQL database "dialoqbase", schema "public" at "dialoqbase-pg:5432"
dialoqbase       |
dialoqbase       | 14 migrations found in prisma/migrations
dialoqbase       |
dialoqbase       | Error: P3009
dialoqbase       |
dialoqbase       | migrate found failed migrations in the target database, new migrations will not be applied. Read more about how to resolve migration issues in a production database: https://pris.ly/d/migrate-resolve
dialoqbase       | The q_13 migration started at 2023-10-03 11:32:24.510138 UTC failed
dialoqbase       |
dialoqbase       |
dialoqbase       | error Command failed with exit code 1.
dialoqbase       | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
dialoqbase exited with code 1
dialoqbase       | yarn run v1.22.19
dialoqbase       | $ npx prisma migrate deploy && fastify start  app.js
dialoqbase       | Prisma schema loaded from prisma/schema.prisma
dialoqbase       | Datasource "db": PostgreSQL database "dialoqbase", schema "public" at "dialoqbase-pg:5432"
dialoqbase-postgres | 2023-10-03 11:32:30.060 UTC [75] LOG:  could not receive data from client: Connection reset by peer
dialoqbase       |
dialoqbase       | 14 migrations found in prisma/migrations
dialoqbase       |
dialoqbase       | Error: P3009
dialoqbase       |
dialoqbase       | migrate found failed migrations in the target database, new migrations will not be applied. Read more about how to resolve migration issues in a production database: https://pris.ly/d/migrate-resolve
dialoqbase       | The q_13 migration started at 2023-10-03 11:32:24.510138 UTC failed
dialoqbase       |
dialoqbase       |
dialoqbase       | error Command failed with exit code 1.
dialoqbase       | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
dialoqbase exited with code 1
dialoqbase       | yarn run v1.22.19
dialoqbase       | $ npx prisma migrate deploy && fastify start  app.js
dialoqbase       | Prisma schema loaded from prisma/schema.prisma
dialoqbase       | Datasource "db": PostgreSQL database "dialoqbase", schema "public" at "dialoqbase-pg:5432"
dialoqbase       |
dialoqbase       | 14 migrations found in prisma/migrations
dialoqbase       |
dialoqbase       | Error: P3009
dialoqbase       |
dialoqbase       | migrate found failed migrations in the target database, new migrations will not be applied. Read more about how to resolve migration issues in a production database: https://pris.ly/d/migrate-resolve
dialoqbase       | The q_13 migration started at 2023-10-03 11:32:24.510138 UTC failed
dialoqbase       |
dialoqbase       |
dialoqbase       | error Command failed with exit code 1.
dialoqbase       | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
dialoqbase exited with code 1
^CGracefully stopping... (press Ctrl+C again to force)
Stopping dialoqbase          ... done
Stopping dialoqbase-postgres ... done
Stopping redis               ... done

Hey, I'm releasing a patch now. Sorry for the issue

Hey, a patch has been released. Please check if you still encounter the error.
Use the following commands:
sudo docker-compose pull
sudo rm -rf .redis
sudo rm -rf .postgres


Spring cloud consul with Feign Client

I am trying to use @FeignClient annotation with consul agent to discover a service. I have a spring boot application which is trying to invoke another spring boot application using RestTemplate. I want to replace resttemplate with Feign Client implementation. Below is the Feign client having consul url.
@FeignClient(value= "service-name", url = "http://localhost:8500")
public interface InterceptTargetStoreFeignClient {
@RequestMapping(value = "/abc", method = RequestMethod.GET)
ResponseEntity<gpb object> getAbc();

}
Invoking the URL is giving 404 error. Any help will be appreciated

Is your service running on http://localhost:8500? I suspect it's not and you just put the consul api url there. Remove the url attribute.

Thanks for the reply. It seems I made some progress. Yes the consul service is running. Removed the "url" attribute and added dependencies for "consul" and added annotation "@EnableDiscoveryClient". Making a call to health URL works but I have an API that returns GPB and some accept GPB. In rest template, I usually set the content type in the headers. Can it be done with Feign as well ?

You will want to use Spring MVC annotations to set the appropriate headers.

Thanks all worked !


How to limit the output mp4 file zsize?

Hi @pmeenan ,
Thanks for your useful tool that can help record iOS device.
But I found that the output mp4 file is tool large(40s=50MB), if there is a way to limit the output file size within the commandline parameter?
Thanks
Luis

Sorry, no.  Right now it is hard-coded to record at the highest quality: https://github.com/WPO-Foundation/xrecord/blob/master/xrecord/capture.swift#L22
It shouldn't be too hard to add a command-line setting that let you pick the medium or low quality settings though you'll sacrifice the quality of the actual recording: https://github.com/WPO-Foundation/xrecord/blob/master/xrecord/capture.swift#L22
The size of the video is largely going to depend on what is happening on the screen (the more it changes the bigger the files).  Setting a file size limit would just truncate the video earlier so I'm assuming that's not what you want.
For the best control over it I recommend using ffmpeg to post-process the video after it was recorded.  You could resize it to be lower resolution and adjust the quality with a lot more control.
I'm happy to add the 3-level quality settings to the command-line if that would help but I don't know if that will give you the control you're looking for.

Thanks, I tried the ffpmeg to compress the video before you instrumention. It works fine.
Look forward your new innovation.

There is now a --quality setting that lets you specify low, medium, high or photo.  It may still not give you the exact quality/size you are looking for and ffmpeg still gives you a lot more knobs but it may help.


list-group has double border if last element on card (v4)

I've added a box shadow to cards via the following css
.card {
  box-shadow: 0 0.125em lightgrey;
}

If my last element is a list-group list-group-flush then it looks like there's a second border.

Whereas if the last element on a card is something else, like an empty card-block, it looks fine.

If this doesn't happen without your custom CSS, then it's a bug in your CSS, not in Bootstrap.
Support questions related to custom CSS don't belong on this issue tracker; see https://github.com/twbs/bootstrap/blob/master/CONTRIBUTING.md#using-the-issue-tracker

It appears to occur independently of the box-shadow addition: https://jsfiddle.net/orheqwk0/1/

You're absolutely right about the custom css bit. I'm sorry, I should have explained better - I mentioned it because that's when the issue became obvious to me.
I should have taken the shadow off and added screenshots without it.

Fixed with a22d2fb.


logging

Clear warning, add logging. Closes #104

@volodya-lombrozo At the moment I need logs for tests, not parsing and transformations. This is due to the fact that compilation tests take quite a long time and I need to make sure that these are the reasons for the PR merging timeout.
I agree that it is better to move logging closer to the intended problem, so I only left logs in dataize. It seems to me that there is not much to expand the context here, because it is just a method called in assert.

@volodya-lombrozo What do you think?

@volodya-lombrozo Thanks for review.
@yegor256 I agree that this PR can be merged.

@rultor merge

@rultor merge

@yegor256 Done! FYI, the full log is here (took me 57min)


Update fzf#install to handle spaces on Windows

Didn't see any issues addressing this problem, or any other pull requests. Should fix problems for Windows users that have a space in the plugin path.

So this will fix #2992, right?

No, I'm still not sure what's causing the issue with #2992. For the moment, I'm avoiding using fzf#install() since using a manual install (~\.fzf\bin\fzf.exe) works just fine. This was a separate issue I noticed for a while but didn't have time to investigate. I have a space in my home directory path, so this fixes that for myself and anyone else with a similar issue.

I see, thanks for the explanation. The patch is merged, thanks!


Add boundary.country section and info to autocomplete docs

Connects https://github.com/pelias/pelias/issues/403

LGTM

:shipit:

Let's :shipit: since the feature is getting rolled out today.


Add ability to invoke services in actions via event

Signed-off-by: Tihomir Surdilovic<EMAIL_ADDRESS>Many thanks for submitting your Pull Request :heart:!
Please specify parts this PR updates:

[x] Specification
[x] Examples
[x] Schema
[ ] Roadmap
[ ] Use Cases
[ ] Community
[ ] Website
[ ] SDK
[ ] TCK
[ ] Other

What this PR does / why we need it:
Some services cannot be invoked via a source uri but only via events. This pr adds the ability to reference a trigger and result event in action definitions to cover this scenario.
Also for event correlation rules, we only so far allow a single string-based "token" which references a name of a CE context attribute. Adding ability to add more than one correlation rule as well as be able to correlate on context attribute value of multiple events to be the same, as well as set a specific value of a context attribute.
Special notes for reviewers:
Additional information (if needed):

rebased


Also search on the domain name for the virtual domain name in the ldap

See #638

@johansmitsnl, @tomav the tests are passing because we have currently no explicit unit test for virtual domains. We should extend the tests, so that we cover at least:

does the the provided file gets copy / is in place
extend the var substitution check for the new added file
extend the mail delivery checks for ldap based virtual domains

@alinmear agree to the tests. I'm not very familiar with the test of this project, could you create them based on the pull request?

@johansmitsnl when i have time, i can check how to implement the tests.

I have reworked the PR.
Tested on my server environment and it works.
I also added LDAP_QUERY_FILTER_DOMAIN ENV variable to customise the query as other ldap filters.
It should make these tests:

uid different from the user part of the email: uid: username | email<EMAIL_ADDRESS>postfix test for vhosts: email<EMAIL_ADDRESS>Test email delivery for the alias/group

When the escaping is fixed remove the \| from the makefile on the LDAP_QUERY_FILTER_DOMAIN
My production env that is used (and working):
      - VIRTUAL_HOST=mail.xxx.net
      - LETSENCRYPT_HOST=mail.xxx.net
      -<EMAIL_ADDRESS>      - ENABLE_SPAMASSASSIN=1
      - ENABLE_CLAMAV=1
      - ENABLE_FAIL2BAN=1
      - ENABLE_FAIL2BAN=0
      - ENABLE_POSTGREY=0
      - ONE_DIR=1
      - DMS_DEBUG=0
      - ENABLE_MANAGESIEVE=1
      - SSL_TYPE=letsencrypt
      - SASLAUTHD_PASSWD=
      # >>> SASL Authentication
      - ENABLE_SASLAUTHD=1
      - SASLAUTHD_LDAP_SERVER=ldap
      - SASLAUTHD_LDAP_PROTO=
      - SASLAUTHD_LDAP_BIND_DN=cn=admin,dc=xxx,dc=net
      - SASLAUTHD_LDAP_PASSWORD=xxx
      - SASLAUTHD_LDAP_SEARCH_BASE=dc=xxx,dc=net
      - SASLAUTHD_LDAP_FILTER=(&(objectClass=PostfixBookMailAccount)(uniqueIdentifier=%U))
      - SASLAUTHD_MECHANISMS=ldap
      # <<< SASL Authentication
      # >>> Postfix Ldap Integration
      - ENABLE_LDAP=1
      - LDAP_SERVER_HOST=ldap
      - LDAP_SEARCH_BASE=dc=xxx,dc=net
      - LDAP_BIND_DN=cn=admin,dc=xxx,dc=net
      - LDAP_BIND_PW=xxx
      - LDAP_QUERY_FILTER_ALIAS=(&(mailAlias=%s)(mailEnabled=TRUE))
      - LDAP_QUERY_FILTER_GROUP=(&(mailGroupMember=%s)(mailEnabled=TRUE))
      - LDAP_QUERY_FILTER_USER=(&(mail=%s)(mailEnabled=TRUE))
      - LDAP_QUERY_FILTER_DOMAIN=(&(\|(mail=*@%s)(mailalias=*@%s)(mailGroupMember=*@%s))(mailEnabled=TRUE))
      # <<< Postfix Ldap Integration
      # >>> Dovecot Ldap Integration
      - DOVECOT_USER_FILTER=(&(objectClass=PostfixBookMailAccount)(\|(uniqueIdentifier=%n)(mail=%u)))
      - DOVECOT_PASS_FILTER=(&(objectClass=PostfixBookMailAccount)(\|(uniqueIdentifier=%n)(mail=%u)))
      # <<< Dovecot Ldap Integration

Welcome @alinmear in docker-mailserver collaborators :-)

@tomav thx for adding me ;)

Not sure why tests are failing. Did a rewrite of the PR 3 times now and before this last rewrite it was ok. Could @alinmear or @tomav take a look at it before more changes are made to master?

Restarted build.

@johansmitsnl i will check this on the weekend.

@alinmear thnx, currently on holidays, but I'll check in every now and then.

@tomav @alinmear I have updated the PR with tests and they pass all now.
Can someone review and accept if ok?

@tomav @alinmear I have updated the PR with tests and they pass all now.
Can someone review and accept if ok?

@johansmitsnl looks good to me; thx for the contribution. Anyone else, otherwise i would merge it?!


The NHS QR code still doesn't work

Describe the bug
Scanning the NHS results in an invalid certificate error
Expected behaviour
NHS QR code should be valid
Technical details
I took a quick look at the validation tests and replaced the bodyStr with the one coming from the NHS QR code, the problem seems to be the format of the JSON contained in the NHS QR, it's not valid (properties like -260 and 1 are not in quotes, and other properties use single quotes instead of double). It means the JSON parse fails
Possible Fix
As a temporary fix, maybe check if the JSON is valid and if not do a string replace and add quotes (and replace single quotes with double)

I had a chat with Andrea, probably the validation only fails in the test. The UK certificates haven't been loaded yet, that should solve the issue.

Do we know when the certificates will be loaded? It fails to verify using the public 1.1.0 verifica release and my (genuine) UK QR code now.

My NHS-issued QR code is now been correctly verified. Thank you!


ReadPreference and slaveOk

While setting read preference on a secondary, i get this error: not master and slaveOk=false.
But I can't find how to set it with the driver.
Thanks!

Can you paste an example code that results in this behavior?
We are aware of one case where this happened which is fixed now; https://jira.mongodb.org/browse/PHPC-441
But that case should be very bleeding edgecase you should never experience in an normal usage of the driver.

Thanks, I recompiled from master and it seems that it has been solved by this fix.
But I don't think it was an edge case.
the read preference used: new ReadPreference(ReadPreference::RP_NEAREST, [])
and the query was just a basic find([])

Interesting.
Were you connecting to a secondary directly? (e.g. not provding the "replicaSet=name" option to the uri?)
I guess we underestimated the impact of this issue :/

It was not in the uri, but in the options of the Client (2nd argument).

Can you post the actual line you constructed the Manager with?
It may have been a different bug.

recompiled from master

@vlechemin: Additionally, can you tell us what versions of the extension (actual release) and this library (commit hash would be fine) you were using?
I assume you were on 1.0.0beta2 of the extension, as there shouldn't be anything its master branch that would have affected read preference application unless this was actually an issue with the underlying C driver (we recently bumped things from 1.2.0rc0 to 1.2.0 final).

On second thought, this might have been PHPC-441, which was resolved with bumping the C driver to 1.2.0 final (and currently only in the extension's master branch). PHPLIB makes heavy use of these hinted queries, since we do server selection manually and then execute commands, queries, and writes directly on Server objects (instead of through the Manager).

@bjori, it was with the wrapper provided by the php lib:
new MongoDB\Client('mongodb://host1,host2/dbname', [
    'replicaSet' => 'rsName',
    'username' => 'user',
    'password' => 'pwd',
])

hi @jmikola, it was the beta1 from this archive: https://s3.amazonaws.com/drivers.mongodb.org/hhvm/hhvm-mongodb-1.0beta1.tgz
and the version of the lib is: fbb10fec3c423d306a76e0915688c09e0272547f

@vlechemin: Thanks for confirming. The bump to libmongoc 1.2.0 was done after the HHVM driver's 1.0.0-beta1 release (see changelog). If you're willing to recompile its master branch and confirm that it solves the issue, that'd be appreciated. Otherwise, we should have a new HHVM tag cut later in the week for you to test with.

I think I misunderstood when you asked about the hash, the one for the driver is a89194261edbd1eb3fdb8cbf808a767866b29403 and had the commit about libmongoc 1.2.0.
Everything is working fine now, thank you

:+1:


Limit batches in PDisk, add lwprobes to detect batch bursts

Changelog entry
...
Changelog category

New feature
Experimental feature
Improvement
Performance improvement
Bugfix
Backward incompatible change
Documentation (changelog entry is not required)
Not for changelog (changelog entry is not required)

Additional information
...

moved to https://github.com/ydb-platform/ydb/pull/9099


Koa parameter names don't match zod/openapi schema and causes validation errors

So for example this is what I have in my openapi schema
  /v1/users/{user_id}:
    get:
      operationId: UserGetById
      description: Get a user by ID.
      tags: [users]
      parameters:
        - name: user_id
          required: true
          in: path
          schema: { $ref: '#/components/schemas/Identifier' }
      responses:
        default: { $ref: '#/components/responses/InternalServerError' }
        '404': { $ref: '#/components/responses/NotFound' }
        '401': { $ref: '#/components/responses/Unauthorised' }
        '200': { $ref: '#/components/responses/UserGetByIdOK' }

as you can see I have the parameter as user_id and the generated schema for this becomes
const userGetByIdParamSchema = z.object({ user_id: s_Identifier })

so far this all looks fine, until you look at the route that is generated
router.get("userGetById", "/v1/users/:userId", async (ctx, next) => { ... }

and now you'll notice it's checking against userId and not user_id which leads to a validation error. I'm aware I could just rename the parameter in my openapi file to match the koa parameter, but it's probably a good idea to address this, so it's not an annoying requirement.

Good spot, thanks for reporting. Fixed in #120, apologies for the delay was taking a bit of a break over Christmas.


Automatically generate the widget usages

I think we could make our JSDoc parser generate the usage as well to ensure we keep them always synchronized and DRY.
const usage = require('./usage');

module.exports = `Usage:
@function({
  @mandatoryArg,
  [...]
  [ @optionalArg=@defaultValue ],
  [ [...] ]
})`;

Yes! We could have everything in the js doc :)

Nobody showed up to build this and we never had to revisit it: not a true blocker


Connection between two nodes.

@campagnola:
The commit 8e21cfbbb45674febd00fe4e6cf543b635396406 can be remove if you dont like it.
It is just a try.

Hi Luke:
this is a very long PR:
* NodeGroup and QApplication more clean
* Node and NodeWidget can be lanch locally or distantly
* StreamSender and Stream receiver with socket plaindata or sharedarray
* remotly register Node
* some test with webcam
What I am not happy:

the way how Node connect them. We need some more deep discussion about that.
Connection bewteen local apps Node and distant nodes.

All is quite drafty but there tests.

Hi luke I have push some changes and try to fix your conerns.
Tell me your thnogth.

Travis is complaining about the size.
"Estimated content size difference = 148 kB"
I guess it is in the .travis.yaml.
What shall we do ?

You can ignore that error--it's just a warning to make sure we don't
accidentally merge large files.
On Thu, Aug 27, 2015 at 10:42 AM, Garcia Samuel<EMAIL_ADDRESS>wrote:

Travis is complaining about the size.
"Estimated content size difference = 148 kB"
I guess it is in the .travis.yaml.
What shall we do ?
—
Reply to this email directly or view it on GitHub
https://github.com/pyacq/pyacq/pull/14#issuecomment-135455728.

Any other comments for this very long PR ?

Do you anderstand the travis segmentation fault ?
It occurs after all tests pass ?
It is in rpc stuff...
Any ideas ?

No clue about the segfault. This is exactly why it's so important to be meticulous about threading--in my experience with acq4, there are two things that cause segfaults more than any other: multithreading mistakes (which is why the 0MQ folks consider "shared state" to be a fundamentally broken programming model), and misuse of Qt (which is why I started this: http://stackoverflow.com/questions/11945183/what-are-good-practices-for-avoiding-crashes-hangs-in-pyqt ).
I would start by adding faulthandler.enable(all_threads=True) to see if we can get more information about the crash. If you can make it crash locally, that will greatly improve the chances of discovering the cause. If it crashes when the application exits, then it's very likely to be caused by some mishandling of Qt (perhaps creating QObjects without parents).

I don't think that it is QtThread relative. It is in RPC and so inanother process.
The strange thing is that it occurs AFTER that all tests are passed!!
How is it possible ?

If it's after the tests have passed, then it is probably caused by Qt tearing down incorrectly when python exits (which is usually fixed by making sure the QObject hierarchy is set up correctly). I'm trying to run the tests on my end but I seem to have a broken pytest..


python311Packages.python-smarttub: 0.0.33 -> 0.0.34

Diff: https://github.com/mdz/python-smarttub/compare/refs/tags/v0.0.33...v0.0.34
Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 265328 at 97408c6d run on aarch64-darwin 1

2 packages failed to build:

python310Packages.python-smarttub
python311Packages.python-smarttub

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

5 packages built:

home-assistant-component-tests.smarttub
python310Packages.python-smarttub
python310Packages.python-smarttub.dist
python311Packages.python-smarttub
python311Packages.python-smarttub.dist


Update 02-third-party.md

This syntax looks outdated.
I've just copy-pasted the following module declaration from the docs:
declare module "lodash" {
  declare module.exports: {
    find<T>(list: Array<T>, properties: Object): T;
  };
}

and it results in:
flow-typed/npm/lodash.js|2 col 26 error|  Unexpected token {

I have no idea what happened, but now everything works as expected, sorry!


Public Distributed lib not available

Hi, my suggestion is to distribute lib with either Gradle/Maven using jitpack or any other distributor.
This makes easy to include this project as lib rather than adding as Dependency module( which is meaning less for most of the developers :)
Thanks

Is there any progress on this?


which port does rclone used for uploading file to google drive?

which port does rclone used for uploading file to google drive?

The source port is controlled by the TCP implementation on your machine.
The destination port is https/443

BTW If you are wanting to do QoS then look at the --bwlimit flag.

using port 443 if i am not wrong

thanks @sjurtf

BTW If you are wanting to do QoS then look at the --bwlimit flag.

This is not correct. bwlimit flag is a permanent bwlimit.  QOS throttles the application while other network devices are in use and has the ability to provide full speed when they are not in use.  This is a preferred option as it is more efficient.


[Design] OpenIdConnect needs a definition for agumenting the 'state' parameter on request.

If a users wants to add to the 'state' parameter when sending a request, there is no easy way to do this.

Adding custom properties to AuthenticationProperties when calling HttpResponse.Challenge sounds rather easy for me. Do you have something particular in mind?

That works fine with Challenge(...). I am thinking about a user that is hooking the RedirectToIdentityProviderNotification. The runtime sets OpenIdConnectMessage.State with protected AuthenticationProperties before the call. How would a user add to the state. I am thinking that it maybe we may want to pass the AuthenticationProperties to the notification and protect afterwards.

This should be done as part of the recent PR that was merged.


Gettext

How about including gettext?

It is available from the python standard lib. You probably just need an import?
$ docker run -it --rm django python
Python 3.4.3 (default, Oct 23 2015, 22:19:50)
[GCC 4.9.2] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import gettext
>>> gettext.gettext("Hello, World!")
'Hello, World!'
>>>

I'm actually talking about GNU gettext.
From https://docs.djangoproject.com/en/1.8/topics/i18n/translation/#message-files:

The makemessages command (and compilemessages discussed later) use commands from the GNU gettext toolset: xgettext, msgfmt, msgmerge and msguniq.

The minimum version of the gettext utilities supported is 0.15.

I see; that seems valid to add to the image.  Want to make a PR?


[Question] Is there a way to exclude all commands to be send to chat?

Checks

[X] I confirm that I have searched for existing issues / pull requests before reporting to avoid duplicate reporting.
[X] I confirm that I noted that if I don't follow the instructions, the issue may be closed directly.

Description
I am new to this mod (I come from DisFabric, but that one doesn't seem to work for me atm). I don't like that other people can see the commands that I write (as an admin, or whilst using WorldEdit). Is there a way to disable all (worldedit) commands from being send in stead of having to write every single one?
I tried to exclude "/" and "/." or "/*", but that didn't work.
PS. All WorldEdit commands start with "//", by which I don't seem to be able to dissable any of them, like "//pos1"

Is your broadcastPlayerCommandExecution option set to false? Not sure how worldedit command works.


docs: add bridge-history deployment in readme

Purpose or design rationale of this PR
PR title
Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:

[x] docs: Documentation-only changes

Deployment tag versioning
Has tag in common/version.go been updated or have you added bump-version label to this PR?

[x] Yes

Breaking change label
Does this PR have the breaking-change label?

[x] No, this PR is not a breaking change

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 56.11%.  Consider uploading reports for the commit e27dcbd to get more accurate results

Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #1281   +/-   ##
========================================
  Coverage    56.11%   56.11%
========================================
  Files          156      156
  Lines        12131    12131
========================================
  Hits          6807     6807
  Misses        4798     4798
  Partials       526      526

Flag
Coverage Δ

bridge-history-api
72.50% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Add a 'Retry' Status

Is your feature request related to a problem? Please describe.
As we are running are cucumber scenarios using wdioParallel, each of our features are split into their own scenarios, therefor for the retrying of failing tests we make use of the specFileRetries option in the config file.
This means that when a single test is retried, it is then added as an additional test instead. The report the shows the test as 2 failing tests rather than the preferred 1 failing test and 1 retried test.
Describe the solution you'd like
I would like a way for the report to group the retried tests together showing that the test has failed and has retried x number of times. (if if we are allowing 2 retry attempts and the test passes on the second attempt, we would like to see the failed attempts before the passing attempt.)
Describe alternatives you've considered
I have tried overwriting the the result status, but this doesnt fixing the skewing test numbers where retries are being counted as additional tests.
Additional context

this image shows my example, of 2 tests running, 1 passing and 1 failing with 2 retry attempts (i have overwritten the status to be ambiguous to try and differentiate the retry attempts) But it is still appears as 4 test being executed vs just the desired 2.

Hi @stephenrafferty3
Any change that you can share a sample output from the wdioParallel service that you are referring to? That would help in understanding the issue

the main part of the output im referring to is result":{"status":"failed"}, a status type of "retry", which is not counted towards the total number of unique tests would solve this issue.
Is that the output information you require?

Not sure what you mean, can you elaborate it a bit more what you want / expect?

I think that this issue is related to https://github.com/WasiqB/multiple-cucumber-html-reporter/issues/221


add missing space

PR for issue
What is being addressed
Describe the current behavior you are modifying
How is this addressed

Describe the changes made, and if appropriate, why they are addressed this way
Note any pending work (with links to the issues that will address them)

@dvoet thanks, I'm guessing you are David, and this is a fix for the nexus account setup issue meninges on a call this week?! Apologies if I'm guessing incorrectly.
Can you edit the PR description to explain please, and I'll test and merge.

No, this is Doug Voet from The Broad Institute. We met last week. I ran into this problem in the script setting up nexus for the first time.

Sorry, and thanks! I'll take a look at it tomorrow. Expect its the same issue someone else hit.

it's a trivial thing, a missing space between a value and the next parameter name in a command line call


articles/openshift/support-lifecycle: "outside of the support", etc.

Surrounding text use "outside of support", so adjust for consistency.  Also shift "are voided" to get "guarantees are voided" close together, without having the "for clusters ..." qualifier in the middle of the effect description.
Also fix the . -> , typo for "'before receiving support".

@wking : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@wking : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#label:"aq-pr-triaged"

#sign-off

#reassign:rayoef

#sign-off

#unassign-reviewer:sakthi-vetrivel

#assign-reviewer:rayoef

#sign-off

#sign-off

@johnmarco
Thanks for the review! The article has been updated since this pull request was opened, and the proposed changes are already reflected there: https://learn.microsoft.com/en-us/azure/openshift/support-lifecycle.
We'll close this PR.


Export component's and path's types with friendly names

Description
First of all, I want to thank you for this great lib! :)
To make it even better, I suggest exporting component types and paths like open-api-generator does.
Proposal
The first attempt to implement this is here https://github.com/drwpow/openapi-typescript/pull/1260.
The idea is to generate types like this:
Components:
export type SchemaSimpleUser = components["schemas"]["simple-user"];
export type SchemaInstallation = components["schemas"]["installation"];
...
export type ResponseNotFound = components["responses"]["not_found"];
export type ResponseRequiresAuthentication = components["responses"]["requires_authentication"];
...
export type ParameterPerPage = components["parameters"]["per-page"];
export type ParameterPage = components["parameters"]["page"];
...
export type HeaderLink = components["headers"]["link"];
export type HeaderXRateLimitLimit = components["headers"]["x-rate-limit-limit"];

Paths:
export type RequestEnterpriseAdminListGlobalWebhooks = paths["/admin/hooks"]["get"]["parameters"];
export type RequestEnterpriseAdminGetGlobalWebhook = paths["/admin/hooks/{hook_id}"]["get"]["parameters"];

It would be also nice to generate types for requestBody and responses, but not sure how to properly handle content type (application/json, application/yaml etc.)
We also need to resolve the duplication issue described in this comment https://github.com/drwpow/openapi-typescript/pull/1260#issuecomment-1658694431. This can be solved by adding a number as a suffix to the duplicate name.
Checklist

[x] I’m willing to open a PR for this (see CONTRIBUTING.md)

Just for cleanup: this already exists at #1414; closing this to track that.
This solution has been frequently-requested, but is fraught with problems and gotchas (since OpenAPI allows so many characters that are not valid JS identifiers, not to mention conflicts, it makes this approach non-deterministic and full of edge cases that amount to a significant amount of work, to result in what is only a cosmetic difference of what’s available in the library today.
The current status of this is if someone can open a PR that meets full requirements this will be accepted, but so far it’s been too much work to take on.


fix(FormField): fix aria-invalid on error false

If error is false, <Form.Field error={false} /> aria-invalid is set to undefined. So it will not be present anymore. I also added some tests for aria-invalid

Codecov Report

Merging #4043 into master will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master    #4043   +/-   ##
=======================================
  Coverage   99.84%   99.84%
=======================================
  Files         183      183
  Lines        3276     3280    +4
=======================================
+ Hits         3271     3275    +4
  Misses          5        5

Impacted Files
Coverage Δ

src/collections/Form/FormField.js
100.00% <ø> (ø)

src/modules/Dropdown/Dropdown.js
100.00% <100.00%> (ø)

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 1c24915...6fddcc7. Read the comment docs.

Can you please update your PR description to have Fixes #4042, this will auto close the issue?
https://docs.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword

Can you please update your PR description to have Fixes #4042, this will auto close the issue?
https://docs.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword

Sorry, forgot about that, just added it :)


Added Travis Continuous Integration

Is this ready?

@ylow - yes this is ready. If it looks good please merge.


Update to tower 0.5

Tower 0.5 includes some breaking changes that do not impact this crate's usage.

Thanks - v0.9 is published on crates.io!


[Combat] Create option to hide non-relevant stages of the Grayscales.

After making the improvement of adding the new grey scale rows, find a way to hide them when a character doesn't have need of them. (probably just toggle buttons)

If possible, I think that the only thing needed for this is a drop-down menu for every point on the current form of the PTGS. In the same way that we already have for changing the wound type (Bu/Su/Li/Mi/Se/Tr/M), we could have one for shade too (B/G/W). That way it takes up less visual space and is still quite clear and easy to use. It doesn't even really need any logical functions tied to it, the mechanical aspects are already handled by wound type. The shade is just for visual reference.
On top of that, I don't think it's even mathematically possible for a creature to have a health bar that spans all the way from Black to White (just based on the way the spacing of the PTGS is calculated), so overlap would almost never be an issue.

I agree this would be relevant really only for a couple characters and monsters, but I think it should be an option in any case. I know for one of they characters it was super handy (they had gray MW). Aimed mostly been a GM aid, but will likely fold this into a monster burner option. Closing this :)


feature :Email Messaging System

Email Messaging System
Contribution Idea: Create an integrated email messaging feature that allows users to send and receive emails within the app.

@RiyaJain8114 Assign me this issue..
i will make UI of email send with using them users will able to send mail to anyone..

@RiyaJain8114  You are Assigned.

@RiyaJain8114 Hey, there is no auto routing after filling this signin form. so can you help me with this problem.


Bumping up DAPLink interfaces will/may happen in the near future

Description

Issue request type

[ ] Question
[x] Enhancement
[x] Bug

https://github.com/ARMmbed/mbed-os-tools/blob/master/src/mbed_os_tools/detect/windows.py#L36 needs future proofing.

Internal Jira reference: https://jira.arm.com/browse/MBOCUSTRIA-1074

@brianesquilona What is the issue?

@loverdeg-ep we looked at this offline, but basically @brianesquilona was experimenting with the composite USB device of the firmware and found that Mbed LS would no longer detect the mount point for the device. I'm pretty sure this is the reason for his particular issue (I asked him to put up an issue so we didn't lose track of it).

My comment should have been more descriptive.
I'm a fan of most things DAPLink and was just curious what "bumping up" meant.
I checked the linked line of code and assumed increasing the number of devices within the composite but was lost as to the context of the issue.

@brianesquilona told me offline that this change will no longer be needed, so closing this now.


Jenkins+Windows node configuration issue

While configuring a windows node to my Jenkins master which is hosted in an AWS machine i found that, there is no option "Let Jenkins control this windows agent as a windows service" available under launch method field. Is there a way to enable this option?

actually this is the process

launch a windows node and
then goto your jenkins server and then configure the node, once you configured the node then you will get some commad copy that command
next move on to windows node and execute that command or write a windows service for using that command.

I think this is useful to you if not please ignore.


Support ONNX export for Streaming CTC Encoder

Thank you for the great work!
any chance you could make an export for the offline version as well ?

Hi, thanks for asking.
You might want to check this script
https://github.com/k2-fsa/icefall/blob/master/egs/librispeech/ASR/zipformer/export-onnx-ctc.py
for the non-streaming CTC model exporting. Please see if this one fits
your needs.
On Thu, Dec 21, 2023 at 5:48 AM joazoa @.***> wrote:

Thank you for the great work!
any chance you could make an export for the offline version as well ?
—
Reply to this email directly, view it on GitHub
https://github.com/k2-fsa/icefall/pull/1413#issuecomment-1865187787, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AOON42BOM6DY3LDHK7S5AI3YKNMKRAVCNFSM6AAAAABASNLXFGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRVGE4DONZYG4
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

@JinZr  is there already support for zipformer CTC offline for sherpa?

yes, i think the support has been finalized for a while.
Best Regards
Jin
joazoa @.***>于2023年12月23日 周六08:30写道：

@JinZr https://github.com/JinZr is there already support for zipformer
CTC offline for sherpa?
—
Reply to this email directly, view it on GitHub
https://github.com/k2-fsa/icefall/pull/1413#issuecomment-1868150482, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AOON42EZWWBSDV3JMMPAQ63YKYQ3HAVCNFSM6AAAAABASNLXFGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRYGE2TANBYGI
.
You are receiving this because you were mentioned.Message ID:
@.***>


4oD extractor, with a testcase

mostly unusable, since FlashAccess DRM is not implemented, here or in ffmpeg.
youtube-dl can at least download subtitles and metadata, and make the stream URL available through -j for external decryption.
see also: #2050

If I get it right, all channel4 videos are DRM protected. So, despite subtitles and metadata extraction, I see little sense in extractor that will grab unplayable videos, as downloading playable media is the primary purpose of youtube-dl.


Penn Treebank throws tuple out of range error when NUM_LAYER=1

Bug Reports/Feature Requests/Usage Questions Only:
Bug reports or other problems with code: PLEASE always include

What you did. (command you run and changes you made if using examples; post or describe your code if not)
When I edit so that NUM_LAYER=1 in
examples/PennTreebank/PTB-LSTM.py

What you observed, e.g. as much as logs possible.
File "PTB-LSTM.py", line 87, in _build_graph
tf.assign(state_var[1].c, last_state[1].c),
IndexError: tuple index out of range

What you expected, if not obvious.

Your environment (TF version, cudnn version, number & type of GPUs), if it matters.
TF 1.4.1

About efficiency, PLEASE first read http://tensorpack.readthedocs.io/en/latest/tutorial/performance-tuning.html

Feature Requests:

Improve an existing feature.
Add a new feature. Please note that, you can implement a lot of features by extending tensorpack
(See http://tensorpack.readthedocs.io/en/latest/tutorial/index.html#extend-tensorpack).
It may not have to be added to tensorpack unless you have a good reason.
Note that we don't implement papers at others' requests.

You can also use gitter (https://gitter.im/tensorpack/users) for more casual discussions.
Could it be due to the update ops assume there exist next layer holding next state?
Thanks.

The code was only written for two layers. Now it should work for one layer as well.

That was fast.
Thank you!
By the way, any recommendation or guide on how to use tfdbg to 'trace' value of gradients flow.
Currently I am porting code from bit-rnn (quantized RNN, He et al)to tensorpack

callbacks=[
            HookToCallback(tf_debug.LocalCLIDebugHook()), ...

Thanks again


Update pspnet.py

Corrected decoder layer names.

I am using the pspnet from your library. While running the code I found one bug.
In encoder and decoder layers of pspnet, the pytorch throws error for wrong type of in_channels and n_filers variables. Since they are divided by feature scales they are of float type instead of int.
I have fixed the issue by correcting the type of these variables in conv2DBatchNorm/Relu functions.
Moreover I have changed the order of the inputs of the conv2DBatchNorm/Relu functions. to match the convention of pytorch. The order is (in_channels, n_filters, k_size, padding, stride, bias).
I changed linknet and pspnet files to reflect these changes.
Addition to these changes, I have also added deconv2DBatchNorm/Relu functions in utils.py and used them in linknetUp function to make it consistent with your code style.
Let me know if you find any problems in this patch. Looking forward to hear your suggestions.


Enable fp8 inference for Llava-hf 7B and 13B in 1.16 release

What does this PR do?

Reference link GS-119
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?

@Luca-Calabria , one more: please add the command examples to README. thanks

please also test llava-13b for both bf16/fp8 and add the tests to CI

@mandy-li  Done

@Luca-Calabria , one more: please add the command examples to README. thanks

Done

@Luca-Calabria , LGTM. Did you run make style to check code format?

@Luca-Calabria , LGTM. Did you run make style to check code format?

I do it now

@mandy-li I did "make style" commit

LGTM. @regisss , can you review pls? also i don't see any reasons why the unit tests fail.

LGTM. @regisss , can you review pls? also i don't see any reasons why the unit tests fail.

Unit tests fail because I have to actually trigger them for people who are not collaborators of this repo.
@Luca-Calabria I tried the measure command in the README with SynapseAI v1.15.1 and got this error:
AttributeError: 'PatchedKVCache' object has no attribute 'quant_input_0'

It's supposed to work with v1.16 I guess?

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

LGTM. @regisss , can you review pls? also i don't see any reasons why the unit tests fail.

Unit tests fail because I have to actually trigger them for people who are not collaborators of this repo.
@Luca-Calabria I tried the measure command in the README with SynapseAI v1.15.1 and got this error:
AttributeError: 'PatchedKVCache' object has no attribute 'quant_input_0'

It's supposed to work with v1.16 I guess?

@regisss exactly, you must test it on version 1.16


Better repository

I added issue templates, and an examples dir, so it's easier to navigate and open issues!

It's all good except for examples, it looks like a repeat of what we already have -- tests

mm-hm

Have you moved the tests to examples? Would that not nullify the tests which run the programs in there?

A lot of languages repos have examples, so I thought to add it here, and to answer your criticism winter, the hello-world is one I also see, but you can edit it to be a more advanced hello world

IK, but you can take out any example, add any example, and add a readme.md to the dir, with a disclaimer and whatnot.

@darkdarcool You don't understand. You've broken the tests.

I didn’t edit the code, and you can put som of the examples back, I can do it later

@cursorweb You deleted the test programs directory, please just put them back

Oh yeah they are in the tests folder


Dont commit on consumer seek

This changes the behavior of consumer.seek so that when the consumer is running with autoCommit: false, the offsets that are seeked to are not committed. Instead, the previous offset is just resolved.
I opted for using autoCommit instead of an explicit flag in consumer.seek because I figured if you are using autoCommit: false it's because you don't want to us to commit offsets for you. I'm open to feedback on this, as I first did implement the flag, which wasn't any harder, it just seemed more elegant with less chances of accidental offset commits this way.
It's late and I'm very sleepy, so I'm not sure yet if I did this properly.  One thing I know I need to check is: do we actually change the resolved offset if we seek to an offset that is lower than the previously resolved one? If not, I need to special case this and "force" the resolved offset to change.
Fixes #395

I think this change is good and fixes what amounts to a bug in the current behaviour.  But the consumer.seek() behaviour is still rather awkward when autoCommit=true.  E.g. the synchronous consumer.seek() call can succeed without throwing an error but the actual commit may still fail later in the fetch loop.  It also silently just ignores partitions that aren't assigned to this member.
Now that consumer.commitOffset() exists, maybe take the opportunity to clean up the api, either:

introduce a new seekTo() function that never commits and mark the current one as deprecated
just break the current behaviour more and never commit the new offset in seek()

I think this change is good and fixes what amounts to a bug in the current behaviour.  But the consumer.seek() behaviour is still rather awkward when autoCommit=true.  E.g. the synchronous consumer.seek() call can succeed without throwing an error but the actual commit may still fail later in the fetch loop.  It also silently just ignores partitions that aren't assigned to this member.
Now that consumer.commitOffset() exists, maybe take the opportunity to clean up the api, either:

introduce a new seekTo() function that never commits and mark the current one as deprecated
just break the current behaviour more and never commit the new offset in seek()

It also silently just ignores partitions that aren't assigned to this member.

That is actually intentional, albeit as a side-effect of the way seek was implemented. If you are not assigned the partition, you cannot commit offsets for it, and as a developer it's not that easy to keep track of what partitions you are assigned (and why should you, when we already know it?), so the easiest thing for the user would be to just provide all the partition-offsets they want to seek to, and we make sure that we seek on all the assigned partitions.

But the consumer.seek() behaviour is still rather awkward when autoCommit=true. E.g. the synchronous consumer.seek() call can succeed without throwing an error but the actual commit may still fail later in the fetch loop.

This I very much agree with though.  Out of you suggestions, I'm leaning more towards:

introduce a new seekTo() function that never commits and mark the current one as deprecated

And then changing seek's default behavior in a future version (#1013)

It also silently just ignores partitions that aren't assigned to this member.

That is actually intentional, albeit as a side-effect of the way seek was implemented. If you are not assigned the partition, you cannot commit offsets for it, and as a developer it's not that easy to keep track of what partitions you are assigned (and why should you, when we already know it?), so the easiest thing for the user would be to just provide all the partition-offsets they want to seek to, and we make sure that we seek on all the assigned partitions.

But the consumer.seek() behaviour is still rather awkward when autoCommit=true. E.g. the synchronous consumer.seek() call can succeed without throwing an error but the actual commit may still fail later in the fetch loop.

This I very much agree with though.  Out of you suggestions, I'm leaning more towards:

introduce a new seekTo() function that never commits and mark the current one as deprecated

And then changing seek's default behavior in a future version (#1013)

When I read the name autoCommit for the setting I would assume it works as some kind of master switch, i.e. the other two autoCommit-y settings would not ever be looked at when autoCommit is false. I think that that isn't true, and the ...IfNecessary functions do consider these values.
(Just a note to consider, please disregard if I missed something somewhere)

When I read the name autoCommit for the setting I would assume it works as some kind of master switch, i.e. the other two autoCommit-y settings would not ever be looked at when autoCommit is false. I think that that isn't true, and the ...IfNecessary functions do consider these values.
(Just a note to consider, please disregard if I missed something somewhere)

When I read the name autoCommit for the setting I would assume it works as some kind of master switch, i.e. the other two autoCommit-y settings would not ever be looked at when autoCommit is false. I think that that isn't true, and the ...IfNecessary functions do consider these values.
(Just a note to consider, please disregard if I missed something somewhere)

I agree. I had the exact same thought when I was looking at the function, but I decided to keep it out of my mind for the time being as to not bloat the scope. I was thinking that maybe the two thresholds were only set if autoCommit was true, but I didn't look to see if that was actually the case. Good thing to follow up on.

When I read the name autoCommit for the setting I would assume it works as some kind of master switch, i.e. the other two autoCommit-y settings would not ever be looked at when autoCommit is false. I think that that isn't true, and the ...IfNecessary functions do consider these values.
(Just a note to consider, please disregard if I missed something somewhere)

I agree. I had the exact same thought when I was looking at the function, but I decided to keep it out of my mind for the time being as to not bloat the scope. I was thinking that maybe the two thresholds were only set if autoCommit was true, but I didn't look to see if that was actually the case. Good thing to follow up on.

Now I've had a nights sleep (and a days work), and the implementation still looks okay to me. I've verified that resolving a lower offset than an already resolved offset allows you to seek backwards, so it all seems fine.
As soon as @JaapRood or @ankon has had a chance to review and hopefully ✅, I'll go ahead and merge.

Now I've had a nights sleep (and a days work), and the implementation still looks okay to me. I've verified that resolving a lower offset than an already resolved offset allows you to seek backwards, so it all seems fine.
As soon as @JaapRood or @ankon has had a chance to review and hopefully ✅, I'll go ahead and merge.