No easy way to get substituted holiday translations?

I love this package and have been using it for years. I used to be able to simply do  $holiday->translations['en'] to get translations, even for substituted holidays. Now it seems like I have to do something like this monstrosity:
if ($holiday instanceof SubstituteHoliday) {
    $original = $holiday->substitutedHoliday;

    $holiday_en = $original->translations['en'];
    $holiday_jp = $original->translations['ja'];

    $substitute_en = $holiday->substituteHolidayTranslations['en'];
    $substitute_jp = $holiday->substituteHolidayTranslations['ja'];

    $en = str_replace('{0}', $holiday_en, $substitute_en);
    $jp = str_replace('{0}', $holiday_jp, $substitute_jp);
} else {
    $en = $holiday->translations['en'];
    $jp = $holiday->translations['ja'];
}

Is there no better way? Couldn't find it in the docs..

I suggest adding an optional argument for $holiday->getName() that allows you to override the provider's displayLanguage.
This would allow you to do $holiday->getName('en') and $holiday->getName('ja').
I'll be happy to create a PR for this.

@zachleigh Indeed this isn't really friendly.
@c960657 Pre v2.2.0 the substituted holiday would return all the available translations, whereas v2.2.0 would simply return blank if you use the translations attribute.
Pre v2.2.0
<?php
require 'vendor/autoload.php';

$holidays = Yasumi\Yasumi::create('Japan', 2019);
$childrensDay = $holidays->getHoliday('substituteHoliday:childrensDay');
print_r($childrensDay->translations);

would return:
Array
(
    [en_US] => Children's Day Observed
    [ja_JP] => 振替休日 (こどもの日)
)

v2.2.0 would return an empty array.
I think it is better the behavior is the same as before.

v2.2.0 introduced locale fallback, so we don't have the en_US and ja_JP entries anymore, just en and ja. Preserving the previous behaviour would be difficult.
In general, it is hard to preserve BC for public instance variables.
It would not be difficult to populate translations for substitute holidays, assuming we just use the en/ja keys. I suggest we do this for BC, but that we deprecate such access. Instead I suggest that we add the optional argument for getName() as mentioned, and possibly a new accessor, getTranslations() that returns all available translations.

It would not be difficult to populate translations for substitute holidays, …

On second thought, it is not completely trivial.
E.g. New Year's Day has just one English translation, so the translations array would contain just en (in addition to the non-English locales). The substitute pattern has multiple English patterns (en, en_US, en_CA etc.), so the translations array for substituteHoliday:newYearsDay would need to be populated with entries for the union of locales supported by the substituted holiday and the substitution pattern. This is doable, but it seems like a lot of effort. The resulting translations array would still need some locale-fallback-aware post-processing in order to be useful for the use-case described in this issue.


Implemented new unified strings

MOB-2346
Created and unified new string keys in a backwards compatible manner. The only exception was made for the plurals key, where the override should be for the individual values, not the plural itself.
In minor places, trimmed down reference links in string values, still some TODO-s left in the strings.xml file but vast majority of them is about ADA witch is yet to be unified and will be done in MOB-2280
Decided it is probably be for the best to go with a feature branch approach for this, because we will probably start breaking things otherwise until main functionality is there. Should not cause many conflicts by the end though.

!squash


ZEPPELIN-1063: fix flaky python interpreter test

What is this PR for?
fix flaky python interpreter test
What type of PR is it?
Bug Fix
Todos

[x] cleanup test code
[x] fix flaky open port check

What is the Jira issue?
ZEPPELIN-1063
How should this be tested?
mvn "-Dtest=org.apache.zeppelin.python.PythonInterpreterTest" test -pl python
Questions:

Does the licenses files need update? No
Is there breaking changes for older versions? No
Does this needs documentation? No

Ready to be merged, \cc @minahlee @prabhjyotsingh for review.
CI failure is being taken care of under #1092

Rebased on latest master, after #1092 got merged

CI fails on Integration tests, and failure looks different from #1091 and #1092
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 143.455 sec - in org.apache.zeppelin.integration.ZeppelinIT

Results :

Tests in error:
  ParagraphActionsIT.testClearOutputButton:285->AbstractZeppelinIT.waitForParagraph:70->AbstractZeppelinIT.pollingWait:96 Â» Timeout

Tests run: 15, Failures: 0, Errors: 1, Skipped: 0

CI failure is not related and handled under ZEPPELIN-1073
Merging if there is no further disucssion

Yes, I've seen this, this happens when spark takes longer that 60sec to start up.
Will open up a new jira and fix this as well.


Quick-Start: look into using nomad-local-demo wholesale for ec2_assets

For the Quick-Start scenario, currently we upload all of the Hashistack config, scripts and Fermyon Platform nomad jobs onto the EC2 instance.  (See the ec2_assets dir)
All of these assets were derived from the nomad-local-demo repo, with the bulk of the changes/updates made to the Nomad jobs, Traefik config and how the jobs are run in the run_servers.sh script.
Anyways, cut to the chase: it would be nice to see if all of these changes could somehow be configurable and exist in one, canonical repo (nomad-local-demo) such that this automation could be updated to just run a git clone of the canonical repo and proceed with configuring as needed.
That being said, it may indeed be beneficial to have the assets exist in their different form in this repo, as it can certainly be helpful for users to modify to suit their needs rather than creating a fork/branch of the canonical repo, etc.

For now, we've decided to let each aws and local installer flow manage their own assets/config, despite a fair amount of overlap.  We can revisit down the road.


Wrong permissions

The plugin registers the rainlab.googleanalytics.access_settings permission, but the settings register with the rainlab.googleanalytics.settings

Fixed by #45
Same issue as was https://github.com/rainlab/user-plugin/pull/161


Makefile: two issues related to install_fips resp. uninstall_fips target

make install_fips
It seems like the rule for the install_fips target calls openssl without providing a path.
https://github.com/openssl/openssl/blob/52c6c12c1cad6f1046b34f4139d1aa3e967a5530/Configurations/unix-Makefile.tmpl#L562-L567
In my case, the openssl (1.1.1g) application from my Linux distribution is called, which does not recognize the fipsinstall command:
Invalid command 'fipsinstall'; type "help" for a list.
make: *** [Makefile:3362: install_fips] Error 1

make uninstall_fips
It does not seem right to me to have the uninstall_fips target depend on uninstall_sw, because it should be allowed to remove the FIPS module configuration without uninstalling the entire software.
https://github.com/openssl/openssl/blob/52c6c12c1cad6f1046b34f4139d1aa3e967a5530/Configurations/unix-Makefile.tmpl#L569-L572
Instead, the dependency should probably be the other way around: uninstall the FIPS module configuration as part of uninstalling the software.
Attempted Fix
I tried to use $(DESTDIR)$(INSTALLTOP)/bin/openssl, but I got shared library issues
opt/openssl-dev/bin/openssl: error while loading shared libraries: libssl.so.3: cannot open shared object file: No such file or directory

and I wasn't sure how to address them correctly, i.e. whether I should set the LD_LIBRARY_PATH or use the wrap.pl script and the not-yet-installed openssl app from the source tree instead.
Also, I had problems with my Perl installation (issue #13679), so I gave up.
diff --git a/Configurations/unix-Makefile.tmpl b/Configurations/unix-Makefile.tmpl
index 342e46d24d..d7acecccc4 100644
--- a/Configurations/unix-Makefile.tmpl
+++ b/Configurations/unix-Makefile.tmpl
@@ -552,7 +552,7 @@ depend:

 install_sw: install_dev install_engines install_modules install_runtime

-uninstall_sw: uninstall_runtime uninstall_modules uninstall_engines uninstall_dev
+uninstall_sw: uninstall_runtime uninstall_fips uninstall_modules uninstall_engines uninstall_dev

 install_docs: install_man_docs install_html_docs

@@ -562,11 +562,12 @@ uninstall_docs: uninstall_man_docs uninstall_html_docs
 install_fips: install_sw
        @$(ECHO) "*** Installing FIPS module configuration"
        @$(ECHO) "fipsinstall $(DESTDIR)$(MODULESDIR)/$(FIPSMODULENAME).cnf"
-       @openssl fipsinstall -module $(DESTDIR)$(MODULESDIR)/$(FIPSMODULENAME) \
+       @$(DESTDIR)$(INSTALLTOP)/bin/openssl fipsinstall \
+               -module $(DESTDIR)$(MODULESDIR)/$(FIPSMODULENAME) \
                -out $(DESTDIR)$(MODULESDIR)/$(FIPSMODULENAME).cnf \
                -macopt 'key:$(FIPSKEY)'

-uninstall_fips: uninstall_sw
+uninstall_fips:
        @$(ECHO) "*** Uninstalling FIPS module configuration"
        @$(ECHO) "$(RM) $(DESTDIR)$(MODULESDIR)/$(FIPSMODULENAME).cnf"
        @$(RM) $(DESTDIR)$(MODULESDIR)/$(FIPSMODULENAME).cnf

./util/wrap apps/openssl fipsinstall ...
That's the safest bet.

Ok, I can make  a PR for it, if you help me get my perl problem fixed first.

As noted the other issue is key: should be hexkey:

See #13684.


dom level 2 traversal apis

annotating the DOM Level 2 Traversal API

Thanks! Just a few small things. The test breakages are line number related, so solving them is just replacing the .exp files with .out files.
If you're motivated, it would be awesome to replace the number annotations with the actual constant values. (Unfortunately, we don't support hex format for literal numbers, but the decimal representation should work.)
If you don't want to support this PR, let me know. I'll make the necessary fixes and push it through. Don't worry—you'll still be attributed in the commit!

Thanks! I added the numerical annotations along with some type parameters make use of them in common cases. Is there a way to annotate the fact that despite being class-like, NodeIterator, NodeFilter and TreeWalker do not have constructors?

Woah! Very cool changes. I'm especially intrigued by the type parameter stuff. It's sophisticated enough that I'm worried we might run into a Flow bug. Do you have any examples of code that you'd like to typecheck? There are some tests under tests/node_tests that specifically exercise these libdefs to make sure they're right. I think we can take this without tests, but they'd be nice.
For annotating class-like things which don't have constructors, a few things come to mind. Are NodeIterator, NodeFilter, and TreeWalker runtime values at all, or are they purely interfaces? That is, can I write typeof foo === NodeIterator? If not, you might consider declaring interfaces instead of classes.

They are non-callable objects that behave like constructors as far as instanceof is concerned.
> typeof NodeFilter;
< "object"
> NodeFilter.hasOwnProperty('SHOW_TEXT');
< true
> typeof NodeIterator;
< "object"
< typeof TreeWalker;
< "object"
> var i = document.createNodeIterator(document.body);
> i instanceof NodeIterator
< true
> var w = document.createTreeWalker(document.body);
> w instanceof TreeWalker
< true

Right right. Thanks for understanding me, even though I mixed up typeof and instanceof :P

