/usr/bin/python: bad interpreter: No such file or directory

there's a bug in the latest 2.7 version of the container

docker pull python:2.7
docker run -it --rm python:2.7 bash -c 'apt-get update && apt-get install -y supervisor && supervisord —help'
...
...
Processing triggers for systemd (215-17+deb8u4) ...
bash: /usr/bin/supervisord: /usr/bin/python: bad interpreter: No such file or directory

I think this issue is related with https://github.com/docker-library/python/pull/131

This is also affecting us, supervisor from the debian packages stopped working.

This is also a problem for the lsb-release package:
$ docker run -it --rm python:3.5 /bin/bash
root@403420f42ad8:/# apt-get update
Get:1 http://security.debian.org jessie/updates InRelease [63.1 kB]
Ign http://httpredir.debian.org jessie InRelease
Get:2 http://security.debian.org jessie/updates/main amd64 Packages [373 kB]
Get:3 http://httpredir.debian.org jessie-updates InRelease [142 kB]
Get:4 http://httpredir.debian.org jessie Release.gpg [2373 B]
Get:5 http://httpredir.debian.org jessie-updates/main amd64 Packages [17.6 kB]
Get:6 http://httpredir.debian.org jessie Release [148 kB]
Get:7 http://httpredir.debian.org jessie/main amd64 Packages [9032 kB]
Fetched 9778 kB in 1min 42s (95.6 kB/s)
Reading package lists... Done
root@403420f42ad8:/#
root@403420f42ad8:/#
root@403420f42ad8:/# apt-get install -y lsb-release
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
  lsb
The following NEW packages will be installed:
  lsb-release
0 upgraded, 1 newly installed, 0 to remove and 4 not upgraded.
Need to get 26.5 kB of archives.
After this operation, 99.3 kB of additional disk space will be used.
Get:1 http://httpredir.debian.org/debian/ jessie/main lsb-release all 4.1+Debian13+nmu1 [26.5 kB]
Fetched 26.5 kB in 1s (22.7 kB/s)
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package lsb-release.
(Reading database ... 21490 files and directories currently installed.)
Preparing to unpack .../lsb-release_4.1+Debian13+nmu1_all.deb ...
Unpacking lsb-release (4.1+Debian13+nmu1) ...
Setting up lsb-release (4.1+Debian13+nmu1) ...
root@403420f42ad8:/#
root@403420f42ad8:/#
root@403420f42ad8:/#
root@403420f42ad8:/# lsb_release
bash: /usr/bin/lsb_release: /usr/bin/python: bad interpreter: No such file or directory

I'm facing this when running node installer scripts from nodesource/distributions repo which use lsb_release to identify the O.S. version.
setup_6.x: /usr/bin/lsb_release: /usr/bin/python: bad interpreter: No such file or directory

I'm seeing the exact same issue as @pitervergara. I believe this was introduced in a819c92949e182901df10e52d41bc57c6ca73bd5 when this was replaced:
RUN apt-get purge -y python.*

I believe that command would have left /usr/bin/python in place, but when it effectively replaced with dpkg-divert --rename /usr/bin/py* that scooped up /usr/bin/python which used to be untouched.
I don't have any background on the reasoning behind that change so I don't feel confident suggesting what the "correct" behavior is.
Unrelated to the python issue, for @pitervergara's I suggest just replacing the call to the nodesource installation script with the Nodesource manual installation instructions instructions in your Dockerfile.

Thanks for the tip, @jalessio !
About node, I did exactly that to make my build run again.
I agree that the issue arrived with that change, because now the files are named "*.distrib", which seems to be the intention of that commit, but the lsb_release and perhaps some other utilities are expecting to find a python executable at /usr/bin/python.
root@b3742b74c10d:/# ls -l /usr/bin/py*
...
lrwxrwxrwx 1 root root       9 Mar 16  2015 /usr/bin/python.distrib -> python2.7
-rwxr-xr-x 1 root root 3785928 Mar  1  2015 /usr/bin/python2.7.distrib
lrwxrwxrwx 1 root root       9 Mar 16  2015 /usr/bin/python2.distrib -> python2.7
...

root@b3742b74c10d:/# head /usr/bin/lsb_release
#! /usr/bin/python -Es

# lsb_release command for Debian
# (C) 2005-10 Chris Lawrence<EMAIL_ADDRESS>
...

One solution is probably just to symlink the Python that is built in this image from source to the location that things expect the Debian version to be:
RUN ln -s /usr/local/bin/python /usr/bin/python

Things like the Debian-packaged supervisor were working before because apt would just reinstall Python after it was purged as a dependency of the supervisor package. This effectively resulted in 2 Pythons being installed (3 Pythons if you include the Python in the lower layers that is purged).

@JayH5, at least for the lsb_release package, synlinking the python interpreter won't work because of the PYTHONPATH.
The python version at /usr/bin/python is the 3.5 compiled into the image, and the debian original /usr/bin/python is a 2.7, whith different lib folder.
To use symlink, we have to point it to the "diverted" one.
root@fb96f95a04d5:/# lsb_release -a
bash: /usr/bin/lsb_release: /usr/bin/python: bad interpreter: No such file or directory
root@fb96f95a04d5:/#
root@fb96f95a04d5:/#
root@fb96f95a04d5:/# ln -s /usr/local/bin/python /usr/bin/python
root@fb96f95a04d5:/#
root@fb96f95a04d5:/# lsb_release -a
Traceback (most recent call last):
  File "/usr/bin/lsb_release", line 28, in <module>
    import lsb_release
ImportError: No module named 'lsb_release'
root@fb96f95a04d5:/#
root@fb96f95a04d5:/#
root@fb96f95a04d5:/# unlink /usr/bin/python
root@fb96f95a04d5:/# ln -s /usr/bin/python2.7.distrib /usr/bin/python
root@fb96f95a04d5:/#
root@fb96f95a04d5:/# lsb_release -a
No LSB modules are available.
Distributor ID:	Debian
Description:	Debian GNU/Linux 8.5 (jessie)
Release:	8.5
Codename:	jessie
root@fb96f95a04d5:/#

Also, note that it must be the "/usr/bin/python2.7.distrib" because "/usr/bin/python.distrib" and "/usr/bin/python2.distrib" both are symlinks to a missing file (the original interpreter name, before dpkg-divert)

Supervisor issues for us to running 2.7.12.  Has there been any update on this?

I had used home-brew to install 2.7 on Ubuntu and the new install was missing the sym links. I ran
brew link --overwrite python

Simply run this
sudo bash -c "test -e /usr/bin/python || (apt -qqy update && apt install -qy python-minimal)
Then run command "katoolin"


use Ostruct#marshal_dump instead of #to_h to support Ruby 1.9.3

grape-swagger-rails currently breaks on Ruby < 2.0 cause it relies on OpenStruct#to_h, which is new. OpenStruct#marshal_dump is equivalent and is backwards compatible
Also consider adding v1.9.3 to the Travis matrix?

If we're going to reintroduce 1.9.3 compatibility, please add it to .travis.yml.

@dblock Added 1.9.3 to .travis.yml and linked to another PR which shows failures on 1.9.3 without this fix

Merged


chore(main): release 1.1.6

:robot: I have created a release beep boop
1.1.6 (2023-01-20)
update

添加路由守卫 (1e01b36)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/School-of-Website-Engineering/Knock-Ding-Yanxuan/releases/tag/v1.1.6 :sunflower:


MDNS: Additional records from query

Hi,
Is it only possible to readout additional records when the received packet is a response ? mdns_flags = 0x8000. I can't find anything in rfc that says query can't contain additional records so is this intentionally?
https://github.com/azure-rtos/netxduo/blob/72dcde94184b9996894c4be3b4a5cafb2b448100/addons/mdns/nxd_mdns.c#L7920-L7926
BR

Hi @casperjuul Sorry for the late response. In RFC6762, Section18.14, query message may contain Known Answers in the Answer Section, but there is no other info that mentions query can contain additional records. In RFC6763 Section 12, server/responder should include additional records in response, it is also not for query. Did you encounter any issue for query?

Closing, feel free to create new one if you have further issue.


DB Light...

why all addresses in the Light database start with 1

https://en.bitcoin.it/wiki/Invoice_address
We can only generate P2PKH addresses. All these starts with one.


ci: run tests on windows

These changes have been rolled into https://github.com/MystenLabs/sui/pull/2713


Unexpected token END OF FILE at position 0

Describe the bug
It says end of file and may sometimes even say no space left on device.
To Reproduce
Startup the Server
Screenshots
[18:24:43 INFO]: [BeaconWaypoints] Enabling BeaconWaypoints v1.6.3
[18:24:43 INFO]: [BeaconWaypoints] Loading module for version 1_20_R1
[18:24:43 WARN]: Unexpected token END OF FILE at position 0.
[18:24:43 WARN]:        at org.json.simple.parser.JSONParser.parse(JSONParser.java:257)
[18:24:43 WARN]:        at org.json.simple.parser.JSONParser.parse(JSONParser.java:92)
[18:24:43 WARN]:        at BeaconWaypoints-1.6.3.jar//com.github.dawsonvilamaa.beaconwaypoint.Main.loadData(Main.java:151)
[18:24:43 WARN]:        at BeaconWaypoints-1.6.3.jar//com.github.dawsonvilamaa.beaconwaypoint.Main.onEnable(Main.java:103)
[18:24:43 WARN]:        at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:281)
[18:24:43 WARN]:        at io.papermc.paper.plugin.manager.PaperPluginInstanceManager.enablePlugin(PaperPluginInstanceManager.java:189)
[18:24:43 WARN]:        at io.papermc.paper.plugin.manager.PaperPluginManagerImpl.enablePlugin(PaperPluginManagerImpl.java:104)
[18:24:43 WARN]:        at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:507)
[18:24:43 WARN]:        at org.bukkit.craftbukkit.v1_20_R1.CraftServer.enablePlugin(CraftServer.java:562)
[18:24:43 WARN]:        at org.bukkit.craftbukkit.v1_20_R1.CraftServer.enablePlugins(CraftServer.java:473)
[18:24:43 WARN]:        at net.minecraft.server.MinecraftServer.loadWorld0(MinecraftServer.java:636)
[18:24:43 WARN]:        at net.minecraft.server.MinecraftServer.loadLevel(MinecraftServer.java:435)
[18:24:43 WARN]:        at net.minecraft.server.dedicated.DedicatedServer.e(DedicatedServer.java:308)
[18:24:43 WARN]:        at net.minecraft.server.MinecraftServer.w(MinecraftServer.java:1101)
[18:24:43 WARN]:        at net.minecraft.server.MinecraftServer.lambda$spin$0(MinecraftServer.java:318)
[18:24:43 WARN]:        at java.base/java.lang.Thread.run(Thread.java:833)
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Are any of the player files in plugins/BeaconWaypoints/players empty? There might be an issue when it's writing player data to the files, possibly because of there not being enough storage space to save to. Also, could you check if there are any errors when it's trying to save? That would be when the server shuts down, the plugin is reloaded, or every 5 minutes when it autosaves.

I still have alot of storage space, there don't seem to be any issues with saving i think cause there were no messages that indicated anything wrong however it didn't mention saving either so idk.


problem loading Coco models

