#36044 Fix and enhance new autocompletion engine

[ ] https://github.com/dbeaver/dbeaver/pull/36434#issuecomment-2528477790
[ ] Add autocompletion of join condition by non-compound foreign keys

[ ] Fix completion right after the keyword
[ ] Fix qualified table names accomplishment
[ ] Fix keyword completion for some cases (now you can see more keywords in proposals than in the previous version)
[ ] Fix duplicated table aliases generation #35891
[ ] Fix additional dot inserting when applying the completion proposal in the join condition #35893
[ ] Autocomplete of tables columns in self-joins #34251

if you put a dot after an alias and do autocomplete, the alias is duplicated
https://github.com/user-attachments/assets/09511cf4-0493-4930-994f-156cddc4dd43

left in LEFT JOIN recognized as alias
select   from x left join y on x.x1 = y.y1 ;
https://github.com/user-attachments/assets/ef6463f2-1014-4378-b058-ecf407b1b26c

verified


Bump guava version since it's vulnerable

https://devhub.checkmarx.com/cve-details/CVE-2020-8908/

done


docs: Small fix to writing-marble-tests.md

Description: Small fix to the examples that were missing their closing single quotation mark.

Coverage remained the same at 97.204% when pulling 1de310ec50f19018dc940955bd7a9c98491afdf8 on getDanArias:docs-marble-tests-examples into cff9dfa7c5fdc6606721a2efcee23327ff966a5f on ReactiveX:master.

Thanks for the small fixes!


add macro recording option

Description of the new feature / enhancement
Record mouse and keyboard actions and any other device input (barcode scanner)
Shortcut keys for activation or virtual menu
shortcut for saved recording profile menu...
Scenario when this would be used?
Automatization of steps...
Supporting information
No response

You can use PowerAutomate Desktop to do exactly this. Create a flow and then assign a keyboard shortcut to it.

You can use PowerAutomate Desktop to do exactly this. Create a flow and then assign a keyboard shortcut to it.

Is there Admin permission?
Power toys is great because it doesn't need admin...

Hi, I went through issues for finding using Mouse shortcuts with keyboard in PowerToys.
My mouse has 2 extra buttons, usually using it for Go Back & Go forward, but I want to use it with different shortcuts for specific applications, I used Auto Hot Key for it, but still want to find a way to use Mouse shortcuts on PowerToys.


Accept URIs without none+ and return URIs without none+

I see usability issues with none+ prefix in URI scheme:

A user must specify a URL that starts with none+ to create an HttpClient with a ClientBuilder.

We could assume none+ exists when a user did not prepend it.
It becomes a little bit more ambiguous, I think it will not be that confusing. It's like removing 0 from 0.1 (= .1).

HttpClient.uri() returns a URI that starts with none+, which is somewhat confusing. For example, a user cannot convert the returned URI into a URL:HttpClient client = ...;
client.uri().toURL(); // Fail

I'd like to:

Make the none+ prefix optional when creating a client.
Make ClientBuildParams.uri() return a URI without the none+ prefix.

/cc @anuraaga We had a discussion about this before and chose to make it always explicit but what do you think about reconsidering?

Can't remember the discussion ;) I think allowing URL without none+ for ClientBuilder makes sense, but I'd suggest uri() returns what the user entered, so including none+ if they had it themselves. Losing user information seems weird to me.

Losing user information seems weird to me.

I'm not sure I like this idea because the caller of uri() might not always be who created the client and might expect a consistent return value for the both cases (with/without none+).

Hmm that's true - in that case how about we add  serializationFormat() and sessionProtocol() (less important) to ClientBuilderParams and change uri() to never return *+ even for non-http clients? That allows the pieces of information to be easily available and is the most consistent, so .uri().toURL() will always work.
I'm also a littler concerned about the ClientBuilder API after this change - I think I'd expect this to work
new ClientBuilder("http://github.com")
  .serializationFormat(SerializationFormat.PROTO)
  .build(...)

Should we also make a change to allow that?

What if a user wants a URL with serfmt? Should we add a method like fullUri()?

I guess that seems like overkill - it seems fine to me then for uri() to return a + or not based on serialization format as proposed.

@trustin Would like to work on this.
In your description you have mentioned,

ClientBuildParams.uri() return a URI without the none+ prefix.

Is it to be done only for none SerializationFormat, or for all?
And if it's only for none, I am assuming it does not matter if it's armeria defaulting to none or client provided URI has none in serialization format?
I am assuming, you would like as mentioned in below tests?
    @Test
    public void nonePlusSchemePassed() {
        final HttpClient client = new ClientBuilder("none+https://google.com/").build(HttpClient.class);
        assertThat(client.uri().toString()).isEqualTo("https://google.com/");
    }

    @Test
    public void noSchemeShouldDefaultToNone() {
        final HttpClient client = new ClientBuilder("https://google.com/").build(HttpClient.class);
        assertThat(client.uri().toString()).isEqualTo("https://google.com/");
    }

@rmohta Thanks for your interest.

Is it to be done only for none SerializationFormat, or for all?

IIRC, We have decided to apply only for none.

I am assuming, you would like as mentioned in below tests?

That’s right! It would be a great.
By the way, our HTTP client don't accept URL.
https://github.com/line/armeria/blob/master/core/src/main/java/com/linecorp/armeria/client/HttpClient.java#L229
If we choose this policy, I guess creating an HTTP client from URL is more natural.
HttpClient client1 =...
URL url = client1.uri().toURL();
HttpClient client2 = HttpClient.builder(url)...build()

@trustin @minwoox WDYT?


chore: analytics event for schema fetch failure

Description

Added events for Data source schema fetch failure.

PR fixes following issue(s)
Fixes #23131
Type of change

New feature (non-breaking change which adds functionality)

How Has This Been Tested?

[x] Manual

Checklist:
Dev activity

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

QA activity:

[ ] Speedbreak features have been covered
[ ] Test plan covers all impacted features and areas of interest
[ ] Test plan has been peer reviewed by project stakeholders and other QA members
[ ] Manually tested functionality on DP
[ ] We had an implementation alignment call with stakeholders post QA Round 2
[ ] Cypress test cases have been added and approved by SDET/manual QA
[ ] Added Test Plan Approved label after Cypress tests were reviewed
[ ] Added Test Plan Approved label after JUnit tests were reviewed

/ok-to-test sha=c792740


Would you please tell me how you mix the inline img like cityscapes with the ood image like coco?

I see that you extact ood mask from coco ,and how you mix the mask with cityscapes image?

Hi @Orange-rightperson
We describe such process in the paper

, where we crop the partial image from COCO and mix (overlap) it to the inlier image (from Cityscape).
Such operation is performed in the dataloader, and in this function.

Thank you @yyliu01
Is the position where to overlap coco and mix it to de inlier image fixed? And what if the coco image shield the object in inlier image?

Hi @Orange-rightperson , it's in here!
Cheers,
Yuyuan

Thank you!


Bug/crash running Direct Display (KHR_display) programs from terminal (without Xorg)..

