ionic resources command problems

From @mflmartin on November 4, 2016 10:2
Short description of the problem:
ionic resources does not generate ios and android icons & splash screens in any way
ionic resources --icons generates icons for ios but NOT android. They are generated into the resources/android folder, BUT not copied and propertly renamed to platform/android/res, which means that when you compile the app, you get the cordova robot.
ionic resources --splash generates splash for ios but NOT android They are generated into the resources/android/splash folder, BUT not copied and propertly renamed to platform/android/res, which means that when you compile the app, you get the cordova robot.
What behavior are you expecting?
That it works correctly.
Steps to reproduce:

place icon.png and splash.png in the resources folder
Execute ionic resources
They are not created propertly.
Execute ionic resources --icons
Android icons in platform/res, are not propertly updated
Execute ionic resources --splash
Android splash in platform/res, are not propertly updated

Which @ionic/app-scripts version are you using?
Your system information:
Cordova CLI: 6.4.0
Gulp version:  CLI version 3.9.1
Gulp local:
Ionic Framework Version: 2.0.0-rc.1
Ionic CLI Version: 2.1.4
Ionic App Lib Version: 2.1.2
Ionic App Scripts Version: 0.0.39
OS:
Node Version: v6.4.0
Copied from original issue: driftyco/ionic-app-scripts#312

From @mflmartin on November 4, 2016 10:44
I found a res folder at the ROOT of my project containing android resources. It might be that it creates it in the ROOT folder of the project, instead of placing it inside the platforms/android folder. If this helps you narrow it down more.

From @ferranvila on November 6, 2016 9:2
@mflmartin Me too. I think this happens after the new cordova-android version: 6.X.X. If you downgrade to 5.2.2 the icon is displayed but the splash screen don't.

Possibly related https://github.com/driftyco/ionic/issues/9060

Problem with cordova-android, should be fixed in 6.1.0, but it's not available on npm yet.
See changelog here: https://github.com/apache/cordova-android/blob/master/RELEASENOTES.md, and issue here: https://issues.apache.org/jira/browse/CB-12077

https://github.com/driftyco/ionic/issues/9060#issuecomment-259445756
Can be closed.


Is it possible to host a Winforms control in a Dlang UI?

The thing is that I'd like to use some 3rd-party controls which are only offered as Winforms controls. Is there a way to host a winforms control in a Dlang UI window like how we can host Wpf controls in Winforms applications (and vice-versa)?

Probably not, considering winforms is a .NET language (C# / VB.NET, etc...). I don't think D can use .NET libraries.


I am not able to use onDestroy() lifecycle hook in my flutter application? Can you tell me what is the workaround to this?

Could you please give some more details?

Actually, I wanted my application to perform some tasks everytime it is closed, even if its closed forcefully.
To do that, I tried to tap into onDestroy() lifecycle method, by creating a plugin. Since no other option was known to me and I certainly didn't find it that easy on Official docs.
Please help me, I am new to flutter.

Can you please provide the information I asked for ;-)

Adityas-MacBook-Air-2:~ adityas$ flutter doctor -v
[✓] Flutter (Channel beta, v0.7.3, on Mac OS X 10.13.6 17G65, locale en-IN)
• Flutter version 0.7.3 at /Users/adityas/developments/flutter
• Framework revision 3b309bda07 (4 weeks ago), 2018-08-28 12:39:24 -0700
• Engine revision af42b6dc95
• Dart version 2.1.0-dev.1.0.flutter-ccb16f7282
[!] Android toolchain - develop for Android devices (Android SDK 28.0.2)
• Android SDK at /Users/adityas/Library/Android/sdk
• Android NDK location not configured (optional; useful for native profiling support)
• Platform android-28, build-tools 28.0.2
• Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b01)
! Some Android licenses not accepted.  To resolve this, run: flutter doctor --android-licenses
[!] iOS toolchain - develop for iOS devices (Xcode 9.4.1)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 9.4.1, Build version 9F2000
✗ libimobiledevice and ideviceinstaller are not installed. To install, run:
brew install --HEAD libimobiledevice
brew install ideviceinstaller
✗ ios-deploy not installed. To install:
brew install ios-deploy
• CocoaPods version 1.5.3
[✓] Android Studio (version 3.1)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin version 27.1.1
• Dart plugin version 173.4700
• Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b01)
[✓] IntelliJ IDEA Community Edition (version 2018.2.2)
• IntelliJ at /Applications/IntelliJ IDEA CE.app
• Flutter plugin version 28.0.4
• Dart plugin version 182.4129.13
[✓] VS Code (version 1.27.2)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 2.18.0
[!] Connected devices
! No devices available
! Doctor found issues in 3 categories.

Yeah, It worked while the thread was suspended. But this method does not do the job when the app is terminated purposefully.
Anyways, thanks for the help.
I think there is no way to do it in Flutter.

I think there is no way to do it in Flutter.

I rather think there is no way to do it in iOS.

Yes, I also read in a few articles saying that no such hooks exist in IOS, while some say that such an arrangement can be made.
But, I think this type of hooks must be provided.

this is happening to me also and I think xyx.luan.audioplayers is causing this.

this is happening to me also and I think xyx.luan.audioplayers is causing this.

currently, I finding in AppLifecycleState but not found destroy state


Poor Extraction of Mathematical Expressions in Document Conversion Output

I tried extracting data from a PDF containing the image below.

However, the result was

The output was not accurate, especially for the basic mathematical expressions.

I tried extracting data from a PDF containing the image below.

However, the result was

The output was not accurate, especially for the basic mathematical expressions.

@jiraiya1729 Thanks for the report. Mathematical expressions in digital PDFs are often encoded in various obfuscated and incomplete ways, such as seen in your case.
We are actively working on bringing an equation recognition model to Docling soon, to solve these issues.

@jiraiya1729 Thanks for the report. Mathematical expressions in digital PDFs are often encoded in various obfuscated and incomplete ways, such as seen in your case. We are actively working on bringing an equation recognition model to Docling soon, to solve these issues.

Hi, when do you plan to address and release the modified version?

@cau-git
Thanks for taking notice, as i am also struggling for exact same issue. Is there any workaround to this problem?
Is there any workaround to this problem?