when I try to load a Res101 model trained on Coco, I get this error:
RuntimeError: While copying the parameter named RCNN_rpn.RPN_cls_score.weight, whose dimensions in the model are torch.Size([18, 512, 1, 1]) and whose dimensions in the checkpoint are torch.Size([24, 512, 1, 1]).

I trianing  vgg16 on coco ,  but when I load the modle in test_net.py , I met the same error , and I tried your method, but it do not work.  could you help me？

well, there is no vgg16_ls.yml file in cfgs folder. you could create one by comparing res101.yml and res101_ls.yml or you could check test_net.py to see how it's done in case "--ls" command is specified for large scale.


flexmeasures entsoe import-day-ahead-generation

A CLI command for getting tomorrow's info ENTSO-E has about generation, with the goal to estimate CO2 content.

At least the roundtrip works now. Some topics for eventual immediate attention:

Any validation we could add in place (for preventing bad surprises)?
Change / adapt the source data (see extensive discussion in this PR). Document the shortcomings or issues to be evaluated.

I suggest we merge this PR now (unless you find other issues to fix, of course) and make those things above into new issues, to be worked on next.


AUR: build is broken

I'm getting this when trying to update hyprland-git from the AUR
cmake --build ./build --config Release --target all -j12
ninja: error: '/home/x/.cache/yay/hyprland-git/src/hyprland/subprojects/udis86/build/libudis86/liblibudis86.a', needed by 'Hyprland', missing and no known rule to make it

Yeah I too am getting the same error since today.
cmake --build ./build --config Release --target all -j16
ninja: error: '/home/justine/.cache/paru/clone/hyprland-git/src/hyprland/subprojects/udis86/build/libudis86/liblibudis86.a', needed by 'Hyprland', missing and no known rule to make it
make: *** [Makefile:144: release] Error 1

Everybody seems to have more than 10 cores these days, i'm still seeing -j4

Atleast it aint a Intel(R) Core(TM) i3-3110M CPU @ 2.40GHz, idk why i still have this relic

@ThatOneCalculator offering help as a contributor to the aur repo. ping me on discord if you want help.

T1C is not the owner of the aur -git pkg. @sandervankasteel  is.

I am aware that the AUR package isn't building. I hope to checkout it tonight (CEST) and get  it resolved. :relaxed:

@WasteOfO2

Atleast it aint a Intel(R) Core(TM) i3-3110M CPU @ 2.40GHz, idk why i still have this relic

Because as you are already wasting O2 you don't want to produce too much CO2?
Fun fact: it's Intel(R) Core(TM) i3-2310M CPU @ 2.10GHz  on my site!

@WasteOfO2

Atleast it aint a Intel(R) Core(TM) i3-3110M CPU @ 2.40GHz, idk why i still have this relic

Because as you are already wasting O2 you don't want to produce too much CO2?
Fun fact: it's Intel(R) Core(TM) i3-2310M CPU @ 2.10GHz on my side!

why can't all of this be part of one makefile target?

it is... it's make all.

First of all, personal life stuff got in the way. Secondly, I refused to be called and treated like this. I've just disowned the package. Whoever wants to take over the responsibility for it, he or she can have it.
I'm out.

I've disowned the package on the AUR.

Thanks! :)

@vaxerski If you want I can own it for now.

I'd rather Kainoa owned it (just like all hyprland packages) He is now the maintainer. (Was co-) but still for some reason can't add me as a co-.
I usually update -bin and hyprland for updates, and I would do the same to -git if I had the perms.

This adapts the approach taken by the PKGBUILD for make all. If it conflicts with something else, this could be an dedicated target. It would be nice not to have keep two separate build scripts in sync.
  diff --git a/Makefile b/Makefile
  index 0bef0dc..0b53170 100644
  --- a/Makefile
  +++ b/Makefile
  @@ -1,5 +1,7 @@
   include config.mk

  +ROOT_DIR := $(shell dirname $(realpath $(firstword $(MAKEFILE_LIST))))
  +
   CFLAGS += -I. -DWLR_USE_UNSTABLE -std=c99

   WAYLAND_PROTOCOLS=$(shell pkg-config --variable=pkgdatadir wayland-protocols)
  @@ -156,7 +158,12 @@ clear:
   all:
    make clear
    make fixwlr
  - cd ./subprojects/wlroots && meson build/ --buildtype=release && ninja -C build/ && cp ./build/libwlroots.so.12032 /usr/lib/ && cd ../..
  + cd "./subprojects/wlroots/" \
  +   && meson build/ --prefix="$(ROOT_DIR)/tmpwlr" --buildtype=release \
  +   && ninja -C build/ \
  +   && echo mkdir -p "$(ROOT_DIR)/tmpwlr" \
  +   && ninja -C build/ install \
  +   && cd ../
    cd subprojects/udis86 && cmake --no-warn-unused-cli -DCMAKE_BUILD_TYPE:STRING=Release -H./ -B./build -G Ninja && cmake --build ./build --config Release --t  arget all -j$(shell nproc)
    make protocols
    make release

I'd rather Kainoa owned it...

Well I tried... hahaha, I though that would be my first contribution to the AUR (I even created an account for that), I suppose that maybe I will calm down my urges with another project this weekend, either way I fixed the error with @Dickby's workaround. Thanks 👍🏻

PSA: The -git package got broken another time (wlroots dep update) and now it has a hard depend on libdisplay-info (AUR) and libliftoff.

PKGBUILD needs no change to build, but you need those two.
Even with these two packages installed, it won't compile

sudo pacman -Qk libliftoff libdisplay-info
libliftoff: 16 total files, 0 missing files
libdisplay-info: 18 total files, 0 missing files

cmake --build ./build --config Release --target all -j16
ninja: error: '/home/haru02w/.cache/yay/hyprland-git/src/hyprland/subprojects/udis86/build/libudis86/liblibudis86.a', needed by 'Hyprland', missing and no known rule to make it
make: *** [Makefile:144: release] Error 1

PKGBUILD needs no change to build, but you need those two.

Even with these two packages installed, it won't compile
sudo pacman -Qk libliftoff libdisplay-info
libliftoff: 16 total files, 0 missing files
libdisplay-info: 18 total files, 0 missing files

cmake --build ./build --config Release --target all -j16
ninja: error: '/home/haru02w/.cache/yay/hyprland-git/src/hyprland/subprojects/udis86/build/libudis86/liblibudis86.a', needed by 'Hyprland', missing and no known rule to make it
make: *** [Makefile:144: release] Error 1

It builds just fine for me with those two installed and changing the PKGBUILD using this:
build() {
	cd "${srcdir}/${_pkgname}"
	git submodule update --init
	make fixwlr
	cd "./subprojects/wlroots/" && meson build/ --prefix="${srcdir}/tmpwlr" --buildtype=release && ninja -C build/ && mkdir -p "${srcdir}/tmpwlr" && ninja -C build/ install && cd ../
	cd udis86 && cmake --no-warn-unused-cli -DCMAKE_BUILD_TYPE:STRING=Release -H./ -B./build -G Ninja && cmake --build ./build --config Release --target all -j$(shell nproc) && cd ../..
	make protocols
    make release
	cd ./hyprctl && make all && cd ..
}

As I'm now back from vacation and finally have access to my keys, the fix has been pushed

This bug is relevant for me on hyprland aur package (not hyprland-git)

Facing the same issue on non-git hyprland on fresh archinstalled system atm

fixed

@vaxerski Could you also bump pkgrel in https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=hyprland as you did for the .SRCINFO please?
Bumping pkgrel on the latter while not doing on the former means that AUR helpers are seeing a -2 revision available, but are still building a -1 if user don't manually edit the PKGBUILD, resulting in the AUR helper wanting to update hyprland on every run.
Also, I randomly bumped into https://github.com/hyprwm/aur which seemed to be a good idea considering there's no way for non-maintainers to submit patches on AUR, but I guess it was too painful to maintain this on different places at the same time?

my bad fixed


#350 Add Slf4j logging implementation

Love the idea, thanks @jarrodcodes

I don't believe this test failure is related to my changes? Anything I need to change?

Some flaky test, will fix it later


Doc example showing root level definitions?

Would it be possible to provide documentation as how one would use root-level definitions?  In the current examples the definitions are implemented per path or operation object.
I'd like to keep my definitions similar to the Petstore example, at the root level of the spec so they can be referenced by multiple paths/operation objects.  Is that possible with flask-swagger?
Thanks!

Yes you can simply follow the swagger spec eg.
type: array
items:
   $ref: "#/definitions/Event"

Where Event is a definition that was defined elsewhere (any other response/parameter via schema)


Change of maintainer

Closes #11

Hello @rubenspgcavalcante, looks like no one merged this PR. Doing it now.

Thanks @LappleApple :)


Wip/service worker

It's been a while. Let's see if we can add a service worker to complete the PWA requirement. I'll quickly deploy these changes to see if they still affect the other GH sites. If it doesn't work, we roll back to the main branch.

The service workers are still having that issue. But we can fix this by excluding external GH pages from being cached. The best way is to either only cache sites with a hash or sites with an empty pathname, depends how the rest of the static content behaves.
I was originally thinking about parsing projects.json to exclude some of the project URLs, but that won't account for the other sites not included in the portfolio and could affect the sites currently listed if they have separate service workers.


Update AppCode to version 3.1.3

This commit updates the version number to 3.1.3 and the SHA.

Thanks @mauricerkelly


rest_client.get_timeseries() return

RestClient.get_timeseries() method returns an object of type DeferredResultResponseEntity which always has following properties:
{
    'result': None,
    'set_or_expired': None
}

I have tried the same requests to same urls and same parameters using plain python requests library and I get  correct results (actual timeseries data I have  saved in thingsboard), so I dont know why the result property is None when I use  get_timeseries() method. What is the correct way of extracting  the result from  DeferredResultResponseEntity object?

Hi @jaimef1603 ,
You can try to use the code like following, just replace some values:

import logging
# Importing models and REST client class from Professional Edition version
from tb_rest_client.rest_client_pe import *
from time import time
from tb_rest_client.rest import ApiException
logging.basicConfig(level=logging.DEBUG,
                    format='%(asctime)s - %(levelname)s - %(module)s - %(lineno)d - %(message)s',
                    datefmt='%Y-%m-%d %H:%M:%S')
# ThingsBoard REST API URL
url = "http://localhost:8080"
# Default Tenant Administrator credentials
username =<EMAIL_ADDRESS>password = "tenant"
# Creating the REST client object with context manager to get auto token refresh
def main():
    with RestClientPE(base_url=url) as rest_client:
        try:
            # Auth with credentials
            rest_client.login(username=username, password=password)
            entity_id = EntityId("DEVICE", "b8a718c0-d550-11ea-9c98-a75a5432dc3b")
            end_ts = int(time()*1000)
            x = rest_client.get_timeseries(entity_id, 'humidity', use_strict_data_types=False, start_ts=1, end_ts=end_ts)
            logging.info(x)
        except ApiException as e:
            logging.exception(e)
        except Exception as e:
            logging.exception(e)
if __name__ == '__main__':
    main()

