Didn't found any sample up to date to the last version of prism

Hi,
I'm trying to code an UWP app with the last Prism Windows package.

Prism.Unity <IP_ADDRESS>7
Prism.Windows 6.3.0

The given sample is not up to date to the last version.
For example I didn't found the PrismUnityApplication class in the new version.
Regards.

There is no Prism.Windows anymore.


Add references to the user-agent in the guide about creating a new integration

We do have a guide about how to create a new meili integration https://github.com/meilisearch/integration-guides/blob/main/resources/build-integration.md
And we now have a nice and clean way to understand the behavior of our users as you can see here: https://github.com/meilisearch/integration-guides/issues/150
Based on that, it would be nice to see third-party integrations in the usage graphs!

Definitely a good idea :)

Done https://github.com/meilisearch/integration-guides/commit/7468c7c0ce805114f3182ec38a5a7f4aff184811


Add SSL/TLS [🚀]

:rocket: Feature request
Description
 A lot of testing scenarios might involve having the web application using SSL/TLS.
Solution ideas
 Add an option to run web application on both http and https simultaneously.
Possible alternatives
 Have you considered any alternative solutions or workarounds? N/A

When I tried something in this direction in the past, it completely messed up the test automation. For that reason I didn't pursue it and left it to whoever hosts the application to sprinkle SSL/TLS on the environment, e.g. like http://demo.owasp-juice.shop/ and https://demo.owasp-juice.shop/ both work fine on Heroku.


URL error when the char %25C3 appears

%25C3 stretches to:
%2525252525252525252525252525252525252525252525252525252525252525252525252525252525252525252525252525252525252525252525252525252525252525252525252525252525252525252525252525252525252525252525252525252525252525252525C3

/tecnología-ip/cámaras-ip-1/camara-domo-ip-motorizada-detail or
/tecnolog%C3%ADa-ip/c%C3%A1maras-ip-1/camara-domo-ip-motorizada-detail
to
/tecnolog%25252525252525252525252525252525252525252525252525252525252525
252525252525252525252525252525252525C3%25252525252525252525252525252525
2525252525252525252525252525252525252525252525252525252525252
52525ADa-ip/c%252525252525252525252525252525252525252525252525252525252525
25252525252525252525252525252525252525C3%25252525252525252525252525252525
252525252525252525252525252525252525252525252525252525252
525252525A1maras-ip-1/punto-de-acceso-netis-wifi-300-antena-5dbi-detail


Chapter 06 DQN pong training

Hi,
so I faced this error while running the code for training the DQN agent on pong
8589: done 9 games, mean reward -20.444, eps 0.91, speed 124.21 f/s
9518: done 10 games, mean reward -20.400, eps 0.90, speed 121.48 f/s
Traceback (most recent call last):
File "02_dqn_pong.py", line 169, in
    loss_t = calc_loss(batch, net, tgt_net, device=device)
File "02_dqn_pong.py", line 96, in calc_loss
   state_action_values = net(states_v).gather(1, actions_v.unsqueeze(-1)).squeeze(-1)
RuntimeError: index<PHONE_NUMBER>5 is out of bounds for dimension 1 with size 6
I want to know the reason for this indexing error, it happens when I start training the network and I don't have any idea on it's cause

There is no such big action,  the correct action range is from 0 to env.action_space.n (which is 5 on Pong, totally 6 actions). So, I think you can check the array action_v. make sure that was the really action array you want to input to the method gather.

Hi,
so I faced this error while running the code for training the DQN agent on pong
8589: done 9 games, mean reward -20.444, eps 0.91, speed 124.21 f/s
9518: done 10 games, mean reward -20.400, eps 0.90, speed 121.48 f/s
Traceback (most recent call last):
File "02_dqn_pong.py", line 169, in
 loss_t = calc_loss(batch, net, tgt_net, device=device)
File "02_dqn_pong.py", line 96, in calc_loss
 state_action_values = net(states_v).gather(1, actions_v.unsqueeze(-1)).squeeze(-1)
RuntimeError: index<PHONE_NUMBER>5 is out of bounds for dimension 1 with size 6
I want to know the reason for this indexing error, it happens when I start training the network and I don't have any idea on it's cause

There is no such big action, the correct action range is from 0 to env.action_space.n (which is 5 on Pong, totally 6 actions). So, I think you can check the array action_v. make sure that was the really action array you want to input to the method gather.

Hi, guys,
This error also appears when I use the CPU instead of the GPU.
If I use the GPU the error appears:
Traceback (most recent call last):
File "...Chapter06/02_dqn_pong.py", line 176, in
loss_t = calc_loss(batch, net, tgt_net, device=device)
File "...Chapter06/02_dqn_pong.py", line 97, in calc_loss
state_action_values = net(states_v).gather(1, actions_v.unsqueeze(-1)).squeeze(-1)
RuntimeError: Expected object of scalar type Long but got scalar type Int for argument #3 'index' in call to _th_gather_out
If I use '.long()' the speed decreases massively. But the code runs.
And:
print(actions_v.shape) -> torch.Size([32])


Sometimes when opening, tryies to install lsp servers but looks they're invalid

Mostly after installing plugins

Seemed to be missing npm binary to install those lsp's, however there're some lsp not available for some OS's like lua-ls on Alpine


UX design for multiaccoutn login

@nbashirbello pointed me to an internal design doc about this. I see that our IntelliJ plugin follows the UX design in the doc faithfully. (However, IMHO, the design doc is about personalized IDE experience much like the Chrome login feature, e.g., saving IDE user preferences on cloud, so I think the context is a little bit different.)

@chanseokoh This is done, right?


Suggest package to replace while this return BAD_REQUEST

This project looks like are not have maintenance.
I don't know how long it will be, but i here to suggest alternative for this package.
Check out https://github.com/translate-tools/core (npm)
I maintanence this project and its support typescript and have google, yandex and bing modules.
@matheuss if you not have time for maintenance a https://github.com/matheuss/google-translate-api can you insert in head of README.md link to @translate-tools/core package until you not return?
Your package is popular and you can help users find solution while google-translate-api is not working

Thanks a lot.
https://github.com/translate-tools/core
works for me.


BoxMan.APPEND_TYPE_BETWEEN needs to adjust scroll position.

It solved.
Check http://localhost:8081/sj-js/boxman/append_type.html


Segments are not being counted since april update.

Segments just sit at 0 on the counter  the whole run.

Thank you for the report. I was aware of this but didn't comment. This happened to coincide with the v2 update. So I have made the release available now after thourough testing for several weeks/runs. This is fixed with https://github.com/MarianArlt/sheolhelper/commit/bc4a30887d50652204fbaa054621712b0a10ef96. You can simply grab the latest release by clicking here.

Thanks for getting the update out to us. Your plug in is the best thing to happen to odyssey from the community. Thanks so much for it.
D. "Trey" Bennett
@.***
@.***
225.270.0209

From: Marian Arlt @.>
Sent: Monday, April 25, 2022 7:53:52 AM
To: MarianArlt/sheolhelper @.>
Cc: Trey Bennett @.>; Author @.>
Subject: Re: [MarianArlt/sheolhelper] Segments are not being counted since april update. (Issue #2)
Thank you for the report. I was aware of this but didn't comment. This happened to coincide with the v2 update. So I have made the release available now after thourough testing for several weeks/runs. This is fixed with bc4a308https://github.com/MarianArlt/sheolhelper/commit/bc4a30887d50652204fbaa054621712b0a10ef96. You can simply grab the latest release by clicking herehttps://github.com/MarianArlt/sheolhelper/releases/latest/download/sheolhelper.zip.
—
Reply to this email directly, view it on GitHubhttps://github.com/MarianArlt/sheolhelper/issues/2#issuecomment-1108531842, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AWAFP23W5CWW4X2TPBRSNKDVG2IWBANCNFSM5UFIBBOQ.
You are receiving this because you authored the thread.Message ID: @.***>


feat: add pinned post component

What does this change?
Why?

Coverage remained the same at 99.638% when pulling 66d50dbc841a0e52599dcbc121230f4cbe8b4bc8 on add-pinned-post-component into d494fe6e5b673ef6156aeef95efebe5d92ed5a34 on main.


Bugfix/hoomd import

This bugfix addresses issue #33. It's pretty straightforward and hopefully I didn't overlook anything with my regex replacements. All tests still pass, so this should be ready to merge. Separately, we should address #34 at some point.
I didn't think about it, should this go into develop or master?

Thank you very much! Please target this onto develop, and I will look it over and merge when I check on the other PRs. (Likely tomorrow night.)

Resolves #33


Wrong naming in heading of documentation "Deploy the grafaml helm chart on Kubernetes"

Problem description
While googling for the Helm Chart "grafaml", which i am the author of, i found a Pulumi documentation with the name "Deploy the grafaml helm chart on Kubernetes".
After being really confused why Pulumi would know about my Helm Chart and describe how to install it, i quickly realised, after reading the documentation, that a normal Grafana Helm Chart Deployment is being described. So i guess it is just a typo in the Heading of the documentation page? I guess it should actually be "Deploy the Grafana helm chart on Kubernetes"
Suggestions for a fix
Change the heading to "Deploy the Grafana helm chart on Kubernetes"

thanks @erNail !

We've removed this answer page in the near term.


Changes redcord errors to subclass RedcordError < StandardError

A light-touch PR to change all Redcord errors that subclass StandardError to instead subclass RecordError, which is a StandardError subclass. Not sure if I'm missing other desired functionality. Putting up a draft to run CI - no review needed as of now.
Closes #100.
Note: I'm a new intern generally onboarding to the team! No rush on review and any/all feedback is appreciated!

Hm, I think I'm changing some conditional paths by accident - likely on error creation/checking. I'll investigate later!


idf_monitor: only mangle /dev/tty.* on Darwin (IDFGH-3507)

On my Linux system, I use udev rules to be able to easily identify serial ports based on their USB bus path, for example
SUBSYSTEM=="tty", ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="ea60", SYMLINK+="tty.cp2102-%s{devpath}"

So it took me a while to figure out why the tools were looking for /dev/cu. devices. This fixes it for me.

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

Thanks for your contribution.

Hi @kzyapkov,
Sorry for the slow turnaround on reviewing your PR. This looks good to me, I've pushed it into our internal review & merge queue.
Angus


How to support video processing

Apply the same algorithms for each frame of the video.  Not really knowledgeable on how to do it in matlab but using tensorflow and opencv python/c++ you can implement something similar.


Adjust shared content-meter component setting of gateType & add support for AB, DE & WATT customizations.

Set the gateType to metered within the additionalEventData portion of the content meter component.  This will then set the actionSource to content gate and content gate type of meter.
This will go in conjunction with:

https://github.com/parameter1/cox-matthews-associates-websites/pull/273
https://github.com/parameter1/watt-global-media-websites/pull/272
AB will also need a dep upgrade and push to get the Metered contentGateType update.

 GTM/IdentityX  unification & documentation


Nukies sometimes get stuck in place and cannot move.

Description

Sometimes nukies get stuck and can't move, but they can turn/spin their character, interact with items, see others move, and chat.
I've tried to get logs, but the best I've been able to get teased out is:
"can't resolve robust shared physics components physicscomponet"
If I were to guess at a source it would be something with changing grids or maps, that could be a wild goose chase though.
I tried many things to get them moving again. None of these worked:

teleporting them
sending them to admin test area
putting them to sleep with nocturine
FTLing them on the nukie shuttle to the station
putting them in a new body in the admin test area, on the nukie shuttle, or on the station (if I entered the body I could move it.)
having them use f10 > disconnect > reconnect
having them relaunch the client.

Reproduction

Sorry, I don't have any repro steps.
Screenshots

Additional context

If you want to look in a replay (since I have seen people ask in previous issues) you could in round Levi 36595

I got a same problem with salvages, but it go fixed by crossing through fence.

Railings could possibly have something to do with it. I'll come back and say something if I managed to repro that.

Once my nukie buddy was unable to move after vaulting a railing on nukie planet, got fixed after i vaulted him again

This happened to a player that was on station and I tried: Teleporting them, putting them in a locker, shoving them over a table, sitting and unbuckling them. The player mentioned they had vaulted onto a table and tried diving in a trash bin, so maybe it's not the same bug? But the effect is similar, where they can't move and can only spin

It does look like its the railings. Maybe its something to do with vaulting off of the grid into "space"? Not sure, but re-vaulting onto a table fixes it.

i had a similar thing happen and sitting on a chair fixed it

ok reproduced:

get on the infiltrator
jump out the back
drift towards a docking arm
try to vault a railing
cant move


Data Fetch Issue with Some Leagues

Hey, I realized that some of leagues' data can not be fetched correctly.
Following one is working
df = pb.footballdata.fetch_data("england", 2021, 0)

Following ones are not working
df = pb.footballdata.fetch_data("turkey", 2021, 0)
df = pb.footballdata.fetch_data("italy", 2021, 0)

Reduced issue as following
<EMAIL_ADDRESS>in http_error_default(self, req, fp, code, msg, hdrs)
    639 class HTTPDefaultErrorHandler(BaseHandler):
    640     def http_error_default(self, req, fp, code, msg, hdrs):
--> 641         raise HTTPError(req.full_url, code, msg, hdrs, fp)
    642
    643 class HTTPRedirectHandler(BaseHandler):

HTTPError: HTTP Error 300: Multiple Choices

Following one is url from turkey related call though
https://www.football-data.co.uk/mmz4281/2122/T0.csv

When we go to that website, we see following...

Thanks for letting me know.
It looks like there are inconsistencies in how football-data are naming their files, I'll need to add something in to the code to handle this


OVCHTTPSessionManager+PromiseKit.h file not found

I cannot build my project when upgrading to 4.0 beta 1, error is:
/Pods/Overcoat/sources/PromiseKit/OvercoatPromiseKit.h:23:9: 'OvercoatPromiseKit/OVCHTTPSessionManager+PromiseKit.h' file not found
In my Podfile:
 pod 'Overcoat', '~> 4.0.0-beta.1'
 pod 'Overcoat/PromiseKit'
 pod 'PromiseKit'

Also hitting this issue, any resolution?

Hi guys,
sorry for the late response due to being busy these days.
I've updated to 4.0.0-beta.2. The major change is I split Overcoat into multiple podspecs instead of using subspecs.
Could you have a try/test for me? Thanks.
The Podfile has to be changed to:
pod 'Overcoat+PromiseKit', '~> 4.0.0-beta.2'


Application of algorithm

Is this algorithm applicable to outdoor urban scenes?

Yes, it does not make assumptions on the scene type. You might need to tune the kpconv parameters to better handle large scenes though.

Yes, it does not make assumptions on the scene type. You might need to tune the kpconv parameters to better handle large scenes though.

Thanks for your reply. I think I know what to do next.


[TACHYON-1576] Force each key-value partition no larger than the max size set in Conf

https://tachyon.atlassian.net/browse/TACHYON-1576

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/8027/
Test FAILed.

Jenkins, test this again.

just one minor comment

Jenkins, test this please.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/8029/
Test FAILed.

LGTM

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/8031/
Test PASSed.

@jsimsa , I fixed the comment. PTAL

LGTM


Login error

I am a newbie to this and this is my first time trying to use python module Instaloader.
When trying to login I get the error
InvalidArgumentException: Login error: User darkjewel5 does not exist.
I have tried with an older existing account (although not very active) and I just created the new account darkjewel5 above which does not work.
self.context.login(user, passwd)
...\instaloadercontext.py", line 232, in login
raise InvalidArgumentException('Login error: User {} does not exist.'.format(user))
InvalidArgumentException: Login error: User darkjewel5 does not exist.
Instaloader version
instaloader --version 4.2.8.
Please help?

I have figured this out.


Bug when running inflow calculation

Mesh Python SDK version: 1.9.0
Mesh version: 2.15.1+7
Python version: 3.12.1
Operating System (Windows, Ubuntu, etc.): Windows
Environment: dev
When running the following command:
session.run_inflow_calculation(
                    model="Agder",
                    area="Norge",
                    water_course="Otra",
                    start_time=datetime.now().astimezone(timezone.utc) - timedelta(days=30=,
                    end_time=datetime.now().astimezone(timezone.utc),
                    return_datasets=False,
                    resolution=timedelta(minutes=60),
                )

I get the following error message:
2024-10-07 12:28:10,291 - __main__ - ERROR - MainThread - fatal exception (code=0xc0000005):
stack trace:
0> Powel_Mesh_Common!Powel::Common::FatalVectoredExceptionHandler+0x5B
1> ntdll!RtlInitializeCriticalSectionAndSpinCount+0x1C6
2> ntdll!RtlWalkFrameChain+0x1119
3> ntdll!KiUserExceptionDispatcher+0x2E
4> OraOCIEI!slgetohorabaseconfig+0x2509
5> OraOCIEI!slgetohorabaseconfig+0x1B25
6> OraOCIEI!slgetohorabaseconfig+0x1748
7> OraOCIEI!slgetohorabaseconfig+0x15CC
8> OraOCIEI!kzssqlname+0x2B665
9> OraOCIEI!dbgtfFilePop+0xB5BE
10> OraOCIEI!dbgtfFilePop+0xB194
11> OraOCIEI!dbgecPop+0x179D5
12> OraOCIEI!dbgecPop+0x18234
13> OraOCIEI!dbgfcsIlcsRegister+0x4943
14> OraOCIEI!dbgfcsIlcsRegister+0x2E51
15> OraOCIEI!dbgePostErrorDirect+0x11FB
16> OraOCIEI!dbgePostErrorDirect+0x2D3
17> OraOCIEI!kpeDbgHdlPostop+0x1C90
18> OraOCIEI!slgetohorabaseconfig+0x598E
19> KERNELBASE!UnhandledExceptionFilter+0x1BC
20> ntdll!memset+0x1C40
21> ntdll!_C_specific_handler+0x96
22> ntdll!_chkstk+0x11F
23> ntdll!RtlWalkFrameChain+0x14BF
24> ntdll!RtlRaiseException+0x316
25> KERNELBASE!RaiseException+0x69
26> OraOCIEI!slgetohorabaseconfig+0x5B1E
27> ucrtbase!raise+0x1DD
28> ucrtbase!abort+0x31
29> ucrtbase!terminate+0x1F
30> VCRUNTIME140_1+0x1911
31> VCRUNTIME140_1+0x218F
32> VCRUNTIME140_1+0x21E9
33> VCRUNTIME140_1!_CxxFrameHandler4+0xA9
34> ntdll!_chkstk+0x11F
35> ntdll!RtlWalkFrameChain+0x14BF
36> ntdll!RtlRaiseException+0x316
37> KERNELBASE!RaiseException+0x69
38> VCRUNTIME140!CxxThrowException+0x97
39> sim_core_12!sim::core::solver::restart+0x3351
40> sim_core_12!sim::core::solver_t::operator()+0x45
41> Powel_Mesh_Server!volue::mesh::grpc::datatransfer::v1alpha::ExportTimeseriesRequest::query_ids+0x1B473
42> Powel_Mesh_Server!volue::mesh::grpc::datatransfer::v1alpha::ExportTimeseriesRequest::query_ids+0x1CD65
43> Powel_Mesh_Server!volue::mesh::grpc::datatransfer::v1alpha::ExportTimeseriesRequest::query_ids+0x180D5
44> Powel_Mesh_Server!??$CreateMaybeMessage@VRollbackResponse@v1alpha@session@grpc@mesh@volue@@$$V@Arena@protobuf@google@@CAPEAVRollbackResponse@v1alpha@session@grpc@mesh@volue@@PEAV012@@Z+0x4ECBF
45> Powel_Mesh_Server!??$CreateMaybeMessage@VRollbackResponse@v1alpha@session@grpc@mesh@volue@@$$V@Arena@protobuf@google@@CAPEAVRollbackResponse@v1alpha@session@grpc@mesh@volue@@PEAV012@@Z+0x50B03
46> ucrtbase!o_exp+0x5A
47> KERNEL32!BaseThreadInitThunk+0x14
48> ntdll!RtlUserThreadStart+0x21
2024-10-07 12:28:13,536 - __main__ - ERROR - MainThread - Failed to run inflow calculation for Otra:
<_MultiThreadedRendezvous of RPC that terminated with:
        status = StatusCode.UNAVAILABLE
        details = "IOCP/Socket: Connection reset (An existing connection was forcibly closed by the remote host.
 -- 10054)"
        debug_error_string = "UNKNOWN:Error received from peer ipv4:<IP_ADDRESS>:50051 {grpc_message:"IOCP/Socket: Connection reset (An existing connection was forcibly closed by the remote host.\r\n -- 10054)", grpc_status:14, created_time:"2024-10-07T10:28:13.5242622+00:00"}"
>
Traceback (most recent call last):
  File "C:\Users\103281\repos\nwb_model/src/scheduledrun.py", line 75, in start_nwb_run
    for response in session.run_inflow_calculation(
  File "c:\Users\103281\repos\nwb_model\src\.env\Lib\site-packages\volue\mesh\_connection.py", line 499, in run_inflow_calculation
    for response in self.hydsim_service.RunInflowCalculation(request):
  File "c:\Users\103281\repos\nwb_model\src\.env\Lib\site-packages\grpc\_channel.py", line 543, in __next__
    return self._next()
           ^^^^^^^^^^^^
  File "c:\Users\103281\repos\nwb_model\src\.env\Lib\site-packages\grpc\_channel.py", line 969, in _next
    raise self
grpc._channel._MultiThreadedRendezvous: <_MultiThreadedRendezvous of RPC that terminated with:
        status = StatusCode.UNAVAILABLE
        details = "IOCP/Socket: Connection reset (An existing connection was forcibly closed by the remote host.
 -- 10054)"
        debug_error_string = "UNKNOWN:Error received from peer ipv4:<IP_ADDRESS>:50051 {grpc_message:"IOCP/Socket: Connection reset (An existing connection was forcibly closed by the remote host.\r\n -- 10054)", grpc_status:14, created_time:"2024-10-07T10:28:13.5242622+00:00"}"
>
2024-10-07 12:28:33,573 - __main__ - ERROR - MainThread - An error occurred: <_InactiveRpcError of RPC that terminated with:
        status = StatusCode.UNAVAILABLE
        details = "failed to connect to all addresses; last error: UNKNOWN: ipv4:<IP_ADDRESS>:50051: tcp handshaker shutdown"
        debug_error_string = "UNKNOWN:Error received from peer  {grpc_message:"failed to connect to all addresses; last error: UNKNOWN: ipv4:<IP_ADDRESS>:50051: tcp handshaker shutdown", grpc_status:14, created_time:"2024-10-07T10:28:33.5607869+00:00"}"
>
Traceback (most recent call last):
  File "C:\Users\103281\repos\nwb_model/src/scheduledrun.py", line 147, in <module>
    main()
  File "C:\Users\103281\repos\nwb_model/src/scheduledrun.py", line 135, in main
    start_nwb_run(development=development, watercourses=watercourses, comment=args.comment)
  File "C:\Users\103281\repos\nwb_model/src/scheduledrun.py", line 54, in start_nwb_run
    with mesh_client.mesh_connection.create_session() as session:
  File "c:\Users\103281\repos\nwb_model\src\.env\Lib\site-packages\volue\mesh\_connection.py", line 99, in __exit__
    self.close()
  File "c:\Users\103281\repos\nwb_model\src\.env\Lib\site-packages\volue\mesh\_connection.py", line 130, in close
    self.session_service.EndSession(_to_proto_guid(self.session_id))
  File "c:\Users\103281\repos\nwb_model\src\.env\Lib\site-packages\grpc\_channel.py", line 1181, in __call__
    return _end_unary_response_blocking(state, call, False, None)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "c:\Users\103281\repos\nwb_model\src\.env\Lib\site-packages\grpc\_channel.py", line 1006, in _end_unary_response_blocking
    raise _InactiveRpcError(state)  # pytype: disable=not-instantiable
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
        status = StatusCode.UNAVAILABLE
        details = "failed to connect to all addresses; last error: UNKNOWN: ipv4:<IP_ADDRESS>:50051: tcp handshaker shutdown"
        debug_error_string = "UNKNOWN:Error received from peer  {grpc_message:"failed to connect to all addresses; last error: UNKNOWN: ipv4:<IP_ADDRESS>:50051: tcp handshaker shutdown", grpc_status:14, created_time:"2024-10-07T10:28:33.5607869+00:00"}"
>
2024-10-07 12:28:33,578 - opentelemetry.attributes - WARNING - MainThread - Invalid type _RPCState for attribute 'exception.message' value. Expected one of ['bool', 'str', 'bytes', 'int', 'float'] or a sequence of those types

Is seems like the calculation is going fine, and crashes in the end.
Other runs with other watercourses works as expected with the exact same command. Also, this command with the same watercourse worked fine until this two days ago. (It started failing on saturday around 17:00 CET (we run in dev environment every hour)).
log messages leading up to the error (excluding debug - let me know if you need):
2024-10-07 12:28:07,443 - __main__ - INFO - MainThread - [nwb] Starting historical inflow calculation for watercourse Otra from area Norge in session {ABD61246-AB0F-4842-8457-2C17F0DC8AB8}
2024-10-07 12:28:07,448 - __main__ - INFO - MainThread - [nwb] HydSim version 12.8.0-1 for session:{ABD61246-AB0F-4842-8457-2C17F0DC8AB8} area:Norge watercourse:Otra
2024-10-07 12:28:07,449 - __main__ - INFO - MainThread - [nwb] Time interval [2024-09-07 10:28, 2024-10-07 10:28) resolution 01:00 for session:{ABD61246-AB0F-4842-8457-2C17F0DC8AB8} area:Norge watercourse:Otra
2024-10-07 12:28:07,519 - __main__ - INFO - MainThread - [nwb] Found 1 topology invariant intervals for session:{ABD61246-AB0F-4842-8457-2C17F0DC8AB8} area:Norge watercourse:Otra
2024-10-07 12:28:07,612 - __main__ - INFO - MainThread - [nwb] Loaded models for 1 topology invariant intervals for session:{ABD61246-AB0F-4842-8457-2C17F0DC8AB8} area:Norge watercourse:Otra in cpu-user:156ms cpu-kernel:0ms
2024-10-07 12:28:07,613 - __main__ - INFO - MainThread - [nwb] Calculating topology invariant interval [2024-09-07 10:28, 2024-10-07 10:28) for session:{ABD61246-AB0F-4842-8457-2C17F0DC8AB8} area:Norge watercourse:Otra
2024-10-07 12:28:08,999 - __main__ - WARNING - MainThread - [hyd-core] Missing values for b_Beihølen_Venneslafjorden L3, with id d376958a-a93d-4c89-8c54-82408dc40de9, and symbol symbol-resource_gate_38-flow
2024-10-07 12:28:09,121 - __main__ - WARNING - MainThread - [hyd-core] Missing values for b_Nomeland_dam_Beihølen L3, with id c5ead456-e840-4a86-822a-655decca6048, and symbol symbol-resource_gate_50-flow
2024-10-07 12:28:09,306 - __main__ - WARNING - MainThread - [hyd-core] Missing values for b_Inntak_Fennefoss_Kilefjorden L2, with id 00e156bf-4d93-4b68-b8b6-f1c275c68dc8, and symbol symbol-resource_gate_74-flow
2024-10-07 12:28:09,306 - __main__ - WARNING - MainThread - [hyd-core] Missing values for b_Inntak_Fennefoss_Kilefjorden L4, with id b237ab25-e56d-4097-94cf-d46521cfd512, and symbol symbol-resource_gate_75-flow
2024-10-07 12:28:09,306 - __main__ - WARNING - MainThread - [hyd-core] Missing values for b_Inntak_Fennefoss_Kilefjorden L1, with id 79fe7f13-42a7-4acf-8e33-6560bdcc82db, and symbol symbol-resource_gate_76-flow
2024-10-07 12:28:09,306 - __main__ - WARNING - MainThread - [hyd-core] Missing values for b_Inntak_Fennefoss_Kilefjorden L3, with id f4851207-42dc-4eec-9c50-155101962d1c, and symbol symbol-resource_gate_77-flow
2024-10-07 12:28:09,337 - __main__ - WARNING - MainThread - [hyd-core] Missing values for w_Ormsavatn_Vatnedalsvatn L1, with id fb662454-d79b-4d49-9e44-c553db7f258d, and symbol symbol-resource_gate_88-flow
2024-10-07 12:28:09,739 - __main__ - INFO - MainThread - [nwb] Read flow input for session:{ABD61246-AB0F-4842-8457-2C17F0DC8AB8} area:Norge watercourse:Otra in cpu-user:1516ms cpu-kernel:62ms
2024-10-07 12:28:09,987 - __main__ - INFO - MainThread - [nwb] Computed small scheduled input for session:{ABD61246-AB0F-4842-8457-2C17F0DC8AB8} area:Norge watercourse:Otra in cpu-user:250ms cpu-kernel:0ms

I see there are some warnings. However, I see the same warnings in other watercourses that don't crash like this.

Hi!
As I understand this error causes mesh crash?
If so could you provide mesh process core dump? Could you also provide us with Mesh log file?
Also if this is mesh crash I'd suggest filing issue against Mesh and providing all requested information in that issue rather than in this Public repo.

Hi!
As I understand this error causes mesh crash? In this case I'd suggest filing (through proper channels) issue against Mesh and providing additional information in that issue rather than in this Public repo:
Could you provide mesh process core dump? Could you also provide us with Mesh log file?

No, Mesh does not crash. Or, at least not the whole server.
Do you mean a server crash, or that the crash is on the Mesh side of things, so its not really a Python SDK issue?

No, Mesh does not crash. Or, at least not the whole server. Do you mean a server crash, or that the crash is on the Mesh side of things, so its not really a Python SDK issue?

I believe that the problem is on the Mesh side. Not sure yet what exactly is the problem though.

Okay, thanks, will open an issue in proper channels


Add apple_preprocessed_plist rule

This is necessary before we can add an app example using the default
Info.plist from Xcode when you start a new project.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: thii:x: ChristopherRogersYou have signed the CLA already but the status is still pending? Let us recheck it.


New Azure CosmosDB Emulator v2.14.17 published?  Now signature verification fails. ⚠ A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider

New Azure CosmosDB Emulator v2.14.17 published?  Now signature verification fails.
Get-AuthenticodeSignature -FilePath "$env:USERPROFILE\Downloads\azure-cosmosdb-emulator-2.14.17-ae439f25.msi"

SignerCertificate      : [Subject]
                           CN=Microsoft Azure Code Sign

                         [Issuer]
                           CN=AME CS CA 01, DC=AME, DC=GBL

                         [Serial Number]
                           36000001DF73819716BE32FD0D0002000001DF

                         [Not Before]
                           1/19/2024 5:33:44 PM

                         [Not After]
                           1/18/2025 5:33:44 PM

                         [Thumbprint]
                           1226440E939A24EB202C2A517CE13F8326EFDE60

TimeStamperCertificate : [Subject]
                           CN=Microsoft Time-Stamp Service, OU=nShield TSS ESN:7F00-05E0-D947, OU=Microsoft America Operations, O=Microsoft Corporation, L=Redmond, S=Washington, C=US

                         [Issuer]
                           CN=Microsoft Time-Stamp PCA 2010, O=Microsoft Corporation, L=Redmond, S=Washington, C=US

                         [Serial Number]
                           33000001F02A7C1D593BE61FAD0001000001F0

                         [Not Before]
                           12/6/2023 10:45:51 AM

                         [Not After]
                           3/5/2025 10:45:51 AM

                         [Thumbprint]
                           C228064A2AFE65B1D0B6CA8306298890CBBF69FF

Status                 : UnknownError
StatusMessage          : A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider
Path                   : $env:USERPROFILE\Downloads\azure-cosmosdb-emulator-2.14.17-ae439f25.msi
SignatureType          : Authenticode
IsOSBinary             : False

Comparing with previous version, Certification path 2.14.16 --> 2.14.17
Microsoft Root Certificate Authority 2011 --> ameroot
    Microsoft Code Signing PCA 2011 --> AME CS CA 01
        Microsoft Corporation --> Microsoft Azure Code Sign

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 5fdb4950-6ebf-979a-ec1d-8edf7858db71
Version Independent ID: 46e9cb49-6b34-e355-b552-9b293c38814c
Content: Release notes for the Windows (local) emulator - Azure Cosmos DB
Content Source: articles/cosmos-db/emulator-release-notes.md
Service: cosmos-db
GitHub Login: @sajeetharan
Microsoft Alias: sasinnat

@aluty
Thanks for your feedback! We will investigate and update as appropriate.

@aluty
Thank you for your feedback!
I'd recommend working closer with our support team via an [Azure support request] (https://docs.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request). Or you can leverage our Q&A forum by posting your issue there so our community, and MVPs can further assist you in troubleshooting this issue or finding potential workarounds.
[Teams Q&A forum] (https://docs.microsoft.com/en-us/answers/topics/46488/office-teams-windows-itpro.html) for technical questions about the configuration and administration of Microsoft Teams on Windows.
[Microsoft Teams Community forum] (https://answers.microsoft.com/en-us/msteams/forum?sort=LastReplyDate&dir=Desc&tab=All&status=all&mod=&modAge=&advFil=&postedAfter=&postedBefore=&threadType=All&isFilterExpanded=false&page=1)
Thank you for your time and patience throughout this issue.

Verified signing fixed in version 2.14.18
Get-AuthenticodeSignature -FilePath "$env:USERPROFILE\Downloads\azure-cosmosdb-emulator-2.14.18-e2d1bbf7.msi" | Format-Table -AutoSize

SignerCertificate                        Status Path
-----------------                        ------ ----
C2048FB509F1C37A8C3E9EC6648118458AA01780 Valid  azure-cosmosdb-emulator-2.14.18-e2d1bbf7.msi


TypeError: Cannot read property 'renderer' of undefined

https://github.com/handsontable/react-handsontable/blob/78848f87cf0253273a51ba54560550fbeeb3fc1c/src/hotTable.tsx#L375
columns in HotTable settings are defined as function:
columns: index => {
return {
renderer: hotTable.textRender
}
}

Hi @sbzmpa
Please create a demo or/and bug scenario.

How exactly can I do that?

Here https://jsfiddle.net/y62jar1c/ is a React for Handsontable example. Please fill the settings that you use. You do not need to paste everything - just the settings that are needed to replicate the issue.
Once you get everything done you click fork button

in the result you get a new dedicated link that you can share.

We have several deployments of application that uses Handsontable. Only one of them gives that error:
Handsontable.js:44 TypeError: Cannot read property 'renderer' of undefined
at t.value (react-handsontable.js:950)
at t.value (react-handsontable.js:1056)
at react-dom.production.min.js:6321
at t.unstable_runWithPriority (scheduler.production.min.js:266)
at qo (react-dom.production.min.js:2794)
at xl (react-dom.production.min.js:6105)
at gl (react-dom.production.min.js:5408)
at react-dom.production.min.js:2829
at t.unstable_runWithPriority (scheduler.production.min.js:266)
at qo (react-dom.production.min.js:2794)

That should make the case easier. What do you use in that single table that differs from the rest (working examples)? A renderer is used along the way in all processes and by all plugins so I'd need to know more about the bug scenario.

All deployments have the same source code and we haven't localized the problem yet. The hypothesis is - usage of different versions of Handsontable and/or react-handsontable.
I'll get back with details if I find something or if I would be able to reproduce the bug in jsfiddle.

How can I use the latest versions of Handsontable and/or react-handsontable in the fiddle you mentioned?
These

don't work.
The displayAutoSizeWarning function was created in 3.1.0 release, about 2 days ago. That's when the bugs began to appear in our deployment.

Here's fiddle with this error
https://jsfiddle.net/4tg9kcys/

Thank you for sharing the demo @sbzmpa
Sorry that I did not answer immediately but we've checked the code and moved with fixes in https://github.com/handsontable/react-handsontable/pull/142 so it shouldn't take us long to published the changes

No probs, Aleksandra! Thank you for quick response on the issue .

Hey @sbzmpa
I'm happy to announce that we've just updated the wrapper and fixed this issue. Thank you very much for sharing. We make this library better together :)

Thank you, guys!


Configuration to assist with physically close ble proxies

Hi Ashley,
Here is my downloaded diagnostics if you see anything that might need tweaking in the configuration of devices. I am finding that when I am on the couch, the proxies are flicking between the tv ble proxie and the guest bedroom proxie which is on the upper level behind a wall. I could try to move them more apart physically but thought I would send you this in case there is anything glaringly obvious to your much more expertly trained eyes!
thanks again!
config_entry-bermuda-01JBEQ9H5CGXMXCHZST3XMC8VY.json

Hi again Ashley,
Here is an updated diagnostics where I have not yet done the reinstall remedy I described on the bermuda HA page to put those devices back online. Thanks heaps.
config_entry-bermuda-01JBEQ9H5CGXMXCHZST3XMC8VY (3).json


mongodb.rb (cluster_up_to_date?): optimize

Fixes a rubocop Performance/InefficientHashSearch: Use #key? instead of #keys.include? warning
Hopefully makes #222 green

          1 Error

:no_entry_sign:
Please include a CHANGELOG entry.

  Generated by :no_entry_sign: Danger


LFX-Proposal: Cloud-edge collaborative speculative decoding for LLM based on KubeEdge-Ianvs

What type of PR is this?
/kind design

What this PR does / why we need it:
Proposal for LFX Project CNCF - KubeEdge: Cloud-Edge Speculative Decoding for LLM via KubeEdge-Ianvs
Which issue(s) this PR fixes:

Fixes #126

Got to fix the below CI errors for Pylint (3.9) before further actions, see CI logs

This is fixed by #158

I have refined the proposal.

The motivation for using the technique is not quite clear. I believe that it would make sense the improve the inference time. But the reason and potential of solving this problem could be further explored, e.g., by adding examples.

For the motivation part, I explained the necessity of improving inference speed for long-context chatbot scenario and LLM-based Agents scenario.

Need to highlight the difference against the existing design.

For the difference against Query-Routing, I add a Highlight Section and highlight the new modules in the overall architecture picture.

By the way, as an intuitive presentation, I currently tested the inference speed of Qwen2-7B-Instruct on different inference frameworks running on a single RTX 4090 GPU.
However, this is just for preliminary experimentation. I think it would be inappropriate to include in the Proposal and am posting it here only as a preview of results.

Serving Engine
Time to First Token (s)
Internal Token Latency (s)
Throughput (tokens/s)
Speed Up

transformers
1.4382
0.0202
49.60
1.00x

vLLM
0.0676
0.0168
59.54
1.20x

EAGLE
0.1918
0.0076
131.80
2.66x

EAGLE is a speculative decoding framework, tested with draft model yuhuili/EAGLE-Qwen2-7B-Instruct.
Notice that EAGLE's inference speed is more than two times higher of  transformers, showcasing the huge potential for speculative decoding.

Good job. We see that the revised version is much improved in the proposal where the inference-time saving is discussed and the difference against the existing design is highlighted.
Nevertheless, the quantification result is not included in the proposal, and using adjectives is not enough to justify the motivation. Is there any clue, e.g., about how much improvement could be potentially provided or how fast is sufficient for an LLM query?

Thanks for the review.
Are the preliminary test results I mentioned in my previous comment what you want as quantified results? If you think it's okay, I will include them in the proposal.

I just added the following paragraph into the proposal, which showcases the practice and effects of Speculative Decoding technique in OpenAI's products.

On November 6, 2024, OpenAI introduced an innovative feature named Predicted Outputs, which is capable of accelerating GPT-4o generation by 2-4 times while maintaining accuracy. This remarkable capability is rooted in the concept of Speculative Decoding, showcasing its immense potential to enhance the inference speed of Large Language Models (LLMs).

Is this sufficient support for motivation, thereby justifying the necessity of Speculative Decoding?

/lgtm

/approve


Disable go1.3 tests for circle and upgrade to go1.4.2

This should massively speed up the unit tests. We don't really use go1.3 anymore.
Signed-off-by: Stephen J Day<EMAIL_ADDRESS>

LGTM


Issue — Release 0.9.1 fails to launch due to missing JSON

Launching Node-RED-Desktop release 0.9.1 raises the following error:

Error: schema with key or id "http://json-schema.org/draft-06/schema" already exists (line:22)

The very same flow worked fine with previous version 0.9.0 beta 2.
When performing a fresh install of Node-RED-Desktop release 0.9.1, the json node is missing.

Thank you for your reports.
This is a build problem on my mac.
I had replaced the mac binary in v0.9.1.
Please download and install the replaced one manually.
Regards,
sakazuki

Everything works fine with the new package. Thank you!


Use more efficient algorithm for rescoring good blocks after healing

Description
Right now, we use a very naive algorithm to rescore which blocks should be marked as "good" blocks, on the basis of new information, after self-healing successfully heals one or more layers:
https://github.com/spacemeshos/go-spacemesh/blob/e09b148deab77f05ceab52ae8b7495adfc5102aa/tortoise/verifying_tortoise.go#L874-L892
Basically, it rescores every block in every intervening layer, from the first healed layer up to the top layer. This is quadratic, if not worse.
This research forum thread contains ideas on how we can do this more efficiently. We should be able to achieve an algorithm that is linear in the number of healed blocks/layers.
Affected code
This issue appears in commit hash: e09b148d
Related files (optionally with line numbers): tortoise/verifying_tortoise.go

For this specific issue we don't need more efficient algorithm. With recent optimizations rerun of 4000 layers takes ~40 seconds. Most of the bottlenecks that are left are related to the number of votes that we have. So once we switch to unified content block rerun will be blazingly fast. Rescoring blocks is a part of rerun and in this particular case, we will never rescore blocks for 4000 layers, at most for 2000 in mainnet.
We may need a more efficient algorithm for the rerun, it will take around ~30minutes to rerun a mesh after it was up for a year. But this needs to be re-evaluated after the unified content block is introduced.


Update github.com/syndtr/gocapability to 66ef2aa

It adds List function which allows to get list of all supported caps

LGTM

LGTM


A issue happened when I make

my opencv version is 3.1

libippicv is part of opencv. Please make sure you installed opencv properly.

Thank you. I have resolved!


Cached - Loading of fonts ?

Is the loading of custom fonts cached ?

@luserdroid See https://github.com/chrisjenx/Calligraphy/blob/master/calligraphy/src/main/java/uk/co/chrisjenx/calligraphy/TypefaceUtils.java#L21
Technically its unneeded, as the underlying impl does its own caching.


Extracted ChunkMath from TeraMath

The goal of this PR is to prepare moving the TeraMath class to the project TeraMath, where it is needed. In the next iteration, Vector3i, Region3i, etc. can be moved there also.
I therefore split the class into general math code that stays (can be moved transparently to TeraMath later) and chunk/block-related code, which shouldn't be in a generic math library. This is now in ChunkMath.
I guess that ChunkMath is not ideal for all methods. Some should be somewhere else, but the focus here is on the TeraMath refactoring.
This PR already fixes all uses in engine and Core and supports a transition phase for modules through the @Deprecate annotation.

I just moved the code from one file to another without changing it. I'd like to deal with individual methods/documentation in a separate cleanup step. This PR is just about the split.

Merged despite pending questions based on the whole "not done yet" bit :-)
Tested around in a few worlds and didn't notice anything bad.

Understood @msteiger. I look forward to the PR where we can address those issues.


Fix pre-InstallValidate custom action conditions

What does this PR do?

Changes the conditions of our custom actions that are sequenced before InstallValidate. Since these custom actions are safe to always run, they are now configured to always run.
Motivation

According to Microsoft documentation, the REMOVE property may not be set to ALL before the InstallValidate action. We have custom actions that are sequenced before InstallValidate but were checking for this condition.
Additional Notes

https://datadoghq.atlassian.net/browse/WA-261
Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

I have two comments:

We should not apply the skip-qa label as QA is required for this PR.
Its good to add details in "Describe how to test/QA your changes" section. This just saves time gathering the details from the linked cards and clarifies expectations of what needs to be QAed in one place.


Change TitleExtension to PageContentExtension

Description
This is a major change.
Currently we have a TitleExtension which hooks up PageContent. We've talked about how this should have been changed in the early days of v4, so I've done it now before we actually get to the point of official release to avoid it being something we wish we'd done but didn't.

@Aiky30 thanks for taking a look. I've got a PR on versoning to bring support for this change. So the two can come into play together. It'll just need a plan for how best to do that.

@fsbraun So I updated the branch and resolved the conflicts, but something in that commit has destroyed the test results 😬

It seems that the merge sneaked in title_cache again:

@fsbraun Oh well spotted! That wasn't part of the conflicts either so I missed it.


refactor: metadata serializer

:white_check_mark: Build TheIdServer 4.4.1-ws-fed-metadata1-0057 completed (commit https://github.com/Aguafrommars/TheIdServer/commit/96e8d2bc38 by @)


Generate stack usage information with -fstack-usage.

Fix: #275
Generate an extra file that specifies the maximum amount of stack used, on a per-function basis.
Signed-off-by: Qi Zhang<EMAIL_ADDRESS>

Please add one section in document (https://github.com/DMTF/libspdm/blob/main/doc/test.md) on

how to collect the data.
sample output.

Question: Is there any solution in Windows/MSVC?

Do you need mention https://dlbeer.co.nz/oss/avstack.html ?

looks good

conflict resolved.


Fixed valid meshconfig error

Signed-off-by: harkiratsm<EMAIL_ADDRESS>Description
This PR fixes #5905
Notes for Reviewers
Signed commits

[ ] Yes, I signed my commits.

Codecov Report

Merging #5907 (3c31fe0) into master (07b6118) will decrease coverage by 4.34%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #5907      +/-   ##
==========================================
- Coverage   17.80%   13.45%   -4.35%
==========================================
  Files         107      107
  Lines        9994     9994
==========================================
- Hits         1779     1345     -434
- Misses       7779     8359     +580
+ Partials      436      290     -146

Flag
Coverage Δ

gointegrationtests
?

unittests
13.45% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

mesheryctl/internal/cli/root/system/update.go
1.05% <0.00%> (-58.95%)
:arrow_down:

mesheryctl/internal/cli/root/system/start.go
1.88% <0.00%> (-55.19%)
:arrow_down:

mesheryctl/internal/cli/root/system/status.go
1.14% <0.00%> (-55.18%)
:arrow_down:

mesheryctl/internal/cli/root/system/restart.go
1.92% <0.00%> (-48.08%)
:arrow_down:

mesheryctl/internal/cli/root/system/stop.go
2.00% <0.00%> (-46.67%)
:arrow_down:

mesheryctl/internal/cli/root/system/logs.go
3.26% <0.00%> (-36.96%)
:arrow_down:

mesheryctl/internal/cli/root/system/check.go
1.03% <0.00%> (-23.03%)
:arrow_down:

mesheryctl/internal/cli/root/system/dashboard.go
1.70% <0.00%> (-9.41%)
:arrow_down:

mesheryctl/pkg/utils/healthcheck.go
8.82% <0.00%> (-4.42%)
:arrow_down:

Continue to review full report at Codecov.

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

Testing the PR now...


Invalid JSON data returned for highlight.js

Help request
Problem
Highlight.js returning invalid JSON data. URL: https://api.cdnjs.com/libraries/highlight.js
Error:
SyntaxError: JSON.parse: unterminated string at line 1 column 2626990 of the JSON data
What I have tried
Tried using CURL to fetch with cache control set to no-cache and still returns the same invalid JSON.
curl -H 'Cache-Control: no-cache' https://api.cdnjs.com/libraries/highlight.js --trace-asci output.txt
output.txt

👋 I just ran curl -H 'Cache-Control: no-cache' https://api.cdnjs.com/libraries/highlight.js | jq locally (piping into jq to validate the JSON), and this is returning completely valid JSON for me.
If you could provide a full response headers dump for the invalid response, that'd be great!

HTTP/2 200
date: Tue, 17 Aug 2021 20:30:12 GMT
content-type: application/json; charset=utf-8
access-control-allow-credentials: true
access-control-allow-origin: *
cache-control: public, max-age=21600
etag: W/"3b7577-5/xK/ndRckL3O36agHf8NLOno4g"
expires: Wed, 18 Aug 2021 01:48:59 GMT
vary: Accept-Encoding
cf-cache-status: HIT
age: 2473
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=BnkHyZ%2Fvn0Ly2OB5ZhvRu4F2w25Xt0TOZWz8WFWGHYQaMcupKgwDY3%2BWf9VWdSTiYJlwGD9vgJndop%2FM%2FcxJamR5QPSLmNzvr%2FKVN1pgqymV729%2FoLSWk21umPQPpOk%3D"}],"group":"cf-nel","max_age":604800}
nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
strict-transport-security: max-age=31536000; includeSubDomains; preload
x-content-type-options: nosniff
server: cloudflare
cf-ray: 6805a8b26c49f1c2-ATL

Thanks -- the team are looking into it!

Hi @theit8514,
It looks like for some reason a bad response was in a cache somewhere -- we've purged the cache, so hopefully, all should be good now! Could you check and confirm?
We've verified the responses from the API origin servers directly, as well as through the public API URL above and we can no longer reproduce the issue on our end.

Yes, that has fixed the issue for me as well. Thanks.


Secure rest endpoints

Branch: https://github.com/prperiscal/general-purpose-user-service/tree/feat/include-security


Support package Manager Conan

Maybe sol2 will support the package Manager from the conan ?

sol2 comes with CMake support. It's also a header only library. I don't know what else I need to do to support Conan.

If there's a recipe for a conan . The ability to add sol2 support in one line in the file will be very cool

Someone talked about making one or made one, but I don't keep up to date with the latest build systems and package managers, sorry!

Maybe it'll help . https://conan.io/

https://github.com/bincrafters/conan-templates

I think if there's a person who wants to do it, they can make a bincrafters repo and we can link it in this repo.

Yeah this looks like a lot of work for something I have no intention of using ever...
Pull requests welcome, until I one day decide that sinking myself into Yet Another Crappy Build And Package System is worth the effort.

I will write the conan recipe, it is not difficult at all if you know the tool.

Bless your soul 🙏

Sorry for such a terrible delay on this, I am working on this now

@Lnk2past Just make sure when you work on it, you do the work relative to the sol3 branch!

@ThePhD Sure thing. The conanfile.py will live on the sol3 branch, but for starters it will point to the 2.20.5 release. Once I create that release, I will move to update it to produce a "git-develop" release from the sol3 branch.
I have a question though about naming/versioning: is the idea that sol3 will be the name of a new product? Or is that just the "codename" for the sol2-v3.0.0 release? Just trying to wrap my head around how to name these releases/repositories.
As far as what the package contains, to begin I am going to have it capture only the headers (and not try to do anything with CMake up front) and it will by default grab the sol directory, with an option to grab the single directory instead. If you would like the default to be single let me know. Obviously in sol3 this would change to point to the include directory instead.

I would greatly prefer you point to the proper sol3 directories first (and encourage sol3 use); it's stable and ready for production use. (Just lacking in docs, bwuh.)
sol3 is the "next" version of sol2. They should all be called "sol2" in repositories, mostly because other people probably will want to take the name "sol" and I don't want to be in that sandwich. I use sol3 as a convenient shorthand for sol2-v3.0.0, and as M A R K E T I N G H Y P E .

Gotcha, I will point from the sol3 branch and get things started with a 3.0.0-unstable (or -dev, or -whatever you really want to suffix it with) version. I should have everything ready in the next few days.
Though I'll get everything setup, it should probably be you, being the owner/author and all, that pulls the trigger on getting everything officially uploaded/owning the deployment repositories. This would mostly be a one-time thing for you to setup, as I am also adding in the hooks to deploy automatically via TravisCI (or AppVeyor, if you prefer). When I have everything ready I can provide you with the detailed instructions to make sure that everything is pushed properly.

We should already have Travis and Appveyor running. The sol3 builds are now clean, as far as those 2 CI systems are concerned.

Yea, I saw both, so I was not sure if you wanted to deploy through one or the other. Whenever you tag a release Travis (or AppVeyor) would pump that release over to bintray, that way you do not have to manually do it every time.

Ooooh, that's what you mean.
Yeah, do whatever makes you happy. I'm not the expert with these things. :D

Is it possible to build support for a stable branch too? @Lnk2past

The stable branch has been cannibalized by sol3.

@ThePhD Support for version 2 will not be ?

No. I have no intention of supporting multiple versions of a thing I am not paid for. That being said, sol2's latest v2.x.x are still all freely available and still work fairly well with C++14, but I'm not going to be working on adding any features to it.

Recipe for Canon made.
It started with the version of sol2 2.20.6.
I will be happy to suggestions for improvement.
https://github.com/jinncrafters/conan-sol2

@kotbegemot Hey, thanks for the first draft! I haven't had time to look, but maybe soon.

I will try to add the latest version of the library soon .

Tested it on Ubuntu and seems to work! Thank you!

I just tested it on Ubuntu and it only works if I'm also including/linking the Lua library, otherwise linking fails with "undefined reference" to the various Lua functions. Otherwise, works great, thank you.

The issue I believe is that sol has a dependency on the lua library, but the recipe doesn't include that dependency. However, I don't think there is an official conan recipe for lua, so it may be a loss cause doing more than just saying "you need to provide lua yourself".

I just create a PR for the conan index center so that the package will just exist in future via conan
https://github.com/conan-io/conan-center-index/pull/1220
I used version 3.0.3 since it was not obvious to me if 3.2.0 is an official release, I think the lastest stable label is at 3.0.3
it usually takes some tweaks and a few days until such PRs are accepted,
please review and add a comment if you see something to improve.

Use head. All the time. Literally, pull from the latest. Never from a tagged version. If it requires a tagged version, let me know so I can start slapping tiny minor revision tags on everything.
But please, always live at head.

always from head is not doable for this kind of packaging,
There are many situations where you need to have the same version no matter if I build today, or tomorrow, a package. The outcome must be the same. Therefore the source must be the same, and a checksum for the source must be stored somewhere (else).
And for this a download link is needed. And sem versioning for some other checks, because git shas sort so bad.
And I know the talk from Titus, yes, but there are other industries and scenarios also ;-)

sol2 is now available via conan center :-)
https://github.com/conan-io/conan-center-index/commit/79541efd967e9a07704a96f63444681c3dbfaaf7
and
https://conan.io/center/sol2/3.0.3/?user=_&channel=_
next step is to add the last 2.x release for those who are pinned to c++14,
and then the 3.2 release
(there can only be one version update per PR)
after this I hope there will be regularly tagged versions of sol2 so the recipe can be updated from time to time to the latest and greatest sol2 experience :-)  but this is up to @ThePhD to decide

