Undefined index when persisting

Error I get when I try to load the fixtures:
[Symfony\Component\Debug\Exception\ContextErrorException]
  Notice: Undefined index:<PHONE_NUMBER>5aab41000000017e09a5d6

hidden\hidden\CoreBundle\Entity\Userhidden:
    superadmin_hidden:
        hiddenFonction: "NA"
        hiddenMatricule: "NA"
        hiddenInsee: "NA"
        hiddenPilotage: 0
        user: @superadmin

hidden\hidden\CoreBundle\Entity\User:
    superadmin:
        username: admin
        email: <email()>
        enabled: 1
        plainPassword: admin
        firstname: hidden
        lastname: hidden
        roles: [ROLE_SUPER_ADMIN]

Userhidden entity:
hiddenFonction, hiddenMatricule, hiddenInsee and hiddenPilotage are string/integer columns.
....

/**
 * @var \User
 *
 * @ORM\Id
 * @ORM\GeneratedValue(strategy="NONE")
 * @ORM\OneToOne(targetEntity="User")
 * @ORM\JoinColumns({
 *   @ORM\JoinColumn(name="user_id", referencedColumnName="id")
 * })
 */
private $user;

UserHidden has a relation to User but the column is also the primary. I guess that's the problem.

Err not really sure, looks more like a Doctrine or Alice error to me, but I must say I find it weird to have a User as an id.

Ok, thanks for your answer. The database was made by a DBA and I'm not allowed to edit it. Symfony2 doesn't like such relations, this is not the first issue I had with.

Well, I'm no database expert and I don't know what kind of database you're using, but yeah chances are high that Doctrine doesn't like it (Symfony should not have any problem with that thought).

Yes I meant Doctrine doesn't like it. This issue can be close because it's related to my configuration. Thanks for your answers.


Misspeling in release note

Page not found (404)

Now you see our shadowy private repo. Fixed, thanks!


Credhub set using CLI > 2.0.0 fails to save values to server 2.0.2

What version of the credhub server you are using?
2.0.2
What version of the credhub cli you are using?
2.0.1
2.1.0
If you were attempting to accomplish a task, what was it you were attempting to do?
Save a value
credhub s -n /foo -t value -v bar
What did you expect to happen?
Save the value
What was the actual behavior?
CLI 2.0.1 and 2.1.0 send invalid parameter "mode". CLI 2.0.0 writes successfully.
[DEBUG] PUT /api/v1/data HTTP/1.1
Host: <IP_ADDRESS>:8844
User-Agent: Go-http-client/1.1
Content-Length: 63
Content-Type: application/json
Accept-Encoding: gzip

{"mode":"overwrite","name":"/foo","type":"value","value":"bar"}
[DEBUG] HTTP/1.1 422
Transfer-Encoding: chunked
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
Content-Type: application/json;charset=UTF-8
Date: Wed, 14 Nov 2018 19:06:00 GMT
Expires: 0
Pragma: no-cache
Strict-Transport-Security: max-age=31536000 ; includeSubDomains
X-Content-Type-Options: nosniff
X-Frame-Options: DENY
X-Xss-Protection: 1; mode=block

81
{"error":"The request includes an unrecognized parameter 'mode'. Please update or remove this parameter and retry your request."}
0

Hey @xtreme-conor-nosal, we're trying to reproduce this and could use some more information.

Have you upgraded either the credhub server or CLI before this started happening?
What is the ServerVersion field in ~/.credhub/config.json?
What is your workflow for targeting/logging into CredHub? Do you set environment variables? Do you use the credhub login or credhub api commands?

The CLI was updated on the local workstation. The server is deployed as part of a bosh-bootloader deployment. We don't upgrade in place - we always repave.
The ServerVersion in ~/.credhub/config.json is 1.6.5
We set environment variables:

CREDHUB_SERVER=https://<IP_ADDRESS>:8844
CREDHUB_CA_CERT=$CERT
CREDHUB_PROXY=ssh+socks5://jumpbox@$IP:22?private-key=/tmp/bbl_cWbdY8
CREDHUB_CLIENT=credhub-admin
CREDHUB_SECRET=$SECRET

The issue seems to be that your ~/.credhub/config.json says that the server version is 1.6.5. We introduced caching of this in CLI version 2.0.1 which is why 2.0.0 still works for you.
You can fix this issue by running credhub login using the latest CLI after setting those environment variables. This is in fact how the CLI should be used (although I recognize that it is not well documented). That will update the ServerVersion in the config file as well as update your UAA auth token.

We use the environment variables to avoid writing the client secret to disk, and to try and avoid stale properties.
For consistency, would it be possible to control the ServerVersion via the environment?
e.g. one of:
CREDHUB_SERVER_VERSION=2.0.2
CREDHUB_API_VERSION=2
CREDHUB_DISABLE_VERSION_CACHE=true

As a workaround, would something like curl /version > config.json work in combination with the environment variables?

@xtreme-conor-nosal The cli relies on ~/.credhub/config.json to cache the server version.  Unfortunately, this file will be overwritten by the cli when you call credhub login.  If you try to replace values in the config.json file with environment variables, then they will be overwritten the next time you call credhub login.  Does that help?

@xtreme-conor-nosal we've had some discussion about using only environment variables when running the CLI (https://github.com/cloudfoundry-incubator/credhub-cli/issues/34), but it would be a pretty large change and probably not something we'll get around to in the near future.
Your workaround of modifying the config file will definitely work, but I wouldn't suggest it as a long-term solution. I understand your concern of not wanting to write the client secret to disk, and using credhub login wouldn't actually require that. If you run credhub login with no arguments, it will use the CREDHUB_* environment variables. But it will also ensure that the server version is correct by making a request to credhub.

@xtreme-conor-nosal We just tried it out and you're right, the UAA creds get written to the config file even when using environment variables. We made a story here to stop writing them to disk.


[5.9.0] Update Options.swift for '-load-plugin-executable' update

release/5.9.0 version of #1409 , update for https://github.com/apple/swift/pull/67835

Explanation: -load-plugin-executable compiler option is the primary supported way of using macro plugin. SwiftPM uses this when developers use .macro() target. The help text should clarify the format and the semantics of the arguments.
Scope: Help message for -h
Risk: Low, this is just a message change
Testing: Passes current test suite
Issues: rdar://113646544
Reviewer: Artem Chikin (@artemcm)

@swift-ci please test

@swift-ci please test macOS platform


[Enhancement] Add option for with-brpc-keepalive to run-be-ut.sh

Why I'm doing:
We have with-brpc-keepalive in build.sh. This PR is to align it in BE UT.
What I'm doing:
Add the flag of with-brpc-keepalive.
Fixes #issue
What type of PR is this:

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

[ ] This is a backport pr

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.3
[ ] 3.2
[ ] 3.1
[ ] 3.0
[ ] 2.5

ignore backport check: 3.2.8

ignore backport check: 3.3.0

ignore backport check: 3.2.9

ignore backport check: 3.3.1


Communication LED is off, not working, why? How to fix it?

I am working with 6 Turtlebot 4 under the same router. Frequently, the COMM LED turns off automatically. I want to know the reason. I have separated them with different ROS_DOMAIN_ID  What is the proper and fastest way to turn on or fix the issue with COMM Led?

The COMM led being off indicates that the connection between the RPI4 and Create3 is not up. It may be that the Create 3 or RPi lose WiFi connection at some point. I would recommend trying to use FastRTPS as it will maintain the USB-C connection even if WiFi drops. Take a look at the tutorial here for instructions on how to easily switch RMW's.

@roni-kreinin , I have followed the instruction. I did it by creating and running ros_config.sh script in /usr/local/bin of RPI 4 of the turtlebot. But the problem is when I separate two turtlebots with different ROS_DOMAIN_ID and set RMW_IMPLEMENTATION to rmw_fastrtps_cpp using ros_config.sh, under the same wifi router, the IP address of both robots starts to blink. The last 3digits of IP addresses start to exchange among each other. For example, Turtlebot1 with domain_id 1 has IP address <IP_ADDRESS> and is switching to Turtlebot2's (domain_id 5) IP address <IP_ADDRESS> and vice versa. The remaining turtlebots(4 of them still using cyclone_dds) start making chiming sounds but not blinking. If I shut down one turtlebot that is using fastrtps, then the blinking/exchanging of other turtlebot stops.
What should I do?

I forgot to add to the instructions that you also need to update your install.py script. You can find the updated script here. Download it and move it to /usr/local/bin/, then run the ros_config.sh script again.

@roni-kreinin , It worked for those two turtlebot4. But when I tried with another one, the led lights, with led display is gone. But I could ssh into it using previous IP address.Then I ssh into it using ethernet cable with <IP_ADDRESS>. But after using sudo wifi.sh -a it is showing me turtlebot4 wifi. But still led light and display is not working. How to fix this?

sudo wifi.sh -a puts the RPi back into AP mode. You need to connect it to the same WiFi network as the Create3.

The problem is that turtlebot is working but I can not see the led display or light. I know how to connect to Create3 under same wifi. But LED light or display is not working.

You can check the logs of the turtlebot4 service with sudo journalctl -u turtlebot4 -r. You might need to restart the service with sudo systemctl restart turtlebot4.

I solve it using this command. sudo apt-get install -y ros-galactic-rmw-fastrtps-cpp
Cause it is not installed in our turtlebots. I think this the reason when I switch to rmw_fastrtps_cpp, my led lights and display turns off.
I might be wrong. But it is solved after installing this package.

@roni-kreinin , I am still facing problem. It is very slow when students work with the six turtlebot4  simultaneously. So, should I add more routers? Or can I solve it in another way? Sometimes, COMM led is off for 20-30 seconds. What more can I do to make the turtlebot response smoothly under the same router? Or how many bots should I place under a router that will not slow it down?

@Tanjim13 I would like to figure out if this is a bandwidth or signal strength issue. Can you answer the following questions:

Does the COMM led turn off while the robot is driving around or when it is standing still?
How strong is the WiFi signal for both 2.4 and 5GHz in the area that you are testing? You can check with a phone or laptop.
Next time the COMMs light turns off, can you retrieve the logs from the Create 3 webserver and upload them here?
Can you also call ros2 topic list from a remote PC when the light turns off? To check that the RPi4 topics still publish.
Can you check the framerate of the camera stream with ros2 topic hz /color/preview/image? It should be publishing at 30hz.

@roni-kreinin,

Sometimes, It goes off while driving (both in fastrtps & cyclonedds mode). But fastrtps mode, it comes back after few seconds. Another problem is that, it is very slow when we run programs using virtual machines in fastrtps mode without ssh into RPI compare to cyclonedds.
For 5GHz:, RSSI: -45dBm, Noise: -93dBm, TxRate: 867Mbps...  2.4GHz: RSSI: -34dBm, Noise: -88~-93dBm, TxRate: 145Mbps
I will try to answer rest of the questions, when I will work with them again.

@roni-kreinin , I tried to retrieve logs from create3 webserver, but it did not work. I tried <IP_ADDRESS>:8080, but it did not let me go to the site.
ros2 topic hz /color/preview/image it worked fine.. I will investigate it further.
fastrtps is very slow compare to cyclonedds.

