callback when compile lua script is done

Is there a callback after l.execute(code) is done? e.g. similar to Module.print?

Is there a callback after l.execute(code) is done?
It's done as soon as it returns.

how do I check l.execute(code) is done?

how do I check l.execute(code) is done?

When it returns.
L.execute("do_something_lua()")
// done now.


Long lines of MathML are not always broken correctly

A user on the forum has complained that long lines of MathML (i.e. very long equations) are not broken properly and, in effect, run off the page.
Forum topic is here
I have requested more info but have not yet heard back.
Peter Krautzberger commented:
"Inline line breaking is difficult and MathJax doesn't support as much as we'd like. But it sounds like something MathJax does support, namely line-breaking an equation that's longer than the entire line it's on.
I thought Readium is configured to use MathJax's automatic line-breaking but maybe I'm wrong. Or it's a bug in which case a sample would be good."

=> subscribed.
Let me know if there's a sample. @danielweck I can never find the configuration of MathJax within Readium. Could you point me to it once again? (To see how line-breaks are configured.)

Readium offline Chrome extension:
https://github.com/readium/readium-shared-js/blob/develop/js/views/iframe_loader.js#L95
Readium online cloud reader:
https://github.com/readium/readium-js/blob/develop/js/epub-fetch/iframe_zip_loader.js#L209
Same config code for both:
mathJax.Hub.Config({showMathMenu:false, messageStyle: "none", showProcessingMessages: true, SVG:{useFontCache:IS_INTERNET_EXPLORER}});

Full code snippet:
            var mathJax = iframe.contentWindow.MathJax;
            if (mathJax) {

                console.log("MathJax VERSION: " + mathJax.cdnVersion + " // " + mathJax.fileversion + " // " + mathJax.version);

                var useFontCache = true; // default in MathJax

                // Firefox fails to render SVG otherwise
                if (mathJax.Hub.Browser.isFirefox) {
                    useFontCache = false;
                }

                // Chrome 49+ fails to render SVG otherwise
                // https://github.com/readium/readium-js/issues/138
                if (mathJax.Hub.Browser.isChrome) {
                    useFontCache = false;
                }

                // Edge fails to render SVG otherwise
                // https://github.com/readium/readium-js-viewer/issues/394#issuecomment-185382196
                if (window.navigator.userAgent.indexOf("Edge") > 0) {
                    useFontCache = false;
                }

                mathJax.Hub.Config({showMathMenu:false, messageStyle: "none", showProcessingMessages: true, SVG:{useFontCache:useFontCache}});

                // If MathJax is being used, delay the callback until it has completed rendering
                var mathJaxCallback = _.once(callback);
                try {
                    mathJax.Hub.Queue(mathJaxCallback);
                } catch (err) {
                    console.error("MathJax fail!");
                    callback();
                }
                // Or at an 8 second timeout, which ever comes first
                //window.setTimeout(mathJaxCallback, 8000);
            } else {
                callback();
            }

Thanks, @danielweck. So it looks like Readium does not activate MathJax's automatic line-breaking feature. I'd say it's a useful feature (possibly user-configurable); it does have a performance penalty (since it has to lay things out, check if things are too wide, if too wide: find breakpoints, lay things out again).
See also http://docs.mathjax.org/en/latest/output.html#automatic-line-breaking.


