Can not write to /var/jenkins_home/copy_reference_file.log

When using docker-compose up the running fails with
'''
~/Desktop/jenkinstest/course-jenkins-getting-started/dockers/compose$ docker-compose up
Starting compose_jenkins_1 ... done
Starting compose_mails_1   ... done
Attaching to compose_mails_1, compose_jenkins_1
mails_1    | 2022/03/18 14:41:48 Using in-memory storage
jenkins_1  | touch: cannot touch '/var/jenkins_home/copy_reference_file.log': Permission denied
mails_1    | 2022/03/18 14:41:48 [SMTP] Binding to address: <IP_ADDRESS>:1025
mails_1    | 2022/03/18 14:41:48 Serving under http://<IP_ADDRESS>:8025/
jenkins_1  | Can not write to /var/jenkins_home/copy_reference_file.log. Wrong volume permissions?
mails_1    | [HTTP] Binding to address: <IP_ADDRESS>:8025
'''
and a bunch of
'''
jenkins_1  | touch: cannot touch '/var/jenkins_home/copy_reference_file.log': Permission denied
jenkins_1  | Can not write to /var/jenkins_home/copy_reference_file.log. Wrong volume permissions?
'''
I have tried (for testing) to set the permissions of the folder to 777, not working either
'''
course-jenkins-getting-started/dockers/compose$ sudo chmod -R 755  jenkins_home_on_host
'''
NOT helping either:
course-jenkins-getting-started/dockers/compose$ sudo chown -R jenkins:jenkins jenkins_home_on_host
Seems a problem with the jenkins repo, but for using this tut/repo from g0t4, the tut here needs some additions described in the link below.
Details here: https://github.com/jenkinsci/docker/issues/177#issuecomment-451137786
... This does NOT help entirely either. Plugins will not load entirely.
Suggested work-around is to disable the folder binding in the docker-compose file and access the logs by entering the containers with "docker exec -it bla-bla".
'''
#volumes:
#- ./jenkins_home_on_host:/var/jenkins_home
'''

Which now after testing proves NOT to work either. Plugins will not load entirely.

Hi @itofficeeu
I've tried docker command first: docker run -d -p 8080:8080 -v jenkins_home:/var/jenkins_home jenkins/jenkins:lts
then I didn't remove the .jenkins folder under my home folder but simply continue to created a docker-compose.yml file and copied all of the content of the course's yml file, however I did need to change the jenkins version to a newer one as when I install the plugins, it all failed with error complaining the jenkins version, therefore, I gave the version that the requires for my case was to be lts rather the specified older version in your yml file. It works for me. Before you try again, remove the folder jenkins_home jenkins first then run the docker-compose up again.
Hope this is helpful.

Very kind of you, @YunjunWang, thanks. I will try that out next time I work with the tutorial.


Removes new line at EOF when file has been reformatted

Still seeing the behavior from https://github.com/jlongster/prettier/issues/55 and https://github.com/jlongster/prettier/pull/105
When formatting a file with the JSPrettier package in Sublime it removes the new line if any reformatting has been done. Looks they are using the latest version of prettier (https://github.com/jonlabelle/SublimeJsPrettier/blob/master/package.json).
Would this be specific to the plugin?

https://packagecontrol.io/ is down so I can't install it right now, but it's likely an issue with the package.

Note that this is using the globally installed version of prettier. If you do
npm ls -g prettier

you can see what version it uses.

Looks like I'm using<EMAIL_ADDRESS>I'll do some more digging to see if I can repro without this package

Thank you!

If you can run prettier file.js --write and repro locally that would be useful as well.

You're absolutely right, running from the command line works fine, but repros with the package. Sorry for erroneous issue!

Thanks for raising it, we need to make sure that the prettier integrations are of high quality, this is a big part of the experience :)


Project-level Optional Property; Keyboard Language

There's no tooltip for Keyboard Language.  Takeshi Adachi has written this text for the wiki page.
"Provides the ability to give the user keyboard language support when they are required to enter text on an interactive page. E.g., if a language other than English is selected, a pop-up dialog of special characters (appropriate to the chosen language) will appear when the user enters a text box."
Could this be added as a tooltip?

@JMarco27 Thank you. Yes I will add this as a tooltip.


[Docs] Issue template for blog posts

Current State:
See these issue templates? We’re missing one for creating a blog post.
Desired State:
Copy the issue template format from layer5io/layer5 repo and paste into a new issue template in meshery/meshery.io, making changes as appropriate?

Contributor Resources

Meshery documentation site
Meshery documentation source
Instructions for contributing to documentation

Hi @leecalcote
Could you please assign this to me, would love to work on it.

@hymmns so sorry... we just missed you. Sadam Mohamed volunteered just a bit earlier. He'll need to comment on this issue in order to have it assigned, though.

@hymmns, are you Taiwo (is that your name)? I'm just trying to ensure that I start to consider for you going forward and trying to align a Slack name to GitHub face, so to speak.

Yes @leecalcote
My name is Taiwo

https://github.com/meshery/meshery.io/pull/1966


Checking is AWS env var is available before starting app.

CC @ktp242
I think the other PRs included if (!process.env.AWS_LAMBDA_FUNCTION_NAME). If the variable is undefined it will run through the code. So I think the ! is actually not needed.
Also updated app.js and index.js to use the standard style.

Updated and also updated the README to include instructions on how to separately run the lambda locally and the API locally.


sage: don't test for Cython source code in tracebacks (temporarily)

Motivation for this change
To emit better tracebacks, IPython 8 (#154969) parses Python files using the ast module (via the stack_data package). Since Cython is a superset of Python, this results in no Cython code being printed in tracebacks. Fixing this properly is tracked in https://github.com/alexmojaki/stack_data/issues/21, but for now we just disable the corresponding test. An alternative would be to revert IPython's IPython/core/ultratb.py, but this would need to be Sage-specific (since it would worsen tracebacks for pure Python code).
Sage tracks the IPython 8 upgrade at https://trac.sagemath.org/ticket/33170, a ticket which also includes two minor test changes. I added those to this PR as well.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Thanks for merging! This will be a temporary fix indeed, since upstream IPython just fixed this properly. But the fix will have to go through staging, so it's great to have this one merged already.

#160031 removes this patch.


Pallas Broken after making JAX-Triton calls serializable update

The new update has broken pallas again with the error shown below. I have tried updating jax / jaxlib to head and the issue persists.
I0624 11:43:47.866600<PHONE_NUMBER>78464 xla_bridge.py:568] Unable to initialize backend 'rocm': NOT_FOUND: Could not find registered platform with name: "rocm". Available platform names are: CUDA Interpreter Host
I0624 11:43:47.866749<PHONE_NUMBER>78464 xla_bridge.py:568] Unable to initialize backend 'tpu': module 'jaxlib.xla_extension' has no attribute 'get_tpu_client'
I0624 11:43:47.866775<PHONE_NUMBER>78464 xla_bridge.py:568] Unable to initialize backend 'plugin': xla_extension has no attributes named get_plugin_device_client. Compile TensorFlow with //tensorflow/compiler/xla/python:enable_plugin_device set to true (defaults to false) to enable this.
(4, 8)
Traceback (most recent call last):
  File "/media/adam/shared_drive/PycharmProjects/triton_test/pallas_test.py", line 231, in <module>
    app.run(main)
  File "/home/adam/anaconda3/envs/triton_test/lib/python3.10/site-packages/absl/app.py", line 308, in run
    _run_main(main, args)
  File "/home/adam/anaconda3/envs/triton_test/lib/python3.10/site-packages/absl/app.py", line 254, in _run_main
    sys.exit(main(argv))
  File "/media/adam/shared_drive/PycharmProjects/triton_test/pallas_test.py", line 226, in main
    print(pl.pallas_call(kernel1, out_shape=out_shape, grid=grid)(x, y))
  File "/home/adam/Downloads/jax-triton/jax_triton/pallas/pallas_call.py", line 352, in wrapped
    out_flat = pallas_call_p.bind(
jax._src.source_info_util.JaxStackTraceBeforeTransformation: TypeError: __init__(): incompatible constructor arguments. The following argument types are supported:
    1. jaxlib.cuda._triton.TritonKernel(arg0: str, arg1: str, arg2: int, arg3: int)

pallas_error.txt

Could you provide your JAX Triton and JAXlib versions?

Ok, so I have gone back through and created a fresh install.
jax / jaxlib 0.4.12 with cuda 11 work. jax / jaxlib 0.4.13 is where the problem starts (but these versions work for code prior to the serialisation change commit f947255bc2c3dfa3d21e59c01e7f3b7b78e5e02b).

I'm having the same issue.

I haven't been able to reproduce this but I used jaxlib-0.4.14 from the nightlies: https://storage.googleapis.com/jax-releases/jaxlib_nightly_cuda12_releases.html. (Specifically the 0705 one).

Are you able to try a nightly?


Add SymfonyInsight stars badge, run [SymfonyInsight sensiolabs amo chrome-web-store redmine spigetratings vaadin-directory visualstudiomarketplacerating wordpress]

Closes #1433 and fixes #2928

Adds a new Stars badge for SymfonyInsight (formerly known as Sensiolabs)
Fixes schema validation issue for projects that haven't been analyzed recently (#2928)
Makes the max star value configurable in the starRating function in lib/text-formatters.js
Leverages the new canonical redirect functionality added in #2939 to handle redirecting the old sensiolabs/i badge paths
Refactors the SymfonyInsight badges into separate service classes, and moves the services & tests into separate files

Warnings

:warning:

:books: Remember to ensure any changes to serverSecrets in services/symfony/symfony-test-helpers.js are reflected in the server secrets documentation

:warning:

:books: Remember to ensure any changes to serverSecrets in services/symfony/symfony-insight-base.js are reflected in the server secrets documentation

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @calebcartwright!

  Generated by :no_entry_sign: dangerJS against 8880323ce381793d77315b580b7108dd369f8fb3

I've removed a couple of the tests (although I've kept the mocked 404 and 401 tests in place) and made a minor update to address the issue described in #2928


Fixes typo of "informaiton" to "information"

Fixes typo of "informaiton" to "information" under Usage section.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

NIce catch @valenzsa - Thanks for fixing it, and congratulations on your first contribution to freeCodeCamp!


Difference in how targets are handled when -resultBundlePath is used

This is very likely an Xcode thing.
I've noticed that when you build with Xcode or with xcodebuild using the -resultBundlePath, you get different output regarding targets.
More specifically, when building with Xcode, target names with the hash show up in the signature. However when xcodebuild with -resultBundlePath, the signature is empty. The target name is in the title showing up as "Target XYZ" whereas when running from Xcode it would show up as "Build target XYZ".
I wrote a tool which works with this one to better analyze the numbers, which is why I ran across this ... my code broke. I worked around it, but I wonder if you noticed this before.
Note that I could not check running xcodebuild without the -resultBundlePath to verify if the issue is actually running xcodebuild or -resultBundlePath due to #16.

