promql: numerical comparison of label values

Proposal
I'm not sure if the following is a good idea, but since we (inconclusively) discussed it at the dev summit, I thought I put it in here so that at least we don't forget and can come to an informed decision later.
I also have a vague feeling that this was proposed earlier, but I couldn't find any reference to it.
Problem
Sometimes label values (which are always strings in Prometheus) happen to contain numbers. That's generally not a good idea, but sometimes it just happens. And most prominently, this case features in classic histograms (with the values of the le labels) and in summaries (with the values of the quantile labels).
Now there are many ways of writing the same number, for example .1, 0.1, 0.10, +0.1', 1e-1` are all representing the same number while not passing as equal when doing label matching in PromQL. OpenMetrics took a stab at unifying the formatting, but there are still two problems left:

In practice, there will always be non-compliant metrics producers, because – depending on your tool chain – generating the “right” formatting might be quite cumbersome and not-obvious (e.g. in Go).
There are numbers where the common formatting algorithms just don't come up with a reproducible answer. A formatting algorithm is mostly concerned with creating the shortest sequence of digits that recreates the exact same IEEE 754 float representation when parsed. There can be up to nine different sequences all fulfilling this requirement, and while I can imagine an algorithm that reproducibly picks one out of those, it would probably be quite expensive, and more importantly, most languages won't have an implementation ready.

Furthermore, once you have to deal with numbers in label values, you might want to do comparisons like "greater than".
Proposal
We could introduce new label matching operators that act based on parsed float values. They could look like:

{foo=="1.234"}: numerical equality
{foo!=="1.234"}: numerical inequality
{foo<="1.234"}: numerically less than or equal
{foo>="1.234"}: numerically greater than or equal
{foo<"1.234"}: numerically less than
{foo>"1.234"}: numerically greater than

If a label value doesn't parse as a float number, the matcher would not match (and maybe we can issue a warning via the new warning framework in PromQL).
Concerns

This is a lot of new syntax for a niche use case.
And it won't even end there because one might argue we should then also be able to do aggregation based on the numerical label value (do a sum by (le) where all numerically equal le labels end up in one resulting entry).

Alternatives
Normalization on ingestion
Prometheus 1.x normalized the values of the le and quantile labels of (classic) histograms and summaries, respectively, i.e. it parsed them as floats and then reformatted them into strings before storing them into the TSDB.
This is happening again in Prometheus 2.x if you activate native histograms because then you will also resurrect protobuf  scraping, which represents those values as actual float values anyway.
At the recent dev-summit, we reached the consensus that we want to let Prometheus normalize those two label values always (again), which would then implement an earlier proposal of mine that got rejected by OpenMetrics.
This however doesn't fully solve the problem because it would not affect labels beyond the le and quantile labels. Plus there is still a small chance that some numbers could be formatted differently (if you change the Go version or the hardware platform or something).
First class numerical label value
We could introduce a type dimension to label values, allowing label values that are actually numbers. This would be the cleanest approach, but also a very involved one. It would work against the pragmatic simplicity of Prometheus and PromQL (all sample values are floats, all label values are strings).

Can I work on this issue?

We should first make a call if we want this feature. I'm torn myself, and I would love feedback from others.

I would rather have a relabeling action to normalize numbers in labels than touching PromQL. I think this is also how we should do 'Normalization on ingestion'.

A normalization relabel action sounds good to me. It would help normalize labels that are not le or quantile in a histogram or summary, respectively. However, it would still not solve the case which certain (non-round) numbers where normalization could still lead to varying results, and it would not allow "greater than" comparison etc. (I'm not saying that we have to support those cases, just wanted to clarify what part of the problem space are solved by a normalization relabeling action.)

A practical use case and unit test suggestion for the bucket "le" labels:
When we turn on native histograms feature, every classic histogram "le" label changes value where the number was a whole number. So if le="10" before, now it's le="10.0".  This is a problem for alerts, especially on RED metrics, since the increase/rate/irate functions don't produce correct values anymore.
Case in point, you can add this test:
# Text to OpenMetrics transition test
# Test histogram where half the samples are bellow 2.0 the other half is over.
# Thus quantile of 0.5 should be 2.0.
load 5m
	text2om_bucket{le="2"}	  0+1x5 _x5
	text2om_bucket{le="2.0"}  _ _x5 6+1x5
	text2om_bucket{le="4"}    0+2x5 _x5
	text2om_bucket{le="4.0"}  _ _x5 12+2x5
	text2om_bucket{le="+Inf"} 0+2x10

eval instant at 32m histogram_quantile(0.5, sum by (le) (increase(text2om_bucket[10m])))
	{} 2

But it fails:
error in eval histogram_quantile(0.5, sum by (le) (increase(text2om_bucket[10m]))) (line 262): expected 2 for {} but got NaN

Since increase will not see two samples for the buckets in the given time range. It's even worse if it does see values, because the old buckets will be seen to decrease (to 0).
The overall effect is that the user might get some false positive alerts or possible miss some alerts.

The new label matchers proposed here are actually not really helping with @krajorama 's use case. If you rate a range vector, the differently formatted le labels will really bite you, and the new label matchers don't help with that. That goes into the direction of the aggregation issue already mentioned above.
It amplifies the concerns I'm having anyway. So maybe we should focus indeed on making normalization configurable on scrape, which goes more into the direction of the relabel action @roidelapluie proposed. I'll try to write something up soon.

OK, see #12984 .

Thanks for all your feedback.
To come to some kind of preliminary conclusion:
The equality use case isn't really covered completely with the proposed "numerical equality label matcher" ({foo=="1.234"}). Series identity is wired much more deeply into PromQL, applying to the following aspects (and possibly more):

Aggregation: Something like sum by (foo) would also need a mode where it aggregates numerically equal labels into the same resulting time series. We could even come up with a syntax for this (sum by (foo==) or something), but we are getting deeper down the rabbit hole here.
Range selectors: {foo=="1.234"}[5m] would select by numerical equality, but functions consuming this range selector needed to be made aware of that, because the selected series would still look differently. Or the range selector needed to rewrite the different label values into one canonical form. While I could imagine this is a solvable problem, it is quite involved.

In sum, I think the equality issue is better solved with normalization upon ingestion, as proposed above. See also #12984 for more thoughts about it. It is essentially one know to turn, instead of a whole bunch of relatively complex additions and changes of PromQL as proposed in this issue. It should be noted, however, that the normalization upon ingestion might still run into the possible ambiguity in the case of many decimal places. The doesn't happen in practice with quantile labels because they are usually set manually with a limited number of decimal places (e.g. 0.5, 0.999) where the issue doesn't happen. With le, it could most plausibly happen with automatically set exponential bucket boundaries. But those are prime use cases for native histograms, where we don't have le labels anymore. Which leaves us with the niche case of numerical label values used for other (user-specific) reasons beyond le and quantile in histograms/summaries.
This proposal also contains a solution for "greater than"/"less than" comparison. The question is how often this is needed in practice.
Overall, this proposal is possibly an appropriate solution for rarely occurring niche cases (numerical label values with many decimal places on the one hand, and comparisons beyond simple equality on the other hand). My conclusion for now is that the limited scope of those niche use cases cannot justify the amount of complexity that comes with this proposal. Therefore, I close the issue, but we have it "on file" now and can revisit if we change our mind.


Make Facebook App Id Configurable

Resolves https://github.com/sqren/fb-sleep-stats/issues/5
Makes the app id configurable so that the developer can use their own facebook app.

Thanks!


MOBILE-150 MOBILE-151, MOBILE-188, MOBILE-198, MOBILE-191

@markyou  I'm able to run the build with recent updates locally -- uploads and works with a production account as expected. Looks good to go to QA 🦄


Show result when visiting match urls for completed or underway matches

Thanks! Fixed in https://github.com/sanity-io/squizzy/commit/6625455aadc159c48b01a8efd7ea7f5341ea8a84 😃


Module import is not retried if re-imported after an error

$ cat Lib/foo.py
bar

In CPython (3.7.0):
>>> import foo
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "Lib\foo.py", line 1, in <module>
    bar
NameError: name 'bar' is not defined
>>> import foo
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "Lib\foo.py", line 1, in <module>
    bar
NameError: name 'bar' is not defined

Importing the file for the 2nd time executes the file again, since the first execution resulted in an error.
In RustPython:
>>>>> import foo
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "Lib\foo.py", line 1, in <module>
NameError: name 'bar' is not defined
>>>>> import foo
>>>>> foo
<module object at 0x1b55fd39f70>
>>>>>

Module import apparently succeeded although an exception was encountered.
Actually, the more severe error here is that after the second import, the module is registered and a module object is created regardless of whether the import should have executed successfully or not.

fixed but untracked


Add link to user from team page

Users on the team page should be clickable and go to the user page.

Done


HashMap::get get old value which has been overrided by HashMap::insert operation.

First of all thanks for the great project,
I am developing a reverse proxy and using scc::HashMap to save all the rules (hostname as key, and upstream ip + upstream port as value), there are millions of it.
I found that when i override some existing key by HashMap::insert, the HashMap::get WILL NOT get the latest value, but the previous value which should have been overrided.
The rules object is created as a global static variable like bellow:
lazy_static! {
    pub static ref RULES: scc::HashMap<String, Arc<Upstream>> = scc::HashMap::new();
}

and my project is based on tokio,
Any ideas?

Hi! The semantics of scc::HashMap::insert differs from that of std::collections::HashMap::insert - it does not replace the old value. If you need similar semantics, please try scc::HashMap::upsert.

thanks! upsert is what i want, have to upgrade the crate to newest version though : )


JetBrains: Cody Agent consumes much CPU, even after quitting the IDE

I didn't have IntelliJ running when I took this screenshot:

Sounds like there are two bugs here:

they are hammering the CPU
they didn’t shut down

Clues from @SuperAuguste:

We intend to shut down the agent here, but looks like it doesn't happen.
Perhaps the message gets cut off (agent service dies before shutdown transaction completes), explaining the infinite read loop in the else waiting for the content length remaining to become zero

