Fixed Request Path for Windows OS

First a huge thanks for making terrific plugins for Jenkins, you are helping my team a lot :)
What this change does
I changed the way BlameRequest.fileName is set in case it received a filename with a path containing \ due to Jenkins running on Windows.  In case a Windows OS is detected, it will find an replace all \ by / so JGit can handle the BlameRequest.
Context

Jenkins with Analysis Core+DRY plugins installed running on Windows Server
DRY input: xml file generated by Simian
Noticed code duplicate author info was not displayed on  Duplicate Code Origin tab and when I checked the console output I saw the following:

<Git Blamer> No blame results for request <aaaa\bbbb.cpp - [258, 2307, 2563, 260]>

After a bit of trial and error(tried editing file path in the simian xml files, didn't work) I concluded JGit API couldn't handle path with backslashes, which led me to change how BlameRequest.filename is set in analysis-core and it worked! :)

This is my first pull request on github.com (I mainly use github enterprise...) and I haven't coded in Java almost 10 years, so any advice would be greatly appreciated and please let me know if you have any questions,
Matthieu Parizy

Hmm, that is really strange. Actually the filename should not contain backslash at all: AbstractAnnotation
Can you please have a look into the dry.xml file in your build folder and check the filenames there?

Seems that AbstractBlamer does not handle file names correctly as well.

Ah thank you for the prompt feedback and the pointer to the setFileName( )definition, I forgot to check it out. I am away from my office and lack the environment to check my dry.xml at home, but as you can see in my PR, I double escaped backslash:
this.fileName = fileName.replaceAll("\\\\", "/");

To my understanding, since backslash is both the escape character in Java and in regex, it has to be double escaped for it to be matched.
Tomorrow(in 12 hours), I'll try reverting my change, modifying AbstractAnnotation instead to the line below and I'll report on how it goes:
this.fileName = TreeString.of(StringUtils.strip(fileName).replace('\\\\', '/'));

Not in this case, replace uses a character so replace('\\', '/') should work quite well. (IssueTest is a test of the upcoming successor of analysis-core/warnings plugin, it shows that this is working as expected.
I think the actual problem is the code in AbstractBlamer that uses canonical name on the filename which results in different results if called on Windows.
I think your fix works but will still not get the rest of the code in AbstractBlamer correctly, see mailing list thread.

replace uses a character so replace('\', '/') should work quite well

ah indeed, it does work and is faster than using regex.
Thanks to your feedback and a bit more trial and error, I noticed that:

although extractConflictingFiles(final Set annotations)  , which is the method that sets Blame Requets file names, takes annotations as input
the relativeFileName given to BlameRequest uses getCanonicalPath to get the fileName instead of the given annotations
but the problem is getCanonicalPath uses java.io.file which gives a path with backslashes
the commit I pushed removes backslashes from getCanonicalPath and also fixes my problem.

I will now investigate why annotation.getPrimaryLineNumber() > 0 is false and thus prevent annotations from being used to set Blame Requests file names.

I noticed getWorkspacePath() was taking care of replacing backslashes before calling the problematic getCanonicalPath(), which was not, so  I removed the backslash replacing part from  getWorkspacePath()
it now done in getCanonicalPath().

Thanks for fixing this bug. (Normally I do not accept PRs without test case but in your case you are fine since the author of the blamer missed the test cases for the whole class. Hopefully, I find some time in the future to fix this...)

Glad I could be of help and thanks again for being so prompt!


incrementFlux loop causing performance issues

fluxnetworks-1.12.2-3.0.19-21

Fixed In Dev: The new version will have large performance improvements in this area. Thanks to @BloCamLimb


skybox: add christmas mode toggle for when in PoH. #14120

Adds a toggle in the skybox plugin to change the color whilst in a PoH to white.
Requested in #14120

Is there no way to detect whether you're in a Christmas-themed POH?

Is there no way to detect whether you're in a Christmas-themed POH?

Oh wow, I didn't even realize that Christmas-themed PoHs were a thing. I'll do that now!

This change should be made in skybox.txt, not in code.

Do you think the toggle button should be removed too? I just made another commit before seeing your reply. I'll change it now.

Yes. The only change this PR should include is the skybox definition update.

Yes. The only change this PR should include is the skybox definition update.

All done now!


chore: Update to CP4S 1.10.19

contributes-to: #271
Description of changes:

Updated CP4SThreatManagement to V2

Output of argocd app list command or screenshot of the Argo CD Application synchronization window showing successful application of changes in this branch.
argocd app list
NAME                                  CLUSTER                         NAMESPACE         PROJECT               STATUS  HEALTH   SYNCPOLICY  CONDITIONS  REPO                                    PATH                                  TARGET
openshift-gitops/argo-app             https://kubernetes.default.svc  openshift-gitops  argocd-control-plane  Synced  Healthy  Auto-Prune  <none>      https://github.com/IBM/cloudpak-gitops  config/argocd                         271-cp4s-v2
openshift-gitops/cp-shared-app        https://kubernetes.default.svc  ibm-cloudpaks     default               Synced  Healthy  Auto-Prune  <none>      https://github.com/IBM/cloudpak-gitops  config/argocd-cloudpaks/cp-shared     271-cp4s-v2
openshift-gitops/cp-shared-operators  https://kubernetes.default.svc  ibm-cloudpaks     default               Synced  Healthy  Auto-Prune  <none>      https://github.com/IBM/cloudpak-gitops  config/cloudpaks/cp-shared/operators  271-cp4s-v2
openshift-gitops/cp4s-all             https://kubernetes.default.svc  cp4s              default               Synced  Healthy  Auto-Prune  <none>      https://github.com/IBM/cloudpak-gitops  config/cloudpaks/cp4s                 271-cp4s-v2
openshift-gitops/cp4s-app             https://kubernetes.default.svc  openshift-gitops  default               Synced  Healthy  Auto-Prune  <none>      https://github.com/IBM/cloudpak-gitops  config/argocd-cloudpaks/cp4s          271-cp4s-v2

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


Incorrect data-dfn-for values in CSS Values 4

Latest Editor's Draft of CSS Values 4 has weird data-dfn-for (and ID) attributes whose values start with <fake-production-placeholder ..., for instance:
data-dfn-for="<fake-production-placeholder class=production bs-autolink-syntax='<<request-url-modifier>>' data-opaque>request-url-modifier</fake-production-placeholder>"

https://drafts.csswg.org/css-values-4/#typedef-fake-production-placeholder-classproduction-bs-autolink-syntaxrequest-url-modifier-data-opaquerequest-url-modifier-fake-production-placeholder-referrerpolicy-modifier
I haven't investigated but that seems to be generated by Bikeshed.

This is being caused by Bikeshed, yes, but it's also a markup error. (I'm right this moment working on parsing changes that will incidentally fix this, but the value would still be wrong.) I'll fix, one sec.

And fixed. (Give it a sec for generation.)


[No QA] Create StagingDeployCash utilities

@AndrewGable will you please review this?
We'll also need to create utilities to update existing StagingDeployCash issues, but I think this PR is big enough as-is and we can create the update function in a follow-up.
Fixed Issues
$ https://github.com/Expensify/Expensify/issues/155336
Tests
Automated unit tests created to cover these changes.
QA
No QA.

@AndrewGable Ready for re-review


upgrade supertest to ^1.0.1

Just help to close the #444 in my way, upgrade the supertest version and make the test cases be green.
/cc @jonathanong

Thanks for merge @dead-horse :)


