pinocchio::sdf::buildModel error

I'm using pinocchio3-preview and trying to load a robot model with function "pinocchio::sdf::buildModel" .
Part of my code is:
Model model;
pinocchio::urdf::buildModel(urdf_filename,model);
PINOCCHIO_STD_VECTOR_WITH_EIGEN_ALLOCATOR(RigidConstraintModel) contact_models;
pinocchio::sdf::buildModel(urdf_filename,model,contact_models);
But a segmentation fault come out in parseRootTree， const std::string childName=
jotingElement->GetElement("child")->Getstd::string();;
Maybe i miss something or the model i used is not correct, I  tried the model from here:
models.zip, from #1839;
and here:
https://github.com/osrf/gazebo_tutorials/tree/master/kinematic_loop/four_bar_split_fixed_sdf/model.sdf
Both of them come out the same error above.
Is there a example of sdf model?
Many thanks

Please provide a reproducible example and the way to compile and launch it.

pin_c_test_.zip
cd build
cmake ..
make

@areofire Did you find a fix for your issue?

Not yet. I have spend much time on installing pin-view3, but all failed. As in example above, to use pinnocchio3, i have to include relevant  file in my project.
I got  a pinocchio::sdf::buildModel error and  still working on fixing it.

Maybe the model i used is wrong, there wasn't a "static " parameter in graph.mapOfJoints.

Could you give an example of sdf file, thank you !

@jcarpent


A few tweaks after using it on my machine

Let me know if you don't like any of the changes.

Thanks for the proposal and correction. Merged!


ov2640 image issue

i use the master repo of the project and  the code is running success. but i can not get the correct from the http web server , the image  and video is messy color block.
i will give debug log and image screenshot later.

hi,me too,but i solve it. can you make menuconfig error !

hi,me too,but i solve it. can you make menuconfig error !

me too, can u share the solution?


Fix upload bug in editor

Closes #151.

@mRcfps  You just a model worker! DDD 💇♂

@mRcfps You already a Github Actions Master 🚶 🚶


Question: Removing DB entries?

Thanks for the great plugin! It's proving to be critical in a couple of workflows I'm setting up, both email and the DB.
The DB use case (for now) is to use for logging as I'm building my first module and I want plenty of easily front-end-readable (with login) data for my other admins to read. (As I'm certain my plugin/module will need fixes of all kinds early on :) )

So, though I don't think it will become an issue any time soon, I figured it was best to ask/understand up front now: short of mysql in to truncate the table, is there any way/plans to dump/delete DB notifications? I see they can be marked as read, but not sure that implies any cleanup? (Or I missed it, certainly possible.)
I'm just excited I've gotten this far, but hopefully this will work well enough that I should consider such things for the future :)
Thanks!

Did you ever come up with a workaround for this?

Did you ever come up with a workaround for this?

I actually ended up going a completely different direction, learned how to work with ActiveRecord directly and let myself assume the danger :) But I do love this plugin and I think it's also great code to learn from!

@allenpieper @rtgoodwin I have a simple CLI command that I run via a cron job that deletes read notifications that are older than X days old.
use percipioglobal\notifications\records\NotificationsRecord;

  /**
   * Delete notifications older than X days
   */
  public function actionDeleteReadNotifications($time = "-1 month") {
    $expiration = DateTimeHelper::toDateTime(strtotime($time))->format('Y-m-d H:i:s');
    $notifications = NotificationsRecord::find()
      ->andWhere('read_at IS NOT NULL')
      ->andWhere(['<', 'read_at', $expiration]);

    $count = $notifications->count();
    echo "Found $count notifications.\n";

    if ($count) {
      foreach ($notifications->all() as $notification) {
        $this->stdout(" - Deleting notification {$notification->id} ... ");
        $notification->delete();
        $this->stdout('done' . PHP_EOL, Console::FG_GREEN);
      }

      Craft::warning('Notifications deleted: ' . $count, __METHOD__);
    }

    $this->stdout("Deleted $count read notifications." . PHP_EOL);

    return ExitCode::OK;
  }

Thank you @codyjames for your suggestion. We've integrated your solution in our (release 1.2.2)[https://github.com/percipioglobal/craft-notifications/releases/tag/1.2.2] of today.
The default time is set to -1 month. If you want a custom time frame, provide the date within the strtotime PHP restrictions.
//default
./craft notifications/remove-notifications/index

//custom
./craft notifications/remove-notifications/index --time="-3 months"


[cit-551] fix tarpaulin tests

Proposed changes
Fix the failing tarpaulin tests. The issue was when tests were run in tarpaulin using "sudo" in the tests were failing. This PR makes using the "sudo" an optional parameter. i.e do not use sudo for tests.
Types of changes
What types of changes does your code introduce to thin-edge.io?
Put an x in the boxes that apply

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)
[ ] Documentation Update (if none of the other choices apply)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Paste Link to the issue

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[ ] I have read the CONTRIBUTING doc
[ ] I have signed the CLA (in all commits with git commit -s)
[ ] I ran cargo fmt as mentioned in CODING_GUIDELINES
[ ] I used cargo clippy as mentioned in CODING_GUIDELINES
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

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

Codecov Report

Merging #423 (3249975) into main (cebb8e3) will decrease coverage by 1.01%.
The diff coverage is 23.84%.

@@            Coverage Diff             @@
##             main     #423      +/-   ##
==========================================
- Coverage   63.98%   62.97%   -1.02%
==========================================
  Files         106      106
  Lines        6820     6709     -111
==========================================
- Hits         4364     4225     -139
- Misses       2456     2484      +28

Impacted Files
Coverage Δ

mapper/tedge_mapper/src/collectd_mapper/monitor.rs
0.00% <0.00%> (ø)

sm/tedge_agent/src/agent.rs
0.00% <0.00%> (ø)

sm/tedge_agent/src/main.rs
0.00% <ø> (ø)

tedge/src/cli/connect/command.rs
0.00% <0.00%> (ø)

mapper/tedge_mapper/src/collectd_mapper/batcher.rs
72.00% <30.00%> (-8.36%)
:arrow_down:

sm/plugin_sm/src/plugin.rs
54.70% <50.00%> (-0.66%)
:arrow_down:

...apper/tedge_mapper/src/collectd_mapper/collectd.rs
88.28% <83.33%> (-0.61%)
:arrow_down:

sm/plugin_sm/tests/plugin.rs
98.83% <100.00%> (+0.01%)
:arrow_up:

mapper/thin_edge_json/src/group.rs
84.96% <0.00%> (-5.23%)
:arrow_down:

common/mqtt_client/src/lib.rs
26.00% <0.00%> (-1.84%)
:arrow_down:

... and 1 more

Continue to review full report at Codecov.

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

From my perspective, I'm fine with the code. However, I still don't understand right why it failed on the first place. Can we maybe also add a comment that we circumvent sudo for testing purposes?


helm template: display the default value of --kube-version in help message

This PR improves to display the default value of --kube-version in help message of helm template command.
--kube-version string    kubernetes version used as Capabilities.KubeVersion.Major/Minor (default "v1.7.0")

Hey! Looks like CI's failing on this one. Once it's fixed up we'd be happy to take a look. Thanks!


[Bug] Calendar not working

Log mode enabled.
Error: System.Net.Http.HttpRequestException: Response status code does not indicate success: 403 (Forbidden).
at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode()
at CRD.Utils.HttpClientReq.SendHttpRequest(HttpRequestMessage request)
Response: Just a moment...Enable JavaScript and cookies to continue
No days found in the HTML document.

It got fixed when I changed the stream endpoint to chrome.

that has no impact on the calendar - you can also just use the custom calendar that is more reliable


Handle OneToOneFields in opensearch

Description of change
For OneToOneFields in Django, getting the related object, e.g. interaction.activity returns the actual object itself and not a queryset. This causes an error with the Opensearch sync where it expects to use values_list and also expects to filter which works for ForeignKey fields as they return a queryset.
Checklist

[ ] Has this branch been rebased on top of the current main branch?
[ ] Is the CircleCI build passing?

Closed as decided to revert back to ForeignKey from OneToOne.


Update Readme.md

PR Description 📜
This PR addresses issue, which involves improving the user experience and presentation of the Candy_Match_Saga project by replacing the link to the link with an image. The steps taken include capturing a new screenshot of the game, adding it to the repository, and updating the README.md file to display this image directly.
Fixes #3852

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
[ ] I have added entries for my game in main README.md
[ ] I have added README.md in my folder
[ ] 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(Optional) 📸
BEFORE CHANGES:

AFTER CHANGES :

@kunjgit , Thank you!

Thank you soo much for contributing to our repository 💗

Thank you  @Bindusree1515 , 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🚀


Log better message when connection was evicted or dead.

Closes https://github.com/brettwooldridge/HikariCP/pull/842

Coverage decreased (-0.01%) to 75.868% when pulling d3c859bdae0314bccfc169eb010bce1f4343305a on johnou:evicted_or_dead into 534e50484011161cacc1193cd84edcb3c03d1650 on brettwooldridge:dev.

@brettwooldridge ptal, let me know if further changes are required.

@johnou Thanks for the contribution. 🥇

@johnou HikariCP v2.7.2 containing this fix has been released.

ping @wvuong


Make warnings then first iotest Segmentation fault

Setup
Raspberry Pi 5 4GB
Raspbian/Debian 12 Bookworm 64bit
Home Automation Board v4.0
Test cable connected
Latest ioplus checkout v1.3.5
Issue - Make warnings
kev@garage-pi:~/ioplus-rpi $ sudo make install
[Compile] src/ioplus.c
src/ioplus.c: In function ‘doOwbIdGet’:
src/ioplus.c:2513:22: warning: format ‘%llx’ expects argument of type ‘long long unsigned int’, but argument 2 has type ‘uint64_t’ {aka ‘long unsigned int’} [-Wformat=]
 2513 |         printf("0x%llx\n", romID);
      |                   ~~~^     ~~~~~
      |                      |     |
      |                      |     uint64_t {aka long unsigned int}
      |                      long long unsigned int
      |                   %lx
[Compile] src/comm.c
[Compile] src/thread.c
[Compile] src/gpio.c
[Compile] src/opto.c
[Compile] src/tests.c
[Link]
[Install]
chown: warning: '.' should be ':': ‘root.root’
kev@garage-pi:~/ioplus-rpi $

