WinUI 3.0 with UWP

Is the Win3.0 fully supports for UWP? We have a Project in UWP we are looking that to migrate. Any suggestion? or Best article to refer it.

Did you see MSDN articles like Migrate from UWP to the Windows App SDK ?

Winui3 does not fully support the UWP app model currently.  @ryandemopoulos FYI

I gone through Microsoft article, and before that want to understand is that fully available to migrate. We have developed enterprise application. We are thinking to migrate that.

I gone through Microsoft article, and before that want to understand is that fully available to migrate. We have developed enterprise application. We are thinking to migrate that.

I think you need to read up on the difference between WinUI 2 and WinUI 3 they are 2 completely different things even though their names are almost the same....
In regards of WinUI 3 then no it is not ready atm for enterprise applications.

Closing this item because the WindowsAppSDK does not support UWP apps, details about which can be found in this discussion. If you have further questions about migrating your app, please open a new issue.


Erroneous images when zoomed

When I click on the topmost image to zoom in, the zoomed image is actually the bottom one.

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

ID: 12739084-4ac9-6850-9be5-88877a28e4b2
Version Independent ID: b0f5fb6b-ae55-22aa-6a53-972c52212d6f
Content: Tutorial: Register a Single-page application with the Microsoft identity platform - Microsoft identity platform
Content Source: docs/identity-platform/tutorial-single-page-app-react-register-app.md
Service: active-directory
Sub-service: develop
GitHub Login: @OwenRichards1
Microsoft Alias: owenrichards

@gnic67
Thanks for your feedback! We will investigate and update as appropriate.

@OwenRichards1
Could you please update the document with the correct screenshot where applicable.

@gnic67
Thanks for bringing this to our attention.
I'm going to assign this to the document author so they can take a look at it accordingly.

@gnic67
Thanks for bringing this to our attention.
I'm going to assign this to the document author so they can take a look at it accordingly.

@gnic67 Thanks for highlighting this error - I have now updated to the correct image.


rework groundtruth handling

FYI: pylint is activated in https://github.com/floweisshardt/atf/pull/152

atf_metrics.calculate_distance_to_obstacles is not conform with the way the other metrics are implemented and still uses started, finished etc. boolean logic - should either be adjusted or removed
same for atf_metrics.calculate_resources!

those are unsupported metrics. I removed them in https://github.com/floweisshardt/atf/pull/155 and created a backup branch https://github.com/floweisshardt/atf/tree/feature/old_metrics if we want to reanimate them sometime.

@fmessmer I'd suggest to merge this PR and not wait for the pylint fixes in #153.
I'll add temporary commits to use this feature branch in

[ ] atf_test_apps https://github.com/floweisshardt/atf_test_apps/pull/25
[ ] mojin_atf https://github.com/mojin-robotics/mojin_atf/pull/25
and merge those PRs as soon as Travis passes.

if the metrics are removed in #155, this PR should get rebased on top of floweisshardt/atf#master

PR is now rebased on floweisshardt/master


unable to create feature report

Pretty sure that I just don't know how to set this up.  I'm code diving right now, but what is the right way to get "And I capture a screenshot" configured?  I'm calling set_save_directory(settings.PROJECT_PATH, 'aloe_html') in my with_browser() method and the screenshots are getting generated.
======================================================================
ERROR: test suite for <class 'aloe.testclass.Admin'>
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/bschott/.virtualenvs/sites/lib/python2.7/site-packages/nose/suite.py", line 228, in run
    self.tearDown()
  File "/Users/bschott/.virtualenvs/sites/lib/python2.7/site-packages/nose/suite.py", line 351, in tearDown
    self.teardownContext(ancestor)
  File "/Users/bschott/.virtualenvs/sites/lib/python2.7/site-packages/nose/suite.py", line 367, in teardownContext
    try_run(context, names)
  File "/Users/bschott/.virtualenvs/sites/lib/python2.7/site-packages/nose/util.py", line 471, in try_run
    return func()
  File "/Users/bschott/.virtualenvs/sites/lib/python2.7/site-packages/django/test/testcases.py", line 1288, in tearDownClass
    super(LiveServerTestCase, cls).tearDownClass()
  File "/Users/bschott/.virtualenvs/sites/lib/python2.7/site-packages/django/test/testcases.py", line 168, in tearDownClass
    super(SimpleTestCase, cls).tearDownClass()
  File "/Users/bschott/.virtualenvs/sites/lib/python2.7/site-packages/aloe/testclass.py", line 125, in tearDownClass
    cls.after_feature(cls.feature)
  File "/Users/bschott/.virtualenvs/sites/lib/python2.7/site-packages/aloe/registry.py", line 197, in after_func
    after_hook(*args, **kwargs)
  File "/Users/bschott/.virtualenvs/sites/lib/python2.7/site-packages/aloe_webdriver/screenshot.py", line 68, in record_run_feature_report
    os.path.basename(feature.described_at.file)
