MacOSX fails with icudtl.dat not found in bundle

First off, really like your work on this fork, its the closest to a working xplatform CEF example i can find right now on .net. Kudos on the downloader, no one explains the necessary directory layouts anywhere for this type of setup so its saved me a few nights banging my head against the wall.
Cloning and running the current repo on macOSx Catalina compiles but fails to launch due to this issue
CI-TRACE: Application=Started
CI-TRACE: Chromely.Core=<IP_ADDRESS>
CI-TRACE: Platform=MacOSX
CI-TRACE: AppDirectory=../Chromely-master/src/Tests/Chromely.Integration.TestApp/bin/x64/Debug/netcoreapp3.1/
CI-TRACE: Configuration=Created
2020-07-13 16:08:00.958 [INFO] Running MacOSX chromium 79.0.3945.130
[0713/160801.050579:ERROR:icu_util.cc(132)] icudtl.dat not found in bundle
[0713/160801.051177:ERROR:icu_util.cc(177)] Invalid file descriptor to ICU data received.

https://bitbucket.org/chromiumembedded/java-cef/issues/109/linux-mac-fix-discovery-of-icudtldat
.NET Core SDK (reflecting any global.json):
 Version:   3.1.301
 Commit:    7feb845744

Runtime Environment:
 OS Name:     Mac OS X
 OS Version:  10.15
 OS Platform: Darwin
 RID:         osx.10.15-x64
 Base Path:   /usr/local/share/dotnet/sdk/3.1.301/

Host (useful for support):
  Version: 3.1.5
  Commit:  65cd789777

.NET Core SDKs installed:
  2.0.0 [/usr/local/share/dotnet/sdk]
  3.1.300 [/usr/local/share/dotnet/sdk]
  3.1.301 [/usr/local/share/dotnet/sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.App 3.1.4 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.1.5 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.0.0 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.18 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.19 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.1.4 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.1.5 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]

If i find a solution i'll make a PR.

@captainjono

First off, really like your work on this fork, its the closest to a working xplatform CEF example i can find right now on .net. Kudos on the downloader, no one explains the necessary directory layouts anywhere for this type of setup so its saved me a few nights banging my head against the wall.

Thank you.
Most samples work well on Windows without some modifications. Please let me see if following helps, then we can see how to guide others for MacOS..
For Chromely in MacOS, Linux it is best to start with CrossPlatDemo - https://github.com/chromelyapps/demo-projects/tree/master/regular-chromely/CrossPlatDemo
Also please follow the ReadMe minimal 3 steps - https://github.com/chromelyapps/demo-projects#running-the-demos
If that still does not work please see this chromelyapps/Chromely#214
Attached a flattened demo ChromelyMac79.zip that can help with debugging - https://github.com/chromelyapps/Chromely/issues/214#issuecomment-647009304. With this we can know where the issue is coming from.
Thanks.
_

@mattkol
Sorry i just realised this was a dupe report - sorry about that!
I was not after a .net core solution originally, rather I was attempting to run Chromely via Xamarin.Mac (modern, latest version of the framework that will turn into .net MUI). I leveraged the Chromely.Integration.Test code and shoehorned it into a Xamarin mac solution and it worked after i applied this patch that i found in another fork ->
        protected override void OnBeforeChildProcessLaunch(CefCommandLine browser_cmd)
        {
            // Disable security features
            browser_cmd.AppendSwitch("default-encoding", "utf-8");
            browser_cmd.AppendSwitch("allow-file-access-from-files");
            browser_cmd.AppendSwitch("allow-universal-access-from-files");
            browser_cmd.AppendSwitch("disable-web-security");
            browser_cmd.AppendSwitch("ignore-certificate-errors");

            if (_config.Platform == ChromelyPlatform.MacOSX || _config.Platform == ChromelyPlatform.Linux)
            {
                if (!browser_cmd.HasSwitch("cefglue"))
                {

                    //var path = new Uri(Assembly.GetEntryAssembly().CodeBase).LocalPath;
                    // ^^ not correct path, points too src/TestApp.macOS/bin/Debug/TestApp.Mac.app/Contents/Monobundle/TestApp.Mac.exe

                    //explicit path to see if it solved issue
                    browser_cmd.SetProgram("src/TestApp.macOS/bin/Debug/TestApp.Mac.app/Contents/MacOS/TestApp.Mac");

                    browser_cmd.AppendSwitch("cefglue", "w");
                }
            }

            if (_config.DebuggingMode)
            {
                Console.WriteLine("On CefGlue child process launch arguments:");
                Console.WriteLine(browser_cmd.ToString());
            }
        }

Xam mac uses a different folder structure then .net core and also wraps the mono/code in a Cocoa mac.app so it can be natively executed.
In this case, the app directory ends up being
..src/TestApp.macOS/bin/Debug/TestApp.Mac.app/Contents/MonoBundle
this is where CEF.framework is extracted too automatically by your tooling. The xamarin mac folder allows more probing paths, and ultiamtely doesnt trigger the the issue seen in .net core (mac has MANY probing paths, it really go to extreme lengths searching for your library!) i can optionally put CEF.framework in the folder structure specified by the cefclient.mac documentation (Frameworks/Libaries/Resources folders) and it will work.
So folder structure is 1 element of the failure, the other element is the Helper.app's required for cef mac. The setprogram switch takes care of this for Xam.mac because it bundles mono into an native mac executable (using mkbundle i think) and the cefglue.host implements the CEFclient correctly (great job!! - im going to attempt to port to xamarin.mac using / c#). Im not familiar with .net core native binaries, but this may mean you will need to setprogram to Assembly.ExecutingAssembly().Location and then prepend the "dotnet" runner.
Alot of existing examples of mac code that i came across relied on setting the cefsettings.singleprocessmode = true and i think thats why they worked previously without these extra switches. This option is now deprecated, so you must provide helpers as per the CEFClient docuementation.
Regarding .net core, I found another cefglue fork labeled "avalonia" which also runs on .net core. I had alot of trouble getting off the ground because no on explains to you that you needed to rename CEF.framework as distributed from the main repo, to "libcef". For that branch, I was able to resolve the issue but putting CEF.framework in
CefGlue.Avalonia/bin/debug/runtimes/osx/native/{cef.framework}
But i also had to label from "Chrominium embedded framework" to  "liblibcef". Notice the "liblib"!
This dir didnt exist in your .net core build but i did play around quickly by adding it to all the locations it had probed before but had no luck, could never find the .dat. Thats when i saw that for JCEF, they ended up symloinking this file to what would be the /frameworks/{dotnetcore.framework}/dotnet  directory witch indicates to me that you might need to setup that new command-line arg as per the link i provided.
I only got this working late last night. I am still cleaning up my code so i can ensure it will slot into my existing code-base correctly (i am replacing cefsharp). Would u like me to submit a PR and a demo project once i have a working / reliable implementation on Xamarin? I think once .net5 lands, Xamarin and net core will be running on the same underlining platform, but until then, they both run .net standard, but xamarin.mac requires a mac to compile on and compiles to native cocoa apps by default.
Ive got a deadline to meet so i cant help right this moment debugging the net core issue. I will check back in on the other thread and it if no one else is able to help i will give you a hand at resolving this.

@captainjono so if I understand this well, this is about Chromely + Xamarin.Mac.
The main objective of Chromely is to provide a single browser framework using the "thinnest" possible native host.

It is focused on building apps based on Xilium.CefGlue, CefSharp implementations of embedded Chromium (CEF) without WinForms or WPF, but can be extended to use WinForms or WPF. Chromely uses Windows, Linux and MacOS native GUI API as "thin" chromium hosts.

Xamarin is a full-fledged UI framework like WPF/WinForms, and as such will violate that premise. I kindda explained more here - https://github.com/chromelyapps/Chromely/issues/52
If you go through the history of Chromely, it took us a while to add MacOS support-  none of the 3 of us has Mac experience. We had a few volunteers, but no serious dedication. I had to learn Cocoa API/Objective C from scratch. Of course I did consider Avalonia, LibUI, and Xamarin.Mac but all were too heavy for what we needed it for. LibUI came close but I was spending a lot of time deleting what was not needed.
So my point is if there is a fork dedicated to Chromely/Xamarin, I think it will be great, but I do not think it is advisable to pull into main repo. You can see that we put a lot of thought into the leanness and simplicity and actually removed CefSharp support because of that. But I am looking to bring it back as a separate project. Something I have always wanted to do,

@mattkol
I understand the premise of this project and i appreciate its leanness. I disagree Xamarin.mac is fat!

Xamarin.Mac allows you write C# instead of Objective-C, against ALL the native mac APIs.

Thats what Xamarin mac is. In theory, i can write LibChromely.dynlib in Xamarin.mac and interface directly with lib_cef_dll without any objective C code.
To elaborate further

Xamarin.Mac is NOT Xamarin.Forms. They can be used with eachother, or seperately
Avalonia is a cross-platform UI framework which is designed to have the same "look and feel" on each OS, as opposed to Xamarin.Forms, which is designed to take on the "native look and feel" for each OS. its a fat framework which supports cross-platform p/invoke and takes a different approach to Xamarin.Forms.

The Avalonia fork i mentioned was implemented in .net core as your integration test isI mentioned it because it had a different directly layout and didnt suffer from .dat issue i am experiencing with yours. I mentioned it purely to help with your debugging of this issue. It suffered from other problems though and didnt launch.
I liteterly copy/pasted the current integration test into a Xam.mac project, compiled and ran it, and it basically worked except for the browser_sub_process issue i mentioned previously.
In terms of what i value in cross-platform code, i value the ability to run the same code on any platform so i can re-use logic and tests and onboard new platforms without fuss. I think restricting yourself to running on .net core only defeats the purpose of .net standard and the work you have done to make this library compliant with it.
My end goal is to run the same SPA/C# backend using CEF on Win/mac/Linux/Andriod/iOS.

@mattkol
i understand what you are saying now. Point noted on not wanting to show Xamarin.mac as a supported path as it will increase the workload in the project without appropriate resources and dilute the work going into other areas.
From my perspective, i wanted to show the community an option for Xamarin.mac with CEF. I will continue to work on my intergration and if i am successful i will push a branch to help others out.


🔬🧪🧬 [Refactor] (code + test) Rename functions and elevate to be public function.

Target

Rename functions operates with Zookeeper and elevate to be public function.

Modify Code Scope

Source Code:

module crawler.

Testing Code:

Integration Testing

testing module crawler.

Effecting Scope

Nothing, the major change of this PR is refactoring and elevate these functions to be public.

Description

Rename functions operates with Zookeeper and elevate to be public function.

'register' -> 'register_metadata'.
'register_group_state_to_zookeeper' -> 'register_group_state'.
'register_node_state_to_zookeeper' -> 'register_node_state'.
'register_task_to_zookeeper' -> 'register_task'.
'register_heartbeat_to_zookeeper' -> 'register_heartbeat'.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

