Request for new GO terms

Hello,
Would it be possible to create the following GO terms:

Regulation term (positive and negative) for GO:0045138 (nematode male tail tip morphogenesis), PMID:28068334
A GO term for "pharynx morphogenesis" and its associated regulatory terms (positive and negative), PMID:20805556.
Thank you
Rossana

Hi @rozaru
I can add these terms, but am wondering if the activities of the genes described in this paper regulate the actual morphogenetic processes or if they regulate the activities of members of the BMP signaling pathway that, in turn, regulates the morphogenetic processes?  What do you think?

@dosumis - I was going to add the pharynx morphogenesis term as part_of pharynx development (GO:0060465).
I noticed, however, that the logical def of pharynx development is:
'anatomical structure development'
and ('results in development of' some 'chordate pharynx')
There are a large number of C. elegans gene products annotated to 'pharynx development', though, so would it be okay to make the logical def more general by changing 'chordate pharynx' to the parent 'pharynx' term?
Thx.

I think this is logically valid.
It is somewhat unsatisfying though. The uberon grouping 'pharynx' is not a well defined grouping. The definition comes from GO "the part of the digestive system immediately posterior to the mouth" (terminating where?)
Related:
https://github.com/obophenotype/uberon/issues/1212
This is really cool:
https://github.com/BgeeDB/anatomical-similarity-annotations/issues/18

I think this is logically valid.

Me too.  Perhaps a loose grouping is all we can manage here.  Wondering if this can be tightened up by specifying ectodermal origin?  Works for chordates (pharyngeal arches/neural crest) and arthropods (foregut is ectdoermal).  Don't know about worms though.

Okay, I will update the logical def here to use the more general 'pharynx' term.
In C. elegans, the pharynx contains cells of both ectodermal and mesodermal origin, though, so we can't tighten up by specifying ectodermal origin.
http://www.wormatlas.org/hermaphrodite/pharynx/mainframe.htm


feat: ✨ drop-down

Description
The drop-down is needed for the header. It is used  as a menu if a header icon is clicked.
Acceptance criteria

[ ] All DoD items successfully completed
[ ] Incorporates slots, Events, Methods, Parts from Shoelace
[ ] Tested: Playwright + Chromatic
[ ] create a proper documentation which contains at least everything from the Shoelace component
[ ] Text in the documentation can be synced

design: https://github.com/synergy-design-system/design/issues/25


504 Gateway Time-out error in nginx due to errors in iptable rules

I am getting 504 Gateaway Time-out errors from nginx after deploying an app in dokku, and I've narrowed it down to a problem in iptables. I vaguely remember having similar problems before, which eventually disappeared, but just now I updated dokku and now I am having this problem again.
I am unsure whether this is a problem of dokku, or of docker.
After deploying the app (with the redis plugin enabled for the app), I get the following (redacted) iptables:
# Generated by iptables-save v1.4.21 on Thu Sep 10 20:21:47 2015
*nat
:PREROUTING ACCEPT [156:10009]
:INPUT ACCEPT [15:864]
:OUTPUT ACCEPT [67:4660]
:POSTROUTING ACCEPT [70:4840]
:DOCKER - [0:0]
-A PREROUTING -m addrtype --dst-type LOCAL -j DOCKER
-A OUTPUT ! -d <IP_ADDRESS>/8 -m addrtype --dst-type LOCAL -j DOCKER
-A POSTROUTING -s <IP_ADDRESS>/16 ! -o docker0 -j MASQUERADE
COMMIT
# Completed on Thu Sep 10 20:21:47 2015
# Generated by iptables-save v1.4.21 on Thu Sep 10 20:21:47 2015
*filter
:INPUT DROP [18:1384]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [500:99688]
:DOCKER - [0:0]
... some rules related to ssh ...
-A INPUT -p icmp -m icmp --icmp-type 8 -m state --state NEW,RELATED,ESTABLISHED -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -i eth0 -m state --state RELATED,ESTABLISHED -j ACCEPT
-A INPUT -p tcp -m tcp --dport 443 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 80 -j ACCEPT
-A FORWARD -o docker0 -j DOCKER
-A FORWARD -o docker0 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A FORWARD -i docker0 ! -o docker0 -j ACCEPT
-A FORWARD -i docker0 -o docker0 -j ACCEPT
-A DOCKER -s <IP_ADDRESS>/32 -d <IP_ADDRESS>/32 -i docker0 -o docker0 -p tcp -m tcp --dport 6379 -j ACCEPT
-A DOCKER -s <IP_ADDRESS>/32 -d <IP_ADDRESS>/32 -i docker0 -o docker0 -p tcp -m tcp --sport 6379 -j ACCEPT
COMMIT
# Completed on Thu Sep 10 20:21:47 2015

You can see the rules presumably generated by the redis plugin, but there is no rule to allow access to port 5000 of the app container (IP <IP_ADDRESS>). It seems that some rule like -A INPUT -i docker0 -j ACCEPTis missing (although I am not an expert in iptables).
Anybody experienced similar problems and knows where this problem is coming from, and why it is showing up?

I've never seen this issue, @michaelshobbs have you?
@rssc were you able to figure out any more details? Maybe include deploy output with dokku trace on?

nope. please provide the information requested here and we'll see if we can help: https://github.com/progrium/dokku/blob/master/CONTRIBUTING.md#reporting-other-issues

Description of problem: Dokku app is unreachable for nginx after deployment due to incorrect iptables configuration.
Output of the following commands

dokku version: v0.3.26-128-g1b5756c

dokku plugins:
/var/lib/dokku/plugins/00_dokku-standard/
/var/lib/dokku/plugins/20_events/
/var/lib/dokku/plugins/apps/
/var/lib/dokku/plugins/backup/
/var/lib/dokku/plugins/build-env/
/var/lib/dokku/plugins/certs/
/var/lib/dokku/plugins/checks/
/var/lib/dokku/plugins/common/
/var/lib/dokku/plugins/config/
/var/lib/dokku/plugins/debug/
/var/lib/dokku/plugins/docker-options/
/var/lib/dokku/plugins/dokku-name/
/var/lib/dokku/plugins/dokku-shoreman/
/var/lib/dokku/plugins/domains/
/var/lib/dokku/plugins/enter/
/var/lib/dokku/plugins/git/
/var/lib/dokku/plugins/link/
/var/lib/dokku/plugins/maintenance/
/var/lib/dokku/plugins/nginx-vhosts/
/var/lib/dokku/plugins/ps/
/var/lib/dokku/plugins/psql-sc/
/var/lib/dokku/plugins/rebuild/
/var/lib/dokku/plugins/redis/
/var/lib/dokku/plugins/shell/
/var/lib/dokku/plugins/tags/
/var/lib/dokku/plugins/tar/

docker version:
Client version: 1.6.2
Client API version: 1.18
Go version (client): go1.4.2
Git commit (client): 7c8fca2
OS/Arch (client): linux/amd64
Server version: 1.6.2
Server API version: 1.18
Go version (server): go1.4.2
Git commit (server): 7c8fca2
OS/Arch (server): linux/amd64

docker info:
Containers: 12
Images: 77
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 103
Dirperm1 Supported: false
Execution Driver: native-0.2
Kernel Version: 3.13.0-43-generic
Operating System: Ubuntu 14.04.3 LTS
CPUs: 1
Total Memory: 490 MiB
Name: xxx.yyy.zz
ID: BP4G:KONK:ZIKJ:R72B:QGJ2:JBCP:WKI2:HPPW:X44B:CW6F:IUTN:BRV6
WARNING: No swap limit support

uname -a:
Linux xxx.yyy.zz 3.13.0-43-generic #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

cat /home/dokku/<app>/nginx.conf (if applicable): no changes to default

Output of failing dokku commands with dokku trace on: command does not fail

Environment details (AWS, VirtualBox, physical, etc.): DigitalOcean VPS
How was dokku installed?: from source (I thought I had upgraded it to the package, but I can't see it in "dpkg -l")
Steps to Reproduce: Deploy or rebuild app. App starts up correctly, but is inaccessible through nginx, as iptables does not allow access to the docker container hosting the app. Manually adding rule "iptables -A INPUT -i docker0 -j ACCEPT" fixes the problem.
Additional info: Deploying the app with dokku trace on does not give any hint of any problem, although I have no idea what I would be looking for. It certainly does not mention anything about iptables. So I would assume docker is responsible for updating iptables?
If you could let me know what I would be looking for in the trace I can provide more information.

Thank you for doing that. To be frank, I have not seen the iptables issue specifically. So we're going to need to gather some more info here to rule out other causes.
Please include a gist of the following

output of a deployment with dokku trace on
the contents of your app's nginx config (after that deployment)
the output of ps -ef | grep nginx (after that deployment)

I have seen nginx not reload cleanly and want to make that's the case here.

@rssc any luck with the requests by @michaelshobbs ?

Sorry for the delay in getting back on this. Please find the requested information below.
Gist of deployment with dokku trace on:
https://gist.github.com/anonymous/2e57f45c9232071f2499
Gist of app's nginx config file:
https://gist.github.com/rssc/0328343cddb81da693d6
Output of ps -ef | grep nginx:
root       778     1  0 Sep10 ?        00:00:00 nginx: master process /usr/sbin/nginx -g daemon on; master_process on;
root     16272 14187  0 22:34 pts/0    00:00:00 grep --color=auto nginx
www-data 30467   778  0 Sep15 ?        00:00:00 nginx: worker process

Note: I replaced the actual domain with "xyz" in the gists.

@rssc thanks for putting the info together. that definitely rules out my hope for a simple resolution. as i cannot reproduce the issue, i'm not sure where to go from here.
out of curiosity, can you start up a standard docker container with a listener of some sort and access that? i'm wondering if maybe there is a docker setting we're not seeing here.

@rssc bump

bump

Right. I am not entirely sure what exactly I am supposed to test, but here is what I found:
When I start a new container using the command line docker run -ti -p 8888:5000 ubuntu bash and start a netcat instance with nc -l 5000, then I can only connect to it (using telnet <IP_ADDRESS> 8888 on the host) if I have the iptables rule that allows traffic on the docker interface (i.e., iptables -A INPUT -i docker0 -j ACCEPT). Likewise, if I check the IP address within the docker container (something in the range of 172.17.x.x), then I can only ping it from the host if that rule exists.
My understanding is that if the default policy of the INPUT chain in iptables is DROP, then unless the rule allowing traffic on the docker0 interface is there, no traffic will be going to any docker container. So I suppose the question is whether docker should add that rule (maybe it did, and I inadvertently removed it before?), or whether that is something that the administrator should add at some point.
I just checked docker running on my local machine, and there isn't any explicit rule allowing traffic on the docker0 interface in the INPUT chain, but my default policy locally is ACCEPT, so it's not an issue. As soon as I would change that to DROP, I presume I would have exactly the same problem on my local machine. So in the end this is rather an issue with docker?
In any case, thanks for your help so far.

How are you managing this instance? Is it a custom installation where you are perhaps changing iptables config automatically via something like chef or puppet?

The server in question doesn't use anything like chef or puppet, it's the DigitalOcean dokku image. The only thing that might interfere with iptables is the iptables-persistent package.

Can you try another dokku instance without that package installed and see if you can replicate it? I think docker is meant to handle iptables on it's own. Might be worth seeing what the docker folks say as well...

bump


Fix a bug using encodeInto truncating strings

The last write accidentally wasn't accounted for in the returned length
of the string and we unfortunately don't have any test coverage of
encodeInto since it requires Firefox nightly right now (and doesn't
work in Node yet).
Closes #1436

(facepalm) sorry! I thought it was covered...

I'm realizing now we do actually have coverage of this nowadays, I think we just historically didn't! Yesterday I was confused that tests failed on the release PR and was going to investigate more today, but I realized today that encodeInto is in stable Firefox and the test failures look like this bug, so I think the recent release of Firefox 66 broke our CI and gave us coverage :)


