Error level warning is inconsistent

When a rule has error level warning, stricter will pass silently CI, but it will still output errors in junit reporter, which will might fail the build.
In non-console reporters we should not output warnings - only errors.

Fixed in 0.3.1.


bump FluentBit version to 2.0.0 - Fix CVE-2024-4323

bumped FluentBit version to 2.0.0 (which includes fluentbit 3.0.4) to fix CVE-2024-4323
Additional information about the CVE can be found here: https://fluentbit.io/blog/2024/05/21/statement-on-cve-2024-4323-and-its-fix/

 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.

Hello @simonhoellein,
We truly appreciate the effort you've put into submitting this PR.
As specified in CVE-2024-4323:

Memory corruption vulnerability has been found in Fluent Bit versions 2.0.7 through 3.0.3.

Given that the FluentBit version for Windows currently pinned is 1.9.3, the identified vulnerability doesn’t impact our infra agent.
The New Relic team supporting FluentBit is currently evaluating the merits of upgrading the FluentBit version for Windows. However, we are unable to commit to a definitive timeline for this yet. When deciding to address a problem, we consider various factors such as the nature of the problem, its impact on customers, and the needed development effort.
To take your feature request further, we suggest filing a Feature Request (FR). When submitting your FR, please reference this GitHub issue.
Thank you!

Hello @davidgit
This may be true for the windows release but the Linux one uses the NewRelic FluentBit version 1.19.1 which is equal to the FluentBit version 2.2.0 (which is impacted by the CVE).
Please reconsider this PR


chore: 0.10.2 proposal

Holding for #1383
Draft release: https://github.com/open-telemetry/opentelemetry-js/releases/tag/untagged-4c048f5a61ba62d33385
Releasing soon after another release because @ramya-rao-a has needs for the es5 target PR that is to be included in this release.

imho number of files are too low

imho number of files is too low

was thinking the same. The version.ts files aren't updated.
I am fixing this now, but it is worth mentioning that when you run lerna publish, it runs compile again, which bumps the version.ts files. So it is actually impossible to forget them. But I will fix it for the PR.

Thank you!


Enable retrieving the selection tree of a document or a range of code

Currently LSP contains the textDocument/selectionRange method which allows retrieving one path inside the selection tree of the document. The LSP client I'm working on wants to use the entire selection tree of the document. This tree can be constructed using the textDocument/selectionRange method but this has a high bandwidth overhead since a lot of duplicate data is returned.
Here are my use-cases for constructing a selection tree:

For the "expand selection range" feature of IDEs, which allows developers to quickly select a particular piece of code, a low latency is critical, otherwise developers would be better off making the selection manually. For remote IDEs with a high latency to the development environment, calling textDocument/selectionRange can be too slow. Retrieving the selection tree of a range of code allows resolving "expand selection range" requests from the user with cached data.
Apart from "expand selection range", the selection tree can be used for other forms of navigation such as "jump to previous/next sibling" to hop between functions, function call arguments,  statements, etc.
The selection tree can help the developer understand the code, and can be visualised in a separate outline panel or using decorations in the editor.

Currently the textDocument/documentSymbol method already enables retrieving a hierarchy of document ranges, but only for named ranges. I propose to change DocumentSymbolParams to:
export interface DocumentSymbolParams extends WorkDoneProgressParams,
	PartialResultParams {
	/**
	 * The text document.
	 */
	textDocument: TextDocumentIdentifier;

        /**
        * Whether to include symbols without a name in the hierarchy
        */
        includeAnonymousSymbols: boolean,

       /**
        * The range of the document for which to retrieve symbols
        */
       range?: Range
}

And to change DocumentSymbol to:
export interface Symbol {
	/**
	 * The range enclosing this symbol not including leading/trailing whitespace
	 * but everything else like comments. This information is typically used to
	 * determine if the clients cursor is inside the symbol to reveal in the
	 * symbol in the UI.
	 */
	range: Range;

	/**
	 * Children of this symbol, e.g. properties of a class.
	 */
	children?: Symbol[];
}

export interface DocumentSymbol extends Symbol {

	/**
	 * The name of this symbol. Will be displayed in the user interface and
	 * therefore must not be an empty string or a string only consisting of
	 * white spaces.
	 */
	name: string;

	/**
	 * More detail for this symbol, e.g the signature of a function.
	 */
	detail?: string;

	/**
	 * The kind of this symbol.
	 */
	kind: SymbolKind;

	/**
	 * Tags for this document symbol.
	 *
	 * @since 3.16.0
	 */
	tags?: SymbolTag[];

	/**
	 * Indicates if this symbol is deprecated.
	 *
	 * @deprecated Use tags instead
	 */
	deprecated?: boolean;

	/**
	 * The range that should be selected and revealed when this symbol is being
	 * picked, e.g. the name of a function. Must be contained by the `range`.
	 */
	selectionRange: Range;

	/**
	 * Children of this symbol, e.g. properties of a class.
	 */
	children?: DocumentSymbol[];
}

A positive side-effect of this change is that since textDocument/documentSymbol request now includes a range parameter, when a document changes, it can be invoked on only the part of the document that has changed.
I'd be happy to create a PR for this change if some agreement on the design can be reached.

How do you reconcile this on the client if the user types in a file?

How do you reconcile this on the client if the user types in a file?

Good question. On further thought, I think with the changes I proposed, it's not possible to do this in an incremental way.
For example, given the JSON blob [ [ [ 1 ], 2 ], 3 ], removing the first ] might trigger the parser's error correction to fix the missing ] by appending one at the end, so it parses [ [ [ 1 , 2 ], 3 ] ], which changes the entire structure of the tree. The removed ] was nested several levels deep into the tree and the client has no way of knowing that the entire tree must be rebuilt.
One question I have, does the current textDocument/documentSymbol not lead to problems for large files? Looking at the SymbolKind enum
export namespace SymbolKind {
	export const File = 1;
	export const Module = 2;
	export const Namespace = 3;
	export const Package = 4;
	export const Class = 5;
	export const Method = 6;
	export const Property = 7;
	export const Field = 8;
	export const Constructor = 9;
	export const Enum = 10;
	export const Interface = 11;
	export const Function = 12;
	export const Variable = 13;
	export const Constant = 14;
	export const String = 15;
	export const Number = 16;
	export const Boolean = 17;
	export const Array = 18;
	export const Object = 19;
	export const Key = 20;
	export const Null = 21;
	export const EnumMember = 22;
	export const Struct = 23;
	export const Event = 24;
	export const Operator = 25;
	export const TypeParameter = 26;
}

It seems quite a large part of the document could be returned by a textDocument/documentSymbol request. However, given that DocumentSymbol also has a name: string field, I'm also confused as to which symbols should be returned as part of the current request. Should only named symbols, things that could be considered a 'definition', be returned?
I think to enable incrementally updating the symbol tree, the server must support sending edits of this tree, where an edit could be:
export interface SymbolTreeDelta {
	readonly resultId?: string;
	/**
	 * The symbol edits to transform a previous result into a new
	 * result.
	 */
	edits: SymbolTreeEdit[];
}

interface SymbolTreeEdit {
  nodeRangeBeforeEdit: Range,
  newNode: Symbol
}

This is similar to textDocument/semanticTokens/full/delta, except the positions are absolute not relative.
Do you have any thoughts on the feasibility on making a change that enables having a synchronised symbol tree on the client?
Regards

To support incremental updates on this the data structure need to change. Simple edits don't help since the current format uses absolute positions and to have a nice incremental story you need to use relative position encoding as we do with semantic tokens now.

Simple edits don't help since the current format uses absolute positions and to have a nice incremental story you need to use relative position encoding as we do with semantic tokens now.

Can you share something about what assumptions LSP makes about how the client and server store their text buffers and positions?
I imagine the TextBuffer is a balanced binary tree such as described here.
To efficiently update Positions in for example the AST stored on the server side, when a text change occurs, I would imagine having the Positions be part of the TextBuffer, where a Position contains a reference to a Node in the TextBuffer tree and an offset relative to the start of that Node. Each Node stores which Positions are pointing to it and can re-assign the positions to a different Node if the original one is split or removed.
If clients and servers store positions according to the above, does it still matter whether LSP communicates relative or absolute positions, and whether it communicates offset or line/column based positions?

LSP doesn't enforce any kind of implementation of a text buffer. All it defines is that positions are based on a UTF16 encoding.
The data to be transferred is IMO independent of the implementation used. If you have absolute positions and introduce a new line at the beginning the whole selection tree will change since all its position will change.