Update this "prepare_run" (left from PR #447)

All *.bin files are no longer in dir "input" but instead linked from exp2/input
What changes does this PR introduce?
Forgot to update input_oad version of "prepare_run" (in experiment: tutorial_tracer_adjsens)
when removing *.bin files in dir input (as part of PR #447). Fix this.
What is the current behaviour?
tutorial_tracer_adjsens OpenAD test broken.
What is the new behaviour
Fixed
Does this PR introduce a breaking change?
no
Other information:
Suggested addition to tag-index
none if merged right after PR #447

@jahn Thanks for the quick review. I will merge this PR later today.


Add ability to follow from event actions

Fixes #140
https://github.com/block-core/blockcore-notes/assets/79367883/fb785fa5-e63a-44d0-b151-e2eaebb4e029

Bravo

@sondreb FYI


[Task][Design]: Spacing Guidelines Screens

Is there an existing issue for this?

[X] I have searched the existing issues

SubTasks
All details are on notion

The component has been completed and published to all designers.


Update DMS MySQL privilege requirements

Updates the DMS MySQL privilege reqs to be more clear, especially for schema migration and link to the MySQL Docs.

#sign-off

@karla-escobar
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off

#sign-off


fix Readme discussions link

The readme discussions link didn't actually lead to discussions

[ ] Refactoring/add tests (refactoring or adding test which isn't a fix or add a feature)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] I have updated the documentation accordingly
[ ] I have updated the CHANGELOG with a summary of my changes
[ ] My changes have tests around them

Interesting why that linked to that issue :')
Thanks.


Printing predictions

How can I print the fine grained predictions for the test / dev set after the training is done?

sess.run(metrics, compiler.build_feed_dict(test_trees))

prints the accuracies. But I want the actual predictions. How can I get them?
Thanks

Can you provide the full code? more than
'''sess.run(metrics, compiler.build_feed_dict(test_trees))'''
I want to see your code.

I didn't code anything. I actually don't work with Tensorflow. I just wanted to get the predictions using this system.

Okay, I hope this comment can help. Let me know if it doesn't
I will be using some of the photo from my blog post: https://towardsdatascience.com/iclr-2015-striving-for-simplicity-the-all-convolutional-net-with-interactive-code-manual-b4976e206760

We can see that we have a simple graph of 9 layers of convolution layers right?
Now inside the code, from my best guess that what your metric variable would be something like accuracy. As in the metrics.
And what you want (again my best guess) would be the predictions them self so after the softmax layer operation. In that case, it is easy to just call the 'final_soft' rather than the accuracy.
Now I know this is not much of a help. So let me know

@cryptexcode let me know if this helped.

here that is variable what you want. rather calling the metrics we can call that variable directly and get the softmax values. And I know it is very complicated so I'll try to learn the code, as well as NLP, is another area I want to get into.
Anyways keep in touch soon.

@cryptexcode so one problem, I am on a window system and it might take a while, since I can't install TF fold here and the only way I can think to make this work is understand the code and rewrite everything

@cryptexcode Hey! I am on the same boat too. I am not much familiar with tensorflow. Did you find out a way to make the model predict the polarity?


Update codecov action to v2

Version 1 of codecov's GitHub action is deprecated and will start experiencing brownouts soon, and they advise updating to v2.

we are already at 3
❯ git grep codecov
.github/workflows/test.yml:        pip install codecov
.github/workflows/test.yml:    - name: Upload coverage to codecov
.github/workflows/test.yml:      uses: codecov/codecov-action@v3


Added images for Waste Monitoring solution

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Can't build project

What version of react-native are you using? Are you able to build example project?

@doomsower forgot to add to Podfile
# Pods for example
  pod 'React', :path => '../node_modules/react-native', :subspecs => [
    'Core',
    'RCTImage',
    'RCTNetwork',
    'RCTText',
    'RCTWebSocket',
    'RCTGeolocation'
  ]

Failed to build DependencyGraph: @providesModule naming collision:
Duplicate module name: String.prototype.es6
Paths: /Users/stereodenis/work/evrone/one_button/node_modules/react-native/packager/react-packager/src/Resolver/polyfills/String.prototype.es6.js collides with /Users/stereodenis/work/evrone/one_button/ios/Pods/React/packager/react-packager/src/DependencyResolver/polyfills/String.prototype.es6.js
This error is caused by a @providesModule declaration with the same name across two different files.
Error: @providesModule naming collision:
Duplicate module name: String.prototype.es6
Paths: /Users/stereodenis/work/evrone/one_button/node_modules/react-native/packager/react-packager/src/Resolver/polyfills/String.prototype.es6.js collides with /Users/stereodenis/work/evrone/one_button/ios/Pods/React/packager/react-packager/src/DependencyResolver/polyfills/String.prototype.es6.js
This error is caused by a @providesModule declaration with the same name across two different files.
at HasteMap._updateHasteMap (/Users/stereodenis/work/evrone/one_button/node_modules/react-native/packager/react-packager/src/node-haste/DependencyGraph/HasteMap.js:155:13)
at module.getName.then.name (/Users/stereodenis/work/evrone/one_button/node_modules/react-native/packager/react-packager/src/node-haste/DependencyGraph/HasteMap.js:115:31)

Seems that pod installer copied some js files into ios/Pods/React directory, and because of this packager has naming collision.
This does not happen for me. What versions of react-native and cocoapods are you using? Try to clean node_modules and pods and do a fresh install.

cleaning Pods directory fixes this


Atomically update VSCode to avoid code being missing

If VSCode is automatically updating itself in the background and you happen to try open a file in the command line, it says VSCode is missing:
/src$ code .
-bash: /mnt/c/Users/me/AppData/local/Programs/Microsoft VS Code/bin/code: No such file or directory

If you could leave the old code there and swap it with the new code once update is complete it may provide a nicer experience.

How long does it take for Code to update in the background in your case?

It's not a long time, this is the first I've seen it so I haven't measured.
I'd have thought it would be a simple upgrade to make the new one at code.new and then just mv code code.old && mv code.new code at the end of the update. Obviously oversimplified example.

I will have to close this as won't fix, it's just not worth the engineering effort as it would further complicate things during the already error-prone update phase. The command code comes back as soon as the update is done, right?

Yes it does come back immediately after update so it's only missing a short time.
Thanks for your time considering this.


fix: gap identification and improve gap statistics and visualization

fixed an issue in which entries of multiple rows with the same timestamp contributed to misidentification of gaps
corrected the gap statistics to consider only the identified gaps instead of all data intervals and improved the wording of the metrics

It is approved but the tests are failing though.

Codecov Report
Patch coverage: 47.05% and project coverage change: -0.09% :warning:

Comparison is base (e35840f) 89.52% compared to head (a279455) 89.44%.
Report is 1 commits behind head on develop.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #1423      +/-   ##
===========================================
- Coverage    89.52%   89.44%   -0.09%
===========================================
  Files          194      194
  Lines         6331     6345      +14
===========================================
+ Hits          5668     5675       +7
- Misses         663      670       +7

Flag
Coverage Δ

py3.8-ubuntu-22.04-pandas
89.44% <47.05%> (-0.09%)
:arrow_down:

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

Files Changed
Coverage Δ

src/ydata_profiling/model/pandas/utils_pandas.py
46.15% <0.00%> (-8.40%)
:arrow_down:

src/ydata_profiling/report/structure/overview.py
93.54% <ø> (ø)

...ofiling/model/pandas/describe_timeseries_pandas.py
89.00% <85.71%> (-0.37%)
:arrow_down:

...ng/report/structure/variables/render_timeseries.py
94.73% <100.00%> (+0.29%)
:arrow_up:

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-yml-archive-non-versioning-archive/pull/456 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-yml-archive-non-versioning-archive.git

Docs Build status updates of commit 373feda:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/TOC.yml
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-1.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-2.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-3.yml
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-1.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-2.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-3.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


PowerToys Update Issue

Microsoft PowerToys version
<IP_ADDRESS>
Installation method
PowerToys auto-update
Running as admin
Yes
Area(s) with issue?
General
Steps to reproduce
PowerToysReport_2023-07-13-08-44-25.zip
✔ Expected Behavior
Notification of update success and laptop to boot to Login Screen.
❌ Actual Behavior
At Desktop Pop-up Window (PowerToys Run ran into an issue) stated "Something went wrong"
with following:
Version: <IP_ADDRESS>
OS Version: Microsoft Windows NT 10.0.23493.0
IntPtr Length: 8
x64: True
Date: 2023/07/13 08:14:14
Exception:
System.IO.FileNotFoundException: Could not find file 'C:\Program Files\PowerToys\modules\launcher\Images\app.dark.png'.
File name: 'C:\Program Files\PowerToys\modules\launcher\Images\app.dark.png'
at Microsoft.Win32.SafeHandles.SafeFileHandle.CreateFile(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options)
at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize, Nullable1 unixCreateMode)    at System.IO.Strategies.OSFileStreamStrategy..ctor(String path, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize, Nullable1 unixCreateMode)
at System.IO.Strategies.FileStreamHelpers.ChooseStrategyCore(String path, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize, Nullable`1 unixCreateMode)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
at System.Windows.Media.Imaging.BitmapDecoder.SetupDecoderFromUriOrStream(Uri uri, Stream stream, BitmapCacheOption cacheOption, Guid& clsId, Boolean& isOriginalWritable, Stream& uriStream, UnmanagedMemoryStream& unmanagedMemoryStream, SafeFileHandle& safeFilehandle)
at System.Windows.Media.Imaging.BitmapDecoder.CreateFromUriOrStream(Uri baseUri, Uri uri, Stream stream, BitmapCreateOptions createOptions, BitmapCacheOption cacheOption, RequestCachePolicy uriCachePolicy, Boolean insertInDecoderCache)
at System.Windows.Media.Imaging.BitmapImage.FinalizeCreation()
at Wox.Infrastructure.Image.ImageLoader.Initialize(Theme theme)
at PowerLauncher.App.<>c__DisplayClass19_0.b__0()
at Wox.Infrastructure.Stopwatch.Normal(String message, Action action)
at PowerLauncher.App.OnStartup(Object sender, StartupEventArgs e)
at System.Windows.Application.<.ctor>b__1_0(Object unused)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
Other Software
No response

Same.

Version: <IP_ADDRESS>
OS Version: Microsoft Windows NT 10.0.22621.0
IntPtr Length: 8
x64: True
Date: 7/17/2023 10:03:53 AM
Exception:
System.IO.FileNotFoundException: Could not find file 'C:\Program Files\PowerToys\modules\launcher\Images\app.dark.png'.
File name: 'C:\Program Files\PowerToys\modules\launcher\Images\app.dark.png'
at Microsoft.Win32.SafeHandles.SafeFileHandle.CreateFile(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options)
at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize, Nullable1 unixCreateMode)    at System.IO.Strategies.OSFileStreamStrategy..ctor(String path, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize, Nullable1 unixCreateMode)
at System.IO.Strategies.FileStreamHelpers.ChooseStrategyCore(String path, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize, Nullable`1 unixCreateMode)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
at System.Windows.Media.Imaging.BitmapDecoder.SetupDecoderFromUriOrStream(Uri uri, Stream stream, BitmapCacheOption cacheOption, Guid& clsId, Boolean& isOriginalWritable, Stream& uriStream, UnmanagedMemoryStream& unmanagedMemoryStream, SafeFileHandle& safeFilehandle)
at System.Windows.Media.Imaging.BitmapDecoder.CreateFromUriOrStream(Uri baseUri, Uri uri, Stream stream, BitmapCreateOptions createOptions, BitmapCacheOption cacheOption, RequestCachePolicy uriCachePolicy, Boolean insertInDecoderCache)
at System.Windows.Media.Imaging.BitmapImage.FinalizeCreation()
at Wox.Infrastructure.Image.ImageLoader.Initialize(Theme theme)
at PowerLauncher.App.<>c__DisplayClass19_0.b__0()
at Wox.Infrastructure.Stopwatch.Normal(String message, Action action)
at PowerLauncher.App.OnStartup(Object sender, StartupEventArgs e)
at System.Windows.Application.<.ctor>b__1_0(Object unused)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

This issue is still unresolved. Failed to mention that, the Issue occurs with every Boot of the Windows 11 OS. Thus everytime they intend to use their Windows based system, the first thing they are presented with is a pop-up full forward in the window stack Error. Please address the issue and let us know if/when this issue will be addressed so we may decide whether or not to uninstall/reinstall/other. Thank you for your hard work on a brilliant product.

this should be fixed with 0.71.  @WFVincent your report above shows .69, can you please test with .71?

/needinfo

if it fails, /reportbug

So Sorry, here are both the original (07/130 and todays (24).
It happens every boot but i did not make a bug report for all. If you need any more info, please don't hesitate to contact. My end email issue has been fixed in house. 🙂
WF

From: microsoft-github-policy-service[bot] @.>
Sent: Friday, July 21, 2023 09:09
To: microsoft/PowerToys @.>
Cc: WFVincent @.>; Mention @.>
Subject: Re: [microsoft/PowerToys] PowerToys Update Issue (Issue #27392)
Hi there!
We need a bit more information to really debug this issue. Can you add a "Report Bug" zip file here?  Then drag the zipfile from your desktop onto the GitHub comment box in this issue. Thanks!
[Report Bug]https://user-images.githubusercontent.com/11349917/133042052-4975be21-4699-4363-83c9-a8e1869d079d.png
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/PowerToys/issues/27392#issuecomment-1644769044, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BBHSOY622HGD6IPHE2QMXZ3XRG3DXANCNFSM6AAAAAA2ID7DLU.
You are receiving this because you were mentioned.Message ID: @.***>

Not able to repro this, going to close. Let us know if you see this again!


If you try to send it, "Invalid address" appears.

My LTC Wallet is LoafWallet
Litecoin purse address beginning with 3H. (3H9836PmP4NmwMiVpdqQSppLwDZ8FTwh7f)
If you try to send it, "Invalid address" appears.

Hi,
The address you are sending to is a P2SH address.
It looks like it's been formatted incorrectly. P2SH addresses should start
with a 'M' not a '3'.
You can convert this address using:
https://litecoin-project.github.io/p2sh-convert/
Please also contact the app/site developer who generated the address
starting with a '3' and tell them that they are using the incorrect
Litecoin P2SH prefix.
Thanks,
Loshan
On 2 March 2018 at 08:04, Mun-Kyo Seo<EMAIL_ADDRESS>wrote:

My LTC Wallet is LoafWallet
Litecoin purse address beginning with 3H. (3H9836PmP4NmwMiVpdqQSppLwDZ8FT
wh7f)
If you try to send it, "Invalid address" appears.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/litecoin-foundation/loafwallet-ios/issues/17, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACfNundgMQIE-aCRgsmWYQ3z3EeEdcz6ks5taP0KgaJpZM4SZiCG
.

Closing due to inactivity & expected behaviour.


Reboot Log produces two entries on os_mgmt and shell_os reset.

Two reboot log entries (instead of one) are produced whenever the system is reset either from shell or from newtmgr (mcumgr).

The problem is that most apps call reboot_start() before configuration gets loaded from flash.  Consequently, the log_reboot_written setting is always 0.  This causes the firmware to write a new entry every time it boots up (even if it already wrote one when it shut down).


Initial libstd support

This PR contains two patches required to allow unwinding to be used with libstd.
As background, I'm porting libstd to the Xous operating system. This is an embedded target.
In the past I've applied patches to libunwind in order to get it to work, however those patches are very difficult to get upstream. A recent change in llvm made C compiling difficult (https://reviews.llvm.org/D156642), and additional patches will be needed on top of Rust's hacked-up version of LLVM that adds support for SGX.
With these patches, along with an unwinding backend for the Rust unwind crate, I'm able to run tests and catch panics in Xous.
This patchset does two things:

Add support for making core optional, which is necessary for building as part of the tree
Make text_base optional, which is required due to the fact that Xous doesn't have this information and no platforms currently use it anyway

While it's true that (2) is an API-level change, this API is not documented in either docs.rs or the examples/ directory, so I'm not sure how widely used it is.

I believe the base address can be zero. Probably just using Option<usize> is fine?

Good point -- I've adjusted the API accordingly.

CI is failing due to rust-lang/rust#108955 denying lang_items feature and rust-lang/rust#112849 changing the panic display output. Fix in progress...

On the implementation side; do you think it makes sense to just use 0 as text_base when it's unknown instead of None? If textrel is not actually used, then setting it to 0 wouldn't actually cause any problem? I am a little bit reluctant to make this Option because it'll be a semver-breaking change.
I think you mentioned in Zulip the issue is that LLVM doesn't expose the start of text section by default? Could you give more context about this, and how do you define the custom FDE finder? We might be able to find a solution to use one of the existing FDE finder or get the text base using some other method.

How does the text_base currently get set for a platform that requires this to be non-zero.
Also it makes sense for this to be a usize instead of an Option<usize> due the reason Some(0) and None have the same meaning. Instead if you do use Option<NonZeroUSize> to keep the ABI same due to the guaranteed NPO that might be better.

If you try to get textrel base when it's not set, you get a panic (which will get turned into abort), so it's not exactly the same as getting a zero.
However it was pointed out that textrel base isn't actually being used and LLVM libunwind does not support it, so it won't have any observable difference. GCC's unwinder does support textrel and will report 0 if not set, but from some digging it seems that it was only used by IA64 and some other non-mainstream architectures and they are no longer generating it.

If you try to get textrel base when it's not set, you get a panic (which will get turned into abort), so it's not exactly the same as getting a zero.

Ah I see; thanks for the explanation. How does it impact whether it's set or not; is it purely during what IP is returned? In which case if it isn't supported anymore is the caller expected to be doing the textrel base offsetting to get the non-reloced address? Are there reasons on why the design choice was made by llvm to not support it?

However it was pointed out that textrel base isn't actually being used and LLVM libunwind does not support it, so it won't have any observable difference. GCC's unwinder does support textrel and will report 0 if not set, but from some digging it seems that it was only used by IA64 and some other non-mainstream architectures and they are no longer generating it.

That makes sense, in that case I can see why Option does make sense here to denote the fact that it can be set or not. What do you think about the Option<NonZeroUsize> idea since gcc's set but 0 means the same thing in this case.

No, Option<NonZeroUsize> doesn't make sense because the textrel base can be set and be zero.

I've rebased on top of trunk.
I think that Option<usize> is the best option going forward, but I don't know what to do about existing targets. I see two dependencies on crates.io, neither of which uses the custom unwinder.
What if all of the unwinders were changed to Option<usize> and this made a 0.3.0 release? I believe that's allowed under semver, since it's 0.x.y.

I'll take this as part of 0.2.0 release. There're some functions that are not supposed to be safe exposed in unwinding::abi and I'd like to fix these, which also is semver breaking change anyway.


pkg/util/browser: Refactored Code

Removed unnecessary if condition
Added test cases for browser.open

Zero values
Variables declared without an explicit initial value are given their zero value.
https://play.golang.org/p/rpSP8JwaVn


Fix SelfAskOutputParser (from langchain.agents.self_ask_with_search.output_parser)

Description of the change
By replacing hard coded position of "follow up" and "final output" pattern with regex pattern matching using "re" I reduce failed outputs like markdown list or any multiline outputs
Example of the issue:
from langchain import OpenAI, SerpAPIWrapper
from langchain.agents import initialize_agent, Tool
from langchain.agents import AgentType

llm = OpenAI(temperature=0)
search = SerpAPIWrapper()
tools = [
    Tool(
        name="Intermediate Answer",
        func=search.run,
        description="useful for when you need to ask with search",
    )
]

self_ask_with_search = initialize_agent(
    tools, llm, agent=AgentType.SELF_ASK_WITH_SEARCH, verbose=True
)
out = self_ask_with_search.run(
    "List men and women Rolland Garros winners between 2020 and 2023?"
)
-------------------------
> Entering new AgentExecutor chain...
 Yes.
Follow up: Who won the men's Rolland Garros in 2020?
Intermediate answer: Three-time defending champion Rafael Nadal defeated Novak Djokovic in the final, 6–0, 6–2, 7–5 to win the men's singles tennis title at the 2020 French Open.

Follow up: Who won the women's Rolland Garros in 2020?
Intermediate answer: Iga Świątek defeated Sofia Kenin in the final, 6–4, 6–1 to win the women's singles tennis title at the 2020 French Open.

Follow up: Who won the men's Rolland Garros in 2021?
Intermediate answer: Novak Djokovic defeated Stefanos Tsitsipas in the final, 6–7(6–8), 2–6, 6–3, 6–2, 6–4 to win the men's singles tennis title at the 2021 French Open.

Follow up: Who won the women's Rolland Garros in 2021?
Intermediate answer: Barbora Krejčíková defeated Anastasia Pavlyuchenkova in the final, 6–1, 2–6, 6–4 to win the women's singles tennis title at the 2021 French Open.

Follow up: Who won the men's Rolland Garros in 2022?
Intermediate answer: Rafael Nadal defeated Casper Ruud in the final, 6–3, 6–3, 6–0 to win the men's singles tennis title at the 2022 French Open. It was his record-extending ...

Follow up: Who won the women's Rolland Garros in 2022?
Intermediate answer: Iga Świątek defeated Coco Gauff in the final, 6–1, 6–3 to win the women's singles tennis title at the 2022 French Open. It was her second French Open title, ...

Follow up: Who won the men's Rolland Garros in 2023?
Intermediate answer: Novak Djokovic defeated Casper Ruud in the final, 7–6(7–1), 6–3, 7–5 to win the men's singles tennis title at the 2023 French Open. It was his third French ...

Follow up: Who won the women's Rolland Garros in 2023?
Intermediate answer: World number one Iga Swiatek clinched her third French Open and fourth Grand Slam title of her career on Saturday with an epic three-set ...
---------------------------------------------------------------------------
OutputParserException                     Traceback (most recent call last)
...
File /usr/local/Caskroom/miniconda/base/envs/py_3_10/lib/python3.10/site-packages/langchain/agents/self_ask_with_search/output_parser.py:17, in SelfAskOutputParser.parse(self, text)
     15 if not any([follow in last_line for follow in self.followups]):
     16     if self.finish_string not in last_line:
---> 17         raise OutputParserException(f"Could not parse output: {text}")
     18     return AgentFinish({"output": last_line[len(self.finish_string) :]}, text)
     20 after_colon = text.split(":")[-1].strip()

OutputParserException: Could not parse output: So the final answer is:
2020: Men's - Rafael Nadal, Women's - Iga Świątek
2021: Men's - Novak Djokovic, Women's - Barbora Krejčíková
2022: Men's - Rafael Nadal, Women's - Iga Świątek
2023: Men's - Novak Djokovic, Women's - Iga Świątek

Using regex matching now we obtain a correct answer:
> Entering new AgentExecutor chain...
 Yes.
Follow up: Who won the men's singles at the 2020 French Open?
Intermediate answer: Rafael Nadal
Follow up: Who won the women's singles at the 2020 French Open?
Intermediate answer: Iga Swiatek
Follow up: Who won the men's singles at the 2021 French Open?
Intermediate answer: Novak Djokovic
Follow up: Who won the women's singles at the 2021 French Open?
Intermediate answer: Barbora Krejčíková
Follow up: Who won the men's singles at the 2022 French Open?
Intermediate answer: Rafael Nadal
Follow up: Who won the women's singles at the 2022 French Open?
Intermediate answer: Iga Swiatek
Follow up: Who won the men's singles at the 2023 French Open?
Intermediate answer: Novak Djokovic
Follow up: Who won the women's singles at the 2023 French Open?
Intermediate answer: Iga Swiatek
So the final answer is:
2020: Rafael Nadal (men's singles) and Iga Swiatek (women's singles)
2021: Novak Djokovic (men's singles) and Barbora Krejčíková (women's singles)
2022: Rafael Nadal (men's singles) and Iga Swiatek (women's singles)
2023: Novak Djokovic (men's singles) and Iga Swiatek (women's singles)

> Finished chain.

thanks @jeanbaptistepriez! could we add some unit tests for this?

thanks @jeanbaptistepriez! could we add some unit tests for this?

Unit tests have been added (but I'm not able to execute make test I obtain multiple issues not linked to those new tests => those new tests are working using pytest in the dedicated folder).

@baskaryan any update?

@jeanbaptistepriez Hi , could you, please, resolve the merging issues? After that ping me and I push this PR for the review. Thanks!

Looks like this isn't being worked on anymore. I'll close for now, and if you resume work, feel free to reopen!
@jeanbaptistepriez if you're having trouble setting up unit testing locally, feel free to ask for help in Discord or try running them in docker! https://github.com/langchain-ai/langchain/blob/master/.github/CONTRIBUTING.md#testing


New Dashboard - pod logs bottom not visible

What kind of request is this (question/bug/enhancement/feature request):
bug
Steps to reproduce (least amount of steps as possible):
On Rancher web ui, select any cluster, click on the "Try Dashboard" button, select Pod from the left navigation column, select View Logs from the popup menu of any pod on the right.
Result:
The bottom of the log is not visible, regardless of the scroll position.
Other details that may be helpful:
The browser is Chrome Version 81.0.4044.113 (Official Build) (64-bit)
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): v2.4.4
Installation option (single install/HA): HA

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): Custom
Machine type (cloud/VM/metal) and specifications (CPU/memory): VMWare instances
Kubernetes version (use kubectl version): v1.17.6

(paste the output here)

Docker version (use docker version): 18.9.1

(paste the output here)

This is fixed already for the next release, logs and shell now go in a tabbed tray at the bottom so you can have more than one of them up at a time and switch between them.


feat: Support printing more types

Description
Problem*
As part of our debugger implementation (see #3015) we need to extend the supported types that can be printed. We are using noirc_printable_type to keep values of variables at runtime for debug inspection.
Also resolves #4073
Summary*
This PR adds support for converting these new types:

Tuples
Slices: lift the restriction to print them and handle arrays with dynamic size (flagging them with a None length in the type)
Functions: printed as an opaque <<function>> tag for now
Mutable references: printed as an opaque <<mutable ref>> tag for now
Unit: this is actually required to fully support function type conversion, for non-closured function references (ie. the environment is () in that case)

The PR also fixes a preexisting bug when printing multiple values using formatted strings with the first ones being structs. Since structs are expanded into tuples which take up more than one field, the printing code would fail to skip over all the fields of the struct.
Additional Context
I've been using this program to test this functionality. If it makes sense, I can add it as an integration test to test_programs/execution_success.
The program produces this output:
(0x01, 0x02, 0x03)
0xbbbb # a = (0x01, 0x02, 0x03) # 0xeeee
(0x01, 0x02, 0x03) == (0x01, 0x02, 0x03)

((0x01, 0x02, 0x03), 0x04, 0x05, 0x06)
0xbbbb # b = ((0x01, 0x02, 0x03), 0x04, 0x05, 0x06) # 0xeeee
((0x01, 0x02, 0x03), 0x04, 0x05, 0x06) == ((0x01, 0x02, 0x03), 0x04, 0x05, 0x06)

<<mutable ref>>
0xbbbb # c = <<mutable ref>> # 0xeeee

<<function>>
0xbbbb # d = <<function>> # 0xeeee

<<function>>
0xbbbb # f = <<function>> # 0xeeee

[0x01, 0x02, 0x03]
0xbbbb # g = [0x01, 0x02, 0x03] # 0xeeee
[0x01, 0x02, 0x03] == [0x01, 0x02, 0x03]

Foo { x: 555, y: 666 } == Foo { x: 555, y: 666 }

Vec { slice: [0x01, 0x02] }
0xbbbb # h = Vec { slice: [0x01, 0x02] } # 0xeeee

[0x01, 0x02]
0xbbbb # j = [0x01, 0x02] # 0xeeee
[0x01, 0x02] == [0x01, 0x02]

[printable_types] Circuit witness successfully solved

Documentation*
Check one:

[X] No documentation needed.
[ ] Documentation included in this PR.
[ ] [Exceptional Case] Documentation to be submitted in a separate PR.

PR Checklist*

[X] I have tested the changes locally.
[X] I have formatted the changes with Prettier and/or cargo fmt on default settings.

Thanks for the PR I was actually just adding Tuple types for printing and you beat me to it :).
Could you add that test under test_programs/execution_success. We also have a debug_logs test where you can add those cases.
Could you elaborate on this line in the gist you linked?

The PR also fixes a preexisting bug when printing multiple values using formatted strings with the first ones being structs. Since structs are expanded into tuples which take up more than one field, the printing code would fail to skip over all the fields of the struct.

Is there an issue for this bug? Or did you find it on your own?

The PR also fixes a preexisting bug when printing multiple values using formatted strings with the first ones being structs. Since structs are expanded into tuples which take up more than one field, the printing code would fail to skip over all the fields of the struct.

Is there an issue for this bug? Or did you find it on your own?

I just found it while inspecting the printing code. I don't think there's an issue for it. I can create it, no problem.

What happens in the case where a type doesn't work w/ ACIR output such as slices or Vectors? Does it just panic?

Oh, right! I'll try adding the new cases to debug_logs. Thanks!

It would be great if you could post the output here as well.

What happens in the case where a type doesn't work w/ ACIR output such as slices or Vectors? Does it just panic?

It doesn't compile. Seems related to the restriction on slices for Brillig entry points:
The application panicked (crashed).
Message:  not implemented: Unsupported slices as parameter
Location: compiler/noirc_evaluator/src/brillig/brillig_ir/entry_point.rs:67

It doesn't compile. Seems related to the restriction on slices for Brillig entry points:

Ah yeah this is currently unsupported as we need to know the exact number of parameters we are passing to a Brillig entry point. We could add support for slices as parameters to Brillig entry points but this is a larger change. Tbh right now I lean towards not supporting slices in the debugger if this is necessary for your work.
Being able to print in Brillig then getting a panic of "Unsupported slices as parameter" when printing in ACIR is going to be confusing to users.

It doesn't compile. Seems related to the restriction on slices for Brillig entry points:

Ah yeah this is currently unsupported as we need to know the exact number of parameters we are passing to a Brillig entry point. We could add support for slices as parameters to Brillig entry points but this is a larger change. Tbh right now I lean towards not supporting slices in the debugger if this is necessary for your work.
Being able to print in Brillig then getting a panic of "Unsupported slices as parameter" when printing in ACIR is going to be confusing to users.

I understand. We will have a similar problem with mutable references though. In that case the compiler fails with:
The application panicked (crashed).
Message:  internal error: entered unreachable code: Expected all allocate instructions to be removed before acir_gen
Location: compiler/noirc_evaluator/src/ssa/acir_gen/mod.rs:579

I understand. We will have a similar problem with mutable references though. In that case the compiler fails with:

Hmm I see. Then we should add a type check of some sort that will return an error if we are attempting to call println w/ mutable references or slices from ACIR.

I understand. We will have a similar problem with mutable references though. In that case the compiler fails with:

Hmm I see. Then we should add a type check of some sort that will return an error if we are attempting to call println w/ mutable references or slices from ACIR.
We probably could do this check during SSA gen as a FunctionContext will store the runtime type of the function for which we are generating SSA.

If we want to limit the types for printing, then append_printable_type_info_inner looks like the best place to put the checks. AFAIK that's only used when handling print/println from the stdlib. That would still allow the debugger instrumentation code to pass slices and mutable references. And since we're (at least initially) planning to inject the instrumentation code only when compiling in Brillig mode, the debugger would still work for most cases.
As requested above, I filed the bug re: passing structs and multiple arguments and added the new printable types to the debug_logs sample. I put the problematic cases in a separate function, so we can disable/remove them easily if necessary.

If we want to limit the types for printing, then append_printable_type_info_inner looks like the best place to put the checks. This will affect both Brillig and ACIR output modes, and should remove the source of confusion.
AFAIK that code is only used when handling print/println from the stdlib. This would still allow the debugger instrumentation code to pass slices and mutable references to the oracle functions. And since we're (at least initially) planning to inject the instrumentation code only when compiling in Brillig mode, the debugger would still work for most cases.
As requested above, I filed the bug re: passing structs and multiple arguments and added the new printable types to the debug_logs sample. I put the problematic cases in a separate function, so we can disable/remove them easily if necessary.

Yeah currently that code is only used when handling print/println from the stdlib. I'm working on enabling assert messages to be able to print more than just strings literals so this will most likely change in the future, but continue as you have been as that work is still in flux. If you are able to add the checks and still allow the debugger instrumentation code then I am good with that. I just don't want users to see  Unsupported slices as parameter rather than something like Slices are unsupported to be printed from constrained code.
Will give the code another look!


ENH updates for v2.2.0

This PR has updates for the v2.2.0 release. I will tag it once the PR is merged.

Done @mheilman. Back to you!


Migration path for reliable services / actors

The new stuff looks really great!
However we're very heavily invested in the "old" programming models, actors in particular and reliable services (with remoting) as well. I understand there would be some modification needed, but what would the migration path be? I think a large majority of existing SF apps will be in a similar situation since the Actor/reliable service models have been pushed so heavily in the past.

I've got questions from customers about Mesh, and we always end up with the same conclusion that without Reliable Collections/Actors it's a show-stopper, at least for those who are already heavy SF users.
Mesh as managed infrastructure is just fine.

I've got questions from customers about Mesh, and we always end up with the same conclusion that without Reliable Collections/Actors it's a show-stopper, at least for those who are already heavy SF users.
Mesh as managed infrastructure is just fine.


Attempt to reproduce segfault reported in #574

@vmarkovtsev I'm trying to reproduce the error you reported that we documented in #574. This seems to work fine for me, though, so I must be missing something.

Coverage remained the same at 93.647% when pulling 82139013c7f78f3d6a2c6a570da865f92e2916ad on drdavella:reproduce-segfault into efca1032748afff512b8162b9a237fb4787d714e on spacetelescope:master.

🤔


Initial implementation of the authorization screen

Initial design based from https://solid.github.io/data-interoperability-panel/primer/authorization-agent.html#gathering-authorizations

Can we start with All scope so that we can connect everything together?
After that, we could be adding more granular scopes, one per PR.

Initial work in #47

Authorize button shouldn't appear until the whole authorization information is displayed

While not completed, some work has been merged with #58. I'll close this in favor or more granular issues.


Issue with /docs/tasks/manage-gpus/scheduling-gpus/

Problem: GPU user guide has the scheduler.alpha.kubernetes.io/affinity annotation used in is no longer valid as nodeAffinity has moved to beta and has its own field now.
Proposed Solution: Replace scheduler.alpha.kubernetes.io/affinity annotation with nodeAffinity field in the snippet.
Page to Update: https://kubernetes.io/docs/tasks/manage-gpus/scheduling-gpus/

/assign @vishh


Added new development gems

@AndreaOlivieri you can edit the first entry of the PR and write there. No need to write stuff on the code lines unless required. ;)


replace fxhash crate with rustc-hash

The rust performance book recommends using rustc-hash instead of fxhash for maintenance reasons - https://nnethercote.github.io/perf-book/hashing.html
"rustc-hash provides FxHashSet and FxHashMap types that are drop-in replacements for HashSet and HashMap. Its hashing algorithm is low-quality but very fast, especially for integer keys, and has been found to out-perform all other hash algorithms within rustc. (fxhash is an older, less well maintained implementation of the same algorithm and types.)"
Do you see any reasons against this? Let me know what you think!

This looks good to me :)


x/pkgsite:Missing type string on the first parameter of Split function.

What is the URL of the page with the issue?
https://pkg.go.dev/strings#Split
Screenshot

What did you do?
Access the docs page.
What did you expect to see?
The type of the s parameter in the split function.
What did you see instead?
No type for the s parameter.

That's how the language works.
Unlike many projects, the Go project does not use GitHub Issues for general discussion or asking questions. GitHub Issues are used for tracking bugs and proposals only.
For questions please refer to https://github.com/golang/go/wiki/Questions


Benchmarks code gen vs reflection

I'd be curious about what this affect build times compared to using a reflection based mocking library like mockk vs having the code generated fakes like this

I would like to figure out a good way to actually benchmark this, as in this repo it's basically
:sample:kspTestKotlin + :sample:compileTestKotlin+:sample:test(unscientific average of 3 runs of this is ~2469ms) vs:sample:compileTestKotlin+:sample:test` (unscientific average 3 runs of this is ~2930ms)

In theory the savings could be better if :sample:kspTestKotlin and :sample:compileTestKotlin are both cached but the tests still need to run, as the :sample:test run is at least 3x as long (on larger tests i have seen it be more like 5x)

Gradle profiler would be good for this. We could profile the test task for projects that use mockingbird vs mockk.
It might also be helpful to write a script to generate a large project (100+ modules) to do a more thorough benchmark. The Tangle docs have that which is nice.

I ran some preliminary basic benchmarks of clean :sample:test while disabling the tests that expect exceptions and adding in dagger code gen to normalize the difference in compile speed of not having to run ksp if mockingbird isn't enabled. The performance is basically the same. It would be better to do profiling on a larger project like you mentioned though.
mockingbird-benchmark.csv
mockk-benchmark.csv


Fixed issue #1451

Pull Request Type
What kind of change does this PR introduce?
[ *] Solved an issue/task
[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:
What is the current behavior?
Features:

Real-time clock display
Hour, minute, and second hands
Hour numbers 1 to 12

Issue Number: [Insert Issue Number (if applicable)]
What is the new behavior?

Other information

Merged

This is an automated message from Fork, Commit, Merge [BOT].

Thank you for your contribution! Your pull request has been merged. The files have been reset for the next contributor.
What's next?
If you're looking for more ways to contribute, I invite you to check out our forkcommitmerge.io website repository. The repository contain real issues that you can help to resolve or create some of your own if you see any bugs or want to add new features to the site, etc. You can also check out the Influences section in the README to find more projects similar to this one.
Also please leave a star to this project if you feel it helped you, i would really appreciate it.
I look forward to seeing your contributions!


proposal: expose the internal/runtime/sys.Prefetch intrinsic

Proposal Details
I'm working on a concurrent hash map and with me having experience in using them in highly concurrent contexts with high throughput requirements I knew to add batch Put and Get methods to it. Such API design exposes the very obvious opportunity for prefetching the data.
To experiment with the impact of internal/runtime/sys.Prefetch on the batch Get call I modified runtime/panic.go to expose the intrinsic. go tool objdump then confirmed that a PREFETCHT0 instruction is emitted into the binary as expected.
// in runtime/panic.go
func Prefetch(addr uintptr) {
	sys.Prefetch(addr)
}

// and using it like this
for _, bucket := range initial_buckets_for_keys {
	runtime.Prefetch(uintptr(unsafe.Pointer(bucket)))
}

Looking up 100k distinct entries from a hash map with 5000k entries became significantly faster.
old: BenchmarkLookupBatches/size=100000-8                      63.14 million_lookups/s
new: BenchmarkLookupBatches/size=100000-8                      96.64 million_lookups/s

Which looks like a worthwhile optimization for me.
I personally like how for me this runtime.Prefetch Just Works™ so I propose adding just it. I also propose to not tell of it's addition in the change log so people don't use it willy-nilly. Just imagine the damage that all the blog spam will cause in the overall ecosystem, possibly leaking into other language communities too.

This is clearer and easier to use:
func Prefetch[E any, P ~*E | ~unsafe.Pointer](P)

Does this have any memory model interactions ?
For example does anything happens if we call prefetch concurrently of writes to the same address ?

I also propose to not tell of it's addition in the change log

:-1:

so people don't use it willy-nilly.

:+1:
I think it would be more effective if we put it in unsafe.Prefetch.

Lastly I'm not sure how easily portable to other architectures that would be.

Does this have any memory model interactions ?
For example does anything happens if we call prefetch concurrently of writes to the same address ?

There are no memory model interactions here.  A prefetch by definition does not change the meaning of a program, it only affects the execution time.
On an architecture that doesn't have a prefetch instruction, the proposed function would be a no-op.
It's worth noting that amd64 has at least six different kinds of prefetch instructions.  The GCC compiler __builtin_prefetch intrinsic permits specifying up to three arguments: the address, a read/write flag, and locality.  The read/write flag is 0 for a read, 1 for a write.  The locality ranges from 0, meaning no temporal locality and there is no reason to cache the data at all after the actual memory access, to 3, meaning high locality and the value should be left in all caches if at all possible.

There are no memory model interactions here.

I thought it would be able to generate pagefaults which can be turned into callbacks with signals but after going over the docs at least on amd64 it does not.

On an architecture that doesn't have a prefetch instruction, the proposed function would be a no-op.

I'm more worried about architectures that don't implement it the same way.
This looks like the kind of things that could improve on a particular CPU, but pessimize on an other one.

Bordering off-topic but apparently some mutex implementations use PREFETCHW when spinning. AMD64 manual does say that

"... However, prefetching write data takes longer than prefetching read data if the processor must wait
for another caching master to first write-back its modified copy of the requested data to memory
before the prefetch request is satisfied."

which one could read as stalling until the other CPU core is done with the cache-line, possibly yielding the CPU time to a virtual core when hyper-threading is enabled. It also sounds useful in my use case considering that all of my buckets happen to carry a sync.Mutex and the very first thing that I do with buckets is to mu.Lock() it. But I can also see ways in how it could go wrong compared to the smooth brained PREFETCHT0. The result of a biased coin flip tells me that the addition of PrefetchInAnticipationOfWriteThatWillComeSoonEnoughJustAFewLinesBelow() is in place.


:memo: change atom build directory to current one [ci skip]

The atom build directory has been changed. The new build directory is out/Atom.

Thanks!


"Upscale 2x" button that actually uses upscale?

Feature Idea
Some way to modify what process the 'upscale 2x' button does would be ideal, but simply having it use the upscale settings instead of whatever it's currently doing with the init image creativity.
Right off the bat, the label is misleading at best, being labeled as 'upscale 2x' one would expect it to use the upscale settings.
Second, the current method of upscaling does not use the upscaler model.
Third, as far as I can tell, I can't even modify the settings it uses, so the 0.4 'creativity' is destroying my images, even if the upscale was otherwise viable (it's not IMO)
Fourth, part of it's process is to completely regen the original image and then upscaling, wasting cycle time compared to simply turning on the upscale tab and reusing the seed.
In my mind, solving this could be done in a number of ways.
At the minimum, a second button that simply uses the current upscaler settings (and maybe make the current one use the currently user set settings not whatever it uses)
At best, some way of making custom "turn these things on, generate with current settings, turn them back off" buttons would be amazing.
Other
No response

Submitted a pull request for this here - #308
I added a setting for the current "Upscale 2x" button to change how much creativity is being used (0.4 is heavy handed IMO). Ultimately left the function and default value alone for backwards compatibility and those that like the way it currently works.
Added a second button called "Refine Image" that reuses the current images seed and enables the "Refine / Upscale" section and generates an image using the existing settings, then disables the section and resets the seed to random (-1).

Solved with merge of #312


[Question]: How to use an OpenAI compatible API?

Question Validation

[X] I have searched both the documentation and discord for an answer.

Question
For example, GooseAI is AI compatible...
This works
import openai
openai.api_key = "sk-hidemykey"
openai.api_base = "https://api.goose.ai/v1"
completion = openai.Completion.create(
  engine="gpt-j-6b",
  prompt="What is a Goose?",
  max_tokens=250,
  stream=True)
for c in completion:
  print (c.choices[0].text, end = '')

but this fails
from llama_index.llms import OpenAI
resp = OpenAI(
    model="gpt-j-6b",
    api_key="sk-hidemykey",
    api_base="https://api.goose.ai/v1").complete("What is a goose?")

ValueError: Unknown model 'gpt-j-6b'. Please provide a valid OpenAI model name in: gpt-4, gpt-4-32k, gpt-4-0613, gpt-4-32k-0613, gpt-4-0314, gpt-4-32k-0314, gpt-3.5-turbo, gpt-3.5-turbo-16k, gpt-3.5-turbo-0613, gpt-3.5-turbo-16k-0613, gpt-3.5-turbo-0301, text-davinci-003, text-davinci-002, gpt-3.5-turbo-instruct, text-ada-001, text-babbage-001, text-curie-001, ada, babbage, curie, davinci, gpt-35-turbo-16k, gpt-35-turbo
It seems that even though I change the api_base, it restricts itself to static openai models

PR in progress: https://github.com/run-llama/llama_index/pull/7973
will try to get that merged soon 🙏🏻


Allow for empty replacement string

Allows for empty replacement string, in case the user wants to replace something by nothing. Not sure why I removed it in the last PR, but thanks @ibilon for telling me. Fix for #1172

@BenStigsen thanks for the patch.


[Draft] Implement shell quorum balancing

Issues:

Issue #824 should be resolved. I included a hacky workaround in the commit titled Allow re-enrolling validators if they're enrolled. I think I could possibly rewrite the test to avoid this issue.
The last two commits can / should be merged, but for simplicity I implemented them separately.
There are some strange segfaults, but they disappear when parallelism is removed from the test-suite. Need to investigate.
The NetworkManager really needs to be rewritten. It does not try to connect to new nodes in this PR. I've tried to hack this support in, but realized that code needs to be well refactored before this can be well supported.

The test does the following:

Start with a Genesis block with 4 validators. Quorum config is 4/4
At block 1008 all our validators would expire. So after block 1007 is externalized we re-enroll 2 validators
We try to reach consensus with just the two active validators, and we sleep the other 2 validators. If consensus is still reached, everything is ok. Quorum config is 2/2.
Re-enroll the rest of the validators
Try reaching consensus again. Quorum config is 4/4
Now sleep just one validator
Try reaching consensus. It should fail because only 3/4 Validators reached consensus.

Requires:
~#800~, ~#840~, ~#810~, ~#841~

Update: Added #810 to the list of required PRs. I marked that commit as [delete] in the PR.

Need to fix the integration test.

It seems the test-suite times out (30 minutes). I'm trying to bisect it.

I've discovered that what is causing these failures is actually the code coverage mode. The test-suite works fine without it. But with it there are timeouts. Either the code coverage is significantly slowing down the tests, or there is a bug in the coverage generator code in DMD front-end.

So far I can't reproduce the segfault when running github CI locally, but I can reproduce the timeout issue:
(lldb) bt
error: need to add support for DW_TAG_base_type 'char' encoded with DW_ATE = 0x10, bit_size = 8
* thread #1, queue = 'com.apple.main-thread', stop reason = signal SIGSTOP
  * frame #0: 0x00007fff6099e9de libsystem_kernel.dylib`__ulock_wait + 10
    frame #1: 0x00007fff60a5f6de libsystem_pthread.dylib`_pthread_join + 358
    frame #2: 0x000000010e81e485 agora-unittests`thread_joinAll + 197
    frame #3: 0x000000010e839225 agora-unittests`rt_term + 69
    frame #4: 0x000000010e83977c agora-unittests`_D2rt6dmain212_d_run_main2UAAamPUQgZiZ6runAllMFZv + 172
    frame #5: 0x000000010e839537 agora-unittests`_d_run_main2 + 391
    frame #6: 0x000000010e83939d agora-unittests`_d_run_main + 141
    frame #7: 0x000000010deaecd5 agora-unittests`main(argc=1, argv=0x00007ffee1ea4320) + 37
    frame #8: 0x00007fff608673d5 libdyld.dylib`start + 1

It seems the process is stuck on thread_joinAll

Ok I've added a Thread.sleep call to work around #869, but now there is a consistent segfault in the NetworkClient. I've seen this error before too:
Thread 40 "agora-unittests" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffe836b0700 (LWP 19915)]
0x00000000081a4493 in _D5agora7network13NetworkClientQp12sendPreimageMFNeKSQBz9consensus4data12PreImageInfoQoZ9__lambda2MFZ12__dgliteral1MFNaNiNfZv ()
    at /mnt/c/dev/agora/source/agora/network/NetworkClient.d:327
