Broken develop

Something weird happend to develop :/ Today I merged develop into master (with rebase) to create a release for version v0.2.0. After a while I realized that I forgot to change the version inside csproj file. I did the change on the develop and I created another PR from develop into master. It turned out that the PR contained all commmits (38) and changes (213) from from 0.2.0 once again. I updated the develop using the UPDATE button and... poof...
PR shown correct change (so just one change inside csproj) but develop has now duplicated commits from 0.2.0... I have no idea what happened! Now comes the best part. I didn't want to have a mess inside master so I squashed all these changes into one commit and merged it into master. So great, master has just one more commit since 0.2.0 merge with updated csproj. I wanted to test what would happend if I'll do some change on the develop once again. I did small change in the README, created new PR from develop to into master and... same story... I contains all commits and changes from 0.2.0... Do you have any idea what caused that? What options we have to fix that. The only one I have is to create new develop from master (tested that and worked as expected).
I'm sorry guys, that's probably my fault... But I swear, I've never had simmilar issue before...

The options I see are:

Merge master -> develop and develop ->master to have proper merge done. Byt wi will end up with ~350 commits on both branches with 3 duplicates from 0.2.0
Create new develop from master but we'll need to create new PR

All right, fix that :D

@GooRiOn Done!

@tdeschryver thank you, and once again sorry :/ It's embarrassing :/

Haha, it was no biggie.
It can happen to each one of us! 😄

@GooRiOn I created new PR.

@paw3lx  thank you so much, and sorry for all the trouble!
I close the issue :)


account signup requires EMAIL_BACKEND in settings.py

Issue Summary
Doing a clean install and following the instructions in the docs, I got an error.
[Errno 61] Connection refused
it was after a bit of googling that I found the root cause and solution here, EMAIL_BACKEND is a prerequisite to the site functionality running.
https://groups.google.com/g/django-oscar/c/gc0vwdIoyQY/m/xtxvFaQyCgAJ
   EMAIL_BACKEND = 'django.core.mail.backends.console.EmailBackend'

I would recommend adding this to the docs if it is in fact required to run.
Steps to Reproduce

remove the EMAIL_BACKEND directive from the settings.py
attempt to signup for an account

Technical details

Python version: Python 3.9.1
Django version: Version: 3.1.6
Oscar version: Version: 3.0

EMAIL_BACKEND is not required - it defaults to the SMTP backend. You will get a connection refused error if you have no local SMTP server set up.
I don't think that is an Oscar-specific issue as it's how all Django projects would work out of the box. I'm sure there has been debate about changing Django's defaults, but I don't think it is an issue that Oscar needs to weigh in on.

Thanks for the great and immediate feedback. You are correct of course
EMAIL_BACKEND | 'django.core.mail.backends.smtp.EmailBackend'

Would it be appropriate to use fail_silently or to show a more meaningful error message?

I don't think fail_silently would be an appropriate default, given that sending emails is an important activity performed by Oscar in several places and you'd probably want to know if something went wrong with that.
Oscar could potentially catch any exception raised by the backend. I think the question here would be whether we can add any useful information that the original exception/trace doesn't contain. What was the full stack trace for the error you got?

Request Method:
POST

http://<IP_ADDRESS>:8000/accounts/login/

3.1.6

ConnectionRefusedError

[Errno 61] Connection refused

<EMAIL_ADDRESS>line 831, in create_connection

/Users/john/Library/Caches/pypoetry/virtualenvs/discauction-demo-WPUZWD28-py3.9/bin/python

3.9.1

['/Users/john/src/django-oscar/frobshop'<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS> '/Users/john/Library/Caches/pypoetry/virtualenvs/discauction-demo-WPUZWD28-py3.9/lib/python3.9/site-packages']

Thu, 04 Feb 2021 15:38:19 +0000

here is the FULL output
https://dpaste.com/A53WU4AXD
Yes, technically, I could spend time on this to read and parse the whole error message. The [Errno 61] Connection refused is a bit of a dead end for googling.
I was following the install instructions step by step. I don't think that it would be an issue to add a line to the doc including this information, when it's something that stopped me in my tracks as a first time user.

you can use django.core.mail.backends.console.EmailBackend for development

thanks @glavery, I did find the solution through googling. I just thought that this might be added to the docs, as it would have saved me an hour as a first time user.
SAFE to close this issue. Hopefully this will also help the next user who runs into this.


[Feature][UI] Implement a dark theme

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
Enhance UI themes, implement switching between dark and light themes.
Use case
No response
Related issues
No response
Are you willing to submit a pull request to implement this on your own?

[X] Yes I am willing to submit a pull request on my own!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

If this works well, we could pick dark by default, or pick browser/OS style.


Are we able to add customized attributes to the iframe that opens the Tab app?

Hi team,
Are we able to add customized attributes to the iframe that opens the Tab app? For example for the 3rd party cookie blocking change in Chrome, we consider adding some attributes to the iframe. Is it feasible?

We will check this and get back to you.

Could you please let us know what attributes are you trying to add? If it's allow-storage-access-by-user-activation, then it's being already discussing here - https://github.com/OfficeDev/microsoft-teams-library-js/issues/1460#issuecomment-1884755439


StackLLaMA - ValueError: Please specify target_modules in peft_config

Hi, thank you for your amazing work.
After reading StackLLaMA: A hands-on guide to train LLaMA with RLHF, I try to run StackLLaMA first phase.
When I run supervised_finetuning.py with the model aleksickx/llama-7b-hf, I encounter the following error:
ValueError: Please specify `target_modules` in `peft_config`

Here is the full logs:
===================================BUG REPORT===================================
Welcome to bitsandbytes. For bug reports, please run

python -m bitsandbytes

 and submit this information together with your error trace to: https://github.com/TimDettmers/bitsandbytes/issues
================================================================================
bin /home/re/trl/examples/stack_llama/scripts/env/lib/python3.10/site-packages/bitsandbytes/libbitsandbytes_cuda121.so
/home/re/trl/examples/stack_llama/scripts/env/lib/python3.10/site-packages/bitsandbytes/cuda_setup/main.py:145: UserWarning: /home/ocr/miniconda3 did not contain ['libcudart.so', 'libcudart.so.11.0', 'libcudart.so.12.0'] as expected! Searching further paths...
  warn(msg)
CUDA SETUP: CUDA runtime path found: /usr/local/cuda/lib64/libcudart.so
CUDA SETUP: Highest compute capability among GPUs detected: 8.6
CUDA SETUP: Detected CUDA version 121
CUDA SETUP: Loading binary /home/re/trl/examples/stack_llama/scripts/env/lib/python3.10/site-packages/bitsandbytes/libbitsandbytes_cuda121.so...
Setting EOS, BOS, and UNK tokens for LLama tokenizer
Loading the dataset in streaming mode
100%|█████████████████████████████████████████████████████████████████| 400/400 [00:13<00:00, 30.06it/s]
The character to token ratio of the dataset is: 3.19
Loading the model
Loading checkpoint shards: 100%|████████████████████████████████████████| 33/33 [00:23<00:00,  1.38it/s]
Traceback (most recent call last):
  File "/home/re/trl/examples/stack_llama/scripts/supervised_finetuning.py", line 346, in <module>
    main(args)
  File "/home/re/trl/examples/stack_llama/scripts/supervised_finetuning.py", line 334, in main
    run_training(args, train_dataset, eval_dataset)
  File "/home/re/trl/examples/stack_llama/scripts/supervised_finetuning.py", line 269, in run_training
    model = get_peft_model(model, lora_config)
  File "/home/re/trl/examples/stack_llama/scripts/env/lib/python3.10/site-packages/peft/mapping.py", line 142, in get_peft_model
    peft_config = _prepare_lora_config(peft_config, model_config)
  File "/home/re/trl/examples/stack_llama/scripts/env/lib/python3.10/site-packages/peft/mapping.py", line 117, in _prepare_lora_config
    raise ValueError("Please specify `target_modules` in `peft_config`")
ValueError: Please specify `target_modules` in `peft_config`

Script to reproduce
python supervised_finetuning.py --model_path=aleksickx/llama-7b-hf \
        --streaming --no_gradient_checkpointing --learning_rate 1e-5 \
        --max_steps 1000 --output_dir ./llama-se

My environments: python3.10
peft==0.2.0
torch==2.0.0
transformers==4.28.1
datasets==2.11.0
sentencepiece==0.1.98
protobuf==3.20.3
accelerate==0.18.0
bitsandbytes==0.38.1

Questions:

Is the model aleksickx/llama-7b-hf not compatible to StackLLaMA?

What do I need to define  target_modules in  LoraConfig here ?
https://github.com/lvwerra/trl/blob/160d0c9d6cdbc8b247bad4aa8f97f2c57dc4a60f/examples/stack_llama/scripts/supervised_finetuning.py#L202-L208

Hi @thinh-huynh-re
Thank you for your interest in this work
Llama support has been added very recently into peft. Hence you need to update your peft library to run that script:
pip install git+https://github.com/huggingface/peft

However, you can directly use that version and just specify target_modules as stated on the issue. That argument is used to specify the name of the module you want to replace with the LoRA module. In the Llama case, I'd expect to replace the query and key layers to LoRA modules therefore:
lora_config = LoraConfig(
     r=16,
     lora_alpha=32,
     lora_dropout=0.05,
     bias="none",
     task_type="CAUSAL_LM",
     target_modules=["q_proj", "k_proj"],
 )

should do the trick!

It works.
Thank you for your quickly support!


DoubleEntry::TransferNotAllowed between accounts with different scope (but same identifier)

I defined a primary account like so:
config.define_accounts do |accounts|
    user_scope = ->(user) do
      raise 'not a User' unless user.class.name == 'User'
      user.id
    end

    accounts.define(identifier: :primary, scope_indentifier: user_scope, ...)
end

And a transfer transfer like so:
config.define_transfers do |transfers|
    transfers.define(from: :primary, to: :primary, code: :transfer)
end

If I try to do a transfer like this:
user1 = User.first
user2 = User.last

account1 = DoubleEntry.account(:primary, scope: user1.id)
account2 = DoubleEntry.account(:primary, scope: user2.id)

DoubleEntry.transfer(Money.new(1),
                     from: account1,
                     to: account2,
                     code: :transfer)

It throws a DoubleEntry::TransferNotAllowed. This strikes me as weird behaviour. They don't have the same scope/user. Users should be able to move money between each other's accounts.
I did some further digging and found that both account1.scope_identity and account2.scope_identity return the same User id.
Can't seem to figure out why.

Closing because the answer is pretty obvious and I can't believe I didn't see it all this time.
user1 is the same as user2. I had only one user in my local DB. facepalm


Update enquiry-notification.pug

Fixed the recipient.firstName to actually point to the variable
%recipient.firstName% was compiling to this actual text.
#{recipient.firstName} now compiles to the variable value

Is this dead?


Update Portuguese terms and translations

Hello :wave:
This is a PR to update the NEAR Wallet Portuguese translation.
It's an initiative from NEAR Portuguese Guild
Demo

Running local

@murilooon can you please let me know if this is good to go?

It's good to go :ship:


inference with AWQ quantization

Hi, i got an anomaly while inference mistral with AWQ, below is the GPU usage on 3090 consume 20GB GPU. even if we inference the base model only consume 19GB GPU

here is the command: python -m vllm.entrypoints.openai.api_server --model ../Mistral-AWQ --disable-log-requests --port 9000 --host <IP_ADDRESS> --max-num-seqs 500 --max-model-len 27000 --quantization awq
can anyone help?, thank you.

Maybe cuda graph? If you use eager_force=True, does it still consume the same amount of memory?

Maybe cuda graph? If you use eager_force=True, does it still consume the same amount of memory?

i will try later when my instance active again


Suggestion also

So one person had an idea I thought I'd share - the bot works great but does become a bit spammy on an active pool. Would it be possible to link a symbol to a webhook - that way you could allocate an area on Discord per coin.
Something like:
XVG     Webhook1
RVN     Webhook2

