Add serde to Pong struct

Description
Add serde to Pong struct
Notes & open questions
No rush to get this out, I just think this could be useful
Change checklist

[x] Self-review
[ ] Documentation updates if relevant
[ ] Tests if relevant

is there a use case for this? Otherwise I don't think it's of use to include. Not against the change on itself -it seems simple and well implemented-, but there are plenty types that could derive Serialize and Deserialiaze that don't do since there is no need. So, why pong? it's particularly ephemeral

I want to use the struct as the return type for one of our jsonrpsee endpoints which is calls send_ping and returns Pong. I can always just copy paste this struct then .into() what I get from sigp/discv5, but I thought it was clearer and less duplicate code to just add serde here.

could you please check what other public types trin would use in the json rpc to do this in a batch? Easier to understand as a future reader of the git history if they are all added together instead of one by one

Yeah I agree. If we are going to implement a serialize/deserialze trait on our RPC, we should not do it ad-hoc. If we are going to implement on one, we should at least implement it on all.

closing this as stale


tweaks to caching examples

I hit a few speed bumps setting up caching and thought I'd try to improve the docs for future readers.
The examples contained a couple of hazards:

Permitting fallback to another OS's cache: I'm not sure about all the ecosystems on this page, but for Node.js and Nuget, that's asking for trouble.
The Nuget example file pattern (**/package-lock.json) would pick up build artifacts produced during the build, causing warnings like this:

Resolving key:
 - nuget                 [string]
 - "Linux"               [string]
 - **/packages.lock.json [file pattern; matches: 6]
   - s/server.test/bin/Debug/netcoreapp3.1/packages.lock.json --> 54E021E7782D4EDE29CA84D1911D5F12FF6B97E470A37B8653038CAE09D8BD23
   - s/server.test/packages.lock.json                         --> 54E021E7782D4EDE29CA84D1911D5F12FF6B97E470A37B8653038CAE09D8BD23
   - s/server/bin/Debug/netcoreapp3.1/packages.lock.json      --> 3F864CFCD8CD564E66DE7F2D164366BB03FA8A63776B8202A969641AEB63F2A4
   - s/server/packages.lock.json                              --> 3F864CFCD8CD564E66DE7F2D164366BB03FA8A63776B8202A969641AEB63F2A4
Resolved to: nuget|"Linux"|LTuERQLUCYknQUjgQoKH5DbDWg/nzb306f+taO5LRTI=
##[warning]The given cache key has changed in it's resolved value between restore and save steps;
original key: nuget|"Linux"|u2NhonrMrTrArhCNdFbImE1Do+iWcBhBroeJjLccvXQ=
modified key: nuget|"Linux"|LTuERQLUCYknQUjgQoKH5DbDWg/nzb306f+taO5LRTI=

@jrr : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#reassign ramimsft

#sign-off


Extra bullet points in "Polymorphic Variant" documentation

Fyi, there are two extra bullet points on this page:
https://rescript-lang.org/docs/manual/latest/polymorphic-variant
On the above page, there is an extra bullet point above each of the following items:

It's also harder to refactor poly variants. Consider this:
You might lose some nice pattern match checks from the compiler:

If you don't see the extra bullet points in your browser, please let me know and I will attach a screen shot.
The source for the above page seems to be here:
https://github.com/rescript-association/rescript-lang.org/blob/master/pages/docs/manual/latest/polymorphic-variant.mdx
The extra bullet points do not appear in the source when viewed on Github.
Maybe the extra bullet points are the result of a glitchy Markdown converter somewhere in the production chain?
Given that the extra bullet points do not appear when the page is viewed at Github, I am not able to submit a PR.

I think the trick is to not make any newline inbetween bullet points. There's currently some Markdown logic bug that will interpret the newline weirdly


@jest/types differs from @types/jest causing typing conflicts

🐛 Bug Report
See Title
To Reproduce
Not exactly sure, but in my case it must have been an update and I'd already been using the old types.
Expected behavior
I preferred the @types/jest as their test function has the third time out argument, which caused the error.
Link to repl or repo (highly encouraged)
Here is the types repo.

I don't think you're supposed to use @jest/types right now. It's mostly used for internal typing of the packages within jest. @types/jest is for developers who mostly want typing for jest in vscode

Correct, @jest/types is internal. We'll add types to the jest package once we're ready, no need to add a separate typings package

Is this still accurate? The docs currently instruct you to use @jest/types in jest.config.ts:
// jest.config.ts
import type {Config} from '@jest/types';

// Sync object
const config: Config.InitialOptions = {
  verbose: true,
};
export default config;

// Or async function
export default async (): Promise<Config.InitialOptions> => {
  return {
    verbose: true,
  };
};

Is this still accurate? The docs currently instruct you to use @jest/types in jest.config.ts:
// jest.config.ts
import type {Config} from '@jest/types';

// Sync object
const config: Config.InitialOptions = {
  verbose: true,
};
export default config;

// Or async function
export default async (): Promise<Config.InitialOptions> => {
  return {
    verbose: true,
  };
};


Contribute Logistic Regression

In the repository multiple machine learning techniques are verified. Therefore, application of Logistic Regression should be a good contribution. For further details take a look at the following resources:

SKLearn: LR
LR

Create a well documented .ipynb file detailing your implementation.

I would like to contribute to this problem statement!

Sure just make sure its Logistic Regression only and not a complex networks

Cool!


Double next/prev arrow on blog post

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Prerequisites

[X] I'm using the latest version of Docusaurus.
[X] I have tried the npm run clear or yarn clear command.
[X] I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
[ ] I have tried creating a repro with https://new.docusaurus.io.
[X] I have read the console error message carefully (if applicable).

Description
In the latest release, there are two arrows on the next/prev element on the blog:

This can also be reproduced here:
https://docusaurus.io/blog/2021/11/21/algolia-docsearch-migration
The arrow is once inserted as HTML element and once as :after element with the content attribute.
Steps to reproduce
See above
Expected behavior
Only one arrow instead of two
Actual behavior
Two arrows
Your environment

Public source code:
Public site URL:
Docusaurus version used:
Environment name and version (e.g. Chrome 89, Node.js 16.4):
Operating system and version (e.g. Ubuntu 20.04.2 LTS):

Reproducible demo
No response
Self-service

[ ] I'd be willing to fix this bug myself.

The fix would be easy, but it would be related to our theme designing approach. @slorber should we make DocPaginatorNavLink a generic PaginatorNavLink component, or should we just make another BlogPaginatorNavLink component? I prefer the former

👍 for PaginatorNavLink
We should start to implement our own typesafe theme design system (+ storybook + Chromatic) instead of using Infima classes everywhere, and this component is a good first candidate as it is used in multiple places
See also https://github.com/facebook/docusaurus/issues/6116


openSUSE Leap has it's own platform name

This is a unique platform in the suse platform family

Related ohai issue: https://github.com/chef/ohai/pull/784


Nothing in the Thunderbird Setup 68.7.0

There's nothing in the Thunderbird Setup 68.7.0.
Desktop (please complete the following information):
OS: Win7 x64

This is because the firefox and thunderbird msi files are just a wrapper around the .exe file.
If you want any files from thunderbird, just download the exe file and extract with 7zip.

@jjurkus Thanks, I got it.


⚠ Samsung has degraded performance

In 913a9fe, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2302 ms

Resolved: Samsung performance has improved in 50898e5.


fix: Fix warning about redefining STDC_HEADERS

Closes #834

Codecov Report

Merging #835 (5c9f730) into master (79d692c) will increase coverage by 3.81%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #835      +/-   ##
==========================================
+ Coverage   73.14%   76.95%   +3.81%
==========================================
  Files          17       13       -4
  Lines        3281     2526     -755
==========================================
- Hits         2400     1944     -456
+ Misses        881      582     -299

Impacted Files
Coverage Δ

src/base/mutex.h
100.00% <0.00%> (ø)

src/raw_logging.cc
100.00% <0.00%> (ø)

src/windows/dirent.h

src/windows/port.cc

src/windows/port.h

src/stacktrace_unwind-inl.h

src/demangle.cc
97.50% <0.00%> (+0.02%)
:arrow_up:

src/signalhandler.cc
6.76% <0.00%> (+0.31%)
:arrow_up:

src/glog/logging.h.in
80.64% <0.00%> (+0.64%)
:arrow_up:

src/utilities.cc
69.00% <0.00%> (+1.35%)
:arrow_up:

... and 3 more

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 79d692c...5c9f730. Read the comment docs.

Thanks!


MinDate, MaxDate is not working in Month Range Picker

I have a month range component below:
<DatePicker
className="react-datepicker-wrapper"
selected={this.state.startDate}
startDate={this.state.startDate}
endDate={this.state.endDate}
maxDate={this.state.endDate}
showMonthYearPicker
onChange={(date) => onChange(date, 'startDate')}
/>
I found that maxDate is not working in only month range mode.
Please to help me resolve this issue.

Hi @caothuphu2013 It should ideally work, there was another issue like this which was resolved:
https://github.com/Hacker0x01/react-datepicker/issues/1685
Can you please create a JSFiddle of your use case and share it with us?
Thanks

I can confirm, it is still not working for month picker

@bakaa99 Can you please share a codepen or JSFiddle of what you are doing.

I don't know how to include libraries in there. This is component i am using all across my app. It works fine as when using as a datepicker, when i use it for months , the min and max does not work
<DatePicker
            id={id}
            autoComplete="off"
            dateFormat={showMonthYearPicker ? "yyyy/MM" : "yyyy/MM/dd"}
            showMonthYearPicker={showMonthYearPicker || false}
            placeholderText={placeholder}
            disabled={disabled}
            className={`${error && 'is-invalid'} form-control border-right-0`}
            openToDate={openToDate}
            defaultValue={value}
            value={value}
            minDate={minDate ? minDate : new Date()}
            maxDate={maxDate ? maxDate : null}
            readOnly={readOnly}
            required={validationRules.isRequired}
            // shouldCloseOnSelect={true}
            onSelect={(value) => handleChange(value, id)}
            onChange={(value) => handleChange(value, id)} />

Can you check this:
https://codesandbox.io/embed/peaceful-water-0kzlf

Check this: https://codesandbox.io/s/peaceful-water-0kzlf

i does work when both minDate and maxDate are defined,not when only minDate is defined.I don't want maxDate, only minDate

@bakaa99 I updated the same sandbox to your use case and that's working as well, can you check?

@gautam-pahuja it'll not work if you change the month, i tried and it wasn't working for me.

@gautam-pahuja were you able to reproduce the issue? do you need any more info from my side?

Yes, please. A GIF of what you are trying to do would be nice.

@gautam-pahuja , my requirement is very simple . I should be able to set minDate without a maxDate. I want to set the current month as minimum, so that user should not be able to select any previous month.