@tjdevries fixed this in https://github.com/sourcegraph/cody/pull/109 I believe :)

I'll close it


Pros & Cons: Space name unique vs. not unique

Feature Request
As a product manager
I would like to know the ramifications of making space name NOT unique
so that I can determine the best way to communicate the limitations of peoplemover naming conventions to our users
Acceptance Criteria
Have enough information on effort, benefits, & consequences to make a decision around:

continuing on current flow and keeping the space name unique (letting the user know when a name has been taken) OR
making the space name not unique (allowing several users create their own spaces with the same names)

Notes
What if user wants to edit the name of their space later on? How does that affect URL?

We decided that we will be making space names not unique and will be using some sort of guid in the url


Submission flow no consent keys Submission Screen (EXPOSUREAPP-4064)

Description
Submission Flow No Consent Keys Submission Screen
Steps to reproduce
The other UIs are being worked upon. once they're done you will be able to get to this screen after Ihr Testergibnis screen in No Consent Flow
Screenshot

Note:

Do not worry about the navigation from Submission keys to default thank you screen
The navigation will be changed while marrying the #1738
CountryList is not being retrieved in the current environment. that's why you don't see any list being populated there.

Navigation Flow
Submission Keys -> close button on top -> home screen
Submission Keys - > press Einverstanden - > Google ENF API prompt will show up -> can observe progressbar below - > Thank you screen once completed
TODO
Navigation to and from this screen. will be done in a seprate PR

CountryList is not being retrieved in the current environment. that's why you don't see any list being populated there.

Don't we have a default country in any case? E.g. Germany?

If I keep the environment as INT the default country comes up. weird that it's not in WRU-XD. I'll investigate.


Can't open files in WSL: The editor could not be opened due to an unexpected error

Type: Bug
I can no longer open any files inside of WSL. In the status bar in the lower left, I see "Disconnected from WSL" and while I see the directory I opened VSCode from in the tree (with no open/close widget and nothing under it), when I click on the dir name I get a pop-up saying "Unable to open " unable to resolve resource vscode-remote://
VS Code version: Code - Insiders 1.75.0-insider (f1b09237cd400d92987cf7a9681995e8011ef54c, 2023-01-23T11:53:59.088Z)
OS version: Windows_NT x64 10.0.22621
Modes: Restricted
Sandboxed: Yes
Connection to 'WSL: Debian' could not be established  No remote extension installed to resolve wsl.

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-10875H CPU @ 2.30GHz (16 x 2304)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
31.73GB (20.85GB free)

Process Argv
--folder-uri=vscode-remote://wsl+Debian/home/forrcaho/Amiggi/MetroNet/account-management-api --remote=wsl+Debian --crash-reporter-id 3d6bfcde-d3d0-4831-bc4c-120c572626da

Screen Reader
no

VM
0%

Connection to 'WSL: Debian' could not be established  No remote extension installed to resolve wsl.
Extensions: none

Fortunately, this is only a problem with Insiders.

here is issue: https://github.com/microsoft/vscode-remote-release/issues/7891

duplicate of https://github.com/microsoft/vscode-remote-release/issues/7891, fix is out


[WIP] Screenshot iframe2

In App Preview service that open iframe from the weba.online. weba.online uses the dashboard worker to point to the weba.com
It has it's own queuing systme and can use it based on the load.

Is this for https://github.com/webaverse/app/issues/1896 ?

Is this for #1896 ?

Yes it's for the same PR. it requires worker to be fixed for the QA testing.

We don't need to fiddle with CloudFlare Workers. If that's too hard, we can just start a server which will node-http-proxy and add the headers we need.

We don't need to fiddle with CloudFlare Workers. If that's too hard, we can just start a server which will node-http-proxy and add the headers we need.

Yeah exactly. But i made it work thanks to your proxy suggestion.


Timeout when using within_frame although iFrame seems to be loaded

I'm trying to use the following code to access an iFrame scope.
within_frame(find(:css, "iframe#z_hppm_iframe")) do
  # ...
end

And I'm getting (already tried using high timeout values):
Capybara::Poltergeist::TimeoutError:
       Timed out waiting for response to {"id":"9d43c2b8-81cb-44b7-8811-03ab7a5beea9","name":"push_frame","args":[[3,104]]}. It's possible that this happened because something took a very long time (for example a page load was slow). If so, setting the Poltergeist :timeout option to a higher value will help (see the docs for details). If increasing the timeout does not help, this is probably a bug in Poltergeist - please report it to the issue tracker.

Debug log seems to stop on push_frame step:
{"id":"22372385-d9f5-432a-887e-2094751cd99b","name":"find","args":["css","iframe#z_hppm_iframe"]}
{"command_id":"22372385-d9f5-432a-887e-2094751cd99b","response":{"page_id":3,"ids":[104]}}
{"id":"c216229c-8cb8-4082-8b6a-971e78c973b5","name":"visible","args":[3,104]}
{"command_id":"c216229c-8cb8-4082-8b6a-971e78c973b5","response":true}
{"id":"9d43c2b8-81cb-44b7-8811-03ab7a5beea9","name":"push_frame","args":[[3,104]]}

More information on the iFrame being loaded:

Obs.: When using save_and_open_page I can see that the iFrame is already loaded.
Tried on:

1.13
master

What version of Capybara and PhantomJS?

Thanks for the quick answer @twalpole! Capybara 2.13 and PhantomJS 2.1.1.

@oswaldoferreira This probably won't fix the issue, but just an FYI -- rather than using a find in within_frame you can just pass it the id of the frame you're looking for and it will use the :frame selector to locate it.
within_frame("z_hppm_iframe") do
  # ...
end

@oswaldoferreira  Does sleeping for a few seconds before calling within_frame make a difference?

Already tried using about 30 seconds, but no changes.
FYI, it's working on capybara-webkit 1.14.

@oswaldoferreira I haven't been able to replicate this, although from reading the code I would guess that either the frame page is requesting a resource that is hanging ( throttled, etc ) or there is a race condition in the page loading.  Could you turn on the phantomjs_options: ['--debug=true'] option in your driver registration and/or blacklist/whitelist the resources the page is requesting, and let me know if that provides any more info.

or (of course) a minimal reproducible example :)

@oswaldoferreira  I created a new 'frame_timeout' branch with debugging info around the frame changing code, please give it a try and let me know what it outputs

Closing due to lack of response, we will reopen if/when the requested info is provided.


Some details in mineagent RL implementation

Hello! I am reproducing your paper results (train PPO+self-imitation, with MineCLIP reward), but fail to fill some missing details:

How to implement the agent's 89 discrete actions as said in paper? Currently your MineAgent uses multi-discrete output 3*3*4*25*25*3, which is much larger. Did you remove some action choices？
For computing DIRECT reward using the MineCLIP model, how to sample the negative texts and how many did you sample?
I find the timescale of 1 step in MineDojo simulation is much smaller than 1 second in Youtube videos. Did you use the last consecutive 16 rgb observations to compute reward?

Thank you!

By the way, do you plan to release the training code, or the learned agent parameters?

@YHQpkueecs Were you able to get the learned agent parameters from @LinxiFan @wangguanzhi or @yunfanjiang


feat(manifests): add k8s readiness check

Adds a k8s readiness check to workflow, in addition to the existing liveness check.

Invoking the power of the name Matt to close this issue on @mboersma's behalf.


Research into possibility of Asyncio scraping

I want to scrap all products with asyncio because site very slow. Maybe site block that. Test and research needed.

Research ended, site accept only one request from one IP


Use more [[nodiscard]]

Description
These functions were not flagged by clang-tidy. I searched for patterns like functions that start with get or is and are marked as const. Others were found just by reading various header files looking for more unmarked functions. As it turns out a lot of our functions require using the return value. I think this is a good thing. I'd find it suspicious if we had a lot of functions with optional return values.
There are many, many private functions inside the src/ dir that could theoretically use [[nodiscard]] but I won't bother changing those since it would be a massive effort and offer relatively little marginal value. I plan on stopping the [[nodiscard]] work with the interface and therefore stop with this PR.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall first build on nodiscard at 55.763%

Totals

Change from base Build<PHONE_NUMBER>:
55.8%

Covered Lines:
11673

Relevant Lines:
19694

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.003%) to 55.732%

Totals

Change from base Build<PHONE_NUMBER>:
0.003%

Covered Lines:
11674

Relevant Lines:
19696

💛  - Coveralls


update tagui.cmd with secondary chrome location

Hi @siowyisheng for your review and test on Windows. Closing basecamp issue to follow-up here.

Somehow can't get this working. Even after removing the normal chrome directory and placing a working chrome in the new target directory, the script doesn't run. And it fails silently too.

Not sure how to proceed on this.

I'm guessing that this is expected behaviour, if your Chrome is not installed really installed in %LOCALAPPDATA% folder just moving the folder there may not let Chrome work, as other Windows registry info will still point to the old original location.
The code change for this PR adds below line to check if the original location is not found, it will change to point to below location. But maybe can't test unless we find a Windows laptop that Chrome is installed here.
if not exist "%chrome_command%" set chrome_command=%LOCALAPPDATA%\Google\Chrome\Application\chrome.exe

If can't have a Windows laptop with Chrome at this location to test, can you add another line below you tagui.cmd to echo the command to at least check if it is pointing to a correct new location?
if not exist "%chrome_command%" set chrome_command=%LOCALAPPDATA%\Google\Chrome\Application\chrome.exe
echo %chrome_command%

The secondary location seems to be at %LOCALAPPDATA%, from

https://superuser.com/questions/329112/where-are-the-user-profile-directories-of-google-chrome-located-in
https://superuser.com/questions/545351/install-google-chrome-to-appdata-local-google-chrome-application
https://stackoverflow.com/questions/40674914/google-chrome-path-in-windows-10

As long as after the change, the echo points to the correct secondary location, and that for Windows with Chrome in the original program files location work (for eg your laptop), then the PR should be ok to commit to develop.
You can do other checks if possible to see if Chrome is invoked in the secondary location, or if you try to invoke it manually from command line in the secondary location on your laptop, does it not invoke, in the same way as TagUI does.