Hi I fixed this big in this PR https://github.com/spotify/XCLogParser/pull/58 it will be release v0.2.4


Setting to include import statements in script mode

Resolved with https://github.com/BrendanParmer/NodeToPython/pull/117


[CTIS] New child schooling and child age indicators for Wave 12

Description
Add new indicators to both API and contingency tables at FB's request.
Add new variable creation function for non-schooling, non-vaccine children-related items (e.g. age breakdown).
Changelog

binary.R
contingency_indicators.R
variables.R
responses.R

@krivard This is ready to merge and deploy


Updates docs to v0.3.0 CLI usage

Signed-off-by: Adrian Cole<EMAIL_ADDRESS>

merging this because the site is busted until I do! any polish happy to do tomorrow

👍


fix: allow dashboard buttons to wrap

Description
Allows the buttons Send/Receive/Trade to wrap while remaining centered on the Dashboard when needed (longer text buttons in translations).

Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[x] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)

closes #4376
Risk
None.

Testing
Check the buttons in various languages and low/high width resolutions to be sure they always display properly.

Engineering
☝

Operations
☝

Screenshots (if applicable)
EN:
DE:
ES:
FR:
PT:
TR:
UK:
RU:

@0xApotheosis Np, the secondary nav/tabs one is actually supposed to be a scrollable horizontal area I think. The overflow is supposed to indicate this I think 🤔
On mobile the touch/scroll works well but apparently it's broken in Chrome (I've only managed to scroll by using a mouse middle click and to the "smart" scroll or by switching to Mobile preview in the dev tools as it simulates touch scroll).
On Firefox an horizontal scrollbar shows up when the overflow happens, but a vertical scrollbar also shows up when no horizontal scrollbar is needed which is not so great visually. So there might be some things to fix indeed here, maybe @reallybeard has some input about this:
Firefox with enough horizontal space:

Firefox without enough horizonal space:

@0xApotheosis Np, the secondary nav/tabs one is actually supposed to be a scrollable horizontal area I think. The overflow is supposed to indicate this I think 🤔
On mobile the touch/scroll works well but apparently it's broken in Chrome (I've only managed to scroll by using a mouse middle click and to the "smart" scroll or by switching to Mobile preview in the dev tools as it simulates touch scroll).
On Firefox an horizontal scrollbar shows up when the overflow happens, but a vertical scrollbar also shows up when no horizontal scrollbar is needed which is not so great visually. So there might be some things to fix indeed here, maybe @reallybeard has some input about this:
Firefox with enough horizontal space:
Firefox without enough horizonal space:

There should be no scroll bars I think we might only be targeting WebKit but what you said is correct.
Should scroll horizontally and not vertically. Shouldn’t see scroll bar on either of them though we are hiding for WebKit but not moz based browsers.

Should scroll horizontally and not vertically. Shouldn’t see scroll bar on either of them though we are hiding for WebKit but not moz based browsers.

At least it's functional with the scrollbar, but yeah if there's a way to allow scrolling through click and drag on Browsers too, I think it's still kinda intuitive. But maybe a visual cue like a small alpha transparent gradient on the right/left to let the user know it's not just "cut" or broken might help... as as Apotheosis said wrap them, but it might be a bit of a long list for small resolution, I kinda like that scrollable tabs :D


Remove Medical history from patient registration since

We can remove it as it is medical information and overlaps with clinical data  in the encounter

Hi, Can I work on this issue or are they intended for only Core Team Members? Thanks

@srijantrpth, Yes, it’s only for core team members. 😊


Job spec cli

/retest

just testing, do not merge

@flacatus Will you be doing anything with this PR? If not, can you close it?


make allow_privileged configurable at cluster startup time (providers using salt)

For providers that use salt, currently the way to enable privileged containers is to check out k8s from source, manually edit a salt config, build tarballs (which is very slow, even just make quick-release), and start.  I propose introducing an env var so that this property can be toggled at cluster startup time on a k8s binary release.
I have a draft of said changed here (see top portion, this branch includes some unrelated changes):

https://github.com/GoogleCloudPlatform/kubernetes/compare/master...pwais:pwais_run_proxy_on_master_and_make_priv_nicer_0.18.1

Does this sound like a good idea?  If so, I'd be happy to put together a pull request based on my draft if that helps.

Seems reasonable.
Eventually we should replace this flag with an admission control policy. cc @csrwng
cc @thockin @evandbrown

FWIW I have ported the old branch to a new branch based upon master (~v1.0 at the time of porting) and verified the change still works in GCE.  Here is the new branch/diff: https://github.com/GoogleCloudPlatform/kubernetes/compare/master...pwais:pwais_run_proxy_on_master_and_make_priv_nicer_1.0_master

We enabled privileged containers by default for 1.0.
I don't think we should do something custom for this one option. We should fix the way we configure our components.

Actuallym we didn't in the end we didn't get to hammer it out enough before
Dawn had to take off.  :(
On Wed, Jul 22, 2015 at 10:34 PM, Brian Grant<EMAIL_ADDRESS>wrote:

We enabled privileged containers by default for 1.0.
I don't think we should do something custom for this one option. We should
fix the way we configure our components.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/9626#issuecomment-123977539
.

I agree with the "we should do a general fix", but I think we should leave this open until we can close it with an "obsoleted by"

Ok, sorry. I thought that change went in. :-(

Agree that this branch is a bit of an ugly hack-- it's the minimal work to propagate the flag to the bash provider (~configuration) scripts while keeping with how other salt parameters work.  Mainly trying to create a paper trail here since I spent a lot of time looking for prior work on this issue and found none.  Yes, please do cite this issue when the nicer fix hits a release! <3

#11027 was the attempt right before v1.0, FWIW. But #11027 would be a breaking behavioral change now for upgrades, so I think we'd need to be a little bit more careful to distinguish new clusters versus existing clusters.

Yeah, there's some trailblazing to be done here.  Good point Zach.

Privileged is enabled by default. Control over that is superseded by PodSecurityPolicy.


Update CODEOWNERS for Azure communication serices Phone Numbers and SMS.

Adding specific code owners for communication/azure-communication-phonenumbers and communication/azure-communication-sms.

/check-enforcer reset

/check-enforcer override


user output in slicing

First implementation of #158
Somehow in the to_json() function the arrays that are used there are bypassing the check _convert_to_list_if_needed
So we get "not JSON serialisable" errors.
Maybe @jtorhoff or @budmil ju can have a look on that?
But to dict() is working

I can't figure out why is failing..

Hey I changed a couple of things and it works now, also added accuracy score to the output so this PR also resolves #157. IMO it would be easier to use a JSON library that can serialize objects recursively but for now it works fine.


Not receiving some MSGs

I have a problem that some messages are not arriving, and some arrive normal, someone with the same problem?

This problem is 100% related to the phone Internet connection.
Make sure that you have stady and fast connection in your phone.
Regard

https://github.com/Rhymen/go-whatsapp/issues/351#issue-611351119
Maybe it's related to my issue?

#351 (comment)
Maybe it's related to my issue?

Please share your logs...

I think you WhatsApp in asleep mode.

thanks everyone, I resolved this.

How?
On Fri, 5 Jun 2020, 2:20 pm Mateus Pilo Dias<EMAIL_ADDRESS>wrote:

thanks everyone, I resolved this.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Rhymen/go-whatsapp/issues/366#issuecomment-639420590,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABDLT2YNESA5FBUO2LSDED3RVDIHDANCNFSM4NF4MKFQ
.


Comparison with goreplay

I'm not understanding the high-level differences between this and goreplay. They seem to occupy most of the same problem space. Can someone explain if and how they differ in their use cases?

I think the idea is the same. I didn't dig into goreplay but something I found out:

goreplay implemented in go not sure if it can be used for other languages
The example doesn't show how to support Http.
It supports more protocol such as binary protocol.

For 3, we are going to support that soon. To share some idea how we want to support different protocol:

Based on first a few bytes, we can decide if it's CONNECT or any other Http method or random bytes.
If it's CONNECT, establish TCP connection
If it's HTTP METHOD, decode using HttpDecoder
If it not 2 or 3, then store whatever bytes somewhere.


Create qwe

jjj

Collaborator: Review for this pull request was created. Link to review

Collaborator cannot find remote user mapping for pull request creator, review created by system administrator

Corresponding review in Collaborator has been completed.Author: Administrator.Reviewer: test1.Observer: test2.


Crash on 404

Hey! I've been playing around with my Psion 5mx to get it connected, and also found your proxy which is really awesome. I'd like to add it to my instructions since it can be run on the same raspberry pi that I use to connect to the internet in the first place. It's a bit slow on a Raspberry Pi 3B but let's say that that is part of the retro experience 😉
The only issue I run into is that if I enter a non-existing website, the proxy crashes.
me@MacBook-Air-van-Bjorn retro-proxy % yarn start
yarn run v1.22.21
$ node ./
allow-list [
  'kdelaney.neocities.org',
  'sgi.neocities.org',
  'web.archive.org',
  'toastytech.com',
  'www.theoldrobots.com',
  'retro.hackaday.com',
  'sgi.neocities.org'
]
Listening on port 3000, CSS is disabled, images are compressed

/Users/me/retro-proxy/retro-proxy/node_modules/node-fetch/lib/index.js:1461
			reject(new FetchError(`request to ${request.url} failed, reason: ${err.message}`, 'system', err));
			       ^
FetchError: request to http://gittttthub.org/ failed, reason: getaddrinfo ENOTFOUND gittttthub.org
    at ClientRequest.<anonymous> (/Users/me/retro-proxy/retro-proxy/node_modules/node-fetch/lib/index.js:1461:11)
    at ClientRequest.emit (node:events:519:28)
    at Socket.socketErrorListener (node:_http_client:495:9)
    at Socket.emit (node:events:519:28)
    at emitErrorNT (node:internal/streams/destroy:169:8)
    at emitErrorCloseNT (node:internal/streams/destroy:128:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  type: 'system',
  errno: 'ENOTFOUND',
  code: 'ENOTFOUND'
}

Node.js v21.5.0
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Is this an easy fix maybe?
Also, I've tried to find out how to run this as a service or something, but couldn't find if that works with yarn start. Not a linux expert so to say :)

I have just pushed a fix to send a 502 error page when the fetch fails instead of crashing.
Technically, a 404 is received when the site was found, but the page was not. That worked already. In this case, the site itself was not found, which is a different kind of error that was not being handled.


kitti bin file out of point cloud range

I train a dynamic voxelize model on kitti dataset. And get follwoing error when preparing point cloud data. In file transforms_3d.py, the points_mask get all False after points.in_range_3d(self.pcd_range).
dynamic_voxelize(points, coors, voxel_size, coors_range, 3)
RuntimeError: CUDA error: invalid configuration argument
CUDA kernel errors might be asynchronously reported at some other API call,so the stacktrace below might be incorrect.
For debugging consider passing CUDA_LAUNCH_BLOCKING=1.

My mmdetection3d version is 0.15.0.

Please follow the issue template, did  you make any changes in config or code?

Close due to inactivity.


write README

explain how to start the stack, what to do with the influxdb token, how to use the stack , ...

done, I've written the documentation.
@ArnabPurohit you should tour the whole organisation and review issues.
@nchanon FYI


added diacritcs attribute to made input diacritics insensitive

added a diacritcs attribute that when is set true made the input diacritcs insentitive (the view still keeps the diacritcs)

Pull Request Test Coverage Report for Build 75

1 of 2 (50.0%)  changed or added relevant lines in 1 file are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-1.07%) to 68.317%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/components/VueBootstrapTypeaheadList.vue
1
2
50.0%

