Binding fallback not working on latest 0.9 preview 3

Hi,
I have a TranslateExtension that I use in Avalonia, and WPF to translate some stuff, the code is pretty simple.
    public class TranslateExtension : MarkupExtension
    {
        public TranslateExtension(string key)
        {
            this.Key = key;
        }

        public string Key { get; set; }

        public string FallBack { get; set; }

        public string Context { get; set; }

        public override object ProvideValue(IServiceProvider serviceProvider)
        {
            ....

            var binding = new BindingExtension($"[{keyToUse}]")
            {
                Mode = BindingMode.OneWay,
                Source = Translator.Instance,
                FallbackValue = fallback,
            };

            return binding.ProvideValue(serviceProvider);
        }
    }

Bascialy, when the is no translation for a specific key (returns null), a fallback value is used instead.
This extension works fine with WPF, and Avalonia 0.8.3.
The problem occurs with the latest version 0.9 preview 3, where it seems that it's ignoring the FallbackValue
Repro project: https://github.com/braca/avalonia-binding-fallback-bug
You can load my repro project, with 0.8.3 it will work perfectly, if you update to the latest 0.9 preview 3, the fallback value won't be used.
Note: When you update to the latest preview, comment this using Portable.Xaml.Markup; in TranslateExtensions.cs

@braca I've not had chance to look into this properly, but does it work if you return a Binding rather than a BindingExtension from ProvideValue?
My guess is that Portable.Xaml supported markup extensions returning markup extensions recursively, whereas our XAML compiler doesnt. In fact I'm not even sure that recursive binding extensions should work, it might have just been a "hidden" feature of Portable.Xaml.

Hi @grokys,
I've tried to replace
            var binding = new BindingExtension($"[{keyToUse}]")
            {
                Mode = BindingMode.OneWay,
                Source = Translator.Instance,
                FallbackValue = fallback,
            };

            return binding.ProvideValue(serviceProvider);

with
            var binding = new Binding($"[{keyToUse}]", BindingMode.OneWay)
            {
                Source = Translator.Instance,
                FallbackValue = fallback
            };

            return binding;

but the end result was the same

@grokys I think this is not a bug after all, my bad. In WPF the behaviour is the same, I thought it wasn't but my WPF code had a small difference, and that makes all the difference.
In WPF I'm using TargetNullValue alongside with FallbackValue.
Removing the TargetNullValue, WPF behaves the same way Avalonia 0.9.
Our translator returns null when there is no translation available for the key. null is a valid 'value' for string, so the correct behaviour seems to be, to use null, instead of the fallbackvalue.
So, I believe that the bug was on 0.8.x where it was behaving differently from WPF :)
Feel free to close it

Thanks for letting us know @braca. We're intending to add TargetNullValue soon anyway - here's the issue: https://github.com/AvaloniaUI/Avalonia/issues/2814


bug(MatFormField):MatFormField suffix and prefix are NOT aligned with floating placeholder - even on DEMO PAGE

Reproduction
got to https://material.angular.io/components/form-field/overview#prefix--suffix
Prefix and suffix of second example is not aligned with floating placeholder (when it is not floating)
Expected Behavior
Everything to be alligned
Actual Behavior

Environment
Angular demo page for 11.1.1

I think that in general the new form field appearances aren't really made for text-based prefixes. We should either remove those examples or switch them to icons.

Thanks @annieyw for fixing the example! I'm leaving this bug open because we should be able to do more to improve this experience in the MDC version of the form-field. In that version we actually differentiate between text and icon prefix/suffixes so we can treat them differently. I think the right thing to do for the MDC version is hide the text prefix/suffix when the label is not floating (this is what MDC does in their own demos)


New mod configuration

The Mimicry mod was added to the configurations list.  Additionally, scaling for vanilla clay was changed from base to sea level (to ensure scaling remains locked at 64).

Base scaling is locked at 64, sealevel is via the average ground level.

Point.  Either way, clay should always spawn at sea level, given that it is technically wet clay. ;)


Add powerline font support

Hey there, first of all I want to say thank you very much for this awesome plugin. It is in my opinion definitely the best tabs/buffer handling plugin out there :smile:. The only feature that was missing for me personally was support for powerline font, which I have tried to add. My changes add the following variables:

g:wintabs_use_powerline
This sets whether powerline fonts are used at all, if this is set to 0 nothing changes and the plugin will behave as it always has.

g:wintabs_ui_powerline_sep_active_buffer_left
Defines the seperator symbol on the left side of the currently active buffer.

g:wintabs_ui_powerline_sep_active_buffer_right
Defines the seperator symbol on the right side of the currently active buffer.

g:wintabs_ui_powerline_sep_inbetween_buffer
Defines the seperator symbol that will be shown inbetween buffers.

g:wintabs_ui_powerline_sep_rightmost_buffer
Defines the seperator symbol that will be at the far right of the buffer list.

g:wintabs_ui_powerline_sep_active_tab_left
Defines the seperator symbol on the left of the currently active tab.

g:wintabs_ui_powerline_sep_active_tab_right
Defines the seperator symbol on the left of the currently active tab.

g:wintabs_ui_powerline_sep_inbetween_tab
Defines the seperator symbol that will be shown inbetween tabs.

g:wintabs_ui_powerline_sep_leftmost_tab
Defines the seperator symbol that will be at the far left of the tabs list.