@imbeacon  , I am also getting result as None but for the entity I am using Tenent eg: entity_id = EntityId('43674850-11111-11eb-b40e-4f4f7lik8459', 'TENANT')
do you know if its possible to get historical time-series data from all devices  for particular tenant, or particular customers?


Question about over-parameterization

Dear Liu,
Thanks for your contributions. I have a question about the code. I note that in line 64 in train.py, the "reparameterization_net" is set to "None". I wonder if that is the right way to reproduce the over-parameterization results in your paper? Since it seems that over-parameterization has been implemented in "overparametrization_loss" in model/loss.py.  Do I understand correctly?
Best

Thanks very much!


no-switch-case-fall-through false positive when using curly braces

When a case block is enclosed in curly braces, no-switch-case-fall-through mistakenly reports an error.
Example:
  case JobState.DependencyWait:
    {
      this.m_Description = 'Waiting for Dependencies.';
      break;
    }

  case JobState.Held:

This should be a slightly easier issue to fix than Issue #950

Because the TypeScript compiler recently introduced a --noFallthroughCasesInSwitch flag this rule will most likely soon be deprecated.

Ah, and in fact, this is a duplicate of #785. Thanks for the bug report though @isaacplmann, let us know if you encounter any others!


There was an error in the script when replacing zh_CN.res

How can I send you a wrong page image

I have found it. thanks

We have this function already implemented.. is there a problem?

我们已经实现了这个功能..有问题吗？

我如何向您发送错误的页面图像

我如何向您发送错误的页面图像

如果它真的是一个错误，下次把它附在这里 :)


deployed list replication issues

Users are reporting on the live product that the list will sometimes clear or update incorrectly when new people join the room. Still trying to identify why this is the case. This doesn't appear to happen when I only visit from one ip address.

This service no longer exists. Maybe it's something that will come up with new development


Force 2 decimals with any price / Fix deductFee function

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Bugfix

What is the current behavior? (You can also link to an open issue here)

GDAX: price trim to 8 decimals
GDAX: amount after deductFee() is more than 8 decimals

What is the new behavior (if this is a feature change)?

GDAX: price always trims to 2 decimals
GDAX: amount after deductFee() is always 8 decimals or less

Other information:
Quick bugfix, should be tested with actual scenario. Currently running on ETH-EUR but I won't have time to be behind a computer the next couple of days.

This deductFee function will return another function, so it would set the size prop to a function and not the result:
https://github.com/damianleung/gekko/blob/b7f1662a13f18835d03b648ea0e7af138bec3a5f/exchanges/gdax.js#L116
Though first: what bug is this supposed to fix? I am testing GDAX now and I think it's pretty stable.

Removed deductFee(), it should work without it

My experience with GDAX is limited but I thought:

you can specify amount up to 8 decimals.
you can specify price up to 2 decimals (or 5 for crypto markets).

We know the price can't be 8 from the error in #992 (8 decimals were specified but still an error). Looking at the orderbook (here for USD and here for LTC I see amounts specified in 5 and 2 decmials.

@askmike ok I see, I'll change it to 5 decimas then. I only see BTC as currency on this table https://www.gdax.com/fees/BTC-USD so the currency check is only on BTC.

@damianleung thanks a lot for bearing with me! I'll merge this right now in the hope it fixes #992. I'll merge manually to remove some of the commits.

Merged in these commits:

https://github.com/askmike/gekko/commit/0e8f2b10115eb70fb56aca338f96a388504963ac
https://github.com/askmike/gekko/commit/d2bf48eb947dcede4e1af1260a8ba1d2dfc48f2b

Thanks :)


Everything's busted :/

Godot: 3.2 stable
Plugin: 0.8.0
Nothing happens when I press that exclamation mark in the sign in area. In fact, none of the buttons seem to do anything either.
Also the console printed following errors.
res://addons/github-integration/scripts/SignIn.gd:36 - Parse Error: The identifier "UserData" isn't declared in the current scope.
modules/gdscript/gdscript.cpp:576 - Method failed. Returning: ERR_PARSE_ERROR
res://addons/github-integration/scripts/UserPanel.gd:41 - Parse Error: The identifier "UserData" isn't declared in the current scope.
modules/gdscript/gdscript.cpp:576 - Method failed. Returning: ERR_PARSE_ERROR
res://addons/github-integration/scripts/Repo.gd:107 - Parse Error: The identifier "IconLoaderGithub" isn't declared in the current scope.
modules/gdscript/gdscript.cpp:576 - Method failed. Returning: ERR_PARSE_ERROR
res://addons/github-integration/scripts/Commit.gd:209 - Parse Error: The identifier "UserData" isn't declared in the current scope.
modules/gdscript/gdscript.cpp:576 - Method failed. Returning: ERR_PARSE_ERROR
res://addons/github-integration/scripts/WindowDialog.gd:99 - Parse Error: The identifier "UserData" isn't declared in the current scope.
modules/gdscript/gdscript.cpp:576 - Method failed. Returning: ERR_PARSE_ERROR
res://addons/github-integration/scripts/Gist.gd:66 - Parse Error: The identifier "IconLoaderGithub" isn't declared in the current scope.
modules/gdscript/gdscript.cpp:576 - Method failed. Returning: ERR_PARSE_ERROR
Failed to get modified time for: C:/Users/Student/Documents/Godot Projects/Code Cube/addons/file-editor/fonts/Roboto-Black.ttf.
Cannot open font file 'res://addons/file-editor/fonts/Roboto-Black.ttf'.

Okay, so I tried it today, but it's saying Error: Bad credentials. I triple checked the username and password, and have also tried signing in with those same settings here on GitHub.

You need to access with username and token , as specified in Field's labels
. You can create a token with the button under the token field.
Il sab 1 feb 2020, 21:17 Roujel Williams<EMAIL_ADDRESS>ha
scritto:

Okay, so I tried it today, but it's saying Error: Bad credentials. I
triple checked the username and password, and have also tried signing in
with those same settings here on GitHub.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/fenix-hub/godot-engine.github-integration/issues/34?email_source=notifications&email_token=AKZMSZH4VUPCXX23UTWKR5TRAXKHHA5CNFSM4KN56IB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKRFWQQ#issuecomment-581065538,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKZMSZHER5UEVSXM4QVCI5DRAXKHHANCNFSM4KN56IBQ
.

Okay. It's working now.

Perfect, I'll close the issue then.
Thank you very much for your feedback, if you find any bug don't hesitate
to open a new issue.
Il sab 1 feb 2020, 21:47 Roujel Williams<EMAIL_ADDRESS>ha
scritto:

Okay. It's working now.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/fenix-hub/godot-engine.github-integration/issues/34?email_source=notifications&email_token=AKZMSZDYKEGFP7PCDJNT5ADRAXNWJA5CNFSM4KN56IB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKRGIIY#issuecomment-581067811,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKZMSZE2XMU7KFPB24NGP3TRAXNWJANCNFSM4KN56IBQ
.


updated expected results file for MD-2905 min_max_dir test failure

@prasadns14 Can you please review and merge this test ?
This one takes care of the min_max_dir test failure in drill-3474_5 tests (MD-2905)

LGTM +1

@kfaraaz can you create the PR to 1.11.0-mapr branch?


Update gat4k docker image

gat4k latest tag is currently pointed to <IP_ADDRESS>, and the exact same failure is occurring. I updated #6 with the exact content of RNAseq/<workflow-id>/call-BaseRecalibrator/execution/stderr

@BMurri try now

@MattMcL4475 04d51dd runs successfully


Remove legacy code

Removes:

goBack
stopInFront
separate case for not using VFH*

yes, I didn't notice any difference with respect to master

successful flight tests, no regression


Timeout keyword ignored in pyodbc.connect()

Hi all,
This is linked to an old closed issue but I wanted to re-raise.
Simply if a connection cannot be made to a DB, for example a firewall is blocking the attempt my script will just hang forever. I've looked around at the docs and stack overflow and a lot of people seem to be reporting the keyword doesn't work / is ignored.
For example:
try:
        conn = pyodbc.connect(CONN_STRING,timeout=5)
except:
        print "Connetion to Database timed out"
        sys.exit(1)

The timeout isn't ignored -- it is used to set SQL_ATTR_LOGIN_TIMEOUT.  There is also a SQL_ATTR_CONNECTION_TIMEOUT that could be set, so perhaps I should set it too.
The SQL_ATTR_CONNECTION_TIMEOUT affects all queries, not just connection attempts, so I was trying to keep them separate.  Right now it is only set after connecting when you use cnxn.timeout=4.
I tested setting both before a login with SQL Server on Windows and PostgreSQL on OS X and neither worked.  This seems to be a bug in the drivers.
I'm going to close this, but if you can find any information please reopen.  I'm happy to put a fix in if there is one.

From ODBC API docs on SQL_ATTR_LOGIN_TIMEOUT:

... the number of seconds to wait for a login request to complete before returning to the application.

I don't quite understand why this doesn't timeout for certain connection problems, e.g. firewall block like in @ltoshea s case, or when server sends no response. But it doesn't, and users who have to deal with unreliable connections will sometimes experience indefinite blocks, instead of the expected timeout.
This makes error handling difficult; I see also users struggling with this in #11.
I replaced LOGIN with CONNECTION attribute in this block, which did successfully timeout for me testing with FreeTDS against a server which accepts the TCP connection but never responds.
My suggestion would be to expose both SQL_ATTR_LOGIN_TIMEOUT and SQL_ATTR_CONNECTION_TIMEOUT attributes, perhaps by adding a connection_timeout argument to pyodbc.connect. This way pyodbc doesn't have to make this choice for the user.
Another suggestion might be to also set SQL_ATTR_CONNECTION_TIMEOUT during login, but reset it afterwards, keeping the old behaviour of setting cnxn.timeout=4 so that this doesn't affect queries.
What do you think @mkleehammer ?

Im stuck with this also, any workaround for the moment? Default connection timeout seems to be too high and my entire app hangs cause of this
Thanks

Hi,
What worked for me was getting the latest version of pyodbc from github(not through pip install pyodbc) and using attrs_before dictionary argument for the connect function, just like this:
SQL_ATTR_CONNECTION_TIMEOUT = 113 login_timeout = 1 connection_timeout = 3 connection = pyodbc.connect(connection_string, timeout=login_timeout, attrs_before={SQL_ATTR_CONNECTION_TIMEOUT : connection_timeout})
That 113 can be found in sqlext.h file(my file is in /usr/include/sqlext.h).
Note that by using this dictionary you are able to change many more settings.
If you encounter a problem with "PyInt_AsInt" you can change it to "PyInt_AsLong", like i did here: https://github.com/andreiroman/pyodbc/commit/3a5c1add5515da3a2fd5e178079fd1b42ab81380

Hi andreiroman,
Can you tell me which pyodbc version you have tested "attrs_before". Currently I am using 3.0.7 and your workaround is not working for us.

Hello @piyushiitg,
Version: 3.0.11b16(latest version). You could follow these steps to get it:

uninstall pyodbc
download https://github.com/mkleehammer/pyodbc and extract
navigate to the new folder and do "pip install ./pyodbc"

Hope it helps!