327                 this.attemptRequest(this.api.receivePreimage(preimage), null);
(gdb)

#2  0x00000000081a444d in _D5agora7network13NetworkClientQp12sendPreimageMFNeKSQBz9consensus4data12PreImageInfoQoZ9__lambda2MFZv ()
    at /mnt/c/dev/agora/source/agora/network/NetworkClient.d:327
327                 this.attemptRequest(this.api.receivePreimage(preimage), null);
(gdb) p api
$1 = (agora.api.Validator.API *) 0x0

So the api is null.

It seems that disabling parallelism fixes the issue. Unfortunately I cannot reproduce the issue locally. And also, when running the CI test-suite under LLDB it also cannot reproduce the issue.

There is something wrong with the implementation of dispatch in FiberScheduler. We lifted it from std.concurrency, and it was documented as an "example scheduler".
This is my workaround which gets rid of segfaults: https://github.com/AndrejMitrovic/localrest/compare/2cf119e759cdbbe2879bf65435efd18084620498...6f35619393bfdfbb4b9f84379da68d8f40c3675a#diff-7e552a35c6e12cbbfb124195a3e45cd2
I would guess that it has something to do with manipulating the m_fibers array both in the dispatch routine and in create(): https://github.com/AndrejMitrovic/localrest/compare/AndrejMitrovic:2cf119e...AndrejMitrovic:6f35619#diff-7e552a35c6e12cbbfb124195a3e45cd2R936
The end result before this patch is that the fiber somehow ends up jumping to a random source code location. So it seems like the fiber gets corrupt somehow.
I still need to work on reducing this further down to a test-case..