Should we mask the attention before applying the softmax?

In this line:
          attn_dist *= enc_padding_mask # apply mask
of this function:
def masked_attention(e):
    """Take softmax of e then apply enc_padding_mask and re-normalize"""
    attn_dist = nn_ops.softmax(e) # take softmax. shape (batch_size, attn_length)
    attn_dist *= enc_padding_mask # apply mask
    masked_sums = tf.reduce_sum(attn_dist, axis=1) # shape (batch_size)
    return attn_dist / tf.reshape(masked_sums, [-1, 1]) # re-normalize

you apply the mask after doing the softmax, then the probabilities would be summed up to less than 1. In my humble opinion, you it may be better to first mask the e and then do the softmax.
Does this make sense?
Best,
Lerner

It turns out that I am wrong.

If you check the result of e^0, you'll know the answer.

@eduOS I am wondering on the same question now. I have read the implementation of Bert, where they DO mask the energy(scores) before applying the softmax, actually they fill the places where corresponding to PAD with a large negative number ,say -100000, which lead to softmax result (e^(-10000)) on those places will be all 0. Personally I think this implementation makes more sense. Do you have any idea?


[FEATURE] Create SPDK gRPC service for instance manager

Is your feature request related to a problem? Please describe (👍 if you like this request)
Need a gRPC service to serve as a portal for the operations requested by the Longhorn manager on each node. It will also be responsible for managing the SPDK tgt process to serve all functions supported by SPDK JSON RPC calls from the control plane.
Describe the solution you'd like
Create a gRPC service, and call SPDK manager or similar for replica management, logical volume store management, etc. The code can be in longhorn-spdk-engine then used by instance manager.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
cc @longhorn/qa

https://docs.google.com/drawings/d/1RulA4_IP8ynjStOpZi5XE2qEsYnrPYppDIp1_YxblCA/edit?usp=sharing

This is a dev item instead, so no need to do any e2e testing.


Remove $COFFEELINT_CONFIG

Between configFinder being able to locate the config file in the project, and being able to locate configs in the user's home directory, and the --file parameters, I don't think there's any need for COFFEELINT_CONFIG any more.
This would be a breaking change and require releasing a 2.0.
Is there a compelling use case that I'm simply not seeing?

Having COFFEELINT_CONFIG as a fallback (when there is no project config) is useful, rather than polluting the $HOME directory with yet another config file, especially in this  case where it isn't even an invisible . one!


Fixed padding and close button bugs for chooser modal

Fixes #9053 and #9014.
Compensated the padding with margin. I tested it on different screen sizes, works well for me.
Made close button white.
After:

cherry picked into 4.0 ef9cc8537ca68346d98e710fca0fd62541bc07ee

@PaarthAgarwal  thanks for digging into this one quickly - really appreciate it.


add a new blog：Efficient LLM Deployment and Serving

Thank you very much for your contribution, but I will not merge this PR, thank you.

@zhyncs Could you reopen this PR?


Support for PHP8

