text:
Add keyword methods and/or keyword method arguments to match Appium python-client

The Appium python-client, used by robotframework-appiumlibrary, has a much richer set of functionality that it supports that is not exposed by the robotframework-appiumlibrary. I need some of this richer functionality, in particular at the moment a "double-tap" capability, and I propose to make these enhancements in my fork of robotframework-appiumlibrary and then generate pull requests.
The Appium python-client's tap method signature is:
def tap(self, element=None, x=None, y=None, count=1):
Would you prefer me to expand the arguments of robotframework-appiumlibrary's tap method to match that of the Appium python-client, or would you prefer me to create new keyword methods such as:

double_tap(self, element=None)
tap_element_at_point(self, element=None, x=0, y=0)
double_tap_element_at_point(self, element=None, x=0, y=0)

My thought is that the first approach would be simpler, and more true to the Appium python-client interface, but you may have your reasons for wanting robotframework-appiumlibrary to support a different set of keywords. It seems that is the case in the current keyword set.
Please let me know your thoughts on this as soon as possible, since I'd like to begin work on these enhancements immediately.
Thanks,
C. Martin Taylor
Sr. Test Automation Specialist
Texas Instruments, Inc.

In a general sense, robotframework methods is better to cover one action. Thats is to say limited if cases. I belive seperating, click to a coordinate and tap to an element can be separated.
BR,

I’m not quite sure if I’m understanding your response. Here’s PRECISELY what I’ve implemented and am testing:

 Change the arguments of the “tap” keyword method to match those of the identically named “tap” method in the underlying appium/python-client library:

def tap(self, locator, x=None, y=None, count=1):

 Change the “click_element_at_coordinates” keyword method (that didn’t do what it said at all before) to be implemented in terms of the modified “tap” method:

def click_element_at_coordinates(self, locator, x, y):
""" Click element at the given x, y offset """
self._info("Clicking at (%s, %s)." % (x, y))
self.tap(locator, x, y)

 Add a new “double_tap” KW method, simply for clarity of expression, with the following signature, implemented in terms of the modified “tap” method:

def double_tap(self, locator, x=None, y=None)

I believe that this approach provides a combination of the full richness of the underlying APIs for those who need it and the clarity of specific purpose-named keywords for those who want simpler to read test cases.  I’m testing these changes now and will submit a pull request for them in the next few days.
Thanks,
Martin
From: Serhat Bolsu [mailto:notifications@github.com]
Sent: Wednesday, February 10, 2016 5:29 AM
To: jollychang/robotframework-appiumlibrary
Cc: Taylor, Martin
Subject: Re: [robotframework-appiumlibrary] Add keyword methods and/or keyword method arguments to match Appium python-client (#90)
In a general sense, robotframework methods is better to cover one action. Thats is to say limited if cases. I belive seperating, click to a coordinate and tap to an element can be separated.
BR,
—
Reply to this email directly or view it on GitHubhttps://github.com/jollychang/robotframework-appiumlibrary/issues/90#issuecomment-182324583.

I will try to explain with comments:

On 10 Feb 2016, at 15:35, C. Martin Taylor notifications@github.com wrote:
I’m not quite sure if I’m understanding your response. Here’s PRECISELY what I’ve implemented and am testing:

Change the arguments of the “tap” keyword method to match those of the identically named “tap” method in the underlying appium/python-client library:
def tap(self, locator, x=None, y=None, count=1):

If you provide functionality like this, localtor will be required all times. Instead if you device this method to two:
def tap(self, locator)
def tap at coordinates

Change the “click_element_at_coordinates” keyword method (that didn’t do what it said at all before) to be implemented in terms of the modified “tap” method:
def click_element_at_coordinates(self, locator, x, y):
""" Click element at the given x, y offset """
self._info("Clicking at (%s, %s)." % (x, y))
self.tap(locator, x, y)

There is no click_element_at_coordinates. However tap and click are not same in appium. Click generally goes with selenium back, but tap uses other underlying driver . So I would object to mix those.

Add a new “double_tap” KW method, simply for clarity of expression, with the following signature, implemented in terms of the modified “tap” method:
def double_tap(self, locator, x=None, y=None)

I believe that this approach provides a combination of the full richness of the underlying APIs for those who need it and the clarity of specific purpose-named keywords for those who want simpler to read test cases. I’m testing these changes now and will submit a pull request for them in the next few days.
Thanks,
Martin

Thank you,
Serhat

From: Serhat Bolsu [mailto:notifications@github.com]
Sent: Wednesday, February 10, 2016 5:29 AM
To: jollychang/robotframework-appiumlibrary
Cc: Taylor, Martin
Subject: Re: [robotframework-appiumlibrary] Add keyword methods and/or keyword method arguments to match Appium python-client (#90)
In a general sense, robotframework methods is better to cover one action. Thats is to say limited if cases. I belive seperating, click to a coordinate and tap to an element can be separated.
BR,
—
Reply to this email directly or view it on GitHubhttps://github.com/jollychang/robotframework-appiumlibrary/issues/90#issuecomment-182324583.
—
Reply to this email directly or view it on GitHub https://github.com/jollychang/robotframework-appiumlibrary/issues/90#issuecomment-182378089.

Thanks for clarifying the difference between “tap” and “click”. I agree that they should be kept separate. More comments below:
From: Serhat Bolsu [mailto:notifications@github.com]
Sent: Wednesday, February 10, 2016 7:50 AM
To: jollychang/robotframework-appiumlibrary
Cc: Taylor, Martin
Subject: Re: [robotframework-appiumlibrary] Add keyword methods and/or keyword method arguments to match Appium python-client (#90)
I will try to explain with comments:

On 10 Feb 2016, at 15:35, C. Martin Taylor <notifications@github.commailto:notifications@github.com> wrote:
I’m not quite sure if I’m understanding your response. Here’s PRECISELY what I’ve implemented and am testing:

Change the arguments of the “tap” keyword method to match those of the identically named “tap” method in the underlying appium/python-client library:
def tap(self, locator, x=None, y=None, count=1):

If you provide functionality like this, localtor will be required all times. Instead if you device this method to two:
def tap(self, locator)
def tap at coordinates
CMT: The locator IS REQUIRED for tap at all times. The x,y offset is not required unless you need it. When you do use it, it is an offset from the upper left corner of the element identified by locator, rather than absolute screen coordinates. Therefore I don’t think a “tap at coordinates” method is necessary or appropriate. You already provide “click a point” KW method for clicking at an arbitrary coordinate on the screen.

Change the “click_element_at_coordinates” keyword method (that didn’t do what it said at all before) to be implemented in terms of the modified “tap” method:
def click_element_at_coordinates(self, locator, x, y):
""" Click element at the given x, y offset """
self._info("Clicking at (%s, %s)." % (x, y))
self.tap(locator, x, y)

There is no click_element_at_coordinates. However tap and click are not same in appium. Click generally goes with selenium back, but tap uses other underlying driver . So I would object to mix those.
CMT: Your library provided:
def click_element_at_coordinates(self, coordinate_X, coordinate_Y):
""" click element at a certain coordinate """
self._info("Pressing at (%s, %s)." % (coordinate_X, coordinate_Y))
driver = self._current_application()
action = TouchAction(driver)
action.press(x=coordinate_X, y=coordinate_Y).release().perform()
which doesn’t do what it says it does, since it never references an element. My re-implementation was an attempt to fix this, but I mixed the concepts of “click” and “tap”. I will attempt to re-implement this, with a “locator” argument for the element, in terms of “press” and “release”, rather than “tap”. Given this consistency with “click”, it should probably also have a “duration” argument like the “click a point” method.

Add a new “double_tap” KW method, simply for clarity of expression, with the following signature, implemented in terms of the modified “tap” method:
def double_tap(self, locator, x=None, y=None)

I believe that this approach provides a combination of the full richness of the underlying APIs for those who need it and the clarity of specific purpose-named keywords for those who want simpler to read test cases. I’m testing these changes now and will submit a pull request for them in the next few days.
Thanks,
Martin

Thank you,
Serhat

From: Serhat Bolsu [mailto:notifications@github.com]
Sent: Wednesday, February 10, 2016 5:29 AM
To: jollychang/robotframework-appiumlibrary
Cc: Taylor, Martin
Subject: Re: [robotframework-appiumlibrary] Add keyword methods and/or keyword method arguments to match Appium python-client (#90)
In a general sense, robotframework methods is better to cover one action. Thats is to say limited if cases. I belive seperating, click to a coordinate and tap to an element can be separated.
BR,
—
Reply to this email directly or view it on GitHubhttps://github.com/jollychang/robotframework-appiumlibrary/issues/90#issuecomment-182324583.
—
Reply to this email directly or view it on GitHub https://github.com/jollychang/robotframework-appiumlibrary/issues/90#issuecomment-182378089.

—
Reply to this email directly or view it on GitHubhttps://github.com/jollychang/robotframework-appiumlibrary/issues/90#issuecomment-182384450.

I think this should be an appropriate re-implementation of “click_element_at_coordinates”, do you agree?
def click_element_at_coordinates(self, locator, x, y, duration=100):
    """
    Click the element identified by _locator_ at the given _x_, _y_ offset
    for a given _duration_ that defaults to 100 ms.
    """
    self._info("Clicking element at offset (%s, %s)." % (x, y))
    driver = self._current_application()
    el = self._element_find(locator, True, True)
    action = TouchAction(driver)
    try:
        action.press(el, x=float(x), y=float(y)).wait(float(duration)).release().perform()
    except:
        assert False, "Can't click element at offset (%s,%s)" % (x,y)

Thanks,
Martin
From: Taylor, Martin
Sent: Wednesday, February 10, 2016 8:24 AM
To: 'jollychang/robotframework-appiumlibrary'; jollychang/robotframework-appiumlibrary
Subject: RE: [robotframework-appiumlibrary] Add keyword methods and/or keyword method arguments to match Appium python-client (#90)
Thanks for clarifying the difference between “tap” and “click”. I agree that they should be kept separate. More comments below:
From: Serhat Bolsu [mailto:notifications@github.com]
Sent: Wednesday, February 10, 2016 7:50 AM
To: jollychang/robotframework-appiumlibrary
Cc: Taylor, Martin
Subject: Re: [robotframework-appiumlibrary] Add keyword methods and/or keyword method arguments to match Appium python-client (#90)
I will try to explain with comments:

On 10 Feb 2016, at 15:35, C. Martin Taylor <notifications@github.commailto:notifications@github.com> wrote:
I’m not quite sure if I’m understanding your response. Here’s PRECISELY what I’ve implemented and am testing:

Change the arguments of the “tap” keyword method to match those of the identically named “tap” method in the underlying appium/python-client library:
def tap(self, locator, x=None, y=None, count=1):

If you provide functionality like this, localtor will be required all times. Instead if you device this method to two:
def tap(self, locator)
def tap at coordinates
CMT: The locator IS REQUIRED for tap at all times. The x,y offset is not required unless you need it. When you do use it, it is an offset from the upper left corner of the element identified by locator, rather than absolute screen coordinates. Therefore I don’t think a “tap at coordinates” method is necessary or appropriate. You already provide “click a point” KW method for clicking at an arbitrary coordinate on the screen.

Change the “click_element_at_coordinates” keyword method (that didn’t do what it said at all before) to be implemented in terms of the modified “tap” method:
def click_element_at_coordinates(self, locator, x, y):
""" Click element at the given x, y offset """
self._info("Clicking at (%s, %s)." % (x, y))
self.tap(locator, x, y)

There is no click_element_at_coordinates. However tap and click are not same in appium. Click generally goes with selenium back, but tap uses other underlying driver . So I would object to mix those.
CMT: Your library provided:
def click_element_at_coordinates(self, coordinate_X, coordinate_Y):
""" click element at a certain coordinate """
self._info("Pressing at (%s, %s)." % (coordinate_X, coordinate_Y))
driver = self._current_application()
action = TouchAction(driver)
action.press(x=coordinate_X, y=coordinate_Y).release().perform()
which doesn’t do what it says it does, since it never references an element. My re-implementation was an attempt to fix this, but I mixed the concepts of “click” and “tap”. I will attempt to re-implement this, with a “locator” argument for the element, in terms of “press” and “release”, rather than “tap”. Given this consistency with “click”, it should probably also have a “duration” argument like the “click a point” method.

Add a new “double_tap” KW method, simply for clarity of expression, with the following signature, implemented in terms of the modified “tap” method:
def double_tap(self, locator, x=None, y=None)

I believe that this approach provides a combination of the full richness of the underlying APIs for those who need it and the clarity of specific purpose-named keywords for those who want simpler to read test cases. I’m testing these changes now and will submit a pull request for them in the next few days.
Thanks,
Martin

Thank you,
Serhat

From: Serhat Bolsu [mailto:notifications@github.com]
Sent: Wednesday, February 10, 2016 5:29 AM
To: jollychang/robotframework-appiumlibrary
Cc: Taylor, Martin
Subject: Re: [robotframework-appiumlibrary] Add keyword methods and/or keyword method arguments to match Appium python-client (#90)
In a general sense, robotframework methods is better to cover one action. Thats is to say limited if cases. I belive seperating, click to a coordinate and tap to an element can be separated.
BR,
—
Reply to this email directly or view it on GitHubhttps://github.com/jollychang/robotframework-appiumlibrary/issues/90#issuecomment-182324583.
—
Reply to this email directly or view it on GitHub https://github.com/jollychang/robotframework-appiumlibrary/issues/90#issuecomment-182378089.

—
Reply to this email directly or view it on GitHubhttps://github.com/jollychang/robotframework-appiumlibrary/issues/90#issuecomment-182384450.

At this point I should also note that I dont use click_element_at_coordinates as well.
This re-implementation of this method would be a nice addition. As you explained x, y are used for offset so why not this method is named click_element_with_offset. The name and in line comments would be misleading user as it will press the element on coordinates.

Closing because no activity

authors: CMTaylor serhatbolsu

repo: jollychang/robotframework-appiumlibrary


text:
Sticker Set

Sticker Set für GBoard erstellen

Weißer Rand um alle Symbole beim Export erstellen um die Sichtbarkeit auf dunklem Hintergrund sicherzustellen, alternative Ideen sind willkommen.

GBoard Sticker über Firebase AppIndexing gibt es nicht mehr??

source: gharchive/issue

repo: jonas-koeritz/Taktische-Zeichen

license_type: permissive

license_source: github-api


text:
🛑 Alpine-mirror is down

In 1e74c80, Alpine-mirror (https://alpine.jonasled.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Alpine-mirror is back up in 838b3a3.

repo: jonasled/status

license: MIT


text:
Update Android compression library

This PR updates the library used for video compression on Android.
Looks like that library had no breaking changes, but some fixes: https://natario1.github.io/Transcoder/about/changelog
Updated changelog to mention this update.
I believe that this PR should be merged after #153
As soon as #153 is merged I will update this PR to resolve conflicts.

Thanks for your contribution!

source: gharchive/pull-request

authors: jonataslaw vbuberen

repo: jonataslaw/VideoCompress


text:
Can't show snackbar (Get.snackbar) on store (GetxController ) init

When i trying to show snackbar on store init, it throws exceprion
My code:
class AppStore extends GetxController {
  AppStore() {
    Get.snackbar('a', 'b');
  }
}

Exception:
_E/flutter ( 6692): [ERROR:flutter/lib/ui/ui_dart_state.cc(198)] Unhandled Exception: Null check operator used on a null value
E/flutter ( 6692): #0      SnackbarController._configureOverlay (package:get/get_navigation/src/snackbar/snackbar_controller.dart:91:50)
E/flutter ( 6692): #1      SnackbarController._show (package:get/get_navigation/src/snackbar/snackbar_controller.dart:331:5)
E/flutter ( 6692): #2      GetQueue._check (package:get/get_utils/src/queue/get_queue.dart:42:47)
E/flutter ( 6692): #3      GetQueue.add (package:get/get_utils/src/queue/get_queue.dart:29:5)
E/flutter ( 6692): #4      _SnackBarQueue.addJob (package:get/get_navigation/src/snackbar/snackbar_controller.dart:357:31)
E/flutter ( 6692): #5      SnackbarController.show (package:get/get_navigation/src/snackbar/snackbar_controller.dart:63:27)
E/flutter ( 6692): #6      ExtensionSnackbar.snackbar (package:get/get_navigation/src/extension_navigation.dart:465:18)
E/flutter ( 6692): #7      new AppStore (package:my_app/stores/app_store.dart:20:9)
E/flutter ( 6692): #8      new App (package:my_app/main.dart:42:28)
E/flutter ( 6692): #9      main (package:my_app/main.dart:37:10)
E/flutter ( 6692):

onReady(){
Get.snackbar('a', 'b');
}

Thanks!

authors: Altereyo jonataslaw

repo: jonataslaw/getx


text:
Remove Deref implementation and other refactorings

Deref no longer makes sense for LineBuffer since it can have multiple lines.

Looks good

authors: jasonrhansen jonathandturner

repo: jonathandturner/reedline


text:
Name variable should be PascalCase

Hello, I noticed that, when you pass an already camel case name, the variable Name  loses its casing.
So for example:
create component newComponent

Will create Newcomponent instead of NewComponent as expected.
It will be as easy as just uppercasing the first letter instead of formatting the entire word. Or maybe just use PascalCase instead of whatever you are using right now.
Regards

Thanks, should be good now

repo: jondot/hygen


text:
Allow re-raise configured exceptions to worker

If we need process some exceptions inside worker
before
rescue StandardError, ScriptError => ex

Please handle exceptions in your own code. Sneakers handles exceptions as a last resort. RabbitMQ consumers are generally expected to deal with their own exceptions.
@Tensho OK with you if I close this?

@michaelklishin  Sure, totally agree with your point.

@Curter29 I would like to understand why you would want to have any of StandardError or ScriptError bubble up to your app?
Also, raising exceptions at this point in the code, would make it ambiguous what happens to messages that are fetched from Rabbit. I would say, that they should be handled regardless of any exceptions.

authors: Curter29 Tensho anderslemke michaelklishin

repo: jondot/sneakers

license: mit

license_source: bigquery


text:
🛑 NO - Norway is down

In f175857, NO - Norway (https://www.skyshowtime.com/no/help/) was down:

HTTP code: 404
Response time: 1263 ms

Resolved: NO - Norway is back up in 0f1b91a after 11 minutes.

repo: jonesyriffic/gsp-sst


text:
CentralViewController

How can I get central view controller from left or right menu controller?

Hi @YevhenHerasymenko. Side menus are displayed no differently than standard system calls, like using presentViewController. As such, there's no special coding needed to figure out the central view controller as you can use standard system methods. I'd suggest looking in to presentingViewController.

Thanks. presentingViewController works correctly.

authors: YevhenHerasymenko jonkykong

repo: jonkykong/SideMenu


text:
Cannot display is_mutual.

https://github.com/jonra1993/fastapi-alembic-sqlmodel-async/blob/bb8018cad75b0caf83ce248508f9d949d02bf643/fastapi-alembic-sqlmodel-async/app/api/v1/endpoints/user.py#L120
    query = (
        select(User，UserFollow.is_mutual) <- this line
        .join(UserFollow, User.id == UserFollow.user_id)
        .where(UserFollow.target_user_id == current_user.id)
    )

how to display is_mutual info in this query? I tried many methods, but none of them could be realized.

Hello, @dongfengweixiao mmm looks weird I am going to check it in these days.

Hello, @dongfengweixiao thanks for this insight I am going to check it also.

I see @dongfengweixiao solved this bug extracting User columns as independent fields here https://github.com/jonra1993/fastapi-alembic-sqlmodel-async/pull/26


text:
Revamp

This pull request fixes many long date issues with the SlideOverCard package, including:
✨ Now, the .slideOverCard(:_) modifier uses the SOCManager by default for presentation, meaning it can now present a card over the entire view hierarchy from any child view. To keep this package streamlined, the SOCManager class and the SlideOverCard view have been made private as they're no longer needed. Deprecated structs and initializers have also been removed.
🛠 The presentation behavior in the SOCManager has also been improved substantially — now you can present cards over sheets, tab views and much more. Also, all animation issues were fixed.
👆Now, cards can be dismissed by an outside tap. To disable this behavior, just include .disableTapToDismiss in your SOCOptions.
📱 The default corner radius of the cards is now automatically calculated by the device's bezels' corner radius and the outerPadding parameter.
📁 The project's file structure has been revamped, and the README has been adjusted and streamlined.
🎆 There's also a new, shinier icon!

This pull request resolves #6, resolves #10, resolves #13, resolves #17, resolves #18, resolves #19 and resolves #23.

🥳

🥳

better late than never haha

repo: joogps/SlideOverCard


text:
Activate CodeQL in repo

For security scanning

Done

repo: joolfe/postman-to-openapi


text:
gradle init

I tried to compile with gradle:

Gradle 2.10
Groovy:       2.4.5
Ant:          Apache Ant(TM) version 1.9.6 compiled on July 20 2018
JVM:          1.8.0_191 (Oracle Corporation 25.191-b12)
OS:           Linux 4.4.0-145-generic amd64
I got:
Caused by: org.codehaus.plexus.util.dag.CycleDetectedException: Edge between 'Vertex{label='org.apache.maven.plugin.MavenPluginManager:default'}' and 'Vertex{label='org.apache.maven.plugin.version.PluginVersionResolver:default'}' introduces to cycle in the graph org.apache.maven.plugin.version.PluginVersionResolver:default --> org.apache.maven.plugin.MavenPluginManager:default --> org.apache.maven.plugin.version.PluginVersionResolver:default
at org.codehaus.plexus.util.dag.DAG.addEdge(DAG.java:143)
at org.codehaus.plexus.util.dag.DAG.addEdge(DAG.java:123)
at org.codehaus.plexus.component.composition.DefaultCompositionResolver.addComponentDescriptor(DefaultCompositionResolver.java:60)
... 79 more
any idea?
Thank You

closing as this is now rather old and potentially not relevant any more


text:
Tone Analyzer usage is old

It appears that in the two years since this was maintained the Watson API has been updated.
It appears that Watson API only expects a secret key, not a username and password.

Can you please create a branch for this fix?

@Matthew-Zorumski Is this fixed? Or was the issue invalid? Please update here.

This was invalidated when it was discovered that the username is now universally APIKEY and the password is the apikey you retrieve from IBM.

Can you please update the documentation for tone analyzer?

documentation updated in #11

authors: Matthew-Zorumski jorymorrison

repo: jorymorrison/MLD


text:
api无法粘贴进去

Describe the bug
问题描述
A clear and concise description of what the bug is.
To Reproduce
如何复现
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
期望行为
A clear and concise description of what you expected to happen.
Screenshots
截图说明
If applicable, add screenshots to help explain your problem.
Please complete the following information):
请补全以下内容

OS: [e.g. Windows]
Browser: [e.g. chrome, safari]
Extension Version: [e.g. v2.0.2]

Additional context
其他
Add any other context about the problem here.

没懂什么意思, 录个屏?

最开始就是，往插件里面粘贴api key没反应，试了好一次都不行，然后浏览器重启又可以了

------------------ 原始邮件 ------------------
发件人:                                                                                "josStorer/chatGPTBox"                                                                                @.>;
发送时间: 2023年4月3日(星期一) 晚上11:24
@.>;
@.@.>;
主题: Re: [josStorer/chatGPTBox] api无法粘贴进去 (Issue #143)
没懂什么意思, 录个屏?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

ok, 解决就好

repo: josStorer/chatGPTBox


text:
[FR] - Drop dingo?

@kslimani What do you think about dropping dingo for the following reasons:

Reduce 3rd party dependencies
Encourage API Evolution instead of API Versioning (https://blog.apisyouwonthate.com/api-evolution-for-rest-http-apis-b4296519e564)
Change Fractal in favor of native Resources (https://laravel.com/docs/5.6/eloquent-resources)

Also for the Spec change API Blueprint in favor of OpenAPI 3.0 spec.

@joselfonseca "API evolution" is the methodology i already use for my applications.
By dropping Dingo, you lose the "mime based" ressource versioning feature, but you can still use "URL based" ressource versioning. (so I am not against dropping Dingo dependency).
About replacing Fractal by Eloquent Resources : i have not yet myself tested this feature. It seems powerfull but i don't know how it handle the pagination for collection, especially the links in meta.
Do you know if it is automatically handled by Laravel or do you have to generate the url links yourself  ?
(if not, it may be required to create some helpers to reproduce the Dingo collection metadata)
About the OpenAPI spec i don't know, i think it may depends on the available tools to generate api documentation. (Aglio is pretty cool for API blueprint format).

I have read the pagination part for API resources, i was just wondering how the urls in "links" and "meta" are generated in the provided example :
// Copy paste from https://laravel.com/docs/5.6/eloquent-resources#pagination
use App\User;
use App\Http\Resources\UserCollection;

Route::get('/users', function () {
    return new UserCollection(User::paginate());
});

Yea, I was looking into that and got this:
[
  "data" => array:0 []
  "links" => array:4 [
    "first" => "http://localhost/api/users?page=1"
    "last" => "http://localhost/api/users?page=2"
    "prev" => null
    "next" => "http://localhost/api/users?page=2"
  ]
  "meta" => array:7 [
    "current_page" => 1
    "from" => 1
    "last_page" => 2
    "path" => "http://localhost/api/users"
    "per_page" => 20
    "to" => 20
    "total" => 31
  ]

Using
    /**
     * Returns the Users resource with the roles relation.
     *
     * @param Request $request
     * @return mixed
     */
    public function index(Request $request)
    {
        $paginator = $this->model->with('roles.permissions')->paginate($request->get('limit', config('app.pagination_limit')));
        if ($request->has('limit')) {
            $paginator->appends('limit', $request->get('limit'));
        }

        return UserResource::collection($paginator);
    }

data is empty because I removed it, but the user data is there. I am only worried about like the includes, have not seen how that works.

What happen if instead of /users you rename to something else ?
Route::get('/foobar', function () {
    return new UserCollection(User::paginate());
});

Does it properly generate links like http://localhost/api/foobar?page=1 ?

It actually does XD
  "links" => array:4 [
    "first" => "http://localhost/api/foo?page=1"
    "last" => "http://localhost/api/foo?page=2"
    "prev" => null
    "next" => "http://localhost/api/foo?page=2"
  ]
  "meta" => array:7 [
    "current_page" => 1
    "from" => 1
    "last_page" => 2
    "path" => "http://localhost/api/foo"
    "per_page" => 20
    "to" => 20
    "total" => 31
  ]

Route::group(['prefix' => 'foo'], function () {
        Route::get('/', 'Users\UsersController@index');

/**
     * Returns the Users resource with the roles relation.
     *
     * @param Request $request
     * @return mixed
     */
    public function index(Request $request)
    {
        $paginator = $this->model->with('roles.permissions')->paginate($request->get('limit', config('app.pagination_limit')));
        if ($request->has('limit')) {
            $paginator->appends('limit', $request->get('limit'));
        }

        return UserResource::collection($paginator);
    }

That's pretty cool !

Lets leave this for later XD.

authors: joselfonseca kslimani

repo: joselfonseca/laravel-api


text:
InvalidParameterException  when using plugin with fargate

We have an issue when running the plugin. We always get the exception "InvalidParameterException" although all parameters have been specified. The Task definition will be created by a cloud formation script and therefore must not be created by the plugin. However we still get the InvalidParameterException and we can not figure out how to fix it.
This is our config:
- name: dev:fargate:deploy
   image: pelotech/drone-ecs
   settings:
    region: us-east-1
    family: IndiAuthTaskDefinition
    docker_image: xxxx.dkr.ecr.us-east-1.amazonaws.com/xxxxx-backend
    tag: latest
    service: IndiauthService
    cluster: IndiauthCluster
    container_name: IndiauthContainerDefinition
    deployment_configuration: 50 200
    access_key:
        from_secret: DEV_AWS_ACCESS_KEY_ID
    secret_key:
      from_secret: DEV_AWS_SECRET_ACCESS_KEY

I faced similar issue with "InvalidParameterException" and it was not easy to trace down, in the end I found the error by looking through the API calls in AWS console (Cloudtrail). In my case it was due to service was setup with bridge network and I tried to deploy the task with awsvpc. Error was not in the plugin, but in the AWS end rejecting the config.

repo: josmo/drone-ecs


text:
store

The store directive, and possible other directives, should be reviewed for easier understanding of what's happening.  In particular,  store could have the option of  [name|value](# "store:| cmd1 | cmd2 |...") which would take value and pipe it into cmd1, cmd2, ...  and then store it under the name variable.
The pipe should be safe as a separator as varnames can't have pipes. This should be backwards compatible with the previous store commands.

done as of v1.9.0

repo: jostylr/literate-programming-lib


text:
Fixed jquery 3 promise handling to be compatible with ember promises

More info explained here, which has been found based on this ember issue

I'd rather us just drop replace this with ember-network like ember-simple-auth is doing now.

any update on this? causing me some headaches. getting race conditions in my acceptance tests. using a fork with this proposed fix for now.

@jeffhertzler we had some issues with the migration to ember-network. You could use a more updated version that is also patched on my fork if you want: https://github.com/morhook/ember-simple-auth-token/commits/fix_jquery_3_ember_2_10
Sorry for not having a better fix yet.

No problem. Yeah, your fork is what I'm using for now. Works great til there's a more permanent solution.

@morhook would you want to give this another try? Seems like the preferred alt is ember-fetch. https://github.com/simplabs/ember-simple-auth/pull/1288
If not, anyone else can step up or I'll give it a go in a couple of days.

Using ember-fetch seems like the right way to go, I can review a pull request for including ember-fetch.

@alechirsch https://github.com/jpadilla/ember-simple-auth-token/pull/200 although I'm not sure how to stub fetch, and fix the tests. Any guidance is appreciated.
Maybe something like http://www.wheresrhys.co.uk/fetch-mock/ ?

Closed by #226. Thanks again everyone!

authors: alechirsch jeffhertzler jpadilla knownasilya morhook pfmmfp

repo: jpadilla/ember-simple-auth-token


text:
fix preview problem in ADT

Changes:

Add "if( isInEditMode( ) ) return;" to prevent preview problem in new ADT;
Updated gradle feature: replace "runProguard false" by "minifyEnabled false".
Original preview problem sample happens when use "<com.jpardogo.android.googleprogressbar.library.GoogleProgressBar>" tag in layout XML:

Thanks!

authors: MewX jpardogo

repo: jpardogo/GoogleProgressBar


text:
Config File

There are starting to be a lot of options, which are hard to enter via cli, and annoying to maintain as both cli and .env file options. Refactor app to run off a json config file instead, which would have all available options inside it.

add an init command, like gg init which would generate the config file (ie. ggrc.json)
Running gg without config file will ask you to run gg init first
Drop support for env variables and force everything to be in the single config file. Leave --page support.

Can do this all using the yargs library that's already part of the code base. Would be extra cool though if gg init prompted you for credentials and stuff, using Inquirer.js.
This would be a HUGE breaking change and would have to be a major release.
Not sure if I'll have the time to go through with this, but wanted to write it down while I was thinking about it.

Does your gg init import information from the .env to populate the config file?   I could easily write a shell script to convert a .env into a config file since all the information is already there but that wouldn't work for the windows users.    I ask because I just built my config file manually copying info from my .env so don't know how it works.

Nope, it does not. I thought about it, but it seemed like way too much effort for me, so I put that effort on the user instead. :p But running gg init would have walked you step by step through entering the values for the config file. What you did wasn't much harder though.

authors: famewolf jpchip

repo: jpchip/giveaway-grabber


text:
charset problem

I use this module in the virtual machine to get garbled operating system information, but it is normal to use native wmi statements.

Query.js中280行标准输出流读取的data数据不能直接累加，添加以下处理：

Query.js中280行标准输出流读取的data数据不能直接累加，添加以下处理：

I forked this repository to fixed this problem and published a new npm package calledwmi-client-chinese

authors: liuyiseaduncom rwson

repo: jpgrusling/node-wmi


text:
Allow users to use custom build command

The ino tool is no longer under active development. There is a fork named Arturo maintained, but it uses ano as the command name. This change simply allows users to specify a custom command to run instead of assuming ino.

:+1:

authors: sinisterstuf stevearc

repo: jplaut/vim-arduino-ino


text:
🛑 The Rangoli Restaurant is down

In 0c31951, The Rangoli Restaurant (https://therangolirestaurant.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: The Rangoli Restaurant is back up in f846437 after 9 minutes.


text:
🛑 Tara Gems Galore is down

In b02cac7, Tara Gems Galore (https://taragemsgalorellc.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Tara Gems Galore is back up in 45858c5 after 42 minutes.


text:
More extensive documentation request and some user questions.

This seems an amazing library, but nowhere is clearly explained exactly how you are supposed to update the data in the table, how to access the underlying data structures, and much more.  As an example, I'm trying to display the table inside an ipywidget box, and I don't know if it's possible and which function should I use. A practical example of how to construct DataModel class would be very useful too.
Lastly I am  using get_state() and setData() to get the data from the table w and to change em, is there any easier way to get the data from the table if using pandas DataFrames like for example a w.to_dataframe() method?
EDIT: I see that using w.datamodel._data i can access the underlying dataframe, but if I change it the table widget doesn't update,is there a way to the refresh the view programmatically?

Best bet is to start with the examples:
https://github.com/jpmorganchase/ipyregulartable/tree/main/docs/examples
There is a relatively simple example of a data models here:
https://github.com/jpmorganchase/ipyregulartable/blob/main/ipyregulartable/datamodel/demo.py
The best way to force an update on the frontend is by calling draw on the widget (should happen automatically if the data model changes):
https://github.com/jpmorganchase/ipyregulartable/blob/main/ipyregulartable/widget.py#L110
I haven't written much documentation as the codebase is still pretty alpha, I have a major overhaul in progress in https://github.com/jpmorganchase/ipyregulartable/pull/59 to add some nice defaults like striping, cursor navigation of cells, column/row/both selection, sortable headers, etc. Once that overhaul is done I think the codebase will be in a much better and more stable place and then can have some more extensive docs written.

Thanks for the reply and amazing work! Is ipyregulartable compatible with ipywidgets boxes or will it be in the future?  I tried to capture it with a box and with an Output widget but had no luck.

authors: cmartinotti timkpaine

repo: jpmorganchase/ipyregulartable


text:
Improve Typography styles

Visual design feedback recommends improvements to the typography styles. This will create a simpler token structure and align the typography foundation more with similar design systems in order to improve the potential for theming.

Remove extrabold as a font weight
Change H1 weights to match other header styles
Add display-4
Update all display font sizes based on VD recommendations

This has been added to the Figma theme library as part of Salt 2.0 theme.

repo: jpmorganchase/salt-ds


text:
Woodcutters unable to cut birch and above

Describe the bug
Skeleton woodcutters are unable to cut trees, stumps and logs for birch and above.
I didn't have this issue with version 3.0.1(last time i used woodcutters recently).
Disabled creature level and loot control, changed necromancy skill to get 0 and 2 star woodcutters(i was on 39, had 1 star), still the same results. Looking at my mod list, i don't have any other mods that change either wood hardness, or tame stats/behaviour.
Config setting for tool quality doesn't seem to impact anything(was on 4-black metal before, no change with setting it to other)
To Reproduce (if applicable)

spawn woodcutter near birch or above hardness destroyable
observe skeletons attempt to cut wood

Expected behavior (if applicable)
Workers should be able to cut any tree, i did farm oak with them, can remember something about yggdrasil wood too, so technically they should be able to cut everything.
Screenshots (if applicable)

Desktop

OS: win 10
Mod version: 3.0.3
Game version 0.214.300

Hello, this should be fixed in 3.0.4. If it isn't, please reopen the isuse. Thanks again :)

license: Unlicense


text:
Submit not triggering?

Whenever a user tries to click the submit button, the validate does not trigger. Is there something I can be missing ?
var container = $('.email-form .errorContainer');
$('#email').validate({
    errorContainer: container,
    errorLabelContainer: $('ol', container),
    wrapper: 'li',
    rules: {
        emailTo: {
            email: false,
            required: true,
            maxcount: true,
            multiemail: true
        }
    },
    messages: {
        emailTo: {
            maxcount: 'You can only have up to 5 email addresses.',
            multiemail: 'Invalid email format: please use a comma to separate multiple email addresses.'
        }
    },
    highlight: function (element, errorClass, validClass) {
        $(element).addClass(errorClass);
        $(element).parent().addClass(errorClass);
    },
    unhighlight: function (element, errorClass, validClass) {
        $(element).removeClass(errorClass);
        $(element).parent().removeClass(errorClass);
    },
    submitHandler: function (form) {
        $('.errorContainer').html('');
        $('.successContainer').html('');
        $.ajax({
            type: $(form).method,
            url: $(form).action,
            data: $(form).serialize(),
        }).done(function () {
            $('.successContainer').addClass('is-active').html('Success!');
            $(form)[0].reset();
        }).fail(function () {
            $('.errorContainer').addClass('is-active').html('Failed!');
        });
    }
});

<form id="email" class="email-form" action="#" method="get">

Email

        <svg class="icon icon-error"><use xlink:href="#icon-error"></use></svg>

            There was a problem!

                    Please enter valid email address

                    Please enter valid email address

            To (Up to 5 Email Address, Comma Separated)

                <svg class="icon icon-error-2"><use xlink:href="#icon-error-2"></use></svg>
                <input id="emailTo" class="textfield" type="email" name="emailTo" required>

            Your Email Address

                <svg class="icon icon-error-2"><use xlink:href="#icon-error-2"></use></svg>
                <input id="emailFrom" class="textfield" type="email" name="emailFrom" required>

        <input class="submit" type="submit" value="Send">

</form>

Please provide a JSFiddle or JSBin containing a set of reproducible steps.

It was my fault ... I had a click event on the modal that intercepted the click event on the submit button. Sorry for the bother.

authors: Arkni kkashou

repo: jquery-validation/jquery-validation


text:
Integrate codecov.io

With Codecov.io integration, there can be two benefits:

Coverage information is prominent in every pull request
Code coverage dashboard is available for more detailed information

Any possible coverage regression can be easily tracked.

We recently integrated Coveralls (#1066). However, I'm quite disappointed that it's been quite flaky, see pull request #1213 and also previously #1211. Hence the reason to explore an alternative such as codecov.io.

And again :-( https://travis-ci.org/jquery/esprima/jobs/68963663

Coveralls misbehaves again: https://travis-ci.org/jquery/esprima/jobs/70170819.

repo: jquery/esprima


text:
Fixes issue #33

Now Jobs that don't have any arguments, and are submitted from a
Dagman, will be included in the dag submit file!

See issue #33

repo: jrbourbeau/pycondor


text:
[docs] Update Jbang instructions

Removed "Required Java 8" from the Jbang instructions as this not really necessary given the fact Jbang can install Java when needed.

 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.

Thanks! 😄

authors: CLAassistant aalmiray quintesse

repo: jreleaser/jreleaser


text:
Failed ABI checks

I'm trying to do a build of 10.3-BETA1 package and keep getting failed ABI checks whenever we start a new build. (Which of course requires rebuilding pkgng, and all other packages)
root@bellicose:/synth/world # file bin/sh
bin/sh: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), dynamically linked, interpreter /libexec/ld-elf.so.1, for FreeBSD 10.2 (1002509), stripped
root@bellicose:/synth/world # ./bin/freebsd-version
10.3-BETA1
How is the ABI determined? Anything else I can run to figure out why this fails?

BTW, I should have mentioned, the host system is running -CURRENT, but we are building 10.3-BETA1 packages using a 10.3-BETA1 base in /synth/world. I assume this is supported?

heh.  This is where synth differs from poudriere.
synth is using a filtered version of the host (by default).  So it looks like you're fixing 10.2 and 10.3.  However, that still shouldn't matter wrt to the ABI.
what does pkg -VV | grep ABI show?
in the meantime, I'll tell you where the ABI code is.

here is interesting: https://github.com/jrmarino/synth/blob/master/src/portscan-packages.adb#L731
It's calculating it from the uname.   What does "uname -mr" show?

root@bellicose:/synth/pkg # pkg -vv | grep ABI
ABI = "FreeBSD:11:amd64";
ALTABI = "freebsd:11:x86:64";
root@bellicose:/synth/pkg # uname -mr
11.0-CURRENTJAN2016 amd64

hmm, that uname should led to the same ABI.  the vm I have here is 11.0-CURRENT i386 and that has no issues.

what packages is it complaining about?  packages that synth built previously?

giving it another whirl now. The existing packages its checking originally came from a poudriere build, would that matter?

probably yes, give it a clean directory

if you are really curiously, use pkg query to find out ABI of any package in that poudriere direcotry

pkg  query -F  '%q' I think

pkg query -F pcbsd-utils-qt5-1454017176.txz '%q'
freebsd:10:x86:64

interesting, is it because its x86:64 and not x86_64?

well, there you go

no, it's because it's 10 and not 11

ok, that begs the question then. Should this work? Or will all 10.x packages always fail ABI check when building on 11.x host?

I.E. our build nodes for 10.2 / 10.3 / 11-CURRENT all run -CURRENT. With synth I'm giving it a 10.3 world in 'Directory_system= /synth/world'

loaded question.
If your 11 host builds a 10 world and installs it, and a synth profile uses that 10 sysroot, you can build 10 packages on 11.

but if you use the live system, which is 11, then it's going to be limited to 11 packages.
poudriere does the same thing with jails

maybe I'm misunderstanding the docs then. Is using the Directory_system= the right way to give it a 10 sysroot?

I.E. our build nodes for 10.2 / 10.3 / 11-CURRENT all run -CURRENT. With synth I'm giving it a 10.3 world in 'Directory_system= /synth/world'

ok, logic flaw on my part

checking uname isn't going to work

kmoore: you are doing it right, synth method of getting abi is logically flawed

ok, whew ;) Do you want to ping back when you have a fix? I'll be eager to test it

let me think about it a bit.  I'll ping you back
It will be easy to rebuild with github hash

by the way, it does use the uname in the specified sysroot, but I forgot that uname just reads the running kernel

BTW, while I've got you doing synth things ;)
It would be cool if we had a 'cleanup' sub-command which only does the umount routines. We have things run via Jenkins, and that would be handy if something crashed / didn't cleanup properly.

it already exists.
run "synth configure" (hit enter)
Any command (other than help and version) will clean up dirty mounts

Will that work via script? I.E. in automation for jenkins?

for jenkins, you won't be able to use any saved options configuration (unless you script that they are always valid, otherwise synth will stop before it starts).  However, I assume you don't override options anyway.
I don't see any command that will exit without doing anything substantial.
However, in theory, the next command that the script sends will clean it up.  The only way it would fail is if a process is still running which prevents the umount.
so in other words, if the mounts are dirty and a build command is issued, the mounts will always be clean up before anything else.  they don't need a special command.

okay Kris, I have something for you to test.
On the makefile line 24, change the hash value to "24bc284"
then run "make makefile"
then the whole clean/disinstall/install routine.
It should work as expected now.

I mean "makesum" (edited above)

Getting closer now, no ABI errors, but each package fails with the following:
========================< phase : check-sanity    >========================
make: "/xports/Mk/bsd.port.mk" line 1162: UNAME_r (11.0-CURRENTJAN2016) and OSVERSION (1002509) do not agree on major version number.
This is expected, you'll need to also set UNAME_r env variable before starting a builder, i remember doing this back in the day when I was doing manual builds ;)

there's a workaround right now.  You can /etc/local/etc/synth/-environment and set it manually.
It's a freebsd-specific issue.  I wouldn't have seen it on dragonfly

I think the solution is related to the work I just did.  Synth is caching _OSVERSION and it's caching the host version.  This is the same logic flaw as uname (the difference being I tried to fix the former but failed and I missed this one)
So the same "file /bin/sh" solution for ABI can be reused to set _OSVERSION correctly.

ok, code is reading <sys/param.h> so that's what I need to do as well.

Ok, setting UNAME_r=10.3-BETA1 in /usr/local/etc/synth/-environment worked fine.
Do you want to add something to set that environment variable automatically though? Thats what poudriere does, if you set it to the output of the 'freebsd-version' from the new world directory, it should work.

no, I'm going to fix it properly.

Ok, works for me. I'm going to keep testing with the workaround in the meantime, see if we run into any other issues.

okay.  I'll have a fix later today.  I'm working on it now.

This should be the proper fix: f676f03
The only "strange" thing is the _OSRELEASE now looks something like "11.0-SYNTH".  The suffix is "-SYNTH" regardless of what it really is.  Hopefully this won't cause any issues.  I guess we will see.
ARCH, OSVERSION, _OSRELEASE, OPSYS were all reworked.

cool! I've got some builds going now, I'll give the fix a whirl shortly

Ok, ran some tests here. With the change applied, I'm still getting errors about UNAME_r not matching:
========================< phase : check-sanity    >========================
make: "/xports/Mk/bsd.port.mk" line 1162: UNAME_r (11.0-CURRENTJAN2016) and OSVERSION (1001000) do not agree on major version number.
Additionally I notice some oddness in the configure scripts:
OSVERSION=100000
_OSRELEASE=1.0-SYNTH
Shouldn't _OSRELEASE be 10.0-SYNTH?
Adding UNAME_r manually to environment fixes problems.

those are the "default" values when something failed.
This worked for me.  Can you post part of sys/param.h, the line that defines __FreeBSD_version ?

#define __FreeBSD_version 1001000       /* Master, propagated to newvers */

This is on a 10.1-RELEASE system base BTW

no, I mean the version in the system root.

or is that it?

yea, that is the file from /synth/world/usr/include/sys/parm.h, where /synth/world is my 10.1-RELEASE base

can you find a synth log and and paste the contents of the make.conf according to the log?  There's nothing wrong with the input line as far as I can tell.

Here's a couple:
http://slexy.org/view/s2hX1CkrER
http://slexy.org/view/s2G9XiLpyn
I think you still need to set UNAME_r properly in the environment. Otherwise the port system will run 'uname -r' manually and see the wrong (host) version. Thats why poudriere has to manually set that variable in each jail / builder.

i promise you it won't. :)

lol ok, you are the expert, I'll let you find the way around it ;)

your log is full of errors.
The make.conf suffix is missing and everything else has "discovery error"

basically the code probably worked, but something else is in play.

Anything I can look at? What exactly is a discovery error?

also, check the second log, no discovery error there

discovery error means the executed command failed (the one in the chroot)

Ahh wait, that one may be because it was building while I manually killed synth. My bad, take a look at the lang_gcc log instead

err, no, wait on that:
root@avenger:/jenkins # synth everything
Builder mounts detected; attempting to remove them automatically ...
Dismounting successful!
Scanning entire ports tree.
Scanning existing packages.
00:06:48 => [02] Builder launched
00:06:48 => [01] Builder launched
00:06:48 => [03] Builder launched
00:06:48 => [06] Builder launched
00:06:48 => [04] Builder launched
00:06:48 => [07] Builder launched
00:06:48 => [05] Builder launched
00:06:48 => [10] Builder launched
00:06:48 => [08] Builder launched
00:06:48 => [11] Builder launched
00:06:48 => [12] Builder launched
00:06:48 => [13] Builder launched
00:06:48 => [09] Builder launched
00:06:48 => [14] Builder launched
00:06:48 => [15] Builder launched
00:06:48 => [16] Builder launched
00:07:23 => [04] 00:00:00 Failure multimedia/ffmpeg
00:07:23 => [16] 00:00:00 Failure devel/libc++
00:07:25 => [01] 00:00:00 Failure print/cups-client
00:07:27 => [08] 00:00:00 Failure lang/gnustep-base
00:07:41 => [07] 00:00:18 Success x11-toolkits/gnome-pty-helper
00:07:43 => [14] 00:00:22 Failure lang/sbcl
00:08:04 => [15] 00:00:52 Success textproc/iksemel
00:08:14 => [06] 00:01:00 Success net/glib-networking
00:08:24 => [05] 00:01:10 Success textproc/redland

HAVE_COMPAT_IA32_KERN=YES
CONFIGURE_MAX_CMD_LEN=262144
_SMP_CPUS=16
UID=0
ARCH=amd64
OPSYS=FreeBSD
OSVERSION=100000
_OSRELEASE=1.0-SYNTH
[ /etc/make.conf TAIL ]

Looks better except for OSVERSION and _OSRELEASE.
(That's a hell of a custom makefile)

ffmpeg and a few others failed almost immediately, right at the beginning. (Those are the ones with discovery errors).
And yes, we have quite a custom make.conf, lots of things specific to desktop packages ;)

any chance mounts are failing?  This is new to me.

maybe? Not seeing anything in dmesg or other obvious mount failures. It cleans up and moves onto the next builder before I can look ;)
This is with 16 concurrent builders defined, want me to drop it down?

the number shouldn't be a problem.  You can if you want but I think the same thing will happen.  I've run with 10 before without issue.

is there anything strange about what synth is mounting to? NFS or prior mounts?
At some point I can tell you what to modify to make it print out the actual error.

No NFS, just a local ZFS filesystem. It is cleaning up prior mounts first though, leme manually clean first and test again.

hold on a sec

can you try hash "a8ed62b"?
It should at least fix the OSRELEASE (I'm guessing) and maybe other stuff with luck.

ok, give me a few min, will report back

Ok, looks like it fixes the issue with OSRELEASE:
OPSYS=FreeBSD
OSVERSION=1001000
_OSRELEASE=10.1-SYNTH
I saw the new status line go by on screen, nice!
Still seeing a couple of random builders fail when it starts up, with the discovery errors though. Only happens at the initial startup, maybe when its busy spinning up all the builders at once?

if that's the case, it's an OS issue.  Maybe freebsd isn't concurrent safe?  What filesystem is being used?
maybe now is the time to halve the builders and see if anything changes.

Ok, I just kicked off another (with full 16 builders), and didn't get any of those failures this time... I'll keep an eye on it, see if I can figure out out reproducible it is. If I find something, I'll open a new bug report.
Marking as closed though, the original issue seems to be fixed.

ok, but it would be interesting to know if this is a ZFS system.
I haven't seen anything like this on DragonFly HAMMER or DragonFly UFS
I suspect you'll see it again, randomly.

Yes, this is ZFS system. (100% ZFS on root, nothing else)

i have a fairly strong suspicion that the custom env definitions are responsible for the discovery errors.

repo: jrmarino/synth

license: isc


text:
Add gcs archive

merging in gcs archive config

Merged into status-monitor-enhancements - do not merge this pr.

repo: jrwashburn/mina-node-install


text:
Uncaught TypeError in reTesselateCoplanarPolygons

I use .union() to merge geometries, but when I do so, it causes errors.
Expected Behavior
Geometries are merged with no issues
Actual Behavior
.union() throws an exception
Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'length')
    at reTesselateCoplanarPolygons (reTesselateCoplanarPolygons.js:176:40)
    at retessellate.js:25:44
    at Array.forEach (<anonymous>)
    at retessellate (retessellate.js:23:14)
    at union8 (unionGeom3.js:21:17)
    at union8 (union.js:42:35)

Steps to Reproduce the Problem
I assume this basic example works for everyone
const c1 = cylinder({ radius: 3, height: 12, center: [0, 0, 5], segments: 12 })
const c2 = cylinder({ radius: 3, height: 18, center: [0, 0, 5], segments: 12 })

const u = union(c1, c2)

Specifications

Version:  "@jscad/core": "^2.6.9", "@jscad/modeling": "^2.12.2",
Platform: Windows 11, Brave Browser,
Environment: Node v16.15.1, esbuild, Brave Browser Version 1.69.153 Chromium: 128.0.6613.85 (Official Build) (64-bit)

Same issue for Google Chrome Version 127.0.6533.122 (Official Build) (64-bit)

polygonindexKey is equal to "clear" or "remove" while we iterate over startingpolygonindexes, what causes vertices2d to be undefined.

If we check for Nan with if (isNaN(polygonindexKey)) continue line, other issue occurs:
Uncaught (in promise) TypeError: Cannot read properties of undefined (reading '1')
    at interpolateBetween2DPointsForY (interpolateBetween2DPointsForY.js:11:16)
    at reTesselateCoplanarPolygons (reTesselateCoplanarPolygons.js:226:15)
    at retessellate.js:25:44
    at Array.forEach (<anonymous>)
    at retessellate (retessellate.js:23:14)
    at union8 (unionGeom3.js:21:17)
    at union8 (union.js:42:35)

@kirevdokimov thanks for the excellent example, and the in-depth analysis.
there are lots of tests but not for this specific example. Given the similarity of the two cylinders, there's obviously something about the retellsation. Have you taken a look at the results of the Union before the retessellation? (Sorry for the spelling)
I'll look over the fix.

Responded in a related merge request: #1361

I was not able to reproduce this issue with the example you gave. Maybe I'm missing something?

authors: kirevdokimov platypii z3dev


text:
🛑 Linus-Wordpress is down

In b916156, Linus-Wordpress ($SERVER_BASE/wordpress/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Linus-Wordpress is back up in c084f62 after 13 minutes.

repo: jscmidt/upptime


text:
🛑 Piwigo is down

In ff6ac95, Piwigo ($SERVER_BASE/piwigo/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Piwigo is back up in 43a286b after 10 minutes.


text:
Custom element is not supported.

sample.coffee
class Button
  render: =>
    super <paper-button className="rui-button rui-form-control" onClick={@buttonClicked}>{text}</paper-button>

is translated to sample.js
// Generated by CoffeeScript 1.8.0
var Button,
  __bind = function(fn, me){ return function(){ return fn.apply(me, arguments); }; };

Button = (function() {
  function Button() {
    this.render = __bind(this.render, this);
  }

  Button.prototype.render = function() {
    return Button.__super__.render.call(this, React.createElement(paper - button, {
      "className": "rui-button rui-form-control",
      "onClick": this.buttonClicked
    }, text));
  };

  return Button;

})();

Note that the React.createElement doesn't give the right output.

Would I be right in assuming that the desired output is
React.createElement("paper-button", ...)

Just bumped into this - looks like the issue is that adding non-alpha characters as the element name in JSX will cause the generated output to be encapsulated in quotes. For example:
example.cjsx
namespace = {}

namespace.SubView = React.createClass
  render: ->

Just a subview...

FailureCaseView = React.createClass
  render: ->
    <namespace.SubView />

SuccessCaseView = React.createClass
  render: ->
    React.createElement(namespace.SubView, null)

and the output example.js (look at FailureCaseView vs SuccessCaseView):
// Generated by CoffeeScript 1.9.1
(function() {
  var FailureCaseView, SuccessCaseView, namespace;

  namespace = {};

  namespace.SubView = React.createClass({
    render: function() {
      return React.createElement("div", null, "Just a subview...");
    }
  });

  FailureCaseView = React.createClass({
    render: function() {
      return React.createElement("namespace.SubView", null);
    }
  });

  SuccessCaseView = React.createClass({
    render: function() {
      return React.createElement(namespace.SubView, null);
    }
  });

}).call(this);

In the output JS, FailureCaseView's render should read the same as SuccessCaseView.

Ah nevermind - my hypothesis in the last comment wasn't right. It's the fact that the first character in my namespace is a lowercase character. According to the React documentation the convention is lowercase = HTML tag (and therefore the quotes) and uppercase is another React component. Since the convention is this way, it's probably not an issue.

The official JSX transformer doesn't seem to require the first character to be lower case when a namespace is used. We should probably support that functionality also, to keep in line with JSX. However, the convention is certainly to use an upper case first letter.

It would be great if this could be mentioned somewhere in the documentation. I spent awhile trying to figure out why my element wasn't being compiled "correctly."

@cganas Sure thing. In the near future however, I'll change the implementation to only treat non-namespaced element names as custom elements.

I don't think this works right now. I took the example from the website with the  tag, and it didn't work.

authors: Saturn2888 briann cganas jsdf mirikle

repo: jsdf/coffee-react


text:
Generate documentation for code with return outside function

I am trying to generate jsdoc documentation for code with return statements outside of functions.
Since the 3.5.0 release babylon is used as parser and the parser treats this as an error.
The babylon parser has some Options https://github.com/babel/babylon#options
allowReturnOutsideFunction  By default, a return statement at the top level raises an error. Set this to true to accept such code.
IDEA: Add the possibility to customize the parserOptions in the jsdoc config file.

Fixed on master and releases/3.5. The fix will be included in JSDoc 3.5.4.
Now that I've enabled all of Babylon's options, I don't think there's a good use case for making the parser options customizable.

authors: hegemonic kozi


text:
Closes #1081 by adding the anonfuncs option

This option allows anonymous (unnamed) functions.
If false, anonymous functions will raise a warning (W126).

+1

authors: Starefossen hughes

repo: jshint/jshint


text:
[[FIX]] Don't throw W080 when the initializer starts with undefined

Example:

var a = undefined === 0; // a is 'false', not 'undefined'

Fixes gh-2699

Thanks for the patch! It's missing a few test cases, though. Can you add assertions for destructuring patterns, eg:
var [ a = undefined === 0 ] = [];
[ a = undefined === 0 ] = [];
var { b: b = undefined === 0 } = {};
({ b: b = undefined === 0 } = {});

Can you add assertions for destructuring patterns

Done

Squashed and merged to master at commit 0d879196bab1c733f1299d2dbc470362b64c9bc6. Thanks!

authors: jugglinmike nicolo-ribaudo


text:
explicitly state type member is required in update

Note explaining type is always required was only under 'Creating Resources'

Move note to general CRUD section introduction
Remove blockquote formatting, so it is more visible

type member was explicitly required in 'Creating Resources,' not 'Updating Resources'

Explicitly called it out in 'Updating Resources'
Did not call it out in any relationship updating sections

Feel free to tweak this PR. Mainly a convenient way of pointing out the issue locations.

I believe a good portion of this needs to remain a non-normative note, rather than official language of the spec. But thanks for pointing out that it might get overlooked in its current location. I'll review with @wycats, who wrote this particular note.

Merged via c09a00c17253d332173eb439d657fef97f14f8df and 2bc4a9c0687a7b0d4cd9fc0de76e68c7eacb9960 which returns this to being a non-normative note.

authors: bobholt dgeb

repo: json-api/json-api


text:
Replace the control escape \a with \t in ecmascript-regex.json

At least this fixes the wrong test case reported in issue #309

Thanks very much!

authors: Julian leadpony

repo: json-schema-org/JSON-Schema-Test-Suite


text:
Add in a contributors document outlining the repo's process.

This document is undoubtedly incomplete and can be iterated on.
It represents, to the best of my knowledge, the existing process I have followed myself since the repository's inception, with only minor tweaks (back then lots of GitHub UI features didn't even exist!).
Of course over the years it may not have been followed by everyone, nor even possibly by myself, but putting it here should hopefully make it clearer to everyone what the baseline is, in case we wish to make changes.
There are some differences here from processes followed in other JSON Schema org repos -- whether this is an issue or not is of course constructively debatable.

Thanks. This document was meant to be more about process than a test style guide (which is #439) -- though I did start to get into some of that topic by adding the test modification section it seems, so happy to try to address some of those here.

I'm concerned about the various bits that allow merging or directly committing to main outside of the GitHub UI.  It's important for the community to have visibility, and we get that through GitHub notifications.  For example, I'm fine with merging trivial fixes more-or-less immediately (we do that on the web site repo, and in rare cases even on the spec repo if a trivial fix is blocking something bigger).  But if someone does take too expansive of a view of "trivial", we'll never know without the GitHub notifications.  Most people don't continuously pull a local copy and scan the commit log for commits that didn't go through GitHub PRs.
Also, merging a PR outside of GitHub leaves GitHub in a very confusing state as I discovered when asked to look at such a PR a while back.  I could not figure out what had gone on at al and had to ask to have it explained.  And I'm not exactly a git or GitHub novice.  This would be even more confusing for a less experienced person watching the repo, who might be less comfortable asking.
I don't think it's a huge burden to do things through the GitHub UI, and it adds a lot of community value.

The request was to document the current process. We can certainly discuss changes to it but what I've written down is what's been done until now. GitHub notifications are a way, and maybe one that works well for you personally, but not the only one -- as I say though, we can discuss changes certainly.

@karenetheridge added those, thanks. Have another look.

Thanks all -- going to merge, but will mention again step 1 was to just write this down, so certainly now if anyone feels strongly about changing things feel free to bring it up in a discussion or issue or whatever.

Oh -- in exchange I'll also ask that if something comes up in a PR that seems like it belongs in here (because we forgot to add it, say) please make that note on said future PR when it happens!

authors: Julian handrews


text:
Only add commas between array elements when needed

Old behavior:
[1, -> [1,2, etc.
New behavior:
[1 -> [1,2 etc.
This fixes at least following tests:
ArrayValuesTest
MultipleArrayValuesTest
NestedArraysTest
EmptyStringSpaceTest

Thanks. I'm going to merge this, but it might get replaced in the future by code that is based on the way JSON5.stringify handles arrays, which is in turn based on how ES6 stringify handles arrays.

authors: jordanbtucker mcraiha


text:
add failing test for issue with openai and langchain

The generator crashes when installing openai along with langchain/text_splitter.

 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.

Thanks again for sharing this test case. The error message bug was fixed in https://github.com/jspm/generator/pull/358 and separately OpenAI should now be working.

authors: CLAassistant guybedford haikyuu

repo: jspm/generator


text:
Fix typo

Fix typo in java doc

@doychin please make sure to sign the CLA at https://www.clahub.com/agreements/jsr377/jsr377-api

authors: aalmiray doychin


text:
Do not add the RetryableWriteError label to errors that occur during

a write within a transaction (excepting commitTransaction and abortTransaction)
JAVA-3721
Evergreen patch: https://evergreen.mongodb.com/version/5ebb5ada7742ae20850b776b
Test update only. No code changes needed.

The changes made in JAVA-3531 (https://github.com/mongodb/mongo-java-driver/commit/3d3716c92dbf696e2cb64175830d6e72b662f2d9) implement the correct behavior, especially the method addRetryableWriteErrorLabel (https://github.com/mongodb/mongo-java-driver/blob/1db5680c00469332f24e5349ac75caad729995d8/driver-core/src/main/com/mongodb/internal/operation/CommandOperationHelper.java#L1015)

repo: jstewart-mongo/mongo-java-driver


text:
why is the .off() function isn't working for me?

Hi @jgermade ,
i have this code where i want to be able to drag a button on the X axis and for some reason when i try to off() the 'mousemove' event on the 'mouseup' event it wont work, any i idea why?
Here is my code:
  $(progress-button).on('mousedown', function(e){
        $(this).on("mousemove",function(e){
            $(this).css('left', e.pageX + 'px');
        });
    }).on('mouseup', function(){
      $(this).off('mousemove');
  });

Hi @RongBranovate ,
in order to detach a listener from an element, handler needs to be passed, this should work:
function mousemove (e) {
    $(this).css('left', e.pageX + 'px');
}
 $(progress-button).on('mousedown', function(e){
      $(this).on("mousemove", mousemove);
    }).on('mouseup', function(){
      $(this).off('mousemove', mousemove);
    });

Hi @jgermade , thanks for your reply,
The thing is i can't get the 'mouseup' to fire, the button just keeps moving even after i stoped pressing the mouse button down, its just moves to the right when i try to get to it....

Hi @RongBranovate, I've found this: http://stackoverflow.com/questions/4065992/jquery-detecting-pressed-mouse-button-during-mousemove-event

Hi @jgermade ,
I'll look into this, and let you know,
thanks!

authors: RongBranovate jgermade

repo: jstools/jqlite


text:
Container crashes on cloud run

Container crashes on cloud run
To Reproduce

Use SvelteKit v1.0.0-next.94 and the current version of svelte-adapter-firebase.
Build the SvelteKit demo app with firebase adapter (for cloud run)
Deploy the demo app to cloud run with gcloud beta run deploy mysitessr --platform managed --region us-central1 --source .mysitessr --allow-unauthenticated
Goto /todos on the deployed app -> 500 error in the client and Cannot find package '@sveltejs/kit' imported from /workspace/app.mjs in the cloud run logs (detailed logs in the screenshot below)

This was also reproducible with other projects than the demo app. There the Cannot find package '@sveltejs/kit' imported from /workspace/app.mjs was returned back to the client.
Expected behavior
Container should work and not crash
Screenshots

Current SvelteKit version support is @svelte/kit@1.0.0-next.54, I am updating to @svelte/kit@1.0.0-next.94 atm.
Once the new version is released you can test again.

repo: jthegedus/svelte-adapter-firebase


text:
Init.d script missing

So after running the Server install for OSSEC, it reported that it couldn't start. Here the error from chef log. I checked and ossec didn't create a init.d script.
[2015-03-23T14:21:22+00:00] ERROR: service[ossec] (ossec::default line 76) had an error: Chef::Exceptions::Service: service[ossec]: unable to locate the init.d script!
Looking at the OSSEC information, I found this in the install fill:
The script will create everything in /var/ossec and try to create the initialization script in your system (/etc/rc.local or /etc/rc.d/init.d/ossec). If the init script is not created, make sure to follow the instructions from the install.sh to make OSSEC HIDS start during the boot. To start it by hand, just run /var/ossec/bin/ossec-control start

This seems to be resolved in master right now

repo: jtimberman/ossec-cookbook


text:
Custom detection points are not looked up for possible responses

org.owasp.appsensor.analysis.ReferenceAttackAnalysisEngine's method findPossibleResponses doesn't look up also custom detection points for possible responses.
Is this an intended behaviour or it is a bug?
I have almost ported the code to Javascript.
In one of my tests, I configured custom detection poin and generate events of it.
org.owasp.appsensor.analysis.ReferenceEventAnalysisEngine in analyze method takes advantage of org.owasp.appsensor.core.configuration.server.ServerConfiguration's findDetectionPoints method which looks up custom detection poins as well.
When an attack of this detection point is analyzed by org.owasp.appsensor.analysis.ReferenceAttackAnalysisEngine, it doesn't
find possible response and corresponding generated response's action is empty.
Thank you very much for your great code.
Kind regards,
Spas Iliev

Hello,
I see https://github.com/jtmelton/appsensor/pull/35 and the reason behind to override some aspects of detection points.
I used to think of client/custom detection points as an extension (e.g. Z01) to the points described in the reference of AppSensor Guide v. 2.0.
I think in both cases the question still stands: Why not to override the response as well?
Kind regards,
Spas Iliev

repo: jtmelton/appsensor


text:
Output icon only has 256 indexed colors palette versions

I converted a SVG image using the script in the readme, but the output ICO file only contains versions in 256 indexed colors palette.
Is it possible to choose the bit depth with the sizes as well?

Internally, svg-to-ico uses the sharp package to do SVG parsing and image manipulation.  It looks like it does provide a toColourSpace() function that can be called on an image to change the colour model.  One of the options that can be included with that function is "srgb" but the documentation indicates that this is the default output if no other colour model is specified.

Went down the ICO, BMP, PNG file format specification rabbit hole.. 😄  It seems the desktop application I was viewing the resulting ICO file in just could not handle the embedded PNG image (and showed them as 256-color bitmaps). This program uses Windows 32bpp RGBA bitmap format instead of PNG.
Anyway, this issue is not longer needed. Thanks for the quick response and the tool!

authors: jtrauntvein vHeemstra

repo: jtrauntvein/svg-to-ico


text:
not responding

I have been trying to set this up for a few days now and have uninstalled and reinstalled everything once but when I get to the step to preview the camera and set up the trackers the program stops responding and forces me to close it I don't know if this is a problem on my end and have been working to figure out if it is but would like to hear opinions and /or likely solutions. Thank you

Some USB cameras take a very long time to open on default settings, sometimes up to a minute, so its possible you just have to wait for a bit longer. Or, set the Camera API Preference parameter to 700, that can often speed things up, if supported by the camera.


text:
Improve sample codes

Description
The sample codes are missing a few non-code improvements.
Here are some that could be implemented, in my opinion:

Fully document the sample codes and explain what each function does and everything. Doxygen can be used.
Add syntax coloring to make it more beautiful and understandable.
A few more examples could be added for more variety and a basic understanding/knowledge of the language at first glance. For example: if else cases would be awesome.

Let me know your thoughts. Thanks. 🙂

I've improved the existing codes a little bit, additionally added FizzBuzz and Levenshtein Distance algorithms. If you have any algorithm suggestions, please share them with us.
I think it could also be good with documentation, but without syntax highlighting, I think it would add more complexity for just the reviewers. That's why I'm in the opinion of adding the documentation with syntax highlighting. I have no clear idea if syntax highlighting is possible. @lareii What do you think about syntax highlighting?

I've improved the existing codes a little bit, additionally added FizzBuzz and Levenshtein Distance algorithms. If you have any algorithm suggestions, please share them with us.

Cool, thank you! Adding if else case examples would be great as well, it's one of the most used things, IMO.

Is there an algorithm you suggest we add for if else example?

Good question, not sure about that. Probably something simple related to printing numbers, such as odd/even numbers? 🤔

I'm thinking of an example that might make a little more detailed. But if we improve the example you mentioned a little more, I think it could be something like the following:
enum NumberKind {
	Even,
	Odd,
	Zero,
}

fn kind_of_number(x: int): NumberKind {
	if x == 0 {
		ret NumberKind.Zero
	} else if x%2 == 0 {
		ret NumberKind.Even
	} else {
		ret NumberKind.Odd
	}
}

fn main() {
	outln(kind_of_number(10))
	outln(kind_of_number(0))
	outln(kind_of_number(1))
}

idk how to implement the highligthing but i'll do my best.

I added Number Kind example program, includes enum and if-else chains.
Syntax highlighting is controversial and it's not main purpose of this issue, so I'll close this issue.

authors: Panquesito7 lareii mertcandav

repo: julelang/website


text:
Json Export

Trying to export data in JSON
Until now my litedb file was around 30mb and I was able to export. Now file is doubled and getting errors exporting.
Can you help me with this issue? I see its memory problems. My desktop has 16GB Ram if this is needed
This is what I have in logs file:
2019-03-11 19:42:27.1148|ERROR:Unhandled exception: System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
at System.Text.StringBuilder.ToString()
at LiteDB.JsonSerializer.Serialize(BsonValue value, Boolean pretty, Boolean writeBinary)
at LiteDbExplorer.Modules.DatabaseInteractions.ExportDocuments(ICollection`1 documents)
at LiteDbExplorer.Modules.DatabaseInteractions.ExportSelectedDocuments()
at LiteDbExplorer.MainWindow.ExportCommand_Executed(Object sender, ExecutedRoutedEventArgs e)
at System.Windows.Input.CommandBinding.OnExecuted(Object sender, ExecutedRoutedEventArgs e)
at System.Windows.Input.CommandManager.ExecuteCommandBinding(Object sender, ExecutedRoutedEventArgs e, CommandBinding commandBinding)
at System.Windows.Input.CommandManager.FindCommandBinding(CommandBindingCollection commandBindings, Object sender, RoutedEventArgs e, ICommand command, Boolean execute)
at System.Windows.Input.CommandManager.FindCommandBinding(Object sender, RoutedEventArgs e, ICommand command, Boolean execute)
at System.Windows.Input.CommandManager.OnExecuted(Object sender, ExecutedRoutedEventArgs e)
at System.Windows.UIElement.OnExecutedThunk(Object sender, ExecutedRoutedEventArgs e)
at System.Windows.Input.ExecutedRoutedEventArgs.InvokeEventHandler(Delegate genericHandler, Object target)
at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
at System.Windows.UIElement.RaiseEvent(RoutedEventArgs args, Boolean trusted)
at System.Windows.Input.RoutedCommand.ExecuteImpl(Object parameter, IInputElement target, Boolean userInitiated)
at System.Windows.Input.RoutedCommand.ExecuteCore(Object parameter, IInputElement target, Boolean userInitiated)
at System.Windows.Input.CommandManager.TransferEvent(IInputElement newSource, ExecutedRoutedEventArgs e)
at System.Windows.Input.CommandManager.OnExecuted(Object sender, ExecutedRoutedEventArgs e)
at System.Windows.UIElement.OnExecutedThunk(Object sender, ExecutedRoutedEventArgs e)
at System.Windows.Input.ExecutedRoutedEventArgs.InvokeEventHandler(Delegate genericHandler, Object target)
at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
at System.Windows.UIElement.RaiseEvent(RoutedEventArgs args, Boolean trusted)
at System.Windows.Input.RoutedCommand.ExecuteImpl(Object parameter, IInputElement target, Boolean userInitiated)
at System.Windows.Input.RoutedCommand.ExecuteCore(Object parameter, IInputElement target, Boolean userInitiated)
at MS.Internal.Commands.CommandHelpers.CriticalExecuteCommandSource(ICommandSource commandSource, Boolean userInitiated)
at System.Windows.Controls.MenuItem.InvokeClickAfterRender(Object arg)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)
at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(Object obj)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at MS.Internal.CulturePreservingExecutionContext.Run(CulturePreservingExecutionContext executionContext, ContextCallback callback, Object state)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
at System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame)
at System.Windows.Application.RunDispatcher(Object ignore)
at System.Windows.Application.RunInternal(Window window)
at System.Windows.Application.Run(Window window)
at LiteDbExplorer.App.Main()

See: #12.
Thanks.

If you can try this version to see if it's better: LiteDbExplorer_prev_0.8.0_0312
This is a pre-release. We’ll point out that this release is identified as non-production ready.

authors: informacione julianpaulozzi

repo: julianpaulozzi/LiteDbExplorer


text:
change theme

change theme for first layouts

change theme

authors: JesselizCB julioray

repo: julioray/cotizacion


text:
Not being able to load routes and connections for Munich Central Station

When I try to search the Munich Central Station (https://direkt.bahn.guru/?origin=8000261), I get the following error: "Oops?!
Unknown error. Please try again in a few moments or contact us, if the issue persists.".
Any possible fix for this issue? Thanks!

Should this issue be closed as the link works now?

authors: roboes tuukka

license: ISC


text:
npm install complains

I followed recommended installation process and got some warnings
$ npm install --save bilkom
npm WARN saveError ENOENT: no such file or directory, open '/home/mateusz/Desktop/tmp/bilkom/package.json'
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN enoent ENOENT: no such file or directory, open '/home/mateusz/Desktop/tmp/bilkom/package.json'
npm WARN bilkom No description
npm WARN bilkom No repository field.
npm WARN bilkom No README data
npm WARN bilkom No license field.

--save tries to add the package to your package.json, I'm assuming that there is none in your directory, hence the errors. Not sure if this is bad on the package's part, though, since this is rather normal behaviour.

since this is rather normal behaviour.

In that case I am closing. I have no experience with npm and "npm WARN bilkom" suggested that problem is on npm part.
I will look at npm bugtracker, if they have less than 1000 open issues I will report it.

From what I see at https://github.com/npm/cli and https://npm.community/ they have no bug tracker and handle reports by dumping it on forum, so there is no point in spending time on reporting issues.

Could it be that the directory you were trying to install the package in was also called bilkom? Because as far as I know, the displayed error name will be the current directory.

Yes, from looking at it - there is a complaint about /home/mateusz/Desktop/tmp/bilkom/package.json file.

authors: juliuste matkoniecz

repo: juliuste/bilkom


text:
Estimate account creation date by checking next/previous player creation dates

Since profile number ids are incremental, we could just estimate median creation date by checking closest profiles from the database.

I remember some other website did this. By database, do you mean the profiles stored in vacstatus?

Yes.
And yup, I think it was steamrank.com which no longer exists. Used it very frequently to check quickly age of all accounts, would be nice to have it again.


text:
你好，我正在尝试改进您的模型，想请问一下您的帧率是如何计算的。

比如有输出
[03/30 02:34:58 d2.evaluation.evaluator]: Inference done 1192/1250. Dataloading: 0.0016 s/iter. Inference: 0.0399 s/iter. Eval: 0.1135 s/iter. Total: 0.1550 s/iter. ETA=0:00:08
[03/30 02:35:03 d2.evaluation.evaluator]: Inference done 1227/1250. Dataloading: 0.0016 s/iter. Inference: 0.0399 s/iter. Eval: 0.1132 s/iter. Total: 0.1548 s/iter. ETA=0:00:03
[03/30 02:35:08 d2.evaluation.evaluator]: Total inference time: 0:03:13.537369 (0.155452 s / iter per device, on 4 devices)
[03/30 02:35:08 d2.evaluation.evaluator]: Total inference pure compute time: 0:00:49 (0.039901 s / iter per device, on 4 devices)
请问您计算帧率是 直接 1/ 0.039901 吗？

您好，是的


text:
Typescript implementation of project

There are great complications faced as the architecture is not in typescript, and hence a step towards improving it must be taken !!

@shubhamkakkar Thanks for your comment. We already started a project of rewriting jscu in TypeScript (check the current status on README.md), and it may take several weeks to complete. If you like, you can contribute to it ;-)

We've done it! Please check it out ;-)

authors: junkurihara shubhamkakkar

repo: junkurihara/jscu


text:
Fix unbuild of lines

Lines are not in the air, so unbuild them is not to fill the with air but with a dirt block.

Already done!

repo: juntosdesdecasa/mcthings


text:
Show advanced options when at least one input has an error

Problem
If the advanced options panel is collapsed, and at least one input in it has an error, the user might not know whey they cannot submit the form.
Proposed Solution
When the expandable section is collapsed and at least one error is contained in it, display an indicator on the section.
Alternatively, keep the section expanded and do not let the user collapse the section if at least one error is present.

I believe we can do this 1 of two ways:

pass the functions to set the state for this collapsible panel within advanced options, and we could set it directly, Although I think this might cause issues.

on the advanced options side, we can set the errorMessage state on initial mount (maybe check for empty value) which would then trigger a re-render and prompt you to open up Advanced options. I am more in favor of this approach.

Let me know what you thing 💭

Personally, I prefer the idea of letting the user collapse the expandable section, and then if there's an error in advanced options, provide an indicator like ⚠ or ⛔ to suggest that there is an error in it.
We have errors which is a simple key-value store, but this may not be sufficient, since we don't know which keys in errors correspond with the advanced options section. We could have the advanced options extension point include a list of inputs, or we could have a separate list of errors specifically for the advanced options section. That separate list would give you more direct control, but it'd also require us to check two different errors objects to determine whether the "Create" submit button is active.

I like the idea of keeping two separate error state objects actually. That way we can make sure the advanced options don't mess with the default available options error states. But it does have a caveat of you having to iterate over two objects and checking for validity.
It would, however, also let you better identify on whether or not to show the ⚠ or ⛔ icons based on which iterated object has the error 🤔

authors: awaisabir jweill-aws

repo: jupyter-server/jupyter-scheduler


text:
Logo in docs

I discover yesterday that you can put a logo in the sidebar of readthdocs. Example:  https://flit.readthedocs.org
Do you think that would be useful for  jupyter related docs to have a visual Jupyter logo ?
@ellisonbg @cameronoelsen ?

Yes please!

Has this been assigned yet?

Has this been assigned yet?

No you can try to do it.

We have since made a Jupyter-specific sphinx theme (https://github.com/jupyter/jupyter-alabaster-theme) that fixes this issue!

authors: Carreau cameronoelsen go-bears rgbkrk


text:
buildpacks/nix: 2.3 -> 2.3.9

Update to latest version.

Changelog removed.

Figshare failure is unrelated.

As far as I can tell this is ready to go.

As far as I can tell this is ready to go.

Thanks for this version bump and sorry about being slow getting this merged.

Thanks for this version bump and sorry about being slow getting this merged.

authors: FRidh betatim


text:
refactor(router): change payment error message from not supported to not imp…

…lemented
Type of Change

[ ] Bugfix
[ ] New feature
[ ] Enhancement
[x] Refactoring
[ ] Dependency updates
[ ] Documentation
[ ] CI/CD

Description

Additional Changes

[ ] This PR modifies the API contract
[ ] This PR modifies the database schema
[ ] This PR modifies application configuration/environment variables

Motivation and Context
How did you test it?
Manual checking
Checklist

[x] I formatted the code cargo +nightly fmt --all
[x] I addressed lints thrown by cargo clippy
[x] I reviewed the submitted code
[ ] I added unit tests for my changes where possible
[ ] I added a CHANGELOG entry if applicable

Fixes #2836

Hey @oscar2d2 ,
The issue which you picked was for ACI connector.
Can you please make the required changes in that connector.

Hey @oscar2d2 , The issue which you picked was for ACI connector. Can you please make the required changes in that connector.

Hi @swangi-kumari, thanks for the review. I have updated the branch, would you please review again?

Hey @oscar2d2 ,
Please resolve the conflicts from your branch.

repo: juspay/hyperswitch


text:
🛑 Jellyfin is down

In b294369, Jellyfin (https://video.mkacg.com) was down:

HTTP code: 530
Response time: 61 ms

Resolved: Jellyfin is back up in de3387e after 20 minutes.


text:
Use GitHub actions to automatically create issues for dependabot alerts

Use GitHub actions to automatically create issues when dependabot finds security vulnerabilities, and add the issue to our GitHub project board:
https://docs.github.com/en/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions

I think I may have a path forward for this, but there is a small caveat.
I found this article where someone created a a workflow in their GH repo that will create an issue whenever Dependabot opens a PR: Create Issues Automatically with Dependabot

This workflow ^^ basically listens for pull_request events in the repo and opens an issue IF dependabot is the user that opens the PR.
It seems that might be the criteria we have to go by if we want a version of this action in our workflows - looking at the list of events that trigger workflows , we are unable to listen to events related to dependabot (its not listed as an event we can listen for) - so our next best option would be to listen for Pull Requests opened by Dependabot.
We would need to also add a workflow that listens for new issues and automatically places them in the project board. But there are examples of that:
@jakemer @TiagoFuelber what do you think of doing it this way?
TLDR: We can add a workflow for this, but it will only be able to run when Dependabot opens a PR on its own. We will not be able to make a new issue for any Dependabot alert because Github does not allow us to listen to Dependabot events via their API.

authors: colganmeanor jakemer

repo: justifi-tech/web-component-library


text:
Update from 1.4.4 to 1.5.0 multiple issues

Does this project follow semantic versioning?
Undefined property: stdClass::$definitions
 C:\Proyectos\SwaggerAssertions\vendor\justinrainbow\json-schema\src\JsonSchema\RefResolver.php:270
 C:\Proyectos\SwaggerAssertions\vendor\justinrainbow\json-schema\src\JsonSchema\RefResolver.php:238
 C:\Proyectos\SwaggerAssertions\vendor\justinrainbow\json-schema\src\JsonSchema\RefResolver.php:123
 C:\Proyectos\SwaggerAssertions\src\SchemaManager.php:201
 C:\Proyectos\SwaggerAssertions\src\SchemaManager.php:65
 C:\Proyectos\SwaggerAssertions\src\PhpUnit\ResponseBodyConstraint.php:86
 C:\Proyectos\SwaggerAssertions\src\PhpUnit\ResponseBodyConstraint.php:52
 C:\Proyectos\SwaggerAssertions\src\PhpUnit\AssertsTrait.php:39
 C:\Proyectos\SwaggerAssertions\tests\PhpUnit\AssertsTraitTest.php:34

The maximum stack depth has been exceeded
 C:\Proyectos\SwaggerAssertions\vendor\justinrainbow\json-schema\src\JsonSchema\RefResolver.php:105
 C:\Proyectos\SwaggerAssertions\src\SchemaManager.php:201
 C:\Proyectos\SwaggerAssertions\src\SchemaManager.php:232
 C:\Proyectos\SwaggerAssertions\src\SchemaManager.php:77
 C:\Proyectos\SwaggerAssertions\src\PhpUnit\ResponseHeadersConstraint.php:87
 C:\Proyectos\SwaggerAssertions\src\PhpUnit\ResponseHeadersConstraint.php:52
 C:\Proyectos\SwaggerAssertions\tests\PhpUnit\ResponseHeadersConstraintTest.php:42

@Maks3w welcome back.
There is discussion (see issues) around the addition of an exception in 1.4.4 for maximum depth, and this is the first I am seeing of anything related to the definitions property. Thanks for the report.
What about semver are you expecting presently?

Maximum depth exception was added on 1.4.4. The issue is upgrading from 1.4.4 to 1.5.0
I expect no backward compatibility issues while upgrading between minor versions.

$definitions it's part of the json schema under test (Swagger v2.0 specification)

This still broken in 1.6.1

See #210

See #245

Closed with https://github.com/justinrainbow/json-schema/pull/174

Can you elaborate why #174 is related to this?

@Maks3w I think @bighappyface did mean #245

@jojo1981 @Maks3w yes, I meant https://github.com/justinrainbow/json-schema/pull/245
Sorry for the confusion

repo: justinrainbow/json-schema


text:
Battle steed.Al

Before submission deletes this line:
THIS IS NOT A TOKEN LISTING REQUEST FORM. IF YOU DO NOT FOLLOW THE FORMAT OR MAKE A GENERIC TOKEN REQUEST YOUR ISSUE WILL BE DELETED WITHOUT COMMENT
YOUR JUSTLIST MUST FOLLOW THE JSON SPECIFICATION
https://github.com/justswaporg/justlists/blob/main/example.justlists.ts
Checklist

[ ] I understand that this is not the place to request a token listing.
[x] I have tested that my JustList is compatible by pasting the URL into the add a list UI at justswap.org.
[x] I understand that filing an issue or adding liquidity does not guarantee addition to the justlists website.

Please provide the following information for your token.
JustList URL must be HTTPS.
JustList URL:
JustList Name:
Link to the official homepage of the JustList manager:

Shehroz

Please submit the correct information, invalid information will cause the issue to close

repo: justswaporg/justlists


text:
intervals: test data with multiple intervals

also current_week_number draws different week boundaries from
JuttleMoment, so we need to use current_week_number when deciding
what indices to read from
@VladVega @dmehra

+1 on tests that are here, see above re: tests that are not.

+1

authors: davidvgalbraith dmehra

repo: juttle/juttle-elastic-adapter


text:
vectorized operation on simplify, conjugate and evalf

Can simplify, conjugate and evalf be made work on vectors and matrices? At the moment, they seems to work on scalars only.

On v0.5, conj (aliased to conjugate) works with matrices. But simplify and evalf don't. (But N does.) I could add methods, but it seems that the "." syntax for broadcasting should be encouraged. Let me know if that isn't convenient enough. Thanks for all the feedback.

What, wait, it's me who thanks you for all the good work!
I am not familiar with the "." syntax. Is broadcast(conj, A) what you mean for v0.4.6?

Yes. But with v0.5 this becomes conj.(A).
On Monday, September 5, 2016, Michele Zaffalon notifications@github.com
wrote:

What, wait, it's me who thanks you for all the good work!
I am not familiar with the "." syntax. Is broadcast(conj, A) what you
mean for v0.4.6?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/jverzani/SymPy.jl/issues/86#issuecomment-244724890,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAZvTOWUblGlaAZYMB0cUGdmzPIAK54Gks5qm_zogaJpZM4J0npy
.

--
John Verzani
Chair, Department of Mathematics
College of Staten Island, CUNY
verzani@math.csi.cuny.edu

I am perfectly fine with the syntax boadcast(conj|evalf|simplify, A).

Great

authors: jverzani mzaffalon


text:
i added some stuff

installs more things, adds some color, uses separate functions file, and adds stupid comments from me

Awesome thank you! Will take a look later after work!