Hi,
I tested running 3 programs with KHR_display support and they fail..
only Vulkan program running from console is vulkaninfo works and reports correct info..
of course I'm on terminal and without Xorg server running (on grub I attach 3 to boot in terminal/console mode)..
I tested both latest v-2019.Q3.5 open release and using latest AMDVLK from AMDGPU Pro 19.30 (http://vulkan.gpuinfo.org/displayreport.php?id=6631#device)
(Pro version (driverversion : 2.0.100 ,apiversion : 1.1.113))
I'm on Ubuntu 19.04 and tested using latest included Ubuntu 19.04 kernel 5.0.xx and also latest 5.3RC from ubuntu kernel ppa (https://kernel.ubuntu.com/~kernel-ppa/mainline)just in case some AMDGPU DRM bug..
note both Vulkan drivers correctly work in Xorg (vulkaninfo,vkcube,etc..)
I tested this 3 programs (all I know :-( ):

official Khronos vkcube (https://github.com/KhronosGroup/Vulkan-Tools) compiled with cmake option:
CUBE_WSI_SELECTION STREQUAL ="DISPLAY"
vkcube from https://github.com/krh/vkcube/ which recently added KHR_display support (https://github.com/krh/vkcube/commit/504059b6af0de234981bbdb0656702af24afb316)
retroarch latest version..
For that you need to modify $HOME/.config/retroarch/retroarch.cfg with:
video_context_driver = "khr_display"
video_driver = "vulkan"

2 notes:
a) I verified this 3 programs work in console mode using KHR_display in all other Vulkan drivers I can test: with RADV, with Anvil and with NV propietary driver (I have a PC with 3 GPUs: Vega, Intel HD530 and NV Titan GPU)
b) I even tested using root mode (sudo ...) in case was an privilege/permissions issue..
Note this was a first step in my testing of supposed HDR support in direct mode of AMDVLK since latest versions..
Hope you can help..
so finally I run strace from example 2) running
./build/vkcube -m khr -k 0:0:0
it ends with both 2 AMDVLK drivers (open and propietary) with a killed by SIGSEGV ..
segment violation (core generated):
I attach 2 screenshots of strace before crash (second photo click on it for some reason it's badly rotated and upside down):
seems the error maybe because of DRM_IOCTL_PRIME_FD_TO_HANDLE returning -1..
also maybe because I'm with PC on AMD,NV and Intel GPU? I disable Intel GPU from BIOS for testing and also RADV works correctly on direct mode..
I attach also screenshot #3 which I believe is from working NV in direct mode (sorry I forgot.. I did all this testing few days ago..).. can be useful as shows my nvidia is located at /sys/ddevices/pci00000:00/000:00:01.1/<IP_ADDRESS>/drm/card1/device ..

note I check different info reported by KHR_display running all below and all data reported seems to make sense:
To list displays (monitors) :
./build/vkcube -m khr
To list modes for display 0 :
./build/vkcube -m khr -k 0
Finally to list planes for display 0 in mode 0 :
./build/vkcube -m khr -k 0:0
You can then start the vkcube on the display 0 in mode 0 on plane 0 :
./build/vkcube -m khr -k 0:0:0

Hi @oscarbg , it's working on my platform, Ubuntu18.04 with kernel 5.0.0-27, Vega10 only, libdrm 2.4.0. Probably it's caused by libdrm or multiple GPU. Could you please help to debug a little bit to see where the segfault happens to? Post the callstack will be helpful.

AMDVLK got so many issues when you have multiple GPUs....

good to know @MojoJojoDojo..
thanks @JacobHeAMD ..
no expert on Linux debugging so maybe I'm doing to much work..
I modified krh cube sample (https://github.com/krh/vkcube/) as per first answer of:
https://stackoverflow.com/questions/77005/how-to-automatically-generate-a-stacktrace-when-my-program-crashes
basically adding a signal handler as shown there..
output using AMDVLK v-2019.Q3.5 binary from github is:
Error: signal 11:
./vkcube(+0x8ebb)[0x5647584cdebb]
/lib/x86_64-linux-gnu/libc.so.6(+0x43f60)[0x7f3b8995af60]
/usr/lib/x86_64-linux-gnu/amdvlk64.so(+0x2d9367)[0x7f3b86a76367]
./vkcube(+0x6697)[0x5647584cb697] ./main.c:752
./vkcube(+0x8540)[0x5647584cd540] ./main.c:1439
./vkcube(+0x8d30)[0x5647584cdd30] ./main.c:1634
./vkcube(main+0xcf)[0x5647584cdfd1]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb)[0x7f3b8993db6b]
./vkcube(_start+0x2a)[0x5647584c987a]

I add source file and line info using:
addr2line -e ./vkcube 0x65a9 0x8540 0x8d30 0x6697
/home/cosmic/445/vkcube/build2/../main.c:747
/home/cosmic/445/vkcube/build2/../main.c:1439
/home/cosmic/445/vkcube/build2/../main.c:1634
/home/cosmic/445/vkcube/build2/../main.c:752
sadly I can't get info on amdvlk64.so as maybe compiled without debugging info:
addr2line -e /usr/lib/x86_64-linux-gnu/amdvlk64.so 0x2d9333
??:?

so from this reason program fails is in AMDVLK just called before
/home/cosmic/445/vkcube/build2/../main.c:752 ..
but not always, sometimes it fails before:
on /home/cosmic/445/vkcube/build2/../main.c:747..
main.c:747 corresponds to assert(vc->image_count > 0);
main.c:752 corresponds to assert(vc->image_count <= MAX_NUM_IMAGES);
so error must be inside AMDVLK  vkGetSwapchainImagesKHR source code..
   vkGetSwapchainImagesKHR(vc->device, vc->swap_chain,
                           &vc->image_count, NULL);
   assert(vc->image_count > 0);
   VkImage swap_chain_images[vc->image_count];
   vkGetSwapchainImagesKHR(vc->device, vc->swap_chain,
                           &vc->image_count, swap_chain_images);

   assert(vc->image_count <= MAX_NUM_IMAGES);

attach modified main so you can check exact lines:
main.zip
I assume you would want perhaps I build AMDVLK with debug info so call stack shows exact function in AMDVLK driver?
lazy to compile AMDVLK driver in debug mode but if it's needed will find time to do it..
Open to ideas to help debugging the issue..
thanks..

Yes, I need the segfault call stacks. Please help to get one with debug driver.
BTW, did you add the user into video group? You can do it with "sudo usermod -a -G video $LOGNAME" if you didn't.

@JacobHeAMD i think vkcube crashed because vkGetSwapchainImagesKHR returned an unreasonably large image count

The imageCount is specified by the application, driver just store it and return it to application in vkGetSwapchainImagesKHR. I can't see any reason why it would be 32460?
BTW, Xorg is not running, right? I ask this because "DRM_IOCTL_PRIME_FD_TO_HANDLE returning -1" which means there is no permission to do this. Please try with "root" user.

Close it since no responding from reporter.


Implement group method

Add a new type of log that allows to group logs under the same label.
Example: https://www.w3schools.com/Jsref/met_console_group.asp
Possible usage:
kittylog.group(label, isCollapsed)
...
kittylog.groupEnd(label)
Example of output (here I use native console.group method)

If you like the idea, please, assign this issure to me.

Yeah, it's a great idea! It also works in a nodejs execution?

Yes it works also in node js environment

I woud like to ask for an advise reguarding the feature in this issue.
I have implemented the basic feature of group log, everything works and I can see logs that belong to the group indented correctly.
Now I would like also to group them visually by color. My idea is that the group name should have a color assigned randomly or by user's choice and then all the logs that belong to this group to have a sign "-" (dash) of the same color.
I checked all the documentation and it seems that I can not get the group name from a log itself, so I have to keep it in a local data structure.
So I have following situation:

any log can belong to a group
there can be nested groups
every group has to have a color assigned

I was thinking about stack data structure, where every time a new console.group is called I would push the group color name and on every console.groupEnd I would pull the last group name (LIFO).
So on every log called I should check if there is anything in the stack and if so I have to add the dash of the current color.
So my questions are:

Does it make sence to implement this feature (Though I like the idea of adding colors to the groups)?
Am I thinking in the right way?
Could anyone give me an advise on how to implement this kind of global store with the group stack?

Here is the screenshot to illustrate my idea:

Hi @alexandercerutti!
Thank you so much for analyzing the issue and providing such a detailed response. Actually, the compatibility problem and the global state management problem were my biggest concerns. After reflecting on the functionality, I agree with you, and I've decided to stick with the browser implementation of this feature.
For Kittylog, I've implemented a kind of wrapper for this feature, and then the browser or Node environment will handle it.
Next will I will do the PR with my version.
It's interesting to consider the impact on CI. We should think about this scenario.
Thank you once again for your help!

@olga-demina I think @pietrodev07 will soon (if he already didn't) release a new version with a few changes about how colors are rendered. You might want to check if your PR works with them, to support CI and to not print at all the logs.
@pietrodev07 did you perhaps already release the changes? If not, did you push the branch you were working on? So @olga-demina might check them and test the changes on it.

@alexandercerutti @olga-demina I've just released changes about how colors are rendered. For now browser side and  stdout  (node)!

@pietrodev07 Good job! I've just made the reset of my repo to your new version and actually I have to make a couple of changes to my implementation of this group function.
@alexandercerutti thank you for letting me know about it!


glog_catkin error

Dear developer：
I encountered the following problems when compiling ws:
Errors     << glog_catkin:make /home/ysz/mbplanner_ws/logs/glog_catkin/build.make.000.log
/bin/sh: 1: autoreconf: not found
make[2]: *** [glog_src-prefix/src/glog_src-stamp/glog_src-configure] Error 127
make[1]: *** [CMakeFiles/glog_src.dir/all] Error 2
make: *** [all] Error 2
It seems that it can't find the fix-unused-typedef-warning.patch of GLOG. But it's in the folder.

Hi @YouShaoze,
Sorry for the late reply.
Can you specify which ubuntu and ROS distribution you are using?
Thanks,
Mihir

Hi @YouShaoze,
Sorry for the late reply.
Can you specify which ubuntu and ROS distribution you are using?
Thanks,
Mihir

Hi @YouShaoze,
After a little Googling I found the same issue faced by someone else on the glog_catkin repository here. The issue was resolved by installing autoreconf:
sudo apt install dh-autoreconf

Can you try installing it and see if it works?
Thanks,
Mihir

Hi @YouShaoze,
After a little Googling I found the same issue faced by someone else on the glog_catkin repository here. The issue was resolved by installing autoreconf:
sudo apt install dh-autoreconf

Can you try installing it and see if it works?
Thanks,
Mihir

Closing the issue since the solution is posted and it is inactive for quite some time.


Prefix's not working

in the prefix section of the config i added backend in views and nothing happened.
when i changed it in the paths it generated some wrong paths such as the following error explains

 [ErrorException]
  file_get_contents(/home/vagrant/cruds/d.crud/resources/views/backend/layouts/menu.blade.php): failed to open stream: No such file or directory

If you need to see what i mean i did this first:
/*
    |--------------------------------------------------------------------------
    | Prefixes
    |--------------------------------------------------------------------------
    |
    */
    'prefixes' => [
        'route' => '',
        'path' => '',
        'view' => 'backend',
        'public' => '',
    ],

I did this second:  both are broken.
    'path' => [
        'migration'         => base_path('database/migrations/'),
        'model'             => app_path('Models/'),
        'datatables'        => app_path('DataTables/'),
        'repository'        => app_path('Repositories/'),
        'routes'            => app_path('Http/routes.php'),
        'api_routes'        => app_path('Http/api_routes.php'),
        'request'           => app_path('Http/Requests/'),
        'api_request'       => app_path('Http/Requests/API/'),
        'controller'        => app_path('Http/Controllers/'),
        'api_controller'    => app_path('Http/Controllers/API/'),
        'test_trait'        => base_path('tests/traits/'),
        'repository_test'   => base_path('tests/'),
        'api_test'          => base_path('tests/'),
        'views'             => base_path('resources/views/backend/'),
        'schema_files'      => base_path('resources/model_schemas/'),
        'templates_dir'     => base_path('resources/infyom/infyom-generator-templates/'),
        'modelJs'           => base_path('resources/assets/js/models/'),
    ],

this issue not reproduce. same thing i did and working fine

@phillipmadsen we are not able to reproduce this issue. Maybe it's fixed since it's a very old issue. Also what I see is, in sidebar.stub the template we are using @include('layouts.menu'), so not sure why your project is loading is with prefix backend.
I'm closing this issue if you still found the issue then re-open it with some more specific instructions and steps.


HTTP implementation using tokio-minihttp

Closes #11

Issues addressed.

need merge
@rphmeier
@debris
ok to merge?


Vuestic 2.0 Pagination

I'm submitting a ...

[x] bug report

What is the current behavior?

VaPagination shows incorrect pages, when:
visiblePages > total pages

What is the expected behavior?
visiblePages should be wrapped to Math.max(visiblePages, pages)

Other information
https://github.com/epicmaxco/vuestic-admin/pull/468
https://github.com/epicmaxco/vuestic-admin/pull/468/commits/da942a8d1c3310f6fda9e88e76756cf02bdbbb7d#diff-23ec931fc86bceec4e12313c7b7bff4b

Fix will be available in 2.0.0. Thanks!


Use filename instead of name

Changed action to use the filename of the file instead the name parameter.
Added a raw example on how to run each command in the documentation.
Added a step to lint the project.
Added a test to check if the commander is properly fetching the scripts of a repository.
This resolves #22

/cmd Lint

/cmd Lint


Retain images loaded with fromDataUrl.

Plugs a small gap  with fromDataUrl and toDataUrl, allowing them to work like fromData and toData, although it doesn't populate the internal point structure so toData wont include the image, but I guess most people use either one format or the other.

closing as stale


Is there an existing issue for this?

[X] I have searched the existing issues

Have you tried to reproduce this without OP?

[X] I have tested without OP

Current Behavior
1.The particle effect of the mechanic projectile is faulty and doesn't display any particles.
2.In the mechanics particle section, two sub-items like "points" and "speed" are set by default to some fixed values. When I change the values of these two items, the particle quantity and speed don't change.
Expected Behavior
No response
Steps To Reproduce
No response
Environment
- Server Software:
- ProSkillAPI Version:1.1.12-R08
- ProMCCore Version:1.1.0-R04
- Plugins:Paper Plugins:
  - EconomyShopGUI, ProMCCore, ProRPGItems, ProSkillAPI
 Bukkit Plugins:
  - AdvancedPortals, ajLeaderboards, anticmath, AuthMe, ChatEx, Citizens, CoinsEngine, DeluxeMenus, Essentials, EssentialsSpawn
  ExcellentCrates, Factions, HoloMobHealth, InvSeePlusPlus, LeaderMobs, LibsDisguises, LiteSignIn, LuckPerms, LWC, MarketPlace
 Multiverse-Core, MythicMobs, NexEngine, PlaceholderAPI, ProEnchantmentAPI, ProEnchantmentPack, ProHolographicDisplays, ProtocolLib, RaidsPerRegion, RocketPlaceholders
 Shopkeepers, SilkSpawners, SkinsRestorer, spark, TAB, Thesieutoc, Vault, WorldEdit, WorldGuard, WorldGuardExtraFlags

latest.log
No response
Anything else?
No response

Speed likely isn't what you'd expect it to be. Some particles (like smoke, for example) have a speed that they move away from their spawning point. This isn't the speed of the projectile itself. I haven't heard any other reports lately about particles not working. I'm going to go ahead and close this. If you're still running into issues, please create a post on Discord for more of a discussion.


feature: Support passing config as JSON to trial evaluation script

Supports passing config as JSON file to training script, in local and SageMaker backend.
This needed some small fixes of SageMakerBackend as well.
The new example serves as test, because it fails if the arguments are not passed properly.
Issue: #554

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Hi Jacek, the new example serves as test, because it checks internally whether the list and dict components are properly transmitted. It is run for local backend as part of our tests. It is also run as end-2-end test with SageMaker backend, and I confirmed this works.
In fact, I had to change/fix a few things in SageMaker backend to make this work

Sure makes sense, we have integration tests but I was wondering about unit tests for individual components. I suppose if integ tests cover all the functionalities we can skip the unit tests for now.


A lot of gibberish

There are many more gibberish words than any real english

@francogrex I'm building a script to validate this list and extract only true English words you'd find in the dictionary.
Then I'm going to open source that... Once complete, it won't have every English word ever, and there might be a number of "artifacts" (such as slang, proper nouns that belong in an encyclopediam, or abbreviations), but it will be something that can be improved on.
If you're interested, I can ping you when it is ready (some time this month).

@francogrex this is simply not true.
Yes, there are too many non-words that need to be removed,
but the vast majority are valid English words.
This issue does not identify an actual problem So closing. Thanks.


chore(Dockerfile): update nginx to 1.13.4

See http://nginx.org/en/CHANGES

Codecov Report

Merging #354 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #354   +/-   ##
=======================================
  Coverage   52.75%   52.75%
=======================================
  Files           6        6
  Lines         527      527
=======================================
  Hits          278      278
  Misses        223      223
  Partials       26       26

Continue to review full report at Codecov.

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


[Feature] Take chanceTimer as a config option from client

Is your feature request related to a problem? Please describe.
Currently, the server has the chanceTimer (time after which the player chances are rotated) hardcoded in env.js. Take the value from the user and use the server value as a fallback
Additional context
This can be made more generalized by creating and populating customConfig from user which would override globalConfig, thus allowing for defaults

Update:
The issue is fixed on client-side. Only need to change here


Add retry to LightningClient when handling headless apps

What does this PR do?
We've been seeing this exception sometimes so we're adding a retry on the LightningClient instantiation when handling headless apps
This should help apps be resilient on platform releases
Credits to @alecmerdler on debugging efforts
INFO: Traceback (most recent call last):
  File "/home/zeus/.local/lib/python3.8/site-packages/lightning_launcher/launcher.py", line 255, in run_lightning_flow
    app._run()
  File "/home/zeus/.local/lib/python3.8/site-packages/lightning/app/core/app.py", line 504, in _run
    done = self.run_once()
  File "/home/zeus/.local/lib/python3.8/site-packages/lightning/app/core/app.py", line 425, in run_once
    self._update_is_headless()
  File "/home/zeus/.local/lib/python3.8/site-packages/lightning/app/core/app.py", line 532, in _update_is_headless
    _handle_is_headless(self)
  File "/home/zeus/.local/lib/python3.8/site-packages/lightning/app/utilities/app_helpers.py", line 582, in _handle_is_headless
    list_apps_response = client.lightningapp_instance_service_list_lightningapp_instances(project_id=project_id)
  File "/home/zeus/.local/lib/python3.8/site-packages/lightning_cloud/openapi/api/lightningapp_instance_service_api.py", line 665, in lightningapp_instance_service_list_lightningapp_instances
    ) = self.lightningapp_instance_service_list_lightningapp_instances_with_http_info(
  File "/home/zeus/.local/lib/python3.8/site-packages/lightning_cloud/openapi/api/lightningapp_instance_service_api.py", line 762, in lightningapp_instance_service_list_lightningapp_instances_with_http_info
    return self.api_client.call_api(
  File "/home/zeus/.local/lib/python3.8/site-packages/lightning_cloud/openapi/api_client.py", line 362, in call_api
    return self.__call_api(resource_path, method, path_params,
  File "/home/zeus/.local/lib/python3.8/site-packages/lightning_cloud/openapi/api_client.py", line 173, in __call_api
    response_data = self.request(method,
  File "/home/zeus/.local/lib/python3.8/site-packages/lightning_cloud/rest_client.py", line 81, in wrap
    raise err
  File "/home/zeus/.local/lib/python3.8/site-packages/lightning_cloud/rest_client.py", line 75, in wrap
    response = func(*args, **kwargs)
  File "/home/zeus/.local/lib/python3.8/site-packages/lightning_cloud/openapi/api_client.py", line 388, in request
    return self.rest_client.GET(url,
  File "/home/zeus/.local/lib/python3.8/site-packages/lightning_cloud/openapi/rest.py", line 249, in GET
    return self.request("GET",
  File "/home/zeus/.local/lib/python3.8/site-packages/lightning_cloud/openapi/rest.py", line 239, in request
    raise ApiException(http_resp=r)
lightning_cloud.openapi.rest.ApiException: (502)
Reason: Bad Gateway
HTTP response headers: HTTPHeaderDict({'Content-Type': 'text/html; charset=UTF-8', 'Referrer-Policy': 'no-referrer', 'Content-Length': '332', 'Date': 'Fri, 03 Feb 2023 11:57:57 GMT', 'Alt-Svc': 'h3=":443"; ma=2592000,h3-29=":443"; ma=2592000'})
HTTP response body: b'\n\n<meta http-equiv="content-type" content="text/html;charset=utf-8">\n<title>502 Server Error</title>\n\n\n
Error: Server Error
\n
The server encountered a temporary error and could not complete your request.
Please try again in 30 seconds.
\n

\n\n'

Before submitting

[ ] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[ ] Did you read the contributor guideline, Pull Request section?
[ ] Did you make sure your PR does only one thing, instead of bundling different changes together?
[ ] Did you make sure to update the documentation with your changes? (if necessary)
[ ] Did you write any new necessary tests? (not for typos and docs)
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] Did you list all the breaking changes introduced by this pull request?
[ ] Did you update the CHANGELOG? (not for typos, docs, test updates, or minor internal changes/refactors)

cc @borda

#16382 didn't get released yet. So this PR is not necessary on top of it and the next version release will address this.

The change that flipped the default to True was released last week #16382. Since there hasn't been any activity, I'm closing the PR. If it was a mistake, let me know.


fix(auth, web): get auth credential from exception and pass to user if one is available

Description
I tested this with user's example and it worked as intended. The JS error is correctly parsed and instantiated as a Dart credential if it exists. If not, null is passed as credential which is a nullable argument on FirebaseAuthException:
final AuthCredential? credential;

Related Issues
fixes https://github.com/firebase/flutterfire/issues/12771
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process. Updating the pubspec.yaml and changelogs is not required.

[ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[ ] All existing and new tests are passing.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] The analyzer (melos run analyze) does not report any problems on my PR.
[ ] I read and followed the Flutter Style Guide.
[ ] I signed the CLA.
[ ] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change.
[ ] No, this is not a breaking change.

Waiting for this PR to be merged, thanks @russellwheatley .


nexmo.sendSms Latency:946754 ms  ？？？！！！

I got the sms after about 20 minutes
here is my code:
const Nexmo = require('nexmo')

const nexmo = new Nexmo({
  apiKey: "4cfa19xx",
  apiSecret: "QMugxxxp1oxxxhZw"
})

const from = 'water'
const to = '861366xxx1790'
const text = 'water???'
console.log("new date",new Date())
nexmo.message.sendSms(from, to, text,{},function(err,rst){
	console.log("err",err)
	console.log("rst",rst)
})

response
new date 2018-09-27T02:43:39.838Z
err null
rst { 'message-count': '1',
  messages:
   [ { to: '861366xxx1790',
       'message-id': '0E000000C889DF7B',
       status: '0',
       'remaining-balance': '1.91540000',
       'message-price': '0.02820000',
       network: '46000' } ] }

Is there any way to solve this problem？？

another question

I sent a total of 13 messages to two phones today, but only received eight

This feels like it's an issue with routing and not the node library. Can you please log a support request to<EMAIL_ADDRESS>

I have contacted the customer service to solve this problem, thanks so much~ (～￣▽￣)~


Black Side bar improvement

The text edit to be replaced by arrow pointer
The options to be made more visually visible

The client does not need it anymore


What should the edge_index be for a single node graph?

❓ Questions & Help
Hi, I'm using PyG to deal with molecules. What if I only have one atom, i.e. one node, so there will be no edge, and what should the edge_index be?

Simply create an empty tensor:
torch.tensor(2, 0, dtype=torch.long)

Simply create an empty tensor:
torch.tensor(2, 0, dtype=torch.long)

Oh, that's convienent. Thank you!

Oh, that's convienent. Thank you!


Can click below

Hi,
Thanks for this crate, it's very easy to implement.
I do have an issue though, when the toast appears, I can stii click through to the widgets that are underneeth. Is there a way to make the toast "opaque" to i don't accedently click the buttons below?
thanks

I'm honestly not quite sure how this can be fixed. consume_key may be useful. Where Toasts instance is being shown, it can detect when click happened on top of a toast and consume it, but that obviously would only work if Toasts is being drawn before anything else.


bugfix:权限模型修改

Codecov Report

Merging #65 (6a6227f) into v2.6.x_develop (3dcc40a) will not change coverage.
The diff coverage is n/a.

@@               Coverage Diff               @@
##           v2.6.x_develop      #65   +/-   ##
===============================================
  Coverage           51.31%   51.31%
===============================================
  Files                 692      692
  Lines               36549    36549
===============================================
  Hits                18755    18755
  Misses              17794    17794

Continue to review full report at Codecov.

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


Erased 3vicn compositions

Codecov Report

Merging #11 (24990d3) into main (dc12a32) will increase coverage by 4.76%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #11      +/-   ##
==========================================
+ Coverage   50.00%   54.76%   +4.76%
==========================================
  Files          14       11       -3
  Lines          46       42       -4
==========================================
  Hits           23       23
+ Misses         23       19       -4

Impacted Files
Coverage Δ

src/constraint.jl
92.30% <100.00%> (+0.64%)
:arrow_up:

Continue to review full report at Codecov.

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

Codecov Report

Merging #11 (24990d3) into main (dc12a32) will increase coverage by 4.76%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #11      +/-   ##
==========================================
+ Coverage   50.00%   54.76%   +4.76%
==========================================
  Files          14       11       -3
  Lines          46       42       -4
==========================================
  Hits           23       23
+ Misses         23       19       -4

Impacted Files
Coverage Δ

src/constraint.jl
92.30% <100.00%> (+0.64%)
:arrow_up:

Continue to review full report at Codecov.

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


[Backstage] Remove travis and make changes to use github actions

dojot/dojot#1913

Remove folder src/travis

Please, add upload coverage to Codecov


Card subtitle and tooltip (2)

Modifies the card subtitle for the AWS, OCP, and OCP on AWS overview pages. This also adds a tooltip to the subtitle, showing the date range on hover.
Note: This builds upon https://github.com/project-koku/koku-ui/pull/679, which must be merged first.
Mock: https://redhat.invisionapp.com/share/HEO4ISHAT8Z#/screens/352926694
Fixes https://github.com/project-koku/koku-ui/issues/654

Codecov Report

Merging #680 into master will increase coverage by 0.1%.
The diff coverage is 76.04%.

@@            Coverage Diff            @@
##           master     #680     +/-   ##
=========================================
+ Coverage   79.73%   79.84%   +0.1%
=========================================
  Files         219      219
  Lines        3336     3359     +23
  Branches      532      540      +8
=========================================
+ Hits         2660     2682     +22
+ Misses        602      599      -3
- Partials       74       78      +4

Impacted Files
Coverage Δ

src/store/ocpDashboard/ocpDashboardCommon.ts
95.65% <ø> (ø)
:arrow_up:

...tore/ocpOnAwsDashboard/ocpOnAwsDashboardWidgets.ts
100% <ø> (ø)
:arrow_up:

src/store/awsDetails/awsDetailsCommon.ts
52.63% <ø> (ø)
:arrow_up:

src/store/ocpOnAwsDetails/ocpOnAwsDetailsCommon.ts
52.38% <ø> (ø)
:arrow_up:

src/store/awsDashboard/awsDashboardWidgets.ts
100% <ø> (ø)
:arrow_up:

...eports/ocpReportSummary/ocpReportSummary.styles.ts
100% <ø> (ø)
:arrow_up:

...portSummary/ocpOnAwsReportSummaryDetails.styles.ts
100% <ø> (ø)
:arrow_up:

...wsReportSummary/ocpOnAwsReportSummaryAlt.styles.ts
100% <ø> (ø)
:arrow_up:

...rts/awsReportSummary/awsReportSummaryAlt.styles.ts
100% <ø> (ø)
:arrow_up:

...ocpReportSummary/ocpReportSummaryDetails.styles.ts
100% <ø> (ø)
:arrow_up:

... and 22 more

Continue to review full report at Codecov.

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

LGTM :+1:


Potential bug with 0.6.0 shared storage_context and vector store retrieval

Hey friends!
There's a very good chance that I'm misunderstanding the philosophy with this new refactor, but if I'm not, there may be a bug with how the vector store retriever works.
My understanding is that the storage context is something we can pass to multiple indices to reuse nodes and vectors (coo coo, very nice). However, looking at the retrieval method for the vector stores, there's nothing preventing a node that exists in different indices to be picked up as the closest match (https://github.com/jerryjliu/llama_index/blob/c5d8768f5d0e5789e977c474457b2634f452957e/gpt_index/indices/vector_store/retrievers.py#L73)
Should there exist a node level check to ensure that the specific nodes exist for that given index? From what I gather, there's a filter on the document level, but if a document was parsed differently for different indices, these nodes would have different node ids with the same document id?
This would lead to errors such as:
     78     raise ValueError(
     79         "Vector store query result should return at "
     80         "least one of nodes or ids."
     81     )
     82 assert isinstance(self._index.index_struct, IndexDict)
---> 83 node_ids = [
     84     self._index.index_struct.nodes_dict[idx] for idx in query_result.ids
     85 ]
     86 nodes = self._docstore.get_nodes(node_ids)
     87 query_result.nodes = nodes

File ~/miniconda3/lib/python3.10/site-packages/llama_index/indices/vector_store/retrievers.py:84, in <listcomp>(.0)
     78     raise ValueError(
     79         "Vector store query result should return at "
     80         "least one of nodes or ids."
     81     )
     82 assert isinstance(self._index.index_struct, IndexDict)
     83 node_ids = [
---> 84     self._index.index_struct.nodes_dict[idx] for idx in query_result.ids
     85 ]
     86 nodes = self._docstore.get_nodes(node_ids)
     87 query_result.nodes = nodes

KeyError: '9e513d49-4c87-49f1-ba2f-ef9003529145'```

Adding to this. This impacts every shared storage context with simple vector stores.
I realized that the vector store retriever doesn't know how to pull the doc ids, beyond that the simple vector store doesn't even consider the doc_ids passed to the VectorStoreQuery object (https://github.com/jerryjliu/llama_index/blob/c5d8768f5d0e5789e977c474457b2634f452957e/gpt_index/vector_stores/simple.py#L113)

Thanks for flagging, this is a great point.
Yeah I think at the moment we get around this by instantiating a "new" DocumentStore in StorageContext.from_defaults if persist_dir is None (so if you create multiple vector stores and don't specify persist_dir, then you can avoid this problem).
However if you do specify persist_dir, then simple vector stores may have this problem. This is a TODO for us to add namespace support cc @Disiok

I'm facing the same problem. I'm looking for the update

This is not a fix, but you can make each sub index and save it on its own, and then create the graph on the fly when needed. Not an ideal solution, but it works for now

For me, I have each index saved on a different persist_dir. I can query each index and it works just fine. But after I add_nodes to an index loaded from storage, then query again, I got the error

@Disiok @jerryjliu any chance this was fixed recently? Reading through the commits, can’t see anything specific to this

There's an initial fix (more of a bandaid for now). We pass the list of node ids from the vector index to the retriever, so it knows which subset of nodes.

    def as_retriever(self, **kwargs: Any) -> BaseRetriever:
        # NOTE: lazy import
        from llama_index.indices.vector_store.retrievers import VectorIndexRetriever

        return VectorIndexRetriever(
            self, doc_ids=list(self.index_struct.nodes_dict.values()), **kwargs
        )

(in case others are wondering as I was) the PR seems to be #3695


Update python

Sadly this release is no longer building for some reason.  Even when pointed to master.  🤕

Oh lovely: https://github.com/cloudfoundry/bosh-cli/issues/476


Can not enable NPU surpport in Chrome Canary

I run WebNN on NPU in Edge Dev is OK, but in Chrome Canary is not OK by WebNN Installation Guides' steps, thoses sample's NPU button is still disable, anybody have same problems?
Chrome version: 130.0.6700.0 canary
directML version: 1.15.2
NPU: Intel AI Boost Driver Version: <IP_ADDRESS>0
Thank You!

May I know what is the error message you got?
The installation guide has been updated including steps for Chrome Canary: https://github.com/webmachinelearning/webnn-samples?tab=readme-ov-file#running-webnn-on-npu
At the current stage, devs need to copy the DirectML.dll to Chrome Canary's version folder.

Note that Chrome Canary frequently updates automatically. When this occurs, you'll need to recopy the DirectML.dll to the new version's directory


Update the embeddings

Hi,
I'm using the library to perform k-NN search. However, I have to regularly update the associated embeddings.
Is this possible? What's the optimal way to do it?
I'm using python.

Hi @Stamatios-Korres
It is possible. If you add an element with the same label, it will be updated (the previous element will be no longer present).
Though note that this operation is pretty expensive(several times more expensive than adding an element), so I would consider rebuilding the index from scratch in some situations.

@yurymalkov I have similar requirements as well since i have a pipeline where we receive embeddings in a streaming online way. Is my understanding correct that this approach is equivalent to deleting and re-adding the element with updated embedding or are there some internal implementation detail based caveats .
I am wondering about a scenario where my embedding generation model gets updated and starts producing new embedding for lot of my documents , in this case if i always do incremental updates (either update operation or delete + add operation) , does that change my graph structure or result quality as opposed to doing a full batch rebuild of index ?

@patelprateek inserting new element with existing id (=updating) changes the graph structure. Infinite number of updates are possible without loss of performance, but the operation is pretty costly.
An alternative is manual marking of the element as deleted (without) and inserting a new element leads to some performance degradation  with infinite updates, but a single operation is less costly. Batched rebuild from time to time can fix the issues with degradation.
If the complexity of updates is not a problem, I'd use the first option. If it is, I'd look into the second option, though it requires more complicated maintenance.


delete specific slack link

edited README so we do not need to change it for every code academy we run.

#2


Add Flink read/write operations to FlinkExecutionContext

In order to add all functionality to the (CSV)ReblockFLInstructions we need at least writeDataSetToHDFS(...) and toMatrixBlock(...) methods in FlinkExecutionContext (see SparkExecutionContext methods for reference).
These are used in MatrixObject.readMatrixFromDataSet(...) which is used by MatrixObject.aquireRead().

[x] toMatrixBlock(DataSetObject dso, int rlen, int clen, int brlen, int bclen, long nnz)
[x] toMatrixBlock(DataSet<Tuple2<MatrixIndexes, MatrixBlock>> ds, int rlen, int clen, int brlen, int bclen, long nnz)
[ ] writeDataSetToHDFS(DataSetObject dso, String path, OutputInfo oinfo)

I implemented writeDataSetToHDFS for you since it is really similar to what I did in writing BinaryBlocks in WriteFLInstruction


Scrambled UI when starting Emacs under WSLg. Clears when I wsl --shutdown and try again.

Start Emacs.
Sometimes I see this scrambled UI

If I select in the window with the mouse, the scramble momentarily goes away and is replaced with the correct view, but quickly returns.
Emacs is responsive to keyboard input, but I can't see what I'm doing.

Stop WSL with wsl --shutdown
Start Emacs

WSL logs:
20240212-eb-4993-logs.zip
WSL dumps:
No response
Expected behavior:
Emacs shows
Actual behavior:
Emacs is scrambled

This is fixed by https://github.com/microsoft/WSL/releases/tag/2.1.1.


Update active-directory-devquickstarts-angular.md

made it clear when the user is configuring the front end vs the back end

@fchiachiere,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@fchiachiere : Thanks for your contribution to the Azure documentation! The author, @dstrockis, has been notified to review your proposed change.

#sign-off


chore(package): bump dev dependencies

Description
Bump dev dependencies
Motivation and Context

How has this been tested?

Types of changes

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

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

Coverage remained the same at 98.86% when pulling 60e52c8dd877aec99279e3294df8c538b451a926 on dev-deps into e81a93dea54a83caaac2da65a0bdd4e03457a6a3 on master.


[Bugfix][Op] Fix shape inference of adv_index

Current adv_index will fail the simple case for it does not broadcast the shapes of indices:
# data - (2, 2)
# ind0 - (1, 2)
# ind1 - (2, 1)
adv_index(data, ind0, ind1)

@yzhliu @comaniac

Can you also check if this fixes the issue in https://github.com/apache/tvm/issues/9237?

Can you also check if this fixes the issue in #9237?

it not fix that, that issue is about boolean index, see https://github.com/apache/tvm/pull/7373
I agree that we can add boolean indices support for adv_index

Another question, can the failed CI be retry?

The CI has been dead since the last weekend. Please wait until it is back.

@hgt312 can you push and trigger CI again?

@hgt312 can you push and trigger CI again?

rebased

waiting for the CI issue fixed...

Please kick another CI job.

@masahi rebased

Thanks @hgt312 @masahi @junrushao1994


[UBS]Add validation to Eco Numbers

Add validate to Eco Numbers in method updateOrderAdminPageInfo.
The format of the number is 10 numeric characteristics.
Changes

Not relevant


The release page is not updated

Hi,
the release page is not updated with unity released version.
https://github.com/unitycontainer/unity/releases
with What’s New.
also it will benefit in downloading the .dlls, as nuget download is very slow in my area.
as seen here in EF, release page:
https://github.com/aspnet/EntityFramework/releases
Regards.

Yes! I agree that the info page could be more complete and engaging, showcasing the work that has been complete (perhaps with a "whats new"/"changelog") and the work that is being developed! A roadmap would be nice, along with expected release dates...

Hi,
We're working to publish a CoreClr-compatible version soon. It will come with the release notes too.
Thanks for the patience.


Ensure endCursor is NULL when hasNextPage is FALSE in GraphQL response

Why make this change?
Closes https://github.com/Azure/data-api-builder/issues/2030
Closes https://github.com/Azure/data-api-builder/issues/2130
Fixes a bug where we would have a non null endCursor in GraphQL responses, despite hasNextPage being false. In other words, providing a bookmark to the next page of results when no such page exists.
And also, when we do not include hasNextPage but we are still on the last page, endCursor should be null.
What is this change?
We now check if we have an extra element or not before we create the endCursor. We define having a next page of results as having an extra element in the result set that is returned from our query. This is because when we make a paginated query we add 1 to our limit, that way we can tell if there is another page of results based on if that extra element returns or not. We now include this logic if either hasNextPage, or endCursor is in the request so that we will correctly follow the logic for any pagination scenario. That means adding 1 to the limit and checking if there is another page of records beyond the number in the request.
How was this tested?
Updated the pagination tests to have null endCursor expected when hasNextPage is false.
Added cases to the RequestAfterTokenOnly test cases to include both being on the final page and not, this verifies we get a correctly built non null and correctly built null endCursor for those respective cases.
Sample Request(s)
{
	reviews(first: 2, after: "W3siRW50aXR5TmFtZSI6IlJldmlld3MiLCJGaWVsZE5hbWUiOiJib29rX2lkIiwiRmllbGRWYWx1ZSI6MSwiRGlyZWN0aW9uIjowfSx7IkVudGl0eU5hbWUiOiJSZXZpZXdzIiwiRmllbGROYW1lIjoiaWQiLCJGaWVsZFZhbHVlIjo1NjcsIkRpcmVjdGlvbiI6MH1d") {
		items {
			id
            content
        }
        hasNextPage
        endCursor
    }
}

Before the fix, this request would result in a response that would include an endCursor to a page that does not exist.
  "data": {
    "reviews": {
      "items": [
        {
          "id": 568,
          "content": "I loved it"
        },
        {
          "id": 569,
          "content": "best book I read in years"
        }
      ],
      "hasNextPage": false,
      "endCursor": "W3siRW50aXR5TmFtZSI6IlJldmlldyIsIkZpZWxkTmFtZSI6ImJvb2tfaWQiLCJGaWVsZFZhbHVlIjoxLCJEaXJlY3Rpb24iOjB9LHsiRW50aXR5TmFtZSI6IlJldmlldyIsIkZpZWxkTmFtZSI6ImlkIiwiRmllbGRWYWx1ZSI6NTY5LCJEaXJlY3Rpb24iOjB9XQ=="
    }
  }
}

W3siRW50aXR5TmFtZSI6IlJldmlldyIsIkZpZWxkTmFtZSI6ImJvb2tfaWQiLCJGaWVsZFZhbHVlIjoxLCJEaXJlY3Rpb24iOjB9LHsiRW50aXR5TmFtZSI6IlJldmlldyIsIkZpZWxkTmFtZSI6ImlkIiwiRmllbGRWYWx1ZSI6NTY5LCJEaXJlY3Rpb24iOjB9XQ== decodes to [{"EntityName":"Review","FieldName":"book_id","FieldValue":1,"Direction":0},{"EntityName":"Review","FieldName":"id","FieldValue":569,"Direction":0}] and if we look at the data in our table we can see that an endCursor that indicates the next page of data starts after id=569 will not be providing a link to a page at all as there are no more records after id=569

After adding this fix we can see that instead we will have a null endCursor, as expected
  "data": {
    "reviews": {
      "items": [
        {
          "id": 568,
          "content": "I loved it"
        },
        {
          "id": 569,
          "content": "best book I read in years"
        }
      ],
      "hasNextPage": false,
      "endCursor": null
    }
  }
}

Similar behavior can be seen for only request an endCursor but not including hasNextPage. If you simply remove hasNextPage from the above requests, you will see the same inconsistent behavior before the fix, and the same consistency now after the fix.
So looking at the request
{
	reviews(first: 2, after: "W3siRW50aXR5TmFtZSI6IlJldmlld3MiLCJGaWVsZE5hbWUiOiJib29rX2lkIiwiRmllbGRWYWx1ZSI6MSwiRGlyZWN0aW9uIjowfSx7IkVudGl0eU5hbWUiOiJSZXZpZXdzIiwiRmllbGROYW1lIjoiaWQiLCJGaWVsZFZhbHVlIjo1NjcsIkRpcmVjdGlvbiI6MH1d") {
		items {
			id
            content
        }
        endCursor
    }
}

Before the fix we would see
  "data": {
    "reviews": {
      "items": [
        {
          "id": 568,
          "content": "I loved it"
        },
        {
          "id": 569,
          "content": "best book I read in years"
        }
      ],
      "endCursor": "W3siRW50aXR5TmFtZSI6IlJldmlldyIsIkZpZWxkTmFtZSI6ImJvb2tfaWQiLCJGaWVsZFZhbHVlIjoxLCJEaXJlY3Rpb24iOjB9LHsiRW50aXR5TmFtZSI6IlJldmlldyIsIkZpZWxkTmFtZSI6ImlkIiwiRmllbGRWYWx1ZSI6NTY5LCJEaXJlY3Rpb24iOjB9XQ=="
    }
  }
}

But after the fix we have
  "data": {
    "reviews": {
      "items": [
        {
          "id": 568,
          "content": "I loved it"
        },
        {
          "id": 569,
          "content": "best book I read in years"
        }
      ],
      "endCursor": null
    }
  }
}

can you show example of contents of last page before and after your change?

/azp run

/azp run

/azp run

/azp run

for your pr description:

We not include this logic if either hasNextPage, or endCursor is in the request so that we will correctly follow the logic for any pagination scenario.

do you mean that "this logic" for adding to the limit() value is excluded when both hasNextPage and endCursor are excluded from the GraphQL request?
Does this change look to affect REST API at all, with your latest commits?
Would be good to include a copy/paste of the example request/response for this:

Similar behavior can be seen for only request an endCursor but not including hasNextPage. If you simply remove hasNextPage from the above requests, you will see the same inconsistent behavior before the fix, and the same consistency now after the fix.

/azp run

for your pr description:

We not include this logic if either hasNextPage, or endCursor is in the request so that we will correctly follow the logic for any pagination scenario.

do you mean that "this logic" for adding to the limit() value is excluded when both hasNextPage and endCursor are excluded from the GraphQL request?

Yes, I added that to the PR description now to be more clear.

Does this change look to affect REST API at all, with your latest commits?

No. Nothing on the REST side is changing.

Would be good to include a copy/paste of the example request/response for this:

Similar behavior can be seen for only request an endCursor but not including hasNextPage. If you simply remove hasNextPage from the above requests, you will see the same inconsistent behavior before the fix, and the same consistency now after the fix.

Included!

/azp run

/azp run

/azp run

/azp run

connection issue caused test to fail, re-running

/azp run


Spyder crashes with segmentation fault on startup in Anaconda 4.5.0

DEVELOPER NOTE: This error is now fixed in Spyder >= 3.3.0. To resolve it, please update to the current version with conda update spyder from the Anaconda Prompt/Terminal/command line, which also fixes other bugs and adds new features, enhancement and usability/documentation improvements. Thanks!
Hi,
after updating Spyder on Anaconda it crashes on startup. The splash screen shows up before terminating with a segmentation fault. It can be reproduced in a minimal Anaconda environment with:
# Create minimal environment:
~$ conda --version
conda 4.5.0
~$ conda create --name tst
~$ conda activate tst
~$ conda install spyder
~$ rm -rf ~/.config/spyder-py3
~$ SPYDER_DEBUG="3" spyder --reset
*** Reset Spyder settings to defaults ***
removing: /home/brunn/.config/spyder-py3/spyder.ini
removing: /home/brunn/.config/spyder-py3/langconfig

# Run spyder:
~$ SPYDER_DEBUG="3" spyder
Start of MainWindow constructor
End of MainWindow constructor
*** Start of MainWindow setup ***
  ..core actions
  ..toolbars
  ..tools
  ..sift?
  ..plugin: internal console
    ..internal console: initializing
  ..plugin: working directory
Loading help...
Loading outline explorer...
Loading editor...
Introspection Plugin Loaded: rope
Introspection Plugin Loaded: jedi
Introspection Plugin Loaded: fallback
setfocusto: <spyder.widgets.sourcecode.codeeditor.CodeEditor object at 0x7f99901c3948>
current_changed: 0 <spyder.widgets.sourcecode.codeeditor.CodeEditor object at 0x7f99901c3948><PHONE_NUMBER>92616
Added thread <spyder.widgets.editor.AnalysisThread object at 0x7f9990155ee8> to queue
Added thread <spyder.widgets.editor.AnalysisThread object at 0x7f9990155f78> to queue
  ..widgets
Loading file explorer...
Loading history plugin...
Loading online help...
Loading project explorer...
Updating queue:
    started: 0
    pending: 2
===>starting: <spyder.widgets.editor.AnalysisThread object at 0x7f9990155ee8>
Updating queue:
    started: 1
    pending: 1
===>starting: <spyder.widgets.editor.AnalysisThread object at 0x7f9990155f78>
Loading namespace browser...
Updating queue:
    started: 0
    pending: 0
Updating queue:
    started: 0
    pending: 0
Loading IPython console...
Setting up main window...
Setting up window...
*** End of MainWindow setup ***
Speicherzugriffsfehler (means: segmentation fault)

I'm not quite sure how to continue debugging. Investigating the core dump did not yield in any results.
I'm using Debian unstable. The conda package info returns:
spyder 3.2.8 py36_0
-------------------
file name   : spyder-3.2.8-py36_0.tar.bz2
name        : spyder
version     : 3.2.8
build string: py36_0
build number: 0
channel     : https://repo.anaconda.com/pkgs/main/linux-64
size        : 2.6 MB
arch        : None
constrains  : ()
license     : MIT
md5         : 9ad003181d3ce2134a6f024b86a2cdab
platform    : None
subdir      : linux-64
timestamp   :<PHONE_NUMBER>360
url         : https://repo.anaconda.com/pkgs/main/linux-64/spyder-3.2.8-py36_0.tar.bz2
dependencies:
    chardet >=2.0
    cloudpickle
    jedi >=0.9
    nbconvert
    numpydoc
    pickleshare
    psutil
    pycodestyle
    pyflakes
    pygments >=2.0
    pylint
    pyqt
    python >=3.6,<3.7.0a0
    pyzmq
    qtawesome >=0.4.1
    qtconsole >=4.2
    qtpy >=1.2.0
    rope >=0.9.4
    sphinx

What are your Qt and PyQt versions?

I had the same problem (after pyqt updates Spyder crashed on startup or when I tried to resize windows). Downgrading pyqt to 5.6.0 solved the issue for me.

@ccordoba12 After installing Spyder into a fresh environment on my clean test Win 10 machine with Qt/PyQt 5.9, I also got a crash on launch, while it worked just fine in a 5.6 environment on the same machine.`

This is really bad! I thought things were working fine for PyQt 5.9 on Windows.
@CAM-Gerlach, could you post the output of conda list in your environment? Thanks!

@ccordoba12 Actually, good news and bad news. When I created another new environment on my test machine with Spyder and Qt 5.9, everything worked just fine. It seems the one non-Spyder additional package I'd installed in that env, the pandas soft-dependency feather-format to read feathered data frames, downgraded qt/pyqt to 5.6.2/5.6 which completely broke Spyder to the point it would crash almost instantly on launch to a "Python has stopped working" before even printing the first debug message. Ironically, upgrading back to 5.9.4/5.9.2 got Spyder working again.

Attached is a backtrace generated with:
$ gdb /home/brunn/anaconda3/envs/tst/bin/python
...
(gdb) run
Starting program: /home/brunn/anaconda3/envs/tst/bin/python
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Python 3.6.5 |Anaconda, Inc.| (default, Mar 29 2018, 18:21:58)
...
>>> from spyder.app.start import main
>>> main()
...
Thread 1 "ZMQbg/5" received signal SIGSEGV, Segmentation fault.
0x0000000000000000 in ?? ()
(gdb) bt

Following a suggestion in #3326, I was able to work around the problem by doing
conda install pyopengl

This problem is also addressed in PR #7029. Thanks.

Thanks folks! I have the same issue and fixed it by installing opengl.
One reminder: Be sure to do this for all your environments.

Same issue for me, installing pyopengl solved the issue.

Just to add, same behavior and solution on my Fedora 28 VM.

By doing conda install pyopengl solve my problem on ubuntu 18.04

Also, just FYI, Spyder 3.3 (out in a week or so) has a built-in workaround for the issue so you won't need to install OpenGL and should avoid these segfaults.

Have a low-end AMD/Radeon DELL laptop that has the same problem, Anaconda3-5.2.0 on Ubuntu 18.04.
Installing pyopengl via conda fixed it
Strange thing is I have an Intel/Nvidia DELL tower running Anaconda3-5.2.0 on Ubuntu 18.04 with no issue.

added / updated specs:
- pyopengl
The following packages will be downloaded:
package                    |            build
---------------------------|-----------------
pyopengl-3.1.1a1           |      np113py36_0         1.1 MB
numpy-1.13.3               |   py36hdbf6ddf_4         3.9 MB
freeglut-2.8.1             |                0         554 KB
------------------------------------------------------------
                                       Total:         5.6 MB

The following NEW packages will be INSTALLED:
freeglut: 2.8.1-0
pyopengl: 3.1.1a1-np113py36_0

The following packages will be REMOVED:
anaconda: 5.2.0-py36_3

The following packages will be DOWNGRADED:
numpy:    1.14.3-py36hcd700cb_1 --> 1.13.3-py36hdbf6ddf_4

Could have been different drivers on the machine...I had the same issue, except on a laptop with an Intel (3630QM) and Intel (HD4000)/Nvidia (GTX 670M) setup.

Have a high-end NVIDIA HP OMEN 15-CE072TX laptop that has the same problem, Anaconda3-5.2.0 on Ubuntu 18.04.
Installing pyopengl via conda fixed it
fire command in terminal:- conda install pyopengl
The following packages will be downloaded:

package
build

pyopengl-3.1.1a1
np113py36_0         1.1 MB

numpy-1.13.3
py36hdbf6ddf_4         3.9 MB

freeglut-2.8.1
0         554 KB

                                   Total:         5.6 MB

The following NEW packages will be INSTALLED:
freeglut: 2.8.1-0
pyopengl: 3.1.1a1-np113py36_0
The following packages will be REMOVED:
anaconda: 5.2.0-py36_3
The following packages will be DOWNGRADED:
numpy:    1.14.3-py36hcd700cb_1 --> 1.13.3-py36hdbf6ddf_4

I got the same error on a fresh installation of Anaconda 3.6 on Ubuntu 18.04.01. It was a clean install without any modifications done to it.

Seems like this isn't resolved yet?

Things are solved now in Spyder 3.3.0 without the need of pyopengl. Since that version is not included in the latest Anaconda, you have to update to it with conda update spyder.

Hi everyone!
I've been facing the same issue:
Traceback (most recent call last):
File "/home/usr/anaconda2/envs/py36/lib/python3.6/site-packages/qtpy/QtWebEngineWidgets.py", line 22, in
from PyQt5.QtWebEngineWidgets import QWebEnginePage
ImportError: libGLdispatch.so.0: cannot open shared object file: No such file or directory
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/usr/anaconda2/envs/py36/bin/spyder", line 11, in
sys.exit(main())
File "/home/usr/anaconda2/envs/py36/lib/python3.6/site-packages/spyder/app/start.py", line 190, in main
from spyder.app import mainwindow
File "/home/usr/anaconda2/envs/py36/lib/python3.6/site-packages/spyder/app/mainwindow.py", line 92, in
from qtpy import QtWebEngineWidgets # analysis:ignore
File "/home/usr/anaconda2/envs/py36/lib/python3.6/site-packages/qtpy/QtWebEngineWidgets.py", line 26, in
from PyQt5.QtWebKitWidgets import QWebPage as QWebEnginePage
ModuleNotFoundError: No module named 'PyQt5.QtWebKitWidgets'
I'm working in linux Ubuntu 16.04. I've Nvidia grapphic card too.
I've been searching and trying many different suggestion like:

install pyopengl in my anaconda envs : py 3.5 and py3.6

checking the followed lines in /spyder/app/start.py
import ctypes
ctypes.CDLL("libGL.so.1", mode=ctypes.RTLD_GLOBAL)
from OpenGL import GL

All was OK, but spyder didn't launch ....

Finally,  I solved my problem downgrading pyqt to 5.6.0 in my anaconda env.

I hope it helps to someone else!

@debpol It may be related (both OpenGL) but this doesn't appear to be the exact same issue, since this one is about a segmentation fault (i.e. C==/Qt level problem) on startup while you are describing a Python-level exception, and the confirmed solution to the particular problem in this thread was either conda install pyopengl, or (now) upgrading to Spyder >=3.3.0.
Most likely, this sounds like an OS, Qt, or install-specific issue. What specific version of Spyder, Qt, PyQt, and Python were you running when they happened under PyQt 5.9? Try updating Spyder in place if it is <3.3.0, and creating a fresh environment for Spyder (conda create -n name-your-env python=3.6, then source activate name-your-env), and installing Spyder there (conda install spyder). Also, a potential source of problems is using Anaconda2 with Python 3 environments; it is a much better idea to use Anaconda3 and then create a Py2 env if you need it (I've tested Spyder in Py2 environments on Anaconda3 a number of times, and never had a problem). Finally, please try the steps listed in the Spyder Troubleshooting Guide, specifically the Basic First Aid and Emergency CPR sections, which resolve most common install issues. Thanks!

Ubuntu 18.04 this issue can be resolved by either conda install pyopengl or update spyer version 3.3.1 by conda update spyder

@vollbier thank you very much. this worked for me.
I am using windows linux subsystem. ubuntu 18 from Microsoft store
Anaconda >> python 3.6.
All working file

conda install pyopengl fixed the problem, thanks!

@AlcaArctica update spyder to latest version and the problem will be solved

Yeah, no need of pyopengl.

@ccordoba12 I put a disclaimer at the top of the thread, so hopefully that'll finally help stem the tide of people installing pyopengl (and presumably not updating to the latest version of Spyder).

..should have read it more carefully. Thanks!

@debpol
Using Spyder 3.3.1, python 2.7, and Anaconda 4.5.11
The SegFault issues persists when installing Anaconda in a Python 2.7 environment. debpol's solution of downgrading PyQT to 5.6.0 is what resolved the issue for me.

What worked for me:
Uninstalled: PyOpenGL
Installed:    Spyder 3.3.1    &   QT 5.9.6   &    PyQT 5.9.2
With the 5.6 versions of qt and pyqt I had the 'segmentation fault (core dumped)' error.
I'm using python 2.7, anaconda 4.5.11, Ubuntu 16.04

I install opencv in anaconda and I think my Pyqt is downgrade after that so I update my pyqt and my spyder back to stage:) thanks @albertigno

conda update pyqt solved the problem for me

You can all also try updating to PyQt 5.9, unless you have something else in your environment blocking it (conda install pyqt=5.9 qt=5.9).

Thank you! This solved my problem.


CompareJSONBodyHandler unexpectedly success when params is a reference of map[string]interaface{}

I expected the following test was failed but it wasn't. Am I mis-understood the usage?
func TestClientPost(t *testing.T) {
	srv := httptest.NewServer(
		reqtest.ChainHandler(
			reqtest.CompareJSONBodyHandler(t, &map[string]interface{}{
				"Hello": "World",
			}),
		),
	)
	defer srv.Close()

	body, err := json.Marshal(map[string]interface{}{
		"hello": "hello",
	})
	if err != nil {
		panic(err)
	}
	client := http.DefaultClient
	_, err = client.Post(srv.URL, "application/json", bytes.NewBuffer(body))
	if err != nil {
		panic(err)
	}
}

Unintentionaly, CompareJSONBodyHandler() was only checking for type matches.
So, it has been modified to convert to JSON before comparison.
Thanks for the report.


[DNM] Conform float types to TextOutputStreamable

This is a change included in SE-0228 which allows floating-point types to write themselves into strings without generating a temporary String. It may not be a win for all floating-point types, so I'm pulling it into a separate branch to benchmark it separately.

Performance: -Onone

TEST
OLD
NEW
DELTA
RATIO

Regression

CharIteration_ascii_unicodeScalars_Backwards
251441
317807
+26.4%
0.79x

CharIteration_chinese_unicodeScalars_Backwards
190796
240970
+26.3%
0.79x

CharIteration_punctuated_unicodeScalars_Backwards
55236
69466
+25.8%
0.80x

CharIteration_russian_unicodeScalars_Backwards
210555
264335
+25.5%
0.80x

CharIteration_korean_unicodeScalars_Backwards
245354
307508
+25.3%
0.80x

CharIteration_punctuatedJapanese_unicodeScalars_Backwards
44591
55054
+23.5%
0.81x

CharIteration_japanese_unicodeScalars_Backwards
312278
381897
+22.3%
0.82x

CharIteration_utf16_unicodeScalars_Backwards
223443
262272
+17.4%
0.85x

CharIndexing_japanese_unicodeScalars_Backwards
449180
521656
+16.1%
0.86x

CharIndexing_korean_unicodeScalars_Backwards
370412
429111
+15.8%
0.86x

CharIndexing_ascii_unicodeScalars_Backwards
374159
433184
+15.8%
0.86x

CharIndexing_punctuatedJapanese_unicodeScalars_Backwards
64621
74480
+15.3%
0.87x

CharIndexing_punctuated_unicodeScalars_Backwards
82184
94573
+15.1%
0.87x

CharIndexing_russian_unicodeScalars_Backwards
315630
362414
+14.8%
0.87x

CharIndexing_utf16_unicodeScalars_Backwards
324669
358438
+10.4%
0.91x

Code size: Swift libraries

TEST
OLD
NEW
DELTA
RATIO

Regression

libswiftSwiftPrivate.dylib
40960
45056
+10.0%
0.91x

Improvement

libswiftCoreGraphics.dylib
65536
61440
-6.2%
1.07x

How to read the data
The tables contain differences in performance which are larger than 8% and differences in code size which are larger than 1%.
If you see any unexpected regressions, you should consider fixing the regressions before you merge the PR.
Noise: Sometimes the performance results (not code size!) contain false alarms. Unexpected regressions which are marked with '(?)' are probably noise. If you see regressions which you cannot explain you can try to run the benchmarks again. If regressions still show up, please consult with the performance team (@eeckstein).

Hardware Overview
  Model Name: Mac Pro
  Model Identifier: MacPro6,1
  Processor Name: 12-Core Intel Xeon E5
  Processor Speed: 2.7 GHz
  Number of Processors: 1
  Total Number of Cores: 12
  L2 Cache (per Core): 256 KB
  L3 Cache: 30 MB
  Memory: 64 GB


Enable TravisCI

Thanks! Can you rebase against the current master?

Sure, still fixing the tests, would do before merging :)

@Arachnid all set, ready to be reviewed.

Thanks very much. This was on my todo list, but I'm glad you got to it first. :)

Looks like it's expecting a rakefile? https://travis-ci.org/ethereum/ens/builds/215588850


[ERROR MPL-0040] Failed on cluster

13 minutes to reproduce:
untar https://drive.google.com/file/d/18n0z4_Bk9Gscy3RRCiU6FiNvghIb6zIG/view?usp=drive_link
$ time ./run-me-BoomTile-asap7-base.sh
OpenROAD v2.0-15340-g7ebef4425
Features included (+) or not (-): +Charts +GPU +GUI +Python
This program is licensed under the BSD-3 license. See the LICENSE file for details.
Components of this program may be licensed under more restrictive licenses which must be honored.
HierRTLMP Flow enabled...
rtl_macro_placer -halo_width 20 -halo_height 20 -report_directory .//objects/asap7/BoomTile/base/rtlmp -target_util 0.60
Floorplan Outline: (0.0, 0.0) (2160.73, 2160.73),  Core Outline: (1.026, 1.08) (2159.73, 2159.73)
        Number of std cell instances: 1743858
        Area of std cell instances: 220985.73
        Number of macros: 72
        Area of macros: 691249.12
        Halo width: 20.00
        Halo height: 20.00
        Area of macros with halos: 1292620.62
        Area of std cell instances + Area of macros: 912234.88
        Core area: 4659886.50
        Design Utilization: 0.20
        Core Utilization: 0.06
        Manufacturing Grid: 1

[ERROR MPL-0040] Failed on cluster frontend/bpd/banked_predictors_1/btb
Error: macro_place_util.tcl, 143 MPL-0040

Originally posted by @oharboe in https://github.com/The-OpenROAD-Project/megaboom/issues/97#issuecomment-2308988697

@AcKoucher @maliberty Found a workaround, tweak initial conditions

@AcKoucher @maliberty Found a workaround, tweak initial conditions

From the megaboom PR:
I would like to see an initial diagnosis from @AcKoucher first... but yes. I hope the problem is just some existing rare problem that presents itself with some unfortunate initial conditions and that it can be solved in due course but without urgency.

It looks like there's a combination of things that make this somewhat peculiar.

After clustering we end up with multiple mixed clusters which are mode of some few std cells and a macro (3, 7, 32, 35, 16, 17, 29).

The dead space filling that we apply to mixed clusters during hierarchical macro placement annealing have meaningful effect in just three clusters (4 --> 7, 8 --> 11, 29 --> 32).

That are way to many tiny std cell clusters.

Now, the actual problem seems to be that when we get to the point of placing the children of the cluster 4 in the first image - 7 in the second image after dead space filling - even with the target util variation SA can't fit the clusters in the outline. Apparently this happens, because the outline penalty never wins the fight against the boundary penalty.

However there's something going on with the wire length, because for all the final steps, I see zero at the debug report (perhaps it's too small I have to check).
------ Penalty ------
Area                       1.0186
Outline Penalty            0.4646
Wirelength                 0.0000
Boundary Penalty         102.0848
Normalized Cost           55.1202

My first suggestion would be to try decreasing the halos as @oharboe already did or decrease the boundary penalty.
@maliberty It looks like there's a lot going on, do you have some idea of what to aim first?

Thanks! Sounds like this is in good hands and well understood. No longer urgent for my part as we have a workaround.

@oharboe Ok :-) I'm investigating what is going on with the clustering so we can have a proper fix.

Another workaround I'm trying out is to save a macro placement. With a saved macro placement, I should avoid rtlmp errors due to slight changes in initial conditions, like changed PLACE_DENSITY.
write_macro_placement macros.tcl

@AcKoucher Please confirm that the fixes work on the full testcase of 1 hour
I included a faster, 13 minute, testcase here, that I produced from the full testcase with deltaDebug.py.
There is a risk that deltaDebug.py identified other bugs than the original bug...

@AcKoucher Please confirm that the fixes work on the full testcase of 1 hour
I included a faster, 13 minute, testcase here, that I produced from the full testcase with deltaDebug.py.
There is a risk that deltaDebug.py identified other bugs than the original bug...

ah, the full test-case still fails...

Can you re-delta?

@oharboe As I said in #5666 there are other problems that need to be addressed in other to actually resolve the issue. I'm investigating.

@maliberty New deltadeug: this test case takes ca. 13 minutes and fails on master:
https://drive.google.com/file/d/1klYn7s2_uJBk2Wi-vfPKK_ol8Kwv02sY/view?usp=sharing

@maliberty @jeffng-or @AcKoucher Any news on this?

@AcKoucher Thanks for the update! Do you think that the failure of mpl2 here is just some unfortunate initial conditions and some slight change in initial conditions would cause it to work?
Looks like megaboom passes today if I enable rtlmp and synth_hierarchical...

My thoughts are that even if we can get this test to work with some different initial conditions, it shouldn't be too hard for SA to deal with what's going on here. As I said, the weights for SA were never tuned after its incorporation. This testcase is a good opportunity to do some tuning - especially after many changes were made to mpl2 (fixed, enhancements, refactoring..)


Add isPenTransparent

Add isPenTransparent to decide if to draw outlines... 😂

https://github.com/BOT-Man-JL/EggAche-GL/commit/77b9f655d7071b35e9fcfcd80c9b689f4b678122


Enable the new model serialization for ArcScVmm

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
API changes are not detected in this pull request.


Update debug-live-azure-apps-troubleshooting.md

Add troubleshooting steps for clearing out the MRU (Most Recently Used) lists.

@WilliamXieMSFT : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@Mikejo5000 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@Mikejo5000 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@Mikejo5000 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@Mikejo5000 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off Thanks @WilliamXieMSFT !


Cannot read property 'grid' of undefined

Hey guys,
Running Chrome 55.0.2883.95
Using bower install ng-formio-grid:
we get:
Unable to find a suitable version for angular, please choose one by typing one of the numbers below:
    1) angular#>=1.4.0 which resolved to 1.5.11 and is required by angular-bootstrap#2.4.0, angular-bootstrap#1.3.3
    2) angular#>=1.4.0 1.5.x which resolved to 1.5.11 and is required by angular-ui-grid#4.0.2
    3) angular#>=1.2.18 which resolved to 1.5.11 and is required by angular-ui-select#0.19.6
    4) angular#^1.6.1 which resolved to 1.6.1 and is required by ng-formio#2.8.2, ng-formio-grid#0.12.1
    5) angular#>=1.2.0 <1.7.0 which resolved to 1.6.1 and is required by angular-moment#1.0.1
    6) angular#>= 1.3.6 which resolved to 1.6.1 and is required by angular-ui-mask#1.8.8-beta.1
    7) angular#>1.2.0 which resolved to 1.6.1 and is required by ng-file-upload#12.2.13
    8) angular#1.6.1 which resolved to 1.6.1 and is required by angular-sanitize#1.6.1

