Combining X Below

Non-IPA symbol Combining X Below (U+0353) is used in some consonants and vowels. It seems as though it stands for frication, but this is neither sanctioned by the IPA nor standard or common. I suggest it be replaced with whatever appropriate according to the description of the sources.

You are correct, it is not part of the official IPA.  In fact there are several symbols used in the PHOIBLE dataset that are not part of the official IPA. Most of them are documented here, though we just pushed out a major release and the conventions webpage has not been updated since then (but will be soon).
With regard to your suggestion that we replace U+0353 with "whatever is appropriate according to the description of the sources" --- well, the reason we use that diacritic is because we believe the official set of IPA symbols and diacritics is not sufficient to adequately capture the variety that is present across the roughly 3000 inventories in PHOIBLE.  If there are specific language descriptions where you think our use of U+0353 is unwarranted given the description of the sounds in the cited reference, we welcome you to open issues or pull requests on the development repository to call our attention to it.

Drammock, thank you for your reply and the link to the documentation. I would argue that it could be replaced by symbols officially sanctioned by the IPA in many cases, but that might entail some amount of subjective interpretation of the literature, which I understand is best avoided.
So long as the value of each symbol is defined, I see no problem using non-IPA symbols. But I don't see a link to or a copy of the documentation on the online version (phoible.org). I think there definitely should be one, is there reason why it's not there?

Your initial message made me also realize that the documentation is not prominent from the main website. @xrotwang is there any difficulty in adding a couple static HTML pages to the phoible.org domain?
On April 6, 2019 8:11:31 PM AKDT, Nardog<EMAIL_ADDRESS>wrote:

Drammock, thank you for your reply and the link to the documentation. I
would argue that it could be replaced by symbols officially sanctioned
by the IPA in many cases, but that might entail some amount of
subjective interpretation of the literature, which I understand is best
avoided.
So long as the value of each symbol is defined, I see no problem using
non-IPA symbols. But I don't see a link to or a copy of the
documentation on the online version (phoible.org). I think there
definitely should be one, is there reason why it's not there?

Nope,  that's simple enough. Let me know which ones you want and linked
from where.
Daniel McCloy<EMAIL_ADDRESS>schrieb am So., 7. Apr. 2019,
09:55:

Your initial message made me also realize that the documentation is not
prominent from the main website. @xrotwang is there any difficulty in
adding a couple static HTML pages to the phoible.org domain?
On April 6, 2019 8:11:31 PM AKDT, Nardog<EMAIL_ADDRESS>wrote:

Drammock, thank you for your reply and the link to the documentation. I
would argue that it could be replaced by symbols officially sanctioned
by the IPA in many cases, but that might entail some amount of
subjective interpretation of the literature, which I understand is best
avoided.
So long as the value of each symbol is defined, I see no problem using
non-IPA symbols. But I don't see a link to or a copy of the
documentation on the online version (phoible.org). I think there
definitely should be one, is there reason why it's not there?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/clld/phoible/issues/18#issuecomment-480567911, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA1HKD9qV3ygqLQKdJbj8JeY49n1HfE4ks5veaRZgaJpZM4cgS_T
.

Great. Once @bambooforest and I have updated the docs I'll ping you about where to put them.
On April 7, 2019 12:01:44 AM AKDT, Robert Forkel<EMAIL_ADDRESS>wrote:

Nope,  that's simple enough. Let me know which ones you want and
linked>
from where.>

Daniel McCloy<EMAIL_ADDRESS>schrieb am So., 7. Apr. 2019,>
09:55:>

Your initial message made me also realize that the documentation is
not>
prominent from the main website. @xrotwang is there any difficulty
in>
adding a couple static HTML pages to the phoible.org domain?>

On April 6, 2019 8:11:31 PM AKDT, Nardog<EMAIL_ADDRESS>wrote:>

Drammock, thank you for your reply and the link to the
documentation. I>
would argue that it could be replaced by symbols officially
sanctioned>
by the IPA in many cases, but that might entail some amount of>
subjective interpretation of the literature, which I understand is
best>
avoided.>

So long as the value of each symbol is defined, I see no problem
using>
non-IPA symbols. But I don't see a link to or a copy of the>
documentation on the online version (phoible.org). I think there>
definitely should be one, is there reason why it's not there?>

—>
You are receiving this because you were mentioned.>
Reply to this email directly, view it on GitHub>
https://github.com/clld/phoible/issues/18#issuecomment-480567911,
or mute>
the thread>

https://github.com/notifications/unsubscribe-auth/AA1HKD9qV3ygqLQKdJbj8JeY49n1HfE4ks5veaRZgaJpZM4cgS_T>

.>

-- >
You are receiving this because you commented.>
Reply to this email directly or view it on GitHub:>
https://github.com/clld/phoible/issues/18#issuecomment-480568373


Improvement: Add ability to ingest Office documents

As a user, I would like to be able to select / upload a document, have the text content of the document extracted, chunked (if necessary), and then summarized appropriately.
Documents
https://blog.streamlit.io/langchain-tutorial-3-build-a-text-summarization-app/
https://github.com/GoogleCloudPlatform/generative-ai/blob/main/language/use-cases/document-summarization/summarization_large_documents_langchain.ipynb

https://pypi.org/project/sumy/

Closing due to usage of marker.


vcpkg build failure

Bootstrap build fails on Win10 /w vs2015
Environment:

OS: Windows 10
Compiler: vs2015 14.0.25431.01 Update 3

Steps to reproduce the behavior:

git clone vkpkg
bootstrap-vcpkg.bat

I'm expecting it to build using vs2015. But I get this:
..\src\vcpkg\install.cpp(845): error C2280: 'vcpkg::PortFileProvider::BaselineProvider::BaselineProvider(const vcpkg::PortFileProvider::BaselineProvider &)': attempting to reference a deleted function [E:\vcpkg\toolsrc\windows-bootstrap\vcpkg.vcxproj]
E:\vcpkg\toolsrc\include\vcpkg/portfileprovider.h(84): note: compiler has generated 'vcpkg::PortFileProvider::BaselineProvider::BaselineProvider' here
Looking at the error I can't even figure out why it's trying to call the default constructor there... both calls in the lambda to construct the BaselineProvider are using non-default parameters. I did spend a little time just trying to fix the compile error but I couldn't figure it out. Seems like the compiler is just wrong here...

@strega-nil, could you please have a look? this issue reproed with vs 2015 update3.

Hi, I got the same issue after pulling the repo. Previously I was at 539a182d3, and everything was fine, I pulled 0a457099416a843f442b6c2275b2ec57239b50d9 and I have this issue.
On Windows 10, VS2015
`Building vcpkg.exe ...
install.cpp
..\src\vcpkg\install.cpp(845): error C2280: 'vcpkg::PortFileProvider::BaselineProvider::BaselineProvider(const vcpkg::PortFileProvider::BaselineProvider &)': attempting to reference a deleted function [C:\tools\vcpkg\toolsrc\windows-bootstrap\vcpkg.vcxproj]
C:\tools\vcpkg\toolsrc\include\vcpkg/portfileprovider.h(84): note: compiler has generated 'vcpkg::PortFileProvider::BaselineProvider::BaselineProvider' here
C:\tools\vcpkg\scripts\bootstrap.ps1 : Building vcpkg.exe failed. Please ensure you have installed Visual Studio with the Desktop C++ workload and the Windows SDK for Desktop C++.
Au caractère Ligne:1 : 4

& {& 'C:\tools\vcpkg\scripts\bootstrap.ps1' }

+ CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,bootstrap.ps1

ScriptHalted
Au caractère C:\tools\vcpkg\scripts\bootstrap.ps1:411 : 5

throw

~~~~~

CategoryInfo          : OperationStopped: (:) [], RuntimeException
FullyQualifiedErrorId : ScriptHalted
`

So I investigated blindly on the commits, it's 4fba4b791 who broke the compilation, I tried git revert 4fba4b791 and fixed the problem (temporarily).

cc @BillyONeal please god we need VS2015 compile testing.

I'll fix this by Soon (tm), definitely by EOD

Thanks everyone. Fastest turn around ever. Really appreciate it.


report: Continuous Integration (part of Verification) [7h]

Prerequisite for issue #116.

Completed as of rev 5b17d43f45a77f8831eb71b0c2c45ac5ec42783c.


Compile Source code with Embed python?

hi I wonder if there is any way to change the UnrealEnginePython.Build.cs file to make it enable to compile access the embed python file since embedpython doesn't have a lib file, what should I change to do the compile ?

I've built mine with Python 3.6.5. Once you are done compiling, you can download the Python 3.6.5 embed package and copy it's content into your binary folder. I've been able to move this plugin into another machine, and it has been working fine....so far.

oh

I've built mine with Python 3.6.5. Once you are done compiling, you can download the Python 3.6.5 embed package and copy it's content into your binary folder. I've been able to move this plugin into another machine, and it has been working fine....so far.
oh thx, thought it needs to compile with the embeded version :D


Add option for visible pomodora, for entire channel

As far as I can see, creating a new timer via /startwork creates one timer which is only visible and accessible to the user who input the command.
I've noticed that in teams I work in, we use one timer for the entire group - that way our breaks are synced up, and everyone is quiet at the same times as well.
It'd be great to have the option of creating a public timer which is visible to the channel. Basically mirroring all the functionality you have for individuals, but making it public and only allowing one instance of the public timer (exactly how it is for private).

I've been thinking about this, as it's not the first time it's been requested.
It's a lot of work, as currently, everything is tied to a user, rather than a team or a channel.
One thing that would be fairly simple to implement would be a public keyword, just like /review has at the moment, for any command, so you can share all of the commands, not just the review.
I propose that I implement this quite soon, and we wait and see how popular it is. If it gets some use, I'd be happy to look into the bigger part of this idea.
What do you think?

I love the public keyword idea - that's more along the lines of how I was thinking. It could be pretty cheap to implement.
Thanks for being receptive to the idea!

The public keyword feature is deployed now.


Image Azure training - object reference not set to an instance of an object

Choose Image Classification and Azure training
Select Subscription that does not have any ML workspaces
Try to refresh the Compute
Get error

The refresh button should be disabled if no workspace is selected

This issue can't be repro on：

Windows 10 Enterprise, Version 20H2
ML.Net Model Builder (Preview): <IP_ADDRESS>2301
Microsoft Visual Studio Enterprise 2019: 16.9.4
.Net: 5.0.202

Main branch:
https://privategallery.blob.core.windows.net/gallery/refs/heads/main/atom.xml
Steps：

Create new C# console app with .Net 5.0;
Add model builder by right click on the project;
Select "Object detection";
Navigate to "Environment" page, click "Set up workspace";
Select one subscription without ML workspaces;
Refresh the compute or click refresh button after "Subscription" or "Machine Learning Workspace name" or "Compute name";
No error prompts.


feat!: (HOLD FOR GO 1.22 RELEASE) introduce logger choice via slog

