Avoid withWebId passing undefined when the user is authenticated

When the user is authenticated and withWebId is used on a component, the component is first rendered with withWebId set to undefined and then the prop is changed to the correct user WebId.
The preferred behavior would be to pass the user's webId on the first render.
A very simplified example:
export default MyComponent = withWebId(({webId}) => (
    webId ? <LoggedInComponent/> : <LoggedOutComponent/>
);

On each mount with an authenticated user the LoggedOutComponent is rendered first and then it is replaced by the LoggedInComponent. I would expect only the LoggedInComponent to be rendered.
I'm pretty new to Solid and solid-react-components, so I'm sorry if there is something I misunderstood or used differently that it was designed to work.

Hello and thanks for reporting this! It does seem like an issue that should be addressed. The components in question, withWebId, LoggedInComponent, and LoggedOutComponent are actually just wrappers around another library called solid/react-components (not to be confused with this repo, the inrupt/solid-react-components).
Can you please open an issue on that repo with the same information? We can use this ticket as a reminder to update the library once the fix is in place.


Use task colour (#59), Hide non-working days (#9, #57), See all team …

Use task colour (Fixes #59),
Option to Show/Hide non-working days (Fixes #9 , Fixes #57),
See all team members with capacity (fixes #73),
Use configured capacity (fixes #111 ),
Not showing avatar image after D&D fixes.

@yanivsegev I've bumped the version to 2.1.0 as this introduces new functionality.
If you've got any outstanding changes I'm happy to re-work this after you've merged them in.
I'm probably going to start looking at marking days as holiday from the plan next, but would like to chat to see if this aligns with your goals too.

@yanivsegev I think I have the days off from the plan working, but DevOps is giving me 503 errors right now, so will push that up tomorrow.

@yanivsegev PR updated to include "Mark as Day off" functionality.

@yanivsegev PR updated to also include a team wide setting to use PBI level items instead of Task level items on the plan.
Also fixed an issue where the settings page wasn't saving the highlightPlanningIssues check box.


Fixed close tab and close window shortcut

Description
The command + w shortcut closes the editor instead of the current file. The functionality to close the current file was already implemented in CodeEdit/Features/Tabs/Views/TabBarItemView.swift. The fix was to remove this shortcut from CodeEdit/Features/WindowCommands/FileCommands.swift where it explicitly closes the editor. I moved this code to the correct keyboard shortcut (⌃⇧⌘W) which is the same as the one in Xcode.
Related Issues
Closes #1370
Checklist

[x] I read and understood the contributing guide
[x] The issues this PR addresses are related to each other
[x] My changes generate no new warnings
[x] My code builds and runs on my machine
[x] My changes are all related to the related issue above
[x] I documented my code

Looking back at this, the change I made by removing the shortcut from CodeEdit/Features/WindowCommands/FileCommands.swift means that it won't close the editor window when there are no open files. If instead you would like the editor to close when pressing "command + w" when theres no opened files, I can add this piece back in.

Looking back at this, the change I made by removing the shortcut from CodeEdit/Features/WindowCommands/FileCommands.swift means that it won't close the editor window when there are no open files. If instead you would like the editor to close when pressing "command + w" when theres no opened files, I can add this piece back in.

I would prefer that cmd+w just closes the tabs. if there are no active tabs open, i press cmd+q to close the app


Small formatting fixes (mainly updated output)

Small PR, just updated some output for formatting while I was working on a separate issue.

This change is

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/00bdc136cdcb94e4ae6617cebe8dc344e4003541/
Edited pages:

v19.2/create-table-as.md
v19.2/drop-table.md


Revamp Implement Method Code Action

Purpose
$subject for fixing formatting issues of the text edit.
Fixes #31825

Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[x] Added necessary tests

[x] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

LGTM


Zfits reader cocov

Modified the io/zfits such that it works with latest ctapipe container structure and that it match the CameraToACTL zfits structure.

added a sample file of 5 events
added a unit test

Note that for ctapipe installation procedure, Etienne Lyard now produce a way to install the ProtoZFitReader from CameraToACTL through pip such that it would become easy for anyone who need to work with zfits input file to use ctapipe
Some TODO: not all the fields which can be implemented in zfits file are read yet, they will be implemented as they appear in the protozfitreader.

One comment: I added some fields in the io.containers.RawCameraContainer class, let me know if this is not the proper approach, I could create a new class if needed

I re-attributed the variables to the proper containers and added a DigiCamRawCameraContainer class deriving from RawCameraContainer in io/containers to treat the camera dependent info.
@kosack In the zfits.py I simply overwrite the RawCameraContainer items of the map in the RawDataContainer tel attribute.Does that sounds fine?

I realise also that just before I did the pull request, R0,R1 were introduced in the zfits.py
I'll adapt to it

Is this PR ready to merge? It now says there is a conflict in zfits.py that needs to be resolved, so you may need to pull once more from the upstream repo and commit it.

@kosack  sorry for the delay, I was offline part of last week. I've commit a version with solved conflict

The protozfitreader dependency should be added to the setup.py if its pip installable.

I think this is superseded by #598 and can be closed.


Add some LaTeX templates and ability to use them in Open LaTeX Studio

As a part of this ticket we should first create some sample LaTeX templates - for example for articles, letters, books, CVs and add them to the code repository. We should then allow to load such templates in the Open LaTeX Studio. This should be exposed as an option in the File menu (perhaps named Open template).

As my first task, I think this one will be ok.

For now, I have already created this:

You can find code and commits on my GitHub: aQaTL's Open-LaTeX-Studio fork
How it works: firstly program checks if JTextArea (this one in second box) contains correct path to file - if yes, then loads it, if no - loads selected template from list (if you choose anything in list, it clears JTextArea). So JTextArea literally overrides selection in JList.
Unfortunately, I haven't  added any templates yet. I don't know, how to make them automatically added to Templates folder (I created it manually in app directory) in installation process.
It's my first commit, so any feedback will be really helpful for me.

@aQaTL What exactly would the "Choose your own template" do? Concerning loading of the templates - first of all, we create multiple files under the application directory. You can take a look how it's done in the code. On the other hand, I'm not sure why would you want to place the templates in the app directory. I think they could be simply placed in the resources package in the codebase (unless you plan to make the templates selection extendible by the end users, but that is a bigger task).

@sebbrudzinski I put templates in app directory, just to test if its working (and I thought that it's correct place), but I admit, that placing it in resources is smarter (I will move it). I am not planning to do templates section extendible - for that, I created "Choose your own template" section. So, this section would allow user to use his own LaTeX templates files (if it's doesn't make sense I can delete it).

@aQaTL Correct me if I'm wrong, but I'm thinking that it would do exactly the same thing as "Open File", which we already have under the File menu. If that's the case, we should probably drop it.

@sebbrudzinski Oh, That's true. I didn't think of it that way. Thanks for explaining. How about the rest of code (isn't it bad, too complicated, or something like that)?

@aQaTL I've taken a brief look only and it's not bad. One thing that caught my eye is the placement of braces. As per java and our project coding convention, the opening brace should be in the same line as the instruction (if/method/class etc.). Moreover, it would probably be better to design the panel using the NetBeans GUI designer, so other people can easily adjust it at a later point. I'll do a complete review once a pull request is opened.

@sebbrudzinski Braces placement aren't a problem, I can switch it in NetBeans options, press alt + shift + f and they will match to project convention (I forgot to do that before committing).
Today I realized that everything here is designed with the NetBeans GUI builder and it's a good idea to use it instead of hard-coding entire look. I think it's the easy part of this task. Once I have moved the templates folder to resources it's not easy to operate on them (I assume they will be stored in a jar file). Additionally, I am still learning about LaTeX, so I haven't started working on templates yet.

@sebbrudzinski There's a big problem with operating on files inside the jar - everything in OpenLaTeXStudio uses File object and I can't create a File object from a jar resources(I tried many options). So, even if I load file, I can't pass anything to setCurrentFile method and NullPointerException occurs. I spent a lot of time thinking about it and.. How about placing these files in a jar and unpacking it to normal directory at first run(in an app directory for example)?
One more thing - what do you think about including some templates from this website LaTeX templates? I contacted the owner and I have his permission to use(I can show you it). Just need to mark his website as a source. In my opinion a link in "Open Template" Dialog will be enough and fair. Note that these templates will be much better than mine.

@aQaTL I think it's a wonderful idea to use templates from latextemplates.com  Thanks for contacting them about it. I've created a quick mockup, how selecting a template could look like. What do you think about it? I think it may make sense to specify source per single template, in case we use more templates from other websites in the future.
Load_template_mockup.pdf
Concerning jar resources - we do not really need to convert them to File objects or invoke "setCurrentFile" method. All we should do is extract the content of the file and display it in the Editor window. You can use the loading of the welcome.tex as an inspiration.

@sebbrudzinski I am glad that you like my idea and I think that your vision makes sense.  Take a look at it:

I decided to specify information about templates in templates.xml file (stored in resources), so if somebody will want to add new template, just need to pase it in the templates folder and add a few lines to xml file.
Tell me, if the code is too complicated (I had to learn xml write it).
I've already pushed changes to my repository.

Using XML to define templates sounds reasonable to me. I've taken a look at the code and there are some small issues, but in general it looks good. Feel free to open a pull request once it is ready.

Fixed by @aQaTL   Thank You! :)


NBT: When decoding handle interrupt, NBTValueHelper

When I am going implement NbtBlobHelper, I give up :(

The name NbtValueHelper is quite unspecific. How about something like ToNbt?

Okay :)

No. It is wrong things.


JOY_setEventHandler docs should clarify interrupt callback ramifications

The docs for JOY_setEventHandler() in inc/joy.h say "It update controllers state at each V Blank period and fire event if a state change is detected."  It doesn't clarify that the call comes from within JOY_update() within _vint_callback.  This matters for three reasons: stack use, vblank scheduling, and thread safety.
Stack use
An event handler called from the top level of a program can use practically all of the stack for automatic variables.  By contrast, an event handler called from an interrupt handler that runs while a lot of stack is already allocated to functions on the call stack can use only the portion of the stack that said functions are not using.
Vblank scheduling
On a 60 Hz machine, the VDP is using most of memory bandwidth for 224 out of 262 scanlines, leaving 38 scanlines for transferring data to VRAM without bus contention and tearing.  If controller reading runs during this time, it could take away VRAM DMA time.  I guess this isn't too much of a problem for programs using the DMA queue because _vint_callback calls things in a sane order: XGM, then VRAM DMA queue, then user callback set in SYS_setVIntCallback, then input.
Thread safety
An event handler called from the top level of a program is not running at the same time as other game engine code (AI, physics, graphics, etc.) and can freely read and update game state variables without risking breaking atomicity by reading or writing game state behind the back of a function that does not expect it.  By contrast, an event handler called from an interrupt handler can't do much more than queue up events to be handled later, and even the part of the program that reads the queue needs to take care to update in a way that causes the event handler never to see an inconsistent state. This is likely to happen during a "lag frame", a situation in which other game code takes more than 1/60 of a second on a 60 Hz machine or 1/50 of a second on a 50 Hz machine to execute.
Are examples of safe communication between the main program and the input event handler planned? Or a way to drive input by polling within the main thread as opposed to an interrupt?

That is an issue well organized =)
As i told you in SGDK Discord channel, you have many ways to take care about thread safety.
Still to reply your different point:

stack is big enough so you don't need to care about it (even on interrupt handler), except if you use heavy recursive function but then i guess that would require a specific stack setting (anyway stack is located in high memory so you probably won't collide easily with heap).
as you mentioned, SGDK takes care of processing DMA queue first, so the user callback is always called after critical tasks. Note that you also have access to an early VBlank call for critical users tasks using SYS_setVIntPreCallback(..)
you can easily protect any process from interrupts using SYS_disableInts() / SYS_enablingInts() couple methods :)

Hope that help you in understanding the SGDK workflow in general


content/ssh: Add "git credential manager" to the SSH page.

This is based on my best knowledge but I haven't fully tested.
I have tested on Windows.
Review

Do we want to offer both options?
What are the risks?

Preview: https://coderefinery.github.io/installation/branch/rkdarst--gcm-setup/ssh/
I think this is starting to look good.

It is good to offer this. But do we need to adjust the verification script which only tests the SSH part?

Oh yes... hm.  I can try to work on it.

I think it will work now.  It doesn't promise to verify things, but show's it configured.  I don't know how to fully automate the verification yet

try cloning a private repo - goes to browser, but clone fails.  how to test?  needs some knowledge of what to expect, I think.
try cloning public repo: doesn't use it
...


ERROR Error: Trying to link invalid ‘this’ to a Java object

Please, provide the details below:
Did you verify this is a real problem by searching the NativeScript Forum and the other open issues in this repo?
Yes
Tell us about the problem
During marshaling native library I am getting error as title
Please provide the following version numbers that your issue occurs with:

CLI: (run tns --version to fetch it) 4.1.2
Cross-platform modules: (check the 'version' attribute in the
node_modules/tns-core-modules/package.json file in your project) 4.1.0
Runtime(s): (look for the "tns-android" property in the
package.json file of your project) 4.1.3

I am trying to implement https://github.com/socketio/socket.io-client-java in NativeScript as bellow:
let manager = new io.socket.client.Manager(android.net.Uri("http://<IP_ADDRESS>:3001"));
let socket = manager.socket("/status");
socket.connect();

But I am getting this error:
JS: ERROR Error: Trying to link invalid 'this' to a Java object
Any idea in where I am doing mistake? Thanks in advance.

Solution: https://discourse.nativescript.org/t/error-error-trying-to-link-invalid-this-to-a-java-object/6683


Is there a way to encrypt data in my nodejs server and decrypt in my php page?

Hi, im having some problems here is my code.
in node side
`const secret = "seg078691";
const salt = "28yf3rh37rvh2e8vj28eh73rhv28jev28h375h";
var downloadCrypt = PolyAES.withPassword(secret, salt).encrypt(id_post.link);
`
then i pass the 'downloadCrypt' var in url like this
campanha.php?id=eQ3VQLrk6x3KKe97nziYv2oCg4QSSAEzsb7BQ4uDDToJEyFExOgQyHCOGV4uhQg4oK+3y6OoFc1RrYjQqgjcEk1OwWZ/hYCcE8je9omsBAdYQGlz1q0uE1bkuTM=
then get by id and
in php side to decrypt..
`<?php
require_once('../vendor/autoload.php');
use PolyCrypto\PolyAES;
$data = $_GET['id'];
$password = 'seg078691';
$salt = '28yf3rh37rvh2e8vj28eh73rhv28jev28h375h';
echo $decrypted = PolyAES::withPassword($password, $salt)->decrypt($data);
?>`
but its not working im doing domething wrong?

Hi @wilsntn, Base64 is not safe to put in a URL. In your campanha.php?id=... you'll notice that there is a plus there. PHP will interpret the plus as a space when populating $_GET. You'll need to use encodeURIComponent to make the string safe for a URL.
const encodedId = encodeURIComponent(downloadCrypt);
const link = `campanha.php?id=${encodedId}`;

Really, it's best to run encodeURIComponent on every URL param.
Using encodeURIComponent can be confusing and unwieldy, so I actually created a library called fluent-url for working with URLs. Usage:
const url = require('fluent-url');

const link = url('campanha.php', { id: encodedId }).href();


GHA config for PHP with fixed caching and testing for BC breaks

Adds a matrix that installs the lowest-allowed versions of composer dependencies; this should detect any backwards compatibility breaks
Also fixes the composer caching (was pointing to wrong folder) and uses a slightly different 'set up PHP' action that is more widely used

So you don't want to merge or something?

So you don't want to merge or something?

Yes, I do
It would just be nice to have the fix for "ramsey/uuid": "^4.2.1" (refs. https://github.com/cucumber/common/pull/2035/files#diff-0718aab1435f0377cfbb7f61cf52e015269dda9e98090b3ba9522f6612dbb489) to make the CI green
As this is a fork of you, it would be easier for you to push the patch


Added api endpoints test cases (blocks, blocks_children)

I made a subdirectory ./tests/api_endpoints/ for ./notion_client/api_endpoints.py test cases, since there are amount of classes.
Any comments are welcome.

Added BlocksEndpoint, BlocksChildrenEndpoint test case
Some request/response come from notion api document.

Sorry for the long answer but I'm not sure what I want to do with the tests. On this PR specifically, I don't like the fact that the block ids are set in stone, and that since you are the one that generated the cassettes, I wouldn't be able to regenerate them myself with my own API key and Notion workspace. Do you have any idea on what we could do so that it's a bit more permissive?

Closing because there is no answer from OP but feel free to answer with any hint regarding my previous comment and I will gladly reopen, I'm definitely interested in more tests. :)


Need to have onEdgeUpdateEnd

I'm really happy after seeing new features introduce in 9.5.4, i e. onEdgeUpdateStart,
But seems like this is not sufficient, in my use case i will need to have onEdgeUpdateEnd as well,
My Case: onEdgeUpdateStart i'm enabling one flag, which start showing target location on node, but if i left dragging in middle without connecting to target then i also need to reset that flag to hide target location.
Can you please provide this feature as well, i will be really thankful.

Indeed!
We have functionalities like
onConnect
onConnectStart
onConnectEnd
onEdgeUpdateStart
onEdgeUpdate
However, onEdgeUpdateEnd is missing.  I think having onEdgeUpdateEnd would be really helpful
Great library btw!

Really happy for using this library. Looking for the similar kind of feature i.e. onEdgeUpdateEnd .
Thankyou.

yep, we will add that handler.

Would it be possible to fire onEdgeUpdate even when the the edge hasn't been dragged on a new handle?
I'd like to remove an edge by dragging it to empty space!

added in v9.6.0


Trigger a turbo:before-add-element event when adding a new node

While implementing some animations on our page, we realized that we had no access to an event before an element was added to the DOM.
With this PR I'd like an early feedback from maintainers if this is the right direction and I can continue.
In particular regarding the event name.
If I get your OK, I'll:

add tests
update documentation to include this new event

Let me know 🙏

I'd love to get a feedback on this one. Thanks!


Docs: Clarify "^" prefix uses istartswith

https://github.com/django/django/pull/9357/ enabled admin search_fields to use verbose lookups like __istartswith as an alternative to using the shortcut prefixes like ^. The PR linked the lookup for ^ to be startswith but the implementation actually uses istartswith.

Merged upstream


[GHSA-j7hp-h8jx-5ppr] libwebp: OOB write in BuildHuffmanTable

Updates

Affected products
Description

Comments
some third party software includes libwebp.a vs libwebp.so and may be vulnerable unless built on a version that includes the CVE fix.

👋 Hi @jasonculverhouse, thank you for your interest in GHSA-j7hp-h8jx-5ppr. We don't have the bandwidth to verify if org.bytedeco.javacpp is vulnerable to CVE-2023-4863 and would want the maintainer of the package to verify that the software is vulnerable before including it in the advisory.

Yes, I really need to look at the build and see the version of libwebp that is pulled in.  Since you do the build of Open CV vs taking a prebuilt library  on a github container I think that you just need to confirm that the github container that contains the libwebp.a is patched.
I don't see the latest snapshot build logs, but here was the last one that I see 0.6.1-2ubuntu<IP_ADDRESS>  is the one that contains the fix https://launchpad.net/ubuntu/focal/amd64/libwebp6
I don't think the current non-snapshots builds contain this version.
ii  libwebp6:amd64                                              0.6.1-2ubuntu<IP_ADDRESS>                                               amd64        Lossy compression of digital photographic images.
ii  libwebpmux3:amd64                                           0.6.1-2ubuntu<IP_ADDRESS>                                               amd64        Lossy compression of digital photographic images.

https://github.com/bytedeco/javacpp-presets/actions/runs/6274819259/job/17061951688#step:2:1242

👋 This pull request has been marked as stale because it has been open with no activity.  If you do nothing this pull request will be closed eventually by the stale bot. Please see CONTRIBUTING.md for more policy details.

Gonna close this one out as linux modules are out of scope for us.


prepare release 1.4.4

Codecov Report

Merging #455 into 1.4 will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              1.4     #455   +/-   ##
=======================================
  Coverage   38.21%   38.21%
=======================================
  Files          20       20
  Lines        1672     1672
=======================================
  Hits          639      639
  Misses       1033     1033

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 db9257f...6d0f305. Read the comment docs.


Bug: compiler cache does not respect different settings (e.g. Optimizer, EVMVersion)

fixed in 9695daf


Boughtitem value caching

This PR resolves #337. It sets up caching of important values on BoughtItem and BoughtItemDiscount at creation time. This has a double benefit of reducing required queries / query complexity related to calculating prices and discounts AND ALSO preventing unexpected behavior if organizers change a price / discount amount or delete an item or discount altogether.
To look into:

[ ] Discount bug
[ ] Failing/Erroring tests

I haven't yet had a chance to do a QA pass on this, so it may have some bugs. But I think I got all the references and handled the conversion correctly. Bits I know I touched:

modal cart (order base template)
_attendee_summary.html
_transaction_receipt.html
attendees.html
shop.html (sidebar cart)
order_alert email (body & body_inlined & body_plaintext)
order_receipt email (body & body_inlined & body_plaintext)
summary data calculations (price, savings)

Remaining concerns:

Not 100% sure what effect this will have on model tables, in terms of being able to filter by item options.
Alternate solution to this problem would be to disallow editing of discounts / item options that have already been purchased, and to remove the ability to ever really delete them. That may be a better route – really not sure – but it doesn't necessarily conflict with this one. Caching would still be useful from a query complexity perspective.

After talking about this with someone, I am once again convinced that caching is the future!

I'll look over this branch, but as you said, it's not mutually exclusive with keeping items around forever. I think we should (eventually) not delete items but either offer an exposed interface to permanently disable them or keep them in the database for filtering/data purposes.

So just to clarify, the effect on model tables is that you won't be able to filter for item options that you've deleted. We could "fix" that by filtering by item option name & item name, but... that isn't much of a fix and could easily result in incorrect groupings.

Yeah, that's more or less what I was thinking in terms of keeping deleted items in the database (though I guess that would also entail keeping deleted item options in the database...)
With those concerns in mind, do you still want this reviewed and merged?

Oh, yes, absolutely. If we do end up keeping deleted items around, we can always re-create any deleted items from the cached values!

Plus this ticket being merged will help with sliding scale implementation.

and Manual CRUD.

This will need a merge migration, or just switching the dependency of the 0011 migration to the latest master migration.

Not sure if it's this branch or master, but it seems to fail some tests:
Creating test database for alias 'default'...
.F.E.................E..................
======================================================================
ERROR: test_dwolla_payment_form (brambling.tests.functional.test_order_forms.PaymentFormTestCase)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/harris/.virtualenvs/brambling/lib/python2.7/site-packages/mock.py", line 1201, in patched
    return func(*args, **keywargs)
  File "/Users/harris/Projects/Clients/LittleWeaver/django-brambling/brambling/tests/functional/test_order_forms.py", line 191, in test_dwolla_payment_form
    form = DwollaPaymentForm(order=order, amount=Decimal('42.15'), data={'dwolla_pin': pin, 'source': source}, user=person)
  File "/Users/harris/Projects/Clients/LittleWeaver/django-brambling/brambling/forms/orders.py", line 550, in __init__
    self.sources = dwolla_get_sources(dwolla_obj, event)
  File "/Users/harris/Projects/Clients/LittleWeaver/django-brambling/brambling/utils/payment.py", line 120, in dwolla_get_sources
    access_token = dwolla_get_token(user_or_order, event.api_type)
  File "/Users/harris/Projects/Clients/LittleWeaver/django-brambling/brambling/utils/payment.py", line 74, in dwolla_get_token
    dwolla_set_tokens(dwolla_obj, api_type, oauth_data)
  File "/Users/harris/Projects/Clients/LittleWeaver/django-brambling/brambling/utils/payment.py", line 35, in dwolla_set_tokens
    expires = timezone.now() + datetime.timedelta(seconds=data['expires_in'])
KeyError: 'expires_in'

======================================================================
ERROR: test_dwolla_charge__user (brambling.tests.integration.test_dwolla.DwollaChargeTestCase)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/harris/Projects/Clients/LittleWeaver/django-brambling/brambling/tests/integration/test_dwolla.py", line 55, in test_dwolla_charge__user
    source='Balance',
  File "/Users/harris/Projects/Clients/LittleWeaver/django-brambling/brambling/utils/payment.py", line 139, in dwolla_charge
    access_token = dwolla_get_token(sender, event.api_type)
  File "/Users/harris/Projects/Clients/LittleWeaver/django-brambling/brambling/utils/payment.py", line 74, in dwolla_get_token
    dwolla_set_tokens(dwolla_obj, api_type, oauth_data)
  File "/Users/harris/Projects/Clients/LittleWeaver/django-brambling/brambling/utils/payment.py", line 35, in dwolla_set_tokens
    expires = timezone.now() + datetime.timedelta(seconds=data['expires_in'])
KeyError: 'expires_in'

======================================================================
FAIL: test_subject__organization_editor (brambling.tests.functional.test_invites.InviteTestCase)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/harris/Projects/Clients/LittleWeaver/django-brambling/brambling/tests/functional/test_invites.py", line 25, in test_subject__organization_editor
    self.assertEqual(mail.outbox[0].subject, "{} has invited you to edit {}".format(invite.user.get_full_name(), event.name))
AssertionError: u'User4 Test has invited you to help manage Test event' != 'User4 Test has invited you to edit Test event'

----------------------------------------------------------------------
Ran 40 tests in 13.458s

FAILED (failures=1, errors=2)
Destroying test database for alias 'default'...

Again, not sure if this is on this branch or on master, but I attempted to create a discount and apply it to a previous order (from the organizer side), but the discount had no effect.

With those above things fixed (or determined to be on master) and making sure that interactions between deleted items and discounts is reasonable, I think that this is ready.

I also still think at some point we should keep all items in the database to refer to later. But the caching is good anyway, since it preserves the state of the item at the time of purchase, which is also important.

Not applying discounts to completed orders is the new correct behavior, because it was really weird and unintuitive that you could do that in the first place. :-p

Oh. That makes sense. We should probably display a message or something saying it's not allowed—or not show the tab at all. But that sounds like an issue on master.

Merging in master fixed the invite bug. The other two are also master-related. I am not 100% sure, but I'm fairly confident that they are the result of the dwolla test refresh token expiring...

So I think they're safe to ignore for the purposes of merging this branch.

Cool. I'll do a little more checking things, but I anticipate merging this in a few minutes.

Looks good. It's a bit weird that you can end up with a discount that has no applicable items, but I can't think of a better way of handling that and it doesn't seem severe, since the worst case is that an organizer has a discount that doesn't do anything.


Add girder_client to setup.py

Closes #867

Can you remove girder-client from requirements-dev.txt?  No need to have it in both.

Can you remove girder-client from requirements-dev.txt? No need to have it in both.

@manthey  OK, I removed it.

I'm not sure why CI is failing.  I'll look into it.

Something changed in Circle-CI, so fixing CI was a bit more work than expected.  In addition to fixing CI, I've added tests for Python 3.8 and a simple test to ensure that our wheels import successfully.


Build error with old LLVM versions

Look at the xenial-arm64 Travis build:
afl-llvm-pass.so.cc:39:10: fatal error: 'llvm/IR/DebugInfo.h' file not found

#include "llvm/IR/DebugInfo.h"

Seems that with old LLVM the header is `llvm/DebugInfo.h".
Note that this header is not included in original AFL, so probably we broken the compatibility woth LLVM < 3.7.
I say 3.7 cause is the first version with the header inside IR that I've found googling.
This needs more investigation, as a quick fix I added
#include <llvm/Config/llvm-config.h>

#if (LLVM_VERSION_MAJOR <= 3) && (LLVM_VERSION_MINOR < 7)
#include <llvm/DebugInfo.h>
#else
#include <llvm/IR/DebugInfo.h>
#endif

But I'm not sure about the LLVM version.

Not working fix. llvm/Config/llvm-config.h is not present in old llvms. We have to manage it in the Makefile.

Just curious until how far it needs to support old LLVM versions ? egg, LLVM 3.7 2015

I don't really know but a Travis build (ubuntu 16.04) fails to build LLVM mode with this errors.

And this is strange cause clang-6 is installed but probably the script is using the wrong llvm-config and it is not using LLVM 6 but the Ubuntu 16.04 default one.

A fix can be also to decide to not support these LLVM versions and fix Travis

I would not like to drop the support. there are still people out there who test on specific configurations (where their old software they still have to maintain is running).
that being said - I think afl only supported 3.8 onwards anyway?
@hexcoder- you should know :)

The first working llvm_mode from original afl was with llvm 3.4, but since then we have modified some places (in AFL++). I tested always with stock ubuntu 16.04 supplied llvm 3.8.0. I will check, how llvm 3.4 cooperates with AFL++.

is this issue still open?

One open point is:
llvm/Config/llvm-config.h is generally present on older llvm versions (even on my 3.4), but not in our xenial-arm64 travis build it seems. I do not understand, why.
I want that fixed.
This currently prohibits llvm_mode on arm64 there.

I added some debug output to arm64 travis output - maybe that helps you:
find / -name llvm-config.h
apt-cache search clang | grep clang-
apt-cache search llvm | grep llvm-
dpkg -l | egrep 'clang|llvm'

Thanks, you fixed it!.

@hexcoder- for travis I set hard:
LLVM_CONFIG=llvm-config-6.0

The LLVM config file lies in:
/usr/include/llvm-6.0/llvm/Config/llvm-config.h

and now llvm_mode works:
https://travis-ci.com/vanhauser-thc/AFLplusplus/jobs/289760791


Using catch_unwind for any response errors would be better

Report
This way, no Rust panic would be ignored
Steps to Reproduce
Not relevant.
System Information
Not relevant.
rustc --version
protoc --version
flutter doctor

Made redundant by #257


Tutorial is confusing

Tried following the video tutorial, but it's in french.
Tried following the text tutorial, but it's not explained well enough.
"Now replace the values in the .js from this repository of the according variables, by the values of the three variables you found, here is an example of how it should look in the end : "
This means nothing to me, since I don't know anything about java or any sort of script editing. Please make it more user friendly.

Hey there!! Hopefully I can help you with this. At least a little bit.
I'll be providing a bit of extra context as well to (hopefully) make it easier to understand.
Since it sounds like you don't program, I recommend opening up a plain text file (Notepad on Windows (or Notepad++ which is for programming) or TextEdit on Mac should be fine. If you want to get a bit fancier, you can download VS Code) and either copying the code (in main.js) from the repository into the document to make it easier to edit OR downloading the code and opening up the main.js file into your editor.
In JavaScript (the programming language used – it's available on all web browsers), a variable just holds data. It's like a box with a label on it and the variable name is that label.
In the case of this script, there are four spots you want to update the data inside of the variable:
var authorization = "Bearer ";
var client_tid = ""; // replace by X-Client-Transaction-Id value
var client_uuid = "***"; // replace by X-Client-Uuid value
var username = "YourUsernameHere" // replace with your username
The "var" is just a type of keyword that tells the browser "hey, this is the name of this variable, so when I use this name in the code, use the data stored in here". You'll want to replace the *** with data that you get from the developer tools in your browser.
Right click in your browser and hit "Inspect" to bring up the Developer Tools. If you look towards the top of the developer tools, you'll see a series of small tabs. You want to click the "Network" one. Then you'll want to hit the button that says "XHR" (Firefox) / "Fetch/XHR" (Chrome). It'll bring up a list of connections that the site is bringing up over the network. I recommend using the filter in the Network tab to search for all.json (which is the one the example uses). Click it.

In this second panel/section staying on the first tab (where it says "Headers"), scroll down to the "Request Headers" section. Scroll down to where it says "Authorization". Copy the info in the second column. You can leave out the keyword "Bearer" when you copy it because it's already inside of the string (collection of characters) inside of the variable.
If you scroll down a bit further, you will see the X-Client-Transaction-Id and the X-Client-Uuid sections. Copy and paste the info in the second column inside of the variable where the *** is.
Then lastly add your username.
Make sure you leave the the quotation marks!! It tells the browser what kind of data type it is (in this case, these are strings). The code won't run properly if you remove them.
Once that's done, check over the other options inside of the delete_options variable and see if you want any of them enabled / disabled. (If you want it enabled, use the keyword true (without quotations), otherwise use the keyword false. They're a data type called a boolean and it's basically yes / no lol.) It looks like the Lyfhael put some detailed explanations inside the code (between the /* */) for each section. I recommend reading them to see what you would like to enable.
(I personally enabled the from_archive because I downloaded my archive, as well as set my before & after dates under the old_tweets section.)
Once you're done, copy the code in its entirety. Inside of the developer tools while on X / Twitter, hit the "Console" tab and paste the code. Hit enter. The code should successfully run – all you'll need to do is wait.
(I found the code does not run in Firefox, but appears to work fine in Chrome.)
I hope this helps a bit. I know code can be confusing, especially if you don't know how to do it. 😅 Maybe someone will fork this and make a plugin or something at some point that is more user-friendly.

@trainerkelly that was a really helpful comment! I edited it slightly to update the readme, pull request at https://github.com/Lyfhael/DeleteTweets/pull/85

@mialondon Thank you!!


[WIP] Adds progress bar animations for deploying code

This PR improves the UI of deploying code by adding a progress bar so you have some feedback of how long the process will take (and to ensure nothing is hanging). You can test it out with:
t2 init
t2 run index.js

You'll see a fancy progress bar quickly go from 0% to 100%.
The only thing I'm not sure about is how to monitor LAN connection.write progress well. As is, it just hits 100% immediately because the through stream I'm using just gets passed the entire bundle from deploy.js (remoteProcess.stdin.end(bundle)). I need some way to monitor progress in the stream's backpressure. @LinusU or @rwaldron, do you have any ideas of how I might be able to do that?

I'm closing this because I don't have a path forward for both types of connections (SSH and USB).


fix: bypass handler function for non-prerendered dynamic routes without fallback

Summary
THIS IS A DRAFT PR, SEE TASK LIST
We currently support the fallback: false option by routing to the ODB handler function, which serves a 404 when the request hits a dynamic route without a fallback that has not been prerendered. This is undesirable because it creates a function invocation and runs getStaticProps unnecessarily.
This PR fixes this behaviour by:

[x] only creating ODB redirects for dynamic routes with fallback !== false
[x] creating additional redirects to serve custom 404s statically in all locales
[ ] ensuring ISR 404 pages are still redirected to the ODB function
[ ] adding documentation to warn i18n users who don't prerender all their locales

Test plan
See test coverage
Relevant links (GitHub issues, Notion docs, etc.) or a picture of cute animal
Fixes #1179

🧪 Once merged, make sure to update the version if needed and that it was published correctly.

adding documentation to warn i18n users who don't prerender all their locales

Is the motivation for this due to Matt's comment or is this a nice to have? I'm not sure this is necessary (unless I'm missing something) as it appears it's the intended behavior according to the docs (excerpt below).

For pages using getStaticProps with Dynamic Routes, all locale variants of the page desired to be prerendered need to be returned from getStaticPaths. Along with the params object returned for paths, you can also return a locale field specifying which locale you want to render. For example:

Thanks @hu0p, that last item on the checklist is just because the current behaviour will render all locales regardless of whether a user specifies them in getStaticPaths. The new behaviour will 404 for unspecified locales, which is the correct behaviour, as you pointed out, but probably needs to be called out in the release notes.

Got it. Thanks for the clarification! Watching this as much as I can. I appreciate both of your work on all of this. Thank you! I've been eying that highlighted portion of the redirects file off and on for months.


Publish to Terraform Registry

Have you considered publishing this provider to the Terraform Registry ( https://registry.terraform.io/browse/providers?tier=official%2Ccommunity ), would make it soo much easier for everyone to use, no more having to download & install it manually :)

@zahiar Thank you for your feedback.
Unfortunately, publishing the custom provider seems to be closed beta yet.
https://www.hashicorp.com/blog/announcing-the-terraform-0-13-beta/

@suzuki-shunsuke Thanks for taking a look - hopefully one day soon we'll have your provider in the registry! :)

Yes please register for the new registry, that would improve the provider installation a lot!

I found that we can publish the provider to the Terraform Registry if our request is approved.
I'll try it.

The terraform-provider-graylog organization has not completed the provider publishing application process.
In order to begin publishing providers to the Terraform Registry:
Send an email to<EMAIL_ADDRESS>with a description of the Terraform providers you would like to publish.
Provide us with a GPG Public Key (in ASCII-Armor format) for the keypair you will use to sign the provider releases.
Once your application is approved, you can use this screen to publish Terraform providers to the Terraform Registry.
For more information, read our documentation on Publishing Terraform Providers to the Terraform Registry

I did the following actions according to the document https://www.terraform.io/docs/registry/providers/publishing.html .

Add document to this repository's docs
Release v1.0.3-0 which is signed with the GPG key
Send an email to HashiCorp

Now I'm waiting the response from HashiCorp.

Hi folks,
I have a good news.
My request was approved and this provider was published to the Terraform Registry 🎉 🎉 🎉
https://registry.terraform.io/providers/terraform-provider-graylog/graylog
We can read this provider's document at the registry.
https://registry.terraform.io/providers/terraform-provider-graylog/graylog/latest/docs
The document is work in progress so I'll update it later.
And using Terraform v0.13, we can install this provider from the Terraform registry.
terraform {
  required_providers {
    graylog = {
      source = "terraform-provider-graylog/graylog"
      version = "1.0.3-1"
    }
  }
}

$ terraform init

Initializing the backend...

Initializing provider plugins...
- Finding terraform-provider-graylog/graylog versions matching "1.0.3-1"...
- Installing terraform-provider-graylog/graylog v1.0.3-1...
- Installed terraform-provider-graylog/graylog v1.0.3-1 (self-signed, key ID DB205F1CE2708DF8)

Partner and community providers are signed by their developers.
If you'd like to know more about provider signing, you can read about it here:
https://www.terraform.io/docs/plugins/signing.html

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

$ terraform version
Terraform v0.13.0-rc1
+ provider registry.terraform.io/terraform-provider-graylog/graylog v1.0.3-1

Note that the Terraform v0.13 and publishing the third party provider to the Terraform Registry is still beta.
Thank you.

The old version of this provider can't be installed from the Terraform Registry because they aren't signed by GPG.
I'll release v1.0.3 later.

I have released v1.0.3.
I'll close this issue few days later if there is no problem.


Identify who created an object and who updated an object

The requirements owner is now checking the validity of data created and updated in ANET.
If the requirements owner finds invalid data, then I must find the created date or updated date in the database.
Then I must find the respective auditLogger log file.
Then I must find the log file entry and email it to the requirements owner so he can send an email to the super user.
Would it be possible to also display the super user who created the object and the date/time and also display the super user who updated the object and the date/time.  This information would only be visible to administrators.

@midmarch @gjvoosten @cemalettin-simsoft
This is still a valid requirement.
The so-called "ANET trainers" cannot look at objects (e.g. principals, principal positions, locations) to see which super user created the object and last updated the object.  Being able to identify the super user who created the object / last updated the object and when they did it, allows the trainers and myself to take immediate corrective action with the super user.  This keeps the data accurate and saves time down the road because myself and the trainers don't have to correct the data.
Currently it is a laborious process from me to look in the log files to see which super user did the damage.  And the trainers don't have access to the log files nor is it their job to check the log files.  The two trainers are volunteers and train ANET when they have time.  ANET is not their primary duty.


HIVE-27824:Upgrade Ivy to 2.5.2

What changes were proposed in this pull request?
Upgrade ivy to 2.5.2
Why are the changes needed?
Fix CVE-2022-46751
Does this PR introduce any user-facing change?
No
Is the change a dependency upgrade?
Yes, Dependency tree attached in the jira
How was this patch tested?
Built locally, relying on pre-commit tests of the PR.

@nrg4878 @saihemanth-cloudera Please review this.


[Feature Request]:   Automatically Close Dropdowns and Menus When Clicking Outside of These Element

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
Requesting the addition of functionality to automatically close UI elements such as the brush dropdown list, download options, and ratio settings when a user clicks outside of these elements. This enhancement will improve the user experience by preventing clutter and confusion.
Use Case
Ensuring that UI elements close when clicking outside of them will make the interface cleaner and more intuitive, providing a better user experience.
Benefits
Benefits:
Improved user experience by reducing UI clutter.
Enhanced intuitiveness of the interface.
A more professional and polished look for the "Draw It Out" project.
Add ScreenShots

Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I'm a SSOC'24 contributor
[X] I want to work on this issue

Kindly assign to me ASAP.

@HarshadaGirase You can work on only one issue at a time.

Kindly assign to me


Security concerns

Unfortunate
Originally posted by @bryjen in edb0c03
@rima1881 @genericlearner
please fix

Wonderful! Amazing! Subarashi!
I had a dream that this would happen. You know, sometimes I get dreams of events that looked like they would happen in the future. When I tuck myself into bed late at night, I think to myself "Damn, i feel like somebody's gonna be leaking an api key tonight". However, I look at myself and realize that its impossible for that to happen to me. I'm better, I say to myself. It has been months since this dream has last appeared to me, and so, like any normal human being, I forgot about it.
However, after this series of events, I realized that everything happened as foretold by my dreams. Everything was true. I'm glad that I'm not part of whatever has transpired. If so, it would have been life changing. My career would be cut early, and instead of figuring out how to make backend or frontend software, I would be figuring out the optimal temperature for the friers in mcdonalds. I'm sure that my colleagues have realized that they will be working at mcdonalds or burger king soon - it is an inevitability.
@rima1881  @genericlearner


Refactor .ics exports for new time formats

Summary
Fixes the Export Calendar as .ics file feature. I forgor 💀 about it on #679
Test Plan
Check that downloading the .ics file works

[ ] Courses occur on the correct days of the week
[ ] Courses occur at the right time
[ ] Courses begin and end at the right times in the year (date-wise)
[ ] Finals occur at the right time and date

Issues
Closes #

@ap0nia , I've made the unit test use Fall 2023 as its placeholder since quarterStartDates gets its data from a hardcoded array, so placeholderTerm would return undefined.
Would it be more correct to add a placeholderTerm to termData so that this term runs correctly, or to keep the test case as is with Fall 2023?


Updated comments in resolve.rs to reflect actual data strcture used.

r? @alexcrichton
(rust_highfive has picked a reviewer for you, use r? to override)

Thanks!
@bors r+

:pushpin: Commit 0f9442ffc2091fc17df4827c2bede4c36374d038 has been approved by ehuss

:hourglass: Testing commit 0f9442ffc2091fc17df4827c2bede4c36374d038 with merge<PHONE_NUMBER>25d5ec07785245a182398216bc25f2...

:sunny: Test successful - checks-azure
Approved by: ehuss
Pushing<PHONE_NUMBER>25d5ec07785245a182398216bc25f2 to master...

@hbina Thanks for spotting this inconsistency!


CircleIndicator2 is not working with recyclerview snaphelper

I'm using support version which is implementation 'me.relex:circleindicator:1.3.2' . After i attach this to recyclerview and snaphelper, the indicator is not showing. The CircleIndicator for viewpager working but CircleIndicator2 is not showing at all with recyclerview. I tried added adapter observable which is stated optional but still same.

Hi. show your code, please.

`<me.relex.circleindicator.CircleIndicator2
android:layout_width="wrap_content"
android:layout_height="48dp"
android:id="@+id/dotindicator"
android:visibility="visible"
app:ci_drawable="@drawable/active_dots"
app:ci_drawable_unselected="@drawable/deactive_dots"
android:layout_alignParentRight="true"
android:layout_below="@+id/select_title"
android:layout_marginRight="10dp">
    </me.relex.circleindicator.CircleIndicator2>`

`private void SetUpRecycle(){
rda = new RecyclerDefectAdapter(this,defectLists);
rv.setAdapter(rda);
rv.setLayoutManager(new GridLayoutManager(this,2,GridLayoutManager.HORIZONTAL,false));
rda.notifyDataSetChanged();
    PagerSnapHelper snapHelper = new PagerSnapHelper();
    snapHelper.attachToRecyclerView(rv);
    ci.attachToRecyclerView(rv,snapHelper);
}`

Hi. show your code, please.

Above is my code, xml and java code, please let me know what is the problem..

Recently you said that you tried adding adapter observable. It is missed in SetUpRecycle.

I tried that before, still no changes so i removed that line.

We can't run this piece of example to try to reproduce this error.
Show your working code, with an adapter and data that you insert to an adapter.


cmd/go: go.mod can not lock indirect dependencies version

What version of Go are you using (go version)?

go1.14.7 windows/amd64

Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (go env)?
go env Output
set GO111MODULE=
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\18511\AppData\Local\go-build
set GOENV=C:\Users\18511\AppData\Roaming\go\env
set GOEXE=.exe
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=C:\Users\18511\go
set GOPRIVATE=
set GOPROXY=https://proxy.golang.org,direct
set GOROOT=c:\go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLDIR=c:\go\pkg\tool\windows_amd64
set GCCGO=gccgo
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=C:\Users\18511\AppData\Local\Temp\go-build311380846=/tmp/go-build -gno-record-gcc-switches

What did you do?
There are 3 go modules A: v1.0.0, B:v1.0.0, C:v1.0.0. Now it is known that B:v1.0.0 depends on A:v1.0.0, and C:v1.0.0 depends on B:v1.0.0. When B:v1.0.0 -> B:v2.0.0, A:v1.0.0 -> A:v2.0.0 (incompatible upgrade), use go get -u B to upgrade the version of B in the C project, B was upgraded to v2.0.0, and A was also upgraded to v2.0.0, causing the C project to fail to run.
What did you expect to see?
I hope lock the indirect dependency version
What did you see instead?

There isn't a way to enable locking indirect dependency versions in libraries in the general case, as that would cause problems elsewhere. It was considered during the design of the Minimal Version Selection algorithm (see https://research.swtch.com/vgo-mvs).
If you're not looking to update indirect dependencies, you probably should not use -u flag with go get.
Finally, in the example you shared, a jump from v1.0.0 to v2.0.0 is not expected to be backwards compatible per semantic version rules. Did you mean to use something like v1.0.0 to v1.1.0 instead?
I believe this is working as intended. If you think there is a specific problem, please elaborate.
/cc @bcmills @jayconrod @matloob per owners.

This does seem like it's working as intended. Requirements in go.mod files are minimum versions, not pinned versions. It should be safe to upgrade to any later version of the same module.
Note that higher major versions (v2.0.0 and above) technically belong to different modules. So if example.com/A is the original module, example.com/A/v2 is the v2 module. The go command can't upgrade across major versions, so the upgrade from<EMAIL_ADDRESS>to<EMAIL_ADDRESS>shouldn't happen.

At present, there are indeed many upgrade management solutions in github that do not use the standard go package. When using these packages, you often use go get -u to upgrade your own dependencies. However, the use of the -u parameter has been upgraded. Indirect dependency, which may cause the project to fail to start normally. Why does the version management of go not depend on the interval setting of the version?

Why does the version management of go not depend on the interval setting of the version?

Modules work differently than other dependency management systems, which are traditionally designed around constraint satisfaction algorithms. The module system is designed around minimal version selection, which is a fast, predictable algorithm at the cost of some flexibility. Modules must follow semantic versioning and must declare module paths matching their major versions. As long as those rules are followed, go get -u won't automatically upgrade to an incompatible version, since a new major version of a module (after v2) is treated as a distinct module by the algorithm.
You may find the vgo blog posts interesting, especially The Principles of Versioning in Go. They go into depth about the initial design of modules.
Closing this issue, because it doesn't sound like there's a specific bug to fix here.


Create Button Bug

First of all, thanks for building this project for the Meteor community. I'm really excited to get it working with my app, and would like to contribute to its development if I can. But I am having some trouble and suspect there is some kind of bug...
When creating a post through the Admin panel, the "Create" button doesn't submit the form. For an example, please checkout the microphone-orion tutorial: https://github.com/fuzzybabybunny/microscope-orionjs
One thing is really strange: in that project, it's possible to create a new "Post," but not a new "Comment." Saving edits to preexisting Comments and Posts works fine, too.  When you create a new post, clicking Create validates the form and gives errors if they're missing or formatted incorrectly, but other than that it doesn't seem to do anything.
I don't understand why this is the case. The console shows no errors, and none of the debugging I've tried has turned up an answer. I've tried a few different browsers and they all have the same problem. Is this a bug?

I'm also experiencing this issue

Did this problem disappear?

Yes, at least in my later efforts it doesn't seem to be a problem.


Cannot install package, failing at "mkdirp build && browserify -r ./:biojs-xpression -o build/xpression.js'"

I currently  have issues to install the npm package in my project. I'm using nvm as my npm version tool and try to install biojs-xpression via  npm  v2.11.3 (node v0.12.7) on an Ubuntu 14.04 machine.
Is there an issue with the latest stable package release or has this something to do with my setup?
$ npm install biojs-xpression
\
><EMAIL_ADDRESS>install /<MY PROJECT DIRECTORY>/biojs-xpression
> npm run build

><EMAIL_ADDRESS>build /<MY PROJECT DIRECTORY>t/node_modules/biojs-xpression
> mkdirp build && browserify -r ./:biojs-xpression -o build/xpression.js

sh: 1: mkdirp: not found

npm ERR! Linux 3.13.0-74-generic
npm ERR! argv "/home/jj/nvm/versions/node/v0.12.7/bin/node" "/home/jj/nvm/versions/node/v0.12.7/bin/npm" "run" "build"
npm ERR! node v0.12.7
npm ERR! npm  v2.11.3
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR<EMAIL_ADDRESS>build: `mkdirp build && browserify -r ./:biojs-xpression -o build/xpression.js`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script 'mkdirp build && browserify -r ./:biojs-xpression -o build/xpression.js'.
npm ERR! This is most likely a problem with the biojs-xpression package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     mkdirp build && browserify -r ./:biojs-xpression -o build/xpression.js
npm ERR! You can get their info via:
npm ERR!     npm owner ls biojs-xpression
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /<MY PROJECT DIRECTORY>/node_modules/biojs-xpression/npm-debug.log
npm ERR! Linux 3.13.0-74-generic
npm ERR! argv "/home/jj/nvm/versions/node/v0.12.7/bin/node" "/home/jj/nvm/versions/node/v0.12.7/bin/npm" "install" "biojs-xpression"
npm ERR! node v0.12.7
npm ERR! npm  v2.11.3
npm ERR! code ELIFECYCLE

npm ERR<EMAIL_ADDRESS>install: `npm run build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'npm run build'.
npm ERR! This is most likely a problem with the biojs-xpression package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm run build
npm ERR! You can get their info via:
npm ERR!     npm owner ls biojs-xpression
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /<MY PROJECT DIRECTORY>/npm-debug.log

Hi Jessica,
you seem to not have dev(elopment) dependecies installed. Does it work if you try installing after globally installing the dev dependencies (mkdirp, browserify, etc.)?
Kind regards,
Benedikt


Missing @medatadata[beat]

This is when using the beats protocol.
I followed the common output pattern in logstsash:
output {
  elasticsearch {
    hosts => ["http://<IP_ADDRESS>:9200"]
    index =><EMAIL_ADDRESS>  }
}

It seems @metadata is missing, therefore @metadata[beat] is missing. This configuration in logstash results in indexes like<EMAIL_ADDRESS>I would expect the index name to be something like my_beat_name-2020.05.25 for a standard output to elasticsearch.
It would be useful to add an example configuration in logstash pipeline to send data to elasticsearch.

I'm not completely sure what the problem is.
The metadata field exists only in Logstash (https://www.elastic.co/guide/en/logstash/current/event-dependent-configuration.html#metadata) and so I assume whatever you are missing, it is probably to be configured in Logstash.

In the formatter we have:
 message = {
            '@timestamp': self._format_timestamp(record.created),
            '@version': '1',
            'host': self._host,
            'level': record.levelname,
            'logsource': self._logsource,
            'message': record.getMessage(),
            'pid': record.process,
            'program': self._program_name,
            'type': self._message_type,
        }

In the message dict, we need the key beat. The beat key is expected in common logstash beat input configuration.
I think that will solve the problem.
Here's a reference: https://www.elastic.co/guide/en/beats/metricbeat/current/logstash-output.html

  elasticsearch {
    hosts => ["http://localhost:9200"]
    index => "%{[@metadata][beat]}-%{[@metadata][version]}"
  }
}```
This is a common configuration in logstash to send data to elasticsearch when receiving data from beats. Hence, I requested to have the 'beat` field in the metadata.

Well, you could achieve that by adding the @metadata field to the extra fields and use no extra_prefix so the additional fields will be placed on the top-level of the event:
formatter = LogstashFormatter(extra_prefix=None, extra={'@metadata':{'beat': 'your-beat-name', 'version': 'whatever-version'})

Alternatively, you can subclass the LogstashFormatter class and customize it to your needs.
I'm not completely against adding a @metadata to the formatter in general, it just seem quite specific to me. The "common" configuration you talk about is only common for the various Beats products. Anyway, feel free to submit a well written PR for adding a @metadata argument to LogstashFormatter.

Thanks. I will make some research to better understand this and will submit a PR if necessary.

I did some tests.
This worked:
formatter = LogstashFormatter(extra_prefix=None, extra={'@metadata':{'beat': 'your-beat-name', 'version': 'whatever-version'})

The next step is to make @metadata available in the LogstashFormatter itself. I am thinking of adding the key to https://github.com/eht16/python-logstash-async/blob/master/logstash_async/formatter.py#L91
Does it mean, you have to add @metadata to the constant FORMATTER_LOGSTASH_MESSAGE_FIELD_LIST?

Yes, otherwise the added @metadata field would be moved in the extra field structure.


Why does only ToTensor handle numpy arrays?

Out of all the classes in transforms.py, only ToTensor handles numpy arrays.
It would be much smoother if all classes handle numpy arrays.
I can make a PR if this is something you guys can accept.

Most of the transforms (if not all) handle PIL Images, which is a wrapper around numpy arrays. The ToPILImage transform can convert a numpy array to an Image and then it would be compatible with all of the transforms.

I think it would be better to keep the data wrapped as an Image for as long as possible as then we can utilize some metadata such as colorspace etc. We can also then use built in mehtods on the Image type to do things like resize or scaling.
If your data is in numpy format, I suggest adding the ToPILImage transform to the start of your Compose and this will then convert it correctly for you.

I second what @alykhantejani said, you can seamlessly convert from PILImage to numpy arrays and vice versa, while PILImages have more information about the image (colorspace for example).


Support MySQL 8 (currently MySQL 8 is not supported)

(I am using a digitalocean mysql 8 instance)
Right now the CLI doesn’t support MySQL 8 as it using an older client.

This might automatically be fixed with the introspection rewrite in Rust.
Also, lift is able to connect to the instance but it is unable to save migrations. It is able create the _Migrations table but when I run prisma lift save --name 'init' it is unable to save the migration in the file system and unable to create tables.

Made a separate issue for the second part of this issue: https://github.com/prisma/lift/issues/107

Default MySQL installation on Windows via e.g. Chocolatey is MySQL 8 - so having this (or at the very least a more informative error message!) would be nice.

Possible workaround posted here: https://github.com/prisma/prisma2/issues/38#issuecomment-532176320

Just a note, MySQL is aware:

In Mac i use this for solve problem
$ mysql -uroot -pPassowrd
$ ALTER USER 'root'@'localhost' IDENTIFIED WITH mysql_native_password BY 'Strong Pass';

and work good but get another problems in use #516

Yes, that is the workaround I linked to in https://github.com/prisma/prisma2/issues/384#issuecomment-532589572 - we will continue our investigation of #516 and see if this is a side effect or another unconnected problem.

I did some investigation and was able to confirm that for me, it happens only in the prisma2 init flow with MySQL 8. The connection to the database at this stage is done on the typescript side and doesn't go through the migration engine nor the introspection engine, as far as I could tell.
I can also confirm the migration issue mentioned above is a separate bug, I'm working on fixing it.

I believe that this issue was also a cause of a panic I recently received from prisma2 dev. Reverting to mysql5 fixed the issue.
dieff@hex ~/W/B/c/api> prisma2 dev

   Watching for changes in prisma/schema.prisma
   No changes yet

 Error

   Error: Error in migration engine: thread 'tokio-runtime-worker-0' panicked at 'get data_type', src/libcore/option.rs:1034:5
   stack backtrace:
      0: backtrace::backtrace::libunwind::trace
                at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.29/src/backtrace/libunwind.rs:88
      1: backtrace::backtrace::trace_unsynchronized
                at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.29/src/backtrace/mod.rs:66
      2: std::sys_common::backtrace::_print
                at src/libstd/sys_common/backtrace.rs:47
      3: std::sys_common::backtrace::print
                at src/libstd/sys_common/backtrace.rs:36
      4: std::panicking::default_hook::{{closure}}
                at src/libstd/panicking.rs:200
      5: std::panicking::default_hook
                at src/libstd/panicking.rs:214
      6: migration_engine::main::{{closure}}
      7: std::panicking::rust_panic_with_hook
                at src/libstd/panicking.rs:481
      8: std::panicking::continue_panic_fmt
                at src/libstd/panicking.rs:384
      9: rust_begin_unwind
                at src/libstd/panicking.rs:311
     10: core::panicking::panic_fmt
                at src/libcore/panicking.rs:85
     11: core::option::expect_failed
                at src/libcore/option.rs:1034
     12: core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &mut F>::call_once
     13: <alloc::vec::Vec<T> as alloc::vec::SpecExtend<T,I>>::from_iter
     14: sql_schema_describer::mysql::SqlSchemaDescriber::get_table
     15: <core::iter::adapters::Map<I,F> as core::iter::traits::iterator::Iterator>::fold
     16: <alloc::vec::Vec<T> as alloc::vec::SpecExtend<T,I>>::from_iter
     17: <sql_schema_describer::mysql::SqlSchemaDescriber as sql_schema_describer::SqlSchemaDescriberBackend>::describe
     18: <sql_migration_connector::sql_database_migration_inferrer::SqlDatabaseMigrationInferrer as migration_connector::database_migration_inferrer::DatabaseMigrationInferrer<s
ql_migration_connector::sql_migration::SqlMigration>>::infer
     19: <migration_engine::commands::infer_migration_steps::InferMigrationStepsCommand as migration_engine::commands::command::MigrationCommand>::execute
     20: <migration_engine::api::MigrationApi<C,D> as migration_engine::api::GenericApi>::infer_migration_steps
     21: migration_engine::api::rpc::RpcApi::create_sync_handler
     22: tokio_executor::enter::exit
     23: tokio_threadpool::blocking::blocking
     24: <futures::future::lazy::Lazy<F,R> as futures::future::Future>::poll
     25: futures::future::chain::Chain<A,B,C>::poll
     26: <futures::future::then::Then<A,B,F> as futures::future::Future>::poll
     27: <futures::future::lazy::Lazy<F,R> as futures::future::Future>::poll
     28: futures::future::chain::Chain<A,B,C>::poll
     29: <futures::future::then::Then<A,B,F> as futures::future::Future>::poll
     30: <futures::future::map::Map<A,F> as futures::future::Future>::poll
     31: <futures::future::either::Either<A,B> as futures::future::Future>::poll

I had migrated my data development to a new instance of mysql running 8.x, instead of 5.7.x.
Here are details for my system:
$ uname -ra
Linux hex 5.3.0-arch1-1-ARCH #1 SMP PREEMPT Mon Sep 16 03:29:01 UTC 2019 x86_64 GNU/Linux
$ prisma2 --version
<EMAIL_ADDRESS>binary version: 2292f8d0c3bd11fe9cca7c6df4a10061bf58fd18

The output from the error above is probably a case of bad error handling. Rather than panicking and dumping the Rust stacktrace, there should probably be a message to the user. Let me know if I should open a separate issue.

Please do that @Dieff - then we can let a developer double check that this was already resolved via recent work on the migration engine (which gave you this nice error) 🚀

Internal note: Dropping from this sprint, we will pick this up again in 2 weeks when @do4gr is back.

If you mean the Introspection part, that the TS Introspection can not handle MySQL 8, then I agree. This might take some time.

Yes exactly, sorry for the ambiguity.

(I was actually just using my comment to repeat this and make it explicit for everyone ;) )

Do you think we’ll get MySQL 8 support with Prisma 1? I’m almost done building a Prisma (1) app and wanted to deploy to Digital Ocean but just found out that they only support MySQL 8 and Prisma 1 doesn’t.
I’d use Prisma 2 if support was there but I know the official release is still a bit away so I’m kind of stuck. Any advice?

Do you think we’ll get MySQL 8 support with Prisma 1?

We will not have MySQL 8 support with Prisma 1. I suggest using MySQL 5.7 with some other provider for now and migrate to DO with MySQL 8 once Prisma 2 is there.

Hi, @divyenduz. Thank you for your response. That's a little disappointing but I really appreciate the transparency. 👍

MySQL 8 is fully supported with Prisma2 for quite some time now (as the mentioned CLI command was fully rewritten) 🚀


Potential JSON Schema issues

Some potential improvements and/or issues in the JSON Schema:

[x] $defs keyword in the schema was only added in draft 2019-09 (see also #127 )
[x] additionalProperties: true is the default and could be removed
[x] "patternProperties":  with a pattern ".*" is basically equivalent to additionalProperties and thus can be simplified a bit.
[x] "enum": ["WKB"] is equivalent to "const": "WKB", the same applies to "enum": ["counterclockwise"]
[x] PROJJSON has a new schema version, 0.5
[x] The bbox schema looks weird. Are more than 4 values allowed? Right now it would allow [0,1,2,3,"asdsad"]. Could probably also be simplified using min/maxItems... I think you were looking for something like "items": {"type": "number"}, "minItems": 4
[x] By the way, the spec says double for epoch, but this is not enforced in the schema and could be an int (or should this be "number" in the spec?)
[x] I understand the spec that you can either specify an array of geometry types or a single geometry type as string or Unknown (so always as a string, not in an array). If this is the case, the schema doesn't check it. ["Polygon", "Unknown"] is valid.
[x] The Z suffix to the geometry types is not part of the JSON Schema it seems

Happy to work on PRs, just let me know whether all this is correctly captured.

I am not very familiar with JSON schema details, but that all sounds correct from the geoparquet side.

The bbox schema looks weird. Are more than 4 values allowed? Right now it would allow [0,1,2,3,"asdsad"]. Could probably also be simplified using min/maxItems... I think you were looking for something like "items": {"type": "number"}, "minItems": 4

I am currently updating this field in https://github.com/opengeospatial/geoparquet/pull/88, so your feedback there is certainly welcome! (we are basically already doing something with items and minItems now, just spelling out the 4 or 6 values explicitly)

"enum": ["WKB"] is equivalent to "const": "WKB", the same applies to "enum": ["counterclockwise"]

Although it is not the case right now, but we are planning to add more options in the future, so can maybe keep it like that? (although also the enum wouldn't allow any other value right now, so it wouldn't really matter)

Okay, I'll draft a PR.

I am currently updating this field in #88, so your feedback there is certainly welcome!

Done.

"enum": ["WKB"] is equivalent to "const": "WKB", the same applies to "enum": ["counterclockwise"]

Although it is not the case right now, but we are planning to add more options in the future, so can maybe keep it like that? (although also the enum wouldn't allow any other value right now, so it wouldn't really matter)

Cou can always change it back to enum once you've decided to add a new option. :-)

Call 11/7 - Merging this should block on #134, just to make sure it's doing what we think it's doing.
It'd also be good to break up #131 into multiple PR's. @tschaub will do the geometry updates in a new PR.

#140 proposes changes to the geometry types.


[Chore]Update .licenserc.yaml(ignore .svg checker)

should also remove this https://github.com/apache/incubator-seatunnel/blob/dev/.github/workflows/license.yml#L26

should also remove this https://github.com/apache/incubator-seatunnel/blob/dev/.github/workflows/license.yml#L26

To avoid regression.

I will add more type files in directory docs

I will add more type files in directory docs

thanks for your reminder:)


Issue when building pytorch image

When attempting to build a pytorch image I run:
./scripts/docker_build_ml.sh pytorch
and get the following when it gets to torchvision:
From some responses I've seen on google this might be a CUDA version issue, but I'm a bit in over my head so not sure how to proceed.
`
Step 15/22 : RUN git clone -b ${TORCHVISION_VERSION} https://github.com/pytorch/vision torchvision &&     cd torchvision &&     python3 setup.py install &&     cd ../ &&     rm -rf torchvision &&     pip3 install "${PILLOW_VERSION}"
---> Running in 18d6e6d7c9d0
Cloning into 'torchvision'...
Note: checking out '78ed10cc51067f1a6bac9352831ef37a3f842784'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
git checkout -b
Traceback (most recent call last):
File "setup.py", line 13, in
import torch
File "/usr/local/lib/python3.6/dist-packages/torch/init.py", line 188, in
_load_global_deps()
File "/usr/local/lib/python3.6/dist-packages/torch/init.py", line 141, in _load_global_deps
ctypes.CDLL(lib_path, mode=ctypes.RTLD_GLOBAL)
File "/usr/lib/python3.6/ctypes/init.py", line 348, in init
self._handle = _dlopen(self._name, mode)
OSError: libcurand.so.10: cannot open shared object file: No such file or directory
`

What version of JetPack-L4T are you running on your Jetson?
You can check by running cat /etc/nv_tegra_release.   If you are running L4T version < R32.4.4 but >= R32.4.2, you can check-out one of these branches:

https://github.com/dusty-nv/jetson-containers/tree/L4T-R32.4.2
https://github.com/dusty-nv/jetson-containers/tree/L4T-R32.4.3

If your JetPack version is older than JetPack 4.4, you would need to upgrade JetPack versions to build it successfully.

Thanks Dusty for the reply.
I am running R32.4.4, just downloaded the fresh image last Tuesday.

What version of JetPack-L4T are you running on your Jetson?
You can check by running cat /etc/nv_tegra_release. If you are running L4T version < R32.4.4 but >= R32.4.2, you can check-out one of these branches:

https://github.com/dusty-nv/jetson-containers/tree/L4T-R32.4.2
https://github.com/dusty-nv/jetson-containers/tree/L4T-R32.4.3

If your JetPack version is older than JetPack 4.4, you would need to upgrade JetPack versions to build it successfully.

I am running R32.4.4, just downloaded the fresh image last Tuesday.

Ah right, sorry I forgot to mention that you also need to set the default docker-runtime to nvidia - see here:
https://github.com/dusty-nv/jetson-containers#docker-default-runtime
This is so that CUDA is available during build-time (i.e. when building torchvision in the container)

Ya that would do it.
Thanks for adding.
Currently troubleshooting, as I'm getting an error about what was added.
'
unable to configure the Docker daemon with file /etc/docker/daemon.json: invalid character '"' after object key:value pair
'

I am running R32.4.4, just downloaded the fresh image last Tuesday.

Ah right, sorry I forgot to mention that you also need to set the default docker-runtime to nvidia - see here:
https://github.com/dusty-nv/jetson-containers#docker-default-runtime
This is so that CUDA is available during build-time (i.e. when building torchvision in the container)


Feature: Song config

The two songs that are built in are cool, but it would be really cool if there was a config where we could put songs in using the note variables.

I'm looking for a way to give the user the opportunity to tune in his own songs.
I have several solutions in my mind.
The best one so far in my opinion is this one :

prompt for a string array
ask the song name
add it to the Atom play piano package top menu.
Persist it into the serializedState of the package.

Pros :

You can add as much song as you like
Cons :
A bit longer to do. Not actually sure how i could prompt for the musicsheet and name.

For a faster result, i could just put some "Free slots" that could be overrided in the package settings.
Pros :

Easy and fast
Cons :
The number of custom songs will be limited.

I'll be starting with the second solution, i'll try the first one if i have some free time.
Anyway, if you want to permanently add a song and share it for any users, pull request are welcome ;) !
WDYT ?

As requested, in the new v3.2.0, you can now configure up to Three custom songs for atom-play-piano package.
You can refer to the updated read-me for 'how to'.
Hope you'll like it :) !


add logos

Ⅰ. Describe what this PR did
add logos

Codecov Report

Merging #2336 into develop will decrease coverage by 0.01%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             develop    #2336      +/-   ##
=============================================
- Coverage      51.62%   51.61%   -0.02%
+ Complexity      2693     2691       -2
=============================================
  Files            517      517
  Lines          16728    16728
  Branches        2038     2038
=============================================
- Hits            8636     8634       -2
  Misses          7284     7284
- Partials         808      810       +2

Impacted Files
Coverage Δ
Complexity Δ

...o/seata/server/coordinator/DefaultCoordinator.java
54.35% <0%> (-0.52%)
28% <0%> (-1%)

...in/java/io/seata/server/session/GlobalSession.java
84% <0%> (-0.45%)
72% <0%> (-1%)


Relax constraints on Python version

At the moment, we have python==3.10 in the README. This was only the case because the handling of the toml library changed between versions 3.10 and 3.11. We should be able to relax this constraint.

The CI runs fine on 3.10-3.12 (have not yet tested the new 3.13!). I've dropped the suggestion for 3.10 specifically in #7

Closed by merge of #7!


Correct a link in documentation

This pointed to https://github.com/evancz/elm-components, but that link now simply redirects to https://github.com/evancz/elm-effects, which is not what one wants here.
(Alternatively, and maybe in any case, make sure that https://github.com/evancz/elm-components redirects to https://github.com/evancz/elm-architecture-tutorial, I guess?)

This is the right fix, thanks :)

Okay, the fix should be on the website. Thanks again!


Tracking: integrate with usage of nss-resolve

Fedora 33 released and now uses systemd-resolved for its DNS lookups from glibc's level. This means that the resolv.conf approach is not as useful anymore. I have modified /etc/nsswitch.conf to avoid nss-resolve for now, but this is not a long-term solution. I've started a discussion on Ask Fedora, but would like to let developers here be aware of it in case there's something that can be done here too.
I suspect we'll need something from systemd to support network namespaces better, but I don't know.

As a band-aid, it should be possible to bind-mount over /etc/nsswitch.conf as well (just creating, e.g., /etc/netns/protected/nsswitch.conf with a hosts line that doesn't use systemd-resolved). I'll test this approach.


flutter sdk升级到最新版本后运行不起来

dependencies:
  desktop_multi_window:
    git:
      url: https://github.com/Kingtous/rustdesk_desktop_multi_window
      ref: master

flutter 版本

Flutter 3.8.0-1.0.pre.4 • channel master • https://github.com/flutter/flutter.git
Framework • revision a752c2f154 (2 days ago) • 2023-02-01 00:41:16 -0500
Engine • revision 1703a39662
Tools • Dart 3.0.0 (build 3.0.0-187.0.dev) • DevTools 2.20.1

执行 flutter run -d windows -v 后报错
[  +20 ms] Building Windows application... (completed in 9.9s)
[   +1 ms] Exception: Build process failed.
[   +4 ms] "flutter run" took 10,346ms.
[   +3 ms]
           #0      throwToolExit (package:flutter_tools/src/base/common.dart:10:3)
           #1      RunCommand.runCommand (package:flutter_tools/src/commands/run.dart:740:9)
           <asynchronous suspension>
           #2      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1287:27)
           <asynchronous suspension>
           #3      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #4      CommandRunner.runCommand (package:args/command_runner.dart:212:13)
           <asynchronous suspension>
           #5      FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:288:9)
           <asynchronous suspension>
           #6      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #7      FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:236:5)
           <asynchronous suspension>
           #8      run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:64:9)
           <asynchronous suspension>
           #9      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #10     main (package:flutter_tools/executable.dart:91:3)
           <asynchronous suspension>

flutter的问题，插件会跟随stable channel适配

要是能更新下readme就好了。。。很多东西要猜，比如：desktop_lifecycle都没人说要手动添加一下依赖？

要是能更新下readme就好了。。。很多东西要猜，比如：desktop_lifecycle都没人说要手动添加一下依赖？

原项目的问题，不需要手动去各个平台集成一下代码了，我删了也OK。不过与windows_manager还是有冲突？Unhandled Exception: MissingPluginException(No implementation found for method ensureInitialized on channel window_manager)

在 3.7.5版本上也是一样的


Code cleaning

Risk or conflicts between versions.

Hello @PierreLaville, the merge has quite a few conflicts, Is there a way for you to start resolving part of the conflicts?


Add a bit more info for unsafe features

Actual Situation
I just upgraded from Copier 7.2 to 8.1, and got "bitten" by the safety measures that were implemented in that change (the --UNSAFE and --trust options). I actually think this is a great idea, especially going with the --trust option as an alternative to --UNSAFE, but might suggest adding a note to the error message to help those encountering this issue in the future. Right now, I just got an error that
Template uses unsafe feature: tasks

I had to dig through the CHANGELOG (fine; it showed the issue, but didn't really give motivation for why my previously trusted template was now doing something "unsafe") and then dig further until I came across issue #1137 (and corresponding PR).
Desired Situation & Proposed Solution
To avoid that legwork for each user, perhaps that error could just be changed to note that users who trust their templates should run with either the --UNSAFE or --trust option if they trust the template? Looks like this might be as simple as changing line 109 in copier.errors.py to be something like:
super().__init__(
    f"Template uses potentially unsafe feature{s}: {', '.join(features)} \n"
    "If you trust this template, consider adding the `--trust` option when running `copier copy`."
)

Thanks for all your hard work, seems like an awesome tool so far!

I like it! :+1: Just a minor suggestion: I think just stating copier copy may be misleading when seeing this message during copier update, so how about changing it like this?
 super().__init__(
     f"Template uses potentially unsafe feature{s}: {', '.join(features)} \n"
-    "If you trust this template, consider adding the `--trust` option when running `copier copy`."
+    "If you trust this template, consider adding the `--trust` option when running `copier copy/update`."
 )

Sounds good! See #1280.


Add test cases to the Configurator after version 2.7

What is the purpose of the change
Add test cases to the Configurator after version 2.7

Codecov Report

Merging #8560 (b36098f) into 3.0 (8739374) will increase coverage by 0.03%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                3.0    #8560      +/-   ##
============================================
+ Coverage     62.94%   62.97%   +0.03%
- Complexity      310      311       +1
============================================
  Files          1117     1117
  Lines         46735    46735
  Branches       7010     7032      +22
============================================
+ Hits          29416    29431      +15
+ Misses        14057    14041      -16
- Partials       3262     3263       +1

Impacted Files
Coverage Δ

...rg/apache/dubbo/monitor/support/MonitorFilter.java
66.66% <0.00%> (-25.50%)
:arrow_down:

...he/dubbo/remoting/transport/netty/NettyServer.java
70.17% <0.00%> (-3.51%)
:arrow_down:

...pache/dubbo/registry/support/AbstractRegistry.java
78.10% <0.00%> (-1.46%)
:arrow_down:

...ting/zookeeper/curator/CuratorZookeeperClient.java
71.42% <0.00%> (-0.99%)
:arrow_down:

.../java/org/apache/dubbo/config/ReferenceConfig.java
77.16% <0.00%> (-0.46%)
:arrow_down:

...apache/dubbo/rpc/protocol/dubbo/DubboProtocol.java
65.38% <0.00%> (-0.35%)
:arrow_down:

...in/java/org/apache/dubbo/config/ServiceConfig.java
70.76% <0.00%> (-0.28%)
:arrow_down:

...apache/dubbo/common/extension/ExtensionLoader.java
79.00% <0.00%> (-0.21%)
:arrow_down:

...che/dubbo/common/compiler/support/JdkCompiler.java
63.55% <0.00%> (ø)

...va/org/apache/dubbo/registry/RegistryNotifier.java
85.71% <0.00%> (ø)

... and 17 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 8739374...b36098f. Read the comment docs.


Remove unneeded seriesBound computation

New Pull Request
We used to persist the bounding rectangle of the series in the Tooltip
object in the property seriesBound, without ever using it.
Also removed the commented code that references that property.
With this patch, we found a significant performance improvement in our project. The call to getBoundingClientRect was triggering many "Recalculate Style", which have now disappeared.
Type of change
Performance improvement.
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

@junedchhipa Should I leave the changes on dist/apexcharts.js in the PR?
They were automatically introduced by the tests.

Hey @yacinehmito
Thanks for your contribution and sorry for the delay in reviewing this PR.
Can you please remove the dist file as it should only be generated for a new build/release?
Thanks!


GuiType.HOPPER Click Events Not Firing

When using GuiType#HOPPER for a GUI's type, click events do not get fired. Not even default event.

Apologies for the delay on this issue, I tried a few things then I found out that Spigot doesn't call the event for Hoppers because the InventoryHolder is null. Because of that I decided to remove the Hopper option for now. I'll try finding a work around for this and re-add it.


Command always fails after first run

Expected Behavior
I should be able to run the nyc consecutively and get the same outcome each time.
Observed Behavior
The second time I run the nyc command (wrapping mocha), the command fails.
Here's the command I'm using:
./node_modules/.bin/nyc ./node_modules/.bin/_mocha packages/*/test/*-test.js

Here's the error I'm getting (after the first run, which succeeds):
SyntaxError: Invalid or unexpected token
    at createScript (vm.js:80:10)
    at runInThisContext (vm.js:139:10)
    at Object.vm.runInThisContext (/tmp/antora/node_modules/nyc/node_modules/istanbul-lib-hook/lib/hook.js:142:16)
    at Module._compile (module.js:599:28)
...

If I remove node_modules and run yarn again, then the command succeeds the next time I run it, but fails again the time after that.
Code (or Repository) that Reproduces Issue
https://gitlab.com/opendevise/oss/antora (branch nyc-issue-749)
git clone -b nyc-issue-749 https://gitlab.com/opendevise/oss/antora.git

Use yarn to install dependencies.
(ignore the Gulp build)
Forensic Information
Operating System: Fedora 26
Environment Information:
Node 8.9.3
yarn 1.3.2

It's worth noting the deprecated istanbul 1.1.0-alpha.1 works on the exact same repository with no issue.


dotnet nuget sign doc

Summary
dotnet 6.0.0-preview.5 SDK has added dotnet nuget sign command.
Happy to iterate to make the doc better based on feedback.
Fixes https://github.com/dotnet/docs/issues/25049

Thanks @Youssef1313 and @tdykstra for your feedbacks!
I've addressed most of the comments, except the non-loc comments.
May I know if you could point me to an example of non-loc comments? I tried to search in the repo but failed.

May I know if you could point me to an example of non-loc comment? I tried to search in the repo but failed.

https://github.com/dotnet/docs/pull/25050#discussion_r667107788

For no-loc syntax, see also https://docs.microsoft.com/en-us/contribute/markdown-reference#non-localized-strings

Thanks @Youssef1313 and @tdykstra for your help and quick response!
All comments are addressed :)

Staging looks good, this PR is ready to merge as soon as the comment from @adegeo is addressed.

Just noticed -- the Options section wasn't put in alphabetic order to match the synopsis.

Just noticed -- the Options section wasn't put in alphabetic order to match the synopsis.

Thanks! Fixed the order in Options section to match the synopsis.


different checksum

I'm seeing 'be697c0baccfae2641fd1ed036e96334' as the checksum for my patched file. different version of bzr? I have 2.6.0+bzr6595-6ubuntu1

There are many "correct" checksums. Each depends on the version of bzr you are using. Just verify the file is correct and propose a patch with the new extra checksum please.


tor: provide service file

Like for example mdev does, in /ect/sv/
@IslandAlpha

Gotcha, I'll get to work on it.


LinterContext fields analysisOptions and declaredVariables can be made private.

These do not appear to be used outside of the file in which LinterContext is declared, so they can be removed or made private.
Any objections?
CC @pq @bwilkerson

@incendial @rrousselGit In case either of you are using these getters or know anyone who is.

I think LinterContext is not available to the plugins. But if I'm wrong, then I definitely never used it.

Oh, you're right. It looks like all of the support we have for the linter package is in lib/src. I'd thought we'd made some of it public.
In which case we ought to be able to make any changes we want without impacting anyone. Thanks!

Closed in 7629e1e669d0309c35c9e568d1758bd495b67de8


Update anaconda-project version

[x] fixes #176

I also saw in here where there is instruction to install anaconda-project but no version was recommended. I don't know if I should add a version number there as well.

Yes please let's align them.

Done!


Wrong assumption about remote ip

Macbook with Eden <IP_ADDRESS> :
Eve (RPI4): <IP_ADDRESS>
I have: internal nw: 192.168.1.* with Eden and Eve
Adam Nats to external IP
Eden has a wrong assumption about EVE IP. It's <IP_ADDRESS> not <IP_ADDRESS>
(base) Vladimirs-MacBook-Air:eden fleandr$ ./eden eve ssh
ssh: connect to host <IP_ADDRESS> port 22: Operation timed out
FATA[0005] ssh error: exit status 255
(base) Vladimirs-MacBook-Air:eden fleandr$ ./eden status
✔ Adam status: container with name eden_adam is running
        Adam is expected at https://<IP_ADDRESS>:3333
        For local Adam you can run 'docker logs eden_adam' to see logs
✔ Registry status: container with name eden_registry is running
        Registry is expected at https://<IP_ADDRESS>:5000
        For local registry you can run 'docker logs eden_registry' to see logs
✔ Redis status: container with name eden_redis is running
        Redis is expected at <IP_ADDRESS>:6379
        For local Redis you can run 'docker logs eden_redis' to see logs
✔ EServer process status: container with name eden_eserver is running
        EServer is expected at http://<IP_ADDRESS>:8888 from EVE
        For local EServer you can run 'docker logs eden_eserver' to see logs

--- context: default ---
EVE state: registered

✔ EVE REMOTE IPs: <IP_ADDRESS>; fe80::9c9f:d71:819b:1770
        Last info received time: 2021-04-28 15:32:04 +0300 MSK
✔ EVE memory: 0 B/0 B
✔ EVE Request IP: <IP_ADDRESS>

I can see EVE REMOTE IPs: <IP_ADDRESS>.
EVE request IP is an assumption of Adam, which one is under docker network

Yes but we rely on that for eden eve ssh and it doesn't work

@giggsoff tested https://github.com/lf-edge/eden/pull/608.
./eden eve ssh  works fine
OS: macOS Big Sur
 ./eden status
✔ Adam status: container with name eden_adam is running
        Adam is expected at https://<IP_ADDRESS>:3333
        For local Adam you can run 'docker logs eden_adam' to see logs
✔ Registry status: container with name eden_registry is running
        Registry is expected at https://<IP_ADDRESS>:5000
        For local registry you can run 'docker logs eden_registry' to see logs
✔ Redis status: container with name eden_redis is running
        Redis is expected at <IP_ADDRESS>:6379
        For local Redis you can run 'docker logs eden_redis' to see logs
✔ EServer process status: container with name eden_eserver is running
        EServer is expected at http://<IP_ADDRESS>:8888 from EVE
        For local EServer you can run 'docker logs eden_eserver' to see logs

--- context: default ---
EVE state: registered

✔ EVE REMOTE IPs: <IP_ADDRESS>; fec0::f91c:c4f6:7eb4:ff52; fec0::13f7:49de:5029:c709; fe80::522c:3724:efa4:35aa; <IP_ADDRESS>; fec0::277d:4645:7cfd:7ff0; fec0::5e4b:1df0:c92c:f593; fe80::5054:ff:fe12:3457
        Last info received time: 2021-05-03 22:40:38 +0300 MSK
✔ EVE memory: 401 MB/3.5 GB
✔ EVE on Qemu status: running with pid 56628
        Logs for local EVE at: /Users/rd/GolandProjects/eden/dist/default-eve.log
✔ EVE Request IP: <IP_ADDRESS>
------

 ./eden eve ssh
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ECDSA key sent by the remote host is
SHA256:9j74TDLU7AjzNvmrva+iIwjOk3r1vRgchfOSpa2rc0I.
Please contact your system administrator.
Add correct host key in /Users/rd/.ssh/known_hosts to get rid of this message.
Offending ECDSA key in /Users/rd/.ssh/known_hosts:13
Password authentication is disabled to avoid man-in-the-middle attacks.
Keyboard-interactive authentication is disabled to avoid man-in-the-middle attacks.
EVE is Edge Virtualization Engine

Take a look around and don't forget to use eve(1).
15461694-49ed-4d58-a34d-bd43a76b4406:~#

solved