Add an option to group global search results by top-level directory

In my work environment, I started out having a multi-root workspace with all of the roots being only a few folders out of a parent directory that contains many others. Recently I found a way to reconfigure this workspace into one that uses the parent directory as the sole root and only includes the same folders as before by excluding all of the unwanted stuff, and I am currently getting used to the differing practicalities of this setup vs. the previous one.
One of the benefits of the previous multi-root workspace was that global search results were grouped by root, so the root itself could be expanded or collapsed and all search results within the root would be revealed or hidden appropriately. I would love a way to do that with this workspace as well, where each top-level subdirectory of the root is its own group containing all search results within itself and can be collapsed and expanded as such. It's inconvenient to have every single file containing search results be listed at the same level where I must scroll down a long way just to find the one I'm looking for. The only current workaround is to type a file path or extension into the "files to include" field.

This is also quite similar to https://github.com/microsoft/vscode/issues/20224


[1.10.2] Can't disable deffault recipes

Can't disable the default recipes. Will turn "defaultRecipes="true"" to "defaultRecipes="false"" but nothing happens(after closing and reopening MC of course).

Turns out to be the default template is broken.
Rename "defaultRecipes" to "useDefault" and it should work


ARROW-4565: [R] Fix decimal record batches with no null values

Fix for https://issues.apache.org/jira/browse/ARROW-4565. We were missing to handle cases where decimal arrays have no null values.
Regarding adding a test, there seems to be no way to convert arrays to DecimalType, if someone can thing of a workaround I'll add a test.  I'm also planning to start testing against arrow devel in our Travis builds.

Not sure I understand how https://github.com/apache/arrow/pull/3307 is related to this. Is that the correct reference?

This is probably a mixup between the github and the jira issues with the same number.

ARROW-3307 "[R] Convert chunked arrow::Column to R vector" is resolved already and does not seem related either. Should we merge?

https://github.com/apache/arrow/pull/2845 Is the one I meant, although i’m not sure yet how to handles nulls there, so yeah we can merge this in the meantime

:+1:

I went ahead and opened https://issues.apache.org/jira/browse/ARROW-4621


Gosund SP1 dead after set up wifi SSID on device

Hi, I m struggling with my SP1.
followed: https://www.heise.de/ct/artikel/Tuya-Convert-IoT-Geraete-ohne-Loeten-vom-Cloud-Zwang-befreien-4283623.html
all fine. flash complete , SP1 comes up with own WIFI.
After changing the settings to my own wifi, SSID & password the device is rebooting and seems to be dead.
After connection with energy: LED blinks 1x and after some seconds 3x more
not connected to my Wifi, no Tasmoto wifi found.
Resetting: press button 4x or 6x or for more then 40seconds, -- no response
also no reaction on single press (on/off)
any ídeas

Please see Tasmota for assistance troubleshooting Tasmota. This is the issue tracker for tuya-convert issues.

Please see Tasmota for assistance troubleshooting Tasmota. This is the issue tracker for tuya-convert issues.


Update Twitter.svelte

Added X Logo

Thanks for this. Why is it a draft? Are you still working on it?

Nope, first time contributing to a repo. So I wasn't sure how it works

Looks perfect.  Thank you!


chore: prepare Lean version bump with explicit simp

I've pushed a few fixes, and am now most of the way through a local build.

bors d+

bors merge

bors p=10


Determine if GUI apps can be installed as part of the laptop script