Hi @andreiroman
If I set SQL_ATTR_CONNECTION_TIMEOUT this variable inside below block. Is there any issue. Because after setting this my timeout issue is solved.
if (timeout > 0)
{
Py_BEGIN_ALLOW_THREADS
ret = SQLSetConnectAttr(hdbc, SQL_ATTR_LOGIN_TIMEOUT, (SQLPOINTER)timeout, SQL_IS_UINTEGER);
ret = SQLSetConnectAttr(hdbc, SQL_ATTR_CONNECTION_TIMEOUT, (SQLPOINTER)timeout, SQL_IS_UINTEGER);
Py_END_ALLOW_THREADS
if (!SQL_SUCCEEDED(ret))
RaiseErrorFromHandle("SQLSetConnectAttr(SQL_ATTR_LOGIN_TIMEOUT)", hdbc, SQL_NULL_HANDLE);
}
Thanks
PIyush

Hi @piyushiitg,
There shouldn't be any problem at all for now, but it would be a good idea to keep an eye on this module until the next version is available via pip install and you can use the attrs_before then.

Hung process using pyodbc.
info :
python2.7/site-packages/pyodbc-4.0.22-py2.7-macosx-10.13-intel.egg

before :
pyodbc.connect(cnxn_string, timeout=2)

debug :
sudo bash -c 'source /Users/stuff-intern1/.zshrc && dtruss -a python pystuff/loaders/sql.py'

...

12908/0x7a9cb:     39548       4      1 close_nocancel(0x3)      = 0 0
12908/0x7a9cb:     39591      16     12 socketpair(0x1, 0x1, 0x0)        = 0 0
12908/0x7a9cb:     39650      32     27 socket(0x2, 0x1, 0x0)        = 5 0
12908/0x7a9cb:     39664       8      3 setsockopt(0x5, 0xFFFF, 0x8)         = 0 0
12908/0x7a9cb:     39666       4      0 setsockopt(0x5, 0xFFFF, 0x1022)      = 0 0
12908/0x7a9cb:     39667       3      0 setsockopt(0x5, 0x6, 0x1)        = 0 0
12908/0x7a9cb:     39690       4      1 ioctl(0x5, 0x8004667E, 0x7FFEE561FCA4)       = 0 0
12908/0x7a9cb:     39791      97     93 connect(0x5, 0x7F902F425670, 0x10)       = -1 Err#36

with info from this thread:
    SQL_ATTR_CONNECTION_TIMEOUT = 113
    login_timeout = 1
    connection_timeout = 1
    connection = pyodbc.connect(cnxn_string,
                                timeout=login_timeout,
                                attrs_before={
                                SQL_ATTR_CONNECTION_TIMEOUT: connection_timeout})

After:
python pystuff/loaders/sql.py
('08S01', u'[08S01] [FreeTDS][SQL Server]Unable to connect: Adaptive Server is unavailable or does not exist (20009) (SQLDriverConnect)')

This was through pip install. Looks like the attrs_before stuff works great.
Thanks.

Actually - there's not much information in this thread about what drivers are being used.  Recently I had a patch accepted at FreeTDS which fixes a bug with the SQL_ATTR_LOGIN_TIMEOUT value.  The driver was storing it, but not using it.
So if (1) you're using FreeTDS, and (2) you install the latest 'master', this shouldn't be a problem anymore.

Hi! I have pyodbc 4.0.23, and timeout on LOGIN is not working! Tried to use "attrs_before" - same result(( Is it work only with pyodbc 3.0.11b? The problem is very actual, loses sense of taste great pyodbc! Can anyone help me!

@yevgeniyclaudio  What driver are you using? Please describe your environment in more detail, as explained above it may be the ODBC driver which is not recognising the setting of timeout.

v-chojas, thanks for reply! I have Microsoft Win Server 2003 R2, python 2.7.3 32x, driver SQL Server Native Client 10.0, pyodbc-4.0.23, when impot 4.0.0! Pyodbc built with VCForPython27.msi

Hello,
Has this issue been resolved? I've been using pyodbc on both MySQL and SQL Servers and it appears the timeout attribute on the connect method is always ignored

You can post an ODBC trace for more information.

Im looking forward to the resolution! :)
In the meantime, as an alternative to the SQL_ATTR_CONNECTION_TIMEOUT solution kindly proposed by @allen-munsch and @andreiroman, it is also possible to modify the connection via SQL after you open it
SET statement_timeout = 10000

Im looking forward to the resolution! :)
In the meantime, as an alternative to the SQL_ATTR_CONNECTION_TIMEOUT solution kindly proposed by @allen-munsch and @andreiroman, it is also possible to modify the connection via SQL after you open it
SET statement_timeout = 10000

Im looking forward to the resolution! :)
In the meantime, as an alternative to the SQL_ATTR_CONNECTION_TIMEOUT solution kindly proposed by @allen-munsch and @andreiroman, it is also possible to modify the connection via SQL after you open it
SET statement_timeout = 10000

Hi ernesto, I believe the timeout being discussed here is the login timeout and not the statement execution timeout. The first is the time the driver waits while it's trying to connect to eht DB, the second is the time it waits for a given command to finish executing.

Im looking forward to the resolution! :)
In the meantime, as an alternative to the SQL_ATTR_CONNECTION_TIMEOUT solution kindly proposed by @allen-munsch and @andreiroman, it is also possible to modify the connection via SQL after you open it
SET statement_timeout = 10000

Hi ernesto, I believe the timeout being discussed here is the login timeout and not the statement execution timeout. The first is the time the driver waits while it's trying to connect to eht DB, the second is the time it waits for a given command to finish executing.

Thanks Alex,
My understanding from the above was that indeed the original issue was reported for login timeouts but that the ticket is now about applying SQL_ATTR_CONNECTION_TIMEOUT through pyodbc's interface. I also understood that SQL_ATTR_CONNECTION_TIMEOUT is intended to be a timeout for the connection (in any query), which if true would solve the issue that I have of not being able to set connection timeouts for the psqlodbc driver. This is why I suggested a workaround.

SQL_ATTR_CONNECTION_TIMEOUT affects all queries, not just connection attempts, so I was trying to keep them separate.

Please do excuse if I have misunderstood the intent of the thread and ignore my above comment. I was just trying to contribute.

Hi,
Is the issue resolved? I am trying to connect to Microsoft SQL and want to handle connection timeout in scenarios where server is either not reachable or down. For this is am unable to set connection timeout which I could use for error handling.
Following are more info:

SQL server Driver : {ODBC Driver 17 for SQL Server}, {SQL Server Native Client 11.0}
pyodbc version : '4.0.30' (installed by pip)
Python version : '3.8'
Windows 10

I have attached the ODBC logs which shows that server is not reachable, which is indeed the case that I want to handle, but I don't get this response from connection object.
Really hoping to find some solution to this.
SQL.LOG
Thanks
Abhishek

Hell Guys,
I was stuck with this timeout thing too so somehow reached here. I've tried the workaround mentioned here.
And I am using this to connect:
SQL_ATTR_CONNECTION_TIMEOUT = 113
cnxn = pyodbc.connect(CONNECTION_STRING,timeout=1,attrs_before={SQL_ATTR_CONNECTION_TIMEOUT : 1})
However, still for some connections timeout is not working as expected.
Timeout worked correctly when exception was:
('08001', '[08001] [Microsoft][ODBC SQL Server Driver][DBNETLIB]Invalid connection. (14) (SQLDriverConnect); [08001] [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Invalid Instance()). (14); [08001] [Microsoft][ODBC SQL Server Driver]Invalid connection string attribute (0)')
However, the program took too long to respond(ignoring timeout) when below error is encountered:
('08001', '[08001] [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied. (17) (SQLDriverConnect); [08001] [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()). (53); [08001] [Microsoft][ODBC SQL Server Driver]Invalid connection string attribute (0)')
Can anyone help me with the workaround for this ?

That's a very old ODBC driver, many bugs have been fixed since. The fact that it's warning about invalid connection string attribute also suggests you should check if the connection string is valid for it. If you're connecting to SQL Server, try the latest Microsoft ODBC Driver for SQL Server.

Actually I know the connection won't get established because of port issue in the server. The idea here us I am connecting hundreds of SQL server through my script and some may not get connected. I just don't want it to spend more than 1 second if connection is not getting established in that time. That's why I need timeout variable working for each case.

Actually I know the connection won't get established because of port issue in the server. The idea here is I am connecting hundreds of SQL server through my script and some may not get connected. I just don't want it to spend more than 1 second if connection is not getting established in that time. That's why I need timeout variable working for each case.

I am not concerned why connection is not getting established. I am concerned about the working of timeout.

I updated latest ODBC driver and timeout issue still persists:
('08001', '[08001] [Microsoft][ODBC Driver 17 for SQL Server]Named Pipes Provider: Could not open a connection to SQL Server [53].  (53) (SQLDriverConnect); [08001] [Microsoft][ODBC Driver 17 for SQL Server]Login timeout expired (0); [08001] [Microsoft][ODBC Driver 17 for SQL Server]Invalid connection string attribute (0); [08001] [Microsoft][ODBC Driver 17 for SQL Server]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. (53)')

What is in the connection string? "Invalid connection string attribute" suggests you may have something else incorrect there.
If you set the login timeout that low, it may be taking long inside OS, and only when it returns can the driver check and return the timeout.

Is there a workaround for this ? What is the lowest possible timeout that can work ?
There is nothing wrong with the connection string. Its with the destination server, port is not opened for remote connections as I have already mentioned earlier.

It depends on various factors such as OS version and configuration.

There is nothing wrong with the connection string.

The "Invalid connection string attribute" warning clearly shows otherwise.

SQL_ATTR_CONNECTION_TIMEOUT = 113
cnxn = pyodbc.connect('DRIVER={ODBC Driver 17 for SQL Server};SERVER=XX.XXX.X.XXX;PORT=1433;DATABASE=master;UID=XXXX;PWD=XXXX;',
timeout=1,attrs_before={SQL_ATTR_CONNECTION_TIMEOUT : 1})
('08001', '[08001] [Microsoft][ODBC Driver 17 for SQL Server]Named Pipes Provider: Could not open a connection to SQL Server [53].  (53) (SQLDriverConnect); [08001] [Microsoft][ODBC Driver 17 for SQL Server]Login timeout expired (0); [08001] [Microsoft][ODBC Driver 17 for SQL Server]Invalid connection string attribute (0); [08001] [Microsoft][ODBC Driver 17 for SQL Server]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. (53)')
Reason I said connection string is fine because I said I am connection hundreds of servers in a loops and it is working for many

PORT is not a valid connection string keyword, and neither is timeout,
Please see the documentation: https://docs.microsoft.com/en-us/sql/connect/odbc/dsn-connection-string-attribute

Timeout is not used as a part of connection string. It is used as a parameter to connect method of pyodbc.

@swarnveer , I'm not exactly sure what the fundamental issue is with the connection timeouts, but here are a few thoughts:

On the pyodbc.connect() call, it shouldn't be necessary to set both the timeout parameter and the attrs_before parameter with {SQL_ATTR_CONNECTION_TIMEOUT : 1}.  Those two parameters do exactly the same thing.  Providing just the timeout parameter should suffice (for the connection that is, executing queries with a timeout is a different matter).
When the connection attempt times out (whatever the timeout value is), pyodbc will raise a pyodbc.OperationalError error.  That can't be avoided.
If the pyodbc error message includes "Login timeout expired", then that shows the connection attempt timed out.  As far as I can tell, there doesn't seem to be any other way of detecting a timeout.
Setting a timeout value does not mean the connection attempt will timeout after exactly the specified number of seconds.  There is inevitably lag, so the connection may take a few more seconds to actually give up the attempt.  The minimum value you can set the timeout to is one second, but in that case you shouldn't expect connections to timeout immediately after one second.
Be aware of connection pooling which may be a factor here.  This is where, under the hood, closed connections are not actually closed but left open for re-use (this is the default behavior, but it can be switched off if you wish).  This probably doesn't impact your scenario but it's worth knowing about.

The problem here is that the timeout parameter is completely ignored by the driver when connecting. You can try 1 second, 3 seconds, 60 seconds, 300 seconds, it doesn't matter: if the connection is bound to timeout, it will always happen after around 60 seconds.

Yes, that's true, @alexnbferreira .  Unfortunately, if the driver doesn't support timeouts, there's not much pyodbc can do about that.  In my tests with the SQL Server "ODBC Driver 17 for SQL Server" driver, setting the timeout parameter did make a difference to how long it took before the connection attempt failed, so the timeout parameter does work in some cases.

"ODBC Driver for SQL Server" (both 13 and latest 17) doesn't have any timeout capabilities built in. So if you're using e.g. turbodbc, you're completely out of luck.
However, if you use pyodbc, you can use "timeout" param:

pyodbc.connect('conn_str', timeout=X)
and it will "simulate" login timeout behavior

Closed due to inactivity.

