Kong not starting in MAC

Summary
We were trying to install Kong (docker) on my Mac by following the instructions mentioned on the website (https://getkong.org/install/docker/ ).
When it ask to start Kong…..we are facing error
KONG START
/usr/local/bin/KONG:7: module 'kong.cmd.init' not found:No LuaRocks module found for kong.cmd.init
no field package.preload['kong.cmd.init']
no file 'kong/cmd/init/init.lua'
no file '/usr/local/openresty/site/lualib/kong/cmd/init.lua'
no file '/usr/local/openresty/site/lualib/kong/cmd/init/init.lua'
no file '/usr/local/openresty/lualib/kong/cmd/init.lua'
no file '/usr/local/openresty/lualib/kong/cmd/init/init.lua'
no file './kong/cmd/init.lua'
no file '/usr/local/openresty/luajit/share/luajit-2.1.0-beta2/kong/cmd/init.lua'
no file '/usr/local/share/lua/5.1/kong/cmd/init.lua'
no file '/usr/local/share/lua/5.1/kong/cmd/init/init.lua'
no file '/usr/local/openresty/luajit/share/lua/5.1/kong/cmd/init.lua'
no file '/usr/local/openresty/luajit/share/lua/5.1/kong/cmd/init/init.lua'
no file '/Users/asingh493/.luarocks/share/lua/5.1/kong/cmd/init.lua'
no file '/Users/asingh493/.luarocks/share/lua/5.1/kong/cmd/init/init.lua'
no file '/usr/local/openresty/site/lualib/kong/cmd/init.so'
no file '/usr/local/openresty/lualib/kong/cmd/init.so'
no file './kong/cmd/init.so'
no file '/usr/local/lib/lua/5.1/kong/cmd/init.so'
no file '/usr/local/openresty/luajit/lib/lua/5.1/kong/cmd/init.so'
no file '/usr/local/lib/lua/5.1/loadall.so'
no file '/Users/asingh493/.luarocks/lib/lua/5.1/kong/cmd/init.so'
no file '/usr/local/openresty/site/lualib/kong.so'
no file '/usr/local/openresty/lualib/kong.so'
no file './kong.so'
no file '/usr/local/lib/lua/5.1/kong.so'
no file '/usr/local/openresty/luajit/lib/lua/5.1/kong.so'
no file '/usr/local/lib/lua/5.1/loadall.so'
no file '/Users/asingh493/.luarocks/lib/lua/5.1/kong.so'
Steps To Reproduce
as per website https://getkong.org/install/docker/

docker run -d --name kong-database
-p 9042:9042
cassandra:3.10
docker run -d --name kong
--link kong-database:kong-database
-e "KONG_DATABASE=cassandra"
-e "KONG_CASSANDRA_CONTACT_POINTS=kong-database"
-e "KONG_PG_HOST=kong-database"
-p 8000:8000
-p 8443:8443
-p 8001:8001
-p 7946:7946
-p 7946:7946/udp
kong:latest
Kong Start

Additional Details & Logs

Kong version ($ kong version)
Kong debug-level startup logs ($ kong start --vv)
Kong error logs (<KONG_PREFIX>/logs/error.log)
Kong configuration (registered APIs/Plugins & configuration file)
Operating System - MAC Sierra

@asingh493 would you please try again, I tried locally on my mac and it just worked fine. Also please give it a try with  explicit version kong:0.10.3

It seems problem was because of Docker Machine. I installed Docker toolbox and as a result, there was a default docker machine and as a result, if I just issue command like
curl http://<IP_ADDRESS>:8001......give connection refused.
But if I give cmd like
curl http://<IP_ADDRESS>:8001....I see a response.

So I removed everything....and installed native Docker.
once I installed Kong again...I see the same problem.
asingh493$ kong stop
/usr/local/bin/kong:7: module 'kong.cmd.init' not found:No LuaRocks module found for kong.cmd.init
no field package.preload['kong.cmd.init']
no file 'kong/cmd/init/init.lua'
no file '/usr/local/openresty/site/lualib/kong/cmd/init.lua'
no file '/usr/local/openresty/site/lualib/kong/cmd/init/init.lua'
no file '/usr/local/openresty/lualib/kong/cmd/init.lua'
no file '/usr/local/openresty/lualib/kong/cmd/init/init.lua'
no file './kong/cmd/init.lua'
no file '/usr/local/openresty/luajit/share/luajit-2.1.0-beta2/kong/cmd/init.lua'
no file '/usr/local/share/lua/5.1/kong/cmd/init.lua'
no file '/usr/local/share/lua/5.1/kong/cmd/init/init.lua'
no file '/usr/local/openresty/luajit/share/lua/5.1/kong/cmd/init.lua'
no file '/usr/local/openresty/luajit/share/lua/5.1/kong/cmd/init/init.lua'
no file '/Users/asingh493/.luarocks/share/lua/5.1/kong/cmd/init.lua'
no file '/Users/asingh493/.luarocks/share/lua/5.1/kong/cmd/init/init.lua'
no file '/usr/local/openresty/site/lualib/kong/cmd/init.so'
no file '/usr/local/openresty/lualib/kong/cmd/init.so'
no file './kong/cmd/init.so'
no file '/usr/local/lib/lua/5.1/kong/cmd/init.so'
no file '/usr/local/openresty/luajit/lib/lua/5.1/kong/cmd/init.so'
no file '/usr/local/lib/lua/5.1/loadall.so'
no file '/Users/asingh493/.luarocks/lib/lua/5.1/kong/cmd/init.so'
no file '/usr/local/openresty/site/lualib/kong.so'
no file '/usr/local/openresty/lualib/kong.so'
no file './kong.so'
no file '/usr/local/lib/lua/5.1/kong.so'
no file '/usr/local/openresty/luajit/lib/lua/5.1/kong.so'
no file '/usr/local/lib/lua/5.1/loadall.so'
no file '/Users/asingh493/.luarocks/lib/lua/5.1/kong.so'

Are you running those commands on your host machine instead of inside the container? It looks like it, since the steps you described show:

docker run kong:latest (this should start Kong in the created container already)
kong start (if you did not ssh into your container, this will attempt to start Kong into the host machine, where Kong doesn't seem to be installed...)

The 0.10 family of images has been released for a while and running in production with no such issue.

I’m just following your docs.
In that case you need to update your doc.

Cheers
Abhishek Singh
PMP, CSM, SAFe, CSPO
DXC | EGL | Bengaluru | India
Ph: + 91 80 61762299 | CUG: 762299
From: Thibault Charbonnier<EMAIL_ADDRESS>Reply-To: Mashape/kong<EMAIL_ADDRESS>Date: Monday, 26 June 2017 at 6:52 PM
To: Mashape/kong<EMAIL_ADDRESS>Cc: "Singh, Abhishek 5"<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [Mashape/kong] Kong not starting in MAC (#2646)
Are you running those commands on your host machine instead of inside the container? It looks like it, since the steps you described show:

docker run kong:latest (this should start Kong in the created container already)
kong start (if you did not ssh into your container, this will attempt to start Kong into the host machine, where Kong doesn't seem to be installed...)

The 0.10 family of images has been released for a while and running in production with no such issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Mashape/kong/issues/2646#issuecomment-311057661, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AS5RdIt9zddKpZTDQXvWEcD6va9Levzgks5sH7CzgaJpZM4ODTzx.
CSC Technologies India Private Limited (a DXC Technology Company) - Unit 13, Block 2, SDF Bldgs, MEPZ SEZ, Tambaram, Chennai 600 045, Tamil Nadu. Registered in India, CIN: U72900TN2015FTC102489.
DXC Technology Company -- This message is transmitted to you by or on behalf of DXC Technology Company or one of its affiliates. It is intended exclusively for the addressee. The substance of this message, along with any attachments, may contain proprietary, confidential or privileged information or information that is otherwise legally exempt from disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient of this message, you are not authorized to read, print, retain, copy or disseminate any part of this message. If you have received this message in error, please destroy and delete all copies and notify the sender by return e-mail. Regardless of content, this e-mail shall not operate to bind DXC Technology Company or any of its affiliates to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose.

The doc does not instruct to run kong start. If you hit the admin API on your container's IP, it seems to work?

yes… once I give
curl http://<IP_ADDRESS>:8001
I get response.

Cheers
Abhishek Singh
PMP, CSM, SAFe, CSPO
DXC | EGL | Bengaluru | India
Ph: + 91 80 61762299 | CUG: 762299
From: Thibault Charbonnier<EMAIL_ADDRESS>Reply-To: Mashape/kong<EMAIL_ADDRESS>Date: Monday, 26 June 2017 at 11:54 PM
To: Mashape/kong<EMAIL_ADDRESS>Cc: "Singh, Abhishek 5"<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [Mashape/kong] Kong not starting in MAC (#2646)
The doc does not instruct to run kong start. If you hit the admin API on your container's IP, it seems to work?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Mashape/kong/issues/2646#issuecomment-311141485, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AS5RdMJGprKOh-pj3ZjqAaTJYYNEXf-Oks5sH_ddgaJpZM4ODTzx.
CSC Technologies India Private Limited (a DXC Technology Company) - Unit 13, Block 2, SDF Bldgs, MEPZ SEZ, Tambaram, Chennai 600 045, Tamil Nadu. Registered in India, CIN: U72900TN2015FTC102489.
DXC Technology Company -- This message is transmitted to you by or on behalf of DXC Technology Company or one of its affiliates. It is intended exclusively for the addressee. The substance of this message, along with any attachments, may contain proprietary, confidential or privileged information or information that is otherwise legally exempt from disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient of this message, you are not authorized to read, print, retain, copy or disseminate any part of this message. If you have received this message in error, please destroy and delete all copies and notify the sender by return e-mail. Regardless of content, this e-mail shall not operate to bind DXC Technology Company or any of its affiliates to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose.

but I see same error whenever I try to issue Kong commands as per doc
https://getkong.org/docs/0.10.x/getting-started/quickstart/
kong start
kong stop
kong reload
Can you please suggest how can I make use of these commands?

@asingh493 the commands above need to be issued inside the machine/container running Kong, not the Docker host.

thanks @p0pr0ck5
Will try....Kong document does not talk about if these commands need to be run inside the container.

@asingh493 the docs assume, I think, some basic knowledge of using Docker in the context. The docs are also open source at github.com/mashape/getkong.org; feel free to submit a PR to improve them if you think they are lacking. Thanks! :)

i also got this problem in my mac, anyone has a solution? it's 2020!

i also got this problem in my mac, anyone has a solution? it's 2020!
it's not in docker, just in my mac machine.

I got similar error, completely followed https://docs.konghq.com/install/source/?_ga=2.262757068.1939498096.1595639928-1882141532.1595639928

_ga

same error in ubuntu 18.04:

i also got this problem in my mac, anyone has a solution? it's 2020!
it's not in docker, just in my mac machine.

i got an similar error  in my mac too,steps followed https://docs.konghq.com/install/source/ ,have you solved the problem?

similar issue followed the same steps in mac followed https://docs.konghq.com/install/source/ ,have you solved the problem?

I slove it.  when you according to the official steps successfully installed,  and run kong cmd  must be in path $xxx/kong-sources/kong
for example:
cd xxxx/kong-sources/kong
kong start

similar issue followed the same steps in mac followed https://docs.konghq.com/install/source/ ,have you solved the problem?

I slove it. when you according to the official steps successfully installed, and run kong cmd must be in path $xxx/kong-sources/kong
for example:
cd xxxx/kong-sources/kong
kong start

I am in /kong-sources/kong and doing kong start having same error.

I am in /kong-sources/kong and doing kong start having same error.
try run
export LUA_PATH="xxxxxx/kong-sources/deps/luarocks/share/lua/5.1/?.lua;"

tried as you suggested , sharing the structure
*****/kong-sources/kong/kong
ERROR: /Users/niraj/kong-sources/kong/bin/kong:9: module 'kong.cmd.init' not found:
no field package.preload['kong.cmd.init']
no file './kong/cmd/init.lua'
*****/kong-sources/kong
ERROR: ./kong/globalpatches.lua:50: module 'socket' not found:
no field package.preload['socket']
no file './socket.lua'

and also when $ git clone git@github.com:Kong/kong.git
$ cd kong
$ git checkout 2.2.1
$ make install
an error is coming
Error: Failed installing dependency: https://luarocks.org/kong-plugin-serverless-functions-1.0.0-1.src.rock - Could not fetch rock file: Error fetching file: Failed downloading https://luarocks.org - Failed downloading https://luarocks.org/kong-plugin-serverless-functions-1.0.0-1.src.rock - /Users/niraj/.cache/luarocks/https___luarocks.org/kong-plugin-serverless-functions-1.0.0-1.src.rock

Thank you :), issue got resolved.
I have ran the below command and its working now.
$luarocks install luasocket

same error, it's 2021!!!!!!

when I meet the error like "no file xxxxxxx",I try to add the file to the lua path，such like:
1.change the filebin/kong, the value of package.path,try to add the path you need
2.change the environment variable LUA_PATH,try to add the path you need
3.change the file kong.conf,the value of lua_package_path,try to add the path you need
lua or kong will scan the path above。
the only way what I do is try to add the lua file to the path,now it works。I‘m build kong1.4.0.now it works,but maybe not in a standard way.


add pipeline_pixart_inpaint

Can we add a code block about how to use it?

Can we add a code block about how to use it?
Here is an example of how to use it:
”“”
from scripts.pipeline_pixart_inpaint import PixArtAlphaInpaintPipeline

prompt = ""
image = Image.open('')
mask_image = Image.open('')
out = pipe(
prompt,
image=image,
mask_image=mask_image,
strength=1.0).images[0]
out.save('/path/to/save')
“”“

Is there any sample pairs (image, prompt, mas) to show the results?

prompt=”“
The results above are the input image, the result, and the input mask.
An empty string is sufficient for prompt.

I just found a problem. I pull request with one account and commit with another.

How about the problem. Wondering any update :) @eightmusic

How about the problem. Wondering any update :) @eightmusic

代码部分没有更新，就是pr用的一个账号，commit是另一个账号，我就是说一下，这里面的两个账号都是我的

Ok. Cool. Approved and merged. Thank you so much for your PR. 🥰

Ok. Cool. Approved and merged. Thank you so much for your PR. 🥰

I also added this function in the diffuers official library, and the reviewer mentioned you. If you find it OK, could you please reply to him. @lawrence-cj

Got it. I'll look into it later.

Firstly, thank you for your PR.
But I had the following dimension error when running

I think we need to add the following code to do after line 972:

There is no problem with the code you added. This has something to do with the diffusers version. I used version 0.24.0 to implement it. @lavenderhhl

There is no problem with the code you added. This has something to do with the diffusers version. I used version 0.24.0 to implement it. @lavenderhhl

OK, I used diffusers==0.27.2 to implement it. Thank you!


No Session Found For Given Token

I think this is a DoltHub bug as well, but easy to reproduce with DoltLab.

Fixed in doltlab-v0.2.0


Unable to execute Dex

I am getting this issue while I am trying to build a project or APK. If I remove flutter_secure_storage, the project builds and APK is generated.

Please try again with latest code on develop branch and report if it's still not working


Blocker message are not Blocking explicit requests.

What is the issue?
If i am testing Ollama ability to block explicit requests , it will block it once but then if I tell it to write it again it ignores the blocker/filter.
OS
Linux, Windows
GPU
Nvidia, AMD
CPU
AMD
Ollama version
0.3.13

How are you giving this instruction to ollama?  What client are you using?  What model(s)?

How are you giving this instruction to ollama? What client are you using? What model(s)?

i am using ollama run llama3.2 and i am telling write me a story with the explicit information. At first it claims it cant right it, great that's what i want to see. but then i tell it again and spews out the request with the explicit information.

How are you giving this instruction to ollama on what to block?

How are you giving this instruction to ollama on what to block?

No I am letting find out on it's own.

How are you giving this instruction to ollama on what to block?
Is their a requirement to do that with ollama?

So you aren't telling it to block explicit information, then you ask it twice to give you explicit information, and it complies the second time.  Sounds like you convinced it that you really want the information.
A model has no judgement or intelligence, it's a text completion engine and it will generate anything you ask it if it doesn't have guidelines.

So you aren't telling it to block explicit information, then you ask it twice to give you explicit information, and it complies the second time. Sounds like you convinced it that you really want the information.
A model has no judgement or intelligence, it's a text completion engine and it will generate anything you ask it if it doesn't have guidelines.

oh i see, now I know theirs limitations on ollama. Thanks for telling me this.

It's not an ollama limitation, it's the nature of LLMs.

It's not an ollama limitation, it's the nature of LLMs.
got it


1581086, update image filenames part two 10-11.

Updates related to User Story 1581086.

@mairaw, this PR related to User Story 1581086 is ready for review.
Please have a look at the edits that I made and let me know if there's anything you'd like me to change or update.
CATs report: https://contentqacats.azurewebsites.net/CheckResults/2019101100007/Report/

@mvelosop I have incorporated your feedback. Please have a look. If everything looks good, feel free to sign-off.
If you notice anything else you'd like me to change, please let me know.


Do you support Collections?

http://jekyllrb.com/docs/collections/

Yes you do.
This works
pretzel:
    engine: liquid
collections:
- portfolioContent

This does not works:
pretzel:
    engine: liquid
    collections:
    - portfolioContent

Not exactly but we have "DirectoryPages" which can do almost the same things.

Does this mean it is not possible to configure the permalink structure differently for different "collections"? How do I have a different output folder structure depending on different source collections (e.g. _posts vs _pages)?

I must admit that I don't know, I haven't used them at all.
I wanted to add the real collections but haven't got the time...


Compile Error: 'utf-8' codec can't decode byte 0xd5 in position 4: invalid continuation byteCompile Error: 'utf-8' codec can't decode byte 0xd5 in position 4: invalid continuation byte

How to deal with this situation? Thank you for your help

Ask the same question，so do i.

If you can paste the base64 encoded shellcode, there may be an error there. But, without the compiler error, I can't tell you exactly what's happening.

your shellcode must be utf-8

python3 builder.py -s C:\Users\ivonne\Desktop\临时下载\Alaris\1\https.bin -p pass
[i] Key, IV Generation:       Successful
   [+] Key:   1c765353e47969fbca1b204287acfdea0c291b13ed0d47e8415e25b38f0ccb0f
   [+] IV:            ea8e0d4e7b20e6e9eb272a2c3599d91d
   [+] Salt:  88ee737cd1d6bb7d1b07054c5b000448
[i] Encrypt Shellcode:        Successful
[i] Variable Swap:    Successful
Compile Error: 'utf-8' codec can't decode byte 0xd5 in position 4: invalid continuation byte

How to deal with this situation? Thank you for your help


Added new project GitXpress

GitXpress is a website used to search people on Github using their usernames. Made with HTML,CSS JS and used Github API for data fetching.

Do not add a git repository
Add only projects


Require loaders

Implement a pluggable loader infrastructure in our module loader, similar to RequireJS plugins.

We are currently evaluating SystemJS #165


ATM

When i opened my ATM, mc decided i should hit the npc when closing the GUI. Maybe set the ATM to not retaliate if hit.

This should be fixed now.


Fix IPv6 detection for EKS

Please provide a description of this PR:
EKS clusters on IPv6 map a host-local NAT interface to each pod for IPv4 egress. For that the pod will be assigned an IP from the link-local reserved CIDR range (more specifcally, from <IP_ADDRESS>/22) that is unique only to the host. These IPs are not advertised to Kubernetes in any way, they are just available within the pod as the v4if0 network interface. For proper IPv6 detection we need to exclude these IPs from the discovery mechanisms, otherwise Istio thinks that it is in an IPv4 cluster when it sees this network interface.
More details on the EKS IPv6 networking can be found in the official blog post.
Unfortunately, I did not find existing tests for this code - if there are any that I have overlooked do let me know and I will update the pull request accordingly.
Fixes #36961.

Hi @mKeRix. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@mKeRix: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
74e62a681195e51b8e6247ece1b7372dd9e2e3e5
link
true
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Also I think this worth a release notes.

@bianpengyuan Added the release note now. I think excluding link-local multicast makes sense, I initially didn't include in this PR to keep it as small as possible to get the bug fixed. However, I'm happy to add it either directly to this PR or to open an additional followup PR - just let me know what you'd prefer.

@mKeRix: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-multicluster_istio
2111cf237340ad8033adb5e6097bf8cb00872892
link
true
/test integ-pilot-multicluster_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-pilot-multicluster_istio

I'm happy to add it either directly to this PR

@mKeRix I think it is fine to include that directly here

Done!

@mKeRix: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-multicluster_istio
2d849a5e26344603889e0363b515d1d23321e175
link
true
/test integ-security-multicluster_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

This seems reasonable but I don't have enough expertise to approve. @ramaraochavali @lambdai @costinm @hzxuzhonghu any concerns?

We had to do this for implementing dual-stack which we will have more information shortly. LGTM, but I'll wait to approve after the networking maintainers approve.


Fix raft node getting stuck in candidate state

This PR fixes an issue where a raft peer gets stuck in candidate state and never increments it's index.  This happens after an election and somewhat sporadically.  The root issue appears to be that the node in candidate state should return to follower state if it starts receiving heartbeats from a new leader.  The node was not returning to follower state causing it to become inconsistent w/ the cluster.
In addition to this fix, when running multiple nodes locally w/ raft tracing, it's very difficult
to determine which node is logging.  This adds the nodes state(leader,follower,candidate) and
id to all the log messages so we can trace the nodes states more easily.
Also fixes test output alignment when there is a failure in an integration test.

+1 on green build.

@benbjohnson -- please double-check this change.


Road to stable release

This package is almost ready for production usage, needs just some minor checking.

[ ] Review docs
[ ] Bump code coverage (Infection)
[ ] Remove any extra dependency

Get rid of "chevere/filesystem" dependency.


feat: kics api spec scanner

Proposed Changes

Create a release pipeline to publish a thin version of KICS with just API spec scanning capabilities

I submit this contribution under the Apache-2.0 license.

We're still testing this


Locking axis

Hi!
Is it possible to lock an axis of moved element, while dragging (for instance vertical or horizontal only)?

Not really

Could you add such feature? This will allow to sort the list by dragging in the IOS style.

Sorry, but no

@bevacqua would you accept a PR with an axis:"y"||"x" option?
I needed it on a project and implemented it in a local fork.

Sure

@cfenzo Did you open that PR you mentioned anywhere?

@cfenzo @bevacqua any updates on this?

I'm unclear why this issue is closed; but here's a PR for restricting the dragging element to an axis.

@philippfrank @d-steinberg Take a look at the PR and let me know if you have any questions.

@nguyenj Just in time, I had literally began to look at dragula.js the moment I got an email from this thread! Thank you!

Thanks @d-steinberg
@bevacqua how can I get this merged?


[Post] Seal vs Freeze vs PreventExtensions

this closed https://github.com/yceffort/yceffort-blog-v2/commit/17d6c13245f4ffb983d37aa7ffb5ff47d4ed7688


Fix some typo's

As the title says: this PR fixes some typo's.

Thanks, I'll merge this in shortly.

Thanks, @BernhardHofmann, definitely. I'm glad people are taking some interest. I'll be approving all of these pull requests on the next release of Blunder.

Thanks @mvanthoor, I also share a similar sentiment. Of course nothing wrong if an author chooses to work alone and only then share their engine, but it's nice and helpful to see things done from scratch and people work their engine up from mid-to-low 1000s up with 3000+. I also feel it's much more rewarding to heavily document things starting out so you can see how far you've come.
And excellent to hear regarding XBoard support. I look forward to seeing you finish your tuner and release the next version of Rustic! :)