AttributeError: 'TestFeature' object has no attribute 'described_at'```

OK, maybe a bug.  I think description_node is the right attribute not 'described_at'.
(Pdb) p feature.description_node.__dict__
{'line': 2, 'lines': (u'This feature tests that the admin view functions correctly.',), 'col': 1, 'filename': '/Users/bschott/Source/sites/awesim/site_common/features/admin.feature'}

This is a bug, the screenshot feature got in without tests. I am curious to know your use case, since I'm using a much simpler "screenshot on failure" step instead.

I hand hacked it just to use feature.filename and it generates what looks like the correct json file.  I'm not sure if there are cases where description_node.filename and feature.filename are different.
I'm was porting some code from our old lettuce terrain.py file that generates an html report and colorizes red or green with a link to the screenshot.  Sort of gives you the same experience as coverage report.

We also had a single page that tiled all of the screenshot thumbnails so you could look for bad template bugs that didn't actually break lettuce (like at one point remember white text on white background suddenly became the default).  Lettuce was perfectly happy!

I can PR that fix, but not sure about the right approach for the tests.  It appears we're really missing some command line flags to set that directory and I don't know why "./aloe_html" isn't just the default if you have --aloe_html=True or whatever.

Given that this feature is not very configurable in its current form, and broken for quite a long time, I'm going to remove it altogether. If you want to keep using the report, please copy it somewhere in your code base.
What I still want to add is a hook to save the page screenshot and HTML source on a failure.

I'd like to see your screenshot on failure approach.  Seems faster and simpler, but isn't it almost the same amount of code?  I back burnered this particular feature until we get the rest of our lettuce integration tests ported.  I'd be happy to test it as a snippet if you care to share.
We're trying to use this opportunity to clean up a lot of imperative non-Gherkin style integration tests and use the built-in steps wherever possible.  I might have several other minor issues to post where I got tripped up just for the sake of documentation for others.  For example,  "I see a link " steps doesn't find drop-down menus because of filter_displayed=True.  I made versions "I have a link " without this filter.  I also made versions that reverse on url name because we have multiple sites with different paths for the same thing (bike-shedding logout versus signout mostly :-).

Watch the pull requests here, I'll extract the failed screenshots once I have time.
If you have documentation problems, I'd like to hear about them - the docs are not as good as they can be, unfortunately.
In general, the steps here follow the user's perspective as much as possible. If a user does not see a link, it will not be reported visible. If you want to check the menu for links, write your own step, such as "The menu contains a link to...".

The replacement screenshot steps are implemented in #25, that's about to be released.


DB Error when revoking/dropping pgp key

I'm getting "▶ ERROR DB error" when trying to revoke/drop my pgp key. Same error occurs when running from the commandline, mac app, and android app.
-Mark

Thanks, CC @maxtaco @patrickxb.

I believe @zapu just fixed this. @zapu do we need a merge and a rollout or
is it a different bug?
On Sun, Jul 2, 2017 at 6:22 PM Chris Ball<EMAIL_ADDRESS>wrote:

Thanks, CC @maxtaco https://github.com/maxtaco @patrickxb
https://github.com/patrickxb.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/keybase/client/issues/7615#issuecomment-312520608,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA05_06pBWfT-QAT9f_6Xx8WL3JRsVJGks5sKBgkgaJpZM4OLs2M
.

If it's CORE-5589, then I started on Friday but haven't finished it yet.
@mehuman I think the workaround is to remove your encrypted secret key first, on the website; and then try pgp drop. Let me know if this worked.

@zapu The delete from the website and then a drop from the mac client worked.
I will add that switching between using drop and revoke between the different clients is confusing.
Drop - Mac client, Windows client, cli
Revoke - Android client, Website
Thanks for the help!


Add delays to network retries.

This adds a delay to network retries to help guard against short-lived transient errors.
The overview of how this works is: Requests that fail are placed into a queue with a timestamp of when they should be retried. The download code then checks for any requests that need to be retried, and re-injects them back into curl.
Care must be taken in the download loops to track which requests are currently in flight plus which requests are waiting to be retried.
This also adds jitter to the retry times so that multiple failed requests don't all flood the server when they are retried. This is a very primitive form of jitter which suffers from clumping, but I think it should be fine.
The max number of retries is raised to 3 in order to bring the total retry time to around 10 seconds. This is intended to address Cloudfront's default negative TTL of 10 seconds. The retry schedule looks like 0.5seconds ± 1 second, then 3.5 seconds then 6.5 seconds, for a total of 10.5 to 11.5 seconds.  If the user configures additional retries, each attempt afterwards has a max delay of 10 seconds.
The retry times are currently not user-configurable. This could potentially be added in the future, but I don't think is particularly necessary for now.
There is an unfortunate amount of duplication between the crate download and HTTP index code. I think in the near future we should work on consolidating that code. That might be challenging, since their use patterns are different, but I think it is feasible.

Also did we want to add some limit on the total number of retries system wide? Like if 20 requests need a retry then the registry is probably down/overlodad and retrying is just making it harder for the registry to come back up.

Also did we want to add some limit on the total number of retries system wide? Like if 20 requests need a retry then the registry is probably down/overlodad and retrying is just making it harder for the registry to come back up.

Can you say more about how you would envision that working?
I'm not sure how that would work beyond what is implemented here. If it is currently being overwhelmed, cargo will back off and smear the requests over some period of time.
If there is some hard limit for proactively giving up, I think that could be difficult to tune. Cargo inherently sends hundreds of requests all at once. In a situation where the server is having a temporary upset, it may very well recover within the existing retry schedule, even with hundreds of requests.
The current schedule is geared around the behaviors that I'm familiar with. Most recoverable transient errors can recover within a very short period of time. The second cliff is the set of errors that are recoverable within a moderately short period of time. Beyond that, most recovery won't happen for minutes/hours/days, which is longer than I think Cargo should bother waiting.
One of the hypothetical scenarios this is intended for is a temporary spike that triggers a rate limit. After waiting for Cloudfront's 10s negative TTL, things should be cleared up if there isn't a sustained barrage of traffic.
There could be a slower resume, with some intelligence of "ok, requests are succeeding again, let them go through faster" vs "requests are still failing, let's slow down even more". This would be similar to a slow-start algorithm, but only engaging when errors are encountered. However, I'm concerned about the complexity of implementing such a solution.

Can you say more about how you would envision that working?

All I had in mind was a global static RETRY_COUNT = AtomicU8::new(20), and then subtracting one from it before doing each retry. When it hits zero then cargo errors instead of continuing to do retries.

Cargo inherently sends hundreds of requests all at once. In a situation where the server is having a temporary upset, it may very well recover within the existing retry schedule, even with hundreds of requests.

That is a problem for the "simple" thing I had in mind. It's entirely possible that cargo is started 200 requests all of which will fail and all of which will succeed on their retry. :-/
Perhaps every time we make a "first request" foreign asset we increase the RETRY_COUNT. Now we have a system that lets us retry everything once, but only 20 things more than that. I don't know if this gets us the traffic shaping benefits I discuss below.

Most recoverable transient errors can recover within a very short period of time. The second cliff is the set of errors that are recoverable within a moderately short period of time. Beyond that, most recovery won't happen for minutes/hours/days, which is longer than I think Cargo should bother waiting.

Crates.io is set up with infrastructure that tends to either be up or down, not infrastructure that might be running at degraded service. Not all registries will work that way. For example a private registry might need to do a database call for every request that comes in.
One common pattern that happens with systems is that they are running entirely smoothly close to capacity. Then a some small hiccup happens, say a small number of requests take longer to process than they should. Connections start timing out before a response is ready. By the time the server is ready to start processing the next request it's even further into the connections timeout. This isn't entirely tragic, there is excess capacity that the server can use to catch up. It was running at say 90% of theoretical capacity, but thanks to the backlog is now running flat out and only getting 99% requests in on time. The 1% of Clients start receiving connection timeout errors and retry. The server is now receiving 1% more traffic, and it was already effectively overloaded. So now 2% requests get time outs. 2% of Clients retry. So the server is even more overloaded and 4% retry. This pattern continues until no actual work is getting done. As the queue builds up, the requests the server are picking up have been waiting longer and are closer to timing out. The recurrence relation is something like traffic = base traffic + retries but retries ~= max(0, capacity - traffic) which tends towards infinity. If the clients have a limit retries < %10 of base traffic, then a server running against base traffic with %10 headroom will be able to catch up even if all requests start hitting retries.
There is also a problem with nested retries. If cargo will retry all of its requests three times but cargo is run in a CI environment that will retry three times, then there is nine times as much traffic hitting the server when it's down than when it's running smoothly. Lots of systems would consider 9x normal traffic as a DDOS level. If cargo limits the total number of retries to 10% of base then even with a CI retry there is only a 3.3x.

One of the hypothetical scenarios this is intended for is a temporary spike that triggers a rate limit. After waiting for Cloudfront's 10s negative TTL, things should be cleared up if there isn't a sustained barrage of traffic.

This got me wondering, when we have this 503 issue is Cloudfront returning 503 for all endpoints or only specific packages? If most packages are still cashed correctly and working, but a handful are being retried, then even my simple suggestion should work well.
I just generated a bunch of words, but I don't know what we should do next. Sorry. Did anything I say make any sense?

This got me wondering, when we have this 503 issue is Cloudfront returning 503 for all endpoints or only specific packages?

Based on my reading of the documentation, I think it is not a simple answer. I believe the rate limit on S3 is per prefix. The prefix is everything up to the last slash. But the docs also say that the partitioning is adjusted dynamically based on the traffic patterns. So if everything is partitioned completely, then I think the rate limit would be based on the first 4 letters (that is, /ca/rg/* would all have the same rate limit). However, if it is not fully partitioned, then the rate limit could be broader (perhaps the entire bucket?).
I'm pretty sure Cloudfront's cache will be per endpoint.
But these are just guesses based on the available docs.

Lets not delay this, desperately needed, PR for the "cap on retries" functionality. We can move it to an issue and come back to it latter.

@epage I was wondering if you've had a chance to look at this? I think this is a relatively high priority change that I would like to see get into beta to help mitigate some risk with the registry change.

@bors r+

:pushpin: Commit 4fdea658a895d5de01fd7dbe92848d50361092f2 has been approved by epage
It is now in the queue for this repository.

:hourglass: Testing commit 4fdea658a895d5de01fd7dbe92848d50361092f2 with merge 0e474cfd7b16b018cf46e95da3f6a5b2f1f6a9e7...

:sunny: Test successful - checks-actions
Approved by: epage
Pushing 0e474cfd7b16b018cf46e95da3f6a5b2f1f6a9e7 to master...


added dropdown to navbar

Related Issue
added dropdown to navbar
Closes: #216
Describe the changes you've made
https://user-images.githubusercontent.com/55352601/118739891-2ca43280-b868-11eb-8618-4ae865a66d3c.mp4
Type of change
What sort of change have you made:

[]Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Mention any unusual behaviour of your code (Write NA if not)
Any unusual behaviour of your code
Additional Info (optional)
Any additional information you want to give
Checklist:

[x] My code follows the guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly whereever it was hard to understand.
[x] My changes generate no new warnings.
[ ] Any dependent changes have been merged and published in downstream modules.

@adarshvulli @ankitapuri kindly review this PR.
currently i had removed that previous drop down for avoiding merge conflicts.
As soon my PR is reviewed I will remove it immediately

@adarshvulli @ankitapuri kindly review this PR.
currently i had removed that previous drop down for avoiding merge conflicts.
As soon my PR is reviewed I will remove it immediately

There is no need of the dropdown on the left-side then

Yes i am removing it right now @ankitapuri


Mouse click remains when touch screen used

Test device:
Dell Laptop
Operating System:
Win 10
Browser:
Chrome
Problem description:
Found during https://github.com/phetsims/QA/issues/212, but not restricted to that sim.
When holding something with the mouse, if the touch screen is used during that time the mouse can be released but acts as if it is not.  Assigning to @jonathanolson as it looks like an input event issue.
Steps to reproduce:

Go to States of Matter's second screen
Use the mouse to turn on the heat bucket.
While using the mouse to keep the heat bucket on, use the touchscreen to move the roof of the container
While using the touch screen release the mouse.  The heat bucket should stay on.
After this you can let go of the touch screen and the heat bucket will stay on.

Screenshots:

Troubleshooting information (do not edit):

Name: States of Matter
URL: https://phet-dev.colorado.edu/html/states-of-matter/1.1.0-rc.3/phet/states-of-matter_en_phet.html
Version: 1.1.0-rc.3 2018-10-26 18:31:25 UTC
Features missing: touch
Flags: pixelRatioScaling
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36
Language: en-US
Window: 1536x732
Pixel Ratio: 2.5/1
WebGL: WebGL 1.0 (OpenGL ES 2.0 Chromium)
GLSL: WebGL GLSL ES 1.0 (OpenGL ES GLSL ES 1.0 Chromium)
Vendor: WebKit (WebKit WebGL)
Vertex: attribs: 16 varying: 30 uniform: 4096
Texture: size: 16384 imageUnits: 16 (vertex: 16, combined: 32)
Max viewport: 16384x16384
OES_texture_float: true
Dependencies JSON: {"assert":{"sha":"928741cf","branch":"HEAD"},"axon":{"sha":"d7ba44e2","branch":"HEAD"},"brand":{"sha":"89d28f63","branch":"HEAD"},"chipper":{"sha":"bbbb514a","branch":"HEAD"},"dot":{"sha":"820111c8","branch":"HEAD"},"joist":{"sha":"749f10ff","branch":"HEAD"},"kite":{"sha":"59755f7e","branch":"HEAD"},"nitroglycerin":{"sha":"ccaab9cd","branch":"HEAD"},"phet-core":{"sha":"68a89cc4","branch":"HEAD"},"phet-io":{"sha":"364077cf","branch":"HEAD"},"phet-io-wrapper-classroom-activity":{"sha":"abc4ae3e","branch":"HEAD"},"phet-io-wrapper-hookes-law-energy":{"sha":"429886e7","branch":"HEAD"},"phet-io-wrapper-lab-book":{"sha":"ef0b0b0c","branch":"HEAD"},"phet-io-wrappers":{"sha":"7ec1a04a","branch":"HEAD"},"phetcommon":{"sha":"22b158d0","branch":"HEAD"},"query-string-machine":{"sha":"c2e502fb","branch":"HEAD"},"scenery":{"sha":"415371c3","branch":"HEAD"},"scenery-phet":{"sha":"94b92879","branch":"HEAD"},"sherpa":{"sha":"a9fd066b","branch":"HEAD"},"states-of-matter":{"sha":"fc42d33b","branch":"HEAD"},"sun":{"sha":"3086e97a","branch":"HEAD"},"tambo":{"sha":"0e5b9133","branch":"HEAD"},"tandem":{"sha":"a2348c0c","branch":"HEAD"}}

Is Hanson the device that exhibited this problem? I might wait until Tuesday to investigate this in person.

@jonathanolson, I think the device Katie used is a similar model to Hanson. It's essentially a larger version of Hanson.


Question about the naming (Test dataset split)

If there is any good reason of using the term --train_split for testset?
https://github.com/huggingface/autotrain-advanced/blob/22944c0cbb1c5e0f0929407438e8a6ae34fe9ed2/src/autotrain/cli/run_llm.py#L47-L52
Would it be more straightforward with a name --test_split?

sorry, thats a typo. fixed


update recipe to work with the new neo4j

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-webservice.
I tried to re-render for you, but it looks like there was nothing to do.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Just asking, who am I waiting for?
And another thing importing v1 is deprecated, should I remove it too, or wait until it's deprecated?

@pvanheus

@ocefpaf

Looks like the maintainer here is unresponsive.  In that case you should contact @conda-forre/core and, if you want to take it over, add yourself as a maintainer.
Let me know if you want add yourself, if not I can merge this for you.

Hmm... I think that for now just merge, I'll think about maintaining it later


Use new GH action for adding to projects

We want to use this action in more than one repository.

@bot-gradle test and merge

OK, I've already triggered a build for you.


Feature request

Explain that using the vagrantfile is just a way to test the ilke distribution in a local environment, with a local version only .

Duplicate of #13


add python-dotenv

The OpenAI and Azure API Key should be isolated in the pipx installation. The user should be prompted to enter the necessary environment variables if not available in the isolated environment. These variables should be stored in an .env file.
Use https://github.com/theskumar/python-dotenv

you can assign this to me?

Sure, thanks for picking this up @bhargavnova !

Hi @fynnfluegge , I add coded the module,
Just let me know where should I put that in your repo code.
that would be easy for you.
script_name : env_loader.py has funciton env_loader()

Hi @fynnfluegge , I add coded the module,
Just let me know where should I put that in your repo code.
that would be easy for you.
script_name : env_loader.py has funciton env_loader()

Perfect, I think app.py is fine. You can raise a PR and I will take a look later 🙌

done : )


Plugin incorrectly active in subsequent calls on connection keep-alive (problem new since 2.4.0)

Summary
When two calls are made to the same server+hostname but different routes and using connection keep-alive, then plugins that are active in the first call are also (incorrectly) active in the second call.
The plugin is configured on the route belonging to the first call. The second call uses a different uri (i.e. route) where the plugin is not configured. So the plugin must not be called there.
i.e.
myserver.com/route1 -> plugin active
myserver.com/route2 -> plugin not active
Requesting myserver.com/route1 and myserver.com/route2 seperately (no connection keep-alive) results in everything working fine. Requesting both in one connection results in the plugin being active in both requests.
The problem first appeared after upgrading from kong 2.3.3 to kong 2.4.0. In 2.3.3 everything was ok. No change was made while upgrading to 2.4.0 - just the upgrade itself by switching docker base image from kong:2.3 to kong:2.4.
Steps To Reproduce
In my case:

Plugin is kong-referer-restriction (https://github.com/dsteinkopf/kong-referer-restriction). This is configured for myserver.com/route1 and checks if the referer contains 'myserver.com'. Result is http 403 if not.
The plugin is not configured for myserver.com/route2
curl https://myserver.com/route2 results correctly in status 200 which shows that the plugin is correctly inactive here.
Do two consecutive calls using the same connections: curl -v -K curl.txt.  curl.txt:

url = "https://myserver.com/route1"
referer = "https://myserver.com/test"
output = "dummy1"
next
url = "https://myserver.com/route2/"
output = "dummy2"

Output is:
...
< HTTP/1.1 200 OK
...
< Via: kong/2.4.0
<
{ [1968 bytes data]
100  1956    0  1956    0     0  17621      0 --:--:-- --:--:-- --:--:-- 17621
* Connection #0 to host myserver.com left intact
* Found bundle for host myserver.com: 0x7fb38ae18230 [can pipeline]
* Could pipeline, but not asked to!
* Re-using existing connection! (#0) with host myserver.com
* Connected to myserver.com (xxx) port 443 (#0)
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
> GET /route2/ HTTP/1.1
...
< HTTP/1.1 403 Forbidden
...

This shows that the plugin is active is (incorrectly) active in this case.
Additional Details & Logs

Kong version ($ docker-compose exec kong kong version) -> 2.4.0
Kong debug-level startup logs ($ kong start --vv) -> How can I do this when using docker?
Kong error logs (<KONG_PREFIX>/logs/error.log) -> I don't see any errors in my logging server.
Operating system: Docker hub image kong:2.4
Kong configuration (the output of a GET request to Kong's Admin port - see
https://docs.konghq.com/latest/admin-api/#retrieve-node-information) -> I'll try to give some extract here, if needed.

The problem seems not to depend on the plugin itself. I have a very similar problem in another case where the plugins acl+key-auth resp. acl+basic-auth are used.

@dsteinkopf, thank you for report. We try to reproduce, and fix it asap.

BTW. I am now using a workaround to prevent this problem: Add a global response-transformer plugin with "replace headers" Connection: close. This avoids connection keep-alive and so the problem does not occur.

@dsteinkopf, we have had some hard time trying to reproduce this, could you provide us step by step instructions how you are able to reproduce it?

@dsteinkopf, actually I got something reproduced now. Looking in the detais.

@dsteinkopf,
Findings so far:

happens only with client tls connections
does not happen when downgrading OpenResty to <IP_ADDRESS>

We are working on it, and I hope we have a good solution soon.

Thank you for your work. Sorry I wasn't able to help you better. Seems it was really hard to reproduce. (Only TLS ... that would have been the last thing for me to mention...)

@dsteinkopf, yes, no problem, this has been hugely valuable feedback, and this needs attention. Thanks for helping us.

I can confirm that kong 2.4.1 fixes this reported problem. Thank you very much.


[Tests-Only] Test against core branch refactor-tests-to-use-Shares-folder

The core PR has been merged.
There will be new scenarios to add to expected-failures.


Vickel: Watch<PHONE_NUMBER>

Vickel requests the watch of the watch_number<PHONE_NUMBER>. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

Approved by Makyen in Charcoal HQ


Fixed NetworkPopup.tscn UI so the buttons host and join are always visible

(Literally the 2 inspector changes in #240 but without that whole 4.3 baggage, reposting images below)
Before

After

Below is on the scene itself, before:

After (noray was taken in mind)

Ideally, host/join would be on the bottom of the panel, but I would have to make a new Control node, and that would be too much for sth like this

Since only the example project is modified in this PR, the version bumps for the netfox libraries aren't necessary.

Thanks for working on this! The way I understand, the current changes are to shrink the UI.
Would it be possible to have the panel have a max size ( i.e. no bigger than 540x540 ), but shrink if the window gets smaller, and keep it centered? Let me know if you'd like to work on this, otherwise I can mess around with it too.

It would need custom code to scale down, as the Control property works via anchor/size, doesn't have a Scale property like Node2D and Node3D and will not downscale its elements within.
Not worth the time imo. This PR took 5 minutes. Gathering the images and doing the git push took more time than making this. I would recommend just merging this and using the saved time for netcoding PRs, instead of UI

I can take a look at making the window scaleable if it's alright with you all.

@annamaria-szentpeteri please feel free!

I just realized that this NetworkPopup.tscn which is used in both multiplayer-simple.tscn and multiplayer-netfox.tscn examples, is not used in forest-brawl. This is kinda understandable, given forest brawl includes player name and settings.
Anyway, this PR is exclusively for these 2 examples multiplayer-simple.tscn and multiplayer-netfox.tscn not forest-brawl.

Happened to stumble into a video which explains scaling Control nodes without code, sharing it here:
https://www.youtube.com/watch?v=blPqie3Z_F0

Added a custom minimum size and centered the panel, so it will be visible in many more cases.


Error after update.

After the <IP_ADDRESS> I've been getting this error in my console, and my server is constantly crashing, here is the log. http://pastebin.com/NavDRAgD Not really sure what to do to fix this, but been working on it for about 12 hours.

Could you make a picture of your Permissions.config.xml? Maybe is something wrongthere.

Here's my permissions. http://pastebin.com/3DYnGLAM They were working before the update, and whenever I change them I validate my XML.

Hmm I can´t see any mistake and I think you already tried to remove the prefix/suffix for the player "76561198136976221". And the Permissions.config work well for me. Which plugins do you use?

Sorry for the delay, I use uEssentials, Airdrop Manage, ZaupFeast, ZaupShop, Uconomy, WebsiteCommands, Votifier, isAbusing, VehicleEvents. I've made a completely new server, re-downloaded the plugins, re-made the permissions and moved over just the map and players data but I just got his data http://pastebin.com/qqncM5Gw.

Can you see if removing the parent group from the main group does anything? the main group has the parent set to the main group on the server.

We use github to track repeatable bugs, and feature requests.
The scenario you've described seem to not be caused by a bug in Rocket itself.
Please consult this guide to figure a solution for your problem.
You can also create a new topic in the support section on our forum.
If you can reproduce the bug in Unturned without Rocket being installed you may report it directly to the Unturned developers.
Feel free to reopen this issue if you can bring up new details on the topic.


Massive multi-threaded writes uses up all tcp ports

I'm getting this error:
Unable to connect to the remote server ---> System.Net.Sockets.SocketException: Only one usage of each socket address (protocol/network address/port) is normally permitted
when I'm pushing the WriteAsync method hard from multiple threads. If I understand the error correctly it indicates that a new connection is created for each write. Is there a way where we can reuse an existing connection instead?

Hi HakanL,
I actually had a very similar issue while I was using ziyasal's InfluxDB.Net. I tried to make a singleton wrapper around the HttpClient to reuse the same connection but after testing it I realized i was still getting new connections all the time.. So the library currently doesn't handle that.
However, I managed to go around that problem by batching my writes. Here is the ticket that was opened for that. In that thread I provided some sample code for how to batch the writes. Perhaps that might be a good enough solution for you for now. It significantly reduced the stress from the InfluxDB machine in our case. The only downside is - we now have a "listener app" which handles incoming readings, batches them and then submits them to the DB.
If you have some spare time (that you're reaaaalllly not sure what to do with :D ) , perhaps you could try to modify the library to make it reuse an existing connection and test that?

Turns out there are 5-6 different .NET clients for Influx so I ended up using a different one that didn't have this issue.

Glad you managed to make it work out for you. :)
Would you mind please telling me which client did you end up using so I could take a look how they did it? It might help me resolve the issue in this library as well. Thanks.

Yea of course! https://github.com/nblumhardt/influxdb-lineprotocol

Thanks!

This has been fixed with the v5.0.1.


[epics-db] support macro in macro

lines
record(stringin, "${SIGNAL}-CAL-NNAM") {
    field(INP,  "$(NNAM_PV=${SIGNAL}-NNAM CPP)")
}

tree-sitter message:
$ tree-sitter parse --stat  $file
(source_file [0, 0] - [4, 0]
  (record_instance [0, 0] - [2, 1]
    type: (record_type [0, 7] - [0, 15])
    name: (record_name [0, 17] - [0, 37]
      (macro_expansion [0, 18] - [0, 27])
      (string_text_fragment [0, 27] - [0, 36]))
    (field [1, 4] - [1, 48]
      name: (field_name [1, 10] - [1, 13])
      value: (string [1, 16] - [1, 47]
        (macro_expansion [1, 17] - [1, 46]
          (ERROR [1, 35] - [1, 45]
            (ERROR [1, 36] - [1, 45])))))))
calibPolynom.template	0 ms	(ERROR [1, 35] - [1, 45])
Total parses: 1; successful parses: 0; failed parses: 1; success percentage: 0.00%

fix:
remove macro in macro :smile:

Welp, the fix doesn't support every cases. The parser seems to like when the macros all have the same convention (only ${} or only $()). It seems quite hard to fix every cases, I think it's because macros can be everywhere, the parser gets confused as to if the macro inside the macro is here because it's manually handled, or because it can be anywhere...

thanks for the fix, it solves the main cases. For example, in my case INP 1 and 2 are ok for tree-sitter-epics but not the 2 last one (like you say in your comment above).
record(ai, "${SIGNAL}-CAL-SRAT-RB") {
    field(INP,  "${SRAT_PV=${SIGNAL}-SRAT-RB CPP}")
    field(INP,  "$(SRAT_PV=$(SIGNAL)-SRAT-RB CPP)")
    field(INP,  "$(SRAT_PV=${SIGNAL}-SRAT-RB CPP)")
    field(INP,  "${SRAT_PV=$(SIGNAL)-SRAT-RB CPP}")
}```