Create New Release for NPM

Please. 😄
Just want fixes for #4 and #6 to be available. Thanks!  🍻

Sorry, just realized that v0.0.5 was put on NPM an hour ago, but I just don't see it in this repo. Thanks 👍


Tesseract giving series of errors

from PIL import Image
import pytesseract
tesseract_cmd = 'C:\\Program Files (x86)\\Tesseract-OCR\\tesseract'
im = Image.open("jumbled.jpg")
text = pytesseract.image_to_string(im, lang = 'eng')
print(text)

I am trying to use tesseract for character recognition on an image (attached below)

but I am getting the following errors in command line, I am new to python and OCR, please help.
C:\Users\aryan\Documents\Computer\Programming\Atom Test>python HQSolver.py
Traceback (most recent call last):
  File "HQSolver.py", line 6, in <module>
    text = pytesseract.image_to_string(im, lang = 'eng')
  File "C:\Users\aryan\AppData\Local\Programs\Python\Python36-32\lib\site-packages\pytesseract\pytesseract.py", line 193, in image_to_string
    return run_and_get_output(image, 'txt', lang, config, nice)
  File "C:\Users\aryan\AppData\Local\Programs\Python\Python36-32\lib\site-packages\pytesseract\pytesseract.py", line 140, in run_and_get_output
    run_tesseract(**kwargs)
  File "C:\Users\aryan\AppData\Local\Programs\Python\Python36-32\lib\site-packages\pytesseract\pytesseract.py", line 111, in run_tesseract
    proc = subprocess.Popen(command, stderr=subprocess.PIPE)
  File "C:\Users\aryan\AppData\Local\Programs\Python\Python36-32\lib\subprocess.py", line 709, in __init__
    restore_signals, start_new_session)
  File "C:\Users\aryan\AppData\Local\Programs\Python\Python36-32\lib\subprocess.py", line 997, in _execute_child
    startupinfo)
FileNotFoundError: [WinError 2] The system cannot find the file specified

I already tried to change the pytesseract.py from
tesseract_cmd = 'tesseract'
to
tesseract_cmd = '/usr/local/bin/tesseract'

We do not provide support for 3rd party (python wrapper) project. Please contact its author or use tesseract user forum.

nic


3.5 Gb network traffic for 30 days

Microsoft PowerToys version
"0.35.0"
Running as admin

[X] Yes

Area(s) with issue?
ColorPicker, FancyZones
Steps to reproduce
EXTREMELY NETWORK TRAFFIC

Hi, for 30 days this app use 3.5 Gb network traffic, what happiness?
✔ Expected Behavior
No response
❌ Actual Behavior
for 30 days this app use 3.5 Gb network traffic
Other Software
No response

cc: @yuyoyuppe

cc: @yuyoyuppe Maybe the updater?

but not 3.5 Gb per month))

@iBelow, I know, we'll need to investigate this. Could you attach a full bug report file?
Right-click on the tray icon and click Report Bug. Then drag-and-drop the generated file into the GitHub comment to upload it. Thanks!

Sure!
PowerToysReport_2021-11-11-12-02-33.zip

Might be related to an older version of the code.
You're running 0.35.0 while the newest version is 0.49.1.
Would you mind updating to the latest version and verify if the behavior keeps happening?

@jaimecbernardo is correct, we've improved the autoupdate mechanism since then, please try the newest version and see if you experience any issues.

Let's close it for now. Please open it again if the issue still occurs.


Add location filters to search dashboard

This has now been added.
https://reporting.wellcomecollection.org/s/search/app/dashboards#/view/bc389f10-0262-11eb-a00d-fb76dba0bb01?_g=(filters:!(),refreshInterval:(pause:!t,value:0),time:(from:now-5M,to:now))&_a=(description:'2020-09-29%0AAn%20overview%20of%20how%20search%20is%20performing',filters:!(),fullScreenMode:!f,options:(hidePanelTitles:!f,useMargins:!t),query:(language:kuery,query:''),timeRestore:!t,title:Search,viewMode:view)


Could not update annotations. Error: "rotation" is expected to be "number", but "object" has been got."

My actions before raising this issue

[ ] drag the bbox to the next position
[ ] change it's action labels

Expected Behaviour
the bboxes should move and track to the next position
Current Behaviour
it stays in the last position
Possible Solution

Steps to Reproduce (for bugs)

Create an annotation project, with only one label, add several attributes (checkbox, False, Mutable)
Add a new task, link to a video with normal resolution, in the , <frame_step> set as the fps of the video, others remain default
Open the task and start annotation, try to change the position and labels of all bboxes as possible
Go and annotate the video frame by frame
At some frames during annotation, you will encounter such situation: you drag one target bbox to it's expected new position and change it's action labels, press F, it dramatically shift back to it's original position, and when you mark it as a keyframe, it pop up the error "Could not update annotations
Error: "rotation" is expected to be "number", but "object" has been got."

Context
It memory serve correctly, when using a previous CVAT version in last summer, I did not have such a problem. I update the repo these days and now this problem accidentally but frequently happens in my annotation, severely slowdown the dataset preparing work.
Your Environment

Docker version : 19.03.14/20.10.6-ce
Are you using Docker Swarm or Kubernetes? No
Operating System and version (e.g. Linux, Windows, MacOS): linux/amd64, openSUSE Leap 15.2
Code example or link to GitHub repo or gist to reproduce problem: the latest commit of this repo

I believe we fixed that, but could not find the PR.
Please, try the newest version.


The app crash when using generic class.