I could also flush found blocks per coin and per time limit

Meaning get rid of history in a given channel by hook? .. If so I'd love it, like limiting to the last 10 blocks or such. Great thought.

Regarding your first answer, I think it's already doable actually. As the coin in requested by passing ?algo=all you could run several instance of the script binded on different hooks and using ?algo=xvg or ?algo=rvn

Hmm interesting, although if the pool is large I'm not in love with one systemd per coin.
That becomes unwieldy, but I understand.

Well, it's a Python script using asyncio. It does NOT use any resource basically so it's clearly intended to be run multiple times if you want.


Add shortcuts galley

This website has more shortcuts than sharecuts.app https://shortcutsgallery.com

added. thanks


Add test for flag order

cc @ehazlett @bfirsh
Not a "critical path" by any stretch of the imagination but want to encourage good testing discipline on machine.
Signed-off-by: Nathan LeClaire<EMAIL_ADDRESS>

Where did your flag fix go?

Where did your flag sort fix go?

It's in master - this is a followup test for it.
Edit: That's what I get for not running test in a container.  Build should be fixed now.

Ah gotcha thanks!  LGTM


XML special characters

Hi,
If I want to add xml special characters like >, how can I do?
I tried writing & gt; (without the space) in the xml but not works.
Thanks you! great lib!

Hi !
I'm not sure to understand where you want this special character to be displayed ...
Can you be more precise and eventually post an example of what you want to do ?

        /// <summary>         /// Get entities from a given domain.         /// </summary>         /// <remarks>         /// Use this method to retrieve data from a domain:         /// ----------------------------------------------         /// Use the *Filter* parameter to query data.          /// The parameters by which you can filter are those included in the entities of the schema.         /// You can only filter the entity type you specified in the URL.          /// Supported boolean operators: AND|OR         /// Supported logical operators: <![CDATA[>|<|>=|<=|=]]>         ///          /// Use the *Expand* parameter to include data from related entities. If you want to expand all relations between two entities, you can use --> to expand any relation between two entities.         /// </remarks>
That XML comment is showed like:

I want to show >, >= instead the encoded characters.

To help you i need to see the generated JSON or YAML provided to angular-swagger-ui and the way you initialize the component


Hide "Download Log" button while pipeline is running instead of disabling it

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/1893
Originally created by @DouweM on 2020-03-26 22:40:01

View 3 previous comments from the original issue on GitLab


Too large

Thanks for making this, but somehow the icons appear so large that they overlap with the text. Perhaps it is my custom theme, but I don't know how to fix it?

The setting item exists in the plugin settings. ("Large icon?")

However, if it's influenced by other Custom CSS or themes, will need to look into that. Try setting it to standard and see what affects it.

It is a little better if I set it to "small" but on further inspection, the real problem seems to be the space between the icon and the start of the text, not the icon size.

It is most likely influenced by Custom CSS. Without looking at your CSS code, I can't see what CSS is being applied.

I'm using the Flow Nord theme (with a few modifications, but mostly for color):
https://github.com/henices/logseq-flow-nord

I enabled the theme, but it didn't look like that. Try disabling Custom CSS temporarily. Need to find out which CSS code is causing the problem.

Seems to be the custom code I have to make the font size bigger:
  --cl-font-size: 1.15em;
But I need that to make the text readable...

In my environment, that alone does not cause the icon and text to overlap. It seems like there are other things as well. Alternatively, release it and press [Ctrl +] or [Ctrl -] to zoom in or out.

After that....
I found the code that is probably the cause.. https://github.com/henices/logseq-flow-nord/blob/5cbb665d823d8994182d5ed1da2c1bd5aebefff3/src/code/interface.css#L376
Applying the following CSS code may solve the problem.
main div.block-main-container div.bullet-container div.bullet {
    font-size: unset;
}

Thank you so much. I appreciate you taking the time to look into this for me. I modified the code a little, but this works:
.block-main-container .bullet-container .bullet {
    font-size: unset !important;
}


Auto update to onflow/cadence v0.39.14

Description
Automatically update to:

onflow/cadence v0.39.14
onflow/flow-go-sdk v0.41.9
onflow/flow-go 82d6e5f45ca1
onflow/flow-emulator v0.52.0
onflow/cadence-tools/test v0.9.3
onflow/cadence-tools/lint v0.10.1
onflow/cadence-tools/languageserver v0.30.1

Codecov Report

Merging #1126 (8243d0c) into master (8c42ef6) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1126   +/-   ##
=======================================
  Coverage   39.28%   39.28%
=======================================
  Files          37       37
  Lines        1876     1876
=======================================
  Hits          737      737
  Misses       1051     1051
  Partials       88       88

Flag
Coverage Δ

unittests
39.28% <ø> (ø)

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


implement Search Recipe page

Please do work for this task in a branch named issue-14.
Page should show all recipes on the site by default
Should have a filter that user can click on to show recipes with the selected filters
Search bar that users can type in and will show recipes with similar name to input?

Search page is complete on branch issue-07 and merged with main


SDXL checkpoint format/compatibility

Training with the train_sdxl configs outputs checkpoints which are the size of the SDXL unet(10.3 GB) in diffusers format.
How do I use these files for anything?

Fixed in https://github.com/Mikubill/naifu-diffusion/commit/5de1f3fbebe80ab78d02118aa3f108173c2e110f and now can get a full checkpoint in new training.
For existing checkpoints you can use something like this to build the original one
from safetensors.torch import load_file, save_file

orig_file = load_file("naifu-checkpoint.safetensors")
full_model = load_file("sd_xl_base_1.0_0.9vae.safetensors") # from huggingface
full_model.update(orig_file)
save_file(full_model, "fixed_model.safetensors")


Just use regular httpx to fetch the book info/availability

Only my list of "interesting books" actually requires auth; everything else I could fetch as an unauthenticated request and thus throw lots of concurrency at it. That would make fetching the books much faster!

It would make it faster, but I'm not sure it would make it fast – the speed of the library website is an upper bound on how fast I can go.


Theme Provider with AOS Configuration Not working

I'm not a contributor, but I noticed this issue. It's quite vague. To benefit all parties, you should provide more details about the specific requirements and functionalities you have in mind.
Being more explicit about your needs will help potential contributors better understand the scope and purpose of the request, making it easier for them to provide a meaningful solution.

Sorry for not putting the code
This is the previous that I faced problem with (The AOS Animation not working)

I just simply removed the props of the ThemeProvider of disableTransitionOnChange and it working now haha


module 'i3ipc' has no attribute 'Connection'

Hi,
I just tried to learn i3ipc a bit. I downloaded it from PyPi and copied the example apps-on-ws-init.py. My version is Python 3.7.3 on an up-to-date Archlinux.
When I run the script, I get
Traceback (most recent call last):
  File "./app-on-ws-init.py", line 6, in <module>
    import i3ipc
  File "/home/me/test/i3ipc.py", line 7, in <module>
    i3 = i3ipc.Connection()
AttributeError: module 'i3ipc' has no attribute 'Connection'

I am just beginning to learn python, so I don't exactly know what this means... considering that this is an official example file, the attribute Connection should work. Is my python setup messed up or what could cause this?
Thanks for your support :)

When you say import i3ipc, it's importing the file in that directory /home/me/test/i3ipc.py, not the library.
Rename that file and it should work.
Read this:
https://docs.python.org/3/tutorial/modules.html#the-module-search-path

Doh! How could I not have thought of that. Thank you so much, works perfectly now.


Pipeline functions returning null does not discard token

The documentation states "A pipeline function can indicate that the passed token should be discarded by returning null. This token will not be passed to any downstream pipeline functions and will not be added to the index."
However, the code checks for undefined or empty string, and will pass null tokens through to the next pipeline function.

Can confirm via fiddle
The documentation for the module itself implies that undefined is indeed the right value to return, and there's a test that backs this up

I've submitted a PR to address this: #423

I think the right fix here is to treat a null in the same way the code currently treats undefined and ""
@hoelzro thanks for the pull request, but I think we can take this opportunity to make the code match the documentation! I'll put together a change with a fix just now.

I've just pushed 2.3.8 which includes a fix for this issue, thanks for taking the time to report and to @hoelzro for investigating.


trivial Plan 9 port

Just a few changes to make it build and run under Plan 9. Also replaced /bin/bash with /bin/sh, seemed like no actual bash features are used and /bin/bash doesn't exist on some Unix systems (OpenBSD, NixOS) so this makes it build on those without any changes as well.

Unfortunately this pull request conflicts heavily with the goals of the project, see #1

I see. If it's mostly because of mkfile I could either replace it with an equivalient of build.sh named build.rc (rc is the shell in Plan 9) or just remove that altogether if that'd be a plausible solution.

The mkfile is unwanted, but it's mostly the other parts -- firstly it seems to conflict with the project's goal explicitly stated at the top of the README. The project is written in ANSI C, it's made to compile with -std=c89 -pedantic; before I removed support for 16bit targets it would compile in a 16bit version of TurboC for MS-DOS released in the 1980s. As far as I can tell your changes allow it to work with a language which I would describe as "resembling C" which isn't something I plan to support.
Secondly the change is large in the context of this project, the project isn't small incidentally, it's small from being hacked away on for years as an exercise in practical minimalism (eg. the code to handle escape sequences in a string is barely 4 lines). In the space of the 22 lines of code which this pull request adds, substantial functionality could have been added.
Note this is a criticism only of this pull request and the reasons for it not being introduced into the project. The fact that you've modified it to allow it to run on Plan 9 is pretty cool, it's just something that would exist better outside of this repo as a Plan 9 specific fork.

ok, makes total sense. thanks for the response!

Just a friendly reminder that a proposed change to #!/bin/sh can cut weight by further two characters, as well as having an overall healing effect.


'peering.models.models.InternetExchangePeeringSession object' has no attribute 'communities'

Interface have separate community list for each peering session.
But when i try to access it - "'peering.models.models.InternetExchangePeeringSession object' has no attribute 'communities'" error.
Reproduced always.
Template code
{{- session.communities.all() | filter(type="ingress") | iterate('slug') | join(' ') -}}{{ " " }}
same with internet_exchange - is working well.
Vesion - lastes git - 1.4.5-dev

We can add a new jinja filter to fetch communities (a bit like routing policies) like {{ session | communities }}, if it can help in template simplification.


docs(Toggle): adding example for resizing using style properties

@jpuri The PR looks good. I just noticed it looks bad when switching to the Bootstrap theme. Should we maybe exclude it in case the bootstrap theme is active?

Or might be get rid of it, resizing by changing size is much complex, I doubt is anyone will do that.

I was thinking about better explaining to the how it works in case they want to have completely different styling, but I guess you are right. It's too complex anyway. I will merge it and maybe kick it out later.


Install System folder in Vendor folder

I was wondering is there a way to install CodeIgniter using composer, but ignore the system folder.
I just installed this package and was happy about being able to install Codeigniter with composer, but then I noticed that the source code still outside the vendor folder.
Wonder if it is possible to install codeigniter inside the vendor file.

I'm not even aware of a way to make Composer install source code outside of vendor/ and we're certainly not doing that, so ... Whatever is happening it's outside of our control.

I'm not even aware of a way to make Composer install source code outside of vendor/ and we're certainly not doing that, so ... Whatever is happening it's outside of our control.

When you install codeigniter using composer, is the /system/core folder inside the /vendor folder? Maybe I did something wrong.


Cannot install on 1.8.7

Gem::Installer::ExtensionBuildError: ERROR: Failed to build gem native extension.

       ~/.rbenv/versions/1.8.7-p375/bin/ruby extconf.rb
extconf.rb:153: undefined (?...) sequence: /^Version: ImageMagick\s+(?<Version>\d+\.\d+\.\d+\-\d+)\s+(?<Unknown>\S+)\s+(?<Arch>\S+)\s+(?<Date>\S+)/