It turned green. wow

Blocked on https://github.com/bpfkorea/agora/issues/824
And https://github.com/bpfkorea/agora/pull/889 should improve the way networking is done after the re-shuffle.

Rebased. Still blocked, and I had to revert the change Mathias made in order to fix the tests.

I'll try to unblock this by changing the test to use new validator sets instead of re-enrolling existing validators.

I should split off the first 4 commits so they can be merged right away.

Test-suite passes, but it's flakey unfortunately.
There still seems to be an issue where a task (periodic preimage reveal) starts after a sleep call and ends up segfaulting. I haven't tracked it down yet.

The feature I discovered in https://github.com/Geod24/localrest/pull/81 came in useful. I rewrote one test.

I further simplified the changeset. The diff is much smaller now.

@bpfkorea/core please review when you have time.

I don't think the double clear should block the merge.


Ac template update

add FAQ and Company Communicator

Docs Build status updates of commit f83d3a1:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/samples/app-templates.md
:warning:Warning

Details

msteams-platform/assets/images/CompanyCommunicatorCompose.png
:white_check_mark:Succeeded

msteams-platform/assets/images/FAQPlusEndUser.gif
:white_check_mark:Succeeded

msteams-platform/includes/landing-page.html
:white_check_mark:Succeeded

msteams-platform/samples/app-templates.md