remsh doesn't works when vm.args cookie is quoted

In https://github.com/apache/couchdb-pkg/pull/106 we fixed a bug where the Erlang cookie couldn't accept some characters. With that fix the cookie value in vm.args might be quoted and our remsh script doesn't know how to parse that yet. That will break remsh access on next release.
We'll likely need updates here  https://github.com/apache/couchdb/blob/88ebc65c0d0c464bf45b10ad6a3234dd07361975/rel/overlay/bin/remsh#L50-L57
And here https://github.com/apache/couchdb/blob/88ebc65c0d0c464bf45b10ad6a3234dd07361975/rel/overlay/bin/remsh#L121-L130

@imskr
Do you have any news / work on this feature?

Hi @big-r81 I need some help here. Can you guide me?

Hi, what questions do you have? Are you able to compile CouchDB already? If not, read our README for Devs. If you have any other questions, please just ask.

Yes I'm able to compile. I was wondering how we can parse the quoted cookie value

The cookie can come from an env var (ERL_FLAGS), from an args file (vm.args) or from the command line as argument from the remsh script. In https://github.com/apache/couchdb-pkg/pull/106 there should be some inspirations of the changed regex for cookie extractions.


Race condition with setHeightCalculationMethod()

I'm using setHeightCalculationMethod() from within the content window to set the height calculation method, as lowestElement is the only method that correctly calculates the height for me. This is working only intermittently, and I believe I've figured out why.
When it works (about 20% of the time), the order of events is:

