[SR-15709] Overflowing operations on Int8 fail to trap if done as FixedWidthInteger

Previous ID
SR-15709

Radar
None

Original Reporter
@saagarjha

Type
Bug

Environment
https://swift.godbolt.org/z/Ta35Yn5zf

Additional Detail from JIRA

Votes
0

Component/s

Labels
Bug

Assignee
None

Priority
Medium

md5: fc0730224133a7d6c5bdc494ea2b731b

Issue Description:
Operations that should overflow a Int8 silently return zero if you run them in a context where Self is FixedWidthInteger. Here's an example:
protocol Foo {
}

extension Int8: Foo {}

extension FixedWidthInteger {
    var bar: UInt8 {
        return UInt8(self & 0xFF)
    }
}

extension Int8 {
    var baz: UInt8 {
        0
        // Compiler error: integer literal '255' overflows when stored into 'Int8'
        // return UInt8(self & 0xFF)
    }
}

let qux = 1 as Int8

print(qux.bar)
print(qux.baz)

This executes and prints 0, but the first operation should have trapped. (In previous versions of Swift, this returned a non-zero value.) The operation is broken, and the compiler throws an error in contexts where it can figure out that there will always be an overflow.

Duplicate of #42919.


history section added

Maybe @sdarwin can check to see if there are any other non-html documents on the server?

The boostorg website is stored in the repository https://github.com/boostorg/website
It has the these PDF files:
website/community/blom_libraries/BLOM_MoU_v0.pdf
website/users/proposal.pdf
Also rst files:
development/report-apr-2006.rst
development/report-apr-2008.rst
development/report-dec-2009.rst
development/report-jan-2006.rst
development/report-jun-2009.rst
development/report-may-2008.rst
development/report-nov-2007.rst
development/report-nov-2008.rst
development/report-sep-2007.rst
And many PHP files.

yeah I dpnt care too much about the php but the rst is interesting

@sdarwin Good info - I have added links to the rst files to my history topic. I cannot find a blom_libraries folder under the communities folder - any insight - do I need to update something?

Looks like Glen removed that directory in Feb 2023 https://github.com/boostorg/website/commit/7bee278d220d1c6e954ba4648146936b31d27e3c


Place variable in matrix namespace.

Follow-up to #1427

Confirmed that when ophyd-version is "master" it is installed from GitHub:
Run python -m pip install git+https://github.com/bluesky/ophyd.git@master
Collecting git+https://github.com/bluesky/ophyd.git@master
  Cloning https://github.com/bluesky/ophyd.git (to revision master) to /tmp/pip-req-build-sysjawub
Requirement already satisfied: networkx>=2.0 in /opt/hostedtoolcache/Python/3.6.12/x64/lib/python3.6/site-packages (from ophyd==1.5.4.post94+g2f5ce65) (2.5)
Requirement already satisfied: numpy in /opt/hostedtoolcache/Python/3.6.12/x64/lib/python3.6/site-packages (from ophyd==1.5.4.post94+g2f5ce65) (1.19.4)
Requirement already satisfied: decorator>=4.3.0 in /opt/hostedtoolcache/Python/3.6.12/x64/lib/python3.6/site-packages (from networkx>=2.0->ophyd==1.5.4.post94+g2f5ce65) (4.4.2)
Building wheels for collected packages: ophyd
  Building wheel for ophyd (setup.py): started
  Building wheel for ophyd (setup.py): finished with status 'done'
  Created wheel for ophyd: filename=ophyd-1.5.4.post94+g2f5ce65-py3-none-any.whl size=252704 sha256=9c064003c45bba8a37dc27a863db01854a54033d4d396a71052cc4af03c086ce
  Stored in directory: /tmp/pip-ephem-wheel-cache-f6y8qlhj/wheels/12/9a/f7/b83aa57d85b9b4c8e8ef9e0bd7e91868a859e81a7423f542d1
Successfully built ophyd
Installing collected packages: ophyd
  Attempting uninstall: ophyd
    Found existing installation: ophyd 1.5.4
    Uninstalling ophyd-1.5.4:
      Successfully uninstalled ophyd-1.5.4
Successfully installed ophyd-1.5.4.post94+g2f5ce65

but when ophyd-version is "latest" it is left as is from PyPI.


Smart filter options

Started using GutenTag as a way of noting what is done, what needs works, things I've checked, etc. Didn't have a clear idea of what tags I would need so I just kept adding as needed. At some point, I wanted to be able to see all the tags I've added to organize further and filter through them.
I'd like to note a couple of questions, observations, and feature requests:

In the Smart Filter list would it be possible to extend the search from Contains to the full dropdown list with Contains, Doesn't Contain, Begins With, Ends With, etc.? This could be helpful if, for example, someone adds a Done tag then wants to filter all the not Done (doesn't contain Done tag) glyphs.

The portion in the smart filter option for the name of the tag...would it be possible for that to be a dropdown that is automatically populated by all the available tags? If this is possible would the tags stay hot-linked if tag names are changed later on?

On a tangential note, is there a way to see all the tags (to view, organize, rename, access the glyphs within the tag)...if not, would this be useful additional perhaps through a popup window UI or an extension of the tags panel (sort of how the Reporters plugin has the Edit view to see all the list of possible reporter plugins )?

1: doesn’t contain: Create an empty smart filter, hold down the Option key and press the ••• button, then switch to the None mode. Any rules nested in a None block are negated, so a contains becomes a does not contain. This is a bit convoluted, I know, but Apple’s frameworks allow for little extensibility in this regard. (See also the Glyphs Handbook on Smart Filters, page 92 and especially 94.) Begins with and ends with are not available for lists (such as tags) with the rule editor that Apple provides, but maybe we can work around that.
2: Offering a menu might be possible. Regarding hot-linking for renaming: that is something that Guten Tag might do, but if you rename tags manually (i.e. not using the dedicated Rename feature of Guten Tag), than that would register as deleting a tag and creating a new tag, since that is what you would habe to do to rename a tag manually. Such manual renaming would not be recognized by the smart filters as a rename.
3: Control-click or richt-click a glyph in Font View and you will see all tags of the font in the Tags menu (see page 84 of the Glyphs Handbook for details). A better overview of all tags in a font is in the works, but I cannot give you a timeline for that.

Convoluted but works perfectly! Looks like it gets boiled down into a Custom filter NOT tags CONTAINS "name_of_tag". The other options are probably less important but I guess a lot comes down to tag organization.

Thanks for the info! Great plugin and looking forward to using it more.


[DO NOT MERGE] fix: getting npm publish from CI working

Codecov Report

Merging #296 (02b5c73) into main (868867b) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #296   +/-   ##
=======================================
  Coverage   89.48%   89.48%
=======================================
  Files          34       34
  Lines        1217     1217
  Branches      273      273
=======================================
  Hits         1089     1089
  Misses        125      125
  Partials        3        3

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 868867b...02b5c73. Read the comment docs.


Train costume dataset

Hello, Thank for your great work and open source selflessly.
I repclace coco dataset with my dataset, which without segmentation annotation, some error happened.
  File "/fastdata/computervision/liuxingyu/shared/projects/pose_estimation/DEKR/tools/../lib/dataset/COCOKeypoints.py", line 47, in __getitem__
    mask = self.get_mask(anno, image_info)
  File "/fastdata/computervision/liuxingyu/shared/projects/pose_estimation/DEKR/tools/../lib/dataset/COCOKeypoints.py", line 110, in get_mask
    obj['segmentation'], img_info['height'], img_info['width'])
KeyError: 'segmentation'

Could I replace segmentation with bbox annotation and then to train ? Will it affect model badly ?

Hi, you do not need the mask for your dataset, it does not influence the performance.

Thanks, I got it.


fix error nav menu mobile

hello, i fix responsive nav menu mobile

Hi, there is a template that shows up when you create a pull request similar to the image. It should be filled in with the change being made and linked to an open issue. You link them using the # sign followed by the issue number. You may create an issue to adds value to the site, but please keep the scope smaller. In this pr you are changing 7 files and it is hard to see what is going on. Also, the menu on the left is yours and looks out of alignment compared to how the right is centered.

Since there has been no communication on this, I am closing for now. Feel free to retry a pr with a linked issue and small change.


Added Greek Language

I added translation for "Modern Greek" (Greek) language here.

I will make sure to update the translation now, whether I am not sure how to actually update my fork without the merging commit appearing.

Duplicate of #6.


Fix broken link

https://github.com/driftyco/ionic/issues/7820

@jgw96 close my PR please, @brandyscarney fix it here https://github.com/driftyco/ionic-site/issues/768


Install IVT Vent 202

Describe the bug
I'm trying to install a IVT Vent 202 which I have installed a IP-module in. But there is a problem when Im installing it in HA.
To Reproduce
Install integration and configure IVT account data using XMPP. (tried HTTP as well)
Expected behavior
The installation to go thru without error.
Screenshots

Version

HA version 2021.9.7
HA Bosch component version v0.15.1
Python Bosch HTTP client version?

** Debug SCAN **
http://jsonblob.com/893474473148432384
Additional context
Log when I did the Debug scan

HA Log message
This error originated from a custom integration.
Logger: custom_components.bosch
Source: custom_components/bosch/init.py:246
Integration: Bosch thermostat (documentation, issues)
First occurred: 14:22:48 (1 occurrences)
Last logged: 14:22:48
Cannot connect to Bosch gateway, host 855362261 with UUID: None
This error originated from a custom integration.
Logger: custom_components.bosch
Source: custom_components/bosch/init.py:244
Integration: Bosch thermostat (documentation, issues)
First occurred: 14:22:48 (1 occurrences)
Last logged: 14:22:48
Your device is unknown null
Logger: bosch_thermostat_client.gateway.ivt_gateway
Source: /usr/local/lib/python3.9/site-packages/bosch_thermostat_client/gateway/ivt_gateway.py:98
First occurred: 14:22:47 (2 occurrences)
Last logged: 14:22:48
I cannot find supported device. Your devices: null

scan is empty. What IP module do you have? What app do you use to control it?

I'm using this IP-module https://jsenergi.com/koppla-upp-din-varmepump/ivt-franluftsvarmepump/ip-modul-rego-2000-ivt-geo-ivt-vent.html
And the app that I'm using is IVT Anywhere.

I think this one uses different protocol. Maybe you are able to sniff to what server module is connecting and if it uses xmpp as protocol (port 5222).

Haven't done it before but I'll give it a try. Are you using Wireshark when sniffing?

Have bout an EMS gateway because I couldn't connect to the gateway


simplifying the python environment creation on windows

Thank you for the great work and for sharing this code.
I simplified the environment creation process on my machine by using conda to install the cuda toolkit dlls and binaries. This also has the advantage it creates a self-contained environement that does not interfere with other cuda installations on the machine. Maybe this could be integrated in this repository?
I added diff-gaussian-rasterization as a git submodule to this repo using
git submodule add https://github.com/graphdeco-inria/diff-gaussian-rasterization.git third_party/diff-gaussian-rasterization

then added an  environment.yml file with
name: splatter_image

channels:
  - pytorch
  - defaults
  - nvidia/label/cuda-11.8.0
  - conda-forge

dependencies:
  - python=3.10
  - cuda-version=11.8
  - cuda-toolkit=11.8
  - pip=24.0
  - pytorch=2.0.0
  - plyfile
  - torchaudio
  - torchvision
  - tqdm
  - pip:
    - third_party/diff-gaussian-rasterization
    - -r requirements.txt
variables:
  CUDA_PATH: ""

and final added a script install_on_windows.bat with
git submodule init
git submodule update --init --recursive
set DISTUTILS_USE_SDK= 1
set CUDA_PATH=
call "C:\Program Files\Microsoft Visual Studio\2022\Enterprise\VC\Auxiliary\Build\vcvars64.bat"
conda env create --file environment.yml

This is great @martinResearch - thanks a lot! I'll try to integrate it in the main repo.


Website is down (wrong status)