it would need to be on windows 7 I think. That's where chrome is installed
at that path.
On Mon, Mar 2, 2020, 17:29 Ken Soh<EMAIL_ADDRESS>wrote:

I'm guessing that this is expected behaviour, if your Chrome is not
installed really installed in %LOCALAPPDATA% folder just moving the folder
there may not let Chrome work, as other Windows registry info will still
point to the old original location.
The code change for this PR adds below line to check if the original
location is not found, it will change to point to below location. But maybe
can't test unless we find a Windows laptop that Chrome is installed here.
if not exist "%chrome_command%" set chrome_command=%LOCALAPPDATA%\Google\Chrome\Application\chrome.exe
If can't have a Windows laptop with Chrome at this location to test, can
you add another line below you tagui.cmd to echo the command to at least
check if it is pointing to a correct new location?
if not exist "%chrome_command%" set chrome_command=%LOCALAPPDATA%\Google\Chrome\Application\chrome.exe
echo %chrome_command%
The secondary location seems to be at %LOCALAPPDATA%, from

https://superuser.com/questions/329112/where-are-the-user-profile-directories-of-google-chrome-located-in
https://superuser.com/questions/545351/install-google-chrome-to-appdata-local-google-chrome-application
https://stackoverflow.com/questions/40674914/google-chrome-path-in-windows-10
As long as after the change, the echo points to the correct secondary
location, and that for Windows with Chrome in the original program files
location work (for eg your laptop), then the PR should be ok to commit to
develop.
You can do other checks if possible to see if Chrome is invoked in the
secondary location, or if you try to invoke it manually from command line
in the secondary location on your laptop, does it not invoke, in the same
way as TagUI does.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kelaberetiv/TagUI/pull/732?email_source=notifications&email_token=AGB7JBBNDINE54AFZIBY2DTRFN36FA5CNFSM4KV7ANTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENOSIPA#issuecomment-593306684,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGB7JBG5BXWZS3XDJCTL3YTRFN36FANCNFSM4KV7ANTA
.

I see.. Do you think anyone in office has a Windows 7 computer to test?
Will be tricky to find, since AISG main hiring only started in 2018.

Will be difficult to find. Asked a few people but don't have.

I see, in that case 1 way to test whether this change works is you try to do an echo statement like the above example. If you moved Chrome to the fake folder and the echo statement shows the correct chrome.exe location, and if it is in original folder, it shows the original folder location, then the code change is working as intended.
The assumption is if the chrome.exe is in other folder calling the chrome.exe command should work. If that doesn't work it isn't really something TagUI can do anyway as that is some problem with Chrome installation in that folder that can't be invoked from command line. But in order to get feedback on whether that works, need to implement first.
I'm good with committing to develop branch and also committed to the fork I maintain. But closing the PR for now until you are comfortable to implement.

backup of the code changes in src\tagui.cmd before deleting branch -
rem configure default command location to launch Chrome on Windows
set chrome_command=C:\Program Files (x86)\Google\Chrome\Application\chrome.exe

rem fallback to backup location for some users who cannot install Chrome system-wide
if not exist "%chrome_command%" set chrome_command=%LOCALAPPDATA%\Google\Chrome\Application\chrome.exe

		echo ERROR - cannot find Chrome at "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe"
 		echo ERROR - or at user folder "%LOCALAPPDATA%\Google\Chrome\Application\chrome.exe"


Implement CreateOrUpdateNetworkContainerInternal API.

Added implementation for CreateOrUpdateNetworkContainerInternal. This will be called by the CNS requestController and it will handle SecondaryIpConfigs update which will add state for new Secondary ips and delete the state for any delta.

/azp run

/azp run


The config file about Cityscapes dataset

Thank you for sharing your code.
Can you share the config file on the Cityscapes dataset? I just achieved the PQ=58.9 via the default config with 8gpus.

hi @Shun14 . Is your learning schedule following default config or paper?

@Shun14 @hsfzxjy Please note that, as highlighted in the README, the parameters in the default configuration files are just an indication of what a "reasonable" value for each parameter could be, and are not meant as a way to reproduce any of the results from our paper.

@ducksoup would be great if you can share your config file for Cityscapes

@ducksoup Hi, Would you kindly share your config for Cityscapes for reproducing your results ?


ACCEPTANCES: Generate Image

The Ask
Develop an Acceptance test to verify Generating Images from Text components are working correctly
How to Complete this Task
Here's some steps to complete this deliverable.

Watch how The Standard Community developed a similar Acceptance Tests for OpenAI here
You cannot start working on this issue until #206 is completed and closed

How to claim this issue?

Post on this issue a comment that says: "I claim this issue"
You will be given 24 hours to complete the issue - if no PR is opened within 24 hours someone else will claim it
If you have an open PR but is inactive for more than 24 hours from the last review comment we will shutdown your PR

I claim this issue


add HeaderValue::from_shared_unchecked

The reason for wanting this is to prevent double parsing a header value. For example, in hyper, the bytes are parsed using httparse, which already verifies the header values do not contain illegal values.
There's a technicality issue here: it's not actually unsafe, according to Rust's strict definition of unsafe meaning memory unsafety. These bytes are never converted into a str without validating them first.
At the same time, it is totally unsafe in a HTTP context...

I assume that it is backwards compatible to remove the unsafe annotation in the future?

Removing it would cause any usage to trigger the unused_unsafe warning. That will fail locally if you have deny(warnings), but lints will never fail a build of a dependency.

Right, I think "backwards compatible" means that new warnings are permitted.


'cannot set property 'domain' of null'

Operation System: Mac OSX
Beaker Version: current version (can't get into beaker).
I am getting errors from electron when I attempt to open beaker.
The error was not allowing me to copy it but I got a screenshot of it:

Ah that's no good! Are you getting this from the last build release, or from building from source?

I was running from the last release, not from source. I had just restarted my computer and no windows were currently open.

Are you sure you're on the latest version? If you're not sure, could you try redownloading?
(This is a bug we've been battling with for a while, and this will help me figure out if it's still an issue or if you're just experiencing the old bug.)

I could not recreate the problem, although it could have been the result of a memory leak that it experienced prior to me restarting my computer. In case the console's log from the memory leak may help I will include it:
internal/process/warning.js:28 (node:18142) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 set-active listeners added. Use emitter.setMaxListeners() to increase limit

Nah that warning's about having a lot of event emitter handlers set.
This bug is basically something that electron does temperamentally. I've been trying to guard against it in Beaker's code, with varying levels of success. Going to close for now. If it happens again, please reopen!

We have one new recent report from our customer about this issue.
Electron version is 2.x
Tue Dec 04 2018 12:05:37 GMT-0500 (EST)    TypeError: Cannot set property 'domain' of null
at EventEmitter.init (events.js:63:15)
at EventEmitter (events.js:28:21)
at Object. (/Applications/Mitel Teamwork.app/Contents/Resources/electron.asar/browser/api/screen.js:7:14)
at Object. (/Applications/Mitel Teamwork.app/Contents/Resources/electron.asar/browser/api/screen.js:19:3)
at Module._compile (module.js:642:30)
at Object.Module._extensions..js (module.js:653:10)
at Module.load (module.js:561:32)
at tryModuleLoad (module.js:504:12)
at Function.Module._load (module.js:496:3)
at Module.require (module.js:586:17)


Add version dropdown to Doc-site global nav

Is your feature request related to a problem? Please describe.
As a Zarf user, I would like to be sure that the information I see in the docs matches the version of Zarf I am using.
Currently, The docs only show the most recent update;
If my system still uses an older version of Zarf,
then  I need a way to select and view that matches the version I am on.
Describe the solution you'd like
Add Version Drop Down to Top Nav. I looks like Docusaurus has this as a feature that can be turned on

[ ] Add version drop down to docusaurus site
[ ] For each major and minor update, add a new version to the dropdown for users

How many past versions should we support in dropdown? @Racer159
Describe alternatives you've considered
Waiting to add this feature until we hit v1.0 was mentioned, but i think we have enough users who are using the tool (not all using the most updated version) and need to be aware of differences based on the version that this is valuable.
Additional context
Issue carried over from deprecated docs-site repo
Design

Examples
https://hasura.io/docs/latest/graphql/core/index

Will be completed by moving docs over to the new Hugo theme


Add Redis functionality and library

🎯 Goal: - Add Redis to our flow and show how to use it properly. When querying for orders, we may cache an item in Redis for 1 minute. If it's already in the cache - we can serve it from there. If not, we try the DB and add to the cache (if found).
The deliverable constitutes (A) our own library that wraps a reputable redis client (B) Redis within our docker-compose (C) The change to the flow that were described above
🤔 Things to consider:

Library decision - We may need to carefully pick between reputable libraries like ioredis and node-redis
Create a wrapper library - Going with our existing architecture, the code is not approaching the redis client directly rather our own wrapper which itself is approaching the redis client (e.g., ioredis)
Tests our library
Prefer promisified version of clients
Ensure the Redis connection/pool is a 'singleton' (no connection is opened for every interaction)
Mind other Redis best practices, not necessarily in the 1st iteration

@goldbergyoni
Some questions:
If is a library cache.
1)What do you think about lru-cache in memory?
2)The library should export a middleware or a depency to be injected to some service ?

@marcosmol204 Handling Redis is a viable option, that said we have other priorities that should be addressed before caching. Shall I present you with a list of interesting contributions?

About lru - To my understanding, it's in-process cache which is not as useful and scalable as cross-process cache
The lib should expose a service that allows to set/get cache. It should not be coupled to Express (i.e. middleware)

You may see a POC here:
https://github.com/practicajs/practica/pull/173

@goldbergyoni Yes, you can present me good first issues with higher priorities.

@marcosmol204 Just got back from a trip, back on track
I would suggest one of these 3 issues:

https://github.com/practicajs/practica/issues/83
https://github.com/practicajs/practica/issues/144
https://github.com/practicajs/practica/issues/158