I'll absolutely help put out tagged releases to help with this. Thank you so much!

I think you can close this now :-)
the latest 2.x for C++14 apps, and 3.2 are now at conan
https://github.com/conan-io/conan-center-index/tree/master/recipes/sol2
if nothing changes in the build logic with CMake, adding new versions is as easy as adding the URL and the checksum in this file (and therefore tags are needed ;-)
https://github.com/conan-io/conan-center-index/blob/master/recipes/sol2/3.x.x/conandata.yml

WOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO! 🎉


Each CullerRenderer creates a new WebGL context

Describe the bug 📝
Each CullerRenderer uses one WebGL context. Browsers have hard limits to the number of contexts available (typically 16). This means that an application may only have 16 Cullers at the same time. This becomes a limiting factor in cases we have more than one viewport in a scene.
When the WebGL context limit has been reached, the browser will remove older WebGL contexts to keep within the hard limit. This will lead to the application using CullerRenderer breaking down or misbehaving.
Reproduction ▶
No response
Steps to reproduce 🔢
No response
System Info 💻
System:
    OS: macOS 14.4.1
    CPU: (10) arm64 Apple M1 Pro
    Memory: 92.77 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.14.0 - /opt/homebrew/opt/node@18/bin/node
    npm: 9.3.1 - /opt/homebrew/opt/node@18/bin/npm
  Browsers:
    Chrome: 127.0.6533.90
    Edge: 127.0.2651.86
    Safari: 17.4.1

