Suggest moving away from npm blake3 package

The package has only 2,500 weekly downloads, and seems poorly maintained. An alternative to consider is @noble/hashes, which has 1.7 million weekly downloads, has a much better maintenance record, and is externally audited.

Hey @jrayback  I played a bit around with the nobles libraries and it looks like there is secp256r1 within @noble/curves

I found this example of usage of secp256r1 in the did-jwt library here

Oh, wow! Good catch! Thank you. I think the @noble library will be much better. I'll look at the example you sent through and include the migration to the new library in a PR resolving the other package dependency problems.

@AlexAndrei98 , looks like you've already pushed a PR for this one. Thanks. I'll submit something today to handle the other package deps.

OK, @AlexAndrei98 , I'm actively working on handling the other packages:

text-encoding (remove)
urlsafe-base64 (remove in favor of native node.js capability)
ecdsa-secp256r1 (replace with @noble/curves)
I hope to have a PR ready for review by tomorrow's dev meeting.

closed by #16


502 Bad Gateway and then DDev stops working - all projects won't start, "failed to read the CA certificate: unexpected content"

Describe the bug
While working on a project, updating twig code, all of a sudden  the project will return a 502 bad gateway error in the browser.
Stop Ddev and then run DDEv start and get the following error:
Failed to start project-name: ddev-router failed to become ready: logOutput=, err=container exited, please use `'ddev logs -s ddev-router`` to find out why it failed
running ddev logs outputs this:
Using the local CA at "/root/.local/share/mkcert" ✨
ERROR: failed to read the CA certificate: unexpected content

I then ran ddev poweroff and restarted - got the same issue. Rebooted compuger and got the same issue.
Am unable to work on any projects at this point.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Version and configuration information (please complete the following information):

Host computer OS and Version: Windows 10
Docker version information 19.03.8
ddev version information 1.14.2
config.yaml contents for the misbehaving project
-- APIVersion: v1.13.1
name: compugen-new
type: php
docroot: public
php_version: "7.3"
mysql_version: "5.7"
webserver_type: nginx-fpm
router_http_port: "80"
router_https_port: "443"
xdebug_enabled: false
additional_hostnames: []
additional_fqdns: []
nfs_mount_enabled: false
provider: default
use_dns_when_possible: true
timezone: ""
host_db_port: "32890"
Do you have any custom configuration (nginx, php, mysql) in the .ddev folder? no

Additional context
This is the full output when running ddev start
λ ddev start
Starting compugen-new...
Building ddev-ssh-agent
Creating ddev-ssh-agent ... done

ssh-agent container is running: If you want to add authentication to the
ssh-agent container, run 'ddev auth ssh' to enable your keys.
Pushing mkcert rootca certs to ddev-global-cache
failed to copy root CA into docker volume: container run failed with exit code 1, output=''
Pushed mkcert rootca certs to ddev-global-cache
Building db
Building web
Creating ddev-compugen-new-db ... done
Creating ddev-compugen-new-dba ... done
Creating ddev-compugen-new-web ... done

Creating ddev-router ... done

Failed to start compugen-new: ddev-router failed to become ready: logOutput=, err=container exited, please use 'ddev logs -s ddev-router` to find
out why it failed

Somebody else reported this, the fix for them was ddev poweroff and  then restart docker. What version of Docker Desktop for Windows are you using?

Docker 19.03.8
restarting docker appears to have fixed it. weird.

Thanks, please take a look at the "About docker desktop" and report the version of Docker desktop, thanks.

Okay and 2 minutes later I've got the same issue.

Please show the results of docker logs ddev-router

And then if you haven't already, rebuild the mkcert CA with the instructions in https://github.com/drud/ddev/issues/2285#issuecomment-636928527 (this does no harm)
OH, please check to make sure you're not out of docker disk space, that would sure do it.

docker logs here: https://pastebin.com/sjTKi0du
How do I see if I'm out of space?

Hoping to hear what your results are, @CreateSean , since this has happened to at least one other person.

rebuilding mkcert seems tohave worked for me. I'm haven't had a problem in 2 hours.
Thank you for your time @rfay

Thanks. Sure is weird. Will be interested to hear if you disk space looks like it's running low.

I have plenty of disk space

Thanks, I wonder what's happening. Now the fact that you made an issue will help collect information for the future. We'll be able to make sure we know whether it's just Windows, etc.

This issue happened again. I resolved it by once again following the instructions in this comment https://github.com/drud/ddev/issues/2285#issuecomment-636928527 after restarting docker.

This happened in my ddev version v1.22.4 with Docker Desktop 4.25.2 after renaming my ddev project:

ddev delete
renamed the directory the .ddev is in
ddev config --project-name=<new_name>
ddev restart
ddev launch
now getting "Bad Gateway"

First tried to uninstall and reinstall mkcert as described above. Didn't help.
Then tried to restart Docker Desktop and ddev restart. Now getting invalid SSL cert error in https requests. After a minute or so I'm back to "Bad Gateway" on the same request.
Another ddev project on my machine does work fine (SSL cert works), so it must be related to this very project.

Thanks, the solution works! @cepheiVV @rfay


Twitter reports: TAN hotline does not issue TANs for normal PCR tests because the staff thinks it is a quick PCR test

Which hotline
TAN
Describe the bug
I have multiple Twitter reports complaining that the TAN hotline does not issue TANs for normal PCR tests. The call agents say that the result was too quick delivered, so it was a quick PCR test. The users said this is not true but the staff still did not issue a TAN.
Steps to reproduce the issue

Have a PCR test done
Get the result quite fast (12h-30h)
Attempt to request a TAN at the TAN hotline

Expected behaviour
The TAN hotline should issue TANs for normal PCR tests.
Additional context
Links to Twitter:

https://twitter.com/Pixtxa/status/1499001085951938562?s=20&t=Occl6K5IZzak0-HvnYOaLw
https://twitter.com/Cartman_FFM/status/1498991173523984391?s=20&t=Occl6K5IZzak0-HvnYOaLw
https://twitter.com/christjan82/status/1498698649274142721?s=20&t=Occl6K5IZzak0-HvnYOaLw

Internal Tracking ID: EXPOSUREAPP-10939

If this was forwarded, that's all that can be done here. Thus closing this issue.


Fallback on convertdate if hijri-converter package is not installed

If hijri-converter package is not installed, fall back to using less precise converdate now that it's part of the installation (used for hebrew calendar) instead of skipping estimating of Hara Rasa Puasa and Hara Rasa Haji Singapore holidays.
Coverage will decrease since not all lines can be tested.

Pull Request Test Coverage Report for Build 877

4 of 11 (36.36%)  changed or added relevant lines in 1 file are covered.
6 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.1%) to 99.855%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

holidays/utils.py
4
11
36.36%

Files with Coverage Reduction
New Missed Lines
%

holidays/utils.py
6
60.61%

Totals

Change from base Build 856:
-0.1%

Covered Lines:
8956

Relevant Lines:
8969

💛  - Coveralls

Hey great one.. Thank you!
dr-p


⚠ Bofrost.de has degraded performance

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

HTTP code: 200
Response time: 701 ms

Resolved: Bofrost.de performance has improved in 4214034 after 6 minutes.


Fix image not shown bug

New card sequence diagram is now shown in developer guide

Pull Request Test Coverage Report for Build 680

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 90.413%

Totals

Change from base Build 679:
0.0%

Covered Lines:
2169

Relevant Lines:
2399

💛  - Coveralls


Inference works just once

