Color Picker: Finalize Color Picker API

There are two APIs we need to finalize: Monaco and VSCode.
Both APIs are identical except in terms of color formatters: VSCode supports a declarative format for color formats, while Monaco supports more generic function-style formatters.
Discussion Points

[ ] Color value ranges - We have a very peculiar Color class internally, which has predefined value ranges for color components. RGB is stored in ranges of [0-255], for example. I am more in favor of using floating point [0-1] ranges for all color coordinates in the API. This is what is currently implemented. We just need consensus on the approach.
[ ] Color.fromHex - I suggest we keep this in proposed state until #32295 is fixed, at which point it can be completely removed.
[ ] Color Insertion - The current API works great with colors which are already in the document. Both the API and the color picker widget don't work really well when the user wants to insert a new color. This needs thought. I think we can surface this as a feature request so we can get the API out the door asap.

Color Picker should be appeared after clicking on rectangle color symbol (box) like chrome. It is appearing with hovered action now.

@joaomoreno considering the inline box pr is still under review, I'd like to share some thoughts of API finalization of both VSCode and Monaco.
VSCode

Color Ranges. Right now extTypes is already using float numbers, IMHO it's already in a good shape.
As we are suggesting users to use Float number instead of more preferred integer, I'd like to keep fromHex, fromHSLA, etc in the exposed Color class for now, which can help generate correct rgba value.
Code insertion is still not there, but it's not a blocker.

I would expect VSCode API to be like what's in https://github.com/Microsoft/vscode/pull/32864 .
Monaco
Exposing this feature to Monaco requires more work, in order to get a consistent API declaration. Currently the API is like
export interface IColorFormatter {
	readonly supportsTransparency: boolean;
	format(color: Color): string;
}

export interface IColorRange {
	range: IRange;
	color: IColor;
	formatters: IColorFormatter[];
}
export interface IColor {
	readonly red: number;
	readonly green: number;
	readonly blue: number;
	readonly alpha: number;
}

It's a bit confusing as the relationship between IColor and Color is not Interface and Implementation. IColor is more likely RGBA. So we can probably change ICodeRange to
#1
export interface IColorFormatter {
	readonly supportsTransparency: boolean;
	format(color: Color): string;
}

export interface IColorRange {
	range: IRange;
	color: RGBA;
	formatters: IColorFormatter[];
}

or even better we use Color directly.
#2
export interface IColorFormatter {
	readonly supportsTransparency: boolean;
	format(color: Color): string;
}

export interface IColorRange {
	range: IRange;
	color: Color;
	formatters: IColorFormatter[];
}

#3
Another way is changing the signature of IColorFormatter to
export interface IColorFormatter {
	readonly supportsTransparency: boolean;
	format(color: IColor): string;
}

and cast IColor to Color internally, in which way Monaco extensions have no access to Color and build their own formatters on top of IColor (which is RGBA actually).
#3 is more appealing. I'd like to hear your voice on this @joaomoreno

fyi - before this all becomes API we need to discuss the color format. it looks like a pretty big stunt and if we want something like that we should at least pick a syntax that is closer to what text mate snippet its variables and transforms look like

It's a bit confusing as the relationship between IColor and Color is not Interface and Implementation.

Yeah, IColorFormatter should work in terms of IColor. That was an oversight.

Another way is drop IColor and use RGBA directly

Definitely interesting, but not yet convinced.

@jrieken based on my understanding of TextMate snippet, we can do slight changes to current format to make it closer to TextMate snippet and share those concepts.
Our current format rgb({red:d[0-255]}, {green:d[0-255]}, {blue:d[0-255]}) is declarative, red, green and blue are Variables and we'll replace these placeholders with corresponding channel. While a typical Variable in TextMate snippet is like \textbf{${TM_SELECTED_TEXT:no text was selected}}.
Their similarities:

surrounded by curly braces {}
variable name and value/format are separated by :

Differencies

TextMate variables are all upper case.
If we use TM variable directly, we don't wrap the name with {} otherwise when we need to set its default value and do formatting, wrap it with {}. Our color format is always surrounded by {}
We don't use $

To make it closer to TM, we can define our color format in following way:

A color format contains Variables.
Available variables: RED, GREEN, BLUE, HUE, SATURATION, LUMINANCE and ALPHA.
We use variables in color format by prefixing the variable name with $, e.g., rgb($RED, $GREEN, $BLUE).
Each variable has its default number format and range, e.g., RED's default number format is Integer and default range is [0-255].
We can change the variable number format and range by using this syntax ${«variable»:«new format»«new range»}, e.g. ${RED:f[0-1]}
Available number format

f, float with 2 decimal points.
Xf, float with X
d, decimal.
x, X, hexadecimal.

Range format is [LOW:HIGH]

Several samples with this new syntax

rgb(${RED}, ${GREEN}, ${BLUE}, ${ALPHA:d[0-255]})
#${RED:X}${GREEN:X}${BLUE:X}

As we only convert color value from its default format/range to new format/range, a declarative format «new format»«new range» is good enough for now. If ppl have complex feature requests, we can then add Transformations to this. @jrieken look forward to your comments on above proposal.

Great, I think we are on the right path with this. Some more thoughts...

I don't think that there is rule saying TextMate variables must be upper case, it just happens to be like that for most dynamic variables, similar to environment variables
The notion ${var_name:default value} is just one aspect of it and I don't know if it's the best fit because the semantics are: "Insert the resolved value of var_name and if that isn't possible insert default value. In our case we do have values for $RED, $GREEN etc. and I think we need something else.

In order to stay closer to the semantics and features of TextMate I can think of the following

We have more variables to statically cover number formats $RED_HEX, $RED_FLOAT, $RED_DEC etc. Next is number ranges and I believe the most common color ranges are [0-1], [0-100], [0-255], and [0-360]. I might be mistaken but could add more variables, e.g $HUE_DEC_360.
We can fiddle with the variable names and make them 'carry information', e.g $RED_HEX[0-255] which then will be interpreted as todays {blue:X[0-255]}. The challenge is that it's not well defined what a variable name is. From my experience it is [a-zA-Z_][_a-zA-Z0-9]* so it needs some tweaking or a different format.
The big hammer is something like snippet-transforms. They allow to manipulate the resolved value of a variable before insertion. The general format is ${«variable»/«regexp»/«format»/«options»} A real world sample that inserts your user name with the first latter capitalised is this: Hello ${USER/./${0:/upcase}/}. So, in original text mate the format-string supports built-in modifiers, like /upcase etc. I am looking at those modifiers and we could have something in the same spirit, e.g ${RED/.*/${0:/toDecimal(0,255)}/} which admittedly looks very complex...

To conclude, my preferences are option 1 and 2 or something in-between them. Our snippet parser and controller support all of this already today and it just needs another snippet variable resolver. I personally need to get a better understanding of the color formats because I don't understand red:d[0-255] when I can only create a Color object with numbers between 0 and 1. That makes me believe the 0 isn't actually needed in the formats. Please enlighten me @joaomoreno.

0 just serves as a minimum, as you could also have red:d[-128:128] although that is a very far fetched example... so I think we could drop the minimum and just go with red:d[255] or similar.

Ok, so my proposal would be dynamic variables ala $RED_HEX_FF. That would allows us to dump all custom parsing logic, make the API use the SnippetString and make the implementation use the SnippetController. So, I believe the format for color variable names would be
color    -> '$_' name ('_' format)?
name   ->  'red' | 'green' | 'blue' | 'hue' | 'saturation' | 'luminance' | 'alpha'
format -> ('d' | 'x' | 'f' | 'f' decimal) ('_' decimal){0-2}

Which allows for $red_x_ff (upper bound) or $red_x_00_ff (lower/upper bound) etc. This isn't the prettiest and bends a little the meaning of variables names but if we want to ship this month we have little slack for other experiments.
Now, seeing these names I might prefer something more transform-like, e.g ${RED/toDecimal(0,255)} which isn't adhering to the text mate snippet syntax but maybe something we can invent...

Alternatively to the discussions above I'd propose we stop the effort in trying to describe all possible color representations on this planet and simply delegate this to the extension in question. So, instead of a template string, we simply ask the provider for the insert string of a color. It will adding to the provider something like this
interface ColorProvider {
  resolveColor(color: Color): ProviderResult<string>
}

So, while the color changes (or on commit) we ask the provider to turn it into a string. Yeah, more chatty but more conservative, less API exposure etc.

That was the original approach, of course. I'll write down the missing drawbacks:

The label in the UI can possibly be laggy due to the roundtrip
That lag will be aggravated when we start throttling the calls, which we must
There won't be any label when the extension host is busy, which it can bee since while we pick a new color, we update the model, which can trigger extensions to do some work

With formats, we're obviously optimising towards responsiveness. I'm still convinced it is the way to go, especially considering that the argument against it is purely not being sure about the format syntax.
I personally don't have an opinion on the syntax itself. We can align it better with TextMate, but I doubt we'll change the experience for anyone for the better. Developers will still need to read the documentation to learn how to use them.

There won't be any label when the extension host is busy, which it can bee since while we pick a new color, we update the model, which can trigger extensions to do some work

Well, with todays implementation we keep it very busy by sending hundreds of document change events while dragging around in the picker UI. Also something we don't want.

It's really just a feeling... it would actually be cool to see it live.

resolveColor

I don't have a strong opinion on this. When we ask provideDocumentColors, extensions need to convert to color from whatever to RGBA. Considering they have the toolset to do the transformation, resolveColor can convert RGBA to the target format with the same toolset, e.g. parse-color.
To support multiple formats,  resolveColor should better return string[] which does toString for all formats.

The label in the UI can possibly be laggy due to the roundtrip
That lag will be aggravated when we start throttling the calls, which we must

This pushes me more to declarative format as we need throttling and we don't want to make it laggy.

with todays implementation we keep it very busy by sending hundreds of document change events while dragging around in the picker UI

@alexandrudima pointed this out to me in this morning as well and I did some basic testing. I didn't check whether it makes extensions laggy but dragging around for a few seconds, the CPU usage increases 50% and even 100% sometimes (well if you keep dragging it for 5 seconds, you can see a 100+% Code Helper).
No one complains about it yet but I'd like to have it fix to avoid another HN post.
I'll add more info ...

Current format
const CSSColorFormats = {
	Hex: '#{red:X}{green:X}{blue:X}',
	RGB: {
		opaque: 'rgb({red:d[0-255]}, {green:d[0-255]}, {blue:d[0-255]})',
		transparent: 'rgba({red:d[0-255]}, {green:d[0-255]}, {blue:d[0-255]}, {alpha})'
	},
	HSL: {
		opaque: 'hsl({hue:d[0-360]}, {saturation:d[0-100]}%, {luminance:d[0-100]}%)',
		transparent: 'hsla({hue:d[0-360]}, {saturation:d[0-100]}%, {luminance:d[0-100]}%, {alpha})'
	}
};

Dynamic TextMate Snippet Variable
const CSSColorFormats = {
	Hex: '#${red_x}${green_x}${blue_x}',
	RGB: {
		opaque: 'rgb(${red_d_0_255}, ${green_d_0_255}, ${blue_d_0_255})',
		transparent: 'rgba(${red_d_0_255}, ${green_d_0_255}, ${blue_d_0_255}, ${alpha})'
	},
	HSL: {
		opaque: 'hsl(${hue_d_0_360}, ${saturation_d_0_100}%, ${luminance_0_100}%)',
		transparent: 'hsla(${hue_d_0_360}, ${saturation_d_0_100}%, ${luminance_d_0_100}%, ${alpha})'
	}
};