[backport] Fix type of return value of fused function

Backport of #1349

Jenkins CI test (for commit dbc68a92a642cb1176514a4300b0a8855cd680c1, target branch v4) succeeded!

LGTM.


Diffsinger Onnx Error

Acknowledgement

[X] I have read Getting-Started and FAQ

🐛 Describe the bug
An error occurred when using Diffsinger's ONNX Variance function
No error occurred when converting Torch version 1.13 to Onnx.
This time I used Torch 2.2 and got an Onnx error.
Have the model parameters themselves changed?
The version of Torch currently used for both SOME and SOFA is 2.2.
Thank you for your improvement.
Explains how to reproduce the bug
Errors Onnx　Pitch、Duration、linguistic
Variance
OS & Version
Windows10-11
Logs
Failed to run editing macro
[ErrorCode:RuntimeException] Non-zero status code returned while running Reshape node. Name:'/encoder/layers.0/op/self_attn/Reshape_4' Status Message:
Microsoft.ML.OnnxRuntime.OnnxRuntimeException: [ErrorCode:RuntimeException] Non-zero status code returned while running Reshape node. Name:'/encoder/layers.0/op/self_attn/Reshape_4' Status Message:
at Microsoft.ML.OnnxRuntime.NativeApiStatus.VerifySuccess(IntPtr nativeStatus)
at Microsoft.ML.OnnxRuntime.InferenceSession.RunImpl(RunOptions options, IntPtr[] inputNames, IntPtr[] inputValues, IntPtr[] outputNames, DisposableList1 cleanupList)    at Microsoft.ML.OnnxRuntime.InferenceSession.Run(IReadOnlyCollection1 inputs, IReadOnlyCollection1 outputNames, RunOptions options)    at Microsoft.ML.OnnxRuntime.InferenceSession.Run(IReadOnlyCollection1 inputs, IReadOnlyCollection1 outputNames)    at Microsoft.ML.OnnxRuntime.InferenceSession.Run(IReadOnlyCollection1 inputs)
at OpenUtau.Core.DiffSinger.DsPitch.Process(RenderPhrase phrase) in C:\projects\openutau\OpenUtau.Core\DiffSinger\DiffSingerPitch.cs:line 126
at OpenUtau.Core.DiffSinger.DiffSingerRenderer.LoadRenderedPitch(RenderPhrase phrase) in C:\projects\openutau\OpenUtau.Core\DiffSinger\DiffSingerRenderer.cs:line 304
at OpenUtau.Core.Editing.LoadRenderedPitch.Run(UProject project, UVoicePart part, List`1 selectedNotes, DocManager docManager) in C:\projects\openutau\OpenUtau.Core\Editing\NoteBatchEdits.cs:line 464
at OpenUtau.App.ViewModels.PianoRollViewModel.<.ctor>b__94_10(BatchEdit edit) in C:\projects\openutau\OpenUtau\ViewModels\PianoRollViewModel.cs:line 167

CPU　Ver
Failed to run editing macro
[ErrorCode:RuntimeException] Non-zero status code returned while running Reshape node. Name:'/encoder/layers.0/op/self_attn/Reshape_4' Status Message: D:\a_work\1\s\onnxruntime\core\providers\cpu\tensor\reshape_helper.h:41 onnxruntime::ReshapeHelper::ReshapeHelper gsl::narrow_cast<int64_t>(input_shape.Size()) == size was false. The input tensor cannot be reshaped to the requested shape. Input shape:{3,1,128}, requested shape:{5,2,64}
Microsoft.ML.OnnxRuntime.OnnxRuntimeException: [ErrorCode:RuntimeException] Non-zero status code returned while running Reshape node. Name:'/encoder/layers.0/op/self_attn/Reshape_4' Status Message: D:\a_work\1\s\onnxruntime\core\providers\cpu\tensor\reshape_helper.h:41 onnxruntime::ReshapeHelper::ReshapeHelper gsl::narrow_cast<int64_t>(input_shape.Size()) == size was false. The input tensor cannot be reshaped to the requested shape. Input shape:{3,1,128}, requested shape:{5,2,64}
at Microsoft.ML.OnnxRuntime.NativeApiStatus.VerifySuccess(IntPtr nativeStatus)
at Microsoft.ML.OnnxRuntime.InferenceSession.RunImpl(RunOptions options, IntPtr[] inputNames, IntPtr[] inputValues, IntPtr[] outputNames, DisposableList1 cleanupList)    at Microsoft.ML.OnnxRuntime.InferenceSession.Run(IReadOnlyCollection1 inputs, IReadOnlyCollection1 outputNames, RunOptions options)    at Microsoft.ML.OnnxRuntime.InferenceSession.Run(IReadOnlyCollection1 inputs, IReadOnlyCollection1 outputNames)    at Microsoft.ML.OnnxRuntime.InferenceSession.Run(IReadOnlyCollection1 inputs)
at OpenUtau.Core.DiffSinger.DsPitch.Process(RenderPhrase phrase) in C:\projects\openutau\OpenUtau.Core\DiffSinger\DiffSingerPitch.cs:line 126
at OpenUtau.Core.DiffSinger.DiffSingerRenderer.LoadRenderedPitch(RenderPhrase phrase) in C:\projects\openutau\OpenUtau.Core\DiffSinger\DiffSingerRenderer.cs:line 304
at OpenUtau.Core.Editing.LoadRenderedPitch.Run(UProject project, UVoicePart part, List`1 selectedNotes, DocManager docManager) in C:\projects\openutau\OpenUtau.Core\Editing\NoteBatchEdits.cs:line 464
at OpenUtau.App.ViewModels.PianoRollViewModel.<.ctor>b__94_10(BatchEdit edit) in C:\projects\openutau\OpenUtau\ViewModels\PianoRollViewModel.cs:line 167
0.1.384.0


yara: 4.4.0 -> 4.5.0

Changes: https://github.com/VirusTotal/yara/releases/tag/v4.5.0
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Rebased to pull in musl patch PR and drop it as it's already included into 4.5.0.


reserve @rend and @style for CSS-like renditional information

From<EMAIL_ADDRESS>on February 21, 2013 16:05:39
Current @rend and @style attributes other than those on the <rend> element should be renamed in order to clear the path for generic @rend and @style attributes than can be applied to more elements (not global, but common). @rend will be used to record visual characteristics of the input document, while @style will be used to specify visual characteristics of potential output. CSS may be used in both attributes.  @altrend will allow user-defined values; that is, ones not permitted by @-rend or CSS.
Original issue: http://code.google.com/p/music-encoding/issues/detail?id=144

From<EMAIL_ADDRESS>on December 10, 2014 12:10:18
<desc> for del/@rend should be modified thus:
"contains an indication of how the deletion is rendered in the source document."
del/@rend may be restricted to a subset of the values provided by rend/@rend.  Or not.  :-)

related task: move attributes in att.beamrend to att.beam.vis and eliminate att.beamrend.


CORS blocked by browser. API doesn't return CORS related headers.

Same here. Can't GET the API with Axios locally

Allow your localhost to access origins outside

How would one go about doing that @AlexFlipnote?

https://medium.com/swlh/avoiding-cors-errors-on-localhost-in-2020-5a656ed8cefa


Enable static compiler with sample

This change hooks the static compiler back up. As part of this, a separate sample project has been added. However, this uses the same assets as the other one, just sets the project file up slightly differently to statically compile rather than dynamically.

Blocked by #99 and #100

taking a look


Integrate grafana into docker stack

Grafana is currently only setup to run using a manager node. This is very restrictive and will not work on certain setups. In an effort to support systems without a management node, docker support should be added.


proto: correct go_package of contrib

Commit Message: proto: correct go_package of contrib
Additional Description:
This fixes up the go_package descriptor on contrib/ protos. I am not sure how the bazel protoc stuff works, but standard proto compiler seems trip up on this being incorrect, and generate invalid imports
Risk Level: Low
Testing: Manual
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

There's a proto validator that probably needs to be updated. Otherwise, LGTM.

There's a proto validator that probably needs to be updated. Otherwise, LGTM.

Thanks, found it and updated it

Not quite:
-    options.go_package = "".join([
-        "github.com/envoyproxy/go-control-plane/", golang_package_base, golang_package_name])
+    options.go_package = "".join(
+        ["github.com/envoyproxy/go-control-plane/", golang_package_base, golang_package_name])