Fist of all thanks for such impressive framework.
The framework works fine and convert json object to model into simulator only using generic class  pattern. But the same time if i am going to run the application on actual device it will crash on below line.
`let contentString = try NSString(contentsOfFile: resourceDBFolderPath!, encoding: NSUTF8StringEncoding)
print(contentString)
let anyObj: AnyObject? =  try NSJSONSerialization.JSONObjectWithData(contentString.dataUsingEncoding(NSUTF8StringEncoding)! , options: NSJSONReadingOptions(rawValue: 0))
if NSJSONSerialization.isValidJSONObject(anyObj!)
{
           // let rootObject:RootApp =  Mapper<RootApp<Template>>().map(anyObj)!

//
let result = Mapper<Result
So could you please check it and i have create same generic class as mention so could please let me know is there any other way to use it for both debug and release version

I'm not sure what is causing your specific crash but in this code snippet there are many unsafe ! operations.
I do not have any issues with generics when running on my device at the moment. I am closing this until further response.


Choosing all packages to bump also includes ignored packages and results in error during version phase

Affected Packages

not sure, guess cli

Problem
I tried to create a changeset using yarn chageset. I needed to bump all packages in your monorepo. So I choose all changes package and all unchanged packages. It results in adding ignored packages (defined in ignore in the config files) to the list of changes.
When trying to run yarn changesets version command, it now thrown an errors:
Mixed changesets that contain both ignored and not ignored packages are not allowed

Proposed solution
Remove ignored packages from the selection list in yarn changeset command? 🤔

Good suggestion - we probably should filter out any dependants of ignored packages as IIRC we don't allow them to be published because it would possibly result in a broken release.


feature(Back): Expenses category in dto

Codecov Report

Merging #56 (b4a9fcb) into main (dbe7a0e) will decrease coverage by 0.17%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##               main      #56      +/-   ##
============================================
- Coverage     44.70%   44.53%   -0.18%
  Complexity       67       67
============================================
  Files            32       32
  Lines           255      256       +1
  Branches          7        7
============================================
  Hits            114      114
- Misses          137      138       +1
  Partials          4        4

Impacted Files
Coverage Δ
Complexity Δ

...a/pl/dicedev/kakebo/services/dtos/ExpensesDto.java
60.00% <0.00%> (-15.00%)
3.00 <0.00> (ø)

Continue to review full report at Codecov.

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

Codecov Report

Merging #56 (b4a9fcb) into main (dbe7a0e) will decrease coverage by 0.17%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##               main      #56      +/-   ##
============================================
- Coverage     44.70%   44.53%   -0.18%
  Complexity       67       67
============================================
  Files            32       32
  Lines           255      256       +1
  Branches          7        7
============================================
  Hits            114      114
- Misses          137      138       +1
  Partials          4        4

Impacted Files
Coverage Δ
Complexity Δ

...a/pl/dicedev/kakebo/services/dtos/ExpensesDto.java
60.00% <0.00%> (-15.00%)
3.00 <0.00> (ø)

Continue to review full report at Codecov.

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


Move "Smooth Animation" Into a Sample Project

Summary
Currently, smooth animation support is all over the core, despite the fact that it will only very rarely actually be used. It's rather specific and complicates a lot of things. There is no reason for it to be tied to the core. To fix this, move smooth animation into a distinct sample project, which will be released as a package.
Analysis

Update AnimSpriteRenderer API so a subclass can introduce smooth animation support for the sample project.
Remove builtin Default Resources related to smooth animation and re-create the required ones in the sample project.
Remove smooth animation support from the DynamicLighting plugin entirely.
Having it in a distinct sample project also has the advantage of being ready for testing at all times.

Done.


Fix unintended dev-only assignment in mesh baking

I wouldn't even call this a bug, but looks like the best fitting label...

That's fixed already by #82368 :)


How to clean all jump marks after switched to normal mode?

Problem Statement
Say if current snippet is defined like this
snippet fr
  for $1, $2 := range($3) {
    $4
  }$0

Press ESC to switch to normal mode after jumped to the $4 mark, move the cursor to some place, press "i", press "tab", cursor will still jump to previous snippet's $0 mark.
Ideas or possible solutions
When i press "ESC" to switch to normal mode, all marks of previous snippet should not remain valid.
Alternatives you have considered
Any solution for it? I used to use autocmd to manually disable all jump marks of luasnip when I switched to normal mode.

You could use an autocmd to run require('snippy.buf').clear_state(), which will clear all jump marks.

@dcampos It's not as easy as I think.
I create an autocmd for ModeChange and specify pattern for any mode to normal mode, the snippy jump will be totally disabled for nvim-cmp, reason is, when I hit enter to complete a auto-complete from lsp, the mode will change three times, i->n, n->v, v->s.
How to enable to snippy jump after nvim-cmp's complete and still clean the jump marks when I actually hit esc?

I see. Maybe you could set up a mapping for that? This one worked for me:
vim.keymap.set({'i', 's'}, '<Esc>', function()
    if require('snippy').is_active() then
        require('snippy.buf').clear_state()
    end
    return '<Esc>'
end, { expr = true })


WalletConnect: this.send is not a function

onboard to connect using WalletConnect causing an error after the scanning QR code, and then getting eth address using the web3 object created from the returned provider. WalletConnet works alone as expected.
Uncaught (in promise) TypeError: this.send is not a function
    at 48c68d3.js:2
    at Generator.next (<anonymous>)
    at 48c68d3.js:2
    at new Promise (<anonymous>)
    at Module.A (48c68d3.js:2)
    at request (48c68d3.js:2)
    at request (bfb900b.js:2)
    at e.d.send (bfb900b.js:2)
    at w (bfb900b.js:2)
    at C.c (bfb900b.js:2)

Hello, would you mind detailing a little bit more about how to recreate this issue because I cannot recreate at the moment. Hopefully we can get this resolved asap :)

@itsmnthn you have closed this without any info.
how did you resolve this issue? I am having the same thing now

@dzek69 I had an issue because of the scope of this object, changed function to arrow function, and able to solve because of access to this
Here is my implementation check it out

@itsmnthn that's weird, because after my analyze the problem seems to me to be fixable either from onboard internals or walletconnect side and shouldn't be fixable from the onboard config. I have arrow function there just like you are but still I get this issue.
Walletconnect dev even announced a fix: https://github.com/WalletConnect/walletconnect-monorepo/issues/384#issuecomment-769682914 but the current version released yestarday is not fixing it for me so I think this particular fix is not released yet.
Thanks for your reply anyway :)

Edit: Maybe your fix fixes just some of the cases? Can you try Walletconnect with the MetaMask app?

It works for me using MetaMask and other WallectConnect supported apps. Maybe try it out in the empty project and then see what happens 👍🏻


Token should work with sharing site set to same hostname

When using /share/<jwt-token> there is no overlap between the urls accessible at the sharing site and those of the normal site, so the sharing site should be able to use the same hostname.
This worked when tested locally (not verified) but not when deployed in a project on heroku for some reason, assume something project specific but would like to check/resolve before submitting PR back to cfpb repo.

issue describe in https://github.com/tombola/wagtail-sharing/pull/1#discussion_r466059906. this can be closed


prune does not check against tests

I noticed that if you run cargo features prune it will not ensure the feature changes are compatible with tests too.
I do understand that tests should probably use different features if they are not required by main, but does increase barrier to entry.
Maybe introduce a flag to have it also run against tests?
You can validate this by checking out this commit and remove this line, then run cargo features prune:
https://github.com/allada/nativelink-fork/blob/390490efbd86b3b16609fa0a30d067f5cae8ec8b/Cargo.toml#L72C1-L72C18

actually, I already do but it seems like cargo test does not run tests within a workspace.
will investigate this tomorrow or on Tuesday.
Thanks for reporting & for using the tool!

just published a new version that should fix this


CERTIFICATE_VERIFY_FAILED when using custom API provider via httpS

Hello,
My custom OpenAi Provider (ollama) use https with a self-signed certificate.
When the plugin try to connect to it, an error pops up with "error OpenAi: CERTIFICATE_VERIFY_FAILED..."
How can I tell the plugin to not verify the ssl context of the connection ? (or better, set the path to ca bundle to use ?)
thanks a lot !
update: I found some reference, but not sure if it is the solution, and how to apply it to your code. : https://stackoverflow.com/questions/48908044/how-to-disable-ssl-verification-for-http-client-httpsconnection-class-in-python

Hi, well, the problem is that the solution that I have in my mind I consider as the high severity security issue.
I mean the issue is caused by ssl pinning which is toggled on by default in the default Python http library, so from my perspective it's quite a bad idea to give a user an option to opt it out. Have you a different view on this?

Hello, thanks for your quick feedback.
I agree with you, we should not touch the default TLS Pinning mode.
In my case, my issue is about the unknown CA certificate provided by my certificate (as it is self signed).
I managed to bypass this SSL verification, by adding a context param to the self.connection.request like bellow.
    def prepare_request(self, json_payload):
        self.connection.request(method='POST', url='/v1/chat/completions', body=json_payload, headers=self.headers, context=ssl._create_unverified_context())

It would be cool if this behaviour could be set in settings with a boolean param.
like ssl_no_verify

I see you, more than that this is how I handle this issue by myself locally, when I needed to debug network layer of the plugin using mitm proxy.
But at my taste this issue is too specific to become the part of the release. Let's wait a bit if there any folks who'll upvote it as well.

Closing it so far.


Docker container not resolved to the appropriate ip address

I've an application composed of a kafka producer and another kafka consumer. I'm trying to deploy it on a Docker swarm on AWS with mutli-host networking enabled. Kafka container is created by the following docker-compose.yml file:
kafka:
  image: spotify/kafka
  environment:
    ADVERTISED_PORT: 9092
  ports:
    - "2181:2181"
    - "9092:9092"

This is how I run the containers for the different components:
> docker-compose -f helloworld_kafka.yml --x-networking up -d
Creating network "helloworld"
...
> docker run -d --name helloworld_producer_1 --net helloworld -it elsoufy/myimage ./myexec -role producer -queue helloworld_kafka_1:9092
> docker run -d --name helloworld_consumer_1 --net helloworld -it elsoufy/myimage ./myexec -role consumer -queue helloworld_kafka_1:9092

When I check the /etc/hosts of helloworld_kafka_1 I found entries for both helloworld_server_1 and helloworld_consumer_1:
<IP_ADDRESS>    kafka_container_id
<IP_ADDRESS>   localhost
::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
<IP_ADDRESS>    helloworld_server_1
<IP_ADDRESS>    helloworld_server_1.helloworld
<IP_ADDRESS>    helloworld_consumer_1
<IP_ADDRESS>    helloworld_consumer_1.helloworld

But when I check the logs of the latter I realize that they failed to connect to kafka. I see the following:
> docker logs consumer_container_id
2015/11/27 16:05:52 Kafka brokers: helloworld_kafka_1:9092
2015/11/27 16:05:52 Failed to start consuming dial tcp: lookup kafka_container_id on <IP_ADDRESS>:53: no such host

It looks like When <IP_ADDRESS> is the DNS (port 53) used by containers to resolve name and that it's not reachable. When I inspect the network of any nodes I cannot find this address, and it's not in the range of the helloworld overlay network (This address is part of my AWS VPC). How I can make this DNS reachable? any suggestion is appreciated.

@abronan i'm not using links, it's a DNS problem, why this issue is closed??

same problem here. "dial tcp: lookup ce328c91cbf4 on <IP_ADDRESS>:53: no such host"

This seems to be a timing issue.
I just ran in to the exact same problem: "dial tcp: lookup dtr-etcd-73aa19d1bd89.dtr-ol on <IP_ADDRESS>:53: no such host".  When I added a 5 second sleep before trying to access the host everything worked fine.

thanks @pdevine for the hint, but where exactly should the timing be added?

@dzlab It has been detected that this issue has not received any activity in over 6 months. Can you please let us know if it is still relevant:

For a bug: do you still experience the issue with the latest version?
For a feature request: was your request appropriately answered in a later version?

Thank you!
This issue will be automatically closed in 1 week unless it is commented on.
For more information please refer to https://github.com/docker/libnetwork/issues/1926


Get connection from Java EE server datasource

I don't know if it's possible to get the JDBC connection from a datasource and pass it to speedment, but I think that would be really interesting.
Or maybe a way to extract the connection info, so speedment would be able to create the connection by itself.

I think this would be a good thing! Loosely related to #177

It is possible to get a Connection from Datasource, I had it done several times.

@rkiranchowdhary , would you please demonstrate how to get connection from datasource?

We will try to see if we can have a look at this and implement the feature.


ver.653  Not listening  But [fully supported]

Not listening,  but other is green.
I've tried many ways, but I still can't solve the problem.

Applicable to https://github.com/stascorp/rdpwrap/issues/1843
Check for solution at https://github.com/stascorp/rdpwrap/issues/1883


[Migrated] import routes causing 404 error

Originally from: https://github.com/Miserlou/Zappa/issues/1475 by johnedstone
What is it about the import statement from app import routes in this example that causes the app to fail (returns 404) when deployed as a lambda package with Zappa?
Later: I just realized that if I changed the app_function value in zappa_settings.json generated by zappa init to microblog.app (or app.app ) that it would work.  The default: "app_function": "microblog.__init__.app", though it works with flask run, doesn't work when deployed with zappa.   You can close this issue.   Thanks again for this awesome project!

not enough info.
closing.


Add  Command Selector interface and various other improvements

Similar to how a single cluster is selected out of a set of theoretically equivalent clusters in a ClusterSelector implementation the CommandSelector will attempt to resolve a single Command out of a set of commands. Random and script based implementations are included in this PR.
Contrary to the current behavior of the ClusterSelector logic there is no current fallback for command selection. There is only a single bean in the context as of now. We may want to change this going forward.

Coverage increased (+0.05%) to 92.712% when pulling bab7b10125b58d456e934ddce0c0874cb49206a8 on tgianos:GENIE-513 into 197ac1ca9ef7b7ff67adf10b02ea8023c7457681 on Netflix:master.

I'm going to merge this. We can keep making improvements if necessary in subsequent PRs. I already have some work building on top of all this so I don't want to keep rebasing and going through the PR build cycle.


How to access backend data from frontend component AdminBro?

Hello I have a function that calculate sum of money spent by user. I want to use this function in my frontend component to plot the data on the dashboard of admin bro how can I achieve that? Thank you.

@bennaaym We don't provide support for AdminBro anymore since we'd rebranded to AdminJS 2 years ago.
You can use ApiClient to run requests against AdminJS backend, an example for dashboard is in the docs:
https://docs.adminjs.co/ui-customization/dashboard-customization#optional-creating-a-handler-for-your-dashboard-to-access-server-data


Monitoring excessive pod restarting across the cluster

Hi,
I am trying to monitor excessive pod pre-emption/reschedule across the cluster. Right now, we have a prometheous alert set up that monitors the pod crash looping as shown below.
 - name: KubePodCrashLooping
   message: '{{ $labels.namespace }}/{{ $labels.pod }} ({{ $labels.container }})
          is restarting {{ printf "%.2f" $value }} / second'
   severity: medium
   impact: This pod is crashing continuously
   action: Look at the pods logs to find why it is crashing consistently, if that doesn't show any service level issues check Kubelet's logs
   expression: >
          sum(rate(kube_pod_container_status_restarts_total{job="kube-state-metrics"}[15m])) by (namespace, pod)
          * on (namespace, pod) group_left(label_name)
          kube_pod_labels{label_monitoring="roger"} > 0
   for: 1h

But we want to monitor it in slight different way. I want to specify a value let say 55, if pods crashloops/restarts more than 55 times, lets say 63 times then I should get an alert saying pod crash looping has increased 15% than usual in specified time period. I did not find a good way to accomplish this in promql. Is this something that can be done?

It makes more sense to ask questions like this on the prometheus-users mailing list rather than in a GitHub issue. On the mailing list, more people are available to potentially respond to your question, and the whole community can benefit from the answers provided.


Added conditional data on type LIMIT and MARKET and fixed some typos.

A condition is created when Limit use original data with price and timeinforce and when market is removed price and timeinforce.

It looks goo to me. But there is some conflict about the file name. Please address the conflict and use the latest name BinanceSpotTrade.node.ts something.


Error: Cannot find module 'node_modules/sails/node_modules/captains-log

After run npm install and then run sails lift appear the next error stack.
error: Error: Cannot find module '/home/leosuncin/Workspaces/github/student/node_modules/sails/node_modules/captains-log'
  at Function.Module._resolveFilename (module.js:339:15)
  at Function.Module._load (module.js:290:25)
  at Module.require (module.js:367:17)
  at require (internal/module.js:16:19)
  at Object.<anonymous> (/home/leosuncin/Workspaces/github/student/node_modules/sails-hook-winston/index.js:6:19)
  at Module._compile (module.js:413:34)
  at Object.Module._extensions..js (module.js:422:10)
  at Module.load (/home/leosuncin/Workspaces/github/student/node_modules/coffee-script/lib/coffee-script/register.js:45:36)
  at Function.Module._load (module.js:314:12)
  at Module.require (module.js:367:17)
  at require (internal/module.js:16:19)
  at /home/leosuncin/Workspaces/github/student/node_modules/sails/lib/hooks/moduleloader/index.js:463:26
  at /home/leosuncin/Workspaces/github/student/node_modules/sails/node_modules/lodash/index.js:2523:13
  at /home/leosuncin/Workspaces/github/student/node_modules/sails/node_modules/lodash/index.js:3073:15
  at baseForOwn (/home/leosuncin/Workspaces/github/student/node_modules/sails/node_modules/lodash/index.js:2046:14)
  at /home/leosuncin/Workspaces/github/student/node_modules/sails/node_modules/lodash/index.js:3043:18
  at baseReduce (/home/leosuncin/Workspaces/github/student/node_modules/sails/node_modules/lodash/index.js:2520:7)
  at Function.<anonymous> (/home/leosuncin/Workspaces/github/student/node_modules/sails/node_modules/lodash/index.js:3446:13)
  at /home/leosuncin/Workspaces/github/student/node_modules/sails/lib/hooks/moduleloader/index.js:417:29
  at /home/leosuncin/Workspaces/github/student/node_modules/sails/node_modules/async/lib/async.js:52:16
  at /home/leosuncin/Workspaces/github/student/node_modules/sails/node_modules/async/lib/async.js:548:17
  at /home/leosuncin/Workspaces/github/student/node_modules/sails/node_modules/async/lib/async.js:542:17
  at _arrayEach (/home/leosuncin/Workspaces/github/student/node_modules/sails/node_modules/async/lib/async.js:85:13)
  at Immediate.taskComplete (/home/leosuncin/Workspaces/github/student/node_modules/sails/node_modules/async/lib/async.js:541:13)
  at processImmediate [as _immediateCallback] (timers.js:383:17)

I think sails try to find captains-log inside sails/node_modules, but is in ../node_modules. I tried to fix with these:
cd node_modules/sails
npm install

But then appear:
/home/leosuncin/Workspaces/github/student/node_modules/sails/lib/app/private/loadHooks.js:148
          async.each(_.without(_.keys(hooks), 'userconfig', 'moduleloader', 'userhooks'), function (id, cb) {
                ^

TypeError: async.each is not a function
  at Object.async.series.prepare (/home/leosuncin/Workspaces/github/student/node_modules/sails/lib/app/private/loadHooks.js:148:17)
  at /home/leosuncin/Workspaces/github/student/node_modules/async/lib/async.js:499:25
  at iterate (/home/leosuncin/Workspaces/github/student/node_modules/async/lib/async.js:108:13)
  at /home/leosuncin/Workspaces/github/student/node_modules/async/lib/async.js:119:25
  at /home/leosuncin/Workspaces/github/student/node_modules/async/lib/async.js:505:21
  at nextTickCallbackWith0Args (node.js:452:9)
  at process._tickDomainCallback (node.js:422:13)

I have to run npm install async inside node_modules/sails in order to fix the problem.
My current enviroment:

sails 0.12.0-rc7
node 5.5.0
npm 3.3.12

I am the only one with these issue.

Hi @leosuncin, NPM 3.3.12 unfortunately has some issues.  See our blog post on the issue, and the bug report on the NPM repo.  Please try installing the latest NPM with npm install -g npm@latest, then re-install Sails with:
npm uninstall -g sails
npm cache clean
npm install -g sails

(Or if you're not installing Sails globally, skip the -g option)

The problem persist after npm install -g npm@latest with:

npm 3.6.0
node 5.5.0
sails 0.12.0-rc7

error: Error: Cannot find module '/home/leosuncin/Workspaces/github/student/node_modules/sails/node_modules/captains-log'
  at Function.Module._resolveFilename (module.js:339:15)
  at Function.Module._load (module.js:290:25)
  at Module.require (module.js:367:17)
  at require (internal/module.js:16:19)
  at Object.<anonymous> (/home/leosuncin/Workspaces/github/student/node_modules/sails-hook-winston/index.js:6:19)
  at Module._compile (module.js:413:34)
  at Object.Module._extensions..js (module.js:422:10)
  at Module.load (/home/leosuncin/Workspaces/github/student/node_modules/coffee-script/lib/coffee-script/register.js:45:36)
  at Function.Module._load (module.js:314:12)
  at Module.require (module.js:367:17)
  at require (internal/module.js:16:19)
  at /home/leosuncin/Workspaces/github/student/node_modules/sails/lib/hooks/moduleloader/index.js:463:26
  at /home/leosuncin/Workspaces/github/student/node_modules/sails/node_modules/lodash/index.js:2523:13
  at /home/leosuncin/Workspaces/github/student/node_modules/sails/node_modules/lodash/index.js:3073:15
  at baseForOwn (/home/leosuncin/Workspaces/github/student/node_modules/sails/node_modules/lodash/index.js:2046:14)
  at /home/leosuncin/Workspaces/github/student/node_modules/sails/node_modules/lodash/index.js:3043:18
  at baseReduce (/home/leosuncin/Workspaces/github/student/node_modules/sails/node_modules/lodash/index.js:2520:7)
  at Function.<anonymous> (/home/leosuncin/Workspaces/github/student/node_modules/sails/node_modules/lodash/index.js:3446:13)
  at /home/leosuncin/Workspaces/github/student/node_modules/sails/lib/hooks/moduleloader/index.js:417:29
  at /home/leosuncin/Workspaces/github/student/node_modules/sails/node_modules/async/lib/async.js:52:16
  at /home/leosuncin/Workspaces/github/student/node_modules/sails/node_modules/async/lib/async.js:548:17
  at /home/leosuncin/Workspaces/github/student/node_modules/sails/node_modules/async/lib/async.js:542:17
  at _arrayEach (/home/leosuncin/Workspaces/github/student/node_modules/sails/node_modules/async/lib/async.js:85:13)
  at Immediate.taskComplete (/home/leosuncin/Workspaces/github/student/node_modules/sails/node_modules/async/lib/async.js:541:13)
  at processImmediate [as _immediateCallback] (timers.js:383:17)

Hm, on second look, it seems like the error is coming from the sails-hook-winston plugin you have installed.  You'll have to contact that project maintainer directly.  It may have compatibility issues with the latest version of Sails.

Yup, this line:
var captain     = require(path.resolve('node_modules/sails/node_modules/captains-log'));

will not work with NPM 3.  They'll need to patch that!

Thanks @sgress454


Would it be wrong to use parcelize to transfer the plant objects between the fragments?

Thank you for presenting the Sunflower app to us. I am using it as a template for an own app which tries to update an item in the Room database.
Still haven't found a solution but I will try to use the parcelize functionality instead the plantId or plantName arguments in the navigation.
Is it a recommended approach to do it like that or do you have some hints about implementing it? Do you have interest in using parcelize in the original Sunflower project as well?
I am looking forward to your answer.

This was no real problem. Simply provide the update methods inside the ViewModel, the Repository and the DAO. Calling the update method of the ViewModel inside the Fragment and it works like a charm.
Closing this issue.


Send2ue 2.4.3 "No instance of UnrealEditor found" on Debian 12

Steps to Reproduce the Problem:

Addon: Send to Unreal
Click Pipeline -> Exports -> Push Assets
See error "No instance of UnrealEditor found"  after a short delay with no additional info

Error Log: None other than the error in "No instance of UnrealEditor found" in a popup
OS: Debian GNU/Linux 12 (bookworm) x86_64
Addon Version: Send to Unreal 2.4.3
Blender Version: Blender  3.6.12
Unreal Version: 5.4.2-33871570+++UE5+Release-5.4

Stuff already tried:

 <IP_ADDRESS> addresses were <IP_ADDRESS>, I changed as per feedback in issue 695 this had no effect
tried Blender 4.x, same result
additionally tried send2ue versions: 2.4.3_v4fixes_28-03 and 2.4.5 with both Blender 3.6 and 4.x, same result

Work around:
Found a fix that's fairly self explanatory:

Edit send2ue/dependencies/remote_execution.py and change <IP_ADDRESS> to <IP_ADDRESS> for the following constant declarations (at the top) DEFAULT_MULTICAST_BIND_ADDRESS and DEFAULT_COMMAND_ENDPOINT, as shown here:
closed Blender
deleted all .pyc files in send2ue sub directories
started Blender and "Push Assets" works once more
(note a restart is needed, using System > Reload scripts in Blender does not seem to reliably reload changed addons)

Observations:

From reading descriptions of similar issues in Windows and Mac I think (but did not verify) loopback multicast behavior (<IP_ADDRESS>) differs on Linux as compared to Mac or Windows, using sudo ss -tunlp | egrep 6766 I could see UE upon first install was listening on <IP_ADDRESS>,however using tcpdump -i lo port 6766I could only packets sent by send2ue, never a response until implementing the workaround above so both UE and Blender bind to <IP_ADDRESS>, then I was able to see the packet response with tcpdump -- but not on loopback.
Also related
The following settings work but seem to interact with this problem somehow as well when set to 0 (in /etc/sysctl.conf)

net.ipv4.conf.all.rp_filter = 1
net.ipv4.conf.lo.rp_filter = 1
net.ipv4.conf.eth0.rp_filter = 1
net.ipv4.icmp_echo_ignore_broadcasts = 1

Probably needs further investigating how these interact with the problem
also note setting the kernel command-line ipv6.disable=1 or disabling ipv6 will cause UE to not start at all

The project is not maintaned anymore.
See this community fork instead:
https://github.com/poly-hammer/BlenderTools

Thank you! I finally got the addon to work in Linux thanks to your workaround.
In addition to your workaround, I also needed to set my Multicast Bind Address in the Unreal Project settings in the Remote Execution section. Setting that to <IP_ADDRESS> was what finally made it work for me.


Use LazyColumn to list animes in the Home tab

LazyColumn and LazyRow are similar to a RecyclerView in Jetpack Compose.
I'm learning Jetpack Compose so feel free to merge or reject this.

Appreciate the PR! Let me spend some time trying to understand those and then merge/leave comments.


feat: Websocket Infrastructure and Music dashboard

To set it up locally, run this branch (with lavalink running and connected), and install the  music-page branch of skyra.pw for the dashboard part.


[BUG] Roles Cannot be updated due to missing ObjectID in payload

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
When creating roles, no issues, but updating there is a ObjectID missing in the payload, which stops it from updating the record. Unfortunately, it seems CustomerKey cannot be used with Role as an upsert value.
Expected Behavior
Update of roles should perform as create roles.
Steps To Reproduce
Download Roles from any org
Move to deploy folder, and deploy
Version
3.1.3
Environment

OS: Windows
Node: 17
npm: 8

Participation

[X] I am willing to submit a pull request for this issue.

Additional comments
No response

still failing after the one commit, though with a different error:
before:

now:

stack trace
10:40:57.791 debug: TypeError: Cannot read property 'Results' of undefined
at C:\Git\sfmc-devtools\lib\metadataTypes\MetadataType.js:343:36
at Array.map ()
at Function.upsert (C:\Git\sfmc-devtools\lib\metadataTypes\MetadataType.js:343:18)
at async Function.deploy (C:\Git\sfmc-devtools\lib\metadataTypes\MetadataType.js:121:31)
at async Deployer.deploy (C:\Git\sfmc-devtools\lib\Deployer.js:92:32)
at async Function._deployBU (C:\Git\sfmc-devtools\lib\index.js:487:17)
at async Function.deploy (C:\Git\sfmc-devtools\lib\index.js:578:17)


Display in tracker if the current area has a uncollected relic

If the current area has a uncollected relic it should be highlighted in the tracker.
Idea: set the color of the icon of the relic counter yellow

waiting for a virtual uberstate -> waiting for c++ ;P

implemented in 3.0


UserId

I added a userModel, and userId opt at update/create (show at debug) but not insert userId at Revisions.
The Revisions table has a userdbid column.
var opts = {
//underscored: true,
//underscoredAttributes: true,
//enableCompression: false,
//enableMigration: true,
userModel: 'userdb'
,debug: true
};
afterHook called
instance: roledb {
dataValues:
{ ............ },
_previousDataValues:
{ ........ },
_changed: { structureread: true, structurewrite: true, revision: true },
_modelOptions:
{ ........ },
_options:
{ ........ },
__eagerlyLoadedAssociations: [],
isNewRecord: false,
context: { delta: [ [Object], [Object] ] } }
opt: { userId: 2,
fields: [ 'structureread', 'structurewrite', 'updatedAt', 'revision' ],
defaultFields: [ 'structureread', 'structurewrite', 'updatedAt' ],
hooks: true,
validate: true }

Faced the same problem.
Pass the userModel to options. add userId opt at update.
But the query is executed without userId.
INSERT INTO "Revisions" ("id","model","document","operation","documentId","revision","createdAt","updatedAt") VALUES (DEFAULT,'OrganizationSettings','{"id":1,"use_fisca l_printer":true,"fiscal_printer_service_type":"atol","use_scanner":false,"scanner_service_uri":"","revision":10,"organization_id":1}','update',1,10,'2019-03-02 12:14:06.283 +00:00','2019-03 -02 12:14:06.283 +00:00') RETURNING *;

@rmeloni @lmorningstar116 are you using the continuation local storage package?

No...
The problem is that the Revision.build() use "userId" field and my table name is userdb and create a userdbid field at Revision table.
I changed userId: ns && ns.get(options.continuationKey) || opt['userId'], to userdbId: ns && ns.get(options.continuationKey) || opt['userId'], at query and works.

Ah I get it, I think if I add a userIdAttribute that you can set to userdbId in your case and then I will use that in that line it should pick the right attribute 🤔

@rmeloni can you try it by installing the package from this github commit:
git://github.com/nielsgl/sequelize-paper-trail.git#e62c103bac72cb848018ef1554bd5dbb64d8ee20

@nielsgl this github has a change for previous and current version.  Is it github?

I'm not sure what you mean. You can find the code here: https://github.com/nielsgl/sequelize-paper-trail/blob/feature/refactoring/lib/index.js

It´s works!

Awesome, I'm finishing up that branch and will release it tomorrow as a next major release (v3). I'll drop a comment here when it's done so you can upgrade it and install it as a normal npm package.

@rmeloni it's available in<EMAIL_ADDRESS>


Spark package

Is anyone working on getting Spark in mantl-universe? I am working to deploying Spark on MANTL, having a package here it might be the way to go. I could put some extra effort in making a PR if you guys think it would be useful.

Yes, please. It would be really nice to have. Let me know if I can help.

Just figured this out #27, I might test if that works first!

code was contributed in #30. merged manually into the version-0.6 branch


Missing Endstone Texture

The version I used is for 1.18.1 on a modpack called "afterlife" which I have slightly modified, removing a mod that makes you change origins when you die. Arriving at the end the normal endstone (dragon island and also the various islands after to go and get the elytra), they have the problem of giving the black and purple block without texture. Removed the mods the problem is not there. (At the moment I have no screenshots because I have taken the mods off for a long time, and I am nowhere near the end in the new world!)

One of your mods breaks Fabric rendering API or endstone rendering. You can use Indium to fix this. This is not a BE issue


Feature/prisma upgrade

This PR includes:

Upgrade all prisma related packages to v4
Upgrade most of the package to the latest versions
Replace @prisma/sdk with @prisma/internals
Keep typescript version due to the jest error

@abenhamdine Sorry this was an unintentional change. This change was supposed to be for our internal fork of this repo. My bad. Closing this PR.


what is going on?

see above, somebody help me?
I can run project example successfully.

Please show your code.
It seems that you pass a wrong property type to ellipsizeMode

@whatlife
Got the same error: problem in this component
https://github.com/dancormier/react-native-swipeout/blob/master/NativeButton.js#L61
and clip is working only for iOS

@n4bcak3 @whatlife Sorry about this, this pr https://github.com/dancormier/react-native-swipeout/pull/183/files caused the problem.
I will fix this soon.

https://github.com/dancormier/react-native-swipeout/commit/533b307d359d797d86cae88269b77fb00ada23cb
version: 2.1.3

Setting the ellipsizeMode fixes the below issue.  I suggest the following:
ellipsizeMode={Platform.OS ==='ios' ? 'clip' : 'tail'}
This will fix issue on iOS and perform the default for Android.
https://facebook.github.io/react-native/docs/text.html
Without the clip (and Android behavior)

With the clip on iOS

@kmcrawford Hope for your PR


make the doc accessible at runtime

copy it into the static files of the python package.
make a menu item to open up the top level.

may need to define a MixedContentsManager like https://github.com/jupyter/jupyter-drive/blob/master/README.md
for referring to a regular filesystem rooted at doc.


RuntimeError when predicting with the french models

I tried to use the french models (both fr.22000 and fr-txt.large.19000) on a very simple text:

j'aime les fleurs les olives et la raclette

When running python3 recasepunc.py predict fr.22000 < input.txt > output.txt (or with the other model), I get the following RuntimeError:
Traceback (most recent call last):
  File "/home/mael/charly/recasepunc/recasepunc.py", line 733, in <module>
    main(config, config.action, config.action_args)
  File "/home/mael/charly/recasepunc/recasepunc.py", line 707, in main
    generate_predictions(config, *args)
  File "/home/mael/charly/recasepunc/recasepunc.py", line 336, in generate_predictions
    model.load_state_dict(loaded['model_state_dict'])
  File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1497, in load_state_dict
    raise RuntimeError('Error(s) in loading state_dict for {}:\n\t{}'.format(
RuntimeError: Error(s) in loading state_dict for Model:
	Unexpected key(s) in state_dict: "bert.position_ids".

I tried the same with the english model, and it worked perfectly. Looks like something is broken with the french ones?

Did you install the version of transformers from requirements? This kind of error is typical of a mismatch in Bert model class structure.

That was indeed the issue, and installing the required version of transformers fixed it. Thanks a lot!
I may as well add that I did not use requirements.txt because, when running pip3 install -r requirements.txt -f https://download.pytorch.org/whl/torch_stable.html, I got the following error:
ERROR: Could not find a version that satisfies the requirement torch==1.9.0+cu111 (from versions: 1.11.0, 1.11.0+cpu, 1.11.0+cu102, 1.11.0+cu113, 1.11.0+cu115, 1.11.0+rocm4.3.1, 1.11.0+rocm4.5.2, 1.12.0, 1.12.0+cpu, 1.12.0+cu102, 1.12.0+cu113, 1.12.0+cu116, 1.12.0+rocm5.0, 1.12.0+rocm5.1.1)

I had the same problem for the French language.
I tested several types of configuration files. With the following content as requirements.txt file, the installation is done without problem:
git+https://github.com/benob/mosestokenizer.git
numpy
regex
torch
tqdm
transformers==4.10.0

Then, I can install recasepunc with simple pip install -r requirements.txt.
I would add that the pytorch version required in the original requirements.txt file crashes my computers that don't have enough RAM (8GB + 6GB swap). The latest version doesn't seem to exceed the 3GB of Ram used for the installation.
With this requirements.txt file the installation works very well (I have only tested the French models and the English model...) ! Maybe it deserves a commit ;)


Remove support for pre-3.6 server releases

JAVA-4295
I divided this up into a commit for each release that we're dropping.  So if we ever need to roll back, it's easy to do it for a single release.
I suggest enabling Hide Whitespace Only Changes in the UI when you review, as many of the lines changed only whitespace based on the removal of conditional statements.

@jyemin Just curious, what was the process for removing support? Were you able to find all locations by following version checks from some single location? (For example, I see that you have removed methods like validateReadConcern, but I did not immediately see why.)

Yes, just following version checks and then removing anything unused as a result of removing the version check and any code branches that were no longer needed.


Trying an operation after calling .quit() doesn't trigger any errors

Given this piece of code :
var memjs = require('memjs')
var client = memjs.Client.create('localhost:11211')

client.quit()

client.get('hello', function(err, val) {
  // Callback never called since we are disconnected
  console.log(err, val);
})

We never enter the get() callback because we're disconnected. I was wondering if this was a desired behavior or a bug?

Hey Julien
Good question. I looked at the code, and based on that

Calling quit closes all connections (code).
Calling get will create a new connection and perform the request (code).

So callbacks should be executed on get requests that happen after the quit. I suspect the reason the callback is not executed is because of the race condition between quit and get as detailed here.
To answer your question, if the callback is not called, it is a bug. If the connection is in the process of being closed, the callback should at least be called with an error.

Hey, thanks for your reply!
Yes, it's definitely that. As soon as I add a setTimeout after the client.quit then it's OK, the callback is called.
I will try sending a PR

Hello, sorry, I've decided not to support memcached and to use redis instead. So i won't be able to make a PR


v2 changes

it won't happen soon, just want to list all the possible things:

Node.js

Drop Node 12 support (end-of-life 2022-04-30)
Drop Node 13 support (end-of-life 2020-06-01)
Drop Node 14 support (end-of-life 2023-04-30)
Drop Node 15 support (end-of-life 2021-06-01)
Drop Node 17 support (end-of-life 2022-06-01)

jest v28 https://jestjs.io/blog/2022/04/25/jest-28, https://jestjs.io/docs/upgrading-to-jest29
Typescript v5.0 https://devblogs.microsoft.com/typescript/announcing-typescript-5-0/
rollup v3: https://www.rollupjs.com/guide/migration
upgrade react/react-dom to v18 (template)
Convert to esm? (ts v4.7)
...

Maybe consider switching dts.config.ts/dts.config.js to use a defineConfig function similar to how vitest does?
Example:
import { defineConfig } from 'dts-cli/config';

export default defineConfig({
  rollup: (config: RollupOptions, options: DtsOptions) => // ...
});

For better compat, I was thinking to support both, and it can be in a minor release - as no longer a breaking change?

How about using Vitest instead of Jest? The API is almost the same and the performance is so much better.

sounds interesting! :🤔

rollup => vite (lib mode)
jest => vitest

They are already on Jest 29!?

Consider Node 18 as well since it goes active in November 2022

pushed a pre-release: https://github.com/weiran-zsd/dts-cli/releases/tag/v2.0.0-beta.0
I will test it in some of my private projects and push a stable release (if works fine! 😄 ).

v2.0 has been released: https://github.com/weiran-zsd/dts-cli/releases/tag/v2.0.0


[Android] - Toast appears below Modal

The below screen recording demonstrates the bug reproduction.
https://user-images.githubusercontent.com/23293248/129330590-4eff19d3-2f8a-4e72-8526-08044876c158.mov
Reason
On Android, we're using RN's Modal to show the Overlay instead of using OverlayContainer. This has been done for accessibility reasons (to auto-shift focus when opened). This is leading to the below issue. RN's Modal has the highest precedence and it won't let any absolutely placed View appear on top. A quick fix would be to replace RN modal with OverlayContainer and shift focus manually.

This is also an issue on iOS with react-navigation's modal.

We're working on it. Thanks for reporting!

+1

@surajahmed any updates on this?
I can also confirm I am having the same problems as @garrett-gottlieb with react navigation modals.
Perhaps the title of this issue should be changed to iOS as well or should I open another issue?

Hi @yotamishak.
We're changing the architecture of the overlay component. This is due to the conflict between the native overlay and our Portal component. We'll fix this in the coming release. Thanks for your patience.

hi @surajahmed , any updates on this?

Still waiting here also

same issue here. Still waiting here...

Hi, any updates on this?


update default reply_delimiter

This makes the default setting "-- REPLY ABOVE THIS LINE --", which is consistent with the Readme and loooks better than "Reply ABOVE THIS LINE". Fixes #218.

Thanks!

No problem. Thanks for creating the gem - it's really useful!


Specifying  'build_branch'  / 'branch' for che plugin and devfile registry to have a control over promotions to prod-preview

…

Closing in favour of https://github.com/openshiftio/openshiftio-cico-jobs/pull/1056
It was decided to create a dedicated job for prod-preview / prod updates


What to do with forfeited HNT?

          I like this HIP but think it needs to go further.

Where does the HNT go that is forfeited by people who submit denied requests?  I propose it goes to a Subdao with the funds set aside for compensation of those who have waited moths for a review already. Should a removal request be validated it should be easy to see the date the hotpot was put on the deny list and how many days have passed to a successful review. a compensation could be fixed at 0.05 HNT a day for example. This can be in conjunction with the HIP entitled : Hold_Rewards_for_Denylist_Hotspots.  This is a show of good faith in Innocent hotspot owners and restores trust in the network.

submitted.
Originally posted by @Screwtape7 in https://github.com/helium/HIP/issues/662#issuecomment-1556007256
This issue has been questioned in PR 551 and referenced in this PR under "Unresolved Questions "

@Tony12times - I think you put this comment in the wrong place. Make sure it's on your PR. This was opened as an Issue ticket. I am closing it.

@vincenzospaghetti yes.  I made as an accident and asked for help right after I realized it.


Stack's version warning is considered as error

When using stack with GHC8.8, stack emits follwing warnings via stderr.
Stack has not been tested with GHC versions above 8.6, and using 8.8.2, this may fail
Stack has not been tested with Cabal versions above 2.4, but version <IP_ADDRESS> was found, this may fail

Despite of these messages, brittany works fine with GHC 8.8.
Below is an typical error message with incorrect syntax.
Command failed: brittany --write-mode display
parse error:
"RealSrcSpan SrcSpanOneLine \"stdin\" 9 26 28: parse error on input \8216le\8217"

https://github.com/MaxGabriel/brittany-vscode-extension/blob/e4c1820b73fee4a89646434276a82e8e0cd34c05/src/formatter.ts#L154-L158
IMHO checking if err contains parse error or ignoring line starts with Stack has not been tested with could be a workaround.

If you run stack --silent exec brittany from the command line, does it still show the version errors?
I'd rather not use any string manipulation functions, because that could be prone to error in the future.

stack --silent exec brittany
stack --verbosity silent exec brittany
stack --verbosity error exec brittany

All of them does not shows version related errors.

Thank you for checking.
Modifying the command that it is called to include --silent should fix it then.
I will update the extension when I have the chance.

I added --verbosity error as some errors should still be reported.
The extension has been updated to 0.0.9 with the fix. Should be live on the marketplace in a few minutes.


Text does not appear to be smoothed

Apologies as this is quite a vague issue and I don't have any diagnostics to show, but I don't see any change to the smoothing in VSCode version 1.11.2, using Text Clarity 1.0.1.
I can see the new additions to index.html after installing (although I had to run VSCode in administrator mode first).

The purpose of the extension is to disable the smoothing (anti-aliasing) of the editor pane; this is to allow for usage of bitmap fonts that do not require any form of anti-aliasing (such as Terminus TTF)
The name of the extension might be a bit misleading, I see that now.


[1/3] Proper path resolution: add openat functionality

This PR is the first in a series that will implement the path resolution algorithm described by wasi-filesystem.  Since this new path resolution implementation requires the use of openat, this PR first introduces openat(2) and its Windows equivalent NtCreateFile to Wazero.

[x] Linux implementation with openat(2)
[x] Darwin implementation with trampoline to openat(2)
[x] Windows implementation with NtCreateFile
[x] Add more test cases to internal/sysfs/dirfs_test.go

The next PR will stack on this one and use the openat functionality to implement path resolution.

FYI I can't stack PRs on top of this one because I can't push branches to this repo.

Quick update: I'm on a cross-country move at the moment. Will get around to this again after mid-August. Thanks for the speedy reviews @evacchi


sample: structured LLM response data

Process LLM response in structured data show in a chart using the responseBuilder argument to the LlmChatView widget: https://github.com/csells/flutter_ai_toolkit/blob/main/lib/src/views/llm_chat_view.dart#L31.
Note: associated with this feature.

closed as dup to #42


Add gitpod config

this commit adds support for Gitpod.io, a free automated
dev environment that makes contributing and generally working on GitHub
projects much easier. It allows anyone to start a ready-to-code dev
environment for any branch, issue and pull request with a single click.

Change Description

Deployment Changes

[ ] Deployment Changes

API Changes

[ ] API Changes

Documentation Additions

[ ] Documentation Additions

That container doesn't include tools necessary to build eosio.contracts.


Request to update gh_pages

Hello,
While trying to follow the example and also reference the gh_pages sites, I've realized that they are running two entirely different code bases. The gh_pages are severely out of date, so it was a little hard to figure out why copying the example code gave me a white background, while the gh_pages example gave me the typical black background.
Can someone update this for other newcomers?

@Mr-Antivirus Thanks for your request.  I'm working on a new gh-pages site.  I'll see about getting my WIP pushed up so people can at least see some of the updated material soon.

@Mr-Antivirus I spent a good portion of the day today working on this... hopefully this meets your needs.  It's incomplete, but should be much more up-to-date and have better examples.
https://reactcommunity.org/react-modal/


Add extensibility support for custom types

Add PBFormat a combination of PBReader and PBWriter
Use cats to provide extensibility methods to support custom types:

provide map to create new PBReader from existing ones
provide contramap to create new PBWriter from existing ones
provide imap to create new PBFormat from existing ones

Update README

Codecov Report

Merging #14 into master will increase coverage by 0.05%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #14      +/-   ##
==========================================
+ Coverage   98.97%   99.03%   +0.05%
==========================================
  Files           5        6       +1
  Lines         195      207      +12
  Branches        1        1
==========================================
+ Hits          193      205      +12
  Misses          2        2

Impacted Files
Coverage Δ

src/main/scala/pbdirect/PBFormat.scala
100% <100%> (ø)

src/main/scala/pbdirect/PBReader.scala
97.67% <100%> (+0.17%)
:arrow_up:

src/main/scala/pbdirect/PBWriter.scala
97.29% <100%> (+0.23%)
:arrow_up:

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 f3cc946...baf367b. Read the comment docs.


Maintain changelog file

Make sure these boxes are checked before submitting your issue - thank you!

[.] I have checked the superset logs for python stacktraces and included it here as text if any
[.] I have reproduced the issue with at least the latest released version of superset
[.] I have checked the issue tracker for the same issue and I haven't found one similar

Superset version
Expected results
CHANGELOG.md should be updated as part of release
Actual results
CHANGELOG.md is not being maintained
Steps to reproduce
Open the CHANGELOG.md, the last release listed is 0.15.1, current release is 0.16.0

I usually do it but skipped it on a few releases. Its up to date now

It has fallen behind again...


Verify learner count

User Story
As a developer,
I want to run a BigQuery query to verify that the # of learners that I am seeing in All Learners matches what is displayed in the FTL app,
So that we can 1.) check our work to verify ingestion is working as intended and 2.) that we get a sense of how many people download the app and actually become Learner Level 1 by opening the app.
Acceptance Criteria
Given that I am viewing the All Learners tab of the FtL web app and the BigQuery Console for Follow the Learners
when I run the following query in BigQuery, I should see a number equal to the number of learners listed on the All Learners tab.
Query:
SELECT
  COUNT(event_name)
FROM
  `ftm-hindi.analytics_174638281.events_*`
WHERE
  event_name = "first_open" AND traffic_source.name = "India-Hindi-FTM-5_11_20_Campaign"
UNION ALL
SELECT
  COUNT(event_name)
FROM
  `ftm-swahili.analytics_160694316.events*`
WHERE
  event_name = "first_open" AND traffic_source.name = "Tanzania-Swahili-FTM-5_11_20_Campaign"

Currently the query returns the following information:
India Campaign: 187 learners
Tanzania Campaign: 248 learners


[BUG]: Parsing https://example.com error

[https://example.com](https://example.com)

see https://github.com/web-infra-dev/rspress/issues/875
After mdx-rs compile:

https://example.com

It's looks like a bug in the markdown library.
If you use to_mdast to parse  [https://example.com](https://example.com) you get the following result

and if you use to_mdast to parse  [example](https://example.com) you get the following result

comparing the structure of the two reveals an extra layer of nesting

set gfm_autolink_literal to true does this, which seems to be a problem with the markdown library

The rust version of markdown library is just getting afoot, still has a long way to go hh.


[Request] please add PDFgear 🫡

Package Request
Criteria
For a package to be acceptable in the Nonportable bucket, it should be:

[X] a reasonably well-known and widely used application
[X] the latest stable version of the program
[X] the full version i.e. not a trial version

Information
Name: [ pdfgear ]
Description: [ Read, edit, convert, merge, and sign PDF files across devices, for completely free and without signing up. ]
Homepage: [ https://www.pdfgear.com/ ]
Download link(s): [ https://www.pdfgear.com/download/pdfgear_setup_v2.1.0.exe ]
Some indication of popularity/repute:

[Get more practical video tutorials on the PDFgear YouTube Channel]

5 BEST PDF Editors in 2023 (One is REALLY FREE!)

Software Vision:

Revolutionizing the way people interact with PDFs.
We believe everyone has access to the tools they need, which is why we're currently offering PDFgear for free. We take privacy seriously and ensure all data is secure.

thanke I solved the problem.


zeebe installation fails

I am trying to install zeebe via helm charts in a separate namespace, the same fails. I have capture the debug logs from helm command as below:
$ helm install zeebe zeebe/zeebe-full-helm -n zeebe --debug
install.go:178: [debug] Original chart version: ""
install.go:199: [debug] CHART PATH: /home/edgeprov/.cache/helm/repository/zeebe-full-helm-1.3.1.tgz
client.go:128: [debug] creating 1 resource(s)
install.go:151: [debug] CRD alertmanagerconfigs.monitoring.coreos.com is already present. Skipping.
client.go:128: [debug] creating 1 resource(s)
install.go:151: [debug] CRD alertmanagers.monitoring.coreos.com is already present. Skipping.
client.go:128: [debug] creating 1 resource(s)
install.go:151: [debug] CRD podmonitors.monitoring.coreos.com is already present. Skipping.
client.go:128: [debug] creating 1 resource(s)
install.go:151: [debug] CRD probes.monitoring.coreos.com is already present. Skipping.
client.go:128: [debug] creating 1 resource(s)
install.go:151: [debug] CRD prometheuses.monitoring.coreos.com is already present. Skipping.
client.go:128: [debug] creating 1 resource(s)
install.go:151: [debug] CRD prometheusrules.monitoring.coreos.com is already present. Skipping.
client.go:128: [debug] creating 1 resource(s)
install.go:151: [debug] CRD servicemonitors.monitoring.coreos.com is already present. Skipping.
client.go:128: [debug] creating 1 resource(s)
install.go:151: [debug] CRD thanosrulers.monitoring.coreos.com is already present. Skipping.
W0117 18:44:32.951595 1150858 warnings.go:70] policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget
client.go:299: [debug] Starting delete for "zeebe-ingress-nginx-admission" ServiceAccount
client.go:128: [debug] creating 1 resource(s)
client.go:299: [debug] Starting delete for "zeebe-ingress-nginx-admission" ClusterRole
client.go:128: [debug] creating 1 resource(s)
client.go:299: [debug] Starting delete for "zeebe-ingress-nginx-admission" ClusterRoleBinding
client.go:328: [debug] clusterrolebindings.rbac.authorization.k8s.io "zeebe-ingress-nginx-admission" not found
client.go:128: [debug] creating 1 resource(s)
client.go:299: [debug] Starting delete for "zeebe-ingress-nginx-admission" Role
client.go:328: [debug] roles.rbac.authorization.k8s.io "zeebe-ingress-nginx-admission" not found
client.go:128: [debug] creating 1 resource(s)
client.go:299: [debug] Starting delete for "zeebe-ingress-nginx-admission" RoleBinding
client.go:328: [debug] rolebindings.rbac.authorization.k8s.io "zeebe-ingress-nginx-admission" not found
client.go:128: [debug] creating 1 resource(s)
client.go:299: [debug] Starting delete for "zeebe-ingress-nginx-admission-create" Job
client.go:328: [debug] jobs.batch "zeebe-ingress-nginx-admission-create" not found
client.go:128: [debug] creating 1 resource(s)
client.go:528: [debug] Watching for changes to Job zeebe-ingress-nginx-admission-create with timeout of 5m0s
client.go:556: [debug] Add/Modify event for zeebe-ingress-nginx-admission-create: ADDED
client.go:595: [debug] zeebe-ingress-nginx-admission-create: Jobs active: 0, jobs failed: 0, jobs succeeded: 0
Error: INSTALLATION FAILED: failed pre-install: timed out waiting for the condition
helm.go:88: [debug] failed pre-install: timed out waiting for the condition
INSTALLATION FAILED
main.newInstallCmd.func2
helm.sh/helm/v3/cmd/helm/install.go:127
github.com/spf13/cobra.(*Command).execute
github.com/spf13/cobra@v1.2.1/command.go:856
github.com/spf13/cobra.(*Command).ExecuteC
github.com/spf13/cobra@v1.2.1/command.go:974
github.com/spf13/cobra.(*Command).Execute
github.com/spf13/cobra@v1.2.1/command.go:902
main.main
helm.sh/helm/v3/cmd/helm/helm.go:87
runtime.main
runtime/proc.go:225
runtime.goexit
runtime/asm_amd64.s:1371

Please try with the new chart https://github.com/camunda-community-hub/camunda-cloud-helm/tree/main/charts/ccsm-helm


[SECOAUTH-432] Support automatically destroying session on OAuth2 authorization server as soon as user redirected to client app

Priority: Minor
Original Assignee: Dave Syer
Reporter: Harleen Sahni
Created At: Wed, 18 Dec 2013 02:41:26 +0000
Last Updated on Jira: Mon, 30 Dec 2013 14:52:48 +0000

It'd be a nice feature to only maintain the session on the authorization server as long the user is granting approval to an oauth2 client, and no longer. This is useful for when your authorization server's sole role is for authorizing oauth2 clients, and nothing else. In this case, a longer lived session has no real value.
Also, if an oauth2 client wants to switch users for oauth2 access, it can't do so easily today. As long as the user's session is alive on the authorization server what will happen is as the client sends the user to /oauth/authorize, the client will be using the user's old session, and the client will be auto approved since it has a current access token for that user.
This feature should be configurable.
Currently I've accomplished this with use of aspects:
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpSession;

import org.apache.log4j.Logger;
import org.aspectj.lang.JoinPoint;
import org.aspectj.lang.annotation.AfterReturning;
import org.aspectj.lang.annotation.AfterThrowing;
import org.aspectj.lang.annotation.Aspect;
import org.springframework.security.core.context.SecurityContextHolder;
import org.springframework.stereotype.Service;
import org.springframework.web.context.request.RequestContextHolder;
import org.springframework.web.context.request.ServletRequestAttributes;
import org.springframework.web.servlet.ModelAndView;
import org.springframework.web.servlet.View;

@Service
@Aspect
public class SessionInvalidationOauth2GrantAspect {

    private static final String FORWARD_OAUTH_CONFIRM_ACCESS = "forward:/oauth/confirm_access";
    private static final Logger logger = Logger.getLogger(SessionInvalidationOauth2GrantAspect.class);

    @AfterReturning(value = "within(org.springframework.security.oauth2.provider.endpoint..*) && @annotation(org.springframework.web.bind.annotation.RequestMapping)", returning = "result")
    public void authorizationAdvice(JoinPoint joinpoint, ModelAndView result) throws Throwable {

        // If we're not going to the confirm_access page, it means approval has been skipped due to existing access
        // token or something else and they'll be being sent back to app. Time to end session.
        if (!FORWARD_OAUTH_CONFIRM_ACCESS.equals(result.getViewName())) {
            invalidateSession();
        }
    }

    @AfterReturning(value = "within(org.springframework.security.oauth2.provider.endpoint..*) && @annotation(org.springframework.web.bind.annotation.RequestMapping)", returning = "result")
    public void authorizationAdvice(JoinPoint joinpoint, View result) throws Throwable {
        // Anything returning a view and not a ModelView is going to be redirecting outside of the app (I think).
        // This happens after the authorize approve / deny page with the POST to /oauth/authorize. This is the time
        // to kill the session since they'll be being sent back to the requesting app.
        invalidateSession();
    }

    @AfterThrowing(value = "within(org.springframework.security.oauth2.provider.endpoint..*) &&  @annotation(org.springframework.web.bind.annotation.RequestMapping)", throwing = "error")
    public void authorizationErrorAdvice(JoinPoint joinpoint) throws Throwable {
        invalidateSession();
    }

    private void invalidateSession() {
        HttpServletRequest request = ((ServletRequestAttributes) RequestContextHolder.getRequestAttributes())
                .getRequest();
        HttpSession session = request.getSession(false);
        if (session != null) {
            logger.warn(String.format("As part of OAuth application grant processing, invalidating session for request %s", request.getRequestURI()));

            session.invalidate();
            SecurityContextHolder.clearContext();
        }
    }

}

Comments:
david_syer on Mon, 30 Dec 2013 10:57:23 +0000

I'm not really sure what the use case is for a "client switching users". Maybe you could be a bit more specific about that?
In any case I would prefer not to have explicit HttpSession-specific code in Spring OAuth if we can avoid it. A short session timeout in the server is definitely a good idea, but that's better left to the server setup.
If the client is a webapp (I think that's the only scenario that makes sense in your description), then the user's session will be tied to their browser, and they can control sessions by logging out and logging back in again (as long as the server provides that feature, which isn't really anything to do with OAuth)?

harleen on Mon, 30 Dec 2013 14:52:48 +0000

A short lived session on the authorization server would help accomplish about the same thing, but not as effectively.
When talking about the client that's being authorized for oauth2 access, it's true that the session on that client is tied to the browser. We do provide a logout out of the client session. However, in our case, the client's sole means of authenticating the user is via being redirected to login to the oauth2 authorization server, and be redirected back the client web app. The client has no user store of its own and no login of its own. So when the the client web app logs out of it's session, the user is asked to log back in by being redirected to the authorization server to login again. If the authorization server's session is still active, the user would be automatically logged back in. This isn't desirable for us, and that's why we're killing the authorization server's session immediately after authorization.

Great! This is exactly what I was looking for.

Awesome Harleen.
This may not be an oath protocol, but this should be a basic/necessary feature in spring-oauth to make oauth protocol work correctly.

This worked wonderfully for me.  When a user logs out of my ui service, they would just get logged back in automatically since their auth server session never expired.  Now, when the user logs out of the ui server, they are brought to the auth server login page as expected.

Outstanding--exactly what I needed! @dsyer, when my people come to enslave your planet, you will not be harmed.

Note that the aspect above will work, but it's neater to do the same thing with a HandlerInterceptor (may not have been possible at the time the feature request was made). E.g. this should work in a AuthorizationServerConfigurerAdapter:
		@Override
		public void configure(AuthorizationServerEndpointsConfigurer endpoints)
				throws Exception {
			...
			endpoints.addInterceptor(new HandlerInterceptorAdapter() {
				@Override
				public void postHandle(HttpServletRequest request,
						HttpServletResponse response, Object handler,
						ModelAndView modelAndView) throws Exception {
					if (modelAndView != null
							&& modelAndView.getView() instanceof RedirectView) {
						RedirectView redirect = (RedirectView) modelAndView.getView();
						String url = redirect.getUrl();
						if (url.contains("code=") || url.contains("error=")) {
							HttpSession session = request.getSession(false);
							if (session != null) {
								session.invalidate();
							}
						}
					}
				}
			});
		}

This interceptor jest fine when form login shows as result of standard process - ie. GET /oauth/authenticate which redirects to /login.html on which you log in.
But when you directly enter at /login.html (manually write URL or click backward in browser) and log in then this interceptor is not even called and session stayed alive.

@tomasz-werminski that's expected though, I should think, because you aren't going to go through the OAuth2 protocol in that case. You just authenticated with the auth server, and now you could, for instance do some admin actions in there or something. It's nothing to do with OAuth2 at that point. Or am I missing something?

@dsyer
Yes, you are right, /login.html page on her own is not a part of oauth2 flow. But from user's point of view it may be a bit confiusing.
User starts authentication process - ie. /oauth/authenticate call happens, then redirect to /login.html, then interceptor kicks in and finally redirect to client-app happens. But if at this moment user clicks browser backward button he or she is able to see login page again. So he or she can log-in too and leave active session. In this case, next call for /oauth/authenticate won't trigger login page.
This is, of course, not a problem with this interceptor because its role is to invalidate session on oauth2 auhtentication process. But if your authorization server's only role is to authorize oauth clients above flow could be a problem (luckily it's no frequent).
I was faced with such a flow so I've decided to describe it here because it's related to this topic, maybe it'll be helpful for somebody. As a workaround in login controller I check if /login.html call is "a part of normal flow", ie. whether in session is any saved request which triggered login proces. If not I make redirect to some configured URL.

For newcomers, use the HandlerInterceptor approach instead of the @Aspect, because the last one will invalidate the session "always", even when user mistype his/her credentials.

How this feature can be implemented with Single Sign on Kerberos/Spnego authentication. I am using pretty older version of zuul 1.1.0 . A example or pointer would be great.

Note that the aspect above will work, but it's neater to do the same thing with a HandlerInterceptor (may not have been possible at the time the feature request was made). E.g. this should work in a AuthorizationServerConfigurerAdapter:
		@Override
		public void configure(AuthorizationServerEndpointsConfigurer endpoints)
				throws Exception {
			...
			endpoints.addInterceptor(new HandlerInterceptorAdapter() {
				@Override
				public void postHandle(HttpServletRequest request,
						HttpServletResponse response, Object handler,
						ModelAndView modelAndView) throws Exception {
					if (modelAndView != null
							&& modelAndView.getView() instanceof RedirectView) {
						RedirectView redirect = (RedirectView) modelAndView.getView();
						String url = redirect.getUrl();
						if (url.contains("code=") || url.contains("error=")) {
							HttpSession session = request.getSession(false);
							if (session != null) {
								session.invalidate();
							}
						}
					}
				}
			});
		}

This might be a silly question . But how do I attach this handler interceptor via xml config? my organization uses <oauth2:authorization-server... and it's either that or I migrate everything to annotations. Currently I just placed a filter at the top of the chain that intercepts the auth code response and invalidates the session. However it seems a bit hacky to me.

So what's the correct and better approach to fix this behaviour? The HandlerInterceptor or the SessionInvalidationOauth2GrantAspect?


refactor: git-like usage commands

closes #333
Some screenshots of the new usage:
new-account command:

account command:

It seems a bit more usable/cleaner at first sight, but also it showcases the types of entities that are involved a little less.

Agreed - but I think we can showcase the entities via the client library interface and CLI could still be a bit more "customized" to make it more user friendly.

I'd change --acc-type to --type in the new-account command, since it feels a bit redundant.

As I mentioned in https://github.com/0xPolygonMiden/miden-client/issues/333#issuecomment-2106055289, I'd probably split this into two commands new-wallet and new-faucet. This way, both commands would be simpler (in terms of options to chose from).


CPU 100% after upgrade to v 4.0.0

Problem
(X) bug report => please search github for a similar issue or PR before submitting

Current behavior
I am using:
Raspberry PI Zero W
connected to Modbus TCP (WIFI) Relay modules.
DietPI SW package is installed and updated
NPM version 5.6.0
Node-red version v0.18.4 (latest)

CPU USAGE 100%
After upgrading to version v4.0.0 I get allmost 100% CPU usage all the time.
I reinstalled version v3.6.1 and CPU usage is around 25%.
Your Environment
Please tell us about your environment:
(X) I am using just the Node-RED package and got modbus-serial installed with it

( ) I have installed modbus-serial global from source (using git clone)

( ) I have installed modbus-serial as a global package (using npm i -g)

Device :
    ( ) macOS: v
    () Linux: v
    ( ) Windows: v
    ( ) Raspbian: v
    (X) Other: Raspberry PI Zero W
        Name: DietPI (based on Raspbian Stretch if I understand correctly)
        Version:  v6.12

Description of the connecting Modbus system:
    Name : Denkovi Modbus WIFI Relay board
    Version: latest
    Vendor : Denkovi
    Link : https://

node-red-contrib-modbus version: ``
    latest = 4.0.0.

Node: (min. 8.x)
node --version = v8.11.3 (LTS)

It is a major version. Please, check your flows and maybe you have to update or replace some nodes. Node-RED did not update all changes automatically. Otherwise, I need some logs or information what is the memory consumption about, please.

It could help to get the flow.

Please, test with nodejs v10 and node-RED v0.19!

Hi,
I upgraded everything to latest:
node-red: v0.19.2
node.js: v10.9.0
node-red-contrib-modbus: v4.0.0
My findings are:

I started fresh without any nodes. Created ONLY modbus-server node (both flex and simple), and everytime I create a modbus server on port 502 node-red crashes!
When creating modbus server with port 10502 is working OK (no crash).

CPU usage is OK, WHEN NOT USING node-red modbus server.

when using modbus server in node-red and I am doing also reading/writing modbus from within node-red, CPU usage is high (100%) + memory leaks are high.

when creating modbus server on different - dislocated machine (not on RPI Zero, where node-red is operating), and I am using only reading/writing in node-red to dislocated modbus server, CPU usage is OK (avg 15%), also I dont see high memory leaks at the moment.

All in all, I think there is a problem in node-red handling modbus server node (both flex and simple).
Best regards.

Just an update with running bash command: netstat --tcp --listening --programs --numeric
Checking to see if port 502 is reserved or used by another process.
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 <IP_ADDRESS>:1880            <IP_ADDRESS>:*               LISTEN      13104/node-red
tcp        0      0 <IP_ADDRESS>:1883            <IP_ADDRESS>:*               LISTEN      1074/mosquitto
tcp        0      0 <IP_ADDRESS>:443             <IP_ADDRESS>:*               LISTEN      474/vpnserver
tcp        0      0 <IP_ADDRESS>:222             <IP_ADDRESS>:*               LISTEN      314/sshd
tcp        0      0 <IP_ADDRESS>:992             <IP_ADDRESS>:*               LISTEN      474/vpnserver
tcp        0      0 <IP_ADDRESS>:1443            <IP_ADDRESS>:*               LISTEN      474/vpnserver
tcp        0      0 <IP_ADDRESS>:1194            <IP_ADDRESS>:*               LISTEN      474/vpnserver
tcp        0      0 <IP_ADDRESS>:5555            <IP_ADDRESS>:*               LISTEN      474/vpnserver
tcp6       0      0 :::1883                 :::*                    LISTEN      1074/mosquitto
tcp6       0      0 :::443                  :::*                    LISTEN      474/vpnserver
tcp6       0      0 :::222                  :::*                    LISTEN      314/sshd
tcp6       0      0 :::992                  :::*                    LISTEN      474/vpnserver
tcp6       0      0 :::1443                 :::*                    LISTEN      474/vpnserver
tcp6       0      0 :::1194                 :::*                    LISTEN      474/vpnserver
tcp6       0      0 :::5555                 :::*                    LISTEN      474/vpnserver

502 is a well known port on Unix / Linux and is just to use with root or sudo running node-red - to use sudo for node-red means every user on website of node-red is sudo/root
Sent with GitHawk

Is the point 4 also v4.0.0 in you listing?
Sent with GitHawk

I’ll test it with PIW in the next few days.
Sent with GitHawk

Yes, everything on v4.0.0
Before upgrade I could use port TCP 502 for modbus server without any problem!

25 Aug 11:35:42 - [red] Uncaught Exception:
25 Aug 11:35:42 - Error: listen EACCES <IP_ADDRESS>:502

when using modbus server in node-red and I am doing also reading/writing modbus from within node-red, CPU usage is high (100%) + memory leaks are high.

@jinx17 could you find a memory leak or is it just a guess?

Error when crash occurs:
24 Aug 20:41:30 - [red] Uncaught Exception:
24 Aug 20:41:30 - Error: listen EACCES <IP_ADDRESS>:502
at Server.setupListenHandle [as _listen2] (net.js:1317:19)
at listenInCluster (net.js:1382:12)
node-red.service: Main process exited, code=exited, status=1/FAILURE

Memory leak is educated guess. I find memory rises very quickly over an hour or two from around 100MB to 160 or more. The same behaviour where memory rises from 100MB to 450MB in about 12 hours was observed all the time this week (so it is experience with same settings but before upgrade).
Now, when I am using dislocated modbus server, memory usage is pretty stable around 110MB for 3 hours now.

@jinx17 some more news here?

Hi Klaus,
I had to fund another sollution - using modbus server on another device. It
was simply too many problems and instabillity with CPU usage and memory
leaks. I am only using only modbus client on PI-zero now, and its working
good.
BR,
Gregor
V V pet., 9. nov. 2018 ob 05:48 je oseba Klaus Landsdorf <
<EMAIL_ADDRESS>napisala:

@jinx17 https://github.com/jinx17 some more news here?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/biancode/node-red-contrib-modbus/issues/109#issuecomment-437118998,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AZXe38syq5ej4ok4_0_BgoLh278gMy53ks5utID-gaJpZM4WJxdk
.

--
Lep pozdrav,
Gregor Jenko
031/77.55.33
TechnoSoft d.o.o.
Lipa 22
3320 Velenje
t: 03/897.5000
www.technosoft.si


Fix the stop command hanging the daemon instead of existing

Because as soon as we do a release, I have forgotten something small but critical.
@nesquena I have updated the version in preparation for release v0.6.1, which should probably get released as soon as you are happy with this PR.

Pushed: https://rubygems.org/gems/gitdocs/versions/0.6.1


does not seem to be working with new dnd

Hi, i know it did work previously, however it seems like the timer on effects and the like don't seem to be counting down any more.
many thanks

What dnd5e and foundry version are you on? What other modules are you using?


[AIRFLOW-3220] Implement Instance Group Manager Operators for GCE

[AIRFLOW-3220] Implement Instance Group Manager Operators for GCE
There are two operators:

* GceInstanceTemplateCopy - existing template is copied with some
changes specified
* GceInstanceGroupManagerUpdateVersion - template is replaced in
the instance group manager with patch method

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@7df4405). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff            @@
##             master      #7   +/-   ##
========================================
  Coverage          ?   77.9%
========================================
  Files             ?     199
  Lines             ?   15957
  Branches          ?       0
========================================
  Hits              ?   12432
  Misses            ?    3525
  Partials          ?       0

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 7df4405...92bfdd3. Read the comment docs.

All comments addressed!

@TrevorEdwards - any chance for approving this one as well? I think the GCE team will need it some time in December, so it would be great if we can merge it quickly :)

Closing this PR, opening an Apache one


Remove Moq

Remove Moq and replace with an alternative mocking library, such as NSubstitute.
I had a quick look into this myself, but due to the way the test code is structured, Moq is everywhere.

I'll take a look at this one over the weekend

I already made a start on Wednesday and have got around to finishing it: #370


Difference between GroundingDINO and UniDetector.

I am a fresh hand for open-set OD. Now I try to learn the difference between your Grounding DINO with UniDetector. Both can implement open-set detection. I think the difference may be, for each dataset, you need to prompt the novel labels into the network for zero-shot, but the UniDetector inputs many prompts, not limited to the labels in each dataset. Besides, may you provide more insight on the contributions of GroundingDINO? The answer will be helpful to me. Thanks!

You can view our paper for more details. Our model supports any text inputs, which means you can detect everything you can think of. Moreover, we use grounded pre-training, which enables to detect the noun phrases in input sentences. It cannot be finished in the UniDetector.

I understand GroundingDINO's ability of grounding in the context and especially in REC tasks. Thanks for your great work and timely response.