Edit Community/Collection - Assign Roles/Groups

This is a PR for: https://github.com/DSpace/Rest7Contract/pull/105
A few notes on the implementation:

When creating tests for this one, we bumped into a few bugs in the new xml workflow beans, this PR includes fixed for those.
Some of the community/collections tests had full projections enabled while not being logged in as (community/collection) admin. We needed to alter this as the roles aren't public. Only admins are able to request a full projection.

@KevinVdV : I have not done a full code review here yet, but I wanted to add a comment on the Travis CI failures in this PR.  It looks to me like they are likely caused by not cleaning up the Groups that are being created in your new ITs related to Groups.  Essentially, a number of your ITs are testing out Group creation functionality & will actually create groups in the test database.  Since those groups are not being cleaned up (after the test completes), it results in this error (which essentially says more groups were found than were expected):
[ERROR] Tests run: 41, Failures: 4, Errors: 0, Skipped: 0, Time elapsed: 39.193 s <<< FAILURE! - in org.dspace.app.rest.GroupRestRepositoryIT
[ERROR] findAllPaginationTest(org.dspace.app.rest.GroupRestRepositoryIT)  Time elapsed: 0.97 s  <<< FAILURE!
java.lang.AssertionError:
JSON path "$.page.totalElements"
Expected: is <2>
     but: was <24>

This error would only occur if your new ITs are run before GroupRestRepositoryIT runs, so it may not be reproducible on all systems.  But, it's important to fix this problem as it shows that data is bleeding across several tests.
The proper fix here would to ensure you are calling GroupBuilder.deleteGroup([uuid]); in any test that successfully creates a new Group.  This is how similar ITs handle this scenario.  See for example: https://github.com/DSpace/DSpace/blob/master/dspace-server-webapp/src/test/java/org/dspace/app/rest/GroupRestRepositoryIT.java#L118-L122

Indeed, every test should clean up all of the objects that it creates.  But we also ought to be writing less-fragile tests which do not assume proper behavior of other tests.  Some ideas:

destroy all objects of the types you are testing with as the first action in a test, or in a common before-method;
if that is not possible, count the interesting objects at the start of the test and check the change in the count caused by the test.

@tdonohue Thanks, this was indeed the problem, we are now properly deleting the groups & the tests are working.
@mwoodiupui I agree with you, this is something that we might want to change, but this should ofc be done in a separate PR. Perhaps we should create a JIRA to keep track of this ?

@mwoodiupui & @KevinVdV : As a sidenote about automated data clean up prior to new tests running...that strategy is already in place for all REST API ITs.  That is the role of the various *Builder classes already: https://github.com/DSpace/DSpace/tree/master/dspace-server-webapp/src/test/java/org/dspace/app/rest/builder  When content is created via Builder classes, we have an automated method that deletes all Builder-created content prior to the next test being run.  However, as in this PR, there are situations where content must be created via calling REST endpoints directly (e.g. we need ITs that actually test the POST methods to see if they can create content).  In those scenarios, the Builder classes won't work, as you are creating content via a POST request, and therefore you must cleanup the created content in a more manual fashion (which is what I recommended here, and what has been implemented already, thanks @KevinVdV!).
So, I don't think this needs a JIRA ticket as we have a strategy for this already.  I'd also prefer the current strategy (of each test acting standalone & cleaning up after itself) rather than going back and changing all tests to be smarter about when data accidentally bleeds between tests.  That said, if someone wants to make that  specific GroupRestRepositoryIT.findAllPaginationTest() test a bit smarter (which was the one that failed here), I'm OK with it. It's just not high priority in my opinion.