["github.com/envoyproxy/go-control-plane/", golang_package_base, golang_package_name])

Thanks! I am a bit slow :slightly_smiling_face:


UI Enhancement: Character Page Styling and Pagination

Overview
This PR implements pagination functionality for the character listing page and enhances the UI with responsive styling and animations.
Changes Made
Pagination

Add page navigation controls
Handle API pagination response
Extract and format page numbers from API URLs
Implement error handling for pagination requests

Styling

Add responsive grid layout for character cards
Implement hover effects and transitions
Add loading animations
Style pagination controls
Set up static file serving for CSS/JS assets

Template Updates

Update index.html with new style classes
Add pagination navigation elements
Include CSS and JS file references

Testing

[x] Tested pagination navigation across multiple pages
[x] Verified responsive design on different screen sizes
[x] Confirmed animations work across different browsers
[x] Validated static file serving

Excellent documentation.


BACKLOG-21889 Improve performance of TextFileOutput step when using s…

@rmansoor

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -Dsurefire.runOrder=alphabetical -B -fn -f 'pom.xml' -pl 'engine' -P '!assemblies' -amd clean install && mvn -B -f 'pom.xml' -pl 'engine' -P '!assemblies' -amd site

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'engine' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  engine/src/main/java/org/pentaho/di/trans/steps/textfileoutput/TextFileOutput.java
  engine/src/main/java/org/pentaho/di/trans/steps/textfileoutput/TextFileOutputData.java
  engine/src/test/java/org/pentaho/di/trans/steps/textfileoutput/TextFileOutputTest.java

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes: +15.7% (click to expand)
:new: org.pentaho.di.trans.steps.textfileoutput.TextFileOutputData

Branch Coverage: 75% :exclamation:

:new: org.pentaho.di.trans.steps.textfileoutput.TextFileOutputData.FileStream

Branch Coverage: 25% :exclamation:
Complexity Coverage: 75% :exclamation:

:new: org.pentaho.di.trans.steps.textfileoutput.TextFileOutputData.FileStreamsList

Coverage: 0% :exclamation:


v1.12.0 is somehow missing OPT4048::D65_Illuminant ?

