Register iCub iCubManchester01 and update robotology-superbuild

Hi,
we are based in University of Manchester and we have an iCub in our lab with a version of robotology-superbuild 1.2.
We want to update the robotology but the name is not in the page of list of iCub.
Name: iCubManchester01
Could you please help us to register iCub and obtain the correct configuration file?
Thank you,
CoRoLab University of Manchester

Hi @albertolillo23
Thanks for reaching out.
We will evaluate this request in terms of the required activities and get back to you with an estimate.
cc @Nicogene

For more information, I add that the version of yarp is <IP_ADDRESS>
Thanks

Hi @albertolillo23!
From:

https://github.com/robotology/robots-configuration/pull/533

We decided to put the configuration files of the robots we didn't have news of for a while in the robot-icebox folder to shorten the list of maintained robots and the required efforts for keeping this repo up-to-date.
Having YARP 2.3.72 means that on your robot the software you are running on the robot is stuck to ~ 2018, maybe for you is sufficient to upgrade it to just before the institution of robot-icebox, i.e. the Distro 2023.05.0?
This should be possible right now without the need of any intervention.
For upgrading, I suggest starting from a clean state, and follow these instructions

for the workstation -> https://icub-tech-iit.github.io/documentation/sw_installation/linux_from_sources_superbuild/
for the pc104 -> https://icub-tech-iit.github.io/documentation/sw_installation/icub_head_superbuild/

using the  v2023.05.0 tag.
Please let us know if it is sufficient, if you instead want to put your robot out from the robot-icebox more actions are needed, first of all, changes to the configuration files are needed to make them compatible with the latest software changes.
A robot similar to yours that can be taken as example is iCubLondon01 but it took also several hw maintenance to make it up-to-date:

https://github.com/robotology/icub-tech-support/issues/1171

Hi @albertolillo23!
any update on this? Have you managed to update to the distro 2023.05.0?

Hi @Nicogene!
Sorry for the late reply, two days ago we tried to do the update.
Following the guide in the link regarding pc104, I noticed that in our pc, inside the robot folder we do not have a pre-existing "robotology-superbuild" folder, but I only have these folders:

icub-basic-demos
iCubContrib
icub-contrib-common
icub-firmware-build
icub-firmware-shared
icub-main
robots-configuration
yarp

So I downloaded it and followed the compile commands.
When I run the command (in the path: /usr/local/src/robot/robotology-superbuild):

cmake -DROBOTOLOGY_USES_GAZEBO:BOOL=OFF -DROBOTOLOGY_ENABLE_ICUB_HEAD:BOOL=ON ..

I get an error saying:

"CMake Error: The source directory "/usr/local/src/robot" does not appear to contain CMakeLists.txt".

How can we solve it?
Thanks for the support.

Hi @albertolillo23 you need to do the following steps:
cd robotology-superbuild
mkdir build && cd build
cmake -DROBOTOLOGY_USES_GAZEBO:BOOL=OFF -DROBOTOLOGY_ENABLE_ICUB_HEAD:BOOL=ON ..
make

Once the build is finished you need to add this line at the beginning of the bashrc
source /usr/local/src/robot/robotology-superbuild/build/install/share/robotology-superbuild/setup.sh

Once the build is finished you need to add this line at the beginning of the bashrc

Probably, it could also help cleaning up the content of bashrc by removing any reference to YARP_* and ICUB_* env variables, including relevant paths appended to PATH and LD_LIBRARY_PATH.

Hi @albertolillo23!
Did you manage to install the distro 2023.05.0 via robotology-superbuild?

Hi @Nicogene,
sorry for the slow response, but we don't always have the availability of the lab where iCub is located, we will try it on Thursday and as soon as it is done we will let you know.
Thanks for the support.

Hi @Nicogene
Today we tried it and found this error:
CMake Error at src/libYARP_eigen/src/CMakeLists. txt:25 (target_link_libraries):
	The link interface of target "VARP_eigen" contains:

		Eigen3:: Eigen

	but the target was not found. Possible reasons include:

          * There is a typo in the target name.
          * A find package call is missing for an IMPORTED target.
          * An ALIAS target is missing.

CMake Error at src/libYARP_math/src/CMakeLists. txt:86 (target_link_libraries):
	Target "VARP_math" links™ to:

		Eigen3: : Eigen

        but the target was not found. Possible reasons include:

            * There is a typo in the target name.
            * A find package call is missing for an IMPORTED target.
            * An ALIAS target is missing.

How can we solve this?
Thanks.

Hi @albertolillo23,
To install the required dependencies, you have to follow these instructions:

https://github.com/robotology/robotology-superbuild?tab=readme-ov-file#linux-from-source-with-dependencies-provided-by-apt

Here is instead the complete guide for installing from sources:

https://github.com/robotology/robotology-superbuild?tab=readme-ov-file#source-installation

Hi @albertolillo23,

it can no longer find the other parts,

This is fine, you don't have to worry about it, the superbuild will clone and build the missing repositories.

So as to start from a clean situation and download and build everything, upgrading the pc to a newer version of Ubuntu, now is 16.04.

We do not support Ubuntu 16.04, so yes I suggest you upgrade it to at least Ubuntu 20.04
Ccing @AntonioConsilvio for the upgrade procedure of the pc104

Hi @albertolillo23
We had an internal meeting yesterday with our coordinator @maggia80 about the update of iCubManchester01 and, given that it turned out to be quite old software-wise, we think it may be worth running a thorough maintenance.
In our experience, in fact, updating/upgrading the SW of a robot equipped with old HW is a painful procedure if carried out remotely. Also, while doing so, we often find that some HW intervention is required.
Therefore, we suggest that you get in contact with our manager Andrea Derito (✉ andrea.derito[at]iit.it) to ask for a quotation.
cc @andreaderito @Fabrizio69 @Nicogene


Update CHANGELOG.md

Fixes #IssueNumber
Changes proposed:

[ ] Add
[ ] Delete
[x] Fix
[ ] Prepare

Closing in favor of #1723

Thanks @MongkonEiadon for your contribution but there was a previous PR. Maybe next time! 😉


componentWillMount is deprecated warning

Hi,
Be careful, componentWillMount has been renamed and is not recommanded for use with React 16.9.0
Thx for the fix

Have you resolved this issue ?

Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-async-component-lifecycle-hooks for details.

    * Move data fetching code or side effects to componentDidUpdate.
    * If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://fb.me/react-derived-state
    * Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.

    Please update the following components: MultiSlider

Get this warning every time a the slider component is mounted

Maybe this is fix for this issue:
https://github.com/ptomasroos/react-native-multi-slider/compare/master...balbirsng:master
@balbirsng what about to create new PR for this ?

I am also getting this error message, it would be great if the previous mentioned fix worked or one was developed. Thank you in advance!

I have tested it and no this "fix" not works.. but its appers that this project is not actively maintained @ptomasroos ?

I’m currently not in the process of releasing updates to our apps. But feel free to send a pull request!

ok you can review this :)
https://github.com/ptomasroos/react-native-multi-slider/pull/151

Any updates?

Fixed in master! Soon published

@ptomasroos imo, this really shouldn't be closed until the fix is pushed to npm. Most of the users submitting issues here are still working off 1.0.0...which is almost 2 years outdated.

Thanks for the feedback. But github closes all issues on merge of a pull request for instance. I haven’t seen a single repo keeping issues open until released.


Remove ToC and remove headings numbers

Solution for all other warnings encountered in other .md files concerning:

newlines, whitespaces and trailing spaces
(un)necessary characters and typos
hierarchy and indentations
unused labels
code blocks
formatting of the text

It contributes to #329
Fixes #329


Arrange questions in folders.

To be arranged topic wise? Or, according to the language? Probably, topic -> language?

I guess topic wise if required. Because language is almost immaterial, I feel its more upto personal preferences.

But I saw your format for comment as a preamble to question today, which mentions sources and all. I guess that's something  important. Also I putting a leetcode question number in front of my submission for quick ref I don't know if its necessary.
And as an aside how do you even find the solution complexity.
Also leetcode does a good job of organising questions topic wise, can we leverage that.

This is done


adding start to budgeting

We will definitely need help from Sandy etc. to make sure we aren't summarizing this incorrectly and to make it more understandable to people who are less familiar with grant language.
I pulled some directly from the websites and I find it a bit confusing still, but at least this gives people something to review.

@cansavvy  this is interesting... the url page is blank yet it says there is a broken url

@cansavvy this is interesting... the url page is blank yet it says there is a broken url

It’s telling me ‘no broken urls’ in the comment above.

@cansavvy this is interesting... the url page is blank yet it says there is a broken url

It’s telling me ‘no broken urls’ in the comment above.

huh ok I guess it just didn't refresh that for me - I made an issue about this in the reports repo

I guess maybe we would just want to tell people to refresh then


Add visitor to remove bias from bn_ layer inputs (#closes 2155)

As I explained in #2155, this PR adds a visitor that will automatically remove bias learning from all layers that are inputs of bn_ layers.

I think it's ready for review :)

Thanks for the PR :)
As an side, you might want to add a .disable_bias() to the layers that makes them not execute the bias addition at all, since that will run faster. Then instead of calling set_bias_learning_rate_multiplier() you could call an equivalent disable_bias().

Yes, that was bothering me, the fact that even all the values are 0, we're still performing the computation. I stared looking at the fc_no_bias to see how you disabled the bias there. I will try to do it :)

Thanks for the PR :)
As an side, you might want to add a .disable_bias() to the layers that makes them not execute the bias addition at all, since that will run faster. Then instead of calling set_bias_learning_rate_multiplier() you could call an equivalent disable_bias().

Yes, that was bothering me, the fact that even all the values are 0, we're still performing the computation. I stared looking at the fc_no_bias to see how you disabled the bias there. I will try to do it :)

Na, don't do it like fc_no_bias.  It's probably nicer and simpler if this is just a normal runtime bool in each applicable layer that controls if the bias is added or not. Then a member function can just set it to true or false.

Done, I hope this is what you expected. I had to modify the serialize functions as well, but I made sure to keep backwards compatibility: I've successfully loaded and run the following models:

resnet34 model, which contains fc layers
dlib_face_recognition_resnet_model, which contains fc_no_bias and con layers
a saved sync file from the dcgan example, which contains con and cont layers.

I've also checked that the DCGAN example still runs. I've modified a little bit to print out the number of trainable parameters, to ensure the bias are not allocated when disabling the bias.

Do you think I need update the operator<< so that I show the bias status? Right now, the only way to know is by looking at whether the bias learning rates are printed.

Do you think I need update the operator<< so that I show the bias status? Right now, the only way to know is by looking at whether the bias learning rates are printed.