Nougat (https://github.com/facebookresearch/nougat) does math...


Add :type option to show which element it is (+ related improvements)

I see the following downsides in some aspects of Capybara:

find always returns instance of Element, not a subclass of it. Therefore some methods that make sense only for some kinds of elements aren't provided (e.g. Select#selected_option, FileField#set, Image#loaded?, etc.)
:field, :radio_button, etc. are:

hard to debug if ElementNotFound occurs. Writer of the code may have meant id/name/placeholder/etc. but it's not easy to find if that element really exists on the DOM
difficult to remember which attributes are supported and which are not (is alt attribute supported?)
But people use them as:
have_field('name') looks better than have_css("*[name='name']")
there is no good alternative if you want to use selector-specific options.
expect(page).to have_field('field_id', with: 'something')
expect(page).to have_select('label_text', with_options: ['42', '43'])

Proposed solution:

Add :name, :value, :label_text, :href, etc. selector kinds out-of-the-box to make it easier to find elements in a deterministic way without necessity to write longer css/xpath selectors
Add :type option that specifies which kind of element it is. Examples:

have_selector(:id, 'field_id', type: :field) # additional options specific to type: :field are available
have_selector(:field, 'field_id') # type: :field is implicit if selector kind is :field
find(:id, 'field_id', type: :field) # returns a subclass of Capybara::Node::Element, e.g. Capybara::Node::Element::Field

New methods Capybara.register_element_type and Capybara.register_selector_kind will be added. Capybara.add_selector will be deprecated. It will be possible to register both element type and selector kind using add_selector (some methods will be delegated to registering element type and some others to registering selector kind).
User would be able to define a subclass of Capybara::Node::Element and its relation to one of registered element types (some subclasses will be defined as part of Capybara).
:type won't be used to check element's tag but only to return element of a more specific class and to support type-specific options (like :checked, :disabled, :href, etc that are defined by register_element_type).
This change looks backwards compatible to me.
WDYT?

Sorry for the delay on this - personal issues have kept me away for a while.
At first glance this sounds interesting, although I think it is two different issues and if implemented should probably be done as two different PRs.  A couple of issue

Its not clear to me why add_selector would be deprecated, or what register_selector_kind would be for.
Would you  see this being implemented via changes to the xpath gem, or strictly in capybara.
If :type isn't checking elements tags isn't this opening users up to even more difficult to debug issues?

Its not clear to me why add_selector would be deprecated, or what register_selector_kind would be for.

I played around with code and decided that there's no need to deprecate it. Only element type - related methods (label, filter, description, describe) will be deprecated by adding @deprecated YARD tag.

Would you see this being implemented via changes to the xpath gem, or strictly in capybara.

XPath/css selectors needed for :href or :name are very simple so it doesn't make sense to extract them to xpath gem. If there would be complex enough selectors, probably I'll try to make a change in xpath gem.

If :type isn't checking elements tags isn't this opening users up to even more difficult to debug issues?

I believe :element shouldn't be used for checking element tags as:

L&F of HTML element can be significantly changed from standard.
It would complicate implementation (we have to merge it into css/xpath selectors)
I don't think an idea to merge a tag name into css/xpath selector is a good one. I wouldn't expect Capybara to do it. Probably it makes sense to merge it into selectors like :id but I would vote for selectors to be consistent here.
That would separate responsibilities of element type and selector.

I have been implementing this feature and there's an issue with behavior of Capybara.add_selector if selector/element type with that name was already registered. There are two options:

When it's invoked, replace existing Selector with Selector created from supplied block + replace ElementType with created from the supplied block
When it's invoked, replace existing Selector with Selector created from supplied block + instance_eval block in scope of existing ElementType

Option 1 will be fully compatible with existing behavior of add_selector. But in this case it would be impossible to add selector without not-deregistering element type. Users of 2.x versions will have to invoke add_selector prior to register_element_type. If filter, label, etc. will be removed in 3.0 from Selector, there will be no need to do anything with ElementType from Selector so there will be no this limitation.
Option 2 will break the following use case:
Capybara.add_selector(:beatle) do
  # filter and xpath are invoked here
end
Capybara.add_selector(:beatle) do
  # xpath is invoked here
end
# filter still exists for :beatle element type

I would prefer option 1 as limitation will exist only until 3.0. Do you agree?

I have to think about this some more.  I don't understand why we would be deprecating anything for this change.   It seems to me that just adding support for the :type parameter as the class which results should be, and then adding some new predefined selectors (which really is a different issue than this one) produces the same outcome without massive changes, and still keeping the current flexibility for custom selectors?
As far as calling add_selector twice for the same selector, I would expect it to completely replace the current selector (as I believe it currently does).  Maybe we need to add a Capybara.update_selector or something to allow for changing a selector, or update_selector_type if we really think people will want to be changing the returned element types of the default selectors - of course users could just do something like  Capybara::Selector.all(name).some_method_name = :new_type to change the returned element type too.

I don't understand why we would be deprecating anything for this change.

I want to give users ability to write:
have_selector(:id, 'field_id', element: :field, with: 'contents')

To make it possible custom filters like :with should be part of ElementType, not Selector. Therefore, I'd like to remove this ability from Selector (in future) so it won't be duplicated in two places. If :element isn't supplied, then it's set to @selector.name.

So it seems like I didn't understand what you were suggesting in the first place - I don't think moving the "selection" of elements from the selector to element types is helpful, and seems like its going to end up with more duplication than before.  I think
have_selector(:id, 'field_id', element: :field, with: 'contents')

is going to become highly confusing since with: will no longer have a standard meaning when used with the :id selector.  A user will now also have to add a new ElementType for ever selector type they add.  This seems to add layers of complexity for few if any benefits.  I get the desire for being able to change the type of the returned element, but I don't get what benefit the rest of these changes bring that couldn't just be done with a custom selector.  I'll go look at the PR you just pushed, but as of now I'm not leaning towards this.  If you really need to be able to call random methods on the element type couldn't that just be done with a filter
have_selector(:id, 'field_id', element: :field, call_on_element({with: 'content'}))

or something - while still maintaining the current flexibility  (obviously call_on_element is a terrible name for the filter, but something along those lines)

I guess maybe my real issue with this is that this is really multiple issues that have been intertwined,  I think I read at least 3 things you're trying to change -

Being able to return instances of a subclass of Element for given selectors
Being able to have sets of filters that can be specified for use with any selector (and hopefully allowing for a default set for any given selector)
Add new selectors out of the box

Is that correct?

@abotalov  for # 2 in my list of what I think you're looking for - please take a look at the filter_set branch I just pushed - I think something along those lines would provide the functionality you're looking for without requiring deprecation of a bunch of things, although its just a first stab at it and I may need to spend a bit more time thinking things through

I haven't responded previously as I got some concerns whether this feature has a value at all.
I don't see much value in using :type without any wrapper. It's just some additional code and I would like to use it via some sugar placed on top of it (the sugar might be not a part of Capybara, though).
Consider this example (with sugar):
class LoginPage < BasePage
  field :username_field, :id, 'field_id'
end

login_page = LoginPage.new
expect(login_page).to have_field('field_id') # capybara matcher
expect(login_page).to have_username_field # matcher provided via method_missing, equivalent to have_selector(:id, 'field_id', type: :field)

The fact that field and have_field take inconsistent parameters doesn't look consistent, unfortunately.

Would this solve my problem?
I want to show that the "selected" option for a select element is "Extension". With my current knowledge of Capybara, I cannot do this with simply page.has_field?("Key type", with: "Extension"), because the resultant "match" contains all options.... Not looking for the CSS for the one selected.

@onebree Please ask how do I do things type questions on the mailing list as requested in the README -  or read the docs and look for has_select? with the :selected option

@twalpole thank you, that helps. I thought the item was a field.

I added the reusable sets of filters as PR #1679 so thoughts about it can be added there.  I believe the rest of this was determined to probably not be useful so I'm closing it.  If it is still considered useful we can reopen


Look into creating a system for dealing with immutables

Verifiable immutability - guaranteed - with exceptions if one exposes mutability.

Roslyn extension for compiletime checking for immutability. If public setters, error.


Typo in Uri.resolveUri() documentation

Please see https://api.dartlang.org/stable/1.21.1/dart-core/Uri/resolveUri.html

Updated to handle the case where the base URI is just a relative path - that is: when it has no scheme or authority and the path does not start with a slash.

There should be ...when it has no scheme AND NO authority...

Good point. I was probably going for "neither scheme nor authority", but missed the mark with the current wording.


Update nuget references to 140 version.

note: should re-run strongly typed model code, but leaving as there are issues that need to be resolved before this will build with the new code.

@kevcunnane

should re-run strongly typed model code, but leaving as there are issues that need to be resolved before this will build with the new code.

Does that mean that strongly typed model cannot be used with 140 or?? (Plan to use it in a tool)

That's right. The non-strongly typed model is fine but there are some bugs in the internal mappings that cause problems when running this strongly typed model. It'll work against older versions but not the recent one. I'd suggest opening an issue against this, we can at least track the desire to use this and see if we can resolve the blockers in a future Dacfx update.

Just to be clear: I can get the latest source, by change all DacFX references to 130 (from 140) in order to use the stringly typed model - is that correct?

What is means is you may not be able to use the strongly typed model fully against 130 (SQL2016) or 140 (SQL2017) sources. It hasn't had the T4 templates re-run, so the most up to date set of metadata comes from 120.
You should still be able to run against those target and do queries for existing objects, properties and relationships defined pre-2016, but for newer objects etc. you will have to fall back to the regular (not strongly typed) model.


[FEAT]: Find Python libraries to control LEGO Mindstorms NXT brick

Description
Search for a library able to control BrickLink part 53788 (@alv67 and @gmacario have 1x item available as part of their Mindstorms NXT sets)
The library should work with Python 3.8.x or later.
Additional Information
Test the library on the following target OS/HW:

Windows 10 on personal laptop
Raspberry Pi OS (buster) on Raspberry Pi 4

Document the result in a .md file under /docs

Postponed to a later date since we should not need it for the OpenCV Spatial AI Challenge


ZXP Installation Fails with Code -410

Using both Adobe's included UPIA or Anastasiy's Extension Manager to try installing the extension results in a -410 error code, the likes of which I cannot find any information online about or any other error codes related to this.
To Reproduce
Attempt to install the extension via a ZXP file using either of these two methods.
Expected behavior
The extension installs successfully.
Screenshots

(UPIA and AEM have the same dialog, so I assume AEM uses UPIA with a GUI over it)
Desktop:

OS: Windows
Version 10, 212H

If this has already been reported, I apologize for the duplicate.

dont use the zxp, its deprecated and rarely works, zip method should be good enough


Refactor: Pass payment hash by reference to TrackPayment

See comment:

Update LightningNode trait track_payment to take a reference
Update implementations accordingly

Closed in #179


Expose props to Section collection item

The Item component does this already, and I believe this is an inconsistency.
Although, we can get around this issue by doing this:
function Section() {
  return null
}

Section.getCollectionNode = function* (props) {
  const node = DefaultSection.getCollectionNode(props).next()
  yield { ...node.value, props }
}

I feel this behavior should be consistent across the collection components.

seems reasonable, thanks for the PR
just curious, what're you sending through?

I'm sending an slice prop which will try to slice the number of items within a section and add an expanding menu item so that multiple sections can be glanced quicker, instead of scrolling through a very first large section of items to choose an option from the second section.
A quick doodle:

I'm not sure if I will be able to achieve that, but there may be more use cases for having props shared.


Newbie Looking for Advice!

Hi Justin,
Sorry to add an "issue" to your project, but I was actually hoping to ask for some advice. This has been immensely helpful to me in trying to create an automation for a part time job! I struggled for so long with OAuth2, and after finding your repo it made complete sense. I'm currently hung up on that very issue though... I was just able to get my container running on Google Cloud Run Jobs but, if you're familiar with the service, there is no real CLI. You've already solved this problem I think based on glancing at the recent commits, but when running the code on my local computer previously I'd been manually going to Constant Contact's auth URL and manually pasting the callback URL to authenticate myself. This is an issue now that I'm trying to deploy to GCR. I'm missing an important piece of fundamental understanding when it comes to OAuth2 and how to initialize my access and set up recurring refresh tokens with CC API. Would you be able to help me? You can reach me at<EMAIL_ADDRESS>I hope to hear from you!
Best,
Ashly

Hi Ashly,
I'm glad to hear that the project has been beneficial for you! I completely understand the challenges of automating the OAuth2 process, especially in deployment scenarios like Google Cloud Run. Let's dive into the details:
Token Management:
We utilize a dedicated JSON file (tokens.json) to store and manage access and refresh tokens.
TOKEN_FILE = 'tokens.json'

def ensure_token_file_exists():
    if not os.path.exists(TOKEN_FILE):
        with open(TOKEN_FILE, "w") as file:
            json.dump({
                "access_token": "",
                "refresh_token": "",
                "expires_in": 0
            }, file)

# Call this function at the beginning to ensure tokens.json exists
ensure_token_file_exists()

This strategy is key for avoiding manual steps and ensuring an automated OAuth2 flow.
OAuth2 Flow:

Refreshing the Access Token:

def refresh_access_token():
    token_data = load_tokens_from_file()
    refresh_token = token_data.get('refresh_token')

    if not refresh_token:
        return None

This function fetches the refresh token from the saved tokens file and, if present, uses it to request a new access token.

Saving Tokens:

def save_tokens_to_file(access_token, refresh_token, expires_in):
    expiration_time = datetime.now() + timedelta(seconds=expires_in)
    token_data = {
        'access_token': access_token,
        'refresh_token': refresh_token,
        'expires_at': expiration_time.strftime('%Y-%m-%d %H:%M:%S')
    }
    with open(TOKEN_FILE, 'w') as f:
        json.dump(token_data, f)

After obtaining the tokens, they're persistently saved in the tokens.json file. This ensures the tokens are available for future requests and can be refreshed as necessary.
By managing tokens in this manner and understanding the OAuth2 flow, the need for manual intervention, such as visiting the auth URL, is minimized.
I hope this provides a clearer picture of the OAuth2 process implemented in the repository. Please don't hesitate to reach out if you have further questions or need more insights!
Best wishes,
Justin

Hello!
It's taken me awhile but I'm implementing your above advice and working to adapt your repo to my project! I've hit a wall related to oauth2 yet again though... I feel like it's something simple but cannot figure out what. I have created a tokens.json file but it's currently empty of any data. I have added the same get_access_token() function:
`def get_access_token():
token_data = load_tokens_from_file()
if not token_data:
return None
if is_token_expired(token_data):
    return refresh_access_token()
else:
    return token_data.get('access_token')`

but my code errors when trying to GET/POST to ConstantContact. Specifically when I call the following function:
def create_or_update_contact(self, data):         url = self.api_url + '/contacts/sign_up_form'         headers = {             'Authorization': 'Bearer ' + self.access_token,             'Content-Type': 'application/json'         }         response = requests.post(url, headers=headers, json=data)         response.raise_for_status()         return response.json()
I'm getting the error "TypeError: can only concatenate str (not "NoneType") to str" at the following line:
'Authorization': 'Bearer ' + self.access_token,
My code is an amalgamation of a previous version of constant-sync that utilized Classes (hence the self.access_token) so it may be that I'm trying to Frankenstein parts together in a way that simply won't work... Here's the init method for a little more context:
class ConstantContactAPI:
def init(self, access_token):
self.access_token = get_access_token()
self.api_url = 'https://api.cc.email/v3'`
In short, did I miss something simple or is there a larger disconnect in my code generally? I appreciate your help! It's been difficult to adapt my older version to the recent commits for constant-sync, so if the solution is follow along more closely to match my project to yours (i.e. drop the classes, implement the "HEADERS" and get_auth_headers() in api_integration.py) I'm happy to do so! If I've left out any information or need to clarify anything please ask, I appreciate your help so much!
Best,
Ashly

Hello Ashly,
That's fantastic news—congratulations on successfully implementing the changes and overcoming the OAuth2 hurdles! It's always rewarding to see hard work and persistence pay off.
Interestingly, your journey mirrors my own experience with this project. I actually had to rewrite the entire codebase from scratch to solve more or less the same problems you were facing, especially with OAuth2. It's reassuring to hear that you got it to work, as it validates the effectiveness of the latest changes.
If you have any more questions or run into other challenges, don't hesitate to reach out. Otherwise, best of luck with the rest of your project!
Warm regards,
Justin


Problems with team access channels

When a team doesn't have access to channel ID 1, the radio disappears. Not sure why this is happening.

Never mind I fixed it.


colorscheme isn't actually changing colors. I plugged the repo and set colorscheme shado, but all the colors remain the exact same as if I didn't.

I don't receive any error that "colorscheme shado doesn't exist", or whatever the exact wording is.

Hey @kayte-q I'm super sorry about this! Looking into this now. Had a recent move to lua as well so that may help clear things up. Oddly enough too i found that if you dont load shadotheme after treesitter gets loaded too it may get funky. Not sure if that is the same issue you are having. Will try to figure this out soon.
Thanks for trying the theme though!

I was able to fix some stuff up with the Lua port tonight. Try seeing with it if anything is fixed or not. I'd assume not being you've tried old versions as well but worth a shot. Will look more at this issue tomorrow.
Thanks for bringing it up!!

Hi @Shadorain I ran :PlugUpdate and reloaded nvim, but instead I got this message:
Error detected while processing /home/amber/.local/share/nvim/plugged/shadotheme/colors/shado.lua:
E5113: Error while calling lua chunk: ...er/.local/share/nvim/plugged/shadotheme/colors/shado.lua:129: attempt to index field 'cmd' (a function value)
stack traceback:
...er/.local/share/nvim/plugged/shadotheme/colors/shado.lua:129: in main chunk
Press ENTER or type command to continue
Thank you for helping btw

Sure no need to thank me! 😁
Awesome thank you for testing too. Try the newest commit, I changed it to just run vimscript from lua for the highlight clear command where your's is getting tripped up. Make sure to be running latest nvim version as well!

I updated again and now it's saying "error detected while processing /home/usr/.local/share/nvim/plugged/shadotheme/colors/shado.lua:", then "W18: Invalid character in group name" repeated a bunch of times over. Loading it anyways makes syntax all completely white.

Hm definitely an issue with the version you are running. It isnt supporting the new treesitter highlighting style with @ syntax. Try to build nvim from source and then post the running version here?

I compiled nvim from github and ran that, this time it gave no errors but it was still all white. The compiled version was 0.8.0, the apk version was 0.7.0

Thats super odd... maybe because it is init.vim it doesnt like certain things 🤔  I really am not sure what is going on. Do you have your updated conf online somewhere?

I made a pastebin link for it: https://pastebin.com/h1q4rZUC

update: I the commit before the lua port and got the issue this started with.

Ah gosh... I think you just are missing the set termguicolors piece.  Please let me know! so sorry about the delay!

It worked! Thank you for all the help, and sorry if I wasted your time.

Sure anytime! Glad that worked, no no sorry I didn't think about mentioning that earlier 🤣  No no never a waste. Glad we got that figured out! Good work 😁


MacOS_SDK needs updating from 10.9

Issue description
os-specific/darwin/apple-sdk hard-wires the SDK version to 10.9, but os-specific/darwin/apple-source-releases includes framework versions from 10.11 and 10.10, including IOKitUser.
The IOKitUser then won't work in 10.11, as it includes strings like AVAILABLE_MAC_OS_X_VERSION_10_10_AND_LATER which should be defined in apple-sdk, but aren't defined in 10.9's (obviously).
So basically, apple-sdk needs versioning in the same was as the frameworks.
Steps to reproduce
I found this trying to make a working mplayer package, but anything which tries to #include "/hid/IOHIDDevice.h" from IOKit will hit this problem.
Technical details

System: Mac os X 10.11.5
Nix version: 1.11.2
Nixpkgs version: "16.09pre83147.df89584"

I've started the work to update the whole darwin shebang, but it's a decent amount of work and I'm short on time. I doubt it makes much sense to hand it off in its current state to anyone else, but when I get finished I'll write up the various gotchas so that this isn't so hard for others to pick up next time around.

related to #13779 just so it doesn't get lost

I think this can now be closed.

@matthewbauer what has changed?

Unless someone else has updated it, it still needs a bump. I'll try to get to it soon

@copumpkin will the shebang refactoring remove MacOS_SDK and OSXPrivateSDK from closures?

It should eventually. I actually made an attempt to bump this up to 10.11 (we got a native xhyve build for a couple of git revisions!!) but it got reverted because it broke a bunch of stuff unexpectedly and I haven't had time to investigate. It should be coming back soon though 😄

So what's the status on this issue?

It's on 10.10 so is technically updated now. I wanted 10.11 but that one is trickier

On Apr 21, 2017, at 02:36, Matthew Justin Bauer<EMAIL_ADDRESS>wrote:
So what's the status on this issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

see #37407


Children props as a react component

Children now only accepts String or Array:
https://github.com/deanhet/react-native-text-ticker/blob/7767053d3af1a64380fe9b11016c924b0d344003/index.js#L28-L31
Can you add more to it please?
For now I have conditional rendering in which if the object has url the children will be <Text onPress={}> and just plain string if no url. I'm not sure what to append to just support react component but PropTypes.element and PropTypes.node seem to be choices.
Reason for this issue is that I got this warning all the time:
Warning: Failed prop type: Invalid prop `children` supplied to `TextMarquee`.

Note: you can release this as a patch version 0.12.1 instead of a major version 😄

This can be an option as I found the other way to solve this, sorry for that.


not able to add data to database

This repository is only for reporting bugs or issues. If you need support, please use the forums:

https://laracasts.com/discuss
https://laravel.io/forum

Alternatively, you may use Slack (https://larachat.co/), Discord (https://discordapp.com/invite/mPZNm7A), or Stack Overflow (http://stackoverflow.com/questions/tagged/laravel).
Thanks!

Illuminate/Database/Eloquent/MassAssignmentException with message 'Add [name] to fillable property to allow mass assignment on [App/Company].' error coming while using add data via tinker

Looks like you need to add your mass assignment attributes.
As the template stated, this repository issue area is for reporting bugs or issues with the framework itself. Please reach out to the community channels for assistance.

laracasts.com/discuss
laravel.io/forum
Discord


feat(gs-grid): Add flex renderers for grid.

Add flex renderers to render header & columns.

First render of grid complete.
LGTM


Don't report timeouts while enableTimeouts=false

Timeouts that occcur while enableTimeouts = false should not be
reported when timeouts are enabled again before calling the callback.

Hi @Rob--W,
I agree with @boneskull that I don't really see the necessity. Should others chime in and ask for the same, I'd be happy to reopen the corresponding issue. Note that the built of this PR also reported errors. so it would need some attention before being potentially merged anyway.
Thanks for the effort though!


New version: Spotify.Spotify version <IP_ADDRESS>0.gf994cb0b

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[ ] Have you tested your manifest locally with winget install --manifest <path>?
[X] Does your manifest conform to the 1.2 schema?

Microsoft Reviewers: Open in CodeFlow

Close with reason: Replaced by PR 80581;

Close with reason: Replaced by PR 80581;

Could you reopen this PR? I don't think this PR is needed to be replaced.

@ItzLevvie

cc @denelon: This PR needs to be re-opened.
It replaces the non-versioned URL (which always points to the latest version) with the versioned URL.

@wingetbot run

@wingetbot run

@msftbot reset feedback


REAL HARD CORE Maaaaaaan!!!

 Reall cool application we got here if it does what looks like it does

I was inspired by this example and made a simple script for the video
effect, but I didn’t do such complex formulas as here, it’s very difficult
for me to understand
вт, 9 июл. 2024 г., 18:57 gitgotagit @.***>:

it seems to work
What are your specifics ? mine doesnt work unfortunately. Reall cool
application we got here if it does what looks like it does
—
Reply to this email directly, view it on GitHub
https://github.com/wardzin/animusic/issues/1#issuecomment-2218080178,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVVL5T2KBDNRK5O3FG6MPGTZLQB77AVCNFSM6AAAAABDKW2RBKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJYGA4DAMJXHA
.
You are receiving this because you authored the thread.Message ID:
@.***>


Use RbConfig instead of deprecated Config

This fixes the following warning under ruby 1.9.3-p0:
fssm/lib/fssm/support.rb:40: Use RbConfig instead of obsolete and deprecated Config.

I've got this same warning and have uninstalled and re-installed the fssm gem (currently running fssm-0.2.7) but the warning hasn't disappeared. Is there something else I need to do?
I'm running Snow Leopard, not Lion, if that makes a difference.

@ijy, the warning has been fixed in the source code here on GitHub, but it has not yet been officially released as a gem. The fssm-0.2.7 gem doesn't have the fix. You'll need to wait for fssm-0.2.8 to come out. I don't maintain this project so I don't know when that will be.
In the meantime, the warning is benign so I wouldn't worry too much about it.

Ahhh, that explains it. Thanks for the tip before I start wholesale gem nuking. :) No real biggie. That message is just more of an annoyance than anything else but nothing critical. I just like to try and clear warnings like that when I see them. What's the best way of getting notified when 0.2.8 is released?

@ijy, one way to keep track of gem releases is to sign up for an account at rubygems.org. You can subscribe to your favorite gems and get updates via RSS.

Ah, I didn't know that. Thanks for the tip. All signed up and subscribed to fssm.

With FSSM largely being glue code for other libraries it tends to sit here ignored until someone hits the issue button. My apologies.
My view is that if no significant changes are made then I probably shouldn't do a gem release. I've also had this "you know, I should really..." in the back of my head for a while that I was intending to do a release for, but, uh... I obviously never got around to it.
If you need a release, then that's what you'll get. I have some jiggery-pokery I might end up doing, but either way there will be a new version at some point tonight.

@tdreyno 0.2.8 has been released addressing this as well as a $LOAD_PATH issue.

Thanks @ttilley


Windows 10 Notification auto dismiss

Describe the bug

For windows 10 notifications the banner pops on the display but after its time out the notification dismisses instead of showing up in the action center.
To Reproduce

Steps to reproduce the behavior:

Enable service
Receive notification
Wait for it to time out (3 or 5 seconds etc)
Check action center there will be no notification that you can check after

Expected behavior

Screenshots

Desktop:

OS: Windows 10 build 1909
Ferdi Version Latest 5.4.4 beta 3

Server Used: [e.g. https://api.getferdi.com]

Debug information: https://debug.getferdi.com/...
Additional context

Possible solution mentioned here: https://github.com/electron/electron/issues/3916#issuecomment-567860009

This is still an issue with electron v10.1.1
Is there anything out there discussing this bug?

Cannot reproduce this problem on Windows 10 Pro with the latest nightly.
The notification stays in the notification center also after marking the e.g. WhatsApp message as read.
It only gets dismissed when doing so manually through the notification center dialog.
Please reply in case this still occurs so I reopen this.


Multiple date support

Hey @RichardLindhout! Awesome library. Is there a way to select multiple dates like the screenshot above?

Not yet but I think we should add it, but I'm really short on time a.t.m. but I'm currently building some projects related to dates so maybe within 6 months I will add it.
Ofcourse a PR would also be greatly appreaciated!

Got it, if I were to work on this would you be open to merging? Seems like it would just take an array of year-month-day strings and display them in a list next to / below the calendar.
The normal calendar picker would probably need to be edited to receive an array of dates, in addition to a single date.
Does that sound good to you? If so, I can take a look tomorrow!

Opened PR that solves this at #44

Released in 0.3.0! https://github.com/web-ridge/react-native-paper-dates/releases/tag/v0.3.0


postgres - add indexes to foreign keys

Description
We don't have indexes on foreign keys in our postgres db. This adds indexes to our foreign keys.
Reviewer Notes
I think I caught them all, but worth a double check?
Setup
make db_dev_e2e_populate
make db_test_e2e_populate
Ensure no errors and check for indexes on table columns.
Code Review Verification Steps

Any new migrations/schema changes:

[ ] Follow our guidelines for zero-downtime deploys (see Zero-Downtime Deploys)
[ ] Have been communicated to #dp3-engineering
[ ] Secure migrations have been tested using bin/run-prod-migrations

[ ] Request review from a member of a different team.
[ ] Have the Pivotal acceptance criteria been met for this change?

References

Pivotal story for this change
this article explains more about the approach used.

Added the additional indexes you requested...
Added indexes on any email fields I saw...
I did not add single field indexes on tables that had a composite index as we can use the existing index.

When you're ready to try this on experimental let me know and I'm happy to walk you through the process.


fixed setting of init nibble in function select gpio peripheral register

When replacing LED_GPFBIT and LED_GPIO_BIT i noticed the LED_GPFSEL register does not get set properly.

No idea why this PR has sat around for so long. Sorry about that!


start:dashboard not serving

fresh clone.
npm install && dotnet restore - no errors.
npm run start:dashboard - no errors.
Project is running at http://localhost:8080/
webpack output is served from /dist/
webpack webpacks without errors.
http://localhost:8080/ can't be found.
the /dist/ folder contains the following:
0.js
0.js.map
main-client.js
main-client.js.map
vendor.css
vendor.js
vendor-manifest.json
this seems... lacking.
Know what I'm doing wrong?
Side note, server serves when I launch IIS from VS. Is that how I'm supposed to do things?

Might be wrong but this project is based on ASP.NET MVC so you NEED ASP.NET to take care of your Index.cshtml which can be done only by starting it with dotnet. If you start it with npm it shouldn't work

@daveo1001 That may be my fault, the dashboard was working a bit ago, but there have been some underlying build changes I might of forgotten to check/test that functionality! Thanks for letting me know I'll look into it right now.
As for Launching, yes IIS. So basically it's bare-bones MVC as Ema was saying. This allows us to serialize the Angular application on the server, since we're able to invoke a Node process inside of .NET Core (universal is written in Node), giving you an almost instant application paint. You can test it by "disabling JavaScript" in Chrome settings and refreshing. That's all server rendered.
Let me get back to you about the dashboard!

@EmaGht @MarkPieszak Thanks folks! Makes sense!

We're all set, you can see the updates in commit https://github.com/MarkPieszak/aspnetcore-angular2-universal/commit/a81495821c37b5451485a02a00d46ffac0f2a94a or can get latest to see that it works now :)

Had to temporarily shut off the dashboard to fix the npm install from hanging, so i'll re-open this until I can get them both to play well together.
Related dashboard issue:
https://github.com/FormidableLabs/webpack-dashboard/issues/96

This has been removed for now, I might look into re-adding the dashboard in the future.
For now it caused so much headache before I'm afraid to even try again :cry:
We'll see though, trying to knock out the bigger fish at the moment!


Responsive design is rendering menu items inaccessible

What happened?
When using the dartpad in half- or quarter-screen the menu items "format" and "new pad" are no longer accessible
Steps to reproduce problem
Steps to reproduce:

Now resize the window:

Additional info
Browser
Browser: Safari
Version: Catalina
Are you using any extensions/plugins that affect website behavior
(particularly those that affect iframes, such as ad blockers)?
No
Are there any warnings or errors in your browser's JavaScript console?
If so, paste them below:
-

Machine
Operating system: OSX Catalina
Version: 10.15.3
Your code
What code was in the editor, if any, when the failure occurred? You
can paste it in below:
See screenshot

DartPad's output
Did DartPad print anything to the console pane? If so, paste it below:
-

Thanks for filing this, and for including so much detail!

Thanks for filing an issue - it sounds like we should add these to the dropdown menu instead of just hiding them.

As mentioned above, thanks for the report and the details!
The DartPad frontend has been rewritten and as a result this menu has a different behavior, so I'll close this issue as stale. However, the new UI has been written to be a bit more responsive and seems to keep relevant items accessible.
Please open a new issue with reproduction details if you're experiencing inacessible items with the current UI. Thanks again :)


fix: infinite AccountDropdown toggle

Description

Notice

[ ] Have you followed the guidelines in our Contributing guide?
[ ] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[ ] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)

closes #
Risk

Testing

Engineering

Operations

Screenshots (if applicable)

Current dependencies on/for this PR:

develop

PR #3115

PR #3116   👈

This comment was auto-generated by Graphite.


Custom Image and Documents Models should use Django Swappable Models

Is your proposal related to a problem?
Wagtail currently provides support for Custom Image and Document models as described in Custom image model and Custom document model. However, it does not use the swappable model feature of Django (available since version 1.5); see
Fixed #3011 -- Added swappable auth.User models.
This means that when a custom model is used, the table for the default model is still created; this causes conflicts if both models have the same name i.e. wagtailimages.image and media.image see #5119, It can also hide errors such as some model directly referring to wagtailimages.image if swappable models as used this will cause a migration error as the table doesn't exist, alerting the developer to the bad reference rather than just referring to an empty table and causing runtime bugs.
Also, See #5789
Describe the solution you'd like
Make wagtailimages.image, wagtailimages.rendition and wagtaildocs.document swappable models like auth.user form django.contrib.auth see
Fixed #3011 -- Added swappable auth.User models for how auth.user was done plus added the test for testing the feature.
I believe this just requires adding  swappable = "{custom_model_setting}" to the meta class for each model, and everything should just work as you have already implemented the custom model dependency in Wagtail; this should just cause the Django ORM to substitute the new model in the database. But I could be missing something as I've only skimmed through your implementation to work out why I had a naming conflict occurring for my custom model.
Describe alternatives you've considered
The only alternative is to use illogical names for custom models to avoid conflicts; this still dosen't address the possibly of silent reference error due to the default table still existing.
Additional context
Related Issues (mentioned above):

#5119
#5789

Thanks for the really clearly laid out issue @glenfletcher

Thanks for the suggestion @glenfletcher! I'm a little wary that making changes to swappable models on an already-running project is notoriously difficult in Django, and doing this within the Wagtail codebase might be the equivalent of forcing that kind of change on all existing Wagtail users - and from our side we have very limited control over details like the execution order of migrations, that would assist in smoothing that process. At the very least, making a change like this would need a lot of careful testing.

@gasman What about forking the documents and images app currently wagtail.documents and wagtail.images to say wagtail.swapable.documents and wagtail.swapable.images and then either checking which app is in the loaded apps or using a flag in settings to determine which app is being used by the site. That way, the settings file would require an active change to use the new behaviour.  So existing users wouldn't be forced to change. Once the new model is considered stable, you could then mark the old model as deprecated. So existing users could migrate to the new model on their own schedule.
As for using the correct app, would it be possible to make an import wrapper, say wagtail.autodetect.X, so when something is imported from wagtail.autodetect.X, it would check which version the site is using then import all names from there.
i.e. for wagtail/autodetect/images/models.py something like the following:
from wagtail.autodetect.images.detect import is_image_app_swappable()
if is_image_app_swappable():
    from wagtail.swappable.images.models import *
else:
    from wagtail.images.models import *

The problem would be if the import is used somewhere before Django has loaded sufficiently to answer which app should be used, something about which I have no idea.

Getting people to adopt a not-so intuitive module name like wagtail.swappable.images might be worse for the developer experience than just working around it with a different model name, I think.
Either way - I'm not ruling out the possibility of being able to add the swappable attribute to the existing app just yet - it just needs more testing.

See also - Swappable Site model https://github.com/wagtail/wagtail/issues/11440 & RFC for Swappable page model https://github.com/wagtail/rfcs/pull/53


Community Meeting February 15, 2022

At 11am Eastern, 8am Pacific, 3pm UTC; find your time
Video call link: https://meet.google.com/ohf-kwvd-mrp
Or dial: (US) +1<PHONE_NUMBER> PIN: 936<PHONE_NUMBER>#
More phone numbers: https://tel.meet/ohf-kwvd-mrp?pin=9361820877398
Or join via SIP<EMAIL_ADDRESS>Meeting recordings available on YouTube at https://www.youtube.com/channel/UCfP_yS5uYix0ppSbm2ltS5Q
This issue will collect prospective agenda topics. Add topics you'd like to discuss below!

General announcement:

Target March 18 for closing P3
Target March 7th to begin writing P3 script
Expect P4 to run to April 29th to get back to monthly cadence

Docs of the week:

https://docs.google.com/document/d/1N3AxSN-XmTVzFjJp_7OyPA2eHGvJyKY-ZfqkqjDzxho/edit# – Collection of Transparent Multi Cluster Challenges
https://docs.google.com/document/d/1SD2gVJk0FNPV9bsJucTwo9F1esNPa89_rmn5Roq7Ca4/edit#heading=h.d5ctd5ff38z9 – Exploration: workspace types and policy

Update kcp-dev/kubernetes default branch to feature-logical-clusters-1.23 (?)

Next: https://github.com/kcp-dev/kcp/issues/519

Recording: https://youtu.be/CUdGXF5V-vk


[AMPGW-520] - Improve  obscure values for numbers, unit tests

Took in consideration some of the comments, and added another small fix


Update Google MobileAds to use googleads-consent-sdk-ios 1.0.5 to remove UIWebView

googleads-consent-sdk-ios has been updated from 1.0.4 to 1.0.5 to remove UIWebView:
https://github.com/googleads/googleads-consent-sdk-ios/releases/tag/v1.0.5
https://github.com/googleads/googleads-consent-sdk-ios/commit/5cc10860a9e3edec73264c5fe8a77759b8d11148
https://github.com/googleads/googleads-consent-sdk-ios/issues/41
The Google MobileAds dependency now needs to be updated to this version to remove support for the deprecated UIWebView.

Hi @brianlenz! We are working right now on an update that fixes this.

Any updates here?

Hi @SotoiGhost ,
I am using Xamarin.Google.iOS.MobileAds NuGet and want to update it because of UIWebView. I am not sure the latest version 7.57.0 already removed this. It looks it is by seeing that this ticket is merged to #388 and closed. Additionally, it seems I have to update those Firebase libraries as well to get it work. It would be great if you can correct me if I'm wrong.
Thanks.

Hi @SotoiGhost ,
I am using Xamarin.Google.iOS.MobileAds NuGet and want to update it because of UIWebView. I am not sure the latest version 7.57.0 already removed this. It looks it is by seeing that this ticket is merged to #388 and closed. Additionally, it seems I have to update those Firebase libraries as well to make it work. It would be great if you can correct me if I'm wrong.
Thanks.

No luck with the 7057.0
There is still
`/// Presents the full screen consent form over viewController. The form is dismissed and
/// completionHandler is called after the user selects an option. Must be called on the main queue.

(void)presentFromViewController:(nonnull UIViewController *)viewController
dismissCompletion:(nullable PACDismissCompletion)completionHandler;`

in place in PACConsentForm.h file which clearly links to the deprecated UIWebView.

Version 7.66 resolved the issue for me


Add flag to disable process.exit()

I'm have some code that runs a few tests then calls process.exit(). Without process.exit the code never terminates in node on the command line which breaks my automated tests. However if I'm using devtool this means the windows closes before I can see the test results and I don't get to check what state it was in just before exiting. Right now I'm just inserting a debugger statement just before process.exit so it's not a big deal but a command line flag to prevent process.exit closing the window would be lovely.

The snippet below would work, too. But I agree that devtool should have this by default.
process.on('exit', function() {
  debugger;
});


Default to localhost

If running sdk-doctor diagnose, it'd be nice if it warned and assumed couchbase://localhost

The main reason I did not do this is that running diagnostic on the localhost cluster isn't very useful, since the majority of the testing is network related.

I agree, but some use cases like the Mac OS Sierra (where query fails to run and just crashes all the time) or Docker (where people forget to map ports) are localhost.  I'm okay if you don't want to do this, but I do kind of like the symmetry with the sdks of 'localhost by default if not specified'.
Up to you, close it if you decide not to.

Oh, Windows anniv. edition also has that "some services fail to run" thing.


Docked toolbar behavior with expansion functionality

I spot the new docked toolbar, which can certainly be preferable under some circumstances. :)
However it seems to me it doesn't behave consistently with older functionality if you want things expanded. Forcing dumps with ! or Kint::$expanded expands them within the toolbar, while toolbar itself stays collapsed on load.
It might make sense if toolbar could start expanded, whether implicitly from the expansion status of dumps within it or via explicit configuration ($expanded or dedicated setting).

Expanded is a per-dump setting. Unless you want the dock to be expanded even if only one of the 100 dumps you did is expanded, that's not going to work.
In the meantime, the version on master places dumps expanded with the ! modifier outside of the panel, in the page layout, as before. (And you can always disable the panel with RichRenderer::$folder)

Ok, I guess that's good enough. :) Thank you for reply.


Unable to import module 'image_handler/lambda_function'

When I am using https://s3.amazonaws.com/solutions-reference/serverless-image-handler/latest/serverless-image-handler.template
to resize my image size from 523×784 to 200x200, I got 133×200 image size instead of 200x200.
So, I try to configure thumbor.conf to customize my solution based on https://github.com/awslabs/serverless-image-handler/commit/f47c7c7c8a29e605921297a4bf301a24637f10b1  e.g.
MAX_WIDTH = 0
MAX_HEIGHT = 0

Just to try if it won't keep the image proportion etc.
Even though the CloudFormation deployment succeed, I see the following error when lambda function executes:
Error Log:
16:38:37
START RequestId: 330fa07d-4e79-49af-833c-ea4deacd47d3 Version: $LATEST
16:38:37
Unable to import module 'image_handler/lambda_function': No module named image_handler/lambda_function
16:38:37
END RequestId: 330fa07d-4e79-49af-833c-ea4deacd47d3
16:38:37
REPORT RequestId: 330fa07d-4e79-49af-833c-ea4deacd47d3	Duration: 0.51 ms	Billed Duration: 100 ms Memory Size: 1536 MB	Max Memory Used: 20 MB

Also, here is additional run info:
HTTP GET request URL:
https://xxx.cloudfront.net/fit-in/200x200/my_image.jpg
Unit Tests:
./run-unit-tests.sh

pytest source/image-handler
================================================== test session starts ==================================================
platform linux2 -- Python 2.7.15, pytest-3.5.0, py-1.7.0, pluggy-0.6.0
rootdir: /home/ec2-user/serverless-image-handler/source/image-handler, inifile:
collected 4 items

source/image-handler/tests/test_lambda_function.py ..                                                             [ 50%]
source/image-handler/tests/test_lambda_metrics.py .                                                               [ 75%]
source/image-handler/tests/test_lambda_rewrite.py .                                                               [100%]

=============================================== 4 passed in 0.80 seconds ================================================
All tests were successful
Clean up test material
remove virtualenv
/home/ec2-user/serverless-image-handler
Completed testing distribution

S3 Upload:
export TEMPLATE_OUTPUT_BUCKET=company-image-handler
export DIST_OUTPUT_BUCKET=company-image-handler
export VERSION=3.1.1

aws s3 cp ./dist/ s3://$DIST_OUTPUT_BUCKET-ap-southeast-1/serverless-image-handler/$VERSION/ --recursive --exclude "*" --include "*.zip"
aws s3 cp ./dist/serverless-image-handler.template s3://$TEMPLATE_OUTPUT_BUCKET/serverless-image-handler/$VERSION/

CloudFormation Stack deploy:
S3 template URL: https://s3-ap-southeast-1.amazonaws.com/company-image-handler/serverless-image-handler/3.1.1/serverless-image-handler.template

Origin S3 Bucket: company-website-bucket
Origin S3 Bucket Region: ap-southeast-1
Deploy UI: No

System info:
NAME="Amazon Linux AMI"
VERSION="2018.03"
ID="amzn"
ID_LIKE="rhel fedora"
VERSION_ID="2018.03"
PRETTY_NAME="Amazon Linux AMI 2018.03"
ANSI_COLOR="0;33"
CPE_NAME="cpe:/o:amazon:linux:2018.03:ga"
HOME_URL="http://aws.amazon.com/amazon-linux-ami/"
AMI: Amazon ECS-Optimized Amazon Linux AMI 2018.03.j

python --version
Python 2.7.15

So, I'm wondering why it raises error despite it follows the bucket configuration convention in README.
Any idea for what am I missing or went wrong?

Hi @zdk. Looking into this issue.

bump, also having this problem!

Resolved with v4.0.0


PostgresDsn doesn't accept valid socket for host host

Checks

[x ] I added a descriptive title to this issue
[ x] I have searched (google, github) for similar issues and couldn't find anything
[ x] I have read and followed the docs and still think this is a bug

Bug
It is valid to give a unix socket file as a host when connecting to Postgres (e.g. via sqlalchemy) but PostgresDsn throws a 'URL host invalid' error.
from pydantic import BaseSettings, PostgresDsn

class PGSettings(BaseSettings):
    dsn: PostgresDsn = 'postgresql://derp@/databasename?host=/var/run/postgresql'

Output of python -c "import pydantic.utils; print(pydantic.utils.version_info())":
pydantic version: 1.9.0
            pydantic compiled: True
                 install path: /opt/conda/envs/geneap-1/lib/python3.9/site-packages/pydantic
               python version: 3.9.9 | packaged by conda-forge | (main, Dec 20 2021, 02:41:03)  [GCC 9.4.0]
                     platform: Linux-5.11.0-36-generic-x86_64-with-glibc2.31
     optional deps. installed: ['dotenv', 'typing-extensions']

P.S. Valid format of postgres connection string:
postgresql://[user[:password]@][netloc][:port][/dbname][?param1=value1&...]
References
https://stackoverflow.com/questions/27037990/connecting-to-postgres-via-database-url-and-unix-socket-in-rails
https://www.postgresql.org/docs/current/libpq-connect.html
Browsing the code I see that PostgresDsn subclasses AnyUrl, I think it's quite possible to construct a valid Postgres connection string that is not a valid URL.

I've encountered the same thing a few days ago.
It seems like this issue has been around for a while, see #960

Ran into this due to google cloud. Seems like https://github.com/samuelcolvin/pydantic/issues/960 was closed
Do you think the community would be open to a PR to support a new PostgresDsn -- e.g. GoogleCloudPostgresDsn

Yup - just ran into this on https://github.com/danizen/fastapi-bakeoff

My guess would be that this is fixed in v2 she therefore main, PR welcome to add a unit test to check.

My guess would be that this is fixed in v2 she therefore main, PR welcome to add a unit test to check.

I would have been happy to add a unit test but unfortunately such a DNS still isn't considered valid.
dsn
  Input should be a valid URL, empty host [type=url_parsing<EMAIL_ADDRESS>input_type=str]

Thanks for investigating, looks like this needs to be fixed in pydantic-core, I've created https://github.com/pydantic/pydantic-core/issues/378.
PR welcome to fix that.

We’re no longer actively developing Pydantic V1 (although it will continue to receive security fixes for the next year or so), so we’re closing issues solely related to V1. If you really think this shouldn’t be closed, please comment or create a new issue 🚀.


Add Installer

An installer would be useful and possibly bypass the windows defender warning.

Agreed make it real easy for novices.
Installers are always more messy to make than you'd think, but I've done one before.
To get rid of the defender notice I think you need to build signed binaries in git or something, have to look into that.
Other than using proper installers I was thinking of a single exe installer that just downloads and places the files. Some users will probably struggle just extracting a ZIP.

Closing this, maybe one day, but no plans at all currently.


Add user's menu to the sidebar

Free template doesn't include the user menu in the sidebar.
Build user menu using the paid template component as reference.
Evaluate if it's worth it to implement Vue behavior as well.

Closed by #165


Disabled attribute in expansion panel not working

Bug, feature request, or proposal:
Bug
What is the expected behavior?
<md-expansion-panel [disabled]=true> should disable the panel and should not expand.
What is the current behavior?
Getting the below error .
Can't bind to 'disabled' since it isn't a known property of 'md-expansion-panel'.

If 'md-expansion-panel' is an Angular component and it has 'disabled' input, then verify that it is part of this module.
If 'md-expansion-panel' is a Web Component then add 'CUSTOM_ELEMENTS_SCHEMA' to the<EMAIL_ADDRESS>of this component to suppress this message.
To allow any property add 'NO_ERRORS_SCHEMA' to the<EMAIL_ADDRESS>of this component. ("

What are the steps to reproduce?
Providing a StackBlitz/Plunker (or similar) is the best way to get the team to see your issue.
Plunker starter (using on @master): https://goo.gl/DlHd6U
StackBlitz starter (using latest npm release): https://goo.gl/wwnhMV
What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
@angular/cli: 1.2.1
node: 7.7.3
os: win32 x64
@angular/animations: 4.2.6
@angular/cdk: 2.0.0-beta.8
@angular/common: 4.2.6
@angular/compiler: 4.2.6
@angular/core: 4.2.6
@angular/flex-layout: 2.0.0-rc.1
@angular/forms: 4.2.6
@angular/http: 4.2.6
@angular/material: 2.0.0-beta.8
@angular/platform-browser: 4.2.6
@angular/platform-browser-dynamic: 4.2.6
@angular/router: 4.2.6
@angular/cli: 1.2.1
@angular/compiler-cli: 4.2.6
@angular/language-service: 4.2.6
Is there anything else we should know?

This feature is only available from beta.10. Update your @angular/material.


Release and build documentation

Hey @derrickstaten can you let me know what you think of this? Hoping this clears up how all this documentation, building, and release automation works.

This is awesome! Maybe we could go through the motions of cutting a release on my computer sometime (if we ever have ample time)

:+1:


Fix log messages

Tests are not fixed with modified log messages.

Yes because I want feedback for more better message.

Update test for EventRouter.

Test passed excluding unstable test. Re-run test.

Test are passed.

If no concern, I will merge it.


Best practice - sharing data between components

Hi Trey,
I'm just curious if there's a recommended way to share data between components.
As an example, say I have the following 2 components:
comments-container and comment.
comments-container is responsible for loading comments from the server and rendering them with the class comment on the page.
That's where the comment component comes in and handles any comment-specific interactions.
At the moment, for the comment component I'm defining the comments-container element as a prototype attribute.
i.e.
skate('comment', {
  type: skate.type.CLASSNAME,
  prototype: {
    commentsContainer: document.getElementsByClassName('comments-container').item(0)
  }
  ...
});

I know that's one way of sharing data - but is it a method that you'd recommend?
If there's a better/nicer way, please share.
Thanks,
Maikel

From what you've shown me, it seems like you want access to the container so that you can call methods on it. Either that or you want to get information from it on-demand from the comments themselves.
For the former, I would recommend emitting events from the children. When the event bubbles, the comment container can respond to it.
You can trigger native custom events by using the Element.prototype.dispatchEvent() and the CustomEvent constructor. Depending on your browser support requirements you'll have to polyfill the CustomEvent constructor and possibly the dispatchEvent() method (supported in IE9).
References:

dispatchEvent()
CustomEvent

For the latter situation, it depends on exactly what you want to do. Having to reach up to the parent generally means you need to decouple your code a bit more and possibly relocate responsibilities so that they can facilitate that decoupling.
 Parents control the children and if the children make assumptions about where they are, that will break if the parent decides that should change. The relationship here is cyclic and implicit.
Another caveat which exists because of the first is that functional programming dictates that information should flow in one direction. In the case of the DOM, parents should know about children but children should not know about their parents. This is why I had suggested bubbling events because that makes no assumption about parent heirarchy and the parent can respond to child events because they are supposed to know about children.
If you look at how the Shadow DOM style templating is designed, it allows the parent to choose where it's children should go, but never allow the child to decide where it should go on its own. How your components are designed should reflect this.
I hope this helps.

Yeah, makes sense.
I'm using RadioJS for all my events needs, it's a pubsub library and I do use events whenever I need get the parent to perform an action, or any part of the app for that matter.
But if you were to access some properties on the comments-container component from your comment component, would you achieve it by querying the DOM and reading that attribute or is there's another recommended way?
My throught process is coming from AngularJS and how you can define a service between directives/controllers/etc which allow for easy data-sharing.

Why not just use the built-in DOM events? The API has mostly stabilised across browsers since IE9 and you get bubbling for free. My biggest recommendation I can make to anyone using Skate or web components in general is: think native. It's been designed to work very well with existing APIs.

I actually used the CustomEvent class just this week for the first time, I was curious about it and had a quick peek.
For the current project, I'm under a bit of pressure, time-wise, and the RadioJS library was added in the beginning of the project.
I am, however, trying to use as much native as possible. My current project just happens to be the first project I build without jQuery or AngularJS. And I'm enjoying it a lot. So I'm heading into the more native direciton :)

Ok. Just know that RadioJS is not intended for event communication between DOM elements. You can still use it, but I strongly recommend using native events for communication between web components. RadioJS will only make that worse.

Oh right. I'll have a second look when I get a chance.
Thanks for your help :)


Adding the official jekyll-feed gem.

This PR is for #292. It adds the official jekyll-feed gem to generate the atom/rss feed and removes the included one. The gem uses /feed.xml by default so the setup is still the same, just put anything in _config.yml for rss and the icon shows up.

Awesome! We get to delete a file 💥✨
Thanks @fleeting!


1.1.2: Minor patch

Coverage remained the same at 82.767% when pulling 62d1d02a1694da44f0524f1cd21edbfb15edd8cd on dev into f9cada0c9916ca96ab5a7af52bd60189c1407b2a on master.


Issue #9 100 Seconds Max Duration

set max duration to 999 on CircleControl.cs
set max duration to 999 on SpiralControl.cs

Should be merged into branch "Version2.1.0" instead of master. PR will be reopened


Reorderable list

This has some buttons which can move around, but they keep the same Id.
It would have been nice if I could borrow self.data inside the callback immutably, as I first tried it:
https://github.com/tbelaire/crochet/blob/wishful-thinking/examples/travelling_button.rs#L30
I can see that self.data is already borrowed immutably, so I don't see why I cant borrow it immutably again.  It'd be nice to avoid this kinda ugly pattern if possible.
Anyways, this moving of rows around is something fairly reasonable for the gui to do.  It suffers from the same bug in #5, as swapping the data doesn't seem to trigger an update.
I know you were aiming for the Optimistic Merge pattern, but I don't actually trust my code to be idiomatic, and would rather have some code review if you don't mind.

Some thoughts.
First, it's a known limitation of the current tree mutation engine that it doesn't do reorders, only insert, delete, and update. I do plan to add this, as it is useful functionality. What happens on swap is that the first element is deleted, the second element is skipped, then another copy of the first element is inserted. That's fine for labels but otherwise you'd lose the widget state. As I say, fixable, but it does mean making the tree mutation protocol more complicated. It's kinda nice that there are 4 variants: insert, delete, update, skip. I have a design in mind with "detach" and "reattach" as 2 more variants, but am still refining it in my head.
You can fix the borrow pattern by doing let data = &self.data; before calling the list's run method, then referring to data rather than self.data. The reason it's complaining here is that the closure wants to borrow all of self, and there's a mutable borrow from self for its list_view field. I think this is standard Rust borrow checker being difficult and nothing to do with Crochet. Even though the use of closures for scopes in general is still a bit controversial (see #1), for a list view component, there kinda needs to be a closure for creating a list element. That said, the pattern you've come up with - not doing a lot of work inside the closure, but getting an "action" out of it, seems like a pretty general solution.
I'd be happy to merge what I have, but I'll let you decide whether to revise your PR based on this feedback.

Yeah I think I'd like to simplify it down to only one action being passed out.

Alright, fixed it up, thanks for the review.


Small fixes for tests

In 3a6e0a272 an assert was erroneously changed and the test was ignored.

Nice catch, thanks.


Enabling reward_wsl2_direct_mount in .reward.yml file slows down installation and every container operation

Tested this on WIndows 10 with WSL2 installed, Ubuntu 20.04:
I have uncommented the flag reward_wsl2_direct_mount in the ~/.rewardw.yml file to leverage WSL2, however after setting up a env and running reward bootstrap, the whole installation process takes about ~50m, vs ~4m of normal installation without direct mount.
Also after using reward shell and any command inside the container, even just bin/magento are super slow, as well as the site page load, while it works perfectly with a Mutagen installation.
Moreover when exiting from a container with exit it produce the following error:
/var/www/html$ exit
exit
Error: exit status 130
Usage:
  reward shell [command] [flags]

Flags:
      --container string   the container you want to get in (default "php-fpm")
  -h, --help               help for shell

Global Flags:
      --app-dir string       app home directory (default "C:\\Users\\micro\\.reward")
  -c, --config string        config file (default "C:\\Users\\micro\\.reward.yml")
      --debug                enable debug mode (same as --log-level=debug)
      --disable-colors       disable colors in output
      --docker-host string   docker host (default "npipe:////./pipe/docker_engine")
      --log-level string     logging level (options: trace, debug, info, warning, error) (default "info")
      --wsl2-direct-mount    use direct mount in WSL2 instead of syncing

INFO[2021-03-05T10:18:44Z] exit status 130

I am not sure why this happens, just noticed while testing multiple site installations

Hello @adexandros, thank you for opening the first issue! 🎂
Please make sure if you are using Reward with WSL2 then your working directory have to be inside your WSL2 partition.
Also, could you run the following command and send me its output?
DEBUG=true reward shell

@adexandros on your second question. If you exit reward's shell without explicitly defining the exit code the previous command's exit code will be passed.
Example:
If you call /bin/true, that commands exit code will 1. If you exit after running it, bash will pass this exit code as it's own and that will be caught by reward.
reward shell
www-data@m2-php-fpm:/var/www/html$ /bin/false
www-data@m2-php-fpm:/var/www/html$ echo $?
1
www-data@m2-php-fpm:/var/www/html$ /bin/false
www-data@m2-php-fpm:/var/www/html$ exit
exit
Error: exit status 1
Usage:
  reward shell [command] [flags]

Flags:
      --container string   the container you want to get in (default "php-fpm")
  -h, --help               help for shell

Global Flags:
      --app-dir string       app home directory (default "/Users/mixe3y/.reward")
  -c, --config string        config file (default "/Users/mixe3y/.reward.yml")
      --debug                enable debug mode (same as --log-level=debug)
      --disable-colors       disable colors in output
      --docker-host string   docker host (default "unix:///var/run/docker.sock")
      --log-level string     logging level (options: trace, debug, info, warning, error) (default "info")

INFO[2021-03-05T14:31:04+01:00] exit status 1

This behaviour is coming from the underlying architecture like docker compose or even bash as you can find in exit command's help.
www-data@m2-php-fpm:/var/www/html$ exit --help
exit: exit [n]
    Exit the shell.

    Exits the shell with a status of N.  If N is omitted, the exit status
    is that of the last command executed.

Hi @janosmiko , where do you want me to type that command exactly?
If I type in my powershell I am getting:
INFO[2021-03-05T10:18:44Z] exit status 130
PS C:\Projects\magento-test> DEBUG=true reward shell
DEBUG=true : The term 'DEBUG=true' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included,
verify that the path is correct and try again.
At line:1 char:1
+ DEBUG=true reward shell
+ ~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (DEBUG=true:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

Also what do you mean exactly with:

Please make sure if you are using Reward with WSL2 then your working directory have to be inside your WSL2 partition.
the path from inside my Ubuntu would be: /mnt/c/Users/micro ;  I cannot create a new project with reward directly inside since the reward command is not recognized by Ubuntu in this instance.

I am still new to WSL2 so it's very likely I am doing something wrong

Thanks for your reply, @adexandros !
The command with the DEBUG=true environment variable have to be run in you Ubuntu shell.
I'm not sure where you installed Reward but if its something like C:\bin, then append the following line to your .bashrc in Ubuntu:
export PATH=$PATH:/mnt/c/bin
And reload your bash (or just run this command: source ~/.bashrc).
With this you will be able to reach reward (as reward.exe) from your Ubuntu.

And lastly, if your Project is directly on your Windows drive (like C:\Users\micro\Project is), then it's not "compatible" with WSL2. (In this case it's just mounted to WSL2)
If you open an Ubuntu WSL2 terminal, that will be on a filesystem which is inside your Ubuntu Virtual Machine. And the folders under /mnt are the Windows partitions mounted back to your WSL2 System (so in this case Ubuntu mounts your Windows drives).
So to use WSL2, you will have to clone your project directly inside Ubuntu WSL2 terminal to for example /home/micro/Projects.
For more information about how WSL2 works you can see the first section here and I suggest to check the 2 links there:
https://rewardenv.readthedocs.io/en/latest/configuration/wsl2.html#wsl-and-wsl2-support

Hi @janosmiko , so I did the following:

Logged into my Ubuntu instance
added export PATH=$PATH:/mnt/c/bin to my ~/.bashrc
also added alias reward=reward.exe because otherwise I wouldn't be able to actually execute it
created in my linux instance a new folder in /home/micro/projects/wsltest
cd into directory
run reward env-init wsltest
run reward bootstrap

Getting this error now:
wsltest_elasticsearch_1 is up-to-date
Creating wsltest_php-fpm_1 ... error

ERROR: for wsltest_php-fpm_1  Cannot create container for service php-fpm: failed with: can't access specified distro mount service: stat /run/guest-services/distro-services/ubuntu-20.04.sock: no such file or directory

ERROR: for php-fpm  Cannot create container for service php-fpm: failed with: can't access specified distro mount service: stat /run/guest-services/distro-services/ubuntu-20.04.sock: no such file or directory
ERROR: Encountered errors while bringing up the project.
Error: exit status 1

Could you check if you enabled WSL2 Integration in Docker settings?
You can find a documentation about this here (see the "if you encounter the following error section"):
https://rewardenv.readthedocs.io/en/latest/configuration/wsl2.html
Related issue:
https://github.com/docker/for-win/issues/5096

I just noticed that that's one of the know issue in the documentation

@janosmiko so I had the WSL2 integration enabled already but I specifically needed to select my instance of Ubuntu even though was the only and default one;
That resolved the issue, installation completed in about ~4m, like the other initial tests I made, so all good here, thanks for the help; I'll keep experimenting

I'm glad to hear that!


Germany - May 8th 2020 - "Tag der Befreiung"

Berlin gets a one-time public holiday next year

DE-BE
May 8th 2020

See for reference: https://www.feiertage-deutschland.de/tag-der-befreiung/
localName: Tag der Befreiung
name: Liberation day ? (this is not official but this should be the right translation)

hello,
will this be reflected in the API ?
thx,

My daughter was born a few days ago, I hope the change still has a little time I will take care of it as soon as I have some air for it again.

congrats!!!
there is definitely no hurry.
take care :-)

The api is now updated


Fails to build cryptomator 1.4.0-beta1 and the continous releases

The build for anything beyond 1.3.0-rc1 fails with
Buildfile: /home/build.xml   [taskdef] Could not load definitions from resource com/sun/javafx/tools/ant/antlib.xml. It could not be found.
It would be nice to be able to build any version from source.

What build container did you use?

I'm using the cryptomator-dev-x64 (on bionic 18.04 if that matters).
Update the Dockerfile with
 CRYPTOMATOR_VERSION=1.4.0-beta1
Then
``
$docker build . -t testing
$ docker run --name testing testing
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
100   603    0   603    0     0    875      0 --:--:-- --:--:-- --:--:--  1213
100 10.8M  100 10.8M    0     0  2852k      0  0:00:03  0:00:03 --:--:-- 4106k
Buildfile: /home/build.xml
[taskdef] Could not load definitions from resource com/sun/javafx/tools/ant/antlib.xml. It could not be found.
BUILD FAILED
/home/build.xml:6: Problem: failed to create task or type javafx:com.sun.javafx.tools.ant:application
Cause: The name is undefined.
Action: Check the spelling.
Action: Check that any custom tasks/types have been declared.
Action: Check that any / declarations have taken place.
No types or tasks have been defined in this namespace yet
Total time: 0 seconds
``
Also using the "continuous" build gives the same error (substitute 1.4.0-beta1 with continuous).

1.4.0+ will no longer work on these containers, we're using appimages and do not intend to publish .deb or .rpm files.
But 1.3.0-rc1 until 1.3.5 should work just fine.


pass additional parameters of getInitialProps all the way down

Hey guys,
when using this package I stumbled upon the problem, that the next-apollo integration provides the apollo client object as second parameter to the getInitialProps call. But as the HOC for the NextApp does not pass these values along that information is lost.
Use case is, that I need the apollo client in the getInitialProps of my app to fetch the authentication state of the user.
Maybe this is also helpful for others around here.
If this is anti-pattern or something you shouldn't do - please explain me why and what are possible options to work around that. I'm still pretty new to the whole nextjs ecosystem.
Thanks!

First of all, we are not talking about "parameters" or "arguments", but rather a single argument which is an object.
Second, I wasn't aware that people were using this package with other next-x packages, cool!
Finally, this approach seems totally sensible. That said, I'd rather rename additionalContext to rest. If someone has a problem with that naming, we can call it otherKeys or something.

Apologies, I misread the PR. This is in regards to further arguments on getInitialProps. I have not seen this done before, and I wonder why next-apollo is doing this instead of passing it through the object.
I'll need to look into this a bit further.

Okay, after looking around it seems like NextJs is committed to handling all their internals via the first-arg object.
Using rest params here should be fine, and certainly isn't an anti-pattern, but could break if the NextJs API changes.

@fgreinus Did you test this approach and ensure it works with next-apollo?

Thanks for your input! Actually I was able to get it working using the with-apollo-auth example from the next.js repo.
This is because in there the apollo client is manually set in the context object (ctx) and then passed along.
See: https://github.com/zeit/next.js/blob/canary/examples/with-apollo-auth/lib/withApollo.js
This methods has no need for any change on next-i18next and seems to be working fine for me now. Your questions/thoughs made me try that approach, so thank you!
I'll close this here then.
Have a nice day and thanks for you work 👍 .

@fgreinus I'm also using i18next and apollo-client in a few of projects and I recently played with integrating them with next-i18next. The composition of HOCs seem to work and you can check-out my approach in this open-source code base here: https://gitlab.com/kachkaev/website-frontend.

@fgreinus Ah yeah, very nice. It definitely makes more sense (to me) to pass things through the object. Good to hear that it worked.

@fgreinus I'm also using i18next and apollo-client in a few of projects and I recently played with integrating them with next-i18next. The composition of HOCs seem to work and you can check-out my approach in this open-source code base here: https://gitlab.com/kachkaev/website-frontend.

Thanks! That's pretty similar to what i'm currently doing, except that i'm passing the apollo client instance into the context object that's passed to other getInitialProps calls, because i need it in _app.jsx's getInitialProps method.


setup.sh script does not handle white spaces in directory name

setup.sh script does not handle white spaces in directory name

Lowering the priority of this issue and changing to requested enhancement as the viable workaround is not to use white spaces in directories and file names.

hey @faberga, i just pulled a request regarding the issue. Pls review the code and suggest better modifications.


Handle id attributes required

id field in attributes cannot be null if exists

@ngtk please review

we've talked to go with this. but, actually, it is our company's preference. 😅
let me think again.

we've talked to go with this. but, actually, it is our company's preference. 😅

Definitely. How about add a option like id_always_required to handle this?

Definitely. How about add a option like id_always_required to handle this?

Looks good. or I can approve an option like always_required_fields(array of symbol).
I think either is fine. you can go with these ways.

@ngtk fixed.

you need to fix the spec too.

@ngtk Fixed again.


Fix ndarray.get() not honoring current stream when layout is not contiguous

This appears to be a very old bug that we managed to expose somehow 😄
When the layout is not contiguous, we call _internal_ascontiguousarray or _internal_asfortranarray, which calls the ufunc elementwise_copy, which then fetches the current stream before launching. However, if the stream is passed as an argument to .get(), it's not set as a current stream, thus not used by the ufunc.

/test mini

LGTM. Thanks for your PR!


scopedSlots as Function returns only first element from array: res[0]

Subject of the issue
We can't use code like this:
wrapper = mount(Tag, {
	scopedSlots: {
		myScoped() {
			return [

Click in this must return 0 in console
,

Click in this must return 1 in console

			]
		}
	}
})

Steps to reproduce
https://gitlab.com/vskrsl/vtu-issue-scopedslots-array
I try to describe more about use case in test file. And example in native vue (instead tsx) how i can solve this.
Expected behaviour
I expected that all slots will be rendered not only first.
Actual behaviour
Because we have check on string https://github.com/vuejs/vue-test-utils/blob/dev/packages/create-instance/create-scoped-slots.js#L126 we got only first element of scopedSlots array (res[0])
Possible Solution
Does we realy still need this check for return result ? If i delete this check and will always return return res all internal VTU test passed.

Hi!
Looks like these lines were added in a PR to close this issue a couple of years ago. Could you check if you find anything relevant in the discussion there? Otherwise I think it make sense to remove this check as long as no internal tests fail (we might be missing some, so it would be wise to check if the tests in the PR covered all cases).
Thanks!


Unable to run cron!

Hello @odeke-em!
Thank you for this lib "drive push" can be run as a cron job. I have a python script that uploads a folder to drive using the push command. And, I'm trying to run a cron job on it so this can happen every hour. I redirected the output of the cron to a log file and it said "Permission Denied", but when I run it under root it says "drive not found". Is there any way I can work around this? I saw that there was an earlier post about crons, but I didn't quite understand what was discussed there! I'm sorry if this question is silly, and repetitive, I'm a little new to this!

I've been using "sudo -u $user drive pull" to make the permissions work properly.

I tried that, it still says "sudo: drive: command not found"! I, now, understand that this is because the path for drive is not known to root. How do I set this?

Right, you need to specify the full path to drive.
My script looks like:
cd /usr/backup
sudo -u peter /home/peter/go/bin/drive pull

Hello @Deekshay, thanks for reporting this and welcome to drive!
Sorry for the late reply, was busy earlier.
So @pefoley2's solution will work, and thanks @pefoley2. This is why you weren't finding the path given that the root ~/.bashrc file never had the proper path to it.
However, it is important to properly set up your $GOPATH as specified here in the README https://github.com/odeke-em/drive#requirements
$ cat << ! >> ~/.bashrc
> export GOPATH=\$HOME/gopath
> export PATH=\$GOPATH:\$GOPATH/bin:\$PATH
> !
$ source ~/.bashrc # To reload the settings and get the newly set ones # Or open a fresh terminal

Please don't forget to reload your shell or open up a new terminal

Specifying the path worked! Thank you! Sorry for the delayed response, though.
I have one last question, how do I set the GOPATH for root user, because I did follow the steps on the README and I even added the path for GO in PATH, but it won't work! drive works if I access it as a regular user, though! What am I doing wrong?

Good to know, thanks again @pefoley2 for the full path suggestion.
As for setting the gopath for root? Depends, if you are using it exclusively as root, after setting the gopath, you can build drive and it should properly create the binary. I don't know if this is the best option to be honest, @pefoley2 might suffice better.

Thank you!


UPDATE MISTRALAI SDK AND AZURE SEARCH SDK TO LATEST STABLE

@Wendong-Fan @sophiamyang minor packaging update here on the MSFT side. Plz approve.

Looks good! Thank you! I've approved!

@pandora-s-git thx. please merge

My bad! Merging!


Implement a config-update CLI command

Description
As part of the work to implement the RFC for our revamped config handling (https://github.com/arkime/aws-aio/issues/80, https://github.com/arkime/aws-aio/issues/81), this task is the work to add a config-update command to update the capture/viewer node configuration, per the RFC.  The steps should look something like:
* Create `config-update` command to update the existing config with new changes
* Implement/test rollback behavior
* README update

Acceptance Criteria

config-update implemented; should synchronously update the configuration on the capture and viewer nodes
config-update should not touch the capture/viewer nodes unless there is new/different config or behavior
config-update should gracefully roll back if there is a bad configuration
README updated to explain how to update configuration using the new command

Acceptance criteria met; resolving.


Icons should be transpiled beforehand

Reproduce:

Run vue init webpack test
Add vue-octicon & an icon
Run npm run build
Watch UglifyJs fail

Workaround: Using this webpack configuration
    {
        test: /\.js$/,
        loader: 'babel-loader',
        include: [resolve('src'), resolve('test'), resolve('node_modules/vue-octicon')]
      },

Actually in a related project Vue-Awesome I already put this into readme. I'll update that for this project later. As for now you can refer to Vue-Awesome's readme and make similar updates.

From my point of view, transpiling these icons could be the better way.

ERROR in js/vendor.39228e8c3d000eeb2e39.js from UglifyJs
Unexpected token: name (warn) [./~/vue-octicon/util.js:3,0][js/vendor.39228e8c3d000eeb2e39.js:13682,4]

This the way I solved, by submodule/download this repo to src/components directory
import Octicon from<EMAIL_ADDRESS>import '@/components/vue-octicon/src/icons/device-desktop'
...


Precompiled module doesn't work

"Entropy bunny couldn't find that"

Hmm... maybe reload the module page (http://<IP_ADDRESS>:1471/#/Modules/dnsspoof)?
When you install it and run it without a reboot, it will give you "Entropy bunny couldn't find that".
Just reloading the page (or a reboot) should do the job.
If that won't fix it, you may want to tell me exactly what you did to get the file onto your pineapple?

Can I close this issue? Do you still have problems according to DNSspoof?


Fix broken comment in example in qmlstart.rst

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

Look good. Thank you!


Support additional root device hints

Using "name" isn't reliable on baremetal as device
name can swap from one deploy to anopther, causing
boot failures as the image gets written to the wronge
drive.
To use another root device hint in place of "name"
a deploy can set
export ROOT_DISK_NAME=
export ROOT_DISK_HCTL=0:0:0:0

Build FAILURE, see build http://<IP_ADDRESS>:8080/job/dev-tools/554/

needs a rebase now, sorry

Build FAILURE, see build http://<IP_ADDRESS>:8080/job/dev-tools/595/

Build SUCCESS, see build http://<IP_ADDRESS>:8080/job/dev-tools/596/


Removing dir that exists in settings creates unhandled exception

If a directory that is listed in Diffusion Folders gets deleted, the next time the application starts it throws.

You can solve this by deleting the C:\Users\Utilzador\AppData\Roaming\DiffusionToolkit\diffusion-toolkit.db file
Then edit the config.json in the same folder and remove the line that references the 'Desktop\test' folder.
It should be fine after that.

Thanks for logging. Makes sense. I'll put this as a low-priority

You can solve this by deleting the C:\Users\Utilzador\AppData\Roaming\DiffusionToolkit\diffusion-toolkit.db file
Then edit the config.json in the same folder and remove the line that references the 'Desktop\test' folder.
Then just use the rebuild images button in the ui, It should be fine after that.

... or just recreate the directory, start app and remove it from settings.


service account token missing in pod

Pods using in-cluster authentication are failing because /run/secrets/kubernetes.io/serviceaccount/token is missing from their file system. I am using this KIP provider version:
    Image:         elotl/kip:latest
    Image ID:      docker-pullable://elotl/kip@sha256:8182c30c9751290ce319eaa27f82109bd907c5f265095c37d0520b82bd7fa510

on a AWS cluster recently created using KIP's terraform script.
One way to reproduce this problem is to start a simple ubuntu pod that runs an infinite loop:
kubectl run xenial --image=ubuntu:xenial --command -- bash -c 'while true; do echo `date`; sleep 5; done'

Then, this command shows the contents of /run/secrets/kubernetes.io/serviceaccount/:
kubectl exec xenial -- bash -c "ls -l /run/secrets/kubernetes.io/serviceaccount/"

The output shows that the token file is missing:
total 4
-rw-r--r-- 1 root root 1066 Sep 14 04:00 ca.crt

This command shows that the serviceaccount directory appears correctly mounted. It's just that its contents are missing the token file:
$ kubectl describe pod xenial

Namespace:    default
Priority:     0
Node:         kip-provider-0/<IP_ADDRESS>
Start Time:   Mon, 13 Sep 2021 20:59:18 -0700
Labels:       run=xenial
Annotations:  <none>
Status:       Running
IP:           <IP_ADDRESS>
IPs:
  IP:  <IP_ADDRESS>
Containers:
  xenial:
    Container ID:
    Image:         ubuntu:xenial
    Image ID:      ubuntu:xenial
    Port:          <none>
    Host Port:     <none>
    Command:
      bash
      -c
      while true; do echo `date`; sleep 5; done
    State:          Running
      Started:      Mon, 01 Jan 0001 00:00:00 +0000
    Ready:          True
    Restart Count:  0
    Environment:    <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-lb7j8 (ro)


Setup dependabot to update dependencies

We should setup dependabot to update dependencies in this repository, we should update dependencies daily. Documentation on setting up dependabot can be found here https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates#example-dependabotyml-file

I can work on this.

@engineerakki That's awesome, this is all yours. Please let us know if you have any questions as you explore. You can also ask questions on the contributors discord https://discord.gg/RAbjRr3kds

Closed by https://github.com/build-trust/ockam-website/pull/860. Thanks @engineerakki