depthengine_2_0.dll  Cannot find or open the PDB file.

Hi,
I installed my SDK using MSI file, trying to run the example cpp file on MSVC2017 WIN10 but I encountered this problem.(figure attached below). Any suggestion to fix this?
Thanks
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Users\jniu0\source\repos\ConsoleApplication1\Debug\ConsoleApplication1.exe'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\ntdll.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\kernel32.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\KernelBase.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Users\jniu0\source\repos\ConsoleApplication1\Debug\k4a.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\cfgmgr32.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\ucrtbase.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\advapi32.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msvcrt.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\sechost.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\rpcrt4.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\sspicli.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\cryptbase.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\bcryptprimitives.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\ole32.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\combase.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\gdi32.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\win32u.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\gdi32full.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msvcp_win.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\user32.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\vcruntime140d.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\ucrtbased.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\mf.dll'. Cannot find or open the PDB file.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\mfplat.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\SHCore.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\mfreadwrite.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msvcp140.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\vcruntime140.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\mfcore.dll'. Cannot find or open the PDB file.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\crypt32.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msasn1.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\powrprof.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\umpdc.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\kernel.appcore.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\bcrypt.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\ksuser.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\mfperfhelper.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\RTWorkQ.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\imm32.dll'. Symbols loaded.
The thread 0xcbc has exited with code 0 (0x0).
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\setupapi.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\winusb.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\hid.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\devobj.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\wintrust.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Unloaded 'C:\Windows\SysWOW64\winusb.dll'
'ConsoleApplication1.exe' (Win32): Unloaded 'C:\Windows\SysWOW64\hid.dll'
'ConsoleApplication1.exe' (Win32): Unloaded 'C:\Windows\SysWOW64\devobj.dll'
'ConsoleApplication1.exe' (Win32): Unloaded 'C:\Windows\SysWOW64\wintrust.dll'
'ConsoleApplication1.exe' (Win32): Unloaded 'C:\Windows\SysWOW64\setupapi.dll'
The thread 0x66c has exited with code 0 (0x0).
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\setupapi.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\winusb.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\hid.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\devobj.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\wintrust.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\CompPkgSup.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\oleaut32.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\clbcatq.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\Windows.Media.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\ws2_32.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\ntmarta.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\FSClient.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\d3d11.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\dxgi.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\mfsensorgroup.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\DXCore.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\Windows.ApplicationModel.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\twinapi.appcore.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\rmclient.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\avrt.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\AppXDeploymentClient.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\FirewallAPI.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\StateRepository.Core.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\dnsapi.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\nsi.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\IPHLPAPI.DLL'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\fwbase.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\vidcap.ax'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\Kswdmcap.ax'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.18362.1082_none_bb5fb711ec92dd42\comctl32.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\mfc42.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\Windows.StateRepositoryPS.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\WinTypes.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\mfmjpegdec.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msvproc.dll'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\COLORCNV.DLL'. Symbols loaded.
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msdmo.dll'. Symbols loaded.
The thread 0x4874 has exited with code 0 (0x0).
The thread 0x3a88 has exited with code 0 (0x0).
The thread 0xa30 has exited with code 0 (0x0).
The thread 0x4614 has exited with code 0 (0x0).
The thread 0x3250 has exited with code 0 (0x0).
The thread 0x5bc8 has exited with code 0 (0x0).
The thread 0x3448 has exited with code 0 (0x0).
The thread 0x56a4 has exited with code 0 (0x0).
The thread 0x33fc has exited with code 0 (0x0).
The thread 0x1a60 has exited with code 0 (0x0).
'ConsoleApplication1.exe' (Win32): Unloaded 'C:\Windows\SysWOW64\winusb.dll'
'ConsoleApplication1.exe' (Win32): Unloaded 'C:\Windows\SysWOW64\hid.dll'
'ConsoleApplication1.exe' (Win32): Unloaded 'C:\Windows\SysWOW64\devobj.dll'
'ConsoleApplication1.exe' (Win32): Unloaded 'C:\Windows\SysWOW64\wintrust.dll'
'ConsoleApplication1.exe' (Win32): Unloaded 'C:\Windows\SysWOW64\setupapi.dll'
The thread 0x5144 has exited with code 0 (0x0).
The thread 0xa1c has exited with code 0 (0x0).
The thread 0x43e0 has exited with code 0 (0x0).
'ConsoleApplication1.exe' (Win32): Loaded 'C:\Users\jniu0\source\repos\ConsoleApplication1\Debug\depthengine_2_0.dll'. Cannot find or open the PDB file.
The program '[20204] ConsoleApplication1.exe' has exited with code 0 (0x0).

By design due to the depth engine being closed source


Interface Support for Signals

Is your feature request related to a problem? Please describe.
Declaring Concrete signal types
make posible just subscribing to that concrete type
so i can not normally subscribe to interfaces of fired signals
Describe the solution you'd like
What i want is to declare the signals in a way that it's interfaces do it too
and when i fire the concrete signal, interfaces declarations do it too
Describe alternatives you've considered
just working normally coupling the concrete types to the subscriptors

#91 Resolves this issue

Continuous Integration workflow is running smoothly. It will now run the tests from the test suite and create Unity builds for all the supported targets.
You can now do your PR again.
Cheers!


Bits for ADI1MUX, BDI1MUX and CDI1MUX

Recently merged PR https://github.com/SymbiFlow/prjxray/pull/900 allows to have in DB bits for those muxes. The bits are required for SRL32/SRL16 support.
This issue is here to not forget to push those to the DB

Looks like these have been included now.
Artix
https://github.com/SymbiFlow/prjxray-db/commit/84a5ffc0d5f87d57f0fd5cde135edb7a2198212e#diff-0de60774b3b2c1043cb089e5a0ca0d94R354
https://github.com/SymbiFlow/prjxray-db/commit/84a5ffc0d5f87d57f0fd5cde135edb7a2198212e#diff-0de60774b3b2c1043cb089e5a0ca0d94R441
https://github.com/SymbiFlow/prjxray-db/commit/84a5ffc0d5f87d57f0fd5cde135edb7a2198212e#diff-0de60774b3b2c1043cb089e5a0ca0d94R534
Zynq
https://github.com/SymbiFlow/prjxray-db/commit/2d9308a8d8f54c0ffc34f12c0c40e11676fd0774#diff-a8616afb89051e8a009ab9defd46f0dcR354
https://github.com/SymbiFlow/prjxray-db/commit/2d9308a8d8f54c0ffc34f12c0c40e11676fd0774#diff-a8616afb89051e8a009ab9defd46f0dcR441
https://github.com/SymbiFlow/prjxray-db/commit/2d9308a8d8f54c0ffc34f12c0c40e11676fd0774#diff-a8616afb89051e8a009ab9defd46f0dcR530


Add interfaces for destination service

For further development: The need may arise to add other services as a destination. Need to create an interface where the controller sends the messages to.

In a132fb4 this functionality was added, but need to think about a proper restructure to match enterprise requirements.


Wiki describing the cleanmate tcp commands

Is your feature request related to a problem? Please describe:

It was quite hard to reverse engineer the tcp commands to create this plugin. Make it easier for other developers developing plugins for other platforms.
Describe the solution you'd like:

Create a structured wiki describing all the tcp commands that can be sent to the Cleanmate robot

This should be done in the new cleanmate package

This should be done in the new cleanmate package.


Json import api endpoint

Part of https://github.com/swisstopo/swissgeol-boreholes-suite/issues/1636

Can be considered to merge into main after next prod release


BERNICK PULL TEST FOR JENKINS - IGNORE

run eval

eval test this please

eval test this please

test bot

test this please

test this please

test this please

testtesttest

test this please

test this please

test this please

test this please

test this please

test this please

ok to test

test this please

test this please

eval test please


how can I delete software item in Eclipse Steady Web Frontend

I run the Steady-CLI tool in the IP: Port/APPS interface. I successfully obtained some software lists with vulnerabilities. Because it is testing data, I want to delete these loopholes on the interface. What should I do?

Hi @momo-tong ,
the frontend displays the data available in the backend, you can delete such data using the clean goal (https://eclipse.github.io/steady/user/tutorials/java_cli/#clean).

Thank you for your answer！


Improve accessibility for screen readers season

Duck season

Failed Test
Failure Summary
Logs

Test_UnsupportedMediaType
failure_message: Failedfailure_text: === RUN   Test_UnsupportedMediaType    api_test.go:74: Unsupported media type provided--- FAIL: Test_Unsu...
Logs ↗

Flaky Test
Failure Summary
Logs

[chromium] should return list of users correctly.
The API call to get a list of users failed with a 404 Not Found error.
Logs ↗

[chromium] should display user profile information correctly.
The test timed out waiting for the expected text "User Profile" in the page, but it received an empty array instead.
Logs ↗

[chromium] should login with credentials correctly correctly.
The login request to the server failed with a 404 Not Found error.
Logs ↗

[chromium] should display error message for invalid login correctly.
The expected HTTP status code 401 was not received, instead a function was returned.
Logs ↗

View Full Report ↗ ⋅ Docs

Failed Test
Failure Summary
Logs

Test_UnsupportedMediaType
failure_message: Failedfailure_text: === RUN   Test_UnsupportedMediaType    api_test.go:74: Unsupported media type provided--- FAIL: Test_Unsu...
Logs ↗

Flaky Test
Failure Summary
Logs

[chromium] should return list of users correctly.
The API call to get a list of users failed with a 404 Not Found error.
Logs ↗

[chromium] should display user profile information correctly.
The test timed out waiting for the expected text "User Profile" in the page, but it received an empty array instead.
Logs ↗

[chromium] should login with credentials correctly correctly.
The login request to the server failed with a 404 Not Found error.
Logs ↗

[chromium] should display error message for invalid login correctly.
The expected HTTP status code 401 was not received, instead a function was returned.
Logs ↗

View Full Report ↗ ⋅ Docs


Show relationships(BelongsToMany) default id filter not work

Laravel Version: Laravel Version: 5.5.40
PHP Version: 7.2
Laravel-admin: 1.6.0

Description:
Show relationships(BelongsToMany) default id filter is not work.
I get an error like the following.
1052 Column 'id' in where clause is ambiguous.
Steps To Reproduce:
    protected function detail($id)
    {
        $show = new Show(ModelClass::findOrFail($id));

        $show->id('ID');
	$show->relationName('label', function (Grid $grid) {
		$grid->id('ID')->sortable();
        });

        return $show;
    }

If filtering with ID Filter on the page of show created as above will result in an error.

Can you try to add group by id ?

I tried add group by id.

$grid->model()->groupBy('id');
$grid->model()->groupBy('relation.id');

But not works.
One to many filter is works. query is
select * from `relation` where `relation`.`parent_id` = '1' and `reration`.`parent_id` is not null and `id` = '2' and `client_user`.`deleted_at` is null limit 20 offset 0

But many to many filte is not works. query is
select * from `relation` inner join `pivot_table` on `relation`.`id` = `pivot_table`.`relation_id` where `pivot_table`.`parent_id` = 1 and `id` = 2 and `relation`.`deleted_at` is null

Probably I think that the cause is joining.
Filter.php
    public function __construct(Model $model)
    {
        $this->model = $model;

        $pk = $this->model->eloquent()->getKeyName();

        $this->initLayout();

        $this->equal($pk, strtoupper($pk)); // <- this
        $this->scopes = new Collection();
    }

In the case of Many to Many, I feel I have to prefix the table name to the ID Filter's PK.

Yes, there is an error.
Example: in my case, Exams has many Test object.
In ExamsController::Show method, I need to show directly test id, but $grid->id fails.
$grid->column('test_id', "ID");
Column referenced from pivot table. In pivot table there are two columns
test_id, exam_id


Remove usages of androidx.appcompat

Removes androidx.appcompat imports from android-browser-helper to
reduce the default TWA apk size (~500KB difference).
All activities in androidbrowserhelper module now extends Activity
instead of AppCompatActivity.
Most of the demo app's theme changed to Theme.Translucent.NoTitleBar
instead of the Theme.LauncherActivity that inherits the appcompat
style Theme.AppCompat.NoActionBar.
Theme.Translucent.NoTitleBar has the same translucent style as the
Theme.LauncherActivity, there should be no change in styles.
Some of the themes changed from Theme.AppCompat.Light.DarkActionBar
to Theme.Material.Light.DarkActionBar
The only demo app that's still import androidx.appcompat is the
custom-tabs-example-app. It contains many Activities and some of them
are using methods from AppCompatActivity, do not change it for now.
@PEConn @andreban  PTAL Thanks :)