Historically brokerapi has required use of the
lager logger. In Go 1.21, structured logging was introduced into the Go standard library via the log/slog package, and slog compatability was added to lager.
brokerapi has been modified to require a slog logger to be passed rather than a lager logger. This allows users a choice of logger. Users who still want to use lager can easily do that using the lager/slog compatability:
logger := lager.NewLogger(name)
brokerAPI := brokerapi.New(serviceBroker, slog.New(lager.NewHandler(logger)), credentials)

And users who want to use slog or an slog-compatible logger can do that instead.
A key advantage is that lager is no longer a dependency of this package, which simplifies package management for apps that use brokerapi and other libraries which use lager.

Wouldn’t it be better to use an interface that matches the slog/Logger, instead of the concrete type?
Good point. That's a good pattern in general for Go. I think I was influenced by an example (that I can no longer find) that I interpreted as it being "normal" to pass a logger concrete type. But the more I think about it, the more it makes sense to take an interface that's defined in brokerapi. (One of the big issues with lager.Loger is that despite being an interface, it's defined in the lager package, so you end up being tightly coupled to lager even if you write another logger that implements the interface.)

I'll have a go at re-working this to make that change.

There is a snag in using the interface approach. We use the With() method which returns a *slog.Logger, so if you define the interface to be:
type Logger interface {
	With(args ...any) Logger
}

Then *slog.Logger does implement this interface because With() has the wrong return type. And the alternative:
type Logger interface {
	With(args ...any) *slog.Logger
}

Is an improvement on a concrete type, but still ties us to the concrete type. But I had been thinking about usages of With() because in this PR they are quite boilerplate-heavy. If we could refactor them away, then we might get something much nicer.

I'm struggeling at the same spot for the last 30 minutes 😂
Sadly it's go, not swift (where we could just have had an interface extension as a default implementation...)
Looking at the implementation of With, we could also have another method within tooling, doing the same.
In the end it would be something like
func With(args ...any) *Logger {
	if len(args) == 0 {
		return l
	}
	return slog.New(l.handler.WithAttrs(argsToAttrSlice(args)))
}

Ok, didn't say a word slog.New isn't any better.
Maybe try to avoid With and pass the args?

I tried to turn https://github.com/pivotal-cf/brokerapi/blob/main/utils/context.go#L46 around, into a context-aware handler, so that we could have all values within the context. But in the end we would need to set the handler, which is also not going to work without slog...

In the end people have a dependency to the standard library (anyways) and could provide a custom ‚slog.Handler‘. So let’s keep the ‚slog‘ for simplicity?

Thanks for trying @elgohr. I also considered not using the With() method which means that you can write an interface that doesn't mention *slog.Logger. But I agree that just taking a concrete *slog.Logger is simpler for now, and if we discover a better fix later, it would not be a breaking change.


Bug 1146 test invalid val bit patterns

This provides some tests for bad bit patterns in Val, as suggested in #1146; along the way it does a few other things:

Pushes Val integrity checks earlier, to wasmi dispatch "unmarshalling" phase
Makes VmCallerEnv do the same (or very similar) checks so we get (near) fidelity when calling natively
Updates the way we build test-wasms to be more like soroban-cli (making them much smaller)
Defines a couple undefined parts of Vals, especially SymbolSmall which had 2 stray bits
Deletes some seemingly-dead test wasms that @sisuresh included in #1133 (can you confirm these were a mistake?)

Fixes #1146

Deletes some seemingly-dead test wasms that @sisuresh included in https://github.com/stellar/rs-soroban-env/pull/1133 (can you confirm these were a mistake?)

@graydon I think you meant to tag @dmkozh?

Deletes some seemingly-dead test wasms that @sisuresh included in #1133 (can you confirm these were a mistake?)

@graydon I think you meant to tag @dmkozh?

... yeah, weird, I could have sworn I saw your name on the commit! hah, well, sorry!


remove libsystemd dependency

(I messed stuff up with git branches so decided to create a new PR instead of the old one)
Hello. This PR introduces home-baked sd_booted and sd_notify functions, so it's now possible to completely remove the libsystemd dependency as per Lennart Poettering's advice

I'd recommend apps to just embed their own minimal version of the sd_notify() protocol, in their native language. It's trivial, and nowadays even in crazy languages like Java you have AF_UNIX support that is sufficient to implement it in a few lines of code.

I copied sd_booted almost as-is from libsystemd. As for sd_notify, I've been looking at python implementation and its documented behavior.
This code is entirely untested, other than "it compiles", so please test it before merging (if you'd like to merge this PR, that is)

https://github.com/hyprwm/Hyprland/pull/5582#discussion_r1564664542 - also adressed this review

but yeah needs testing + nix fails @fufexan


add 11D release and updated win11 24H2 product release

Summary
Add release notes for 11D (scheduled non-sec release for 11/21 am), update operating system support to include Windows 11, version 24H2 and Server 2025.
Fixes #Issue_Number (if available)

Internal previews

📄 File
🔗 Preview link

docs/framework/get-started/system-requirements.md
docs/framework/get-started/system-requirements

docs/framework/install/on-server-2025.md
docs/framework/install/on-server-2025

docs/framework/install/on-windows-11.md
docs/framework/install/on-windows-11

docs/framework/release-notes/2024/11-21-november-preview-cumulative-update.md
docs/framework/release-notes/2024/11-21-november-preview-cumulative-update

PLAN TO MERGE THIS PR ON 11/20.

[docs/framework/get-started/system-requirements.md] : Can this be Windows Server 2025 and Newer as we are already saying Windows Server comes with 4.8 and 4.8.1 is installable. Having Windows Server 2022 will cause the confusion for 4.8.1 as preinstalled.


Simplify CD pipeline, get rid of EndBug/add-and-commit action

Similar changes were done in apilytics/apilytics-node@6e1b953.

Codecov Report

Merging #12 (99a9daa) into master (c63dab5) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master       #12   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            4         4
  Lines           82        82
  Branches         7         7
=========================================
  Hits            82        82

Impacted Files
Coverage Δ

apilytics/core.py
100.00% <ø> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c63dab5...99a9daa. Read the comment docs.


Updating Anaconda product name from Commercial to Professional edition

[x] The commits are squashed in a cohesive manner and have meaningful messages.
[ ] For commits that came from upstream, [UPSTREAM] has been prepended to the commit message
[x] JIRA link(s): https://issues.redhat.com/browse/RHODS-3582
[x] The Jira story is acked
[x] An entry has been added to the latest build document in Build Announcements Folder.
[ ] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious)
[x] The developer has manually tested the changes and verified that the changes work.

Just noticed that PR 208 (not merged yet) updates one of the three files I update here. Might need to either close 208 or remove one of the file changes here and merge both.

Commits are squashed!

I did the live build and it looks good to me. I am just waiting for @bdattoma to take a look at it and confirm it as well.

yes, we're going to use the live build to check the changes we need to do in our automated tests. Thank you! :)

lgtm


ACSPublicCoverage Income Threshold

Hi, thank you for creating these datasets! I am currently looking into ACSPublicCoverage, and I have a few questions about the criteria used in its creation:

Why was $30k chosen as the cutoff for ACSPublicCoverage? 'Low-income' status varies depending on state, number of household members, etc. Applying a $30k threshold to every state when each state has a different cost of living doesn't make sense to me, and I was unable to find a justification for this cutoff in the paper.

ACSPublicCoverage focuses on individuals, but low-income status also depends on household size, which isn't one of the 19 features. On the other hand, the dataset includes "ESP," or "employment status of parents," but the individual isn't always living with parents, so I am concerned that the inclusion of ESP but lack of household size can affect model training/predictions.

I would love to hear your thoughts on this matter - thank you again!
Tagging people who are also interested in this: @romanlutz, @imatiach-msft, @kspieks

Hi, thanks for the questions!
You're absolutely right that designation as "low income" usually depends on household size, and also that for certain programs, it may also depend on the state or local cost of living estimates. Unfortunately the individual level records that we access with ACSPublicCoverage don't have a feature for household size, so that is the reason we didn't include this feature. I believe it's possible to link individual-level records with household-level records (see page 13 here) so that we can add a household size feature to each individual, but we kept the scope of the first iteration of folktables limited to the individual person records from the Census.
We also set a single income threshold rather than state-specific thresholds to keep the example prediction problem relatively simple. Our main goal with the five prediction problems included in folktables was to illustrate the range of target variables made available in Census data and provide examples for how to define new problems of interest. There are many subtleties to the factors that contribute to whether individuals are more or less likely to have public health insurance, as you point out, and ACSPublicCoverage is definitely not designed to produce predictive models that allow for interpretation of those factors. That being said, if it would help to have state-specific filtering criteria added to the definition of ACSPublicCoverage, I'd be happy to add that in and discuss with you what criteria would be most appropriate!
As for the $30,000 income threshold, we arrived at that number by starting with the average US household size (2.53 people), rounding that up to 3, finding that the Federal Poverty Line in 2021 for 3 person households was $21,960, and then multiplying that number by 1.33 since the Affordable Care Act allowed states to extend Medicaid eligibility to adults with income up to 133% of the Federal Poverty Line. That results in a total of $29,206.8, which we rounded up to $30,000. As I mentioned above though, since this was a very rough approximation, we're very open to modifying the prediction problem, or creating a more detailed, state-specific one, if you have that need.
For your second question, we didn't have a particular reason for including "employment status of parents", other than that it could possibly be predictive for individuals who are still living with their parents. In general, we thought it was interesting from a machine learning perspective to include both features that we intuitively thought would be predictive, and features that we didn't always expect to be predictive, since that is the case for many machine learning applications that indiscriminately use all the data available to them. It seems plausible that the inclusion of the ESP variable could make some models less accurate or make the model internals less interpretable -- it seems interesting to study which models are more vulnerable in this way, or also how the ESP variable could be flagged, as part of data cleaning.
Hope that was helpful -- thanks again for the thoughtful questions!


OSError: [Errno 28] No space left on device

Description
What steps will reproduce the problem?

What is the expected output? What do you see instead?
Please provide any additional information below
File "/anaconda3/lib/python3.6/site-packages/spyder/plugins/ipythonconsole.py", line 944, in set_working_directory
refresh_console=False)
File "/anaconda3/lib/python3.6/site-packages/spyder/plugins/workingdirectory.py", line 296, in chdir
self.refresh_plugin()
File "/anaconda3/lib/python3.6/site-packages/spyder/plugins/workingdirectory.py", line 204, in refresh_plugin
self.save_wdhistory()
File "/anaconda3/lib/python3.6/site-packages/spyder/plugins/workingdirectory.py", line 234, in save_wdhistory
encoding.writelines(text, self.LOG_PATH)
File "/anaconda3/lib/python3.6/site-packages/spyder/utils/encoding.py", line 236, in writelines
return write(os.linesep.join(lines), filename, encoding, mode)
File "/anaconda3/lib/python3.6/site-packages/spyder/utils/encoding.py", line 228, in write
textfile.write(text)
OSError: [Errno 28] No space left on device
Version and main components