I don't think we have a great way to type that. I think for now it's OK to leave them as classes. Maybe add a note that the constructors aren't callable, and we can come back in and fix that once we support that use case.

Hey @samwgoldman - I added a two small tests against the behavior I expect from these generics. They aren't currently working as I expect. Do you mind taking a look?

Man, I was going to wait for Travis to do the work for me, but I'll take a look manually tomorrow to see what's up. Thanks a ton for your continued work on this!

withdrawing in favor of https://github.com/facebook/flow/pull/1339


Possible to set a password to protect the write access ?

Hello, we're wondering if it would be possible to set a password to protect the write access from the web GUI interface ?
Thanks

It might be possible, but doing it properly is difficult, and I don't want to put something out that promises "password protection", but is actually insecure.
What is the use case? To stop other staff members writing to PandA by accident? Or to stop extenal people connecting?
At DLS we treat PandA in the same way as PowerBrick and other embedded Devices, we hide it on a separate network so you can only access it on the beamline. This is sufficient for us.

This is more to prevent accident writing if someone opens the GUI just for monitoring. Is it possible to have a read-only option by defaut ?
At SOLEIL the pandabox is also on the beamline separeted network so no external connecting issue.

Sounds a good option if it doesn't bring too much work for you. lt could be very helpful. So the writable button will come with a duration parameter in second?
Thanks

Probably? Or in minutes? Or would you prefer just a simple toggle between writeable and read-only that you have to remember to press to make it read-only again when you're done?

Sorry I meant "minute" actually, it's good for me

Actually, we might be able to be cleverer than this, and make it per session, then we can have a simple toggle. We will investigate, but not until 3.0 is out...

I think we can do this by inspecting the client name here:
https://github.com/dls-controls/pymalcolm/blob/408ab2b6fa4e2dd9c6cbc1a415d49688dc6a3df8/malcolm/modules/web/parts/websocketserverpart.py#L80
Then keeping an internal record of whether the client can write or not

Actually, we might be able to be cleverer than this, and make it per session, then we can have a simple toggle. We will investigate, but not until 3.0 is out...

Ok thanks

This is not planned at the moment


imgui-glium-renderer: export glium and imgui crate

This exports the glium and imgui crates found in the glium-renderer.
This should help glium-renderer users avoid library version conflicts by having them use
use imgui_glium_renderer::glium;
use imgui_glium_renderer::imgui;

I have also removed default-features = false as it was causing undefined references to glium::glutin.

I agree with this piece of code being merged. What's more, I think the same should be done for the imgui-gfx-renderer.

Hmm, I like the idea, but doesn't this mean it's impossible to opt out of glutin now? Using the glium renderer shouldn't pull glutin and all its friends unnecessarily.

Hmm, I like the idea, but doesn't this mean it's impossible to opt out of glutin now? Using the glium renderer shouldn't pull glutin and all its friends unnecessarily.

Not sure what you mean by opt out of glutin. If a project depends on imgui-glium-renderer, then cargo should recursively pull the dependencies of imgui-glium-renderer which include glium.
The reexport here makes the imgui-glium-renderer glium dependency public so that other projects can use the correct version of glium when working with imgui-glium-renderer.

Yes, if a project depends on imgui-glium-renderer, it now pulls glium with default features which then pulls glutin. This is not cool if I have a project that doesn't want glutin and all its friends recursively.
I did a quick test with a dummy project that has a dependency on imgui-glium-renderer in your repository:
master branch in your repository:
[metadata]
"checksum backtrace 0.3.8 (registry+https://github.com/rust-lang/crates.io-index)" = "dbdd17cd962b570302f5297aea8648d5923e22e555c2ed2d8b2e34eca646bf6d"
"checksum backtrace-sys 0.1.19 (registry+https://github.com/rust-lang/crates.io-index)" = "3951a5d75651d5817056daf3132ed9cd7918bc7f2afc313b379009e832209a4d"
"checksum bitflags 1.0.3 (registry+https://github.com/rust-lang/crates.io-index)" = "d0c54bb8f454c567f21197eefcdbf5679d0bd99f2ddbe52e84c77061952e6789"
"checksum cc 1.0.15 (registry+https://github.com/rust-lang/crates.io-index)" = "0ebb87d1116151416c0cf66a0e3fb6430cccd120fd6300794b4dfaa050ac40ba"
"checksum cfg-if 0.1.3 (registry+https://github.com/rust-lang/crates.io-index)" = "405216fd8fe65f718daa7102ea808a946b6ce40c742998fbfd3463645552de18"
"checksum fnv 1.0.6 (registry+https://github.com/rust-lang/crates.io-index)" = "2fad85553e09a6f881f739c29f0b00b0f01357c743266d478b68951ce23285f3"
"checksum gl_generator 0.9.0 (registry+https://github.com/rust-lang/crates.io-index)" = "7a795170cbd85b5a7baa58d6d7525cae6a03e486859860c220f7ebbbdd379d0a"
"checksum glium 0.21.0 (registry+https://github.com/rust-lang/crates.io-index)" = "c1c404ffd4d79f1e8f7821fcecaf7530bd08318256d7ce0ec0cdb48fca81cb36"
"checksum imgui 0.0.19-pre (git+https://github.com/SSStormy/imgui-rs.git)" = "<none>"
"checksum imgui-glium-renderer 0.0.19-pre (git+https://github.com/SSStormy/imgui-rs.git)" = "<none>"
"checksum imgui-sys 0.0.19-pre (git+https://github.com/SSStormy/imgui-rs.git)" = "<none>"
"checksum khronos_api 2.2.0 (registry+https://github.com/rust-lang/crates.io-index)" = "037ab472c33f67b5fbd3e9163a2645319e5356fcd355efa6d4eb7fff4bbcb554"
"checksum lazy_static 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)" = "c8f31047daa365f19be14b47c29df4f7c3b581832407daabe6ae77397619237d"
"checksum libc 0.2.41 (registry+https://github.com/rust-lang/crates.io-index)" = "ac8ebf8343a981e2fa97042b14768f02ed3e1d602eac06cae6166df3c8ced206"
"checksum log 0.4.1 (registry+https://github.com/rust-lang/crates.io-index)" = "89f010e843f2b1a31dbd316b3b8d443758bc634bed37aabade59c686d644e0a2"
"checksum rustc-demangle 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)" = "76d7ba1feafada44f2d38eed812bd2489a03c0f5abb975799251518b68848649"
"checksum smallvec 0.6.1 (registry+https://github.com/rust-lang/crates.io-index)" = "03dab98ab5ded3a8b43b2c80751194608d0b2aa0f1d46cf95d1c35e192844aa7"
"checksum winapi 0.3.4 (registry+https://github.com/rust-lang/crates.io-index)" = "04e3bd221fcbe8a271359c04f21a76db7d0c6028862d1bb5512d85e1e2eb5bb3"
"checksum winapi-i686-pc-windows-gnu 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)" = "ac3b87c63620426dd9b991e5ce0329eff545bccbbb34f3be09ff6fb6ab51b7b6"
"checksum winapi-x86_64-pc-windows-gnu 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)" = "712e227841d057c1ee1cd2fb22fa7e5a5461ae8e48fa2ca79ec42cfc1931183f"
"checksum xml-rs 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)" = "3c1cb601d29fe2c2ac60a2b2e5e293994d87a1f6fa9687a31a15270f909be9c2"