I thought about that earlier and I'm on the fence.  operator<< output is just for humans to eyeball and at some level adding more and more stuff to it makes it busy and hard to read.  Take a look at it for a printout of a network and set it however you think looks the most clear in that context.  But likely what you have in there now is fine.

I think it's more clear this way:

if we are using bias, keep it as it was, that is, print the bias multipliers
otherwise, do not print those, and print use_bias=false, so that users don't think there has been an error, or the output has been truncated.

I think it's a good trade-off, since we are not making the lines with bias even longer, and the ones without are still short in comparison.

I think it's more clear this way:

if we are using bias, keep it as it was, that is, print the bias multipliers
otherwise, do not print those, and print use_bias=false, so that users don't think there has been an error, or the output has been truncated.

I think it's a good trade-off, since we are not making the lines with bias even longer, and the ones without are still short in comparison.

Sounds good :)

Sweet, thanks for another cool PR :)

Thank you! I am really learning a lot by doing these things :)


Add a test framework for monitoring across mirror maker pipelines.

The newest update uses the RecordMetadata key field to propagate the source cluster partition across mirror maker while maintaining ordering.

Probably this needs use the XConfig classes.  Other changes could be in a different patch.  What do you say @lindong28 ?

@smccauliff I think the MirrorPipelineMonitor has a number of redundant methods that can be simplified. Are you suggesting that we can leave it as it is and refactor the code later? What are the "other changes" that can be in a different patch?

@lindong28 Just my suggestion:  the improvement that needs to be made before the PR can be merged is to use the XConfig classes rather than the methods that exist there already since that reuses the configuration code and is consistent with how the code is configured elsewhere.  Most of the other changes are either minor or are too large (e.g. better coordination of number of partitions).  The larger problems should be fixed with some other PR.

@WarrenGreen Thanks for all the effort to make the code better!

Thanks! LGTM. I just realized that props.getOrDefault is only available in Java 8. I will submit pull request to make it Java 7 compatible.


jQuery.foundation() is not a function

I am using foundation-sites plugins in my existing project, and after updating foundation to 6.4.1 $(document).foundation(); returns an 'is not a function error'.
But issue was solved by calling Foundation.addToJquery($); beforehand.
So question: is it a bug or a feature?

I've the same issue, your fix doesn't work either @voogieJames.

@klloe, before that I've updated jQuery to make sure its version is >= 3.. and also 'npm update -g'

@voogieJames Already use the CDN version

Hey @voogieJames @klloe I'd like to help track this down - how are you downloading and installing Foundation? What does your build look like? And are you using the built dist files or importing from the sourcefiles?

@kball I'm using the basic template and load all the necessary scripts via CDN
  <script src="https://cdnjs.cloudflare.com/ajax/libs/jquery/3.2.1/jquery.min.js" integrity="sha256-hwg4gsxgFZhOsEEamdOYGBf13FyQuiTwlAQgxVSNgt4=" crossorigin="anonymous"></script>
  <script src="https://cdnjs.cloudflare.com/ajax/libs/what-input/4.2.0/what-input.min.js" integrity="sha256-7wGy9IEPmo9Jk/I86siWbZFPeclfjFitAAfmvxBUc7k=" crossorigin="anonymous"></script>
  <script src="https://cdnjs.cloudflare.com/ajax/libs/foundation/6.4.1/js/foundation.min.js" integrity="sha256-Nd2xznOkrE9HkrAMi4xWy/hXkQraXioBg9iYsBrcFrs=" crossorigin="anonymous"></script>

  <script>
    $(document).foundation();
  </script>

Hi @klloe,
Using that exact pasted script, I see the following error:
Failed to find a valid digest in the 'integrity' attribute for resource 'https://cdnjs.cloudflare.com/ajax/libs/foundation/6.4.1/js/foundation.min.js' with computed SHA-256 integrity 'ssuvZ7clQBE8C6fdKygrQfRqIx5bFb/F/Abeqq1dr/w='. The resource has been blocked.

If I cut out the integrity hash it loads and works fine... I'm not an expert in how the integrity pieces work, but it seems like the issue is the foundation JS isn't loading at all

Hi @kball
So I am using npm(npm v. 5.1.0) for installing foundation-sites. Below is a part of my packages.json file:
...
"dependencies": {
    "foundation-sites": "^6.4.0",
    "jquery": "^2.2.4"
  },
  "browser": {
    "jquery": "./node_modules/jquery/dist/jquery.min.js",
    "foundation": "./node_modules/foundation-sites/dist/foundation.js"
  },
  "browserify-shim": {
    "jquery": "jQuery",
    "foundation": "foundation"
  },
  "browserify": {
    "transform": [
      "babelify",
      "browserify-shim"
    ]
  },
...

In my index.js file I import all necessary foundation modules, like so:
...
import $ from 'jquery';
import 'foundation-sites';
import 'foundation-sites/js/foundation.core';
import 'foundation-sites/js/foundation.util.mediaQuery';
import 'foundation-sites/js/foundation.toggler';
import 'foundation-sites/js/foundation.sticky';
...

And the mentioned problem (foundation is not a function) occurs when I try to call $(document).foundation(); function.
But as I mentioned before, if I run Foundation.addToJquery($); function first, then I can initiate foundation framework.

Hi @voogieJames I think this is a documentation problem, that we need to figure out how to address... and possibly improve on. I'd love your feedback and help to figure out how to best document this, or if there's a better way to approach this...
The root of the issue is that we wanted the module imports to be side effect free (for the backstory, see the discussion starting here: https://github.com/zurb/foundation-sites/issues/9438#issuecomment-266933957), but what that means is that when using the imports there is now an initialization step if you want to add them to the foundation jquery helpers.
For our built distfiles we do all of this invisibly to maintain backwards compatibility, but since you're using a module bundler you'll probably need to do more. For an example see this entry file that we ship with the new starter template: https://github.com/zurb/foundation-zurb-template/blob/master/src/assets/js/lib/foundation-explicit-pieces.js
You could also look at our default entry port for folks who just want to import foundation: https://github.com/zurb/foundation-sites/blob/develop/dist/js/npm.js

@kball So as an example, if we just wanted to initialise a single plugin, e.g. "Reveal", what are the required steps when using a module bundler?
Also, how could this be done on the fly? Many of us are now leveraging Webpack's code-splitting feature to only load the module we need. We may need to initialise a plugin after page load.

@justrhysism You can import a single plugin straight from that plugin's file (e.g. import { Reveal } from 'foundation-sites/js/foundation.reveal';
If you're doing stuff by hand, it may well be straightforward for you to do the instantiation yourself using a direct constructor (e.g. var thisReveal = new Reveal($('#my-reveal'), options)).
Or if you want to use the jquery helper (e.g. $(document).foundation()) you'd want to do something like:
// import jQuery
import $ from 'jquery';
// import core foundation (possibly misnamed due to legacy)
// to allow global bookkeeping & jquery helper
import { Foundation } from 'foundation-sites/js/foundation.core';
// import component
import { Reveal } from 'foundation-sites/js/foundation.reveal';

// set up the $.fn.foundation helper so you can just grab
// DOM elements and call foundation on them
Foundation.addToJquery($);

// Tell Foundation global bookkeeping/jquery helper about Reveal plugin
Foundation.plugin(Reveal, 'Reveal');

Let me know if this makes sense or what doesn't... really want to make the docs for this better.

Thanks for you timely response @kball, much appreciated.
Ah right - yes, being able to use the plugin directly is much nicer.
For thread followers:
import $ from 'jquery';
import { Reveal } from 'foundation-sites/js/foundation.reveal';

const options = { /* Reveal Options, if any */};
const $myRevealElement = $('#my-reveal-selector');
const myReveal = new Reveal($myRevealElement, options);

I'm using Foundation with Vue, and it's good practice (particularly for event listeners) to "clean up" in Vue's beforeDestroy() lifecycle method. I noticed that there's a _destroy() method on the class, but being prefixed with an underscore _ seems to indicate that it's private. Is there any reason this method is private? Or is this something which involves greater discussion and I should open another Github issue?

With respect to the docs, I think there needs to be a couple of versions depending on use case. Anyone using a bundler such as Webpack would greatly benefit from the new simplicity of being able to instantiate a component directly, without having to manually import the required dependencies. Big win.
But I think you'll probably also need docs for people upgrading to 6.4 from an older version, demonstrating the "quick fix" approach to keep people's projects going, but also maybe a side-by-side demonstration of the old-vs-new methods - because the changes are pretty significant (but definitely for the better).

@kball I've added some documentation here: https://github.com/zurb/foundation-sites/pull/10782.

I am having the same issue with "dist" packages. jQuery, Foundation 6.4.3 and my code are all in one JS file and it sometimes (mostly on back button) fails on "$(document).foundation();"

if you are reading this please check #10782 for instructions on how to fix this issue.

@ncoden I see #10864  has Milestone 6.4.4 set. I'm not familiar with how this translates to the release candidates – I installed 6.4.4-rc1 and don't see this working yet. Is that expected?
When I try to run it in a create-react-app setup, I get the following output during build:
Failed to compile.

Failed to minify the code from this file:

        ./node_modules/foundation-sites/js/foundation.util.core.js:24

Read more here: http://bit.ly/2tRViJ9

https://github.com/zurb/foundation-sites/pull/10864 was after RC1.

Also the error in your create-react-app project is not complete as there is no full stacktrace or error message. Or do you mean the error fixed by https://github.com/zurb/foundation-sites/pull/10864?

@DanielRuf makes sense, will keep an eye out then.
 I'll update my comment with those if that's helpful.

Hey @justrhysism did you ever get an answer about your _destroy() question?  I am in almost exactly the same use case as you. I'm importing the Equalizer plugin directly and instantiating it myself, and I'm wondering if there is any reason I can't call equalizer._destroy() when I need to remove the plugin from the element.
How did you end up handling this?

Actually, when I import { Equalizer } from 'foundation-sites/js/foundation.equalizer'; and then try to this.equalizer = new Equalizer(this.$el, {equalizeByRow: true});, I get an error that Equalizer is not a constructor. If I console.log(Equalizer), it shows as undefined.

It should be Foundation.destroy() or $('.tooltip').foundation('_destroy')
Please open a new issue as this is not about the initial issue.

In case anyone is wondering, the base Plugin class defines the public destroy method, so you actually can and should call destroy() on the equalizer instance.

Still biting me with webpack --mode production with import 'script-loader!foundation-sites/dist/js/foundation'; in the entrypoint file

@lessless not sure what you mean. Please open a new issues with more derails.


LOGIC System

A system that registers LOGIC objects similarly to ENT and PANEL objects. Should support defining custom logic objects, that each have a set of inputs and outputs, as well as Initialize and Think functions. Logic objects should be able to be enabled and disabled.  Should be connectable to other Logic-enabled entities or units.
Overall Logic system:

[x] LOGIC registration
[ ] Base Logic metatable
[x] Instantiation of Logic objects
[ ] Enabling/Disabling
[x] Entity tying
[ ] Logic sleeping (non-active in Sandbox and outside main game)
[ ] Support ENT-defined Logic (built directly into entities themselves)
[x] Support LOGIC tables basing themselves on another LOGIC table (LOGIC.Base = "logic_class")

Logic unit support:

[ ] Unit settings (with defaults)
[ ] Connection handling
[ ] Argument handling (binding argument to connection)
[ ] Dynamic arguments (using output to pass along the input argument)
[ ] Caller/Activator arguments (passing responsible player and logic unit along chain reactions)

Logic unit creation, networking, and connection now works! They act like our very own custom object type! :D

local LOGIC = {}

-- These are only used for UI; any output can be connected (you can make secret code-only outputs this way)
LOGIC.Outputs = {
	"UponPrintA", "UponPrintAnything"
}

local function doprint(self, str)
	print(str)
	print(type(str), str == "A")
	if str == "A" then print("Firing output") self:Output("OnPrintA", str) end
	self:Output("UponPrintAnything", str)
end

LOGIC.Inputs = {
	["Print"] = {
		Function = function(self, activator, caller, args, ...)
			doprint(self, args)
		end
	},
	["TimedPrint"] = {
		ParseArgs = function(args)
			local strs = string.Split(args, " ")
			if strs[1] and strs[2] then
				local time = tonumber(strs[1])
				if time then
					return {Time = time, Str = strs[2]}, strs[1] .. " " .. strs[2]
				end
			end
		end,
		Function = function(args, ...)
			if args.Time then
				timer.Simple(args.Time, function()
					doprint(self, args.Str)
				end)
			end
		end
	},
}
nzu.RegisterLogicUnit("nzu_logic_test", LOGIC)


Move GCM webhooks to dedicated Admission Controller

How to categorize this PR?

/area scalability
/kind enhancement
/priority normal
What this PR does / why we need it:
This PR moves Gardener-Controller-Manager related webhooks to a dedicated component/binary called Gardener-Admission-Controller. Introducing a dedicated webhook server allows us to efficiently run multiple replicas in the garden cluster and also follows a separation of concerns.
Prerequisite for #2781
Special notes for your reviewer:

I didn't remove the HTTPS settings for GCM because in the near future remaining endpoints should be protected by TLS (#2829)
The namespace deletion validator now works with the cached runtime-client instead of client + project informer + shoot  informer.

Release note:

Gardener validating webhooks have been moved from the `Gardener-Controller-Manager` to a dedicated component `Gardener-Admission-Controller`. Therefore, new values have been added to the Gardener Helm chart (`charts/gardener/controlplane`). Please consult the documentation (`docs/concepts/admission-controller.md`) for more information about the `Gardener-Admission-Controller`.

Gardener validating webhooks have been moved from the `Gardener-Controller-Manager` to a dedicated component `Gardener-Admission-Controller`. Please run `make dev-setup` to create the necessary configuration for this component for local development use-cases. `make start-admission-controller` starts the new component locally.

@rfranzke @timebertt let me address the last comments before you play around with it. I'll let you know asap.

Thanks for you feedback which is now incorporated in the PR:

Add readyz and healthz endpoints as well as readiness and liveness checks.
Fixed wait for cache sync and informer retrieval bug.

No additional comments from my side.
Looks great :)