When I first load a model and ask it to infer, I get a good result. On a second inference it ignores what it should respond with and just keeps on generating more on the original input text. On the third inference, it just gives stacktraces and any subsequent inferences repeat the stacktraces:
Traceback (most recent call last):
  File "/home/vadi/Programs/miniconda3/envs/finetuner2/lib/python3.10/site-packages/gradio/routes.py", line 394, in run_predict
    output = await app.get_blocks().process_api(
  File "/home/vadi/Programs/miniconda3/envs/finetuner2/lib/python3.10/site-packages/gradio/blocks.py", line 1075, in process_api
    result = await self.call_function(
  File "/home/vadi/Programs/miniconda3/envs/finetuner2/lib/python3.10/site-packages/gradio/blocks.py", line 884, in call_function
    prediction = await anyio.to_thread.run_sync(
  File "/home/vadi/Programs/miniconda3/envs/finetuner2/lib/python3.10/site-packages/anyio/to_thread.py", line 31, in run_sync
    return await get_asynclib().run_sync_in_worker_thread(
  File "/home/vadi/Programs/miniconda3/envs/finetuner2/lib/python3.10/site-packages/anyio/_backends/_asyncio.py", line 937, in run_sync_in_worker_thread
    return await future
  File "/home/vadi/Programs/miniconda3/envs/finetuner2/lib/python3.10/site-packages/anyio/_backends/_asyncio.py", line 867, in run
    result = context.run(func, *args)
  File "/home/vadi/Programs/miniconda3/envs/finetuner2/lib/python3.10/site-packages/gradio/helpers.py", line 587, in tracked_fn
    response = fn(*args)
  File "/home/vadi/Programs/simple-llama-finetuner/main.py", line 67, in generate_text
    model = PeftModel.from_pretrained(
  File "/home/vadi/Programs/miniconda3/envs/finetuner2/lib/python3.10/site-packages/peft/peft_model.py", line 138, in from_pretrained
    remove_hook_from_submodules(model)
  File "/home/vadi/Programs/miniconda3/envs/finetuner2/lib/python3.10/site-packages/accelerate/hooks.py", line 407, in remove_hook_from_submodules
    remove_hook_from_submodules(child)
  File "/home/vadi/Programs/miniconda3/envs/finetuner2/lib/python3.10/site-packages/accelerate/hooks.py", line 405, in remove_hook_from_submodules
    remove_hook_from_module(module)
  File "/home/vadi/Programs/miniconda3/envs/finetuner2/lib/python3.10/site-packages/accelerate/hooks.py", line 187, in remove_hook_from_module
    delattr(module, "_hf_hook")
  File "/home/vadi/Programs/miniconda3/envs/finetuner2/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1328, in __delattr__
    super().__delattr__(name)
AttributeError: _hf_hook

Do others get the same?

I get the same problem running it in Colab.
Traceback (most recent call last):   File "/usr/local/lib/python3.9/dist-packages/gradio/routes.py", line 394, in run_predict     output = await app.get_blocks().process_api(   File "/usr/local/lib/python3.9/dist-packages/gradio/blocks.py", line 1075, in process_api     result = await self.call_function(   File "/usr/local/lib/python3.9/dist-packages/gradio/blocks.py", line 884, in call_function     prediction = await anyio.to_thread.run_sync(   File "/usr/local/lib/python3.9/dist-packages/anyio/to_thread.py", line 31, in run_sync     return await get_asynclib().run_sync_in_worker_thread(   File "/usr/local/lib/python3.9/dist-packages/anyio/_backends/_asyncio.py", line 937, in run_sync_in_worker_thread     return await future   File "/usr/local/lib/python3.9/dist-packages/anyio/_backends/_asyncio.py", line 867, in run     result = context.run(func, *args)   File "/usr/local/lib/python3.9/dist-packages/gradio/helpers.py", line 587, in tracked_fn     response = fn(*args)   File "/content/simple-llama-finetuner/main.py", line 67, in generate_text     model = PeftModel.from_pretrained(   File "/usr/local/lib/python3.9/dist-packages/peft/peft_model.py", line 138, in from_pretrained     remove_hook_from_submodules(model)   File "/usr/local/lib/python3.9/dist-packages/accelerate/hooks.py", line 405, in remove_hook_from_submodules     remove_hook_from_module(module)   File "/usr/local/lib/python3.9/dist-packages/accelerate/hooks.py", line 187, in remove_hook_from_module     delattr(module, "_hf_hook")   File "/usr/local/lib/python3.9/dist-packages/torch/nn/modules/module.py", line 1328, in __delattr__     super().__delattr__(name) AttributeError: _hf_hook

Hi! Same issue in Colab as well, running on the base GPU.

I'm currently refactoring the model loading/unloading to fix the inference.

Should be fixed in https://github.com/lxe/simple-llama-finetuner/commit/ecf29d859062f256b5b393e3ceeba8f25b69a263

@lxe Awesome! Thanks a lot! Will try this and report here.

Loading the model right after training still caused an error (unfortunately forgot to save the traceback before re-running the cell), but once I re-ran the cell I have been able to keep using the model without errors like it used to !

Loading the model right after training still caused an error (unfortunately forgot to save the traceback before re-running the cell), but once I re-ran the cell I have been able to keep using the model without errors like it used to !

Are you running on Colab or elsewhere?

@lxe I'm running on Collab

I just merged another change that does a GC after inference. Try running the notebook again.

@lxe I tried it again and got an error: AttributeError: 'NoneType' object has no attribute 'device'
Here is the full traceback:
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/dist-packages/gradio/routes.py", line 394, in run_predict
    output = await app.get_blocks().process_api(
  File "/usr/local/lib/python3.9/dist-packages/gradio/blocks.py", line 1075, in process_api
    result = await self.call_function(
  File "/usr/local/lib/python3.9/dist-packages/gradio/blocks.py", line 884, in call_function
    prediction = await anyio.to_thread.run_sync(
  File "/usr/local/lib/python3.9/dist-packages/anyio/to_thread.py", line 31, in run_sync
    return await get_asynclib().run_sync_in_worker_thread(
  File "/usr/local/lib/python3.9/dist-packages/anyio/_backends/_asyncio.py", line 937, in run_sync_in_worker_thread
    return await future
  File "/usr/local/lib/python3.9/dist-packages/anyio/_backends/_asyncio.py", line 867, in run
    result = context.run(func, *args)
  File "/usr/local/lib/python3.9/dist-packages/gradio/helpers.py", line 587, in tracked_fn
    response = fn(*args)
  File "/content/simple-llama-finetuner/main.py", line 104, in generate_text
    output = model.generate(  # type: ignore
  File "/usr/local/lib/python3.9/dist-packages/peft/peft_model.py", line 581, in generate
    outputs = self.base_model.generate(**kwargs)
  File "/usr/local/lib/python3.9/dist-packages/torch/autograd/grad_mode.py", line 27, in decorate_context
    return func(*args, **kwargs)
  File "/usr/local/lib/python3.9/dist-packages/transformers/generation/utils.py", line 1462, in generate
    return self.sample(
  File "/usr/local/lib/python3.9/dist-packages/transformers/generation/utils.py", line 2478, in sample
    outputs = self(
  File "/usr/local/lib/python3.9/dist-packages/torch/nn/modules/module.py", line 1194, in _call_impl
    return forward_call(*input, **kwargs)
  File "/usr/local/lib/python3.9/dist-packages/accelerate/hooks.py", line 165, in new_forward
    output = old_forward(*args, **kwargs)
  File "/usr/local/lib/python3.9/dist-packages/transformers/models/llama/modeling_llama.py", line 765, in forward
    outputs = self.model(
  File "/usr/local/lib/python3.9/dist-packages/torch/nn/modules/module.py", line 1194, in _call_impl
    return forward_call(*input, **kwargs)
  File "/usr/local/lib/python3.9/dist-packages/transformers/models/llama/modeling_llama.py", line 614, in forward
    layer_outputs = decoder_layer(
  File "/usr/local/lib/python3.9/dist-packages/torch/nn/modules/module.py", line 1194, in _call_impl
    return forward_call(*input, **kwargs)
  File "/usr/local/lib/python3.9/dist-packages/accelerate/hooks.py", line 165, in new_forward
    output = old_forward(*args, **kwargs)
  File "/usr/local/lib/python3.9/dist-packages/transformers/models/llama/modeling_llama.py", line 309, in forward
    hidden_states, self_attn_weights, present_key_value = self.self_attn(
  File "/usr/local/lib/python3.9/dist-packages/torch/nn/modules/module.py", line 1194, in _call_impl
    return forward_call(*input, **kwargs)
  File "/usr/local/lib/python3.9/dist-packages/accelerate/hooks.py", line 165, in new_forward
    output = old_forward(*args, **kwargs)
  File "/usr/local/lib/python3.9/dist-packages/transformers/models/llama/modeling_llama.py", line 209, in forward
    query_states = self.q_proj(hidden_states).view(bsz, q_len, self.num_heads, self.head_dim).transpose(1, 2)
  File "/usr/local/lib/python3.9/dist-packages/torch/nn/modules/module.py", line 1194, in _call_impl
    return forward_call(*input, **kwargs)
  File "/usr/local/lib/python3.9/dist-packages/accelerate/hooks.py", line 165, in new_forward
    output = old_forward(*args, **kwargs)
  File "/usr/local/lib/python3.9/dist-packages/peft/tuners/lora.py", line 522, in forward
    result = super().forward(x)
  File "/usr/local/lib/python3.9/dist-packages/bitsandbytes/nn/modules.py", line 242, in forward
    out = bnb.matmul(x, self.weight, bias=self.bias, state=self.state)
  File "/usr/local/lib/python3.9/dist-packages/bitsandbytes/autograd/_functions.py", line 488, in matmul
    return MatMul8bitLt.apply(A, B, out, bias, state)
  File "/usr/local/lib/python3.9/dist-packages/bitsandbytes/autograd/_functions.py", line 317, in forward
    state.CxB, state.SB = F.transform(state.CB, to_order=formatB)
  File "/usr/local/lib/python3.9/dist-packages/bitsandbytes/functional.py", line 1698, in transform
    prev_device = pre_call(A.device)
AttributeError: 'NoneType' object has no attribute 'device'

I'm gonna close this as a duplicate of #6.
This happens when there's not enough RAM on the colab host.

I can confirm inference works multiple times now. FTR I'm running this on an RTX 4080 with 16GB vram and that hasn't changed, so thanks for fixing this one!


Redis transactions support

Add redis transactions support to Redis.OM, via redis WATCH and MULTI.
It would be nice to be able to grant atomicity and consistency of read/write operations, also in case multiple entities are updated.

Hi @slorello89 I would like to work on this.


drivers: modem: create subfolders

I'm not sure it's okay to suggest this, but wouldn't it be better to move modem drivers in subfolders?
I'm once again back to porting a modem driver and find it really hard to follow the code in those single files. I'd prefer to create "my" driver in a subfolder and split several parts across multiple files (power management, socket handling, command handling to name a few)

There has been some talks in the past that we should have proper modem APIs but so far no one has stepped up and send patches. Atm the modem directory is just a bunch of files and the actual drivers need to use the facilities directly. So this needs more TLC and patches are welcome in this area.
cc @mike-scott

I absolutely agree, but I honestly refrain from starting with patching w/o further discussions before.. I want to do it right and not submit a finished concept which gets declined immediately ;)
Well, I could start by publishing a fork to check out for everyone involved... happy to discuss


Favicon and logo issue

This is a(n):

[ ] Update to an existing Animated Button
[x] Any Error
[ ] Proposal to the Repository
[ ] Documentation / README.md changes

Details:

The favicon and the logo of the website do not match. Both should be same as part of the same website. Instead of the website logo, there is the user's logo and the GDSC logo which is not a good practice. Can you please assign me this issue under GSSOC'23?

The project is under GDSC DYPCOE. So suggest something more appealing than that in the form of design, and then I will assign it to you!


Mismatch of coreruleset GitHub Repos and Branches

At the very beginning
"The Azure-managed Default Rule Set is based on the OWASP Core Rule Set (CRS)"
The link tied to the OWASP Core Rule set is:
https://github.com/SpiderLabs/owasp-modsecurity-crs/tree/v3.1/dev
Then under
https://docs.microsoft.com/en-us/azure/web-application-firewall/afds/waf-front-door-tuning#understanding-waf-logs
"you could go to the OWASP ModSecurity Core Rule Set Official Repository"
The link for that OWASP repo is:
https://github.com/coreruleset/coreruleset
with the default branch of v3.4/dev (at the time of this writing)
But then for "and search by that rule ID"
The link for Rule ID is: https://github.com/coreruleset/coreruleset/blob/v3.1/dev/rules/REQUEST-942-APPLICATION-ATTACK-SQLI.conf
which is v3.1/dev
To sum it up:

2 different repos (coreruleset\coreruleset & SpiderLabs\owasp-modsecurity-crs)
2 different branches for the coreruleset\coreruleset repo.

Does the Azure WAF use the default repo - thus dynamic changes upon new commits, or a set branch version?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: d38eb998-6925-5ab2-ad2c-4367a7c22895
Version Independent ID: 0e0590c0-42d5-c5a3-86b6-2d396a43cf19
Content: Tuning Web Application Firewall (WAF) for Azure Front Door
Content Source: articles/web-application-firewall/afds/waf-front-door-tuning.md
Service: web-application-firewall
GitHub Login: @mohitkusecurity
Microsoft Alias: mohitku

@hctrr We are checking this and will get back to you.

@hctrr Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.


[6.3.x] GUVNOR-2459: NPE when open an Organization Unit that doesn't have a repository yet

*** DO NOT MERGE ***
*** @Rikkola Can you please check if we should be committing to 6.3.x? ***
==========================================================================
See https://issues.jboss.org/browse/GUVNOR-2459
This is the corollary of https://github.com/droolsjbpm/kie-wb-common/pull/315 for 6.3.x
(cherry picked from commit a08a9e5a9c9299cb02bf0102138c31d0b944b31e)
Conflicts:
kie-wb-common-screens/kie-wb-common-project-explorer/kie-wb-common-project-explorer-backend/src/test/java/org/kie/workbench/common/screens/explorer/backend/server/ProjectExplorerContentResolverTest.java

No we should not at this point.
Only tickets that get approved to the next patch release and after the previous patch is done. So right now we are on hold.

I have a list of commits that need to go in once we have green light and this is on that list. If this PR  does not bother anyone we can leave it open for now.

This should go in now or never. Asking for permissions.

Made new PR that replaces this with a correct commit message.
https://github.com/droolsjbpm/kie-wb-common/pull/347
This one can now be rejected.

Rejected, replaced by https://github.com/droolsjbpm/kie-wb-common/pull/347

Thank you @manstis


fix implied_bounds_entailment future compatibility lint

Your crate unintentionally relied on a soundness bug in the Rust compiler, see https://github.com/rust-lang/rust/issues/105572 for more info. This lint will be a hard error in a future release. This PR fixes that lint.

closing this to cleanup my open PRs


call server uri instead of localhost

Hi,
we had a problem during the connection attempt for the first time, the js variable Settings.Uri reference localhost uri or we need to call server uri,
Problem encoutred when the app is deployed as docker container in aws ec2 instance and called from outside.
changing localhost with window.location.hostname worked for us
maybe need more investigation...

@anouarattn This will work if the Wexflow server and the backend are on the same server. Howver, if Wexflow server and the backend are on different servers, this won't work. Can you access Swagger on port 8000 from a web browser? Also did you try curl?

@anouarattn This will work if the Wexflow server and the backend are on the same server. Howver, if Wexflow server and the backend are on different servers, this won't work. Can you access Swagger on port 8000 from a web browser? Also did you try curl?

they are on the same ec2 instance, We are calling the Ui from a client computer.

they are on the same ec2 instance,

You mean the server and the backend are on the same machine and you call the backend from a client computer?
Did you use Dockerfile or docker-compose?

they are on the same ec2 instance,

You mean the server and the backend are on the same machine and you call the backend from a client computer?
Did you use Dockerfile or docker-compose?

we use docker-compose as described in the wiki page
https://github.com/aelassas/Wexflow/wiki/Docker

Ah Ok. I have just tested docker-compose on a virtual machine and accessing the ui from another computer and it worked fine.
Maybe it's related to cache. Did you try Ctrl+F5?
Can you make sure that http://hostname:8011/js/settings.js is updated with your config.
Also make sure that you have access to http://hostname:8000/ from the client computer.

not working, here is the error we get

@anouarattn Can you show me your  http://hostname:8011/js/settings.js?

8011/js/settings.js?

@anouarattn You must update Uri setting and put http://hostname:8000/wexflow/ where hostname is the hostname of ec2 instance instead of http://localhost:8000/wexflow/. After you modify settings.js on ec2 instance you must re-run docker-compose up and refresh the cache of the client computer Ctrl+F5. Can you try this and let me know?

@anouarattn You must update Uri setting and put http://hostname:8000/wexflow/ where hostname is the hostname of ec2 instance instead of http://localhost:8000/wexflow/. After you modify settings.js on ec2 instance you must re-run docker-compose up and refresh the cache of the client computer Ctrl+F5. Can you try this and let me know?

we done that, we replaced
Uri: "http://localhost:8000/wexflow/"
with
Uri: "http://" + window.location.hostname + ":8000/wexflow/"
and now its working good. that's way we created the pull requests,
the problem with this solution is that it will not work if we deploy wexflow3_wexflow and wexflow3_wexflow-backend in two different machines

@anouarattn Your ec2 instance hostname is static or dynamic?

@anouarattn Your ec2 instance hostname is static or dynamic?

static

So why don't you put:

@anouarattn  So why don't you put:
Uri: "http://ecs2instance:8000/wexflow/"
instead of:
Uri: "http://" + window.location.hostname + ":8000/wexflow/"

@anouarattn So why don't you put:
Uri: "http://ecs2instance:8000/wexflow/"
instead of:
Uri: "http://" + window.location.hostname + ":8000/wexflow/"

Uri: "http://" + window.location.hostname + ":8000/wexflow/"
will always work regardless of which server we use

Uri: "http://" + window.location.hostname + ":8000/wexflow/"
will always work regardless of which server we use

Ok, I understand what you want. You can use window.location.hostname. I will update Swagger to use window.location.hostname too.

@anouarattn I updated Swagger to use window.location.hostname. This will be available in the v5.4.

@anouarattn I've just released the v5.4. I updated settings.js.


Add step to UTM code to write out analysis images as nifti

This issue will be closed by a PR on https://github.com/kitwaremedical/utm
We see here in the Rshiny app that what we want is the data that gets written to cor-vbm-utm.Rdata.
Assuming RNifiti is installed (see #111), here is a code snippet that worked for me when testing out writing an image as nifti:
library(RNifti)
load('cor-vbm-utm.Rdata') # From within UTM analysis results directory, where `'cor-vbm-utm.Rdata'` was saved.
img = cor.res[[1]]$im$allocation # an example img to work with
writeNifti(img, 'example_nifti.nii.gz') # IDK if it compresses it when we use gz in extn, but this did work for me

We want to write out cor.res[[j]]$name (string), cor.res[[j]]$im$allocation (nifti), cor.res[[j]]$pim$allocation (nifti), cor.res[[j]]$im$transport (nifti), cor.res[[j]]$pim$transport (nifti), cor.res[[j]]$im$vbm (nifti), cor.res[[j]]$pim$vbm (nifti).
We probably want to do that just before or after this line.
See RNifti documentation here.

Closed by https://github.com/KitwareMedical/UTM/pull/5 and https://github.com/KitwareMedical/UTM/pull/7


chaining filters to find dates within a month..

so i've been trying to filter the query to get all dates within the month, but nothing comes up...  if i drop one portion of the filter or the other, it gets me more than what i'm looking for:
`
let calendar = NSCalendar(identifier: NSCalendarIdentifierGregorian)
let components = NSDateComponents()
components.year = dayOfMonth.year
components.month = dayOfMonth.month
components.day = 1
let dateFrom = calendar?.dateFromComponents(components)
print("From: (dateFrom)")
	components.month = dayOfMonth.month + 1
	let dateTo = calendar?.dateFromComponents(components)
	print("To: \(dateTo)")

	let filter = Filter
	.greaterOrEqual("buttonPressedTimestamp", value: dateFrom)
	.lessOrEqual("buttonPressedTimestamp", value: dateTo)
	let results = database.objectsForType(Event.self, matchingFilter: filter)

`
any suggestions?

Thanks for the heads-up!
I believe this issue is fixed in 1.1.0. Try updating SwiftyDB and see if it helps :)

The SQLiteValue protocol has been renamed to Value with the introduction of storeable collections


[Bug?]: Conflicting versions of package 'seroval' are created in output.

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
When I build my SolidStart app, the output produces two different versions of a package called seroval which are conflicting and cause errors when trying to deploy the app.
When running bun run build (or npm...causes the same output), the following is produced:

I am building for Vercel specifically (with the --preview vercel flag on the vinxi build command inside package.json), but the same occurs under the normal .output/... if built without this flag.
The following error occurs: SyntaxError: The requested module 'seroval' does not provide an export named 'createStream'
When running npm ls seroval, I get:

I have the current latest version of both solid start and solidjs. Here are the relevant dependencies:
"dependencies": {
       ...
        "@solidjs/meta": "^0.29.3",
        "@solidjs/router": "^0.10.5",
        "@solidjs/start": "^0.4.2",
        "clsx": "^2.1.0",
        "solid-js": "^1.8.7",
        "solid-start": "^0.3.10",
        "vinxi": "0.0.62"
       ...
    },

Expected behavior 🤔
The output to be built correctly without conflicting dependencies.
Steps to reproduce 🕹
Steps:

Create a solid app with the dependencies shown above
Build with npm/bun run build
Try to run or deploy it somewhere (vercel or locally; same error)

Context 🔦
No response
Your environment 🌎
MacOS Ventura
VSCode

Updated Solid with the lates. All versions of Seroval are the same.


How to train a single rpn model using mxnet (not faster rcnn )

How to train a single rpn model, not faster rcnn using mxnet?

One implementation of Faster RCNN uses alternative training strategy. In its first phase, it trains RPN. You can just use that.


ack links broken when weird chars are in them

Ex: http://ny-bosun01.ds.stackexchange.com/action?key=it.ping.packetloss{destination=ny-intbuild01,host=nyhq-intmon01}&type=ack breaks after "destination", so on the =.

I think we have this now, reopen if I am mistaken.

we use  [<{{.Ack}}|Acknowledge alert>] in template 'subject'
and in notification block:
     body = payload={"username": "bosun", "text": {{.|json}}}

in result we get broken links in slack without encodings symbols
actual result:
  http://mtrc01l1.root.company.com:8070/action?key=rabbitmq.errors{host=rbng01l1.root.company.com}&type=ack

expected result:
  http://mtrc01l1.root.company.com:8070//action?type=ack&key=rabbitmq.errors%7Bhost%3Drbng01l1.company.root.com%7D


Continued work on CST Location tracking.

@clement26695 You may be interested in this PR as I am continuing your work on CST Location tracking.

Part of #932

TODO:

[ ] Evaluate Flag for virtual Tokens with recovery off
- Maybe document assumptions instead that even virtual Tokens should have position info
[ ] Update docs / examples

Performance impact is very low, JSON and CSS grammars showed ~5% regression
when error recovery was disabled.
This is achieved by leverging the fact that the token input is sorted so we only update the location
information twice for each CstNode:

When creating the CstNode (looking at the next token).
When a CstNode is finalized (existing rule/subrule/nestedrule) by looking at the previous token.

Naturally this logic is not sufficent in error recovery scenarios where there could be invalid tokens/re-sync of the token stream.
In the recovery scenario we must update the location information after every terminal/nonterminal
and in that case a ~10% performance impact was measure in the JSON/CSS grammars.


WL-4939: Include citationCollectionId in stacktrace to fix broken lists

more quickly.

Because I'm surrounding the entire method with a try catch, the indentation has changed.  Not sure if there's better way.


Testing

How should these components be tested? I know there's a tests example but that only has a simple test for clamp.js. When you get to testing an actual component, jsdom will complain about the canvas element. Installing node-canvas is no walk in the park afterwards.
Any pointers?

For anyone running into this, using
var Canvas = require('canvas');

in the preprocessor works.


add screen to calibrate touch

https://github.com/user-attachments/assets/2015b0c2-660f-4255-8eae-1f0d26a2682e

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


Adding ex_terminate_on_shutdown to ec2 compute driver

To support termination of the instance if the OS shutdown command is called

Merged, thanks!


Proposal: Replace docker_command wrapper with docker-py python module

The docker-py python module can be used to invoke the Docker Engine API. This means replacing all of the subprocess commands in container.py with the docker-py API. This invariably means nuking container.py
https://github.com/docker/docker-py

I can work on this!

assigned to @jeevers


Platform independent mouse handling.

Introduced a VirtualMouseButtonFlags struct in the vks namespace. It represents virtual mouse button states.
Currently Android is still handled different as it has vastly different actions being tanken on touch.
Note: If any of the platform 'mouse' handlers operate others threads than the main one, then we really ought to add a properly guarded queue for the events.
Removed all the duplicated mouse handling code and moved it into
void handleMouseButton(const vks::VirtualMouseButtonFlags& buttonFlags, const glm::vec2& position);
void handleMouseMove(const vks::VirtualMouseButtonFlags& buttonFlags, const glm::vec2& position);
void handleMouseWheel(const float delta);
Added custom mouse event handling methods for examples that want to handle mouse events.
virtual void onMouseButton(const vks::VirtualMouseButtonFlags& buttonFlags, const glm::vec2& position);
virtual void onMouseMove(const vks::VirtualMouseButtonFlags& buttonFlags, const glm::vec2& position);
virtual void onMouseWheel(const float delta);

As I'm preparing for a cleanup of the repo I'm closing this for now. I may at some point return to this for a bigger UI and cleanup. See also #315,


YouTube playlists - probably not intentional from user

https://podrobnosti.ua/2443817-na-kivschin-cherez-vorozhij-obstrl-vinikla-pozhezha.html
This site contains a live link at the top which is a link to a YouTube playlist with 1 item which is a live stream.
Currently the 'is_live' check doesn't catch it as it is a playlist, and will proceed to download 3.7GB of stream, then create 1000's of thumbnails.
I propose a simple fix in youtubedl_archiver.py to stop downloading of playlists which stuck me as probably not what the user would want.
        if info.get('is_live', False):
            logger.warning("Live streaming media, not archiving now")
            return ArchiveResult(status="Streaming media")

       # added this catch below
        infotype = info.get('_type', False)
        if infotype is not False:
            if 'playlist' in infotype:
                logger.info('found a youtube playlist - this probably is not intended. Have put in this as edge case of a live stream which is a single item in a playlist')
                return ArchiveResult(status="Playlist")

There is probably a much more elegant way to express this!
Can submit a PR if you agree.

this can happen in multiple platforms, for example a vimeo account will exctract all of the videos from it.
Proposal: a new option in the https://github.com/bellingcat/auto-archiver/blob/main/src/auto_archiver/archivers/youtubedl_archiver.py which sets the maximum number of videos to be extracted.


Cover new incremental updating methods in user guide

Documentation updates for #18352

@bot-gradle merge

The merge queue build has started. Click here to see all failures if any.


PhotonDetectors directory is duplicated from duneprototypes

The PhotonDetectors directory in this repo is a seeming duplicate of the one in duneprototypes
We should trim this down @yangtj207 @tomjunk any preference/idea?

There is also protodune photon detector code in this repository:
https://github.com/DUNE/duneopdet/tree/develop/duneopdet/OpticalDetector


Support for celsius units

Adding support for celsius units in a custom hook.

Celsius units were implemented in the sidebar. Still have to do the rest.


Standardization of documentation and installation instructions

Review of the installation instructions is necessary:
https://github.com/PiRK/silx/blob/doc/doc/source/install.rst
Specifically:

Do we agree that we officially support only Python 2.7 and 3.5+?
I haven't been able to find a PyQt5 project on pypi. This seems to contradict a recent e-mail about availability of PyQt5 wheels. What is the easy way to install a Qt wrapper on Windows and Mac OS X?

We support Python 2.7, 3.4 and 3.5.
On windows full functionality might only be available under Python 3.5 due to the use of obsolete compilers (VS 2008) under python 2.7


CONFLUENT: Sync from apache/kafka trunk to confluentinc/kafka master (12 Jun 2022)

Merge remote-tracking branch 'apache/trunk' into sync-upstream-jun-12-2022

* apache/trunk: (52 commits)
  KAFKA-13967: Document guarantees for producer callbacks on transaction commit (#12264)
  [KAFKA-13848] Clients remain connected after SASL re-authentication f… (#12179)
  KAFKA-10000: Zombie fencing logic (#11779)
  KAFKA-13947: Use %d formatting for integers rather than %s (#12267)
  KAFKA-13929: Replace legacy File.createNewFile() with NIO.2 Files.createFile() (#12197)
  KAFKA-13780: Generate OpenAPI file for Connect REST API (#12067)
  KAFKA-13917: Avoid calling lookupCoordinator() in tight loop (#12180)
  KAFKA-10199: Implement removing active and standby tasks from the state updater (#12270)
  MINOR: Update Scala to 2.13.8 in gradle.properties (#12273)
  MINOR: add java 8/scala 2.12 deprecation info in doc (#12261)
  ...

 Conflicts:
        gradle.properties

Trivial conflict in gradle.properties because version is different in confluentinc/kafka
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@jolshan Thanks for the review, merging.


ZEP0001 to active

This moves ZEP0001 to the active directory and updates the status in the document.

Could there be a redirect from the draft URL to the active URL?

Thanks for looking this over and sending the PR, @jhamman.
Based on the discussions from previous ZEP meetings, we decided to add a contributors section in the ZEP0001 to include the names of community members who helped us finalise the spec.
I've added #43 to include the list and also changed the status from Draft → Accepted.
Please have a look at it. Thank you!

Thanks @MSanKeys963 -- do you want to close this then? It looks like you've started off a fresh branch so only one of these should go in.

@jhamman -  Apologies for not updating this branch.
Let's close this and continue over at #43.


tagged releases corresponding to compatible mesos versions

Problem:  I'm running mesos version X.  What git SHA should I be using?

Initially, I'd like to see a tag for:
0.22.0
0.23.0 (after https://github.com/mesos/mesos-go/pull/159 is merged in and more testing is performed)
new versions after they have been properly tested

Merged with #166.


renderer: set unordered_map static

This is not critical since it's used in debug command print functions, but why not. Those unordered_map are never modified so there is no need to rebuild them on every function call.

Both GCC and Clang error out if I add const to an unordered_map.

To use it with const you can do map.at(key) instead of map[key]. This crashes if the key is missing though, so maybe it's better not to.

I always check for the key not missing (was not expecting to not crash if the key is missing anyway), so maybe I can try that.

I now use const and .at(). It is useful to check for unknown keys and report debug logs if it happens.


auto_increment keyword used in apimgt mssql db scripts

Description:
User cannot run existing api manager database scripts on a mssql database.
AUTO_INCREMENT keyword has been used in SP_TEMPLATE table.
Affected Product Version:
wso2am-2.6.0-beta2-SNAPSHOT
OS, DB, other environment details and versions:
MSSQL
Steps to reproduce:
Execute dbscript/apimgt/mssql.sql script on a mssql database.

Fixed with https://github.com/wso2/carbon-apimgt/pull/5653


aelf-Studio: Add Description and Instruction in Readme file

Add description, all featured and usage of instruction in readme file

Here is the PR - https://github.com/yongenaelf/vscode-aelf-studio/pull/1


0.23 JVMism cleanups

Setting us up for a JVMism free 1.0, either directly or by deprecation.

Do you want to try to squeeze the Dns in before merging this?  Do we need to wait on that to release 0.23?

No, the Dns can come later. No need to block 0.23 on that.

But I would still prefer to get https://github.com/typelevel/fs2/pull/2655 out first. What's the timeline for the release train?

0.21 is ready now.  I'm gathering notes for 0.22.  Nothing says they need to go together, but it's frustrating when old versions get shiny things first.

https://github.com/typelevel/fs2/pull/2655 is on the way.

I bumped fs2 to a hash so I could make the final changes.

Seems there's something changed in fs2 since 3.1.3 that causes ember-server to fail tests. Ignoring this PR here, if on series/0.23 I bump fs2 to 3.1-69-b2a90a1 basically every test fails with:
==> X org.http4s.ember.server.EmberServerSuite.server responds to requests  0.015s java.net.BindException: Address already in use

Ok, I tracked it down to https://github.com/typelevel/fs2/pull/2644.


Scala 2.12.20 (was .19)

I'll un-draft after 2.12.20 has been announced
CI will fail for now because some dependencies haven't published yet (kind-projector, scalameta)

it seems from https://github.com/scalameta/scalameta/issues/3950 that the oldest semanticdb version available for 2.12.20 is 4.9.3. wasn't sure whether to go with that or upgrade all the way to 4.9.9; let's try 4.9.9 and see how CI feels about it


Port nginx-buildpack resolver code to the Paketo NGINX Buildpack

We did some work in the CF NGINX Buildpack to support this (https://github.com/cloudfoundry/nginx-buildpack/pull/12). We should look into supporting this in the NGINX Paketo buildpack

@dwillist could you update this? Not sure if this was a CF specific feature. If it is, let's delete.

This feature is also useful for kube-dns. CC: @kvedurmu

@sclevine I noticed the needs-triage label was removed. Should we keep this issue open?

Still seems important to me :)
Not sure why the label was removed

Bump @paketo-buildpacks/web-servers-maintainers and @ryanmoran what is the state of the world on this feature given my understanding of what we are hoping to support with user interpolation.


Used with logseq-plugin-link-preview cause preview transparent background and weird font styles

Info:

OS: macOS 13.1
Logseq ver: 0.8.18
Plugin ver: 3.6.7
[ ] ⚠ Do i have issue with DISABLED my custom.css?
[ ] ⚠ Do i have the same on default theme?

Description:
When logseq-plugin-link-preview and logseq-awesome-styler both enabled, mouse over a link the preview card renders a the title and description with a transparent background, no borders and weird font styles.
Same issue has been opened in logseq-plugin-link-preview: pengx17/logseq-plugin-link-preview#122
To Reproduce:
Enable logseq-plugin-link-preview and logseq-awesome-styler at same time.
Screenshots

PR created https://github.com/pengx17/logseq-plugin-link-preview/pull/126


Download CSV/etc Directly from Website

Although this is a pretty cool project it looks like you can download the CSV.
On the main page you can click on Accounts > your account > Scroll to bottom under Transactions > Change time period to time period you desire > On the right side you will see an export option > choose CSV or Text or QFX or ... This is for <citi.com>. So, I'm not sure if this would work for you or not.

lol, just noticed this was written 4/5 years ago! :-)

Thanks for letting me know @jon49! That option might have been around back then as well, and I might just have missed it.
I do have another project that I still use which takes that data and sticks it into a Google Sheet (https://github.com/matthewrwilton/citibank-statement-to-sheets) and occasionally I have to make an adjustment when something in the PDF changes. Next time that happens I think I'll rewrite it to use the CSV download.


Feature/use new hashing service

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

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

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Test A
[ ] Test B

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

Since we're going for a more fair distance metric, it would also make sense to update the way libp2p keys are created. Right now keys are created at random, which means with a smaller network there is the possibility of having uneven distribution of nodes on the ring.
With this update it should be possible to predict a spot on the ring which maximizes chance to store assets. We can then create some fixed number of keys (ex. 1000) and pick the one that has position closest to this spot.
I would suggest to go with such an update sooner than later so that the gnosis sharding table has a better node distribution from the start.


Add and define code-style rules in .editorconfig

I've initiated the process of integrating and refining our .editorconfig to align with the code-style rules recommended by Microsoft and the broader .NET community. This action aims to enhance consistency and maintainability across our codebase, leveraging best practices from notable .NET repositories like dotnet/runtime, dotnet/aspnetcore, and dotnet/efcore.
Your Feedback is Crucial: Before we finalize and enforce these configurations, I highly encourage everyone to review the proposed .editorconfig, and share any feedback or suggestions. Your insights are invaluable in ensuring that our coding standards meet our collective needs and preferences.

would you be interested in setting up GitHub Actions + validation of the editorconfig?

would you be interested in setting up GitHub Actions + validation of the editorconfig (#12)?

Of course, you can assign this task to me. Also, please keep in mind that I would like to be assigned the issue related to the implementation of MSA.BuildingBlocks.Logging. I have already started planning the implementation."


Crash when loading on server

crash-2021-08-01_18.24.51-fml.txt

will be fixed in the next version. for now you can use this jar on your server (only required on the servers, players can use whatever)
https://cdn.discordapp.com/attachments/861376036331192330/871411495622283274/createautomated-1.16.5-1.2.1a.jar

Thanks!


refactor(local-server-tests): Clean-up dependencies

Description
This is a private package that only runs some tests. It has no need of production dependencies, so this PR does two things:

Move all its dependencies to devDependencies
Removes several dependencies that were not used

Reviewer Guidance
The review process is outlined on this wiki page.

I like it - I tried to do similar for azure-end-to-end-tests in #21389 but never had time to fully deal with the questions that were raised for install. Should it get revived?


Correctly propagate exceptions from inbound operations in all cases

Motivation:
In AbstractChannelHandlerContext we had some code where we tried to guard against endless loops caused by exceptions thrown by exceptionCaught(...) that would trigger exceptionCaught again. This code was proplematic for two reasons:

It is quite expensive as we need to compare all the stacks
We may end up not notify another handlers exceptionCaught(...) if in our exeuction stack we triggered actions that will cause an exceptionCaught somewhere else in the pipeline

Modifications:

Just remove the detection code as we already handle everything correctly when we invoke exceptionCaught(...)
Add unit tests

Result:
Ensure we always notify correctly and also fixes performance issue reported as https://github.com/netty/netty/issues/10165

👍

@slandelle any other comments ?

@netty-bot test this please

@netty-bot test this please

@normanmaurer any ETA for next verison bump? 🙏

@ninja- this week


Console Command too Presumptuous

Currently the console command will try to run pry -r ./config/boot.rb if it detects the pry binary (if it couldn't find rails). It's unlikely that all projects will have a ./config/boot, for example a gem. It might be better to use bundlers option to set the console binary.
Perhaps this would a be better implementation:
if [ -f script/console ]; then
  script/console
else
  if hash pry 2>/dev/null ; then
    bundle config console pry
  fi

  bundle/console
fi

Resolved by #34


Write permissions... again

i have similar issues whne it comes to writing files
i run this on a openmediavault machine using docker
i run the emoncms logging software and with mysql store it works fine, but when it needs to create files and directories it stops
ERROR: Feed could not be created, could not write meta data file fopen(/srv/mergerfs/Data/Emoncms/docker-compose-lamp/emoncmsdata/phpfina/80005.meta): Failed to open stream: No such file or directory
i tried to move the emoncmsdata folder inside the emoncms folder i created in www... still the same issue
# Please Note:
# In PHP Versions <= 7.4 MySQL8 is not supported due to lacking pdo support

# To determine the name of your containers
COMPOSE_PROJECT_NAME=lamp

# Possible values: php54, php56, php71, php72, php73, php74, php8, php81
PHPVERSION=php8
DOCUMENT_ROOT=./www
APACHE_DOCUMENT_ROOT=/var/www/html
VHOSTS_DIR=./config/vhosts
APACHE_LOG_DIR=./logs/apache2
PHP_INI=./config/php/php.ini
SSL_DIR=./config/ssl

# PHPMyAdmin
UPLOAD_LIMIT=512M
MEMORY_LIMIT=512M

# Xdebug
XDEBUG_LOG_DIR=./logs/xdebug
XDEBUG_PORT=9003
#XDEBUG_PORT=9000

# Possible values: mysql57, mysql8, mariadb103, mariadb104, mariadb105, mariadb106
#
# For Apple Silicon User:
# Please select Mariadb as Database. Oracle doesn't build their SQL Containers for the arm Architecure

DATABASE=mysql8
MYSQL_INITDB_DIR=./config/initdb
MYSQL_DATA_DIR=./data/mysql
MYSQL_LOG_DIR=./logs/mysql

# If you already have the port 80 in use, you can change it (for example if you have Apache)
HOST_MACHINE_UNSECURE_HOST_PORT=8081

# If you already have the port 443 in use, you can change it (for example if you have Apache)
HOST_MACHINE_SECURE_HOST_PORT=443

# If you already have the port 3306 in use, you can change it (for example if you have MySQL)
HOST_MACHINE_MYSQL_PORT=3306

# If you already have the port 8080 in use, you can change it (for example if you have PMA)
HOST_MACHINE_PMA_PORT=8082
HOST_MACHINE_PMA_SECURE_PORT=8443

# If you already has the port 6379 in use, you can change it (for example if you have Redis)
HOST_MACHINE_REDIS_PORT=6379

# MySQL root user password
MYSQL_ROOT_PASSWORD=tiger

# Database settings: Username, password and database name
#
# If you need to give the docker user access to more databases than the "docker" db
# you can grant the privileges with phpmyadmin to the user.
MYSQL_USER=docker
MYSQL_PASSWORD=docker
MYSQL_DATABASE=docker

docker exec -it CONTAINER_HASH_NAME bash
chown -R www-data:www-data ./

docker exec -it CONTAINER_HASH_NAME bash cd /var/www/html chown -R www-data:www-data ./

Thank you very much, it worked for me!

docker exec -it CONTAINER_HASH_NAME bash cd /var/www/html chown -R www-data:www-data ./

is there another solution? i just code a simple php application with upload feature, but i got Failed to open stream : permission denied, so i cant move uploaded files


Show name of intent(s) that lack enough train examples

I think Rasa Intent Classification Component should output the name of the intent(s) it warns about that lack enough training data. This would enable easy identification of problem intent(s)

Hi There.
I interested working on this issue. Could anyone describe more? Should I add new endpoint to lists all intents that lack of training examples

Hello, I'd like to work on this as well-- has the situation changed at all since the issue was posted?

@madimov I haven't seen any work on this, so I'd be glad if you give it a try 👍

@tmbo  Great, I'm on it-- brainstorming an approach / solution and will comment back here soon

@tmbo One approach I can see so far is to:

catch the UndefinedMetricWarning (mentioned in issue #288 ) issued by sklearn/metrics/classification.py when the F-score is ill-defined due to insufficient training examples.
identify the class that sklearn is processing when the warning arises. I am not sure how feasible this is, considering it may involve fiddling with sklearn's functions for them to provide such information.

In a few discussions about catching out of scope intents (e.g. issue #387 ), confidence thresholds have been suggested. At first glance, this seemed an (incomplete) solution to this issue as well, because in most cases of low confidence, more training examples are likely to help. That is larger issue, however, and not foolproof.
Do you have any thoughts on a preferred approach?

@tmbo @madimov Is this issue solved yet?

@nahidalam Not yet-- didn't get feedback for my suggestions, but feel free to take on the task!

unable add more intents in rasa_nlu even using rasa-nlu trainer ? need help

I would really like to see this feature, as I currently get a series of 12 UndefinedMetricWarning: F-score is ill-defined warnings which I don't know how to respond to.

@nahidalam or anyone who wants to take this one (sorry I wasn't aware you are waiting for a reply here). I guess catching the warning and tryng to figure out which intent caused it is a good approach :+1:

This may be of some use if anyone wants to implement this: https://stackoverflow.com/questions/43162506/undefinedmetricwarning-f-score-is-ill-defined-and-being-set-to-0-0-in-labels-wi

this question was also asked on SO, here's my answer: https://stackoverflow.com/a/51738593/1408476 it may help anyone who decides to tackle this.

this functionality exists now


backporting log4j to main

Signed-off-by: Shenoy Pratik<EMAIL_ADDRESS>Description
Update release bump and log4j changes from 1.2.3
Issues Resolved
updated workflow, gradle and release notes
Check List

[ ] New functionality includes testing.

[ ] All tests pass, including unit test, integration test and doctest

[ ] New functionality has been documented.

[ ] New functionality has javadoc added
[ ] New functionality has user manual doc added

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #348 (6f3437c) into main (106dae5) will increase coverage by 62.91%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           main     #348       +/-   ##
=========================================
+ Coverage      0   62.91%   +62.91%
=========================================
  Files         0       10       +10
  Lines         0      658      +658
  Branches      0      118      +118
=========================================
+ Hits          0      414      +414
- Misses        0      191      +191
- Partials      0       53       +53

Flag
Coverage Δ

query-workbench
62.91% <ø> (?)

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

Impacted Files
Coverage Δ

workbench/public/components/SQLPage/SQLPage.tsx
100.00% <0.00%> (ø)

workbench/public/components/Main/main.tsx
53.00% <0.00%> (ø)

...h/public/components/QueryLanguageSwitch/Switch.tsx
85.71% <0.00%> (ø)

workbench/public/utils/PanelWrapper.tsx
100.00% <0.00%> (ø)

workbench/public/components/app.tsx
0.00% <0.00%> (ø)

workbench/public/application.tsx
0.00% <0.00%> (ø)

workbench/public/components/Header/Header.tsx
100.00% <0.00%> (ø)

...ch/public/components/QueryResults/QueryResults.tsx
61.60% <0.00%> (ø)

workbench/public/components/PPLPage/PPLPage.tsx
56.52% <0.00%> (ø)

...ublic/components/QueryResults/QueryResultsBody.tsx
68.68% <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 106dae5...6f3437c. Read the comment docs.


Fix deprecation warning for pandas.tslib

At the moment, running cufflinks with Plotly in a Jupyter notebook will pop up a nasty deprecation warning for pandas.tslib. As far as I can tell, this was the only use. This change removes the deprecation warning and, as far as I can tell, matches currently plotly behaviour.

HI @apetresc - thank you for this. This was solved on some pending updates. This should be fine now.


[BACKLOG-20601] - moving RecordsFromStream to main kettle because it …

…is now needed by the base streaming dialog

Build Completed
:x: This pull request has errors. They will need to be addressed before it can be accepted. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -Dsurefire.runOrder=alphabetical -B -fn -f 'plugins/file-stream/pom.xml' -pl '.' -P '!assemblies' -amd clean install && mvn -B -f 'plugins/file-stream/pom.xml' -pl '.' -P '!assemblies' -amd site
mvn -Dsurefire.runOrder=alphabetical -B -fn -f 'pom.xml' -pl 'ui,engine' -P '!assemblies' -amd clean install && mvn -B -f 'pom.xml' -pl 'ui,engine' -P '!assemblies' -amd site

Cleanup Commands
mvn -B -f 'plugins/file-stream/pom.xml' -pl '.' -P '!assemblies' -amd build-helper:remove-project-artifact && mvn -B -f 'pom.xml' -pl 'ui,engine' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  engine/src/main/java/org/pentaho/di/trans/steps/recordsfromstream/RecordsFromStream.java
  engine/src/main/java/org/pentaho/di/trans/steps/recordsfromstream/RecordsFromStreamData.java
  engine/src/main/java/org/pentaho/di/trans/steps/recordsfromstream/RecordsFromStreamMeta.java
  engine/src/main/resources/kettle-steps.xml
  engine/src/main/resources/org/pentaho/di/trans/steps/recordsfromstream/messages/messages_en_US.properties
  plugins/file-stream/src/main/java/org/pentaho/di/trans/step/filestream/FileStreamDialog.java
  ui/src/main/java/org/pentaho/di/ui/trans/step/BaseStreamingDialog.java
  ui/src/main/java/org/pentaho/di/ui/trans/steps/recordsfromstream/RecordsFromStreamDialog.java
  ui/src/main/resources/ui/images/get-records-from-stream.svg

Newly Broken Tests:
org.pentaho.di.trans.streaming.common.BlockingQueueStreamSourceTest.testError:
:red_circle: java.lang.NullPointerException
java.lang.NullPointerException
	at org.pentaho.di.trans.streaming.common.BlockingQueueStreamSourceTest.testError(BlockingQueueStreamSourceTest.java:177)

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes: <0.1% (click to expand)
:new: org.pentaho.di.trans.steps.aggregaterows.AggregateRows

Branch Coverage: 36.2% :exclamation:
Complexity Coverage: 30.3% :exclamation:
Instruction Coverage: 55.2% :exclamation:
Line Coverage: 60.5% :exclamation:

:new: org.pentaho.di.trans.steps.aggregaterows.AggregateRowsMeta

Branch Coverage: 0% :exclamation:
Complexity Coverage: 2.2% :exclamation:
Instruction Coverage: 10.4% :exclamation:
Line Coverage: 7.6% :exclamation:
Method Coverage: 4.5% :exclamation:

:new: org.pentaho.di.ui.trans.steps.aggregaterows.AggregateRowsDialog

Coverage: 0% :exclamation:

:new: org.pentaho.di.trans.steps.abort.Abort

Branch Coverage: 38.9% :exclamation:
Complexity Coverage: 38.5% :exclamation:
Instruction Coverage: 68.8% :exclamation:
Line Coverage: 75.7% :exclamation:

:new: org.pentaho.di.trans.steps.abort.AbortData

Coverage: 0% :exclamation:

:new: org.pentaho.di.trans.steps.abort.AbortMeta

Branch Coverage: 25% :exclamation:
Complexity Coverage: 59.1% :exclamation:
Instruction Coverage: 63.2% :exclamation:
Line Coverage: 62.9% :exclamation:
Method Coverage: 65% :exclamation:

:new: org.pentaho.di.trans.steps.analyticquery.AnalyticQuery

Coverage: 0% :exclamation:

:new: org.pentaho.di.trans.steps.analyticquery.AnalyticQueryData

Coverage: 0% :exclamation:

:new: org.pentaho.di.trans.steps.analyticquery.AnalyticQueryMeta

Branch Coverage: 52.2% :exclamation:
Complexity Coverage: 59.3% :exclamation:
Instruction Coverage: 67.2% :exclamation:
Line Coverage: 65.6% :exclamation:
Method Coverage: 71% :exclamation:

:new: org.pentaho.di.trans.steps.append.Append

Coverage: 0% :exclamation:

:new: org.pentaho.di.trans.steps.append.AppendData

Coverage: 0% :exclamation:

:new: org.pentaho.di.trans.steps.append.AppendMeta

Branch Coverage: 0% :exclamation:
Complexity Coverage: 7.1% :exclamation:
Instruction Coverage: 1.7% :exclamation:
Line Coverage: 4.1% :exclamation:
Method Coverage: 10.5% :exclamation:

:new: org.pentaho.di.trans.steps.autodoc.AutoDoc

Coverage: 0% :exclamation:

:new: org.pentaho.di.trans.steps.autodoc.AutoDocData

Coverage: 0% :exclamation:

:new: org.pentaho.di.trans.steps.autodoc.AutoDocMeta

Branch Coverage: 0% :exclamation:
Complexity Coverage: 64.2% :exclamation:
Instruction Coverage: 60.7% :exclamation:
Line Coverage: 57.1% :exclamation:

Note: The list of offending coverage changes extends beyond the presented results and was truncated to prevent reaching the comment size limit.

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -Dsurefire.runOrder=alphabetical -B -fn -f 'plugins/file-stream/pom.xml' -pl '.' -P '!assemblies' -amd clean install && mvn -B -f 'plugins/file-stream/pom.xml' -pl '.' -P '!assemblies' -amd site
mvn -Dsurefire.runOrder=alphabetical -B -fn -f 'pom.xml' -pl 'ui,engine' -P '!assemblies' -amd clean install && mvn -B -f 'pom.xml' -pl 'ui,engine' -P '!assemblies' -amd site

Cleanup Commands
mvn -B -f 'plugins/file-stream/pom.xml' -pl '.' -P '!assemblies' -amd build-helper:remove-project-artifact && mvn -B -f 'pom.xml' -pl 'ui,engine' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  engine/src/main/java/org/pentaho/di/trans/steps/recordsfromstream/RecordsFromStream.java
  engine/src/main/java/org/pentaho/di/trans/steps/recordsfromstream/RecordsFromStreamData.java
  engine/src/main/java/org/pentaho/di/trans/steps/recordsfromstream/RecordsFromStreamMeta.java
  engine/src/main/resources/kettle-steps.xml
  engine/src/main/resources/org/pentaho/di/trans/steps/recordsfromstream/messages/messages_en_US.properties
  engine/src/test/java/org/pentaho/di/trans/streaming/common/BlockingQueueStreamSourceTest.java
  plugins/file-stream/src/main/java/org/pentaho/di/trans/step/filestream/FileStreamDialog.java
  ui/src/main/java/org/pentaho/di/ui/trans/step/BaseStreamingDialog.java
  ui/src/main/java/org/pentaho/di/ui/trans/steps/recordsfromstream/RecordsFromStreamDialog.java
  ui/src/main/resources/ui/images/get-records-from-stream.svg

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes: <0.1% (click to expand)
:new: org.pentaho.di.trans.steps.aggregaterows.AggregateRows

Branch Coverage: 36.2% :exclamation:
Complexity Coverage: 30.3% :exclamation:
Instruction Coverage: 55.2% :exclamation:
Line Coverage: 60.5% :exclamation:

:new: org.pentaho.di.trans.steps.aggregaterows.AggregateRowsMeta

Branch Coverage: 0% :exclamation:
Complexity Coverage: 2.2% :exclamation:
Instruction Coverage: 10.4% :exclamation:
Line Coverage: 7.6% :exclamation:
Method Coverage: 4.5% :exclamation:

:new: org.pentaho.di.ui.trans.steps.aggregaterows.AggregateRowsDialog

Coverage: 0% :exclamation:

:new: org.pentaho.di.trans.steps.abort.Abort

Branch Coverage: 38.9% :exclamation:
Complexity Coverage: 38.5% :exclamation:
Instruction Coverage: 68.8% :exclamation:
Line Coverage: 75.7% :exclamation:

:new: org.pentaho.di.trans.steps.abort.AbortData

Coverage: 0% :exclamation:

:new: org.pentaho.di.trans.steps.abort.AbortMeta

Branch Coverage: 25% :exclamation:
Complexity Coverage: 59.1% :exclamation:
Instruction Coverage: 63.2% :exclamation:
Line Coverage: 62.9% :exclamation:
Method Coverage: 65% :exclamation:

:new: org.pentaho.di.trans.steps.analyticquery.AnalyticQuery

Coverage: 0% :exclamation:

:new: org.pentaho.di.trans.steps.analyticquery.AnalyticQueryData

Coverage: 0% :exclamation:

:new: org.pentaho.di.trans.steps.analyticquery.AnalyticQueryMeta

Branch Coverage: 52.2% :exclamation:
Complexity Coverage: 59.3% :exclamation:
Instruction Coverage: 67.2% :exclamation:
Line Coverage: 65.6% :exclamation:
Method Coverage: 71% :exclamation:

:new: org.pentaho.di.trans.steps.append.Append

Coverage: 0% :exclamation:

:new: org.pentaho.di.trans.steps.append.AppendData

Coverage: 0% :exclamation:

:new: org.pentaho.di.trans.steps.append.AppendMeta

Branch Coverage: 0% :exclamation:
Complexity Coverage: 7.1% :exclamation:
Instruction Coverage: 1.7% :exclamation:
Line Coverage: 4.1% :exclamation:
Method Coverage: 10.5% :exclamation:

:new: org.pentaho.di.trans.steps.autodoc.AutoDoc

Coverage: 0% :exclamation:

:new: org.pentaho.di.trans.steps.autodoc.AutoDocData

Coverage: 0% :exclamation:

:new: org.pentaho.di.trans.steps.autodoc.AutoDocMeta

Branch Coverage: 0% :exclamation:
Complexity Coverage: 64.2% :exclamation:
Instruction Coverage: 60.7% :exclamation:
Line Coverage: 57.1% :exclamation:

Note: The list of offending coverage changes extends beyond the presented results and was truncated to prevent reaching the comment size limit.

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -Dsurefire.runOrder=alphabetical -B -fn -f 'plugins/file-stream/pom.xml' -pl '.' -P '!assemblies' -amd clean install && mvn -B -f 'plugins/file-stream/pom.xml' -pl '.' -P '!assemblies' -amd site
mvn -Dsurefire.runOrder=alphabetical -B -fn -f 'pom.xml' -pl 'ui,engine' -P '!assemblies' -amd clean install && mvn -B -f 'pom.xml' -pl 'ui,engine' -P '!assemblies' -amd site

Cleanup Commands
mvn -B -f 'plugins/file-stream/pom.xml' -pl '.' -P '!assemblies' -amd build-helper:remove-project-artifact && mvn -B -f 'pom.xml' -pl 'ui,engine' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  engine/src/main/java/org/pentaho/di/trans/steps/recordsfromstream/RecordsFromStream.java
  engine/src/main/java/org/pentaho/di/trans/steps/recordsfromstream/RecordsFromStreamData.java
  engine/src/main/java/org/pentaho/di/trans/steps/recordsfromstream/RecordsFromStreamMeta.java
  engine/src/main/resources/kettle-steps.xml
  engine/src/main/resources/org/pentaho/di/trans/steps/recordsfromstream/messages/messages_en_US.properties
  engine/src/test/java/org/pentaho/di/trans/streaming/common/BlockingQueueStreamSourceTest.java
  plugins/file-stream/src/main/java/org/pentaho/di/trans/step/filestream/FileStreamDialog.java
  ui/src/main/java/org/pentaho/di/ui/trans/step/BaseStreamingDialog.java
  ui/src/main/java/org/pentaho/di/ui/trans/steps/recordsfromstream/RecordsFromStreamDialog.java
  ui/src/main/resources/org/pentaho/di/ui/trans/step/messages/messages_en_US.properties
  ui/src/main/resources/ui/images/get-records-from-stream.svg

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes: <0.1% (click to expand)
:new: org.pentaho.di.trans.steps.aggregaterows.AggregateRows

Branch Coverage: 36.2% :exclamation:
Complexity Coverage: 30.3% :exclamation:
Instruction Coverage: 55.2% :exclamation:
Line Coverage: 60.5% :exclamation:

:new: org.pentaho.di.trans.steps.aggregaterows.AggregateRowsMeta

Branch Coverage: 0% :exclamation:
Complexity Coverage: 2.2% :exclamation:
Instruction Coverage: 10.4% :exclamation:
Line Coverage: 7.6% :exclamation:
Method Coverage: 4.5% :exclamation:

:new: org.pentaho.di.ui.trans.steps.aggregaterows.AggregateRowsDialog

Coverage: 0% :exclamation:

:new: org.pentaho.di.trans.steps.abort.Abort

Branch Coverage: 38.9% :exclamation:
Complexity Coverage: 38.5% :exclamation:
Instruction Coverage: 68.8% :exclamation:
Line Coverage: 75.7% :exclamation:

:new: org.pentaho.di.trans.steps.abort.AbortData

Coverage: 0% :exclamation:

:new: org.pentaho.di.trans.steps.abort.AbortMeta

Branch Coverage: 25% :exclamation:
Complexity Coverage: 59.1% :exclamation:
Instruction Coverage: 63.2% :exclamation:
Line Coverage: 62.9% :exclamation:
Method Coverage: 65% :exclamation:

:new: org.pentaho.di.trans.steps.analyticquery.AnalyticQuery

Coverage: 0% :exclamation:

:new: org.pentaho.di.trans.steps.analyticquery.AnalyticQueryData

Coverage: 0% :exclamation:

:new: org.pentaho.di.trans.steps.analyticquery.AnalyticQueryMeta

Branch Coverage: 52.2% :exclamation:
Complexity Coverage: 59.3% :exclamation:
Instruction Coverage: 67.2% :exclamation:
Line Coverage: 65.6% :exclamation:
Method Coverage: 71% :exclamation:

:new: org.pentaho.di.trans.steps.append.Append

Coverage: 0% :exclamation:

:new: org.pentaho.di.trans.steps.append.AppendData

Coverage: 0% :exclamation:

:new: org.pentaho.di.trans.steps.append.AppendMeta

Branch Coverage: 0% :exclamation:
Complexity Coverage: 7.1% :exclamation:
Instruction Coverage: 1.7% :exclamation:
Line Coverage: 4.1% :exclamation:
Method Coverage: 10.5% :exclamation:

:new: org.pentaho.di.trans.steps.autodoc.AutoDoc

Coverage: 0% :exclamation:

:new: org.pentaho.di.trans.steps.autodoc.AutoDocData

Coverage: 0% :exclamation:

:new: org.pentaho.di.trans.steps.autodoc.AutoDocMeta

Branch Coverage: 0% :exclamation:
Complexity Coverage: 64.2% :exclamation:
Instruction Coverage: 60.7% :exclamation:
Line Coverage: 57.1% :exclamation:

Note: The list of offending coverage changes extends beyond the presented results and was truncated to prevent reaching the comment size limit.

@pentaho/ackbar please review


hipMemcpy problem: Data_d cannot be accessed on the device side

hello,everyone.
I would like to ask a question about hipMemcpy.I hope someone can help me with this.
The question are as follows:
I want to copy a table to the device side and get the key of the table on the device side.
error:
Memory access fault by GPU node-8 (Agent handle: 0x9bc790) on address 0xb05000. Reason: Page not present or supervisor privilege.
code as below:
dict struct as below:
typedef struct dictEntry {
void *key;
void *val;
struct dictEntry *next;
} dictEntry;
typedef struct dict {
dictEntry **table;
dictType *type;
unsigned long size;
unsigned long sizemask;
unsigned long used;
void *privdata;
} dict;
dictEntry entry;
hipMalloc((dictEntry*)&entry, sizeof(ht->table[i]));
hipMemcpy(entry, ht->table[i], sizeof(ht->table[i]), hipMemcpyHostToDevice);
hipLaunchKernelGGL(test,1,5,0,0, key, entry);
global void test(char *key1, dictEntry entry) {
while(entry){
int i =0;
auto key2 = (char)entry->key;
while(key1[i] == key2[i] && i < 24){  // memory access fault
i++;
}
....
}
on host side, I can get the vallue of  entry->key[i] ,but on test kernel, I can't access entry->key[i].
If you have a solution or a good suggestion, please feel free to communicate.
I look forward to hearing from you!

A complete example might be helpful.

@xianwujie  Hi, were you able to resolve this issue on the latest HIP? If so can we close this ticket?


Cannot log a normal variable

Environment

Server - Azure Pipelines
Agent - Hosted VS2017

Issue Description

as you can see, the account has been replaced with *, but account is just a normal variable, what is your display rules about what kind of variable should be replaced with *

@928PJY Do you have your variable set as secret? Any variable marked as secret will be masked out, but other variables will not.
This page might give you some more info: https://docs.microsoft.com/en-us/azure/devops/pipelines/process/variables?view=azure-devops&tabs=yaml%2Cbatch#secret-variables

No, it is not a secret variable, it is just a variable I created from code in Nodejs. here is a sample
const config = require('config.json');
console.log(config.account);

@joshmgross any update?

@928PJY Is the variable the same value as another secret variable?
Any variable marked as secret will be masked from the logs

Thanks @joshmgross, That's a good point, it has the same value with the variable restored from Azure key vault, which will be automatically set as a secret variable, right? so this is a by-design behavior? is there any workaround for this or I have to remove it from key vault if I want to output the value.

@928PJY Yeah, it's by design. If a value is found in KeyVault (or is otherwise marked secret), it will get masked from the logs, regardless.


Helper for controlling anger of Control node can't be off

Godot version:

3.2.dev 755b58938
OS/device including version:

Kubuntu 19.04
Issue description:

Helper for controlling anger of Control node can't be off
Steps to reproduce:
try to off helper

Minimal reproduction project:

Yeah I changed that on purpose as it was confusing for users.
Do you think it deserves a dedicated checkbox ? I mean, for me anchors are as important as drag handles for control nodes, so I am not sure it should be allowed to disable their display.

Sorry, had to :P

@groud it was coming from this.
I was trying to resize the control but the anchor is grabbed...

@volzhs ah indeed this is more annoying. But it could be solved by charging the anchor input priority

that is enough for me i think


[Bug] Tokenizer's BOS/EOS/PAD not set for inference

Following https://discord.com/channels/1104757954588196865/1111279858136383509/1113729100763381804, a user saw that the tokenizer's bos/eos/pad is not set when inference mode.
We can fix this by just setting this following yaml.
https://github.com/OpenAccess-AI-Collective/axolotl/blob/288fd62431be84a7112fd461feeb9322f1177d3c/scripts/finetune.py#L66-L68
We need to update this as Alpaca is not the only method now.
Depends on https://github.com/OpenAccess-AI-Collective/axolotl/issues/64

Actually it's also seen during finetuning:
Setting ds_accelerator to cuda (auto detect)
WARNING:root:`trust_remote_code` is set to true. Please make sure that you reviewed the remote code/model.
INFO:root:loading tokenizer... tiiuae/falcon-7b
Using bos_token, but it is not set yet.
Using pad_token, but it is not set yet.
Using unk_token, but it is not set yet.
INFO:root:Loading prepared dataset from disk at last_run_prepared/31a4e867d804a957707db033c9abcd13...
INFO:root:Prepared dataset loaded from disk...
INFO:root:loading model and peft_config...
Loading checkpoint shards: 100%|██████████████████| 2/2 [00:16<00:00,  8.49s/it]
INFO:root:converting PEFT model w/ prepare_model_for_int8_training

@utensil , Which dataset format are you using?

@utensil , Which dataset format are you using?

alpaca:chat
as in https://github.com/OpenAccess-AI-Collective/axolotl/pull/132

we should probably change these to info and move it to after we add the special tokens from the config
https://github.com/OpenAccess-AI-Collective/axolotl/blob/main/src/axolotl/utils/models.py#L53-L56

Doesn't https://github.com/OpenAccess-AI-Collective/axolotl/blob/main/src/axolotl/utils/models.py#L68-L70 already solve this?

Hm, yes. I think the problem is due to that code block in the first post. It may overwrite previous setting. I think just removing it is enough? The main work is in https://github.com/OpenAccess-AI-Collective/axolotl/issues/64

If we were to remove the block in the first post, we need to make sure llama configs/tokenizers have those added in somewhere to prevent a regression.

If I understand it right, the code from https://github.com/OpenAccess-AI-Collective/axolotl/pull/180
should be ok as well for training, allowing to define only the yet undefined tokens, with config keeping precedence in case of Falcon for isntance.


Typings throwing error during compile. helper.d.ts

🐛 Bug Report
I am trying to use react-spring and react-use-gesture in a react application and specifically useGesture() and useSpring() but when trying to run the application, the typescript compiler throws an error about shared/helpers.d.ts typings in the react-spring package. Below is the error being thrown.
Environment
react-spring: 9.0.0-beta.22 //This installs by default
react-use-gesture: 5.1.2
react: 16.8.4
vec-la: 1.5.0

Error
Type error: '>' expected.  TS1005

     6 | export declare const is: {
     7 |     arr: IsArray;
  >  8 |     obj: <T extends any>(a: T) => a is Exclude<T & Indexable<any>, Function | readonly any[]>;
       |                                                                                ^
     9 |     fun: (a: unknown) => a is Function;
    10 |     str: (a: unknown) => a is string;
    11 |     num: (a: unknown) => a is number;

Reproduction
I am following an example from react-springs docs, here is how I am using the hooks:
import {useSpring, animated} from 'react-spring';
import {useGesture} from 'react-use-gesture';
import {add, scale} from 'vec-la';

const Animator = ({children}: {children?: any}) => {
    const [{y}, set] = useSpring(() => ({y: 0}));
    const bind = useGesture({
        onDrag: ({ active, delta, velocity, direction, temp = y.getValue() }) => {
            set({
                y: add(delta, temp),
                immediate: active,
                config: { velocity: scale(direction, velocity), decay: true },
              });
            return temp;
        },
    });
    return <animated.div {...bind()} style={{ transform: y.interpolate((_y: number) => `translateY(${_y}px)`)}}>{children}</animated.div>;
};

There are no inline errors or anything indicating and error until it tries to compile then bails.
Any and all help is very appreciated. I have tried a couple other versions but no change.
Thanks,
Nicholas

Should be fixed now. Try reinstalling! 👍


Using spress anywhere on command line

Hi,
Just wondering how to use spress from the command line like the laravel command.
Does anyone know how to do that? If I copy /bin/spress to /usr/local/bin/ and type spress in the command line it asks me to run composer update first, but that doesn't work in the new location.
Regards,
Joren

Are you using .phar file? I have spress.phar at /usr/local/bin and work fine for me.
If you are using the source code, you need to create a symbolic link.

I've build the phar file using Box, copied it to /usr/local/bin and it gives me these errors:
PHP Fatal error:  Cannot redeclare composerRequire0cd75bdd1fa15afefe7e0cdf3f1712cd() (previously declared in phar:///usr/local/bin/spress.phar/vendor/composer/autoload_real.php:56) in /Server/Spress/vendor/composer/autoload_real.php on line 59

Fatal error: Cannot redeclare composerRequire0cd75bdd1fa15afefe7e0cdf3f1712cd() (previously declared in phar:///usr/local/bin/spress.phar/vendor/composer/autoload_real.php:56) in /Server/Spress/vendor/composer/autoload_real.php on line 59

Move the resulting .phar file to another folder. That error is threw if you are running spress.phar in the same folder of Spress source code because conflicts with Composer loader.

I think it worked. Thanks!


remove unnecessary jruby env check on specs

Thanks for contributing to Logstash! If you haven't already signed our CLA, here's a handy link: https://www.elastic.co/contributor-agreement/

@jsvd LGTM :)


WIP Initial Implementation of kpod launch

This is a mostly functional implementation of kpod launch. This is mostly an analogue for kubectl run which can be run without a running cri-o daemon, with a bit more flexibility. Eventually it will allow you to insert a container into an existing pod for debugging/inspection, but for now it creates new pods and launches containers into them.
The code is working and should be ready to test (with the exception of a number of CLI options that aren't implemented yet). It successfully creates pods and containers, which can be seen and interacted with by the normal CRI-O daemon (it should work without the daemon running as well, but because we don't have a kpod remove yet you can't remove containers without CRI-O).
Ongoing work is documented in the TODO list at the top of launch.go.

CC @mrunalp @rhatdan

Missing Man pages and bash completions.

Does kpod launch launch PODs or containers?

docker launch --help
Should never show "value".

./kpod launch --help | grep value
   --image value             image to launch
   --env value               specify environment variables to be set inside launched container, specified as KEY=VALUE
   --labels value, -l value  specify labels to be set on launched container
   --limits value            specify resource limits for launched container
   --ports value             specify ports to be forwarded to launched container
   --mount value             attach mounts on the host to created container
   --device value            make host devices available inside the container
   --dns value               set DNS servers for container
   --dns-search value        set DNS search domains for container
   --pod value               launch container inside an existing pod

@rhatdan Did an initial pass at addressing your comments on the help test. Everything that refers to the primary container effects only a single container, everything referring to a pod affects the entire pod.
Also, hopefully, Travis should be fixed.

Closing this, working on a new approach


Made magic_file_path only apply in windows

So that applications that have magic_file_path defined work in both windows and linux. (magic_file_path must not defined in linux)

@hirunatan this fix is needed, otherwise if someone specifies MAGIC_FILE_PATH in the settings.py, the plugin won't work on linux.


dsc_resource has a fixed 10 minute timout which causes long running dsc resources to fail

Using DSC resources with Chef-client 12.5.1 and WMF 5 "Production Preview" will timeout and fail if the resource takes longer than 10 minutes to complete a change. This is especially problematic when using the xSQLServerSetup DSC resource.
Unlike dsc_script there is no property within the dsc_resource that allows the timeout value to be modified.

Yep, looks like an oversight. Thanks for the report


union node not passing points

Script:
var system = stream|from().measurement('system')|log()
var ntpq = stream|from().measurement('ntpq')|log()
system|union(ntpq)|log()

Output:
[ntpq_orphan:log4] 2017/02/24 12:27:44 I!  {"Name":"ntpq","Database":"telegraf","RetentionPolicy":"autogen","Group":"","Dimensions":{"ByName":false,"TagNames":null},"Tags":{"env":"local","group":"uxdb","host":"influxdb","location":"infl","os":"Linux","refid":"<IP_ADDRESS>","remote":"<IP_ADDRESS>","stratum":"2"},"Fields":{"delay":3.464,"jitter":10.218,"offset":3.573275e+06,"poll":64,"reach":377,"when":38},"Time":"2017-02-24T12:27:38.782Z"}
[ntpq_orphan:log4] 2017/02/24 12:27:44 I!  {"Name":"ntpq","Database":"telegraf","RetentionPolicy":"autogen","Group":"","Dimensions":{"ByName":false,"TagNames":null},"Tags":{"env":"local","group":"uxdb","host":"influxdb","location":"infl","os":"Linux","refid":"<IP_ADDRESS>","remote":"<IP_ADDRESS>","stratum":"2"},"Fields":{"delay":3.464,"jitter":10.218,"offset":3.573275e+06,"poll":64,"reach":377,"when":43},"Time":"2017-02-24T12:27:43.817Z"}
[ntpq_orphan:log2] 2017/02/24 12:27:45 I!  {"Name":"system","Database":"telegraf","RetentionPolicy":"autogen","Group":"","Dimensions":{"ByName":false,"TagNames":null},"Tags":{"env":"local","host":"db1","location":"db1","os":"Linux"},"Fields":{"load1":0,"load15":0.05,"load5":0.01,"n_cpus":3,"n_users":0},"Time":"2017-02-24T14:01:50.131Z"}
[ntpq_orphan:log2] 2017/02/24 12:27:45 I!  {"Name":"system","Database":"telegraf","RetentionPolicy":"autogen","Group":"","Dimensions":{"ByName":false,"TagNames":null},"Tags":{"env":"local","host":"db1","location":"db1","os":"Linux"},"Fields":{"uptime":230904},"Time":"2017-02-24T14:01:50.131Z"}
[ntpq_orphan:log7] 2017/02/24 12:27:45 I!  {"Name":"ntpq","Database":"telegraf","RetentionPolicy":"autogen","Group":"","Dimensions":{"ByName":false,"TagNames":null},"Tags":{"env":"local","group":"uxdb","host":"influxdb","location":"infl","os":"Linux","refid":"<IP_ADDRESS>","remote":"<IP_ADDRESS>","stratum":"2"},"Fields":{"delay":3.464,"jitter":10.218,"offset":3.573275e+06,"poll":64,"reach":377,"when":28},"Time":"2017-02-24T12:27:28.802Z"}
[ntpq_orphan:log7] 2017/02/24 12:27:45 I!  {"Name":"ntpq","Database":"telegraf","RetentionPolicy":"autogen","Group":"","Dimensions":{"ByName":false,"TagNames":null},"Tags":{"env":"local","group":"uxdb","host":"influxdb","location":"infl","os":"Linux","refid":"<IP_ADDRESS>","remote":"<IP_ADDRESS>","stratum":"2"},"Fields":{"delay":3.464,"jitter":10.218,"offset":3.573275e+06,"poll":64,"reach":377,"when":33},"Time":"2017-02-24T12:27:33.782Z"}
[ntpq_orphan:log7] 2017/02/24 12:27:45 I!  {"Name":"ntpq","Database":"telegraf","RetentionPolicy":"autogen","Group":"","Dimensions":{"ByName":false,"TagNames":null},"Tags":{"env":"local","group":"uxdb","host":"influxdb","location":"infl","os":"Linux","refid":"<IP_ADDRESS>","remote":"<IP_ADDRESS>","stratum":"2"},"Fields":{"delay":3.464,"jitter":10.218,"offset":3.573275e+06,"poll":64,"reach":377,"when":38},"Time":"2017-02-24T12:27:38.782Z"}
[ntpq_orphan:log7] 2017/02/24 12:27:45 I!  {"Name":"ntpq","Database":"telegraf","RetentionPolicy":"autogen","Group":"","Dimensions":{"ByName":false,"TagNames":null},"Tags":{"env":"local","group":"uxdb","host":"influxdb","location":"infl","os":"Linux","refid":"<IP_ADDRESS>","remote":"<IP_ADDRESS>","stratum":"2"},"Fields":{"delay":3.464,"jitter":10.218,"offset":3.573275e+06,"poll":64,"reach":377,"when":43},"Time":"2017-02-24T12:27:43.817Z"}
[ntpq_orphan:log2] 2017/02/24 12:27:51 I!  {"Name":"system","Database":"telegraf","RetentionPolicy":"autogen","Group":"","Dimensions":{"ByName":false,"TagNames":null},"Tags":{"env":"local","host":"jump","location":"jump","os":"Linux"},"Fields":{"load1":0,"load15":0.05,"load5":0.01,"n_cpus":3,"n_users":0},"Time":"2017-02-23T13:18:58.856Z"}
[ntpq_orphan:log2] 2017/02/24 12:27:51 I!  {"Name":"system","Database":"telegraf","RetentionPolicy":"autogen","Group":"","Dimensions":{"ByName":false,"TagNames":null},"Tags":{"env":"local","host":"jump","location":"jump","os":"Linux"},"Fields":{"uptime":1622654},"Time":"2017-02-23T13:18:58.856Z"}
[ntpq_orphan:log2] 2017/02/24 12:27:54 I!  {"Name":"system","Database":"telegraf","RetentionPolicy":"autogen","Group":"","Dimensions":{"ByName":false,"TagNames":null},"Tags":{"env":"local","group":"uxdb","host":"influxdb","location":"infl","os":"Linux"},"Fields":{"load1":0.01,"load15":0.05,"load5":0.03,"n_cpus":3,"n_users":4},"Time":"2017-02-24T12:27:44.135Z"}
[ntpq_orphan:log2] 2017/02/24 12:27:54 I!  {"Name":"system","Database":"telegraf","RetentionPolicy":"autogen","Group":"","Dimensions":{"ByName":false,"TagNames":null},"Tags":{"env":"local","group":"uxdb","host":"influxdb","location":"infl","os":"Linux"},"Fields":{"uptime":1825019},"Time":"2017-02-24T12:27:44.135Z"}
[ntpq_orphan:log4] 2017/02/24 12:27:54 I!  {"Name":"ntpq","Database":"telegraf","RetentionPolicy":"autogen","Group":"","Dimensions":{"ByName":false,"TagNames":null},"Tags":{"env":"local","group":"uxdb","host":"influxdb","location":"infl","os":"Linux","refid":"<IP_ADDRESS>","remote":"<IP_ADDRESS>","stratum":"2"},"Fields":{"delay":3.464,"jitter":10.218,"offset":3.573275e+06,"poll":64,"reach":377,"when":48},"Time":"2017-02-24T12:27:48.784Z"}
[ntpq_orphan:log4] 2017/02/24 12:27:54 I!  {"Name":"ntpq","Database":"telegraf","RetentionPolicy":"autogen","Group":"","Dimensions":{"ByName":false,"TagNames":null},"Tags":{"env":"local","group":"uxdb","host":"influxdb","location":"infl","os":"Linux","refid":"<IP_ADDRESS>","remote":"<IP_ADDRESS>","stratum":"2"},"Fields":{"delay":3.464,"jitter":10.218,"offset":3.573275e+06,"poll":64,"reach":377,"when":53},"Time":"2017-02-24T12:27:53.781Z"}
[ntpq_orphan:log7] 2017/02/24 12:27:54 I!  {"Name":"ntpq","Database":"telegraf","RetentionPolicy":"autogen","Group":"","Dimensions":{"ByName":false,"TagNames":null},"Tags":{"env":"local","group":"uxdb","host":"influxdb","location":"infl","os":"Linux","refid":"<IP_ADDRESS>","remote":"<IP_ADDRESS>","stratum":"2"},"Fields":{"delay":3.464,"jitter":10.218,"offset":3.573275e+06,"poll":64,"reach":377,"when":48},"Time":"2017-02-24T12:27:48.784Z"}
[ntpq_orphan:log7] 2017/02/24 12:27:54 I!  {"Name":"ntpq","Database":"telegraf","RetentionPolicy":"autogen","Group":"","Dimensions":{"ByName":false,"TagNames":null},"Tags":{"env":"local","group":"uxdb","host":"influxdb","location":"infl","os":"Linux","refid":"<IP_ADDRESS>","remote":"<IP_ADDRESS>","stratum":"2"},"Fields":{"delay":3.464,"jitter":10.218,"offset":3.573275e+06,"poll":64,"reach":377,"when":53},"Time":"2017-02-24T12:27:53.781Z"}

Notice that the only points passing to log7 are the "ntpq" points. None of the "system" points are making it through.
However if I stop the task, all of a sudden all the "system" points are released.
This looks to be somehow related to the time. I found this issue in my development environment (bunch of vagrant VMs), and the clocks are horribly out of sync. Once I synced all the clocks it started behaving more normal. However the documentation on the union node gives no indication that it cares about time at all. And while my clocks were horribly out of sync, how out of sync do they have to be to break the union node? Will a few milliseconds break it?
This is kapacitor built from current master (d57e7ba).

+1. I also encountered this in v1.2, although I saw it's marked as fixed in https://github.com/influxdata/kapacitor/issues/1100

We are using Kapacitor 1.4.1 and I still see this behaviour.
If any one if the parent nodes does not have data, union node holds the data of rest of the nodes indefinitely.
At scale, if union node is not flushing the data down the pipeline, we end up using huge amount of RAM and eventually all applications starve for memory.

I'm also having this problem.  I setup a deadman alert that Unions Linux (system) and Windows (win_system) together, so I can have a single alert setup for both platforms.

I'm not sure if this is an intended behavior but I would expect that union would not block when a single parent node stops providing data.

Same thing here. Kapacitor v1.5.4


Download fails with error "Invalid cross-device link"

When I try to download a model, I get the error "Invalid cross-device link" after download.
I think that this is caused by the fact that /tmp and my home are on two different volumes, on which indeed hard linking is not possible.
Log, for reference:
[2023-05-09 19:50:06,937] model_loader.download_model_to_path:182 ERROR -> [Errno 18] Invalid cross-device link: '/tmp/tmp3ull87ia' -> '/home/myuser/.cache/Buzz/ggml-model-whisper-tiny.bin'
Traceback (most recent call last):
  File "buzz/model_loader.py", line 174, in download_model_to_path
  File "buzz/model_loader.py", line 231, in download_model
OSError: [Errno 18] Invalid cross-device link: '/tmp/tmp3ull87ia' -> '/home/saverio/.cache/Buzz/ggml-model-whisper-tiny.bin'

Answer here: https://stackoverflow.com/a/43967659. The API shutil.move() should be used instead of os.rename().

Ah, thanks a lot. Will work on a fix.


Reinstate ability to add multiple themes to Guidance

We changed the way admins apply themes to Guidance mainly to prevent having no themes - #1212 . But the restriction on applying only one theme per individual piece of Guidance turns out to be undesirable for users. @briri confirmed that it's not technically difficult to reinstate the ability to apply multiple themes.
Many DMPtool users have requested this but if it poses problems for DCC services @sjDCC we can make this configurable. See screenshot below for an example of why users want to be able to apply multiple themes still. Previously UCSF could have one piece of Guidance with the themes "Data repository, Preservation, Data sharing" that ensured their suggested language about the IR would appear on any template with a question related to data preservation. Now they have to create 3 pieces of guidance to achieve the same.

The call to the shared partial that handles the display of theme options takes an as_radio argument which defaults to false so it should be as simple as changing that flag to false here: https://github.com/DMPRoadmap/roadmap/blob/c62704337e7dc66fb8a4b519327e75d04ec9871b/app/views/guidances/new_edit.html.erb#L17
A thorough test should be done though to be certain.

Agree that we can allow multiple themes to be assigned to a piece of guidance. We allow multiple themes to be selected per question when adding templates so a similar model could be applied to guidance.

this turns out to be a bug. one example: a since a single piece of guidance (e.g. about the UC IR) that previously had multiple themes (Preservation, Data repo, Data sharing) is now duplicated as 3 pieces of guidance, with one theme for each. if a template question is tagged with more than one of these themes, the same guidance appears multiple times. it was a hot topic of discussion during the admin webinar today and something i promised we would revert back to allowing for multiple themes. thanks for the confirmation @sjDCC that this works for you too.

@briri i can still only select one theme at a time. also the tooltip should be revised slightly as follows:

Select one or more themes that are relevant to this guidance...

back to checkboxes and i can now select multiple themes. the only problem now is that nothing happens when i hover over the Themes tooltip @briri (i.e. no message pops up)


unable to install

Fetched 10.2 MB in 7min 11s (23.5 kB/s)
W: Failed to fetch http://deb.debian.org/debian/dists/jessie-updates/InRelease  Unable to find expected entry 'main/binary-amd64/Packages' in Release file (Wrong sources.list entry or malformed file

Thank you for reporting this error. Could you please paste the complete log showing the progress of docker build?

docker build -t auto-traveler .
Sending build context to Docker daemon  248.6MB
Step 1/28 : FROM gcc:4.9
---> 1b3de68a7ff8
Step 2/28 : RUN apt-get update
---> Running in e28583fcf22c
Ign http://deb.debian.org jessie InRelease
Get:1 http://deb.debian.org jessie-updates InRelease [7340 B]
Get:2 http://security.debian.org jessie/updates InRelease [44.9 kB]
Get:3 http://deb.debian.org jessie Release.gpg [2420 B]
Get:4 http://deb.debian.org jessie Release [148 kB]
Get:5 http://security.debian.org jessie/updates/main amd64 Packages [849 kB]
Get:6 http://deb.debian.org jessie/main amd64 Packages [9098 kB]
Fetched 10.2 MB in 13s (774 kB/s)
W: Failed to fetch http://deb.debian.org/debian/dists/jessie-updates/InRelease  Unable to find expected entry 'main/binary-amd64/Packages' in Release file (Wrong sources.list entry or malformed file)
E: Some index files failed to download. They have been ignored, or old ones used instead.
The command '/bin/sh -c apt-get update' returned a non-zero code: 100

Thanks! Could you please try the solution suggested here?
https://superuser.com/questions/1423486/issue-with-fetching-http-deb-debian-org-debian-dists-jessie-updates-inrelease?answertab=votes#tab-top
I can't test it out myself right now unfortunately. Thank you!

A pre-built image is now also available on Docker Hub: https://hub.docker.com/r/rnacentral/auto-traveler. Thank you for raising this issue!


option to append timestamp prefix to workflow name when workflowtemplate is submitted via cli

currently if u have deployed a workflowtemplate and then try to submit a run of it via the cli it will generate a workflow name with 5 random chars on the end of it. would like that it generates a workflow name with the timestamp in the name too. 2 benefits: easy to see from the name when it was submitted, less chance of a name collision from 10000s of runs

make generateName configurable does sound like an awesome idea

https://argo-workflows.readthedocs.io/en/latest/cli/argo_submit/ has option like --name

#7900 seems like a more generic option that would supersede this.