Parent window loads
Child window loads
Child window sets height calculation method
Iframe-resizer calculates height correctly

When it fails, the order of events is:

Parent window loads
Child window loads
Iframe-resizer calculates height based upon the default height calculation method
Child window sets the desired height calculation method
Iframe-resizer does not reset the iframe height
No further window events fire to cause another iframe resize

I've tried hacking the iframe-resizer code to make setHeightCalculationMethod() cause an iframe resize, and I've also tried manually calling the undocumented public method reset() after setting the height calculation method.
Neither of these approaches work, because of the triggerLocked system that is in place in iframeResizer.contentWindow.js. If I'm interpreting the code correctly, it's designed to prevent the resize happening in rapid succession.
There are two things I think would fix this, and potential future race condition issues:

Scrap the triggerLocked system in favour of a proper debounce implementation. Rather than just ignoring subsequent events, this will allow you to perform a resize on the leading and/or trailing edge of a set of events.
Setting the height calculation method should automatically trigger a reset(). Either that, or document reset(), and mention that it needs to be called manually after setting the method.

If I get a chance, I'll have a go at a PR, but this one might be a bit complex for me to tackle.

Okay, I may have jumped the gun there. There is a race condition, but it's not the one described above. I was using this logic in my app (forgive the CoffeeScript and Angular-ness):
if $window.parentIFrame?
    $window.parentIFrame.setHeightCalculationMethod "lowestElement"

The problem was actually that, most of the time, window.parentIFrame did not exist yet, as the parent window had not finished executing its initialization code in time. So now I'm stuck with the lovely solution of using setInterval() to account for this delay:
iFrameResizeAttempts = 0
iFrameResizeInterval = null
initIframeResize = ->
    if ++iFrameResizeAttempts > 30
        $window.clearInterval iFrameResizeInterval
    else if $window.parentIFrame?
        $window.clearInterval iFrameResizeInterval
        $window.parentIFrame.setHeightCalculationMethod "lowestElement"
iFrameResizeInterval = setInterval initIframeResize, 100

Do you have any better ideas on how to solve this?

Your the second person this week to raise this, maybe the lib needs to fire a custom event event on ready. Easy with jQuery, need to think about native.

That said why are you not setting the height calc mode in the parent?

The parent is controlled by a different software company to the one I work for. Setting the calc method from the child allows me to change it without instigating a laborious political process ;)

Ah.
https://c1.staticflickr.com/1/36/96987427_d3a0582fdc.jpg
--
Sent from my iPhone.


Upgraded HTTP to 0.5

Upgraded HTTP to 0.5 with async Response

@yegor256 I'm available for review, please assign me

@g4s8 I'm available for review, please assign me

This pull request #8 is assigned to @hdouss/z, here is why; the budget is 15 minutes, see §4; please, read §27 and when you decide to accept the changes, inform @g4s8/z (the architect) right in this ticket; if you decide that this PR should not be accepted ever, also inform the architect; this blog post will help you understand what is expected from a code reviewer; there will be a monetary reward for this job

@HDouss made changes, please review

@g4s8 Please review and/or merge.

Job audit: ARC didn't merge or close PR, performer @hdouss/z/z didn't make CR comments

Job was finished in 19 hours, bonus for fast delivery is possible (see §36)


[BUG]

Version information

Laravel: v5.7.x
Voyager: v1.1.x
PHP: 7.2
Database: mysql 14.14 ( Distrib 5.7.24)

Description

Throwing exception instead of showing error for "Integrity constraint violation".
Steps To Reproduce
Steps to reproduce the behavior:

Go to 'Roles'
Click on 'CreateRole'
Go to 'Users'
Assign the newly created role
5.Go to 'Roles'
6.Try to delete the newly created role (which was assigned to user in step 4)

Expected behavior
Some error message I am excepting like "assigned roled cannot be deleted" (It may be a featuere as well) when tried to delete the role which was assigned to user already.
Screenshots

If Voyager would cover all possible exceptions, it would be a few GB in size.
Instead, create exception-handlers as you'd do in normal Laravel.


Rare encoding unseen levels in fit

Currently if a categorical column level appears in transform that was not part of the column the rare transformer was fitted to, the level will be passed to rare.
This conflcts with the newest mean response transformer implementation (which allows encoding unseen levels to the global target average) when a pipeline applies both mean response and rare transformers to a column. As the rare transformer tends to come up before the mean response transformer, any new levels that appear in that column are passed to rare and encoded to the mean response of that category. There is therefore no distinction between levels being rare within the training data and new levels appearing over the time.
A flag input to be able to keep rare levels that were not observed when fitting as the same value would be ideal

Thanks @Decima2014 this is a good point.  Will look to add in the option to leave alone/rare encode new levels in rare encoder.

Could I ask for a MRE  - this sounds like a fairly clear requirement and is worth adding a test for the expected behaviour first.


Allow setting aws logger through appsettings.json in .net core and respond to runtime configuration changes

Description

Added the ability to set a logger through appsettings.json ( or any IConfiguration source ) under the LogTo property. LogTo was chosen as a name to mirror AWSConfigs.cs. I am aware that the field is obsolete in AWSConfigs.cs, however the related LogResponse and LogMetrics can already be set on the configuration file, and I thought it would be cleaner to keep them together.
Added an options monitor that listens for configuration changes and will forward any changes made to the LogTo property to AWSConfigs.cs. The  InvokeChanged method can be extended in the future to react and propagate other updated configurations in the future. A lock is used to prevent rapid file updates from colliding.
As the unit test needs to write changes to a JSON file, I've added a helper that creates a temporary file and stores the path to it.
The monitor absolutely the IConfiguration, so the change monitoring only works if either of the new AddDefaultAWSOptions overloads is used.
One open thought or concern is that users could inject their AWSOptions class somewhere and change LogTo, and it would not do anything ( as only the change monitor propagates the updates value to AWSConfigs.cs ). I think the best approach there is to make AWSOptions implement property change notification and making the monitor respond to them. This ensures we only have a single AWSOptions-of-truth ( the singleton in the DI context ) and only respond to changes made to that particular instance.
Motivation and Context

We would have been able to debug an ongoing issue if we have had the ability to turn on logging during runtime. With this change you can go onto your box/container, update appsettings to specify LogTo and get the data you need.
This is especially important as dotnet tooling for linux is still lacking, and any form of debugging or dumping requires extra software that can't always be installed on production boxes, meaning logging can sometimes be the only way to debug ongoing production issues.
Testing

Added 3 Tests that ensure correct propagation of the LogTo property and the monitor's ability to respond to file changes.
Screenshots (if appropriate)
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[x] My code follows the code style of this project
[ ] My change requires a change to the documentation
[ ] I have updated the documentation accordingly
[x] I have read the README document
[x] I have added tests to cover my changes
[x] All new and existing tests passed

I held off on documentation changes for now, as I am not 100% sure how you want to document this new functionality.
License

[x] I confirm that this pull request can be released under the Apache 2 license

What needs to be done to move this MR forward?

The AWSSDK.Extensions.NETCore.Setup library has been updated to support configuring logging. Here is an example appsettings.json file showing how to configure logging. https://github.com/aws/aws-sdk-net/blob/master/extensions/test/NETCore.SetupTests/TestFiles/EnableLoggingTest.json


Fix TensoredOp.to_matrix with global coefficients

Summary
Fixes #9398.
Details and comments
As the author of #9398 correctly pointed out, this is the analogous error fixed in #9283, where the global coefficient was multiplied with the matrix once per element in the tensored expression, when it should only be applied once.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

4 of 4 (100.0%)  changed or added relevant lines in 1 file are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.04%) to 84.93%

Files with Coverage Reduction
New Missed Lines
%

src/sabre_swap/layer.rs
2
98.95%

Totals

Change from base Build<PHONE_NUMBER>:
0.04%

Covered Lines:
66659

Relevant Lines:
78487

💛  - Coveralls


YAML way of doing this?

This page does not describe how to do this with azure-pipelines.yml.

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