Install test dependencies

I rule and have completed some work on Case Manager that's ready for review!
Small mod to install test / dev dependencies
This pull request makes the following changes:

Mods Dockerfile to install test/dev dependencies

It relates to the following issue #s:

Fixes #901

This pretty much duplicates #912 , although this goes straight to bundle install and removes the --without (not sure how that snuck in tbh). Either PR will solve the issue, this one is just a lil broader.

thanks a ton @zorkian and @DarthHater for working on this!


Workflow - Path Exclusion and Linux Job

Prevent workflows from running when we directly edit README, CONTRIBUTORS and LICENSE docs
Added a linux build and test job that runs on Ubuntu.

Note
The setup-swift action page for reference

Yes, I was exactly looking into this problem yesterday before calling it a night and going to sleep.
I've browsed the GH marketplace to no avail, there's no GitHub authored or verified equivalent.
I'm weary of granting permission. I expect in the future we'll have to deal with secrets, uploads to servers and the like. If we grant them permission, we're not just trusting their code, which is fine, but also that this code will never be tampered with, which is not so certain.
Another option is to fork their sources and I'm giving it a try. What do you think?

I think you can grant access to a specific release / commit. This would allow us to look over any new code / changes before approving it. Which I guess is similar to forking it into the swift-quic repo but less code duplication.