Finally, This issue has not been resolved

I fixed this issue. You can see by: https://github.com/Hacker0x01/react-datepicker/pull/1805

After lots to r&d I found the solution for set minDate and maxDate properly for DatePicker component.
It accept only "yyyy-MM-dd hh:mm:ss" format and also it is must be java script 'Date' object. moment type is not supported for minDate and maxDate.
eg.
maxDate = {moment(this.props.maxDate).toDate()}
minDate= {moment(this.props.minDate).toDate()}
or
maxDate = {new Date("2020-05-25")}
minDate = {new Date("2010-05-25")}
These are 100% succeed formats. I am using it.
I hope it will help some one to fix their issue. You don't need to write any validation any more for selected value. Handle it on UI layer of your product. :)

If someone needs to set the date min for today, you can do it this way
`const DatePickerInput = () => {
const [startDate, setStartDate] = useState(new Date());
return (
<DatePicker
showWeekNumbers
selected={startDate}
onChange={(date) => setStartDate(date)}
locale="en-gb"
minDate = {new Date(startDate)}
placeholderText="Weeks start on Monday"
	/>
);

};`

I just ran into the same issue when using Luxon.DateTime as input to the picker.
Solution: Always use toJSDate() when providing values to the picker, and transform its returns back to DateTime with fromJSDate. Easy.


Add logging on shared.Prtintf calls

Signed-off-by: Łukasz Gryglicki<EMAIL_ADDRESS>

main changes in log.go firehose changes are just go fmt and Makefile changes are due to firebase being in a separate dir so go vet/imports/errcheck etc cannot work with all files at one - it needs to check top-level first and then firehose/ - seems like somebudy who upaded this module didn't check in make works with current Makefile cc @fayazg


Fix link direction

Currently adding something to the top of mind links the new thought to the preceding one, like this:
Tom 1

^
|

Tom 2

^
|

Tom 3

...

I think it should be the opposite direction -- you start on the outside and link to increasingly centralized thoughts.

We now link the most recent top of mind thought to the incoming thought, whether it is user-written or pulled in from the stream. It is done at the provider level:
https://github.com/mind-co/comind/blob/73ba9a996372f5560ca5f506e9c4a3edb9c139c9/lib/stream.dart#L642-L645
and
https://github.com/mind-co/comind/blob/d6c841332d9124a93c79dc1f7e067a923611ed35/lib/providers.dart#L217-L224


Spending password ui fixs

closes #324

38

Error when building "The document "Main.storyboard" could not be opened. Multiple elements have the ID "dPx-ZI-D15"

This issue is fixed in #347.


[HUDI-365] Refactor hudi-cli based on new ImportOrder code style rule

Tips

Thank you very much for contributing to Apache Hudi.
Please review https://hudi.apache.org/contributing.html before opening a pull request.

What is the purpose of the pull request
To refactor hudi-cli based on new ImportOrder code style rule
Brief change log

Modify ImportOrder based on checkstyle rule in checkstyle.xml

Verify this pull request
(Please pick either of the following options)
This pull request is a trivial rework / code cleanup without any test coverage.
Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

👍

@yanghua could you review this one please


Not working with Angular.js?

This is a cool addon for Leaflet!
After playing around with it using Angular.js, I could only get it to work with spinner.js using:
      var loadingControl = L.Control.loading({
          spinjs: true
      });
      map.addControl(loadingControl);

But I much prefer the image you use, and not spinner.js. I am wondering if something in Angular is tripping up the normal initialization of this control?
If you have any ideas I would be happy to poke around and create a pull request if I can get it fixed.

@F1LT3R I'm not aware of anything Angular-specific that would stop this from working but I'd appreciate a small example if you have one.
Are you setting the CSS to make the image show up? See the examples for details, specifically these lines.

Just to advise I have this working in angularjs with the default icon showing as expected.

Thanks @MarkAPhillips, you didn't have to do anything special did you? If not I think I'll close this, but let me know.

Sorry for not coming back to this earlier - I did not do anything different and had the basic functionality working with the default icon as expected. I did though later decide to change to another plugin as this worked better in the angularjs application I was creating but was more down to personal choice and also as I could not get the icon to show correctly all the time for different events.
I decided to use  http://makinacorpus.github.io/Leaflet.Spin/  which I found easier to plug in to my application

Closing this as there doesn't seem to be anything to do from this side, please open it back up if I am wrong.


Caching Purge

Allow users to purge their cache automatically via the dashboard

We added a cache seed which should suffice: https://docs.helicone.ai/features/advanced-usage/caching#adding-cache-seed


Hierarchical Tag Helper binding

Summary
This feature would add support for directly binding Tag Helper properties to child Tag Helper instances from the source document, thus making it much simpler to author related Tag Helpers that are designed to work together in a hierarchy.
Background
Today, we provide a number of features to assist with authoring sets of Tag Helpers that are intended to be used together in a logical hierarchy, including:

RestrictChildrenAttribute to restrict which tags are valid as children of the element a Tag Helper instance is attached to
HtmlTargetElementAttribute.ParentTag to restrict which tag is valid as a parent of an element a Tag Helper instance is attached to
TagHelperContext.Items to allow passing of data between different Tag Helpers attached to the same element, and between Tag Helpers attached to an element and Tag Helpers attached to that element's children

The use of TagHelperContext.Items to pass data between related Tag Helpers is somewhat cumbersome, e.g.:
public class ParentChildContext
{
    public string SomeData { get; set; }
}

[RestrictChildren("child")]
public class ParentTagHelper : TagHelper
{
    private ParentChildContext _context;

    public override void Init(TagHelperContext context)
    {
        _context = new ParentChildContext();
        context.Items.Add(typeof(ParentChildContext), _context);
    }

    public override async Task ProcessAsync(TagHelperContext context, TagHelperOutput output)
    {
        // Force children to process
        var childContent = await output.GetChildContentAsync();

        // Read context data set by child here
        // _context.SomeData
    }
}

[HtmlTargetElement("child", ParentTag = "parent", TagStructure = TagStructure.WithoutEndTag)]
public class ChildTagHelper : TagHelper
{
    public string SomeData { get; set; }
    public override void Process(TagHelperContext context, TagHelperOutput output)
    {
        var parentContext = context.Items[typeof(ParentChildContext)];
        parentContext.SomeData = SomeData;
    }
}

<parent>
    <child some-data="This will be accessible to the parent" />
</parent>

Proposal
Tag Helper property binding would be expanded to support directly binding Tag Helper instances to properties on a Tag Helper using Tag Helpers attached to the current element's children as the source.
Binding will:

Support the binding of any type that implements ITagHelper

In the case where multiple children of the matching type are present, the first instance will be bound

Support the binding of IEnumerable<T> where T : ITagHelper to enable simple access to multiple child Tag Helper instances of the same type

When the binding applies, it will always create and set an IEnumerable<T> instance to the property, irrespective of the property's initial value (i.e. it will overwrite any current value of the property)

Bind only the first level of children (i.e. it would not perform a "deep" or "recursive" bind)
Only support binding to public settable properties (like other bindings)
Be implied (i.e. automatic) based on the property being public and the type being derived from ITagHelper

Review: Should this be opt-in via a new attribute rather than implied?

Support being disabled via HtmlAttributeNotBoundAttribute on the property that would otherwise be bound

Example
Here is the example from above reimplemented with the proposed behavior implied:
[RestrictChildren("child")]
public class ParentTagHelper : TagHelper
{
    public ChildTagHelper Child { get; set; }

    public override async Task ProcessAsync(TagHelperContext context, TagHelperOutput output)
    {
        // Force children to process
        var childContent = await output.GetChildContentAsync();

        // Read data directly from child here
        // Child.SomeData
    }
}

[HtmlTargetElement("child", ParentTag = "parent", TagStructure = TagStructure.WithoutEndTag)]
public class ChildTagHelper : TagHelper
{
    public string SomeData { get; set; }
}

<parent>
    <child some-data="This will be accessible to the parent" />
</parent>

More Examples
/// <summary>This Tag Helper applies to all elements and effectively creates a server-side DOM, albeit with a single, forward-only pass rather than being stateful.</summary>
[HtmlTargetElement("*")]
public class DomTagHelper : TagHelper
{
    public DomTagHelper Parent { get; set; }

    public IEnumerable<DomTagHelper> Children { get; set; }

    public override void Init(TagHelperContext context)
    {
        // Set parent on all children
        foreach (var child in children)
        {
            child.Parent = this;
        }
    }

    public override async Task ProcessAsync(TagHelperContext context, TagHelperOutput output)
    {
        // Run children
        var childContent = await output.GetChildContentAsync();

        //
    }
}

Thanks for contacting us. We're closing this issue as there was no community involvement here for quite a while now.


[BugFix] Fix bug which cause storage volume is shown unexpectedly

Why I'm doing:
The system database information_schema and sys  is not bind to storage volume. But in show create db statement, it will show it has been bind to storage volume.
mysql> show create database information_schema;
+--------------------+-----------------------------------------------------------------------------------------------+
| Database           | Create Database                                                                               |
+--------------------+-----------------------------------------------------------------------------------------------+
| information_schema | CREATE DATABASE `information_schema`
PROPERTIES ("storage_volume" = "builtin_storage_volume") |
+--------------------+-----------------------------------------------------------------------------------------------+
1 row in set (0.00 sec)

What I'm doing:
Fix bug which cause storage volume is shown unexpectedly.
mysql> show create database information_schema;
+--------------------+--------------------------------------+
| Database           | Create Database                      |
+--------------------+--------------------------------------+
| information_schema | CREATE DATABASE `information_schema` |
+--------------------+--------------------------------------+
1 row in set (0.01 sec)

Fixes #issue
What type of PR is this:

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

[ ] This is a backport pr

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.2
[x] 3.1
[ ] 3.0
[ ] 2.5

backport 3.1: https://github.com/StarRocks/starrocks/pull/42057


Cannot add the same file I want to upload after clicking the red trash can button

I cannot upload the same file after I find the file I want to upload in File Explorer and click the red trash can button to remove it.
The specific scenario is as follows:

Click "Drop Files Here" and add a file you want to upload
Click the red trash can button to delete it
Click "Drop Files Here" again and add the same file

The third step fails.

related to #2134


vBump ScriptDom version for sql projects

Updated from 161.8817.2 to 161.8910.0 version

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.001%) to 41.758%

Files with Coverage Reduction
New Missed Lines
%

src/sql/workbench/services/connection/browser/connectionDialogWidget.ts
1
73.44%

Totals

Change from base Build<PHONE_NUMBER>:
-0.001%

Covered Lines:
30827

Relevant Lines:
69082

💛  - Coveralls


Sign in to confirm you’re not a bot. This helps protect our community. Learn more