ID: c78a9f20-b8d2-4aa7-c52d-a968ab87315d
Version Independent ID: 3880a787-8f70-8c13-176e-c732b619fb06
Content: Restore Package Management NuGet packages in Azure Pipelines - Azure Pipelines
Content Source: docs/pipelines/packages/nuget-restore.md
Product: devops
Technology: devops-cicd
GitHub Login: @thomps23
Microsoft Alias: amullans

@CornedBee -- thank you for your feedback.  I have notified the author of your suggestion.  In the meantime, you may find related information on Azure DevOps on Stack Overflow.  I am closing this issue now -- you are welcome to reply to this issue in the future with an @ mention.
@andyjlewis -- do you have any yaml examples in the works?


fix(index): export tooltip, datepicker

Fix Export
A few elements were not being exported. This fixes that.

Exports Toolbar and DatePicker and all subcomponents

👍 ✅

Bluemix toolchain: Delivery Pipeline deployed carbon-components-react to Bluemix Design System, including commit 400de050d972fd59ffeb326901b7b077599e1d3a


update dependencies

Codecov Report

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

@@           Coverage Diff           @@
##             master     #3   +/-   ##
=======================================
  Coverage       100%   100%
  Complexity      220    220
=======================================
  Files            20     20
  Lines           340    340
=======================================
  Hits            340    340

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 780eec1...1d7a385. Read the comment docs.


Chore: Fix deprecation notice in action "version-or-publish"

This deprecation notice.
version-or-publish
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

seen in this test run.
https://github.com/martinfrances107/tauri/actions/runs/9995204078

I should explain the second commit.
When I reviewed my own fix... I saw that it should be universally applied to  many actions.

Opps so I went stomping arround in clodhoopers over a pre-existing well thought out set of policies. ( thanks for being so polite with the bull in the china shop :) )
... My bad.
For reference I went looking for the node policy, I will quote it at the end. The LTS changed annually
For our discussion the options  from actions/setup-node@v3 that I want to use seem to be "latest" "current" or "lts/*" as appropiate
For this change there is a negative aspect..
When debugging/comparing test between passes and failures... a developer might grimace to discover that the node version is not static from run to run.
But given that policy this will be a "once yearly event"
I just wanted that converstion to be stated in public.
Anyway I will fix all my errors over the weekend.

https://nodejs.org/en/about/previous-releases
Major Node.js versions enter Current release status for six months, which gives library authors time to add support for them. After six months, odd-numbered releases (9, 11, etc.) become unsupported, and even-numbered releases (10, 12, etc.) move to Active LTS status and are ready for general use. LTS release status is "long-term support", which typically guarantees that critical bugs will be fixed for a total of 30 months. Production applications should only use Active LTS or Maintenance LTS releases.

Sorry for the delay here .. this had to wait until the weekend
Ok I think have more faithfully expressed the requirements .. here it is in bullets points.

Anything publishing or deployment related
-- A hard coded number. Ensures no surprise updates. Human will always be involved in change.

lint/testing
-- auto increment with a bias to the conservative "LTS"

android... I think my best response is the backout the changes in that regard completely
and let someone else drive change.

Other more informed android devs will have opions about lastes/LTS and for example wheather those measures
should be ignored because they deviate from the long tail of the install base.
Another thing I see in a few places is a list of supported nodes version --
      matrix:
        node:
          - '16'
          - '18'
          - '20'

to my mind I think we can drop support for 16 now, but I think especially when discussing policy.
micro PRs are better.
PS
A PR is incomming.

Many of the change have already filtered into the dev branch
Mostly due to last saturdays commit
Author: Lucas Fernandes Nogueira<EMAIL_ADDRESS>Date:   Sat Aug 17 08:21:27 2024 -0300
23a912bb84d7c6088301e1ffc59adfa8a799beab
So I have redone this PR (hence the force push) with just small items left.
In fact The only thing that remain is ...
lint/testing
-- auto increment with a bias to the conservative "LTS"

Thank you


TouchableHighlight object inside a FlashList Losing Focus on fast key navigation with React Native TVOS

TouchableHighlight object inside a FlatList Losing Focus on fast key navigation
I have a FlashList with 100 TouchableHighlight with images.
On navigation, the TouchableHighlight gets the focus properly (underlay colour).
but when we do fast navigation (left/right keys), the Focus is lost. This happens when you see empty scrolling without containers, you can stop here to load the items and see the focus is lost.
When checked with Flipper, The focus is given to the parent FlashList container tag.
On further left/right arrow keys able to highlight the children again.
This issue is easily reproduced with FireTV-4k
This issue is very easily seen with RecyclerList and also happens with FlatList.
With android emulator little hard to reproduce running in MAC-M1, can also reproduce by making the app little slow with some timers/keeping-js-busy. (use on-screen directional pad for key navigation for fast key repeats.)
A Test app is provided with FlatList and FlashList.
We are facing this issue in our project running on fireTv with recycler list.
has anyone faced this issue or already have any solution for this ?
Steps to reproduce:

PFA test app.js
Run on android emulator or with FireTV
Do fast left/right key navigation with FireTV remote or with android-tv emulator's directional keypad.
You see the focus changing on navigation, but on fast navigation see the focus is Lost. This happens when you see empty scrolling without containers, you can stop here to load the items and see the focus is lost.
If you are running on android emulator and not seeing the issue, please make the app slow by configuring the following values in the test app provided.
Please configure the following values before running.

let TIMERS_COUNT = 35; // On FireTV 4k, you can just set to 0. On MAC with android-tv emulator set to 35
let MATH_LOOP = 2500; // on FireTV 4k, you can just set this to 1000 or calibrate this to see the issue with emulator running in MAC.
App.js.zip

if you are using this repo for making your tvos app, use TVFocusGuideView as mentioned in it's documents, it solves many issues regarding focus management in TVs

@DevineDecrypter This is not a solution to the problem, I am already using TVFocusGuideView and this is still an issue with flashlist.
I am not sure if @shyamsrj is still having this problem, but I certainly am.
Lets say you have a large flashlist full of items, and you want to have a border width around these items to show "focus", and you fast nav through the items by holding down the navigation key (right arrow, if using a horizontal flashlist + tvfocusguideview), the border width for the focus cannot keep up with the flashlist navigation, and furthermore freezes when you load more items with the flashlist. Any idea where to look to try and resolve this? It seems like an asynchronous issue, or something to do with the UI / JS thread being consumed.
CC: @shyamsrj


Feature Request:

Is your feature request related to a problem? Please describe.
Nope.
Describe the solution you'd like
Service "go to saved position". I'd like to reset camera to previously saved position. Maybe just to first/only saved position
Describe alternatives you've considered
Additional context

See service ptz documentation.


Make 'SplitContainer' update drawing only if actually needs to

@akien-mga This is more of something I forgot to edit in #26146 (without it, the handles flicker when dragging then with some speed) than an "enhancement", so it would be for the best to be squeezed in for 3.1.

Thanks!


feature Alter be to fetch vault info after creating storage vault

Proposed changes
Issue Number: close #xxx
Make BE eagerly fetches the vault info right after FE receives the create vault resp from MS.

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run feut

run buildall


Dependency compatibility issues with google.golang.org/api and cloud.google.com/go

Client
google.golang.org/api
google.golang.org/grpc
cloud.google.com/go
Describe Your Environment
In an AppEngine Flex Go service we use pubsub/spanner/datastore/firestore/firebase admin apis and "google.golang.org/api" for metrics and the spanner iterator and when building after running "dep init" we get this error message:
go src/lc-api-cover/vendor/cloud.google.com/go/firestore/query.go:163:40: too few values in struct initializer
We've had this message for a while and we could previously solve it using this in our Gopkg.toml but this no longer works:
[[override]]
 name = "github.com/golang/protobuf"
 version = "~1.0.0"

Expected Behavior
Our service builds even if we need to pin some dependencies
Actual Behavior
Dependency compatibility issues
go src/lc-api-cover/vendor/cloud.google.com/go/firestore/query.go:163:40: too few values in struct initializer

Do you have the latest version of this library? I just fixed that in https://github.com/GoogleCloudPlatform/google-cloud-go/commit/d011423af2899e53bf9981a5c0e5e54d5e7c7de2

Ah! Right on. Sorry about breaking y'all!

v0.23.0 is now released and has the fixes.


hotkeys: Disable n hotkey functionality if user cannot create streams.

Previously, a user could use the n hotkey in the stream subscriptions modal to open the Create new stream panel even though organization settings disabled a user from doing so. This commit prevents that from happening.

I ended up merging this as bd7d9da668a049de13fa30d5ceb7730e6a11892d, after adding a test and making sure to return false in the else case (which required a bit more changes due to lint).
Thanks for fixing this @synicalsyntax!


Add method generation / annotation generation

[ ] integrate generation of DependencyProvider basic Methods
[ ] integrate generation of the @method tags for following classes

[ ] /all -Factories
[ ] /all -Plugin
[ ] others to add here...

For example you can lookup the old Spryker IntelliJ Plugin: https://github.com/tobi812/idea-php-spryker-plugin
There is a @method generation


View header icons in Safari are off

Commit: higlass.io
Steps to reproduce

Open higlass.io in Safari

Observed behavior

Those view header icons are way to high!

Expected behavior

The height of the icons should be normal.

This problem is back.
Commit: Whatever is running on https://higlass.io/app today.
Steps to reproduce

Open https://higlass.io/app in Safari Version 12.1.1 (146<IP_ADDRESS>.1) on Mac OS X 10.14.5 (18F132)
Look at copy/settings/etc. controls for the main view.

Observed behavior

Controls for view are not shown where they belong.

Expected behavior

Controls are where they belong.

A hard reload fixed the issue for now.


Warnings in CI, looks not ran interactive mode