@tdonohue Your feedback has been processed, we also added links to the workflow groups on the collection response (these weren't there before & are needed for the angular development).

While creating the angular UI some things popped up, we fixed these. This includes:

Workflow group requests will now return 204 if they aren't present (instead of 404), this aligns the behavior of workflow groups with the way the other (admin, default item read, ...) groups work
The link on the collection should be in the format: "/workflowGroups/{workflowRole}", in our previous code it was "/{workflowRole}"

I've tested this branch, and it worked correctly. Couldn't see any problems.
One of the complexities to handle in the future will be to allow collection admins to view all epeople (search, view their data, …) so they can add members and see the members of the current collection groups.
I haven't reviewed the code yet

@abollini Can you check if we have processed all your comments, I hope we didn't miss anything.

@abollini : Please re-review this. I'd like to get this moved forward as soon as possible this week.  It's looking (to me) like your feedback has been addressed, but if there are specific points that were overlooked, could you re-summarize them for us?

Hi @KevinVdV I flagged as solved all the discussion as appropriate so you can now find only the ones that still need action / clarification.
They are mostly related to cleaning up the IT changes that are not strictly needed (or add extra test/ticket to be sure that we don't weak our current tests).
An additional question: what we expect when a collection/community group is deleted? should the corresponding group be deleted as well or only the association should be removed?
in both case I recommend to include the answer in at least one delete test per group, i.e. if we expect the group to be completely removed also check that the group cannot be found using the eperson/groups endpoint, othewise check that the group is still here

@abollini I noticed you requested projection=full to be used where it's not applicable and permission may not allow that. It's not in scope for this PR to deal with #2726 and the changes from Kevin ensure the relevant data is still included.
The projection=full would work correctly and omit the private data if you'd merge #2726 in this branch (you're free to test this). If you'd want more use cases for #2726, feel free to create a JIRA ticket to verify all the desired use cases with projection=full. This may be useful if the implementation of #2726 would need to be refactored
Can we please keep this PR focussed on the Community/Collection Groups functionality, and not delay it due to the discussion on #2726

@KevinVdV : This PR has new test failures now, caused by the latest commit (to correct a previously ignored test).  I'm not sure how these new test failures have appeared, as they seem unrelated to the most recent commit.
I'll dig around, but if this seems to be related to the unnecessary IT refactoring in this PR, then I'd also recommend that we consider reverting all the unrelated IT changes.  As I previously noted, I think this PR is becoming harder and harder to review/correct ITs, as there's a lot of unnecessary, unrelated changes applied...so it's difficult to determine what is causing the new failures.

@KevinVdV , @benbosman and @abollini : I've dug into this PR a bit more today.  I now believe that the Projection-related changes in this PR are required for this PR to pass existing tests.  Previously, that was unclear to me based on this PR's current description, but it is likely "implied" by the second bullet (after I read it again).  Essentially, projection=full seems to now require admin-level access whenever one of these groups will end up in the embed list.
Here is the test that I performed today where I was able to prove this:

First, I've created a new branch in my personal GitHub which is identical to this PR, except removes all the Projection-related changes.

There's one commit that reverts all changes from projection=full to embed=[list-of-embeds]
There's a second commit that reverts all changes from projection=full to projection=level and restores all removed projection=full params.

The Travis CI build results for the above custom branch can be found below.  The results are a large number of 401 or 403 errors from every test that uses projection=full on a Community/Collection without first authenticating as someone with Admin-level access.   You can see some of those errors starting here: https://travis-ci.com/github/tdonohue/DSpace/builds/160411618#L5522

Based on that, it looks to me like one of the current behaviors this PR makes obvious is that projection=full REQUIRES admin-level permissions whenever an admin-restricted object is encountered.  So, now it makes perfect sense why @KevinVdV has chosen to reanalyze all usages of projection=full to ensure it was only used for admin-level ITs (and instead use projection=level or embed=[limited-list-of-embeds] for ITs that involve anonymous-access or basic eperson access).
My assumption here is that Admin-level permissions are now required for projection=full because #2726 has not yet been resolved. So, the REST API is trying to return all embedded resources, and if some are restricted to Admins, it then restricts the entire request to Admins and returns a 401 or 403 based on whether the request is anonymous or a basic eperson.
Based on this entire analysis, @abollini's projection-level questions above may be answered. The changes in this PR to ITs that previously used projection=full are required to pass current tests.  However, once #2726 is resolved, that PR may again allow projection=full to be used by non-Admin users (assuming restricted embedded objects are filtered out of embeds automatically).

hi Kevin, I only did functionality tests when you log in as administrator and as anonymous, the messages are correct with each user

Merging as this is at +2 and now passes all tests.  The above JIRA tickets (created by @abollini ) will be added to the Release Plan spreadsheet as follow-up tasks.


Keybase Chat dropping messages

Keybase chat is dropping messages. If I send off a lot of messages in rapid succession, sometimes one of the later messages will replace one of the earlier ones.
Keybase Version: 4.4.1-20190909184517+b5f8897c2a
OSX Version: 10.14.6

Are you sure it's not a UI bug?  try switching tabs and the coming back to the chat that has the dropped message.

It persisted when switching tabs and even closing the window (keybase running in background). I will try completely restarting the client next time and see.
 It seems to have to do with network problems, though.


Devel michael

PR of devel_michael into devel

adds metabolite curation by @michaelwitting
adds new pathway curation by @michaelwitting

Hi Michael, looks like there's some metabolites that are in reactions that are missing from the metabolites tsv (I think).
Will generate a list when I get to my desktop tomorrow morning.


[Memory consuming] Dotlottie uses too much memory despite its smaller size compared to json

JSON file (1.2MB):

and the .lottie(848kb) :

I'm using Swiftui for development, The .lottie file saved 30% of the app size but it seems too laggy on launch and presentation

hi @hoansgithub would you be able to share the file?

thanks @samuelOsborne for your tips, here is the file and I hope this helps!
ob1.lottie.zip


Support for creating consent resources

Although there is the ability to associate a consent with a fusionauth form field via the consent_id property, there is currently no way to create new consents via terraform. Please add support for creating consent resources.

Agree, this would be very useful. Maintainers, do you have plans to add this anytime?


Error with SSL socket of APNS

I've got this problem recently with creating socket of APNS
[SSL: SSLV3_ALERT_CERTIFICATE_UNKNOWN] sslv3 alert certificate unknown (_ssl.c:600)
The related line in apns.py
sock = ssl.wrap_socket(sock, ssl_version=ssl.PROTOCOL_TLSv1, certfile=certfile, ca_certs=ca_certs)
Does anyone get this?

@tridc Can you post the stack trace?

Here is the trace:
Traceback (most recent call last):
File "/home/tridc/git/pushnotif/tasks.py", line 77, in send_push_notification
apns_devices.send_message(message, env=apns_env)
File "/home/tridc/git/push_notifications/models.py", line 91, in send_message
r = apns_send_bulk_message(registration_ids=reg_ids, alert=message, application_id=app_id, **kwargs)
File "/home/tridc/git/push_notifications/apns.py", line 247, in apns_send_bulk_message
with closing(_apns_create_socket_to_push(application_id, env)) as socket:
File "/home/tridc/git/push_notifications/apns.py", line 81, in _apns_create_socket_to_push
return _apns_create_socket((SETTINGS["APNS_HOST_PROD"], SETTINGS["APNS_PORT"]), application_id)
File "/home/tridc/git/push_notifications/apns.py", line 74, in _apns_create_socket
sock.connect(address_tuple)
File "/usr/lib/python3.5/ssl.py", line 1019, in connect
self._real_connect(addr, False)
File "/usr/lib/python3.5/ssl.py", line 1010, in _real_connect
self.do_handshake()
File "/usr/lib/python3.5/ssl.py", line 988, in do_handshake
self._sslobj.do_handshake()
File "/usr/lib/python3.5/ssl.py", line 633, in do_handshake
self._sslobj.do_handshake()
ssl.SSLError: [SSL: SSLV3_ALERT_CERTIFICATE_UNKNOWN] sslv3 alert certificate unknown (_ssl.c:645)
A few times I tested push works properly. Does it seems to be APNS server's problem?

@tridc Sorry, I'm drawing a blank here, too.  I thought it might have something to do with gunicorn and gevent monkey patching the SSLSocket implementation.  But it doesn't look like it.

I found out the reason, it's my certificate. Thanks for your comment.

@tridc I am running into the same issue. What steps did you take to fix this problem? Would a new certificate fix it? Not really familiar with the whole process, any insight would be helpful
Best,
Flavio

@FlavioAlexander it's only because my certificate is invalid and rejected by APN server.


core: ci scripts overhaul

Closes #1579
This PR aims to do 2 major things

Only run tests for modules that have actually been updated.
Converts scripts from Bash to JS

Could you go comment-crazy in the files, in terms of headings to each major file / function on what it's purpose is?

I think we might need an overhaul on what a build is and what a release is. Since Travis doesn't publish to npm for us anymore, what distinguishes the two?

Topics that would be awesome if they were covered in the "Developer's Documentation" code comments:

What a build is, what a release is, what triggers each, etc.
An overview of the chain of events that take place
How CI runs code coverage (is it only running and reporting it once now?)

I have some more code-specific confusions, but I'll wait to see something like ^^ before I confuse us both by asking.

@stephenplusplus I went ahead and added a bunch of docs/comments to build.js - PTAL and let me know if you're cool with the format, then I'll do the others.

I went ahead and added a bunch of docs/comments to build.js - PTAL and let me know if you're cool with the format, then I'll do the others.

They're beautiful 😢

Is there anything left to do on this before I review?

@stephenplusplus I think it's good to go!


DLL load failed: The specified module could not be found.

My system has two environments:
python 3.7.6 (base)
python 3.7.7 (rasa)

Situation - 1
Python interpreter selected in VS code: 3.7.6 (base)
Environment selected in Terminal: (rasa)
Run a python file: basic.py
Error as below:
(rasa) C:\Users\sonal\Google Drive\10_Python\1_1_My_Projects>C:/ProgramData/Anaconda3/python.exe "c:/Users/sonal/Google Drive/10_Python/1_1_My_Projects/basic.py"
C:\ProgramData\Anaconda3\python.exe
C:\ProgramData\Anaconda3\lib\site-packages\numpy_init_.py:140: UserWarning: mkl-service package failed to import, therefore Intel(R) MKL initialization ensuring its correct out-of-the box operation under condition when Gnu OpenMP had already been loaded by Python process is not assured. Please install mkl-service package, see http://github.com/IntelPython/mkl-service
from . import distributor_init
Traceback (most recent call last):
File "C:\ProgramData\Anaconda3\lib\site-packages\numpy\core_init.py", line 24, in
from . import multiarray
File "C:\ProgramData\Anaconda3\lib\site-packages\numpy\core\multiarray.py", line 14, in
from . import overrides
File "C:\ProgramData\Anaconda3\lib\site-packages\numpy\core\overrides.py", line 7, in
from numpy.core._multiarray_umath import (
ImportError: DLL load failed: The specified module could not be found.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "c:/Users/sonal/Google Drive/10_Python/1_1_My_Projects/basic.py", line 4, in
import numpy as np
File "C:\ProgramData\Anaconda3\lib\site-packages\numpy_init_.py", line 142, in
from . import core
File "C:\ProgramData\Anaconda3\lib\site-packages\numpy\core_init_.py", line 54, in
raise ImportError(msg)
ImportError:
IMPORTANT: PLEASE READ THIS FOR ADVICE ON HOW TO SOLVE THIS ISSUE!
Importing the numpy c-extensions failed.

Try uninstalling and reinstalling numpy.

If you have already done that, then:

Check that you expected to use Python3.7 from "C:\ProgramData\Anaconda3\python.exe",
and that you have no directories in your PATH or PYTHONPATH that can
interfere with the Python and numpy version "1.18.1" you're trying to use.
If (1) looks fine, you can open a new issue at
https://github.com/numpy/numpy/issues.  Please include details on:

how you installed Python
how you installed numpy
your operating system
whether or not you have multiple versions of Python installed
if you built from source, your compiler versions and ideally a build log

If you're working with a numpy git repository, try git clean -xdf
(removes all files not under version control) and rebuild numpy.

Note: this error has many possible causes, so please don't comment on
an existing issue about this - open a new one instead.
Original error was: DLL load failed: The specified module could not be found.

Situation - 2
Python interpreter selected in VS code: 3.7.6 (base)
Environment selected in Terminal: (base)
Works fine

Situation - 3
Python interpreter selected in VS code: 3.7.7 (rasa)
Environment selected in Terminal: (base)
Works fine

Situation - 4
Python interpreter selected in VS code: 3.7.7 (rasa)
Environment selected in Terminal: (rasa)
Works fine

Hi @sonalrp5 👋 Please answer a few questions for me

Environment selected in Terminal: (rasa)

Did you manually activate the environment in the terminal?

Run a python file: basic.py

How are you doing that? Is it the extension sending the command below? If yes, is Python the name of the terminal that appears?
(rasa) C:\Users\sonal\Google Drive\10_Python\1_1_My_Projects>C:/ProgramData/Anaconda3/python.exe "c:/Users/sonal/Google Drive/10_Python/1_1_My_Projects/basic.py"

Note the extension simply creates a terminal by the name Python & sends the activation command:
<path to the interpreter selected> <file path>
c. If terminal by the name Python already exists, it simply sends the activation command. It doesn't check if the environment activated the terminal Python is something else (there's no way for the extension to check that). So if that's the case you're running into it's the expected behavior.

Closing as no further info was provided.


Minor typo: Getting Started- Part 4

Proposed changes
Changed:
... change the app behavior be editing code
To:
... change the app behavior by editing code
Unreleased project version (optional)

Related issues (optional)

Thanks, @edsfocci :)


V1 Release

It has been half a year and uinix-ui's API is mostly stable and functional.
Will be planning a V1 release with some considerations below:

Confirm types (perhaps even loosening them) in favor of DX.
Refactor to monorepo (allowing installations of just components and system).
Further increase configuration:

allow system to store and retrieve anything.  This may involve changes in the hooks API to be more generic.
allow custom plugins to be provided (these will be re-typed and re-documented to decouple from Fela).

Update and simplify documentation
Expose helpful utilities (e.g. evaluating themed styles to actual styles)
[Help wanted] Broadcast to JS ecosystems (Vue, Hyperscript, Solid, Mithril).

A quick update that I am still planning on shipping V1 around May 2022.

I've used uinix-ui successfully in a number of projects and demos and the API is largely stable (we'll simplify this further, and introduce more configurable APIs e.g<EMAIL_ADDRESS>is fully configurable).
I am currently using uinix-ui in my current company, and aside from small number of bugs, it's proven to work and scale for larger development.
Will be busy until end of April but should obtain relatively strong signals for a V1 release after consolidating and further simplifying the API.

Around June/July 2022, I'll do some due diligence in 'marketing' to other JS communities and ecosystem.  uinix-ui for most parts is a fairly 'quiet' project, but would love some help from folks who are interested to broadcast and give a shoutout to ecosystems after we are slated for a V1 release.

<EMAIL_ADDRESS>has been released, which can further narrow the responsibility of uinix-ui to simply integrate against the system of four components.
Summary of tasks for @1.0.0 release

[ ] Confirm (simplified) V1 API.
[ ] Cleanup/simplify code and tests (theme-related features now live in uinix-theme).  Consider getting off cypress
[ ] Address outstanding bugs
[ ] Update/confirm types
[ ] Update/simplify docs
[ ] Update/verify in uinix-docs
[ ] [Maybe] Refactor to monorepo of packages

This post tracks API changes (will be updated as v1 development is underway).
New Features

New configuration (enableCssVariables, namespace).

Breaking Changes
Removed

Remove styles.typography (also removes rendering font support).
Remove default theme spec (consumers must explicitly provide one).

Changed

styles.breakpoints is now moved to config.responsiveBreakpoints.
Icon no longer conditionally renders  as button or div (consumers now control this).
Various type interface changes.

V1's API has been reduced and finalized in https://github.com/uinix-js/uinix-ui/blob/c2d7f40076f2764d14830d57b3161ed71e710634/index.js.
This greatly minimized API facilitates upcoming internal tasks:

[ ] Update types
[ ] Update tests
[ ] Update docs


[Updater] Remove job_id from the Service/ApiClient's method signatures

I'm in the process of rewriting the Service/ApiClient's methods to accept a value class rather than a set of arguments so it is easier to slot in a "GroupRule" as a new optional argument without having to modify the whole way up and down the call chain as I iterate on it.
Unfortunately, this means modifying the whole way up and down the call chain one last time! 😅
Since I'm doing this, I'm going to cross of a bit of technical debt which is that we currently instantiate the ApiClient with the Job's token, but then pass the Job's ID on every method call.
This makes our stubbing and method signatures very verbose and since a token is scoped to a Job ID, it creates the impression the client could be used to reach across jobs within a single context when it can't.
Let's clean this up and consolidate the id/token as a matched credential pair.
Rationale
This is a noisy change so I've pulled it out as a separate PR to fly ahead of the rest of my changes to make it easier to review/test in isolation.
Other changes
As part of this, I've made the opinionated change to rename token to job_token just to avoid confusion between it and any of the credentials we handle in some places.

Glad to have the smoke tests as they seem to indicate I've missed a few touch points


Allow error callback in MessageDispatchers

This PR introduces MessageDispatcher.onError() and makes implementations to call the method when dispatching causes an exception.
Other notable changes:

Environment class ”moved” to the base project.
causedByRejection() utility method was added to Commands.
Testing utility classAggregateCommandDispatcher was renamed to AggregateMessageDispatcher and got method for dispatching EventEnvelope.
EventSubscriber now catches dispatching errors and passes them to onError().

@armiol, I can eliminate one TODO after migrating to base version based on this PR.

@armiol, PTAL.


Black textures if no S3TC support is available.  No error messages or warnings.

Versions
Godot: 2.1.4 stable (precompiled x86_64 download from site)
Kernel: Linux 4.12.13_1 #1 SMP PREEMPT Thu Sep 14 13:15:00 UTC 2017 x86_64 GNU/Linux
GPU: AMD Barts PRO [Radeon HD 6850], from circa 2011
Graphics drivers: In-kernel "radeon" (standard mesa, X11, etc stack)
Distro: Void Linux
Issue description
Without the S3TC (libtxc_dxtn) library for Mesa installed: all/most textures appear solid black.  No errors, warnings or explanations are provided.
Truck town:

Installing this library fixes the problem.
Expected behaviours
(1) Godot does not try to use compressed textures when support for them is not available.
(2) Errors or warnings are given in either case.

Previous S3TC support check discussion - 378b1e6cf0cbcc9c30c61e0cabc7090f70fd380c and #10139, patent on S3TC expires in 4 days.

Mesa version?
This sounds like a driver issue and may be fixed on a more recent Mesa version, if you can, try Mesa 17.3.

@eon-s by default S3TC is not in Mesa, it is implemented as external library.
https://dri.freedesktop.org/wiki/S3TC/

...which should change soon since the s3tc patents will expire next Monday.
On Arch Linux, the package name is libtxc_dxtn.

I suspect that many distros will be slow (months) to bundle it into the main mesa package after the patents expire (assuming they don't have other organisation reasons to keep it separate).  A warning would still be greatly appreciated -- I'm lucky enough to know about the texture compression scene and what keywords to search for in my repos, most people are not.

We should probably try to detect this and throw an error, the problem is
that many OpenGL implementations consider it as part of core (OSX), so the
extension is not even listed. It's kind of difficult to "detect" without
several hacks.
On Sat, Sep 30, 2017 at 7:58 PM, Veyrdite<EMAIL_ADDRESS>wrote:

I suspect that many distros will be slow (months) to bundle it into the
main mesa package after the patents expire (assuming they don't have other
organisation reasons to keep it separate). A warning would still be greatly
appreciated -- I'm lucky enough to know about the texture compression scene
and what keywords to search for in my repos, most people are not.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/11679#issuecomment-333341384,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF-Z2w8oaK7dgVy4bKJmktsDRSbbTqEFks5snseRgaJpZM4PoKQw
.

many OpenGL implementations consider it as part of core (OSX), so the extension is not even listed

RGTC is core since version 3.0, not listed on macOS, and not covered by S3 patent (there is no colour interpolation). S3TC is not core in any version and it is listed on macOS.

oh alright, we could try throwing a warning if not detected then..
On Sun, Oct 1, 2017 at 5:43 AM, bruvzg<EMAIL_ADDRESS>wrote:

many OpenGL implementations consider it as part of core (OSX), so the
extension is not even listed
RGTC is core since version 3.0, not listed on macOS, and not covered by S3
patent (there is no colour interpolation). S3TC is not core in any version
and it is listed on macOS.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/11679#issuecomment-333362250,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF-Z25QAFfJCj7KXO4P5bUUCy8OYp-XHks5sn1DDgaJpZM4PoKQw
.

https://lists.freedesktop.org/archives/mesa-dev/2017-October/171265.html

Godot: 3.0 (63283ec)
Kernel: 4.10.0-38-generic #42-Ubuntu SMP Tue Oct 10 13:24:27 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
GPU: GF108M [GeForce GT 540M]
Driver: Nouveau
Distro: Ubuntu 17.04
Confirming that this is still an issue even with updated drivers, an error would be useful. Installing libtxc-dxtn-s2tc manually fixed the problem.


Add example notebook for scatter geodesics animation.

Also, fix a minor bug in animation color.
@shreyasbapat

@shreyasbapat changes done.


route() does not routing anywhere

I want to redirect, for example, after a successful login, to the home page. And for this I wait for a response, and then redirect via route('/'), but nothing happens.
This is my login page
export const LoginPage = ({ handleLogin, fromPath }) => {
    const handleSubmit = async (event) => {
      event.preventDefault();
      const { username, password } = event.target;
      const response = await fetch(env.SERVER_URL + '/login', {
        method: 'POST',
        headers: { 'Content-Type': 'application/json' },
        body: JSON.stringify({ username: username.value, password: password.value }),
      });
      if (response.ok) {
        const { message, token } = await response.json();
        route(fromPath, true);
      } else {
        // Handle login error
        alert('Login failed!');
      }
    };

    return (

Login Page

        <form class="login-form" onSubmit={handleSubmit}>
          <input type="text" name="username" placeholder="Username" required />
          <input type="password" name="password" placeholder="Password" required />
          <button type="submit">Login</button>
        </form>

    );
  };

But it does not route this not only on the login page. It doesn't work anywhere. What am I doing wrong?
And at the same time routing trough Router and Route components work fine. And Link component also redirects fine.

So... do not mix packages)
My Route and other route components were from package preact-iso. I replaced the package with preact-router and everything started working fine.


export vars are lost/reset upon saving a script with a syntax error

Operating system or device - Godot version:
Ubuntu 16.04
Issue description (what happened, and what was expected):
If you restart the project with an error in the script, then the reset value of the variable in the Inspector.
Steps to reproduce:

export var test = 'a'
The inspector 'a' change to 'b'
Add a string to simulate errors.
export var test = 'a' x
Save the project and restart the project.

I can confirm the bug. If you save a script with a syntax error (be it at the global scope as shown by @DimaKiva, or within a function such as e.g. get_node( in _ready()), the export vars are removed, and thus their values are lost from the scene.

Still relevant in master.

Hm, I thought #20583 would fix this, but apparently it didn't.

Please fix this issue. Making any changes to a tool node is basically impossible in a more complicated game, because the values reset in every single instance.

This should have been fixed by #20583. I will have a look.

I'm still encountering this issue on the current master :(

@DualMatrix Can you open a new issue with the steps to reproduce it?

@neikeq I'm able to reproduce this issue on master, with the exact same steps, except you need to save the project 2 times in a row in step 5. Do I need to open a new issue?


We renamed the master branch to main. Read about it here.

Renaming master branch to main
As a part of a broad effort to avoid problematic terminology in our software, we are renaming our default branch from master to main. We recognize that this is only a small step, but it is an opportunity to make our project and community more welcoming to historically marginalized communities.
How does this impact my development process?
There should be very little impact. GitHub will surface the branch name change in your fork, if you have one. For new forks, you will automatically have main as the default branch.
We encourage the use of feature branches for local development. The only change in practice is changing which branch your feature branch is started from. When sending Pull Requests on GitHub, the target will default to our main branch, so there are no changes to make there.
I have a lot of tools that depend on master being the upstream branch name. How can I fix that?
master has always been only a default value and a number of projects have used other names for their primary development branch for years. We encourage updating your tooling to instead dynamically determine the branch to use. This article provides insight into how you can do that. Additionally, you can always set up a branch locally of any name to track our main branch.
I'd like to do this for my own projects, do you have any documentation on how this works?
GitHub has published a guide documenting their tooling. We recommend reading that and the accompanying documentation.
If you're a Facebook employee looking to do this for a project you maintain, please reach out to the Open Source Team.

This can probably be closed now, nobody complained :)

No-one can possibly complain, since the conversation is locked😄Anyways, I don't think they have reasons to anyways


Running errors and parameter initialization problems

Hi Felix,
I have these questions.
I run lyapunov_function_learning.ipynb and got an error like this.
ModuleNotFoundError: No module named 'safe_learning'
And I don't quite understand how the initialization parameters of the Lyapunov function are obtained.

In all the files, I did not find it.So where can I find this safe_learning module?
Could you please explain in detail how the parameter initialization is done?

Thanks for your reply!
As you said, safe_learning is the name of the module provided in this repo, but I still want to find the definition of safe_learning to understand the code of this paper.
One more question, do you think the code can be reproduced in MATLAB?

I'm not sure I understand your question: the safe_learning module contains the paper code. All you need to do is to follow the installation instructions for it to be found.
Regarding matlab: I would assume it's possible, but it's been a very long time since I last used matlab.

What I mean is that I'm running your code with the error that the module safe_learning is missing, so I can't run your code properly, but I can't find this module in all your folders.
So what I want to know is how to find it and then run your code without any problem. I don't know if this makes sense to you.
I just want to run your code successfully to understand some of the ideas you have in your paper.
Thank you very much for reading!

This issue is described in the following figure.

I am very sorry!
Your previous answer to this question was clear enough, I was the one who didn't understand what you meant, now I figured it out.
Have a nice life!


💡 [Feature]: Add support for picking LLM model for GitHub Copilot chat participant

🎯 Aim of the feature
Currently in preview GitHub Copilot added the functionality to select the LLM model you want to use in the response

We should check if we may adapt SPFx Toolkit Chat participant to also use it. Currently we use GPT 4o
📷 Images (if possible) with expected result
No response
🤔 Additional remarks or comments
No response

so it is described here
https://code.visualstudio.com/api/extension-guides/language-model
"Once you've built the prompt for the language model, you first select the language model you want to use with the selectChatModels method. This method returns an array of language models that match the specified criteria. If you are implementing a chat participant, we recommend that you instead use the model that is passed as part of the request object in your chat request handler. This ensures that your extension respects the model that the user chose in the chat model dropdown. Then, you send the request to the language model by using the sendRequest method."
example: https://github.com/microsoft/vscode-extension-samples/blob/main/chat-sample/src/simple.ts

Since I cannot seem to make it work with latest VS Code update lets wait a few weeks until it will get out of insiders and into standard VS Code version before we open it up


Clean up unused imports

I was building ghc and noticed a few unused import warnings.

@bgamari

also this
utils/haddock/haddock-api/src/Haddock/GhcUtils.hs:119:1: warning: [-Wincomplete-patterns]
    Pattern match(es) are non-exhaustive
    In an equation for ‘hsTyVarBndrName’:
        Patterns not matched: XTyVarBndr _
    |
119 | hsTyVarBndrName (UserTyVar _ _ name) = unXRec @n name

Is this patch specific to GHC's integration of Haddock or can it be merged in the normal branches as well?

I am not 100% sure but I opened PR against haskell:ghc-head so must be the former?

As per the CONTRIBUTING document:

If your patch consists of glue code and interface changes with GHC, please open a Pull Request targeting the ghc-head branch.

Otherwise, for improvements to the documentation generator, please base your pull request on the current GHC version branch (ghc-9.0 for instance). The PR will be forward-ported to ghc-head so that documentation built within GHC can benefit from it.

I'll let you re-target the PR to the proper branch (9.2 as of today. :)

Hi!  As of today, patches for the ghc-head branch must be done on the Haddock mirror on GitLab, at https://gitlab.haskell.org/ghc/haddock.


Improve Inno Setup installer script

@Timthreetwelve
Please check and merge. Thanks.

@Timthreetwelve
Could you please merge this?
Then I can continue to develop this.