This is happening on hetzner server.
passing cookie works for 2 min & again ask the same question.
Any way to by pass this.
    const videoInfo = await retryOperation(() => youtubedl(url, {             dumpSingleJson: true,             cookies: './cookies.txt'         }));

Try using yt-dlp --help, I guess you can pass cookies using --add-headers


Detect lua 4911 v3

Includes test for LuaMatchTest01-LuaMatchTest06
Link to redmine ticket: https://redmine.openinfosecfoundation.org/issues/4911
Previous PR: https://github.com/OISF/suricata-verify/pull/1086

I seem to have messed up my commit history and I'm not sure how to fix it. Do I create another branch?

I seem to have messed up my commit history, I can't seem to squash the commits and I'm not sure how to fix it. Do I create another branch?

That is the easier, cleaner, and safer way - also useful for the next PR, as you keep different branch versions :P
If you are feeling adventurous, though, you can rework your history with an interactive rebase: git rebase -i HEAD~numberofcommitstoorganize. This can be messy when we're not used to it, so I recommend you create a new branch for that in any case, to practice a bit, if you are not familiar with it.

Replaced With  #1242


fix: patch for 1.5.1

re-includes the test-helper directory in the npm build for txwrapper-core.

reverts #175

Any ETA on when this will be merged/published?

@lcovar @byhow Publishing right now

1.5.1 is published


Issue when trying to set filePathRoot with relative path

Hello,
I read in the documentation that relative path were possible for filePathRoot
_'Note:'' All paths can be either absolute or relative. Relative paths are relative to the folder with tiddlywiki.js in it if you are using the plugin version or the folder with the executable file if you are using the BobEXE version.
''Note for windows:'' All the example paths here are how they would appear on linux or osx. On windows the paths would look like C:\Users\inmysocks\TiddlyWiki\Wikis. To make the examples what you would use in windows replace /home with C:\Users and change the / into ._
When trying to have path like ."/Wikis" or "Wikis" either through the UI or directly modifying settings.json I'm getting an error message (see hereafter) and $__WikiSettings.tid is not updated.
By the way stuff is working correctly even when entering an absolute path (even if this path does not exist on my file system)
PS1: Congratulation for the job you are doing on Bob !!!
WebSocket error, probably closed connection:  TypeError: Cannot read property 'RootWiki' of undefined
at Object.$tw.CreateSettingsTiddlers ($:/plugins/OokTech/NodeSettings/NodeSettings.js:121:18)
at Object.$tw.nodeMessageHandlers.browserTiddlerList ($:/plugins/OokTech/Bob/NodeMessageHandlers.js:47:9)
at WebSocket.$tw.Bob.handleMessage ($:/plugins/OokTech/Bob/NodeWebSocketsSetup.js:157:50)
at emitOne (events.js:116:13)
at WebSocket.emit (events.js:211:7)
at Receiver.receiverOnMessage ($:/plugins/OokTech/Bob/External/WS/lib/websocket.js:720:20)
at emitOne (events.js:116:13)
at Receiver.emit (events.js:211:7)
at Receiver.dataMessage ($:/plugins/OokTech/Bob/External/WS/lib/receiver.js:415:14)
at Receiver.getData ($:/plugins/OokTech/Bob/External/WS/lib/receiver.js:347:17)
new connection
Make sure you read contributing.md and check the correct boxes below and then
add your issue text here.
If you don't than the issue will be tagged as spam and closed or deleted.

I am running (check any that apply, put an x inside the [ ] to check a box, like this: [x]):

[ ] Windows
[x] OSX
[ ] Linux
[ ] Other

and using

[x] The nodejs version
[ ] The single file executable

Before posting I read issue guidelines and:

[x] I am using the newest version
[x] The answer to my question isn't listed in the documentation or this isn't
a question
[x] This is not a duplicate issue
[x] I have not done anything that required me to set acceptance to
I Will Not Get Tech Support For This

This is my impression too. That the pathing for "filePathRoot" currently has to be absolute; relative does  not seem to work. Otherwise Bob is fully portable.
I'm on Bob.EXE on Windows 7 in Firefox 52 ESR, both 64.


Connectors without ISE label

'Connectors that don't display the ISE label run in the global Logic Apps service.'
Does this mean they will be charged on the normal consumption based charge just as if the LA was outside the ISE?
Rather than being part of the ISE executions?

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

ID: 63815982-c91f-8078-f89d-af3a89dda954
Version Independent ID: 0ffd6861-b0df-a675-6b56-16542c2ef0e5
Content: Pricing & billing model - Azure Logic Apps
Content Source: articles/logic-apps/logic-apps-pricing.md
Service: logic-apps
GitHub Login: @kevinlam1
Microsoft Alias: klam

Hi @gavinhow Thanks for reaching out. We will review and update as appropriate.

If the logic app is running in the ISE then there will not be any action execution charges regardless of what type of connector or where it runs.


Update docs