The What
We have a doc that lists the desktop application we want to install for new hires.
Currently, we install these manually through a web browser. We should determine if we can instead make this part of the laptop setup script, and implement it if we can.
The How
We think we may be able to  get Chrome installed with Brew Cask (https://github.com/Homebrew/homebrew-cask) (a way to use Homebrew to install GUI apps)
We should verify this and see if we can do the same for the other GUI/desktop apps that we need.

It looks like cask is already set up, so it may just work™

It also looks like it may uninstall cask, so we may want to test it.
When setting up for interns, we should try adding a line like:
cask "google-chrome"

and see if it works.

We have IT install these apps ahead of time before they give the laptop to the new hire, so the need for this is low enough that we can close this.


Switch to SQLite, will it migrate

Hi there,
ive just seen that some months ago you switch to sqlite for the history db.
Before  i update (i think i use the version from end of last year) i would like to know if my old history will be migrated?
Else i would have to edit my shows.txt to only download new shows after the current date.

I'm sorry to say that but it will not.
I was about to integrate code to do so, but at this point I also decided to use a built-in hash algorithm to reduce dependencies further. So migration became impossible.


[BUG] Renesas RSK64F Demo build errors (linker)

Describe the bug
There are 33 errors when trying to build the RX600_RX64M_RSK_Renesas_e2studio demo with the latest E2 Studio IDE.
Target

Development board: Renesas RSK+RX64M (R5F564MLLCDFC processor)
Instruction Set Architecture: RXv2
IDE and version: Renesas E2 Studio Version <IP_ADDRESS>
Toolchain and version: RX Compiler CC-RX V2.01.00

Host

Host OS: Windows 10
Version: 10.0.15063 Build 15063

To Reproduce
You do not need hardware to reproduce this issue. Simply download the latest E2 Studio IDE from Renesas website [Windows only] and import the RX64M demo as described on the FreeRTOS website (https://www.freertos.org/RX64M_RTOS_Renesas_GCC_e2studio.html). The initial build fails with 33 linker errors related: 2 related to undefined ref to sprint and 31 related to undefined refs to stream buffer symbols.
Expected behavior
Building the demo project should complete successfully without any user modifications required.
Screenshots
N/A
Additional context
Console output:
Description	Resource	Path	Location	Type
E0562310: Undefined external symbol "_xStreamBufferReceiveFromISR" referenced in ".\Source\Common_Demo_Source\Minimal\StreamBufferDemo.obj"	RTOSDemo		 	C/C++ Problem
E0562310: Undefined external symbol "_xStreamBufferReceiveFromISR" referenced in ".\Source\Common_Demo_Source\Minimal\MessageBufferDemo.obj"	RTOSDemo		 	C/C++ Problem
E0562310: Undefined external symbol "_xStreamBufferSend" referenced in ".\Source\Common_Demo_Source\Minimal\MessageBufferDemo.obj"	RTOSDemo		 	C/C++ Problem
E0562310: Undefined external symbol "_xStreamBufferSend" referenced in ".\Source\Common_Demo_Source\Minimal\MessageBufferAMP.obj"	RTOSDemo		 	C/C++ Problem
E0562310: Undefined external symbol "_xStreamBufferSend" referenced in ".\Source\Common_Demo_Source\Minimal\StreamBufferDemo.obj"	RTOSDemo		 	C/C++ Problem
recipe for target 'RTOSDemo.abs' failed [Conflicting names] 	makefile	/RTOSDemo/HardwareDebug	line 119	C/C++ Problem
make: *** [RTOSDemo.abs] Error 1	RTOSDemo		 	C/C++ Problem
E0562310: Undefined external symbol "_xStreamBufferIsEmpty" referenced in ".\Source\Common_Demo_Source\Minimal\MessageBufferDemo.obj"	RTOSDemo		 	C/C++ Problem
E0562310: Undefined external symbol "_xStreamBufferBytesAvailable" referenced in ".\Source\Common_Demo_Source\Minimal\StreamBufferDemo.obj"	RTOSDemo		 	C/C++ Problem
E0562310: Undefined external symbol "_xStreamBufferGenericCreate" referenced in ".\Source\Common_Demo_Source\Minimal\StreamBufferDemo.obj"	RTOSDemo		 	C/C++ Problem
E0562310: Undefined external symbol "_xStreamBufferGenericCreate" referenced in ".\Source\Common_Demo_Source\Minimal\MessageBufferDemo.obj"	RTOSDemo		 	C/C++ Problem
E0562310: Undefined external symbol "_xStreamBufferGenericCreate" referenced in ".\Source\Common_Demo_Source\Minimal\MessageBufferAMP.obj"	RTOSDemo		 	C/C++ Problem
E0562310: Undefined external symbol "_xStreamBufferIsEmpty" referenced in ".\Source\Common_Demo_Source\Minimal\StreamBufferDemo.obj"	RTOSDemo		 	C/C++ Problem
E0562310: Undefined external symbol "_xStreamBufferSendCompletedFromISR" referenced in ".\Source\Common_Demo_Source\Minimal\MessageBufferAMP.obj"	RTOSDemo		 	C/C++ Problem
E0562310: Undefined external symbol "_sprintf" referenced in ".\Source\Common_Demo_Source\Minimal\MessageBufferDemo.obj"	RTOSDemo		 	C/C++ Problem
E0562310: Undefined external symbol "_sprintf" referenced in ".\Source\Common_Demo_Source\Minimal\MessageBufferAMP.obj"	RTOSDemo		 	C/C++ Problem
E0562310: Undefined external symbol "_xStreamBufferGenericCreate" referenced in ".\Source\Common_Demo_Source\Minimal\StreamBufferInterrupt.obj"	RTOSDemo		 	C/C++ Problem
E0562310: Undefined external symbol "_xStreamBufferSendFromISR" referenced in ".\Source\Common_Demo_Source\Minimal\MessageBufferDemo.obj"	RTOSDemo		 	C/C++ Problem
E0562310: Undefined external symbol "_xStreamBufferSendFromISR" referenced in ".\Source\Common_Demo_Source\Minimal\StreamBufferDemo.obj"	RTOSDemo		 	C/C++ Problem
E0562310: Undefined external symbol "_xStreamBufferIsFull" referenced in ".\Source\Common_Demo_Source\Minimal\MessageBufferDemo.obj"	RTOSDemo		 	C/C++ Problem
E0562310: Undefined external symbol "_xStreamBufferIsFull" referenced in ".\Source\Common_Demo_Source\Minimal\StreamBufferDemo.obj"	RTOSDemo		 	C/C++ Problem
E0562310: Undefined external symbol "_xStreamBufferReceive" referenced in ".\Source\Common_Demo_Source\Minimal\MessageBufferDemo.obj"	RTOSDemo		 	C/C++ Problem
E0562310: Undefined external symbol "_xStreamBufferReceive" referenced in ".\Source\Common_Demo_Source\Minimal\StreamBufferDemo.obj"	RTOSDemo		 	C/C++ Problem
E0562310: Undefined external symbol "_xStreamBufferSendFromISR" referenced in ".\Source\Common_Demo_Source\Minimal\StreamBufferInterrupt.obj"	RTOSDemo		 	C/C++ Problem
E0562310: Undefined external symbol "_xStreamBufferReceive" referenced in ".\Source\Common_Demo_Source\Minimal\MessageBufferAMP.obj"	RTOSDemo		 	C/C++ Problem
E0562310: Undefined external symbol "_xStreamBufferSpacesAvailable" referenced in ".\Source\Common_Demo_Source\Minimal\StreamBufferDemo.obj"	RTOSDemo		 	C/C++ Problem
E0562310: Undefined external symbol "_xStreamBufferReset" referenced in ".\Source\Common_Demo_Source\Minimal\MessageBufferDemo.obj"	RTOSDemo		 	C/C++ Problem
E0562310: Undefined external symbol "_xStreamBufferReceive" referenced in ".\Source\Common_Demo_Source\Minimal\StreamBufferInterrupt.obj"	RTOSDemo		 	C/C++ Problem
E0562310: Undefined external symbol "_xStreamBufferSpacesAvailable" referenced in ".\Source\Common_Demo_Source\Minimal\MessageBufferDemo.obj"	RTOSDemo		 	C/C++ Problem
E0562310: Undefined external symbol "_vStreamBufferDelete" referenced in ".\Source\Common_Demo_Source\Minimal\MessageBufferDemo.obj"	RTOSDemo		 	C/C++ Problem
E0562310: Undefined external symbol "_vStreamBufferDelete" referenced in ".\Source\Common_Demo_Source\Minimal\StreamBufferDemo.obj"	RTOSDemo		 	C/C++ Problem
E0562310: Undefined external symbol "_xStreamBufferReset" referenced in ".\Source\Common_Demo_Source\Minimal\StreamBufferDemo.obj"	RTOSDemo		 	C/C++ Problem
E0562310: Undefined external symbol "_xStreamBufferNextMessageLengthBytes" referenced in ".\Source\Common_Demo_Source\Minimal\MessageBufferDemo.obj"	RTOSDemo		 	C/C++ Problem

https://forums.freertos.org/t/renesas-rsk64m-demo-build-errors-undefined-external-symbol-sprintf/9286

I think that this pull request can be closed because the issue is solved by commit https://github.com/FreeRTOS/FreeRTOS/commit/1ae6eda77aa5665d50a889f814736121e7f9960e

CLosing as per NoMaY-jp above


WebPart zone mapping to one third right column layout

Category
[ x ] Bug
[ ] Enhancement
Problem Area
[ ] Page Transformation: Error during the setup/use of the Page Transformation UI solution (did you check our troubleshooting guide?)
[ ] Page Transformation: Error during the use of page transformation from PnP PowerShell
[ ] Page Transformation: Error during the use of page transformation from .Net
[ x ] Page Transformation: Page is not looking correct after transformation
[ ] Modernization Scanner: something went wrong...
Expected or Desired Behavior
Using the new publishing page layout mapping I try to convert a classic one third right column layout to a modern page using the following XML
<WebPartZones>
  <WebPartZone ZoneIndex="0" ZoneId="pageLayoutBRow1Left" Row="1" Column="1" />
  <WebPartZone ZoneIndex="0" ZoneId="pageLayoutBRow1Right" Row="1" Column="3" />
</WebPartZones>

I set the column value to 3 hoping that the one third right column layout is chosen for the modern page. But the chosen layout is 'two columns'.
Observed Behavior
Two column layout is chosen instead of One third right column layout
Steps to Reproduce

Create a classic page layout with at least two zones
Create a publishing page mapping file and configure the web part zones to use column 1 and 3 respectively. See xml above.
Perform transformation

Hey @robi26 ,
See #168 for an explanation on why this happens and a possible workaround

Thanks for the reference to the issue, didn't see that.
Setting the PageLayoutTemplate property to a specific layout works as long as you have only one row.  The problem arises as soon as you have more than one row or mixed layouts.
If you have multiple rows with the same layout I get the following error:
ConvertTo-PnPClientSidePage : Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
Set the PageLayoutTemplate="TwoColumnsWithSidebarRight"
The xml looks like:
<WebPartZones>
  <WebPartZone ZoneIndex="0" ZoneId="pageLayoutBRow1Left" Row="1" Column="1" />
  <WebPartZone ZoneIndex="0" ZoneId="pageLayoutBRow2Left" Row="2" Column="1" />
  <WebPartZone ZoneIndex="0" ZoneId="pageLayoutBRow1Right" Row="1" Column="2" />
  <WebPartZone ZoneIndex="0" ZoneId="pageLayoutBRow2Right" Row="2" Column="2" />
</WebPartZones>

When using mixed layouts the PageLayoutTemplate property on the page layout is too 'global' because the first row could be TwoColumnsWithSidebarRight and the second ThreeColumns

Why don't you specify all in the same row like this...this should retain your 1/3 and 2/3 split and I think the web part order should follow the web part zone order if I'm not mistaken.
<WebPartZones>
 <WebPartZone ZoneIndex="0" ZoneId="pageLayoutBRow1Left" Row="1" Column="1" />
 <WebPartZone ZoneIndex="0" ZoneId="pageLayoutBRow2Left" Row="1" Column="1" />
 <WebPartZone ZoneIndex="0" ZoneId="pageLayoutBRow1Right" Row="1" Column="2" />
 <WebPartZone ZoneIndex="0" ZoneId="pageLayoutBRow2Right" Row="1" Column="2" />
</WebPartZones>

That works if all rows have the same layout.
But we also have some page layouts having a 'special' design, something like this:

In this scenario the workaround does not work.

That design is anyhow currently not possible. We'll be shipping a continuous column as part of the home site release, once we have that capability we can re-evaluate this. There's nothing I can do short term here, hope you understand.

We now support a right side vertical column that spans the page. Will integrate using this for the October release

Moved to November release

@robi26 : with the November release you'll be able to transform publishing pages into modern pages that use a vertical column. See https://github.com/SharePoint/sp-dev-modernization/commit/ded7f1f6649ea8150a8f84d4ed89e4bea13b9990. Will close this issue now, if after testing with the November release you still have issues then please open a new issue with the needed details.

Thanks, that sounds great. I'll try it in November.


How to better avoid "Error: free joint can only be used on top level" when combining two models

I want to create separate xml files for robot,  object, arena and combine them together later.
Because all the objects are very similar, I decided to put all of them in one xml file. Each object are should move freely.
Something like this:
<mujoco model="objects">
  <worldbody>
    <body >
      <freejoint/>
      <geom>
    </body>

    <body >
      <freejoint/>
      <geom>
    </body>
  </worldbody>

Then I use .attach to combine two models: modelArena.attach(modelObject)
But, this will create an outside <body that wraps all <body from modelObject.
Something like this:
<mujoco model="arena>
  <worldbody>

<body name="objects">
    <body>
          <freejoint/>
          <geom>
    </body>
    <body>
          <freejoint/>
          <geom>
    </body>
</body>
  </worldbody>

Then I will get a problem "Error: free joint can only be used on top level".
I know one solution would be to create xml file for each object individually and let the attachment frame add('freejoint').
But this is not very elegant, and it will create many redundant attributes (like <default, because each xml file has the same default setting)
So is there any better way to achieve the same result? I tried to find a way to do without creating another <body that wraps all these but still haven't found one. Thanks!

From the MJCF documentation, it seems that the following is the only way at the moment to add a freejoint:
attachment_frame = parent_model.attach(child_model)
attachment_frame.add('freejoint', name=...)

Have you considered doing the combination in the XML, using the <include /> element? See the hammock.xml file in the example models, which can thought of as the arena, and the humanoid.xml it includes, which could be thought of as the objects.

For easy reference, the "hammock.xml"/"humanoid_body.xml" mentioned: https://github.com/deepmind/mujoco/tree/main/model/hammock
@Balint-H: My problem is that even though the <include /> format in your "hammock.xml" example works and is necessary when testing in "mujoco.viewer", once I try to programmatically attach the "humanoid_body.xml" to a different scene (e.g. when using dm_control.composer), then I get the error.
For example, this does not work:
from dm_control import mjcf, composer
from dm_control.locomotion import arenas

HUMANOID_XML_PATH = 'test/humanoid_body.xml'

class Humanoid(composer.Entity):
    def _build(self):
        self._mjcf_model = mjcf.from_path(HUMANOID_XML_PATH)

    @property
    def mjcf_model(self):
        return self._mjcf_model

robot = Humanoid()     # composer.Entity
arena = arenas.Floor() # composer.Entity
arena.attach(robot)

print(arena.mjcf_model.to_xml_string())

because it produces:
...
<worldbody>
    <geom name="groundplane" class="/" type="plane" size="8 8 0.25" material="groundplane"/>
    <camera name="top_camera" class="/" fovy="10.058147163570894" pos="0 0 100" quat="1 0 0 0"/>
    <body name="Humanoid body/">
      <body name="Humanoid body/torso" childclass="Humanoid body/body" pos="0 0 1.5">
        <camera name="Humanoid body/back" mode="trackcom" pos="-3 0 1" xyaxes="0 -1 0 1 0 2"/>
        <camera name="Humanoid body/side" mode="trackcom" pos="0 -3 1" xyaxes="1 0 0 0 1 2"/>
        <freejoint name="Humanoid body/root"/>
...

resulting in:
Error: free joint can only be used on top level

So the problem is what works for (1) mujoco.viewer doesn't work for (2) dm_control.composer. If I remove the <freejoint/> in the XML file, then use arena.add_free_entity(robot) then (2) works but (1) shows a fixed humanoid. Ideally, would like to find a solution for both to work. Any ideas?

Any updates on this? In my case, I need to add multiple robots (e.g. from mujoco_menagerie) onto an plane. I would have thought this would be simple to do but seems the freejoint issue prevents the straightforward solution with attach.


exact colour matching in shaders fails with when using floats

Godot version:
3.2.2 stable
OS/device including version:
linux mint
Issue description:
In the image you can see from a paint picker that the yellow is 255,255,0. Or 1.0,1.0,1.0 in Godot colours.
The cyan is 0,192,192. Or 0, 0.75, 0.75 in Godot colours.

However, when doing a colour replacement shader, the code will match the yellow fine, however the cyan has to be a fuzzy match, as shown below. I presume this is a floating point issue, but given the values I would expect it not to fail.
Apologies if I'm misinterpreting how shader colour comparison should be working.
shader_type canvas_item;

void fragment() {
	COLOR = texture(TEXTURE, UV);

        //this fails if use exact 0.75 so have to do the following. The colour is exactly 0.75 though
	if(COLOR.r==1.0 && COLOR.b>0.75 && COLOR.b<0.753 && COLOR.g>0.75 && COLOR.g<0.753) {
		COLOR.r=0.75;
		COLOR.g=0.0;
		COLOR.b=0.0;
	}

        //this works fine as it is 1.0
	if(COLOR.r==1.0 && COLOR.g==1.0 && COLOR.b==0.0) {
		COLOR.r=d;
		COLOR.g=0.0;
		COLOR.b=0.0;
	}
}

Steps to reproduce:
Minimal reproduction project:

Your not misunderstanding shader color comparisons, you are actually misunderstanding how floating point numbers work in general. Floating point numbers don't store exact representations. So floating point comparison using == is not guaranteed to be accurate.
You have to realize that the GPU does a lot of operations on the float when converting it into a texture and reading from the shader, so there is no guarantee that 0.75 is exactly 0.75 or 1.0 is exactly 1.0. It is pure chance that 1.0 is working for you. If you switch to another computer or update your driver's, it may no longer work.
In shaders you should always use a fuzzy comparison.

Thanks, that's why I said is it a floating point issue :)
This seems bad, how are you supposed to do an exact perfect colour replacement? what if I want exactly this colour and not a small fractional variation and how are you supposed to know what range to have, i.e. this would be fine with values in the range 0-255, seems overly vague when using 0..1 as a range.

This seems bad, how are you supposed to do an exact perfect colour replacement? what if I want exactly this colour and not a small fractional variation and how are you supposed to know what range to create, do you do a variance of 0.05, 0.1, will it work on another computer?, i.e. this would be fine with values in the range 0-255, seems overly vague when using 0..1 as a range.

Well you can't do this with computers :)
If you want exact comparison, use integers. Otherwise you have to use epsilons for comparison to account for precision errors. An epsilon (small value bigger than the precision errors, typically 10e-5 or 10e-4) shouldn't make a perceivable difference for Color values.

On, fair enough. In the olden days it wasn't hard to choose to use rgb as a
range of 0 to 255 😉
I'll rethink how I do it.
On Tue, 22 Sep 2020, 06:18 Rémi Verschelde<EMAIL_ADDRESS>wrote:

This seems bad, how are you supposed to do an exact perfect colour
replacement? what if I want exactly this colour and not a small fractional
variation and how are you supposed to know what range to create, do you do
a variance of 0.05, 0.1, will it work on another computer?, i.e. this would
be fine with values in the range 0-255, seems overly vague when using 0..1
as a range.
Well you can't do this with computers :)
If you want exact comparison, use integers. Otherwise you have to use
epsilons for comparison to account for precision errors. An epsilon (small
value bigger than the precision errors, typically 10e-5 or 10e-4) shouldn't
make a perceivable difference for Color values.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/42237#issuecomment-696512919,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADCERRKONRFXLIFMSOIUSB3SHAXTVANCNFSM4RVEGVNQ
.

I'm using this method to colour match in shaders currently:
bool colorMatch(vec3 c1, vec3 c2, float maxDiff) {
    return (
        abs(c1.r - c2.r) < maxDiff
        || abs(c1.b - c2.b) < maxDiff
        || abs(c1.b - c2.b) < maxDiff
    );
}

void fragment() {
    vec3 color = textureLod(SCREEN_TEXTURE, SCREEN_UV, 0.0).rgb;
    if (colorMatch(color.rgb, someColor.rgb, 0.01)) {
        COLOR = vec4(1f, 0f, 0f, 1f);
    } else {
        COLOR = vec4(0f, 0f, 0f, 0f);
    }
}

I'm using this method to colour match in shaders currently:
bool colorMatch(vec3 c1, vec3 c2, float maxDiff) {
    return (
        abs(c1.r - c2.r) < maxDiff
        || abs(c1.b - c2.b) < maxDiff
        || abs(c1.b - c2.b) < maxDiff
    );
}

void fragment() {
    vec3 color = textureLod(SCREEN_TEXTURE, SCREEN_UV, 0.0).rgb;
    if (colorMatch(color.rgb, someColor.rgb, 0.01)) {
        COLOR = vec4(1f, 0f, 0f, 1f);
    } else {
        COLOR = vec4(0f, 0f, 0f, 0f);
    }
}

FWIW if anyone's finding this through Google, the above code didn't work for me, but a tweak did. Changed colorMatch's 'or' to 'and' operator. Mine's no a screen shader either, for what that's worth.
bool colorMatch(vec4 c1, vec4 c2, float maxDiff) {
    return (
        abs(c1.r - c2.r) < maxDiff
        && abs(c1.g - c2.g) < maxDiff
        && abs(c1.b - c2.b) < maxDiff
    );
}

void fragment() {

	vec4 curr_color = texture(TEXTURE,UV); // Get current color of pixel
	float variance = 0.0001;

	if (curr_color.a == 1.0 && colorMatch(curr_color, exit_col_1, variance)) { curr_color = enter_col_1; }
	[repeat for howevermany colours you're swapping]

	COLOR = curr_color;
}


[CT-1197] [Bug] Schema Files not parsed for models at the right time

Is this a new bug in dbt-core?

[X] I believe this is a new bug in dbt-core
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
When we parse a model node, any configs set in the schema yaml file do not get incorporated until after the fact.
Specifically all nodes are considered enabled (if only disabled in the schema yaml file) while we parse through the sql files until we parse the schema file.  So they end up as nodes in the manifest to be processed and are not in the disabled dict.
Specifically the value of node.config.enabled will always be True when the node was set to disabled only in the yaml file.  It will probably be incorrectly set to False if it is set to False at the project level and overridden at the yaml level to be True.
https://github.com/dbt-labs/dbt-core/blob/f5a94fc77428426002ef2a908ebf57a32597a627/core/dbt/parser/base.py#L370-L374
There is also a bit of hacky logic as follows to ensure we don't resolve refs on disabled nodes even though the node is in the manifest.
TODO: add link to process_refs in parser/manifest.py after #5868 gets merged
            # if the node is disabled, no need to resolve the refs
            if node.config.enabled:
                _process_refs_for_node(self.manifest, current_project, node)

The above conditional should be removed when this gets resolved since we would no longer be resolving refs for disabled nodes.
Expected Behavior
Account for configs set in schema files.
Steps To Reproduce
A barebones project with 3 models:
-- my_model.sql
select 1 as user

-- my_model_2.sql
select * from {{ ref('my_model') }}

-- my_model_3.sql
select * from {{ ref('my_model_2') }}

A schema.yml like so:
version: 2
models:
  - name: my_model
  - name: my_model_2
    config:
      enabled: false
  - name: my_model_3
    config:
      enabled: false

run dbt run and examine manifest.nodes and manifest.disabled
Additional Context
#5868 fixed the bugs users are experiencing, this is to fix the underlying issue

@emmyoop Thanks for the thorough writeup!
The fundamental issue in the parsing order that you've identified here feels related to https://github.com/dbt-labs/dbt-core/issues/4000 as well. We instantiate snapshot nodes after parsing the .sql file, perform dataclass validation, check for specific configs, if they're not supplied we raise an error, before actually parsing the .yml file that might contain those configs.


Extend model to allow adjusters to record problems in the relevant spans

Coverage remained the same at 100.0% when pulling 4ae8d62cd1093909fe50ef7f63dcfa3ab877e86a on record-problems-in-spans into 0fe24722ea1d4e06ea76a6728dd25ae9a5dc87ed on master.

Coverage remained the same at 100.0% when pulling feb6c6cee6985512af6617ab096e2bdd4a4a9bed on record-problems-in-spans into 0fe24722ea1d4e06ea76a6728dd25ae9a5dc87ed on master.

Coverage remained the same at 100.0% when pulling 79c9214e1264e2bd242423f6032cb86a99ea8b03 on record-problems-in-spans into 0fe24722ea1d4e06ea76a6728dd25ae9a5dc87ed on master.

Coverage remained the same at 100.0% when pulling aa62f36c08d6ab50c1d6bb4a3a0f6c00aad167cd on record-problems-in-spans into 0fe24722ea1d4e06ea76a6728dd25ae9a5dc87ed on master.

Coverage remained the same at 100.0% when pulling f7864d480e5f08f8d85e5d15bd6456699e30c76a on record-problems-in-spans into 0fe24722ea1d4e06ea76a6728dd25ae9a5dc87ed on master.


Unable to update fee market state

We have an issue since a few days with Restake Cosmoshub:
TX 1: Failed 50 messages: unable to update fee market state: block utilization of 31858354 cannot exceed max block utilization of 30000000 with gas used: '31864524'
TX 2: Failed 50 messages: unable to update fee market state: block utilization of 31860901 cannot exceed max block utilization of 30000000 with gas used: '31867071'

with the following config:
  "cosmoshub": {
    "gasPrice": "0.005uatom",
    "restUrl": [
      "our rest URL"
    ],
    "autostake": {
      "gasModifier": 2.0,
      "batchPageSize": 30,
      "batchQueries": 1,
      "delegationsTimeout": 30000
    },
    "healthCheck": {
      "uuid": "healtcheckUuid"
    }
  },

I've tried to change:

restUrl
gasPrice
gasModifier
batchPageSize

Nothing changed :/ I have still the issue.
When I change the batchPageSize the length is still 50, is this normal?
[2024-08-28T09:11:44.552Z] info: Failed messages chain=cosmoshub module=network_runner error=unable to update fee market state: block utilization of 31860881 cannot exceed max block utilization of 30000000 with gas used: '31867051' length=50

Version used: v2.15.0

Reduce the batchTxs config - default is 50 but it must be too high at times for CosmosHub dynamic gas limit.
"autostake": {"batchTxs": 25}

Indeed, it worked, didn't see this parameter, thanks!

Totally my bad, I reaaally need to update the docs!


error CS1929: 'Sequence' does not contain a definition for 'WithCancellation' and the best extension method overload 'EnumeratorAsyncExtensions.WithCancellation(IEnumerator, CancellationToken)' requires a receiver of type 'IEnumerator'

In the unity

example with all installed dependencies, it gives this error, I can’t decide.
Error in all scripts related to animation

and you can also speak Russian, also, by the way, from Siberia

How did you manage this error?

How did you manage this error?

Please, use discussions to have conversations and post questions without opening issues.
https://github.com/ChebanovDD/Match3-SDK/discussions/10

Thank you, now it works.
On Mon, Apr 10, 2023 at 1:30 PM Dima @.***> wrote:

How did you manage this error?
Please, use discussions
https://github.com/ChebanovDD/Match3-SDK/discussions to have
conversations and post questions without opening issues.
#10 https://github.com/ChebanovDD/Match3-SDK/discussions/10
—
Reply to this email directly, view it on GitHub
https://github.com/ChebanovDD/Match3-SDK/issues/16#issuecomment-1501656922,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUD4EPK6LFIAQ4JIY5T6O63XAPOLVANCNFSM6AAAAAAWRAVYOU
.
You are receiving this because you commented.Message ID:
@.***>


Video Field Collection is_empty_alter

The video field collection needs to implement hook_field_collection_is_empty_alter.
Without this, field_collection_item id's without a video id are still created because there's a default value provided for "Video Provider".

seeing video collections still appear on campaign pages after the video id is removed
refs #5776


this token does not appear to be valid

When i try to get access to the teletype i crash into an error "this token does not appear to be valid". And Atom's notification is "Failed to authenticate to teletype. Signing in failed with error Unexpected response".

Description
I tried to search for that issue and to make simpler helping, here are screenshots of the responses.

and ice-servers:
��Q���N�W�.e(��N���}��https://cloud.githubusercontent.com/assets/16760489/19395499/69bbb780-922d-11e6-9779-2b8327027ea5.png�#�
�;])�.�puVT�
�G:F�https://chrome-devtools-frontend.appspot.com/serve_file/@7accc8730b0f99b5e7c0702ea89d1fa7c17bfe33/product_registry_impl/product_registry_impl_module.js(���^+b�.2DH�&ЁShttps://travis-ci.org/AtomLinter/l
Steps to Reproduce

Tap on teletype icon
Go to https://teletype.atom.io/login
Login via GitHub, get and copy token
Put token in the teletype's field

Versions
Teletype is the latest's 0.13.3 version.
Hope for helping.

Thanks for the report - just to confirm if this is specific to Teletype, do you have a similar problem if you try to login to the GitHub tab?  Also, can you share what operating system you're running and copy/paste the output of atom -v?

Thanks for the recent answer.
The OS os Windows 10.
Here is the output of the atom -v:

As for GitHub, the access is granted.

Were you able to get past that error @LigaFrost?
Sorry and just to clarify about the "GitHub tab", I meant in Atom for the GitHub package.  In the command palette, it's the "GitHub: Toggle GitHub Tab" command and like Teletype, will have you get a token from atom.io when you have a repository open with a github.com remote.

Now all works perfectly. As for solution: I did nothing to fix the problem. It just started working next day (like in issue #367). GitHub was working, if it could help you. Anyway thanks for answers:)

Now all works perfectly. As for solution: I did nothing to fix the problem. It just started working next day (like in issue #367). GitHub was working, if it could help you. Anyway thanks for answers:)


OCPBUGS-17164: Fix SELinuxprofile inherit issue

What type of PR is this?
/kind bug
What this PR does / why we need it:
In conjunction to PR#1904, this pr is also needed in order to fix the selinux profile inherit issue, do not inherit system container on all selinuxprofile. In additional, the .process suffix is breaking the profile install as well, so it is now removed.
Which issue(s) this PR fixes:
Fixes # OCPBUGS-17164
Does this PR have test?
Yes
Special notes for your reviewer:
Does this PR introduce a user-facing change?
None
In conjunction to PR#1904, this pr is also needed in order to fix the selinux profile inherit issue for [OCPBUGS-17164](https://issues.redhat.com/browse/OCPBUGS-17164), do not add inherit system container line when we have selinuxprofile inherit.

Codecov Report

Merging #1919 (d61538d) into main (db43880) will increase coverage by 0.02%.
The diff coverage is 100.00%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1919      +/-   ##
==========================================
+ Coverage   49.22%   49.25%   +0.02%
==========================================
  Files          72       72
  Lines        7033     7037       +4
==========================================
+ Hits         3462     3466       +4
  Misses       3437     3437
  Partials      134      134


Download link to dataset is broken

The download link to the MUSCIMA++ dataset is broken: https://ufal.mff.cuni.cz/jan-hajic-jr/MUSCIMA++_v0.9.zip
Can you upload it to a place, where it is revision-controlled and available for download? Maybe another git-repository?
Many thanks!

Found the data here


Animate: CSS - Refactor with Fancy

Animate: CSS - Refactor with Fancy

This update refactors the Animate component's CSS with Fancy.
This is especially important for Portal'ed components like Tooltips and
Modals to animate correctly, as the previous SCSS styles may / may not be
available/loaded correctly in the Portal'ed environments.
Bonus: Animate has also been refactored with Flow

Coverage remained the same at 100.0% when pulling 5e4e302f2d91d9846a5658259e9cc78b748270b5 on animate-fancy-refactor into 1cd64fa4b9a723e1181c87357f33b8cbbf1bbcc3 on master.

Gonna merge this one up!


deps: Temporarily use fork for @react-navigation/stack

(Much like we did for @react-navigation/bottom-tabs in c0b17bd32.)
To get chrisbobbe/react-navigation@a588dcee9, which I've published to NPM in<EMAIL_ADDRESS>It cherry-picks react-navigation/react-navigation@5a1987708, which fixes #5486, as noted there:
https://github.com/zulip/zulip-mobile/issues/5486#issuecomment-1261138257
So this fix will become unnecessary when we're on React Navigation 6; that's issue #4936.
Tested the bugfix on my iPhone 13 Pro running iOS 16.1, with and without "Debug with Chrome". The bug was fixed, and back navigation worked as expected, both with the swipe gesture and the back button.
Fixes: #5486

Sounds good, thanks! Merging.


copycat: 001 -> 002

Updated the release to version 002 which has some improvements.

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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 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

[ ] Fits CONTRIBUTING.md.

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

Please reword to copycat: 001 -> 002

Do I need to redo the commit message as well?

The commit message. PR title isn't that important

I hope I did it correctly now.


Trained model checkpoints available?

you have found? I download the models and data, and I found nothing but some strange data


convert some service classes to static props, run [bitbucket bitrise bountysource]

Warnings

:warning:
This PR modified service code for bountysource but not its test code. That's okay so long as it's refactoring existing code.

:warning:
This PR modified service code for bitrise but not its test code. That's okay so long as it's refactoring existing code.

:warning:
This PR modified service code for bitbucket but not its test code. That's okay so long as it's refactoring existing code.

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @calebcartwright!

  Generated by :no_entry_sign: dangerJS against 807d8687fce34977335b24bff9fe2a6ca983241c


(FACT-853) Add epoch for Redhat packaging

The last Facter release used an epoch, so now we're stuck with it.

The changelog at the bottom also needs the epoch added.


question random scheduling methods?

hello i want the details about random scheduling methods and how the steps to work in pox and mininet?

@mcanalesmayo


Minecraft block logo looks weird

The only reason I suggested the dirt background was to fix this issue and thought that this issue could be fixed as its in the mod not outside, I guess that was a waste of my time as the same issue happens here.
https://imgur.com/a/JPdq9Hy

????????
Could you send a crash report so I can see your system specs and such? (Hold F3+C for 10 seconds then release to force a crash, even in the menu)

No response, closing as cannot reproduce.


Add support for EC2 Spot Instance Termination notices

See https://aws.amazon.com/blogs/aws/new-ec2-spot-instance-termination-notices/

Done.


error when using crystal docs

Crystal 0.21.1 (2017-03-07) LLVM 3.9.1
Trying to re-generate docs for the crecto library.
If I comment out my model.cr file, everything works fine.
Error:
Unhandled type in `name`: Crecto::Model+:Class
0x1009789e3: *raise<String>:NoReturn at ??
0x102164896: *Crystal::Doc::Type#name:String at ??
0x10216efe6: *Crystal::Doc::Type#full_name_without_type_vars<String::Builder>:String::Builder at ??
0x10216f7cc: *Crystal::Doc::Type#full_name<String::Builder>:(String::Builder | Nil) at ??
0x10216c28b: *Crystal::Doc::Type#type_to_html<Crystal::NamedTupleInstanceType, String::Builder, Nil, Bool>:String::Builder at ??
0x10216d176: *Crystal::Doc::Type#type_to_html<Crystal::GenericInstanceType+, String::Builder, Nil, Bool>:(String::Builder | Nil) at ??
0x1021686d3: *Crystal::Doc::Method#args_to_html<String::Builder, Bool>:(String::Builder | Nil) at ??
0x10216696a: *Crystal::Doc::Method#id:String at ??
0x1021ba4a5: *Crystal::Doc::MethodSummaryTemplate#to_s<File>:File at ??
0x1021b1762: *Crystal::Doc::TypeTemplate#to_s<File>:File at ??
0x1021a8cbe: *Crystal::Doc::Generator#generate_types_docs<Array(Crystal::Doc::Type), String, Array(Crystal::Doc::Type)>:Nil at ??
0x1021a91ea: *Crystal::Doc::Generator#generate_types_docs<Array(Crystal::Doc::Type), String, Array(Crystal::Doc::Type)>:Nil at ??
0x1021934a5: *Crystal::Command#docs:Nil at ??
0x1009d73f0: *Crystal::Command#run:(Bool | Crystal::Compiler::Result | IO::FileDescriptor | Nil) at ??
0x1009a276d: main at ??

Error: you've found a bug in the Crystal compiler. Please open an issue, including source code that will allow us to reproduce the bug: https://github.com/crystal-lang/crystal/issues

I've reduced to:
class Bar
  property classes = Array(Foo.class).new
end

abstract class Foo
end

The crecto Multi references to the Model inheritors metaclasses.
  class Multi
    ...
    property delete_alls = Array(NamedTuple(sortorder: Int32, queryable: Crecto::Model.class, query: Crecto::Repo::Query)).new
    ...

Docs fails because there is no pretty name for that type. Using the internal to_s for those type would lead to Crecto::Model+:class shown in docs. Which is not that nice :-(

@fridgerator  Does it make sense to document Multi#delete_alls and Multi#update_alls to end users or is just an internal class. If so, # :nodoc: above those properties will allow you to publish the docs with the current crystal release.

@bcardiff Those are internal and I can use nodoc, thanks!

Cool :-)
If a public api needs to express those constraints reconsider this again.
To avoid the crash, for the record, I did:
--- a/src/compiler/crystal/tools/doc/type.cr
+++ b/src/compiler/crystal/tools/doc/type.cr
@@ -47,6 +47,8 @@ class Crystal::Doc::Type
       type.name
     when TypeSplat
       "*#{type.splatted_type}"
+    when VirtualMetaclassType
+      "#{type}"
     else
       raise "Unhandled type in `name`: #{@type}"
     end

Unhandled type in `name`: HTML::Pipeline::Filter+:Class
0x10bc629e3: *raise<String>:NoReturn at ??
0x10d44e896: *Crystal::Doc::Type#name:String at ??
0x10d458fe6: *Crystal::Doc::Type#full_name_without_type_vars<String::Builder>:String::Builder at ??
0x10d4597cc: *Crystal::Doc::Type#full_name<String::Builder>:(String::Builder | Nil) at ??
0x10d4571ad: *Crystal::Doc::Type#type_to_html<Crystal::GenericInstanceType+, String::Builder, Nil, Bool>:(String::Builder | Nil) at ??
0x10d4526d3: *Crystal::Doc::Method#args_to_html<String::Builder, Bool>:(String::Builder | Nil) at ??
0x10d45096a: *Crystal::Doc::Method#id:String at ??
0x10d4a44a5: *Crystal::Doc::MethodSummaryTemplate#to_s<File>:File at ??
0x10d49b762: *Crystal::Doc::TypeTemplate#to_s<File>:File at ??
0x10d492cbe: *Crystal::Doc::Generator#generate_types_docs<Array(Crystal::Doc::Type), String, Array(Crystal::Doc::Type)>:Nil at ??
0x10d4931ea: *Crystal::Doc::Generator#generate_types_docs<Array(Crystal::Doc::Type), String, Array(Crystal::Doc::Type)>:Nil at ??
0x10d47d4a5: *Crystal::Command#docs:Nil at ??
0x10bcc13f0: *Crystal::Command#run:(Bool | Crystal::Compiler::Result | IO::FileDescriptor | Nil) at ??
0x10bc8c76d: main at ??

Same issue here:
https://github.com/huacnlee/html-pipeline/blob/390fc8ec0b47172823df1863365b4971504791e6/src/html-pipeline/filter.cr


Update download script to use evaluated field + refactor of download script.

LGTM, awesome work! Will ping @abidlabs about this today.

Actually I tried running the code using the following command
python download.py --cache_dir ../../data/juz_amma -s 78 -v True -k True

and it seems to completely ignore the --cache_dir (its empty once the script finishes), but the audio is saved in a .tmp-RANDOM directory where the script was run from - can you check why this is happening?


Add linuxdeveloper.io to webring

Hello!
Thanks for putting this together. Very much appreciated.
The webring link is located at the very bottom of my page.
Thanks again

Couldn't find any content hosted on the site itself, everything links offsite to third parties.


Add mjml-python to community page

Add mjml-python to community page

Can you open a PR about this ? In the tooling section please

My bad, I meant this one : https://github.com/mjmlio/mjml/blob/master/doc/ports.mdOn 17 Mar 2024, at 03:24, mgd020 @.***> wrote:
Hi @iRyusa,
Do you mean this (source) section? I'm not sure how appropriate it would be to add the Python library there. I do not see any other libraries listed there.
I originally suggested the community page due to there being other libraries analogous to mjml-python, so to me it made sense to add it along side.
Keen to hear your thoughts.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>


Scan jobs are failing with "FATAL multiple targets cannot be specified" if scanJobCompressLogs is false

What steps did you take and what happened:
After installing trivy operator via helm with --set "trivyOperator.scanJobCompressLogs=false" no vulnerability reports are generated in cluster. The reported problem is FATAL   multiple targets cannot be specified.
Installing same chart in same cluster without the mentioned option fixes the problem.
What did you expect to happen:
Vulnerability reports are generated regardless of scanJobCompressLogs setting.
Anything else you would like to add:
After checking the job template we found the following:
containers:
  - args:
    - --cache-dir
    - /tmp/trivy/.cache
    - --quiet
    - image
    - --scanners
    - vuln,secret
    - ""
    - ""
    - --format
    - json
    - --server
    - <TRIVY SERVER URI>
    - <IMAGE TO BE SCANNED>
    - --slow
    - --image-config-scanners
    - secret
    - --list-all-pkgs
    command:
    - trivy

We tried to run the trivy command via cli with exactly the same arguments trivy --cache-dir /tmp/trivy/.cache --quiet image --scanners vuln,secret "" "" --format json --server <TRIVY SERVER URI> <IMAGE TO BE SCANNED> --slow --image-config-scanners secret --list-all-pkgs and did get the same error as specified above. It seems that the two empty string args are causing this issue.
Without scanJobCompressLogs flag the job definition is like:
containers:
  - args:
    - -c
    - trivy image --slow '<IMAGE TO BE SCANNED>'
      --scanners vuln,secret --image-config-scanners secret     --cache-dir
      /tmp/trivy/.cache --quiet --list-all-pkgs --format json --server '<TRIVY SERVER URI>'
      > /tmp/scan/<CONTAINER>.json &&  bzip2 -c /tmp/scan/<CONTAINER>.json
      | base64
    command:
    - /bin/sh

which does not contain these empty strings as arguments. And this configuration seems to work just fine.
Environment:

Trivy-Operator version: 0.16.0
Kubernetes version: v1.24.16
OS: not applikable

@Ingradi thank you for the input I'll take a look at it and update you


Design API to support fetching of "lookup data"

Verbs Supported: GET
Design route to support lookup data (states, colors, makes, models, years).
This data is read-only. Any maintenance will be via code updates.
I'm thinking a single path with composable query string options...

Implemented and tested, but I still need to update the api doc.

Just updated the api design doc. Closing.


Add k8s contiv-vpp-ui Helm support for arm64 platform - also to dev branch

Coverage remained the same at 76.189% when pulling f0ed4627cdfd1d5c2648b5c5ada08cf38f786903 on stanislav-chlebec:dev into f72b6ee88a490be2247424b4700a182547994474 on contiv:dev.

Is this still needed after merging master to dev? (https://github.com/contiv/vpp/pull/1469)

Superseded by #1469


Things that get thrown off-station should eventually be deleted.

See #565.
If you throw something into space it'll keep flying forever. It would be good if things thrown in this manner were somehow stopped.
For now the easiest way would just be flat deletion. In the future we could maybe make it so that things you throw off-map gravitate towards some form of debris field where they get stopped.

I don't think flat-out deleting them would be a good idea as there's always an off-chance it would be important enough to want to be recovered like the nuke disk or a mission critical item.
The main problem we had with CM was people shooting bullets into infinite space, but there's also the point to be made that those have gameplay value as well, like imagine you're traveling towards the station in the arrivals shuttle and a bunch of bullets suddenly slam into you because some traitor had the foresight to spray lead where the shuttle was coming from. (Bad Example)
I'm not really an engine guy but could we do something like decreasing the amount of calculations on stuff that flies out of range of the station?
Or maybe stuff slowly decelerates and drifts back towards the station?

I don't think flat-out deleting them would be a good idea as there's always an off-chance it would be important enough to want to be recovered like the nuke disk or a mission critical item.

The whole point is that it's basically impossible to recover them without admin help when they're just thrown into space like that.

like the nuke disk or a mission critical item.

SS13 automatically respawns the disk if it gets deleted.

The main problem we had with CM was people shooting bullets into infinite space

No, the main problem was items being thrown into space. Bullets despawned after a bit. Items did not.

The whole point is that it's basically impossible to recover them without admin help when they're just thrown into space like that.

So in SS14 should we fix this? Because we might as well just delete them if they're going to be impossible to retrieve without admin intervention. (This is not the ideal option)

SS13 automatically respawns the disk if it gets deleted.

Does SS14 have this functionality?

No, the main problem was items being thrown into space. Bullets despawned after a bit. Items did not.

My bad

(This is not the ideal option)

This is why I suggested an alternative at the bottom of the OP...

Does SS14 have this functionality? Should I make this issue a feature to implement this functionality?

Well we don't exactly have a nuke disk...

I personally like the debris field idea, could even have it be fluffed as a bluespace anomaly things end up drifting to in nearby space. Could have stuff from previous rounds turn up there etc.

#705 Is somewhat related
I'm wondering if we should do something like throwing stuff in space makes it travel slower like in real life, maybe just slow shit down that's thrown into space making recoverability a little easier.

torus topology so items wrap around and hit the other side of the station when

Fire bullets into space from one side of the station then run over to the other side to eat your own lead

I also like the items looping around the station SS13-esque.
What does it mean to be "off-station"?

The easiest way to define off-station is not being on a grid or shuttle. Though for things that aren't moving it's not so much of a problem, so for this issue it would be things not on a grid that are moving.

I also like the items looping around the station SS13-esque.

Well the thing is if I shoot something out of the station mass driver I expect it to stay off station, not hit the windows on the other side of the station after 5 minutes.

Usually in SS13 it has to not get stuck on several different z-levels before ending up on the other side of the station.
Are there any plans for recreating these "nearby" structures that randomly border each other?
If not, then I agree that just looping around is weird and dumb.
If yes, then passing into these different zones until it gets stuck on something seems fine to me even if it could lead to it ending up on the other side of the station.


Add user choice on existing output file; don't just overwrite target

Overwriting should not be a sane default, but neither are skip or ask (because some person could start a batch job and go AFK, just to find their encodings weren't done).
This adds a command line flag, together with an ask menu and a rename function (with tests). Renames are done based on the pattern that if a file name ends on _<number>, that number is incremented. If it doesn't, an _1 is appended.
@alexheretic I didn't ask you if you want this feature, so it's ok if you dont. But what do you think about it?

I think your answer points out very accurately the decisions to be done about design direction - how much the target of the app is to be used by users directly, or via scripting; and how much the user should need to know - about scripting or encoding.
E.g I would love to close #159 with hints to an easy shell scripting solution, as that averts feature creep imho. On the other hand, I am undecided as to the general direction in which I would want this project to go. (And obviously I have no authority whatsoever - It's your project and I am fine with that :) ) But an action about overwriting should not be left to scripting, since it's not a nuisance but data-critical and painful to get wrong.
It's ok for me to leave out the "ask" dialog, as I can imagine the use cases would be very few. On the other hand even ffmpeg by default asks if it should overwrite an output, and the code isn't very complex or prone to break in the future I think.
As for the renaming part - a friend actually raised the issue as I talked to him about the patch I was just starting; he brought up the idea, but I really liked about it, that you have an option wherein you neither overwrite some file nor abort prematurely (and possibly lose a day or more in which no rendering is done). I know the logic and tests are quite complex, and I don't think I have the energy to reduce the complexity, but we have tests and I think the feature could be quite handy.

Thanks for the feedback, I see your point!
I will adapt my changes as soon as I find time.


Two fixes:

JSON should go upstream with the correct MIME type
Fix "resolveString" to work around an issue with Groovy not properly handling non-ASCII text. (this fix is backwards compatible, but does lock things to UTF-8 solely)

(This should resolve #9)

👷 Still waiting for that sweet emoji support.


Added menu for sending messages of night events

TODO: needs tesing & further modification

Alright... then let's reopen this again :-)

Please update given the most recent changes :D Current master is 95% what game will run on. Discuss with me on Discord if you need. :)

If you have some time today before the game starts we could test this code on the server...
I think it would be a great quality of life improvement for the mods :)


Update README.md

Description
Readme document contains references to provenance prior to mainnet launch (April 20, 2021).  Updates include links to both testnet and mainnet configurations as well as minor status clarifications.
closes: #XXXX

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against correct branch (see CONTRIBUTING.md)
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Wrote unit and integration tests
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[ ] Added relevant godoc comments.
[ ] Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
[ ] Re-reviewed Files changed in the Github PR explorer
[ ] Review Codecov Report in the comment section below once CI passes

Linked in @jdfigure and @dcshock in case they have info they would like to see on the main repository readme/landing page.


How to Change FullScreen Mode on Screen Orientation Landscape

Version 3.4.1 automatically switches to full screen mode on landscape orientation. To disable the feature reactToOrientationChange can be used.

@sarbagyastha Need same update for your youtube_player_flutter


How to have .optional() survive during transform()

How would I keep a property as truly optional ({ a?:..}) in my resulting object after doing a .transform().
Take the example below, the property is correctly inferred as optional (a?:...) after parsing but before transforming.
However, after transforming, it no longer is optional.
const objectA = z.object({ a: z.number().optional() })

type A = z.infer<typeof objectA>;
// { a?: number  | undefined } <-- optional

const objectB = z.object({ a: z.number().optional() }).transform((x) => {
  return { a: x.a?.toString() };
});

type B = z.infer<typeof objectB>;
// { a: string  | undefined } <-- no longer optional

Is this what you are looking for?
const objectA = z.object( { a: z.number().optional() } )

type A = z.infer<typeof objectA>
// type A = { a?: number | undefined }

const objectB = z.object( { a: z.number().optional() } ).transform( ( x ) => {
    const a = x.a?.toString()
    if ( a ) return { a }
    return {}
} )

type B = z.infer<typeof objectB>
// type B = { a: string } | { a?: undefined }

If you found my answer satisfactory, please consider supporting me. Even a small amount is greatly appreciated. Thanks friend! 🙏
https://github.com/sponsors/JacobWeisenburger

Thanks! Yes, that's technically the result I want..but I'm not clear about the way to get there outside of this simple example.
I'm transforming many properties at once, each of which may be undefined. How would I do this with many properties?
const objectB = z.object( {
 a: z.number().optional(),
b: z.string().optional(),
c. z.string(),
...
x: z.string().optional(),
})

.transform( ( x ) => {

// a should be {a?: undefined}
// b should be {b?: undefined}
// c should be {c: string}
//etc.

} )

In zod, an optional property means that it could be undefined. I understand that it is confusing, because in typescript undefined and optional are 2 similar things, but not the same.


Default parameters changed Interpretation of Argument

I have the following keywords
dummy keyword
    [Arguments]  @{param}
    ${len} =  get length  ${param}
    FOR  ${Item}  IN  @{param}
        log to console  ${Item}
    END

dummy keyword with default
    [Arguments]  @{param}=@{EMPTY}
    ${len} =  get length  ${param}
    FOR  ${Item}  IN  @{param}
        log to console  ${Item}
    END

and a Testcase
dummy
    @{List} =  create list  Hello  World
    ${status}  ${unused} =  run keyword and ignore error  dummy keyword  ${List}
    ${status}  ${unused} =  run keyword and ignore error  dummy keyword  @{List}
    ${status}  ${unused} =  run keyword and ignore error  dummy keyword with default  ${List}
    ${status}  ${unused} =  run keyword and ignore error  dummy keyword with default  @{List}

This leads to the following output:
['Hello', 'World']
Hello
World
Hello
World
| FAIL |
Keyword 'dummy keyword with default' expected 0 to 1 arguments, got 2.

I encountered the following issue, that a List-Argument i pass to a Keyword is interpreted differently depending on if i define a Default-Parameter or not. Can someone explain this behavior ?
The attached file is a robot HTML Logfile but for GitHub i added a ".log" so it can be uploaded.
log.html.log
I use python 3.9 and robotframework 4.03 on Windows 10

List arguments do not accept default values. The problem here is that such situation isn't detected and reported as an error correctly.


Add explicit load method to lazyloadEncoder

This is to allow e.g. half precision loading and similar.

Added in latest pr


GSD Request

--- GSD JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v5.5 to before v5.16.8",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=670638477aede0d7a355ced04b569214aa3feacd",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=feffb6ae2c80b9a8206450cdef90f5943baced99"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "670638477aede0d7a355ced04b569214aa3feacd",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "feffb6ae2c80b9a8206450cdef90f5943baced99",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "perf/x86/intel/pt: Fix crash with stop filters in single-range mode\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.16.8 by commit feffb6ae2c80b9a8206450cdef90f5943baced99, it was introduced in version v5.5 by commit 670638477aede0d7a355ced04b569214aa3feacd. For more details please see the references link."
}
--- GSD JSON ---

This issue has been assigned GSD-2022-1000681


Configurable MongoDB exposed port

Added port_to_expose argument on init to configure MongoDB with different exposed ports

Codecov Report

Merging #245 (f89ca98) into master (b65c8a0) will decrease coverage by 22.65%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           master     #245       +/-   ##
===========================================
- Coverage   86.05%   63.40%   -22.66%
===========================================
  Files          27       27
  Lines         746      746
  Branches       70       70
===========================================
- Hits          642      473      -169
- Misses         80      256      +176
+ Partials       24       17        -7

Impacted Files
Coverage Δ

testcontainers/mongodb.py
100.00% <100.00%> (ø)

testcontainers/mssql.py
0.00% <0.00%> (-100.00%)
:arrow_down:

testcontainers/postgres.py
0.00% <0.00%> (-100.00%)
:arrow_down:

testcontainers/compose.py
0.00% <0.00%> (-98.37%)
:arrow_down:

testcontainers/elasticsearch.py
0.00% <0.00%> (-85.72%)
:arrow_down:

testcontainers/mysql.py
0.00% <0.00%> (-84.00%)
:arrow_down:

testcontainers/oracle.py
0.00% <0.00%> (-55.56%)
:arrow_down:

testcontainers/core/generic.py
77.14% <0.00%> (-8.58%)
:arrow_down:

testcontainers/core/container.py
70.83% <0.00%> (-6.25%)
:arrow_down:

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


Date Lock

What would it take to have Date Lock added to this project?
Thanks

Closed. Right now i don't see any reason to add date lock feature.

Would you add it for a consulting engagement? If so, let me know costs.

Hi Timofey
I have a need to date lock my code through your obfuscator.
Would you add it as a consulting engagement? Or inform my staff how to modify?
Greg Winterhalter
VP, Professional Services, PMP
d:925.804.6757 | f:<PHONE_NUMBER> |<EMAIL_ADDRESS>2603 Camino Ramon | Suite 200 | San Ramon | CA 94583
People | Project | Performance
Microsoft Gold Partner | PMI Global Education Provider | ISO 9001:2008 Certified
Inc 500 America's Fastest Growing Private Company | Fast 50 Asian American Business
From: Timofey Kachalov<EMAIL_ADDRESS>Sent: Tuesday, December 12, 2017 2:03 PM
To: javascript-obfuscator/javascript-obfuscator<EMAIL_ADDRESS>Cc: Greg Winterhalter<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [javascript-obfuscator/javascript-obfuscator] Date Lock (#116)
Closed. Right now i don't see any reason to add date lock feature.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/javascript-obfuscator/javascript-obfuscator/issues/116#issuecomment-351209625, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ASg3PAr459Eq-LXdDIS_E2-ypG9tdkElks5s_vf5gaJpZM4QQBYx.

Main problem of all features of this type - all code that will added with this feature can be tracked and removed by "third party" user, this is why i want to focus on transformations of AST tree - they can't be reverted.


atlas map axes range invalid options

I think the Axes Range All setting is incorrect for atlas maps - seems to be showing a calendar:

🙈


Integrate notebook and terminal into core project

Literally every time a new version of Spyder IDE comes out, either terminal, notebook or both get broken or just stop working. It would be AWESOME if you could integrate these two add-ons into the core project, so they get tested as part of the release process. I absolutely LOVE Spyder, but it is beyond frustrating to continually lose the functionality of these addons over and over and over again. I've become uber-gun shy about installing new versions because of this.
I waited months for notebook to get fixed, and now that it's working in 5.3.3. the terminal stopped working. So frustrating............

Hi @dkinneyBU sorry for all the troubles you are facing trying to install the plugins! Although I think we should still keep them as external plugins/packages, I also think that having some sort of workflow that at least checks the most used ones (like the Notebook and the Terminal) will help a lot to spot easily introduced incompatibilities or errors when doing changes over the Spyder source code. Just in case, what do you think @spyder-ide/core-developers

I assume that @dkinneyBU is using a conda installed Spyder, rather than the standalone application, since the Notebook plugin is not installed for the standalone.
Perhaps we could implement a test similar to the macOS standalone test, which is to just launch the application and ensure that errors are not raised.
For starters, we could just include all external plugins (that work) in the spyder-ide account.

Ideally, we could do an actual integration test and run the plugin's test suite, and or a quick manual integration check, at least once prior to final release.

For starters, we could just include all external plugins (that work) in the spyder-ide account.

Huh?

@mrclary I install everything via conda, and usually with -c conda-forge.
I understand your desire to keep them separate, but the various suggestions to include them in your test suite would at least catch the major issues. I'm sure with Macs, PCs, linux boxes, all running different versions of OS and Python, you'll never catch everything (nor should anyone expect you to) but if you could catch the biggies before a release, that would likely eliminate some frustration in the community.
This is STILL the best IDE around. You folks do a commendable job.

This is STILL the best IDE around. You folks do a commendable job.

@dkinneyBU, thanks for the kind words!
Just to clarify my suggestions, in order of increasing difficulty/complexity:

Just launch Spyder. This is the easiest thing to do, but only checks that Spyder doesn't crash. It won't check any functionality.

Just create a conda environment on CI that includes specific plugins (spyder-terminal, spyder-notebook, or whatever)
Launch Spyder. Do errors occur or not?

Run a plugin's test suite. This would check a plugin's functionality, but requires that a plugin actually have a test suite as part of the conda package that is intended to be run after installation (as opposed to CI unit tests).

Create a conda environment on CI that includes specific plugins.
Run each plugin's test suite. Do they pass?

For starters, we could just include all external plugins (that work) in the spyder-ide account.

Huh?

There are potentially two sources for plugins: what we refer to as "external" plugins, but reside in the spyder-ide account, e.g. spyder-terminal, spyder-notebook, and spyder-vim (any others?); and true third-party plugins (do these even exist?) in some other github account.
If we are going to test plugins, it makes sense to limit the list of plugins tested. At first that list would be limited to those in the spyder-ide account (i.e. exclude third-party plugins), and further limited to those we expect to actually work (i.e. exclude experimental plugins)
But perhaps I was being overly general since there appear to only be 3 plugins to worry about 😄

That works for me, the only two I use happen to be terminal and notebook. :-)

@mrclary I created a separate environment and just installed spyder, spyder-terminal, and spyder-notebook. Same results.
But wait, there's more!
This machine is showing Python 3.10.6 in the Console. On a whim, I went through the same install process on my gaming laptop (both machines are running Windows 11). Terminal is working on that install, but this one is showing 3.9.12.
So, maybe this is indeed a Python 3.10 thing. There is also an issue opened for that, I will go update it with same. So consider this just FYI. :-)

If we wanted to go for quick and dirty, we could add to the instructions in RELEASE.md that at the same time when a message is send to the translators (a week before release), you also send a message to the maintainers of the main plugins, or maybe just open an issue against each of the plugins. That should hopefully alert them to test manually.


Link for NFDI4Microbiota domain on biotools is broken

The link for the NFDI4Micro biotools is broken on the knowledge base page: https://knowledgebase.nfdi4microbiota.de/Software-Development/02-toolsurvey.html

checking

If I am not to late, I am already working on this, along with updating all of the broken links, and removing the duplicates


Fix NSInteger -> long conversion for 32bit builds

Codecov Report

Merging #56 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master      #56   +/-   ##
=======================================
  Coverage   93.11%   93.11%
=======================================
  Files          44       44
  Lines        2557     2557
=======================================
  Hits         2381     2381
  Misses        176      176

Impacted Files
Coverage Δ

LayoutTest/TestCase/LYTLayoutTestCase.m
91.66% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e1065b0...dd9f7bd. Read the comment docs.


ESP32 swapped A0/A3 and GPIO36/39

In the ESP32 model, Pins GPIO36, ADC1_CH0, S_VP and GPIO39, ADC1_CH3, S_VN are swapped but have VP and VN as the correct imprint on the board. Test-projects:
Analog values https://wokwi.com/projects/388882778029965313
Digital values  https://wokwi.com/projects/388882863434397697
What will happen to existing projects, when you correct the device? Will the router swap the signals too?
One easy Q'n'D fix would be to change the picture of the esp32 and use 36/A0 instead of VP (now VN)... or simply swap VP and VN.
best regards
Bernhard

Thanks for spotting this!
Confirmed this is an issue by looking at the ESP32-DevKitC pinout in Espressif's documentation:

Uploading a fix.


[stable/moodle] fix upgrading existing deployments

What this PR does / why we need it:
In https://github.com/helm/charts/pull/17301 the apiVersion of the deployment resource was
updated to apps/v1 in tune with the api's deprecated in k8s 1.16. This change however breaks
upgradability of existing moodle deployments with helm v3 (rc) as described in
https://github.com/helm/helm/issues/6646.
To fix this, we have defined a moodle.deployment.apiVersion helper that returns the new
apiVersion only when k8s 1.16 or higher is in use.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

On hold until https://github.com/helm/charts/pull/18704 is merged, after which dependencies will be updated in this PR.


Add RFS GPIO support

Add support for triggering RFS via a GPIO line.

I think 10 seconds is quite common. 30 s is too long, it's a pain to keep it pressed that long.

Updated just to take out the CHANGELOG.md edit.


Update scalacheck to 1.14.2

Updates org.scalacheck:scalacheck from 1.13.5 to 1.14.2.
Release Notes/Changelog
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalacheck", artifactId = "scalacheck" } ]

Applied Migrations

github:typelevel/scalacheck/v1_14_1?sha=3fc537dde9d8fdf951503a8d8b027a568d52d055

labels: semver-minor, scalafix-migrations

Codecov Report

Merging #333 into develop will decrease coverage by 0.06%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop     #333      +/-   ##
===========================================
- Coverage    61.29%   61.23%   -0.07%
===========================================
  Files           50       50
  Lines         1540     1540
  Branches        40       40
===========================================
- Hits           944      943       -1
- Misses         596      597       +1

Impacted Files
Coverage Δ

...a/com/twitter/bijection/CollectionInjections.scala
93.54% <0%> (-3.23%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b606200...cb33859. Read the comment docs.


[hotfix][hbase]Fix HBaseRowInputFormat cannot get the zk address set in the table pr…

What is the purpose of the change
Because the Configuration in HBaseRowInputFormat cannot be serialized, the task cannot obtain the zk address set in the table parameter, which prevents the task from connecting to Hbase.
Because the default value of hbase.zookeeper.quorum is localhost, the unit test is ok
Brief change log
Fix failure to read hbase table
Verifying this change
no
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? not documented

cc @zentol @fhueske  can you review this for me if you have time, thanks ~

@flinkbot go


[feature request] alternative geometry columns

Huge thank you for making such a wonderful tool! It has been an excellent for projects I have been working on (including tree equity score).
Request: to be able to assign the geometry column used in the config.toml file. At the moment, the column needs to be set as geom and I often use multiple geometries when developing and it would be nice to be able to switch between these different geometries (i.e. geom1, geom2) without modifying my database and instead just updating the config.toml file

Hey @rohitmusti, you can do that already in the provider layers.
[[providers.layers]]
name = "landuse"
geometry_field = "foo"
sql = "SELECT gid, ST_AsBinary(foo) AS foo FROM gis.rivers WHERE geom && !BBOX!"

should suffice. Does also work when the provider is mvt_postgis.

Thank you, I can't believe I missed that.!

@rohitmusti Tree equity score looks like a great project and it's great to hear that tegola can be part of it.


Update python310Packages.snowflake-connector-python to 2.7.12

Checklist

[X] Checked the nixpkgs master branch

[X] Checked the nixpkgs pull requests

Project name
nix search name: python310Packages.snowflake-connector-python

current version: 2.7.9
desired version: 2.7.12
Notify maintainers

maintainers: @mweinelt
Note for maintainers
Please tag this issue in your PR.

maintainers: @mweinelt

Uh, no. The package simply has no maintainer.

Sorry if I tagged you in error -- I just went by the instructions that suggested tagging the last person who made the change when there is no designated maintainer. Maybe this could be an opportunity for me to learn some light package updates. :)
Cheers!

This has been updated to 2.8.0 in master now, so I'm going to close this issue.

Thank you!


Tests (and other fixes)

Major changes in this PR, besides the addition of tests:

Refactored the consumers code. One of the tests showed it not actually working properly (not cleaning up consumer set for queues that didn't have any active consumers), and I wanted to refactor it to be a bit more readable and testable anyway. So I did that.

Made QSTATUS take in an optional list of queue names. This was mostly to aid in testing, but it could be useful to users too. Also, made the output be more human readable.

Made clients.Client hold onto a ClientConn instead of a net.Conn. A ClientConn is an interface I made up which encompasses all the features we need out of a net.Conn, while still allowing us to essentially fake a network connection in our tests.

So I don't really like that we increased the complexity of the consumers operation (having to scan and serially correct each queue) but this works whereas it was broken previously. We should plan on trying to make that simpler later.
Everything else looks good!

I rebased this a bit and merged, last commit of it is 0d3d13.


Backport 2.7: Correct length check for DTLS records from old epochs.

This is a backport of a particular commit #52c6dc64c675d24b1be65e06d43dd67dc111e762 added in #946.
Before submitting this PR I have reviewed the original commit and ran ssl-opt and compat.sh locally, having both of them pass.

Travis passed and Jenkins only failed in the known-fragile timing test on BSD, so as good as a pass.
This PR doesn't have any ChangeLog entry, but the original PR didn't include an entry for this particular change either (and the issue was not reported externally) so lack of a ChangeLog entry is acceptable.
This has been approved and tested, so labeling "ready for merge".


Cannot see the string 'Auto Rotate' if the black part covers on the string when previewing one .glb file

Storage Explorer Version: 1.34.0-dev (98)
Build Number: 20240316.1
Branch: main
Platform/OS: Windows 10/Linux Ubuntu 22.04/MacOS Sonoma 14.4(Apple M1 Pro)
Architecture: x64/x64/x64
How Found: From running test cases
Regression From: Not a regression
Steps to Reproduce

Expand one storage account -> File Shares.
Open one file share -> Upload one .glb file that contains black part when it's being previewed.
Select the file -> Click 'Preview' -> Try to zoom in the preview content to cover the string 'Auto Rotate'.
Check whether it is clear to see the string.

Expected Experience
It is clear to see the string.
Actual Experience
Can't see the string.

Verified this issue on the main build 20240319.1. Fixed. So, we are going to close it.


Reset Button

As a user, I should be able to clear all of my changes on edit screen, resetting it to the last state.

Refer PR- 28 for changes.


Appstudio update mvp-test-component

Pipelines as Code configuration proposal

Pipelines as Code CI/mvp-test-component-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
6 seconds
init

✅ Succeeded
18 seconds
clone-repository

✅ Succeeded
1 minute
build-container

✅ Succeeded
12 seconds
sanity-inspect-image

✅ Succeeded
10 seconds
deprecated-base-image-check

✅ Succeeded
1 minute
clamav-scan

✅ Succeeded
18 seconds
clair-scan

✅ Succeeded
14 seconds
sbom-json-check

✅ Succeeded
14 seconds
sanity-label-check

✅ Succeeded
14 seconds
sanity-optional-label-check

✅ Succeeded
5 seconds
show-summary


Upgrading rimraf broke moves of filenames containing [ and *

The new version of rimraf expands globs by default.  This breaks node-mv if you try to move files containing glob characters.
To fix this, you should explicitly pass { disableGlob: true } as the second option to rimraf whenever it is used.

Fuck, what a disaster.

They changed that in a minor version upgrade?!

Fixed by aed9a5c688a7f7ee760


Aligned the logo and badges

Aligned the logo and badges on the top of README in the center

@bryphe @CrossR any idea why appveyor might be hanging here?

Change looks great, thank you @gebeto ! Bringing it in now.

That is, we skip building markdown only changes, but AppVeyor doesn't have any way of reporting a skipped build. Its not the problem of the changes, more just AppVeyor wanting GitHub to add a skipped state

Ya, that's a bummer.. thanks for the heads up


Bump version to 0.15.0

Bumps the version from 0.14.0 to 0.15.0
This version bump is on the merged PR https://github.com/k8s-ruby/k8s-ruby/pull/44
this version will start supporting ruby 3.2.2

How long until this makes it to rubygems.org?

We will be releasing this by today @zakainsworth.


bug: Some invalid queries get exposed as "unknown" or "Intenal" instead of "ValidationError" or "BadRequest" in micrometer

Expected behavior
When modifying the GraphQL request and sending a variable that is not in the query, I would expect it to get exposed as ValidationError or BAD_REQUEST in micrometer.
Actual behavior

When modifying the GraphQL request and sending a variable that is not in the query, it gets exposed as errorType unknown in micrometer.
When modifying a federated GraphQL request and sending a variable that is not in the query, it gets exposed as errorTyoe INTERNAL in micrometer.

This is preventing me to exclude client errors from our alerting that we base on these metrics.
Steps to reproduce
I think the behaviour description is pretty self explanatory. Please let me know if something is not clear.
But I'd like to provide some additional information.

When the error type "unknown" is exposed, the exception that DgsGraphQLMetricsInstrumentation->instrumentExecutionResult receives is graphql.execution.InputMapDefinesTooManyFieldsException: The variables input contains a field name 'myDemoKey' that is not defined for input object type 'MyDemoInput' . The ErrorUtils.sanitizeErrorPaths() call then sets the type to unknown.
When the error type INTERNAL is exposed,  the exception that DgsGraphQLMetricsInstrumentation->instrumentExecutionResult receives is TypedGraphQLError{message='java.lang.IllegalStateException: Expected key 'myDemoKey' in received federated values map does not exist.', locations=[], path=[_entities], extensions={errorType=INTERNAL}}. The ErrorUtils.sanitizeErrorPaths() call then sets the type to INTERNAL.

Thanks @hpuac, it should be consistent with BAD_REQUEST in both cases.

Closing this issue since it should be addressed in the latest release. Please reopen, if issue exists.

Hey @srinivasankavitha, sorry for the delay but I was now able to re-test it with DGS 5.0.5.
The following errors are still not exposed to micrometer as expected:

Exposed as INTERNAL: {"message":"com.netflix.graphql.dgs.exceptions.MissingFederatedQueryArgument: The federated query is missing field(s) __typename","locations":[],"path":["_entities"],"extensions":{"errorType" :"INTERNAL"}}
Exposed as unknown: {"message":"Variable 'representations' has an invalid value: Variable 'representations' has coerced Null value for NonNull type '[_Any!]!'","locations":[{"line":1,"column":23}],"extensions":{ "classification":"ValidationError"}}
Exposed as unknown: {"message":"Variable 'input' has an invalid value: Variable 'input' has coerced Null value for NonNull type 'MyDemoInput!'","locations":[{"line":1,"column":36}],"extensions":{"c lassification":"ValidationError"}}
Exposed as unknown: {"message":"The variables input contains a field name 'myDemoName' that is not defined for input object type 'MyDemoInput' ","extensions":{"classification":"ValidationError"}}
Does not get exposed to micrometer as error at all: {"message":"The query is null or empty.","locations":[],"extensions":{"errorType":"BAD_REQUEST"}}

Hey @berngp and @srinivasankavitha, should I create a new issue or will you reopen this one? 🙂

Let's keep this one.

@berngp do you have the rights to reopen it? I don't have any button for it.


Add metrics for Worker RPC counts

This PR aims at adding metrics for tracking the number of active RPCs handled by the Alluxio worker.

Codecov Report

Merging #13481 (03b2347) into master (2ebe171) will decrease coverage by 19.98%.
The diff coverage is 34.35%.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 70ca3cf...03b2347. Read the comment docs.

https://github.com/Alluxio/alluxio/issues/13480
Could you please also add Alluxio master related rpc metrics?

@ZhuTopher could you verify that we don't already get some RPC statistics for free from this line https://github.com/Alluxio/alluxio/blob/696647645c30d3a63b4a197aa0dfce9e11df3c39/core/server/common/src/main/java/alluxio/RpcUtils.java#L111
@ggezer AFAIK, these counters are meant to measure how many concurrent requests we are serving at a particular instant in time, not an aggregate count of how many reads and writes we did.
@calvinjia could you confirm that is the requirement here?

@yuzhu Referring to https://github.com/Alluxio/alluxio/blob/696647645c30d3a63b4a197aa0dfce9e11df3c39/core/server/common/src/main/java/alluxio/RpcUtils.java#L111
The only worker-owned pieces of code calling RpcUtils which would use that metric is BlockWorkerClientService. The methods/operations are the following:

asyncCache
removeBlock
moveBlock
clearMetrics

From what I can tell, the readBlock and writeBlock methods in this class flow down into the BlockReadHandler and BlockWriteHandler where I added the RPC metrics. So I think the answers to your question is no?

@ZhuTopher i see, yeah streamingRPCs do not use RPCUtils.
https://github.com/Alluxio/alluxio/blob/3762d75eb611f388895ad9bea0746b17afc7cdd1/core/transport/src/main/proto/grpc/block_worker.proto

alluxio-bot, merge this please


Added Enron Email Dataset Link

Added a link to the enron email dataset page (current download size 1.7 GB)

s


cro3.bash: Handle if there are short and long options

If an option parameter has short and long formats, those are connected with comma and space. e.g. "-v, --verbosity".
This checks the first format ends with ',' (and removes it). In that case, parses the 2nd word as an option.

@mhiramat sorry for the late reply...
The code itself looks good. Can you add a test that covers this case? Thank you!


RUMM-1963 Automatic update Flutter SDK

What does this PR do?
Create a PR on Flutter SDK repo whenever a new version is released

Codecov Report

Merging #846 (35afb6d) into release/1.12.0 (5657d59) will decrease coverage by 0.13%.
The diff coverage is n/a.

@@                Coverage Diff                 @@
##           release/1.12.0     #846      +/-   ##
==================================================
- Coverage           80.45%   80.32%   -0.13%
==================================================
  Files                 254      254
  Lines                8533     8533
  Branches             1458     1458
==================================================
- Hits                 6865     6854      -11
- Misses               1322     1330       +8
- Partials              346      349       +3

Impacted Files
Coverage Δ

...android/rum/internal/ndk/DatadogNdkCrashHandler.kt
83.13% <0.00%> (-4.82%)
:arrow_down:

...g/internal/domain/event/DdSpanToSpanEventMapper.kt
94.23% <0.00%> (-3.85%)
:arrow_down:

...ain/java/com/datadog/opentracing/PendingTrace.java
58.97% <0.00%> (-0.85%)
:arrow_down:


Font Family inconsistent

Noticed multiple fonts on the web page. Stick with the font family which says "We are OSL VVCE.".
It is a sans-serif font and the rest of the webpage uses serif fonts.

Also the font sizes are not working in the website overall. Consider reducing the size of fonts, especially in the contacts part. @sanjithpk


syzkaller: add reinforcement-learning-based task and seed selection

Use Multi-armed-bandit(MAB) algorithm to 1) schedule generate/mutate/triage
task to run and 2) select seed to mutate.
Working on unit tests.
Detailed changes:
pkg/instance, pkg/mgrconfig: add two individual toggles of MAB task/seed
selection.
pkg/mab: some basic data structures that will be used.
pkg/rpctype, syz-manager: synchonization of MAB status between manager and
fuzzer. Useful for state restoring when fuzzer
crashes. Only works well on one fuzzer for now.
syz-fuzzer/mab*: core logic of MAB algorithm.
syz-fuzzer: modify existing tasks to collect coverage and timing informations.

Before sending a pull request, please review Contribution Guidelines:
https://github.com/google/syzkaller/blob/master/docs/contributing.md

Hi @SoveraNia,
Thanks for working on this. I am aware of the great results you achieved.
I have not looked at the code in detail. But this adds 1000 lines of code and 0 tests. This is not right. Even if it works now it will break tomorrow. Please factor as much code as possible into testable units and add tests.

Hi @dvyukov,
Thanks for the feedback. I will definitely work on unit testing to match the engineering standard.
A few other things I'm considering.

Right now I'm super uncomfortable how the new scheduler is littered in syz-fuzzer. I tried moving them outside into pkg/mab but they need access to many Fuzzer internals (e.g. workqueue, program execution control, corpus, etc). Is there any way to make this cleaner?
To Prog, I added a data structure to track its coverage and timing information. This forces me to split MAB functionality into two different locations to avoid cyclic dependency. (reward_struct <- prog <- mab_scheduler) Any suggestions on how this should be refactored?

Please let me know if you have any other refactor suggestions.
Thanks,

Hi @SoveraNia,
Just to let you know, this is on my radar. I am just paged out by some intern-season preparation work. I hope to look at this in more detail tomorrow.

Hi @dvyukov,
Do you think it's helpful to split this huge PR into several smaller PRs? Here is a list of relatively independent components I can think of right now:

Logging maxSignal alongside corpusSignal and corpusCover. This is useful since the RL algorithm is currently optimizing for maxSignal.
Modify execute() and triageWork() to obtain timing and coverage information. (might merge with one of the following two)
Seed selection with reinforcement-learning
Task selection with reinforcement-learning
Synchronization of reinforcement learning result between syz-fuzzer and syz-manager.

What do you think?

Hi @dvyukov,
Do you think it's helpful to split this huge PR into several smaller PRs? Here is a list of relatively independent components I can think of right now:

Logging maxSignal alongside corpusSignal and corpusCover. This is useful since the RL algorithm is currently optimizing for maxSignal.
Modify execute() and triageWork() to obtain timing and coverage information. (might merge with one of the following two)
Seed selection with reinforcement-learning
Task selection with reinforcement-learning
Synchronization of reinforcement learning result between syz-fuzzer and syz-manager.

What do you think?

Yes, please, it will make it much easier to review and move incrementally.
pkg/mab with all of the abstract math logic is a good candidate as well. It can be separated from all of its uses and well tested with fast unit tests.
I am also interested in how easy it will be to reuse the mab for other choices (mutations, etc). It existing MAB logic seems to be closely tied to existing 2 use cases, while I expected to see something like a more abstract MAB logic, e.g. N choices, some abstract reward notion and then the MAB machinery selects 1 out of N. Are there reasons why this is not possible? I need to admit I still did not look very too closely at all the details.

Since we have decided to break this up into smaller pieces. Shall we withdraw this PR as it will no longer being maintained? I wonder whether it's possible to retain the conversation for future references.
I think it will be a brilliant idea that this MAB engine can be extended to other choices. The current engine is tailored towards the unique traits of task scheduling (association between tasks) and seed selection (ever-growing number of choices). The reward function is also going to be vastly different, should we want to extend it to other parameters. I'll definitely keep this in mind when refactoring the MAB engine for future PRs.


Fix panic with weapon procs

This doesn't fix the underlying problem that the proc effect target is never actually populated when a new magic item is generated. This is just treating the symptom, not the problem.


duplicate definition JSONModel Property Compatibility

I use cocoa pods  'user_framework!'
so  I get the warning "duplicate definition JSONModel Property Compatibility"

https://github.com/jsonmodel/jsonmodel/blob/master/CONTRIBUTING.md#bugs

Open a new issue conforming to the contribution requirements and we'll get it fixed


merge package template from Kronos-Tools/npm-package-template

Updated standard to latest version

Codecov Report

Merging #173 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #173   +/-   ##
=======================================
  Coverage   98.14%   98.14%
=======================================
  Files           1        1
  Lines         108      108
=======================================
  Hits          106      106
  Misses          2        2

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c2ae7f7...81face9. Read the comment docs.


Fix and simplify CI caching

Objective
Currently, the CI cache is only renewed when the Cargo.toml files are updated. However, when a patch dependency is released which is compatible with the Cargo.toml, the CI cache will be outdated and the dependencies will need to be recompiled every time.
Additionally, our CI workflow definitions are quite verbose, because the cache paths need to be defined every time.
Solution
Use the Leafwing-Studios/cargo-cache action.
It generates the Cargo.lock file before determining the cache key, such that the exact dependencies can be used to keep the cache up-to-date and avoid recompiles. The cache falls back to similar previous caches to avoid completely starting from scratch.
This also reduces a lot of boilerplate in the CI definitions.
Additional Context

The cache is only updated when the key is not already available. This is why the Cargo.lock file should be part of the cache key, because it determines exactly which dependencies are used.
The Cargo.lock file is not committed to the repository, because this is not recommended for libraries. This is why the Rust toolchain action must be used before the cargo-cache action, because it uses the cargo update command to generate the Cargo.lock file.
For Leafwing-Studios/Emergence, this reduced our CI times from ~15 min to ~2 min.

Security Considerations
Adding a new third-party action increases the attack vector and should be considered carefully.
I recommend to audit the action first, it should be easy enough to understand (it's very similar to the current system we use) and I tried to add as many comments as possible.
I also published the action under the Leafwing org to get additional eyes on every PR (e.g. Alice).
If you'd prefer, we can also target an explicit commit of the action instead of a tag, to ensure that updates can be audited properly.

As a small example, notice how in this CI run, there was a cache hit, but still some dependencies had to be downloaded and recompiled.

At a glance, doesn't this break caching of the cargo registry, cargo binaries, etc if cargo update is run before the cache is set up?

In theory yes, but in practice this doesn't seem to matter compared to the compile times that are saved. For example, in Emergence, the toolchain action takes 12s and the cache action with cargo update takes ~1m.
Probably not ideal, but the compile step then only takes 4s which is a huge win.
I also experimented with caching the binaries before the cargo update step, but that didn't seem to make a big difference.

The cache falls back to similar previous caches to avoid completely starting from scratch.

Is this behavior explained somewhere?

This is implemented via the restore-keys attribute of the cache action, see the caching docs.
It basically allows you to fall back of prefixes of cache keys.
We first fall back to the same Cargo.toml file when the Cargo.lock file is outdated and then to the same workflow job if the Cargo.toml file is outdated.
You can view it in the action definition here.

This has been working great for us in practice, but I'll abstain from reviewing this myself.


pypi overwrote 0.4.1

Looks like you guys somehow uploaded version 0.4.1 to pypi and overwrote the previous "version" of 0.4.1 with different code.
Might wanna upgrade the version before pushing to pypi, this broke stuff for us.

 I wanted to just add a wheel to the old release.
I removed the incorrect wheel from 0.4.1 on PyPI to restore the old behaviour, and published a new version, with a wheel, as 0.5.


Odemetry misspelling

We have two options here:

change all instances of "odemetry" to "odometry"
just stick with "odemetry" for this entire project

Pros of "odometry":

Proper spelling

Pros of "odemetry":

Meme potential

k we're keeping it at odemetry