After loading the OPT4048 by RetroSpy Technnologies, version 1.12 in my Arduino IDE 2.2.1 I cannot compile the provided example code, because it reports missing OPT4048::D65_Illuminant although that does appear on line 282 of https://github.com/retrospy/OPT4048/blob/main/src/OPT4048.h
For what it's worth I'm using a Pi Pico, not any Teensy product at the moment.
C:\Users\beale\AppData\Local\Temp\arduino\sketches\49DDEE2FAEB092E94E301BE1D35BF515\libraries\OPT4048\OPT4048.cpp.o: In function `OPT4048::ConvertXYZtoRGB(OPT4048_XYZ)':
c:\Users\beale\Documents\Arduino\libraries\OPT4048\src/OPT4048.cpp:302: undefined reference to `OPT4048::D65_Illuminant'
c:\Users\beale\Documents\Arduino\libraries\OPT4048\src/OPT4048.cpp:302: undefined reference to `OPT4048::XYZ_to_RGB'
collect2.exe: error: ld returned 1 exit status

For what it's worth, it does compile and work OK if I move the D65_Illuminant and XYZ_to_RGB[][] inside the function in the '#else' clause of the #if defined(CORE_TEENSY), as shown:
OPT4048_RGB OPT4048::ConvertXYZtoRGB(OPT4048_XYZ xyz)
{
	static constexpr OPT4048_XYZ D65_Illuminant = { 95.0500, 100.0000, 108.9000, NAN };
	static constexpr float XYZ_to_RGB[3][3] = { {  3.2404542, -1.5371385, -0.4985314 },
						{ -0.9692660,  1.8760108,  0.0415560 },
						{  0.0556434, -0.2040259,  1.0572252 }
	};
	return ConvertXYZtoRGB(xyz, XYZ_to_RGB, D65_Illuminant, &OPT4048::sRGBCompandingFunction);
}

Let me take a look.  I am not sure I tried it with a Pi Pico.  Thanks for letting me know.

Thanks. I am using Arduino Mbed OS RP2040 boards (Raspberry Pi Pico) https://github.com/arduino/ArduinoCore-mbed
I guess some people also use a different toolchain for Pico, like https://github.com/earlephilhower/arduino-pico but I have not tried that.

This should be fixed in 1.13, which will take a little while to propagate out to the world


PR validation build

When a PR is created then there is a check if the PR builds, and passes the tests

Closed with: 3d3d0f234711193f36e3b0bc4429eff03841c6f3


FS-1671

What does this PR implement/change/remove?
Support for X13 inventory and X13 BIOS/BMC Firmware update
New example for firmware upload and firmware install uploaded

Please add a better title to the PR :rofl:

Is this work compatible with https://github.com/bmc-toolbox/bmclib/pull/394 ?

Is this work compatible with bmc-toolbox#394 ?

@ofaurax
This work will replace that work.


form bot fixes

Proposed changes:

...

Status (please check what you already did):

[ ] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog (please check changelog for instructions)
[ ] reformat files using black (please check Readme for instructions)

test_end_to_evaluation_with_forms is still failing at this point

Train endpoint is wrapped up. Do you want to wrap it up @akelad or should I?

@wochinge do you have time to? I probably won't this week

Will do 👍

@akelad Do you have time for a review tomorrow?

@melindaloubser1 Would you have time for a review? Akela won't get to it until tomorrow.

reviewing now

sorry! 😶


testnet network not found error.

after calling ./scripts/init-rd-sram.sh and init-oc-opencloudmesh.sh  I am facing with this error on calling ./scripts/oc-opencloudmesh-testing.sh

docker: Error response from daemon: network testnet not found.

it seems the testnet network is not created on previous commands.

Has been fixed for a while.


queue based stream

This is to address the concerns in #15 and #18. I believe it might fix the issues in #13. This will supersede the feature/thread #16 PR.

@adamkaplan is any of this still valuable that can be merged in master?

Yeah..... lot of great stuff in there actually. But it still fails the Autobahn high-performance tests. I haven't had time to fix it and probably won't for quite a while.
It hurts to leave this incomplete for so long :cry:


Should "layer_steps" change with the size of input?

Hi, I have a question of evaluation the ssd300 using different size of images
The layer_steps=[8, 16, 32, 64, 100, 300]
and the layers_shapes = [(38, 38), (19, 19), (10, 10), (5, 5), (3, 3), (1, 1)],
when using the input size 300.
When I evaluate a new image with size 512, the layers_shapes will be
[(64, 64), (32,32), (16, 16), (8, 8), (6, 6), (4, 4)]. Should the "layer_steps" be [8, 16, 32, 64, 85.3, 128]?

@ZhenyF layer_steps is same for any size of input, while the feat_shape is fixed when given the the input shape

Many thanks for  the reply!
I can understand that the "layers_shapes" is changed with the input size but why the "layers_steps" is fixed for any input size?

@ZhenyF is is determined by the downsampled strides compared to input image

For the last two of feature layers, feature map is reduced using "VALID" padding with stride = 1. When the input is 300, the sizes of the last two feature map will be (3,3) and (1,1), so the layer steps are 300/3=100 and 300/1 = 300 respectively.
However, when the input size is 512, the sizes of the last two feature map will be (6,6) and (4,4), so why the layer steps are not changed rather than 512/6=85.3 and 512/4 = 128 respectively?

@ZhenyF R-CNN minus R

@ZhenyF check https://github.com/HiKapok/SSD.TensorFlow/pull/113/commits/1f4fc8a36beeb936cea462b1b151666ad851f75a

@jamiechoi1995 and image size 256?


Unable to rename "Sub Environment" in "Manage Environments"

Expected Behavior
Within "Manage Environments" I should be able to change the name of a "Sub Environment".
Actual Behavior
Unable to change the name.
Reproduction Steps
https://github.com/Kong/insomnia/assets/1020551/6ba24ea7-1ba6-445d-8934-ce00c6163b3e
Is there an existing issue for this?

[X] I have searched the issue tracker for this problem.

Additional Information
No response
Insomnia Version
2023.4.0
What operating system are you using?
macOS
Operating System Version
13.4.1 (22F82)
Installation method
Download from website
Last Known Working Insomnia version
?

I believe this commit fixes the issue (as well as the issue of not being able to go between Base Environment and the same sub environment).  I'm unable to test it, however, as the latest code doesn't want to run on my machine due to several "Extension Errors".
https://github.com/Kong/insomnia/commit/eaece7c8636bb887ff18a28b531deb4df2805a46

I'm getting this problem on the same operating system. Using an M1 if that matters. It completely freezes the app, so you have to force quit.

Have the same issue

@wilsonpage @ethancdaniel @TearsOfFears
Double click on the Environment title

Thx)))

@wilsonpage @ethancdaniel @TearsOfFears
Double click on the Environment title

Oh wow, thanks! This definitely changed and is now inconsistent with the rest of Insomnia renaming UX.


Fix the logger

The oslo_log module needs to be registered before we parse any arguments in order to work.

Fixed with https://github.com/micumatei/asciipic/commit/9769a355d6462f23be3e1657152bb7147987f9ff


⚠ Bofrost.at has degraded performance

In f2b6a67, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1276 ms

Resolved: Bofrost.at performance has improved in 6ea2591.


Integrating with outlines

I'd love to use ctransformers with the outlines library for constrained generation. I opened this issue  about it on their repo.
In order to hack away at this integration, the forward pass and pure logit output of the model would need to be exposed in the ctransformers API -- having looked through ctransformers/llm.py it seems as though the .sample method which wraps the .ctransformers_llm_sample method from the C API is the only way to sample tokens from the ctransformers models in it's current state.
Would there be any scope for adding a .forward or .sample_logits method? How would I go about implementing it if there were?

You can get the logits using llm.logits property. In order to implement forward, you can use the low-level llm.eval() method.
I have done some work on this in the past to make ctransformers a drop-in replacement for 🤗 transformers models (see https://github.com/marella/ctransformers/issues/13#issuecomment-1597662836) Here is the code for reference.
Recently I created a better version of it but haven't pushed it yet. Here is a sample code from the newer version:
import torch
from transformers import PretrainedConfig, PreTrainedModel
from transformers.modeling_outputs import CausalLMOutput

class Model(PreTrainedModel):
    def __init__(self, config: PretrainedConfig, llm):
        config.vocab_size = llm.vocab_size
        config.eos_token_id = llm.eos_token_id
        config.pad_token_id = llm.eos_token_id
        super().__init__(config)
        self._llm = llm
        self._past = []

    def prepare_inputs_for_generation(
        self,
        input_ids,
        attention_mask=None,
        **kwargs,
    ):
        return {"input_ids": input_ids}

    def forward(
        self,
        input_ids=None,
        return_dict=None,
        **kwargs,
    ):
        llm = self._llm
        tokens = input_ids.flatten().tolist()
        n_past = len(self._past)
        if tokens[:n_past] == self._past:
            self._past = tokens
            tokens = tokens[n_past:]
        else:
            self._past = tokens
            llm.reset()
        llm.eval(tokens)
        logits = torch.tensor(llm.logits).reshape([1, 1, -1])
        if not return_dict:
            return (logits,)
        return CausalLMOutput(logits=logits)

    @property
    def device(self) -> torch.device:
        return torch.device("cpu")

It can be used as:
from ctransformers import AutoModelForCausalLM

llm = AutoModelForCausalLM.from_pretrained(...)
model = Model(PretrainedConfig(), llm)

But the API is not finalized and may change by the time I release it.

Looks like outlines generate needs a custom model and tokenizer object which can be created using Transformers and TransformersTokenizer classes. I recommend using the original HF tokenizer to simplify things:
model = Model(PretrainedConfig(), llm) # ctransformers model

from outlines.models.transformers import Transformers, TransformersTokenizer

tokenizer=TransformersTokenizer("Open-Orca/OpenOrca-Platypus2-13B") # change based on the model you are using for ctransformers
model = Transformers(model=model, tokenizer=tokenizer) # outlines model

answer = generate.choice(model, ["Positive", "Negative"])(prompt)

For outlines 0.0.9, the forward pass should return a CausalLMOutputWithPast object instead of a CausalLMOutput. A drop in replacement work although more tweaks should allow for significant speedups.


Unlockable Trophies / Cards

Summary
This feature is a system that allows modes to easily unlock trophies that will apply across the whole swadge. These trophies could either be special ones that are unlocked by a specific mode/achievement, or they could be more generic ones that can be unlocked randomly. These trophies could also act like trading cards (and maybe we'd call them that instead too), and perhaps duplicates could be collected.
There would also be a mode, something like a "Trophy Room" that would let you see the total number of trophies, view the ones you have unlocked, and maybe even trade them with other swadges.
Each trophy would have:

A name
A sequential number
Either a 3D model, or a 2D sprite
A few sentences or so of bio/flavor text/trivia, e.g. "King Donut is the supreme ruler of the MAGLord. Did you know that MAGFest is a donut?"
A few stats, e.g. Height: 17.3m, Weight: 83,204kg,
Rarity / "drop rate", if it should be randomly unlockable (rather than a specific unlock)

Things that could be the subjects of of trophies / cards:

MAG characters (especially ones we already have a model for)
Old swadges
Characters / things from previous swadge games
MAGFest themes/events
MAGFest memes
Bands? Guests?
MAG... departments?

Technical Spec
For modes wishing to unlock trophies, there would be a few simple functions:

bool unlockRandomTrophy(trophyInfo_t* trophy) - Simply unlocks a random trophy and writes the info for the one that was unlocked to the given pointer. Returns true if this is the first time this trophy has been unlocked.
bool unlockTrophy(trophyInfo_t* trophy, uint16_t trophyNumber) - Unlocks a specific trophy by number, returning true if the trophy
void drawTrophyUnlockScreen(const trophyInfo_t* trophy) - Draws a screen that tells the user they just unlocked a trophy and shows which one.
void getTrophyInfo(trophyInfo_t* trophy, uint16_t trophyNumber)  - Writes details about the requested trophy to the given pointer
void getTrophyStats(trophyStats_t* stats) - Writes trophy statistics into the given pointer, detailing the total number of available and unlocked trophies.

For the trophies themselves, they would be stored in a JSON asset, structured something like this:
[
  {
    "name": "King Donut",
    "number": 1,
    "model": "king_donut.obj",
    "desc": "King Donut is the supreme ruler of the MAGLord. Did you know that MAGFest is a donut?",
    "drop_rate": 1,
    "stats": {"Height": "16.7m", "Weight": "83,204kg", "Age": "Timeless"}
  },
  {
    "name": "Gunship Swadge",
    "number": 2,
    "model": "gunship_swadge.obj",
    "desc": "It looks very familiar...",
    "drop_rate": 10,
    "stats": {"Buttons": "8", "Pixels": "53,564", "Speakers": "2"}
  },
  ...
]

UI
What are the display screens & menus (if applicable)?
What user inputs are there for each screen?
The main UI would just be a simple screen showing each trophy's information and model/image, where you can navigate left/right to go to the next unlocked trophy.
There could also be a main screen which shows basic info (number out of total unlocked) and shows a list-style overview of all the locked or unlocked trophies. And for trading, users would be able to select trophies to use for a trade here, which confirming would lead to another screen to connect and confirm an incoming offer.
Mockups
Paste any mockups of screens or anything else here.

How to Test
How can we verify the feature is working?

Seems good! I'm a bit jaded this year, but I bet getting assets and text will be harder than spinning up the trophy system. Do you plan on trophy-ifying modes, or putting that onus on devs? It's a little lateish in the development cycle to scope creep everyone.


yum update 后报错

上线出错:（

初始化部署隔离空间出错::'ERROR! Unexpected Exception, this is probably a bug: (setuptools 0.9.8 (/usr/lib/python2.7/site-packages), Requirement.parse('setuptools>=11.3')) the full traceback was: Traceback (most recent call last): File "/usr/bin/ansible", line 85, in mycli = getattr(__import__("ansible.cli.%s" % sub, fromlist=[myclass]), myclass) File "/usr/lib/python2.7/site-packages/ansible/cli/__init__.py", line 38, in from ansible.inventory.manager import InventoryManager File "/usr/lib/python2.7/site-packages/ansible/inventory/manager.py", line 29, in from ansible.inventory.data import InventoryData File "/usr/lib/python2.7/site-packages/ansible/inventory/data.py", line 30, in from ansible.plugins.cache import FactCache File "/usr/lib/python2.7/site-packages/ansible/plugins/cache/__init__.py", line 30, in from ansible.plugins.loader import cache_loader File "/usr/lib/python2.7/site-packages/ansible/plugins/loader.py", line 22, in from ansible.parsing.plugin_docs import read_docstring File "/usr/lib/python2.7/site-packages/ansible/parsing/plugin_docs.py", line 12, in from ansible.parsing.yaml.loader import AnsibleLoader File "/usr/lib/python2.7/site-packages/ansible/parsing/yaml/loader.py", line 30, in from ansible.parsing.yaml.constructor import AnsibleConstructor File "/usr/lib/python2.7/site-packages/ansible/parsing/yaml/constructor.py", line 29, in from ansible.parsing.vault import VaultLib File "/usr/lib/python2.7/site-packages/ansible/parsing/vault/__init__.py", line 44, in from cryptography.hazmat.backends import default_backend File "/usr/lib64/python2.7/site-packages/cryptography/hazmat/backends/__init__.py", line 7, in import pkg_resources File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 3011, in parse_requirements(__requires__), Environment() File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 630, in resolve raise VersionConflict(dist,req) # XXX put more info here VersionConflict: (setuptools 0.9.8 (/usr/lib/python2.7/site-packages), Requirement.parse('setuptools>=11.3'))'
'ANSIBLE_SSH_ARGS='-o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o CheckHostIP=false' ansible 'all' -u 'xxxx' -m shell -a 'mkdir -p /mnt/www/releases/xxx/20171106-181440' -i '/mnt/data/wwwroot/walle-web/runtime/ansible_hosts/project_1' -f 10 -T 600'

请联系SA或者重新部署

不知道为啥自己好了


Add support for different UILayouts in VerticalCollapsableSection

Currently, the VerticalCollapsableSection component uses UIListLayout. A better alternative to UIListLayout for this component would be UITableLayout.

Generally I have found that the use cases for this section point more towards using a List- rather than TableLayout here, most obviously for creating panels similar to sections in the properties widget. I think a List layout is more flexible because it allows you to have varying sizes along the same row.
In the properties widget case, this also matches up more closely with how I would expect child components to be designed - one entry per row, containing both the left-hand side (property name) and the right-hand side (property value). A table layout would require the name and value components to be separate, which strikes me as a weird design.
Not convinced by the change as it stands but feel free to provide more use cases. We could also think about adding some flexibility here and letting the user provide props to decide which layout they want to use. This is what we do in the ScrollFrame component. An alternative would be to provide the layout itself as a Roact element in a specific prop.


chore(release): 1.0.0-beta.2

👀 PR includes

🔧 Chore

[ ] Test case
[ ] Docs / demos update
[ ] CI / workflow
[x] Release version 1.0.0-beta.2
[ ] Other ()

:tada: This PR is included in version @antv/s2-v1.53.0-beta.1 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Authentication page

GoFreelancer: Sign up and Sign in

We implemented the log in and sign in #1

Made Changes as suggested by the previous reviewer

Made Changes as suggested by the previous reviewer


Tailer user experience improved

When tailer starts it creates empty gradle/instanceTail/incidentFilter.txt file that could be used by the user for filtering

at the moment when user creates this file tailer needs to be restarted to start reading from it

Tailer automatically resumes tailing after instance restart

it used to work, now it is broken

When used with -v switch tailer prints logs stream from the local author

why local author? this shouldn't be hardcoded

Use --console=plain mode in Gradle in this verbose mode. (Gradle startup params console)

Now it prints logs to console by default, you can turn it off using: -Pinstance.tail.console=false

Closing as released in 9.1.0


nuke hiding on warops results in roundstalls

Description
title, people may sometimes hide the nuke on warops which results in roundstall
i suggest: make nukie pinpointers switchable between point to nuke and to disk
Reproduction

wait for it to nukies
cover yourself in disk
nuke hidden, can't get major

Screenshots

The pointer is able to be EMAG'ed to point to the nuke for this reason but maybe we should just add another way to find the nuke, maybe a nuke pinpointer on the station. This could also be a solution #23152

The pointer is able to be EMAG'ed to point to the nuke for this reason but maybe we should just add another way to find the nuke, maybe a nuke pinpointer on the station. This could also be a solution #23152

station nuke

The pointer is able to be EMAG'ed to point to the nuke for this reason but maybe we should just add another way to find the nuke, maybe a nuke pinpointer on the station. This could also be a solution #23152

Why does the pinpointer need to be emagged? Nukie pinpointers should be able to swap between disk and nuke through interaction.


Google Storage filesystem not being passed into DistCp and S3MapReduceCp

Coverage decreased (-0.7%) to 74.114% when pulling 4b6e308c8896eb834f7532333d207102832f2345 on BDP-1135-Run-From-AWS into 8badadf96cdafa67442c4a4bc321efeaf8c9cafe on master.

Looks good, test coverage has decreased nearly 1% though. Can you look? I think it needs to reach 75% at least


update readme

Signed-off-by: x893675<EMAIL_ADDRESS>
What type of PR is this?

/kind documentation
What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #12
Special notes for reviewers:

Does this PR introduced a user-facing change?

None

Additional documentation, usage docs, etc.:

/cc @lixd

Codecov Report

Merging #94 (4b21c96) into master (65bafe8) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #94   +/-   ##
=======================================
  Coverage   11.65%   11.65%
=======================================
  Files          98       98
  Lines       15023    15023
=======================================
  Hits         1751     1751
  Misses      13043    13043
  Partials      229      229


Updated Cloudflare tunnels docs to include how you can allow setting https in the UI

Hey!
Big fan of this project I think it's incredible. I self host this on a mini home server, so a tunnel grants me the most flexibility.
I've been wanting to contribute somehow and I think this PR could be a good one to put into the docs
I've spent enough time trying to work out how to do correct all the way to the container https with a Cloudflare tunnel that I figured it'd benefit the most from being in the official docs for Coolify.
This work updates the Cloudflare Tunnels docs to let you know how you can configure it so that the domain in the UI can be https and it works correctly.
I can't take all credit the final piece that got me there was setting the origin name to be the domain of the added Origin Certificate as seen in this issue discussion -> https://github.com/coollabsio/coolify/issues/3653
I've attempted to write up a guide for everyone. Hopefully everyone finds it useful!
Keep up the great work!

Thanks for the PR 💜. Can I close the linked issue?

Hey!
I leave that to your discretion as I didn't originally make that linked issue. I was having a similar issue that's all!


Environment variables

.env files and environment variables

Introduced a new Environment class. The class holds methods to check the current environment (prod, dev or test).
Introduced support for .env files. FOSSBilling will load the .env file and the corresponding .env.local, .env.$env (e.g. .env.dev) and .env.$env.local (e.g. .env.dev.local) files if they exist.
Environment variables set in the operating system will override the values in the .env files.
The .env file will be used to provide the default values. The .env.local file will be used to override the values in the .env file.
The installer will no longer hold a hardcoded list of configuration options. Instead, it will will just copy the config-sample.php file to config.php and create a .env.local file with the configuration options set by the user. The sample config file is already prepared to look for the environment variables where needed.

This PR also updates the Cypress spec files, hopefully in order to implement automated runs via Cypress Cloud and GitHub Actions in the future.

https://github.com/FOSSBilling/FOSSBilling/assets/35808275/33b7c863-d675-4654-bbf8-dbdd64b34091

I still need to find a way to keep the environment variables working when the config migrator is run.

I still need to find a way to keep the environment variables working when the config migrator is run.

We need to do this before this PR can be merged

I still need to find a way to keep the environment variables working when the config migrator is run.

We need to do this before this PR can be merged

Yep. Any ideas?

I still need to find a way to keep the environment variables working when the config migrator is run.

We need to do this before this PR can be merged

Yep. Any ideas?

Honestly, I'm not sure what the best way to handle it would be.

I still need to find a way to keep the environment variables working when the config migrator is run.

@evrifaessa Any update on this, if not then I think this PR should be marked as draft until there is.

Woah. This looks a little messy. I should separate the Cypress changes and get them merged. The environment variables can stay as a draft.

This likely won't happen in the near future, other beneficial changes were already split into smaller PRs and got merged.


Implement user-selectable compiler warning switches

It has become apparent that a "one-size-fits-all" approach to compiler warnings may not be sufficient going forward.
In general, most developers should be using "-Werror" in addition to "-Wall", "-pendantic", etc to catch any coding issues at first sight.
However, the specific set of warnings for any given piece of code is dependent on the specific compiler version, target architectures, and optimization level in use at the time of build.  This can mean code that builds without warnings on one build can fail miserably on a different build.
This could be an major issue for a novice who clones the latest code from the community repository, and builds it with the latest version of GCC (i.e. one that we may not have tested yet) and finds a new warning that causes the entire build to fail unexpectedly.
As a compromise, the following is proposed:

Always use "-Wall" switch to enable the most reasonable warnings (incidentally, this is not all warnings, it leaves out the ones most likely to generate false positives).
Do not put "-Werror" in the official build scripts, so if compiling with a new GCC version or a different target architecture than the what has been officially tested, the build will not fail if a new warning is triggered.
Also leave out "-pedantic" from the official build as this, by definition, tends to warn on constructs that are generally OK in practice but violate some (possibly esoteric) aspect of the C standard.  The thought behind this is that plenty of old existing code out there may work fine but might not compile cleanly using "-pedantic", so we should not force this switch upon users by default.
Add a mechanism by which developers can easily add extra CFLAGS to a build, without modifying a Makefile (or CMakeLists) file.  This way, any users that want to may enable "-Werror" or "-pedantic" on their own builds, all the time, without having to maintain a private branch of the build script.

The automatic builds done by Bamboo, these will be built without "-Werror" but the build log will be checked for warnings, and the presence of any new warnings will be logged as a unit test error so they can be fixed before moving the code forward.

Trac comment by glimes on 2015-05-18 20:04:56:
Accept.

Trac comment by jphickey on 2015-04-17 14:52:46:
Commit [changeset:f46224c] has been pushed for this
The extra flags are specified through a variable called "OSAL_USER_C_FLAGS".  The value of this variable is set in one of two ways:

Via an environment variable, e.g. {{{export OSAL_USER_C_FLAGS=-Werror}}}
Via a "-D" option to the cmake commend, i.e. {{{-DOSAL_USER_C_FLAGS=-Werror}}}

In all cases, a CMake cache variable is utilized so that value will be retained from build to build, even if the original environment variable changes.  This is important for building from an IDE that may have a different environment than the command shell.
Also, the {{{-Wall}}} build option is added to all builds.

Imported from trac issue 37.  Created by jphickey on 2015-04-17T14:18:14, last modified: 2015-11-20T16:22:16

Trac comment by sstrege on 2015-05-19 10:38:17:
What is the mechanism by which developers can easily add extra CFLAGS to a build using the old build system?

Trac comment by sstrege on 2015-06-29 16:53:27:
The answer to my question above is provided in the comments (through an environment variable).

Trac comment by glimes on 2015-06-30 11:02:42:
Recommend accept.

Trac comment by sstrege on 2015-06-29 16:53:39:
Accept

Trac comment by glimes on 2015-06-30 14:37:42:
CCB approved.

Trac comment by acudmore on 2015-06-30 12:40:43:
Recommend accept.


Hotfix: dbr tapered fix

Summary by Sourcery
Fix parameter naming and improve cross-section handling in the '_generate_fins' function of the 'dbr_tapered' component.
Bug Fixes:

Fix the parameter name from 'xs' to 'cross_section' in the '_generate_fins' function to improve clarity and correctness.

Enhancements:

Use 'gf.get_cross_section' to retrieve the cross-section specification, ensuring consistency and correctness in the '_generate_fins' function.

I merged this one https://github.com/gdsfactory/gdsfactory/pull/3418 as it also removed a warning


Length parameters incorrectly declared as distance

Reported by jriel on 11 Apr 2011 19:10 UTC
The partial models
Modelica.Mechanics.Translational.Interfaces.PartialCompliantWithRelativeStates
Modelica.Mechanics.Translational.Interfaces.PartialCompliant
incorrectly declare the variable
SI.Distance s_rel(start=0) "relative distance (= flange_b.s - flange_a.s)";
This should be declared as SI.Length.  The Distance type specifies a minimum value of 0, which is not relevant for this variable (the spring equations are valid regardless whether the spring is compressed past the 0 length).

Migrated-From: https://trac.modelica.org/Modelica/ticket/526

Modified by dietmarw on 12 Apr 2011 06:07 UTC

Comment by anonymous on 12 Apr 2011 10:00 UTC
Duplicate of #446

Modified by dietmarw on 12 Apr 2011 10:31 UTC


Add GALWEM support to USAFSI

Adds support for GALWEM 17-km or 10-km GRIB2 data as source of 2-m air temperature in USAFSI.
Includes updates to ldt.config documentation.

Hello Eric,
I have a few questions and comments.
In ldt/USAFSI/USAFSI_galwemMod.F90:

subroutine USAFSI_get_galwem_t2m

130           write(LDT_logunit,*) '[WARN] in grib_count_in_file: ' // &
131                'dataTime in USAFSI_get_galwem_t2m'

This warning message is incorrect.

subroutine USAFSI_get_galwem_t2m

384        if (found) exit

I believe that this line is should be if ( k > nvars ) exit.  The while loop will end when found == .true..

subroutine USAFSI_get_galwem_t2m

389     if (.not. found) then

Does not make sense unless we change line 384.  As written, the code will not reach line 389 unless found == .true..  At which point, the code will not execute the body of this if block.

subroutine USAFSI_get_galwem_t2m

402     return

This return statement is not needed.

subroutine interp_galwem_t2m

Can we compute the weights and neighbours just once, say in subroutine set_galwem_griddesc?

Regarding 5.  I see that this is being done just once.  This routine processes only 2m temperature.

Hi Jim:
Regarding 2:  The logic is designed to gracefully handle a corrupt GRIB file.  If after looping through a particular file and not finding 2-m temperature, the subroutine will roll back to an earlier forecast run.  This "roll back" option is part of the outer while loop, while the inner do loop (k = 1, nvars) handles a particular GRIB file.  The "found" logical flag should only be set to .true. if 2-m temperature is indeed found; and at that point, both outer and inner loops should be exited.
Bottom line:  I believe the existing logic is correct.  If 2-m temperature is not found (or not found with the right map projection, time, cannot be read, etc), the inner loop will continue cycling until all nvars are searched.  Found will still be false, so the outer loop will cycle.

Hi Jim:
Regarding 3: Again, it is possible 2-m temperature won't be found after searching all the GRIB files.  In this case, the logic will cause the subroutine to return early, cleaning up allocated memory before it leaves.

Hi Jim:
Regarding 5:  Those interpolation weights are only need to be used once, so I don't think there's a need to move the code.

Hello Eric,
Sorry.  I did not take the roll back into account.  I now see that line 97 will abort the while loop in case everything goes wrong.  And now I understand the if at line 389.  Thanks for the explanation.
I am still confused by the if on line 384.  I believe that it is not needed.  The code leaves the do k = 1, nvars loop when the GRIB file cannot be opened, when k > nvars, or when 2 meter temperature is found.  All three cases are handled by the enddo at line 388.  For the first two cases, the code goes back to the top of the while loop and rolls back.  For the last case, the code found the temperature field.
What else did I not take into account?
And I agree with you regarding 5.

I removed the if statement in 3) above.


Investigate supporting other container runtimes for `container_spec

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/3323
Originally created by @tayloramurphy on 2022-03-08 21:23:43

From Florian

Since we don't wrap the docker cli, it might not be as easy to swap in other container run times unless they support the Docker API. So might be worth investigating how this works with containerd. At first glance, I can't tell if containerd has a legacy Docker compatible API (seems like older version may have). Containerd is grpc based so guessing there are already python bindings floating around we could leverage in the future.
The other one that pop'd up when we were chatting with the community last year about docker alternatives was Podman. Poking around a bit it does seem like Podman still has a docker compatible API (https://docs.podman.io/en/latest/_static/api.html?version=v4.0) so might be worth seeing if that just works or if requires additional config.
Just flagging this because with the new Docker Desktop license change in full effect https://gitlab.com/meltano/meta/-/issues/174 might become a bit more tricky/important.

View 2 previous comments from the original issue on GitLab


add new RenameInput component to ColField and ComponentWrapper

💬 Description
Now that we have a fancy new component (https://github.com/gathercontent/gather-ui/pull/920) we should use it
✅ Checklist

[ ] Tests written
[ ] Browser tested
[ ] Added to documentation
[ ] Added to storybook

 Update component label input to be inline with tabs

 Update component label input to be inline with tabs


Vs Code update caused workspace to dissapear

Issue Type: Bug

Vs Code automatically updated to the latest version
Vs Code opened with a blank workspace
Old workspace is completely gone. Can't even find it on my hard drive anymore.

VS Code version: Code 1.36.1 (2213894ea0415ee8c85c5eea0d0ff81ecc191529, 2019-07-08T22:59:35.033Z)
OS version: Windows_NT x64 10.0.17134

System Info

Item
Value

CPUs
AMD FX-8320E Eight-Core Processor               (8 x 3222)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwareoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_deferred_display_list: disabled_offskia_renderer: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
7.98GB (4.37GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (11)

Extension
Author (truncated)
Version

very-smart-select
clo
0.3.0

prettier-vscode
esb
1.9.0

auto-close-tag
for
0.5.6

auto-complete-tag
for
0.1.0

auto-rename-tag
for
0.1.0

macros
ged
1.2.1

python
ms-
2019.6.24221

color-highlight
nau
2.3.0

LiveServer
rit
5.6.1

code-settings-sync
Sha
3.4.1

guides
spy
0.9.3

(1 theme extensions excluded)

Managed to find some backup information of the workspace in roaming appdata of Vs Code. It says the exact folder where my project (cencored red) was before the update. It does no longer exist now and also is nowhere to find in my recycling bin.

@sitoprvt that is unfortunate, sorry. But should never store workspaces within the installation directory of VSCode as that directory gets deleted when updating.
//cc @joaomoreno
Duplicate of https://github.com/microsoft/vscode/issues/76567


AWTUtils.getViewPointer(Component component) cause NPE

I tested this library (loaded from maven repo) within my testing java app and it alway produce NPE:
Exception in thread "main" java.lang.RuntimeException: java.lang.NullPointerException
at com.thizzer.jtouchbar.awt.AWTUtils.getViewPointer(AWTUtils.java:25)
at com.thizzer.jtouchbar.JTouchBar.enableForComponent(JTouchBar.java:60)
at Start.init(Start.java:34)
at Start.main(Start.java:23)
Caused by: java.lang.NullPointerException
at com.thizzer.jtouchbar.awt.AWTUtils.getViewPointer(AWTUtils.java:19)
... 3 more
Problematic line follow (AWTUtils: 24)
Object peer = Component.class.getMethod("getPeer").invoke(component);
where peer object return null and next line (of course) end up NPE.
any idea?

What object/class are you passing to the ‘enableForComponent’ method?

I followed example so here is that piece:
JFrame frame = new JFrame();
JTouchBar jTouchBar = new JTouchBar();
jTouchBar.setCustomizationIdentifier("TouchBar");
jTouchBar.enableForComponent(frame);
frame is of course javax.swing.JFrame

Hmm.. This should of course just work. I will look in to this, what version of macOS and Java are you using?

jdk1.8.0_152
macOS Sierra 10.12.6

The way I can reproduce this is when JFrame.pack(); and/orJFrame.setVisible(true); have not been called.
So you have to properly initialise your JFrame, this should go as follows;
JFrame frame = new JFrame();
// .. add stuff to frame
frame.pack();
frame.setVisible(true);

JTouchBar jTouchBar = new JTouchBar();
jTouchBar.setCustomizationIdentifier("TouchBar");
jTouchBar.enableForComponent(frame);

Could you please let me know if this works? I will try to add a more elaborate examples in the future.

Hey, with pack() && setVisible() that works as charm :)

Thats good to hear 👍
Please let me know if you have any suggestions for the library or features you would like to see added.


Loosing 'auth' when using "Cloud Foundry" menu

Frontent Deployment type

[ ] Cloud Foundry Application (cf push)
[x] Kubernetes, using a helm chart
[ ] Docker, using docker compose
[ ] Docker, single container deploying all components
[ ] npm run start
[x] Other (please specify below)
Console 2.1.0 with CAP 1.2.1

Backend (Jet Stream) Deployment type

[ ] Cloud Foundry Application (cf push)
[x] Kubernetes, using a helm chart
[ ] Docker, using docker compose
[ ] Docker, single container deploying all components
[x] Other (please specify below)
UAA/CF 2.13.3 on CaaSP3 (NFS storage)

Expected behaviour

Goto https://<domain>:8443/cloud-foundry, select "Organizations" and create org 'suseqa'
Click on org 'suseqa', select "Spaces" and create space 'susetest'

Actual behaviour

After clicking org 'suseqa' and selecting sapces, "'Cloud Foundry > suseqa' Spaces" loads forever.

From here on any other menu, e.g. "Services" loads forever, too, even when you return to "Cloud Foundry" - it seems like not being authenticated with the endpoint anymore

Simply reloading the browser page on a page that "hangs" fixes the issue.

Steps to reproduce the behavior
Log output covering before error and any error statements
Unfortunately I was not able to see any error logged:
Request: [2018-10-01T11:57:11Z] Remote-IP:"<IP_ADDRESS>" Method:"GET" Path:"/v1/auth/session/verify" Status:401 Latency:65.157µs Bytes-In:0 Bytes-Out:43
INFO[Mon Oct  1 11:57:17 UTC 2018] Found existing cloud foundry endpoint matching https://api.<IP_ADDRESS>.omg.howdoi.website. Will not auto-register
INFO[Mon Oct  1 11:57:17 UTC 2018] Determining if user should auto-connect to https://api.<IP_ADDRESS>.omg.howdoi.website.
INFO[Mon Oct  1 11:57:17 UTC 2018] Yes, user should auto-connect to auto-registered cloud foundry https://api.<IP_ADDRESS>.omg.howdoi.website.
INFO[Mon Oct  1 11:57:17 UTC 2018] Auto-connecting to the auto-registered endpoint with credentials
INFO[Mon Oct  1 11:57:17 UTC 2018] CloudFoundry Connect...
Request: [2018-10-01T11:57:18Z] Remote-IP:"<IP_ADDRESS>" Method:"POST" Path:"/v1/auth/login/uaa" Status:200 Latency:532.690164ms Bytes-In:32 Bytes-Out:90
Request: [2018-10-01T11:57:18Z] Remote-IP:"<IP_ADDRESS>" Method:"GET" Path:"/v1/auth/session/verify" Status:200 Latency:5.004533ms Bytes-In:0 Bytes-Out:2668
Request: [2018-10-01T11:57:18Z] Remote-IP:"<IP_ADDRESS>" Method:"GET" Path:"/v1/info" Status:200 Latency:3.92472ms Bytes-In:0 Bytes-Out:2668
Request: [2018-10-01T11:57:18Z] Remote-IP:"<IP_ADDRESS>" Method:"GET" Path:"/v1/proxy/v2/apps" Status:200 Latency:38.508909ms Bytes-In:0 Bytes-Out:115
Request: [2018-10-01T11:57:18Z] Remote-IP:"<IP_ADDRESS>" Method:"GET" Path:"/v1/proxy/v2/organizations" Status:200 Latency:104.229272ms Bytes-In:0 Bytes-Out:3900
Request: [2018-10-01T11:57:24Z] Remote-IP:"<IP_ADDRESS>" Method:"GET" Path:"/v1/proxy/v2/shared_domains" Status:200 Latency:14.122311ms Bytes-In:0 Bytes-Out:431
Request: [2018-10-01T11:57:24Z] Remote-IP:"<IP_ADDRESS>" Method:"GET" Path:"/v1/proxy/v2/info" Status:200 Latency:27.536657ms Bytes-In:0 Bytes-Out:758
Request: [2018-10-01T11:57:24Z] Remote-IP:"<IP_ADDRESS>" Method:"GET" Path:"/v1/proxy/v2/organizations" Status:200 Latency:36.196932ms Bytes-In:0 Bytes-Out:1627
Request: [2018-10-01T11:57:24Z] Remote-IP:"<IP_ADDRESS>" Method:"GET" Path:"/v1/proxy/v2/organizations" Status:200 Latency:74.945893ms Bytes-In:0 Bytes-Out:6016
Request: [2018-10-01T11:57:24Z] Remote-IP:"<IP_ADDRESS>" Method:"GET" Path:"/v1/proxy/v2/users" Status:200 Latency:107.604265ms Bytes-In:0 Bytes-Out:1959
Request: [2018-10-01T11:57:29Z] Remote-IP:"<IP_ADDRESS>" Method:"GET" Path:"/v1/proxy/v2/organizations/9aaa261d-1236-4cda-8e11-ead1002512c0/users" Status:200 Latency:56.787312ms Bytes-In:0 Bytes-Out:115
Request: [2018-10-01T11:57:29Z] Remote-IP:"<IP_ADDRESS>" Method:"GET" Path:"/v1/proxy/v2/organizations" Status:200 Latency:84.159799ms Bytes-In:0 Bytes-Out:1627
Request: [2018-10-01T11:57:36Z] Remote-IP:"<IP_ADDRESS>" Method:"GET" Path:"/v1/auth/session/verify" Status:200 Latency:13.410628ms Bytes-In:0 Bytes-Out:2668
Request: [2018-10-01T11:57:36Z] Remote-IP:"<IP_ADDRESS>" Method:"GET" Path:"/v1/info" Status:200 Latency:7.68204ms Bytes-In:0 Bytes-Out:2668
Request: [2018-10-01T11:57:36Z] Remote-IP:"<IP_ADDRESS>" Method:"GET" Path:"/v1/proxy/v2/shared_domains" Status:200 Latency:15.229401ms Bytes-In:0 Bytes-Out:431
Request: [2018-10-01T11:57:36Z] Remote-IP:"<IP_ADDRESS>" Method:"GET" Path:"/v1/proxy/v2/organizations/9aaa261d-1236-4cda-8e11-ead1002512c0/spaces" Status:200 Latency:29.989988ms Bytes-In:0 Bytes-Out:1448
Request: [2018-10-01T11:57:36Z] Remote-IP:"<IP_ADDRESS>" Method:"GET" Path:"/v1/proxy/v2/organizations/9aaa261d-1236-4cda-8e11-ead1002512c0" Status:200 Latency:40.100252ms Bytes-In:0 Bytes-Out:3820
Request: [2018-10-01T11:57:36Z] Remote-IP:"<IP_ADDRESS>" Method:"GET" Path:"/v1/proxy/v2/organizations" Status:200 Latency:29.595215ms Bytes-In:0 Bytes-Out:1627
Request: [2018-10-01T11:57:36Z] Remote-IP:"<IP_ADDRESS>" Method:"GET" Path:"/v1/proxy/v2/users" Status:200 Latency:290.600597ms Bytes-In:0 Bytes-Out:1959

This was fixed in upstream a few weeks back, we need to update and retest

Uber PR #59 has now merged. Have tested on v2-master and all looks good.


Added slinkydeveloper as approver

Signed-off-by: Francesco Guardiani<EMAIL_ADDRESS>See https://github.com/knative/eventing/pull/3091

/assign @n3wscott

/lgtm
/approve


Allow users to install git-theta in multiple ways

There is now a --scope argument for git theta install. It has the following values:

global: Install git-theta via ~/.gitconfig
user: Install git-theta via $XDG_CONFIG/git/config, this dir needs to exists
system: Install to /etc/git/config which often needs root powers
repository: You need to be in a repo and it installs it to .git/config

As we use git config --list which checking if git-theta is installed, we should find it no matter where it is installed.

closes https://github.com/r-three/git-theta/issues/233


Execution error on macOS: "dyld: Symbol not found: _objc_alloc_init" on macOS 10.13.6

Related to https://github.com/golang/go/issues/37849
CC @wasedaigo

https://github.com/golang/go/issues/18400#issuecomment-270414574
Specifying CGO_CFLAGS would solve this, but I'd want to avoid this 🤔

I think CGO_CLAGS is the only way so far. I'll add documentation.
In the long term, #1162 should solve this.


[Image] 0.8.0-rc.2 Appearing 1px border When the image is scaled.

I should display brand images in box, the images size is 186x120, But it's too big,so I use resizeMode:Image.resizeMode.contain to control.
However, If you're using iPhone 6Plus, it shows the following appearance.:sob:  Who has met this problem,Seeking solutions.

This is the demo:
https://github.com/cssoul/react-native-trade/blob/master/demo3/brands.js

Duplicate of my own #1870

Thanks @grabbou!


[REQ] Custom death sound effect

Acknowledgement of preliminary instructions

[X] I have read and acknowledged the preliminary instructions.

What idea do you have?
If you add custom death sound effect option, that would be great

https://github.com/pizzaboxer/bloxstrap/wiki/Adding-custom-mods
Death sound is located at content\sounds\ouch.ogg. We might consider making this a little bit easier as a preset though.


Which version of ResNet you implemented here?

Actually I don't know, the model and weights borrowed from https://github.com/ry/tensorflow-resnet


[YUNIKORN-2982] Send event when preemption occurs

What is this PR for?
When a preemption occurs, send an event to be displayed in the victim's event list.
https://github.com/apache/yunikorn-core/pull/1000
What type of PR is it?

[x] - Improvement

What is the Jira issue?
YUNIKORN-2982
How should this be tested?
Trigger preemption

@rhh777 do we still need this? Please close it if the changes in the core alone suffice.

close


OAuth Migration: migrate all configs in one job

Tiez to moc nepouzivam, ale zrovna sa mi to hodilo
On Thu, 20 Dec 2018 22:12 Ondrej Popelka<EMAIL_ADDRESS>wrote:

@odinuv commented on this pull request.
In tests/Keboola/ConfigMigrationTool/Migrations/OAuthMigrationTest.php
https://github.com/keboola/config-migration-tool/pull/33#discussion_r243419324
:

         $this->assertArrayHasKey('created', $response);

         $this->assertArrayHasKey('#data', $response);
         $this->assertArrayHasKey('oauthVersion', $response);
         $this->assertArrayHasKey('appKey', $response);
         $this->assertArrayHasKey('#appSecret', $response);

<EMAIL_ADDRESS>$response['authorizedFor']);

       $this->assertEquals($configurationId, $response['id']);

       $this->assertContains($response['id'], $this->configurations);