reexport branch in your repository:
[metadata]
"checksum android_glue 0.2.3 (registry+https://github.com/rust-lang/crates.io-index)" = "000444226fcff248f2bc4c7625be32c63caccfecc2723a2b9f78a7487a49c407"
"checksum backtrace 0.3.8 (registry+https://github.com/rust-lang/crates.io-index)" = "dbdd17cd962b570302f5297aea8648d5923e22e555c2ed2d8b2e34eca646bf6d"
"checksum backtrace-sys 0.1.19 (registry+https://github.com/rust-lang/crates.io-index)" = "3951a5d75651d5817056daf3132ed9cd7918bc7f2afc313b379009e832209a4d"
"checksum bitflags 1.0.3 (registry+https://github.com/rust-lang/crates.io-index)" = "d0c54bb8f454c567f21197eefcdbf5679d0bd99f2ddbe52e84c77061952e6789"
"checksum block 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)" = "0d8c1fef690941d3e7788d328517591fecc684c084084702d6ff1641e993699a"
"checksum cc 1.0.15 (registry+https://github.com/rust-lang/crates.io-index)" = "0ebb87d1116151416c0cf66a0e3fb6430cccd120fd6300794b4dfaa050ac40ba"
"checksum cfg-if 0.1.3 (registry+https://github.com/rust-lang/crates.io-index)" = "405216fd8fe65f718daa7102ea808a946b6ce40c742998fbfd3463645552de18"
"checksum cgl 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)" = "80f05e25f9631fdee56693110feda284a49308ca1e768857a0ad3906cfc1502a"
"checksum cocoa 0.14.0 (registry+https://github.com/rust-lang/crates.io-index)" = "b0c23085dde1ef4429df6e5896b89356d35cdd321fb43afe3e378d010bb5adc6"
"checksum core-foundation 0.5.1 (registry+https://github.com/rust-lang/crates.io-index)" = "286e0b41c3a20da26536c6000a280585d519fd07b3956b43aed8a79e9edce980"
"checksum core-foundation-sys 0.5.1 (registry+https://github.com/rust-lang/crates.io-index)" = "716c271e8613ace48344f723b60b900a93150271e5be206212d052bbc0883efa"
"checksum core-graphics 0.13.0 (registry+https://github.com/rust-lang/crates.io-index)" = "fb0ed45fdc32f9ab426238fba9407dfead7bacd7900c9b4dd3f396f46eafdae3"
"checksum dlib 0.4.1 (registry+https://github.com/rust-lang/crates.io-index)" = "77e51249a9d823a4cb79e3eca6dcd756153e8ed0157b6c04775d04bf1b13b76a"
"checksum fnv 1.0.6 (registry+https://github.com/rust-lang/crates.io-index)" = "2fad85553e09a6f881f739c29f0b00b0f01357c743266d478b68951ce23285f3"
"checksum foreign-types 0.3.2 (registry+https://github.com/rust-lang/crates.io-index)" = "f6f339eb8adc052cd2ca78910fda869aefa38d22d5cb648e6485e4d3fc06f3b1"
"checksum foreign-types-shared 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "00b0228411908ca8685dba7fc2cdd70ec9990a6e753e89b6ac91a84c40fbaf4b"
"checksum fuchsia-zircon 0.3.3 (registry+https://github.com/rust-lang/crates.io-index)" = "2e9763c69ebaae630ba35f74888db465e49e259ba1bc0eda7d06f4a067615d82"
"checksum fuchsia-zircon-sys 0.3.3 (registry+https://github.com/rust-lang/crates.io-index)" = "3dcaa9ae7725d12cdb85b3ad99a434db70b468c09ded17e012d86b5c1010f7a7"
"checksum gl_generator 0.9.0 (registry+https://github.com/rust-lang/crates.io-index)" = "7a795170cbd85b5a7baa58d6d7525cae6a03e486859860c220f7ebbbdd379d0a"
"checksum gleam 0.5.0 (registry+https://github.com/rust-lang/crates.io-index)" = "e47b39459e47b76be4d2c82702932cdc66df09dcb8f813424167991adb8b3380"
"checksum glium 0.21.0 (registry+https://github.com/rust-lang/crates.io-index)" = "c1c404ffd4d79f1e8f7821fcecaf7530bd08318256d7ce0ec0cdb48fca81cb36"
"checksum glutin 0.14.0 (registry+https://github.com/rust-lang/crates.io-index)" = "5ed2d11d21384aa2e0ad027105a26d93d5ca22c73da4000ddd0ecede89571cf0"
"checksum imgui 0.0.19-pre (git+https://github.com/SSStormy/imgui-rs.git?branch=reexport)" = "<none>"
"checksum imgui-glium-renderer 0.0.19-pre (git+https://github.com/SSStormy/imgui-rs.git?branch=reexport)" = "<none>"
"checksum imgui-sys 0.0.19-pre (git+https://github.com/SSStormy/imgui-rs.git?branch=reexport)" = "<none>"
"checksum khronos_api 2.2.0 (registry+https://github.com/rust-lang/crates.io-index)" = "037ab472c33f67b5fbd3e9163a2645319e5356fcd355efa6d4eb7fff4bbcb554"
"checksum lazy_static 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)" = "c8f31047daa365f19be14b47c29df4f7c3b581832407daabe6ae77397619237d"
"checksum libc 0.2.41 (registry+https://github.com/rust-lang/crates.io-index)" = "ac8ebf8343a981e2fa97042b14768f02ed3e1d602eac06cae6166df3c8ced206"
"checksum libloading 0.5.0 (registry+https://github.com/rust-lang/crates.io-index)" = "9c3ad660d7cb8c5822cd83d10897b0f1f1526792737a179e73896152f85b88c2"
"checksum log 0.4.1 (registry+https://github.com/rust-lang/crates.io-index)" = "89f010e843f2b1a31dbd316b3b8d443758bc634bed37aabade59c686d644e0a2"
"checksum malloc_buf 0.0.6 (registry+https://github.com/rust-lang/crates.io-index)" = "62bb907fe88d54d8d9ce32a3cceab4218ed2f6b7d35617cafe9adf84e43919cb"
"checksum memmap 0.6.2 (registry+https://github.com/rust-lang/crates.io-index)" = "e2ffa2c986de11a9df78620c01eeaaf27d94d3ff02bf81bfcca953102dd0c6ff"
"checksum objc 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)" = "877f30f37acef6749b1841cceab289707f211aecfc756553cd63976190e6cc2e"
"checksum osmesa-sys 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)" = "88cfece6e95d2e717e0872a7f53a8684712ad13822a7979bc760b9c77ec0013b"
"checksum percent-encoding 1.0.1 (registry+https://github.com/rust-lang/crates.io-index)" = "31010dd2e1ac33d5b46a5b413495239882813e0369f8ed8a5e266f173602f831"
"checksum pkg-config 0.3.11 (registry+https://github.com/rust-lang/crates.io-index)" = "110d5ee3593dbb73f56294327fe5668bcc997897097cbc76b51e7aed3f52452f"
"checksum rand 0.4.2 (registry+https://github.com/rust-lang/crates.io-index)" = "eba5f8cb59cc50ed56be8880a5c7b496bfd9bd26394e176bc67884094145c2c5"
"checksum redox_syscall 0.1.38 (registry+https://github.com/rust-lang/crates.io-index)" = "0a12d51a5b5fd700e6c757f15877685bfa04fd7eb60c108f01d045cafa0073c2"
"checksum remove_dir_all 0.5.1 (registry+https://github.com/rust-lang/crates.io-index)" = "3488ba1b9a2084d38645c4c08276a1752dcbf2c7130d74f1569681ad5d2799c5"
"checksum rustc-demangle 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)" = "76d7ba1feafada44f2d38eed812bd2489a03c0f5abb975799251518b68848649"
"checksum shared_library 0.1.8 (registry+https://github.com/rust-lang/crates.io-index)" = "8254bf098ce4d8d7cc7cc6de438c5488adc5297e5b7ffef88816c0a91bd289c1"
"checksum smallvec 0.6.1 (registry+https://github.com/rust-lang/crates.io-index)" = "03dab98ab5ded3a8b43b2c80751194608d0b2aa0f1d46cf95d1c35e192844aa7"
"checksum tempfile 3.0.2 (registry+https://github.com/rust-lang/crates.io-index)" = "47776f63b85777d984a50ce49d6b9e58826b6a3766a449fc95bc66cd5663c15b"
"checksum token_store 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)" = "a686838375fc11103b9c1529c6508320b7bd5e2401cd62831ca51b3e82e61849"
"checksum wayland-client 0.12.5 (registry+https://github.com/rust-lang/crates.io-index)" = "2b90adf943117ee4930d7944fe103dcb6f36ba05421f46521cb5adbf6bf0fbc8"
"checksum wayland-kbd 0.13.1 (registry+https://github.com/rust-lang/crates.io-index)" = "4fe0fb1c9917da9529d781659e456d84a693d74fe873d1658109758444616f76"
"checksum wayland-protocols 0.12.5 (registry+https://github.com/rust-lang/crates.io-index)" = "fb5942dd2fc79d934db437c9ea3aabffceb49b546046ea453bcba531005e5537"
"checksum wayland-scanner 0.12.5 (registry+https://github.com/rust-lang/crates.io-index)" = "dcffa55a621e6f2c3d436de64d840fc325e1d0a467b92ee5e7292e17552e08ad"
"checksum wayland-sys 0.12.5 (registry+https://github.com/rust-lang/crates.io-index)" = "377a2f83063c463e801ca10ae8cb9666e6e597eecac0049ac36cc7b9a83b0db3"
"checksum wayland-window 0.13.3 (registry+https://github.com/rust-lang/crates.io-index)" = "e5bf431e84f0de9cd06a30b2fb9ab9458f449cb6c36277da703e979ad5c141b1"
"checksum winapi 0.3.4 (registry+https://github.com/rust-lang/crates.io-index)" = "04e3bd221fcbe8a271359c04f21a76db7d0c6028862d1bb5512d85e1e2eb5bb3"
"checksum winapi-i686-pc-windows-gnu 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)" = "ac3b87c63620426dd9b991e5ce0329eff545bccbbb34f3be09ff6fb6ab51b7b6"
"checksum winapi-x86_64-pc-windows-gnu 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)" = "712e227841d057c1ee1cd2fb22fa7e5a5461ae8e48fa2ca79ec42cfc1931183f"
"checksum winit 0.12.0 (registry+https://github.com/rust-lang/crates.io-index)" = "a282d348b2a57f74617972c08dda0ff74a7383c9fe4f861a882e6fbba46a6521"
"checksum x11-dl 2.17.5 (registry+https://github.com/rust-lang/crates.io-index)" = "3235540540fde1ae074c8df49054166c0e070407f1c6e1ee17b8c87c2c7bcc7d"
"checksum xml-rs 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)" = "3c1cb601d29fe2c2ac60a2b2e5e293994d87a1f6fa9687a31a15270f909be9c2"

In that case, how about we add a cargo feature that lets users chose whether the reexport or not?
I've pushed a commit to my branch, check it out if you can.

Unfortunately that doesn't help, because the problem is not the re-export but the removal of default-features = false :cry:

as it was causing undefined references to glium::glutin

What did these errors look like? The re-export is a very good idea, and I'll immediately merge this if we can solve these errors without removing default-features = false.

I solved this issue by introducing new feature in glium renderer, that turns on glutin feature on glium.
Take a look: https://github.com/semtexzv/imgui-rs/commit/35f3cb8a5d9cef31bd1127609b389ec7d701c511

Implemented in https://github.com/Gekkio/imgui-rs/commit/bbf9c57cdc68abb45a301a02ed7c1b9389a16d51 (discussed caveats still apply though)


Formatting issues on page - perhaps several pages effected

Issue in ./help/marketo/product-docs/demand-generation/landing-pages/landing-page-templates/create-a-guided-landing-page-template.md
The code is wrapped by confluence html, this should be removed throughout the document.
<pre data-theme="Confluence">

Almost two years and no results? This is an easy update!


Can't install using npm

resin-cli version: latest
Operating system and architecture: macOS Hight Sierra