Issue - First iotest run
Then first run of iotest fails, followed by reltest which works then second run of iotest then works:
kev@garage-pi:~/ioplus-rpi $ ioplus 0 iotest 2
Segmentation fault
kev@garage-pi:~/ioplus-rpi $ ioplus 0 reltest
Are all relays and LEDs turning on and off in sequence?
Press y for Yes or any key for No....y
Relay Test ............................ PASS
kev@garage-pi:~/ioplus-rpi $ ioplus 0 iotest 2
DAC 1 to ADC 4 @2V...PASS
DAC 1 to ADC 4 @0V...PASS
DAC 2 to ADC 3 @2V...PASS
DAC 2 to ADC 3 @0V...PASS
DAC 3 to ADC 2 @2V...PASS
DAC 3 to ADC 2 @0V...PASS
DAC 4 to ADC 1 @2V...PASS
DAC 4 to ADC 1 @0V...PASS
DAC 1 to ADC 8 @2V...PASS
DAC 1 to ADC 8 @0V...PASS
DAC 2 to ADC 7 @2V...PASS
DAC 2 to ADC 7 @0V...PASS
DAC 3 to ADC 6 @2V...PASS
DAC 3 to ADC 6 @0V...PASS
DAC 4 to ADC 5 @2V...PASS
DAC 4 to ADC 5 @0V...PASS
kev@garage-pi:~/ioplus-rpi $

Thanks!

Thanks for the report we will solve them in a near future, we are little sort on resources right now.
Thank you for your patience


Use type given by quint to build lambda bodies

Hello :octocat:
Fixes https://github.com/informalsystems/quint/issues/1393
The issue happened because we were only using the types given by Quint in the type map to annotate parameters, but not the result type of lambdas. This way, there was a mismatch in variable names on Apalache type inference (used for the body) and Quint type inference (used for the parameters).
This PR ensures that we always use Quint types.

[X] Tests added for any new code
[X] Ran make fmt-fix (or had formatting run automatically on all files edited)
[X] Documentation added for any new functionality
[x] Entries added to ./unreleased/ for any new functionality

This PR ensures that we always use Quint types.

Just to be clear: we have always been using quint types, it's just a matter of where we were sourcing those types from.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 78.90%.  Consider uploading reports for the commit 3dac602 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2856      +/-   ##
==========================================
+ Coverage   78.89%   78.90%   +0.01%
==========================================
  Files         467      467
  Lines       15956    15959       +3
  Branches     2625     2631       +6
==========================================
+ Hits        12588    12592       +4
+ Misses       3368     3367       -1

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


Color and layout fixes and theming simplification.

Always include the expander in the state tree layout so that keys at the same level always line up.
Always apply a theme class to  to simplify theming.
Remove all app.css theme overrides.
Move all single-use PostCSS variable values to the reference site.
Remove all unused PostCSS variables.
Correct tab menu light theme styles.
Move the Router Tree outside of the , which belongs to the Component Tree.
Remove unused node-item styles.
Move some component-specific styles from base.css to appropriate component css files.
Fix light theme colours.
Use ViewChild and element refs in Header instead of querySelector and global ids.
Wrap theme selector menu radio labels around their corresponding radio inputs so that clicking them selects the corresponding radio button.
Remove unnecessary null check on event.target in Header.resetIfSettingOpened(), since every onclick event has a non-null target element.
Use .transparent instead of .invisible on non-expandable state editor nodes, to prevent mouse events from being emitted.

@xorgy UI changes looks good few things Show HTML elements is not working

@sumitarora strangely, the CRX build seems to be of an older version. There may be some state which is preventing it from building the new version.

@sumitarora I just tested the CI CRX from this, and it is functioning as expected. The Show HTML elements toggle is working as well.

@xorgy LGTM :shipit:


Adds login/logout functions for generating and destroying Matrix Tokens

I found it annoying that I had to steal a token from another matrix client session or manually generate a token with the matrix REST API.
This PR allows you to login and logout to create or destroy sessions/tokens respectively.

Thank you, that looks great!


Add feature for each input of a mux

Example:
CLBLM_L.SLICEM_X0.ALUT.DI1MUX.AI 00_00
CLBLM_L.SLICEM_X0.ALUT.DI1MUX.BDI1 !00_00
CLBLM_L.SLICEM_X0.BLUT.DI1MUX.BI 00_20
CLBLM_L.SLICEM_X0.BLUT.DI1MUX.DI !00_20

This makes it easier to read, and will allow detecting conflicts.

A grep inside https://github.com/SymbiFlow/prjxray-db/blob/master/artix7/segbits_clblm_l.db gives;
CLBLM_L.SLICEM_X0.ALUT.DI1MUX.AI 00_00
CLBLM_L.SLICEM_X0.BLUT.DI1MUX.BI 00_20
CLBLM_L.SLICEM_X0.CLUT.DI1MUX.CI 01_43

Should this really be;
CLBLM_L.SLICEM_X0.DI1MUX.AI 00_00
CLBLM_L.SLICEM_X0.DI1MUX.BI 00_20
CLBLM_L.SLICEM_X0.DI1MUX.CI 01_43

This seems to be done by the https://github.com/SymbiFlow/prjxray/tree/master/fuzzers/019-clb-ndi1mux fuzzer...

https://github.com/SymbiFlow/prjxray/tree/master/fuzzers/019-clb-ndi1mux/minitest has some more comments?

BTW If it is the missing zero bits -- then bits.dbf file is what should be used I think?
See https://github.com/SymbiFlow/prjxray/blob/36e6290ec6638f88962d23582a3c5329e6d665d3/fuzzers/036-iob-ologic/bits.dbf#L1-L3 and https://github.com/SymbiFlow/prjxray/blob/36e6290ec6638f88962d23582a3c5329e6d665d3/fuzzers/036-iob-ologic/Makefile#L9-L11

A grep inside https://github.com/SymbiFlow/prjxray-db/blob/master/artix7/segbits_clblm_l.db gives;
CLBLM_L.SLICEM_X0.ALUT.DI1MUX.AI 00_00
CLBLM_L.SLICEM_X0.BLUT.DI1MUX.BI 00_20
CLBLM_L.SLICEM_X0.CLUT.DI1MUX.CI 01_43

Should this really be;
CLBLM_L.SLICEM_X0.DI1MUX.AI 00_00
CLBLM_L.SLICEM_X0.DI1MUX.BI 00_20
CLBLM_L.SLICEM_X0.DI1MUX.CI 01_43

This is wrong, the current definition is correct, we are missing the inverted versions.

So for the ADI1MUX both BDI1 and the BMC31 values are missing?

CLBLM_L.SLICEM_X0.ALUT.DI1MUX.AI     00_00
CLBLM_L.SLICEM_X0.ALUT.DI1MUX.BDI1  !00_00
CLBLM_L.SLICEM_X0.ALUT.DI1MUX.BMC31  ?????

https://github.com/SymbiFlow/prjxray/tree/master/fuzzers/019-clb-ndi1mux/minitest

So for the ADI1MUX both BDI1 and the BMC31 values are missing?

CLBLM_L.SLICEM_X0.ALUT.DI1MUX.AI     00_00
CLBLM_L.SLICEM_X0.ALUT.DI1MUX.BDI1  !00_00
CLBLM_L.SLICEM_X0.ALUT.DI1MUX.BMC31  ?????

https://github.com/SymbiFlow/prjxray/tree/master/fuzzers/019-clb-ndi1mux/minitest

 GitHub**SymbiFlow/prjxray**Documenting the Xilinx 7-series bit-stream format. - SymbiFlow/prjxray

No, as a said above, the database is correct.  There is no bit at all for the BMC31 or BDI1 port of the mux.  The likely table is:
SRL -> ADI1MUX.BMC31
RAM -> ADI1MUX.BDI1
ADI1MUX.AI -> ADI1MUX.AI

So, this would be the real info?
CLBLM_L.SLICEM_X0.ALUT.DI1MUX.AI              00_00
# Slice configured as SRL == BCM31, RAM == BDI1
CLBLM_L.SLICEM_X0.ALUT.DI1MUX.BDI1_OR_BMC31  !00_00

So, this would be the real info?
CLBLM_L.SLICEM_X0.ALUT.DI1MUX.AI              00_00
# Slice configured as SRL == BCM31, RAM == BDI1
CLBLM_L.SLICEM_X0.ALUT.DI1MUX.BDI1_OR_BMC31  !00_00

Yes

@litghost Is this done now with #900 or do we need a list of other muxes which need to be done?

I only added bits for the ADI mux, I believe there are others.  For example, I know the CARRY [ABCD]CY mux needs this treatment.

I opened #939 to get someone to go through and figure which other muxes need this treatment (and then hopefully fix them).
Closing this issue.


fix tests for FileCheck behaviour

What's in this pull request?

Resolved bug number: (SR-)

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    OS X platform               | @swift-ci Please test OS X platform
    Linux platform              | @swift-ci Please test Linux platform

Note: Only members of the Apple organization can trigger swift-ci.

FileCheck does not support the combination negation.  These tests were incorrect
and silently passing rather than checking what they intended.  The changes in
the DAG tests are due to the fact that they ensure that the order is matched,
which the tests seem to not be interested in.

Most of these aren't testing the same thing—they're either weaker tests, or cases where we should have been failing all along. I'm not sure if there's always a better way to fix them, but I'd want the owners of the tests to come take a look. Most of them are IDE and SourceKit, so @benlangmuir and @nkcsgexi?

I think all of the NEXT-NOT to NOT changes would be okay, but the DAG to DAG-NOT changes indicate we need to do something else in the test, since FileCheck doesn't re-order DAGs across NOTs (which I must not have known at the time I wrote all those tests).  @compnerd, do you feel up to improving the DAG-NOT cases?  If not, feel free to just drop them from this PR and I can take a look at them later.

@benlangmuir I agree that the NEXT-NOT to NEXT changes should be inconsequential.  I think I explicitly called out the DAG changes in the commit message as being somewhat less stringent.  Im happy to help improve the DAG tests, but Im not sure I know what you have in mind.  Given the nature of the change, I think that a split into two PRs may be wise.  The first one would take care of the NEXT-NOT to NEXT cases so that we can get these enabled ASAP.  A second PR can tackle the DAG-NOT changes with the improvements that you may have in mind.

Given the nature of the change, I think that a split into two PRs may be wise. The first one would take care of the NEXT-NOT to NEXT cases so that we can get these enabled ASAP

Yes please.

I think I explicitly called out the DAG changes in the commit message as being somewhat less stringent. Im happy to help improve the DAG tests, but Im not sure I know what you have in mind.

For the DAG cases: I think most of these just want to check for the complete absence of something, so we could add a separate _NEGATIVE check prefix variant for those tests, and just put the NOT there. E.g.
-// DEFAULT_ARGS_8-DAG-NOT: methodWithDefaultArgsInSub1()
Would become
+// DEFAULT_ARGS_8_NEGATIVE-NOT: methodWithDefaultArgsInSub1()
plus a change to the RUN lines to run both checks.  I don't know if there's a better way to accomplish that, since it feels a bit clunky.

Ill push an update to split it in a bit.  I think that there were a couple of cases where the complete negation check will fail though.

Anything else that should be changed on this PR?

@swift-ci Please test

LGTM, I'll merge when tests pass.

Seems like an unrelated failure?

Yep!  Thanks for working on this.


Setting up karma and jasmine

#1

Awesome, @drdpedroso! Thank you!

@matheuslc Nice :) Can you add the hacktoberfest label to this PR please? Thanks :)

@drdpedroso, done!


Create Automation Schedule, Interval field type problem

In the type ScheduleCreateOrUpdateProperties there is an Interval field. It's type is *map[string]interface{}. I couldn't find any documentation what kind of map should i use there. I checked the powershell and the c# SDKs and they use a simple byte field there.
If this is the proper type of Interval can you someone provide some information what keys and values should i add to that dictionary?

Howdy @Kemyke,
The type *map[string]interface{}  is coming from our generator's mapping of OpenAPI types to Go Types. In particular, we only use map[string]interface{} when we don't have enough information about the service to be more specific. Digging into the particular operation that you're mentioning, you can see that Interval doesn't specify any type information.
Now, that doesn't mean that the situation is hopeless! I'll open an issue in the azure-specs-repository asking to improve the definition of the Interval field. In the mean time, to unblock you, I tinkered around with Go and didn't find a good way to json.Serialize a map[string]interface{} into a JSON token instead of a JSON object the way the C# SDK would. The next step, assuming we can't find a way to structure the map, would be to create a custom Preparer which will set the value of Interval on the response manually.  I recognize that it's a lot of work for little return, but it may be the fastest way to get unblocked while we  fix it the right way.

Because there aren't any more actionable items in this issue, I'm going to close it out. However, feel free to keep commenting here and ping me if needed.

I know it is dirty but isn't it a possible workaround to modify the models.go and change the type of the Interval field manually on this type until the rest api spec fixed?

And one more thing, may i ask why you use map[string]interface{} for the unkown types and not an empty interface (interface{})

You're free to do that in a vendored copy of our SDK, and that may be easier for you than building a preparer. Do note though, that beyond just feeling dirty, the consequence of doing so is that updating your dependency will wipe away your work.
In terms of the choice of map[string]interface{}, this is something that puzzles me too. I've dived into it before, and convinced myself that interface{} was a poor choice. If I remember correctly, I basically think that the type assertion story in the default json.Unmarshal & json.Marshal functions isn't strong enough to allow for just interface{}. (This is a bit of a cop-out statement, I know please forgive me.) If I were going to choose anything, I would have thought json.RawMessage would be a reasonably good choice.
@jhendrixMSFT, @mcardosos, @salameer have any thoughts on this? I think it probably merits someone spending a little time next sprint evaluating whether or not switching to json.RawMessage would be safe.


Dark Mode: Flash of Undarkened Content

I noticed if you are clicking into a new feed, the Web View for the article content clears to white before reloading with the expected dark gray backdrop.

Open NetNewsWire in Dark Mode.
Click on any feed that is not currently selected, so that the detail view shows "No selection".
Click on any article in that feed.

Result: the detail view flashes bright white before loading the expected dark-themed background.
This can probably be remedied by some combination of pre-loading the web view with theme-suitable content, or maybe making the web view have a transparent background?

A faster way to test the flash of white is simly to cmd-click the selected news item to unselect and reselect. The white background appears for each transition.

I confirmed with the View Debugger that the white is being drawn by NetNewsWire.DefaultWebView.

It's not trivial to address this problem, but here is a summary:

WKWebView seems to default to a white background while loading content for the first time, or when switching back to "empty" content.
We could alleviate the problem by hiding the WKWebView when first loading it, and then re-showing it again when it's done loading. At this point any future loads should inherit the previous style of the web view until the new content gets loaded to supersede it.
In the Slack, Matt Meissner mentioned a private SPI in WebKit:

webview.setValue(true, forKey: "useSystemAppearance")
Which apparently will achieve the desired use of correct background colors. We probably don't want to rely upon private SPI though.
I think a reasonable solution might be to simply "prime" the WebView with suitable empty content to match the current appearance. We might not even need to hide the webview in that case because the process of priming it when the view is loaded might complete before it's really substantially used.

Update from Matt Meissner that the "useSystemAppearance" hack doesn't completely solve the flash on its own. I think looking into some clever combination of hiding and/or pre-loading the webview with pertinent content would be a reasonable approach.

I think a reasonable solution might be to simply "prime" the WebView with suitable empty content to match the current appearance. We might not even need to hide the webview in that case because the process of priming it when the view is loaded might complete before it's really substantially used.

I think this is most likely approach to getting the flashing issue resolved.  We remove the NoSelectionView all together and use HTML to replace its functionality so that the WebView never hides again.  Worse case is that we have a white flash when the application loads.
@brentsimmons If you approve this approach, I'll code it up and we can see if it works.

@vincode-io I agree — sounds like a good approach. Approved.

This appears to have resurfaced quite prominently in iOS 17 in both flash-to-white & flash-to-black varieties.
From testing: any time your phone switches display mode you need to go through roughly three articles before the flashing behaviour stops.
See #4252

It looks like a little bit of code might got lost when we reverted to mac-release. The current webView should be removed from its super view before inserting the new one in WebViewController. I'm not 100% sure that is the problem, but that is the only thing I can see different from what used to work.

This is behaviour on the prod release. It's not a dev build.

In that case it might already be fixed on main since the implementation of how we mitigate the flashing has changed there.
@brentsimmons You will still want to take a look at my previous comment. It will cause a memory leak at the least if not addressed.


Select gcc string ABI, etc.

Add a build-time option to select which std::string ABI to use.
Building with GLIBCXX_USE_CXX11_ABI=1 uses the new (C++11 compliant) ABI,
building with =0 uses the traditional gcc string ABI for compatibility.
This only affects gcc builds.
Also automatically define _GLIBCXX_SANITIZE_VECTOR=1 when compiling for
sanitize mode, it turns on some extra instrumentation to detect running
off the end of a std::vector but still within its allocated capacity.

LGTM!


[hotfix] Fix savepoint not auto create tag

Purpose
Savepoint not trigger notifyCheckpointComplete method
Tests

API and Format

Documentation

cc @liming30

@wxplovecc Thanks for your contribution, left one comment.

Get it close this


Modified front end to make cool div container for cool words generated

Modified the front end and added div containers for the names generated by the cool name api. Hover effect on mouse over also added.
Fixes Issue #2
Screenshot:

Ok I will try it.
On Fri 7 Dec, 2018, 11:58 AM Mohit Kumar Yadav<EMAIL_ADDRESS>wrote:

@tmsreekanth98 https://github.com/tmsreekanth98 changes you are
proposing in this PR are very much similar to what we currently have. Can
you make these names display in a responsive table, currently a single cool
name is consuming full width and rest of the part is empty. You can take a
look at https://getuikit.com/docs/table
for various types of tables.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NJACKWinterOfCode/cool-name-api/pull/6#issuecomment-445136487,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AhXQggjAbfWNIMua8s2pV9RHx1LA4nLnks5u2gqcgaJpZM4ZBKCi
.

Regarding the responsive table idea: I have done it, but if the name is too long the table has to be scrolled to the right horizontally.  The cool name generated has no space in between the word, so the text is not going to the next line and hence it is difficult to keep the table width in control as text spans across the width of the screen and not to the next line.
1 in each row will not have that problem. If u want i can send a PR for the 3 in a row version but it does not look good when names entered are big in size.

@tmsreekanth98 explore the uk-width-* in UIkit it allows to have dynamic width. That can be an alternative of using a table, I can understand that can be a problem since the number of columns is fixed so you can try it with 2 columns.

Ok. I am looking into it. :)
On Mon 10 Dec, 2018, 7:00 AM Mohit Kumar Yadav<EMAIL_ADDRESS>wrote:

@tmsreekanth98 https://github.com/tmsreekanth98 explore the uk-width-*
in UIkit it allows to have dynamic width. That can be an alternative of
using a table, I can understand that can be a problem since the number of
columns is fixed so you can try it with 2 columns.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NJACKWinterOfCode/cool-name-api/pull/6#issuecomment-445614435,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AhXQgj_CV6KHEkV8aT7gOE8_0KVRpibVks5u3bksgaJpZM4ZBKCi
.


Define Target Group

Seekers who are searching for Christian community and truth
Seekers who don't know the details of denominations
Profession: international students, businessmen, refugees, (tourists)
Age group: > 10
Language: English, German, more

https://www.figma.com/design/jn1oKvVODFGrgxUqRKcHDn/AI-and-Search-With-Prototype-(Community)?node-id=0-1&t=lZOAhrVq1pVn3D1E-1


Proxy missing identifiers when making Auth0 request on SPA

What is your Test Scenario?

We would like to sign in using Auth0 with the flag useRefreshToken enable.
What is the Current behavior?

On call to auth0 token, we have a 404 error (page not found) due to testcafe proxy missing identifier:
Example request failed: http://localhost:1337//https://dev-thomas.eu.auth0.com/oauth/token
Example request working when the useRefreshToken flag is disable: http://localhost:1337/pEoiZVXss*WYH65fc4A
/https://dev-thomas.eu.auth0.com/oauth/token
What is the Expected behavior?

We expect the proxy to correctly intercept the request to the token, please look at the example above.
What is your web application and your TestCafe test code?