OR
Replicate our data-access layer using Prisma. We want to evaluate whether Prisma is a good option, hence we should create the same data access layer code using it and then compare Sequelize vs Prisma

I think this feature will create libary and inject into services or controller before it get from DB. Should not be included as middleware will make the data in the general cache and if the data changes frequently, it is almost unusable.


Add quick create feature in the navbar

🚀 Feature Proposal
In the top right of the navbar, there should should be a feature that allows me to quickly navigate to create pages that I have access to do.
Technical Notes

Icon should be the add icon from @hospitalrun/components
Options should be listed in the same order as the sidebar
Only options that I have access to view should show up

PR is ready for your review. Thank you. https://github.com/HospitalRun/hospitalrun-frontend/pull/2108


Proposal: How to do concurrency access?

Well, LiteDb must improve concurrency access in datafile to be more safe (avoiding corruped data). So my idea is implement a solid and simple solution to v2.

No more thread-safe. It's a little complicate handle with that. Keep as v1 version and be only "process safe".
Back transaction operations.

How will work concurrency in v2:

Datafile will be opened in READONLY shared support. So, can have multiple read only connections at same time.
All write operations will be inside a transaction.
Begin transaction will try open file as WRITE exclusive operation. No one can write/read data file until Commit/Rollback.
Cached pages will be clear after any read (non-transaction) operation (non-dirty). Avoid concurrency changes between run queries.
Transaction operations (read/write) will keep cached pages (or journal file with more than 5000 pages in memory) until end transaction. At end of transaction, clear all pages (dirty and non-dirty).
All this operations will works only with FileDiskServices na EncryptedDiskService. StreamDiskService will be to single-connection only.

Did you enjoy LiteDB and have any suggestion about that? Please, comment here.

I think this sounds good, simple and clear.

I agree - it will support my LiteDB usage perfectly.
In the meantime, I'm going to wrap all usages with a (machine) global mutex to guarantee concurrency/stability; - I'll take the performance hit for now.

good job, but i can't wait for new 2.0 stable ver.You know I've been pulling for you.

Yes please. Concurrency safety should come first. Right now we are in 2.0RC and are syncing across the public API surface. I'd rather have the sync granularity on a transactional basis.

I just found LiteDB. Great project!
All locking seems to be based on file locking. I was wondering how locking works when you're writing to custom streams instead of file streams. With 2.0, is it possible to delegate locking to some custom object?


stash

cipher on e2e.  very open

Coverage remained the same at 49.95% when pulling<PHONE_NUMBER>114c9795d3ff0de692f07f16ab8c30 on kulicuu:e2e into fc2dc8ea32d6e47a2df32e4866a69b36146a4725 on socketstream:master.


[release-2.7] Trigger rebuild to pick up base OS CVE fixes

Signed-off-by: Subbarao Meduri<EMAIL_ADDRESS>

/lgtm


Grpc Conversion issue from RepeatedCompositeContainer to dict

Hi,  I have question to ask regarding grpc  about this RepeatedCompositeContainer
I have write this code
The user.result has the data in the format of  RepeatedCompositeContainer
convert_dict = MessageToDict(user.results, descriptor_pool=True)
This is throwing me error  "question google._upb._message.RepeatedCompositeContainer' object has no attribute 'file'"
I want to convert RepeatedCompositeContainer into the dict and this is throwing me error as you see
Please help me out with this.

I might be wrong, but this issue seems only related to Protobuf and upb, please add more details if you think it's related to grpc.


Fluentbit Container Update

Description
What:
Why:
When:
Where:
Tasks

[ ]
[ ]
[ ]
[ ]
[ ]

Acceptance Criteria

Constraints

N/A

References:

References #16

Closing as duplicate of #284.

Closing as duplicate of #284.


UK authority data source changed API/death processing

RuntimeError: Request failed: {"response":"Invalid parameter 'newDeathsByPublishDate' in the requested JSON structure. Did you mean 'newTestsByPublishDate'?","status_code":404,"status":"Not Found"}
at _get (/env/lib/python3.7/site-packages/uk_covid19/api_interface.py:226)
at get_json (/env/lib/python3.7/site-packages/uk_covid19/api_interface.py:278)
at parse (/home/vmagent/app/pipelines/epidemiology/gb_authority.py:102)
at parse (/home/vmagent/app/pipelines/epidemiology/gb_authority.py:131)
at run (/home/vmagent/app/lib/data_source.py:226)
at _run_wrapper (/home/vmagent/app/lib/pipeline.py:164)

The UK govt is changing the way they report deaths. From the official document (https://assets.publishing.service.gov.uk/government/uploads/system/uploads/attachment_data/file/908781/Technical_Summary_PHE_Data_Series_COVID-19_Deaths_20200812.pdf)

There are 2 definitions of a death in a person with COVID-19 in England, one
broader measure and one measure reflecting current trends:

A death in a person with a laboratory-confirmed positive COVID-19 test and
either died within 60 days of the first specimen date or died more than 60 days
after the first specimen date, only if COVID-19 is mentioned on the death
certificate
A death in a person with a laboratory-confirmed positive COVID-19 test and
died within (equal to or less than) 28 days of the first positive specimen date
c. A measure of acute deaths which can be used to understand current trends is
further defined as a “a death in any person with a laboratory-confirmed positive
COVID-19 test AND within (equal to or less than) 28 days of the first positive
specimen date.

Unfortunately they already changed the API.

I propose that we use the broader definition (60 days) rather than the "acute" definition. @owahltinez what do you think?

What definition is being used to report aggregated numbers, e.g. to the WHO or the ECDC?

Apparently neither - "The WHO recommendation is to report on death certification, which England will continue to do through the ONS. For daily reported death figures, there is no international consensus on methods."

Unfortunately the ONS only reports weekly.

I see. I don't feel strongly about either metric, my preference is to use whichever gets us "closer" to the number of deaths reported through the ONS.

It looks like the 60days version does not work through the API - in order to continue reporting I'm moving to the 28 days version. It's also what is now reported on the official website - https://coronavirus.data.gov.uk/


feat: Adds keepends option to iter_lines in StreamingResponse

This PR aims to add an optional keepends parameter to the iter_lines in StreamingResponse
From the python documentation readline and readlines should keep new line characters at the end of the string:

f.readline() reads a single line from the file; a newline character (\n) is left at the end of the string, and is only omitted on the last line of the file if the file doesn’t end in a newline.

See https://docs.python.org/3/tutorial/inputoutput.html#methods-of-file-objects
Adding this option would make it easier to get this behavior for classes relying on StreamingResponse.
To not break the current implementation, this parameter is set to False by default.

Codecov Report

Merging #2235 (6eb6109) into develop (034d5d1) will decrease coverage by 0.42%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           develop    #2235      +/-   ##
===========================================
- Coverage    98.25%   97.83%   -0.43%
===========================================
  Files           58       58
  Lines        10857    10857
===========================================
- Hits         10668    10622      -46
- Misses         189      235      +46

Impacted Files
Coverage Δ

botocore/response.py
92.64% <100.00%> (ø)

botocore/compat.py
72.15% <0.00%> (-22.16%)
:arrow_down:

botocore/hooks.py
95.18% <0.00%> (-0.81%)
:arrow_down:

botocore/httpsession.py
92.48% <0.00%> (-0.58%)
:arrow_down:

botocore/awsrequest.py
97.22% <0.00%> (-0.35%)
:arrow_down:

botocore/utils.py
97.55% <0.00%> (-0.19%)
:arrow_down:

botocore/credentials.py
98.54% <0.00%> (-0.11%)
: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 034d5d1...6eb6109. Read the comment docs.


is_installed fails in a RpmPackage that has dpkg installed

I'm testing a CentOS system and after installing dpkg package in that system, testinfra tests fail for all packages.
Looking at the code
    @classmethod
    def get_module_class(cls, host):
        if host.system_info.type == 'windows':
            return ChocolateyPackage
        if host.system_info.type == "freebsd":
            return FreeBSDPackage
        if host.system_info.type in ("openbsd", "netbsd"):
            return OpenBSDPackage
        if host.exists("dpkg-query"):
            return DebianPackage
        if host.exists("rpm"):
            return RpmPackage
        if host.exists("apk"):
            return AlpinePackage
        if host.system_info.distribution == "arch":
            return ArchPackage
        raise NotImplementedError

I can see that instead of deciding the Package class on system_info.distribution the decision to use dpkg is based solely in its presence.
How to reproduce
In a CentOS host, install dpkg package and check for any package host.package("kernel").is_installed
(Pdb) host.package("kernel").version
*** AssertionError: Unexpected exit code 127 for CommandResult(command=b"dpkg-query -f '${Status} ${Version}' -W munge", exit_status=127, stdout=None, stderr=b"Warning: Permanently added '<IP_ADDRESS>' (ED25519) to the list of known hosts.\r\nbash: dpkg-query: command not found\n")
assert 127 == 0

This is how I've fixed. Unfortunately, right now I don't have the bandwidth to submit a merge request. :/
...
        if host.system_info.distribution in ("debian","ubuntu"):
            return DebianPackage
        if host.system_info.distribution in ("centos"):
            return RpmPackage
...


Initial project setup

resolve #2

For the yarn test as it seems it's just a deprecation warning, and also this is just a dummy test file so for the future tests we will use the mentioned function createRoot.
As the coverage folder is auto generated by jest, we thought there is no need to include it.

For the yarn test as it seems it's just a deprecation warning, and also this is just a dummy test file so for the future tests we will use the mentioned function createRoot.
As the coverage folder is auto generated by jest, we thought there is no need to include it.

OK, we will make a separate issue for it.

For the yarn test as it seems it's just a deprecation warning, and also this is just a dummy test file so for the future tests we will use the mentioned function createRoot.
As the coverage folder is auto generated by jest, we thought there is no need to include it.

OK, we will create a seperate issue for it

@atwfk @AhmedAdel999 prettier is not running on pre-commit

we will keep testing, automate workflow with commitlint, husky and prettier config in another  issue.

@elhaw @ahmedkhitaby
I just tested prettier and commit lint and both works fine with me as you see in the screenshots
please try these steps:

write yarn to install all the dependence
go to .prettierrc file and set "semi": "false" instead of true
go to src/index.tsx and just save the file to reflect the new format
go to .prettierrc again and reset "semi" to true again
write in your terminal git add . and lint-staged

@elhaw @ahmedkhitaby I just tested prettier and commit lint and both works fine for me as you see in the screenshots
please try these steps:

write yarn to install all the dependence
go to .prettierrc file and set "semi": "false" instead of true
go to src/index.tsx and just save the file to reflect the new format
go to .prettierrc again and reset "semi" to true again
write in your terminal git add . and lint-staged

Yes, configurations works fine. but some issue while running git commit -m "some message"


count-words in all-the-icons-region-info is slow

According to the profiler, the use of count-words in spaceline-all-the-icons is slow. The only place I could find this being used was the region info and unfortunately there's no way to turn it off. I'm quite happy to trade off word count in a region for speed.

For reasons I don't understand, this is significantly worse (bordering on unusable) when selecting a region of Python imports.
Would you be willing to make this feature customizable?

You can disable the entire segment if you don't want to use it with
(spaceline-toggle-all-the-icons-region-info-off)

But if you'd still like something to indicate that the region is active, let me know and I'll update this :)

