Add support for "Is it going to rain?"

Based on the forum post:
https://www.domoticz.com/forum/viewtopic.php?f=65&t=13938
Which is the Python rewrite of buienradar_rain_example.pl which is on domoticz/scripts
These scripts works with a percentage device and shows the average expected rain for the total period (coming 2 hours).
There is also a LUA script:
https://www.domoticz.com/wiki/Is_it_gonna_rain
Basically they all retrieve their data from:
http://gadgets.buienradar.nl/data/raintext/?lat=52.1&lon=4.3
That data is explained at
http://www.buienradar.nl/overbuienradar/gratis-weerdata#Neerslag lat lon
Question is:  what to display?
Is it raining or going to rain with XXX minutes seems most useful.
This would need a "Switch" or "Selector Switch" (what is the difference?) to be set to true or false.
It is also possible to create a "Rain" device. But that stores the rain that actually has fallen. It wants a rate and counter: https://www.domoticz.com/wiki/Domoticz_API/JSON_URL's#Rain
So that is not the most logical device to use. And it is a bit unclear to me what the RAINCOUNTER value means.

Choosing the right device is indeed not easy. I use a "custom sensor" but is has some (2 in fact) issues.
My implementation can be found on: https://github.com/seventer/raintocome

The Rain device can't be used for this, because it is indeed showing the rain that actually has fallen.
RAINCOUNTER is showing the total amount of rain that has fallen (so since the device has started measuring the rain fall).
I am using a humidity sensor which can show the values between 0 and 255. That way you can also use the dry and wet values.

But using a custom sensor maybe makes more sense.

Any news on this one. Your plugin is working perfectly fine on my Synology NAS, thumbs up for that! I would also like to have rain prediction so I don't have to maintain a seperate script for that.

See pull request #8.

solved


Unable to parse configuration: EOF

heketi deploy, but it is not running, the error log:
deploy-heketi-559446b649-bbgm6      0/1       CrashLoopBackOff   4
Setting up heketi database
File: /var/lib/heketi/heketi.db
Size: 0               Blocks: 0          IO Block: 4096   regular empty file
Device: fd00h/64768d    Inode: 168112378   Links: 1
Access: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2018-08-15 09:06:07.875238074 +0000
Modify: 2018-08-15 09:06:07.875238074 +0000
Change: 2018-08-15 09:06:07.875238074 +0000
Birth: -
ERROR: Unable to parse configuration: EOF
Heketi v7.0.0-128-g801480d

This indicates the heketi.json file is empty or not correctly formatted. Can you explain which container image you are using and how you pass the heketi.json to the container?

I use the master branch deploy directory deploygk-deploy -g.
I copyed the json file out from docker to run, it's normal.


AMQP message sending

In order to control the simulator (dpsim), we need to send AMQP messages in the JSON format defined here:
https://villas.fein-aachen.org/doc/controller-protocol.html
To begin we need to be able to start and stop a simulation.
Perhaps this will be later expanded to communicate with dpsim during the run.

For now, we are mainly focusing on the parameters map to store simulation specific attributes.


Serving a .tar.gz model file

I have a 13GB llama 2 fine tuned model called "llama2-finetuned.tar.zst".
How would I go about deploying this using vllm? I have only tried the hugging face models.

.tar.gz files have been zipped. likely you will need to unzip that file to obtain the weights

vLLM supports *.safetensors and *.bin files for the model weights, just like HF transformers. Please unzip the file.


[Updates section: What’s new and Release highlights]:

@claycrenshaw @shixiedesign @jeanservaas
What’s new:
Captions: Should not be italic and too close to image
Remove the rule between the dates

also in Safari the en dash bullets don’t show up so looks like below.


Procedural Clouds in CesiumJS

This issue tracks the progress of adding procedurally-generated clouds to CesiumJS.
Inspiration
GeoFS

Dzung, who initially worked on this feature for Cesium, modeled her clouds system after GeoFS. Cumulus clouds were represented with billboard png images, and GLTFs were used for the flat clouds. Supposedly, they are also generated on real weather data.
Google Earth

Google Earth features an imagery layer of cloud on its globe that might be real data. It fades as you zoom in and out.
Horizon Zero Dawn

Horizon Zero Dawn (HZD) implements procedural volumetric clouds according to this presentation here. Their process of modeling the clouds can be summarized as follows.

Three textures are used along with a variety of signals / inputs to define the shape of the clouds.

[Texture 1]: 3D texture with four channels, the first channel containing Perlin-Worley noise and the others containing layered Worley noise
[Texture 2]: 3D texture with three channels, all different resolutions of Worley noise
[Texture 3]: 2D texture with three channels, all curl noise

The first texture is used as a base shape, and at the edges of the base cloud, the second texture of noise is subtracted, such that it "erodes" the edges of the cloud. The curl noise is used to distort [Texture 2] to fake distortions from atmospheric turbulence. This is further modified by height gradients depending on cloud type and a "coverage signal" (not well-explained in the presentation), as well as a multiplier that reduces density towards the bottom of the clouds (apparently clouds grow denser with altitude).
This algorithm is for their fluffy cumulus clouds. Flat cirrus clouds are apparently rendered as textures above a certain height.
Unreal Engine Plugin

The trueSKY plugin generates good-looking clouds. I have not done a lot of research into this, though.
Implementation
I will be focusing on implementing billboard clouds in Cesium, since it presents a more reasonable scope than volumetric clouds. This will involve the following details:

New primitive type similar to BillboardCollection and Billboard: CloudCollection + Cloud

With this API, user can add or remove clouds themselves, e.g. for taking good screenshots
Might want an overarching Clouds.js that can host multiple Cloud Collections
A cloud should keep track of what type of cloud it is (cumulus + round vs. stratus / cirrus + flat), since they will be rendered differently

Procedurally generated image in the shader based on noise function and parameters passed in as uniforms Cl

should generate color but not save to a texture, don’t want to take up texture space
geometry is instanced with scale + position attributes, but if browser doesn’t support instancing, it should still batch into a single draw call

Option to autogenerate clouds

Procedurally place clouds depending a wrapping noise function
Should add / remove clouds when camera moves
Radius of generation vs. vision

the generation radius is bigger than the vision one
when a cloud leaves the vision radius, it is not necessarily destroyed, until it leaves the generation radius
clouds should be generated before they enter the player's vision

Animation over time (extra)

Timeline
I have about four or five weeks to complete this, since I leave on August 27th.

[x]  Create Cloud, CloudCollection, and Clouds classes, and their corresponding specs.

[x] Cloud and CloudCollection done as of 7/29. #9701 The structure of Clouds, if we even include it, will be discussed later.

[x] Create the shaders and rendering commands to visualize the clouds. #9701
[x] Develop a convincing procedural cloud texture
[ ] Implement autogeneration to generate these clouds (big task, will break into subtasks later)

cc @lilleyse

Procedurally generated image in the shader based on noise function and parameters passed in as uniforms Cl

Depending on performance it might be better to create a small set of procedurally generated textures on initialization and then reuse them by multiple cloud instances. Maybe there's a way to modulate the texture in a cheap way so that individual cloud instances still look unique.

@j9liu Is this issue at a point where it can be closed? Is there any remaining work in this issue that we plan on still tackling?

Yes, I can close this issue. Everything else related to future work on clouds is listed under #9764 .


Add soundclound and mixcloud icon links

Description: The menu icons could do with soundcloud and mixcloud. While at it, we could change the all of the icons so they all follow a particular style.
ToDo:

[ ] Add soundcloud and mixcloud icons
[ ] Update all icons so they are of the same design

@Lewisthiverval this could be a quick fix and win for us

@Lewisthiverval this could be a quick fix and win for us

Yep will get that done asap

@t-scale do you think you could link us up with the assets you wanted for links e.g. mixcloud, soundcloud etc


Spelling and links

Updated GitHub links and fixed some spelling errors
Signed-off-by: Thomas Sjögren<EMAIL_ADDRESS>

oh. looks like we could add codespell in pre-commit for this kind of things I guess (probably deserves its own PR).

yeah, that's how i caught them


Proper way to store API key

We tried to store our API_KEY in environment variables, but we encountered the same issue as in issue #2.
The challenge we faced is that JavaScript and Node.js operate in different environments. As a result, the process.env.OUR_API_KEY variable is not accessible in a browser, which is only capable of handling JavaScript.
We explored two options to store the API_KEY:

Store it in a JSON file:
We found that this approach worked, but only when the JSON file was loaded in a Node.js server. When the file was loaded in a
browser, it could not access the file.

Store it in an environment variable:
We attempted this approach, but faced the same issue as before.

Our temporary solution was to set the API_KEY directly in the code as a string. While this solution is not ideal for security reasons, it allows us to continue testing and developing the application until we can find a more secure solution.

Fixed : use dotenv to store api_key in the .env file or environement variables


moveit_core test failures

build/moveit_core/Testing/20190523-0142/Test.xml: 17 tests, 0 errors, 11 failures, 0 skipped
build/moveit_core/test_results/moveit_core/test_aabb.gtest.xml: 1 test, 0 errors, 1 failure, 0 skipped
build/moveit_core/test_results/moveit_core/test_collision_distance_field.gtest.xml: 1 test, 0 errors, 1 failure, 0 skipped
build/moveit_core/test_results/moveit_core/test_constraint_samplers.gtest.xml: 1 test, 0 errors, 1 failure, 0 skipped
build/moveit_core/test_results/moveit_core/test_constraints.gtest.xml: 1 test, 0 errors, 1 failure, 0 skipped
build/moveit_core/test_results/moveit_core/test_distance_field.gtest.xml: 1 test, 0 errors, 1 failure, 0 skipped
build/moveit_core/test_results/moveit_core/test_fcl_collision_detection.gtest.xml: 1 test, 0 errors, 1 failure, 0 skipped
build/moveit_core/test_results/moveit_core/test_moveit_robot_model.gtest.xml: 1 test, 0 errors, 1 failure, 0 skipped
build/moveit_core/test_results/moveit_core/test_planning_scene.gtest.xml: 6 tests, 0 errors, 6 failures, 0 skipped
build/moveit_core/test_results/moveit_core/test_robot_state_benchmark.gtest.xml: 1 test, 0 errors, 1 failure, 0 skipped
build/moveit_core/test_results/moveit_core/test_robot_state_complex.gtest.xml: 1 test, 0 errors, 1 failure, 0 skipped
build/moveit_core/test_results/moveit_core/test_time_parameterization.gtest.xml: 1 test, 0 errors, 1 failure, 0 skipped