Spyder Version: 3.2.6
Python Version: 3.6.3
Qt Versions: 5.6.2, PyQt5 5.6 on Darwin

Dependencies
pyflakes >=0.6.0 :  1.6.0 (OK)
pycodestyle >=2.3:  2.3.1 (OK)
pygments >=2.0   :  2.2.0 (OK)
pandas >=0.13.1  :  0.22.0 (OK)
numpy >=1.7      :  1.12.1 (OK)
sphinx >=0.6.6   :  1.6.6 (OK)
rope >=0.9.4     :  0.10.7 (OK)
jedi >=0.9.0     :  0.11.1 (OK)
psutil >=0.3     :  5.4.3 (OK)
nbconvert >=4.0  :  5.3.1 (OK)
sympy >=0.7.3    :  1.1.1 (OK)
cython >=0.21    :  0.27.3 (OK)
qtconsole >=4.2.0:  4.3.1 (OK)
IPython >=4.0    :  6.2.1 (OK)
pylint >=0.25    :  1.8.2 (OK)

We'll catch the error and show a warning in our next release, but you need to delete some stuff for Spyder to be able to save your files.

@ccordoba12  To note, this is also a duplicate of #6495 which you previously decided to close due it being user error and not a Spyder one.

Let's address this in 3.3. I think it's valid in Linux clusters, where people has a very limited quota, most of it probably filled with Anaconda itself.

Gotcha, thanks.

I am experiencing the exact problem trying to install Spyder on a RHEL 7.4 machine. There is plenty of disk space in all mounted filesystems and there are no quotas in place. The splash screen appears, then it crashes:
[REDACTED]@[REDACTED]:~ $ spyder3
[35407:35407:0603/163727.596738:FATAL:credentials.cc(137)] Check failed: error == EPERM || error == EUSERS || error == EINVAL || error == ENOSYS.

This seems very unlikely to be the "exact problem", since the error message is different, the circumstances are different, the traceback is different, the error location is very different, the error appears to be in Qt C code rather than Spyder's pure Python codebase, etc. In any case, as you can see the fix for this problem was already committed to our codebase, so if it is indeed the "exact problem" you can just run Spyder from the latest github source and the problem will be resolved.
Most likely, however, this is a non-Spyder-related  install issue specific to your machine, quite possibly the result of using an install method other than that we recommend—we aren't generally able to provide individual support for install issues for non-Anaconda installs, due to the number of tricky issues that can result. Considering you are using RHEL, it is also quite likely the version it installed is very out of date, without the benefit of months or quite possibly years worth of fixes and improvements. Therefore, you should install the current release via the latest version of Anaconda or Miniconda instead (conda install spyder), running under Python 3.6/x64/Qt5 if at all possible (although we still support legacy Python 2.7 and 3.5 for now, there's no reason to use them unless you need a specific package that doesn't run under Python 3.6).
You can also try the other steps listed in the Spyder Troubleshooting Guide, specifically the Basic First Aid and Emergency CPR sections, which resolve the great majority of Spyder installation issues, to see if you can fix your problem on your own. Thanks, and best of luck!

Thanks for the quick feedback. Right after I wrote "exact same problem" I realised the issue end edited the post.
The install method is "pip3.6 install spyder". The system is up to date.
It's unfortunate in my opinion that conda is now favoured over pip, but whatever, will give it a try.
Enjoy the weather!

Thanks for the quick feedback. Right after I wrote "exact same problem" I realised the issue end edited the post.

Ah, sorry—it must not have updated for me before I submitted my post.

The install method is "pip3.6 install spyder". The system is up to date.

Okay, that should indeed get you the latest version—many users install the versions available through their downstream package managers, which often lag far behind the current Spyder release, sometimes by years or more. Are you using a virtualenv/venv to install it in an isolated environment, to avoid conflicts with your system python and other packages? That can help avoid many issues, if you want to stick with pip and try to work through these problems with our troubleshooting guide and your own experience.

It's unfortunate in my opinion that conda is now favoured over pip

We do our best to support both, and we provide official wheels, fix any bugs we can from our side in them, and run our CIs using both pip and conda; also, several of the developers install and run Spyder and their other packages via pip. However, since we're a small team of unfunded volunteers stretched between maintaining Spyder 3, developing Spyder 4, developing and maintaining over a half-dozen plugins, other related projects, and responding to sometimes dozens of user issue reports per day just on Github, plus our Google Group/mailing list, Stack Overflow, Gitter public chat, social media and more, we have to prioritize our limited resources, and since most conda tends to be a much more reliable install method overall and avoids the many user/environment/machine specific issues with pip and compiled packages that we can't really control from the Spyder side of things, we only recommend it for users able to resolve such issues, as most likely there isn't anything we can really do about them anyway. Thanks for being willing to try conda, and best of luck!

Enjoy the weather!

Thanks...being an atmospheric scientist, I do love watching storms which we get here quite regularly in the summer now.

Perfect, thanks. Understood the reasons for conda. I'll try a few more things to see if it works with pip, and if not, will switch over (perhaps also drop various other Pythons installed... though they aren't supposed to be conflicting).

being an atmospheric scientist, I do love watching storms

I guessed that. Have fun :)
Thanks again!

Ok, I've removed completely pythons 3.4 and 3.6 that were in the system (from RHEL and EPEL repositories) and installed Anaconda. Still it crashes. Interestingly, in two other machines, both with same software, and one of them with same hardware, Spyder works just fine.
The only "special" thing about storage in this machine is that it has the logical volumes attached directly to it. This includes the /home directory, which is mounted as a local filesystem. The other two see the same filesystem via NFS (i.e., served from this one that is giving the error).
Should I open a separate thread, or this should be unrelated to Spyder? Thanks.
[REDACTED]@[REDACTED]:~ $ /opt/anaconda3/5.2.0/bin/spyder
[59046:59046:0603/194125.689576:FATAL:credentials.cc(137)] Check failed: error == EPERM || error == EUSERS || error == EINVAL || error == ENOSYS. : No space left on device
#0 0x7fcec909718e <unknown>
#1 0x7fcec90a9832 <unknown>
#2 0x7fcec90aabac <unknown>
#3 0x7fcec9a6f21b <unknown>
#4 0x7fcec9a6f5bc <unknown>
#5 0x7fcec8e13897 <unknown>
#6 0x7fcec8bbd6ce <unknown>
#7 0x7fcec8bc1461 <unknown>
#8 0x7fcec8a530d0 <unknown>
#9 0x7fcec8a532a6 <unknown>
#10 0x7fcec8a4a255 <unknown>
#11 0x7fcec8a4a306 QtWebEngineCore::WebContentsAdapter::WebContentsAdapter()
#12 0x7fcecd316866 <unknown>
#13 0x7fcecd3145b4 <unknown>
#14 0x7fcecd314742 QWebEnginePage::QWebEnginePage()
#15 0x7fcecd346369 sipQWebEnginePage::sipQWebEnginePage()
#16 0x7fcecd3464f2 init_type_QWebEnginePage
#17 0x7fced1d11f04 <unknown>
#18 0x5602c7f4f9b7 <unknown>
#19 0x5602c7ebfd7b <unknown>
#20 0x5602c7f4f7ce <unknown>
#21 0x5602c7f71cba <unknown>
#22 0x5602c7f49d7b <unknown>
#23 0x5602c7ebff5f <unknown>
#24 0x5602c7ec4a03 <unknown>
#25 0x5602c7ebf99e <unknown>
#26 0x5602c7f1c02b <unknown>
#27 0x5602c7f4f9b7 <unknown>
#28 0x5602c7ebfd7b <unknown>
#29 0x5602c7f4f7ce <unknown>
#30 0x5602c7f71cba <unknown>
#31 0x5602c7f49d7b <unknown>
#32 0x5602c7ebff5f <unknown>
#33 0x5602c7ec4a03 <unknown>
#34 0x5602c7ebf99e <unknown>
#35 0x5602c7f1c02b <unknown>
#36 0x5602c7f4f9b7 <unknown>
#37 0x5602c7ebfd7b <unknown>
#38 0x5602c7f4f7ce <unknown>
#39 0x5602c7f71cba <unknown>
#40 0x5602c7f49d7b <unknown>
#41 0x5602c7ebff5f <unknown>
#42 0x5602c7ec4a03 <unknown>
#43 0x5602c7ebf99e <unknown>
#44 0x5602c7f1c02b <unknown>
#45 0x5602c7f4f9b7 <unknown>
#46 0x5602c7ebfd7b <unknown>
#47 0x5602c7f4f7ce <unknown>
#48 0x5602c7f71cba <unknown>
#49 0x5602c7f48dae <unknown>
#50 0x5602c7f49e1b <unknown>
#51 0x5602c7ebff5f <unknown>
#52 0x5602c7ec4a03 <unknown>
#53 0x5602c7ebf99e <unknown>
#54 0x5602c7f1c02b <unknown>
#55 0x5602c7f4f9b7 <unknown>
#56 0x5602c7ebfd7b <unknown>
#57 0x5602c7f4f7ce <unknown>
#58 0x5602c7f71cba <unknown>
#59 0x5602c7f48dae <unknown>
#60 0x5602c7f49941 <unknown>
#61 0x5602c7f4f755 <unknown>

Aborted (core dumped)

Ok, I've removed completely pythons 3.4 and 3.6 that were in the system (from RHEL and EPEL repositories) and installed Anaconda.

FYI, Anaconda doesn't touch any other Python installs on your machine, including your system Python, so you don't need to remove any others in the future. Its completely self-contained.

The only "special" thing about storage in this machine is that it has the logical volumes attached directly to it. This includes the /home directory, which is mounted as a local filesystem.

Seems likely to be related, as strange as it sounds, given the nature of the error. It shouldn't happen, but clearly, for some reason, it does. Something to do with your storage interacting with a possible bug in QtWebEngine it seems.

Should I open a separate thread, or this should be unrelated to Spyder?

Unrelated to Spyder, I'm virtually certain, as the problem isn't anywhere in Spyder's codebase or even in Python it all. Skimming over the top three Google results, It appears it might be some sort of bug in QtWebEngine on Linux, which also cropped up in Chromium and various KDE applications. You could try asking on our Google Group or on one of the Stack Exchange sites to see if anyone else has seen it, or try your local sysadmin. Unfortunately, as it appears to be in KDE itself and specific to your machine configuration, we have no control over it :(
Hope you get it figured out!

Righto. Will do, thanks!


Ticking issue in IE - in response to #8

This seems to correct the IE ticking issue #8.
If its OK to commit that would be great

Thanks @fitzy90, however this change silents the issue instead of fixing it, which can potentially hide real errors later. We need to figure out why stub is undefined (or null) in some cases, maybe event.target is not correct or maybe IE doesn't accept expando?
I'm not able to reproduce this issue in IE11, what version are you using to reproduce this error? can you log the content of event and node when stub is undefined?