Using the sample application from auth0 (https://github.com/auth0/auth0-spa-js), force the useRefreshToken to be true always and then run the test.
What we do is:
AUTH0 Credentials
 var defaultDomain = 'dev-thomas.eu.auth0.com';
 var defaultClientId = 'QxaJHsHhAuVPv4M3uBv99ECfuE6LJgZ3';
 var defaultAudience = '';

Testcafe fixture
  await t.click(Selector("#login_redirect"));
  await t.typeText( Selector("#username"), "customerTest@thomas.co");
  await t.typeText(Selector("#password"), "Customer1!1");
  await t.click( Selector("button[type='submit']"));
  await t.click( Selector("button[data-cy='get-token']"));
  await t.click(getToken);

We are having a "Unexpected end of JSON input" and we want to see the token on the default section.

Your complete test code (or attach your test files):

  await t.click(Selector("#login_redirect"));
  await t.typeText( Selector("#username"), "customerTest@thomas.co");
  await t.typeText(Selector("#password"), "Customer1!1");
  await t.click( Selector("button[type='submit']"));
  await t.click( Selector("button[data-cy='get-token']"));
  await t.click(getToken);

Your complete configuration file (if any):

 var defaultDomain = 'dev-thomas.eu.auth0.com';
 var defaultClientId = 'QxaJHsHhAuVPv4M3uBv99ECfuE6LJgZ3';
 var defaultAudience = '';

Screenshots:

![TestCafe](https://user-images.githubusercontent.com/50017052/97719792-69bcf900-1abf-11eb-9ba1-b56080e2cba3.PNG)

Steps to Reproduce:

As abode descibed
Your Environment details:

testcafe version:  1.9.4
node.js version:  11.10.1
command-line arguments:  testcafe chrome test
browser name and version: chrome (not headless)
platform and version:    Windows

@alexpthomasdev, Thank you for your report.
I reproduced this issue, we'll update this thread once it's fixed.
For the team:
import { Selector } from 'testcafe';

fixture`1`.page`localhost:3000`;

test('1', async t => {
    await t
        .typeText(Selector('#domain'), 'dev-thomas.eu.auth0.com', { replace: true })
        .typeText(Selector('#client_id'), 'QxaJHsHhAuVPv4M3uBv99ECfuE6LJgZ3', { replace: true })
        .click(Selector('button').withText('Save'));

    await t.navigateTo('http://localhost:3000');

    await t.click(Selector('#refresh_token_switch'));

    await t
        .click(Selector('#login_redirect'))
        .typeText(Selector('#username'<EMAIL_ADDRESS>        .typeText(Selector('#password'), 'Customer1!1')
        .click(Selector('button[type="submit"]'))
        .click(Selector('button[data-cy="get-token"]'));

    await t.debug();
});

Any updates on this issue?

@dylanz666
Hello,
We have no updates yet.

any workaround there ?

@svnindia
There is no workaround. We need to research this issue. We'll update this thread once we have any results.

We've also hit this blocker, and unable to find away around it. :(

It seems like the issue was resolved in the latest TestCafe release ('v1.10.0'): the test posted above works fine - the access token is shown in the default "Access tokens" section and there is no "Unexpected end of JSON input" message.
If anybody is still experiencing issues with this, please comment here with another example for reproducing the issue and we will reopen it.

Thanks @wentwrong. I can confirm this update has fixed our issues.

@danderton, I'm happy to hear it's resolved for you. Thank you for reporting back.


crontab is not running on ros console

RancherOS Version: 1.5.0
Hi
I have trying to enable crontab on ros console for that I was followed some steps like
1)sudo ros service enable crontab
2)crontab -e  and add this line to it

*/1 * * * * . $HOME/.profile ; /opt/sample.sh
But its not running even at the time of  reboot the whole crontab list is getting vanished from the machine

please help me to solve this issue
Thank you

This issue has not been updated within 50 days and I will close this issue.
If you still have doubts, please reopen it and let me know.


false positive on www.proxmox.com

Proxmox (www.proxmox.com) is not a Piracy or bittorrent tool. It is a virtualisation platform

Removed, thanks!


Feature/extend joi validation

Resolves #65 + some small additions

Able to extend the default Joi validation schema produced by enjoi
Make console warning on empty schema configurable through options - an empty schema or one that is considered empty is valid, so the warning should be removable. Refer to https://json-schema.org/latest/json-schema-core.html#rfc.section.4.3.1. The default value of the option is left to true to avoid breaking changes.
Tests and documentation covering the new functionality

Well the original idea (which was inspired by the needs of our project) was to stay as close to native JSON Schema and Joi as possible. x- attributes are not exactly native JSON Schema, so they conflict with this idea. We can also extend the validation by writing validation logic ourselves outside of Enjoi. I don't see what advantages would x- attributes bring us in that case.
The advantage of using Joi is the standardization of the validation definitions and the aggregation of all validation errors in one place. The latter being the bigger advantage and the main motivation for this PR.

I think at this point this needs to be closed. I believe this feature would now be supported by recent merged refineSchema as well.


Execution result: failed(logs) uploading zip file into Lambda function

Getting Error while uploading zip file into Lambda function :-1:
{
"errorMessage": "Cannot read property 'application' of undefined",
"errorType": "TypeError",
"stackTrace": [
"AlexaSkill.execute (/var/task/AlexaSkill.js:86:62)",
"exports.handler (/var/task/index.js:549:16)"
Kindly suggest

hey there, i'm working on alexa right now and i've got this error, i was just wondering if you had fixed your problem, can you help me too?

Hi, i got the same error, using the "savvyConsumer" template.
I uploaded a zip file with a custom index.js, AlexaSkill.js and the node_modules directory.
Any help?

Ok, i start from scratch following the Setup from here:
https://github.com/amzn/alexa-skills-kit-js/tree/master/samples/savvyConsumer
I checked:

the APP_ID: it has to be the Skill Application ID found in the Skill Information tab.
the ACCESS and SECRET KEY: i create new keys in my account Security Credentials (not IAM)

And it works !

Please be advised that we're no-longer providing support for this project and so instead, please check out the replacement Alexa Skills Kit SDK for Node.js:
https://github.com/alexa/alexa-skills-kit-sdk-for-nodejs
Also, we have a number of sample skills based on this newer SDK, under here:
https://github.com/alexa


[reverse min-height for images and IE11]

#176
@prehnRA I apologize I only saw the open issue tonight, this is due to a change of mine to fix the extra space there is with images in IE11. I will look for a solution on the extra space issue in IE 11.

Deploy failing at "Executing user command: (npm run postinstall;npm run prepublishOnly;cd docs-src;npm install;npm install -g gatsby;gatsby build)"
=>npm run postinstall is now located inside docs-src package


CVAT new UI: object's details menu settings

My actions before raising this issue

[x] Read/searched the docs
[x] Searched past issues

Expected Behaviour

The object's details menu should have a setting to automatically hide or unhide it for all objects, including new.
Current Behaviour

Object's details are hidden by default. We have to make one more click every time to enter some attributes.
It's inconvenient.

Possible Solution

Add a setting "always show objects details" into "settings". This setting should be enabled for new objects too.
It'll let annotate attributes quickly.

Operating System and version (e.g. Linux, Windows, MacOS):
Code example or link to GitHub repo or gist to reproduce problem:
Other diagnostic information / logs:
Logs from `cvat` container

Next steps
You may join our Gitter channel for community support.

Settings option "always show objects details" already exist. I can suggest another solution:
If the button "expand all" was pressed, all new objects are created with opened details. If the button "collapse all" was pressed, all new objects are created with closed details.

I think it could be a good solution. Thank you.


nothing happening in install in some spots

I only caught a second of it.  But there are long pauses of nothing

gotcha.  You have to turn off the spinner before printing, so in the weaving I missed something.  Thx for reporting.

So we have a problem here that I worked on for about an hour and don't see a particularly elegant solution to. Every time we spawn a new process like ignite add i18n there's a pause before the ignite-i18n package starts displaying its own output.
The solution I attempted was to try displaying our own output in the template while these packages were installing. That way we could kick off a spinner before spawning the process and kill it when the process is completely done.
The problem is that each of these plugins is supposed to handle their own spinners. So, in order to do this, we'd need to make sure to run ignite add <package> --app-template and have each plugin check to make sure they're not running as part of an app template and suppress the spinner output if so.
There are a number of issues with this. One is that the process is now opaque to us in the app template, so all we know is the process is running, not that it's installing or linking or whatever. I don't think it's a good thing to lose this detail. Another issue is that if the package author forgets to suppress output, it starts competing with the app template's spinner output, which results in flickering.
I'm now implementing a hack that will display a brief "initializing " message and then stop the spinner on a timeout. It'll at least let the user know that something's happening. Not a great long-term solution, probably, but also probably good enough to ship.

This isn't too bad. I think we can live with this. If someone has a faster machine than me or for whatever reason ignite add runs much faster, we'll need to tweak the temporary spinner timeout from its current 8 seconds.


FactoryBoy data not created using json POST request

I've discovered a weird interaction between Flask, pytest, SQLAlchemy, and FactoryBoy that I think is a Flask bug. Consider these two identical routes that should both return the number of records in a database table:
bp = Blueprint('example', __name__, url_prefix='/example')

@bp.route('/form', methods = ['POST'])
def test_form():
    return str(db_session.query(Person).count())

@bp.route('/json', methods = ['POST'])
def test_json():
    return str(db_session.query(Person).count())

The difference is in the unit tests:
def test_form(self, client):
    person = PersonFactory()
    resp = client.post('/example/form', data={'foo': 'bar'})
    assert resp.data == b'1'

def test_json(self, client):
    person = PersonFactory()
    resp = client.post('/example/json', json={'foo': 'bar'})
    assert resp.data == b'1'

We're posting form data in the first test and JSON in the second. The first test succeeds and you see this in the log:
2019-04-30 14:26:05,425 INFO sqlalchemy.engine.base.Engine BEGIN (implicit)
2019-04-30 14:26:05,427 INFO sqlalchemy.engine.base.Engine INSERT INTO people (id) VALUES (%(id)s)
2019-04-30 14:26:05,427 INFO sqlalchemy.engine.base.Engine {'id': '658e241a-5522-47ca-9e61-bd6862d6ddc6}
2019-04-30 14:26:05,432 INFO sqlalchemy.engine.base.Engine SELECT count(*) AS count_1 FROM (SELECT people.id AS people_id FROM people) AS anon_1
2019-04-30 14:26:05,432 INFO sqlalchemy.engine.base.Engine {}
2019-04-30 14:26:05,433 INFO sqlalchemy.engine.base.Engine ROLLBACK

FactoryBoy correctly inserts the data and rolls it back when the test is done. However, the second test fails because the test person isn't inserted:
2019-04-30 14:28:27,341 INFO sqlalchemy.engine.base.Engine BEGIN (implicit)
2019-04-30 14:28:27,342 INFO sqlalchemy.engine.base.Engine SELECT count(*) AS count_1
FROM (SELECT people.id AS people_id FROM people) AS anon_1
2019-04-30 14:28:27,342 INFO sqlalchemy.engine.base.Engine {}
2019-04-30 14:28:27,343 INFO sqlalchemy.engine.base.Engine ROLLBACK

tests/test_example.py:40 (TestExample.test_json)
b'0' != b'1'

See this gist for how I'm creating the Flask app, initializing SQLAlchemy, and configuring the test suite: https://gist.github.com/dpmccabe/6d3bed81c37817c38fb3f2b262d1393d
Apologies if I'm doing anything unconventional, since I'm new to Flask.

Expected Behavior
The format of the request body (form data vs. JSON) should have nothing to do with whether FactoryBoy inserts records.
Actual Behavior
FactoryBoy records are not inserted when testing a post endpoint with a JSON body. It seems like there's some preprocessing step that's not performed with a JSON body.
Environment

Python version: 3.7
Flask version: 1.0.2
Werkzeug version: 0.15.2

There's no difference between the routes, because you're not parsing the form or JSON data, you're ignoring it.
This doesn't appear to be an issue with Flask, it appears to be an issue with Factory Boy not inserting data. Why do you think it's an issue with Flask?

Maybe it would be more accurate to claim that the problem might be with the Flask test client. It just can't imagine why changing the type of request in the test client would have anything to do with other code in that unit test that has nothing to do with the request and in fact occurs before the request is made.

The test client isn't involved in the code that's causing the issue, the issue is that Factory Boy doesn't insert data, which is not part of the Flask app or test client.


Crash when adding trim

Hi Guys
Script work well WITHOUT trim. I'm just in that situation a have 500 images that needs to be trimmed for making clickable surface buttons in an application.
I work on Photoshop CS6 (OSX Yosemite 10.10.2)
I get this error when i add trim. What can i do?
Error: General Photoshop error occurred. This functionality may not be available in this version of Photoshop.

Could not complete the command because of a program error.: on line 374

Here i have attached som images of my process..
Thanks you in advance.

Second time i run the script with same adjustment as above these two error come:

You have empty layers in your document, don't you? I fixed it, so it should be ok now. Update.

Still crashes, not really any difference. I tried this time with CS5 on OSX 10.8.5

Could you send me your PSD, please? Just post the link here if you can. (Or something else that crashes.)

Yes here you go. Hope you can crack the issue.
http://we.tl/3I3byugI1d
Thanks for quick reply.
Cheers.

Would just be great to have a solution that could export all layers (also in groups within groups) to trimmed single png's.
I got it to work i Photoshops own "save layers to file" script, if you remove all groups and only have layers. But anyone that makes any bigger(serious)(50+layers) projects needs to make groups to keep track of where all your stuff is. So don't understand why there is not a decent solution to this. Hope some of you guys can give me a tip/hint.
Cheers.

"a solution that could export all layers [...] to trimmed single png's"
I don't think I follow. What do you mean?
"I cannot believe this can be close to impossible. I think the amount of user on photshop and the budget + talent available to adobes staff should be able to fix this little tweak"
It's not impossible, although not exactly a little tweak, they just don't care enough. They can't make a decent "layers to files" script for years; why would they bother about this?

Works fine in CS 6 on Win 7. Looks like another mysterious Mac OS X issue. Cracked version? I guess we'll never know. I've done one thing I can do with it and that's pretty much it, even if I could reproduce the problem. Please try and let me know.

#1 Each layer exported into a trimmed png.
#2
Because every things made i photoshop related to app, website designs end up at a programmer as trimmed png's.
Am i wrong?

ok

#1 That's what this script does, doesn't it? Even the built-in PS script can trim when exporting to PNGs if I remember correctly. (Aside from organizing them into folders.)

If the crack is bad, it may overwrite wrong places in memory and disrupt the original functionality. Basically throwing nonsense errors anywhere in the app. And your problem sounds exactly like an internal bad memory management issue. But it may be just poor QA testing from the Adobe. Everything's possible.


Sam not detecting game phasmophobia

I have tried putting in the steam is but when I get to the game on Sam I get this issue generic issue. I attatched a screenshot showing I own the game on steam. I have tried restarting my pc redownloading the game trying beta mode and it wont detect it.

This game doesn't have achievements currently.


Wrapped the country selector button with Expanded widget in order to avoid overflow in a narrow container.

Wrapped the country selector button with Expanded widget in order to avoid overflow in a narrow container. In one of my project I found out the selector button is overflowing my container. So I wrapped the selector button with a Expanded widget and it solved the issue.

is this going to get merged? That is a really annoying error, and this fixes it. This has been here waiting for 3 months now


host_ptr semantics for clCreateBuffer/clCreateImage  when called without CL_MEM_USE_HOST_PTR or CL_MEM_COPY_HOST_PTR

The spec currently says that clCreateBuffer or clCreateImage should return CL_INVALID_HOST_PTR

if host_ptr is NULL and CL_MEM_USE_HOST_PTR or CL_MEM_COPY_HOST_PTR are set in flags

or if host_ptr is not NULL but CL_MEM_COPY_HOST_PTR or CL_MEM_USE_HOST_PTR are not set in flags.

However, CTS tests do not test or follow the second part of the spec above.
There are few places in CTS where these APIs are called with non NULL host_ptr, but without CL_MEM_USE_HOST_PTR or CL_MEM_COPY_HOST_PTR
https://github.com/KhronosGroup/OpenCL-CTS/blob/0ad8c9a9c02c9881ffce8bb9944136214db1f9e7/test_conformance/images/kernel_read_write/test_iterations.cpp#L1375
So, we have two options -

Fix the spec to allow non-NULL host_ptr in absence of CL_MEM_USE_HOST_PTR or CL_MEM_COPY_HOST_PTR

Fix CTS to disallow passing non-NULL host-ptr in absence of CL_MEM_USE_HOST_PTR or CL_MEM_COPY_HOST_PTR  and potentially add a test to cover this scenario to ensure implementations return appropriate error.

Thanks Ben !!
Moved the issue to OpenCL-CTS.

Created PR for addressing this https://github.com/KhronosGroup/OpenCL-CTS/pull/1087/

#582 looks like a duplicate

#582 looks like a duplicate

Closing this as corresponding CTS change is merged as part of PR #1087


pub get fails: (1; So, because  depends on both sentry_flutter ^4.0.1 and flutter_driver any from sdk, version solving failed.)

I did a flutter upgrade yesterday as last action in the night. Today, none of my flutter projects are able to resolve dependencies:
Steps

Run flutter upgrade.    --> Channel stable, 2.5.2, on macOS 11.6 20G165 darwin-x64, locale es-ES)
Try to compile any project
**Expected
Project compiles without errors

**Actual
pub get doesn't complete. It throws this error
pub get failed (1; So, because pro_insurance_dictionary depends on both sentry_flutter ^4.0.0 and flutter_driver any from sdk, version solving failed.)
I have tried to fiddle with different version in the dependencies section, commenting out some of them... no way to get a meaningful outcome that leads to the root cause of this.
Could you investigate?
** Full error messages:
pub get
Running "flutter pub get" in pro_insurance_dictionary...
Because sentry_flutter >=4.0.0 <4.1.0-nullsafety.0 depends on sentry ^4.0.0 and sentry_flutter ^4.1.0-nullsafety.0 depends on package_info ^2.0.0, sentry_flutter ^4.0.0 requires sentry ^4.0.0 or package_info ^2.0.0.
And because sentry >=4.1.0-nullsafety.0 depends on http ^0.13.0 and firebase >=5.0.3 <9.0.0 depends on http >=0.11.3 <0.13.0, if sentry_flutter ^4.0.0 and firebase >=5.0.3 <9.0.0 then package_info ^2.0.0 or sentry >=4.0.0 <4.1.0-nullsafety.0.
And because firebase_analytics 6.3.0 depends on firebase_analytics_web ^0.1.0 which depends on firebase ^7.3.0, if sentry_flutter ^4.0.0 and firebase_analytics 6.3.0 then package_info ^2.0.0 or sentry >=4.0.0 <4.1.0-nullsafety.0.
And because no versions of firebase_analytics match >6.3.0 <7.0.0 and sentry >=4.0.0-alpha.1 <4.1.0-nullsafety.0 depends on uuid ^2.0.0, if sentry_flutter ^4.0.0 and firebase_analytics ^6.3.0 then package_info ^2.0.0 or uuid ^2.0.0.
And because uuid >=2.0.0-rc1 <3.0.0-nullsafety.0 depends on crypto ^2.0.0 and every version of flutter_driver from sdk depends on crypto 3.0.1, if sentry_flutter ^4.0.0 and firebase_analytics ^6.3.0 and flutter_driver any from sdk then package_info ^2.0.0.
And because pro_insurance_dictionary depends on both firebase_analytics ^6.3.0 and package_info ^0.4.3+2, sentry_flutter ^4.0.0 is incompatible with flutter_driver from sdk.
So, because pro_insurance_dictionary depends on both sentry_flutter ^4.0.0 and flutter_driver any from sdk, version solving failed.
pub get failed (1; So, because pro_insurance_dictionary depends on both sentry_flutter ^4.0.0 and flutter_driver any from sdk, version solving failed.)

I have tried to downgrade Flutter to versions 2.5.1 and 2.5.0 and I'm getting the same errors...
Have some nasty ghost haunted this computer?  :(
** Any ** advice will be very welcome

Hi @pedrosc1967, this appears to be an issue with resolution of your dependencies.
My guess is that some of your dependencies have transitive dependencies that are conflicting with each other.
My advise would be to continue fiddling with the dependencies as you have, you'll eventually find a fix. Also, from what I can see, you are using old dependencies in your project, I would advise you update them to the latest versions by checking their versions on pub.dev.
You could also try to run
flutter pub outdated which will allow you to see the outdated versions and will provide further instructions on how you can upgrade to the latest versions.
As this is an issue with resolving dependencies, this is not an issue with flutter itself, as such I'm going to have to close the issue.

I solved it by myself by downgrading Flutter to 2.5.1


Failing when changing from WiFi to 4G or the other way

Hello world,
Currently I use part of NEKit to apply some logic to DNS queries and my extension is working really well.
I only have one problem and I guess is related to NEPacketTunnelProvider rather than NEKit, but not completely sure.
Basically, my extension fails (internet does not work) when I move from WiFi to 4G, or the other way (but not airplane mode, I guess because NEOnDemandRuleConnect restarts the extension)
The thing is: Do I have to use a special logic when there is an interface change? (I would say yes)
Here:
https://github.com/zhuhaow/NEKit/issues/77
I see that defaultPath is used and startTunnel called again (although apple docs that method is called by system). Is that right?
Perhaps I have to use setTunnelNetworkSettings again, several times in the tunnel life-cycle.
Is it right to use defaultPath to detect when user goes from WiFi to 4G and and viceversa?
I would appreciate any ideas about this topic.
Thanks a lot for your help.

It seems now it is working better. Thanks!


Add Db authentication method in addition do Discord for user management

This PR adds a secondary authentication method for user access to the map, if for instance you manage yourself your user access rights and store them in a database.
A new DB is available in config for management of users, where you can specify the name of your user table:
  "database": {
    "settings": {
[...]
      "localUserTableName": "members",
[...]
    },
    "schemas": {
[...]
      "localAuth": {
        "enabled": true,
        "type": "localAuth",
        "host": "<IP_ADDRESS>",
        "port": 3306,
        "username": "user",
        "password": "pass123!",
        "database": "localauthdb",
        "charset": "utf8mb4",
        "arScanColumn": false,
        "useFor": ["localUser"]
      }
    }
  },

A new section similar to the Discord section with specific options:
  "localAuth": {
    "settings": {
      "usernameFormField": "username",      <- if authentication is made from an external form
      "passwordFormField": "password",      <- if authentication is made from an external form
      "usernameToLowerCase": true,          <- to force user entry in form to lowerCase before checking if valid
      "passwordEncryption": "bcrypt",       <- password encryption in Db (bcrypt, md5 or none)
      "usernameDbField": "username",        <- username column name in Db
      "passwordDbField": "password",        <- password column name in Db
      "discordIdDbField": "discordId",      <- Discord ID column name in Db if used
      "emailDbField": "email",              <- email column name in Db if used
      "statusDbField": "status"             <- status column name in Db = access level for perms. ie. "confirmed", "donator", "admin"
    },
    "allowedUsers": [],
    "perms": {
      "map": {
        "enabled": true,
        "status": []
      },
      "pokemon": {
        "enabled": true,
        "status": ["admin","donator"]
      },
[...]

Example of a typical user local Db:

database name: localauthdb
member table: members
structure: [id, username, password, discordId, email, status]
typical entry: ["123", “john", "098f6bcd4621d373cade4e832627b4f6", "32163294729173792"<EMAIL_ADDRESS>"donator"]

Login page gives the choice between the enabled auth methods:

Also moves the Login/Logout button to root of drawer menu

I would get rid of none and md5 choices and leave only bcrypt. It's up to @TurtIeSocks though.
Even if we don't store anything sensitive in this database, users tend to use same login & password combination all over the places. Any leak could lead to hacks on other accounts - that's what I'm concerned about.

I'll have more time to dig through this later this afternoon but my initial thoughts are that I would prefer there to only be 1 user table, even if it means having a column that specifies the strategy used, which I planned to add in the future anyway. Thank you though for the amazing work on this one!

I'll have more time to dig through this later this afternoon but my initial thoughts are that I would prefer there to only be 1 user table, even if it means having a column that specifies the strategy used, which I planned to add in the future anyway. Thank you though for the amazing work on this one!

There is still only one user table for the ReactMap current users, shared with Discord (if a user logs in via db auth and the db has a column for a discordID then it's pulled and used as identifier in the user table for sessions).
The whole point is to be able to use a db that is managed outside ReactMap and shared through different services, so "including it" in ReactMap makes it dependent from this one service.

I like this idea, but big NO for MD5 as "password hashing". Please use bcrypt instead.
I would also get rid of none as those are bad habits and shouldn't be allowed.
First result from google related to md5/bcrypt https://security.stackexchange.com/a/19908

I 💯 agree, MD5 should never be used as a password hashing method anymore, especially if saved to the database.
Instead of saving the actual encrypted password in the database, I recommend just saving the encryption key and salt in the tables. Example: https://stackoverflow.com/a/4330586

I like this idea, but big NO for MD5 as "password hashing". Please use bcrypt instead.
I would also get rid of none as those are bad habits and shouldn't be allowed.
First result from google related to md5/bcrypt https://security.stackexchange.com/a/19908

I 💯 agree, MD5 should never be used as a password hashing method anymore, especially if saved to the database.
Instead of saving the actual encrypted password in the database, I recommend just saving the encryption key and salt in the tables. Example: https://stackoverflow.com/a/4330586
If you have user passwords saved in MD5 then it's time they get a password reset imo.

Yes sure. Here we are never writing / registering users but only reading an external dB which could be set with any encryption (or not...).
It’s important to allow ReactMap to work with multiple methods (as crappy / insecure as they may be).
It’s up to the actual dB writing tool to use a proper encryption if it’s exposed to outside.

I'm in favor of dropping md5 support, already a huge number of packages in this project 😊  I think offering custom auth integration is enough on its own. Forcing a password reset on users is not the end of the world for them.

There's another possibility. Modules support (custom scripts based on hooks, like modules in IRC bots).
Though this is A LOOT more job to achieve what you need in there.

It’s important to allow ReactMap to work with multiple methods (as crappy / insecure as they may be).

It's fresh project... 👼
I would go with md5 and none removal for now like three of us suggested. This way future admins won't be able to abuse it. I bet you know what you do... but people tend to use easier solutions like no encryption at all or md5 (which is basically the same when done incorrectly).

Replaced by #111


Implementation of segments for pyglet.shapes.BezierCurve

Created pull request to allow comments and suggestions.

Looks good! There are some small linter complaints, but i'll take care of those locally. after merging.


Why would a tab ever get demoted from master?

Feedback from putting it in my production app:
It would be nice to have utility methods like: crosstab.isMaster() and crosstab.isSupported().
It'd be (subjectively) better if crosstab.on(crosstab['util']['eventTypes']['becomeMaster'] was something more like crosstab.on('becomeMaster', ...).

Sorry. I found crosstab.supported.


feat: add StopTimeTripWithoutTimes validator

Summary:
Summarize the changes in the pull request including how it relates to any issues (include the #number, or link them).
Partially resolves #1089
Expected behavior:
Adds a new validator that reports an error if a trip includes stop time that are missing either arrival time or departure time.
Please make sure these boxes are checked before submitting your pull request - thanks!

[x] Run the unit tests with gradle test to make sure you didn't break anything
[x] Format the title like "feat: [new feature short description]". Title must follow the Conventional Commit Specification(https://www.conventionalcommits.org/en/v1.0.0/).
[x] Linked all relevant issues
[ ] Include screenshot(s) showing how this pull request works and fixes the issue(s)

If I understand properly, this notice is different from the other ones in the sense that it informs that a notice could not have been checked.
I saw that this was briefly discussed in the issue related, but this is a broader question of what to do when portions of this validator don't run (and a notice could not have been checked). This is the case for plenty of these validator notices and I think they should be treated differently since it's not technically a spec violation.


Bugfix for Particle Gibbs

Proposition to solve https://github.com/yebai/Turing.jl/issues/383 and https://github.com/yebai/Turing.jl/issues/373.

I still have to fix something

I still have to fix something

Right - let me know when you're done.

Right - let me know when you're done.

Good, but it'd be nice to have another test targeting what we fixed.
Otherwise what do you think of using gid=-1 in push!(vi, vn, r, dist, -1)(at https://github.com/yebai/Turing.jl/blob/bugfix-383-pg/src/samplers/pgibbs.jl#L167) since we don't know what is the sampler associated with the random variables encountered. As proposed here https://github.com/yebai/Turing.jl/issues/373#issuecomment-344213583, we could get the right gid by looking at sub_alg's spaces. What do you think @yebai ?


Upgrade postgresql cluster to v17

Describe the bug or feature request
Steven told me to do it.
Code of Conduct

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

Just bored things

BYE


Whiteboard #286, Main Page Layout #195

The whiteboard displays.
Ticket #286
commit a8a2874e1b4af474c827be19676f0ce8a923c981
Main Page is divided into two major Containers
Ticket #195
commit 2c0465cb2821319d8f845308fbae043881465c0e

Looks good to me, update the CSS units from pixels to percentages and you're good.


issue #3: use prepared statements

I replaced all (except one without parameters) db queries with prepared statements.  Prepared statements are the best safeguard against sql injection. (You still have to sanitize your input though.)
Prepared statements also speed up "batch queries".
I think I tested everything, if I overlooked something, I'm sorry. I tried to stay as close to your original code as possible.
You can merge this pull request or use it as reference.
Edit: I didn't change the create table statements etc. in install.php and the queries in db.php.

Thank you! I think you forgot to remove the mysqli_real_escape_string calls in some places, resulting in double escaping. I'll fix that after merging.


[Request]  Read and Set Timecode from the Atem

Being able to read the Timecode from the Atem as Feedback.   But also being able to Set the timecode To the Atem.   As many Atems can not handle Time of Day.   It would be great to push a button and let it sync to PC time or NTP.    Or preset time configured.

I also agree with this idea. It would be great to be able to read the timecode of an ongoing recording or live stream.

This is implemented and will be in the betas shortly


Correct line spacing with multi-line names and titles

See https://tex.stackexchange.com/q/661729/113546
and https://github.com/xdanaux/moderncv/issues/99
In several head styles the name and title parts are typeset with a specific font (defined in \namestyle/\namefont and \titlestyle/\titlefont respectively). This is done inside a group, in braces {...}. However the paragraph is not finished inside the group, which means that the element is typeset in the chosen font, but not with the corresponding \baselineskip. This manifests itself when a multi-line entry is given where the line spacing is too cramped.
I have corrected this by adding \par at the appropriate places. This also causes some \\ command to have to be replaced by \vspace.

Hi @pietvo
There's only some very minor changes requested here - are you interested in making and pushing those?
If not (or if not response), I'll try to finalize this at some point.
Thanks again for the contribution.


redundant code??

I'm learning saga, and found 2 small issues.

How can we fork an iterator?
https://github.com/redux-saga/redux-saga/blob/c61d6f13a33837e92fd36f9b332661a8200782ec/packages/core/src/internal/io.js#L122

will enforce that you can only pass function (could be a Function Generator)  into fork;  you can not pass an iterator to fork;
but, in a different place we have
https://github.com/redux-saga/redux-saga/blob/c61d6f13a33837e92fd36f9b332661a8200782ec/packages/core/src/internal/proc.js#L133
Questions: in what case will above if be truthy?

How do we yield an iterator? where can I find document for it?
https://github.com/redux-saga/redux-saga/blob/c61d6f13a33837e92fd36f9b332661a8200782ec/packages/core/src/internal/proc.js#L382

I also checked its history, it seems to me that it needs to be cleaned up

U might be right, would u like to remove this if statement, check if tests pass & send a PR?
you can just yield someGenerator() (someGenerator returns an iterator), but it's not recommended, it's better to yield call(someGenerator)

I also checked its history, it seems to me that it needs to be cleaned up

Not sure what do u mean. Could u elaborate?

thanks for your reply.
https://github.com/redux-saga/redux-saga/blob/c61d6f13a33837e92fd36f9b332661a8200782ec/packages/core/src/internal/io.js#L110
so it seems you can't call a generator. you can only call a fn;
it seems that yield someGenerator() has the same effect as yield* someGenerator(), but I can't find the source code for yield* someGenerator() . can you point me the direction? thanks

but I can't find the source code for yield* someGenerator(

There is no source code for this, because it's language feature.
function* someGenerator() {
  yield 2
  yield 4
  return 6
}

const res = yield* someGenerator()

is equivalent to
yield 2
yield 4
const res = 6

i see.
thank you for your help!


Open Plan File button opens plan XML

Is your feature request related to a problem? Please describe.
When viewing a plan (CTRL+M) the pop up for the icon says "Open Plan File", but it opens the plan XML.  I would expect a "plan file" to be a saved execution plan.

Describe the solution or feature you'd like
Better text for the icon might be "View Plan XML" or "Open Plan XML".
Describe alternatives you've considered
See above.
Additional context
In SSMS, if you right-click in the plan you have Show Execution Plan XML... as an option.

These menu labels are trying to generic, to be applicable to other data provider execution plans.  But in the meantime, I agree Show Execution Plan XML seems like a more appropriate text.


leader election needs to operate configmaps and leases

Related PR: https://github.com/open-cluster-management-io/registration-operator/pull/260
Signed-off-by: haoqing0110<EMAIL_ADDRESS>

/assign @qiujian16
/cc @ldpliu

/approve
/lgtm


Error

Im getting an error on line 28 of ViewController.m in the example project
[self.dataSource populateCellWithBlock:^void(MessageTableViewCell * __nonnull cell, Message * __nonnull message) {

the error reads: "incompatible block pointer types sending 'void(^)MessageTableViewCell __nonnull__strong, Message__nonnull__strong)' to parameter of type 'void(^ __nonnull)(UITableViewCell *__nonnull__strong, NSObject *__nonnull__strong)'

Looks like the problem is due to the fact that __kindof was introduced in Xcode 7 Beta 5 (and has essentially zero documentation), which means that this feature is really exclusively Xcode 7 b5 and above. I'll go ahead and fix the macros to use id instead of __kindOf UITableViewCell * which should solve this problem for now.

youre totally right about that. Im running xcode 6.4 so this makes plenty of sensee

Should be in master as of: https://github.com/firebase/FirebaseUI-iOS/commit/264f596f610c85856e808fea370633c006f0a187
Since it's not pushed to Cocoapods, you'll need to do:
pod 'FirebaseUI', :path => '../../'
Which will pull the pod in from the local git repo. Thanks for checking this!

got it to work, thanks !


SSH Default Password - alpine is not working

Device Info: iPhone 7 - iOS 15.1
When I tried to connect my iPhone via SSH, the default password "alpine" is not working. So I couldn't able to connect my device via SSH.
Here is the SC:

jajajja my friend root not work so you need to put ssh<EMAIL_ADDRESS>

WOW!! Thanks @edwin170 it worked finally hahaha..! Can you able to add any other repos or only mineek repo works here?

i think only mineek for now

and only repo rootless

hey, have you ever tested dual boot on iPhone ?

where is sshd_config located?


Incorrect unescaping of column names

Consider the following table:
CREATE TABLE example (
  `from` DATE NOT NULL
);

from is a reserved SQL keyword. If you try to insert a row into that table using named columns, the from column is not escaped, which causes a syntax error. I haven't found a way to force the library to not remove escapes for this column name even after forcing it to insert a raw value:
// this query unescapes "`from`" into "from"
connection.query(
  "INSERT INTO example (`from`) VALUES (?)",
  ["2020-01-01"]
);

// this query does the same
connection.query(
  "INSERT INTO example (?) VALUES (?)",
  [mysql.raw('`from`'), "2020-01-01"]
);

This also affects exports from MySQL that contain backtick-escaped column names that are reserved keywords when being passed to the query function after reading from a file.
Is there something I'm missing? Is there a way to force identifiers to always be escaped in the final query?

Hi @KrofDrakula I ran the code you provided and have no issues. This library does not do any kind of unescaping, so I'm not sure why you would be having issues. I know you only gave a piece of code, so maybe there is some kind of things happening in code that is not provided.
For reference, here is a complete, stand alone file I used to try and reproduce. Perhaps you can run this and see if it reproduces for you? Just change the connection options:
const mysql = require('mysql')
const conn = mysql.createConnection({ /* your conn options */ })

conn.query('CREATE TEMPORARY TABLE `from` (`col1` DATE)', function (e) {
  console.log('create table 1: ' + (e ? e.message : 'OK'))
})

conn.query('CREATE TEMPORARY TABLE `example` (`from` DATE)', function (e) {
  console.log('create table 2: ' + (e ? e.message : 'OK'))
})

conn.query('INSERT INTO example (`from`) VALUES (?)', ["2020-01-01"], function (e) {
  console.log('insert 1: ' + (e ? e.message : 'OK'))
})

conn.query('INSERT INTO example (?) VALUES (?)', [mysql.raw('`from`'), "2020-01-01"], function (e) {
  console.log('insert 2: ' + (e ? e.message : 'OK'))
})

conn.end()

Running this for me results in the following:
create table 1: OK
create table 2: OK
insert 1: OK
insert 2: OK

@dougwilson Sorry for the late response; this might be a problem with node-mysql2, as we're currently using that version of the library, not the base mysql. Not sure if it has anything to do with the specific setup there, but I'll move the conversation to the relevant repo.
Thanks!


Reorganizing repo and build scripts

Read the README.md for more info on how the code is organized with this change.

single script to build whatever you need - e.g. ./wl-make.sh php/php-7.3.33
patches stored separately so patch evolution history is accessible
no dependency on other cloned repositories, submodules or pre-built libraries - all necessary code is cloned in a shallow way on-the-fly, then patched and then built

LGTM! I really like the new organization. I believe it's clear and it helps to grow this repository.
The only point I'm missing is where the target repository (ex. sqlite.git) changes it's HEAD to the specific version. I see the script that sets the repo is in the top level folder of libs and languages. However, I couldn't identify where the version is properly set before start building.
Apart from that, I would also include a clear list of tools required to build the different languages / libs. This may be done directly by documentation. For example, include a Requisites section on the README.md file on every language / lib version.

LGTM! I really like the new organization. I believe it's clear and it helps to grow this repository.

Thanks @Angelmmiguel

The only point I'm missing is where the target repository (ex. sqlite.git) changes it's HEAD to the specific version. I see the script that sets the repo is in the top level folder of libs and languages. However, I couldn't identify where the version is properly set before start building.

The base tag for each version is checked out separately inside build-staging. So you'd have build-staging/php/php-7.3.33/checkout and then also build-staging/php/php-7.4.32. This is a shallow clone of the tag so it's usually pretty fast.

Apart from that, I would also include a clear list of tools required to build the different languages / libs. This may be done directly by documentation. For example, include a Requisites section on the README.md file on every language / lib version.

You're right. I will add more information on this.

This addresses https://github.com/vmware-labs/webassembly-language-runtimes/issues/4


HIVE-26722: HiveFilterSetOpTransposeRule incorrectly prunes UNION ALL…

… operands

What changes were proposed in this pull request?

Changing the way RexSimplify is invoked in HiveFilterSetOpTransposeRule to make it conform the way it’s always used in Calcite when you have inferred predicates: here they are doing a big conjunction of all inferred predicates plus the pushed-down one, instead of passing the inferred predicates as a parameter of RexSimplify::simplify.
Why are the changes needed?

Correctness
Does this PR introduce any user-facing change?

No.
How was this patch tested?

Existing tests plus added the following qtest mvn test -Dtest=TestMiniLlapLocalCliDriver -Dqfile="union_all_filter_transpose.q" -Dtest.output.overwrite -pl itests/qtest -Pitests

LGMT


Add support of AsciiDoc

Language name
AsciiDoc
URL of example repository

https://github.com/asciidoctor/asciidoc-docs
https://github.com/eclipse/che-docs
https://github.com/viatra/org.eclipse.viatra

URL of syntax highlighting grammar
https://github.com/highlightjs/highlight.js/blob/main/src/languages/asciidoc.js
Most popular extensions
.adoc, .asciidoc, .ad, .asc
Detected language
There is none

Linguist already has support for AsciiDoc:
https://github.com/github/linguist/blob/32ec19c013a7f81ffaeead25e6e8f9668c7ed574/lib/linguist/languages.yml#L350-L359
It won't show up in your language statistics by default as it's considered prose and prose is not counted by default. If you want your repo to show AsciiDoc, you'll need to implement the linguist-detectable override in your repos.

Oh, thanks and sorry for the irrelevant issue then!


more consistent geometries handling

This PR aims to make handling of geometries more consistent.
The goal is that all functions that take geometries as input (e.g. extract, rasterize, boolmask, zonal) will behave consistently.
Progress:

[x] Implent an internal function
[x] Decide whether or not to add a geometrycolumn keyword
[x] Decide whether or not to allow point tables (e.g. tables with X and Y columns)
[ ] Update the docs

Do you want to give your two cents on these decisions @rafaqz?

I guess it's like mask where that's a fairly sensible thing to do. Maybe less so for rasterize

After looking into the test fails, I think we should not allowing the data argument in rasterize to be a Raster anymore.
Two things are tested: that rasterizing a Raster can return itself, and that rasterizing a Raster with a fill argument can return a RasterStack or Raster with fill values. The first is redundant, and there are much more intuitive ways to accomplish the second. Also, this behaviour is undocumented.
I think that for the most part mask, boolmask, and missingmask just pass their geoms to burn_geometry!.
I'll also add a geometrycolumn keyword to all the functions and allow for point tables. I agree it makes sense to allow point tables, there are many cases where you otherwise have to go out of your way to make a geometry column.

Ok let's delete it.

I've now implemented point tables. They will only be used if geometrycolumn is specified as a Tuple of Symbols, which I think is the way to go. Automatically detecting point column would open a whole can of worms and I don't think we want to go there.
I've made the docstrings more consistent throughout, but there might still be room for improvement to make them clearer. Same goes for error messages.
Also want to flag that functions such as boolmask now call _get_geometries twice, first because _init_bools calls _extent and then again in _burn_geometry!. I think this is a pretty minor problem and fixing it is not trivial.
I also still need to look at adding more tests.

Automatically detecting point column would open a whole can of worms and I don't think we want to go there.

Absolutely, users should always have to specify the columns.

Also want to flag that functions such as boolmask now call _get_geometries twice

Can we call _get_geometries at the top level before we do anything else? I know I'm a little pedantic with these things but they do add up, in both performance and in our mental models of "what happens in the algorithm".
boolmask is used in other methods too, so it should be one of the most optimised and simple things in the package.

Can we call _get_geometries at the top level before we do anything else?

That would be the way to go, I suppose. I just spent an hour or two on trying to make this work, without too much to show for my efforts so far.
If we do this, we need to have dedicated dispatches for all methods at lower levels on objects returned from _get_geometries, similar to how they dispatch on GeoInterface.Features, and so we need to add a bunch of dispatches.
Right now a function like extent just calls GI.trait, but that will return nothing for objects returned by _get_geometries, and so there is no way to discern those from all kinds of other objects that we want to call _get_geometries on.

Thinking about this a bit more, I guess an alternative approach could be to just add a dispatch for _get_geometries on AbstractVector and just make it return the object passed (maybe with a check_geometries keyword that defaults to false).
In that case some function calls would still have a bunch multiple calls to _get_geometries, but most of them have basically no cost, and we wouldn't need to add all those dispatches.

Don't we have to deal with user supplied vectors of geoms anyway?

Yes, but there's not a dispatch on it - _get_geometries just assume that if something is not a table it must be an iterable, and then check if all elements in the iterable are actually geometires.
So I do think we'll need some dedicated dispatch of _get_geometries.

Ah right. Yeah I wish GeoInterface traits worked on types then this could just compile away

We can also merge as is and I can tweak it later.

I think it makes sense to call _get_geometries at the top level and pass the resulting object. As long as _get_geometries returns doesn't Vector{Any}, any further calls of _get_geometries on it won't have any cost. This is also pretty easy to implement. I think that in practice the case with Vector{Any} will be quite rare.

Okay I have one more question: some methods (e.g. rasterize) have dispatches on GeoInterface traits (such as FeatureCollection) whereas others do not. I'm not so familiar with these - what objects could these be (other than those this PR covers already) and should _get_geometries work on these as well or not?

Probably they should all handle Feature/Feature collection.
For our purpose here Feature is a wrapped geometry (unwrap with GI.geometry) and FeatureCollection holds something like a vector of Feature (you iterate over it with GI.getfeature)

It's again failing on this
[3017] signal (6.-6): Aborted
in expression starting at /home/runner/work/Rasters.jl/Rasters.jl/test/resample.jl:9
ERROR: LoadError: Package Rasters errored during testing (received signal: 11)

which I don't get on my machine. So not sure where to start to fix this.

Damn that's just GDAL I'm not sure what's causing it, and no time to look until JuliaCon probably.
You could move the resample tests to the end?  Then we'll know this passed.

Something I did in the latest commit fixed it, so checks pass now! As far as I'm concerned this one is good to go, but maybe you could give it a look whenever you have time.

Can you rebase main?


is this project is officially dead?

if yes, please announce it on your web page and people could acknowledge what happens.
if no, let us know what is happening.
i'd like to help but i need to be sure that core team is working on it.

If the authors are still active on github it would be very much appreciated to get a response to this issue

None of the authors (I'm only one of them), afaik, use Disco in their current jobs.  It's up to active users to step up and take over maintainership/development. Ideally, this would be folks who run it everyday at scale.

Hello everyone,
I am working on reviving Disco Project again and I will start by upgrading the python version and would really appreciate any help from the erlang people =)
I wrote these two articles of my experience so far with Disco:
https://hefnawi.me/posts/disco-erlang-python-mapreduce/
https://hefnawi.me/posts/disco-erlang-python-mapreduce-part-2/
Not very comprehensive but I will dedicate some hours every week to push this project to life again.
This is my fork if you are interested: https://github.com/SecretsHive/disco
Thanks,
Hefnawi


feat(admin): Create initial admin scaffolding, settings and users pages (WIP)

Pull Request Template
⚠ Pre-Submission Steps:

Before starting work, make sure your main branch has the latest commits with npm run update
Run linting command to find errors: npm run lint. Alternatively, ensure husky pre-commit checks are functioning.
After your changes, reinstall packages in your current branch using npm run reinstall and ensure everything still works.

Restart the ESLint server ("ESLint: Restart ESLint Server" in VS Code command bar) and your IDE after reinstalling or updating.

Clear web app localStorage and cookies before and after changes.
For frontend changes:

Install typescript globally: npm i -g typescript.
Compile typescript before and after changes to check for introduced errors: tsc --noEmit.

Run tests locally:

Backend unit tests: npm run test:api
Frontend unit tests: npm run test:client
Integration tests: npm run e2e (requires playwright installed, npx install playwright)

Summary
Please provide a brief summary of your changes and the related issue. Include any motivation and context that is relevant to your changes. If there are any dependencies necessary for your changes, please list them here.
Change Type
Please delete any irrelevant options.

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

Testing
Please describe your test process and include instructions so that we can reproduce your test. If there are any important variables for your testing configuration, list them here.
Test Configuration:
Checklist

[ ] My code adheres to this project's style guidelines
[ ] I have performed a self-review of my own code
[ ] I have commented in any complex areas of my code
[ ] I have made pertinent documentation changes
[ ] My changes do not introduce new warnings
[ ] I have written tests demonstrating that my changes are effective or that my feature works
[ ] Local unit tests pass with my changes
[ ] Any changes dependent on mine have been merged and published in downstream modules.

Amazing work! I'll jump on a new branch soon to check it out.
My main question would be, is there any reason we aren't doing this in the client folder?
I have always thought that the client folder needs a bit of a restructure as its mostly about frontend stuff but I do feel like we should have a root folder for "backend" vs "frontend" code to keep things simplified and more spa app like

Amazing work! I'll jump on a new branch soon to check it out.
My main question would be, is there any reason we aren't doing this in the client folder?
I have always thought that the client folder needs a bit of a restructure as its mostly about frontend stuff but I do feel like we should have a root folder for "backend" vs "frontend" code to keep things simplified and more spa app like

@danorlando i second Clara’s sentiment, should really be in client folder, otherwise adding more complexity especially when it comes to building docker images

Also I think we could easily reuse the Auth components

Ideally, we should have the same auth, but just pages that are sectioned off using a middleware for admin only. No need for anything login related

Ideally, we should have the same auth, but just pages that are sectioned off using a middleware for admin only. No need for anything login related

Valid! Either way I'm thankful this is being worked on. Happy to help with this @danorlando

Amazing work! I'll jump on a new branch soon to check it out.
My main question would be, is there any reason we aren't doing this in the client folder?
I have always thought that the client folder needs a bit of a restructure as its mostly about frontend stuff but I do feel like we should have a root folder for "backend" vs "frontend" code to keep things simplified and more spa app like

@danorlando i second Clara’s sentiment, should really be in client folder, otherwise adding more complexity especially when it comes to building docker images

Well, this was why I brought this up in the last meeting we had as well as in the moderation channel. I wanted to make sure we had a discussion about it before I went and did it which was why I was pretty vocal about what I was planning before I started but no one spoke up when I said this was what I was doing.
Allow me to explain the reasoning behind this architectural decision...
The primary reason is for purposes of scalability. From an architectural perspective, the purpose of a mono-repo (ie. npm workspaces) is to be able to maintain independent, decoupled packages and applications that are separated by their context. This makes the code easier to maintain and build on top of, and it also has the benefit of allowing for the organizational structure to make sense for people who have never seen the code. If integration is an issue, the start script can run the admin app on a different port and if its an admin user, a button can be displayed in the nav that opens the admin app. I'm not sure how this translates to docker, but I will look into as its a pretty standard architecture so I'm sure someone has figured it out.
Another reason has to do with performance. The client already produces a fairly large bundle size as it is, which will continue to grow as more features are added.  I saw the comment about this increasing complexity, but I believe this is how we add an admin portal with the least amount of complexity. At the rate we are moving, consider how much code there will be 6 months or even a year from now.... by combining the applications, we'll have to  start adding suspense boundaries and lazy-loading components or make a move to server rendering entirely. I think we need to pay careful consideration to the performance implications if we want to continue to build on top of what we have, otherwise we'll eventually have to re-architect the whole thing when it becomes too much to manage.
I've been on projects before where the application became so bloated that it was hard to work with and the contributors lost interest. At work, my job is to think about the future of the code and put practices in place to guarantee it's longevity.  Rather than being concerned about keeping things separate, what we should be concerning ourselves with is how to separate things more. For example, we should really have another package to house UI components that can be shared between applications. Then they can use the same auth components. Things like having a reusable component library, a package to hold the business/data services layer, and applications separated by context that can run independently but are linked from the UI, are all standard practices in web application development, so I'm actually a bit surprised by the resistance. I understand that the sentiment is for the sake of simplicity, but I think we have to ask ourselves if it will really be making things simpler in the long run.
If after reading this you are still in agreement about moving all of the admin code to the client folder, I'll start thinking about how to structure it. I'll give you some time to think it over before I continue.

@danorlando
Thing is, we don't stand to gain from scalability if these packages are not setup so that they can stand independently. Currently, to make use of the data-provider for the backend, I'm running into several different errors and the solutions are very hacky to build the docker images with the introduction of data-provider, which is indicative of this problem. Ideally, these are setup so they can be shipped independently, and it's easy to miss when node_modules bubbles up resolution for packages.
LibreChat-API     | Clearing sync timeouts before exiting...
LibreChat-API     | node:internal/modules/cjs/loader:1093
LibreChat-API     |   throw err;
LibreChat-API     |   ^
LibreChat-API     |
LibreChat-API     | Error: Cannot find module 'react-dom'
LibreChat-API     | Require stack:
LibreChat-API     | -<EMAIL_ADDRESS>

The client already produces a fairly large bundle size

There's been no optimization efforts toward this. To this point, I made an easy swap of a dependency that had a large bundle size, and the bundle size is now 200 kb smaller. That said..

 I saw the comment about this increasing complexity, but I believe this is how we add an admin portal with the least amount of complexity.

I can get behind this point. But the problem of it standing independently should be first and foremost.

If integration is an issue, the start script can run the admin app on a different port and if its an admin user, a button can be displayed in the nav that opens the admin app.

I like these ideas

For example, we should really have a @librechat/ux-patterns package to house UI components that can be shared between applications

I think this might be overkill for now. I'm ok with re-using code to avoid this.
Long and short of it is, the monorepo setup thus far has added a list of backlog of items that no one really cares to address aside from myself. I'm hesitant to add more backlog for myself when there are clear goals in sight that I feel isolated in.

Long and short of it is, the monorepo setup thus far has added a list of backlog of items that no one really cares to address aside from myself. I'm hesitant to add more backlog for myself when there are clear goals in sight that I feel isolated in.

Ok, well we might as well move the data-provider back to the client then if it doesn't need to be used by more than one app or module.

Is it really worth going through the trouble of moving the admin to the client when it's practically done and DanO already spent a month on it?
I know I'm not much of a dev, but I personally find modular code much easier to work with. Modular components tend to be more flexible, easier to maintain, and replace when necessary.
Plus, having the admin section as a separate app has its perks, like the ability to run it selectively for security reasons instead of having it constantly running. Just my two cents!

Hey Team,
I get it—refactoring code might not be the most exciting task, but it's like spring cleaning. The sooner we tackle it, the easier it is. We've built LibreChat quickly as an MVP—a "first draft" to prove our concept. But as with any first draft, it's time to revise and improve. We're at a stage where we can make choices that will set us up for success in the long run.
Remember, good practices in software development aren't just fancy buzzwords; they're the building blocks of a stable and scalable product, based on empiric knowledges. Think of it as paying off a debt—the sooner we do it, the less it'll cost us in effort and stress down the line.
Yes, it'll be a challenge. New skills, and new methods. But that's what makes this field both demanding and rewarding. It's an opportunity to grow not just as coders, but as problem-solvers. What's the point to get involved in an Open Source project if it doesn't reward us with learning opportunity, which is the main reason to get involved in an Open Source project in the first place. Building a community, learning from each other and improving our skills to become more competitive in the market.
With the collective experience we have, especially some of us who've been around since the beginning like @danny-avila and @danorlando, we must align ourselves and realize the positive impact this will have. We'll have a more robust project and the freedom to add even cooler features down the line.
So let's come together, learn, and create something we're all proud of. Trust me, future us will thank today's us for making the wise decision.
Let's aim high and build something amazing together


Undertow global settings

https://github.com/hal/berg/issues/37
Transfer of tests from legacy TS at: https://github.com/hal/testsuite.next/blob/master/tests-configuration-undertow/src/test/java/org/jboss/hal/testsuite/test/configuration/undertow/GlobalSettingsTest.java

@vsalbaba update your branch please. There is a conflict otherwise LGTM.

Rebased,