Using 'husky attach' inside multi-project solutions leads to compile errors due to 'husky install' running multiple times

Version
v0.4.4
Details
After you run dotnet husky attach someproject.csproj, and doing so on multiple projects inside a solution to ensure people working on individual projects are forced to use Husky (in my case: formatting in pre-commit hook), leads to the following error:
The process cannot access the file 'D:\Projects\MyProject\.husky\_\.gitignore' because it is being used by another process.
error MSB3073: The command "dotnet husky install" exited with code 1.

It is clear that the error is caused by the parallel build feature of MSBuild, as each project in a solution is being build. I have not yet found a stable, different way of ensuring the dotnet husky install is run only once.
Hand-crafted ways that probably work is do a file-exists test of the .husky folder. But by itself, that is not enough, as Husky won't run unless core.hooksPath of Git is set to .husky, which this command so conveniently does.
Ideally, dotnet husky install should not lock files it reads, or use a mutex of sorts (available cross-platform in dotnet nowadays) to prevent it from running multiple times.
Alternative, without using exclusive locks, dotnet husky install could just check if Husky is already installed and of the correct version. But that still leaves the issue that, if it is not installed yet, that "Rebuild All" will have multiple parallel dotnet husky install running.
Steps to reproduce

Create a solution with 2 or more projects (more is better)
Run dotnet husky attach for each project
Clean project, then Build All.

You will now get the above mentioned error.
PS: I really like Husky.Net. The above is just a minor inconvenience. After trying many different ways of creating cross-platform auto-installed pre-commit hooks for Git, basically nothing worked out of the box, but Husky did. It is awesome!!!!

It took me a while, but here's a configuration that works with the current dotnet husky install by basically checking if it is installed or not. It is a bit tricky to get right, though, and I wouldn't expect people to add such complex tasks. Would be better if it could be fixed somehow in dotnet husky install instead.
The following code does:

Only runs dotnet tool restore and dotnet husky install on non-Clean targets. That is, it runs on Build, Rebuild, Build All, but not on Clean. This dramatically increases the speed of Clean on large solutions, as restore & dotnet husky install is a relatively slow set of commands (didn't test which of the two was the biggest contributor).
Still runs dotnet tool restore for every Build-like action for each project in the solution. Still thinking of a way around this.
Does not run dotnet husky install anymore if it is already installed. This is now merely a config check (though this required git to be accessible, this may not be ideal, though for a git-hook you'd expect git to be there ;) ).

It turned out to be a bit tricky to ensure the not running when cleaning bit. Maybe there's a better way, but in the end, the below works. I just dumped it in an EnableHusky.proj and use <Import Project="EnableHusky.proj" /> in each project file.
  <!--
    Prevent running Husky-Install when Target=Clean.
    Must run before 'BeforeClean' (just before 'Clean' is not correct and will execute Husky anyway.)
  -->
  <Target Name="NoHuskyCheckOnClean" BeforeTargets="BeforeClean">
    <CreateProperty Value="1">
      <Output TaskParameter="Value" PropertyName="SkipHuskyCheck" />
    </CreateProperty>
  </Target>

  <!--
    This checks whether Husky is already installed, then installs it, if necessary.
  -->
  <Target Name="CheckAndInstallHusky" BeforeTargets="Restore;CollectPackageReferences" Condition="'$(SkipHuskyCheck)' != '1'">
    <Exec Command="git config --local --default "" --get core.hookspath" ConsoleToMSBuild="true" StandardOutputImportance="Low">
      <Output TaskParameter="ConsoleOutput" PropertyName="HuskyHookLocation" />
    </Exec>
    <CreateProperty Value="true" Condition="'$(HuskyHookLocation)'=='.husky'">
      <Output TaskParameter="Value" PropertyName="HuskyAlreadyInstalled" />
    </CreateProperty>

    <!-- restore dotnet tools -->
    <Exec Command="dotnet tool restore" StandardOutputImportance="Low" StandardErrorImportance="High" />
    <Message Condition="'$(HuskyAlreadyInstalled)'=='true'" Text="Husky installation skipped: already installed" Importance="high" />

    <!-- call husky installer conditionally -->
    <CallTarget Targets="InstallHusky" Condition="'$(HuskyAlreadyInstalled)'!='true'" />
  </Target>

  <!-- The actual Husky Install target, dependently called from CheckAndInstallHusky -->
  <Target Name="InstallHusky">
    <Message Text="Installing Husky" Importance="high" />
    <Exec Condition="'$(HuskyHookLocation)'!='.husky'" Command="dotnet husky install" StandardOutputImportance="Low" StandardErrorImportance="High" WorkingDirectory="..\.." />
  </Target>

Lol, meanwhile you've been fixing this on your end! If you want me to test something, let me know (though it's past midnight here, may be tomorrow).

Hi @abelbraaksma,
First of all, thank you for the feedback and your great ideas, I really enjoy these kinds of issues 🙏.
On my end, I solved the problem with a global mutex (as you correctly suggested), and you can try it in v0.5.2.
but you also mentioned another problem which is multiple restore and install that could make builds slow. I usually don't attach husky to all of my projects and a common/shared project usually does the job, also according to my tests the performance overhead of these two commands is really low but if you think there is a better way to handle this or you had any other suggestion for improvement, you're really welcome, we can discuss it in another issue. btw your configuration is really interesting (I may use some of your checking ideas in the next versions) 👏.
Good luck.

Thanks for the quick fix, it is much appreciated!
On the significance of small things, I did a little experiment:
Here's a timing on my machine of dotnet husky install. Commands were given without intervening pause (ignore the first timestamp and call):
d:\temp 2:09:03.99>dotnet husky install
Git hooks installed
d:\temp 2:09:10.41>dotnet husky install
Git hooks installed
d:\temp 2:09:11.15>dotnet husky install
Git hooks installed
d:\temp 2:09:11.90>dotnet husky install
Git hooks installed
d:\temp 2:09:12.64>dotnet husky install
Git hooks installed
d:\temp 2:09:13.39>

On my machine that is 4 commands is 13.39 - 10.41 = 2.98s, or about 0.75s per command. This may be dotnet overhead, I don't know. But take the Clean example. I have 12 projects in a solution (it depends, we have many solutions, some smaller, some larger, up to 30-something projects). Cleaning takes about 2-3s (without Husky). With each project having this command as well, it adds 9s, which is significant.
I also timed dotnet tool restore, which likely depends on the amount of tools. It took 0.5s per command. Altogether, in this example the two together become ~1.25s. Could be worse, but it adds up (and if this is network time, a faster PC won't solve it enough).

I usually don't attach husky to all of my projects and a common/shared project usually does the job

Yes, I thought of that too. But as soon as it is shared, it'll run on each compile. Oh wait, Visual Studio probably won't recompile the dependency, as long as it is a project with output. But that requires something to be compiled, but maybe there's a simpler way with the EnableHusky.proj approach where you import it everywhere, but it runs only once (like VS does for already compiled projects).

To answer my own question, it turns out that Target Batching works. With your mutex (which prevents problems when run in parallel) and the Outputs vs Inputs behavior (where MSbuild diligently tests whether source has been updated), this indeed prevents the execution of the tasks.
There's now probably some code that's redundant and hopefully a smaller version is possible. I'll soon test with your mutexed version. For posterity, this is the current version:
<Project>

  <PropertyGroup>
    <CurrentDate>$([System.DateTime]::Now.ToString(o))</CurrentDate>
  </PropertyGroup>

  <!--
    Prevent running Husky-Install when Target=Clean.
    Must run before 'BeforeClean' (just before 'Clean' is not correct and will execute Husky anyway.)
  -->
  <Target Name="NoHuskyCheckOnClean" BeforeTargets="BeforeClean">
    <CreateProperty Value="1">
      <Output TaskParameter="Value" PropertyName="SkipHuskyCheck" />
    </CreateProperty>
  </Target>

  <!--
    This checks whether Husky is already installed, then installs it, if necessary.
  -->
  <Target Name="CheckAndInstallHusky"
          BeforeTargets="Restore;CollectPackageReferences"
          Condition="'$(SkipHuskyCheck)' != '1'"
          Inputs="$(MSBuildProjectDirectory)\..\..\.config\dotnet-tools.json"
          Outputs="$(MSBuildProjectDirectory)\..\..\.config\husky-installed.lock">

    <Exec Command="git config --local --default "" --get core.hookspath" ConsoleToMSBuild="true" StandardOutputImportance="Low">
      <Output TaskParameter="ConsoleOutput" PropertyName="HuskyHookLocation" />
    </Exec>

    <CreateProperty Value="true" Condition="'$(HuskyHookLocation)'=='.husky'">
      <Output TaskParameter="Value" PropertyName="HuskyAlreadyInstalled" />
    </CreateProperty>

    <!-- restore dotnet tools -->
    <Exec Command="dotnet tool restore" StandardOutputImportance="Low" StandardErrorImportance="High" />
    <Message Condition="'$(HuskyAlreadyInstalled)'=='true'" Text="Husky installation skipped: already installed" Importance="high" />

    <!-- call husky installer conditionally -->
    <CallTarget Targets="InstallHusky" Condition="'$(HuskyAlreadyInstalled)'!='true'" />

    <!-- after successful task exec, ensure on next build it is not run again (MSBuild uses Inputs/Outputs compare for that) -->
    <WriteLinesToFile File="$(MSBuildProjectDirectory)\..\..\.config\husky-installed.lock"
                      WriteOnlyWhenDifferent="true"
                      Overwrite="true"
                      Lines="$(CurrentDate)"/>

  </Target>

  <!-- The actual Husky Install target, dependently called from CheckAndInstallHusky -->
  <Target Name="InstallHusky">
    <Message Text="Installing Husky" Importance="high" />
    <Exec Condition="'$(HuskyHookLocation)'!='.husky'" Command="dotnet husky install" StandardOutputImportance="Low" StandardErrorImportance="High" WorkingDirectory="..\.." />
  </Target>

</Project>

Thanks for sharing your configuration, something like this could be an additional advanced feature to the husky attach command, I'll be happy if you test this and share your final thoughts on another issue that you think is necessary for others facing a similar problem.

Btw, your name reminds me of this brilliant chess player, I assume you're a different Alireza? ♟

Yeah 😉, there are a lot of Alireza in Iran, but firoozja is originally from the city I'm living now. :) we have at least one thing in common 😅, plus I also like chess but my rating is half of his.
Have a nice day


Update JS collector config --> OTLP exporter config

The way you do it isn't really specific to collectors, so this can be generally useful.

Preview: https://deploy-preview-988--opentelemetry.netlify.app/docs/instrumentation/js/exporters/

CC @open-telemetry/javascript-approvers

@austinlparker - I'll let you have a final look and merge. Thx


Add PWA support

Adding PWA (Progressive Web App) support to the özgürsözlük would be a nice enhancement.
This feature would allow users to "install" the app on both desktops and mobile devices, optimizing their experience.

I have not used PWA in my previous projects. Can you guide me?


.NET8 preview 7 seems to be incompatible

.NET8 will launch in a few months so we started migrating our code base libraries.
It seems Cosmos SDK cannot work with .NET8 while we don't have any problem with .NET7
Please take a look at this repo for a repro example.
https://dev.azure.com/milanifrancesco/Public Tests/_git/CosmosSdkNet8Issue
Examples running:
.NET7 OK

.NET8 not working (just hangs...)

After further investigation, I've realised it might just be a problem related to localhost.

Certificate or SSL negotiation is not directly controlled by the SDK, this is the .NET HttpClient. There are known cases (like running the Emulator on a docker image) already documented where you can disable the SSL verification if needed: https://learn.microsoft.com/en-us/azure/cosmos-db/local-emulator?tabs=ssl-netstd21#disable-ssl-validation


[ROCM] Fix build with runtime tracing enabled

lol the cuda one also has this issue - probably copy/pasted - vulkan matches what you've done here and it works fine so this should be good!

yeah I just copied Vulkan :P

Interesting. I see we changed how this is done in Vulkan side sometime ago: https://github.com/openxla/iree/pull/14665/files#diff-b316655a6a62e74728a2fbe6887d9a04a7463c6307bb98bf1ad518e71b585183 So all others are still living a past life. ;)
Though tracing bots are okay with the split (https://github.com/openxla/iree/actions/runs/8241141147/job/22537827719) and local also builds fine for me for both cuda and hip..
Anway, I'm gonna change cuda/hip to follow the change there.


perf-regression: try resolving JAVA_HOME first in itest #4023

@jamesnetherton FYI

My original intention was to use the java.home System property as it'll point to the JDK that the test is running under and is always guaranteed to be present.

Ok, the pr has been updated and now uses java.home system property.


add a Webfinger endpoint, allowing mentioning fedi users by GTN handle

This can make it easier to announce news on the fedi, as we can write things like "Thanks<EMAIL_ADDRESS>and it'll mention @abretaud's account :)
requires https://github.com/galaxyproject/infrastructure-playbook/pull/44

Nice! feeling sooo social :D


Adapt Gossip layer to pt2 messages

Gossip protocol
TX processor
Blake2b-Hashing
Fix peering handshake bitmask by replacing it with a version

Done


Create linter.yml

Attach project to the pull request

can u pls also add status badge of this action


Edge probing: Add TACRED and SemEval relation-classification tasks

New tasks: edges-rel-tacred and edges-rel-semeval. Add to the standard data-prep and experiment scripts.
Also adds edges-ner-tacred for sanity-checking with the entity type tags from TACRED, although these are silver labels.

Hello @iftenney! Thanks for submitting the PR.

In the file probing/data/convert-semeval2010-task8.py, following are the PEP8 issues :

Line 26:1: E402 module level import not at top of file
Line 27:1: E402 module level import not at top of file
Line 28:1: E402 module level import not at top of file
Line 29:1: E402 module level import not at top of file
Line 31:1: E402 module level import not at top of file
Line 33:1: E302 expected 2 blank lines, found 1
Line 56:1: E305 expected 2 blank lines after class or function definition, found 1
Line 60:1: E302 expected 2 blank lines, found 1
Line 71:35: E231 missing whitespace after ','
Line 78:1: E302 expected 2 blank lines, found 1
Line 97:1: E302 expected 2 blank lines, found 1
Line 102:1: E302 expected 2 blank lines, found 1
Line 119:1: W391 blank line at end of file

In the file probing/data/convert-tacred.py, following are the PEP8 issues :

Line 28:1: E402 module level import not at top of file
Line 29:1: E402 module level import not at top of file
Line 30:1: E402 module level import not at top of file
Line 31:1: E402 module level import not at top of file
Line 33:1: E402 module level import not at top of file
Line 35:1: E302 expected 2 blank lines, found 1
Line 53:1: E302 expected 2 blank lines, found 1
Line 63:24: E128 continuation line under-indented for visual indent
Line 67:24: E128 continuation line under-indented for visual indent
Line 72:1: E302 expected 2 blank lines, found 1
Line 80:1: E302 expected 2 blank lines, found 1
Line 114:1: W391 blank line at end of file

In the file probing/data/utils.py, following are the PEP8 issues :

Line 12:1: E302 expected 2 blank lines, found 1
Line 18:1: E302 expected 2 blank lines, found 1
Line 59:80: E501 line too long (82 > 79 characters)
Line 89:80: E501 line too long (93 > 79 characters)
Line 90:80: E501 line too long (95 > 79 characters)
Line 91:80: E501 line too long (95 > 79 characters)
Line 101:1: E302 expected 2 blank lines, found 1

In the file probing/deterministic_split.py, following are the PEP8 issues :

Line 22:1: E302 expected 2 blank lines, found 1
Line 59:1: W391 blank line at end of file

In the file src/tasks/edge_probing.py, following are the PEP8 issues :

Line 30:1: E302 expected 2 blank lines, found 1
Line 193:80: E501 line too long (81 > 79 characters)
Line 196:80: E501 line too long (85 > 79 characters)
Line 203:80: E501 line too long (87 > 79 characters)
Line 245:1: E305 expected 2 blank lines after class or function definition, found 1
Line 246:16: E127 continuation line over-indented for visual indent
Line 247:16: E127 continuation line over-indented for visual indent
Line 254:16: E127 continuation line over-indented for visual indent
Line 255:16: E127 continuation line over-indented for visual indent
Line 262:16: E127 continuation line over-indented for visual indent
Line 269:16: E127 continuation line over-indented for visual indent
Line 270:16: E127 continuation line over-indented for visual indent
Line 277:16: E127 continuation line over-indented for visual indent
Line 284:16: E127 continuation line over-indented for visual indent
Line 285:16: E127 continuation line over-indented for visual indent
Line 292:16: E127 continuation line over-indented for visual indent
Line 299:16: E127 continuation line over-indented for visual indent
Line 306:16: E127 continuation line over-indented for visual indent
Line 317:16: E127 continuation line over-indented for visual indent
Line 324:16: E127 continuation line over-indented for visual indent
Line 338:16: E127 continuation line over-indented for visual indent
Line 345:16: E127 continuation line over-indented for visual indent
Line 352:16: E127 continuation line over-indented for visual indent
Line 359:16: E127 continuation line over-indented for visual indent
Line 366:16: E127 continuation line over-indented for visual indent
Line 373:16: E127 continuation line over-indented for visual indent
Line 380:16: E127 continuation line over-indented for visual indent
Line 381:16: E127 continuation line over-indented for visual indent
Line 388:16: E127 continuation line over-indented for visual indent
Line 395:16: E127 continuation line over-indented for visual indent
Line 400:1: W391 blank line at end of file


:many query returns nil slice on empty result

Version
1.13.0
What happened?
When executing a :many query that returns an empty slice, the returned slice is nil.
e.g.
With this query,
-- name: GetItems :many
SELECT * FROM items;

The following code is generated
func (q *Queries) GetItems(ctx context.Context) ([]*Item, error) {
	rows, err := q.db.Query(ctx, getItems)
	if err != nil {
		return nil, err
	}
	defer rows.Close()
	var items []*Item
	for rows.Next() {
		var i Item
		if err := rows.Scan(
			&i.ID,
		); err != nil {
			return nil, err
		}
		items = append(items, &i)
	}
	if err := rows.Err(); err != nil {
		return nil, err
	}
	return items, nil
}

func main() {
  items, err := db.GetItems(context.Background())
  fmt.Println("items is nil: ", items == nil) // true
  fmt.Println("err is nil: ", err == nil) // true
}

IMO, an empty array should be returned instead of nil.
For the usecase, it can be an issue when you want to serialize items as JSON because it gets serialized as null instead of an empty array ([]).
As a fix, it's possible to change the following line in the generated function:
- 	var items []*Item
+	items := []*Item{}

I can open a PR if that sounds good to you.
Thanks!
Relevant log output
No response
Database schema
No response
SQL queries
No response
Configuration
No response
Playground URL
No response
What operating system are you using?
No response
What database engines are you using?
No response
What type of code are you generating?
No response

You can change this behavior by setting emit_empty_slices to true.
emit_empty_slices:
    If true, slices returned by :many queries will be empty instead of nil. Defaults to false.

Thanks for the fast answer @kyleconroy! Sorry, I missed that but it does exactly what I need.
Thanks for this great library also!


Remix fails to run with<EMAIL_ADDRESS>- TypeError: Cannot read properties of undefined (reading 'v2_errorBoundary')

What version of Remix are you using?
1.15.0
Are all your remix dependencies & dev-dependencies using the same version?

[X] Yes

Steps to Reproduce

Upgrade netlify-cli to latest (14.2.1 at the time of this writing).
Attempt to run Remix with whatever package.json command in your project invokes netlify dev.
Observe CLI error.
Load in browser and observe The function has crashed error.

Expected Behavior
Project is able to run.
Actual Behavior
Stack trace:
TypeError: Cannot read properties of undefined (reading 'v2_errorBoundary')
~/my-project/node_modules/@remix-run/server-runtime/dist/routes.js:42:35
Array.map ()
Object.createStaticHandlerDataRoutes (~/Projects/my-project/node_modules/@remix-run/server-runtime/dist/routes.js:41:45)
Object.createRequestHandler (~/Projects/my-project/node_modules/@remix-run/server-runtime/dist/server.js:28:27)
createRequestHandler (~/Projects/my-project/node_modules/@remix-run/netlify/dist/server.js:31:28)
Object. (~/Projects/my-project/server.js:43:24)
Module._compile (node:internal/modules/cjs/loader:1226:14)
Object.Module._extensions..js (node:internal/modules/cjs/loader:1280:10)
Module.load (node:internal/modules/cjs/loader:1089:32)
Function.Module._load (node:internal/modules/cjs/loader:930:12)

This is most likely due to one of your remix dependencies not being at the same versions of the others.
Can you provide your package.json dependencies & devDependencies ?

npm list results of my working project:
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>
As far as I can tell, we should be good from a Remix package version match standpoint.

Interesting, I can't reproduce this with the npx create-remix@latest command.

Could you try explicitly listing @remix-run/server-runtime in your dependencies? (At the same version ofc)

Could you try explicitly listing @remix-run/server-runtime in your dependencies? (At the same version ofc)

The same error occurs after that change.

I'm happy to try a few things on my end. I suspect it's an artifact of having an old Remix app upgraded many, many times in these early days! Something is still stuck in the past.

Yup, I cleaned up an old netlify directory and updated some configs, and things run now on latest netlify-cli. Thanks, closing this out!

@juliaschiller150 you mind to share what you fixed, im having the same issue on remix 1.7.9 with<EMAIL_ADDRESS>typeError: Cannot read properties of undefined (reading 'v2_errorBoundary')     at /var/task/node_modules/@remix-run/netlify/node_modules/@remix-run/server-runtime/dist/routes.js:46:35     at Array.map (<anonymous>)     at Object.createStaticHandlerDataRoutes (/var/task/node_modules/@remix-run/netlify/node_modules/@remix-run/server-runtime/dist/routes.js:45:45)     at Object.createRequestHandler (/var/task/node_modules/@remix-run/netlify/node_modules/@remix-run/server-runtime/dist/server.js:28:27)     at createRequestHandler (/var/task/node_modules/@remix-run/netlify/dist/server.js:31:28)     at Object.<anonymous> (/var/task/.netlify/functions-internal/server.js:11231:55)     at Module._compile (node:internal/modules/cjs/loader:1356:14)     at Object.Module._extensions..js (node:internal/modules/cjs/loader:1414:10)     at Module.load (node:internal/modules/cjs/loader:1197:32)     at Function.Module._load (node:internal/modules/cjs/loader:1013:12)

I'm afraid I can't remember the specifics beyond the above, @nunoci. I would recommend spinning up a fresh Remix install in a sibling directory and diffing netlify related directories and Remix configs between that new install and your existing app.
Let us know what you find!


[AutoScheduler] Fix distill record

The distill record in auto_scheduler is broken due to the recent change (#7344). This PR fixes the function and make it self-contained.
cc @merrymercy

We also have to update the command in tvm/tutorials/auto_scheduler/tune_network*.py
https://github.com/apache/tvm/blob/12c6b70e334da811d0330622460158b369388ae2/tutorials/auto_scheduler/tune_network_arm.py#L411


[vcpkg baseline][monkeys-audio] Update to 5.59

Describe the pull request

What does your PR fix? Fixes #

Released MAC_SDK files are currently only provided for download for a
short period of time and replaced frequently by newer versions.
Building package monkeys-audio[core]:x64-windows...
-- Downloading https://monkeysaudio.com/files/MAC_SDK_548.zip...
-- Downloading https://monkeysaudio.com/files/MAC_SDK_548.zip... Failed. Status: 22;"HTTP response code said error"
CMake Error at scripts/cmake/vcpkg_download_distfile.cmake:182 (message):

      Failed to download file.
      If you use a proxy, please set the HTTPS_PROXY and HTTP_PROXY environment
      variables to "https://user:***@your-proxy-ip-address:port/".
      Otherwise, please submit an issue at https://github.com/Microsoft/vcpkg/issues

So update the current version in vcpkg to the latest version 5.59.
Related PR #7733
Note: feature has been passed with the following triplets:

x86-windows
x64-windows

/azp run

Ping @strega-nil for merge this PR first.

Thanks Nancy!


"odig doc" failing on MacOS 10.13.2 with Chrome

Running "odig doc sedlex" on MacOS 10.13.2 with my browser set to Chrome does this:
$ odig doc sedlex
1934:1971: execution error: Error on line 55: Error: Invalid index. (-1719)
odig: [ERROR] run ['osascript' '-l' 'JavaScript' '-' 'false' 'false'
          'com.google.chrome'

          'file:///Users/perry/.opam/4.06.0/var/cache/odig/odoc/sedlex/index.html']:
          exited with 1
          browser reload: run ['osascript' '-l' 'JavaScript' '-' 'false'
          'false' 'com.google.chrome'

          'file:///Users/perry/.opam/4.06.0/var/cache/odig/odoc/sedlex/index.html']:
          exited with 1

This seems to be a problem with webbrowser can you please reproduce the problem with the browse cli tool  and report the error there.

I can try to do that. Can you suggest what I should run? I will then go to that package and report the problem...

Never mind, I think I got a reproducing case pretty easily.

Thanks, I could indeed have been more specific. The issue was https://github.com/dbuenzli/webbrowser/issues/4


CARLA crashes when reloading world with low quality settings

CARLA version: 0.9.13
Platform/OS: Windows 10
Problem you have experienced: CARLA crashes when reloading world with low quality settings
Steps to reproduce:

Start windows command-prompt and launch CARLA 0.9.13 (installed to C:\apps\CARLA) using following two steps (had to wait ~30secs between two commands for my computer configuration).

start "" /D C:\apps\CARLA /MIN /B CarlaUE4.exe -windowed -carla-server -carla-no-networking -quality-level=Low
start "" /D C:\apps\CARLA\PythonAPI\util /MIN /B python config.py --map Town01

Start Python and run following

import os, sys
sys.path.append(r'C:\apps\CARLA\PythonAPI\carla\dist\carla-0.9.13-py3.7-win-amd64.egg')
import carla
client = carla.Client('localhost', 2000)
client.reload_world()

Above causes CARLA to crash with following error written to python terminal

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
RuntimeError: time-out of 5000ms while waiting for the simulator, make sure the simulator is ready and connected to localhost:2000

Remove -quality-level=Low in Step 1 and launch CARLA again

Now run commands in Step 2, and CARLA should work fine (warning message in Step 3 still an issue).

I have the same issue on ubuntu 20 and carla 0.9.13


Convert calendar_dates to schedule exceptions on import into editor

 Issue by landonreed
Thursday Apr 26, 2018 at 17:00 GMT
Originally opened as https://github.com/catalogueglobal/datatools-server/issues/80

Currently (and since the earliest versions of gtfs-editor), when importing a feed into the editor the calendar_dates.txt table is entirely disregarded.  Schedule exceptions must be generated and managed from scratch within the feed editor. This is due in part to the complex combinations of calendars.txt and calendar_dates.txt that can be found in GTFS feeds. One notable example, a case which is also described in the reference documentation, is the TriMet feed, which explicitly defines all dates of operation in calendar_dates.txt.
While there is no support currently for moving from calendar_dates.txt to editor-defined schedule exceptions, there may be some simple rules we could introduce to simply convert single or paired dates entries into the SWAP exception type.

 Comment by cbergy
Friday Sep 21, 2018 at 08:49 GMT

Hi @landonreed ,
is the import of calendar_dates.txt planned somehow in the next future, or al least to implement the rules you mentioned?

 Comment by abyrd
Friday Sep 21, 2018 at 09:48 GMT

@cbergy we are working on this now.

 Comment by landonreed
Tuesday Nov 13, 2018 at 17:15 GMT

This has been fixed in the downstream library conveyal/gtfs-lib#141, but we need to first release gtfs-lib and bump the version of gtfs-lib in datatools-server's pom.


feat: add request date in logs

If call fails with an exception, there is no date to get proper traceability

Oups, gonna fix Unit tests


CHEBI:82334, please check

Dear ChEBI curators,
Please would you check CHEBI:82334 needed for Rhea.
Cheers, Anne

Now done.
Adnan


Show ASN information for IPs

It would be great if ASN information could be stored and displayed for example on mouseover over an IPv4/6 address.
Instead of entering these values manually, you could check if the geoip module is available and use https://www.php.net/manual/de/function.geoip-asnum-by-name.php for lookups.

I did some tests and using the geoip module seems to be a bad idea for some reasons. For example, it does not properly support IPv6. I'll look into some alternatives and will eventually open a PR. :)

I did some tests and using the geoip module seems to be a bad idea for some reasons. For example, it does not properly support IPv6. I'll look into some alternatives and will eventually open a PR. :)

I can host the data from here an example:https://api.srv3r.com/asn/?ipv4=<IP_ADDRESS>

I can host the data from here an example:https://api.srv3r.com/asn/?ipv4=<IP_ADDRESS>


⚠ Bofrost.fr has degraded performance

In a997eec, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1491 ms

Resolved: Bofrost.fr performance has improved in 8ea3fd2 after 6 minutes.


Add User Authentication to Code

User Authentication is based off a Bearer strategy.
Following Endpoints were added:

POST /api/v1.1/token authentication endpoint

TBD: Tests

Moved User authentication to cassandra.
Benefits: More stable and faster


Raster Layer fixes

Addresses #1677
Use just 1 texture, bind in both locations, update drawable's vertex vector in place.

I'll see about pulling this into #1678, it's all the same code changing there.
The sampler locations can be stored with the shader reference as well.

This should be subsumed by #1678 now, including sharing the textures between bindings, caching the indexes, and only rebuilding drawables when the bucket or vertices change.

This should be subsumed by #1678 now, including sharing the textures between bindings, caching the indexes, and only rebuilding drawables when the bucket or vertices change.

Closing this PR as it's included into #1678.


Implement 2D instance uniforms

Adds support for 2d instance shader parameters. Cherrypicked the original PR as first commit.
Supersedes https://github.com/godotengine/godot/pull/97058
Fixes https://github.com/godotengine/godot/issues/62943
Also works with use_parent_material:

Can you link that original PR? Is this new PR meant to supersede it, or it's a follow-up and KoBeWi's PR needs to be merged first?

Can you link that original PR? Is this new PR meant to supersede it, or it's a follow-up and KoBeWi's PR needs to be merged first?

It's the follow-up PR to https://github.com/godotengine/godot/pull/97058 but it is in VERY early stages. I am trying to wrap my head around the code. Clay gave me instructions on how it could be done for the compatability renderer. All the rest is already done

I started writing up what to do, then I realized it was less work for me to just show you, so here is a patch that gets 2D instance uniforms working in 2D.
0001-Finish-GLES3-support.patch
The final piece before this is ready is getting it to work with the "use_parent_material" property. CanvasItems often inherit the material from their parent. Currently it mostly works, but the editor doesn't expose the instance property for updating so you can't set the instance uniform in the editor.

I started writing up what to do, then I realized it was less work for me to just show you, so here is a patch that gets 2D instance uniforms working in 2D.
0001-Finish-GLES3-support.patch
The final piece before this is ready is getting it to work with the "use_parent_material" property. CanvasItems often inherit the material from their parent. Currently it mostly works, but the editor doesn't expose the instance property for updating so you can't set the instance uniform in the editor.

Thank you! I applied your patch except for this part as I couldn't figure out where this goes:
material_storage->shaders.canvas_shader.version_set_uniform(CanvasShaderGLES3::SPECULAR_SHININESS_IN, state.canvas_instance_batches[i].specular_shininess, shader_version, variant, specialization);

Updated with all feedback. Once the code changes are approved I will squash them so we have one commit at the end. The current two commits are for easier checking of the changes I made versus the previous authors made.

I'd like to test this, is it possible to get those conflicts resolved?

@huwpascoe Conflicts resolved.
Be aware that currently the editor doesn't show the parent material properties when use_parent_material is enabled. Still working on that part.

Be aware that currently the editor doesn't show the parent material properties when use_parent_material is enabled. Still working on that part.

I didn't even know that was a feature....well I remember enough about my own work to fix that!
@paddy-exe Here is a patch that implements the parent materials.
0001-implement-use_parent_material.patch

Alright, patch applied. Works great. Thank you for the assistance with this @huwpascoe. Squashed into one commit. Adjusted the code to AThousandShip's codestyle feedback.

Thanks!


Could you fix the YouTube playlist by teaching how to execute the project + client?

I would like to run the project, but I don't know how to run the client or how to interconnect it with the project's server. However, I saw that you made a playlist available that is unavailable, would it be possible to update the link?

This project no longer maintained. This means no support and no updates.


Implement reaction to rerun job

Allow rerunning jobs using the rerun button

I can't find any way to do this. But I am not certain that it is 100% needed


Add MaqlAst

resolves #231

I miss some test checking those new flags "production" and "sharedWithSomeone"
The rests LGTM

LGTM


google oauth2 acting weird

Thanks for creating an issue! Please fill out this form so we can be sure to have all the information we need, and to minimize back and forth.

What are we trying to do?
got a bug report (and was able to replicate) when logging in with google:

Could not authenticate you from GoogleOauth2 because "Invalid segment encoding"

What feature or behavior is this required for?
logging in

How could we solve this issue? (Not knowing is okay!)
tbd

Anything else?

https://stackoverflow.com/questions/35439904/could-not-authenticate-you-from-googleoauth2-because-invalid-credentials

lol we're on the bleeding edge here, eh


[Android] Wrong TextInput height when lineHeight is set

Description
When setting the lineHeight style on TextInput, the height of the component is wrong after typing in the first letter. Typing after the first letter causes the height to get back to the correct one, however, deleting the content causes the height to reset as if the lineHeight is not set.
I believe the problem comes from spannable caching, since removing these lines "solves" the problem. It's possible that the order the methods are called in is to blame. It looks like AndroidTextInputShadowNode::measureContent is called before AndroidTextInputShadowNode::layout, but the second method may update the state of the component, which effectively makes those methods work with different versions of attributed strings - the cachedAttributedStringId property is set when measureContent is called, but the cached spannable gets updated afterwards.
https://user-images.githubusercontent.com/21055725/214325504-9605935f-9eb8-41eb-ae36-7d60a7f52133.mov
Version
0.71.1
Output of npx react-native info
System:
    OS: macOS 12.6
    CPU: (8) arm64 Apple M1 Pro
    Memory: 94.56 MB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 16.15.1 - ~/.nvm/versions/node/v16.15.1/bin/node
    Yarn: 1.22.19 - /opt/homebrew/bin/yarn
    npm: 8.11.0 - ~/.nvm/versions/node/v16.15.1/bin/npm
    Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
  Managers:
    CocoaPods: Not Found
  SDKs:
    iOS SDK:
      Platforms: DriverKit 21.4, iOS 16.0, macOS 12.3, tvOS 16.0, watchOS 9.0
    Android SDK:
      API Levels: 24, 26, 28, 29, 30, 31, 32, 33
      Build Tools: 26.0.3, 28.0.3, 29.0.2, 30.0.2, 30.0.3, 31.0.0, 32.0.0, 32.1.0, 33.0.0
      System Images: android-28 | Google ARM64-V8a Play ARM 64 v8a, android-32 | Google APIs ARM 64 v8a
      Android NDK: Not Found
  IDEs:
    Android Studio: 2021.3 AI-213.7172.25.2113.9123335
    Xcode: 14.0.1/14A400 - /usr/bin/xcodebuild
  Languages:
    Java: 11.0.14 - /usr/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: 18.2.0 => 18.2.0
    react-native: 0.71.1 => 0.71.1
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

Steps to reproduce
Run the code below and type in one letter into the text input to see it move up, and type another to see the text input sized correctly.
Snack, code example, screenshot, or link to a repository
import React, {useState} from 'react';
import {View, TextInput} from 'react-native';

const App = () => {
  const [text, setText] = useState('');

  return (
    <View style={{flex: 1, backgroundColor: 'yellow', paddingTop: 100}}>
      <TextInput
        style={{
          padding: 8,
          borderColor: 'black',
          borderWidth: 1,
          backgroundColor: 'white',
          margin: 50,
          lineHeight: 40,
        }}
        placeholder="Type here"
        onChangeText={text => {
          setText(text);
        }}
        value={text}
      />
    </View>
  );
};

export default App;

https://github.com/Expensify/App/issues/14799#issuecomment-1584432995

@fabriziobertoglio1987 Maybe it would be helpful for the reviewers of this PR if you provided some context on what you're trying to communicate rather than just dropping the link?

Thanks @roryabraham. I updated my comment.

I have the same problem, the height of the text input on android is too high like 2px on top and 2px at the bottom, the inspector say that there is no padding/margin on it

It seems to have been fixed by 0.74.0-rc.0
https://github.com/facebook/react-native/assets/21055725/44ec5fc9-ea40-43cc-a003-2677352145c8


Update markdown.jsx for numbers in uris

Rebasing #16 on top of release-4.3 (closes #16).
Should not add http:// if the first part have numbers:
uri1:test
cc @ccbrown

Thanks @ryantm for the pull request!
Per the CONTRIBUTING.md file displayed when you created this pull request, we need to add you to the list of approved contributors for the Mattermost project.
Please help complete the Mattermost contribution license agreement?
This is a standard procedure for many open source projects. Your form should be processed within 24 hours and reviewers for your pull request will be able to proceed.
Please let us know if you have any questions.
We are very happy to have you join our growing community! If you're not yet a member, please consider joining our Contributors community channel to meet other contributors and discuss new opportunities with the core team.

I signed the CLA.

Thanks!


Placeholder for Caddyfile Snippets

I love the new Snippets feature in 10.11, but I would like to suggest the ability to use placeholders in the Snippets feature for Caddyfile.  It would be great to setup a generic block for all/most of my sites with
gzip
tls<EMAIL_ADDRESS>log {hostonly}_access.log
error {hostonly}_error.log

So my access and error logs are split up by subdomain.

I'm pretty sure that placeholders can't be used at that point in the application because they're only defined after the Caddyfile is parsed. What could be possible though is have arguments for the snippet. Syntax for that would need to be defined. As-is, snippets are just syntax sugar for copy-pasting chunks of directives.

It would really be great, as @francislavoie says it to be able to pass arguments to snippets.
For example, in the following example, passing arguments like path, and port number would allow to simplify a lot the caddyfile, having snippets like the following:
(forwardToVmName) {
    proxy <variablePath> vmName:<variablePort> {
        transparent
        insecure_skip_verify
        ...
    }
}

@eauchat it would probably be better to open a new issue as a formal feature request for this

@francislavoie

@eauchat it would probably be better to open a new issue as a formal feature request for this
done: new issue #2408


Probes intended for proxyless gRPC can break other setups

When GRPC_XDS_BOOTSTRAP is set we perform probes to make sure the certs exist.
The certs are expected to be at OUTPUT_CERT_DIR/....
At some point we set a default value for the GRPC_XDS_BOOTSTRAP so that agent would always generate the bootstrap, and applications could just use it if they wanted.
We either need to:

Require enabling this check explicitly
Make the assumed location of certs more intelligent

cc @howardjohn

https://istio.slack.com/archives/GHKNPELMS/p1643312321979929

Basically this issue makes it so readiness fails when OUTPUT_CERTS is set but we don't write the expected files there.

@howardjohn
There are a lot of paths in this part of the code.. do you know off the top of your head a scenario where OUTPUT_CERTS is set, but we don't care that the certs aren't output?
This failure will only occur if OUTPUT_CERTS != ""

pkg/istio-agent/README.md could be useful if you haven't seen it. Do you
know why they are not written? Doesn't that mean we never fetched any
certs? That seems odd.
On Fri, Feb 4, 2022 at 9:08 AM Steven Landow @.***>
wrote:

@howardjohn https://github.com/howardjohn
There are a lot of paths in this part of the code.. do you know off the
top of your head a scenario where OUTPUT_CERTS is set, but we don't care
that the certs aren't output?
This failure will only occur if OUTPUT_CERTS != ""
—
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/37056#issuecomment-1030179345, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXMZXVROZAOSDYEHFOTUZQBZBANCNFSM5M7ASX6Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>


Add the 4

As in https://www.ripublication.com/aama17/aamav12n1_01.pdf says, the 4 could be generated with a probability of about .10

Sorry, @yangshun, what about this PR?


Add a dark mode or theming

Feature Description
A dark-mode like many applications (e.g Discord, IntelliJ and others) offer or the possibility to create and install own themes to manipulate the look of Franz.
Motivation and Context
The proposed dark-mode is a feature many users got accustomed to in other applications and that can benefit users working in dark environments.
Expected Behavior
A slider in the settings to enable dark-mode permanently.
Additionally a time-based activation could also co-exist there.
Current Behavior
Currently no change of the theming of the application is possible
Your Environment

Franz Version used: 5.0.0-beta.14
Operating System and version: Kubuntu 16.04 (Main Computer) and Windows 7 and 10 on various other machines.

Can the Franz dark mode be connected to Mac OS X dark mode? https://developer.apple.com/documentation/appkit/supporting_dark_mode_in_your_interface


fix: introduce a COS workaround to fix regression #1157

What type of PR is this?
/kind bug
Any specific area of the project related to this PR?
/area driver-modern-bpf
Does this PR require a change in the driver versions?
What this PR does / why we need it:
This PR fixes the regression reported here https://github.com/falcosecurity/libs/issues/1157 as suggested by @FedeDP.
I want to highlight that this is just a temp workaround for tag 0.11.3 we need to find for sure a better solution, hoping to receive some inputs from kernel engineers<EMAIL_ADDRESS>Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
NONE

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

driver/OWNERS [Andreagit97]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 3b8a1b89774ae57c069d73d565290d2c0887b58e

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, erthalion, FedeDP
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

driver/OWNERS [Andreagit97,FedeDP]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, erthalion, FedeDP, jasondellaluce
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

driver/OWNERS [Andreagit97,FedeDP,jasondellaluce]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Fix focus management issues in Firefox

Summary
Resolves #706
Deployment Link
https://terra-core-deployed-pr-765.herokuapp.com/static/#/site/time-input
Before fix in Firefox

After fix in Firefox

Thanks for contributing to Terra.
@cerner/terra

With this logged bug, @benbcai  commented:

Anywhere that calls handleValueChange should pass in event as it is being used in handleValueChange.

In debugging we noticed event is not being passed to the handleValueChange function, which in turn is not being returned in the onChange function. Not sure if we want to handle that issue here as well.

@emilyrohrbough I'll take a look at the event stuff as well.

Functional verification completed. Time input focus now functions correctly in Firefox and other supported browsers.


Doesn't seem to work with go test output

I tried using this within a go test function and was not able to get the color in the terminal. It works within a regular main() function.
func Test_Color(t *testing.T) {
	color.Set(color.FgWhite, color.Bold)
	color.Cyan("Prints text in cyan.")
	fmt.Println("This is white in color")
}

Hi,
Unfortunately, I'm archiving this project and will no longer maintaining it. For more information, please read my blog post: Taking an indefinite sabbatical from my projects.
Thanks for the feedback and contribution.

I've faced it today, any chance it can be fixed? I see you still maintain this project @fatih (PRs are being merged)?

Hi folks. Yeah I guess this one got slipped through my archived projects, and yes I'm maintaining this actively. This is really an old issue, so would appreciate to open a new one, with a reproducable case, what you're expecting. Of top of my mind comes that the Testing packages changes the stdout/stderr pipes, so maybe you have to explicitly set that inside the color package. Again would appreciate if you could open a new issue with a reproducible case.


Suggest accessibility: make announcements more concise

We got feedback from users for debug accessibility to make the announcements as concise as possible. Here are some ideas on how to make it more concise for suggest widget:

Do not announce 'suggestion' after each suggestion, instead of that announce when suggest widget opened and closed - that way the user will know that what he is hearing are suggestions inside the widget
instead of saying 'name, suggestion accepted' just say 'name, accepted'

@zersiax opinions very welcome

Haha that user feedback came from me among others :) Yes, in this case
that is even more important. I think just 'list opened'  and 'list
closed'  or something similar should be enough, definitely not longer,
for announcing the intelliSense popping up.
As for what to announce for the suggestions, for that I would need to
know what is on the screen visually. For example, in Visual Studio
when methods are autocompleted using IntelliSense I think it gives the
short synopsis as well, at least for screenreaders. Are we interested
in doing that as well for Code? Or do we just report the current
autocompletion and give some kind of mechanism for the user to report
the help text using a hotkey, if the help text even exists in Code?

@isidorn There is no need to announce the suggest widget opening, that would only add more noise. There is still a need to announce "suggestion" after each suggestion as now the entire line gets read again on cursor up/down. I will write down more details in #3787. I have shortened the message when accepting a suggestion, as per your point number 2.
@zersiax I will describe shortly the current state of the suggest widget in #3787


docs: misc fixes in user input

fixes #159
supersedes #161 (This PR as the same content in a single commit)

CLA's ok

@kwalrath @naomiblack could one of you please merge this PR ? We've had 10+ bug reports for this

@naomiblack is out, but this seems safe enough, so I'll merge it and attempt to republish.

Thanks !

The fix is up! Please let me know if you notice anything that went wrong with the updated site. (I had to delete an extra lesson: #196.)


Report Settings - Selecting questions for public report

As a Superuser/TM, I want to be able to select the questions I want to show on the public report so that I can only disclose the answer to specific questions from my survey.
All questions are listed. Default is checked "Include in Report"
Pagination matches the survey.
Design matches wireframe
Search questions is a separate task:
https://xd.adobe.com/view/30bd16a9-0635-4ee0-907b-ee3aab727fcc-65ee/screen/88f5dfaf-3579-4453-9f49-0efb52a88915/

Verified, only selected questions are showing up on the report.


Removing duplicate js import

@GeorgePlukov, I also noticed the bullet points (Best Practices) somehow get periods added at render time. Any idea how to stop that? Couldn't find anything about it on the web.

@geurts I'm not seeing periods being added at render time, I think we removed the periods from the status-indicator page in a recent PR so It's possible the site you are viewing is out of date

Thanks @GeorgePlukov I just had to rm package-lock & node modules, I didn't realize it wasn't pulling in the latest READMEs. The PR218 site is also showing the periods so it convinced me the issue wasn't local :P


Fix #4320: Button label only loading icon spacing

@ulasturann
See the ticket: https://github.com/primefaces/primereact/issues/4320

Fixed in code so closing ticket.


adding Github repo icon for quick navigation to the code repo

add GSOC ext and hacktoberfest labels...........

For now we don't require for this, we will look into this later, so I am closing this issue.


Docker slow and not responding

Output of docker version:
Docker version 1.12.0, build 8eab29e

Output of docker info:
Containers: 7
 Running: 2
 Paused: 0
 Stopped: 5
Images: 1
Server Version: 1.12.0
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 86
 Dirperm1 Supported: false
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local nfs
 Network: host null bridge overlay
Swarm: active
 NodeID: 34495kge70x4i15lnenpxop4w
 Is Manager: true
 ClusterID: 2t06r0vn5n38xeot3p5x72nia
 Managers: 2
 Nodes: 2
 Orchestration:
  Task History Retention Limit: 5
 Raft:
  Snapshot interval: 10000
  Heartbeat tick: 1
  Election tick: 3
 Dispatcher:
  Heartbeat period: 5 seconds
 CA configuration:
  Expiry duration: 3 months
 Node Address: <IP_ADDRESS>
Runtimes: runc
Default Runtime: runc
Security Options: apparmor
Kernel Version: 3.13.0-92-generic
Operating System: Ubuntu 14.04.3 LTS
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 3.859 GiB
Name: iron-1
ID: MKUL:QCR3:AVT6:BRO3:XILV:OROV:XEXK:LRET:EY5X:D2EX:HICN:WEKL
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Username: user
Registry: https://index.docker.io/v1/
WARNING: No swap limit support
Insecure Registries:
 <IP_ADDRESS>/8

Additional environment details (AWS, VirtualBox, physical, etc.): aws (EC2 Medium), Docker in Swarm Mode.
Issue: Docker is not responding and takes a long time to put this message out:
# docker service ls
Error response from daemon: rpc error: code = 4 desc = context deadline exceeded

It takes also a considerable time to restart it:
service docker restart
[... waiting ..]
docker stop/waiting
docker start/running, process 26324

This is happening for the first time for me.
The only plugin I installed is ContainX/docker-volume-netshare, but it was not running when this bug happened.
The real problem with this is that all of my containers are shut down after restarting Docker (on the first node). Are containers supposed to shut down after a restart ?
docker service ps app
ID                         NAME            IMAGE                    NODE    DESIRED STATE  CURRENT STATE            ERROR
5an2nk1o2l1r2vfx1nsdh3heq  app.1      eon01/app:v1  server-2  Running        Running 13 minutes ago
82fboutukie10eymspduhnq7k   \_ app.1  eon01/app:v1  server-1  Shutdown       Rejected 14 minutes ago  "Error processing tar file(exi…"
8ktfk350k8lly9w4v95ehpwcp   \_ app.1  eon01/app:v1  server-1  Shutdown       Rejected 14 minutes ago  "open /var/lib/docker/containe…"
65zcu4ja474nkzdhgjlwo444p   \_ app.1  eon01/app:v1  server-1  Shutdown       Rejected 15 minutes ago  "open /var/lib/docker/containe…"
dpr3g9c96sifw7498826kopyu   \_ app.1  eon01/app:v1  server-1  Shutdown       Failed 15 minutes ago    "task: non-zero exit (137)"
4ubbcl41iapze1lmd54y3li7f  app.2      eon01/app:v1  server-2  Running        Running 15 minutes ago
cl6kqevl3uvw6qm9ir96b2yjk   \_ app.2  eon01/app:v1  server-1  Shutdown       Failed 15 minutes ago    "starting container failed: Ad…"
0pvxt5dihlglyy5yoz45alvwf  app.3      eon01/app:v1  server-1  Running        Running 13 minutes ago
cpsp219b745eh00e2ahjlhtu1   \_ app.3  eon01/app:v1  server-1  Shutdown       Rejected 14 minutes ago  "Error processing tar file(exi…"
6fswazl2ktzsen6ljc6z2pbyu   \_ app.3  eon01/app:v1  server-1  Shutdown       Rejected 14 minutes ago  "Error processing tar file(exi…"
6whkrdggtz11smmfq08tj3ycz   \_ app.3  eon01/app:v1  server-1  Shutdown       Rejected 15 minutes ago  "Error processing tar file(exi…"
3wg9mq2s6ajljzyrvvzxngzgp   \_ app.3  eon01/app:v1  server-1  Shutdown       Failed 15 minutes ago    "task: non-zero exit (137)"
1kacslfttd037fmunz1y0y7rm  app.4      eon01/app:v1  server-2  Running        Running 15 minutes ago
c8r28f4devj8bkav9xkoazxff   \_ app.4  eon01/app:v1  server-1  Shutdown       Failed 15 minutes ago    "task: non-zero exit (1)"
e04mnf2fuw4b9a2lfps20nduk  app.5      eon01/app:v1  server-1  Running        Running 13 minutes ago
e66dw4ng982t19texewywotr9   \_ app.5  eon01/app:v1  server-1  Shutdown       Rejected 14 minutes ago  "open /var/lib/docker/containe…"
ecefkbp9h8sc7ycrf0o7cvwuh   \_ app.5  eon01/app:v1  server-1  Shutdown       Rejected 14 minutes ago  "Error processing tar file(exi…"
11p172nz7757sx4qo440nxkbl   \_ app.5  eon01/app:v1  server-1  Shutdown       Rejected 15 minutes ago  "Error processing tar file(exi…"
1kh8nmk01mmlu70x379spsuv3   \_ app.5  eon01/app:v1  server-1  Shutdown       Failed 15 minutes ago    "task: non-zero exit (137)"

Just some initial thoughts; This may be related to https://github.com/docker/docker/issues/25017
I do notice you're running a two-node cluster with two managers; you should never run with two managers; 1 manager or 3 managers is better. In fact, when running with two managers, you double the chance of a manager failure (compared to running a single manager); here's why;
The RAFT algorithm requires the managers to reach a quorum when making changes to the Swarm; in a two node manager setup, this effectively means that all managers must be present; if a single manager is lost, you lose control over the cluster. (And with two managers, chances are doubled that one of them fails). Also read this section of the documentation https://docs.docker.com/engine/swarm/admin_guide/#/add-manager-nodes-for-fault-tolerance
/cc @LK4D4 @aaronlehmann do you think this issue is the same / related to https://github.com/docker/docker/issues/25017?

do you think this issue is the same / related to #25017?

It's possible, but hard to know without more context. It could simply be that the other manager is down, has changed its IP address, or some similar problem. As @thaJeztah mentioned, a two manager setup has the worst fault tolerance properties, so it's better to run with a single manager (or three).

Isn't  ContainX/docker-volume-netshare in stopping status the reason? If your containers are using volumes.

@liubin ContainX/docker-volume-netshare is installed but it was not running right when I got the problem.

Let me close this ticket for now, as it looks like it went stale.


Include other compressors like XZ for smaller size and LZO for speed

Although Attic make a good job deduplicating data, it seems it uses a simle deflate method for compression (like the ones of zip and gzip).
However for data that is going to be backup once for the long term, it makes sense to take a different approach. XZ (Parallel lzma as in zbackup) is in my opinion one of the best compression you can get to further reduce the size at the expense of more cpu and extra time to encrypt and only a little bit more work to restore. For low-end computers or quick short term backups, LZO is the way to go, it's much much faster during compression and decompression at the expense of smaller compression rate.

lz4 seems pretty good and fast.


Readme on how to integrate

Can you explain how to get the bot running, such as how to install the API key, restrict the bot to certain users only, etc? Not very experienced with discord moderation/bot management.
I can't use any commands in the section [CHANNEL ONLY+OWNER ONLY] and even the completions aren't showing as you can see:

It isn't giving any completions and the only commands that work are [CHANNEL ONLY]

It isn't giving any completions and the only commands that work are [CHANNEL ONLY]

Hi, there was a connectivity issue with Discord API and it's resolved now. Can you please try again? I will soon add a readme for setup.

Hi, there was a connectivity issue with Discord API and it's resolved now. Can you please try again? I will soon add a readme for setup.

Still not producing an output. It just checks my command with a white tick and doesn't actually produce an output. Also, none of the [CHANNEL+OWNER ONLY] commands work so I can't see anything with !config

Still not producing an output. It just checks my command with a white tick and doesn't actually produce an output. Also, none of the [CHANNEL+OWNER ONLY] commands work so I can't see anything with !config

@ShivanshuPurohit I'm assuming you have:

Created a .env file and populated it with:

Your discord bot token
Mongo database user
Mongo user password
Mongo database name
Mongo host IP
Mongo host Port

Example here.

If so, can you please verify that you can find your own server in "gp3_servers" collection within the database?
Can you please verify that you have setup a valid OpenAI API token by DM'ing the bot with command !setup?
Can you please verify that once you have setup the API token through !setup, the collection is updated?

I'm thinking your requests are receiving a unhandled response status code. Current implementation only checks for 400,429 and 500. You can add a print(status_code) to handle_status() function and check from terminal what you are receiving.

@ShivanshuPurohit I'm assuming you have:

Created a .env file and populated it with:

Your discord bot token
Mongo database user
Mongo user password
Mongo database name
Mongo host IP
Mongo host Port

Example here.

If so, can you please verify that you can find your own server in "gp3_servers" collection within the database?
Can you please verify that you have setup a valid OpenAI API token by DM'ing the bot with command !setup?
Can you please verify that once you have setup the API token through !setup, the collection is updated?

I'm thinking your requests are receiving a unhandled response status code. Current implementation only checks for 400,429 and 500. You can add a print(status_code) to handle_status() function and check from terminal what you are receiving.

for now I have just added the bot. I will try to host my  own to add different features. I did kick the bot and add it back but I still cant do !config (shows no response) but it generating outputs now

for now I have just added the bot. I will try to host my  own to add different features. I did kick the bot and add it back but I still cant do !config (shows no response) but it generating outputs now

The config issue has been resolved. however i will close this issue once we have a proper readme with instructions.

This is the most confusing setup. I have no experience making bots for discord, so I am finding it difficult to make it work.

Are you ever going to update this with instructions, especially for using the Docker container?

@e4c6 Why hasn't there been any update on this?

@Marcus-Arcadius @youthyio I have been very busy lately, however now i have some time on my hands and i will be documenting the project better.


[chip-test] chip_sw_gpio

Test point name
chip_sw_gpio_out
chip_sw_gpio_in
chip_sw_gpio_irq
Host side component
Unknown
OpenTitanTool infrastructure implemented
Unknown
Silicon Validation (SiVal)
Yes
Emulation Targets

[ ] None
[ ] CW310
[ ] Hyperdebug + CW310

Contact person
No response
Checklist
Please fill out this checklist as items are completed. Link to PRs and issues as appropriate.

[x] Check if existing test covers most or all of this testpoint (if so, either extend said test to cover all points, or skip the next 3 checkboxes)
[ ] Device-side (C) component developed
[ ] Bazel build rules developed
[ ] Host-side component developed
[ ] HJSON test plan updated with test name (so it shows up in the dashboard)
[ ] Test added to dvsim nightly regression (and passing at time of checking)
[ ] For SiVal test cases, test is running relevant FPGA or silicon regression

Moving to SV2 based on https://github.com/lowRISC/opentitan/pull/20322

Moving to SV2 based on #20322

ack


Feedback for saving a report

Is your feature request related to a problem? Please describe.
If one is trying to click on the button to save a report, there is no feedback. This results in clicking several times and not being aware, that the report has been saved several times.
Describe the solution you'd like
When saving a report, a message would be good, that it has been saved.

Should be deployed.

Closing. Feedback is provided for two states: success - report added, fail - report not added (error happened during creation).


REPL isn't available on NuGet.org

This new library needs to be added.  It was not published with the other 1.1 libraries.

Expecting it under: https://www.nuget.org/packages/Microsoft.PowerFx.repl


Allow extensions to opt-out of having a "contextualTitle" for a view

Currently extensions are forced to have a "contextual" title on their views, otherwise the name of the "home" container gets automatically tacked on to the view title as a prefix. I'm not sure I've really ever understood the value of this broadly (as opt-in it makes sense if your view title needs it), but it creates a far less than ideal experience for users in many cases.
For example, with GitLens, we have 3 "homes" for views -- Source Controls, GitLens, and GitLens Inspect. Views are grouped within these for optimized usage patterns, but users can drag these views out of those "homes" to better suit their needs. But once views get moved out of their home, they are forced to get prefixed.
So for example, if a user wants to drag the File History view out of the GitLens Inspect side bar and into any other, it will end up with a GitLens:  prefix. It would be great if extensions could maybe set contextualTitle to null or have some other way to opt out of that behavior.
/cc @sbatten @sandy081

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

I intend to move this to the backlog. I've assigned to backlog candidates for now to see how much interest there is in this.

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


About the "Re-list FUTBIN" button in the auction screen

Thank you very much for keeping the software up to date, it has been a great help to me.
In the "Re-list FUTBIN" button in the auction screen, could you add an option to enter a percentage of the futbin price, I think this would be very useful, thanks again.

Bella Idea


Fake loading timeout is too long

3.5 seconds is way too much - something like half a second makes more sense.

Sure would look into it also you can make a pr for this. Thanks for the suggestion.


Something went wrong during upgrade

After successfully upgrading the stage environment, the upgrade did not successfully upgrade the production environments. SnubaOutcomesConsumer exits with an error like this: https://github.com/getsentry/snuba/issues/760
Looking at the thread it seems that the DB migration in Clickhouse did not work and I'd like to execute the commands that are shown in the thread but I don't know how.
Furthermore the UI also generates similar errors:
QueryMissingColumn: [47] DB::Exception: Missing columns: 'quantity' 'category' while processing query: 'SELECT outcome AS _snuba_outcome, category AS _snuba_category, project_id AS _snuba_project_id, sum(quantity) AS _snuba_quantity, _snuba_project_id, _snuba_outcome, _snuba_category, _snuba_quantity FROM outcomes_hourly_local PREWHERE _snuba_project_id IN (1, 2, 3, 4, 5, 7, 8, 9, 35) WHERE ((org_id AS _snuba_org_id) = 1) AND ((timestamp AS _snuba_timestamp) >= toDateTime('2021-04-16T00:00:00', 'Universal')) AND (_snuba_tim...
(3 additional frame(s) were not displayed)
...
  File "sentry/snuba/outcomes.py", line 282, in run_outcomes_query
    limit=10000,
  File "sentry/utils/snuba.py", line 654, in raw_query
    [snuba_params], referrer=referrer, use_cache=use_cache, snql_entity=snql_entity
  File "sentry/utils/snuba.py", line 695, in bulk_raw_query
    params, referrer=referrer, use_cache=use_cache, snql_entity=snql_entity
  File "sentry/utils/snuba.py", line 731, in _apply_cache_and_build_results
    query_results = _bulk_snuba_query(map(itemgetter(1), to_query), headers, snql_entity)
  File "sentry/utils/snuba.py", line 808, in _bulk_snuba_query
    error["message"]

Thanks for a little hint :)

Hi @nodomain
The only thing that comes to mind right now is this ->
Find the task definition that was created for Snuba Migrations (https://github.com/Rungutan/sentry-fargate-cf-stack/blob/main/cloudformation-template.yaml#L5517) and simply create a service/container with it manually, execute it once and check the logs

Found a trace during stack update:
Resource template validation failed for resource TaskDefinitionSnubaMigrations as the template has invalid properties. Please refer to the resource documentation to fix the template. Properties validation failed for resource TaskDefinitionSnubaMigrations with message: #/ContainerDefinitions/0: extraneous key [Entrypoint] is not permitted

Perhaps this is the reason why the task is not executed because the entrypoint is not used?

Looks like the "original" snuba container definition switched and uses a different logic for entrypoint/cmd now.
Updated the template for Entrypoint and Command -> https://github.com/Rungutan/sentry-fargate-cf-stack/pull/50/files
Please do a stack update with the new template and let me know how it goes

Cool, will test!

I got the root cause after creating a manual task because the fix provided did not solve the issue.

Where to move from here? Still trying to understand the moving parts ;)

I'm .... lost ....

Maybe this helps -> https://forum.sentry.io/t/migration-error/11882/2 ...

Thanks! Got a trace
0014_backfill_errors (IN PROGRESS) (blocking)

2021-04-29 12:13:02[X] 0003_sessions_matview
2021-04-29 12:13:02[ ] 0010_transactions_nullable_trace_id
2021-04-29 12:13:02[ ] 0011_transactions_add_span_op_breakdowns
2021-04-29 12:13:02discover
2021-04-29 12:13:02[X] 0001_discover_merge_table
2021-04-29 12:13:02[X] 0002_discover_add_deleted_tags_hash_map
2021-04-29 12:13:02[X] 0003_discover_fix_user_column
2021-04-29 12:13:02[X] 0004_discover_fix_title_and_message
2021-04-29 12:13:02[X] 0005_discover_fix_transaction_name
2021-04-29 12:13:02[ ] 0006_discover_add_trace_id
2021-04-29 12:13:02outcomes
2021-04-29 12:13:02[X] 0001_outcomes
2021-04-29 12:13:02[X] 0002_outcomes_remove_size_and_bytes
2021-04-29 12:13:02[ ] 0003_outcomes_add_category_and_quantity
2021-04-29 12:13:02[ ] 0004_outcomes_matview_additions (blocking)
2021-04-29 12:13:02sessions
2021-04-29 12:13:02[X] 0001_sessions
2021-04-29 12:13:02[X] 0002_sessions_aggregates
2021-04-29 12:13:02[X] 0006_errors_tags_hash_map
2021-04-29 12:13:02[X] 0007_groupedmessages
2021-04-29 12:13:02[X] 0008_groupassignees
2021-04-29 12:13:02[X] 0009_errors_add_http_fields
2021-04-29 12:13:02[X] 0010_groupedmessages_onpremise_compatibility
2021-04-29 12:13:02[X] 0011_rebuild_errors
2021-04-29 12:13:02[X] 0012_errors_make_level_nullable
2021-04-29 12:13:02[X] 0013_errors_add_hierarchical_hashes
2021-04-29 12:13:02[-] 0014_backfill_errors (IN PROGRESS) (blocking)
2021-04-29 12:13:02[ ] 0015_truncate_events
2021-04-29 12:13:02transactions
2021-04-29 12:13:02[X] 0001_transactions
2021-04-29 12:13:02[X] 0002_transactions_onpremise_fix_orderby_and_partitionby
2021-04-29 12:13:02[X] 0003_transactions_onpremise_fix_columns
2021-04-29 12:13:02[X] 0004_transactions_add_tags_hash_map
2021-04-29 12:13:02[X] 0005_transactions_add_measurements
2021-04-29 12:13:02[X] 0006_transactions_add_http_fields
2021-04-29 12:13:02[X] 0007_transactions_add_discover_cols
2021-04-29 12:13:02[X] 0008_transactions_add_timestamp_index
2021-04-29 12:13:02[X] 0009_transactions_fix_title_and_message
2021-04-29 12:13:02system
2021-04-29 12:13:02[X] 0001_migrations
2021-04-29 12:13:02events
2021-04-29 12:13:02[X] 0001_events_initial
2021-04-29 12:13:02[X] 0002_events_onpremise_compatibility
2021-04-29 12:13:02[X] 0003_errors
2021-04-29 12:13:02[X] 0004_errors_onpremise_compatibility
2021-04-29 12:13:02[X] 0005_events_tags_hash_map

I think part of the problem was that we skipped in-between versions: https://github.com/getsentry/onpremise#updating-sentry
Waiting for input from the forum, asked there for help.

0014_backfill_errors is part of the events group - this did the "reverse" trick:

After reversing the stuck transaction and running the container with "snuba", "migrations", "run" everything seems to settle now.
I'll close the issue after better documenting it.

See my PR - I was getting annoyed by the "launch a container manually and wait for the result, fail, try again" thing :D

Note: reverse, optimize, migrate did the trick


Allow running without network access

I came to deno_vm as an alternative for the now unmaintained node_vm2. Something that is really unexpected for me, is that additional dependencies seem to be downloaded at run-time. Even with cryptographic hashes (so at least tampering with those files would result in an error), this is something I would not really be comfortable with in a production system.
Apart from that, there are cases where network access is not available, and this package would seem to break completely.
Hence the question: could deno be run with completely no network access?
Could the necessary dependencies be downloaded in the Python package, e.g. with a custom DENO_DIR containing these files?
This can be tested as follows.
# Dockerfile
FROM denoland/deno:debian-1.40.4 as deno

FROM python:3.11-slim as python
COPY --from=deno /usr/bin/deno /usr/bin/

RUN pip3 install deno-vm

CMD ["python3", "-c", "from deno_vm import eval; print(eval('hello from deno'))"]

docker build -t dt .
docker run --rm --network=none dt

shows
Download<EMAIL_ADDRESS>Download<EMAIL_ADDRESS>error: Import<EMAIL_ADDRESS>failed: error sending request for url (https://deno.land/std@0.203.0/streams/mod.ts): error trying to connect: dns error: failed to lookup address information: Temporary failure in name resolution
    at file:///usr/local/lib/python3.11/site-packages/deno_vm/vm-server/index.js:1:32

There seems to be a --cached-only deno flag that could help.

deno hosts std library via https.
I think we can bundle the application into a single file to solve this issue. Have to investigate whether it works with web workers.

Bundling is easy, e.g.: deno bundle deno_vm/vm-server/index.js deno_vm/vm-server/bundle.js
Ideally, this would happen when the package is built to be submitted to PyPi. I suppose something like this (and here is an example of an extension generating data files).
Note that this issue is mainly about the core deno_vm Javascript requiring network access. If a user of the package executes a Javascript file that imports from deno.land, I would disallow that by default (breaks the sandbox) - or is that a targeted use-case?
Regarding workers, they would either reference a local file (does that work?), or if they are remote files, would already break (unless the worker lives on deno.land, is that a common case?).

First step in https://github.com/eight04/deno_vm/pull/14.

I'm not familiar with workers in this context. Would you be able to give an example of how to test a worker (or give a pointer)?

I can confirm that https://github.com/eight04/deno_vm/pull/15#issuecomment-1968916966 makes this work.
FROM denoland/deno:debian-1.40.4 as deno

FROM python:3.11-slim as python
COPY --from=deno /usr/bin/deno /usr/bin/
COPY deno_vm-0.5.1-py3-none-any.whl /

RUN pip3 install /deno_vm-0.5.1-py3-none-any.whl

CMD ["python3", "-c", "from deno_vm import eval; print(eval('1+1'))"]

docker build -t dt .
docker run --rm --network=none dt

displays 2


Axelar nodejs version mismatch

I think v16.0.0 is what's required.
cd axelar-cgp-solidity
+ npm ci
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '<EMAIL_ADDRESS>npm WARN EBADENGINE   required: { node: '>=16 <17' },
npm WARN EBADENGINE   current: { node: 'v18.14.1', npm: '9.1.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package<EMAIL_ADDRESS>npm WARN EBADENGINE   required: { node: '^12.0.0 || ^14.0.0 || ^16.0.0' },
npm WARN EBADENGINE   current: { node: 'v18.14.1', npm: '9.1.2' }
npm WARN EBADENGINE }

<EMAIL_ADDRESS>flatten
> sh scripts/flatten-contracts.sh

Flattening contracts...
You are using a version of Node.js that is not supported by Hardhat, and it may work incorrectly, or not work at all.

Please, make sure you are using a supported version of Node.js.

It still builds but the warnings seems risky.

Rather than the current apk add --update nodejs npm jq py3-pip for axelar pre-build, would be nice to detect the required node version and install that specifically.


deploy: revert template changes of 3.7.0 to canary

Helm deployments and other deploy scripts are updated to have
canary tag in the release version
Signed-off-by: Humble Chirammal<EMAIL_ADDRESS>

Nfs provisioner image is not changed https://github.com/ceph/ceph-csi/pull/3320/files

Done.. ptal. thanks @Rakshith-R


Fix Auto Layout Intercepter on Xcode 10

This PR fixes an issue with autolayout failure interceptions on Xcode 10.

Codecov Report

Merging #50 into master will decrease coverage by 0.14%.
The diff coverage is 73.68%.

@@            Coverage Diff             @@
##           master      #50      +/-   ##
==========================================
- Coverage   91.57%   91.43%   -0.15%
==========================================
  Files          43       43
  Lines        2493     2509      +16
==========================================
+ Hits         2283     2294      +11
- Misses        210      215       +5

Impacted Files
Coverage Δ

...tBase/Autolayout/LYTAutolayoutFailureIntercepter.m
90% <73.68%> (-10%)
: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 486b620...41b1c48. Read the comment docs.

I'd prefer just go ahead with only latest & best Xcode 10 (Remove the PreXcode10 support), if a user is still with Xcode 9.x, they can piggyback on an older version.
@plivesey ^ if you have objection.

Apologies for the many builds. Haven't used travis before :(

I'll look into it. Maybe the sims need to be booted?

It seems the CI build failed again, could you take a look? @danl3v

We don't have control to reboot Travis's simulators, however I think Travis would clean up a box before kicking off a new task tho.

Not 100% sure, maybe we're not supposed to launch 3 simulators at the same time with Travis. We can try 2 simulators and see if it passes...

@oliverhu made some headway. Looks like the iPhone SE is the magic travis ci sim. Gonna do some more testing and clean up my commits

@oliverhu looks like trying to set iOS 11 as a destination is causing some issues. I can experiment more if you would like or also downgrade from 10.1 to 10.

LGTM.


Linting and Formatting for the backend

Fixes
Issue #62
Proposed Changes

Adds linting to the backend
Adds linting CI using github actions

Tests
Please describe the tests that you ran to verify your changes.

[x] Compiled typescript via yarn run build to make sure no type errors are caused
[x] Ran eslint style checks

Note: This PR is missing husky integration

If possible, could you also add in the Husky integration with this? Thanks!

Husky with github desktop seems to be a known issue with some working hacks
Try:
https://github.com/typicode/husky/issues/1163
https://stackoverflow.com/questions/66520423/github-desktop-husky-pre-commit-hook-does-not

What errors are you encountering with Husky on Windows?

Have a look at https://discord.com/channels/732778344466087967/1025580306926948494/1029134370671427584

For next time please try to resolve such issues
You will definitely come across projects where you might not be able to setup your dev environment as smoothly. But it is definitely worth setting up your dev env correctly otherwise your PRs might be blocked until their standards are met.
But congrats on your first PR!


Readme Slack and Google Group Updates Needed

The links for Google Groups and Slack are probably great for those who already have access, but for people like me who have not been invited yet they aren't very useful. Is there someone I can email about getting an invite to one of these groups?

You can post on this thread: https://groups.google.com/forum/#!topic/earlgrey-discuss/RpmBE74oFNk[151-175]. If you rather not post on a public thread, you can send a pm to either myself or @tirodkar
Also the google group is open to public.

I'm not able to view the Google Group from either the link in the readme or from the link you just sent.


PTZ recall works but PTZ-Controll doesn‘t on CR-500N

Hi,
I have a Canon CR-500N.
I can connect to it‘s instance with companion and I can store and recall presets, however most other functions like pan or tilt, zoom and p/t-speed don’t seem to work.
I connect to the camera via vista protocol, wich works with other softwares (e.g. vMix), so the protocol can not be the issue.
Any ideas on how to solve this?
Thanks a lot!

There's a canon-ptz module now, so I will close this out since you can just use that module.


Fixed search bar transition

- Redesigned search bar with default UISearchController to meet HIG requirements and simplify code
- Fixed missing cancel button on iPad
- Removed account property (UUID type) from token searching filter

Fixes #229
Hidden:

Unhidden:

Active:

Hi @justin-stephenson !
Are there any suggestions for this pull request?  I want to try to implement a UICollectionView List (issue #268) and would like to do so given this pull request.

Hello @igor2890 - This PR is working well, but  would like to avoid moving around the top bar icons (scan, manual add token). Thanks for cleaning up the code here.
Please use a separate PR for the issue #268.

Changes LGTM, thanks!


#614 Fix Views not visible when added programmatically

Could you explain why this is needed? I'm don't quite understand.

When you add views programmatically (create view, create yoganode and call YogaLayout's addView), views are not visible because in yogalayout, the node belongs to the child view will not be added.
When infiating fromlayout, everything is okay, but when you want to use yogalayout and node programmaticaly, node will not added as a childNode to its parent and this will cause views not visible

Thanks! Sorry for the delay

@birfincankafein This is actually failing some of the android test suite. Could you have a look and fix?

Still failing? :D

It looks like this PR has has unactioned feedback about causing test failures. Going to take the liberty of closing it out, but please reopen if you disagree.


Failure when parsing invalid HTML

I tried to parse the github page of my project (https://github.com/yannham/mechaml/) using Lambdasoup, but I got an underlying unexpected error from Markup.ml. When I type in a REPL (utop)
Soup.read_file "github.html" |> Soup.parse
where github.html is a dump of the previously given github page, I get

Exception: Failure "require_current_element: None"

While I expected Lambdasoup and Markup.ml to fail quietly
on invalid HTML5, or at least not to fail with an uncaught exception.
Here is a snapshot code of the incriminated version of the page

Thanks. This is an internal error in Markup.ml that needs to be fixed.
This is due to wrong handling of an unmatched </form> tag in the (ill-formed) HTML input.
I want to note that Markup.ml should not exactly fail quietly, more like report the bad tag to ~report and then recover in a certain way – there is a specific behavior required by HTML5 (see 'An end tag whose tag name is "form"'), so I hesitate to call the correct behavior a failure.

This should be fixed now (in Markup.ml master).  While thinking about how to resolve that, I eventually got swamped by other work. See the commit message for some detail on what I chose – but it's ultimately it's just some comments on esoteric HTML error recovery behavior.


Updated Angular sample version number & readme

Updated Angular sample version number & readme

Hi @waldekmastykarz, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;


replace echo -n with printf for POSIX compatibility

/bin/sh on OS X notably lacks support for echo -n, and echo -n is
explicitly defined as not-portable by the POSIX standard. On shells
whose echo lacks the -n flag, make output is garbled:
[libs/libsel4utils] building...
 [HEADERS]
 -n  [STAGE]
 -n sel4utils

Replace all instances of echo -n with printf, which is
POSIX-compatible.

I don't think any of the kernel team develop on OSX and the build system outside of the kernel's own Makefile was not designed to work on an OSX host. Having said that, I think these changes are a good idea. We've never previously supported OSX because there was no demand for it, but if you want to pull everything in line with POSIX, great! :) Just a warning though, that what you are seeing here is probably just the tip of the iceberg of assumptions that you're building on a Linux host.

Awesome! Great to hear. I figured OS X support wasn't high-priority, but surprisingly enough everything works once you get a cross-compiling GCC installed.
There are also a number of places that the build script relies on GNU-specific coreutils options (rmdir  --ignore-fail-on-non-empty and cp -u, for example). I left those alone since it's easy enough to grab a copy of GNU coreutils on OS X (brew install coreutils), but I'd be happy to take a stab at POSIXifying the rest of the command invocations if you think its worthwhile.
On a related note, are pull requests the best way to contribute to these non-kernel repositories?

Couple of questions about this PR:

Is it safe to pass a variable as the first argument to printf? I would never do this in C because you usually don't know whether the variable contains things that might be interpreted as formatting tokens, but I don't know if the equivalent is acceptable practice in shell.
Should all calls to echo be replaced with printf? Purely for consistency, if nothing else.

I'm by no means an expert, but here are my two cents on those issues:

Uncontrolled printf format strings in C are dangerous because you can smash the stack; with printf(1) the worst that happens is that printf consumes a inadvertent format string and fills it in with a default value (0 or the empty string). Unlikely but possible; I suppose to be entirely correct printf %s "uncontrolled: $variable" should be used.
I think that's entirely up to you! POSIX notes that echo is portable when used without options and without escape sequences. So it's a question of whether you find the consistency of printf everywhere worth having to include the newline explicitly.

Happy to tackle either of these issues whichever way you decide!

OK, I'm fine with this PR as it stands. Have you signed a contributor license agreement? If not, we'll need you to complete one of those.
I've posted an internal PR to remove capdl.mk from this repo. It probably doesn't make sense to merge this before that PR is merged. @AdrianDanis, can I leave you to shepherd this one?

CLA signed!


KeyError when transfering checkpoints

Hi, I got this error when running [python3 tools/transform.py --hf_path ${PATH_TO_PYTORCH_MODLE_BIN} --save_path "./checkpoints/t5-base" --half] in terminal. I download t5_base_model.bin.
KeyError:'encoder.block.12.layer.0.SelfAttention.q.weight'.
Could you give me some advice?

t5 base model has only 12 layers. Maybe you should change the layer number at this line to 12.


Revisit number of metrics exported to Prometheus

Describe the bug
If a specific topic has a consumer group, the metrics with the following template are pushed into Prometheus:
kafka_server_fetcherlagmetrics_total_consumerlag_clientid_replicafetcherthread_0_<number>_topic_<topic_name>_partition_<partition number>_value. This causing num of topics * number of partitions metrics to be exported into Prometheus
If there are large number of topics with high partition counts, the amount of metrics is very large. This potentially degrades Prometheus server performance.
Steps to reproduce the issue:

Create several topics with high number of partitions.
Upload some data to them.
Create consumer groups.
Check Prometheus UI for the list of metrics: you will find many of them.

Expected behavior
See a lot less metrics.
Screenshots

Additional context
These metrics are generated by the misconfigured JMX exporter config.
The original metrics from Kafka JMXBean for reference:
kafka.server:clientId=ReplicaFetcherThread-0-1,name=ConsumerLag,partition=0,topic=__CruiseControlMetrics,type=FetcherLagMetrics
kafka.server:clientId=ReplicaFetcherThread-0-1,name=ConsumerLag,partition=0,topic=__KafkaCruiseControlPartitionMetricSamples,type=FetcherLagMetrics
kafka.server:clientId=ReplicaFetcherThread-0-1,name=ConsumerLag,partition=0,topic=_kafka-connect-kafka-config,type=FetcherLagMetrics
kafka.server:clientId=ReplicaFetcherThread-0-1,name=ConsumerLag,partition=1,topic=__KafkaCruiseControlModelTrainingSamples,type=FetcherLagMetrics
...

The JMX config can be finetuned a bit to push the topic name as labels instead of putting it into the name of the metric. Prometheus is better handling those.

+1 - Kafka recently also added support for filtering out metrics server side https://cwiki.apache.org/confluence/plugins/servlet/mobile?contentId=133631990#content/view/133631990
Should we use this to filter these metrics?

+1 - Kafka recently also added support for filtering out metrics server side https://cwiki.apache.org/confluence/plugins/servlet/mobile?contentId=133631990#content/view/133631990
Should we use this to filter these metrics?

Thanks for the link @amuraru. I think we can leverage this feature. Also, we should finetune the jmx exporter config as well.
Using both methods should be effective.

Thanks for the link @amuraru. I think we can leverage this feature. Also, we should finetune the jmx exporter config as well.
Using both methods should be effective.

hi @adamantal - checked this in our environment and couldn't reproduce.
I am seeing instead:
# HELP kafka_server_fetcherlagmetrics_consumerlag Attribute exposed for management (kafka.server<type=FetcherLagMetrics, name=ConsumerLag, clientId=ReplicaFetcherThread-1-304, topic=cjm_ups_xport_perf_32, partition=14><>Value)
# TYPE kafka_server_fetcherlagmetrics_consumerlag gauge
kafka_server_fetcherlagmetrics_consumerlag{clientId="ReplicaFetcherThread-1-304",partition="14",topic="cjm_ups_xport_perf_32",} 0.0
kafka_server_fetcherlagmetrics_consumerlag{clientId="ReplicaFetcherThread-1-203",partition="8",topic="dx_mob_push_messages",} 0.0
kafka_server_fetcherlagmetrics_consumerlag{clientId="ReplicaFetcherThread-3-205",partition="2",topic="dx_mob_push_messages",} 0.0
kafka_server_fetcherlagmetrics_consumerlag{clientId="ReplicaFetcherThread-3-302",partition="5",topic="dx_cjm_mr_mpu_in_1",} 0.0
kafka_server_fetcherlagmetrics_consumerlag{clientId="ReplicaFetcherThread-1-202",partition="105",topic="cjm_imp_email_perf_128",} 0.0

Could it be that recent changes fixed that?

@amuraru Sorry for the late reply.
Thanks for checking this. Do you use the upstream jmx-exporter configs or a custom one? If you use the upstream one, then I'm fine to close this.

I am using default jmx config from the operator and not overriding

Closing this since as stated above the recent change fixed the issue.


Multiple Instances of WebRTC card in same view inherit setting from one another

Multiple Instances of WebRTC card for version 3.0.2 configured in the same view inherit setting from one another. An example is if I disable the viewing of the WebRTC mode via the style command "style: .mode {display: none}" on one webRTC card it disables them for both cards.  This seems to occur for anything that is related to "style:"
Home Assistant 2023.2.0
Supervisor 2023.01.1
Operating System 9.5
Frontend 20230201.0 - latest

Fixed https://github.com/AlexxIT/WebRTC/releases/tag/v3.1.0

Same problem with the latest version of v3.1.0

It's just browser cache. I think I forgot to update version in the code.


Error "Only one system with concentrations allowed per package" doesn't indicate which package it is

In GitLab by @betsyromero on Jan 24, 2020, 10:22
When running build-model.py and getting the error "ValueError: Only one system with concentrations allowed per package" it's not indicating to which package it's referring to.

In GitLab by @Huite on Feb 20, 2020, 12:55
mentioned in commit 0f276d045283903c44ccae86420b0e19d54a7058

In GitLab by @Huite on Feb 12, 2020, 08:52
closed via commit 0f276d045283903c44ccae86420b0e19d54a7058


Leaked connection warning could be more actionable

We shouldn't print the same warning multiple times.
It should include a stacktrace.

Also maybe Response.body().closeQuietly() to make that less of a hassle.

We talked about removing IOException from close() since it's not useful

#2129

Plus, we’re seeing this when I run Crawler with the new HttpURLConnection frontend. So I can use it myself!

I was tracking one of these down recently, would you be ok with capturing a stack trace at the time of execute/enqueue?

Yeah, I think that's exactly what we should be doing.


Missing runtime bindings: Timers

As per https://developers.cloudflare.com/workers/reference/apis/standard/, the timer API (setInterval, clearInterval, setTimeout, and clearTimeout) should be available in the request context.

Pretty sure these are available: https://github.com/dollarshaveclub/cloudworker/blob/master/lib/runtime.js#L11-L14