After re-enable CI for dashing, I'm getting the following test errors.
@anasarrak, could you please have a look?

I've managed to solve some of the test errors, the problem was the moveit_resources cmakelist, the path where it was including them was incorrect. I've made a PR that solves the path, and now most of them works.
With the remaining tests, some of them are fixed manually and the others when running colcon test_result we can see them as errors, but launching them manually they seem to pass.
erle@kaladin:~/myfiles/github/moveitmaster$ colcon test-result
build/moveit_core/Testing/20190524-0906/Test.xml: 17 tests, 0 errors, 8 failures, 0 skipped
build/moveit_core/test_results/moveit_core/test_aabb.gtest.xml: 1 test, 0 errors, 1 failure, 0 skipped
build/moveit_core/test_results/moveit_core/test_collision_distance_field.gtest.xml: 1 test, 0 errors, 1 failure, 0 skipped
build/moveit_core/test_results/moveit_core/test_constraint_samplers.gtest.xml: 1 test, 0 errors, 1 failure, 0 skipped
build/moveit_core/test_results/moveit_core/test_constraints.gtest.xml: 1 test, 0 errors, 1 failure, 0 skipped
build/moveit_core/test_results/moveit_core/test_distance_field.gtest.xml: 1 test, 0 errors, 1 failure, 0 skipped
build/moveit_core/test_results/moveit_core/test_fcl_collision_detection.gtest.xml: 1 test, 0 errors, 1 failure, 0 skipped
build/moveit_core/test_results/moveit_core/test_planning_scene.gtest.xml: 1 test, 0 errors, 1 failure, 0 skipped
build/moveit_core/test_results/moveit_core/test_robot_state_benchmark.gtest.xml: 1 test, 0 errors, 1 failure, 0 skipped

Summary: 52 tests, 0 errors, 16 failures, 0 skipped

Launching test_collision_distance_field manually: the above output says that it has an error, the below one every single test passes, it takes a looot of time to complete, and this might cause the error. I'm trying to debug it.
erle@kaladin:~/myfiles/github/moveitmaster$ ./build/moveit_core/collision_distance_field/test_collision_distance_field
[==========] Running 6 tests from 1 test case.
[----------] Global test environment set-up.
[----------] 6 tests from DistanceFieldCollisionDetectionTester
[ RUN      ] DistanceFieldCollisionDetectionTester.DefaultNotInCollision
[INFO] [robot_model]: Loading robot model 'pr2'...
[       OK ] DistanceFieldCollisionDetectionTester.DefaultNotInCollision (19758 ms)
[ RUN      ] DistanceFieldCollisionDetectionTester.ChangeTorsoPosition
[INFO] [robot_model]: Loading robot model 'pr2'...
[WARN] [moveit.collision_distance_field]: State for Variable torso_lift_joint has changed by  radians
[       OK ] DistanceFieldCollisionDetectionTester.ChangeTorsoPosition (27424 ms)
[ RUN      ] DistanceFieldCollisionDetectionTester.LinksInCollision
[INFO] [robot_model]: Loading robot model 'pr2'...
[       OK ] DistanceFieldCollisionDetectionTester.LinksInCollision (24800 ms)
[ RUN      ] DistanceFieldCollisionDetectionTester.ContactReporting
[INFO] [robot_model]: Loading robot model 'pr2'...
[       OK ] DistanceFieldCollisionDetectionTester.ContactReporting (22794 ms)
[ RUN      ] DistanceFieldCollisionDetectionTester.ContactPositions
[INFO] [robot_model]: Loading robot model 'pr2'...
[       OK ] DistanceFieldCollisionDetectionTester.ContactPositions (19908 ms)
[ RUN      ] DistanceFieldCollisionDetectionTester.AttachedBodyTester
[INFO] [robot_model]: Loading robot model 'pr2'...
[       OK ] DistanceFieldCollisionDetectionTester.AttachedBodyTester (39240 ms)
[----------] 6 tests from DistanceFieldCollisionDetectionTester (153924 ms total)

[----------] Global test environment tear-down
[==========] 6 tests from 1 test case ran. (153924 ms total)
[  PASSED  ] 6 tests.


Use local solc

I have installed solc 0.4.10. However, it seems that the extension ships with some default version that currently is at 0.4.9 (pragma solidity ^0.4.10; gives an error). I can change this version to a remote compiler version via the settings. This change requires me to be online. For train-coders like myself it would be very useful to simply use the locally installed solc in whatever version that is.

@SCBuergel  Updated now

@juanfranblanco this issue is not (just) about updating the default compiler from 0.4.9 to 0.4.10. It is about using the local solc instead of the default provided one. Is that on the roadmap? Would be fantastic!

@SCBuergel yes it might be possible "downloading" solcjs from local storage.

Note: This might possible using require-from-string and the wrapper setupMethods()

@juanfranblanco if you had any more instructions on how to "download" solcjs from local storage that would be helpful. I see that the current version is still on 0.4.10. I just tried simply installing npm install -g solc which did not do the trick, the extension seems to always use its own.

@SCBuergel check the latest, now you can use any of the sol-bin files

@SCBuergel  I will be adding a capability (working on it) to install in the project solc from npm and use that as the first option.
1st local
2nd check settings for local bin file (soljs bin)
3rd check settings for remote version ('latest')
4th finally use the version within vs code


Implement filters in the CLI

The Bindle client should have a command that gives an invoice and some filters (groups and features toggles) and gives back a list of matching parcels from that invoice.

Optionally, we could also do this in a search endpoint for thin clients

I think it should both have an option to return just the filtered list, or to fetch the parcel list generated by the filter


Governance Proposal voting

UI Version: 0.X.X
Description:

Problem
After double voting on a proposal I get an error message saying that my action is already in the cache and I'm prevented to act on this proposal and on others too.
Steps

Create a proposal
Deposit (I did it 1 + 2 + 40) 43 Steak then the Vote button is enabled
Vote for it, let's say YES
Vote again with the same value
Every other action gets blocked: Invalid Sequence. Got 9 expected 10

Possible solution
As far as I understood the root cause is the double voting with identical value, it will try to create two identical blocks, we can prevent this by storing in the state the last vote and disable just that value so you can't vote twice with the same value
Related: https://github.com/cosmos/cosmos-sdk/issues/3002

is double voting supposed to be permitted?

is double voting supposed to be permitted?

no. but you can change your vote.

is double voting supposed to be permitted?

you can vote as many times you want if the proposal is still on voting period. You just need to pay gas every time

isn't the sequence number supposed to address this?

isn't the sequence number supposed to address this?

yes you are right, maybe there is a bug in incrementing the sequence on our side.

I would still disable the option to vote for the same for a better UX.

I'm trying to reproduce it but it doesn't happen anymore

I would still disable the option to vote for the same for a better UX.

but if a user is allowed to vote more than once - shouldn't we permit this?

but if a user is allowed to vote more than once - shouldn't we permit this?

I suppose this would only confuse the user. "Have I voted already? Why can I vote 'Yes' again?". I would disable all options, that don't bring any value to the user.

Why can I vote 'Yes' again?". I would disable all options, that don't bring any value to the user.

We should display the previous vote by the user somewhere on the proposal, that's the main issue here imo.
Thus, I disagree with disabling voting for the same option, if users want to throw away their funds we shouldn't prevent them to do so

if users want to throw away their funds we shouldn't prevent them to do so

what's the reasoning here?

I guess the question is more why are you preventing them to do it ? I know it's not "bringing value" but if they choose to do so then be it

maybe add an additional confirmation with a note like
You already vote ${this.option} on this proposal. Do you still want to send an additional transaction (with gas costs) ?
But definitely not preventing them to vote twice on the same option

why are you preventing them to do it

reduced complexity is always better for UX. preventing users to make errors as well. We are also i.e. validating form inputs. just because the user is in theory able to perform some action in the backend shouldn't mean the UI allows the user to do so.

So the outcome for this if I got it correctly should be:

At loading get your last vote, if you voted in another session, reopened the app, we should behave in the same way as if you voted right now
Save in the store your action even before the reply from the APIs, so speedy users won't have surprises
once you get back the data add/update your last vote in the store

I've seen that in the /proposals response this information is not there (who voted what) we just have a summary.

do something with this information: either block that vote option and / or show the datetime when you voted there

nice to have: show the datetime of your vote

query the transaction that contain your most recent vote

is "voting again" the same as changing your vote? if i vote "yes" and "no" on the same proposal - what is the expected result?

is "voting again" the same as changing your vote? if i vote "yes" and "no" on the same proposal - what is the expected result?

that your final vote is "No"

so it's not "voting again" then - it's "changing your vote" - which should be permitted @faboweb

I am all for "changing your vote". I understood the discussion was around if we should allow "voting again" (with the same option).


Add sample csv file tooltip on Movie_Analysis page

There should be a tooltip or something similar on Movie_Analysis page to know about what will be inside csv file.

Closing it because of setup issues


refactor(server): links routes and logic

Hello @lyrgard,
I'm willing to contribute to this project by improving the existing code, using my current experience with Node.js projects.
Here, I refactored a small part of the server logic to improve readability and separation of concerns. Is this kind of work of any interest for you ?
Let me know :)