Description
I am using PHP 8 and wish to use this package, however only PHP 7.2 is supported.
Motivation and context
Why is this change required? What problem does it solve?
Support for PHP 8.
If it fixes an open issue, please link to the issue here (if you write fixes #num
or closes #num, the issue will be automatically closed when the pull is accepted.)
How has this been tested?
Please describe in detail how you tested your changes.
Include details of your testing environment, and the tests you ran to
see how your change affects other areas of the code, etc.
Screenshots (if appropriate)
Types of changes
What types of changes does your code introduce? Put an x in all the boxes that apply:

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:
Go over all the following points, and put an x in all the boxes that apply.
Please, please, please, don't send your pull request until all of the boxes are ticked. Once your pull request is created, it will trigger a build on our continuous integration server to make sure your tests and code style pass.

[ ] I have read the CONTRIBUTING document.
[ ] My pull request addresses exactly one patch/feature.
[ ] I have created a branch for this patch/feature.
[ ] Each individual commit in the pull request is meaningful.
[ ] I have added tests to cover my changes.
[ ] If my change requires a change to the documentation, I have updated it accordingly.

If you're unsure about any of these, don't hesitate to ask. We're here to help!

Duplicate of #28


[Request] Added some color to topic list make it easier to read.

Add color to +score, -score, no of reply to make topic easier to read.
Preview:

Please pull the master branch and fix the conflict in order to merging this PR, thanks!

Done. Please check 😆


Update nginx to version 1.19

This is a feature-parity pull request whose only purpose is to update nginx to the current version 1.19. All of my evidence so far is that this is a clean update with no feature changes or problems.

Pull Request Checklist:

[ ] Positive Test Case Written by Dev

[ ] Automated Testing

[ ] Sufficient User and Developer Documentation

[ ] Passing Jenkins Build

[ ] Peer Code review and approval

Positive Test Case

[Enter positive test case here]
Nothing changes at all!

@sblack-usu @cbcunc This is the first in a sequence of PRs intended to enable large file upload. Many of these are very small PRs with very broad potential impact. For example, this particular PR touches basically everything in the UI by modifying the underlying web server! I wish to have @ndebuhr validate each one for problems to be sure before going to the next step.

@sblack-usu @cbcunc This is the first in a sequence of PRs intended to enable large file upload. Many of these are very small PRs with very broad potential impact. For example, this particular PR touches basically everything in the UI by modifying the underlying web server! I wish to have @ndebuhr validate each one for problems to be sure before going to the next step.

METRIC
VALUE

NEW BUGS
0

NEW CODE SMELLS
0

NEW SECURITY HOTSPOTS
0

NEW VULNERABILITIES
0

NEW DUPLICATED LINES DENSITY
0.0

https://sonarqube.cuahsi-workstation.com:9000/dashboard?id=hydroshare-4113

METRIC
VALUE

NEW BUGS
0

NEW CODE SMELLS
0

NEW SECURITY HOTSPOTS
0

NEW VULNERABILITIES
0

NEW DUPLICATED LINES DENSITY
0.0

https://sonarqube.cuahsi-workstation.com:9000/dashboard?id=hydroshare-4113


Rails 7 - uninitialized constant Impressionist::Engine::ImpressionistController (NameError)

After upgrading to rails 7 I'm getting the below error with the impressionist gem. When I start my local server.
uninitialized constant Impressionist::Engine::ImpressionistController (NameError)
ruby 3.0.2
rails 7.0.1
gem "impressionist", git: "https://github.com/charlotte-ruby/impressionist
This is the full stack after installing with bundler and running rails g impressionist:
/Users/rodi/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/impressionist-2.0.0/lib/impressionist/engine.rb:15:in `block (2 levels) in <class:Engine>': uninitialized constant Impressionist::Engine::ImpressionistController (NameError)
	from /Users/rodi/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activesupport-7.0.1/lib/active_support/lazy_load_hooks.rb:71:in `class_eval'
	from /Users/rodi/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activesupport-7.0.1/lib/active_support/lazy_load_hooks.rb:71:in `block in execute_hook'
	from /Users/rodi/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activesupport-7.0.1/lib/active_support/lazy_load_hooks.rb:61:in `with_execution_control'
	from /Users/rodi/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activesupport-7.0.1/lib/active_support/lazy_load_hooks.rb:66:in `execute_hook'
	from /Users/rodi/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activesupport-7.0.1/lib/active_support/lazy_load_hooks.rb:43:in `block in on_load'
	from /Users/rodi/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activesupport-7.0.1/lib/active_support/lazy_load_hooks.rb:42:in `each'
	from /Users/rodi/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/activesupport-7.0.1/lib/active_support/lazy_load_hooks.rb:42:in `on_load'
	from /Users/rodi/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/impressionist-2.0.0/lib/impressionist/engine.rb:14:in `block in <class:Engine>'
	from /Users/rodi/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/railties-7.0.1/lib/rails/initializable.rb:32:in `instance_exec'
	from /Users/rodi/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/railties-7.0.1/lib/rails/initializable.rb:32:in `run'
	from /Users/rodi/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/railties-7.0.1/lib/rails/initializable.rb:61:in `block in run_initializers'
	from /Users/rodi/.rbenv/versions/3.0.2/lib/ruby/3.0.0/tsort.rb:228:in `block in tsort_each'
	from /Users/rodi/.rbenv/versions/3.0.2/lib/ruby/3.0.0/tsort.rb:350:in `block (2 levels) in each_strongly_connected_component'
	from /Users/rodi/.rbenv/versions/3.0.2/lib/ruby/3.0.0/tsort.rb:431:in `each_strongly_connected_component_from'
	from /Users/rodi/.rbenv/versions/3.0.2/lib/ruby/3.0.0/tsort.rb:349:in `block in each_strongly_connected_component'
	from /Users/rodi/.rbenv/versions/3.0.2/lib/ruby/3.0.0/tsort.rb:347:in `each'
	from /Users/rodi/.rbenv/versions/3.0.2/lib/ruby/3.0.0/tsort.rb:347:in `call'
	from /Users/rodi/.rbenv/versions/3.0.2/lib/ruby/3.0.0/tsort.rb:347:in `each_strongly_connected_component'
	from /Users/rodi/.rbenv/versions/3.0.2/lib/ruby/3.0.0/tsort.rb:226:in `tsort_each'
	from /Users/rodi/.rbenv/versions/3.0.2/lib/ruby/3.0.0/tsort.rb:205:in `tsort_each'
	from /Users/rodi/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/railties-7.0.1/lib/rails/initializable.rb:60:in `run_initializers'
	from /Users/rodi/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/railties-7.0.1/lib/rails/application.rb:372:in `initialize!'
	from /Users/rodi/workspace/projects/tailwind_awesome/config/environment.rb:5:in `<main>'
	from /Users/rodi/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/bootsnap-1.9.4/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:23:in `require'
	from /Users/rodi/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/bootsnap-1.9.4/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:23:in `block in require_with_bootsnap_lfi'
	from /Users/rodi/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/bootsnap-1.9.4/lib/bootsnap/load_path_cache/loaded_features_index.rb:88:in `register'
	from /Users/rodi/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/bootsnap-1.9.4/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:22:in `require_with_bootsnap_lfi'
	from /Users/rodi/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/bootsnap-1.9.4/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:31:in `require'
	from /Users/rodi/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/zeitwerk-2.5.3/lib/zeitwerk/kernel.rb:35:in `require'
	from /Users/rodi/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/railties-7.0.1/lib/rails/application.rb:348:in `require_environment!'
	from /Users/rodi/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/railties-7.0.1/lib/rails/command/actions.rb:28:in `require_environment!'
	from /Users/rodi/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/railties-7.0.1/lib/rails/command/actions.rb:15:in `require_application_and_environment!'
	from /Users/rodi/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/railties-7.0.1/lib/rails/commands/generate/generate_command.rb:21:in `perform'
	from /Users/rodi/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/thor-1.2.1/lib/thor/command.rb:27:in `run'
	from /Users/rodi/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/thor-1.2.1/lib/thor/invocation.rb:127:in `invoke_command'
	from /Users/rodi/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/thor-1.2.1/lib/thor.rb:392:in `dispatch'
	from /Users/rodi/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/railties-7.0.1/lib/rails/command/base.rb:87:in `perform'
	from /Users/rodi/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/railties-7.0.1/lib/rails/command.rb:48:in `invoke'
	from /Users/rodi/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/railties-7.0.1/lib/rails/commands.rb:18:in `<main>'
	from /Users/rodi/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/bootsnap-1.9.4/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:23:in `require'
	from /Users/rodi/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/bootsnap-1.9.4/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:23:in `block in require_with_bootsnap_lfi'
	from /Users/rodi/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/bootsnap-1.9.4/lib/bootsnap/load_path_cache/loaded_features_index.rb:105:in `register'
	from /Users/rodi/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/bootsnap-1.9.4/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:22:in `require_with_bootsnap_lfi'
	from /Users/rodi/.rbenv/versions/3.0.2/lib/ruby/gems/3.0.0/gems/bootsnap-1.9.4/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:31:in `require'
	from bin/rails:4:in `<main>'

Facing the same issue with my existing app after an upgrade to rails 7 and ruby 3.0.1
/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/bundler/gems/impressionist-e0db056a2ac0/lib/impressionist/engine.rb:15:in block (2 levels) in <class:Engine>': uninitialized constant Impressionist::Engine::ImpressionistController (NameError) 	from /Users/charliewiredu/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/activesupport-7.0.1/lib/active_support/lazy_load_hooks.rb:71:in class_eval'
from /Users/charliewiredu/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/activesupport-7.0.1/lib/active_support/lazy_load_hooks.rb:71:in block in execute_hook' 	from /Users/charliewiredu/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/activesupport-7.0.1/lib/active_support/lazy_load_hooks.rb:61:in with_execution_control'
from /Users/charliewiredu/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/activesupport-7.0.1/lib/active_support/lazy_load_hooks.rb:66:in execute_hook' 	from /Users/charliewiredu/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/activesupport-7.0.1/lib/active_support/lazy_load_hooks.rb:43:in block in on_load'
from /Users/charliewiredu/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/activesupport-7.0.1/lib/active_support/lazy_load_hooks.rb:42:in each' 	from /Users/charliewiredu/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/activesupport-7.0.1/lib/active_support/lazy_load_hooks.rb:42:in on_load'
from /Users/charliewiredu/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/bundler/gems/impressionist-e0db056a2ac0/lib/impressionist/engine.rb:14:in block in <class:Engine>' 	from /Users/charliewiredu/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/railties-7.0.1/lib/rails/initializable.rb:32:in instance_exec'
from /Users/charliewiredu/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/railties-7.0.1/lib/rails/initializable.rb:32:in run' 	from /Users/charliewiredu/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/railties-7.0.1/lib/rails/initializable.rb:61:in block in run_initializers'
from /Users/charliewiredu/.rbenv/versions/3.0.3/lib/ruby/3.0.0/tsort.rb:228:in block in tsort_each' 	from /Users/charliewiredu/.rbenv/versions/3.0.3/lib/ruby/3.0.0/tsort.rb:350:in block (2 levels) in each_strongly_connected_component'
from /Users/charliewiredu/.rbenv/versions/3.0.3/lib/ruby/3.0.0/tsort.rb:431:in each_strongly_connected_component_from' 	from /Users/charliewiredu/.rbenv/versions/3.0.3/lib/ruby/3.0.0/tsort.rb:349:in block in each_strongly_connected_component'
from /Users/charliewiredu/.rbenv/versions/3.0.3/lib/ruby/3.0.0/tsort.rb:347:in each' 	from /Users/charliewiredu/.rbenv/versions/3.0.3/lib/ruby/3.0.0/tsort.rb:347:in call'
from /Users/charliewiredu/.rbenv/versions/3.0.3/lib/ruby/3.0.0/tsort.rb:347:in each_strongly_connected_component' 	from /Users/charliewiredu/.rbenv/versions/3.0.3/lib/ruby/3.0.0/tsort.rb:226:in tsort_each'
from /Users/charliewiredu/.rbenv/versions/3.0.3/lib/ruby/3.0.0/tsort.rb:205:in tsort_each' 	from /Users/charliewiredu/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/railties-7.0.1/lib/rails/initializable.rb:60:in run_initializers'
from /Users/charliewiredu/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/railties-7.0.1/lib/rails/application.rb:372:in initialize!' 	from /Users/charliewiredu/Dev/uppro/config/environment.rb:5:in '
from /Users/charliewiredu/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/bootsnap-1.10.2/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in require' 	from /Users/charliewiredu/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/bootsnap-1.10.2/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in require'
from /Users/charliewiredu/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/zeitwerk-2.5.4/lib/zeitwerk/kernel.rb:35:in require' 	from /Users/charliewiredu/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/bootsnap-1.10.2/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:42:in require_relative'
from config.ru:3:in block in <main>' 	from /Users/charliewiredu/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/rack-2.2.3/lib/rack/builder.rb:116:in eval'
from /Users/charliewiredu/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/rack-2.2.3/lib/rack/builder.rb:116:in new_from_string' 	from /Users/charliewiredu/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/rack-2.2.3/lib/rack/builder.rb:105:in load_file'
from /Users/charliewiredu/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/rack-2.2.3/lib/rack/builder.rb:66:in parse_file' 	from /Users/charliewiredu/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/rack-2.2.3/lib/rack/server.rb:349:in build_app_and_options_from_config'
from /Users/charliewiredu/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/rack-2.2.3/lib/rack/server.rb:249:in app' 	from /Users/charliewiredu/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/rack-2.2.3/lib/rack/server.rb:422:in wrapped_app'
from /Users/charliewiredu/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/railties-7.0.1/lib/rails/commands/server/server_command.rb:76:in log_to_stdout' 	from /Users/charliewiredu/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/railties-7.0.1/lib/rails/commands/server/server_command.rb:36:in start'
from /Users/charliewiredu/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/railties-7.0.1/lib/rails/commands/server/server_command.rb:143:in block in perform' 	from <internal:kernel>:90:in tap'
from /Users/charliewiredu/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/railties-7.0.1/lib/rails/commands/server/server_command.rb:134:in perform' 	from /Users/charliewiredu/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/thor-1.2.1/lib/thor/command.rb:27:in run'
from /Users/charliewiredu/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/thor-1.2.1/lib/thor/invocation.rb:127:in invoke_command' 	from /Users/charliewiredu/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/thor-1.2.1/lib/thor.rb:392:in dispatch'
from /Users/charliewiredu/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/railties-7.0.1/lib/rails/command/base.rb:87:in perform' 	from /Users/charliewiredu/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/railties-7.0.1/lib/rails/command.rb:48:in invoke'
from /Users/charliewiredu/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/railties-7.0.1/lib/rails/commands.rb:18:in <main>' 	from /Users/charliewiredu/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/bootsnap-1.10.2/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in require'
from /Users/charliewiredu/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/bootsnap-1.10.2/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in require' 	from bin/rails:4:in '

Same as above

found temporary solution:
impressionist_dir = Gem::Specification.find_by_name('impressionist').gem_dir
require File.join(impressionist_dir, '/app/controllers/impressionist_controller.rb')

Enjoy :)