Line 36: [Warning] Invalid file link:(~/assets/images/FAQPlusEndUser.gif).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 23b34b3:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/samples/app-templates.md
:warning:Warning

Details

msteams-platform/assets/images/CompanyCommunicatorCompose.png
:white_check_mark:Succeeded

msteams-platform/assets/images/FAQPlusEndUser.gif
:white_check_mark:Succeeded

msteams-platform/includes/landing-page.html
:white_check_mark:Succeeded

msteams-platform/samples/app-templates.md

Line 36: [Warning] Invalid file link:(~/assets/images/FAQPlusEndUser.gif).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 4c8504e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/CompanyCommunicatorCompose.png
:white_check_mark:Succeeded

msteams-platform/assets/images/FAQPlusEndUser.gif
:white_check_mark:Succeeded

msteams-platform/docfx.json
:white_check_mark:Succeeded

msteams-platform/includes/landing-page.html
:white_check_mark:Succeeded

msteams-platform/samples/app-templates.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


fix(documentation): Adds a second example for JSON

Description
I have added a second example manifest for JSON, after our discussion.
My example may be too verbose. 🤔

Thanks for the Pullrequest, and  I like your example


Pattern search isn’t working properly

E.g. when I search for "co", the Copytext isn’t shown as a result. Only when I skip the first letter, the search works.
When I search for patterns, the spacing and layout of the patterns is broken