First, I'm all for this sort of cleaning/refacto and ready to integrate you PL.
However, when trying your code with a locally running node server, I got the following exception when trying to log in with google :
TypeError: oauth2Client.setCredentials is not a function
at getDriveConfigClient (/home/lyr/dev/sources/ffbeEquip/server.js:188:18)
at getFileFromGoogleDrive (/home/lyr/dev/sources/ffbeEquip/server.js:145:29)
at /home/lyr/dev/sources/ffbeEquip/server.js:84:9
at Layer.handle [as handle_request] (/home/lyr/dev/sources/ffbeEquip/node_modules/express/lib/router/layer.js:95:5)
at next (/home/lyr/dev/sources/ffbeEquip/node_modules/express/lib/router/route.js:137:13)
at Route.dispatch (/home/lyr/dev/sources/ffbeEquip/node_modules/express/lib/router/route.js:112:3)
at Layer.handle [as handle_request] (/home/lyr/dev/sources/ffbeEquip/node_modules/express/lib/router/layer.js:95:5)
at /home/lyr/dev/sources/ffbeEquip/node_modules/express/lib/router/index.js:281:22
at param (/home/lyr/dev/sources/ffbeEquip/node_modules/express/lib/router/index.js:354:14)
at param (/home/lyr/dev/sources/ffbeEquip/node_modules/express/lib/router/index.js:365:14)
at Function.process_params (/home/lyr/dev/sources/ffbeEquip/node_modules/express/lib/router/index.js:410:3)
at next (/home/lyr/dev/sources/ffbeEquip/node_modules/express/lib/router/index.js:275:10)
at jsonParser (/home/lyr/dev/sources/ffbeEquip/node_modules/body-parser/lib/types/json.js:109:7)
at Layer.handle [as handle_request] (/home/lyr/dev/sources/ffbeEquip/node_modules/express/lib/router/layer.js:95:5)
at trim_prefix (/home/lyr/dev/sources/ffbeEquip/node_modules/express/lib/router/index.js:317:13)
at /home/lyr/dev/sources/ffbeEquip/node_modules/express/lib/router/index.js:284:7
TypeError: oauth2Client.setCredentials is not a function
at getDriveConfigClient (/home/lyr/dev/sources/ffbeEquip/server.js:188:18)
at getFileFromGoogleDrive (/home/lyr/dev/sources/ffbeEquip/server.js:145:29)
at /home/lyr/dev/sources/ffbeEquip/server.js:103:9
at Layer.handle [as handle_request] (/home/lyr/dev/sources/ffbeEquip/node_modules/express/lib/router/layer.js:95:5)
at next (/home/lyr/dev/sources/ffbeEquip/node_modules/express/lib/router/route.js:137:13)
at Route.dispatch (/home/lyr/dev/sources/ffbeEquip/node_modules/express/lib/router/route.js:112:3)
at Layer.handle [as handle_request] (/home/lyr/dev/sources/ffbeEquip/node_modules/express/lib/router/layer.js:95:5)
at /home/lyr/dev/sources/ffbeEquip/node_modules/express/lib/router/index.js:281:22
at param (/home/lyr/dev/sources/ffbeEquip/node_modules/express/lib/router/index.js:354:14)
at param (/home/lyr/dev/sources/ffbeEquip/node_modules/express/lib/router/index.js:365:14)
at Function.process_params (/home/lyr/dev/sources/ffbeEquip/node_modules/express/lib/router/index.js:410:3)
at next (/home/lyr/dev/sources/ffbeEquip/node_modules/express/lib/router/index.js:275:10)
at jsonParser (/home/lyr/dev/sources/ffbeEquip/node_modules/body-parser/lib/types/json.js:109:7)
at Layer.handle [as handle_request] (/home/lyr/dev/sources/ffbeEquip/node_modules/express/lib/router/layer.js:95:5)
at trim_prefix (/home/lyr/dev/sources/ffbeEquip/node_modules/express/lib/router/index.js:317:13)
at /home/lyr/dev/sources/ffbeEquip/node_modules/express/lib/router/index.js:284:7

Hi @lyrgard, whoops ! seems like a bug inside googleapis package: https://github.com/google/google-api-nodejs-client/issues/869
I'll downgrade one version for the time being, sorry 👍

I've added some tests

Merged, tested it and deployed it. It is live now ! Thanks a LOT for your cleaning work.


Same problem here.
I'm trying to use Sortable with some livewire components and getting this error.


Using sensu-client to check the machine where container is running

Is the docker sensu-client designed to perform checks in the machine where the container is running?
For example process checks are returning just results relative to processes running within the container.
How can we manage that?

Honestly, what would be the goal to monitor processes inside a container where only the monitoring tool is running?
Of course, it is meant to monitor its host, or other external items (host, processes/container on the host, remote checks, ...).

@gianfrancocianchetti it's setup to allow you to mount the proc of the host so you can monitor the host OS.  Please see Define volumes to access host
https://github.com/sstarcher/docker-sensu#configuration


Merge branch indev into branch master

Release version 0.5.0

Look like CSSLint is not working like what i wanted. Disabling it now

Still hunting for bugs.....

ready to merge!


Feature/communication interaction controller

Initial PR of merging callAutomation (callingServer V3) into the main branch from private repo

API change check
API changes are not detected in this pull request.


Discuss: Input validation of XML file

While this is not part of the offer, we would like to also run some basic input validation on XML level.
Are you aware of a good tool to run?
Or should we go into validating the XML schema of CVRF 1.2 (e.g. using lxml)?
In the end, the XML schema validator will help us to reject invalid files as a pre-step.

I'm currently not aware of a good tool to run. However, I think validating the input against the XML Schemas of CSAF CVRF 1.2 might be a good start.

Maybe @sthagen has additional insights.

Maybe existing projects, like sthagen/csaf-lint could help in the implementation?
Flagging @sthagen for attention.

I will open a new ticket in csaf-lint project with more details.

Waiting for @zpevma to come back from vacation - Will be opened after next internal meeting.

Currently input validation is done by xsd schema.

sthagen/csaf-lint is discontinued. The only option left is validating the XSD schema (which we are doing already).


Present stdout in CLI

Not sure if this is something that make sense.
Currently the CLI presents the command description (developer desc. of what happens) as a short notice to the user and stderr if something goes wrong.

Done. Pass -v or --verbose to the CLI


Increast to Py37 Only

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

Numpy values not available for Python 3.6 & Python 3.7 on conda.


Improve UI when an entity is missing from the selected timeline

Rerun shows simply "no data" for all entities that exist on a timeline that isn't selected right now. In the selection ui there is no indication that there is in fact data, just not on the active timeline
Irritatingly, the blueprint view shows all entities just as normal even if there's no data for them available right now.
There's a bunch of improvements that could be made for this:

blueprint view could already indicate via style and tooltip that an entity is "inactive" due to the "lack of data"
upon selection it shouldn't just say "no data" but indicate if there's maybe data on another timeline or time, ideally with links

challenge here: Each timeline may be set to something else at any point

Overall, it's right now easy to shoot oneself in the foot by creating a new timeline and then accidentally no longer logging to it. (but even when done intentionally, the additional context may very helpful!)

Currently, data is identified by a rather nondescript bullet · as icon. Maybe we could have a more informative icon there, reflecting availability of data (of course in a way that's consistent between the Blueprint and Streams trees).

In any case, the tooltip could display a conspicuous note indicating why no data might be displayed.

After discussing this issue with @martenbjork, we figured that the best course of action was to not do anything further than #3779 because:

the source/occurrence rate of user confusion over this is not yet well identified
more generally, the use-cases involving multiple timeline with mutually exclusive data are not well mapped out
the interaction with related problem are not yet identified (e.g. should we also highlight entities/components that have data logged on the current timeline, but only after the current cursor position?)
it generally feels like too much design for too little of a problem, given #3779 addressed 90% of the original issue

Quick illustration of the 3rd bullet point for records, made using #3792

Here the hello entity and its components are italic because they are only logged to another timeline, and everything else is normal. The hour_hand stuff is not visible in the space view though, because it's been logged only after the current cursor position. Should it be highlighted as well in the Blueprints tree? Certainly not in the Streams tree. Though question better avoided for now.


Adds StatsReceiver to ThriftClientConfiguration

Adds

Allows a consumer of async-utils to supply a StatsReceiver implementation to the underlying Finagle Thrift client in ThriftClient.

Context
Local experiments to ingest Finagle Thrift client metrics suggest that providing a StatsReceiver implementation--like is done here--can be used to export Finagle Thrift client metrics to a metrics service like Prometheus.

This looks like a good idea, but it's failing the MiMa binary compatibility checks. Could you take a look and try to resolve those? Let me know if you need any help.

I tried to look at this locally and after merging main into this branch, I was not able to reproduce the MiMa failure, so maybe we can just do that and it will be ok?


/mc command group

We now have /mcwhitelist and /mcadmin run and /mcunwhitelist. These should all be placed under the umbrella of one (1) command group, instead of being different commands.
Additionally, more functionality:

allowing non-admin users to unwhitelist themselves (or maybe this is a feature? only letting admins remove your entries from the whitelist means no account-switching shenanigans)
allowing you to see which user you currently have whitelisted
allowing admins to prevent someone from whitelisting an account
allowing admins to link admin-whitelist entries with accounts so people who've been admin-whitelisted don't get a 2nd go at the whitelist

My very rare "appearing for 2 cents moment": as you cant restrict commands in a command group, i think splitting into minecraft and mcadmin might be a better solution


No unread message count barge

My Setup

Operating System: OSX 10.14.6
App Version: 2.15.5
Installation type: dmg

[x] I have tested with the latest version
[x] I can simulate the issue easily

Description
Sometimes (actually pretty often) there is no unread count barge on the app icon.
I do see a dock icon jumping when I have a new direct message, but there is no unread count barge, so if you missed that jump - you will never know, that there is something unread.
Current Behavior
No unread barge on the app icon
Expected Behavior
App icon should display the quantity of unread private messages.

i have the same problem too

Please test if the latest release did solve this. If not please reopen the issue or create a new one and tell us. I will be closing this one for now.
Thank you!


Starter Kit

Developers are wanting to start from a blank project. We need to consider the option to provide developers with a true starter it that does not include a CSS style sheet, color palette, and other elements needed to set the structure of a site frontend.
From some brainstorming, I'm thinking:

Starter kits have representative UX to highlight the integration with a storefront

Now that @cartogram has the new examples directory, we could add a simple blank-example.

Actively developing this in #620

Closed with #1119


Atom Info.plist

I was trying to add a new file type to Info.plist in OS X but no success about that.
The extension which i added don't is accepted by the editor ( the blank icon remains )
Others file in the editor like .md don't work too, someone know why?
I already rebuild the LaunchService database, then what could be?

What is the issue you are experiencing?

I'm guessing this is spam, please let me know if it isn't

@kevinsawicki Sorry, i typed enter by mistake.

@kevinsawicki Finder preferences have a mark up option which is "Show preview icon" this override the atom icons with a OS X preview icon or a blank icon if the file type is unknown, this cause files like markdown and others to have a blank icon.


0.19 test-db-import NPE when running tests after the first time in quarkus dev mode

Quarkus version:  2.16.9.Final
Steps to reproduce:

Clone this small example project or setup a new one only with hibernate, pg-jdbc, resteasy and db-import extensions
https://github.com/chrispysz/quarkus2-playground

Run mvn quarkus:dev

Press "r" (test should pass)

Press "r" again (test fails)

2023-10-27 12:34:02,055 ERROR [io.qua.test] (Test runner thread) Test GreetingResourceTest#testHelloEndpoint() failed                                                                                : java.lang.RuntimeException: java.lang.RuntimeException: io.quarkus.builder.BuildException: Build failure: Build failed due to errors
[error]: Build step org.tkit.quarkus.test.dbimport.DevServicesDbImportProcessor#startDbImportDevService threw an exception: java.lang.NullPointerException: Cannot invoke "io.quarkus.datasource.deployment.spi.DevServicesDatasourceResultBuildItem.getDefaultDatasource()" because "devServiceDatasource" is null
at org.tkit.quarkus.test.dbimport.DevServicesDbImportProcessor.startDbImportDevService(DevServicesDbImportProcessor.java:51)

Hi @chrispysz, thank you for reporting this issue.
The current implementation does not support reusable data source dev-services.
https://quarkus.io/guides/databases-dev-services#reuse
You can disable it.
quarkus.datasource.devservices.reuse=false

The disadvantage is that Quarkus starts the new database container every time the tests are repeated.

Fix in release version 2.13.0.


chore(tooling): update build pipeline to npm 5

maybe. it might actually be enough to just let jenkins run npm install and commit package-lock.json at that point since we're not directly merging PRs.

but, that's also part of why i haven't package-lock yet :)

blocked by https://github.com/npm/npm/issues/16807

closing for now.


Deploy Checklist: New Expensify 2023-03-06

Release Version: 1.2.79-0
Compare Changes: https://github.com/Expensify/App/compare/production...staging
This release contains changes from the following pull requests:

[x] https://github.com/Expensify/App/pull/9306
[ ] https://github.com/Expensify/App/pull/15022
[x] https://github.com/Expensify/App/pull/15207
[x] https://github.com/Expensify/App/pull/15280
[x] https://github.com/Expensify/App/pull/15391
[x] https://github.com/Expensify/App/pull/15476
[ ] https://github.com/Expensify/App/pull/15517
[x] https://github.com/Expensify/App/pull/15555
[x] https://github.com/Expensify/App/pull/15610
[x] https://github.com/Expensify/App/pull/15614
[x] https://github.com/Expensify/App/pull/15626
[x] https://github.com/Expensify/App/pull/15643
[x] https://github.com/Expensify/App/pull/15678

Deploy Blockers:

[x] https://github.com/Expensify/App/issues/15697
[ ] https://github.com/Expensify/App/issues/15703

Deployer verifications:

[ ] I checked the App Timing Dashboard and verified this release does not cause a noticeable performance regression.
[ ] I checked Firebase Crashlytics and verified that this release does not introduce any new crashes.  Checking off
PR https://github.com/Expensify/App/pull/15517#issuecomment-1456547141. Are we ok to check it off?

@mvtglobally

#15676 should be fixed now. Can we retest please?
#15517 should be okay to check off

Checking off remaining items as expected behavior

:shipit:

:shipit:

:shipit:

:shipit:

:shipit:


Can we return value inside provider.request ?

Hi guys i am using newest Moya version and swift 3.0
I have question, can we return some values in a function which will call a provider request ?
I need it bcs i will use that values in objective-c bridging, since i will use it for react-native .
The below code i use always return "" instead of dict that will be filled inside provider.request
public func setupRx() -> Any {

        provider = RxMoyaProvider<GitHub>()
        var dict : Any? = ""

        provider.request(.bible).subscribe { event in
            switch event {
            case let .next(response):
                //image = UIImage(data: response.data)
                do{
                    dict = try response.mapJSON()
                    try print("Dict is : ", dict)
                }catch {
                    print("Something wrong");
                }
            case let .error(error):
                print("Error : ",error)
            default:
                break
            }
        }
        return dict
}

//BRIDGING CODE in Obj-C for react-native

RCT_EXPORT_METHOD(connectToHub

                  :(RCTPromiseResolveBlock)resolve
                  :(RCTPromiseRejectBlock)reject)
{
    RCTMain * helloWorld = [RCTMain newInstance];
    //call setupRx
    NSString *test = [helloWorld setupRx];
    //always nil never get the value from API that has been called inside setupRx
    NSLog(@"Test Dictionary return : %@", [helloWorld setupRx]);
    [self.bridge.eventDispatcher sendAppEventWithName:@"onHubConnected" body:nil];
}

Thank you..

One thing is crystal clear: you cannot synchronously return something that will arrive in the future, asynchronously. (Not to mention that using side-effects to sneak out values from RX is malpractice by itself.)
The setupRx function should be rewritten to take callbacks or return an Observable, and your bridging code should make use of the resolve/reject blocks you get from the framework. This seems to be related.

@vzsg Thank you so much sir.. Your solution using completion block is worked. Now i could get result in my obj-c bridging..


update documentation to working docker image

Description

I updated the example of the config file in the documentation to a working docker image.
Motivation and Context

The other docker image isn't available (maybe it is private and only limited set of people can access it)
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[x] I have read the contributing document.
[ ] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Thanks! 👍


Adding 979 blank emails

Receiving some blank Summary of Adding 979 fields to MARC emails. Per Jeremy Maybe when no 979s are added then don’t trigger the polling dag?

It looks like for the task retrieve_variables, if it is a manual run, then we have dag_runs returned and proceed with sending an email. But for the scheduled runs of poll_for_digital_bookplate_979_emails it always returns empty (the list of dag run IDs) yet we send an email. I wonder why there is even a scehdule for this dag since it should always be triggered from the other dag.


Address #74 - add new-exe-project subcommand

This PR is an attempt to address #74 by adding a new-exe-project subcommand.
It includes changes to jpm/scaffold.janet and jpm/commands.janet.
jpm/scaffold.janet:

Addition of a new template named exe-project-template
Change the logic a bit in scaffold-project to accomodate the new template

jpm/commands.janet:

Modify the usage string in help to mention the new subcommand
Addition of a new-exe-project function that invokes scaffold/scaffold-project appropriately
Add key-value pair for new subcommand in subcommands definition

LGTM.


Detect message finished processing

I am trying to deploy a node bot to aws lambda using serverless framework, but I cant figure out how to detect Bot framework finished his job(Saved user data and sent all pending messages) to stop aws lambda.
I thought about detecting the response send in listen method, but It wont work because the bot framework continues processing the message.
How could I detect the event has been processed?

Is this the Node SDK?

Yes,It is on the node sdk, I want to detect when processing a message ends

@Stevenic can this be done with ISessionMiddleware?

I helped someone do this a few months back but I think it was on gitter as I can't find an issue for it here.
@charlesmst basically what you need to do is manually call ChatConnector.listen() with a mocked up request & response object. So something like:
var statusCode;
connector.listen({
   body: <body received>,
   headers: <headers received>
}, {
   status: function (code) {
      statusCode = code;
   },
   end: function () {
      // return status code here.
   }
});

Basically you just need to wait until we call response.end() and then you can send back the statusCode we set.

I'll test it as soon as I can, but I dont know if this is gonna work, bucause end method is called before messages have been sent.
I was trying to do something like this https://gist.github.com/charlesmst/6ddf02fc3506c590004c5bf9d989088e
where I override send method in ChatConnector and add a onFinish callback, and add a onFinish callback on storage saveData, and when this two onFinish methods have been called, I invoke callback, is there a problem on this?

But we send messages using a separate HTTP POST back to the connector service so it's ok if end() has already been called. That's the expected behavior. We receive the incoming message and ACK immediately with a 202.  That's because it can take several seconds for the bot to respond and the bot is free to send several message in response to a single incoming message.

I should add that the one issue you may have to concern yourself with is how long will the Lambda service let the bots code run after it ACKs the incoming message.  On Azure Functions it's 5 minutes (for the free tier) before the bots process becomes a candidate for being recycled.  That means that your bot generally has 5 minutes to respond to the user or it could be shutdown which is a fairly long time.  I'd assume that AWS Lambda has a similar recycle timeout.

Alright, thanks for the help

@charlesmst I've created this module to simplify the deployment of serverless bots on Amazon Lambda https://github.com/palmerabollo/botbuilder-aws-lambda. The same approach should work on Azure Functions as well. I'll write a post someday.
Thanks @Stevenic for your tips. I'm not sure about whether including a generic ServerlessChatConnector that extends/decorates ChatConnector would be possible / a good idea.

I have a variation of this problem. I am connecting my bot to Twillio. Each time I pick up voice from my user I call my Bot via the DirectLine API. I have to keep the request open and collect all the replies before responding the the user.
Unfortunately my bot can reply with anywhere between 1 and 4 messages. So I need to be able to detect when the bot has finished that batch of replies.
Will @Stevenic suggestion above with the end event be something I could use?
Would I pass that back using the backchannel to my proxy service thats connected to Twillio?

@bradleyscott You are commenting on a closed issue.
If you have a question or problem, please open a new issue.

        var heroCard = new HeroCard
        {

            Text = "Suggestions for Next...",
            Buttons = new List<CardAction>()
        };

        for (int i = 0; i < Answers.Count(); i++)
        {
            heroCard.Buttons.Add(new CardAction(ActionTypes.ImBack, Answers[i] ?? "No Choice Found", value: Answers[i] ?? "No Choice Found"));
        }

        heroCard.Buttons.Add(new CardAction(ActionTypes.ImBack, NoReplyMessage ?? "", value: NoReplyMessage ?? NoReplyMessage));

        var reply = activity.CreateReply();
        reply.Attachments.Add(heroCard.ToAttachment());

        _activity = reply;

.........................................................................
how can i stop processing NoReplyMessage by bot? bot takes the noreply message as a input and processing it. what's the best solution for this?

@nmssalman Please ask your question on Stack Overflow using the Bot Framework tag and someone will assist you there.  The Bot Framework Team prefers that HowTo questions be on stack overflow so the entire community can benefit from the answer.


Init project failure

Started like this:
➜  rootDir  npm install -g create-graphql-server
/Users/me/.nvm/versions/node/v6.9.1/bin/create-graphql-server -> /Users/me/.nvm/versions/node/v6.9.1/lib/node_modules/create-graphql-server/dist/bin/create-graphql-server.js
/Users/me/.nvm/versions/node/v6.9.1/lib
└──<EMAIL_ADDRESS>
Error:
➜  rootDir create-graphql-server init generator
env: babel-node: No such file or directory

i have the same problem...

Have you tried installing babel-cli globally?
npm install -g babel-cli

npm install -g babel-cli fixed this for me.
thanks @xavcz

@xavcz That resolves the issue...
I was trying sth similar : npm install babel-cli - forgot to add -g

This sounds like a bug though, I don't think you should have to do that.

Fixed in 0.5.3


Add support for MathJax equation numbering

Using the flag 'number_equations:true' you can add equation numbering to MathJax. The numbering happens when you write equations using \begin{equation}...\end{equation} as described here:
https://docs.mathjax.org/en/latest/input/tex/eqnumbers.html
An example was included in:
_posts/2019-08-08-text-and-typography.md
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Improvement (refactoring and improving code)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update