All systems are operational:
https://dogchef-be.github.io/uptime-monitor
Website is down (wrong status):
https://dogchef-be.github.io/uptime-monitor/history/erp

Looks like two sites are indeed down on the hompage, but the summary says "All systems operational". Super weird!

Could it be that it's because you don't use the README.md feature and the "All systems operational" text is fetched from the repository's README?

Could it be that it's because you don't use the README.md feature and the "All systems operational" text is fetched from the repository's README?

But the website isn't down as it says.. In fact, it has 2 resolved incidents.

Another one that doesn't refresh the status:

Thanks for the follow up! I'll definitely investigate as soon as I have some time.

Np! Many thanks 👍🏻

We're seeing this too at https://status.materialsproject.org

I have the same problem. In different times says that my domain is down, but on manual check i have good response.

Strangely, for us, the logs suggest status is up and skips committing anything, nevertheless a "Complete outage" is reported in the README. Log below.
 Will investigate!

Hello to all,
i got the same problem when i add the bellow settings on the .upptimerc.yml
commitMessages:
  readmeContent: ":pencil: Update summary in README [skip ci] [Something Other]"
  summaryJson: ":card_file_box: Update status summary [skip ci] [Something Other]"
  statusChange: "$EMOJI $SITE_NAME is $STATUS ($RESPONSE_CODE in $RESPONSE_TIME ms) [skip ci] [Something Other]"
  graphsUpdate: ":bento: Update graphs [skip ci] [Something Other]"

Then my monitors goes down on the github while the sites was all operational.
I dont know if this is the issue.. but i just add my opinion to help peoples!
Thanks,
Ioannis


v18.1.6 - delegate skeleton for multisig

adds makeDelegate function for stx over btc wire formats

~the wire format in SIP-015 might be incorrect, seems the last bit-length is off (see comment below)~ using same wire-format as rust code (u64 as last part)

CC @donpdonp

I'm getting build errors (during browserify) due to the stacks.js include:
$ npm run build

><EMAIL_ADDRESS>build
> npm run compile && npm run browserify

><EMAIL_ADDRESS>compile
> rm -rf lib; babel src -d lib

Successfully compiled 48 files with Babel (1864ms).

><EMAIL_ADDRESS>browserify
> ./node_modules/.bin/browserify lib/index.js --standalone blockstack -o ./dist/blockstack.js

/Users/aaron/devel/stacks.js/node_modules/@stacks/transactions/dist/transaction.js:20
                ...payload,
                ^
ParseError: Unexpected token

