[ARM] az group deployment create: Fix "stat: path too long for Windows" error when using large parameters.json file (#11646)

Fix issue: #11646
When the prefix of the --paramters parameter passed in is @, the JSON data will be loaded according to the file name in advance.
Later in the process, os.path.isfile() is called to determine whether the JSON data is a file name.
When the length of the JSON data is too long, os.stat() will have an error of "stat: path too long for Windows" (belonging to ValueError).
In Python 3.8, the ValueError would be caught, whereas in versions before 3.6, it will make a direct error.
So add the logic to catch ValueError in order to compatible with the older versions of Python.
History Notes:
(Fill in the following template if multiple notes are needed, otherwise PR title will be used for history note.)
[Component Name 1] (BREAKING CHANGE:) (az command:) make some customer-facing change.
[Component Name 2] (BREAKING CHANGE:) (az command:) make some customer-facing change.

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

A small question here is that "path too long" is caused by file name or file content size?

A small question here is that "path too long" is caused by file name or file content size?

@Juliehzl The prefix of the filename contains @ and the contents of the file are too large will cause this problem.

A small question here is that "path too long" is caused by file name or file content size?

@Juliehzl The prefix of the filename contains @ and the contents of the file are too large will cause this problem.

What about no @ in parameter value? From my previous understanding, @ is just used to help find file path in some scenario. And eventually they will call the same load file function. So I think it should also have the same error although there is no @ in parameter value. Is it right?

What about no @ in parameter value? From my previous understanding, @ is just used to help find file path in some scenario. And eventually they will call the same load file function. So I think it should also have the same error although there is no @ in parameter value. Is it right?

@Juliehzl There is no problem if the prefix of the parameter does not contain @, because when os.path.isfile(value) is called in _process_parameters(), the value is a filename.
But when the parameter prefix is @, the contents of the file are loaded ahead of time by _pre_command_table_create(). Then in the _process_parameters() process, os.path.isfile(value) is used to determine if the value is a filename, at which point the value has become the contents of the file.


[WIP] MSMR model

Description
Implements the MSMR model from Baker & Verbrugge, 2018.
In particular, this PR adds a new "particle" model that solves for the potential within the particles. Then OCP is then this potential evaluated at the surface. In order to use this model, users must write down the OCV for each reaction (in the form of Eq 3), which are inverted to give the fraction of occupied sites (Eq 5). These are summed to give an explicit expression for the inverse of the OCV (Eq 6).
Also updates the electrode State of Health models to work with the MSMR formulation.
Fixes # (issue)
Type of change
Please add a line in the relevant section of CHANGELOG.md to document the change (include PR #) - note reverse order of PR #s. If necessary, also add to the list of breaking changes.

[ ] New feature (non-breaking change which adds functionality)
[ ] Optimization (back-end change that speeds up the code)
[ ] Bug fix (non-breaking change which fixes an issue)

Key checklist:

[ ] No style issues: $ pre-commit run (see CONTRIBUTING.md for how to set this up to run automatically when committing locally, in just two lines of code)
[ ] All tests pass: $ python run-tests.py --all
[ ] The documentation builds: $ python run-tests.py --doctest

You can run unit and doctests together at once, using $ python run-tests.py --quick.
Further checks:

[ ] Code is commented, particularly in hard-to-understand areas
[ ] Tests added that prove fix is effective or that feature works

Thanks. Yep, tests and examples still to do but wanted another pair of eyes on the general implementation.

To do:

[ ] Refomulate exchange current to use potential and lithiation extent (for numerical stability)
[ ] Make setting up options cleaner for half cells. At the moment the checks are set up such that you have to pass a tuple of options for the open circuit potential, particle and intercalation kinetics for a half cell even though the values in the li metal side are ignored (or don't make sense in the case of particle)


Update treegrid.html

Use jsTree assets from cdnjs, this makes the page work without having to put a jsTree distribution into the lib directory

I used to do a lot of offline work with this. Nowadays, I even have Internet at 39,000 feet. Thanks.


[Gally]: master <- dev

Automatically created by Git-Ally

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


config.yml corrupted/not working at all

Describe the bug
Opening config.yml will simply show Error while running this#saveToString(). I tried deleting it and reloading the plugin, same thing happened
Expected behavior
The config.yml should not return an error and therfor be uneditable
Screenshots

Additional context
The error isn't the only thing that shows but the rest are just comments, so it's still a useless and uneditable config
Discord contact: raffel080108#4231

I was also having this issue yesterday, I think it affects all of TradeSystem's .yaml files.

The file extension is .yml and I cannot confirm this as my layouts.yml file does not do this. I didn't edit it tho since the issue had occured so I'm not sure if it's because of that

Oh yeah, my bad, I meant .yml files

I know, just mentioned it

I personally think I had it happening for all of my yml files, though I removed the plugin and its folder from my server so I can't check

I already posted information about this. Please follow my guidelines on my discord in #talk.


Large test command api

Fix content-type of post new command request
Add large tests for command apis: postNewCommand, getCommand, listCommands

@yongpingchen LGTM.


Determine conf hashtag and add to website

So far, looking at #msdayny. Doesn't seem to have been used before so no tag pollution on twitter.


[Form Provider Refactor] WaypointEditor

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/30008
Tests

After logging in press + button > Request money
Open Distance tab
Press start
On next screen start typing the address
Press Save
You should be navigated back and the address should be saved.

[x] Verify that no errors appear in the JS console

Offline tests
Same as above

QA Steps
Same as above

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
https://github.com/Expensify/App/assets/91068263/7837ac77-ebae-4a8d-92ed-4d6b48d5bf2b

Android: mWeb Chrome
https://github.com/Expensify/App/assets/91068263/401a3724-f517-4c65-83f5-b1790bbbd012

https://github.com/Expensify/App/assets/91068263/ff3aeee2-c1f6-4226-9802-a8468f829b2f

iOS: Native
https://github.com/Expensify/App/assets/91068263/b3d07096-9ec6-42ef-9d9f-7365ef3a4c53

iOS: mWeb Safari
https://github.com/Expensify/App/assets/91068263/06db3d6f-1a6f-4947-a194-782457d08495

MacOS: Chrome / Safari

https://github.com/Expensify/App/assets/91068263/3ae45bb5-b936-4f75-b33d-4bbc7a739479

MacOS: Desktop
https://github.com/Expensify/App/assets/91068263/bb03e490-fc35-4b43-96dc-9c19a806789e

@hoangzinh done ✅

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Cherry-picked to staging by https://github.com/yuwenmemon in version: 1.4.7-4 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Deployed to staging by https://github.com/luacmartins in version: 1.4.8-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
cancelled 🔪

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/yuwenmemon in version: 1.4.8-3 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅


Create a blinkenlights player

For scenarios where you want lights to alternate between one (or more) colors, we should create a blinkenlights config player which can have all the specific properties, timing, and sync we'd want for that.
Details will need to be worked out. This is more of a placeholder for now.

Hi there. As far as working out the details for this, who/what needs to be involved in working them out?

I thought about some config options for how this might work a while back:
https://groups.google.com/g/mpf-users/c/tcU-dRa1zdQ/m/2dAS0_mABgAJ

Let me just copy your suggestion over here:

I considered something like what you suggested, but the thing with Game of Thrones is, there are 7 modes, any 2 of which can run concurrently.  So there would be 7 "slots" for the lights and that would mean the lights were in the "off" state most of the time.  I saw your link for the blinkenlights discussion and I think this would be a solution to this problem.  I started thinking about this some.  I was thinking to have a "blinkenlights" section of the config, along with a "blinkenlights_player".
Example:

blinkenlights:
  stark:
    each_duration: 1 # How long each color will be on per cycle
    off_duration: 1 # How long the light is off per cycle
    off_when_multiple: false # whether the light turns off in each cycle if multiple colors are defined for this blinkenlights already (ie, does it go red, green, off, red, green, off - or just red, green, red, green)
    light: l_stark_sigil # the light - this should be a color-changing light

blinkenlights_player:
  my_event:
    stark: # which blinkenlights to change
      action: add # add a color to the blinker
      key: mykey # each new color should have its own key so that it can be removed later
      color: white # the color of the blink

  mode_ended:
    stark:
      action: remove # remove the color from the blinker
      key: mykey # the key to remove

So the blinkenlights section would define the blinker (lights and duration etc), and you would use the blinkenlights_player along with a key to add and remove a blink.

I like this. Very good starting point. I guess we do not even need the mode_ended as this would be auto-removed if the blinkenlight_player is used inside a mode.
Open questions to me:

How long is each cycle? Does it get longer with more lights?
How do we sync those cycles? For instance, one blinkenlight might have one colors on it and anther one two. Will one of them run faster? Will the off time be shorter?
Is there a max for active lights per blinkenlight?
How do we order lights? By mode priority? I guess it should be the same for all blinkenlights.

Here are my thoughts for the questions:

How long is each cycle? Does it get longer with more lights?

Each cycle is determined by the each_duration parameter in the blinkenlights: section. So, if each_duration is 0.5, then every color that's added to the light will last for 0.5 seconds (plus 0.5 second for the "off" state of the light if off_when_multiple is set to true and there are more than 1 color).

How do we sync those cycles? For instance, one blinkenlight might have one colors on it and anther one two. Will one of them run faster? Will the off time be shorter?

Multiple blinkenlights would not be sync'd together.  If one blinkenlight has 1 color, and other has 3 colors, then they would get out of sync.  But this is ok, since the idea is, they are signaling to the player which modes (colors) are active for that shot, so you wouldn't expect their cycles to be in sync.

Is there a max for active lights per blinkenlight?

I don't have a strong preference for this, but if it's necessary to implement a max, then I would guess once the max is reached, additional add to that blinkenlight would just be ignored.

How do we order lights? By mode priority? I guess it should be the same for all blinkenlights.

My initial thought was to order this based on first-come-first-served.  I hadn't given this much thought to mode priority, since in Game of Thrones, all the relevant modes that use the blinkenlight would probably run at the same priority anyway.

I think we should sync those somehow. Otherwise the result would look odd. Stern also somehow syncs and sorts them. Just did not figure out the logic yet.

I can add here for how Game of Thrones works with its lights.  There are two things to note that it does, and it is how I would propose it be introduced to MPF.

There is always a defined order, and that order cannot ever change.  That sequence always ends with an off segment (however, I think config to allow the user to say true or false would be good).  So if it is playing one light its on then off repeat.  If you have three (the max in GoT), it might go white, blue, light purple, off, then repeat.  So if you went into blinkenlight said an existing light is of this type, I would need to tell it the duration I want (which I would recommend the end user make the same for all of their blinkenlights), and if you have an off segment at the end of your loop.

There is never an issue with the sync_ms, as the all go for a fixed amount of time.  You cannot change the time to say red for 200ms and green for 100ms, and then off for 50ms.  It is always a fixed amount of time (We should let the user customize this).  But then all lights should blink for the same duration.  In GoT, if one light has color, another has two colors, and a third has three colors, they all hit the same period of time in any color or off.  So while they might be doing different things, the transition for colors is perfectly in sync always.  I have slow mo video of this if needed for reference.

So that being said, I would propose the code for the config should look like the following:
blinkenlights:
  stark:
    light: l_stark_sigil # the light - this should be a color-changing light
    off_when_multiple: false # whether the light turns off in each cycle if multiple colors are defined for this
          blinkenlights already (ie, does it go red, green, off, red, green, off - or just red, green, red, green)
    duration: 100ms #or whatever you want in ms

As for the player, I think that looks good.  Maybe it makes sense to have a priority for that color, which could be applied every time by the user when the player is called.  My thoughts here are that you could say I want white to be priority 100 so that it always plays first, and every time you're player queues a white light, you would need to put priority 100.  Then I want purple to be priority 0 so it always plays last.  I could then stack any colors that I want using the player and be able to give them relative priorities on their show.  This way you have full control over the order regardless of the order when the are invoked by the code.  And with duration being the same for all lights, they are in sync, although we probably still want sync_ms on the player, so that the flashes sync with all other lights going on the playfield.  Then whether this show, or another show would all be based on priority of the mode where its in, and relative priority of the show itself.  So this can still get covered up, just like any other show.
blinkenlights_player:
  my_event:
    stark: # which blinkenlights to change
      action: add # add a color to the blinker
      key: mykey # each new color should have its own key so that it can be removed later
      color: white # the color of the blink
      priority: 100

In looking at the current lights code a bit, I have a thought assuming that my understanding is correct.  We have the LightStack, which is an array that houses all calls to that light and the priorities (in a sorted order with highest priority in slot [0]).
So it almost seems like we could utilize many of the things that are already in lights today.  We would just need a flag for lights of is_blinkenlight: (true of false).  If you set true, then we can run a different player for lights with that setting.  If the flag is false, do it just like today, top priority plays.  If the flag is true, then we play them through in priority, and loop.  When we move to the next value in the array, we just need to verify an item still exists.  If so, continue on, if not its time to loop back to the beginning.
Maybe I'm oversimplifying or not understanding the complexities here.  But if we can argue through final stuff, I am happy to help (as my abilities allow) with implementing this new feature.

Yeah we can definitely use something like LightStack in the Blinkenlights device. I would not merge this logic into lights for a few reasons. First you probably still want to run normal light shows on blinkenlights which might otherwise become tricky. Second lights already contain a lot of logic and complexity. However, the I would choose a similar approach: Blickenlights contains and ordered list. As soon as there is something on the stack it would run an async loop and keep updating the underlaying light. Blinkelights player would just add and remove entrys.

Jan, I will certainly defer to you on knowledge of how all of this should work from a technical perspective.  My questions are:

Do we still need color corrections an all of that that's contained in the lights?
Do we want to use the stack, and just add another param of blinkenlights (True/False).  All lights are false, then blinkenlights_player passes true, and we iterate through true only?

If the answer is need our own device type from scratch, are you thinking we need the fades, color corrections, light config verification, etc.?  Or can we assume that is handled in lights.  We then just need the stack class, and then the color, add_by_key, remove_by_key, etc. to just pass the minimal amount of data into this method, assuming that lights are already taken care of in their device?
Also, the name blinkenlights... are we set on this?  It doesn't seem to be very informative for what this actually is.  MultiColorLights, MultiLights, DynamicLights, (I'm sure others have better thoughts) seem to be more descriptive of what this is, a single light that can cycle multiple colors at a time.

Also, the name blinkenlights... are we set on this? It doesn't seem to be very informative for what this actually is. MultiColorLights, MultiLights, DynamicLights, (I'm sure others have better thoughts) seem to be more descriptive of what this is, a single light that can cycle multiple colors at a time.

We are not set on that. I guess we should think about when you use it. Something such as StackedIndicatorLight or IndicatorLight or ModeIndicatorLight?

Jan, I will certainly defer to you on knowledge of how all of this should work from a technical perspective. My questions are:
1. Do we still need color corrections an all of that that's contained in the lights?

Yes we still need that. But it already exists in the Light class. I would just add/remove entries from the light stack in our new device based on the new internal stack of all entries. Does that make sense?

2. Do we want to use the stack, and just add another param of blinkenlights (True/False).  All lights are false, then blinkenlights_player passes true, and we iterate through true only?

I would separate those two into separate classes because the logic is different.

If the answer is need our own device type from scratch, are you thinking we need the fades, color corrections, light config verification, etc.? Or can we assume that is handled in lights. We then just need the stack class, and then the color, add_by_key, remove_by_key, etc. to just pass the minimal amount of data into this method, assuming that lights are already taken care of in their device?

Yes exactly. We build this on top of lights (similar to how light_player works on top of lights). Our new device would interface lights. Then our new player would interface our new device.
Kind of like this: blinkenlights_player -> blinkenlight -> light -> hw_light -> hardware

I submitted a pull request for an implementation of blinkenlights, but it could be improved.  The current pull request works the way I outlined above, but it doesn't use LightStacks or anything that was discussed afterwards.  Mainly because I don't know how light stacks work.  I created a new device called blinkenlight, along with a config player called blinkenlights_player.  Of course, this all could be change/improved as needed.  It was just my initial stab at it.
I created tests as well, but didn't update the documentation yet, since all this could change/be scrapped.

Looks good overall. I like that you included tests. Some small things I would like to add/change:

Synchronization of blinkenlights
Methods to add/remove entries instead of direct access to internal variables


Fixed issue where the estimator was printing beyond the dataset size …

…for the last batch
Description
As title.
@roywei @abhinavs95 @karan6181

@mxnet-label-bot Add [Gluon]

Thank you for your contribution. LGTM

@mxnet-label-bot Update [Gluon, pr-awaiting-merge]

Merged. Thanks for your contribution!

Is it merged into the branch fit-api?

@wkcn yes, that feature is being developed in the feature branch.


[DS-1702] XSS injection possible on recent submission (JSPUI)

This PR addresses the resolution for the possible XSS injection in the "recent submissions" excerpt (in homepage, collection home and community home) as mentioned in https://jira.duraspace.org/browse/DS-1702
The PR contains also a change on configuration (see dspace.cfg). Now the default for "how many recent submission should be displayed" is set to 5. Also I have modified the comment above the line to clarify that is only for JSPUI. I have seen in XMLUI code and i think that this configuration is not used. But i need a double check from a XMLUI developer.

I've tested this, and it looks to work well. I'll merge this shortly.
As for the minor configuration change...@lap82 is correct. The "recent.submissions.count" option in dspace.cfg is no longer used by XMLUI (with Discovery as the default option).  But, leaving it as defaulting to "0" disables the recent submissions carousel on the JSPUI homepage. So, the new default of "recent.submissions.count=5" seems fine.

On further analysis, I'm wrong.
"recent.submissions.count" is still actively used in XMLUI on the Collection and Community homepages ONLY.  Setting it to "5" as a default causes the last 5 recent submissions to be listed twice (once by Discovery, once by the "recent.submissions.count" setting).
So, we'll need to wait to resolve the configuration around "recent.submissions.count".  That likely should be logged as a separate bug in DSpace.
For now, I'll just merge the security fix (https://github.com/lap82/DSpace/commit/542ab19f62a0aff43422bddf108bf2c67535dc76), and not change the "recent.submissions.count" default.

Rather than merging this entire PR, I've manually cherry-picked the security fix commit ONLY  to master: https://github.com/DSpace/DSpace/commit/5aa9ce16f07450324bd3302b5e3147915795cc92


api title when nil

https://scr.infinum.co/stjepan_hadjic/nar-connecting.devapidocsversion1_2015-03-26_11-44-48.jpg

This has now been fixed on the master branch and will be published with release 0.0.13


latest Zanata translation changes in drools-wb from 2016-09-04

Jenkins please retest this.

+1 to merge.


combustion 1.3.6 fails to require sprockets for Rails 6.1.1+

Upgrading from combustion 1.3.5 to 1.3.6 caused my project build for Rails 6.1 to start failing with:
         ActionController::RoutingError:
       No route matches [GET] "/javascripts/application.js"

I confirmed that the difference between combustion 1.3.5 and 1.3.6 alone determines green/red.
Oddly, my project was still passing fine for Rails 6.0 and 7.0 -- failing only for Rails 6.1.
Rather than spend time getting to the bottom of this somewhat confusing situation, I was considering just locking to combustion 1.3.5 in my Appraisal gemfile for Rails 6.1.  ¯\(ツ)/¯
But... took a look at the diff.... https://github.com/pat/combustion/compare/v1.3.5...v1.3.6 ...
Hmm, it it possible sprockets is no longer being included for Rails 6.1 because of different logic here?   Maybe the new rails_gate.call(">= 3.1", "<= 6.1") will not actually pass for Rails 6.1.6, is 6.1.6 <= 6.1 according to rails_gate?
Yep, debugging, I think that's it. rails_gate.call(">= 3.1", "<= 6.1") is false for Rails 6.1.6.  I think you mean it to be true for any Rails 6.1.x, but in fact it's true for 6.1.0 but not 6.1.1+.
One way to workaround: manually adding sprockets-rails to my Gemfile resolves the problem (I think because having it in top-level Gemfile is one way to force the require that combustion is erroneously deciding not to do).
Editing combustion source to change that line to eg rails_gate.call(">= 3.1", "< 6.2") resolved the problem for me too.
It would probably be useful to have some specs for the VersionGate class, verifying it's behavior.

Thanks for the debugging @jrochkind, that's super helpful :) I've just pushed a fix and released a new version as well (1.3.7).


[PL-45598] Add diagrams to external MongoDB tutorial

Add diagrams to external MongoDB tutorial
https://harness.atlassian.net/wiki/spaces/SPG/pages/21324073461/Harness+Self+managed+with+External+MongoDB
For reviewers, a preview is available:
---preview building---
What Type of PR is This?

[ ] Issue
[ ] Feature
[x] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[x] Tested Locally
[ ] Optional Screenshot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65cff1571a4874388881a7ed--harness-developer.netlify.app


Flashlight icon unintuitive

My natural inclination for adding attaching parts to constructs in the diagram was to double-click on the diagram.  The dialog that comes up there should have some way of getting you into part-adding mode.
I only found the flashlight icon after Chris told me about it - before that I was totally lost.

I will change the icon to a magnifying glass.

The flashlight icon has been replaced by a magnifying glass and there is now a button in the part editor labeled "import registry part" which lets you browse the registries and select a part to import.


[Snyk] Security upgrade wheel from 0.30.0 to 0.38.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

requirements/dev.txt

⚠ Warning
virtualenv 20.24.5 has requirement distlib<1,>=0.3.7, but you have distlib 0.3.6.
virtualenv 20.24.5 has requirement platformdirs<4,>=3.9.1, but you have platformdirs 3.8.0.

Vulnerabilities that will be fixed
By pinning:

Severity
Priority Score (*)
Issue
Upgrade
Breaking Change
Exploit Maturity

589/1000  Why? Has a fix available, CVSS 7.5
Regular Expression Denial of Service (ReDoS) SNYK-PYTHON-WHEEL-3180413
wheel:  0.30.0 -> 0.38.0
No
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.
Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Regular Expression Denial of Service (ReDoS)

Checkmarx One – Scan Summary & Details – 603f4add-5e8e-4874-8596-d317a34262a3
No New Or Fixed Issues Found


Running a command without the required parameters should show --help

If I run an epinio command and forget that there are additional parameters required, I have to rerun the command with --help.
Instead if required parameters are missing --help should be shown instead of just an error message.
At the moment it looks like this:
epinio services list-plans
accepts 1 arg(s), received 0

And it should look like this:
epinio services list-plans
accepts 1 arg(s), received 0

Lists all plans provided by the named service class

Usage:
  epinio service list-plans CLASS [flags]

Flags:
  -h, --help   help for list-plans

Global Flags:
      --config-file string       (EPINIO_CONFIG) set path of configuration file (default "/home/thardeck/.config/epinio/config.yaml")
  -c, --kubeconfig string        (KUBECONFIG) path to a kubeconfig, not required in-cluster
      --no-colors                Suppress colorized output
      --skip-ssl-verification    (SKIP_SSL_VERIFICATION) Skip the verification of TLS certificates
      --timeout-multiplier int   (EPINIO_TIMEOUT_MULTIPLIER) Multiply timeouts by this factor (default 1)
      --trace-level int          (TRACE_LEVEL) Only print trace messages at or above this level (0 to 5, default 0, print nothing)
      --verbosity int            (VERBOSITY) Only print progress messages at or above this level (0 or 1, default 0)

Acceptance criteria

Missing required parameters result in the output of --help of this command
There is still an error message shown what is missing above or below

It looks be the SilenceUsage: true config in our cobra commands. Now going over all and changing them to false.

For best effect it seems that we should use SilenceUsage: false in general, and dynamically set it to true where needed. Which is when an internal error happens, i.e. from the backend and such. These are not helped by showing the usage, at all.


Updated comments in questions_fetch.py

Comments were added to the code . Which gives an  understanding about the function , pre-conditions for the function to work successfully and the post conditions is given when is function meets the pre-conditions .


Rolling up main to beta

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.5 out of 6 committers have signed the CLA.:white_check_mark: seojune79:white_check_mark: ctowns:white_check_mark: cjswedes:white_check_mark: greens:white_check_mark: dsobierajsk:x: kdbangYou have signed the CLA already but the status is still pending? Let us recheck it.


bpf: nodeport: don't reset aggregate ID when revDNAT is called by bpf_lxc

tail_rev_nodeport_lb*() is typically used for RevDNAT of replies by a remote service backend, on a NAT connection. To avoid accidental rate-limiting in to-netdev, we need to clear the EDT aggregate-ID (which is stored in skb->queue_mapping).
But in the "legacy" path for replies by local service backends, from-container also tail-calls to CILIUM_CALL_IPV*_NODEPORT_REVNAT for RevDNAT handling. Current code would then accidentally clear the aggregate-ID that was previously set by bpf_lxc, and the traffic would pass through to-netdev without rate-limiting.
Fix this by excluding the relevant code for bpf_lxc.

/test


using hf_transfer should download shards in parallel not sequentially

Is your feature request related to a problem? Please describe.
I have observed when enabling hf_transfer that while the download of each shard in a repo is extremely fast, multiple shards are not downloaded in parallel. In contrast, downloading without hf_transfer enabled does seem to download shards in multiple processes but downloading speed in each process is slow. My understanding is that hf_transfer functions by dividing individual files into multiple chunks to download in multiple threads.
Describe the solution you'd like
Would it also be possible to download multiple files simultaneously with hf_transfer enabled?
Describe alternatives you've considered
None that I think immediately think of, since hf_transfer is the only approach providing extremely fast download speeds per file.
Additional context
Add any other context or screenshots about the feature request here.

Hey @tmabraham, you are indeed right. We are deactivating multithreading in Python when downloading with hf_transfer. This is because hf_transfer (written in Rust) is primarily designed to max-out the available bandwidth. As a result, multithreading in both Python and Rust shouldn't bring any beneficial advantage since the main bottleneck is the network bandwidth -or disk IO speed- rather than the cpu compute. In general it is not good practice to multitask a job in several layers since it can overload the machine - bringing a slow down instead of a speed-up.
That been said, you can still try it by yourself (I haven't tested myself). You can run hf_hub_download+hf_transfer on each shard file  in parallel and compare it to snapshot_download+hf_transfer.

(closing this issue as completed given https://github.com/huggingface/huggingface_hub/issues/1831#issuecomment-1814459972)


Start benchmarking with tango

Sets up some benchmarks using tango-bench.
Apart from total compile time, each stage is also benchmarked separately.
 It would be even cooler if we could run the same tests against nu-parser to see how new-nu-parser compares.

I can try to add nu-parser benchmarks, good idea.

Oops, so the new compiler appears slower, even in its incomplete implementation. I wonder why. Clearly, the parsing stage is much slower than everything else, that might be due to the constant peek() re-lexing.

Another item, while we're talking about benchmarks, might be memory consumption since one of the points is to remove spans. Not sure how to get there exactly but it's something to think about.

Good idea. I'll merge this at least, but let's keep digging.


Allow escaped, non-displayable ascii characters

Issue #, if available: #226
Description of changes:
Allows ASCII characters with a numeric value < 32 to be included in string, symbol, and clob values as long as they were escaped in the text source.
e.g. allow the escaped hex sequence \x0b, but not the literal byte 11.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

This changeset is not required. See #226 for details. Closing.


Tweak some scss so that longer descriptions don't overflow or push ma…

…in content

Coverage remained the same at 54.511% when pulling 851f5ec8c7732fdb5bdab16630bf38744c4c60de on feature/long_descriptions into 68f2f6fac14003741826991cab6732a919c448c3 on master.


Change http.request.body.size and http.response.body.size attributes from recommended to opt-in

Fixes #456
Changes
There are a few concerns with http.request.body.size and http.response.body.size:

They are not useful enough to justify their current "Recommended" requirement level
They are defined in terms of the Content-Length header which can already be captured as http.request.header.content-length and http.response.header.content-length
They should potentially be defined in terms of actual bytes read, since Content-Length is not always available, and actual bytes read could be different anyways if the request/response was cancelled.

This PR does two things:

Removes them from HTTP semconv (effectively making them opt-in)
Explicitly marks them as experimental, along with a comment not to mark them stable when we mark the other HTTP attributes as stable next week

I will send a separate PR to propose changes to the definition of these attributes based on the other concerns above.
Merge requirement checklist

[x] CONTRIBUTING.md guidelines followed.
[x] CHANGELOG.md updated for non-trivial changes.
~schema-next.yaml updated with changes to existing conventions.~

@trask I think you need to regenrate the tables

I guess we should then consider doing the same for messaging (messaging.message.body.size and messaging.message.envelope.size) and RPC (message.compressed_size and message.uncompressed_size)?

I guess we should then consider doing the same for messaging (messaging.message.body.size and messaging.message.envelope.size) and RPC (message.compressed_size and message.uncompressed_size)?

I opened #474 to discuss/track


Release 0.12.0

Coverage decreased (-6.4%) to 71.732% when pulling 397da5c08d4f5f6e753f941e5576cce684a8282e on eatonphil:release-0.12.0 into a3a35b035e3b4c98142031e6776c5bf61dbf3352 on linode:master.

Coverage decreased (-6.4%) to 71.702% when pulling fea5dfad352a122501c44a658bf4e608755193d7 on eatonphil:release-0.12.0 into a3a35b035e3b4c98142031e6776c5bf61dbf3352 on linode:master.

Coverage decreased (-6.4%) to 71.732% when pulling 0b93072413b387822dd9389d6cd21239baa2d8a3 on eatonphil:release-0.12.0 into a3a35b035e3b4c98142031e6776c5bf61dbf3352 on linode:master.

Coverage decreased (-6.4%) to 71.732% when pulling 0b93072413b387822dd9389d6cd21239baa2d8a3 on eatonphil:release-0.12.0 into a3a35b035e3b4c98142031e6776c5bf61dbf3352 on linode:master.

Coverage decreased (-6.4%) to 71.732% when pulling 0b93072413b387822dd9389d6cd21239baa2d8a3 on eatonphil:release-0.12.0 into a3a35b035e3b4c98142031e6776c5bf61dbf3352 on linode:master.

Coverage decreased (-6.3%) to 71.735% when pulling c8b95c66a5469dcf4ab15719580bcffe4e734e61 on eatonphil:release-0.12.0 into a3a35b035e3b4c98142031e6776c5bf61dbf3352 on linode:master.


Return code 1 in gulp-sonar 3.0.0

I have gulp-sonar 3.0.0 with Sonarqube 5.3 and JavaScript plugin version 2.10.we get the following error in our build scripts:
11:42:44] 11:42:44.510 ERROR: Error during SonarQube Scanner execution
[11:42:44] java.lang.IllegalStateException: Report processing is taking longer than the configured wait limit.
at org.sonar.plugins.buildbreaker.QualityGateBreaker.getAnalysisId(QualityGateBreaker.java:165)
at org.sonar.plugins.buildbreaker.QualityGateBreaker.execute(QualityGateBreaker.java:108)
[11:42:44] Return code: 1.
/development/workspace/<PROJECT_NAME>/node_modules/gulp-sonar/index.js:74
throw new PluginError('gulp-sonar', format('Return code: %d.', code));
^
Error: Return code: 1.

Please try again with the latest version.


How we can force/test error event?

📚 Documentation
No information about how to test and see error event in action. Is it event working?

Yea because no one was eager to answer.


ppn2ocr: oai.sbb.berlin certificate problem

f5b2eed contains a work around (verify=False) for https://oai.sbb.berlin not having a valid certificate. This should be removed as soon as it gets a proper certificate.

It seems to be signed by DFN – is this not part of the "normal" CA bundles?

It's a certificate chain problem. I opened a ticket at SBB.

https://oai.sbb.berlin is fixed now and bb703152db47a4f522d581f240822643c1516eac removes the workaround.


menuOptions in MathJax 3 seems to be ignored altogether

Issue Summary
Tried in Chrome 98
Steps to Reproduce:
According to https://docs.mathjax.org/en/latest/options/menu.html, the options.menuOptions.settings configuration object should enable the user to, for example, turn off assistive MML(assistiveMml) and remove math from tabbing (inTabOrder). However, these options do not seem to work at all.
With the following configuration:
MathJax = {
  options: {
    enableMenu: true,
    /*renderActions: {
      assistiveMml: []
    },*/
    menuOptions: {
      settings: {
        semantics: true,
        assistiveMml: false,
        inTabOrder: false
      }
    }
  }
};

... I would expect all math to be out of tab indexing, assistive mml to be disabled and the math menu to show (and some semantics feature to show in the code). The menu is indeed available but so is assistive mml and all math are included in tabbing. If I disable the math menu and uncomment the block in renderActions, I accomplish what I want, but this is not what the documentation says. Also, I should be able to disable math menu but still have tabbed math, which I can't.
Sandbox: https://codesandbox.io/s/pure-mathjax-v3-menuoptions-xdk7fc
In MathJax 2, the options for including math in tabbing works great and interplay with the menu being enabled flawlessly, e.g., I can enable the menu and disable the tabbing and vice versa with
MathJax = {
  menuSettings: { inTabOrder: false },
  showMathMenu: true
};

Sandbox: https://codesandbox.io/s/pure-mathjax-v2-menuoptions-f8c3n5
Any other information you want to share that is relevant to the issue
being reported. Especially, why do you consider this to be a bug? What
do you expect to happen instead?
I would expect these settings to control what the documentation says and that the control would be independent from other settings, such as enableMenu.
Technical details:

MathJax Version: 3.2.0
Client OS: Mac OS Catalina 10.15.7
Browser: Chrome 98.0.4758.80 (Official Build) (x86_64)

Also, I should be able to disable math menu but still have tabbed math, which I can't.

Not a response regarding whether this is expected MathJax behavior but in such a situation (menu present, output not in the tab order) the page would fail WCAG 2.1.1 (all functionality must be keyboard operable).

Aha..

So this behaviour changed from version 2?
If so it should be clearly documented that the menu cannot be visible with tabbing disabled
What about the assistiveMml thing? I didn't manage to turn that off (using the property in menuOptions no matter if the menu was enabled or not.

There is a bug where of some of the sticky value (the ones set in the menuOptions.settings variable) are not being initialized correctly.  This was reported in #2786, and is fixed in pull request mathjax/Mathjax-src#769, so it will be working in the next release.
Both the Assistive MML and the tab order settings were subject to this problem, along with a few others.  The semantics setting is not one of them, so you can see in your example that that one is working (if you show the MathML for your equation).   Also, the menu items are properly checked/uncheck, so the settings are not entirely ignored.  They just don't initialize properly.
In the meanwhile, here is a configuration that applies the patch from the pull request:
MathJax = {
  options: {
    enableMenu: true,
    menuOptions: {
      settings: {
        semantics: true,
        assistiveMml: false,
        inTabOrder: false
      }
    }
  },
  startup: {
    ready() {
      const {Menu} = MathJax._.ui.menu.Menu;

      class myMenu extends Menu {
        constructor(document, options) {
          super(document, options);
          this.applySettings();
        }

        applySettings() {
          this.setTabOrder(this.settings.inTabOrder);
          this.document.options.enableAssistiveMml = this.settings.assistiveMml;
          this.document.outputJax.options.scale = parseFloat(this.settings.scale);
          if (this.settings.renderer !== this.defaultSettings.renderer) {
            this.setRenderer(this.settings.renderer);
          }
        }
      }

      if (MathJax.version === '3.2.0') {
        MathJax.config.options.MenuClass = myMenu;
      }
      MathJax.startup.defaultReady();
    }
  }
};

So this behaviour changed from version 2?

Only accidentally due to this initialization bug.  But Peter is right, these settings are not in compliance with WCAG specifications, and should only be used if there is a very good reason for it.  While it is possible for a user to enable the tab order setting in the menu, an assistive user who is using the keyboard rather than the mouse will not be able to get to the MathJax menu if the math isn't in the tab order, and so you will have made your page inaccessible to such a user.  It is much easier for a non-assistive user to turn off the setting than for an assistive user to turn it back on, so it is best to leave the tabbing order as is, unless you either don't care about such users, or know for certain that you will not be having any of them visit your site (e.g., if your site is for a specific audience and you know there are no assistive users in it).

Thanks for a great answer. I admire the extra effort for assistive users, even though in a lot of cases it boils down to non-assistive users wanting to get rid of the extra resulting details in graphic and ux ... But I agree with you from a principal level... So the idea is that as long as you have regular text, there are very many assistive technologies and such to help out but once it is typeset by MathJax, then an assistive user can't use those tools anymore and that's why you're putting so much effort into these features? Just guessing here...
All in all, there should be a flag in browsers / window object which indicates to libraries whether we want to enable assistive features and based on that do different things (e.g. useAssistiveDefaults if in assistive mode or something). Because I think most people would want to please assistive users too but maybe not at the cost of, what they see, as a lower experience for a larger user group.... then ofc it's debatable whether the experience is really worse or if it's just a mental hangup but....yeah this is a different subject altogether :)
But very happy with the answer! Thanks!

But the documentation is hopefully improved by 3.2.1 then so that it's clear, both what is possible and not and also why this design was chosen :)


(graphcache) - Fix edge-case of erroring introspection on schema-awareness

Resolve https://github.com/dotansimha/graphql-code-generator/issues/5981

Add missing test for formatted introspection query on introspected schema-aware store
Add cases for built-in typenames to ast/schemaPredicates

Thank you!


WIP: Use 'OPENSSL_' as common include guard prefix [1.1.1]

This is a backport of #9274 to [1.1.1].
The first two commits of #9274 were cherry-picked (actually, rebased) onto #9281. The third commit is autogenerated using the update-openssl-include-guards script.
be1d69965f util/mkerr.pl: use 'OPENSSL_' as include guard prefix of *err.h files
27d86e8037 Add update-openssl-include-guards script [to be discarded]
5044ba16d3 run update-openssl-include-guards
Using pull request #9281 as the base is necessary to apply the changes in util/mkerr.pl cleanly.
This pull request is currently just a proof-of-concept of how I intend to do the semi-automated backporting. It will go out of WIP after #9274 and #9281 have been approved.

Rebased from pull request #9281 onto master (without further changes), since the former has been merged now.

This is a backport of #9274

Pull request  #9274 has grown too large now to be backported. Apart from that, it remained unclear whether changing the names of the #incude header guards in a stable release could be safely done without breaking things.
That's why I am closing this pull request.


#2989 Onboard helm charts in CLI

Signed-off-by: Christian Kreuzberger<EMAIL_ADDRESS>Implements #2989
This PR depends on https://github.com/keptn/keptn/pull/3201 and https://github.com/keptn/keptn/pull/3218
With this PR I've moved the functionality for onboarding a helm chart (into the git config repo) into the cli command onboard service.

Same as in #3201, I've updated
 			stagesHandler := apiutils.NewAuthenticatedStageHandler(endPoint.String()+"/shipyard-controller", apiToken, "x-token", nil, endPoint.Scheme)

But I believe it won't work until some other changes from go-utils etc... go through, which was not PART of this PR.


Add delay after countdown to trigger capture (and Display Smile-Screen longer)

Is your feature request related to a problem? Please describe.
My backend (gphoto2 / Canon 700D) is so fast, that the Countdown won‘t run till the end and the „smile-screen“ is often skipped completely.
Countdown will directly go to 9-dot-animation.
Describe the solution you'd like
It would be nice to be able to set a delay for the Camera to be triggered.
In the delay-period the smile-screen will be shown.
Maybe additional customizations for smile screen would be nice (e. g. disable liveview, so that the attention goes to the Camera and Not the screen.)
Describe alternatives you've considered
Using slower Camera lol
Additional context
I could add a .gif later

What about raising the timing in uisettings for the message time?

So sorry, I missed that implementation, since it's in another place. My bad.
I still think the current implementations isn't very intuitive.
The "Takepic Msg Time" steals the time from the countdown.
In my opinion it would be better, if the Msg Text would be shown after the countdown is finished and can then be modified as desired. But that's just my taste.
Describe the solution you'd like
Maybe a compromise would be to have two settings. This way it would be completely configurable:

Time to display Msg Text before countdown ends
Time to display Msg Test after countdown ends

Thank you!

It's a bit more complicated and the implementation needs to cover also slower backends. It's built with that in mind.
You can offset the capture when the camera is triggered before count to 0. That is to improve experience with slower backends.
You can also offset the takepic msg time, which steals the time from the overall counter, but you could extend by that amount.
Now the message is hidden in the moment the backend signals that the capture is done and the 9 processing dots appear.
I see that for fast backends the flicker of takepicture message could be confusing.
I am still hesistant to add another option for this and maybe find a better simpler solution.

I get your point but also see the advantage of my solution :)
In my opinion it is nicer if the countdown runs to 0 and I see the smile page for like 2-3 seconds and in the worst case the picture is already taken, when the smile is still shown. People who don't want the "extend after the countdown" just could leave it at 0.
Another option would be to configure an offset between real counter and displayed counter. That way the displayed counter could already be at 0 and show the Msg Text but in the background the real counter has time remaining. But I think this is more complex.
In the mean time I think I have to live with the counter to switch to the Msg Text bis X seconds not been displayed counting down.