Hi @roni-kreinin , I want a suggestion. If I add routers to the turtlebot4 will it create any difference? Also if I use fastrtps do I need to change anything in my local linux machines? like changing in my ~/.bashrc file? I found fastrtps is very slow compare to cyclonedds. When I work alone, it is okay to work. But if multiple users in a same room working with 4-7 turtlebots simultaneously, I find comm stops working on few of them. Even in fastrtps it turns off and on.

@roni-kreinin, I can access to Create3 webserver using the IP address of the iRobot-8XXXXXXXXXX device from the Router's connected devices. So, I checked that the version of Firmware version is G.2.2.
Another turtlebot4 has come to the lab recently and I can access the web server using the IP address of RPI with 8080 port. The firmware version of this turtlebot4 is G.3.1.
So, should I update the firmware of the create3 base? Will it solve the problem?
I will try to send you the log files from the webserver next time when we will work with more robots simultaneously and if the COMM goes off.

The other two turtlebots are connected to another router within the room.

@Tanjim13 Sorry for the delay.
I would recommend updating any robots you have to G.3.1 to have all of the latest Create 3 features and bug fixes. As for accessing the webserver with the 8080 port, that is only installed by default on the 0.1.3 image in the link you mentioned. You can manually add it to an older image if you want by copying this file to /etc/systemd/system/ and then calling sudo systemctl enable webserver.service.
Regarding the comms issue, the easiest solution is likely to just use 2 routers and have 3 robots on each. There is an update coming that adds discovery server support to the Create 3, but until then there isn't a great solution.

@roni-kreinin Thank you so much.
I will look into it.

Closing as stale. Feel free to reopen if the issue persists.


added disable masks: supports business days and even/odd weeks; completed nl_NL translations

nl_NL counts as nl_BE too btw

I'm new to committing and this is my first JS project in a long while. I may be doing things wrong but that's mostly because all these new tools confuse me.
Still, added are a few functions to do the following:

completed the nl_NL translation (added labels)

set different weekday masks on odd or even weeks
syntax:
disable: [       { oddWeeks: [1,3,5], evenWeeks: [2,4,6] }         ]
in above example, the 1st, 3rd and 5th day will be disabled on odd weeks, while on even weeks the 2nd, 4th and 6th days will be disabled. It also takes your firstDay setting into account.

modified the { from - to } mask to take business days into account
syntax:
disable: [    { from: [2016,7,9], to: 3, toWorkingDays: true }     ]
in the above example, it will disable the next three business days after Saturday 9th and Sunday 10th July 2016. I.e. it will disable Monday 11, Tuesday 12 and Wednesday 13.

Currently no experience with Grunt so I didn't update the minified versions of the JS.

Please separate feature and i18n. And please rebase your master branch before creating the new branches from it.

Hi.. How to disable specific days of each month, for the entire period, or the other way around, enable only specific days. In the specific case, I want only the 15th of each month to be chosen. Thanks for the feedback


Stream is captured error in ROCm tests

https://jenkins.preferred.jp/job/chainer/job/cupy_master/TEST=rocm-4-0,label=mnj-mi50/1919/console
 E   RuntimeError: streamIsCapturing is supported since CUDA 10.1+

Hmmm how come Jenkins didn't complain at all in the PR?

yeah, seems like not all tests are being enforced


Drop spire version ranges

Here: https://github.com/spiffe/helm-charts-hardened#dependencies-and-version-compatibility
we claim to support all the 1.6.x and 1.7.x series. We don't test hardly any of it though. Thinking we should only claim official support of the version we are testing/releasing a particular version of the chart with?

That table is definitely out of date.  That sounds fine to me.


Remove log of uncaughtException config

@ofrobots PTAL.

LGTM.

@ofrobots please take another look. I've updated our jshint configuration to catch delinquent log statements.

LGTM.


Respect TMPDIR environment variable when creating temporary files

Steps to reproduce the issue
I'm using Linux with tmpfs located somewhere other than /tmp. In https://github.com/YosysHQ/yosys/blob/master/kernel/yosys.cc#L379-L460, I noticed that the actual value of TMPDIR is never read but is hard-coded to /tmp.
Expected behavior
If I set TMPDIR=/dev/shm, Yosys should put temporary files into /dev/shm when calling ABC.
Actual behavior
If I set TMPDIR=/dev/shm, Yosys still put temporary files into /tmp when calling ABC.

This bug looks to have been fixed as the line https://github.com/YosysHQ/yosys/blob/master/kernel/yosys.cc#L402 calls std::getenv("TMPDIR"); to assign the temporary directory.


Change expiryDate date parameter to take timestampDelta

At the moment, when we have task n who has an action which submits a new task to gelato, then we cannot really choose a valid expiry date when we encode the payload for submitTask, because we dont know when the task will actually be submitted.
Similar to the Stateful conditions, we could use a delta for that, where users input that they want the claim to be active for e,g, 24 hours. Gelato will then calculate the respective timestamp on-chain.
At the moment, to create have one task submit another which is limited to a certain timestamp, we have to write a wrapper action around gelato which enables you to do that.

Jo - delta's based on submission time sind gut.


Uploading Assignment Tasks

Uploading tasks: 12,13,14,15,16,17,18,20,22,23,24
Also re did the tasks 1,2,4 for my practice.

SourceCode/2023/Sep2023/Basics/Sandhya/Task12/Task12/project.json
NoFile

Issue: Your project is missing an Automation Hub URL.

Solution: Go to "Project Settings" and add the missing URL.

Issue: Unused dependency packages detected. One or more of UiPath.Excel.Activities, UiPath.Mail.Activities, UiPath.Testing.Activities, UiPath.UIAutomation.Activities isn't needed.

Solution: Remove these unused packages. It'll make your process run faster.

Main.xaml

Issue: Log Message not being used in Main workflow.

Solution: You should use Log Message activities. They help in understanding the flow and identifying the source of errors. Add where needed.

Issue: Duplicate Activity display names (Body, Else If, Assign).

Solution: Please rename these activities. Each should have a unique name that indicates its purpose.

Issue: Some Activities (For Each, Else If, Assign) have default names.

Solution: Rename these activities with more descriptive titles. It makes understanding their functions easier.

SourceCode/2023/Sep2023/Basics/Sandhya/Task13/Task13/project.json
NoFile

Your project doesn't have a defined Automation Hub URL. To fix this, add the missing information in the "Project Settings".

Seems like you've included packages that you're not using. It's best to remove these to improve processing time. These are: UiPath.Mail.Activities, UiPath.System.Activities, UiPath.Testing.Activities, and UiPath.UIAutomation.Activities.

Main.xaml

You don't have any "Log Message" activities in your workflow - these are really useful for understanding the flow during development and after release, particularly when identifying errors.

There's a variable, Dt_Data1, that you're not using. Best to remove it.

This same variable, Dt_Data1, is defined multiple times - you'll need to give variables unique names, even if they're within different scopes.

The variable, Dt_Data, should start with a dt_ prefix. Same with the Dt_Data1 variable. They don't comply with the set pattern ^(dt_)?([A-Z]|[a-z])+([0-9])*$ and don't respect the naming convention.

These changes should make your project a lot more efficient and easier to debug - please

SourceCode/2023/Sep2023/Basics/Sandhya/Task14/Task14/project.json
Files: NoFile

Your project is missing its Automation Hub URL. Kindly add it via the "Project Settings" tab.

Detected unused UiPath.Mail.Activities package. Suggesting to remove it to lower process execution time.

Detected unused UiPath.Testing.Activities package. Suggesting to remove it to lower process execution time.

Files: Main.xaml

No Log Message used in Main workflow. Remember, log messages are your friends in both development and debugging phases.

Variable "ExtractDataTable" does not have a "dt_" prefix. DataTable variables should begin with "dt_".

Variable "Dt_Dataresult" does not have a "dt_" prefix. DataTable variables should begin with "dt_".

Variable "Dt_Dataresult" seems to not follow the required pattern ^(dt_)?([A-Z]|[a-z])+([0-9])*$, please adjust to comply with naming conventions.

Activity "Extract Table Data" also has a default name. More descriptive titles are always better for readability and maintenance purposes. Go ahead and adjust it if possible.

SourceCode/2023/Sep2023/Basics/Sandhya/Task15/Task15/project.json
For NoFile:

"Put your work's URL from Automation Hub into 'Project Settings'. Your work needs it."
"You don't appear to be using the UiPath.Mail.Activities, UiPath.Testing.Activities, or the UiPath.UIAutomation.Activities. Get rid of these packages to make your bot run faster."

For Main.xaml:

"I don't see any 'Log Message' activities in 'Main'. These come in handy for both making and maintaining your bot. When something goes wrong, they also point you right to the problem."
"You've used the 'Write Line' activity in 'Write Line'. This works for debugging but has to go before you publish your work. Use 'Log Message' instead if you really need it for debugging."
"The name 'Assign' is being used more than once. The current limit is one but your code has two. Names have to relate to what these activities do. Default names won't do."
"You've used default names for 'For Each Row in Data Table', 'Write Line' and 'Assign' activities. Make these more descriptive. They should tell anyone about what these activities do."

SourceCode/2023/Sep2023/Basics/Sandhya/Task16/Task16/project.json
NoFile

Issue 1: Your project needs an Automation Hub URL. Go to 'Project Settings' and fill it in.

Issue 2, 3, 4: You have packages that aren't being used: UiPath.Mail.Activities, UiPath.Testing.Activities, and UiPath.UIAutomation.Activities. Remove these to make your process run faster.

Main.xaml

Issue 1: No 'Log Message' used in your workflow 'Main'. Logs help understand the flow path, are useful for maintenance, and help identify where and why errors are happening.

Issue 2, 3, 4: Your activities 'Build Data Table', 'Output Data Table', and 'Message Box' are using default names. Rename them to something that tells us what they do.

SourceCode/2023/Sep2023/Basics/Sandhya/Task17/Task17/project.json
NoFile:

Warning: The Automation Hub URL is not defined. Easy fix: Go to "Project Settings" and drop in the link there.

Heads up: It seems like we have UiPath.Mail.Activities package included, but it ain't used. Let's save some time by removing it.

Same situation with the UiPath.UIAutomation.Activities package. Let's clear the unused baggage.

Main.xaml:

Noticed, 'Log Message' is non-existent in the 'Main'. Remember, logs are our eyes during and after deployment. They help us track the flow and identify any hiccups. Worth adding a few.

There's a variable 'outputtext' that's missing the DataTable prefix. Mirroring conventions, DataTable Variables should start exactly like this: 'dt_outputtext'. Correct it, mate.

SourceCode/2023/Sep2023/Basics/Sandhya/Task18/Task18/project.json
Post for "NoFile":
Hey there,

Come across a couple of things that need your attention:

1. We need to have an Automation Hub URL defined in your project. You can simply add this info through "Project Settings".

2. Noticed some unused packages like `UiPath.Mail.Activities`, `UiPath.Testing.Activities` and `UiPath.UIAutomation.Activities`. Honestly cleaning those up improves process execution time. So, just get rid of those.