Trying to organise and structure my thoughts here... I have two main concerns, one is regarding the declarative nature and one is the constantly changing document
Declarative Color Format
It definitely looks appealing and is cleverly implemented however it's not free of worry to me. These are my concerns

The API is asymmetric: we execute code to find colours but use a declarative approach for printing. It makes we wonder why we can express the printing of a color in declarative terms but not the discovery?
It increases the API surface by another dimension, even if we use a snippet syntax we need custom transformer functions like toDecimal
I doubt that we cover all color formats. In C# there is Color.FromArgb(int) with special byte order for that int. We might be able to express that but it might get ugly with un-padded values (F vs 0F). Then there are also well-known constants for colors, e.g. #FFF0F8FF is Color.AliceBlue and I don't see how that is expressed in the color format string.

Document Change Event Avalanche
This isn't really an API concern but an implementation concern. Today, while dragging around the model is being updated, these changes are forwarded to the extension host and language servers. I am unsure how we cope with that. I believe this is comparable to previewing IntelliSense suggestions on focus vs. inserting them on select and I'd feel better if we make this a UI thing and not a model change.
In short, my suggestion would be to execute code that transforms a color into one or many strings or text edits. Unsure how often we call that, personally I wouldn't feel uncomfortable if the document only changes on commit. Then I don't feel like I am loosing my current state. Updating the label inside the widget is another story, but we could also show two labels. A fixed color format (RGBA) and the 'preview' change that the provider will do.

@rebornix fyi - I have one or two little nits we should discuss around the new API but we can put that in a different issue

Was verifying this, but the API still lives in the proposed dts? I thought the plan is to move it to stable during Sep.

no


Arc correction for 400M1 and 600B modes

These observing modes contain arcs caused by light scattering inside GOODMAN. Flat images with and without gratings are obtained in order to correct this and get a normalized flat without this feature. This is not considered in the software by now and it is a must since the 400M1 mode is frequently used.

We should keep an eye on this and increase priority


chore: replace usage of deprecated cobra function

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 1 (0.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 27.805%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

cmd/completion.go
0
1
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
114

Relevant Lines:
410

💛  - Coveralls


Changing HTML source doesn't update model

Not sure if this is a bug or feature - when you change the HTML source in the editor, the model is not updated until you click the Source button again to turn off HTML editing. OnChange is also not triggered. Would be nice if updating the HTML would cause the model to be updated without having to click the Source button again.
Steps to reproduce:
https://embed.plnkr.co/hnB0R3/

Click "Source" to turn on html editing, type something in the editor. Notice that the output hasn't changed.
Click "Source" to turn off html editing. The output does update.

Hi, no this is not possible at all. Please check the reported bug in ckeditor forum, which has been closed because it's invalid. Change event was defined only for WYSIWYG mode. You can use the (change)="onChange($event)" event from ckeditor in order to get the changes when you change from source code to wysiwyg mode. Sorry, but this is not ng2-ckeditor issue. Please close this issue.


Add chocolatey and scoop installation in docs

workspacer is available in Scoop, and recently I have started to maintain a Chocolatey package of workspacer. It might be good to add these installation methods to the docs.

That's absolutely awesome and I definitely welcome this initiative￼!
That said, I think having the official release channel listed first and having third party distribution methods listed makes more sense.
￼￼￼If you can order things that way, I will certainly approve of this PR. ￼
What do you say @rickbutton ? 🙂

That said, I think having the official release channel listed first and having third party distribution methods listed after that makes more sense.
￼￼￼If you can order things that way, I will certainly approve of this PR. ￼

Sure, I will fix that.

PRs haven’t been merged in months and Rick haven’t been answering emails either.
Right now it seems a fork is needed to keep workspacer going forwards.
I’m discussing this in a issue here: https://github.com/rickbutton/workspacer/issues/211
Feel free to let me know your thoughts.

@dalyIsaac: Your suggestion looks fixed now. Can you click “Review” and formally “approve” the PR? 🙂

Resolved the conflict and finally got this merged. Thanks for helping out everyone.
We’re in a package-manager now 😎


Some threads are not HTTPS secure

In some threads, for example: https://forum.arduino.cc/index.php?topic=498224.0 the post is marked as only partially secure, as you can see:

Judging by the page source, the avatars are served up as HTTP links, not HTTPS.
Whilst I don't think this particular issue is a major security threat, it looks bad if you see messages about the site not being secure, and if you get used to seeing them, you may not care if a more serious security issue happens to strike.

I think it's solved


Update bots-guide.md

Updated the bots-guide.md to reflect the addition of helloworld bot; removed instructions to use followup bot

Automated message from Dropbox CLA bot
@theairportexplorer, thanks for the pull request! It looks like you haven't yet signed the Dropbox CLA. Please sign it here.

Automated message from Dropbox CLA bot
@theairportexplorer, thanks for signing the CLA!

@theairportexplorer thanks for working on this!
I'm a little unsure about the structure of this. I agree that the testing of the helloworld bot shouldn't have a separate header, maybe it'd be better to make it a sub-header? (#### Testing the helloworld bot instead of Talk to the bot.)
There, you can add the
It is recommended that you use the helloworld bot to start off.
The helloworld bot is a simple bot that responds with a 'beep boop'
 when queried. It can be used as a template to build more complex
bots.

section as an introduction and describe the process of how to set up the helloworld bot.

That makes sense. I'll reorganize it

I'm still going to leave a suggestion for using either the helloworld or help bot, that way it doesn't overwhelm new users with too many choices.

Fixed the indentation and merged, thanks @theairportexplorer!


Minor change to layer documentation file

CI Vulkan-ExtensionLayer build queued with queue ID 19587.

CI Vulkan-ExtensionLayer build # 124 running.

Oop, merged it without anyone reviewing this.


Feature/712 documentation overhaul

closes #712
Documentation changes will be smaller, more iterative amendments thus merging this initial overhaul now

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


React update

Do not merge!
This may currently break the build of this project, but is required for fra-manager. Currently investigating other workarounds for the @import issue.

Updating dependencies on React, React Tools and Jest to work with newer versions without writing warnings to the console.
The version bump to ^0.2.0 will mean that all users who depend on a ^0.1.x version will not be upgraded to this version automatically, although perhaps it should be kept in a separate branch from master (I can't specify that with my permissions).
Also contains the fix from #9, but that can be dropped if there is another workaround.

That's awesome Matt!

Seems out of date, closing and we can re-open if it's still needed.


do some juggling to wrap the unmount call in a retry

Inside umount, inspect the result and raise a new CommandException to trigger a retry. If we exhaust retries, the CommandException is still raised, so catch that in the caller and handle appropriately.
Could probably do without the else: clauses in the try/except as a run w/o an exception should return a result where result.success == True, but kept it in as a sanity check/safeguard.

I also moved the call to busy_mount inside unmount when result.success != true which gives us a bit more debug output on every failed unmount command rather than just the top-level umount.


Following the tutorial

I am using the details I you have provided it sounds awesome but the thing is that as mentioned the hand is not appearing in the screen and the final output is a Sphere around the character.I am doing an extended work On realSense n Unreal4 and very thankful for your work.
RealSenseUnreal4integration.pdf
I am icluding the entire PDF that I have done work with.I am unable to find the hand and gestures not showing in the screen that black hand.One More thing the 4.9.2 update when I am including the binaries it's crashing my Project.I would like to contribute extensively to this project.

That's a very cool pdf, you may want to shrink the debug sphere size to see the hand shape more clearly and you can change the color to have the same setup as shown in the readme.
Parts of this plugin are not particularly stable and even with the 4.9 update things are not yet perfect. If you wish to help, exposing more of the realsense functionality as well as improving multithreading stability are the most pressing concerns at the moment.

I recommend you use the official plugin from now on: https://github.com/GameTechDev/UE4RealSensePlugin


Add icon headset

I really don't understand how to do a pull request. Keeps failing (really new to github), so i am putting the icon I created here. Any suggestions to improve would also be appreciated.

I really don't understand how to do a pull request. Keeps failing (really new to github), so i am putting the icon I created here.

You can find out in our contributor's guide.
If you do not wish to bother with submitting PRs and working with code, just open an icon request issue and feel free to leave the dirty work to us. :)
Nonetheless, any icon design must stick to our icon design guidelines.

I want to work up to doing code, but that's a bit beyond me atm ^_^;... I think I have kept to your design guidelines from my read through, but apologies if I have made a mistake.

@karsa-mistmere after reading the document again I realised I made a few mistakes. Hopefully this version will be in line with the standards now.

Maybe we should switch to using 2px radii like this for the headphones icon?
https://lucide-site-git-feat-added-edit-page-jguddas.vercel.app/edit?PHN2ZwogIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyIKICB3aWR0aD0iMjQiCiAgaGVpZ2h0PSIyNCIKICB2aWV3Qm94PSIwIDAgMjQgMjQiCiAgZmlsbD0ibm9uZSIKICBzdHJva2U9ImN1cnJlbnRDb2xvciIKICBzdHJva2Utd2lkdGg9IjIiCiAgc3Ryb2tlLWxpbmVjYXA9InJvdW5kIgogIHN0cm9rZS1saW5lam9pbj0icm91bmQiCj4KICA8cmVjdCB4PSI5LjUiIHk9IjE4IiB3aWR0aD0iNSIgaGVpZ2h0PSI0IiByeD0iMiIgLz4KICA8cGF0aCBkPSJNMTQuNSAyMGgxYTQgNCAwIDAgMCA0LTRWOS41YTcuNSA3LjUgMCAwIDAtMTUgMFYxNGEyIDIgMCAxIDAgNCAwdi0yLjVhMiAyIDAgMCAwLTItMmgtMiIgLz4KICA8cGF0aCBkPSJNMTkuNSAxNGEyIDIgMCAxIDEtNCAwdi0yLjVhMiAyIDAgMCAxIDItMmgyIiAvPgo8L3N2Zz4=

Prefer your edit @jguddas, opening up those speakers makes it look far more balanced.

@jguddas Nice work, feel free to open a PR!

Alternative with adjusted headphones icon.

Adjusting the headphone icon also look better and more balanced and centered.
Comparison with @jguddas version (right one):


refactor(samples): update params in teradata transfer config

LGTM - waiting on product team to get back on any additional feedback.


Player view is deprecated when i use 2.18.0

I have migrate to exoplayer 2.18.0
Now playerview is deprecated. Can you look into this

Updated in #2


how simple is the base inputs

like I mean like how hard would it be to remake the inputs this uses. and just the inputs and nothing else

Duplicate PlayerSettings and Controls into a new flixel project. Also duplicate KeyBinds. I think that's it lol

like I mean like how hard would it be to remake the inputs this uses. and just the inputs and nothing else

so thats how you did it

I figured it out on my own in like 5 minutes
And it took me 5 months to figure it out.


SSMS 18.2:  Opening Saved Database Diagram crashes application

Hi:
For some reason, this only happens in a specific database; the others have not presented this problem.
Problem:  After saving a database diagram without any problems, trying to open the diagram (modify) crashes the entire application.  The application re-starts.
Things I've already tried:
1- Deleted the diagram
2- Refreshed the connection to the server (right-click on server node => refresh)
3- Confirmed the diagram no longer exists
4- Disconnected from Server
5- Closed application (SSMS)
6- Started application
7- Created a new diagram
8- Made necessary editions and saved the diagram
9- Closed the diagram
10- Re-opened (modify) the diagram (Diagram doesn't open and SSMS crashes)
11- Repeated steps 1 to 5
12- Performed an installation Repair
13- Repeated steps 6 to 10 with no success
Please let me know if there's any additional data needed.

@ArnieGA  We're sorry to hear you're experiencing issues.
Generally this forum is documentation or product-related issues that reference a specific article (tutorials, how-tos, etc.) only.
Please post your issue in the SQL Server forum.  There's a much better chance there to get the traction it needs to be handled by the product team.

I am also experiencing the same problem, but I can overcome it.
Open your diagrams not by double-clicking them, but instead by right-clicking them to open the related context menu and then select Modify menu. Everything is running well.

I am also experiencing this problem.   The right-context menu does not work around the issue.   This is with SSMS version  xxx.   It reproduces when run under Administrator or restricted Windows permission, and connecting using Domain, Local System and SQL Server accounts.  (Yes, I went through the matrix).   I am willing to provide whatever debugging data or access anyone want to take a look at this.   I was a developer in the Windows group for 9 years and thus am very accomodating to whatever may be needed to understand the issue.  SQL Server Management Studio						15.0.18330.0
SQL Server Management Objects (SMO)						16.100.37971.0
Microsoft Analysis Services Client Tools						15.0.19040.0
Microsoft Data Access Components (MDAC)						10.0.19041.1
Microsoft MSXML						3.0 6.0
Microsoft .NET Framework						4.0.30319.42000
Operating System						10.0.19041

Nevermind.  Known issue.


[Page] Permission

Migrate Permission page from vue-element-admin

[ ] Page permission
[ ] Directive permission
[ ] Two-step login

#38

Will work on this later this week.

Done!


upgrade Gadgetron

Failing due to
mv: cannot stat ‘INSTALL/share/gadgetron/config/gadgetron.xml.example’: No such file or directory

presumably they no longer include this?
In any case, this is going to hit https://github.com/CCPPETMR/SIRF/issues/432

the gadgetron.xml.example is still provided. In this case the Gadgetron compilation fails, so this is why the file doesn't exist. Error a little higher up:
-- Found BLAS: /usr/lib/libopenblas.so
OpenBLAS found
OPENBLAS_OMP_LIBRARIES OPENBLAS_OMP_LIBRARIES-NOTFOUND
OMP OPENBLAS NOT FOUND
BLAS /usr/lib/libopenblas.so LAPACK
CMake Error at /home/travis/.local/bin/cmake-3.13.4-Linux-x86_64/share/cmake-3.13/Modules/FindPackageHandleStandardArgs.cmake:137 (message):
  Could NOT find CBLAS (missing: CBLAS_INCLUDE_DIR)
Call Stack (most recent call first):
  /home/travis/.local/bin/cmake-3.13.4-Linux-x86_64/share/cmake-3.13/Modules/FindPackageHandleStandardArgs.cmake:378 (_FPHSA_FAILURE_MESSAGE)
  cmake/FindCBLAS.cmake:43 (find_package_handle_standard_args)
  CMakeLists.txt:323 (find_package)

-- Configuring incomplete, errors occurred!
See also "/home/travis/build/CCPPETMR/SIRF-SuperBuild/builds/Gadgetron/build/CMakeFiles/CMakeOutput.log".
make[2]: *** [builds/Gadgetron/stamp/Gadgetron-configure] Error 1
make[1]: *** [CMakeFiles/Gadgetron.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....

I had this error too, fixed by setting CBLAS_INCLUDE_DIR to /usr/include/x86_64-linux-gnu.


Add telnet package

Added telnet package.
Chocolatey installs package in system32, which is reflected by the changes in the install script compared to default template.

I assume this is for CommandVM usage. Is this a valuable tool for red teams?

Yes it is!

@Ana06  I locked the version to 0.9.0 in the nuspec file <dependency id="telnet" version="[0.9.0]"/>, is there another place I should be locking it?

The windows-2022 CI run is still not happy :(

Documenting possible solutions discussed privately:

Increase the Sleep to 20 seconds
Do not use the telnet dependency and instead use:
Start-Process -FilePath $pkgmgr -Argumentlist '/iu:"TelnetClient"' -Wait
Both options work, but the second is more elegant.

@geo-lit let me know if you need help to address the changes or if you don't have time (and then I'll address them).

Also, @geo-lit it would be very appreciated if you could squash the commits to keep a clean commit history (I can help you if you are not familiar with this). Alternatively, we can merge the PR with the squash and merge option (one commit for the whole PR).
Good reference: https://about.gitlab.com/blog/2018/06/07/keeping-git-commit-history-clean

It seems like the checks are passing. Please let me know how you would like me to squash the commits


Fix EdDSA keys / improve YubiKey support

This PR fixes two issues we faced with YubiKeys.
First issue: kty and crv can either be int or tstraccording to the RFC, where the string version should be one of the constants (like OKP or Ed25519). However, this library parses only the int version. This PR adds support for the string constants related to elliptic curves. There are likely more places where string constants are applicable, but the provided fixes are at least enough to get YubiKey working. Example input of such a key: {1: 'OKP', 3: -8, -1: 'Ed25519'}.
Second issue: some keys generate broken keys during registration (two errors: map length is wrong, and public key component x is bytearray instead of bytestring). See this issue for a more in-depth discussion. While this is technically not a fault in this library, this PR adds a workaround that detects and fixes those broken keys. Other webauthn libraries use such workarounds as well.

Thanks for your PR! I will look into it and include it in the next release.


OCPBUGS-34211: docker.io registry/2 is pulled with a platform argument

Description

docker.io updated to a  manifest listed image.
the code accounts for this change.

Fixes # https://issues.redhat.com/browse/OCPBUGS-34211
Type of change
Bug fix (non-breaking change which fixes an issue)
How Has This Been Tested?
Run on Z
Expected Outcome
e2e tests run on z/power

/jira refresh

/lgtm

/approve


how to edit as cs file with RoslynCodeEditor

At first, thank you very much for your sharing. My project uses the RoslynCodeEditor control, but it always works in *. CSX file. I would like it to work in *.CS file. How can I implement it through this control?

Duplicate of #150
See last comment https://github.com/aelij/RoslynPad/issues/150#issuecomment-341541762

I've tried, but failed. The example of RoslynCodeeEditor can't work normally. What I'm trying to do now is to copy the code of the example and regenerate it. But there are many problems, so now I can't even locate the problem. Can you provide me a download link for the normal operation of the example. I've tried to download many versions of RoslynPad, but all RoslynPadReplSample can't work.

I've tried, but failed. The example of RoslynCodeeEditor can't work normally. What I'm trying to do now is to copy the code of the example and regenerate it. But there are many problems, so now I can't even locate the problem. Can you provide me a download link for the normal operation of the example. I've tried to download many versions of RoslynPad, but all RoslynPadReplSample can't work.


Unexpected uint error with newtype wrapper

Hello!
I have a newtype wrapper around a u64 like so:
#[derive(Debug, Hydrate, Reconcile)]
pub struct Item {
    pub name: String,
    pub date: Option<Date>,
}

#[derive(Debug, Hydrate, Reconcile)]
pub struct Date(u64);

When I attempt to hydrate it from a doc with a value present for that key, I get the error unexpected uint.
I think this is because Option::hydrate calls Date::hydrate_uint but the derive impl for a newtype struct only generates Hydrate::hydrate. Is there a better way to accomplish what I'm trying to do here?
And as a larger meta question, why isn't the Hydrate impl for Option simply something like this that handles both missing and explicitly null values?
Ok(match doc.get(obj, &prop)? {
    Some((Scalar(v), _)) if *v == Null => None,
    Some(_) => Some(T::hydrate(doc, obj, prop)?),
    None    => None,
})

The reason Option<T>::hydrate returns an error if the value is not present at all is that sometimes you need to know that there wasn't a value in the document. Schema migrations are actually a good example of this, you might introduce a field which is optional but which you wish to have a default value for when the document was created before the field was introduced; in this case you would need to distinguish between the value being Null vs not present at all.
We have two tools for managing this. First there's MaybeMissing which is a wrapper type which allows you to detect the missing value. Second there is the missing= attribute which allows you to specify a function which will be used to populate the missing value (in your case you can use Default::default() to get the None).

Having a mechanism to detect and handle missing values makes sense, thanks! However this default behavior for Option is very surprising, Rust (serde)^1, Swift^2, and Go^3 all support deserializing both { "name": "test" } and { "name": "test", "date": null } into a struct with optional date field, where the date will be None/nil. TypeScript with zod's nullish behaves similarly.
I think optionality is orthogonal to defaults, when I want a default value in Rust I use the Default trait, not Option. Wouldn't it be better to make the missing= attribute an opt-in feature similar to serde's default attribute? As it stands right now I'd have to add #[autosurgeon(missing="Default::default")] to every single optional field in my schema which adds a lot of noise.


SendTransaction causes error DllNotFoundException: JustCRC32C_Native_x64.dll when confirm transaction

Update Asset from releases topic

https://github.com/continuation-team/unity-ton-connect/releases/tag/v0.2.4-alpha


state endpoint in "List of classes in the triple store"

"List of classes in the triple store"
http://aquarius.tw.rpi.edu/datafaqs/DataFAQs-lodspeakr/index.html
should state the endpoint being inspected.

Idem https://github.com/alangrafu/lodspeakr/issues/26

sorry, double-clicked submit :-)


Merge pull request #3 from sbkirby/sbkirby-patch-3

Change #background color to #202020 while using en_Night.css

my mistake


Rebrand

some polish modification pending

The readmes look good to me in general. I think we can merge it first and I will submit prs to update some details. Thanks.


Update fileio Vignette from the Perspective of hySpc.read.txt

This issue could be potentially be raised several places, but it's going here for now.
As this package is reaching a completion point in the very near future, it's a good time to update fileio.Rmd that resides in hyperSpec (I will mention this issue over there).  I'm assigning to Erick as his fresh eyes will be a real advantage.

[ ] Examine the outline of the document and see if it flows logically.  Some of these vigs have grown by accretion and re-organization is in order. Repeat this process as you go along, it might be necessary to move things several times.
[ ] Read over the intro vignette for general "feel" and to know what's in there, so it can be referenced potentially, there may even be some parts that can be re-used (and possibly re-used via a common file that is inserted).  Please see https://github.com/cbeleites/hyperSpec/issues/261 as well.
[ ] Update the material that relates to hySpc.read.txt appropriately so it is current.
[ ] Go over the entire document for flow and clarity and user-friendliness, the latter from the perspective of a newish user. Edit as needed.

@bryanhanson on the first pass of reading fileio.Rmd:
Text:
“Thus, once your data is in R’s workspace, creating a hyperSpec object is easy. I suggest wrapping the code to import your data and the line joining it into a hyperSpec object by your own import function. You are more than welcome to contribute such import code to package hyperSpec. Secion ?? discusses examples of custom import functions.”
Comment: Shouldn't "I" be replaced with "We": "We suggest wrapping the code..."

Text:
"The NIST (National Institute of Standards and Technology) has published a data base of basic atomic emission spectra see http://physics.nist.gov/PhysRefData/Handbook/periodictable.htm with emission lines tabulated in ASCII (HTML) files."
Comment: Can links be styled (i.e., [see here])(http://physics.nist.gov/PhysRefData/Handbook/periodictable.htm)

Text:
"Here’s an example [of] how to extract the data of the Hg strong lines file:"
Comment: I think it would benefit to add comments to each line for newbies and pros

Text:
"Many spectrometer manufacturers provide a function to export their spectra into ASCII files. The functions discussed above are written in a very general way[,] and are highly customizable. I recommend wrapping these calls with the appropriate settings for your spectra format in an import function. Please consider contributing such import filters to package hyperSpec: send me the documented code (for details see the box at the beginning of this document). If you are able to import data of any format not mentioned in this document (even without the need of new converters), please let me know (details again in the box at the beginning of this document)."
Comment: Shouldn't "I" be replaced with "We": "We recommend wrapping these calls..."
Other than that, I think the document is pretty well structured. There also appears to be "??" to indicate where sections need to be referenced.

Some general comments:

"We" is probably better since there is a team now.  You could check the intro vignette too (I re-wrote it but cannot remember just now any details).  Whatever you choose, be consistent with the "voice".
Styling links, fixing cross references etc.  Look to the intro vignette for how this is done.  These documents are using a bookdown approach where the details of these markdown signals are actually different that basic markdown.  VG translated these documents from knitr to  bookdown but there are still a lot of places to fix the details (As I edited the intro vig, and then updated my own package  pkgdown site, I realized how in-flux the markdown/bookdown/blogdown world is.  Hopefully it becomes more standardized)
VG implemented a means of inserting (and hiding) comments from developers and editors.  I actually eliminated most of these in the intro version as it evolved.  Those sections show up as colored boxes with outlines.  If you have trouble finding how he does this give me a holler.

Code blocks like this one mark developer's comments, and there is a flag to display or not somewhere.
{block, type="note-t", echo=show_reviewers_notes}

Code blocks like this one mark developer's comments, and there is a flag to display or not somewhere.
{block, type="note-t", echo=show_reviewers_notes}

Got it!

So use those blocks to write comments when you are not sure how to handle more significant or unclear items, then one of us can come along and respond/act.  Since you are actually working over in the hyperSpec repo leave these comments hidden since the vig is published when pushed.

This has been settled with the PR #28


[BUG] [JavaCPP] createImageManip fails with 2.18.0 (Fatal error on MSS CPU: trap: 09, address: 801F6FC8' '0')

Using JavaCPP as wrapper worked fine up to 2.17.4 creating and running multiple nodes on OAKD Lite. Using 2.18.0, processing stops at the point where an ImageManip node is created without any messages or errors and the device provides no output anymore.

Hi @ecmnet
I would need more information on this issue - do you mind appending DEPTHAI_LEVEL=debug output?
Also if you can create an MRE or pack the whole program with java libs alongside, I can take a look with a debugger (built in Debug configuration preferably)

Hi @themarpe
providing an example would take some more time. At least here's the debug output:
[2022-11-01 06:14:51.073] [debug] Library information - version: 2.18.0, commit:  from , build: 2022-10-28 12:12:15 +0000
[2022-11-01 06:14:51.090] [debug] Initialize - finished
[2022-11-01 06:14:51.259] [debug] Resources - Archive 'depthai-bootloader-fwp-0.0.21.tar.xz' open: 5ms, archive read: 178ms
[2022-11-01 06:14:51.638] [debug] Device - OpenVINO version: 2022.1
[2022-11-01 06:14:51.638] [debug] Device - BoardConfig: {"emmc":null,"gpio":[],"logDevicePrints":null,"logPath":null,"logSizeMax":null,"logVerbosity":null,"network":{"mtu":0,"xlinkTcpNoDelay":true},"pcieInternalClock":null,"sysctl":[],"uart":[],"usb":{"flashBootedPid":63037,"flashBootedVid":999,"maxSpeed":3,"pid":63035,"vid":999},"usb3PhyInternalClock":null,"watchdogInitialDelayMs":null,"watchdogTimeoutMs":null}
libnop:
0000: b9 0e b9 05 81 e7 03 81 3b f6 81 e7 03 81 3d f6 03 b9 02 00 01 ba 00 be be bb 00 bb 00 be be be
0020: be be be be
[2022-11-01 06:14:51.919] [debug] Resources - Archive 'depthai-device-fwp-a555263a9dbff1166088bcb758ab4306dca9ae1a.tar.xz' open: 4ms, archive read: 839ms
[2022-11-01 06:14:53.083] [debug] Searching for booted device: DeviceInfo(name=20.3, mxid=1844301011B57D1200, X_LINK_BOOTED, X_LINK_USB_VSC, X_LINK_MYRIAD_X, X_LINK_SUCCESS), name used as hint only
[1844301011B57D1200] [20.3] [67.961] [system] [info] Memory Usage - DDR: 0.12 / 340.61 MiB, CMX: 2.05 / 2.50 MiB, LeonOS Heap: 7.22 / 77.48 MiB, LeonRT Heap: 2.88 / 41.35 MiB
[1844301011B57D1200] [20.3] [67.961] [system] [info] Temperatures - Average: 29.65 °C, CSS: 31.04 °C, MSS 29.59 °C, UPA: 28.62 °C, DSS: 29.35 °C
[1844301011B57D1200] [20.3] [67.961] [system] [info] Cpu Usage - LeonOS 9.34%, LeonRT: 1.67%
[2022-11-01 06:14:53.903] [debug] Schema dump: {"connections":[{"node1Id":1,"node1Output":"preview","node1OutputGroup":"","node2Id":6,"node2Input":"inputImage","node2InputGroup":""},{"node1Id":2,"node1Output":"depth","node1OutputGroup":"","node2Id":0,"node2Input":"in","node2InputGroup":""},{"node1Id":1,"node1Output":"preview","node1OutputGroup":"","node2Id":0,"node2Input":"in","node2InputGroup":""},{"node1Id":7,"node1Output":"out","node1OutputGroup":"","node2Id":5,"node2Input":"in","node2InputGroup":""},{"node1Id":6,"node1Output":"out","node1OutputGroup":"","node2Id":7,"node2Input":"in","node2InputGroup":""},{"node1Id":4,"node1Output":"out","node1OutputGroup":"","node2Id":2,"node2Input":"right","node2InputGroup":""},{"node1Id":3,"node1Output":"out","node1OutputGroup":"","node2Id":2,"node2Input":"left","node2InputGroup":""}],"globalProperties":{"calibData":null,"cameraTuningBlobSize":null,"cameraTuningBlobUri":"","leonCssFrequencyHz":700000000.0,"leonMssFrequencyHz":700000000.0,"pipelineName":null,"pipelineVersion":null,"xlinkChunkSize":-1},"nodes":[[0,{"id":0,"ioInfo":[[["","in"],{"blocking":true,"group":"","name":"in","queueSize":8,"type":3,"waitForMessage":true}]],"name":"XLinkOut","properties":[185,3,136,0,0,128,191,189,7,112,114,101,118,105,101,119,0]}],[1,{"id":1,"ioInfo":[[["","inputConfig"],{"blocking":false,"group":"","name":"inputConfig","queueSize":8,"type":3,"waitForMessage":false}],[["","frameEvent"],{"blocking":false,"group":"","name":"frameEvent","queueSize":8,"type":0,"waitForMessage":false}],[["","video"],{"blocking":false,"group":"","name":"video","queueSize":8,"type":0,"waitForMessage":false}],[["","raw"],{"blocking":false,"group":"","name":"raw","queueSize":8,"type":0,"waitForMessage":false}],[["","inputControl"],{"blocking":true,"group":"","name":"inputControl","queueSize":8,"type":3,"waitForMessage":false}],[["","isp"],{"blocking":false,"group":"","name":"isp","queueSize":8,"type":0,"waitForMessage":false}],[["","still"],{"blocking":false,"group":"","name":"still","queueSize":8,"type":0,"waitForMessage":false}],[["","preview"],{"blocking":false,"group":"","name":"preview","queueSize":8,"type":0,"waitForMessage":false}]],"name":"ColorCamera","properties":[185,23,185,27,0,3,0,0,0,185,3,0,0,0,185,5,0,0,0,0,0,185,5,0,0,0,0,0,0,0,0,0,0,0,0,185,3,0,0,0,185,3,0,0,0,0,0,0,0,0,0,0,0,0,0,255,255,0,0,0,129,224,1,129,128,2,255,255,255,255,0,136,0,0,112,65,136,0,0,128,191,136,0,0,128,191,1,185,4,0,0,0,0,3,3,4,4,4]}],[2,{"id":2,"ioInfo":[[["","right"],{"blocking":false,"group":"","name":"right","queueSize":8,"type":3,"waitForMessage":true}],[["","debugDispLrCheckIt2"],{"blocking":false,"group":"","name":"debugDispLrCheckIt2","queueSize":8,"type":0,"waitForMessage":false}],[["","rectifiedRight"],{"blocking":false,"group":"","name":"rectifiedRight","queueSize":8,"type":0,"waitForMessage":false}],[["","inputConfig"],{"blocking":false,"group":"","name":"inputConfig","queueSize":4,"type":3,"waitForMessage":false}],[["","debugExtDispLrCheckIt1"],{"blocking":false,"group":"","name":"debugExtDispLrCheckIt1","queueSize":8,"type":0,"waitForMessage":false}],[["","syncedLeft"],{"blocking":false,"group":"","name":"syncedLeft","queueSize":8,"type":0,"waitForMessage":false}],[["","confidenceMap"],{"blocking":false,"group":"","name":"confidenceMap","queueSize":8,"type":0,"waitForMessage":false}],[["","syncedRight"],{"blocking":false,"group":"","name":"syncedRight","queueSize":8,"type":0,"waitForMessage":false}],[["","outConfig"],{"blocking":false,"group":"","name":"outConfig","queueSize":8,"type":0,"waitForMessage":false}],[["","debugExtDispLrCheckIt2"],{"blocking":false,"group":"","name":"debugExtDispLrCheckIt2","queueSize":8,"type":0,"waitForMessage":false}],[["","left"],{"blocking":false,"group":"","name":"left","queueSize":8,"type":3,"waitForMessage":true}],[["","depth"],{"blocking":false,"group":"","name":"depth","queueSize":8,"type":0,"waitForMessage":false}],[["","debugDispLrCheckIt1"],{"blocking":false,"group":"","name":"debugDispLrCheckIt1","queueSize":8,"type":0,"waitForMessage":false}],[["","rectifiedLeft"],{"blocking":false,"group":"","name":"rectifiedLeft","queueSize":8,"type":0,"waitForMessage":false}],[["","debugDispCostDump"],{"blocking":false,"group":"","name":"debugDispCostDump","queueSize":8,"type":0,"waitForMessage":false}],[["","disparity"],{"blocking":false,"group":"","name":"disparity","queueSize":8,"type":0,"waitForMessage":false}]],"name":"StereoDepth","properties":[185,16,185,5,185,9,2,2,136,0,0,122,68,1,0,1,5,3,0,185,7,7,0,185,5,0,2,136,0,0,0,63,0,1,185,4,0,3,136,205,204,204,62,0,185,2,0,134,255,255,0,0,185,2,0,50,185,2,1,0,185,4,255,0,1,0,185,5,1,0,0,100,185,3,0,2,127,185,5,1,128,250,129,244,1,128,250,129,244,1,255,1,255,190,190,133,128,2,133,224,1,1,185,5,189,0,189,0,190,16,16,0,1,255,255,1,0]}],[3,{"id":3,"ioInfo":[[["","inputControl"],{"blocking":true,"group":"","name":"inputControl","queueSize":8,"type":3,"waitForMessage":false}],[["","frameEvent"],{"blocking":false,"group":"","name":"frameEvent","queueSize":8,"type":0,"waitForMessage":false}],[["","out"],{"blocking":false,"group":"","name":"out","queueSize":8,"type":0,"waitForMessage":false}],[["","raw"],{"blocking":false,"group":"","name":"raw","queueSize":8,"type":0,"waitForMessage":false}]],"name":"MonoCamera","properties":[185,7,185,27,0,3,0,0,0,185,3,0,0,0,185,5,0,0,0,0,0,185,5,0,0,0,0,0,0,0,0,0,0,0,0,185,3,0,0,0,185,3,0,0,0,0,0,0,0,0,0,0,0,0,0,1,255,3,136,0,0,112,65,3,3]}],[4,{"id":4,"ioInfo":[[["","inputControl"],{"blocking":true,"group":"","name":"inputControl","queueSize":8,"type":3,"waitForMessage":false}],[["","frameEvent"],{"blocking":false,"group":"","name":"frameEvent","queueSize":8,"type":0,"waitForMessage":false}],[["","out"],{"blocking":false,"group":"","name":"out","queueSize":8,"type":0,"waitForMessage":false}],[["","raw"],{"blocking":false,"group":"","name":"raw","queueSize":8,"type":0,"waitForMessage":false}]],"name":"MonoCamera","properties":[185,7,185,27,0,3,0,0,0,185,3,0,0,0,185,5,0,0,0,0,0,185,5,0,0,0,0,0,0,0,0,0,0,0,0,185,3,0,0,0,185,3,0,0,0,0,0,0,0,0,0,0,0,0,0,2,255,3,136,0,0,112,65,3,3]}],[5,{"id":5,"ioInfo":[[["","in"],{"blocking":true,"group":"","name":"in","queueSize":8,"type":3,"waitForMessage":true}]],"name":"XLinkOut","properties":[185,3,136,0,0,128,191,189,2,110,110,0]}],[6,{"id":6,"ioInfo":[[["","inputConfig"],{"blocking":true,"group":"","name":"inputConfig","queueSize":8,"type":3,"waitForMessage":false}],[["","out"],{"blocking":false,"group":"","name":"out","queueSize":8,"type":0,"waitForMessage":false}],[["","inputImage"],{"blocking":true,"group":"","name":"inputImage","queueSize":8,"type":3,"waitForMessage":true}]],"name":"ImageManip","properties":[185,6,185,8,185,7,185,4,136,0,0,0,0,136,0,0,0,0,136,0,0,0,0,136,0,0,0,0,185,3,185,2,136,0,0,0,0,136,0,0,0,0,185,2,136,0,0,0,0,136,0,0,0,0,136,0,0,0,0,0,136,0,0,128,63,136,0,0,128,63,0,1,185,15,133,160,1,133,160,1,1,0,0,0,186,0,1,0,186,0,0,0,136,0,0,0,0,0,1,185,3,32,0,0,0,1,0,0,0,134,0,0,16,0,4,0,0,189,0]}],[7,{"id":7,"ioInfo":[[["","in"],{"blocking":true,"group":"","name":"in","queueSize":5,"type":3,"waitForMessage":true}],[["","passthrough"],{"blocking":false,"group":"","name":"passthrough","queueSize":8,"type":0,"waitForMessage":false}],[["","out"],{"blocking":false,"group":"","name":"out","queueSize":8,"type":0,"waitForMessage":false}]],"name":"DetectionNetwork","properties":[185,6,130,198,227,57,0,189,12,97,115,115,101,116,58,95,95,98,108,111,98,8,2,0,185,7,0,136,154,153,153,62,80,4,186,18,136,0,0,32,65,136,0,0,80,65,136,0,0,128,65,136,0,0,240,65,136,0,0,4,66,136,0,0,184,65,136,0,0,240,65,136,0,0,116,66,136,0,0,120,66,136,0,0,52,66,136,0,0,108,66,136,0,0,238,66,136,0,0,232,66,136,0,0,180,66,136,0,0,28,67,136,0,0,70,67,136,0,128,186,67,136,0,0,163,67,187,3,189,6,115,105,100,101,49,51,188,12,6,0,0,0,7,0,0,0,8,0,0,0,189,6,115,105,100,101,50,54,188,12,3,0,0,0,4,0,0,0,5,0,0,0,189,6,115,105,100,101,53,50,188,12,0,0,0,0,1,0,0,0,2,0,0,0,136,154,153,153,62]}]]}
[2022-11-01 06:14:53.903] [debug] Asset map dump: {"map":{"/node/7/__blob":{"alignment":64,"offset":0,"size":3793862}}}
[1844301011B57D1200] [20.3] [68.142] [MonoCamera(4)] [info] Using board socket: 2, id: 2
[1844301011B57D1200] [20.3] [68.142] [MonoCamera(3)] [info] Using board socket: 1, id: 1
[1844301011B57D1200] [20.3] [68.144] [system] [info] SIPP (Signal Image Processing Pipeline) internal buffer size '16384'B
[1844301011B57D1200] [20.3] [68.179] [system] [info] ImageManip internal buffer size '372736'B, shave buffer size '35840'B
[1844301011B57D1200] [20.3] [68.180] [system] [info] NeuralNetwork allocated resources: shaves: [0-9] cmx slices: [0-9]
ColorCamera allocated resources: no shaves; cmx slices: [13-15]
MonoCamera allocated resources: no shaves; cmx slices: [13-15]
StereoDepth allocated resources: shaves: [13-13] cmx slices: [10-12]
ImageManip allocated resources: shaves: [15-15] no cmx slices.
[1844301011B57D1200] [20.3] [68.184] [StereoDepth(2)] [info] Using focal length from calibration intrinsics '453.64474'
[1844301011B57D1200] [20.3] [68.191] [StereoDepth(2)] [info] Rectification mesh loaded, will override camera intrinsics/extrinsics matrices
[1844301011B57D1200] [20.3] [68.204] [DetectionNetwork(7)] [info] Needed resources: shaves: 5, ddr: 4142144
[1844301011B57D1200] [20.3] [68.215] [DetectionNetwork(7)] [info] Inference thread count: 2, number of shaves allocated per thread: 5, number of Neural Compute Engines (NCE) allocated per thread: 1
[1844301011B57D1200] [20.3] [69.465] [system] [critical] Fatal error. Please report to developers. Log: 'Fatal error on MSS CPU: trap: 09, address: 801F6FC8' '0'
[2022-11-01 06:14:57.396] [debug] DataOutputQueue (preview) closed
[2022-11-01 06:14:57.397] [debug] DataOutputQueue (nn) closed
[2022-11-01 06:14:57.665] [debug] Log thread exception caught: Couldn't read data from stream: '__log' (X_LINK_ERROR)
[2022-11-01 06:14:57.667] [debug] Timesync thread exception caught: Couldn't read data from stream: '__timesync' (X_LINK_ERROR)
[2022-11-01 06:14:57.667] [debug] Watchdog thread exception caught: Couldn't write data to stream: '__watchdog' (X_LINK_ERROR)

Might be related to https://github.com/luxonis/depthai-core/issues/621

@ecmnet
Do you mind testing out with latest 2.19.0? There were some bugfixes along the way, that might be relevant.

Will do as soon as 2.19.0 Is available in javacpp 1.5.9-snapshot

Any news on this @ecmnet ?
There was also a v2.19.1 release which addresses some (runtime though) issues

@themarpe According to the debug output with 1.5.9-SNAPSHOT using 2.19.1 the error mentioned above does not occur anymore. However, the code running with 2.17.4 still does not provide any data. As far as I can see up to now, the callback, I am using is not triggered anymore.
       imageCallback = new OAKDImageCallback(); 	 queue.addCallback(imageCallback);
Callback class:
`private class OAKDImageCallback extends Callback {
	public void call() {

		try {

			ImgFrame imgFrame = queue.tryGetImgFrame();
			if(imgFrame!=null && !imgFrame.isNull() ) {
				switch(imgFrame.getInstanceNum()) {
				case RGB_FRAME:
					rgb_tms = System.currentTimeMillis();
					if(rgb_mode)
						transfer_rgb.offer(imgFrame);
					else
						imgFrame.close();
					break;
				case MONO_FRAME:
					rgb_tms = System.currentTimeMillis();
					if(!rgb_mode)
						transfer_mono.offer(imgFrame);
					else
						imgFrame.close();  // Shouldn't this be called always??
					break;
				case DEPTH_FRAME:
					depth_tms = System.currentTimeMillis();
					transfer_depth.offer(imgFrame);
					break;
				}

			}
		} catch (Exception e) {	}
	}
}`

Thanks - does this happen with 2.19.1?
I'm sorry, but I unfortunatelly won't have time to dig into Java port for the time being. You can try checking further with a debugger to see where the native code gets stuck.
By "before stopping" does it close or just nothing comes through? Do you mind try running with DEPTHAI_WATCHDOG=0 (a warning should be printed)?

Yes this is 2.19.1, stopping means just nothing coming through. Other API calls such as reading intrinsics etc are fine.
Will stick to 2.17..4 as a working solution for now.

Tested with Watchdog disabled. Same result - polling stops after 2 or 3 frames.
[2022-12-03 08:32:23.747] [warning] Watchdog disabled! In case of unclean exit, the device needs reset or power-cycle for next run
Connected cameras: 0 1 2  USB speed is HIGH
OAK-D Lite pipeline started

Callback does not work at all:
OAK-D Lite pipeline started
[2022-12-03 08:35:14.011] [warning] Watchdog disabled! In case of unclean exit, the device needs reset or power-cycle for next run
0 1 2 - HIGH
CameraPinholeRadial{fx=453.11041259765625, fy=453.11041259765625, skew=0.0, cx=331.7960205078125, cy=240.80442810058594, width=640, height=480}
OAK-D Lite depth pipeline 1 started: true

FYI, seems to be fixed in recent versions: https://github.com/bytedeco/javacpp-presets/issues/1278#issuecomment-1519405288


future?

Is the plan to keep this project separate and distinct from react-select, or is it eventually going to get merged back.

I'd be happy to see the added features in this project merged in to react-select, but ultimately that's up to the react-select maintainers. Until then, I intend to maintain this fork.

@TrevorBurnham Appreciate you adding more to react-select. Is it possible to have a short summary of what all features does it have in addition to the original react-select library?

Currently, react-select-plus has these features that react-select does not have:

Most important: Support for option groups (https://github.com/HubSpot/react-select-plus/pull/3)
The dropdown can be a custom component, e.g. allowing it to be rendered in a position: fixed container to avoid z-index issues: https://github.com/HubSpot/react-select-plus/pull/2
If value does not match any option, the value can be displayed: https://github.com/HubSpot/react-select-plus/pull/9
You can override the open/closed state of the dropdown: https://github.com/HubSpot/react-select-plus/pull/1


Questions about description

I noticed that the fill_replay function in your code always selects the first description.
desc = descs[0]

But an RLBench task usually has several different descriptions.
Can the trained model generalize to other descriptions?

@SatireY, I made this design choice to make it easier for PerAct to learn. But in theory, randomly sampling from all descriptions should work. CLIP's language encoder might be robust to small paraphrases, but I haven't tested this extensively.

Ok, I see. Thank you for your reply


Fail with error: URL is required on resumable upload

Error while resumable upload due to metadata size.
The original error is metadata size but some issue in gcd-resumable, due to issue  in gcd-resumable upload not able to write entry URI field in ~/.config/configstore/gcs-resumable-upload.json.
Error: URL is required.
    at Gaxios.validateOpts (/home/nodejs-storage/node_modules/gaxios/build/src/gaxios.js:111:19)
    at Gaxios.request (/home/nodejs-storage/node_modules/gaxios/build/src/gaxios.js:58:21)
    at Object.request (/home/nodejs-storage/node_modules/gaxios/build/src/index.js:29:29)
    at DefaultTransporter.request (/home/nodejs-storage/node_modules/google-auth-library/build/src/transporters.js:65:29)
    at JWT.requestAsync (/home/nodejs-storage/node_modules/google-auth-library/build/src/auth/oauth2client.js:346:41)
    at process.internalTickCallback (internal/process/next_tick.js:77:7)

Here is the content  of ~/.config/configstore/gcs-resumable-upload.json
{
  "fe-store/1.txt": {
    "txt": {
      "firstChunk": {
        "type": "Buffer",
        "data": [
          116,
          101,
          115,
          116
        ]
      }
    }
  }
}

Environment details

OS: os x
Node.js version: 11.1.0
npm version: 6.9.2
@google-cloud/storage version:  3.1.0

Steps to reproduce
https://gist.github.com/jiren/2d6dec5b42f9c8559837339c3b0232e7

I've sent a PR to fix this on gcs-resumable-upload: https://github.com/googleapis/gcs-resumable-upload/pull/255

Fix merged! Just need a release of gcs-resumable-upload, then we will update here.

New installations of Storage should pick up the underlying change made in gcs-resumable-upload.


Remove duplicate submitButton macro option

What is the context of this PR?
Remove duplicate question macro option submitButton
How to review
Docs make sense

 Remove duplicate macro option for onsQuestion


Support "Django Sites" in Mezzanine

Hi, I need to have multiple sites with different content. I sought support for multiple sites in Mezzanine and I only found to change themes.
I need to specify which sites the content is displayed.
Thank you very much.

This is all built in, spend some more time looking.

I looked at the file models.py from mezzanine.core app and have not found anything.
I want to have several websites:

spain.market.domain
portugal.market.domain

I want to create a page visible only to Spain and is displayed on the menu. Then I want to create a different page, and make it available only in Portugal.
I have looked at the documentation and source code and do not see anything. I could modify default models (blog, etc.) to add support for sites, but I would have to modify insurance more.

That's bizarre, because the first piece of code in the file you mentioned is exactly the code you're asking about.
Like I said, it's all built in already, but if you don't believe me, try the mailing list, maybe someone else can convince you.

Ok, sorry for my fault. I did not see documented and thought "SiteRelated" was something else.

It's documented here: http://mezzanine.jupo.org/docs/multi-tenancy.html


Snowsql error: The number of downloading files doesn't match the encryption materials

Papetrail search
Snowflake ticket

https://connection.keboola.com/admin/utils/logs?file=2019/06/12/10/2019-06-12-10-02-52-5d00b1ac1a4c6-exception
https://connection.keboola.com/admin/utils/logs?file=2019/06/12/10/2019-06-12-10-02-52-5d00b1ac2c0c8-log
(2) Snowsql error, process output * SnowSQL * v1.1.49 Type SQL statements or !help
+----------------------------------+
| status                           |
|----------------------------------|
| Statement executed successfully. |
+----------------------------------+
1 Row(s) produced. Time Elapsed: 0.214s
+----------------------------------+
| status                           |
|----------------------------------|
| Statement executed successfully. |
+----------------------------------+
1 Row(s) produced. Time Elapsed: 0.388s
+----------------------------------+
| status                           |
|----------------------------------|
| Statement executed successfully. |
+----------------------------------+
1 Row(s) produced. Time Elapsed: 0.243s

If the error message is not clear, enable the logging using -o log_level=DEBUG and see the log to find out the cause. Contact the support for further help. Goodbye!
Snowsql error: 253008 (n/a): The number of downloading files doesn't match the encryption materials: files=16, encmat=15
[2019-06-12 10:02:50] CRITICAL: Exception:File download error occurred processing [V_PIVOT_VECTOR_MERGED]
{
    "errFile": "/code/src/Keboola/DbExtractor/Extractor/Snowflake.php",
    "errLine": 226,
    "errCode": 0,
    "errTrace": "#0 /code/src/Keboola/DbExtractor/Extractor/Snowflake.php(116): Keboola\\DbExtractor\\Extractor\\Snowflake->exportAndDownload(Array)\n#1 /code/vendor/keboola/db-extractor-common/src/Keboola/DbExtractor/Application.php(166): Keboola\\DbExtractor\\Extractor\\Snowflake->export(Array)\n#2 /code/vendor/keboola/db-extractor-common/src/Keboola/DbExtractor/Application.php(65): Keboola\\DbExtractor\\Application->runAction()\n#3 /code/run.php(43): Keboola\\DbExtractor\\Application->run()\n#4 {main}",
    "errPrevious": ""
}

https://keboola.slack.com/archives/C09U3R1J4/p1561091746004700

https://keboola.slack.com/archives/C09U3R1J4/p1561518315012200

again https://keboola.slack.com/archives/C09U3R1J4/p1565434271000100

again https://keboola.slack.com/archives/C09U3R1J4/p1565768974002900
so far we have:

project id 1514  - Aug 10 12:50:29 and Aug 14 09:49:08
project id 5714 -  Jun 21 06:34:46 and Jun 26 05:03:47

Aug 27 00:53:28 again in project id 1514 - https://keboola.slack.com/archives/C09U3R1J4/p1566860048000900

Sent to Snowflake support: https://support.snowflake.net/s/case/5000Z00001FPpbWQAT/snowsql-error-253008 for details

They admit it is a rare error and they do not know its root cause. So it would be most likely best to retry when it appears.

again https://keboola.zendesk.com/agent/tickets/11646

dneska opat na shared configu: https://keboola.zendesk.com/agent/tickets/12888


feat: provide "index" pages for deno.land packages

Closes #129

I still need to write tests, but it is functionally complete and I am happy with the look.

Here is an example of what the std lib looks like now<EMAIL_ADDRESS>

nice work! small detail improvement i want to request, can we hide the border between index items? i think it looks vary rough, or you can show it only the content is expanded

This looks good - but ultimately we need to move docs to deno.land itself - no long in doc.deno.land. I'm sure this work will be useful for that eventually.

This looks good - but ultimately we need to move docs to deno.land itself - no longer on doc.deno.land. I'm sure this work will be useful for that eventually.

Yes, it is currently easier to improve doc.deno.land as we figure out how to combine the two.

nice work! small detail improvement i want to request, can we hide the border between index items? i think it looks vary rough, or you can show it only the content is expanded

@ije thanks for the feedback...  It was inspired by GoLang's doc website:

We are missing a lot of module level documentation (JSDoc @module) in the std lib at the moment which is why there is nothing populated in the right, but when we do populate it, it will look a lot like what you see in the GoLang example, in which some sort of delimiter feels necessary to me.  Given that information, do you still feel the same way that we should eliminate it?

@ije again, thanks for the feedback, but removing it feels like the "wrong" direction personally and makes the page a lot more difficult to read:

and:

I am totally open to revisiting the whole design, as well as taking a PR that changes the design in the future, but I think we should just move forward with something with the visual line breaks until we have a better overall design.


Fixing sonar code smells

Do not use Array index in keys
Unnecessary use of conditional expression for default assignment.
Refactor this function to reduce its Cognitive Complexity

coverage: 94.273% (+0.001%) from 94.272% when pulling b1160a9c7e32f7f32a4f294d34325522603d6c18 on cody-sonar-code-smells-2023-07-31 into 7fb02b94b3fb052da22d5b892ff0e951d11b1912 on main.


Add support for platform api 0.9 and bump lifecycle to 0.14.1

resolves #998

Codecov Report

Merging #1026 (9f88b1a) into main (79b4727) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1026   +/-   ##
=======================================
  Coverage   70.14%   70.14%
=======================================
  Files         122      122
  Lines        5658     5658
=======================================
  Hits         3969     3969
  Misses       1313     1313
  Partials      376      376

Impacted Files
Coverage Δ

pkg/apis/build/v1alpha2/build_pod.go
98.60% <ø> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


PedalLine half-lfit bug fixed

Pedal Line currently crashes if NO half lift positions are declared. Added if statement to check if half_lift_positions is empty. And checks if half lift positions are within pedal line length.

Andrew - I've had to work on this blind as my Poetry wont install on my Mac, but my GitHub access is declined in Linux. The tests and code fix work on my Linux machine, but having to PR via my Mac :(

Pre-commit is throwing an error from **sh dev_scripts/pre_commit.sh **
Running pre-commit cleanup
Removing unused imports
Traceback (most recent call last):
File "/usr/local/Caskroom/miniconda/base/bin/unimport", line 10, in
sys.exit(main())
File "/usr/local/Caskroom/miniconda/base/lib/python3.7/site-packages/unimport/main.py", line 60, in main
utils.get_used_packages(Import.imports, unused_imports)
File "/usr/local/Caskroom/miniconda/base/lib/python3.7/site-packages/unimport/utils.py", line 102, in get_used_packages
name = package_name_from_metadata(package)
File "/usr/local/Caskroom/miniconda/base/lib/python3.7/site-packages/unimport/utils.py", line 90, in package_name_from_metadata
return metadata(package)["Name"]
File "/usr/local/Caskroom/miniconda/base/lib/python3.7/site-packages/importlib_metadata/init.py", line 1010, in metadata
return Distribution.from_name(distribution_name).metadata
File "/usr/local/Caskroom/miniconda/base/lib/python3.7/site-packages/importlib_metadata/init.py", line 567, in from_name
raise ValueError("A distribution name is required.")
ValueError: A distribution name is required.

ugh, more environment shenanigans. i don't know. i just ran it on my machine and pushed, once the build passes I will merge.

the error sounds similar to what we were seeing over here https://github.com/hakancelikdev/unimport/issues/229 - I assume you're running on Ubuntu as well...

thank you!

@craigvear could you confirm the version number of unimport that was giving you trouble? unimport --version should tell you


[RFC] zephyr: renamed single-image mode to single-slot mode

The terms "single-image boot" and the "single image application"
of Zephyr are confused. It might be might be understood as one-pair image
dual-bank mode in comparison to multi-image mode.
This patch replaces CONFIG_SINGLE_IMAGE_DFU by CONFIG_SINGLE_SLOT_DFU
name, which makes this mode name unambiguous.
fixes #800
Signed-off-by: Andrzej Puzdrowski<EMAIL_ADDRESS>

@de-nordic ?

I do not mind changing the name. Unfortunately I had not gave enough though to the name prior to crafting that motley of words.
Generally it should mean "The one application slot configuration" so maybe it should be rather replaced with
SINGLE_APPLICATION_SLOT. I think that the DFU is misleading here because the code does not actually provide DFU functionality, it is provided by other components of the MCUBOOT; even the source file name indicates that this is only loader (single_loader.c).

@de-nordic SINGLE_APPLICATION_SLOT sound good to me as well. And, right DFU abbreviation  has nothing to what MCUBoot does.

@davidvincze Do you want to look at this?


JIRA-750: Fixing the style so the private icon does not overlap

To test:
Prior to pulling branch, log in to Center using obrien.
Find a Listing under the Minipax org (ex: Wolf Finder)
Open the listing and click the edit button.
Scroll down to the "Private Listing" section and enable the listing as private.
Click Save.
Return to Center, find the Minipax listing that was edited, open the listing, and see that the Lock icon is overlapping the Minipax text.
Pull this branch.
Restart center server
Refresh the browser.
The icon should no longer be overlapping the text.

Prior:

After:

:+1:

:+1:


user12986714: Watch triclara(?!.com)

user12986714 requests the watch of the watch_keyword triclara(?!\.com). See the MS search here and the Stack Exchange search in text, in URLs, and in code.

triclara(?!\.com) has been seen in 2 true positives, 0 false positives, and 0 NAAs.

Approved by Daniil in Charcoal HQ


CLIXBOX-833 - Let devs open dev console on Xbox

This allows place/group owners to open the developer console on Xbox. Adjusted some selection issues with gamepad navigation, removed the old dev console script in favor of moving things to the module itself.


Registration of our school

Official website of the school: https://www.saintpaulsrajkot.org/
About the School's Academic Info: https://www.saintpaulsrajkot.org/page.php?pid=6
Thank You,

@Jay-Karia First stage of verification passed, official domain is saintpaulsrajkot.org as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

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


Missing character messages with TikZ

When mixing the current color . in TikZ environment produces messages such as these
Missing character: There is no ! in font nullfont!
Missing character: There is no 5 in font nullfont!
Missing character: There is no 0 in font nullfont!

in the log. When warnings are treated as errors, e.g., using latexmk -Werror, the above output will prevent the document to successfully compile.
I previously submitted the issue to the pgf bug tracker. However, it was quickly closed claiming the bug is caused by xcolor.
Minimal working example (MWE)

\documentclass[tikz]{standalone}

\begin{document}
\begin{tikzpicture}
  \draw[.!50] (0,0) -- (1,0);
\end{tikzpicture}
\end{document}

then inspect the log.

I was almost ready to say this is not supported syntax because it is not documented anywhere.  However, "Figure 7: Current color" of xcolor.pdf includes \textcolor{.!50}{50\%} as an example.
I agree the \XC@info test is faulty.  It is meant to detect the type of color and produce a number (0 for ., 1 for names like red, 2 or 3 for certain expressions).  However it seems the number is almost not used: only the case where it is 1 is used in the code that calls \XC@info.  Of course we cannot rely on that because other packages might use \XC@info.  I think the least invasive change is to replace the test by a corrected one, presumably tested after filtering out the cases of complicated expressions:
\def\XC@info#1#2%
 {\XC@edef#2{#1}%
  \expandafter\in@\expandafter>\expandafter{#2}%
  \ifin@\def#2{4}\else\expandafter\in@\expandafter:\expandafter{#2}%
  \ifin@\def#2{3}\else\expandafter\in@\expandafter!\expandafter{#2}%
  \ifin@\def#2{2}\else % now there's no >,:,!
  \if-\expandafter\@car#2\@nil\def#2{2}\else % catches -red
<EMAIL_ADDRESS>  \edef#2{\ifin@0\else1\fi}\fi\fi\fi\fi}

where I used \@car rather than the previous method to determine if the expression starts with -, and I applied that previous method to test for an argument being exactly ..  Hopefully I got the number of closing \fi right.  Can we please use expl3 when rewriting such pieces of LaTeX2e code?

Can we please use expl3 when rewriting such pieces of LaTeX2e code?

we can, but we have inherited this package a few weeks ago, it wasn't written by any of us.

@blefloch I just tried your code on a complicated plot and all the null font messages are gone ;-)

Can we please use expl3 when rewriting such pieces of LaTeX2e code?

I would have not problems  with
\ExplSyntaxOn
\cs_new_protected:Npn \XC@info ....

\ExplSyntaxOff

Can we please use expl3 when rewriting such pieces of LaTeX2e code?

we can, but we have inherited this package a few weeks ago, it wasn't
written by any of us.

oops, overlooked the "re", but yes overtime we should move things over
anyway

@blefloch  no objection to your code but are there cases other that the test for . that required the other re-arrangements?
a smaller change just fixing the \if. test might be
\def\XC@info#1#2%
 {\XC@edef#2{#1}%
  \if.\expandafter\@car#2\relax\@nil\def#2{0}\else\expandafter\in@\expandafter>\expandafter{#2}%
  \ifin@\def#2{4}\else\expandafter\in@\expandafter:\expandafter{#2}%
  \ifin@\def#2{3}\else\expandafter\in@\expandafter!\expandafter{#2}%
  \ifin@\def#2{2}\else\edef#2{\noexpand\in@{/-}{/#2}}#2%
  \edef#2{\ifin@2\else1\fi}\fi\fi\fi\fi}

down the line we probably want bigger changes (and in color) to interface better with l3color but keeping changes small (and in 2e style) until we are ready for that seem desirable to me at least.

The reason was that your code yields 0 for an expression such as .!50!red contrarily to the intent of that command, which seems to be to give larger numbers for more complicated expressions.  On the other hand \XC@info is only used in one place where the only value that is singled out is 1, so it doesn't actually matter.  I'll let you pick whichever code you like best.

@blefloch  oh of course yes I had that in mind at the start and then completely forgot:-) I wasn't sure what you meant by "presumably tested after filtering out the cases of complicated expressions:"  do you mean that the code as posted needs a filter adding or were you describing the code as written?

Yes, sorry, I wrote "presumably tested after filtering out the cases of complicated expressions:" then I figured it wasn't so trivial to write the code and I ended up writing the code.  So yest, it's just a description of the code I wrote.

This has been resolved in xcolor 2021/10/31 v2.13 and uploaded to ctan.


Fine-tuning on already fine tuned model stuck at "copying training files"

Dear Tommi and all,
I'm very excited about this development and the professional work involved with it! Thank you!
I have trained a Hungarian base model that I downloaded from the program.
I then decided to further fine-tune it with more TMX memory.
However when I start to load the next TMX, the progress is stuck at "Copying training files."
It never finishes that. If I close and reopen the program it says "Ok."
But it isn't ok for sure...
If I take the same TMX that bugs the already fine-tuned model and use it on the base mode, it is running.
I can't find error log or anything like that. Any idea or suggestion why this could be? I'm using the latest pre-release <IP_ADDRESS>. I also tried prior to that with the actual released version, same result.
Thank you.
Best Regards,
Charlie

Currently you can't fine-tune models that have already been fine-tuned. Unfortunately the user interface currently doesn't block it, it just hangs during the process. I should either make it possible to do repeated fine-tuning or to just remove the option. I'm not sure what repeated fine-tuning will do for model quality, it might degrade it eventually, that's why I'm a bit wary of it.


hidden-definition-finder.rb  `write_constants': Your source can't be read by Sorbet. (RuntimeError)

disclaimer: occurs in a kind of legacy project.
Gem versions:
sorbet (0.5.5784)
sorbet-rails (0.7.0)
Input
srb rbi update

Observed output
Generating /var/folders/v_/xmfm5zgd58j5l108ftb89s9r0000gn/T/d20201106-75025-ok2ri/reflection.rbi with 16579 modules and 264 aliases
Printing your code's symbol table into /var/folders/v_/xmfm5zgd58j5l108ftb89s9r0000gn/T/d20201106-75025-ok2ri/from-source.json
/Users/benja/.rvm/gems/ruby-2.4.10/gems/sorbet-0.5.5784/lib/hidden-definition-finder.rb:119:in `write_constants': Your source can't be read by Sorbet. (RuntimeError)
You can try `find . -type f | xargs -L 1 -t bundle exec srb tc --no-config --error-white-list 1000` and hopefully the last file it is processing before it dies is the culprit.
If not, maybe the errors in this file will help: /var/folders/v_/xmfm5zgd58j5l108ftb89s9r0000gn/T/d20201106-75025-ok2ri/from-source.json.err
        from /Users/benja/.rvm/gems/ruby-2.4.10/gems/sorbet-0.5.5784/lib/hidden-definition-finder.rb:47:in `main'
        from /Users/benja/.rvm/gems/ruby-2.4.10/gems/sorbet-0.5.5784/lib/hidden-definition-finder.rb:38:in `main'
        from /Users/benja/.rvm/gems/ruby-2.4.10/gems/sorbet-0.5.5784/bin/srb-rbi:232:in `block in make_step'
        from /Users/benja/.rvm/gems/ruby-2.4.10/gems/sorbet-0.5.5784/bin/srb-rbi:121:in `init'
        from /Users/benja/.rvm/gems/ruby-2.4.10/gems/sorbet-0.5.5784/bin/srb-rbi:196:in `main'
        from /Users/benja/.rvm/gems/ruby-2.4.10/gems/sorbet-0.5.5784/bin/srb-rbi:237:in `<main>'

Expected behavior
I expect the command finishes without breaking.
I was able to run this a few weeks ago, the only difference is I updated a few gems, but sorbet remained the same.

the error file has this content:
/Users/benja/.rvm/gems/ruby-2.4.10/gems/sorbet-0.5.5939/bin/srb: line 46: 42467 Segmentation fault: 11  "${sorbet}" "${args[@]}"

upgrading sorbet solved it


server: check learner regardless of whether learner enabled or not

Please add the description for this PR.

Please split into 2 PRs. The one checks learner peer, and the one add learner count gauge.

LGTM. PTAL @nolouch


fix: annotations

Description
This PR introduces a way to update service annotations.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[x] Refactor/improvement
[x] This change requires a documentation update

How Has This Been Tested?
Manual tests.
Checklist

[x] My commit message is conventional
[x] I have run pre-commit on all files before creating the PR
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I have checked my code and corrected any misspellings

Codecov Report

Merging #575 (0a818bd) into develop (de6b45a) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 0a818bd differs from pull request most recent head 0b48d31. Consider uploading reports for the commit 0b48d31 to get more accurate results

@@           Coverage Diff            @@
##           develop     #575   +/-   ##
========================================
  Coverage    86.72%   86.72%
========================================
  Files           25       25
  Lines         1590     1590
========================================
  Hits          1379     1379
  Misses         211      211

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

:tada: This PR is included in version 1.8.2-beta.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Make responders into GenServers

This change makes responders into isolated GenServers allowing responders to maintain/update state.
TODO

[ ] Update docs
[ ] More tests

Coverage decreased (-1.8%) to 83.708% when pulling 09728bc9e558cdf42509d97b136a7ed8794766ae on scrogson:refactor_responders into 5484ff6123561fa9bfafeb0a2a1ff963c225035e on hedwig-im:master.

Coverage decreased (-2.2%) to 83.24% when pulling 5201e1311aa97183130ba5a834a8c9801fcb9cff on scrogson:refactor_responders into 5484ff6123561fa9bfafeb0a2a1ff963c225035e on hedwig-im:master.

Coverage decreased (-2.2%) to 83.24% when pulling cda2e64e707bd8297a28de0a6c2afb676cd1ebc5 on scrogson:refactor_responders into 5484ff6123561fa9bfafeb0a2a1ff963c225035e on hedwig-im:master.

Coverage decreased (-2.2%) to 83.24% when pulling ca41e0bb64794e48a4542565c367609b03f250c1 on scrogson:refactor_responders into 5484ff6123561fa9bfafeb0a2a1ff963c225035e on hedwig-im:master.

Coverage decreased (-2.2%) to 83.24% when pulling f04574c17e0f65c4e23826ffdd875f629d01ab38 on scrogson:refactor_responders into 5484ff6123561fa9bfafeb0a2a1ff963c225035e on hedwig-im:master.

Coverage increased (+7.2%) to 92.67% when pulling 4cb98a39bbfa44683def9e852c439c9ec0019e51 on scrogson:refactor_responders into 5484ff6123561fa9bfafeb0a2a1ff963c225035e on hedwig-im:master.

Coverage increased (+7.2%) to 92.67% when pulling 7437aa0364c36a4a738e759bc6ae0aaaf253a1f1 on scrogson:refactor_responders into 5484ff6123561fa9bfafeb0a2a1ff963c225035e on hedwig-im:master.

Coverage increased (+6.5%) to 92.021% when pulling b256a163a39058666efa65a5436252261b1b78b3 on scrogson:refactor_responders into 5484ff6123561fa9bfafeb0a2a1ff963c225035e on hedwig-im:master.


Upgrade to Solr 4.9.1 and Jetty 8

This move Chef Server onto the latest version of Solr, which includes
Jetty 8 rather than Jetty 6.

Passing wilson build: http://wilson.ci.chef.co/job/chef-server-12-trigger-ad_hoc/500/downstreambuildview/
Per https://github.com/chef/chef-server/issues/180 Jetty 8 is still old and we need to move to Jetty 9 eventually. I'm taking a look at the changes needed to do that, but since moving to 8 appears to be a drop-in upgrade, I figured it was worth getting closer to correct in the near term.
cc @chef/lob

@chef/lob I've also tested an 11->12 solr->solr4 migration manually.


Feature Request - iOS Support

There are no Zebra printer Cordova plugins out there with both Android and iOS support. It would be great to have 1 plugin for both platforms. I developed an @getcapacitor plugin for iOS and Andorid with a nearly identical interface as yours, and would like to migrate it to Cordova. Rather than create yet another zebra plugin, it would be better to migrate the iOS platform into this one. If you are interested in having iOS added to this plugin i'll send you a pull request.

I don't really use this plugin anymore and only left it up in case someone else might need it.
I'd be fine with taking a pull request.  I cannot offer general support though.

Actually, if you want to take ownership of this plugin - I would be fine with transferring ownership of this repository.


Dependencies that usually are dev deps are problematic.

Usually one has the likes of isort, and black in dev dependencies with close to little care which versions those are on. Codegen having those in main deps enforce specific versions of these. If those are used to post-process the generated code - which would make them truly main deps then maybe that post-process feature should be a plugin? At the very least I propose unlocking the post-processors to a "*" version.
This is safe as I can't imagine you relly on the output of the linters/formaters, right?

We actually run those on generated code as final step ☠


examples: switch to adjoint time derivative

Switch time derivative positon for the gradient as discussed on slack
tests pas locally so should be green.

Since this has implications on GPU+data streaming, we should wait for #1702 to land first, which also "fixes" the current mismatching tag issue that is causing the omp offloading job to get scheduled to wampa rather than kimogila

sure

Merged, thanks


Dict is not implemented

Reproducible code:
> erg examples/dict.er

Result:
thread 'main' panicked at 'not yet implemented', C:\Users\sbym8\.cargo\registry\src\github.com-1ecc6299db9ec823\erg_parser-0.2.4\parse.rs:1425:17
stack backtrace:
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

It is not a proper error, but a panic. At least, this needs to be fixed.

I assume any code level contribution needs Rust proficiency, right?

Basically, yes. I use advanced and modern features of Rust in several pieces of code.
However, I believe that formatting the code using cargo fmt or clippy, for example, can be done by someone who is not very familiar with Rust. I have neglected to do this and would be very grateful if you could do it for me.
And I'm planning on making the error messages multilingual. This will be open to anyone who speaks any language other than English.

However, I believe that formatting the code using cargo fmt or clippy, for example, can be done by someone who is not very familiar with Rust. I have neglected to do this and would be very grateful if you could do it for me.

Would you like this to be set-up as a pre-commit config? Something like this
repos:
  - repo: local
    hooks:
      - id: rustfmt
        name: rustfmt
        description: Check if all files follow the rustfmt style
        entry: cargo fmt --all -- --check --color always
        language: system
        pass_filenames: false

It looks good. I will adopt later.

This issue itself probably requires an understanding of the Rust language and an overall understanding of the Erg source code.
I will put up an explanation of the Erg source code later in the doc.


add first draft comfy api example

Basically modal app version of the comfyUI websockets example.
This passes a comfy workflow json to a running comfyUI server, queues a job, and fetches the image outputs of that job via API.
Chatted with @thundergolfer on how this could be expanded into a more standalone example:

Put a simple frontend (like this example) that allows a user to adjust the editable parts of a comfyui json workflow (e.g. text prompts).
Use this code as a starting point web endpoint to handle those requests and create the workflow json, spin up a "headless" comfyui server, and return the output

Other thoughts:

fal.ai allows you to pass urls of models
how would people adapt this if their workflow included plugins?

Superseded by https://github.com/modal-labs/modal-examples/pull/628


Misleading docs/error message for gefyra up --endpoint

There are a few small shortcomings we encountered when getting started with gefyra.

It would probably make sense to include a "Getting started" guide for a generic, remote cluster that is not vendor specific. No need to document what's needed in order to setup kubectl, just start from where kubectl is working and all that's need is something in the line of:

gefyra up --endpoint <IP_ADDRESS>:31820
gefyra run -i myorg/dataserver-web -N dataserver-web -n dataserver --env-from deployment/lab-dataserver-web
gefyra bridge -N dataserver-web -C dataserver-web -n dataserver -p 8000:8000 -I dataserver-bridge --deployment lab-dataserver-web

The gefyra up --endpoint flag is not well document and implemented IMO. a) It should allow to just pass the IP of the cluster and just use the default port 31820, currently this is not accepted. Would be a handy feature. b) Because of the wording in the docs "The Wireguard endpoint in the form IP:Port for Gefyra to connect to", one can be misguided to look at the kubeconfig and use the port specified there, in our case 6443.

The wording of the error message is misleading, "that the [kubernetes cluster] can reach Kubenetes port 31820 from this machine". That makes no sense at all.

[ERROR] Gefyra could not successfully confirm the Wireguard connection working. Please make sure you are using the --endpoint argument for remote clusters and that <IP_ADDRESS>:6443 can reach Kubernetes node port 31820 from this machine. Please check your firewall settings, too. If you are running a local Minikube cluster, please use the 'gefyra up --minikube' flag.

Things should be mostly addressed. Generic getting started is in the works (https://github.com/gefyrahq/gefyrahq.github.io/issues/40)


ANGULAR: Phylogeny. Seeing negative branches

Please see input file I used- It's a NWK tree, can be found at this link
https://cdc.sharepoint.com/:f:/r/teams/nchhstp-dhap-lb-microbetrace/Shared Documents/General/Files for bug reports?csf=1&web=1&e=0SGxGE

I'm not seeing a negative branch length for cdcgov or mossy426 - this is what I'm seeing (with distance labels enabled)

I am talking about the two branches that extend to the left of the node. That is not correct. And even the rest of branches look different from how they look if I open this nwk file in a different tree viewer like MEGA (I sent a detailed email about that)


Permissions no longer available

In Step 2 Office 365 Exchange Online is no longer provided as an option and consequently Exchange.ManageAsApp can not be selected/added.

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

ID: d2cfafdf-cbe9-2ffe-eabe-becc66d51728
Version Independent ID: 4a46c8a8-dc70-d877-271e-6679c465a6d5
Content: App-only authentication
Content Source: exchange/docs-conceptual/app-only-auth-powershell-v2.md
Service: exchange-online
GitHub Login: @chrisda
Microsoft Alias: chrisda

@trentcioran, are you saying that step 2 in Step 2 where you enter the GUID value on the Manifest page no longer works?
"requiredResourceAccess": [
   {
      "resourceAppId": "00000002-0000-0ff1-ce00-000000000000",
      "resourceAccess": [
         {
            "id": "dc50a0fb-09a3-484d-be87-e023b12c6440",
            "type": "Role"
         }
      ]
   }
],

Hi @chrisda ,
No, what I was pointing out is that when adding permissions you are indicated to select Office 365 Online and then add the permission Exchange.ManageAsApp, but Office 365 Online is no longer an option available in the Request API permissions selection APIs, not even shown in the legacy APIs so either it is no longer possible (making this document invalid) or the name of the API changed and the document needs update.

@trentcioran, the topic was rewritten to account for the fact that you can't select Exchange.ManageAsApp in the UI anymore. Known issue.
Are you talking about the reference in step 2 in the Set up app-only authentication section?
The title and link of that step is: Assign Exchange Online API permissions to the application.
Once you click the link, all of the information in that target section should be correct.
The text below the link title says:

An application object has the default permission User.Read. For the application object to access Exchange Online resources, it needs to have the Application permission Exchange.ManageAsApp.

That is effectively what you are doing in Step 2: Assign Exchange Online API permissions to the application.
I can find no text in the topic that says, "select Office 365 Online" or "add the Exchange.ManageAsApp permission".
If you configure the Manifest pages as described, it should add everything for you.

Thank you! that made it. Sorry for letting this without response for so long.


php: generated class name is case unmatched

protoc --version: libprotoc 3.2.0
test proto:
syntax = "proto3";

package rpc.v1;

service svc {
  rpc test (requestMessage) returns (responseMessage) {}
}

message requestMessage {
  string field = 1;
}

message responseMessage {
  string field = 1;
}

protoc --php_out=. --grpc_out=. output:
└── Rpc
    └── V1
        ├── requestMessage.php
        ├── responseMessage.php
        └── svcClient.php

However,  svcClient requires \Rpc\V1\RequestMessage and \Rpc\V1\ResponseMessage

The upper case is converted by the grpc plugin.
I think this is because the protobuf style guide recommends use CamelCase for the message name.

And also, the psr coding style also suggests using CamelCase to define the class name.