Description
Option 1 (implemented)
I added a new flag:
'number_equations:true' in order to support equation numbering.
This flag changes the configuration for MathJax such that when true, MathJax supports equation numbering.
The change happens in js-selector.html and looks like:
  <!-- MathJax -->
  <script>
    /* see: <https://docs.mathjax.org/en/latest/options/input/tex.html#tex-options> */
    MathJax = {
      tex: {
        /* start/end delimiter pairs for in-line math */
        inlineMath: [
          ['$', '$'],
          ['\\(', '\\)']
        ],
        /* start/end delimiter pairs for display math */
        displayMath: [
          ['$$', '$$'],
          ['\\[', '\\]']
        ],
        {% if page.number_equations %}
          /* equation numbering */
          tags: 'ams'
        {% else %}
          /* by default don't number equations */
          tags: 'none'
        {% endif %}
      }
    };
  </script>

The tags: 'ams' causes MathJax to generate equation numbering inside \begin{equation} and \end{equation} blocks.
Option 2 (not implemented/simpler)
Potentially a simpler idea would be to have the equation numbering always on. This way, if someone wants to use it they can, but most people probably would not notice. I could prepare that patch if this is a direction you would be willing to pursue.
If the equation numbering would always be on, then:
$$ equation $$

Would work like previously.
However,
$$
\begin{equation}
equation
\end{equation}
$$

Would now require a \notag or \nonumber to skip the (1) that would appear on the right.
Additional context
This feature would be an answer to a previous request in issue https://github.com/cotes2020/jekyll-theme-chirpy/issues/147
You can see a live demo of this working on https://qbrak.github.io/posts/how-to-least-squares
Here is the documentation from MathJax on how this works: https://docs.mathjax.org/en/latest/input/tex/eqnumbers.html
EDIT: I added more structure and clarity to the text

@cotes2020 Thanks for the feedback.
I have been thinking about the differences between Options 1 and 2 (from the description). What I have implemented is Option 1 which is non-breaking, but it does introduce more complexity to the codebase (when you want equation numbering you need to set a new flag).
I was wondering if it would not be cleaner to just always enable equation numbering. So then we would have:
  <!-- MathJax -->
  <script>
    /* see: <https://docs.mathjax.org/en/latest/options/input/tex.html#tex-options> */
    MathJax = {
      tex: {
        /* start/end delimiter pairs for in-line math */
        inlineMath: [
          ['$', '$'],
          ['\\(', '\\)']
        ],
        /* start/end delimiter pairs for display math */
        displayMath: [
          ['$$', '$$'],
          ['\\[', '\\]']
        ],
        /* equation numbering */
        tags: 'ams'
      }
    };
  </script>

I have not found any issues online with this. The only case something would break was if someone used the following syntax:
$$
\begin{equation}
equation
\end{equation}
$$

instead of the simpler
$$
equation
$$

and the breaking behavior would be that they get an equation number on the right-hand side which they did not have previously.
Please let me know what you think. If you would still like to go with the 100% non-breaking option 1 I will implement your requested changes and update the PR.


Drop support for EOL Python 2.6 and Python 3.3

Python 2.6 reached its EOL in October, 2013. Python 3.3 reached its EOL in September, 2017. I guess that usage of botocore on this platform is really low (see PyPI stats). Is there a reason why botocore has to support this versions?

@and-semakin - Thank you for your post. We are dropping support for Python 2.6 and Python 3.3. This blog post contains all the details :
https://aws.amazon.com/blogs/developer/deprecation-of-python-2-6-and-python-3-3-in-botocore-boto3-and-the-aws-cli/
Hope it helps.

Yep, thank you! I think this issue may be closed :)


Users logged out of Identityserver/AspnetIdentity running on IIS

If you use Identityserver 4 in combination with AspnetIdentity Core 2 or 2.1, and roll this out to production using IIS 7.5 or later, you might encounter spurious logouts of users after 20 minutes or longer, even thought they have checked "Remember me".
Everything seems to be running perfectly in a development environment with IIS Express.
The reason for this is that if IIS is recyling your application (default setting 29 hours), or if your application is inactive for longer than 20 minutes (e.g. over night), the Aspnet Core Data Protection Stack will use a new set of Cryptographic keys, which in turn will invalidate all issued Identity cookies, forcing your users to login again.
Since this a very common scenario, that is also hard to debug, I felt the need to file this report.
Please see the instructions for configuring "Data Protection" when hosting under IIS at https://docs.microsoft.com/en-au/aspnet/core/publishing/iis
Similar case with only Aspnet Identity
https://github.com/aspnet/Identity/issues/1338
Hopefully this might be of use to anybody encountering this problem.
Ronald Wijnsema

The solution for me was setting "Load User Profile" in the Advanced Settings of your application pool to "True".
While you're at it, also change "Idle Time-out" to 0, the default of 20 minutes would only make sense if you're hosting thousands of sites.


"Could not be spawned" after installing package

Hi, I installed fuse through the Atom app. After the install (or anytime I startup Atom) I get the following error:

I then looked at Console and saw the following error:

Uncaught Error: spawn fuse ENOENT
at exports._errnoException (util.js:1022:11)
at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
at onErrorNT (internal/child_process.js:359:16)
at _combinedTickCallback (internal/process/next_tick.js:74:11)
at process._tickCallback (internal/process/next_tick.js:98:9)

OS: Fedora 26 (Linux 4.13.5-200.fc26.x86_64)
Atom 1.19.2 x64
Plugin: fuse 0.4.0

Hi, Fuse does not support Linux, and the Atom plugin needs to connect to Fuse for things like code completion, launching preview etc. Maybe Fuse isn't what you're looking for here?


need to know how to change the read write access for matter attributes

Hi , i need to know why the attribute values are not updating and if that attribute is not writable one please guide us for the solution please.

some attributes has write access but some doesn't have , if need to work with that particular cluster's attribute how to enable the write access to it
does zap tool or .zap file has the control for attribute read and write permission ?
is it possible to tap the default values of the particular attribute in endpoint_config.h where it contains Default value as macro

i attached the relevant issue ticket in matter sdk for this issue.
https://github.com/project-chip/connectedhomeip/issues/28330
thanks and regards
Aravind

I solved this issue by editing the read access in the .matter file in the common repo of all-clusters-app.


Log where an editor action was triggered from

For evaluating #15156
@bpasero I would like to add a 'from' to the editor actions telemetry, the same way we have that for workbench actions. Could you take a look? I might be missing things since the data flows past a lot of code.

@chrmarti I suggest @alexandrudima to review this. My initial feeling is that you cannot change command arguments (e.g. by adding one) because some commands might assume a specific set of arguments to be passed over to run properly.

@alexandrudima The only way I can see this being implemented properly is with an additional parameter to commandService.executeCommand() so we can pass contextual information like 'from'. What do you think?

@bpasero / @alexandrudima It looks like we have been using that 'args' object for passing along the 'from' argument for a while. Maybe that should be cleaned up?

Sorry for being late, I can't assess the risks of this change, since there might be commands in our system or coming in from an extension that might find a new argument unexpected. This change also prohibits any command from being able to use the argument "from". Perhaps there might be a better way to get this information? i.e. the keybinding service could directly log a telemetry event?
@jrieken for ideas