I have npm 5.6 and node 9.5, can't install resin-cli due to multiple deprecated warnings.
I have tried multiple solutions but to no avail, any ideas?
Thank you for your time
npm install --global --production resin-cli
npm WARN deprecated<EMAIL_ADDRESS>please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
npm WARN deprecated<EMAIL_ADDRESS>CoffeeScript on NPM has moved to "coffeescript" (no hyphen)
npm WARN deprecated<EMAIL_ADDRESS>please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
/Users/Odys/.npm-packages/bin/resin -> /Users/Odys/.npm-packages/lib/node_modules/resin-cli/bin/resin
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/resin-cli/node_modules/diskpart):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"win32","arch":"any"} (current: {"os":"darwin","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/resin-cli/node_modules/removedrive):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"win32","arch":"any"} (current: {"os":"darwin","arch":"x64"})

+<EMAIL_ADDRESS>added 4 packages and updated 1 package in 48.659s

Hi @OdysLam ,
resin-cli should be installed anyway, regardless of the warnings. Does$ resin version yield any results?
In any case, we should look into deprecated dependencies since these warnings can (and do) cause confusion.

Either resin is not installed or not linked because it says "Command not found"

@OdysLam my guess is that the folder of globally installed npm scripts is missing from your $PATH , which could happen depending on how you installed npm.
Normally, the resulting folder from echo $(npm config --global get prefix)/bin should appear in $PATH. If it does not, a quick workaround would be to append this folder in the $PATH variable in your ~/.bashrc. A second option would be to attempt an npm reinstall (By the way, how do you install npm in the first place?). Another alternative is to try using our standalone CLI binary by following these installation instructions.

I had a huge problem with a nextclick-args bug  and eventually re-installed node using the provided .pkg from their site.
The USER/.npm-packages does not appear in the $PATH, that's strange since I suppose that the .pkg is the official way of installing node/npm (and not brew).

@OdysLam It sounds like from the above, this is a configuration issue on your system, not a CLI bug, is that right? You'll definitely need the npm bin path in your $PATH to install packages like resin CLI.
I'm going to close this bug report for now, since it doesn't look like a CLI bug, but feel free to ping here if you are still having trouble.


[HUDI-5963] Release 0.13.1 prep

Change Logs
Preparing 0.13.1 branch.
Impact
Preparing 0.13.1 branch.
Risk level (write none, low medium or high below)
low.
Documentation Update
N/A
Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

@hudi-bot run azure

@hudi-bot run azure

Hope we can also include: https://github.com/apache/hudi/pull/8374

Hope https://issues.apache.org/jira/browse/HUDI-6021 can solve this problem in 0.13.1 too


libcbor: unstable-2023-01-29 -> 0.10.2

Description of changes
None.  The unstable commit that this package is already using was from Jan 29 2023.  Two days later, a stable release was cut.  In the interim, two changes were made to the readme and nothing else.
Things done

Built on platform(s)

[ ] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@simonhollingshead greetings !
this PR causes mass rebuilds and should target staging
see more https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md#changes-causing-mass-rebuilds
there is a commit pitfall when changing target branch, please read
https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md#rebasing-between-branches-ie-from-master-to-staging

I think it's been rebased correctly now.

yes !


Fix navigation parameters on GoBackAsync

Previously, when navigation parameters were handed into GoBackAsync, the navigation service ignored them and used default(INavigationParameters), which resulted in the navigation service using whatever parameters had originally been handed to the page. This change respects the provided parameters.

I implement your pull requests in my repo and it works very well. The navigation works for me now.


BoundingBoxGizmo causes issues with soft-parented meshes

Bug
Repro playground: https://www.babylonjs-playground.com/#B92VVX#2
As you can see from the playground, I've got a box mesh with a BoundingBoxGizmo attached. Separately, there's an abstract mesh (mimicRoot) with another box mesh parented to it. Before every render frame, the transforms (scale, rotation, and position) of the box are copied to mimicRoot, causing its child to follow the big box around the screen as it's dragged.
The problem occurs when you scale or rotate using the gizmo. This causes the smaller box to flicker around the screen haphazardly. Eventually, it goes back where it should when you stop dragging.

@nbduke does this work https://www.babylonjs-playground.com/#B92VVX#3 The world matrix needs to be updated manually.

That does fix the issue - until you add another layer in between the gizmo and the box. See https://www.babylonjs-playground.com/#B92VVX#4.

Yes, that works. Do you mind explaining why it works? And also, is this a possible performance issue? Is there another way to do it?

In Babylon, meshes have a position rotation and scale as well as a world matrix. Creating the matrix from position/roation/scale is a little expensive so babylon tries to do this only once per frame. The bounding box gizmo only modifies the position/rotation/scale but not the matrix but you are trying to get the position rotation and scale of the matrix which may be incorrect as it has not been computed yet. To do this you can call computeWorldMatrix of the parent, because of the way parenting matrix's currently works in babylon the child's matrix also needs to be computed considering the parent's matrix but since the child isn't yet flagged as a dirty matrix it needs to be forced into being computed which is why the true parameter is passed in.

Ok that makes sense, thanks. Would it be better (or equivalent) to call scene.incrementRenderId() instead?

Yep, that should work as well but instead of just the gizmo object it will do this for all objects in your scene so if you change position/rotation/scale many times after calling scene.incrementRenderId() you may get double matrix computations so I would only recommend doing this to the objects you need if you are extremely worried about perf.

Closing for now, feel free to reopen if you hit any issue.


Cleanup dependencies to deprecated Spring Security Oauth

With the implementation in these two classes

https://github.com/SAP/cloud-security-xsuaa-integration/blob/master/spring-xsuaa/src/main/java/com/sap/cloud/security/xsuaa/token/OAuth2AuthenticationConverter.java
https://github.com/SAP/cloud-security-xsuaa-integration/blob/master/spring-xsuaa/src/main/java/com/sap/cloud/security/xsuaa/token/AuthenticationToken.java
we have dependecies to Spring Security OAuth2 which is already deprecated. We have to check whether we can setup a principal differently, maybe as described here in the baeldung tutorial

References:

https://www.baeldung.com/spring-security-oauth-principal-authorities-extractor
https://github.com/SAP/cloud-security-xsuaa-integration/issues/399
https://github.com/spring-projects/spring-security/wiki/OAuth-2.0-Migration-Guide

Hi @pianocktail,
can you please create a JIRA Ticket for that, this has to be solved soon.
Best regards,
Nena

SECAUTH-1125 created


fixes #60 not tested in arduino

not tested on arduino

what does this do? Can you test on Arduino?

Must have been a bug in esp32, seems to be resolved now.


Update CODEOWNERS and docs to align with new MR review process

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/3294
Originally created by @pandemicsyn on 2022-02-28 18:33:19

Per meta#212 we're overhauling our review processes and assigning approval pairs to subsections of our code. With the break down being as follows:

source path
primary approver
secondary approver

src/webapp
@alexmarple
@pandemicsyn

src/meltano/api
@pandemicsyn
@alexmarple

docs
@tayloramurphy
@afolson

discovery.yml
@aaronsteers
@pnadolny13

* (else)
@pandemicsyn
@edgarrmondragon

View 5 previous comments from the original issue on GitLab


SHA1 Hashing Algo

Name: Ritika Chand
Title: SHA1 hashing Algo
Language: Python

[x] Hacktoberfest2022 Participant
[x] Contributor

Description:
Python code to hash sentences in SHA1

@prathimacode-hub please assign this issue to me as part of hacktober fest 2022

Issue assigned to @RC2208


Attempt to fix example syntax sections

Something fishy going on with the Markdown for the code examples in the
Notes page. Might be down to the indentation of the list item's content?
The vim markdown parser seems to think so anyway; let's see what
pythonhosted.org says ...

Hmm. It's still broken. The resource generator I use tends to be ok at generating code blocks nested within list items as long as everything's indented, ensuring the list numbering doesn't end.
However, mkdocs is breaking the code blocks here. I've tried with two, three and four space indentations and they're all broken.
I did manage to fix it by replacing fenced code blocks with just double indented code, like so:
1. **Keep your program alive with `signal.pause`**

    The following program looks like it should turn an LED on:

       from gpiozero import led

       led = LED(2)

       led.on()

Hmm, the GFM-based syntax highlighter I use in vim (https://github.com/jtratner/vim-flavored-markdown) thinks that the 4-char indented content of the lists is all a huge code block (because it's 4-chars indented) and corrects this when I dropped it to 3, which is why I thought it might work on pythonhosted. Unfortunately this is one of several areas where MD isn't well specified so implementations tend to vary substantially in their interpretations.
I'm vaguely tempted to convert that chapter to reST so I can at least link to things like signal.pause properly and highlight lines in code blocks, but I know you'd hate me for it ;) I'll tweak it to use indented blocks for now!


Why delete entrypoint.sh ?

Support guidelines

[X] I've read the support guidelines

I've found a bug and checked that ...

[ ] ... the documentation does not mention anything about my problem
[ ] ... there are no open or closed issues that are related to my problem

Description
Hello I liked the entrypoint.sh because I could specify :
client min protocol = NT1
server min protocol = NT1
ntlm auth = ntlmv1-permitted

Now I don't get the init file point
Expected behaviour
retro compat please ?
Actual behaviour
entrypoint is misplaced
Steps to reproduce
...
Docker info
...

Docker Compose config
No response
Logs
...

Additional info
No response

entrypoint is misplaced

It has changed since switch to s6-overlay in https://github.com/crazy-max/docker-samba/pull/85 which does not need an entrypoint script as the base s6-alpine image already has one: https://github.com/crazy-max/docker-alpine-s6/blob/aa655e9d8a090907690f244af93be90a8963ce75/Dockerfile#L256

Hello I liked the entrypoint.sh because I could specify :
client min protocol = NT1
server min protocol = NT1
ntlm auth = ntlmv1-permitted

I guess you were mounting a custom entrypoint.sh? If so you should not as it tampers the container lifecycle. Instead you can set smbd command options like: https://github.com/crazy-max/docker-samba/discussions/77#discussioncomment-6714035
But with switch to s6-overlay I don't think you can do this anymore. Maybe I could allow passing additional flags to the process.
Have you tried making changes in the yaml config?:
global:
  - "client min protocol = NT1"
  - "server min protocol = NT1"
  - "ntlm auth = ntlmv1-permitted"

Also if what you want with NT1 is service discovery, you can use https://github.com/crazy-max/docker-samba#service-discovery-for-windows instead.

I'm running it into a container in a kubernetes cluster, for redundancy,
I struggled to find the config file but you're right with the global options it seems working.
I also tried to modify it from the Dockerfile at the armv8 build stage :
For who wants :

COPY ./01-config.sh /etc/cont-init.d/01-config.sh

Maybe it should be explicit in the repo if we want to add something else for those who are not familiar with s6 / overlay or add new features like ? btrfs ? ipfs ?
Thanks, you can close this ticket.

COPY ./01-config.sh /etc/cont-init.d/01-config.sh

Maybe it should be explicit in the repo if we want to add something else for those who are not familiar with s6 / overlay or add new features like ? btrfs ? ipfs ?

If you want to fork and make your own changes feel free to do so but don't think it should be documented here. Also like I said, we could allow additional args being passed to smbd, I would not be against that.

Thanks, you can close this ticket.

:+1:


objects completely broken #V2

Expected Behavior
cylinder
Actual Behavior
messed up triangles
Steps to Reproduce the Problem

load simple project

const jscad = require('@jscad/modeling')
const { cuboid, sphere, cylinder, circle, star } = require('@jscad/modeling').primitives
const main = () => {
return [
cylinder({ radius: 1 }),
]
}
module.exports = { main }

Specifications

Version: v2
Platform: Windows
Environment: browsers: Chrome, FF

@hrgdavor thanks
Also reported in #576
I have already added a pull request to fix this #578
Hold on...

sorry to bother u, but I tried to switch to the branch with the fix, (v2-fix-compact-binaries)
did npm run clean
npm run bootstrap
went into packages/web
npm run dev
Error: Cannot find module './cylinderElliptic' from 'C:\wrk\OpenJSCAD.org\packages\vtree\core\modeling\primitives'
    at C:\wrk\OpenJSCAD.org\packages\web\node_modules\browserify\node_modules\browser-resolve\node_modules\resolve\lib\async.js:55:21
    at load (C:\wrk\OpenJSCAD.org\packages\web\node_modules\browserify\node_modules\browser-resolve\node_modules\resolve\lib\async.js:69:43)
    at onex (C:\wrk\OpenJSCAD.org\packages\web\node_modules\browserify\node_modules\browser-resolve\node_modules\resolve\lib\async.js:92:31)
    at C:\wrk\OpenJSCAD.org\packages\web\node_modules\browserify\node_modules\browser-resolve\node_modules\resolve\lib\async.js:22:47
    at FSReqCallback.oncomplete (fs.js:166:21) {
  stream: [Labeled]

@hrgdavor You are fast...
OK. Once again, pull the latest updateds on that branch (v2-fix-compact-binaries)
I think that will work now.

nice, it works now on that branch :) :) :)

This should work now. Please pull the latest changes from V2 branch.