Thanks @timuthy! Kindly update the pipeline definitions now that it's merged :)


Text color in CodeGlance scroll area does not match editor color theme.

My Android Studio 2.0 editor color scheme is "cobalt" but the CodeGlance scroll area displays what appears to be the default color scheme. Since I am used to my syntax coloring, this makes it harder to visually interpret the minimized text.

PHP Storm has the same issue, only selected coloring appears if at all and the issue is inconsistent across open files as some areas are all white while the same areas / code are correctly highlighted elsewhere.

@MonteCreasor: have you tried restarting the IDE? My guess is that CodeGlance uses the color scheme that is active at start up time.
When I change the color scheme of the IDE (PyCharm 2016.3 in my case) in File->Settings->Editor->Colors&Fonts, CodeGlance does not update its colors accordingly, making up for a confusing experience, indeed.

duplicate of https://github.com/Vektah/CodeGlance/issues/109


[PE-D][Tester C] Incorrect Edit Command Format for Room Number in Command Summary

This was what was provided in the UG:

This was the error message received:

Labels: type.DocumentationBug severity.Medium
original: chuahjiajie/ped#3

Proposed fix:

Update correct format for edit command


fix: [#4684] ESLint issues in botbuilder-azure

Addresses # 4684
#minor
Description
This PR fixes all the new ESLint errors and warnings that appeared after the ESLint packages' upgrade in the botbuilder-azure project.
Specific Changes

Removed 'only-warn' plugin from 'botbuilder-azure'.
All updated TS and JS files were due to prettier, mocha and some deprecated rules.

Testing
The following image shows that there are no more ESLint issues.

/promoted 4828


[ENG-1104] patch json.dumps to handle __wrapped__ objects

Unwrap proxied objects if the default serializer doesn't work.
Is this a good idea? That remains to be seen... but it does work.
import json

import reflex as rx

class State(rx.State):
    value: list[int] = [50]

    def foo(self):
        print(json.dumps(self.value))

def index() -> rx.Component:
    return rx.button("Foo", on_click=State.foo)

app = rx.App()
app.add_page(index)

Is this a good idea? That remains to be seen... but it does work.

Maybe we should rename it to __reflex_wrapped__ if we decide to patch python internals


Able to customize package.json

Allow users to customize package.json by providing either inline --packageJson or --packageJsonPath that points to an existing JSON file.

Thanks for the PR, @JohnCido!


Update py-ingestion-core version control and publish workflows to ignore json/data changes

Describe your changes :

See https://github.com/open-metadata/OpenMetadata/pull/2328#discussion_r789412880

Type of change :

[x] Bug fix
[ ] Improvement
[ ] New feature
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation

Frontend Preview (Screenshots) :
For frontend related change, please link screenshots of your changes preview! Optional for backend related changes.

Checklist:

[x] I have read the CONTRIBUTING document.
[x] I have performed a self-review of my own.
[ ] I have tagged my reviewers below.
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] My changes generate no new warnings.
[ ] I have added tests that prove my fix is effective or that my feature works.
[x] All new and existing tests passed.

Reviewers

Ingestion: @harshach @ayush-shah @pmbrull

I think we are not using the data models anywhere (as they don't have a title, they do not get generated "properly"). We could indeed remove them for now to ease the process and if at some point we start using those in the ingestion framework we can come back here.
Thanks


Change color of the file name to Light ones

When using Chernobyl, the information (e.g., filename, word counts) on top of the window is in dark color, thus cannot be distinguished. Please consider changing it to a light color.
For example, this is a screenshot using "Blackout Gamer" theme:

This is a screenshot using Chernobyl:

Many thanks!

Got it
Its a pity that I do not have a MacBook to test this theme, but I'll keep an eye on it.


rubocop: Set EnabledByDefault: true, disabling cops with offenses

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[ ] Have you successfully run brew typecheck with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

Part of #15297. Specifically, bullet point three of Mike's suggestion. After this, I'll start chipping away at switching cops on.
EnabledByDefault is a feature of RuboCop that enables all cops even those marked Enabled: false in core RuboCop.
I went through and disabled all the cops with offenses from this config change. This way we can do a piecemeal approach to enabling cops with offenses, while getting the benefits of the new cops with no offenses.
It is intentional that brew style comes back green here and there are no code style fixes.

I was going to put these in alphabetical order, but it's probably not worth it. Once we've moved sufficiently many of these to Enabled: true, if we're doing that, or if we decide we're not, then we can do that. But batching them into sections with TODOs for "these need looking at" seemed more sensible to me.

Ah, tap_syntax caught me out again. I'll add them to the list in the morning - now I must sleep.

Thanks @issyl0 looking great so far!

Great start, thanks again @issyl0!


Improve julia queries

Before:

After:

Before:

After:

The previous commit doesn't take care of all cases. If, for example, the end keyword is part of another expression, e.g. end-1, then it doesn't capture it. How can I express using this tree-sitter language that end should be captured at any level within a range_expression?

Before:

After:

Before:

After:

Before:

After:

This query is problematic:
((identifier) @type
  (match? @type "^[A-Z]"))

It captures variables that start with upper case and highlights them as types.
I disabled it but still need to find a replacement.
Before:

After:

@theHamsta mentioned that there are no "real priorities" between different queries. Can somebody explain to me how to get around this limitation? I have different queries that catch the same part of the code and I want to assign which one has more priority than the other.

((identifier) @type
  (match? @type "^[A-Z]"))

What's the problem with that? We also use it in other languages. Isn't using first letter upper case also a bad thing in Julia?

I have different queries that catch the same part of the code and I want to assign which one has more priority than the other.

If it captures the same thing, the later one wins. If that doesn't work, you need to make one of the queries more precise.
I actually meant that you create a PR at nvim-treesitter. But I can also merge your changes to my branch.

Before:

After:

Before:

After:

Do you think this is ready for review for the main repo? We could defer the operators for a separated PR as they are very convoluted.

Yes. I think it is ready if we leave the operators for a separate PR.

@mroavi are you still around? would you be interested in helping with the parser itself?

Hi @clason. I'm afraid I don't have time at the moment. I'll reach out whenever I manage to free up some time.


Alternative grammars

Is there a recommended way to install grammars not build by default with zee --build?

Thank you for the question!
Right now it's only possible to configure the available grammars by editing modes.ron and rebuilding the editor.
I am working on changing this in https://github.com/zee-editor/zee/pull/29 which makes grammars configurable at runtime (e.g. the tree sitter parsers and modes).
Longer term: a lot more things will be configurable, such as key bindings, themes and I hope eventually using rust/wasm plug-ins to extend zee itself.

See the configuration section in the README and the config.ron file for customising what grammars are used -- both git and local are supported.
Fixed by #29


Update analysis deps test Tags

Updating Testapp analysis test Tags with deps from maven repo with current output (change on Nov 10th 2023).
@pranavgaikwad This is update to current analysis test results, please could you confirm the change in issues is OK?

Already convered by https://github.com/konveyor/go-konveyor-tests/pull/55


Running on Mac: AttributeError: 'str' object has no attribute 'get'

Trying to run this on m1 max macbook
while running the example code, here's what I ran into
AttributeError: 'str' object has no attribute 'get'

Need a little more context. Can you provide the full stack trace?


Harden app against invalid requests

Currently if you attempt to load a user profile for a user that doesn't exist the server throws an exception resulting in a 500 error which isn't ideal. We should fix this (and other paths that take an id) to not throw an exception and return a 404.

Clean up the error page and we can call this a day


WIP: apps: Switch to using OSSL_STORE for loading keys, certs, ...

This makes all the format specifiers largely irrelevant, except for
the ENGINE format when a key is given as a key ID only.  However, with
the engine loader, it's possible to change this:
-engine {engineid} -key {keyid} -keyformat ENGINE

To this:
-key engine://{engineid}/{keyid}

We retain the ENGINE format for the sake of compatibility.  All other
input formats are simply ignored.  Note that output formats is a
different story.
Fixes #1963

Richard Levitte wrote:

This makes all the format specifiers largely irrelevant, except for
the ENGINE format when a key is given as a key ID only.  However, with
the engine loader, it's possible to change this:
 -engine {engineid} -key {keyid} -keyformat ENGINE

To this:
 -key engine://{engineid}/{keyid}

[SNIP]
Proposed modification is not store specific.
Let me quote in brief from PKIX-SSH manual
("http://securebox.termoneplus.com/man5/ssh_config.5.html") for option
IdentityFile.
(1) If file name starts with prefix ‘engine:’ instead from file identity
load is redirected to “loadable cryptographic module” (engine).
Name format is engine:{engineid}:{keyid} using syntax above.
(2) Prefix “store:” could be used if cryptographic library supports
ossl_store(7) functionality.
In such case name format is store:{uri}. Engine if applicable is encoded
in URI-scheme.
Second case is more generic. It is store related as it allows use of
URIs not supported by engine.
For instance based on store functionality PKIX-SSH could use directly as
identify key and certificates stored in PKCS#12 file (side effect).
Without store user should unpack (extract) PKCS#12 file into text file
(PEM format).
Otherwise there is no big difference for PKIX-SSH:
(1) ssh ... -i engine:e_nss:{keyid} vs
(2) ssh ... -i store:nss:{keyid}
Remark: in both cases engine require explicit configuration.
And one note more: {engineid}/{keyid} is not in store URI format.  You
know engine , you know keyid, but you don't know how to build store URI.
It is engine specific and is more one direction process: URI ->
{{engineid}, {keyid}, {extras...}}.
Regards,
Roumen Petrov

Ah, there's a précédent for a engine: scheme. Sure, I can use that instead.
Why someone has implemented a store: scheme is beyond me, though. Does that mean that if I want to express a file name in uri form, I would have to write store:file:///home/levitte/foo.pem? Why isn't file:///home/levitte/foo.pem enough? I cannot see why we should support such a contraption...

Richard Levitte wrote:

Ah, there's a précédent for a engine: scheme. Sure, I can use that instead.
Why someone has implemented a store: scheme is beyond me, though. Does that mean that if I want to express a file name in uri form, I would have to write store:file:///home/levitte/foo.pem?

So I use prefix:data, whre prefix is engine or store  just to avoid
failback case into code.
There is no reason OpenSSL to use such format.

Why isn't file:///home/levitte/foo.pem enough? I cannot see why we should support such a contraption...

Yep . Support of "Store URI" as input source should be enough . Perhaps
if store fails with "invalid scheme" then code could try to open file
(failback case).
Drawback of "Store URI" is that engine may not be loaded.
Work around is to keep "engine" argument.
Regards,
Roumen Petrov

Perhaps if store fails with "invalid scheme" then code could try to open file (failback case).

The current file loader does this already, i.e. it defaults to file: if no scheme is present.

Drawback of "Store URI" is that engine may not be loaded. Work around is to keep "engine" argument.

The proper workaround is to do what I do in this PR, i.e. define a engine: scheme loader.  See apps/app_engine_loader.c

Please do not start using an unregistered URI scheme: https://www.iana.org/assignments/uri-schemes/uri-schemes.xhtml

Code updated to use engine:{engineid}:{keyid}

Apparently, I hadn't completed what I said.  Now fixed, and tests added.

Finally, this builds and tests fine. I will fix the docs, then it will be time for a review

Richard Levitte wrote:

Apparently, I hadn't completed what I said.  Now fixed, and tests added.

Perhaps in next weeks :-( I could find time to continue discussion.
Regards,
Roumen

I'll echo the "please don't use an unregistered URI scheme" comment with its converse: please do support PKCS#11 URIs directly, without them having to be prefixed or mangled. The {engine}:… form mentioned above would have worked for that, given that the name of the engine in question would be pkcs11.
If you end up with a form that doesn't Just Work for RFC7512 PKCS#11 URIs, please special-case them to use the pkcs11 engine. Thanks.

If you create a proper OSSL_STORE loader that registers the scheme "pkcs11:", then you can use that scheme directly.
The "engine:" 'scheme' is an interim construct to allow access via the older ENGINE calls to access keys; ENGINE_load_private_key and ENGINE_load_public_key.  However, if the engine offers an OSSL_STORE loader, there is no reason whatsoever to use the "engine:" 'scheme'

Perfect. Thank you.

Needs a rebase

But seeing that PKIX-SSH uses the same scheme, and uses a different syntax to boot, that might be qualification enough to make a provisional registration after all. (I don't see it ever changing status to something more provisionalpermanent, btw)

Was the scheme ever registered as suggested here?

Was the scheme ever registered as suggested here?

No, but can certainly be done.  I have the impression that it's not very hard...

Needs a rebase

Getting at it now

The more I looked at the branch, the more I realised it's not quite ready for final review.  So I put it back in WIP.
Comments are still welcome!

This is still a WIP but placing a hold so it doesn't end up in OpenSSL 3.0 without a discussion and decision on the points already raised in the feedback.

Automated Ping: This issue is in a state where it requires action by @openssl/omc but the last update was 30 days ago

This is related to #12647 and likely further more recent PRs..

Isn't this change already implemented in master/3.0?

Isn't this change already implemented in master/3.0?

Almost, there were nuances that are not caught by @DDvO's changes.
I've left this unchanged for a while for the sake of priority, but intended to rebase this when I've got a chunk of time, to see what there is left.

OMC: There is no decision to be made here at this stage.


Issues with Forking Cloudflare ETH Endpoint

When forking https://cloudflare-eth.com, I get the error:
mike@darwin:~$ ganache-cli -f https://cloudflare-eth.com
Ganache CLI v6.11.1-alpha.1 (ganache-core: 2.13.0-alpha.2)
Error: The fork provider errored when checking net_version: Invalid JSON RPC response: "502 Bad Gateway"
    at web3.eth.net.getId (/home/mike/.nvm/versions/node/v10.20.1/lib/node_modules/ganache-cli/build/ganache-core.node.cli.js:55:2099379)
    at Object._fireError (/home/mike/.nvm/versions/node/v10.20.1/lib/node_modules/ganache-cli/build/ganache-core.node.cli.js:4:75935)
    at s (/home/mike/.nvm/versions/node/v10.20.1/lib/node_modules/ganache-cli/build/ganache-core.node.cli.js:4:120922)
    at a (/home/mike/.nvm/versions/node/v10.20.1/lib/node_modules/ganache-cli/build/ganache-core.node.cli.js:55:2114702)
    at Promise.all.then.e (/home/mike/.nvm/versions/node/v10.20.1/lib/node_modules/ganache-cli/build/ganache-core.node.cli.js:55:2099002)
    at process._tickCallback (internal/process/next_tick.js:68:7

The URL does respond to a CURL request:
$ curl -X POST --data '{"jsonrpc":"2.0","method":"net_version","params":[],"id":67}' https://cloudflare-eth.com
{"jsonrpc":"2.0","result":"1","id":67}

This is also seen in v2.12.1

I can't reproduce. Can you try https://github.com/trufflesuite/ganache-cli/releases/tag/v6.11.1-beta.1 ?

I can no longer reproduce on 6.11.1-alpha.1, 6.11.1-beta.1, or 6.11.0.
I'm guessing the issue was on Cloudflare's end and they fixed it. Closing this one! cc @rishanb


docs: add example org structures and new potential package

The goal of this PR is to add an example deployment of both a multi-org and a single org deployment of the Landing Zone v2 to demonstrate how the lego blocks should fit together.
When building out the single org environment in order to match up with the guidelines I had to create a new package for the creation of the multiple environment folders solutions/single-org-environments (placeholder name). I also made a change to the hierarchy deployment in the solutions folder to add a setter for environment that would be used to prepend to the folder names the environment the belong to environments/dev/hierarchy/audits/folder.yaml
Example:
apiVersion: resourcemanager.cnrm.cloud.google.com/v1beta1
kind: Folder
metadata: # kpt-merge: hierarchy/audits
  name: audits # kpt-set: ${environment}-audits
  namespace: hierarchy

Putting this as a draft for now as I believe some of the changes I made are made not necessary (folder name prepend) or how I assembled the pieces into either the multi-org or single org examples might need tweaking.
All in all the experience I had putting it together was pretty great!

@davelanglois-ssc could I get your eyes on this one, in particular the single org design? Not high priority but wanted to validate I have the example structure correct-ish.


No Duplicates

When pressing the keybind to load files, is there a way for the script not to load files that were already in the playlist? Hence, no duplicates.

Quick fix in bc139f779080469840c55504acbbf36a7c9e6427
It's naive and only looks at filenames. Duplicate filenames between directories is not handled correctly, because I'm not sure how that would be done correctly.

I went ahead and tried it out, and this is exactly what I wanted. Thank you so much.
Azmaan Kolondar - Chat @ Spike	[1k7z8g]
On May 21, 2022 at 13:19 GMT, Jonnie @.***> wrote:
Quick fix in bc139f7
It's naive and only looks at filenames. Duplicate filenames between directories is not handled correctly, because I'm not sure how that would be done correctly.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


Upgrade error 9.9.0: Could not load file or assembly 'System.Buffers' or one of its dependencies.

upgrade DNN 9.8.1 --> DNN 9.9.0
Could not load file or assembly 'System.Buffers, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)]
System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) +0
System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) +232
System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean forIntrospection) +113
System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) +23
System.Reflection.Assembly.Load(String assemblyString) +35
System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective) +49
Affected version

[ ] 10.00.00 alpha build
[ ] 09.09.00 release candidate
[ ] 09.08.01 latest supported release

Affected browser

[ ] Chrome
[ ] Firefox
[ ] Safari
[ ] Internet Explorer 11
[ ] Microsoft Edge (Classic)
[ ] Microsoft Edge Chromium