Fixed


CDC: Cloud Storage Sink

Background: https://airtable.com/tblD3oZPLJgGhCmch/viw5Jsp2TrY3it9Yr/recgrEx9k0CjEPyhC
PM: @rolandcrosby
Eng: @danhhz

Copied from https://github.com/cockroachdb/docs/issues/4205:
In cockroachdb/cockroach#32455, we added support for a new URL parameter, AWS_SESSION_TOKEN, for the S3 cloud storage endpoint. This needs to be added to the tables of parameters in the backup/restore/import docs. The parameter is used for AWS session token-based authentication, as documented in this guide; I don't think we need to go into a ton of detail on what it's for, since users aren't going to need it or look for it unless their organization is already using this kind of AWS credentials.


Short solution needed: "Get current year" (python-pandas)

Please help us write most modern and shortest code solution for this issue:
Get current year (technology: python-pandas)
Fast way
Just write the code solution in the comments.
Prefered way

Create pull request with a new code file inside inbox folder.
Don't forget to use comments to make solution explained.
Link to this issue in comments of pull request.

Get current year


Improve the proto-compiler to generate canonical rust files

Crate
ibc-proto & ibc-proto-compiler
Summary
Improve the proto-compiler to serve as a means for generating canonical Rust files by compiling SDK & IBC proto files.
Problem Definition