I chose 4.... then
1) angular-bootstrap#^1.2.0 which resolved to 1.3.3 and is required by bootstrap-ui-datetime-picker#2.5.4
2) angular-bootstrap#^2.4.0 which resolved to 2.4.0 and is required by ng-formio#2.8.2pyh

I chose option2.
I use wiredep -s index.html to load all the dependencies:

      <link rel="stylesheet" href="bower_components/angular-ui-grid/ui-grid.css" />
      <link rel="stylesheet" href="bower_components/bootstrap/dist/css/bootstrap.css" />
      <link rel="stylesheet" href="bower_components/angular-ui-select/dist/select.css" />
      <link rel="stylesheet" href="bower_components/ng-formio/css/formio.css" />

      <formio src="'https://myapp.form.io/ecoffintest'"></formio>

      <formio-grid src="'https://myapp.form.io/ecoffintest'"></formio-grid>

The form view / submit works fine.
However with data grid never loads with the following errors:
angular.js:14328 TypeError: element.html(...).show is not a function
    at Object.link (http://localhost:8000/bower_components/ng-formio-grid/dist/ng-formio-grid.js:51:30)
    at http://localhost:8000/bower_components/angular/angular.js:1291:18
    at http://localhost:8000/bower_components/angular/angular.js:10246:44
    at invokeLinkFn (http://localhost:8000/bower_components/angular/angular.js:10252:9)
    at nodeLinkFn (http://localhost:8000/bower_components/angular/angular.js:9641:11)
    at compositeLinkFn (http://localhost:8000/bower_components/angular/angular.js:8881:13)
    at compositeLinkFn (http://localhost:8000/bower_components/angular/angular.js:8884:13)
    at publicLinkFn (http://localhost:8000/bower_components/angular/angular.js:8746:30)
    at http://localhost:8000/bower_components/angular/angular.js:1843:27
    at Scope.$eval (http://localhost:8000/bower_components/angular/angular.js:17972:28)

(anonymous) @ angular.js:14328
(anonymous) @ angular.js:10837
invokeLinkFn @ angular.js:10254
nodeLinkFn @ angular.js:9641
compositeLinkFn @ angular.js:8881
compositeLinkFn @ angular.js:8884
publicLinkFn @ angular.js:8746
(anonymous) @ angular.js:1843
$eval @ angular.js:17972
$apply @ angular.js:18072
bootstrapApply @ angular.js:1841
invoke @ angular.js:4842
doBootstrap @ angular.js:1839
bootstrap @ angular.js:1859
angularInit @ angular.js:1744
(anonymous) @ angular.js:32977
trigger @ angular.js:3314
2017-01-26 10:06:48.599 angular.js:14328 Error: [jqLite:nosel] Looking up elements via selectors is not supported by jqLite! See: http://docs.angularjs.org/api/angular.element
http://errors.angularjs.org/1.6.1/jqLite/nosel
    at http://localhost:8000/bower_components/angular/angular.js:68:12
    at Object.JQLite [as element] (http://localhost:8000/bower_components/angular/angular.js:3067:13)
    at setLoading (http://localhost:8000/bower_components/ng-formio-grid/dist/ng-formio-grid.js:117:39)
    at http://localhost:8000/bower_components/ng-formio-grid/dist/ng-formio-grid.js:363:15
    at processQueue (http://localhost:8000/bower_components/angular/angular.js:16648:37)
    at http://localhost:8000/bower_components/angular/angular.js:16692:27
    at Scope.$eval (http://localhost:8000/bower_components/angular/angular.js:17972:28)
    at Scope.$digest (http://localhost:8000/bower_components/angular/angular.js:17786:31)
    at http://localhost:8000/bower_components/angular/angular.js:18011:26
    at completeOutstandingRequest (http://localhost:8000/bower_components/angular/angular.js:6111:10) Possibly unhandled rejection: {}
(anonymous) @ angular.js:14328
(anonymous) @ angular.js:10837
processChecks @ angular.js:16674
$eval @ angular.js:17972
$digest @ angular.js:17786
(anonymous) @ angular.js:18011
completeOutstandingRequest @ angular.js:6111
(anonymous) @ angular.js:6390
2017-01-26 10:06:48.609 angular.js:14328 TypeError: Cannot read property 'grid' of undefined
    at ng-formio-grid.js:373
    at angular.js:19916
    at completeOutstandingRequest (angular.js:6111)
    at angular.js:6390
(anonymous) @ angular.js:14328
(anonymous) @ angular.js:10837
(anonymous) @ angular.js:19919
completeOutstandingRequest @ angular.js:6111
(anonymous) @ angular.js:6390
2017-01-26 10:06:48.610 angular.js:14328 TypeError: Cannot read property 'grid' of undefined
    at http://localhost:8000/bower_components/ng-formio-grid/dist/ng-formio-grid.js:373:124
    at http://localhost:8000/bower_components/angular/angular.js:19916:31
    at completeOutstandingRequest (http://localhost:8000/bower_components/angular/angular.js:6111:10)
    at http://localhost:8000/bower_components/angular/angular.js:6390:7 Possibly unhandled rejection: {}
(anonymous) @ angular.js:14328
(anonymous) @ angular.js:10837
processChecks @ angular.js:16674
$eval @ angular.js:17972
$digest @ angular.js:17786
$apply @ angular.js:18080
(anonymous) @ angular.js:19924
completeOutstandingRequest @ angular.js:6111
(anonymous) @ angular.js:6390

@edcoffin try manually placing the jquery dependency before angular.

That fixed it. Thanks @zackurben !


nss: 3.74 -> 3.75

Motivation for this change
upstream release
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

The FF 98 scheduled tomorrow won't need this one yet, right?  (I expect FF 99 in a month will.)

Yep, they're usually a month behind.
https://wiki.mozilla.org/NSS:Release_Versions

@ofBorg build firefox-unwrapped firefox-esr-unwrapped

For me firefox did build with this atop staging-next.


Add a mini.starter MiniStarterEchoHeader highlight group

Contributing guidelines

[X] I have read CONTRIBUTING.md
[X] I have read CODE_OF_CONDUCT.md

Module(s)
mini.starter
Description
The mini.starter echo() function hard codes the WarningMsg hl group for the '(mini.starter)' text that appears before echo's log messages link to source . I propose that a new highlight group is created (potentially called MiniStarterEchoHeader) that links to WarningMsg allowing color schemes to customize the color of this log message header.
I think this should be considered because currently colorscheme maintainers cannot customize this prompt without effecting all warning messages for all plugins, and the mini.starter echos are not always actually warnings so it would be nice if they did not have to use warning colors.
I would be  interested in helping implement this feature if this feature request is approved, and help is wanted :)

The orange text in the bottom left is what I would like to customize with my colorscheme lackluster.nvim

Thanks for the suggestion!
The major problem in having this done is that the same approach is used in 10 modules in total. All of them have (mini.xxx) prefix whenever the text is echoed and highlighted as a WarningMsg.
Case can be made that 'mini.starter' (and probably 'mini.align') use them not for one time messages but for user interaction. I am not yet sure how strong of a case that this. Currently preserving all modules to behave in the same way feels like a stronger argument, but I'll think about it.

@echasnovski Thanks for responding so quickly :)
Your hesitation makes a lot of sense.  I think preserving consistency is always a good idea. Plus this isn't really a critical feature request, and it seems like it could be quite a bit of effort to implement and maintain across all the mini modules. I'll mark this issue as closed for now.
If you ever change your mind and want to re-open this issue, I'd be happy to help you experiment to find a solution that could fit all 10 modules. Perhaps with something like MiniLogHeader linking to WarningMsg, or whatever you think works best.
Anyways thanks for all your great work on this project! I think mini.nvim is a really inspiring project!


compilerArgs get overwritten

See https://github.com/gradle/gradle-java-modules/issues/10 for full description

Thanks - it's indeed a limitation.
Regarding doFirst, I'd be cautious. I changed it to doLast while fixing issue #4, and it turned out that Jigsaw parameters stopped being applied at all to the run task. It needs some extera investigation.

No, of course not doLast, that would be worse, as it is run after the existing actions, which is the compiler execution, amongst possible other actions.
Both, doLast and doFirst actions are executed at execution phase though and during execution phase no configuration should be changed, especially not those configurations that could influence the incremental execution, meaning the inputs and outputs of a task and thus its up-to-date check.
Configuration of a task should only be done during the configuration phase, so probably do it in an afterEvaluate block instead to do it at end of configuration phase when the normal configuration actions are done, but still within the configuration phase.
Actually in which block it is done does not change the bug reported here, the bug here is mainly that setCompilerArgs is used instead of getting them and adding the addtional ones. The doLast think was only a side-note that should probably also get fixed.

Thanks for the explanation. I'll create a separate issue for updating the task configuration, and here I'll just fix for compilerArgs.

The fix is available on master branch. For now, overriding JVM args it not possible, because it breaks integration tests and I must take a closer look at it.

What do you mean by "overriding JVM args is not possible"?
The compilerArgs are the JVM args, aren't they?


net: refactor to simplify lifetimes/generics.

Refactor embassy-net api. Advantages:

Now there's a separate Runner struct. run() requires &mut self, this prevents the user from doing weird stuff like calling run() in two tasks concurrently.
Stack is now Copy, so you can pass it by value everywhere. This means you need only one StaticCell (for the resources) instead of two (resources, stack).
Stack is no longer generic over the driver, only the runner is. This makes code using embassy-net agnostic to what driver is in use, only the code creating the stack has to care.
DnsSocket is not generic over the driver anymore.
No forced 'static litetime anymore. This means you can now dynamically create/teardown the network stack as many times as you want. If you run everything in a single task with join you don't need StaticCell at all.
Stack and the sockets are all covariant over the lifetime now.


finishInsert and finishDelete call reload so fast that the server unable to handle the request

Could you provide a proper issue description with an example illustrating the issue?


Adds a user-agent to emission queries

Adds a user agent to the metaphysics graphql requests - re https://github.com/artsy/force/issues/2191
We could expose some more information in the user agent (version of app, version of emission) if we write a bit of native code, opening so that the discussion on what to send can happen,

I agree with @joeyAghion.
Not sure what you were thinking in terms of native code, but I think it can be limited to an extra configuration that the AREmission object takes when initialising.

OK, this will force someone to add the user agent in Eigen when it updates 👍

Perfect 👌


Docker container is not https-enabled by default

Currently it accepts plaintext http connections. Might be intended behavior if we do not publish ports directly, but still confusing.

Either I have to put some work in place to get to HTTPS with self signed certificates. Or we expect the user to set up a ngnix/apache container and proxy https to http.
Since we cannot rely on this having a domain name and being externally visible we can do self signed certificates at best.

Yes.
We need to understand what data interfaces should docker container have.
Certificate deployment/setting hostname is the obvious one, but there are more.
Like, importing certificates for validation chain (when talking to Nessus/OpenVAS servers), database persistence/backup/whatever, log export, reports export, maybe something else.
Let's make a list -- do you have more suggestions?


Database Driver: RethinkDb. Often compared to MongoDb.

Database Driver: RethinkDb. Often compared to MongoDb.

LGTM - @quozd @vladen @Jeffiy @devkhan
Link https://github.com/bchavez/RethinkDb.Driver/

Thanks.


BIRS talk

Is this the implementation you described in:
http://www.birs.ca/events/2016/5-day-workshops/16w5099/videos/watch/201611150930-Blanck.html
If not, is the implementation described there available somewhere publically? Thanks.

Hi,
Yes, it is. Beware though that it is not complete and there are some bugs.
Jens
On Mon, 24 Apr 2017, 17:17 Abhishek Anand<EMAIL_ADDRESS>wrote:

Is this the implementation you described in:
http://www.birs.ca/events/2016/5-day-workshops/16w5099/videos/watch/201611150930-Blanck.html
If not, is the implementation described there available somewhere
publically? Thanks.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jensblanck/cdar/issues/3, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABvAyKFp_2JfqrNEn7oyAsLAz8gVauXrks5rzMr8gaJpZM4NGY8_
.


Expand Quarkus testing

Now that we have jdk8 on xlinux (in containers), these tests can be expanded to include jdk11 and out to p & z platforms.

Looks like flapdoodle-oss/de.flapdoodle.embed.process#109 got merged (including the fix for aarch64 as well)... maybe things are looking up :)

I still do not see that the mongoDB tests are passing (do we need for the quarkus project to pick up the latest version of flapdoodle I wonder)?

This can now be closed as quarkus, quarkus_quickstarts and camel tests added on x/p/zlinux arches (Docker-based testing).


doc: clarify which flags are supported in uv_fs_event_start

R=@bnoordhuis
R=@piscisaureus

Thanks for the comments Ben! I left those notes in, better be more explicit indeed.


Show bits per second instead of bytes per second

Hi,
Would it be possible to optionally show speed in bits instead of bytes? Meaning, show speed like "bps", "Kbps" and "Mbps" so that it matches up with what ISPs advertise as their speeds?
Thanks!

I've been searching for a way to do this... Agree it would be a good option to have.

Guys, I am very open to new contributions. The thing is that I don't have enough time to dedicate to this project and I don't know when I will have...I do tend to do something here and there in my free time... but can't promise anything regarding this feature