https://github.com/kachick/dotfiles/actions/runs/5714858903/job/15483004035?pr=225#step:12:8
warning: Could not set up terminal.
warning: TERM environment variable not set.
warning: Using fallback terminal type 'xterm-256color'.
warning: Could not set up terminal.
warning: TERM environment variable not set.
warning: Using fallback terminal type 'xterm-256color'.
starship 1.15.0
branch:
commit_hash:
build_time:19[8](https://github.com/kachick/dotfiles/actions/runs/5714858903/job/15483004035?pr=225#step:12:9)0-01-01 00:00:00 +00:00
build_env:rustc 1.70.0 ([9](https://github.com/kachick/dotfiles/actions/runs/5714858903/job/15483004035?pr=225#step:12:10)0c54[18](https://github.com/kachick/dotfiles/actions/runs/5714858903/job/15483004035?pr=225#step:12:19)06 [20](https://github.com/kachick/dotfiles/actions/runs/5714858903/job/15483004035?pr=225#step:12:21)23-05-31) (built from a source tarball),
not interactive and can't open terminal
compinit: initialization aborted
(eval):1: can't change option: zle
(eval):1: can't change option: zle

Similar of https://github.com/actions/runner/issues/241?
(https://github.com/kachick/times_kachick/issues/162)


Wiki page reference sequence

Hi @colindaven,
I created a Wiki page regarding the bulding of a reference sequence and added my notes to the page.
Now you can complete it.
Note: We use split_fasta_names_samtools.sh at one point. Should this be added to the repository or do we need another solution?
The content of the file is:
## Colin D., 2018 and 2020
## Splits a big multifasta into individual fasta files so they can be recombined
## Only extracts the files in the fa.fai (so you can delete some lines out of this,
## and have the genomes excluded from the out directory
## Uses a fasta index and samtools

#gen=refSeqs_allKingdoms_2020_03.fa
#gen=selectedgenomes.fa
#gen=all_1_cln_1strainperspecies.fa
gen=all_bact.fa.masked.fa

mkdir out

for i in `cut -f1 $gen.fai`
        do
        samtools faidx $gen $i > out/$i.fa
done

thanks Lisa ! Good point.
Maybe put that script in a subdirectory of scripts called eg ref_build


MM-14787 - Updating dropdown menu on mobile

Summary
MM-14787 - Updating dropdown menu on mobile
Ticket Link
https://mattermost.atlassian.net/browse/MM-14787

@saturninoabril @deanwhillier Removed that menu stuff for now.

Done cherry-pick to release-5.10


fix: refactor transaction page

Applying same refactor to transaction and address page

@He1DAr can you provide any context in the description about the changes being made here? Link any issues?

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


Web PDX UI - Setup project

As a developer I would like to have a "kitchen sink" to start working with for the new Web UI.

[x] Create repository
[x] Create new React project
[x] Install StorybookJS
[x] Create temporary logo
[ ] Create bootstrap theme
[ ] Create a General layout

[ ] Header bar
[ ] Footer

New repo can be found here: https://github.com/PDXFinder/pdcm-web-ui
And a public instance of our StoryBookJS installation can be accessed here: https://pdxfinder.github.io/pdcm-web-ui/


The diff coverage is 100.00%.

:exclamation: Current head bf4bff4 differs from pull request most recent head 0795909. Consider uploading reports for the commit 0795909 to get more accurate results

@@            Coverage Diff             @@
##             main      #41      +/-   ##
==========================================
+ Coverage   85.45%   90.42%   +4.97%
==========================================
  Files          48       50       +2
  Lines        1148     1180      +32
  Branches      108      109       +1
==========================================
+ Hits          981     1067      +86
+ Misses        126       83      -43
+ Partials       41       30      -11

Impacted Files
Coverage Δ

atv/decorators.py
100.00% <100.00%> (+30.50%)
:arrow_up:

documents/api/viewsets.py
95.94% <100.00%> (+5.94%)
:arrow_up:

services/utils.py
100.00% <100.00%> (+15.15%)
:arrow_up:

utils/test/test_exceptions.py
100.00% <100.00%> (ø)

utils/uuid.py
100.00% <100.00%> (ø)

documents/models.py
100.00% <0.00%> (+7.27%)
:arrow_up:

documents/serializers/attachment.py
100.00% <0.00%> (+9.09%)
:arrow_up:

services/signals.py
94.73% <0.00%> (+10.52%)
:arrow_up:

atv/exceptions.py
97.95% <0.00%> (+12.24%)
:arrow_up:

... and 3 more

Continue to review full report at Codecov.

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


[CELEBORN-141][IMPROVEMENT] Refactor error log about quota exceed

What changes were proposed in this pull request?
Make exceed log of quota show byte string, more human readable
Why are the changes needed?
Does this PR introduce any user-facing change?
How was this patch tested?

@waitinfuture @nafiyAix  Also need to backport to branch-0.2


Inject into the game converter display?? What do you do? Help me

Inject into the game converter display?? What do you do? Help me

*Changer, use the default dll injector with manual map


added column widths and fixed header option

added body and header wrapper css class options.
The purpose of this PR is to provide a height and a fixed header option to vuetable.
Mainly to address Issue 178.
I am not exactly sure what you need me to do in order to accept this PR (add docs maybe?) - So I will be more than happy if you could provide some feedback regarding what you need me to do in order for you to merge this pull request (assuming you want it).
The idea behind the implementation is taken from the markup of Element's table  where I build one table with only a header and one table with a body - thus allowing fixed scroll without the need for JS.
But - for the table header and body to be aligned with their column widths I had to add also a "width" option to the fields definition (which I felt that was missing anyway).
Fixed header is activated when you specify a tableHeight option - then the component renders the content of the table in the given height and makes the header fixed.
I modified the demo app to include a table with a fixedHeader and a height.
I just starting using your component yesterday and I implemented this today as I could not use the table in my system without having a fixed header.
Thanks.

@rubinsh Thank you very much for this PR. Many people have been looking for this feature.
One point that really stops me is that you're using width attribute on the th and td. Since the width attribute is not supported in HTML5 and it is recommended that we use CSS for styling this instead.

Good point @ratiw - I was not aware that it was deprecated in HTML5.
I will update my PR to use style attribute (and not CSS) as the width can be determined for each column separately.
Please let me know if you have other comments regarding the code - I will be happy to fix/explain

@ratiw - I've updated the code.
I also removed the witdth/style attributes from td elements as they were not needed and kept them only on the th elements and the colgroups elements.

@ratiw - I rebased the changes from upstream (your origin) to mine and did the merge.
Seems OK now.
If you are fine with the changes - please do merge this PR so I won't have to do the merge again next time.
Thanks!

@rubinsh Would it be possible to just leave out the style attribute and just specify the width of each column in the CSS? What do you think?

@ratiw - I don't think it is possible to programmatically  add css rules.
Assuming you have 10 different columns with 10 different widths - how will you define it in css?
You could add an option to the column config of something like "columnHeaderCSSClass" and have that option for each column and then set the width in that CSS class but that would be very uncomfortable from the API's perspective...
I modified the code so that the style attribute is only on the th and colspan elements - so performance wise it is OK and there is almost no performance penalty (or none whatsoever) for the inline styles in this case.
From the API perspective - I think it is much more comfortable and intuitive to just set a "width" attribute for each column as opposed to defining a  columnHeaderCssClass for each column and then write a css rule with the width for each column.
I am an experienced frontend developer - and I know that in 99% of the cases inline styles are a big no no - but I think that in this case it makes sense to use inline styles.
Also, using inline styles this way (and not css classes) allows you to programatically change the width of each column from Vue (assuming we would want to have re-sizable columns in the future)

@rubinsh Got it. Will find time to review it a bit and see there is anything that need to be added. Thank you very much for this. :)

Sure thing.
We will need to add documenation later after you approve, and maybe make
the demo app switch between fixed header and non fixed header in the table
settings.
Thank you for the great component :-)
On Oct 20, 2017 3:11 PM, "Rati Wannapanop"<EMAIL_ADDRESS>wrote:

@rubinsh https://github.com/rubinsh Got it. Will find time to review it
a bit and see there is anything that need to be added. Thank you very much
for this. :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ratiw/vuetable-2/pull/266#issuecomment-338188929, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAipi3kHtRaYHZoaGvYiAcJLu481oqEFks5suI3kgaJpZM4PslWN
.

@rubinsh I'm experiencing problem with column width inconsistency as shown in the following picture.

Something is causing the header to shift more to the right. Have you experiencing this?

Make sure you a width settings for all the columns.
Also make sure you are on my latest commit.
Which browser are uou using?
On Oct 21, 2017 4:14 PM, "Rati Wannapanop"<EMAIL_ADDRESS>wrote:
@rubinsh https://github.com/rubinsh I'm experiencing problem with column
width inconsistency as shown in the following picture.
[image: column width inconsistency in header and body]
https://github.com/ratiw/images/raw/master/vuetable-2/column-width-inconsistency.png
Something is causing the header to shift more to the right. Have you
experiencing this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ratiw/vuetable-2/pull/266#issuecomment-338393632, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAipiyADQYuDq0NSnuJshg5I039-A1Krks5sue4cgaJpZM4PslWN
.

@rubinsh I am on the latest commit and I'm using Chrome the latest version. After some tinkering, it seems that the problem is not on the header, but actually on the body of the table.
The v-scroll bar seems to cause the table body to shrink to accommodate its size resulting in the table itself adjusting the size by reducing each column size to reflect the changes. When turning overflow-y off, the column sizes seems to be ok.

You are correct.
This can happen if the scrollbar becomes visible and it was not visible
when the table was initially rendered.
What I did when using it in my app is to add the width of the scrollbar to
the last column of the table header if the scrollbar is visible.
I will include this code in the component.
I forgot about this as this was already a few weeks ago.
On Oct 21, 2017 4:43 PM, "Rati Wannapanop"<EMAIL_ADDRESS>wrote:
@rubinsh https://github.com/rubinsh I am on the latest commit and I'm
using Chrome the latest version. After some tinkering, it seems that the
problem is not on the header, but actually on the body of the table.
The v-scroll bar seems to cause the table body to shrink to accommodate its
size resulting in the table itself adjusting the size by reducing each
column size to reflect the changes. When turning overflow-y off, the column
sizes seems to be ok.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ratiw/vuetable-2/pull/266#issuecomment-338395924, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAipi513C7sLF10puhEc9OmpQDJJ0Qmrks5sufUIgaJpZM4PslWN
.

@ratiw - I've updated the code to address the issue you raised.
Now, when the scrollbar is visible - I add an invisible "gutter" column to solve the column widths offsets.
When the scrollbar is not visible - the column is removed.
This is the cleanest solution I could come up with and I'm pretty happy with it.
I also looked at what other libraries are doing to solve this and it's pretty much the same concept.

I have tried to implement by following the steps (defining width for columns and table height) but I am not getting a desirable outcome.
One element in field looks like:
{name: entry[0], title: entry[1].title,  width: "50px"}
I have passed down the table-height="600px".
Is there something I missed?


Add GetNearest method to the DB interface

Summary
There is an issue in cosmos-sdk: Make KVStore interface have methods to getNearest entry.
To address this issue, we can add a new method, GetNearest to the DB interface and implement it for all supported storage engines. This method should have a similar cost to the Get operation and provide a more efficient alternative to iterators for finding the nearest key.
// GetNearest retrieves the nearest key to the given key.
// If 'ascending' is true, the method returns the smallest key greater than the given key.
// If 'ascending' is false, the method returns the largest key smaller than the given key.
// In case there is no key in the desired direction, the method returns nil.
// CONTRACT: key, value read-only []byte
GetNearest(key []byte, ascending bool) ([]byte, error)

Once implemented, the method can be used in the cosmos-sdk repo to add a GetNearest function to the KVStore interface, as described in the original issue.

@babadro are you actively working on this?

@elias-orijtech
Not yet.
I was uncertain whether I correctly understood the concept and if the problem is still relevant considering the age of the original issue.
Hence, I decided to verify it by opening this discussion first.

I still believe that this would be valuable


Fix #2297: Enable branch coverage

Codecov Report

Merging #2317 into master will decrease coverage by -4.5%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master    #2317     +/-   ##
=========================================
- Coverage   77.56%   73.07%   -4.5%
=========================================
  Files         457      457
  Lines       19447    19447
  Branches        0     2739   +2739
=========================================
- Hits        15084    14210    -874
+ Misses       4363     4304     -59
- Partials        0      933    +933

Impacted Files
Coverage Δ

...i-iot/azure/cli/command_modules/iot/_validators.py
55.55% <0%> (-22.23%)
:x:

...evice/lib/operations/iot_hub_devices_operations.py
60.51% <0%> (-21.89%)
:x:

...i-acr/azure/cli/command_modules/acr/_validators.py
57.89% <0%> (-21.06%)
:x:

src/azure-cli-core/azure/cli/core/_environment.py
60% <0%> (-20%)
:x:

.../network/mgmt_nic/lib/operations/nic_operations.py
64.81% <0%> (-16.67%)
:x:

...gmt_app_gateway/lib/app_gateway_creation_client.py
70.27% <0%> (-16.22%)
:x:

...odules/network/mgmt_nsg/lib/nsg_creation_client.py
70.27% <0%> (-16.22%)
:x:

...t_vnet_gateway/lib/vnet_gateway_creation_client.py
70.27% <0%> (-16.22%)
:x:

...local_gateway/lib/local_gateway_creation_client.py
70.27% <0%> (-16.22%)
:x:

...nd_modules/acs/mgmt_acs/lib/acs_creation_client.py
70.27% <0%> (-16.22%)
:x:

... and 97 more

Continue to review full report at Codecov.

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


Update qbraid.ipynb

When https://github.com/ionq-samples/getting-started/pull/49 was merged, qBraid-SDK v0.7 was still in pre-release, which is why the integration tests failed.
qBraid-SDK v0.7 has now been released, and you no longer need to install the qbraid[runtime] extra to import the qbraid.runtime.ionq.IonQProvider. In fact, the runtime extra doesn't exist anymore. All of the necessary requirements to use the IonQProvider are now included in the qBraid-SDK's core dependencies.
See also: https://docs.qbraid.com/sdk/user-guide/providers/ionq

thank you for the fix :)


Trying to load area description that doesnt exist...

Happens in: Carnivores: Mandibles
Trying to load AREA8.TXT which doesn't exist, there are only 6 areas in the game.

This occurs due to the _RES having 8 entries for areas in the prices {} block.
Changing the code to verify if there are actual .MAP files for those indexes, if there isn't, we don't bother trying to find any other files and ignore the price entry.


Changed React to React Native in README.md

Referencing #16142

@facebook-github-bot shipit

Thanks for contributing!


use a Boolean class

Can we make DDNode an instance of (a class like) https://hackage.haskell.org/package/ersatz-0.3.1/docs/Ersatz-Bit.html#t:Boolean ?
If yes, then we could write  polymorphic formulas: one piece of code that produces a formulat that I can

evaluate, given an assignment
ask a SAT solver for a model
ask a BDD implementation for number of models, etc.

But no, we cannot, since we need the DDmanager. Or - we can do as ersatz does, and just construct an AST, which will be sent to a back-end only later. This needs observable sharing (in ersatz: to detect whether we already Tseitin-transformed an expression to a literal, in cudd: whether we already have the DDnode for the expression). Looks like another optional layer for the Cudd API.

Sounds like another good interface. However, I think it would be best to keep this library as a relatively low level wrapper around CUDD that more advanced interfaces like the one you're proposing can be built on top of.
I can point to this separate package from my readme for people who are looking for a nicer high level interface.

I made this: https://github.com/jwaldmann/cudd-ersatz

Looks nice! Would you like me to link to it from readme in my CUDD bindings? Is it mature enough yet?

I'd appreciate if you reference cudd-ersatz. Mature? Well, I have a few tests that show that it works, but I'm quite sure I need to add more stuff to the API for convenience. E.g., for getting (some, all) models, I should like to have something like https://hackage.haskell.org/package/ersatz-0.3.1/docs/Ersatz-Codec.html#t:Codec .

I have referenced it in the markdown readme as well as the cabal file.


 This part simply enables the use of SIGKILL and SIGTERM as constructs in the signal map. They don't actually relate to signals in the Unix sense, since Windows does not support signals.
This PR will actually start docker kill working against a Windows daemon, as opposed to erroring out immediately, just it will always go through an attempt at graceful shutdown, not the forced shutdown. That'll be fixed in part two...

LGTM

Except from the typo, LGTM 🐶

Ugh, corrected comment.

LGTM waiting janky

janky is happy, merging


Upgrade Feast to 0.34

This is temporarily blocked due to some dependencies in the latest version of feast. Will revisit in the future.

I'll merge this after all. The problem initially was that the new feast version requires a lower version of typeguard and it conflicts with pandera. But having this upgraded is more critical than pandera, we can remove the use of it.


flask based REST api for generating event hash

Hi @RalphTro and @Echsecutor,
As part of EPCIS 2.0 prototype, we intend to integrate this event hash generator. It would be nice to treat it as an internal micro service which exposes REST endpoint for generating hash of EPCIS event passed as part of request.
To be able to achieve that, I have added flask based REST api under webapi directory and also added required files to prepare docker container which will make the deployment in various environments consistent.
Please suggest if any parts required improvement or not in-line with normal python development.
Looking forward to your feedback.
Cheers,
Bhavesh

Many thanks for adding this web service functionality which is much better than the simpler container which just whatches a folder for new files and hashes them.

Hi @Echsecutor, Thank you so much for taking time to review the changes and providing valuable feedback. I am glad that you are finding webapi more convenient for end users. All your suggestions are incorporated.
I will raise separate PR to supply hashing algorithm as part of POST request. Thinking to pass it as URL query param. Let me know if prefer to do it via request header.
Whenever you find time please review the commit again.


Implement WiFi Long Range

The long range is a feature that increase the range of the wifi but it changes also the format so it is not possible to connect with the module using the standard wifi connection (works only between the modules).
I already tried and found not easy to use / debug.
Do not seems to be a big interest

Yes, this seems to me a very special use case, which is already covered by other techniques.


Merge master into release for next version

Merge master into release for next version

@bot-gradle test and merge

No milestone for this PR. Please set a milestone and retry.

@bot-gradle test and merge

I've triggered a build for you.


Support for WebGL2 and GLSL 3.0 shaders.

Commit to close #1575
Determine WebGL2 support via canvas capabilities via MapView
Use new glslVersion setting (as of<EMAIL_ADDRESS>in ShaderMaterials to support GLSL 3.0 features.
Signed-off-by: Jose Rojas<EMAIL_ADDRESS>

Unfortunately I don't have much time to fix these tests. The code works well for me. If anyone would like to address the intergration tests, I'd appreciate it.

@harpgl-bot retest this please

Closing, because this was superseded by: https://github.com/heremaps/harp.gl/pull/1887


CalDAV: RELATED-TO doesn't get set when dragging a task into another to make it a subtask

With a CalDAV backend, when creating a subtask in Errands, the RELATED-TO field in the CalDAV VTODO is set to the ID of the parent task to indicate the relationship (as Apple Calendar does).
However, if a task is created and then dragged into another task to make it a subtask, the field does not get set correctly.

Is it fixed in the last update?

Radicale with Errands 46.2.1, but there were more serious problems with the sync logic that led me to stop using Errands for now to avoid data loss.

It's not working well with radicale servers.


Port to 1.19.3

Ports the mod for use in 1.19.3

Commits merged onto new branch by 8fb3935804d09a769b720772d86ed646a2750b00 to retain authorship and separate codebases for incompatible MC versions.
Thanks again. Will make a release soon.


Tear-off: expression is not evaluated to object

According Dart spec "16.18.3 General Closurization"
"Evaluation of a property extraction i of the form e#m proceeds as follows:
First, the expression e is evaluated to an object o. Then:..."
But in fact expression is not evaluated to object o. Run the following program
class A {
  int get g => 1;
}

class C {
  A get m => new A();
}

main() {
  C c = new C();
  var x = c.m#g;
}

Result: error: semicolon expected
var x = c.m#g;
var x = (c.m)#g works well.
Tested on Dart VM version: 1.13.0-dev.2.0 (Tue Sep  8 05:28:05 2015) on "linux_x64"

The behavior is what the current grammar specifies:
postfixExpression:
  assignableExpression postfixOperator |
  primary (selector* | ( ‘#’ ( (identifier ‘=’?) | operator)))
  ;

This means that you can't put a "#foo" after a selector like .m - you can do either, but not both. It does work when you wrap it in parentheses because a parenthesized expression is a primary.

Isn't it a contradiction with
Evaluation of a property extraction i of the form e#m proceeds as follows:
First, the expression e is evaluated to an object o.?
According this statement getter invocation should be evaluated to the object which is  value of the getter

It's not a contradiction, it just doesn't stand on its own.  You have to read that section along with the grammar as @lrhn did above.
Consider the analogous: Evaluation of an multiplication expression of the form e0 * e1 proceeds as follows: first the expression e0 is evaluated, then the expression e1 is evaluated, then the result is multiplied.
Now, would you expect x * y + z to first evaluate x, then evaluate y + z, then multiply the results?  That's not what actually happens, because if the precedence rules encoded in the grammar.

Over to Gilad to validate that the VM's approach is correct here.

What about this?
class A {
  int m() => 1;
}

A getA() {
  return new A();
}

main() {
  var f = getA()#m;
}

Result:
error: line 24 pos 17: semicolon expected
var f = getA()#m;
^

getA()#m is still not valid syntax. The grammar allows either a tear-off operation or a "selector" chain (call or member access, basically) after a primary expression. Here you do getA() which is not a  primary expression (getA is a primary expression, getA() has the call selector after it so you can't also have a tear-off). Again you need to write (getA())#m if that is what you want to do.

Ok, thank you for clarification. But I think  this grammar is, at least, not obvious at this point and the above is not what Dart user, not deeply familiar with the specification and sophisticated syntax like 'primary (selector* | ( ‘#’ ( (identifier ‘=’?) | operator)))', expects.
getA().m works, getA()#m not. Why? Why this limited (limited comparing with '.') syntax is needed at all?

Generalized tear-offs are being removed (#27518) so I don't think we have to worry about this.


Add React 18 as peer dependency.

Updates the React package to accept React v18 as a peer dependency.
Closes #41

Available at<EMAIL_ADDRESS>


NumberField initial documentation

🙋 Documentation Request

This is an issue for the initial NumberField documentation. It should include react-spectrum and the aria hooks documentation.
🧢 Your Company/Team

closing in favor of https://github.com/adobe/react-spectrum/issues/1482


[source stability] Updating the known source breaking changes file

Intents API has been fixed in a source incompatible way, and that was caught by the api-digester test.

@swift-ci Please smoke test and merge


Remove excessive quoting of arguments in Makefile.prebuild again

fixes #3755 , bug introduced in #3722

tested and closes #3755


Add test cases for ParseIdentity function

Added coverage for wrong separator scenarios

Please provide a description of this PR:
Add test cases for ParseIdentity function

Added coverage for wrong separator scenarios

Hi @shimengwang. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@shimengwang: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio
38296d543c9ed7d63df3cede00a85e20ab59c729
link
unknown
/test integ-basic-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

/test integ-basic-arm64


RTK Correction topic exposed on microRTPS

gps_inject_data Topic is exposed on microRTPS bridge enabling the use of RTK base corrections

Please make these into one commit (squash the commits and force-push the pr)  . Looks cleaner in git.history afterwards :) Then it is good!


Add santatra.html

your filename must be nirinarisantatra.html

Doing this instead of #65

Thank you very much @RaidAndFade !


Scaling up an auto scaling group fails

Scaling up an auto scaling group fails because the instance is not in service yet (Pending:Wait while CodeDeploy deploys) and the deregister script fails to set the instance to OutOfService.

Thanks for the pull request!


Trailing comments break subsequent comments

I have a rustfmt.toml like this:
max_width = 79
comment_width = 79
error_on_line_overflow = true

and a line like this:
pub const IFF_MULTICAST: ::c_int = 0x0000000800; // Supports multicast
// Multicast using broadcst. add.

gets incorrectly formatted into a line like this
pub const IFF_MULTICAST: ::c_int = 0x0000000800; // Supports multicast
                                                 // Multicast using broadcst. add.

notice that the  comment is incorrectly wrapped to the right, and that as a consequence the 79 character limit is not satisfied after formatting, such that a subsequent rustfmt --check fails.

Related to #2996


enable sharing tests

[ ] API test
[ ] UI tests

Questions to discuss:

in ocis every share needs to be accepted first, how should we deal with that in the tests

make the step Given parameter "shareapi_auto_accept_share" of app "core" has been set to "yes" set some flag, so that the tests know to accept shares without it being mentioned in the Gherkin
duplicate tests

in OCIS shares are accessible via the Shares folder.

make the test be aware of that, so that it does not need to be mentioned in the Gherkin. But how to deal with when the tests check the existence of files/folders? The test code would have to know that this particular item is to be expected in the Shares folder or outside.
add %SharesFolder% in front of every item that is expected to be a Share, in ocis-tests substitute that to Shares. This would not work for tests that expect the receiving item to ass (2) to the name if an item with the same name exists
duplicate tests

CC @phil-davis @dpakach @PVince81 @kulmann

Also see https://github.com/owncloud/ocis-reva/issues/415 - which is a more general issue to enable as many API test scenarios as "reasonable" so that they are run in CI, listed in expected-failures and "ready to be made to pass"

Note: PR https://github.com/owncloud/core/pull/37774 did enable a small number tests that happened to pass.

core PR https://github.com/owncloud/core/pull/37881 has the way forward for this. It creates new sharing scenarios that have share_folder set to Shares and auto-accept of shares off. That corresponds to the default OCIS settings. Those new scenarios run on both ownCloud10 and OCIS. See the PR for a detailed description of what is done with tags, scenario background, accepting received shares etc.
This issue can now be assigned to someone to do similar with the remaining sharing API tests.

I moved this to ToDo in Sprint 20-17 because there seems be no other sprint to choose.

[ ] apiShareReshare1

[ ] apiShareReshare2

[ ] apiShareReshare3

@HariBhandari07 please also assign anyone else who is working on this.

WebUI Tests

[ ] webUIResharing
[ ] webUIRestrictSharing
[ ] webUISharingAcceptShares
[ ] webUISharingAutocompletion
[ ] webUISharingExternal
[ ] webUISharingFilePermissionMultipleUsers
[ ] webUISharingFilePermissionsGroups
[ ] webUISharingFolderAdvancedPermissionMultipleUsers
[ ] webUISharingFolderAdvancedPermissionsGroups
[ ] webUISharingFolderPermissionMultipleUsers
[ ] webUISharingFolderPermissionsGroups
[ ] webUISharingInternalGroups
[ ] webUISharingInternalUsers
[ ] webUISharingNotifications
[ ] webUISharingPermissionsUsers

Webui tests to enable in CI

[ ]  webUIResharing
[ ]  webUIRestrictSharing
[ ]  webUISharingAcceptShares
[ ]  webUISharingAutocompletion
[ ]  webUISharingExternal
[ ]  webUISharingFilePermissionMultipleUsers
[ ]  webUISharingFilePermissionsGroups
[ ]  webUISharingFolderAdvancedPermissionMultipleUsers
[ ]  webUISharingFolderAdvancedPermissionsGroups
[ ]  webUISharingFolderPermissionMultipleUsers
[ ]  webUISharingFolderPermissionsGroups
[ ]  webUISharingInternalGroups
[ ]  webUISharingInternalUsers https://github.com/owncloud/phoenix/pull/4161
[ ]  webUISharingNotifications
[ ]  webUISharingPermissionsUsers https://github.com/owncloud/phoenix/pull/4161


ChaCha20 support

Is there any plan to add ChaCha20? Thanks.

You could temporarliy use this, since I needed chacha20 in Dart as well: https://github.com/gi097/salt

No plans to add anything. I'm not even maintaining really anymore except when someone finds a real bug.
You're very much encouraged to provide an implementation of ChaCha20 for PointyCastle. I'd happily spend the time reviewing it.

You could temporarliy use this, since I needed chacha20 in Dart as well: https://github.com/gi097/salt

Thanks, I'll try it.


import Hello ^ Syntax Error

As a beginner, it is kind of hard to figure out what syntax is supported out of the box. For example

let Hello = 'Hi';
export default Hello;
import Hello from './components/hello';
console.log(Hello);
..will throw the error: "Hmmm. We're having trouble parsing a file.".
More clear docs/readme regarding what syntax to use would be awesome.

Oh, that's odd — I'm not getting the same error for similar code. Could you perhaps create a repro? Thanks!

Seems like I missed the crucial part that generated the error. Here is a rep to replicate: https://github.com/jhammars/bankai-import-hello
, where this commented line somehow is causing the error: https://github.com/jhammars/bankai-import-hello/blob/master/src/index.js#L1

It looks like the sheetify transform does not like the import line.
https://github.com/choojs/bankai/blob/master/lib/graph-script.js#L53
Commenting it out the sheetify transform allows this to run.
I tried moving the sheetify transform to after the babeliy transform, but the error is still thrown. :(

Oh interesting!
If the // sheetify comment is removed from here:
https://github.com/jhammars/bankai-import-hello/blob/master/src/index.js#L1
Then it works!
I think this is related to https://github.com/stackcss/sheetify/issues/131

Yes, It's a little peculiar. The word "sheetify" is explicitly causing the error, even when it is in a comment. Spell sheetify wrong and you are all good =)
And yes, it looks like it is related to stackcss/sheetify#131

The problem for me personally, as a JS beginner, is that I have no clue how to use sheetify in combination with ES6 module syntax.


docs: rif marketplace services guide

What

set up automatic copying and post-processing of RIF Marketplace User Guide via cpdoc
added nav menu items
fix existing <li> and <ul> nesting issues within left nav menu

NOTE: To be pedantic, this was not related to this PR, but was necessary to fix for the menu items that are being added as part of this PR

Why

lead up to launch of RIF marketplaces
more documentation is good!

Refs

task

which personal account is displayed?

Hackmd users

We can remove that. We dont need to put link to the HackMD.


Adding Git log chapter

Hey I started working on the topic for git log, I will be keeping this as a draft request as I work on the branch

I think the chapter content is done @woojiahao.
Hopefully can get your comment on the above change and maybe we can start adding the final touches before merging :D
I think all that is really left is to proofread, add the link to the readme at root.

Hi, um I'm not sure if editing the suggestions through GitHub or directly changing them and pushing the changes is better.
Let me know cause I think I should have resolved them on github before pulling them down.

Could you re-export the PDF and name it as git-log.pdf instead? I'm currently going over the changes made :+1:

Could you re-export the PDF and name it as git-log.pdf instead? I'm currently going over the changes made

Will do after this batch of changes are done

Above review was outdated, made a new review so as to allow for changes

PDF export is also added with the above commits

Updated the pdf and removed the table of contents from the readme.
I think the main readme could be started on, although I'm not sure how it would look like and what topics would be inside it.

Hey! The I've gone over the recent changes and they look great! I think we are ready to merge this. Let me know whenever you are ready to modify the main README and you can add the timestamp. In the table of contents, you can add a sub-list to section seven like so:
7. Advanced Git
    1. `git log`

Looks good!  Thank you for investing your time into writing this guide!

Thanks, hopefully, we can work on more of the advanced chapters together :D.

Hey! The I've gone over the recent changes and they look great! I think we are ready to merge this. Let me know whenever you are ready to modify the main README and you can add the timestamp. In the table of contents, you can add a sub-list to section seven like so:
7. Advanced Git
    1. `git log`

For now, I think I'll add a commit to say WIP and the starting of the list of chapters there.
Hopefully, after that, we can release this chapter.

Looking good to merge! Thank you so much for all your hard work, @chuanhao01 ! :smile:

Oh no seems like there is a few more changes haha :D

Oh dear! :scream: Please make a separate PR :joy: My bad :sweat_smile: