Podspec: Include SSKeychain as a dependency, rather than including the source

I've just run into a duplicate symbols issue after adding SSKeychain to my project (which also uses Simperium) and then I noticed that you include an (unprefixed!) version of this library in your source... Having a look at your Podfile, you seem to include most of your external stuff as Cocoapods dependencies (most notably JRSwizzle and SocketRocket) - why not do the same for SSKeychain?
But apart from that, if you also distribute your lib outside of Cocoapods, you should really think about prefixing your external dependencies (or remove them and require users to manually install them).

@danielr you're indeed right sir. We'll be soon updating the way we handle dependencies.
Thanks for the suggestion!

@danielr Dependencies prefixed, except for DiffMatchPatch, which will remain pristine, for the time being.
We'll be releasing a new Cocoapods version shortly, thank you!


Screenshot shows text highlighting

If you have some text highlighted on the code snippet it preserves that highlighting when the image is generated.
Not sure if this is desired or not. I unexpectedly generated an image with the highlight when I didn't want it.
Thanks for an awesome resource!

If you look at what's actually converting your code into an image
https://github.com/dawnlabs/carbon/blob/de11ff034fe4bc270ddf9550d6d12e3b3a1ba6c2/pages/editor.js#L75-L88
... and
https://github.com/dawnlabs/carbon/blob/de11ff034fe4bc270ddf9550d6d12e3b3a1ba6c2/pages/editor.js#L94-L103
... it merely just picks up your code and converts it to a .PNG image. Internally, it (the 3rd party library, dom-to-image) calls HTMLCanvasElement.toDataURL(), which in turns just returns a data URI.
IMO, I think the text highlight is a good thing, as I would sometimes want to highlight important sections of my code. Whether it was intended or not, I can't quite say. Hope this helps, tho!

Thanks for the code reference.
I don't mind it either way... but wasn't sure if it was desired or not so figured I'd submit an issue and allow the maintainers to decide.

It wasn't intended, but I'm with @yeskunall in that it can sometimes prove useful. Let's keep it in for now. Thanks for reporting, @vmitchell85, we're glad you like Carbon 👍.


Android TV Focus?

How can we use this on tv?there is no Focus for navigation with Dpad?is there a way to add it without touching the libs?

I would recommend to add an onFocusChanged modifier to your composables for program cell / channel / timeline, and use an appropriate ProgramGuideState::animateTo* method for each.
Check my answer here https://github.com/oleksandrbalan/programguide/issues/8#issuecomment-1810123264

Hey @techker  , have a look at my repo. Its still in early stages but it is developed for TV first and it can handle very large datasets https://github.com/sajidalidev/compose-epg-viewer/tree/develop . I appreciate your feedback to improve the library https://github.com/sajidalidev/compose-epg-viewer/tree/develop

hey, thx for the reply i will take a look for sure..been on this for a while..have different version im testing out. last one seems better, but still issues in navigation due to lots of data..
https://github.com/techker/ComposeTV_EPG

@techker I have had a quick look and it seems like you're not using lazy layouts(LazyColumn or LazyRow) or filtering the data to draw only visible data. You can check the Channels , Events composable in my repo. It should give you the idea.

ya, the first tries i was, but having issues with horizontalScrollState vs
vertical, then i noticed in my last example was able to do some
workarounds with Surface.. not easy..lol thx for the help
On Fri, Oct 25, 2024 at 10:30 AM Sajid Ali @.***> wrote:

@techker https://github.com/techker I have had a quick look and it
seems like you're not using lazy layouts(LazyColumn or LazyRow) or
filtering the data to draw only visible data. You can check the Channels
, Events composable in my repo. It should give you the idea.
—
Reply to this email directly, view it on GitHub
https://github.com/oleksandrbalan/programguide/issues/18#issuecomment-2437977557,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABOFGYRLBA4RYEP6DHJUZWTZ5JIYNAVCNFSM6AAAAABKVIXPNCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZXHE3TONJVG4
.
You are receiving this because you were mentioned.Message ID:
@.***>

No issues :)

Ya...i hate to admit it but i hate you LOL, i have been on this for a while on and off since my job is taking lots of my time, never got it to were your code is at.. i imported the jctvguide lib in my code and works very good.. now il study it to see where i went wrong and adapt it tweek it... i see i was close..but you nailed it. Thx again for your help. it will never be a release, but for sure i will credit your work on my page.

Haha, no worries. Happy to help. Let me know if you have any further questions.


[build] Errors building on Visual Studio 2015

Hi guys, and sorry for my english.
I've downloaded raylib, and I would like to use it with Visual Studio 2015. I am newbie at programming, but I am learning for a while now. So my problem is, when I want to build the projects, I've got a bunch of errors. I suppose that errors occurs, because of two header files are missing, or cant read. This two are : Cannot open include file: 'AL/al.h': No such file or directory, and Cannot open include file: 'GLFW/glfw3.h': No such file or directory.
I've tried to going through the configure description (raylib/wiki/Create-Visual-Studio-Projectstep ) step by step. Sadly, without any success, the two errors still there. Can anybody help me?
When I am using notepad++ version, it is fine and cool. (unfortunately it has no stepping mode debugging feature, as far as I know.)
Thanks
Phar

Have you tried the VS2015 solutions that come with raylib in folder raylib/project/vs2015?

Thank you for faster, than light reply. :)
Yes, I did, and I tried it on my pc and on my laptop.

It should be preconfigured to work... just checking it now.

Ok, I see, try building in Release mode...
I got the same issue in Debug mode, don't know why... include paths are correctly defined but VS2015 does not find the headers... weird...

ok... just found the issue... my fault, just configured paths for Release... >___<

Yess, cool :) I mean you found the problem :)

Issue corrected in commit https://github.com/raysan5/raylib/commit/ecf797cc7da985a6a4ebbd00b14b7056e582d714

@Phariax could you try updating project include paths to point to raylib/release/include folder?
Just go to project Properties (right-mouse-click over project) and:
Configuration Properties  >  C/C++  >  General  > Additional Include Directories
There you have to set the correct include paths, be careful with selected Configuration to be Debug.

I started to write another comment, but I'll do the change now, and I'll write soon.

I made the changes.  Now the raylib project build is succeed (and the core_basic_window example as well), so that is ok. But now, If I want to run the basic window example, I'v got an error window "...it's not a valid win32 application." It is doesn't matter I am trying to run debug or release.  I have tried to rewrite the Additional include directories path both debug and release, but If I tried building in debug path, It is doesnt work, just like before...
I hope my english is clear enough to understand my comment.

Ok, so I found the solution on the web. I had to set the project as a StartUp Project. After that I just restarted the Visual Studio and everything works fine.
Thank you for your quick help,it is awesome,  and keep up the good work.
Phar

Glad to read you managed to get it working. Closing the issue.

Hi raysan5,
I stumble upon the same problem today with VS2019, why not set the project to be a StartUp Project when you release the file so it will not happens anymore? isn't it the right fix?


Check AKA links

@crutkas,
Since you have access to the AKA links, I want to ask you to check them, with a couple notes

I see we use both https://aka.ms/powertoys-docs and https://aka.ms/PowerToysOverview
can we use "directories" in the links? like aka.ms/PowerToys/Overview or aka.ms/PowerToys/repo
powerToysReportBug and powerToysRequestFeature URLs can be simplified - labels (etc.) can be determined in the ~template~ form, not the URL
add links for newest modules
few suggestions for existing links (/devdocs/akalinks.md)

current
suggestion

getpowertoys
PowerToys/Store

powertoys
PowerToys/github or PowerToys/repo

powerToysGiveFeedback
PowerToys/issues

from when PT was created to now, AKA can do the subdirectory and args too. I don't see a pressing need to adjust as the legacy format would need to continue as it has become a known pattern IMO and any of the stuff inside the application.
I don't see actively doing this due to the fact it would double the effort, no direct user ask, and  increase risk to forget creating one in the future.


typespec: init at 0.62.0

This PR adds typespec, a compiler with included language server for defining API shapes for REST, OpenAPI, gRPC and others.
We have been using this derivation at work for some time and it worked well.
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[X] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Thanks for your quick review! I implemented your suggestions.

As the root repository has github releases, I believe you could add an update script

Good idea, thanks. I have now added one.

@PauKaifler By the way, it has been a while, and this risks getting lost in the sea of nixpkgs PRs. My suggestion would be to find someone who has merged a similar package into nixpkgs recently, and request a review from them


Emeter UDP packet size

Hi @RalfOGit,
I'm just starting to develop a meter that sends out the information using the SMA protocol, so your library comes really useful. Thank you for your work!
Anyway, I have a real EMETER at hand and I see that the sent packets are 608 bytes in size. But when looking at your code here, I see you are using a payload size of 600 bytes instead. Is that correct?
https://github.com/RalfOGit/sma-emeter-simulator/blob/b77a558aed413f6b966cb6d5eae40302e935892f/src/main.cpp#L55

Hi Gonzalo,Interesting. I modelled the UDP packet to be identical to what my own emeter sends out. Can you send me a wireshark dump of the 608 byte packet? It would be interesting to see what they have changed.Best regards RalfAm 04.05.2023 um 19:18 schrieb Gonzalo Brusco @.***>:
Hi @RalfOGit,
I'm just starting to develop a meter that sends out the information using the SMA protocol, so your library comes really useful. Thank you for your work!
Anyway, I have a real EMETER at hand and I see that the sent packets are 608 bytes in size. But when looking at your code here, I see you are using a payload size of 600 bytes instead. Is that correct?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

Yes sure. Here it is!
The IP of the meter is <IP_ADDRESS>
There's no inverter nor any other SMA device on that network. Just the Emeter.
SMA UDP<PHONE_NUMBER>2.zip

Check this!
https://github.com/kettenbach-it/FHEM-SMA-Speedwire/blob/8e406890be575a245a6908d91008f2b32ccd1820/77_SMAEM.pm#L391

… ok, this explains it. Thanks for the Wireshark dump. There is a new 8-byte field that needs to go behind PowerFactorTotal:
obis = insert(emeter_packet, obis, ObisData::NegativeApparentEnergyTotal,  327.62);

obis = insert(emeter_packet, obis, ObisData::PowerFactorTotal,               0.54);

    0e04000000c39300

Looking at the OBIS definitions and at fields displayed, or better not displayed, by the Energy Meter app for iOS, this is likely a value for the grid frequency. I will need to adapt the code to accommodate for this new field. Give me a bit of time for this change.
Have a nice evening
Ralf

Hi Gonzalo,
I just added obis definitions for frequency measurements to libspeedwire and added it to the emeter-simulator as well. Please update both git repositories and check if this works for you.
I deleted your email with the zip attachment for privacy reasons.
Best regards
Ralf

Thanks @RalfOGit !! That was fast!!
I will check it out. Thanks again


Updated DINOCPU assignment1 instruction page and worksheet.

In this commit, it also updated the ECS 154B TA and OH in the syllabus page.

A couple of small things, but otherwise, it looks good to me.

Thanks! I fixed them and pushed the newer version.


DictIter needs some safety improvements

I think instead of locking length changes we should instead lock all mutations to the iterated dict.

Looking back at this, I think the current limitation of not allowing the length to change should be fine. Removing an adding back an item is likely okay since it won't trigger a reallocation (since in the end the amount of buckets occupied is the same,) though the iterator will not know about the change and may or may not reflect it.


rebar3 releases not working on Mac