Hey
I have managed to replicate for you, see the test case link. I haven’t looked at it for very long so I can’t really comment.
If you use IE11 to navigate here you should see the issue in the developer tools
http://chart.tech-solutions.co.uk/
Let me know if can help any further
Thanks
Jack
From: Simon Brunel<EMAIL_ADDRESS>Sent: 02 March 2018 13:28
To: chartjs/chartjs-plugin-deferred
Cc: Jack Fitzgerald; Mention
Subject: Re: [chartjs/chartjs-plugin-deferred] Ticking issue in IE - in response to #8 (#10)
Thanks @fitzy90https://github.com/fitzy90, however this change silents the issue instead of fixing it, which can potentially hide real errors later. We need to figure out why stub is undefined (or null) in some cases, maybe event.target is not correct or maybe IE doesn't accept expando?
I'm not able to reproduce this issue in IE11, what version are you using to reproduce this error? can you log the content of event and node when stub is undefined?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/chartjs/chartjs-plugin-deferred/pull/10#issuecomment-369920441, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AfISlDDDT7ttW-l55qHiB7NmVF50EenRks5taUjKgaJpZM4SZ4Cv.

Thanks @fitzy90, I can reproduce it! I think the problem is that the scroll event is not correctly removed (at this line), certainly because Chart.helpers.removeEvent doesn't call the associated "remove" method matching the call at line 104

@fitzy90 I pushed a fix for this issue in master (ee8c7a9ee18558304ed9d065f8354db709b964c9), can you confirm that it works correctly now?

@simonbrunel I can confirm that works perfectly! Thanks for your help on this!

Thanks @fitzy90, I'm closing this PR and will release the fix very soon.


RayCast get_collider() (3.0 beta 2)

Godot version:
3.0 beta 2
OS/device including version:
Ubuntu 16.04 64
Issue description:
Object caught in the beam remains in its getter forever
In BULLET mode
Minimal reproduction project:
Bug physics.zip

Can confirm on Windows 10 for a recent-ish pull of master.

Ubuntu 17.10, Godot 3.0 Beta 2, AMD Radeon R9 Fury
I can confirm the behavior you're reporting and it's not what I would expect.  However, I can't tell if this is intended behavior and/or intended usage of the API.
http://docs.godotengine.org/en/latest/classes/class_raycast.html?highlight=RayCast#class-raycast-is-colliding
When incorporating the is_colliding() check, the behavior is what I would expect.
func _process(delta):
	var ray = get_node('ray')
	if ray.is_colliding():
		print(ray.get_collider())

3.1-alpha1 The problem is no longer there.


Image not uploaded pls resdolve it

image not uploaded in blog management. can you fix it.

@khushub  can you please let me know on which module or area you are not able to upload a file.


Cleanup documentation

Remove reference to zlog (zillow internal logging implementation)
Added worker-deadletter and worker-delay
Add maked targets for new examples
Updated readme.md
Updated DeadLetterTopicConfig to honor parent consumer config's clientid

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 0% with 2 lines in your changes missing coverage. Please review.

Project coverage is 93.86%. Comparing base (a16d04c) to head (27902d7).

Files
Patch %
Lines

work.go
0.00%
1 Missing and 1 partial :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main       #7      +/-   ##
==========================================
+ Coverage   93.77%   93.86%   +0.08%
==========================================
  Files          17       17
  Lines        1286     1288       +2
==========================================
+ Hits         1206     1209       +3
+ Misses         53       52       -1
  Partials       27       27

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


move repo kazimuth --> jdf

replace all urls -- including github.com and travis-ci.org

Closes #138


Build failing for Docker

Describe the bug
The WalletConsole utility shows incorrect Cardano addrDefault value, so I want to build from scratch to see if it works correctly but the build fails with the error below. The WalletConsole was accessed using docker run -i -t trustwallet/wallet-core /wallet-core/build/walletconsole/walletconsole. Related issue #2924.
#14 196.1 /wallet-core/src/Everscale/CommonTON/RawAddress.cpp:23:33: fatal error: use of undeclared identifier 'LONG_MAX'
#14 196.1     if (errno == ERANGE && l == LONG_MAX) {
#14 196.1                                 ^
#14 196.1 1 error generated.
#14 196.1 make[3]: *** [CMakeFiles/TrustWalletCore.dir/build.make:1812: CMakeFiles/TrustWalletCore.dir/src/Everscale/CommonTON/RawAddress.cpp.o] Error 1
#14 196.1 make[3]: *** Waiting for unfinished jobs....
#14 199.3 make[3]: Leaving directory '/wallet-core/build'
#14 199.3 make[2]: *** [CMakeFiles/Makefile2:252: CMakeFiles/TrustWalletCore.dir/all] Error 2
#14 199.3 make[2]: Leaving directory '/wallet-core/build'
#14 199.3 make[1]: *** [CMakeFiles/Makefile2:259: CMakeFiles/TrustWalletCore.dir/rule] Error 2
#14 199.3 make[1]: Leaving directory '/wallet-core/build'
#14 199.3 make: *** [Makefile:182: TrustWalletCore] Error 2
#14 199.3 make: Leaving directory '/wallet-core/build'
------
executor failed running [/bin/bash -o pipefail -c tools/generate-files     && cmake -H. -Bbuild -DCMAKE_BUILD_TYPE=Debug     && make -Cbuild -j12 TrustWalletCore]: exit code: 2

To Reproduce

Change line 23 of Dockerfile to RUN wget http://archive.ubuntu.com/ubuntu/pool/main/o/openssl/libssl1.1_1.1.1f-1ubuntu2.17_amd64.deb && dpkg -i ./libssl1.1_1.1.1f-1ubuntu2.17_amd64.deb since 2.16 returns 404
docker build . -t wallet-core-dev

Expected behavior
The build to succeed

#2981 should fix it


Where to find service interface?

Hi,
I followed the instructions to install duofern in my HomeAssistant and it seems to work.
But now I need to pair my DuoFern devices and according to the instructions I need the "service interface" for this.
I clicked all over the HomeAssistant GUI but I'm not able to find the part shown in the screenshot.
Where is this hidden?
Thanks

It's "Developer Tools -> Action" ("Developer Tools -> Service "in HA 2024.7 or older)
If you have 'my' integration enabled, you can click below link:
https://my.home-assistant.io/redirect/developer_call_service/?service=duofern.start_pairing

Aaah! Thank you so much!
Maybe the instructions could be improved or am I the first one stumbling across this?

You're the first. Homeassistant has changed the naming in the menu just a few weeks ago.


Error: Attempting to use a disconnected port object

Hey @kumar303, thank you for updating the readme.
I followed it very carefully and it still won't work for me.
Here's what I see in the log:
[1028:1028:0922/133011.626205:INFO:CONSOLE(11)] "Sending: link http://d.aliexpress.com/http://trade.alibaba.com/order_detail.htm?order_id=503899967560071&tracelog=rowan&rowan_id1=buyerAcceptGoodsTORemindGoodsAcceptToBuyer_en_US_2017-09-21&rowan_msg_id=007150389996756$47a5c37d7e814915a41305051b5833b6&ck=in_edm_other ", source: chrome-extension://pcnngcfomnggkpeoffiigmnlcpnnpbgp/background.js (11)
[1028:1028:0922/133011.626359:INFO:CONSOLE(0)] "Error in event handler for contextMenus: Error: Attempting to use a disconnected port object
    at onclick (chrome-extension://pcnngcfomnggkpeoffiigmnlcpnnpbgp/background.js:12:10)", source: chrome-extension://pcnngcfomnggkpeoffiigmnlcpnnpbgp/_generated_background_page.html (0)

I tried to keep the app running in the background with python default_opener.py, but it doesn't make a difference.

The port gets connected here so I would check earlier in the log to see if there's a reason for why it got disconnected. As I understand it, Chrome starts up its own process to run default_opener.py in the background but I don't know when that starts. Maybe when Chrome start up? If there is some error in the script (like maybe you have a different version of Python) then I suppose it will crash and that could cause the error you saw but that's just a guess.
On my machine it uses python 2.7.13 to run the script.  I just added it so pull in these git changes and reload the extension (or restart Chrome). https://github.com/kumar303/default-opener/commit/d33d1135f67687da54e7f1ed8eb8a245bbe1c529

Adding port = chrome.runtime.connectNative("default_opener"); to the disconnect listener seems to fix it.


Add support for AlternateNamesV2

This PR adds support for the AlternateNamesV2 file type (see #5). It really just adds two new fields to the AlternateName entity that existed already - To and From, denoting the start and end of the historical period during which a particular alternate name was in usage. These fields have a type of String - I wasn't sure if this was the most appropriate type (versus DateTime, for example) but there seem to be a good few edge cases in the data itself (see, for example, alternate name ID 13653649). Tests and some new test data are included.

Hi! Thanks very much! I'll have a look at this ASAP and merge it. From a first glance it looks great!


Refine "vela traits" format if it failed to resolve a trait template

I applied a TraitDefinition, in which, the value v1 of output.apiVersion is not in double-quotes. vela traits doesn't display in the right format.
$ vela traits
WARN: handle trait template `loadbalancer` failed
: output.apiVersion: reference "v1" not found (and 2 more errors), you will unable to use this trait capabilityNAME     	DESCRIPTION                                                      	APPLIES TO
autoscale	Automatically scale the app following certain triggers or metrics	webservice
         	                                                                 	worker
metrics  	Configure metrics targets to be monitored for the app            	webservice
         	                                                                 	task
rollout  	Configure canary deployment strategy to release the app          	webservice
route    	Configure route policy to the app                                	webservice
scaler   	Manually scale the app                                           	webservice
         	                                                                 	worker

can you give the traitdefinition yaml here?

apiVersion: core.oam.dev/v1alpha2
kind: TraitDefinition
metadata:
  name: loadbalancer
  annotations:
    definition.oam.dev/description: Provide loadbalancer for an application and publish its service"
spec:
  appliesToWorkloads:
    - webservice
  workloadRefPath: spec.workloadRef
  definitionRef:
    name: service
  extension:
    template: |
      output: {
        apiVersion: v1
        kind: "Service"
        spec: {
          ports: parameter.ports
          selector: {
            "app.oam.dev/component": context.name
          }
          type: "LoadBalancer"
        }
      }

      parameter: {
      	ports: [...{
            name: string
            port: *80 | int
            protocol: *"TCP" | string
            targetPort: int
      	}]
      }

Of course you need to keep double-quote for v1, it's cue format.
In cuelang, you use "v1" to define it as a string. Use v1 to define it as a variable.

It's not, the .cue part can pass eval/export validation.


Steem Bot Tracker 404 Error

Expected behavior
Clicking on the logo shown in the left of the top navigation bar should take you to the home page of the site.
Actual behavior
Clicking on the logo shown in the left of the top navigation bar should takes you to a page that shows a 404 when clicked on certain pages.
How to reproduce
A) Visit https://steembottracker.com/
B) Click on Tools in the top navigation
C) Click on Curation Estimator
D) Once the page has loaded on the curation estimator page, click on the steemtracker logo located at the top left corner of page in the navigation area.
Browser: Google Chrome (Version 63.0.3239.132 (Official Build) (64-bit))
Operating system: MacOS HighSierra Version 10.13
Recording Of The Bug
A video of the bug can be found here: https://d.tube/#!/v/tobias-g/u9ktmw23
Posted on Utopian.io -  Rewarding Open Source Contributors