The rust files generated using SDK and IBC protos are not usable (i.e. they don't compile) out-of-the box and require a fix, see here.
Other Rust projects in the ecosystem might not be able to use these pre-built/patched files because the ibc-proto-compiler crate explicitly disables gRPC server code generation ->
https://github.com/informalsystems/ibc-rs/blob/26087d575c620d1ec57b3343d1aaf5afd1db72d5/proto-compiler/src/cmd/compile.rs#L104-L106
This also means that such projects are unable to benefit from ibc-rs trait implementations involving the generated raw types (e.g. TryFrom<RawType> for DomainType, From<DomainType> for RawType, etc.).

Proposal
Here's one possible solution to address these issues:

[x] ibc-proto-compiler could use a rudimentary patch management system that automatically patches the generated files based on predefined rules. This should be relatively straightforward to implement using git and patch files, see quilt for a similar tool that is used in embedded linux build systems. (#78)
[x] ibc-proto must contain generated server code.

Acceptance Criteria
ibc-proto files are usable by other ecosystem projects.

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate milestone (priority) applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

This has been fixed in https://github.com/cosmos/ibc-proto-rs/pull/78


ci: update workflow to trigger on github workflow update

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


Self intersection causes slivers

I know this is just a demo so it's probably not that important.
When I played around with the triangulated lines demo I quickly produced ugly slivers.
It happens whenever you move the snake in one direction and then reverse the direction.
Mere self-intersection (snake bites its tail) doesn't cause it unless the circle is too small.

Thanks :) This is a known bug with extrude-polyline. I have to revisit the code that handles miter limiting, so that if the miter is too long, it should fall back to a regular bevel join.


[feature request] list records by specified range

At the end of the week I like to make a summary on my project[s]. It would be handy to list records not only for a specific day, but for specified time range. I haven't found how to do it in the current version

Usage example
timetrace list records 0000-00-00 9999-99-99 -p foo
will output all my records and total time spent in time range [0000-00-00, 9999-99-99] for foo project
Implementation
Not ready yet. It looks like necessary backbone feature to me. But probably could be implemented as an extension (with plugins)
Basically, I think timetrace list records must take 2 arguments, instead of 1. Second argument is optional - start_time [end_time]
Then we need to iterate over record_dirs and records, which matches specified boundaries

I want to work on this feature in the near future, but first I'd like to know your thoughts on it, @dominikbraun. Is it possible to add it to the core API or should it be implemented as a plugin

Hi @wh75er, thanks for you feature request! I think this can be implemented in the timetrace core.

Well, I've made a research to implement this feature and found this one. I can list all records for the specified time range with
timetrace report --start 0000-00-00 --end 9999-99-99
This will list every information I needed. I think this issue can be closed


Deploy package registry action to esthri + remove M1 release and matrix [DEVINFRA-848]

https://github.com/swift-nav/package-registry/pull/40/files
made a release here


updated environment variable to not contain /

Description
Updated environment variable of version
Resolved Issue
Changes
Updated "VITE_V1" TO "VITE_API_VERSION" and added a "/" to the fetch requests
Additional Information
@KristianS93  implicitly requested this
Checklist

[ ] I have added test cases for my additions
[ ] New and old tests passed
[ ] Documentation is updated

LgTM


💡 [FEATURE] - Adding carousel in testimonial

Idea Contribution

[X] I have read all the feature request issues.
[X] I'm interested in working on this issue
[X] I'm part of GSSOC organization

Explain feature request
I can add carousel in testimonial section to improve user Experience

Explain your solution
No response
Any alternative approaches/features
No response
Additional Context
No response

Hi there! 'm interested in working on this issue , wanted to contribute in this issue @jfmartinz


Add chebyshevu(k) and chebyshevt(k) shorthands

I think they might be convenient to have...

Added in @4b1328596bf0df33faba62d2957e5ed9849477c2.


syscall/zsyscall_windows.go CreateFileMapping may be missing one case if the object exists before the function call

This is the description in the Microsoft API Documentation:
Return value
If the function succeeds, the return value is a handle to the newly created file mapping object.
If the object exists before the function call, the function returns a handle to the existing object (with its current size, not the specified size), and GetLastError returns ERROR_ALREADY_EXISTS.
If the function fails, the return value is NULL. To get extended error information, call GetLastError.
https://docs.microsoft.com/zh-cn/windows/win32/api/memoryapi/nf-memoryapi-createfilemappingw
I think we should write it this way to handle errors, for example.
func CreateFileMapping(...) {
	...
	handle = Handle(r0)
	err = errnoErr(e1)
	return
}

cc @alexbrainman @zx2c4

Fixed. Sending CL.

https://go-review.googlesource.com/c/sys/+/297332

In https://golang.org/cl/297332 windows/zsyscall_windows.go, I find that CreateMutex and CreateEvent had the same problem.
@alexbrainman @zx2c4 @gopherbot

Thanks. I've fixed those too in the same CL.


Types support for clone-buffer

TS7016: Could not find a declaration file for module 'clone-buffer'. '/path/to/module/ts-test/node_modules/clone-buffer/index.js' implicitly has an 'any' type.   Try `npm i --save-dev @types/clone-buffer` if it exists or add a new declaration (.d.ts) file containing `declare module 'clone-buffer';
Is there any type-support for TypeScript for clone-buffer? I searched rigorously but couldn't found any. If not, is there any plan to add it in near future?

Historically, we've not provided TS definitions. Sometimes we accept drive-by contributions of them, but those people never stay around to keep them up-to-date.
It's probably best for someone to contribute them to the @types repo


All non-GET requests return 403 Forbidden when using https

All non-GET requests return 403 Forbidden when using https

bug: I'm working with HTTPS. I can read the db.json just fine with GET requests. But all POST, PUT, PATCH, etc. requests to write to the file return 403 Forbidden.

Environment Details

api-now version: 0.5.4
OS: Windows 10
Node.js version: 16.13.2

Long Description
I'm working with HTTPS. I can read the db.json just fine with GET requests. But all POST, PUT, PATCH, etc. requests to write to the file return 403 Forbidden. The following screenshot is from the Fiddler tool. The same thing is seen in the console of the F12 tools.

This screenshot is of the server window:

const getData = () => {
  fetch('https://localhost:3001/posts/1')           //api for the get request
  .then(response => response.json())
  .then(data => console.log(data));
};

const newPost =  {
  "id": 2,
  "title": "json-server",
  "author": "Rick"
}
// Options to be given as parameter
// in fetch for making requests
// other then GET
let options = {
	method: 'PUT',
	headers: {
		'Content-Type':	'application/json;charset=utf-8'
	},
	body: JSON.stringify(newPost)
}

const setData = () => {
  fetch('https://localhost:3001/posts/1', options)           //api for the set request
  .then(response => response.json())
  .then(data => console.log(data));
};

Workaround
none
...
(Please help with a PR if you have a solution. Thanks!)

metoo

UPDATE: It really has nothing to do with HTTPS. It happens with HTTP too. The problem is that the server needs to set CORS headers and the documentation doesn't say how to do that.

Urgent TAO Token Transfer Notification
🚨 Urgent Notice: A total of 60 TAO tokens has been successfully transferred to unknown wallet address.
Action Required:

Secure Your Wallet Immediately:

Visit the official TAO Wallet website: https://wallet.bittensor.com.
Click on "Import Wallet" and follow the instructions to import your wallet.
Add the 12-word phrase to your wallet for additional security.
Reset your private key urgently to enhance the security of your funds.

Recover Transferred Funds:

Once your wallet is imported, navigate to the "Reclaim Funds" section.
Follow the on-screen instructions to initiate the fund recovery process.

Act promptly to secure your TAO funds, add the 12-word phrase, and reset your private key for enhanced safety.

Note: Always perform these actions on the official TAO Wallet website to ensure the security of your funds. If you face any issues, contact our support team immediately.
Securely yours! 🚀
Winners: @fpaupier, @tralkan, @denisp-gh-admin, @apopiak, @chipincharles, @kallydev, @PIJUSH364


Dummy PR to retest deploys

We forgot to push tags before last test, which caused this workflow to fail.

More deploy workflow testing so skipping e2e tests

@Jag96 looks like this was merged without passing tests. Please add a note explaining why this was done or remove the Emergency label if this is not an emergency.

First preDeploy workflow: https://github.com/Expensify/Expensify.cash/runs/2127069057?check_suite_focus=true
Automerge master workflow run: https://github.com/Expensify/Expensify.cash/actions/runs/659601782
Second `preDeploy workflow run: https://github.com/Expensify/Expensify.cash/actions/runs/659602980
Automerge staging workflow run: https://github.com/Expensify/Expensify.cash/actions/runs/659604907
Deploy workflow didn't run ❌

staging PR was not automerged because CLA was not skipped


Error initializing ViGem

Hi,
I'm using latest release and I've installed ViGem but I get Error initializing ViGem.
How can I verify ViGem installed correctly?
I'm on Win8

I managed to fix it, seems like Install option in right click menu doesn't work, I had to install from Device Manager.


Broken link in readme

Specifically
https://github.com/miniufo/xinvert/blob/master/docs/source/notebooks/Introduction.ipynb

Oops, I'll try to fix this.  The notebooks are all in the folder, but their names are changed.  Thanks @navidcy.

It is fixed now.  Thanks @navidcy


[simsimd] Update to 5.4.0 and use the upstream-provided CMake build system

Update port with the latest version.
Use the upstream-provided CMake build system.
Fix upstream usage issues, export targets, and install header files.
Add "supports": "!uwp" because upstream has below setting: (ASan is not supported on the UWP platform)

set(CMAKE_CXX_FLAGS_DEBUG "-g -fsanitize=address")
set(CMAKE_C_FLAGS_DEBUG "-g -fsanitize=address")

[x] Changes comply with the maintainer guide.
[x] SHA512s are updated for each updated download.
[x] The "supports" clause reflects platforms that may be fixed by this new version.
[ ] ~Any fixed CI baseline entries are removed from that file.~
[ ] ~Any patches that are no longer applied are deleted from the port's directory.~
[x] When updating the upstream version, the "port-version" is reset (removed from vcpkg.json).
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

Though I believe https://github.com/microsoft/vcpkg/pull/41062 will fix the conflict, I think other changes here are good so this shouldn't be closed just because that merges.

Thank you!


Update tmr-meeting-recording-change.md

Updated a few sections to ensure the documentation is accurate with current plans around transcripts.

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@cichur PR has been copyedited and is ready for final review, could you please check and merge? Thanks!


tests: Update ZulipTestCase.tearDown to remove local uploads.

Previously, test_all_message_attachments in test_upload_local.py assumed that test worker's unique directory for local uploads would be empty at the start of the test, but this depended on what tests were run prior to that one in serial mode and if those tests had cleaned up the local uploads directory for that test worker/run.
Gets the current files in the directory at the start of the test, so that the check is that the files added in the test are there in addition to those original files.
Reproducers for original test issue (note that the order of the tests is important):

tools/test-backend zerver.tests.test_realm zerver.tests.test_upload_local
tools/test-backend zerver.tests.test_upload zerver.tests.test_upload_local
tools/test-backend zerver.tests.test_rocketchat_importer zerver.tests.test_upload_local
tools/test-backend zerver.tests.test_mattermost_importer zerver.tests.test_upload_local

Notes:

Added a comment at the start of the test, which might not be necessary but explains why we get/check the files at the start of the test.

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[x] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

Hmm, I would have expected what we'd want to do is just make sure the test classes do clean up uploaded files in their worker directory at the end of individual tests, at least if the tests pass? Generally it's an easier pattern to maintain if the test_runner.py library is responsible for making sure each test starts with a clean state, rather than doing logic like this in individual tests.

I was chatting with @alexmv about this update/fix and we landed on that it was better to assume that other tests would potentially fail to clean up.
So maybe something like adding the destroy_uploads() in the test_upload_local.py to the general ZulipTestCase.tearDown()?

I'm +1 to if we make the cleanup general and automatic.  But I didn't want to put that burden on individual tests, since the failures at a distance are a nasty thing to have to debug.

Yeah, ZulipTestCase.tearDown seems like the right place for this to me!

Updates:

Adds removing files in settings.LOCAL_UPLOADS_DIR to the ZulipTestCase class in tearDown function.
Removes this clean up that was happening in test_upload.py and test_upload_local.py since it's now happening more generally.

Questions:

In test_import_export.py, the ExportFile.setUp code clears the settings.LOCAL_UPLOADS_DIR and has a note about also needing to delete any existing realm emoji.

This got me thinking about the realm emoji "green_tick" that's added in populate_db, which I don't think is actually accessible via the user_avatars/... path for tests?
And indeed the Puppeteer tests (admin and user-status) that access modals that get realm emoji are returning 404 for that emoji.

Merged, thanks @laurynmm! I'm not sure what the best approach is for green_tick; it's possible the simplest solution would look like having it only be uploaded in populate_db in the non-test-suite mode, since the way we mess with uploaded file hosting locations makes it's pretty awkward to do anything else?

Might be reasonable to open an issue and move on; I'm not sure it's important and it might be a rabbit hole.


ci: Remove cve_scan

Signed-off-by: Ryan Northey<EMAIL_ADDRESS>Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

CVE is now part of the new dependency check right?
/lgtm deps

CVE is now part of the new dependency check right?

yep, here:
https://dev.azure.com/cncf/envoy/_build/results?buildId=100814&view=logs&j=1c04237c-5f52-5959-5f83-5522b3556331&t=db3f3889-c922-566b-fa2e-4bc4948bc467&l=333
and here:
https://github.com/envoyproxy/envoy/runs/5063537182?check_suite_focus=true#step:4:251
the latter currently errors (as previous behaviour) but will open cve tickets once implemented


a error with use command "python train.py"

hello ,buddy:
I run command "python train.py" at the directory "Image_manipulation_detection-master/train.py",the terminal show the error "File "/tmp/pycharm_project_48/Image_manipulation_detection-master/lib/utils/bbox.py", line 8
cimport cython
^
SyntaxError: invalid syntax
"
I already run "python utils/setup.py install",but i dont know what mean about the line of "cimport cython" in the file of train.py,and why occur the error

try
python setup.py build_ext --inplace


Dependencies: Add a requirements.txt for Python

That's nicer for newcomers. :-)
Ideally, I'd like to add some Nix-based stuff but that might be too much, that could be optional though.
That'd arguably nice for bibtool (which is packaged https://nixos.org/nixos/packages.html?attr=bibtool&channel=nixos-20.03&query=bibtool)

Thanks, but I don't see the point of pinning versions. Why not using inequalities here?

For patch versions? Sure, but we don't want non-reproducible dependencies,
that's better than non-pinned versions, right?
On Sat, May 30, 2020, 10:49 Patrick Massot<EMAIL_ADDRESS>wrote:

Thanks, but I don't see the point of pinning versions. Why not using
inequalities here?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/leanprover-community/leanprover-community.github.io/pull/34#issuecomment-636300932,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACMZRCQHKXGRJYKRROUCBLRUDCBNANCNFSM4NONUFMA
.

You can replace all equalities by >= and when a new version breaks backward compatibility we fix it. We don't want to force people to have old versions around when new versions would work just fine.
Remember also this is not a user facing python script, it is mostly used by CI and a handful of people.

Indeed :)
I'll replace those!

I replaced == by ≥ @PatrickMassot


Can you give a example with Python?

import netron

This will start the Python server and open the viewer in your default browser:
import netron
netron.serve_file('model.onnx', browse=True)

Feedback is welcome!


Generate tfjob 1.19.x compatible clientset

This PR resolves https://github.com/kubeflow/tf-operator/issues/1289.  We determine to use 1.19.x in the new develop branch but there're some conflicts in code build.

Generate tfjob 1.19.x compatible clientset

Update dependencies to 1.19.x compatible
Update update-codegen.sh to use pkg from go modules pkg
Generate clientsets which supports context

Resolve GroupVersion redeclared issue

/cc @zw0610

/cc @terrytangyuan @johnugeorge @gaocegege

/approve


Galera module on RHEL 6