Actually the offset is also to take into account that the trigger to the camera is offsetted in case the delay of the camera is quite long.
Just extending the smile message is not working. I would not like to have an additional delay just to display the smile longer even if all processing is done. It shall be fast :)
I consider how it can be improved without additional settings.

Yes, since speed is a key feature of the software, I totally get your point.
Maybe a solution would be to allow negative values for Capture Offset.
This way the processing can continue right when capture is done...

I'd consider the virtualcamera as fast backend. I used it to improve the countdown. The improved version is in the main branch of this repo. Changes made here: https://github.com/photobooth-app/photobooth-frontend/commit/32a884797af9a67cf307ba023e90ec3bbebe3ee6
Following values give me now way better UX in the latest main:
Countdown Capture First = 3
Countdown Camera Capture Offset = 0,2
Takepic Msg Time = 1
The fix lowers the animation-speed to 100. The default was 600 and led to the circle still showing some remaining time despite countdown was finished already.
Also the takepicture message is now displayed on top of the circle, the number is hidden if the takepicture message is shown.
I think this should be fine for your setup also?

https://github.com/photobooth-app/photobooth-app/assets/3868450/d1424f11-d270-4f88-8169-ea480f4c9588

Version 2 with the improved timing is released just now.


Show price of entire stack for stackable items when examined