38 of 41 (92.68%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 92.635%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

smoothcrawler_cluster/crawler.py
38
41
92.68%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1044

Relevant Lines:
1127

💛  - Coveralls


WA3: exoplayer fails to run because of 'get_rotating' error

Hi,
I trying to run an exoplayer workload but I get the error:
ERROR          File "/usr/local/lib/python2.7/dist-packages/wa/framework/execution.py", line 420, in run_next_job
ERROR            self.do_run_job(job, context)
ERROR          File "/usr/local/lib/python2.7/dist-packages/wa/framework/execution.py", line 457, in do_run_job
ERROR            job.setup(context)
ERROR          File "/usr/local/lib/python2.7/dist-packages/wa/framework/job.py", line 101, in setup
ERROR            self.workload.setup(context)
ERROR          File "/usr/local/lib/python2.7/dist-packages/wa/workloads/exoplayer/init.py", line 167, in setup
ERROR            self._original_orientation = self.target.get_rotation()
ERROR          File "/usr/local/lib/python2.7/dist-packages/devlib/target.py", line 1373, in get_rotation
ERROR            return int(self.execute(cmd).strip())
ERROR
ERROR        ValueError(invalid literal for int() with base 10: 'null')
INFO         Completing job wk1
ERROR    Job wk1 iteration 1 completed with status FAILED. Max retries exceeded.
However, running the same workload with the commit-id 833c3dd0a00a0a76e8441da994c96beaf97bb768 runs fine.

Hi,
This was due to a bug in devlib, this should now be fixed https://github.com/ARM-software/devlib/commit/f3c8ce975ee3980134a5e306af05bda0e1eb0d5c. Could you update to the latest version of devlib and try again?

Actually it shifted the error to the end of the test.
ERROR          File "/usr/local/lib/python2.7/dist-packages/wa/framework/execution.py", line 420, in run_next_job
ERROR            self.do_run_job(job, context)
ERROR          File "/usr/local/lib/python2.7/dist-packages/wa/framework/execution.py", line 488, in do_run_job
ERROR            job.teardown(context)
ERROR          File "/usr/local/lib/python2.7/dist-packages/wa/framework/job.py", line 124, in teardown
ERROR            self.workload.teardown(context)
ERROR          File "/usr/local/lib/python2.7/dist-packages/wa/workloads/exoplayer/init.py", line 217, in teardown
ERROR            self.target.set_rotation(self._original_orientation)
ERROR          File "/usr/local/lib/python2.7/dist-packages/devlib/target.py", line 1381, in set_rotation
ERROR            raise ValueError('Rotation value must be between 0 and 3')
ERROR
ERROR        ValueError(Rotation value must be between 0 and 3)
INFO         Completing job video_workload_task_placement
ERROR    Job video_workload_task_placement iteration 1 completed with status FAILED. Max retries exceeded.

Ok, this should now be fixed with commit https://github.com/ARM-software/workload-automation/commit/ff5e5821d05da32020448094c275cfebd0e0346c.

Yes, confirmed.


Executing the dependencies.sh fails on step 3

After many attempts, I can't seem to get past step 2.  Installing pocketsphinx seems to fail.
[STEP 3/5] Installing pocketsphinx
Cloning into 'pocketsphinx'...
remote: Enumerating objects: 17888, done.
remote: Counting objects: 100% (1719/1719), done.
remote: Compressing objects: 100% (643/643), done.
error: RPC failed; curl 56 GnuTLS recv error (-9): Error decoding the received TLS packet.
error: 6726 bytes of body are still expected
fetch-pack: unexpected disconnect while reading sideband packet
fatal: early EOF
fatal: fetch-pack: invalid index-pack output
[STEP 3/5] Installing pocketsphinx | Failed
Does this script still work? Has anyone been successful recently with this install?

see my comment here
https://github.com/mykle1/Hello-Lucy/issues/36#issuecomment-1008437468

I did not make any changes.  After I received your comment I executed the dependencies script again (probably my 6th or 7th time) and it worked.  Strange!


Node click not work for viewgenerator if node id is number

Describe the bug
Create multiple Node with viewgenerator(custom node design of 520px) because size is overalpping
e.g.
["nodeID", "123","node23", "345"]
Add Apply on-click event to graph when you are going to click on 345 it always select "node23"
To Reproduce
Steps to reproduce the behavior:

Go to Create nodes with viewgenerator
Click on number node
It will selecte previous node of the click node because size is overalpping
See error

Also need to restrict drag n drop functionality to particular width and height
Expected behavior
On Click will need to work with all behaviour on paricular node
Screenshots
If applicable, add screenshots to help explain your problem.

Environment:

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]
Node version [e.g. 8.11.0]
react-d3-graph version [e.g. 2.0.0-rc2]
d3 version [e.g. 5.5.0]
react version [e.g. 16.0.0]

Additional context
Add any other context about the problem here.

Hi @saurabh98505, it seems what you're describing here it's a side effect of you're layout overlapping. Could you please provide the data payload and the configuration you're passing to react-d3-graph Graph component?


autofilter incorrectly pointing to previous month file

Hi all,
I have seen that in the most recent commit the autofiltering is incorrectly identifying the previous month file, pointing to the present month file. Here's the log of January 1950 analysis
+ /marconi_work/Pra13_3311/ecearth3/PRIMAVERA/cmorization/ece2cmor3/ece2cmor3/ece2cmor.py /marconi_scratch/userexternal/pdavini0/tmp_cmor/qctr_8872/atm_1950_1/linkdata 1950-01-01 --exp qctr --conf /marconi_scratch/userexternal/pdavini0/tmp_cmor/qctr_8872/atm_1950_1/CMIP6/metadata-qctr-year1950.json --vars /marconi/home/userexternal/pdavini0/ecearth3/ece3-postproc/ece2cmor3_support/varlist/varlist-short.json --npp 1 --tmpdir /marconi_scratch/userexternal/pdavini0/tmp_cmor/qctr_8872/atm_1950_1/CMIP6 --ifspar /marconi/home/userexternal/pdavini0/ecearth3/ece3-postproc/ece2cmor3_support/paramtable/ifspar.json --tabid CMIP6 --tabdir /marconi_work/Pra13_3311/ecearth3/PRIMAVERA/cmorization/cmip6-cmor-tables/Tables --mode append --atm --filter
INFO:ece2cmor3.taskloader:Found 4 cmor target variables in input variable list.
INFO:ece2cmor3.taskloader:Created 2 ece2cmor tasks from input variable list.
INFO:ece2cmor3.ece2cmorlib:Selected 2 IFS tasks from 2 input tasks
INFO:ece2cmor3.grib_filter:Searching for previous month file of /marconi_scratch/userexternal/pdavini0/tmp_cmor/qctr_8872/atm_1950_1/linkdata/ICMGGqctr+195001
INFO:ece2cmor3.ifs2cmor:Inspecting 2 tasks.
INFO:ece2cmor3.ifs2cmor:Validated 2 tasks for processing.
INFO:ece2cmor3.ifs2cmor:Executing 2 IFS tasks...

This is happening even if december 1949 is found in the tmp folder:
[pdavini0@r000u06l01 ~]$ ls /marconi_scratch/userexternal/pdavini0/tmp_cmor/qctr_8872/atm_1950_1/linkdata/
ICMGGqctr+194912  ICMGGqctr+195001  ICMSHqctr+194912  ICMSHqctr+195001

This is affecting several high frequency variables...

Hi @goord,
my bad, sorry. I misunderstood the plotting of the code: the new logfile correctly reporting that autofilter is pointing to the 194912 file.
I had some problem with 3hrs file and I thought they were connected to this, but it does not seem to be the case. Closing this.


TypeError: _handle_remote_call_reply()

Description
What steps will reproduce the problem?

First time startup offered to install Kite, which I did, and after that (a) Kite has claimed it cannot find Spyder, and (b) Spyder frequently gives me this issue reporter. Other than the issue reporter appearing, Spyder appears operational. Kite did install and works in VS Code.
Traceback
  File "/usr/local/lib/python3.7/site-packages/qtconsole/comms.py", line 177, in comm_msg
    comm.handle_msg(msg)
  File "/usr/local/lib/python3.7/site-packages/qtconsole/comms.py", line 265, in handle_msg
    return self._msg_callback(msg)
  File "/usr/local/lib/python3.7/site-packages/spyder_kernels/comms/commbase.py", line 331, in _comm_message
    msg_dict, buffer)
TypeError: _handle_remote_call_reply() missing 1 required positional argument: 'load_exception'
ERROR:traitlets:Exception in comm_msg for 22301ab066c711ea8566acbc327a2501
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/qtconsole/comms.py", line 177, in comm_msg
    comm.handle_msg(msg)
  File "/usr/local/lib/python3.7/site-packages/qtconsole/comms.py", line 265, in handle_msg
    return self._msg_callback(msg)
  File "/usr/local/lib/python3.7/site-packages/spyder_kernels/comms/commbase.py", line 331, in _comm_message
    msg_dict, buffer)
TypeError: _handle_remote_call_reply() missing 1 required positional argument: 'load_exception'

Versions

Spyder version: 4.0.1
Python version: 3.7.6
Qt version: 5.12.7
PyQt5 version: 5.12.3
Operating System: Darwin 19.3.0

Dependencies
applaunchservices >=0.1.7    :  0.2.1 (OK)
atomicwrites >=1.2.0         :  1.3.0 (OK)
chardet >=2.0.0              :  3.0.4 (OK)
cloudpickle >=0.5.0          :  1.2.2 (OK)
diff_match_patch >=20181111  :  20181111 (OK)
intervaltree                 :  None (OK)
IPython >=4.0                :  7.9.0 (OK)
jedi =0.14.1                 :  0.14.1 (OK)
nbconvert >=4.0              :  5.6.0 (OK)
numpydoc >=0.6.0             :  0.9.2 (OK)
pexpect >=4.4.0              :  4.7.0 (OK)
pickleshare >=0.4            :  0.7.5 (OK)
psutil >=0.3                 :  5.6.3 (OK)
pygments >=2.0               :  2.5.2 (OK)
pylint >=0.25                :  2.4.2 (OK)
pyls >=0.31.2;<0.32.0        :  0.31.8 (OK)
zmq >=17                     :  18.1.0 (OK)
qdarkstyle >=2.7             :  2.8 (OK)
qtawesome >=0.5.7            :  0.7.0 (OK)
qtconsole >=4.6.0            :  4.7.1 (OK)
qtpy >=1.5.0                 :  1.9.0 (OK)
sphinx >=0.6.6               :  2.4.3 (OK)
spyder_kernels >=1.8.1;<2.0.0:  1.9.0 (OK)
watchdog                     :  None (OK)
cython >=0.21                :  0.29.13 (OK)
matplotlib >=2.0.0           :  3.1.1 (OK)
numpy >=1.7                  :  1.17.3 (OK)
pandas >=0.13.1              :  0.24.2 (OK)
scipy >=0.17.0               :  1.3.1 (OK)
sympy >=0.7.3                :  None (NOK)

Solved by installing Spyder via Anaconda, as recommended. I had these issues when pip installing on separate Python 3.7 or Python 3.8 installations.

Thanks for understanding. This is a dependency incosistency we easily fixed in Anaconda but we couldn't fix in pip.
Our new version (4.1.0, to be released later today) will fix it.

The solution is to downgrade to spyder-kernels 1.8.1 or to use Anaconda.

I uninstalled Spyder and then re-installed it via Anaconda. But I have the same warning message about the internal problem (after having accepted to install Kite)


Feature request: please add Y min to Dual Axis chart type

Make sure these boxes are checked before submitting your issue - thank you!

[ ] I have checked the superset logs for python stacktraces and included it here as text if any
[x ] I have reproduced the issue with at least the latest released version of superset
[x ] I have checked the issue tracker for the same issue and I haven't found one similar

Superset version
0.19.1
Expected results
I'd like to be able to set Y min = 0 (or other value) for one or both Ys on the Dual Axis chart
Actual results
Currently, I can only set Y min on Time Series- Line Chart
Steps to reproduce
Create slice with Dual Axis chart type- you will see no option to set Y min for either Y
Thank you!

Please reproduce with latest superset version.


Offering assistance

Hey Roy,
Cool project. If you have space for a second set of hands, I'd like to help out.
Is there a good place to chat about TODOs/the next incarnation of NSL? You mentioned code is moving - are you going to the decky plugin repo? Or is it a rewrite of the bash script?
Cheers,
Nelly

@NellyWhadsDev there is a lot of changes coming up for nsl in the nest couple weeks. There is also a lot of interest in helping such as your self! Thank you for offering your assistance and would be glad put your skills to use. This week I'm hoping an update can be pushed to the decky plug-in as well as some small changes to the bash file. From there you will be able to see the direction of both the plugin and the NSL project if that makes sense.

Rocket on, good sir. Cheers

Rocket on, good sir. Cheers

Actually there is something if you could look into for me. Do you have discord? @moraroy

Request sent - I'm not on it often, but I can start watching my notifs for this project / from you.


Item installation not from current directory fail

Fixed via https://github.com/jakev/dtf/commit/1da0cf79efb60033993bd758bb6c316301d00fc1


fix: replace resolveString with verifyString

Replaces a reference to the now removed Util.resolveString with Util.verifyString
Introduced by https://github.com/discordjs/discord.js/pull/4880

I just tested this PR and looks like this.options is giving the error TypeError: Cannot read property 'content' of undefined, without the this.options is working fine

Shouldn't StringResolvable be Replaced with string in the Typings?

StringResolvable is being used for message sending and editing, both of which are changing in https://github.com/discordjs/discord.js/pull/5758
Once the PR has landed, this can be updated and fix two breaking changes together.

I don't believe this PR should address both changes, no. I will update the typing though.

Oh, yeah mb, I thought this was a PR for updating Commando for v13.

Oh, yeah mb, I thought this was a PR for updating Commando for v13.

There are a lot of things missing to support v13, This is getting kinda off-topic lets discuss on library-discussion if You want.

can this be merged so we can use commando with the master version of discord.js

This PR just Broke lmao, now You get verifyString is not a function

It's still in there:
https://github.com/discordjs/discord.js/blob/master/src/util/Util.js#L403
Are you sure you didn't change back to 12.5.3?

It's still in there: https://github.com/discordjs/discord.js/blob/master/src/util/Util.js#L403
Are you sure you didn't change back to 12.5.3?

Yea He Just forgot to add .Util after requiring d.js


Add renderOverlay method in NavigatiorTransitioner component

NavigationAnimatedView had a renderOverlay props,
but now i can't render overlay in new NavigationTransitioner component

is it possible ?

Yes it's still possible but you need to modify the render function and render the overlay in there.
Have a look at the NavigationCardStack custom component and you can see how it's done: https://github.com/facebook/react-native/blob/master/Libraries/CustomComponents/NavigationExperimental/NavigationCardStack.js#L131

That's it!
Thank you !


Automatic go get?

Is it possible to make gore run go get when a package is not locally installed?
I am working on a web REPL for Go (using web terminals + containers), and this (or some shortcut to go get/install) would make it perfect for the REPL system.

You mean automatic go-get when :importing? Yeah, maybe with some startup options.


feat: more sub lemmas for Nat

[x] Mathlib patch: https://github.com/leanprover-community/mathlib4/pull/6216

There's a bunch of deprecated lemmas, all of which have better alternatives except for one which appears to be a single purpose lemma that lost its purpose.

@YaelDillies, do you have an opinion here, or are able to review?

This is the last in a series. They're mostly independent but it might be easier to start with #194.

I'd rather we did none of the above. The tsub lemmas are more complex to understand, and elaborate. I think there should be no particular preference in mathlib for one over the other. Certainly there won't be a warning about not adding any more lemmas on Nat: tsub is only relevant if you care about other types with truncated subtraction like NNReal.

If we had to only do one of my suggestions, I would like it to be

Put in the docstring of duplicate Nat.sub_something that tsub_something exists in mathlib
because I want mathlib users to be directed towards the API that's useful to them, avoiding ad hoc Std lemmas.

@YaelDillies Note that Nat lemmas in Std are primarily to reason about sizes of objects, array indices and such. There's no intent to duplicate or clash with Mathlib. My impression is that most users would use these lemmas for their intended purpose, so I don't quite see the need for the first three suggestions.
However, I am happy with the fourth suggestion:

Put a big warning in Std.Data.Nat.Lemmas that if people want a lot of theory about truncated subtraction, then they should use Mathlib.Algebra.Order.Sub.Canonical instead of PRing more lemmas here

I will add a module doc to clarify the intended purpose of these lemmas and a pointer to Mathlib alternatives.
I would like to hear what others think before implementing the first three suggestions.

@YaelDillies Please see #237.

I agree that module-docs are the way to go to explain the additional theory available in Mathlib.
Any results that are needed or helpful for non-mathematical uses of Nat need to be here in Std, without expecting such users to know about the general theory of truncated subtraction.
I am ambivalent about the "Mathlib-specific deprecation" suggestion, but don't think we should mention tsub in Std.
@fgdorais, as far as I'm concerned I think you can mark this back as awaiting-review.


Allow FuseMountName for chansrv to be absolute path

This PR primarily addresses #1048 (Drive redirection location).
It also contains:-

a fix for the first of the two issues mentioned in #1658 (xrdp-chansrv become defunct in docker while file copy)
a way to disable the FUSE filesystem at runtime if the system was built with --enable-fuse.

Documentation for the new features has been added to sesman.ini and the manpage xrdp-sesman.ini(5).
The code has been largely tested by @hmakmur, but, as ever, could do with a second pair of eyes.
An extra module string_calls.c has been added to contain the g_format_info_string() function. Over time, some other string functions which are not operating-system specific could be moved here from os_calls.c.

I haven't tested yet but overall LGTM.

Hadn't noticed this one was no longer mergeable - it now is.
I've squashed the original commits into 1, and added another one which moves g_text2bool() into string_calls, where it joins g_bool2text(). So that's now consistent.
@metalefty - there's a bunch of string calls in os_calls.h which could be moved in to string_calls.h:-
https://github.com/neutrinolabs/xrdp/blob/bfe76e0499fd2c02eb2c97d49dce79ffa2262a19/common/os_calls.h#L122-L142
I could move them now. Quite a few files might need #include "string_calls.h" adding, but I think that's a pretty minimal change, provided it stays as a single commit. Do you agree?

@matt335672
Hi, sorry for the delay. Of course, a separate PR is a good idea but let's add a single commit to this PR to move them.
Merge it when you finished.


[5.7] Policies don't redirect unauthenticated users to login page

Laravel Version: 5.7.2
PHP Version: 7.2.7
Database Driver & Version: MySQL 5.7.23

Description:
Laravel 5.7 introduced a new feature to allow guest authorization in policies. This is great, but I come across one problem. When guest users are not authorized to perform an action a 403 error is thrown instead of the user being redirected to the login page.
Steps To Reproduce:
Create an action guarded by a policy which allows guests (a question mark in front of the first argument), then deny access for that guest.
class ItemPolicy {
    use HandlesAuthorization;

    public function view(?User $user, Item $item) {
        return false;
    }
}

Proposed solution
To overcome this, the deny method of the Illuminate\Auth\Access\HandlesAuthorization trait can be updated from:
protected function deny($message = 'This action is unauthorized.') {
    throw new AuthorizationException($message);
}

to something like this :
protected function deny($message = 'This action is unauthorized.') {
    if(Auth::guest())
        throw new AuthenticationException($message);
    else
        throw new AuthorizationException($message);
}

I am willing to create a PR for this, but since I'm not sure if the current behaviour is meant this way and it would be my first PR, I want to discuss it with you first.

Hi @anneheijink ,
You are able to discuss ideas at https://github.com/laravel/ideas
However, given this is a small change, you might as well just create a PR for it, and include your "reasons", then let Taylor decide.
I'll close this ticket, as it is not a framework bug.
Let me know if you need anything else.


To integrate Go's unit test report

I recommended to integrate Go's unit test report (GoConvey: https://github.com/smartystreets/goconvey), the Go's unit test report is very important and useful.

Go test is already supported, or are you referring to something specific to goconvey?

The GoConvey has native integration Go test , but it is more powerful, such as support for BDD testing framework, while a wealth of assertions. and more https://github.com/smartystreets/goconvey

Sorry, I really don't understand what you're asking for. What do you mean by "integrate"?
Are you referring to something like gometalinter --enable goconvey? If so, I don't understand how that would work, as it looks like goconvey isn't a tool at all?
If you're suggesting that gometalinter use goconvey for its own tests, then no, I think that is unnecessary. The standard testing package is fine.

Oh, How to enable Go test?

To enable linters refer to this. To use a custom linter, or override the flags of an existing one, refer to the flag --linter.


chore: add text file with current compiler version for CI use

This change is

Codecov Report
Attention: Patch coverage is 75.00000% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 76.48%. Comparing base (ba7cf07) to head (0d4274f).

Files
Patch %
Lines

crates/blockifier/src/test_utils/cairo_compile.rs
75.00%
1 Missing :warning:

Additional details and impacted files
@@                           Coverage Diff                           @@
##           dori/verify-cairo-repo-is-directory    #1881      +/-   ##
=======================================================================
+ Coverage                                76.40%   76.48%   +0.08%
=======================================================================
  Files                                       61       61
  Lines                                     8767     8770       +3
  Branches                                  8767     8770       +3
=======================================================================
+ Hits                                      6698     6708      +10
+ Misses                                    1630     1622       -8
- Partials                                   439      440       +1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Change base map drop down on google sheet

Hiya,
I would like to add: Esri.WorldImagery and a few others  to the dropdown on the 'Options' tab under Base Maps on the google sheets template, can you advise how I can do that please?
The main reason for wanting to do this is because the other base maps don't cover the area where I want my story map so it just shows as grey.
All the best,
Mark

Hi Mark–
We are using leaflet-providers plugin to load basemaps, so you should be able to manually edit the cell to load a different basemap (in your case, Esri.WorldImagery).
Let me know if that helps!
Ilya


Can multiple values in one cell work?

Say my CSV file is:
name,value
Alice,a
Bob, "b,c,d"

And my template:
{{name}}:: [[{{value}}]]