My suggestion would be to either have "twin" calls like commandService.excuteCommand(id, args) and telemetryService.publicLog(...) or to have another method on the ICommandService ala executeCommand<T>(id: string, telemetryData:any, ...args: any[]): TPromise<T> {


Allow method chaining in @sendgrid/mail

Issue Summary
Very minor, but it would be nice to allow method chaining in the MailService of @sendgrid/mail so that setting the API key could be handled on one line:
const mailer = require('@sendgrid/mail').setApiKey(process.env.SENDGRID_API_KEY);

// vs

const mailer = require('@sendgrid/mail');

mailer.setApiKey(process.env.SENDGRID_API_KEY);

This is all it would require as far as I can tell:
class MailService {
  // ...

  setClient(client) {
    this.client = client;

    return this; // TODO (optional, but good for consistency)
  }

  setApiKey(apiKey) {
    this.client.setApiKey(apiKey);

    return this; // TODO
  }

  setSubstitutionWrappers(left, right) {
    // ...

    return this; // TODO (optional, but good for consistency)
  }

  // ...
}

(It looks like this pattern is used here in @sendgrid/client https://github.com/sendgrid/sendgrid-nodejs/blob/master/packages/client/src/classes/client.js#L53-L67 as well.)
Steps to Reproduce

Install @sendgrid/mail
Set the API key

Technical details:

sendgrid-nodejs version ^6.2.1

Thanks for the suggestion @reichert621!
I've added this to our backlog for consideration.
Please feel free to submit a PR as well :)

Thank you @AllUsernamesHaveBeenTaken! It's all yours.


tukenya

Official website: tukenya.ac.ke

@AbeNalee First stage of verification passed, official domain is tukenya.ac.ke as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@AbeNalee Thank you for your patience while waiting for a review and processing your request. Pull request merged.


Flowise UI requires these packages so npm i flowise-ui works

Updated package.json so when npm i flowise-ui can run smoothly.

Module not found: Error: Can't resolve 'axios' in 'C:\xx\packages\ui\src\api'
ERROR in ./src/api/client.js 3:0-26
Module not found: Error: Can't resolve 'axios' in 'C:\xx\packages\ui\src\api'
ERROR in ./src/ui-component/dialog/AboutDialog.js 10:0-26
Module not found: Error: Can't resolve 'axios' in 'C:\xx\packages\ui\src\ui-component\dialog'
ERROR in ./src/ui-component/dropdown/AsyncDropdown.js 8:0-26
Module not found: Error: Can't resolve 'axios' in 'C:\xx\packages\ui\src\ui-component\dropdown'
ERROR in [eslint] Failed to load plugin 'prettier' declared in '.....eslintrc.js': Cannot find module 'eslint-plugin-prettier'
Require stack:

C:\xx\node_modules\react-scripts\config_placeholder_.js
Referenced from: C:\xx.eslintrc.js

webpack compiled with 4 errors
Face the above error when trying to npm run dev on packages/ui


Submit transactions with Tickets (RIPD-837):

There are a number of changes to Tickets with this commit:
o A Ticket can be used in place of a Sequence in a transaction.
o The external JSON representation of a Ticket has changed from
a 256-bit hash to a two-entry object.
o In TicketCreate and TicketCancel transactions it is not valid
to use a Ticket instead of a Sequence.
o Transactions with Tickets sort behind transactions without
Tickets when they are applied to the ledger.  This will tend
to keep TicketCreate and TicketCancel operations in front of
transactions that consume Tickets.
o There are C++ unit tests for Ticket functionality.
Work remaining:
o There is some question about whether Tickets need to be
threaded.  If they do, then threading will need to be added.
o Documentation needs to be amended.
o There may be additional fallout when David reviews the code.

Names of programmers and "meta discussion" should not appear in commit comments (e.g. Work Remaining section)

Reviewers: @JoelKatz for security, @nbougalis for Tickets, and @vinniefalco for general code niceness.
This pull request affects transaction processing, since it changes the order of some transaction verification checks.

Why is transaction processing affected if tickets are disabled?

Transaction processing is affected because the order of validation checks have changed in Transactor::checkSeq(): https://github.com/ripple/rippled/pull/1131/files#diff-63e38aef10c237031210901286f42aa2R162

@scottschurr Can we arrange this code so that if tickets are disabled, tx processing is not changed?

@vinniefalco I rearranged the checks so we check for tef errors, which will stop the transaction, before we check for tec errors.  I assumed that if a tef error was discovered, then that would be considered a more important failure than a tec.

@nbougalis and @vinniefalco: how do you feel about this pull request?  Should I squash it and rebase and then start pestering @JoelKatz for a code review?  Nik, you indicated you were going to spend more time looking over the code.  Have you done that?
The biggest question right now that I'm aware of is the "[FOLD] Maintain transaction backward compatibility:" commit (https://github.com/scottschurr/rippled/commit/4a898a91f881ea920b95d619a3d35d489118bcb1).  It arguably preserves transaction backward compatibility.  But it's just as easy to argue that the commit changes a more appropriate tem to a less appropriate tef.  A transaction with a zero sequence and no Ticket really is malformed and can never succeed in any ledger. If it were my call, I'd remove the [FOLD].  But I don't feel strongly about it.  You guys make the call.

At Vinnie's suggestion I've modified the "[FOLD] Maintain transaction backward compatibility:" commit (scottschurr@4a898a9) to this:https://github.com/scottschurr/rippled/commit/5e44b6cae27fc62d3b3273cc64d8edca6a65eaa3.  The new version changes the return error code based on whether Tickets are disabled (backward compatibility) or enabled (which is a transaction change, so we can use the better code).
So at this point, as far as I know, I've addressed all concerns from Nik and Vinnie.

I'm closing this pull request.  There are enough unsolved problems with the Ticket design that I'm hesitant to introduce the Ticket-related complexity into the code base without clear solutions.  I'll keep a copy of this branch in case we decide to revisit Tickets in the future.


Add smooth Hamburger menu for responsive design to the navbar #17

Hi @fykaa  I Have made the changes please take a look and merge the changes accordingly i will try to keep the design as same if possible. Thanks!

Hi @fykaa I don't know why netlify is not run here so run it separately on my fork and attached the url for your reference to test before merge. https://6352fddfa3b96c61ce255e6e--fantastic-macaron-8e34a8.netlify.app
Thanks!

Hey, not sure if this is the same for you, but the PR seems to have completely changed the Home page functions such as:

The slideshow is now not working
The cursor effect is not working
Scroll to top button is not working
Hamburger is tilted and not aligned
The contributor's section lost it's responsiveness

Hi @fykaa yes i have checked that, was busy in festival will raise a new PR for this you can disapprove this one. Thanks!


TypeError: Required argument 'vtln_warp' (pos 3) not found

bash train_transducer_bmuf_otfaug.sh
/utils/compute_global_cmvn.py", line 64, in
vtnl_warp=1.0)
TypeError: Required argument 'vtln_warp' (pos 3) not found

This is due to typos in older version pykaldi, could you try to change 'vtnl_warp' to 'vtln_warp' in these two lines,
https://github.com/tencent-ailab/pika/blob/23c4cddef4392bc035207187d3b5653e9a3f083e/utils/compute_global_cmvn.py#L64
https://github.com/tencent-ailab/pika/blob/23c4cddef4392bc035207187d3b5653e9a3f083e/loader/otf_utt_loader.py#L234

This is due to typos in older version pykaldi, could you try to change 'vtnl_warp' to 'vtln_warp' in these two lines,
https://github.com/tencent-ailab/pika/blob/23c4cddef4392bc035207187d3b5653e9a3f083e/utils/compute_global_cmvn.py#L64
https://github.com/tencent-ailab/pika/blob/23c4cddef4392bc035207187d3b5653e9a3f083e/loader/otf_utt_loader.py#L234

thank you very much

thank you very much

thank you very much@cweng6

thank you very much@cweng6


nb steps in early stop

What does this PR do?
On master, we observe random failers for PT 1.3 and 1.4
I have pulled the docker image with 1.3 and 1.4 and have not observed this failed also from checking other PR it seems to be rather random for one of these envs, so let's try to lover the limit to be sure loading fails >> test passes
PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃

@Borda do you know why this didn't fail locally and only in CI?

nice fix!

@Borda do you know why this didn't fail locally and only in CI?

it was quite random as I pulled the exact docker image which is used in CI tests and it did not happen also seeing some PR it did not fail always too


KIP-297: MINOR: Handle null config values during transform

Fix NPE when processing null config values during transform.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

retest this please

@rayokota you  might want to associate the issue KAFKA-7068 to the PR


Rewrite lead paragraph, remove duplicate text

The first paragraph was a list of guidelines, some too specific, and a bit abrupt. I've rephrased it into a lead paragraph. Farther down, the "Forms are hard to fill out on mobile..." paragraph was repeated verbatim. I've fixed that as well.
CC: @petele

:tada: This has been pushed live to https://developers.google.com/web/


Provide checkpoints of re-trained DETR3D model

All three configs have been trained and the correctness between old mmdet3d and new mmdet3d is tolerable.
Logs files and model checkpoints is available at Baidu Netdisk:
Link: https://pan.baidu.com/s/13XlTxPSeRK21ls9EH28sow
Password：1ydk

This PR will be merged after the link of models and logs have been updated.

The checkpoints and logs have been uploaded to the cloud. The link format in the readme:
https://download.openmmlab.com/mmdetection3d/v1.1.0_models/detr3d/${FILE_NAME}

@ZLTJohn Please pull the latest code and resolve the conflicts.

Already pulled the latest code and resolved the conflicts.

All three configs have been trained and the correctness between old mmdet3d and new mmdet3d is tolerable. Logs files and model checkpoints is available at Baidu Netdisk:
Link: https://pan.baidu.com/s/13XlTxPSeRK21ls9EH28sow Password：1ydk

为什么我用你的权重测试结果这样呢？我自己训练了十几轮也是这样


3.3.3 release ETA?

Is there any planned date for 3.3.3 release on Maven?

I'll get it out this week.

I pushed a 3.3.4 to maven central today.


Python: migrate GH Action dependencies for Ollama model downloads, move to Azure assets

During SK integration tests, we perform 5 Ollama model pulls:
ollama pull ${{ vars.OLLAMA_CHAT_MODEL_ID }}
ollama pull ${{ vars.OLLAMA_CHAT_MODEL_ID_IMAGE }}
ollama pull ${{ vars.OLLAMA_CHAT_MODEL_ID_TOOL_CALL }}
ollama pull ${{ vars.OLLAMA_TEXT_MODEL_ID }}
ollama pull ${{ vars.OLLAMA_EMBEDDING_MODEL_ID }}

This puts a lot of stress on the network, is prone to failure, and adds latency. For example, here's a failure: https://github.com/microsoft/semantic-kernel/actions/runs/11685739831/job/32539906324#step:10:966.
We do need coverage for AI connectors; however, it may make more sense to deploy one Azure resource that Ollama can use to handle all the chat completion related operations, and one embedding model for those tests.

This model may work for the tool call scenario: https://ollama.com/library/smollm2:135m


2340: Enhance karate summary report

-  Add skipped scenario count
-  Add pass percentage
-  Add totals row

Description
Thanks for contributing this Pull Request. Make sure that you submit this Pull Request against the develop branch of this repository, add a brief description, and tag the relevant issue(s) and PR(s) below.

Relevant Issues : (compulsory)
Relevant PRs : (optional)
Type of change :

[ ] New feature
[x] Bug fix for existing feature
[x] Code quality improvement
[x] Addition or Improvement of tests
[ ] Addition or Improvement of documentation

The approach is detailed here:
https://github.com/karatelabs/karate/issues/2340#issuecomment-1890260295

Something to note - this is a breaking change i.e. getScenariosTotal becomes getRunScenariosTotal and Results is a public interface so I think this will need highlighting in a change log.

@codehackerr do you think we can keep it as getScenariosTotal- tagging @rc2201 because I think this was requested by only that team :| i haven't seen any other team care about skipped scenarios

changes reverted in https://github.com/karatelabs/karate/commit/8b911471869d734dc807d651d2d1541fc2aa2720

@ptrthomas do you want me to reopen with the name getScenariosTotal reinstated ?

@codehackerr no I would hold for now, most teams are fine with karate - and if anyone needs a custom report they can write their own: https://stackoverflow.com/a/66773839/143475


Convert enum element to plain value. OKTA-393048

Related to https://github.com/okta/okta-sdk-python/issues/198
Example of output (used app config from the issue above):
print(type(app), app.sign_on_mode, type(app.sign_on_mode))

<class 'okta.models.application.Application'> BROWSER_PLUGIN <class 'str'>

Looks like this may be a breaking change. If someone is already taking config["signOnMode"] and calling .value already, what happens?
Yes, it is a breaking change if someone is already calling .value, but config for internal use only and I haven't seen any such usecase. Also, all existing integration tests passed.

Closed accordingly to another solution https://github.com/okta/okta-sdk-python/pull/215


Ensure all common-types files are included in the latest version (v5)

ARM (Control Plane) API Specification Update Pull Request
PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

[1] public repo review queue, private repo review queue
The PRs are processed by time opened, ascending. Your PR may show up on 2nd or later page.
If you addressed Step 1 from the diagram and your PR is not showing up in the queue, ensure the label ARMChangesRequested
is removed from your PR. This should cause the label WaitForARMFeedback to be added.
[2] https://aka.ms/azsdk/support/specreview-channel
[3] List of SDK breaking changes approvers in pinned Teams announcement
[4] public repo merge queue, private repo merge queue
If you need further help with anything, see Getting help section below.
Purpose of this PR
What's the purpose of this PR? Check all that apply. This is mandatory!