[AutoPR datafactory/resource-manager] Updating the default package tag for ADF to latest API

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/3333

(message created by the CI based on PR content)

@AutorestCI rebase

Rebase done and pushed to the branch

This PR has been merged into https://github.com/Azure/azure-sdk-for-python/pull/2293


[Enhancement] update starlet to v1.0.1

update starlet minor version, support ks object storage domain name

What type of PR is this：

[ ] BugFix
[ ] Feature
[X] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[X] I have checked the version labels which the pr will be auto backported to target branch

[X] 3.0
[ ] 2.5
[ ] 2.4
[ ] 2.3

@Mergifyio backport branch-3.0


Build the distribution using Gradle

[ ] make all Java projects compile at least

[x] cli
[x] cmr
[x] common
[ ] compiler-java
[ ] compiler-js
[ ] dist
[ ] java-main
[x] langtools-classfile
[ ] language
[x] model
[ ] runtime
[ ] tool-provider
[ ] typechecker

[ ] make sure the jars get the same name they get now
[ ] make sure they get copied to their proper places in ./dist/dist/repo
[ ] create the special jars like ceylon-bootstrap.jar and ceylon-ant.jar
[ ] add ceylon compilation (ceylon.language)
[ ] handle the OSGi (for the IDE) stuff somehow
probably more stuff

If @chochos and @ckulenkampff want to contribute they are very welcome becuase my knowledge of Gradle is close to 0. Just check out the gradle_build branch

OK cmr builds now. I also fixed some missing resources in common and model.

And I just merged master so I had to change it a bit (because it now needs the new cli project).
I also made it put all the build artifacts in ./ceylon/build instead of in the build folders where Ant puts things so they don't mess with eachother

Now 5 cmr tests fail, but it doesn't seem to be because of missing stuff, something to do with assertions.

You're even running the tests? Great! I was already happy things were building! ;)

I added a (non-working) build file for the typechecker, but ANTLR complains for some reason. I've pushed it but haven't updated the settings file so it won't break the current build.

@chochos the assertion error is almost certainly because of more missing dependencies. In the CeylonClassLoader the following dependencies are added to the classpath:
        archives.add(getRepoJar(ceylonRepo, "org.eclipse.aether.aether-api", "1.1.0")); // optional
        archives.add(getRepoJar(ceylonRepo, "org.eclipse.aether.aether-spi", "1.1.0")); // optional
        archives.add(getRepoJar(ceylonRepo, "org.eclipse.aether.aether-util", "1.1.0")); // optional
        archives.add(getRepoJar(ceylonRepo, "org.eclipse.aether.aether-impl", "1.1.0")); // optional
        archives.add(getRepoJar(ceylonRepo, "org.eclipse.aether.aether-connector-basic", "1.1.0")); // optional
        archives.add(getRepoJar(ceylonRepo, "org.eclipse.aether.aether-transport-file", "1.1.0")); // optional
        archives.add(getRepoJar(ceylonRepo, "org.eclipse.aether.aether-transport-http", "1.1.0")); // optional
        archives.add(getRepoJar(ceylonRepo, "com.google.guava.guava", "18.0")); // optional
        archives.add(getRepoJar(ceylonRepo, "org.apache.commons.lang3", "3.4")); // optional
        archives.add(getRepoJar(ceylonRepo, "org.apache.maven.maven-artifact", "3.3.9")); // optional
        archives.add(getRepoJar(ceylonRepo, "org.apache.maven.maven-model", "3.3.9")); // optional
        archives.add(getRepoJar(ceylonRepo, "org.apache.maven.maven-model-builder", "3.3.9")); // optional
        archives.add(getRepoJar(ceylonRepo, "org.apache.maven.maven-repository-metadata", "3.3.9")); // optional
        archives.add(getRepoJar(ceylonRepo, "org.apache.maven.maven-builder-support", "3.3.9")); // optional
        archives.add(getRepoJar(ceylonRepo, "org.apache.maven.maven-settings", "3.3.9")); // optional
        archives.add(getRepoJar(ceylonRepo, "org.apache.maven.maven-settings-builder", "3.3.9")); // optional
        archives.add(getRepoJar(ceylonRepo, "org.apache.maven.maven-aether-provider", "3.3.9")); // optional
        archives.add(getRepoJar(ceylonRepo, "org.codehaus.plexus.plexus-interpolation", "1.22")); // optional
        archives.add(getRepoJar(ceylonRepo, "org.codehaus.plexus.plexus-utils", "3.0.22")); // optional

        archives.add(getRepoJar(ceylonRepo, "com.github.lookfirst.sardine", "5.1"));
        archives.add(getRepoJar(ceylonRepo, "org.apache.httpcomponents.httpclient", "4.3.2"));
        archives.add(getRepoJar(ceylonRepo, "org.apache.httpcomponents.httpcore", "4.3.2"));
        archives.add(getRepoJar(ceylonRepo, "org.apache.commons.logging", "1.1.1"));
        archives.add(getRepoJar(ceylonRepo, "org.apache.commons.codec", "1.8"));
        archives.add(getRepoJar(ceylonRepo, "org.slf4j.api", "1.6.1"));
        archives.add(getRepoJar(ceylonRepo, "org.slf4j.simple", "1.6.1")); // optional

So for runtime many more dependencies are needed, I jsut added the ones necessary for compilation.

I'll work on the typechecker today then. And I'll take a look at those missing runtime dependencies.

Btw @gijsleussink this is the issue we use to track the progress of the Gradle build conversion (referencing him because he has indicated he's willing to help us out here)

So the typechecker now also builds... but only because I faked it by delegating the ANTLR stuff back to Ant. This is not what we want as a final solution of course, but it at least lets us continue converting the rest of the projects.

ok cool. What's next, compilers?

yeah, I made a start with the jvm backend already. The js backend should be simpler (less dependencies and there's only a single output jar/module compared to the jvm backend's 4)

I added a build file for the JS backend @chochos (you're just too slow ;) ).

I've been asked by @gijsleussink whether I can maybe help out with some Gradle-specific stuff.
@quintesse Any specific subproject that you need help in most where I can try to get my hands dirty on?

Hi @ysb33r , any help would be very much appreciated indeed! The final goals we are trying to achieve is to a) make the Ceylon distribution build using Gradle and b) have a proper working Gradle plugin for the Ceylon compilers and tools.
The problem is that there's nobody on the team right now that knows much about Gradle (normally just about enough to be able to fiddle around with existing Gradle builds without breaking too much).
We've been busy moving the current Ceylon Ant build (as documented here) to Gradle step by step. Meaning that for some complicated parts we're still using the Gradle Ant integration to use the current Ant build files.
The first direct goal is to finish the Gradle build files in such a way that we would be able to create the same results using Gradle as using Ant. Right now all the sub-projects and their dependencies are defined but one of those projects is being deferred to Ant completely (the language sub-module) and the projects that depend on it don't build because of missing symbols. I'm guessing that's because what gets built by Ant is not what Gradle is expecting so we need to give it more information somehow.
You can reproduce this if you check out the gradle_build branch of https://github.com/ceylon/ceylon.git and run ./gradlew assemble.
If we fix that we would at least have all the main artifacts built. We would still have to make sure that:

some secondary artifacts get built (one or two of the sub-projects actually generate 2 jars instead of one, I don't know how to tell Gradle to do that)
the jars get their proper name and get copied to a central location like we do with Ant
the jars get an OSGi post-processing step applied to them (we should leave that to Ant in the beginning probably)

Only then would we be at the point that Gradle would generate a working Ceylon distribution.
After that we could make improvements, make sure we can run the tests, move more things away from Ant and hopefully get rid of using Ant entirely.
As you can see there's still enough left to do ;)
Maybe it seems a bit much. But even having somebody who really knows Gradle that can take a look at our Gradle build and give advice and answer noob questions would really help us out.

So, we've come a long way, but it seems there's just a tiny little thing to fix before we can actually use Gradle to at least build the distribution. This is what I do:
 $ ant clean-all
 $ ./gradlew clean dist
 $ cp -a build/distribution dist/dist
 $ mkdir -p build/osgi-distribution dist/osgi/build
 $ cp -a build/osgi-distribution dist/osgi/build/dist
 $ ant clean-sdk sdk clean-ide ide

And the SDK builds fine, and so do the IDE dependencies like the formatter and the convertor and ide-common, but compiling the Eclipse plugin I get this error:
 [exec] [INFO] Resolving dependencies of MavenProject: com.redhat.ceylon.eclipse:com.redhat.ceylon.eclipse.ui:1.3.2-SNAPSHOT @ /home/ceylon/ceylon/ceylon-ide-eclipse/plugins/com.redhat.ceylon.eclipse.ui/pom.xml
 [exec] [INFO] {osgi.os=macosx, osgi.ws=cocoa, org.eclipse.update.install.features=true, osgi.arch=x86_64}
 [exec] [ERROR] Cannot resolve project dependencies:
 [exec] [ERROR]   Software being installed: com.redhat.ceylon.eclipse.ui 1.3.2.qualifier
 [exec] [ERROR]   Missing requirement: com.redhat.ceylon.eclipse.ui 1.3.2.qualifier requires 'bundle com.redhat.ceylon.dist.repo 1.3.2' but it could not be found

Looking at the bit where it says "1.3.2.qualifier" I guess the problem is that the qualifier hasn't been specified yet and we're seeing a placeholder value?
Could you take a look @davidfestal ? (Or point me in the right direction)

It seems to me that the ant targets that replace the qualifer string by real the qualifier value has not been implemented in gradle.
More pecisely, I'm speaking of the updateManifest target of the ceylon/dist/osgi/build.xml file:
    <target name="updateManifest" >
        <copy todir="${basedir}/META-INF" overwrite="true">
            <fileset dir="${basedir}/meta-inf-templates">
                <include name="**" />
            </fileset>
            <filterset>
                <filter token="ceylon-version" value="${ceylon.osgi.version}"/>
            </filterset>
        </copy>

    	<copy todir="${build.classes}" >
            <fileset dir="${basedir}">
                <include name="META-INF/**" />
            </fileset>
        </copy>
        <replaceregexp file="${build.classes}/META-INF/MANIFEST.MF"
            match="(Bundle-Version: .*\-)qualifier"
            replace="\1${qualifier}"
            byline="true"/>

        <copy todir="${repoDir}/META-INF" overwrite="true">
            <fileset dir="${repoDir}/meta-inf-templates">
                <include name="**" />
            </fileset>
            <filterset>
                <filter token="ceylon-version" value="${ceylon.osgi.version}"/>
            </filterset>
        </copy>
    	<copy todir="${build.repo}" >
            <fileset dir="${repoDir}">
                <include name="META-INF/**" />
            </fileset>
        </copy>
        <replaceregexp file="${build.repo}/META-INF/MANIFEST.MF"
            match="(Bundle-Version: .*\-)qualifier"
            replace="\1${qualifier}"
            byline="true"/>
    </target>

If you still need it, next week I'll try to have a look at where this should be done in the gradle build.

I've looked into it. it's not precisely what I had thought. the embedded repo pluginis not correctly generated. I'll debug this further.

@davidfestal Just mention me on Gitter and I'll see where I can help.


Failed to upgrade Spring Boot app from Flyway 8.5.13 to 9.0.1

Which version and edition of Flyway are you using?
9.0.1
If this is not the latest version, can you reproduce the issue with the latest one as well? (Many bugs are fixed in newer releases and upgrading will often resolve the issue)
N/A
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)
Gradle
Which database are you using? (Type & version)
Postgres 11
Which operating system are you using?
MacOS
What did you do? (Please include the content causing the issue, any relevant configuration settings, the SQL statement(s) that failed (if any), and the command you ran)
I attempted to upgrade a Spring Boot app (2.7.2) built with Gradle from Flyway 8.5.13 to 9.0.1. I made the following changes in build.xml
plugins {
    id "org.flywaydb.flyway" version "9.0.1"
}