Looking at some other swift-nio projects, they seem to be using Docker to handle all of their CI. I'm not very well versed in Docker. But they've probably thought through a bunch of these issues and decided Docker was the way to go.
https://github.com/apple/swift-nio/tree/main/docker
Maybe that's a bridge we cross later on...

Looking at some other swift-nio projects, they seem to be using Docker to handle all of their CI. I'm not very well versed in Docker. But they've probably thought through a bunch of these issues and decided Docker was the way to go.
https://github.com/apple/swift-nio/tree/main/docker
Maybe that's a bridge we cross later on...

Exactly! I think we'll eventually go this way.

Forking setup-swift apparently worked. I think we can leave it as this for now. What do you think?

Sounds good for the time being!


Add initial fixture for categories

Generated using:
./manage.py dumpdata categories_i18n (after populating via admin)
Should migrate using:
./manage.py loaddata healthmate/sources/fixtures/categories_i18n.json
(last thing is currently not working, do we need to move fixture folder / set some config somewhere?)

:+1:


CREO2URDF – Correctly handle the joint definition when using CSYS

In creo2urdf the linkFrames parameter is optional, it allows to specify which frame has to be used as the reference frame for a specific link.
To be compliant with the urdf specification, this frame has to lie on the axis of the joint of which the link is the child link.
If not specified we use the default CSYS that may have an offset w.r.t the axis of the joint, this means that the joint right now might rotate "outside" the link
✔ We correctly handle it

❌ We do not handle it correctly

In:

#97

a lot of debugging has been made but unfortunately something is missing

Thanks to:

https://github.com/robotology/idyntree/pull/1193

this issue now is way simpler!

Thanks to the PR of @traversaro in idyntree now we can export the icub urdf!

cc @pattacini @maggia80 @fiorisi @Lawproto @salvi-mattia @mfussi66


Making sure Score .to_float() can handle strings (in tasks that are scored by strings, e.g. GAIA)

This PR contains:

[ ] New features
[ ] Changes to dev-tools e.g. CI config / github tooling
[ ] Docs
[X] Bug fixes
[ ] Code refactor

What is the current behavior? (You can also link to an open issue here)
Currently the to_float doesn't handle string inputs (not sure if this a was change!), leading to errors like:
│ │                                                                                │                                                                            │
│ │ /home/ubuntu/src/agent_framework/.venv/lib/python3.12/site-packages/inspect_ai/scorer/_metric.py:87 in as_float      │                                                                            │
│ ╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯                                                                            │
│ ValueError: could not convert string to float: 'I'

This would fix it for me. I suspect its a wrong/incorrecfix, value_to_float needs to be configurable with how you are mapping values to float - more opening for discussion, I suspect @jjallaire can rustle up a better fix quite quickly.

Closing since we rolled back the error. I'll take an another crack at the underlying issue soon! Thanks for catching this and suggesting this fix!


Solution: Deleted Quantum.Normalizer.field type

Should fix #246 .
In fact, the cause is the same as in #214 : missing value (:timezone) in the field type.
But then I thought, maybe it's better to remove this type, since there is no easy way in Elixir to avoid duplication of a value list in the typespec.

Changes Unknown when pulling 3cd5581449d34a8f0aa5acd56a9eec0d42b18501 on narkq:remove-job-field-type into ** on c-rack:master**.

Thank you very much @narkq ❤


Idea

Hi!
Can make animations like this?
https://github.com/daimajia/NumberProgressBar

Well, you can put that in a custom view dialog.
Including it in this library will increase the size of it a bit. To follow the guidelines, it's better to match stock views.
That's a very cool looking library though, just starred it.

Thank you for the quick response!


"Query" button grayed out

When I now visit https://php.energy/trealla.html using Firefox 78.15.0esr (64-bit), Chrome or Safari on OSX, the "Query" button is unexpectedly grayed out, and I cannot post a query (also not using ENTER).
This is highly unexpected, what could be the reason for this?

Sorry about that. It starts grayed out until the library loads and initializes as a very crude loading bar. Need to add an error message when it fails. Might be related to #11. Will take a look. If you look at the browsers develop console output it should tell you why it failed.

When loading the page in Firefox, the single message I see in the console is:

[Exception... "Favicon at "https://php.energy/favicon.ico" failed to load: Not Found."  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: resource:///modules/FaviconLoader.jsm :: onStopRequest :: line 227"  data: no] [FaviconLoader.jsm:227:22](resource:///modules/FaviconLoader.jsm)
    onStopRequest resource:///modules/FaviconLoader.jsm:227

So, it seems that the only issue is that favicon.ico failed to load, this seems not so serious.

Thank you, this works as expected now on OSX!


[AIRFLOW-1723] Support sendgrid in email backend

Dear Airflow maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[x] My PR addresses the following Airflow JIRA issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-1723

Description

[x] Here are some details about my PR, including screenshots of any UI changes:
Extend airflow email backend to support sending emails via sendgrid.

Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:
tests.utils.test_email to ensure the mail data is constructed correctly.

May want to include sendgrid package install in setup.py and requirements.txt (for ci)

@andyxhadji good point, was about to add these :+1:

Codecov Report

Merging #2695 into master will decrease coverage by 0.14%.
The diff coverage is 51.61%.

@@            Coverage Diff             @@
##           master    #2695      +/-   ##
==========================================
- Coverage   71.77%   71.62%   -0.15%
==========================================
  Files         154      154
  Lines       11814    11845      +31
==========================================
+ Hits         8479     8484       +5
- Misses       3335     3361      +26

Impacted Files
Coverage Δ

airflow/utils/email.py
84.25% <51.61%> (-13.15%)
:arrow_down:

airflow/task_runner/bash_task_runner.py
93.33% <0%> (-6.67%)
:arrow_down:

airflow/utils/helpers.py
53.44% <0%> (-2.88%)
:arrow_down:

airflow/jobs.py
79.06% <0%> (-0.46%)
:arrow_down:

Continue to review full report at Codecov.

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

@criccomini mind taking a quick look?

Started a mail chain about reverting this commit from the master.
cc - @criccomini @Fokko @mistercrunch @r39132 and @bolkedebruin

I'm fine with reverting and doing a plugin instead, as discussed on email.


Dealing with .netmodule files

Hi,
Is it possible to support .netmodule files? not only DLL files. I have .netmodules files need to protect, some tools like dnSpy can convert .netmodule to dll, however when I convert back from dll to .netmodule, the file is corrupted, so I need to protect .netmodule files directly without conversion.
Thanks.

The problem is that dnspy and ConfuserEx are using the same library to handle assemblies and modules (dnlib). So even if I add the support for directly working with netmodules you'd like encounter the same issue.
Is the module actually being corrupted if you just put it into an assembly and pull it back out right away (without obfuscating it)?
If so, the question is why dnSpy is corrupting the netmodule. That is a question for @0xd4d over at 0xd4d/dnSpy. Placing the module in an assembly and pulling it back out shouldn't corrupt it.

Hi, thanks for your reply, the issue is the application is using a DLL with OnDisk metadata (i.e: hosing its module as external .netmodule files), so to use Confuser, I had to convert it to DLL, then protect it, then convert it back to .netmodule file, the problem, is when converting the protected DLL back to .netmodule, it does not produce a .netmodule file correctly (Actually this is good protection), that's why I need to select a .netmodule in Confuser, so that I don't need to convert the "protected" DLL back to .netmodule file!
I hope I clarified the problem well! thanks.

This is something I won't be able to implement quickly. Access to the assembly is done in many different places in the code of ConfuserEx.
From my initial analysis I can tell you that the resources protection is very likely the source of the issues for you. This protection will not work without an assembly. Could you give it a shot without this protection enabled? Just remove it from the rules in general to make sure it's disabled.
Also everything related to WPF will cause a lot of issues. If the assemblies contains XAML files, the rename protection will not work, unless you disable renXaml


CRDs are deleted when uninstalling with helm

Otterize CRDs are currently managed by helm, so running helm uninstall  removes them and as a result, all matching CRs. This can cause network policies and Kafka ACLs created by those custom resources to be removed as well, which is not the desired behavior.
We address this in 2 separate stages:

Firstly, add "helm.sh/resource-policy": keep annotation to prevent helm for uninstalling CRDs. Merged in helm charts PR.
Move CRDs to the helm crds directory and out of templates, as helm best practices suggest.

Fixed in https://github.com/otterize/helm-charts/pull/63


Add the required "source" line and fix spelling mistakes

Adding the source bin/activate line to show people how to actually activate the newly created virtualenv.
Fixing up some spelling mistakes.

👍 Thanks for the PR!


KubeClarity installation using Helm fails | grype-server pod CrashLoopBackOff status

What happened:
KubeClarity installation using Helm fails after following the steps outlined at https://github.com/openclarity/kubeclarity#install-using-helm
What you expected to happen:
All pods are expected to up and running. KubeClarity UI should be accessible after port forwarding
How to reproduce it (as minimally and precisely as possible):

Install the latest Helm charts

# helm repo add kubeclarity https://openclarity.github.io/kubeclarity
"kubeclarity" has been added to your repositories

Update the Helm charts to ensure latest version

helm repo update kubeclarity
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "kubeclarity" chart repository
Update Complete. ⎈Happy Helming!⎈

Save KubeClarity default chart values
No changes made to default "value.yaml"

Deploy KubeClarity with Helm

# helm install --values values.yaml --create-namespace kubeclarity kubeclarity/kubeclarity -n kubeclarity
NAME: kubeclarity
LAST DEPLOYED: Fri Mar 24 14:20:03 2023
NAMESPACE: kubeclarity
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
Thank you for installing KUBECLARITY.

Your release is named kubeclarity.
Here is how to access the KubeClarity UI:
    $ kubectl port-forward --namespace kubeclarity svc/kubeclarity-kubeclarity 9999:8080
    $ Open KubeClarity UI in the browser: http://localhost:9999/

Confirm if all pods are running

# kubectl get pods --namespace kubeclarity
NAME                                                    READY   STATUS     RESTARTS      AGE
kubeclarity-kubeclarity-76b95bb8c-k8l6q                 0/1     Init:2/3   0             29s
kubeclarity-kubeclarity-grype-server-7d5bb4fbfc-gr4mv   0/1     Error      2 (22s ago)   29s
kubeclarity-kubeclarity-postgresql-0                    1/1     Running    0             29s
kubeclarity-kubeclarity-sbom-db-748c45594b-mzjv4        1/1     Running    0             29s

Are there any error messages in KubeClarity logs?
(e.g. kubectl logs -n kubeclarity --selector=app=kubeclarity)
Seems Readiness probe fails for grype-server pod. Please see the logs below
# kubectl describe pod/kubeclarity-kubeclarity-grype-server-7d5bb4fbfc-gr4mv --namespace kubeclarity
Name:             kubeclarity-kubeclarity-grype-server-7d5bb4fbfc-gr4mv
Namespace:        kubeclarity
Priority:         0
Service Account:  kubeclarity-kubeclarity-grype-server
Node:             kind-worker2/<IP_ADDRESS>
Start Time:       Fri, 24 Mar 2023 14:20:04 +0530
Labels:           app=kubeclarity-kubeclarity-grype-server
                  pod-template-hash=7d5bb4fbfc
Annotations:      <none>
Status:           Running
IP:               <IP_ADDRESS>
IPs:
  IP:           <IP_ADDRESS>
Controlled By:  ReplicaSet/kubeclarity-kubeclarity-grype-server-7d5bb4fbfc
Containers:
  grype-server:
    Container ID:  containerd://01823316ed798f55c2de2b793b5e3ee40f166bc9447961c924ae873ac1a7dca4
    Image:         gcr.io/eticloud/k8sec/grype-server:v0.1.5
    Image ID:      gcr.io/eticloud/k8sec/grype-server@sha256:0791bcb8688a437ba71ae4d9d1bf350be88fff6124c661d40d1317124e860fae
    Port:          <none>
    Host Port:     <none>
    Args:
      run
      --log-level
      warning
    State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       Error
      Exit Code:    1
      Started:      Fri, 24 Mar 2023 14:20:49 +0530
      Finished:     Fri, 24 Mar 2023 14:20:49 +0530
    Ready:          False
    Restart Count:  3
    Limits:
      cpu:     1
      memory:  1G
    Requests:
      cpu:      200m
      memory:   200Mi
    Liveness:   http-get http://:8080/healthz/live delay=10s timeout=10s period=30s #success=1 #failure=5
    Readiness:  http-get http://:8080/healthz/ready delay=0s timeout=10s period=30s #success=1 #failure=5
    Environment:
      DB_ROOT_DIR:  /tmp/
    Mounts:
      /tmp from tmp-volume (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-qcp6m (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  tmp-volume:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  kube-api-access-qcp6m:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   Burstable
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason     Age                From               Message
  ----     ------     ----               ----               -------
  Normal   Scheduled  83s                default-scheduler  Successfully assigned kubeclarity/kubeclarity-kubeclarity-grype-server-7d5bb4fbfc-gr4mv to kind-worker2
  Normal   Pulled     81s                kubelet            Successfully pulled image "gcr.io/eticloud/k8sec/grype-server:v0.1.5" in 925.975547ms
  Normal   Pulled     77s                kubelet            Successfully pulled image "gcr.io/eticloud/k8sec/grype-server:v0.1.5" in 867.647423ms
  Warning  Unhealthy  76s (x2 over 79s)  kubelet            Readiness probe failed: Get "http://<IP_ADDRESS>:8080/healthz/ready": dial tcp <IP_ADDRESS>:8080: connect: connection refused
  Normal   Pulled     62s                kubelet            Successfully pulled image "gcr.io/eticloud/k8sec/grype-server:v0.1.5" in 891.527807ms
  Normal   Pulling    40s (x4 over 82s)  kubelet            Pulling image "gcr.io/eticloud/k8sec/grype-server:v0.1.5"
  Normal   Created    39s (x4 over 81s)  kubelet            Created container grype-server
  Normal   Pulled     39s                kubelet            Successfully pulled image "gcr.io/eticloud/k8sec/grype-server:v0.1.5" in 851.217379ms
  Normal   Started    38s (x4 over 80s)  kubelet            Started container grype-server
  Warning  BackOff    25s (x7 over 75s)  kubelet            Back-off restarting failed container

Anything else we need to know?:
Environment:

Kubernetes version (use kubectl version --short):
Client Version: v1.26.1, Kustomize Version: v4.5.7, Server Version: v1.25.3

Helm version (use helm version):
v3.11.1

KubeClarity version (use kubectl -n kubeclarity exec deploy/kubeclarity -- ./backend version)

KubeClarity Helm Chart version (use helm -n kubeclarity list)
NAME            NAMESPACE       REVISION        UPDATED                                 STATUS          CHART                   APP VERSION
kubeclarity     kubeclarity     1               2023-03-24 14:20:03.624246496 +0530 IST deployed        kubeclarity-v2.14.0     v2.14.0

Cloud provider or hardware configuration:
On-prem, Ubuntu 20x

Others:

Hi @sprathod369 thanks for reporting the issue.
I see that the pod is in CrashLoopBackOff, can you please share the log before the crash, you can use logs -p to get them.
kubectl logs -p pod/kubeclarity-kubeclarity-grype-server-7d5bb4fbfc-gr4mv --namespace kubeclarity

Thanks @FrimIdan  - here are the logs
kubectl logs -p pod/kubeclarity-kubeclarity-grype-server-7d5bb4fbfc-gr4mv --namespace kubeclarity
time="2023-04-05T05:07:42Z" level=fatal msg="Failed to start scanner: failed to load DB: unable to check for vulnerability database update: unable to download listing: Get "https://toolbox-data.anchore.io/grype/databases/listing.json\": x509: certificate signed by unknown authority" func=main.run file="/build/grype-server/cmd/grype-server/main.go:53"
While using grype standalone in the past, I had observed a similar ad-hoc issue with database update. My pipeline works (if I'm lucky) but the same pipeline fails multiple times due to the database download issue. There are already some open issues wrt vulnerability database download and updates reported in Grype GitHub.
I'm able to curl https://toolbox-data.anchore.io/grype/databases/listing.json from my Ubuntu VM so I doubt if this is getting blocked by firewall on my end.

Unless I'm missing something, I've commented on a reported issue in Grype community #310 issues as even the latest version of Kubeclarity (v2.18.1) setup fails using the default as-is values.yaml.
Below are my K8s logs.
root@xxxx:~/KubeClarity# kubectl logs pod/kubeclarity-kubeclarity-grype-server-7d969b865-9lxks --namespace kubeclarity
time="2023-05-25T11:12:48Z" level=fatal msg="Failed to start scanner: failed to load DB: unable to check for vulnerability database update: unable to download listing: Get \"https://toolbox-data.anchore.io/grype/databases/listing.json\": tls: failed to verify certificate: x509: certificate signed by unknown authority" func=main.run file="/build/grype-server/cmd/grype-server/main.go:53"

How do I check what Grype image version is in use by the Kubeclarity v2.18.1?

How do I check what Grype image version is in use by the Kubeclarity v2.18.1?

You can see in the go.mod of the grype server repo, current grype version is v0.61.0
BTW - I've tested the latest version an it works find on my env, it might be something in your outbound network configuration, are you running behind a proxy or something?


Add setting options on the naming format and location of the newly created diagrams

Hi, thank you for making this great plug-in!
This PR basically provides setting options and implementations of:

Allow creating diagrams in the attachment folder specified in the Obsidian Settings (Files & Links > Default location for new attachments).
Allow naming new diagrams in the format of ${activeFileName}-${timestamp}.svg.

Demos & Tests
Testing Directory Structure
- Vault
    - testfolder
        - testfolder.md
    - ZOB_assets

Settings page

Default location: "Same folder as current file", timestamp naming on, wikilink: relative path
Obsidian settings

Demo
https://user-images.githubusercontent.com/11176415/230839195-d1f35ce7-2977-49ab-8e87-45136f72e5e6.mov
In File Explorer

Default location: specified global attachments folder, wikilink: relative path

Default location: specified global attachments folder, wikilink: absolute path

Will open a new PR for the same feature. The implementation in this PR is able lol


ignore date expiration

implements https://github.com/tfsec/tfsec/issues/758
new feature: expiration date for ignore
Adds in expiration date for ignore so that when adding ignore I can decide when I should be reminded about check that I am ignoring.
Current format
# tfsec:ignore:AWS006 exp:2221-12-02

This is still WIP
but @owenrumney does it make any sense and is worth pursuing?
@vsetka any input ideas?

Can we go with no spaces when there is an expriy. something like
# tfsec:ignore:AWS069:exp:2021-12-02

ok @owenrumney # tfsec:ignore:AWS069:exp:2021-12-02 will be now supported I ll just cover the edge cases.

Cool cool, sounds good

@owenrumney this is ready to be reviewed
The one thing requiring improvement is the way we should communicate to the user that the date format is probably incorrect and we were not able to parse it thus we cant use this ignore.
https://github.com/tfsec/tfsec/pull/762/files#diff-7d15dd8f6560094188d965b3619a075c1ee50bc7a80ce28374c9ea409d19957bR137
Any ideas how to do it?
I tried using tml but at this level it breaks unit tests as tml changes something in execution context.
At the moment I have put debug.log in there.

Reversed the logic:
Here is a snippet of how the debug log looks like.
[DEBUG][2021-06-24 19:07:06.300724775 +0200 CEST m=+0.001887818] Running rule for AWS006 on resource.aws_security_group_rule.my-rule (/home/michal-franc/Work/go-src/github.com/michal-franc/tfsec/bin/linux/test.tf)...
[DEBUG][2021-06-24 19:07:06.300753002 +0200 CEST m=+0.001916045] Expiration date found on ignore '# tfsec:ignore:AWS006:exp:2000-01-02 #tfsec:ignore:AWS018'
[DEBUG][2021-06-24 19:07:06.300761128 +0200 CEST m=+0.001924171] Ignore expired, check will be performed Filename: /home/michal-franc/Work/go-src/github.com/michal-franc/tfsec/bin/linux/test.tf:2

Also fixed the scenario with
#tfsec:ignore:AWS018:exp:2021-10-12 #tfsec:ignore:AWS006

Didn't have to make tokenization but instead as the checks are performed per rule we can actually check if line contains <code>:exp for example AWS018:exp.

Thanks @michal-franc  - just need to sync your branch then we can merge

@owenrumney I have just rebased it.

Updating docs now and it is good to go.


Added a null check for the messages we receive from Symphony in Proce…

Added a null check for the messages we receive from Symphony in ProcessMessageList since it could be null. This was the case when we received a payload from Symphony when a user removes a connection with our bots.

@malaysf can you take a look at this? Thanks.


feat: support bit bucket

Loading config from environment variables via viper now, to support multiple CI system.
A general renaming of arguments is required.

github-repo(r) -> repo(r)

github-owner(o) -> owner(o)

github-token -> token

add bitbucket support

BREAKING CHANGE: rename cli argument short and long names
closes #29

Did this request die? I wanted to do gitlab support (and probably will in my fork) but I would much rather it be part of the upstream repo. That requires the refactoring to support multiple providers so I can implement to those patterns. Happy to help where I can.

Sounds great, I continue on Sunday and let you know

:tada: This PR is included in version 2.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Tips router should not invoke page move

In use case, user's swipe gesture is the only way to go back (especially for IOS user). User's router history should be simple. So, Tips topic selection's page move is not suitable. It could be occur frequently that mess up user router history.

Tips topic selection and pagination do not make page move
Enhance type inference for Topic page

Okay, I understand your intention and I agree that pushing history on every topic selection is redundant.
But your implementation has a problem. Selecting a topic never leaves a trace in URL, which means users cannot reach the page with a specific topic directly. For instance, think about this use case,

A user visit the page and click a topic ('exam' for example)
then share it with friends.
Friends press the link
and they will always see the page with default option ('all').

I think replacing history instead of pushing might be a better solution.


Serve static files

Closes https://github.com/ethyca/fides/issues/560
Code Changes

[ ] Add static files to API server

Steps to Confirm

[ ] Spin up the webserver and hit localhost:8080 to see a minimal frontend

Pre-Merge Checklist

[ ] All CI Pipelines Succeeded
Documentation Updated:

[ ] documentation complete, or draft/outline provided (tag docs-team to complete/review on this branch)
[ ] documentation issue created (tag docs-team to complete issue separately)

[ ] Issue Requirements are Met
[ ] Relevant Follow-Up Issues Created
[ ] Update CHANGELOG.md

Description Of Changes
Adds a path where static files can be served from our existing python webserver.

@allisonking fill out the PR description and merge when ready!


--default-resources combined with partial resource specification causes TypeError

Snakemake version

7.3.5+0.g4f2258ff.dirty
Describe the bug

When running snakemake using --default-resources, but without specifying mem_mb so that the Snakemake-defined default of mem_mb=max(2*input.size_mb, 1000) kicks in, along with the --resources flag with mem_mb, if a root rule specifies a mem_mb requirement under its resources directive and a downstream rule doesn't, the downstream rule will error out with
TypeError: '>' not supported between instances of 'TBDString' and 'int'

Logs

Minimal example

# Snakefile
rule all:
    input:
        "a.out"

rule a:
    output:
        "a.out"
    resources:
        mem_mb=2000, # Note that resources are specified here, but not in all.
    shell:
        "touch {output}"

# CLI call
snakemake --default-resources --resources mem_mb=4000 -c1 all

Additional context
The last version the above code will work is v6.4.1. The first version the error appears in is v6.8.0. Weirdly, in v6.7,6,5, I get completely different errors, but perhaps those issues have been resolved?
# 6.6,7
TypeError: unsupported operand type(s) for +=: 'int' and 'str'

# 6.5
AttributeError: 'list' object has no attribute 'items'

I'm currently looking into the source if the error, although it obviously stems from the fact that, in the example above, all does not know the size of it's input, so it's mem_mb gets automatically set to "<TBD>". Obviously in previous versions that would get reset when all actually ran, but this isn't happening any more.

Here's the complete trace:
Traceback (most recent call last):
  File "/path/to/snakemake/lib/python3.9/site-packages/snakemake/__init__.py", line 722, in snakemake
    success = workflow.execute(
  File "/path/to/snakemake/lib/python3.9/site-packages/snakemake/workflow.py", line 1099, in execute
    success = self.scheduler.schedule()
  File "/path/to/snakemake/lib/python3.9/site-packages/snakemake/scheduler.py", line 484, in schedule
    run = self.job_selector(needrun)
  File "/path/to/snakemake/lib/python3.9/site-packages/snakemake/scheduler.py", line 638, in job_selector_ilp
    return self.job_selector_greedy(jobs)
  File "/path/to/snakemake/lib/python3.9/site-packages/snakemake/scheduler.py", line 823, in job_selector_greedy
    a = list(map(self.job_weight, jobs))  # resource usage of jobs
  File "/path/to/snakemake/lib/python3.9/site-packages/snakemake/scheduler.py", line 897, in job_weight
    return [
  File "/path/to/snakemake/lib/python3.9/site-packages/snakemake/scheduler.py", line 898, in <listcomp>
    self.calc_resource(name, res.get(name, 0)) for name in self.global_resources
  File "/path/to/snakemake/lib/python3.9/site-packages/snakemake/scheduler.py", line 877, in calc_resource
    if value > gres:
TypeError: '>' not supported between instances of 'TBDString' and 'int'

An immediate fix that DOES work is to modify rules.resources so that every time it's called, it checks for a "<TBD>" in rules._resources. If found, it reevaluates the resources by calling self.rule.expand_resources(...) again.
Happy to make a PR, but this may be too much the "band-aid" fix for a deeper problem. Let me know what you'd like.

Thanks a lot, good catch! I have fixed this in above PR. Basically the call to update the resources before scheduling came too late.


Fixing bug if no efo short form is present in the solr

This modification supposed to deal with cases when the solr document doesn't have EFO shortForm. In that case, the mapedUri is used and parsed the short form out of it. If that is also missing, the document is skipped.
As the mappedUri is seemingly always there, we can just use that? Anyways, curators have verified this modification.

Looks good! There are some other locations where "efoLink" is used in functions, I'll push an update for those changes.
As a note, the attributes missing in the Fat Solr for EFO terms that are not yet in a released version of EFO are: parent, efoLink, label, shortForm

Oops, meant to close comment not close the PR.


Update RecordCount on ManagedZone

The managed zone API response doesn't contain information about the number of records in a zone, instead we can just make a request to get all the records and set it to the length.
Other minor updates:

Fix issue with nameservers not updating correctly
Improve handling of ManagedZone and DNSRecord deletion
Use pointer receiver
Order, public before private
Use ensureTrailingDot
Add toManagedZoneOutput to convert a google ManagedZone into the mgc expected output

@R-Lawton Leaving it up to you to merge this or not

/close


Make foldmethod configurable

I'm not sure what is the best practice to do that, but some way of configuring it would be nice. Example, the user can do:
let g:solidity_fold = 'manual'

and the way of using it in the plugin is
let &l:foldmethod=get(g:, 'solidity_fold', 'syntax')

I can send a PR if you are ok with adding this option and with this approach.

Agreed it should be configurable! Down to peek at a couple other plugins to see what's common?

From grepping my ~/.vim/bundle:

pangloss/vim-javascript doesn't set foldmethod, it just gives you instructions on how to do it in the readme.
rust.vim has a g:rust_fold variable, where 0 is no folding, and 1 are 2 set the method to syntax with different levels

The rest of the plugins only change foldmethod temporarily or for plugin-specific buffers.
I think both approaches make sense, but personally I prefer the vim-javascript one of not doing anything and assuming this is done by the user.

@Philogy going to take this approach of not stomping on foldmethod. Thanks @fvictorio!


IEM: added Zenodo data download links

@manojneuro Sorry for the delay. The datasets are now uploaded and available at https://zenodo.org/record/4950267.
The individual files are now linked in the notebook.

LGTM


Improved error message when topic name changes within same supervisor

Recently ran into a situation where a task failed with an error "Aborting Transaction". The error is not user-friendly and doesn't really tell the user what they can do about it. In this PR, I try to surface the actual error that caused the transaction to be aborted. So users don't have to stitch together an error in overlord logs and a failure message in task reports to figure out what's going on.
Apart from that, changed the error message of query timeout exceptions. A user, who is issuing a query, doesn't know anything about the sequence iterator. We developers often throw errors that can include too many implementation details. These details can appear daunting to users who are just starting out.
This PR has:

[ ] been self-reviewed.
[ ] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
[x] added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
[ ] been tested in a test Druid cluster.

this seems to be failing CI https://github.com/apache/druid/actions/runs/4335791832/jobs/7570791036 which has broken master for other PRs such as https://github.com/apache/druid/actions/runs/4360704265/jobs/7624217643
currently looking into a fix...


Create a home/root entry point

I saw a blank page when running the solution. Two options to consider:
A) Creating a RootController with a default /index action method that renders the server's time.
B) Route to an API description/doc if we have. I couldn't check the swagger changes yet. Does that provide a UI that we can point to?

Fixed with #25


master update dev tooling

This updates development tooling on the master branch.
Note: This should not be squashed.

This is ready to be merged now.


Bug: Service redshift with wrong brightness

16.09.git.89c567c (Flounder)
I am using Plasma5, but after I logged out, RedShift displayed a login screen on my main monitor in a way too dim fashion. Additionally, I was not able to move the mouse to this login screen. After a reboot everything was fine again.
Relevant configuration:
  services.redshift.enable = true;
  services.redshift.brightness.day = "0.8";
  services.redshift.brightness.night = "0.4";
  services.redshift.latitude = "52";
  services.redshift.longitude = "4";

  services.xserver.displayManager.sddm.enable = true;
  services.xserver.desktopManager.kde5.enable = true;

Graphics hardware: NVIDIA Corporation GM107M [GeForce GTX 960M] (rev a2)

The whole point of a service like redshift is that it should always work. I am not sure whether there are any debugging files for redshift, but I would like to see a feature where one can configure such a file, if it doesn't exist yet.
It might be that this cannot be debugged in its current state, but I am sure this will also happen to others, and as such at least there is just a starting point for further investigation and collecting experiences.

Are there any updates to this issue, please?


logback 1.4.8 breaks RequestScopedMdc

https://github.com/qos-ch/logback/commit/ca7fbc7f4c1b1883092037ee4a662034586df07a / https://jira.qos.ch/browse/LOGBACK-1742 changed how the MDCAdapter is taken from at log time to at logger creation time. This means that if the logger object is created outside the request (e.g. a static logger object), the MDCAdapter attached to the object is not RequestScopedMdc.Adapter, and the MDC recorded at log time does not use RequestScopedMdc. A possible workaround is to create the logger at request time.
I'm unsure if this is something to fix in Armeria (is it possible to register this adapter earlier?), or something to fix in Logback.

Thanks for reporting! It's being fixed at #5079 :bow:

I'm unsure if this is something to fix in Armeria (is it possible to register this adapter earlier?), or something to fix in Logback.

I had to use reflection to illegally access LogbackMDCAdatper in LoggingContext because Logback disallows overriding the MDCAdapter set before.
https://github.com/qos-ch/logback/blob/ca7fbc7f4c1b1883092037ee4a662034586df07a/logback-classic/src/main/java/ch/qos/logback/classic/LoggerContext.java#L412-L419
@r3mariano It would be worth opening an issue to Logback to override LogbackMDCAdatper with an API. Otherwise, the hacky workaround could be broken easily.

Thanks so much for the fix. I've emailed the logback-dev mailing list to see what they think.


How would I go about adding Tailwind

Sorry if this is an annoying question - but how would I go about adding a CSS library like TAILWIND - I know how to add this to an existing Phoenix app - but if you could give a few pointers that would be awesome - Thanks for your hard work creating this project...

Hey @netflakes we are about to finish some work that will make it super easy to integrate node packages. There are so many ways we can do this that we need to test a bunch of things. Still (:p) I didn't want to leave you waiting so I made a little example to get you started https://github.com/still-ex/tailwind_example some of this will not be necessary afterward. There are two commits, the first is just the scaffold, the second is what you want.
I'll keep this issue open until we have that other package.

Hey @netflakes are you still looking for tailwind support? We are just doing some final testing on the snowpack support here and I already updated my website with tailwind. If you have the time, let me know what you think!

Fixed in https://github.com/still-ex/still/commit/c954a8bc6ae9b88e9e7e77f3acbc49f6aeec2980


Fix ClientLogger issue with GraalVM native

See https://github.com/Azure/azure-sdk-for-java/issues/39699#issuecomment-2110510713
Fix #39699

API change check
API changes are not detected in this pull request.


Do not print stacktrace for socket timeout exceptions

Talking with @hideki, I asked him if this was due to an error. He said that this doesn't not need to be printed since it is not an error state but rather a transient timeout. https://gist.github.com/sethrosetter/f1151d1eca25f25f498c#file-gistfile1-txt-L16-L43

I believe this is already fixed.


What about Yarn PnP support?

Any loader used in PnP mode can't resolve/load any packages except Node builtins. Yep, we have discussion in Node community how to improve loaders, how to redesign API, etc.
But now only one way - to have bundled loader. It works perfectly for me (I use simple esdbuild-based transpiler for .ts, as an example), but I can't use esmock 'out of box' (proxy bundle is the way, but...) to try node native test runner instead of Jest.
Can we remove single external dependency, 'resolvewithplus' here? Or, mark it optional and use import.meta.resolve (by flag / different import path like esmock/native or so on).

@koshic does resolvewithplus need to be removed from package.json? If resolvewithplus is not removed from package.json, but if esmock does something like this, would this work for your situation?
const resolver = typeof import.meta.resolve === 'function'
  ? import.meta.resolve
  : (await import('resolvewithplus')).default

@jakebailey I think the second one is the best solution, with marking resolvewithplus as optional peer dependency, thx!

there will be less maintenance, if we wait for import.meta.resolve to be stable and complete before using it.

Or, mark it optional and use import.meta.resolve (by flag / different import path like esmock/native or so on).

a good idea BUT esmock tried exporting something like this a month or two ago and typescript does not support this sort of thing https://github.com/TypeStrong/ts-node/discussions/1877 even if typescript could (or can?) do this, the support is or will not be great and annoying complexity necessary to placate typescript

"import.meta.resolve" does not resolve subpaths. The test creates a call like await import.meta.resolve('#sub', parent)

It supports:

there will be less maintenance, if we wait for import.meta.resolve to be stable and complete before using it.

--experimantal-loaders is experimental too, so waiting can be looong )

@koshic if you approve this PR, let's merge and use follow-up PRs to specifically resolve the two issues,

https://github.com/iambumblehead/esmock/issues/178 use loader mechanism directly to detect esmock loader,
https://github.com/iambumblehead/esmock/issues/176 (this ticket) make resolvewithplus an optional dependency

I have not used optional dependencies myself so am interested to see how it works. If resolvewithplus is an optional dependency, will npm continue to download it by default for esmock? My research indicates resolvewithplus will continue to be downloaded in the default case, but I haven't used optional dependencies before so am not certain.
@koshic if you still have test files you made for testing stub export, would you test if import.meta.resolve returns paths for moduleIds with extensions like "tsx" or "json"? If you're not interested to test this that's good and I can make a little test later this evening or tomorrow.

@iambumblehead I will approve after few small fixes )
And yes, import.meta.resolve returns all paths:

changes are published and deployed https://github.com/iambumblehead/esmock/releases/tag/v2.0.7
feel free to re-open if there is any issue :)


increase macos default disk size

There is not enough free disk space (17G vs required 21G) to install Command Line Tools, which are often required by development tools.
This PR increases the default macos disk size from 50Gb to 100Gb.

That is not how image builders generally work. The goal of the makeDarwinImage is to make as small an image as possible, which can later be extended. You can already increase the disk size yourself manually, by copying the base image to a local directory and then running all of the operations (qemu-img resize, and expansion in the guest). To do this declaratively is already in the TODO https://github.com/MatthewCroughan/NixThePlanet?tab=readme-ov-file#todo, but I've been looking for funding to help me move towards this.
The way it would work is that makeDarwinImage would produce two derivations:

The original 50GB disk image
A disk image of declarative size

The second derivation would be constructed by expanding the qemu qcow2 of the original image, booting the machine in qemu, then using SSH to expand the macOS machine from inside, and then taking another snapshot. This means you don't have to wait another hour to increase the disk size like you've suggested in this PR, and keeps the original base image small.


Fixed barometric sensor readings

Used current latest version of TI's Android source code to write this patch

Mistakenly did not isolate the barometer fix to the CC2650 file. Fixed in second commit.

@piekstra thanks, I've just merged #40 which has a similar fix.


Update layouts that use pf-m-gutter to use md spacer on mobile

The gutter spacing size should match the general padding we apply to the page section where we use $pf-global--spacer--md up to md and $pf-global--spacer--lg greater than md.

:tada: This issue has been resolved in version 2.6.16 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Migrate the qenvs image to a migrated version of the image under redhat-developer

Is your enhancement related to a problem? Please describe
Qenvs image that we use to crate a windows azure agents (quay.io/rhqp/qenvs:v0.6.3) in the windows e2e workflow was moved under official repository.
Describe the solution you'd like
Switch the image and use the actual version. Same change was done in e2e repo: https://github.com/containers/podman-desktop-e2e/pull/212
Describe alternatives you've considered
No response
Additional context
No response

AI LAb nightly windows https://github.com/containers/podman-desktop-extension-ai-lab/pull/1859


Add an integration test with the Swagger endpoint disabled

This adds a flag to the test fixture to toggle whether the Swagger
endpoint is active, which allows tests to be written with it on or off.
Still to do: find a way to toggle it on each test run.  Ideally, we
would have a single Theory test which would take as inputs whether the
Swagger endpoint is active, and the corresponding expected output.
Currently the tests have to be separate because the server is started
during Fixture initialization, which is before the test method receives
control.

Yes, I'd like to see that at some point - namely, we have 3 endpoint readers implemented, it'd be nice to be able to target each of them with the "live" endpoint.  But for now I want to get the basics in so we can have some level of test authoring.
I'd also prefer to split these out differently once we sort out integration vs. unit tests.  E.g. these should be ChangeDirectory tests instead of Swagger/NonSwagger tests, but I didn't want to confuse them with the "unit"-like tests currently in this project.


Hi, not an issue, just a question!

Love what you've done with this port. I've user Phaser2 for a few games, but this is my first attempt with Phaser 3, so thought I'd use this repo as a guide.
I've tried creating a new style sheet with alternative characters on it using TexturePacker.
The issue I'm having is when using a smart folder, the exported filenames in the JSON have the files/structure/ as part of the filename. What are your texture packer settings? and how can I stop this happening?

@adstyles as far as I know there is an option in TexturePacker for trimming file extensions (Advansed settings -> Trim sprite names checkbox). But I don't know about setting for removing file paths
So basically if  you want to use flat in-game file structure (like in this repo) you need to use flat file structure in TexturePacker.
Or you can write a simple nodejs/python/whatever script that will read generated json file and remove prepended filepaths.
Also this is fine to use filenames with paths and extensions inside phaser 'cause it's only a 'title' for adressing sprites in your code
Have a look at this tutorial. Also there is a github repo link  at the end of it with examples of using sprites with filepaths and extensions

@Autapomorph this is great, thank you!


User registration

no reason for a full api point for this, we can just make it a standard from, if you need backend support just give us a shout


Android 11: FormOperationErrorCode.FORM_COULD_NOT_BE_OPEN

Hi all,
Since Android 11 upgrade on my Samsung s10e, I can't seem to use these any more:
ContactsService.openContactForm()
ContactsService..openDeviceContactPicker()

same on simulators. Android 10 and below are fine.
Thanks.

@ghenry let's move this discussion to #197


When user turn on peer via CC management could not start.

Steps to reproduce:
Create peer.
Turn it off and turn it back on via CC.
Reload peer also did not help.
Result:
NAME        STATE    IP    Interface
----        -----    --    ---------
management    STOPPED        eth0```

@kurmanbekova6 with running management when you reload vagrant or reboot peer, is it the same?

WIll be handled by https://github.com/subutai-io/agent/issues/869


Needed disambiguation for pawns even if not necessary

I have noticed that pawn capture moves are only taken if I include disambigurations. Here is the test code to reproduce it:
// <reference path='chess.js.d.ts' />
import { Chess } from 'chess.js'
describe("Show failing tests for chess.js", () => {
it ("when needing disambiguration for pawn moves not working", () => {
    var chess = new Chess()
    chess.move("e4")
    chess.move("d5")
    chess.move("xd5")
    console.log(chess.ascii())
})
it ("when needing disambiguration for pawn moves working", () => {
    var chess = new Chess()
    chess.move("e4")
    chess.move("d5")
    chess.move("exd5")
    console.log(chess.ascii())
})
})

The result when running that test case is the following:
    Started
   +------------------------+
 8 | r  n  b  q  k  b  n  r |
 7 | p  p  p  .  p  p  p  p |
 6 | .  .  .  .  .  .  .  . |
 5 | .  .  .  p  .  .  .  . |
 4 | .  .  .  .        P  P  P |
 1 | R  N  B  Q  K  B  N  R |
   +------------------------+
     a  b  c  d  e  f  g  h

.

2 specs, 0 failures
Finished in 0.029 seconds

As you can see, only in the second case the pawn move is done. It did not work with the valid notation "xd5".

Reading the specification again (http://www.saremba.de/chessgml/standards/pgn/pgn-complete.htm#c8.2.3), I have found my fault:

<IP_ADDRESS> Basic SAN construction: ... Capture moves are denoted by the lower case letter "x" immediately prior to the destination square; pawn captures include the file letter of the originating square of the capturing pawn immediately prior to the "x" character.

So in strict mode, it is ok to want the file letter of the originating square prior to the "x" character.
However, it would be nice if the SLOPPY mode would allow the more lax notation. I will check that.

Not interested any more, after 4 years ticket is then closed.


cloned existing project a windows machine - tests hang (both from CI and vitest extension)

Describe the bug
[INFO 8:44:06 PM] Trying to get vitest version from e:\Projects\denarius\node_modules\.bin\vitest.cmd -v...

System Info
System:
    OS: Windows 10 10.0.22621
    CPU: (32) x64 AMD Ryzen 9 7950X3D 16-Core Processor
    Memory: 36.71 GB / 63.14 GB
  Binaries:
    Node: 18.18.2 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.19 - C:\Program Files\nodejs\yarn.CMD
    npm: 9.8.1 - C:\Program Files\nodejs\npm.CMD
    pnpm: 8.9.2 - C:\Program Files\nodejs\pnpm.CMD
  Browsers:
    Edge: Chromium (118.0.2088.61)
    Internet Explorer: 11.0.22621.1
  npmPackages:
    vite: ^4.5.0 => 4.5.0
    vitest: ^0.34.6 => 0.34.6

### Used Package Manager

npm

### Validations

- [X] Follow our [Code of Conduct](https://github.com/vitest-dev/vitest/blob/main/CODE_OF_CONDUCT.md)
- [X] Read the [Contributing Guidelines](https://github.com/vitest-dev/vitest/blob/main/CONTRIBUTING.md).
- [X] Read the [docs](https://vitest.dev/guide/).
- [X] Check that there isn't [already an issue](https://github.com/vitest-dev/vitest/issues) that reports the same bug to avoid creating a duplicate.
- [X] Check that this is a concrete bug. For Q&A open a [GitHub Discussion](https://github.com/vitest-dev/vitest/discussions) or join our [Discord Chat Server](https://chat.vitest.dev).
- [X] The provided reproduction is a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) of the bug.

I have no idea what is written in "describe the bug"

I will create minimal repro that fials to run vitest on a windows machine in couple of hours. 👍
P.S. Describe the bug is the output of the vitest vscode extension. Note that it doesn't work when running vitest from the package.json scripts neither. 💯

Describe the bug is the output of the vitest vscode extension

Extension has a separate repository: https://github.com/vitest-dev/vscode

As I said it's not only from the extension. Running vitest from package.json scripts just hangs.


Invalid data after some time

I've setup the sensor with a Adafruit Feather HUZZAH (ESP8266) and can read data for a while (1-3 days) then suddenly i only get 65k capacitance and invalid temperatures. The connections are soldered on a prototype board and 10k pull-ups
Power supply is a Anker wall adapter, so i don't think it's an issue.
Here's the relevant code (stripped the network pieces):
#include <ESP8266WiFi.h>
#include <WiFiUDP.h>
#include <I2CSoilMoistureSensor.h>
#include <Wire.h>

int status = WL_IDLE_STATUS;     // the Wifi radio's status
WiFiUDP udp;

I2CSoilMoistureSensor sensor;

void setup() {
  Wire.begin();
  Serial.begin(9600);

  Serial.println("Attempting to connect to WPA network...");
  udp.begin(4097);

  sensor.begin(); // reset sensor
  delay(1000); // give some time to boot up
  Serial.print("I2C Soil Moisture Sensor Address: ");
  Serial.println(sensor.getAddress(),HEX);
  Serial.print("Sensor Firmware version: ");
  Serial.println(sensor.getVersion(),HEX);
  Serial.println();
}

void loop() {
  while (sensor.isBusy()) delay(1000); // available since FW 2.3

  int capacitance = sensor.getCapacitance();
  float temperature = sensor.getTemperature()/(float)10;

  sensor.sleep(); // available since FW 2.3
  udp.beginPacket({192, 168, 2, 48}, 8089);

  Serial.print("Soil Moisture Capacitance: ");
  Serial.print(capacitance); //read capacitance register
  Serial.print(", Temperature: ");
  Serial.println(temperature); //temperature register

  udp.print(chirpLine);
  udp.endPacket();

  delay(10 * 1000);
}

Any ideas what might cause this? Currently testing a version without the sensor.sleep(), because i haven't found any statements regarding wakeup.

Hi,
Probably it's a combination of long cable and esp8266 side treating clock stretching poorly. Have a look in this thread where we were debugging something similar to this:
https://github.com/Apollon77/I2CSoilMoistureSensor/issues/8

Haven't seen Apollon77/I2CSoilMoistureSensor#8 as relevant in my case, as i only got the issue after some time. Got the rugged version too, so cable length wouldn't be my fault ;) It's currently mitigated by not using sensor.sleep(), but maybe i'll move away from the esp8266 too and move to some other low power solution. Without the sleep it's running now for 5 days and i'll further look into this once it's happening again.


Show overlay box when in hot region

I think it would be a great feature if you could have it overlay a translucent box around the area where the window will snap into. This will give a visual cue to the user that they have placed their cursor in the right place and that when they release it will snap into the shown region.
This should probably use the GTK theme defined selected item colour to fit with the end users theme.

It'll be a long while.


feat: use latest devtools styles

They have changed to use new dynamic themes colors. Assuming default one for simplicity.

#515  👈
main

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

Join @davidlj95 and the rest of your teammates on  Graphite


Option query silently overrides url query

Given
I have a function like this:
protected function getPage($url, $query = []){
    // `$this->client` is `\GuzzleHttp\Client` instance.
    return $this->client->get($url, [
        'query' => $query,
    ])->getBody()->getContents();
}

I call it: $this->getPage('image?event=2');
Expectation
I expect the request url to be http://my-site.com/image?event=2.
Reality
Request url is http://my-site.com/image.
Details
What, happens is, when you provide 'query' in options, it will silently override query from url. If query is not provided, query from url will be used.
As guzzle/php doesn't provide means to easily see/debug resulting url, this little thing might result in nice hourly debug session.
Possible solutions

Merge query from url and query.
Throw exception when both are provided.
Trigger notice when both are provided.

Thanks for your attention.

This behavior is by design. Instead of using a default query request option, you need a middleware that will add to the query string rather than replace it, and the middleware needs context as to how the query string is serialized.

Thanks.
Understood. Can't say it doesn't make sense.
I'll split method signature on my side:
// from
getPage($url, $query = []);
// to
getPageWithQuery($url, $query);
getPage($url, $query);

This should quell any kind of confusion.


Added strayer folder to edu directory

Attempting to add Strayer University to the list of student email addresses.

@JoshDrentlaw Thank you for your patience while waiting for a review and processing your request. Pull request merged. Please start applying for JetBrains educational subscription at https://www.jetbrains.com/shop/eform/students in an hour, to allow the changes to propagate through JetBrains systems.


seed objects 24-January

This PR:

seeds an additional cluster for testing.  These contents will more than likely need to be amended in future PRs, but seeding something now to get started.

This PR:

seeds an additional cluster for testing.  These contents will more than likely need to be amended in future PRs, but seeding something now to get started.

Fixed yaml


Error writing request body to server, server ClickHouseNode

We are trying to load data into ReplicatedMergeTree table in clickhouse via spark from Google Dataproc Cluster. However, we are getting intermittent Error while inserting data using jdbc driver: 0.46 shaded
Clickhouse version: <IP_ADDRESS>
spark version: 2.4.8

Error shown below(sensitive data is hidden)  :
[Stage 4:=========>                                             (24 + 15) / 136]23/08/02 13:08:51 WARN
org.apache.spark.scheduler.TaskSetManager: Lost task 24.0 in stage 4.0 (TID 5320, dataproc_cluster, executor 15): java.sql.BatchUpdateException: Error writing request body to server, server ClickHouseNode [uri=http://dummyclickhouseserver:8123/default, options={async_insert=1,wait_for_async_insert=1}]@668945829
        at com.clickhouse.jdbc.SqlExceptionUtils.batchUpdateError(SqlExceptionUtils.java:107)
        at com.clickhouse.jdbc.internal.InputBasedPreparedStatement.executeAny(InputBasedPreparedStatement.java:154)
        at com.clickhouse.jdbc.internal.AbstractPreparedStatement.executeLargeBatch(AbstractPreparedStatement.java:85)
        at com.clickhouse.jdbc.internal.ClickHouseStatementImpl.executeBatch(ClickHouseStatementImpl.java:754)
        at org.apache.spark.sql.execution.datasources.jdbc.JdbcUtils$.savePartition(JdbcUtils.scala:671)
        at org.apache.spark.sql.execution.datasources.jdbc.JdbcUtils$.$anonfun$saveTable$1(JdbcUtils.scala:840)
        at org.apache.spark.sql.execution.datasources.jdbc.JdbcUtils$.$anonfun$saveTable$1$adapted(JdbcUtils.scala:838)
        at org.apache.spark.rdd.RDD.$anonfun$foreachPartition$2(RDD.scala:980)
        at org.apache.spark.rdd.RDD.$anonfun$foreachPartition$2$adapted(RDD.scala:980)
        at org.apache.spark.SparkContext.$anonfun$runJob$5(SparkContext.scala:2116)
        at org.apache.spark.scheduler.ResultTask.runTask(ResultTask.scala:90)
        at org.apache.spark.scheduler.Task.run(Task.scala:123)
        at org.apache.spark.executor.Executor$TaskRunner.$anonfun$run$3(Executor.scala:414)
        at org.apache.spark.util.Utils$.tryWithSafeFinally(Utils.scala:1360)
        at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:417)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:750)

There are no errors in the clickhouse server logs. When this error occurs, spark tries to retry the failed task which eventually succeeds, thereby resulting in duplicate data. When does this error occur and how can we prevent to avoid duplicate data ?

Hi @ekatabavkar, sorry for the late reply.

There are no errors in the clickhouse server logs.

If we can confirm that the query has no issue, then it's probably just related to the network. You may want check ClickHouse/clickhouse-docs#1178 and see if it will help.

thereby resulting in duplicate data. When does this error occur and how can we prevent to avoid duplicate data ?

@ekatabavkar you should disable async_insert to avoid problems with deduplication. see https://clickhouse.com/docs/en/optimize/asynchronous-inserts

AUTOMATIC DEDUPLICATION IS DISABLED BY DEFAULT WHEN USING ASYNCHRONOUS INSERTS
Manual batching (see section above)) has the advantage that it supports the built-in automatic deduplication of table data if (exactly) the same insert statement is sent multiple times to ClickHouse Cloud, for example, because of an automatic retry in client software because of some temporary network connection issues.


waiting for accepting team request

cc @keybase/y2ksquad

@keybase/react-hackers bump

Did a quick sweep and other places it's used make sense


fix a bug causing an infinite loop when the field settings are validated

@ryanscherler when you have the time, will you also please do a new release of this plugin so that the changes will be installed by composer/craft?
https://docs.craftcms.com/v3/extend/plugin-store.html#plugin-releases

@ryanscherler when you have the time, will you also please do a new release of this plugin so that the changes will be installed by composer/craft?
https://docs.craftcms.com/v3/extend/plugin-store.html#plugin-releases

For sure - I meant to do that yesterday!

New release tagged! https://github.com/eastslopestudio/craft3-sites-field/releases/tag/v1.0.1 🎉


[v1.x] test_gluon_data unit tests failing

Description
On the v1.x pipeline, we are seeing the following test failures consistently:
in tests/python/unittest/test_gluon_data.py:
test_multi_worker_dataloader_release_pool
test_multi_worker_forked_data_loader
Occurrences
https://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Funix-cpu/detail/PR-19872/7/pipeline/293/#step-776-log-1725
https://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Funix-cpu/detail/PR-19872/4/pipeline/296
Test failure logs:
[2021-02-10T01:39:46.205Z] test_gluon_data.test_multi_worker_dataloader_release_pool ... terminate called after throwing an instance of 'dmlc::Error'
[2021-02-10T01:39:46.205Z]   what():  [01:39:41] src/storage/./cpu_shared_storage_manager.h:218: Check failed: count >= 0 (-2 vs. 0) :
[2021-02-10T01:39:46.205Z] Stack trace:
[2021-02-10T01:39:46.205Z]   [bt] (0) /work/mxnet/python/mxnet/../../lib/libmxnet.so(dmlc::LogMessageFatal::~LogMessageFatal()+0x61) [0x7f191fc63b61]
[2021-02-10T01:39:46.205Z]   [bt] (1) /work/mxnet/python/mxnet/../../lib/libmxnet.so(mxnet::storage::CPUSharedStorageManager::FreeImpl(mxnet::Storage::Handle const&)+0xd3) [0x7f192522fdf3]
[2021-02-10T01:39:46.205Z]   [bt] (2) /work/mxnet/python/mxnet/../../lib/libmxnet.so(mxnet::storage::CPUSharedStorageManager::Free(mxnet::Storage::Handle)+0x98) [0x7f1925237348]
[2021-02-10T01:39:46.205Z]   [bt] (3) /work/mxnet/python/mxnet/../../lib/libmxnet.so(mxnet::StorageImpl::Free(mxnet::Storage::Handle)+0x69) [0x7f1925232ce9]
[2021-02-10T01:39:46.205Z]   [bt] (4) /work/mxnet/python/mxnet/../../lib/libmxnet.so(+0x5ade409) [0x7f1924b21409]
[2021-02-10T01:39:46.205Z]   [bt] (5) /work/mxnet/python/mxnet/../../lib/libmxnet.so(+0x61d3c50) [0x7f1925216c50]
[2021-02-10T01:39:46.205Z]   [bt] (6) /work/mxnet/python/mxnet/../../lib/libmxnet.so(mxnet::engine::ThreadedEngine::ExecuteOprBlock(mxnet::RunContext, mxnet::engine::OprBlock*)+0xa50) [0x7f1925210440]
[2021-02-10T01:39:46.205Z]   [bt] (7) /work/mxnet/python/mxnet/../../lib/libmxnet.so(mxnet::engine::ThreadedEnginePerDevice::PushToExecute(mxnet::engine::OprBlock*, bool)+0x349) [0x7f192522c9d9]
[2021-02-10T01:39:46.205Z]   [bt] (8) /work/mxnet/python/mxnet/../../lib/libmxnet.so(mxnet::engine::ThreadedEngine::Push(mxnet::engine::Opr*, mxnet::Context, int, bool)+0x42b) [0x7f1925219f5b]
[2021-02-10T01:39:46.205Z]   [bt] (9) /work/mxnet/python/mxnet/../../lib/libmxnet.so(mxnet::engine::ThreadedEngine::PushAsync(std::function<void (mxnet::RunContext, mxnet::engine::CallbackOnComplete)>, mxnet::Context, std::vector<mxnet::engine::Var*, std::allocator<mxnet::engine::Var*> > const&, std::vector<mxnet::engine::Var*, std::allocator<mxnet::engine::Var*> > const&, mxnet::FnProperty, int, char const*, bool)+0xd8) [0x7f1925216948]
[2021-02-10T01:39:46.461Z] /work/runtime_functions.sh: line 1008:     6 Aborted                 (core dumped) nosetests-3.4 $NOSE_COVERAGE_ARGUMENTS $NOSE_TIMER_ARGUMENTS --with-xunit --xunit-file nosetests_unittest.xml --verbose

[2021-02-09T22:11:59.574Z] ======================================================================
[2021-02-09T22:11:59.574Z] ERROR: test_gluon_data.test_multi_worker_forked_data_loader
[2021-02-09T22:11:59.574Z] ----------------------------------------------------------------------
[2021-02-09T22:11:59.574Z] Traceback (most recent call last):
[2021-02-09T22:11:59.574Z]   File "/usr/local/lib/python3.7/dist-packages/nose/case.py", line 198, in runTest
[2021-02-09T22:11:59.574Z]     self.test(*self.arg)
[2021-02-09T22:11:59.574Z]   File "/work/mxnet/tests/python/unittest/common.py", line 226, in test_new
[2021-02-09T22:11:59.574Z]     mx.nd.waitall()
[2021-02-09T22:11:59.574Z]   File "/work/mxnet/python/mxnet/ndarray/ndarray.py", line 211, in waitall
[2021-02-09T22:11:59.574Z]     check_call(_LIB.MXNDArrayWaitAll())
[2021-02-09T22:11:59.574Z]   File "/work/mxnet/python/mxnet/base.py", line 246, in check_call
[2021-02-09T22:11:59.574Z]     raise get_last_ffi_error()
[2021-02-09T22:11:59.574Z] mxnet.base.MXNetError: Traceback (most recent call last):
[2021-02-09T22:11:59.574Z]   [bt] (9) /work/mxnet/python/mxnet/../../lib/libmxnet.so(mxnet::engine::ThreadedEngine::PushAsync(std::function<void (mxnet::RunContext, mxnet::engine::CallbackOnComplete)>, mxnet::Context, std::vector<mxnet::engine::Var*, std::allocator<mxnet::engine::Var*> > const&, std::vector<mxnet::engine::Var*, std::allocator<mxnet::engine::Var*> > const&, mxnet::FnProperty, int, char const*, bool)+0xd8) [0x7f0df6da1c48]
[2021-02-09T22:11:59.574Z]   [bt] (8) /work/mxnet/python/mxnet/../../lib/libmxnet.so(mxnet::engine::ThreadedEngine::Push(mxnet::engine::Opr*, mxnet::Context, int, bool)+0x42b) [0x7f0df6da525b]
[2021-02-09T22:11:59.574Z]   [bt] (7) /work/mxnet/python/mxnet/../../lib/libmxnet.so(mxnet::engine::ThreadedEnginePerDevice::PushToExecute(mxnet::engine::OprBlock*, bool)+0x349) [0x7f0df6db7e69]
[2021-02-09T22:11:59.574Z]   [bt] (6) /work/mxnet/python/mxnet/../../lib/libmxnet.so(mxnet::engine::ThreadedEngine::ExecuteOprBlock(mxnet::RunContext, mxnet::engine::OprBlock*)+0xa50) [0x7f0df6d9b740]
[2021-02-09T22:11:59.574Z]   [bt] (5) /work/mxnet/python/mxnet/../../lib/libmxnet.so(+0x63dbf50) [0x7f0df6da1f50]
[2021-02-09T22:11:59.574Z]   [bt] (4) /work/mxnet/python/mxnet/../../lib/libmxnet.so(+0x5cde545) [0x7f0df66a4545]
[2021-02-09T22:11:59.574Z]   [bt] (3) /work/mxnet/python/mxnet/../../lib/libmxnet.so(mxnet::StorageImpl::Free(mxnet::Storage::Handle)+0x69) [0x7f0df6dbe0b9]
[2021-02-09T22:11:59.574Z]   [bt] (2) /work/mxnet/python/mxnet/../../lib/libmxnet.so(mxnet::storage::CPUSharedStorageManager::Free(mxnet::Storage::Handle)+0x98) [0x7f0df6dc2718]
[2021-02-09T22:11:59.574Z]   [bt] (1) /work/mxnet/python/mxnet/../../lib/libmxnet.so(mxnet::storage::CPUSharedStorageManager::FreeImpl(mxnet::Storage::Handle const&)+0xcf) [0x7f0df6dbb27f]
[2021-02-09T22:11:59.574Z]   [bt] (0) /work/mxnet/python/mxnet/../../lib/libmxnet.so(dmlc::LogMessageFatal::~LogMessageFatal()+0x61) [0x7f0df16c59e1]
[2021-02-09T22:11:59.574Z]   File "src/storage/./cpu_shared_storage_manager.h", line 218
[2021-02-09T22:11:59.574Z] MXNetError: Check failed: count >= 0 (-1 vs. 0) :

Since we're trying to unblock the v1.x CI pipeline, I am disabling these 2 tests for now in https://github.com/apache/incubator-mxnet/pull/19872.

this PR made changes to gluon data loader #19748 . But the issue is not reproducible on local machine though. CI is unblocked for now. This requires further investigation for root cause

Raised PR #19879 to revert #19748 and re-enable gluon data loader tests to see if test failure is caused by the PR or not. Unable to repro failure on local instance using master w/o skipping tests.

Getting another test failure, looks related to gluon data loader stuff. We really need to dig down and root cause this issue.
[2021-02-11T06:56:52.649Z] test_gluon_data.test_list_dataset ... terminate called after throwing an instance of 'dmlc::Error'
[2021-02-11T06:56:52.649Z]   what():  [06:56:48] /work/mxnet/src/storage/./cpu_shared_storage_manager.h:218: Check failed: count >= 0 (-1 vs. 0) :
[2021-02-11T06:56:52.649Z] Stack trace:
[2021-02-11T06:56:52.649Z]   [bt] (0) /work/mxnet/python/mxnet/../../build/libmxnet.so(dmlc::LogMessageFatal::~LogMessageFatal()+0x61) [0x7f882bad4491]
[2021-02-11T06:56:52.649Z]   [bt] (1) /work/mxnet/python/mxnet/../../build/libmxnet.so(mxnet::storage::CPUSharedStorageManager::FreeImpl(mxnet::Storage::Handle const&)+0xd3) [0x7f882e523ea3]
[2021-02-11T06:56:52.649Z]   [bt] (2) /work/mxnet/python/mxnet/../../build/libmxnet.so(mxnet::storage::CPUSharedStorageManager::Free(mxnet::Storage::Handle)+0x98) [0x7f882e527c08]
[2021-02-11T06:56:52.649Z]   [bt] (3) /work/mxnet/python/mxnet/../../build/libmxnet.so(mxnet::StorageImpl::Free(mxnet::Storage::Handle)+0x69) [0x7f882e526d39]
[2021-02-11T06:56:52.649Z]   [bt] (4) /work/mxnet/python/mxnet/../../build/libmxnet.so(+0xc747fa) [0x7f882bdc47fa]
[2021-02-11T06:56:52.649Z]   [bt] (5) /work/mxnet/python/mxnet/../../build/libmxnet.so(+0xac46bf) [0x7f882bc146bf]
[2021-02-11T06:56:52.649Z]   [bt] (6) /work/mxnet/python/mxnet/../../build/libmxnet.so(mxnet::engine::ThreadedEngine::ExecuteOprBlock(mxnet::RunContext, mxnet::engine::OprBlock*)+0x5c4) [0x7f882bc20234]
[2021-02-11T06:56:52.649Z]   [bt] (7) /work/mxnet/python/mxnet/../../build/libmxnet.so(mxnet::engine::ThreadedEnginePerDevice::PushToExecute(mxnet::engine::OprBlock*, bool)+0x33e) [0x7f882bc2694e]
[2021-02-11T06:56:52.649Z]   [bt] (8) /work/mxnet/python/mxnet/../../build/libmxnet.so(mxnet::engine::ThreadedEngine::Push(mxnet::engine::Opr*, mxnet::Context, int, bool)+0x190) [0x7f882bc16ba0]
[2021-02-11T06:56:52.649Z]   [bt] (9) /work/mxnet/python/mxnet/../../build/libmxnet.so(mxnet::engine::ThreadedEngine::PushAsync(std::function<void (mxnet::RunContext, mxnet::engine::CallbackOnComplete)>, mxnet::Context, std::vector<mxnet::engine::Var*, std::allocator<mxnet::engine::Var*> > const&, std::vector<mxnet::engine::Var*, std::allocator<mxnet::engine::Var*> > const&, mxnet::FnProperty, int, char const*, bool)+0xd7) [0x7f882bc143b7]
[2021-02-11T06:56:52.649Z]
[2021-02-11T06:56:52.649Z]
[2021-02-11T06:56:52.649Z] /work/runtime_functions.sh: line 1008:     6 Aborted                 (core dumped) nosetests-3.4 $NOSE_COVERAGE_ARGUMENTS $NOSE_TIMER_ARGUMENTS --with-xunit --xunit-file nosetests_unittest.xml --verbose

I don't think it's related, but I create https://github.com/apache/incubator-mxnet/pull/19886 to test if upgrading python (from 3.6 to 3.7) caused these unit test failures.

See my comment in the other issue about this: https://github.com/apache/incubator-mxnet/issues/19918#issuecomment-781832648

Thanks @ptrendx for the fix! Closing this issue.