Thanks, @domtronn, I didn't see that command. For my needs it's perfectly fine to turn off the region info altogether.


blog post: how to fork via ganache, mint + use Dai, etc

Have begun work here: https://medium.com/p/d8b62a82b3f7/edit

Published! https://medium.com/ethereum-grid/forking-ethereum-mainnet-mint-your-own-dai-d8b62a82b3f7


Add WINPR_ONLY build option to build WinPR separately from FreeRDP

This pull request includes various cmake build system changes along with internal refactoring of OpenSSL/mbedTLS function structures to allow building WinPR against mbedTLS separately from FreeRDP (still using OpenSSL). While OpenSSL is still required for FreeRDP, we have been using WinPR mbedTLS builds for years on our side for multiple projects other than FreeRDP, and our FreeRDP builds are linked against the same prebuilt WinPR library that links against mbedTLS.
I've been very cautious with these changes, they should have no impact on the existing build options. Another option that was added is WITH_WINPR_TOOLS to turn off the WinPR tools like such as makecert that were never ported to mbedTLS.

I have another more general remark, isn't it the sign that winPR should move to its own repo, and FreeRDP would depend on it just like any other external dependency ?

Sorry, the whole crypto/ssl part should not be part of this.
We try to move this kind of dependency to winpr, not the other way around.

That is simply not possible, because FreeRDP and WinPR currently share common OpenSSL crypto utils, and the only way to build FreeRDP and WinPR against a separate crypto library is to split those utils (one for FreeRDP, one for WinPR). In other words, I just cannot make a simple PR that does nothing more than edit the cmake files, the end result wouldn't even build and run.
FreeRDP still has a direct dependency on OpenSSL, and abstracting it all away to move it down to WinPR would be serious refactoring to the TLS and TS Gateway code. If we move it down to WinPR, it wouldn't feel much like a Windows API unless we make an SChannel interface, and that is probably not what we want, even if we already have the stubs in libwinpr-sspi.

I have another more general remark, isn't it the sign that winPR should move to its own repo, and FreeRDP would depend on it just like any other external dependency ?

I thought about it, and FreeRDP is already complex enough as it is. Moving WinPR to a separate repo would often mean making pull requests in both repos at the same time, a lot of the fixes being done have to touch both FreeRDP and WinPR sides. I am using WinPR in two other internal projects at Devolutions, but since I prebuild it separately, it is not much of an issue. Making it possible to build WinPR only inside the same FreeRDP build system is the solution that is the least painful for everyone.

@freerdp-bot test

@akallabeth @hardening as discussed on IRC, we want to take baby steps here, and the last thing I want is to make this initial FreeRDP/WinPR separation more than what it should be. We can consider removing the OpenSSL dependency in FreeRDP later, and I don't think we need to plan to move WinPR outside of the FreeRDP repository, because it would make FreeRDP development much harder by having to make a lot of commits in two separate repositories.
However, I would appreciate if we could get this PR moving promptly this week, as it is a very important change that we need on side to get back in sync with the FreeRDP upstream sources.

@freerdp-bot test

@akallabeth that is what I had initially attempted, only to realize the sheer amount of cmake duplication it would require to build correctly. Since I didn't intend to split repositories (and still don't) the path of least disturbance was to keep using the FreeRDP parent cmake build system but add a WINPR_ONLY option in it. If this is what you truly want anyway, I would still recommend we do it in a second PR after this one to reduce the size of individual PRs.

@awakecoding there is not that much duplication (config.h, build-flags.h files maybe) but the build procedure must change. See #7082 which is not ready yet.


Adjusted close price

It seems that the output price dataframe does not include the "adj. close" column from Yahoo Finance (or am I missing it somewhere?). As mentiond in the Yahoo Finance footnote:
"Close price adjusted for splits. Adjusted close price adjusted for splits and dividend and/or capital gain distributions."
So the adjusted close is more critical in some, if not most, cases.

Hi @codeterm, thanks for raising the issue.
I could probably add an option to the PricesYahoo constructor, adj_close: bool = False, where setting it to True would return the close prices as the 'adj_close'.
Would that work for you?

Hi @maread99, yes, I think that's the perfect way to do it. Thanks!

Am I right in thinking this is only relevant when the interval is daily or a multiple of days?

Am I right in thinking this is only relevant when the interval is daily or a multiple of days?

yes, I think for purely intraday data (within a single day) it is irrelevant.