Add documentation for HTTP bundles. (#75)
Add an example unit test for using bundle files.
Fix IDE warning about unused local variable.
Update benchmarks for .NET Core SDK 2.2.105 and version 2.0.0 of the code base.

Codecov Report

Merging #79 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #79   +/-   ##
=======================================
  Coverage   98.94%   98.94%
=======================================
  Files          12       12
  Lines         947      947
  Branches      150      150
=======================================
  Hits          937      937
  Partials       10       10

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 b60b750...e8a9a6c. Read the comment docs.


Email compliance

https://help.mailgun.com/hc/en-us/articles/20263554449179-Enhancing-Email-Compliance-A-Guide-To-The-2024-Gmail-And-Yahoo-Changes-For-Optimal-Deliverability

DMARC set up


Missing image lists

Thank you for the great code base!
I was hoping to replicate your results, but found that the image lists in your train prototxt are not in the repo anywhere: https://github.com/janesjanes/sketchy/blob/master/training/Triplet_googlenet_train_test.prototxt - would you mind sharing these?  Thank you!

i'm also interested in this 👍

I am also looking for the list!

I found the test set list in "Annotation and Info" link in the official website of Sketchy.
Download URL: https://goo.gl/rn6XGx
You can exclude the test set images from the database to get the training images.

I found the test set list in "Annotation and Info" link in the official website of Sketchy. Download URL: https://goo.gl/rn6XGx You can exclude the test set images from the database to get the training images.

Hello, excuse me, can you please share the sketchy dataset? Thank you!


starter-template can't npm install, 1error

components/Logo.vue dependency was not found /
i npm install this file again,   but failed again, anyone knows how to fix it??? thanks

Hi @winterfall1121
I updated the starter template, please re-install it.


GUACAMOLE-55: Add interface-level support for image clipboard contents

This change implements a new directive, guacClipboard, which provides support for image clipboard contents in addition to text. All clipboard contents intended for (or coming from) this directive are communicated via the data property on the scope as ClipboardData objects. These objects are also consumed and produced by the clipboardService which has been refactored to support them. All of these objects, services, etc. have been collected together into their own "clipboard" module.

Closing this until we can resolve the latest ridiculous quantity of browser-specific issues.


post-install causing more noise in yarn pnp

Environment
Using yarn 2 -- the plug n play system -- will result in an "unplugged" installation of styled-components because of the postinstall script. This script is not necessary for projects to run that are including styled components. It's been altered and even removed before, but keeps making its way back in.
Reproduction
Run yarn 2 in pnp mode and you will see at least one copy of styled-components in .yarn/unplugged.
Expected Behavior
styled-components should not need to be unplugged nor run a postinstall script.

For yarn 2 users, you can just disable .yarnrc.yml to disable postinstall scripts:
enableScripts: false


events_order of RSSAgent when defining an array of urls

Hi,
it is possible to define multiple urls for the RSSAgent. In this case the RSS urls are parsed one after one.
However I want to get a misced output for further processing sorted by publication date. Ok, so I've set the events_order key, but it only effects events created by the SAME url.
Do you have any solution? What am I doing wrong?
Thanks,
hunhejj

Hey @hunhejj, you're not doing anything wrong, I think that's a bug.  Would you mind seeing if #1079 fixes this for you?

Thanks for the quick reply @cantino! Honestly I'm not sure how to apply the fix. Where can I access the event source files if I'm using Heroku?

You'd need to checkout the rss_agent_sorts_all_events git branch locally, then push it to Heroku.  It'd be something like:
git pull
git checkout rss_agent_sorts_all_events
git push heroku rss_agent_sorts_all_events:master

I did the steps you've wrote, but I got the following error message:

! [rejected]        rss_agent_sorts_all_events -> master (non-fast-forward)
error: failed to push some refs to 'https://git.heroku.com/(...).git'
hint: Updates were rejected because a pushed branch tip is behind its remote
hint: counterpart. Check out this branch and integrate the remote changes
hint: (e.g. 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.


[ENHANCEMENT] Reduce default line width, more subtle hover state

Description
Default line width seems large so I adjusted and tweaked the hover state (since reducing the line width made a higher opacity necessary).
Screenshots
https://happo.io/a/1009/p/1488/compare/3f92d334f907c3d2042ed5d458a4005640053100/7dc3820d9d773be4f172187f6790037fa4553178
Before

After

Checklist

[x] Pull request has a descriptive title and context useful to a reviewer.
[x] Pull request title follows the [<catalog_entry>] <commit message> naming convention using one of the
following catalog_entry values: FEATURE, ENHANCEMENT, BUGFIX, BREAKINGCHANGE, DOC,IGNORE.
[x] All commits have DCO signoffs.

UI Changes

[x] Changes that impact the UI include screenshots and/or screencasts of the relevant changes.
[x] Code follows the UI guidelines.
[x] Visual tests are stable and unlikely to be flaky.
See Storybook
and e2e docs for more details. Common issues
include:

Is the data inconsistent? You need to mock API requests.
Does the time change? You need to use consistent time values or mock time utilities.
Does it have loading states? You need to wait for loading to complete.

Hi Steven, to be honest I don't see the difference 😅 reviewing on mobile right now. But lgtm anyway

Haha it’s subtle, you can tell a little more when you hover but maybe I should have adjusted the values more 🙃

Ah yeah, just tried the happo on my big screen and I see now. Let's merge this no brainer :)


Webpack overwrites custom objects passed into resolve.unsafeCache

Bug report

When upgrading from Webpack 4 to Webpack 5, we identified an issue where custom Proxy cache objects passed into resolve.unsafeCache are overwritten by the removeOperations function. This function is executed recursively on resolve options, transforming the Proxy cache into a plain, empty object right before the options are utilized by the enhanced-resolve library.
In enhanced-resolve, we should be able to pass a boolean or an object to unsafeCache. Passing an object allows it to serve as the cache directly. This functionality is crucial for maintaining custom caching logic in complex projects.
What is the current behavior?
The custom Proxy cache object is replaced with a plain, empty object due to the recursive execution of removeOperations.

Steps to Reproduce

Implement a custom Proxy object for caching in Webpack 5's resolve options. For example, this configuration invalidates the cache if the file does not exist on disk:

const fileSystemAwareCache = new Proxy({},{
    get(target, key, receiver) {
        const entry = Reflect.get(target, key, receiver);
        if (entry && fs.existsSync(entry.path)) {
            return entry;
        }

        Reflect.deleteProperty(target, key);
        return undefined;
    },

    set(target, key, value, receiver) {
        return Reflect.set(target, key, value, receiver);
      }
});

// and in our config:
resolve: {
    unsafeCache: fileSystemAwareCache,
}

Observe that upon startup, the custom Proxy is utilized, but once a file is renamed and a server is running, the cache entry is sourced from an unexpected location, bypassing the custom Proxy.

I've created a minimal reproducible example here: https://github.com/jpbriggs408/Webpack-UnsafeCache-ModuleBuildError-Repro.
What is the expected behavior?

The custom Proxy cache object should be consistently used for caching across all operations, maintaining its integrity and functionality throughout the Webpack resolution process.
Possible Solutions

Consider revising the handling of objects passed to resolve.unsafeCache to preserve custom caching mechanisms.
Rather than preventing the issue at the source, another approach is to allow developers to intervene or correct the cache's state dynamically, exposing a way to recover when using resolve.unsafeCache
Amending the cache key used in enhanced-resolve is a potential solution, though this has not been explored in depth.
Investigating the use of module.unsafeCache with a function to re-resolve requests dynamically for non-existent modules.

Notes
Enabling filesystem caching and disabling resolve.unsafeCache re-gains some lost perf benefits, though ideally, we should be able to have both. In our (extremely large) monorepo, the overhead of the filesystem check is minimal and having both options is a clear perf benefit. This actually makes Webpack 5 with filesystem caching only marginally slower for us in dev than our Webpack 4 version with the above simple filesystem check enabled for the resolver cache. Also, special thanks to @joebeachjoebeach for helping connect the final dots with this investigation!
Other relevant information:
webpack version:   5.89.0
Node.js version: 16.13.2
Operating System: CentOS 7
Additional tools: N/A
Previous Context
I previously opened a GitHub Discussion when I began this investigation.
TL;DR Summary
We've discovered an issue in Webpack 5 where custom Proxy cache objects specified in resolve.unsafeCache are overwritten by the removeOperations function in cleverMerge.js. This function's recursive operation on resolve options transforms our Proxy cache into a plain, empty object, just before being passed to enhanced-resolve. Despite enhanced-resolve's capability to use an object directly as the cache, this behavior negates the utility of custom Proxy caches, affecting developers working on complex projects.
We're seeking insights on preserving custom caching logic within Webpack's ecosystem. Feedback and suggestions would be greatly appreciated to navigate and “resolve” this challenge.
Thanks in advance!

I see your problem

I found two solution:

in convertToResolveOptions:

const unsafeCache = options.unsafeCache;
const normalizedOptions = removeOperations(
  resolveByProperty(options, "byDependency", dependencyType)
);
if (unsafeCache !== undefined) {
  normalizedOptions.unsafeCache = unsafeCache;
}

return normalizedOptions;

This is not a universal solution, we assume that only there a proxy can be used for unsafeCache

Implement const removeOperations = (obj, ignoredKeys = []) => { /* ... */ } and so put unsafeCache in ignoredKeys, so keep them as is without deep merging

Make Proxy to be VALUE_TYPE_ATOM in getValueType, but it is only for Node.js, so if somebody will want to bundle webpack for browser, it will not work

const getValueType = value => {
	if (value === undefined) {
		return VALUE_TYPE_UNDEFINED;
	} else if (value === DELETE) {
		return VALUE_TYPE_DELETE;
	} else if (util.types.isProxy(value)) {
		return VALUE_TYPE_ATOM;
	} else if (Array.isArray(value)) {
		if (value.lastIndexOf("...") !== -1) return VALUE_TYPE_ARRAY_EXTEND;
		return VALUE_TYPE_ATOM;
	} else if (
		typeof value === "object" &&
		value !== null &&
		(!value.constructor || value.constructor === Object)
	) {
		return VALUE_TYPE_OBJECT;
	}
	return VALUE_TYPE_ATOM;
};

All solutions works with your repo. But yeah, that is intresting problem, because we use getValueType in many places, and so these places will not work with Proxy
Want to get some feedback from you

Another solution like 3. but we can make it smarty:
if (util.types.isProxy(value) || value.__isProxy) {
}

and
fileSystemAwareCache.__isProxy = true;

so it give ability to mark Proxy in a browser

Thank you for the quick response!
Options 1 and 2 seem like the safest immediate fixes with minimal impact, though we acknowledge they might not cover all future scenarios.
Option 3 (and its browser-compatible variant) do offer a more universal fix. It does seem like the most ideal solution to our specific problem. However, our main concern revolves around potential side-effects across other getValueType usages. It would be great to know more about the specific operations removeOperations aims to exclude from your perspective. That would help us to gauge this option's viability better. That being said, we only pass in our custom cache object in the development environment, but browser compatibility is important to us.

see if this helps
const fileSystemAwareCache = new Proxy({}, {
get(target, key, receiver) {
if (key in target) {
const entry = target[key];
if (entry && fs.existsSync(entry.path)) {
return entry;
} else {
delete target[key];
}
}
return undefined;
},
set(target, key, value, receiver) {
    target[key] = value;
    return true;
}

});

@jpbriggs408 There is a fix https://github.com/webpack/webpack/pull/18152/, I decide to avoid proxy check, because it is not universal (we can't undestand when it is a plain object or a proxied object, except node.js utils ), so let's just keep unsafeCache as is and avoid the object creation

@alexander-akait thank you so much! I think this solution makes a lot of sense.
If documentation needs to be updated, I'm happy to take a crack at it. Let me know, and thanks again!

I don't thank we need document it, because it is like a bug

Totally reasonable! In webpack's documentation, it isn't clear that an object can be passed, but that is outlined in enhanced-resolve's code which is sufficient enough to me.

@alexander-akait thank you for this fix, we really appreciate it! Would we be able to get a release cut with this fix in it at your convenience?

Yeah, this week


Caching data response for complete event parsing

Buffer
Add buffer in parser to store parts of the messages that are not complete, as mentioned in https://github.com/Recouse/EventSource/issues/19
Now parser would store received data parse full messages and retain remaining of the message to parse with next chunk
If the connection closes and buffer is not empty events are not processed, this behaviour is according to the SSE documentation

If the file ends in the middle of an event, before the final empty line, the incomplete event is not dispatched.

Thread safety
To provide thread-safe access to buffer, parser is isolated to an actor.
Test Cases Adjustments:

Tests/EventSourceTests/EventParserTests.swift: Modified test cases to support asynchronous parsing by updating the parse method calls to use await. Added new test cases to handle incomplete and separated messages. [1] [2] [3] [4] [5] [6] [7] [8]

Typo
Fixed a typo in the sessionDelegateTask variable name. [1] [2] [3] [4]

Thank you for the contribution, this is a great improvement to the package!


pretrain llava1.6?

I saw a mention that this repo has been upgraded to llava 1.6, is it possible to pretrain a llava 1.6 based on llama 3 ?

I saw a mention that this repo has been upgraded to llava 1.6, is it possible to pretrain a llava 1.6 based on llama 3 ?

Hi, I am sorry for the late reply. Currently, it only supports the multi-resolution inference. I have not tried to reimplement the multi-resolution training. If you are interested in this, you can follow https://github.com/arielnlee/LLaVA-1.6-ft/tree/main to fine-tune LLaVA-v1.6. Welcome to submit a PR to my repo.


[BUG] RockyLinux/Centos PVC never gets Healthy

Describe the bug
PVCs never reach healthy stage and cause pods to terminate and retry.
To Reproduce
Steps to reproduce the behavior:

Deploy K3S on RockyLinux 8 or Centos 8.
Yaml install Longhorn from kubectl apply -f https://raw.githubusercontent.com/longhorn/longhorn/master/deploy/longhorn.yaml
Deploy PVC/Deployment
Watch the churn

Expected behavior
It should  not churn. The exact same stack works on Ubuntu. I have double checked selinux if off.
Log or Support bundle
Not sure where to check other than the longhorn-manager pod. This stands out :
time="2022-01-06T16:17:58Z" level=warning msg="pvc-0b3e0e06-32a9-4ef6-aa55-b308539d54cb-r-735b2083: time=\"2022-01-06T16:17:09Z\" level=info msg=\"Opening volume /host/var/lib/longhorn/replicas/pvc-0b3e0e06-32a9-4ef6-aa55-b308539d54cb-8dce51e1, size 104857600/512\""
time="2022-01-06T16:17:58Z" level=warning msg="pvc-0b3e0e06-32a9-4ef6-aa55-b308539d54cb-r-735b2083: time=\"2022-01-06T16:17:57Z\" level=info msg=\"Lost connection from: <IP_ADDRESS>:33060\""
time="2022-01-06T16:18:00Z" level=debug msg="Prepare to delete instance pvc-0b3e0e06-32a9-4ef6-aa55-b308539d54cb-r-735b2083"

Environment

Longhorn version: 1.2.3
Installation method (e.g. Rancher Catalog App/Helm/Kubectl): Kubectl
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version: k3s v1.22.5+k3s1

Number of management node in the cluster: 1
Number of worker node in the cluster: 2

Node config

OS type and version: Centos 8.6 - 4.18.0-240.1.1.el8_3.x86_64
CPU per node: 4
Memory per node: 8
Disk type(e.g. SSD/NVMe): CLOUD
Network bandwidth between the nodes: HUGELY

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal): VM - Digital Ocean
Number of Longhorn volumes in the cluster: 3

Additional context
Odd since this works on Ubuntu.
here is what the GUI is doing.

@clemenko did you install the required packages?
Like open-iscsi and so on? At debian I have to do apt-get install -y open-iscsi nfs-common
see https://longhorn.io/docs/1.2.3/deploy/install/#installation-requirements

Yup iscsi-initiator-utils.x86_64 is installed on all nodes.
Even ran the check:
clempro:clemenko k3s ( <IP_ADDRESS>:6443:longhorn-system ) $ curl -sSfL https://raw.githubusercontent.com/longhorn/longhorn/v1.2.3/scripts/environment_check.sh | bash
daemonset.apps/longhorn-environment-check created
waiting for pods to become ready (0/3)
all pods ready (3/3)

  MountPropagation is enabled!

cleaning up...
daemonset.apps "longhorn-environment-check" deleted
clean up complete

You have 2 worker nodes. The default number of replicas is 3. This might be the problem. Change the default number of replicas to 2 and try again - I would say.

my master is also a worker.
like I said this works perfectly on Ubuntu with the same k3s and longhorn versions.

Well. Then I cant help. Sorry.
Maybe just use Debian. :-)