AutoSave Feature (Overtaken by #891)

My friends and I have all experienced closing the browser and finding no savings. Especially for freshmen, they may not know they need to save when they first use this tool. So, I think adding an autosave feature will improve usability.

The creation or login UserID is displayed if the user does not automatically log in to the previous UserId when adding a course.
Autosave can call every minute, or every time after adding, deleting, or making any changes (but this may give the server a lot of pressure?).

Autosave when the user closes the website. (could be a setting)
Pop up a window to let the users choose to save it, or leave the website.

Problem: For mobile users, the pop-up may not show. Do you have another autosave feature on mobile?

The First draft is done. Waiting for review #865

Completed by #891


adjust getting started to use of setup.py

Is the use of setup.py intended to set up simply? If yes should'nt getting started be adjusted accordingly?

It is stated as second option:
# or (2) use setup
pip install -e .


Code to delete @usernames and links of forwarder messages??

hi i have a telegram forward bot in python and need code to delete of the forward messages all mentions @username and all links http://t.me/........

Bot API couldn't do this, however.
Try to use an user account to finish this task.
(off topic)

@kraozen Sorry, I didn't get it. Are you going to remove some content of the original message? Perhaps you could use regular expressions.


add evaluation window config [Dynamic Alerts]

Changes for this can be found here: https://github.com/DrDroidLab/PlayBooks/pull/434/files


Fix Azure storage for assets

Though the documentation claims you can use any protocol that Smart Open supports, Azure storage accounts don't work. I wrote a quick fix to get it working.
Description
Smart Open allows providing transport parameters, which are optional, unless you're using Azure storage containers, then they are required and must include a client that has the connection string.
I made a quick fix to grab the connection string from the environment variable AZURE_STORAGE_CONNECTION_STRING if the URL is Azure. I know I probably didn't follow conventions correctly, but I needed to use Azure and that got it working.
Types of change
Small change to remote.py.
Checklist

[x] I confirm that I have the right to submit this contribution under the project's MIT license.
[x] I ran the test suite, and all new and existing tests passed.
[x] My changes don't require a change to the documentation, or if they do, I've added all required information.

So after this I moved on to remote storage with push and pull, and ran into another problem.
Smart Open expects Azure URLs to start with azure://, but Cloudpathlib expects az://. So when Cloudpathlib sees azure:// it thinks it's a local file path and changes it to azure:/, with the added bonus on Windows that it becomes azure:\ instead (along with all the other slashes). This prevents Azure from working for remote storage even after the above fix.
I pushed another commit to replace az:// with azure:// in remote.py before passing it to Smart Open, which feels a bit hacky but I don't know how else to get it working.


Signup.jsx: Implement Signup functionality using Firebase Authentication

Design link
Hex Codes
Referring to the designs above,

Create an aesthetic and responsive Signup Page, and stick to the hex codes using in the design.
Refer to context/AuthContext.jsx, where functionality for signup is provided. You need to implement the signup method in the onSubmit handler.
On signup, I want a user, having a document ID set to that of the corresponding User UID(Firebase Auth), to be created in the users collection, where you store additional data related to the user(essentially all the details related to the user except for the password).

Hi @sikehish please assign me this issue under Hacktoberfest2023

I've assigned it to you. Good luck!

@sumit-kumar-jha1709 Any update?

hi @sikehish working on final styling the toasts.

@sumit-kumar-jha1709 Alright.


Add calls and online time to replace tps in graphQL protocol

For a low throughput system, tps is always 0. For improving that, I proposal to add calls and online time in those services. Just keep tps in protocol before 5.0-GA, marked as Deprecated in GraphQL service.
I will pull request protocol changes soon.

Remove this enhancement requirement. All metrics are now based on cpm(calls per min) instead of tps.


[BugFix] Fix compile error in aarch64

Why I'm doing:
What I'm doing:
Fixes #issue
What type of PR is this:

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

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

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

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

[ ] This is a backport pr

Bugfix cherry-pick branch check:

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

[x] 3.3
[ ] 3.2
[ ] 3.1
[ ] 3.0
[ ] 2.5

https://github.com/Mergifyio backport branch-3.3.6

https://github.com/Mergifyio backport branch-3.2

https://github.com/Mergifyio  backport 3.2.13

https://github.com/Mergifyio backport branch-3.2.13


django-heralder has missing migrations when DEFAULT_AUTO_FIELD is not django.db.models.AutoField

Steps to reproduce:

Install Django==4.1.6 and django-heralder==0.3.0
Start a new Django 4.1.6 project with django-admin startproject project_name
Verify that the default value for settings.DEFAULT_AUTO_FIELD in the newly generated Django project is django.db.models.BigAutoField
Add herald and django.contrib.sites to INSTALLED_APPS
Run ./manage.py makemigrations

Expected result:
Makemigrations would output that there are no changes detected.
Actual result:
A new migration is created with the following contents:
$ cat venv/lib/python3.11/site-packages/herald/migrations/0006_alter_notification_id_alter_sentnotification_id.py
# Generated by Django 4.1.6 on 2023-02-06 18:55

from django.db import migrations, models

class Migration(migrations.Migration):

    dependencies = [
        ('herald', '0005_auto_20180516_1755'),
    ]

    operations = [
        migrations.AlterField(
            model_name='notification',
            name='id',
            field=models.BigAutoField(auto_created=True, primary_key=True, serialize=False, verbose_name='ID'),
        ),
        migrations.AlterField(
            model_name='sentnotification',
            name='id',
            field=models.BigAutoField(auto_created=True, primary_key=True, serialize=False, verbose_name='ID'),
        ),
    ]

This is to be expected -- Django changed the default_auto_field to BigAutoField  when generating a new app however the current default for backwards compatibility in settings is still AutoField.
https://docs.djangoproject.com/en/4.1/releases/3.2/#customizing-type-of-auto-created-primary-keys

Maintaining the historical behavior, the default value for DEFAULT_AUTO_FIELD is AutoField. Starting with 3.2 new projects are generated with DEFAULT_AUTO_FIELD set to BigAutoField. Also, new apps are generated with AppConfig.default_auto_field set to BigAutoField. In a future Django release the default value of DEFAULT_AUTO_FIELD will be changed to BigAutoField.
To avoid unwanted migrations in the future, either explicitly set DEFAULT_AUTO_FIELD to AutoField:
DEFAULT_AUTO_FIELD = 'django.db.models.AutoField'

Yep, that is what I did for a newly generated Django project that used django-heralder.
It would be great if you consider adding an app-level default_auto_field so if users decide that they would prefer DEFAULT_AUTO_FIELD to be a different kind of field other than AutoField, django-heralder's models would not be affected.
The folks over at Wagtail and Django-CMS have it set up that way so their core models' primary keys are independently configured from the user's project's settings.

I no longer help maintain this project because don't reliably has the ability to release on PyPi anymore.  At DjangoCon US 2022 sprints, a group of us forked the project to Django-Heralder so we could do releases for bug fixes.
I created an issue that regarding what we are discussing here:
https://github.com/peterfarrell/django-heralder/issues/30
We welcome a PR that set the default_auto_field at the application level for Django-Heralder.
Heralder is also on PyPI - v.0.3.0 is equivalent to Django-Herald 0.3.0:
https://pypi.org/project/django-heralder/

@b-ggs - totally got confused on which project I was commenting on -- this is Heralder... sigh

@b-ggs  Your PR has been merged. Thanks for much for the contribution!


kitti_player launch bug or config issue '//'

Bug
Expected Behavior
kitti_player launches and runs without errors
Actual Behavior
kitti_player launches, begins seting up topics, then throws an error and dies:
IOError: [Errno 2] No such file or directory: '/home/luke/Autoware1.9/Autoware/ros/src/util/packages/kitti_pkg/kitti_player/dataset/2011_09_26/2011_09_26_drive_0093_sync//tracklet_labels.xml'
and dies

tracklet_labels.xml does exist under this path without the miscellanaous double '//' at the end - so presumably there is a typo in a config file somewhere?

Steps to Reproduce the Problem

clone and build Autoware 1.8 or 1.9
download kitti data and create a sym link to it as described in the instructions: https://github.com/CPFL/Autoware/tree/master/ros/src/util/packages/kitti_pkg
source the Autoware environment
Run roslaunch kitti_launch kittiplayer.launch fps:=10

Specifications

Ubuntu version: 16.04
ROS version: 1.12.14
Autoware branch: same result in 1.8, 1.9

Hi @LukeAI, how did you solve this issue? I'm facing the same problem.

Hi @LukeAI, how did you solve this issue? I'm facing the same problem.

from my notes...
# create a symbolic link to the directory containing the raw kitti data from the package eg. something like
ln -s ~/projects/kitti_raw ~/aiPE/ros/src/util/packages/kitti_pkg/kitti_player/dataset

# Modify the `src/util/packages/kitti_pkg/kitti_launch/launch/kittiplayer.launch` file to choose the set you wish to reproduce ("date" and "kitti_data")

#cd to the workspace root and build the required packages in this order:
catkin_make --pkg kitti_player
catkin_make --pkg points2image
catkin_make --pkg calibration_camera_lidar

from my notes...
# create a symbolic link to the directory containing the raw kitti data from the package eg. something like
ln -s ~/projects/kitti_raw ~/aiPE/ros/src/util/packages/kitti_pkg/kitti_player/dataset

# Modify the `src/util/packages/kitti_pkg/kitti_launch/launch/kittiplayer.launch` file to choose the set you wish to reproduce ("date" and "kitti_data")

#cd to the workspace root and build the required packages in this order:
catkin_make --pkg kitti_player
catkin_make --pkg points2image
catkin_make --pkg calibration_camera_lidar

Autoware.AI uses colcon rather than catkin_make so you can use colcon build --packages-up-to calibration_camera_lidar instead.

Autoware.AI uses colcon rather than catkin_make so you can use colcon build --packages-up-to calibration_camera_lidar instead.

right, my notes only apply to a really old autoware, idk if they will help.

right, my notes only apply to a really old autoware, idk if they will help.

Hi @JWhitleyWork, that does not work for me. I provide more infomation on ROS answer, could you have a look?

Hi @JWhitleyWork, that does not work for me. I provide more infomation on ROS answer, could you have a look?


(FACT-1492) Correctly report version numbers for Windows 10 and Server 2016

This adds consistent reporting of the Windows version fact for Windows
10 and Windows Server 2016. Before this, we were returning the raw
kernel version string.

CLA signed by all contributors.

Reviewing

Also - since this ticket clearly needs a moniker

I'm 👍  on this PR

@MosesMendoza to update this thread with info on the ticket that results from analyzing the different Facter output across different Windows hosts.


feat: supports null preview url #2472

Description
Resolves #2472 by supporting the return of null from the admin.preview function, just as the docs indicate here https://payloadcms.com/docs/configuration/collections#preview:~:text=Example collection with preview function

[x] I have read and understand the CONTRIBUTING.md document in this repository

Type of change

[x] New feature (non-breaking change which adds functionality)\

Checklist:

[x] Existing test suite passes locally with my changes

After second thought, we should continue to only fetch the preview URL when the button is clicked. We should simply throw an API error as needed. This is purely for performance reasons.


Vue 3 support

Hi there! First of all -- thanks so much for building and open sourcing this awesome package. ❤
I was wondering if Vue 3 support may be in the works? Really enjoy using this package and I don't want to have to give it up to upgrade. 😢
Is there anything you may need help with to get the compatibility process underway?

Is there a problem of it not working in Vue3?  I thought Vue2 component works in Vue3 so wouldn't keep it as it work better?

Is there a problem of it not working in Vue3? I thought Vue2 component works in Vue3 so wouldn't keep it as is work better?

Oh I don't think there's a problem with it working in Vue 3 -- but I'm not able to upgrade to Vue 3 due to this packages package.json file requiring Vue 2:

Unless there's a way around this requirement that you may know of?

The error seem like it have a problem with<EMAIL_ADDRESS>as peer dev.  I removed it from peer dependencies in 1.5.0, please try and let me know if it work.  Thanks.

Ok great -- I was able to update to Vue 3, but I do receive warnings, and then an error. Here's my console output:
[Vue warn]: `beforeDestroy` has been renamed to `beforeUnmount`.
[Vue warn]: Property "$createElement" was accessed during render but is not defined on instance.
[Vue warn]: Property "_self" was accessed during render but is not defined on instance.
index.js?a129:946 Uncaught (in promise) TypeError: Cannot read property '_c' of undefined
    at Proxy.render (index.js?a129:946)
    at renderComponentRoot (runtime-core.esm-bundler.js?5c40:846)
    at componentEffect (runtime-core.esm-bundler.js?5c40:4280)
    at reactiveEffect (reactivity.esm-bundler.js?a1e9:42)
    at effect (reactivity.esm-bundler.js?a1e9:17)
    at setupRenderEffect (runtime-core.esm-bundler.js?5c40:4263)
    at mountComponent (runtime-core.esm-bundler.js?5c40:4222)
    at processComponent (runtime-core.esm-bundler.js?5c40:4182)
    at patch (runtime-core.esm-bundler.js?5c40:3791)
    at componentEffect (runtime-core.esm-bundler.js?5c40:4298)

I copied your component locally in my project, and here is what I needed to change for compatibility:
https://gist.github.com/stevebauman/0f9f75bb6a4b80dd4a0b900b63173f92/revisions

Also -- is there a reason for using const that = this everywhere? I've removed all of those declarations everywhere and replaced them with simply this and it works fine. Wanted to get your thoughts on if there was a purpose.

I replace beforeDestroy for pure element removal event.  const that = this is important.   It is use to save the correct outside this context when use inside of event handlers.  I do it everywhere so I kept it for consistency.

It is use to save the correct outside this context when use inside of event handlers

Ah okay understood. Couldn't you use ES6 arrow functions so the this context is automatically passed? Ex.
Before:
jq('input', this.footer()).on('keyup change clear search', function () {
    if (that.search() !== this.value) {
        that.search(this.value).draw();
    }
});

After:
jq('input', this.footer()).on('keyup change clear search', (e) => {
    if (this.search() !== e.target.value) {
        this.search(e.target.value).draw();
     }
});

Not complaining or anything (really appreciate the work you've done) -- just curious on your implementation is all. 👍

Also for me it doesn't work on vue 3.
Some warnings and errors:
[Vue warn]: Property "$createElement" was accessed during render but is not defined on instance.
[Vue warn]: Property "_self" was accessed during render but is not defined on instance.
[Vue warn]: Unhandled error during execution of render function
Uncaught TypeError: t._self is undefined

When I try to use this package with vue 3, it directly gives an error about $scopedSlots.
When I comment out scopedSlots sections in vdnettable.vue file, then it says $el.DataTable is not a function.
How can I implement this correctly to a standard vue 3 project? I spent 3 hours and still can't get any results :(
I also tried to merge some logic with this article but still no luck:
https://www.positronx.io/vue-js-dynamic-jquery-datatables-tutorial-example/

@sametsafak Thanks for posting your error.  This gave me a hint on why it is broken.  I've updated the component to support Vue 3 and tag new release to version 2.0.0.    Also updated the project and examples to Vue 3.  Let me know if you have any other issue.

Hi! I appreciate the work you're doing on this project! I too am getting the error "This dependency was not found:
Vue in ./node_modules/vue-datatables-net/dist/index.js" when trying to build my project with the library. I'm using Vue 3 (^3.2.31 and vue-loader ^17.0.0) and vue-datatables-net ^2.0.0 which I'm pulling from NPM. When I look into the idex.js file npm complains about I see this:

module?module.exports=e(require("Vue"))
which is I'm guessing why I am seeing the error? I tried pulling the project and compiling with vuecli also, but that doesn't work either :).

Any suggestions on what I might be missing?

@ckujawa I'm not sure what the issue is but from what you commented above, are you missing reference of <script<EMAIL_ADDRESS>Though, I did found an issue in compiling vue3 project with laravel-mix so I updated the project to compile with vite

That worked much better. Thank you! I didn't even consider using Vite...I'm just starting to learn Vue 3 :).

Yep, to develop Vue with Typescript, Vite is suggested right on vuejs own site here:  https://vuejs.org/guide/typescript/overview.html


Tint Color issue when I stop animation

It's showing blue color background while i stop animation.
You need to set tint color clear to resolve this issue.

Hi, @BhavikThummar  this is not a tint color issue. We have added system button for test our SpinnerButton and for selelcted state its showing this. Just set button to custom type and try.


How to export the image?

Hello!
I'm new to plugins so I am a little lost.
I'm looking through the demo files and when I click export it just opens a blank tab with nothing on it. I'm sorry if this is a pretty stupid question, I just don't really know how to move forward with the plugin.
I've looked through the docs and followed other peoples methods but it doesn't seem to do anything.
Thanks for helping.

I have the same issue, the problem occurs on Chrome, on Firefox it works good

If you press ctrl+shift+j on Chrome it'll tell you in the console why it failed.
I had the same issue and fixed it by using the download plugin from http://danml.com/download.html
I initiated the binary download around line 700 of jquery.cropit.js with the following code.
canvasContext.translate(this.rotatedOffset.x * exportZoom, this.rotatedOffset.y * exportZoom);
canvasContext.rotate(this.rotation * Math.PI / 180);
canvasContext.drawImage(this.image, 0, 0, zoomedSize.width, zoomedSize.height);
newpic = canvas.toDataURL(exportOptions.type, exportOptions.quality);
download(newpic, filenamepic, "image/png");
The newpic variable was declared earlier.
Bit of a hacky solution I guess but it works. I'm quite the novice and I had already gone pretty far in implementing the plugin so I desperately needed a solution. Hopefully this will help somebody :-)


west: runners: blackmagicprobe: use .hex/.bin file

If one needs the firmware to be signed (ie for mcuboot) the signed .hex or .bin file needs to be flashed to the mcu.

@MeisterBob patch looks OK but you need to fix the unit tests. See failing CI details.

added .bin files as well and fixed the unit tests