Show price of entire stack of stackable items when examined from
inventory, and not only single item in stack

Didn't knew how to do this before so I just shown examine price of one item in stack, but then I noticed how to do it in jewellery count plugin, so here is the change a bit late.

It looks like you can get the quantity of the item clicked from the widget via the event similar to how the client does it:
                                 if(var2 == 1005) {
                                    var26 = VertexNormal.getWidget(var1);
                                    if(var26 != null && var26.itemQuantities[var0] >= 100000) {
                                       class25.sendGameMessage(27, "", var26.itemQuantities[var0] + " x " + KitDefinition.getItemDefinition(var3).name);
                                    } else {
                                       var17 = FileSystem.method4252(ClientPacket.field2402, Client.field888.field1449);
                                       var17.packetBuffer.writeIntLE16(var3);
                                       Client.field888.method1862(var17);
                                    }

It worked, done.


LiveReload in an endless loop... ?

I'm not sure whether to post this issue here or not, since I'm not sure what's the source of this issue. sory if this isn't the place!
I'm unsing guard-jekyll-plus with livereload gem to watch changes instantly when I refresh my browser...
I'm currently on latest version of xubuntu.
When I run "guard" everything works as expected. I can even whatch my site instantly, without using "jekyll serve --watch" command. BUT inmediately after changing a file, the extension goes crazy and starts to reload the webpage everytime.
here's the output of guard. It literaly fills a lot of screens in very few seconds and ctrl+c is not working...
alumno@alumno-Intel-powered-classmate-PC:~/github/SluggyMaster$ guard
Configuration file: _config.yml
01:26:48 - INFO - Jekyll building...
01:26:50 - INFO - Jekyll build completed in 2.07s /home/alumno/github/SluggyMaster → _site
01:26:50 - INFO - Jekyll watching and serving using jekyll at <IP_ADDRESS>:4000
01:26:50 - INFO - Jekyll watching
01:26:50 - INFO - LiveReload is waiting for a browser to connect.
Configuration file: /home/alumno/github/SluggyMaster/_config.yml
01:26:50 - INFO - Guard is now watching at '/home/alumno/github/SluggyMaster'
[1] guard(main)>     Server address: http://<IP_ADDRESS>:4000/
  Server running... press ctrl-c to stop.
01:27:03 - INFO - Browser connected.

(NOTE: unless I save any file, this will remain here, but when i do, the followin happens:)
01:27:13 - INFO - Jekyll Files changed:  building...
|
|  ~ _posts/2015-12-27-reference.md
|
01:27:14 - INFO - Jekyll build completed in 0.94s /home/alumno/github/SluggyMaster → _site
01:27:14 - INFO - Reloading browser: _posts/2015-12-27-reference.md
01:27:14 - INFO - Jekyll Files changed:  building...
|
|  ~ _site/apidocs.html
|  ~ _site/feed.xml
|  ~ _site/index.html
|  ~ _site/jekyll/update/2015/12/27/welcome-to-jekyll.html
|  ~ _site/api/reference/2015/12/27/reference.html
|
01:27:16 - INFO - Jekyll build completed in 1.36s /home/alumno/github/SluggyMaster → _site
01:27:16 - INFO - Reloading browser: _site/apidocs.html _site/feed.xml _site/index.html _site/css/main.css _site/jekyll/update/2015/12/27/welcome-to-jekyll.html _site/api/reference/2015/12/27/reference.html
01:27:16 - INFO - Jekyll Files changed:  building...
|
|  ~ _site/apidocs.html
|  ~ _site/feed.xml
|  ~ _site/index.html
|  ~ _site/jekyll/update/2015/12/27/welcome-to-jekyll.html
|  ~ _site/api/reference/2015/12/27/reference.html
|
01:27:17 - INFO - Jekyll build completed in 1.27s /home/alumno/github/SluggyMaster → _site
01:27:17 - INFO - Reloading browser: _site/apidocs.html _site/feed.xml _site/index.html _site/css/main.css _site/jekyll/update/2015/12/27/welcome-to-jekyll.html _site/api/reference/2015/12/27/reference.html
01:27:18 - INFO - Jekyll Files changed:  building...
|
|  ~ _site/apidocs.html
|  ~ _site/feed.xml
|  ~ _site/index.html
|  ~ _site/jekyll/update/2015/12/27/welcome-to-jekyll.html
|  ~ _site/api/reference/2015/12/27/reference.html
|
^C01:27:19 - INFO - Reloading browser: _site/apidocs.html _site/feed.xml _site/index.html _site/css/main.css _site/jekyll/update/2015/12/27/welcome-to-jekyll.html _site/api/reference/2015/12/27/reference.html
[1] guard(main)>

(etc...)
Here's my Guardfile
guard 'jekyll-plus', :serve => true do
  watch /.*/
  # ignore /^_site/
end

guard 'livereload' do
  watch /.*/
end

OMG! I'm so sory. I just needed to uncomment this line from Guardfile:
 # ignore /^_site/
I'm not sure why I had it commented, on windows it didn't caused any issue so I left it there. I'm closing now this after less than 5 minutes of open it xD

No problem!
Be sure to check the Guardfile templates from time to time - because some workarounds need changes there.
Use this to be on the safe side:
https://github.com/imathis/guard-jekyll-plus/blob/master/lib/guard/jekyll_plus/templates/Guardfile

(The new Guardfile there has a much smarter watch clause that automatically matches your Jekyll config)

Thanks! I will give it a try


Existing nvim-cmp sources disabled by default

@AbaoFromCUG
Thanks for the great plugin!
Could you provide some guidance on the correct way to enable the neopyter nvim-cmp source using lazy?
It seems that by default, neopyter disables other completion sources.
Before installing neopyter, :CmpStatus (in a .ju.py file) gives my default sources
# ready source names
- buffer
- path
- snippets
- nvim_lsp:basedpyright
# unknown source names
- lazydev

After installing neopyter, :CmpStatus (run in a .ju.py file) gives
# ready source names
- snippets
- neopyter
# unknown source names
- nvim_lsp
- path
- buffer
- lazydev

So it seems that somehow by default neopyter has disabled the lsp/path/buffer completion sources.
Here is the simple default config that doesn't specify any completion sources.
return {
  {
    "SUSTech-data/neopyter",
    dependencies = {
      "nvim-lua/plenary.nvim",
      "AbaoFromCUG/websocket.nvim",
    },
    ---@type neopyter.Option
    opts = {
      mode = "direct",
      remote_address = "<IP_ADDRESS>:9001",
      file_pattern = { "*.ju.*" },
      on_attach = function(buf)
        -- Keymaps --------------------------------------------
        local function map(mode, lhs, rhs, desc)
          vim.keymap.set(mode, lhs, rhs, { desc = desc, buffer = buf })
        end
        -- same, recommend the former
        map("n", "<localleader>nc", "<cmd>Neopyter execute notebook:run-cell<cr>", "run selected")
        -- map("n", "<C-Enter>", "<cmd>Neopyter run current<cr>", "run selected")

        -- same, recommend the former
        map("n", "<localleader>nA", "<cmd>Neopyter execute notebook:run-all-above<cr>", "run all above cell")
        -- map("n", "<space>X", "<cmd>Neopyter run allAbove<cr>", "run all above cell")

        -- same, recommend the former, but the latter is silent
        map("n", "<localleader>nr", "<cmd>Neopyter execute kernelmenu:restart<cr>", "restart kernel")
        -- map("n", "<space>nt", "<cmd>Neopyter kernel restart<cr>", "restart kernel")

        map("n", "<localleader>nn", "<cmd>Neopyter execute runmenu:run<cr>", "run selected and select next")
        map(
          "n",
          "<localleader>nN",
          "<cmd>Neopyter execute run-cell-and-insert-below<cr>",
          "run selected and insert below"
        )

        map("n", "<localleader>nR", "<cmd>Neopyter execute notebook:restart-run-all<cr>", "restart kernel and run all")
      end,
      highlight = {
        enable = true,
        shortsighted = false,
      },
      parser = {
        -- trim leading/tailing whitespace of cell
        trim_whitespace = false,
      },
    },
  },
}

I can also confirm this
# unused source names
- neopyter

# unknown source names
- copilot
- nvim_lsp
- path
- luasnip
- cmp_tabnine
- nvim_lua
- buffer
- calc
- emoji
- treesitter
- crates
- tmux

Do you have a complete .lua configuration file?

I not longer use nvim-cmp,(blink.cmp as an alternative).
So I write a minimize reproduction script in https://github.com/SUSTech-data/neopyter/blob/master/lua-tests/manual/repro-cmp.lua
Then I run neovim with:
nvim -u lua-tests/manual/repro-cmp.lua doc/example.ju.py

# ready source names
- path
- buffer
- neopyter

# unused source names
- cmdline

# unknown source names
- nvim_lsp

But I can't reproduce this issue, could you check you filetype with :echo &filetype, and give me more information/context

Som information: neopyter integration with nvim-cmp via https://github.com/SUSTech-data/neopyter/blob/master/after/plugin/cmp_neopyter.lua
and which just register a cmp source


Implement SHA256 in Script

Implement SHA256 and double SHA256 in Script (for up to 80 bytes)

This PR https://github.com/BitVM/BitVM/pull/54 implement SHA256. @RobinLinus
By @Xavier-96 and @wz14


[WINDOWS] default theme completely broken

everything appears white on the window

What does it look like in beta-3.5?

Fixed with beta-4.


Actions Bot testing

Pull request merged
Thank you for your contribution! Your pull request has been merged.
What's next?
If you're looking for more ways to contribute, I invite you to check out my other projects. Just click my username to find more.


Update Kyverno CRDs for v1.7.3

Checklist

[ ] Update changelog in CHANGELOG.md.
[ ] Make sure values.yaml and values.schema.json are valid.

This has been running on Ghost with no issues. Merging


fix: adjusted button link

References https://autoricardo.atlassian.net/browse/DM-1304
Motivation and context
Support NextLink in the component link button
How to test
Listings project -> https://github.com/smg-automotive/listings-web/pull/618
Thank you 🌎

Would this be a breaking change or would existing usage with as="a" still work?
EDIT: I checked - it still works fine

@Averethel exactly. We keep as=a for external links and NextLink for client-side 🌸

@GutierrezGo I've just noticed something. Can you take a look at it before merging?
If I want to render the Button as a different element than a link (e.g. div for whatever reason) the href prop would still be required. I don't think this is intended behaviour since we want to enforce href only when passing a or NextLink as as. I'm not sure how complex figuring out the correct typing here is. I vaguely recall that chakra does provide some helpers to get the types, but I'm not sure to which extent we can use them with an external component such as NextLink.

@Averethel thank you for the comment. Indeed, the href will be required if as props is passed. The reason behind is because now the type as for the link button is ElemetType. I will say a Dev won't pass a div/span/p... with href. Besides if we pass:
   <Button
      as="div"
      href={`/${language}/ld/listings/${listing.id}/message-lead`}
      onClick={() =>
        trackEvent({
          eventCategory: 'www_Interaction_PI-Detail',
          eventAction: 'Open_Contact_Form',
        })
      }

the href attribute won't specifies the URL of the page the link goes to. Therefore, it won't be a hyperlink and it will only trigger the action on onClick.

Exactly, but even if the generated markup does not contain a hyperlink I am still forced to pass the href attribute. This is not ideal. At the same time, it probably won't come up too often. I am a bit uneasy about merging this PR as is. Can you get a second opinion?

@Averethel what use case comes to your mind that you want to render a div (or anything else than a) instead of a button?

@Averethel what use case comes to your mind that you want to render a div (or anything else than a) instead of a button?

Nothing specific, it was an observation. That's why I said it's unlikely to come up very often before.

alternatively you could make href optional, keep the as="a" as is (...)

Wouldn't making the href optional and changing as be the best of both worlds (assuming we don't want to venture into advanced TS for a very rare use-case)?
We would forgo forcing the href prop when rendering buttons as a tags, but that would be in-line with chakra's behaviour I believe.


Automated cherry pick of #5159: region: lbagent: deploy: use 'public' endpoint type

Cherry pick of #5159 on release/3.1.
#5159: region: lbagent: deploy: use 'public' endpoint type

Codecov Report

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

@@              Coverage Diff              @@
##             release/3.1   #5160   +/-   ##
=============================================
  Coverage               ?   6.75%
=============================================
  Files                  ?     545
  Lines                  ?   95281
  Branches               ?       0
=============================================
  Hits                   ?    6433
  Misses                 ?   88310
  Partials               ?     538

Flag
Coverage Δ

#aFlag
6.75% <ø> (?)

Impacted Files
Coverage Δ

pkg/compute/models/loadbalanceragents_deploy.go
0.33% <ø> (ø)

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 fe44564...715a7c3. Read the comment docs.

/lgtm

/approve


What are the TCP metrics available for Web Apps?

In the portal I currently see these options for scaling Web Apps, in addition to the ones listed here.
TCP Close Wait
TCP Closing
TCP Established
TCP Fin Wait 1
TCP Fin Wait 2
TCP Last Ack
TCP Syn Received
TCP Syn Sent
TCP Time Wait
What are these metrics? They don't appear in the list of Azure metrics.

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

ID: d2dc1ab9-8002-cf0f-d147-f493f3e0ac28
Version Independent ID: 53d9f4d3-efc2-7b1c-7d64-67557a125799
Content: Autoscale common metrics
Content Source: articles/azure-monitor/platform/autoscale-common-metrics.md
Service: azure-monitor
Sub-service: autoscale
GitHub Login: @anirudhcavale
Microsoft Alias: ancav