Used Package Manager 📦
npm
Error Trace/Logs 📃
No response
Validations ✅

[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a repository issue and not a framework-specific issue. For example, if it's a THREE.js related bug, it should likely be reported to mrdoob/threejs instead.
[X] Check that this is a concrete bug. For Q&A join our Community.
[X] The provided reproduction is a minimal reproducible example of the bug.

@onderilkesever what solution would you suggest?

Couple suggestions;

@agviegas thanks for quick response. Maybe single renderer can be used for all cullers, but you need to reset it all the time before rendering off screen so i am not sure about the performance.

@onderilkesever we could do that, but the problem is that sharing the same renderer among many cullers might result in the cullers queueing to use it, damaging the experience.
If three.js can't support more than simultaneous 16 renderers, I'd stick with that limit for our library as well for now. Regarding disposing:

it will fail the next time when trying to create new one.

I just tried this, and it works perfectly. Did you try this on your end? It seems like you can create and dispose as many cullers as you want:
const cullers = components.get(OBC.Cullers);
let culler = cullers.create(world);
for (let i = 0; i < 100; i++) {
  culler.dispose();
  culler = cullers.create(world);
}

If three.js can't support more than 16 simultaneous renderers, I'd stick with that limit for our library as well for now.
It is not the three js what is limiting that number, it's the browsers..

I just tried this, and it works perfectly. Did you try this on your end? It seems like you can create and dispose as many cullers as you want:
I have tried and unfortunately it did not work for me. might be related to that you simply create and dispose, can you maybe simulate real life example e.g add meshes to cullers, update etc. because i think whats eventually not releasing the webgl contexts is that some resources have still been referenced from somewhere, and that leads my garbage collection to not collect those context.

@onderilkesever I was able to reproduce the issue with this code:
const cullers = components.get(OBC.Cullers);
let culler = cullers.create(world);

let counter = 0;
async function disposeCullerRecursive() {
  if (culler) {
    cullers.delete(world);
  }

  culler = cullers.create(world);
  culler.enabled = true;

  for (const fragment of model.items) {
    culler.add(fragment.mesh);
  }

  culler.onViewUpdated.add(() => {
    if (counter < 100) {
      console.log(counter++);
      disposeCullerRecursive();
    }
  });

  culler.updateVisibility(true);
}

await disposeCullerRecursive();

https://github.com/user-attachments/assets/c22def93-8147-464b-a2e3-f38e1dfbbf2d
I discovered that Three.js has a way to force the release of the context. Applying it to the culler renderer solves the problem:
https://github.com/user-attachments/assets/df297108-8b5c-4ab8-ba38-cc1f99bca955
I've addeed this everywhere in our library where we dispose a renderer, so this should solve the issue for disposing.
For having more than 16 active renderers, I don't think we can do anything for now, as any solution would reduce the performance and/or flexibility of the culler. If this becomes a major issue for the community, we'll see if we can find a solution.
This fix is available from<EMAIL_ADDRESS>and<EMAIL_ADDRESS>Let me know if you still face the issue.

Thanks for the support here @agviegas !


BACKPORT: Add additional debug information to cgroup writes

@runcom @rhatdan PTAL
Signed-off-by: Mrunal Patel<EMAIL_ADDRESS>

LGTM

:+1:

@mrunalp @rhatdan shall we get this in if we're going to have another docker 1.9 release in RHEL?

Yeah, it will be good to have.

I think this won't hurt and will be helpful in case we'll ship a docker 1.9 in RHEL so merging

Make sure if we build a new docker-1.9 in RHEL we do  it with golang < 1.6 or we  add the /run/docker.sock patch.  I am pretty sure kubernetes might be looking to build with golang 1.6 soon.

ack - I think RHEL won't have go1.6 for some time so docker-1.9 will be built with go < 1.6 hopefully


./apollo.sh build_no_perception dbg --> build msf_localization failed

apollo@in_dev_docker:/apollo$ ./apollo.sh build_no_perception dbg
System check passed. Build continue ...
[WARNING] ESD CAN library supplied by ESD Electronics does not exist. If you need ESD CAN, please refer to third_party/can_card_library/esd_can/README.md.
[INFO] Start building, please wait ...
[INFO] Skip building perception module!
INFO: Reading 'startup' options from /apollo/tools/bazel.rc: --batch_cpu_scheduling
[INFO] Building on x86_64...
INFO: Reading 'startup' options from /apollo/tools/bazel.rc: --batch_cpu_scheduling
ERROR: /apollo/modules/localization/msf/BUILD:5:1: no such package '@local_integ//': Expected directory at /usr/local/apollo/local_integ but it does not exist. and referenced by '//modules/localization/msf:msf_localization'
ERROR: Analysis of target '//modules/localization/msf:msf_localization' failed; build aborted
INFO: Elapsed time: 6.276s
FAILED: Build did NOT complete successfully (5 packages loaded)
currently loading: @bazel_tools//tools/test
[ERROR] Build failed!
[INFO] Took 10 seconds

root error:
apollo@in_dev_docker:/apollo/modules/localization$ bazel build :localization_lib
INFO: Reading 'startup' options from /apollo/tools/bazel.rc: --batch_cpu_scheduling
INFO: Analysed target //modules/localization:localization_lib (0 packages loaded).
INFO: Found 1 target...
ERROR: /apollo/modules/localization/BUILD:23:1: C++ compilation of rule '//modules/localization:localization_lib' failed (Exit 1)
In file included from modules/localization/localization.cc:23:0:
./modules/localization/msf/msf_localization.h:42:40: fatal error: include/localization_integ.h: No such file or directory
#include "include/localization_integ.h"
^
compilation terminated.
Target //modules/localization:localization_lib failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 8.728s, Critical Path: 7.01s
FAILED: Build did NOT complete successfully

This command "./apollo.sh build_no_perception dbg" works well on my computor. Does the folder path "/usr/local/apollo/local_integ" exist? If it doesn't exist, maybe you should update the docker environment by "./docker/scripts/dev_start.sh".

Closing this issue as there has been no communication for a while. Feel free to open it up if you have additional questions.


outdated

https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/aha-tutorial#configure-azure-ad-single-sign-on
#1 in this section has instructions to select something that doesn't exist in the Azure Portal anymore.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: f04661cf-b570-9ac7-028b-22f3e28e145d
Version Independent ID: 32744020-62e8-8720-019f-eceae04a509e
Content: Tutorial: Azure Active Directory integration with Aha!
Content Source: articles/active-directory/saas-apps/aha-tutorial.md
Service: azure-active-directory
GitHub Login: @jeevansd
Microsoft Alias: jeedes

Single sign-on option is still available and even in the same order as in the documentation

@kplantus If you add the new application from the gallery then you will see this view. If you have already enabled SSO for the app then you can see the button on the top of the page change the SSO mode and when you click on that then you will see this UI.

#please-close


Doesn't play nice with aws-assume-role

I see since version 2.0.0 this ECR plugin hooks into the step lifecycle at the environment stage. This breaks the integration with the cultureamp/aws-assume-role plugin.
To be specific we have many build steps that follow this pattern:
    plugins:
      - cultureamp/aws-assume-role#v0.1.0:
          role: "arn:aws:iam::$AWS_ACCOUNT_ID:role/$AWS_ROLE"
      - ecr#v1.2.0:
          login: true
          account_ids: "$AWS_ACCOUNT_ID"
      - docker-compose#v2.5.1:
          …

First the aws-assume-role plugin will assume a role that has access to the AWS ECR. Then the ecr plugin will log in and gain access to the ECR. Later the docker-compose plugin will pull and push to the ECR.
This pipeline fails when the ecr plugin is upgraded to version 2.0.0: the docker-compose plugin is refused access to the ECR. As the ecr plugin now runs at the environment phase it always runs before the aws-assume-role plugin, which runs at the pre-command phase, thus breaking the authorisation.
There's not much information shared in #26 to describe the reason or benefit in this change.

Sorry this broke things for you @orien! The change in #26 was so that ECR could be used in the pre-command hook, which was a common request.
Let's reach out to the folks at CultureAmp and see if we can get them to make the same change.

I have the exact same problem 😭 ....

From what I can tell this is fixed as of https://github.com/cultureamp/aws-assume-role-buildkite-plugin/pull/10
If anyone is still having issues don’t hesitate to comment and we’ll take a look!

Unfortunately not, cultureamp/aws-assume-role-buildkite-plugin#10 was quickly reverted in cultureamp/aws-assume-role-buildkite-plugin#11. 😞
However, we've been using a fork at envato/aws-assume-role-buildkite-plugin. This has the proposed changes accepted and tagged. This works well for us:
    plugins:
      - envato/aws-assume-role#v0.2.0-envato:
          role: "arn:aws:iam::$AWS_ACCOUNT_ID:role/$AWS_ROLE"
      - ecr#v2.3.0:
          login: true
          account_ids: "$AWS_ACCOUNT_ID"
      - docker-compose#v3.8.0:
          …

Hmm, given the tricky interactions here would something like https://github.com/buildkite-plugins/ecr-buildkite-plugin/pull/54 be a better solution?
I could also see it being useful to have a plug-in setting for whether to use any environment variable credentials, or to disregard them and use fresh IDMS/ECS credentials before assuming role to perform an ECR log-in 🤔

+1, that seems like a positive approach that will resolve multiple issues.


Support for Comments on Markup Cells in Notebooks

Hello,
This PR addresses #214332 by enhancing the notebook feature by enabling comments on markup cells, similar to the existing functionality for code cells. Changes include:

Updated the didRenderCell method to handle both Code and Markup cell types.
Ensured compatibility with existing comment infrastructure.

This enhancement improves the flexibility and usability of notebooks, allowing users to comment on all cell types.

Hello @rebornix, I have updated the code to use the initialize method for both cell types to maintain consistency and streamline the process.
Please let me know if any additional changes are required.


Please release the code about generating *.csv file for uspto_mol dataset

Thanks for your open-source and hard work.
However, when I download the upsto_mol dataset, I'm confused about how to generate *.csv for this dataset. can you release the code about generating *.csv file for uspto_mol dataset.
Thanks!

Hi,
Thank you for reaching out!
I believe the uspto_mol.zip already contains the csv file, which can be used for training.
We do not plan to release our full preprocessing script, as it involves other things such as data downloading and filtering. But I share our functions for parsing the MOL files below, which might be helpful to you. If you have other specific questions, please let me know.
def parse_mol_file(mol_file):
    with open(mol_file) as f:
        mol_data = f.read()
        superatom = [(int(i)-1, symb) for i, symb in re.findall(r'A\s+(\d+)\s+(\S+)\s', mol_data)]
        lines = mol_data.split('\n')
        coords = []
        edges = []
        for i, line in enumerate(lines):
            if line.endswith("V2000"):
                tokens = line.split()
                num_atoms = int(tokens[0])
                num_bonds = int(tokens[1])
                for atom_line in lines[i + 1:i + 1 + num_atoms]:
                    atom_tokens = atom_line.strip().split()
                    coords.append([float(atom_tokens[0]), float(atom_tokens[1])])
                for bond_line in lines[i + 1 + num_atoms:i + 1 + num_atoms + num_bonds]:
                    bond_tokens = bond_line.strip().split()
                    start, end, bond_type, stereo = [int(token) for token in bond_tokens[:4]]
                    etype = bond_type if bond_type <= 4 else 1
                    if bond_type == 1:
                        if stereo == 1:
                            etype = 5
                        if stereo == 6:
                            etype = 6
                    edges.append((start - 1, end - 1, etype))
                break
    return superatom, coords, edges

def convert_mol_to_smiles(mol_file, debug=False):
    try:
        mol = Chem.MolFromMolFile(mol_file, sanitize=False)
        smiles = Chem.MolToSmiles(mol)
        atom_order = mol.GetProp('_smilesAtomOutputOrder')
        atom_order = eval(atom_order)  # str -> List[int], since the Prop is a str
        reverse_map = np.argsort(atom_order)
        if mol.GetNumAtoms() < 3 or mol.GetNumAtoms() > 100:
            return None, None, None, None
        superatoms, coords, edges = parse_mol_file(mol_file)
        coords = np.array(coords)
        coords = coords[atom_order].tolist()
        edges = [(int(reverse_map[start]), int(reverse_map[end]), etype) for (start, end, etype) in edges]
        pseudo_smiles = smiles
        if len(superatoms) > 0:
            superatoms = {int(reverse_map[atom_idx]): symb for atom_idx, symb in superatoms}
            tokens = atomwise_tokenizer(smiles)
            atom_idx = 0
            for i, t in enumerate(tokens):
                if t.isalpha() or t[0] == '[' or t == '*':
                    if atom_idx in superatoms:
                        symb = superatoms[atom_idx]
                        tokens[i] = f"[{symb}]"
                    atom_idx += 1
            pseudo_smiles = ''.join(tokens)
        return smiles, pseudo_smiles, coords, edges
    except Exception as e:
        if debug:
            raise e
        return None, None, None, None

Thanks for your reply!

I have another question. For the upsto_mol dataset, how to ensure the correct mapping between the position of atoms in MOLFILE and the position of atoms in the image? Mapping refers to pixel-level coordinate matching

Moreover, if there are abbreviations for groups (such as CO2Et, COOEt, OiBu, nDec, nNon)in the image, how do you represent the coordinates of the groups and the relationship between the edges in this case?

Thanks!!!


in-range method is not documented

Here is the example code of what in-range method is.
$ perl6 -e 'my $range = 0..3; say $range.in-range(1);'
True
$ perl6 -e 'my $range = 0..3; say $range.in-range(4);'
Value out of range. Is: 4, should be in 0..3
  in block <unit> at -e line 1

See also:
https://github.com/rakudo/rakudo/blob/nom/src/core/Range.pm#L661-L664

This ticket gets a comment similar to the one I gave to (the original version of) #818 :  I don't know that "in-range" is properly a part of the Perl 6 language specification -- it may just be a Rakudo internals method that shouldn't be used outside of the Range class.  In particular, there are no roast tests for "in-range".
Pm

As a possible alternative, rather than not documenting the "in-range" (or "clone-with-op") method at all, they could be listed as being Rakudo internals methods not intended for use outside of Rakudo.
Pm

It's a strange one as it is only used in Date and DateTime  to check for out of bounds arguments and throw an exception.  Its basically ($range ~~ $val) || die but with an OutOfRange exception.

From the perspective of language evolution, functionality created to
overcome some limitation or is more convenient than the standard
specification, points to how the language should develop in the future.
The specification and test suite are there to create portability across
implementations. But if the methods are useful and are used by other
programmers, then they will want them to work across all compilers.
Perl6 explicitly provides for extensions. Perhaps, these methods
(internal to Rakudo) could be documented together with standard Perl6
code that does the same thing, perhaps more slowly or less elegantly.
That way, even if they are used with other implementations, it would
only be necessary to include the extra code in the set up phase, rather
than going through all the code to look for where they are used.
Good practice - of course - is only to use standard specification, but
sometimes code is generated with no intent for it to be portable, only
to find that it is more widely useful than originally intended.
Richard
On Monday, August 08, 2016 02:45 AM, Patrick R. Michaud wrote:

As a possible alternative, rather than not documenting the "in-range"
(or "clone-with-op") method at all, they could be listed as being
Rakudo internals methods not intended for use outside of Rakudo.
Pm
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/perl6/doc/issues/819#issuecomment-238100375, or
mute the thread
https://github.com/notifications/unsubscribe-auth/AAWMnCNkTEz-Hu62IFUaofSUP7bSZp7Jks5qdifagaJpZM4Jeiki.

So, uh, what does it mean?
Does it mean that we should document such things, but we should add a note that it is rakudo-specific and not part of the language?

On Sun, Aug 07, 2016 at 06:55:18PM -0700, Richard Hainsworth wrote:

From the perspective of language evolution, functionality created to
overcome some limitation or is more convenient than the standard
specification, points to how the language should develop in the future.
[...]
The specification and test suite are there to create portability across
implementations. But if the methods are useful and are used by other
programmers, then they will want them to work across all compilers.

On the other hand, sometimes (internal) methods are added to the
implementation simply as scaffolding, with the expectation that they
may be removed or refactored later.  If we treat them as being "usable"
outside of the internals -- i.e., if we document them as being supported
by the language when that's not the intent -- that's akin to a commitment
that they will exist in all sibling and future implementations or that
there will be suitable deprecation cycles prior to their removal.
I'd prefer that such methods be clearly marked as "for internal use only",
so that they don't find their way into the (de-facto) language specification
more by accident than design.
In the specific cases given by #818 and #819, my first reaction upon
seeing the tickets was "that doesn't look consistent with the rest
of Perl 6" and "that almost certainly isn't a deliberate language
design choice", which is why I've called attention to it.
Pm

Since we still don't have a way to make the transition from v6.c to v6.d, both for code and for the docs it would be ill advised to sneak internals in because they are useful. If you believe the method should be in v6.d provide a PR against roast. You can link the PR/RT here and reopen this issue. That the proper order to make sure things don't fall through the cracks.
ENOSPEC, closed

To me it sounds like using the new NOTSPECCED label is an even better way to make sure that it wont fall through the cracks.
If it some point we decide that it will never be documented, we will close it. But if at some point it is added to roast, we will not forget to write the docs. In other words, check again later!
Feel free to reclose if you think that we should not have an issue here.
That being said, maybe we should doc it: “Do not use this! It is not even an experimental feature.”. Again, if we decide that it is how we should document stuff like this, then with this new label it will be much easier to find it.

Maybe there should be a "meta-issue" to discuss where the line is drawn for un-specced items, and what the threshold for discovery of undocumented items should be.

There's a reasonable use case here. Maybe we should document it in this case. This kind if limbo it's in forces us to check from time to time...


Doc suggestion: add a glossary

I think that https://tokio.rs/docs/getting-started/tokio/ would benefit from a glossary of terms covering tokio-core, tokio-proto, tokio-service, and futures. I think a lot of the terms are already explained well in isolation on various pages, but a single page that brings all the definitions together would be helpful.

This would be great, especially something which documented all the types and their relationships, such as Codec, Dispatch, the various Protos, etcetera.

Great idea!

I moved this issue to the website repo: https://github.com/tokio-rs/website/issues/62


Implement Gifts Details Page

As a user
I need to view detailed information about available gifts
So that I can decide if I want to claim them
Details and Assumptions

Gift details should include image, description, condition, and location
The page should show the current status of the gift (available/claimed)

Acceptance Criteria
Given that I am browsing gifts
When I click on a specific gift
Then I should see all relevant details about the gift
And I should have the option to claim it if it's available


Enhance File Processing with AI Features: Improved Encoding, and Cleanup

This Pull Request enhances the file_processing.py script by integrating advanced AI features and improving overall functionality. The key updates are:

AI-Driven File Type Detection and Encoding:

Enhanced MIME Type Detection: Improved MIME type detection for files to ensure correct identification of file types, leveraging more reliable methods.
Base64 Encoding: Added functionality to encode files in Base64 format, allowing for easier transmission and embedding of files in various contexts. This includes improved handling for different MIME types.

PDF Conversion and Handling:

Automatic PDF Conversion: Implemented automatic conversion of supported files to PDF format. This enhancement ensures that files are in a universally accessible format, making them easier to share and process.
Error Handling for Conversion: Added robust error handling to manage issues during the PDF conversion process, ensuring smoother operation and better user feedback.

Advanced File Cleanup and Management:

File Cleanup Enhancements: Improved file cleanup processes to handle temporary files and directories more effectively. This includes additional safety checks to prevent accidental deletion of critical system directories.
Binary vs. Text File Detection: Enhanced the method for distinguishing between binary and text files. This helps in applying appropriate processing methods based on file type.

Integration with AI-Enhanced Clients:

Client-Side Updates: Modified the run_openai_client function to better integrate with AI-driven clients, including the ability to handle agent files and convert them as needed.
Text Context and Response Handling: Improved handling of text context and responses from the AI client, ensuring that the generated responses are accurately processed and formatted.

Improved File Name Management:

File Name Updates: Added functionality to ensure consistent file naming conventions, including renaming files with missing extensions to .txt if appropriate.

These updates collectively enhance the script's ability to process, manage, and convert files using advanced AI features, ensuring greater reliability and efficiency in handling various file types and operations.

This pull request introduces several key improvements and new AI-driven features to enhance file processing capabilities:

AI-Driven File Encoding: Added functionality to automatically convert files to base64 format, including support for MIME type detection and dynamic data URL construction. This improvement ensures compatibility with various file types and better integration with web-based applications.

Enhanced PDF Conversion: Integrated a local PDF conversion function with error handling to ensure robust processing of file conversions. This includes a fallback mechanism for handling errors during the PDF conversion process.

Advanced File Management: Improved file handling with a more comprehensive cleanup mechanism. Added functionality to rename files with missing extensions and handle errors during file operations more gracefully.

AI-Powered File Renaming: Incorporated a new mechanism for automatically renaming files with missing extensions based on their content, leveraging AI to determine appropriate file types and enhance file management.

Improved Error Handling: Added detailed error messages and enhanced error handling throughout the script to improve robustness and debugging capabilities.

Base64 Encoding for Agent Files: Provided an option to base64 encode files obtained from agents, with improved handling for file paths and names.