Gem files will remain installed in ~/myapp/vendor/bundle/gems/rmagick-2.13.4 for inspection.
Results logged to ~/myapp/vendor/bundle/gems/rmagick-2.13.4/ext/RMagick/gem_make.out

Looks like its an issue with 1.9.3 style regexp syntaxes

Wow, are you still running 1.8? Cool!
Thanks for reporting this. Looks like 1.8 compatibility really needs to be addressed.
We'd totally welcome a patch from you that simplifies that version check. It will be tested on Travis and we'll see if it works on 1.8 at once.
If not, please allow some time for this to be fixed.

1.8 has been deprecated for years. If you need to support 1.8 please use one of the previous gem releases that supports it.

@vassilevsky I'll certainly take a look and see what I can do. It doesn't look like it would be too hard to make this bit of regexp pass.
@ioquatix I know :cry: I wish we could upgrade easily

We must have unreleased code because that's not in master

If someone wants to help update the https://github.com/gemhome/rmagick/blob/master/ChangeLog I'll cut a release

I'll cut a release

Oh, I face a build error now. Wait a moment please.

#172 was merged - I'd love to see this fix released :+1:

Note that this issue was rejected by merging "Drop support for Ruby 1.8 and 1.9" #232 - so it may be closed

Support for Ruby 1.x was dropped in the develop branch and when it is released it is going to have version 3.0. Version 2.0 should be compatible with Ruby 1.8.


keywords language

Thanks for your 4.1.1 fix!
I must have missed something because I keep getting this error:
Error: Language must be one of [danish,dutch,english,french,galician,german,italian,polish,portuguese,russian,spanish,swedish]

Where, how should I set the language in the yml?
I tried in the main jsonContent, directly in jsonContent.posts and also as a property of keywords in both of them…

Ohhh, found it by checking the code!
in the main object it's not keywords: true but keywords: LANG.
The README wasn't clear about it.

Thanks @Buzut !
I merged your PR and will release a new patch.


OpenSSL 3.0.3 fails to auto-init rng on Windows 7

curl users on Windows 7 immediately ran into problems with the bump to OpenSSL 3..0.3 as RAND_status() now returns false when expected to return true - and it worked fine in 3.0.2.
See further discussions in the curl issue https://github.com/curl/curl/issues/8849

Likely related to: https://github.com/openssl/openssl/pull/18282

@bagder Could you please try the current openssl-3.0 branch if this resolves the issue?

Unfortunately, I submitted the issue here on others' behalf - I can't reproduce it. @vszakats could you repeat the problem and/or see if it is fixed?