[x] New API version. (Such PR should have been generated with OpenAPI Hub, per this wiki doc.)
[ ] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix swagger quality issues in S360.
[ ] Other, please clarify:

edit this with your clarification

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[x] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
[x] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to Step 2, "ARM Review", for this PR.

Breaking changes review (Step 1)

If the automation determines you have breaking changes, i.e. Step 1 from the diagram applies to you,
you must follow the breaking changes process.
IMPORTANT This applies even if:

The tool fails while it shouldn't, e.g. due to runtime exception, or incorrect detection of breaking changes.
You believe there is no need for you to request breaking change approval, for any reason.
Such claims must be reviewed, and the process is the same.

ARM API changes review (Step 2)

If this PR is in purview of ARM review then automation will add the ARMReview label.
If you want to force ARM review, add the label yourself.
Proceed according to the diagram at the top of this comment.

Getting help

For general PR approval workflow, see the diagram at the top of this comment.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

Worry based on vaguely remembered past discussions where I never fully understood what the right answer is.
While it seems technically accurate to model these things with uuids,
I vaguely recall in the past some downside that if we model it as uuid, then it gets modeled differently in the SDK, so it might e.g. become a breaking change to update from one common-types to the other with the different format? (I wonder if the SDK still does it that way?)

hmm I recall we made a similar change in the past , but we can have extra pair of eyes look at this. @markcowl ?

In reply to:<PHONE_NUMBER>

Worry based on vaguely remembered past discussions where I never fully understood what the right answer is. While it seems technically accurate to model these things with uuids, I vaguely recall in the past some downside that if we model it as uuid, then it gets modeled differently in the SDK, so it might e.g. become a breaking change to update from one common-types to the other with the different format? (I wonder if the SDK still does it that way?) And if so I would worry that maybe its not worth the pain. Anyone else have strong opinions on uuids?

@bdefoy , format is not processed in client SDK side.

/azp run


Improve clearing the current console line

Clear the previously written line instead of clearing the whole console window width. This way, when resizing the console window, lines don't wrap.
Here's a GIF to better understand what happens. The first two message batches use the console width (code before this commit). The last two message batches use the new code that clear only what's needed. Dots have been added (second and fourth samples) instead of spaces to better see why line wraps.

Thank you for your contribution! This fix looks really good to me.

Thanks for merging and releasing a new version so quickly ! 🎉


Create Xamarin iOS specific project

This adds a Xamarin.iOS project (non PCL). This is needed by my app Continuous, but I hope it will also serve as a base for extending the library to use Apple's native Accelerate framework (BLAS and LAPACK).

Could it work to use globbing here like we do with the other derived projects, e.g. here? Mainly to make sure we cannot forget to update it when files are being added. This is assuming any development happens on the primary project.

Ah, it started out globbed but Xamarin Studio trickily changed it on me. Fixing now...

I assume the output of this project would have to end up in the NuGet package in the end?

In the end yes, but I don't see any reason now until it actually has the native providers working.

NB: Would be great indeed if we could support Apple's native Accelerate framework as linear algebra native provider!

I added the F# project too but had to change to use the bigint ( - ) operator. Xamarin for some reason doesn't include bigint.Negate.

Thanks!


Feature/validate entity

Coverage increased (+0.02%) to 91.53% when pulling c2fcc5dc57fb8889b8f142fee41fdc16db9111e0 on feature/validate-entity into e5c54b349336fd041864fa215735e976787ebb34 on develop.


Volume as a Fan is on at 0% when te TV is off

Hello Webos Tv team,
I have an issue with the new “Volume as Fan” option, the control in HomeKit shows a on when the Tv is off and the volume is at 0%, I expect this behavior when the Tv is on and on mute but not when the Tv is off.
kind regards,

Yeah, you are completely right, this is a bug. Should now be fixed in version 2.3.2


created lint for checking common name length limit

lint to check if the common name is too long

Hi @titmus, thanks for the contribution. I believe that this lint is already covered here: https://github.com/zmap/zlint/blob/master/v3/lints/rfc/lint_subject_common_name_max_length.go.

Hi @titmus, thanks for the contribution. I believe that this lint is already covered here: https://github.com/zmap/zlint/blob/master/v3/lints/rfc/lint_subject_common_name_max_length.go.

I think we'll decline this PR for now. Let us know if we missed something!

I think we'll decline this PR for now. Let us know if we missed something!


Implementation strange

I find the implementation of the CarouselView strange.  I am seeing a problem on Android where the second invocation of a CarouselView does NOT listen to INotifyCollectionChanged on ItemsSource.  This is caused by the fact that the SetNativeView on Android is only called when Element_SizeChanged or when Orientation changes.  This is a problem because OnElementPropertyChanged ignores all property changes if viewPager == null.  Therefore, if SetNativeView is not called before element properties start to change, like ItemsSource, all of the handlers for those property changes never execute.  For ItemsSource, this means INotifyCollectionChanged is never added.
The reason I find this implementation strange is why wouldn't the native control be created when the Element is first attached in OnElementChanged.  Why wait until Element_SizeChanged or Orientation chnages?
For some weird reason, the first invocation of my page with CarouselView has the correct order where SetNativeView is called BEFORE ItemsSource changes so everything works.  Any subsequent time my page with CarouselView is opened, SetNativeView is called AFTER ItemsSource changes so INotifyCollection is never registered.
I don't set my ItemsSource until OnAppearing yet for some reason, the initialization of the CarouselView on Android doesn't always happen BEFORE OnAppearing.
I am not sure what to do.
Also, on iOS, SetNativeControl is called MUCH more than on Android.  Android has 2 places where it is called and iOS has 6.

@scastria could you test my implementation as well https://github.com/AndreiMisiukevich/CardView ?

Will take a look

INotifyCollectionChanged on the ItemsSource doesn't have any relationship with where you set the native view. If i don't set it when the final size of the Element is set, the carousel will not know it's dimensions and as a results, its children neither.

Can you provide a demo reproducing the issue?

I am getting close to release date. Please submit a demo reproducing the issue if you want a fix to be included. Thanks


[TRANSLATION] Add docker section on CONTRIBUTING.md portuguese translation

There's a missing piece on the Portuguese translation comparing with the original one, the docker section.
I'm creating this issue to fix it.

Thanks @carlan ! I will help out with this one ;)


Add Gnosis Network

Fixes | Closes | Resolves #

Anything marked as optional that you didn't need to fill in, please remove it from the PR description. Choose one of the keywords above to refer to the issue this PR solves, followed by the issue number (e.g Fixes # 666). If there is no issue, remove the line. Remove this note after reading.

Changes:

Types of changes
What types of changes does your code introduce?
Put an x in the boxes that apply

[x] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Other (please describe):

Testing
Requires testing

[x] Yes
[ ] No

In case you checked yes, did you write tests?

[ ] Yes
[x] No

Comments about testing , should you have some (optional)
Further comments (optional)
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

Codecov Report

Merging #73 (40075da) into develop (6959fba) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           develop      #73      +/-   ##
===========================================
+ Coverage    84.61%   84.63%   +0.01%
===========================================
  Files           32       32
  Lines         1853     1855       +2
===========================================
+ Hits          1568     1570       +2
  Misses         230      230
  Partials        55       55

Flag
Coverage Δ

unittests
84.63% <100.00%> (+0.01%)
:arrow_up:

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

Impacted Files
Coverage Δ

configs/init.go
100.00% <100.00%> (ø)

internal/pkg/generate/generate_scripts.go
96.48% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Could this HyenaDNA model be used for a pure language task?

Could this HyenaDNA model be used for a pure language task? Of course with some changes, such as a tokenizer for language! And maybe some other things ? Which other things would that be?
If this can be done, than that would give an enormous advantage of being able to work with a giant context size while still having an acceptable (or even a very good) performance for training and inference! Am I correct here?
Also I saw a mention of the HyenaDNA model being able of in-context learning, which is a very important prerequisite of such a model!
I have not read the paper, but could you show a table with a comparison between the pros and cons of a standard normal transformer and a HyenaDNA model?
But my main question is:
Could this HyenaDNA model be used for a pure language task? And how exactly to go about actually implementing that? What would be gained in comparison with using a conventional Transformer for that?
Thank you for this amazing development! What a time to be alive!
Happy New Year for you and the entire team of HyenaDNA!

yes


[json-rpc] update json-rpc-spec.md, split it into multiple md files

Refreshed document with latest codebase change.
Split one big doc into small md files and created table of contents in README.md for easier navigation.

@bors-libra land

:clipboard: Looks like this PR is still in progress, unable to queue for landing

@bors-libra land


Fix install problem

Fix install when i dont have data inside  cataloginventory_stock_item.

This is the fix for #2.

Close, sorry for the duplicate pull request, the other one have both.
Still learning making pull requests.


Show same header everywhere

The index.html shows a different header than all other sites. If one clicks on one of the links in the header, for example documentation, the mouse may select downloads afterwards because the position of the header is slightly different.
But that is just a minor issue.

Thanks! Not sure I can do much about it given all the dynamic resizing, but I'll keep it in mind when I touch this the next time!

Ok, got it down to a small offset, is this fine now?

Still not perfect but good enough for me. ;)

Thanks!


[feature request] Give a human readable description for MessageId

Currently the MessageId cannot be converted to a human readable string.
>>> producer.send('hello'.encode('utf-8'))
<_pulsar.MessageId object at 0x00000226E895AC70>

@BewareMyPower I like the idea too, any thoughts on what would make for a nice string representation of a MessageId? Something indicating the entry_id, ledger_id, etc?

I think we can follow the description of the Java client, i.e. 1:2:3 means the ledger id is 1, entry id is 2, partition index is 3. 1:2:3:4 means the batch index is 4 in addition to 1:2:3. We can reuse the implementation of the C++ client and we should modify the C++ wrapper becase send API returns the MessageId in the _pulsar module, not pulsar. It should be easy to implement, see examples here: https://pybind11.readthedocs.io/en/stable/advanced/classes.html
        .def("__repr__", &Vector2::toString);

Awesome, thanks @BewareMyPower . Yep should be pretty straight forward. Only immediate question I have - is there actually an existing toString (or similar) implementation on the C++ client for MessageId? I looked here: https://github.com/apache/pulsar-client-cpp/blob/main/lib/MessageId.cc and didnt see it. I guess we could have something like:
    std::string toString() const {
        return std::to_string(impl_->ledgerId_) + ":" + std::to_string(impl_-> entryId_) + ":" + std::to_string(impl_->partition_)
    }

With an added conditional to include the batch index if needed. I just wanted to make sure im not missing somewhere where this has already been done.

