text:
Preinstall mamba in base images

Describe the feature you'd love to have in Orchest
mamba is a drop-in replacement for conda that is super fast. It is helpful when trying to install complex dependencies from conda-forge, because otherwise the dependency resolution can take a very long time (several hours in some extreme cases).
However, as it stands now, mamba is difficult to install on the base image:

conda install -c conda-forge -y mamba draws a really old version by default that minimizes package upgrades (what happened to me earlier)
conda install -c conda-forge -y "mamba=0.22.1", the latest version, gives conflicts
In fact, conda install -c conda-forge -y "mamba>0.15.3" gives conflicts, and while building a conflict report, hits a conda bug https://github.com/conda/conda/issues/9681

Surprisingly (I'm still astonished), conda install -c conda-forge -y "mamba=0.15.3" && mamba install -c conda-forge -y "mamba>0.15.3" installed the latest mamba version, conflict free, and now I'm able to do mamba install -c conda-forge -y pytorch without waiting a million years. Therefore, the case for having the latest mamba version preinstalled is quite compelling (and would help making ~conda~ mamba the default recommendation, as discussed in gh-759).
(For the record, I believe there are some ongoing efforts to make conda use libmamba and therefore become much faster, but I don't know what's the roadmap or what can users expect)
There are two ways to do this:

Preinstall mamba on our current base images, possibly following the steps I "discovered".
Upgrading our Docker baseline. The latest jupyter/scipy-notebook image has mamba preinstalled already, however elyra/kernel-py:2.5.2 seems to be based on an older version, and I can't find the sources of the Elyra dockerfiles. This last option requires more work though.

Is your feature request related to a problem? Please describe.
At the time of writing conda is very problematic: it needs extremely long installation times (too long by any sane measure) and it often gets stuck in suboptimal solutions and unnecessary conflicts.
However, conda/mamba allow installing arbitrary versions of non-Python dependencies (as opposed to apt-get) and allow installing some packages that are not available on pip, like RAPIDS.
And finally, lots of data scientists have familiarity with conda and the Anaconda distribution already.
Therefore, it would be great if we could make conda/mamba work well in Orchest.

For future reference, this is the absolutely conflict report that conda produced when trying to install a modern mamba on the current environment: https://gist.github.com/astrojuanlu/e910cf7299910cbf972746936283757b (too long for GitHub)

repo: orchest/orchest


text:
List doesn't update if the items themself change, maintaining the same length

I have a view with some tabs, if you change a tab you'll get a different user. Only when the amount of items are the same, the view doesnt get updated.
<div className="table-responsive" style={{ maxHeight: @state.height, overflow: 'auto' }}>
        <ReactList
          itemsRenderer={@itemsRenderer}
          itemRenderer={@itemRenderer}
          length={@state.items.length}
          type='simple'
          translate3d={true}
        />
</div>

A quick console.log in the itemRenderer proves that the row's are not updated / rendered. My solution now is to add a ref to the reactlist and forceupdate it
@refs.list.forceUpdate()
....
 <ReactList ref="list"

All suggestions are more than welcome, thanks!

This is a duplicate of #36.
Also, I see you're using a translated3d prop when you probably meant useTranslate3d.

Ah! Thanks!

source: gharchive/issue

authors: caseywebdev reneweteling

repo: orgsync/react-list

license: mit

license_type: permissive

license_source: bigquery


text:
页面沉浸式

页面沉浸式的时候，蒙板如何全屏

同问，@wangyoucai 你解决了吗

repo: orhanobut/dialogplus


text:
🛑 TTS / Tillgängliga röster is down

In 8f0a396, TTS / Tillgängliga röster ($TTS_ENDPOINT/voices) was down:

HTTP code: 502
Response time: 160 ms

Resolved: TTS / Tillgängliga röster is back up in 1028dd2 after 16 minutes.

repo: oribisoftware/upptime

license: MIT

license_source: github-api


text:
🛑 TTS (Oribi Speak) is down

In 907093f, TTS (Oribi Speak) (https://tts.oribi.se/v2/speakb64) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TTS (Oribi Speak) is back up in 252ace0 after 7 minutes.


text:
Create a WiKi page about installing OrientDB using different ways

We should create new pages for:

[ ] Install with wget
[ ] Install with MacOSX homebrew
[x] Install with Dockers
[ ] Start OrientDB server on Amazon AWS
[ ] Start OrientDB server on Jelastic (we're waiting for the Jelastic post about it)

We already have this in docs.

repo: orientechnologies/orientdb


text:
Unable to deploy in Docker swarm

This is a: Run Issue
Details

I tried to run this Docker image on my Docker Swarm and it fails with this error message in the Logs:
Stopping lighttpd
s6-rc: info: service lighttpd successfully stopped
s6-rc: info: service pihole-FTL: stopping
Stopping pihole-FTL

  [✗] Unable to fill table adlist in database /etc/pihole/gravity.db

s6-rc: info: service pihole-FTL successfully stopped
s6-rc: info: service _startup: stopping
Terminated
s6-rc: info: service _startup successfully stopped
s6-rc: info: service _uid-gid-changer: stopping
s6-rc: info: service _uid-gid-changer successfully stopped
s6-rc: info: service cron: stopping
  [i] Cleaning up stray matter...Stopping cron
s6-rc: info: service cron successfully stopped
s6-rc: info: service legacy-cont-init: stopping
  [✓] Cleaning up stray matter
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

the Normal Pihole Docker image Runs fine.
What is also noticed that the pihole folder i use gets the permission changed from the usual default i give it to 999:lxd which im pretty sure the normal image doesnt.
also had it stuck hard on the unbound.sh once and the container wouldn't get killed.
Related Issues

[ ] I have searched this repository/Pi-hole official repository/Pi-hole forums for existing issues and pull requests that look similar

How to reproduce the issue

Environment data

Operating System: Ubuntu Server 22.04
Hardware: Turing RK1
Kernel Architecture: aarch64
Docker Install Info and version:

Software source: docker-ce
Supplimentary Software: portainer

Hardware architecture: aarch64
Docker Image Tag: latest

docker-compose.yml contents, docker run shell command, or paste a screenshot of any UI based configuration of containers here

version: '3.8'

services:
  pihole:
    image: rlabinc/pihole-unbound:latest

    ports:
      - "80:80/tcp"
      - "443:443/tcp"
      - target: 53
        published: 53
        protocol: tcp
        mode: host
      - target: 53
        published: 53
        protocol: udp
        mode: host
      - target: 67
        published: 67
        protocol: udp
        mode: host

    environment:
      - TZ=${TIMEZONE}
      - WEBPASSWORD=${WEBPASSWORD}

    volumes:
      - type: bind
        source: /mnt/docker-storage-ssd/pihole/pihole
        target: /etc/pihole
      - type: bind
        source: /mnt/docker-storage-ssd/pihole/dnsmasq.d
        target: /etc/dnsmasq.d

    deploy:
      replicas: 1
      restart_policy:
        condition: on-failure
        max_attempts: 3

any additional info to help reproduce
the cluster is running with 4 nodes and all nodes have access to the same files via glusterfs.
and i know that this might be hard to debug. but since im only running this on one node this should be the same as running it on a normal system

These common fixes didn't work for my issue

[X] I have tried removing/destroying my container, and re-creating a new container
[X] I have tried fresh volume data by backing up and moving/removing the old volume data
[ ] I have tried running the stock docker run example(s) in the readme (removing any customizations I added)
[ ] I have tried a newer or older version of Docker Pi-hole (depending what version the issue started in for me)
[X] I have tried running without my volume data mounts to eliminate volumes as the cause
[X] I have tried running official Pi-hole docker image to check if it works there

If the above debugging / fixes revealed any new information note it here.
Add any other debugging steps you've taken or theories on root cause that may help.

Is this a fresh installation?
Send me the unbound log file located at /opt/unbound/etc/unbound/unbound.log inside the container.

the log is completely empty.
also tried the solution you suggested.
when i try to restart it fails now at this "Unable to create new database /etc/pihole/gravity.db_temp"

Tried fresh install without the volumes?

it stopped compaining about unable to create new database but still wont start.
Current docker compose file looks like this.
version: '3.8'

services:
  pihole:
    image: rlabinc/pihole-unbound:latest

    ports:
      - "80:80/tcp"
      - "443:443/tcp"
      - "192.168.3.203:53:53/tcp"
      - "192.168.3.203:53:53/udp"
    environment:
      - TZ=${TIMEZONE}
      - WEBPASSWORD=${WEBPASSWORD}

      # This below is just Docker Swarm stuff
    deploy:
      replicas: 1
      placement:
        constraints: [node.labels.pihole == true ]
      restart_policy:
        condition: on-failure
        max_attempts: 3

Share the docker log?

_pihole-unbound_pihole.1.zdf27tczpcn3418nrce1w0lrd_logs.txt
this is the complete log it gives me.

uh i also tried with the exact same docker compose file the "old" imager cbcrowe/pihole-unbound:latest.
and that works fine but it uses a old pihole version.

It seems something is wrong with the database. Can you run the container with your main compose file but without the Docker Swarm stuff and check if it works? If this issue is related to Docker Swarm then I'm afraid I can't help you out.
Also, send me the FTL.log and FTL.log.1 from /var/log/pihole/ inside the container along with the complete docker log.

ok i got it to work on certain conditions.
New Containers will ALWAYS crash for me no matter what with or without the swarm stuff (and Docker swarm starts always starts new containers)
if i try to start a existing container again with "docker compose up" when the container has already crashed once it will start fine.
there is a pihole-1  | [1706568999] unbound[239:0] warning: unbound is already running as pid 259.  line in the log when it has started fine.
with docker compose up --force-recreate it will always crash.

As I can't recreate this issue on my end and you've found a fix, I'm closing this issue.

As I can't recreate this issue on my end and you've found a fix, I'm closing this issue.

no i havent found a fix for docker swarm since containers are always recreated resulting in a crash no matter what.
i just decided that i wont use this repo and used another that works fine.

authors: DreiPixel origamiofficial

repo: origamiofficial/docker-pihole-unbound


text:
Keep order of keys by default

Hey,
thanks a lot for this tool – just installed it and I'm already sold. <3
There's one thing I'd love, however: A way to keep the input order of the keys. Right now, convfmt always sorts the keys alphabetically, which is something I would expect behind a switch.
Again, thank you for this!

Hi, thanks for the feedback!
Unfortunately, for now most of underlying implementations of formats don't the order of keys:

https://github.com/serde-rs/json/issues/1014

But I'm open to experiments with IndexMap, PRs are very welcome.

authors: oriontvv runiq

repo: oriontvv/convfmt


text:
fix MuAPI Config::get Error

app/Controllers/Mu/UserController.php
if (Config::get('log_traffic_dynamodb')) {             try {                 $client = new DynamoTrafficLog();                 $id = $client->store($u, $d, $nodeId, $id, $totalTraffic, $rate);                 $res['id'] = $id;             } catch (\Exception $e) {                 $res['msg'] = $e->getMessage();                 Logger::error($e->getMessage());             }         }
not implemented Config Get static function

Coverage decreased (-0.03%) to 8.171% when pulling 019a24217e37fb2919e415c55fa9c09493f6f676 on charleyzhu:dev into d2977dabc07f767cc7cdd33c0ec3f6a16f3766d2 on orvice:dev.

请问下 这个几个pull request是没通过吗？

dockerfile没必要添加mysql判断, depends_on 会决定启动顺序了
另外docker-compose.yml里redis端口不应该映射出去

depends_on是决定了启动顺序，但是如果使用docker-compose启动应用，在ss-panel启动完成然后导入数据库的时候你会发现这时候sspanel-mysql是起来了，但是mysql的服务并没有启动完全，这时候并不能完成导入操作和创建管理员的操作

那加下restart也可以了，mysql链接失败，自动重启即可。

还有
app/Controllers/Mu/UserController.php
里面使用 if (Config::get('log_traffic_dynamodb'))
这个Config::get这个static方法并不存在

redis是我理解错误，我以为这个是给服务器用的，所以映射出去了，但是如果endpoint加入判断mysql服务是否启动成功可以提示docker-compose的体验

Coverage decreased (-0.03%) to 8.171% when pulling 019a24217e37fb2919e415c55fa9c09493f6f676 on charleyzhu:dev into d2977dabc07f767cc7cdd33c0ec3f6a16f3766d2 on orvice:dev.

1  mu v1是有问题，v4开发的时候仅考虑到了mu v2
2 首先引入新依赖本来就不太好，而且  有depend on，mysql先启动就没有问题了，有restart重启机制，也能够跑起来，而且其实mysql没启动完成这种情况很少。

mysql的属性里面也没有指定sspanel这个库的用户和密码，连接的时候还会提示用户名和密码错误
不能用root用户来连接吧？在docker-compose中也指定了DB_USERNAME和DB_PASSWORD使用sspanel作为连接mysql的用户和密码

使用root情况一般是，一个web服务一个mysql实例
如果是高级用户，完全可以自己定制docker-compose，自己创建msyql账户配置

"而且其实mysql没启动完成这种情况很少",偏偏我就遇到了 :( 使用的是vultr.com的vps，1G内存，1核CPU，可能配置太差了，docker-compose定制确实是可行的，可能我想多了，

app/Controllers/Mu/UserController.php
里面使用 if (Config::get('log_traffic_dynamodb'))
这个Config::get这个static方法并不存在
这个怎么处理呢？我是加了个方法

还有MuV2的获取用户的方法里面没有ret

@charleyzhu mu config的问题我会改，  mu v2里已经不需要retle

@orvice 现在V4版本使用ss-go的时候如果config返回不是json，ss服务器提示以后端口监听会莫名的取消，这个问题还没找到在哪里，另外问下以后V2版本的api是不是依据http 状态码来区分是否请求成功？

是  现在ss客户端都用状态码判断成功了

@orvice 好的，谢谢！自己在练习重复造轮子，重写ss-go-mu

删除了项目是不是说明提交新的版本？

O大神求解，v4.0.0 用hyperapp教程布置
问题一：用户分配端口正确，但是二维码获取的端口错误，例:用户端口分配为1026，二维码获取的是1027
问题二：默认邀请码数量设置不了，不管设置成什么每个人都还是可以获取10个邀请码，希望可以设置成0，关闭这个功能

求助：搭建完V4.0.0的前端后，访问http://IP/admin  后不能正常停在管理员界面，日志显示GET /api/users/null/ HTTP/1.1" 401 44   ，这是什么原因呢？
其他界面都可以正常访问，admin账户也已经建好了。谢谢答复。

source: gharchive/pull-request

authors: charleyzhu coveralls gtihubAlimjan michaelauto orvice stone1949

repo: orvice/ss-panel


text:
reorganize layout of settings

It should be nicely and correctly divided into screens and fragments

duplicate

repo: orzechowskikamil/motoresponder


text:
Fix eslint loader issues

eslint-loader is replaced with the eslint-webpack-plugin and the order of functions is updated.

@henrywang This only passes the travis eslint test when the node_modules are cached. This passes make eslint locally for me. Do you have any thoughts on fixing this?

@jkozol, I think we can clear travis cache to fix this issue by following this guide. But I have no permission on Travis to clear cache. Could you please help to do that or do you know who have permission to do that? Thanks.

authors: henrywang jkozol

repo: osbuild/cockpit-composer


text:
test: add README.md on how to make tests for stages

Adds a README.md which explains what do you need
to do to add a new test for an stage
This hopes to document a bit how to add new tests for an stage.

:eyes: @gicmo

repo: osbuild/osbuild


text:
stages/oci-archive: write history entries

According to the OCI Image Format Specification history entries for layers in the container are optional; but when trying to push a container quay.io via skopeo (copy oci-archive:… docker://quay) it will fail with "Cannot convert an image with 0 history entries". This seems to come from the containers/image library when the container is converted back from the docker distribution format to oci-archive on quay.io. Thus it seems that when skopeo converts the image to the docker format for the distribution it does not fill any the history entries, which are then assumed and required to be there when converting back.
To fix this, insert history entries for each layer that is created.

@teg @gicmo This PR fixed quay.io uploading issue. And it works with docker.io as well.
Verified on:
osbuild-selinux-27-1.20210329gita96eaf1.20210329gita96eaf1.el8.noarch
python3-osbuild-27-1.20210329gita96eaf1.20210329gita96eaf1.el8.noarch
osbuild-27-1.20210329gita96eaf1.20210329gita96eaf1.el8.noarch
osbuild-composer-core-28.3-1.el8.x86_64
osbuild-composer-28.3-1.el8.x86_64
osbuild-ostree-27-1.20210329gita96eaf1.20210329gita96eaf1.el8.noarch
osbuild-composer-worker-28.3-1.el8.x86_64

Upload to quay.io:
[cloud-user@new-rhel-8-4 ~]$ skopeo copy oci-archive:e4fa3a99-11f4-4035-971c-fbc58c49725c-rhel84-container.tar docker://quay.io/xiaofwan/rhel-edge:latest
Getting image source signatures
Copying blob c00a33b1e994 done
Copying config f4f290da2e done
Writing manifest to image destination
Copying config f4f290da2e [======================================] 471.0b / 471.0b
Writing manifest to image destination
Storing signatures

[cloud-user@new-rhel-8-4 ~]$ sudo podman pull quay.io/xiaofwan/rhel-edge:latest
Trying to pull quay.io/xiaofwan/rhel-edge:latest...
Getting image source signatures
Copying blob c00a33b1e994 done
Copying config f4f290da2e done
Writing manifest to image destination
Storing signatures
f4f290da2ecc190609189ea43003ba32d0f740f4a8e10219d5fa3c252481bd40

[cloud-user@new-rhel-8-4 ~]$ sudo podman images
REPOSITORY                                   TAG     IMAGE ID      CREATED         SIZE
quay.io/xiaofwan/rhel-edge                   latest  f4f290da2ecc  11 minutes ago  1.25 GB

Upload to docker.io
[cloud-user@new-rhel-8-4 ~]$ skopeo copy --dest-creds henrywangxf:hello112233 oci-archive:e4fa3a99-11f4-4035-971c-fbc58c49725c-rhel84-container.tar docker://docker.io/henrywangxf/rhel-edge:latest
Getting image source signatures
Copying blob c00a33b1e994 done
Copying config f4f290da2e done
Writing manifest to image destination
Storing signatures

[cloud-user@new-rhel-8-4 ~]$ sudo podman pull docker.io/henrywangxf/rhel-edge:latest
Trying to pull docker.io/henrywangxf/rhel-edge:latest...
Getting image source signatures
Copying blob c00a33b1e994 [--------------------------------------] 0.0b / 0.0b
Copying config f4f290da2e done
Writing manifest to image destination
Storing signatures
f4f290da2ecc190609189ea43003ba32d0f740f4a8e10219d5fa3c252481bd40

[cloud-user@new-rhel-8-4 ~]$ sudo podman images
REPOSITORY                                   TAG     IMAGE ID      CREATED         SIZE
docker.io/henrywangxf/rhel-edge              latest  f4f290da2ecc  16 minutes ago  1.25 GB
quay.io/xiaofwan/rhel-edge                   latest  f4f290da2ecc  16 minutes ago  1.25 GB

OpenStack broken again. All else is good.

authors: gicmo henrywang teg


text:
Update python versions employed in CI/CD pipelines

Issue description / feature objectives
Update workflows:
python-push.yml
python-test.yml
Revise python versions:

Add: 3.11, 3.10
Keep: 3.9
Drop 3.8

Caveats / Assumptions
N/A
Completion Criteria
All test cases pass.

Fixed by #1533.

repo: oscal-compass/compliance-trestle


text:
Speaker Post Needed for CNCF Gandhinagar - 15th Oct 2023

Goal:
To Create the Poster For CNCF Gandhinagar Speaker post
Info:
Event name: Cloud Native Gandhinagar <> Open Source Edition
Venue: Lucent Innovation
Time: 10.00am to 1.00pm
Date: 15th Oct 2023
Info : Speaker 1

Name : Neel Shah

Title : Kickstart your journey with CNCF Glossary and Kubernetes Projects

Speaker 2

Name : Kaivalya Shah

Title : Getting started with Gitops and ArgoCD

Good work @URMIT18 🚀

repo: oscfcommunity/OpenDesign


text:
Power BI Connector Sample Improvements

Converted API endpoint path to optional parameter so that OAuth token is reused
Removed Refresh OAuth signature as no refresh token is provided by the Authorization Code + PKCE flow
Added optional timeout parameter for large / long queries
Removed Json.Document function call so that form=csv can be used in API

seems ok, but  All of the checks fail

repo: osisoft/OSI-Samples-OCS


text:
PyOsmium on Windows

In theory PyOsmium should work on Windows, but I don't think anybody ever tried.
@alex85k Do you want to try this out and maybe get an Appveyor config going?

I have tried, it needs some patches on library-finding (or hardcoding), dininot manage to make it use my static boost for now.

Managed to fix libraries (mostly hardcoding for now), it installs but does not find any classes when running:
TypeError: No Python class registered for C++ class class osmium::Way

Maybe I'll have more luck with python3, not 2.7.

The "No Python class registered" was because of static boost libs (static boost.python3 gave the same error). Fixed whe I built it with dynamically-licked boost.
Now it compiles but wants dll in paths and fails one test.
Will create a WIP pull-request to share.

@springmeyer Can you activate Appveyor for this repository so that we can tests the work from @alex85k ?

Yes, now working on devpack...

Added: https://ci.appveyor.com/project/Mapbox/pyosmium

authors: alex85k joto springmeyer

repo: osmcode/pyosmium


text:
Edit in iD does not select

Expected behavior: When I 'Edit in iD' the editor should have the object selected.
Observed behavior: For this overpass challenge iD opens without the object being selected.
This issue is similar to #78 but as the tasks are retrieved from an overpass result, the ID should be available.

Thanks for reporting, this will be fixed in the next release.

Will it be possible to add a specific property (e.g. @id=n{dddd}) in manually uploaded GeoJSON (use case #78) that will be interpreted as OSM-ID?

Fixed in v3.4.2
And yes, @id properties in the GeoJSON are already supported and interpreted as OSM ids. They typically are formatted as node/12345789.

authors: hbruch nrotstan


text:
Broken stats

the to-fix stats is broken,
,
I think the d3 library is not working, any idea?
cc. @aaronlidman @tristen

Included d3 and rebuilt: https://github.com/osmlab/to-fix/commit/0cf90ffb235563d671456402c2d368f37631c482
Not sure why it worked before without d3, weird.

repo: osmlab/to-fix


text:
chore: enable markdown linter

Closes: #1210
What is the purpose of the change
Enabled markdown linter.

GitHub Action: https://github.com/github/super-linter
Linter: https://github.com/igorshubovych/markdownlint-cli#readme

Brief Changelog

enabled linter
Fixed all automatic issues
Fixed some manual issues
disabled files with too many issues that cannot be fixed automatically

Testing and Verifying
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
Documentation and Release Note

Does this pull request introduce a new feature or user-facing behavior changes? no
Is a relevant changelog entry added to the Unreleased section in CHANGELOG.md? no
How is the feature or change documented? not applicable

Codecov Report

Merging #1478 (f49061a) into main (f6275dc) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1478   +/-   ##
=======================================
  Coverage   19.49%   19.49%
=======================================
  Files         231      231
  Lines       31503    31503
=======================================
  Hits         6140     6140
  Misses      24237    24237
  Partials     1126     1126

Continue to review full report at Codecov.

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

repo: osmosis-labs/osmosis


text:
[CL Incentives] Implement setIncentiveRecords and getIncentiveRecords

Closes: #4274
What is the purpose of the change
This PR implements a more portable version of state reads/writes relating to incentive records with the primary goal of making it simpler to abstract this logic into a separate module in the future. Specifically, it changes incentive records to work based off of pool Ids instead of as a field under pool objects.
Brief Changelog

Implement set/get functions for incentive records that do not depend on pool objects
Remove the PoolIncentives field from CL pools

Testing and Verifying

The new functions/logic are tested in incentives_test.go

Documentation and Release Note

Does this pull request introduce a new feature or user-facing behavior changes? (no)
Is a relevant changelog entry added to the Unreleased section in CHANGELOG.md? (no)
How is the feature or change documented? (not documented)

Note that this PR was approved in #4283 but preemptively merged. Should merge this directly to main after #4231 is merged.


text:
fix: replace np.int alias with builtin int

This changes the np.int alias of the Python builtin int type as the alias was deprecated in numpy version 1.20.0 and lead to an AttributeError starting with version 1.24.0.
This should fix issue #104

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@marvinvanaalst, and sorry for the delay in getting to this, and thanks a bunch for the PR.
2 things before we merge this is:

Can you undo the change in pyproject.toml regarding the black configuration? (since its outside the scope of this PR).
It looks to me like the alias for np.int pointing to int has been in numpy since version 1.7, the current min. version of numpy for osqp. So while I agree that np.int should be replaced with int, there's no need to bump up the required numpy version. If you can change that back in requirements.txt that would be the right thing to do.

@marvinvanaalst - after approving PR #109 with this fix, I'm closing this PR. Release v0.6.2.post9 of osqp incorporates these changes. Thanks for bringing this to our attention!

repo: osqp/osqp-python


text:
setup.py: Remove outdated setup_requires

This has been superseded by the declarations in pyproject.toml. Removing it will suppress the message _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated. upon installing the package.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant mkoeppe

repo: osqp/qdldl-python


text:
Wrong package manager test

In the test case analyzer/src/test/kotlin/PackageManagerTest.kt the cargo-specific file 'Cargo-.tml' is assigned to 'bundler' but it should probably read 'cargo'
in lines:

39: 'bundler/Cargo.toml' should read 'cargo/Cargo.toml'
95: 'bundler/Cargo.toml' should read 'cargo/Cargo.toml'

Thanks for spotting, I've filed a PR to fix this.

authors: rbieniek sschuberth

repo: oss-review-toolkit/ort


text:
Error while gradle  install "rescripts' is not recognized as an internal or external command"

Hello,
I am trying to install ORT into my Machine but my build is failed at 95%  :(
yarn --version 1.22.18
npm --version 8.5.5
node --version 16.15.0
Gradle --v  7.4.2
java --version
java 11.0.15.1 2022-04-22 LTS
Java(TM) SE Runtime Environment 18.9 (build 11.0.15.1+2-LTS-10)
Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.15.1+2-LTS-10, mixed mode)
ERROR

FYI, we had a similar report on Slack when building on Windows by @bennati, who then concluded

It worked on a fresh windows user, possibly a previous installation of node.js somehow messed with this installation

Hello Thomas,
still have same issue.
when I run build after delete yarn.lock and node_moules
 yarn build
yarn run v1.22.18
error Couldn't find a package.json file in "C:\\code-challenge\\ort"
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

I delete whole ort repository and clone repo again.  and I got same error
> Task :kotlinNodeJsSetup
Setting up Node.js / NPM in 'C:\Users\jk87829\.gradle\nodejs\node-v16.13.0-win-x64'...

> Task :kotlinYarnSetup
Setting up Yarn in 'C:\Users\jk87829\.gradle\yarn\yarn-v1.22.10'...

> Task :reporter-web-app:yarnBuild FAILED
yarn run v1.22.10
$ rescripts build
'rescripts' is not recognized as an internal or external command,
operable program or batch file.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':reporter-web-app:yarnBuild'.
> Process 'command 'C:\Users\jk87829\.gradle\nodejs\node-v16.13.0-win-x64\node.exe'' finished with non-zero exit value

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 5m 59s
54 actionable tasks: 52 executed, 2 from cache

FYI, we had a similar report on Slack when building on Windows by @bennati, who then concluded

It worked on a fresh windows user, possibly a previous installation of node.js somehow messed with this installation

I tried on my personal laptop I have the same error

@karippery would you mind giving https://github.com/oss-review-toolkit/ort/pull/5659 a try to see if that also works around this issue of yours?

I'm reopening this as I now believe to have found the real root case. Watch this space 😃

I didn't find the solution for this issue.  that's why I used gitlab version of ORT

I didn't find the solution for this issue. that's why I used gitlab version of ORT

See the linked PR https://github.com/oss-review-toolkit/ort/pull/5814 for the solution.

authors: karippery sschuberth


text:
Move application of Binary Artifacts Gradle Wrapper Action exception into checks/evaluation/

Is your feature request related to a problem? Please describe.
This is where the feature should be implemented so that log messages can reflect the exception, rather than having it be an opaque process for users. It would mean that raw/binary_artifacts returns the expected files, without special exclusions.
Describe the solution you'd like
Move the exception to checks/evaluation/binary_artifacts.go.

Create log messages reflecting the status of the exception so that users can see details

Describe alternatives you've considered
Current stopgap implementation is opaque and solves the immediate issue by having raw/binary_artifacts exclude gradle-wrapper.jar files from being returned when the Action is detected.
Additional context
First mentioned in #2039.

Completed as part of #3508

authors: ethanent spencerschrock

repo: ossf/scorecard


text:
流列表有多条记录但客户端列表无记录导致无法正常拉流

** 流列表有多条记录但客户端列表无记录导致无法正常拉流**

SRS Version(版本): 4.0

SRS Config(配置):

listen 1935;
max_connections 1000;
srs_log_tank file;
srs_log_file ./conf/log/srs.log;
daemon on;
http_api {
    enabled on;
    listen 1985;
    raw_api {
        enabled on;
        allow_reload on;
        allow_query on;
        allow_update on;
    }
    https {
        enabled on;
        listen 443;
        key ./conf/fan_***.com_NGINX.key;
        cert ./conf/fan_***.com_NGINX.crt;
    }
}
http_server {
    enabled on;
    listen 8080;
    dir ./objs/nginx/html;
    https {
        enabled on;
        listen 1990;
        key ./conf/fan_***.com_NGINX.key;
        cert ./conf/fan_***.com_NGINX.crt;
    }
}
stats {
    network 0;
    disk sda sdb xvda xvdb vda;
}
rtc_server {
    enabled on;
    listen 8000;
    candidate ***.***.***.221;
}
vhost __defaultVhost__ {
	http_hooks {
        enabled         on;
        on_connect      https://***.***.com/hjkj-video-center/srsCallback/onConnectCallBack;
        on_close        https://***.***.com/hjkj-video-center/srsCallback/onCloseCallBack;
        on_publish      https://***.***.com/hjkj-video-center/srsCallback/onPublishCallBack;
        on_unpublish    https://******.com/hjkj-video-center/srsCallback/onUnPublishCallBack;
        on_play         https://***.***.com/hjkj-video-center/srsCallback/onPlayCallBack;
        on_stop         https://***.***.com/hjkj-video-center/srsCallback/onStopCallBack;
		on_dvr          https://***.***.com/hjkj-video-center/srsCallback/onDvrCallBack;
    }
    tcp_nodelay on;
    min_latency on;
    dvr {
        enabled on;
        dvr_path ./objs/nginx/html/record/[app]/[stream]/[2006]/[01]/[02]/[15]:[04]:[05].mp4;
        dvr_plan session;
        dvr_duration 10;
        dvr_wait_keyframe on;
        dvr_apply all;
    }
    hls {
        enabled on;
    }
    rtc {
        enabled on;
        bframe discard;
        rtc_to_rtmp on;
		rtmp_to_rtc on;
		stun_timeout 3;
		nack on;
		twcc on;
    }
    http_remux {
        enabled on;
        mount [vhost]/[app]/[stream].flv;
    }
    play {
        gop_cache off;
        queue_length 10;
        mw_latency 100;
    }
    publish {
        mr off;
    }
}

Replay(重现)

Please describe how to replay the bug? (重现Bug的步骤)

某一段时间内流列表有多条记录(这些记录均为视频通话流)，但客户端列表为空->通过SRS控制台观察
此时无法正常拉在流列表中存在的流，需要重启srs后才正常
截图见：https://hengine-public.huanjianit.com/Image/project/MIM/test/20220815092949.png

Expect(期望行为)

流列表能随着客户端的下线而销毁相应的流

Fixed in 5.0, 重复问题会删除。

authors: starise-wg winlinvip

repo: ossrs/srs


text:
Feature/set asan report path

Asan: support set asan report log path by conf

不建议给asan使用单独的日志，而是应该直接写入到SRS的日志中，可以参考FFmpeg API和SRT的日志的做法。
这样用户不需要单独再找日志文件。

authors: chen-guanghua winlinvip


text:
I created a Discord server.

I created an OSSU Discord server. The link is https://discord.gg/4PDbvp9
The idea is students can help each other/work together/discuss problems. This is the aspect that we're missing compared to traditional education, so maybe it will fill the gap!

Always happy to see contributors jumping in with solutions to problems!
At the same time, it would be great to ensure that we don't replicate old problems. One issue that OSSU has had in the past is to have a multiple lightly populated pages on many different platforms. You can read some of the later posts in this issue for some examples:
https://github.com/ossu/computer-science/issues/495
What can OSSU do to ensure that a Discord server is improving the experience over the current tools?

I understand that it's been discussed. We can do it as an experiment. If it works and lots of people use it, great, we keep it and maintain it. If it's not used, we shut it down.
I think it does fill a gap though, GitHub has an issues section, but lots of discussion points don't fit into that.

In terms of improving the experience for students, it'll only be useful if it gets a large population. We could advertise it on the curriculum page. Something along the lines of:
"We are trying to improve student community engagement, so we've trialing a Discord at https://discord.gg/4PDbvp9. Join the conversation!"

You're not aware of the Gitter are you

I wasn't, no. It's not listed anywhere except in closed issues. I'm happy to close up the Discord. But we should promote the Gitter on the front page with a direct link and explanation. New students shouldn't have to search in closed issues to find it.

Oh sorry, CTRL-F didn't find it. There is a small link at the bottom. I think it should be much though! And near the top!

Outcome of the issue is PR 663
Hopefully this will mean more students connect with the OSSU community!

authors: Alaharon123 waciumawanjohi xxylem

repo: ossu/computer-science


text:
chore: address deprecations caused by updating packages

Describe your changes
RFC. This is the minimal required to get it into a working state. See: https://fastapi.tiangolo.com/advanced/events/#lifespan
Breaking changes spotted:

https://github.com/tiangolo/fastapi/releases/tag/0.106.0
https://github.com/tiangolo/fastapi/releases/tag/0.93.0
https://www.starlette.io/release-notes/#0260
https://www.starlette.io/release-notes/#0340
https://github.com/redis/redis-py/releases/tag/v5.0.1
akatsuki-pp-py version bump. Did we historically handle pp system versioning in some way? @cmyui

As a side effect, we now should technically support Python 3.12
Other things of note:
We may support Pytest 8 soon once pytest-asyncio v23.5 is out of alpha. https://github.com/pytest-dev/pytest-asyncio/issues/737#issuecomment-1930632667 done in #571
Related Issues / Projects
Depends on #568
Checklist

[x] I've manually tested my code

+1 👍🏻

authors: NiceAesth cmyui


text:
Trouble with prettier (Parsing error: import can only be used in import() or import.meta)

Before You File a Bug Report Please Confirm You Have Done The Following...

[X] I have tried restarting my IDE and the issue persists.
[X] I have updated to the latest version of the packages.

What version of ESLint are you using?
8.50.0
What version of eslint-plugin-astro are you using?
0.29.0
What did you do?

Configuration
{
  "extends": [
    "planet"
  ],
  "parserOptions": {
    "ecmaVersion": "latest",
    "sourceType": "module"
  },
  "rules": {
    "import/named": "off",
    "import/default": "off",
    "import/no-unresolved": [
      "error",
      {
        "ignore": [
          "astro:content",
          "@astrojs/*"
        ]
      }
    ]
  },
  "overrides": [
    {
      "files": [
        "*.astro"
      ],
      "extends": [
        "plugin:astro/recommended"
      ]
    },
    {
      "files": [
        "*.jsx"
      ],
      "extends": [
        "planet/react"
      ],
      "rules": {
        "import/named": "off"
      }
    },
    {
      "files": [
        "*.mdx"
      ],
      "extends": [
        "plugin:mdx/recommended",
        "planet/react"
      ]
    }
  ]
}

---
import '../styles/global.css';

const {frontmatter} = Astro.props;
const title = (frontmatter && frontmatter.title) || Astro.props.title;
---

    <meta charset="utf-8" />
    <meta name="viewport" content="width=device-width" />
    <title>{title}</title>

@planet/maps

<a href={`${import.meta.env.BASE_URL}examples/`}>examples

{title}

    <slot />

What did you expect to happen?
I upgraded from Astro 2 to 3 (see https://github.com/planetlabs/maps/pull/278/files), and expected the linter configuration to continue working.
What actually happened?
# npx eslint site/src/layouts/BaseLayout.astro

/Users/tim/projects/maps/site/src/layouts/BaseLayout.astro
  2:2  error  Parsing error: `import` can only be used in `import()` or `import.meta`  prettier/prettier

Link to Minimal Reproducible Example
https://github.com/planetlabs/maps/pull/278/files
Additional comments
I know this is not a minimal preproduction, I'll see if I can create one.  But before upgrading to Astro 3, the linter configuration was working using this plugin together with eslint-plugin-prettier.  After upgrading to Astro 3, the linter can no longer parse *.astro files.
I imagine this has to do with the parser or parserOptions that are being used, but I cannot figure out a combination that works.  So far, the only solution I have found is to disable the prettier/prettier rules when using this eslint-plugin-astro plugin.
I see that the readme suggests turning the prettier/prettier rules off: https://github.com/ota-meshi/eslint-plugin-astro/blob/v0.29.0/README.md?plain=1#L165-L172
Is anyone successfully using this plugin together with Prettier and Astro 3?

The prettier/prettier rule has nothing to do with this plugin. Perhaps you should open the issue in another repository.
The branch you shared doesn't seem to exist anymore and I couldn't debug it.

authors: ota-meshi tschaub

repo: ota-meshi/eslint-plugin-astro


text:
Unsovlable Dependency Tree

    "stylelint": "^16.0.0",
    "stylelint-config-recommended": "^14.0.0",
    "stylelint-config-recommended-vue": "^1.6.0",
    "stylelint-config-standard": "^35.0.0",
    "stylelint-config-standard-scss": "^12.0.0",

± |stylelint-16 U:1 ✗| → yarn
yarn install v1.22.21
warning ../package.json: No license field
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
warning "stylelint-config-recommended-vue > stylelint-config-recommended@13.0.0" has incorrect peer dependency "stylelint@^15.10.0".
[4/4] 🔨  Building fresh packages...
success Saved lockfile.
✨  Done in 0.75s.

There's no way to solve this. If I put it recommended stylelint-config-recommended on v13 then i can't use stylelint 16.
yarn install v1.22.21
warning ../package.json: No license field
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
warning " > stylelint-config-recommended@13.0.0" has incorrect peer dependency "stylelint@^15.10.0".
[4/4] 🔨  Building fresh packages...
success Saved lockfile.
✨  Done in 0.72s.

But if I downgrade to v15 I get:
warning " > stylelint-config-standard@35.0.0" has incorrect peer dependency "stylelint@^16.0.0".
warning "stylelint-config-standard > stylelint-config-recommended@14.0.0" has incorrect peer dependency "stylelint@^16.0.0".
warning " > stylelint-config-standard-scss@12.0.0" has incorrect peer dependency "stylelint@^16.0.2".
warning "stylelint-config-standard-scss > stylelint-config-recommended-scss@14.0.0" has incorrect peer dependency "stylelint@^16.0.2".
warning " > stylelint-scss@6.0.0" has incorrect peer dependency "stylelint@^16.0.2".

There's no solve unless you support recommended @14 i think.
Otherwise the only working version of this is:
    "stylelint": "^15.0.0",
    "stylelint-config-recommended": "^13.0.0",
    "stylelint-config-recommended-vue": "^1.5.0",
    "stylelint-config-standard": "^33.0.0",
    "stylelint-config-standard-scss": "^10.0.0",
    "stylelint-scss": "^5.0.0",
    ```

duplicate of #69

authors: johnnyshankman ota-meshi


text:
Monitor all / filter repositories in organization

Is your feature request related to a problem? Please describe.
The dashboard is very handy for monitoring workflow success and failures however the specification of repositories can become quite unruly if an organization has many repositories.
Describe the solution you'd like
Provide the ability to monitor all repositories or allow wildcard matching.
Example: I may have a template repository and client repositories are created from this template with the same naming convention such as:
Test-Repo-Client-A
Test-Repo-Client-B
docker run \
  -p <host machine port>:8080 \
  -e REPO_OWNER_NAME=<organization/username> \
  -e REPO_NAMES="Test-Repo-Client*" \
  -it ottoopensource/gitactionboard:<docker tag>

Example: Monitor all current and future repositories within an organization:
docker run \
 -p <host machine port>:8080 \
 -e REPO_OWNER_NAME=<organization/username> \
 -e REPO_NAMES="*" \
 -it ottoopensource/gitactionboard:<docker tag>

This helps in case there are other contributors creating repositories at random which requires constant updating of the environment variables.
Describe alternatives you've considered
None that I can think of
Additional context
N/A

Hi @data-tangles, I have following questions to understand the idea better

When the service should fetch the new repos from github ?
What's your view point of how to handle the archived repos?

My opinion

When the service should fetch the new repos from github ?
When you perform a docker run i.e. during startup,

What's your view point of how to handle the archived repos?
Ignore archived repos by default.

repo: otto-de/gitactionboard


text:
Building Windows exe fails

Building Windows exe (package.sh -w) currently fails with ab error that is caused by the app icon format. See PR #16 for fix.

@redvox you might want to update the README if you are not accepting issues and pull requests. At least some kind of feedback is highly appreciated.

repo: otto-de/logsmith


text:
write meaningful error message

In systems with multiple models and/or multiple model locations it's often not obvious which of the models / model locations is missing something. This gives a more meaningful error message.

Change was applied to develop branch, thank you!

authors: alattner yv

repo: ottogroup/palladium


text:
Document UI/UX Design Process

Create documentation detailing design philosophy and research conducted in UI/UX design stage (tasks 1 and 2).
Definition of Done: Documentation detailing tasks 1 and 2 exists.

Consider adding visual examples  for design tasks. This can help visualize the end goals and ensure everyone's on the same page.

authors: ferialna rockandfire


text:
Link to best Typescript/Node.js Zora SDK repo?

What is the link to the best Typescript/Node.js Zora SDK repo?

This one is the current SDK: https://docs.zora.co/protocol-sdk/introduction

authors: iainnash roschler

repo: ourzora/zora-protocol


text:
PANIC from mysql-datadir-available-space

When there are errors running mysql-datadir-available-space it panics
[martini] Started GET /api/mysql-datadir-available-space for 192.168.57.200:48631
[martini] PANIC: runtime error: index out of range
/usr/lib/golang/src/runtime/panic.go:423 (0x429d59)
        gopanic: reflectcall(nil, unsafe.Pointer(d.fn), deferArgs(d), uint32(d.siz), uint32(d.siz))
/usr/lib/golang/src/runtime/panic.go:12 (0x428239)
        panicindex: panic(indexError)
/home/vagrant/go/src/github.com/outbrain/orchestrator-agent/src/github.com/outbrain/orchestrator-agent/osagent/osagent.go:319 (0x5805aa)
        GetMySQLDataDirAvailableDiskSpace: result, err := strconv.ParseInt(lineTokens[4], 10, 0)
/home/vagrant/go/src/github.com/outbrain/orchestrator-agent/src/github.com/outbrain/orchestrator-agent/http/api.go:360 (0x5a1ad1)
        (*HttpAPI).GetMySQLDataDirAvailableDiskSpace: output, err := osagent.GetMySQLDataDirAvailableDiskSpace()
/home/vagrant/go/src/github.com/outbrain/orchestrator-agent/src/github.com/outbrain/orchestrator-agent/http/api.go:502 (0x5a7a28)
        (*HttpAPI).GetMySQLDataDirAvailableDiskSpace-fm: m.Get("/api/mysql-datadir-available-space", this.GetMySQLDataDirAvailableDiskSpace)
/usr/lib/golang/src/runtime/asm_amd64.s:437 (0x459d8e)
        call32: CALLFN(·call32, 32)
/usr/lib/golang/src/reflect/value.go:432 (0x5ce3da)
        Value.call: call(frametype, fn, args, uint32(frametype.size), uint32(retOffset))
/usr/lib/golang/src/reflect/value.go:300 (0x5cd0a1)
        Value.Call: return v.call("Call", in)
/home/vagrant/go/src/github.com/codegangsta/inject/inject.go:102 (0x68e7d2)
        (*injector).Invoke: return reflect.ValueOf(f).Call(in), nil
<autogenerated>:30 (0x591aed)
/home/vagrant/go/src/github.com/go-martini/martini/router.go:408 (0x58e3a7)
        (*routeContext).run: vals, err := r.Invoke(handler)
/home/vagrant/go/src/github.com/go-martini/martini/router.go:285 (0x58d4f9)
        (*route).Handle: context.run()
/home/vagrant/go/src/github.com/go-martini/martini/router.go:132 (0x58c0b4)
        (*router).Handle: bestRoute.Handle(context, res)
/home/vagrant/go/src/github.com/go-martini/martini/martini.go:125 (0x58f314)
        (Router).Handle-fm: m.Action(r.Handle)
/usr/lib/golang/src/runtime/asm_amd64.s:438 (0x459e2e)
        call64: CALLFN(·call64, 64)
/usr/lib/golang/src/reflect/value.go:432 (0x5ce3da)
        Value.call: call(frametype, fn, args, uint32(frametype.size), uint32(retOffset))
/usr/lib/golang/src/reflect/value.go:300 (0x5cd0a1)
        Value.Call: return v.call("Call", in)
/home/vagrant/go/src/github.com/codegangsta/inject/inject.go:102 (0x68e7d2)
        (*injector).Invoke: return reflect.ValueOf(f).Call(in), nil
/home/vagrant/go/src/github.com/go-martini/martini/martini.go:179 (0x58a0ee)
        (*context).run: _, err := c.Invoke(c.handler())
/home/vagrant/go/src/github.com/go-martini/martini/martini.go:170 (0x589ffc)
        (*context).Next: c.run()
/home/vagrant/go/src/github.com/martini-contrib/gzip/gzip.go:40 (0x596aed)
        glob.func1: c.Next()
/home/vagrant/go/src/github.com/martini-contrib/gzip/gzip.go:56 (0x596bc1)
        All.func1: serveGzip(w, r, c, opt)
/usr/lib/golang/src/runtime/asm_amd64.s:438 (0x459e2e)
        call64: CALLFN(·call64, 64)
/usr/lib/golang/src/reflect/value.go:432 (0x5ce3da)
        Value.call: call(frametype, fn, args, uint32(frametype.size), uint32(retOffset))
/usr/lib/golang/src/reflect/value.go:300 (0x5cd0a1)
        Value.Call: return v.call("Call", in)
/home/vagrant/go/src/github.com/codegangsta/inject/inject.go:102 (0x68e7d2)
        (*injector).Invoke: return reflect.ValueOf(f).Call(in), nil
/home/vagrant/go/src/github.com/go-martini/martini/martini.go:179 (0x58a0ee)
        (*context).run: _, err := c.Invoke(c.handler())
/home/vagrant/go/src/github.com/go-martini/martini/martini.go:170 (0x589ffc)
        (*context).Next: c.run()
/home/vagrant/go/src/github.com/go-martini/martini/recovery.go:142 (0x58fa02)
        Recovery.func1: c.Next()
/usr/lib/golang/src/runtime/asm_amd64.s:437 (0x459d8e)
        call32: CALLFN(·call32, 32)
/usr/lib/golang/src/reflect/value.go:432 (0x5ce3da)
        Value.call: call(frametype, fn, args, uint32(frametype.size), uint32(retOffset))
/usr/lib/golang/src/reflect/value.go:300 (0x5cd0a1)
        Value.Call: return v.call("Call", in)
/home/vagrant/go/src/github.com/codegangsta/inject/inject.go:102 (0x68e7d2)
        (*injector).Invoke: return reflect.ValueOf(f).Call(in), nil
/home/vagrant/go/src/github.com/go-martini/martini/martini.go:179 (0x58a0ee)
        (*context).run: _, err := c.Invoke(c.handler())
/home/vagrant/go/src/github.com/go-martini/martini/martini.go:170 (0x589ffc)
        (*context).Next: c.run()
/home/vagrant/go/src/github.com/go-martini/martini/logger.go:25 (0x58ef52)
        Logger.func1: c.Next()
/usr/lib/golang/src/runtime/asm_amd64.s:438 (0x459e2e)
        call64: CALLFN(·call64, 64)
/usr/lib/golang/src/reflect/value.go:432 (0x5ce3da)
        Value.call: call(frametype, fn, args, uint32(frametype.size), uint32(retOffset))
/usr/lib/golang/src/reflect/value.go:300 (0x5cd0a1)
        Value.Call: return v.call("Call", in)
/home/vagrant/go/src/github.com/codegangsta/inject/inject.go:102 (0x68e7d2)
        (*injector).Invoke: return reflect.ValueOf(f).Call(in), nil
/home/vagrant/go/src/github.com/go-martini/martini/martini.go:179 (0x58a0ee)
        (*context).run: _, err := c.Invoke(c.handler())
/home/vagrant/go/src/github.com/go-martini/martini/martini.go:75 (0x588c2d)
        (*Martini).ServeHTTP: m.createContext(res, req).run()
/usr/lib/golang/src/net/http/server.go:1862 (0x55e6ae)
        serverHandler.ServeHTTP: handler.ServeHTTP(rw, req)
/usr/lib/golang/src/net/http/server.go:1361 (0x55be2e)
        (*conn).serve: serverHandler{c.server}.ServeHTTP(w, w.req)
/usr/lib/golang/src/runtime/asm_amd64.s:1696 (0x45c0b1)
        goexit: BYTE    $0x90   // NOP

Closed by https://github.com/outbrain/orchestrator-agent/pull/16

authors: jcesario shlomi-noach

repo: outbrain/orchestrator-agent


text:
Move Nova::script()/Nova::style() methods to NPMServiceProvider

The correct place to attach the relevant JS/CSS files for a tool is in the ServiceProviders boot() method
Using the latest Nova, the tools CSS and JS files were not loading since they were being initialised in the wrong place.
This PR fixes issue #166

Thanks a ton! :)

authors: Tarpsvo matthewjumpsoffbuildings


text:
Nova 5.x compatibility

Hello,
Do you have any plans to support Nova 5.x?
Thanks in advance.

thanks @hossammonir I can see you also forked some other plugins I have issues with :) Good luck with that!

Test it out. :)

authors: Tarpsvo vbezruchkin


text:
Update sbt to 1.9.6

About this PR
📦 Updates org.scala-sbt:sbt from 1.6.2 to 1.9.6
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-sbt", artifactId = "sbt" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scala-sbt", artifactId = "sbt" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, version-scheme:early-semver, commit-count:1

Superseded by #113.

repo: outr/perfolation


text:
Separate state mappings for different issue types

When experimenting with different workflows for different issue types in my local Jira setup, I noticed that it is not possible to change the type of an issue to a type that belongs to a different workflow. This makes it a lot easier!

I've left in the skipped BoardManagerTest.testChangeIssueTypeWithIssueTypeStateLinkOverrides() as a reminder with a comment that changing an issue's type to a type that has a different workflow (and thus potential state mapping our end) is not possible.

repo: overbaard/overbaard


text:
Convolution perf model generalizatoin

cuDNN only optimizes for certain sizes, which makes our conv performance model hard to generalize if the microbenchmark dataset only covers limited (but still huge!) number of sizes and/or only for forward. Conversely, performance model trained for cuBLAS GEMM generalize well, for both forward and backward. We want to explore for an economical way to do the microbenchmark for conv, so that we can train much less sizes and/or only for forward to achieve good prediction, generalization, and coverage.

Not urgent. Close for now.


text:
lib/datautils: groupby_agg on string column with missing values introduces 0

While running the tests with the next version of pandas, I ran into this case:
https://github.com/owid/etl/blob/f9e2f93e70e1ba38210cc51f900d1f92475ca45d/lib/datautils/tests/test_dataframes.py#L309-L329
where the expected result df_out column "value_02" is a mixed integer/string column, because of a zero being introduced through the groupby's sum on a group with only missing values.
While being tested as the expected result, I am wondering if this is the intended or desired behaviour to get a 0 in there (I assume this is not the case). Or whether this is just from using some dummy data in the test, and not something you encounter or want on the actual datasets? (for example, I don't know if you actually ever use the "sum" operation on a string column in practice)
The reason I ran into this case is because this test is failing with pandas' future string dtype enabled. It is failing because the result now no longer has an integer 0 but a string "0" (and hence the assert equals(..) failed), which I think is even worse (so I opened an upstream issue to fix this in pandas: https://github.com/pandas-dev/pandas/issues/60229, thanks to running your test suite!)

@pabloarosado will take a quick look, it may not be trivial for us to make a change to behaviour since it affects a bunch of our steps.

It took me a while to understand what’s going on. Fortunately, this is dummy data and isn’t very representative of our typical use case. In fact, I’d say running sum on strings would generally be considered bad practice for us.
I’m closing this for now. If it gets fixed upstream, we’ll address it on our side. Thanks, Joris!

authors: Marigold jorisvandenbossche larsyencken

repo: owid/etl


text:
decomposedfs requires uuid length space ids

Set "OCIS_SYSTEM_USER_ID": "some-system-user-id" and "OCIS_ADMIN_USER_ID": "some-admin-user-id", login will work, but listing the personal space produces a panic:
goroutine 1531 [running]:
runtime/debug.Stack()
	/usr/local/go/src/runtime/debug/stack.go:24 +0x7a
runtime/debug.PrintStack()
	/usr/local/go/src/runtime/debug/stack.go:16 +0x19
github.com/cs3org/reva/v2/internal/grpc/interceptors/recovery.recoveryFunc({0x5f653f8, 0xc004984450}, {0x4a33060, 0xc0043ddd40})
	/home/vscode/repositories/reva/internal/grpc/interceptors/recovery/recovery.go:48 +0x51
github.com/grpc-ecosystem/go-grpc-middleware/recovery.recoverFrom({0x5f653f8, 0xc004984450}, {0x4a33060, 0xc0043ddd40}, 0x5c50b40)
	/home/vscode/go/pkg/mod/github.com/grpc-ecosystem/go-grpc-middleware@v1.3.0/recovery/interceptors.go:61 +0x8f
github.com/grpc-ecosystem/go-grpc-middleware/recovery.UnaryServerInterceptor.func1.1()
	/home/vscode/go/pkg/mod/github.com/grpc-ecosystem/go-grpc-middleware@v1.3.0/recovery/interceptors.go:29 +0xaa
panic({0x4a33060, 0xc0043ddd40})
	/usr/local/go/src/runtime/panic.go:844 +0x25a
github.com/cs3org/reva/v2/pkg/storage/utils/decomposedfs.readSpaceAndNodeFromSpaceTypeLink({0xc00453e840, 0x3a})
	/home/vscode/repositories/reva/pkg/storage/utils/decomposedfs/spaces.go:228 +0x35a
github.com/cs3org/reva/v2/pkg/storage/utils/decomposedfs.(*Decomposedfs).ListStorageSpaces(0xc000f44a00, {0x5f653f8, 0xc004984720}, {0xc000a7e4e0, 0x1, 0x1}, 0x0)
	/home/vscode/repositories/reva/pkg/storage/utils/decomposedfs/spaces.go:341 +0xc3c
github.com/cs3org/reva/v2/internal/grpc/services/storageprovider.(*service).ListStorageSpaces(0xc000f44a50, {0x5f653f8, 0xc004984720}, 0xc00495d080)
	/home/vscode/repositories/reva/internal/grpc/services/storageprovider/storageprovider.go:524 +0x3fc
github.com/cs3org/go-cs3apis/cs3/storage/provider/v1beta1._ProviderAPI_ListStorageSpaces_Handler.func1({0x5f653f8, 0xc004984720}, {0x4a6be80, 0xc00495d080})
	/home/vscode/go/pkg/mod/github.com/cs3org/go-cs3apis@v0.0.0-20220412090512-93c5918b4bde/cs3/storage/provider/v1beta1/provider_api.pb.go:6103 +0xfd
go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc.UnaryServerInterceptor.func1({0x5f653f8, 0xc004984720}, {0x4a6be80, 0xc00495d080}, 0xc004964860, 0xc0049689d8)

where /home/vscode/repositories/reva/pkg/storage/utils/decomposedfs/spaces.go:228 expects spaceid and nodeid of uuid length:
	if link[0:10] != "....spaces" || link[46:51] != "nodes" {
		return "", "", errtypes.InternalError("malformed link")
	}

fix in https://github.com/cs3org/reva/pull/2854

repo: owncloud/ocis


text:
How to contribute to first time or beginners

trying to contribute but not sure what the next step is?

@sunnycal ,
You can create a PR from any HackerRank problem which you resolved and commit the solutions in the HankerRank folder. Thanks
cc. @ows-ali

authors: seancyw sunnycal

repo: ows-ali/Hacktoberfest


text:
connection errors

Hi, love the new approach :) It works in general, however, I get
Local IP address: 192.168.178.26
2023/06/26 18:24:53 http: TLS handshake error from 192.168.178.20:53025: EOF
2023/06/26 18:24:54 http: TLS handshake error from 192.168.178.20:53026: EOF
^C
reMarkable: ~/ ./goMarkableStream
Local IP address: 10.11.99.1
Local IP address: 192.168.178.26
2023/06/26 18:27:48 http: TLS handshake error from 10.11.99.2:53059: EOF
2023/06/26 18:27:48 http: TLS handshake error from 10.11.99.2:53060: EOF
2023/06/26 18:27:48 http: TLS handshake error from 10.11.99.2:53061: EOF

And it's repeatedly asking for credentials and shows "waiting for remarkable".
That's via both wifi and usb.
goMS is v 0.8.2, your binary, browser is Safari 16.5.1 on macOS 12.6.7

edit: works fine with Firefox... so, I can live with that.

I will have a look if I have time.
Meanwhile, you can disable password authentication with -unsafe and/or disable HTTPS. It should do the trick (it does for iOS)

repo: owulveryck/goMarkableStream


text:
Change to use self-contained lld by default in rustup nightly artifacts breaks native linking

https://github.com/rust-lang/rust/issues/71515#issuecomment-2116969162 mentions that the next nightly will switch to using the self-contained lld by default instead of the system linker. Trying to do some pre-testing of this setup by manually enabling the new defaults in a project with a native dependency indicates that this causes issues with library loading (presumably something rpath related, but I've never dug into the details of how that is handled normally):
> cargo rustc -- -Clink-self-contained=+linker -Clinker-flavor=gnu-lld-cc
   Compiling u2f-touch-detector v0.1.0 (/home/nemo157/sources/u2f-touch-detector)
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.58s

> $CARGO_HOME/target/shared/x86_64-unknown-linux-gnu/debug/u2f-touch-detector --help
/run/user/1000/cargo-home/target/shared/x86_64-unknown-linux-gnu/debug/u2f-touch-detector: error while loading shared libraries: libudev.so.1: cannot open shared object file: No such file or directory

The PR linked from the tracking issue mentions that the workaround will be to use -Zlinker-features=-lld.

I assume we'll probably need to wrap rust-lld, similar to https://github.com/NixOS/nixpkgs/issues/24744#issuecomment-2094118403

I found out why, I use cranelift as my codegen backend which disables default-active lld. Testing with that overridden successfully fails:
> CARGO_PROFILE_DEV_CODEGEN_BACKEND=llvm cargo run -- --help
   Compiling u2f-touch-detector v0.1.0 (/home/nemo157/sources/u2f-touch-detector)
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.61s
     Running `/run/user/1000/cargo-home/target/shared/x86_64-unknown-linux-gnu/debug/u2f-touch-detector --help`
/run/user/1000/cargo-home/target/shared/x86_64-unknown-linux-gnu/debug/u2f-touch-detector: error while loading shared libraries: libudev.so.1: cannot open shared object file: No such file or directory

The wrap function is fairly simple, maybe worth vendoring it:
wrap() {
  local dst="$1"
  local wrapper="$2"
  export prog="$3"
  export use_response_file_by_default=${if isCCTools then "1" else "0"}
  substituteAll "$wrapper" "$out/bin/$dst"
  chmod +x "$out/bin/$dst"
}

You could then reference the ld wrapper like so:
mv $out/bin/rust-lld $out/bin/.rust-lld-unwrapped
wrap $out/bin/rust-lld \
  ${pkgs.path + /pkgs/build-support/bintools-wrapper/ld-wrapper.sh} \
  $out/bin/.rust-lld-unwrapped

The wrap function is fairly simple, maybe worth vendoring it:

Thanks for the investment of the ld-wrapper. I ends up copying part of the wrapper implementation to make it actually work. I created #171 and it works for me now. I'm looking for tests and feedback from people involving here.

authors: Nemo157 oxalica szlend

repo: oxalica/rust-overlay


text:
Resolving symlinked long path on Windows returns a DOS device path

When resolving a symlinked file that has a long path, oxc-resolver returns a DOS device path (a path starting with \\?\) on Windows. I expect a normal path to be returned (a path without \\?\).
Reproduction

Clone https://github.com/sapphi-red-repros/oxc-resolver-windows-long-path-dos-device-path-reproduction on Windows
run pnpm i
run node index.js
the output is something like result \\?\D:\documents\GitHub\oxc-resolver-windows-long-path-dos-device-path-reproduction\node_modules\.pnpm\@vitejs+longfilename-aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa_pdxfg5khqstn67ymcqlkhhhflu\node_modules\@vitejs\longfilename-aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa\index.js

https://github.com/oxc-project/oxc-resolver/blob/a6a9b0bcd1a068bb228c1ab011144a2055a9b644/src/file_system.rs#L173
If you are on windows, can you try and use the example https://github.com/oxc-project/oxc-resolver/blob/main/examples/resolver.rs and see what's happening here.
I'm not on windows :-/

dunce::canonicalize seems to only trim \\?\ when the path is shorter than 260 chars.
https://gitlab.com/kornelski/dunce/-/blob/1ee29a83526c9f4c3618e1335f0454c878a54dcf/src/lib.rs#L176-180
On the other hand, libuv always strips \\?\ regardless of the char length.
https://github.com/libuv/libuv/blob/d4ab6fbba4669935a6bc23645372dfe4ac29ab39/src/win/fs.c#L2780-L2785

When using the path from Node.js side, it would be easier to use if \\?\ is always stripped. But I'm not sure if that is easier to use for the Rust side.

When using the path from Node.js side, it would be easier to use if \\?\ is always stripped. But I'm not sure if that is easier to use for the Rust side.

Rust side has no preference, we can strip it if things still work.

authors: Boshen sapphi-red

repo: oxc-project/oxc-resolver


text:
fix(transformer/class-properties): replace references to class name with temp var in static prop initializers

Similar to #7516. Fix class properties transform to replace references to class name in static prop initializers with temp var.
Input:
class C {
  static getSelf = () => C;
}
const C2 = C;
C = 123;
assert(C2.getSelf() === C);

Output:
var _C;
class C {}
_C = C;
_defineProperty(C, "getSelf", () => _C);
const C2 = C;
C = 123;
assert(C2.getSelf() === C);

Previously, temp var wasn't used so code was _defineProperty(C, "getSelf", () => C);. C is altered later by C = 123, so C2.getSelf() returned 123, instead of reference to the class.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#7610  👈 (View in Graphite)
#7609
#7608
main

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

Merge activity

Dec 3, 7:42 AM EST: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.

authors: Dunqing overlookmotel

repo: oxc-project/oxc


text:
Empty topic when using the plugin

When I use this given Mermaid sample:
<foreign outputclass="embed-mermaid-diagram">
    graph TD;
    A-->B;
    A-->C;
    B-->D;
    C-->D;
</foreign>

The webhelp topic containing this code is not rendered at all. The HTML file is completely empty. All other topics are rendered fine. The DITA-OT does not throw an error message.
The Plant UML diagrams (which are generated locally) work fine. So I guess the DITA-OT cannot contact the Mermaid server. IMHO the build should throw an ERROR in this case.

@stefan-jung I tried the plugin in Oxygen Publishing Engine 27.0 and the diagram did render in WebHelp Responsive output:

@jlacour31 Does it also render when you disconnect all network connections (the Mermaid API is not reachable)?

@stefan-jung I did some modifications could you try to update the plugin and see if you get a warning now?
I don't think an error is necessary in this case, the diagram will be ignored and the output will contains the topic.

repo: oxygenxml/dita-ot-diagrams-plugin


text:
Typescript intellisense broken

Most everything here works great but something seems to be off config wise where in VSCode it can't detect/import via the normal ^ + Space flow from installed packages.

Just tested this out and it appears to work fine so going to close this. Feel free to reopen if it is still happening but please include a reproduction repo

authors: bradymwilliams ozziexsh

repo: ozziexsh/laravel-jetstream-react


text:
Dev Dialog Box Pop up more then once

Resolve Dev Dialog pop up more then once.

Issue if fixed #37


text:
Every minute syncing

I use Nightscout as source. Sometimes the app  synchronizes every minute, sometimes every 2 minutes, sometimes every 4 minutes etc. No battery optimization and things disturbing synchronization, the app can do all. But no stable every minute syncing, can you test and fix it please?

Can you save the logs and send them to my mail using the contact option in GlucoDataHandler

Close as it seems to be a problem with Realm mobile.


text:
Create official docker image for pachctl

What is the goal / desired outcome?
Having official images for the pachctl executable would make it simple to run the client on multiple environments. (see postgres image as an example https://github.com/docker-library/postgres)
(Optional) What is your proposal for a feature to solve this?
I am an official maintainer for the NodeJS docker image and have done a lot of the work for the management of that image and I am volunteering to do most of the ground work required to get the image setup. I already created an image for Alpine linux which gives an image that is 60mb.

Doing it this way should also be much easier since it can use the same script we use to compile our other binaries. If you take a look at docker-build-pachd it looks like this:
docker-build-pachd: docker-clean-pachd
	docker run  \
		-v $$GOPATH/src/github.com/pachyderm/pachyderm:/go/src/github.com/pachyderm/pachyderm \
		-v $$HOME/.cache/go-build:/root/.cache/go-build \
		--name pachd_compile $(COMPILE_RUN_ARGS) $(COMPILE_IMAGE) /go/src/github.com/pachyderm/pachyderm/etc/compile/compile.sh pachd "$(LD_FLAGS)"

that argument on the last line pachd could be changed to pachctl to compile pachctl instead. I suspect a few other complications will arise but that should be most of it.
The harder question here is how to make pachctl connect to pachd from within a container. Have you thought about how we might pull that off @LaurentGoderre?

@JoeyZwicker I would strongly recommend using FROM scratch and adopt the official image standard. Otherwise you will not get the full benefit of the images security scans and automated security updated you get from Docker Hub

@jdoliner for connecting to pachd from a container, wouldn't it simply be a matter of setting -e ADDRESS=[ip to pahcd]?

Here's the repo that creates the images: https://github.com/LaurentGoderre/docker-pachctl

/cc @tianon

Given that there's an officially-published binary release of pachctl, I'd honestly recommend not going for FROM scratch and instead targeting FROM alpine:3.9.  It's a ~4MB difference (which is pretty negligible when compared to even the compressed ~14MB of pachctl on https://github.com/pachyderm/pachyderm/releases/tag/v1.8.5).  Then the image can ideally consume those official release binaries directly, something like this:
FROM alpine:3.9
ENV PACHCTL_VERSION 1.8.5
RUN set -eux; \
	wget -O pachctl.tgz "https://github.com/pachyderm/pachyderm/releases/download/v$PACHCTL_VERSION/pachctl_${PACHCTL_VERSION}_linux_amd64.tar.gz"; \
	tar -xvf pachctl.tgz --strip-components=1 -C /usr/local/bin/; \
	rm pachctl.tgz

(Note that this doesn't currently actually work because the release binaries are compiled dynamically instead of statically, so they're expecting to find glibc, but that's a reasonably easy problem to solve and IMO worthwhile for published binary releases.)

@tianon, what about all the other achs?

I mean, it's Go, so releasing official binaries for every architecture the
project wants to officially support is a pretty easy task too. 😅
(Go's cross-compilation support is legendary 😃)

There have been a few requests for arm (#1734 ), but hasn't been tackled yet. I haven't done any cross compilation with go, so good to know it shouldn't be hard

@gabrielgrant if we can create the binaries for all the arch using static linking, we can probably get this as an official image and all the different arch will be managed in docker hub.

Still no idea what pachctl is, but I took https://github.com/tianon/gosu/blob/f87df69c868e19f7258b4facb7c2472d76d98dda/Dockerfile (which I use to release gosu binaries for a pretty large number of architectures with the smallest possible binaries I could get Go to create), and adapted it to build the latest release of pachctl:
FROM golang:1.12-alpine3.9

RUN apk add --no-cache file

ENV PACHYDERM_VERSION 1.8.5
WORKDIR /go/src/github.com/pachyderm/pachyderm
RUN set -eux; \
	wget -O pachyderm.tgz "https://github.com/pachyderm/pachyderm/archive/v${PACHYDERM_VERSION}.tar.gz"; \
	tar -xvf pachyderm.tgz --strip-components=1; \
	rm pachyderm.tgz
WORKDIR ./src/server/cmd/pachctl

# disable CGO for ALL THE THINGS (to help ensure no libc)
ENV CGO_ENABLED 0
ENV BUILD_FLAGS="-v -ldflags '-d -s -w'"

# /go/bin/pachctl-$(dpkg --print-architecture)

RUN set -eux; \
	eval "GOARCH=amd64 go build $BUILD_FLAGS -o /go/bin/pachctl-amd64"; \
	file /go/bin/pachctl-amd64; \
	/go/bin/pachctl-amd64 --help

# ../../pkg/deploy/assets/assets.go:82:37: constant 8589934592 overflows int
#RUN set -eux; \
#	eval "GOARCH=386 go build $BUILD_FLAGS -o /go/bin/pachctl-i386"; \
#	file /go/bin/pachctl-i386; \
#	/go/bin/pachctl-i386 --help

# ../../pkg/deploy/assets/assets.go:82:37: constant 8589934592 overflows int
#RUN set -eux; \
#	eval "GOARCH=arm GOARM=5 go build $BUILD_FLAGS -o /go/bin/pachctl-armel"; \
#	file /go/bin/pachctl-armel
#RUN set -eux; \
#	eval "GOARCH=arm GOARM=6 go build $BUILD_FLAGS -o /go/bin/pachctl-armhf"; \
#	file /go/bin/pachctl-armhf
# boo Raspberry Pi, making life hard
#RUN set -eux; \
#	eval "GOARCH=arm GOARM=7 go build $BUILD_FLAGS -o /go/bin/pachctl-armhf"; \
#	file /go/bin/pachctl-armhf

RUN set -eux; \
	eval "GOARCH=arm64 go build $BUILD_FLAGS -o /go/bin/pachctl-arm64"; \
	file /go/bin/pachctl-arm64

RUN set -eux; \
	eval "GOARCH=ppc64 go build $BUILD_FLAGS -o /go/bin/pachctl-ppc64"; \
	file /go/bin/pachctl-ppc64

RUN set -eux; \
	eval "GOARCH=ppc64le go build $BUILD_FLAGS -o /go/bin/pachctl-ppc64el"; \
	file /go/bin/pachctl-ppc64el

RUN set -eux; \
	eval "GOARCH=s390x go build $BUILD_FLAGS -o /go/bin/pachctl-s390x"; \
	file /go/bin/pachctl-s390x

RUN file /go/bin/pachctl-*

I've had to comment out all 32-bit platforms since there's some constant in here somewhere that overflows an int, but otherwise it appears reasonably OK:
/go/bin/pachctl-amd64:   ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, Go BuildID=Qa0N5tgrqh9Ws0hmAjMX/CEcy2VNZ5newmwm-9eEN/lz6JT17Cb3v33NZRNA-k/LYWF4FzHeFQwmsE9zDpl, stripped
/go/bin/pachctl-arm64:   ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), statically linked, Go BuildID=ObIrbZrDC3xbeByO3fx-/ErjTZZbyXg_t-vOeOuW1/eqgptHcmaTinyAFtYn5f/Hg1WybSpenoIqPbmKUjR, stripped
/go/bin/pachctl-ppc64:   ELF 64-bit MSB executable, 64-bit PowerPC or cisco 7500, version 1 (SYSV), statically linked, Go BuildID=69hid6CLNHdtMJ7EoQnI/V9kt7uUKIWT1IdlEIr7-/rxITTV8y3BaBlYgjJ7ga/ovG2muJF0dlgWwqtaYgH, stripped
/go/bin/pachctl-ppc64el: ELF 64-bit LSB executable, 64-bit PowerPC or cisco 7500, version 1 (SYSV), statically linked, Go BuildID=8C976BozPzHj0VgHiMU7/ZPhDqujGUzSZy2gu77K6/_h8Ya2tJA44Mt6AArntS/n8v4HgLqAKqs_bnMNrxL, stripped
/go/bin/pachctl-s390x:   ELF 64-bit MSB executable, IBM S/390, version 1 (SYSV), statically linked, Go BuildID=a-CIo0Wry9oMWQh-yk22/R-RZZEv4QAEhIJ7k1Xqm/cn6TkXDy2viLE2QW8UBn/iUbdfe827iokF_AJm_I_, stripped

-rwxr-xr-x    1 root     root       42.4M Feb 28 23:43 pachctl-amd64*
-rwxr-xr-x    1 root     root       40.6M Feb 28 23:45 pachctl-arm64*
-rwxr-xr-x    1 root     root       41.1M Feb 28 23:45 pachctl-ppc64*
-rwxr-xr-x    1 root     root       41.0M Feb 28 23:46 pachctl-ppc64el*
-rwxr-xr-x    1 root     root       42.4M Feb 28 23:46 pachctl-s390x*

Amazing @tianon!! Thanks for this!

Currently using a fork of @LaurentGoderre's Dockerfile for this. Would also like an official one.

I can transfer ownership of my repo to this org and help maintain it.

Official support is a WIP, and should come out around the 1.11 release. However, we've pursued a different approach than the excellent work @LaurentGoderre has done. The official version ties deeply into our CI and deployment infrastructure. This will provide better support for the newest versions of pachctl, at the detriment of lack of support for multiple architectures or non-glibc bindings.
This covers our internal needs for a dockerized pachctl (for use in testing Pachyderm hub, and as a first step toward integrating with github actions) and I suspect may cover most other needs as well. However, users who want support for other architectures or non-glibc can use Laurent's builds, at least for versions up to 1.9.
I do hope to support multiple architectures (and possibly non-glibc) eventually via docker multi-arch builds. But I get the impression that it's not particularly mature yet.

authors: LaurentGoderre chriszs gabrielgrant jdoliner tianon ysimonson

repo: pachyderm/pachyderm


text:
Create a pipeline environment doc

This came out of an offline discussion with @JoeyZwicker about pipeline docs. I think we should have a doc dedicated to the environment that use code runs in. This would include:

The env-vars that the pipeline code can access. Right now this is documented in the pipeline spec and configure env vars doc. I think the latter location doesn't make a ton of sense for pipeline environment variables, because it's about configuring and deployment of Pachyderm, ie env vars that you set to modify the behavior of Pachyderm, rather than env vars that Pachyderm gives to worker code. Once we have a dedicated doc for pipeline environment I think we should remove the pipeline env vars from that doc and have it just be about configuration env vars.

What /pfs looks like, this would be a good place to note that the directories under /pfs are actually symlinks to directories and not traditional directories.

Things that get inherited from the docker container image, such as the user that the code runs as, the entrypoint and working dir.

We should note that this environment is setup by our worker code, not by kubernetes. So it won't be visible when you exec into a pod, it's only visible from your transform that gets execced.

Environment:

Kubernetes version (use kubectl version):
Pachyderm CLI and pachd server version (use pachctl version):
Cloud provider (e.g. aws, azure, gke) or local deployment (e.g. minikube vs dockerized k8s):
OS:
Other:

I think we have addressed most of these concerns in the last few PRs and the resulting doc is here: https://docs.pachyderm.com/latest/deploy-manage/deploy/environment-variables/. If something is missing, feel free to reopen.

authors: jdoliner svekars


text:
Add optional docker build step to docs

Even when running locally, pachd is defined to be an instance of pachyderm/pachd, so if it isn't found locally it's pulled from the public hub which leads to a version mismatch.
This affects deploying to gcs too I believe, and for the same reasons. But that's a less-trivial fix so it can wait.

This is a helpful clarification for the state of things right now. They're about to change though so that manifests reference specific versions in which case people shouldn't have to build images as a part of the normal deploy process.
I think this could make sense as a section called "Deploying from Head" though We could put that at the bottom and explain to people how head is generally less stable but has new features. We could also explain how to deploy from head on cloud infrastructure which requires pushing to docker hub or another container registry to get the image to the machines.

I moved the notes down to the bottom but haven't added anything about pushing to a registry yet.
Since there's usually no reason to make an image built from head private, I think we can recommend pushing to the public hub as a simple solution and not take on the burden of documenting one of many ways to make a private registry.

@jdoliner clarification on revision needed here. If there's no issue with not explaining registries I can rewrite against master and update this.

authors: jdoliner sambooo


text:
Set environment and custom tags for sentry events

sentry environment
configure scope
local scope

affects events only within the context

:tada:
This is great!
I do understand the "environment" part, but don't really understand why tags will be useful. Would it make sense to capture this info in the commit message for future readers.

The reasoning is now present.

authors: csomh dhodovsk

repo: packit-service/packit-service


text:
Build logs should use use browser wrapping

At this moment the build logs are not wrapped to browser window size and that makes it quite hard to read essential information from lines that are longer than the window.
https://dashboard.packit.dev/results/srpm-builds/28981
This css hack seems to achieve the desired wrapping:
code {
    white-space: pre-wrap;
}

This behavior would also match what a normal user terminal would see, as terminals do not usually hide the long lines and do wrap them instead.

Thanks for opening the issue, indeed a good suggestion. I'm also wondering if patternfly has native support for terminal-like outputs.

Does https://github.com/patternfly/patternfly-design/issues/955 look familiar? ;) -- apparently things are moving slowly but in good direction.

@ssbarnea nice!!
I can see some related PRs were already merged, e.g. https://github.com/patternfly/patternfly/pull/4029
shall we use that?

If it was released I would clearly take a look at at it. Still, there is something confusing me about patternfly release process, apparently all tags are marked as prerelease when I look at https://github.com/patternfly/patternfly/tags

@ssbarnea: @mfocko is already busy with some updates to the log-viewer as you can see above :) stay tuned!

Small update on the issue: I have tried the LogViewer, spotted 2 issues:

empty lines in logs made huge dead space, which I have fixed in upstream already
each line is estimated 60px height; that at least from my perspective is bigger issue than the logs not being wrapped, I will try to fix that in the upstream too

After fixing the 2nd issue we should be good to go :)

authors: TomasTomecek mfocko ssbarnea

repo: packit/dashboard


text:
Remove AWS SQS support

Related packit/deployment#226

N/A

recheck

repo: packit/packit-service


text:
ZXControllerBuilder

Make ZXControllerBuilder for ZXController

implemented via common ZXSettings struct e4e351349cdde75c4c1e81bf5ae5c0fad6a1acfa

repo: pacmancoder/rustzx


text:
Rewrite the SDK

Hello, Pactus developers.
I wanted to use the SDK but the structure of SDK is not developer-friendly it just provides auto-generated GRPCs API and some functionality they not useful.
the point of SDKs is to create things easy to use, I want to rewrite the whole SDK to improve the structure and functionality.
I hope it is acceptable

@0keeper1 Hi, that's nice too see you are interested in contributing.
Make sure you don't break current behavior or tests over all. and consider that the gRPC file at the moment have a open issue may it can affect your changes in rpc package. so, make sure you take a look at it before adding codes:

#19

@0keeper1 Hi, that's nice too see you are interested in contributing.
Make sure you don't break current behavior or tests over all. and consider that the gRPC file at the moment have an open issue may it can affect your changes in rpc package. so, make sure you take a look at it before adding codes:
* [gRPC packages and paths #19](https://github.com/pactus-project/python-sdk/issues/19)

about this issue, I will re-generate the GRPCs. and I will fix the issues.
And I will release the SDK with version 2.0.0.

repo: pactus-project/python-sdk


text:
🛑 Fantastic wheels is down

In 1260507, Fantastic wheels (https://fantasticwheels.be) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Fantastic wheels is back up in 015be27.

repo: pageon/uptime


text:
[CHK-1110]: Test trigger

List of Changes

just a few updates on the readme to test the CR pipeline trigger

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

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

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

Try to align this branch to the develop to see if the tests still fails

authors: infantesimone stratoivandiluccio

repo: pagopa/pagopa-checkout-fe


text:
feat: add kill count notifier

Closes #1

Your subdued Wintertodt count is: 359
Your Barrows chest count is: 268

For some boss kills, felan pointed out the kill time & PB are sent in chat: https://cdn.discordapp.com/attachments/901356769371107398/1032366619789369364/collectionImage.png
So, a future feature could also trigger a notification on new PB, even if interval isn't satisfied
This increases the complexity of the notifier and the message format is different for group boss fights, so I have not yet implemented this

Will merge in as soon as raids are tested :)

Will merge in as soon as raids are tested :)

(we're not going to test raids unless pajlada can wrangle notheowner dfantasy and 🅱 upinic)

authors: Felanbird Mm2PL iProdigy

repo: pajlads/DinkPlugin


text:
Generate a custom JRE with jlink

Hello,
I'm not sure if this is the right repo to ask this... Is it possible to generate a custom JRE via jlink in order to get smaller docker image ?

Any update on this? I'm thinking along the lines of the plugin being able to use module-info.java files (if present) to create a docker image of a spring boot app which only contains the used JDK modules.

@Decat-SimonA I know it's been a long time, sorry. I think this is something we might be able to move forward with, but I'm trying to gather more feedback first. If this is something you're still interested in seeing, can you expand on how you'd see something like this working?
It would certainly be possible for the buildpack to run jlink as part of its build process. To run jlink we need some configuration though. What comes to my mind would be to start basic. We could make the buildpack provide a set of default arguments for jlink and allow the user to override those arguments.
For example, we could do something like this, where we include all modules but strip out man pages, header files and debug.
jlink --add-modules "$(java --list-modules | sed -e 's/@[0-9].*$/,/' | tr -d \\n)" --no-man-pages --no-header-files --strip-debug --output /opt/corretto

Alternatively, a user could override that default behavior by supplying their own list of modules.
At least initially, I think we would need to make this behavior off by default. If we get enough positive feedback, I could perhaps see us eventually enabling it by default.
Anyway, do you see this working for your use case? If not, can you expand on how you'd like to see this work?
@vab2048 - Same questions for you, but also can you expand on what you mean with regards to module-info.java files?
Thanks

I was pointed here, when I was trying to understand the size of images created by the Amazon Corretto buildpack. Since they don't release a JRE, there obviously needs to be a form of JDK in the run-image to run the compiled code, but I would like to have that JDK as minimal as possible (to reduce the size of the created image).
To that end, @dmikusa-pivotal, running jlink like that (as it's run by the Corretto project when creating a slimmer image) would definitely be great for that.

@dmikusa-pivotal apologies - what I wrote was not particularly clear.
Let me explain my use case...
Currently we can make docker images for our Spring Boot apps by using the Spring Boot plugin (for Maven/Gradle) and running the associated task (bootBuildImage with Gradle). Under the hood I am assuming this buildpack library is used. Currently it is common for the built docker images to be between 300mb and 500mb in size.
My point was that it would be desirable for the buildpack to be able to build 'slimmed down' Spring Boot docker images which only contain those Java modules which are actually used. Hopefully then the images built could be < 100mb in size.
What you are suggesting - using jlink to build the custom JRE and stripping out unnecessary files - is probably exactly what is needed.
Good luck!

OK, thanks for the feedback. I think that is probably good for us to start with an MVP for this feature. We can obviously iterate from there.
If anyone else has ideas or suggestions, free to add them here. Also, 👍 if you are looking for this feature.
There is some work we need to address before we can get to this particular issue, so I can't give a definite date. I'd say Jan/Feb of next year is a likely target. If you stay tuned to this issue I'll update as we're making progress.

@dmikusa-pivotal any word on this by any chance? :)

It's on the roadmap. We definitely plan to implement. It's more of a timing issue. There are a few other projects in our queue first.
If someone were interested in submitting a PR, I could make time to merge that. It would need to be in libjvm. It would be something to add to the Contribute method, this is where we configure the JRE that ends up in the launch layer. We'd want to filter so that it only runs jlink if the j.DistributionType == JDKType, which limits it to run when a JDK is being used as a JRE. The buildpack would need to run jlink, basically like this, and handle arguments similar to this.

repo: paketo-buildpacks/libjvm


text:
Tidy up some things

Tidy up some things

I chose semver:minor since this bumps the buildpack API version, although this should be invisible to consumers.

@joshuatcasey this LGTM.
Just FYI the Paketo semver guidelines suggest that a Buildpack API bump would be a major - but so far we've been treating Buildpack API bumps as a minor and I think I'm ok with that for this situation too, as we only just released v1.0.0 of this buildpack. Perhaps future API version bumps should be majors though? What do you think?

@robdimsdale @thitch97 wait a minute - we've been treating API bumps as minors in other buildpacks because we hadn't cut a 1.0.0 release of those buildpacks yet. I think that this should be a major bump, we should follow the rules now that we're at a 1.0.0 release.

@sophiewigmore sure - we could fast-follow 1.0.0 with 2.0.0.
Or we could hold off bumping the API until we need it

@sophiewigmore sure - we could fast-follow 1.0.0 with 2.0.0.
Or we could hold off bumping the API until we need it

I'm fine with either option here, leaning toward the latter. In my mind, the main changes introduced in API 0.8 weren't immediately relevant to this buildpack but @sophiewigmore makes a good point.

@paketo-buildpacks/php-maintainers I've updated this PR to (1) remove the buildpack API version bump, (2) rebase on latest, and (3) downgrade the semver to patch.

authors: joshuatcasey robdimsdale sophiewigmore thitch97

repo: paketo-buildpacks/php-dist


text:
record response metrics

these are generally useful, but the explicit goal here is to start recording enough information such that we can determine when interactions with services we depend on are unhealthy.

@schlosna what's the concern with the metrics dependency?

@uschi2000 wired in the interceptor. any other concerns?

repo: palantir/http-remoting


text:
no-unbound-method: referencing methods that are bound in constructor should be ok

Bug Report
In https://github.com/palantir/tslint-react/issues/63 it was mentioned that a rule such as no-unbound-method should check for methods that are bound in the constructor (e.g. this.handleClick = this.handleClick.bind(this);) to avoid false positives. Although https://github.com/palantir/tslint-react/issues/63 was closed with the introduction of no-unbound-method this case does not seem to be implemented.

TSLint version: 5.5.0
TypeScript version: 2.4.1
Running TSLint via: CLI

TypeScript code being linted
class C {
  public constructor() {
    this.method = this.method.bind(this);
  }
  public method(): number {
    return 1;
  }
}

const c = new C();
[0].forEach(c.method);

with tslint.json configuration:
{
  "no-unbound-method": true
}

Actual behavior
⚠ Fails with:
[11, 13]: Avoid referencing unbound methods which may cause unintentional scoping of 'this'.

Expected behavior
✅  Has no errors.

I guess your suggestion is technically valid, but I'm not sure if the the extra complexity in this rule is worth it -- since this is TS, couldn't you just bind your methods using arrow functions?

I guess arrow functions as class properties would be fine for most cases in the React world (referring to https://github.com/palantir/tslint-react/issues/63). But they do have the disadvantage that you can not call super in them, i.e. something like this is not possible without the bind in the constructor as far as I know:
class A {
  count: number;

  constructor() {
    this.count = 0;
    this.method = this.method.bind(this);
  }

  method() {
    this.count++;
  }
}

class B extends A {
  method() {
    super.method();
    this.count++;
    console.log(this.count);
  }
}

const b = new B();
// This would be an event handler or something:
[0].forEach(b.method); // logs 2

closing, see https://github.com/palantir/tslint/pull/3017#issuecomment-314368510

+1 for re-open. It would be very good if someone will implement checking for binding in the constructor. There was a try (#3017), but it has failed. no-unbound-method rule is really a pain for React, because recommend way is to bind in the constructor, not to create arrow lambda.

You can refile a new issue I'd you'd lilezz so you have authorship of it.

Is this being tracked in any open issue? This rule will be really useful if it checks if the function is bound in the constructor.
I converted a bunch of class functions to be arrow functions, but that makes the class not mockable.

🤖 Beep boop! 👉  TSLint is deprecated 👈  and you should switch to typescript-eslint! 🤖  #4534
🔒 This issue is being locked to prevent further unnecessary discussions. Thank you! 👋

authors: Amaimersion JoshuaKGoldberg KingHenne adidahiya karanrajpal

repo: palantir/tslint


text:
Fixing by prefer-object-spread breaks indentation

Bug Report

TSLint version: 5.5.0
TypeScript version: 2.1.6
Running TSLint via: CLI

TypeScript code being linted
const obj1 = {a: 1};
const obj2 = {b: 2};

const merged = Object.assign(
  {},
  obj1,
  {
    a: 11,
    b: 22,
  },
  obj2
);

with tslint.json configuration:
{
  "rules": {
    "prefer-object-spread": true
  }
}

Actual behavior
After fixing, I got:
const merged = {...obj1,

    a: 11,
    b: 22,
  ...obj2
};

Expected behavior
const merged = {
  ...obj1,
  a: 11,
  b: 22,
  ...obj2
};

I know the current behavior is a PITA.
Making the fixer output of rules compatible with any other rule you may have enabled is not a very high priority.
In fact it would be really hard to get the indentation right, especially for the nested properties a and b in your example.

In fact it would be really hard to get the indentation right, especially for the nested properties a and b in your example.

I have the same opinion. It seems to be hard.
However, the current output is unshapely. I think this rule might be better to drop fixability.

However, the current output is unshapely. I think this rule might be better to drop fixability.

It works nice for single line expressions. And besides the code style issues, it works in all scenarios. I don't think that this justifies removing the fixer.
When I find the time, I'll look into this and fix the output to something like this:
const merged = {
  ...obj1,
    a: 11,
    b: 22,
  ...obj2
};

The align issue will be fixed by the align rule afterwards (or on a second run).

That's a good idea. Simple but worthy.

☠ TSLint's time has come! ☠
TSLint is no longer accepting most feature requests per #4534. See typescript-eslint.io for the new, shiny way to lint your TypeScript code with ESLint. ✨
It was a pleasure open sourcing with you all!

🤖 Beep boop! 👉  TSLint is deprecated 👈 (#4534)  and you should switch to typescript-eslint! 🤖
🔒 This issue is being locked to prevent further unnecessary discussions. Thank you! 👋

authors: JoshuaKGoldberg ajafff berlysia


text:
indent: Convert to function

PR checklist

[ ] Addresses an existing issue: #0000
[ ] New feature, bugfix, or enhancement

[ ] Includes tests

[ ] Documentation update

Overview of change:
Just a refactor.

let's wait until #2723 goes in and then try to rebase (or do the work again and open a new PR)

ping @andy-hanson

authors: adidahiya andy-hanson


text:
New Rule: no-inferrable-types

Resolves https://github.com/palantir/tslint/issues/676

looks pretty good overall; needs merge conflict resolution

still waiting on removal of the typo fix in README

[changes made]

authors: JKillian adidahiya


text:
Remove check() API

Overview
This change removes the client.check() API. The rationale is that this shortcut is considered a duplicate and violates the ElmoClient class responsibility. This class must stay lightweight without any extra logic other than handling the connection and make API calls.

Codecov Report

Merging #71 (3db524e) into master (50e0303) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master       #71   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            5         5
  Lines          276       271    -5
=========================================
- Hits           276       271    -5

Impacted Files
Coverage Δ

elmo/api/client.py
100.00% <ø> (ø)

Continue to review full report at Codecov.

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

authors: codecov-commenter palazzem

repo: palazzem/econnect-python


text:
Use error source fixed

This fixes your fix https://github.com/rust-lang-nursery/error-chain/pull/255 ;)
It moves usage of has_error_source flag outside the macro, otherwise it will break compilation in dependent crates as they do not have this flag defined.

Thanks for this. Possibly should file a bug with upstream to test this in Travis, as otherwise we'll forget about this in the future?

authors: palfrey tworec

repo: palfrey/error-chain