sem vubec nevedel, ze assertContains funguje i na pole
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/keboola/config-migration-tool/pull/33#pullrequestreview-187186646,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABa0j5gbHmJqvi_15hWKO9EV0qTjexLQks5u6_1UgaJpZM4ZcGDZ
.


STYLE: Update GIFEE expansion. Add capitalization rules for project names

Proposed. List of projects with lower case rule can probably be lengthened.
Eventually want to simplify this rule to be "Project names are proper nouns." Currently proposing we write them with initial capitals when beginning a sentence. Baby steps.

@jonboulle I know you are going to be this PR's biggest fan. PTAL.


responsible nodes-the old version was still there

I removed the finding responsible nodes in the old way but somehow it stayed there after merge.

Hi Vahid,
can you also remove it from config/testdata/default_config.yaml and from config.yaml?


StackExchange Markdown

For {{prefix:ref}}: https://github.com/pi-base/web/blob/main/packages/core/src/Ref.ts

Looks good!


Is there any ability to connect REST api and grab data from it for view in metatron-discovery dashboard

I wanted to know that there is any option to connect REST api and grab data from it for view in metatron-discovery dashboard ?

Currently, this feature is not supported.
To visualize data through the dashboard, only the data loaded on the metatron-engine is available.
Data loading on the engine is possible with the following data.