I would like to know if releases are supposed to work on Mac?
When I run rebar3 release or rebar3 as prod release I have the error below:
./rebar3 release
===> Verifying dependencies...
===> sh info:
	cwd: "/Users/carlosedp/projects/dcca-server-OTP"
	cmd: git rev-parse -q HEAD

===> 	opts: [{cd,"/Users/carlosedp/projects/dcca-server-OTP/_build/default/lib/lager"}]

===> Port Cmd: git rev-parse -q HEAD
Port Opts: [{cd,"/Users/carlosedp/projects/dcca-server-OTP/_build/default/lib/lager"},
            exit_status,
            {line,16384},
            use_stdio,stderr_to_stdout,hide,eof]

===> Comparing git ref d33ccf3b69de09a628fe38b4d7981bb8671b8a4f with d33ccf3b69de09a628fe38b4d7981bb8671b8a4f
===> sh info:
	cwd: "/Users/carlosedp/projects/dcca-server-OTP"
	cmd: git config --get remote.origin.url

===> 	opts: [{cd,"/Users/carlosedp/projects/dcca-server-OTP/_build/default/lib/lager"}]

===> Port Cmd: git config --get remote.origin.url
Port Opts: [{cd,"/Users/carlosedp/projects/dcca-server-OTP/_build/default/lib/lager"},
            exit_status,
            {line,16384},
            use_stdio,stderr_to_stdout,hide,eof]

===> Comparing git url {"github.com","basho/lager"} with {"github.com",
                                                                 "basho/lager"}
===> sh info:
	cwd: "/Users/carlosedp/projects/dcca-server-OTP"
	cmd: git rev-parse -q HEAD

===> 	opts: [{cd,"/Users/carlosedp/projects/dcca-server-OTP/_build/default/lib/goldrush"}]

===> Port Cmd: git rev-parse -q HEAD
Port Opts: [{cd,"/Users/carlosedp/projects/dcca-server-OTP/_build/default/lib/goldrush"},
            exit_status,
            {line,16384},
            use_stdio,stderr_to_stdout,hide,eof]

===> Comparing git ref 71e63212f12c25827e0c1b4198d37d5d018a7fec with 71e63212f12c25827e0c1b4198d37d5d018a7fec
===> sh info:
	cwd: "/Users/carlosedp/projects/dcca-server-OTP"
	cmd: git config --get remote.origin.url

===> 	opts: [{cd,"/Users/carlosedp/projects/dcca-server-OTP/_build/default/lib/goldrush"}]

===> Port Cmd: git config --get remote.origin.url
Port Opts: [{cd,"/Users/carlosedp/projects/dcca-server-OTP/_build/default/lib/goldrush"},
            exit_status,
            {line,16384},
            use_stdio,stderr_to_stdout,hide,eof]

===> Comparing git url {"github.com","DeadZen/goldrush"} with {"github.com",
                                                                      "DeadZen/goldrush"}
===> sh info:
	cwd: "/Users/carlosedp/projects/dcca-server-OTP"
	cmd: git --git-dir="/Users/carlosedp/projects/dcca-server-OTP/_build/default/lib/goldrush/.git" rev-parse --verify HEAD

===> 	opts: [{use_stdout,false},
                       {debug_abort_on_error,
                           [76,111,99,107,105,110,103,32,111,102,32,103,105,
                            116,32,100,101,112,101,110,100,101,110,99,121,32,
                            102,97,105,108,101,100,32,105,110,32,
                            "/Users/carlosedp/projects/dcca-server-OTP/_build/default/lib/goldrush"]}]

===> Port Cmd: git --git-dir="/Users/carlosedp/projects/dcca-server-OTP/_build/default/lib/goldrush/.git" rev-parse --verify HEAD
Port Opts: [exit_status,{line,16384},use_stdio,stderr_to_stdout,hide,eof]

===> sh info:
	cwd: "/Users/carlosedp/projects/dcca-server-OTP"
	cmd: git --git-dir="/Users/carlosedp/projects/dcca-server-OTP/_build/default/lib/lager/.git" rev-parse --verify HEAD

===> 	opts: [{use_stdout,false},
                       {debug_abort_on_error,
                           [76,111,99,107,105,110,103,32,111,102,32,103,105,
                            116,32,100,101,112,101,110,100,101,110,99,121,32,
                            102,97,105,108,101,100,32,105,110,32,
                            "/Users/carlosedp/projects/dcca-server-OTP/_build/default/lib/lager"]}]

===> Port Cmd: git --git-dir="/Users/carlosedp/projects/dcca-server-OTP/_build/default/lib/lager/.git" rev-parse --verify HEAD
Port Opts: [exit_status,{line,16384},use_stdio,stderr_to_stdout,hide,eof]

===> Compiling diameter files...
===>      Skipped rfc4006_cc_Gy.dia
===> Compiling ocsgateway
===> erl_opts [debug_info,debug_info,
                      {parse_transform,lager_transform},
                      {lager_truncation_size,10485760},
                      {i,"include"}]
===> Files to compile first: []
===> Compiling dccaserver
===> erl_opts [debug_info,debug_info,
                      {parse_transform,lager_transform},
                      {lager_truncation_size,10485760},
                      {i,"include"}]
===> Files to compile first: []
===> Starting relx build process ...
===> Resolving OTP Applications from directories:
          /Users/carlosedp/projects/dcca-server-OTP/_build/default/lib
          /Users/carlosedp/projects/dcca-server-OTP/_build/default/lib/lager/ebin
          /usr/local/Cellar/erlang/17.5/lib/erlang/lib
          /Users/carlosedp/projects/dcca-server-OTP/_build/default/rel
===> Resolved dccaserver-0.1.0
===> Dev mode enabled, release will be symlinked
===> Uncaught error in rebar_core. Run with DEBUG=1 to see stacktrace
===> Uncaught error: {badmatch,false}
===> Stack trace to the error location: [{rlx_util,load_file,3,
                                                 [{file,
                                                   "/Users/carlosedp/projects/rebar3-carlosedp/_build/default/lib/relx/src/rlx_util.erl"},
                                                  {line,168}]},
                                                {rlx_prv_assembler,render,2,
                                                 [{file,
                                                   "/Users/carlosedp/projects/rebar3-carlosedp/_build/default/lib/relx/src/rlx_prv_assembler.erl"},
                                                  {line,602}]},
                                                {rlx_prv_assembler,
                                                 include_nodetool,1,
                                                 [{file,
                                                   "/Users/carlosedp/projects/rebar3-carlosedp/_build/default/lib/relx/src/rlx_prv_assembler.erl"},
                                                  {line,377}]},
                                                {rlx_prv_assembler,
                                                 write_bin_file,4,
                                                 [{file,
                                                   "/Users/carlosedp/projects/rebar3-carlosedp/_build/default/lib/relx/src/rlx_prv_assembler.erl"},
                                                  {line,345}]},
                                                {rlx_prv_assembler,do,1,
                                                 [{file,
                                                   "/Users/carlosedp/projects/rebar3-carlosedp/_build/default/lib/relx/src/rlx_prv_assembler.erl"},
                                                  {line,58}]},
                                                {relx,run_provider,2,
                                                 [{file,
                                                   "/Users/carlosedp/projects/rebar3-carlosedp/_build/default/lib/relx/src/relx.erl"},
                                                  {line,286}]},
                                                {lists,foldl,3,
                                                 [{file,"lists.erl"},
                                                  {line,1261}]},
                                                {relx,run_providers,1,
                                                 [{file,
                                                   "/Users/carlosedp/projects/rebar3-carlosedp/_build/default/lib/relx/src/relx.erl"},
                                                  {line,266}]}]
===> When submitting a bug report, please include the output of `rebar3 report "your command"`

Report:
./rebar3 report release                                     rebar3@9b17dc8 ✗
Rebar3 report
 version 3.0.0-beta-1
 generated at 2015-07-21T00:39:06+00:00
=================
Please submit this along with your issue at https://github.com/rebar/rebar3/issues (and feel free to edit out private information, if any)
-----------------
Task: release
Entered as:
  release
-----------------
Operating System: x86_64-apple-darwin13.4.0
ERTS: Erlang/OTP 17 [erts-6.4] [source] [64-bit] [smp:4:4] [async-threads:0] [hipe] [kernel-poll:false] [dtrace]
Root Directory: /usr/local/Cellar/erlang/17.5/lib/erlang
Library directory: /usr/local/Cellar/erlang/17.5/lib/erlang/lib
-----------------
Loaded Applications:
bbmustache: 1.0.3
common_test: 1.10
compiler: 5.0.4
crypto: 3.5
erlware_commons: 0.13.0
eunit: 2.2.9
inets: 5.10.6
kernel: 3.2
providers: 1.4.1
relx: 3.3.0
sasl: 2.4.1
ssl_verify_hostname: 1.0.5
stdlib: 2.4
syntax_tools: 1.6.18
tools: 2.7.2

-----------------
Escript path: /Users/carlosedp/projects/dcca-server-OTP/rebar3
Providers:
  app_discovery as clean clean compile compile cover ct deps dialyzer do edoc escriptize eunit help install_deps list lock new pkgs release relup report shell tar unlock update upgrade upgrade version xref

Hm, that error message seems to be saying it can't get nodetool out of the escript, which would mean relx isn't properly bundled in rebar3.
Did you build rebar3 yourself from the beta-1 tag or download a prebuilt escript?

Same problem with prebuilt downloaded from https://s3.amazonaws.com/rebar3/rebar3 and the one I built myself.

Maybe this is related to the bug in my Diameter plugin. Will check later.

Actually the release generation worked fine but console does not load app:
~/projects/dcca-server-OTP
☹  ./_build/prod/rel/dccaserver/bin/dccaserver console           rebar3@a688ecc