This should be fixed now, thanks for reporting the issue!


🐛 Rome check command ignoring file arguments

Environment

$ rome rage --summary
Environment Variables
  Object {
    COLORTERM: "truecolor"
    LANG: "en_US.UTF-8"
    PATH: "/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Users/Yasser/bin:/Users/Yasser/bin"
    TERM: "xterm-256color"
    TERM_PROGRAM: "vscode"
    USER: "Yasser"
  }

User Config
  unset

Rome Version
  10.0.3-beta

Node Version
  14.6.0

Platform
  darwin x64 19.5.0

Terminal Features
  Object {
    background: "unknown"
    colorDepth: 24
    columns: 157
    cursor: true
    hyperlinks: true
    isTTY: true
    unicode: true
  }

Client Flags
  Object {
    clientName: "cli"
    cwd: "/Users/Yasser/Dev/Test/TestRome/test"
    realCwd: "/Users/Yasser/Dev/Test/TestRome/test"
    silent: false
  }

Server Status
  Object {
    projects: Array [
      Object {id: 0}
      Object {id: 1}
    ]
    server: Object {
      heapTotal: 56_242_176
      pid: 56_881
      uptime: 0.625772617
    }
    workers: Array [
      Object {
        astCacheSize: 0
        heapTotal: 56_242_176
        ownedBytes: 0
        ownedFileCount: 0
        pid: 56_881
        uptime: 0.625644493
      }
    ]
  }

Steps To Reproduce

In a project with files foo.ts and bar.ts both containing errors, running rome check foo.ts results in:
 bar.ts:1:4 lint/js/noUnusedVariables ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ✖ The let variable bar is unused.

    let bar;
        ^^^

  ℹ Unused variables are dead code and usually the result of incomplete refactoring.

 foo.ts:1:4 lint/js/noUnusedVariables ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ✖ The let variable foo is unused.

    let foo;
        ^^^

  ℹ Unused variables are dead code and usually the result of incomplete refactoring.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Expected Results

Rome should only check and report diagnostics for foo.ts

Relevant method is ServerRequest#glob which is meant to default the args to the query if they weren't supplied.


MULTI-GITTER PR: migration github-config-and-gitignore-changes

Summary by Sourcery
Revise GitHub configuration files to improve contribution guidelines, update CI workflows, and introduce a new deployment workflow for demo environments.
Enhancements:

Update the CONTRIBUTING.md file to include additional guidance for Alaska Airlines employees and clarify the process for submitting issues and pull requests.
Revise the CODE_OF_CONDUCT.md to improve readability and update the enforcement contact information.
Enhance the ISSUE_TEMPLATE files by adding an 'exit criteria' section to better define when an issue can be closed.

CI:

Modify the testPublish.yml workflow to ensure it only releases on push to main or beta branches and update the Node.js version specification.

Deployment:

Introduce a new publishDemo.yml workflow to automate the deployment of demo environments on pull requests to the main branch.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Message extension project cannot be created on 2.7.0-preview3

i'm getting the exception, if i try to create a message extension:

staticTab is not defined.

Related issue:
https://github.com/OfficeDev/generator-teams/issues/51

Fixed in 2.7.0-preview4 (da75026f1944a500aa1b134f978a7564ca18a02e)


 We will review this ASAP

setting to draft due to the following observations
I will provide more guidance how we should proceed with this PR in near future


Reduce Travis Logs v2

Description

Continuation of #5039
Additions:

LogHandler Lock, used to stop other classes from overwriting the log handler, by default it is false. I used this in our test initialize to force the rest of the tests to maintain my log handler. Check changes to see the tests that absolutely need to change loghandler and how it is dealt with. Simply store the old handler and lock setting, replace it with the appropriate log handler, then reset it when completed.
Silence dotnet building the stubs in travis

Related Issue

Motivation and Context

This continues the changes made in #5039, there were a lot in there that greatly reduced the log size but I was running into a couple issues that I hope this PR will address and limit it even further.
When it comes to the LogHandler lock I am not sure this is the right implementation but it was a concept that I think is worth looking at. Mostly because some of our classes such as QuantBook will set the log handler on its own. With this implementation our lock will stop it from being changed.
Requires Documentation Change

N/A
How Has This Been Tested?

All tests have been ran and are successful
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[x] Refactor (non-breaking change which improves implementation)
[ ] Performance (non-breaking change which improves performance. Please add associated performance test and results)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Non-functional change (xml comments/documentation/etc)

Checklist:

[x] My code follows the code style of this project.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.
[x] My branch follows the naming convention bug-<issue#>-<description> or feature-<issue#>-<description>

Travis Log after the last commit is only 7812 Lines, if this is merged we will see the buildstubs script length as well which will hopefully only make it a little longer because I quieted the dotnet call that build the stubs.

I'd prefer we "set properly" the classes who change the log handler, rather than lock it from being changed which could introduce bugs later when the logs don't change as expected.

Gotcha, I thought that may be the case. I will have to find a way to work around the classes that do change it so we can maintain one specific loggingHandler for all the tests that don't need something specific.

You can reduce the Travis logs on tag builds by an additional ~2,000 lines if you revert the changes made in #4933. These changes were only needed temporarily to debug what turned out to be an authentication issue, but were never reverted after that issue was fixed.

Thank you Jasper!!

Ouch switching AlgorithmRunner back to ConsoleLogHandler doubled the travis log to 28k 😬


Chain support

Please add support for Optimism Mainnet and Optimism Kovan

Hi,
I have never used Optimistm yet 🤦♂
Can you confirm me these values are correct?
{
        name: 'Optimistic Ethereum',
        chainName: 'optimistic',
        chainId: 10,
        gas: 'auto',
        defaultRpcUrl: 'hhttps://mainnet.optimism.io'
},
{
        name: 'Optimistic Ethereum Testnet Kovan',
        chainName: 'optimisticTestnetKovan',
        chainId: 56,
        gas: 'auto',
        defaultRpcUrl: 'https://bsc-dataseed1.binance.org'
}

Thank you

Hi,
Thanks for the quick response.
Mainnet is correct.
For Optimism Kovan, the correct chainId is 69 and defaultRpcUrl is https://kovan.optimism.io/
Looks like the values you have is for BSC mainnet

Thank you :)
This has been included in #20 package v0.0.3 💪


Documentation: Typo?

Hi
in https://github.com/bitcoin-core/HWI/blob/7fd2cead481197f88cad180757b5cf982eb0a0b1/hwilib/common.py#L41C1-L42
there is  P2WPSH. But should it not be P2WSH as defined in https://github.com/bitcoin/bips/blob/master/bip-0048.mediawiki ?

I think so. P2WSH/P2SH-P2WSH for scripts.


Live editing causing flickering

Which Umbraco.Community.BlockPreview version are you using?
1.8.4
Which Umbraco version are you using? For example: 10.4.0 - don't just write v10
13.2.2
Bug summary
When editing block with live editing enabled it will cause flickering of editor in background.
Steps to reproduce
Add few blocks to block grid
modify one (best example when rte is in) and see editor in background is flickering
Expected result / actual result
Editors post loading are not flickering but updating with required changes.

@rickbutterfield I have investigated it and it could be solved easily by changing:
function loadPreview(content, settings) {
      $scope.markup = $sce.trustAsHtml('
Loading preview
');
      $scope.loading = true;

      var formattedBlockData = {
        layout: $scope.block.layout,
        contentData: [content || $scope.block.data],
        settingsData: [settings || $scope.block.settingsData]
      };

      previewResource.getPreview(formattedBlockData, $scope.id, $scope.blockEditorAlias, $scope.model.constructor.name == 'BlockGridBlockController', $scope.language).then(function (data) {
        $scope.markup = $sce.trustAsHtml(data);
        $scope.loading = false;
      });
    }

    loadPreview($scope.block.data, $scope.block.settingsData);

to
function loadPreview(content, settings) {
      var formattedBlockData = {
        layout: $scope.block.layout,
        contentData: [content || $scope.block.data],
        settingsData: [settings || $scope.block.settingsData]
      };

      previewResource.getPreview(formattedBlockData, $scope.id, $scope.blockEditorAlias, $scope.model.constructor.name == 'BlockGridBlockController', $scope.language).then(function (data) {
        $scope.markup = $sce.trustAsHtml(data);
        $scope.loading = false;
      });
    }
    $scope.markup = $sce.trustAsHtml('
Loading preview
');
    $scope.loading = true;
    loadPreview($scope.block.data, $scope.block.settingsData);

Hey @bielu! This was released in 1.9.0, so that or any newer versions will have a fix in!


Good job ! bower ?

Thanx for your great work !
Will you support bower soon ?

Hi @kpt-yleviavant! I don't have lot of time these last weeks as you can see on my contributions, but it could be a quick & simple one, so I'll try to work on this in April.


Catch the error before the response is processed by goth.

The code introduced by #18185 gets the error from response after it was processed by goth.
That is incorrect, as goth (and golang.org/x/oauth) doesn't really care about the error, and it sends a token request with an empty authorization code to the server anyway, which always results in a oauth2: cannot fetch token: 400 Bad Request error from goth.
It means that unless the "state" parameter is omitted from the error response (which is required to be present, according to RFC 6749, Section <IP_ADDRESS>) or the page is reloaded (makes the session invalid), a 500 Internal Server Error page will be displayed.
This fixes it by handling the error before the request is passed to goth.

(My review can be dismissed if we can get an answer on this.)

Actually do we to tell goth that this request has failed and to cancel any data it has too?

Yes.

IMO it's also fine for doing nothing in the error callback. Just like there is a network error occurring during the callback, Gitea even wont't get the response callback, then nothing happens, nothing wrong in the end.
And it's also fine to call the Logout to clear the data in session, just like what oauth2Source.Callback does (oauth2Source.Callback -> gothic.CompleteUserAuth -> Logout).
LGTM


Moved PySparkMagClass.py to Shared folder

OPS Build status updates of commit d275eb2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

academic-services/graph/media/databricks/import-notebook.png
:white_check_mark:Succeeded

academic-services/graph/media/databricks/import-shared-notebook.png
:white_check_mark:Succeeded

academic-services/graph/samples-azure-databricks.md
:white_check_mark:Succeeded

academic-services/graph/tutorial-azure-databricks-hindex.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 incorrect cross-reference label

Starting from the latest main as of 2023-Apr-30, there is only 1 warning about invalid cross-references that I see when creating HTML and PDF versions of the spec, and this PR fixes that.
It also updates what I believe is the only occurrence of "infinite-precision integer" that has not yet been replaced with "arbitrary-precision integer"

In this document https://p4.org/p4-spec/docs/p4-16-working-draft.html you can search for [#.

With commit 2 of this PR, there are no more occurrences of [# in the HTML output.

Thanks @jfingerh!


Conflicting information

The phrase on this page, 'only one management group contains a subscription' seems to directly contradict the explanation and illustration here.

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

ID: 4b24efd3-3fda-7c73-6bf6-cfed8a3e2785
Version Independent ID: 95e455f3-674a-7554-bfd8-d43e46c60271
Content: Organize and manage multiple Azure subscriptions - Cloud Adoption Framework
Content Source: docs/ready/azure-best-practices/organize-subscriptions.md
Service: cloud-adoption-framework
Sub-service: ready
GitHub Login: @alexbuckgit
Microsoft Alias: abuck

Hi @sqlsolver,
Sorry for the delay.
The sentence 'only one management group contains a subscription' is correct. Each subscription can belong to one management group.
I don’t see today any diagram in your reference, and it seems that the referenced section was deleted.
I will close the ticket, but feel free to re-open if additional clarification is needed.

#please-close

The semantics are still incorrect. I understand the one-to-many
relationship between a management group and the subscriptions it
contains. What
the existing sentence, 'only one management group contains a
subscription', conveys is that among many management groups only one
contains a subscription. You might instead say, 'a single management group
contains one or more subscriptions' or call it a one-to-many relationship.
Either would be well understood.
On Tue, Jan 31, 2023 at 3:02 AM Federico Arambarri @.***>
wrote:

Hi @sqlsolver https://github.com/sqlsolver,
Sorry for the delay.
The sentence 'only one management group contains a subscription' is
correct. Each subscription can belong to one management group
https://learn.microsoft.com/azure/governance/management-groups/overview.
I don’t see today any diagram in your reference
https://learn.microsoft.com/azure/cloud-adoption-framework/ready/landing-zone/design-area/resource-org-subscriptions#mix-subscription-strategies,
and it seems that the referenced section was deleted.
I will close the ticket, but feel free to re-open if additional
clarification is needed.
—
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/cloud-adoption-framework/issues/952#issuecomment-1410157964,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABCVUJYWMCPGP3AGVVKAMMTWVDWN7ANCNFSM6AAAAAAQRVG4AI
.
You are receiving this because you were mentioned.Message ID:
@.***>


Preview release at 08 october can not load gltf

Bugs
Importing babylon like
<script src="https://cdn.babylonjs.com/babylon.js"></script>
<script src="https://preview.babylonjs.com/inspector/babylon.inspector.bundle.js"></script>
<script src="https://preview.babylonjs.com/loaders/babylonjs.loaders.min.js"></script>
<script src="https://cdn.babylonjs.com/materialsLibrary/babylonjs.materials.min.js"></script>
<script src="https://cdn.babylonjs.com/postProcessesLibrary/babylonjs.postProcess.min.js"></script>
<script src="https://cdn.babylonjs.com/proceduralTexturesLibrary/babylonjs.proceduralTextures.min.js"></script>
<script src="https://cdn.babylonjs.com/serializers/babylonjs.serializers.min.js"></script>

Loading a gltf like
const engine = new BABYLON.Engine(canvas, true);
var loader = BABYLON.SceneLoader.Load("/assets/", "map.gltf", engine, function (scene) {
		console.log("here")
	});
})

localhost:3000/assets/map.gltf returns the file.

Expected result:
Have the console log "here".

Current result:

Uncaught TypeError: Cannot read property 'asset' of undefined
    at e._getLoader (babylonjs.loaders.min.js:1)
    at e.loadAsync (babylonjs.loaders.min.js:1)
    at babylon.js:formatted:45829
    at f (babylon.js:formatted:45576)
    at XMLHttpRequest.p (babylon.js:formatted:6575)

This was working with preview yesterday, but now it is not.
File in question is:
https://d2nmr6p48f8xwg.cloudfront.net/instructions_steps/steps_map_entities/map_files/000/003/746/4fb577a65be1dd90424d6f571fe5cff901275196/map.json

Just download and rename to map.gltf
Update:
If I try to the file with fetch() the following code works:
fetch("/assets/map.gltf")
    .then(function(response) {
      return response.json();
    })
    .then(function(jsonData) {
    	console.log("here")
    });

The file is loaded. Its a json.
Update 2:
Trying to load as gltf string
	fetch("/assets/map.gltf")
	    .then(function(response) {
	      return response.text();
	    })
	    .then(function(gltfAsString) {
	    	BABYLON.SceneLoader.Append("", "data:"+gltfAsString, scene, function(scene) {
	    		console.log("here");
	    	})
	    });

Same error occurs.
Uncaught (in promise) TypeError: Cannot read property 'asset' of undefined
    at e._getLoader (babylonjs.loaders.min.js:1)
    at e.loadAsync (babylonjs.loaders.min.js:1)
    at babylon.js:16
    at f (babylon.js:16)
    at Function.e._loadData (babylon.js:16)
    at Function.e.Append (babylon.js:16)
    at babylon_gltf_data_handler.self-cf4e0e058249d11825fc327b96c779c0f30ff0998707023feab97b334e58ddc4.js?body=1:202

I have tried to load to file in sandbox babylon and it is successfully loading
Update 3 - file is loading correctly with cdn and as a string instead of preview:
Using cdn. instead of preview.
I have changed
<script src="https://preview.babylonjs.com/loaders/babylonjs.loaders.min.js"></script>

to
<script src="https://cdn.babylonjs.com/loaders/babylonjs.loaders.min.js"></script>

And I have used
fetch("/assets/map.gltf")
	    .then(function(response) {
	      return response.text();
	    })
	    .then(function(gltfAsString) {
	    	BABYLON.SceneLoader.Append("", "data:"+gltfAsString, scene, function(scene) {
	    		console.log("here");
	    	})
	    });

Output in console is:
here

But using SceneLoader.Load() throws an error
fetch("/assets/map.gltf")
	    .then(function(response) {
	      return response.text();
	    })
	    .then(function(gltfAsString) {
	    	BABYLON.SceneLoader.Load("/assets/", "map.gltf", engine, function(scene) {
	    		console.log("here");
	    	})
	    });

throws
Uncaught TypeError: Cannot read property 'asset' of undefined
    at e._getLoader (babylonjs.loaders.min.js:1)
    at e.loadAsync (babylonjs.loaders.min.js:1)
    at babylon.js:16
    at f (babylon.js:16)
    at XMLHttpRequest.p (babylon.js:16)

So as a string with "cdn." and SceneLoader.Append it is loading correctly, but with SceneLoader.Load the same file is not loading.

Turns out I should have everything to preview.
I've changed
<script src="https://cdn.babylonjs.com/babylon.js"></script>
<script src="https://preview.babylonjs.com/inspector/babylon.inspector.bundle.js"></script>
<script src="https://preview.babylonjs.com/loaders/babylonjs.loaders.min.js"></script>
<script src="https://cdn.babylonjs.com/materialsLibrary/babylonjs.materials.min.js"></script>
<script src="https://cdn.babylonjs.com/postProcessesLibrary/babylonjs.postProcess.min.js"></script>
<script src="https://cdn.babylonjs.com/proceduralTexturesLibrary/babylonjs.proceduralTextures.min.js"></script>
<script src="https://cdn.babylonjs.com/serializers/babylonjs.serializers.min.js"></script>

<script src="https://preview.babylonjs.com/babylon.js"></script>
<script src="https://preview.babylonjs.com/inspector/babylon.inspector.bundle.js"></script>
<script src="https://preview.babylonjs.com/loaders/babylonjs.loaders.min.js"></script>
<script src="https://preview.babylonjs.com/materialsLibrary/babylonjs.materials.min.js"></script>
<script src="https://preview.babylonjs.com/postProcessesLibrary/babylonjs.postProcess.min.js"></script>
<script src="https://preview.babylonjs.com/proceduralTexturesLibrary/babylonjs.proceduralTextures.min.js"></script>
<script src="https://preview.babylonjs.com/serializers/babylonjs.serializers.min.js"></script>

Not sure if this is a bug now. Should the preview of loaders be expected to work to the cdn of babylon.js. If not, than this is probably not a bug.

Everything should be at the same version to work together as new version of the loader could need new apis from core.
Thanks for the complete details of your issue :-)


Modules doesn't work

Describe the issue
Hello all, i'm sure i have installed all dependencies for polybar and modules, but they still doesn't work.
When i'm launching polybar with this command line : polybar -l info white (white is the name of my polybar), i have theses results endlessly :

Bar window: 0x0800002
module/volume: Rebuilding cache
module/battery: Rebuilding cache
module/mpd: Rebuilding cache
module/mpd: Hiding module since queue is empty
module/i3: Rebuilding cache
module/wlan: Rebuilding cache
module/cpu: Rebuilding cache
module/date: Rebuilding cache
module/time: Rebuilding cache
module/powermenu: Rebuilding cache
Redrawing bar window
Redrawing bar window
Redrawing bar window
module/battery: Polling values (inotify fallback)
module/battery: Rebuilding cache
module/cpu: Rebuilding cache
Redrawing bar window
module/battery: Rebuilding cache
module/cpu: Rebuilding cache
module/time: Rebuilding cache
Redrawing bar window
module/battery: Rebuilding cache
module/cpu: Rebuilding cache
Redrawing bar window
module/battery: Polling values (inotify fallback)
module/battery: Rebuilding cache
Redrawing bar window
module/battery: Rebuilding cache
module/cpu: Rebuilding cache
module/battery: Rebuilding cache
module/wlan: Rebuilding cache
module/cpu: Rebuilding cache
module/battery: Polling values (inotify fallback)

I'm working on Ubuntu 18.04 with i3-gaps
Thanks for any helpful informations

Could you please post the entire output of polybar -l info white, not just the last few lines. Any errors you get often appear at the beginning.

I except that i i could see all wifi networks around me.
Also if i click on the shutdown button, i can see reboot and power off buttons but nothing happens if click on them.

But the bar actually displays correctly?

The problem is if i click on wifi modules for example, nothing happens.
I except that i i could see all wifi networks around me.

Polybar doesn't have that feature built-in

Also if i click on the shutdown button, i can see reboot and power off buttons but nothing happens if click on them.

Well, it depends on how you configured them. If you used the sample config, the commands tied to those buttons are sudo reboot and sudo poweroff. This often requires you to enter a password. You'll probably have to reconfigure the powermenu module to use reboot and poweroff commands that work on your system without entering a password.

Yes bar displays correctly, but it's oblige me to disconnect from i3 to use a wlan network..
Ok i will dig it, thanks for your help! :)

Ok i just found the command nmtui which let me see all wlan networks.
You can close the ticket :)

but it's oblige me to disconnect from i3 to use a wlan network..