Files with Coverage Reduction
New Missed Lines
%

src/components/VueBootstrapTypeaheadList.vue
2
83.78%

Totals

Change from base Build 38:
-1.07%

Covered Lines:
47

Relevant Lines:
69

💛  - Coveralls

This repo seems to no longer maintained. I've forked the repo here and have been maintaining it as best I can.
I just pushed a release that I think should solve the problem of matching diacritics (accents, etc). Check out v2.6.1 here!


drivers: serial: Add Driver for CDNS UART IP6528

Adding New Serial/UART driver for Cadence UART IP6528.
Signed-off-by: Ravik Hasija<EMAIL_ADDRESS>

Please remove the merge commit.

Updated. With only commit for driver changes. Thanks.

I know that some of this is some lines of code internally that I wrote (that got considered to upstreamed), but the interrupts we're not fully tested and verified. Have you verified it with CONFIG_UART_INTERRUPT_DRIVEN

I know that some of this is some lines of code internally that I wrote (that got considered to upstreamed), but the interrupts we're not fully tested and verified. Have you verified it with CONFIG_UART_INTERRUPT_DRIVEN

Yes, we have tests that to verify the interrupts work correctly.

@XenuIsWatching / @dcpleung Thanks for the in-depth review. I have address all the previous comments, and updated the driver code to be in line with recent changes. Please have a look & let me know. Thanks.

@dcpleung Thanks for approving the diff yesterday. Current changes just merge the uart_cdns_registers.h into uart_cdns.h. Thanks.


SOAP to REST conversion with complexType Lists getting converted to a string type in the swagger

Hi,
When we try to create REST API by referencing a WSDL file/URL some of the data types are not getting converted properly in the swagger definition. Due to this when we try to build the SDK created for this API there are errors with missing classes.
complexType definition of Lists in the WSDL file with an Array are getting converted to a string type in the swagger, which should ideally be converted into an object type.
For example,
<xs:complexType name="CustomSearchOrderByList">
  <xs:complexContent>
		<xs:restriction base="soapenc:Array">
			<xs:sequence>
				<xs:element name="OrderByStruct" type="tns:CustomSearchOrderByStruct" minOccurs="0" maxOccurs="unbounded"/>
			</xs:sequence>
			<xs:attribute ref="soapenc:arrayType"/>
		</xs:restriction>
	</xs:complexContent>
</xs:complexType>

CustomSearchOrderByList complex type is converted as the following in the swagger definition generated for the API.
CustomSearchOrderByList:
    type: string
    properties:
      OrderByStruct:
        type: array
        items:
          $ref: "#/definitions/CustomSearchOrderByStruct"
    xml:
      namespace: "http://www.w3.org/2001/XMLSchema"
      prefix: xs

Since the type: string there is no object getting created for this complex type and thus gives
"Class not found" errors when building the SDK of the API.

Tagging https://github.com/wso2/product-apim/issues/7130

Closing as SOAP to REST feature is to be deprecated from apim-4.1.0


save audios here as well

This should save the audio files locally here
Signed-off-by: Arnav Gupta<EMAIL_ADDRESS>

Merged it but build is failing at the moment.

https://fossasia.slack.com/messages/app-dev/

Can you give me write access to this?
I can't test the travis builds in isolation.
I'll be better if I can push myself and ammend commits if needed.
On Mon, May 30, 2016, 12:02 Mario Behling<EMAIL_ADDRESS>wrote:

https://fossasia.slack.com/messages/app-dev/
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/OpenTechSummit/open-event-scraper/pull/31#issuecomment-222420966,
or mute the thread
https://github.com/notifications/unsubscribe/ABQ_yoY6tUw-QDIwk8EsZ01s6Aqwyx9Fks5qGoRtgaJpZM4IpeIu
.

Done.


show organization link for org. owner in public dashboard dropdown

close #4400
the problem with these two dropdowns is that they are created differently, one model (dashboard) comes from the window.user_data which is exposed in the rails view as this:
var user_data = <%= safe_js_object current_user.data.to_json %>;

the other model (public dashboard) comes from the authenticated user as this:
var user = new cdb.admin.User(authenticatedUser.attributes);

these two models carry different attributes thus the specific _isOrgAdmin
CR @CartoDB/frontend @viddo

Adding myself as a watcher, I reported to Maria that these options appear differently and was wondering about consistency.  I'll need to know if/when these options are changed in a future milestone so that I can update the doc accordingly.

alright! in the so I modified the api/user_controller to return the needed info for the isOrgAdmin to work plus replicated some methods from the model (upgrade_url) https://github.com/CartoDB/cartodb/blob/4400-org_public_dropdown/app/controllers/carto/api/users_controller.rb#L64-L92
it would be great for some @CartoDB/backend to review this

Being a url that usually points to Central looks ok

k, going through the hound madness and merging :disappointed:

bump!

I'll try to make it fit while work on other feature

the bug is solved but I cannot invest time in fixing it properly, as per conversation with @xavijam I'm closing the PR but leaving the branch open


update to 1.3.1

contourpy 1.3.1
Destination channel: main
Links

PKG-6199
https://github.com/contourpy/contourpy/tree/v1.3.1

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_868am41cmt/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:53: invalid_url: https://contourpy.readthedocs.io : Not reachable: 403
===== Final Report: =====
0 Errors and 1 Warning were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_c4hp7iz822/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:53: invalid_url: https://contourpy.readthedocs.io : Not reachable: 403
===== Final Report: =====
0 Errors and 1 Warning were found


[WIP] Feature/115

I would set it in WIP for now, because i assume it's not done and need some more improvements, please take a look and tell me if i'm implementing it correctly or not.
Remarks i have :

The jsonnetfile example you published on the issue doesn't contains enough information as specified in DependencyManagementFile.
As i'm supposed to be unfamiliar with Jsonnetfile manifests file, can you show example of jsonnetfile.json as manifest file in a project rather than the example you mentionned.

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

| The jsonnetfile example you published on the issue doesn't contains enough information as specified in DependencyManagementFile interface.
Correct. We're actually working on simplifying this part of the schema so some of those fields are deprecated. Unfortunately, my NodeJS code generation doesn't support deprecated annotations yet. Still trying to figure out what to do there.

Thanks @Redaloukil for the PR!


future: hint need_preempt() accordingly to SEASTAR_DEBUG

Although seastar::need_preempt() is really small in terms of code footprint, it's also frequently used with no code differences between occurrences. Not surprisingly compilers might consider it as a candidate to actually not inline. Moreover, GCC 8.1.0 on Ubuntu has failed to propagate the branch prediction hinting present in the definition:
inline bool need_preempt() noexcept {
    // ...
    return __builtin_expect(head != tail, false);
}