dependencies {
    implementation "org.flywaydb:flyway-core:9.0.1"
}

What did you expect to see?
I expect the Spring Boot app to start without errors
What did you see instead?
I get the following error, which prevents the app from starting. In the app's configuration, I don't specify any particular value for the "ignore missing migrations" setting, so the default should be used
***************************
APPLICATION FAILED TO START
***************************

Description:

An attempt was made to call a method that does not exist. The attempt was made from the following location:

    org.springframework.boot.autoconfigure.flyway.FlywayAutoConfiguration$FlywayConfiguration.configureIgnoredMigrations(FlywayAutoConfiguration.java:264)

The following method did not exist:

    'org.flywaydb.core.api.configuration.FluentConfiguration org.flywaydb.core.api.configuration.FluentConfiguration.ignoreMissingMigrations(boolean)'

The calling method's class, org.springframework.boot.autoconfigure.flyway.FlywayAutoConfiguration$FlywayConfiguration, was loaded from the following location:

    jar:file:/Users/donal/.gradle/caches/modules-2/files-2.1/org.springframework.boot/spring-boot-autoconfigure/2.7.2/f358e3f8ce01d3a26605fa23f9d3fd408726b033/spring-boot-autoconfigure-2.7.2.jar!/org/springframework/boot/autoconfigure/flyway/FlywayAutoConfiguration$FlywayConfiguration.class

The called method's class, org.flywaydb.core.api.configuration.FluentConfiguration, is available from the following locations:

    jar:file:/Users/donal/.gradle/caches/modules-2/files-2.1/org.flywaydb/flyway-core/9.0.1/b3c2b2ec888a69d2a759552c4678c6f1a12a037c/flyway-core-9.0.1.jar!/org/flywaydb/core/api/configuration/FluentConfiguration.class

The called method's class hierarchy was loaded from the following locations:

    org.flywaydb.core.api.configuration.FluentConfiguration: file:/Users/donal/.gradle/caches/modules-2/files-2.1/org.flywaydb/flyway-core/9.0.1/b3c2b2ec888a69d2a759552c4678c6f1a12a037c/flyway-core-9.0.1.jar

Action:

Correct the classpath of your application so that it contains compatible versions of the classes org.springframework.boot.autoconfigure.flyway.FlywayAutoConfiguration$FlywayConfiguration and org.flywaydb.core.api.configuration.FluentConfiguration

Flyway V9 introduced breaking changes that you can read about here
You will likely need to ask the Spring Boot maintainers to update to support the latest version of Flyway

It appears that Flyway 9.2.1 is compatible with the current version of Spring Boot, i.e. 2.7.3


Curriculum for beginner, intermediate & advanced tracks?

We've talked about this a lot in the past, but I think we need to come to a conclusion about how to proceed on this.  The issue here is that having a 2-3 day tutorial is not enough time to cover both beginner and intermediate topics.  One thought for discussion:
Thought: Beginner-level participation looks very different than intermediate- or advanced-level participation.  At the intermediate and advanced levels, participants can be expected to participate in a hackathon-like environment.  At the beginner level, participants do not have the tools (yet) to do anything like a hackathon.  This suggests the following:

Perhaps the goal of the beginner-level tutorial should be to get participants to the minimal level where they could contribute to and develop a hackathon project.  This would cover git, GitHub, beginner Python, Jupyter Notebooks.  This might be 1-2 days.
Perhaps the intermediate-level tutorial should focus on giving participants additional tools upon which they can find solutions via a hackathon project.  This might be tools like intake, xarray, dask, etc.  This might be 1-2 days.
Perhaps the advanced-level tutorial is just a hackathon.  This should be 2-3 days.

All told, this is a curriculum spanning 4-7 days.
Thought: Experience trying to accommodate all levels of experience in a single tutorial does not seem to work as effectively as we would like.  Namely, participants who start as beginners rarely are able to participate at the intermediate or advanced level in the same tutorial.  So, it seems to me that people need time to develop their knowledge and let the concepts "sink in."  This might suggest the following:

Perhaps the beginner-level tutorial precedes the intermediate-level tutorial by at least 1 week but possibly 2-4 weeks.
Perhaps the intermediate and advanced tutorials can be adjacent, such that 2-3 days are spend on technical topics followed by 2-3 days of hackathon.
Advanced-level participants would not need to show up for the intermediate topics section.
Advanced-level participants can be tapped as instructors.

This would allow for a 2-day beginner tutorial that might be followed by a week-long tutorial + hackathon about 2 weeks later.
Questions to Answer:

What do people think about this approach?
What would need to change with the material we have to make this possible?

I recently came across a great curriculum for an introduction to Python course and I thought I would share it here. My hope is that we can use the list below in conjunction with the official Python tutorial to come up with our own curriculum.

Data structures

Interactive Python
Variables — dynamic and strict typing
Blocks and indentation
Writing and executing programs in files
Conditionals
Basic types: None, boolean, numeric, string, list, tuple, dictionary, set
Loops
Sequences
Reading from and writing to files
Creating and working with complex data structures

Functions and functional programming

What is a function? Functions as objects
Writing functions
Return values, returning sequences
Function parameters
Variable function parameters with *args and **kwargs
Variable scopes in Python
Functional programming introduction (map, filter, etc...)
List comprehensions
Customizing sort by passing function arguments
Modules and packages

Objects

What is an object?
Classes and instances
Constructors and destructors
Instance attributes
Getters and setters
Class attributes
Attribute scoping rules
Inheritance
Exceptions

A few days ago, someone put in a FOIA request to the NSA for their Python training materials and they got back a 400-page PDF of their training course. The PDF resides here: https://nsa.sfo2.digitaloceanspaces.com/comp3321.pdf
The very first line of the pdf:

So, you're teaching the Python class. What have you gotten yourself into? You should probably take a few moments (or possibly a few days) to reconsider the life choices that have put you into this position.
😅

Since nbgallery is mentioned a lot in this printout, I presume that this is likely the same training material we heard about during the nbgallery talk a few weeks ago.
Having skimmed it.. This is a quality guide. It appears to be comprehensive - it's clearly meant for someone self-studying or who's very self-motivated.
Hopefully, this is going to be useful reference for our curriculum.

Nice!

Thanks @andersy005 I will take a closer look at this. I am currently creating a draft of a notebook that covers python topics without using any packages.


chore: deprecate Case2Camel

📑 Description

Summary by CodeRabbit

New Features

Updated command stub generation to use snake case formatting for placeholders, enhancing consistency across the application.

Bug Fixes

Improved matching logic in data processing by adjusting string transformation methods, which may impact case sensitivity and format handling.

Documentation

Added deprecation notices for older string transformation methods to guide users towards modern alternatives.

✅ Checks

[ ] Added test cases for my code

Great! Are we using these method other than this repo?

Yes, maybe, so I don't remove it directly.


Turn off Modem/GPS, Set MCU to sleep

Hi,
I'd like to build a GPS-Tracker based on the module. Is there any way to turn off the GSM-Modem and GPS-Receiver? I'd also like to put the MCU to timer based deep sleep. Is this possible?
Thanks

https://github.com/Ai-Thinker-Open/GPRS_C_SDK/blob/master/demo/pm/src/demo_pm.c

Thanks, but can you provide a brief explanation of what this function exactly does? Does it really power down the modem and the GNSS receiver? It seems like a lot of code besides the SDK is closed source. All I can find is binaries. Is there a way to get the full source code? My A9G is already on the way and I'd love to start developing as soon as it arrives. Thanks!


correct typos and improve refresh.yml documentation in README

Originally intended to only correct the obvious typos. But took a stab at improving the documentation for the configuration file as well as I had to customize it for my project.
Let me know if you just want a PR with just the obvious typos fixed.

Looks great! Thanks!


Cupcake website page content creation - Help/FAQ page

As a Cupcake website content creator

I need to: know what frequently asked questions our adopters have

so that I can: consolidate them and present them on the FAQ page.

Additional information

Let's create the content for the current release based on the v19a, Carbon website FAQ page and input from Linda, Wonil, and Jeff.

Acceptance criteria

[ ] A list of the questions published with markdowns
[ ] Reviewed the list with Linda, Wonil, and Jeff.
[ ] Content and design accepted by Linda.

@JennySanchez
FAQ page is ready for review!
Live link: https://deploy-preview-111--carbon-for-ibm.netlify.com/help/faqs

Our next step is to review the content with Linda and get her input on finalizing the content.

My feedback below in red.docx

@ljcarot Thank you for reviewing and making edits to the FAQ page content. It makes sense to me and I will make updates to the page.

@ljcarot FAQ page update completed and can be viewed on the Cupcake website.

@wonilsuhibm @jeffchew Please take a look and let me know if we missed anything. Thank you.


Generated enums and operations contain character names

When I update from 0.1.0 to 1.0.0.alpha.1 my enum value that used to be basic_image is now basic_hyphen_image string value from backend is basic_image
for schema:
          type: string
          nullable: false
          enum:
            - basic-video
            - basic-image

It also applies to Operations:
get_feed__session_ -> get_sol_feed_sol__lcub_session_rcub_
for schema:
/feed/{session}:
    get:
      tags:
        - Feed
      summary: Retrieve feed entries for the session

Hi @erikhric,
yes that's intentional, check out the proposal that changed the mapping: https://swiftpackageindex.com/apple/swift-openapi-generator/0.3.5/documentation/swift-openapi-generator/soar-0001
For the enum values, you'd need to change the raw values to only contain characters allowed in Swift identifiers if you want to avoid mapping special characters to words. But that might have impact on the API stability, if it's already shipped. There isn't a way to override this name.
For the operation names, you should override the operationId field in the OpenAPI document for each operation, and that's the name that gets used for the function name.
Overall, this is expected behavior so you'll just need to update your code.


endeavour: 42.0 -> 43.0