In C++ we usually don't provide a toString method, instead, a operator<< is provided so it can be reused to write an object to standard output, files or strings via std::ostream.
https://github.com/apache/pulsar-client-cpp/blob/63c424555cdb1209c82e2f844d7414c1fc399ef8/lib/MessageId.cc#L121
You can see here for how to convert a MessageId to std::string:
https://github.com/apache/pulsar-client-python/blob/cbd31e75adc592ee16dd1698335f6f34b8fb4844/src/message.cc#L53-L55

Thanks @BewareMyPower - very unfamiliar with C++ so appreciate the guidance 👍 . I'll open a PR soon

Merged in as of today!


Create snippets from editor selection

In the edit mode, I think it would be better if user take right mouse button click to define a custom code snippet.
One of the situations would be like this:
The user can select multiple line of the code and click right mouse button, then popup a menu and select "convert to code snippet" or something else.
All in all, we want a simple and fast way to create custom code snippet

fyi @jrieken

I like, had similar ideas the other day

I was a iOS developer turned to be a web front end developer, so same idea came from Xcode using experience.

Agreed. Would make snippets even more approachable and friendly. I never have enough time to sit down and define a code snippet (even though it's only a few lines), but I can definitely see myself converting some code I've typed a million times in to a snippet by clicking my mouse a few times.

This'd make VS Code much more powerful for me, I don't currently use snippets mostly due to lack of this functionality 🙏
I'll try the extensions recommended here, but I'd argue it'd be better if users were able to create their own easily without an extension.

@jrieken How is the status here, are you guys still interested in a solution inside of vscode or are the listed extensions the way to go? :)

I personally would love the right click > create snippet functionality. Definitely still interested in this solution.

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.
If you wonder what we are up to, please see our roadmap and issue reporting guidelines.
Thanks for your understanding, and happy coding!

Please do reconsider, this would make writing and using snippets a breeze.


Parsing of codemeta.json is incorrect

http://citeas.org/cite/https://github.com/ropensci/piggyback finds the codemeta.json file, but parses it incorrectly; using the DESCRIPTION as the title.  (should use "name", since schema:name is owl:sameAs dc:title).

This is fixed. What do you think of pulling the version from that file if it's available? So in an APA citation for this package it would include (Version 0.0.9) after the package name.

Nice.  Yes, I think pulling the version as makes sense (could be done from the DESCRIPTION file too).
On the codemeta parsing, it might also be good to check first for a referencePublication field (though maybe that should be renamed something more intuitive like suggestedCitation or citeAs  see https://github.com/codemeta/codemeta/issues/144).  The name field etc will always refer directly to the SoftwareSourceCode object, whereas this field is a ScholaryArticle type can describe a paper associated with the publication instead (identical to what CiteAs very nicely does when it finds CITATION files)!
On including versions, as you no doubt know, including versions is considered best practice, e.g. by the Force11 working group paper, but I'm not particularly bullish on it myself.  I agree that version information is important, but the problem is that there's no way to also capture precise versions of the dependencies, since the software package itself won't state these -- by design, most software is compatible with multiple versions of it's own dependencies.

Ok the software now pulls the version from codemeta.json. Also, as you mentioned if a citation field is present, it will use the fields in that part of the document as the input to be parsed.


ResNet flatten layer shape issue

Hi,
First of all thanks for sharing. I ran your ResNet code and found your implementation of the torch.flatten function appears to be outdated. According to your syntax, the batch_size dimension will also be flattened, resulting in an incorrect shape before being passed to the fully connected layer.

Hi, First of all thanks for sharing. I ran your ResNet code and found your implementation of the torch.flatten function appears to be outdated. According to your syntax, the batch_size dimension will also be flattened, resulting in an incorrect shape before being passed to the fully connected layer.

Thank you!
It appears to me that you are right. I checked the same problem on https://stackoverflow.com/questions/60115633/pytorch-flatten-doesnt-maintain-batch-size and fixed my code.
Incorrect:
input = torch.flatten(input)

Correct:
input = torch.flatten(input, start_dim=1)


Only style mat-input-elements in mat-form-field

Material input elements only need to be styled when used in material form fields.
Constraining the .mat-input-element class inside .mat-form-field ensures that any inputs using the matInput or matnativecontrol directive not inside a material form field will not be styled unnecessarily.
Example use case:
We are a small team building a custom form-field component that uses matInput to communicate with inputs. If the page also has a material form field component, extra styles are applied to all inputs with matInput including our own custom form field.

I have signed a CLA. Please rescan the cla/google check


Export Database and Collection types

Please export the type for Database and Collection<T> types so we can store them in variables.

It would also allow to have the documentation on<EMAIL_ADDRESS>


Refactor: rename one of the TargetConfig classes

Rename one of these TargetConfig classes
https://github.com/numba/numba/blob/38ab89dd369a14b8826d3fa30d080aa083aed00b/numba/core/dispatcher.py#L28
https://github.com/numba/numba/blob/38ab89dd369a14b8826d3fa30d080aa083aed00b/numba/core/targetconfig.py#L99

@sklam  Is it still opened ?

This is a maintainer task. See https://github.com/numba/numba/issues/7150#issuecomment-896073525 for details.


Some units added

Added ValvePosition, ValveDriveSpeed, RotationalSpeedChangeRate, PressureChangeRate. Changed abbreviations with prefixes for Pressure unit (ru-ru culture).

Hello!
Let's start from the end of the list.
ValveDriveSpeed.json
We discussed that point in our team once again and decided we don't need it actually. So, I can remove it at all.
ValvePosition.json
I agree, it looks like the Ratio, but we need also "complement" units. And I'm confused about their abbreviations. Could you advise me?
RotationalSpeedChangeRate.json
We think RotationalAcceleration sounds better. I can rename the unit. Ok?
PressureChangeRate.json
As I understand right, it's OK for you and no changes needed in that unit. Right?

ValveDriveSpeed
Ok by me to delete this from the PR.
ValvePosition
It seems the term "complement" is used to represent the "other" part of a fraction/ratio/percentage, so lets go with that. If you see in Ratio.json, I specify empty string for DecimalFraction as abbreviation. I would expect the same for ComplementDecimalFraction, if we are to name it that. The only conflict in that, is that we can't unambiguously parse the two with Ratio.Parse("0.5"), but that makes sense anyway I think. For that case, I find it reasonable to do a double.Parse() first, then create it with Ratio.FromDecimalFraction() or similar for complement units.
So to summarize

Add Ratio.ComplementDecimalFraction with empty string as abbreviation
Add Ratio.ComplementPercent with % as abbreviation.

Rename to RotationalAcceleration is fine by me.
PressureChangeRate is fine as it is, however there are many other pressure units in Pressure.json. I leave it up to you to decide whether to add more or not.

Leave a comment when you have updated the PR so I am notified. Thanks!

Just checking in on this, still working on it?

Unfortunately, we got some more prioritized tasks, so we had to postpone working on this.
We plan to resume working on this soon.

Thanks, no problem. Just checking in.

Hello Andreas!
I have updated the PR.
I added Ratio.ComplementDecimalFraction and Ratio.ComplementPercent units as you advised.
Also after some investigation we decided we don't need RotationalSpeedChangeRate (or RotationalAcceleration) unit any more. So it was deleted as well as ValveDriveSpeed and ValvePositionUnit.
Please take a look. Thanks!

It seems we don't auto-generate any Parse() tests, which would probably reveal that either Percent or ComplementPercent does not parse into the right amount, same for DecimalFraction and ComplementDecimalFraction.

So I see from previous discussion that I argued Parse("5%") should always parse as Percent, not ComplementPercent, which I still think is fair. Same for DecimalFraction. The problem is just to ensure that this in fact happens, and not the other way around.
Scratch my previous comment about changing abbreviation to "% comp.", I don't think that makes sense. However, I just came to realize something. Do we really need a complementary unit, or would it be sufficient to have a FromComplement and ToComplement methods instead? So the unit of representation is still just Percent or DecimalFraction, but you have convenience methods/properties for converting to the complement.
Example:
These would be equal:
Ratio.FromPercent(30);
Ratio.FromComplementPercent(70);
Ratio.FromPercent(70).ToComplement();
Ratio.FromDecimalFraction(0.3);
Ratio.FromComplementDecimalFraction(0.7);
Ratio.FromDecimalFraction(0.7).ToComplement();

Hello Andreas!
After some thinking we decided to perform all conversions with complement units on our side.
So we don't need to include them to the library.
If no objections, I will remove Ratio.ComplementDecimalFraction and Ratio.ComplementPercent from the PR.
Sorry for bothering you.

Ok, sounds good to me.

I've updated the PR, please take a look. Thanks!

This looks good to me now, thanks!

Nuget 3.21 is now out.


[5.0] IRGen: Don't assert on keypaths that use a subclass as root

class A {
let x : Int = 0
}
class B : A {}
_ = \B.x

No ABI impact
Correctness fix: We would emit wrong offsets for stored properties in
this case in an non-assert build.

rdar://46562046

@swift-ci Please test


added TODO about modeling haskell hashing;

Signed-off-by: Harold Carr<EMAIL_ADDRESS>

@haroldcarr, sorry, I've rather hijacked this PR.  Feel free to merge if you're happy with it.

I am going to squash/merge.
I want to have more discussion on hashing in our next meeting (for bandwidth).


https://www.facebook.com/groups/free.code.camp.fullerton.city/

https://www.facebook.com/groups/free.code.camp.fullerton.city/

@odhiambo123 Hi can you confirm this is Fullerton City, California?

Sorry for the late response here @johnkennedy9147 yes I am based in Fullerton City, I just haven't had enough Fullerton people in the group yet. https://www.facebook.com/groups/free.code.camp.fullerton.city/ is based in Fullerton


Sad Sax Man user scenario

Great user scenario.  Lines 12 through 15 should probably be moved to the top of the document since they're a general outline for all of our scenarios, but we can update that in a future commit.


Rebase off Mesos 1.0.x branch to get containerizer env fix.

Targeting for 1.8.5

@cmaloney Rebased after @kaysoky 's #572 landed, looking green.


Import 2017 Google Summer of Code blog post and latest changes to previous blog posts.

CC @laurentlb for the GSoC blog post


feat: generalize tensor product constructions to semirings

The current proofs already work for semirings.

Is it worth to benchmark this?  It might simplify the typeclass search space to only look for Semiring instances...

!bench

I agree that it probably will not have a huge effect overall, but tensor stuff seems to be straining TC, so any little helps!

bors merge