Thanks for the comment! We will investigate this issue and get back to you soon.

@dcbrown16 thanks for reporting this. I'll take a look to see if these are new metrics from App Services.

Thanks!

@anirudhcavale we continue to receive inquiries about this in CSS. Any news?

We appreciate your question. Sorry didn't fully answer in a timely manner. Since this question was created some time ago, we don't know if it still applies. We kindly ask you to create a new github issue if it's still important. We will engage with you on the new thread. Thank you for your understanding.
#please-close

#assign:rboucher

#please-close


fixes custom circuit breaker config not being injected

Fixes bug in 3.0 where CircuitBreakerConfiguration is not injected into DI and is therefore ignored - this means that the default CircuitBreakerConfiguration is always used regardless of configuration passed.

Thanks @andy-williams for the contribution, this PR has been merged!

Thanks @andy-williams for the contribution, this PR has been merged!

:clap: :clap: :clap: thanks

Hey @jeffrymorris thanks for the update.
However, I don't see this in master.
https://github.com/couchbase/couchbase-net-client/blob/master/src/Couchbase/ClusterOptions.cs#L333
It appears that the CircuitBreakerConfiguration is never injected and this results in using the default rather than the assigned CircuitBreakerConfiguration.

@andy-williams -
My bad, it has been reviewed but not merged yet: http://review.couchbase.org/c/couchbase-net-client/+/131513
There is a comment that needs to be addressed, please respond and will get it worked out!
-Jeff