If you got any questions, feel free to ask.

Post for "Main.xaml":
Hey,

Just had a look over your workflow in 'Main.xaml'. Here's what stood out:

1. Missed out using `Log Message`. It's like breadcrumbs in the woods mate, helps you backtrack during development and post release. No worries, add it to easily trail errors.

2. Variables for DataTable should start with a dt_ prefix. Found one - `Datatable` which doesn't follow the naming style. Tweaking ought to do it.

3. Spotted activities with default names: `Build Data Table`, `Multiple Assign`, `Assign`, `Add Data Row`. Seriously, more descriptive names make understanding easier. Switch it up to better ones

SourceCode/2023/Sep2023/Basics/Sandhya/Task20/Task20/project.json
For Main.xaml

Start using "Log Message" activities in your workflow. This helps both during development and also after release. If there's an issue, these logs can help us find the source and cause more easily.

Try to replace "WriteLine" activity with tracepoints during the debug stage. Ideally, get rid of it before publishing. If really needed for debugging, perhaps change WriteLine to Log Message.

Prefix your DataTable Variable with "dt_". So, change "readrange" to "dt_readrange".

Please name your activities more descriptively. For example, "For Each Row in Data Table" and "Write Line" are too generic and it's hard for others to understand their purpose without context.

For NoFile

Your project needs an Automation Hub URL defined. Go to "Project Settings" and add it.

The dependency package "UiPath.Mail.Activities" is currently not in use. Let's get rid of it to improve process execution time.

The same goes for "UiPath.Testing.Activities". If it's not in use, remove it to speed up process execution time.

SourceCode/2023/Sep2023/Basics/Sandhya/Task22/Task22/project.json
Main.xaml