It's a long shot, as I stopped using OpenSSL on Windows (due the long-time unfixed engine/config-loading vulnerabilities) and also miss a Win 7 test env. But, I've kicked off a CI build with the latest OpenSSL snapshot (and the latest stable curl/libssh2 sources). I'm keeping an eye of the build and once ready, the artifacts can be freely tested on Win 7.
[ It'd be nice to have built-in tests for this in OpenSSL itself, as engine loading seems just one of the more obvious issues stricmp_l may cause, and all this is unrelated to curl. ]

Update: Binaries here: https://ci.appveyor.com/project/curlorg/curl-for-win/builds/43573097/artifacts

Update: Binaries here: https://ci.appveyor.com/project/curlorg/curl-for-win/builds/43573097/artifacts

The CURL binary here does not work, still getting 35. - Windows 7 SP1

@vszakats
Try configuring OpenSSL 3.0.4-dev with -DOPENSSL_NO_LOCALE switch. I could be wrong but Windows 7 locale support could be broken...

If this option is required for 3.0.x to work correctly on previously supported Windows versions, I think this options should be enabled by default. There is a fair chance that not everyone will be aware of this before running into some issues, potentially a silent and/or security-related one.

@vszakats Try configuring OpenSSL 3.0.4-dev with -DOPENSSL_NO_LOCALE switch. Perhaps Windows 7 locale support could be broken...

I could not even build 3.0.3 on my platform because of locale issues. We are very explicit about specifying the randomizer in OpenSSL.

It shouldn't be switched on by default because modern Windows versions work with locales correctly.

grepping the list of places [1] where OPENSSL_str[n]casecmp is used, it's unclear why locale-dependent comparison is used now when comparing with 7-bit ASCII literals? For the remainder of cases, the question is what issues/breakage can be expected with OPENSSL_NO_LOCALE enabled? (As committed here, Turkish locale can indeed break some of these because of the dotless-'i' in the alphabet, regardless of Windows version.)
[1]:
$ grep -R -E 'OPENSSL_strn?casecmp'

./asn1/ameth_lib.c:            && OPENSSL_strncasecmp(ameth->pem_str, str, len) == 0)
./asn1/asn1_gen.c:            && (OPENSSL_strncasecmp(tntmp->strnam, tagstr, len) == 0))
./trace.c:        if (OPENSSL_strcasecmp(name, trace_categories[i].name) == 0)
./LPdir_unix.c:        if (OPENSSL_strcasecmp((*ctx)->entry_name,
./ffc/ffc_dh.c:        if (OPENSSL_strcasecmp(dh_named_groups[i].name, name) == 0)
./ctype.c:int OPENSSL_strcasecmp(const char *s1, const char *s2)
./ctype.c:int OPENSSL_strncasecmp(const char *s1, const char *s2, size_t n)
./ctype.c:int OPENSSL_strcasecmp(const char *s1, const char *s2)
./ctype.c:int OPENSSL_strncasecmp(const char *s1, const char *s2, size_t n)
./encode_decode/decoder_lib.c:            && OPENSSL_strcasecmp(data_structure, "type-specific") == 0)
./encode_decode/decoder_lib.c:            && OPENSSL_strcasecmp(ctx->start_input_type, new_input_type) != 0) {
./encode_decode/decoder_lib.c:                || OPENSSL_strcasecmp(data_structure,
./encode_decode/decoder_lib.c:            if (OPENSSL_strcasecmp(new_input_structure,
./encode_decode/encoder_lib.c:                && OPENSSL_strcasecmp(current_output_type,
./encode_decode/encoder_lib.c:            if (OPENSSL_strcasecmp(data->ctx->output_structure,
./property/property_parse.c:    if (OPENSSL_strncasecmp(s, m, m_len) == 0) {
./rsa/rsa_backend.c:        if (OPENSSL_strcasecmp(param_mgf->data,
./ec/ec_lib.c:    if (OPENSSL_strcasecmp(ptmp->data, SN_X9_62_prime_field) == 0) {
./ec/ec_lib.c:    } else if (OPENSSL_strcasecmp(ptmp->data,
./ec/ec_backend.c:        if (OPENSSL_strcasecmp(name, encoding_nameid_map[i].ptr) == 0)
./ec/ec_backend.c:        if (OPENSSL_strcasecmp(name, check_group_type_nameid_map[i].ptr) == 0)
./ec/ec_backend.c:        if (OPENSSL_strcasecmp(name, format_nameid_map[i].ptr) == 0)
./objects/o_names.c:        name_funcs->cmp_func = OPENSSL_strcasecmp;
./objects/o_names.c:            ret = OPENSSL_strcasecmp(a->name, b->name);
./core_namemap.c:    return OPENSSL_strcasecmp(a->name, b->name);
./params_dup.c:    return OPENSSL_strcasecmp(l->key, r->key);
./params_dup.c:        diff = OPENSSL_strcasecmp((*p1cur)->key, (*p2cur)->key);
./x509/v3_tlsf.c:            if (OPENSSL_strcasecmp(extval, tls_feature_tbl[j].name) == 0)
./x509/v3_utl.c:        subject_len >= 4 && OPENSSL_strncasecmp((char *)subject, "xn--", 4) == 0)
./x509/v3_utl.c:                && len - i >= 4 && OPENSSL_strncasecmp((char *)&p[i], "xn--", 4) == 0)
./http/http_client.c:        if (add_host && OPENSSL_strcasecmp("host", hdr->name) == 0)
./http/http_client.c:                    && OPENSSL_strcasecmp(key, "Location") == 0) {
./http/http_client.c:                    && OPENSSL_strcasecmp(key, "Content-Type") == 0) {
./http/http_client.c:                if (OPENSSL_strcasecmp(rctx->expected_ct, value) != 0) {
./http/http_client.c:            if (OPENSSL_strcasecmp(key, "Connection") == 0) {
./http/http_client.c:                if (OPENSSL_strcasecmp(value, "keep-alive") == 0)
./http/http_client.c:                else if (OPENSSL_strcasecmp(value, "close") == 0)
./http/http_client.c:            } else if (OPENSSL_strcasecmp(key, "Content-Length") == 0) {
./evp/ec_support.c:            if (OPENSSL_strcasecmp(curve_list[i].name, name) == 0)
./evp/p_lib.c:        if (OPENSSL_strcasecmp(name, standard_name2type[i].ptr) == 0)
./evp/evp_lib.c:    if (OPENSSL_strcasecmp(type, "RSA") == 0) {
./evp/evp_lib.c:    } else if (OPENSSL_strcasecmp(type, "EC") == 0) {
./evp/evp_lib.c:    } else if (OPENSSL_strcasecmp(type, "ED25519") != 0
./evp/evp_lib.c:               && OPENSSL_strcasecmp(type, "X25519") != 0
./evp/evp_lib.c:               && OPENSSL_strcasecmp(type, "ED448") != 0
./evp/evp_lib.c:               && OPENSSL_strcasecmp(type, "X448") != 0) {
./evp/ctrl_params_translate.c:            if (OPENSSL_strcasecmp(ctx->p2, kdf_type_map->kdf_type_str) == 0) {
./evp/ctrl_params_translate.c:                && OPENSSL_strcasecmp(tmpl->ctrl_str, item->ctrl_str) == 0)
./evp/ctrl_params_translate.c:                     && OPENSSL_strcasecmp(tmpl->ctrl_hexstr,
./evp/ctrl_params_translate.c:                    && OPENSSL_strcasecmp(tmpl->param_key,
./rand/rand_lib.c:        if (OPENSSL_strcasecmp(cval->name, "random") == 0) {
./rand/rand_lib.c:        } else if (OPENSSL_strcasecmp(cval->name, "cipher") == 0) {
./rand/rand_lib.c:        } else if (OPENSSL_strcasecmp(cval->name, "digest") == 0) {
./rand/rand_lib.c:        } else if (OPENSSL_strcasecmp(cval->name, "properties") == 0) {
./rand/rand_lib.c:        } else if (OPENSSL_strcasecmp(cval->name, "seed") == 0) {
./rand/rand_lib.c:        } else if (OPENSSL_strcasecmp(cval->name, "seed_properties") == 0) {
./conf/conf_def.c:    if (OPENSSL_strcasecmp(pval, "on") == 0
./conf/conf_def.c:            || OPENSSL_strcasecmp(pval, "true") == 0) {
./conf/conf_def.c:    } else if (OPENSSL_strcasecmp(pval, "off") == 0
./conf/conf_def.c:            || OPENSSL_strcasecmp(pval, "false") == 0) {
./conf/conf_def.c:             && OPENSSL_strcasecmp(filename + namelen - 5, ".conf") == 0)
./conf/conf_def.c:                 && OPENSSL_strcasecmp(filename + namelen - 4, ".cnf") == 0)) {
./engine/tb_asnmth.c:            && OPENSSL_strncasecmp(ameth->pem_str, str, len) == 0)
./engine/tb_asnmth.c:                && OPENSSL_strncasecmp(ameth->pem_str, lk->str, lk->len) == 0) {
./store/store_result.c:            && (OPENSSL_strcasecmp(data->data_type, PEM_STRING_X509_TRUSTED) == 0))
./store/store_lib.c:        if (OPENSSL_strcasecmp(scheme_copy, "file") != 0) {

Even when we compare 7-bit ASCII, we can trigger Turkish "i" effect.
OPENSSL_str[n]casecmp is used consistently to avoid Unix/Windows string comparison functions mismatch.

Even when we compare 7-bit ASCII, we can trigger Turkish "i" effect.

Sorry for being unclear, that is what I meant.
Could it be a solution to use non-locale-dependent comparisons on both Unix and Windows for 7-bit ASCII strings? This would re-stabilize them, while making them work identically accross all platforms. Majority of comparisons seem to fall into this case (inside crypto and ssl libs at least).

@vszakats you misunderstand the problem, there is no such thing as non-locale-dependent comparisons for 7-bit ASCII strings. In the turkish locale the ASCII i will not match ASCII I in case insensitive comparison.

Sorry, I don't get. The current solution was implemented to ensure locale-independent comparison where locale concept is implemented.
To avoid the locale stuff, we could switch to uppercase strings only and use strcmp instead of strcasecmp but it will break everything.

I'm so puzzled. Is there actually ever a need for locale-aware string comparisons in a TLS library?

@bagder please read my comment above about the case insensitive comparisons in Turkish locale.

Could you please test an OpenSSL build with the #18337 in place on Windows 7 to see if that helps?

That would highlight the need for something that is not locale aware, like I said.  Compare strings ignoring locale: don't use strcasecmp().

Like we do in curl since 2008: https://daniel.haxx.se/blog/2008/10/15/strcasecmp-in-turkish/

Like Apache does since forever. HTTP header field names are not case sensitive. But the equality of different writings MUST NOT depend on any locale set on the client or server side.
Could you name an example where a crypto parameter name equality has need for locale specific equality checks? Would this not rather be a security issue if a server admin changes a locale and an EC parameter is not longer applied?

I'll try to write a replacement tomorrow.
@icing, the direct concern is the Turkish locale where strcasecmp("i", "I") != 0
Could this be turned into a security issue?  Probably.....

The Turkish locale is one (in-)famous example.
Also, those rules may be subject to change over time, just like timezones. For an example of that, you can read on the evolution of the uppercase form of the German ß.

@icing exactly.  We don't know all of the problems.  This one has been raised as a specific issue which we want to address.

@t8m: 7-bit ASCII is a-z and A-Z. There is definitely a locale-agnostic way to compare those case-insenstitvely.

@vszakats yes, char-by-char and veeery slow

@beldmit If speed is of any concern here, being locale-aware will only make it worse. By the list of places this is used, probably security (stability and consistency) is more of a concern here, than speed.

Possibly related: https://github.com/openssl/openssl/issues/18339

No, that is almost surely not related.

I agree, it should be unlinked.


Implementation of dirt upscattering.

@jhoefken implementing dirt in Booster Neutrino Beam.

Done! Included also flux scaling along the z direction.


Fix touch icon url path

Thanks for your patch, @lepture. This has since been fixed in the latest version of the site.


Incorrect configuration line - wrong regexp

Hi
For ssht:
$ ssht
WARNING:root:KEYWORD: Incorrect configuration line 'HostKeyAlgorithms=+ssh-dss,ssh-rsa' on SSH-config line number 241
WARNING:root:KEYWORD: Incorrect configuration line 'PubkeyAcceptedKeyTypes=+ssh-dss,ssh-rsa' on SSH-config line number 242
WARNING:root:KEYWORD: Incorrect configuration line 'HostKeyAlgorithms=+ssh-dss,ssh-rsa' on SSH-config line number 246
WARNING:root:KEYWORD: Incorrect configuration line 'PubkeyAcceptedKeyTypes=+ssh-dss,ssh-rsa' on SSH-config line number 247

because of ssh_config.py:132
match = re.search(r"^(\w+)\s+(.+)$", line)

In addition, the line number is wrong:
  1 #------------------------
241 Host gdndev112 gdndev112.
  1     HostKeyAlgorithms=+ss
  2     PubkeyAcceptedKeyType
  3

Probably both are wrong:

Configuration options may be separated by whitespace or optional whitespace and exactly one ‘=’; the latter format is useful to avoid the need to quote  whitespace when specifying configuration options using the ssh, scp, and sftp -o option

You are right, currently regex is working for reading config parameters assuming only whitespace separation, I'll have to update regex to cover also optional "=" separator when "reading" the ssh config file.
However when ssh config file is changed or re-rendered due to adding or changing parameters, only one "style" should be preferred. That could be handled trough embedded meta config I guess, or some ENV var.
I would avoid supporting mixes of both types when reading and re-writing the same config file, at the end, that was the point of the tool for me, to be consistent in specific style and keeping the config "clean"-ish. :)
But from your Host definition I can see I have totally overlooked option to define multiple hostname definitions on the same line!

The Host directive can contain one pattern or a whitespace-separated list of patterns.

For instance:
Host test test.tmp
    ...

In this case parsing the host name internally will try to use it as test text.lab... This looks like it would not cause big issue, and even rendering configuration back will work, however... for sure its not correct! :)
And then using some TUI feature, connect options will not work as they take the name part and pass it to local ssh or sftp shell commands via subprocess fork.
In this case that would not work as expected, as it would result in ssh test test.tmp execution, which would establish connection to test host, but then try to execute test.tmp command. :)
As I have some new changes that I haven't pushed in a while, I'll try to merge some of this fixes as well.

Unfortunately I had to update all unmerged changes, and not in very clean way... :/
Anyway main branch is now up to date.... but not really ready for release to PyPI.
In main branch, I've added support for multiple entry names in config file, and parsing of config file with optional "=" symbol between keyword and attributes, with tests that cover that. Alt names are visible in the object and renderable in all currently supported styles in outputs (and will persist config changes trough sshc commands).
If you want to test current release from main branch, you can install it from source.
(its alpha... so it has some new stuff coming to TUI part, but only visual, not functional yet)
!! Please note that although parsing can now properly read parameters with "=", if configuration is edited, output rendering will default to using just space as separator. So if you prefer to have "=" in your config files, use only show and list commands. :)
Otherwise your config will be re-rendered with spaces as defaults.
I plan to add this as other "global config" option, that can be changed on the fly, and it will affect and re-render whole config with one of the preferred styles.


[Feature]  smaller script

Device
Other
Operating System
Android
Browser
Other
Suggestion
It is possible to make a smaller version with only one language option, English or only with high bitrate and co-op mode, preferably lower than 280kbps, use for a browser where the maximum size is this

Which browser has this limitation?

berry browser, as it is a very specific use it is not necessary that much dedication, it is better to try and ask

Sorry but this will take a lot of work


The synth produces empty templates when modules with constructs not imported from a package

Description of the bug:
We've developed a lib with constructs, publishing it on the internal npm registry. We want to import modules directly to make development faster, bypassing npm packaging. Npm has a feature for this https://docs.npmjs.com/cli/v9/commands/npm-link
When it is used, cdk synth creates empty templates
Reproduction Steps:
import { myconstruct } from "../mylib" (or using package name after applying npm link)
Error Log:
No errors, constructs that imported from the package sythed correctly, alongside empty files for constructs imported from the filesystem
Environment:
OSx, Node18
Other:
I can capture stack trace or debug info, but I am not sure what to do it with the cli. It should be pretty easy to reproduce as well.

This is :bug: Bug Report

@OperationalFallacy Can you share your exact setup please? That is, which dependencies are defined in the library that is being linked, and which ones are defined in the library that does the linking?

I have a similar setup. I don't use npm link, but this gets the job done. NPM package is cloned & extracted from the git repository.
  "dependencies": {
    "my-cdk8s-library": "git+ssh://git@github.com:my-org/my-cdk8s-library.git#semver:v0.5.0"
  },


[TEST][IGNORE] Remove drag&drop from FTP

Resolved / Related Issues
Items resolved / related issues by this PR.

Closes #issue...
Related #issue...

Details of Changes
Add details of changes here.

Added...
Fixed...

Validation
How did you test these changes?

[ ] Built and ran the app
[ ] Tested the changes for accessibility

Screenshots (optional)
Add screenshots here.

/azp run

/azp run


sample start for unit testing

This ended up being a little more involved than I expected; hopefully it's still useful. I went ahead and did some minor restructuring so we can do the "correct" approach of swapping out real vs. test implementations of a thing.
Some notes:

I took the command and put it in a runCmd helper; the idea there is that runCmd accepts all the state required to do i/o since that's what we want control over when we go to test
Test cases can be added to the cases list
I didn't add an affordance for testing writing to a file, but hopefully it's clear how to extend what I set up to cover that
I named some nested structs just to make reuse easier; more of that could be done.

It might seem like a lot in root_test, but a lot of it (setting up cases and looping over it, making a test implementation of an interface) is very standard Go stuff that can be reused/referenced for other projects. You can also save a lot on code by using a library like moq, but adding that here would be a lot more cognitive load than just writing up a quick and dirty stubber.
Let me know which bits are confusing and I'm happy to explain them in detail!

@vilmibm : love everything here!  last question: what change would you make to the workflow to run the unit test as part of it?  :)

I'm going to follow up around https://github.com/actions/starter-workflows/blob/main/ci/go.yml after this rather than blocking this review

andyfeller@Andrews-MacBook-Pro:gh-dependency-report/cmd ‹test-suggestions*›$ go build -v
andyfeller@Andrews-MacBook-Pro:gh-dependency-report/cmd ‹test-suggestions*›$ go test -v
=== RUN   TestCommand
=== RUN   TestCommand/example_test
2022-01-26T23:10:22.843-0500	INFO	cmd/root.go:80	Processing repos: [REPO]
2022-01-26T23:10:22.843-0500	DEBUG	cmd/root.go:122	Processing OWNER/REPO
2022-01-26T23:10:22.843-0500	DEBUG	cmd/root.go:143	Processing OWNER/REPO > cool.pkg
2022-01-26T23:10:22.843-0500	DEBUG	cmd/root.go:154	Processing OWNER/REPO > cool.pkg > Great package
--- PASS: TestCommand (0.00s)
    --- PASS: TestCommand/example_test (0.00s)
PASS
ok  	github.com/andyfeller/gh-dependency-report/cmd	0.223s
andyfeller@Andrews-MacBook-Pro:gh-dependency-report/cmd ‹test-suggestions*›$ pwd
/Users/andyfeller/Documents/workspace/andyfeller/gh-dependency-report/cmd


Branch find name 1

Edit/Add Find n/, Find r/ . Fix test cases issues
Closes #44  , closes #46  ,

@e0260222 Hi Weizhong, Please help to add milestone and merge it. thanks

LGTM


use proc_macro::... -> use crate::proc_macro::... in examples?

In a 2018 edition crate, the recent module system changes prevent the current README example from working on a recent nightly. Referencing the proc_macro crate as crate::proc_macro appears to resolve the problem for me. Is this the correct fix?

Yes, I would use crate::proc_macro:: until we land the stabilization (and possibly backport) for https://github.com/rust-lang/rust/issues/55599. Let's update the documentation to use 2018 edition as soon as the edition is officially released.

Updated example code to 2018 edition in 87f72917ddabadb12fb1eb614559e07dc91dfb23.


[Bug]: Issue deploying Nodejs project

Description
NODEJS PROJECT / SERVER DEPLOYMENT ISSUE
Minimal Reproduction (if possible, example repository)
I was testing the system, but each time i try to deploy a node project.

It crushes 500 Something is not okay
it keeps loading and loading.

Otherwise amazing work!
Exception or Error
No response
Version
4.0.0-beta.256

Based on the image, it seems that you are running a self-hosted version. It appears that the Redis container that Coolify starts is not running.
Can you please check if it's running properly?

Based on the image, it seems that you are running a self-hosted version. It appears that the Redis container that Coolify starts is not running.
Can you please check if it's running properly?

Its working now. thanks alot!
i am testing mongodb. how can i change the mongodb default db name test to any name of choice?
MONGODB_URI=mongodb://root:zobFryH4RjGVZorVwDI36mIqKUrvR6S82eumrKvR1LDyEcnz5t5G1vlgdQKQ1IBr@<IP_ADDRESS>:5436/techdevcyber?directConnection=true

Based on the image, it seems that you are running a self-hosted version. It appears that the Redis container that Coolify starts is not running.
Can you please check if it's running properly?

Its working now. thanks alot!
i am testing mongodb. how can i change the mongodb default db name test to any name of choice? basically my node server doesnt connect to mongodb when i provide specific db name. am i missing something 😃?
MongoParseError: Invalid scheme, expected connection string to start with "mongodb://" or "mongodb+srv://" at new ConnectionString (/app/node_modules/mongodb-connection-string-url/lib/index.js:86:19) at parseOptions (/app/node_modules/mongodb/lib/connection_string.js:188:17) at new MongoClient (/app/node_modules/mongodb/lib/mongo_client.js:46:63) at /app/node_modules/mongoose/lib/connection.js:802:16 at new Promise (<anonymous>) at Connection.openUri (/app/node_modules/mongoose/lib/connection.js:799:19) at /app/node_modules/mongoose/lib/index.js:414:10
this is how i am doing. MONGODB_URI=mongodb://root:zobFryH4RjGVZorVwDI36mIqKUrvR6S82eumrKvR1LDyEcnz5t5G1vlgdQKQ1IBr@<IP_ADDRESS>:5436/techdevcyber?directConnection=true

without the name the connect is working.

Based on the image, it seems that you are running a self-hosted version. It appears that the Redis container that Coolify starts is not running.
Can you please check if it's running properly?

it working. thanks


Simplify QC workflow replacing script with dodola v0.18.0 command

This simply swaps an argo-nested script for the simpler dodola command.
We couldn't do this in dodola releases before v0.18.0 because of memory issues resolved in this release.

[ ] closes #xxxx
[ ] tests added / passed
[ ] docs reflect changes
[ ] passes flake8 downscale tests docs
[ ] entry in HISTORY.rst

[summarize your pull request here]

I tested this update manually, here: https://argo.cildc6.org/workflows/default/qualitycontrol-check-cmip6-test-5kckg

@emileten when you have a minute, can you give this a quick check? Thank you for your help.

@brews the input which failed -- where did you pick the input path from ? I see that it's downscaled data. Making sure it's not our current output.

Good question, @emileten. That's the default arguments to the QC workflowtemplate.

Ah I had dropped this, sorry @brews. I had just that question. It looks good otherwise !


Got wrong file path in task if has gulp.dest after the task.

I am trying to gather some information of JavaScript files. So I wrote a simple task and recorded file.path in an JavaScript Object and then copy files into another directory named output with gulp.dest
I didn't get any error result until this evening and I don't think I did any changes on my tasks.
There is one JavaScript file, nothing different with other JavaScript files, always got the wrong file.path that the file.path got the new path after the file copied into output dir.
The code of task in gulpfile.js
gulp.task( 'js', () => {
    return gulp.src( 'src/**/*.js', { buffer : false } )
        .pipe( pkg() )
        .pipe( gulp.dest( 'output' ) );
} );

The code of task pkg
const Transform = require( 'readable-stream/transform' );
const rs = require( 'replacestream' );
const utils = require( '../utils' );

const map = {};

module.exports = () => {
    return new Transform( {
        objectMode : true,
        transform( file, enc, callback ) {
            if( file.isNull() ) {
                return callback( null, file );
            }
            console.log( '++++++++++', file.path ); // It can display correct file path for all files
            file.contents = file.contents.pipe(
                rs( /__PACKAGE__\.([\w\d\-_]+)/g, ( m, n ) => {
                    console.log( '------------', file.path );
                    // It can display correct file path for all files except one file

                    const pkg = utils.getPackage( file.path );
                    if( !map[ pkg ] ) {
                        map[ pkg ] = {
                            id : 'ns-' + utils.uid()
                        };
                    }
                    return map[ pkg ][ n ];
                } )
            );

            callback( null, file );
        }
    } );
};

Output of console.log
+++++++++++ /Users/L/workspace/amazing/fe-amazing/src/static/packages/select/index.js
----------- /Users/L/workspace/amazing/fe-amazing/output/static/packages/select/index.js

If I remove the .pipe( gulp.dest( 'output' ) ), It will be working all right.
gulp -v
[21:57:42] CLI version 1.2.2
[21:57:42] Local version 3.9.1

npm -v
3.10.3

node -v
v6.7.0

When  you call callback( null, file ); you're telling the stream that you're done with that file and to pass it along to the next plugin (which is gulp.dest() in your case). gulp.dest() is changing the file.path property before the replacestream has a chance to use it, so it's showing the updated path.
If you wait for the replacestream processing to finish before calling callback( null, file );, the paths should be correct:
const Transform = require( 'readable-stream/transform' );
const rs = require( 'replacestream' );
const utils = require( '../utils' );

const map = {};

module.exports = () => {
    return new Transform( {
        objectMode : true,
        transform( file, enc, callback ) {
            if( file.isNull() ) {
                return callback( null, file );
            }
            console.log( '++++++++++', file.path ); // It can display correct file path for all files
            file.contents = file.contents.pipe(
                rs( /__PACKAGE__\.([\w\d\-_]+)/g, ( m, n ) => {
                    console.log( '------------', file.path );
                    // It can display correct file path for all files except one file

                    const pkg = utils.getPackage( file.path );
                    if( !map[ pkg ] ) {
                        map[ pkg ] = {
                            id : 'ns-' + utils.uid()
                        };
                    }
                    return map[ pkg ][ n ];
                } )
            )
            .on('end', function() {
                callback( null, file );
            });
        }
    } );
};

@doowb Thanks for your comment. But still something wrong with your code and I did some changes to make it work well.
module.exports = () => {
    return new Transform( {
        objectMode : true,
        transform( file, enc, callback ) {
            if( file.isNull() ) {
                return callback( null, file );
            }
            const content = file.contents.pipe(
                rs( /__PACKAGE__\.([\w\d\-_]+)/g, ( m, n ) => {
                    console.log( file.path );
                    const pkg = utils.getPackage( file.path );
                    if( !map[ pkg ] ) {
                        map[ pkg ] = {
                            id : 'ns-' + utils.uid()
                        };
                    }
                    return map[ pkg ][ n ];
                } )
            );
            file.contents.on( 'end', () => {
                file.contents = content;
                return callback( null, file );
            } );
        }
    } );
};

You helped me to solve a big problem. And I can't thank you enough.


[WIP] [SRVKS-1123] Add perf tests

What this PR does / why we need it:
Which issue(s) this PR fixes:
JIRA: SRVKS-1123
Does this PR needs for other branches:
YES 1.11+

Backports upstream work to 1.10 (can't be done simply by cherry-picking)
Moves OCP scripts under openshift (Reto's scripts from here https://github.com/ReToCode/ocp-serverless-perfromance-testing)
Adds performance test images to be built for each CI run
Adds a new ElasticSearch dashboard (to integrate with the midstream infra), upstream InfluxDB is used.
Refactors metrics client to write to ElasticSearch/OpenSearch
Adds a new command to the Makefile to trigger performance tests (uses run-all-performance-tests.sh script).
Customized scenarios are not run.

Sample visualization of the es dashboard:

Next step is to setup a CI job to use this (run periodically and on-demand).
Pending improvements:

Control variance eg. make sure that Serverless pods are isolated from OCP stuff eg. Prometheus and the targeted backends are distributed evenly on worker nodes (https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints, https://access.redhat.com/solutions/6788741).
Add metadata to the documents via https://github.com/cloud-bulldozer/go-commons/tree/main/ocp-metadata so we can query data per Serverless or OCP version etc.
Use kustomize or some other tool to improve yaml patching.

/test 413-test-e2e-aws-ocp-413

/assign @ReToCode

I tested a bit the pod distribution on OCP worker nodes. So with a simple K8s deployment I get node distribution on the 12 nodes and 120 replicas:
ci-ln-c4i3vi2-72292-4jjv2-worker-a-5ljcg    11
ci-ln-c4i3vi2-72292-4jjv2-worker-a-m4h77    10
ci-ln-c4i3vi2-72292-4jjv2-worker-a-sj4sd     9
ci-ln-c4i3vi2-72292-4jjv2-worker-b-8vdvq    11
ci-ln-c4i3vi2-72292-4jjv2-worker-b-gg56z    10
ci-ln-c4i3vi2-72292-4jjv2-worker-b-vnk4q     9
ci-ln-c4i3vi2-72292-4jjv2-worker-c-kpkjv    10
ci-ln-c4i3vi2-72292-4jjv2-worker-c-kqclw    10
ci-ln-c4i3vi2-72292-4jjv2-worker-c-njj77    10
ci-ln-c4i3vi2-72292-4jjv2-worker-f-4b4tr    10
ci-ln-c4i3vi2-72292-4jjv2-worker-f-7455p    10
ci-ln-c4i3vi2-72292-4jjv2-worker-f-njphx    10

/retest

I'm wondering if it would make sense to set both requests and limits for the Jobs that run the test. This could reduce the variance between runs.

@mgencur yeah could be useful, the more controlled the env the better should be ideally. I will check.

/retest

/retest

closing will create a new one, deps changes create a lot of conflicts.


CASMCMS-6989: Adds playbook for adding cfs and bos packages to compute

Summary and Scope
This adds a new playbook that can be run in order to add the cfs-state-reporter and bos-reporter packages so that they can be removed the image recipe.  There will be a corresponding change in the docs to add this layer in image customization.
The new playbook will not work completely until the bos-v2 branch is merged and deployments include the bos-reporter in nexus.
Issues and Related PRs

Resolves CASMCMS-6989

Testing
Tested on:

Hela

Test description:
Tested image creation with the new layer.  The test did fail on bos-reporter because it is not yet available.
Risks and Mitigations
None
Pull Request Checklist

[X] Version number(s) incremented, if applicable
[X] Copyrights updated
[X] License file intact
[X] Target branch correct
[X] CHANGELOG.md updated
[X] Testing is appropriate and complete, if applicable
[X] HPC Product Announcement prepared, if applicable

Should there have been a playbook for Application nodes?


Nexus repository manager warning: License expires in 36 days.

Need to understand what this means before the time expires and we're left without a way to release our Java client packages

We received the following email from Sonatype:
Greetings Maven Central Publisher,

We are reaching out to you because you are registered as a publisher with Maven Central’s [oss.sonatype.org](http://oss.sonatype.org/) or [s01.oss.sonatype.org](http://s01.oss.sonatype.org/) services. Although there are no immediate changes to how you publish, we want to inform you of a number of upcoming changes to your account. Currently, you manage your account credentials through [issues.sonatype.org](http://issues.sonatype.org/). On Tuesday the 12th of March, we are moving account management to a temporary service located at [https://account.oss.sonatype.org/realms/central-ossrh/account/](https://u21795309.ct.sendgrid.net/ls/click?upn=u001.cdbupahfLeeV0JrmnGgqhmrkSpaJs-2FAXk1UxmFQyoqkxghtD-2BsbQvbtncphSXH6Jx1NTrruOQ5KGQt9XimpaQQd2ELcBR78XdWSabPCyAws-3DCQSg_4bjYlWYs0AyLtX64Sx1A0u1pSQ50xNugKQDNuJ-2BK5QRnoy0lwQSYvPwmQ533SaqHlHHJKC7KxyhAXhkg1SI25s0y9EE3cKgcTqW50DI-2Fv8W2q-2Bv6I7FU0WPyjq9ZPt-2Fp6j-2BDMuaeihRkU6uVB2H5pKDFNv0e-2FxL9zoWqDnaRA333X23iIyD6Dsk8n-2BMuTTmaOc-2Fpqe87l6EJzQ2O1TlecvbwiUWPPoHx4YJRqo8nOuByoOetGVCOjFsj3aSotG9H0e3u1Km4MAPY9LkRmwlK37PFAaPJFLB10tKYAxQIATXo60DR6H8Kwr4z31e4B8-2FmV-2BGgo0ObUT67IqwOIZQtlnwefGxbeC9DybG-2BZvDpZfTb-2BOk1WHeWwM1od6L1gcbJa97xiU0PRmEuyz5-2B2Bd-2FoLFGeh-2FMLiiyOn-2Fv5l-2FCWa0HOmajHSwfdrSRXF6gxZ0Lz-2F63z9R0SQjelXx53nlu3zxGTxAqSBenT08094TE-2FJvMOeBKXg9PPbir3vm47-2BTVayTR04LLpV8NsGE6wi3A6rFdn075D2UYXlcB6Ibtelyrgiz-2BDCYW6ifctXByYW4VaFL-2FkDfsPJZ-2BLk1Sf5VEOYLtCwe4CQOO9ULouIfHLrtVd3LGhBF-2FWF6Obqhes2pgOnFjduQmo2Edi9Hi5sGzqABwpnlks1eaxDWZjmshl8FQ9AlPb8hRy4VxnRf0b3QHJbGZTMhKYXdn5OMTjJChe84ms0-2BOGcNnpkDPeXm9VLmHjP0lKEkrQaM2IlvYKLDxUukc-2Bzsfd3HxJ52jlivj0McP-2ByntYb1m7X-2BJMBjUargpNQAdkn2f3-2F3Z5vYSG2-2FzfQHn6gVy35BZsZQJhNjasosO-2BrBoIo-2F5o-2FD3k1ss7DPJWHqV8EoEaXMAcVQRb8TFNhVzLe3yawVdmS81dGtFBI2hslWZ-2BHSJKxPOGGlb2SynK70UjuG-2FB7dLoTRYTsTW3Tb31sMXPp7bbWO23hOq548IpJTr4Mm2xH3lnNqJdOZYcoFD2hcL-2FFtpLX2Fgg-2F0qrakZYgbaX5iVuJgVLdC8A-3D-3D). This should hopefully involve minimal disruption for our publishers. You will still use the same username and password to log in to the OSSRH instance, and should only need to interact with the new account management service when you wish to change or reset your account credentials.

Also, you will likely see information directed at new OSSRH publishers registering via [central.sonatype.com](http://central.sonatype.com/) (documented here -- https://central.sonatype.org/register/legacy/). While this does not impact you at the moment, you should be aware that we are moving account management to a unified system across the Central Publishing Portal and OSSRH. We will communicate again before that takes place, to ensure that our users have a clear understanding of where and how they will be able to manage their accounts.

You may also have been impacted by the retirement of [issues.sonatype.org](http://issues.sonatype.org/) which you previously used for signing up for new namespaces and getting publishing support. We have transitioned to using the same workflow system used for our paid products. To generate a ticket, you can email [central-support@sonatype.com](mailto:central-support@sonatype.com). We acknowledge that, in doing so, you have lost some of the self-service functionality for requesting and being granted publisher access to new namespaces. We are working on restoring that functionality on [central.sonatype.com](http://central.sonatype.com/). The migration to a unified account management system we mentioned previously enables us to build integrations between the two services later in the year, such as displaying a user’s complete list
of registered namespaces and allowing self-service migration to the Publisher Portal.

Thank you,
The Central Team

Currently the new sonatype portal is still not fully active. Will check back 7 days before expiry

It's a miracle!
My account is no longer about to expire... 🤔


UMLs or data flow diagram for Dev plugin

Add gliffy diagrams to wiki

flow of data from module to module
detailed data flow with most common use case like policy export-build with 1 environment property

Tracked internally by US573761.


feat(flags): Better support for flags

Codecov Report

Merging #1 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master     #1   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           4      5    +1
  Lines          40     51   +11
  Branches        8     12    +4
=====================================
+ Hits           40     51   +11

Impacted Files
Coverage Δ

lib/common/prompt.js
100% <100%> (ø)
:arrow_up:

lib/common/formatArguments.js
100% <100%> (ø)

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 80cecfb...8ed1c89. Read the comment docs.


Remove tensor flow datasets from the package

As described in the current README (and can be seen in the redesigned pipeline here) we will no longer be using TFDS for the dataset conversion and creation. This is in part because it is a bit of a dependency nightmare currently (although this will no doubt improve as it matures) but also because we wish to have more flexibility for users when it comes to conversions between different input sets, and not rely on tensorflow etc.
In preparation for the creation of the msp2model converters, we should:

[ ] Remove all tfds related code from the package
[ ] Make sure it now builds correctly

wouldn't it make more sense to remove the code bit by bit as we are replacing it by new code that does the job without tfds?
Or is that what you meant anyway?


Steam VR Controller not rotating at all.

In Steam VR the controller position tracks, just not any rotational data at all.

Have you already done the magnetometer calibration for your controller?

@HipsterSloth yes. When I test tracking it rotates, but not in steam.

Closing old support issues. If this is still a problem please post a request to the google group:
https://groups.google.com/forum/#!forum/psmoveservice


HDDS-8024. When readChunk from a datanode fails, retry other datanodes.

What changes were proposed in this pull request?
When failing read chunk from a datanode, exclude it and retry other datanodes.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-8024
How was this patch tested?
Updated TestHSync

@szetszwo thanks for the improvement.  Sorry for being late, but I tried this fix in repeated CI runs and it didn't seem to fix the problem.
56 out of 300 iterations failed:
https://github.com/adoroszlai/hadoop-ozone/actions/runs/4326162668

@adoroszlai , thanks a lot for testing it!
	at java.io.DataInputStream.read(DataInputStream.java:149)
	at org.apache.hadoop.fs.ozone.TestHSync.runTestHSync(TestHSync.java:201)
	at org.apache.hadoop.fs.ozone.TestHSync.runTestHSync(TestHSync.java:154)
	at org.apache.hadoop.fs.ozone.TestHSync.testO3fsHSync(TestHSync.java:122)

https://github.com/adoroszlai/hadoop-ozone/actions/runs/4326162668/jobs/7553254946#step:5:6237
The line numbers do not match the latest code.  I guess it was testing the old code?

The line numbers do not match the latest code. I guess it was testing the old code?

No, it was testing the PR, you can find diff here: https://github.com/apache/ozone/compare/master...adoroszlai:hadoop-ozone:HDDS-8024-repeat
Line numbers in TestHSync are off because a01676a9af changed that file on master in the meantime.

Line numbers in TestHSync are off because https://github.com/apache/ozone/commit/a01676a9afccf4d7c4c80066d999a087973a9def changed that file on master in the meantime.

@adoroszlai , https://github.com/apache/ozone/commit/a01676a9afccf4d7c4c80066d999a087973a9def is HDDS-8029 which is BEFORE this commit https://github.com/apache/ozone/commit/3bbb5742c5f494d940ced1553e5772eecfb6398c as shown below.  Anyway, could you run the test again with the latest code?
commit 3bbb5742c5f494d940ced1553e5772eecfb6398c
Author: Tsz-Wo Nicholas Sze<EMAIL_ADDRESS>Date:   Fri Mar 3 17:03:45 2023 -0800

    HDDS-8024. When readChunk from a datanode fails, retry other datanodes. (#4336)

commit 88292e8a446d183d78f74aefda2b72d3e02ab2f7
Author: Stephen O'Donnell<EMAIL_ADDRESS>Date:   Fri Mar 3 21:00:45 2023 +0000

    HDDS-8075. ECReconstructionCoordinatorTask.runTask should catch Exception (#4342)

commit a432438c363622d287fb4ac3524394fa2ec5fc13
Author: djordje-mijatovic<EMAIL_ADDRESS>Date:   Fri Mar 3 21:33:47 2023 +0100

    HDDS-7210. Missing open containers show up as "Closing" on the container report. (#4207)

commit a01676a9afccf4d7c4c80066d999a087973a9def
Author: Wei-Chiu Chuang<EMAIL_ADDRESS>Date:   Fri Mar 3 11:14:41 2023 -0800

    HDDS-8029. [hsync] Outputstream in encrypted buckets do not return the correct stream capabilities. (#4316)

The line numbers do not match the latest code. I guess it was testing the old code?
Line numbers in TestHSync are off because a01676a9afccf4d7c4c80066d999a087973a9def changed that file on master in the meantime.
a01676a is HDDS-8029 which is BEFORE this commit 3bbb574

The lines added by a01676a were not present in your PR, as it was based on a prior state of master:
* 3bbb5742c5 HDDS-8024. When readChunk from a datanode fails, retry other datanodes. (#4336)
* ...
* a01676a9af HDDS-8029. [hsync] Outputstream in encrypted buckets do not return the correct stream capabilities. (#4316)
* ...
| * 6fa8fc1291 (HDDS-8024-repeat) TEST 10x30x TestHSync,ITestOzoneContractCreate
| * 91958b3e0f (HDDS-8024) Fix test failures.
| * 67a8b10fdb HDDS-8024. Intermittent inconsistent read in HSync tests.
|/
* 84f1523d24 HDDS-7869. Log configuration on component startup. (#4271)

Now that the PR has been merged and became 3bbb5742c5f494d940ced1553e5772eecfb6398c on master, line numbers are different, due to the presence of a01676a9af.  But that doesn't mean I was testing code without the fix.
Now I have launched a new run with current master: https://github.com/adoroszlai/hadoop-ozone/actions/runs/4347182297

new run with current master: https://github.com/adoroszlai/hadoop-ozone/actions/runs/4347182297

This one failed, too.
Example:
Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 54.159 s <<< FAILURE! - in org.apache.hadoop.fs.ozone.TestHSync
org.apache.hadoop.fs.ozone.TestHSync.testO3fsHSync  Time elapsed: 3.85 s  <<< ERROR!
java.io.IOException: Inconsistent read for blockID=conID: 1 locID:<PHONE_NUMBER>19200001 bcsId: 0 length=97 position=64 numBytesToRead=33 numBytesRead=-1
	at org.apache.hadoop.ozone.client.io.KeyInputStream.checkPartBytesRead(KeyInputStream.java:175)
	at org.apache.hadoop.hdds.scm.storage.MultipartInputStream.readWithStrategy(MultipartInputStream.java:97)
	at org.apache.hadoop.hdds.scm.storage.ExtendedInputStream.read(ExtendedInputStream.java:54)
	at org.apache.hadoop.fs.ozone.OzoneFSInputStream.read(OzoneFSInputStream.java:64)
	at java.io.DataInputStream.read(DataInputStream.java:149)
	at org.apache.hadoop.fs.ozone.TestHSync.runTestHSync(TestHSync.java:211)
	at org.apache.hadoop.fs.ozone.TestHSync.runTestHSync(TestHSync.java:164)
	at org.apache.hadoop.fs.ozone.TestHSync.testO3fsHSync(TestHSync.java:132)

@adoroszlai , thanks for the update.  Sorry that I may have misunderstood how the test was run.

This one failed, too.

The line number in this stack trace matched the current code.  Let me take a look.

@adoroszlai  found that getBlock also does not retry other datnaodes.  Submitted #4357


Drop layout:include/layout:replace for the new Thymeleaf 3.0 fragment expressions

Looking at the new fragment expressions feature of Thymeleaf 3.0, it basically does what layout:include/layout:replace do.  If that's the case, then maybe I can remove layout:include/layout:replace from this dialect.

So fragment expressions can do the job, but it approaches the problem at a different angle.  If used the way that layout:include/layout:replace are documented, the resulting code can look very unreadable! (because the selection mechanism will have to include the scope at which the inclusion/replacement takes place)
I think I'll leave layout:include/layout:replace processors well enough alone.


Add environment variable DISABLE_ESLINT

The idea behind this new environment DISABLE_ESLINT_DEV variable is to:

speed up compilation time on dev mode
allow developers to write temporary code without caring about ESLint too much.

At the moment 2) is pretty hard, because depending on your ESLint config you might not even able to have a console.log or an unused variable in your code without seeing your dev build failing, making the experience pretty frustrating.
Open for feedback. I am actually uncertain whether we should have instead just a DISABLE_ESLINT setting that would disable ESLint for both environments.
Related issues:

https://github.com/facebook/create-react-app/issues/7828
https://github.com/facebook/create-react-app/issues/7078

I've changed it to DISABLE_ESLINT as it would make this more useful for all the projects that already have a lint step in CI and/or precommit hooks, so to avoid duplicated linting.

Hi team, any updates on this one?

I think this will likely be a config flag, we've been talking about adding a config file in the next major release of CRA. Does anyone else in the team have thoughts? @ianmcnally or @ianschmitz perhaps?

Just my 2¢, but I think it would be awesome if a CRA project could have a cra.config.js file at the top-level of the project that worked similarly to next.config.js, i.e. CRA's config could be passed to a function-export from cra.config.js and tweaked as needed.

@michaelsbradleyjr That's on the cards for v4 at this stage.

I don't care about CRAs eslint rules for two reasons. First one, I have own rule set, which I use through multiple projects. And the second, I don't want that eslint slows me down while development. Therefore a big +1 for this PR.

Thanks, @giuband! This is a great thing to have supported natively, since it's so frustrating having the build break on you while you while you're actively coding, and you have to stop, add a disable comment, etc. It just breaks the flow.
Please, let me know if I can be of any help!

It's very useful for this issue: #8096

any update on this?

@mrmckeb @ianmcnally any updates on this one? Is it still under the radar to offer more flexibility regarding running or not eslint?

Closing as this has been implemented in https://github.com/facebook/create-react-app/pull/10170. Thanks @mrmckeb !


bump extension gallery for server reports

@dzsquared Do the latest builds have all the changes you want for this?

@dzsquared Do the latest builds have all the changes you want for this?

It looks like @alanrenmsft took care of this while my github notifs weren't functioning - thanks! (closing)

It looks like @alanrenmsft took care of this while my github notifs weren't functioning - thanks! (closing)

@dzsquared oops, sorry, I didn't realize the very existence of this PR, otherwise I would have reused it. haha

@dzsquared oops, sorry, I didn't realize the very existence of this PR, otherwise I would have reused it. haha


Angular & angular/material compatibilities and deprecated Md modules on build

Bug :
I am using @angular/material & @angular/cdk version "2.0.0-beta.7" and @angular/core v4.0.2
when I import a module from the '@angular/material' as the "MdCheckboxModule" the IDE highlights it with the ERROR (@angular/material has no exported member 'MdCheckboxModule') but it works fine with <md-..> tags, the problem is when I run a webpack cmd to build the frontEnd code to the dist directory webpack throws an ERROR (@angular/material has no exported member 'MdCheckboxModule') and the same error is shown in the navigator's console
When I replace "MdCheckboxModule" by "MatCheckboxModule" and the <md-..> tags with <mat-..> it don't work locally but it works when I build the code
Is there any specific version that I can use with my angular/core version to avoid this error on build plz
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular :
"@angular/core": "4.0.2",
"@angular/animations": "4.0.2",
"@angular/cdk": "^2.0.0-beta.7",
"@angular/material": "^2.0.0-beta.7"
TypeScript:
"typescript": "~2.2.1",
OS: Linuxmint 18.2 Cinnamon

Please keep GitHub issues for bug reports / feature requests. Better avenues for troubleshooting / questions are stack overflow, gitter, mailing list, etc.


Won't work with containerization

Well, I'm trying to build container image. And I stuck with this python error, this stderr appears when I'm running your script in container.
STDERR
?main ~/Desktop/devroom/ChatGPTerminator> podman run -it --name gpterm gpterm
Traceback (most recent call last):
  File "/usr/local/bin/gpterm", line 5, in <module>
    from gpterminator.__main__ import main
  File "/usr/local/lib/python3.9/site-packages/gpterminator/__main__.py", line 1, in <module>
    from . import GPTerminator
  File "/usr/local/lib/python3.9/site-packages/gpterminator/GPTerminator.py", line 168
    match msg["role"]:
          ^
SyntaxError: invalid syntax
exit 1

Dockerfile
FROM python:3.9-alpine
WORKDIR /root
COPY . .
RUN mkdir -p /root/.config/gpterminator
RUN pip install .
ARG APIKEY
ENV OPENAI_API_KEY=$APIKEY
CMD ["gpterm"]

Match case was introduced in Python 3.10, try updating and trying again!

I plan to switch to if else statements soon to make it more comparable with older versions...

Alright, I'll check soon

Everything is fine


Changed Actions schedule to SAT 22:00

No review needed.

Coverage remained the same at 32.794% when pulling 83ae6845dec7ab5e00d487fc0ce9ca3471c483de on andy/testrun into 3254dfe255679f7d66a980178caa4a8ce3dd5a4b on master.


Engine often fails to grab input on vid_restart or r_fullscreen toggling

I experience this bug a lot were the game fails to grab input after vid_restart. The grab failure is easy to reproduce by putting the game window behind another unrelated window while the reloading is going on, waiting enough to make sure the whole reload process complete (and map is displayed again) before putting the game window on foreground.
Also, toggling fullscreen / windowed mode is likely to reproduce the bug, especially going from fullscreen to windowed mode.
Better a load a map first to reproduce the bug.
A vid_restart call while keeping the game in foreground usually grabs input again (but I'm afraid it may only be done on a TTY console in some case).

It looks like the bug also occurs when Alt-Tabbing from fullscreen: input is lost when returning to the game.

This bug is critical. Players quit the game in a middle of playing because of this. @slipher you seems to know a bit the input code, do you have any idea about that bug?
If we don't know how to fix it we better workaround it by calling vid_restart on Alt-Tab. Releasing something with such bug in it would be a disaster.

Right, according to this : https://discourse.libsdl.org/t/problem-with-switching-between-full-screen-to-window-mode/24689

You’ll need to use: SDL_SetWindowFullscreen(mWindow, 0); to get out of fullscreen mode, and then use: SDL_SetWindowSize(SDL_Window* window, int w, int h) to set the size of the screen.

So it seems you need to tell SetWindowSize and it should start working properly. Note a comment from the bottom

Calling SDL_SetWindowSize(SDL_Window* window, int w, int h) in the start of the next frame was the solution.

I had a look at adding the SetWindowSize, but i'm not sure how it relates to GLimp_StartDriverAndSetMode or GLimp_SetMode. Maybe you want the setwindowsize in one of those functions, and call it when the fullscreen switches back to windowed mode.
Best I could find, and it does seem quite relevant.

Related issues:

https://github.com/DaemonEngine/Daemon/issues/234
https://github.com/DaemonEngine/Daemon/issues/408
https://github.com/Unvanquished/Unvanquished/issues/1136

@bofh80 interesting!

Fixed by DaemonEngine/Daemon#409.

Fixed by DaemonEngine/Daemon#409.

I wonder if we can do improvements based on suggestion there: https://github.com/DaemonEngine/Daemon/issues/365#issuecomment-749806034.

I wonder if we can do improvements based on suggestion there: https://github.com/DaemonEngine/Daemon/issues/365#issuecomment-749806034.


ERROR QUERYING BOCKCHAIN

Entro a mi billetera y me dice esto:
ERROR QUERYING THE BOCKCHAIN
Y no me parecen los últimos movimientos ni las transferencia.
Me pueden ayudar por favor?
Saludos.

Good day, Thanks for reporting this.
We are aware of the issue and looking at some changes, but looks like we cant support Bitcoin at this stage.
As a solution the best we can suggest/advise would be to download Flarewallet or  Bitpay and importing your wallet there.

@glopezriv Good news, I transferred my BTC on th Bitpay wallet. I used these recovery tools.
I hope you will be able to restore your BTZ as well.
Unfortunately this is known. Bitpay did change their servers and at the moment there are no developer resources free to fix this within Particl Copay wallet. You have to move your BTC funds to another wallet. It even may be possible the Particl Copay wallet will abandon BTC support -but this is not final. At the moment, if you need to access your funds, you need to move.
Tool to extract keys (optionally, if needed): https://bitpay.github.io/copay-recovery/
Source of native BTC Copay wallet (see available for section):
https://github.com/bitpay/copay
How to:
https://support.bitpay.com/hc/en-us/articles/115003028346-How-do-I-move-my-wallet-from-Copay-to-BitPay-How-do-I-move-my-wallet-between-mobile-and-desktop-
Use your Particl Copay recovery phrase to recover your wallet on Bitpay Copay app.


Fix error responses from server so they get logged

We're logging the error from serving an error. We should always log the error that was served to ensure reporting systems get triggered.
Use an appropriate log level. Anything in the 5XX range should get logged as an error. 4XX should probably be info.

https://github.com/docker/notary/blob/master/server/timestamp/timestamp.go#L65 is getting logged as an error, and it should probably not be an error - this can happen if someone has metadata cached locally, and then tries to pull from a server that doesn't know about that metadata.  For instance if they uploaded signed metadata to one notary server, and then switched notary servers and tried to pull.


Remove obsolete tests (pool container configuration)

Code cleanup

one file was missed in the cleanup

wrong issue


useTransparentSessionID doesn't work

What steps will reproduce the problem?
In config/main.php set the session component config as follows:
'session' => [
            'name' => 'advanced-frontend',
            'useCookies'=>false,
            'useTransparentSessionID'=>true,
]

What is the expected result?
Session ID should be passed as a $_GET param.
What do you get instead?
Session ID is NOT currently passed in $_GET or anywhere else in the request.
Additional info

Q
A

Yii version
2.0.32

PHP version
7.3.8

Operating system
Linux

I confirm the issue.

PHP can't handle trans_sid via header() redirects (used in actionLogin() in case below).
You have to append the session_name and session_id manually to redirect.
Modify your actionLogin()
public funtion actionLogin()
{
// .... some code

$model = new LoginForm();
        if ($model->load(Yii::$app->request->post()) && $model->login()) {
            //return $this->goBack();
            return $this->redirect(['site/index', Yii::$app->session->name => Yii::$app->session->id], 302);
        }

// ... some code
}

This applies to all "POST-redir-GET" scenarios (login, update and delete for example).
Tested and works fine for me.

Seems can't be fixed from within the framework.


Add release notes count badge to tab

Marking this one as a draft purely on the basis that I'm not even sure this is desired, let alone implemented correctly.
Probably one for Dave to make a call on. Close PR/delete branch if it's not something we care about.
One thing to note is that this is driven by GitHub release count (what the tab actually renders) as opposed to the release reference count shown elsewhere on the package page (which is based on any tags (?)) so it's plausible this number will be different. Having said that, if we showed tags on the release notes page it could make sense to remove this extra field in the DB.
⚠ Schema change.
Branched off #1224 which is off #1213.

Going to close this off - it feels too confusing when compared to the other release count number (which is based on tags). 'Why are they different?' - some user


update to webpack 4

Upgrades to webpack 4
Fixes #86 and #85
Chunk ids can now be alphanumeric namedChunks (s/o @saveman71)
Bumps quite a few dependencies
Common chunks is no longer in webpack, remove tests around this
extract-text-webpack-plugin does not support webpack@4 and suggests switching to mini-css-extract-plugin instead, if you want a test for this to check support I could add one

Very quickly put together just to get rid of the deprecation warning in our console after upgrading to webpack 4. Let me know if I missed anything.

Tested this by pulling down my forked version and running locally and everything is working, including mini-css-extract-plugin.

AppVeyor seems to fail due to the node version being used I think? Without running the files through babel or something I think the easiest solution would just be to build on the latest LTS of node, the tests pass locally for me on<EMAIL_ADDRESS>

Tested this by pulling down my forked version and running locally and everything is working, including mini-css-extract-plugin.
AppVeyor seems to fail due to the node version being used I think? Without running the files through babel I think the easiest solution would just be to build on the latest LTS of node, the tests pass locally for me on<EMAIL_ADDRESS>Edit: Okay, updated appveyor and travis to use node 8. Took a few guess and check commits 😉

@ztoben Do you think you could fix #85 in this PR as well?
Thank you for the work already done here!

@kossnocorp, any chance you could take a look at this?

Wondering when will this get merged?

@ztoben @saveman71 @SebastiaanNijland thank you, guys! This PR was published as<EMAIL_ADDRESS>Any chance that some of you want to help me maintain the package? My priorities have shifted, and nowadays I'm entirely focused on my own business and date-fns. I would appreciate the help as the package obviously needs some love.

@kossnocorp, I'd be happy to help maintain it. I use it at work and get some time there to work on projects like these.

@kossnocorp, the same as my github handle.


L2DepositedERC20Deployment didn't work right way

ERC20_L1_to_L2_Deposit_and_Withdraw.cs
When I tried to test ERC20_L1_to_L2_Deposit_and_Withdraw.cs, I found that L2DepositedRC20Deployment didn't work right way.
Actually, L2DepositedERC20.sol contracts is inherited ERC20.sol and when the initialSupply is initialized as 0 in L2DepositedERC20.
However, after running the deploying code, and get the deployed smart contracts address, then import token with that address into wallet.
It is not 0, but random number I think.

Is there any problem?
In this test, I used
L1 as https://kovan.infura.io/v3/9aa3d95b3bc440fa88ea12eaa4456161
L2 as https://kovan.optimism.io
Another weird thing is receipt .DecodeAllEvents can't catch any event so that count = 0.
So I think these factors occur this exception.

Thx! Mr. Juan
I think there's a problem with sending message,
I tried to another test, 'StorageCrossPlatformTests.cs', but still same error.
In "ERC20_L1_to_L2_Deposit_and_Withdraw.cs"
var receiptDeposit = await gatewayService.DepositRequestAndWaitForReceiptAsync(new DepositFunction() { Amount = 1, Gas = 7000000 });
In "StorageCrossPlatformTests.cs"
var messageTransactionReceipt = await l2CrossDomainMessengerService.SendMessageRequestAndWaitForReceiptAsync(message);
After running that code lines, "watcher.GetMessagesHashes" can't catch sent messages.

Hi, Mr. Juan
Please consider the deploying smart contracts to Layer2.
I tried to deploy ERC20 Contracts to Layer2 with hardhat, and used testchain (localhost:8545), but also there seems be random number of tokens<PHONE_NUMBER>859429580717715935127017118905506969531736240423467206075712395313....
So I am just curious that the Layer 2 is all right?

Hi, Mr.Juan
Hope you are doing well.
Please inform me if there's any update.
It's really necessary for me and for all nethereum fans.

Hi, Juan
Any updates?

@kevinlai219 updated now have a look

Thanks Juan.
Thanks for your effort.
I will have a look on it right now.

Test it on Kovan, most contracts have changed, so it is much easier to get started now.

Hi, Juan
I have tested new code you pushed, and it works very good.
Thanks.
Kevin


[stable/prometheus-operator] Clarify serviceMonitorNamespaceSelector

@zytek You will need to increase the chart version in order for the tests to pass


String primary key with default auto_incrementing breaks app.

Description
When using String as primary key "Execution Error: Failed to find inserted item" appears.
Steps to Reproduce
Entity model:
use sea_orm::prelude::*;
use serde::{Deserialize, Serialize};

#[derive(Clone, Debug, PartialEq, DeriveEntityModel, Deserialize, Serialize)]
#[sea_orm(table_name = "clients")]
pub struct Model {
    #[sea_orm(primary_key)]
    pub id: String,
    pub name: String,
    pub surname: String,
    pub nip_prefix: i32,
    pub nip: String,
    pub state: String,
    pub postcode: String,
    pub locality: String,
    pub street: String,
    pub house_nb: i32,
}

#[derive(Copy, Clone, Debug, EnumIter, DeriveRelation)]
pub enum Relation {}

impl ActiveModelBehavior for ActiveModel {}

actix web function:
	pub async fn add(pool: Data<DatabaseConnection>, json: Json<client::Model>) -> HttpResponse {
		let pool = pool.as_ref();

		let json: client::ActiveModel = json.0.into();

		let res = json.insert(pool).await;

		if let Err(err) = res {
			println!("{err}");
			HttpResponse::InternalServerError().body(err.to_string())
		} else {
			HttpResponse::Ok().finish()
		}
	}

Expected Behavior
If 'json' model is correct it should be inserted to db and 'res' should not return Err.
Actual Behavior
Wild "Execution Error: Failed to find inserted item" appears when 'json' model is correct.
More interestingly item is correctly inserted into database.
Problem is with retrieving the inserted item.
Reproduces How Often
always
Versions
├── sea-orm v0.6.0
│ ├── sea-orm-macros v0.6.0 (proc-macro)
│ ├── sea-query v0.21.0
│ │ ├── sea-query-derive v0.2.0 (proc-macro)
│ ├── sea-strum v0.23.0
│ │ └── sea-strum_macros v0.23.0 (proc-macro)
Mysql + Windows
Additional Information
Problem disappears when disabling auto_increment:
pub struct Model {
	#[sea_orm(primary_key, auto_increment = false)]
	pub id: String,
	pub name: String,
	pub surname: String,
	pub nip_prefix: i32,
	pub nip: String,
	pub state: String,
	pub postcode: String,
	pub locality: String,
	pub street: String,
	pub house_nb: i32,
}

Sorry for my poor english.

Hey @xodix, welcome! I wonder why the id column is of Strong type?

And, is the id column an auto generated column?

Some primary keys are meant to be representation of ID codes found in an ID card or a passport ID.

And, is the id column an auto generated column?

I am working with an existing database not generated by SeaORM.

Ok, the id column does not auto increment on its own. So, it normal to specify #[sea_orm(auto_increment = false)] on the Model.


Radare2 with Ghidra

Radare2 allows using Ghidra as a decompiler: https://github.com/radareorg/r2ghidra-dec. But it's impossible to install it via r2pm in NixOS.
It would be nice to have a package that contains r2 together with Ghidra.
@Mic92

But it's impossible to install it via r2pm in NixOS.

Why? What is the error?

CMake Error: CMake was unable to find a build program corresponding to "Unix Makefiles".  CMAKE_MAKE_PROGRAM is not set.  You probably need to select a different build tool.
CMake Error: CMAKE_C_COMPILER not set, after EnableLanguage
CMake Error: CMAKE_CXX_COMPILER not set, after EnableLanguage
-- Configuring incomplete, errors occurred!

All right, maybe it's possible to install with nix-shell. But it's inconvenient and breakage-prone.

I have not looked into r2pm and nix yet. As you already found out it might be possible to compile it for now using nix-shell -p cmake.

It partially compiles with nix-shell -p cmake bison flex and then errors with no meaningful error message.

Creating a proper nixpkgs requires some patching though:
$ r2 -H R2_LIBR_PLUGINS
/nix/store/fgiv9xh85yj26vyq4f8lp51fnbm6a7n0-radare2-4.3.1/lib/radare2/4.3.1
$ r2 -H R2_USER_PLUGINS
/home/joerg/.local/share/radare2/plugins

Ideally radare2 would accept environment variables to load plugins from.

I tried this one:
$ git clone https://github.com/radareorg/r2ghidra-dec
$ cd r2ghidra-dec
$ git submodule update --init
$ cat > shell.nix <<EOF
with import <nixpkgs> {};
stdenv.mkDerivation {
  name = "env";
  buildInputs = [
    radare2
  ];
  nativeBuildInputs = [
    cmake bison flex
    pkgconfig
  ];
}
EOF
$ nix-shell
$ mkdir build
$ cd build
$ cmake ..
$ make -j$(nproc)

It still does not compile. I assume the radare2 version in our repos is too old:
/home/joerg/git/r2ghidra-dec/src/R2TypeFactory.cpp: In member function ‘Datatype* R2TypeFactory::queryR2(const string&, std::set<std::__cxx11::basic_string<char> >&)’:
/home/joerg/git/r2ghidra-dec/src/R2TypeFactory.cpp:157:8: error: ‘R_TYPE_TYPEDEF’ was not declared in this scope
  157 |   case R_TYPE_TYPEDEF:
      |        ^~~~~~~~~~~~~~
/home/joerg/git/r2ghidra-dec/src/R2Scope.cpp: In member function ‘virtual bool R2Scope::isNameUsed(const string&) const’:
/home/joerg/git/r2ghidra-dec/src/R2Scope.cpp:590:6: error: ‘r_anal_get_function_byname’ was not declared in this scope; did you mean ‘r_anal_get_function_at’?
  590 |  if (r_anal_get_function_byname(core->anal, name.c_str()))
      |      ^~~~~~~~~~~~~~~~~~~~~~~~~~
      |      r_anal_get_function_at
make[2]: *** [CMakeFiles/core_ghidra.dir/build.make:132: CMakeFiles/core_ghidra.dir/src/R2TypeFactory.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: *** [CMakeFiles/core_ghidra.dir/build.make:119: CMakeFiles/core_ghidra.dir/src/R2Scope.cpp.o] Error 1
make[2]: Leaving directory '/home/joerg/git/r2ghidra-dec/build'
make[1]: *** [CMakeFiles/Makefile2:145: CMakeFiles/core_ghidra.dir/all] Error 2
make[1]: Leaving directory '/home/joerg/git/r2ghidra-dec/build'
make: *** [Makefile:147: all] Error 2
make: Leaving directory '/home/joerg/git/r2ghidra-dec/build'

It compiles with https://github.com/NixOS/nixpkgs/pull/86458

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/radare2-plugins-in-nixpkgs/8485/1

I wrote a rizin with plugins nix wrapper that also packages rz-ghidra, it may be helpful to anyone trying to package r2ghidra
https://im.badat.dev/bad/rizin-nix-plugins

Ideally radare2 would accept environment variables to load plugins from.

radare2 already accepts R2_LIBR_PLUGINS but that is just one path
feature request for multiple paths in https://github.com/radareorg/radare2/issues/21300

This is my attempt at packaging this https://github.com/NixOS/nixpkgs/pull/220885

$ cat > shell.nix <<EOF
with import <nixpkgs> {};
stdenv.mkDerivation {
  name = "env";
  buildInputs = [
    radare2
  ];
  nativeBuildInputs = [
    cmake bison flex
    pkgconfig
  ];
}
EOF
$ nix-shell
$ r2pm -ci r2ghidra

worked for me (no other actions needed r2 can find the plugin and start decompiling)


F #4302: Change wild detecion method and fix resource pool names

Re-dded disk info to vm monitoring


Whether to increase the dimension of the metrics

What would you like to be added:
Dimension of the Kmesh‘s metrics.
Why is this needed:
The metrics for kmesh metrics at this stage are:

Name
Describe

kmesh_tcp_workload_connections_opened_total
The total number of TCP connections opened to a workload

kmesh_tcp_workload_connections_closed_total
The total number of TCP connections closed to a workload

kmesh_tcp_workload_received_bytes_total
The size of the total number of bytes received in response to a workload over a TCP connection

kmesh_tcp_workload_sent_bytes_total
The size of the total number of bytes sent in response to a workload over a TCP connection

kmesh_tcp_workload_conntections_failed_total
The total number of TCP connections failed to a workload

And the metrics that kmesh can get directly from the kernel are:
struct tcp_probe_info {
    __u32 type;
    struct bpf_sock_tuple tuple;
    __u32 sent_bytes;
    __u32 received_bytes;
    __u32 conn_success;
    __u32 direction;
    __u64 duration; // ns
    __u64 close_ns;
    __u32 state; /* tcp state */
    __u32 protocol;
    __u32 srtt_us; /* smoothed round trip time << 3 in usecs */
    __u32 rtt_min;
    __u32 mss_cache;     /* Cached effective mss, not including SACKS */
    __u32 total_retrans; /* Total retransmits for entire connection */
    __u32 segs_in;       /* RFC4898 tcpEStatsPerfSegsIn
                          * total number of segments in.
                          */
    __u32 segs_out;      /* RFC4898 tcpEStatsPerfSegsOut
                          * The total number of segments sent.
                          */
    __u32 lost_out;      /* Lost packets			*/
};

But these metrics are connection granularity metrics. Do we need to add these metrics?

I was thinking about support better loadbalancing based on rtt