debugger

@x1unix
Really learned alot from this project. I am needing to run many golang wasm workers, and i can see now how you did it.
The GUI is very snappy fast !

You might like this. Its is a golang debugger written in golang.  The GUI / IDE is also golang.
It connects to standard delve.
It currently won't run in the browser because of the local FS calls, but with a remote FS over http it would.
https://github.com/gioui/gio-cmd/tree/main/gogio can be used for building for different targets such as wasm ( web ), but also mobile and desktops.

I presume that all compilation is occurring on the google go play server. Even the "Run program in browser as WebAssembly module" option ?

@gedw99 regarding WebAssembly, there are 2 modes:

First option: builds a wasm program on our server.
Second option: Go Interpreter.

Second option supports third-party packages, but not very stable at the moment.
Thanks for a link, I'll take a look.

@gedw99 if you're interested in WebAssembly Go internals, please take a look at our Go interpreter WASM module source.
https://github.com/x1unix/go-playground/tree/master/internal/gorepl
One of interesting topics is custom FS mocking and custom wasm syscalls without syscall/js overhead.


ObjectPage: async creation of block views

OpenUI5 version: 1.58.5
Browser/version (+device/version): Chrome 70
Hello,
Lately, I was checking my application with support assistant and found the following:
The XML view 'MyPageBlock' is loaded synchronous. Please take a look at the resolution 'Instantiating Views'.
I was trying to find something about the async block view creation in the BlockBase documentation, but didn't find anything. So, I just tried to add an "async": true to my block view definition:
		metadata: {
			views: {
				Expanded: {
					viewName: "MyBlockView",
					type: "XML",
					async: true
				} ...

It's sorta helped - I don't see this error anymore, but I found another issue - this.oParentBlock became undefined in the block's controller.
Could you give me some advice on this or is it a bug?
Thanks!

Hello @whydrae ,
Thank you for sharing this finding. I've created an internal incident<PHONE_NUMBER>. The status of the issue will be updated here in GitHub.
Regards,
Georgi

Hi @whydrae,
Can you provide some more code samples and explanations in order to understand the issue better?
Thanks,
Georgi

Hi @GeorgiValkanov,
Go to https://sapui5.hana.ondemand.com/#/sample/sap.uxap.sample.ObjectPageBlockBase/preview page and run Support Assistant with rule "Asynchronous XML views". In the log you'll see a lot of warnings on blocks, for example "The XML view 'BlockBlue is loaded synchronous. Please take a look at the resolution 'Instantiating Views'.".
Could this be a Support Assistant issue?
Best regards,
Ilya

Hello @whydrae ,
The information you provided is not enough for us to be able to analyze what the problem is.
Could you please make a simple example in JSBin , so we can check what is wrong with it?

Hi,
This issue is expected to be reported by Support Assistant. One should also not make the views async as this is not expected to work correctly. The ObjectPage's BlockBase currently loads views using an older, synchronous API. Converting this functionality to become based on asynchronous API is a task our team plans to execute in the near future and an internal backlog item is created.
I am closing this issue now and stay posted for details on this feature in the next releases.
Best regards,
Jordan

Hi, is there a plan when this feature will be available? Version 1.xx?

Since https://github.com/SAP/openui5/commit/773800eb93677a66b43d21e51f091723cf1d45f6, the BlockBase creates views always asynchronously. And the oParentBlock is available in the onParentBlockModeChange handler of the controller.
return Controller.extend("...", {
  onParentBlockModeChange: function(sMode) {
    // this.oParentBlock is available here
  },
  // ...
});


Change raining gold to x0 rounds except x00 rounds

Also did some refactoring in code related to raining gold rounds

Request looks good to me.  It makes sense to use Raining Gold on non-wormhole boss levels instead of wormhole levels where we don't want to do damage.

Currently low priority due to lack of relevance for RG.


Feature request: Webview console output event

I would like to be able to read the webview console, for tracking js errors and debugging information.
something like: webView:addEventListener("console", cback)

We got it by adding console output after the # in the url, then the app gets advised of a URL change and you can grab the console output:
eg http://yourpage.html?console=blahblahblah

We got it by adding console output after the # in the url, then the app gets advised of a URL change and you can grab the console output:
eg http://yourpage.html?console=blahblahblah

I know, i can send messages between webview/lua with this hack - a good thing, but its dont related to this issue - send messages between relams is not a goal.


Support for fully offline search like PWAs

Pagefind is a great project and a boon to static/JAM stack websites.
I run a blog that is also a Progressive Web Application (PWA) and I thought as page find is fully client side it would work offline for a PWA. Unfortunately, that was not the case, the main blocker I found was the metadata timestamp call. I have made sure that all the .pf_fragment, .pf_index, .pagefind, pf_meta files are cached by the service worker, still when the server is not there, the /_pagefind/pagefind.pf_meta?ts={current-ts} fails and the search fails too. Is there a way to also be cached by the service worker so that the search works offline? May be not the latest index but whatever was cached. I may be oversimplifying it.
Patch fix
If I force remove the ?ts={current-ts} it kinda works fully offline, is there a way to remove it with a flag or something?

I'm not particularly on top of PWAs, but I could definitely add an option for configuring that query parameter. That would let you specify a custom query parameter rather than using the timestamp automatically, but would still allow you to set a new parameter on each build if you ran into caching issues. I'll wire that up 🙂

@bglw that would be really helpful, then I can replace my google search with Pagefind and it will work fully offline too.

Grand! I'll include that in the next release.

Hi @geshan — unfortunately there wasn't a super simple way to drop this in with the latest release. This file is loaded on initialization before any options get passed to Pagefind in the browser, so there isn't a great way to connect this to a flag in a nice way. (and I'm hesitant to make it a build-time flag)
For now, after running pagefind you could automatically patch out that query parameter each time:
# Linux
pagefind && sed -i 's/?ts=${Date.now()}//g' public/_pagefind/pagefind.js

# MacOS
pagefind && sed -i '' 's/?ts=${Date.now()}//g' public/_pagefind/pagefind.js

I will keep ruminating on this though and try find a better solution that I'm comfortable with 🙂

Sounds fine for now, thanks!

Hi @geshan — unfortunately there wasn't a super simple way to drop this in with the latest release. This file is loaded on initialization before any options get passed to Pagefind in the browser, so there isn't a great way to connect this to a flag in a nice way. (and I'm hesitant to make it a build-time flag)
For now, after running pagefind you could automatically patch out that query parameter each time:
# Linux
pagefind && sed -i 's/?ts=${Date.now()}//g' public/_pagefind/pagefind.js

# MacOS
pagefind && sed -i '' 's/?ts=${Date.now()}//g' public/_pagefind/pagefind.js

I will keep ruminating on this though and try find a better solution that I'm comfortable with 🙂

It works for now and also works in GitHub Workflows. And yes, it needs a better solution.

Ah, I had forgotten about this issue but I'll pencil in proper support soon! As of Pagefind 1.0, the file is not loaded  on initialization, and passing options could totally influence this behavior, so I can certainly add an option to resolve this. I'll target the next release for that 🙂

this feature is important many people use lunr over pagefind because it works fully offline
i maneged to cache everything on the pagefind folder even the entry.json but when it dose the ?ts= it dosen't work because it can't get date offline


Test 8.2.08 does not properly URL encode the _outputFormat query param for Bulk Data v2

The request does not properly encode the + in the _outputFormat=application/fhir+ndjson, leading servers to interpreting that as a space potentially.
This may cause some servers (include HAPI at the time of this ticket) to reject the request due to an unknown output format request.

This is addressed in #242


fix: #1066

Change: English -> Plain English
Change: Linguist -> Linguistic

Codecov Report

Merging #1075 (3808566) into main (e0abf59) will increase coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1075      +/-   ##
==========================================
+ Coverage   78.31%   78.33%   +0.01%
==========================================
  Files         151      151
  Lines        5534     5534
  Branches      886      886
==========================================
+ Hits         4334     4335       +1
  Misses       1067     1067
+ Partials      133      132       -1

Impacted Files
Coverage Δ

src/CreeDictionary/CreeDictionary/views.py
62.50% <0.00%> (+0.59%)
:arrow_up:

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 e0abf59...3808566. Read the comment docs.


entortill, dehypnotizing

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.4
logical conflict every: 100
sleep for: 300s
[pullrequest]
requests per hour: 30
deps=[d,e]

/trunk merge


issue #109 refactor data.py

Pull Request
Description
The pvnet_app/data.py had multiple functions in it. A new folder within pvnet_app called data is created and within it two files: satellite.py and nwp.py are made, each having appropriate functions from the previous data.py. Appropriate changes to test have also been made to ensure that there are no errors during imports from pvnet_app/data/satellite and pvnet_app/data/nwp
Fixes #
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.
Please also list any relevant details for your test configuration

[ ] Yes

If your changes affect data processing, have you plotted any changes? i.e. have you done a quick sanity check?

[ ] Yes

Checklist:

[Yes] My code follows OCF's coding style guidelines
[Yes] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[Yes] I have checked my code and corrected any misspellings

Ive just updated the repo so it runs on numpy>2. Have you been able to run the tests locally? Looks like there might be some relative path dependencies - https://github.com/openclimatefix/pvnet_app/actions/runs/10139748337/job/28033615438#step:6:111

I tried changing the relative path problems which was in nwp.py

@all-contributors please add @DivyamAgg24  for code


Enable collateral conversions

In order to maximize yield and minimize risk, the OETH strategists (and the community at large) need to be able to adjust the makeup of the vault collateral periodically. For example, during one of last year's USDT scares, we voted to swap all of our USDT for DAI temporarily. Another example from OUSD is when voters elect to increase our Morpho Aave USDT position beyond the amount that we're currently holding. OUSD has long since been able to swap collateral because it includes a Curve 3pool strategy. The strategists are able to conver DAI to USDC, for example, by depositing DAI into the Curve 3pool strategy and then withdrawing USDC from the same pool. Sometimes there are costs or slippage associated with this but we at least have the capability and can do a cost-benefit analysis before taking the action.
OETH doesn't have the same capabilities. There is no existing strategy in place to be able to use as a swapping mechanism. This is important for OETH because of the diversity of collateral types and the increased likelihood of volatility. While OUSD has a default, yield-generating strategy for each of its supported collateral types (DAI, USDC, USDT), it's never stuck holding stagnant USD. OETH, however, is currently stuck holding [w]ETH that is not earning yield. We don't have any basic single-sided strategies to earn yield with ETH. We also may need to diverify LSD holdings if everyone mints with stETH and we want greater decentralization or higher yield from rETH and frxETH.
Ultimately, there are two near-term objectives:

Make it possible for the collateral to be converted from one supported asset type to another
Limit this capabilty to the strategists rather than exposing it to decentralized actors or being automated (for now)

Implementation tasks

[ ] #1539
[x] #1540

I'll do the analysis and solution design in Notion https://www.notion.so/Analysis-of-OETH-Collateral-Swapper-1d9d8b2d2b104968ad81c734d161fe58

The solution design decisions have been reviewed and agreed with the DeFi team.
https://www.notion.so/813478cd16c84f3bb869a5e6ff0a2eda
Work not progresses to implementation.

This is now being deployed with PR https://github.com/OriginProtocol/origin-dollar/pull/1655


Undefined symbols for architecture arm64

--- xcodebuild: WARNING: Using the first of multiple matching destinations:
{ platform:macOS, arch:arm64, id:00008103-001E08202ED9001E }
{ platform:macOS, arch:x86_64, id:00008103-001E08202ED9001E }
Undefined symbols for architecture arm64:
"OBJC_CLASS$_FlutterAppDelegate", referenced from:
type metadata for macdeskfac.AppDelegate in AppDelegate.o
"OBJC_CLASS$_FlutterViewController", referenced from:
objc-class-ref in MainFlutterWindow.o
"OBJC_METACLASS$_FlutterAppDelegate", referenced from:
OBJC_METACLASS$__TtC10macdeskfac11AppDelegate in AppDelegate.o
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
run on Mac mini (M1, 2020).
please help

On my M1, everything runs like a charm. Which version of Flutter are you using? Mine is 3.0.5

在我的 M1 上，一切都像魅力一样运行。你使用的是哪个版本的 Flutter？我的是 3.0.5
Flutter 3.1.0 • channel beta • https://github.com/flutter/flutter.git

On my M1, everything runs like a charm. Which version of Flutter are you using? Mine is 3.0.5

Flutter 3.1.0 • channel beta • https://github.com/flutter/flutter.git
Framework • revision bcea432bce (3 months ago) • 2022-05-26 09:05:34 -0700

remove your macos folder and let Flutter 3.3.8 re-create it. This Solved it for me.

Please try updating to the latest bitsdojo_window version.


Implement CodeTalk extension for VS Code

We are looking for help from community members who might be interested in implementing a CodeTalk extension for VS Code.
@suiyengar from the CodeTalk extension can provide more details if there are interested community members.
@sana-ajani maybe we should note this issue for the next time MS opens accessbility challanges.
More about CodeTalk extension which currently exists for Visual Studio https://github.com/microsoft/CodeTalk
https://github.com/microsoft/CodeTalk/issues/11

@venkateshpotluri is interested to work on this. So if more people are interested it would be best to coordinate with him.

No further actions planned here. Though work on the extension side is appreciated of course.
Thus closing this for now.


Add v3 txes to versioned_constants.

This change is

Codecov Report
Attention: 2 lines in your changes are missing coverage. Please review.

Comparison is base (0af8a3e) 69.88% compared to head (e2362d6) 69.88%.

Files
Patch %
Lines

crates/blockifier/src/versioned_constants.rs
50.00%
0 Missing and 2 partials :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1500      +/-   ##
==========================================
- Coverage   69.88%   69.88%   -0.01%
==========================================
  Files          59       59
  Lines        8180     8181       +1
  Branches     8180     8181       +1
==========================================
  Hits         5717     5717
  Misses       2005     2005
- Partials      458      459       +1

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


Suggestion

can you add a autowall?

it already exists in the cheat, turn off visible only in aimbot settings to activate autowall

turn on autoshot and turn off visible only


Update zio, zio-test, zio-test-sbt to 1.0.7

Updates

dev.zio:zio
dev.zio:zio-test
dev.zio:zio-test-sbt

from 1.0.6 to 1.0.7.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "dev.zio" } ]

labels: library-update, semver-patch

Superseded by #115.


Fix og image meta links to link to the correct domain and not build url

add NEXT_PUBLIC_SITE_URL=http://localhost:3000 to your local .env

NEXT_PUBLIC_SITE_URL

done


Request limit

Added limit support in get_all()

Coverage increased (+0.03%) to 95.736% when pulling c092595b2550f2e590f4822c7b737cd5facc2577 on request-limit into b400758d9127713946a31187fda8d9d67c1c2861 on branch0.3.2.


Failure to overwrite settings with python lib usage

I should be able to change the username, host, and password when executing a tower-cli command. I should still be able to do this when importing it in python and executing that same command.
That does not appear to be working. Consider the following, performing a list of users, giving a new value for tower_host.
>>> user_res.list(verbose=True, tower_host="http://localhost")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/alancoding/.virtualenvs/cli2/lib/python2.7/site-packages/ansible_tower_cli-3.0.1-py2.7.egg/tower_cli/models/base.py", line 732, in list
    response = self.read(**kwargs)
  File "/Users/alancoding/.virtualenvs/cli2/lib/python2.7/site-packages/ansible_tower_cli-3.0.1-py2.7.egg/tower_cli/models/base.py", line 516, in read
    r = client.get(url, params=kwargs)
  File "/Users/alancoding/.virtualenvs/cli2/lib/python2.7/site-packages/requests/sessions.py", line 487, in get
    return self.request('GET', url, **kwargs)
  File "/Users/alancoding/.virtualenvs/cli2/lib/python2.7/site-packages/ansible_tower_cli-3.0.1-py2.7.egg/tower_cli/api.py", line 137, in request
    'Right now it is: "%s".' % settings.host
tower_cli.utils.exceptions.ConnectionError: There was a network error of some kind trying to connect to Tower.

The most common  reason for this is a settings issue; is your "host" value in `tower-cli config` correct?
Right now it is: "http://<IP_ADDRESS>:8013".

It uses the old value of the host. This is a component of the issue #149, but here, it is using the outright incorrect value.
We will probably be able to unit test this bug.

This is still one of my top priorities, but it's too much to cram into the 3.1.0 release.

believed to be solved by #266

Issue solved. Patch will ship with 3.1.1 release.


Negativer Corona-Test, Status weiterhin rot

App Status rot, wegen mehrerer Risikobegegnungen.
Test mit QR Code eingescannt
Negatives Testergebnis erhalten

IST: App Status weiterhin rot, auch nach Aktualisierung am nächsten Tag (Siege Screenshot)

SOLL: App sollte bei negativem Ergebnis wieder grün werden.
Technical details

CWA version 1.5.2
iOS Version: 13.7
Device: iPhone 8

Dear @Oaky78,
Thank you for your report.
Can you confirm that you are using CWA version 1.5.2?
Please, have a look here https://github.com/corona-warn-app/cwa-wishlist/issues/239.
I think you are basically suggesting the same, i.e. after a negative test result, you wish that the red card should change to green.
Also, how many days are between the risk encounter and the corona-test?
Best regards,
DS
Corona-Warn-App Open Source Team

dangerous contacts -> 21.10.
app turns red -> 24.10.
added test -> 26.10.
get negative result -> 28.10.

I did ask the developers and this is not a bug.
The card displays the risk calculation based on the last 14 days. The fact that a user enters a test and gets a negative result does not change your personal risk score or the color of the app card.

@svengabr I don't get it either. If you have a contaminated contact and get tested negative after said contact, the card should not be red. Unless you've had another contamination since your last test of course.
A negative test at any time should set the card to green for the moment of the test. Don't you agree?

Dear @Oaky78, dear @nschloe,
The current situation is:

A person has high-risk encounters according to CWA and gets a red card in CWA.
Based on that information, he does a test (should be done after x days of incubation time)
He gets a negative test result
Still, the CWA shows red for altogether 15 days.

Analysis:
Maybe is a user experience problem (not a bug), not to distinguish carefully between:
(a) Risk calculation by the CWA based on past risk encounters and
(b) Actually NOT being infected, although a risk has existed, proved by a negative test result.
Mitigation possibilities:

Improve web FAQ/documentation and explanation in CWA stating clearly the difference between (a) and (b)

Or would you like to suggest is a different user experience. Let's say you are tempted to worry unnecessarily by a red card, i.e. In the case mentioned above, your suggestion is basically: after a negative test result, the card should go green, meaning: the past high-risk encounters are irrelevant from now on?

Or would you like to suggest is a different user experience. Let's say you are tempted to worry unnecessarily by a red card, i.e. In the case mentioned above, your suggestion is basically: after a negative test result, the card should go green, meaning: the past high-risk encounters are irrelevant from now on?

That'd make lot more sense imho. A red card indicates a warning, danger, the need of attention, so it's a good thing that it's shown after a high-risk contact. After a negative test, there is no danger anymore, so the card can turn green again.
The current situation has another significant disadvantage. If the card stays red for 14 days no matter what, the user will not know if she had another high-risk encounter after a negative test. If, on the other hand, the card turns green after the test and red again a few days later, it's clear that attention is required once again.

@dsarkar I think you're spot on: the current behavior is not strictly speaking a "bug" but rather an annoying "feature" of CWA from a UX perspective. Regarding mitigations I think your second proposal is what https://github.com/corona-warn-app/cwa-wishlist/issues/239 is aiming for and why it's placed in the wishlist repo:

Or would you like to suggest is a different user experience. Let's say you are tempted to worry unnecessarily by a red card, i.e. In the case mentioned above, your suggestion is basically: after a negative test result, the card should go green, meaning: the past high-risk encounters are irrelevant from now on?


Client-side Supabase Auth Session/Access Token Expires Too Soon

Bug report

[x] I confirm this is a bug with Supabase, not with my own application.
[x] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug
Currently we are using Supabase's client-side Auth in our next.js app, and bumped into a problem where a few users kept getting session expired and thus requesting new refresh tokens in supa.auth.getSession() call. After following with these users, we found that their local times were a lot earlier than the access token expiration time, causing newly fetched sessions to expire immediately (https://github.com/supabase/auth-js/blob/f131300d753634fcf3fbc93dc7a762031f096749/src/GoTrueClient.ts#L1081-L1090).
Given that this Date.now() reads the epoch time purely using the user's local system info, potentially with a time drift against the server, we wonder if it is recommended, or even required, to run the Auth logic on the server side?
To Reproduce
We can fairly easily reproduce this problem:

Setting our system time to be JWT.exp + 1 minute before the actual time.
Invoking supabase.auth.getSession() would timeout the session

Expected behavior
getSession() is independent of the user's local system time.
Screenshots
If applicable, add screenshots to help explain your problem.
System information

OS: In practice, we found this to happen mostly on Windows users. (Our guess is that Mac's settings enable automatic time sync by default)
Browser (if applies) Tested on Chrome
Version of supabase-js:

supabase-js: 2.43.4
auth-js: 2.64.2

Version of Node.js: v18.19.0

Additional context
Add any other context about the problem here.

By turning on debug logging, I think it was pretty obvious what has happened. Here's the log for two consecutive call to auth.getSession(), after advancing my local system's time.
# 1st getSession()
GoTrueClient.js:47 GoTrueClient@0 (2.64.2) 2024-06-19T10:19:47.181Z #_useSession begin
GoTrueClient.js:47 GoTrueClient@0 (2.64.2) 2024-06-19T10:19:47.181Z #__loadSession() begin
GoTrueClient.js:47 GoTrueClient@0 (2.64.2) 2024-06-19T10:19:47.181Z #getSession() session from storage {access_token: '***', token_type: 'bearer', expires_in: 900, expires_at:<PHONE_NUMBER>, refresh_token: '***', …}
GoTrueClient.js:47 GoTrueClient@0 (2.64.2) 2024-06-19T10:19:47.181Z #__loadSession() session has expired expires_at<PHONE_NUMBER>
GoTrueClient.js:47 GoTrueClient@0 (2.64.2) 2024-06-19T10:19:47.181Z #_callRefreshToken(*...) begin
GoTrueClient.js:47 GoTrueClient@0 (2.64.2) 2024-06-19T10:19:47.181Z #_refreshAccessToken(*...) begin
GoTrueClient.js:47 GoTrueClient@0 (2.64.2) 2024-06-19T10:19:47.181Z #_refreshAccessToken(*...) refreshing attempt 0
GoTrueClient.js:47 GoTrueClient@0 (2.64.2) 2024-06-19T10:19:47.496Z #_refreshAccessToken(*...) end
GoTrueClient.js:47 GoTrueClient@0 (2.64.2) 2024-06-19T10:19:47.496Z #_saveSession() {access_token: '***', token_type: 'bearer', expires_in: 900, expires_at:<PHONE_NUMBER>, refresh_token: '***', …}
GoTrueClient.js:47 GoTrueClient@0 (2.64.2) 2024-06-19T10:19:47.496Z #_notifyAllSubscribers(TOKEN_REFRESHED) begin {access_token: '***', token_type: 'bearer', expires_in: 900, expires_at:<PHONE_NUMBER>, refresh_token: '***', …} broadcast = true
GoTrueClient.js:47 GoTrueClient@0 (2.64.2) 2024-06-19T10:19:47.496Z #_notifyAllSubscribers(TOKEN_REFRESHED) end
GoTrueClient.js:47 GoTrueClient@0 (2.64.2) 2024-06-19T10:19:47.496Z #_callRefreshToken(*...) end
GoTrueClient.js:47 GoTrueClient@0 (2.64.2) 2024-06-19T10:19:47.497Z #__loadSession() end
GoTrueClient.js:47 GoTrueClient@0 (2.64.2) 2024-06-19T10:19:47.497Z #_useSession end
# 2nd getSession()
GoTrueClient.js:47 GoTrueClient@0 (2.64.2) 2024-06-19T10:19:47.497Z #_useSession begin
GoTrueClient.js:47 GoTrueClient@0 (2.64.2) 2024-06-19T10:19:47.497Z #__loadSession() begin
GoTrueClient.js:47 GoTrueClient@0 (2.64.2) 2024-06-19T10:19:47.497Z #getSession() session from storage {access_token: '***', token_type: 'bearer', expires_in: 900, expires_at:<PHONE_NUMBER>, refresh_token: '***', …}
GoTrueClient.js:47 GoTrueClient@0 (2.64.2) 2024-06-19T10:19:47.497Z #__loadSession() session has expired expires_at<PHONE_NUMBER>
GoTrueClient.js:47 GoTrueClient@0 (2.64.2) 2024-06-19T10:19:47.497Z #_callRefreshToken(*...) begin
GoTrueClient.js:47 GoTrueClient@0 (2.64.2) 2024-06-19T10:19:47.497Z #_refreshAccessToken(*...) begin
GoTrueClient.js:47 GoTrueClient@0 (2.64.2) 2024-06-19T10:19:47.497Z #_refreshAccessToken(*...) refreshing attempt 0
GoTrueClient.js:47 GoTrueClient@0 (2.64.2) 2024-06-19T10:19:47.771Z #_refreshAccessToken(*...) end
GoTrueClient.js:47 GoTrueClient@0 (2.64.2) 2024-06-19T10:19:47.771Z #_saveSession() {access_token: '***', token_type: 'bearer', expires_in: 900, expires_at:<PHONE_NUMBER>, refresh_token: '***', …}
GoTrueClient.js:47 GoTrueClient@0 (2.64.2) 2024-06-19T10:19:47.771Z #_notifyAllSubscribers(TOKEN_REFRESHED) begin {access_token: '***', token_type: 'bearer', expires_in: 900, expires_at:<PHONE_NUMBER>, refresh_token: '***', …} broadcast = true
GoTrueClient.js:47 GoTrueClient@0 (2.64.2) 2024-06-19T10:19:47.771Z #_notifyAllSubscribers(TOKEN_REFRESHED) end
GoTrueClient.js:47 GoTrueClient@0 (2.64.2) 2024-06-19T10:19:47.772Z #_callRefreshToken(*...) end
GoTrueClient.js:47 GoTrueClient@0 (2.64.2) 2024-06-19T10:19:47.772Z #__loadSession() end
GoTrueClient.js:47 GoTrueClient@0 (2.64.2) 2024-06-19T10:19:47.772Z #_useSession end

I believe the key problem is that, as mentioned above, the SDK is effectively comparing expires_at (timestamp returned by server) against the client's local time: https://github.com/supabase/auth-js/blob/f131300d753634fcf3fbc93dc7a762031f096749/src/GoTrueClient.ts#L1081-L1082

session's expire_at is set here: https://github.com/supabase/auth-js/blob/f131300d753634fcf3fbc93dc7a762031f096749/src/lib/fetch.ts#L206-L208. /token?grant_type=refresh_token's response does contain an expire_at field, among other things like access_token and refresh_token.

I think this is caused by a server change last year, where you've introduced the expire_at field in https://github.com/supabase/auth/pull/1183.
Then the client started reading expire_at in https://github.com/supabase/auth-js/pull/735, instead of computing a local expiry based on Date.now() + expire_in.

Clock drift issues are not something we can fix easily. The change to use expire_at instead of expire_in was intentional as that calculation with expire_in is not mathematically sound.
One way you can handle this in your app is to detect that the user's clock has drift and show them a banner. You can do this easily by having an API endpoint in your app that returns the current server time, and compare it with the Date.now() time. If it's off by more than a minute or so you should show that banner.
In future versions of the library we may add native support for detecting clock drift, but there is no way for us to use "relative" time.
Please also be aware that the user's clock is not absolute. A user can change their clock at any time, causing Date.now() to jump back/forth a lot, so there really is nothing we can do about issues like these. But you can handle it in your app with a warning.


don't clobber add_registry and etc

It seems that we're clobbering the ADD_REGISTRY directive that's already there when the SDN writes out the new config

This will actually be resolved with: https://github.com/openshift/openshift-sdn/issues/52

https://github.com/openshift/openshift-sdn/issues/54 has been merged, and openshift-sdn-node no longer clobbers /etc/sysconfig/docker


Latest indexer-agent Docker image throws error Epoch subgraph could not be queried

The latest indexer-agent Docker image ghcr.io/graphprotocol/indexer-agent:v0.20.9 throws the following error when brought up:
[23:11:04.712] WARN (IndexerAgent/1): Epoch subgraph could not be queried
    component: "NetworkMonitor"
    networkID: "eip155:5"
    networkAlias: "goerli"
    attempt: 1
    retriesLeft: 5
    err: "getaddrinfo EAI_AGAIN api.thegraph.com"

Then a number of errors about being unable to query epoch values. Eventually It exhausts its retries and reports:
[23:13:50.227] WARN (IndexerAgent/1): Epoch subgraph could not be queried
    component: "NetworkMonitor"
    networkID: "eip155:5"
    networkAlias: "goerli"
    attempt: 6
    retriesLeft: 0
    err: "Failed to query latest valid epoch and block hash"
[23:13:50.227] ERROR (IndexerAgent/1): Failed to query latest epoch number
    component: "NetworkMonitor"
    networkID: "eip155:5"
    networkAlias: "goerli"
    err: {
      "type": "IndexerError",
      "message": "Failed to query latest valid epoch and block hash",
      "stack":
          IndexerError: Failed to query latest valid epoch and block hash
              at indexerError (/opt/indexer/packages/indexer-common/dist/errors.js:169:12)
              at IndexingStatusResolver.<anonymous> (/opt/indexer/packages/indexer-common/dist/indexing-status.js:234:55)
              at Generator.throw (<anonymous>)
              at rejected (/opt/indexer/packages/indexer-common/dist/indexing-status.js:6:65)
              at runMicrotasks (<anonymous>)
              at processTicksAndRejections (node:internal/process/task_queues:96:5)
      "code": "IE070",
      "explanation": "https://github.com/graphprotocol/indexer/blob/main/docs/errors.md#ie070",
      "cause": {
        "type": "Error",
        "message": "Failed to query graph node for blockHashFromNumber: no data returned",
        "stack":
            Error: Failed to query graph node for blockHashFromNumber: no data returned
                at IndexingStatusResolver.<anonymous> (/opt/indexer/packages/indexer-common/dist/indexing-status.js:210:31)
                at Generator.next (<anonymous>)
                at fulfilled (/opt/indexer/packages/indexer-common/dist/indexing-status.js:5:58)
                at runMicrotasks (<anonymous>)
                at processTicksAndRejections (node:internal/process/task_queues:96:5)
        "attemptNumber": 6,
        "retriesLeft": 0
      },
      "attemptNumber": 6,
      "retriesLeft": 0
    }
[23:13:50.228] WARN (IndexerAgent/1): Failed to obtain protocol chain's latest valid epoch
    component: "Agent"
    error: {
      "code": "IE069",
      "explanation": "https://github.com/graphprotocol/indexer/blob/main/docs/errors.md#ie069",
      "cause": {
        "code": "IE070",
        "explanation": "https://github.com/graphprotocol/indexer/blob/main/docs/errors.md#ie070",
        "cause": {
          "attemptNumber": 6,
          "retriesLeft": 0
        },
        "attemptNumber": 6,
        "retriesLeft": 0
      }
    }

This is using the same, default endpoint as on v.0.20.8 which I can switch back to and no longer see these errors https://api.thegraph.com/subgraphs/name/graphprotocol/goerli-epoch-block-oracle

Regression of #563 ?

The issue is that we now rely on graph-node to resolve block hashes for the protocol chain (in the past we just called a function on the smart contracts.)  This update was required to support L2 protocol chains because of some differences with how smart contract function calls are processed there.
In current code this error will go away if you configure a Goerli RPC endpoint on your graph-node config and make sure that the indexer agent status endpoint is configured to point to an index-node (not a query node because those don't setup RPC endpoints).
However, we are working on an update today to no longer require you to have Goerli RPC in your graph-node config.  Should be ready in a couple hours.

Resolved in #591


update README.md

[Current coverage][cc-pull] is 100%

Merging [#386][cc-pull] into [heroku][cc-base-branch] will not change coverage

@@           heroku   #386   diff @@
====================================
  Files          24     24
  Lines         365    365
  Methods        77     77
  Messages        0      0
  Branches        0      0
====================================
  Hits          365    365
  Misses          0      0
  Partials        0      0

Powered by Codecov. Last updated by [5b63940...829c9eb][cc-compare]
[cc-base-branch]: https://codecov.io/gh/eugene-matvejev/battleship-game-api/branch/heroku?src=pr
[cc-compare]: https://codecov.io/gh/eugene-matvejev/battleship-game-api/compare/5b63940bd63d18152d62ae25297abf2fe34cd255...829c9eb6c759314cc90c1dc70d51951e2a247fa3
[cc-pull]: https://codecov.io/gh/eugene-matvejev/battleship-game-api/pull/386?src=pr


Remove useless code in InjvmProtocolTest

What is the purpose of the change
Remove useless code in InjvmProtocolTest
see more detail from #7854
Brief changelog
Verifying this change

Checklist

[x] Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Add some description to dubbo-website project if you are requesting to add a feature.
[ ] GitHub Actions works fine on your own branch.
[ ] If this contribution is large, please follow the Software Donation Guide.

Codecov Report

Merging #7855 (e342a31) into master (a9b31b1) will increase coverage by 0.09%.
The diff coverage is 100.00%.

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


FASTDDS_INSTRUMENTATION CMake option [10700]

Documentation of the new CMake option FASTDDS_INSTRUMENTATION which enables the compilation of the Fast DDS instrumentation module specific code.
Signed-off-by: JLBuenoLopez-eProsima<EMAIL_ADDRESS>

Build status:

Closed in favor of #241


Discord.js V14 Support

Discord.js v14 Support available or can you add it

This is a duplicate issue

soon ;)


Use modern initializer for RelativePath

Just fixes a bunch of warnings that RelativePath(String) is deprecated.

Thank you @beefon for looking into this. Linter job failed, might be worth running make format and make lint locally. Check https://github.com/macvmio/curie?tab=readme-ov-file#set-up-dev-environment if you don't have mise installed.

@marciniwanicki thanks, fixed


HADOOP-19271. NPE in AbfsManagedApacheHttpConnection.toString() when not connected

When AbfsManagedApacheHttpConnection is not connected, the toString() fails with NPE, as it doesn't have httpClientConnection.getRemoteAddress() set.
This PR fixes this and removes dependency on connection being made. When the connection instance is constructed the required target host is shared. This field would be used in the logs.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 31s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
44m 52s

trunk passed

+1 :green_heart:
compile
0m 41s

trunk passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
compile
0m 38s

trunk passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
checkstyle
0m 34s

trunk passed

+1 :green_heart:
mvnsite
0m 43s

trunk passed

+1 :green_heart:
javadoc
0m 43s

trunk passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
javadoc
0m 36s

trunk passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
spotbugs
1m 10s

trunk passed

+1 :green_heart:
shadedclient
35m  7s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 30s

the patch passed

+1 :green_heart:
compile
0m 31s

the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
javac
0m 31s

the patch passed

+1 :green_heart:
compile
0m 29s

the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
javac
0m 29s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 20s
/results-checkstyle-hadoop-tools_hadoop-azure.txt
hadoop-tools/hadoop-azure: The patch generated 6 new + 0 unchanged - 0 fixed = 6 total (was 0)

+1 :green_heart:
mvnsite
0m 31s

the patch passed

+1 :green_heart:
javadoc
0m 28s

the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
javadoc
0m 26s

the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
spotbugs
1m  6s

the patch passed

+1 :green_heart:
shadedclient
35m 10s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
2m 23s

hadoop-azure in the patch passed.

+1 :green_heart:
asflicense
0m 37s

The patch does not generate ASF License warnings.

129m 29s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7040/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/7040

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux c57df4f411b6 5.15.0-117-generic #127-Ubuntu SMP Fri Jul 5 20:13:28 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / ae4f392b9f4215b2ed75cc3d56cb0489bc17608f

Default Java
Private Build-1.8.0_422-8u422-b05-1~20.04-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_422-8u422-b05-1~20.04-b05

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7040/1/testReport/

Max. process+thread count
551 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-azure U: hadoop-tools/hadoop-azure

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7040/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 30s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
44m 27s

trunk passed

+1 :green_heart:
compile
0m 40s

trunk passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
compile
0m 38s

trunk passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
checkstyle
0m 34s

trunk passed

+1 :green_heart:
mvnsite
0m 43s

trunk passed

+1 :green_heart:
javadoc
0m 41s

trunk passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
javadoc
0m 35s

trunk passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
spotbugs
1m  9s

trunk passed

+1 :green_heart:
shadedclient
34m 27s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 30s

the patch passed

+1 :green_heart:
compile
0m 30s

the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
javac
0m 30s

the patch passed

+1 :green_heart:
compile
0m 28s

the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
javac
0m 28s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 21s
/results-checkstyle-hadoop-tools_hadoop-azure.txt
hadoop-tools/hadoop-azure: The patch generated 4 new + 0 unchanged - 0 fixed = 4 total (was 0)

+1 :green_heart:
mvnsite
0m 32s

the patch passed

+1 :green_heart:
javadoc
0m 29s

the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
javadoc
0m 26s

the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
spotbugs
1m  8s

the patch passed

+1 :green_heart:
shadedclient
34m 27s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
2m 22s

hadoop-azure in the patch passed.

+1 :green_heart:
asflicense
0m 38s

The patch does not generate ASF License warnings.

127m 35s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7040/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/7040

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux dac3309acb20 5.15.0-117-generic #127-Ubuntu SMP Fri Jul 5 20:13:28 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 0e6beef91b1a289749ee7ae20532f8476dbeccbe

Default Java
Private Build-1.8.0_422-8u422-b05-1~20.04-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_422-8u422-b05-1~20.04-b05

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7040/2/testReport/

Max. process+thread count
552 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-azure U: hadoop-tools/hadoop-azure

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7040/2/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
1m 27s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
47m 41s

trunk passed

+1 :green_heart:
compile
0m 42s

trunk passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
compile
0m 36s

trunk passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
checkstyle
0m 34s

trunk passed

+1 :green_heart:
mvnsite
0m 45s

trunk passed

+1 :green_heart:
javadoc
0m 42s

trunk passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
javadoc
0m 34s

trunk passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
spotbugs
1m 16s

trunk passed

+1 :green_heart:
shadedclient
38m 52s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 29s

the patch passed

+1 :green_heart:
compile
0m 38s

the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
javac
0m 38s

the patch passed

+1 :green_heart:
compile
0m 31s

the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
javac
0m 31s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 22s
/results-checkstyle-hadoop-tools_hadoop-azure.txt
hadoop-tools/hadoop-azure: The patch generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

+1 :green_heart:
mvnsite
0m 34s

the patch passed

+1 :green_heart:
javadoc
0m 29s

the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
javadoc
0m 27s

the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
spotbugs
1m 18s

the patch passed

+1 :green_heart:
shadedclient
38m 25s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
2m 22s

hadoop-azure in the patch passed.

+1 :green_heart:
asflicense
0m 37s

The patch does not generate ASF License warnings.

140m 29s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7040/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/7040

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux d8e956eccb98 5.15.0-119-generic #129-Ubuntu SMP Fri Aug 2 19:25:20 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 0ed7893f64e38f3a5b63675bae6350c897ca2e14

Default Java
Private Build-1.8.0_422-8u422-b05-1~20.04-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_422-8u422-b05-1~20.04-b05

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7040/3/testReport/

Max. process+thread count
527 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-azure U: hadoop-tools/hadoop-azure

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7040/3/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 56s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
47m 32s

trunk passed

+1 :green_heart:
compile
0m 43s

trunk passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
compile
0m 37s

trunk passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
checkstyle
0m 33s

trunk passed

+1 :green_heart:
mvnsite
0m 45s

trunk passed

+1 :green_heart:
javadoc
0m 46s

trunk passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
javadoc
0m 33s

trunk passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
spotbugs
1m 16s

trunk passed

+1 :green_heart:
shadedclient
37m 48s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 35s

the patch passed

+1 :green_heart:
compile
0m 36s

the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
javac
0m 36s

the patch passed

+1 :green_heart:
compile
0m 30s

the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
javac
0m 30s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 21s
/results-checkstyle-hadoop-tools_hadoop-azure.txt
hadoop-tools/hadoop-azure: The patch generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

+1 :green_heart:
mvnsite
0m 34s

the patch passed

+1 :green_heart:
javadoc
0m 31s

the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
javadoc
0m 29s

the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
spotbugs
1m 17s

the patch passed

+1 :green_heart:
shadedclient
38m 21s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
2m 21s

hadoop-azure in the patch passed.

+1 :green_heart:
asflicense
0m 36s

The patch does not generate ASF License warnings.

138m 54s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7040/4/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/7040

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux c57c8fa4c504 5.15.0-119-generic #129-Ubuntu SMP Fri Aug 2 19:25:20 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 0ed7893f64e38f3a5b63675bae6350c897ca2e14

Default Java
Private Build-1.8.0_422-8u422-b05-1~20.04-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_422-8u422-b05-1~20.04-b05

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7040/4/testReport/

Max. process+thread count
564 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-azure U: hadoop-tools/hadoop-azure

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7040/4/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 32s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
45m 14s

trunk passed

+1 :green_heart:
compile
0m 41s

trunk passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
compile
0m 38s

trunk passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
checkstyle
0m 35s

trunk passed

+1 :green_heart:
mvnsite
0m 43s

trunk passed

+1 :green_heart:
javadoc
0m 41s

trunk passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
javadoc
0m 35s

trunk passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
spotbugs
1m  8s

trunk passed

+1 :green_heart:
shadedclient
34m 31s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 30s

the patch passed

+1 :green_heart:
compile
0m 32s

the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
javac
0m 32s

the patch passed

+1 :green_heart:
compile
0m 28s

the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
javac
0m 28s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 20s

the patch passed

+1 :green_heart:
mvnsite
0m 32s

the patch passed

+1 :green_heart:
javadoc
0m 27s

the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
javadoc
0m 26s

the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
spotbugs
1m  6s

the patch passed

+1 :green_heart:
shadedclient
34m 57s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
2m 22s

hadoop-azure in the patch passed.

+1 :green_heart:
asflicense
0m 39s

The patch does not generate ASF License warnings.

129m  4s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7040/5/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/7040

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 0b7857b37213 5.15.0-117-generic #127-Ubuntu SMP Fri Jul 5 20:13:28 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / fad8c89671ba5ff480215b117f159860606cb00d

Default Java
Private Build-1.8.0_422-8u422-b05-1~20.04-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_422-8u422-b05-1~20.04-b05

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7040/5/testReport/

Max. process+thread count
552 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-azure U: hadoop-tools/hadoop-azure

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7040/5/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

Hi @steveloughran , requesting your review please. Thanks!

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 31s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
46m 29s

trunk passed

+1 :green_heart:
compile
0m 40s

trunk passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
compile
0m 38s

trunk passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
checkstyle
0m 35s

trunk passed

+1 :green_heart:
mvnsite
0m 44s

trunk passed

+1 :green_heart:
javadoc
0m 41s

trunk passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
javadoc
0m 37s

trunk passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
spotbugs
1m  9s

trunk passed

+1 :green_heart:
shadedclient
34m 36s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 30s

the patch passed

+1 :green_heart:
compile
0m 30s

the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
javac
0m 30s

the patch passed

+1 :green_heart:
compile
0m 29s

the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
javac
0m 29s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 21s

the patch passed

+1 :green_heart:
mvnsite
0m 31s

the patch passed

+1 :green_heart:
javadoc
0m 28s

the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
javadoc
0m 26s

the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
spotbugs
1m  7s

the patch passed

+1 :green_heart:
shadedclient
34m 40s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
2m 24s

hadoop-azure in the patch passed.

+1 :green_heart:
asflicense
0m 36s

The patch does not generate ASF License warnings.

129m 53s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7040/6/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/7040

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 69a22b202f52 5.15.0-117-generic #127-Ubuntu SMP Fri Jul 5 20:13:28 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / ff197fcdf3f2f7f19b2195190f02a07baea643bf

Default Java
Private Build-1.8.0_422-8u422-b05-1~20.04-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_422-8u422-b05-1~20.04-b05

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7040/6/testReport/

Max. process+thread count
552 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-azure U: hadoop-tools/hadoop-azure

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7040/6/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

Thanks @steveloughran a lot for the review. Have taken the comments. Thanks!

Thank you @steveloughran , have changed the Pair implementation with Tuples.pair() which give Map.Entry as suggested. Thanks!

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 34s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
45m  0s

trunk passed

+1 :green_heart:
compile
0m 40s

trunk passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
compile
0m 37s

trunk passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
checkstyle
0m 33s

trunk passed

+1 :green_heart:
mvnsite
0m 41s

trunk passed

+1 :green_heart:
javadoc
0m 40s

trunk passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
javadoc
0m 35s

trunk passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
spotbugs
1m  7s

trunk passed

+1 :green_heart:
shadedclient
34m 41s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 30s

the patch passed

+1 :green_heart:
compile
0m 31s

the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
javac
0m 31s

the patch passed

+1 :green_heart:
compile
0m 28s

the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
javac
0m 28s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 21s

the patch passed

+1 :green_heart:
mvnsite
0m 32s

the patch passed

+1 :green_heart:
javadoc
0m 28s

the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
javadoc
0m 26s

the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
spotbugs
1m  6s

the patch passed

+1 :green_heart:
shadedclient
34m 29s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
2m 23s

hadoop-azure in the patch passed.

+1 :green_heart:
asflicense
0m 39s

The patch does not generate ASF License warnings.

128m 12s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7040/7/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/7040

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 7d967be64bdb 5.15.0-117-generic #127-Ubuntu SMP Fri Jul 5 20:13:28 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 700b8d6d4bf09f3146b66e9e334613f192aac3f1

Default Java
Private Build-1.8.0_422-8u422-b05-1~20.04-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_422-8u422-b05-1~20.04-b05

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7040/7/testReport/

Max. process+thread count
552 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-azure U: hadoop-tools/hadoop-azure

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7040/7/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

backported to branch-3.4 and branch-3.4.1.


Create a section/wiki page for unfamiliar or potentially confusing notation

Thank you for putting this together! I've been studying functional programming on and off for years, and this has reinforced some of the concepts I've learned, clarified others, and taught me new ones. Very nice work.
As I was reading, I came across two notation idioms that confused me, that I'm pretty sure have nothing to do with FP:

The symbol ≍ (which is a black box on my Android, fwiw). From googling, I think it means either logical equivalence, or just equivalence. Not being a mathematician, I'm not sure which it is, and what, specifically, the differences between those are. I can guess why it's preferred over = (which means assignment), but I'm not completely sure why it's different from === (I'm also not a JavaScript expert).
This pattern: ;[1] I'm guessing it means: here's a plain value? and that it's written that way, because of the linter?

Anyway, these details can confuse, and like I said, they're not about FP, so I was thinking it might be nice to have a section, or a wiki page, for them - almost like the sections at the front of many programming books, where they explain how code sections are formatted, that kind of thing. I'm happy to create a wiki page, but I don't know the explanations for either ≍ or ;[1].

@danbernier ;[1] is most likely due to not using semicolons. Browsers won't automatically detect that the line ended otherwise, if you start it with [.

@danbernier ;[1] is most likely due to not using semicolons. Browsers won't automatically detect that the line ended otherwise, if you start it with [.

Thanks @dodekeract! That's exactly the kind of useful info I'm looking to collect.

Thanks @dodekeract! That's exactly the kind of useful info I'm looking to collect.

=== or == aren't correct since they both deal with reference equality.
Mathematically two lists are equal if they contain the same items in the
same order. However two arrays may be equivalent even though they're
different references.
You're right to point out that we don't explain the symbol. Would you
rather we explain the symbol or use english? E.g. xs.map(x => f(g(x))) is
equivalent to xs.map(g).map(f)
On Sun, Jan 1, 2017, 10:14 AM Dan Bernier<EMAIL_ADDRESS>wrote:

Thanks @dodekeract https://github.com/dodekeract! That's exactly the
kind of useful info I'm looking to collect.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/hemanth/functional-programming-jargon/issues/135#issuecomment-269913277,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAB-4LKafv2IEBUtgbsS8frg6Sa76Cc5ks5rN-0EgaJpZM4LYvWZ
.

I'm all for using the symbol, since it expands the language by standing in
for a specific, precise notion. But let's explain that notion somewhere,
for those who are unfamiliar with it.
~
This message was made with 100% thumbs.
On Jan 1, 2017 9:27 PM, "Jethro Larson"<EMAIL_ADDRESS>wrote:

=== or == aren't correct since they both deal with reference equality.
Mathematically two lists are equal if they contain the same items in the
same order. However two arrays may be equivalent even though they're
different references.
You're right to point out that we don't explain the symbol. Would you
rather we explain the symbol or use english? E.g. xs.map(x => f(g(x))) is
equivalent to xs.map(g).map(f)
On Sun, Jan 1, 2017, 10:14 AM Dan Bernier<EMAIL_ADDRESS>wrote:

Thanks @dodekeract https://github.com/dodekeract! That's exactly the
kind of useful info I'm looking to collect.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<https://github.com/hemanth/functional-programming-jargon/
issues/135#issuecomment-269913277>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAB-
4LKafv2IEBUtgbsS8frg6Sa76Cc5ks5rN-0EgaJpZM4LYvWZ>
.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/hemanth/functional-programming-jargon/issues/135#issuecomment-269930184,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAzFTbjFoc55Ctz57zheiocFbr-hzwLks5rOGCZgaJpZM4LYvWZ
.

I found issue #46, which seems to speak to the equality question; linking it here for completeness' sake.
Would still love to see a section for this.


[Timeline][lab] Fix position alternate-reverse generated classname

[x] I have followed (at least) the PR section of the contributing guide.

The classname generated for alternate-reverse class after adding it in #37311 should be .MuiTimeline-positionAlternateReverse, not .MuiTimeline-positionAlternate-reverse. The capitalize function only capitalizes the first letter of the first word and does not convert kebab-case to PascalCase.

Hi @ZeeshanTamboli , is this the cause of  Type '"alternate-reverse"' is not assignable to type '"left" | "right" | "alternate" error? The error is reproducible in the  demo sandbox  .

@Sutar210599 It is not related to this fix. The issue is that we added this feature in https://github.com/mui/material-ui/pull/37311 in the last release but we forgot to bump the version of @mui/lab package in v5.13.6 latest release - #37686.

Ok, thanks.


Why is the current user being set in the context before the password is validated?

Why is the current user being set in the context before the password is validated? In auth.go
authUser := authboss.MustBeAuthable(pidUser)
password := authUser.GetPassword()

// Sets the current user first?
r = r.WithContext(context.WithValue(r.Context(), authboss.CTXKeyUser, pidUser))

// Then validates the password???
var handled bool
err = bcrypt.CompareHashAndPassword(....

And in context.go, the CurrentUser method returns the same context value as the current user:
func (a *Authboss) CurrentUser(r *http.Request) (User, error) {
  if user := r.Context().Value(CTXKeyUser); user != nil {
    return user.(User), nil
  }
...

Is there a gaping security hole where the current user being set even if the login fails? What am I missing here?

I realized that context is only stored during the request lifecycle, and is freed after the response is sent back. The uset context is stored for use by other middleware.


upload converted notebook

adds converted MERFISH notebook.
verified works by converting back and running notebook

Codecov Report

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

@@          Coverage Diff           @@
##           master     #89   +/-   ##
======================================
  Coverage    68.9%   68.9%
======================================
  Files          24      24
  Lines         981     981
======================================
  Hits          676     676
  Misses        305     305

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 1b67fc2...80a5b62. Read the comment docs.

sweet

This should be the same file name as the original .ipynb, except with a different extension.  #81 will be expecting that.

Fixed naming.

Duplicate of #82


Breaking changes

1.)Caching the responses using Map data structure with the concept similar to React query.
2.) Client objects returns corresponding readable store object to enhance svelte by leveraging the svelte store.
3). SSR support for this project with different approach.
Minor changes:
1.) Name fixing.
2.) Js Docs
⚠Caching is expierimental as of now

https://github.com/anasmohammed361/sveltekit-rest/issues/5
Do consider checking that the feature you are trying to add is not yet implemented with svelte query

Which feature is not implemented in svelte query?
On Wed, Dec 6, 2023, 11:33 PM Mohammed Anas @.***>
wrote:

#5 https://github.com/anasmohammed361/sveltekit-rest/issues/5
Do consider checking that the feature you are trying to add is not yet
implemented with svelte query
—
Reply to this email directly, view it on GitHub
https://github.com/anasmohammed361/sveltekit-rest/pull/7#issuecomment-1843403572,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQQHXO74J3DYVIP6TYB6HBDYICXNTAVCNFSM6AAAAABAJTVCWSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBTGQYDGNJXGI
.
You are receiving this because you authored the thread.Message ID:
@.***>


[SPARK-29223][SQL][SS] New option to specify timestamp on all subscribing topic-partitions in Kafka source

What changes were proposed in this pull request?
This patch is a follow-up of SPARK-26848 (#23747). In SPARK-26848, we decided to open possibility to let end users set individual timestamp per partition. But in many cases, specifying timestamp represents the intention that we would want to go back to specific timestamp and reprocess records, which should be applied to all topics and partitions.
This patch proposes to provide a way to set a global timestamp across topic-partitions which the source is subscribing to, so that end users can set all offsets by specific timestamp easily. To provide the way to config the timestamp easier, the new options only receive "a" timestamp for start/end timestamp.
New options introduced in this PR:

startingTimestamp
endingTimestamp

All two options receive timestamp as string.
There're priorities for options regarding starting/ending offset as we will have three options for start offsets and another three options for end offsets. Priorities are following:

starting offsets: startingTimestamp -> startingOffsetsByTimestamp -> startingOffsets
ending offsets: startingTimestamp -> startingOffsetsByTimestamp -> startingOffsets

Why are the changes needed?
Existing option to specify timestamp as offset is quite verbose if there're a lot of partitions across topics. Suppose there're 100s of partitions in a topic, the json should contain 100s of times of the same timestamp.
Also, the number of partitions can also change, which requires either:

fixing the code if the json is statically created
introducing the dependencies on Kafka client and deal with Kafka API on crafting json programmatically

Both approaches are even not "acceptable" if we're dealing with ad-hoc query; anyone doesn't want to write the code more complicated than the query itself. Flink provides the option to specify a timestamp for all topic-partitions like this PR, and even doesn't provide the option to specify the timestamp per topic-partition.
With this PR, end users are only required to provide a single timestamp value. No more complicated JSON format end users need to know about the structure.
Does this PR introduce any user-facing change?
Yes, this PR introduces two new options, described in above section.
Doc changes are following:

How was this patch tested?
New UTs covering new functionalities. Also manually tested via simple batch & streaming queries.

Test build #138756 has finished for PR 32609 at commit f8da576.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/138756/

Kubernetes integration test unable to build dist.
exiting with code: 1
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/43278/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/43278/

Test build #138786 has started for PR 32609 at commit ec1f662.

Test build #138786 has finished for PR 32609 at commit ec1f662.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/138786/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/43309/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/43309/

cc. @viirya @gaborgsomogyi @xuanyuanking

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/43309/

Test build #138897 has started for PR 32609 at commit afd6c11.

Test build #138897 has finished for PR 32609 at commit afd6c11.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Kubernetes integration test unable to build dist.
exiting with code: 1
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/43418/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/138897/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/43418/

When the hardcoded version discussion is resolved then it's good to go from my perspective.

Test build #138917 has started for PR 32609 at commit 20b276d.

Test build #138917 has finished for PR 32609 at commit 20b276d.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/43438/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/138917/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/43438/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/43438/

Test build #138924 has started for PR 32609 at commit b72f590.

Test build #138924 has finished for PR 32609 at commit b72f590.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/43445/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/138924/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/43445/

lgtm too

@HeartSaVioR Thanks for this option. It makes sense to use the same timestamp across the subscribed topics.
@viirya Will it be a part of Spark 3.2.0 release?

@viirya Will it be a part of Spark 3.2.0 release?

Yes. This was merged before 3.2 branch cut.


Heartbeat support

I think, still not 100% positive, this is required for the Spring Boot client; if I send a default response my Spring Boot app happily consumes the messages.
Request code is here: https://github.com/aovestdipaperino/kafka-api/blob/expiration/kafka-api/src/schemata/heartbeat_request.rs
Response code here: https://github.com/aovestdipaperino/kafka-api/blob/expiration/kafka-api/src/schemata/heartbeat_response.rs

Looks reasonable. Let me take a look in this week.

0.3.1 is out with this support


Unexpected behavior in ks.merge how='outer'

Hi,
I have been trying to perform a outer join between two koalas dataframes on basis of a column, but am getting very unexpected results. Below is an example,
left_kdf = ks.DataFrame({'A': [1, 2]})
right_kdf = ks.DataFrame({'B': ['x', 'y', 'z'], 'A':[3, 4, 1]})
left_kdf.merge(right_kdf, on=["A"], how='outer')
The output that I get is

However, if this is a SQL style join as said in the documentation, the output should be something like,

The None part (in Column B) is discussed in #263
What concerns me are the missing values in column A.

Hi @shreyanshu, Thanks for the report.
I submitted a PR to fix this issue. (#595)
Could you review the PR if you have time?
Thanks!


Cannot reasign vars

fn main() {
    let x = 2;
    print x;
    x = 3;
    print x;
}

Will be closed by https://github.com/aDotInTheVoid/skate/tree/lvalues

Closed by 45


UDP support (/process_graphs)

Add support for UDPs (GET /process_graphs and related).
Questions:

where to store? at level of aggregator, or "highest prio" upstream back-end, or all backends?
what to list? only UDPs defined at aggregator or combine multiple upstream back-ends?
how to handle job with UDP usage if UDPs are stored only at level of aggregator? Automatically store UDP in upstream back-end first, or rewrite "UDP calls" in original process graph with actual UDP implementation?

The details have to be discussed, but the most important thing is that files and user-defined processes must be accessible by all back-ends in the federation because otherwise, users can't re-use them properly in other processes. User shouldn't need to care about where something is available and where it's not available.

@m-mohr @soxofaan @jdries
UPD support by the aggregator is important for the platform part!
Could we add a task as part of SAP09 Operationalization on this?

We just added very basic support to the aggregator (just on dev instance openeocloud-dev.vito.be at the moment):
UDP interactions are just proxied directly to VITO back-end: creating, getting, listing UDPs on the aggregator goes directly to VITO UDP storage.
This is not ideal because there is no federation aspect to this, but at least the basics are working for majority of processing requests (which go to VITO anyway)

basic implementation is available, will close this ticket.
Follow-up is for https://github.com/openEOPlatform/architecture-docs/issues/368


fix stale link

@u2takey Thanks for sending this PR! However, changes to the code need to go as a PR against the kubernetes/kubernetes repo. Specifically, you will need to change the files here: https://github.com/kubernetes/kubernetes/tree/master/staging/src/k8s.io/api.
The changes will be later synced to this repo.

ok, thanks. open https://github.com/kubernetes/kubernetes/pull/52731, this closed


Reason for executable Jars not resolving icons packs

Good day.
There are several open issues (#11, #24) that have a problem of executable jar (with dependencies being extracted to this executable jar, instead of linked by manifest to their respective jars) not being able to to resolve icon packs. A workaround was proposed in this post, that suggests to move the icon dependency up the hierarchy. I've figured out the reason why it matters: both ikonli.core and ikonli.<icon pack> have a org.kordamp.ikonli.IkonHandler file in META-INF/services directory. For the application to successfully resolve icons, the ikonli.<icon pack>'s version of the file has to be included in the executable jar.  In certain cases this can be alleviated by altering dependency order (like in IntelliJ). But in other cases (like Gradle's jar task) there's no way of specifying the order in which dependendencies should be extracted (or is there?). Nevertheless, the main point is that this is an issue that has to be handled by library itself, rather than leaving users of this library scratching their heads.
Your response is very much appreciated.

AFAIK multiple instances of a service file (such as META-INF/services/org.kordamp.ikonli.IkonHandler) are supported by the ServiceLoader facility added since JDK6. All matching implementations of a particular service should be loaded, regardless of the order they may appear in the classpath.
Creating a fat JAR with just the regular Gradle Jar task is not the way to go, as service files must be merged. This merging behavior is provided by the Gradle Shadow plugin whose setup is separate from this library.

Are there any specific Shadow config options that are relevant to solving the above mentioned values? Because with default shadow config I did not have much luck. To which options should one pay attention?

According to the documentation, this should be enough
shadowJar {
    transform(ServiceFileTransformer)
}

Or even this
shadowJar {
    mergeServiceFiles()
}

What about maven-shade-plugin users ?

Problem solved
For maven-shade-plugin users, add this to your transformers
<transformer implementation="org.apache.maven.plugins.shade.resource.ServicesResourceTransformer"/>
For more information about Resource Transformers, refer to this page


Form.Validate Not Working in OnAfterRenderAsync with Fluent Validation

Bug type
Component
Component name
MudForm
What happened?
MudForm.Validate does not work as expected when using in OnAfterRenderAsync to display validation errors on component render. The Offer field correctly shows the error message using OnAfterRenderAsync because it has the Validation attribute directly on the field while the other fields fail to show their validation.
Expected behavior
Using the Validation attribute on the form along with calling MudForm.Validate in OnAfterRenderAsync should show the validation errors for the form.
Reproduction link
https://try.mudblazor.com/snippet/QYmQYXcPThFrbine
Reproduction steps

Create a Form using MudBlazor and add fields to the form.
Use FluentValidation to validate the form.
Call the validate method on the form in the OnAfterRenderAsync method.

Relevant log output
No response
Version (bug)
6.0.15
Version (working)
No response
What browsers are you seeing the problem on?
Firefox, Chrome, Microsoft Edge
On what operating system are you experiencing the issue?
Windows
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Isn't this just a hack and not an actual fix? If I'm calling OnAfterRenderAsync, why would the form still be attaching properties? What happens if someone has a slow machine and it loads slower and exceeds the delay? @Mr-Technician

Without looking closely at the lifecycle methods, the validation was applied in OnAfterRenderAsync to ensure all form controls are properly initialized first. There is a possibility the validation rules could be applied when the controls subscribe, however, which would prevent this issue.

See if #5501 fixes your issue. 😄


Programmatic way of loading CSS?

I am using the npm package and browserify it.
var hl = require('highlight.js')

var root = document.createElement('pre')
root.innerHTML = hl.highlightAuto('function foo(a){\n  return a+1\n}').value
document.body.appendChild(root)

This way it can be used with http://requirebin.com
http://requirebin.com/?gist=7ac2d019b8ed89419bd5
I am looking for some programmatic way of getting CSS setup without the need to include CSS into HTML.
--Alexey

There are  some variants here:

http://stackoverflow.com/questions/574944/how-to-load-up-css-files-using-javascript
http://stackoverflow.com/questions/2685614/load-external-css-file-like-scripts-in-jquery-which-is-compatible-in-ie-also

My request was rather related to the internal highlight.js capability as a tool.
If one can require the tool from npm and browserify i, then having on-board CSS initialization might be a good idea ?

I don't think it's a good idea for a library to include glue code for every environment it can be used in, to be honest.

You are right @isagalaev , it is your code, and in the end of the day you are free to decide on it.
But just for a second, consider my :train: of though:

node is my environment.
npm is a node package manager of my choice.
I have discovered great node package on the npm that somebody @isagalaev published.
I am installing it, and require it in my code; as any other npm package. :trophy:

var hl = require('highlight.js');

hl object exposes bunch of useful functions. I can run it to get HTML I need! :+1:

var html = hl.highlightAuto('function foo(a){\n  return a+1\n}').value;

naively, I have expected to get relevant CSS the same way I am getting HTML. By running some function! Is it "every environment" ? I don't think so. It is "the environment", the node. Is it "glue code", may-be but IMHO, it is convenient.

naively, I have expected to get relevant CSS the same way I am getting HTML. By running some function!

This is where you lost me. Presumably you're going to display the formatted code on some web page, and styles are usually linked to to web pages with <link rel="stylesheet">. I don't even understand what an API function is supposed to do here. Generate a link tag? Or content of a CSS file?
Highlight.js is widely used on node.js and until this moment nobody asked what you're asking. This is why I assumed your environment being in some way special.

Sorry for asking something, that nobody asked :smirk:
Assuming you functions returning HTML as-a-string, it make sense returning CSS as-a-string.
Considering the following code; and function hljs__css being part of highlight.js package; someOne may use it this way:
var hl = require('highlight.js'),
    insertCss = require('insert-css');

function hljs__css (name) {
  var css = {
    github: '.hljs-keyword { color: #333; font-weight: bold;}'
  };
  return css[name];
}

insertCss(hljs__css('github'));

var root = document.createElement('pre')
root.innerHTML = hl.highlightAuto('function foo(a){\n  return a+1\n}').value
document.body.appendChild(root);

https://gist.github.com/drom/d95eb5f6d5f3e30743e6
http://requirebin.com/?gist=d95eb5f6d5f3e30743e6

To wrap it up…
We're not going to do this after all because:

An API call returning the contents of a CSS file doesn't provide much value as there's already an established way to do it: linking a file from HTML.
Implementing it by packing the CSS contents into a the .js module would increase its size, most of which would be a useless load in a browser environment as people tend to use only one theme.
In a server environment it can already be done by simply reading a file (as the documentation of "insert-css" suggests, by the way)
Expectation of having a CSS-producing method symmetric to an HTML-producing one is subjective and not at all common, as far as I can see.


single line-break

Hi,
I have noticed that the single line-break is not working. This is the markup I am using:
markdown: |
  Test first line\s\s
  test second line

The result is:

Test first line\s\s
        test second line

But no break line tag "
"  is printed.
Any idea of what could be the problem?
Many thanks!

I had to use:
markdown: |
Test first line
test second line
To achieve what I needed

@marko85to I've added a test case in #3, and it seems to work for me with trailing space characters, unescaped. Can you run npm ls from your project directory to see if we have different versions?


Fixed extra symbols added to ABI when zlib-compat specified.

See #658 for background.
Abi diff before:
31 Added function symbols not referenced by debug info:

  adler32_avx2
  adler32_c
  adler32_ssse3
  chunkcopy_c
  chunkcopy_safe_c
  chunkcopy_safe_sse2
  chunkcopy_sse2
  chunkmemset_c
  chunkmemset_safe_c
  chunkmemset_safe_sse2
  chunkmemset_sse2
  chunksize_c
  chunksize_sse2
  chunkunroll_c
  chunkunroll_sse2
  compare258_c
  compare258_unaligned_16
  compare258_unaligned_32
  compare258_unaligned_64
  compare258_unaligned_avx2
  compare258_unaligned_sse4
  crc32_combine_gen64
  crc32_combine_gen@@ZLIB_1.2.9
  crc32_combine_op@@ZLIB_1.2.9
  longest_match_c
  longest_match_unaligned_16
  longest_match_unaligned_32
  longest_match_unaligned_64
  longest_match_unaligned_avx2
  longest_match_unaligned_sse4
  zlibng_version

4 Added variable symbols not referenced by debug info:

  zlibng_string
  zng_deflate_copyright
  zng_errmsg
  zng_inflate_copyright

After:
Functions changes summary: 0 Removed, 0 Changed, 0 Added function
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
Function symbols changes summary: 0 Removed, 3 Added function symbols not referenced by debug info
Variable symbols changes summary: 0 Removed, 0 Added variable symbol not referenced by debug info
3 Added function symbols not referenced by debug info:

  crc32_combine_gen64@@ZLIB_1.2.12
  crc32_combine_gen@@ZLIB_1.2.12
  crc32_combine_op@@ZLIB_1.2.12

I have resolved all the comments.
The output from abidiff should now be:
+ abidiff test/zlib-1.2.11-x86_64-linux-gnu.abi zlib-built.abi
Functions changes summary: 0 Removed, 0 Changed, 0 Added function
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
Function symbols changes summary: 0 Removed, 4 Added function symbols not referenced by debug info
Variable symbols changes summary: 0 Removed, 1 Added variable symbol not referenced by debug info

4 Added function symbols not referenced by debug info:

  crc32_combine_gen64@@ZLIB_1.2.12
  crc32_combine_gen@@ZLIB_1.2.12
  crc32_combine_op@@ZLIB_1.2.12
  zlibng_version

1 Added variable symbol not referenced by debug info:

  zlibng_string


Does not support negative images in training

I put some images which does not have label in it i.e completely black mask with respect to those images and the output of it is tensors having nan's instead of 0's
outputs----- tensor([[[[nan, nan, nan,  ..., nan, nan, nan],           [nan, nan, nan,  ..., nan, nan, nan],           [nan, nan, nan,  ..., nan, nan, nan],           ...,           ...,           [nan, nan, nan,  ..., nan, nan, nan],           [nan, nan, nan,  ..., nan, nan, nan],           [nan, nan, nan,  ..., nan, nan, nan]]]], device='cuda:0',
due to which there is an error coming up in loss.backward()
   Variable._execution_engine.run_backward(  # Calls into the C++ engine to run the backward pass RuntimeError: CUDA error: device-side assert triggered
My idea was to put some negative images into training so that model understands a bit clearly about the busy background, and as we remove these negative images and corresponding masks the code is working fine.
Please confirm , how to resolve this so that i can consider those negative images as well ???

To compute the loss, you should set the values of label to 0, not nan.
Since you set the values to nan, the loss.backward error occurred.

No i did not assign any labels to nan , as the input goes to inital_conv it gives the output as nan , i can't figure out why??  and Secondly if i manually assign the outputs which are coming nan as 0 and put to cuda again and then compute the loss , than  it would not be correct for the optimizers which are working on loss to reduce it . I meant to say that if i manually assign output as 0's than loss would be 0 for negative images from the very first epoch which may not be good for the learning.
Please suggest if  i am thinking right or not

To be specific--- the mask are labelled as 0 only for the images which do not have any object


requirements: Downgrade pika to 0.11.0.

Downgrading as issue #8466 is not fixed yet.

@hackerkid I merged this, after adding a comment linking to the issue to explain why this isn't upgraded.  That should help avoid problems in the future :)


move after deploy hook into app loop

This change didn't break tests and is what I wanted, so I figured that I'd submit it as a PR.
This moves the after_deploy hook into the each_heroku_app loop which seems like where it should be to me. The stage is passed into the after task as an argument named stage.

Closing to get this out of my dashboard, but it could be reopened later if you wanted.


Advertise offline access and show loading time for 1st time download of files

Maybe one quick hack would be just telling users that "hey! Confer takes a few mins when loaded for the first time, so that you can even use it offline!" And perhaps showing some progress bar (if not too much work). Such messages and displays typically relax me - otherwise I hit refresh etc which probably doesn't hurt too much (if it picks up from already downloaded Json) but doesn't help either..

The offline access features hasn't been maintained properly and I'm not
sure if it  works reliably anymore. The very first version of confer did
support the offline functionality but I think many code changes in the past
3 years bypass offline functionalities.
If the offline feature is really important -- it needs to be properly
tested.
-- anant
On Fri, Mar 25, 2016 at 9:30 PM, Amy Zhang<EMAIL_ADDRESS>wrote:

Maybe one quick hack would be just telling users that "hey! Confer takes a
few mins when loaded for the first time, so that you can even use it
offline!" And perhaps showing some progress bar (if not too much work).
Such messages and displays typically relax me - otherwise I hit refresh etc
which probably doesn't hurt too much (if it picks up from already
downloaded Json) but doesn't help either..
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/anantb/confer/issues/9


Track requests with Pretender in test mode

By default Pretender tracks requests made during the lifespan of the Pretender server. This is a really handy way to spy on requests and assert behaviors in tests.
A simple example:
https://github.com/hashicorp/nomad/blob/master/ui/tests/acceptance/namespaces-test.js#L21-L28
A more complex example:
https://github.com/hashicorp/nomad/blob/master/ui/tests/acceptance/token-test.js#L45-L56
However, in #1137 trackRequests was hardcoded to be false.
I think the best way forward is to track requests in tests by default, don't track requests in dev by default, and expose a property like server.logging to control whether or not requests should be tracked.

Fixed in #1217


SA@NUS: Help not customizable

Currently the help text has no effect:

Markdown would be great!

Addressed in #1878


Early draft of log_artifact

@daavoo Can you discuss with @karajan1001? He was going to take this issue.

@daavoo Can you discuss with @karajan1001? He was going to take this issue.

Yes, we discussed and I open the P.R. to share what I already had

Closing in favor of https://github.com/iterative/dvclive/pull/464