This error means that there was already a System.Buffers.dll in the bin/ directory with a binding redirect in the web.config, and the upgrade overwrote that file with a different version, so that its binding redirect in the web.config is for a different version than what's in the bin/ directory.
The simplest resolution is to replace System.Buffers.dll with the version that was there before.
Alternatively, you can update the binding redirect for System.Buffers.dll in the web.config to match the version from the install package.  That version it <IP_ADDRESS>, so the binding redirect should look like this:
      <dependentAssembly xmlns="urn:schemas-microsoft-com:asm.v1">
        <assemblyIdentity name="System.Buffers" publicKeyToken="cc7b13ffcd2ddd51" />
        <bindingRedirect oldVersion="<IP_ADDRESS>-32767.32767.32767.32767" newVersion="<IP_ADDRESS>" />
      </dependentAssembly>

thanks Brian! did the trick... now I have to find out why there already was a System.Buffers.dll in the bin... maybe a third party module?

thanks Brian! did the trick... now I have to find out why there already was a System.Buffers.dll in the bin... maybe a third party module?

Most likely, yes. I recently ran into a case where Vanjaro had installed it, but it might be another one in your case, obviously.
Also, please note that DNN 9.9 includes a newer version of that assembly, so you will need to change that bindingRedirect again.

Recently Mitch mentioned that this error should be in the past from 9.9.1 but I just tested and it is still the case.
Removing the lines made the upgrade continue as expected.
This was an install that included Vanjaro btw.

@Tychodewaard can we get some details so we can walk through your scenario?
Are you using "Vanjaro for DNN 1.0.4 RC"? What version of DNN are you coming from?
Are you saying that the install appears to work correctly, and there's only the persona bar error?  Or are you initially seeing the Yellow Screen of Death?
Thanks!

@bdukes Sure.
This DNN 9.8.1 install still had the Vanjaro beta2 (0.5.4)

First upgrade try: yellow screen of death, suggesting there are systembuffers issues
tried adjusting the reference to 4.6 but that did not do anything.
deleted the reference to systembuffers from the web.config: the upgrade went through
In the persona bar, the part 'sites' did not work anymore. A quick flash 'sites' and it disappeared again.
adding back your lines of reference to systembuffers made the 'sites' part reappear in the persona bar

🤦🏻♂ looks like I forgot to exclude System.Buffers from the upgrade package.  PR on its way

Thanks for spotting that @Tychodewaard and thanks for the quick fix @bdukes It will be included in either the next 9.9.1 RC or in 9.9.1 release.


Get default person_profiles value from /decide endpoint

Description
Description
Ee now have a way in /decide to say who should be able to use anonymous events as the default config mode: https://github.com/PostHog/posthog/pull/25662
[ ] iOS
[ ] Android
[ ] React Native
[ ] Flutter

Flutter uses the Android and iOS SDKs directly, so nothing to do here either


Docker Restart Policy

When I re-open docker desktop after it's been closed for a system restart or to increase battery life, it always tries to open a random combination of instances. Even the wordpress and sql instances seem randomly selected and are not limited to just one project.
When this happens and you try to start a project in your terminal with docker compose up, you get an error like:
Attaching to client-db-1, fwdus-wordpress-1
Error response from daemon: driver failed programming external connectivity on endpoint client-db-1 (***): Bind for <IP_ADDRESS>:3307 failed: port is already allocated

which persists until the other instances are stopped.
We traced this back to our restart: always config in docker-compose.yml.
Let's consider a different restart: policy to disable this behavior

To use restart policies, Docker provides the following options:
no: Containers won't restart automatically.
on-failure[:max-retries]: Restart the container if it exits with a non-zero exit code, and provide a maximum number of attempts for the Docker daemon to restart the container.
always: Always restart the container if it stops.
unless-stopped: Always restart the container unless it was stopped arbitrarily, or by the Docker daemon.

To test this, i'd start a docker container, then exit docker, and restart. With our current setup, I'd consistently get an outcome outcome where multiple conainers are running 1/2 (one wordpress, one db). This is not ideal and I'd rather a case where nothing open.
Ideally if somehow there is an error in a running container, it's able to self-restart.
Nice to have, trying to load up a new one forces the old ones to close.

on-failure. When you restart docker, the last docker container running successfully re-starts. Trying to load a different one doesn't break the current.
"no" When you restart docker, you have a clean slate, nothing running. Trying to load a different one doesn't break the current.

I don't have a strong opinion, but I'm leaning towards "no", as it gives you a clean docker on startup, and otherwise I don't believe our containers really fail and need to be restarted (and they're not meant for production where you might want that)


After using the daytona create command, http changed to https.

Hello, I set up Gitea locally and tried to create a workspace using Daytona, with the providers URL set to http://localhost:3000/. However, after executing the "daytona create" command, an error appears as shown in the image. It seems that the requested URL is changing from http to https, which is causing the access to fail. How can I resolve this issue?

Hi, thanks for submitting the issue. We pushed a fix regarding this in v0.41.0 but it's possible we missed something - can you please let me know the output of daytona -v to be sure?

Hi, thanks for submitting the issue. We pushed a fix regarding this in v0.41.0 but it's possible we missed something - can you please let me know the output of daytona -v to be sure?

OK. As shown in the figure below, the execution result shows that I'm using version v0.42.

Got it. It's possible we missed something during testing - we will release a fix on Tuesday and I will get back to you to confirm.

@TS35 We just did some testing and realized the issue lies in the need for the Git provider to be accessible to the container (Daytona workspace) cloning the repo.
That means you should expose the Gitea port 3000 using e.g. https://theboroer.github.io/localtunnel-www/, change the domain in the Gitea config to the new endpoint, rerun it and then daytona gp update to change the Base API URL to the newly generated URL to get this to work.
The http -> https fix will be released to the providers so this issue can be closed when that is done. Let me know if you have any questions

Closing this since the http->https fix was released


Clang fixes

This is a back-port PR of various clang-analyzer fixes.

FreeBSD build successful! See https://ci.trafficserver.apache.org/job/freebsd-github/1495/ for details.

Linux build successful! See https://ci.trafficserver.apache.org/job/linux-github/1388/ for details.

clang-analyzer build successful! See https://ci.trafficserver.apache.org/job/clang-analyzer-github/59/ for details.


deb instead of appimage

it installs appimage instead of .deb

? not sure I follow

oh sorry
on a debian based machine, the program chooses the appimage version while there is also a .deb version available in the release section

on a debian based machine, the program chooses the appimage version while there is also a .deb version available in the release section

this is somehow expected given that bin is not built to handle .deb files.

so bin is unable to install .Deb files? are you planning to add it any time soon?
-------- Original Message --------
On 12/18/24 6:32 AM, Marcos Nils  wrote:

on a debian based machine, the program chooses the appimage version while there is also a .deb version available in the release section

this is somehow expected given that bin is not built to handle .deb files.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

so bin is unable to install .Deb files? are you planning to add it any time soon?

yes, bin is unable to install binary files for the moment.There are no plans to add this feature soon since bin has been designed mostly for binary files. If there's enough demand, I could revisit in the future.


Arraization(?) is turning my Eloquent collections into strings (not arrays)