Wow!
I'm playing with this and the Bubblewrap PR locally and generated a project for http://pwa-directory.appspot.com/:

Original size: 1.1Mb
With this PR: 333K

Amazing!

As far as I know, AppCompatActivity was about ensuring Activities looked appropriately Material Designed on older phones. Since we don't care too much about the appearance of our demos, and since the Activities we use in prod are generally meant to be invisible, I don't see and issue with this.


fix(core): can reset tooltip.renderTooltip in setOptions

👀 PR includes

✨ Feature

[ ] New feature

🎨 Enhance

[ ] Code style optimization
[ ] Refactoring
[ ] Change the UI
[ ] Improve the performance
[ ] Type optimization

🐛 Bugfix

[x] Solve the issue and close #2205

🔧 Chore

[x] Test case
[x] Docs / demos update
[ ] CI / workflow
[ ] Release version
[x] Other (new button in react playground which can reset tooltip with setOptions)

📝 Description

s2.tooltip is init in the pivot sheet constructor, s2.setOptions and s2.render can not reset it, so call s2.initTooltip manually if tooltip changed in s2.setOptions.
🖼 Screenshot

Before
After

❌
✅

🔗 Related issue link

🔍 Self-Check before the merge

[x] Add or update relevant docs.
[x] Add or update relevant demos.
[x] Add or update test case.
[ ] Add or update relevant TypeScript definitions.

@tyr1dev Test case failed

:tada: This PR is included in version @antv/s2-v1.47.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version @antv/s2-react-v1.40.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Feature request: phone formatting

I'd be great to have something like DateFormater but for phone numbers.

This might be an interesting feature; see also this doc.


"Skipping rendezvous re-initialization" when calling collective_ops in a distributed cluster

We meet a problem which continuously logs re-initialization within the same MonitoredSession on the leader worker. Furthermore, there seems to be an accuracy losing during the gradient descent of the parabolic toy model. We have no idea how to prevent the logging of re-initialization. All hints or explanations are welcome.
It seems the BaseRemoteRendezvous::Initialize method is called at every train step. The log of the leader worker is attached below.
task 0: before syncing ...
{'u': 0.1, 'loss': -0.19, 'global_step': 0}
task 0: running init_ops ...
{'u': 0.1, 'loss': -0.19, 'global_step': 0}
task 0: obtaining gstep ...
train one step at step 0.
2019-09-30 10:15:56.954439: I tensorflow/core/distributed_runtime/base_rendezvous_mgr.cc:159] Skipping rendezvous re-initialization.
{'u': 0.1, 'loss': -0.19, 'global_step': 1}
train one step at step 1.
2019-09-30 10:15:56.959006: I tensorflow/core/distributed_runtime/base_rendezvous_mgr.cc:159] Skipping rendezvous re-initialization.
{'u': 0.28, 'loss': -0.4816, 'global_step': 2}
train one step at step 2.
2019-09-30 10:15:56.962205: I tensorflow/core/distributed_runtime/base_rendezvous_mgr.cc:159] Skipping rendezvous re-initialization.
{'u': 0.42396685, 'loss': -0.66818583, 'global_step': 3}
train one step at step 3.
2019-09-30 10:15:56.965719: I tensorflow/core/distributed_runtime/base_rendezvous_mgr.cc:159] Skipping rendezvous re-initialization.
{'u': 0.53912044, 'loss': -0.78759, 'global_step': 4}
train one step at step 4.
2019-09-30 10:15:56.969335: I tensorflow/core/distributed_runtime/base_rendezvous_mgr.cc:159] Skipping rendezvous re-initialization.
{'u': 0.6312327, 'loss': -0.8640107, 'global_step': 5}
{'u': 0.70491827, 'loss': -0.9129268, 'global_step': 5}
task 0: final syncing ...
task 0: finalized

A related issue #32810 also has the similar re-initialization at first. But the logging disappears with the improved code snippet, which patches the send_tensor, recv_tensor and ChiefSessionCreator on both workers.

@whhu
I believe the code provided in Stack overflow is the reproducible code with TF version 1.13. Please, confirm.Thanks!

I'm sorry the code is not the reproducible one. We come across the re-initialization problem in a private project, which makes use of the collective_ops in a similar way as the stackoverflow question. This weird problem occurs only in our private project. That is why we want to find out when TensorFlow logs Skipping rendezvous re-initialization.
We try broadcast_send/broadcast_recv and find out that two workers hang and the logging is triggered by worker 0 when worker 1 fetches the collective tensor defined on worker 0. I wish this maybe helpful to illustrate the problem.

The evidence looks like irrelevant to the collective_ops. In our project, the accessing to global_step triggers the re-initialization problem, which is hard to imagine. (-_-)!!
Many thanks for the response all the same. I will close this issue and may start a new one when we locate the problem.


Add support to keyboard properties in scroll view

Add support to keyboardShouldPersistTaps and keyboardDismissMode properties of scroll view component

This is wrong, ignore


SteamVR 2.7.3 allocates

This is a build player that I am benchmarking

Forgot to expand the first allocation

Hey guys any news on this? It still allocates. Makes our game spike from GC collection

UNity docs says, Returns a list of supported XR devices that were included at build time.
Seems safe to cache

@zite i have talked with unity and its safe and best practice to cache the result from getSupportedDevices
https://forum.unity.com/threads/xrsettings-get_supporteddevices-allocate.1364541/#post-8609667


Issue with working with OTP

There seems to be major issues when implementing OTP. First problem is the systemd file<EMAIL_ADDRESS>--the enviromentfile this is pointing at /etc/ipa/default.conf. This breaks when the systemd attempts to add the  [global] tag.
Attempted to patch that and point to the same file without the [global] tag however all OTP still fails with no real indication as to why.

The initial problem appears to have been because latest was mapped to :21 tag. Forcing :22 seems to have allowed the service to start.
OTP is still not working (it appears)

There seems to be major issues when implementing OTP. First problem is the systemd file<EMAIL_ADDRESS>--the enviromentfile this is pointing at /etc/ipa/default.conf. This breaks when the systemd attempts to add the [global] tag.

In the FreeIPA container, no systemd is running. Could you please be more specific about the functional issue?

This is related to using the One Time Password function. Removing the [global] tag (or pointing the @.service file directly to the ldap server) causes the otp service to start - so something is allowing it to run.
Because we couldn't get IPA with OTP working within Docker, we had to scrap and go bare metal, so can't look into it any further.