I tried updating the babel dependencies, which improved the error message slightly:
diff --git a/.babelrc b/.babelrc
index 6bd4d284..900e2920 100644
--- a/.babelrc
+++ b/.babelrc
@@ -1,11 +1,9 @@
 {
-  "presets": ["env", "flow"],
+  "presets": ["@babel/preset-env", "@babel/preset-flow"],
   "plugins": [
-    ["transform-runtime", {
+    ["@babel/transform-runtime", {
       "helpers": false,
-      "polyfill": false,
       "regenerator": true,
-      "moduleName": "babel-runtime"
     }]
   ]
 }
diff --git a/package.json b/package.json
index 589bf3ca..df19fe23 100644
--- a/package.json
+++ b/package.json
@@ -78,14 +78,14 @@
     }
   ],
   "devDependencies": {
-    "babel-cli": "^6.26.0",
+    "@babel/cli": "^7.21.0",
     "babel-eslint": "^8.2.5",
-    "babel-plugin-transform-runtime": "^6.23.0",
-    "babel-polyfill": "^6.26.0",
-    "babel-preset-env": "^1.7.0",
-    "babel-preset-flow": "^6.23.0",
+    "@babel/plugin-transform-runtime": "^7.0.0",
+    "@babel/polyfill": "^7.12.0",
+    "@babel/preset-env": "^7.0.0",
+    "@babel/preset-flow": "^7.0.0",
     "blue-tape": "^1.0.0",
-    "browserify": "^13.1.1",
+    "browserify": "^17.0.0",
     "documentation": "^8.0.0",
     "eslint": "^4.19.1",
     "eslint-config-airbnb": "^17.0.0",

Ah sorry, I removed the stacks.js deps -- after reading the rust part I realized this wasn't needed (I think)
Pushed the latest (which I thinks works for tests), at least the tx are able to broadcast to testnet.

Ready for a final review -- First tx worked and I'm testing more variations tomorrow.


AssetFinder does an is check against strings

https://github.com/quantopian/zipline/blob/master/zipline/assets/assets.py#L605
https://github.com/quantopian/zipline/blob/master/zipline/assets/assets.py#L280
https://github.com/quantopian/zipline/blob/master/zipline/assets/assets.py#L283
This is almost certainly not what we want to be doing. The is operator means "is the same PyObject pointer".  Though strings are generally interned, it's not guaranteed that two strings that compare equal are actually the same object.  Consider:
In [9]: "None" == "None"
Out[9]: True

In [10]: "None" is "None"
Out[10]: True

In [11]: "None" == ''.join(['N', 'o', 'n', 'e'])
Out[11]: True

In [12]: "None" is ''.join(['N', 'o', 'n', 'e'])
Out[12]: False

cc @ehebert @jfkirk.  This is a time-bomb waiting to go off if we haven't hit it already.  cc @jdricklefs also in case this is related to some of the internal asset mapping failures we've seen recently.

Oh gosh, that is clearly wrong. Self-assigning.

Looks like the simple fix is to change to !=.
(Or we could remove placeholder support?)

PR for a fix: https://github.com/quantopian/zipline/pull/651
@ssanderson - I could only find the one bad check in the current Zipline master. Are there others that I missed?

Fix merged - closing.


[Changelog] Update for Sprint 100

[skip ci]

@miq-bot add_label documentation

@carbonin as time permits, can you review/merge.


[proposal] Add full screen support

This is a very impressive plugin, and I had a lot of fun with it! However, if the preview has the full-screen feature, it can even be used as a screen saver.

I took a closer look at this, and from what I can see there is no good way of doing this with the current bundled version of electron. The associated chrome version is quite old and doesn't support the standard web API for fullscreen and the webkit API doesn't work properly from my tests. And even if that is based on my mistake, I think it makes more sense to wait for the next bump in the electron version and try working with that.
Even then, it could still be that VSCode blocks fullscreen on the Webview panels, if that will be the case in the future I will talk with the devs and see what they are thinking.

Small update: With the newest version of VSC using the standardized fullscreen api just results in the VSC window to be fullscreen, not the webview itself. So this still doesn't look doable.


Publish container to registry such as DockerHub/Github

Is your feature request related to a problem? Please describe.
avoiding building the jscpd image, see #356 in order to run it inside container, by using already built image published in available registry, such as:
GitHub Package Registry https://github.com/features/packages
DockerHub https://docs.docker.com/docker-hub/publish/
Describe the solution you'd like
running command like:
docker run --rm -u jscpd --network none -t -v $(pwd):/jscpd/:ro
      [url-of-jscpd-image] ./

will run jscpd on current directory inside container.

unofficial docker image: https://github.com/hata6502/jscpd-docker


Fix Arbitary code execution  in crypto-signal

📊 Metadata *
Bounty URL: https://www.huntr.dev/bounties/1-other-Crypto-Signal/
⚙ Description *
Vulnerable to YAML deserialization attack caused by unsafe loading.
💻 Technical Description *
Fixed by avoiding unsafe loader.
🐛 Proof of Concept (PoC) *
Create the following PoC file:
exploit.py
# exploit.py
with open('defaults.yml', 'r') as config_file:
            default_config = yaml.load(config_file)
if os.path.isfile('config.yml'):
    with open('config.yml', 'r') as config_file:
        user_config = yaml.load(config_file)
#https://github.com/CryptoSignal/Crypto-Signal/blob/master/app/conf.py#L21
run exploit.py
# exploit.py
import os
#PAYLOAD SECTION
exploit = """settings: !!python/object/new:type
  args: ["z", !!python/tuple [], {"extend": !!python/name:exec }]
  listitems: "__import__('os').system('echo pwned')"
"""
os.system('rm -r config.yml')
open('config.yml','w+').write(exploit)
os.system('docker run --rm -v $PWD/config.yml:/app/config.yml shadowreaver/crypto-signal:master')

Execute the commands in another terminal:
python exploit.py

🔥 Proof of Fix (PoF) *
After fix it will not popup a calc.
👍 User Acceptance Testing (UAT)
After fix functionality is unaffected.
🔗 Relates to...
https://www.huntr.dev/bounties/1-other-Crypto-Signal/

👋 Hello, @jrbartola - @b1nslashsh has opened a PR to us with a fix for a potential vulnerability in your repository. To view the vulnerability, please refer to the bounty URL in the first comment, above.
Ultimately, you get to decide if the fix is 👍 or 👎. If you are happy with the fix, please write a new comment (@huntr-helper - LGTM) and we will open a PR to your repository with the fix. All remaining PRs for this vulnerability will be automatically closed.
If you have any questions or need support, come and join us on our community Discord!
@jrbartola & @b1nslashsh - thank you for your efforts in securing the world’s open source code! 🎉

👋 Hello, @jrbartola - @b1nslashsh has opened a PR to us with a fix for a potential vulnerability in your repository. To view the vulnerability, please refer to the bounty URL in the first comment, above.
Ultimately, you get to decide if the fix is 👍 or 👎. If you are happy with the fix, please write a new comment (@huntr-helper - LGTM) and we will open a PR to your repository with the fix. All remaining PRs for this vulnerability will be automatically closed.
If you have any questions or need support, come and join us on our community Discord!
@jrbartola & @b1nslashsh - thank you for your efforts in securing the world’s open source code! 🎉

hey @jrbartola
any update on this
regards
muhaimin


Add Readable and Writable futures

What happens if the Readable/Writable futures outlive the Async? Could that cause problems?

Hmm...
Error: Os { code: 9, kind: Other, message: "Bad file descriptor" }

In this case, the error is expected behavior, but I think I should have left a reference to self to prevent users from writing such code...
async-net's TcpStream and UnixStream wraps the Async in Arc, so it would have made more sense to add a method like readable_owned that takes self: &Arc<Self> instead...
1.5.0 has only been released about 2 hours ago, so I'll yank 1.5.0...
@Kestrer Thanks for catching this problem.

Oh no, is there no way to support this? Would it be possible to for example perform a check if the resource has been unregistered and have Readable error out?

@Kestrer

Would it be possible to for example perform a check if the resource has been unregistered and have Readable error out?

I think it is possible, but I would like to provide an API that prevents such error if possible.
In fact, the error that occurs, in that case, can be easily reproduced by more low-level libraries such as polling, so this PR's API is not necessarily bad. So, we could simply add documentation that says "If writable/readable polled after Async dropped, it will result in an error", but I tend to think it is better if this could be prevented at compile time...
(I'm still not convinced it's worth the breaking change, but we found the problem fast enough that I didn't have to worry about the impact of the breaking change, so I yanked it anyway. Sorry if anyone else is affected by this yanking!)

And here is the API & implementation I'm thinking of: https://github.com/smol-rs/async-io/compare/master...taiki-e/owned
(TR; DR: change Readable and Writable to contain a reference to Async, and add Async::{readable_owned, writable_owned} that take self: &Arc<Self>)
I'm not sure about other use cases where this feature was needed, but it is enough for the async-net use case (https://github.com/smol-rs/async-net/compare/master...taiki-e/owned),
@Kestrer @smol-rs/admins Any thoughts on this?

I think this is a good idea. {readable, writable}_owned should probably take Arc<Self> to reduce unnecessary cloning. And it might be cleaner to implement it using a generic AsRef<Source>, implemented by both Arc<Async> and &Async.

Filed #66. Thanks @Kestrer for the feedback!


Make encoded biscuit editable and block display not editable in bc-token-printer

The <code> block could be turned into a <textarea>, so that people can paste tokens to inspect them. Following the same idea, the blocks displaying datalog should not be editable (since the encoded token can't be re-created). Using the editor is still useful though (unless there is a simple way to get line numbers and syntax highlighting without an editor).
Idk if it's doable to plug authorization to the token printer in the current state of things, but that would be a nice addition to a printer with user input.

Done in https://github.com/biscuit-auth/biscuit-web-components/pull/5


Juno keeps missing blocks without logging and enqueuing again

We keep experiencing miss blocks and those blocks were not logged and enqueued again meaning that those blocks were not in the queue from the beginning.
As new blocks are all enqueued to the worker's queue by listening NewBlock event, it is suspected that blocks will be not enqueued correctly if the node is not responding properly and the Tendermint event is not broadcasted correctly.
Can this be refactored so that JUNO optimistically enqueues all blocks not exist in the database? For example, if the largest block height in the database is H, and the latest block height on chain is H+10,  it enqueues H+1 to H+10 in the queue without listening to the websocket event?

@MonikaCat @huichiaotsou can you take a look and see if this is the root cause for missing blocks? It's not acceptable that some low traffic chains like Agoric would be missing blocks.


unified objects hierachy

Currently, some objects in Easegress belong to a namespace (TrafficGates and Pipelines), and we need to use /<namespace>/<object>/<id> to access their information, while other objects do not belong to a namespace, and we use /<object>/<id> to access their information.
The idea is to put all objects into a namespace, this is to say, we move objects currently not belonging to a namespace to the default namespace.

We fixed X problem in https://github.com/easegress-io/easegress/pull/1197


Unable to cross-compile for aarch64

I've installed Ubuntu 20.04 on a Raspberry 4 and I'm trying to cross-compile a Mediapipe app that uses OpenCV from a Docker container running on Ubuntu 18.04.
I've copied the opencv_*.so files from /usr/lib/aarch64-linux-gnu/ on the Raspberry to `/usr/lib/aarch64-linux-gnu/' in the container.
My third_party/opencv_linux.BUILD looks like:
cc_library(
    name = "opencv",
    srcs = glob(
        [
            "lib/aarch64-linux-gnu/libopencv_core.so",
            "lib/aarch64-linux-gnu/libopencv_calib3d.so",
            "lib/aarch64-linux-gnu/libopencv_features2d.so",
            "lib/aarch64-linux-gnu/libopencv_highgui.so",
            "lib/aarch64-linux-gnu/libopencv_imgcodecs.so",
            "lib/aarch64-linux-gnu/libopencv_imgproc.so",
            "lib/aarch64-linux-gnu/libopencv_video.so",
            "lib/aarch64-linux-gnu/libopencv_videoio.so",
        ],
    ),
    hdrs = glob(["include/opencv2/**/*.h*"]),
    includes = ["include/"],
    linkstatic = 1,
    visibility = ["//visibility:public"],
)

When I run:
bazel build -c opt --crosstool top=@crosstool//:toolchains --compiler=gcc --cpu=aarch64 --define MEDIAPIPE_DISABLE_GPU=1 --define 'libunwind=true' mediapipe/examples/desktop/hand_tracking:hand_tracking_cpu

I get the error:
INFO: Analyzed target //mediapipe/examples/desktop/hand_tracking:hand_tracking_cpu (1 packages loaded, 59 targets configured).
INFO: Found 1 target...
ERROR: /mediapipe/mediapipe/examples/desktop/hand_tracking/BUILD:27:1: Linking of rule '//mediapipe/examples/desktop/hand_tracking:hand_tracking_cpu' failed (Exit 1) aarch64-linux-gnu-gcc failed: error executing command /usr/bin/aarch64-linux-gnu-gcc @bazel-out/aarch64-opt/bin/mediapipe/examples/desktop/hand_tracking/hand_tracking_cpu-2.params

Use --sandbox_debug to see verbose messages from the sandbox
bazel-out/aarch64-opt/bin/mediapipe/examples/desktop/libdemo_run_graph_main.a(demo_run_graph_main.o):demo_run_graph_main.cc:function cv::Mat::~Mat(): error: undefined reference to 'cv::fastFree(void*)'

Has anyone any idea on how to make it work?

Have you take a look at the coral build instructions (seems likely)?   Most of that process would apply here.
Do you have the exact same opencv version installed in both places?
Does compiling just the hello_world work?
It seems to be a linker issue, so please double check that the libs are copied correctly (sometimes symlinks cause issues).
The raspberry pi 4 should be powerful enough (i.e. enough RAM) to compile directly on the device, if that is an option for you.. (the main issue is bazel needs lots of RAM. it's been done on coral 1GB devices too, by specially allocating HD space as extra ram).

Thanks for your help @mcclanahoochie I ended up spotting the error: I was adding the new_local_repository in the wrong file! Maybe I skimmed the docs here a bit too fast :) Once I moved that rule to the right place (mediapipe/WORKSPACE, not mediapipe/third_party/opencv_linux.BUILD) and fixed a compiler issue re the zlib directory (issue #1406), it all worked out fine.
The only problem I'm facing now is that there's a 3-4s lag and the fps is very low when I compile the desktop/hand_tracking example for my Raspberry Pi 4 (running on Ubuntu 20.04). I'm wondering if I'm using the edge tpu capabilities correctly.
Here's my compile command:
bazel build -c opt --crosstool_top=@crosstool//:toolchains --compiler=gcc --cpu=aarch64 --define MEDIAPIPE_DISABLE_GPU=1 --copt -DMEDIAPIPE_EDGE_TPU --copt=-flax-vector-conversions mediapipe/examples/desktop/hand_tracking:hand_tracking_cpu

Any advice on how to increase computing speed with the Coral USB key for that hand tracking example?

Glad you got things running.
I don't think the hand_tracking model is fully supported by coral. Also, the coral TPU requires the model to be converted to 8bit and then recompiled from that into a new edge_tpu file; I guess you have done that?
Double check the logs, because I doubt the usb stick is being used, and if it is, only a few ops are actually running on the accelerator. Unless there has been an update to the coral edge tpu compiler (which is possible), we found there are some ops used in the hand tracking/detection models that were not supported by edge TPU, then delegating those ops (an all following) to the CPU.
So, my suspicion is that the model is just running 100% on the cpu if you haven't recompiled for edge tpu, and if you have, then probably there are unsupported ops preventing running fully on TPU.

The face and object detection examples work perfectly and way faster than the hand tracking one but your suspicions are correct: I haven't converted the tflite to an 8bit one. I'll keep you posted if anything arides when I try so! Still pretty impressed by the relative speed you can get when running the current tflite model on a simple raspberry CPU though. Thanks for the support!

@garyscetbon @mcclanahoochie

@garyscetbon @mcclanahoochie
Hey guys, I am trying to cross compile mediapipe for raspberrypi 4 with Raspbian 32-bit (armhf), but I keep getting linking errors.
I installed opencv libs with armhf on my host machine (ubuntu 18.04 amd64) and modified opencv_linux.BUILD (lib/arm-linux-gnueabihf). By doing so I managed to link libopencv files, however, the linker could not find lib files required by opencv. So I had to add linkopts to opencv_linux.BUILD. Eventually I got
linkopts = [         "-Wl,-rpath-link=/usr/lib/arm-linux-gnueabihf",         "-Wl,-rpath-link=/usr/lib",         "-Wl,-rpath-link=/lib/arm-linux-gnueabihf",         ],
This solved most of the link errors, but finally I got std link errors which do not know how to sovle.


Moving logError from cli to usage-data

Moving logErrorMessage from "office-addin-cli" to "office-addin-usage-data".

Added a commit to also fix packages vulnerabilities.
Ran npm run audit:fix

Added a commit to also fix packages vulnerabilities. Ran npm run audit:fix

Should do the fix in a separate PR (I'll work on that) and publish a patch version of the packages.  This kind of change (moving calls from different packages) will require a major version updated (breaking change) and we don't want to hold up vulnerability fixes for that (i.e. major version changes in customer projects are more involved than minor version changes).

Added a commit to also fix packages vulnerabilities. Ran npm run audit:fix

Should do the fix in a separate PR (I'll work on that) and publish a patch version of the packages. This kind of change (moving calls from different packages) will require a major version updated (breaking change) and we don't want to hold up vulnerability fixes for that (i.e. major version changes in customer projects are more involved than minor version changes).

Actually . . . it looks like we need a major version update for some other changes (linting, mock, etc.) anyway.  But the vulnerabilities should still be fixed in a different PR to keep this one simple and to the point.

Just reverted the upgrade commit. PR is ready to be reviewed now

I'd like to understand the motivation for this PR.

We would like to be adding new commands to office-addin-cli. It would work as a general package that could house some new generic commands.
To do this, it is necessary for office-addin-cli to import office-addin-usage-data in order to have telemetry.
The problem is that office-addin-usage-data imports office-addin-cli because of the method logError, which is a very generic method. This causes a circular dependency that Lerna doesn't like.
This PR aims to move this logError function from office-addin-cli to office-addin-usage-data, in order to also avoid future circular dependency problems.

Added an deprecated to logError in office-addin-cli. This way we don't need to do any major updates, as the function still exists.
@millerds PR is ready to be reviewed.


Add more contributing info

Based on https://github.com/nayafia/contributing-template

We also need to update the docs site with this and other information. Because this needs to be done sooner than later and people are already wanting to contribute/contributing; I'll pick this up and try to get it done ASAP.

Perfect, thanks!

Added in #86. docs website will be updated soon - but that issue doesn't belong here.


Update Timex to avoid Elixir v1.3 warnings

Timex has been updated to avoid compilation warnings on v1.3, so it'd be nice for Quantum to use their v2.2.x

Coverage remained the same at 100.0% when pulling 43a25a445ec4b5e027f332364e00c924385aa459 on zackehh:patch-1 into 36e1ddea71cc0b36698599bae253cb6a64f112c5 on c-rack:master.

Thanks!


building queue for multiselect

hello, in the game, when you multi select a training buiding you can see the size of the building queue for all buildings selected. the queue is only include the size of the queue for each building selected.
is there any way to retrieve this information through pysc2 environment?
thanks

Hi @natangold85 ,
As you might know, pySC2 mimics human playing behaviour.
When you play Starcraft II , I think you should select each building to build units.
You can do the following

Select all buildings and see queues
Select the building
Build the unit

Please let me know if this answer your question .
Thanks!

When you play Starcraft II , I think you should select each building to build units.

Not necessarily. You can select group of buildings (multy select) or use a control group and click 'train something' button. The game will distribute your orders among the selected buildings.

Then is a game-bug right ?

this option is available in the star craft2 game. i don't know if the bug is in the blizzard interface or yours but when you train unit in multiselect the training is distibuted equally in the selected buildings. try it and see.
thanks

This is the same bug that is fixed in 4.6.0.


Update shell_only.ts

Change the icon name 'SHUFFLE_OFF' because it is named incorrectly

Fixed no shuffle issue

Change the icon name 'SHUFFLE_OFF' because it is named incorrectly


[BUG] Approved label CI does not add approved label to pull requests.

Description
As the title suggests the approved label CI does not add approved label to the pull requests
Expected behavior
add an approved label when the pull request is approved
Actual behavior
403 unable to access resource
Steps to reproduce
No response
Context
hard to distinguish which prs are approved.
Additional information
Its a really simple fix, easy as adding
permissions:
   pull_request: write

to the workflow further reading

please assign me this issue

please assign me this issue

How are you going to fix this issue?
From my research it looks unsolvable via actions and I'm currently in the process of making a GitHub bot


Is there a way to keep the author sidebar in the mobile version?

I have modified a website in a hacky way such that there is another menubar in the author sidebar.
But now it disappears in mobile.
Is there a way to just stack it on the top in the mobile view?

Anything is possible if you know enough CSS to pull it off.

If you want just to stack it on the top I think you can just remove the display: none from .article-author-side and fix the grid on it (use other elements as a example).


Address color-similarity issue

Because we are using fixed colors for the forecasters (so they don't change when the plot updates) and because we are using colorblind friendly colors, many of the forecasters have really similar colors and are hard to differentiate.
We could include a reshuffle colors button, so when you have selected the forecasters you want to see, you can press the button and it will redistribute the colors in a better way so you can tell the forecaster lines apart.
We could also add different line types and see if that mostly solves the problem.

Added different linetypes, issue not as high priority now.


Opt-in instead of opt-out

One of the things that currently bothers me in semanticolor is the fact that it is enabled by default in all my languages. That basically breaks the highlighting in e.g. templating languages where semantic coloring only makes things harder to understand.
Would it be possible to disable the module by default for every language, and have the user enable it on a one-by-one basis? Or at least have a whitelist of languages where the module is known to work fine.
Otherwise, thanks for this great module!

There is a blacklist for languages that are known to not work (currently not configurable, though). What grammars don't work? I can add to it and maybe make it configurable.

The ones I've blacklisted so far: JSON, YAML, Dockerfile, Pug, SCSS, CSS.

Added JSON and Dockerfile to blacklist in 3.5.0. I like using CSS and LESS with semanticolor. With YAML you get good results if you set the "Source" setting to "mute". Haven't tried Pug or SCSS. Maybe those languages would work better with the addition of settings for scopes that aren't currently configurable? Use the "Log Cursor Scopes" command from the command palette to figure out if there's a scope that could be configured that would help you get the settings you want. If you find any, let me know here.

Pug (formerly Jade) is a markup language semantically similar to HTML. It's a real punch in the eye using atom with semanticolor on pug/jade files.
I currently disabled semanticolor just to be able to work with pug files, but would love any kind of other solution.
What are my other options?

Just disable that syntax in the semanticolor settings.

Thanks, I managed to disable semanticolor.
I had to reload atom twice: once for semanticolor to list pug among the languages, and the second time to re-enable the default style after disabling semanticolor.

After updating, I have the opposite problem - how do I make it the default? Every file I open, I have to manually select Semanticolor for the grammar.

It should default to semanticolor for any grammar Semanticolor has enabled. After I updated I had to restart Atom before it behaved correctly. Let me know if that doesn't work.

Yeah, I've restarted it twice now and it's not being used by default.

Yeah, I've restarted it twice now and it's not being used by default.

What language?

Python and JavaScript.

Python and JavaScript.

Do you have Tree Sitter parsers enabled? (Settings -> Core -> Use Tree Sitter Parsers)

That fixed it, thanks!


feat: upgrade @xmldom/xmldom to v0.9.5

I've upgraded @xmldom/xmldom to 0.9.5 and added the types to allow both DOM and xmldom Element/Node/Document. Otherwise the parsing result of the new versions wouldn't be accepted. I'm not sure if there would be a smoother path? Looks weird on the Docs like Document | Document 🤔.
Otherwise I only had to switch Array.from() to [...].

Might also be this problem gets resolved by https://github.com/xmldom/xmldom/issues/724.

This is a little problematic: xmldom/xmldom in this PR is still in devDependencies, so it is not guaranteed to be installed when togeojson is installed as a dependency, which will potentially cause an issue when the generated typescript types for this package refer to xmldom/xmldom. So we'd have to include @xmldom/xmldom types, which would bump up this package's dependencies by 156kb.
I think in the medium term, only taking the part of this PR that switches from Array.from to spread syntax would be the best tradeoff, and if xmldom doesn't make a change then people could use as unknown to cast to the xmldom desired types.

The array spread is also only to resolve type issues.
Wise consideration regarding dependency size. If we keep only import type (removing one value import for the Node Type enum) and move from devDependencies to dependencies it shouldn't harm browser users and only add to developers node_module size. What do you think about this approach?
I think for xmldom to have stricter types is the right move. So using the types within the lib might help to limit to the available functions. And having to use unknown when xmldom is the recommended parser feels a bit off.

I've updated with my proposal. Another possibility would be to add xmldom as an optional peer dependency. This would require TypeScript users to install xmldom.

I'm not sure about this overall - it'll take some testing to figure out that if this package introduces @xmldom/xmldom as an optional peer dependency and someone doesn't have it installed, what typescript will do. I suspect TS might produce an error in that case.
Adding @xmldom/xmldom to dependencies doesn't feel right - users shouldn't pay for the package download when they might not even use the provided types. Part of this module's basic premise is that it's zero-deps and tiny, and introducing a big dep would really change that equation.
I'll think about it some more, but having as Document as a recommended strategy might be a little rough but basically have the right tradeoffs. Ideally though xmldom would just produce a compatible Document type :/


multiple worksarea?

hello it is possible to have multiple work areas in the same window?

@cflorioluis no


Bad state: Future already completed

Hi Kilian Schulte!
First I would like to thank you for this package. It seems to me better package among its concurrents especially when we need relationships.
here some suggestion from me. may be they are already implemented but I could not find them.

[ ] default value in models accessors (to fill updatedAt, createdAt automatically and many other cases)
[ ] using postgresql data types in models (now string converts text which is unwanted in many cases)
[ ] Queries & Actions classes with table name in it (e. db.alerts.query(query, params) I would like to have 'alerts' in query without passing it)

Here the issue which makes me create an issue I noticed the strange behaviour.
@Model(
  indexes: [
    TableIndex(name: 'user_id_alerts_index', columns: ['user_id'])
  ],
  views: [#Complete, #Reduced],
)
abstract class Alert {
  @PrimaryKey()
  @AutoIncrement()
  int get id;

  @HiddenIn(#Reduced)
  User get user;

  String get message;
  String? get path;
  bool get isRead;
  bool get isImportant;
  int get statusIndex;
  DateTime get createdAt;
  DateTime get updatedAt;
}

final db = Database(
  host: '<IP_ADDRESS>',
  port: 5432,
  database: 'xyz',
  user: 'xyz',
  password: 'xyz',
  useSSL: false,
);

void main() async {
  try {
    seeds();
  } catch (e) {
    print(e);
  }
}

AlertInsertRequest _getAlertInsertRequestInstance({
  required int userId,
  required String message,
  required int statusIndex,
  required bool isImportant,
  String? path,
}) {
  return AlertInsertRequest(
    userId: userId,
    message: message,
    statusIndex: statusIndex,
    isImportant: isImportant,
    path: path,
    isRead: false,
    updatedAt: DateTime.now().toUtc(),
    createdAt: DateTime.now().toUtc(),
  );
}

void seeds() async {
  firstInsert();
  secondInsert();
}

void firstInsert() async {
  var notId = await db.alerts.insertOne(
    _getAlertInsertRequestInstance(
      userId: 1,
      message: 'Ride #3 rejected.',
      statusIndex: NotificationStatus.warning.v,
      isImportant: true,
    ),
  );
  print('1: $notId');
}

void secondInsert() async {
  var notId = await db.alerts.insertOne(
    _getAlertInsertRequestInstance(
      userId: 2,
      message: 'Passenger #1 rejected from ride #3.',
      statusIndex: NotificationStatus.warning.v,
      isImportant: false,
    ),
  );
  print('2: $notId');
}

Output Details

Bad state: Future already completed
#0      _AsyncCompleter.complete (dart:async/future_impl.dart:41:31)
#1      Database.cancelTransaction (package:stormberry/src/core/database.dart:139:27)
#2      Database.runTransaction (package:stormberry/src/core/database.dart:171:7)

#3      secondInsert (file:///Users/vfiruz/Desktop/rohtj/backend/rohtj_server_grpc/seed/test.dart:58:15)

if I comment out secondInsert then it works.
If I make the returning type Future for firstInsert, secondInsert functions and use await before them then it works
if you could to check it out or explain what was the reason.
The reason not to make future and await sequently is that I want to reduce server response.
run someInserts without waiting and return server response.
and wondering to use some instance of Database class, is it possible?
Thanks!

Thanks, this seems like a bug with handling the transactions. I will take a look (prob next week).

This is fixed in the new version (0.14.0). There the generated methods no longer run their own transaction, instead you manage the transaction yourself and can call multiple operations in one transaction.


timeout starting docker service in vagrant box

i've setup kubernetes via vagrant provider and seems the process does not get past starting up docker service on master.
when i started it again, i saw mkfs.ext4 to run, mostly in D state, and then again docker service startup timed out.
[vagrant@kubernetes-master ~]$ systemctl status -l docker.service
docker.service - Docker Application Container Engine
   Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled)
   Active: activating (start) since L 2015-05-30 07:36:17 UTC; 1min 24s ago
     Docs: http://docs.docker.com
 Main PID: 2786 (docker)
   CGroup: /system.slice/docker.service
           ├─2786 /usr/bin/docker -d --selinux-enabled
           └─2806 mkfs.ext4 -E nodiscard,lazy_itable_init=0,lazy_journal_init=0 /dev/mapper/docker-253:1-1836554-base

[vagrant@kubernetes-master ~]$ ps axwuf
...
root      5579  1.4  1.0<PHONE_NUMBER>0 ?        Ssl  07:49   0:00 /usr/bin/docker -d --selinux-enabled
root      5595  0.3  0.1 120948  1200 ?        D    07:49   0:00  \_ mkfs.ext4 -E nodiscard,lazy_itable_init=0,lazy_journal_init=0 /

[vagrant@kubernetes-master systemd]$ systemctl status -l docker.service
docker.service - Docker Application Container Engine
   Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled)
   Active: failed (Result: timeout) since L 2015-05-30 07:38:55 UTC; 5min ago
     Docs: http://docs.docker.com
 Main PID: 2786

mai   30 07:36:17 kubernetes-master docker[2786]: time="2015-05-30T07:36:17Z" level="info" msg="+job serveapi(unix:///var/run/docker.sock)"
mai   30 07:36:17 kubernetes-master docker[2786]: time="2015-05-30T07:36:17Z" level="info" msg="Listening for HTTP on unix (/var/run/docker.sock)"
mai   30 07:37:47 kubernetes-master systemd[1]: docker.service operation timed out. Terminating.
mai   30 07:38:55 kubernetes-master systemd[1]: Failed to start Docker Application Container Engine.
mai   30 07:38:55 kubernetes-master systemd[1]: Unit docker.service entered failed state.
[vagrant@kubernetes-master systemd]$

i could not find any timeout param in systemd config:
[vagrant@kubernetes-master systemd]$ cat /lib/systemd/system/docker.service
[Unit]
Description=Docker Application Container Engine
Documentation=http://docs.docker.com
After=network.target

[Service]
Type=notify
EnvironmentFile=-/etc/sysconfig/docker
EnvironmentFile=-/etc/sysconfig/docker-storage
EnvironmentFile=-/etc/sysconfig/docker-network
ExecStart=/usr/bin/docker -d \
          $OPTIONS \
          $DOCKER_STORAGE_OPTIONS \
          $DOCKER_NETWORK_OPTIONS \
          $INSECURE_REGISTRY
LimitNOFILE=1048576
LimitNPROC=1048576
LimitCORE=infinity
MountFlags=slave

[Install]
WantedBy=multi-user.target
[vagrant@kubernetes-master systemd]$

nor where the mkfs.ext4 was called. it seems to be embeded in docker binary:
[vagrant@kubernetes-master ~]$ rpm -ql docker-io|xargs grep mkfs.ext4 2>/dev/null
Binary file /usr/bin/docker matches
[vagrant@kubernetes-master ~]$

when i started docker from console, i see ps listing as:
[vagrant@kubernetes-master ~]$ ps axwuf|grep dock
root      6001  0.1  0.2 187264  2728 pts/0    S+   07:52   0:00  |           \_ sudo /usr/bin/docker -d --selinux-enabled
root      6004  1.4  0.9 218116  9728 pts/0    Sl+  07:52   0:00  |               \_ /usr/bin/docker -d --selinux-enabled
root      6021  0.4  0.1 120948  1204 pts/0    D+   07:52   0:00  |                   \_ mkfs.ext4 -E nodiscard,lazy_itable_init=0,lazy_journal_init=0 /dev/mapper/docker-253:1-1836554-base
vagrant   6074  0.0  0.0 112664  1004 pts/1    S+   07:53   0:00              \_ grep --color=auto dock
root      6023  0.3  0.6 215808  6568 ?        Sl   07:52   0:00  \_ docker load -i /srv/salt/kube-bins/kube-apiserver.tar
[vagrant@kubernetes-master ~]$

output when docker started manually from console:
[vagrant@kubernetes-master ~]$ time sudo /usr/bin/docker -d --selinux-enabled
INFO[0000] +job serveapi(unix:///var/run/docker.sock)
INFO[0000] Listening for HTTP on unix (/var/run/docker.sock)
INFO[0241] +job init_networkdriver()
INFO[0242] -job init_networkdriver() = OK (0)
INFO[0243] Loading containers: start.

INFO[0243] Loading containers: done.
INFO[0243] docker daemon: 1.5.0 a8a31ef/1.5.0; execdriver: native-0.2; graphdriver: devicemapper
INFO[0243] +job acceptconnections()
INFO[0243] -job acceptconnections() = OK (0)
INFO[0243] POST /v1.17/images/load
INFO[0243] +job load()
INFO[0243] +job image_get(4986bf8c15363d1c5d15512d5266f8777bfba4974ac56e3270e7760f6f0a8125)
could not find image: no such id: 4986bf8c15363d1c5d15512d5266f8777bfba4974ac56e3270e7760f6f0a8125
INFO[0243] -job image_get(4986bf8c15363d1c5d15512d5266f8777bfba4974ac56e3270e7760f6f0a8125) = ERR (1)
INFO[0243] +job image_get(ea13149945cb6b1e746bf28032f02e9b5a793523481a0a18645fc77ad53c4ea2)
could not find image: no such id: ea13149945cb6b1e746bf28032f02e9b5a793523481a0a18645fc77ad53c4ea2
INFO[0243] -job image_get(ea13149945cb6b1e746bf28032f02e9b5a793523481a0a18645fc77ad53c4ea2) = ERR (1)
INFO[0243] +job image_get(df7546f9f060a2268024c8a230d8639878585defcc1bc6f79d2728a13957871b)
could not find image: no such id: df7546f9f060a2268024c8a230d8639878585defcc1bc6f79d2728a13957871b
INFO[0243] -job image_get(df7546f9f060a2268024c8a230d8639878585defcc1bc6f79d2728a13957871b) = ERR (1)
INFO[0243] +job image_get(511136ea3c5a64f264b78b5433614aec563103b4d4702f3ba7d4d2698e22c158)
could not find image: no such id: 511136ea3c5a64f264b78b5433614aec563103b4d4702f3ba7d4d2698e22c158
INFO[0243] -job image_get(511136ea3c5a64f264b78b5433614aec563103b4d4702f3ba7d4d2698e22c158) = ERR (1)
INFO[0245] +job image_get(511136ea3c5a64f264b78b5433614aec563103b4d4702f3ba7d4d2698e22c158)
INFO[0245] -job image_get(511136ea3c5a64f264b78b5433614aec563103b4d4702f3ba7d4d2698e22c158) = OK (0)
INFO[0245] +job image_get(b8f04e304b16b8d4545c6bd3c5e71c07fc0ac3b6d07c3303d4ca008e2a94f0ad)
could not find image: no such id: b8f04e304b16b8d4545c6bd3c5e71c07fc0ac3b6d07c3303d4ca008e2a94f0ad
INFO[0245] -job image_get(b8f04e304b16b8d4545c6bd3c5e71c07fc0ac3b6d07c3303d4ca008e2a94f0ad) = ERR (1)
INFO[0246] +job image_get(df7546f9f060a2268024c8a230d8639878585defcc1bc6f79d2728a13957871b)
INFO[0246] -job image_get(df7546f9f060a2268024c8a230d8639878585defcc1bc6f79d2728a13957871b) = OK (0)
INFO[0246] +job image_get(ea13149945cb6b1e746bf28032f02e9b5a793523481a0a18645fc77ad53c4ea2)
INFO[0246] -job image_get(ea13149945cb6b1e746bf28032f02e9b5a793523481a0a18645fc77ad53c4ea2) = OK (0)
INFO[0247] -job load() = OK (0)
INFO[0247] POST /v1.17/images/load
INFO[0247] +job load()
INFO[0247] +job image_get(5ab1e7ce693ec9909eda6b8bd2b9c536a4e76650ff4ef83ee2bcf6272c1add36)
could not find image: no such id: 5ab1e7ce693ec9909eda6b8bd2b9c536a4e76650ff4ef83ee2bcf6272c1add36
INFO[0247] -job image_get(5ab1e7ce693ec9909eda6b8bd2b9c536a4e76650ff4ef83ee2bcf6272c1add36) = ERR (1)
INFO[0248] -job load() = OK (0)
INFO[0249] POST /v1.17/images/load
INFO[0249] +job load()
INFO[0249] +job image_get(c9641eb3e74f56a6f02b7ea038c924a4f78996e94f86fd991f28360e3c8cbe83)
could not find image: no such id: c9641eb3e74f56a6f02b7ea038c924a4f78996e94f86fd991f28360e3c8cbe83
INFO[0249] -job image_get(c9641eb3e74f56a6f02b7ea038c924a4f78996e94f86fd991f28360e3c8cbe83) = ERR (1)
INFO[0251] -job load() = OK (0)

and even then, from ps listing, i think i saw it doing docker load -i /srv/salt/kube-bins/kube-apiserver.tar several times before it finally succeeded.

Were you able to get past this issue?  Did you see this multiple times when bringing up the cluster?  I know as of Thursday I was able to bring up a cluster from Head without issue.

#9093 was merged that upgraded vagrant to fedora 21 with docker 1.6
Can you test against HEAD to and re-open if you still need assistance?

thanks. will give a try as i couldn't get it working earlier and did not even know here to look. vagrant was starting point to learn how it works.

btw, had to run build/release.sh before could use HEAD version (which required docker installation)

i can confirm the previous problem (why i made this issue), is gone:
$ ./k8s.io.sh
...
==> minion-1: Importing base box 'kube-fedora21'...
...
==> minion-1:  *  INFO: Running install_fedora_restart_daemons()
==> minion-1:  *  INFO: Running daemons_running()
==> minion-1:  *  INFO: Salt installed!


change LinkedIn colour in SVG from black to white

What kind of change does this PR introduce?
minor, colour

Does this PR introduce a breaking change?

What needs to be documented once your changes are merged?

👷 Deploy Preview for peaceful-meerkat-940447 processing.

Name
Link

🔨 Latest commit
fe1cf1eb213e11374dd9ca9961e94bd0dde4c14d

🔍 Latest deploy log
https://app.netlify.com/sites/peaceful-meerkat-940447/deploys/64072b330ba4dd0008b60adc


chore(apps/prod/tekton/configs/triggers): support first patch version rc build

Signed-off-by: wuhuizuo<EMAIL_ADDRESS>

/approve


iced freeze for multiple seconds, if many image are added at the same time

Is there an existing issue for this?

[X] I have searched the existing issues.

Is this issue related to iced?

[X] My hardware is compatible and my graphics drivers are up-to-date.

What happened?
If I show many (200) Images (100kb each) and add them all at the same view() call iced freeze for multiple seconds. At debug mode it even crash sometimes. If do not show add them all at the same view() step (for example the must be downloaded from the internet first) everything works fine.
It looks like iced reads the images from the ssd and blocks the hole app so long.
What is the expected behavior?
not freeze
Version
crates.io release and master
Operating System
Linux
Do you have any log output?
log.txt

Original example:
https://github.com/LuckyTurtleDev/mtg/tree/d83dd32a35cb7030e992d06e233b90f15f223c03
Steps to reproduce:

Search for "dragon". Everything works fine now since the image must be loaded from the internet first.
Wait a few seconds until everything is fetch.
Select "Stock"
Go back to "Search"
The app freeze now for a few seconds since every image is present at the drive and will be load at the same time now .

So I have impl a second cache to cache the image Handle now, to avoid the lagging. It became a loot faster but still freeze for 1-2 seconds at release mode.
https://github.com/LuckyTurtleDev/mtg/tree/e33ef17ea9cfcc30f497cb67ec1d560897c17535
The only option I currently see, to fix this, is to impl a 3 cache, which tracks which image handle was show at the last view step and limit the count of new handles, which will be used to view an image. But this sound even more hack, like the current version.
This sound like something, which should be impl in iced instead.


Pass URIs for some context snippets

Previously, we used the relative file name to indicate the source file of all context snippets. This causes problems, because:

The user may have more than one workspace folder open, in which case we don't know how to resolve a relative file name, because we lose track of which workspace folder it came from
Context from remote sources (e.g., remote embeddings) isn't attached to a local file, and we may need to treat these differently when trying to open the file

Add a URI field to keep better track of the true location of a context item. Adds creator functions for 2 URI schemes: cody-file-relative:// and cody-embeddings://.
Also add an openUri function that handles opening these URIs and is more forgiving for file:// URIs (will attempt to match a relative file URI with an open workspace folder).
Test plan

Open at least 2 workspace folders
Open a file from the 2nd workspace folder
Create a new chat and ask a question
Attempt to open the context files—these should open properly, whereas before, nothing occurred

See screen recordings for examples.

@abeatrix pushed a patch, PTAL
@arafatkatze can you share the output of your debugger console? I want to see why chat is hanging


Bugs in dark theme

Currently the dark theme has a few minor bugs:

When switching to dark theme, some elements appear to slightly move/change size
The Contribution Graph displays 0 contributions in white instead of gray like github

I wish to fix them, please tag this issue and assign it to me.

Sir I can do this task
But can u please tell me in which project you are facing problem

Sir I can do this task But can u please tell me in which project you are facing problem

Hi @codeansh20 , You can work on any issue from here


Modify ES Reader to use MultiSearch for bulk reading

Coverage remained the same at 100.0% when pulling b1a8d3bd41004e9f2d13e4670e9404e94d15019e on es-bulk-read into 4ef5aec6a38ff695e3c1a2b8c541aa5f91775787 on master.

Coverage remained the same at 100.0% when pulling b1a8d3bd41004e9f2d13e4670e9404e94d15019e on es-bulk-read into 4ef5aec6a38ff695e3c1a2b8c541aa5f91775787 on master.

Coverage remained the same at 100.0% when pulling 5a389d0576f9adcb7664269c133cf5786a6bccc3 on es-bulk-read into 4ef5aec6a38ff695e3c1a2b8c541aa5f91775787 on master.

Coverage remained the same at 100.0% when pulling fc6e25c92ac8d908abad9e0fe4d37fe597c841ef on es-bulk-read into 4ef5aec6a38ff695e3c1a2b8c541aa5f91775787 on master.

Coverage remained the same at 100.0% when pulling 37398b8a07ff8689fd79a541d21fa3ff86b5b5dd on es-bulk-read into 4ef5aec6a38ff695e3c1a2b8c541aa5f91775787 on master.


Add Tradeoff Analytics

Add support for Tradeoff Analytics to the SDK using the new RestKit architecture.

Complete with #326.


Tab frames are inheriting scrollbars from larger tabs, even if not needed.

this is quite possibly fixed -- there were a few issues there that are now fixed with the flow layout -- could have fixed this too -- it looked a lot better to me for gide tabs.

actually, there are two different cases: if a tab has a strong minimum size, then all tabs will get that same minimum size, because it uses a "stacked layout" and that is what it does.  changing that would break a lot of other things. and it makes sure tabs all fit in the same space -- this is a kind of side-effect of that.
but previously we might have had further issues with aberrant scrollbars that might be fixed now (also with scrollbars missing).

I just changed the Layout code for Stacked case to only use the top widget -- actually it works well and doesn't seem to break anything so far!  give it a try..


Typo in header

Change "Wilkommen" to "Willkommen" in the  header.

Coverage remained the same at 93.369% when pulling 591ed461689d66b44ba04c6720444a612f4c9787 on s4magier:patch-1 into 1162a9543010ddcb78ee4197c045d7633f409736 on rdmorganiser:master.

Coverage remained the same at 93.369% when pulling 591ed461689d66b44ba04c6720444a612f4c9787 on s4magier:patch-1 into 1162a9543010ddcb78ee4197c045d7633f409736 on rdmorganiser:master.

Thanks! Somehow noone noticed before, usually people use the template in rdmo-app.


fix(headless): input bug when clearing storefront cart

Context in JIRA. ENG-106
Here's the error from the API.

Tests also seem to be broken on main will take a look later


Re: 'Get started developing on GOV.UK'

Problem with 'Get started developing on GOV.UK' (https://docs.publishing.service.gov.uk/manual/get-started.html)
Under "7. Install and configure the GDS CLI" then "4. Set up AWS credentials", the process reports an error at the end for something related to YubiKeys. There's no mention of this in this section of the documentation. Editing ~/.gds/config.yml and changing yubikey: true to yubikey: false fixes this issue, as documented here. This page should probably be updated to clarify this step

Thanks! Looks like this was independently fixed in the meantime in #4469

We should be giving everyone Yubikeys and have modern, unphishable authn ofc, but that's another story 🙃


app.run() fails with TypeError: function expected at most 3 arguments, got 4

i try to get picoweb running on the esp32. installed it with upip.install("picoweb") and upip.install("micropython-ulogging")`. i used the example code and cant get it running. no matter what i do, i run into this error:
>>> upip.install("picoweb")
Installing to: /lib/
Warning: micropython.org SSL certificate is not validated
Installing picoweb 1.7.1 from https://files.pythonhosted.org/packages/1b/4f/f7d35f90521e95d9d2307f69ff523133d7d4dd6da7ce1ce0c8382e7255fa/picoweb-1.7.1.tar.gz
Installing pycopy-uasyncio 3.1.1 from https://files.pythonhosted.org/packages/5f/24/fb08acdd7ebf1626dcdb3cdaf0d3f463c254a4a3aa2cab70b0ee6562a83d/pycopy-uasyncio-3.1.1.tar.gz
Installing pycopy-pkg_resources 0.2.1 from https://files.pythonhosted.org/packages/05/4a/5481a3225d43195361695645d78f4439527278088c0822fadaaf2e93378c/pycopy-pkg_resources-0.2.1.tar.gz
Installing pycopy-uasyncio.core 2.3 from https://files.pythonhosted.org/packages/6a/96/80a86b1ea4e2b8c7e130068a56f9e8b5bbb28369e48de56a753778e14faf/pycopy-uasyncio.core-2.3.tar.gz
>>> upip.install("micropython-ulogging")
Installing to: /lib/
Installing micropython-ulogging 0.3 from https://files.pythonhosted.org/packages/49/4f/fd39c77fb90dfd188e3e7716556bb3e211edf132d855d7860a8d835b9fbc/micropython-ulogging-0.3.tar.gz
>>> import picoweb
>>> app = picoweb.WebApp("foo")
>>> app
<WebApp object at 3ffd0080>
>>> app.run()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/lib/picoweb/__init__.py", line 299, in run
  File "/lib/uasyncio/core.py", line 163, in run_forever
  File "/lib/uasyncio/core.py", line 129, in run_forever
  File "/lib/uasyncio/__init__.py", line 31, in add_reader
TypeError: function expected at most 3 arguments, got 4

i know... no routes defined but i get the same error all over the place... even with routes and stuff. so i thought this might be the most simplest code to get something running. any ideas?

i browsed through the last commits of picoweb and read about the change from micropython-uasyncio to pycopy-uasyncio in the setup.py file. i deleted uasyncio from lib on the board and did a upip.install("uasyncio"), ran app.run() and it worked.

Great. README also should contain the up to date instructions/information, so just reading it should be enough.

Great. README also should contain the up to date instructions/information, so just reading it should be enough.

sorry for my question. do you mean the part that it should be used with pycopy and not micropython mainline?

And about pycopy-ulogging or pycopy-logging packages, etc.

And about pycopy-ulogging or pycopy-logging packages, etc.

so if i should have flashed my esp32 with pycopy, a upip.install("picoweb") should have worked? i mean after installing logging etc...
im really new to the python on microcontroller world and just read about your fork.

Picoweb is a part of Pycopy project and works only with its infrastructure. I personally don't have esp32, so can't give 100% assurance that everything works seamlessly there (but I don't see why it wouldn't either).

Picoweb is a part of Pycopy project and works only with its infrastructure. I personally don't have esp32, so can't give 100% assurance that everything works seamlessly there (but I don't see why it wouldn't either)

ok... im sold :) will try it. thank you for your amazing work!


Invalid coords in summary is superfluous

I'm pretty sure that cube.summary() will never produce an Invalid coordinate. Specifically, when this line is called:
https://github.com/SciTools/iris/blob/1d7d0b564e82acbbcd25ccd5963b246b186434c8/lib/iris/cube.py#L2045
I believe that invalid_coords will always be empty. It is essentially defined as a coordinate which is neither a scalar coordinate nor a vector coordinate, however vector coordinates are already defined so that they contain all coordinates which are not scalar coordinates. This means that all coordinates are necessarily either scalar or vector coordinates at this point.

@stephenworsley Great spot :eyeglasses: .
I agree. The concept of invalid_coords is, dare I say, invalid... and what's more I've never, ever seen any.
I think this is ancient code from when we were first developing iris and it wasn't well defined the coordinates that we were dealing with. After checking, I believe it's safe to purge this technical debt.
Thanks!

There seem to be a few redundant bits in there.  E.g.

If self.coord_dims(coord) is empty, how could the coord shape be anything other than (1,)?
https://github.com/SciTools/iris/blob/1d7d0b564e82acbbcd25ccd5963b246b186434c8/lib/iris/cube.py#L2020-L2021

How would anything in self.dim_coords be scalar?
https://github.com/SciTools/iris/blob/1d7d0b564e82acbbcd25ccd5963b246b186434c8/lib/iris/cube.py#L2025-L2026


FYI: https://www.heartex.ai/ seems to be offline

URL is listed in READMEs etc: https://github.com/heartexlabs/label-studio-ml-backend/search?q=https%3A%2F%2Fwww.heartex.ai
❯ wget -S https://www.heartex.ai/
--2022-12-16 13:44:14--  https://www.heartex.ai/
Resolving www.heartex.ai (www.heartex.ai)... <IP_ADDRESS>
Connecting to www.heartex.ai (www.heartex.ai)|<IP_ADDRESS>|:443... failed: Connection timed out.
Retrying.

--2022-12-16 13:44:30--  (try: 2)  https://www.heartex.ai/
Connecting to www.heartex.ai (www.heartex.ai)|<IP_ADDRESS>|:443... failed: Connection timed out.
Retrying.

--2022-12-16 13:44:48--  (try: 3)  https://www.heartex.ai/
Connecting to www.heartex.ai (www.heartex.ai)|<IP_ADDRESS>|:443...
...

There should be a redirect to heartex.com.
Now we are on heartex.com.

"should be" is not the same as "there is", so the issue seems to persist:
❯ wget -S https://www.heartex.ai/
--2022-12-22 12:04:56--  https://www.heartex.ai/
Resolving www.heartex.ai (www.heartex.ai)... <IP_ADDRESS>
Connecting to www.heartex.ai (www.heartex.ai)|<IP_ADDRESS>|:443... failed: Connection timed out.
Retrying.

--2022-12-22 12:05:12--  (try: 2)  https://www.heartex.ai/
Connecting to www.heartex.ai (www.heartex.ai)|<IP_ADDRESS>|:443...
...

and you might like to address it properly.

@farioas could you please check? ^
All my devices work well with heartex.ai.

Thanks for the report. We changed all the links from https://www.heartex.ai/ to https://www.heartex.com/.


Lib is not compatible with webpack

amd-define must be removed from the lib

I'm afraid that author of this is dead, according to his site: https://jex.im/


Create voluba content types

json for transformation (consistency update in jsonld filename)
json for landmarks adding as new content type

@jagru20 do you have time to have a look at this PR? let me know if I should assign someone else. Best, Lyuba


Added a new quote

I added this quote:

"Develop a positive mindset and cultivate optimism.

Awesome quote @noyonalways . I am merging your pull request. Keep it up!
And I've invited you to the organization.

Thank you for inviting me.


Add support for generating/deriving interpreter/cursor for datatype backed models

Some progress in https://github.com/gemini-hlsw/gsp-graphql/pull/47.

#47 and subsequent work on effects and mixing of model types covers this I think.


Validate/Tshoot k8s hostNetwork

Ran into an issue where hostNetwork: true was not getting wg traffic off the host. The issue was in an EC2 OCP deployment so we should look at that as well as vanilla k8s.
The following was failing. If you remove hostNetwork: true everything works in the symmetric NAT environment:
apiVersion: v1
kind: Pod
metadata:
  name: nexd
  namespace: <NAMESPACE>
spec:
  hostNetwork: true
  hostAliases:
    - ip: <API_SERVER>
      hostnames:
        - try.nexodus.<IP_ADDRESS>.nip.io
        - api.try.nexodus.<IP_ADDRESS>.nip.io
        - auth.try.nexodus.<IP_ADDRESS>.nip.io
  containers:
  - name: nexd-container
    image: quay.io/nexodus/nexd:latest
    command:
      - nexd
    args:
      - --username
      - <USERNAME>
      - --password
      - <PASSWORD>
      - --insecure-skip-tls-verify
      - https://try.nexodus.<IP_ADDRESS>.nip.io
    securityContext:
      privileged: true

Tested so far:

(Works) Docker docker run --rm -it --network host --cap-add SYS_MODULE --cap-add NET_ADMIN --cap-add NET_RAW  quay.io/nexodus/nexd
(Works) KIND with the above yaml

The isue here is the FirewallMark for exit node that is conflicting with some k8s implementation with hostNetworking: true. Removing the mark resolves the issue. Need a patch to resolve this without breaking exit-node client PBR on linux. https://github.com/nexodus-io/nexodus/blob/30b7ec5af977cd8a909cba053a7ee59f75b86546/internal/nexodus/nexodus_linux.go#L97:
//fwMark := wgFwMark

err = c.ConfigureDevice(nx.tunnelIface, wgtypes.Config{
	PrivateKey:   &privateKey,
	ListenPort:   &listenPort,
	ReplacePeers: true,
	Peers:        nil,
	//FirewallMark: &fwMark,
})

The isue here is the FirewallMark for exit node

@nerdalert exit node wasn't being used here, right? so why is the mark used?

@russellb since exit node can be toggled on and off its pre-provisioned there. I can't really come up with a work around other than tearing the interface down if exit node client is toggled. Any ideas?


phraseupp will delete a key if string is empty

Example:
// bar is not needed for this language
{
foo: 'my phrase',
bar: ''
}
after phraseapp push and pull again json for this language will look like
{
foo: 'my phrase'
}
Expected result is that the key is not deleted from the json file.

Hi @Wendenburg, empty translations are not exported by default but there is a option include_empty_translations: true to keep them.
phrase:
  file_format: simple_json
  pull:
    targets:
      -
        file: ./app/<locale_name>.json
        project_id: <PROJECT_ID>
        params:
          include_empty_translations: true

Let me know this already helps.

Did this resolve the issue? I'll close this for now but please leave a comment if there is still any problem.


🛠  update lodash,knex and bookshelf to latest versions

refs #7189

we had a memory leak after upgrading to knex 0.11.x (see #7189)
knex has published a new version 0.12.x
the memory leak does not longer exists
knex has reverted their pool logic, see tgriesser/knex#1665

I did the same testing as i did when i reproduced the memory leak.
3 requests per second to a Ghost server which has lot of data in the database.
The memory with latest lodash, latest bookshelf and latest knex grows to a max memory of ~300mb and always falls down to 130-140mb.

3 requests per second to a Ghost server which has lot of data in the database.
The memory with latest lodash, latest bookshelf and latest knex grows to a max memory of ~300mb and always falls down to 130-140mb.

Is that the same or different to the previous test? Can you maybe share a graph of both?
If I am correct, this same test did not reproduce the memory leak last time, and so this is not a good test to base an conclusion on?
I now have access to a trace account, so maybe we can setup a longer running test tomorrow ?

Is that the same or different to the previous test? Can you maybe share a graph of both?

Same. I don't have a graph.

If I am remembering correctly, this same test did not reproduce the memory leak last time, and so this is not a good test to base an conclusion on?

I was able to reproduce the memory leak with this exact test suite.

I now have access to a trace account, so maybe we can setup a longer running test tomorrow ?

If you want sure.
My ghost server is running now an hour and memory is good.

When I asked you if it was the same, I meant the results, not the test itself. I'm asking how these results compare to the results you saw last time? I want to see side-by-side results so that I can understand the difference, if there is one.

I can make graphs tomorrow 👍 with knex 0.10 (which we are using know), knex 0.11 (which had a memory leak) and knex 0.12. (which solved the memory leak)

Either a graph or a table would be fab.

It turned out that knex 0.12 is not solving the memory problems.
I did another measuring this morning. Here are the results (tested with lodash 3 and 4, it doesn't matter)

Bookshelf 0.9.x
Knex 0.10.x
Bookshelf 0.9.x
Knex 0.12.x

(both setups result in the same graph)

Bookshelf 0.10.x
Knex 0.12.x
Bookshelf 0.10.x
Knex 0.10.x

(both setups result in the same graph)
Looks like the bookshelf version 0.10.x is causing the problems.

I'll need to take a look to see what's happening here

@kirrg001 is there a step-by-step I can follow to reproduce those graphs and get those results?

Just in looking through the commit log I believe the issue likely has to do with the __super__ reference in .extends in this commit.
If it is indeed the source of issue I can go ahead and revert the portions that change asap, will try and take a look a little later.

@tgriesser Thanks for getting involved.
To reproduce the problem, you need to checkout this branch and setup a ghost blog with a bigger database (i had 20 posts in my database). Then you can trigger some curl commands from shell and watch the memory. Write me a PM in slack, if you need help.
see also #7189

This is fixed in Bookshelf 0.10.2 🎉 - Thanks @kirrg001 for the help in profiling / tracking this one down!

I can confirm: the memory leak is fixed in 0.10.2.
Thank you @tgriesser!

ready for review && merge

@kirrg001 this needs rebasing please :)

@ErisDS 👍 👍 didn't see, will do now

@ErisDS did

I would like this same PR made to the lts branch if possible? I can do it, but I figured you might want to 😉

@ErisDS sure will create


init httproute controller

What
Describe what the change is solving
How
Describe the solution
Breaking Changes
Are there any breaking changes in this PR?

[!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

Current dependencies on/for this PR:

#345  👈
#343
main

This stack of pull requests is managed by Graphite.


fix(artifacts): fix json encoder to allow tensor datatypes for artifact metadata

https://github.com/wandb/wandb/issues/4500
https://wandb.atlassian.net/browse/WB-11691
Description
Fix issue where tensor datatypes weren't json serializable so that it can be set as the metadata. This is a hacky fix to the eventual fix of refactoring the json serialization across this repo
Testing
Added small change to unit test as well as testing manually

@estellazx mind adding more exhaustive testing for this.
Where you able to reproduce the issue? did you verify your change fixed it?


timetableday should only represent hours in timetable not freetime

-> don't save freetime in database and deal with the problems

Commit 137c7778d067840f24c8df995c3d0c17a276e600 should fix this


Incorrect Snap package localisation

In Ubuntu Bionic, the VLC Snap package installs only localised to english, despite the system I'm working on is set to spanish language. It seems there's no way to correct the issue after installation.

Did you get the wrong repo (this issue tracker is for GIMP) or did you mistype GIMP as VLC? The described behaviour is also present GIMP, and has also been reported by others.

Sorry, it was a typo (vlc snap shows the same issue and I was reporting it). The issue is for the gimp snap package as described above (I've just edited the original report).

Thanks for the confirmation, I didn't want you to be confused when we started talking about GIMP if you really meant to file it to VLC :-) This issue is a long-standing one, and I don't understand it yet. I think it might be a deficiency of snapd, but can't be sure I haven't screwed up the GIMP packaging. In a related problem it seems that localisations are also ignored for folders in your home directory, which leads me to think localisations in general are broken across the board.

Thank you for adressing this one! If it helps, Mozilla Firefox, Musescore and gnome-system-monitor snap packages are working fine under my localisation (maybe it's a packaging related issue).

I think I've fixed it. Can you try:
$ sudo snap refresh --candidate gimp

Then run GIMP and see if the localisation/translation is working?

Yes! It's working really fine! Congratulations!
Please, let me know when I could reinstall the stable package when it's fixed.
Thank you!

Closing as fixed then :-)


Empty universe

Describe the bug
Completely empty universe tab as well as other tabs
To Reproduce
Steps to reproduce the behavior:

helm upgrade --atomic -i -n kubevious \

--version 0.7.13 \
--set ingress.enabled=true \
--set ingress.class=nginx \
--set ingress.domain=<my-domain> \
--set provider=eks \
kubevious kubevious/kubevious

Open the UI

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots

Environment Details:

Kubernetes Distribution/Version: v1.16.8-eks
Browser: chrome
Version 85.0.4183.83 (Official Build) (64-bit)

Additional context

I don't see any error in the Kubevious pods
Noticed the websocket has an error "Error during WebSocket handshake: Unexpected response code: 400" But then this error appears on the Kubevious demo page as well and doesn't seem to have any impact
The Parser pod logs show that it is detecting changes in the cluster and acting on them.
But the polling request responses seem small and empty

hi @arleif-dfactory,
How big is your deployment? node/pod count?
This typically happens during the initial startup while the data is being loaded into the backend.
Can you try to open this url and see if there is any data returned: http:///api/v1/diagram/children?dn=root?
Unless there is something else going on wrong, the UI should come up after some time. That depends on cluster size and the resources allocated to kubevious & parser pods.
I'll mark it as an enhancement to work on overall performance improvement and possibly add a loading progress.

hi @arleif-dfactory,
How big is your deployment? node/pod count?
This typically happens during the initial startup while the data is being loaded into the backend.
Can you try to open this url and see if there is any data returned: http:///api/v1/diagram/children?dn=root?
Unless there is something else going on wrong, the UI should come up after some time. That depends on cluster size and the resources allocated to kubevious & parser pods.
I'll mark it as an enhancement to work on overall performance improvement and possibly add a loading progress.

Ruben,
Thanks for the reply.
The deployment is not very large. 15 nodes, 100 pods
I tried giving those two deployments x10 more memory and CPU than the default and waiting a long time, didn't help.
/api/v1/diagram/children?dn=root  returns [ ]
Here are some logs if they give you some info
[2020-08-31 03:05:20.811 +0000] INFO  (LogicProcessor/1 on kubevious-parser-69bdbd6f9b-5t7cj): [process BEGIN
[2020-08-31 03:05:26.455 +0000] INFO  (LogicProcessor/1 on kubevious-parser-69bdbd6f9b-5t7cj): [process READY
[2020-08-31 03:05:26.465 +0000] INFO  (FacadeRegistry/1 on kubevious-parser-69bdbd6f9b-5t7cj): [acceptLogicItems item count: 35498
[2020-08-31 03:05:26.465 +0000] INFO  (FacadeDampener/1 on kubevious-parser-69bdbd6f9b-5t7cj): [acceptJob job date: 2020-08-31T03:05:26.465Z. queue size: 1
[2020-08-31 03:05:26.465 +0000] INFO  (FacadeDampener/1 on kubevious-parser-69bdbd6f9b-5t7cj): [_processJob BEGIN. Date: 2020-08-31T03:05:26.465Z
[2020-08-31 03:05:26.465 +0000] INFO  (LogicProcessor/1 on kubevious-parser-69bdbd6f9b-5t7cj): [process END

The queue size goes up to 10 sometime but drops to 1 quickly.
The snapshot job fails sometimes (timeout) but then it also succeeds occasionally.

The deployment is not very large. 15 nodes, 100 pods
That should be ok. Tested with 1000 pods and worked fine.

@arleif-dfactory, could you provide complete logs for kubevious pod?

The snapshot job fails sometimes (timeout) but then it also succeeds occasionally.
Could you provide more details on that? Its bit hard to help without much info.

Also, please check if "kubevious" pod is crashing/restarting.

Logs of the Kubevious pod. It did not have any restarts, but I had killed it myself to add more resources.

The snapshot job fails sometimes (timeout) but then it also succeeds occasionally.
Could you provide more details on that? Its bit hard to help without much info.

Occasionally there are errors like this in the parser pod but very rare. Other times the snapshot is successful. [2020-09-02 15:36:37.947 +0000] ERROR (ReporterTarget/1 on kubevious-parser-69bdbd6f9b-5t7cj): [request] URL: /snapshot/items, ERROR: timeout of 10000ms exceeded

Logs of the Kubevious pod. It did not have any restarts, but I had killed it myself to add more resources.

The snapshot job fails sometimes (timeout) but then it also succeeds occasionally.
Could you provide more details on that? Its bit hard to help without much info.

Occasionally there are errors like this in the parser pod but very rare. Other times the snapshot is successful. [2020-09-02 15:36:37.947 +0000] ERROR (ReporterTarget/1 on kubevious-parser-69bdbd6f9b-5t7cj): [request] URL: /snapshot/items, ERROR: timeout of 10000ms exceeded

The logs attached include first 90 seconds after start. Could you run it for 10-15 minutes and attach logs for Kubevious as well as Parser pods?

kubevious logs
parser--logs
There wasn't must interesting info in there so I restarted parser.
parser logs after restart

This error explains why the universe is empty:
(ReporterTarget/1 on kubevious-parser-69bdbd6f9b-5t7cj): [request] URL: /snapshot/items, ERROR: timeout of 10000ms exceeded

To debug this further, can you try to ssh into parser pod and send a http POST request to http://kubevious-svc.kubevious.svc.cluster.local:4001/api/v1/collect/snapshot/items
Without payload should receive error (missing snapshot_id), but want to test if parser can communicate with the kubevious backend.

one more thing. how big is your deployment? how many pods, configmaps, nodes, etc?

/app # curl --location --request POST 'http://kubevious-svc.kubevious.svc.cluster.local:4001/api/v1/collect/snapshot/i tems' {"message":"Missing snapshot_id"}/app #
Size: 15 nodes, 200 pods, 200 configmaps

@arleif-dfactory, we need to instrument it more to debug further. Will let you know when changes are ready to try out.
In the logs I see 35059objects captured. Does it sound reasonable? Objects collected by kubevious:

Node
Namespace
LimitRange
Service
ConfigMap
Pod
ServiceAccount
PersistentVolumeClaim
PersistentVolume
ReplicaSet
Deployment
DaemonSet
StatefulSet
HorizontalPodAutoscaler
Job
Ingress
Role
RoleBinding
ClusterRole
ClusterRoleBinding
PodSecurityPolicy

Also, meanwhile could you try to run the Portable version: https://github.com/kubevious/portable
It runs on the same machine where the kubectl is configured. It would help to direct to the cause of the problem.

Ruben,
35k sounds about right since we use Knative and have a lot more services than there are active at any point in time. I'm sorry I didn't make it clear that the number (200 pods) that I quoted earlier was the number of running pods. We have a lot more deployments, most of them scaled down to 0.
Portable - works!. See see results on the UI although it is very slow and sluggish.

@arleif-dfactory, we are definitely hitting scale limits because of increased serverless related content.
We can try to work on that. Would probably need some more of your input to try out few versions to provide feedback.
It would be best if you could join the slack channel of quick communication: https://kubevious.io/slack

Thanks Ruben. I will join, but in case I don't respond there and you need me to run tests, post them here, I get email alerts.

@arleif-dfactory, lets try to run this version and see how it would behave.
helm upgrade --atomic -i -n kubevious \
    --version 0.7.15 \
    --set ingress.enabled=true \
    kubevious kubevious/kubevious

Once you get it running for some time, please upload the logs for parser & kubevious.

Hello, I seem to have the same issue
docker images :

kubevious/kubevious 0.8.1
kubevious/parser 0.8.2

parser
I got this error a few times
[2020-11-20 13:56:15.128 +0000] INFO  (ReporterTarget/1 on kubevious-parser-5b8494985-rwn58): [report] date: 2020-11-20T13:56:04.992Z, item count: 69934
[2020-11-20 13:56:15.151 +0000] ERROR (ReporterTarget/1 on kubevious-parser-5b8494985-rwn58): [request] URL: /snapshot/items, ERROR: timeout of 10000ms exceeded

Also, it seems that the queue never empties , is that normal ?
kubectl logs -f kubevious-parser-5b8494985-rwn58 | grep Reporter
[2020-11-20 14:07:55.955 +0000] INFO  (Reporter/1 on kubevious-parser-5b8494985-rwn58): [_determineCollectors] Collectors:
[2020-11-20 14:08:08.127 +0000] INFO  (Reporter/1 on kubevious-parser-5b8494985-rwn58): [acceptLogicItems] item count: 16243
[2020-11-20 14:08:19.653 +0000] INFO  (Reporter/1 on kubevious-parser-5b8494985-rwn58): [acceptLogicItems] obj count: 69005
[2020-11-20 14:08:19.666 +0000] INFO  (ReporterTarget/1 on kubevious-parser-5b8494985-rwn58): [report] date: 2020-11-20T14:08:08.111Z, item count: 69005
[2020-11-20 14:08:19.666 +0000] INFO  (ReporterDampener/1 on kubevious-parser-5b8494985-rwn58): [acceptJob] job date: 2020-11-20T14:08:08.111Z. queue size: 1
[2020-11-20 14:08:19.666 +0000] INFO  (ReporterDampener/1 on kubevious-parser-5b8494985-rwn58): [_processJob] BEGIN. Date: 2020-11-20T14:08:08.111Z
[2020-11-20 14:08:19.679 +0000] INFO  (ReporterTarget/1 on kubevious-parser-5b8494985-rwn58): [_processSnapshot] date: 2020-11-20T14:08:08.111Z, item count: 69005
[2020-11-20 14:08:19.679 +0000] INFO  (ReporterTarget/1 on kubevious-parser-5b8494985-rwn58): [_reportSnapshot] Begin
[2020-11-20 14:08:19.680 +0000] INFO  (SnapshotReporter/1 on kubevious-parser-5b8494985-rwn58): [run]
[2020-11-20 14:08:19.680 +0000] INFO  (SnapshotReporter/1 on kubevious-parser-5b8494985-rwn58): [_execute]
[2020-11-20 14:08:19.680 +0000] INFO  (SnapshotReporter/1 on kubevious-parser-5b8494985-rwn58): [_reportAsSnapshot]
[2020-11-20 14:08:19.680 +0000] INFO  (SnapshotReporter/1 on kubevious-parser-5b8494985-rwn58): [_createSnapshot]
[2020-11-20 14:08:20.927 +0000] INFO  (Reporter/1 on kubevious-parser-5b8494985-rwn58): [acceptLogicItems] item count: 16239
[2020-11-20 14:08:25.292 +0000] INFO  (Reporter/1 on kubevious-parser-5b8494985-rwn58): [acceptLogicItems] obj count: 68993
[2020-11-20 14:08:25.305 +0000] INFO  (ReporterTarget/1 on kubevious-parser-5b8494985-rwn58): [report] date: 2020-11-20T14:08:20.903Z, item count: 68993
[2020-11-20 14:08:25.305 +0000] INFO  (ReporterDampener/1 on kubevious-parser-5b8494985-rwn58): [acceptJob] job date: 2020-11-20T14:08:20.903Z. queue size: 2
[2020-11-20 14:08:25.316 +0000] INFO  (SnapshotReporter/1 on kubevious-parser-5b8494985-rwn58): [_createSnapshot] id: 89b7cef4-27a3-4d99-ae61-fd40e1ae3148
[2020-11-20 14:08:25.316 +0000] INFO  (SnapshotReporter/1 on kubevious-parser-5b8494985-rwn58): [_publishSnapshotItems]
[2020-11-20 14:08:27.031 +0000] INFO  (Reporter/1 on kubevious-parser-5b8494985-rwn58): [acceptLogicItems] item count: 16235
[2020-11-20 14:08:31.241 +0000] INFO  (Reporter/1 on kubevious-parser-5b8494985-rwn58): [acceptLogicItems] obj count: 68973
[2020-11-20 14:08:31.264 +0000] INFO  (ReporterTarget/1 on kubevious-parser-5b8494985-rwn58): [report] date: 2020-11-20T14:08:27.007Z, item count: 68973
[2020-11-20 14:08:31.264 +0000] INFO  (ReporterDampener/1 on kubevious-parser-5b8494985-rwn58): [acceptJob] job date: 2020-11-20T14:08:27.007Z. queue size: 3
[2020-11-20 14:08:33.590 +0000] INFO  (Reporter/1 on kubevious-parser-5b8494985-rwn58): [acceptLogicItems] item count: 16235
[2020-11-20 14:08:40.690 +0000] INFO  (Reporter/1 on kubevious-parser-5b8494985-rwn58): [acceptLogicItems] obj count: 68973
[2020-11-20 14:08:40.722 +0000] INFO  (ReporterTarget/1 on kubevious-parser-5b8494985-rwn58): [report] date: 2020-11-20T14:08:33.584Z, item count: 68973
[2020-11-20 14:08:40.722 +0000] INFO  (ReporterDampener/1 on kubevious-parser-5b8494985-rwn58): [acceptJob] job date: 2020-11-20T14:08:33.584Z. queue size: 4
[2020-11-20 14:08:42.941 +0000] INFO  (Reporter/1 on kubevious-parser-5b8494985-rwn58): [acceptLogicItems] item count: 16229
[2020-11-20 14:08:52.000 +0000] INFO  (Reporter/1 on kubevious-parser-5b8494985-rwn58): [acceptLogicItems] obj count: 68952
[2020-11-20 14:08:52.031 +0000] INFO  (ReporterTarget/1 on kubevious-parser-5b8494985-rwn58): [report] date: 2020-11-20T14:08:42.917Z, item count: 68952
[2020-11-20 14:08:52.031 +0000] INFO  (ReporterDampener/1 on kubevious-parser-5b8494985-rwn58): [acceptJob] job date: 2020-11-20T14:08:42.917Z. queue size: 5
[2020-11-20 14:08:54.196 +0000] INFO  (Reporter/1 on kubevious-parser-5b8494985-rwn58): [acceptLogicItems] item count: 16229
[2020-11-20 14:09:03.465 +0000] INFO  (Reporter/1 on kubevious-parser-5b8494985-rwn58): [acceptLogicItems] obj count: 68952
[2020-11-20 14:09:03.497 +0000] INFO  (ReporterTarget/1 on kubevious-parser-5b8494985-rwn58): [report] date: 2020-11-20T14:08:54.184Z, item count: 68952
[2020-11-20 14:09:03.497 +0000] INFO  (ReporterDampener/1 on kubevious-parser-5b8494985-rwn58): [acceptJob] job date: 2020-11-20T14:08:54.184Z. queue size: 6

For company policy reasons, I'm not sure I can give you a full dump, however If you tell me what you're looking for or if you create a docker image with some custom profiling, I can run it on our cluster and help it work with bigger workloads.

@onigoetz, I think 69k objects is a little bit too much for the poor thing to handle :)
Could you also provide some logs from the the "kubevious" pod? Also, please check the CPU/memory settings for "kubevious" and "mysql" pods.  Its probably not able to keep up with the incoming traffic.
If you want and policy allows, I can try to help by taking a peek to your cluster. Join the slack channel to discuss.

@arleif-dfactory , @onigoetz , thanks for reporting this issue. We have just released a new version which also includes significant performance improvements. We also split the Backend into Backend and Collector. Backend serves user requests (so the UI is super responsive) and the Collector does the heavy lifting. The setup looks like this:

For your large setups try increasing following variables in the chart:

collector.resources.requests.*
collector.resources. limits.*
parser.resources.requests.*
parser.resources. limits.*

Please try installing again using the latest chart and let us know how it works. Reopen this issue if it still persists.
kubectl create namespace kubevious

helm repo add kubevious https://helm.kubevious.io

helm repo update

helm upgrade --atomic -i kubevious kubevious/kubevious --version 0.9.27 -n kubevious

For more details on installation options, visit Deployment Repository.


Profile URL does not work for non-app-scoped user IDs

FacebookAdapter sets the profile URL to https://www.facebook.com/app_scoped_user_id/{userId}. This URL does however not work for non-app-scoped IDs, i.e. users that first authenticated with API versions earlier than 2.0.
The fix is to user profile.getLink() in ProfileAdapter.

Merged PR #150. Will be in next snapshot build.


⚠ Bofrost.de has degraded performance

In 8859b5f, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 769 ms

Resolved: Bofrost.de performance has improved in e2168df after 309 days, 10 hours, 30 minutes.


Evan Aparri Period 4 | Week 4: Fastpages and Flask local server set up- HACKS and Tangibles

Links

Here is the link to my YouTube video on local server set up

Flask server changes
Here are changes I made to the stub.html file

Collaboration
Here is the link to the commits made by our group members on the fastpages site. Here is the link to our github insights.

Had all the requirements plus group collaboration
2.7+

2.7 I like the side by side, nice collaboration with your group

Good explanations with side by side screens that made it very clear to see what you were doing. 2.7

Met requirements
Showed group collaboration
2.7+

A little long on intro parts.   Side by side is good idea, but I would have done code with screen. 2.7


default/index.php is still looking for vvv.dev

Hi, here is a remaining call to vvv.dev which cause an error.

You're right, I completely forgot about that file. I'll have it fixed in the next round of updates.

Fixed in latest.


Actualize the contribution guidelines

CONTRIBUTING.md is badly outdated.

Do we still need these two here: https://github.com/OpenCyphal/yukon/tree/main/docs


Expose last-100 traefik log lines via WebUI

Do you want to request a feature or report a bug?
Feature
What did you expect to see?
A method for viewing the Traefik logs within the WebUI. To prevent memory issues, it would be reasonable to only show the last X (100? 1000?) lines. Depending on the preference of the maintainers, it would also be reasonable for this to be a default-off feature (similar to Tracing, Metrics, and AccessLog features).
The use case for WebUI-logs is initial setup and debug of Traefik. In a production system I would expect this feature to be either turned off or ignored, as there are numerous methods of accessing/forwarding logs that are better for a production setup.
However, when learning traefik, many common questions are readily answered by the logs. For example, why is my container not showing up at all? Checking the traefik log, we find level=error msg="service \"mon-unsee\" error: port is missing" providerName=docker container=mon-unsee-xi0ez2t13xtgmyttmvo2rgdar. Why am I not getting ACME certs? error: 400 :: POST :: https://acme-staging-v02.api.letsencrypt.org/acme/new-acct :: urn:ietf:params:acme:error:invalidEmail :: Error creating new account :: \"foobar#gmail.com\" is not a valid e-mail address  etc....
Each of the providers has a different way to check container logs, leading to a cycle of "edit config (or labels), redeploy, check dashboard, get confused, pull logs, find issue, repeat".
If traefik had this WebUI-logs feature, I think that would cut down on support requests and would also help newcomers to the traefik project.

This should be very useful! I think it should not only display last 100 lines, but support lazy-loading for those, so entire log will be available.


Add theme support

https://www.qt.io/blog/2007/11/27/theming-qt-for-fun-and-profit

https://doc.qt.io/qt-5/qtquickcontrols2-material.html

https://doc.qt.io/qt-5/qtquickcontrols2-customize.html
https://doc.qt.io/qt-5/qtquickcontrols2-configuration.html

https://doc.qt.io/qt-5/qtquickcontrols2-icons.html

All hardcoded theme'ing has been removed, qtquickcontrols2.conf is used to control the built-in styles. Longer term plan is to create an Imagine style.