Crash dump was written to: erl_crash.dump
Kernel pid terminated (application_controller) ({application_start_failure,kernel,{{shutdown,{failed_to_start_child,net_sup,{shutdown,{failed_to_start_child,net_kernel,{'EXIT',nodistribution}}}}},{k
Exec: /Users/carlosedp/projects/dcca-server-OTP/_build/prod/rel/dccaserver/erts-6.4/bin/erlexec -boot /Users/carlosedp/projects/dcca-server-OTP/_build/prod/rel/dccaserver/releases/0.1.0/dccaserver -boot_var ERTS_LIB_DIR /Users/carlosedp/projects/dcca-server-OTP/_build/prod/rel/dccaserver/erts-6.4/../lib -config /Users/carlosedp/projects/dcca-server-OTP/_build/prod/rel/dccaserver/releases/0.1.0/sys.config -args_file /Users/carlosedp/projects/dcca-server-OTP/_build/prod/rel/dccaserver/releases/0.1.0/vm.args -- console
Root: /Users/carlosedp/projects/dcca-server-OTP/_build/prod/rel/dccaserver
/Users/carlosedp/projects/dcca-server-OTP/_build/prod/rel/dccaserver
{error_logger,{{2015,7,22},{22,47,24}},"Can't set long node name!\nPlease check your configuration\n",[]}
{error_logger,{{2015,7,22},{22,47,24}},crash_report,[[{initial_call,{net_kernel,init,['Argument__1']}},{pid,<0.20.0>},{registered_name,[]},{error_info,{exit,{error,badarg},[{gen_server,init_it,6,[{file,"gen_server.erl"},{line,322}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,237}]}]}},{ancestors,[net_sup,kernel_sup,<0.10.0>]},{messages,[]},{links,[<0.17.0>]},{dictionary,[{longnames,true}]},{trap_exit,true},{status,running},{heap_size,2586},{stack_size,27},{reductions,795}],[]]}
{error_logger,{{2015,7,22},{22,47,24}},supervisor_report,[{supervisor,{local,net_sup}},{errorContext,start_error},{reason,{'EXIT',nodistribution}},{offender,[{pid,undefined},{name,net_kernel},{mfargs,{net_kernel,start_link,[['dccaserver-OTP',longnames]]}},{restart_type,permanent},{shutdown,2000},{child_type,worker}]}]}
{error_logger,{{2015,7,22},{22,47,24}},supervisor_report,[{supervisor,{local,kernel_sup}},{errorContext,start_error},{reason,{shutdown,{failed_to_start_child,net_kernel,{'EXIT',nodistribution}}}},{offender,[{pid,undefined},{name,net_sup},{mfargs,{erl_distribution,start_link,[]}},{restart_type,permanent},{shutdown,infinity},{child_type,supervisor}]}]}
{error_logger,{{2015,7,22},{22,47,24}},crash_report,[[{initial_call,{application_master,init,['Argument__1','Argument__2','Argument__3','Argument__4']}},{pid,<0.9.0>},{registered_name,[]},{error_info,{exit,{{shutdown,{failed_to_start_child,net_sup,{shutdown,{failed_to_start_child,net_kernel,{'EXIT',nodistribution}}}}},{kernel,start,[normal,[]]}},[{application_master,init,4,[{file,"application_master.erl"},{line,133}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,237}]}]}},{ancestors,[<0.8.0>]},{messages,[{'EXIT',<0.10.0>,normal}]},{links,[<0.8.0>,<0.7.0>]},{dictionary,[]},{trap_exit,true},{status,running},{heap_size,376},{stack_size,27},{reductions,117}],[]]}
{error_logger,{{2015,7,22},{22,47,24}},std_info,[{application,kernel},{exited,{{shutdown,{failed_to_start_child,net_sup,{shutdown,{failed_to_start_child,net_kernel,{'EXIT',nodistribution}}}}},{kernel,start,[normal,[]]}}},{type,permanent}]}
{"Kernel pid terminated",application_controller,"{application_start_failure,kernel,{{shutdown,{failed_to_start_child,net_sup,{shutdown,{failed_to_start_child,net_kernel,{'EXIT',nodistribution}}}}},{kernel,start,[normal,[]]}}}"}

Crash dump was written to: erl_crash.dump
Kernel pid terminated (application_controller) ({application_start_failure,kernel,{{shutdown,{failed_to_start_child,net_sup,{shutdown,{failed_to_start_child,net_kernel,{'EXIT',nodistribution}}}}},{k

That is an issue with your host. You can make a vm.args with -sname instead of -name or provide a FQDN in your hosts.

Replacing -name to -sname fixed it. My bad!
Thanks Tristan.


[KAFKA-6265] GlobalKTable missing #queryableStoreName()

@mjsax @guozhangwang  Moving PR from PR #4334  to here.

Ack. Please close the other PR.
Retest this please.

Ok, I closed the one. Thanks for your patience. :)

The Jenkins failure seems not relevant. The Patch LGTM.
Will wait for the KIP to be accepted.


Doing CI on Mac too

Changes:

Skipping tests when lrelease is not found
Fixing using gettext installed from homebrew
Use invoke instead of Makefile

Plus other minor changes

doing this on Aldebaran official repo instead


Build failed

Description
FAILURE: Build failed with an exception.

Where:
Settings file 'D:\Mobile_App_Devlopment\LetestMobileApp\demo\android\settings.gradle' line: 2

What went wrong:
Error resolving plugin [id: 'com.facebook.react.settings']

java.io.UncheckedIOException: Could not move temporary workspace (D:\Mobile_App_Devlopment\LetestMobileApp\demo\android.gradle\8.10.2\dependencies-accessors\569c8b261a8a714d7731d5f568e0e5c05babae10-5dd2a0af-cc67-4253-ad4c-ccfe5db8d92b) to immutable location (D:\Mobile_App_Devlopment\LetestMobileApp\demo\android.gradle\8.10.2\dependencies-accessors\569c8b261a8a714d7731d5f568e0e5c05babae10)

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
Get more help at https://help.gradle.org.

BUILD FAILED in 10s
info Run CLI with --verbose flag for more details.
Steps to reproduce
FAILURE: Build failed with an exception.

Where:
Settings file 'D:\Mobile_App_Devlopment\LetestMobileApp\demo\android\settings.gradle' line: 2

What went wrong:
Error resolving plugin [id: 'com.facebook.react.settings']

java.io.UncheckedIOException: Could not move temporary workspace (D:\Mobile_App_Devlopment\LetestMobileApp\demo\android.gradle\8.10.2\dependencies-accessors\569c8b261a8a714d7731d5f568e0e5c05babae10-5dd2a0af-cc67-4253-ad4c-ccfe5db8d92b) to immutable location (D:\Mobile_App_Devlopment\LetestMobileApp\demo\android.gradle\8.10.2\dependencies-accessors\569c8b261a8a714d7731d5f568e0e5c05babae10)

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
Get more help at https://help.gradle.org.

BUILD FAILED in 10s
info Run CLI with --verbose flag for more details.
React Native Version
0.76.2
Affected Platforms
Runtime - Android
Output of npx react-native info
Windows 11
8GB RAM, 512 GB SAD
AND RISEN 5
PLEASE SOLVE THE PROBLEM

Stacktrace or Logs
FAILURE: Build failed with an exception.

* Where:
Settings file 'D:\Mobile_App_Devlopment\LetestMobileApp\demo\android\settings.gradle' line: 2

* What went wrong:
Error resolving plugin [id: 'com.facebook.react.settings']
> java.io.UncheckedIOException: Could not move temporary workspace (D:\Mobile_App_Devlopment\LetestMobileApp\demo\android\.gradle\8.10.2\dependencies-accessors\569c8b261a8a714d7731d5f568e0e5c05babae10-5dd2a0af-cc67-4253-ad4c-ccfe5db8d92b) to immutable location (D:\Mobile_App_Devlopment\LetestMobileApp\demo\android\.gradle\8.10.2\dependencies-accessors\569c8b261a8a714d7731d5f568e0e5c05babae10)

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.

BUILD FAILED in 10s
info Run CLI with --verbose flag for more details.

Reproducer
expo/expo-template-default
Screenshots and Videos

Try cd android
./gradlew clean
And npx react-native run android or npm start

I have the same problem on all my projects, on 2 different computers, with different versions of Gradle (8.11.1, 8.11, 8.10.2), on projects that were working before without me touching anything. And on WSL it works fine for the same projects, so I think this problem is Windows 11 related. I only have it on Kotlin projects and not on Java projects also, so maybe it's related to the kotlin plugin.
❯ gradle --version

------------------------------------------------------------
Gradle 8.11.1
------------------------------------------------------------

Build time:    2024-11-20 16:56:46 UTC
Revision:      481cb05a490e0ef9f8620f7873b83bd8a72e7c39

Kotlin:        2.0.20
Groovy:        3.0.22
Ant:           Apache Ant(TM) version 1.10.14 compiled on August 16 2023
Launcher JVM:  21.0.5 (Eclipse Adoptium 21.0.5+11-LTS)
Daemon JVM:    C:\Users\marc\scoop\apps\temurin21-jdk\current (no JDK specified, using current Java home)
OS:            Windows 11 10.0 amd64

❯ gradle init --type kotlin-library --dsl kotlin --project-name test-project --java-version 21

Select test framework:
  1: kotlin.test
  2: JUnit Jupiter
Enter selection (default: kotlin.test) [1..2] 1

Generate build using new APIs and behavior (some features may change in the next minor release)? (default: no) [yes, no] no

> Task :init
Learn more about Gradle by exploring our Samples at https://docs.gradle.org/8.11.1/samples/sample_building_kotlin_libraries.html

BUILD SUCCESSFUL in 7s
1 actionable task: 1 executed

./gradlew clean --debug --stacktrace generates this output:
output-log.txt

For me this worked:
In gradle-wrapper.properties
change:
distributionUrl=https\://services.gradle.org/distributions/gradle-8.10.2-all.zip
to
distributionUrl=https\://services.gradle.org/distributions/gradle-8.11.1-bin.zip
then clean gradle by performing
cd android ./gradlew clean

In gradle-wrapper.properties change: distributionUrl=https://services.gradle.org/distributions/gradle-8.10.2-all.zip to distributionUrl=https://services.gradle.org/distributions/gradle-8.11.1-bin.zip
then clean gradle by performing cd android  ./gradlew clean
I have also tried it, and the result is correct on a Windows computer


fix: Support python 3.6

Summary of Changes
Modify workflow to support 3.6.
It works just fine with 3.6!
Fix some details from setup.py while I'm at it, and add types for the conftest file.
CheckList
Make sure you have checked all steps below to ensure a timely review.

[x] PR title addresses the issue accurately and concisely. Example: "Updates the version of Flask to v1.0.2"

In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

[x] PR includes a summary of changes.

Thanks for doing this! I wonder if it makes sense to write a short comment about the 3.6/3.7 divide in the README (but I think it shouldn't really impact people unless they use that one bit of code)

Yeah, I need to write a comment about --roundtrip for pytest also, I'll do that in a subsequent PR.


20180723test

test差分

@RishuSuzuki Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@RishuSuzuki please use your own fork to test Github's features.

sorry


Full FSI support on .NET Core 2.0

From #2400

Properly handle the model for how .dlls are laid out on disk with .NET Core, thus fixing #r
Establish a good working model for how to do the above
Prompt to re-load an FSI session when #r’ing an assembly that targets a higher target than what FSI was launched with?
Error message asking user to re-load FSI manually?
Try to re-target and re-reference everything on the fly?

@dbettin it's like you are channeling my nightmares today.  Assembly reference and loading in a coreclr world requires a lot of thought too.  FSI was and to a lesser extent the desktop FSC were very helpful in finding and resolving assemblies ... at the price of a lot of determinism.
It's a goal we need to fix by the time .NetStandard 2.0 is released.  The details however, are not yet available.

My comment from the fsharp-opensource mailing list:

There’s been progress – we’ve had variations on this working – but there’s a strong feeling that we need to get “#r on a nuget package” designed, implemented and finalized before the experience will be correct and stable for both .NET Core and .NET Framework. See also https://github.com/Microsoft/visualfsharp/pull/2483

Support for FSI on dotnet core.
Yes it will happen absolutely.  That it hasn't yet, is extremely embarrassing to me.  The reason is technical, rather than priorities or anything else.  Well priorities have been impactful ... but they are not the main reason.
The issue is this: we test fsi.exe on coreclr and have done for a long ... long time, and it works well.  Unfortunately ... (and this is the embarrassing bit) it relies on a bug in the coreclr to work ... in AssemblyLoadContext.  If we fix the code to what we need it to be now that the bug is fixed in the coreclr, the entire way we test the coreclr build needs changing.  This is the exact same reason why we still rely on project.json in our build.
I fully understand the irony of what I just said above ... if we fix the bug we can't test it ... if we don't fix the bug we can't ship it.  I hate myself for this ... and if you want to expose me to the universe for the full idiocy of the position I just expressed I know how insane it is.
We must fix our build ... we must fix the testing ... I promise it will happen ...
I actually prefer Don's explanation, because coreclr FSI without built-in package management is definitely going to require external packagement to make scripts that reference libraries reliable.
However, in reality releasing fsi is not gated on adding packagemanagement it is gated on us digging out of a historic build/test mess that I created for us.
I am truly sorry about that.
Kevin

What annoys me personally is that we bundle both things. We could already
have a nice package management story in classic fsi and could make HUGE
progress on FAKE 5. But we wait for netcore....
Am 01.09.2017 9:52 nachm. schrieb "Kevin Ransom (msft)" <
<EMAIL_ADDRESS>
Support for FSI on dotnet core.
Yes it will happen absolutely. That it hasn't yet, is extremely
embarrassing to me. The reason is technical, rather than priorities or
anything else. Well priorities have been impactful ... but they are not the
main reason.
The issue is this: we test fsi.exe on coreclr and have done for a long ...
long time, and it works well. Unfortunately ... (and this is the
embarrassing bit) it relies on a bug in the coreclr to work ... in
AssemblyLoadContext. If we fix the code to what we need it to be now that
the bug is fixed in the coreclr, the entire way we test the coreclr build
needs changing. This is the exact same reason why we still rely on
project.json in our build.
I fully understand the irony of what I just said above ... if we fix the
bug we can't test it ... if we don't fix the bug we can't ship it. I hate
myself for this ... and if you want to expose me to the universe for the
full idiocy of the position I just expressed I know how insane it is.
We must fix our build ... we must fix the testing ... I promise it will
happen ...
I actually prefer Don's explanation, because coreclr FSI without built-in
package management is definitely going to require external packagement to
make scripts that reference libraries reliable.
However, in reality releasing fsi is not gated on adding packagemanagement
it is gated on us digging out of a historic build/test mess that I created
for us.
I am truly sorry about that.
Kevin
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/visualfsharp/issues/2407#issuecomment-326670006,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADgNE-0l8H-ykoQUvECZk7xge5hYyzaks5seGCagaJpZM4L90AM
.

I haven’t bundled both things.  I’m saying, and I think quite clearly, that my stupidity on the build and test is what is blocking this.  Fixing the build and test will enable FSI.  Good Package management in FSI will make the world pretty groovy.
Kevin
From: Steffen Forkmann<EMAIL_ADDRESS>Sent: Friday, September 1, 2017 1:12 PM
To: Microsoft/visualfsharp<EMAIL_ADDRESS>Cc: Kevin Ransom<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [Microsoft/visualfsharp] Full FSI support on .NET Core 2.0 (#2407)
What annoys me personally is that we bundle both things. We could already
have a nice package management story in classic fsi and could make HUGE
progress on FAKE 5. But we wait for netcore....
Am 01.09.2017 9:52 nachm. schrieb "Kevin Ransom (msft)" <
notifications<EMAIL_ADDRESS>
Support for FSI on dotnet core.
Yes it will happen absolutely. That it hasn't yet, is extremely
embarrassing to me. The reason is technical, rather than priorities or
anything else. Well priorities have been impactful ... but they are not the
main reason.
The issue is this: we test fsi.exe on coreclr and have done for a long ...
long time, and it works well. Unfortunately ... (and this is the
embarrassing bit) it relies on a bug in the coreclr to work ... in
AssemblyLoadContext. If we fix the code to what we need it to be now that
the bug is fixed in the coreclr, the entire way we test the coreclr build
needs changing. This is the exact same reason why we still rely on
project.json in our build.
I fully understand the irony of what I just said above ... if we fix the
bug we can't test it ... if we don't fix the bug we can't ship it. I hate
myself for this ... and if you want to expose me to the universe for the
full idiocy of the position I just expressed I know how insane it is.
We must fix our build ... we must fix the testing ... I promise it will
happen ...
I actually prefer Don's explanation, because coreclr FSI without built-in
package management is definitely going to require external packagement to
make scripts that reference libraries reliable.
However, in reality releasing fsi is not gated on adding packagemanagement
it is gated on us digging out of a historic build/test mess that I created
for us.
I am truly sorry about that.
Kevin
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/visualfsharp/issues/2407#issuecomment-326670006,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADgNE-0l8H-ykoQUvECZk7xge5hYyzaks5seGCagaJpZM4L90AM
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fvisualfsharp%2Fissues%2F2407%23issuecomment-326673639&data=02|01|Kevin.Ransom%40microsoft.com|5e2c6ce2b80b41cb984a08d4f175b2ae|72f988bf86f141af91ab2d7cd011db47|1|0|636398935195282907&sdata=SNpGUyHFQz%2BBSAhxipCCQqQRSL8SXUhfl4UKhHx12XA%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAE76FuyHmcWtZ2MCqjmZDKG8MPUuGThUks5seGUMgaJpZM4L90AM&data=02|01|Kevin.Ransom%40microsoft.com|5e2c6ce2b80b41cb984a08d4f175b2ae|72f988bf86f141af91ab2d7cd011db47|1|0|636398935195282907&sdata=f0BqOkTwlXSypXMzk0tMdRWlpd2AiNgYVHAx7Tdu9fk%3D&reserved=0.

@KevinRansom I just really wanted to write that I appreciate and value your response. While I can see that this is embarrassing it feels like honesty is really a good way forward for this repository.
Too often (and maybe even only for historical reasons) we feel like there is some hidden agenda or political reasons behind stuff. So this really helps a lot. Thank you.
About what @forki said: I think a response on the other issue regarding the latest suggestions from the community might help.

Unfortunately .it relies on a bug in the coreclr to work ... in AssemblyLoadContext.

I wasn't aware of this.  Do you have a link to the bug for this?  Thanks. Also a link to the place in the F# code where we are relying on this. Full transparency please :)

The bug is in how you implement load contexts.  What we do in FSI results in a stack overflow on bug fixed coreclr’s.
The fix looks like this:  https://github.com/Microsoft/visualfsharp/pull/3140/files#diff-3229c72e3fbd323c1dde9692aceedd65L322
It was part of PR to basically enable FSI on netstandard 2.0.   However, work you and I have done superseded this PR, apart from this little bit.
From: Don Syme<EMAIL_ADDRESS>Sent: Friday, September 1, 2017 3:44 PM
To: Microsoft/visualfsharp<EMAIL_ADDRESS>Cc: Kevin Ransom<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [Microsoft/visualfsharp] Full FSI support on .NET Core 2.0 (#2407)
Unfortunately .it relies on a bug in the coreclr to work ... in AssemblyLoadContext.
I wasn't aware of this. Do you have a link to the bug for this? Thanks. Also a link to the place in the F# code where we are relying on this. Full transparency please :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fvisualfsharp%2Fissues%2F2407%23issuecomment-326698915&data=02|01|Kevin.Ransom%40microsoft.com|409fc2c1ae3c4b8ce6dd08d4f18af9be|72f988bf86f141af91ab2d7cd011db47|1|0|636399026578283951&sdata=BG0m8myP8fNVRn7bTt04u%2FqEsd0mbn5Nob%2BhYBo0Bbs%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAE76FiF0wKQRdpvRfhPrfOhyzaG4PtVZks5seIi-gaJpZM4L90AM&data=02|01|Kevin.Ransom%40microsoft.com|409fc2c1ae3c4b8ce6dd08d4f18af9be|72f988bf86f141af91ab2d7cd011db47|1|0|636399026578283951&sdata=uF1vQUhBQNd9z4FisR55%2F%2BfRFaud1kya6LgoDjTrTUk%3D&reserved=0.

Just to add: The runtime people suggested to me to use my own assembly load context (as I was hitting some similar issues with FAKE at the time), since I have done that the code and the loading logic feel a lot "cleaner".
Technically, this also fixes a lot of outstanding problems in FAKE like that you cannot use a different fcs version in your script code (for example when using fsf).
So maybe this should be something to consider. But yeah especially for fcs this might be breaking as existing users might depend on having the same set of assemblies available in the script code as in the host code.

Is there any progress regarding this issue?

@halcwb Not at the moment, no. We've been occupied primarily with some critical issues in existing workflows for .NET Core and IDE support. Hoping to pick up the in progress work on this soon.

fsi.exe that comes with SDK 2.1.302(.dotnet/sdk/2.1.302/FSharp/fsi.exe) works, you get missing reference exceptions sometimes (e.g. System.IO.File), but it takes all of 1 minute to work around it:
Create a F# project and add the functions you want, e.g. let read = System.IO.File.ReadAllBytes, then compile this project, and #r the resulting DLL in fsi.exe
As a nice plus, it works well with VsCode, including colours. There are some readline warts, but its still worlds better than mono fsharpi

@abk-x How you managed to run it please?
Cannot get neither .dotnet/sdk/2.1.302/FSharp/fsi.exe nor .dotnet/sdk/2.1.400/FSharp/fsi.exe working on Win10 x64

You can use --readline+
dotnet /usr/local/share/dotnet/sdk/2.1.302/FSharp/fsi.exe --readline+

@zpodlovics

Strange - it seems ok on OSX

@zpodlovics - I see what you mean now, there is definitely something wrong with readline when used from dotnet

The callgraph looks horrible:
https://gist.github.com/zpodlovics/68eab3f5188313e33c665ed1a9af4c09

I have managed to get a source build of fsi.exe (using the tricks from https://github.com/Microsoft/visualfsharp/issues/5636) and created a quick callgraph profiling (using --readline+ option). The first 4/5 of the callgraph is F# startup, the more interesting parts is on the remaining 1/5.
On backspace the writeChar / render loop looks really weird as it use some deeply nested read/change call chain.
The svg callgraph are available here (download it if you want zoomable interface):
https://gist.github.com/zpodlovics/28c61d357b054bd4659cd5b8bd7294d3

A typical callstack looks like this from the callgraph:

The text profile are available for speedscope (https://github.com/jlfwong/speedscope or online https://www.speedscope.app/):
https://gist.github.com/zpodlovics/d0ac67c47680df1e68c0704e918c2b16

@zpodlovics from the code https://github.com/Microsoft/visualfsharp/blob/master/src/fsharp/fsi/console.fs#L381-L470
it's look that something with the tail call is not working
did you profiled the fsi.exe from the Debug or Release directory?

@AviAvni I have tried out originally with the SDK packaged fsi.exe which is a release build (and unusable when readline enabled), but I was not able to resolve the managed symbols in the profile. It was probably the release build, I will create an another profile later. Checked now, the source build release version is still unusable with readline enabled.

@zpodlovics the problem with --readline+ is also happen in the .net framework fsi on windows

Is there a rough view on the ETA for this support ?
Am I correct that we missed (aka were thrown off) the v2 Azure Functions boat already? - Azure/azure-functions-host#3414

We have the necessary infrastructure built in and a first run at a NuGet plugin built. @KevinRansom can share more details, but I would expect this to land in a .NET Core SDK update before a Visual Studio update.

(Note: syntax of #r is not finalized; this is just so there is a straightforward parser)

Any news on this front? 😨

Closing this as it's now in preview: https://devblogs.microsoft.com/dotnet/announcing-net-core-3-preview-3/
dotnet fsi --readline is what you can use now.


Enhancement: Add leading zero for file navigation Issue #440

Modified show.ts so files are named with leading zeros so they're in order in windows file navigation.
Works while there are less than 10,000 problems
#440

Thanks @aebopp,
I think we need a setting to turn on/off this feature.

@aebopp Do you still have the interest to update the PR?

Hi!
I’m not exactly sure how to add settings, so I guess not.
Thanks for checking in :)
On Thu, Jul 23, 2020 at 4:21 AM Sheng Chen<EMAIL_ADDRESS>wrote:

@aebopp https://github.com/aebopp Do you still have the interest to
update the PR?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/LeetCode-OpenSource/vscode-leetcode/pull/582#issuecomment-662879985,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFQ3PLTHW3XCJFEEL5FIFTTR47XG3ANCNFSM4OH73KGA
.

--
Alexandria Bopp
University of Michigan | Class of 2020
B.S. English, Industrial and Operations Engineering
<EMAIL_ADDRESS>|<PHONE_NUMBER>

Instead of hard code the prefix zeros, it will be better to let the user customize it. For example, in the setting leetcode.filePath, we can support something like ${id%05d} in the filename. This will provide enough flexibility to the users.


Merge multiple PDFDocuments

As mentioned in #66 the ability of merging two PDFDocuments into one resulting PDF file should be considered.
Multiple documents get calculated. Then during the render process, all calculated objects are in one list which will then be rendered into a single file.
Known issues:

Pagination will not work → should not work in some cases?
How to implement a generic solution?

Is this still being considered? I am currently using a workaround to convert pdf pages from other documents into uiimages, and then compiling them into the tppdf. I can get it to work in the simulator, but on the iPhone 8 the app crashes due to memory limitations.

Even tough this issue is over a year old, I will reconsider it now, due to personal needs.
For now I'll take the approach simply combining the calculated pages and render it in a single run through, using something like:
try PDFGenerator.generateURL(documents: [
    document1,
    document2
], filename: "ChatBook.pdf", progress: { value in
    print(value)
})

WIP on feature/multi-docs

Released in 1.5.1


[Windows] support win7

What OS are you using (uname -a, or Windows version)?
windows
What programming language are you using (C/C++/Go/Rust)?
c++
What did you expect to see and what you saw instead?
I'm using vs2013 and win7, so I couldn't compile it at all, but the Edge/Chromium browser itself support win7, so I comment all code relate to edge_html, it finally get work on win7! So I think could you add a macro to disable  edge_html  as an option?

maybe you could submit a PR for it.

maybe you could submit a PR for it.

I believe this is actually resolved with the new DLLs. @lynnux - can you confirm that you are still having a problem?

I believe this is actually resolved with the new DLLs. @lynnux - can you confirm that you are still having a problem?

The DLL should be compatible with WIN7, but the source code are not.  I've alreayd ported a CEF version of rust binding https://github.com/lynnux/webview_rust, so close this now

The DLL should be compatible with WIN7, but the source code are not.  I've alreayd ported a CEF version of rust binding https://github.com/lynnux/webview_rust, so close this now

what do you think @wusyong - is this an approach we could adopt?

what do you think @wusyong - is this an approach we could adopt?

@nothingismagick do you mean CEF port? I don't think so, because CEF API are very unstable, it changed very often, I used a very old version which even support windows XP.

@nothingismagick do you mean CEF port? I don't think so, because CEF API are very unstable, it changed very often, I used a very old version which even support windows XP.

Well, I am just thinking about at least documenting your process - because there are probably others who will be in a similar situation where they have to support out of date Microsoft Windows versions.

Well, I am just thinking about at least documenting your process - because there are probably others who will be in a similar situation where they have to support out of date Microsoft Windows versions.


[MX-360] Change email address

Issue
https://artsyproduct.atlassian.net/browse/MX-360

Fails

:no_entry_sign:
Missing Test Files:

src/lib/Components/Modals/__tests__/LoadingModal-tests.tsx

If these files are supposed to not exist, please update your PR body to include "#skip_new_tests".

  Generated by :no_entry_sign: dangerJS


Error: failed to select a version for the requirement salvo-cors = "^0.73.0"

Describe the bug
Can't use "cors" feature with 0.73.0 version cause of:
error: failed to select a version for the requirement `salvo-cors = "^0.73.0"`
candidate versions found which didn't match: 0.72.0, 0.71.1, 0.71.0, ...
location searched: crates.io index
required by package `salvo v0.73.0`
    ... which satisfies dependency `salvo = "^0.73"` (locked to 0.73.0)...

Is it because you are not using the official source and are not synchronized?
This version is in the official source.
https://crates.io/crates/salvo-cors

I use only salvo with its feature.
What should I check to say clearly that I use the official source? I have this line in Cargo.toml:
salvo = { version = "0.73", features = [...] }

I'll try delete Cargo.lock

Check your cargo system config file, if you are using windows, it's path is C:/Users/name/.cargo/config.toml.

I'll try to delete Cargo.lock

This helps.


Add display formatting for number renderer

When the px-data-grid-number-renderer is used for a column the
developer can pass new rendererConfig options, including
rendererConfig.displayFormat, which should be set to a valid
numbro.js string used to format the number before it is displayed.
Additional renderer options are exposed to customize how numbro.js
formats the value. See the px-data-grid-number-renderer.html file
for a full list.
Throws an error when given a value that cannot be parsed
to a number, but recovers and renders the value anyway.
Adds new renderer tests to cover these cases.

See examples/renderer-number-config.html for a demo.
Supersedes #707. Final fixes for #624.

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


KittiSeg_pretrained.zip

Hello! The KittiSeg_pretrained model in the code has failed. Can you give me some information<EMAIL_ADDRESS>thank you very much!

Hello! The KittiSeg_pretrained model in the code has failed. Can you give me some information<EMAIL_ADDRESS>thank you very much!


Avoid missing docs warning on pub extern crate

Due to https://github.com/rust-lang/rust/issues/112308, the public re-export of the pac will trigger a missing docs warning in rust 1.71.0.
This is bogus, as the doc string would not be shown in the rendered docs anyway. However, the warning would be annoying, so add a short doc string to the item.

Does the issue arise if we use edition 2021's pub use rp2040_pac as pac; ?

It doesn't seem so, but it leads to lots of other errors:
    Checking rp2040-hal v0.9.0-alpha.1 (/home/jan/rp2040/rp-rs/rp-hal/rp2040-hal)
error[E0433]: failed to resolve: use of undeclared crate or module `pac`
 --> rp2040-hal/src/i2c/controller.rs:6:5
  |
6 | use pac::{i2c0::RegisterBlock as Block, RESETS};
  |     ^^^ use of undeclared crate or module `pac`

error[E0433]: failed to resolve: use of undeclared crate or module `pac`
 --> rp2040-hal/src/pwm/reg.rs:2:5
  |
2 | use pac::pwm::CH;
  |     ^^^ use of undeclared crate or module `pac`

[...]
error: could not compile `rp2040-hal` (lib) due to 255 previous errors; 4 warnings emitted

Probably all fixable by adjusting those use statements, but is it worth the effort?

Since our MSRV has edition 2021 support anyway, do we have any benefits from sticking with 2018?

I don't think so. It's probably just that nobody did the conversion, because it doesn't give us significant benefits either.
Maybe https://doc.rust-lang.org/stable/edition-guide/rust-2021/panic-macro-consistency.html could add some additional overhead because panic! now always involves string formatting. But my gut feeling is that, as we already have panic statements which use string formatting, the overhead will be very small, if any.


consumer_group newSession() infinite loop

https://github.com/IBM/sarama/blob/9e759865b0d47cd5598befc103c0c40b45784d3c/consumer_group.go#L311
If the error is ErrUnknownMemberId and context gets cancelled by some other go-routine, the above code can go in an infinite loop.
Need a check to cross-check if context is cancelled before below switch:
https://github.com/IBM/sarama/blob/9e759865b0d47cd5598befc103c0c40b45784d3c/consumer_group.go#L305
Example code required:
	select { 	case <-ctx.Done(): 		return nil, ctx.Err() 	default: 	}

Thanks, this is a general bug that the newSession and retryNewSession funcs should both be checking for ctx cancellation to exit early before proceeding


[FEATURE] Add keyvalue-messaging example to the example-components workflow

Affected project(s)

[ ] documentation
[X] examples
[ ] wasmCloud host
[ ] wasmCloud CLI (wash)
[ ] wasmCloud dashboard UI (washboard)
[ ] capability providers
[ ] provider bindgen
[ ] control interface client
[ ] other / not sure

Is your feature request related to a problem? Please describe.
I noticed that I had forgotten to add the keyvalue-messaging example to the example-components.yml workflow, when I submitted PR #2217.
Describe the solution you'd like
I have a new PR to remediate this omission; so, this issue is for tracking purposes only.
Describe alternatives you've considered
No response
Additional context
No response

Hey @ossfellow this was resolved by #2560 right? If not, please let me know and we can re-open!


modify generalCategory key name  (generalCAtegory -> generalCategory)

"Smileys & People"  has a wrong category key (generalCAtegory)

Thank you for the correction!

Thanks for the correction!


Doesn't compile

Building the project with cmake doesnt work.
I get the following error:
[ 74%] Building CXX object examples/CMakeFiles/vivid_examples_advanced.dir/advanced.cpp.o
In file included from /usr/include/oneapi/tbb/detail/_small_object_pool.h:23,
                 from /usr/include/oneapi/tbb/detail/_task.h:23,
                 from /usr/include/oneapi/tbb/parallel_for.h:23,
                 from /usr/include/tbb/parallel_for.h:17,
                 from /usr/include/c++/11/pstl/parallel_backend_tbb.h:20,
                 from /usr/include/c++/11/pstl/parallel_backend.h:20,
                 from /usr/include/c++/11/pstl/algorithm_impl.h:22,
                 from /usr/include/c++/11/pstl/glue_execution_defs.h:50,
                 from /usr/include/c++/11/execution:32,
                 from /home/aether/Desktop/programs/vivid/examples/advanced.cpp:14:
/usr/include/oneapi/tbb/profiling.h:229:15: error: expected unqualified-id before ‘)’ token
  229 |     void emit() { }
      |               ^
/usr/include/oneapi/tbb/profiling.h:231:22: error: expected unqualified-id before ‘const’
  231 |     static void emit(const std::string &) { }
      |                      ^~~~~
/usr/include/oneapi/tbb/profiling.h:231:22: error: expected ‘)’ before ‘const’
  231 |     static void emit(const std::string &) { }
      |                     ~^~~~~
      |                      )
gmake[2]: *** [examples/CMakeFiles/vivid_examples_advanced.dir/build.make:76: examples/CMakeFiles/vivid_examples_advanced.dir/advanced.cpp.o] Error 1
gmake[1]: *** [CMakeFiles/Makefile2:268: examples/CMakeFiles/vivid_examples_advanced.dir/all] Error 2
gmake: *** [Makefile:136: all] Error 2

I am on Ubuntu 22.04

Tests don't compile either. It compiles when I exclude examples and tests though

I tried this on my Desktop Computer, my laptop and my Raspberry Pi, same error occurs every time

Interesting, not sure what exactly causes it, but could be related to either a compiler missmatch with your Qt-version, or some other dev-chain problem, given that the error propagates up from <execution>.
You can try to compile with c++17 or later, and with Qt5.12 or later.
To be fair, I never tried compiling the tests/examples under Ubuntu. Let me know how it goes!

I have gcc 11.3.0, so C++17 is supported. I also have QT 6.3.0 installed.
The library itself works though, and that's all I need... the basic examples work and I don't really need the tests, so I think I'm good


Refactoring proxy forward

This PR refactors proxy forward definitions. Previously was a proxy forward made to a method within a given service. This PR proposes to create a proxy forward to a service instead.
proxy "todo" {
	call "query" {
		request "proto.Todo" "User" {
		}
	}

	forward "proto.Forward" {
	}
}

Blocked by #47


[Help needed] Font size

Environment

Tech
Version

material-ui-pickers
^1.0.0-rc.2

material-ui
^1.0.0-beta.36

React
^16.2.0

Hi, I'm having issue with font size for both the text in DateTimePicker & Input. Both of the font size are too small and I'm unable to find a way to adjust them (show in photo below).
Font size for text in calendar is too small

Font size for value is too small

I understand that they are labelClassName and helperTextClassName but I can't seem to change the style for text in calendar and input value. Any feedback or advice is highly appreciated! Thanks in advance :D

@darylong Please provide sandbox and try to reproduce it. We are actually depends on material-ui theme, but they are using em and rem so I can advice you check the font-size of <html> tag.

@darylong  here is an example of how to change styling of any pickers control

I had the same problem because i use:
html {
  font-size: 62.5%; /* 62.5% of 16px = 10px */
}

I solved with this (as shown in material ui documentation):
const theme = createMuiTheme({
  typography: {
    // ...
    // Tell Material-UI what's the font-size on the html element is.
    htmlFontSize: 10,
    // ...
  },
});

It is already fixed in v3

@darylong here is an example of how to change styling of any pickers control

link not found. Please share it again


CDN tui-image-editor.js not working?

Version
latest (3.2.0 I think)
Development Environment
Google Chrome
Current Behavior
Using CDN

But got the following error from the console.
tui-image-editor.js:4453 Uncaught TypeError: Cannot read property 'forEach' of undefined
    at keyMirror (tui-image-editor.js:4453)
    at Object.<anonymous> (tui-image-editor.js:4377)
    at __webpack_require__ (tui-image-editor.js:36)
    at Object.<anonymous> (tui-image-editor.js:4233)
    at __webpack_require__ (tui-image-editor.js:36)
    at Object.<anonymous> (tui-image-editor.js:4172)
    at __webpack_require__ (tui-image-editor.js:36)
    at Object.<anonymous> (tui-image-editor.js:3819)
    at __webpack_require__ (tui-image-editor.js:36)
    at Object.module.exports (tui-image-editor.js:604)

Expected Behavior
should load correctly?

@dalinhuang99

image-editor has dependencies on the following modules:
Refer to the example page to help you get started.

fabric.js >=1.6.7
tui.code-snippet >=1.3.0
tui.color-picker >=2.2.0


Update from Phore upstream v1.2.2

When merging it, be sure to keep the commit history, don't squash the PR into a single commit.
This update has some problems that we need to investigate.
When running this update on mainnet, it reports error "incorrect proof of work (DGW pre-fork)" at block 37 and the sync can't continue. The PoW related code was not changed in this update.
When I tried the send-qt downloaded from the official site, send-qt doesn't sync at all and report error "Check your wallet version, there is a new protocol on the network.".
We need to make send-qt works, then see if it has issues on block 37.
I build the master and do a test, the sync gets stuck at block 37 for PoW verification error, same as the one in the PR.

Moved From: https://github.com/SocialSend/SocialSend/pull/27

I build the master and do a test, the sync gets stuck at block 37 for PoW verification error, same as the one in the PR.

I have the same issue.  It was a missed problem between version <IP_ADDRESS> and <IP_ADDRESS>. I am not sure exactly what the change or issue is yet..  Version <IP_ADDRESS> should not have this issue and is able to sync.
The warning about protocol version is just an alert message about a protocol version change, and should not effect anything.

When I tried the send-qt downloaded from the official site, send-qt doesn't sync at all and report error "Check your wallet version, there is a new protocol on the network.".

Please try adding some nodes manually.  I am not sure if the seed nodes listed in the older version are still online.  Ignore the protocol version warning..
Try these nodes to get synced up:

fr.socialsend.io
de.socialsend.io
us-e1.socialsend.io
us-e2.socialsend.io

I will compile as well and check on macOS versions 10.15/11 intel and macOS 11 arm(M1)
As @squidicuzz has said there was a change in a previous version that caused a sync issue that was missed. There where only some minor updates so hopefully we can find it easily.

Will not compile on macOS 10.15+
brew no longer supports openssl 1.0., bitcoin upstream has dropped openssl completely and PIVX upstream has moved to  1.1. Seeing how we will not be adding zerocoin, moving to pivx's and then bitcoins solution should be pretty safe in the near future.
Attempting to compile depends to use depends libs instead of brew installed libs resulted in failed downloads.
Fetching v1.1.0.tar.bz2 from https://bitbucket.org/al45tair/ds_store/get   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current                                  Dload  Upload   Total   Spent    Left  Speed   0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0 curl: (22) The requested URL returned error: 404  Fetching v1.1.0.tar.bz2 from https://bitcoincore.org/depends-sources   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current                                  Dload  Upload   Total   Spent    Left  Speed   0     0    0     0    0     0      0      0 --:--:--  0:00:06 --:--:--     0 curl: (22) The requested URL returned error: 404 Not Found
Apple and brew no longer support any os versions below 10.14 and will result in ssl cert errors when trying to download prerequisite libs. Depends should probably reflect this. Machines that can not update to at least 10.15 are over 10 years old. The general EOL for apple device service parts is 7 years.
This is great to because the separate dmgs for multiple version of mac os x can be dropped if depends and gittian can be updated building for 10.14 and higher using the 10.15.1 SDK (xcode version 11.3.1)
I know this is just the start of getting matched up with upstream, just noting the issues here for later, I will try to build on an older version of Mac OS X shortly...

I made a pr to fix the make deploy issue for macOS (10.15 is what I tested the fix on)
https://github.com/wqking-misc/SocialSend/pull/1
if I did the pr on the wrong branch please let me know I will redo it. @wqking


It would be great if balena-sound devices were supported devices by google home.  This would allow you to add them to rooms and control music playback by voice.  For example "hey google play Pink Floyd on balena-sound"

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

@finnje please take a look at #102 . I think that is what you are searching for. And please fill in the form and don't use the title as the whole explenation next time you submit a issue on github.


Maint/must own user

Overview
mustOwnUser was performing an authority check during the process and this should be done through the mustBeAuthenticated middleware instead.
Additionally focused all json error message responses to come under 'error' and not a mixture of 'error' or 'message'. It could be shifted to 'message' it that is preferred but not a mixture. This is a joint effort with devwars.tv-#16 to ensure the error dispatch handles the error or message cases.
Sanitation
User objects that are being bound during the ensured authentication process were not being sanitized which resulted in the generic return current authentication route returning the users more personal information (password).
Temp Route
Since the temp route for /user exists, it required the processing through the mustBeAuthenticated middleware to ensure that the user object was being returned once again.
Notes

Grammar adjustments
shifted to status() over sendStatus() since a json message is is now being sent instead.
refactored user sanitation to the authentication service.
all tests pass

Sounds like a plan regarding the sanitize method, and regarding the (old) editor, I’ll ensure to ensure it’s functionality but it should work as expected.


corrected sign of Coriolis term

Typo in documentation only. I corrected the sign of the Coriolis term in the expression for the meridional momentum tendency in the documentation.
What changes does this PR introduce?
The source code in cd_code_scheme has the correct sign – this is only a bug in the documentation.

LGTM
The tests failed because of an issue installing the dependencies. I've restarted them, and also built the docs locally - as you'd expect with such a small change, everything works just fine.

Thanks – first time submitting a pull request and don't really know how the continuous integration systems work yet!

No worries. Feel free to stop by if you've got any questions.


"Unable to reserve cache with key"

Hi, I've got a workflow where I'm using this action, however, it doesn't seem to be caching anything. I get the error:
Unable to reserve cache with key Linux-xmltv-cache, another job may be creating this cache.

Obviously, because of it, subsequent jobs do not find any caches.
Cache usage (full workflow):
      - name: XMLTV cache
        id: cache-xmltv
        uses: actions/cache@v2
        with:
          path: /config/.xmltv/cache
          key: ${{ runner.os }}-xmltv-cache

Link to workflow

Hi @fugkco, this is usually a symptom indicating the creation of the cache failed.  To avoid wasting unnecessary time creating the cache if it already exists, the cache is first "reserved", then the runner creates the compressed tar with the cache contents, and finally that is uploaded to the server.  If something breaks between when the cache is reserved and when the upload finishes, the cache gets stuck in the "reserved" state.  You will then see the "Unable to reserve cache...another job may be creating this cache" message until that cache is automatically removed (it could take up to 24 hours but work is underway to reduce this delay).
Instead of waiting that long, you can also change the cache key, for example:
key: ${{ runner.os }}-xmltv-cache-v2

After making this change, take a look at the Post Cache step on the next run.  It will show an error if there is any issue creating the cache.
If I had to guess, the failure may have to do with the cache being rooted at /config.  If you see any errors related to that path, try moving that folder to within the GitHub workspace (this is the default folder each step runs in).

I realise that I saw this response, and used gave it a cache key, which worked, but I forgot to reply and close this issue. Anyway, so it worked. Thanks for the help!

@dhadka what is the point of creating a new cache key? If this is what it seems, the best course of action would be to ignore the error. You start X concurrent jobs, they all produce the same artifact, then they try to save it using the same cache key. You need only one of these to succeed.
Ideally, you should be able to run only one of those jobs, then make the other X-1 wait on it to get its artifact from the cache, but AFAIK, there is no easy way to do this.


Make the ghost.url.api

Hi there,
How are you? I'd like to know if it's possible to make this <script> tag async?
Unless you have particular reasons not to do it and I'd be glad to hear them. I can make a PR if you want too :)
Thank you guys!

Hey @eexit!
I'm going to close this issue as we use github solely for bug tracking and feature development. You can raise any idea on https://ideas.ghost.org.
We can provide better support in our slack channel.
Thanks 👋

Duplicate of #7299


Use unary function for numeric to decimal cast

Which issue does this PR close?

Closes #2972.
Rationale for this change

What changes are included in this PR?

Are there any user-facing changes?

I presume you intend to fix the overflow in a subsequent PR?

Yes. 👍


Drop the Content-Length header from multipart parts

This causes our users grief:
https://github.com/square/okhttp/issues/2604
https://github.com/square/okhttp/issues/2138
I've resisted removing it because it seemed like it'd
break compatibility in a significant way. But with OkHttp 5
it's a good time to break compatibility.
As far as I can tell the behavior of including Content-Length
in multipart bodies is not performed by web browsers or other
HTTP clients.

FYI, #7140 also reported this issue with this exact fix proposed in #7139.
As well, the previous behavior is forbidden by RFC7578.
Thanks for implementing the fix.


Error when running node cli

So, I cloned the repo, and the first thing it complains about is missing "use strict";, which I fixed in my clone, but after that it complains when running node cli.js/node cli and gives the following error:
/home/fredrik/Downloads/splash-cli/node_modules/chili-js/index.js:35
module.exports = String.prototype.capitalize = function(divider = ' ', joiner = divider) {
                                                                ^

SyntaxError: Unexpected token =
    at exports.runInThisContext (vm.js:53:16)
    at Module._compile (module.js:374:25)
    at Object.Module._extensions..js (module.js:417:10)
    at Module.load (module.js:344:32)
    at Function.Module._load (module.js:301:12)
    at Module.require (module.js:354:17)
    at require (internal/module.js:12:17)
    at Object.<anonymous> (/home/fredrik/Downloads/splash-cli/libs/variables.js:1:63)
    at Module._compile (module.js:410:26)
    at Object.Module._extensions..js (module.js:417:10

I even tried installing babel-cli to force it to use ECMAscript 2015, but it gives the same error.

So, I cloned the repo, and the first thing it complains about is missing "use strict";

I didn't include it because i use an external file (libs/variables.js) for variables, and it gives error while running.
I'll check chili-js, thanks for report.


Refactor AR process

We should clean up https://github.com/CDCgov/multisignal-epi-inference/blob/main/model/src/pyrenew/process/ar.py to reflect recent design decisions. This work should be similar to the work done in https://github.com/CDCgov/multisignal-epi-inference/pull/275.
We should also look around at other examples to see if we can learn lessons from other examples:

https://forum.pyro.ai/t/ar-p-in-numpyro/2671
https://juanitorduz.github.io/arma_numpyro/
https://num.pyro.ai/en/stable/examples/ar2.html

Also related: https://github.com/CDCgov/multisignal-epi-inference/issues/214

https://github.com/CDCgov/multisignal-epi-inference/pull/262#discussion_r1693486666


Missing secret name for ENV-variable when not creating secret

Problem
When setting secrets.createSecret to false and not configuring secrets.secretName, the ENV-variable definition for PROMITOR_AUTH_APPKEY is missing a secret name.
Actual Behavior
# ...
          env:
          - name: PROMITOR_AUTH_APPKEY
            valueFrom:
              secretKeyRef:
                  name:                        # <------- Missing!
                  key: azure-app-key
# ...

Expected Behavior
I would expect an error because when setting secrets.createSecret to false, I expect the user to specify a custom secret name via secrets.secretName.
Steps to reproduce
helm template promitor ./promitor-agent-scraper --set secrets.createSecret=false

Specifications

Version: latest (bfa0c414efba7e4c85e44bdd9f0206ec36d16566)
Platform: irrelevant
Subsystem: irrelevant

Are you willing to contribute a fix or already adding it through #106 ?

I would prefer to do this in another PR.

Fine by me!

I'm happy to create a new release once this one is in


Error while running

Hello, I get the following error when I try to run homekit2mqtt. I cant make a lot of sense of it. Please help.
2017-05-22 13:13:23.383   homekit2mqtt 0.6.5 starting
2017-05-22 13:13:23.946   mqtt trying to connect mqtt://<IP_ADDRESS>
2017-05-22 13:13:23.999   using hap-nodejs version 0.4.17
*** WARNING *** The program 'node' uses the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see http://0pointer.de/avahi-compat?s=libdns_sd&e=node
*** WARNING *** The program 'node' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see http://0pointer.de/avahi-compat?s=libdns_sd&e=node&f=DNSServiceRegister
2017-05-22 13:13:24.505   loading HomeKit to MQTT mapping file /usr/local/lib/node_modules/homekit2mqtt/example-homekit2mqtt.json
2017-05-22 13:13:24.511  loading accessories/WindowCovering.js
/usr/local/lib/node_modules/homekit2mqtt/accessories/WindowCovering.js:3
var {mqttPub, mqttSub, mqttStatus, log, newAccessory, Service, Characteristic} = iface;
^
SyntaxError: Unexpected token {
at exports.runInThisContext (vm.js:53:16)
at Module._compile (module.js:387:25)
at Object.Module._extensions..js (module.js:422:10)
at Module.load (module.js:357:32)
at Function.Module._load (module.js:314:12)
at Module.require (module.js:367:17)
at require (internal/module.js:16:19)
at loadAccessory (/usr/local/lib/node_modules/homekit2mqtt/index.js:168:28)
at /usr/local/lib/node_modules/homekit2mqtt/index.js:179:9
at Array.forEach (native)

Seems to be an outdated Node.js version. For homekit2mqtt you need Node.js >= 6.0.0.


add all the contributors details in res/contributors.json file

@devansh016 Can you describe a bit on what details are need to be added?

{
"name": "Devansh Chaudhary",
"github_url": "https://github.com/devansh016",
"image_url": "https://avatars.githubusercontent.com/u/58871818?s=96&v=4"
}
Here is a example, You have to add all the contributor details in the json file you can get contributor details from the repo.

@devansh016 Okay. Plz assign me this.

@devansh016 Raised a PR, also do the needful of adding hacktorberfest-accepted label.


publicPath field doesn't work for AWS Lambda + webpack + bugsnag

Tried all the combination of wildcards and file entries, the source map does get uploaded, but it is an incorrect one. Cause it does not trace back to the original source code and just shows the minified weback version instead.
My webpack config (in parts) is as follows:
new BugsnagSourceMapUploaderPlugin({
            apiKey: bugsnagApiKey,
            overwrite: true,
            publicPath: 'dist/email-notifications/src/'
          }),

devtool: 'source-map',
    output: {
      path: join(__dirname, '/dist/email-notifications/src/'),
      filename: 'index.js'
    },

My folder structure is as follows:
- email-notifications
   - src (has the source code on which webpack works)
       - index.js
       - other folders (with functions called from index.js)
   - dist
       - email-notifications
           - index.js
           - index.js.map

My lambda bundle consists of just the dist/email-notifications/index.js file

Closing as we have not heard back. If you have any further questions, please get in touch.


Incompatible Gradle wrapper.

The gradle wrapper is version 2.4, but the Android plugin in version 1.1.0.
You need at least android plugin version 1.2.0 if you are going to run gradle 2.4.
Please upgrade the Android plugin version to something newer ( e.g. 1.3.1 ).

Looks like it was already changed here https://github.com/mixpanel/mixpanel-android/commit/1af0f6af29dc8fa9b298be32c9025a5ef0c0d04d#diff-c197962302397baf3a4cc36463dce5ea
Thanks @yogurtearl for your help!


ADS freezes when opening notebook (file size 475KB and above)

Azure Data Studio Version:
Version: 1.29.0 (user setup)
Commit: 0f5cfdc2c8c2433028842e16dc5ac1a65da24292
Date: 2021-05-15T01:12:11.112Z
VS Code: 1.53.0
Electron: 11.2.2
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19043

Steps to Reproduce:

Open a 475KB notebook.
After a certain time, it will say "the window is no longer responding"

@qifahs - please feel free to add comments here also on your experience here

If you haven't already please get someone on the Notebook team the specific notebook you're having an issue with for debugging.

Thanks Charles! Already sent to @lucyzhang929  and @chlafreniere  :)
My repro TSG has sensitive database perf analysis, hence didn't upload it here.

Moving out to September since I'll be continuing to work on improving the grid rendering times.

Closing this issue since notebook/grid rendering times were improved in the following PRs: https://github.com/microsoft/azuredatastudio/pull/16577, https://github.com/microsoft/azuredatastudio/pull/16709, https://github.com/microsoft/azuredatastudio/pull/16833


Error While Downloading DeepBLAST Model and Database

While trying to install the DeepBLAST model and the associated database using the provided wget commands, I encountered an error indicating that the model file could not be found. Below are the steps I followed and the resulting error message:
Attempted to download the DeepBLAST model using the following command:
wget https://users.flatironinstitute.org/jmorton/public_www/deepblast-public-data/checkpoints/deepblast-v3.ckpt
Error Message:
--2024-07-25 14:03:39--  https://users.flatironinstitute.org/jmorton/public_www/deepblast-public-data/checkpoints/deepblast-v3.ckpt
Resolving users.flatironinstitute.org (users.flatironinstitute.org)... <IP_ADDRESS>
Connecting to users.flatironinstitute.org (users.flatironinstitute.org)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: /~jmorton/deepblast-public-data/checkpoints/deepblast-v3.ckpt [following]
--2024-07-25 14:03:39--  https://users.flatironinstitute.org/~jmorton/deepblast-public-data/checkpoints/deepblast-v3.ckpt
Reusing existing connection to users.flatironinstitute.org:443.
HTTP request sent, awaiting response... 404 Not Found
2024-07-25 14:03:39 ERROR 404: Not Found.
It appears that the file might have been moved or the URL might be incorrect.
Could you please verify the location of the DeepBLAST model file and update the download URL if it has changed?

Hi, I'm not sure where you are seeing these wget instructions. The README has been updated with the latest checkpoints
I'll link them here again https://figshare.com/articles/dataset/TMvec_DeepBLAST_models/25810099


eventIds not updated on 'prepend' action

Hey,
When doing an 'append' action, the eventIds is being updated with the new logs (after removeDuplicates(newLogs) method), to avoid duplicates in the list.
However, on 'prepend' action, new logs are being added to the $scope.events array, but eventIds is not being updated. It is missing the eventIds.add(event.id); line after this one: https://github.com/sivasamyk/logtrail/blob/master/public/app.js#L241

Good catch. Thanks!

Thumbs up for that super fast fix! 👍


[SPARK-47664][PYTHON][CONNECT] Validate the column name with cached schema

What changes were proposed in this pull request?
improve the column name validation, to try the best to avoid RPC.
Why are the changes needed?
existing validation contains two parts:

check whether the column name is in self.columns <- client side validation;
if step 1 fail, validate with additional RPC df.select(...) <- RPC;

the client side validation is too simple, and this PR aims to improve it to cover more cases:

backticks:

'`a`'

nested fields:

'a.b.c'

Does this PR introduce any user-facing change?
no
How was this patch tested?
ci, added ut
Was this patch authored or co-authored using generative AI tooling?
no

Merged to master.


Sort followerinfo in maintainermode right

This is a trivial fix to get the sort order right in maintainer mode for
followerinfo lists.

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/13292/

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/13294/

Now it fails exactly where the modifications were made:
* Test "resilience_move"
    [FAILED]  tests/js/server/resilience/move/moving-shards-cluster.js

      "test" failed: server is dead:
health Check Signal(6)  checkArangoAlive: Marking crashy
health Check Signal(6)  checkArangoAlive: Marking crashy
health Check Signal(6)  checkArangoAlive: Marking crashy

   Suites failed: 1 Tests Failed: 0

--------------------------------------------------------------------------------
Crash analysis of: {"role":"dbserver","port":"12355","endpoint":"tcp://<IP_ADDRESS>:12355","rootDir":"/work/tmp/arangosh_heaLOl/resilience_move/dbserver0","url":"http://<IP_ADDRESS>:12355","args":{"configuration":"/work/ArangoDB/etc/testing/arangod-dbserver.conf","define":"TOP_DIR=/work/ArangoDB","javascript.app-path":"/work/tmp/arangosh_heaLOl/resilience_move/dbserver0/apps","javascript.copy-installation":false,"http.trusted-origin":"all","temp.path":"/work/tmp/arangosh_heaLOl/resilience_move/dbserver0/tmp","server.storage-engine":"rocksdb","server.endpoint":"tcp://<IP_ADDRESS>:12355","database.directory":"/work/tmp/arangosh_heaLOl/resilience_move/dbserver0/data","log.file":"/work/tmp/arangosh_heaLOl/resilience_move/dbserver0/log","javascript.allow-external-process-control":"true","javascript.allow-port-testing":"true","cluster.my-address":"tcp://<IP_ADDRESS>:12355","cluster.my-role":"PRIMARY","cluster.agency-endpoint":"tcp://<IP_ADDRESS>:12311","javascript.enabled":"false"},"pid":18595,"name":"dbserver - 12355","upAndRunning":true,"id":"PRMR-4f0e33c6-001f-49ab-b93f-9b3bc2596635","stats":{"minorPageFaults":47690,"majorPageFaults":0,"userTime":3.05,"systemTime":1.73,"numberOfThreads":1,"residentSize":0,"residentSizePercent":0,"virtualSize":0,"rchar":114716128,"wchar":171818259,"syscr":33911,"syscw":70733,"read_bytes":16384,"write_bytes":172355584,"cancelled_write_bytes":4096},"message":"\n","exitStatus":{"status":"ABORTED","signal":6}}
(gdb) #0  __restore_sigs (set=set@entry=0x7f3de11fb330)
    at ./arch/x86_64/syscall_arch.h:40
#1  0x00007f3defc5ee1c in raise (sig=sig@entry=6) at src/signal/raise.c:11
#2  0x00007f3defc55098 in abort () at src/exit/abort.c:13
#3  0x00007f3dedfd03c5 in (anonymous namespace)::killProcess (
    signal=signal@entry=6) at /work/ArangoDB/lib/Basics/CrashHandler.cpp:120
#4  0x00007f3dedfd0446 in arangodb::CrashHandler::crash (
    context=context@entry=0x7f3de11fb4f0 "assertion failed in /work/ArangoDB/arangod/Cluster/FollowerInfo.cpp:332: diff.empty()")
    at /work/ArangoDB/lib/Basics/CrashHandler.cpp:436
#5  0x00007f3dedfd0509 in arangodb::CrashHandler::assertionFailure (
    file=file@entry=0x7f3defca2df8 "/work/ArangoDB/arangod/Cluster/FollowerInfo.cpp", line=line@entry=332,
    context=context@entry=0x7f3defca2dc1 "diff.empty()")
    at /work/ArangoDB/lib/Basics/CrashHandler.cpp:453
#6  0x00007f3deceb6be8 in arangodb::FollowerInfo::updateFailoverCandidates()
    () at /work/ArangoDB/arangod/Cluster/FollowerInfo.cpp:332
#7  0x00007f3dece4bb2a in arangodb::FollowerInfo::allowedToWrite (

http://<IP_ADDRESS>:8080/job/arangodb-matrix-pr-linux/14754/EDITION=community,STORAGE_ENGINE=rocksdb,TEST_SUITE=cluster,limit=(linux&&test)||gce/artifact/testfailures.txt

http://<IP_ADDRESS>:8080/view/PR/job/arangodb-matrix-pr/13305/

This should be good to go, Jenkins was green. It is a very minor fix, only touching MaintainerMode runs.


Replace aet aliases with at.

See https://github.com/aesara-devs/aesara/issues/328 for the motivation.

Yes! I've noticed the aesara documentation still uses aet in many places as well.

I have a pr to change that too.
On Mon, Jan 10, 2022, 16:26 Rémi Louf @.***> wrote:

Yes! I've noticed the aesara documentation still uses aet in many places
as well.
—
Reply to this email directly, view it on GitHub
https://github.com/aesara-devs/aehmc/pull/51#issuecomment-1008683217,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFETGG5OOV6JI262KF35X3UVKQ33ANCNFSM5LS6RR3A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

Changed in aesara by https://github.com/aesara-devs/aesara/pull/728.

Thank you!


walletSendHandler does not check address length

If you miss a character in the address your coins will be sent to oblivion.

fixed


Fatal type inconsistency in pino-http when installing @types/koa-pino-logger

I get the following error from this package's type declarations:
node_modules/@types/pino-http/index.d.ts:69:9 - error TS2717: Subsequent property declarations must have the same type.  Property 'log' must be of type 'Logger<LoggerOptions>', but here has type 'Logger'.

69         log: Logger;
           ~~~

  node_modules/pino-http/index.d.ts:75:7
    75       log: pino.Logger;
             ~~~
    'log' was also declared here.

Found 1 error in node_modules/@types/pino-http/index.d.ts:69

Here are my package.json dependencies:
{
  "devDependencies": {
    "@types/koa": "^2.13.4",
    "@types/koa-pino-logger": "^3.0.1",
    "@types/koa-router": "^7.4.4",
    "@types/pino": "^7.0.5",
    "@typescript-eslint/eslint-plugin": "^5.20.0",
    "@typescript-eslint/parser": "^5.20.0",
    "eslint": "^8.13.0",
    "eslint-config-airbnb-base": "^15.0.0",
    "eslint-import-resolver-typescript": "^2.7.1",
    "eslint-plugin-import": "^2.26.0",
    "pino-pretty": "^7.6.1",
    "typescript": "^4.6.3"
  },
  "dependencies": {
    "envalid": "^7.3.1",
    "koa": "^2.13.4",
    "koa-pino-logger": "^4.0.0",
    "koa-router": "^10.1.1",
    "pino": "^7.10.0",
    "source-map-support": "^0.5.21"
  }
}

And here's my tsconfig.json
{
  "compilerOptions": {
    "baseUrl": ".",
    "rootDir": ".",
    "outDir": "build",

    "target": "es2021",
    "module": "commonjs",
    "lib": ["es2021"],

    "allowJs": false,
    "strict": true,

    "sourceMap": true,
    "inlineSources": true,

    "allowSyntheticDefaultImports": true,
    "esModuleInterop": true,
    "resolveJsonModule": true,
    "isolatedModules": true,

    "noImplicitAny": true,
    "removeComments": true,
    "preserveConstEnums": true,
    "noErrorTruncation": true,
    "importsNotUsedAsValues": "error",

    "paths": {
      "@libs/*": [
        "./src/libs/*"
      ]
    }
  },
  "include": ["src/**/*.ts"],
  "exclude": ["node_modules"]
}

So it seems the type defined in pino-http directly, is inconsistent with the types declared in @types/pino-http, when installing the latest version of @types/koa-pino-logger
cc @mcollina @jsumners @davidmarkclements

Please do not "cc" people unnecessarily. We get notifications about issues filed here.

We do not maintain any of the definitelytyped types. You should probably report this to them.

Thanks @jsumners will not in future.
@mcollina you're saying the types are entirely maintained by people not associated with the pinojs org?


Try to restore the local parser presence...

because people is asking for it and it's boring to update every single time.

Nope - it's not going to happen.


Use scale-available annotation for harvester services auto-scaling

With this solution, there won't be pending pods if the number of nodes is less than 3.

need to address the CI failure.

Fixed. The annotation does not support 0 replicas which is used in the integration tests. Fall back to spec.replicas in this case to comply with the integration test setup.


--config=c++17 option is incompatible with GCC build

System information

OS Platform and Distribution Ubuntu Linux 18.04 LTS
TensorFlow installed from (source or binary): source
TensorFlow version: master (e2204b27)
Python version: 3.8.3
Bazel version (if compiling from source): 3.1.0
GCC/Compiler version (if compiling from source): 7.5.0-3ubuntu1~18.04

Describe the problem
The --config=c++17 build configuration option adds compiler flags which are incompatible with GCC.
Provide the exact sequence of commands / steps that you executed before running into the problem
./configure (Accept defaults)

bazel build --config=c++17 //tensorflow:tensorflow_cc

Any other info / logs
ERROR: /home/andrew/.cache/bazel/_bazel_andrew/05f0c1fc0fd5d93d6530b840ab375f68/external/com_github_grpc_grpc/BUILD:487:1: C++ compilation of rule '@com_github_grpc_grpc//:gpr_base' failed (Exit 1)
gcc: error: unrecognized command line option '-stdlib=libc++'

The c++17 configuration option adds the -stdlib=libc++ flag to the C++ compiler, but this is a Clang flag, not GCC.

@planetmarshall
Can you please try with C++11 and C++14 and see if the error still persists.Please, refer #39617, #23561 and see if it helps you.Thanks!

Thanks for the response. I can build with C++11 and C++14. The issue is the incompatible compiler flag - I note @golden0080 made the same observation in #23561

@planetmarshall
Please, close this thread if your issue was resolved.Thanks!

Can you send a PR to remove the libc++ setup? We now have a different config option for that.

@planetmarshall
Please, close this thread if your issue was resolved.Thanks!

Well, it's not really resolved. The bazel file contains a configuration option that can't possibly work. Perhaps it should be removed?

That's why I suggested sending a PR to remove the flag.

Made #42158 to try removing the flag. If that works, we can use --config=c++17_gcc to compile as if --config=c++17 was passed in but without linking libc++. If you want, can you patch in the PR and test too?
Unfortunately, we might not be able to change the existing config as there might be people already using the old config.

#42158 landed, I think we can close this now.


Better collection-level metadata

Been having lots of confusion with creators and testers using the tooling about the redundant data in cw721 collection info and contract URI. This is an attempt to clear things up and and have a single source of truth for collection data. It basically moves everything we need from contract URI into sg721.
This introduces two required fields, image that serves as a preview image for the entire collection, and description. image doesn't need to be an IPFS link since it's more marketplace-level metadata and is not a traded asset like the individual NFTs. Note this does not break compatibility with cw721 since instantiation is not part of the cw721 spec.
This also introduces an optional external_link that can be a website, etc.
These two fields are all we needed from contract URI anyway. The name, description, seller_fee (royalties) were redundant because they're already part of cw721 ContractInfo and sg721 royalties. Contract URI is used on OpenSea mainly due to a limitation of ERC721 that doesn't include basic metadata like name and description.
Also removed creator since it's already part of ContractInfoResponse, and payment_address is already part of royalties.
I think this cleans and simplifies a lot, and makes collection info more explicitly defined. Also it's one less thing for creators to worry about and less error prone. Also collection info should be easily queried and can easily live on-chain. No need to hide behind an IPFS link. It's also not part of ICS-721 so there's no benefit in interoperability either.

This is a great improvement, a source of frustration for me when I tried to get the test nft collection up.

@yubrew Good points. I think it makes sense to make all of CollectionInfo editable. The ones that should be static are name and symbol which are part of cw721 and non-editable.

Added https://github.com/public-awesome/stargaze-contracts/issues/99 to the v2 board. Want to keep changes minimal before upload.


Syntax Highlight of SQL in php string is utterly random

Does this issue occur when all extensions are disabled?: Yes

VS Code Version:  1.86.2
OS Version: Manjaro Linux

Steps to Reproduce:
Type the following code in a PHP file:

Either you highlight SQL code in PHP strings or you don't. If you do, the highlight has to make sense.
This doesn't.

Here:

Why is the name field highlighted in blue but the other three arent?

Here:

Why is the parameter :name highlighted in blue but :userinfo isn't?

Here:

same as (1).

@alexr00, is this a grammar issue or language server issue? Thanks!

@php4fan can you share a copy/pastable example that I can use to reproduce the issue?

<?php

$query = "INSERT INTO `user`
(telegram_id, name, info)
VALUES (
    {$user['id']},
    :name,
    :userinfo
)
ON DUPLICATE KEY UPDATE
    info = JSON_MERGE_PATCH(info, VALUES(info)),
    name = VALUES(name)";

Thank you!
It looks like the same highlight occurs even outside of PHP when it's just an SQL file. It turns out that name is actually a keyword in SQL: https://dev.mysql.com/doc/refman/8.0/en/keywords.html
It appears to be fine to use in some places, but not in other: https://stackoverflow.com/questions/738124/is-name-a-reserved-word-in-mysql

Ok, so the error is not in not highlighting the other column names, it's in highlighting the one that happens to be called "name". And I can see there are other keywords that have the same issue, like "user".
This is still a bug. In the cases shown above the word "name" has no special meaning in that context, it's a column name like any other, and the query above works as is. That the word may have some meaning in some other context is irrelevant. If the syntax highlight for SQL is this bad, it is truly worse than no highlight at all.