If it's fine I'd like to reopen this issue because I'm struggling with the timeout as well.
My setup ist the following:
Windows 11
ODBC Driver 17
<EMAIL_ADDRESS>What I'm trying to achieve is to let pyodbc let the OperationalError too throw much earlier when it cannot establish a connection to the mssql db.
No matter how I'm trying to set a timeout value, it seems to be ignored.
pyodbc tries to establish a connection for at least 30 seconds (didn't do any time stoppage to be honest), although I might set the timeout value to 1 second. This also, I believe, cannot be a matter of lag.
Based on the information in this issue I'm not quite sure if I should change the driver for my goal or not.
Can anybody help to clarify what the situation with the timeout parameter is nowadays?
Thanks!

I assume you're using ODBC Driver 17 for SQL Server, since this topic is driver-specific. Which timeout are you using, login timeout or connection timeout?

Sorry for being imprecise but yes, that's correct. ODBC Driver 17 for SQL Server
I wasn't aware of there being a login timeout and a connection timeout.
I'm trying to set the timeout that eventually leads me to a ODBC Driver 17 for SQL Server pyodbc OperationalError with the message:
'08001', '[08001] [Microsoft][ODBC Driver 17 for SQL Server]Named Pipes Provider: Could not open a connection to SQL Server [53]. (53) (SQLDriverConnect); [08001] [Microsoft][ODBC Driver 17 for SQL Server]Login timeout expired (0); [08001] [Microsoft][ODBC Driver 17 for SQL Server]Invalid connection string attribute (0); [08001] [Microsoft][ODBC Driver 17 for SQL Server]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. (53)'
I'm trying to set the timeout according to the documentation (https://github.com/mkleehammer/pyodbc/wiki/Connection#timeout) in the .connect() function with the parameter but this does not seem to work. Granted, I do not know which of either of the timeouts I'm setting with this parameter. Therefore, this might be the wrong way.

Thank you!
At some point, I was going this way as well but immediately dumped it because it wasn't working. But since this seems to be the way, I would appreciate if you could be help making it work.
So going this way, I'm connecting with the following statement:
pyodbc.connect(CONNECTION_STRING, attrs_before={'SQL_ATTR_LOGIN_TIMEOUT': 1})
which gives me the following error:
TypeError: Attribute dictionary keys must be integers
Setting SQL_ATTR_LOGIN_TIMEOUT without the quotes is not working as SQL_ATTR_LOGIN_TIMEOUT is not defined.

Use 103.

I'm sorry but I'm not following you. What do you mean by 103 and how to use it?

SQL_ATTR_LOGIN_TIMEOUT is attribute number 103. Take that in context of the error message you received.

I'm afraid that this solution doesn't help either.
That's how I changed the code line to for establishing the connection with your suggestion:
pyodbc.connect(CONNECTION_STRING, attrs_before={103: 1})
If that's the way how it should be implemented I don't see any change regarding the time passing until the error is thrown.
It still takes at least 30 sec or so. In some occassions even more than 60 or 70 secs. Very weird.
Might there be any other problem that I'm not aware of?

Check ODBC trace to see whether it is setting the attribute correctly.
You can also use strace to see where it is spending the time.

My ugly solution to the timeout problem is checking with sockets
    import customtkinter as ctk
    def so_something_with_sql(self):
        server = '<IP_ADDRESS>'
        port = 1433
        conn_str = (
            'DRIVER={SQL Server};'
            'SERVER=<IP_ADDRESS>\\SQLEXPRESS;'
            'DATABASE=somedatabase;'
            'UID=user;'
            'PWD=password'
        )
        def is_server_reachable(host, port, timeout=2):
            try:
                with socket.create_connection((host, port), timeout):
                    return True
            except (socket.timeout, ConnectionRefusedError, OSError):
                return False
        if not is_server_reachable(server, port):
            self.error_label.configure(text="Could not connect to SQL server", text_color="red")
            return
       # continue with the code in case we got connected


Tooltips on UIImage, UITextbox, and UILabel

Is your feature request related to a problem? Please describe.
I frequently find that it would be convenient to link a tool tip to a piece of text or to an image, rather than to just a button.
Describe the solution you'd like
I'd like them to have the same tooltip system as UIButtons do, with theming capability and the tool tip text added within the element parameters.
Describe alternatives you've considered
I've been using a hack-y solution of a transparent UIButton layered over the image or text, but that's not ideal and adds more elements to juggle.

I expect I can create a function called something like .set_tooltip_text() for all types of UI element and move the button only functionality over to that.

Oh that would be lovely!


Incomplete section pattern

https://trello.com/c/UzOXyxpo/1346-update-the-ui-to-display-completeness-and-link-to-the-correct-questions

We're getting there with this. Here's a few todos around that will help:
Before merge
Validation stuff (you're already working on)
This is probably the biggest thing that will improve this PR

app/models/concerns/validation_tracking.rb
app/validators/date_validator.rb
app/validators/file_upload_validator.rb
app/controllers/referrals/evidence/uploaded_controller.rb
app/forms/referrals/evidence/uploaded_form.rb
app/forms/referrals/previous_misconduct/detailed_account_form.rb
all forms
Maybe add slugs in here as well

QTS bug changes

app/components/manage_interface/personal_details_component.rb
spec/components/manage_interface/personal_details_component_spec.rb
spec/system/manage/case_worker_with_permissions_views_a_public_referral_spec.rb

Handling of action links Also could be a separate PR

specs around that as well
spec/components/summary_card_component_spec.rb

Always passing current_referral into controllers
TODO on this PR

more thorough testing of the new flow

After
Complete Row handling

complete_rows
summary_rows
locally stashed changes

Tidy up


More than one csvs downloaded contains the same data

Hi,
i have executed the following command:
python3.8 download_bars.py --size "30 secs" --security-type CONTFUT --max-days --exchange GLOBEX NQ
Now, in the path /ib-scripts/src/data/CONTFUT/30_secs/NQ i can see a lot of CSVs but some CSVs contains the same data
Example: 20220904.csv
date,open,high,low,close,volume,barCount,wap
20220905  00:00:00,12110.5,12131.0,12104.75,12112.0,332,241,12115.5
20220905  00:00:30,12111.25,12114.5,12106.5,12107.5,119,76,12110.375
Example: 220220905.csv
date,open,high,low,close,volume,barCount,wap
20220905  00:00:00,12110.5,12131.0,12104.75,12112.0,332,241,12115.5
20220905  00:00:30,12111.25,12114.5,12106.5,12107.5,119,76,12110.375

This should be fixed by #6


Support Microsoft Guidance

I am trying to use a 'custom tokenizer' but I am unable to see how can I invoke it. Also can we use a standard tokenizer from HF by pulling it or loading from the local path?

Never mind, I can just load it from transformers...

Yes, custom/HF tokenizer can be used with the generate() method:
from ctransformers import AutoModelForCausalLM
from transformers import AutoTokenizer

tokenizer = AutoTokenizer.from_pretrained('gpt2')
llm = AutoModelForCausalLM.from_pretrained('marella/gpt-2-ggml')

tokens = tokenizer.encode('AI is going to')

for token in llm.generate(tokens):
    print(tokenizer.decode(token))

Please let me know if you were able to use this library with your custom/HF tokenizer.

I am actually trying to use ctransformers with Microsoft guidance, but I am encountering an error with protobuf. I posted a bug report there, but I am unsure what is happening.
import guidance
from ctransformers import AutoModelForCausalLM
from transformers import LlamaTokenizer
from transformers import AutoTokenizer

path = '/home/xxxx/models/gpt4-alpaca-lora_mlp-65B'
llm = AutoModelForCausalLM.from_pretrained('/home/xxxx/models/gpt4-alpaca-lora_mlp-65B/gpt4-alpaca-lora_mlp-65B.ggmlv3.q5_1.bin', model_type='llama')
tokenizer = AutoTokenizer.from_pretrained('decapoda-research/llama-65b-hf')
#print(llm('AI is going to'))
guidance.llm = guidance.llms.transformers.LLaMA(tokenizer, device_map='auto')

"name": "TypeError",
	"message": "Descriptors cannot not be created directly.\nIf this call came from a _pb2.py file, your generated code is out of date and must be regenerated with protoc >= 3.19.0.\nIf you cannot immediately regenerate your protos, some other possible workarounds are:\n 1. Downgrade the protobuf package to 3.20.x or lower.\n 2. Set PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=python (but this will use pure-Python parsing and will be much slower).\n\nMore information: https://developers.google.com/protocol-buffers/docs/news/2022-05-06#python-updates",

Downgrading protobuf to 3.2.0 just leads to another error, duplicate name.
I am not sure however if the error is with any of the components or due to the mismatch between the tokenizer and the model. The model I am using does not have a tokenizer so I am using a generic LLaMA tokenizer to feed the guidance function.

I haven't used the guidance library but the guidance.llms.transformers.LLaMA class is expecting HF transformers object but you are passing ctransformers object, so it won't work.
It looks like there is already an issue opened to support ggml models https://github.com/microsoft/guidance/issues/58

Yes, I saw that thread, but progress slowed down. I would really like the ability to leverage open source community efforts with what comes out of commercial, or well funded (eg HF) groups. ctransformers to me sounds like a great way to achieve that, but perhaps I am misunderstanding the drivers and philosophy behind it. Ideally I would love to be able to do what the other people in the thread were saying, just drop in a local quantized model in place of HF hosted model. This way us independent users, developers and tinkerers can plug into the much better resourced projects.

I would also like to add support for it but it doesn't seem to have documentation on how to add new models.
I will try to follow this example and see if I can make it work. I will look into it next weekend.

@marella Any update on this? I'm looking forward to using StarChat-ggml weights in guidance via ctransformers~
I will take a stab at this later this week, but I don't want to repeat work, especially given the assumption that you might have spent time on this already. Were there any gotchas or big difficulties that I could maybe help with?

Hey, I implemented a 🤗 Transformers compatible model and tokenizer using ctransformers and was able to run one of the examples but I think it has some bugs. I will push the code to GitHub later this week and will let you know. I'm trying to make it work like this:
model = # ctransformers model
tokenizer = # ctransformers tokenizer
llm = guidance.llms.Transformers(model=model, tokenizer=tokenizer)

Hey @marella, any update on this? I like the idea of having a transformers compatible model and tokenizer object for using ctransformers. I'd love to try it out, if you make a public branch with your work (even with the bugs), I can jump off from your starting point and see where it fails for me and offer some fixes if that's helpful.

Hi, I pushed the changes to guidance branch. You can install using:
git clone https://github.com/marella/ctransformers
cd ctransformers
git checkout guidance
pip install -e .

and use it as:
import guidance
from ctransformers import AutoModelForCausalLM
from ctransformers.transformers import Model, Tokenizer

llm = AutoModelForCausalLM.from_pretrained("marella/gpt-2-ggml")
tokenizer = Tokenizer(llm)
model = Model(llm)
llm = guidance.llms.Transformers(model=model, tokenizer=tokenizer)

I fixed some of the bugs. It is working (finishing without errors) with guidance 0.0.61 but getting stuck in latest version.

Thanks very much for this @marella - for the life of me though I can't figure out why it hangs around 450 tokens?

Ok nevermind, it appears to be an issue with ctransformers_llm_context_length returning an incorrect 512 for a llama model. I've overridden and everything is working now.
In doing some benchmarking llm.eval is much slower than llama.cpp

@marella thanks for putting a branch together. I quickly tried to put together a prototype with it with your HF model above marella/gpt-2-ggml and guidance==0.0.61 but it's hanging around _stream_then_save. Any thoughts / tweaks I can make?
Here's a colab to reproduce: https://colab.research.google.com/drive/1YzBvp97pLwAdfl7tlKwCtYH2DZhigXiI?usp=sharing

@marella seconded! This would be killer

Hello, would like address some decode on Japanese character with wrong when decode in streaming.
Does anybody can help how to fix it? (this happened because of llama tokenizer vocab size small, Japanese characters need more than one token to decode correctly)
for example:
��当时年少，��

Hi, I pushed the changes to guidance branch. You can install using:
git clone https://github.com/marella/ctransformers
cd ctransformers
git checkout guidance
pip install -e .

and use it as:
import guidance
from ctransformers import AutoModelForCausalLM
from ctransformers.transformers import Model, Tokenizer

llm = AutoModelForCausalLM.from_pretrained("marella/gpt-2-ggml")
tokenizer = Tokenizer(llm)
model = Model(llm)
llm = guidance.llms.Transformers(model=model, tokenizer=tokenizer)

I fixed some of the bugs. It is working (finishing without errors) with guidance 0.0.61 but getting stuck in latest version.

minstral doesn't work with guidance
Model type 'mistral' is not supported.


pull request for e2e test at 12/18/2016 15:15:17

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


Keepalive timer handling fixed

Starting from version 6.0.0, node returns an error ("callback" argument must be a function) when using native keepalives because of setTimeout calling with null timer handler.

@theturtle32 does this PR look good for you? It seems to really fix an issue with latest version of Node (see #266).

I tested it for months with no issues. As far as I know is a good fix. I tried to modify as little as possible the code but, of course, I'm not sure this will fix all critical races related to the same problem.

Fix released as v1.0.24

                                                                                Hi Brian, Glad to know that my fix has been accepted! I tested it for months on my server with no issues. I don't know if I fixed the problem in the right way, but I think it's not too bad since I found similar keepalive special handling in the source code, as far as I remember.My Best Season's Greetings, Paolo Rossin.                                                                                Invio eseguito dallo smartphone BlackBerry 10.                                                                                Da: Brian McKelveyInviato: giovedì 29 dicembre 2016 03:29A: theturtle32/WebSocket-NodeRispondi a: theturtle32/WebSocket-NodeCc: prossin; AuthorOggetto: Re: [theturtle32/WebSocket-Node] Keepalive timer handling fixed (#251)Fix released as v1.0.24

—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/theturtle32/WebSocket-Node","title":"theturtle32/WebSocket-Node","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/theturtle32/WebSocket-Node"}},"updates":{"snippets":[{"icon":"PERSON","message":"@theturtle32 in #251: Fix released as v1.0.24"}],"action":{"name":"View Pull Request","url":"https://github.com/theturtle32/WebSocket-Node/pull/251#issuecomment-269572984"}}}


fix inherit chart empty check issue

Signed-off-by: yxxhero<EMAIL_ADDRESS>closes: https://github.com/helmfile/helmfile/issues/634

/cc @mumoshu @xiaomudk


Unable to open /dev/mem: Permission denied

I'm having issues getting this to work.
0|mm       | bcm2835_init: Unable to open /dev/mem: Permission denied
0|mm       | Whoops! There was an uncaught exception...
0|mm       | TypeError: Failed to initialize
0|mm       |     at DHT.read (/home/pi/MagicMirror/modules/MMM-DHT-Sensor/node_modules/rpi-dht-sensor/main.js:7:18)
0|mm       |     at Class.checkTemperature (/home/pi/MagicMirror/modules/MMM-DHT-Sensor/node_helper.js:36:32)
0|mm       |     at Timeout._onTimeout (/home/pi/MagicMirror/modules/MMM-DHT-Sensor/node_helper.js:29:18)
0|mm       |     at ontimeout (timers.js:365:14)
0|mm       |     at tryOnTimeout (timers.js:237:5)
0|mm       |     at Timer.listOnTimeout (timers.js:207:5)
0|mm       | MagicMirror will not quit, but it might be a good idea to check why this happened. Maybe no internet connection?
0|mm       | If you think this really is an issue, please open an issue on GitHub: https://github.com/MichMich/MagicMirror/issues

did you ever manage to find the solution to this problem?

@sanjpr Still an open issue for me.

@mchamps
Same issue here.
But I'm working under serveronly cause my board is Raspi B+, so simply run sudo node serveronly and this module works!
Hope there's better solution.


Fixes for 1.0 alpha

Mainly macro syntax changes and using the {:?} format specifier.
Still working on replacing int/uint with isize/usize; will add that to this PR when I'm done.

Finished with the isize/usize conversion. It seems, however, that there are many places where the use of this type isn't appropriate. A more thorough audit is probably a good idea. For now though, the API is unchanged, it just uses the new names.

Waiting for this to be merged.

+1 for this :). Thanks @jpernst

Quick addition to use new us/is literal suffixes that I missed. Thanks @Ketsuban

What I'm writing isn't too fancy, but it is compiling and works with these changes. Thanks!

Grand, cheers folx


bug(TreeControl): TreeControl's trackBy is unusable

Here's the code to create FlatTreeControl:
    this.treeControl = new FlatTreeControl<GeoEntityFlatNode>(
      (node) => node.nodeLevel,
      (node) => node.expandable,
      { trackBy: this.trackByGroupPath } // ========> DOES NOT COMPILE
    );

and the trackByGroupPath:
  trackByGroupPath(index: number, node: GeoEntityFlatNode): string {
    return node.groupPath;
  }

And this whole thing does not compile as

Type '(node: GeoEntityFlatNode) => string' is not assignable to type '(dataNode: GeoEntityFlatNode) => GeoEntityFlatNode'.

Am I missing something or this makes trackBy completely useless?

Looks like this is the same issue as #21364 which should be fixed by #21421.


search: Close search box when searching for an empty string.

Previously clearing the search box and pressing enter would redirect the user to All Messages. This commit changes the behavior so that the search bar closes with no other effects.
More discussion on this on CZO here:
https://chat.zulip.org/#narrow/stream/101-design/topic/recent.20conversations.20for.20streams/near/1621501

@timabbott I added an option to keep the search bar open - what do you think of that?

What's the thinking around the name redirect_search_narrow? I feel like we might want a name with the opposite meaning? Not sure.

Ready for you to look again :)

Merged, thanks @evykassirer!


[feature] create and push to a remote branch if needed

When creating a new request, create and push to a remote branch if necessary.

it actually does that already. try "git review create" (works even on master if you have some unpushed commits.


feat: add an auto-form package to generate forms using Formik; fixes #3

First spike for #3
Figured I'd take a poke at using Formik, so with some copypasta to create a new package I threw together @riccardo-forina's suggestions and it didn't destroy the multiverse :-)  The usage is pretty simple:
        <AutoForm
          definition={formDefinition}
          initialValues={initialValue}
          onSave={onSave}
        />

Where definition is the map of ConfigurationProperty and initialValues would be the usual configuredProperties from the backend.
I didn't wind up using the patternfly-react form components to start off with as I wanted to be sure the binding all worked as expected.
Using the AMQ configuration properties:

Clicking submit after mucking with some values:

TODO - some of these it might be better to iterate on

feedback?
Support more types (currently select, text and textarea)
Validation
Remove submit button from AutoForm component by maybe exposing a doSubmit() on the form object
Move UI widgets to the UI and add dependency
Other TODOs in the code
Proper tests

Great stuff Stan, love the changes so far!

Updated the description a bit, removed the wip label.
I had a look at staging to get some more use cases and realized we needed some additional massaging of form definition properties and even the data and initial values, at least for now if we continue to assume no backend changes.  So I've added in some workarounds and indicated them as such in the comments, namely this and this.


fix: unknown and unused specific device class

TS was right, once again.

@zwave-js-bot automerge


V7  Update

Please update lv_arduino to V7.01, when possible.
Thank you.

I'm waiting for final 7.0.1 release - 7.0.1-dev version is prepared in my repository. Only the first (and siplmest) example is checked because of my limited hardware availability.

Okay. The plan is to release at least a bugfix version every 2 weeks. So v7.0.1 is scheduled to 1 Jun.

@Pablo2048
What do you have to do to release a new Arduino version? If it's possible I can update lvgl's release script to apply some changes in this repo too.

I have to get the new version, check configuration if it's still valid, check at least the simplest example if it still works and if so I have to modify library.json and `library.properties' with new numbers. As I wrote here https://forum.lvgl.io/t/arduino-questions/2405/7?u=pablo2048 I hope that I'll do all this until end of this week.

Would you agree to automatically update library.json on patch releases?
They don't add new features or config options just fixes some bugs.

Okay, no problem with that...

Great! I'll update the script then.

New PR has been created. Can anybody test it (especially with the STM32 example) or should I merge it?


Add flutter sdk 3.24 support

Adding compileOptions and kotlinOptions fixes https://github.com/acoutts/flutter_libphonenumber/issues/79. Upgrading compileSdk fixes https://github.com/acoutts/flutter_libphonenumber/issues/78
Similar issues in another libs: https://github.com/OneSignal/OneSignal-Flutter-SDK/issues/930

@DmitryGaimaldinov is it possible to try this branch in my project before it's merged?
If I add your branch like this:
  flutter_libphonenumber:
    git:
      url: https://github.com/DmitryGaimaldinov/flutter_libphonenumber.git
      ref: support/flutter_3.24.0

I receive the following error:
Resolving dependencies...
Error on line 1, column 7: "name" field doesn't match expected name "flutter_libphonenumber".
  ╷
1 │ name: flutter_libphonenumber_workspace

@richardradics this error happens because flutter_libphonenumber uses melos for packaging. Original package from pub dev is in https://github.com/acoutts/flutter_libphonenumber/packages/flutter_libphonenumber directory (internal directory of https://github.com/acoutts/flutter_libphonenumber). And it's name flutter_libphonenumber. At the same time the main repo https://github.com/acoutts/flutter_libphonenumber has name flutter_libphonenumber_workspace.
I've changed build.gradle inside flutter_libphonenumber_android folder but the package refers internally to flutter_libphonenumber_android: ^1.0.2 which will be next version of https://pub.dev/packages/flutter_libphonenumber_android and not this fork.
If you want to use this fork before merge I've made another branch for you. But I don't suggest using it. It's better to remain on flutter 3.22 and wait for response.
  flutter_libphonenumber:
    git:
      url: https://github.com/DmitryGaimaldinov/flutter_libphonenumber.git
      ref: support/flutter_3.24.0_fork
      path: packages/flutter_libphonenumber

this should be fixed now as of 2.3.1


Bug: Bulk upload API bug

Each bulk upload call will replace previous table.
How to replicate?

Create single catalogue item (via POST api)
Inspect the database for the same item
Now, upload a csv via bulk upload endpoint
Again, inspect the database for the same item

cc: @ub0005

The bug was due to to_sql(...) method of any pandas dataframe (pd.DataFrame object) which had if_exists parameter.

Fixed in PR:
https://github.com/NASA-IMPACT/HLS-Transfer-Catalog/pull/8


Preserve prior op builder backend api

#2560 and #2504 and #2677 changed the way deepspeed creates op builders, this PR aims to preserve the previous API for deepspeed op developers.

Warning
I have not changed all the places to use the new API so many tests will still fail. I want to get early feedback from @delock and @tjruwase first before proceeding with reverting the other changes to ensure everything still works as intended on the Intel side.

Current abstract accelerator API:
from deepspeed.accelerator import get_accelerator
from deepspeed.ops.op_builder.builder_names import CPUAdamBuilder
self.ds_opt_adam = get_accelerator().create_op_builder(CPUAdamBuilder).load()

Prior API and proposed in this PR:
from deepspeed.ops.op_builder import CPUAdamBuilder
self.ds_opt_adam = CPUAdamBuilder().load()

Hi @jeffra , looks like this is a better way of using builder, without need to call create_op_builder() at every place op builder is needed.
In op_builder/init.py, all op builders implemented in deepspeed will be enumerated and their name will be used to build op builders from accelerator extension, I think its a good way to keep the old interface.
https://github.com/microsoft/DeepSpeed/pull/2705/files#diff-3e903a37c259ed263b3073df3b02281c9f4dd22b4f98dd47c4d76a164d376c20R42
In our extension, currently we didn't implement all the builders.  Those builders essential to our customer's workload will be implemented first.   So when DeepSpeed try to get op builder from names that is not implemented in our accelerator extension, None will be returned.   Currently DeepSpeed is build around this awareness.  I'll try this PR in our local environment and see if that still works.

Hi @jeffra , we tested this change in our local environment.  We applied your change and modified all the places that use op builder.  This change works fine on our devices.
When will this change be made, before or after #2677 ?  Another option maybe apply this change on #2677 and merge together.

Hi @jeffra , we tested this change in our local environment. We applied your change and modified all the places that use op builder. This change works fine on our devices.
When will this change be made, before or after #2677 ? Another option maybe apply this change on #2677 and merge together.

Thanks so much for trying this out. If possible could we add it to #2677?

Hi @jeffra , we tested this change in our local environment. We applied your change and modified all the places that use op builder. This change works fine on our devices.
When will this change be made, before or after #2677 ? Another option maybe apply this change on #2677 and merge together.

Thanks so much for trying this out. If possible could we add it to #2677?

Sure, I'll add this change to #2677, thanks!

@jeffra The builder closure needs to return the Builder class during runtime, like implemented as follow.
https://github.com/microsoft/DeepSpeed/pull/2677/commits/0e63cf227fdfdfcdd83f64a0cc247fcf6f0eecbc
Without this change, the following line will fail, since "AsyncIOBuilder" is actually a closure function than a real Builder class.
https://github.com/huggingface/transformers/blob/main/tests/deepspeed/test_deepspeed.py#L103
With the change above, module outside deepspeed which use deepspeed OpBuilder should experience no change of behavior as before.


Node mode on Heroku

Hello, can I somehow use Quagga in Node.js with remote files, without loading them to local filesystem? I want build Telegram bot with ability to recognize barcodes and host it on Heroku, but Heroku doesn't allow projects to save files.

Thanks for giving QuaggaJS a chance to do it's work on the backend. But honestly, I would consider using another solution for decoding barcodes in the backend. QuaggaJS is tailored for the use on frontend.
For node-js I make use of get-pixels and it seems to work with remote data, and even in-memory buffer.
Hope that helps.

Is there an enhancement request here, or is this already something that can be implemented by the user properly?


Vue packages version mismatch

Version
3.9.3
Environment info
Mac OSX
node 8.9.0
npm 6.1.0

Steps to reproduce
Type in terminal:
npm install -g @vue/cli
vue create project
What is expected?
Usual perfect bootstrap of a new vue project
What is actually happening?
Error:
Vue packages version mismatch:

<EMAIL_ADDRESS>(/Users/vincentdupont/node_modules/vue/dist/vue.runtime.common.js)
<EMAIL_ADDRESS><EMAIL_ADDRESS>
This may cause things to work incorrectly. Make sure to use the same version for both.
If you are using<EMAIL_ADDRESS>simply update vue-template-compiler.
If you are using<EMAIL_ADDRESS>or vueify, re-installing vue-loader/vueify should bump vue-template-compiler to the latest.

Why do you have a node_modules in your home directory?
I think it's interfering with the global @vue/cli installation somehow, though I can't reproduce this issue.

Thank you very very much, that was the issue. Removing the home/node_modules folder make the vue cli works correctly now.

On Windows the solution is to remove node_modules from your user directory.

On Windows remove node_modules is a solution. but if i had install some other global package by npm. that solution is costly.
so my soltion is remove node_modules/vue folder if it exist then npm install -g @vue/cli again.
environment(has error):
os: windows
vue: 2.5.6

On a Mac using Yarn I had a node_modules folder in /Users/myuser/.config/yarn/global/ . Deleting that and the yarn.lock and then do a yarn global add @vue/cli solved the problem for me.

remove node_modules  and  yarn.lock in /Users/myuser/.config/yarn/global/  solved my issue. thanks very much~

but... where are globally installed packages supposed to live? it makes sense that folder should exist

Thanks
node_modules in home directory


wanpipe install is broken on Debian

Formally opening a bug for this: this was discussed via email about a month ago.
Wanpipe installation appears to be broken on Debian, but not Ubuntu.
See unary operator expected warnings below:
        ----------------------------------------------------------
                  WANPIPE v7.0.34 Installation Script
            Copyright (c) 1995-2013, Sangoma Technologies Inc.
        ----------------------------------------------------------

Installing WANPIPE Device Drivers: Linux KERNEL

To integrate WANPIPE Multi-Protocol Voice & WAN Router
modules into the Linux kernel, the kernel has to be
updated with latest wanpipe sources.  Install will only
modify existing wanpipe source that is already in the
Kernel.

IMPORTANT:
It is always recommended to say YES to all options
prompted during the install!

        ----------------------------------------------------------
                  WANPIPE v7.0.34 Installation Script
            Copyright (c) 1995-2013, Sangoma Technologies Inc.

Installing WANPIPE include headers ...
ERROR: Directory /lib/modules/5.10.0-12-amd64/build/include/linux not found!
       Corrupted linux headers in /lib/modules/5.10.0-12-amd64/build dir.

ERROR: Failed to upgrade WANPIPE device drivers!

Make sure that following directories exist:
        '/lib/modules/5.10.0-12-amd64/build/net/wanrouter'
        '/lib/modules/5.10.0-12-amd64/build/drivers/net'

Make sure that current kernel image version
matches the kernel version in /lib/modules/5.10.0-12-amd64/build !!!

        ----------------------------------------------------------
                  WANPIPE v7.0.34 Installation Script
            Copyright (c) 1995-2013, Sangoma Technologies Inc.
        ----------------------------------------------------------

WANPIPE KERNEL DRIVER COMPILATION

The next step in WANPIPE installation involves compiling
WANPIPE kernel modules.

This script will compile and install WANPIPE modules
into the currently running linux kernel.

For greater customization you will be prompted to
select which Protocol/Drivers you would like to
build into the WANPIPE kernel modules.

Wanpipe for Asterisk/Dahdi/Zaptel
        Default for Asterisk/Dahdi/Zaptel
Wanpipe for Wan Routing/API
        Default for Wan/IP Routing and Data API
Wanpipe for Asterisk SMG/SS7
        Default for Asterisk SS7
Wanpipe for TDM API
        Default for FreeSwitch and Voice API

Custom Compilation:
------------------
  Customise WANPIPE driver compilation to add only the
  protocols that you need.  This way one can reduce
  the size of the WANPIPE kernel drivers.

Checking current processor type ...x86_64

./Setup: line 2654: [: -eq: unary operator expected
ERROR: Unsupported Kernel Version 5.10.0-12-amd64
wanpipe install failed: unsupported kernel?

@brown1d
Adding some of your insights from email a few months ago here, so they don't get lost over time.
I've also reported this to Sangoma, but I'd be very surprised if they even understand the issue, let alone do anything about it.
Took defaults for modules:
Press Enter for Default: /lib/modules/5.10.0-14-cloud-amd64/build
And yes it died at:
./Setup: line 1350: [: : integer expression expected
Now On Ubuntu you get these values get populated because the script reads from: /lib/modules/5.15.0-41-generic/build/Makefile as:
# SPDX-License-Identifier: GPL-2.0
VERSION = 5
PATCHLEVEL = 15
SUBLEVEL = 39
EXTRAVERSION =
NAME = Trick or Treat

Now on Debian that just contains:
[root@ip-10-0-0-135:/lib/modules/5.10.0-14-cloud-amd64/build#] more Makefile
include /usr/src/linux-headers-5.10.0-14-common/Makefile

And if you follow that link you find the variables:
# SPDX-License-Identifier: GPL-2.0
VERSION = 5
PATCHLEVEL = 10
SUBLEVEL = 113
EXTRAVERSION =
NAME = Dare mighty things

If you change the source directory to be: /usr/src/linux-headers-5.10.0-14-common
Then it magically works. Fix for this would be to make the shell script follow the include file, which we could do.
Ubuntu just uses a bunch of symbolic links to go from build to /usr/src/linux-headers-X, rather than using a Makefile include.  Makefile include’s are a totally reasonable way of doing things, and certainly supported in GNU make.  However the Wanpipe installer just tries to parse the variables out of the original Makefile, and does not follow includes.  I tried to play last night to see if it was possible to build a Makefile that could be used to extract out only the variables but it does not seem to work right (i.e. use make as the parser, rather than rolling your own).
I see two ways to handle this:

Detect Ubuntu vs Debian, and pass the correct source path.  However that’s going to mean we then need to track future changes to either

In Wanpipe installer handle includes, probably by using Recursion.  The way the script file works it expects Makefiles to be called “Makefile” which is an assumption, and not unfair, but not always true…

I would go with option 2, as it could be rolled into a single wanpipe patch, and then we don’t have to worry what happens in the future.


Example of file upload via light4j

Since we are dealing with lower level internals of undertow so it'll be a good idea to see such an example.

@sachinwalia2k8 There is a real example that we use to upload files in light-codegen/codegen-web module.
https://github.com/networknt/light-codegen/blob/master/codegen-web/src/main/java/com/networknt/codegen/handler/ValidateUploadFileHandler.java


Support for table cells?

Now that Firefox supports sticky headers on tables, can we add functionality to support tables in this polyfill as well?

And not only Firefox. All browsers except IE and Opera mini now support sticky on th elements.

For reference, this is the commit where table cell support was removed. I'm looking into this now, and may open a PR.

That would be highly appreciated.

Is there any update on this? support table cells is nice to have.

Would be great to have this feature back


Python 3.12 support

Sean, unit tests are passing, but how can we test the changes to release.yml?

perform the build in push.yml too?

Pushed to pypi!


Correct failures that occur in test code

In the process of processing PR #188,
I confirmed that when I used the Promise chain in Mocha, I did not wait for all Promise to end.
We will have to find another alternative to this part.

Can you past a test code ? Mocha works fine with Promises, I never saw a bug. So I think the usage of Promise might have been incorrect instead.


Fix duties merging bug

Fixes #250
New behaviour: two adjacent duties will be merged on view iff all of these are the same:

the user who drops
is free
requested user

Pull Request Test Coverage Report for Build 1939

3 of 7 (42.86%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.2%) to 89.179%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

app/helpers/duties_helper.rb
3
7
42.86%

Totals

Change from base Build 1929:
0.2%

Covered Lines:
478

Relevant Lines:
536

💛  - Coveralls


PfkD-extended improvement: Use both table and column name for column filtering

As of now, we filter left_col and right_col only on subquery primary key column name, not table name.

This can, in some edge cases, result in undesired filtering of potential foreign key columns with names equals to primary key column names

Therefore, filtering with both the PK table and column name (eg. "customer.id") should avoid this issue

[ ] Modify the query (maybe with REPLACE functions, like the current solution) to filter correctly

[ ] Verify results

Lukket blandt alle changes fra v2 med e290589b72de1f653ca521849359004555fbcd29


Add hollow triangle pattern in C, Pattern34

Description
Task
For the given input n the number of rows printed should be 2*n-1 for ex:

Note

Filename should be Pattern34.c

can you assign this to me?

ok @JayPankajPatel you can work on this issue

@JayPankajPatel are you working on this issue?

The code for this Pattern is ready. Assign me and I'll send a pr.

ok, @MrigankaGhosh I am assigning this issue to you.

@Vishal21121 I  have already sent a pull request

pr merged #57


Add a way to pass request info back in libraries

We have a few use cases that need an extra place to stash information--mainly for results from Library.query().
for example, we need a way to pass back:

Number of chunks returned (for the case where omit='*' is true, and the actual chunks are not returned)
Number of chunks that would have been included because the person didn't pass sufficient access_token (if the host server opts in to revealing that)
A message that should be displayed to clients reading this library (in the Library() constructor if it sees a message it should print it)

Probably the easiest way is to add a details dict to the library format that's optional:
{
  //...
  //details is optional. It's typically only included in libraries generated by Library.query()
  "details": {
    //If message is provided, then any time this library is loaded via Library(), it will print that message to the console. This is useful for example to say "This library included some content that was filtered out. Contact<EMAIL_ADDRESS>for an access key"
    "message": "A message",
    //Counts and all keys inside are optional
    "counts": {
      //How many chunks are included in the `content`, or would have been had they not been omitted.
      "chunks": 5
      //How many chunks were filtered out because they didn't match the filter criteria
      "filtered": 2,
     //How many chunks were filtered out because you didn't pass an access_token that had sufficient access. Hosts by default do not divulge this, but some choose to.
      "restricted": 3
    }
  }
  //...
}

[ ] Add a count_filtered property once we add filtering to Query.

yes


[CT-1718] Add an "FYI" Message Type

Describe the feature
Sometimes we have messages we would would like to write to the console without creating a custom event type. For example, we often want to add formatting by inserting blank lines or break lines like "=====...". We also have a variety of messages we print for informational purposes, but which are unlikely to be consumed programmatically by structured logging users.
To solve this problem, let's introduce a new event type which contains the standard event fields, but only one additional field (called "Text" or "Message"?) which can include miscellaneous text and formatting.
After this change, we should also be able to remove the EmptyLine event.
Who will this benefit?
Consumers of structured logging will benefit from this change, since they will no longer see events like EmptyLine which are useless to them. Since this change will also make it possible to remove other events, like StarterProjectPath and project initialization related events, it will reduce the complexity and size of our event schema.

resolved by https://github.com/dbt-labs/dbt-core/pull/6561

Sorry! This was not included in #6561


Propagate system properties to HadoopJavaJobRunnerMain so that jobs u…

Propagate system properties to HadoopJavaJobRunnerMain so that jobs using HadoopJava's constructor can correctly use them.

Can you elaborate more on the issue this PR is trying to solve? What kind of properties do you mean by "system properties? Why do users need access to them?

Can you elaborate more on the issue this PR is trying to solve? What kind of properties do you mean by "system properties? Why do users need access to them?

There are some jobtypes which need properties set at system level and should not be accessible to user. This is a security feature which ensures certain properties are not overridden.

Can you elaborate more on the issue this PR is trying to solve? What kind of properties do you mean by "system properties? Why do users need access to them?

There are some jobtypes which need properties set at system level and should not be accessible to user. This is a security feature which ensures certain properties are not overridden.

How are we ensuring these properties don't get overridden with this change?

Can you elaborate more on the issue this PR is trying to solve? What kind of properties do you mean by "system properties? Why do users need access to them?

There are some jobtypes which need properties set at system level and should not be accessible to user. This is a security feature which ensures certain properties are not overridden.

How are we ensuring these properties don't get overridden with this change?

There are certain properties which are needed to execute some job types. These properties are only read by the jobtype code and cant be written back. If a user provides any of these properties in DSL, then they go to job props and not sys props.
We can talk about it in more detail offline.


Bump up version to 0.4.1.

Codecov Report

Merging #69 (dcdbc5c) into main (7114098) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main      #69   +/-   ##
=======================================
  Coverage   86.70%   86.70%
=======================================
  Files          29       29
  Lines         782      782
=======================================
  Hits          678      678
  Misses        104      104

Impacted Files
Coverage Δ

pyhpke/__init__.py
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Check correspondence between plot coordinates and "real" coordinates

Check which coordinates are being used for the intensity image - the "real" coordinates up to (10980, 10980) or the coordinates of the current level, or the coordinates of the DATA_LEVEL

Closed by #31


Links to specified rules in contextual menu

When opening the contextual menu of the extension, it could have a list of saved rules, to open the link of that rule
I often reopen a link that is renamed, and I don't want to manage it both in bookmark and in tab modifier (my rules have to be updated sometimes)

(sorry for the french in the screen !)

I agree with this request. It would be very nice to have the contextual "Rename Tab", where I could simply enter the new name, and have the settings transferred into the Rules of Tab Modifier.

Hello @Raph-xyz,
It's not possible to make the contextual menu dynamic.
Best

Syl, couldn't the https://developer.chrome.com/docs/extensions/reference/api/contextMenus#property-CreateProperties-documentUrlPatterns property of the contextMenus API be used to implement that?


Separate react example app from component package

We should move the example react app to an example/ folder and unpack the src/swap/ directory a level up to make more clear the difference between the component package and the example app.

Wrong repo. Closing.


_transient_timeout_timberloader wp_options entries not being cleared on clear_cache_timber_database()

Expected behavior
I'd expect clear_cache_timber_database() to delete not only transient_timberloader but also transient_timeout_timberloader so those entries do not pollute the database.
Actual behavior
Wordpress automatic transient cleanup expects to find matching transient and  transient_timeout matching entries in wp_options. If any of the entries aren't there they do not get deleted as you can see in
wp-includes/option.php delete_expired_transients
Steps to reproduce behavior

Install timber
Create a template and a twig template that uses Timber::render('template.twig', $context, 600);
Ensure that the Timber cache mode is TRANSIENT and no Object Caches are installed or denabled.
Access that template in wordpress.
Check that new _transient_timeout_timberloader and _transient_timberloader have been created.
Create a second template, this time just .php that clears Timber cache: i. e:
<?php $loader = new TimberLoader(); $loader->clear_cache_timber(); $loader->clear_cache_twig();
Access that template in wordpress
Check how _transient_timberloader entries have been deleted.
Access wp-cron.php
Check how _transient_timeout_timberloader are not deleted

What version of WordPress, PHP and Timber are you using?
Wordpress 5.4.1, PHP 5.4, Timber 1.15.2
How did you install Timber? (for example, from GitHub, Composer/Packagist, WP.org?)
Composer/Packagist

I may want to fix this myself and do a pull request this weekend if you find no inconvenience and you think this problem should be adressed.

Thanks for laying out the problem and submitting a PR. I just reviewed and merged. This will be part of the next release (later on this week)


Added blogpost for CLI for Microsoft 365 release 5.3

Category

[ ] Content fix
[x] New article
[ ] Example checked item (delete this line)

@waldekmastykarz: could you please review this post and then merge it when the release is out?
Thank you

Great achievement @plamber 🚀🚀🚀 - thanks for posting this here!
note @waldekmastykarz  -  please don't forget to then remove the popular type from v5.2 post - that then needs to be regular again


(GH-1175) Populate $nodes and $targets with --targets and --nodes

When --nodes or --targets is provided on CLI, "magically" pass that arg to $nodes or $targets if there is a plan parameter with name $targets XOR $nodes of type TargetSpec AND there is not a plan argument specified on the CLI with name nodes or targets.

Looks like I forgot to check in some fixtures. Also need to look in to some legit integration failures.

CLA signed by all contributors.

Closes #1175


fix(gh-239): manually specify install for goreleaser

Resolves gh-239

Tested this locally. The addition of the install line produces the desired output.


Map switches perspective irreversibly

Subject: Map switches perspective irreversibly
Description:
I click-held a part of the map and moved my cursor.
Results:
What happened: The map's angle and orientation changed so that now north-east is on top and locations on the bottom of the screen appear much closer than locations at the top of the screen. There is no clear button or sign to reverse this change.
What should have happened: I simply wanted to move around the map by dragging.
Backend version: develop-7c33e18d
Frontend version:
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.1 Safari/605.1.15
Page: https://couchers.org/search?location=Maastricht%2C+Limburg%2C+Netherlands&lat=50.8512438&lng=5.6909768#loc=3.89/43.52/-76.86/-17.6/60
User: pabluschko (15868)

um, not a bug?