test sync_wait_tests.cpp /"multiple threads" hangs on mac osx

output on the console after ctrl-c under lldb:
...
sync_wait(task<T>)
sync_wait(shared_task<T>)
multiple threads

Process 12959 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = signal SIGSTOP
    frame #0: 0x00007fff7296a7de libsystem_kernel.dylib`__psynch_cvwait + 10
libsystem_kernel.dylib`__psynch_cvwait:
->  0x7fff7296a7de <+10>: jae    0x7fff7296a7e8            ; <+20>
    0x7fff7296a7e0 <+12>: movq   %rax, %rdi
    0x7fff7296a7e3 <+15>: jmp    0x7fff729673b7            ; cerror_nocancel
    0x7fff7296a7e8 <+20>: retq
Target 0: (cppcoro_tests) stopped.
(lldb) bt
* thread #1, queue = 'com.apple.main-thread', stop reason = signal SIGSTOP
  * frame #0: 0x00007fff7296a7de libsystem_kernel.dylib`__psynch_cvwait + 10
    frame #1: 0x00007fff72a24593 libsystem_pthread.dylib`_pthread_cond_wait + 724
    frame #2: 0x00007fff6ff03bda libc++.1.dylib`std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 18
    frame #3: 0x000000010029c331 cppcoro_tests`void std::__1::condition_variable::wait<cppcoro::detail::lightweight_manual_reset_event::wait()::$_0>(this=0x00007ffeefbfd900, __lk=0x00007ffeefbfd800, __pred=(anonymous class) @ 0x00007ffeefbfd7a8)::$_0) at __mutex_base:375
    frame #4: 0x000000010029c24f cppcoro_tests`cppcoro::detail::lightweight_manual_reset_event::wait(this=0x00007ffeefbfd8c0) at lightweight_manual_reset_event.cpp:234
    frame #5: 0x00000001001ad241 cppcoro_tests`cppcoro::awaitable_traits<cppcoro::task<int>&&, void>::await_result_t cppcoro::sync_wait<cppcoro::task<int> >(awaitable=0x00007ffeefbfd970) at sync_wait.hpp:32
    frame #6: 0x00000001001a9d49 cppcoro_tests`_DOCTEST_ANON_FUNC_8() at sync_wait_tests.cpp:72
    frame #7: 0x000000010012a72d cppcoro_tests`doctest::Context::run(this=0x00007ffeefbff108) at doctest.h:5651
    frame #8: 0x000000010012b4b6 cppcoro_tests`main(argc=1, argv=0x00007ffeefbff148) at doctest.h:5759
    frame #9: 0x00007fff7282ded9 libdyld.dylib`start + 1
    frame #10: 0x00007fff7282ded9 libdyld.dylib`start + 1
(lldb)```

The test just hangs for ever.
$ clang -v
clang version 7.0.0 (tags/RELEASE_700/final)
Target: x86_64-apple-darwin18.2.0
Thread model: posix
InstalledDir: /usr/local/opt/llvm/bin```

I spent a few min to debug this. I added
		printf("before schedule\n");
		co_await tp.schedule();
		printf("after schedule\n");

output, and changed the number of times the loop runs:
with 10 - success
with 100 - success
with 1000 - success
with 10'000 - hangs or fails with libc++abi.dylib: terminating with uncaught exception of type std::__1::system_error: condition_variable wait failed: Invalid argument

Actually, after printing the value itself it became clear the number of iterations is  not directly relevant. The test simply has some sort of a race condition. Some time it passes, some time is hangs after 7 iterations, some time after 89. Ex:
before schedule: 204
after schedule: 204
before schedule: 205
after schedule: 205
before schedule: 206
after schedule: 206
before schedule: 207
after schedule: 207
before schedule: 208
after schedule: 208
before schedule: 209
after schedule: 209
before schedule: 210
after schedule: 210
before schedule: 211
after schedule: 211
before schedule: 212
after schedule: 212
before schedule: 213
after schedule: 213
before schedule: 214
after schedule: 214
before schedule: 215
after schedule: 215
before schedule: 216
after schedule: 216
before schedule: 217
after schedule: 217
before schedule: 218
after schedule: 218
before schedule: 219
after schedule: 219
before schedule: 220
after schedule: 220
before schedule: 221
after schedule: 221
before schedule: 222
after schedule: 222
before schedule: 223
after schedule: 223
before schedule: 224
after schedule: 224

<hang>

So the thread in the static thread pool and the main thread are clashing when accessing the task state somewhere.

Thread #2:
  * frame #0: 0x00007fff7296a7de libsystem_kernel.dylib`__psynch_cvwait + 10
    frame #1: 0x00007fff72a24593 libsystem_pthread.dylib`_pthread_cond_wait + 724
    frame #2: 0x00007fff6ff03bda libc++.1.dylib`std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 18
    frame #3: 0x0000000100290a2e cppcoro_tests`cppcoro::auto_reset_event::wait(this=0x00000001017000f0) at auto_reset_event.cpp:91
    frame #4: 0x00000001002a00b9 cppcoro_tests`cppcoro::static_thread_pool::thread_state::sleep_until_woken(this=0x00000001017000c8) at static_thread_pool.cpp:76
    frame #5: 0x000000010029ebfd cppcoro_tests`cppcoro::static_thread_pool::run_worker_thread(this=0x00007ffeefbfda50, threadIndex=0) at static_thread_pool.cpp:485
    frame #6: 0x00000001002a548e cppcoro_tests`cppcoro::static_thread_pool::static_thread_pool(this=0x0000000101700058)::$_0::operator()() const at static_thread_pool.cpp:346
    frame #7: 0x00000001002a5231 cppcoro_tests`void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, cppcoro::static_thread_pool::static_thread_pool(unsigned int)::$_0> >(void*) [inlined] decltype(__f=0x0000000101700058)::$_0>(fp)(std::__1::forward<>(fp0))) std::__1::__invoke<cppcoro::static_thread_pool::static_thread_pool(unsigned int)::$_0>(cppcoro::static_thread_pool::static_thread_pool(unsigned int)::$_0&&) at type_traits:4345
    frame #8: 0x00000001002a5220 cppcoro_tests`void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, cppcoro::static_thread_pool::static_thread_pool(unsigned int)::$_0> >(void*) [inlined] void std::__1::__thread_execute<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, cppcoro::static_thread_pool::static_thread_pool(unsigned int)::$_0>(__t=size=2)::$_0>&, std::__1::__tuple_indices<>) at thread:342
    frame #9: 0x00000001002a51fc cppcoro_tests`void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, cppcoro::static_thread_pool::static_thread_pool(unsigned int)::$_0> >(__vp=0x0000000101700050) at thread:352
    frame #10: 0x00007fff72a21305 libsystem_pthread.dylib`_pthread_body + 126
    frame #11: 0x00007fff72a2426f libsystem_pthread.dylib`_pthread_start + 70
    frame #12: 0x00007fff72a20415 libsystem_pthread.dylib`thread_start + 13```

Thread #1:
* thread #1, queue = 'com.apple.main-thread', stop reason = signal SIGSTOP
  * frame #0: 0x00007fff7296a7de libsystem_kernel.dylib`__psynch_cvwait + 10
    frame #1: 0x00007fff72a24593 libsystem_pthread.dylib`_pthread_cond_wait + 724
    frame #2: 0x00007fff6ff03bda libc++.1.dylib`std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 18
    frame #3: 0x000000010029d211 cppcoro_tests`void std::__1::condition_variable::wait<cppcoro::detail::lightweight_manual_reset_event::wait()::$_0>(this=0x00007ffeefbfd900, __lk=0x00007ffeefbfd800, __pred=(anonymous class) @ 0x00007ffeefbfd7a8)::$_0) at __mutex_base:375
    frame #4: 0x000000010029d12f cppcoro_tests`cppcoro::detail::lightweight_manual_reset_event::wait(this=0x00007ffeefbfd8c0) at lightweight_manual_reset_event.cpp:234
    frame #5: 0x00000001001add61 cppcoro_tests`cppcoro::awaitable_traits<cppcoro::task<int>&&, void>::await_result_t cppcoro::sync_wait<cppcoro::task<int> >(awaitable=0x00007ffeefbfd970) at sync_wait.hpp:32
    frame #6: 0x00000001001aa869 cppcoro_tests`_DOCTEST_ANON_FUNC_8() at sync_wait_tests.cpp:74
    frame #7: 0x000000010012b24d cppcoro_tests`doctest::Context::run(this=0x00007ffeefbff108) at doctest.h:5651
    frame #8: 0x000000010012bfd6 cppcoro_tests`main(argc=1, argv=0x00007ffeefbff148) at doctest.h:5759
    frame #9: 0x00007fff7282ded9 libdyld.dylib`start + 1
    frame #10: 0x00007fff7282ded9 libdyld.dylib`start + 1

I've made this change in 0a768bf45ec73c77c27d56221fced350cdc8a7f5.
@yfinkelstein Let me know if you still see this issue with latest master.

I suspect there is a bug in the lightweight_manual_reset_event::set() method:
void cppcoro::detail::lightweight_manual_reset_event::set() noexcept
{
	{
		std::lock_guard<std::mutex> lock(m_mutex);
		m_isSet = true;
	}
	m_cv.notify_all();
}

I think by having the call to notify_all() outside of the critical section it may potentially miss waking up a a thread that is blocked inside .wait().
Can you try moving this call inside the scope of the lock_guard and see if that fixes the hang?

This should not matter. See this old discussion thread: https://groups.google.com/forum/?hl=ky#!msg/comp.programming.threads/wEUgPq541v8/ZByyyS8acqMJ

I wrote:

This should not matter. See this old discussion thread: https://groups.google.com/forum/?hl=ky#!msg/comp.programming.threads/wEUgPq541v8/ZByyyS8acqMJ

Looking at your comment on commit 0a768bf again, I was wrong. Obviously, if setting m_isSet to true implies permission for another thread to destroy the condition variable, then it must be guaranteed that the new value of m_isSet is not observable yet when notify_all() is called. Sorry for the noise!

@wilevers Your original comment was valid based on a response to my comment on this thread. Indeed, whether or not the call to notify_all() was done inside or outside of the critical section shouldn't cause a missed wake-up.
But, yes, there was another problem which was that it's possible the cv.notify_all() call could be running concurrently with cv's destructor or possibly even concurrently with the constructor of a different condition_variable that was being constructed in the same place.
This seems to be the most likely cause for the condition_variable wait failed: Invalid argument error that @yfinkelstein was seeing. And could plausibly also have been responsible for the hangs.
I'm marking this issue as closed but feel free to reopen if you are still seeing it.

But, yes, there was another problem which was that it's possible the cv.notify_all() call could be running concurrently with cv's destructor or possibly even concurrently with the constructor of a different condition_variable that was being constructed in the same place.
This seems to be the most likely cause for the condition_variable wait failed: Invalid argument error that @yfinkelstein was seeing. And could plausibly also have been responsible for the hangs.
I'm marking this issue as closed but feel free to reopen if you are still seeing it.

Excellent. Thank you, and again, sorry for the noise...


Fix Bad Field type panic

Fixes Or Enhances
Fixes #907 (and possibly others?)
At first I found it weird that the required_if affected the behavior of the gte tag, but after some debugging it seems that the condition runValidationWhenNil is not checked for each field tag, but only for the first one.
In this case it was set to true for the required_if tag, but set to false for gte, so when the required_if preceded the gte tag it meant that the field was incorrectly validated through gte even when it was nil.
Make sure that you've checked the boxes below before you submit PR:

[x] Tests exist or have been written that cover this particular change.

@go-playground/validator-maintainers

coverage: 73.933% (+0.03%) from 73.903%
when pulling d015ea40f59bae1e210eba68b3db03e4b8e31111 on darklam:fix-bad-field-type-panic
into 84254aeb5a59e615ec0b66ab53b988bc0677f55e on go-playground:master.

Thanks fro the PR @darklam
I will have to think hard on if this could cause any breaking side-effects, see here for details.

Thanks fro the PR @darklam
I will have to think hard on if this could cause any breaking side-effects, see here for details.

Yes, agreed that this should be scrutinized a lot regarding breaking changes before merging. I'm happy to add more test cases if there are any specific ones coming to mind.
Also, my first thought was indeed to change some baked ins like gte to handle nil cases, but it didn't seem like the way to go because it became quite repetitive.
I think that the check for that should happen before getting to these validators (as the original intention seems to be with the runValidationWhenNil flag), but of course this is not an informed opinion as I'm quite new with the codebase 😄


Added tests for automatic differentiation

Tested packages include:

ForwardDiff.jl: Works!
ReverseDiff.jl: Not yet working.
Zygote.jl: Not yet working.

Are you overloading solve or __solve? You'll want to use the later and do using DiffEqSensitivity so that it's then captured by the adjoint rrules.

You'll then want to adjust some of these adjoint rules https://github.com/SciML/DiffEqBase.jl/blob/master/src/chainrules.jl#L11-L19 to your new solution type.

Are you overloading solve or __solve? You'll want to use the later and do using DiffEqSensitivity so that it's then captured by the adjoint rrules.

I'm overloading neither right now, I fully built on OrdinaryDiffEq.jl and basically only overload perform_step! and alg_cache, and some more functions that relate to saving values and to the solution object. Which worked well so far! But maybe autodiff is something where I need a bit more control?
And in general, my plan was to soon support backward-mode AD of some form (using ReverseDiff.jl / Zygote.jl / Tracker.jl through the solver). Continuous sensitivites would be nice at some point, but that might need some more research first.

Codecov Report

Merging #41 (bb2812c) into main (e0a3595) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #41   +/-   ##
=======================================
  Coverage   92.75%   92.75%
=======================================
  Files          19       19
  Lines         649      649
=======================================
  Hits          602      602
  Misses         47       47

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 e0a3595...bb2812c. Read the comment docs.


Feat/add prompt suggesting to log-in to water

added disabled button I watered button when logged out
added required attribute to watered amount and date inputs
added onclick listener to close dialog when clicking in the background

fixed clicking outside of dialog
now I can also see the notification about the missing amount
adjusted styling (went back to tertiary button after talking to Emma)


Unknown Type 0x6

I crashed Windows via notmyfault.exe with debugging file option [Automatic memory dump].
The generated dump file is passed through the
. \parser.exe -c -e -p 0x1000 D:\vmware_share\MEMORY.DMP
Execution, hint:
Unknown Type 0x6. The header looks wrong. ParseDmpHeader failed. Parsing of the dump failed, exiting.
So this dump format itself won't be supported? How is it different from other types?

When I debug parser.exe to parse a dmp file with dumptype 6 via windbg, I found that it is able to parse it. Does that mean it's supported?

Let me see..

Indeed, the type '6' isn't supported; here are the ones currently supported:
enum class DumpType_t : uint32_t {
  // Old dump types from dbgeng.dll
  FullDump = 0x1,
  KernelDump = 0x2,
  BMPDump = 0x5,

  // New stuff
  MiniDump = 0x4,                // Produced by `.dump /m`
  KernelMemoryDump = 0x8,        // Produced by `.dump /k`
  KernelAndUserMemoryDump = 0x9, // Produced by `.dump /ka`
  CompleteMemoryDump = 0xa,      // Produced by `.dump /f`
};

I don't think I have ever ran into a type 6 dump yet 😅
What you are saying is the first header of the dump file which is the same across dumps, but then it is followed by other header / data that depends on the type of dump it is. Because kdmp-parser doesn't know about this type 6, it doesn't know how to handle what follow the main header.
I'll leave this issue opened in case somebody feels like reverse-engineering / implementing it!
Thank you for your report :)
Cheers

Thank you for your reply.
I've searched the web and haven't found a specific meaning for dumptype being BMPDump. What is the source of the various types of dumptype, please?

Sorry I am not sure I understood the question - I believe 'BMP' means
'Bitmap' and refer to the way the physical memory is stored in the dump if
I remember correctly.
Cheers
On Tue, Feb 20, 2024 at 10:29 PM frendguo @.***> wrote:

Thank you for your reply.
I've searched the web and haven't found a specific meaning for dumptype
being BMPDump. What is the source of the various types of dumptype, please?
—
Reply to this email directly, view it on GitHub
https://github.com/0vercl0k/kdmp-parser/issues/26#issuecomment-1955979098,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AALIORK7MBF77KK7FY23EH3YUWH25AVCNFSM6AAAAABDQXHKN6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJVHE3TSMBZHA
.
You are receiving this because you commented.Message ID:
@.***>

Thanks for the reply.
Cheers

@frendguo I don't think I've ever seen a type 6 dump. How did you generate it?

I came across this error.
Type 6 is a live kernel dump. We can create this with the task manager. On the process list view, right click on the System process -> Create live kernel memory dump file. You see two options but both generate a type 6 dump file.

I came across this error.
Type 6 is a live kernel dump. We can create this with the task manager. On the process list view, right click on the System process -> Create live kernel memory dump file. You see two options but both generate a type 6 dump file.

Thanks for that update @tandasat I can reproduce on Win11 22H2 and up. I will look into it!

@tandasat / @frendguo this should be fixed in v0.7.4.
Cheers

Excellent. Thank you for fixing the issue!

Thank you for sharing the repro information @tandasat, and thank you @hugsy for implementing it 🫡

@hugsy @0vercl0k wow, thank you for fixing this issue!


macs2 bdgdiff for calling differential binding events without control

I had one treated sample and one non-treated sample, but without Chip-Seq mock (or background control). But I want to identify regions that are differentially histone modification between control and treated. MACS2 bdgdiff is a prefect tool to complete the differential analysis of Chip-seq between two conditions. But how could MACS2 bdgdiff identify differential peaks without ChIP-Seq control. I really appreciate your help.
Thanks a lot!

I haven't tested if bdgdiff works fine on two conditions without control. Theoretically it should be able to run through but I haven't studied if the results look fine. In this case, I would suggest you to generate treatment bdg files  for two condition from callpeak or pileup function, then compare them directly using bdgcmp.

Hi Sorry to hijack the post, but we are having the same issue
4 ChIP experiments without mock IP data
We are very confused as to which parameters to call. Please help!
This is what we did

callpeak with --dup all --nomodel -extsize <average frag length from 4 datasets> --nolambda --call-summits -B
dup all - because the redundancy rate in the datasets are high ~0.79
nolambda - because no control data
nomodel & extsize as mentioned in bdgdiff tutorial

Which method should I choose for bdgcmp?
I tried ppois and got a bed file. What does the last column indicate?

Also How do I use the -S (scaling factor) option to normalize among the 4 datasets?

I haven't tested if bdgdiff works fine on two conditions without control. Theoretically it should be able to run through but I haven't studied if the results look fine. In this case, I would suggest you to generate treatment bdg files for two condition from callpeak or pileup function, then compare them directly using bdgcmp.

Hi Tao Liu,
Could you please elaborate on how to compare the treatment bdg files for two conditions from callpeak or pileup function directly using bdgcmp, as you have suggested here?
In your tutorial on how to build a signal track you explain how to generate the bdg files, how to compare them using bdgcmp, how to convert the *_FE.bdg and *logLR.bdg files to bigWig etc. - but at the end you use wigCorrelate on the two *_FE.bdg files from the two different samples, which is what we don't have in this case - only one treatment file and one control file, i.e., we only have one *FE.bdg file.
Thank you so much for your help!


Website Builder Not Working

There is an error when trying to "Play Plasmic Levels" or start with a template.
Tried on Chromium and Firefox.
Unexpected error
Error: Loading CSS chunk 12 failed. (/static/css/12.d7d6fc65.chunk.css)

@CanIGetaPR thanks for the report, does it still happens if you refresh the page?

Oddly it loads when I try Opera with VPN on. I have tried doing a full refresh ignoring cache yes.

Updated the original post with additional information.


How to make Swipper Component not pushes content up when keyboard is shown ?

Which OS ?
OSX - High Sierra
Version
Which versions are you using:

react-native-swiper v1.5.13
react-native v0.50.3
platform: Android, IOS working fine

Expected behaviour
My custom button avoid view should be right on top of the keyboard

That was my Login screen it has no problem at all because of no Swipper Component. Problem occur at SignUp screen, but without my custom avoid view, the button will automatically align right on top of keyboard, so my guess it is the Swipper's work. I put my custom avoid view here because on IOS, the button will be hidden away by keyboard.
Actual behaviour
My custom avoid view button was on twice height of where it should be, which is right on top of the keyboard

That was signup screen
How to reproduce it
When I wrapper my button with my custom avoid view button instead of normal View component.
code:
<View>

    <Swipper>
        ...
    </Swipper>

    // this custom avoid view just simple event to detect keyboard hide/show, and use animation to align keyboard
    <MyCustomAvoidView>
        button...
    </MyCustomAvoidView>

</View>

Just use  instead of  for the pages you want to avoid pushing content.

Which OS ?
OSX - High Sierra
Version
Which versions are you using:

react-native-swiper v1.5.13
react-native v0.50.3
platform: Android, IOS working fine

Expected behaviour
My custom button avoid view should be right on top of the keyboard

That was my Login screen it has no problem at all because of no Swipper Component. Problem occur at SignUp screen, but without my custom avoid view, the button will automatically align right on top of keyboard, so my guess it is the Swipper's work. I put my custom avoid view here because on IOS, the button will be hidden away by keyboard.
Actual behaviour
My custom avoid view button was on twice height of where it should be, which is right on top of the keyboard

That was signup screen
How to reproduce it
When I wrapper my button with my custom avoid view button instead of normal View component.
code:
<View>

    <Swipper>
        ...
    </Swipper>

    // this custom avoid view just simple event to detect keyboard hide/show, and use animation to align keyboard
    <MyCustomAvoidView>
        button...
    </MyCustomAvoidView>

</View>

You can use this method:
Keyboard.addListener('keyboardDidShow', () => {
this.setState({ showsPagination: false })
})
Keyboard.addListener('keyboardDidHide', () => {
this.setState({ showsPagination: true })
})


TypeError: list indices must be integers or slices, not tuple when printing the user information table when running as a shell executable on Mac and on Windows when creating a new user

After submitting the information needed to create a new user, KMLogger tries to display the information as a PrettyTable. The same is also true when displaying a returning user's saved information. When running locally this seems to work without issue. However, when running as a standalone shell executable or on Windows this functionality results in:
Traceback (most recent call last):
 File "tui.py", line 164, in <module>
 File "tui.py", line 135, in run
 File "base/user_ops/yml_ops.py", line 111, in create_user
 File "base/user_ops/yml_ops.py", line 65, in tuple_to_dict
TypeError: list indices must be integers or slices, not tuple

No longer relevant


Refactor Grandpa Test IBC Transfer to use suite.Transfer

Summary
ref: #4959
Refactor the cli usage of ibc transfers in TestMsgTransfer_Succeeds_GrandpaContract to use suite.Transfer(...)

For Admin Use

[X] Not duplicate issue
[X] Appropriate labels applied
[ ] Appropriate contributors tagged/assigned

Same reasoning.


Add importer issue that estimates the number of broken species URLs

Sometimes data providers are providing broken species URLs and if that happens a lot it might hurt CoL+'s page rank. Crawling every link each time a dataset is imported is probably impractical (and might DoS the provider) but it might be useful to check a random sample of URLs and report back a metric on estimated number of broken URLs.

We should also routinely check GSD hostnames to make sure they are up, and crawl a random sample of their species URLs. If their site is down for an extended period of time, we should temporarily disable their URLs in the CoL+ public interface. Broken links were a major problem in the 2019 annual edition and probably are reducing CoL's visibility via reduced search engine page rank.
Another possibility would be automatically linking to archive.org if the their page has been crawled. The Wayback Machine has a JSON API and it's pretty easy to determine if a page has been crawled or not.


Legion: Application-driven inline task launches

Currently a mapper can request that a task is executed inline. However, there may be situations where an application might want to request inline task launch (and therefore not leaving it up to a mapper decision). For example, if you wanted to execute an inline task launch inside of a leaf task, one would not want to leave it up to the mapper as to whether or not to execute the task inline.
This would presumably require modifying either the task registration or launcher to request inline execution. I don't think I have a preference, but it probably makes more sense in the launcher.

I should add: this is one possible way to implement https://github.com/StanfordLegion/legion/issues/1073.

How is this difference than "local function" tasks?
https://gitlab.com/StanfordLegion/legion/-/blob/master/runtime/legion.h#L1497-1505

The main difference is that I need to be able to include region requirements. However, my expectation is that all of the regions will already be mapped, and so the region requirements are "trivial" in the sense that they will always be a strict subset of the parent's existing region requirements and any existing instances of those regions are assumed to be sufficient.

What is the value add for the runtime being able to do this? It seems like if you're writing in C++ you should just be able to manually inline it. In the case of a compiler like Regent, it will be much more efficient for the compiler to inline it. You're just asking for runtime overhead by asking the runtime to inline a task without getting anything back in return. I'm just not seeing the value-add.

Regent's current task calling convention relies on certain runtime data structures that I cannot manufacture on my own. E.g., the Task object (that contains the task arguments). In implementing #1073 I need to either implement an entirely new calling convention (that was the original plan) or else figure out how to leverage Legion to help me fit the original one.
In principle there's no reason that the compiler can't do this, aside from time and effort to write and maintain two separate code paths in the compiler.

It's not very difficult to add to this to the runtime, but it just feels like an anti-feature. We definitely wouldn't recommend for anyone to use this in general. It's not really offering you anything.

Another direction I could go would be to modify the Task object myself. The inline call itself is not the hard part, the hard part is setting up all the arguments so that they're "similar enough" to what Regent is expecting to trick it into doing the right thing.
I see most Task fields are public, so as far as that goes, it's not an issue.
One issue is that there are no public Task constructors or copy constructors as far as I can tell. Maybe that's fine, but it would mean I'd need to reuse the parent task's Task object instead of creating a fresh one (or copy). I can make this work by saving the old values are restoring them (a bit like saving registers...) but it does seem a bit conceptually unclean.
What do you think? Would public constructors for Task open up too many opportunities for abuse?

Another direction I could go would be to modify the Task object myself.

You can't modify the Task object you get from the runtime. It is actually a const Task* and points to a data structure that the runtime owns. Casting away the const and modifying the data structure yourself is unsafe and will likely break things.

One issue is that there are no public Task constructors or copy constructors as far as I can tell. Maybe that's fine, but it would mean I'd need to reuse the parent task's Task object instead of creating a fresh one (or copy).

I don't think I would mind making the constructors of derived Mappable types public, especially so users can make their own copies or derived types if they want. Note that the Task does inherit from Mappable and there are a few virtual methods you would need to provide implementations to, but I think that is doable.

If you don't mind adding this, it seems like the fastest way to implement what I want for #1073.

All Mappable type default constructors are now public:
https://gitlab.com/StanfordLegion/legion/-/commit/7ddd8467a727f35ff37308b1463163d42d5f1988

Thanks, this resolves my need.


Proposal: Implement savedb subcommand

I propose the creation of a subcommand that uses a SQLite database to create/manage backups of save files.
It will have the following subcommands:

jhmod savedb watch will watch a specified directory for the existence/creation of save files (using inotify or similar). Upon the detection of a save file by filename, it will read the file into memory, parse it to verify it is a valid save file (depends on #16), and store the save file directly in the database (as a BLOB). It may compress the save file before storing it in the database; we'll need to experiment with various compression methods to see if the time cost + space savings would justify it. Columns in this table can be the original save file name, the player name, the current level, and the game type--these are all good identifiers and what we're able to parse already
jhmod savedb list will list the save files that are currently stored in the database
jhmod savedb restore will restore a save file from the database to the Jupiter Hell game directory
jhmod savedb delete will delete a save file from the database

The gui branch offers a PoC:

jhmod scum list
jhmod scum restore ID
jhmod manager runs a gui that does the watching... needs more work

Thinking I might cherry pick those commits into a different branch then clean up.


Improve Spanish translation

Description

Improve Spanish translation:

Pone coma después de «por favor». El complemento oracional «por favor» debe ir seguido de una coma.
Añade signos de interrogación de apertura donde he encontrado sin cerrar.
Correcciones menores.
«Está seguro que» es un queísmo. Lo he corregido.
Pone tilde a «esta» cuando se usa como verbo.
Pone tilde a «mio».

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[x] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

GitHub Issue/PRs

Fixes #2569
But I didn't review it throughly enough, so maybe there are more small little errors.
Screenshots (if appropriate):
How Has This Been Tested?

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
Testing
[ ] I have added tests to cover my changes.
[ ] All relevant new and existing integration tests have passed.
[ ] A full integration testsuite with all test that can run on my environment has passed.

We will need Spanish speakers to help us review this one :)

@milamberspace can you please advise if this is the proper way to go?

you please translate the PR description in Spanish to English?

I would have to link to every grammar rule I quoted and there are no equivalence for some in English (like queísmo, complemento oracional, diacritic), and only Spanish-speakers should review it anyway, so I don't think it's necessary.

Please note : We use Transifex for the translation of Web UI. You need bring your changes on Transifex otherwise they will be erased on next update (when we download the messages files from transifex to the repo)
https://www.transifex.com/ke4qqq/CloudStack_UI/410_messagesjson/

I opened a pull request because I was told to do that (see https://github.com/apache/cloudstack/issues/2569). I won't use Transifex as it requires proprietary JavaScript code to be executed. I hope someone can volunteer to upload the updates for me or (better yet) use a free replacement to Transifex.

@milamberspace how does transifex work? I mean, if I create a new key, does it pick that key automatically?
Do we have a documentation that talks about the process of generating new message keys?

@rafaelweingartner The process is describe here ./tools/transifex/README-transifex.txt
and on (to update the resources)
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Update+L10N+files+from+Transifex+to+git+repo

@milamberspace thanks!
The page in our wiki is outdated, but the README file is updated :)
I will send the new keys to transifex, and then I will also update the translations suggested here as well.


[DS] Model iterators

We need a way to transform model (repository,reference,commit,blob) -> Iterator[Row]
It should be an abstract class with all the generic code for all the models, and specific code to generate rows per each model.
This iterator should be able to process more than one repository in a lazy way.

Assign to @ajnavarro

RepositoryIterator: https://github.com/src-d/spark-api/pull/20
ReferenceIterator: https://github.com/src-d/spark-api/pull/20
CommitIterator: Pending
BlobIterator: Pending. Mandatory have filtering logic implemented

CommitIterator #21
BlobIterator #25


Can we use "and" when we add the tags in testNG files? For BDD2 or for Gherkin based approach

QAF Version - 3.0.0

Note: only the latest version is supported

Steps To Reproduce - NA (This is a question)
Expected behavior
The user wants to include two combinations of the tags, for example, the user wants to mention that @tag1 and  @tag2, scenarios that have both of these tags should be picked up for execution. Is this possible to filter out using this condition?
Actual behavior -NA

Refer meta-data filter documentation.
It is recommended to post questions with details (your current configuration, relevant code, execution logs, etc) in users group or in stack-overflow with qaf tag.

Sure, will do that going forward, thanks a lot @cjayswal. Appreciate your quick response.


s.type is not a constructor

i don't know what i should do

if this still occurs, please open the console (ctrl+shift+i, switch to the console tab if not selected), click the error message and screenshot the message that appears in the console

The best issue ever

is this fixed? getting same issue

It is not fixed since I don't know how to reproduce this and thus can't really fix it

I have an idea, can you please tell me if this problem still exist so I can check if that actually is the problem (when I update it later)


Compile JS using closure compiler

In the build process, instead of copying the sources, run the closure compiler first before serving individual JS files.

This version of colaboratory is no longer supported, please switch to https://colab.research.google.com.


Simplex Domain Bug

Describe the bug
The sample() method for SimplexDomain class does not work.
To Reproduce
Run 1:
domain = SimplexDomain(
        [
            LabelTensor(torch.tensor([[0., 0]]), labels=["x", "y"]),
            LabelTensor(torch.tensor([[1, 1]]), labels=["x", "y"]),
            LabelTensor(torch.tensor([[1.5, 0.5]]), labels=["x", "y"]),
        ], sample_surface=True
    )

pts = domain.sample(n=1000)

Run 2:
domain = SimplexDomain(
        [
            LabelTensor(torch.tensor([[0., 0]]), labels=["x", "y"]),
            LabelTensor(torch.tensor([[1, 1]]), labels=["x", "y"]),
            LabelTensor(torch.tensor([[1.5, 0.5]]), labels=["x", "y"]),
        ], sample_surface=False
    )

pts = domain.sample(n=1000)

Expected behavior
Run1:
pts a LabelTensor of size [1000, 2] with points sampled on the boundaries.
Run 2:
pts a LabelTensor of size [1000, 2] with points sampled on the interior.
Output
Run1:
AttributeError: 'LabelTensor' object has no attribute 'index'
Run 2:
TypeError: len() of a 0-d tensor
Additional context
I have also noticed that there are no tests for the sample() method in tests/test_geometry/test_simplex.py

Solved, closing the issue.


[Bug]: Failed compilation on stable rustc 1.70.0

What happened?
Installing shuttle on the most recent version of stable Rust (1.70.0) fails. I've attached a copy of the logs alongside this issue.
Version
v0.17.0
Which operating system(s) are you seeing the problem on?
macOS
Which CPU architectures are you seeing the problem on?
ARM64
Relevant log output
error[E0308]: mismatched types
  --> /Users/toks/.cargo/registry/src/index.crates.io-6f17d22bba15001f/shuttle-common-0.17.0/src/models/error.rs:27:43
   |
27 |             self.message.to_string().with(Color::Red)
   |                                      ---- ^^^^^^^^^^ expected `crossterm::style::Color`, found `comfy_table::Color`
   |                                      |
   |                                      arguments to this method are incorrect
   |
   = note: `comfy_table::Color` and `crossterm::style::Color` have similar names, but are actually distinct types
note: `comfy_table::Color` is defined in crate `crossterm`
  --> /Users/toks/.cargo/registry/src/index.crates.io-6f17d22bba15001f/crossterm-0.26.1/src/style/types/color.rs:28:1
   |
28 | pub enum Color {
   | ^^^^^^^^^^^^^^
note: `crossterm::style::Color` is defined in crate `crossterm`
  --> /Users/toks/.cargo/registry/src/index.crates.io-6f17d22bba15001f/crossterm-0.25.0/src/style/types/color.rs:28:1
   |
28 | pub enum Color {
   | ^^^^^^^^^^^^^^
   = note: perhaps two different versions of crate `crossterm` are being used?
note: method defined here
  --> /Users/toks/.cargo/registry/src/index.crates.io-6f17d22bba15001f/crossterm-0.25.0/src/style/stylize.rs:78:8
   |
78 |     fn with(self, color: Color) -> Self::Styled {
   |        ^^^^

error[E0308]: mismatched types
  --> /Users/toks/.cargo/registry/src/index.crates.io-6f17d22bba15001f/shuttle-common-0.17.0/src/models/service.rs:45:27
   |
45 |                     .with(deployment.state.get_color()),
   |                      ---- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected `crossterm::style::Color`, found `comfy_table::Color`
   |                      |
   |                      arguments to this method are incorrect
   |
   = note: `comfy_table::Color` and `crossterm::style::Color` have similar names, but are actually distinct types
note: `comfy_table::Color` is defined in crate `crossterm`
  --> /Users/toks/.cargo/registry/src/index.crates.io-6f17d22bba15001f/crossterm-0.26.1/src/style/types/color.rs:28:1
   |
28 | pub enum Color {
   | ^^^^^^^^^^^^^^
note: `crossterm::style::Color` is defined in crate `crossterm`
  --> /Users/toks/.cargo/registry/src/index.crates.io-6f17d22bba15001f/crossterm-0.25.0/src/style/types/color.rs:28:1
   |
28 | pub enum Color {
   | ^^^^^^^^^^^^^^
   = note: perhaps two different versions of crate `crossterm` are being used?
note: method defined here
  --> /Users/toks/.cargo/registry/src/index.crates.io-6f17d22bba15001f/crossterm-0.25.0/src/style/stylize.rs:78:8
   |
78 |     fn with(self, color: Color) -> Self::Styled {
   |        ^^^^

For more information about this error, try `rustc --explain E0308`.

Duplicate declaration

[X] I have searched the issues and there are none like this.

The new release is out now, but maybe we should consider adding --locked to the install instructions in the README.

Adding the --locked hint in #989


FIX: Names were blank on the leaderboard when the user does not have full name

When users did not have their full names, the leaderboard did not put any name for the users:

I fixed this to show usernames when users' full names are not available:

Thanks!


Allow different typeface weights in font selection window.

When selecting different fonts to use, there's no option to select the weight (e.g., Regular, Bold, etc.)

I've stumbled upon this issue recently, too.


 Make a script to remote-start and connect to a padre in one go:

ssh into host, cd into dir, start radiopadre

parse output of above to determine the port it has selected

open a second ssh connection with that port forwarded

open local browser on localhost:port

Fixed in https://github.com/o-smirnov/padre/commit/1cd51b3951ac5ecb82ae1d4d923e8a2d801c2d57


elliptic/package.json Module parse failed while using ethereumjs-abi with babel/es6

In es6/babel/webpack:
import abi from 'ethereumjs-abi'

./~/elliptic/package.json
Module parse failed: /home/nick/github/cosmo/node_modules/elliptic/package.json Line 2: Unexpected token :
You may need an appropriate loader to handle this file type.
| {
|   "_args": [
|     [
|       "elliptic",
 @ ./~/elliptic/lib/elliptic.js 5:19-45onSocketMsg.errors @ client:47sock.onmessage @ client:82EventTarget.dispatchEvent @ eventtarget.js:49(anonymous function) @ main.js:274SockJS._transportMessage @ main.js:272EventEmitter.emit @ emitter.js:44WebSocketTransport.ws.onmessage @ websocket.js:35

Just reporting this problem here. Looking like a problem with es6/elliptic/babel/webpack. Try using ethereumjs-abi with this webpack/es6/react boilerplate: https://github.com/gaearon/react-hot-boilerplate to recreate the error.
However, when I install just the elliptic package, it seems to build fine in webpack.
Any thoughts on how to proceed? @axic

Strange, I have no idea.  I have used it with react + grunt + babel, but no es6 syntax.

@axic
import * as util from 'ethereumjs-util'

./~/secp256k1/lib/messages.json
Module parse failed: /home/nick/github/cosmo/node_modules/secp256k1/lib/messages.json Line 2: Unexpected token :
You may need an appropriate loader to handle this file type.
| {
|   "COMPRESSED_TYPE_INVALID": "compressed should be a boolean",
|   "EC_PRIVATE_KEY_TYPE_INVALID": "private key should be a Buffer",
|   "EC_PRIVATE_KEY_LENGTH_INVALID": "private key length is invalid",
 @ ./~/secp256k1/lib/index.js 4:15-41onSocketMsg.errors @ client:47sock.onmessage @ client:82EventTarget.dispatchEvent @ eventtarget.js:49(anonymous function) @ main.js:274SockJS._transportMessage @ main.js:272EventEmitter.emit @ emitter.js:44WebSocketTransport.ws.onmessage @ websocket.js:35
client:47 ./~/elliptic/package.json
Module parse failed: /home/nick/github/cosmo/node_modules/elliptic/package.json Line 2: Unexpected token :
You may need an appropriate loader to handle this file type.
| {
|   "_args": [
|     [
|       "elliptic",
 @ ./~/elliptic/lib/elliptic.js 5:19-45```

Found the problem, it's to do with webpack.
For all those who ran into this, install a JSON loader... lol. Webpack... Ugh..
require("json-loader")
... { test: /\.json$/, loader: "json-loader" },


Dealing with multiple-inverse associations

Consider the following data model:
Location = DS.Model.extend
  name: DS.attr 'string'
  currentFloorplan: DS.belongsTo 'floorplan', async: true
  upcomingFloorplans: DS.hasMany 'floorplan', async: true

Floorplan = DS.Model.extend
  name: DS.attr 'string'
  location: DS.belongsTo 'location', async: true, inverse: null

A Floorplan always belongs to a Location, but the inverse association could be one of two different options, so we set it to null because Ember only allows a single inverse. Unfortunately there's no clean way to deal with this situation in Factory Guy, so we end up doing this Em.run workaround in every test that involves floorplans:
describe 'An association with multiple possible inverses', ->
  it 'requires a clunky workaround', ->
    location = factories.make 'location'
    floorplan = factories.make 'floorplan', location: location
    Em.run -> location.get('upcomingFloorplans').addObject(floorplan)

    expect(location.get('upcomingFloorplans.length')).to.equal 1

In Factory Girl, this kind of thing is usually handled with callbacks that access transient attributes to execute some custom behavior. It would of course be a substantial effort to add these features to Factory Guy, so maybe there is an easier targeted solution.

@grantovich , how could you see this working in FactoryGuy?  Could you give me an idea of what you would like to see ( even if its just a copy of what FactoryGirl does )  .. will help to get my ideas going.

@grantovich .. I just looked over the callbacks in FactoryGirl, and I understand what you want .. I just want to make double extra sure that I have it 100% exactly correct ( the way you want it ) before I build this.

If you're looking to implement the whole transients/callbacks thing, this is roughly how I'd envision it working in the factory definitions:
FactoryGuy.define 'location',
  default:
    name: 'Test Location'

FactoryGuy.define 'floorplan',
  default:
    location: {}
    name: 'Test Floorplan'

  transient:
    locationInverse: null

  afterMake: (model, attributes) ->
    switch attributes.locationInverse
      when 'currentFloorplan' then model.location.set('currentFloorplan', model)
      when 'upcomingFloorplans' then model.location.get('upcomingFloorplans').addObject(model)

And the usage:
location = factories.make 'location'
floorplan = factories.make 'floorplan', location: location, locationInverse: 'upcomingFloorplans'

The transient key would contain attributes that are ignored when constructing the model itself. The afterMake callback would receive the constructed model instance and the hash of attributes provided to the make call, including any transient attributes.
If implemented as-is, this would not be backwards compatible since transient and afterMake could previously be used as trait names. Since this problem would keep showing up if you added more "special" keys, it might be worthwhile to put traits under their own sub-key to ensure there are no collisions.
FactoryGuy.define 'user',
  default:
    username: 'bob'
    isModerator: false
    isAdmin: false

  traits:
    admin:
      isAdmin: true
    moderator:
      isModerator: true

This would be super-not-backwards-compatible, but you could leave in the ability to define traits at the top level and just give a deprecation warning.

(By the way, I and my team really appreciate your work on this project – I was only asking for advice on how to handle our particular situation, but you've gone far above and beyond. :clap: We are on a rather time-crunched project right now, but I hope to make some contributions to Factory Guy myself once I have enough Ember experience.)

Thanks for the proposed usage Alex, that was helpful, and thanks for the kind words :)
This library has made testing ember app's so much easier and fun for me, and I am happy to hear that others like yourselves are enjoying it too.
And good point about the collisions .. luckily traits already have their own sub_key already,
so that should not be too bad.

Thanks for the proposed usage Alex, that was helpful, and thanks for the kind words :)
This library has made testing ember app's so much easier and fun for me, and I am happy to hear that others like yourselves are enjoying it too.
And good point about the collisions .. luckily traits already have their own sub_key already,
so that should not be too bad.

Thanks for the proposed usage Alex, that was helpful, and thanks for the kind words :)
This library has made testing ember app's so much easier and fun for me, and I am happy to hear that others like yourselves are enjoying it too.
And good point about the collisions .. luckily traits already have their own sub_key already,
so that should not be too bad.

Thanks for the proposed usage Alex, that was helpful, and thanks for the kind words :)
This library has made testing ember app's so much easier and fun for me, and I am happy to hear that others like yourselves are enjoying it too.
And good point about the collisions .. luckily traits already have their own sub_key already,
so that should not be too bad.

luckily traits already have their own sub_key already, so that should not be too bad.

Ah, okay. I was looking at a section of the README that just used top-level keys for the traits.

Hey @grantovich , I finally got around to finishing this feature. Check it out in version 1.0.5, and let me know if you see any bugs?

Awesome! Thanks so much for adding this, I'll try it out and report any issues I find.

Actually I was not quite finished when I pushed out version 1.0.4 .. I am finishing it up today, and will release new version 1.0.5 when I am done.

ok .. I fixed that issue, and its on version 1.0.6 where afterMake will work as you expected.


Cannot retrieve API key

Describe the issue
When I try to unhide tha API key on https://pirate-weather.apiable.io/subscriptions/{my_subscribcion}/Details, there is visible "Retrieving..." info in API key field, then after a while there is visible random text like: "The first website was published in 1991.". When I try to regenerate API key it behave the same, after a while I see a random text.
I also create a new account and when I try to get new subscribtion there is visible an error:
{     "timestamp": "2024-08-22T08:23:46.242+00:00",     "status": 500,     "error": "Internal Server Error",     "message": "Failed to parse HTTP response: unexpected EOF",     "path": "/api/int/subscriptions" }
Acknowledgements

[X] I have searched this repository and Home Assistant Repository to see if the issue has already been reported.
[X] I have read through the API documentation before opening this issue.
[X] I have written an informative title.

Really sorry for this! Bug in a config file took down both production backends. It's fixed now, so should be working again


lint: fix linting

Title says it all
please review @sdobbert

Looks good to me, thank you @FritzHoing


Cannot use warm startup of an estimator with MirroredStrategy

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 16.04
TensorFlow installed from (source or binary):  using nvidia containter: https://docs.nvidia.com/deeplearning/dgx/tensorflow-release-notes/rel_18.06.html#rel_18.06
TensorFlow version (use command below): 1.8.0
Python version: 3.5
Bazel version (if compiling from source): N/A
GCC/Compiler version (if compiling from source):N/A
CUDA/cuDNN version: 9.0.176
GPU model and memory: nvidia tesla v100
Exact command to reproduce:N/A

Describe the problem
I'm training an network using tf.estimator where I load a set of variables from an existing checkpoint. This is done using the warm start-up option from the estimator class. While the code works when running on a single GPU, It generates an error when I use the MirroredStrategy.
Source code / logs
The code:
ws = tf.estimator.WarmStartSettings(ckpt_to_initialize_from="init_checkpoint.ckpt"),
                                                vars_to_warm_start="^((?!Logits).)*$"
                                                )
self.trainer = tf.estimator.Estimator(
            model_fn=self.get_model_fn,  # First-class function
            params=None,  # HParams are passed using the config file
            config=run_config,
            warm_start_from=ws
        )

This generate the following trace:
Traceback (most recent call last):
  File "train.py", line 37, in <module>
    experimenter.run_training_experiment(config)
  File "/media/local/BDA_tf_framework/neuralnetwork/trainingexperimenter.py", line 39, in run_training_experiment
    tf.estimator.train_and_evaluate(self.trainer, self.training_specs, self.eval_specs)
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/estimator/training.py", line 439, in train_and_evaluate
    executor.run()
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/estimator/training.py", line 518, in run
    self.run_local()
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/estimator/training.py", line 650, in run_local
    hooks=train_hooks)
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/estimator/estimator.py", line 363, in train
    loss = self._train_model(input_fn, hooks, saving_listeners)
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/estimator/estimator.py", line 841, in _train_model
    return self._train_model_distributed(input_fn, hooks, saving_listeners)
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/estimator/estimator.py", line 977, in _train_model_distributed
    saving_listeners)
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/estimator/estimator.py", line 986, in _train_with_estimator_spec
    warm_starting_util.warm_start(*self._warm_start_settings)
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/training/warm_starting_util.py", line 342, in warm_start
    _warm_start_var(variable, ckpt_to_initialize_from, prev_var_name)
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/training/warm_starting_util.py", line 139, in _warm_start_var
    "PartitionedVariable, but is {}".format(type(var)))
TypeError: var MUST be one of the following: a Variable, list of Variable or PartitionedVariable, but is <class 'tensorflow.contrib.distribute.python.values.MirroredVariable'>
Makefile:19: recipe for target 'train_gpu' failed
make: *** [train_gpu] Error 1

The fix has been merged: https://github.com/tensorflow/tensorflow/commit/f1de0ddd55dcae6237ea7d21ccddcc6467a6cf8b
You should be able to test this out in a nightly build soon.


Migrate documentation notebooks

The four notebooks added in this PR were previously directly a part of the Planetary Computer Data Catalog site. In order for them to take advantage of the dev environment contained within this repo, and to allow them to be syned to the PC Hub, all docs notebooks are getting migrated here.
To facilitate a better dev experience, a small webserver container has been added to this project. When ./scripts/server is run, a localhost instance is started which can act as the external resource to the docs site build process, when that project is being developed. Additional instructions will be included in separate PR in that repository.
Note: merging this PR is a prerequisite for the associated docs site PR, as these materials need to exist for the CI process to build and pass.

@lossyrob @TomAugspurger fyi on this change. Will also tag you on the related PR in the catalog app.


Colab precision

In Colab, hyperparameter values show only two digits after the decimal which is not enough for things like tol or learning rates. Is there a way to change this?

Hi @rxjx , that makes sense. I increased the number of decimals to 5. I plan on adding a parameter for this in the profiler call in the future, but this should fix it for now. Can you try it out using pipelineprofiler 0.1.16 ?
Closing this issue.

Hi @rxjx , that makes sense. I increased the number of decimals to 5. I plan on adding a parameter for this in the profiler call in the future, but this should fix it for now. Can you try it out using pipelineprofiler 0.1.16 ?
Closing this issue.

Thanks, I'll take a look next week. I was going to suggest using the 'g' format for float parms.

Thanks, I'll take a look next week. I was going to suggest using the 'g' format for float parms.

Definitely improved. But some parms are still zero so the 'g' format would help. Here's an example:


French translation of Advanced Algorithm Scripting

[ ] Validate US Telephone Numbers
[ ] Symmetric Difference
[ ] Exact Change
[ ] Inventory Update
[ ] No repeats please
[ ] Friendly Date Ranges
[ ] Make a Person
[ ] Map the Debris
[ ] Pairwise

Issue moved to FreeCodeCamp/TranslationExpansion #70 via ZenHub


Deal with Bash unset's -v and -f flag.

Unset in bash is able to alternate between unsetting functions and variables, using the -f and -v flags, respectively.
This fixes a problem where babelfish would translate unset -f foo to set -e -f; set -e foo. The correct translation would be functions -e foo.

I also need this fix, merge plz


Passing the provided dt doesn't match the default dt

When you pass the delta t in the update function of a Sprite, it causes the sprite to move at 1/60th the speed of a Sprite without a specific delta t. See the following code.
import {
    init, initKeys, keyPressed, Sprite, GameLoop
} from 'kontra'
import './style.scss'

const { canvas, context } = init()

let sprites = []

const sprite = Sprite({
    x: 100,
    y: 80,
    color: 'red',
    width: 20,
    height: 40,
    dx: 1,
    update(dt) {
        this.advance()
        if (this.x > this.context.canvas.width) {
            this.x = -this.width
        }
    }
})

sprites.push(sprite)

const sprite2 = Sprite({
    x: 100,
    y: 160,
    color: 'yellow',
    width: 20,
    height: 40,
    dx: 1,
    update(dt) {
        this.advance(dt)
        if (this.x > this.context.canvas.width) {
            this.x = -this.width
        }
    }
})

sprites.push(sprite2)

const loop = GameLoop({ // create the main game loop
    update(dt) { // update the game state
        sprites.forEach((sprite) => sprite.update(dt))
        sprites = sprites.filter((s) => s.isAlive())
    },
    render() { // render the game state
        sprites.forEach((sprite) => sprite.render())
    }
})

initKeys()
loop.start() // start the game

According to the docs, the optional dt parameter in the advance function is the same parameter in the update function, Time since last update..
This has been the case for basically all of kontra's development, and it never felt right to me. I would expect the number being passed into the update function to be the right one to continue sending through to the advance function.

The dt is used if you want to use time based movement, so you'll need to use dx and dy values that represent how far to move in 1 second rather than how far to move in 1 frame. In this case, sprite2 should have a dt value of 60 rather than 1.

So the two lines of thought are delta x per frame, and delta x per second, and they're only determined by the advance function's parameter is called?
Hmm, does that mean the documentation for Sprite.advance([dt]) needs to be updated? What the advance function receives is being multiplied, so would that be the n frames rather than delta t?

It could probably use a bit more clarification. The advance function takes the dt value and uses it as a scalar multiplier for the vector addition.


[DO NOT MERGE] rooms changes for beta4 to create the apiview

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

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.Communication.CallAutomation


Update v2alpha1 APIRule rule path validation

Description
This PR introduces restrictions to using * in APIRule path.
Instead of allowing /.* the path will only allows /* if a rule should apply to all paths.
In the ADR it's also mentioned that a configuration of * Should be warning user that it is not recommended, as it applies to all paths. This will not be handled in this PR, but should be handled once there is support for APIRule v2alpha1 in the UI.
Changes proposed in this pull request:

Update allowed wildcard from * to /* in the ADR and documentation
Update v2alpha1 APIRule rule path validation to allow * in the format of /*.
Simplify code for v2alpha1 authorization policy creation, because * is supported in the path.
Update integration tests to use /* instead of /.*
Remove unnecessary integration test

Pre-Merge Checklist

[ ] As a PR reviewer, verify code coverage and evaluate if it is acceptable.

Related issues

https://github.com/kyma-project/api-gateway/issues/1282

Technical side looks good.
Should (or did we already) document that customers need to switch their /.* paths to /* as part of migration?

Good point, I'll check how we want to communicate this.


[Task]: Is there any plan to add Unsupervised Continual Anomaly Detection with Contrastively-learned Prompt?

What is the motivation for this task?
1.The current anomaly detection can only train one model for one class. What if only one model is trained for multiple classes?
2.How to add continuous learning to anomaly detection model training?
Describe the solution you'd like
I saw a paper like Unsupervised Continual Anomaly Detection with Contrastively-learned Prompt in AAAI-2024 [paper link] [code link] , it's a great idea to work with, and it might be even better to add it to anomalib.
Additional context
No response

This looks like an interesting approach. I'll add it to the feature request section with Good First Issue label in case someone  wants to work on it.
Thanks for sharing it!


Add example to MinIO ILM Transition for identifying object status

User request: Would be nice to check if an object is transitioned, and to what remote tier.
Checking object storage class + metadata should be sufficient here. Test the procedure and provide an example for all three tutorials.

mc ls already does this.
See https://min.io/docs/minio/linux/reference/minio-mc/mc-ls.html.


thickPolyline acts like thickPolygon

Introduced in a recent pull request.  Rolling out the fix now.

@kammitama5 FYI


Allow the project to be compiled with Java 11

I've switched from Java 8 a while back and it appears I'm not able to build the project with Java 11. I've tried both Oracle and AdaptOpenJDK.
It seems the issue is with the Maven Surefire plugin. It's not explicitly added as a dependency to the pom.xml but version 2.20.1 is used and it crashes for the reasons outlined in https://issues.apache.org/jira/browse/SUREFIRE-1440, due to a dependency on Apache Commons Lang (https://issues.apache.org/jira/browse/LANG-1365)
The project should be possible to build with both Java 8 and 11
Be sure to update https://github.com/Cognifide/AEM-Rules-for-SonarQube/blob/master/.travis.yml

Resolved by #196


fix(deps): update dependency pydantic to v2

This PR contains the following updates:

Package
Type
Update
Change

pydantic (changelog)
dependencies
major
^1.10.9 -> ^2.0.0

Release Notes

pydantic/pydantic (pydantic)
v2.3.0
Compare Source
GitHub release

🔥 Remove orphaned changes file from repo by @lig in #7168
Add copy button on documentation by @Kludex in #7190
Fix docs on JSON type by @Kludex in #7189
Update mypy 1.5.0 to 1.5.1 in CI by @hramezani in #7191
fix download links badge by @samuelcolvin in #7200
add 2.2.1 to changelog by @samuelcolvin in #7212
Make ModelWrapValidator protocols generic by @dmontagu in #7154
Correct Field(..., exclude: bool) docs by @samuelcolvin in #7214
Make shadowing attributes a warning instead of an error by @adriangb in #7193
Document Base64Str and Base64Bytes by @Kludex in #7192
Fix config.defer_build for serialization first cases by @samuelcolvin in #7024
clean Model docstrings in JSON Schema by @samuelcolvin in #7210
fix #7228 (typo): docs in validators.md to correct validate_default kwarg by @lmmx in #7229
✅ Implement tzinfo.fromutc method for TzInfo in pydantic-core by @lig in #7019
Support __get_validators__ by @hramezani in #7197

v2.2.1
Compare Source
GitHub release

Make xfailing test for root model extra stop xfailing by @dmontagu in #6937
Optimize recursion detection by stopping on the second visit for the same object by @mciucu in #7160
fix link in docs by @tlambert03 in #7166
Replace MiMalloc w/ default allocator by @adriangb in pydantic/pydantic-core#900
Bump pydantic-core to 2.6.1 and prepare 2.2.1 release by @adriangb in #7176

v2.2.0
Compare Source
GitHub release

Split "pipx install" setup command into two commands on the documentation site by @nomadmtb in #6869
Deprecate Field.include by @hramezani in #6852
Fix typo in default factory error msg by @hramezani in #6880
Simplify handling of typing.Annotated in GenerateSchema by @dmontagu in #6887
Re-enable fastapi tests in CI by @dmontagu in #6883
Make it harder to hit collisions with json schema defrefs by @dmontagu in #6566
Cleaner error for invalid input to Path fields by @samuelcolvin in #6903
:memo: support Coordinate Type by @yezz123 in #6906
Fix ForwardRef wrapper for py 3.10.0 (shim until bpo-45166) by @randomir in #6919
Fix misbehavior related to copying of RootModel by @dmontagu in #6918
Fix issue with recursion error caused by ParamSpec by @dmontagu in #6923
Add section about Constrained classes to the Migration Guide by @Kludex in #6924
Use main branch for badge links by @Viicos in #6925
Add test for v1/v2 Annotated discrepancy by @carlbordum in #6926
Make the v1 mypy plugin work with both v1 and v2 by @dmontagu in #6921
Fix issue where generic models couldn't be parametrized with BaseModel by @dmontagu in #6933
Remove xfail for discriminated union with alias by @dmontagu in #6938
add field_serializer to computed_field by @andresliszt in #6965
Use union_schema with Type[Union[...]] by @JeanArhancet in #6952
Fix inherited typeddict attributes / config by @adriangb in #6981
fix dataclass annotated before validator called twice by @davidhewitt in #6998
Update test-fastapi deselected tests by @hramezani in #7014
Fix validator doc format by @hramezani in #7015
Fix typo in docstring of model_json_schema by @AdamVinch-Federated in #7032
remove unused "type ignores" with pyright by @samuelcolvin in #7026
Add benchmark representing FastAPI startup time by @adriangb in #7030
Fix json_encoders for Enum subclasses by @adriangb in #7029
Update docstring of ser_json_bytes regarding base64 encoding by @Viicos in #7052
Allow @validate_call to work on async methods by @adriangb in #7046
Fix: mypy error with Settings and SettingsConfigDict by @JeanArhancet in #7002
Fix some typos (repeated words and it's/its) by @eumiro in #7063
Fix the typo in docstring by @harunyasar in #7062
Docs: Fix broken URL in the pydantic-settings package recommendation by @swetjen in #6995
Handle constraints being applied to schemas that don't accept it by @adriangb in #6951
Replace almost_equal_floats with math.isclose by @eumiro in #7082
bump pydantic-core to 2.5.0 by @davidhewitt in #7077
Add short_version and use it in links by @hramezani in #7115
📝 Add usage link to RootModel by @Kludex in #7113
Revert "Fix default port for mongosrv DSNs (#6827)" by @Kludex in #7116
Clarify validate_default and _Unset handling in usage docs and migration guide by @benbenbang in #6950
Tweak documentation of Field.exclude by @Viicos in #7086
Do not require validate_assignment to use Field.frozen by @Viicos in #7103
tweaks to _core_utils by @samuelcolvin in #7040
Make DefaultDict working with set by @hramezani in #7126
Don't always require typing.Generic as a base for partially parametrized models by @dmontagu in #7119
Fix issue with JSON schema incorrectly using parent class core schema by @dmontagu in #7020
Fix xfailed test related to TypedDict and alias_generator by @dmontagu in #6940
Improve error message for NameEmail by @dmontagu in #6939
Fix generic computed fields by @dmontagu in #6988
Reflect namedtuple default values during validation by @dmontagu in #7144
Update dependencies, fix pydantic-core usage, fix CI issues by @dmontagu in #7150
Add mypy 1.5.0 by @hramezani in #7118
Handle non-json native enum values by @adriangb in #7056
document round_trip in Json type documentation  by @jc-louis in #7137
Relax signature checks to better support builtins and C extension functions as validators by @adriangb in #7101
add union_mode='left_to_right' by @davidhewitt in #7151
Include an error message hint for inherited ordering by @yvalencia91 in #7124
Fix one docs link and resolve some warnings for two others by @dmontagu in #7153
Include Field extra keys name in warning by @hramezani in #7136

v2.1.1
Compare Source
GitHub release

Skip FieldInfo merging when unnecessary by @dmontagu in #6862

v2.1.0
Compare Source
GitHub release

Add StringConstraints for use as Annotated metadata by @adriangb in #6605
Try to fix intermittently failing CI by @adriangb in #6683
Remove redundant example of optional vs default. by @ehiggs-deliverect in #6676
Docs update by @samuelcolvin in #6692
Remove the Validate always section in validator docs by @adriangb in #6679
Fix recursion error in json schema generation by @adriangb in #6720
Fix incorrect subclass check for secretstr by @AlexVndnblcke in #6730
update pdm / pdm lockfile to 2.8.0 by @davidhewitt in #6714
unpin pdm on more CI jobs by @davidhewitt in #6755
improve source locations for auxiliary packages in docs by @davidhewitt in #6749
Assume builtins don't accept an info argument by @adriangb in #6754
Fix bug where calling help(BaseModelSubclass) raises errors by @hramezani in #6758
Fix mypy plugin handling of @model_validator(mode="after") by @ljodal in #6753
update pydantic-core to 2.3.1 by @davidhewitt in #6756
Mypy plugin for settings by @hramezani in #6760
Use contentSchema keyword for JSON schema by @dmontagu in #6715
fast-path checking finite decimals by @davidhewitt in #6769
Docs update by @samuelcolvin in #6771
Improve json schema doc by @hramezani in #6772
Update validator docs by @adriangb in #6695
Fix typehint for wrap validator by @dmontagu in #6788
🐛 Fix validation warning for unions of Literal and other type by @lig in #6628
Update documentation for generics support in V2 by @tpdorsey in #6685
add pydantic-core build info to version_info() by @samuelcolvin in #6785
Fix pydantic dataclasses that use slots with default values by @dmontagu in #6796
Fix inheritance of hash function for frozen models by @dmontagu in #6789
✨ Add SkipJsonSchema annotation by @Kludex in #6653
Error if an invalid field name is used with Field by @dmontagu in #6797
Add GenericModel to MOVED_IN_V2 by @adriangb in #6776
Remove unused code from docs/usage/types/custom.md by @hramezani in #6803
Fix float -> Decimal coercion precision loss by @adriangb in #6810
remove email validation from the north star benchmark by @davidhewitt in #6816
Fix link to mypy by @progsmile in #6824
Improve initialization hooks example by @hramezani in #6822
Fix default port for mongosrv DSNs by @dmontagu in #6827
Improve API documentation, in particular more links between usage and API docs by @samuelcolvin in #6780
update pydantic-core to 2.4.0 by @davidhewitt in #6831
Fix annotated_types.MaxLen validator for custom sequence types by @ImogenBits in #6809
Update V1 by @hramezani in #6833
Make it so callable JSON schema extra works by @dmontagu in #6798
Fix serialization issue with InstanceOf by @dmontagu in #6829
Add back support for json_encoders by @adriangb in #6811
Update field annotations when building the schema by @dmontagu in #6838
Use WeakValueDictionary to fix generic memory leak by @dmontagu in #6681
Add config.defer_build to optionally make model building lazy by @samuelcolvin in #6823
delegate UUID serialization to pydantic-core by @davidhewitt in #6850
Update json_encoders docs by @adriangb in #6848
Fix error message for staticmethod/classmethod order with validate_call by @dmontagu in #6686
Improve documentation for Config by @samuelcolvin in #6847
Update serialization doc to mention Field.exclude takes priority over call-time include/exclude by @hramezani in #6851
Allow customizing core schema generation by making GenerateSchema public by @adriangb in #6737

v2.0.3
Compare Source
GitHub release

Mention PyObject (v1) moving to ImportString (v2) in migration doc by @slafs in #6456
Fix release-tweet CI by @Kludex in #6461
Revise the section on required / optional / nullable fields. by @ybressler in #6468
Warn if a type hint is not in fact a type by @adriangb in #6479
Replace TransformSchema with GetPydanticSchema by @dmontagu in #6484
Fix the un-hashability of various annotation types, for use in caching generic containers by @dmontagu in #6480
PYD-164: Rework custom types docs by @adriangb in #6490
Fix ci by @adriangb in #6507
Fix forward ref in generic by @adriangb in #6511
Fix generation of serialization JSON schemas for core_schema.ChainSchema by @dmontagu in #6515
Document the change in Field.alias behavior in Pydantic V2 by @hramezani in #6508
Give better error message attempting to compute the json schema of a model with undefined fields by @dmontagu in #6519
Document alias_priority by @tpdorsey in #6520
Add redirect for types documentation by @tpdorsey in #6513
Allow updating docs without release by @samuelcolvin in #6551
Ensure docs tests always run in the right folder by @dmontagu in #6487
Defer evaluation of return type hints for serializer functions by @dmontagu in #6516
Disable E501 from Ruff and rely on just Black by @adriangb in #6552
Update JSON Schema documentation for V2 by @tpdorsey in #6492
Add documentation of cyclic reference handling by @dmontagu in #6493
Remove the need for change files by @samuelcolvin in #6556
add "north star" benchmark by @davidhewitt in #6547
Update Dataclasses docs by @tpdorsey in #6470
♻ Use different error message on v1 redirects by @Kludex in #6595
⬆ Upgrade pydantic-core to v2.2.0 by @lig in #6589
Fix serialization for IPvAny by @dmontagu in #6572
Improve CI by using PDM instead of pip to install typing-extensions by @adriangb in #6602
Add enum error type docs  by @lig in #6603
🐛 Fix max_length for unicode strings by @lig in #6559
Add documentation for accessing features via pydantic.v1 by @tpdorsey in #6604
Include extra when iterating over a model by @adriangb in #6562
Fix typing of model_validator by @adriangb in #6514
Touch up Decimal validator by @adriangb in #6327
Fix various docstrings using fixed pytest-examples by @dmontagu in #6607
Handle function validators in a discriminated union by @dmontagu in #6570
Review json_schema.md by @tpdorsey in #6608
Make validate_call work on basemodel methods by @dmontagu in #6569
add test for big int json serde by @davidhewitt in #6614
Fix pydantic dataclass problem with dataclasses.field default_factory by @hramezani in #6616
Fixed mypy type inference for TypeAdapter by @zakstucke in #6617
Make it work to use None as a generic parameter by @dmontagu in #6609
Make it work to use $ref as an alias by @dmontagu in #6568
add note to migration guide about changes to AnyUrl etc by @davidhewitt in #6618
🐛 Support defining json_schema_extra on RootModel using Field by @lig in #6622
Update pre-commit to prevent commits to main branch on accident by @dmontagu in #6636
Fix PDM CI for python 3.7 on MacOS/windows by @dmontagu in #6627
Produce more accurate signatures for pydantic dataclasses by @dmontagu in #6633
Updates to Url types for Pydantic V2 by @tpdorsey in #6638
Fix list markdown in transform docstring by @StefanBRas in #6649
simplify slots_dataclass construction to appease mypy by @davidhewitt in #6639
Update TypedDict schema generation docstring by @adriangb in #6651
Detect and lint-error for prints by @dmontagu in #6655
Add xfailing test for pydantic-core PR 766 by @dmontagu in #6641
Ignore unrecognized fields from dataclasses metadata by @dmontagu in #6634
Make non-existent class getattr a mypy error by @dmontagu in #6658
Update pydantic-core to 2.3.0 by @hramezani in #6648
Use OrderedDict from typing_extensions by @dmontagu in #6664
Fix typehint for JSON schema extra callable by @dmontagu in #6659

v2.0.2
Compare Source
GitHub release

Fix bug where round-trip pickling/unpickling a RootModel would change the value of __dict__, #6457 by @dmontagu
Allow single-item discriminated unions, #6405 by @dmontagu
Fix issue with union parsing of enums, #6440 by @dmontagu
Docs: Fixed constr documentation, renamed old regex to new pattern, #6452 by @miili
Change GenerateJsonSchema.generate_definitions signature, #6436 by @dmontagu

See the full changelog here
v2.0.1
Compare Source
GitHub release
First patch release of Pydantic V2

Extra fields added via setattr (i.e. m.some_extra_field = 'extra_value')
are added to .model_extra if model_config extra='allowed'. Fixed #6333, #6365 by @aaraney
Automatically unpack JSON schema '$ref' for custom types, #6343 by @adriangb
Fix tagged unions multiple processing in submodels, #6340 by @suharnikov

See the full changelog here
v2.0
Compare Source
GitHub release

Split "pipx install" setup command into two commands on the documentation site by @nomadmtb in #6869
Deprecate Field.include by @hramezani in #6852
Fix typo in default factory error msg by @hramezani in #6880
Simplify handling of typing.Annotated in GenerateSchema by @dmontagu in #6887
Re-enable fastapi tests in CI by @dmontagu in #6883
Make it harder to hit collisions with json schema defrefs by @dmontagu in #6566
Cleaner error for invalid input to Path fields by @samuelcolvin in #6903
:memo: support Coordinate Type by @yezz123 in #6906
Fix ForwardRef wrapper for py 3.10.0 (shim until bpo-45166) by @randomir in #6919
Fix misbehavior related to copying of RootModel by @dmontagu in #6918
Fix issue with recursion error caused by ParamSpec by @dmontagu in #6923
Add section about Constrained classes to the Migration Guide by @Kludex in #6924
Use main branch for badge links by @Viicos in #6925
Add test for v1/v2 Annotated discrepancy by @carlbordum in #6926
Make the v1 mypy plugin work with both v1 and v2 by @dmontagu in #6921
Fix issue where generic models couldn't be parametrized with BaseModel by @dmontagu in #6933
Remove xfail for discriminated union with alias by @dmontagu in #6938
add field_serializer to computed_field by @andresliszt in #6965
Use union_schema with Type[Union[...]] by @JeanArhancet in #6952
Fix inherited typeddict attributes / config by @adriangb in #6981
fix dataclass annotated before validator called twice by @davidhewitt in #6998
Update test-fastapi deselected tests by @hramezani in #7014
Fix validator doc format by @hramezani in #7015
Fix typo in docstring of model_json_schema by @AdamVinch-Federated in #7032
remove unused "type ignores" with pyright by @samuelcolvin in #7026
Add benchmark representing FastAPI startup time by @adriangb in #7030
Fix json_encoders for Enum subclasses by @adriangb in #7029
Update docstring of ser_json_bytes regarding base64 encoding by @Viicos in #7052
Allow @validate_call to work on async methods by @adriangb in #7046
Fix: mypy error with Settings and SettingsConfigDict by @JeanArhancet in #7002
Fix some typos (repeated words and it's/its) by @eumiro in #7063
Fix the typo in docstring by @harunyasar in #7062
Docs: Fix broken URL in the pydantic-settings package recommendation by @swetjen in #6995
Handle constraints being applied to schemas that don't accept it by @adriangb in #6951
Replace almost_equal_floats with math.isclose by @eumiro in #7082
bump pydantic-core to 2.5.0 by @davidhewitt in #7077
Add short_version and use it in links by @hramezani in #7115
📝 Add usage link to RootModel by @Kludex in #7113
Revert "Fix default port for mongosrv DSNs (#6827)" by @Kludex in #7116
Clarify validate_default and _Unset handling in usage docs and migration guide by @benbenbang in #6950
Tweak documentation of Field.exclude by @Viicos in #7086
Do not require validate_assignment to use Field.frozen by @Viicos in #7103
tweaks to _core_utils by @samuelcolvin in #7040
Make DefaultDict working with set by @hramezani in #7126
Don't always require typing.Generic as a base for partially parametrized models by @dmontagu in #7119
Fix issue with JSON schema incorrectly using parent class core schema by @dmontagu in #7020
Fix xfailed test related to TypedDict and alias_generator by @dmontagu in #6940
Improve error message for NameEmail by @dmontagu in #6939
Fix generic computed fields by @dmontagu in #6988
Reflect namedtuple default values during validation by @dmontagu in #7144
Update dependencies, fix pydantic-core usage, fix CI issues by @dmontagu in #7150
Add mypy 1.5.0 by @hramezani in #7118
Handle non-json native enum values by @adriangb in #7056
document round_trip in Json type documentation  by @jc-louis in #7137
Relax signature checks to better support builtins and C extension functions as validators by @adriangb in #7101
add union_mode='left_to_right' by @davidhewitt in #7151
Include an error message hint for inherited ordering by @yvalencia91 in #7124
Fix one docs link and resolve some warnings for two others by @dmontagu in #7153
Include Field extra keys name in warning by @hramezani in #7136

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Thanks for the PR!
Deployments, as required, will be available below:

Frontend
Backend
Backend-java
Backend-py
Backend-go

Please create PRs in draft mode.  Mark as ready to enable:

Analysis Workflow
Tests Workflow

After merge, new images are promoted to:

Main Merge Workflow

Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.

pydantic v2 introduced breaking change, I will have to look and update the code @DerekRoberts

https://docs.pydantic.dev/2.0/migration/#code-transformation-tool

@franTarkenton or @conbrad do you have some time to help us and move from pydantic from v1 to v2?
cc @DerekRoberts

@franTarkenton or @conbrad do you have some time to help us and move from pydantic from v1 to v2? cc @DerekRoberts

@mishraomp I can try to carve out some time tomorrow. We've updated this here: https://github.com/bcgov/wps/pull/3028
I'll be less familiar with your domain models so that will require some extra testing from your team but as a short summary, what I found was:

Optional fields set to None by default are more strict on type annotations
Datetime format has changed to expect the Zulu "Z" notation
parse_obj -> model_validate if you're using that anywhere

@franTarkenton or @conbrad do you have some time to help us and move from pydantic from v1 to v2? cc @DerekRoberts

sry... been sick!  Just saw this now

Hey I just had a quick peek at this, it looks like it's failing on trying to build greenlet: https://github.com/bcgov/quickstart-openshift-backends/actions/runs/6431005121/job/17463035443?pr=5#step:2:1012
You might need to update your poetry install

Looks like your base image is using poetry 1.2.2: https://github.com/bcgov/quickstart-openshift-backends/actions/runs/6431005121/job/17463035443?pr=5#step:2:724
But your package.lock file states 1.6.1

@conbrad Thanks!  That explains what I'm working through over here.  Hopefully Python gets a little easier soon.  :D


Codemod for smooth upgrade to 1.0

It would be also to provide a codemod (with the help of js-codeshift) that automatically updates a whole project from Version 0.7.x to 1.0.
Things to change are listed in the Changelog already.

[x] Lowercase Look calls
[x] Remove Component from StyleSheet.create

[x] Merge existing classNames
[x] Use StyleSheet.combineStyles for multiple

Solved long time ago, yet we might need to test and provide those codemods to be working with know tools.


fix example code

I assume &; was leftover from some & html tags.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: Kagre sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

VBA/Language-Reference-VBA/articles/enum-statement.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

All content in this repository has been migrated to a new repository (https://github.com/MicrosoftDocs/VBA-Docs). The changes in this PR have been applied in the new repository, so this PR is being closed. The changes will be published to the live docs soon. Thank you for your contribution!


Adding Twitter Bootstrap CSS Framework

I got bored on the train ride home from work so I decided to take a crack at adding the Twitter Bootstrap framework to Roots.
I added support for the regular framework and the "less" framework as well.  I also added a dropdown on the options page when either version of the framework is selected to either use the optional javascript files for bootstrap or not use them depending as recommended by the bootstrap repo.
Let me know if everything looks ok.

I just saw bootstrap and was looking into integrating into roots and then saw your pull request. Nice job!

kudos!

although this would be great integration, it definitely needs to be tweaked in several places to make it bug free.

Would you mind pointing out what you have seen that could some work?  I have not had a chance to really look through it again, but I would be happy to make some corrections as needed.

You don't need to include the html5shim since modernizr is always loaded.

other than what @swalkinshaw said, do you have anything else you can point out @moimikey?

I will submit an updated pull request once we hear back from @moimlkey

aside from the gravity forms portion, everything else seems a-ok to me if nobody has seen any weird things with a fresh activation of roots and selecting bootstrap.

thx yall :)

need to fix these:
Notice: Undefined index: bootstrap_javascript in /wp-content/themes/roots/inc/roots-actions.php on line 101

Notice: Undefined index: bootstrap_less_javascript in /wp-content/themes/roots/inc/roots-actions.php on line 102

that notice probably applies to all placements of $roots_options['css_framework'] then, no?


Array util function is buggy

I just saw that @willeastcott removed the set util file in https://github.com/playcanvas/engine/commit/f12ab342763ce9a077cf2e0bbe77e3a1018383c1 and took a look at the array one:
https://github.com/playcanvas/engine/blob/main/src/core/array-utils.js
Test code:
function equals(arr1, arr2) {

        if (arr1.size !== arr2.size) {
            return false;
        }
        for (let i = 0; i < arr1.length; i++) {
            if (arr1[i] !== arr2[i]) {
                return false;
            }
        }
        return true;
    }
equals([1, 2], [1, 2, 3]); // Outputs: true

It's clearly wrong, since it needs to access length.

yeah what is that .size doing there!

Luckily it only gets used on an equal sized arrays .. so this has no impact. But much appreciated you finding this out!

yeah what is that .size doing there! What was I thinking! :)

Lets blame the ES people for introducing different nomenclature just to confuse everyone :sweat_smile:


Fix for arabic translations

Looks good, just the one comment I left + this little bug that I found on mobile (missing padding):

Thank you, glad this is coming a long. That's good fine, thank you! I have updated it. I will also send Ahmad the latest staging and ask for his opinion with this. :)

Thanks for fixing the padding issue!
There's one more thing, sorry for not noticing before... this is kinda nitpicky, but I wonder if the diamond next to the active nav item should be on the right end side, to keep the logic consistent with ltr languages. Notice how there's padding on the left of the nav in English to make space for the diamonds, and that padding is also on the left in Arabic, but perhaps it should be on the right? I think this would be especially beneficial on mobile, where the diamond currently ends up pretty far from the text. We could do this in a separate PR, let me know what you think.

I understand what you mean, but I am not sure if we should do this just for diamond icon, to me if we are doing this for diamond then shouldn't we do this for all icons? I think we should ask @ahmadmardeni1 for what he thinks to be honest. Because I don't know how would be the understanding arabic user in this all. @ahmadmardeni1 what do you recommend us doing please?

Yes, all diamonds should be on the right side. But on staging everything is back to ltr for some reason:

Can you check so I can take a look? @alexandriaroberts

Can you check so I can take a look? @alexandriaroberts
ohh, we need to redeploy the staging. Let me do that and I will message you when it's done @ahmadmardeni1. Thank you for checking this!

I've just checked the new deployment. I think all icons are already on the right side like the search and GitHub icons except for the diamond and yes it should be on the right side. @alexandriaroberts @benface

Just checked, great work! @alexandriaroberts


GTK3 apps have no widget themes

GTK3 apps have no themes when run outside of Gnome. For example, with gnome_themes_standard installed in the user profile and the theme set to Adwaita, running
evince

has no theming. If you set GTK_DATA_PREFIX instead,
GTK_DATA_PREFIX=$HOME/.nix-profile evince

it is themed correctly. If the theme is installed in the system profile, set GTK_DATA_PREFIX appropriately.

(triage) @vcunat @lethalman This is probably fixed by now, right?

I'm not sure. Xfce and e19 set $GTK_DATA_PREFIX to the system-env path, so that would e.g. prevent me experiencing the problem.

Sounds to me like a workaround

What would be the right place to document this workaround? I found it quite useful.

Previously the wiki, but I’m not sure where something like that should go now (cc @garbas). We desperately need a cookbook.

there is already a section on Qt, i guess we can create one for GTK as well

Mhm the headlines says Nixpkgs Contributors Guide but this looks this looks like a end-user problem, not related to package contribution. Probably I will write to the wiki anyway to avoid this docbook stuff.

@Mic92 The wiki is in read-only mode and won’t be switched back.

@Mic92 yes, the title is misleading. we should also fix that. right now we need to collect all documentation resources in one place. then it will be much easier to create shape documentation which would target different audience.

(triage) has it been fixed by now?

I'm happily running gtk3 applications outside of gnome without issues, so I think this is safe to close.


Change color

Change the blue color buttons to green color

Hi i would like to work on it

Start working on it


Go SDK build errors on worktree not clean in GHA

@jaxxstorm the build of the Go SDK for this provider errors that the worktree is not clean when building on Github Actions:
https://github.com/pulumiverse/pulumi-scaleway/runs/7856771524?check_suite_focus=true
After running make build_sdks on my local system, my worktree is clean. I can't reproduce this error. I cleaned my Go module cache and retried but still can't reproduce this.
Do you have any idea on how to fix this?

It looks like the Go version isn't pinned, so it's pulling Go version 1.19:
https://github.com/pulumiverse/pulumi-scaleway/blob/master/.github/workflows/main.yml#L39
We need to pin the Go version or update our local one


Cannot consume scoped service from singleton

Today, I updated my project to ASP.NET Core 2 and now, I get the following error:

Cannot consume scoped service IMongoDbContext from singleton IActiveUsersService

All works fine for ASP.NET Core 1.1
I have the following code:
services.AddSingleton<IActiveUsersService, ActiveUsersService>();
services.AddScoped<IMongoDbContext, MongoDbContext>();
services.AddSingleton(option =>
{
   var client = new MongoClient(MongoConnectionString.Settings);
   return client.GetDatabase(MongoConnectionString.Database);
})

public class MongoDbContext : IMongoDbContext
{
   private readonly IMongoDatabase _database;

   public MongoDbContext(IMongoDatabase database)
   {
      _database = database;
   }

   public IMongoCollection<T> GetCollection<T>() where T : Entity, new()
   {
      return _database.GetCollection<T>(new T().CollectionName);
   }
}

public class IActiveUsersService: ActiveUsersService
{

   public IActiveUsersService(IMongoDbContext mongoDbContext)
   {
      ...
   }
}

All works fine for ASP.NET Core 1.1

Yes, it's likely that you had a bug in your 1.1 application. This is now disallowed by default. When you consume a scoped service from a singleton you're forcing the scoped service to be a singleton. Why is your services scoped in the first place? Who is supposed to dispose this scoped object?

Yeah, I have realized it... Need to check all my services. Thanks.


SignalR extensions 1.13.0 Could not load file or assembly 'Microsoft.Extensions.Options, Version=<IP_ADDRESS>,

Description
Currently I have the feeling that both 1.12.0 and 1.13.0 still have the issue as described in #1709
For the analysis that was done in that specific issue I don't have the skills but here is what I found.
When using version 1.13.0 the function app generates an Exception Exception while executing function: Function <--- Could not load file or assembly 'Microsoft.Extensions.Options, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=adb9793829ddae60'. The system cannot find the file specified. I tried adding Microsoft.Extensions.Options to the packakes list (Both <IP_ADDRESS> and the latest), however that failed.
Using version 1.12.0 also results in Exception while executing function: Function <--- Could not load file or assembly 'Microsoft.Extensions.Options, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=adb9793829ddae60'. The system cannot find the file specified.
Only if I use 1.7.0 is this issue resolved.
Steps to reproduce
Note: I didn't test this exact setup but I think the environment should be clear.

Create a new a new Function App with Runtime .NET 8 (LTS) isolated worker model on windows.
Install the nuget Microsoft.Azure.Functions.Worker.Extensions.SignalRService
Create a function that returns a single object that, in turn contains multiple outputs
Publish the function to Azure
Trigger the function and in the Live metrics an exception is generated

In this project I use the following function definition:
[Function("AFunction")]
public Response Run(
    [CosmosDBTrigger(databaseName: "Database",
                     containerName: "InContainer",
                     Connection = "CosmosDbConnectionString",
                     LeaseContainerName = "Leases")] IReadOnlyList<Document> documents)
{
    var documents = new List<OutputDocuments>();
    var actions = new List<SignalRMessageAction>();

    //Some code to fill the documents and the actions

    return new Response()
    {
        OutputDocuments = documents,
        Actions = actions,
    };
}

The Response class contains something similar to this
    public class Response
    {
        [CosmosDBOutput(databaseName: "Database", containerName: "OutContainer", Connection = "CosmosDbConnectionString")]
        public IReadOnlyList<OutputDocuments>? OutputDocuments { get; set; }

        [SignalROutput(ConnectionStringSetting = "AzureSignalRConnectionString", HubName = "TestHub")]
        public IReadOnlyList<SignalRMessageAction>? Actions { get; set; }
    }

Comments
While debugging, I noticed that the exception only occurs after the Run method returned.

Could you please update packages "Microsoft.Azure.Functions.Worker" and "Microsoft.Azure.Functions.Worker.Sdk" to the latest version and have a retry? If it's still not working, please provide a minimal reproducible project.

As requested I just tried with all the latest versions for all the packages.

This time it seems to be working ok.


Does nothing

Does nothing with default or custom settings.

Attempted via options menu
Attempted via shortcuts ctrl+alt+v,  ctrl+alt+c and ctrl+alt+f
Attempted assigning my own shortcuts
Checked file paths are correct

OS
Windows 11 Pro

Windows Version
21H2

Sublime version
<IP_ADDRESS>

Chrome version

99.0.4844.82

It happens to me too dx


Added Facade to the package.

Hello, I loved the package, easy to use, so I decided to shorten it even more by adding a facade, now there is no need for the new Covid() people can simply use the Facade.

Hi, thank you very much for contributing. Please change facade class Covid to Covid19

I just updated the package to start using the Facade, the package is not auto-updated in packagist, so It's still using version 1.1, can you check that out? (the documentation will be irrelevant if the Facade is not working), thanks.


⚠ ClamAV has degraded performance

In 5bed3c1, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 216 ms

Resolved: ClamAV performance has improved in 1eb6dcf after 5 minutes.