The file seems to have a problem, it cannot create an unknown type {http://schemas.uipath.com/workflow/activities}BuildDataTable. Looks like there is an unrecognized activity in the workflow. Make sure to use supported activities or import the necessary packages.

Your project analysis is suffering because of some errors in your workflows. Clean up the errors first before running the project analysis.

Remember to thoroughly check your workflow for any unrecognized or forbidden activities. Keep your UiPath packages updated to avoid this kind of errors.

SourceCode/2023/Sep2023/Basics/Sandhya/Task23/Task23/project.json
File: Main.xaml
Hey there,

It seems your Main.xaml file is trying to create a type ({http://schemas.uipath.com/workflow/activities}MessageBox) that the software doesn't understand. Be sure to use only supported types. Maybe you're trying to show a MessageBox? Use MessageBox.Show("Your message here").

In addition, because of the errors in this file, the project analysis can't be completed. Fix the problem above and we should be able to analyze the project again.

Let's get this sorted and move forward. Review and update the file accordingly.
Cheers.

SourceCode/2023/Sep2023/Basics/Sandhya/Task24/Task24/project.json
Hey there,
I've looked over your changes and found some stuff we need to sort out:

"An exception was thrown while activating ?: UiPath.Studio.Platform.Contracts.IPlatformWrapper."

Seems there's an issue with the PlatformWrapper activation. You might want to check how this was implemented. Make sure all prerequisites for the activation are satisfied.

"Cannot perform project analysis because some workflows have errors."

Seems like there are errors in some of your workflows, which is blocking project analysis. This is likely caused by faulty or incomplete workflows. Try going over them again and debug any issues. Let me know if you need extra eyes on them.

Cheers, mate and keep up the good work!

SourceCode/2023/Sep2023/Basics/Sandhya/Task2_R1/Task2_R2/project.json
File: Main.xaml
Hey there,
Just a heads up, there seems to be a problem loading your Main.xaml file. This could possibly be due to an issue with the InputDialog activity in your UiPath project.
It might be because UiPath can't recognize this activity. It could happen if you're using an outdated package version or the specific activity isn't installed in your project.
To fix this, please check if you've installed all necessary dependencies and their versions are up-to-date.
Additionally, I noticed that the project analysis isn't complete due to some workflow errors. Once you address the above issue, this should be resolved. Remember, it's important for all workflows to be free of errors before we can perform a thorough project analysis.
Let me know if you need help figuring this out. Cheers!

SourceCode/2023/Sep2023/Basics/Sandhya/Task3_R1/Task3_R1/project.json
File: NoFile
Comments:

An exception was thrown: It seems like something is preventing your code from activating the IPlatformWrapper interface. Ensure that all dependencies are correctly installed and functioning as they should. If the issue persists, try debugging your code to find the conception point of the exception.

 Go through your workflows step by step; identify and fix the errors to allow for accurate project analysis. Problem could be as simple as a syntax mistake, logic error or a missing/incorrect variable. Look for red underlines or exclamation marks that would indicate an error.

@Sandhyathota1
Task -2
Code verified.
Task -3
Code verified.
Task -12
Code Verified. Default activity Names

Task -13
Code verified.
Task -14
Code Verified. Default activity Names

Task -15
Code Verified. Default activity Names

Task -16
Code Verified. Default activity Names

Task -17
Code Verified.
Task -18
Code Verified. Default activity Names

Task -20
Code Verified. Default activity Names

Task -22
Code Verified. Default activity Names

Task -23
Code Verified. Default activity Names

Task -24
Code Verified. Default activity Names


Use operate instead of put to overcome the bin-convergence restriction

Hmm. I think that Bin convergence is not enabled by default and is not used by all the clients, yet the changes in the PR expect this feature to be enabled/used by everyone.
It is not that I am against this feature, but it does not look good to increase number of requests for the feature that is not even used on production. Maybe there is another workaround for the REPLACE_ONLY strategy?

According to the doc:

In spite of the best efforts, there may be cases where the system clock may fall behind or go ahead compared to the other DCs. If a node's system clock falls behind, the client writes may fail with error code 28 (LOST CONFLICT). This may happen because the incoming XDR writes would have written the bins with a higher timestamp. A subsequent local client write will use the local time and may be behind the XDR write's timestamp. In this case, the client write will be rejected as we cannot allow the bin-level LUT to go back in time.

Should we also handle the LOST CONFLICT error code?

Addressed in #494.


Record dependency on jQuery

This package references $, but doesn't declare a dependency on jQuery.

woops, thanks!


Makes it a compilation error if a variable is unused.
I'm unsure how I feel about this currently. It can get annoying,
but I think it's a good help and it needs to be available somehow.
The way to silence the error is to just, read the value on the line
after. It might be better to enforce a naming standard, like Rust?
Or maybe this is a good way to do it, since you don't have to rename
stuff?
Closes #37
Starts work on #63

killer feature: Allow the typechecker to run on code that is only faulty when it comes to unused variables. So a program can now be valid in different ways. Off to bed I go!

I think some way of silencing the warning is needed before merging. Either renaming to _x or passing a hard-coded flag (as in, we don't need a full-blown -Wno-unusued-variable-system).

Not sure what the best solution is here. Passing flags to the compiler, will require a pretty large rewrite, and might be the better way. In some ways I dislike the Rust way, since it promotes a lot of edits to the code. But then again I guess people like it, because it makes it painfully obvious if a variable is unused.
Go enforces this as an error, making programs with unused variables faulty programs. We're not more extreme than Go here. And I think it's a good mentality to be extreme, and push for the features we want as hard as possible.
TL;DR I don't agree that we need a flag or way to silence the warning, other than making a "fake-usage" of the variable. We need to take a discussion here.


Mirror ticks #30

This feature here basically looks at all the climbs a user has done and sees if they completed it.  If they complete the climb in reverse, then then a reversed checkmark shows. However, if a user marks the climbs in the forward and reverse way, then a forward and reflected check mark shows.

Ok I believe I fixed everything, let me know if any problems occur

It's alright, I was able to fix it. Let me know if I missed something, I am fine with going back and fixing


Actor registry

I think there should be per Arbiter registry, some kind of actor singleton system.
maybe even with auto actor spawn. so Arbiter can provide per thread registry and System can provide global registry.
interface could be very simple, something like this

trait Registry<A: Actor> {

   fn get<A: Default>() -> Address<A>;

    fn query() -> Option<Address<A>>;

    fn register(addr: Address<A>);
}

implemented


Unit test for grad accum

Would be nice to have a unit test for grad accum to make sure gradients are close to that without it.

Jillian taking over on this based on some boiler plate I pushed here: https://github.com/mlfoundations/open_lm/tree/testing

#50


RTC

This adds RTC for most of the stm32 chips. Nearly all of the work was not done by me, but I took it the last bit by disabling the chips that weren't working. I think it would be easier to enable them in future PRs if requested.

bors r+


tpcds add tpchds 1T shape check

Proposed changes
add regression case to simulate tpcds 1T.
shape check will be added later after they are stable.
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


MuleSoft: Deploy to Cloudhub - option is not available on command Palette

<!— This repo is for feedback on Anypoint Code Builder during open Beta, please limit your issues to those associated with Anypoint Code Builder. Please let us know if you encounter any issues both creating or launching the web IDEs along with issues implementing your use cases.
This is not a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, please use official support channels. -->
Describe the bug
I have created a simple application using "Develop an Integration" option from Anypoint Code Builder. The application is running fine from Anypoint Code Builder. But when try to deploy the application to CloudHub, trying to select the option "MuleSoft: Deploy to Cloudhub" on Command Palette, but getting a response as "no matching command".
I am exploring Anypoint Code Builder from my trial account.
To Reproduce
Steps to reproduce the behavior:

Click on Develop an Integration option from Anypoint Code Builder
Create a simple application (with HTTP connector and Transformation)
Open the Command Palette (ctrl/cmd + shift + P) and type MuleSoft: Deploy to Cloudhub
Getting a response - "no matching command"
Expected behavior
It should allow deploying the application on CloudHub

Impact
Select from

Poor Usability

Frequency
Select from

Always

Screenshots/Recordings
If applicable, add screenshots or recordings to help explain your problem.  They really help!
Please complete the following information:

Anypoint Code Builder web IDE URL - https://hyacinth-yu5in0.builder.code.com
Browser [e.g. chrome, safari] - Chrome
Version [e.g. 29]  ver 24.1.0

Additional context
Add any other context about the problem here.

Are you on a windows laptop? We will deploy a fix for cloud hub deployment tomorrow (Monday)

Hi Simone,
Yes I am on a Windows machine. Thanks for your update.
Thanks and regards
Ananda
On Mon, 20 Mar, 2023, 2:17 am Simone Geib, @.***> wrote:

Are you on a windows laptop? We will deploy a fix for cloud hub deployment
tomorrow (Monday)
—
Reply to this email directly, view it on GitHub
https://github.com/forcedotcom/try-acb-feedback/issues/35#issuecomment-1475392405,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AT3RVET55SDLRL6SO5RI5UTW45WGTANCNFSM6AAAAAAV77WPNM
.
You are receiving this because you were mentioned.Message ID:
@.***>


Fix vendored_static_libraries in apple_library

Summary
While working on #530 I wanted to see if this was just an XCFramework issue and so I've added a fixture for a static library. This will allow us to test the vendored_static_libraries feature of apple_library.
Fixtures
This PR adds some new fixtures for testing static libraries

tests/ios/libraries/StaticLib

Contains the App target which imports all of the static library
Test with bazel build //tests/ios/libraries/StaticLib:StaticLibApp

tests/ios/libraries/StaticLib/ObjcLib

Contains a fixture for a pure Objective-C static library (for the simulator platforms)
Test with bazel build //tests/ios/libraries/StaticLib/ObjcLib

Testing
From testing with bazel build //tests/ios/libraries/StaticLib:StaticLibApp it looks like support for static libraries in general is broken in rules_ios. A fix for this simple case should be sufficient to fix issues in #530 as well.
bazel build //tests/ios/libraries/StaticLib:StaticLibApp

INFO: Build options --copt and --features have changed, discarding analysis cache.
INFO: Analyzed target //tests/ios/libraries/StaticLib:StaticLibApp (0 packages loaded, 1434 targets configured).
INFO: Found 1 target...

Error in child process '/usr/bin/xcrun'. 1
Target //tests/ios/libraries/StaticLib:StaticLibApp failed to build
INFO: Elapsed time: 1.739s, Critical Path: 1.44s
INFO: 2 processes: 2 internal.
FAILED: Build did NOT complete successfully

@jerrymarino Just re-read your comment and I agree, removing the implicit behavior of collecting the headers for vendored_static_libraries makes sense.
I've updated the PR to remove the implicit glob and instead rely on the public_headers property being provided to apple_framework


azd.exe process hanging around after VS exit

This may be a solar flare but I was cleaning up some code on my cloud hosted DevBox and I noticed that azd.exe was running and had a handle open on my source folder:

I suspect this process was launched by VS, but VS wasn't running so perhaps it didn't clean itself up. I can't remember interacting with the VS publish features on this devbox though so I'm not entirely sure where it came from.
Filing an issue just in case others have seen it.

Was definitely launched by VS.

@anvillan @abpiskunov can you triage this for anything on VS side? cc @ellismg @weikanglim

@rajeshkamal5050 @mitchdenny
I gave it a try but could not repro: the azd.exe process is always terminated along with VS.
Remember that VS starts the azd vs-server as soon as it detects the current project is an Aspire project. Thus, even if you do not perform and 'Deploy' related tasks, the azd.exe process should be started already.
I tried...

Create Aspire project, add new Environment, Publish
Running the project, stopping it
Intentionally terminating the azd.exe process while VS is running, so we recover it
Closing VS while we are in the middle of a (long running) RefreshEnvironment operation
Terminating (kill process) VS IDE in the middle of a RefreshEnvironment and/or running the project

If you could find a way to repro it consistently, that would help to see if there is any issue

Let's pencil it in as a solar flare for now.


Sphinx build failed with unknown error.

Details

Project URL: https://readthedocs.org/projects/pub2sd/
Build URL (if applicable):https://readthedocs.org/projects/pub2sd/builds/6277134/
Read the Docs username (if applicable): silseb

Expected Result
Tried to build the documents following a 'git push' to "https://github.com/madskinner/pub2sd"
Actual Result
The build failed with Error: Unknown error encountered. Please include the build id (6277336) in any bug reports.
Sphinx build for 'building [readthedocssinglehtmllocalmedia]' apparently passed, but error occurred immediately after or at start of next build.
Retrying with PDF and EPUB build disabled in 'Advanced Settings' made no difference. Likewise clearing as many warnings as I could, made no change.

In my case the similar problem was solved by putting Sphinx>=1.6.5 into requirements.txt. The Sphinx version 1.5.6 (as it was used to build your project, too) provided corrupted latex output.

Thanks for the suggestion 'Piogor', just tried it. Unfortunately it still fails at the same point even though the log shows it running Sphinx 1.6.5 in build:
https://readthedocs.org/projects/pub2sd/builds/6280898/

Thanks for the report @madskinner, this is an uncaught error in our build system. We're trying to surface these more in hopes of actually creating a caught error.


[tool]: How to calculate the Dart SDK snapshot download URL

When downloading and installing the Flutter too, it first downloads the Dart SDK snapshot, having the URL:
DART_SDK_BASE_URL="${FLUTTER_STORAGE_BASE_URL:-https://storage.googleapis.com}"
DART_SDK_URL="$DART_SDK_BASE_URL/flutter_infra_release/flutter/$ENGINE_VERSION/$DART_ZIP_NAME"

E.g. for current stable Flutter, this results in: https://storage.googleapis.com/flutter_infra_release/flutter/caaafc5604ee9172293eb84a381be6aadd660317/dart-sdk-linux-x64.zip
I was wondering what SHA256 (is it?) the ENGINE_VERSION is computed with? In $FLUTTER_ROOT/bin/flutter/internal/update_dart_sdk.sh, it is simply read out from $FLUTTER_ROOT/bin/internal/engine.version
In environments Flutter is installed in without any network access, this might be useful to know. Especially e.g. for distributors of Linux distributions willing to package Flutter.

May this help:
https://github.com/meta-flutter/meta-flutter/blob/kirkstone/conf/include/flutter-version.inc


Fix properties file loading

The value of the propertiesPath variable looked like null/./orion.properties, which was the wrong path to the properties file.

Thanks.


Added compose file to setup multinode Raft network on different physi…

…cal machines.
Signed-off-by: Pankaj Goyal<EMAIL_ADDRESS>

How can we test this?

Steps to create Sawtooth-raft network using docker-swarm

Create 3 physical machines with Ubuntu 18.04. Lets call those machines as node1, node2 and node3
Install docker and docker-compose in all the machines
node1 will be master node and node2 and node3 are worker nodes
open certain ports on all the nodes: 2377/tcp, 7946/udp, 7946/tcp, 4789/udp

Initialize swarm
Swarm has to be initialized on master node (node1). In order to do this, run the below command on node1:
	docker swarm init
The output of above command will be something like this:
Swarm initialized: current node (bvz81updecsj6wjz393c09vti) is now a manager.
To add a worker to this swarm, run the following command:
docker swarm join \
--token SWMTKN-1-3pu6hszjas19xyp7ghgosyx9k8atbfcr8p2is99znpy26u2lkl-1awxwuwd3z9j1z3puu7rcgdbx \
<IP_ADDRESS>:2377

To add a manager to this swarm, run 'docker swarm join-token manager' and follow the instructions.
As the above output shows, worker nodes need to join the swarm by running the following command:
docker swarm join
--token SWMTKN-1-3pu6hszjas19xyp7ghgosyx9k8atbfcr8p2is99znpy26u2lkl-1awxwuwd3z9j1z3puu7rcgdbx
<IP_ADDRESS>:2377
So, run the above command on node2 and node3. This way node2 and node3 will join the swarm.
Create swarm network
Run the below command on master node (node1) to create swarm network:
	docker network create –d overlay raftnetwork
The above command creates a network named ‘raftnetwork’ which will be used by the docker compose file.
Validator keys management
Run the swarm/validator_keys.yaml file. This will generate the validator key pairs in /home/Ubuntu/validator_keys folder
	docker-compose -f swarm/validator_keys.yaml up
	docker-compose -f swarm/validator_keys.yaml down
Copy /home/Ubuntu/validator_keys folder in all the other nodes to /home/Ubuntu folder.
Environment variables
On master node (node1), define the following variables in swarm/.env file:
export TAG=1.1               <1.1/latest/nightly>
export node1=<hostname_of_node1>
export node2=<hostname_of_node2>
export node3=<hostname_of_node3>
Create docker containers
Run the below command on master node (node1):
	docker stack deploy –c swarm/raft_3_nodes.yml raft
You can check all the services started by above command:
	docker service ls
The above command should show that all services are running.
Now, all the containers should be running in respective machines. This can be checked on each node that respective containers are running.
On master node, there is a shell conainter running. This can be used to start the intkey workload after generating the user key.
At any time, the services created by stack deploy can be destroyed by:
	docker service rm $(docker service ls -q)
Services can be started again by running “docker stack deploy –c swarm/raft_3_nodes.yml raft”

The author on the commit is 'Ubuntu' which is why the DCO is failing.

Thanks for the nice instructions!

Could you update your commit message to follow the format described in https://chris.beams.io/posts/git-commit/
Likewise, include some more information about the commit and what it changes/provides.


label overflow in barchart

Why are the labels overflowing here?
https://snack.expo.dev/kAIinbKfvt1viem9v9JFF

Hi @sd535682
This can be fixed using the labelWidth and xAxisLabelTextStyle props.
Here's my snack with the above props- https://snack.expo.dev/@ak_97/hot-indigo-cookie

instead of alignSelf: "flex-end", you can use textAlign: "right"


Make CPU builds parallel and customizable AMD GPUs

The linux build now support parallel CPU builds to speed things up. This also exposes AMD GPU targets as an optional setting for advaced users who want to alter our default set.

@mxyng this should provide some additional primitives to tune our CI builds.  Since there are other PRs in flight, I didn't include those in this to avoid conflicts, but we can now split out all the CPU variants as separate runners, and reduce ROCm down to ~1 GPU target to make it go a lot faster.
With the full set of GPU targets on my laptop the build looks like:
 => [rocm-6-build-amd64 6/6] RUN OLLAMA_SKIP_CPU_GENERATE=1 sh gen_linux.sh                                              241.7s
 => [rocm-5-build-amd64 6/6] RUN OLLAMA_SKIP_CPU_GENERATE=1 sh gen_linux.sh                                              237.5s

Reducing down to justAMDGPU_TARGETS=gfx1010
 => [rocm-5-build-amd64 6/6] RUN OLLAMA_SKIP_CPU_GENERATE=1 sh gen_linux.sh                                               70.5s
 => [rocm-6-build-amd64 6/6] RUN OLLAMA_SKIP_CPU_GENERATE=1 sh gen_linux.sh                                               70.8s


Frends.SFTP.DownloadFiles can't connect to server with keyboard-interactive authentication method

Task needs to implement keyboard-interactive authentication method which is not currently implemented.

This was fixed in PR #76


Automated Testing of Happy Path for presenting credential

[x] Test Development of present credential
[x]  AMTH Agent interface extended for send presentation request
[x]  PR Merged

This is completed in this PR - https://github.com/hyperledger/aries-mobile-test-harness/pull/45


Treat external content as pre-rendered

Bug/issue #, if applicable: rdar://78718811 #468
Summary
This cleans up a long standing design flaw of mixing local and external content.
History
Long before the initial open source release, we designed ExternalReferenceResolver and ExternalSymbolResolver as two facets of a mechanism to interface with other documentation sources. At the time, we thought that it would be a good idea to model the external pages the same as local pages so that all DocC's processing of local content would automatically apply to external content as well. Later FallbackReferenceResolver adopted the same pattern for filling in local content in a partial documentation build.
From the start, this decision had a couple of drawbacks;

Since the documentation context mixed local and external nodes, we needed to track which nodes were local and external to avoid rendering full pages for the external nodes. Also, the local context needed a mechanism for determining the URLs of the external content.
Since the documentation node models are initialized with the unprocessed markup, and then processed by DocC. Any external content needed to be turned back into markup to then be processed and rendered. This wasn't an issue for basic text formatting, but if the external content contained links, those links would need to be re-resolved in the local context where they most likely would fail to resolve.

Over time we added more features, some of which didn't work well with this design decision. The primary example is the support for page images. For external documentation sources to replicate the behavior of page images, the markup needed to reference the images by name and those images needed to be mixed with the other local assets from the local documentation catalog so that the images could be found when processing the markup and rendering the external content.
More recently, #710 added support for external content from other DocC documentation sources. This external content wasn't mixed with the local content and was modeled as already-rendered, so that DocC doesn't need to process or render it.
A guide through these changes
To address this design flaw, this PR makes a handful of changes, one leading to the other
New protocols
First, since ExternalReferenceResolver, ExternalSymbolResolver, and FallbackReferenceResolver are public protocols, it would be source breaking to add or remove functions to any of these protocols. In order to maintain source compatibility these protocols all needed to be deprecated with new protocols taking their place. Also, since DocumentationContext had public properties that held values conforming to these protocols, those properties also needed to be deprecated and replaced with new properties.

Looking for another name, ExternalReferenceResolver  became ExternalDocumentationSource. It returns LinkResolver.ExternalEntity (same as in #710) and is no longer a throwing function because it is passed a reference it already successfully resolved. Because the local context no longer decides the URLs for the external content, there is no need for a urlForResolvedReference(_:) API.

ExternalSymbolResolver because GlobalExternalSymbolResolver  since there could only ever be one symbol resolver for all external symbols references. Because external symbols are resolved using the symbol's precise identifier and later tracked with a reference, this protocol only has one function that returns both the external entity and its reference.

_ExternalAssetResolver only existed to workaround the issues with external page images and has no replacement. It is simply deprecated.

FallbackReferenceResolver and FallbackAssetResolver are combined into a single internal ConvertServiceFallbackResolver. These protocols were only ever intended to be used with the convert service as a mechanism for on-demand resolving references to local content in partial documentation builds. Because there's only one local bundle there's also only a single ConvertServiceFallbackResolver. Its API very much resembles the external documentation source's API with the added capability of resolving local assets. Even though the resolved entities represents "local" content, they shouldn't be processed and rendered in the partial build so for all intents and purposes they are external to the provided build inputs.

Tracking external symbols
Because rdar://116085974—which is a follow up to #710 for supporting external DocC symbols—isn't implemented yet. This PR needed to track the symbols resolved by GlobalExternalSymbolResolver and make sure that their references are associated with the conformances and declaration tokens of the local symbols that have some relationship to these external symbols.
For local symbols, this was tracked with two separate variables
var symbolIndex: [String /* symbol ID */ : ResolvedTopicReference]
var documentationCache: [ResolvedTopicReference: DocumentationNode]

Instead of adding a externalSymbolIndex (in addition to the existing externalCache), I identified that we need to track local and external content much the same way, but store different values. To abstract away the common behaviors I created DocumentationContext/ContentCache<Value> and used it to track the external content.
Various places that looked for the reference for a symbol ID needed to be updated to check for both local and external symbols.
Merging fallback link results
DocC gathers all external links and resolves them in a dedicated phase, but the fallback resolver resolves local links as part of the local link resolution. This required some changes to how the fallback results are gathered but gave a good single point to add fetch all the assets referenced by fallback entities and associate the data assets with the external entities without mixing any fallback content with the local content.
Using ContentCache for local content
After all the tests passed, I updated DocumentationContext to leverage the same ContentCache type for both local and external content. Doing so designs away some possible scenarios where a local value is updated in the documentationCache but not the symbolIndex or vice versa. This also found a handful of places where the symbolIndex was passed as inout but didn't need to be.
Dependencies
None
Testing
This can be tested using the bin/test-data-external-resolver and some <doc://com.test.bundle/something> links

Update the test resolver to return URLs to some images on the web for both "card" and "icon" type images.
"topicImages": [
  {
    "type": "card",
    "identifier": "some-external-card-image-identifier"
  },
  {
    "type": "icon",
    "identifier": "some-external-icon-image-identifier"
  }
],
"references": [
  {
    "type": "image",
    "identifier": "some-external-card-image-identifier",
    "variants": [
      {
        "url": "https:\/\/SOME_PATH_TO_SOME_IMAGE_HERE.png",
        "traits": [
          "1x"
        ]
      }
    ]
  },
  {
    "type": "image",
    "identifier": "some-external-icon-image-identifier",
    "variants": [
      {
        "url": "https:\/\/SOME_PATH_TO_SOME_IMAGE_HERE.png",
        "traits": [
          "1x"
        ]
      }
    ]
  }
],

Configure DocC to use the test resolver to resolve external links
export DOCC_LINK_RESOLVER_EXECUTABLE=$PWD/bin/test-data-external-resolver

In any project with symbols, add an article with external links in prose, curation, and @Links directives
# Some article

This page links to external documentation in a few different ways

Here's the link in prose: <doc://com.test.bundle/something>

@Links(visualStyle: compactGrid) {
   - <doc://com.test.bundle/something>
}

@Links(visualStyle: detailedGrid) {
   - <doc://com.test.bundle/something>
}

## Topics

- <doc://com.test.bundle/something>

Preview documentation for that project and navigate to the added article

Verify that the link in the prose displays the link with the resolved title as the link text.

Note that clicking the link won't work since there isn't a real page to link to.

Verify that both @Links groups display the card page image.
Verify that the curation displays the icon page image.

Navigate to a symbol that conforms to an external protocol (for example Equatable) or subclasses an external class (for example NSObject)

Verify that the Conforms To or Inherits From sections contains links with the resolved title as the link text.

Note that clicking the link won't work since there isn't a real page to link to.

Navigate to a symbol with a declaration that mentions an external type (for example an Int property, or a String argument, or a Bool return type)

Hover over the external type name token in the declaration and verify that the token becomes underlined to indicate that it's a link.

Note that clicking the link won't work since there isn't a real page to link to.

Checklist
Make sure you check off the following items. If they cannot be completed, provide a reason.

[x] Added tests
[x] Ran the ./bin/test script and it succeeded
[x] Updated documentation if necessary

@swift-ci please test

I don't think I'm fully aware about what is considered an external symbol. I know about links to external references, but, in which case I have an external symbol or resource? when mixing doc archives?

I don't think I'm fully aware about what is considered an external symbol. I know about links to external references, but, in which case I have an external symbol or resource? when mixing doc archives?

Basically, if there's no symbol with that unique identifier in any of the symbol graph, then that's an external symbol.
There are two different types of "external symbols":

Symbols in other modules, for example if a local symbol conforms to Swift/Equatable or has a function that returns Swift/Int.
Symbols in the same module in a partial symbol graph file (as described in this comment)

@swift-ci please test

@swift-ci please test

@swift-ci please test

@mayaepps @daniel-grumberg @sofiaromorales @patshaughnessy Is there anything else I can do to make it easier to review these changes? I was hoping to open new PRs that build on what's in this PR in the next couple of weeks.

@swift-ci please test

After some more extensive testing with a large, realistic documentation project, we were able to verify that Render JSON produced by the code in this PR vs. the main branch is equivalent. I'd go ahead and merge this 👍

@swift-ci please test


Powers in log args are incorrectly factored out during parsing

nerdamer('log(2*((a+b)^7))') => 7log(2(a+b)), cannot move out exponent in presence of factor, should be log(2)+7*log(a+b) (after simplification).
Bug is in nerdamer.core.js 8191.

Fixed in 8fc61717a69c0a2c1cb83690707e8e42047b47ee


Set correct location of typescript definition file

Fixing:
Could not find a declaration file for module 'nervjs'.
'./default/node_modules/nervjs/index.js' implicitly has an 'any' type.
Try `npm install @types/nervjs` if it exists
or add a new declaration (.d.ts) file containing `declare module 'nervjs';

Coverage remained the same at 94.172% when pulling 73e3a90de46c93cf1df2667e1607375f02d8d274 on bogdan:patch-1 into aaa405e79de5926e30ff07a0bb1b94dc994e9446 on NervJS:master.


Document naming convention for the config format

cc: @dingxiangfei2009 @antigravityla @trha

There is a proposed change as well for this in #27, but I'll merge this one anyway since it won't cause any harm.


Use capitalised source labels

Follow up to https://github.com/hrsh7th/nvim-compe/pull/91#issuecomment-769665330
Did I miss anything?

Thank you very much! LGTM

Thank you very much! LGTM


Node.js  Community Committee Meeting 2021-08-05

Time
UTC Thu 05-Aug-2021 16:00 (04:00 PM):

Timezone
Date/Time

US / Pacific
Thu 05-Aug-2021 09:00 (09:00 AM)

US / Mountain
Thu 05-Aug-2021 10:00 (10:00 AM)

US / Central
Thu 05-Aug-2021 11:00 (11:00 AM)

US / Eastern
Thu 05-Aug-2021 12:00 (12:00 PM)

EU / Western
Thu 05-Aug-2021 17:00 (05:00 PM)

EU / Central
Thu 05-Aug-2021 18:00 (06:00 PM)

EU / Eastern
Thu 05-Aug-2021 19:00 (07:00 PM)

Moscow
Thu 05-Aug-2021 19:00 (07:00 PM)

Chennai
Thu 05-Aug-2021 21:30 (09:30 PM)

Hangzhou
Fri 06-Aug-2021 00:00 (12:00 AM)

Tokyo
Fri 06-Aug-2021 01:00 (01:00 AM)

Sydney
Fri 06-Aug-2021 02:00 (02:00 AM)

Or in your local time:

https://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Community Committee+Meeting+2021-08-05&iso=20210805T1600
or https://www.wolframalpha.com/input/?i=04PM+UTC%2C+Aug+05%2C+2021+in+local+time

Links

Minutes Google Doc: https://docs.google.com/document/d/1CIdfWEQumHMuogvmGRgEwSzB6uOw3Stms3TXaubE4yI/edit

Agenda
Extracted from cc-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
Invited

CommComm Members: @nodejs/community-committee

Observers/Guests
Feel free to follow along on the YouTube live stream, or attend meeting as a guest
by calling in to Zoom, using the links below. If you will be attending as a guest,
please comment on this issue to let us know you'll be joining.
Notes
The agenda comes from issues labelled with cc-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.
Joining the meeting

Link for participants: https://zoom.us/j/95198277339
For those who just want to watch: https://www.youtube.com/channel/UCQPYJluYC_sn_Qz_XE-YbTQ

Invitees
Please use the following emoji reactions in this post to indicate your
availability.

:+1: - Attending
:-1: - Not attending
:confused: - Not sure yet

I suggest we cancel as the Next-10 meeting is at the same time and many of those who regularly come to the Community committee meeting are part of the Next-10 effort.

Thanks all, see you next time! 😄
Wish I could've made it to the Next-10 session today, looking forward to hearing about the great things that come from it. 🚀


Code review

use Disposables
use notification for errors
add CI configurations (you must activate CI in Travis CI and AppVeyor)
add CoffeeLint configuration
use Opn (don't reinvent the wheel)
works with standard Atom and Nuclide
fix keymaps bindings and change to ctrl-shift-q and cmd-shift-q on OSX

Fix #28, #26, #25, #23, #21

Any remarks ?

@ldez thank you for your contribution. I've only glanced it, but I'll be looking at it soon.

@magbicaleman now you can activate CI with Travis CI and AppVeyor
Can you publish a new version ?

I have Travis CI activated (failed), not yet with AppVeyor. I'm assuming the AppVeyor CI, is to test out the plugin in the windows environment.


Doesn't detect first visited page

Environment

Operating System: Windows_NT
Node Version:     v16.14.2
Nuxt Version:     3.2.3
Nitro Version:    2.2.3
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      runtimeConfig, modules, gtag, vite, css, build, nitro, sitemap
Runtime Modules:  `@pinia/nuxt@0.

Reproduction
No reproduction.
Describe the bug
Immediately after opening a website the first visisted page 'page_view' is not sent to Google Analytics, so it doesn't show up in Realtime or Engagement reports.
If you then start navigating to other pages it works, the problem only applies to the first page visited.
Additional context
No response
Logs
No response

Same issue

Mmmh… That's unfortunate. Any idea why Google Analytics might not pick up the initial page_view?

Is this being looked at? I feel like this is a major bug.

It seems that the module is correctly setting up Google Analytics, but it's not sending the initial page_view event. You can manually track the initial visit by sending a page_view event after the Google Analytics script is loaded.
// Send initial `page_view` event
useGtag('event', 'page_view', {
  page_location: window.location.href,
  page_path: useRoute().path,
  page_title: document.title,
})

I have incorporated the initial page_view into the plugin itself. Available in v0.5.5.
Please test it. Feedback much appreciated!

Thanks for the quick fix!
In my case, sending events has never worked with this plugin (or GA4?) unless I add send_to: 'G-...' to the event parameters, so that piece of code won't work.
Has anyone experienced the same problem?

@soylomass Are you sure the GA ID is set in your nuxt.config.ts? Please create a separate issue including your Nuxt configuration if that issue persists. Thanks!

I have incorporated the initial page_view into the plugin itself. Available in v0.5.5. Please test it. Feedback much appreciated!

Thanks for the update.
I just tested it and it still does not seem to work.. In incognito and first page load, analytics only gets the event name 'first_visit'. The 'page_view' is still not being recognised by Google  Analytics.

@ttonyh Thanks for verifying. I believe so, too, since gtag.js will handle tracking all by itself. I will probably hide the initial page_view behind a module config flag. So everyone is happy. 🙂

@ttonyh I have just released v0.5.6 with the manual tracking removed.
If another issue persists, please open a separate issue.


chore: move Go services to different repo

removes packages/services/ to a new repo
may even want to consider breaking this up further into js/client packages and
solidity/blockchain packages. despite the autogenerated inter-language type
dependencies, a monorepo seems a bit of a mistake between all these disparate
domains
also removes tutorials/ we wont need those where we're going

@chlwys for general awareness
@darrylyeo to confirm for me this isnt a footgun :)


Sharepoint incorrectly produces N/A for policy 3.2 when using service principal but it should perform the policy check because the needed fields exist

💡 Summary
The Rego code for Sharepoint policy 3.2 incorrectly produces an N/A when you run with a service principal. I guess the coder thought that the Get-PnPTenant cmdlet does not contain the necessary fields, but based on my testing, it does contain them. I temporarily changed the Rego code and it worked when running with a service principal. The fix to correct this is easy and I provide a code snippet below that I tested with. The fields needed are FileAnonymousLinkType and FolderAnonymousLinkType.
Screenshots of the problem
Run the Sharepoint provider with a service principal and you will get the following:

After I fixed the code, this is what the report looks like. It matches the output when running with interactive authentication.

Code Fix
I commented out the lines that should be removed.
tests contains {
    "PolicyId": "MS.SHAREPOINT.3.2v1",
    "Criticality": "Shall",
    "Commandlet": ["Get-SPOTenant", "Get-PnPTenant"],
    "ActualValue": [FileLinkType, FolderLinkType],
    "ReportDetails": FileAndFolderLinkPermission(FileLinkType, FolderLinkType),
    "RequirementMet": Status
} if {
    # input.OneDrive_PnP_Flag == false
    SharingCapability == ANYONE

    FileLinkType := Tenant.FileAnonymousLinkType
    FolderLinkType := Tenant.FolderAnonymousLinkType
    Conditions := [
        FileLinkType == 1,
        FolderLinkType == 1
    ]
    Status := count(FilterArray(Conditions, true)) == 2
}

# Test for N/A case
tests contains {
    "PolicyId": PolicyId,
    "Criticality": "Shall/Not-Implemented",
    "Commandlet": ["Get-SPOTenant", "Get-PnPTenant"],
    "ActualValue": [],
    "ReportDetails": CheckedSkippedDetails(PolicyId, Reason),
    "RequirementMet": false
} if {
    PolicyId := "MS.SHAREPOINT.3.2v1"
    # input.OneDrive_PnP_Flag == false
    SharingCapability != ANYONE
    Reason := NAString(SliderSettings(2))
}

# tests contains {
#     "PolicyId": PolicyId,
#     "Criticality": "Shall/Not-Implemented",
#     "Commandlet": [],
#     "ActualValue": [],
#     "ReportDetails": NotCheckedDetails(PolicyId),
#     "RequirementMet": false
# } if {
#     PolicyId := "MS.SHAREPOINT.3.2v1"
#     input.OneDrive_PnP_Flag == true
# }
#--

Implementation notes

[ ] Modify the Rego code
[ ] Double check if we need to modify any of the functional tests
[ ] Revise the unit tests that pass the OneDrive_PnP_Flag or modify them if they no longer make sense after the code update

@mitchelbaker-cisa You can lump this with the quick fix in #1220.

You can probably take care of this one at the same time as well to maximize pull request resources: #1268 If you agree, you can self-assign.


(BUG) [RN] The blank invite page is displayed after clicking the "Invite+" button

Precondition:
The user is signed in and the "Home" page is opened
Steps to reproduce:

Click the "Invite+" button
Pay attention to the blank page and error messages on the console

Actual result: The blank invite page is displayed after clicking the "Invite+" button
Expected result: The invite page with content should be displayed after clicking the "Invite+" button

Checked on native V 1.3.1-1 QA 1.6.1-3
Desktop: Windows 10 // Google Chrome  86.0.4240.75
https://www.screencast.com/t/WEGVksht

invite is not relevant. I'll update when we enable it


Youtube hard

Youtube is listed as impossible, but the description clearly describes how to close the account, which is rather simple.

Hello @hobarrera ,
This repo is not being maintained anymore, but we are trying to keep it alive on a fork here, would you kindly submit your PR there and close this one here? :)

Closing due to project deadness.


 If yes, I'll close this PR.
If this function doesn't exist, view_cell() will not work.

Doh! Thanks. Looks like I was a little overzealous in fixing a merge conflict late last night.


allow swapping out openssl for rustls

This is a pattern that is somewhat standard in other crates:

sentry
github-rs

But it only actively stops you from pulling in openssl if all crates let you customise this.

Thanks. Seems pretty reasonable and looks good to me from a quick glance. Will give it a quick spin in a min

i take it this isn't usable from slack-rs because it uses tungestenite which doesn't have a rustls option.
also the request version needs bumping to "^0.9.6" otherwise the feature doesn't exist

i take it this isn't usable from slack-rs because it uses tungestenite which doesn't have a rustls option

You could make it usable from slack-rs by exporting similar features. Although it depends on what the rest of its dependencies pull in. I can see that tungstenite has some native tls option. It probably maps to the same thing, but have not tested. That's kind of an orthogonal problem because the default mode of this crate isn't changed, so it won't cause any problems for slack-rs. This is only a benefit for people using slack-rs-api directly atm.

the request version needs bumping to "^0.9.6" otherwise the feature doesn't exist

The reqwest dependency is compatible with 0.9.6 because it specifies 0.9 in both your Cargo.toml. Cargo generally picks the latest compatible with everything, but can bump the minimum to 0.9.6.

Bumped it. Now if you cargo build without a lockfile it'll pick 0.9.20.

thanks


Cant open terminal

Hi,
Thanks for this repo, its very useful.
I have a problem when I do: Terminal -->New Terminal

Do you have any idea what is causing the problem?
Thanks

Hey did they fix this?

Hey did they fix this?

Nope! still broken

Fixing now!

I'm updating to Cursor 0.42 right now. That release should have the fix!

@elmerfds can you help me test a new build? kylecarbs on Discord.

@elmerfds can you help me test a new build? kylecarbs on Discord.

Unfortunately the new release didn't fix it

@elmerfds can you help me test a new build? kylecarbs on Discord.

Unfortunately the new release didn't fix it

same error just installed it.
is the work around just using another termimal?
sorry stopped using cursor for a while so forgot if there wany advantage of using the built-in terminal.

me too

0.43.5,still broken


Breaking(?) change from Behat/Gherkin should be outlined in changelog?

Behat/Behat 3.15.0 bumped Behat/Gherkin
The "simple" change of https://github.com/Behat/Gherkin/commit/5a0836db6fd4f0d6fe1db6dfff5118ab615681b4 however breaks all TableNodes that use JSON data with escaped backslashes.
In our case we had:
    And user "admin" creates global flow with 200
      | name      | Admin flow                       |
      | class     | OCA\FilesAccessControl\Operation |
      | entity    | OCA\WorkflowEngine\Entity\File   |
      | events    | []                               |
      | operation | deny                             |
      | checks-0  | {"class":"OCA\\WorkflowEngine\\Check\\FileName","operator":"is","value":"foobar.txt"} |

working for years, and the above change makes touch all tables and escape the slashes another time
    And user "admin" creates global flow with 200
      | name      | Admin flow                       |
      | class     | OCA\FilesAccessControl\Operation |
      | entity    | OCA\WorkflowEngine\Entity\File   |
      | events    | []                               |
      | operation | deny                             |
      | checks-0  | {"class":"OCA\\\\WorkflowEngine\\\\Check\\\\FileName","operator":"is","value":"foobar.txt"} |

We can of course do that, but I think it should at least be added to the changelog for clarity?
There already was another question about it in https://github.com/Behat/Gherkin/issues/268
But the library issues/changelog might not be what most users check.

Thanks @nickvergessen your suggestion to mention this in the changelog seems reasonable. @acoulton how should we handle this?

My suggestion would be to add a "Breaking" section to https://github.com/Behat/Behat/blob/master/CHANGELOG.md#3150---2024-10-29 and manually edit it also into the existing tag/release description (without a further release for now)

Hmm - I'm not sure.
We could flag it in the behat changelog (I hadn't actually noticed that the minimum requirement was bumped, as it was done direct on master before we took over).
However, ultimately the break is in<EMAIL_ADDRESS>and will affect people even if they stick with<EMAIL_ADDRESS>So the main / correct place to highlight it would be the gherkin CHANGELOG (where it is also not clear). It's only coincidence that both packages are from the same org, it could just as easily be an external dependency causing the problem and I don't really want a convention that the behat changelog details the changes in other packages as that will be impossible to maintain and will give people a false sense of security if we miss something that affects them.
tl;dr - if people are upgrading behat/gherkin then they should be checking the gherkin changes, even if they're upgrading behat at the same time. But we definitely need to fix the gherkin changelog asap.

The Behat changelog should highlight the fact that it migrates to a new major version of behat/gherkin though.

@stof it doesn't, it bumps from ^4.9.0 to ^4.10.0 https://github.com/Behat/Behat/commit/382826ef35ee94c03a968d370f8878ea63335767

So it doesn't bump a major, but a minor. Might still be worth to outline, to give users a hint for related changelogs :)

Added a hint in #1517

Thanks a lot everyone :+1:


Static code analysis using SonarQube - sonarcloud.io

With integration with Travis CI - fail the build if SonarQube finds a problem.

Done.


using wss:// style to access emqttd

Environment

OS: centos7.1
Erlang/OTP: 7.3
EMQ: 2.0.7

Description
How to use wss://xxxx:8084/mqtt/  style to use emqttd?  notice:  like https style.
I use  http://www.hivemq.com/demos/websocket-client/  to test,  if I don't select ssl, it's working, if I select ssl, it's not working.

@maxshucn The hivemq demo uses a JS (mqttws31.js) in browser to access the MQTT broker, and thus it won't support self-signed ssl certificates by default - it depends on the trusted CA certificates installed in your browser.
You need a CA SSL certificate, and configure it in your emq.conf file.
If you just want to have a try with you self-signed certificate (there's already one configured in the emq.conf), try to install the cert in your browser by accessing 'https://xxxx:8084/mqtt', and then select 'continue' if any warning about security.
The mqttws31.js  uses the 'wss://' style to connect to the Broker, you could dive into the code if you want to know more.

I had imported my self-signed certificate to ie. but not working...

@maxshucn Use the original self-sgined certificate come with EMQ, and do not modify the emq.conf. Then install the certs by accessing 'https://xxxx:8084' and click continue or 'always trust' when the address bar becomes red. This works fine for me.
If not, try the similar procedure with Chrome or other web browsers.

@maxshucn Please fix your SSL configurations of EMQ first. I will close the issue now.  @terry-xiaoyu

:-(


Project_DB_Data_Automation_REFramework_Priyesh

The objective is to develop an automated pricess that fficiently retrieves all records from the "Vajrang' database and generates individual text files for each record, containing the first name, last name, and suffix of the individuals listed.
Upload it to the bucket storage and send Report.
Resources:-
Asset Names- DbConnString- to store connection string as secure string value, Credential type.
Queue Name- Dbqueue
Storage Bucket Name- SbVajrangUsers

Completed the project.


Uncaught Error: Computed Property declared without a property function

With ember-cli 0.2.7 and ember-cli-flash 1.2.0 I'm getting this error stopping the entire Ember app from loading:
Uncaught Error: Computed Property declared without a property function
computed @ ember.debug.js:10586
add @ computed.js:17
(anonymous function) @ object.js:14
Stems from the following line within: https://github.com/poteto/ember-cli-flash/blob/develop/addon/flash/object.js
totalTimeout: customComputed.add('timeout', 'extendedTimeout').readOnly(),

Hey thanks for the report! This is a bug, I'll get a fix out soon. Sorry for the trouble

So I've been trying to reproduce the issue but I haven't had much luck. Could you share more details?

I've the same problems - @twest7 what ember version do you have? I am on 1.11

almost certainly related to the computed property changes introduced in 1.12

Also experiencing the same issue, using Ember 1.11.1.

Hey guys, you should try to upgrade your Ember versions to at least 1.12. If this is not possible, you can use 1.1.2– https://github.com/poteto/ember-cli-flash/releases/tag/1.1.2 which still works with Ember 1.11.

@nicolas-dular @Jellyfishboy Good news, 1.3.2 now works with Ember 1.11.x, thanks to @truenorth :)

thanks @poteto in the meanwhile I've upgraded to ember 1.13 so I can use your libary and it works perfectly, thanks :+1:


Replace ScanStream with Lua Scan

We are using aedes & aedes-persistence-redis in production, and we had some CPU load issues on our node workers due to the large number of retained messages in Redis. I narrowed down the performance issue to scan_stream in ioredis.
This change offloads the work to the Redis server, and results in a very noticeable performance improvement in node with very little impact to Redis. The performance improvement should be very similar to my other pull request to mosca: mcollina/mosca#379

Thanks for contributing this here!

@mcollina moved to lib/match.js. thanks for reviewing this, and for your work on mosca & aedes!

Merged, thanks!


Left Hand Side Table of Content

This pull request resolves the LHS of issue #93

@AceTheCreator could you provide a bit of detail in the PR descriptor e.g. what you did, how it provides it, maybe a screenshot of what it looks like etc.
Also when i visit a page i don't see any table of contents e.g. https://deploy-preview-104--boring-fermat-22cb64.netlify.app/concepts/bitcoin

@rufuspollock there's a table of content on the RHS that says on this page with an arrow

@AceTheCreator great - yes please make it open by default (we don't even need the open or closed part i think).


Pico W fails to connect to Adafruit IO during the first boot of WipperSnapper

The Raspberry Pi Pico W should attempt to connect to Adafruit IO more than once per run (prior to the reboot). Currently, the WDT fires after the first failure to connect to Adafruit IO:
12:35:09.274 -> Attempting to connect to WiFi...
12:35:09.274 -> Attempting to connect to WiFi...
12:35:17.587 -> Attempting to connect to WiFi...
12:35:17.587 -> Attempting to connect to Adafruit IO...
WDT EXPIRED - REBOOT
12:35:37.315 -> Attempting to connect to WiFi...
12:35:37.315 -> Attempting to connect to WiFi...
12:35:45.623 -> Attempting to connect to WiFi...
12:35:45.623 -> Attempting to connect to Adafruit IO...
WDT EXPIRED - REBOOT
12:36:05.389 -> Attempting to connect to WiFi...
12:36:05.389 -> Attempting to connect to WiFi...
12:36:13.702 -> Attempting to connect to WiFi...
12:36:13.702 -> Attempting to connect to Adafruit IO...
12:36:19.669 -> Registering hardware with WipperSnapper...
12:36:19.669 -> Registering hardware with IO...

This has been addressed by #514


inrange & inlist marked as not explicit if statements

Specify the condition in the if statement: Always explicitly specify the condition in the if statement. For example, declare if var == 1 instead of if var.

This marks statements such as
if inrange(z,a,b)
if inlist(z,a,b,...)
as not explicitly stated.

corrected in v1.02


Test CI

[ ] Tests added / passed
[ ] Passes black dask / flake8 dask

test_json_compressed[xz] fails due to a change in the fsspec==0.4.5 release, but has been fixed upstream in https://github.com/intake/filesystem_spec/pull/139. Apologies, I should have raised an issue in the issue tracker here to bring attention to this.
ping @martindurant @TomAugspurger would it be possible to get a new fsspec release?

I can do one in ~5 hours or tomorrow morning.
On Wed, Sep 18, 2019 at 3:47 PM James Bourbeau<EMAIL_ADDRESS>wrote:

test_json_compressed[xz] fails due to a change in the fsspec==0.4.5
release, but has been fixed upstream in intake/filesystem_spec#139
https://github.com/intake/filesystem_spec/pull/139. Apologies, I should
have raised an issue in the issue tracker here to bring attention to this.
ping @martindurant https://github.com/martindurant @TomAugspurger
https://github.com/TomAugspurger would it be possible to get a new
fsspec release?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/pull/5415?email_source=notifications&email_token=AAKAOIU7G46J57ESRYHNKQ3QKKHWNA5CNFSM4IYDMCT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7BMXLY#issuecomment-532859823,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAKAOIR5Y3HLNCUVKUBRMMLQKKHWNANCNFSM4IYDMCTQ
.

I'll start an fsspec 0.5 release now.

Thanks for pushing out a new fsspec release @TomAugspurger. It looks like tests are passing now (woo!). Do we also want to bump the minimum fsspec version to 0.5.1 in setup.py?

I didn't follow the fsspec issue too closely. From a skim, it seems sensible to bump the required version though.


Update fault diagram

Update fault diagram tunable section

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65ad2dcfc319e86a4ead6a35--harness-developer.netlify.app


Fix non-default library path grabbing

The regex is (now?) broken for the format of the VDF file. I used a library to parse it correctly and just grab the paths from each individual library.
Also not 100% sure but this should work for Linux/Mac paths now

should work for Linux/Mac paths now

Yep, but I think there's a still a dependency on the Windows registry 😅


SNZB-06P Light sensor random readback

The snzb-06p show random light detection status. No evidence of error. Do you have any solution?

You can collect debug logs and make sure the integration is displaying what the cloud is sending
https://github.com/AlexxIT/SonoffLAN?tab=readme-ov-file#issues

Here is a series of test. Looks like the light detection is updated when human presence is detected. When the room is dark the "brState" is missing.
Event with light in the room:
2024-10-07 10:56:20.965 DEBUG (MainThread) [custom_components.sonoff.core.ewelink] a4800a70e4 <= Cloud3 | {'sensitivity': 3, 'judgeTime': 15, 'human': 1, 'trigTime':<PHONE_NUMBER>885, 'brState': 'brighter'} | None
2024-10-07 10:56:40.037 DEBUG (MainThread) [custom_components.sonoff.core.ewelink] a4800a70e4 <= Cloud3 | {'sensitivity': 3, 'judgeTime': 15, 'human': 0, 'trigTime':<PHONE_NUMBER>988} | None
Event without light:
2024-10-07 10:59:22.519 DEBUG (MainThread) [custom_components.sonoff.core.ewelink] a4800a70e4 <= Cloud3 | {'sensitivity': 3, 'judgeTime': 15, 'human': 1, 'trigTime':<PHONE_NUMBER>951} | None
2024-10-07 10:59:41.080 DEBUG (MainThread) [custom_components.sonoff.core.ewelink] a4800a70e4 <= Cloud3 | {'sensitivity': 3, 'judgeTime': 15, 'human': 0, 'trigTime':<PHONE_NUMBER>873} | None

It's usual situation for many motion sensors on market. They updating light only with motion event.

how I can do it?


No title fetching on mobile

I've recently noticed that link paste action doesn't fully work on my Obsidian iOS version. I'm saying fully because whenever I paste a link, it's pasted with Markdown link formatting but there's no title fetching happens. Text part just stays blank.
I've tried waiting and checking if there might be something else causing an issue but everything seems fine. I'm not sure if it's a mobile limitation or a bug but I'd like to have this plugin working as intended on my phone too.

I’m having the exact same problem.

Do you have "Enhance Default Paste" on?

I have the same problem. i paste a URL and it produces a Markdownlink with an empty Textfield.
"Enhance Default Paste" is on.
I was very hopeful because that would have simplified the link insertion on mobile very much.

iOS 15.7.3
Obsidian 1.4.3
Auto Link Title 1.4.1

Ditto. Read the docs which day to use tap and hold and it doesn't work.
However when I use the ribbon it works.

https://github.com/zolrath/obsidian-auto-link-title/issues/46
at the same post


Red Headband - Fixing random crashing bug (thanks to Discord's Cookiechu#2073 for finding this bug - sorry for the double crash : p)

Broke cookiechu game :/
Essentially, random being called there returns 0, 0 crashes game.

How I'm breaking stuff with random is something I just don't get -_-
Have to change the way I randomize that but for now... yeah, for now, DrawAction should save cookiechu's run.

And done.


Trimmed down app for prototyping

Time Tracking: MA-33
This is done when:

[x] A trimmed down campus mobile app has been setup for rapid prototyping
[x] Home view displays

(1) prototyped Native card
(1) prototyped Web card

[x] Onboarding, Map, Notifications views remain in-tact
[ ] Prototyping documentation added to Collab/Readme

Trimmed down campus-mobile prototype available on branch prototype


Patch edk2-ovmf file to fix UEFI support

The file 50-edk2-ovmf-cc.json is used by Nova in get_loader() when lauching UEFI instances without Secure Boot.
It only supports machine type pc-q35-rhel8.5.0. However, with recent nova-compute container images built on CentOS Stream 8, the machine type is pc-q35-rhel8.6.0, which results in failures to launch instances with:
nova.exception.UEFINotSupported: UEFI is not supported

There is a fix for RHEL9/c9s [1], but not for RHEL8/c8s. Also see [2] for more details.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=2090752
[2] https://bugs.launchpad.net/nova/+bug/1955035

I've just realised this needs to be made specific to centos as it might fail on Ubuntu.

I've just realised this needs to be made specific to centos as it might fail on Ubuntu

oops, you are quite correct.


Update PNG rendering

Use the zscale algorithm from katsdpsigproc now that it has moved there. The rest is largely a cut-and-paste job from render.py in katsdpimager. The commit messages describe the changes I needed to make for continuum images.
@bmerry, as we discussed, this (or a variant) could go somewhere else where both katsdpimager and katsdpcontim can import it. I suspect zscale could also leave katsdpsigproc and join it as well. As such this PR is really just an indication of how things will work for the continuum case so we can identify whether or not the implementations have enough in common to move things somewhere else. I'll put a 'do not merge' on this while we work that out.

@bmerry I've added an option to change the facecolor of the plots and fixed up the default bounding box range. Can you please have one more look.
At the moment the tests of png output just involve checking that an image is produced. This could possibly be expanded but will need some way of reading png output into an array to check the pixel values (pillow probably will do). I think any further tests can wait until this ends up in its own repository.

At the moment the tests of png output just involve checking that an image is produced.

I think that's fine. It really needs a human to look at them to see if they're "right" e.g. text is all readable, doesn't overlap, sane colour scheme etc.
I'd suggest we merge this; moving the code to a common place can happen afterwards.


Suggestion: <Link> should always render an <a> (or at least have the option to do so)

Currently, <Link> not render an <a> when its child is a single ReactElement, but does render an <a> otherwise.
Our team is using wouter at scale (overall we love it!) but we've found this behavior to be problematic, for a few reasons:

Inconsistent presence of <a>-specific browser features, like right-clicking to open in a new tab, or copy link address.
Accessibility is much harder without <a>.
Inconsistent behavior with CSS-in-JS, because styles applied on <Link> are applied to the child component's styles applied to the child component. (At least they are with styled-components.) This breaks use cases where two DOM nodes would have different behavior than one DOM node with combined styles, like flex containers, absolute-positioned elements inside relative containers, etc.

The recommended pattern of putting an <a> inside a <Link> leaves it up to the caller to always remember to do this. In a large team with a large codebase, we've found this to be a common source of errors, especially for new team members who are more familiar with other routing libraries, the vast majority of which always render an <a>.
For this reason we stopped using <Link> as-is and instead we use a wrapper component that always creates an <a>.  I'm not suggesting that the current behavior is always bad, but IMO it's a bad *default* behavior because it makes it too easy to create difficult-to-style, inaccessible code.
Would you consider changing the behavior of <Link> to always render an <a>?  If no, would you consider adding an option to <Link> (or a new component) to enable always-render-a-DOM-node behavior?
In case it's helpful to others, below is our current wrapper component. It's missing some features (e.g. forwardRef) that we didn't have time to implement yet.
To make it less likely that users would accidentally import Link from wouter (VS Code's auto-import feature makes it trivially easy to make this mistake when other imports from wouter are used), we created a new wrapper package that re-exports all the other wouter exports that we use, and prohibit use of wouter imports elsewhere in our codebase.
import React, { isValidElement } from "react";
import { Link as _Link, LinkProps } from "wouter";

export { Router, Route, Params, Switch, Redirect, useLocation, useRoute } from "wouter";

/**
 * Wrap wouter's <Link> component to ensure that an <a> element is always
 * created. This ensures that you can style a Link and its child component
 * without worrying about the styles being squished together in one component at
 * runtime. It's also better for accessibility, and enables <a>-dependent
 * features like "open in new tab" right-click actions in the browser.
 */
export function Link(props: LinkProps) {
  const { to, href, children, onClick, ...rest } = props;

  // wouter tries to treat mailto links as regular URLs, and it tries to put
  // them into the browser history stack, which fails. So just use plain links
  // in that case.
  if ((to ?? href)?.toLowerCase().startsWith("mailto:")) {
    return <a {...props} />;
  }

  if (!isValidElement(children)) {
    return <_Link {...props} />;
  }

  return (
    <_Link to={to ?? href} onClick={onClick}>
      <a {...rest}>{children}</a>
    </_Link>
  );
}

Hi! We addressed this in the newest version, see https://github.com/molefrog/wouter/releases/tag/v3.0.0-rc.2 (link composition)
I didn't have time to work on the library properly dec/jan, but I'll try to make a final release soon. I still have to update the docs to match the new API, but this is taking ages for me sorry.

Hey @molefrog please dont feel sorry about this, even though words cannot do justice just how much I deeply appreciate the effort from you and your team building and maintaining open source software like this, thank you for all that you have done!
On another note, the new release looks awesome, thanks for taking into consideration all the feedbacks!
Hope you have a great week ahead!

Hi, the new release is out including the new documentation. Can you take a look:
https://github.com/molefrog/wouter?tab=readme-ov-file#link-hrefpath-
Can I close this issue if everything looks good?

Looks great, thanks!


Correction for raw affiliation CREM, University of Rennes, France

Correction needed for raw affiliation CREM, University of Rennes, France
raw_affiliation_name: CREM, University of Rennes, France
new_rors: 015m7wh34;0047rmf80
previous_rors: 015m7wh34
works_examples: W4322744220
contact: 46ede1c5a666c7d20840a2b16baee2a3:eee42ae6fb64fb44785e1f1fc3dbeeb0 @ univ-rennes.fr

This issue was accepted and ingested by the OpenAlex team on 2024-10-10. The new affiliations should be visible within the next 7 days.


Add favicon

Add favicon to the website

can i work it

I have added favicon and I made a pull request about it.


Modal UI issues

Steps:

Click on a service
Go to the Pod menu and select execute logs

Issues:

[ ] Need the modal to take up most of the screen.  kinda like old rancher 2

[ ] Add close x to top right corner

[ ] show connection state as explicit text

[ ] Don't close on background page click or escape key

[ ] Add boarder/show/fade-out background/something to separate it from the background page.

Here is old rancher
Old Rancher

Date - 11/14
Verified fixed


Merge Uat ke Master 26 Sept 2017

Coverage increased (+0.6%) to 72.673% when pulling 8c81a671ef4747d662321174a826273889f43577 on uat into 117f479f0902495993c36b99378a1d0e241a994e on master.


University of Alberta added to list of schools

@Dricmoy I have to close this request without merging, because you requested to add a non-existent domain to this repository: Host ualberta.ab.ca not found: 3(NXDOMAIN) Please ensure that you are familiar with this repository rules located at the bottom of this page and submit a new request with the correct information. Thank you for your understanding!

@philipto the host should be ualberta.ca, I don't exactly know why the ab is added. Could you please help me with this, thanks a lot.


how to do aggregation with feathers-objection?

I noticed that there are no examples when doing aggregation with feathers-objection.
How should it be done? I can't seem to find any.
I just need to do a simple sum and group by.
Please direct me to where I can find more information.
Thank you.

GROUP BY queries are not supported in feathers-objection and can be run directly with knex.

@dekelev, thank you for your prompt answer. I appreciate it a lot.
Can you guide me on how that can be done or can you refer me to an example? Not really sure how to reach knex from feathers-objection -> objection -> knex.

Sure. Take a look at the Initializing the Library section in the docs.
You'll see that inside your objection.js file, you should run app.set('knex', knex), so to run query with Knex directly later, you simply need to get it back from the app with const knex = app.get('knex') and use it like this: knex.raw('SELECT * FROM ...') or use its built-in methods like this: knex('users').groupBy(...).

Just to add, you should also be able to access the Objection model from the service like app.service('users').Model to use Objection's query builder.
app.service('users').Model.query().groupBy(...)

@dekelev, @robbyphillips Thank you for these. These are very helpful

Also, you should be able to write the query inside the model and expose it via the modify functionality https://github.com/feathersjs-ecosystem/feathers-objection#query-operators and https://vincit.github.io/objection.js/api/query-builder/other-methods.html#modify

Any idea on how to reset the select so that I don't have to include the Model.id?


Update workflow figure in HoVerNet

Part of https://github.com/Project-MONAI/MONAI/issues/5181.
Description
Update the workflow figure to avoid license issues.
Status
Ready

/build


Add config option to set default mode on markdown widget

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

I want to be able to set the markdown widget in markdown mode by default and keep rich text as optional.
Describe the solution you'd like

a solution could be when defining modes for the markdown widget on config.yml to honor the array order:
(e.g. modes: ["raw", "rich_text"], should set markdown by default`)
Additional context

default:

with modes: ["raw", "rich_text"]:

Hi @cdeath, please note that Rich Text/Markdown selection is "sticky" - the preference is persisted in local storage.

@erezrokah even better... but most will never touch the preference and i want my audience to use markdown primarily. if one team member wants to use Rich Text it's up to him (and to take the blame for breaking stuff).


[FEA] For hash joins where the build side can change use the smaller table for the build side

Is your feature request related to a problem? Please describe.
In some joins, like an inner join, we can pick either left or right as the build side. Right now we always pick the right table as the build side. That is not a good solution, but oddly it has worked out really well in most cases.  We should have the join code so that if it pulls from what we guessed the build side to be and it is larger than a single batch, then we try to pull from the other side to see if it is smaller.
This is not really ideal because after getting a single batch we don't know if it is the last batch or not. We have some optimized code where it in some cases we can tag a batch as the final batch, but it would be good to at least have a follow on issue to try and add in this same kind of functionality as a follow on piece.

The ask from the user is at least to make Full Outer Join choose the right build side.
Of course, if we can make both inner join together with Full Outer Join make the right decision that is better

build