I'm passing in Eloquent Collections like so:
$engine->render('index/index', [
    'questions' => $questions,
);

If I var_export in the my controller class, the variable is set as an instance of Collection, but if I var_export within the template it's not an object, it's not an array even, but is a json_encoded string! I guess I could json_decode but is this the desired behaviour?
Also, how do I turn off Arraization for all templates? I might not wish to have this feature for now. Thanks

@martynbiz Arraization is needed for autoescape. You can turn it off by disabling autoescape.
Regarding Collection convert to JSON encoded string this is very weird, indeed.
Eloquent collections have a toArray method that is called by arraization routine to arrayize it.
Then, each element of the array is converted to array (if not scalar) using same method, which should never end up in  a JSON encoded string...


Saving the network-setting failed

Steps to reproduce:

On the settings page, edit the network-setting, remove the Physical NIC, then save
Edit it again, fill in the Physical NIC again, then save

Result:
Save failed, along with an error message
Operation cannot be fulfilled on settings.harvester.cattle.io "network-setting": the object has been modified; please apply your changes to the latest version and try again

duplicate of https://github.com/rancher/harvester/issues/594


Cloud thickness and transparency options.

Would be great to be able to make clouds more clear or less tall.

I added this to my to-do list.

I should probably keep this issue open anyways though.


🐛 [BUG] : Clear Error after it is shown.

Describe the bug
When the "User not found" button is pressed in the "Profile Visitors" section, a red error is displayed. This error persists and is shown every time the "Community" button is pressed afterwards.
To Reproduce
If you press User not found in Profile Visitors you getting red error every time you press Community button

Go to 'Profile Visitors'
Click on 'User not found'
Notice the red error
Click on 'Community' button
See error

Expected behavior
The error should be cleared after it is shown, and should not persist or be shown again when the "Community" button is pressed.
Screenshots
https://github.com/languageXchange/languageXchange/assets/3280475/6432fdca-03d0-48e0-900a-405bbca9b923

Additional context
Contributor @dev-vaganov
If you want speed up process of this issue, please send 🚀 as a reaction.

@dev-vaganov
https://github.com/languageXchange/languageXchange/assets/3280475/cb3d0b92-dc3a-4b8a-a83b-47273e8cb62e

It's fixed with RN version.


vcpkg should work on Alpine linux

Describe the bug
With the recent change (commit 5bdb9d60123df20c247a1654e6a1def51d6c5140) that incorporates a pre-built binary that is downloaded during the bootstrap process, the overall user experience is clunky/inconsistent when using vcpkg on Alpine linux
Environment

OS: Alpine linux
Arch: x86_64

To Reproduce
Steps to reproduce the behavior:

clone vcpkg
run bootstrap.sh, user sees...

Downloading vcpkg-muslc...

attempt to install any package. for example, zlib.

/src/vcpkg # ./vcpkg install zlib

Computing installation plan...
The following packages will be built and installed:
    zlib[core]:x64-linux -> 1.2.11#13
Detecting compiler hash for triplet x64-linux...
A suitable version of ninja was not found (required v1.10.2). Downloading portable ninja v1.10.2...
Downloading ninja...
  https://github.com/ninja-build/ninja/releases/download/v1.10.2/ninja-linux.zip -> /vcpkg/downloads/ninja-linux-1.10.2.zip
Extracting ninja...
sh: /vcpkg/downloads/tools/ninja-1.10.2-linux/ninja: not found

Failed to get version of /vcpkg/downloads/tools/ninja-1.10.2-linux/ninja

The problem is that the downloaded support tool cannot work in Alpine linux.
Expected behavior
The combo of now providing a pre-built vcpkg binary built for the musl-based system but downloading a tool binary that doesn't work is very confusing.  From a broad point of view, it would be nice to see one of the following behaviors:

all tools (vcpkg, ninja, etc) built to the same standard. thus avoiding any additional workaround. If a vcpkg is provided then the other tools should be usable, or
when vcpkg is downloaded, a warning message stating that the VCPKG_FORCE_SYSTEM_BINARIES is required, or
vcpkg attempts to find the system binaries automatically when on a musl-based system, or
in the worst case, just remove the musl-based pre-built binary and just let the user build from source. in this manner, you'd at least have a very consistent experience.

Seems the extract command failed.

The file is downloaded successfully.  Here's a comparison of the file that is downloaded vs the one that was installed using the native package manager
## view downloaded general properties
/vcpkg # ls -al /vcpkg/downloads/tools/ninja-1.10.2-linux/ninja
-rwxr-xr-x    1 root     root        228616 Nov 28  2020 /vcpkg/downloads/tools/ninja-1.10.2-linux/ninja

## use "file" command to view detailed properties
/vcpkg # file /vcpkg/downloads/tools/ninja-1.10.2-linux/ninja
/vcpkg/downloads/tools/ninja-1.10.2-linux/ninja: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=3c1def4659e39fa9a2870be5e78feea4a96e8bc3, stripped

## now view system installed ninja, which is symbolic link to samu
/vcpkg # file /usr/bin/samu
/usr/bin/samu: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-musl-x86_64.so.1, stripped

Note the downloaded version shows a different interpreter than the system installed file.

Related to https://github.com/microsoft/vcpkg/issues/21142, another issue which related to https://github.com/microsoft/vcpkg/commit/5bdb9d60123df20c247a1654e6a1def51d6c5140.
cc @BillyONeal

With the recent change (commit 5bdb9d6) that incorporates a pre-built binary that is downloaded during the bootstrap process, the overall user experience is clunky/inconsistent when using vcpkg on Alpine linux

To be clear, the status quo before was "bootstrap fails on Alpine because it tries to download cmake for glibc which can't run on Alpine, and also vcpkg looks for a nonexistent linux-x64-muslc triplet", and the behavior now is "bootstrap succeeds, but then trying to do anything useful fails because vcpkg tries to download a version of cmake unavailable on Alpine". In both cases Alpine is broken, but it blows up somewhat later.
I generated a muslc version so that we could target Alpine because it was my intent to make Alpine work as part of those changes, but lack of available dependencies which worked with the existing catalog stopped it.
As soon as a version of cmake new enough to use is available from apk, that vcpkg-muslc should start to "just work".

all tools (vcpkg, ninja, etc) built to the same standard. thus avoiding any additional workaround. If a vcpkg is provided then the other tools should be usable, or

There is nothing we can do about this because we do not control those dependencies. I think we need to consider Alpine next time we change the required CMake version, but for now I think our hands are kinda tied, since reducing the CMake version would be a breaking change to the existing catalog.

when vcpkg is downloaded, a warning message stating that the VCPKG_FORCE_SYSTEM_BINARIES is required, or

I believe we do that: https://github.com/microsoft/vcpkg/blob/66c39e113a348a6ae80419fae5a629b951b00f1a/scripts/bootstrap.sh#L70-L82

vcpkg attempts to find the system binaries automatically when on a musl-based system, or

It already does do that; the problem is that the version of CMake provided on Alpine is too old. vcpkg runs the command "cmake", checks the version, and only tries to download a copy if the provided version is not recent enough. VCPKG_FORCE_SYSTEM_BINARIES skips the version check, but last time I tried this it immediately blew up since the version requirement is also enforced by the scripts tree:
https://github.com/microsoft/vcpkg/blob/66c39e113a348a6ae80419fae5a629b951b00f1a/scripts/ports.cmake#L1

in the worst case, just remove the musl-based pre-built binary and just let the user build from source. in this manner, you'd at least have a very consistent experience.

That gives up compiler consistency for the team maintaining the tool which was a major design goal of offering binaries, and since it doesn't make anything actually work, I don't think it's a useful thing to do.

To be clear, I would really like Alpine to just work out of the box. I think the changes needed to vcpkg to get there are relatively minor, although I ran out of time to figure out all the implications as part of the binaries project. We absolutely are going to consider what is available in the most recent Alpine before changing our required CMake versions again, so hopefully they "catch up" soon and things start to just work. Until then your only options are really to build a more recent cmake from source.
I think there's also a potential feature here where we suggest an apk command to install dependencies rather than trying to download if we are unable to provide that seamlessness.

Thanks for the taking the time to elaborate.
There is a "timing" issue present with bootstrap code mentioned in item 2. If all the prerequisites are in place, the bootstrap doesn't present the message about requiring VCPKG_FORCE_SYSTEM_BINARIES. For example...
/vcpkg # ./bootstrap-vcpkg.sh
Downloading vcpkg-muslc...
Telemetry
---------
vcpkg collects usage data in order to help us improve your experience.
The data collected by Microsoft is anonymous.
You can opt-out of telemetry by re-running the bootstrap-vcpkg script with -disableMetrics,
passing --disable-metrics to vcpkg on the command line,
or by setting the VCPKG_DISABLE_METRICS environment variable.

Read more about vcpkg telemetry at docs/about/privacy.md

In my test image, I had the latest version of cmake as provided with...

apk add --no-cache cmake --repository=http://dl-cdn.alpinelinux.org/alpine/edge/main

but I had forgotten to set the environment variable. When the new 5bdb9d60123df20c247a1654e6a1def51d6c5140 bootstrap ran, it pulled down the pre-built and didn't warn. If the alpine environment is a special case (akin to ARM), it would be nice if vcpkg would just tell you. For instance, if running on an ARM system, you can't run vcpkg w/o seeing the following:

Environment variable VCPKG_FORCE_SYSTEM_BINARIES must be set on arm, s390x, and ppc64le platforms.

Perhaps worth considering adding the musl platform to that list?
I can get vcpkg to build the zlib library if the following is done.

install cmake from the edge repo first (see above)
install remaining packages (build-base curl git g++ make ninja pkgconfig tar unzip zip)
clone, run bootstrap
set VCPKG_FORCE_SYSTEM_BINARIES
install zlib

Unit tests for our project work just fine. The latest improvements are definitely getting us closer to fully utilizing vcpkg on alpine.

Hmm, that didn't work from
RUN apk add --no-cache build-base zip unzip curl git && \
    apk add --no-cache --repository="http://dl-cdn.alpinelinux.org/alpine/edge/main" cmake ninja

I get:
fetch http://dl-cdn.alpinelinux.org/alpine/edge/main/x86_64/APKINDEX.tar.gz
fetch https://dl-cdn.alpinelinux.org/alpine/v3.15/main/x86_64/APKINDEX.tar.gz
fetch https://dl-cdn.alpinelinux.org/alpine/v3.15/community/x86_64/APKINDEX.tar.gz
ERROR: unable to select packages:
  ninja (virtual):
    provided by: samurai
    required by: world[ninja]

…ditto if I put ninja on the first line (error only occurs when it tries to install CMake on the second). Installing CMake not from edge works, but leaves me with:
CMake Error at /opt/vcpkg/scripts/buildsystems/vcpkg.cmake:836 (message):
  vcpkg install failed.  See logs for more information:
  /cauthflow/build/vcpkg-manifest-install.log
Call Stack (most recent call first):
  /usr/share/cmake/Modules/CMakeDetermineSystem.cmake:124 (include)
  CMakeLists.txt:2 (project)

CMake Error: CMake was unable to find a build program corresponding to "Unix Makefiles".  CMAKE_MAKE_PROGRAM is not set.  You probably need to select a different build tool.
CMake Error: CMAKE_C_COMPILER not set, after EnableLanguage

Trying again, this time with cmake not from apk but from:
ADD "https://github.com/Kitware/CMake/releases/download/v3.23.0-rc1/cmake-3.23.0-rc1-linux-x86_64.sh" "/down/cmake.sh"

RUN sh /down/cmake.sh --skip-license --prefix='/usr/local'

But that didn't work either.
Is there an updated guide for Feb 2022?

@SamuelMarks, in the steps I mentioned above, notice that the edge-based cmake is installed first. Then everything else second.  If you flip that order, you will get the errors you included in your reply.
Our docker scripts are basically setup as...

We use both make-based and cmake-based configurations. The cmake call is pretty straightforward.
cmake -DCMAKE_BUILD_TYPE=release -DCMAKE_TOOLCHAIN_FILE=${vcpkgFolder}/scripts/buildsystems/vcpkg.cmake -B build/release -S .

If the edge repo call is the first action, then I think you will have better luck.

As of Jan 2024, vcpkg needs a newer version of ninja and tries to install it. And it was the case with cmake, the installed ninja can not run on Alpine.
To make things slightly more complex, Alpine changed the name of the ninja package to ninja-build and changed the installation location.
Here is an updated Dockerfile
FROM alpine:edge as devconfig
RUN apk add --no-cache cmake --repository=http://dl-cdn.alpinelinux.org/alpine/edge/main

#vcpkg needs at least cmake version 3.27.1, which is not yet in regular alpine  RUN apk add --no-cache cmake
RUN apk update && \
    apk add --no-cache \
      bash \
      build-base \
      curl \
      git \
      g++ \
      make \
      ninja-build \
      pkgconfig \
      sudo \
      unzip \
      zip \
      python3

RUN ln -s /usr/lib/ninja-build/bin/ninja /usr/bin/ninja

There is a package, ninja-is-really-ninja , when you install this, ninja's name and location will be as expected


Fix for error showing on dashboard

Description
This problem occurs when logged in and the dashboard is open, for some reason the snapshot.data received from the call to topBooks in file dashboard.dart is null.
So when null is passed to BookList widget as the second argument, the following error shows up as on the screenshot below

due to calling the shuffle method on null and length method on null in the book_list.dart file
After doing the changes, Here is how it looks and functions when it is null

I understand that there could be improvements to this, like showing a message which says "No new books to discover"
If there are any modifications or suggestions to this, I would be glad to add them.
Type of change

[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 not work as expected)

Checklist:

[x] My code follows the code of conduct of this project
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas

[ ] My changes generate no new warnings

@RandyKdev it's already described in #38.
Please follow the README guidelines properly.
I'll review the PR once you get the issue assigned.

Ok, thanks. I didn't know there was issue like that.
Thanks.

I have updated this PR to reflect recent commits to main.

I am closing this because I discovered that I didn't create my own branch before making the changes.


Modify skip_reset_qubits to apply DD on all qubits when False

Clone of https://github.com/Qiskit/qiskit-ibm-provider/pull/776 (see comments)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 3 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.009%) to 81.016%

Totals

Change from base Build<PHONE_NUMBER>:
0.009%

Covered Lines:
5023

Relevant Lines:
6200

💛  - Coveralls


Make contact person optional in Add Organization form

It should be simple to add an organization to APIKA. It is possible that it is unclear who will be the contact person for the organization while the organization is being added. The fields related to contact person should not be mandatory on the form.
Definition of done

[ ] User can save the Add Organization form without giving  contact information.

Interested

Closing the issue. Any fields related to contact person are optional.


Add a LED API

We also need an API to control the LED (because we need it).
From what I can gather from the various devices I encountered, some have very tunable LED (like the G303), others have basic functionalities (like the Etekcity). I think the common denominator is:

export, per profile, one LED object per LED on the device (Roccat Konw XTD has 4, G303 has 2 and pretty much the rest 1)
allow to change the LED color if possible (we need a capability for that)
allow to apply an effect on the color (or not -> only seen in the Roccat, maybe in the G303)
allow to turn to set the light effect:

on
off
hearbit
breathing
pulsing

We might not expose that many effects (breathing, heartbit, etc). The most important ones are IMO ON/OFF and the set_color so we can assign a color per profile.

I added LED support for g502 and g900 devices  #113
can you please review it

Apologies for the delay in the review process.
Before starting the review (and asking for changes if need be), I wanted to coordinate with @whot given that your pull request contains both internal changes in the hidpp20 driver and public API changes. I have done that just now, and so we can move on to the next part of the process, doing the actual review.
However, as you must know, the public API changes are the most difficult ones because we need to be spot on. We can't change the API/ABI at each commit, so we need to be careful when we amend the public API. Don't be afraid if we ask for changes. Just keep pushing :)
Anyway, thanks a lot for your pull request. I really appreciate the work done, especially for caring about tests. Expect a review of the pull request in the coming days, and if it doesn't come up, don't hesitate to send (again) a gentle ping :)