Do they logs make sense to anyone?
---- instance-manager-e-9b797db9 ----
[pvc-1dcc513e-93e4-4f43-b0c2-a6f11a18b43a-e-9cc9b9a8] time="2022-01-06T18:26:56Z" level=warning msg="FAIL to discover due to Failed to execute: nsenter [--mount=/host/proc/1/ns/mnt --net=/host/proc/1/ns/net iscsiadm -m discovery -t sendtargets -p <IP_ADDRESS>], output , stderr, Failed to connect to bus: No data available\niscsiadm: can not connect to iSCSI daemon (111)!\niscsiadm: Could not scan /sys/class/iscsi_transport.\nFailed to connect to bus: No data available\niscsiadm: can not connect to iSCSI daemon (111)!\niscsiadm: Cannot perform discovery. Initiatorname required.\niscsiadm: Could not perform SendTargets discovery: could not connect to iscsid\n, error exit status 20"
[pvc-1dcc513e-93e4-4f43-b0c2-a6f11a18b43a-e-9cc9b9a8] time="2022-01-06T18:27:01Z" level=warning msg="FAIL to discover due to Failed to execute: nsenter [--mount=/host/proc/1/ns/mnt --net=/host/proc/1/ns/net iscsiadm -m discovery -t sendtargets -p <IP_ADDRESS>], output , stderr, Failed to connect to bus: No data available\niscsiadm: can not connect to iSCSI daemon (111)!\nFailed to connect to bus: No data available\niscsiadm: can not connect to iSCSI daemon (111)!\niscsiadm: Cannot perform discovery. Initiatorname required.\niscsiadm: Could not perform SendTargets discovery: could not connect to iscsid\n, error exit status 20"

@clemenko
Do you start the iSCSI daemon service?
You can try
systemctl restart iscsid.service
systemctl enable iscsid.service

how did i miss that. Thanks @derekbit

in kind. iscsid say: "sendmsg: bug? ctrl_fd 5"


use front end layout for password reset pages

fixes #153

@cornernote Thanks!
@Konrad90 I'll merge this for now, could you please add the windows fixes to the merged files, like here

done https://github.com/phundament/app/pull/157


Create release page

Description
Add a release page to hold download links for wallet, server, and miner binaries.
Context
https://gitter.im/grin_community/dev?at=5c6c229ca7d733509d912c92:

Gary Yu @garyyu Feb 19 17:37
with multiple projects, I think we need a release page on our website, to hold 3 binaries for one release: server, wallet, miner?
instead of on each github project.
Yeastplume @yeastplume Feb 19 17:37
@garyyu sure, we can just link from there
Gary Yu @garyyu Feb 19 17:37

Would be great to have it in time for release of v1.1.0 (ETA a couple of weeks).

@lehnberg Does this still need to be done? I'd love to help out!

@arteagabriel  Yes, still need :-)  thanks if you can help out 😄

@garyyu ok cool! I'll see what I can do. I'm guessing if I have any questions to ask on gitter?

Yes.
And propose to use https://gitter.im/grin_community/design for site design related discussion.

Thanks for picking this up @arteagabriel! 🥇
You can always ask questions here on the ticket as well.

I guess the last thing missing from https://grin.mw/download is the miner binary?

Arguably it's good enough, not sure how useful grin-miner is beyond its role as a reference miner. Closing 👍


Key Error: 'brand'

When using the module a Key Error is thrown and the process halts.
Traceback (most recent call last):
  File "proc.py", line 4, in <module>
    from system_info import sysinfo
  File "/miniforge3/lib/python3.9/site-packages/system_info/sysinfo.py", line 230, in <module>
    sysInfo = os_info.systemSpec()
  File "/miniforge3/lib/python3.9/site-packages/system_info/sysinfo.py", line 55, in systemSpec
    data["Processor"] = cinfo['brand']
KeyError: 'brand'

'brand' versus 'brand_raw'  for the get_cpu_info() dictionary key.
https://github.com/suhanna/System_info/blob/master/system_info/sysinfo.py#L55
miniforge3/envs/myenv/lib/python3.9/site-packages/system_info/sysinfo.py
        cinfo = cpuinfo.get_cpu_info()
        data = {}
        data["Processor"] = cinfo['brand']

Edit:
system-info               2.0.0                    pypi_0    pypi

This was fixed in #3 . Its a simple misname, please update your system_info library
Using
python -m pip install --update system_info

This error is still present in the latest version in PyPi repo.

This error is still present in the latest version in PyPi repo.

Mind sending a stacktrace?

Yes, issue is still prevalent in PyPi repo.


What about Project troublesshoothing?

I've successfully integrated Azure DevOps with Excel, however the Team tab doesn't appear in the Project ribbon.
These instructions work well for Excel, but they don't for Project, specifically the regedit section.

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

ID: bf4c6dd3-d2d2-0d41-9958-d3f7d85b5c05
Version Independent ID: e5e4a28f-30b8-0dab-b94b-d94fe6d341fe
Content: TFS-Office integration issues - Azure Boards
Content Source: docs/boards/backlogs/office/tfs-office-integration-issues.md
Product: devops
Technology: devops-agile
GitHub Login: @KathrynEE
Microsoft Alias: kaelli

Project is deprecated. EX: the note on https://docs.microsoft.com/en-us/azure/devops/boards/backlogs/office/schedule-projects-using-microsoft-project?toc=%2Fazure%2Fdevops%2Fboards%2Ftoc.json&bc=%2Fazure%2Fdevops%2Fboards%2Fbreadcrumb%2Ftoc.json&view=tfs-2018&viewFallbackFrom=azure-devops

Starting with Visual Studio 2019, the Team Foundation plug-in for Office is deprecating support for Microsoft Project. Project integration and the TFSFieldMapping command is not supported for Azure DevOps Server 2019 nor for Azure DevOps Services. You can continue to use Microsoft Excel.