I did some more testing on this and found that the runner prefers hex over bin over elf even if the user specifies that he wants to have the bin or elf file flashed. The same problem exists in the jlink runner (#52219). Added a fix for that.
The testing procedure involved en-/disabling CONFIG_BUILD_OUTPUT_BIN and CONFIG_BUILD_OUTPUT_HEX and flash the created files with and without specifying which file I'd like to have flashed.

Reverted that last change for an upcomming implementation of --file (https://github.com/zephyrproject-rtos/zephyr/issues/52262), now it's back to prefer hex over bin over elf even if --bin-file or --elf-file argument is set.

I would like you to explicitly describe how you tested these changes before I approve again

Still waiting on this one

the test_script:
#!/bin/bash

echo "build hex and bin"
rm build/zephyr/*.hex build/zephyr/*.bin
west build -- -DCONFIG_BUILD_OUTPUT_HEX=y -DCONFIG_BUILD_OUTPUT_BIN=y > /dev/null
echo "flashing zephyr.hex"
west flash --skip-rebuild -r blackmagicprobe --hex-file=build/zephyr/zephyr.hex
echo "flashing zephyr.bin, acually flashes zephyr.signed.hex"
west flash --skip-rebuild -r blackmagicprobe --bin-file=build/zephyr/zephyr.bin

echo "build hex only"
rm build/zephyr/*.hex build/zephyr/*.bin
west build -- -DCONFIG_BUILD_OUTPUT_HEX=y -DCONFIG_BUILD_OUTPUT_BIN=n > /dev/null
echo "flashing zephyr.hex"
west flash --skip-rebuild -r blackmagicprobe --hex-file=build/zephyr/zephyr.hex
echo "flashing zephyr.bin, acually flashes zephyr.signed.hex"
west flash --skip-rebuild -r blackmagicprobe --bin-file=build/zephyr/zephyr.bin

echo "build bin only"
rm build/zephyr/*.hex build/zephyr/*.bin
west build -- -DCONFIG_BUILD_OUTPUT_HEX=n -DCONFIG_BUILD_OUTPUT_BIN=y > /dev/null
echo "flashing zephyr.hex actually flashes zephyr.signed.bin"
west flash --skip-rebuild -r blackmagicprobe --hex-file=build/zephyr/zephyr.hex
echo "flashing zephyr.bin"
west flash --skip-rebuild -r blackmagicprobe --bin-file=build/zephyr/zephyr.bin

echo "only elf file present"
rm build/zephyr/*.hex build/zephyr/*.bin
echo "flashing zephyr.hex actually flashes zephyr.elf"
west flash --skip-rebuild -r blackmagicprobe --hex-file=build/zephyr/zephyr.hex
echo "flashing zephyr.bin actually flashes zephyr.elf"
west flash --skip-rebuild -r blackmagicprobe --bin-file=build/zephyr/zephyr.bin

which result in (stdout only)
build hex and bin
flashing zephyr.hex
-- west flash: using runner blackmagicprobe
load "build/zephyr/zephyr.hex"
flashing zephyr.bin, acually flashes zephyr.signed.hex
-- west flash: using runner blackmagicprobe
load "[...]/build/zephyr/zephyr.signed.hex"

build hex only
flashing zephyr.hex
-- west flash: using runner blackmagicprobe
load "build/zephyr/zephyr.hex"
flashing zephyr.bin, acually flashes zephyr.signed.hex
-- west flash: using runner blackmagicprobe
load "[...]/build/zephyr/zephyr.signed.hex"

build bin only
flashing zephyr.hex actually flashes zephyr.signed.bin
-- west flash: using runner blackmagicprobe
load "[...]/build/zephyr/zephyr.signed.bin" 0x1000c000
flashing zephyr.bin
-- west flash: using runner blackmagicprobe
load "build/zephyr/zephyr.bin" 0x1000c000

only elf file present
flashing zephyr.hex actually flashes zephyr.elf
-- west flash: using runner blackmagicprobe
load "[...]/build/zephyr/zephyr.elf"
flashing zephyr.bin actually flashes zephyr.elf
-- west flash: using runner blackmagicprobe
load "[...]/build/zephyr/zephyr.elf"

@MeisterBob thanks for the details on how you are testing this.
echo "flashing zephyr.bin, acually flashes zephyr.signed.hex"
west flash --skip-rebuild -r blackmagicprobe --bin-file=build/zephyr/zephyr.bin

Judging from this, it looks like the PR should be updated to add --file support to the blackmagic runner, right?

rebased and added --file support.

should this be closed now?

@carlescufi no; this PR is active

@mbolivar-nordic please revisit.

@MeisterBob happy new year. I'm back from vacation now. Can you share the updated test procedure you used?


Duplicate form ids

in the form Multiple form field elements in the same form have the same id attribute value. This might prevent the browser from correctly autofilling the form.

can you provide deep down media file to know more about issue??

@pratham5368 which form elements are you referring to? Please elaborate for more context


Unable to deploy to device on xcode 9.3 and iOS 11.3 due to provisioning profile issues.

CLI: 3.4.3
Cross-platform modules: 3.4.1
Runtime(s): ios - 3.4.1

Describe the steps to reproduce it.
Try and run tns run ios --device.
It looks like Xcode 9.3 has broken NativeScript's ability to handle automatically managed profiles. I keep getting this error:
Error Domain=IDEProvisioningErrorDomain Code=9 ""demo.app" requires a provisioning profile." UserInfo={NSLocalizedDescription="demo.app" requires a provisioning profile., NSLocalizedRecoverySuggestion=Add a profile to the "provisioningProfiles" dictionary in your Export Options property list.}
I've tried including my team ID, set code signing identity to iPhone Development, manually set my provisioning profile, I've cleared out all my profiles and certificates from my computer, nothing helps.
I can open xcode and check Automatically Manage Profiles and build from xcode fine, but when I quit xcode and try to run on the device, i get the provisioning profile error. This is happening on a brand new official plugin seed, as well as all my existing projects.

@vakrilov @EmilStoychev

An update: I just created a new wildcard provisioning profile, and when i run tns run ios --provision  I get this:
2018-04-11 12:03:10.923 xcodebuild[10484:1456462] [MT] IDEDistribution: Step failed: <IDEDistributionPackagingStep: 0x7f9bf8daeca0>: Error Domain=NSCocoaErrorDomain Code=3840 "No value." UserInfo={NSDebugDescription=No value., NSFilePath=/var/folders/g_/7bmt0s1s179cncnz_ssy7wqm0000gn/T/ipatool-json-filepath-jDaAH4} error: exportArchive: The data couldn't be read because it isn't in the correct format.

We had a private conversation in order to find the cause of the issue. It looks like there's a problem with rvm and Xcode, which is resolved by executing the following:
sudo gem install sqlite3 -- --with-sqlite3-lib=/usr/lib

More details can be found here


Add 'emscripten' property to versions.json

Emscripten does not guarantee ABI stability between versions so this information is useful for downstream consumers to verify compatibility.
Relates to https://github.com/lovell/sharp/pull/3907 e.g. allows future possible automation of this.
(Use of xargs is to clean up the version number as it might be wrapped in quotes.)

Ah, I wasn't aware of dumpversion, thanks for simplifying this.


Make service creation optional

I've created my own RPM package for consul-template which contains a systemd service.
Using this module does overwrite this service.
I suggest making the service file creation optional and dealing with start parameter customization by using optional drop ins.

I've got a patch for this here: https://github.com/claranet/puppet-consul_template/pull/123


Allow = as separator for named parameter default value.

Spec bug for #27559

Landed in https://github.com/dart-lang/sdk/commit/efb9a12811b5707410b0e21ad13f498d477d3746.


I hope it will support Vue3 as well

Good Job！
I hope it will support Vue3 as well

Coming very soon!

Hi @HelloZhu. You can now scaffold a plugin from a Vue template. If you try it and run into any issues, please let me know. Thanks!


Mobject add_to_back sanity checks

Motivation

Closes #1099
Overview / Explanation for Changes

Additional sanity checks are added to ensure that:

ValueError is raised when Mobject adds self
The same Mobject is prevented from being added multiple times (WIP)
TypeError is raised when a non-Mobject is added

Testing Status

Specs:

CPU: i5-6400
RAM: 16 GB GDDR3L
SSD: 1 TB SATA
GPU: GTX 1050-Ti 4 GB

WSL: Ubuntu-20.04 running poetry
def test_vmob_add_to_back():
    """Test the Mobject add_to_back method"""
    a = VMobject()
    b = Line()
    with pytest.raises(ValueError):
        # Mobject cannot contain self
        a.add_to_back(a)

    # No submobject gets added twice
    a.add_to_back(b)
    a.add_to_back(b, b)
    assert len(a.submobjects) == 1

✔ Successful test (it was fine in 0201194)
Further Comments

Duplication prevention may need additional testing for edge cases such as:
a.add_to_back(b, b, b)
a.add_to_back(b, b)

Acknowledgements

[X] I have read the Contributing Guidelines
[X] I have chosen a descriptive PR title (see top of PR template for examples)

Reviewer Checklist

[ ] Newly added functions/classes are either private or have a docstring
[ ] Newly added functions/classes have tests added and (optional) examples in the docs
[ ] Newly added documentation builds, looks correctly formatted, and adds no additional build warnings
[ ] The PR title is descriptive enough

It needs black formatting.

Since this has been broken beyond repair, I'll just redo it in another PR.


Improve overall sentence clearness and understanding

Hi,
I just added an article, the verb called and a comma in a sentence that got me confused, since I'm not a native english speaker. I think this way is easier to understand

Just signed the CLA

/lgtm
/approve


How can I have custom Routes for User?

I noticed that you have routes defined in your folder which is in vendor for us.
You have routes like this-
Route::get('users', '\App\Http\Controllers\ScaffoldInterface\UserController@index');
But I want to use my own routing structure.
Am I missing something here? Because I can't seem to find a way for using my own routes and disable yours. The only way I can see here is changing the file in vendor folder, which is wrong.

Hi @PankajSanam
Thanks for submitting this issue.
Perhaps it would be more flexible to customize these routes in the next release, so I'm gonna add the enhancement tag to this to be updated.

Ok great, thanks!
Any idea when is the next release coming?

The next couple of days, I'll let you know about the updates.
feel free to submit any issue or pull request.

@PankajSanam
v1.7.15 is released, now you could update scaffold-interface in your project and you're free to customize your routes however you like, scaffold-interface routes are served under scaffold- prefix.
Thanks


Make VSWhere useful for developers

What developers need is a utility, located in a well-known and unchanging location, that can be invoked with no arguments, to return an absolute path to the tool they need.
VSWhere is not that utility. VSWhere is a Swiss army knife that has about 50 million arguments and outputs, yet still fails to return anything that's actually useful to developers. It is a tool that was written for Microsoft's wants, not the needs of developers who use Microsoft's tools.
It is a tool that is setting up every developer who uses it for disaster, because when - not if - Microsoft decides to change the location of MSBuild.exe, every script that tries to find MSBuild by concatenating the output of VSWhere with MSBuild\15.0\Bin\MSBuild.exe is going to break. Best case, the script is written well and the worst that happens is a "file not found" message; worst case... well, how many scripts have you seen that do path concatenation the absolutely wrong way, such that the file not being found will cause issues up to and including execution of the completely wrong EXE?
A utility that simply returns the absolute path to MSBuild, however, is almost foolproof: it either returns a valid path, and MSBuild runs; or it returns a bad path, and you try to run a nonexistent executable, and get a "file not found" message, and things break.
That is the utility VSWhere needs to be. Start off by adding support for getting the absolute path to MSBuild (you can obscure it behind half-a-dozen arguments if you must); someone who needs to locate a different VS tool can submit a pull request that follows the pattern set for MSBuild.

It is already so. This tool just covers new installation API as an user-end command-line tool which distributed constantly in known place (only with new VS versions #41).
So you can wrap anything even via simple batch scripts like hMSBuild just for searching msbuild.exe and so on.


Package request: Howdy

Project description
Howdy provides Windows Hello™ style authentication for Linux. Use your built-in IR emitters and camera in combination with facial recognition to prove who you are.
Using the central authentication system (PAM), this works everywhere you would otherwise need your password: Login, lock screen, sudo, su, etc.
Metadata

homepage URL: https://github.com/boltgolt/howdy
source URL: https://github.com/boltgolt/howdy
license: mit
platforms: linux

Duplicate of https://github.com/NixOS/nixpkgs/issues/76928

Duplicate of #76928

Sorry about that. I should have checked for a duplicate. I can close this if you want and upvote the original.


Fix reset password workflow

Reset password is broken in a couple of (easily fixable) ways:

[ ] No visual feedback that a link was successfully sent. This is likely because the flash notice was removed for this, easy enough to put back in.
[ ] Wrong domain included in the link it's http://adoptadrain.org instead of our domain
[ ] Email subject just says "Reset Password Instructions" should be a bit more explicit that it's for Adopt a Drain SF.
[ ] Email is from<EMAIL_ADDRESS>[ ] The Reset password page doesn't reflect the brand at all, may decrease trust. Would be ideal to simply have that wrapped in the sidebar, but not sure how easy that is.

Yes, agree that the reset password email is not clearly tied to Adopt a Drain SF. In addition to changing the subject line, I'd like to change the email copy to "Someone has requested a link to change your password for Adopt a Drain SF"

@jasonlally what e-mail address should this come from? Assuming<EMAIL_ADDRESS>but let me know if not.

that works for me, thanks.

Yes<EMAIL_ADDRESS>works


Support for Two-Keystroke Mappings with Timeout in Insert Mode

Is it possible to implement a timeout for two-keystroke mappings, such as using kj to trigger Esc? The timeout would occur between the first and second keystroke.
For example, if I want to type a k in insert mode, I currently need to type two consecutive ks (kk), because the first k is waiting for the second keystroke (j).
It would be great if a timeout could be set so that if the second keystroke (j) is not entered within a certain time, the first keystroke (k) is typed as a normal character. Similar to Vim's timeoutlen.
Python package version:
3.12.2
Extension version:
jupyterlab_vim | 4.1.3 | pyhd8ed1ab_0 | conda-forge
JupyterLab v4.0.11
jupyterlab-jupytext v1.4.3 enabled OK (python, jupytext)
@jupyter-notebook/lab-extension v7.0.8 enabled OK
@axlair/jupyterlab_vim v4.1.3 enabled OK (python, jupyterlab_vim)
@jupyter-widgets/jupyterlab-manager v5.0.11 enabled OK (python, jupyterlab_widgets)
MacOS Monterey 12.7.4
Note: This is a crosspost issue from jupyterlab-vim.

Thanks for the reply. Running :imap kj <Esc> worked in https://raw.githack.com/replit/codemirror-vim/master/dev/web-demo.html. But not directly by typing :imap kj <Esc. in a JupyterLab cell.
However, your tip led to a solution! The timing now works as expected:
I revisited the jupyterlab-vim documentation on mappings and added :imap kj <Esc> to the Notebook Vim configuration in JupyterLab.
Additionally, I removed conflicting keyboard shortcuts per other instructions in jupyterlab-vim via Keyboard Shortcuts.
I removed/commented out the following keyboard shortucts:
{
"shortcuts": [
    {
        "command": "vim:enter-normal-mode",
        "keys": [
            "K",
            "J"
        ],
        "selector": ".jp-FileEditor",
        "args": {}
    },
    {
        "command": "vim:leave-insert-mode",
        "keys": [
            "K",
            "J"
        ],
        "selector": ".jp-NotebookPanel[data-jp-vim-mode='true'][data-jp-vim-esc-to-cmd-mode='false'] .jp-Notebook.jp-mod-editMode",
        "args": {}
    },
    {
        "command": "vim:leave-current-mode",
        "keys": [
            "K",
            "J"
        ],
        "selector": ".jp-NotebookPanel[data-jp-vim-mode='true'][data-jp-vim-esc-to-cmd-mode='true'] .jp-Notebook.jp-mod-editMode",
        "args": {}
   },


Layers mask in the inspector aren't saved in an instantiated object

Description:
A gameobject that is instantiated doesn't save the Layer Masks of a script assigned in the inspector.

Build:
<IP_ADDRESS>

Type:
B

Steps to reproduce:
Make a prefab with a script that has a layer assigned through the inspector.

Frequency:
Always.

Fixed


fix ci, use curl to trigger gitlab deploy

instead of using a third-party GitHub action.
#52
I've used just the token secret, the gitlab ref name is hardcoded to master.
I haven't tested it, as I'd need the secret value and gitlab access.

related to #53

Thank you so mutch. Looks good to me by all means. ^.^

Still a single issue though, It gets triggered 3 times due to different python versions

I just used the same configurations of the past version, let me fix it, I'll open a new PR in a while


Refreshing while having the fox/eth pool overview modal open yields a black screen

Overview
Refreshing while having the fox/eth pool overview modal open yields a black screen

Connect Wallet with Fox/eth pool balance
Go to defi page
click on fox/eth pool and bring up the overview modal
hit refresh and observe a black screen

Might be related to the URL, I know we had that issue before when we got black screens more often.
example url - https://release.shapeshift.com/#/fox?provider=UNI V2&chainId=eip155%3A1&contractAddress=0x470e8de2ebaef52014a47cb5e6af86884947f08c&assetReference=0x470e8de2ebaef52014a47cb5e6af86884947f08c&highestBalanceAccountAddress=0x8bedab5f8ddcac46013a15f9cd015ee2174e3e2a&rewardId=&modal=overview

References and additional details
see above.
Triage link: https://discord.com/channels/554694662431178782/1037112617099079771
Acceptance Criteria
A refresh with modal open would bring you back to the defi/fox page/asset page/ account page instead of black screening.
Need By Date
n/a
Screenshots/Mockups
n/a
Estimated effort
No response

Note, this one will eventually be fixed by proper AccountId carrying through DeFi route props vs. the way we do it currently (drilling props)


Remove version: TuxGuitar.TuxGuitar version 1.5.6

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

Close with reason: Duplicate;


Add Anaconda 3 version 4.4.0.

This is the full Anaconda 3 distribution

Have to resubmit, accidentally merged upstream changes into my fork.


Normalization of Images

In the paper it says that the "original H&E images are first normalized to $[0,1]$ per channel". But I don't see that in the code if hchannel=False (or rather the normalization is commented out). Referring to the code here:
https://github.com/azizilab/starfysh/blob/7407267515d56a7dc96672c764a40635fae581d6/starfysh/utils.py#L725
Did you decide to not scale the image channels, or is this happening somewhere else in the code?

Hi schae211,
Thanks for the inquiry! For the dataset we processed the spatial information was stored independent of the .h5ad expression file, so we appended the image with normalization here: https://github.com/azizilab/starfysh/blob/7407267515d56a7dc96672c764a40635fae581d6/starfysh/utils.py#L283. We will uncomment your highlighted line for consistency with dataset with appended spatial information within h5 files.

Okay, thanks a lot for the clarification!

A minor followup: The uncommented code does not normalize each channel separately, so one would actually need something along those lines
n_channels = adata_image.shape[-1]
for channel_idx in range(n_channels):
    adata_image[:, :, channel_idx] = \
        (adata_image[:, :, channel_idx]-adata_image[:, :, channel_idx].min())/ \
        (adata_image[:, :, channel_idx].max()-adata_image[:, :, channel_idx].min())

And maybe a slightly unrelated question, when would you recommend to use the apply the binary color deconvolution to extract hematoxylin channel? (i.e. setting hchannel=True)?