[front] Issue when selecting a channel to join

With wrong default value set in the choice list, there is issue when selecting a value that is the default value, or something like that. It's quite particular as an issue. Sorry if I don't explain it well haha. It need a bit of testing to figure out exactly the source of the issue.

I found the bug:

have no channel in public
with 2 accounts, one on try to join and other to try to create
see no channel exists
create a channel with the account "try to create" in public (without password, it is esaier to test)
on account "try to join" see the new channel
try to join -> bug


feat: Introduce .kraftignore

Prerequisite checklist

[x] Read the contribution guidelines regarding submitting new changes to the project;
[x] Tested your changes against relevant architectures and platforms;
[x] Ran make fmt on your commit series before opening this PR;
[ ] Updated relevant documentation.

Description of changes
This PR fixes https://github.com/unikraft/kraftkit/issues/135
Specifying contents (file or directory paths) in .kraftignore file in the working directory forces Kraftkit to ignore matching children files or directories sharing from the sharing directory as rootfs.
For now, .kraftignore only work when rootfs is specified for a directory path.
Rules for .kraftignore:

Line starts with a # will be ignored by Kraftkit.

Every blank line will be ignored by Kraftkit.

Directory or File path that contains glob-patterns (characters like *, !, [ and ?) will be ignored by Kraftkit and return a warning message.

One needs to specify the entire relative path (relative path to the sharing directory e.g. if rootfs=share/ and share directory contains sample.txtand sample/, So relative path in .kraftignore file can be defined as /sample.txt, sample.txt and ./sample.txt for share/sample.txt to ignore) of the file or directory that have to be ignored.

Various directory and file paths can be specified in a .kraftignore file using space separator or new line e.g.
random1/random01/random01.txt /random.txt

random1/random01

All the specified paths in .kraftignore will be relative to the root of sharing directory, means if share/ directory contains sample.txt and sample/, and set as rootfs to kraftkit then to ignore /share/sample.txt only sample.txt needs to be defined in kraftignore.
Note: All the paths can start with ./ or / (Since prefix / and ./ with paths simply ignored by Kraftkit).

I think we also need to document this somewhere otherwise it will be lost
@nderjung do you have a use case in mind? maybe an app which would currently benefit from .kraftignore?

One more thing: does it support using "" or '' characters? I was thinking about the case of "./nginx/strange test.txt"

Hey @MdSahil-oss found 1 small bug but otherwise it seems to work:
test.txt <-- works (ignored)

# test1.txt <-- works (not ignored)

nginx/test3.txt    #       test2.txt  <-- works (both ignored, basically # was ignored)

test.txt <-- works (nothing changed)

# test.txt <-- works (nothing changed)

./nginx <-- works (ignored)

./nginx/* <-- works (prints warning)

.///////////////////nginx <-- fails (multiple slashes are usually ignored)
./nginx/../test1.txt <-- fails (I think .. is not understood)
././././././././././././test1.txt <-- fails (I think . is not understood)

Nice catch @craciunoiuc, I will work on your suggestions

One more thing: does it support using "" or '' characters? I was thinking about the case of "./nginx/strange test.txt"

Don't think so, I will update this PE for these characters.

what is the state on this @MdSahil-oss @nderjung
I think it was almost ready to go out?


Doesn't work on Chrome

Hello,
I am not an expert but in Chrome it seems that it doesn't work on Chrome.
On my computer it shows  + and - signs on the left and right of the input box instead of the spin up and down.
Anyone is having the same issue?
works fine with Edge and firefox.
Thanks

Hi

Make mobile attribute false in the component

Thanks for the reply.
To follow up
I have just looked at http://vlad-ignatov.github.io/react-numeric-input/examples/v2.0.5/index.html  with chrome and I have the same issue

and - are in the right and left instead of being a spin box with up and down arrow
I will reopen and issue with screenshot


Add support for the deprecated user field in login

https://gitlab.com/famedly/conduit/-/issues/379
That deserialisation error is actually from ruma because they're assuming the username will only exist in the identifier field. The let user_id field attempts to create a Password struct with the identifier field, but when it doesn't exist ruma fails to deserialise hence where the M_BAD_JSON error comes from (not from Conduit)
I'm not sure if this is a mistake or why they don't implement the deprecated field, but they would need to wrap UserIdentifier as an Option in the Password struct.
I have an idea on how I can implement it, but sticking a ton of logic inside a single variable assignment is making this annoying.

(Saving this for later https://github.com/girlbossceo/conduwuit/commit/9b1a9ce35ae30bc09bb5cfead884dee54d53cffa)

This was indeed Ruma not implementing it, hopefully I did it right: https://github.com/ruma/ruma/pull/1725

Implemented in https://github.com/girlbossceo/conduwuit/pull/165


AI bot for Docs TBC

https://www.notion.so/1-Deploy-an-AI-Bot-for-docs-f269023b80074c33a80f567099630c4e

Trial with https://www.kapa.ai/
we'll kick this off on Discord and the website (I expect the website integration to be minimal effort).


sess.run() with Keras model and TFRecord tensor based images

There isn't much documentation on how to run a keras model with image tensors loaded from a TFRecord, there is the keras as a simplified interface to tensorflow blog post, but it loads up all the images as a numpy array.
Since I already have TFRecords loaded from a function read_tfrecord_and_decode_into_image_annotation_pair_tensors() and tensors storing my images I don't think I need to go back to a feed dict. However, when I try to call sess.run, Keras expects a numpy array feed_dict for the keras.model.layers.Input() as I encountered in this error.
How do I use keras models with a keras.layers.Input() node, input tensor images, TFRecords, and queue runners together?
some of the key code lines:

        coord = tf.train.Coordinator()
        threads = tf.train.start_queue_runners(sess=sess,coord=coord)

        print('starting training...')

        # 10 epochs
        for i in xrange(11127 * number_of_epochs):

            cross_entropy, summary_string, _ = sess.run([ cross_entropy_sum,
                                                        merged_summary_op,
                                                        train_step ],
                                                        feed_dict={K.learning_phase(): 1})

            print("Current loss: " + str(cross_entropy))

            summary_string_writer.add_summary(summary_string, i)

            if i % 11127 == 0:
                save_path = saver.save(sess, FLAGS.save_dir + "model_fcn8s_epoch_" + str(i) + ".ckpt")
                print("Model saved in file: %s" % save_path)

I will update with more details once tf is reinstalled, though I don't think the error is key to these questions as it is primarily about Keras + TF integration.

I also created a stackoverflow question in case that's more appropriate:
http://stackoverflow.com/questions/42184863/tensorflow-session-run-tfrecord-keras-example

A first pass of this is in https://github.com/fchollet/keras/pull/6928, feedback + fixes would be appreciated!

I consider this issue resolved.


build_sysext: bugfixes, QoL changes, help updated

This change improves build_sysext by sourcing a missing lib dependency, adding a number of comfort / quality-of-life options, and updating the output of --help accordingly.
The OEM sysext finction in build_library/vm_image_util.sh is also updated to use new command line format.

Include missing dependency toolchain_util.sh to fix an error in board_options.sh when --board was not specified (get_board_arch undefined).
Use positional parameters for mandatory arguments. build_dir and sysext_name are mandatory and are now positional arguments instead of options. binary_package is the third positional argument but can be omitted if --metapkgs was specified.
--squashfs_base is now guessed better and will use the most recent build by default.
A new boolean flag --ignore_version_mismatch for the more daring developer was added. The flag will cause the script to continue if a version mismatch between SDK board packages and squashfs base is detected.
Error messages were improved for when mandatory parameters were not provided.
The --help message was improved and adjusted to the new parameters.

Tested with a custom sysext build and with a image_to_vm.sh qemu build (for testing the generic OEM sysext build).

can you also add -noappend to the mksquashfs invocation?

Fixed hard-coded architecture, added -noappend option to mksquashfs.

@krnowak @jepio One more round please:  --image_builddir is now guessed and defaults to a sysext sub-directory in the directory the squashfs base resides in. Everything else has been addressed.
This allows a user, after a build, to plainly run
./build_sysext python dev-lang/python

to build a python sysext for the OS image that was just built.


npm install fails with error: no template named 'remove_cv_t' in namespace 'std'; did you mean 'remove_cv'?

If you have this error like me,
First:
yarn add<EMAIL_ADDRESS>yarn add<EMAIL_ADDRESS>yarn install will work with these deps properly.
We need to fix the following line from
import sass from 'gulp-sass';
to
var sass = require('gulp-sass')(require('sass'));
in the following files: gulpfile.js

Hi there, the starter template uses gulp-sass v4 which uses the compiler property to set the sass compiler:
var sass = require('gulp-sass');
sass.compiler = require('sass');

If upgrading to v5 (as you did), you'll need to use the new syntax:
var sass = require('gulp-sass')(require('sass'));

We'll make sure to update the package and the gulpfile to this new version. Thanks!


feedback on using Apache OpenWhisk name

Recently, an opportunity arose to provide a virtual machine image as a one click deployment of OpenWhisk to appear in the market place for a cloud provider. I reviewed the trademark details (https://www.apache.org/foundation/marks/faq) and concluded that the name of the image can at best refer to OpenWhisk using the “Powered by” approach… which was too long for the formatting, so I opted for a different naming approach (that omits Apache OpenWhisk entirely in the name) and used the Powered by language in the detailed description (with links to our project page).
There are two parts to describing the image.
The first is a brief description (where XYZ below is a place holder name of the image) for which I intend to use the following:
XYZ provides you with a platform for building serverless applications, not just functions.
It is [Powered by Apache OpenWhisk](https://openwhisk.apache.org), an industry-strength
platform for serverless computing that can handle enterprise-level scaling...

The second is a longer set of instructions in which I links to our github docs and tutorials. At the end of the instructions, I will conclude with the following:
More information about Apache OpenWhisk is available on the project website at
https://openwhisk.apache.org. Apache OpenWhisk and OpenWhisk, are either
registered trademarks or trademarks of The Apache Software Foundation in the
United States and other countries. All other marks mentioned may be trademarks
or registered trademarks of their respective owners.

Inline with one of the early suggestions I received, I linked to https://openwhisk.apache.org instead of the shorter http://openwhisk.org in the spirit of promoting the Apache brand. (Plus it's https :)
With this issue, I'm soliciting additional feedback that can help promote Apache/OpenWhisk, and also document the text as an example for future use by others.

Thanks for this, looks good to me! Does your image have an URL that you can include here for reference?
I added the "compliance" label to this ticket, maybe "branding" would be good as well but I'm not sure about creating yet another label.

Here is the url https://marketplace.digitalocean.com/apps/nimbella-lite.
Thanks for the feedback here and on the dev list.


PHP 7 warning of Illegal string offset

Under PHP7, the warning:
Warning:  Illegal string offset 'message' in /.../vendor/stevenmaguire/oauth2-microsoft/src/Provider/Microsoft.php on line 58

is generated.
Changing (in protected function checkResponse(ResponseInterface $response, $data) )
 $data['error']['message'] ?: $response->getReasonPhrase(),

to:
 (isset($data['error']['message']) ? $data['error']['message'] : $response->getReasonPhrase()),

fixes this warning.

Great, thank you for catching that. I've made a code change and cut a new release tag. Version 0.2.1 is available now.


Apply Input Formatter at Action level?

I note from the docs that in order to use a custom formatter you have to apply it globally:
services.AddMvc(options =>
{
    options.InputFormatters.Insert(0, new VcardInputFormatter());
});

However I didn't notice any option to apply a Formatter for specific Action method/s can this be done?

Hi @dazinator. You can use the ProducesAttribute and ConsumesAttribute on action level, to enforce certain formatting. You an read more about formatting with those attributes here.

@mkArtakMSFT - Thanks - I found information on that page about the ProducesAttribute but nothing about the ConsumesAttribute. Should this be added to the docs?

ConsumesAttribute is covered under model binding: https://docs.microsoft.com/en-us/aspnet/core/mvc/models/model-binding#bind-formatted-data-from-the-request-body


Unable to create a web app using vs code aand azure extension.

Does this occur consistently?
Repro steps:

1.Tried craeting an app using the VS Code Azure extension but was greeted with this error.
Action: appService.CreateWebApp
Error type: Conflict
Error Message: Server Farm with name 'appsvc_linux_centralus' already exists for subscription '5588708f-9f99-4c4c-b379-cbb672ee4c81'.
I have deleted the any previous instances of 'appsvc_linux_centralus'.
Version: 0.20.0
OS: win32
OS Release: 10.0.18363
Product: Visual Studio Code
Product Version: 1.53.2
Language: en

Call Stack
new RestError extension.bundle.js:46:66146
extension.bundle.js:46:496611extension.bundle.js:46:496611
processTicksAndRejections task_queues.js:97:5

@MohdMaaz19 Weird, have you created a web app with the extension prior to getting this error?  Where did you delete appsvc_linux_centralus?  How long ago was it?  It might be some race condition where the app service plan is deleted, but not fully yet.
A workaround for now would be to use advanced create so that you can specify what app service plan to use.

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Allow apostrophe in entity names

It is currently not possible to use apostrophes in a glossary term's name (term is then invalid).
Lots of expressions in French use d' or l' and it is difficult not to use it in something that should reflect the business language.
Many thanks

adding @sureshms to the convo hear. Not sure if this should be something that can be achieved via a Display Name. In any case, I think there might be an issue on how the query gets run
An exception with message [java.sql.SQLSyntaxErrorException: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '.'))  WHERE fullyQualifiedName LIKE 'Balan GLOSS TEST.Demo term 2.another name.%'", arguments:{positional:{}, named:{}, finder:[]}]] was thrown while processing request.

@chirag-madlani and @ShaileshParmar11, I have removed ' from the regex that validates the name. However, we still should not allow ' for the Type name and Extension names. In fact, the regex pattern for the names there is "^[a-z][a-zA-Z0-9]+$ as defined in the JSON schema. Can you please make this change in the validation only for them?

@chirag-madlani and @ShaileshParmar11, I have removed ' from the regex that validates the name. Please review that change in this patch. However, we still should not allow ' for the Type name and Extension names. In fact, the regex pattern for the names there is "^[a-z][a-zA-Z0-9]+$ as defined in the JSON schema. Can you please make this change in the validation only for them?

Hi @sureshms, as I understood we should not allow ' for custom property name and type and we should validate the same with ^[a-z][a-zA-Z0-9]+$ this Regex pattern!

Hi @sureshms, as I understood we should not allow ' for custom property name and type and we should validate the same with ^[a-z][a-zA-Z0-9]+$ this Regex pattern!
@ShaileshParmar11 that is correct.


Generate optional getters for nullables only

This PR adds the ability to generate optional getters only for the nullable fields. The reasoning behind this change is that I would like to let users know whether the field is really optional or not.
At first I wanted to change the behaviour of the gettersReturnOptional option but this would be a big breaking change. So I decided to add an additional option that works in conjunction with the gettersReturnOptional.
If everything is ok with this PR, I would also like to backport this change to 1.9 branch if that is possible.

Closed in favor of #817


fix typo

@unional Hmmm... I'm more used to seeing "reference to".
It's not a formal survey, but I see these stats when searching stackoverflow.com:
"reference to"  352,609 results
"reference of"   35,780 results

I tend to strong associate "to" with pointers as well - "pointer to" instead of "pointer of".
Change my mind! :-)

I see.  :)
When I read Let's pass a reference to num to our function... it just look weird and have to stop and rethink what it means.
When I try Let's pass a reference of num to our function... then it clicks as (reference of num) can be substituted with the reference, i.e. Let's pass "the reference" to our function.
When using reference to num, it focus on the relationship, i.e. that is the reference to something, instead of emphasize on the reference itself.
It is relatively minor and maybe you can leave it as is. 🍻

@unional Oh, thank you! Yes, I see what you mean. Using "to" twice in Let's pass a reference to num to our function... is not good.  Let's find a way to re-word that sentence entirely to avoid the confusion!
How about we change:
    // Let's pass a reference to num to our function and print it:

by removing "to our function" entirely:
    // Let's pass a reference to num, then print the result:

What do you think?

How about even skip the latter part? It describes the next two lines, but what's really important is just the first line.
This is the same for the next comment.
i.e. update that section to:
    // Let's pass a reference to num:
    makeFive(&num);
    std.debug.print("num: {}, ", .{num});

    // Now something interesting. Let's pass a reference to a
    // specific array value:
    makeFive(&more_nums[2]);

    // [also remove this comment, doesn't add anything to the exercise (pass by reference)]
    std.debug.print("more_nums: ", .{});
    for (more_nums) |n| {
        std.debug.print("{} ", .{n});
    }

🍺

How about we change:
...
by removing "to our function" entirely:
    // Let's pass a reference to num, then print the result:

My suggestion would be:
Let's pass the num reference to our function and print it: