text:
How to add text as MultipartFormData with images

Moya/Core (12.0.1)

above is our requirement, below is my code in task
var identificationData = [MultipartFormData(provider: .data(model.frontImage), name: "file1", fileName: "frontImage", mimeType: "jpg/png"),
            MultipartFormData(provider: .data(model.backImage), name: "file2", fileName: "backImage", mimeType: "jpg/png")]
            identificationData.append(MultipartFormData(provider: .data("description".data(using: .utf8)!), name: "description"))
            return .uploadMultipart(identificationData)

seeing a http 400 error code.

Hey @GKicw. It seems like you might need to update the name in your MultipartFormData:
let images = [MultipartFormData(provider: .data(model.frontImage), name: "frontImage", fileName: "frontImage", mimeType: "jpg/png"),
              MultipartFormData(provider: .data(model.backImage), name: "backImage", fileName: "backImage", mimeType: "jpg/png")]

You are also lacking barCodeText property in your array of properties (you have description, though). Plus, take a look at your mimeType as well in your images: you are specifying jpg/png, but I'm not sure this is a valid MIME-type (I might be wrong though, but I think you would need to specify it as image/jpeg or image/png depending on your content type).

@sunshinejr i'm using the same for an image it works properly, issue is when adding text.
here is updated code
var identificationData = [MultipartFormData(provider: .data(model.frontImage), name: "file1", fileName: "frontImage", mimeType: "image/jpeg"),
MultipartFormData(provider: .data(model.backImage), name: "file2", fileName: "backImage", mimeType: "image/jpeg")]
identificationData.append(MultipartFormData(provider: .data("barCodeText".data(using: .utf8)!), name: "barCodeText"))
return .uploadMultipart(identificationData)

@GKicw hmm, I'm not sure I follow! But also it seems like you've resolved the issue, is that correct? If so, would you please let me know what was the culprit?

@sunshinejr Thanks, you found the issue, updating the name in MultipartFormData fixed my issue.

Perfect! Glad you got it working @GKicw 👍🏻

authors: GKicw sunshinejr

repo: Moya/Moya


text:
fix memory leak in stub mode

Seems like the request for plugin in stub mode never complete so just cancel it. It fix the memory leak issue. Related to https://github.com/Moya/Moya/issues/1000

          1 Error

:no_entry_sign:
Any changes to library code need a summary in the Changelog.

  Generated by :no_entry_sign: danger

Codecov Report

Merging #1002 into master will increase coverage by 0.03%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #1002      +/-   ##
==========================================
+ Coverage   73.61%   73.65%   +0.03%
==========================================
  Files          22       22
  Lines         724      725       +1
==========================================
+ Hits          533      534       +1
  Misses        191      191

Impacted Files
Coverage Δ

Sources/Moya/MoyaProvider+Internal.swift
62.27% <100%> (+0.17%)
:white_check_mark:

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 ca5c9fe...d2070ee. Read the comment docs.

Thanks a lot for contributing to Moya! I've invited you to join the Moya GitHub organization – no pressure to accept! If you'd like more information on what that means, check out our contributor guidelines and feel free to reach out with any questions.

source: gharchive/pull-request

authors: MoyaBot ashfurrow bestwnh codecov-io

license: mit

license_type: permissive

license_source: bigquery


text:
Introducing Path.

When new API endpoints are introduced, the TargetType enum can easily grow larger and, in such a case, I find it not easy to check if the endpoints are associated with the right HTTP methods.
For the given reason, I'm introducing Path which combines in one place the endpoint and the HTTP method.
Example:
extension MyService: TargetType {
    var baseURL: URL {
        return URL(string: "https://api.myservice.com")!
     }

    var path: Path {
        switch self {
        case .zen:
            return .get(endpoint: "/zen")
        case .showUser(let id):
            return .get(endpoint: "/users/\(id)")
        case .updateUser(let id, _, _):
            return .post(endpoint: "/users/\(id)")
        case .createUser(_, _):
            return .post(endpoint: "/users")
        case .showAccounts:
            return .get(endpoint: "/accounts")
        }
    }
    ...
}

Let me know your thoughts!
Thanks 😊

Warnings

:warning:
The Package.swift was updated, but there were no changes in Moya.podspec, Cartfile, Cartfile.resolved, Package.resolved.
Did you forget to update them?

:warning:

Consider adding supporting documentation to this change. Documentation can be found in the docs directory.

:warning:

Consider also updating the English docs. For Chinese translations, request the modified file(s) to be added to the list here for someone else to translate, if you can't do so yourself.

:warning:

Any changes to library code should be reflected in the Changelog.
Please consider adding a note there and adhere to the Changelog Guidelines.

Messages

:book:
macOS: 	 Executed 282 tests, with 0 failures (0 unexpected) in 15.766 (16.055) seconds

:book:
tvOS: 	 Executed 282 tests, with 0 failures (0 unexpected) in 13.057 (13.427) seconds

:book:
iOS: 	 Executed 282 tests, with 0 failures (0 unexpected) in 13.112 (13.469) seconds

Mdspell report on docs/Releasing.md:

Line
Typo

32
changelog._

46
Readme

46
e.g.

Proselint report on docs/Releasing.md

Line
Message
Severity

12
Use curly quotes “”, not straight quotes "".
warning

  Generated by :no_entry_sign: Danger Swift against 841ee18db5f41dca8bd264ef3d2f15c573848803

Codecov Report

Merging #2001 into development will increase coverage by 0.65%.
The diff coverage is 81.57%.

@@               Coverage Diff               @@
##           development    #2001      +/-   ##
===============================================
+ Coverage        92.91%   93.56%   +0.65%
===============================================
  Files               27       28       +1
  Lines              931      963      +32
===============================================
+ Hits               865      901      +36
+ Misses              66       62       -4

Impacted Files
Coverage Δ

Sources/Moya/TargetType.swift
100% <ø> (ø)
:arrow_up:

Sources/Moya/MoyaProvider+Defaults.swift
78.26% <100%> (ø)
:arrow_up:

Sources/Moya/URL+Moya.swift
100% <100%> (ø)
:arrow_up:

Sources/Moya/MultiTarget.swift
100% <100%> (ø)
:arrow_up:

Sources/Moya/Path.swift
78.12% <78.12%> (ø)

Sources/Moya/Response.swift
95.34% <0%> (+4.65%)
:arrow_up:

Sources/RxMoya/Observable+Response.swift
61.53% <0%> (+7.69%)
:arrow_up:

Sources/ReactiveMoya/SignalProducer+Response.swift
93.93% <0%> (+9.09%)
:arrow_up:

Sources/RxMoya/Single+Response.swift
100% <0%> (+12.5%)
: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 86f2b1f...841ee18. Read the comment docs.

@jdisho Thank you for the proposal :))
My two cents here:
Would it be a better idea to bring this in a retro compatible way, where the old option still valid ... and the user could choose? This is really a question because personally, I think some people may prefer the old way and this could be inserted as an option (we could do either way) and not a breaking change :)

cc @sunshinejr @Moya/contributors

I agree with @LucianoPAImeida that this should try to be a backwards compatible change - with that said, I really like the idea! (I would agree with most “decluttering” of the Target protocol - it’s kind of a mess sometimes to find the right code). Would it be going too far to include the request params? Question: when will we be building a request that uses the path& http method, but doesn’t need the parameters?
For backwards compatibility some renaming would be in order; if instead of var path: Path which replaces var path: String, this could be an optional-and-default implemented var request: Request. Then we could migrate towards this feature without requiring another major version release. I really dig the name Path, but we’re already at version 5 in what was always meant to be just a thin network organization tool.

On second thought adding parameters would be too much clutter. Http method and path make sense to me.

👍 for what it wants to solve. I'm using MoyaSugar to reduce bunch of boilerplates. Hope this discussion goes well :)

I like the idea! Seems like a win in the long run. Thought I'm having a hard time thinking about a nice way of keeping it backwards compatible without introducing other problems. Then also we are refactoring the Task type in #1936, so when you add these two it might be too much for a single release (? not sure).

Hi folks! 👋
Any direction regarding this PR?

My desire to have this implemented in a backwards-compatible way still stands.  As it is now including this feature would require a new major version release due to the change to path

Also, we might want to look to the past as we think about this: https://github.com/Moya/Moya/pull/427 and https://github.com/Moya/Moya/issues/408
https://github.com/Moya/Moya/blob/9cc10d0f6ba8179c46695bf0831fd22a83e7a6c5/Sources/Moya/MultiTarget.swift

Could we rename Path into Route as in MoyaSugar ? I think it makes more sense than having the http method and the path into the notion of Path.

authors: LucianoPAlmeida MoyaBot amaurydavid codecov-io colinta devxoul jdisho sunshinejr


text:
Add types for system query results

This PR adds strict type safety for system query results. Currently ECSY assumes entity.getComponent(ComponentA) will always return ComponentA, in reality, it may return undefined. However, if the query had ComponentA in its components array, we could safely assume that the entity had the component in the system's execute method.
import { System, Component } from "ecsy";

class ComponentA extends Component<ComponentA> {
  a!: number;
}

class ComponentB extends Component<ComponentB>{
  b!: number;
}

class ComponentC extends Component<ComponentC> {
  c!: number;
}

// The <typeof MySystem> parameter is optional when you aren't using strict mode.
// The benefit outside of strict mode is that you will get typechecking and autocompletion for query keys like "ab"
class MySystem extends System<typeof MySystem> {
  static queries = {
    ab: {
      components: [ComponentA, ComponentB],
    }
  };

  execute() {
    const entity = this.queries.ab.results[0];

    // ComponentA is in the query
    entity.getComponent(ComponentA).a;
    entity.getMutableComponent(ComponentA).a = 1;

    // ComponentC is not in the query so we need to cast it
    (entity.getComponent(ComponentC) as ComponentC).c;
    (entity.getMutableComponent(ComponentC) as ComponentC).c = 1;

    // Note casting gets rid of the Readonly type. I'm not sure what to do about that.
    (entity.getComponent(ComponentC) as ComponentC).c = 1;
  }
}

This was a cool experiment, but after getting everything working, the error messages were not very readable and the strict types weren't really strict. An entity inside a system's execute could at anytime be missing a component even if it is in the system's query. This is because components can be removed immediately.
So rather than merging this PR I think we should go with https://github.com/MozillaReality/ecsy/pull/240

repo: MozillaReality/ecsy

license: MIT

license_source: github-api


text:
View Result表示後 AviUtlのプロセスが終了できなくなる

AviUtl本体ウィンドウの閉じるボタンを押した場合、本体ウィンドウは閉じるが、プロセスが裏で生きている。

r35で修正

source: gharchive/issue


text:
Implementing zoom

Hi! Thanks so much for your work on react-flow-chart so far - Using it for a personal project and it's worked perfectly.
I'm implementing zoom at the moment. Trying to figure out the best way to go about this - Since the container is just a plain div, is the best way to zoom in/out to just adjust the zoom property? I'm not sure I can think of another way to implement this functionality.
Thanks!

I'd tend towards adding a css style along the lines transfrom: scale(${chart.zoom}) to a div inside the canvas.wrapper. zoom should probably be added as a top level property alongside offset in the IChart type. As such, you'd bind some onScroll handlers in the canvas wrapper and add some action handlers to adjust chart.zoom. PR would be appreciated :)

authors: MrBlenny timminkov

repo: MrBlenny/react-flow-chart


text:
backend error  init missing  pos......

Model: gpt-4-1106-preview
I encountered a lot of backend error and json.loads failed to parse

I found that it was easy to report errors when parsing json, so I modified the parameter description in function call, and now the frequency of occurrence is reduced a lot。

repo: MrGreyfun/Local-Code-Interpreter


text:
Update readme to warn against issue #17

Updated the order of the example code and added an explicit warning against calling get_local_address prior to adding a route on Linux machines. In response to #17.

Coverage remained the same at 64.758% when pulling 7be070a2ba993f457353ed4e7b2cca04560bcfc2 on dabrowne:master into 473f5773015e49ed0e63e1a2c706f1454335df5a on MrLeeh:master.

authors: coveralls dabrowne

repo: MrLeeh/pyads


text:
Race: Shifter(Multiverse)(Auto Effects)

Describe the bug
If you made a Shifter in the Multiverse one, and the last racial feature is set to Shifting: Wildhunt:
The Changemode on the effect that "Shift" has on it is set to ADD when it needs to be CUSTOM(its a midi key that is typically undefined so ADD can't work on it)
To Reproduce
Steps to reproduce the behavior:

Import a Shifter from multiverse that has the final racial setting set to Wildhunt
Edit the Shift feature and look at the key/changemode/value on the ae

Expected behavior
Midi keys typically can't be ADD cause their values are usually undefined on actors, CUSTOM or OVERRRIDE are usually recommended, CUSTOM for this specific one.
Screenshots

Environment:

Browser [e.g. chrome] Newest Chrome
Foundry Version [e.g. 10.288] 11.313
5e System Version [e.g 2.0.3] 2.3.1
Module Version [e.g 3.1.21] 3.5.8
N/A

Additional context
Found while working on the midi wiki
Be sure not to check CPR's setting cause he has his own version of this specific feature

Ta

repo: MrPrimate/ddb-importer


text:
1080p YouTube download not working (requested format not available, even though it is)

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like that [x])
Use Preview tab to see how your issue will actually look like

WARNING
All invalid issues will be rejected!!

Before going further

If your problem is a bug with youtube-dl or a request for new site support please report it here

Make sure you are using the latest youtube-dl-gui version (Click the Settings icon and then About to view the current version)

Make sure you are using the latest youtube-dl version (Click the Settings icon and then Update to update to the latest youtube-dl version)

Make sure you searched the bugtracker for similar issues including closed ones

Make sure to read the FAQs file

[x] I think my problem is NOT with youtube-dl
[x] I've verified and i assure that I'm running youtube-dl-gui 0.4
[x] I assure that i am using the latest version of youtube-dl
[x] Searched bugtracker
[x] I've read the FAQs file

What is the purpose of your issue?

[x] Bug report
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

Please remove any sections between (---) if they are not related to your issue

Bug report
If the problem occurs when downloading a URL please provide the full verbose output as follows:

Restart youtube-dl-gui
Go to Options > Extra tab
Enable Debug youtube-dl
Go to Options > Advanced tab and Clear your log content
Try to download the URL
Copy the whole log content and insert it between the ``` part below

[Wed Sep 12 22:40:34 2018] ERROR: requested format not available

What operating system do you use ?
Ubuntu 16.04
List of actions to perform to reproduce the problem:

Try to download this video: https://www.youtube.com/watch?v=-KGnRe1f2DA
Either leave it default manually select 1080p
Download the video.

What is the expected behaviour ?
You should get 1080p when leaving it default or manually selecting 1080p.
What happens instead ?
Instead you get 720p default or an error when downloading 1080p.

Okay I feel really silly but I literally just fixed it. I de-selected "prefer native HLS" and now it automatically downloads the highest quality. Feel free to close this issue if you feel it's invalid, but I do have a suggestion. I think it might be worth adding this to the FAQ:
Q: how come 1080p YouTube download is not working
A: Try disabling native HLS. You can disable the "Prefer Native HLS" option under the Options>Extra tab.

Hi,
I'm using the Windows version but facing the same issue. Disabling "Prefer Native HLS" didn't work for me.
Does anyone know how to solve this issue?
Thanks!

Make sure FFmpeg is installed on your system. youtube-dl uses FFmpeg with 1080p videos.
This project is not maintained any more, perhaps you would find this fork easier, since it will install FFmpeg for you.

Thank you @axcore

authors: Akhilesh-T axcore ipkpjersi

license: unlicense


text:
Compatibility issues with chat portrait

The module "chat portrait" seems to confuse the image of the cross on the double damadge button as an additional portrait. This only happes while its enabled alongside this module

Also apologies for posting too much about the problems i notice, im not trying to do it out of malice, but i wish to report any bugs i find

I don't believe this is a PF2e Target Damage issue but a Chat Portrait one, especially with the fact it's removing the system buttons icon, not one from the module.

Oh, it seems so. Ive just tested the portrait module by itself on a pf2e game and the issue happens. ill notify them. Sorry for the confusion

authors: Janonas MrVauxs


text:
BlackJack in python project

Type of change

[✅ ] Added new project
[ ] Bug fix
[ ] New features
[ ] Enhanced documentation

Changes proposed in this pull request
added a new project

Project name :

BlackJack

Short description :

We all know about the popular card game BlackJack. Here I have created a simplified implementation of it in python where the computer acts as the dealer. It's a single-player game. The player can bet a certain amount of money. The project is easy to read and follow and contains comments as necessary.
Checklist

[ ✅] The code is Python 3 compatible
[✅ ] I have added relevant comments in my file to make the code understandable
[ ✅] I have added my project to a folder that includes all the necessary files

Looks good thanks for contributing 👍


text:
请问这个预计会支持1.12.2版本吗

请问这个预计会支持哪些mc版本呢

1.16.4起步

repo: MscBaiMeow/FishBotReload


text:
Error when build Project "MudToolBarSpacer" is obsolate

Bug type
Component
Component name
MudToolBarSpacer
What happened?
After I was changed .NET from 5.0 => 6.0 So I was nuget update to Mudblazor 6.0.2
and this errors when i rebuild my project

Expected behavior

Reproduction link

Reproduction steps

Relevant log output
No response
Version (bug)
6.0.2
Version (working)
5.2.0
What browsers are you seeing the problem on?
Safari
On what operating system are you experiencing the issue?
Mac OSX
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

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

Your fix: #1840

Thank you.

Like @Yomodo said. This is not a bug. You need to replace MudToolBarSpacer with MudSpacer

authors: JonBunator Yomodo beginflints

repo: MudBlazor/MudBlazor


text:
DatePicker: KeyInterceptor Crash Workaround

Description
A workaround about #4897 and #4853.
The issue is, when datepicker's popover opening, _keyInterceptor is null (despite being initialized in OnAfterRender) and application crashes with null reference.
Actually i don't know about exact problem, probably it may about transient #4631.
In this PR we only added that the code checks the _keyInterceptor again on opening and initialize it if its null.
This PR may not be the final solution, but i think we should solve this crashing datepicker, its unavoidable and common situation now.
How Has This Been Tested?

Website doesn't crash with this PR when we click datepickers which has OpenTo="Year" parameter.
Types of changes

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

Checklist:

[x] The PR is submitted to the correct branch (dev).
[x] My code follows the code style of this project.
[ ] I've added relevant tests.

@henon @just-the-benno could you make a review? Datepicker is broken in some situations and affects really bad. This prevents some users to update the last release.

 _keyInterceptor.KeyDown -= HandleKeyDown;

I added this line into dispose methods, but they also give the same null reference exceptions. The problem should be somewhere else. Do you have an idea why _keyInterceptor is null? (Because it hit the _keyInterceptor.Connect checkpoint in debug, it should not be null)
And the other point i think we will probably delete the key interceptors keydown event, because picker etc. also has keydown definition in razor code and key events are working twice for now.

Hi @mckaragoz
I've created a new PR that took your idea and also fixed some other minor issues. Have a look at #4987

#4987 fixes the issue better, so we are now closing this PR.

authors: just-the-benno mckaragoz


text:
MudMenu: Fix when PositionAtCursor is true and touch is used.

Description
Fixes: https://github.com/MudBlazor/MudBlazor/issues/7006
The problem was obvious that the ToggleMenuTouch(TouchEventArgs args) casts args to EventArgs for OpenMenu, but then OpenMenu would cast it to MouseEventArgs without validation if it's possible, it works for mouse but not for touch, like the issue author said it does not account for the args potentially being TouchEventArgs when casting the EventArgs.
How Has This Been Tested?
Manually, but let me know if we need unit test for this.
Types of changes

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

Checklist:

[x] The PR is submitted to the correct branch (dev).
[x] My code follows the code style of this project.
[ ] I've added relevant tests.

So what happens in the touch scenario, nothing?

So what happens in the touch scenario, nothing?

The popover will showup just the way it would with PositionAtCursor=false,
PositionAtCursor only makes sense for mouse input.
Also getting OffsetY and OffsetX from TouchEventArgs is hard as it's not included in the event, you would need to get the canvas / document size, call js getBoundingClientRect and then do some simple math e.targetTouches[0].clientX - bcr.x;, e.targetTouches[0].clientY - bcr.y;.

Thanks @ScarletKuro !

authors: ScarletKuro henon


text:
Clear up console warnings about cookie "Same Site" attribute

...by assigning the default value, "lax".
I think we could switch to "strict", maybe, but this PR is not aiming to change cookies, just get rid of console warnings for the sake of JS debugging.
It also tries, but does not succeed, in eliminating the nonstandard CSS zoom property that throws a warning in FF.

coverage: 93.605%. remained the same when pulling 7543f23f76b04bdd2febac8d87521a48d35dcf9f on nimmo-cookie-samesite into 5601e98425247f980797c51208256436f58e7ce5 on main.

authors: coveralls nimmolo

repo: MushroomObserver/mushroom-observer


text:
Split Kobold out of Shadowdark Core Source

Currently it shows up as part of the core rulebook when it was a forum created addon not part of any core rulebook.
Split out similar to Bard and Rogue since it was created in a similar fashion.

Bard and Ranger are currently under their own tag. Yes, Kobold is a weird one, but I think we can move under the B&R tag similar to how shadowdarklings does it.

authors: PrototypeESBU xanstin

repo: Muttley/foundryvtt-shadowdark


text:
Link List not visible in the table of contents of the target journal entry

seen behavior
The link-list is not visible in the table of contents of the journal entry.
(see screenshot)

expected behavior
The Link List should be visible in the table of contents according to the selectes "h" tag (h1 = page, h2 below page and so on).
Thanks a lot in advance.

That's currently not intended, as it would create the same heading for every page. But I'll consinder it as an optional Setting für the next Update. Thanks for the Idea.

You can test in with by installing the new alpha
https://github.com/Muwak77/journal-backlinks-extended/releases/download/0-12-6a/module.json


text:
fix(gux-table): fix checkbox row disabled bug affecting Vue

backport of https://github.com/MyPureCloud/genesys-spark/pull/526

Any idea why most of the playgrounds are in /playground and just vue-3 is in /playgrounds in v3?

repo: MyPureCloud/genesys-spark


text:
Steps to build sui using clang vs gcc on Fedora due to rocksdb compile issue

When attempting to build on fedora, the rocksdb compilation steps utilizing gcc fail due to a dependency mismatch.
In order to work around this, I ended up using clang/clang++ instead of gcc.
I added the following to my .bashrc and re logged in, and successfully built using cargo build --release:
export USE_CLANG=1
export RUSTC_LINKER=lld
export RUSTFLAGS="-C linker=clang -C link-arg=-fuse-ld=lld -C link-arg=-lc++ -C link-arg=-lc++abi"
export CXXFLAGS=-stdlib=libc++
export LDFLAGS="-stdlib=libc++"
export CC="clang"
export CXX="clang++"

Thanks for the work-around and it works! I hope it can be added to the official document.

@ronny-mysten should we add this to our docs? This seems useful in a section like Debugging Installation Errors?

authors: DaveWK chinggg stefan-mysten

repo: MystenLabs/sui


text:
[gql] objects_snapshot test for availableRange-aware object history lookup

Description
Expose a way to provide config values to ObjectsSnapshotProcessor to enable e2e tests around objects_snapshot.

Adds a SnapshotLagConfig to ObjectsSnapshotProcessor struct
ReaderWriterConfig for start_test_indexer_v2, reorganizes some logic on instantiating a reader or writer indexer_v2
RunGraphqlCommand now waits for objects_snapshot catch up in addition to the existing checkpoint catch up.

snapshot.move to test querying against objects_snapshot and objects_history tables
Test Plan
snapshot.move

If your changes are not user-facing and do not break anything, you can skip the following section. Otherwise, please briefly describe what has changed under the Release Notes section.
Type of Change (Check all that apply)

[ ] protocol change
[ ] user-visible impact
[ ] breaking change for a client SDKs
[ ] breaking change for FNs (FN binary must upgrade)
[ ] breaking change for validators or node operators (must upgrade binaries)
[ ] breaking change for on-chain data layout
[ ] necessitate either a data wipe or data migration

Release notes

I was curious when else persist_object_snapshot got called, other than when this flag was set. It seems like it should be called as part of commit_checkpoints, here:
https://github.com/MystenLabs/sui/blob/2814db65293ceeafe00c0e2cad30ecce9b230f27/crates/sui-indexer/src/handlers/committer.rs#L152
Which makes me think that calling create-checkpoint in the test should have the desired effect -- is that not the case? If not, it seems reasonable to add the functionality to kick it manually, but I would prefer adding it to create-checkpoint or its own dedicated command. It feels wrong to add it to a command that is otherwise only intended for reading the simulator state.

Yes this was my assumption as well. What I've observed is that since the indexer commits not one but potentially a set of checkpoints at a time, it's possible that while the latest checkpoint to commit would exceed the max lag allowed by the snapshot, because the persist_objects_snapshot method only sees the current state of the indexer's db, which is at an earlier checkpoint, it does not actually kick off a new snapshot.
For example, at min_lag=0, max_lag=2, we'll take a snapshot every time max(sequence_number) on checkpoints >= max_lag-min_lag + max(checkpoint_sequence_number) on snapshots.
Let's say indexer falls behind, and now is trying to index checkpoints 3 through 6. the checkpoints table will show that it is currently at checkpoint 2. to the objects_snapshot logic, this checkpoint is still within the allowable lag, so it does not do anything, even though by the end of this commitment we will be at checkpoint 6, and the objects_snapshot table will have fallen further behind.
Thus, in our tests we have to force the indexer to take another look. This time, it'll see that checkpoints table is at checkpoint 6, and it will take a snapshot.
I think realistically this is not that big of a concern since the allowable lag is much greater, about hundreds of checkpoints, but tagging @gegaowp on whether we should reorganize the objects_snapshot logic a bit. Maybe it can take place after we've committed the checkpoint's contents and itself?

@amnn I'm going to close https://github.com/MystenLabs/sui/pull/15672 and have this one implement the necessary changes to support tests around objects_snapshot.

When it comes to the environment variables, I think the right move here is to have the indexer accept a config struct that you can either construct from environment variables when it's created from the indexer binary, or pass in as a struct when creating for tests. It's annoying work, but it's got to be done -- environment variables are not the right tool for communicating values between two parts of the same binary.

The entrypoint would have to be in //# init, so we can extend SuiInitArgs to accept parameters for the config fields needed to instantiate PgIndexerStoreV2. I was also thinking instead that we could introduce a PgIndexerStoreV2Config that can read from a yaml file, and in our e2e tests instantiate PgIndexerStoreV2Config::ci_integration_test_cfg that would read from a yaml file.

Agreed with your assessment that it's easiest to pass the config inline in the init call!

whether we should reorganize the objects_snapshot logic a bit. Maybe it can take place after we've committed the checkpoint's contents and itself?

yes in a recent PR https://github.com/MystenLabs/sui/pull/15793, I separated the snapshot persisting logic from the synced batch persisting; in that sense, snapshot will start updating, but it will not guarantee that the max lag will not go beyond the configured number.

authors: amnn gegaowp wlmyng


text:
[sui-adapter] Relax orphan rule. Relax by-value object rule

Relax orphan rule so that it only pertains to by-value child object usage
Relax by-value object rule so shared objects can be consumed
Shared objects can be taken by-value in only their defining module

Removed by-value shared object code for now.


text:
🛑 Mysteryexe is down

In 5622628, Mysteryexe (https://mysteryexe.xyz) was down:

HTTP code: 403
Response time: 1148 ms

Resolved: Mysteryexe is back up in 1aa4777 after 5 minutes.

repo: Mysteryexe/uptime-checker


text:
New LIS-based WRF forcing reader for AK domain

New LIS forcing reader for WRF-based Alaska (AK) domain (polar-stereographic projection)
@karsenau

The new WRF Alaska (AK) reader in LIS and its elevation file reader in LDT are now ready, along with test cases for LDT and LIS (with and without topographic corrections).
The test case files can be found here:
LDT: /discover/nobackup/karsenau/LISF_PR/WRF_AKReader/LDT_Test
LIS: /discover/nobackup/karsenau/LISF_PR/WRF_AKReader/LIS_Test
This PR addresses feature issue #812

repo: NASA-LIS/LISF


text:
Fix for S2S-Post accumulated variables

Committing update to S2S-Post monthly script for accumulated variables (e.g., total precip).
Also, include minor fixes to BCSD python script headers (e.g., "NMME" to "CFSv2).

@jvgeiger and @emkemp:
This is the latest commit for the LIS 7.5.11 557 WW PR.


text:
Stop using astropy channel; only conda-forge has latest astropy

Fixes #105 by conda installing astropy from the conda-forge channel rather than the astropy channel.  conda-forge seems to be the only channel with the latest (5.2) version of astropy, and 5.2 is needed for compatibility with numpy==1.24.
Also updated the check_env.py script with latest versions for astropy and numpy.

I'm merging this now, and suggest to check on the build failures separately.

I lost track of the problems, but is it right that we bumped the min version of numpy and astropy permanently? (if yes, it should be propagated to the env file and tox, too).

authors: bsipocz tomdonaldson

repo: NASA-NAVO/navo-workshop


text:
CODEOWNERS groups lack write permissions

The @NASA-PDS/pds-software-committers lacks write perms to the repo so CODEOWNERS isn't doing anything for us.
See #13 for demonstration.

Changed "Read" → "Write" for @NASA-PDS/pds-software-committers on this repository

repo: NASA-PDS/pds-template-repo-java


text:
Update Header for RootErrorBoundary layout

💡 Description
The Header implementation in the RootErrorBoundary needs to be updated to make use of the newly revised header component that is provided by wds-react.
The fix is to elevate the current header component in portal-wp to centralize the navItems definition.
⚔ Parent Epic / Related Tickets
No response

The RootErrorBoundary layout has been updated to integrate the header component that was added to wds-react.
PR containing this implementation coming later today.

repo: NASA-PDS/portal-wp-tasks


text:
BiG-SLICE and BiG-SCAPE integration strategy

For projects with too large number of BGCs, BiGSLICE is the preferred choice. However, I wanted to discuss a potential strategy to run BiGSLICE first to get first degree of GCF annotation and then run BiGSCAPE on each of the GCFs to get second degree of GCF annotation.
This strategy needs further discussion on which of the 1st-degree GCFs to select for 2nd-degree GCF annotation.

Shall we run BiGSCAPE on every BiGSLICE detected GCF?
Shall we run BiG-SCAPE on a few of the most abundant GCFs only (e.g GCFs with around 50 BGCs or more)? And then run a BiGSCAPE on all remaining BGCs together.
Shall we include all of the MIBIG DB for each of the BiGSCAPE run?
Do we need this feature as an additional rule of BGCFlow?

Please drop other considerations that would be relevant for this strategy- @matinnuhamunada

@matinnuhamunada - we should build on something similar to what I started to propose here.

repo: NBChub/bgcflow


text:
Vertical Change Detection

This PR adds the vcd command and some library functions to compute vertical change meshes and raster products between two aerial lidar point clouds

I would like to include the extrusion-to-ground functionality, but I don't want to hold this PR up because of it 😬
Thanks @hobu for implementing this!

repo: NCALM-UH/CODEM


text:
Added messaging to details panel matching command line output for CL …

…CODEM

Thanks @willforker LGTM, merging!


text:
Additional content needed for Getting Data into VAPOR

A few missing items from our "Getting Data into VAPOR" documentation:
Additional NetCDF using Python examples

Creating a NetCDF-CF file from an Xarray array (or numpy array) I.e. generate a 3D Xarray/Numpy array with synthetic data and write it to a NetCDF-CF file with coordinates.
Create a NetCDF-CF file that contains a curvilinear grid. This could be done with synthetic data as per above, or simply modifying the "dealing with stretched grids" example so that it has 2D coordinate variables instead of 1D

Add "UGRID" to the list of supported file formats

@sgpearse can we close this now?

@clyne I have a curvilinear grid example that I had to table before the 3.6 release.  It needs to be added here.  After we get that in, we should be able to close this.

authors: clyne sgpearse

repo: NCAR/VAPOR


text:
keyError on to_dataset_dict

Description
I get key errors in calling to_dataset_dict
Code
Running the following on cheyenne (via iPython):
# Imports
import intake
import pprint

# Parameters
var_ids = ['tas']
exp_ids = ['historical']

# Grab catalog data
col = intake.open_esm_datastore("catalogs/glade-cmip6.json")
cat = col.search(activity_id="CMIP", experiment_id=exp_ids,
                 variable_id=var_ids, table_id="Amon")
uni_dict = cat.unique(['source_id', 'experiment_id', 'table_id'])
pprint.pprint(uni_dict, compact=True)

dset_dict = cat.to_dataset_dict(zarr_kwargs={'consolidated': True, 'decode_times': False},
                                cdf_kwargs={'chunks': {}, 'decode_times': False})

I get the error message at bottom (note I've gotten different keyErrors using the same code, including for 'lat').

.
.
.
/glade/work/pochedls/miniconda3/lib/python3.7/site-packages/xarray/core/utils.py in getitem(self, key)
382
383     def getitem(self, key: K) -> V:
--> 384         return self.mapping[key]
385
386     def iter(self) -> Iterator[K]:
KeyError: 'j'

Environment (base environment, probably a remnant of the environment created in the tutorial)

(base) pochedls@cheyenne4:~/cmip6hack-pacific-sst> conda list
packages in environment at /glade/work/pochedls/miniconda3:
Name                    Version                   Build  Channel
_libgcc_mutex             0.1                        main    defaults
aiohttp                   3.6.1            py37h516909a_0    conda-forge
appdirs                   1.4.3                      py_1    conda-forge
asciitree                 0.3.3                      py_2    conda-forge
asn1crypto                1.0.1                    py37_0    conda-forge
async-timeout             3.0.1                   py_1000    conda-forge
attrs                     19.2.0                     py_0    conda-forge
backcall                  0.1.0                      py_0    conda-forge
bash                      4.4.18            hcee41ef_1001    conda-forge
bash_kernel               0.7.2                    py37_1    conda-forge
bleach                    3.1.0                      py_0    conda-forge
blinker                   1.4                        py_1    conda-forge
bokeh                     1.3.4                    py37_0    conda-forge
boto3                     1.9.250                    py_0    conda-forge
botocore                  1.12.250                   py_0    conda-forge
bzip2                     1.0.8                h516909a_1    conda-forge
ca-certificates           2019.9.11            hecc5488_0    conda-forge
cachetools                2.1.0                      py_0    conda-forge
certifi                   2019.9.11                py37_0    conda-forge
cffi                      1.12.3           py37h8022711_0    conda-forge
cftime                    1.0.3.4         py37hd352d35_1001    conda-forge
chardet                   3.0.4                 py37_1003    conda-forge
click                     7.0                        py_0    conda-forge
cloudpickle               1.2.2                      py_0    conda-forge
conda                     4.7.12                   py37_0    conda-forge
conda-package-handling    1.6.0            py37h516909a_0    conda-forge
cryptography              2.7              py37h72c5cf5_0    conda-forge
curl                      7.65.3               hf8cf82a_0    conda-forge
cytoolz                   0.10.0           py37h516909a_0    conda-forge
dask                      2.3.0                      py_0    conda-forge
dask-core                 2.3.0                      py_0    conda-forge
dask-labextension         1.0.3                      py_0    conda-forge
decorator                 4.4.0                      py_0    conda-forge
defusedxml                0.6.0                      py_0    conda-forge
distributed               2.3.2                      py_1    conda-forge
docutils                  0.15.2                   py37_0    conda-forge
entrypoints               0.3                   py37_1000    conda-forge
fasteners                 0.14.1                     py_3    conda-forge
freetype                  2.10.0               he983fc9_1    conda-forge
fsspec                    0.5.2                      py_0    conda-forge
gcsfs                     0.3.1                      py_0    conda-forge
google-auth               1.6.3                      py_0    conda-forge
google-auth-oauthlib      0.4.1                      py_0    conda-forge
hdf4                      4.2.13            h9a582f1_1002    conda-forge
hdf5                      1.10.5          nompi_h3c11f04_1103    conda-forge
heapdict                  1.0.1                      py_0    conda-forge
icu                       64.2                 he1b5a44_1    conda-forge
idna                      2.8                   py37_1000    conda-forge
importlib_metadata        0.23                     py37_0    conda-forge
intake                    0.5.3                      py_0    conda-forge
intake-esm                2019.10.15                 py_0    conda-forge
intake-xarray             0.3.1                      py_0    conda-forge
ipykernel                 5.1.2            py37h5ca1d4c_0    conda-forge
ipython                   7.8.0            py37h5ca1d4c_0    conda-forge
ipython_genutils          0.2.0                      py_1    conda-forge
ipywidgets                7.5.1                      py_0    conda-forge
jedi                      0.15.1                   py37_0    conda-forge
jinja2                    2.10.3                     py_0    conda-forge
jmespath                  0.9.4                      py_0    conda-forge
jpeg                      9c                h14c3975_1001    conda-forge
json5                     0.8.5                      py_0    conda-forge
jsonschema                3.1.1                    py37_0    conda-forge
jupyter-server-proxy      1.1.0                      py_0    conda-forge
jupyter_client            5.3.3                    py37_1    conda-forge
jupyter_contrib_core      0.3.3                      py_2    conda-forge
jupyter_contrib_nbextensions 0.5.1                    py37_0    conda-forge
jupyter_core              4.5.0                      py_0    conda-forge
jupyter_dashboards        0.7.0                 py37_1000    conda-forge
jupyter_highlight_selected_word 0.2.0                 py37_1000    conda-forge
jupyter_latex_envs        1.4.4                 py37_1000    conda-forge
jupyter_nbextensions_configurator 0.4.1                    py37_0    conda-forge
jupyterlab                1.1.4                      py_0    conda-forge
jupyterlab_server         1.0.6                      py_0    conda-forge
krb5                      1.16.3            h05b26f9_1001    conda-forge
libblas                   3.8.0               13_openblas    conda-forge
libcblas                  3.8.0               13_openblas    conda-forge
libcurl                   7.65.3               hda55be3_0    conda-forge
libedit                   3.1.20170329      hf8c457e_1001    conda-forge
libffi                    3.2.1             he1b5a44_1006    conda-forge
libgcc-ng                 9.1.0                hdf63c60_0    defaults
libgfortran-ng            7.3.0                hdf63c60_2    conda-forge
libiconv                  1.15              h516909a_1005    conda-forge
liblapack                 3.8.0               13_openblas    conda-forge
libnetcdf                 4.7.1           nompi_h94020b1_101    conda-forge
libopenblas               0.3.7                h6e990d7_1    conda-forge
libpng                    1.6.37               hed695b0_0    conda-forge
libsodium                 1.0.17               h516909a_0    conda-forge
libssh2                   1.8.2                h22169c7_2    conda-forge
libstdcxx-ng              9.1.0                hdf63c60_0    defaults
libtiff                   4.0.10            h57b8799_1003    conda-forge
libuv                     1.32.0               h516909a_0    conda-forge
libxml2                   2.9.9                hee79883_5    conda-forge
libxslt                   1.1.33               h31b3aaa_0    conda-forge
locket                    0.2.0                      py_2    conda-forge
lxml                      4.4.1            py37h7ec2d77_0    conda-forge
lz4-c                     1.8.3             he1b5a44_1001    conda-forge
markupsafe                1.1.1            py37h14c3975_0    conda-forge
mistune                   0.8.4           py37h14c3975_1000    conda-forge
monotonic                 1.5                        py_0    conda-forge
more-itertools            7.2.0                      py_0    conda-forge
msgpack-numpy             0.4.4.3                    py_0    conda-forge
msgpack-python            0.6.2            py37hc9558a2_0    conda-forge
multidict                 4.5.2           py37h14c3975_1000    conda-forge
nb_conda_kernels          2.2.2                    py37_0    conda-forge
nbconvert                 5.6.0                    py37_1    conda-forge
nbformat                  4.4.0                      py_1    conda-forge
ncurses                   6.1               hf484d3e_1002    conda-forge
netcdf4                   1.5.1.2          py37hf3213d6_2    conda-forge
nodejs                    12.11.1              h10a4023_0    conda-forge
notebook                  6.0.1                    py37_0    conda-forge
numcodecs                 0.6.3            py37hf484d3e_0    conda-forge
numpy                     1.17.2           py37h95a1406_0    conda-forge
oauthlib                  3.0.1                      py_0    conda-forge
olefile                   0.46                       py_0    conda-forge
openssl                   1.1.1c               h516909a_0    conda-forge
packaging                 19.2                       py_0    conda-forge
pandas                    0.25.1           py37hb3f55d8_0    conda-forge
pandoc                    2.7.3                         0    conda-forge
pandocfilters             1.4.2                      py_1    conda-forge
parso                     0.5.1                      py_0    conda-forge
partd                     1.0.0                      py_0    conda-forge
pexpect                   4.7.0                    py37_0    conda-forge
pickleshare               0.7.5                 py37_1000    conda-forge
pillow                    6.2.0            py37h6b7be26_0    conda-forge
pip                       19.2.3                   py37_0    conda-forge
prometheus_client         0.7.1                      py_0    conda-forge
prompt_toolkit            2.0.10                     py_0    conda-forge
psutil                    5.6.3            py37h516909a_0    conda-forge
ptyprocess                0.6.0                   py_1001    conda-forge
pyasn1                    0.4.6                      py_0    conda-forge
pyasn1-modules            0.2.7                      py_0    conda-forge
pycosat                   0.6.3           py37h14c3975_1001    conda-forge
pycparser                 2.19                     py37_1    conda-forge
pygments                  2.4.2                      py_0    conda-forge
pyjwt                     1.7.1                      py_0    conda-forge
pyopenssl                 19.0.0                   py37_0    conda-forge
pyparsing                 2.4.2                      py_0    conda-forge
pyrsistent                0.15.4           py37h516909a_0    conda-forge
pysocks                   1.7.1                    py37_0    conda-forge
python                    3.7.3                h33d41f4_1    conda-forge
python-dateutil           2.8.0                      py_0    conda-forge
python-snappy             0.5.4            py37hee44bf9_0    conda-forge
pytz                      2019.3                     py_0    conda-forge
pyyaml                    5.1.2            py37h516909a_0    conda-forge
pyzmq                     18.1.0           py37h1768529_0    conda-forge
readline                  8.0                  hf8c457e_0    conda-forge
requests                  2.22.0                   py37_1    conda-forge
requests-oauthlib         1.2.0                      py_0    conda-forge
rsa                       3.4.2                      py_1    conda-forge
ruamel.yaml               0.16.5           py37h516909a_1    conda-forge
ruamel.yaml.clib          0.2.0            py37h516909a_0    conda-forge
ruamel_yaml               0.15.71         py37h14c3975_1000    conda-forge
s3fs                      0.3.5                      py_0    conda-forge
s3transfer                0.2.1                    py37_0    conda-forge
send2trash                1.5.0                      py_0    conda-forge
setuptools                41.4.0                   py37_0    conda-forge
simpervisor               0.3                        py_1    conda-forge
six                       1.12.0                py37_1000    conda-forge
snappy                    1.1.7             he1b5a44_1002    conda-forge
sortedcontainers          2.1.0                      py_0    conda-forge
sqlite                    3.30.1               hcee41ef_0    conda-forge
tblib                     1.4.0                      py_0    conda-forge
terminado                 0.8.2                    py37_0    conda-forge
testpath                  0.4.2                   py_1001    conda-forge
tk                        8.6.9             hed695b0_1003    conda-forge
toolz                     0.10.0                     py_0    conda-forge
tornado                   6.0.3            py37h516909a_0    conda-forge
tqdm                      4.36.1                     py_0    conda-forge
traitlets                 4.3.3                    py37_0    conda-forge
urllib3                   1.25.6                   py37_0    conda-forge
wcwidth                   0.1.7                      py_1    conda-forge
webencodings              0.5.1                      py_1    conda-forge
wheel                     0.33.6                   py37_0    conda-forge
widgetsnbextension        3.5.1                    py37_0    conda-forge
xarray                    0.14.0                     py_0    conda-forge
xz                        5.2.4             h14c3975_1001    conda-forge
yaml                      0.1.7             h14c3975_1001    conda-forge
yarl                      1.3.0           py37h14c3975_1000    conda-forge
zarr                      2.3.2                    py37_0    conda-forge
zeromq                    4.3.2                he1b5a44_2    conda-forge
zict                      1.0.0                      py_0    conda-forge
zipp                      0.6.0                      py_0    conda-forge
zlib                      1.2.11            h516909a_1006    conda-forge
zstd                      1.4.0                h3b9ef0a_0    conda-forge

I was able to avoid this error by reversing the order of operations in the aggregations specified in the JSON file. This would likely resolve #151 too.
{
  "esmcat_version": "0.1.0",
  "id": "glade-cmip6",
  "description": "This is an ESM collection for CMIP6 data accessible on the NCAR's GLADE disk storage system in /glade/collections/cmip/CMIP6",
  "catalog_file": "/glade/collections/cmip/catalog/intake-esm-datastore/catalogs/glade-cmip6.csv.gz",
  "attributes": [
    {
      "column_name": "activity_id",
      "vocabulary": "https://raw.githubusercontent.com/WCRP-CMIP/CMIP6_CVs/master/CMIP6_activity_id.json"
    },
    {
      "column_name": "source_id",
      "vocabulary": "https://raw.githubusercontent.com/WCRP-CMIP/CMIP6_CVs/master/CMIP6_source_id.json"
    },
    {
      "column_name": "institution_id",
      "vocabulary": "https://raw.githubusercontent.com/WCRP-CMIP/CMIP6_CVs/master/CMIP6_institution_id.json"
    },
    {
      "column_name": "experiment_id",
      "vocabulary": "https://raw.githubusercontent.com/WCRP-CMIP/CMIP6_CVs/master/CMIP6_experiment_id.json"
    },
    { "column_name": "member_id", "vocabulary": "" },
    {
      "column_name": "table_id",
      "vocabulary": "https://raw.githubusercontent.com/WCRP-CMIP/CMIP6_CVs/master/CMIP6_table_id.json"
    },
    { "column_name": "variable_id", "vocabulary": "" },
    {
      "column_name": "grid_label",
      "vocabulary": "https://raw.githubusercontent.com/WCRP-CMIP/CMIP6_CVs/master/CMIP6_grid_label.json"
    },
    {
      "column_name": "version",
      "vocabulary": ""
    },
    {
      "column_name": "dcpp_start_year",
      "vocabulary": ""
    }
  ],
  "assets": {
    "column_name": "path",
    "format": "netcdf"
  },
  "aggregation_control": {
    "variable_column_name": "variable_id",
    "groupby_attrs": [
      "activity_id",
      "institution_id",
      "source_id",
      "experiment_id",
      "table_id",
      "grid_label"
    ],
    "aggregations": [
      {
        "type": "union",
        "attribute_name": "variable_id"
      },
      {
        "type": "join_existing",
        "attribute_name": "time_range",
        "options": { "dim": "time", "coords": "minimal", "compat": "override" }
      },
      {
        "type": "join_new",
        "attribute_name": "member_id",
        "options": { "coords": "minimal", "compat": "override" }
      },
    {
        "type": "join_new",
        "attribute_name": "dcpp_init_year",
        "options": { "coords": "minimal", "compat": "override" }
      }
    ]
  }
}

cc @andersy005

I can confirm that this is fixed. @pochedls, can you update the collection json files with respective file content from https://github.com/cmip6hack/project-template/tree/master/catalogs and let us know whether this is still an issue for you?

Is this an xarray bug?

I am reopening this since it appears to be related to #169

@dcherian,

Is this an xarray bug?

So far, I believe this issue has to do with our order of operations and not an xarray bug. I am looking into this in #169 and will let you know.

With #171, the issue seems to be fixed.
import intake
col = intake.open_esm_datastore("/glade/collections/cmip/catalog/intake-esm-datastore/catalogs/glade-cmip6.json")
cat = col.search(activity_id="CMIP", experiment_id="historical", variable_id="tas", table_id="Amon")

However, I am noticing some discrepancies in the time axis length for different models. For instance (CMIP.CAS.FGOALS-g3.historical.Amon.gn, CMIP.NOAA-GFDL.GFDL-ESM4.historical.Amon.gr1):
dsets = cat.to_dataset_dict(cdf_kwargs={"chunks": {"time": 36}})
for key, ds in dsets.items():
    print(f"{key}")
    print(f"\t{ds.dims}")

CMIP.BCC.BCC-CSM2-MR.historical.Amon.gn
	Frozen(SortedKeysDict({'lon': 320, 'bnds': 2, 'time': 1980, 'lat': 160, 'member_id': 3}))
CMIP.BCC.BCC-ESM1.historical.Amon.gn
	Frozen(SortedKeysDict({'lon': 128, 'bnds': 2, 'time': 1980, 'lat': 64, 'member_id': 3}))
CMIP.CAMS.CAMS-CSM1-0.historical.Amon.gn
	Frozen(SortedKeysDict({'lon': 320, 'bnds': 2, 'time': 1980, 'lat': 160, 'member_id': 1}))
CMIP.CAS.FGOALS-g3.historical.Amon.gn
	Frozen(SortedKeysDict({'lon': 180, 'bnds': 2, 'time': 2004, 'lat': 80, 'member_id': 3}))
CMIP.CCCma.CanESM5.historical.Amon.gn
	Frozen(SortedKeysDict({'lon': 128, 'bnds': 2, 'time': 1980, 'lat': 64, 'member_id': 49}))
CMIP.CNRM-CERFACS.CNRM-CM6-1.historical.Amon.gr
	Frozen(SortedKeysDict({'time': 1980, 'axis_nbounds': 2, 'lon': 256, 'lat': 128, 'member_id': 15}))
CMIP.CNRM-CERFACS.CNRM-ESM2-1.historical.Amon.gr
	Frozen(SortedKeysDict({'time': 1980, 'axis_nbounds': 2, 'lon': 256, 'lat': 128, 'member_id': 5}))
CMIP.E3SM-Project.E3SM-1-0.historical.Amon.gr
	Frozen(SortedKeysDict({'lon': 360, 'bnds': 2, 'time': 1980, 'lat': 180, 'member_id': 5}))
CMIP.EC-Earth-Consortium.EC-Earth3.historical.Amon.gr
	Frozen(SortedKeysDict({'j': 256, 'i': 512, 'time': 1981, 'bnds': 2, 'vertices': 4, 'lat': 514, 'lon': 512, 'member_id': 12}))
CMIP.EC-Earth-Consortium.EC-Earth3-Veg.historical.Amon.gr
	Frozen(SortedKeysDict({'lon': 512, 'bnds': 2, 'time': 1980, 'lat': 258, 'member_id': 4}))
CMIP.IPSL.IPSL-CM6A-LR.historical.Amon.gr
	Frozen(SortedKeysDict({'time': 1980, 'axis_nbounds': 2, 'lon': 144, 'lat': 143, 'member_id': 32}))
CMIP.MIROC.MIROC-ES2L.historical.Amon.gn
	Frozen(SortedKeysDict({'lon': 128, 'bnds': 2, 'time': 1980, 'lat': 64, 'member_id': 3}))
CMIP.MIROC.MIROC6.historical.Amon.gn
	Frozen(SortedKeysDict({'lon': 256, 'bnds': 2, 'time': 1980, 'lat': 128, 'member_id': 10}))
CMIP.MOHC.HadGEM3-GC31-LL.historical.Amon.gn
	Frozen(SortedKeysDict({'lon': 192, 'bnds': 2, 'time': 1980, 'lat': 144, 'member_id': 4}))
CMIP.MOHC.UKESM1-0-LL.historical.Amon.gn
	Frozen(SortedKeysDict({'lon': 192, 'bnds': 2, 'time': 1980, 'lat': 144, 'member_id': 9}))
CMIP.MRI.MRI-ESM2-0.historical.Amon.gn
	Frozen(SortedKeysDict({'lon': 320, 'bnds': 2, 'time': 1980, 'lat': 160, 'member_id': 5}))
CMIP.NASA-GISS.GISS-E2-1-G.historical.Amon.gn
	Frozen(SortedKeysDict({'lon': 144, 'bnds': 2, 'time': 1980, 'lat': 90, 'member_id': 22}))
CMIP.NASA-GISS.GISS-E2-1-H.historical.Amon.gn
	Frozen(SortedKeysDict({'lon': 144, 'bnds': 2, 'time': 1980, 'lat': 90, 'member_id': 10}))
CMIP.NCAR.CESM2.historical.Amon.gn
	Frozen(SortedKeysDict({'lon': 288, 'nbnd': 2, 'time': 1980, 'lat': 192, 'member_id': 11}))
CMIP.NCAR.CESM2-WACCM.historical.Amon.gn
	Frozen(SortedKeysDict({'lon': 288, 'nbnd': 2, 'time': 1980, 'lat': 192, 'member_id': 3}))
CMIP.NCC.NorESM2-LM.historical.Amon.gn
	Frozen(SortedKeysDict({'lon': 144, 'bnds': 2, 'time': 1980, 'lat': 96, 'member_id': 3}))
CMIP.NOAA-GFDL.GFDL-CM4.historical.Amon.gr1
	Frozen(SortedKeysDict({'lon': 288, 'bnds': 2, 'time': 1980, 'lat': 180, 'member_id': 1}))
CMIP.NOAA-GFDL.GFDL-ESM4.historical.Amon.gr1
	Frozen(SortedKeysDict({'lon': 288, 'bnds': 2, 'time': 780, 'lat': 180, 'member_id': 1}))
CMIP.NUIST.NESM3.historical.Amon.gn
	Frozen(SortedKeysDict({'lon': 192, 'bnds': 2, 'time': 1980, 'lat': 96, 'member_id': 5}))
CMIP.SNU.SAM0-UNICON.historical.Amon.gn
	Frozen(SortedKeysDict({'lon': 288, 'bnds': 2, 'time': 1980, 'lat': 192, 'member_id': 1}))

I haven't looked into these inconsistencies in the data yet!

authors: andersy005 dcherian matt-long pochedls

repo: NCAR/intake-esm


text:
PEAR-2159: Fix projects json download

Description
Also fixes: https://gdc-ctds.atlassian.net/browse/PEAR-2189
Checklist

[N/A] Added proper unit tests
[N/A] Left proper TODO messages for any remaining tasks
[N/A] Scanned for web accessibility with aXe, and mitigated or documented
flagged issues

Screenshots/Screen Recordings (if Appropriate)
https://github.com/user-attachments/assets/16cd7308-3abc-4a88-9ae8-e5bdbe723371

The error is gone, but now, when I search in the table, the JSON no longer reflects the results of the search. It contains all the projects. Same if I use the filters on the left.

looks good 👍

looks good! 👍 👍

authors: paribartandhakal wteouchicago

repo: NCI-GDC/gdc-frontend-framework


text:
Events Committee - Add more replacements

The events-commitee instance uses it's own aliases.mainnet.json. Which contains this "REPL_DEVHUB": "events-commitee.near",.
In order to replace components/core folders with the components of devhub.near we need extra replacements variables.
This does not changes much, all we need is to add two more replacements and points all components to events-committe.near at first so we can gradually point components to devhub.near.  As part of 777.
  "REPL_DEVHUB": "devhub.near",
  "REPL_EVENTS": "events-committee.near",

@race-of-sloths please score this PR.

repo: NEAR-DevHub/neardevhub-bos


text:
Events

Resolves https://github.com/NEARBuilders/gateway/issues/126

@itexpert120 Looks great, it works very well and I'm glad to see all the filters working. Some feedback:

[ ] clear filters doesn't clear the date fields (I'm a bit confused by the props.setFilters being passed around from modals -- any way you think to simplify it all? Or reasoning to justify current setup?)
[x] I renamed "fetchEvents" to "fetchThings", as it wasn't really specific to events (also renamed to lib.everything-sdk)
[ ] rename "test" to "every" once ready
[ ] Imagine if we want others to use this calendar component, how can we have the theme all define in one place for easy customization?

@itexpert120 Looks great, it works very well and I'm glad to see all the filters working. Some feedback:

[ ]  clear filters doesn't clear the date fields (I'm a bit confused by the props.setFilters being passed around from modals -- any way you think to simplify it all? Or reasoning to justify current setup?)
[x]  I renamed "fetchEvents" to "fetchThings", as it wasn't really specific to events (also renamed to lib.everything-sdk)
[ ]  rename "test" to "every" once ready
[ ]  Imagine if we want others to use this calendar component, how can we have the theme all define in one place for easy customization?

Thanks for the review @elliotBraem. The reason for having setFilter passed to filter Modal is because the filters are stored in parent component. This makes handling filters easier. If you have a better solution, please share and I'll implement it.

repo: NEARBuilders/gateway

license: Unlicense


text:
Change field name for Legacy Street Name Type from “LSt_Type” to “LSt_Typ”

Structural change between versions 1 and 2 or NENA-STA-006
Change field name for Legacy Street Name Type from “LSt_Type” to “LSt_Typ” in the RoadCenterLine layer and the SiteStructureAddressPoint layer.
Source
NENA-STA-006.2-2022 from sub-bullets in "Specific structural changes to the Data Model that were made:" bullet on page 13 under the Reason for Issue/Reissue section.

Adopted by Data Model Template working group Consent Agenda on 2022-11-23.


text:
Select seems only  support string 's ngModel, and will support the enum and number type?

Version
1.3.0
Environment
Win10 X64 Node LTS
Reproduction link
https://stackblitz.com/edit/ng-zorro-antd-enum-select
Steps to reproduce
Sometime we use the the enum type to regard the select.and in the ts language default ,the enum value is a number in fact.And i want to use the enum value to binding with the ngModel like
[(ngModel)]="menu.menuType"

And in my example.it can not show the correct value in the first Select.And when I use a string value,it seems correct in the second Select
What is expected?
The select can support the number value ,and also i found the select in multi select mode,it  also only support string .It would be nice if both single and multi mode can support the number value.
What is actually happening?
Can binding the ngModel with the number and enum type.
Other?

This is not the way how HTML <select></select> tag works. Your proposal is unnatural for other developers to understand. You should write code to find the index of the value if you really need it.

by view the source code and i  binding a compareWith function like this:
 static compareOjects(o1:any,o2:any):boolean
    {
        let result=false;
        if (o1===o2) {
            result=true;
        }
        if (o1.toString()===o2.toString()) {
            result=true;
        }
        return result;
    }

and i use it like this:
 <nz-select [nzDisabled]="editOrNew" [compareWith]="compareObject" name="status"  formControlName="status" placeholder="状态"  [(ngModel)]="record.status">
                      <nz-option nzValue="0" nzLabel="正常"></nz-option>
                      <nz-option nzValue="1" nzLabel="删除"></nz-option>
                      <nz-option nzValue="2" nzLabel="禁用"></nz-option>

                    </nz-select>

it works as i expect.the only this is two many step to do this .
It 's usually we get the dic from the server.and also there some option we usually do not change in the soft life.and use the enum is suitable.

authors: startewho wendzhue

repo: NG-ZORRO/ng-zorro-antd


text:
feat(module:steps): fix steps not rendered in async situation

close #3191
PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/NG-ZORRO/ng-zorro-antd/blob/master/CONTRIBUTING.md#commit
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features) Not needed

PR Type
What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Application (the showcase website) / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: #3191
If users do not put any nz-step in a nz-steps but wait for a sec, nz-step would not be rendered at all.
What is the new behavior?
Use can load nz-step asynchronously.
Does this PR introduce a breaking change?
[ ] Yes
[x] No

Other information

the below code can solve the same problem(#3191), can you explain? thanks
 if (this.steps) {
     // this.steps.changes.pipe(takeUntil(this.destroy$)).subscribe(this.updateChildrenSteps);
      this.steps.changes.pipe(takeUntil(this.destroy$)).subscribe(() => {
        this.updateChildrenSteps();
      });
    }

the below code can solve the same problem(#3191), can you explain? thanks
 if (this.steps) {
     // this.steps.changes.pipe(takeUntil(this.destroy$)).subscribe(this.updateChildrenSteps);
      this.steps.changes.pipe(takeUntil(this.destroy$)).subscribe(() => {
        this.updateChildrenSteps();
      });
    }

the below code can solve the same problem(#3191), can you explain? thanks
 if (this.steps) {
     // this.steps.changes.pipe(takeUntil(this.destroy$)).subscribe(this.updateChildrenSteps);
      this.steps.changes.pipe(takeUntil(this.destroy$)).subscribe(() => {
        this.updateChildrenSteps();
      });
    }

Oh, I misunderstood that problem.

authors: giscafer wendzhue


text:
xsd validace premis object

Z neznámého důvodu je při validaci PREMIS záznamu typu objekt v techMD s pomocí XSD vyhazována následující chyba:
UndeclaredPrefix: Cannot resolve 'premis:file' as a QName: the prefix 'premis' is not declared.
Jde o:
<premis:object xsi:type="premis:file">

Přižemž prefix "premis" definovaný je.
Validuje se oproti lokální kopii premis_2.2.xsd, pripadne mets_1.9.1.xsd.
Vypadá to na  bug samotné javy.

nedaří se mi replikovat.

Při validaci premisu pomocí Validátoru v2.1 vyskakuje chyba checkPremisIsValidByXsd: amd_mets_aee001-0005ka_0001.xml: OBJ_001: cvc-elt.4.2: Cannot resolve 'file' to a type definition for element 'premis:object'. Z mého pohledu by měla být hodnota v xsi:type="premis:file", pak projde validace oproti xsd korektně. Problém je že hodnota premis:file není uvedena ve standardu. V další verzi standardu by bylo vhodné tuto hodnotu doplnit

Ještě přikládám amd soubor
amd_mets_aee001-0005ka_0001.zip

Validátor zahlásí tuto chybu, když v elementu premis:object není definován namespace pro premis (tj. aby nedošlo k chybě, musí být otevírací tag v této podobě: <premis:object xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="premis:file" xmlns:premis="info:lc/xmlns/premis-v2">). Z nějakého důvodu tedy nefunguje dědičnost namespace definice z kořenového elementu mets:mets pro prefix premis použitý v hodnotě atributu.
@rzeh4n Nebude příčina třeba někde ve spouštěči validace premisu dle xsd? Nebo zde?

repo: NLCR/komplexni-validator


text:
Added F# FizzBuzz

Added F# version of the C# version of FizzBuzz  :)

Awesome! Thank you :)

authors: NLDev royvou


text:
DicAnalysis切词时，有些自定义词未切出来

添加了两个自定义词，包括"骁龙"， "魅族"。通过DicAnalysis切不出来，ToAnalysis可以
 String key = "dic_entity" ;
    DicLibrary.put(key, key, new Forest());
    DicLibrary.insert(key, "魅族", "entity", 1000);
    DicLibrary.insert(key, "骁龙", "entity", 1000);
    System.out.println(DicAnalysis.parse("魅族",DicLibrary.gets(key)));
    System.out.println(ToAnalysis.parse("魅族",DicLibrary.gets(key)));
    System.out.println(DicAnalysis.parse("骁龙",DicLibrary.gets(key)));
    System.out.println(ToAnalysis.parse("骁龙",DicLibrary.gets(key)));

result：
魅,族/ng
魅族/entity
骁,龙/n
骁龙/entity
@ansjsun

请问您的版本是?可能是版本问题.目前在我的代码中是正常的.您可以尝试升级最新版本
魅族/entity
魅族/entity
骁龙/entity
骁龙/entity

  我用的版本是5.1.0
  <dependency>
        <groupId>org.ansj</groupId>
        <artifactId>ansj_seg</artifactId>
        <version>5.1.0</version>
    </dependency>
    <dependency>
        <groupId>org.ansj</groupId>
        <artifactId>tree_split</artifactId>
        <version>1.5</version>
    </dependency>
    <dependency>
        <groupId>org.nlpcn</groupId>
        <artifactId>nlp-lang</artifactId>
        <version>1.7.2</version>
    </dependency>

升级到5.1.2 吧.这个版本是有问题的...ps maven只需要些

org.ansj
ansj_seg
5.1.2

其他都不用写..

authors: ansjsun liuboya


text:
Add support for various missing record types

As it says on the tin, but not complete yet. Will probably add support for more involved types, e.g. SVCB, in separate PRs.

Compiles now, onto tests...

Still need to fixup handling of unknown record types and there seems to be a quirk in the fallback scanner. After that this should be ready to go in. Fun fact: I now made sure that even on error, the data member in the token points to valid memory, allowing us to handle the unusual case of generic encoding (start RDATA with \\#) quicker. i.e. check if it starts with \\ instead of checking if it's CONTIGUOUS and then verifying it exactly matches \\#. This improves performance noticeably.

repo: NLnetLabs/simdzone


text:
logged time of event stays behind real time

Loggin configuration is:
<targets async="true">
  <target name="file" xsi:type="File"
        layout="${longdate}|${level:uppercase=true}|${logger}|${message}"
        fileName="log.txt"/>
</targets>

In log below you can see that time generated by NLog (start of line) is sometimes different than time saved in message by application. Later is synchronized again for a millisecond.

2013-12-02 15:33:09.6337|TRACE|TestActors.Program|2013-12-02 15:33:09.6337 a1.Request finished (9991) (9)
2013-12-02 15:33:09.6337|TRACE|TestActors.Program|2013-12-02 15:33:09.6337 a1.Request start (9990) (9)
2013-12-02 15:33:09.6337|TRACE|TestActors.Actor1|2013-12-02 15:33:09.6347 DoSomthing1 called (14)
2013-12-02 15:33:09.6337|TRACE|TestActors.Actor2|2013-12-02 15:33:09.6347 DoSomthing2 called (15)
2013-12-02 15:33:09.6337|TRACE|TestActors.Program|2013-12-02 15:33:09.6347 a1.Request finished (9990) (9)
2013-12-02 15:33:09.6337|TRACE|TestActors.Program|2013-12-02 15:33:09.6347 a1.Request start (9989) (9)
2013-12-02 15:33:09.6337|TRACE|TestActors.Actor1|2013-12-02 15:33:09.6347 DoSomthing1 called (14)
2013-12-02 15:33:09.6337|TRACE|TestActors.Actor2|2013-12-02 15:33:09.6347 DoSomthing2 called (15)
2013-12-02 15:33:09.6337|TRACE|TestActors.Program|2013-12-02 15:33:09.6347 a1.Request finished (9989) (9)
2013-12-02 15:33:09.6337|TRACE|TestActors.Program|2013-12-02 15:33:09.6347 a1.Request start (9988) (9)
2013-12-02 15:33:09.6337|TRACE|TestActors.Actor1|2013-12-02 15:33:09.6347 DoSomthing1 called (14)
2013-12-02 15:33:09.6337|TRACE|TestActors.Actor2|2013-12-02 15:33:09.6347 DoSomthing2 called (15)
2013-12-02 15:33:09.6337|TRACE|TestActors.Program|2013-12-02 15:33:09.6357 a1.Request finished (9988) (9)
2013-12-02 15:33:09.6337|TRACE|TestActors.Program|2013-12-02 15:33:09.6357 a1.Request start (9987) (9)
2013-12-02 15:33:09.6337|TRACE|TestActors.Actor1|2013-12-02 15:33:09.6357 DoSomthing1 called (14)
....
2013-12-02 15:33:09.6337|TRACE|TestActors.Program|2013-12-02 15:33:09.6485 a1.Request finished (9943) (9)
2013-12-02 15:33:09.6337|TRACE|TestActors.Program|2013-12-02 15:33:09.6485 a1.Request start (9942) (9)
2013-12-02 15:33:09.6337|TRACE|TestActors.Actor1|2013-12-02 15:33:09.6485 DoSomthing1 called (14)
2013-12-02 15:33:09.6495|TRACE|TestActors.Actor2|2013-12-02 15:33:09.6495 DoSomthing2 called (15)
2013-12-02 15:33:09.6495|TRACE|TestActors.Program|2013-12-02 15:33:09.6495 a1.Request finished (9942) (9)
2013-12-02 15:33:09.6495|TRACE|TestActors.Program|2013-12-02 15:33:09.6495 a1.Request start (9941) (9)
2013-12-02 15:33:09.6495|TRACE|TestActors.Actor1|2013-12-02 15:33:09.6495 DoSomthing1 called (14)
2013-12-02 15:33:09.6495|TRACE|TestActors.Actor2|2013-12-02 15:33:09.6495 DoSomthing2 called (15)

This seems the answer to your question.  So closing this one.
Thanks @ilya-g

repo: NLog/NLog


text:
.NET5 The log cannot be recorded to the database

Have generated nlog file record，The log cannot be recorded to the database
<?xml version="1.0" encoding="utf-8" ?>
<nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      autoReload="true"
      internalLogLevel="Warn">
	<extensions>
		<add assembly="NLog.Web.AspNetCore"/>
	</extensions>
	<!-- define various log targets -->
	<targets>
		<!-- write logs to file -->
		<target xsi:type="File" name="allfile" fileName="${basedir}/logs/nlog-all-${shortdate}.log"
					 layout="${longdate}|${event-properties:item=EventId.Id}|${logger}|${uppercase:${level}}|${message} ${exception}" />
		<target xsi:type="File" name="ownFile-web" fileName="${basedir}/logs/nlog-own-${shortdate}.log"
				 layout="${longdate}|${event-properties:item=EventId.Id}|${logger}|${uppercase:${level}}|  ${message} ${exception}" />

		<target name="database" xsi:type="Database">
			<connectionString>${var:connectionString}</connectionString>
			<commandText>
				INSERT INTO [AspNetLogs]([AppName],[MenuName],[LogType],[Url],[LogLevel],[StackTrace],[LogMessage],[IPAddress],[Remark],[CreatedOn],[UpdatedOn])
				                 VALUES (@AppName,@MenuName,@LogType,@Url,@LogLevel,@StackTrace,@LogMessage,@IPAddress,@Remark,@CreatedOn,@UpdatedOn)
			</commandText>
			<parameter name="@AppName" layout="DBCRM" />
			<parameter name="@MenuName" layout="${callsite}" />
			<parameter name="@LogType" layout="" />
			<parameter name="@Url" layout="${aspnet-request-url:IncludeQueryString=true}" />
			<parameter name="@LogLevel" layout="${level}" />
			<parameter name="@StackTrace" layout="${stacktrace}" />
			<parameter name="@LogMessage" layout="${message}" />
			<parameter name="@IPAddress" layout="${aspnet-request-ip}" />
			<parameter name="@Remark" layout="" />
			<parameter name="@CreatedOn" layout="${date}" />
			<parameter name="@UpdatedOn" layout="${date}" />
		</target>
	</targets>
	<rules>
		<!--All logs, including from Microsoft-->
		<logger name="*" minlevel="Trace" writeTo="allfile" />
		<!--Skip Microsoft logs and so log only own logs-->
		<logger name="Microsoft.*" minlevel="Trace" writeTo="blackhole" final="true" />
		<logger name="*" minlevel="Trace" writeTo="database" />
	</rules>
</nlog>```

Please include the output from the NLog InternalLogger

authors: DavidStrive snakefoot


text:
${Callsite} fix class naming when includeNamespace=false and cleanNamesOfAnonymousDelegates=true

Fixed Callsite class name of compiler generated type when includeNamespace=false and cleanNamesOfAnonymousDelegates=true.
Fixes #2762

Thanks!!


text:
[1pt] PR: refinements to usgs_gage_crosswalk.py

This pull request adds an additional feature_id attribute associated with USGS gage locations (feature_id obtained from the WRDS API) output in the usgs_gage_crosswalk.py. There is also a new USGS gage query to check that gage HUC8 matches the FIM HUC when performing the gage-huc spatial query (avoids duplicating gages in multiple HUCs). Address #498 #502
Changes

src/run_by_unit.sh: updated to include the HUC8 id as an input argument to usgs_gage_crosswalk.py when running fim_run.sh
usgs_gage_crosswalk.py: updated to include both feature_id (HAND-FIM crosswalked feature_id) and feature_id_wrds (feature_id assoicated with USGS gage location obtained from WRDS API). Also included the gage_distance_to_line attribute to potentially identify issues with correlating gage locations to the nearest thalweg pixel.

Screenshots
Example of USGS gage that was previously associated to two different HUCS. UGSG gage 01357500 falls with the boundaries of HUC 02020004 but is also inside the wbd_buffered boundary for huc 02020003 (orange polygon). This pull request uses the HUC8 attribute within the USGS gage layer to perform a HUC query within 'usgs_gage_crosswalk.py`. The final result in gage 01357500 is now associated with huc 02020004 and not huc 02020003.

Example of a new usgs_elev_table.csv for huc 02020003 with the new attributes highlighted in yellow

Notes

Check with team to determine if there are any pitfalls with this solution for ensuring gage is only associated with one HUC

Todos

Need to apply these changes to a full BED run for MS and FR

@RyanSpies-NOAA Has this been tested at the BED scale? I see your comment about needing to apply these changes to a full BED run for MS and FR.

@BradfordBates-NOAA I would like to kickoff a full MS BED run as soon as the API is updated to send outputs to the new shared dir.

@nickchadwick-noaa Are we still waiting for the machine(s) to come back online?

@BradfordBates-NOAA MS BED job is currently running on the API. I will check the results first thing tomorrow.

authors: BradfordBates-NOAA RyanSpies-NOAA

repo: NOAA-OWP/cahaba


text:
Nonlinear Reservoir Outlet Max Flow

Adding nonlinear reservoir max outlet flow parameter.
Additions
Adding nonlinear reservoir max outlet flow parameter.
Testing

Added corresponding unit test.

Notes
PR #56 needs to be merged before this one.
Fixes Issue #54
Checklist

[x] PR has an informative and human-readable title
[x] Changes are limited to a single goal (no scope creep)
[x] Code can be automatically merged (no conflicts)
[x] Code follows project standards (link if applicable)
[x] Passes all existing automated tests
[x] Any change in functionality is tested
[x] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged / future todos are captured in comments
[ ] Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)
[ ] Reviewers requested with the Reviewers tool :arrow_right:

Testing checklist (automated report can be put here)

Target Environment support

[ ] Linux

PR #56 has been merged into master. I rebased on top of master from that merge.

repo: NOAA-OWP/ngen


text:
Is there a way to stop the playback of automated audio in quest (ambience)?

When starting a quest there is an automated audio that plays. In events the audio command allows to start new sounds, but there is no way to halt the current ambience. This lead to multiple audio files playing above each other without any real control over the audio ambience of newly revealed tiles.
A "StopAudio" command would be very useful to set a certain mood when revealing new tiles.

Is what you want music control (#165)?  Or do you have a long audio sample on an event?

Currently, as soon as the quest starts one of the ambience sound effects starts playing. When I start another ambience track, these 2 play over each other.
What I´d like to do is stop the current ambience sound and play a new one.

Yes, this is #165, I will close this one.

authors: DelphiDie NPBruce

repo: NPBruce/valkyrie


text:
Clip charging is on by default for peak shaving

Describe the bug
When attempting to run the peak shaving algorithm for a DC connected battery such that it only charges from the grid, the clip-charging variable gets turned on inappropriately.
To Reproduce
Steps to reproduce the behavior:

Open a behind the meter battery case
Change the battery to DC connected
Uncheck charge from system and check charge from grid
Run simulate
See that the battery is charging from system

Expected behavior
The peak shaving algorithm should respect the choices in the UI. Clipped charging should always be off.
Operating System and Version

Version 2021.12.02r2 and develop

Additional context
I think the fix is likely to be in the UI equations. Workaround is to select price signals, check and uncheck clip charging, and then change back to peak shaving.

It looks like some of the recent UI defaults changes on develop have fixed this. I can reproduce this on  2021.12.02r2, but not on today's develop. Closing.

repo: NREL/SAM


text:
gendaylit1axis not finding match on EPW

EPW files are being shifted 1 hour to match TMY data. However this creates 1 extra entry the next year.

The current trackerdict matching between wanted startdate and enddate is very archaic, and it's failing to find 01/01 correctly since it ifnds it in the next year.

Temporary fix fixes the issue, but we should probably think of changing the way we are using matchers internally to match the desired date to the metadata datetimes by making the datetimes an integer... !!!

well, it sort of fixes the issue. If the enddate is the same, it creastes ALL the files.

However for other times it makes 0.

fixed in development branch


text:
Encoding.GetString calls in Portable Class Library projects

The C# code generated calls the Encoding.UTF8.GetString() with just the byte[] parameter, but for Portable Class Library projects, there is only the call with the bytes, index and count. Would it be possible to put this behavior in by default?
Example of code currently generated:
result_ = JsonConvert.DeserializeObject<OrderResponse>(Encoding.UTF8.GetString(responseData_));
Example of code that will should on any project type:
result_ = JsonConvert.DeserializeObject<OrderResponse>(Encoding.UTF8.GetString(responseData_, 0, responseData_.Length));

Fixed in https://github.com/NSwag/NSwag/commit/10ef3baa3ed1e05810e4af7070489f15503dbd24

repo: NSwag/NSwag


text:
Support for additionalProperties with specified schema

I tried modifying the PetStore example, adding additionalProperties to the Pet schema definition, in accordance with the Swagger–OpenAPI spec:
    "Pet": {
      "type": "object",
      "required": [
        "name",
        "photoUrls"
      ],
      "properties": {
        "id": {
          "type": "integer",
          "format": "int64"
        },
        "category": {
          "$ref": "#/definitions/Category"
        },
        ... (other properties)
      },
      "additionalProperties": {
        "type": "string"
      },
      "xml": {
        "name": "Pet"
      }
    }

The NSwag-generated C# client and server classes don't seem to have any provision for this additional collection of string properties.
I created this example in NSwag studio using "Create Local Copy" from http://petstore.swagger.io/v2/swagger.json.  Then I modified the schema a shown above, saved the .nswag file, and clicked Generate Outputs.  I'm new to NSwag, so if I missed a step, or I'm misreading the output, please let me know.
What I expected was something like an _additionalProperties property, whose value is an IDictionary<String, String>.  I guess this would need some special Newtonsoft attributes to make it serialize as part of the containing class.  Or, maybe the class itself should inherit from Dictionary.
Note that there are some limitations with additionalProperties support in Swagger's core Java libraries.  I've documented these in detail here.   In particular, Swagger doesn't really seem to support additionalProperties with a boolean true or false value.  You have to specify a schema as the value.
So that's the level of support I'm looking for, if it exists or can be added: additionalProperties with an embedded sub-schema or referenced schema specified as its value.

This should actually generate an additional property:
    [JsonExtensionData]
    public IDictionary<string, object> ExtensionData { get; set; }

With the value type of the schema.
This is an NJsonSchema issue and must be implemented there...

https://github.com/NJsonSchema/NJsonSchema/commit/6263b3fcd6f5f19edeef8ed402ab2549efb03d31

Thank you for the fast turnaround, @rsuter!  What is the best way for me to test this new feature?

https://github.com/NJsonSchema/NJsonSchema/commit/01c803d2f21e405d15a4045398249eda90aa8e2c

You can test with the latest CI build artifacts: https://ci.appveyor.com/project/rsuter/nswag-25x6o/build/artifacts

Generated code looks good.  Thanks again!

authors: rsuter tedepstein


text:
fix: solve transparency troubles

solves  #28

My pleasure 😅


text:
update MSVC compiler flags for modules

According to https://devblogs.microsoft.com/cppblog/standard-c20-modules-support-with-msvc-in-visual-studio-2019-version-16-8/ the compiler flags for MSVC have been updated. See under "Compiler Switch Overhaul". I had to use this in order to make the hello-world example compile.
Hope this helps.

Thank you for you PR. Can you modify it so it will still work for older MSVC versions?

@NTSFka I'm not sure what to check and how to do it succinctly. I can see the following:

https://cmake.org/cmake/help/latest/variable/CMAKE_LANG_COMPILER_VERSION.html
https://cmake.org/cmake/help/latest/variable/MSVC_VERSION.html#variable:MSVC_VERSION
https://cmake.org/cmake/help/latest/variable/MSVC_TOOLSET_VERSION.html

Firstly I'm not sure which version this was actually introduced with, the blogpost only mentions 16.8, so I'll assume it's that. However it's not mentioned in any of their changelogs: https://github.com/microsoft/STL/wiki/Changelog.
I'm also not sure which numbers for MSVC_VERSION correspond to a given version. Mine currently says 1928. I would infer that 16.0 -> 1920 and 16.8 -> 1928?

Yeah, MSVC_VERSION should be fine.
I was also trying to find which specific version introduces the new flags and found nothing. Compiler flag documentation (https://docs.microsoft.com/en-us/cpp/build/reference/experimental-module?view=msvc-160) describes old flags - it's updated a day before the blog post.

authors: NTSFka samwalls

repo: NTSFka/CMakeCxxModules


text:
remove array-init

dependencyless woohoo!

somehow the MSRV doesn't even change

no, I reverted that. Thought it would change the MSRV, but then I actually checked

We bumped the MSRV with the edition update anyways


text:
Replacement for TBS discovery drone?

Is there a good replacement for the TBS discovery drone? I just got off the phone with TBS and they stated that the discovery has been out of production for about 2 years now. Could someone recommend something compatible that this redtail wiki could still support? Or where they still have the discovery in stock?
Thanks

@Alexey-Kamenev
Thank you for the response. I will do some research into different types of kits and see if something else will work for me.

@daylanc I had success with a DJI F550 kit – I couldn't buy the TBD Discovery neither, so ended up getting the F550. It still seems to be available in a few shops. I had to design and 3d print a few additional parts (to mount the Jetson TX2 and the battery) – I can share the details if you're interested.

@EEGL
Yes please! That would really help me out!

@EEGL Would you be willing to share some pics of how you mounted your Jetson to the F550?  Would you be willing to share designs of your 3D printed parts?

@eeglbalazs
Could you share the details of your F550 build with me? Which propellers, motors, batteries, ESCs, etc. did you choose to use?

@daylanc @briannelson45 Here are details for the F550 build https://github.com/eegl/Redtail-F550-Build/wiki If you read through the TBS build in this Redtail repo and then check my instructions, that should be enough to get you going. One thing I don't remember is which screws I used to assemble the 3d printed parts.

authors: EEGL briannelson45 daylanc eeglbalazs

repo: NVIDIA-AI-IOT/redtail


text:
Remove imports to deprecated modules

Functionality like dispatch,io,utils,graph has moved to the merlin-core package.
This change fixes imports to use the merlin-core packages directly, instead of
the API compatability stubs included here

Its a nice to have - there are a bunch of warnings being thrown in the notebooks etc, and this will help clean them up

authors: benfred viswa-nvidia

repo: NVIDIA-Merlin/NVTabular


text:
Remove explicit DictArray reference from merlin.core.dispatch

This chunk of code makes it difficult to refactor Systems, since we'd like to copy DictArray into that code base while we work out what the new Column abstraction should look like with the plan to migrate the changes back to Merlin Core once we're happy with them and have the Systems tests passing.
The rewrite here changes the isinstance() checks to use protocols instead of the concrete DictArray class, which allows both the DictArray implementation here and the temporary one in Systems to be dispatched correctly.

(The test failures in NVT and Models appear unrelated)

repo: NVIDIA-Merlin/core


text:
use rapids infra to run testing

This PR activates rapids resources to run ci tests

/ok to test

/ok to test

/ok to test

/ok to test

/ok to test

/ok to test

/ok to test

/ok to test

/ok to test

/ok to test

repo: NVIDIA-Merlin/models


text:
[nvmdev] fix bug in construction of parent PCI device

When constructing NvidiaPCIDevice objects for each 'parent' device in the '/sys/class/mdev_bus' directory, use the default PCI devices root '/sys/bus/pci/devices'. All devices in '/sys/class/mdev_bus' will have a corresponding directory at '/sys/bus/pci/devices'.
Starting with https://github.com/NVIDIA/go-nvlib/commit/bf3f431fc86e4ab07c782e2a0d1e2855f8352c3e0 the construction of the NvidiaPCIDevice object will fail when attempting to detect the physfn. When SRIOV is used, all the VFs will show up under '/sys/class/mdev_bus', but the physfn will only show up under '/sys/bus/pci/devices'.

The commit you linked is a broken link. What was the change that broke things?

https://github.com/NVIDIA/go-nvlib/commit/bf3f431fc86e4ab07c782e2a0d1e2855f8352c3e

@PiotrProkop can you take a look at this

To provide more context, a call to nvmdev.GetAllParentDevices() results in the following error:
error getting all parent devices: error constructing NVIDIA parent device: failed to construct NVIDIA PCI device: unable to detect physfn for 0000:3b:00.4: unable to read PCI device vendor id for 0000:3b:00.0: open /sys/class/mdev_bus/0000:3b:00.0/vendor: no such file or directory"

0000:3b:00.0 is the PF for 0000:3b:00.4 (VF). 0000:3b:00.4 and all the other VFs will have entries at /sys/class/mdev_bus, but the PF does not.

Good catch!
/lgtm

authors: PiotrProkop cdesiniotis klueska

repo: NVIDIA/go-nvlib


text:
Fix bug with latitude weighting

Modulus Pull Request
Description
This PR fixes a bug where the latitude weights in the diagnostic model training example were computed incorrectly at the poles (and only at the poles).
Checklist

[x] I am familiar with the Contributing Guidelines.
[x] New or existing tests cover these changes.
[x] The documentation is up to date with these changes.
[ ] The CHANGELOG.md is up to date with these changes.
[ ] An issue is linked to this pull request.

Dependencies

/blossom-ci

repo: NVIDIA/modulus


text:
[submodule-sync] bot-submodule-sync-branch-23.06 to branch-23.06 [skip ci] [bot]

submodule-sync to create a PR keeping thirdparty/cudf up-to-date.
HEAD commit SHA: 6e186c8f22b316f3a765f732ac4be2e4b9c7043d, cudf commit SHA: https://github.com/rapidsai/cudf/commit/9be347f19d35aae1318abdabd2c3b38f4520c472
This PR will be auto-merged if test passed. If failed, it will remain open until test pass or manually fix.

HEAD commit SHA: 6e186c8f22b316f3a765f732ac4be2e4b9c7043d, CUDF commit SHA: https://github.com/rapidsai/cudf/commit/9be347f19d35aae1318abdabd2c3b38f4520c472
Test passed: True

SUCCESS - auto-merge

repo: NVIDIA/spark-rapids-jni


text:
[submodule-sync] bot-submodule-sync-branch-24.10 to branch-24.10 [skip ci] [bot]

submodule-sync to create a PR keeping thirdparty/cudf up-to-date.
HEAD commit SHA: 6d922a7f8aff64297684b9d6cf5f6112899d393c, cudf commit SHA: https://github.com/rapidsai/cudf/commit/124d3e353eeebd595da113dbef3d5bad842a791d
This PR will be auto-merged if test passed. If failed, it will remain open until test pass or manually fix.

HEAD commit SHA: 6d922a7f8aff64297684b9d6cf5f6112899d393c, CUDF commit SHA: https://github.com/rapidsai/cudf/commit/124d3e353eeebd595da113dbef3d5bad842a791d
Test passed: True

SUCCESS - auto-merge


text:
fix benchmarks for py3.8

Fixes discrepancies in behavior of inspect.signature() between py3.8 and py3.9 by forcing the code to inspect the __init__ function.

How does this problem surface?   I haven't encountered any issues in a 3.8 env in DB.

Saw this behavior in a local conda env and in docker containers built from the dockerfiles.  When running ./run_benchmark.sh, I got this error:
benchmark_runner.py: error: unrecognized arguments: --k 3

The problem occurs when calling benchmark.utils.inspect_default_params_from_func(). Would the same problem exists in calling spark_rapids_ml.utils._get_default_params_from_func()? The two functions look very similar that have the same set of arguments (func: Callable, unsupported_set: List[str] = []).

The problem occurs when calling benchmark.utils.inspect_default_params_from_func(). Would the same problem exists in calling spark_rapids_ml.utils._get_default_params_from_func()? The two functions look very similar that have the same set of arguments (func: Callable, unsupported_set: List[str] = []).

Yeah, the problem seems to be isolated to the Spark class constructors.  The cuML constructors worked fine, so it looks like some combination of py3.8 + spark.

FYI, confirmed that the problem is specific to py3.8 + pyspark 3.3.  Pyspark 3.2 works fine with py3.8.

authors: eordentlich leewyang lijinf2

repo: NVIDIA/spark-rapids-ml


text:
Unshim common classes after spark31x removal

Is your feature request related to a problem? Please describe.
After #11159, there are a number of classes that are under a spark-specific shim directory but are now common across all supported Spark versions.
Describe the solution you'd like
Shimmed classes that are now common should be moved to the standard paths and shim directives removed to simplify the code base.Identify common classes.  Base classes or traits that only existed for shim reasons and no longer need to be shims should be removed (e.g.: ShimUnaryExpression and many other classes in TreeNode.scala).

Here's a naive approach to identifying candidates for unshimming, which is seeing how many files under sql-plugin/src/main/spark320/ have no other peers after #11159:
$ cd sql-plugin/src/main/spark320
$ for i in $(find . -type f);do count=$(ls ../*/$i | wc -l); if [[ $count == 1 ]];then echo $i;fi;done
./scala/com/nvidia/spark/rapids/v1FallbackWriters.scala
./scala/com/nvidia/spark/rapids/shims/GpuOrcDataReaderBase.scala
./scala/com/nvidia/spark/rapids/shims/Spark320PlusShims.scala
./scala/com/nvidia/spark/rapids/shims/HashUtils.scala
./scala/com/nvidia/spark/rapids/shims/YearParseUtil.scala
./scala/com/nvidia/spark/rapids/shims/CudfUnsafeRowBase.scala
./scala/com/nvidia/spark/rapids/shims/ShimBaseSubqueryExec.scala
./scala/com/nvidia/spark/rapids/shims/OffsetWindowFunctionMeta.scala
./scala/com/nvidia/spark/rapids/shims/ShimAQEShuffleReadExec.scala
./scala/com/nvidia/spark/rapids/shims/extractValueShims.scala
./scala/com/nvidia/spark/rapids/shims/TreeNode.scala
./scala/com/nvidia/spark/rapids/shims/ShimPredicateHelper.scala
./scala/com/nvidia/spark/rapids/shims/gpuWindows.scala
./scala/com/nvidia/spark/rapids/shims/TypeSigUtil.scala
./scala/com/nvidia/spark/rapids/shims/GpuOrcDataReader320Plus.scala
./scala/com/nvidia/spark/rapids/shims/RapidsCsvScanMeta.scala
./scala/com/nvidia/spark/rapids/shims/Spark31Xuntil33XShims.scala
./scala/com/nvidia/spark/rapids/shims/AnsiCastRuleShims.scala
./scala/com/nvidia/spark/rapids/shims/RebaseShims.scala
./scala/com/nvidia/spark/rapids/shims/GpuBatchScanExecBase.scala
./scala/com/nvidia/spark/rapids/shims/OrcShims320untilAllBase.scala
./scala/com/nvidia/spark/rapids/shims/Spark320PlusNonDBShims.scala
./scala/com/nvidia/spark/rapids/shims/spark320/SparkShimServiceProvider.scala
./scala/com/nvidia/spark/rapids/spark320/RapidsShuffleManager.scala
./scala/org/apache/spark/rapids/shims/GpuShuffleBlockResolver.scala
./scala/org/apache/spark/rapids/shims/ShuffledBatchRDDUtil.scala
./scala/org/apache/spark/rapids/shims/storage/ShimDiskBlockManager.scala
./scala/org/apache/spark/sql/rapids/shims/misc.scala
./scala/org/apache/spark/sql/rapids/shims/Spark32XShimsUtils.scala
./scala/org/apache/spark/sql/rapids/shims/AvroUtils.scala
./scala/org/apache/spark/sql/rapids/shims/RapidsQueryErrorUtils.scala
./scala/org/apache/spark/sql/rapids/shims/RapidsShuffleThreadedWriter.scala
./scala/org/apache/spark/sql/rapids/shims/datetimeExpressions.scala
./scala/org/apache/spark/sql/rapids/GpuDataSource.scala
./scala/org/apache/spark/sql/execution/ShimTrampolineUtil.scala
./scala/org/apache/spark/sql/hive/rapids/shims/GpuInsertIntoHiveTable.scala
./scala/org/apache/spark/sql/hive/rapids/shims/GpuCreateHiveTableAsSelectCommand.scala
./scala/org/apache/spark/storage/RapidsShuffleBlockFetcherIterator.scala
./scala/org/apache/spark/storage/RapidsPushBasedFetchHelper.scala
./java/com/nvidia/spark/rapids/shims/ShimSupportsRuntimeFiltering.java
./java/com/nvidia/spark/rapids/shims/XxHash64Shims.scala

repo: NVIDIA/spark-rapids