Thanks for taking the time and reviewing my PR, i will gladly modify the PR to suite your standards.

I pushed changes the PR #113
its still big change, and i am not sure how to break it further, open for suggestions.

#129 resolves this issue

#129


Adding first and second properties to iteration_proxy_internal

This PR fixes #350 by adding property-like members to the iterator_proxy_internal class.
The fix proposed in that issue looks as if you pay for it even if you don't use .first or .second (at least the .first shows a copy of a string each time the iterator is incremented). That cost shouldn't have to be payed, but we don't have to sacrifice the interface that we want.
This solution provides the .first and .second interface as outlined in the issue, but shouldn't cost anything, and is likely inlined out of existence after compilation.

Here's the test that I used:
#include <json.hpp>
#include <iostream>

using namespace std;
using namespace nlohmann;

int main()
{
  json j = {{"A", 1}, {"B", 2}};

  for (auto i : json::iterator_wrapper(j))
  {
    auto x = i.first; // x = "A", x = "B"
    auto y = i.second; // y = 1, y = 2

    cout << x << ", " << y << endl;
  }
}

Here's the output:
"A", 1
"B", 2

This is a nice solution! Thanks!

Coverage increased (+0.0004%) to 99.722% when pulling 6a656ed375d96b64ddbb0d7d364fb03627f9b3ac on Type1J:develop_feature_first_second into 2afbd33472a2b64ccf57767e90427bba6b469be2 on nlohmann:develop.

Unfortunately, the code does not work for me. If you look into the test suite in tests/src/unit-iterator_wrapper.cpp, replacing calls to key() withfirst and value() with second yields compilation errors.
It would be great if you could have a look at this.

I'm using MSVC 2017. What compiler failed for you?

clang version 5.0.0 (trunk 292523) (llvm/trunk 292718) - in any case, it would be great to have unit tests - I should not have merged the code without.

I'll look into it, and I'll see about adding the unit tests as well.

That would be great!


Gemma2 Support

⚠ Please check that this feature request hasn't been suggested before.

[X] I searched previous Ideas in Discussions didn't find any similar feature requests.
[X] I searched previous Issues didn't find any similar feature requests.

🔖 Feature description
With the release of Google's new models Gemma2 9B and Gemma2 27B, it would be very useful to have those models incorporate to the training framework of Axolotl.
✔ Solution
Integrate the new model by providing configuration scripts and incorporating the Gemma2 template.
❓ Alternatives
No response
📝 Additional Context
No response
Acknowledgements

[X] My issue title is concise, descriptive, and in title casing.
[X] I have searched the existing issues to make sure this feature has not been requested yet.
[X] I have provided enough information for the maintainers to understand and evaluate this request.

Seems to be implemented now.


"Timed out sending input to device" if I add the "aaa group server tacacs+" config

Hi all. The issue is: if I add this config by scrapli telnet, it fails with timeout issue.
Here is the code:
import logging
from scrapli.driver.core import IOSXEDriver

logging.basicConfig(
    level=logging.DEBUG,
    format="%(name)s %(asctime)s [%(levelname)s] %(message)s",
    datefmt="%Y-%m-%d %H:%M:%S",
    handlers=[logging.FileHandler("scapli_debug.log"),logging.StreamHandler()]
)

logging.getLogger('transport').propagate = False

CONFIGS_1 = [
    'aaa group server tacacs+ Hello',
    'server name srv1',
]

cisco_s = {'host': 'X.X.X.X', 'auth_username': 'cisco', 'auth_password': 'cisco', 'auth_secondary':'cisco', 'transport': 'telnet', 'port': 23}
conn = IOSXEDriver(**cisco_s)
conn.open()
response = conn.send_configs(CONFIGS_1)
conn.close()