Why? Connecting to a wifi network should be completely indepent of polybar.
I will close this as it seems the bar is actually working correctly.


Move SHA from KeyVault common to Azure Core

After talking to the team, there's not a real benefit right now from moving SHA from KeyVault to Core, as no other service is using it.
So, leaving SHA in KeyVault only until some other service requires it


[Console Settings] - on clicking the administrator, the page crashes to Something went wrong error message

Describe the issue:
How to reproduce:
Pack produced: https://wso2.org/jenkins/job/products/job/product-is/4957/

Login to the console
Click on Console Settings
Click on the Administrator

Actual behavior:
The user is redirected to the page:

Error in Stack trace:

The stack trace produced show
Environment information (Please complete the following information; remove  any unnecessary fields) :

Product Version: [e.g., IS 5.10.0, IS 5.9.0] - IS 7.0 RC1 SNAPSHOT
OS: [e.g., Windows, Linux, Mac] - MAC
Database: [e.g., MySQL, H2] - ANY
Userstore: [e.g., LDAP, JDBC]

Optional Fields
Related issues:

Suggested labels:

Duplicate of https://github.com/wso2/product-is/issues/18288


Make sure Commands are indexed from metadata by Discord

We had a misunderstanding. There is no way to speed up the process for now.
Discord takes almost 24h to actually index the commands out of metadata.
Commands will come in after phase1.
First we need to show DATA


ci: use the latest stable version of Deno

This should fix the fmt differences between v2 and v1

Confer #1132


fixing the unit test race condition

put in a mock for _send_upstream  to avoid the queue being drained

cc @rogaha
LGTM

LGTM, I did the same thing locally! :)


The cache should be or offer an option to be thread-safe

In the way to test the QNCache to find a concurrency issue, we found that it is 100% thread safe. So, it doesn't need an option to make it (or not) thread safe.


Adding to this.$options.computed during beforeCreate only works if computed is already defined on component

Version
3.0.4
Reproduction link
https://jsfiddle.net/6k3nod2c/
Steps to reproduce
Create a component / app with a mixin that adds to this.$options.computed.
const mixin = {
  beforeCreate() {
    if (!this.$options.computed) {
      this.$options.computed = {};
    }

    this.$options.computed.value = () => {
    	return 'works';
    }
  }
}

Vue.createApp({
  mixins: [mixin],
  // computed: {} // Uncommenting this line makes it work
}).mount('#app')

What is expected?
Expect this.value to be "works".
What is actually happening?
this.value is undefined.

In vue 2 this worked.
In vue 3 this only works if the computed option is already defined.

only components change could be expected work right in beforeCreated, not including dynamic methods computed inject props.
because they are pre defined in the prototype, not define for each instance. and only root instance (new Vue / Vue.createApp) won't do that, component in compontents or registered in Vue.component or extended by Vue.extend, they will all do that for performance.

The example was a simplification, so it's not that simple. I encountered this bug when upgrading to Vue 3 where this used to work.
In our app we have a global mixin that looks at another $options to generate computed properties.
Something like:
const mixin = {
  beforeCreate() {
    const magicOptions = this.$options.magic;

    for (const alias in magicOptions) {
      // subscribe to kv store
      const getterAndSetter = subscribe(magicOptions[alias]);

      this.$options.computed[alias] = getterAndSetter;
    }
  },
  unmounted() {
    // unsubscribe when
    this.$options.magic.forEach(unsubscribe);
  }
}

Then any component can define a "magic" object to subscribe to the backend, and subscription is stopped when component is removed.
export default {
  magic: {
    state: 'some-key-in-the-kv-store',
  },
  mounted() {
    console.log('state', this.state);
  },
  methods: {
    start() {
      this.state = 'start';
    }
  }
}

I might be doing this the wrong way, so any suggestions are welcome.

I think your solution is not completely，take a look about this PR @edison1105

The example was a simplification, so it's not that simple.

I see. I think add a hook beforeExtend which run once for each component would really help.

Add a lifecycle hook beforeExtend seems like not a recommendable resolve:

User have to modify code because its inconsistent with vue2
Ambiguous because its overlap with beforeCreate
Efficiency has not change(In fact i don't wunderstand why beforeCreate is indirect and inefficient)

We ran into the same issue in our app where we're creating a validation helper similar to Vuelidate.
We define a validations option in a component when we want some data properties to be validated, and a global mixin will add this to a computed property (so that validation rules can rely on other data properties with reactivity).
We ran into two problems:

As mentioned in this issue, if we didn't add an empty computed definition to our mixin, adding a dynamic computed property in beforeCreate didn't work. This seems due to how options is destructured at the start of applyOptions: https://github.com/vuejs/vue-next/blob/master/packages/runtime-core/src/componentOptions.ts#L478-L509

I believe this could be fixed by only defining computedOptions immediately before it's used: https://github.com/vuejs/vue-next/blob/master/packages/runtime-core/src/componentOptions.ts#L647
const computedOptions = options.computed;
if (computedOptions) {
...

This way if a beforeCreate hook added a computed object to options dynamically, it should be accessible here.

When we tried adding a computed definition to the global mixin, the computed object reference was shared between all component instances

For example, adding to the example from @MiniGod:
const mixin = {
  computed: {},
  beforeCreate() {
    if (condition) {
      this.$options.computed.example = () => {
      	return 'works';
      }
    }
  }
}

In theory this fixes the issue, however since mixin is defined as a const in our module, the reference to the mixin.computed object is shared among all component instances that apply the mixin. Then when the condition passes for any instance, and example is added to this.$options.computed, it is added to the referenced object, and hence it gets added to every instance created afterwards.
This may be something to be added in a separate issue, I only bring it up because it's a major issue in the only workaround I can see to this issue.

We ran into the same issue in our app where we're creating a validation helper similar to Vuelidate.
We define a validations option in a component when we want some data properties to be validated, and a global mixin will add this to a computed property (so that validation rules can rely on other data properties with reactivity).
We ran into two problems:

As mentioned in this issue, if we didn't add an empty computed definition to our mixin, adding a dynamic computed property in beforeCreate didn't work. This seems due to how options is destructured at the start of applyOptions: https://github.com/vuejs/vue-next/blob/master/packages/runtime-core/src/componentOptions.ts#L478-L509

I believe this could be fixed by only defining computedOptions immediately before it's used: https://github.com/vuejs/vue-next/blob/master/packages/runtime-core/src/componentOptions.ts#L647
const computedOptions = options.computed;
if (computedOptions) {
...

This way if a beforeCreate hook added a computed object to options dynamically, it should be accessible here.

When we tried adding a computed definition to the global mixin, the computed object reference was shared between all component instances

For example, adding to the example from @MiniGod:
const mixin = {
  computed: {},
  beforeCreate() {
    if (condition) {
      this.$options.computed.example = () => {
      	return 'works';
      }
    }
  }
}

In theory this fixes the issue, however since mixin is defined as a const in our module, the reference to the mixin.computed object is shared among all component instances that apply the mixin. Then when the condition passes for any instance, and example is added to this.$options.computed, it is added to the referenced object, and hence it gets added to every instance created afterwards.
This may be something to be added in a separate issue, I only bring it up because it's a major issue in the only workaround I can see to this issue.

I found a terrible (but working) solution:
define a property directly on an instance
// in beforeCreate-hook
const foo = computed(getter/setter)
Object.defineProperty(this, 'foo', {
    enumerable: true,
    configurable: true,
    get: ()=> foo.value,
    set: (v)=> foo.value=v
})

I found a terrible (but working) solution:
define a property directly on an instance
// in beforeCreate-hook
const foo = computed(getter/setter)
Object.defineProperty(this, 'foo', {
    enumerable: true,
    configurable: true,
    get: ()=> foo.value,
    set: (v)=> foo.value=v
})

This has been fixed by e2ca67b


"Rantito" .. typo on home page

From (https://berkin.me/rant/)
"Browse the documentation and familiarize yourself with all aspects of Rant. Engross yourself in every detail of every function, langauge feature, and construct available in the library."
As intriguing as it might be to have a LAN gauge in a text processing lib, the language features are even more interesting.  :)
Regards (and many thanks),
burque505

Oops! Just fixed it. Thanks!

That was fast! Thanks very much for the program.


C, C++, and Go do not show up in Service grouping

Service grouping currently doesn't work for C, C++ and Go because package name and Service name is not available for these reviews to  map. We don't have a mechanism to find this mapping for these reviews. Can you please file an issue? I will check what can be done to identify this info. all C++ reviews are listed under "Other -> Other" group.

I also found that Go (golang) shows up as "Other" with a C# icon and assembly name e.g., https://apiview.dev/Assemblies/Review/81f68e700dcd4243a0ced7223e4d71fa. Perhaps related, but I'm happy to open another bug if needed.
/cc @JeffreyRichter

Closing this issue since we removed service name-based grouping


The text rotation appears to have a bug, with extra points appearing in the transformation matrix for the rotation？

yes, its a limitation, as I paint characters using gl_points, which are square so when rotated enter in the next character area.


Added basic support for users api

Includes call for currently authenticated user's detailed data as well as public data for an arbitrary user.

Sorry, Benjamin, but I've been swamped the last week and haven't had a
chance to look at this yet. I will try to get to it this weekend,
though.
On Thu, Nov 24, 2011 at 7:04 PM, Benjamin Jackson
<EMAIL_ADDRESS>wrote:

Includes call for currently authenticated user's detailed data as well as public data for an arbitrary user.
You can merge this Pull Request by running:
git pull https://github.com/benjaminjackson/github-v3-api master
Or you can view, comment on it, or merge it online at:
https://github.com/jwilger/github-v3-api/pull/6
-- Commit Summary --

Added support for users api which allows clients to get the current authenticated user as well as an arbitrary user record by name.

-- File Changes --
M github-v3-api.gemspec (2)
M lib/github_v3_api.rb (10)
A lib/github_v3_api/user.rb (15)
A lib/github_v3_api/users_api.rb (40)
A spec/user_api_spec.rb (25)
A spec/user_spec.rb (38)
-- Patch Links --
https://github.com/jwilger/github-v3-api/pull/6.patch
 https://github.com/jwilger/github-v3-api/pull/6.diff

Reply to this email directly or view it on GitHub:
https://github.com/jwilger/github-v3-api/pull/6

--
Regards,
John Wilger
<EMAIL_ADDRESS>971-678-0999

OK, this is release in version 0.2.0 of the gem, which I just pushed up. Thanks for the contribution!

\o/
On Sunday, December 4, 2011, John Wilger <
<EMAIL_ADDRESS>wrote:

OK, this is release in version 0.2.0 of the gem, which I just pushed up.
Thanks for the contribution!

Reply to this email directly or view it on GitHub:
https://github.com/jwilger/github-v3-api/pull/6#issuecomment-3010934

--
Ben Jackson
<EMAIL_ADDRESS>@benjaminjackson
http://90wpm.com/about
http://www.linkedin.com/pub/benjamin-jackson/1/240/a38


build: change product name from ZapDesktop to Zap

Description:
Change product name from ZapDesktop to Zap.
This updates everything except for the IndexedDb database name, which would be relatively complex and potentially problematic to rename and not worth the hassle IMO.
Motivation and Context:
Fix #1554
How Has This Been Tested?
Manually
Checklist:

[x] My code follows the code style of this project.
[x] I have reviewed and updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes where needed.
[ ] All new and existing tests passed.
[x] My commits have been squashed into a concise set of changes.

Coverage remained the same at 19.716% when pulling b0b740e17eb32362c75041e82ae55e0b387797e7 on mrfelton:build/app-name into 72b117edfd2bb738f07246a631965d3f24e2531b on LN-Zap:master.


Add browser-based end-to-end tests

New feature description
This adds a top-level export acp_lowlevel_preview that reckless developers people can import to get all the ACP functions, and an end-to-end test running in the browser (because they need to be authenticated) that uses them to create a Policy Resource, make it publicly accessible, and delete it again.
Still to do: use the correct ESS credentials, and fix the Windows test (it's using the wrong slash when switching directories...). But it can already be reviewed.
Also, the build is failing due to inrupt.net having issues, but you can see a working run here: https://github.com/inrupt/solid-client-js/runs/1316068235?check_suite_focus=true
See /src/e2e-browser/README.md for a general description of the setup.
Checklist

[x] All acceptance criteria are met.
[x] Relevant documentation, if any, has been written/updated.
[x] The changelog has been updated, if applicable.
[x] New functions/types have been exported in index.ts, if applicable.
[x] Commits in this PR are minimal and have descriptive commit messages.

The e2e tests now also run in Windows (against Chrome, Firefox and Edge) and MacOS (Safari only, with a somewhat cumbersome workaround - but at least we have Safari).


Services with sidecar cannot talk to services without sidecar when mTLS is globally turned on

Before customer installing istio sidecar, we have a svc A talking to svc B via http.
However, if we install sidecar for svc A, and mTLS is turned on globally, i.e., by running istio-auth.yaml in this page: https://istio.io/docs/setup/kubernetes/quick-start.html#installation-steps. Then svc A cannot talk to svc B any more. Because svc A always sends https traffic while svc B expects http traffic.
The idea is when pilot constructs CDS, if mTLS is turned on globally, we always add ssl_context (v1 api)/tls_context (v2 api) to it, no matter whether the upstream service has sidecar or not. This is a bug when upstream service does not have sidecar.

Thanks Tao, this sounds reasonable.  What is the rough time frame for this?

I am talking with Networking team for support, i.e., we need to know whether the upstream has sidecar.

After chatting with @louiscryan , it seems this is pretty expensive to detect whether the other side has sidecar. He will add more context in this issue.

we're going to have this issue with mesh expansion and other situations where endpoints are registered but we don't know or control how they are registered. I'm wary of depending on Envoy to effectively register an endpoint for a service in the near term. This issue is exacerbated by folks directly creating ServiceEntry resources.
DestinationRule controls how a service is connected to at this layer and AuthorizationPolicy dictates what a service endpoint implements. The flag mentioned above controls global enablement of mTLS and is risky to use in existing clusters where the operator hasn't validated proper migration, i.e its really only safe to use for new clusters.
For folks incrementally rolling out mTLS they should use a combination of AuthorizationPolicy and DestRule to control the migration. AuthPolicy can declare that an endpoint accepts mTLS or Plaintext, then DestRule is updated to require mTLS when reaching that endpoint, then AuthPolicy can be updated to require mTLS once the metrics show that there is no Plaintext traffic.

@louiscryan just to make sure we are on the same page... Let's say I have a simple guestbook app that has 2 services (A and B).  I'm moving A to the istio mesh and B continues to run in the same k8s cluster.  A (with envoy side car) calls B (no envoy).  Can you apply AuthorizationPolicy for service B effectively when service B doesn't have side car?    Or are you suggesting using the new Auth policy to disable mTLS for the namespace X that A is deployed to?   And once service B is also moved to the mesh with service A, then user can 1)  test require mTLS among A and B using dest rule 2) enable mTLS for namespace X using Auth policy.
Essentially, user needs to turn off the mTLS globally for the mesh prior to 0.8... with 0.8, this is nicer because users can turn it on or off per namespace via the new AuthPolicy.

@incfly @diemtvu

For B (no envoy) we can't apply authorization policy or MTLS. What we can
do is set a DestinationPolicy
that configures 'no tls' for connections from A to B.
In 0.8 user should be able to turn on/off MTLS explicitly via
DestinationPolicy, per service (envoy-cluster or hostname).
The default helm templates are set with global MTLS off - we still ship the
'demo' istio-auth.yaml, but we expect
most users will use 'helm template' or 'helm' instead, so at install or
update they can set the global MTLS policy,
and to use DestinationPolicy to fine tune it.
On Mon, Apr 30, 2018 at 6:33 PM, Lin Sun<EMAIL_ADDRESS>wrote:

@louiscryan https://github.com/louiscryan just to make sure we are on
the same page... Let's say I have a simple guestbook app that has 2
services (A and B). I'm moving A to the istio mesh and B continues to run
in the same k8s cluster. A (with envoy side car) calls B (no envoy). Can
you apply AuthorizationPolicy for service B effectively when service B
doesn't have side car? Or are you suggesting using the new Auth policy to
disable mTLS for the namespace X that A is deployed to? And once service B
is also moved to the mesh with service A, then user can 1) test require
mTLS among A and B using dest rule 2) enable mTLS for namespace X using
Auth policy.
Essentially, user needs to turn off the mTLS globally for the mesh prior
to 0.8... with 0.8, this is nicer because users can turn it on or off per
namespace via the new AuthPolicy.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/5296#issuecomment-385577408, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAFI6iKv-BXwG3vUn19odsZTi-fyz4iFks5tt7t_gaJpZM4Ts63E
.

There is another strange interaction here - if they are migrating from 0.7
to 0.8/alpha3.
In this case I'm not sure what should happen - in 0.7 we used some service
annotations
to disable mtls for some services. I assume users will keep them while they
upgrade to 0.8,
and create equivalent DestinationPolicy.
On Tue, May 1, 2018 at 4:31 PM, Costin Manolache<EMAIL_ADDRESS>wrote:

For B (no envoy) we can't apply authorization policy or MTLS. What we can
do is set a DestinationPolicy
that configures 'no tls' for connections from A to B.
In 0.8 user should be able to turn on/off MTLS explicitly via
DestinationPolicy, per service (envoy-cluster or hostname).
The default helm templates are set with global MTLS off - we still ship
the 'demo' istio-auth.yaml, but we expect
most users will use 'helm template' or 'helm' instead, so at install or
update they can set the global MTLS policy,
and to use DestinationPolicy to fine tune it.
On Mon, Apr 30, 2018 at 6:33 PM, Lin Sun<EMAIL_ADDRESS>wrote:

@louiscryan https://github.com/louiscryan just to make sure we are on
the same page... Let's say I have a simple guestbook app that has 2
services (A and B). I'm moving A to the istio mesh and B continues to run
in the same k8s cluster. A (with envoy side car) calls B (no envoy). Can
you apply AuthorizationPolicy for service B effectively when service B
doesn't have side car? Or are you suggesting using the new Auth policy to
disable mTLS for the namespace X that A is deployed to? And once service B
is also moved to the mesh with service A, then user can 1) test require
mTLS among A and B using dest rule 2) enable mTLS for namespace X using
Auth policy.
Essentially, user needs to turn off the mTLS globally for the mesh prior
to 0.8... with 0.8, this is nicer because users can turn it on or off per
namespace via the new AuthPolicy.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/5296#issuecomment-385577408, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAFI6iKv-BXwG3vUn19odsZTi-fyz4iFks5tt7t_gaJpZM4Ts63E
.

@costinm @wattli would the service annotation in 0.7 continue to work in 0.8?   It would not be obvious to user to change the service annotation to destinationpolicy as service annotation is at the service yaml today in 0.7. cc @esnible


[#3903] Add topic validation, forbid sending message to system topic

Make sure set the target branch to develop
What is the purpose of the change
#3903
Brief changelog
XX
Verifying this change
XXXX
Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

[x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Coverage increased (+0.02%) to 51.58% when pulling e5c21b7bf18e7a3d927ff077825e187b81130327 on sunxi92:fix_topic_validatation into 7281b5d9a0db15e5ec1ab9e3444091e7022f65fb on apache:develop.

Coverage increased (+0.02%) to 51.58% when pulling e5c21b7bf18e7a3d927ff077825e187b81130327 on sunxi92:fix_topic_validatation into 7281b5d9a0db15e5ec1ab9e3444091e7022f65fb on apache:develop.

This may affect the sending of trace messages.
https://github.com/apache/rocketmq/blob/7281b5d9a0db15e5ec1ab9e3444091e7022f65fb/client/src/main/java/org/apache/rocketmq/client/trace/AsyncTraceDispatcher.java#L386

Codecov Report

Merging #3904 (58647c0) into develop (799d412) will decrease coverage by 0.00%.
The diff coverage is 100.00%.

@@              Coverage Diff              @@
##             develop    #3904      +/-   ##
=============================================
- Coverage      47.45%   47.44%   -0.01%
+ Complexity      4922     4919       -3
=============================================
  Files            633      633
  Lines          42498    42520      +22
  Branches        5579     5582       +3
=============================================
+ Hits           20166    20173       +7
- Misses         19826    19839      +13
- Partials        2506     2508       +2

Impacted Files
Coverage Δ

...g/apache/rocketmq/common/topic/TopicValidator.java
97.05% <100.00%> (+0.23%)
:arrow_up:

...rocketmq/broker/filtersrv/FilterServerManager.java
20.00% <0.00%> (-14.29%)
:arrow_down:

...org/apache/rocketmq/common/stats/StatsItemSet.java
43.28% <0.00%> (-7.47%)
:arrow_down:

...ache/rocketmq/common/stats/MomentStatsItemSet.java
39.13% <0.00%> (-4.35%)
:arrow_down:

...he/rocketmq/client/impl/consumer/ProcessQueue.java
61.00% <0.00%> (-0.92%)
:arrow_down:

...he/rocketmq/tools/admin/DefaultMQAdminExtImpl.java
39.83% <0.00%> (+0.12%)
:arrow_up:

...mq/client/impl/producer/DefaultMQProducerImpl.java
45.10% <0.00%> (+0.24%)
:arrow_up:

.../apache/rocketmq/logging/inner/LoggingBuilder.java
64.71% <0.00%> (+0.31%)
:arrow_up:

...apache/rocketmq/tools/admin/DefaultMQAdminExt.java
41.40% <0.00%> (+0.46%)
:arrow_up:

...ent/impl/consumer/DefaultLitePullConsumerImpl.java
68.27% <0.00%> (+0.51%)
:arrow_up:

... and 4 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 799d412...58647c0. Read the comment docs.