g:wintabs_ui_active_buffer_higroup
The highlight group for the currently active buffer.
(e.g. : g:wintabs_ui_active_buffer_higroup='WintabsActiveBuffer' with
hi! WintabsActiveBuffer cterm=NONE ctermbg=1 ctermfg=8 guibg=#009933 guifg=#000000)

g:wintabs_ui_active_buffer_changed_higroup
The highlight group for the currently active buffer when there are unsaved changes.

12.g:wintabs_ui_inactive_buffer_higroup
The highlight group for currently inactive buffers.
(e.g. g:wintabs_ui_inactive_buffer_higroup='WintabsInactiveBuffer' with
let s:linenr_bg_color = synIDattr(synIDtrans(hlID('LineNr')), 'bg', "gui")
let s:linenr_fg_color = synIDattr(synIDtrans(hlID('LineNr')), 'fg', "gui")
execute 'hi! WintabsInactiveBuffer cterm=NONE ctermbg=1 ctermfg=8 guibg='.s:linenr_bg_color.' guifg='.s:linenr_fg_color
Here is my current setup:
let g:wintabs_use_powerline = 1
let g:wintabs_ui_powerline_sep_active_buffer_left = "\ue0b4"
let g:wintabs_ui_powerline_sep_active_buffer_right = "\ue0b4"
let g:wintabs_ui_powerline_sep_inbetween_buffer = "\ue0b5"
let g:wintabs_ui_powerline_sep_rightmost_buffer = "\ue0b4"
let g:wintabs_ui_active_buffer_higroup = "WintabsActiveBuffer"
let g:wintabs_ui_active_buffer_changed_higroup = "WintabsActiveBufferChanged"
let g:wintabs_ui_inactive_buffer_higroup = "WintabsInactiveBuffer"
let g:wintabs_ui_active_tab_higroup = "WintabsActiveTab"
let g:wintabs_ui_inactive_tab_higroup = "WintabsInactiveTab"
let g:wintabs_ui_show_vimtab_name = 2
colorscheme solarized (its important that the higroups are declared after this)
let s:linenr_bg_color = synIDattr(synIDtrans(hlID('LineNr')), 'bg', "gui")
let s:linenr_fg_color = synIDattr(synIDtrans(hlID('LineNr')), 'fg', "gui")
execute 'hi! WintabsInactiveBuffer cterm=NONE ctermbg=1 ctermfg=8 guibg='.s:linenr_bg_color.' guifg='.s:linenr_fg_color
hi! WintabsActiveBuffer cterm=NONE ctermbg=1 ctermfg=8 guibg=#009933 guifg=#000000
hi! WintabsActiveBufferChanged cterm=NONE ctermbg=1 ctermfg=8 guibg=#f2b81e guifg=#000000
hi! WintabsActiveTab cterm=NONE ctermbg=1 ctermfg=8 guibg=#FFFFFF guifg=#000000
hi! WintabsInactiveTab cterm=NONE ctermbg=1 ctermfg=8 guibg=#073642 guifg=#586e75
Which ends up to look like this for an unmodified buffer:

And this for a modified buffer:

A different possible look:

There are a couple of problems still:

The seperators break when .vimrc is reloaded from within vim, a restart fixes this, but this should definitly be fixed
I haven't been able to get the truncation of the bufferline to work yet
Doesn't work with the 'taboo' plugin
Haven't implemented it for statusline option yet

I guess its not really in a mergable state right now but if you are interested in this feature I would try to fix the problems that still exist and add my changes to the docs. Just let me know what you think.

Hey @kafendt,
Thank you for the PR. This looks like a really good addition and I would certainly like to have it in wintabs. Unfortunately like you said, currently this isn't in a mergable state. When I wrote wintabs, powerline/airline support was on my roadmap, but the huge complexity it brings to the tabs layout made me drop it. The main challenges for supporting this feature are:

the layout calculation in wintabs counts string length literally and special cases highlight groups. This doesn't work with any multi-byte unicode characters or other control code (like mouse handler in neovim)
the current layout solver is a very fragile and naive one, it's mostly correct (can handle most edges cases of truncation, overflow, underflow, re-position, re-size) but very hard to extend
to support this use case (string display length != byte count), a rewrite of the layout solver (or rather, writing a real solver) is likely unavoidable

Currently I don't have short term plans to add multi-byte character support to wintabs, but I may do it whenever I find opportunity. If you want to continue to evolve this PR, I'd suggest tackling another issue first: to allow separator or tab name to be multi-byte unicode. It's more clear how to test the correctness of that issue (total length of tabs is calculated correctly), and it's trivial to extend it to support powerline once its correctness is guaranteed.

Hey sorry for the late reply, I am pretty busy at the moment.
I agree with you, I mainly created the pull request to see whether there was interest in the feature at all. Now that I know there is I'll try to implement what you mentioned. It might take me a while though because I am currently still busy with a few other things, I will get back to you as soon as I am working on it again!
Thanks @zefei !

Hey @kafendt,
I did find opportunity to work on this issue lately, and I rewrote the renderer and layout functions to support multibyte characters. With the new renderer API (g:wintabs_renderers), your changes could be easily adopted to render powerline characters correctly.
I plan to move powerline support or other renderer features into separate plugins, so that the core wintabs options are not too many. Do you want to make your repo vim-wintabs-powerline standalone and containing only renderer functions? I can do that as well since I do plan to revamp wintabs a bit next month (will include your code, neovim mouse support, a few more utility commands).

Hey there,
thats awesome I'd be happy to implement the changes. So, as I take it you want to have plugins to your plugin, right? My repo would then only contain functions that extend the base vim-wintabs, is that what you're going for? I could probably work on this again within the next month. If you'd prefer to keep all elements under one roof (your github account) that'd be fine by me too. Just let me know you plans :smiley:.

Hey @kafendt,
Yeah that's what I meant. I don't really need all repos under this account, but I'll probably still create another repo here, since I do want to make sure it reflects some basic designs of wintabs - having simple defaults that work with default highlight groups such as Tabline, TablineSel, etc. And leave further customizations to pull requests.
If I don't have time to do that within the next month, you can surely create the repo, and I'll change the doc and README to link to that.

@kafendt,
I've pushed a v0 for powerline font support in this repo: https://github.com/zefei/vim-wintabs-powerline. I haven't got enough time to put in docs or fully test it, but it should be functional enough. Let me know if you have any suggestions. Thanks!

This seems like a great feature!

This feature is now fully supported in vim-wintabs-powerline, so closing this PR. Thank you @kafendt for the work you did here!


Make the testpmd resources templates + some fixes.

Turn the Openshift resources - SriovNetwork, SriovNetworkNodePolicy and VM - to parameterized templates rather than hard-coded resources.
In addition - reduce user manual involvement, e.g. add the script for changing NIC driver to the image, and run the script as part of VM's cloud-init.

@ormergi As for the comment about modifying the README, and explain how to reuse the common parameters between the templates - honestly, I think it's redundant. If the user has enough experience in Kubernetes to allow him to use templates, then he would probably know how to reuse the parameters from the CLI.

The README should include that huge pages need to be enabled on the nodes

Regarding the comments to handle hugepages in the VM - currently it is still not possible, until hugepages is configured on the BM cluster nodes (https://issues.redhat.com/browse/CNV-16709).

LGTM


Http Status 500 index out of bounds in Generics.hs

An 500 Http Status occurs, when calling a function with an invalid JSON String. (Binary Ubuntu 64 bit v<IP_ADDRESS>)
create or replace function d(in int) returns integer as
$$ select $1 * 2; $$ immutable language sql ;

curl 'http://localhost:3000/rpc/d' -H "Content-Type: application/json" -X POST -d '2'

causes an 500 status code with "Something went wrong" in the http body
postgrest output

./Data/Vector/Generic.hs:235 ((!)): index out of bounds (0,0)

PostgREST currently requires named arguments for calling RPC functions. For instance
create or replace function d(in foo int) returns integer as
$$ select $1 * 2; $$ immutable language sql ;

would be called with
{ "foo": 2 }

I'll improve the error message in the non-JSON arg post to document this.

Moving this issue to the new postgrest-docs repo.


Only set long expiration for files in _app/immutable directory

Recently SvelteKit introduced the _app/immutable directory in the buildout. This directory contains all files that should be cached with a long TTL. Serving the whole _app/ directory with a long TTL impacts the SvelteKit update check via the updated store from $app/stores (see: https://kit.svelte.dev/docs/modules#$app-stores-updated) which relies on being able to fetch the current app version from _app/version.json.
This PR splits the handlers for _app/ and _app/immutable and only sets the 30d expiration on the _app/immutable handler. Other assets in _app/ are then served with the default expiration which can further be customized by setting default_expiration in the top-level app.yaml.
Similar changes in the default adapters were introduced in https://github.com/sveltejs/kit/pull/5051

With #28 merged, can you try and rebase / merge to master. Also, integration test needs to be updated to contain the new expected yaml in /tests/expected_app.yaml. Try running npm run test:integration

HI @HalfdanJ and sorry I completely missed the notifications on the PRs. I see you already merged the other one. I'll rebase this one and update the integration tests.

Thanks @sfriedel !


Audio doesn't stop when returning to state without id

Translation: Going back to /soundboard doesn't stop audio.

This was fixed in d7d419aae1bdf116e153915e5b3e5c1d61339f4e.


Update ParsedownExtraPlugin.php

Fixed an issue where this caused the prefix "language" to be added twice (with parsedown 1.8 beta 7)

The option was added to automatically append language- prefix to code block class name without dot prefix. The correct fix would be to check whether a class name already prefixed with language- from the initial state. If that’s the case, do not add prefix.

If that’s is your preference, (to add language- prefix manually from the markdown source, you can create the same effect without modifying the core this way:
$Parsedown = new ParsedownExtraPlugin;
$Parsedown->blockCodeClassFormat = '%s';

echo $Parsedown->text($content);


Add Feature Request and Community Discussion to Left nav

Fixes #1245
Any feedback on the icons? @lstrano-broad @bradtaylor @jeromechadel

icons look good - thx!

I’m ok with the icons as well.
Once you are in the Terra Support website, I don’t see a way of going back to Terra.
Could the Terra logo serve that purpose?
Thank you,
Jerome

On Mar 4, 2019, at 5:25 PM, Kate Voss<EMAIL_ADDRESS>wrote:
Fixes #1245 https://github.com/DataBiosphere/saturn-ui/issues/1245
Any feedback on the icons? @lstrano-broad https://github.com/lstrano-broad @bradtaylor https://github.com/bradtaylor @jeromechadel https://github.com/jeromechadel
https://user-images.githubusercontent.com/2395211/53766999-70d2d480-3ea2-11e9-96b9-4a5091eeed33.png
You can view, comment on, or merge this pull request online at:
https://github.com/DataBiosphere/saturn-ui/pull/1253 https://github.com/DataBiosphere/saturn-ui/pull/1253
Commit Summary
Add Feature Request and Community Discussion to Left nav
File Changes
M src/components/TopBar.js https://github.com/DataBiosphere/saturn-ui/pull/1253/files#diff-0 (42)
Patch Links:
https://github.com/DataBiosphere/saturn-ui/pull/1253.patch https://github.com/DataBiosphere/saturn-ui/pull/1253.patch
https://github.com/DataBiosphere/saturn-ui/pull/1253.diff https://github.com/DataBiosphere/saturn-ui/pull/1253.diff
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/DataBiosphere/saturn-ui/pull/1253, or mute the thread https://github.com/notifications/unsubscribe-auth/AtZ8bvxxsDJguIWJkuHDQvNvm3auheWcks5vTZ1PgaJpZM4bdVbe.

That's a good idea @jeromechadel, @tmm211 do you know if it's possible to add a link from the Terra Support site (on Zendesk) back to Terra?
Also, note that each of the support links, "Learn about Terra", "Request a feature", and "Community discussion", open in a new tab in the browser so the user is not actually directed off of Terra. They have it open in the prior browser tab.

Yes, we can do that...where makes sense?


Rewrite Function for Scheduling Notifications to Avoid Network Discovery

Title
Rewrite Function for Scheduling Notifications to Avoid Network Discovery
Description
The current function for scheduling notifications uses the libs.androidx.work.runtime.ktx library (version work-runtime-2.9.0), which relies on network discovery. We want to avoid using network discovery due to its associated permissions and potential privacy concerns. We need to find an alternative approach to schedule notifications without requiring these additional permissions.
Requirements

Remove Dependency: Identify and remove the dependency on network discovery within the scheduling function.
Alternative Solution: Explore and implement a different method for scheduling notifications that does not require network-related permissions.
Permissions: Ensure that the new implementation does not introduce unnecessary permissions or privacy issues.

Steps to Implement

Review Current Implementation: Examine the existing notification scheduling function to understand its reliance on libs.androidx.work.runtime.ktx and network discovery.
Explore Alternatives: Research and evaluate alternative libraries or methods for scheduling notifications that align with our requirements.
Implement New Solution: Replace the current implementation with the chosen alternative method for scheduling notifications.
Test Functionality: Thoroughly test the new implementation to ensure it works as expected and does not require network discovery or additional permissions.
Update Documentation: Document the new approach and update any relevant sections in the project documentation.

Acceptance Criteria

The notification scheduling function no longer relies on network discovery.
The new implementation does not require additional or unnecessary permissions.
The function successfully schedules notifications as intended without any issues.

Additional Notes

Ensure that the new method complies with best practices for Android notification scheduling.
Provide feedback or additional suggestions for the alternative approaches and their implementation.

Please review and provide input on the proposed changes and approach.
(Related to #70)

Look into this and see if it can be used;
https://developer.android.com/develop/background-work/services/alarms/schedule


Replace strlen with sizeof for kconfig string

Summary
improve the speed and reduce the code size a little bit
Impact
code refactor
Testing
ci

I think it will not bring a speed and size impact. Maybe only with O0. I've experimented with similar things in the past and compiler computes all possible things at compile time so strlen call will not be inserted, but the computed value will be used.


remove spaces and put tabs to run sideload bash

This was a required change so i can run the "make sideload" on linux mint with bash terminal

@mcphee11 Thanks for the contribution! Similar changes were just made in PR #617. If these changes work for you, we can close this PR

I did a fresh git pull with these new changes and its now working fine with the "make sideload" I did email John about this so I assume it was updated before my push. Cheers


[VL] Fallback scan if root path is not supported by registered file systems

What changes were proposed in this pull request?
Fallback scan if root path is not supported by registered file systems
Fixes: #6620
How was this patch tested?
UT.

cc @PHILO-HE , thanks.

@wForget, could you take a look if you have time?

@zhli1142015 Thanks for your work, as comment in https://github.com/apache/incubator-gluten/pull/4086#issuecomment-1871937485  suggested putting the validation into SubstraitToVeloxPlanValidator, I also tried it in the original PR, can you confirm which way is better?

Yes. There are lots of change sinse your PR. setSplitInfos method is removed from the SubstraitContext. If we want to still follow that way, we need to bing it back or add separate property for this.
And getSplitInfos is an expensive call, we should avoid to use it in validation. Instead we retrieve the first root path for validation here.
And looks all file related validation is kept in the method supportFileFormatRead, file format, schema, etc. So we put the check here also.
Last, FakeParentPathFileSystem doesn't work as expected in my local UT runs, mockfs:// is not supported by local file system. so I think a separate JNI wrapper API is needd for UT.
Hee are the differences in my mind, please le me know is this makes sense to you, @PHILO-HE  and @wForget , thanks.

Thanks, overall LGTM.

@zhli1142015, could you respond to @wForget's comments?

Just updated, thanks.


how we scrape log based metrics

Hi team ,
I try to scrape custom log based metrics and exporter doesn't do anything..

No scraping for below args

Args
--monitoring.metrics-type-prefixes=logging.googleapis.com/user/*
--monitoring.metrics-type-prefixes=logging.googleapis.com/user/my-custom-metric

level=info ts=2022-01-05T19:47:53.425Z caller=stackdriver_exporter.go:164 msg="Starting stackdriver_exporter" version="(version=0.11.0, branch=HEAD, revision=aafa2f0e851f2e07772a388dbf4590484513a19f)"
3
level=info ts=2022-01-05T19:47:53.425Z caller=stackdriver_exporter.go:165 msg="Build context" build_context="(go=go1.15.1, user=root@67413d69d3db, date=20200902-14:39:30)"
2
level=info ts=2022-01-05T19:47:53.425Z caller=stackdriver_exporter.go:166 msg="Using Google Cloud Project ID" projectID=<ProjectID >
1
level=info ts=2022-01-05T19:47:53.425Z caller=stackdriver_exporter.go:188 msg="Listening on" address=:9255

Scraper  pods crashes with duplicate metric name error for below args

Args
--monitoring.metrics-type-prefixes=logging.googleapis.com
--monitoring.metrics-type-prefixes=logging.googleapis.com/user

panic: duplicate label names goroutine 128 [running]: github.com/prometheus/client_golang/prometheus.MustNewConstHistogram(...) /app/vendor/github.com/prometheus/client_golang/prometheus/histogram.go:620 github.com/prometheus-community/stackdriver_exporter/collectors.(*TimeSeriesMetrics).newConstHistogram(0xc00050fa08, 0xc0002e8000, 0x4d, 0x1a3388e8, 0xed967ec17, 0x0, 0xc000686100, 0xb, 0x10, 0xc0001e9440, ...) /app/collectors/monitoring_metrics.go:102 +0x228 github.com/prometheus-community/stackdriver_exporter/collectors.(*TimeSeriesMetrics).completeHistogramMetrics(0xc00050fa08) /app/collectors/monitoring_metrics.go:199 +0x1f0 github.com/prometheus-community/stackdriver_exporter/collectors.(*TimeSeriesMetrics).Complete(0xc00050fa08) /app/collectors/monitoring_metrics.go:162 +0x39 github.com/prometheus-community/stackdriver_exporter/collectors.(*MonitoringCollector).reportTimeSeriesMetrics(0xc00027e300, 0xc0001e8bd0, 0xc000770800, 0xc0000b78c0, 0xc0001e8bd0, 0x0) /app/collectors/monitoring_collector.go:404 +0x1465 github.com/prometheus-community/stackdriver_exporter/collectors.(*MonitoringCollector).reportMonitoringMetrics.func1.1(0xc0004aea50, 0xc00027e300, 0x1a338c07, 0xed967eb63, 0x0, 0x1a338c07, 0xed967ec8f, 0x0, 0xc000731a40, 0xc000770800, ...) /app/collectors/monitoring_collector.go:257 +0x6b6 created by github.com/prometheus-community/stackdriver_exporter/collectors.(*MonitoringCollector).reportMonitoringMetrics.func1 /app/collectors/monitoring_collector.go:231 +0x3f5

Can someone help on this one.. Thanks

Any moderators up here ??

For me it looked like they end up under stackdriver_k_8_s_container_logging_googleapis_com_user_???

@Coder63 did you figure it out ?

For anyone that stumbles onto this, the method that I used was to use a metrics-type-prefix of logging.googleapis.com/user/ which collected all of the log-based metrics defined within the project.
The metric name is based on the underlying resource associated with the log.  For example a log-based metric named foo-bar against logs from a cloud function resulted in a prom metric named stackdriver_cloud_function_logging_googleapis_com_user_foo_bar


Update blocking overlay for css only solution

If PR merged, blocking overlay will be updated of css solution.
The original solution worked but had opacity transition to non-blocking overlay as well. i.e.: if no blocking state on server happened in 2s+, user would have experienced the same - correct transition.
This PR separates classes and prevents transition mixing.
Continuation of #17 and #236

@mturoci - It would be good if you can review and try this out so that we can close it.


E621 no results on 7.2.1(x64)

im trying to download from e621 but i keep getting no results anyone know how to fix this?

sorry i just notice the pinned tag


Only support 'user with login' in dialog (#22175)

Part of changes to finish user management for March tracked here https://github.com/microsoft/azuredatastudio/issues/22173.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
2 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.003%) to 41.936%

Files with Coverage Reduction
New Missed Lines
%

extensions/notebook/src/dialog/configurePython/configurePathPage.ts
1
57.02%

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

Totals

Change from base Build<PHONE_NUMBER>:
-0.003%

Covered Lines:
28803

Relevant Lines:
63772

💛  - Coveralls


Android Keystore entry is deleted when app is uninstalled?

Hi
Thanks for the plugin. I have been using it successfully on iOS for 6 months. Now trying to release an Android version and I find the behaviour is different.  I am new to Android and tried research on this, but it may be a dumb question. Should the key-value be retained after the app has been uninstalled?
Use-case:

Install App
Read key. If null then write key value.
Uninstall app.
Read key.   On iOS I get the saved value returned. On Android it returns null.

So should the key-value be retained after the app has been uninstalled?

Ok so I have delved further into this and see that Android Keystore does get wiped on app deletion.
Thus the plugin does exhibit different behaviour on iOS and Android so maybe that should be highlighted in the help or readme.
Having said that... does anyone know how to securely persist a value across delete & reinstall?

@systemcode
So what is your solution to store a value which persists after uninstall

On ios this plugin is ok. On Android, I have failed to find a good method so had to rework my app.

same problem here, at remove app on Android i need go to settings -> apps ->  -> remove storage & cache, and again works.
@systemcode  What you did it? 😮

@systemcode  What you did it? 😮

No I didn't

I added a try catch when exception is triggered by uninstall and re-install application. if exception occurs so I instantiate the lib and remove all content from secure-storage, until issue is handled (anyway I don't believe that occurs)

This is expected behavior on Android.

Having said that... does anyone know how to securely persist a value across delete & reinstall?

You should encrypt your data and store it on the filesystem. However for now this is out of the scope of this package.

@juliansteenbakker

You should encrypt your data and store it on the filesystem

Could you please share a link about how we can do this


Don't require enter press to run search

I would rather keep all workflows that I make (moving forward) tied to this repo for consolidation purposes. If you could submit the PRs here, that would be lovely.

Alright, if that's specifically what you'd like then I have no objections, I'll submit a PR later today. I'm just fixing my fork right now. How's this look to you?

Next course of action for me is that i'd like to get icons

Alright, if that's specifically what you'd like then I have no objections, I'll submit a PR later today. I'm just fixing my fork right now. How's this look to you?

That looks fine.


Example Addition

I would like to add an example based on the Multi-commodity network flow problem by Cappanera & Frangioni. This example would help other users overcome the two-dimensional limitation of CVXPY and be able to port models built in CPLEX with minimal code changes.
Please check the example code here
Thank you.

That's great! Our format is to make Jupyter notebooks, where first you describe the problem mathematically, then you have code to solve an example. Out of curiosity, why does the problem benefit from more than 2D matrices? I've set up multi-commodity flow problems before with just normal linear algebra.

Thanks for the response. I will work on the notebook and send the link later. The benefit of the X-D (where X= 1,2, 3 ...) structure is to offer that flexibility as given in for instance IBM CPLEX which makes it easier to ead any model code. It makes use of the same complex indexing shown in the written math model. The model to be used in my example is the arc-flow type based on MNETGEN instances.

That's great! Our format is to make Jupyter notebooks, where first you describe the problem mathematically, then you have code to solve an example. Out of curiosity, why does the problem benefit from more than 2D matrices? I've set up multi-commodity flow problems before with just normal linear algebra.

Here is the link to the notebook that contains the example in the format you suggested.
link.
Please let me know if there are any issues. Thanks

This is quite unpythonic in some places.
Instead of all those repeated int() conversions, wouldn't it be better to do:
data = map(int,eachLine.split(" "))
? Also, the python lists should be numpy arrays, and are all those temp variables really needed?
K

From: Evans Sowah Okpoti<EMAIL_ADDRESS>Sent: 06 May 2020 15:32
To: cvxgrp/cvxpy<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: Re: [cvxgrp/cvxpy] Example Addition (#1015)
That's great! Our format is to make Jupyter notebooks, where first you describe the problem mathematically, then you have code to solve an example. Out of curiosity, why does the problem benefit from more than 2D matrices? I've set up multi-commodity flow problems before with just normal linear algebra.
Here is the linkhttps://github.com/okpoti2/CVXPYContributions/blob/master/MMCF.ipynb to the notebook that contains the example in the format you suggested.
Please let me know if there are any issues. Thanks
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/cvxgrp/cvxpy/issues/1015#issuecomment-624669149, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABHIQEM2BLBAOVWIKYPLBDTRQFYGFANCNFSM4MW5LL5Q.

Thanks for your comments. I have updated the file based on your suggestions. However, the use of the lists (and also the tem variables) is to build a kind of data structure that would allow ease modeling since the original input file as information scattered over with some lines made of int and float.

for eachLine in mcpFileData:
data = tuple(map(int, eachLine.split("      ")))
mutualCapacityPointer[data[0]] = data[1]
However, all this could probably be done much better with np.loadtxt().

From: Evans Sowah Okpoti<EMAIL_ADDRESS>Sent: 06 May 2020 16:42
To: cvxgrp/cvxpy<EMAIL_ADDRESS>Cc: Briggs,KM,Keith,TUD2 R<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [cvxgrp/cvxpy] Example Addition (#1015)
Thanks for your comments. I have updated the file based on your suggestions. However, the use of the lists (and also the tem variables) is to build a kind of data structure that would allow ease modeling since the original input file as information scattered over with some lines made of int and float.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/cvxgrp/cvxpy/issues/1015#issuecomment-624726406, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABHIQEKYOXIWUBXG6J2WXALRQGAPXANCNFSM4MW5LL5Q.

That was great info.

Read mutual capacity pointer file
mutualCapacityPointer = np.loadtxt(mutFile)
You don't need to open and close it.

From: Evans Sowah Okpoti<EMAIL_ADDRESS>Sent: 06 May 2020 17:05
To: cvxgrp/cvxpy<EMAIL_ADDRESS>Cc: Briggs,KM,Keith,TUD2 R<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [cvxgrp/cvxpy] Example Addition (#1015)
That was great info.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/cvxgrp/cvxpy/issues/1015#issuecomment-624739491, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABHIQEJGRISKEO6UKQKF7CDRQGDFFANCNFSM4MW5LL5Q.

Ok

Read mutual capacity pointer file mutualCapacityPointer = np.loadtxt(mutFile) You don't need to open and close it.
…
________________________________ From: Evans Sowah Okpoti<EMAIL_ADDRESS>Sent: 06 May 2020 17:05 To: cvxgrp/cvxpy<EMAIL_ADDRESS>Cc: Briggs,KM,Keith,TUD2 R<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [cvxgrp/cvxpy] Example Addition (#1015) That was great info. — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#1015 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABHIQEJGRISKEO6UKQKF7CDRQGDFFANCNFSM4MW5LL5Q.

@okpoti2 this looks pretty good! Could you start a pull request, and we'll help integrate it into the cvxpy examples?


move nix.System call inside featureflag.RemoveNixpkgs if-condition

Summary
I'm not yet entirely sure why, but #1245 led to some testscript error.
For now, I'm hiding the nix.System call inside the feature flag's if-condition
to get the testscripts status to green again on main.
How was it tested?
testscripts should pass

Current dependencies on/for this PR:

main

PR #1247   👈

This comment was auto-generated by Graphite.


dubbo 2.7.1  consumer side does not show the provider, but in provider side, consumer can be shown

What version of pinpoint are you using?
agent 2.0.1
collector 1.7.2
web 1.7.2
Describe your problem**
dubbo 2.7.1  consumer side does not show the provider, but in provider side, consumer can be shown
What have you done?
1.i saw consumer and provider agent log, but nothing found
2.i found that in the single request's server map ui, the request map can be shown normally
Screenshots
Service A ui(dubbo consumer):

consumer doesn't show the provider:

Serivce B ui(dubbo provider):
2.provider show the consumer:

3.in the Service A(consumer) single request Server Map ui, the request map and service b(provider) can be shown normally

I want the consumer side to show the provider side, what should I do?

Hello, @wangran123
Please check version compatibility
http://naver.github.io/pinpoint/2.0.1/main.html#upgrade-consideration

i updated all componets to 2.0.1, and it's work find. Thanks a lot


Connectionist Temporal Classification example

I found these lines in array_grad.py
# Edit Distance has no gradient (but can be used to eval seq2seq or CTC).
ops.NoGradient("EditDistance")

Is there any implementation of CTC cost function in tensorflow, or any example concern CTC ?

Thank you for inquiring.  We are working on an implementation.  It will be released if/when we are happy with its performance, API, and documentation.

Here's another request for a CTC layer / objective.  I'm working on speech modeling, and CTC is pretty much essential to this.

Here here, I'm working on speech modeling too. A CTC implementation will help my effort greatly.

Just an update on timelines: we're getting closer but it won't happen before January sometime at the earliest.

Baidu has just released a fast open source implementation of CTC for CPUs and GPUs.
https://github.com/baidu-research/warp-ctc
It has a very simple C interface and it should hopefully be fairly easy to create Tensorflow bindings (we're happy to help).  The release includes Torch bindings.

China is out silicon valleying silicon valley!

what's the timeline now @ebrevdo

We're closer. Still cleaning up code for release.
On Jan 15, 2016 6:41 AM, "qingzew"<EMAIL_ADDRESS>wrote:

what's the timeline now @ebrevdo https://github.com/ebrevdo
—
Reply to this email directly or view it on GitHub
https://github.com/tensorflow/tensorflow/issues/32#issuecomment-171977442
.

Hi Ebrevdo,
A CTC implementation would be really useful to me for some genome analysis tasks that are handled poorly by HMM approaches.
Matthew

@ebrevdo any progress? :)

Also highly interested in this and I hope that you can release your implementation soon! @ebrevdo

Coming very soon (I hope).
On Feb 22, 2016 5:34 AM, "bmilde"<EMAIL_ADDRESS>wrote:

Also highly interested in this and I hope that you can release your
implementation soon! @ebrevdo https://github.com/ebrevdo
—
Reply to this email directly or view it on GitHub
https://github.com/tensorflow/tensorflow/issues/32#issuecomment-187175302
.

The CTC loss and two decoders (greedy & beam search for CTC) should be in the next push.

(it'll be accessible via tf.contrib.ctc.ctc_loss etc.)

Awesome!

Very Awesome

very very awesome!

https://github.com/tensorflow/tensorflow/commit/8509f88ade3fc65f4cc530780d06100f0b1ea108
ctc_loss and friends is now part of contrib directory -- once it matures and we fix any issues, we'll add it to the core.


Documentation is not clear regarding creation of service principals

The page says that workspace admin can create a service principal via SCIM API. On the other hand, SCIM API manual for Azure states that Azure AD application id is required and describes POST method as "Add service principal" (unlike AWS documentation, that describes POST method as  "Create service principal" and applicationId is auto-generated).
In practice it means that in order to create a service principal in Azure Databricks, an Azure AD app must be registered first by User Access Administrator and only then SCIM API can be used by workspace admin.

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

ID: 4388a2ca-f34b-b83b-f315-4c5cd821d19f
Version Independent ID: f97dbccf-bce5-b240-0813-046056a52254
Content: Manage service principals - Azure Databricks
Content Source: databricks/administration-guide/users-groups/service-principals.md
Service: azure-databricks
GitHub Login: @mssaperla
Microsoft Alias: saperla

@amichel  Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

Thanks for your dedication to our documentation. Unfortunately, we have been unable to address your issue and apologize for the delayed response. We are closing this issue, but if you feel that it's still a concern, please let us know directly at<EMAIL_ADDRESS>#please-close

#please-close


[FEAT EXTRACTION]

Hi,
I have a question regarding voxel-based extraction of radiomics features. I am currently performing this with the default voxel-based settings using the code below:
featureVector = extractor.execute(im,ma,voxelBased=True)
for key, val in six.iteritems(featureVector):
if isinstance(val, sitk.Image):
parametermap = sitk.GetArrayFromImage(val)
For now I am only extracting glcm features (extractor.enableFeatureClassByName('glcm'))
This runs without any error messages. However, I am confused by the size of parametermap.
np.shape(parametermap) returns (14, 14, 9), while the shape of my image is (49, 816, 1361).
What do the 3D dimensions of the parametermap represent?
Thanks!

During pre-processing the image is optionally resampled and always cropped onto the bounding box of the mask. The output remains in the geometry after this pre-processing. As they are SimpleITK.Image objects, they contain the necessary information to ensure correct alignment to the original image.
If no resampling was performed, you can easily port the output map to the original space if necessary:
import SimpleITK as sitk
im = sitk.ReadImage('<path/to/original_image.nrrd>')
map = sitk.ReadImage('<path/to/feature_map.nrrd>')

rif =  sitk.ResampleImageFilter()
rif.SetInterpolator(sitk.sitkNearestNeighbor)  # Pixel locations overlap, but feature map is cropped
rif.SetReferenceImage(im)
rif.SetOutputPixelType(map.GetPixelID())
map = rif.Execute(map)
sitk.WriteImage(map, '<path/to/output.nrrd>')


Mixing proxy and non-proxied crates

Hello! (I don't know much of this subject),
At work I've been trying to use Rust and the policy there is as follows: we do need a proxy setup to get to github; and we need a no-proxy setup to get to our internal git server.
But projects usually depend on both internal projects and github projects.
When an internal dependency is updated, cargo fetch usually doesn't work - with or without a proxy setup. When on a no-proxy setup, it fails to update the registry. When on a proxy setup, it is barred from the internal git server.
I've tried many times, with both settings (proxy and no-proxy), and vice-versa, and then also trying --offline on all situations, and there are times that it still doesn't work. Then I proceed to comment-out all crates from Cargo.toml which are not internal, and in a no-proxy setup, run a cargo check until it fetches and then starts to build and then errors'. Then I un-comment the github crates and run again in a proxy setup - and then it does work.
I really don't know if this is an overall configuration flaw (or bad decision) from the company-side on the proxy setting, but would you have some ideas on improvement? Thanks a lot!

Currently Cargo doesn't support a mixed configuration where some hosts use a proxy and others don't, but this sounds like a feature that can be added!

cough your internal server could be http and external be https? That would allow you to configure both. It's a hack but it's quite a neat one!

@gilescope Thanks for the idea! I think they could be!
I reality I didn't update on this issue, but the proxy setup changed (in overall), and now they made it work under a proxied setup even when accessing the company's internal content! So I stoped having this proxy issue! (don't know if others would still encounter this though..)
Well, I guess I'm closing then!
Thanks once again!


How to slow down request via command line?

Instagram seems to be very strict with rate limits these days. Im using my own account and my own IP.
Even when trying to only "fastupdate" one profile i am getting kicked out and getting a 401.
When i return to the browser version i get:
_"We suspect automated behavior on your account
To prevent your account from being temporarily restricted or permanently disabled, ensure that no other users or tools have access to your account and that you're following our Terms of Use. Also consider changing your password to a stronger one to prevent unauthorized access to your account by third parties."
Is there a way i can slow down the request?

Here are the changes that work for me. I should maybe submit a pull request.
in ~/.local/lib/instaloadercontext.py
in class RateController:

fast_sleeps = 10

def sleep(self, secs: float):
global fast_sleeps
if fast_sleeps > 0:
fast_sleeps = fast_sleeps - 1
else:
wait_time = random.uniform(15, 30)
print(wait_time)
time.sleep(wait_time)

Remove > 0 guards in front of sleep further down

Here are the changes that work for me. I should maybe submit a pull request.
# in ~/.local/lib/instaloadercontext.py
# in class RateController:
#
# fast_sleeps = 10
#
#    def sleep(self, secs: float):
#        global fast_sleeps
#        if fast_sleeps > 0:
#            fast_sleeps = fast_sleeps - 1
#        else:
#            wait_time = random.uniform(15, 30)
#            print(wait_time)
#            time.sleep(wait_time)
#
# Remove > 0 guards in front of sleep further down

Can you please explain where I make this change? I cannot find any of these strings in any of the py files.. sorry, sorta python noob here still figuring things out.

Made a pull request.

Still pertinent.

I am wondering the same thing. I got the warning for suspicious activity...I don't want Instagram to ban my account!


Do not disable collision and dont stop moving when goes from crit to dead

About the PR

Resolves #22564
Do not disabling collision for dead mobs since we have #27905  that was the reason why mob stops moving in crit to dead
Why / Balance

Technical details

Media
https://github.com/space-wizards/space-station-14/assets/52600490/091d2dec-2c62-49a8-a0df-2a3343d5392a

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog
fix: mobs continue moving when turning dead state from crit and also still can collide

got a new pr anyway that got merged by emo so...


The new clothing styles cannot be recognized.

The new clothing styles cannot be recognized，What is the solution? Is it to retrain the model?

The new clothing styles cannot be recognized，What is the solution? Is it to retrain the model?

HI @prog-ape ,
The model is trained for imaterialist-fashion-2019-FGVC6 dataset. So if you are using a diffet style then you need to retrain your model.


Added X11 back to the linker list for FreeBSD

It was removed in https://github.com/LaurentGomila/SFML/commit/f464e2502af84ab4a0e8777e32e101812c4e6563. However when I was attempting the build SFML on FreeBSD with static libs the examples failed to link with the following error.

/usr/local/bin/ld: ../../lib/libsfml-window-s-d.a(WindowImplX11.cpp.o): undefined reference to symbol 'XCreateIC'
/usr/local/lib/libX11.so.6: error adding symbols: DSO missing from command line

After some digging I discovered XCreateIC is defined in X11, so when attempting to link the examples to static SFML libs it failed because X11 was not in the linker list.
So this PR adds X11 back to the link list for FreeBSD (and allows linking to static SFML libs again on BSD platforms).

Looks alright. I'd like to understand why that doesn't happen on Linux, though. Any ideas?

Probably because BSD is trying to be cleaner than Linux and really separating XCB and GLX from Xlib. If you ask me, it's Linux who exhibits the "non-standard" behaviour. If you link to OpenGL on Linux, it automatically pulls in Xlib as well, same with XCB probably. This is why the only real way to get rid of the Xlib dependency is to drop GLX and use EGL like Wayland does (it uses EGL on purpose so it doesn't pull in X) and hope that one day XCB on Linux won't pull in Xlib automatically any more.

Well does anyone have anything against this or any suggestions to try instead of linking X11?

@binary1248
That's true, and that's also what made me wonder why removing the libraries from linkage actually worked... lol
@zsbzsb
It's alright. I removed it because not necessary on Linux. Now that we know it's necessary, we can simply add them again.
:+1:

we can simply add them again.

:smiley_cat:  :+1:

This PR has been added to my merge list, meaning it will be merged soon, unless someone raises any concerns.

:+1:

Merged in ae53cfd0d960f6ea9424b63b9141045c1137b7b3


scheduler: fix min counter get count not correct

这个 PR 实现什么功能/修复什么问题:

是否需要 backport 到之前的 release 分支:

2.13
/area scheduler
/cc @ioito

Codecov Report

Merging #6381 into master will decrease coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #6381      +/-   ##
==========================================
- Coverage    7.13%    7.13%   -0.01%
==========================================
  Files         646      646
  Lines      108451   108451
==========================================
- Hits         7740     7738       -2
- Misses     100114   100115       +1
- Partials      597      598       +1

Flag
Coverage Δ

#aFlag
7.13% <ø> (-0.01%)
:arrow_down:

Impacted Files
Coverage Δ

pkg/appsrv/response.go
66.17% <0.00%> (-2.95%)
:arrow_down:

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 86fbbf5...db65bf4. Read the comment docs.


Support using the plugin as a terminal background

It would be awesome if the plugin could provide a 'background' mode instead of only showing up on keystroke 😺

Published in v3.1.0 as an alwaysActive option.

I'm not sure it was exactly what you were requesting. It has the same effect as what @cripplet was suggesting though.


fix go vet warnings: call to (*T).Fatalf from a non-test goroutine

The goroutine started from test must not call t.Fatal, but t.Error. Adds
a sync.WaitGroup to make sure all goroutines have a chance to report an
error before test stops.
Similar fix to https://github.com/fsnotify/fsnotify/pull/416

Codecov Report
Base: 87.63% // Head: 87.63% // No change to project coverage :thumbsup:

Coverage data is based on head (ed8db3c) compared to base (ae97080).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #166   +/-   ##
=======================================
  Coverage   87.63%   87.63%
=======================================
  Files          15       15
  Lines         954      954
=======================================
  Hits          836      836
  Misses         74       74
  Partials       44       44

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Thank you


updated GUI result display at start up

GUI now displays any error that happened during the initial loading of the data

Codecov Report

Merging #191 (58ff350) into master (4515eb8) will decrease coverage by 0.47%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master     #191      +/-   ##
============================================
- Coverage     45.25%   44.78%   -0.48%
  Complexity      470      470
============================================
  Files           115      115
  Lines          2457     2483      +26
  Branches        273      273
============================================
  Hits           1112     1112
- Misses         1279     1305      +26
  Partials         66       66

Impacted Files
Coverage Δ

src/main/java/seedu/address/MainApp.java
0.00% <0.00%> (ø)

src/main/java/seedu/address/ui/MainWindow.java
0.00% <0.00%> (ø)

src/main/java/seedu/address/ui/UiManager.java
0.00% <0.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 4515eb8...58ff350. Read the comment docs.


bugfix: fix code compiling failed with rust-1.49.0

rust v1.49.0 has stricter constraint, causing Nydus code
compiling failed. This PR will sovle it.
Fixes: #39
Signed-off-by: LiYa'nan<EMAIL_ADDRESS>

While at it, please change .travis.yaml to use rustc v1.49.0 so that we don't introduce breakage accidentally.

While at it, please change .travis.yaml to use rustc v1.49.0 so that we don't introduce breakage accidentally.

While at it, please change .travis.yaml to use rustc v1.49.0 so that we don't introduce breakage accidentally.

Thank you @bergwolf
I have updated the rust version to 1.49.0, but CI is still failed.
Cloud you give some advice?

While at it, please change .travis.yaml to use rustc v1.49.0 so that we don't introduce breakage accidentally.

Thank you @bergwolf
I have updated the rust version to 1.49.0, but CI is still failed.
Cloud you give some advice?

@Apokleos Sure, your change looks good. Let me take a closer look.

@Apokleos Sure, your change looks good. Let me take a closer look.

Turns out we do have multiple places to specific rust version for different tools. Please also change the smoke Dockerfile as well... Thanks a lot!
https://github.com/dragonflyoss/image-service/blob/master/misc/smoke/Dockerfile#L1

Turns out we do have multiple places to specific rust version for different tools. Please also change the smoke Dockerfile as well... Thanks a lot!
https://github.com/dragonflyoss/image-service/blob/master/misc/smoke/Dockerfile#L1


Wrong code in example in empty table overlay

Wrong code for example empty table overlay. No source of NoDataIndication in the example

@vikhyatprabhu thanks, I will patch in next release.

Fixed on official document and source code, thank you 👍


Email from CircleCI, any action needed?

Hi there,
On November 1st, Docker Hub will begin limiting anonymous image pulls. We want to make sure you know how you might be impacted and what you can do to avoid interruptions to your workflow.
Adding Docker authentication to your pipeline config is the easiest way to avoid any service disruptions. If you use the Docker executor or pull Docker images when using the machine executor on CircleCI, we encourage you to authenticate. Because the anonymous API rate limits are based on IP addresses, they will impact CircleCI cloud customers. Authenticated users get higher per-user rate limits, regardless of IP.
We are currently working on a partnership with Docker to minimize the impact of this change for our users and will share more details as we get them.
For more information or to leave a question for us, please head over to Discuss or contact support.
Thanks and happy building,

The CircleCI team

/cc https://github.com/KhronosGroup/glTF-Blender-IO/pull/1274


[Bug] exercise "en/c/variables/1.md" has an issue

I wrote you twice already. The first exercise on variables says my answer is wrong but it’s right because I paid and I can see the solution and it’s the same as my answer. I can’t go forward now and I’m stuck on this and it’s the same problem on many other questions in other chapters. Please fix this!!!

@all-contributors please add @valevolta0501 for bug

I found the problem, thank you very much for the report! 😊
Before testing again, please go to the Profile page and tap on the Delete cache button


require CallExpressions inside MemberExpressions trick group-imports rule

Just noticed this while looking at https://github.com/liferay/liferay-js-themes-toolkit/pull/393/files#diff-607f89928a61f2489713663b891f76aa
diff --git a/packages/liferay-theme-tasks/plugin/test/tasks/version.js b/packages/liferay-theme-tasks/plugin/test/tasks/version.js
index 1ebd412..1634a94 100644
--- a/packages/liferay-theme-tasks/plugin/test/tasks/version.js
+++ b/packages/liferay-theme-tasks/plugin/test/tasks/version.js
@@ -10,6 +10,7 @@ var chai = require('chai');
 var del = require('del');
 var fs = require('fs-extra');
 var Gulp = require('gulp').Gulp;
+
 var os = require('os');
 var path = require('path');

@@ -30,11 +31,11 @@ var initCwd = process.cwd();
 var registerTasks;
 var runSequence;

Looks like the Gulp require is tricking the group-imports rule into starting a new group.

Similar problem here: https://github.com/liferay/liferay-js-themes-toolkit/pull/393/files#diff-5688ba5971f6c2d3bdf9cf4265442a01
diff --git a/packages/liferay-theme-tasks/tasks/build.js b/packages/liferay-theme-tasks/tasks/build.js
index 5e06621..8fa8470 100644
--- a/packages/liferay-theme-tasks/tasks/build.js
+++ b/packages/liferay-theme-tasks/tasks/build.js
@@ -8,12 +8,13 @@

 const del = require('del');
 const fs = require('fs-extra');
-const _ = require('lodash');
-const path = require('path');
-const plugins = require('gulp-load-plugins')();
 const replace = require('gulp-replace-task');
-const through = require('through2');
+const _ = require('lodash');
+const plugins = require('gulp-load-plugins')();
+
+const path = require('path');
 const PluginError = require('plugin-error');
+const through = require('through2');

 const getBaseThemeDependencies = require('../lib/getBaseThemeDependencies');
 const lfrThemeConfig = require('../lib/liferay_theme_config');

This time the CallExpression is inside another CallExpression.

I think the fix here will be two (or maybe three parts):

Teach group-imports to not add those blank lines.
(Definitely) Add a new lint that tells people to prefer destructuring over x = require('foo').x.
(Maybe) Add a new lint that tells people not to immediately call require results (eg. x = require('x')()).

Crude fix for "1." is up at https://github.com/liferay/eslint-config-liferay/pull/97
Will look at "2." (and maybe "3.") later on.

New "destructure-requires" rule to address "2." is up at: https://github.com/liferay/eslint-config-liferay/pull/98

New "no-require-and-call" rule to address "3." is up at: https://github.com/liferay/eslint-config-liferay/pull/99


Enable-WriteCore-for-Azure.Messaging.EventGrid.SystemEvents

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

/azp run

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.Messaging.EventGrid.SystemEvents


are you still alive

i noticed the site has gone down and no one has updated this since 2017

This project has been dead a LONG time. It's horribly outdated too I don't suggest doing anything with it.

well that is unfortunate i was looking  for an alternative to bitmessage and retroshare


[1.7.10] draconium ore from draconic evolution

hello,
I don't know why but, the builder in quarry mod with fortune doesn't mine draconium ore.
any idea on how to fix it ?

It is because it is a tile entity and by default the rftools quarry doesn't mine those. You can change that in the config. There is an option for it


Request connection permissions and retrieve wallet data

I've been working with the sats-connect package and tried running the example you provided here. Unfortunately, I encountered some issues, and it doesn't seem to work as expected. Could you please provide information about the latest version of your package and any updates or fixes that might address this problem?

I've been working with the sats-connect package and tried running the example you provided here. Unfortunately, I encountered some issues, and it doesn't seem to work as expected. Could you please provide information about the latest version of your package and any updates or fixes that might address this problem?

Hi @abdolian,
This feature is still a work in progress, but we plan to release it soon. In the meantime, I'm happy to help with any other issues you might be experiencing with the latest version.

@abdolian this was released in sats-connect 2.5.0 and supported by xverse chrome extension >=0.38.1, so that example in the docs should work with the latest versions.
thanks


[Service Bus] The code always throws error "Operation to settle the message has timed out. The disposition of the message may or may not be successful" after processing message.

@azure/service-bus:
1.0.2:
Mac OS:
[ ] nodejs

11.2.0:

[ ] typescript

3.5.1:

The error "Operation to settle the message has timed out. The disposition of the message may or may not be successful" happens every time during message processing
I have created topic inside AzurePortal => Service Bus and created subscription to that topic.
I copied the example from documentation.
const { ServiceBusClient, ReceiveMode, delay } = require('@azure/service-bus');

export class SubscriptionService {
  constructor() {
    this.main().catch((err) => {
      console.log('Error occurred: ', err);
    });
  private async main() {
   const sbClient = ServiceBusClient.createFromConnectionString(process.env.AZURE_SERVICEBUS_CONNECTION_STRING || '');

    // If receiving from a Subscription, use `createSubscriptionClient` instead of `createQueueClient`
    const queueClient = sbClient.createSubscriptionClient(TestTopic, 'test');

    // To receive messages from sessions, use getSessionReceiver instead of getReceiver or look at
    // the sample in sessions.js file
    const receiver = queueClient.createReceiver(ReceiveMode.peekLock);

    const onMessageHandler = async (brokeredMessage: any) => {
      console.log(`Received message: ${brokeredMessage.body}`);
      await brokeredMessage.complete();
    };
    const onErrorHandler = (err: any) => {
      console.log("Error occurred: ", err);
    };

    try {
      receiver.registerMessageHandler(onMessageHandler, onErrorHandler, { autoComplete: false });

      // Waiting long enough before closing the receiver to receive messages
      await delay(5000);

      await receiver.close();
      await queueClient.close();
    } finally {
      await sbClient.close();
    }
  }
}

onMessageHandler receives a message from the topic. The code processes the message. Message got removed from Azure Portal => Service Bus. I get the error Operation to settle the message has timed out. The disposition of the message may or may not be successful inside onErrorHandler after onMessageHandler is done executing. Error happens every time.
To Reproduce
Steps to reproduce the behavior:

Create topic in service bus
Create subscription to the topic
Use the code from documentation

const { ServiceBusClient, ReceiveMode, delay } = require("@azure/service-bus");

// Define connection string and related Service Bus entity names here
const connectionString = "";
const queueName = "";

async function main() {
  const sbClient = ServiceBusClient.createFromConnectionString(connectionString);

  // If receiving from a Subscription, use `createSubscriptionClient` instead of `createQueueClient`
  const queueClient = sbClient.createQueueClient(queueName);

  // To receive messages from sessions, use getSessionReceiver instead of getReceiver or look at
  // the sample in sessions.js file
  const receiver = queueClient.createReceiver(ReceiveMode.peekLock);

  const onMessageHandler = async (brokeredMessage) => {
    console.log(`Received message: ${brokeredMessage.body}`);
    await brokeredMessage.complete();
  };
  const onErrorHandler = (err) => {
    console.log("Error occurred: ", err);
  };

  try {
    receiver.registerMessageHandler(onMessageHandler, onErrorHandler, { autoComplete: false });

    // Waiting long enough before closing the receiver to receive messages
    await delay(5000);

    await receiver.close();
    await queueClient.close();
  } finally {
    await sbClient.close();
  }
}

main().catch((err) => {
  console.log("Error occurred: ", err);
});

Execute code

Expected behavior
Process and clear up messages inside the topic without error.
Screenshots
Receive message from topic inside onMessageHandler:

When onMessageHandler is done executing:

Error:

Additional context
Full error:
condition:"com.microsoft:timeout"
info:undefined
message:"Operation to settle the message has timed out. The disposition of the message may or may not be successful"
name:"ServiceUnavailableError"
retryable:true
stack:"ServiceUnavailableError: Operation to settle the message has timed out. The disposition of the message may or may not be successful\n    at Object.translate (/Users/d/Projects/SB/node_modules/@azure/amqp-common/dist/index.js:741:17)\n    at Timeout.setTimeout [as _onTimeout] (/Users/d/Projects/SB/node_modules/@azure/service-bus/dist/index.js:2317:46)\n    at listOnTimeout (timers.js:324:15)\n    at processTimers (timers.js:268:5)"
translated:true

Thanks for reporting @dlukianenko
When a request to settle a message (in your case "complete" a message) is made to Service Bus, the library waits for 20 seconds to hear back an acknowledgement that the message has indeed been successfully settled. The error you are seeing is thrown when this 20 second duration times out.
@binzywu What should be the ideal timeout duration for this case i.e. how long should the client library wait to hear back an acknowledgement from the service?

@dlukianenko, would  you please create a support request from the Azure Portal for this issue and include in it more contextual information like the name of your namespace? This is an issue for which we need to do further investigation on the service side.  20 seconds timeout should be enough and the fact that you are getting an error may be indicative of some other problem condition.
I am going to close this issue, but feel free to reopen it if you have other kind of questions.

@dlukianenko

@dlukianenko, did you create the support request? Would you please share the SR#?

Hello, I'm on a dev-test subscription and currently, I don't have a tech support subscription, so I cannot really create actual ServiceBus support requests without paying for tech support subscription. Is there any other option available to me?

We've also seen this over 1500 times since our service using service into production a few months ago. Are there any queue configurations to check or anything we can do before raising a support query? Thanks @ramya-rao-a :)

As a work around, would it make sense to check message.isSettled before processing? Does that get successfully written in the case of these timeouts?

@SamJarmanPP Unfortunately no. he isSettled property on a message gets set on the service side before it sends the message to the client. Once the client makes the request to settle the message, the client then waits for an acknowledgement from the service. This is where the time out happens. The message object is entirely on the client side at this point and is not mutated.

@ramya-rao-a Ah okay, darn. I asked over here what we should do in these cases - looking forward to hearing back :) We just want to make sure the message is processed once and only once, and that this is guaranteed. (Are we asking too much? haha)

@SamJarmanPP please could you open a support case and provide us more details of namespace, entity, timestamp and ideally few sample message ids will be very helpful.

@binzywu Sure but I feel the answer you provide would be applicable to anyone receiving this error?

@SamJarmanPP Opening a support case/ticket will help @binzywu's team investigate the problem because they can then check the logs from the service side as well. Once they come to a conclusion on what the problem is, @binzywu or his team will surely update this GitHub issue with the answer and possible steps that can be taken to fix it

@binzywu @ramya-rao-a opened one yesterday -<PHONE_NUMBER>02394 :)

Thanks @SamJarmanPP,
I'll close the issue now and we can track this via the support ticket.

@axayjo Based on the support ticket logged by @SamJarmanPP, his issue is with what is being discussed at https://github.com/Azure/azure-sdk-for-js/pull/2828#issuecomment-521110301
Originally, this issue was logged by @dlukianenko who doesn't have a subscription with tech support. Can you suggest any other way you can look into why the service is not able to settle messages within 20 seconds?

@dlukianenko
We will need to access the service logs for the specified namespace to debug the root cause of the delay in completing the message.
In the meantime, there are some options

Increasing the operation timeout (in other lang clients, the default timeout is 60 seconds)
Rely on retry logic

I'm closing the issue for now. Please feel free to reopen if you still have questions.


Fixes at-expiration values being nan

Fixes #89.  Fixes at-expiration values being nan for certain option models.
Tests were run to ensure that values prior to expiration are not affected.  Tests were also run to ensure that execution time was not impacted materially.  Bazel tests also passed for all modified functions.

Could you please sync your version to head as well to fix current merge failure?

I synced my fork and I see there is a new commit here, but it looks like copybara is still failing.  Is there anything else I need to do?

Thank you, Alex! Could  you please run git squash?

I haven't added in the test yet, I only synced my fork with master.  I will have the tests done soon and then I will squash the commits and force push.

OK, test added and squashed commits, I hope I did it right.


[lint] Lint errors in test directory

************* Module tests.defaults
tests/defaults.py:1:0: C0114: Missing module docstring (missing-module-docstring)
************* Module tests.unit.test_image_introspection
tests/unit/test_image_introspection.py:5:0: R0402: Use 'from ansible_navigator import utils' instead (consider-using-from-import)
************* Module tests.unit.test_yaml
tests/unit/test_yaml.py:1:0: C0114: Missing module docstring (missing-module-docstring)
tests/unit/test_yaml.py:4:0: C0116: Missing function or method docstring (missing-function-docstring)
************* Module tests.unit.test_cli
tests/unit/test_cli.py:99:11: C1803: 'exit_msgs == []' can be simplified to 'not exit_msgs' as an empty sequence is falsey (use-implicit-booleaness-not-comparison)
tests/unit/test_cli.py:112:11: C1803: 'exit_msgs == []' can be simplified to 'not exit_msgs' as an empty sequence is falsey (use-implicit-booleaness-not-comparison)
************* Module tests.unit.test_log_append
tests/unit/test_log_append.py:5:0: R0402: Use 'from ansible_navigator import cli' instead (consider-using-from-import)
************* Module tests.unit.configuration_subsystem.test_invalid_params
tests/unit/configuration_subsystem/test_invalid_params.py:80:49: R1732: Consider using 'with' for resource-allocating operations (consider-using-with)
************* Module tests.unit.configuration_subsystem.conftest
tests/unit/configuration_subsystem/conftest.py:45:13: W1514: Using open without explicitly specifying an encoding (unspecified-encoding)
************* Module tests.unit.configuration_subsystem.test_fixture_sanity
tests/unit/configuration_subsystem/test_fixture_sanity.py:25:9: W1514: Using open without explicitly specifying an encoding (unspecified-encoding)
************* Module tests.unit.configuration_subsystem.test_previous_cli
tests/unit/configuration_subsystem/test_previous_cli.py:81:11: C1803: 'exit_messages == []' can be simplified to 'not exit_messages' as an empty sequence is falsey (use-implicit-booleaness-not-comparison)
tests/unit/configuration_subsystem/test_previous_cli.py:101:11: C1803: 'exit_messages == []' can be simplified to 'not exit_messages' as an empty sequence is falsey (use-implicit-booleaness-not-comparison)
tests/unit/configuration_subsystem/test_previous_cli.py:128:15: C1803: 'exit_messages == []' can be simplified to 'not exit_messages' as an empty sequence is falsey (use-implicit-booleaness-not-comparison)
tests/unit/configuration_subsystem/test_previous_cli.py:152:15: C1803: 'exit_messages == []' can be simplified to 'not exit_messages' as an empty sequence is falsey (use-implicit-booleaness-not-comparison)
tests/unit/configuration_subsystem/test_previous_cli.py:179:11: C1803: 'exit_messages == []' can be simplified to 'not exit_messages' as an empty sequence is falsey (use-implicit-booleaness-not-comparison)
tests/unit/configuration_subsystem/test_previous_cli.py:201:11: C1803: 'exit_messages == []' can be simplified to 'not exit_messages' as an empty sequence is falsey (use-implicit-booleaness-not-comparison)
tests/unit/configuration_subsystem/test_previous_cli.py:228:11: C1803: 'exit_messages == []' can be simplified to 'not exit_messages' as an empty sequence is falsey (use-implicit-booleaness-not-comparison)
tests/unit/configuration_subsystem/test_previous_cli.py:249:11: C1803: 'exit_messages == []' can be simplified to 'not exit_messages' as an empty sequence is falsey (use-implicit-booleaness-not-comparison)
tests/unit/configuration_subsystem/test_previous_cli.py:293:11: C1803: 'exit_messages == []' can be simplified to 'not exit_messages' as an empty sequence is falsey (use-implicit-booleaness-not-comparison)
tests/unit/configuration_subsystem/test_previous_cli.py:309:11: C1803: 'exit_messages == []' can be simplified to 'not exit_messages' as an empty sequence is falsey (use-implicit-booleaness-not-comparison)
************* Module tests.unit.configuration_subsystem.test_precedence
tests/unit/configuration_subsystem/test_precedence.py:22:0: W0611: Unused GenerateConfigResponse imported from conftest (unused-import)
************* Module tests.unit.configuration_subsystem.utils
tests/unit/configuration_subsystem/utils.py:43:0: C0116: Missing function or method docstring (missing-function-docstring)
tests/unit/configuration_subsystem/utils.py:47:12: C0103: Variable name "vm" doesn't conform to snake_case naming style (invalid-name)
************* Module tests.unit.configuration_subsystem.test_sample_configurations
tests/unit/configuration_subsystem/test_sample_configurations.py:43:11: C1803: 'configurator._exit_messages == []' can be simplified to 'not configurator._exit_messages' as an empty sequence is falsey (use-implicit-booleaness-not-comparison)
************* Module tests.unit.configuration_subsystem.test_container_engine_auto
tests/unit/configuration_subsystem/test_container_engine_auto.py:1:0: C0114: Missing module docstring (missing-module-docstring)
tests/unit/configuration_subsystem/test_container_engine_auto.py:31:14: W0613: Unused argument 'arg' (unused-argument)
************* Module tests.unit.actions.test_config
tests/unit/actions/test_config.py:4:0: W0611: Unused import os (unused-import)
************* Module tests.unit.actions.test_inventory
tests/unit/actions/test_inventory.py:1:0: C0114: Missing module docstring (missing-module-docstring)
************* Module tests.unit.actions.test_run
tests/unit/actions/test_run.py:189:4: W0212: Access to a protected member _queue of a client class (protected-access)
tests/unit/actions/test_run.py:190:4: W0212: Access to a protected member _run_runner of a client class (protected-access)
************* Module tests.integration._interactions
tests/integration/_interactions.py:44:8: R1705: Unnecessary "else" after "return" (no-else-return)
************* Module tests.integration.test_pass_environment_variable
tests/integration/test_pass_environment_variable.py:10:0: R0402: Use 'from ansible_navigator import cli' instead (consider-using-from-import)
tests/integration/test_pass_environment_variable.py:67:4: R0913: Too many arguments (6/5) (too-many-arguments)
************* Module tests.integration._common
tests/integration/_common.py:24:0: R0913: Too many arguments (6/5) (too-many-arguments)
tests/integration/_common.py:75:0: C0116: Missing function or method docstring (missing-function-docstring)
************* Module tests.integration.test_execution_environment_image
tests/integration/test_execution_environment_image.py:10:0: R0402: Use 'from ansible_navigator import cli' instead (consider-using-from-import)
************* Module tests.integration._action_run_test
tests/integration/_action_run_test.py:24:0: R0902: Too many instance attributes (13/7) (too-many-instance-attributes)
tests/integration/_action_run_test.py:27:4: R0913: Too many arguments (12/5) (too-many-arguments)
tests/integration/_action_run_test.py:140:21: R1732: Consider using 'with' for resource-allocating operations (consider-using-with)
tests/integration/_action_run_test.py:141:21: R1732: Consider using 'with' for resource-allocating operations (consider-using-with)
************* Module tests.integration.test_execution_environment
tests/integration/test_execution_environment.py:10:0: R0402: Use 'from ansible_navigator import cli' instead (consider-using-from-import)
************* Module tests.integration._tmux_session
tests/integration/_tmux_session.py:16:0: R0902: Too many instance attributes (16/7) (too-many-instance-attributes)
tests/integration/_tmux_session.py:19:4: R0913: Too many arguments (9/5) (too-many-arguments)
tests/integration/_tmux_session.py:157:4: R0914: Too many local variables (22/15) (too-many-locals)
tests/integration/_tmux_session.py:264:21: W1514: Using open without explicitly specifying an encoding (unspecified-encoding)
tests/integration/_tmux_session.py:274:21: W1514: Using open without explicitly specifying an encoding (unspecified-encoding)
tests/integration/_tmux_session.py:157:4: R0912: Too many branches (27/12) (too-many-branches)
tests/integration/_tmux_session.py:157:4: R0915: Too many statements (76/50) (too-many-statements)
************* Module tests.integration.test_set_environment_variable
tests/integration/test_set_environment_variable.py:10:0: R0402: Use 'from ansible_navigator import cli' instead (consider-using-from-import)
tests/integration/test_set_environment_variable.py:67:4: R0913: Too many arguments (6/5) (too-many-arguments)
************* Module tests.integration.actions.templar.base
tests/integration/actions/templar/base.py:121:17: W1514: Using open without explicitly specifying an encoding (unspecified-encoding)
************* Module tests.integration.actions.images.base
tests/integration/actions/images/base.py:17:14: C0207: Use DEFAULT_CONTAINER_IMAGE.rsplit('/', maxsplit=1)[-1] instead (use-maxsplit-arg)
tests/integration/actions/images/base.py:47:4: R0201: Method could be a function (no-self-use)
tests/integration/actions/images/base.py:99:17: W1514: Using open without explicitly specifying an encoding (unspecified-encoding)
tests/integration/actions/images/base.py:14:0: W0611: Unused FIXTURES_DIR imported from defaults (unused-import)
************* Module tests.integration.actions.doc.test_welcome_interactive_ee
tests/integration/actions/doc/test_welcome_interactive_ee.py:20:0: W1404: Implicit string concatenation found in assignment (implicit-str-concat)
tests/integration/actions/doc/test_welcome_interactive_ee.py:28:0: W1404: Implicit string concatenation found in assignment (implicit-str-concat)
************* Module tests.integration.actions.doc.test_welcome_interactive_noee
tests/integration/actions/doc/test_welcome_interactive_noee.py:3:0: W0611: Unused Optional imported from typing (unused-import)
************* Module tests.integration.actions.doc.base
tests/integration/actions/doc/base.py:41:4: R0914: Too many local variables (19/15) (too-many-locals)
tests/integration/actions/doc/base.py:41:4: R0912: Too many branches (14/12) (too-many-branches)
tests/integration/actions/doc/base.py:9:0: C0411: standard import "from typing import Optional" should be placed before "import pytest" (wrong-import-order)
************* Module tests.integration.actions.doc.test_direct_interactive_noee
tests/integration/actions/doc/test_direct_interactive_noee.py:5:0: C0411: standard import "from typing import List" should be placed before "import pytest" (wrong-import-order)
************* Module tests.integration.actions.doc.test_stdout
tests/integration/actions/doc/test_stdout.py:107:0: W1404: Implicit string concatenation found in assignment (implicit-str-concat)
tests/integration/actions/doc/test_stdout.py:131:0: W1404: Implicit string concatenation found in assignment (implicit-str-concat)
************* Module tests.integration.actions.doc.test_direct_interactive_ee
tests/integration/actions/doc/test_direct_interactive_ee.py:11:0: W1404: Implicit string concatenation found in assignment (implicit-str-concat)
tests/integration/actions/doc/test_direct_interactive_ee.py:20:0: W1404: Implicit string concatenation found in assignment (implicit-str-concat)
tests/integration/actions/doc/test_direct_interactive_ee.py:29:0: W1404: Implicit string concatenation found in assignment (implicit-str-concat)
************* Module tests.integration.actions.run.base
tests/integration/actions/run/base.py:116:17: W1514: Using open without explicitly specifying an encoding (unspecified-encoding)
tests/integration/actions/run/base.py:61:4: R0912: Too many branches (13/12) (too-many-branches)
tests/integration/actions/run/base.py:8:0: C0411: standard import "from typing import Optional" should be placed before "import pytest" (wrong-import-order)
************* Module tests.integration.actions.config.base
tests/integration/actions/config/base.py:102:17: W1514: Using open without explicitly specifying an encoding (unspecified-encoding)
************* Module tests.integration.actions.collections.test_welcome_interactive_ee
tests/integration/actions/collections/test_welcome_interactive_ee.py:29:0: R0903: Too few public methods (1/2) (too-few-public-methods)
************* Module tests.integration.actions.collections.test_welcome_interactive_noee
tests/integration/actions/collections/test_welcome_interactive_noee.py:28:0: R0903: Too few public methods (1/2) (too-few-public-methods)
************* Module tests.integration.actions.collections.base
tests/integration/actions/collections/base.py:91:13: W1514: Using open without explicitly specifying an encoding (unspecified-encoding)
tests/integration/actions/collections/base.py:19:0: R0903: Too few public methods (1/2) (too-few-public-methods)
************* Module tests.integration.actions.collections.test_direct_interactive_noee
tests/integration/actions/collections/test_direct_interactive_noee.py:27:0: R0903: Too few public methods (1/2) (too-few-public-methods)
************* Module tests.integration.actions.collections.test_direct_interactive_ee
tests/integration/actions/collections/test_direct_interactive_ee.py:28:0: R0903: Too few public methods (1/2) (too-few-public-methods)
************* Module tests.integration.actions.inventory.base
tests/integration/actions/inventory/base.py:123:17: W1514: Using open without explicitly specifying an encoding (unspecified-encoding)
************* Module tests.integration.actions.replay.base
tests/integration/actions/replay/base.py:56:13: W1514: Using open without explicitly specifying an encoding (unspecified-encoding)
************* Module tests.integration.actions.stdout.test_welcome_interactive_ee
tests/integration/actions/stdout/test_welcome_interactive_ee.py:9:0: W1404: Implicit string concatenation found in assignment (implicit-str-concat)
************* Module tests.integration.actions.stdout.base
tests/integration/actions/stdout/base.py:57:13: W1514: Using open without explicitly specifying an encoding (unspecified-encoding)

Note:  These have been here since the early days since pylint was never in scope for the tests directory

all done.


[Wave Size Range] Should constant values be allowed?

Which proposal does this relate to?
https://github.com/microsoft/hlsl-specs/blob/main/proposals/0014-wave-size-range.md
Describe the issue or outstanding question.
Do the parameters to WaveSize really need to be literals or could they be compile-time constant expressions?
Is there any reason not to support something like:
static const int Val = 2;
[WaveSize(Val, Val * 4, Val * 2)]
We have some bugs in DXC that relate to evaluation of constant expressions, but we could certainly support this use case in Clang.
Additional context
https://github.com/microsoft/hlsl-specs/pull/149#discussion_r1458175836

Related: https://github.com/microsoft/DirectXShaderCompiler/issues/2188
IMO, if we consider the above to be a bug, we should write our spec to treat it as a bug that DXC can't support these cases.

In group discussion, we decided to formally allow any compile-time constant values for any parameter of WaveSize. This includes the legacy 6.6 version. As Chris pointed out, due to the above-mentioned bug, these compile time constants can't actually be used for such until it is resolved, but as far as the spec is concerned, any compile-time constant value that the language supports is acceptable.


Fix Bear asset import when they have the same base name (#229)

I've taken this idea and run with it, modifying it so that it uses getAvailablePathForAttachment instead (commit). I'm going to close this PR now. Thanks.


[MM-38503] Upgrade to Electron v14

Summary
Upgrading to Electron v14 as it is stable now. Should fix some bugs.
Ticket Link
https://mattermost.atlassian.net/browse/MM-36727
https://mattermost.atlassian.net/browse/MM-38503
Release Note
Upgraded to Electron v14

@jupenur Added you just for awareness, no issues to call out I don't think based on the changes.


[log4cplus] update

@atkawa7,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

Nice! Thanks for the PR!


Swagger API Browser No Longer Filters By Endpoint

Environment

Python version:  3.6.5
NetBox version:  v2.5.1

Steps to Reproduce
Browse to /api/docs/ and attempt to filter on dcim.
The only filter that functions now is api which is not very helpful as they all being with api
See screenshot below from v2.5.1.
With no filter applied:

Attempting to filter on dcim:

Versus the previous behavior on v2.4.8:
With no filter applied:

Filtering on dcim:

Expected Behavior
It should correctly filter on the named endpoints.
Observed Behavior
Endpoints are no longer filterable.

Swagger has been rife with problems since it was introduced. We're soon replacing it with either the DRF built-in docs (#2665) or custom code. If you want to submit a PR for a short-term fix I'll leave this open. Otherwise, I don't think we're going to expend any more effort on Swagger unless it's a critical bug.

Fixed this by excluding the root API view from Swagger UI.

That appears to have been a simple fix, thanks!

Yeah, it was a pleasant surprise. :)


Add Unit Tests

Detailed Description
We should add more unit tests for the repo, downloading, etc.
Context
Unit tests are good
Possible Implementation
Possibly pass in the key and secret through GH Repo secrets? Then it could try downloading some data, etc.

Plotting has some unit tests, need to add them for checking that time period already exists or not (I am not convinced it is currently working...)

As mentioned over at https://github.com/openclimatefix/Satip/issues/72, I would be a taker for this one. I like writing tests. :)
You mentioned above the problem of passing secrets.
But the API-keys are personalised, so I guess the best way would be to provide a detailed instruction where to get your own set of API-keys when you want to contribute to development, instead of semi-hard-coding the keys via e.g. git-secrets. What do you think?

Actually, I've added the keys as secrets here, so I think it's good so that the tests can be run with actual data on the ci tests. But also, adding to the readme how  to get your own keys would be great too!

Ah, cool, had not seen that keys had been added, but had not really looked.
Will add a section on how to get your keys, as I got them yesterday and let's say the documentation from Eumetsat is comprehensive and slightly unforgiving. At least to me it seemed. ;)

thanks @notger for doing this

No worries, my pleasure. However, this weekend I came down with Covid and the fun-factor in that is limited. So I don't guess I will get much done this week.

Would suggest to close this issue as well, see discussion in issue #72 .
More unit testing does seem neither feasible nor sensible.

Happy to close, keeps the conversation tidy


if ngModel is temporarily undefined, avoid to call setModelData

I think this should solve:
https://github.com/esvit/ng-ckeditor/issues/64

sorry, more work to do :/