@codeterm, implemented by #118 which has just been merged.
To use the adjusted close prices just pass the new adj_close parameter to PricesYahoo as True (default is False).
The functionality will be available if you install from the master (I wasn't planning on publishing a new release to PyPI any time soon).
Any problems, let me know.
Cheers

thanks a lot!


Suggestion on time picker

Is your feature request related to a problem? Please describe.
Although your current time picker (the one where the clock is painted and you click arrows) might seem pretty, I'd say it can be a bit not intuitive for some users to use (especially non computer savvy ones).
Describe the solution you'd like
I'd suggest just as an alternative to also additionally provide other kinds of time pickers, like this for example:

Although it may not look as pretty as your approach, I think you would agree it is much easier and straightforward for users to use and grasp.

Duplicate of #1860


[Translations] Chips.Removable: Remove translations-prop (partly reverts #3232)

Description
We decided not having a translation-prop after all. No one was using removeLabel, so we will deprecate/remove it when i18n-provider is made available.
Component Checklist 📝

[x] JSDoc
[x] Examples
[x] Documentation
[x] Storybook
[x] Style mappings (@navikt/core/css/config/_mappings.js)
[x] Component tokens (@navikt/core/css/tokens.json)
[x] CSS class deprecations (@navikt/aksel-stylelint/src/deprecations.ts)
[x] Exports (@navikt/core/react/src/index.ts and @navikt/core/react/package.json)
[x] New component? CSS import (@navikt/core/css/index.css)
[x] Breaking change? Update migration guide. Consider codemod.
[x] Changeset (Format: <Component>: <gitmoji?> <Text>. E.g. "Button: :sparkles: Add feature xyz.")

There was a bug, but not in Storybook afaics. My local TypeScript server had a hiccup 😅


Incompatible with VS Code 1.57.1 in MacOs

When I install Jupyter Power Tools v0.0.4, VS Code noticed "Jupyter Power Tools extension is incompatible with VS Code (version 1.57.1)".
OS: MacOs Big Sur 11.4
VS Code: 1.57.1
Jupyter Power Tools: v0.0.4
Jupyter core: 4.7.1
Jupyter-notebook: 6.4.0
Python: 3.8.10
Date: 2021-06-29 22:09:21

Hi, same here but on Windows 10 :
VSCode 1.60.0 (2021-09-01)
Jupyter extension v2021.8.2041215044
Python is evolving blazingly fast on vscode :-)


menu菜单，子菜单较多，内嵌菜单被缩起，鼠标移到一级菜单的图标时，子菜单显示不全

Reproduction link
https://stackblitz.com/edit/angular-anuxrh?file=src/app/app.component.ts
Steps to reproduce
点击收缩图标，缩起后，鼠标移到第一个用户图标上面即可重现
What is expected?
被缩起时，子菜单太多，能出现滚动条，和菜单列展开效果一样
What is actually happening?
被缩起时，子菜单太多，看不全

Environment
Info

ng-zorro-antd
7.5.1

Browser
谷歌

This issue has been closed due to inactivity.
Please file a new issue or discussion if you are encountering a similar or related problem.


⚖ Register Validator:

Network Choice
nemeton-1
Who are you?
AviaOne 🟢 is  a Validator on more than 10 mainnets.
We are specialized in the Cosmos ecosystem and tendermint and proud to valid for OKP4.
gentx
{"body":{"messages":[{"@type":"/cosmos.staking.v1beta1.MsgCreateValidator","description":{"moniker":"AVIAONE 🟢","identity":"DCD3D6C0BF61C200","website":"https://aviaone.com","security_contact":"","details":"Retain ownership of your tokens and earn money  with us 👍. Join the winner team 🏆 in the best safety conditions without any risk for your money"},"commission":{"rate":"0.050000000000000000","max_rate":"0.200000000000000000","max_change_rate":"0.020000000000000000"},"min_self_delegation":"1","delegator_address":"okp417x0ewz3gwwk52eeryhg89q6g0zknpwlm8pvw7p","validator_address":"okp4valoper17x0ewz3gwwk52eeryhg89q6g0zknpwlmjxu8qq","pubkey":{"@type":"/cosmos.crypto.ed25519.PubKey","key":"y3ADhmbQDdqhkRyYgomC+9IqDuelNrU62QbYdWa3jBc="},"value":{"denom":"uknow","amount":"10000000000"}}],"memo":"867eb2870a5553360887d5ac1ed6922828f05e0e@<IP_ADDRESS>:26656","timeout_height":"0","extension_options":[],"non_critical_extension_options":[]},"auth_info":{"signer_infos":[{"public_key":{"@type":"/cosmos.crypto.secp256k1.PubKey","key":"A/wg2H9+JhO/sd9jFpkBYUXPX8TtZ1efcB4quV0mtCt0"},"mode_info":{"single":{"mode":"SIGN_MODE_DIRECT"}},"sequence":"0"}],"fee":{"amount":[],"gas_limit":"200000","payer":"","granter":""},"tip":null},"signatures":["yGePXIFKyAdiNvzNPRL2rltx1MqbuMuBzBDx+3IaP4kwf5HQMFsi2Z4+fUA+hDMyvvKs8T3FXuC6p6kWoFMoRg=="]}

😉 Here is the corresponding PR: https://github.com/okp4/networks/pull/289


Look forward to exposing your GMMsegcode

Closed as the full code has been released. Please feel free to reopen this thread if you have any further questions or need assistance.


Exclude archived pages from PDF exports

Short description
Exclude archived pages from PDF exports
Proposed changes

check if paghe is archived before adding it to list of to-be-exported pages

Side effects

none

Resolved issues

Fixes: #1800

Pull Request Review Guidelines

Looks good IMHO and we should merge this sooner than later. I have not looked into PDF tests yet, but if we could add some sort of test for this it would probably be a very good idea.

Looks good IMHO and we should merge this sooner than later. I have not looked into PDF tests yet, but if we could add some sort of test for this it would probably be a very good idea.

Agreed, but I don't see a quick way of doing this, at least not today.
I could add an archived page to an existing test, but not sure how meaningful that would be? Is it OK with you to if we put this off for now?

I could add an archived page to an existing test, but not sure how meaningful that would be? Is it OK with you to if we put this off for now?

I'd say the change is trivial enough that we don't need a test now - we can just keep it in mind for the future.


impala: add LDAP authentication

See https://community.plot.ly/t/error-read-econnreset-cannot-to-impala-via-falcon-sql-client/7686
This request would require contributing to node-impala (see https://github.com/ufukomer/node-impala/issues/17).

Hey Guys,
It would be great to know the status of this issue. Please let us know when this issue resolved.

@logicsandeep There is no one working on this issue (mostly because this is actually an enhancement request for node-impala). I'm tagging this issue as community, so that people know that help will be appreciated.

I believe this is a very important requirement. I can't think of people connecting to impala with out a username/password. It would be great if this issue is prioritized.

It would be great if this issue is prioritized.

If you would like particular features built that aren't in the roadmap, your company or organization can sponsor them through Plotly's Advanced Development team: https://plot.ly/products/consulting-and-oem/

@chriddyp : We consider this secure connections a core feature for a reporting platform.  For our Hadoop-based warehouse platform (https://github.com/servinglynk/hmis-lynk-open-source), that would mean either support for secure Hive or secure Impala connections.  We do not have funds available to support development of those features, since we are committed to our core features.  But, we would love to be able to recommend your product as our default open source reporting tool, if this feature were included in Falcon.  cc: @logicsandeep


Extension document doesn't update after extension version change

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.62.1
OS Version: macOS 11.6 (20G165)

Steps to Reproduce:

Use “Install Another Version…” from the context menu
Choose a previous version

The document does not update until another extension is selected and the extension is selected again.

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.
If you wonder what we are up to, please see our roadmap and issue reporting guidelines.
Thanks for your understanding, and happy coding!

Thanks for verifying that this issue was fixed.


Next.js 12 support?

I am trying to add this project to an existing Next.js 12 site but it fails because next-drupal defines its next dependency requirement as "next": "^11.0.0".  Will Next.js 12 be supported at some point?  If so, is there an ETA?

Next.js 12 is supported. I'll update the peer dependencies. Thanks for heads up.

:+1:


Add histogram stats

This information is necessary for auto-pagination on non-uuid fields, and collaterally could make cost estimation more accurate.
When naming these functions, i considered other names that didn't work out as well:

histogram: This is not a statistical term, but a visualization method.
percentile: More widely known than quantile, but implies we use percents.

Looks good mostly nits.


New rebus

Associated Issue: #
Summary of Changes

change 1
change 2

Pull Request Test Coverage Report for Build 766

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 87.143%

Totals

Change from base Build 514:
0.0%

Covered Lines:
158

Relevant Lines:
180

💛  - Coveralls


⚠ Bofrost.at has degraded performance

In 13efdaa, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 832 ms

Resolved: Bofrost.at performance has improved in 740ac3d.


Error: "url" could not be found

I've been working to update AFJ in the Cardea-Mobile-Holder app. When I attempt to use "0.1.0-alpha.269" I encounter the following error:

When I remove the "url" line from node_modules, or update to "0.1.0-alpha.273" then I instead encounter this error:

This isn't an error I encountered prior to updating. I'm not 100% sure AFJ is causing it, but it seems like newer versions of AFJ might not mesh well with Hermes.

@blu3beri Could the problem be that hermes doesn't support TextDecoder (which may be used (indirectly) by query-string?)

@blu3beri Could the problem be that hermes doesn't support TextDecoder (which may be used (indirectly) by query-string?)

I do think that that is the issue. However I checked all the dependencies of query-string and they don't seem to depend on anything or use TextDecoder themselves. So I am curious where it comes from.
We did not introduce any new dependencies or updates to afj core / rn ?

@seajensen could you run it again on version 270

Unfortunately this hasn't fixed the issue--thanks for your help digging into it. 😄

@seajensen could you run it again on version 270

Unfortunately this hasn't fixed the issue--thanks for your help digging into it. 😄

Ah that is too bad. I think I will just do the parsing like before. It should suffice.

Hmmm this might be an us problem? I just tried version 264, I'm not super sure what version of the code it corresponds to, but it's older than your URL changes, so this issue may be unrelated.

After some further investigation we finally identified that the metro bundler config didn't get the inlineRequires to be set to true as part of a RN upgrade, and we had a duplicate import that was also throwing in problems.
Sorry for the false alarm, I appreciate the help looking into it.


Cannot load gem in version 1.1.0

When using the gem with version 1.1.0 (just got a Dependabot PR), require "idempo" fails with:
/drone/src/vendor/bundle/ruby/3.3.0/gems/idempo-1.1.0/lib/idempo/active_record_backend.rb:2:in `<main>': uninitialized constant Idempo (NameError)

class Idempo::ActiveRecordBackend

That's because the order of the require statements was changed - I guess require "idempo/version" should still come first.
Was this a standardrb thing? In this case, the alternative would be to nest the modules instead of defining classes with the shortcut class Idempo::ActiveRecordBackend syntax. Happy to send a PR if you tell me which version you prefer. 😉

Good catch! Yes, please do send a PR. What do you mean by "which version"? what should we bump the gem version to? If that, I will take care of it and it will likely be a patch version bump 🙏

Actually - come to think of it, maybe we should use autoload for the various backends? This would allow people not to load code they never use.

Happy to send a PR if you tell me which version you prefer.

I was asking which of the two alternatives I should implement. But you already fixed it, great!
Thanks! And also for inviting me to the repo. 🤗


modify copy resource message

Modify copy resource message to only log error when required subresource size is less than the actual subresource size and log debug message if required subresource size is greater than the actual subresource size

Author jirongjiao not on autobuild list. Waiting for curator authorization before starting CI build.

CI gfxreconstruct build queued with queue ID 249550.

CI gfxreconstruct build # 4761 passed.


[issue-2116] - Add target property to MlModel

Describe your changes :

This PR fixes https://github.com/open-metadata/OpenMetadata/issues/2116.
As we are already tracking mlFeatures we should add as well the target property to MlModel for supervised ML algorithms.
Thanks! Happy to discuss 🙏

⚠  I updated the ingestion-core publishing workflow with pull_request_target to have it work with forks. Please, ignore the failure in this PR, but we should then publish it manually to not lose the changes. If it is easier for you all, I can prepare a separate PR updating the CI that we can merge before this one. Thanks!

Type of change :

[ ] Bug fix
[ ] Improvement
[x] New feature
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation

Frontend Preview (Screenshots) :
For frontend related change, please link screenshots of your changes preview! Optional for backend related changes.

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] I have performed a self-review of my own.
[ ] I have tagged my reviewers below.
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] My changes generate no new warnings.
[ ] I have added tests that prove my fix is effective or that my feature works.
[x] All new and existing tests passed.

Reviewers

@sureshms @harshach

Hi, @akash-jain-10! Took a spin on the ingestion-core docs and setup. I actually wanted to test the CI bump message on this PR but I guess it did not run here because the PR was already opened.
However, it already gave me the chance to test the process, so I unified a bit the install approach we had on ingestion.
Thanks!


Implement QPACK dynamic table

Motivation
We should support QPACK dynamic tables.
Modification
Implementation for QPACK dynamic table.
Result
QPACK now supports dynamic table.

@normanmaurer fyi; blocked streams and duplicate support is already added. I am working on some more tests but seems like it works 🤪
The h3spec tests are failing as establishing encoder/decoder streams sometimes take time and the delay is something that h3spec does not seem to like. I will try a few things to see how to address this properly.

@NiteshKant maybe consider adding an issue to the h3spec issue tracker and explain the problem ? https://github.com/kazu-yamamoto/h3spec

@NiteshKant also I wonder if this already will fix your problem: https://github.com/kazu-yamamoto/h3spec/commit/fdf9e6249ffba79ac8ea8913eef198e5f13a8987 ?

@normanmaurer plz hold off on further review till I exit draft status

@normanmaurer this is ready now for the review!


Access current workdir from inside log_handler

Is your feature request related to a problem? Please describe.
I am trying to create a custom log_handler that can save the workflow´s log as a JSON file in {workdir}/logs.
However, I cannot seem to access workdir.
Describe the solution you'd like
I'd like to be able to access workdir from inside log_handler, so that I can save the JSON file inside the workdir, e.g.:
LOG_FILE = open(Path(workdir) / "logs/log.json", "w", encoding = "utf-8")

Describe alternatives you've considered
I have also tried using Path.cwd() to get current working dir, but that is not set to snakemake's workdir.

I think questions about usage are better asked on stackoverflow. I'm not sure what you mean by {workdir} (in fact an example would help...). If you want to access the directory where snakemake is executed, as opposed to the directory set by-d/--directory or the current directory, then you can use the object workflow:
rule one:
    log:
        os.path.join(workflow.basedir, 'logs/log.json'),
    run:
        fin = open(os.path.join(workflow.basedir, 'foo.txt'), 'w')

I think in recent versions of snakemake there are better alternatives to querying workflow but I cannot find them now...

For workdir I mean the folder that snakemake uses as cwd (example here).
However, I'd like to access that variable from inside the log_handler script, not from inside the workflow.
https://snakemake.readthedocs.io/en/stable/_modules/snakemake/logging.html
PS - I can also port it on StackOverflow.


Disable warning for rename function on Swift_FileSpool class

Q
A

Bug fix?
yes

New feature?
no

Doc update?
no

BC breaks?
no

Deprecations?
no

Fixed tickets
#...

License
MIT

I disabled the warning of the native rename function (FileSpool.php line 166) because in a scenario where several workers are allocated to process spool messages, the function in question returns a warning because the file could be processed by another process (another worker)
PHP Warning:  rename(/srv/app/var/spool/foo/uyhkfPBqqP.messagetototo,/srv/app/var/spool/foo/uyhkfPBqqP.message.sending): No such file or directory in /srv/app/vendor/swiftmailer/swiftmailer/lib/classes/Swift/FileSpool.php on line 166

Thanks for the PR. As announced some time ago, Swiftmailer is not maintained anymore.
Symfony Mailer is the next evolution of Swiftmailer.
It provides the same features with support for modern PHP code and support for third-party providers.


MacOsX

Is your package is compatible with Mac ? Is thes is under active development ? do i need to install the pygames / piglet also ? what are the dependencies to connect it to the game and opencv ?
Do i require gamepad ? what are Gamepads alternatives for MacOSx ? as the mentioned game pads are not available for mac. Please guide

It is compatible with Mac for keyboard and mouse so far. If I remember rightly, some gamepads come through as keyboards on the mac, not sure about the rest. If you find out more, please let me know.
This is (again) under active development.


ConfigContext data migration and make sure the SiteLocationType.content_types is set to allow all Location ContentTypes

Closes: N/A
What's Changed

Migrate ConfigContext regions and sites data to ConfigContext.locations.
Ensure the new "Site" LocationType allows all ContentTypes allowed by Location (FeatureQuery("locations").get_query()).
Tested thoroughly and did what it was intended.

TODO

[ ] Explanation of Change(s)
[ ] Added change log fragment(s) (for more information see the documentation)
[ ] Attached Screenshots, Payload Example
[ ] Unit, Integration Tests
[ ] Documentation Updates (when adding/changing features)
[ ] Example Plugin Updates (when adding/changing features)
[ ] Outline Remaining Work, Constraints from Design

See https://github.com/nautobot/nautobot/pull/3208#discussion_r1095829166 for more migrations we need to do in this PR


Upgrade to Elastic 7.14.0

Hi,
Elastic 7.14 is available.
Many change to security :fireworks:
So can you add to the short roadmap .
Thanks

I will update to ELK 7.14.0

Issue can be closed this commit upgrade ELK to 7.14.1 https://github.com/V1D1AN/S1EM/commit/1dcae1fea133f51bbca01ec1f9f123272072b9a7


Tensorflow unstable?

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 16.04 with Tensorflow 1.8 nad ROCm 1.9
GPU model and memory: Radeon RX 480

Describe the problem
I previously had the same MIOpen Error as in Issue #93 and Issue #142. By updating to ROCM 1.9 this error (in this problem at least) has disappeared. However, training appears to be very volatile. During the first epoch, a seemingly random step will fail with either the message CtxFailure at reshape_op.h:82: Invalid argument: Input to reshape is a tensor with 8000 values, but the requested shape has 0 or tensorflow.python.framework.errors_impl.OutOfRangeError: box_index has values outside [0, batch_size) or WhereOp: Race condition between counting the number of true elements and writing them.  When counting, saw 5830 elements; but when writing their indices, saw 1380 elements.
Source code / logs
The code is based on matterport's MaskRCNN (trainshapes.py) which would have to be installed and the images are quite large, so I have only included a very few.  I was able to train using tensorflow-cpu, so the code does seem to work.
bbc-mwe.zip

@lukas6464 ROCm TF1.10 is released, could you try that and let us know if the issue can be fixed there?
It would be helpful if you can try with docker images:
https://hub.docker.com/r/rocm/tensorflow/

related issue: https://github.com/tensorflow/tensorflow/issues/6378
could you help tune GPU VRAM usage and see if the issue gets away?

@lukas6464 ROCm TF1.10 is released, could you try that and let us know if the issue can be fixed there?
It would be helpful if you can try with docker images:
https://hub.docker.com/r/rocm/tensorflow/

Is it also possible to install without docker? I tried this, but can't seem to get it running. That is, I installed docker, downloaded the image, installed my dependencies, but can't get it  or a jupyter notebook running.
However, this does sound very much like the issue referenced below. Could you perhaps elaborate on what you mean with tuning gpu vram usage? I'm not sure what you mean with tuning

I am running into this problem as well, using TF1.10 with docker, training a Tensor2Tensor model. I am fairly certain this is not an issue with batch size or input size, but rather some bug in the underlying ROCM layer( I don't run into issues training these models on an NVIDIA Titan X).
 It also happens when I train smaller models like a MNIST VAE (multiple copies of the same model back to back).
I find that rebooting the machine seems to fix the issue sometimes, but I'm not certain if it's related.

@ericjang , can you set the following environment variable and provide your full logs that show the failure?
export MIOPEN_ENABLE_LOGGING=1

@lukas6464 @ericjang any updates on your issue?
Please try our latest docker image based on ROCm2.1:
rocm/tensorflow:rocm2.1-tf1.12-python3
If the problem persists, it would be helpful if you were able to provide us with the exact steps to reproduce or the logs we requested.

I'm closing this issue, please reopen it if there are further questions.


not working with react-native @0.60.5

Getting
Cannot read property 'Show' of undefined

same problem
TypeError: null is not an object (evaluating 'RNToasty.Show')

Running into the same issue in RN 0.61.3

Same problem on RN 0.61.4

Same problem with RN 0.61.1

Anyone has fix it ?

Anyone fix this ?

same problem, in ios
TypeError: null is not an object (evaluating 'RNToasty.Show')

I already solved it by delete app from simulator -> terminate npm server and start new one -> npm run ios.

Was having the same issue 4 months ago.. Had stopped using the library and looking for an alternative.
Just tried the library out now and its working fine for both IOS and Android.
"react-native": "0.61.1",
"react-native-toasty": "^1.0.0",


Custom import issue closed

Comment/edit permissions are completely disabled for me so I couldn't edit the other ticket, but #5 is fixed now after a third reinstall of the same version from pypi.
Thanks!

Sorry for that. Thanks for the update.


Updated tox and Travis to use py36.

Update Python interpreter used in Tox tests from py34 to py36.  3.6 seems to be what is used in the current Docker container.  Not sure what is deployed to sites.
Made equivalent changes to Travis config.  FWIW also locked dist to trusty, and added a matrix to split the 2.7 and 3.6 builds to use exactly those runtimes (possible the tox env was achieving this anyway).

thanks for merging this, @sigmavirus24


Change Signer::sign_tx_input to Signer::sign_psbt_input

With the previous API, signing taproot inputs comes with a lot of problems. Taproot signatures commit to the previous txo of all the inputs so to be able to construct a signature, you need to have all of them available. The previous API would require the user to look up the outputs themself which does not really work for mobile clients and it is a bad practice. This changes it to a PSBT so we can give all the necessary info to the user directly.

Mmm I'll have to sit on this one for a bit. I'm actually experimenting with taproot DLC now I'll let you know once I've got a better understanding of the issue.

Mmm I'll have to sit on this one for a bit. I'm actually experimenting with taproot DLC now I'll let you know once I've got a better understanding of the issue.

Okay, FWIW, I couldn't sign a funding tx with taproot inputs without this but now was able to.

I'm not sure I see the advantage of using a PSBT compared to just passing say an array of (TxOut, Script)? E.g., in the bitcoin-rpr-provider code it looks like you're just de-constructing it and then re-adding things after. I can see that in can be useful in some cases, but I feel it'd be better to keep it outside of the interface and let users decided to use it or not, unless there is some advantage that I'm not seeing?

You could just pass the txouts and scripts but i imagine most people will just make it into a PSBT, most wallets and libraries just use PSBTs for negotiating all this information.

Would like to see this make it's way through.
If most users, like myself, are using BDK it makes the API a lot easier.

I'm not convinced that the PSBT should be created within the library. It's easy to create it if people want to use it, but it adds many lines of codes to the library (creating and unpacking it after it gets signed).

Created #184 but tbh this still feels like a better approach

I personally much prefer #184. @luckysori any opinion on this?

Sorry I took so long to get to this.
#184 is nice because the change set is smaller and clearer. But I can see why this PR might make things easier for others. Also, I would assume most people using rust-dlc use bdk (we certainly do).
We're not currently affected by this, so I don't feel strongly about this.

I can't speak to how much this change will make life easier for signing taproot transactions but in general I'm in favor of using PSBTs on the API level. It's very likely that developers using rust-dlc will also be using bdk which already uses PSBTs.
As @luckysori already said, we're currently not affected by this, so I neithert feel strongly about this (:

Fixed


Show corresponding commands when hovering over Git menu items

The Git menu has a couple items that use terminology that doesn't originate from within Git. ("Sync", "Clean All", "Publish"?  What are these going to do?)  Even when they do, it's still not always clear what exactly will happen when you click them.  ("Pull" pulls from where?  Origin?  Using its branch of of the same name as the one that's checked out on your repo?)
Hovering over any of these items should show the commands that these items correspond with, so you know exactly what they're going to do.

Pull does the same as executing git pull without any special arguments.


Remove unnecessary parameters

Enhanced msvc cross-compile compatibility

Can you clarify how this helps?

This msvc version of the function does not depend on tz, tz was introduced (and not used) in the linux version of the function, where if it was for binary compatibility I think it could be retained but the function name has changed and there is no binary compatibility issue. Then in a cross-compiled environment it even brings some compiler alerts

And in linux the tz parameter is only used in the kernel, so I think it's possible to remove the unnecessary parameter


CI job update 2017-12-25 04:41

Update from CI

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

:x:Error

Details

[Error] Failed to load 29 files, aborting...
[Error] System.IO.FileNotFoundException: File not found.
File name: 'W:\kukj-log-88cb77f8\change-list-with-redirection.mapped.tsv'
at Microsoft.DocAsCode.Build.Engine.Incrementals.ChangeList.Parse(String tsvFile, String baseDir)
at Microsoft.DocAsCode.SubCommands.DocumentBuilderWrapper.BuildDocument(BuildJsonConfig config, TemplateManager templateManager, String baseDirectory, String outputDirectory, String pluginDirectory, String templateDirectory)
at Microsoft.DocAsCode.SubCommands.DocumentBuilderWrapper.BuildDocument()
Line 80: [Warning] Failed to run script W:\kukj-s_dependentPackages\ECMA2Yaml\tools\Run.ps1 with exit code -1

[Error] Failed to load 29 files, aborting...
[Error] System.IO.FileNotFoundException: File not found.
File name: 'W:\kukj-log-88cb77f8\change-list-with-redirection.mapped.tsv'
at Microsoft.DocAsCode.Build.Engine.Incrementals.ChangeList.Parse(String tsvFile, String baseDir)
at Microsoft.DocAsCode.SubCommands.DocumentBuilderWrapper.BuildDocument(BuildJsonConfig config, TemplateManager templateManager, String baseDirectory, String outputDirectory, String pluginDirectory, String templateDirectory)
at Microsoft.DocAsCode.SubCommands.DocumentBuilderWrapper.BuildDocument()
Line 80: [Warning] Failed to run script W:\kukj-s_dependentPackages\ECMA2Yaml\tools\Run.ps1 with exit code -1

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.

Still duping. Needs review.


Make data argument optional in GitHubAPI.post

Closes https://github.com/brettcannon/gidgethub/issues/70

Closed in favor of #73


fix: broken link from artwork page to auction house

The type of this PR is: Fix
This PR solves FX-4484
Description
Fixes a bug affecting all auction artwork pages.
The artwork page renders an auction partner entity header that attempts to link out to a non-existent auction profile page. Such profile pages for auction partners are not reachable on artsy.net (I'm not sure if they ever were.)

The fix here is to simply display that^ entity header without enclosing it in an <a>, behavior which is already supported in the EntityHeaderPartner component.
(There is also likely a fix to be made in MP, which maybe should not construct these invalid links in the case of auction partners)

Note that in https://github.com/artsy/force/pull/11465/commits/528ce3222907367c91a4d7613257b22df25da566 I updated the approach here based on some conversations in Slack here and here
TLDR: after going way down the rabbit hole I've decided to simply mirror the check that determines whether a partner page can even be rendered in the first place. That brings this entity link into sync with reality (without needing to reference whether it's for an auction, private partner page, etc.)


CU-86dtu92vq - Include how to test smart contract events using boa test constructor

Task linked: CU-86dtu92vq Include how to test smart contract events using boa test constructor

coverage: 91.201%. remained the same
when pulling 12e442ecd3c7087413d927eb10aa0ed439f9f199 on CU-86dtu92vq
into 9c903f9e55e0b943a6dfa59381255fa0889ca237 on development.

coverage: 91.201%. remained the same
when pulling 7f2b3329556477ccc35de5baa31de0a28b986e5f on CU-86dtu92vq
into 9c903f9e55e0b943a6dfa59381255fa0889ca237 on development.


New package: YO3DMU.PstRotatorAz version 14.82

Description

Resolve #111380

Checks

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.5 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

It's able to download the package with winget download -m and via Motrix on my local device without a proxy, but "Hash mismatch" occurs.

This package is using a vanity installer URL which always points to the latest release. Version 14.83 is released now (when commented). I'll upgrade the manifest. :smile:

@wingetbot waivers Add Validation-Domain


Fix conversion behavior which requires interfaces to be passed

Pass interfaces to the final conversion to avoid server-side error. Additionally, block transitions if an error occurs.

No longer needed, specific to #114 being out of date


mixcloud

youtube-dl --verbose https://www.mixcloud.com/b4m/2015-07-let-there-be-sun/
[debug] System config: []
[debug] User config: []
[debug] Command-line args: ['--verbose', 'https://www.mixcloud.com/b4m/2015-07-let-there-be-sun/']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2014.08.05
[debug] Python version 2.7.9 - Linux-3.16.0-4-amd64-x86_64-with-debian-8.1
[debug] Proxy map: {}
[mixcloud] b4m-2015-07-let-there-be-sun: Downloading webpage
[mixcloud] Trying with m4a extension
ERROR: Unable to extract title; please report this issue on https://yt-dl.org/bug . Be sure to call youtube-dl with the --verbose flag and include its complete output. Make sure you are using the latest version; type  youtube-dl -U  to update.
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/youtube_dl/YoutubeDL.py", line 516, in extract_info
ie_result = ie.extract(url)
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/common.py", line 170, in extract
return self._real_extract(url)
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/mixcloud.py", line 75, in _real_extract
PREFIX + r'm-title="([^"]+)"', webpage, 'title')
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/common.py", line 401, in _html_search_regex
res = self._search_regex(pattern, string, name, default, fatal, flags)
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/common.py", line 391, in _search_regex
raise RegexNotFoundError(u'Unable to extract %s' % _name)
RegexNotFoundError: Unable to extract title; please report this issue on https://yt-dl.org/bug . Be sure to call youtube-dl with the --verbose flag and include its complete output. Make sure you are using the latest version; type  youtube-dl -U  to update.

You are using an outdated version of youtube-dl. Read our FAQ if you have troubles updating.

Yes thanks!
apt-get -t jessie-backports install youtube-dl helped!


Add tcp support

:link: zboto Link

nice, I'm glad to see you didn't permanently remove the tcp-transport in favor of the z-emu transport :star_struck:

Closed in favor of #104


Auto Methods Encapsulation

fix the auto methods???

i went to the shop and tested out the updated version and it works!!


[Microsoft.Resources] Added missing error property to deployment properties

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[X] Other, please clarify

Added missing "error" property in all api-versions >= 2015-11-01 to match service response

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific language SDKs and CLIs that must be refreshed after the swagger is published.

[X] SDK of .NET (need service team to ensure code readiness)
[X] SDK of Python
[X] SDK of Java
[X] SDK of Js
[X] SDK of Go
[X] PowerShell
[X] CLI
[X] Terraform
[ ] No refresh required for updates in this PR

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[X] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

closes #1975

@jorgecotillo , can you fix lintDiff failures?

@jorgecotillo , can you fix lintDiff failures?

Do you mind helping me understand the failure and how to fix, I am not fully sure how to fix it, my PR just added a missing property.

/azp run

@jorgecotillo , can you fix lintDiff failures?

@raych1 Do you mind helping me understand the failure and how to fix, I am not fully sure how to fix it, my PR just added a missing property.

@jianyexi , can you light on the lintDiff errors?

@jorgecotillo , we're enforcing the rule to provide swagger example for each operation. That's what you saw as model validation failures. They're legacy issues and I won't block this PR merge, but please plan on the fix later.

@jorgecotillo , we're enforcing the rule to provide swagger example for each operation. That's what you saw as model validation failures. They're legacy issues and I won't block this PR merge, but please plan on the fix later.

Thanks a lot! I'll create a task on our board to account for this, given that there are several APIs without example, this effort is quite significant but we'll plan for it.

Hi @jorgecotillo, one or multiple breaking change(s) is detected in your PR. Please check out the breaking change(s), and provide business justification in the PR comment and @ PR assignee why you must have these change(s), and how external customer impact can be mitigated. Please ensure to follow breaking change policy to request breaking change review and approval before proceeding swagger PR review. Action: To initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki. If you want to know the production traffic statistic, please see ARM Traffic statistic. If you think it is false positive breaking change, please provide the reasons in the PR comment, report to Swagger Tooling Team via https://aka.ms/swaggerfeedback.

@jorgecotillo , can you get breaking change review approval?

Hi @jorgecotillo, one or multiple breaking change(s) is detected in your PR. Please check out the breaking change(s), and provide business justification in the PR comment and @ PR assignee why you must have these change(s), and how external customer impact can be mitigated. Please ensure to follow breaking change policy to request breaking change review and approval before proceeding swagger PR review. Action: To initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki. If you want to know the production traffic statistic, please see ARM Traffic statistic. If you think it is false positive breaking change, please provide the reasons in the PR comment, report to Swagger Tooling Team via https://aka.ms/swaggerfeedback.

@jorgecotillo , can you get breaking change review approval?

Do we need another breaking change approval? Jeffrey added the label some days ago, please let me know if another breaking change approval is needed so I can request it again. One question though, since the first breaking change approval, I haven't changed the spec, do you mind letting me know what is the change that needs approval please?

@raych1 please let me know if an additional breaking change approval is needed, Jeffrey already added the label but not sure if we need a separate breaking change approval. Thanks!


Fix actuators disabling

This PR ensure that a similar procedure is taken for all the cases where the Autoref reset the position of players (i.e. changes both, pose and posture). Those cases are:

Removal penalty
Set position at the beginning of half time
Set position at the beginning of a penalty kick (kicker or goalkeeper)

Since 1 was properly working, 2 and 3 have a behavior similar to 1 now.
Finally, a minimal duration of disabling the actuators is used rather than relying on secs_till_unpenalized transition which is expected to fix #217
Current status

[x] Automated tests
[x] Testing effects in games
[x] Feedback from teams

According to a game that was run and to feedback, this fix seems valid.