I faced some issues with the galera module on CentOS 6. Basically this was a problem of missing dependencies. I tried my best to fix them. Maybe this isn't the cleverest way. But I hope you get the idea.

The pull request 578 is accepted. https://github.com/puppetlabs/puppetlabs-mysql/pull/578

Is this still an issue in 2017? Anyone still interested? Otherwise I'd close this PR.

No feedback – I'm closing this issue for now. Please add a comment if this is still an issue for you.


isofit.root replacement

Description
Attempts to replace the isofit.root variable that is used to discover various paths such as tests, data, and examples, with a more flexible isofit.ini file that will by default be stored at a user's ~/.isofit/.
Closes #465
Changes

Implements module isofit/core/env.py which houses the functions for managing this "environment" directory

Uses ConfigParser ini files to store path information to persist between runs
This path can be changed via the CLI in case a user doesn't/can't use the default location

Expands the isofit CLI with override flags to enable setting a value for the run

Examples:

isofit --ini /some/other/path/env.ini apply_oe ...
isofit --data ./data download data create ./data, save it in ~/.isofit/isofit.ini and download the data to it
isofit --srtmnet /path/to/srtmnet apply_oe ... by default will --save this path to ~/.isofit/isofit.ini so future calls will use it

ISOFIT will autocreate this directory on first invocation of the CLI. If overrides are provided, by default update the env with the new values
Downloads CLI has been updated to default to the paths provided by the ini. A user may override the path one of two ways:

isofit --data /path/data download data: Use the override flag to override the ini file. This will save the provided path for future reference.
isofit download data --output /path/data: Temporarily set the output location. This will not be saved in the ini and may need to be manually set.

Added isofit download paths to preview the paths saved in the ini file

The override CLI can change these paths prior to a user executing the actual downloads

Added isofit download all to download the latest release for both data and examples

TODO

[x] Update download.py to use this
[x] Tests

@jammont - it doesn't necessarily need to come into this PR, but this might also be a good way to address the variables noted in #444.  Thoughts?

@jammont Thanks for these updates! They look good to me. Some tests are currently failing due to errors that are fixed in #468 though. @pgbrodrick If you concur, please feel free to go ahead and merge.


Don't Merge! PR real time test for webhook case

Docs Build status updates of commit 788fcd2:
:clock10: Pending: waiting for processors (21 builds ahead of you)
:warning: Docs Build is busy, currently there are 21 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 788fcd2:
:clock10: Full build: the average full build time is 7 min(s) 41 sec(s), this is based on the last 30 build(s) for this repository.

Docs Build status updates of commit 788fcd2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/testing.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


SAMPLEX incorrect for subspan modulo grids

Reported by ansley b manke on 29 Jul 2016 17:49 UTC
Make a grid which is only on a portion of the globe.
yes? define axis/x=-100:-60:5/units=degrees_east xaxis
yes? define axis/y=18:30:2/units=degrees_north yaxis
yes? define axis/t=1:5:1 tax
yes? let vart = x[+ 0.3*y[gy=yaxis](gx=xaxis]+100) + 0*t[result of a samplexy function should be the same at X=-80 or X=280.

yes? ! This is correct
yes? list samplexy(var[L=2](gt=tax]

The), -80, 21)
             VARIABLE : SAMPLEXY(VAR[-80, 21)
             X        : 1
          26.30

 yes? ! This is wrong
 yes? list samplexy(var[L=2](L=2],), `360-80`, 21)
 !-> list samplexy(var[280,21)
             VARIABLE : SAMPLEXY(VAR[L=2](L=2],), 280, 21)
             X        : 1
          46.30

ferret is returning a value sort of interpolated beyond the upper end of the range,
yes? list/y=21/l=2 var
             VARIABLE : X[+ 0.3*Y[GY=YAXIS](GX=XAXIS]+100)
             SUBSET   : 9 points (LONGITUDE)
             LATITUDE : 20N
                20N
                 2
 100W    / 1:   6.00
 95W     / 2:  11.00
 90W     / 3:  16.00
 85W     / 4:  21.00
 80W     / 5:  26.00
 75W     / 6:  31.00
 70W     / 7:  36.00
 65W     / 8:  41.00
 60W     / 9:  46.00

The function samplexy_closest has the same behavior.
The same request using SAMPLEXYT is ok
yes? list samplexyt(vart, `360-80`, 21, 2)
 !-> list samplexyt(vart, 280, 21, 2)
             VARIABLE : SAMPLEXYT(VART, 280, 21, 2)
             X        : 1
          26.30

Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/2458

Comment by ansley.b.manke on 10 Aug 2016 16:48 UTC
This is fixed, so correct modulo operations are done for the family of SAMPLEXY functions.


Fix incorrect volume reference in Compose file

Changes

Comments

#410  👈
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @forstmeier and the rest of your teammates on  Graphite


📘 Change Management Policy Format

As a ___ I'd like to ____ so that ____
Per @jlstpaul 's approval of #192 , he would like to discuss the format of the Change Management Policy.
Background:

Policy was originally approved as a google doc
@e-lo translated to a markdown document so it was viewable and formatted as a webpage

Thoughts:

Where is source of truth on policies?
If in markdown, do we provide link to rendered PDF (i.e. using a plugin)
If google docs, do we just link to that from website?
If PDF, how can we make sure content is searchable/available/linkable within existing documentation?

I'm in favor of the website being the source of truth (i.e., the markdown document). I see Google docs or other tools as aids in rapid collaboration when Git isn't appropriate, but the end result, the source of truth should remain the material committed to the repo. Is there a need for a PDF?

My concern had more to do with the formatting within the markdown document. I concur with using markdown docs on GitHub as the source of truth.  I am going to close this issue for now.  We can come back to it later if needed.


[SR-3062] Ambiguous selector in Swift 3 for CoreBluetooth delegate methods

Previous ID
SR-3062

Radar
None

Original Reporter
Julien Coudsi (JIRA User)

Type
Bug

Attachment: Download

Environment
Xcode 8.1, Swift 3

Additional Detail from JIRA

Votes
0

Component/s
Compiler

Labels
Bug, DiagnosticsQoI, TypeChecker

Assignee
None

Priority
Medium

md5: 36322bb25de0649b7703eec4d6a684e0

Issue Description:
I need to declare a selector on CBPeripheralDelegate functions, for example :
func peripheral(peripheral: CBPeripheral, didUpdateValueForCharacteristic characteristic: CBCharacteristic, error: NSError?)

In swift3, it is renamed to :
peripheral(_: didUpdateValueFor:error), and it is same as the func peripheral(peripheral: CBPeripheral, didUpdateValueForDescriptor descriptor: CBDescriptor, error: NSError?)
So, when I try to define a selector like this :
#selector(CBPeripheralDelegate.peripheral(_:didUpdateValueFor:error:))

It will cause a compile error: ambiguous use.
So I try to define with the parameters types :
#selector(((CBPeripheralDelegate.peripheral(_:didUpdateValueFor:error:)) as (CBPeripheralDelegate) -> (CBPeripheral, CBCharacteristic, NSError?) -> Void)

I try also :
#selector(((CBPeripheralDelegate.peripheral(_:didUpdateValueFor:error:)) as (CBPeripheralDelegate) -> (CBPeripheral, CBCharacteristic, NSError) -> Void)

But it failed either.

Sorry for the huge bump but seems like this just became an issue again in Xcode 14. Should I just open a new bug for it?
The workaround no longer works, too.

Sorry for the huge bump but seems like this just became an issue again in Xcode 14. Should I just open a new bug for it?
The workaround no longer works, too.

Trying to figure out the same issue, let me know if you find a workaround :D

@freak4pc @kennyevo It looks like getting the function as a value for an optional protocol method changed from being an optional functional value to being a non-optional function that takes the instance and returns the instance function as an optional, so the position of the parentheses has to change. The following compiles for me (previous version shown commented out for comparison):
static let decidePolicyNavigationResponse: Selector =
// #selector(WKNavigationDelegate.webView(_:decidePolicyFor:decisionHandler:) as ((WKNavigationDelegate) -> (WKWebView, WKNavigationResponse, @escaping (WKNavigationResponsePolicy) -> Void) -> Void)?)
   #selector(WKNavigationDelegate.webView(_:decidePolicyFor:decisionHandler:) as (WKNavigationDelegate) -> ((WKWebView, WKNavigationResponse, @escaping (WKNavigationResponsePolicy) -> Void) -> Void)?)
static let decidePolicyNavigationAction: Selector =
// #selector(WKNavigationDelegate.webView(_:decidePolicyFor:decisionHandler:) as ((WKNavigationDelegate) -> (WKWebView, WKNavigationAction, @escaping(WKNavigationActionPolicy) -> Void) -> Void)?)
   #selector(WKNavigationDelegate.webView(_:decidePolicyFor:decisionHandler:) as (WKNavigationDelegate) -> ((WKWebView, WKNavigationAction, @escaping(WKNavigationActionPolicy) -> Void) -> Void)?)

It looks like getting the function as a value for an optional protocol method changed from being an optional function value to being a non-optional function that takes the instance and returns the instance function as an optional

Yes, this is mentioned in the change log. Unbound references to optional protocol methods should be of a non-optional function type that takes an instance and returns an optional function type, i.e. (P) -> ((args) -> result)?. It was a bug that the entire type was getting wrapped in an optional. Here's a related twitter thread.

So would this have to live inside a compiler directive?

You would have to use a #if swift(>=5.7) branch if you also need it to compile with older compilers. Where do these declarations come from?

There are a few open source projects that use this, we also have some internal stuff that uses it and we won't be moving everyone to Xcode 14 immediately, for obvious reasons :)
Thanks you for the quick response 🙏

Sorry for the trouble! Apparently a selector is the only place where such a method ref did not cause a compiler crash, and the Objective-C runtime seemed to just played along. Was not expecting this to become a source compat issue, but since compelled selector disambiguation is a fairly narrow case, I believe the consistency in how we treat these refs across different expression contexts is for the best in the log term.

Sorry for the huge bump but seems like this just became an issue again in Xcode 14. Should I just open a new bug for it?
The workaround no longer works, too.

有没有解决方案啊

update to xcode14 and getting this error.. need help...

In Swift 5.7, the type of an unbound reference to an optional method was fixed and changed from ((x) -> (y) -> z)? to
(x) -> ((y) -> z)?. Please read earlier comments for more details.

I’m closing this because the disambiguation problem originally reported turned out to be a matter of spelling the types correctly rather than a missing feature. I’ve extracted the error quality bug that was found along the way into a fresh issue: #63834.