@ufoscw Ah ,  I want to feed the realtime data stream through "rest api" and to monitor it via metatron-discovery dashboard. Waiting for it until it will be enabled in future versions :-)

@kaviranga
I'll give you a link to a blog post related to real-time data analysis at metatron.
https://metatron.app/2018/08/02/visualize-real-time-data-with-metatron-discovery/

@ufoscw Thank you for the support . This is great . I'll try it by myself !


pilosa import --create doesn't use --string-keys

For bugs, please provide the following:
Expected behavior
./pilosa import --create --string-keys --index i1 --field f1 CSV_FILE should create i1 and f1 with keys=true.
Actual behavior
Running the following:
curl localhost:10101/index/i1/query -d 'Row(f1="foo")'

Results in:
{"error":"executing: string 'row' value not allowed unless field 'keys' option enabled"}

Steps to reproduce the behavior
./pilosa import --create --index i1 --field f1 --string-keys 1.csv

With the following CSV:
foo,bar

Then:
curl localhost:10101/index/i1/query -d 'Row(f1="foo")'

Good catch. I want to add that having string-keys apply to both the index and the field is not ideal, since it's possible to have string keys for one and not the other. We should think about how (and whether) we handle index and field options on the pilosa CLI command.

Let's do an --index.keys boolean and a field.keys boolean. As we add more options to indexes and fields, they will follow naturally as flags in this fashion