I'm seeing the same issue trying to use OTP-TOTP. Set up all goes fine in the GUI, but then when I try to login after successfully syncing OTP token, I see this in the logs:
==> /var/log/krb5kdc.log <==
Jul 22 21:47:01 ip-172-31-28-101.ec2.internal krb5kdc2035: AS_REQ (6 etypes {18 17 16 23 25 26}) <IP_ADDRESS>: NEEDED_PREAUTH<EMAIL_ADDRESS>for<EMAIL_ADDRESS>Additional pre-authentication required
Jul 22 21:47:01 ip-172-31-28-101.ec2.internal krb5kdc2035: closing down fd 12
==> /var/log/systemctl.log <==
[start<EMAIL_ADDRESS>Running [export host=ip-172-31-28-101.ec2.internal; export basedn=dc=ec2,dc=internal; export realm=EC2.INTERNAL; export domain=ec2.internal; export xmlrpc_uri=https://ip-172-31-28-101.ec2.internal/ipa/xml; export ldap_uri=ldapi://%2fvar%2frun%2fslapd-EC2-INTERNAL.socket; export enable_ra=True; export ra_plugin=dogtag; export dogtag_version=10; export mode=production; /usr/libexec/ipa-otpd $ldap_uri]
Marked pid [2913] for<EMAIL_ADDRESS>LDAP: ldapi://%2fvar%2frun%2fslapd-EC2-INTERNAL.socket
Socket closed, shutting down...
[start<EMAIL_ADDRESS>Running [export host=ip-172-31-28-101.ec2.internal; export basedn=dc=ec2,dc=internal; export realm=EC2.INTERNAL; export domain=ec2.internal; export xmlrpc_uri=https://ip-172-31-28-101.ec2.internal/ipa/xml; export ldap_uri=ldapi://%2fvar%2frun%2fslapd-EC2-INTERNAL.socket; export enable_ra=True; export ra_plugin=dogtag; export dogtag_version=10; export mode=production; /usr/libexec/ipa-otpd $ldap_uri]
Marked pid [2916] for<EMAIL_ADDRESS>LDAP: ldapi://%2fvar%2frun%2fslapd-EC2-INTERNAL.socket
Socket closed, shutting down...
[start<EMAIL_ADDRESS>Running [export host=ip-172-31-28-101.ec2.internal; export basedn=dc=ec2,dc=internal; export realm=EC2.INTERNAL; export domain=ec2.internal; export xmlrpc_uri=https://ip-172-31-28-101.ec2.internal/ipa/xml; export ldap_uri=ldapi://%2fvar%2frun%2fslapd-EC2-INTERNAL.socket; export enable_ra=True; export ra_plugin=dogtag; export dogtag_version=10; export mode=production; /usr/libexec/ipa-otpd $ldap_uri]
Marked pid [2919] for<EMAIL_ADDRESS>LDAP: ldapi://%2fvar%2frun%2fslapd-EC2-INTERNAL.socket
Socket closed, shutting down...
[start<EMAIL_ADDRESS>Running [export host=ip-172-31-28-101.ec2.internal; export basedn=dc=ec2,dc=internal; export realm=EC2.INTERNAL; export domain=ec2.internal; export xmlrpc_uri=https://ip-172-31-28-101.ec2.internal/ipa/xml; export ldap_uri=ldapi://%2fvar%2frun%2fslapd-EC2-INTERNAL.socket; export enable_ra=True; export ra_plugin=dogtag; export dogtag_version=10; export mode=production; /usr/libexec/ipa-otpd $ldap_uri]
Marked pid [2922] for<EMAIL_ADDRESS>LDAP: ldapi://%2fvar%2frun%2fslapd-EC2-INTERNAL.socket
Socket closed, shutting down...
==> /var/log/krb5kdc.log <==
Jul 22 21:47:07 ip-172-31-28-101.ec2.internal krb5kdc2036: preauth (otp) verify failure: Connection timed out
Jul 22 21:47:07 ip-172-31-28-101.ec2.internal krb5kdc2036: AS_REQ (6 etypes {18 17 16 23 25 26}) <IP_ADDRESS>: PREAUTH_FAILED<EMAIL_ADDRESS>for<EMAIL_ADDRESS>Preauthentication failed
Jul 22 21:47:07 ip-172-31-28-101.ec2.internal krb5kdc2036: closing down fd 12

I also commented out the first line in /data/etc/ipa/default.conf
otherwise this was the log output:
[start<EMAIL_ADDRESS>Running [export [global]; export host=ip-172-31-28-101.ec2.internal; export basedn=dc=ec2,dc=internal; export realm=EC2.INTERNAL; export domain=ec2.internal; export xmlrpc_uri=https://ip-172-31-28-101.ec2.internal/ipa/xml; export ldap_uri=ldapi://%2fvar%2frun%2fslapd-EC2-INTERNAL.socket; export enable_ra=True; export ra_plugin=dogtag; export dogtag_version=10; export mode=production; /usr/libexec/ipa-otpd $ldap_uri]
Marked pid [2826] for<EMAIL_ADDRESS>sh: line 0: export: `[global]': not a valid identifier
LDAP: ldapi://%2fvar%2frun%2fslapd-EC2-INTERNAL.socket
Socket closed, shutting down...

Some more info: When I use google  authenticator I get this error message when adding the token. (centos-7 and fedora-22). Authy allows me to add the token.

Also tried adding the token with FreeOTP - can't login to the admin tools with password+token after setup.

@dmcnaught The "invalid barcode" issue is related to this bug: https://www.redhat.com/archives/freeipa-devel/2015-June/msg00505.html

Notes from mailing list:
@adelton : Can we run systemd in the centos-7 container so that ipa-otp will work?

On Mon, 2015-09-21 at 16:49 -0600, Duncan McNaught wrote:

Dear freeipa-users,
I'm having an issue with otp in freeipa. I can set up the service as
described in the blog post for TOTP or HOTP, and sync the token fine.
When I try to login to the admin tools or an ipa-managed client
(with ) , I get a password incorrect message.
Here are some more details: https://github.com/adelton/docker-freeipa
/issues/34
Can anyone help me to debug/get this working?

I'm very unclear as to what you are trying to do. Are you trying to
run FreeIPA in a container? If so, Jan is probably your man. AFAIK,
ipa-otpd will require systemd in the container.
If you are trying to run this on CentOS 7.1 (not a container), it
seems to me that your LDAP server isn't running or something is wrong
with ldapi.
Can you explain your setup in more detail?

Notes from mailing list:
@adelton : Can we run systemd in the centos-7 container so that ipa-otp will work?

Not yet, it should be possible with Docker 1.9.

Fix for the issue was now pushed to the master branch and also to the rhel-7 and centos-7 branches. The automated builds on the hub are running and updated images should be available shortly.
Sorry it took me so long to resolve the problem.

Great - thanks @adelton


Fix: All Warnings addressed

Now finally I am able to provide a PR that addresses all warnings in one unified PR.
Sorry for the multiple PRs before I had to withdraw.

Hi Michele,
Thanks for work! I've fixed typos in your code and omit more warnings.
I've made another pull request if you do not mind
https://github.com/CANopenNode/CANopenNode/pull/144


Celery Beat ignores a task's options dictionary

Say I decorate a task and pass values to it using the options dictionary
@shared_task(options={'queue': 'low-default'}). Here the queue is set, but other options can be set also. Djcelery will ignore these options when kicking off the task.
A possible solution is to just set a default to the options like so in the scheduler init
self.options = {'queue': model.queue or task_options.get('queue'),
                        'exchange': model.exchange or task_options.get('exchange'),
                        'routing_key': model.routing_key or task_options.get('routing_key'),
                        'expires': model.expires or task_options.get('expires')}

I've been doing that with success.
If that looks good, I'll roll up a PR.

which options do you need should be allowed and which kept off?

Seemed to me the same options that it can pull from the model. This allows the model to override the options in the code.

This issue was fixed in https://github.com/celery/django-celery-beat/pull/34 in the django-celery-beats repo, is this issue still applicable to this repo in particular? @emperorcezar

Don't think so. I'll close.


Replace Ctx datatype by Ctx type family to allow for empty contexts

This is the result of me being curious if there was a way to get rid of Always. Turns out there is by switching to a type family instead. The advantage apart from getting rid of Always is that you could also use multiple constraints in this case by mapping to something like Ctx a = (Eq a, Ord a). The downside is that apparently signatures are checked before type families are expanded so the constraints need to mention Ctx explicitely rather than the constraint it maps to (so we can’t omit constraints syntactically in the empty constraints case after all).
As I mentioned this was just an experiment, so definitely feel free to reject it. I just thought it might be interesting and perhaps useful information for someone given that there aren’t too many backpack projects out there in the wild.
Either way, looks like a really cool project! Keep up the good work!

Thanks for looking into this. Since it ends up leaking Ctx into the public interface, I am going to reject the change, but it's an interesting point in the design space. As a side note, I find it a little disappointing that I even have to write the Data.Set.Unboxed, etc. modules at all. I wish I could just write an indefinite module and then export the instantiate it three times. But, if you do this, you don't get any haddocks, which seriously impacts the ability of end users to work with the library. However, even if we had better haddock generation with backpack, there's still the problem that the Set type from Data.Set.Lifted can technically have a Foldable instance while the other variants cannot (because their elements are constrained). So, the public interfaces do actually end up needing to differ slightly.

Thanks for your quick comment! For the record, the GHC issue for removing the need to change the constraints to Ctx is https://ghc.haskell.org/trac/ghc/ticket/12703. Sadly it hasn’t seen any recent activity so we’re probably stuck with creating dummy classes unless we want to leak type families (which I completely agree is a bad idea).


Add a simple jvm like virtual machine.

Codecov Report

Merging #75 (29b7890) into main (adca63c) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #75   +/-   ##
=======================================
  Coverage   61.64%   61.64%
=======================================
  Files          82       82
  Lines        2988     2988
=======================================
  Hits         1842     1842
  Misses       1146     1146

Impacted Files
Coverage Δ

sources/libs/brutal/io/buf.h
100.00% <ø> (ø)

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 adca63c...29b7890. Read the comment docs.

i'm pretty excited about this OwO

after this pr we will have 994 commits :open_mouth:


Update Docu

@froster82 Some docu changes to verify ;-)
Just a question, what do you prefer: English text to translate or ChatGPT translated text to verify?

@pachi81 , I rephrased the strings a bit. I think I prefer English ones to translate them on my own :) Maybe it's a force of habit for me. I read the English texts anyway to get the right meaning and context.


Builder: Support for fields from parent classes

As a solution for #853 (and peichhorn/lombok-pg#78), I implemented a new feature for (type) builders, so that fields from the parent class can also be set using the builder.
The idea is to generate a constructor on the type that takes a builder as a parameter and uses the fields from the builder to set the fields of the new instance. The Builder.build() method calls this constructor.
The feature must be explicitly switched on, in order to not break existing implementations, which may rely on the all-args constructor generated by @Builder.

@janrieke could you fix merge conflicts and probably it will be merged?

@bitsal: I've tried to get a reply from @rzwitserloot several times, also via email. No success. I will not spend time fixing conflicts as long as don't know how the chances are that this will be included.

@janrieke did you get any news from @rzwitserloot ?

Unfortunately not.
Maybe @rspilker can say something?

@janrieke if @bitsal has write access, maybe he could merge your pull request? With the fixed conflicts of course.

It seems I don't have write access

@rzwitserloot @rspilker can you review this PR? would be great to land this.

I have no idea why I have zero emails on this. Looking at it now.

This needs lots of tests, documentation, changelog, etc. I've fixed the merge issues and done some codereview, as well as made a behavioural change (trying to inherit = true when you have no parent now fails instead of mostly silently doing nothing, I think - testing yet to commence).
Further development of this feature will occur in branch builderParentClass.

@janrieke Can you write a pullreq in branch https://github.com/rzwitserloot/lombok/tree/builderParentClass where you add your name to the AUTHORS file?

Allright, bad news. I'm pretty sure this feature is not gonna make it.
Here's the problem:
You can't use this feature unless you do NOT chain it. The whole point of builders it to chain it, so that makes this feature dead on arrival. Specifically, this must be possible:
Child  c = ChildClass.builder().fieldFromParent1(0).fieldFromChild(1).fieldFromParent2(2).build();
and there's no way to make that work; the fieldFromParent1 method returns a ParentBuilder and not a ChildBuilder. I tried some fancy generics footwork to get out of this, but [A] this gets you a boatload of unsafe casting warnings, [B] by convoluting the type of the builder, makes it basically impossible to use the builder in any way other than one-linering it, and [C] still doesn't work, for some reason the build() method doesn't wanna play ball, feels like a javac/ecj bug to me, but given that both javac and ecj exhibit this bizarre behaviour I guess it is somehow spec. It certainly highlights the usual problem with 'using fancy generics footwork to get out of a typing issue' which is that once you get beyond academic examples it generally just doesn't work well unless you add explicit type params at which point all semblance of utility is right out the window.
What am I missing, here, guys? some 90 thumbsup/hearts/whatsit and a massive pullreq.
Completely our mistake for not tracking pullreqs carefully (we're making changing on that front and will start investigating pullreqs as they come in from here on out), but how would this feature ever have worked?
Specifically, make this code not-ugly, and compile properly, and then we have something to target:
import java.util.List;
public class BuilderWithInherit {
	public static class Parent {
		int field1;

		protected Parent(final ParentBuilder<?, ?> b) {
			this.field1 = b.field1;
		}

		public static class ParentBuilder<Z extends Parent, B extends ParentBuilder<Z, B>> {
			private int field1;

			ParentBuilder() {}

			public B field1(final int field1) {
				this.field1 = field1;
				return (B) this;
			}

			public Z build() {
				return (Z) new Parent(this);
			}
		}

		public static ParentBuilder<Parent, ParentBuilder> builder() {
			return new ParentBuilder<Parent, ParentBuilder>();
		}
	}

	public static class Child extends Parent {
		double field2;

		protected Child(final ChildBuilder<?, ?> b) {
			super(b);
			this.field2 = b.field2;
		}

		public static class ChildBuilder<Z extends Child, B extends ChildBuilder<Z, B>> extends ParentBuilder<Z, B> {
			private double field2;

			ChildBuilder() {}

			public B field2(final double field2) {
				this.field2 = field2;
				return (B) this;
			}

			public Z build() {
				return (Z) new Child(this);
			}
		}

		public static ChildBuilder<ChildBuilder, Child> builder() {
			return new ChildBuilder<ChildBuilder, Child>();
		}
	}

	public static void test() {
		Child x = Child.builder().field1(5).field2(1.0).field1(2).build();
	}
}

@rzwitserloot override all the getters/setters of the parent and redefine the methods with the ChildBuilder as a return.
This is valid:
class A {
        private int a;
        public A a(int a) { this.a = a; return this; }
        public int getA() { return this.a; }
    }
    class B extends A {
        public B a(int a) { super.a(a); return this; }
        public int foo() { return super.getA(); }
    }
    class test {
        public void test() {
            (new B()).a(42).getA();
        }
    }```

Great to have some feedback, although it took a while :)
Yes, the chaining/casting is a problem. I agree that, without solving it, this feature will look quite ugly when used in code. And as Lombok aims at making code nicer, I can understand that you do not want it merged, @rzwitserloot.
However, in the issue thread there was already a suggestion (https://github.com/rzwitserloot/lombok/issues/853#issuecomment-148284229) which seems to be implementable. It looks quite similar to what you suggested above. The generated code will be using generics heavily, which will make it difficult to understand. But as it's generated code, I think that this would be ok.
@rzwitserloot: If you think that such an approach could make it to Lombok, I would try to get that idea implemented.

@aikar That would require resolution which is tricky (lombok needs to run during compilation; asking the compilation process about the methods/fields in some external class is a problem; that's not done yet, and if we wait until it IS done, lombok's too late to add any methods. There are ways around it but they carry a heavy maintenance and performance burden).
@janrieke Assuming the generics can be sorted out, I'm still not convinced. This really uglies up those builders beyond all recognition. The best solution is to override the methods, but that gets back to requiring resolution which makes the maintenance burden too high for the feature.

Using Interfaces to help get around cyclic dependencies on the generics, I was able to get this almost working....
    public interface IParentBuilder<Z extends Parent, B> {
        int field1();
        public B field1(final int field1);
        public Z build();
    }

    public static class Parent {
        int field1;

        protected <Z extends Parent, B extends IParentBuilder<Z, B>> Parent(final ParentBuilder<Z, B> b) {
            this.field1 = b.field1;
        }

        public static class ParentBuilder <Z extends Parent, B extends IParentBuilder<Z, B>> implements IParentBuilder<Z, B> {
            int field1;

            ParentBuilder() {}

            public int field1() {
                return field1;
            }

            public B field1(final int field1) {
                this.field1 = field1;
                return (B) this;
            }

            public Z build() {
                return (Z) new Parent(this);
            }
        }

        public static <T extends ParentBuilder<Child, T>> T builder() {
            return (T) new ParentBuilder();
        }
    }

    public interface IChildBuilder<Z extends Child, B> extends IParentBuilder <Z, B> {
        double field2();
        public B field2(final double field2);
        public Z build();
    }
    public static class Child extends Parent {
        double field2;

        protected <Z extends Child, B extends IChildBuilder<Z, B>> Child(final ChildBuilder<Z, B> b) {
            super(b);
            this.field2 = b.field2;
        }

        public static class ChildBuilder<Z extends Child, B extends IChildBuilder<Z, B>>
                extends ParentBuilder<Z, B> implements IChildBuilder<Z, B> {
            double field2;

            ChildBuilder() {}

            public double field2() {
                return field2;
            }
            public B field2(final double field2) {
                this.field2 = field2;
                return (B) this;
            }

            public Z build() {
                return (Z) new Child(this);
            }
        }

        public static <T extends ChildBuilder<Child, T>> T builder() {
            return (T) new ChildBuilder();
        }
    }

    public static void test() {
        Child x = Child.builder().field1(5).field2(1.0).field1(2).build();
    }

The issue now is clashes in erasure on the builder method :/ If you rename the parent or childs builder method, the code is then valid.
Any ideas to work around that?
@rzwitserloot

A bridge method could solve that final detail right?

@aikar My solution is quite similar, except that I use abstract builder classes instead of interfaces (which I personally find a bit nicer, because you do not have to generate the setter method signature twice). Implemented in this way, there are no compiler warnings, and builder method chaining works nicely.
But I do not see a solution for overriding the builder() method in subclasses. Using generics there as return type compiles: public static <B extends AbstractParentBuilder<?, ?>> B builder()
However, you cannot call such a method from your code, as this produces two different methods, which makes the method call ambiguous for the compiler.
But maybe it's ok to require manually setting a different builder method name on subclasses?

Made it ;)
In this way, it compiles without any warnings, chaining works, and the builder methods can have the same name.
Superclass:
public class Superclass {

    final int field1;

    protected Superclass(final AbstractSuperclassBuilder<?, ?> b) {
        this.field1 = b.field1;
    }

    public static final class Builder extends AbstractSuperclassBuilder<Superclass, Builder> {
        @Override
        public Superclass build() {
            return new Superclass(this);
        }

        @Override
        protected Builder getInstance() {
            return this;
        }
    }

    protected abstract static class AbstractSuperclassBuilder<C, B extends AbstractSuperclassBuilder<?, ?>> {
        private int field1;

        public B field1(final int field1) {
            this.field1 = field1;
            return getInstance();
        }

        protected abstract B getInstance();
        protected abstract C build();
    }

    public static AbstractSuperclassBuilder<? extends Superclass, ? extends AbstractSuperclassBuilder<? extends Superclass, ?>> builder() {
        return new Builder();
    }
}

Subclass:
public class Subclass extends Superclass {

    final double field2;

    protected Subclass(final AbstractSubclassBuilder<?, ?> b) {
        super(b);
        this.field2 = b.field2;
    }

    public static final class Builder extends AbstractSubclassBuilder<Subclass, Builder> {
        @Override
        public Subclass build() {
            return new Subclass(this);
        }

        @Override
        protected Builder getInstance() {
            return this;
        }
    }

    protected abstract static class AbstractSubclassBuilder<C, B extends AbstractSubclassBuilder<Subclass, B>>
        extends Superclass.AbstractSuperclassBuilder<Subclass, B> {
        private double field2;

        public B field2(final double field2) {
            this.field2 = field2;
            return getInstance();
        }

        @Override
        protected abstract B getInstance();
    }

    public static AbstractSubclassBuilder<? extends Superclass, ? extends AbstractSubclassBuilder<? extends Subclass, ?>> builder() {
        return new Builder();
    }
}

It's really crammed with generics and thus not the nicest code. But I think this type of builders will be generatable by Lombok. Or do I miss something?
Should I give it a try implementing, @rzwitserloot?

Just a short status update: Builders with generics on the annotated class turned out to be a bit more complex to generate than expected. However, javac implementation is working now. I just started with the Eclipse implementation.

Any update on this?

Eclipse implementation is finished to most parts. I'm currently setting up several test cases to make sure everything works as expected.
You can watch the progress in the branch https://github.com/janrieke/lombok/tree/superBuilder

I created new pull request #1711.
Further discussions over there. Closing here.


Documentar uiDateMask e uiNfeAccessKeyMask

Vi no código, mas não tem no README ;)

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/9574426-documentar-uidatemask-e-uinfeaccesskeymask?utm_campaign=plugin&utm_content=tracker%2F1022469&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1022469&utm_medium=issues&utm_source=github).

Yes, the documentation is outdated. However the right place to include it is in the gh-pages.

Landed in v1.5.1.
However, the README only lists the undocumented directives.


Allow basic auth for Redis clients

I ran into an issue that seems similar to https://github.com/socketry/async-redis/discussions/35
I have a URL like so:
rediss://:PASSWORD@redis-10954.c246.us-east-1-4.ec2.cloud.redislabs.com:10954

...but in lib/async/job/backend/redis.rb I can't include protocol as in the example.
My config is a bit convoluted, but I believe otherwise working:
    # used for Sidekiq
    config.redis_ssl_params = {
      cert_store: OpenSSL::X509::Store.new.tap { |store|
        store.add_file(Rails.root.join("config/redis.pem").to_s)
      },
      cert: OpenSSL::X509::Certificate.new(File.read(
        Rails.root.join("config/redis.crt")
      )),
      key: OpenSSL::PKey::RSA.new(
        Rails.application.credentials.services.redis.private_key
      ),
      verify_mode: OpenSSL::SSL::VERIFY_PEER
    }

    # building for use in async-job
    config.redis_ssl_context = OpenSSL::SSL::SSLContext.new.tap do |context|
      context.cert_store = config.redis_ssl_params[:cert_store]
      context.cert = config.redis_ssl_params[:cert]
      context.key = config.redis_ssl_params[:key]
      context.verify_mode = config.redis_ssl_params[:verify_mode]
    end

  config.async_job.backend_for "redis_remote" do
		uri = URI(ENV["REDIS_ASYNC_JOB_URL"])
    queue Async::Job::Backend::Redis, endpoint: Async::IO::SSLEndpoint.new(Async::IO::Endpoint.tcp(uri.hostname, uri.port), ssl_context: Rails.configuration.redis_ssl_context)
	end

Perhaps there's an easier way to configure, or maybe we can figure out how to get it working and provide an integration guide, but in any case I'd need to be able to get the password passed through somehow.

Yes, good idea, done :)

Let me apply the previous fix/PR.

Async::Redis::Endpoint is introduced, so this should enable you to provide an endpoint argument with credentials.

I spent a bit of time playing with this, but couldn't quite get things with "just" passing a URL. Here's what I'd like to work:
require 'async/redis'

ssl_context = OpenSSL::SSL::SSLContext.new.tap do |context|
  context.cert_store = OpenSSL::X509::Store.new.tap { |store|
    store.add_file(Rails.root.join("config/redis.pem").to_s)
  }
  context.cert = OpenSSL::X509::Certificate.new(File.read(
    Rails.root.join("config/redis.crt")
  ))
  context.key = OpenSSL::PKey::RSA.new(
    Rails.application.credentials.services.redis.private_key
  )
  context.verify_mode = OpenSSL::SSL::VERIFY_PEER
end

uri = URI("REDIS_URL=rediss://:PASSWORD@redis-12345.c246.us-east-1-4.ec2.cloud.redislabs.com:12345")
endpoint = Async::Redis::Endpoint.new(uri, ssl_context: ssl_context)
client = Async::Redis::Client.new(endpoint)

Sync { puts client.call("PING") }

...but I think the credentials aren't working as I'd like (note there's no username, just a password) so I think I still need to do something like https://github.com/socketry/async-redis/blob/main/examples/auth/protocol.rb myself.
So, I think it's better, but not quite allowing configuring by "just" passing in a URL as expected by Redis.com. FWIW this is the new working example I have:
ruby
require 'async/redis'

ssl_context = OpenSSL::SSL::SSLContext.new.tap do |context|
  context.cert_store = OpenSSL::X509::Store.new.tap { |store|
    store.add_file(Rails.root.join("config/redis.pem").to_s)
  }
  context.cert = OpenSSL::X509::Certificate.new(File.read(
    Rails.root.join("config/redis.crt")
  ))
  context.key = OpenSSL::PKey::RSA.new(
    Rails.application.credentials.services.redis.private_key
  )
  context.verify_mode = OpenSSL::SSL::VERIFY_PEER
end

class AuthenticatedRESP2
	def initialize(credentials, protocol: Async::Redis::Protocol::RESP2)
		@credentials = credentials
		@protocol = protocol
	end

	def client(stream)
		client = @protocol.client(stream)

		client.write_request(["AUTH", *@credentials])
		client.read_response # Ignore response.

		return client
	end
end

uri = URI("REDIS_URL=rediss://:PASSWORD@redis-12345.c246.us-east-1-4.ec2.cloud.redislabs.com:12345")
endpoint = Async::Redis::Endpoint.new(uri, ssl_context: ssl_context)
client = Async::Redis::Client.new(endpoint, protocol: AuthenticatedRESP2.new(["PASSWORD"]))

Sync { puts client.call("PING") }

Note I just have to define AuthenticatedRESP2 and pass the PASSWORD in manually, then it's working.

For the record, this is now fixed with tests, and the documentation updated.


ARROW-10526: [FlightRPC][C++] Client cookie middleware

Added client cookie middleware which caches and monitors expiry
Added testing for client cookie middleware

@lidavidm
Hi David, when you have some time please take a look at the changes I have introduced here. As you can probably tell, this is adds a client side middleware for cookie handling in C++. I am still waiting for the CI to complete so I can make sure that it is good on all platforms, but the code structure should not change much from here unless changes are requested.
Thank you!

There appears to be a failure in the python build, I think it's caused by something unrelated to this pull request though, I noticed the same here: https://github.com/apache/arrow/runs/1456411775?check_suite_focus=true

@lidavidm That's a really good point, there is a lot of code that wasn't facing direct testing. I followed suggestion of moving the parsing logic to an internal header (the client_header_internal files seemed appropriate since this code is all related to headers). I added a bunch of tests for all the different internal parsing functions that were added.


Add user groups to autocomplete list

Trying to at-mention a user group does not work as we do not support user groups.
We now have the data for user groups in store, so adding this is straightforward.

Implemented in #2602 .


Add Mastodon extension

Description
Raycast Extension for Mastodon

Features:

Write status with markdown support.(Only if the instant supports Markdown)
Publish simple status with text.
Publish scheduled status with natural date format.
Publish status with attachments (image, video, files); add alt text to the image when only one image is attached.
Save draft status.
View your bookmarked statuses.
View your latest statuses.
Open the latest published status that was published from Raycast through the actions.

Screencast
Login
Input your Mastodon instance's URL, then click the "Continue" button in the bottom-right corner.

Add simple status with text

Add scheduled status

Add status with image and alt text

View your latest status

Mark status as sensitive
Toggle the "Sensitive" checkbox to mark the attached image as sensitive, or add a content warning to the status.

Write status with markdown
Toggle the "Markdown" checkbox to render markdown in the text file. Markdown shortcuts are also supported (e.g., pressing ⌘ + B will add **bold** around the selected text, ⌘ + I will make the selected text italic, etc.).

Draft status

Available Settings

If the instance supports Markdown, please select the Built-in Markdown Support checkbox.
Status limit
Based on performance considerations, the number of statuses displayed is limited, with the default being 20. You can adjust this limit in the extension settings.

Actions

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

@BasixKOR has been working on #5001 for some time and it seems like it’s almost ready.
Now we also have #6117 and #6156 in the queue, we need to decide what to do with all three, are you up for selecting the best version and going with that and improving with the feature respectably from the other PRs?

Assistance would be very appreciated (as you may have noticed). It seems like your extension has markdown features for Glitch or other forks and attachments. Those features are currently missing in my PR, but I'd happily implement them for my extension.
Would you mind if I took some of your code to implement those?

Assistance would be very appreciated (as you may have noticed). It seems like your extension has markdown features for Glitch or other forks and attachments. Those features are currently missing in my PR, but I'd happily implement them for my extension.
Would you mind if I took some of your code to implement those?

Never mind. Feel free to do whatever you like with this codebase.

Are we going with this or yours @BasixKOR as base?


Working with Modules (as namespaces)

Environment
Crystal 0.31.0 (2019-09-24)
LLVM: 8.0.1
Default target: x86_64-apple-macosx

Issue
Where it works has expected here;
class D1
  def initialize
    puts "Hi from D1"
  end
end

class D2
  def initialize(@d1 : D1); end
end

D2.new(D1.new) #Hi from D1

Syringe.injectable(D1)
Syringe.wrap(D2)

D2.new #Hi from D1

I'm having some trouble getting it to work with Modules;
module A
  class A1
    def initialize
      puts "Hi from A::A1"
    end
  end
end

module B
  class B1
    def initialize(@a1 : A::A1); end
  end
end

B::B1.new(A::A1.new) #Hi from A::A1

Syringe.injectable(A::A1) #ERR: Called macro defined in macro 'injectable'; def Syringe.getA::A1; Error: unexpected token: ::
Syringe.wrap(B::B1)

..and trouble getting it to work from within Modules;
module C
  class C1
    def initialize
      puts "Hi from C::C1"
    end
  end

  class C2
    def initialize(@c1 : C1); end
  end

  Syringe.injectable(C1) #ERR: Called macro defined in macro 'injectable'; return C1.new; Error: undefined constant C1
  Syringe.wrap(C2)
end

C::C2.new(C::C1.new) #Hi from C::C1

C::C2.new

I've had limited success in using Providers here —which works for a single namespace, but not for dependencies across namespaces. Probably something I've missed, is there a canonical way in using this lib with namespaces?

I found this bug a while back and am working on a patch already I just haven't had time to finish. Let me see if I can get a PR up.

@stergiom https://github.com/Bonemind/syringe/pull/3 Is my first attempt. The code is pretty gross and will go back but does this fix your issue?

Thanks @elliotize, can confirm that this does work for my one-namespace-deep use-case, also works fine for Classes I'd like to have behave as Singletons, currently have that wrapped up for convenience;
macro define_singleton_di_providers(*klasses)
  {% for klass in klasses  %}
    module {{ klass.id.split("::").reject { |k| k == klass.id.split("::").last}.join("::").id }}
      class {{ klass }}Provider
        Syringe.provide({{ klass }})

        @@instance = {{ klass }}.new

        def self.getInstance
          @@instance
        end
      end
    end

    \{% if !{{klass}}.methods.select { |m| m.name == "initialize" }[0].args.empty? %}
      Syringe.wrap({{ klass }})
    \{% end %}
  {% end %}
end

..this too could probably be improved.

Sorry for the radio silence, was on a vacation.
I'll have a look into both the issue, and the PR from elliotize soon

@stergiom I am working on my Spectrum Shard which is an async/domain event system using Syringe and realized I too have use for a singleton. Are you planning on making a PR to this repo or do you have another Shard you are adding it to.

To be frank, I've only just started fiddling with Crystal and had not considered it. I've dropped a quick'n dirty off at https://github.com/Bonemind/syringe/pull/5, really just convenience macros for using as light IoC containers, but unsure about the scope/direction of Syringe to say whether this would be useful to add;
Syringe.define_singleton_providers(
  UseCase::DoAThing,
  UseCase::DoSomeOtherThing
)

*spec should pass on your module/namespace branch.

If it's just singelton behaviour that you're after, self.getInstance pointing to a class variable that is an instance might be all you need?

For singletons I'd expect a provider which returns an instance to indeed work.
And for the scope of syringe: Primary goal is to provide an easy to digest/use DI shard which does not do much more than that, so it should be complete enough to be usable, but the documentation, and more importantly, setup of the shard itself should be simple and not require any/much config beyond pointing to classes that can be injected and want to be injected into.
Onto the issue itself, good find, I've left a comment on the PR of elliotize, and I'm thinking how we can keep this code a bit more manageable. It looks like the pr of @elliotize works for N deep, so if we can figure out readability i'll merge.


Jest stop working

running jest doest execute the test scripts.
"use strict";

// Do this as the first thing so that any code reading it knows the right env.
process.env.BABEL_ENV = "test";
process.env.NODE_ENV = "test";
process.env.PUBLIC_URL = "";

// Makes the script crash on unhandled rejections instead of silently
// ignoring them. In the future, promise rejections that are not handled will
// terminate the Node.js process with a non-zero exit code.
process.on("unhandledRejection", err => {
  throw err;
});

// Ensure environment variables are read.
require("../config/env");

const jest = require("jest");
const argv = process.argv.slice(2);

// Watch unless on CI or in coverage mode
// if (!process.env.CI && argv.indexOf('--coverage') < 0) {
//   argv.push('--watch');
// }

jest.run(argv);

env.js
"use strict";

const fs = require("fs");
const path = require("path");
const paths = require("./paths");

// Make sure that including paths.js after env.js will read .env variables.
delete require.cache[require.resolve("./paths")];

const NODE_ENV = process.env.NODE_ENV;
if (!NODE_ENV) {
  throw new Error("The NODE_ENV environment variable is required but was not specified.");
}

// https://github.com/bkeepers/dotenv#what-other-env-files-can-i-use
var dotenvFiles = [
  `${paths.dotenv}.${NODE_ENV}.local`,
  `${paths.dotenv}.${NODE_ENV}`,
  // Don't include `.env.local` for `test` environment
  // since normally you expect tests to produce the same
  // results for everyone
  NODE_ENV !== "test" && `${paths.dotenv}.local`,
  paths.dotenv,
].filter(Boolean);

// Load environment variables from .env* files. Suppress warnings using silent
// if this file is missing. dotenv will never modify any environment variables
// that have already been set.
// https://github.com/motdotla/dotenv
dotenvFiles.forEach(dotenvFile => {
  if (fs.existsSync(dotenvFile)) {
    require("dotenv").config({
      path: dotenvFile,
    });
  }
});

// We support resolving modules according to `NODE_PATH`.
// This lets you use absolute paths in imports inside large monorepos:
// https://github.com/facebookincubator/create-react-app/issues/253.
// It works similar to `NODE_PATH` in Node itself:
// https://nodejs.org/api/modules.html#modules_loading_from_the_global_folders
// Note that unlike in Node, only *relative* paths from `NODE_PATH` are honored.
// Otherwise, we risk importing Node.js core modules into an app instead of Webpack shims.
// https://github.com/facebookincubator/create-react-app/issues/1023#issuecomment-265344421
// We also resolve them to make sure all tools using them work consistently.
const appDirectory = fs.realpathSync(process.cwd());
process.env.NODE_PATH = (process.env.NODE_PATH || "")
  .split(path.delimiter)
  .filter(folder => folder && !path.isAbsolute(folder))
  .map(folder => path.resolve(appDirectory, folder))
  .join(path.delimiter);

// Grab NODE_ENV and REACT_APP_* environment variables and prepare them to be
// injected into the application via DefinePlugin in Webpack configuration.
const REACT_APP = /^REACT_APP_/i;

function getClientEnvironment(publicUrl) {
  const raw = Object.keys(process.env)
    .filter(key => REACT_APP.test(key))
    .reduce(
      (env, key) => {
        env[key] = process.env[key];
        return env;
      },
      {
        // Useful for determining whether we’re running in production mode.
        // Most importantly, it switches React into the correct mode.
        NODE_ENV: process.env.NODE_ENV || "development",
        // Useful for resolving the correct path to static assets in `public`.
        // For example, <img src={process.env.PUBLIC_URL + '/img/logo.png'} />.
        // This should only be used as an escape hatch. Normally you would put
        // images into the `src` and `import` them in code to get their paths.
        PUBLIC_URL: publicUrl,
      }
    );
  // Stringify all values so we can feed into Webpack DefinePlugin
  const stringified = {
    "process.env": Object.keys(raw).reduce((env, key) => {
      env[key] = JSON.stringify(raw[key]);
      return env;
    }, {}),
  };

  return { raw, stringified };
}

module.exports = getClientEnvironment;

jest -v
23.1.0
node -v
v8.11.2
npm -v
5.6.0

Found the fixed. Uninstall watchman solved the issue.
brew uninstall watchman

You should be good with just clearing watchman cache

@thymikee how do you clear watchman cache?


Build compatibility for Linux OSs with LIBDIR=lib64

Amazing work on this treerite crate!
Problem:
Building on Amazon Linux 2/other RedHat-derived distros (x86-64) failed because the default CMAKE_INSTALL_LIBDIR=lib64. I'm not familiar with CMake, but this dir is lib by default for Ubuntu but lib64 for other distros—it seems very case-by-case.
As a result, the search directory (/path/to/cargo/project/target/debug/build/treerite-49cc21405edc7651/out/lib) as defined in line 12 of build.rs  doesn't exist under that name; the library is in .../out/lib64.
Error message:
   Compiling treerite v0.1.3 (https://github.com/dovahcrow/treerite#893d6e90)
     Running `rustc --crate-name treerite --edition=2018 /home/ec2-user/.cargo/git/checkouts/treerite-60cb798f712ec7e5/893d6e9/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C debuginfo=2 --cfg 'feature="default"' --cfg 'feature="free_panic"' --cfg 'feature="static"' -C metadata=0e14c6fb393d182b -C extra-filename=-0e14c6fb393d182b --out-dir /path/to/cargo/project/target/debug/deps -L dependency=/path/to/cargo/project/target/debug/deps --extern [...] --cap-lints allow -L /path/to/cargo/project/target/debug/deps -L /path/to/cargo/project/target/debug -L /home/ec2-user/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib -L /home/ec2-user/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib -L /path/to/cargo/project/target/debug/build/treerite-49cc21405edc7651/out/lib -l static=treelite_runtime_static -l stdc++ -l gomp`
error: could not find native static library `treelite_runtime_static`, perhaps an -L flag is missing?

Solution:
We can standardize CMAKE_INSTALL_LIBDIR to compile into lib as an additional -D flag to CMake in lines 9 & 21 of build.rs.
let dst = cmake::Config::new("treelite")
        .define("BUILD_STATIC_LIBS", "ON")
        .define("CMAKE_INSTALL_LIBDIR", "lib") <<<<
        .build();

Also: The dynamic library did not build, switching dynamic—>dylib fixes that. (see Cargo Book)

bump. can we merge this?


Added new 'jerry_value_instanceof' API function.

JerryScript-DCO-1.0-Signed-off-by: László Langó<EMAIL_ADDRESS>

Closing PR to prevent merging. Let's discuss and make decision on #2746 first.


Fix bug that happened in standup

The back button only works if you actually prompt when you return true in shouldPrompt. This step wasn't prompting when it should've been (we can at least prompt and let them select + Create new local app setting

Good question. I'll look into it tomorrow


Turn deprecation warnings into logs

Deprecation warnings in the latest 3.x versions make my app look like it's broken, while it works perfectly. I know that these warnings only appear in development, however they bring a lot of noise and potentially hide real errors.
Is it possible to turn these warnings into console.log() messages instead of console.error()?

[x] This is not a v0.x issue.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior 🤔
Use code from 3.0 with the latest 3.x without error (because of semver)
Current Behavior 😯
Using an old Typography variant (like <Typography variant="title" />), or a <TableCell numeric />, or a raised Button raises error in the console:

Context 🔦
I'm migrating react-admin from material-ui v1 to material-ui v3 (cf https://github.com/marmelab/react-admin/pull/3102). And I can't find a syntax that works for both versions :(

@fzaninotto This is a prop-type warning. I would encourage you to move the discussion to prop-types: https://github.com/facebook/prop-types/blob/e32c4900f5ab5fd3acea93e9d2f0d09e4a2f2ceb/checkPropTypes.js#L20.

There is no syntax that works with both versions. The simplest is probably to jump from v1 to v4.

By the way, if you want to comment on https://spectrum.chat/material-ui/general/what-do-you-guys-think-about-the-tables-and-how-they-are-handled-in-material-ui~27c0b5be-9cea-4e8f-88bc-faaf4103bf33. It would be appreciated.

Allow me me disagree.
If I made a mistake with a proptype, I find it normal that the console shows an error - it's my mistake.
If I wrote code with material ui v3 and it works without error, I find it normal that the console shows no error when I upgrade to a minor release.
The current behavior is really misleading: the console shows error while the code works perfectly and will continue to work fine in all 3.0 releases. That's a break of the semver semantics.

This is a prop-type warning. We try to follow the convention.

There is no standard for deprecation warnings that I know of. You chose to use PropTypes for these, but it's an implementation detail.

The simplest is probably to jump from v1 to v4.

No, because V1 and V3 are almost compatible (except for Firefox), while you're still busy adding instructions to the V4 upgrade guide.

There is no standard for deprecation warnings that I know of. You chose to use PropTypes for these, but it's an implementation detail.

@fzaninotto We hope we can use React.warn in v5 for this problem. React will introduce a new method that shows the stack trace when warning: https://github.com/facebook/react/pull/15170.

Maybe you can upgrade to a v3 version that doesn't has the deprecation warnings?

Is it possible to turn these warnings into console.log() messages instead of console.error()?

We might want to use console.warn. console.log is too weak.

The most important constraint we have considered when adding the deprecation warning was to show the component stack trace. The only option we had was the prop-types warning, that happens to use console.error. I think that console.warn would be better here. (We were using the same strategy in v0.x).

Maybe you can upgrade to a v3 version that doesn't have the deprecation warnings?

That's a good idea, but:

Which version is it?
It's not me who is going to upgrade to v3, it's the react-admin user base. I find it hard to explain them that react-admin supports v3.a but not v3.b because there are some breaking changes, while you say that you support semver...

I understand that you're deeply involved in v4 and that v3 might not be a priority for you, but I insist that this is a BC break.
Would it help if I submitted a PR to master?

@fzaninotto What about upgrading to v3, accepting v1 in the dependency range but fixing the deprecating warnings?

How can I fix the deprecations warnings? The code would stop working on V1.

I don't see the problem with react-admin introducing deprecation warnings to the users in a minor version bump.

I agree if these are warnings. But your deprecation warnings are actually console errors.

Correct. This stratategy can't work. It's not backward compatible. What you want is an option to disable the deprecation warnings. console.log would probably still be too noisy.

I don't mind a console.log.

And your users?

Is this a public API? Maybe we could feature detect the API?

Is this a public API? Maybe we could feature detect the API?

I don't understand your question. I gave an example code that triggers the error in the description: <TableCell numeric />. This is called by react-admin's <NumberField />, which is public API.

console.log for deprecation wrnings isn't a problem because:

it only appears in development
it doesn't make CI builds fail

Also you and I actually need a communication channel to warn about deprecations. react-admin uses console.warn() for that.

Import * from @material-ui/core/utils/reactHelpers.
See if setRef is defined.
defined => v3. not defined => v1

It's not perfect, setRef was introduced in v3.1.1.

react-admin uses console.warn() for that.

So why should Material-UI use console.log?

Oh, console.warn() is fine, too ;)

It's not perfect, it's a rough approximation. setRef was introduced in v3.1.1, the deprecation latter on.

I appreciate that you try to find a solution for react-admin, but again, I think this is a bug in material-ui. A minor version should not cause errors on code created for a lower version.

A minor version should not cause errors on code created for a lower minor version.

These are not actual errors. These are warnings that are logged via console.error.
We want to move things like deprecation warnings to use React.warn. Right now we don't have another choice than using warning and propTypes.

These are not actual errors. These are warnings that are logged via console.error.

For my CI, it makes no difference. I haven't released a react-admin version that supports material-ui v3, but I'm ready to bet that for the react-admin users, it won't make any difference, either.

Right now we don't have another choice than using warning and propTypes.

I don't understand why. If react-admin uses console.warn(), why can't you do it, too?
But it seems we don't agree so I won't bother you guys anymore. I'm just sorry you don't follow semver more carefully.

I'll just add one remark: the deprecation warnings are not all equal regarding noise. See this extract of my console:

If you insist on logging errors for deprecations, could you at least do it in the less-cumbersome way (first example) instead of the super noisy one (second example)?

It was designed on purpose to have the component stack trace, hence it's verbose.

If react-admin uses console.warn(), why can't you do it, too?

But it seems we don't agree so I won't bother you guys anymore. I'm just sorry you don't follow semver more carefully.

We can disagree but lets not make this conversation accusatory. If you want to fail on console.error then this is your choice. A react app won't crash by default if a console.error is logged. Hence adding those warnings is not a Semver breaking change. We only add deprecation warnings in minor releases which is exactly what SemVer defines.
Using console.warn won't help anybody because you will get the stack trace from react internals. They give you no clue where the warning originated.

If you insist on logging errors for deprecations, could you at least do it in the less-cumbersome way (first example) instead of the super noisy one (second example)?

The component stack isn't noise. It's information that helps you locate the issue. This is common in react. I don't understand why you consider it noise all of the sudden.
I understand that these can be frustrating. In a perfect world (php did this right) deprecation warnings would have their own log level. Maybe we can re-evaluate the message format so that you easily hide deprecation warnings by looking for a Material-UI Deprecation Warning in the message and hide those.
Once React.warn is available we can provide component stacks via console.warn instead of relying on propTypes validation. But if this lands we need to include our caching solution for these messages and make sure we support earlier react versions.

I didn't want to sound accusatory, sorry if I did. So let me rephrase:

I'm just sorry you don't follow semver more carefully.

as

I'm just sorry you don't follow semver the same way as I do, which is to guarantee that a minor upgrade will not break existing code, including by raising new errors.

As for using console.error instead of console.warn because it has a stack trace, I understand that you're doing the opposite trade-off in material-ui as I did in react-admin: improve the upgrade path for future versions while making the upgrade path to the current version harder.
These differences in interpretation prevent me from publishing a minor version of react admin that raises new errors, so they prevent react-admin from using material-ui v3.

If you want to blame Material-UI for react admin using v1 instead of v3, why not, It's fine with me. As long as the migration to v4 can be smooth, I'm happy :).

I am very confused about those console errors and it's not clear to me how to get rid of them. They are very noisy, I can't easily see the console errors I actually need to care about. I can't influence the deprecation warnings myself, because they're caused by a 3rd-party library (react-admin).
Maybe consider hiding them behind a config flag next time, or do it like Vue and provide a specific migration build/package.

Why couldn't we use console.warns? They have existed in the browser for quite a while.


Bulk data donation POST endpoint

AS a data donor, I want to upload my data using a Web UI or a RESTful Web API.

close with #56


The account or account/partition combination is not recognized!

I encountered a problem where I provided the correct partition and account name, but they seem to be unrecognized by the system. Here’s the command I used:
snakemake --workflow-profile /home/u2204084007/RNA/cofig/profile --configfile cofig/config.yaml --profile profile
/home/u2204084007/RNA/cofig/profile/config.yaml：

default-resources:
slurm_partition: "c01"
slurm_account:   "u2204084007"

/home/u2204084007/.config/snakemake/profile/config.yaml:

executor: slurm
jobs: 100

The output indicates that the profiles are being used for setting default command line arguments:
Using profiles profile and workflow specific profile /home/u2204084007/RNA/cofig/profile for setting default command line arguments.
Building DAG of jobs...

However, there’s a warning that Snakemake is being run in a SLURM job context, which is not recommended:
You are running snakemake in a SLURM job context. This is not recommended, as it may lead to unexpected behavior. Please run Snakemake directly on the login node.
SLURM run ID: e4aa40d6-e26b-4558-a3f8-d614ef095b92

The system proceeds to list the jobs and selects 9 jobs to execute. One of the jobs, copy_input, is detailed with the specified resources, including the partition and account:
rule copy_input:
    input: rawdata/T21-1R_FRAS190282952-1a_1.clean.fq.gz
    output: fastq/raw/T21_1.L001.R1.fastq.gz
    jobid: 28
    reason: Missing output files: fastq/raw/T21_1.L001.R1.fastq.gz; Code has changed since last execution
    wildcards: sample=T21_1, lane=L001, pair=R1
    resources: mem_mb=5622, mem_mib=5362, disk_mb=5622, disk_mib=5362, tmpdir=<TBD>, slurm_partition=c01, slurm_account=u2204084007, io=1

Despite providing the correct partition (c01) and account (u2204084007), the job submission fails with a WorkflowError:
No wall time information given. This might or might not work on your cluster. If not, specify the resource runtime in your rule or as a reasonable default via --default-resources.
WorkflowError:
SLURM job submission failed. The error message was sbatch: error: invalid account or account/partition combination specified
sbatch: error: Batch job submission failed: Unspecified error

This error suggests that there is an issue with the account or partition combination, even though they appear to be correctly specified.

In relation to this issue, it’s important to note that I am not allowed to perform any operations on the login node. Therefore, in practice, I first log into a compute node using salloc, and then from the compute node, I attempt to run the following command:
snakemake --workflow-profile /home/u2204084007/RNA/cofig/profile --configfile cofig/config.yaml --profile profile

Regarding #113, it seems that @cmeesters mentioned potential issues with environment inheritance or that Snakemake is practically dormant. I am uncertain whether these are the primary causes of the error I am encountering.


Remove Jamendo

Fixes

Fixes #124 by @TimidRobot
Description
Redirect the user which checked "use for commercial purposes" to licensing.jamendo which contains music that can be used for commercial purposes and played in public places
Technical details
The editing was in search.js file
Tests
I replace the url that tagged for Jamendo in the right condition in the search.js file as well as i  made some changes of the additional letters/symbol which they putted in the url, that be work well with that licensing.jamendo
Screenshots
https://user-images.githubusercontent.com/66481905/197054016-b7a4abb8-d424-4711-9fe5-1cb357b2e4cb.mov
Checklist

[x] My pull request has a descriptive title (not a vague title like Update index.md).
[x] My pull request targets the default branch of the repository (main or master).
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[ ] I added or updated tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[x] I tried running the project locally and verified that there are no
visible errors.

Developer Certificate of Origin

For the purposes of this DCO, "license" is equivalent to "license or public domain dedication," and "open source license" is equivalent to "open content license or public domain dedication."

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

@Rubadel Thanks for the contribution, but before it could move toward being reviewed effectively it needs to be brought up to current with the base branch. Please do so when you have time. ❤

@Rubadel Hi!
You have a number of files unrelated to this project that are included in this PR. I suggest you make a fresh branch and submit a fresh PR with only the relevant files. (see the Files Changed tab on the PR to reference what I'm talking about)


React Native: Observables and PubSub

Do you want to request a feature or report a bug?
This appears to be a bug.
What is the current behavior?
When subscribing to a topic as suggested in the Amplify docs, react native gives the error: TypeError: One of the sources for assign has an enumerable key on the prototype chain. Are you trying to assign to a prototype property?
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. Your bug will get fixed much faster if we can run your code and it doesn't have dependencies other than AWS Amplify.
import Amplify, { PubSub } from 'aws-amplify';
import { AWSIoTProvider } from 'aws-amplify/lib/PubSub/Providers';
Amplify.addPuggable(new AWSIoTProvider({
        aws_pubsub_region: "VALID_REGION",
        aws_pubsub_endpoint: "VALID_ENDPOINT",
      })
);
PubSub.subscribe('someTopicLiteral').subscribe((msg) => console.log(msg));
// or
PubSub.subscribe('someTopicLiteral2').subscribe({next: (msg) => console.log(msg)});

What is the expected behavior?
PubSub would subscribe to the topic with the specified listener.
Which versions of Amplify, and which browser / OS are affected by this issue? Did this work in previous versions?
iOS React Native, with Amplify ^0.2.11. I don't believe PubSub existed in previous versions
You can turn on the debug mode to provide more info for us by setting window.LOG_LEVEL = 'DEBUG'; in your app.

Same here I am using
"dependencies": {
"aws-amplify": "^0.3.3",
"aws-amplify-react": "^0.1.43",
"aws-amplify-react-native": "^0.2.9",
"react": "16.3.1",
"react-native": "0.55.3"
},
and
PubSub.subscribe('myTopicTest').subscribe({
next: data => console.log('Message received', data),
error: error => console.error(error),
close: () => console.log('Done'),
});
Throws that error.
Can not figure out a way around it  :(.

Having same issue over here.Happens as early as the first function call
PubSub.subscribe('myTopic');
/*
[Unhandled promise rejection: TypeError: One of the sources for assign has an enumerable key on the prototype chain. Are you trying to assign a prototype property? We don't allow it, as this is an edge case that we do not support. This error is a performance optimization and not spec compliant.]
*/

Found the source of the error
    var canonicalRequest = canonical_request({
        method: 'GET',
        url: url.format(__assign({}, parsedUrl, { query: __assign({}, parsedUrl.query, queryParams) })),
        headers: signedHeaders,
    });

inside signUrl in Signer.js
parsedQuery has things on the prototype that are being improperly assigned (from the 'url' npm package)

Any update om this issue. This is a stopper for PubSub aws-amplify use.

If you want a hacky workaround in the meantime (I needed one), go into/node_modules/aws-amplify/lib/Common/Signer.js
and around line 248 change
 var canonicalRequest = canonical_request({
        method: 'GET',
        url: url.format(__assign({}, parsedUrl, { query: __assign({}, parsedUrl.query, queryParams) })), // this line
        headers: signedHeaders,
    });

to
var canonicalRequest = canonical_request({
        method: 'GET',
        url: url.format(__assign(parsedUrl, { query: __assign({}, parsedUrl.query, queryParams) })),
        headers: signedHeaders,
    });

Now after
PubSub.subscribe('myTopicTest').subscribe({
        next: data => console.log('Message received', data),
        error: error => console.error(error),
    close: () => console.log('Done'),
  });

I get
Possible Unhandled Promise Rejection (id: 0):
Object {
"errorCode": 1,
"errorMessage": "AMQJSC0001E Connect timed out.",
"invocationContext": undefined,
}
Any hints?

Yeah, I ran into that right after moving forward. Going to take a leap and say it's the same issue:
Assuming you ran the
aws iot attach-principal-policy --policy-name 'myIOTPolicy' --principal '<YOUR_COGNITO_IDENTITY_ID>' to attach the policy to IoT Core,
you also then have to connect your cognito group to an IoT policy (they left this step out of the docs).
For testing sake, if you add the full AWSIoTFullAccess policy to your Cognito user pool you're using and try to connect, it should work. I'm still thinking about out how to write a good policy for the user pool in the meantime.

Have to connect a cognito group to an IoT policy?

I have finally receiving messages from  mqtt subscribe but I had to modify the myIOTPolicy to
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": "iot:",
"Resource": ""
}
]
}
Thanks johnrjj

dennis-b,
Besides the creation of a policy in aws IOT Core which is attached to a "Thing". The same or another policy with similar permissions should be attach to your cognito pool user too in order to get the mqtt messages.
For the test purposes try
{
"Action": "iot:*"
...
...
}
in your policy.

@richardlevano thanks man, it works working.
but now i see that the messages is not perssist, when my mobile phone is off line then the messages wis not delivered, ahh i will try to create new ticket on this one

In my case the mqtt message also stopped due to the disconnection of the secure websocket (wss).
So you will probably have to try to keep the connection alive.....perhaps a keepalive publish on regular intervals.

eventually i implemented my one MqttOverWSProvider with paho.mqtt.javascript and recconect that looks like this :
 client.onConnected = (reconnect, uri) => {       if (reconnect) {         targetTopics.forEach(topic => { client.subscribe(topic) })        }     }
it  still not supporting offline mode, but it works after reconnect now

This is still an issue on the current version of aws-amplify. Had to apply the small fix to Signer.js otherwise TypeScript complains.

Just ran into this issue. Any progress?

Fix is already published on aws-amplify@unstable (1.1.4-unstable.2)


Purge via native app does not apply

A mind-boggling issue where the NVRAM power pref variable does not apply when the binary is called via a script, which in turn is called via a native macOS app. Boot args are applied fine, so the cause of this is unknown.

According to Apple Developer Relations, **nvram... ** may be doing async work, thus causing problems when the calling thread exits sooner. Did solve a few problems, but still a No-Fix for now.

Ceasing efforts for UI-based application.


added support for amazon s3 cdn #149

See #149

Hey @luceos I applied the changes 👍

@mattmezza can you make sure you pushed the last changes? I'm only seeing your first commit.
Thanks for your patience, I'll get this merged asap.

@luceos really sorry about that. I was working on a trip and pushed to the wrong branch. Changes should be visible to you now

@mattmezza no worries, I was very confused about not seeing anything new, but this is AOK!


Stop polly on test_skip events

On jest-circus, it looks like test_start is fired even if a test is going to be skipped, and then test_skipped is fired right after it.
We were getting "overlapping polly instance" errors until locally patching jest-enviornment-polly to also tear down when test_skipped goes by:
      if ((event.name === "test_done" || event.name === "test_skip") && this.pollyGlobals.pollyContext.polly) {
        await this.pollyGlobals.pollyContext.polly.stop();
        this.pollyGlobals.pollyContext.polly = null;
      }

Fwiw I'm surprised that test_start is fired for skipped tests, but :shrug: , I assume it's a jest-circus change, given we didn't have this issue on jest 26.

Hmmm, yeah, can confirm, thanks for reporing the issue! This sounds like a possible unintentional breaking change in jest, I'll try to create a small repro, find when it started and open an issue on their side. Even if it was intentional, I'd want to hear from them why the change was made to better understand how to handle it, I'd prefer this library not to start and then teardown polly if the suite is skipped if possible to avoid that

Ah yeah, good idea to follow up with Jest!

Okay, so seems like this was happening all the way back even with jest-circus@25 so I'll add a fix for now that starts polly in all cases and stops it if the test was skipped. It's a bit unfortunate though that this needs to happen, so I'll think about how this can be handled better in the future when I have a bit more time to focus on this stuff

Great, thanks!


Creating foreign key in a migration with references/2 leads to FunctionClauseError

If I add a foreign key which references the id (contains UUIDs) column with
references(:tblname, type: uuid)
a FunctionClauseError is raised in lib/ecto/adapters/postgres/connection.ex:525 when I try to migrate. Considering that I'm passing a reference to column_type/2, I would expect that the function should have pattern matched on the first definition in line 519, rather than the third.

Can you provide the complete example of your migration just so we are sure?

Of course, when I'm copying my migration and decide to try one final thing, I find my error. I defined a type when adding the reference (add :fkey, :uuid, references(:tblname, type:uuid) rather than add :fkey references(:tblname, type:uuid)
That way, the reference was passed to column_type as the options, rather than as the first argument.


this is the new error which error when the keybord is open

unimplement error see also : http //flutter .dev.docs/ testing/errors

Hi @khubabcreation
When opening an issue, please try to provide all or some of the information indicated in the template so that we can address this issue properly (See appropriate template here)
Closing this issue, since no information has been provided. Once you updated the issue with more information, please write in the comments and I will re-open this for further discussion. Thanks!


constraint_name for PostgreSQL is not quoted

https://github.com/liquibase/liquibase/blob/1cec0a95810ba881707e97cc989956511a7712e8/liquibase-core/src/main/java/liquibase/sqlgenerator/core/DropPrimaryKeyGenerator.java#L64
I use PostgreSQL 12.2, liquibase 3.8.8 and I have a changeset with objectQuotingStrategy="QUOTE_ALL_OBJECTS" and <dropPrimaryKey tableName="CardToken"/> command (without constraintName). But when I run liquibase update, I get the following error:
Error: ERROR: constraint "cardtoken_pkey" of relation "CardToken" does not exist   Where: SQL statement "alter table "public"."CardToken" drop constraint CARDTOKEN_PKEY" PL/pgSQL function inline_code_block line 7 at EXECUTE [Failed SQL: (0) DO $$ DECLARE constraint_name varchar; BEGIN   SELECT tc.CONSTRAINT_NAME into strict constraint_name     FROM INFORMATION_SCHEMA.TABLE_CONSTRAINTS tc     WHERE CONSTRAINT_TYPE = 'PRIMARY KEY'       AND TABLE_NAME = 'CardToken' AND TABLE_SCHEMA = 'public';     EXECUTE 'alter table "public"."CardToken" drop constraint ' || constraint_name; END $$;] ;]
Constraint CARDTOKEN_PKEY really exists. But in the code, it is substituted without quotes. I think this is the problem.
┆Issue is synchronized with this Jira Bug by Unito

Thanks for submitting this issue!

@kryzha4ok Thanks again for submitting this issue. We are taking a look at the issues and putting plans in place to solve them.

Checked this issue with newer liquibase verision (4.3.1) against Postgresql 12 and 13 versions. Seems like the issue is not actual anymore. No error was thrown.
Example of the changeset:

Hi there,
I ran into the same problem when I upgraded to liquibase 4.4.3 from 3.10.2.
I use postgresql 9.5 (but also tried with 12.8).
My changeset looks like this:
`

    <dropPrimaryKey schemaName="${schemaName}" tableName="TABLE_X"/>
    <dropColumn schemaName="${schemaName}" tableName="TABLE_X" columnName="ID"/>
    <dropColumn schemaName="${schemaName}" tableName="TABLE_X" columnName="CONTENT"/>
    <addPrimaryKey schemaName="${schemaName}"
                   columnNames="NAME"
                   constraintName="PK_TABLE_X"
                   tableName="TABLE_X"/>
    <addColumn schemaName="${schemaName}" tableName="TABLE_X">
        <column name="ETAG" type="NVARCHAR(255)">
            <constraints nullable="false"/>
        </column>
    </addColumn>
    <addColumn schemaName="${schemaName}" tableName="TABLE_X">
        <column name="BODY" type="VARBINARY(max)">
            <constraints nullable="false"/>
        </column>
    </addColumn>
</changeSet>`

I tried to add objectQuotingStrategy="QUOTE_ALL_OBJECTS" but then the changeset already failed at the first  statement.


[WIP] TensorFlow tutorial notebook

@lamblin this is the PR in which I will push updates for the TensorFlow tutorial notebook.

@notoraptor Thanks a lot for the review! I apologize for being a little last-minute on the tutorial, but I do intend to make it as complete as possible today, so I will definitely consider your suggestions.

Also, I know it is last-minute, but maybe it would be worth having an "advanced topics" section mentioning (and linking to) in particular:

Data management, https://www.tensorflow.org/programmers_guide/datasets
Estimators, https://www.tensorflow.org/programmers_guide/estimators (esp. for those who could get access to TPUs)
Eager mode, https://github.com/tensorflow/tensorflow/tree/master/tensorflow/contrib/eager

@lamblin it's been a while since I last kept up-to-date with the latest TensorFlow features, and I certainly won't be able to discuss them in the tutorial, but sure, I can link to them!

@lamblin @notoraptor I think I covered all the points you raised in your reviews, would you mind having another look?

It looks good for me !

Merged, thanks a lot!