Wow, this was quick! Awesome response time.
I see, now if that’s the case, wouldn’t it be convenient to update the documentation stating that?
I spent 2 hours to get to this point and troubleshooting, just to find out it no longer applies for Project.
Thank you.
Hermes López
Offering Lead
Support for Mission Critical
From: Nick Schonning<EMAIL_ADDRESS>Sent: Monday, August 5, 2019 1:23 PM
To: MicrosoftDocs/vsts-docs<EMAIL_ADDRESS>Cc: Hermes Lopez<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/vsts-docs] What about Project troublesshoothing? (#5135)
Project is deprecated. EX: the note on https://docs.microsoft.com/en-us/azure/devops/boards/backlogs/office/schedule-projects-using-microsoft-project?toc=%2Fazure%2Fdevops%2Fboards%2Ftoc.json&bc=%2Fazure%2Fdevops%2Fboards%2Fbreadcrumb%2Ftoc.json&view=tfs-2018&viewFallbackFrom=azure-devopshttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fdevops%2Fboards%2Fbacklogs%2Foffice%2Fschedule-projects-using-microsoft-project%3Ftoc%3D%252Fazure%252Fdevops%252Fboards%252Ftoc.json%26bc%3D%252Fazure%252Fdevops%252Fboards%252Fbreadcrumb%252Ftoc.json%26view%3Dtfs-2018%26viewFallbackFrom%3Dazure-devops&data=02|01|hermes.lopez%40microsoft.com|78ba70fda0d04e56d8dd08d719e2ba17|72f988bf86f141af91ab2d7cd011db47|1|0|637006333883403695&sdata=Xd7vSrVRf%2BrHH9ZOYWdDiQxlLQTy02jmLcv7Tw0uAtc%3D&reserved=0
Starting with Visual Studio 2019, the Team Foundation plug-in for Office is deprecating support for Microsoft Project. Project integration and the TFSFieldMapping command is not supported for Azure DevOps Server 2019 nor for Azure DevOps Services. You can continue to use Microsoft Excel.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fvsts-docs%2Fissues%2F5135%3Femail_source%3Dnotifications%26email_token%3DAM2N23NC6MNI7HUHA34NCBDQDCD2VA5CNFSM4IJORT6KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3S6ZCQ%23issuecomment-518384778&data=02|01|hermes.lopez%40microsoft.com|78ba70fda0d04e56d8dd08d719e2ba17|72f988bf86f141af91ab2d7cd011db47|1|0|637006333883403695&sdata=uzzxTCJavb765tHYRe%2FkHs%2B7fVZEvqoOSrDy%2BDgsaJM%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAM2N23MVA6QUVDSB7FUME23QDCD2VANCNFSM4IJORT6A&data=02|01|hermes.lopez%40microsoft.com|78ba70fda0d04e56d8dd08d719e2ba17|72f988bf86f141af91ab2d7cd011db47|1|0|637006333883413688&sdata=nfKh41eGXapGQi2KjgOByIt0PTag%2Biqtiju9K5W59fM%3D&reserved=0.

@hermesmsft - Thank you for your inquiry, and apologies for any confusion on what is supported. With the latest version of Visual Studio 2019, the Team Foundation Add-in no longer supports Azure DevOps integration with Project or Power Point Storyboarding. I am working to update the articles to make that clearer.

Hi, for me it is still not clear what is really deprecated here. Many colleagues of mine use this Team add-in clicking to "New List" to import query results to Excel. Is this for example deprecated? What means "is deprecating support for Microsoft Project" and "Project integration and the TFSFieldMapping command is not supported"? However, "we can continue to use Microsoft Excel", but the question is, will we have the option to connect Excel to Azure DevOps Server? Could someone please explain it? Thank you.


Add ARO roadmap link under the Resources section

[Enter feedback here]
Could you please add  not only Azure Roadmap but also ARO roadmap under the Resources section : https://aka.ms/openshift/roadmap
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 4a8cb0c6-b695-e55a-d9ec-9a799b802ea3
Version Independent ID: 80fd40f6-a7f3-4848-95ea-9681d266f9a7
Content: Frequently asked questions for Azure Red Hat OpenShift
Content Source: articles/openshift/openshift-faq.md
Service: container-service
GitHub Login: @jimzim
Microsoft Alias: jzim

@ezYakaEagle442
Thanks for the feedback! We are currently investigating and will get back on this.

@sakthi-vetrivel
Can you please check and add your comments on this doc update request as applicable.

Thank you for your feedback on the documentation! This issue has been addressed, so I'm closing this issue.
#please-close


Add integration with QPIC for drawing circuit diagrams

Is your feature request related to a use case or problem? Please describe.
As the size of the circuits we build with Cirq increases, the ASCII style circuit diagrams do not scale very well. We also need a way to draw diagrams for publications in latex and it would be nice if Cirq users have a way to convert their cirq circuits into nice latex diagrams.
Describe the solution you'd like
QPIC is a flexible and powerful framework for drawing quantum circuit diagrams. See https://github.com/qpic/qpic for more details.
What is the urgency from your perspective for this issue? Is it blocking important work?

P1 - I need this no later than the next release (end of quarter)

Other options could be quantikz (https://arxiv.org/abs/1809.03842) or qcircuit, unsure if those tools have different licenses that are more amenable

A good thing about QPIC is that it reads circuits written in an intermediate representation and then generates the corresponding latex code automatically. IIUC, other packages like quantikz / qcircuit provide packages that can be included in a latex document but there would be a non-trivial conversion from a cirq circuit object to the corresponding latex code using commands from these packages. With QPIC, we just need to worry about representing the same circuit in a much more easily human readable IR, that can potentially be tweaked by users manually as well, before passing it over to QPIC to generate the actual diagrams.

From cirq sync:

I confirmed with the legal team that adding an integration such that we don't have a direct dependence on their codebase should be fine. This implies that we can add a method that outputs the circuit in an IR that can be consumed by QPIC without any legal implications.
So yes, this should be done. We should probably add this in cirq/contrib to make sure we don't have any backwards compatibility promises because of an indirect dependency on QPIC.


Market page not compensating for 'Grace Period'

This market was created on Dec. 7th with a closing date of Dec. 14th, a grace period of just over 4 days(Dec. 19th) and a reporting period of 4 days after the end the grace period (Dec. 23rd). However, upon checking the market on Dec. 19th it displays as if the reporting period is concluded with "Oracle failed to report. Reports open to all." Likewise the outcomes have active "Report outcome"  buttons that anybody can click and attempt to report. Upon submitting the report you receive an error "The report is not coming from designated Oracle."
The market should still have 3 days of reporting window at the time of these screenshots.

@Boibit The errors that is being notified The report is not coming from designated Oracle. is correct right? Since any user is able to submit it even though they shouldnt(since its actual state is in reporting state where only oracle should be able to report)?

@saboonikhil Need deadlines on Market to continue with this. https://github.com/zeitgeistpm/tools/issues/242

@Boibit The error that is being notified The report is not coming from designated Oracle. is correct right? Since any user is able to submit it even though they shouldnt(since its actual state is in reporting state where only oracle should be able to report)?

Correct.

Working on some utility to fix this and also the timeline(in a different issue) in the @zeitgeistpm/sdk-next#5 issue


Improve Netty Backend Performance

Improve netty backend performance, support multi query results of mysql connections.

Codecov Report

Merging #1028 into dev will decrease coverage by 0.11%.
The diff coverage is 4.65%.

@@            Coverage Diff            @@
##              dev   #1028      +/-   ##
=========================================
- Coverage   54.92%   54.8%   -0.12%
=========================================
  Files         632     632
  Lines       12372   12396      +24
  Branches     1980    1984       +4
=========================================
- Hits         6795    6794       -1
- Misses       5159    5187      +28
+ Partials      418     415       -3

Impacted Files
Coverage Δ

...o/shardingsphere/proxy/frontend/ShardingProxy.java
0% <0%> (ø)
:arrow_up:

...ket/command/text/fieldlist/ComFieldListPacket.java
0% <0%> (ø)
:arrow_up:

...proxy/backend/common/SQLPacketsBackendHandler.java
0% <0%> (ø)
:arrow_up:

...ysql/packet/command/text/query/ComQueryPacket.java
0% <0%> (ø)
:arrow_up:

...rdingsphere/proxy/backend/ShardingProxyClient.java
0% <0%> (ø)
:arrow_up:

...a/io/shardingsphere/proxy/config/RuleRegistry.java
0% <0%> (ø)
:arrow_up:

...phere/proxy/backend/mysql/MySQLBackendHandler.java
0% <0%> (ø)
:arrow_up:

...here/core/constant/ShardingPropertiesConstant.java
100% <100%> (ø)
:arrow_up:

...OrchestrationMasterSlaveDataSourceFactoryBean.java
66.66% <0%> (-11.12%)
:arrow_down:

...al/state/datasource/DataSourceListenerManager.java
36.66% <0%> (-3.34%)
:arrow_down:

... and 2 more

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 9c28db8...6ae1419. Read the comment docs.


Enhancement: Ruby gem analysis

Like jars, Ruby gems also require analysis to determine potential security issues and I don't know of any other products that offer that functionality.

Dawn (https://github.com/thesp0nge/dawnscanner) and brakeman (https://github.com/presidentbeef/brakeman) both offer this to some extent.

John,
Thanks!  There is also bundler-audit (
https://github.com/rubysec/bundler-audit) which is more focused
specifically on vulns in the dependent gems. I believe the others you
listed do a similar thing with regard to vulns in gems - but they also do
more.  Note - I do not work in the ruby world at all, so if someone else
could comment on this please do.
--Jeremy
On Tue, Apr 28, 2015 at 12:40 PM, John Melton<EMAIL_ADDRESS>wrote:

Dawn (https://github.com/thesp0nge/dawnscanner) and brakeman (
https://github.com/presidentbeef/brakeman) both offer this to some extent.
—
Reply to this email directly or view it on GitHub
https://github.com/jeremylong/DependencyCheck/issues/221#issuecomment-97130657
.

As this is really covered by other projects in the Ruby community I do not believe dependency-check should add support for Ruby.


BMC microcontroller selection

Requirements:

Be upgradable over UF2 (by the RMC)
Forward QUIC/HTTP from USB to SPI
Forward UART logs to USB using QUIC/HTTP (on request or always?)
Power off the compute
Read current/voltage and send to RMC or Pi

TODO:

[ ] Add device-side USB speed identification resistor as discussed in #19


[FEATURE/PERFORMANCE] Better Token Caching for ManagedIdentityCredential

Library or service name.
Azure.Core, Azure.Identity, Azure.Storage, Azure.EventHubs, Azure.ServiceBus
Is your feature request related to a problem? Please describe.
When using Managed Identity, a network call is made to obtain an AAD token used to access an Azure service (i.e. Storage, Service Bus, etc.). Caching of the tokens at the library level is critical to performance and stability of the Managed Identity framework. Looking at the different Azure service clients, caching is inconsistent and can lead to unnecessarily high traffic on Managed Identity dependencies (i.e. Token Service on App Service, IMDS on Azure VMs). Recently, we have seen high traffic on Token Services in the order of thousands of requests per minute - caching in the SDK could drastically reduce the number of calls (already seen with some customers after a design review of their code). This adds resiliency to Managed Identity, especially in the event of an AAD or internal Azure infrastructure outage.
In Azure storage libraries today, caching is done per client (i.e. per BlobContainerClient, BlobClient, QueueClient). This is done through the BearerTokenAuthenticationPolicy in Azure.Core.
When using DefaultAzureCredential directly (for ManagedIdentityCredential), caching is not done at the credential level here. Customers who use these credentials directly often shoot themselves in the foot since caching should be abstracted from them.
In Azure Event Hub library, I don't think token caching is done - EventHubTokenCredential is just passthrough object to the DefaultAzureCredential which leverages ManagedIdentityCredential (no caching).
Possible options:

Caching is performed at the TokenCredential level

A DefaultAzureCredential would maintain a ManagedIdentityCredential that has it's own token cache

Static variables

Can the token cache in BearerTokenAuthenticationPolicy be made static?
This is helpful for scenarios like Azure Functions and WebJobs that can have thousands of requests per minute with different clients instantiated in customer code, leading to thousands of requests to underlying token services downstream without a static cache.
A static cache here would mean consumers of the SDK don't have to think about caching (it just comes out of the box like a static http client).

The goal of this is to reduce the dependency on retrieving tokens through networking calls. In the context of Azure Functions or WebJobs, we have seen abnormally high number of requests that lead to load issues. This can cause customer application downtime.

@karshinlin:  Would you please be so kind as to leave the issues untagged other than needs-triage when filing them so that the Azure SDK team can triage?

@karshinlin: Would you please be so kind as to leave the issues untagged other than needs-triage when filing them so that the Azure SDK team can triage?

Certainly! Noted for future reference too.

With respect to Event Hubs and Service Bus, as an AMQP services, authorization is not performed per-request like it is for HTTP-based services.   Instead, authorization is sent in the background over a dedicated AMQP link as the credential is nearing expiration.
Both perform caching of Identity-based credentials as part of their CBS token providers to ensure that a single token is requested and then used across active links as authorization is needed.

+1 for this! We also migrated recently to use ManagedIdentityCredential for our EventHubClient connections, but ran into a growing number of SocketExceptions and NetworkTimeouts because this was causing so many token service requests to the local network for our App Service in App Service Environment. Today, App Service cannot handle many, many requests to MSI GetToken, so it would be a huge help if Azure.Identity could guarantee some amount of caching.
We also saw this with the Blob SDK w/ MSI which was also calling out at least once a minute to get a token, and sometimes failing, which led to less reliability than we can usually count on with the connection string methods.

@christothes , do you know if an AMQP based client will share a connection for multiple EventHubReceiverClients? Or if each one is initiating the call (and causing a token call)?
We rolled back our MSI change and our network stabilized after that. It's probably a combination of our use case w/ orleans and the lack of token caching, but App Service team said they saw upwards of 30 requests per second against their token service at one point.

I'll let @jsquire comment on the specifics, since this is his area of expertise but I suspect if your use case it to create many clients, you'd get a token request for each instance.

@xinyi-joffre:  With respect to connection sharing, the answer for Event Hubs and Service Bus is:  "it depends on how you create them."   Generally speaking, any type with the Client suffix is intended to represent an independent connection to the service.   However, in Event Hubs it is possible to create a client by passing an existing EventHubConnection, which enables sharing.
For the Orleans use case, depending on which version is in use, you may be using Azure.Messaging.EventHubs or the legacy Microsoft.Azure.EventHubs package.  The details differ a bit, but the result is the same:

In the v3.5 branch and main, Orleans is using Azure.Messaging.EventHubs and creating the PartitionReceiver as a stand-alone instance - which means that it will spawn and own a dedicated connection.  (src).

In the v3.4.3 branch, Orleans is using Microsoft.Azure.EventHubs and is creating a new EventHubClient to spawn each PartitionReciever, which also ensures each will use a dedicated connection.  (src).

orleans and the lack of token caching,

I'm not sure that I understand the inference, and I question its accuracy.  Assuming that the version of Orleans that you're using references the Azure.Messaging.EventHubs package, the Event Hubs clients do not send a token with each service request.  The token is sent only when a connection/link is created and then ~10 minutes before the token is set to expire.   The version of the Event Hubs SDK that Orleans is currently referencing is about 8 months old  (src) and does lack token caching -  but, that would only be impactful if PartitionReciever instances are being created often or there are connectivity issues that require them to reconnect often.

but App Service team said they saw upwards of 30 requests per second against their token service at one point.

Again, assuming the current generation of Event Hubs, this wouldn't happen under normal operation; the expiration of tokens is calculated using some random jitter to ensure that there is no thundering herd of requests due to mass expiration.   This would only be possible if:

You have 30 or more partitions for your Event Hub

Orleans created 30+ PartitionReceivers and invoked a service operation on each of them within the same exact second  OR  the connection for each existing PartitionReceiver disconnected and an operation was invoked on 30+ instances within the exact same second, causing them to all attempt reconnection at once.

@jsquire we are using the latest v3.5 of Orleans, which uses Azure.Messaging.EventHubs. This is the only one supports ManagedIdentityCredential, since it was added in the latest release.
It unfortunately was not a random occurrence, we saw failures throughout a 5 day window after deployment. We were finally able to isolate the root cause and rolled back to using connection strings. We didn't change the EventHub or Orleans version, just the how EventHub was authenticating.
Once we rolled back, the engineer from App Service RDP'd to our instance to ensure that token requests had gotten better (though Blob SDK was still calling out to App Service's token service around once every 1-2 minutes for blob leases), which is an okay load, but it is still more than it needs to call out to token service.
Here's a count of MSI.GetToken DependencyTelemetry failures across 5 day window:
2021-09-09 	82
2021-09-10 	536
2021-09-11 	1382
2021-09-12 	1392
2021-09-13	828 (partial day, this is when we rolled back)
This also happened across multiple global regions, so it was not an isolated to a single instance. You are correct that there was also something amiss in the host environment--App Service could not handle the load, so the token service was breaking and getting stuck (confirmed to be a bug, but even after that's fixed, they still are relying on SDKs having caching to reduce the load).
For the EventHub configuration piece:

Our EventHub did have 32 partitions.
I'm not sure why there were so many MSI.GetToken calls from the EventHub library w/ Orleans, but once we went back to Connection String, even the MSI.GetToken success telemetry was gone from our service telemetry, so it was definitely coming from EventHub MSI connections. I'll see if I can dig into the internals of Orleans later today and see why it was calling out so often. As a consumer of the Azure.Identity and Orleans libraries, we don't directly instantiate any EventHub clients, but at the moment, given the major reliability issues we had migrating, it's not feasible to use Azure.Identity MSI together with Orleans v3.5 and the older EventHubs version.

@ReubenBond, based on discussion above, would we be able to upgrade to the latest EventHub library w/ TokenCaching? Do you want me to create an issue in Orleans repo instead to update packages?:

Assuming that the version of Orleans that you're using references the Azure.Messaging.EventHubs package, the version of the Event Hubs SDK that Orleans is currently referencing is about 8 months old (src) and does lack token caching - but, that would only be impactful if PartitionReciever instances are being created often or there are connectivity issues that require them to reconnect often.

@jsquire Checking back if there is any traction here. App Service team is working on improvements for availability and reliability, but the issue of overloading downstream services while using Managed Identity will continue to be a problem without effective caching at the SDK level. Without a static/shared cache at the library level, customers run into issues requesting too many tokens, causing trouble for their app when deployed to Azure with production load, and often not noticed in dev/qa environments.

@karshinlin:  My role for this issue was only first triage.   For any updates, we'll need to ask the engineers assigned.   @christothes / @schaabs:  Are there any updates to share?

Token Caching support for Managed Identity is being tracked here https://github.com/Azure/azure-sdk-for-net/issues/27778

The development work on token caching for ManagedIdentityCredential kicks off next month. We're targeting the Azure.Identity v1.7.0 release, which will GA in early October. For those interested in testing this caching feature, a beta release will be available before October.

This is now available in the 1.7.0-beta.1 release


FeaturesLineWidget

Hi @dstansby ,
As suggested in #184 , I am transferring the code here without the LineWidget.
This PR brings a BaseLineWidget and a FeaturesLineWidget to napari-matplotlib, where the FeaturesLineWidget has an object-id field capable of grouping objects before plotting, thus displaying individual line plots for each object.
Best,
Marcelo

Just having a play around with this, and I'm confused by what the "object-id" selector is for? Why are there not just two selectors that select what is being plotted on the x/y axes?

Good question. So the object_id is the factor that groups elements from the table using the .groupby from pandas. This allows individual lines for each label with different colors. Typically this is just a column named 'label' in the table containing the label numbers, but as this can vary from different people and I cannot anticipate what it will be, so I chose to add it in the interface and let the user decide.
By the way, I noticed I was still calling 'label' in other places, so I renamed them to object_id now to make it more general.

And following on from that, how is this different from the FeaturesScatterWidget? Could we add the functionality desired by just doing exactly the same as FeaturesScatterWidget, but joining the scatter points with a line?

Hmm I am not sure. Over there, the .scatter is being used, which returns a PathCollection right? I am interested in having access to Line2D objects. That also why I was adding a _lines list as a property of the class before, to store current Line2D artists in the plot, because I thought it would be faster to update existing lines data with .set_xdata and .set_ydata than redraw all the lines.

Hi @dstansby ,
Did you have some time to consider this feature?
Thanks for your time on reviewing this!

This would close #60


Fix formatted image file name assumptions

The regex used to match filenames in Image::deleteFormattedImages required digits in the filename. These digits were present when using the Image::generate* methods, but are not guaranteed to be present when using custom resize methods (added by extension). This meant that the resampled images generated by custom getFormattedImage methods were not guaranteed to be deleted when Image::deleteFormattedImages was called.

Image::cacheFilename did not sanitise arguments before generating a filename. This meant it was possible to generate invalid filenames (for example, containing a slash).

Hi @stecman,
Thanks for this and sorry for the delay in review. It appears this functionality has been modified in the next major release (see introduction of getFilenamePatterns). That regex has changed significantly so try that out. From my quick glance it should.
Cheers


fix: 更新 Proxy 密钥所保存的密钥信息有误(closed #139)

Codecov Report

Merging #1503 (239f44a) into v2.3.1-dev (2fcec42) will decrease coverage by 0.01%.
The diff coverage is n/a.

@@              Coverage Diff               @@
##           v2.3.1-dev    #1503      +/-   ##
==============================================
- Coverage       73.93%   73.93%   -0.01%
==============================================
  Files             369      369
  Lines           25180    25180
==============================================
- Hits            18618    18616       -2
- Misses           6562     6564       +2

see 2 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Correct template-specific workflow syntax

Why:
Closes https://github.com/github/docs/issues/5103
What's being changed:
The syntax $default-branch is specific to workflow templates only and cannot be used in standard workflows. As a result, a copy-paste of the existing yaml workflow for "Starting with the Node.js workflow template" will fail. See https://github.com/steven-wolfman/test-workflow-template-syntax/commit/0d006c52a904911ddb71a13994a4864d7d022e1c#diff-fbdccf80e37a6640cb78bdcf9d90597cb91421747fd5c2365d878287e744ff99 for an example commit that triggers a workflow using the main syntax but fails to trigger workflows using the $default-branch syntax.
Check off the following:

[x] I have reviewed my changes in staging. (look for the deploy-to-heroku link in your pull request, then click View deployment)
[x] For content changes, I have reviewed the localization checklist
[x] For content changes, I have reviewed the Content style guide for GitHub Docs.

OK. There are a few more places where this appears. In English:

https://github.com/steven-wolfman/docs/content/actions/guides/building-and-testing-ruby.md

Plus these translations of both the Ruby and Node.js documents:

https://github.com/steven-wolfman/docs/translations/ko-KR/content/actions/guides/building-and-testing-nodejs.md
https://github.com/steven-wolfman/docs/translations/ko-KR/content/actions/guides/building-and-testing-ruby.md
https://github.com/steven-wolfman/docs/translations/de-DE/content/actions/guides/building-and-testing-nodejs.md
https://github.com/steven-wolfman/docs/translations/de-DE/content/actions/guides/building-and-testing-ruby.md
https://github.com/steven-wolfman/docs/translations/pt-BR/content/actions/guides/building-and-testing-nodejs.md
https://github.com/steven-wolfman/docs/translations/pt-BR/content/actions/guides/building-and-testing-ruby.md
https://github.com/steven-wolfman/docs/translations/ru-RU/content/actions/guides/building-and-testing-nodejs.md
https://github.com/steven-wolfman/docs/translations/ru-RU/content/actions/guides/building-and-testing-ruby.md
https://github.com/steven-wolfman/docs/translations/es-ES/content/actions/guides/building-and-testing-nodejs.md
https://github.com/steven-wolfman/docs/translations/es-ES/content/actions/guides/building-and-testing-ruby.md
https://github.com/steven-wolfman/docs/translations/zh-CN/content/actions/guides/building-and-testing-nodejs.md
https://github.com/steven-wolfman/docs/translations/zh-CN/content/actions/guides/building-and-testing-ruby.md
https://github.com/steven-wolfman/docs/translations/ja-JP/content/actions/guides/building-and-testing-nodejs.md
https://github.com/steven-wolfman/docs/translations/ja-JP/content/actions/guides/building-and-testing-ruby.md

(A grep of all files for $default-branch shows only these locations plus appropriate reference at https://github.com/steven-wolfman/docs/blob/main/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md and its translations.)
I'll work on an update for https://github.com/steven-wolfman/docs/content/actions/guides/building-and-testing-ruby.md. I don't think I can reasonably help with the text in any of the translations.

I think it's not compulsory to rename your default branch main. I have set "source' as my default branch and I have written the workflow as on: push: branches: [source] and the code just works fine for me. So, default-branch option is the correct one. It shouldn't be stated as 'main' as people can rename their default branch to any name.

I agree that it is not compulsory to name the default branch main.
The trouble is that the existing code shows $default-branch which does not work no matter what your default branch is named. Instead, that syntax is specific to GitHub workflow templates and does not work in standard GitHub workflows.
I'm unsure whether putting main into the raw code is the right way to go, but leaving it as $default-branch with no further commentary seems clearly wrong.
Does that make sense?

I think it's not compulsory to rename your default branch main. I have set "source' as my default branch and I have written the workflow as on: push: branches: [source] and the code just works fine for me. So, default-branch option is the correct one. It shouldn't be stated as 'main' as people can rename their default branch to any name.

I agree that it is not compulsory to name the default branch main.
The trouble is that the existing code shows $default-branch which does not work no matter what your default branch is named. Instead, that syntax is specific to GitHub workflow templates and does not work in standard GitHub workflows.
I'm unsure whether putting main into the raw code is the right way to go, but leaving it as $default-branch with no further commentary seems clearly wrong.
Does that make sense?

Yeah I agree but for that an elaborated documentation is needed. If we just put main in the raw code then many one will think they have to set main in their workflow. So the people who have default-branch named as "master" will face error.

I think it's not compulsory to rename your default branch main. I have set "source' as my default branch and I have written the workflow as on: push: branches: [source] and the code just works fine for me. So, default-branch option is the correct one. It shouldn't be stated as 'main' as people can rename their default branch to any name.

I agree that it is not compulsory to name the default branch main.
The trouble is that the existing code shows $default-branch which does not work no matter what your default branch is named. Instead, that syntax is specific to GitHub workflow templates and does not work in standard GitHub workflows.
I'm unsure whether putting main into the raw code is the right way to go, but leaving it as $default-branch with no further commentary seems clearly wrong.
Does that make sense?

Just to make this more concrete, please do open https://github.com/steven-wolfman/test-workflow-template-syntax/commit/0d006c52a904911ddb71a13994a4864d7d022e1c
There, you can see that a workflow that directly copies-and-pastes the $default-branch syntax will not run on a push to the default branch. (Click the green checkmark to see what did run, which was the only one of the three workflows that uses main. The two workflows using $default-branch didn't run because the push was not to a branch named literally $default-branch. You can see the copy-pasted workflow that uses $default-branch at https://github.com/steven-wolfman/test-workflow-template-syntax/blob/0d006c52a904911ddb71a13994a4864d7d022e1c/.github/workflows/copy-paste-of-nodejs-template.yml. All of this would work the same with source as the default branch, replacing main where it appears, i.e., only one of the three workflows would run.)

I think it's not compulsory to rename your default branch main. I have set "source' as my default branch and I have written the workflow as on: push: branches: [source] and the code just works fine for me. So, default-branch option is the correct one. It shouldn't be stated as 'main' as people can rename their default branch to any name.

I agree that it is not compulsory to name the default branch main.
The trouble is that the existing code shows $default-branch which does not work no matter what your default branch is named. Instead, that syntax is specific to GitHub workflow templates and does not work in standard GitHub workflows.
I'm unsure whether putting main into the raw code is the right way to go, but leaving it as $default-branch with no further commentary seems clearly wrong.
Does that make sense?

Yeah I agree but for that an elaborated documentation is needed. If we just put main in the raw code then many one will think they have to set main in their workflow. So the people who have default-branch named as "master" will face error.

Totally, but isn't that better than the current case where everyone will have an error?
And.. is the correct fix for the more elaborate documentation to clarify the need for rename just before the code block (which is what I tried)?
Thanks!

I think it's not compulsory to rename your default branch main. I have set "source' as my default branch and I have written the workflow as on: push: branches: [source] and the code just works fine for me. So, default-branch option is the correct one. It shouldn't be stated as 'main' as people can rename their default branch to any name.

I agree that it is not compulsory to name the default branch main.
The trouble is that the existing code shows $default-branch which does not work no matter what your default branch is named. Instead, that syntax is specific to GitHub workflow templates and does not work in standard GitHub workflows.
I'm unsure whether putting main into the raw code is the right way to go, but leaving it as $default-branch with no further commentary seems clearly wrong.
Does that make sense?

Yeah I agree but for that an elaborated documentation is needed. If we just put main in the raw code then many one will think they have to set main in their workflow. So the people who have default-branch named as "master" will face error.

Totally, but isn't that better than the current case where everyone will have an error?
And.. is the correct fix for the more elaborate documentation to clarify the need for rename just before the code block (which is what I tried)?

I think it's not compulsory to rename your default branch main. I have set "source' as my default branch and I have written the workflow as on: push: branches: [source] and the code just works fine for me. So, default-branch option is the correct one. It shouldn't be stated as 'main' as people can rename their default branch to any name.

I agree that it is not compulsory to name the default branch main.
The trouble is that the existing code shows $default-branch which does not work no matter what your default branch is named. Instead, that syntax is specific to GitHub workflow templates and does not work in standard GitHub workflows.
I'm unsure whether putting main into the raw code is the right way to go, but leaving it as $default-branch with no further commentary seems clearly wrong.
Does that make sense?

Yeah I agree but for that an elaborated documentation is needed. If we just put main in the raw code then many one will think they have to set main in their workflow. So the people who have default-branch named as "master" will face error.

Totally, but isn't that better than the current case where everyone will have an error?
And.. is the correct fix for the more elaborate documentation to clarify the need for rename just before the code block (which is what I tried)?
Thanks!

Yeah default-branch must have to be rename as the branch name that you've set as your default-branch. Set it as main in the raw code will help many ones because we know a huge number of github users are using main as their default-branch. But it still there should be extra documentation for those who have custom default-branch.

Thanks so much for opening an issue and a PR @steven-wolfman! You don't need to worry about any of the translations, updated content in English is automatically sent to our translators once it's merged. I'll get this triaged for review ⚡

Thanks!

Steven A. Wolfman  Ph.D. (he/him)
Professor of Teaching
Department of Computer Science
The University of British Columbia | Vancouver Campus | Musqueam Traditional Territory
201-2366 Main Mall | Vancouver BC | V6T 1Z4 Canada
@.***
On Thu, 8 Apr 2021, Janice wrote:

Date: Thu, 8 Apr 2021 15:07:00
From: Janice @.>
Reply-To: github/docs
@.>
To: github/docs @.>
Cc: Steve Wolfman @.>, Mention @.***>
Subject: Re: [github/docs] Correct template-specific workflow syntax (#5104)
[CAUTION: Non-UBC Email]
Thanks so much for opening an issue and a PR @steven-wolfman! You don't need to worry about any of the translations, updated content in English is automatically sent to our translators
once it's merged. I'll get this triaged for review ⚡
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.[AAHPZBPO67PR7PKS4RTSTUTTHYSIJA5CNFSM42PKHEV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOGCTSSMA.gif]


Output full URL including code when using login --headless

When using aws-cli's login --no-browser the CLI output also includes the URL with the code so you do a single copy and paste. E.g.:
❯ aws sso login --profile my-profile --no-browser
Browser will not be automatically opened.
Please visit the following URL:

https://device.sso.eu-west-1.amazonaws.com/

Then enter the code:

HJRZ-HIWR

**Alternatively, you may visit the following URL which will autofill the code upon loading:
https://device.sso.eu-west-1.amazonaws.com/?user_code=HJRZ-HIWR**

It would be nice to have something like that here when using the --headless option. Currently outputs like this:
❯ aws-sso-util login --force-refresh --headless
Logging in https://d-12345678e9.awsapps.com/start
Identity Center login required.
Open the following URL in a browser:

https://device.sso.eu-west-1.amazonaws.com/

Then enter the code:

HJRZ-HIWR

Also, apologies for using this for an added question. If we don't want to use the --headless, is there a way to choose the browser in MacOS other than the default?

Hmm, apparently you already have that in https://github.com/benkehoe/aws-sso-util/blob/master/lib/aws_sso_lib/browser.py but I'm not experiencing for some reason.
❯ aws-sso-util --version
4.32.0

👀

Sorry for the long delay. For reasons I don't understand, when I cut the last release of the CLI, there were changes to the library as well, but I didn't cut a release for it. So that version of browser.py is on main but not in PyPI yet (which isn't how it's supposed to work). I am going to be working on this and both packages should have new versions, so that will fix this.


Make more efficient openmeteo API call

The current API call uses a lot of memory and data calling unnecessary information, this can be reduced to return only data relevant to the current humidity.

Given open-meteo has a whole python API wrapper (of course it does), I will simplify the file here to simply provide async humidity data.


Ability to exclude/filter migrations files based on a property/parameter

It'd be great if it was possible to exclude certain files based on (say) an Ant expression.
The scenario is as follows:

Multiple directories/modules

root

module 1
module 2

SQL files in some modules, also created (by Maven) in the target directory
We'd like to migrate all files

Migrating based on the root location results in errors because the SQL files are "double-counted" (once in src/, once in target/).
If we could specify e.g., exclude=/target/, that'd allow the usage of flyway to be seamless.

Thanks for your suggestion. I currently have no plans to implement this as it is a niche feature and one can easily work around this by specifying multiple locations (one for each module).

Thanks
We are indeed using multiple locations as you suggested.
The challenge with the current approach is that with multi-module configurations the list of modules may change and this approach requires frequent changes in scripts, maven files etc. (or dynamic generation of configurations - which is what we do now).
I would be surprised if this is an esoteric need for complex projects (presumably 90%+ of the projects are simple, one directory, indeed), and since Flyway is a powerful well designed tool overall it seems like there's no reason to not use it in such projects.
If you feel an opt-out option is inconsistent with Flyway's design, perhaps there could be a more powerful opt-in approach, e.g.,
Files=/src/**/.sql
(Perhaps a superset of the current Locations property? Perhaps also  overriding of prefix and suffix?)
I believe Spring has support for searching using Ant expressions so it's probably less of an implementation challenge and more about finding the right design...
What do you think?
On Nov 10, 2015, 00:19, at 00:19, Axel Fontaine<EMAIL_ADDRESS>wrote:

Thanks for your suggestion. I currently have no plans to implement this
as it is a niche feature and one can easily work around this by
specifying multiple locations (one for each module).

Reply to this email directly or view it on GitHub:
https://github.com/flyway/flyway/issues/1125#issuecomment-155216942

@axelfontaine Could you please help me to understand how to exclude the specific db migration files from a list of migration files we have..
for example:
under sql/ directory i have the below files
V1__INSERT__NBR.sql
V2__INSERT_COLUMN__ .sql
V3__INSERT_COLUMN_UPDATE.sql
V4__INSERT_COLUMN**_ACCESS.sql
Now i wanted to exclude v3__ migration file during my flyway migration execution.. any help will be helpful.

Related to #1192

We don't think this is the right direction for Flyway.


Plugin shows p2p reg ehp for all accounts

The plugin should show the right ehp for the account type - whatever is displayed at the top of the account profile page. ex IM-EHP, UIM-EHP, F2P-EHP, etc.

This might be an API limitation, but I'll definately do some research and see if I can get things moving, as I think this would be a really nice feature.

Any update on this? Would be a great enhancement to have


[BUG] SpringMonitorTest.shouldMonitor is flaky

The test is executed in different pipelines and sometimes fails (pass rate is ~25%)
https://dev.azure.com/azure-sdk/public/_build/results?buildId=3080830&view=ms.vss-test-web.build-test-results-tab&runId=43091482&resultId=102901&paneView=debug
It's being changed to be more tolerant https://github.com/Azure/azure-sdk-for-java/pull/36713/commits/e51588bd14e1ff3f411c73c298f9847e8d301415#diff-f0d0f1635e3aee9c25275a58aa2832dcc2f1afeef51993fe9e94b9f4baf44a13, but perhaps it's worth taking a look?
/cc @jeanbisutti @heyams

thanks to @alzimmermsft for figuring out why monitor tests run in the EH pipeline - #36768

Thank you @alzimmermsft  and  @lmolkova

It may be resolved by making the OTel batch span processor configurable from the Spring starter. An issue was created on OTel side.