The fail traceback is:
Traceback (most recent call last):   File "scrapli_debug.py", line 28, in <module>     response = conn.send_configs(CONFIGS_1)   File "/usr/local/lib/python3.8/dist-packages/scrapli/driver/network_driver.py", line 688, in send_configs     response = super().send_command(   File "/usr/local/lib/python3.8/dist-packages/scrapli/driver/generic_driver.py", line 90, in send_command     raw_response, processed_response = self.channel.send_input(   File "/usr/local/lib/python3.8/dist-packages/scrapli/channel/channel.py", line 268, in send_input     raw_result, processed_result = self._send_input(   File "/usr/local/lib/python3.8/dist-packages/scrapli/decorators.py", line 77, in timeout_wrapper     raise TimeoutError(message) TimeoutError: Timed out sending input to device.
Screenshots

OS (please complete the following information):

OS: Ubuntu 20
scrapli version: 2020.5.9

Additional context
Log

file:
scrapli_debug.log

Hi @artyomovs
Thanks for submitting this issue!
I was able to reproduce your issue and it looks like this occurs because we currently do not allow for matching for the + character in config mode.
The fix for this is of course to just add that + character in the pattern match. You can check out this issue from @IDQDD here -- they have a similar issue and have patched it temporarily by passing in modified privilege levels to scrapli.
I think the privilege pattern will ultimately get updated to look like this below:
    "configuration": (
        PrivilegeLevel(
            pattern=r"^[a-z0-9.\-_@/:]{1,63}\(conf[a-z0-9.\-@/:\+]{0,32}\)#$",
            name="configuration",
            previous_priv="privilege_exec",
            deescalate="end",
            escalate="configure terminal",
            escalate_auth=False,
            escalate_prompt="",
        )
    ),

This pattern will fix this issue as well as @IDQDD's issue.
To make sure we dont run into this again I'm going to add a few tests to ensure that we are matching all the types of base prompts -- i.e. "normal" exec/privilege-exec/config as well as more special prompt pattens like this tacacs+ mode or ssh key config mode.
This should be in develop by this weekend, I'll update this issue when I get it pushed up. I'm also planning/hoping on making a release to pypi this weekend, so hopefully this will make it up there this weekend as well!
Thanks again for submitting this!
Carl

Hi again @artyomovs
The fix for this has now been pushed to master and released. I'll go ahead and close this now, but feel free to reopen if for some reason the fix does not work.
Thanks again for reporting this!
Carl

Hi again @artyomovs
The fix for this has now been pushed to master and released. I'll go ahead and close this now, but feel free to reopen if for some reason the fix does not work.
Thanks again for reporting this!
Carl

Thank you very much:)


[Website] adjust website structure

Description
adjust website structure to reflect the new modules and deprecation
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[x] Changes are complete (i.e. I finished coding on this PR)
[ ] Code is well-documented:
[x] To the best of my knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[x] adjust website structure to promote np/npx, and deprecate ndarray/symbol and other legacy modules.

Preview link: http://ec2-34-219-134-42.us-west-2.compute.amazonaws.com/api/python/docs/tutorials/

@ys2843 many thanks! @sxjscience @eric-haibin-lin @leezu @szhengac please take a look and see if the changes look good to you.

the caffe2mxnet page leads to 404:

@eric-haibin-lin since it's deprecated, I will remove it

@mxnet-bot run ci [unix-cpu, windows-gpu]

Here is the updated preview: http://ec2-18-236-134-13.us-west-2.compute.amazonaws.com/api/python/docs/tutorials/index.html

Looks like there are still many problems in the API cards. I will work on this in the next day or two.

issues found so far:
in http://ec2-18-236-134-13.us-west-2.compute.amazonaws.com/api/python/docs/tutorials/packages/gluon/index.html
ndarray card: http://ec2-18-236-134-13.us-west-2.compute.amazonaws.com/api/python/docs/tutorials/packages/ndarray/index.html
normalization block: http://ec2-18-236-134-13.us-west-2.compute.amazonaws.com/api/python/docs/tutorials/packages/gluon/data/normalization/normalization.html
naming no longer relevant: http://ec2-18-236-134-13.us-west-2.compute.amazonaws.com/api/python/docs/tutorials/packages/gluon/blocks/naming.html
custom loss: http://ec2-18-236-134-13.us-west-2.compute.amazonaws.com/api/python/docs/tutorials/packages/gluon/loss/custom-loss.md
gotchas: http://ec2-18-236-134-13.us-west-2.compute.amazonaws.com/api/python/docs/tutorials/packages/ndarray/gotchas_numpy_in_mxnet.md
in http://ec2-18-236-134-13.us-west-2.compute.amazonaws.com/api/python/docs/tutorials/packages/gluon/image/index.html
image recognition with pretrained models: http://ec2-18-236-134-13.us-west-2.compute.amazonaws.com/api/python/docs/tutorials/packages/gluon/image/pre-trained_models.html
in http://ec2-18-236-134-13.us-west-2.compute.amazonaws.com/api/python/docs/tutorials/performance/index.html
TRT: http://ec2-18-236-134-13.us-west-2.compute.amazonaws.com/api/python/docs/tutorials/performance/backend/tensorrt/tensorrt.html
data parallel: http://ec2-18-236-134-13.us-west-2.compute.amazonaws.com/api/faq/multi_device
in http://ec2-18-236-134-13.us-west-2.compute.amazonaws.com/api/python/docs/tutorials/deploy/index.html
text color orange
cpp inference: http://ec2-18-236-134-13.us-west-2.compute.amazonaws.com/api/python/docs/tutorials/deploy/inference/cpp.html
cloud weird format: http://ec2-18-236-134-13.us-west-2.compute.amazonaws.com/api/python/docs/tutorials/deploy/run-on-aws/use_ec2.html

also most of the API docs are missing as the autodoc doesn't seem to work properly.

Did you specifically request my review? If yes, let me know when it's ready to be reviewed

@marcoabreu I think you were looped in through code owner as I'm updating the CI installation to fix the website build problem
OSError: libopencv_imgcodecs.so.3.2: cannot open shared object file: No such file or directory

Preview link: ec2-34-219-134-42.us-west-2.compute.amazonaws.com

@sza
Thanks. I have saw http://ec2-34-219-134-42.us-west-2.compute.amazonaws.com/versions/1.6/api/python/docs/tutorials/getting-started/to-mxnet/pytorch.html#Variable-wrapper-vs-autograd-scope
I will close #18943

@StevenJokes no worries!


Creating/Opening A Database With Path

Right now I'm struggling with opening a database that doesn't end with .kv. I propose to create a new function like
pub fn open_with_path<S: AsRef<str>>(path_to_kv: PathBuf) -> Result<Self>

For example, path to KV can be /home/user/path/dontcare/keyvaluestore.my. This will result in a more generic way of opening the kv store and easier way to pass the path argument from a file selector (for example).

Hey, you immediately closed this issue. Is this something you don't want to see anymore? Or have you found a solution already?

Hello, sorry for the inconvenience, I was trying to use microkv for my personal project but I find it not suitable for my usecase because microkv is loading the entire store to memory (?).
But regarding this issue, I think my suggestion would be a nice to have. Simply because of its embedded nature, I would like to add some personal touch to the file extension of the store.

No problem at all :)
Yes, you are right. Microkv is like a glorified dictionary that can be stored securely in a file. But whenever you want to access the data, you must load the complete file (and thus the complete dictionary into memory).
Thank you for your suggestion.


feat(Transfer): adds resource support for GCP collections

transfer.endpoint.create can be used to create guest collections on a Globus Connect Personal mapped collection
transfer.endpoint.update can be used to update attributes on a mapped or guest collection

Depends on https://github.com/globusonline/webapp/pull/4295, a subsequent publish of @globus/types, and an update to package.json to pull in the new type.


Colors - Dynamic selection

PR Description 📜
Added Colour selection for players.
Now players can choose their desired colours
It has validation that will prevent user selecting same colour for 2 or more players.
It has advance UI features along back button to navigate back to home screen.
Fixes #547

Mark the task you have completed ✅

[x] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[x] I have added screenshot for review.

## Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗

@ayush-t02 I request you to give a Level 3 label to this PR as I have to work a lot in it. I have also added validation so that no one can choose same colours. Also, with addition of scoreboard, I have to update that as well with the colour rendering. It would be helpful if you add Level 3 label. Thanks!


Updated README with Support Clause

Updated the support clause to remove google groups in favor of slack

Thanks @kacole2


syntax error

File "dmm_util.py", line 93
    match len(name):
            ^
SyntaxError: invalid syntax

What python version do you use?
3.10+ is needed.
I use 3.10.2

3.6.8 :/ - it may be a good idea to add some initial check and message

I bet many electronics engines, even they have the latest and greatest Python version, do not know how to import "serial module".
Probably after 5 minutes of Googling most most of will them will give up. I am still Googling.

I have changed the README.
It's not possible to add check, syntax one is done first.
It would be necessary to add a wrapper.
It's much simpler this way

I did not mean syntax check but Python runtime version check.

I have well understood, but this check is not possible.
Python interpreter checks syntax first.  It runs the script, and thus the test in a second time.
It never gets to that stage.

I see.


X370 Gaming Pro Carbon Wrong Lights

The X370 Gaming Pro Carbon Wrong Lights has two type of lights;

The RGBs
Function lights, which are only in red and lightup when there is a connected RAM module, PCIe card, etc.

But the software interracts with the function lights rather then the RGBs...

The motherboard probably uses a different chip for controlling the RGBs, so unfortunately currently won't be supported. But it's worth a look when I can (and I can't promise it will be any time soon, sorry).

Alright, let me know if you need something, I’ve briefly looked at the code but it’s way to complex for my student knowledge. 🤣

At this moment, this motherboard won't be supported.


Pre-fill Administrator in workshop event

Currently, several of the fields from the Centrally-Organised WRF are being automatically pre-filled in the event when accepting the form.  Would like for the "administrator" to be pre-filled with LC, SWC, or DC based on what was selected on the WRF.

@sheraaronhurt please check if this is still valid feature request. I remember I worked on some advancements in prefilling that form, not sure if that was one of them.

@pbanaszkiewicz  this update didn't happen. This is still a valid feature request.

Yes, in creating a new event from a workshop request/submission, we would want Administrator to auto-populate based on the lesson program of the curricula specified in the workshop request form.

The lessons aren't currently linked to Administrator, so this will require database changes and some migration, and then some changes in form logic.

Just wanted to get some clarity on this one since I'm not as familiar with the website yet.

Yes, in creating a new event from a workshop request/submission, we would want Administrator to auto-populate based on the lesson program of the curricula specified in the workshop request form.

@maneesha I'm not sure where on the website you can create a new event from a workshop. Could you suggest a url or a screenshot that would help me?

@lauryndbrown I can help you with that.
We store Workshop Requests, Workshop Inquiries and Self-Organised Submissions. All of these come from the forms and are often addressed as WRF - Workshop Request Forms.
You can browse existing entries in /requests/workshop_requests/ (for Workshop Requests) and /requests/selforganised_submissions/ (for Self-Organised Submissions). The links to these pages are inside "Requests" dropdown in top-navbar.
Once you open a single request/submission, you'll see a button down below the details table:

It allows you to change state to accepted, or additionally add new event based on the request's data:

This is how the new event from a workshop submission looks like:

To follow up on Piotr's examples above, here's how we'd want to assign Administrator:
If it's a self-organized submission form: Administrator = self organized.
If it's teaching Data Carpentry, Library Carpentry, or Software Carpentry curriculum, then that should indicate the Administrator.
Thank you - Let me know if you have any other questions!

This is a few years old but my last comment is still accurate with the note that this only applies to events created from a workshop request form.  All other events will have this information filled in manually.
@elichad  I think this should be ready to work on now.

related to #2362


Authentication: Email Notification UI

new page alert on the Authentication page
Develop the forget password page UI appropriately
Ensure they are responsive and follow the responsive design on the Figma
Implement images properly
Follow the color guide and the appropriate colors

I am working on this issue!

done


Varying Closure Keyword Parameters Not Being Correctly Evaluated During Batched Execution

Problem
It appears that closure parameters declared with CLOSURE_*_KEYPARAM don't work correctly with varying inputs in batched execution.
I've now got a pretty simple repro, and I've tested with the recently released <IP_ADDRESS>, so I think this is probably a legit issue:
badBatch.osl
shader badBatch()
{
    Ci = diffuse( N, "label", format( "%f", u ) );
    printf( " Ci = %s", Ci );
}

Testing
> oslc badBatch.osl && testshade -g 2 1 badBatch
Ci = (1, 1, 1) * diffuse ((0, 0, 1), "label", "0.000000") Ci = (1, 1, 1) * diffuse ((0, 0, 1), "label", "1.000000")

> oslc badBatch.osl && testshade -batched -g 2 1 badBatch
Ci = (1, 1, 1) * diffuse ((0, 0, 1), "label", "0.000000") Ci = (1, 1, 1) * diffuse ((0, 0, 1), "label", "0.000000")

Passing the -batched flag causing the second shading point to incorrectly get the same value for "label" as the first shading point.
Versions

OSL branch/version:  <IP_ADDRESS> ( first noticed in <IP_ADDRESS> )
OS: CentOS 7.9
C++ compiler: gcc-9.3.1
LLVM version: 13.0.0
OIIO version: <IP_ADDRESS>

I believe this was closed by #1620


Can wt auto change current path to the opening folder ?

Description of the new feature/enhancement
Input wt to the win file explorer address bar . Then wt can auto change path to the folder .

Proposed technical implementation details (optional)
For example, In windows, I open the file folder , and change to e:\foo .  Then I input cmd to the explorer address bar , the cmd window will be open , and the path is e:\foo.
Can wt support the same function ?

yep, it already does. However, you need to type
wt -d .

to specifically tell the Terminal the working directory (-d) is the current directory of explorer (.)
For more details on wt.exe's commandline args, see Using command line arguments for Windows Terminal


SDO-Hearing-Screen-Changes

Before creating a pull request make sure that:

[ ] commit messages are meaningful and follow good commit message guidelines
[ ] README and other documentation has been updated / added (if needed)
[ ] tests have been updated / new tests has been added (if needed)
[ ] the enable_keep_helm label has been added, if the helm release should be persisted after a successful build

Please remove this line and everything above and fill the following sections:
JIRA link (if applicable)
Change description
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

Will open another new pull request


Add repository to Cargo.toml

Saving future me from a extra Google hop.

Went ahead and published a new version so the link is updated on crates.io too (:


Use icons to represent weather conditions.

User Story
As a user,
I want to see weather icons representing the current weather and forecast,
So that I can quickly understand the weather conditions.
Acceptance Criteria
GIVEN the weather data fetched from the API,
WHEN the data includes weather conditions,
THEN the corresponding weather icons are displayed on the webpage.
AND the icons are accurate and visually representative of the weather conditions.

For future reference.


FE-222: fix search & index views

Scope & Purpose

Allow additional properties in arangosearch

Allow empty fields when includeAllFields is true in inverted index

Fix breadcrumbs in arangosearch

[x] :hankey: Bugfix

Checklist

[x] Tests

[x] Manually tested

[x] :book: CHANGELOG entry made

Related Information

[x] GitHub issue / Jira ticket: https://arangodb.atlassian.net/jira/software/c/projects/FE/issues/FE-222

[ ] https://jenkins01.arangodb.biz/job/arangodb-ANY-jslint/28314/