This is merged.


Line labels v2

Resubmission of #62. I squashed the first two commits of that PR together so that git would recognize these all as new commits.

All of the changes for this were in #67, so we don't actually need this.


Rename Iid fields to IID to match golang convention

This is inconsistent right now, there are some fields that are named IID correctly.

Words in names that are initialisms or acronyms (e.g. "URL" or "NATO") have a consistent case. ? > For example, "URL" should appear as "URL" or "url" (as in "urlPony", or "URLPony"), never as "Url". Here's an example: ServeHTTP not ServeHttp.

From https://github.com/golang/go/wiki/CodeReviewComments#initialisms

I'm closing this PR as the changes it contains are already merged/added by your other PR (#245) and this commit: 7c28a6b84d4ea52affd96b054c9d93805ae8f577
Thanks again for your efforts!

Oops, totally forgot that I was pushing to this branch :D Thanks!


Tabs & makefiles

VSCode Version:1.2.1
OS Version: MacOs ElCapitan

Steps to Reproduce:

create a makefile
edit the make file create a very basic build target as in

start file
CC=GCC
CFLAGS=-c -Wall

build:
$(CC) $(CLFAGS) test1.c -o test

end file

running make build will fail with the infamous "missing separator" reason being VSCODE does do tab correctly.
to fix: edit the file with vi or nano remove the old tabs (created by VSCode) add new ones using nano and run make again (works).

sorry didn't have file to look at char codes used by VS code.

I don't think this is a bug. When you select "Indent Using Tabs" editing Makefiles works just fine.
vi and nano default to indention using tabs while VSCode uses 4 spaces by default.

Thanks! - modified the settings file and all worked as expected. will close the issue.


 IF YOU DO NOT FOLLOW THE FORMAT OR MAKE A GENERIC TOKEN REQUEST YOUR ISSUE WILL BE DELETED WITHOUT COMMENT
YOUR JUSTLIST MUST FOLLOW THE JSON SPECIFICATION
https://github.com/justswaporg/justlists/example.justlists.ts
Checklist

[ ] I understand that this is not the place to request a token listing.
[ ] I have tested that my JustList is compatible by pasting the URL into the add a list UI at justswap.org.
[ ] I understand that filing an issue or adding liquidity does not guarantee addition to the justlists website.

Please provide the following information for your token.
JustList URL must be HTTPS.
JustList URL:
JustList Name:
Link to the official homepage of the JustList manager:

Yes

theresa00

Sorry, your issue will be closed as you did not submit your information in the correct format.


nixpkgs-unstable: options-docbook fails because of nextcloud18