Description of changes
https://gitlab.gnome.org/World/Endeavour/-/compare/v42.0...43.0
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

project: Refactoring and cleaning up removes the background plugin and the todoist plugin, you can try remove libportal-gtk4, librest and json-glib and see if it still builds.

Build pass, looks good than before.

Could you please include the changes link in the commit message and split the file move into a separate commit so that Git can better detect the history?

It seems a litte difficult to me.

@ofborg build endeavour
Pushed the changes, also simplified the update script thanks to https://github.com/NixOS/nixpkgs/pull/193248. I guess re-creating the two commits will be faster than interactive rebase - edit in this case? :thinking:

Thank you! It's really helpful.


Use namespace scoping

https://github.com/ahmetsduru/quadcopter_simulator/blob/b99e3547c4e7605bed792276c67fa716b4358350/src/eom.cpp#L359
Use std::atan2.
In general use scoping even if the scope is obvious.

ok


Log is being used by Chia Plot Status

Remove when I try to delete a failed log I get "The file is being used by Chia Plot Status" error, I have to close it, delete the file, and open it again.
Also, there are some plot managers that moves the logs when they are finished, and if Chia Plot Status is open, they fail to move or delete their own logs

There is already a solution for this:
https://github.com/grayfallstown/Chia-Plot-Status#troubleshooting
Don't use this to delete finished log files or you will ruin ETA and warning threshold calculations.

Which plot managers move log files?

https://github.com/abueide/harry-plotter


Where can I find the documentation for nimble-1.4.0 and nimble-1.3.0?

It seems like the Mynewt nimble code (from version 1.1 to 1,5) and Mynewt BLE User Guide (from v1.1 to v1.0) follow the different versioning system. If I am developing on nimble v1.3 or 1.4, where can I find the exact documentation for these two versions? I am talking about the documentation hosted here, not the .rst docs hosted on GitHub, because it does not have the generated API docs.

Hi,
NimBLE is considered internal project of Mynewt and thus we don't provide explicit documentation for nimble versions.
So documentation is always for Mynewt (including BLE features).
I don't think we have explicit mapping for Mynewt<-> NimBLE version used anywhere in documentation but repository.yml [1] should allow for this.  eg  Mynewt 1.9.0 uses nimble 1.4.0
[1]  https://github.com/apache/mynewt-core/blob/master/repository.yml#L107


Verbose "not found version patterns" error

Current "not found version patterns" does not provide any clue about what response payload it is trying to parse.
I'd like it to throw some light about the parsing failure.

@varas Thank you for your contribution!


Some ideas for improving repository tooling and automation

Hello all,
I wanted to start a discussion about a few  repository tooling and automation ideas. Primarily helping and improving development experience.
Here are some ideas that I think are worth pursuing:

Cmake restructuring to break the project down into composable units. Maybe using Conan or other package manager for easier maintenance, easier composability with dependencies.

Adding a devcontainer to the project for easier developer experience.

Improving the CI and/or coverage automation.

Eager to hear everyone's thoughts and additions. Especially looking forward to having a pool of these tooling improvement ideas that we can then pursue based on their easy of implementation, value addition and impact.
CC: @hmartiro , @aaron-skydio

I think a devcontainer is probably the most self-contained and immediately useful idea - made a issue #276 for that.
There are some additional ideas in existing issues as well, under the infra tag (and relatedly the build tag, although that one has more minor issues and bugs and fewer interesting feature additions).
What are you envisioning in terms of restructuring things?  I'm not really familiar with Conan. I don't think we'd want to add something that would prevent or discourage users from including SymForce in vanilla CMake projects, or projects using some other build system that wraps CMake like colcon, but I'm not sure if any of the ideas you have in mind would do that.

Hi @aaron-skydio,
Sorry for the late reply. I agree, conan might be a little non popular option. I was thinking of general cmake improvements such as:

Splitting the code into more atomic pieces: both in directory structure which aligns with cmake submodules or sub-projects.
Adding mechanism where each of these submodules or these smaller building blocks can be compiled, unit-tested atomically.
Adding integration tests where multiple of these modules are combined together.

Yeah I'm generally on board with those ideas, although would want to talk through the specifics.  I think setting up a devcontainer is a good place to start, and will probably give you some exposure to how the build and dependencies are set up as well, then we can go from there

Thanks @aaron-skydio . Sounds good.


Spreads saved as "()" empty string by default

When a user enters no title, it saves it as an empty string "".  Should have a default value in the field and a check for empty strings.

Text box now has a default value and in the case of an empty string, they default to "My Custom Set".


[cl4] post.deleted - Post object has no attribute deleted

Describe the bug
CL4 branch bug. Post object does not have the attribute "deleted", preventing fetching of new posts.
To Reproduce
Steps to reproduce the behavior:

Authenticate API
Make a POST request to /v1/home with a new post as content
Make a GET request to /v1/home
Error...

Expected behavior
After making a post with POST /v1/home and using GET /v1/home, a array of post objects should populate.
Logs
Error while handling error: 'NoneType' object has no attribute '__name__'
Stack: Traceback (most recent call last):
  File "C:\Users\Mike Renaker\AppData\Local\Programs\Python\Python311\Lib\site-packages\sanic\app.py", line 968, in handle_request
    response = await response
               ^^^^^^^^^^^^^^
  File "D:\meower-server\meower\src\api\home.py", line 30, in v1_get_feed
    fetched_posts = posts.get_feed(request.ctx.user, before=request.args.get("before"), after=request.args.get("after"), limit=int(request.args.get("limit", 25)))
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "D:\meower-server\meower\src\entities\posts.py", line 346, in get_feed
    if post.deleted or (post.id in post_ids):
       ^^^^^^^^^^^^
AttributeError: 'Post' object has no attribute 'deleted'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:\Users\Mike Renaker\AppData\Local\Programs\Python\Python311\Lib\site-packages\sanic\handlers.py", line 144, in response
    response = self.default(request, exception)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "D:\meower-server\meower\src\api\errors.py", line 23, in default
    "error": exception.error,
             ^^^^^^^^^^^^^^^
AttributeError: 'AttributeError' object has no attribute 'error'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:\Users\Mike Renaker\AppData\Local\Programs\Python\Python311\Lib\site-packages\sanic\app.py", line 813, in handle_exception
    response = self.error_handler.response(request, exception)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\Mike Renaker\AppData\Local\Programs\Python\Python311\Lib\site-packages\sanic\handlers.py", line 153, in response
    error_logger.exception(response_message, handler.__name__, url)
                                             ^^^^^^^^^^^^^^^^
AttributeError: 'NoneType' object has no attribute '__name__'

You just need to replace '.deleted' with '.deleted_at'

Will patch in new commit

Applied in https://github.com/meower-media-co/Meower-Server/commit/0243e64de5fd4cc6edceb44b8238bd78742f3ff3, closing


[Release-1.27] - Access pods running on k3s via multiple interfaces

Backport fix for Access pods running on k3s via multiple interfaces

#9536

typo when backporting.


Fix #6603: PInvokeStackImbalance error caused by incorrect signature

What does the pull request do?

Fixes #6603
What is the current behavior?

When running WindowsInteropTest in Debug Mode in VS2022, a Managed Debugging Assistant comes up indicating that the call stack has become unbalanced due. This is due to an improper signature on the WindowsCreateString function.

What is the updated/expected behavior with this PR?

The exception no longer comes up.
How was the solution implemented (if it's not obvious)?

When PreserveSig=false, a function that natively returns an HRESULT and has no final [out] parameter should instead be marked as void (since the HRESULT value gets translated into an exception if needed rather than being returned). See:
https://docs.microsoft.com/en-us/dotnet/api/system.runtime.interopservices.dllimportattribute.preservesig?view=net-6.0
Checklist

[ ] Added unit tests (if possible)?
[ ] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/Documentation with user documentation

Breaking changes

Obsoletions / Deprecations

Fixed issues
Fixes #6603

 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: kivarsen sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

You can test this PR using the following package version. 0.10.999-cibuild0020047-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]


Accept haddockHtmlTest test output for ghc-9.0

Refs #1350

@monoidal Could you please rebase on top of current ghc-9.0? The CI is fixed with 62d763f

@Kleidukos I don't have permission to forcepush.

Reopening as #1355.


Using decimal.Big as a map key

Hello.
I would like to use decimal.Big as a map key. At the moment it seems to be impossible. Is there any work-around to allow decimal.Big to be a map key?

I would convert the decimal to a string and store that. You might have to adjust for differing scales. E.g., 410^1 vs 4010^0.
For reference: the moment, slices can't be used as map keys and decimal.Big contains slices by virtue of using big.Int. Pointers can be used in maps, but Go implements equality by comparing the pointers, not the type behind it. And, at any rate, you likely wouldn't want to compare decimal.Bigs using == because even if (*decimal.Big).Cmp returns zero, the structs might have different memory layouts (e.g., scales like previously mentioned).
Further, there's no way to define custom equality for a map (e.g., (*T).Equal(T) bool or (*T).Cmp(t) int).

Thank you for detailed explanation and for the great decimal library!


Is there any plans to support the generation of code from YML or graphql schema for rest-layer?

The aim is to improve development efficiency

No plan on my side but if someone wants to contrib a generator for that, welcome.

Cleaning up the issue tracker, will close this question.


merge release 3.0 to release 3.1

Merge release 3.0 to 3.1

@bb7133 The CI is complaining, PTAL

LGTM


typesafe hooks

TL;DR

Added custom error class ImageStorageError
Modified useImageStorage hook to include timestamp in Image record

What changed?

Added custom error class ImageStorageError
Modified useImageStorage hook to include timestamp in ImageRecord

How to test?

Run tests for storing and fetching images

Why make this change?

Improve error handling with custom error class
Enhance functionality by adding timestamp to ImageRecord

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#10
#9  👈
#8
#7
#6
#5
#4
#3
features/lit-ipfs

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @VPhung24 and the rest of your teammates on  Graphite

Merge activity

Mar 22, 8:01 PM EDT: @VPhung24 started a stack merge that includes this pull request via Graphite.


Message objects in Message Commands lack some of the information, like guild_id and referenced_message

Steps to reproduce

Install the latest versions of hikari and hikari-lightbulb
Save this code:

import hikari
import lightbulb

TOKEN = "your_token" # replace with your token

bot = lightbulb.BotApp(
    token=TOKEN,
    intents=hikari.Intents.ALL_UNPRIVILEGED | hikari.Intents.MESSAGE_CONTENT | hikari.Intents.GUILD_MEMBERS
)

@bot.command
@lightbulb.command(name="Test", description="Test")
@lightbulb.implements(lightbulb.MessageCommand)
async def test_command(ctx: lightbulb.MessageContext):
    message: hikari.Message = ctx.options.target
    await ctx.respond(
        f"""```\n"""
        f"""{message.content=}\n"""
        f"""{message.author=}\n"""
        f"""{message.type=}\n"""
        f"""{message.guild_id=}\n"""
        f"""{message.member=}\n"""
        f"""{message.referenced_message=}\n"""
        f"""```"""
        )