In Alice.md it returns Alice:: a as expected. But in Bob.md it returns Bob:: [[ "b]]. Is it possible to have it return like this?
Bob:: b
Bob:: c
Bob:: d

Hi, because you have a space on the second line after the comma, it is reading the rest of the line as three more fields.
If you had:
name,value
Alice,a
Bob,"b,c,d"

Then it would end up with:
Bob:: [[b,c,d]]

Unfortunately nesting of lists isn't really possible in CSV file formats, and I'm not sure how easy it would be to implement it locally. It would have to consider quotes within quotes and other special characters that could interrupt the detection of commas within the field.

I find the csv-to-md script work like a charm. Do you think it would be best to recommend using it to other users as well?

I find the csv-to-md script work like a charm. Do you think it would be best to recommend using it to other users as well?

How do you use that script to break up your "b,c,d" single value?

not really (see this issue). But it can make it to
Bob:: [[b]] [[c]] [[d]]

and from there you can use regex to split it into multiple lines


Documentation on test ordering

The note at the end of the chapter Parallelism (https://github.com/kotlintest/kotlintest/blob/master/doc/reference.md#parallelism) states:

Note: Test cases inside each spec will always run sequentially (either in definition order, or in a random order, see documentation on test ordering).

However I can't find this documentation on test ordering. Where can I find it?
At the moment, my tests rely heavily on their definition order in their spec and it looks like they are actually running in this way. But I don't know if, in the future, a spec "decided" to run its tests in random order.
Should I avoid to depend on test ordering inside each spec? In this way I can save some computational time, recycling resources.

I'm using 3.1.10 and I've never overridden the function testCaseOrder().
Therefore, I should inherit the function testCaseOrder() of AbstractProjectConfig:
  /**
   * Sets the order of top level tests in a spec.
   * The value set here will be used unless overriden in a [Spec].
   * The value in a [Spec] is always taken in preference to the value here.
   * Nested tests will always be executed in discovery order.
   *
   * If this function returns null then the default of Sequential
   * will be used.
   */
  open fun testCaseOrder(): TestCaseOrder? = null

and my test should run in Sequential order.
Thank you for your quick help.

You can override it in either place.


Support Switch Expressions

https://openjdk.java.net/jeps/361
If you don't have time, could you at least give some tips how to fix it properly?
Would be enough to change  only parse_switch_block_statement_group or  something else should be done?

I suspect that at a minimum that top-level expression parsing would also need to be updated to account for the fact that a switch can now be used as an expression and not just a statement.
Fair warning though, there have been a lot of syntax changes in Java since Java 7 which this library originally targeted. Java 8 is mostly supported at this point, but it was largely bolted onto the existing support for Java 7. I suspect adding support for Java 9+ features will get increasingly difficult without significant refactoring of the parser being required.
Unfortunately, I'm no longer actively using or working on javalang myself, but I would be willing to review a PR that added switch expression support with test coverage for changed code paths.

Thank you for response! I need to think about it 🤔


Servo TSC Meeting June 2024

Date: Monday 24th June 2024 at 15:00 UTC
Location: https://meet.jit.si/Servo-TSC

Agenda

Status update
Crowdfunding
Outreach
AOB

Can we add one about multiprocess mode? I opened several issues that try to reduce the overhead but it seem they are required in multiprocess. But at the same time, multiprocess isn't working and it's not enabled by default either. Perhaps we should discuss the direction of this.

How is multiprocess not working? We run smoke tests with it in CI, I believe.

@jdm I was trying to add -M to the binary but it didn't run. In terms of smoke test CI, I didn't see anywhere that mentions it.
Could you share the mach command I could test?

Hmm, we used to run them in taskcluster: https://github.com/servo/servo/blob/3ce71cda73c9840d36b99c20aecd190125791ea3/etc/taskcluster/decision_task.py#L642 . Maybe they were never migrated?

@jdm I was trying to add -M to the binary but it didn't run.

This was failing due to a panic in the preference code. It should be fixed now with servo/servo#32571.

@mukilan Thank you so much! I think it's still worth adding to the agenda.
Enabling it by default seems to be an improvement.

Please add to the agenda:

Discussion about starting recurring meetings to triage issues in components. I would like to start a bi-weekly one for script.

Please add to the agenda:

Discussion about starting recurring meetings to triage issues in components. I would like to start a bi-weekly one for script.

Do you mean "bi-weekly" as in "twice a week" or "bi-weekly" as in "once every two weeks"?

For the agenda:

AI contributions policy (servo/servo#32287)

"bi-weekly" as in "once every two weeks"?

once every two weeks.


5534 - ET - Fix inactive timeout overflow preventing from users to log in.

User sessions cannot last longer than 90 days (hard coded)
1. Steps to Reproduce
Test library
Make sure the automatic tests pass.
npm test
Test for regression your application login and logout functionalities
The test cases are in the app pr 5534.
This is the idea:

log in your app and open many tabs
Log out
All tabs should be logged out
log in your app and open many tabs
Wait for your session timeout
All tabs should be logged out

2. Performance Considerations
No performance impact besides adding minimum timeout triggering logic.
Additional Notes
Zerv Sync and security libs  are also impacted due to new Zerv core lib version.

Wrong branch


jiggle bones support

Jiggle bones are bones that are animated procedurally in realtime with a physics engine. Used for clothing, items a moving character/ object, hair, hats, bunny ears, etc.
Also, ragdolls. https://www.youtube.com/watch?v=wKLaMN9dnjQ
Reference:
https://www.youtube.com/watch?v=RmCNxNkrrKQ
https://wiki.teamfortress.com/wiki/Jiggle_bones

this is planned for 1.2

Not critical for the upcoming 2.1, so moving to the next milestone.

Is this still planned?

Curious about this feature too.

Planned for 3.1
On May 10, 2017 2:16 AM, "Corruptinator"<EMAIL_ADDRESS>wrote:

Curious about this feature too.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/1533#issuecomment-300346039,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF-Z23AJ9fVHYdZATbds6LNO8J_OJuJQks5r4Q_RgaJpZM4DyeQX
.

I've been working on an addon that does this. Couldn't wait for 3.1 :laughing:.

wasnt this merged ?

This is already supported now, so closing


Release 104

Required for release R114 of Snowplow pipeline.
Contains:

Updated schemas for Sendgrid
Schemas for YAUAA enrichment.

Please assign to me as the last step when everything has been reviewed etc.

Thanks for the review! @dilyand I added you as a reviewer so that you can see the comments related to Sendgrid.

@benjben Would you like me to respond to them or just adding me fyi?

@dilyand If you could respond to them that would be awesome, otherwise no worries I'll do it.

I updated schemas for YAUAA with maxLength and I updated all the descriptions of Sendgrid with a capital letter for consistency. I also used email format (and regenerated the SQL code).
For the last comments regarding I let @dilyand comment.

Please assign to me as the last step when all reviewers have green ticked.

All done now


MULTIARCH-5031: Remove extra code

Remove code relating to tracking registries and mirrors as it has been made redundant by the solution to MULTIARCH-4694

/retest

/restest


Originally posted by @gitpod-io in https://github.com/freeCodeCamp/freeCodeCamp/pull/48179#issuecomment-1287274824

Originally posted by @tuxtvixx in https://github.com/tuxtvixx/repository/issues/9#issuecomment-1295672164

Originally posted by @tuxtvixx in https://github.com/fosshostorg/fosshost.org/issues/64#issuecomment-1295672322

Originally posted by @tuxtvixx in https://github.com/microsoft/vscode-docker/issues/3681#issuecomment-1295672461

Originally posted by @tuxtvixx in https://github.com/tuxtvixx/vscode-remote-try-node.-/issues/2#issuecomment-1295672673

Originally posted by @gitpod-io in https://github.com/freeCodeCamp/freeCodeCamp/pull/48179#issuecomment-1287274824

Originally posted by @tuxtvixx in https://github.com/tuxtvixx/repository/issues/9#issuecomment-1295672164

Originally posted by @tuxtvixx in https://github.com/fosshostorg/fosshost.org/issues/64#issuecomment-1295672322

Originally posted by @tuxtvixx in https://github.com/microsoft/vscode-docker/issues/3681#issuecomment-1295672461

Originally posted by @tuxtvixx in https://github.com/tuxtvixx/vscode-remote-try-node.-/issues/2#issuecomment-1295672673


Allow typing event context

Question: How to define context typescript type?
Hey, not sure if this is an h3 question or a lack of typecript knowledge from me.
I am using Nuxt 3 and am trying to add types to my server handlers. I have a simple server handle:
export default defineEventHandler((event) => { // event here is a H3Event object
    const result = event.context.container.resolve()
    return {
      result
    }
})

The event here is a H3Event:
interface H3Event {
    '__is_event__': true;
    event: H3Event;
    req: IncomingMessage;
    res: ServerResponse;
    context: Record<string, any>;
}

And I have a middleware where I do the following:
export default defineEventHandler((event) => {
  event.context.container = {
    resolve: () => {
      return 'ok'
    }
  }
})

I would like to "type" the event parameter, I would like my VSCode editor to be aware that the event parameter contains a context property that contains a resolve property that is a function that returns a string.
I tried extending the H3Event using the following:
declare module 'h3' {
  interface H3Event {
    context: Record<string, any> & {
      resolve: () => string
    };
  }
}

But Typescript gives me the following error:

Subsequent property declarations must have the same type. Property 'context' must be of type Record<string, any>...

Is there a way to define the context type of the event parameter in a server middleware?

Try CompatibilityEvent instead of H3Event
declare module 'h3' {
  interface CompatibilityEvent {
    '__is_event__': true;
    event: CompatibilityEvent;
    req: IncomingMessage;
    res: ServerResponse;
    context: Record<string, any> & {
      resolve: () => string
    };
  }
}

Sweet, thank you very much!

So, I've managed to make it work as you said. However, I'm wondering if there is something to do on h3 part to simplify the process of what I did:
I had to create first a Context interface extending Record<string, any>:
// Declare Context interface to be able to extend it in middleware files
export interface Context extends Record<string, any> {}

// Overriding CompatibilityEvent to replace context: Record<string, any> by context: Context
import {IncomingMessage, ServerResponse, H3Event} from 'h3'

declare module 'h3' {
  interface CompatibilityEvent {
    '__is_event__': true;
    event: H3Event;
    req: IncomingMessage;
    res: ServerResponse;
    context: Context;
  }
}

After creating this file, I was able to extend the Context interface individually in my middlewares files:
// middleware/logger.ts
declare module '../utils/context' {
  interface Context {
    $logger: Console
  }
}

export default defineEventHandler((event) => {
  event.context.$logger = console
})

// middleware/service.ts
const service = {
  doSomething () {
    console.log('doing something')
  }
}

declare module '../utils/context' {
  interface Context {
    $service: typeof service
  }
}

export default defineEventHandler((event) => {
  event.context.$service = service
})

Is this the good way to do it? Implementing the Context interface on h3 part would simplify the process wouldn't it?

@ElMatella  the problem with that is that all your middleware will have the context type of each middleware

Thanks for the issue. I think we could introduce a new EventContext interface for easy extension. /cc @danielroe is this something you would like to work on?


Allow enabling syscalls through ros2 trace or the Trace action

This adds support for enabling syscall tracing with the ros2 trace command or the Trace launch action.
While system calls are separate from kernel events, both can be traced using the LTTng kernel tracer: https://lttng.org/docs/v2.13/#doc-tracing-the-linux-kernel. Kernel events are "tracepoints" while system calls are their own kind of trace event. This explains why this PR adds a separate option for syscalls instead of just using the kernel events option. See the changes to lttngpy::enable_events in lttngpy/src/lttngpy/event.cpp.
How to use:

ros2 trace command:$ ros2 trace --syscall openat  # interactive
$ ros2 trace start my-session-name --syscall openat  # non-interactive

Launch files (Python, XML, and YAML): syscalls arg

Note that, when enabling a syscall, e.g., openat, the resulting trace has syscall entry and exit events: syscall_entry_openat and syscall_exit_openat.

@mjcarroll would you be willing to review this?

There's something wrong with the GitHub CI binary jobs: https://github.com/ros2/ros2_tracing/actions/runs/11205771796/job/31145663869?pr=137#step:4:1989. I see the same failures in the nightly GitHub CI binary jobs. Not really related to these changes.

Linux
Linux-aarch64
Linux-rhel
Windows

Sorry, I realized that the way I had written the decorator meant it was evaluated during test collection, at the very beginning. This means that, if no session daemon was running before the test was run, then the test would not be allowed to try to spawn a session daemon and therefore the test would definitely be skipped. I modified the decorator so that it's evaluated before running the test: https://github.com/ros2/ros2_tracing/compare/485dca3ac871e2a26d603b2916ac3aa6281ebf28..e12b8044bfd1b8a15209df44c10e0f1e47bcf5b0.
Can you take another look?

Argh this isn't even completely working.

OK, I fixed the decorator and I think this is all I can really do. Implementing the decorator this way ensures it's evaluated right before running the test, after the test class' @unittest.skipIf has been evaluated. Otherwise, running on Windows fails, since lttngpy is empty. See the previous Windows CI job: Windows .
Also, when running with colcon test on my system, test_kernel_tracing runs, because I have a root session daemon running and my user is part of the tracing group. However, if you try to run the test using a build system that does sandboxing, it fails because there's no root session daemon in it, and spawning one would be more tricky. I think this is fine for now.
New CI:

Linux
Linux-aarch64
Linux-rhel
Windows

Thanks for the review @fujitatomoya!
CI looks good.


xcrun instruments can't launch Simulators on Xcode 9

This line:
https://github.com/phonegap/simctl/blob/27193e094e2293b06d5d3536d1f99c4785699fdc/lib/simctl-extensions.js#L33
We need to use "open" again, but note, it is not iOS Simulator now (they changed it again), now it is just Simulator:
open -a 'Simulator' --args -CurrentDeviceUDID <device_udid_here>

Since Simulator app is only on Xcode 9, we need to detect the Xcode version and use it conditionally.

Alternative is to use:
open -b com.apple.iphonesimulator --args -CurrentDeviceUDID <device_udid_here> but we need to test this on Xcode 8 as well.

The open command works well -- if you don't have a Simulator already loaded. If there is a Simulator already loaded, it won't switch to the new specified one.

Another snag, if you use:
open -b com.apple.iphonesimulator --args -CurrentDeviceUDID <device_udid_here> and you have both Xcode 8 (say renamed to Xcode-8.app) and 9 (Xcode.app) installed, it will always launch the Xcode 9 simulator (yes, even after xcode-select switch).
We will have to resort to launching the Xcode Simulator by name, after detecting the Xcode version.

My mistake: it turns out Xcode 8's Simulator is also called 'Simulator', so the change probably occurred during Xcode 8.

Another method is to:
open `xcode-select -p`/Applications/Simulator.app/ --args -CurrentDeviceUDID <device_udid_here>

Further discussion in #15


Incorrect bundle identifier for AFNetworking pod

What did you do?
Add AFNetworking pod to my podFile
What did you expect to happen?
bundleIdentifier of AFNetworking pod is "org.cocoapods.AFNetworking"
What happened instead?
bundleIdentifier of AFNetworking pod is
"org.cocoapods.AFNetworking com.alamofire.AFNetworking"
Also in AFNetworking.xcconfig file I see
PRODUCT_BUNDLE_IDENTIFIER = org.cocoapods.${PRODUCT_NAME:rfc1034identifier} com.alamofire.AFNetworking

iTunes Transporter output above ^
[13:31:47]: ERROR ITMS-90049: "This bundle is invalid. The bundle at path xxxx/xxxx.app/Frameworks/AFNetworking.framework has an invalid CFBundleIdentifier 'org.cocoapods.AFNetworking com.alamofire.AFNetworking' There are invalid characters(characters that are not dots, hyphen and alphanumerics) that have been replaced with their code point 'org.cocoapods.AFNetworking\u0020com.alamofire.AFNetworking' CFBundleIdentifier must be present, must contain only alphanumerics, dots, hyphens and must not end with a dot. [see the Core Foundation Keys at https://developer.apple.com/library/content/documentation/General/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.html#//apple_ref/doc/uid/TP40009249-102070-TPXREF105]"

While app is running as expected and I'm able to upload builds in Firebase my app didn't pass upload to iTunes connect with following error:
Previously I used version 2.6.3 of AFNetworking and it has correct bundle identifier after pod install.
AFNetworking Environment
AFNetworking version: 4.0.1
Xcode version: 11.2.1
Swift version: 5
Platform(s) running AFNetworking: iOS
macOS version running Xcode: macOS Catalina 10.15 (19A603)
Demo Project
https://github.com/LisaKonysheva/TestAFNetworking

@ElfSundae This is likely due to https://github.com/AFNetworking/AFNetworking/pull/4533.
@LisaKonysheva In the mean time, you can likely work around the issue by setting the bundle identifier for the AFNetworking pod, but I'm not sure of the syntax for that, so you'll need to look it up.

@jshier Thanks! I've already made a fix by overriding bundle identifier in post_install, but would be nice to have it fixed properly

@LisaKonysheva It seems like a CocoaPods issue, did you tried upgrading your CocoaPods?
From your demo project, Podfile.lock shows COCOAPODS: 1.6.2, the latest version is 1.9.1.

@ElfSundae Yes, that was it, I've updated to the latest version, now everything works correctly. I guess we can close the issue. Thanks a lot!


HTTP client can be configurate outside the SOAP module.

Using an external HTTP Client allows the users to have more control over how he communicates with the service.
For example, adding certificates to the transport configuration.
httpClient := &http.Client{
  Transport: &http.Transport{
    TLSClientConfig: &tls.Config{
      InsecureSkipVerify: true,
    },
  },
}

soapClient := gosoap.SoapClient(url, httpClient)

And any kind of configuration for the HTTP Client will apply even though when the library is getting the definitions.

Codecov Report

Merging #44 into master will increase coverage by 0.43%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master     #44      +/-   ##
=========================================
+ Coverage   71.37%   71.8%   +0.43%
=========================================
  Files           5       5
  Lines         262     266       +4
=========================================
+ Hits          187     191       +4
  Misses         63      63
  Partials       12      12

Impacted Files
Coverage Δ

response.go
50% <ø> (ø)
:arrow_up:

request.go
75% <ø> (ø)
:arrow_up:

soap.go
73.19% <100%> (+0.56%)
:arrow_up:

wsdl.go
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Hi @highercomve,
Can you fix the problem with the tests?
Thank you

Yeah, I will I did some changes and I forget about the test.

 HTTP client can be configurate outside the SOAP module


Refactor the Modal component to be more generic

The Modal component is used to display a popup modal when users click on "About" or "Privacy" on the navbar.
Current state:
// _app.js
...
<NavBar
  setShowAboutModal={setShowAboutModal}
  setShowPrivacyModal={setShowPrivacyModal}
/>

{(showAboutModal || showPrivacyModal) && (
  <Modal
    modalType={showAboutModal ? "about" : "privacy"}
    setShowAboutModal={setShowAboutModal}
    setShowPrivacyModal={setShowPrivacyModal}
  />
)}
...

The mechanism to show either the About or Privacy's content is not generic. There are two setState methods for each content.
Ideal state:
There is a generic Modal component that receives two props: (1) setOpen that dictates whether the modal should open, and (2) textContent that includes the texts inside the modal.

I can work on it, can you assign it to me?

@mahdiQaempanah Done. Let me know if you have any questions along the way 🙂

I sent the pull request.
https://github.com/qu8n/focusbeacon/pull/23


Clarification about DASH-Thumbnails support in exoplayer

Unfortunately we can't answer all questions. Unclear questions or questions with
insufficient information may not get attention.
Before filing a question:

Ask general Android development questions on Stack Overflow
Search existing issues, including issues that are closed
https://github.com/androidx/media/issues?q=is%3Aissue
For ExoPlayer-related questions, please also check for existing questions on
the ExoPlayer tracker:
https://github.com/google/ExoPlayer/issues?q=is%3Aissue

When filing a question:
Describe your question in detail.
In case your question refers to a problem you are seeing in your app:

Output of running $ adb bugreport in the console

In case your question is related to a piece of media:

URI to test content
For protected content:

DRM scheme and license server URL
Authentication HTTP headers

Don't forget to check ExoPlayer's supported formats and devices, if applicable
(https://developer.android.com/guide/topics/media/exoplayer/supported-formats).
If there's something you don't want to post publicly, please submit the issue,
then email the link/bug report to<EMAIL_ADDRESS>using a
subject in the format "Issue #1234", where #1234 is your issue number (we don't
reply to emails).

Hi
I'd like to clarify and make sure please whether the ExoPlayer in version 2.13.2 support Thumbnails in DASH playout
here's an example of the additional Adaptation Set containing the Thumbnail in the DASH Manifest MPD:
1.This type of Adaptation Set is being supported for the exoplayer 2.13.2 to display the Thumbnails when moving fast forward/rewind on the played program?
2. any modifications need to be made in the player parameters to support the Thumbnails ?
thanks.

DASH_Thumbnail_Adaptation_Set_Example.txt

Hi,
Support for DASH thumbnails playback in Media3 1.3.0, means it's aligned with the DASH-IF interoperability points ? so that for Thumbnails' signaling provided within the DASH Manifest there'll be an additional Adaptation Set with ContentType of 'image' and mimeType of 'image/jpeg' (as per the .txt file I have previously attached) - will Media3 1.3.0 support this structure and display the thumbnails when moving forward/backward on the video ?
thanks.

As I said above, you need manually enable this track if you want to use it and then ExoPlayer outputs the images at the right time to the image output (which you can use to update a corresponding UI element).

Hi
can you please describe with the exact details of this track and its properties we need to enable on the Media 3 code in order to see the image/thumbnails ?
thanks.


Foundation set up for compositional layout

This ticket set up the foundation of the compositional support.

Separate the flow layout and compositional layout section controller
Add the bridge between adapter and compositional layout provider

Hey @Marcocanc, we are updating the SectionKit for compositional layout support, could you also help us to take a look since you are one of the creators of the library? 🙏


Discussion: whether to add new query syntaxes (syntax sugars)

New syntaxes have been proposed several times

https://github.com/risingwavelabs/risingwave/issues/9092
https://github.com/risingwavelabs/risingwave/issues/7506

IIRC until now we haven’t introduced any new query syntaxes/sugars (only some new statements). To avoid bikeshedding, it's time to decide our general attitude/policy about whether and when to add syntax sugars.
Arguments against new syntaxes

We have claimed to be PG-compatible. Users might feel confused if they found we have convenient new syntaxes. We might at least have a doc listing our new syntaxes if we are going to add some.

Our users mainly run long-running MVs instead of ad-hoc queries (unlike Clickhouse/Bigquery/Snowflakes/...), so they can write the SQLs in an editor and it's not that inconvenient and painful.
Besides,

I think it appears to be some dbt-level stuff, like a macro and users write that and get translated automatically, but still send the original to our Frontend to process. No changes need to be made on our side.

Originally posted by @lmatz in https://github.com/risingwavelabs/risingwave/issues/9092#issuecomment-1545468776

A technical concern is that adding new syntaxes may break other things unexpectedly, as SQL is complex and not well-designed.

Arguments for new syntaxes

The new syntax is really convenient in some use cases...

Just feel that the ultimate goal is letting people use RW smoothly,
and being compatible with PG(PG's syntax works in RW) is a proxy goal because if DuckDB suddenly becomes the most popular DB and PG becomes the least popular, it makes sense for us to be compatible with DuckDB.
And providing something extra does not prevent PG users from using their favorite syntax.

Originally posted by @lmatz in https://github.com/risingwavelabs/risingwave/issues/7506#issuecomment-1403154353

Other points

If we do want to add, what's the criteria to add? (Maybe just case by case arguments)

How much is the proxy goal PG-compatibility valid?
One real problem is that many PG driver libraries don't work with RisingWave now, mostly due to the complexity of system tables. So we don't benefit that much from the PG-ecosystem (at least for now). And IIRC we decided to develop some custom drivers for some libraries.
But I think a familiar (or popular) syntax of course lowers the user's learning burden.

I think PG-compatible means that "RisingWave can run the pg SQL without high migration cost" and not the reverse. I do not think there are users want to copy RisingWave's SQL to a PG or other PG-compatible databases. And also, we have support many things PG can not do such as TUMBLE, HOP or CREATE SINK.

We have claimed to be PG-compatible.

Pg also claimed to be standard-compatible, but they add many new syntaxes.

We might at least have a doc listing our new syntaxes if we are going to add some.

risingwave.dev can do this, but I don't think it's necessary.
Redshift also claimed to be pg-compatible, but they don't list every details that are incompatible, e.g. https://docs.aws.amazon.com/redshift/latest/dg/r_CONNECT_BY_clause.html is only available in Redshift.

Users might feel confused if they found we have convenient new syntaxes.

IMO no user will really port some SQL directly from Pg, most of them port their SQL from big data system. Pg-compatibility just make them easy to write SQLs. So the key concept is ease-to-use.

they can write the SQLs in an editor

They also need to debug their SQLs interactively.

BTW, we've already add our new syntaxes, e.g. SHOW families.

I do not think there are users who want to copy RisingWave's SQL to a PG or other PG-compatible databases

I'm imagine there's a cognitive problem: If I see a DB claims to be PG-compatible, and then found a new syntax, I may begin to doubt whether the claim is true. BTW, I think this already happened when users meet problems of client libraries..

And also, we have supported for many things PG can not do such as TUMBLE, HOP or CREATE SINK.

They are necessary new features. I want to discuss mainly syntax sugars here, which seems both reasonable and not that necessary at the same time.

Pg also claimed to be standard-compatible, but they add many new syntaxes.

FYI: https://wiki.postgresql.org/wiki/PostgreSQL_vs_SQL_Standard

I do not think there are users who want to copy RisingWave's SQL to a PG or other PG-compatible databases

I'm imagine there's a cognitive problem: If I see a DB claims to be PG-compatible, and then found a new syntax, I may begin to doubt whether the claim is true. BTW, I think this already happened when users meet problems of client libraries..

And also, we have supported for many things PG can not do such as TUMBLE, HOP or CREATE SINK.

They are necessary new features. I want to discuss mainly syntax sugars here, which seems both reasonable and not that necessary at the same time.

At least SHOW TABLES and SHOW CREATE TABLE is not necessary :)

BTW, I think this already happened when users meet problems of client libraries

I think it is just what I say. Users only are confused when they found something is not supported rather than they found some new syntax.

I'd like to propose more syntax sugars I want to do.

CREATE MVIEW as an alias to CREATE MATERIALIZED VIEW.
COMMENT over a field declaration directly instead of COMMENT ON statement (It's very welcome and almost supported by most databases).
trailing comma everywhere.

We might at least have a doc listing our new syntaxes if we are going to add some.

risingwave.dev can do this, but I don't think it's necessary.
Redshift also claimed to be pg-compatible, but they don't list every details that are incompatible, e.g. https://docs.aws.amazon.com/redshift/latest/dg/r_CONNECT_BY_clause.html is only available in Redshift.

I didn't find they official claim to be PG-compatible. They call themselves "Amazon Redshift SQL".
I found such a doc "Amazon Redshift and PostgreSQL" which seems good enough.

Another RW feature which is already documented :(
CREATE TABLE IF NOT EXISTS taxi_trips(
    id VARCHAR,
    distance DOUBLE PRECISION,
    duration DOUBLE PRECISION,
    fare STRUCT<
      initial_charge DOUBLE PRECISION,
      subsequent_charge DOUBLE PRECISION,
      surcharge DOUBLE PRECISION,
      tolls DOUBLE PRECISION>);

struct<> is not a pg type, we should use CREATE TYPE in pg way.

CREATE MVIEW as an alias to CREATE MATERIALIZED VIEW.

(bikeshedding) BTW, psql can auto-complete MATERIALIZED VIEW by TAB.

At least SHOW TABLES and SHOW CREATE TABLE is not necessary :)

struct<> is not a pg type

Yes I know we have new statements and new data types. (we also have int256) I mentioned that at the beginning.
I'm not sure whether it's reasonable, but I do have a feeling that query-level syntax sugars are of different nature.

https://materialize.com/docs/sql/select/#using-query-hints Options clause in materialize.

cc @fuyufjh @lmatz @neverchanje @xiangjinwu

DEFAULT INDEX in materialize https://materialize.com/docs/sql/create-index/#syntax

Two previous issues and a meta-discussion issue with 15 replies (now 16 and continue) already say a lot about the nature of the discussion, i.e.:

it just all boils down to personal preference, which is not wrong
who has been bothered by the "insufficient" syntax sugar(which could be wrong due to the wrong way of expressing certain SQL), and who just doesn't feel the pain because he does not run into these cases on a daily basis. This could be asymmetric: the affected part is always small with respect to the entire SQL syntax and is likely to only affect a small percentage of people who needs to deal with that part constantly.

I support

just case by case arguments  but (concrete arguments, not taste)

and a simple vote (voters specify the reason or agree to others' arguments) that can be triggered at most every XXX period with new arguments and the vote last for XXX period.

Cases vary a lot in terms of the potential implication they can have. Over-generalization can prevent any conclusion from being made.
Following other DBs or encouraging new inventions are both just strategies, which means they work sometimes and do not work sometimes. Someone/some product is going to make the first move after all.
Avoid whataboutism, which again can prevent any conclusion from being made.
Developers of Risingwave are also real users. They can either argue from their hands-on experience and/or refer to third-party feedback.

The above are all with respect to the topic of this issue add new query syntaxes (syntax sugars).
add is not invalidating any existing syntax. This can be "guaranteed" by adding new test cases. (Proposers of new syntaxes can be responsible for this).
We remark that matter of fact, nobody knows how many incompatibles RW has with regard to PostgreSQL right now. The compatibility can also only be "guaranteed" by adding new test cases progressively too.
A vote with concrete arguments from both sides leads to a decision and a second-time motion allows people to change their minds.
But voting is also just a strategy that tries to have a balance, so feel free to challenge it too.

Super +1 for case by case arguments/concrete arguments
For myself, I am usually willing to play the role of the opponent. A common problem for engineers (especially the smart ones) is trying too hard to avoid "repeat by yourself". But when you look at the big picture, this syntactic sugar may have reduced the workload for 5% of users, but created an average of 15s of confusion for the remaining 95%. If that's the case, it's just not worth it. What's more, those 5% of users often don't mind "repeat by yourself". :)

To summarize, the consensus is that

No one completely rejects adding syntax sugars. We are open to new syntaxes.
PG-compatibility should not be harmed. i.e., new syntax should not conflict with PG syntax.
Case by case arguments are required, as cases vary a lot in terms of the potential implications. There are different strategies proposed:

Follow other DBs
Wait for users' feedbacks
Voting

But people have different attitudes (or philosophy?) towards the necessity of syntax sugars (and maybe also usability features like https://github.com/risingwavelabs/risingwave/issues/10151).
@TennyZhuang is the most aggressive. He thinks micro inventions/improvements are also worth it. We can do it if it can make our users or ourselves even a little happier.
@fuyufjh is the most conservative, He tends to avoid new features unless there are significant benefits. "Any code can be problematic." (So less is better.)

But when you look at the big picture, this syntactic sugar may have reduced the workload for 5% of users, but created an average of 15s of confusion for the remaining 95%. If that's the case, it's just not worth it. What's more, those 5% of users often don't mind "repeat by yourself". :)

This also confirms to @lmatz 's words

This could be asymmetric: the affected part is always small with respect to the entire SQL syntax and is likely to only affect a small percentage of people who needs to deal with that part constantly.

I can imagine further debate like this:

But maybe these small percentage of people are really painful? We can't really know it. So @neverchanje 's idea of waiting for users' feedbacks sound the most practical.

But this prevents micro inventions. And user feedback is a lagging indicator, maybe users don't tell and just walk away if they are unhappy.

But syntax sugars (or some other minor UX improvements) aren't a decisive point that decides whether to use RisingWave or not.

But usability is our target, and we can have a higher standard as aspiring engineers.

I think such debate can hardly come to an end, but practically I guess this is our future:

Of course these are not top-priority, so we should focus on other priorities if there are any.
When there are user feedbacks, we would begin to consider it.
@TennyZhuang got tired of debating, so we don't (or seldom) do micro inventions ahead of time.

I will close this discussion now, but feel free to add some more comments or correct me if I'm wrong.


Update Apache axis 2 packages to 1.8.2

Checklist

[x] the contributor license agreement is signed
[x] commit message follows commit guidelines

Description of change
resolves #4217
HTTPConstants was moved to a different location in the package from 1.8.x, so changing the import reference was all that was required there.
OMLinkedListMetaFactory can no longer be instantiated directly - you have to use OMLinkedListMetaFactoryLoader to load one up. load(Map<String,Object> properties) doesn't ever seem to refer to the properties variable so it should be safe to use null as the input.

hmmm, okay so now we are getting deduplicate errors. :thinking: back to the drawing board.

Added a deduplication strategy for javax.servlet, this allows me to installerZip so fingers crossed it builds correctly this time.

Excellent, thank you @SammyIsConfused


reference error on make -j8 ubuntu 16.04

I keep getting this error on install
/home/russ/cpp-ethereum/libethcore/EthashCUDAMiner.cpp: In member function ‘workLoop’:
/home/russ/cpp-ethereum/libethcore/EthashCUDAMiner.cpp:202:96: warning: ‘startN’ may be used uninitialized in this function [-Wmaybe-uninitialized]
m_miner->search(w.headerHash.data(), upper64OfBoundary, *m_hook, (w.exSizeBits >= 0), startN);
^
/home/russ/cpp-ethereum/libethcore/EthashCUDAMiner.cpp:199:12: note: ‘startN’ was declared here
uint64_t startN;
^
/tmp/ccgJRx2q.ltrans19.ltrans.o::__fatDeviceText: error: undefined reference to 'fatbinData'
collect2: error: ld returned 1 exit status
ethminer/CMakeFiles/ethminer.dir/build.make:118: recipe for target 'ethminer/ethminer' failed
make[2]: *** [ethminer/ethminer] Error 1
CMakeFiles/Makefile2:493: recipe for target 'ethminer/CMakeFiles/ethminer.dir/all' failed
make[1]: *** [ethminer/CMakeFiles/ethminer.dir/all] Error 2
Makefile:127: recipe for target 'all' failed
make: *** [all] Error 2
any help would be appreciated

I have the same problem, I can not find a solution to this problem, but with the parameter cmake -DBUNDLE = miner .. everything is fine, but I'm not sure what CUDA is.
I will be very glad of any help, too!

same problem. want to mention, before  i did
git clone https://github.com/Genoil/cpp-ethereum/
cd cpp-ethereum/
git checkout 110
mkdir build
cd build
cmake -DBUNDLE=cudaminer ..
make -j8

I have same problem.
I try the method，but the problem still exists

git clone https://github.com/Genoil/cpp-ethereum/
cd cpp-ethereum/
git checkout 110
mkdir build
cd build
cmake -DBUNDLE=cudaminer ..
make -j8

Workaround:
In the fork https://github.com/ethereum-mining/ethminer there are binaries that work with cuda and run stable, at least on my ubuntu 14.04

So I was able to get it working on 16.04 but re downloading and following the readme instructions instead of the ones posted everywhere, they seemed the same but don't know the difference..
Gave me an extra 18% hashrate

Hey! You are writing an issue inside the "genoil" ethminer which does not get updated anymore. Please check out the new ethminer fork from 'chfast'.
This is the new repository:
https://github.com/ethereum-mining/ethminer/
You can find the new releases here:
https://github.com/ethereum-mining/ethminer/releases
If the issue still occurs with the new ethminer there please write a new issue here:
https://github.com/ethereum-mining/ethminer/issues


IPython history commands do not work in Python interactive

Environment data

VS Code version: See below
Extension version (available under the Extensions sidebar): 2019.1.0
OS and version: See below
Python version (& distribution if applicable, e.g. Anaconda): Anaconda 5.x Python 3.6.7
Type of virtual environment used (N/A | venv | virtualenv | conda | ...):  conda env
Relevant/affected Python packages and their versions: N/A

Version: 1.30.2 (user setup)
Commit: 61122f88f0bf01e2ac16bdb9e1bc4571755f5bd8
Date: 2019-01-07T22:54:13.295Z
Electron: 2.0.12
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
OS: Windows_NT x64 10.0.17763
Jupyter Server URI: http://localhost:8888/?token=d736b402953fa73de5370395920aaae990f89992e26a5062
Python Version:
3.6.7 |Anaconda, Inc.| (default, Dec 10 2018, 20:35:02) [MSC v.1915 64 bit (AMD64)]
C:\Users\keijik\AppData\Local\Continuum\anaconda3\envs\play\python.exe
Jupyter Notebook Version: (5, 7, 4, '')
Expected behaviour
Typing Out[1], _1, etc. return the value of Out[1]
Actual behaviour
Not sure exactly what the logic is, but after one expression, _1 returns the following, which is part of the printed value from the kernel starting up.
'3.6.7 |Anaconda, Inc.| (default, Dec 10 2018, 20:35:02) [MSC v.1915 64 bit (AMD64)]'
Subsequent _2, etc., return unexpected values as well.
Steps to reproduce:

Start Python Interactive
Type in an expression like 42
Type in _1

Logs
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
Jupyter Server URI: http://localhost:8888/?token=472809184299ca506609537ed2f3ab698ec3ae56b9761f29
Python Version:
3.6.7 |Anaconda, Inc.| (default, Dec 10 2018, 20:35:02) [MSC v.1915 64 bit (AMD64)]
C:\\Users\\keijik\\AppData\\Local\\Continuum\\anaconda3\\envs\\play\\python.exe
Jupyter Notebook Version: (5, 7, 4, '')

[1]

3
3
3

[2]

_1
_1
'3.6.7 |Anaconda, Inc.| (default, Dec 10 2018, 20:35:02) [MSC v.1915 64 bit (AMD64)]'

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help; turn on source maps to make any tracebacks be useful by running Enable source map support for extension debugging)
N/A

We might be able to execute silently instead. I believe this does return results as well, we just don't use them at the moment.

Should be fixed now with https://github.com/Microsoft/vscode-python/commit/7d702c3ca8b0e157fd25860751b87470b6431625#diff-601e30a159c6fb11ce38eb98cad04db4


Optional path parameters?

Is there syntax I am missing to allow Javalin to handle "optional" path parameters i.e. I'd like to be able to have both /dashboard/ and /dashboard/123 point to the same handler.
Obviously, I can do this by setting up two paths to the same handler, but I was wondering if there was a way to say that a path parameter may or may not be present i.e. /dashboard/{id?} or something similar.
I imagine this might make it very hard to identify whether there are duplicate routes and so it may well not be possible - but I just thought I'd check before I go around adding multiple routes when I can do it in one.

@tomhillgreyridge I think this would be confusing, as it would also require Context#pathParam to now be nullable. In what scenario should your dashboard path be optional? What do you display if there is no ID? Should you be using a query parameter instead?

Here's a scenario.  A user of the application can have a small number of projects, one of which is the "currently active" project.  When you come into the project dashboard we show you the "active" project plan if one isn't selected and then a bunch of links where you can select any of the others.
/projectplans/ -> would show the plan for the active project
/projectplans/1234 -> would show the plan for project 1234
Effectively, in our "controller" we do "if id is null, fetch the default and show that".  I've currently gone with a query parameter and am fine with that, it just isn't consistent with everywhere else where we do
/projectplans/edit/1234
/projectplans/complete/1234
As I say, not a biggy, I just wanted to know I wasn't missing anything

As I say, not a biggy, I just wanted to know I wasn't missing anything

You're not missing anything :)

Effectively, in our "controller" we do "if id is null, fetch the default and show that". I've currently gone with a query parameter and am fine with that, it just isn't consistent with everywhere else where we do

Personally I would solve this with a redirect from /projectplans/ to the "active" project.

I had several similar cases, I usually just register those variants as standalone routes and redirects them internally to the main handler, like e.g.:

https://github.com/dzikoysk/reposilite/blob/3bfe2a00a6bb4c70c31c79f7d277519a6b12b169/reposilite-backend/src/main/kotlin/com/reposilite/maven/infrastructure/MavenApiEndpoints.kt#L78-L80

And then I'm taking path parameter from ctx.pathParamMap[property], so it won't throw in case if it's missing.


Asterisk not described in printf format

The asterisk in printf("%*d") should be mentioned somewhere.

Done in 2.2.1


Update Composer dependencies (2024-06-19-00-18)

Visual regression test passed!
View the visual regression test report


fix: delete new entry backup

Proper fix for #2259

@barthc, I reviewed it a while back just forgot to submit it 🤦

@barthc, I think the annoyance of that bug overcomes the scenario I described. Merging this and we can handle that scenario in a future PR


Using the Registration with Postgres cannot start as the SQL database initialization fails

Describe the bug

Serving the registration app with a postgres backed database fails as multiple steps in the database creation process are not done

The ips table does not have a unique constraint with address
Manually adding the constraint still fails as the token and name are incompatible types

To Reproduce

Create a new postgres database with "createdb -O <registration-user> <registration-table>"
Connect to the postgres database using the "postgress://..." connection string
The container will crash hard and will not start up and will display the error about unique constraints, fixing that it still will not start as there are incompatible types with the token and name

Expected behavior

Database is successfully created and the container will start
Screenshots

N/A
System:

OS: Ubuntu (Docker/K8s)
python version: Docker container version
matrix registration version: v0.9.1/v0,9.1.post1

Additional context

N/A

pip install matrix-registration==1.0.0.dev5
this release should fix it

alright docker image:
docker pull zeratax/matrix-registration:v1.0.0.dev6

That seemed to work, thanks for the quick update!


[Bug] Can Initiate Multi-mint Swap With Single Mint And Lose Funds

Steps to reproduce:

User has 2 mints, (Mint 1) with funds and (Mint 2) without funds. User tries to swap from (Mint 2) that has 0 funds to (Mint 1) that already has funds.

User receives not enough funds error in pop-up

User selects (Mint 1) that has funds and proceeds with swap to (Mint 1).

Operation succeeded, but now funds are missing from user's wallet.

Can you check whether you have a pending invoice (in the invoices tab) and what happens when  you press the refresh button?

@cjbeery24 can you check whether the funds were still available as an invoice you need to redeem?


[SPARK-46875][SQL] When the mode is null, a NullPointException should not be thrown

What changes were proposed in this pull request?
The pr aims to provide better prompts when option's mode is null.
Why are the changes needed?
In the original logic, if the mode is null, Spark will throw a NullPointerException, which is obviously unfriendly to the user.
val cars = spark.read
      .format("csv")
      .options(Map("header" -> "true", "mode" -> null))
      .load(testFile(carsFile))
cars.show(false)

Before:
Cannot invoke "String.toUpperCase(java.util.Locale)" because "mode" is null
java.lang.NullPointerException: Cannot invoke "String.toUpperCase(java.util.Locale)" because "mode" is null
	at org.apache.spark.sql.catalyst.util.ParseMode$.fromString(ParseMode.scala:50)
	at org.apache.spark.sql.catalyst.csv.CSVOptions.$anonfun$parseMode$1(CSVOptions.scala:105)
	at scala.Option.map(Option.scala:242)
	at org.apache.spark.sql.catalyst.csv.CSVOptions.<init>(CSVOptions.scala:105)
	at org.apache.spark.sql.catalyst.csv.CSVOptions.<init>(CSVOptions.scala:49)
	at org.apache.spark.sql.execution.datasources.csv.CSVFileFormat.inferSchema(CSVFileFormat.scala:60)

After:
It will fall back to PermissiveMode mode and then display the data normally, as shown below:
18:54:06.727 WARN org.apache.spark.sql.catalyst.util.ParseMode: mode is null and not a valid parse mode. Using PERMISSIVE.

+----+-----+-----+----------------------------------+-----+
|year|make |model|comment                           |blank|
+----+-----+-----+----------------------------------+-----+
|2012|Tesla|S    |No comment                        |NULL |
|1997|Ford |E350 |Go get one now they are going fast|NULL |
|2015|Chevy|Volt |NULL                              |NULL |
+----+-----+-----+----------------------------------+-----+

Does this PR introduce any user-facing change?
Yes, When mode is null, it fallback to PermissiveMode  instead of throwing a NullPointerException.
How was this patch tested?

Add new UT.
Pass GA.

Was this patch authored or co-authored using generative AI tooling?
No.

+1, LGTM. Merging to master.
Thank you, @panbingkun.


CLI v0.1.1-preview8 has openjdk fixes

AdoptOpenJDK has a profilic versioning scheme, that changes all the
time. I added some of the ones that will probably work (80% sure).
The tests have run in my local workspace.

Sorry guys, that wasn't the intention


Add E2E test for puppet android app

Adds github action workflow to run tests against trigger.
Adds test case to run tests against sauce labs.
Adds necessary boilerplate code to setup test execution.

@vkola

Agree with the explicit sleeps.
They are specifically used in the context where we come back from the android settings page to the app.
Sane approach is to bring forward the Chatter activity, than pressing back button twice.
However, activity to foreground didn't work for Real android device in Saucelabs but worked for the emulator on my local machine. So had to resort to this. With some checks in place, we should be able to avoid those explicit sleeps.

Got it


App rejected from the App Store because of "Android" in the Summary of the package

I submitted my app using wakelock_plus for the review in the App Store and it has been rejected with this explanation:

The only usage of "android" outside of comments is this, so I assume this is the cause:

Sorry, there was another occurence of "Android" in my promotional texts, so this is probably irrelevant.


When viewing claim at vanity URL, same pice of content is in "related" content list

The Issue
Steps to Reproduce

Go to lbry://three
See the top item in "related"

Expected Behaviour
That should be removed from the list
Suggested Solutions
We need to pass in the full claim uri into <RecommendedContent uri={full uri plus claim id} />

This is still occuring, reopening. Go to lbry://five, and you'll see the same claim in recommended. Maybe the difference is that it has a channel?

This stopped working because previously, the exact match was always the first result. We just removed the first result assuming it would be the exact match (which is honestly not the best solution).
Either way, the first result coming back is lbry://two which is a porn video with a huge bid. I created https://github.com/lbryio/lighthouse/issues/132. I think this issue should be fixed by that.

Fixed with https://github.com/lbryio/lbry-redux/pull/103


Installation: winget keeps reporting Wasmtime update available

This relates to installing the wasmtime CLI on Windows using the Windows package manager winget
Environment
Windows 11 Pro
Powershell 7.3.4
winget v1.5.1081-preview
I query winget for a list of my packages where an upgrade is available
PS> winget upgrade
Name                                    Id                                  Version    Available  Source
--------------------------------------------------------------------------------------------------------
Wasmtime                                BytecodeAlliance.Wasmtime           8.0.0      8.0.1      winget

I then update Wasmtime (winget ID BytecodeAlliance.Wasmtime) from 8.0.0 to 8.0.1 using the command
PS> winget upgrade BytecodeAlliance.Wasmtime
The installation went perfectly and I open a new Powershell prompt and check the version number:
PS> wasmtime -V
wasmtime-cli 8.0.1

When run winget upgrade again Wasmtime is still there
PS> winget upgrade
Name                                    Id                                  Version    Available  Source
--------------------------------------------------------------------------------------------------------
Wasmtime                                BytecodeAlliance.Wasmtime           8.0.0      8.0.1      winget

I have seen this type of problem before for other packages and for many the root cause was the manifest file.

AFAIK the winget package is not maintained by the bytecodealliance.

@bjorn3 Seems you are right
I did some digging in the Winget package Github repository and the maintainer of the wasmtime entry has neither contributed to the wasmtime repository nor is a member of the bytecodealliance Github "org".
Therefore I am closing the issue


CFP: Support PROXY Protocol from external LoadBalancers

Cilium Feature Proposal
Is your feature request related to a problem?
Some Load Balancing solutions, such as Hetzner's LoadBalancer and AWS' Classic Load Balancer are using the HAProxy Proxy Protocol to pass source IP information along. If you use those Load Balancers with a Cilium-enabled Kubernetes Cluster you currently can not whitelist certain IP ranges, because cilium only sees all connections coming from the Load Balancer.
Describe the feature you'd like
Cilium parses the HAProxy Headers and replace original source IP information with those in the header.
(Optional) Describe your proposed solution

Add global options to:

Enable PROXY Protocol support
Set LoadBalancer Trusted IP range

Check if PROXY support is enabled and the original source IP comes from the trusted proxy IP range.

If not -> use original IP, do not parse anything
If both true > Try to parse the PROXY header, replace original source ip with parsed source ip. Fallback to original IP if parsing fails.

More Information

https://www.haproxy.org/download/1.8/doc/proxy-protocol.txt
https://developers.cloudflare.com/spectrum/how-to/enable-proxy-protocol/#the-proxy-protocol-v2-header
https://docs.nginx.com/nginx/admin-guide/load-balancer/using-proxy-protocol/
https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/filters/listener/proxy_protocol/v3/proxy_protocol.proto

Related: https://github.com/cilium/cilium/issues/7531

There seems to be interested in this feature, can we keep this open please?

There seems to be interested in this feature, can we keep this open please?

We are also interested in this feature because of it's use-case in per host proxy deployment model.

Hello,
until the support is added (if possible of course), is there a way to receive real IP addresses inside Kube ?

Thanks for your answer, I was hoping that it was possible now with some configurations tricks :)

https://github.com/cilium/cilium/issues/26530

if you use ingress service, it also support ProxyProtocol,  see this commit: https://github.com/chaunceyjiang/cilium/commit/24911b03cf4c3f06481394b12e1a06762dce5d2a

I also have a similar use case and would be interested in such functionality 👍🏻

@gadiener there is PR open its just waiting for merge

Thanks @zetaab I saw the PR, great work!
Does it cover the use case presented in my comment?

It'd be great to receive the original source IP information to the destination pod as well. I could't find a way to do that with Cilium for TCP traffic. With Istio, for example, I can resolve the PROXY Protocol header on the sidecar and pass down the information using the transparent proxy feature.

@gadiener you just need to have somekind of component in kubernetes cluster that understands proxy protocol. For instance it can be achieved using nginx-ingress (proxy protocol mode). Nginx can inject the real source ip to x-forwarded-for header as visible to pod itself


Add AsyncButton to Storybook

Summary
Fixes #9358

Occurred changes and/or fixed issues

Merged buttons markup with a story for the AsyncButton
Added all the props related to the button

Technical notes summary

Added i18n/exist getter

Areas or cases that should be tested

Areas which could experience regressions

Screenshot/Video

@scures I am adding you again for the review as I think you are the most suitable person to review this with @kwwii .
I am creating this PR as a draft because:

We should definitely discuss how we handle the buttons and maybe create a new component as suggested
The way the props are used seem quite odd most of them
Some functionalities seems buggy: delay and icon
The way we present the props probably requires some design direction in this case

Here's a video of ho it looks like at the moment
https://github.com/rancher/dashboard/assets/5009481/7af3e5a6-64f0-4cc5-a9ff-e6d29ee977b1


[BUG] Cannot load beit_base_patch16_224_in22k model

MODEL_NAME = "beit_base_patch16_224_in22k"
model = timm.create_model(MODEL_NAME, pretrained=True, num_classes=0)

Getting the following error.
UnpicklingError                           Traceback (most recent call last)
[<ipython-input-43-71fd1ed080e1>](https://localhost:8080/#) in <module>()
      1 MODEL_NAME = "beit_base_patch16_224_in22k"
----> 2 model = timm.create_model(MODEL_NAME, pretrained=True, num_classes=0)

7 frames
[/usr/local/lib/python3.7/dist-packages/torch/serialization.py](https://localhost:8080/#) in _legacy_load(f, map_location, pickle_module, **pickle_load_args)
    918             "functionality.")
    919
--> 920     magic_number = pickle_module.load(f, **pickle_load_args)
    921     if magic_number != MAGIC_NUMBER:
    922         raise RuntimeError("Invalid magic number; corrupt file?")

UnpicklingError: invalid load key, '='.

@dingusagar from master branch working fine for me, note the download URL changed for those models, so the last pip release will be wrong, but master here and pip install --pre will get a version that works. If that doesn't work it's an issue with your net connection.

Oh, and I'll be updating pypi within next few days with a non pre 0.6 release so that won't be an issue anymore.

@librauee again, it works fine, if it isn't working it is your network connection (or corrupt files in your checkpoint cache).
>>> m = timm.create_model('beit_base_patch16_224_in22k', pretrained=True)
Downloading: "https://conversationhub.blob.core.windows.net/beit-share-public/beit/beit_base_patch16_224_pt22k_ft22k.pth" to /home/.../.cache/torch/hub/checkpoints/beit_base_patch16_224_pt22k_ft22k.pth
>>> m.head.weight
Parameter containing:
tensor([[-0.0127, -0.0122,  0.0322,  ..., -0.0126, -0.0174,  0.0007],
        [ 0.0259, -0.0425, -0.0140,  ...,  0.0711,  0.0010, -0.0091],
        [-0.0095, -0.0110,  0.0028,  ..., -0.0059, -0.0110, -0.0241],
        ...,
        [-0.0127, -0.0145, -0.0012,  ..., -0.0077, -0.0150, -0.0199],
        [-0.0757,  0.1348, -0.0583,  ..., -0.1333, -0.0655, -0.1010],
        [-0.0329,  0.0668, -0.0635,  ..., -0.0143, -0.0287, -0.0231]],
       requires_grad=True)


Simplify schema by using definitions

Towards https://github.com/giantswarm/giantswarm/issues/23014
Towards https://github.com/giantswarm/roadmap/issues/1949
This is a copy/paste of schema from https://github.com/giantswarm/default-apps-vsphere/pull/85

I have to remove top level allowAdditionalProperties: false because of:
'Deployment failed for `0.5.3-4addc50ac7c17454246f4933d3eec78328c726a4`
      with `unknown-error`: "values don''t meet the specifications of the schema(s)
      in the following chart(s):\ndefault-apps-cloud-director:\n- (root): Additional
      property clusterCA is not allowed\n- (root): Additional property chartOperator
      is not allowed\n- (root): Additional property cluster is not allowed\n- (root):
      Additional property clusterCIDR is not allowed\n- (root): Additional property
      baseDomain is not allowed\n- (root): Additional property clusterID is not allowed\n-
      (root): Additional property gcpProject is not allowed\n- (root): Additional
      property provider is not allowed\n- (root): Additional property bootstrapMode
      is not allowed\n- (root): Additional property clusterDNSIP is not allowed\n"'

I have to remove top level allowAdditionalProperties: false because of:
'Deployment failed for `0.5.3-4addc50ac7c17454246f4933d3eec78328c726a4`
      with `unknown-error`: "values don''t meet the specifications of the schema(s)
      in the following chart(s):\ndefault-apps-cloud-director:\n- (root): Additional
      property clusterCA is not allowed\n- (root): Additional property chartOperator
      is not allowed\n- (root): Additional property cluster is not allowed\n- (root):
      Additional property clusterCIDR is not allowed\n- (root): Additional property
      baseDomain is not allowed\n- (root): Additional property clusterID is not allowed\n-
      (root): Additional property gcpProject is not allowed\n- (root): Additional
      property provider is not allowed\n- (root): Additional property bootstrapMode
      is not allowed\n- (root): Additional property clusterDNSIP is not allowed\n"'

You could also leave additionalProperties: false and add all the properties that will get injected to the schema.
.clusterCA
.chartOperator
.cluster
.clusterCIDR
.baseDomain
.clusterID
.gcpProject
.provider
.bootstrapMode
.clusterDNSIP

And I think we should discuss how we can avoid this injecting of arbitrarily named properties on the root level of a schema.

You could also leave additionalProperties: false and add all the properties that will get injected to the schema.
.clusterCA
.chartOperator
.cluster
.clusterCIDR
.baseDomain
.clusterID
.gcpProject
.provider
.bootstrapMode
.clusterDNSIP

And I think we should discuss how we can avoid this injecting of arbitrarily named properties on the root level of a schema.

That would mess with my zen too much.

That would mess with my zen too much.

I understand. If it helps: this is what we do with cluster app schemas. I'd rather have the benefit of additionalProperties: false and a messy schema. (I'm not putting effort into annotations or anything for these properties.) It also serves as a reminder that this must go away at some point.