over function's callers.
The topic whether wrapping __builtin_expect() inside inlineable function stops the propagation was discussed on Stack Overflow (see https://stackoverflow.com/a/34427803) but without conclusion for GCC (though Clang forgets it for sure). However, objdump shows the hint has been lost:
  # fragment of crimson-osd's hot path: call the future-returning
  # `PGBackend::read()` and schedule a continuation with `then()`.
   This might have some impact on CPU's frontend but for sure makes reading assembler a little bit easier as humans are much slower with resteers than any CPU. That's also the reason why the hint value depends on SEASTAR_DEBUG.
Signed-off-by: Radoslaw Zarzynski<EMAIL_ADDRESS>

also tested with GCC 9.2
before the change:
(gdb) disass need_preempt
Dump of assembler code for function seastar::need_preempt():
=> 0x0000555555630f90 <+0>:     mov    $0xffffffffffffed80,%rax
   0x0000555555630f97 <+7>:     mov    %fs:(%rax),%rax
   0x0000555555630f9b <+11>:    mov    (%rax),%edx
   0x0000555555630f9d <+13>:    mov    0x4(%rax),%eax
   0x0000555555630fa0 <+16>:    cmp    %edx,%eax
   0x0000555555630fa2 <+18>:    setne  %al
   0x0000555555630fa5 <+21>:    retq
End of assembler dump.

so there is no jump at all! 🤣
on the caller site:
src/seastar/include/seastar/core/future.hh

1064                if (available() && !need_preempt()) {

   0x000055555571e452 <+290>:   jbe    0x55555571ee00 <seastar::reactor::configure(boost::program_options::variables_map)+2768>
   0x000055555571e458 <+296>:   callq  0x555555630f90 <seastar::need_preempt()>
=> 0x000055555571e45d <+301>:   test   %al,%al
   0x000055555571e45f <+303>:   jne    0x55555571e4e0 <seastar::reactor::configure(boost::program_options::variables_map)+432>
   0x000055555571e461 <+305>:   mov    -0x238(%rbp),%rax
   0x000055555571e468 <+312>:   mov    -0x240(%rbp),%rdx
   0x000055555571e46f <+319>:   cmp    $0x2,%rax /// inlined available(), compare _u.st with state::result (which is "2")

so the happy/predicted path is head == tail. this behavior is expected. but after applying
diff --git a/include/seastar/core/preempt.hh b/include/seastar/core/preempt.hh
index 722c7831..665a4050 100644
--- a/include/seastar/core/preempt.hh
+++ b/include/seastar/core/preempt.hh
@@ -49,7 +49,7 @@ inline bool need_preempt() noexcept {
     auto tail = np->tail.load(std::memory_order_relaxed);
     // Possible optimization: read head and tail in a single 64-bit load,
     // and find a funky way to compare the two 32-bit halves.
-    return __builtin_expect(head != tail, false);
+    return __builtin_expect(head != tail, true);
 #else
     return true;
 #endif

the compiler emits exactly the same assembly.

@tchaikov: need_preempt() looks exactly the same on my machine too (x86-64, Ubuntu, GCC 8.1.0).
After consideration I think we should keep  the __builtin_expect() there intact. The reason I see is combination of two factors:

depending on compiler, targeted microarchitecture (-march=) and so on conditional jump might be emitted instead of setne. There is long but interesting post on StackOverflow about cmov and differences between GCCs.
The macro targets situations when a compiler decides to actually not inline the function. However, such decisions are made on per-occurance basis – there could be places where inlining happens. I haven't verified propagation of the hint in "the reversed direction".


[BUG] datepicker field gives js error $(...).datepicker not defined

As the title says it, I get this $(...).datepicker not defined error, but I have published all the configs and should have the vendors and everything.
The datepicker.js script is loaded as well.
Laravel 5.4, with latest versions of Base/Cruds etc.

Same bug for me.

was just about to post this

I also have this bug !

Curious to know if it was caused maybe by this PR? https://github.com/Laravel-Backpack/CRUD/pull/408/commits/987f2d5644c851486387b2a21e8613271301cfa8
If you guys could reverse the change made in that commit, and see if it fixes it, then we know the culprit

Hi @OwenMelbz, thanks for you answer.
I reversed those changes, and I just have a little JS error : invalid date.
But the datepicker works fine !

Hi @OwenMelbz,
Thanks for your answer.
I made those changes and also tested your last fix.
The datepicker works fine but if I have an address field (with the autocomplete), this field doesn't works anymore.

Same problem here, and yes if I revert #408 it works

I have a similar issue. 'date' type works fine but when i use 'date_picker' (even when copy pasted from docs) chrome and firefox throws this error:
TypeError: $(...).datepicker is not a function[Learn More]

Have you tried this ? https://github.com/Laravel-Backpack/CRUD/pull/159#issuecomment-282491621

I had mentioned this error as PR in the Base Repo.
https://github.com/Laravel-Backpack/Base/pull/110
jQuery ui is not loaded.

Adding the jquery ui fixed it for me.

@skatika, yes. But it needs to be a part of the Base. And I've made the PR. But no response.

Well, this goes a little deeper.
First of all, the absence of jQuery UI is not the real issue here.
This all comes down to a bug in Bootstrap Datepicker which has been fixed since Oct 14, 2014.
As Backpack depends on AdminLTE (and its plugins) and AdminLTE uses outdated version of the Bootstrap Datepicker (issue already opened - https://github.com/almasaeed2010/AdminLTE/issues/1462) we're stuck with the buggy version right now.
I'm definitely against including jQuery UI as a fix for this issue, since it's not the right solution.
The question is, how to fix it?
@OwenMelbz @tabacitu - what's your strategy for stuff like this (outdated packages in dependencies)? Should we add our own separate version of said package (Bootstrap Datepicker in this case) and use that one, or should we wait for fix in AdminLTE and use some kind of workaround for now?
As for the workaround (or call it a hot-fix), the best I came up with is to change the #408 to:
if (jQuery.ui) {
    var datepicker = $.fn.datepicker.noConflict();
    $.fn.bootstrapDP = datepicker;
} else {
    $.fn.bootstrapDP = $.fn.datepicker;
}

It isn't ideal, since jQuery UI is not necessarily the only package causing conflicts here, but it's the only one that we know of right now.

@pavoltanuska , I love your reply, and I completely agree with your temporary fix. Would merge it right away if you can submit a PR.
I can't say I have "a strategy" for outdated packages in dependencies, but:

when laracasts/generators didn't update to L5.4 for weeks, I submitted a PR;
when prologue/alerts didn't support new Laravel versions, I took over maintaining it;
if AdminLTE doesn't update their dependencies for a while, I think we (the Backpack community) should totally help them out with PRs; I see you've already submitted an issue, kudos to you!
in this particular case, since we have a working fix (yours), and from what I can tell, it will be backwards-compatible when we update, I say let's include this fix into our datepicker field;

Cheers!

Alright, thanks for the insights and of course for all the work done @tabacitu !
I'll keep an eye on the AdminLTE's take on this issue and will let you guys know once it's fixed.

That would be great, thank you!
Just merged your PR, so let's close this bad boy. Cheers!

I can not used datetimepicker on mac os Is I used Modal BS. datetimepicker display background modal
Help Me.

@kanyapila-101 - at the very minimum we'd need to know if your debug console showed any errors (especially missing files, actual error logs and so forth) and a basic idea of your setup.
As it's not obviously related to this issue, it might be best to open another issue and start there.
If it relates to this issue we can always reference it back to here later.


Support describe table command without primary key information

usage: spark.sql("desc t").show()
Support for primary key will be done in another PR.

/run-all-tests

PTAL @ilovesoup @zhexuany

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

LGTM


CT skull segmentation fills hole in the skull

Holes are present in my CT scans. However, when I perform a skull segmentation, the holes get filled. Any way to resolve this issue?

Can you post some images? Otherwise I do not really understand what you mean.

The holes are present in images due to the operation that treats subdural hematoma, see attached image.
I suppose the holes get filled because the training data did not contain such images?

Thanks for the image. Your assumption is correct. You could do thresholding within the TotalSegmentator skull mask to get a segmentation where the hole is not filled.

Thank you for your answer. What exactly do you mean by "thresholding within the TotalSegmentator skull mask to get a segmentation" ?


💁 change the output of boundaries to be a list of indexes

What the pull request does
Rather than returning a matrix with x, y, z, boundaries return a vector of positions at which the boundaries are located.
Type of change

[x] :boom: Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] :book: This change requires a documentation update

Checklist

[ ] The changes are documented

[ ] The docstrings of the different functions describe the arguments, purpose, and behavior
[ ] There are examples in the documentation website

[ ] The changes are tested
[x] The changes do modify the behavior of the previously existing functions

@TanyaS08 putting you as reviewer as an FYI, but I think the current way to handle the output of boundaries can be improved

Codecov Report

Merging #26 (ec6d200) into main (a2b1744) will increase coverage by 2.81%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main      #26      +/-   ##
==========================================
+ Coverage   47.77%   50.58%   +2.81%
==========================================
  Files           7        7
  Lines          90       85       -5
==========================================
  Hits           43       43
+ Misses         47       42       -5

Flag
Coverage Δ

unittests
50.58% <0.00%> (+2.81%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

src/lib/boundaries.jl
0.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 a2b1744...ec6d200. Read the comment docs.


[Docker Hub] Notifications for images that will soon be marked as "inactive"

Tell us about your request
The ability for a free account owner on Docker Hub to receive notifications with the list of images that are set to expire (within their namespace).
Which service(s) is this request for?
Docker Hub
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
Docker Hub users on free accounts would like visibility into images within a given namespace that are set to expire (i.e. will be marked as "inactive") as a result of the new inactive image retention policy.
Are you currently working around the issue?
In order to view the last pushed info for a given tag, users are currently required to navigate to a Docker Hub repository to find this info.
Note: Docker offers unlimited image retention as a feature of the Pro and Team plans. Visit www.docker.com/pricing to view the available plans.
Additional context
NA

When you're writing programs, e.g., using docker-compose, you may be end up using other namespaces' docker containers. It would ideal to be able to figure out when other namespaces' images may expire as well.

Would also be nice to have notifications on image tag updates or any tag updates to latest image. This looks like it would be a nice feature for many interested


Change Admin account password

Can you help me how to change admin account password on koyeb? I used koyeb's Console with command vim Config.xml but it doesn't show up as your instructions.

Do you have screenshots of the operation?

Do you have screenshots of the operation?

Getting the information from the screenshot, the Config.xml is not found at the location of "/app/Config.xml".
The reason why the password can not be changed is that the container is running.
1.get the Config.xml from the link
2.create the Config.xml file in the koyeb and change the password.
3. excute the code: docker run -d -p 1066:1066 -v /root/Deploy/Config.xml:/app/Deploy/Config.xml  hanhongyong/ms365-e5-renew-x:latest

I followed the instructions, but password didn't change. /root/Deploy/Config.xml and /app/Deploy/Config.xml
both exist and contain the imported configuration.

please notice the warning!!!

the warning may be remind you that you have opened this file but did not close this file and a cache file was generated.
you need to delete the container and try to change the password.
Of course, you can modify the password in Config.xml according to the dockerfile file and create your own separate container, so you don't need to modify the password directly.
In fact, as long as you modify the mapped port to ensure that your domain name is not leaked, it is safe enough to not modify the login password

I deleted the .swp file and redeployed it to clean edit, but the result is still the same. Maybe I need to learn how to build my own dockerfile.

ok


Typo

"Grhave" is definitely not a word.

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[cb-ci-casc] Encrypt Kubernetes secrets with SOAPS

https://github.com/mozilla/sops

K8s secrets are simply not imported to the repo


Make support page more inspiring

Right now the /support comes from https://github.com/fluxcd/community/blob/main/SUPPORT.md
It'd be great if the companies who offer support could showcase their work and services somehow like https://linkerd.io/support-training/

Hello I want to work on this feature _ is it still Open to work?

That's great - thanks @Tarunbot ... let me know if I can help in any way. If you have ideas on how it could be done, maybe let's talk in #flux-contributors on CNCF Slack about it?

Hey @Tarunbot @dholbach please assign me this issue. Thanks.

@UnfixedSun and @Tarunbot Maybe you can collaborate on this issue?

hey, @dholbach I would like to work on this issue, I am looking forward to it. Could you assign this issue to me?

I'm starting work on this as well and will add a draft PR in a bit. If you want to collaborate, let's do it!


Allow env vars to be used in get and new

fixes https://github.com/Shopify/themekit/issues/639
Warn Checklist

[ ] This changes the interface and requires a Major/Minor version change.
[ ] I have :tophat:'d these changes by using the commands I changed by hand.
[ ] I have added a dependancy to the project.
[ ] I have considered any potential impact on node-themekit

The get command still replace the config.yml file with password environment variable.
When I ran:
THEMEKIT_PASSWORD=xxxxx theme get

I expect that config.yml keep with its content cause I don`t want to share passoword.

@tanema FYI the new version hasn't been published on homebrew yet.

@SimJoSt I know. I wait some time between main themekit release and package manager release


add renewal for scanner to prevent lease timeout

This change adds an option to Scan (Renew) that allows for renewal of scanners during periods of starvation to prevent lease timeout. Currently, we are renewing every lease timeout / 2 seconds (10s currently).

Just my 2c:
What's preventing scanning go routine to keep scanning and storing in a buffer end purposefully renewing the lease? I think the lease should only be renewed purposefully if you are actively scanning data.
Also, please make sure to not have this behavior by default as it might be unexpected for some users, as now their "periods of starvation" in client layer will cause leaked snanners within regionservers.

Just my 2c: What's preventing scanning go routine to keep scanning and storing in a buffer end purposefully renewing the lease? I think the lease should only be renewed purposefully if you are actively scanning data.
Also, please make sure to not have this behavior by default as it might be unexpected for some users, as now their "periods of starvation" in client layer will cause leaked snanners within regionservers.

Hey Andrey!
Yeah, I agree this shouldn't be enabled by default inside gohbase.
We have some needs for keeping a long lived scanner running. Buffering extra data is not great because of the extra memory use.

Hey Aaron!
Got it, it makes sense as an option. Just another alternative I'd suggest in those cases is just increasing lease timeout (server or client config). I would expect that eventually you would have to timeout anyway with your scan


ValueError: invalid literal for int() with base 10: 'cs'

$ paster --plugin=ckan celeryd run -c production.ini
WARNING: This function is deprecated. Use `paster jobs worker` instead.
No handlers could be found for logger "ckan.lib.celery_app"
[2017-10-16 17:21:47,113: WARNING/MainProcess] /usr/lib/ckan/default/local/lib/python2.7/site-packages/celery/apps/worker.py:161: CDeprecationWarning:
Starting from version 3.2 Celery will refuse to accept pickle by default.

The pickle serializer is a security concern as it may give attackers
the ability to execute any command.  It's important to secure
your broker from unauthorized access when using pickle, so we think
that enabling pickle should require a deliberate action and not be
the default choice.

If you depend on pickle then you should set a setting to disable this
warning and to be sure that everything will continue working
when you upgrade to Celery 3.2::

    CELERY_ACCEPT_CONTENT = ['pickle', 'json', 'msgpack', 'yaml']

You must only enable the serializers that you will actually use.

  warnings.warn(CDeprecationWarning(W_PICKLE_DEPRECATED))
[2017-10-16 17:21:47,123: ERROR/MainProcess] Unrecoverable error: ValueError("invalid literal for int() with base 10: 'cs'",)
Traceback (most recent call last):
  File "/usr/lib/ckan/default/local/lib/python2.7/site-packages/celery/worker/__init__.py", line 206, in start
    self.blueprint.start(self)
  File "/usr/lib/ckan/default/local/lib/python2.7/site-packages/celery/bootsteps.py", line 119, in start
    self.on_start()
  File "/usr/lib/ckan/default/local/lib/python2.7/site-packages/celery/apps/worker.py", line 169, in on_start
    string(self.colored.cyan(' \n', self.startup_info())),
  File "/usr/lib/ckan/default/local/lib/python2.7/site-packages/celery/apps/worker.py", line 230, in startup_info
    results=self.app.backend.as_uri(),
  File "/usr/lib/ckan/default/local/lib/python2.7/site-packages/celery/backends/base.py", line 118, in as_uri
    url = maybe_sanitize_url(self.url or '')
  File "/usr/lib/ckan/default/local/lib/python2.7/site-packages/kombu/utils/url.py", line 63, in maybe_sanitize_url
    return sanitize_url(url, mask)
  File "/usr/lib/ckan/default/local/lib/python2.7/site-packages/kombu/utils/url.py", line 58, in sanitize_url
    return as_url(*_parse_url(url), sanitize=True, mask=mask)
  File "/usr/lib/ckan/default/local/lib/python2.7/site-packages/kombu/utils/url.py", line 24, in _parse_url
    return (scheme, unquote(parts.hostname or '') or None, parts.port,
  File "/usr/lib/python2.7/urlparse.py", line 113, in port
    port = int(port, 10)
ValueError: invalid literal for int() with base 10: 'cs'

Hi @acer9997,
Thank you for submitting the issue. It looks like you are using CKAN 2.7 which has a different Job Queue - RQ. This is described in the README file:

All versions support celery backend, but version 2.7 will use RQ. There are no changes required to use new backend - just start it using:
paster --plugin=ckan jobs worker -c /config.ini
instead of:
paster --plugin=ckan celeryd run -c /config.ini
Details at http://docs.ckan.org/en/latest/maintaining/background-tasks.html

I am sorry if the documentation doesn't highlight it enough. Do you have any suggestions on how we can improve the documentation to avoid similar confusion in future?
Regards,
Iaroslav

Hi @iaroslav13,
I see what happened!
In my mind, I think what happened was seeing the redis dependency listed with the ckan installation instructions and then blanking on the ckan version number when I was reading the data.world instructions. This probably wouldn't have been lost on most people paying better attention. Maybe a dummy alert under step 5 in the readme for people like me? :)
Thanks so much!


[5.6] Remove the getClientSize() argument on UploadedFile constructor

Passing the file size to the constructor of the Symfony\Component\HttpFoundation\File\UploadedFile class is deprecated since Symfony 4.1, it should be removed.
The change can also be found at Symfony 4.1 upgrade guide

https://github.com/laravel/framework/blob/5.6/composer.json
"symfony/http-foundation": "~4.0",

4.0 still has the $file argument in its constructor https://github.com/symfony/symfony/blob/4.0/src/Symfony/Component/HttpFoundation/File/UploadedFile.php
Since projects could be using between 4.0.0 and 4.1.3, would a minor version bump for Laravel's Symfony dependencies ~4.1 be required to merge this in?
A merge conflict of this 5.7 change will have to be fixed as well: https://github.com/laravel/framework/pull/24602

This sounds like something better for 5.7.

The problem is that the tilde in "symfony/http-foundation": "~4.0", means that it will install the 4.1 version.
I tried installing a fresh Laravel installation and got the exception.

That would be a PHP error instead of a PHP Exception. Symfony 4.1 will still run < 4.1 constructor parameters - it just generates a user-level deprecated error when the extra file-size parameter is given:
        if (4 < \func_num_args() ? !\is_bool($test) : null !== $error && @filesize($path) === $error) {
            @trigger_error(sprintf('Passing a size as 4th argument to the constructor of "%s" is deprecated since Symfony 4.1.', __CLASS__), E_USER_DEPRECATED);
            $error = $test;
            $test = 5 < \func_num_args() ? func_get_arg(5) : false;
        }

You can silence this error by changing the E_DEPRECATED setting in php.ini
e.g.,
error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT


Query in RCON-console not working in production

It works on localhost as expected, but doesn't work in production as the request to /query/api.php is non-local.

I've dug up the cause of this issue. status.php sends api request to the address of the original request. So it requests http://snowwm.ml but the docker container doesn't know that it's its own hostname and forwards request to the host (or, probably, to the DNS).
Working on a PR.


Bibliography not showing up

As the title suggests, the bibliography simply does not show up. I have tried running the main file with biber and following it with pdflatex multiple times but to no avail. The main file is nothing out of the ordinary so I did not include it here.
Any ideas what the issue can be?

Ok I found a workaround for anyone having the same issue as mine:
instead of those two lines in the preamble:
\usepackage[style=authoryear,backend=bibtex]{biblatex} %backend tells biblatex what you will be using to process the bibliography file
\addbibresource{main.bib}
I deleted them and put:
\usepackage{filecontents}
\begin{filecontents}{ [I put here mybiblography]}
\end{filecontents}
and inside the dcoument I removed:
\printbibliography[title=Bibliography]
And replaced it with
\nocite{*}
\bibliographystyle{ieeetr} %to print the bibliography with original typing order
\bibliography{jobname}
After that I would run the main.tex with bibtex and not with biber, and then pdflatex+makeindex+bibtex


Add UI elements (slider, db type selector) to db create page

Add {{no-ui-slider}} component on db create page
Add Database#type field
selector for db type on db create page

Refs #28, closes #33
@mixonic for you

looks like this:

Great!


robot_localization: 2.6.5-1 in 'melodic/distribution.yaml' [bloom]

Increasing version of package(s) in repository robot_localization to 2.6.5-1:

upstream repository: https://github.com/cra-ros-pkg/robot_localization.git
release repository: https://github.com/cra-ros-pkg/robot_localization-release.git
distro file: melodic/distribution.yaml
bloom version: 0.8.0
previous version for package: 2.6.4-0

robot_localization
* fix: wall time used when use_sim_time is true
* Created service for converting to / from lat long
* Fix bug with tf_prefix
* Adding new contribution to doc
* Add missing undocumented params
* Update wiki location
* Contributors: Andrew Grindstaff, Axel Mousset, Charles Brian Quinn, Oswin So, Tom Moore

Holding for melodic sync


Update RouteListCommand.php

Removing empty elements of the array $routes to avoid offset on value of type null

I'm sorry Javier, but you must have mistaken my fork with the official laravel repository.


Get rid of ocean's BitArray in BitField

Ocean's BitArray is just a pain to work with, and a thorn in our side.
It lacks attribute, duplicates most of what BitField is doing, and doesn't expose proper const-correct constructors.

Yes. But the Phobos implementation had its own quirks that lead to some issues with serialization. I did not have luck finding alternatives..

I was thinking of just rolling our own, it shouldn't be too much work.

I considered that too. But I didn't have much time left in the sprint, so I picked ocean's sloppy implementation. (I think that code even dates back to Tango probably).

I'll get to it soon, because it was blocking progress on the deserialization work.


Is it possible to change value in "matrixdropdown"  based on response in same row . Exp:i need to change value based on Column1,2,3  responce in "Result"

Are you requesting a feature, reporting a bug or ask a question?
What is the current behavior?
What is the expected behavior?
How would you reproduce the current behavior (if this is a bug)?
Provide the test code and the tested page URL (if applicable)
Tested page URL:
Test code
your_code_here

Specify your

browser:
browser version:
surveyjs platform (angular or react or jquery or knockout or vue):
surveyjs version:

Thank you for the good suggestion. We've added the expression type to the available column types.
This feature will be available in the nearest update.
You will be able to do it vai code as well as in the SurveyJS Editor.
JSON example:
          {
            type: "matrixdropdown",
            name: "question1",
            columns: [
              { name: "Column 1" },
              { name: "Column 2" },
              {
                name: "Result",
                cellType: "expression",
                expression: "{row.Column 1} + {row.Column 2}"
              }
            ],
            choices: [1, 2, 3, 4, 5],
            rows: ["Row 1", "Row 2"]
          }

Thank You @tsv2013 ,When we can expect ?

Most likely this week


Add a library function to add a subnet to an existing network.

it looks like we are adding integration test in this commit.
it is better to mention it in the commit msg & have a instruction for how to run integration test in README

This commit disables the integration tests unless a flag is given to the test.

ah I got it. I still think it is helpful to have doc about it in Readme.md but it up to you.
LGTM

@nati Somehow your review comments disappeared from the conversation when updated the review.


Renames internal ExtraHandler back to ExtraFactory and clarifies

When integrating secondary sampling, I found the new name (I caused)
more distracting then helpful. The defensive api which led to renaming
was a cure worse than the disease of a preventable programming error.
Instead, this improves Javadoc, notably mentioning how to use the
factory properly (and not crashing on mistake).

here's a side effect which is I think, not just more like the code was before, but more intuitive (or.. maybe less unituitive?)
https://github.com/openzipkin-contrib/zipkin-secondary-sampling/pull/33/commits/b4221511cda5209145386cad449684823135029d
after this, next step is to make a base type for map views over arrays as we need it both for secondary sampling and w3c tracestate


Remove unnecessary fetches from application export query

Description
Remove unnecessary fetches from application export query
Details:

As long as we're only accessing the id of the related entity (eg applicationModel.getProgram().id) we don't need to eagerly fetch the whole related entity.
We only need the program id and applicant ids for export, so we don't need to fetch them.
I confirmed this didn't induce a n+1 query situation. If instead we fetched the program id through the ProgramDefinition (eg applicationModel.getProgram().getProgramDefinition().id()) it does.

Release notes
n/a
Checklist
General
Read the full guidelines for PRs here

[x] Added the correct label: < feature | enhancement | bug | under-development | dependencies | infrastructure | ignore-for-release | database >
[x] Assigned to a specific person, civiform/developers, or a more specific round-robin list
[x] Added an additional reviewer from outside your organization as FYI (if the primary reviewer is in the same organization as you)
[n/a] Created unit and/or browser tests which fail without the change (if possible)
[x] Performed manual testing (Chrome and Firefox if it includes front-end changes)
[n/a] Extended the README / documentation, if necessary

Instructions for manual testing
If you really want to

add <logger name="io.ebean.SUM" level="TRACE"/> to logback.xml
look for the line similar to

[debug] io.ebean.SUM - txn[] FindMany type[ApplicationModel] origin[DXSLCi.A.A] exeMicros[1604] rows[12] predicates[ (program_id) in (select t0.id from programs t0 where  (t0.name) in (select t0.name from programs t0 where t0.id = ?)) and lifecycle_stage = any(?) and t0.id < ?] bind[]

notice that no additional queries with the same origin id are triggered when exporting a CSV or JSON file.

Issue(s) this completes
Related to https://github.com/civiform/civiform/issues/5018

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

#6967  👈
#6873
#6953
main

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

Join @avaleske and the rest of your teammates on  Graphite

@dkatzz is the main reviewer
@nb1701 as FYI

Thanks for looking into this!! I'm noticing a user does access the program definition here: https://github.com/civiform/civiform/blob/main/server/app/services/export/JsonExporterService.java#L140. Does that path still work as expected?

That's fixed in the diffbase:
https://github.com/civiform/civiform/pull/6873


RunWith support runs test suites

The suite runner should be exempt from RunWith support to prevent tests in suites from running multiple times.

For others getting here from Google and struggling to find a way to run a suite of test classes in a specific order, without the Suite runner which is ignored by this JUnit interface, I inspired myself with the Enclosed runner and allowed to run inner classes in a specific order with a custom runner like my gist: OrderableEnclosed


DS1074Z Plus Logic analyzer channels are not recognized

if I try just one LA channel I get a division by zero error:
python .\rigol_plt.py
Traceback (most recent call last):
File "C:\Users\jano\workfolder\code\memosens\rigol_plt.py", line 7, in
w = rigol.Wfm.from_file(filename, scope)
File "C:\Users\jano\AppData\Roaming\Python\Python310\site-packages\RigolWFM\wfm.py", line 209, in from_file
ch = RigolWFM.channel.Channel(w, ch_number, pname, selected)
File "C:\Users\jano\AppData\Roaming\Python\Python310\site-packages\RigolWFM\channel.py", line 162, in init
self.ds1000z(w, channel_number)
File "C:\Users\jano\AppData\Roaming\Python\Python310\site-packages\RigolWFM\channel.py", line 294, in ds1000z
self.points = w.header.points
File "C:\Users\jano\AppData\Roaming\Python\Python310\site-packages\RigolWFM\wfm1000z.py", line 274, in points
self._m_points = self.memory_depth // self.stride
ZeroDivisionError: integer division or modulo by zero
rigol_plt.py contains:
import matplotlib.pyplot as plt
import RigolWFM.wfm as rigol

filename = 'test1.wfm'
scope = 'DS1074Z'

w = rigol.Wfm.from_file(filename, scope)
w.plot()
plt.show()

if along with the LA I turn on CH1, the picture has blocks which are not correct:

If I zoom in:

the pictures in the scope:

I also tried wfmconver.exe, it stays forever doing nothing.
the files:
D.zip
firmware on the scope is 00.04.05.SP2, there is nothing newer than this one on Rigol's website.

Nice bug report.  Unfortunately, the logic analyzer is completely undocumented and unsupported.

The Logic Analyzer functions are not supported and have never been tested
I didn't have a Z series test file with no channels enabled and therefore the division by zero never arose
I just looked and I have no information about how the logic analyzer data is stored or interpreted. For example, I don't see any information in the header that indicates that digital channel 6 was used.

inside the attached D.zip file, test1.wfm has only digital 6 enabled, test3.wfm has digital 6 and analog 1. the digital content should be the same in both, the analog input was not connected (not even the probe).
I only have access to the scope at work (I have the same series oscilloscope at home, but without LA). If there is any other data I can gather to help analyzing this, please let me know.

I see.  Thanks for clarification about what was saved.
The problem is that I do not know where in the file header to find any information about digital signals.  Most specifically which signals have been saved.
The digital data is stored in 2 byte arrays.  One for D7-D0 and the other for D15-D8.  However, for example, test1.wfm has a bunch of 0x40 values (which is not 2^6 as one might expect for digital 6).  So it is also not obvious how to interpret the bytes that are saved.  If we could do that, then we could just discard all the arrays that are identically zeros as not having been saved.
You could help by using going to the kaitai struct IDE and adding wfm1000z.ksy along with the .wfm that you are interested in decoding.  I don't have the time (or equipment) to reverse engineer this stuff.
Finally, you could also contact Rigol Technical Support and ask them to tell you how to interpret the MSO files.

As you might have noticed on #27, I'm trying to figure out that WFM and your comment piked my interest:

The digital data is stored in 2 byte arrays. One for D7-D0 and the other for D15-D8. However, for example, test1.wfm has a bunch of 0x40 values (which is not 2^6 as one might expect for digital 6). So it is also not obvious how to interpret the bytes that are saved. If we could do that, then we could just discard all the arrays that are identically zeros as not having been saved.

Where did you see that? Here's what I see when I have all digital channels enabled (test0.wfm) and then all of them disabled except D0 and D1:

Actual waveform data seems to be encoded later?

@scottprahl, I know your time is limited to dedicate to this particular reversing, but since you've seem a few of those, maybe you can identify patterns that you've seen before and therefore I can fully decode and put it together in Kaitai (as soon as I understand it)?


Wildcard hosts fail to match when port is included in host header

Bug description
Hi,
I am using istio ingress gateway (simplified yaml are shown below) to expose tensorflow serving.
I encounter similar issue where I need to explicitly set the host name in :authority from GRPC client to make GRPC call works.
The setup for HTTP is working fine.
The GRPC issue is similar with what's described by where it seems istio tries to match $host:$port for the hosts in virtual service. e.g. if I have GRPC endpoint in ms-123.byom.abc.com

if explicitly set :authority to ms-123.byom.abc.com, GRPC works fine
if I don't set :authority explicitly. GRPC will return Unimplemented. and I see the access log in ingress-gateway pod that host = ms-123.byom.abc.com:443 (note that there's additional port).

[2020-07-09T01:00:06.361Z] "POST /tensorflow.serving.PredictionService/GetModelMetadata HTTP/2" 200 NR "-" "-" 0 0 0 - "<IP_ADDRESS>" "grpc-java-netty/1.29.0" "8ae3780a-725f-4aa8-899d-ac222968268d" "ms-9177c71a-874d-4821-b65c-9e58ca423fa3.byom.abc.com:443" "-" - - <IP_ADDRESS>:8443 <IP_ADDRESS>:63486 ms-9177c71a-874d-4821-b65c-9e58ca423fa3.byom.abc.com -

Comparing with log of successful HTTP call, that log doesn't have 443 port.
[2020-07-09T01:17:56.496Z] "GET /v1/models/inception-v3-08 HTTP/2" 200 - "-" "-" 0 154 53 53 "<IP_ADDRESS>" "curl/7.64.1" "f9ca8da5-cad2-4d56-8d53-6b9b1a0b1374" "ms-9177c71a-874d-4821-b65c-9e58ca423fa3.byom.abc.com" "<IP_ADDRESS>:53545" outbound|53545||mlf-inference-server.byom.svc.cluster.local <IP_ADDRESS>:38586 <IP_ADDRESS>:8443 <IP_ADDRESS>:64506 ms-9177c71a-874d-4821-b65c-9e58ca423fa3.byom.abc.com -

Can anyone help me find what's missing? We can't force our clients to change their codes to explicitly set :authority in their GRPC requests.
Since @andraxylia mentioned that this is supported by the gateway. I thought there should be a way to make it work in ingress gateway.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ x] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Expected behavior
GRPC client doesn't need to explicitly specify host in authority metadata.
Steps to reproduce the bug

deploy GRPC server (i.e. inception model running on tensorflow serving 1.14)
these are gateway and related virtual service (domain name is modified to byom.abc.com)

tensorflow serving 1.14 expose both GRPC and HTTP. I remove HTTP configuration for brevity, because HTTP call is working fine.
curl -v https://$ENDPOINT/v1/models/inception -H "Authorization: Bearer $TOKEN"

for GRPC, I use grpcurl.
note that here I need to specify -authority $ENDPOINT explicitly to make it work. Otherwise, I will get unimplemented.
grpcurl -v \
-authority $ENDPOINT \
-import-path  $TEST_DATA_DIR/proto -proto $TEST_DATA_DIR/proto/tensorflow_serving/apis/model_service.proto \
-d '{"model_spec": {"name": "inception"}}' \
-H "Authorization: Bearer $TOKEN" \
$ENDPOINT:443 tensorflow.serving.ModelService/GetModelStatus

kind: VirtualService
metadata:
  name: mlf-inference-server
  namespace: byom
spec:
  gateways:
  - istio-system/byom-gateway
  hosts:
  - '*.byom.abc.com'
  http:
  - match:
    - uri:
        prefix: /tensorflow.serving.PredictionService
    - uri:
        prefix: /tensorflow.serving.ModelService
    - uri:
        prefix: /tensorflow.serving.SessionService
    retries:
      attempts: 3
      perTryTimeout: 30s
    route:
    - destination:
        host: mlf-inference-server.byom.svc.cluster.local
        port:
          number: 53547
    timeout: 10m

gateway
apiVersion: networking.istio.io/v1beta1
kind: Gateway
metadata:
  name: byom-gateway
  namespace: istio-system
spec:
  selector:
    istio: ingressgateway
  servers:
  - hosts:
    - '*.byom.abc.com'
    port:
      name: https
      number: 443
      protocol: HTTPS
    tls:
      credentialName: byom-cert
      mode: SIMPLE
  - hosts:
    - '*.byom.abc.com'
    port:
      name: http
      number: 80
      protocol: HTTP
    tls:
      httpsRedirect: true

Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)
(global-3.7.2) i341814@ariefhidayat ~ % istioctl version --remote
client version: 1.6.3
cluster-local-gateway version:
pilot version: 1.6.3
data plane version: 1.6.3 (8 proxies)

(global-3.7.2) i341814@ariefhidayat ~ % kubectl version
Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.3", GitCommit:"b3cbbae08ec52a7fc73d334838e18d17e8512749", GitTreeState:"clean", BuildDate:"2019-11-14T04:24:34Z", GoVersion:"go1.12.13", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.10", GitCommit:"f3add640dbcd4f3c33a7749f38baaac0b3fe810d", GitTreeState:"clean", BuildDate:"2020-05-20T13:51:56Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}

How was Istio installed?
via istioctl
Environment where bug was observed (cloud vendor, OS, etc)
AWS gardener cluster. Haven't tried in other cluster.

seems like I can workaround by specifying * in the hosts. So, it might work for both

HTTP where host header ms-123.byom.abc.com , and
GRPC where authority is ms-123.byom.abc.com:443

as for solution, I think this issue can be solved if istio set strip_matching_host_port in https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/filters/network/http_connection_manager/v3/http_connection_manager.proto

Can reproduce with HTTP by curl http://host -H "Host: host:80" as well. In config we generate:
        "domains": [
         "*.foo",
         "*.foo:*"
        ],

This fails
But if we instead do not have wildcard in the VS host, we end up with config:
        "domains": [
         "foo",
         "foo:*"
        ],

And this does work
I am not sure if this is an Envoy bug or not Wildcard hosts are supported in the suffix or prefix form. does not clarify its exclusive OR or not.
@lambdai @hzxuzhonghu any suggestion?

strip_matching_host_port does not work because we will create the listener on targetPort (8443) but request may come in from the main port (443) or even node port

Based on this I think we need changes in Envoy to support our case here

We are also hit with this problem.
I notice that Istio generates following routes:
    {
        "name": "https.443.https.gateway-ext.istio-system",
        "virtualHosts": [
            {
                "name": "*.domain.net:443",
                "domains": [
                    "*.domain.net",
                    "*.domain.net:*"
                ],
                "routes": [
                    {

The issue is the multiple wildcard on the domain probably.
But since the port is known in the gateway, can Istio not generate:
    {
        "name": "https.443.https.gateway-ext.istio-system",
        "virtualHosts": [
            {
                "name": "*.domain.net:443",
                "domains": [
                    "*.domain.net",
                    "*.domain.net:443"
                ],
                "routes": [
                    {

gateway:
  spec:
    servers:
    - hosts:
      - '*.domain.net'
      port:
        name: https
        number: 443
        protocol: HTTPS
      tls:
        credentialName: ingressgateway-certs
        minProtocolVersion: TLSV1_2
        mode: SIMPLE

As  short term fix that would probably be a good idea, the reason we do a wildcard is that the port may not actually match due to using nodeport or others causing a different port to show up in the header

Opened https://github.com/envoyproxy/envoy/issues/12647

I seem to be experiencing something along what is being reported here, just even more inconsistent.
if i do VS host: *
I get response when doing grpc calls to
api.snbx.asgt.foo.bar:443
but not
api.snbx.ssn.foo.bar:443
If i do VS host: *.foo.bar
Same as above
If i do VS host: [*.ssn.foo.bar, *.asgt.foo.bar]
Both correctly respond
This only happens to one service. I have other services running where VS Host: * works as expected.
The service it happens to is also used by my ext_authz filter and responds to calls caused by the filter.
I have tried in 1.6.7 and 1.6.8 and consistently seen the same issue.

Do the access logs show 404 NR? I think this is what we would see if it
doesn't match the host. It may be the ext_authz possibly rejecting it?
On Wed, Aug 19, 2020 at 1:44 AM Jacob Scherffenberg <
<EMAIL_ADDRESS>wrote:

I seem to be experiencing something along what is being reported here,
just even more inconsistent.
if i do VS host: *
I get response when doing grpc calls to
api.snbx.asgt.foo.bar:443
but not
api.snbx.ssn.foo.bar:443
If i do VS host: *.foo.bar
Same as above
If i do VS host: [*.ssn.foo.bar, *.asgt.foo.bar]
Both correctly respond
This only happens to one service. I have other services running where VS
Host: * works as expected.
The service it happens to is also used by my ext_authz filter and responds
to calls caused by the filter.
I have tried in 1.6.7 and 1.6.8 and consistently seen the same issue.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/25350#issuecomment-675961900, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXIZ3Z2IRC5QKZ54GA3SBOGIDANCNFSM4OVI57LA
.

@howardjohn  yes NR response flag for the one with ssn in it. 200 ok for the one with ASGT in it.
200 ok for both if i am more specific with the hosts

I think the envoy change we need here is ready

I think the envoy change we need here is ready

/assign
should we apply the strip_any_host_port only to the gateway

/assign
should we apply the strip_any_host_port only to the gateway

One concern I have is that the flag actually changes the forwarded Host header flag. I am not sure if that will negatively impact anyone. I am guess not, especially at the gateway?

One concern I have is that the flag actually changes the forwarded Host header flag. I am not sure if that will negatively impact anyone. I am guess not, especially at the gateway?

The Host header won't be forwarded by gateway

The Host header won't be forwarded by gateway

are you sure? I think I was testing this and saw it did? if not, then what
host header is used?
On Wed, Jan 27, 2021, 11:30 PM Zhonghu Xu<EMAIL_ADDRESS>wrote:

The Host header won't be forwarded by gateway
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/25350#issuecomment-768859022, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXLETXSB5O4Y47EUIX3S4EHCFANCNFSM4OVI57LA
.

are you sure? I think I was testing this and saw it did? if not, then what
host header is used?
On Wed, Jan 27, 2021, 11:30 PM Zhonghu Xu<EMAIL_ADDRESS>wrote:

The Host header won't be forwarded by gateway
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/25350#issuecomment-768859022, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXLETXSB5O4Y47EUIX3S4EHCFANCNFSM4OVI57LA
.

You are right, the Host is stipped and forwarded to backend.

You are right, the Host is stipped and forwarded to backend.


Tasks: saved variable becomes visible after pressing Add button only

System information:

Operating system (distribution) and version Mac
DBeaver version 7.3.0 EA

Steps to reproduce, if exist:

Create a task with a variable
Add a variable value and close Variables window
Open Variables window again

Expected: the created variable is visible in the list
Actual result: variable is not displayed and becomes visible only after pressing Add button

Cannot be reproduced anymore


能否增加返回结果的状态，类似langchain的Callbacks/Streaming tokens

Initial Checks

[X] I have searched Google & GitHub for similar requests and couldn't find anything
[X] I have read and followed the docs & demos and still think this feature is missing

Description
目前貌似无法区分哪些是action，哪些是最终可以返回的结果，看了下langchain里边有个callback用来区分就挺方便：on_tool_start  / on_text / on_agent_action / on_agent_finish
https://python.langchain.com/v0.1/docs/modules/callbacks/
langchain0.2里好像还加了个Streaming tokens用来区分 event["event"] == "on_tool_start"
https://python.langchain.com/v0.2/docs/tutorials/agents/#streaming-tokens
Use case
No response

好的，我们尽快调研支持一下


It should be possible to specify multiple feature combos

For some situations there may be several levels of optimization depending on features. Maybe AVX is already enough for some speedups and AVX2 gives something extra. It would be nice to have the macro allow setting multiple alternate versions beyond the base one.

Yes, that's planned next after I fix features with dashs and dots in their names. See https://github.com/parched/runtime-target-feature-rs/issues/1. PS I'm going to close the repo because I have merged it with the other


Composer is soooo slow on WSL 2?

So this issue only started recently. Previously my speeds were fine but now I have no clue why this is happening.
I use composer to manage dependencies on my web projects, and it's always been pretty slow, but my recent usage of it on WSL set's a new record. I'm not sure whether something changed in a recent Insider update but here is basically what happened.
Previously: composer update or composer require would maybe take around 30 to 60 seconds to complete. This is pretty average for composer.
Now: composer update or composer require takes upwards of 60 minutes, but usually 30. No I'm not joking. I enabled verbose with -vvv and I've found that no matter what, it "redownloads" the json manifest for each of my dependencies, and writes it into the cache. The problem is, it does this every time which sorta defeats the point of a cache I guess. Also, each operation of Download + Write to Cache takes around 1-2 minutes EACH.
Considering most modern web projects have quite a number of dependencies, it make it pretty much unusable.
I've read plenty of posts/issues saying that File I/O in WSL isn't great, but what I don't understand is this was working fine like a week or two ago, and now it's randomly just started playing up.
In comparison, if I clone exactly the same git project on a native linux server and use composer, it finishes downloading them from scratch and putting all of them in cache in around 30-45 seconds (as said initially this is expected/usual)
So can someone provide anymore update on this? It's kinda annoying that I want to get some work done but instead I have to sit here for upwards of 1 hour before I can even do anything. Oh and the worst part is if I run composer update and wait an hour for it to finish, if I then decide to install a new dependency with composer require, I literally have to sit here for 1 hour AGAIN to install 1 dependency that might only be 10kb.
It's incredibly frustrating so I hope someone can help me out.
Thanks.

Where do you put your source files ? On the windows filesystem or within your wsl2 distro?

I'm on WSL2, have composer installed (with Docker), my PHP project files reside inside WSL and the speed is amazingly fast. Installing TYPO3 for example took about 40s in total.

Composer 1 takes quite a lot of time indeed, when having the files in /mnt/c, which I need for PHPStorm docker integration to work.
There are two solutions right now:

move your files from /mnt/c into the linux root filesystem and lose docker integration in your IDE
use hirak/prestissimo or composer 2 (run composer self-update --snapshot or use my docker image) to speed up things

Let's hope WSL2 will improve speeds in the future.

You can probably tell phpstorm to hope your project using the Linux file share at \wsl$\Ubuntu\home... This way the files are stored locally on the Linux side and your ide access the files using the remote share.

No actually, you can not do that, it will say something like "UNC paths are not supported".
I also tried mapping wsl$\Ubuntu as a drive with its own letter (net use) and a windows symlink (mklink on cmd or  new-item -itemtype symboliclink on powershell). That gives you the ability to open the files in PHPStorm, but it will kill the docker integration, because for some reason, docker for windows only allows paths on C: to be mounted.
I tried fixing that in the docker for windows settings, but the menu of the current version does not contain anything about file shares.

I've had similar issues. I'm brand new to Linux and WSL (more or less), coming from a Laravel Homestead setup, and I've noticed at least initial composer interactions are quite heavily delayed, to the point I question if anything is happening.
Thing is, I ended up reinstalling Ubuntu a couple times, and I think the worst case I saw might've been running composer from Windows instead of WSL. I'm wondering if that's actually possible now, but something wasn't right any time I ran a composer command.
Now, with my full Apache2 setup mostly worked out and much, much faster. The exception seems to be that composer takes a very long time to respond after running composer update .  Like 20-30 full seconds of nothing.
As far as the updating, I can't confirm this at the moment, but I feel like the individual package download speeds are possibly faster, but there's a split-second of delay between each slowing the process as a whole down. I'm tempted to call it a wash, but it's hard to say. (If anyone actually cares, let me know and I can do some time tests.)
On the bright side though, once things have already been downloaded and composer is pulling from cached packages, the difference is mind-blowing. I literally laughed at how beautiful it was.

Answering my case after 3+ years, just to help anyone landing here.
I had this issue on all my PHP projects under WSL2 (Windows 11 Pro) using Docker containers via DDEV.
After some investigation it was a networking problem.
I tryed using  --prefer-dist, --no-dev and --ignore-platform-reqs options and setting a bigger process-timeout value but nothing worked.
I tried shutting down my Ubuntu WSL (via wsl --shutdown) but nothing changed.
After some hours I restarted Windows and composer was fast as before.


Add component model wasmtime feature to Docs.rs

This PR adds the "component-model" feature to the Docs.rs metadata section in crates/wasmtime/Cargo.toml so that the Wasmtime docs include the component model-specific apis and types. This was discussed on Zulip with @alexcrichton in this thread.

Do we need to add anything to CI to check that docs build successfully when the "component-model" feature is active? It'd be sad to do a release that docs.rs fails to build.

That seems like a reasonable thing to automate, want to file that as an issue to improve the CI?

We already have a CI job running cargo doc. What I'm not sure of is whether we need to change it for this. I think we probably do...?

I would hope that it would respect the Cargo.toml contents for each crate.

It does, but I don't think cargo doc reads the [package.metadata.docs.rs] section. I think that's specifically for the docs.rs invocation of cargo doc.


ts files: link decoration in parameters with 'pos' in name

I'm not sure that the issue really lies with GitLens as it only happens with another extension in conjunction, having only one of the extensions enabled doesn't trigger the effect. An issue I opened in the VS Code repo was closed immediately: https://github.com/microsoft/vscode/issues/83410
Since it is a text decoration issue I reopen the issue here as the other extension doesn't seem to use them.

GitLens Version: 10.1.1
PostgreSQL 1.1.11

VSCode Version: 1.39.2 / 1.40.0-insider
OS Version: Windows 10 1903

Steps to Reproduce:

Install/enable GitLens and PostgreSQL extensions
Create new file and set language mode to typescript
Write a variable with pos somewhere in name and explicitly set the type (doesn't matter which), also happens in interfaces

This is a bug in vscode and will be fixed in the November iteration.


Number/float field are pushed into influxdb as string

Hi,
I try to use this plugin to convert nignx access log into metrics and push it into influxdb.
The nginx access log format likes the following:
[26/Oct/2019:17:21:40 +0000] 302<EMAIL_ADDRESS>"GET / HTTP/1.0" 4801 "-" "-" 0.631 0.631 .

I expect the status code(302), request time(0.631) and response time(0.631) should be saved into influxdb AS number/float data type.  But actually all of them are stored as string.
> select * from fe_portal
name: fe_portal
time                agent        code hostname               method path project   referer region          remote    request_time response_time size tailed_path                     timestamp                  user version
----                -----        ---- --------               ------ ---- -------   ------- ------          ------    ------------ ------------- ---- -----------                     ---------                  ---- -------
1572110977000000000 GoogleHC/1.0 302  wf20-td-agent-test-1-0 GET    /    prod-test -       asia-southeast1 <IP_ADDRESS> 0.630        0.630         4801 /var/log/pan/my-access-test.log 26/Oct/2019:17:29:21 +0000 -    HTTP/1.0
> select request_time::float from fe_portal
> select request_time::string from fe_portal
name: fe_portal
time                request_time
----                ------------
1572110977000000000 0.630
>

My fluentd config likes the following:
<source>
  @type tail
  pos_file /var/log/td-agent/nginx-influx.pos
  path_key tailed_path
  @id input_tail
  path /var/log/pan/*access*.log
  tag fe_portal
  <parse>
    @type regexp
    expression /^\[(?<timestamp>[^\]]*)\] (?<code>[^ ]*) "(?<user>[^ ]*)@(?<remote>[^ ]*)" "(?<method>\S+)(?: +(?<path>[^\ "]*?)(?: +\S*)?) (?<version>\S+/\S+)" (?<size>[\d.]+) "(?<referer>[^ ]*)" "(?<agent>[^\"]*)" (?<request_time>[\d.-]+) (?<response_time>[\d.-]+).*$/
    time_format %d/%b/%Y:%H:%M:%S %z
  </parse>
</source>
<filter fe_portal>
  @type record_transformer
  auto_typecast true
  <record>
    hostname ${hostname}
    project prod-test
    region asia-southeast1
  </record>
</filter>
<match fe_portal>
  type influxdb
  num_threads 8
  dbname test
  host influxdb
  port 8086
  flush_interval 10s
  cast_number_to_float true
  @id influxdb
  tag_keys ["method","path", "code", "region", "hostname"]
</match>

I got it. The type convert should be in fluentd configuration


need to improve filter_kg_and_remap_predicates.py to check subject/object category rules

@chunyuma reported the following issue:

I have a question regarding the predicate “biolink:treats” in our kg2. I found that the “biolink:treats” predicate seems not a relation only existing between “drug” entities (e.g. ‘’biolink:Drug”, “biolink:SmallMolecule”, “biolink:ChemicalEntity”) and “disease” entities (e.g. “biolink:Disease”, “biolink:PhenotypicFeature”, “biolink:DiseaseOrPhenotypicFeature”). It might also exist between “biolink:Procedure” and “biolink:OrganismTaxon”; “biolink:biolink:Activity” and “biolink:GrossAnatiomicalStructure”; “biolink:NamedThing” and “biolink:Cell” and etc. And it seems like most of triples containing this relation are from SEMMEDDB.
So I basically have following two questions regarding this observation:

Can I consider that the predicate “biolink:treats” used in our kg2 might present a general semantic meaning of “treatment” rather than specifically the treatment between drug and disease?

Do we have any specific rules to assign the “biolink:treats” label to a relation when we processed the raw data source and integrate them in kg2? Or we just depends on the original “treats” relation category used in the raw data?

Thanks for your time for helping me answer these questions in advance.
Best,
Chunyu

Right now, semmeddb:treats is mapped to biolink:treats without regard to the subject or object categories. That will have to change, to bring KG2 into full Biolink compliance.
I imagine we could update filter_kg_and_remap_predicates.py to load the Biolink model, and compile a map whose keys are combinations of subject-category, predicate, and object-category (and whose values are indexes of edges corresponding to each such combination). There may be perhaps ten thousand such combinations, but that's OK. Then, it could go through each such combination and check the Biolink rules to see if the subject category and object category are "allowed" for the predicate type. If not, the next parent predicate in the Biolink hierarchy could be checked, and so on, until (if necessary) we get to biolink:related_to whose subject category and object category are the general-purpose named thing. A warning could be issued for each predicate that violates Biolink rules. Then go through and update any edge predicates that need to be updated.

Hi @saramsey, thanks for opening this issue and paying attention to it. Except for biolink:treats, do we also have to check if other predicates also have this similar problem where the subject category or object category of a predicate doesn't fully comply with Biolink model? Thanks!

This ties into #281 (though that is more limited in scope and will occur at a different place in the build process). Overall, it would probably be good to consider the domain and range on the different predicates in the Biolink model.
One option, which is similar to what Steve suggested, is to have a hierarchy (tree) of allowed predicates for each subject-object pairing in KG2. Based on the assigned predicate, it could then assign the most specific predicate that fits.

As of KG2.8.3, there are 1554 subject-object category pairs and 10439 subject-predicate-object pairings.
Here are the results of
match (n)-[]->(m) return distinct n.category, m.category

edge_category_pairings.csv
match (n)-[e]->(m) return distinct n.category, e.predicate, m.category

edge_category_predicate_pairings.csv
on KG2.8.3.

Hi @saramsey, thanks for opening this issue and paying attention to it. Except for biolink:treats, do we also have to check if other predicates also have this similar problem where the subject category or object category of a predicate doesn't fully comply with Biolink model? Thanks!

Hi Chunyu, in general, I think the answer is "yes", there are many predicates in Biolink for which there are restrictions on the allowed categories for subject and or object. I think, in fact, it's the dominant case. I suspect most predicates in the biolink-model.yaml file have domain and or range constraints (which show up as domain or range keys under the predicate's entry in biolink-model.yaml). It's just that for the most part, the KG2pre build system pays no attention to those constraints. Right, @acevedol and @ecwood ?

Hi @saramsey, yes, the KG2pre build system currently ignores those domain and range constraints. Our biolink validation is limited in scope overall, but certainly with regards to domain and range.

Thank you for confirming, @ecwood. That's a good long-term project (to more systematically enforce those constraints).


Check matching input sizes in EmbedBounds

EmbedBounds does not throw error when mask/label and intensity images are not same size.

Fixed by #113


Add support for low-power run/sleep mode

This adds complete support for entering all low-power modes supported by the hardware. Also contains a commit with a small PWR-related fix.

cc @lthiery

Thanks!