Describe the bug
Recently nextcloud 18 was removed from nixpkgs, but it is still present in the related package list of nixos/modules/services/web-apps/nextcloud.nix. These related packages are evaluated when building the nixos-manpages/options-docbook which prevents a system from updating even without using nextcloud
To Reproduce
Steps to reproduce the behavior:

Use current nixos-unstable without having nextcloud enabled but have the manpages enabled
nixos-rebuild switch

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute: nextcloud18
# a list of nixos modules affected by the problem
module: nextcloud

cc @Ma27

It should be sufficient to remote nextcloud18 from relatedPackages in the module. Do you want to file a patch? :)

Unfortunately it seems like it not so easy. My estimate of the root cause is wrong, by error I looked onto an old version of the module. Sorry for that. In the most recent version of nixpkgs-unstable (c5147860e23ed75ce9d40298c66b416c00be1167) there is no mention of nextcloud18 in the module. Still I have the same problem. The full output of nixos-rebuild switch --show-trace is as follows:
building Nix...
building the system configuration...
error: while evaluating the attribute 'activationScript' of the derivation 'nixos-system-nix-rasp-21.05pre-git' at /nix/store/h8kvkz0al23kw1m9hwxrak522l3qdlkd-nixpkgs-unstable-src/nixos/modules/system/activation/top-level.nix:95:5:
while evaluating the attribute 'system.activationScripts.script' at /nix/store/h8kvkz0al23kw1m9hwxrak522l3qdlkd-nixpkgs-unstable-src/nixos/modules/system/activation/activation-script.nix:80:9:
while evaluating 'textClosureMap' at /nix/store/h8kvkz0al23kw1m9hwxrak522l3qdlkd-nixpkgs-unstable-src/lib/strings-with-deps.nix:75:35, called from /nix/store/h8kvkz0al23kw1m9hwxrak522l3qdlkd-nixpkgs-unstable-src/nixos/modules/system/activation/activation-script.nix:101:18:
while evaluating 'id' at /nix/store/h8kvkz0al23kw1m9hwxrak522l3qdlkd-nixpkgs-unstable-src/lib/trivial.nix:14:5, called from undefined position:
while evaluating the attribute 'text' at /nix/store/h8kvkz0al23kw1m9hwxrak522l3qdlkd-nixpkgs-unstable-src/nixos/modules/system/activation/activation-script.nix:9:5:
while evaluating the attribute 'text' at undefined position:
while evaluating 'g' at /nix/store/h8kvkz0al23kw1m9hwxrak522l3qdlkd-nixpkgs-unstable-src/lib/attrsets.nix:294:19, called from undefined position:
while evaluating anonymous function at /nix/store/h8kvkz0al23kw1m9hwxrak522l3qdlkd-nixpkgs-unstable-src/lib/modules.nix:139:72, called from /nix/store/h8kvkz0al23kw1m9hwxrak522l3qdlkd-nixpkgs-unstable-src/lib/attrsets.nix:297:20:
while evaluating the attribute 'value' at /nix/store/h8kvkz0al23kw1m9hwxrak522l3qdlkd-nixpkgs-unstable-src/lib/modules.nix:512:9:
while evaluating the option `system.activationScripts.etc.text':
while evaluating the attribute 'mergedValue' at /nix/store/h8kvkz0al23kw1m9hwxrak522l3qdlkd-nixpkgs-unstable-src/lib/modules.nix:544:5:
while evaluating the attribute 'values' at /nix/store/h8kvkz0al23kw1m9hwxrak522l3qdlkd-nixpkgs-unstable-src/lib/modules.nix:538:9:
while evaluating the attribute 'values' at /nix/store/h8kvkz0al23kw1m9hwxrak522l3qdlkd-nixpkgs-unstable-src/lib/modules.nix:637:7:
while evaluating anonymous function at /nix/store/h8kvkz0al23kw1m9hwxrak522l3qdlkd-nixpkgs-unstable-src/lib/modules.nix:524:28, called from /nix/store/h8kvkz0al23kw1m9hwxrak522l3qdlkd-nixpkgs-unstable-src/lib/modules.nix:524:17:
while evaluating definitions from `/nix/store/h8kvkz0al23kw1m9hwxrak522l3qdlkd-nixpkgs-unstable-src/nixos/modules/system/etc/etc.nix':
while evaluating 'dischargeProperties' at /nix/store/h8kvkz0al23kw1m9hwxrak522l3qdlkd-nixpkgs-unstable-src/lib/modules.nix:596:25, called from /nix/store/h8kvkz0al23kw1m9hwxrak522l3qdlkd-nixpkgs-unstable-src/lib/modules.nix:525:137:
while evaluating the attribute 'value' at /nix/store/h8kvkz0al23kw1m9hwxrak522l3qdlkd-nixpkgs-unstable-src/lib/modules.nix:379:44:
while evaluating the attribute 'sources' of the derivation 'etc' at /nix/store/h8kvkz0al23kw1m9hwxrak522l3qdlkd-nixpkgs-unstable-src/nixos/modules/system/etc/etc.nix:12:5:
while evaluating anonymous function at /nix/store/h8kvkz0al23kw1m9hwxrak522l3qdlkd-nixpkgs-unstable-src/nixos/modules/system/etc/etc.nix:20:20, called from undefined position:
while evaluating the attribute 'source' at undefined position:
while evaluating 'g' at /nix/store/h8kvkz0al23kw1m9hwxrak522l3qdlkd-nixpkgs-unstable-src/lib/attrsets.nix:294:19, called from undefined position:
while evaluating anonymous function at /nix/store/h8kvkz0al23kw1m9hwxrak522l3qdlkd-nixpkgs-unstable-src/lib/modules.nix:139:72, called from /nix/store/h8kvkz0al23kw1m9hwxrak522l3qdlkd-nixpkgs-unstable-src/lib/attrsets.nix:297:20:
while evaluating the attribute 'value' at /nix/store/h8kvkz0al23kw1m9hwxrak522l3qdlkd-nixpkgs-unstable-src/lib/modules.nix:512:9:
while evaluating the option `environment.etc.dbus-1.source':
while evaluating the attribute 'mergedValue' at /nix/store/h8kvkz0al23kw1m9hwxrak522l3qdlkd-nixpkgs-unstable-src/lib/modules.nix:544:5:
while evaluating anonymous function at /nix/store/h8kvkz0al23kw1m9hwxrak522l3qdlkd-nixpkgs-unstable-src/lib/modules.nix:546:17, called from /nix/store/h8kvkz0al23kw1m9hwxrak522l3qdlkd-nixpkgs-unstable-src/lib/modules.nix:546:12:
while evaluating 'check' at /nix/store/h8kvkz0al23kw1m9hwxrak522l3qdlkd-nixpkgs-unstable-src/lib/types.nix:345:15, called from /nix/store/h8kvkz0al23kw1m9hwxrak522l3qdlkd-nixpkgs-unstable-src/lib/modules.nix:546:22:
while evaluating the attribute 'serviceDirectories' of the derivation 'dbus-1' at /nix/store/kih8qrnq654qjkypixhrfhlg9p539k19-nixpkgs-unstable-src/pkgs/build-support/trivial-builders.nix:7:7:
while evaluating anonymous function at /nix/store/h8kvkz0al23kw1m9hwxrak522l3qdlkd-nixpkgs-unstable-src/lib/types.nix:354:14, called from undefined position:
while evaluating the attribute 'value' at /nix/store/h8kvkz0al23kw1m9hwxrak522l3qdlkd-nixpkgs-unstable-src/lib/modules.nix:557:27:
while evaluating anonymous function at /nix/store/h8kvkz0al23kw1m9hwxrak522l3qdlkd-nixpkgs-unstable-src/lib/modules.nix:546:17, called from /nix/store/h8kvkz0al23kw1m9hwxrak522l3qdlkd-nixpkgs-unstable-src/lib/modules.nix:546:12:
while evaluating 'check' at /nix/store/h8kvkz0al23kw1m9hwxrak522l3qdlkd-nixpkgs-unstable-src/lib/types.nix:345:15, called from /nix/store/h8kvkz0al23kw1m9hwxrak522l3qdlkd-nixpkgs-unstable-src/lib/modules.nix:546:22:
while evaluating the attribute 'passAsFile' of the derivation 'system-path' at /nix/store/kih8qrnq654qjkypixhrfhlg9p539k19-nixpkgs-unstable-src/pkgs/build-support/trivial-builders.nix:7:7:
while evaluating the attribute 'buildCommand' of the derivation 'nixos-manpages' at /nix/store/kih8qrnq654qjkypixhrfhlg9p539k19-nixpkgs-unstable-src/pkgs/build-support/trivial-builders.nix:7:7:
while evaluating the attribute 'buildCommand' of the derivation 'manual-olinkdb' at /nix/store/kih8qrnq654qjkypixhrfhlg9p539k19-nixpkgs-unstable-src/pkgs/build-support/trivial-builders.nix:7:7:
while evaluating the attribute 'buildCommand' of the derivation 'nixos-manual-combined' at /nix/store/kih8qrnq654qjkypixhrfhlg9p539k19-nixpkgs-unstable-src/pkgs/build-support/trivial-builders.nix:7:7:
while evaluating the attribute 'buildCommand' of the derivation 'generated-docbook' at /nix/store/kih8qrnq654qjkypixhrfhlg9p539k19-nixpkgs-unstable-src/pkgs/build-support/trivial-builders.nix:7:7:
while evaluating the attribute 'buildCommand' of the derivation 'options-docbook.xml' at /nix/store/kih8qrnq654qjkypixhrfhlg9p539k19-nixpkgs-unstable-src/pkgs/build-support/trivial-builders.nix:7:7:
while evaluating 'genRelatedPackages' at /nix/store/kih8qrnq654qjkypixhrfhlg9p539k19-nixpkgs-unstable-src/nixos/lib/make-options-doc/default.nix:51:34, called from /nix/store/kih8qrnq654qjkypixhrfhlg9p539k19-nixpkgs-unstable-src/nixos/lib/make-options-doc/default.nix:39:99:
while evaluating anonymous function at /nix/store/kih8qrnq654qjkypixhrfhlg9p539k19-nixpkgs-unstable-src/nixos/lib/make-options-doc/default.nix:70:57, called from undefined position:
while evaluating 'describe' at /nix/store/kih8qrnq654qjkypixhrfhlg9p539k19-nixpkgs-unstable-src/nixos/lib/make-options-doc/default.nix:56:18, called from /nix/store/kih8qrnq654qjkypixhrfhlg9p539k19-nixpkgs-unstable-src/nixos/lib/make-options-doc/default.nix:70:60:
while evaluating 'attrByPath' at /nix/store/kih8qrnq654qjkypixhrfhlg9p539k19-nixpkgs-unstable-src/lib/attrsets.nix:24:35, called from /nix/store/kih8qrnq654qjkypixhrfhlg9p539k19-nixpkgs-unstable-src/nixos/lib/make-options-doc/default.nix:61:38:
while evaluating 'attrByPath' at /nix/store/kih8qrnq654qjkypixhrfhlg9p539k19-nixpkgs-unstable-src/lib/attrsets.nix:24:35, called from /nix/store/kih8qrnq654qjkypixhrfhlg9p539k19-nixpkgs-unstable-src/lib/attrsets.nix:29:12:
while evaluating the attribute 'nextcloud18' at /nix/store/kih8qrnq654qjkypixhrfhlg9p539k19-nixpkgs-unstable-src/pkgs/top-level/all-packages.nix:6600:48:
while evaluating the attribute 'nextcloud18' at /nix/store/kih8qrnq654qjkypixhrfhlg9p539k19-nixpkgs-unstable-src/pkgs/servers/nextcloud/default.nix:34:3:
Nextcloud v18 has been removed from `nixpkgs` as the support for it was dropped
by upstream in 2021-01. Please upgrade to at least Nextcloud v19 by
declaring

    services.nextcloud.package = pkgs.nextcloud19;

in your NixOS config.

[1] https://docs.nextcloud.com/server/18/admin_manual/release_schedule.html

If there is anything I can do to help investigate this issue further, please just tell me.

So, on master the nextcloud18-package isn't even listed in relatedPackages, so I guess we can rule this out. I played a little bit around, but couldn't even reproduce the issue. To proceed, it would be awesome to get a minimal way to reproduce this, so ideally:

A nixpkgs (e.g. from nixos-version) rev to use and an expression that I can evaluate with nixos-build-vms(8).
A nixpkgs rev and a minimal configuration.nix I can evaluate to observe the issue.

Thanks!

It took me a while to figure it out, but the problem was due to an inconsistent pinning of nixpkgs/ nixos modules in my configuration. This caused nextcloud18 being used for the documentation while it was already gone.
Sorry for the confusion!


Fixing Win 10 support link

See https://ci.openmicroscopy.org/view/Docs/job/OMERO-DEV-merge-docs/436/warnings3Result/ - this link is registering as broken but it's just delayed and redirecting slightly for me so I'm hoping this URL update will stop the build complaining.

See https://ci.openmicroscopy.org/view/Docs/job/OMERO-DEV-merge-docs/437/ - build now fixed


How to install in angular 2 app?

How to install this plugin into angular 2 application ?

place you plugin.js into assets and include in index.html


Possibility to flash only a partition on a multiple partitionated USB

I have a USB with 2 partition: I want to use one for my stuffs and the other for a LinuxLiveUSB. I like Etcher and I prefer it instead of other softwares, but I can't install an OS only on a partition: Etcher formats all my USB installing the OS on a whole partition. It would be very usefull if I can choose on which partition install the OS (without erease datas from the other, of course ^^)

Hi @mymike00 ,
Keep in mind that Etcher does not partition the drive. As an image flasher, the only thing it does is copy an image to a drive byte by byte, without any transformation. Images contain their own partition table, which means that allowing users to flash an image that comes with multiple partitions to a single partition requires non-trivial transformations and intimate knowledge of what the image represents (e.g. we should hardcode logic for certain Linux distros, etc)
Closing as a duplicate of https://github.com/resin-io/etcher/issues/453.


helm: Add support of servicePort in hubble ui service

Signed-off-by: Nishant Shekhar<EMAIL_ADDRESS>Please ensure your pull request adheres to the following guidelines:

[X] For first time contributors, read Submitting a pull request
[X] All code is covered by unit and/or runtime tests where feasible.
[X] All commits contain a well written commit description including a title,
description and a Fixes: #XXX line if the commit addresses a particular
GitHub issue.
[X] If your commit description contains a Fixes: <commit-id> tag, then
please add the commit author[s] as reviewer[s] to this issue.
[X] All commits are signed off. See the section Developer’s Certificate of Origin
[X] Provide a title or release-note blurb suitable for the release notes.
[ ] Are you a user of Cilium? Please add yourself to the Users doc
[X] Thanks for contributing!

The changes in this PR is for adding support to define servicePort of hubble-ui service.
Fixes: #issue-number
helm: Add support of servicePort in hubble ui service

Travis-CI hit https://github.com/cilium/cilium/issues/27080, re-running.

:wave: hi @nishant221 ! I'll take the liberty to flip this PR to draft, until you had time to address the requested change. Please flip it back when ready, thank you!


Update schema design page

Improves the examples for the sections about encoding data in measurements and tags.

👍


Handle multiple contacts in interaction CSV export

Description of change
This adds a Contacts column to the interaction CSV export, and removes the previous Contact column.
Checklist

[x] Has a new newsfragment been created? Check changelog/README.rst for instructions
[ ] Have any relevant search models been updated?
[ ] Have any relevant fixtures (fixtures/test_data.yaml) been updated?
[ ] Have any relevant select-/prefetch-related field lists in the views and search apps been updated?
[ ] Has the admin site been updated (for new models, fields etc.)?
[ ] Has the README been updated (if needed)?

@reupen looks good to me. :+1: I see you are removing columns in the csv download. Does this need to be communicated to other stake holders that may rely on the csv download prior to the change going live?

@reupen looks good to me. +1 I see you are removing columns in the csv download. Does this need to be communicated to other stake holders that may rely on the csv download prior to the change going live?

Ideally, but I'm not sure there is much of a choice here anyway. I'll mention your concern to the rest of the team.


Feature Request - forced hediff in general settings

Is it possible to have a forcedRaceHediff as part of the general settings in the race?
So every pawn of that race gets the hediff.

You can do that via the races hediffgiver.

I might be missing it - but I can't find the hediffgiver on the wiki

Come on the HAR discord, we will lead you. HediffGiver is a vanilla feature, that's why the wiki does not need to document it.


Add Symfony 4 support -composer level only for now

Hi, still not merged ? :p sorry for spamming you


CORTX-29227: RGW: support bundle should be generated even if config file is missing

Signed-off-by: Palak Garg<EMAIL_ADDRESS>Problem Statement

According to current implementation, rgw support bundle will raise error, if config file is missing.

Design

support bundle should skip the config file if missing, and bundle up other log files present.

Coding
Checklist for Author

[x] Coding conventions are followed and code is consistent

Testing
Checklist for Author

[ ] Unit and System Tests are added
[ ] Test Cases cover Happy Path, Non-Happy Path and Scalability
[x] Testing was performed with RPM

Impact Analysis
Checklist for Author/Reviewer/GateKeeper

[ ] Interface change (if any) are documented
[ ] Side effects on other features (deployment/upgrade)
[ ] Dependencies on other component(s)

Review Checklist
Checklist for Author

[x] JIRA number/GitHub Issue added to PR
[x] PR is self reviewed
[x] Jira and state/status is updated and JIRA is updated with PR link
[x] Check if the description is clear and explained

Documentation
Checklist for Author

[ ] Changes done to WIKI / Confluence page / Quick Start Guide

Tested with custom build: https://eos-jenkins.colo.seagate.com/job/GitHub-custom-ci-builds/job/generic/job/custom-ci/5292
Deployment is successful.
SB is generating for rgw

tar -xvf SBag9s2g01_469f965c135a46859a9f9aff49bf5ec7.tar.gz
SBag9s2g01/
SBag9s2g01/common/
SBag9s2g01/common/common.tar.gz
SBag9s2g01/rgw/
SBag9s2g01/rgw/rgw_SBag9s2g01_469f965c135a46859a9f9aff49bf5ec7_rgw.tar.gz
SBag9s2g01/utils/
SBag9s2g01/utils/SBag9s2g01_469f965c135a46859a9f9aff49bf5ec7_utils.tar.gz
SBag9s2g01/summary.yaml

and rgw support bundle log file will log error if config file is not present

[root@cortx-server-headless-svc-ssc-vm-rhev4-2192 SBag9s2g01]# cat rgw/rgw_support_bundle.log
2022-03-15 08:14:02 rgw_support_bundle [590]: INFO [generate] rgw support bundle generation started!!
2022-03-15 08:14:02 rgw_support_bundle [590]: ERROR [generate] /etc/cortx/rgw/469f965c135a46859a9f9aff49bf5ec7/cortx_rgw.conf is not present.Skipping the config file collection for rgw


fix: headless service as ingress backend

[x] Chart version not bumped (the versions are all bumped and released at the same time)
[.] README.md updated with any new values or changes
n.a.
[x] Updated template tests in ${CHART}/tests/*.py
[.] Updated integration tests in ${CHART}/examples/*/test/goss.yaml
n.a. (doesn't exist for ingress)

Hi all,
I wanted to expose the httpPort of the headless service via ingress, but ran into a bug.
For the ingress backend, the port and service do not match:

Ingress backend port is the httpPort (which is also the port of the headless service)
Ingress backend service is "logstash.fullname" (which equal the name of the ClusterIP service)

In order to expose the httpPort 9600, I needed to change the ingress backend service into:
"logstash.fullname"-headless
Cheers,
Dirc

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

This probably conflicts with:
#1500
I will join the discussion there, since I believe both a ingress for the webapi port and the http plugin port are valuable.

Hi @Dirc, headless service purpose is only for maintaining the network identity of the pods in the statefulset and shouldn't be exposed.
If you need to expose a service, you should create another one using the service value instead of trying to reuse the headless one.

Hi @jmlrt , thanks for explaining. However, I still wonder, why is the httpPort (normally 9600) then the default port for the ingress backend service?