bot.run()

Run the code to start your bot. Invite it to a server.
Create a message, and then a reply to your message
Use the Test message command on the reply (The message menu > “Apps” > “Test”)
See the result

Expected result
The message should display values of all the attributes correctly.
Actual result
message.guild_id, message.member and message.referenced_message are None. The message type is REPLY, as intended, but the referenced message still has no value
System info
hikari-lightbulb (2.3.5)
hikari (2.0.0.dev125) [8ff87e57]
located at C:\Users\boyko\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.11_qbz5n2kfra8p0\LocalCache\local-packages\Python311\site-packages\hikari
CPython 3.11.9 MSC v.1938 64 bit (AMD64)
Windows Ajno_tekkomp 10 10.0.22631 AMD64 AMD64 Family 23 Model 160 Stepping 0, AuthenticAMD

Further info

Checklist

[X] I have made sure to remove ANY sensitive information (bot token, passwords, credentials, personal details, etc.).
[X] I have searched the issue tracker and have made sure it's not a duplicate. If it is a follow up of another issue, I have specified it.

This is not a lightbulb bug - this entirely depends on what data discord sends in the command interaction.


Robot connection times out if Pepper initially not awake

Fixed by simply incrementing the timeout value for the ajax function call in the frontend in this commit: https://github.com/frietz58/WoZ4U/commit/833f1cf24f4b31d11d9c08ff182ca7c5f59e3277


If no return after /* ... */, generate wrong js

/*
aa
*/var c = 1;

generate
/*
aa
/*
aa
 var c = 1;

This is a duplicate of #1714, which we've since fixed. TypeScript 1.4.2, and TypeScript 1.5-alpha, should both have the correct behavior.

Sorry I referred to this as a duplicate; in fact, this might not be a duplicate, but it's since been fixed in the latest of TypeScript 1.4 and 1.5 alpha.


Update for SE-0193

@_inlineable => @inlinable
@_versioned => @usableFromInline
@inlinable @usableFromInline => @inlinable

@swift-ci Please test Linux

Why not rever this? https://github.com/apple/swift-corelibs-foundation/pull/1502 :wink:

@ikesyo sorry I wasn't aware you made an earlier attempt at fixing this. As you noted though my change has an additional cleanup. Now that master has been merged into swift-4.2-branch on the Swift side this PR should be good to go.


In DoEntityReaction, in the Solution class, the foreach loop needs to use _contents.ToArray() instead of just _contents for cases where a reaction removes all of a reagent from a solution.

In DoEntityReaction, in the Solution class, the foreach loop needs to use _contents.ToArray() instead of just _contents for cases where a reaction removes all of a reagent from a solution.


Text on button is not visible

What happened?
Text on the Know More button in Home page is not visible.

How can we reproduce this bug?
I would like to resolve this issue by correcting some code in the CSS file, and make the text visible.
Desktop Information (Optional)
No response
Urgency (Optional)
High priority
Record

[X] I agree to follow this project's Code of Conduct
[X] I have checked the existing issues
[X] I'm a GSSoC'23 contributor
[X] I want to work on this issue

Resolved


How to highlight several different lines?

Hi.
I need to highlight several lines by line number. How can i achieve this with ng2-ace-editor?
There is method highlightLines() at https://ace.c9.io/#nav=api&api=edit_session.
Can we use it?
I am new to ace editor so any help/example appreciated.

Hi,
I have completed my exemple with your question.
With @ViewChild you can access to the component.
Follow my exemple https://github.com/fxmontigny/ng2-ace-editor/commit/11a9c4025465190e2c8e35081e09e51fb32e7848

Github says file not found on link:
https://github.com/fxmontigny/ng2-ace-editor/commit/11a9c4025465190e2c8e35081e09e51fb32e7848

Sorry I forgot to push my commit.
Try again.

Thank you!
I found another way to access Range through brace here. Take a look at code that works for me:
import { Component, ViewChild, AfterViewInit } from '@angular/core';

import 'brace';
import 'brace/theme/solarized_dark';
import 'brace/mode/yaml';
import { AceEditorComponent } from 'ng2-ace-editor';

@Component({
  moduleId: module.id,
  selector: 'm-file-editor',
  templateUrl: 'file-editor.component.html',
  styleUrls: ['./file-editor.component.css'],

})
export class FileEditorComponent implements AfterViewInit {

  @ViewChild('editor') editor: AceEditorComponent;

  constructor() {
  }

  ngAfterViewInit() {
    this.editor.getEditor().$blockScrolling = Infinity;

    this.editor.setOptions({
      readOnly: false,
      highlightActiveLine: true,
      highlightGutterLine: true,
    });

    this.editor.setTheme('solarized_dark');

    this.editor.setMode('yaml');

    let Range = require('brace').acequire('ace/range').Range;

    this.editor.getEditor().session.addMarker(new Range(2, 0, 2, 1), 'myMarker', 'fullLine', true);
  }
}

Perfect. I'm using the same solution ;)
https://github.com/fxmontigny/ng2-ace-editor/blob/master/examples/basic/src/app/app.component.ts


For #5: added rultor support, added badges and updated roadmap.

For #5: added rultor support, added badges and updated roadmap.

@rultor merge


dijkstra

project work
Description of Change

Checklist

[ ] Added description of change
[ ] Added file name matches File name guidelines
[x] Added tests and example, test must pass
[x] Added documentation so that the program is self-explanatory and educational - Doxygen guidelines
[ ] Relevant documentation/comments is changed or added
[ ] PR title follows semantic commit guidelines
[ ] Search previous suggestions before making a new one, as yours may be a duplicate.
[ ] I acknowledge that all my contributions will be made under the project's license.

Notes:

collection of JavaScript and TypeScript data structures and algorithms for education purposes. Source code bundle of JavaScript algorithms and data structures book
set

Implementation of Dijkstra algorithm in a GUI python application.


added Asteroids 3D Game 🌠

PR Description 📜
The code provided is a JavaScript game that implements a 3D software renderer for rendering asteroids. The game features a player-controlled spaceship that can move and shoot bullets. The goal of the game is to destroy the asteroids by shooting them with bullets. The asteroids move around the screen and can collide with the player's spaceship. The game also includes explosions and visual effects.
Fixes #2400

Mark the task you have completed ✅

[X] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[X] I have performed a self-review of my own code or work.
[X] I have commented my code, particularly in hard-to-understand areas.
[X] My changes generates no new warnings.
[X] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[X] I have added screenshot for website preview in assets/images
[X] I have added entries for my game in main README.md
[X] I have added README.md in my folder
[X] I have added working video of the game in README.md (optional)
[X] I have specified the respective issue number for which I have requested the new game.

Add your screenshots 📸

Working Video 📽
https://github.com/kunjgit/GameZone/assets/100849696/c1ef28c3-d6ab-4e2a-bcb2-20b07590372d

Thank you soo much for contributing to our repository 💗

Thank you @sabhisharma-ise ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

@gurjeetsinghvirdee Can you review this PR!

Thank you  @sabhisharma-ise , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀


pythonPackages.cvxpy: add explicit numpy/scipy dependencies

Motivation for this change
Add explicit numpy/scipy dependencies, based on https://www.cvxpy.org/install/#install-from-source.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip". Says NO DIFF.
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Note: borg won't build it due to upstream unfree mkl dependency, which will be fixed in #84124. Builds locally.
nixpkgs-review pr 84120
https://github.com/NixOS/nixpkgs/pull/84120
6 package built:
python37Packages.cvxpy python37Packages.qiskit-aer python37Packages.qiskit-ignis python38Packages.cvxpy python38Packages.qiskit-aer python38Packages.qiskit-ignis

Can you send a 20.03 backport PR as well?

@bhipple same for cvxpy, not in release-20.03.


Add BEF module

Add Better Exposed Filters https://www.drupal.org/project/better_exposed_filters to Openfed (disabled by default)

Added.
Enabling this module requires manual actions to download the jquery.ui.touch-punch.min.js library


Theme is not being installed when using this deployment action

When my site is being deployed with this action, the github theme is no longer installed.

Solved! ✅
I needed to be tracking Gemfile.lock (and I'm assuming Gemfile as well). When the runner loads the cached gemfile (uses: actions/cache@v2), if no gemfile is found, I'm assuming it doesn't install requirements? And skips? Either way, tracking these 2 files (by removing from gitignore) solved it for me.


Some development setup of Redis have a single Master and no Sentinal …

…Slaves.
Calling "sentinel slaves "  returns  (empty list or set)
This causes a NullPointerException in SentinelConnectionManager.  This fix addresses that bug.

Duplicate to #226
:)

Thank you!


Upgrade tap to v15

We were affected by 2 major changes in tap v15:

Separate tap.has (tap.include()) from tap.match, so these are distinct.
It was required to change tap.include() to tap.match() as next code is behaves on v15 like this:

tap.test('test 15', async (tap) => {
  const string = 'some text expected'
  tap.include(string, 'expected') // will fail
  tap.match(string, 'expected') // will pass
})

--check-coverage on by default.
Tap started to fail by default in case coverage is under 100%.
So I added few more tests to be in "100% Coverage Club 🏅"

Related to #89

I had a bit of trouble getting the tests to pass. Even when I pulled from Rodion's branch there were issues.

For it was required to update git version due to git init --initial-branch command was failing.

many thanks @rodion-arr , I'm good again.

:tada: This PR is included in version 0.6.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add Errorf

Thank you. Before I can merge this, please add tests and examples.

I know this is late to the dance, but why not have optional arguments to New and treat it as printf?

@paulstuart probably for the same reason as https://github.com/pkg/errors/issues/6#issuecomment-214054015
Please open a new issue to discuss this, I'm about to merge this PR and this discussion may be lost.

@davecheney the existing solution is fine. It just seemed like the idea was a clean and minimal enhancement. My itch is scratched. Keep doing the good you do.

Hmm, so New() could be redefined as New(string, ...string) but I'm not sure how useful that would be, if you want more complicated formatting, Errorf would probably be the right tool for the job.


update(cmake): updated libs to latest 0.10.1 tag.

What type of PR is this?
/kind feature
Any specific area of the project related to this PR?
/area build
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
update(cmake): updated libs to 0.10.1 tag.

/milestone 0.34.0

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [FedeDP]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP, jasondellaluce, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [FedeDP,jasondellaluce,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Cell editing broken

Hey there,
I just tried to upgrade to the new major 3 version. However, when trying to edit a cell it looks like the approve button is always disabled.
You can find an example here: https://codesandbox.io/s/material-table-starter-template-forked-xb2n6
Am I doing something wrong? Maybe I missed adding an additional function?
Thanks
Matthias

This is fixed in code but the release is not yet through. Will be fixed with the next release

Great thanks :-)