Not implemented: sysctl CTL_KERN:14

TYPE (KERN_PROC): https://github.com/freebsd/freebsd-src/blob/315ee00fa9616b0a192b6834911f98bcf5316a6b/sys/sys/sysctl.h#L975C1-L975C52
Kern_Proc types: https://github.com/freebsd/freebsd-src/blob/315ee00fa9616b0a192b6834911f98bcf5316a6b/sys/sys/sysctl.h#L1001-L1038
Is required by all games. (8/8)

This one is a PS4 specific.

Yeah, but just showing simple grounding.

The data I'm looking for is a struct starting at offset 0x380 on the proc structure, just in case if someone can help with this. Here is what I have so far:

This one is going to take time because I need to find where the return value is coming from.

Hopefully the stuff from the emails help x3

Also, just a quick unrelated thing @ultimaweapon So, https://www.psdevwiki.com/ps4/Package_Files this has example PKGs such as Youtube. Thing is, if I download it and try to extract it, Obliteration gives "Cannot decrypt EKPFS -> Decryption error". I assume it has to be a f(ake)PKG?

Correct. We cannot decrypt the official PKG. It need to be a PKG that was dumped from a jailbroken console with de-factory standard key.

Should totally send me a Ghidra Zip with all that custom goodness you put into reverse engineering the kernel x3

I meant more of a right click, export, and save as Ghidra Zip File

The reason is that it keeps all the metadata and custom types.

Oh, and the GPR file is empty.

I searched and yeah, Ghidra forces you to use Export for this. @ultimaweapon

We need an exact offset and length of each field.

Any terms for me to look for?

You need to find the functions that read/write that struct and figure out what the data it is written to.

Oh, for your UNK value:
const char *__fastcall sub_140037000(unsigned int a1)
{
  const char *result; // rax
  if ( a1 > 0xFE04 )
  {
    if ( a1 > 0xFF00 )
    {
      switch ( a1 )
      {
        case 0xFFA0u:
          return "ET_SCE_PSPRELEXEC";
        case 0xFFA4u:
          return "ET_SCE_PPURELEXEC";
        case 0xFFFFu:
          return "ET_HIPROC";
      }
    }
    else
    {
      switch ( a1 )
      {
        case 0xFF00u:
          return "ET_LOPROC";
        case 0xFE0Cu:
          return "ET_SCE_STUBLIB (Stub library)";
        case 0xFE10u:
          return "ET_SCE_DYNEXEC (Main module - ASLR)";
        case 0xFE18u:
          return "ET_SCE_DYNAMIC (PRX)";
      }
    }
  }
  else
  {
    if ( a1 == 65028 )
      return "ET_SCE_RELEXEC (PRX)";
    if ( a1 > 3 )
    {
      switch ( a1 )
      {
        case 4u:
          return "CORE (Core file)";
        case 0xFE00u:
          return "ET_SCE_EXEC (Main module)";
        case 0xFE01u:
          return "ET_SCE_REPLAY_EXEC";
      }
    }
    else
    {
      switch ( a1 )
      {
        case 3u:
          return "DYN (Shared object file)";
        case 0u:
          return "ET_NONE";
        case 1u:
          return "REL (Relocatable file)";
        case 2u:
          return "EXEC (Executable file)";
      }
    }
  }
  if ( a1 - 65280 > 0xFF )
    result = "Unknown type";
  else
    result = "Unknown user defined";
  return result;
}
    ```

And just after that function, there's this one:
const char *__fastcall sub_140037100(int a1)
{
  const char *result; // rax
  switch ( a1 )
  {
    case 0:
      result = "EM_NONE";
      break;
    case 1:
      result = "WE32100";
      break;
    case 2:
      result = "Sparc";
      break;
    case 3:
      result = "Intel 80386";
      break;
    case 4:
      result = "MC68000";
      break;
    case 5:
      result = "MC88000";
      break;
    case 6:
      result = "Intel 80486";
      break;
    case 7:
      result = "Intel 80860";
      break;
    case 8:
      result = "MIPS";
      break;
    case 9:
      result = "IBM System/370";
      break;
    case 20:
      result = "PowerPC";
      break;
    case 21:
      result = "PowerPC64";
      break;
    case 23:
      result = "PS3 SPU";
      break;
    case 40:
      result = "ARM";
      break;
    case 62:
      result = "x86-64";
      break;
    default:
      result = "Unknown machine";
      break;
  }
  return result;
}

Also seems like titleid uses wchar_t
wchar_t aTitleid[8] = L"TitleID";

So uh @ultimaweapon We were way off... https://www.psdevwiki.com/ps4/SELF_File_Format#ELF_Segment_Structure

Better to create a PR if you find something useful to add.

... So, Ultima.
typedef Elf64_Ehdr ElfHeader;
struct Elf64_Ehdr
{
  unsigned __int8 e_ident[16];
  Elf64_Half e_type;
  Elf64_Half e_machine;
  Elf64_Word e_version;
  Elf64_Addr e_entry;
  Elf64_Off e_phoff;
  Elf64_Off e_shoff;
  Elf64_Word e_flags;
  Elf64_Half e_ehsize;
  Elf64_Half e_phentsize;
  Elf64_Half e_phnum;
  Elf64_Half e_shentsize;
  Elf64_Half e_shnum;
  Elf64_Half e_shstrndx;
};

typedef Elf64_Sym ElfSymbol;
typedef uint32_t Elf64_Word;
typedef uint16_t Elf64_Half;
typedef uint64_t Elf64_Addr;
typedef uint64_t Elf64_Xword;
struct Elf64_Sym
{
Elf64_Word st_name;
unsigned __int8 st_info;
unsigned __int8 st_other;
Elf64_Half st_shndx;
Elf64_Addr st_value;
Elf64_Xword st_size;
};

I'll fill it out in Ghidra, then send you the Ghidra zip, alright?

I already have those things.

You say that when st_info and st_other aren't using the right data types in your version :P

uchar is just an alias to unsigned __int8 so it is the same thing.

Yes, but... You also are missing values from Structs such as ptr for Elf64_dyn

That one is a union field with d_val, which have the same value. It have no benefit to make it as a union like in C so I just use simple field.

Sent -w-

It goes off the source code of the PS4 SDK for Unity, FW 5.50.

What do you mean?

Ah, the updated Structs and TypeDefs

If you didn't see... Email

What changes you have added? If it just a small fixes like we have discussed above it is not worth for me to discards my works to use your fixes.


Set HttpSM::tunnel_handler_post to handle write event for outputing HTTP 408 response.

clang format successful! https://ci.trafficserver.apache.org/job/clang-format-github/64/

RAT check successful! https://ci.trafficserver.apache.org/job/RAT-github/77/

Linux build failed! https://ci.trafficserver.apache.org/job/linux-github/1653/

Intel CC build failed! https://ci.trafficserver.apache.org/job/icc-github/190/

AU check failed! https://ci.trafficserver.apache.org/job/autest-github/61/

FreeBSD11 build successful! https://ci.trafficserver.apache.org/job/freebsd-github/1759/

clang-analyzer build successful! https://ci.trafficserver.apache.org/job/clang-analyzer-github/322/

clang format successful! https://ci.trafficserver.apache.org/job/clang-format-github/65/

RAT check successful! https://ci.trafficserver.apache.org/job/RAT-github/78/

AU check successful! https://ci.trafficserver.apache.org/job/autest-github/62/

Linux build failed! https://ci.trafficserver.apache.org/job/linux-github/1654/

Intel CC build failed! https://ci.trafficserver.apache.org/job/icc-github/191/

FreeBSD11 build successful! https://ci.trafficserver.apache.org/job/freebsd-github/1760/

clang-analyzer build successful! https://ci.trafficserver.apache.org/job/clang-analyzer-github/323/

RAT check successful! https://ci.trafficserver.apache.org/job/RAT-github/79/

clang format successful! https://ci.trafficserver.apache.org/job/clang-format-github/66/

AU check successful! https://ci.trafficserver.apache.org/job/autest-github/63/

Intel CC build failed! https://ci.trafficserver.apache.org/job/icc-github/192/

Linux build failed! https://ci.trafficserver.apache.org/job/linux-github/1655/

FreeBSD11 build successful! https://ci.trafficserver.apache.org/job/freebsd-github/1761/

clang-analyzer build successful! https://ci.trafficserver.apache.org/job/clang-analyzer-github/324/

This sounds like a 7.1.0 candidate?

@zwoop yes, 7.1.x is ok.

This is running on Docs.

I might be able to reproduce the issue, but only with H2. I couldn't reproduce it with H1.
What I did are:

Add sleep(5) into consume() of PostBuffer plugin
Set proxy.config.http.transaction_no_activity_timeout_in and proxy.config.http.transaction_active_timeout_in very small (2~5 sec)
Apply the change on this PR
Run ATS with the modified PostBuffer plugin
Send a big POST request with curl

The patch fixes an abort issue but ATS still aborts. (Fails at another assert.)
Fatal: HttpSM.cc:2725: failed assertion `post_transform_info.entry->in_tunnel == true`
2017-03-22 16:14:23.623562 traffic_server[68093:3635467] Fatal: HttpSM.cc:2725: failed assertion `post_transform_info.entry->in_tunnel == true`

(lldb) bt
* thread #14: tid = 0x37790b, 0x00007fffd5191dd6 libsystem_kernel.dylib`__pthread_kill + 10, name = '[ET_NET 11]', stop reason = signal SIGABRT
  * frame #0: 0x00007fffd5191dd6 libsystem_kernel.dylib`__pthread_kill + 10
    frame #1: 0x00007fffd527d787 libsystem_pthread.dylib`pthread_kill + 90
    frame #2: 0x00007fffd50f7420 libsystem_c.dylib`abort + 129
    frame #3: 0x000000000002abd0 libtsutil.7.dylib`ink_abort(message_format="%s:%d: failed assertion `%s`") + 368 at ink_error.cc:99
    frame #4: 0x0000000000027a0f libtsutil.7.dylib`::_ink_assert(expression="post_transform_info.entry->in_tunnel == true", file="HttpSM.cc", line=2725) + 47 at ink_assert.cc:37
    frame #5: 0x000000010014ca3e traffic_server`HttpSM::tunnel_handler_post_or_put(this=0x0000000005cfd9b0, p=0x0000000005cfef00) + 174 at HttpSM.cc:2725
    frame #6: 0x000000010013fa06 traffic_server`HttpSM::tunnel_handler_post(this=0x0000000005cfd9b0, event=103, data=0x0000000003e2ded0) + 1062 at HttpSM.cc:2790
    frame #7: 0x0000000100137708 traffic_server`HttpSM::main_handler(this=0x0000000005cfd9b0, event=103, data=0x0000000003e2ded0) + 776 at HttpSM.cc:2682
    frame #8: 0x000000010001ef60 traffic_server`Continuation::handleEvent(this=0x0000000005cfd9b0, event=103, data=0x0000000003e2ded0) + 112 at I_Continuation.h:153
    frame #9: 0x00000001001be69f traffic_server`Http2Stream::main_event_handler(this=0x0000000003e2db40, event=103, edata=0x0000000000b46aa0) + 1903 at Http2Stream.cc:88
    frame #10: 0x000000010001ef60 traffic_server`Continuation::handleEvent(this=0x0000000003e2db40, event=103, data=0x0000000000b46aa0) + 112 at I_Continuation.h:153
    frame #11: 0x0000000100375a15 traffic_server`EThread::process_event(this=0x0000000002d0c000, e=0x0000000000b46aa0, calling_code=103) + 405 at UnixEThread.cc:143
    frame #12: 0x00000001003761dc traffic_server`EThread::execute(this=0x0000000002d0c000) + 972 at UnixEThread.cc:240
    frame #13: 0x0000000100374f57 traffic_server`spawn_thread_internal(a=0x00000000037000c0) + 103 at Thread.cc:84
    frame #14: 0x00007fffd527aaab libsystem_pthread.dylib`_pthread_body + 180
    frame #15: 0x00007fffd527a9f7 libsystem_pthread.dylib`_pthread_start + 286
    frame #16: 0x00007fffd527a1fd libsystem_pthread.dylib`thread_start + 13

The vc_table is cleanup_all() and tunnel is chain_abort_all(p) before we call tunnel_handler_post_or_put(p).
vc_table.cleanup_all();
tunnel.chain_abort_all(p);

we should call tunnel_handler_post_or_put() only if event == HTTP_TUNNEL_EVENT_DONE.
and replace HttpSM.cc:2790 with "terminate_sm = true;"

@zwoop @SolidWallOfCode
In HttpSM::tunnel_handler_post(), calling tunnel_handler_post_or_put(p) before vc_table.cleanup_all() and tunnel.chain_abort_all(p) to avoid assert that @maskit met.

clang format successful! https://ci.trafficserver.apache.org/job/clang-format-github/89/

RAT check successful! https://ci.trafficserver.apache.org/job/RAT-github/102/

Intel CC build failed! https://ci.trafficserver.apache.org/job/icc-github/215/

Linux build failed! https://ci.trafficserver.apache.org/job/linux-github/1677/

FreeBSD11 build successful! https://ci.trafficserver.apache.org/job/freebsd-github/1784/

AU check successful! https://ci.trafficserver.apache.org/job/autest-github/86/

clang format successful! https://ci.trafficserver.apache.org/job/clang-format-github/90/

RAT check successful! https://ci.trafficserver.apache.org/job/RAT-github/103/

AU check successful! https://ci.trafficserver.apache.org/job/autest-github/87/

FreeBSD11 build successful! https://ci.trafficserver.apache.org/job/freebsd-github/1785/

Intel CC build successful! https://ci.trafficserver.apache.org/job/icc-github/216/

Linux build successful! https://ci.trafficserver.apache.org/job/linux-github/1678/

clang-analyzer build successful! https://ci.trafficserver.apache.org/job/clang-analyzer-github/347/

clang-analyzer build successful! https://ci.trafficserver.apache.org/job/clang-analyzer-github/348/

@oknet The assert has gone. At least it works with H2. Thanks.

RAT check successful! https://ci.trafficserver.apache.org/job/RAT-github/109/

clang format successful! https://ci.trafficserver.apache.org/job/clang-format-github/96/

AU check successful! https://ci.trafficserver.apache.org/job/autest-github/93/

FreeBSD11 build successful! https://ci.trafficserver.apache.org/job/freebsd-github/1791/

Linux build successful! https://ci.trafficserver.apache.org/job/linux-github/1684/

Intel CC build successful! https://ci.trafficserver.apache.org/job/icc-github/222/

clang-analyzer build successful! https://ci.trafficserver.apache.org/job/clang-analyzer-github/354/

I've been running with this on docs for a few days, with no problem. It does not seem to address the threads running at 100% CPU at times though. But assuming this fixes another problem, it seems safe and fine.


fix(experiments): don't overwrite file locations

Fixes experiments overwriting file locations and corrupting them with bad relative paths.

Pulling the manifset out from CI, this fixes the issue:
{
    "locationsFoundAt": [
        "/go/go.mod"
    ],
    "component": {
        "name": "github.com/davecgh/go-spew",
        "version": "v1.1.1",
        "hash": "",
        "packageUrl": {
            "Scheme": "pkg",
            "Type": "golang",
            "Namespace": null,
            "Name": "github.com/davecgh/go-spew",
            "Version": "v1.1.1",
            "Qualifiers": null,
            "Subpath": null
        },
        "type": "Go",
        "id": "github.com/davecgh/go-spew v1.1.1 - Go"
    },
    "detectorId": "Go",
    "isDevelopmentDependency": null,
    "dependencyScope": null,
    "topLevelReferrers": [
        {
            "name": "github.com/sirupsen/logrus",
            "version": "v1.8.1",
            "hash": "",
            "packageUrl": {
                "Scheme": "pkg",
                "Type": "golang",
                "Namespace": null,
                "Name": "github.com/sirupsen/logrus",
                "Version": "v1.8.1",
                "Qualifiers": null,
                "Subpath": null
            },
            "type": "Go",
            "id": "github.com/sirupsen/logrus v1.8.1 - Go"
        }
    ],
    "containerDetailIds": [],
    "containerLayerIds": {}
}


Fix logical mistake in code sample

hasRun should be defined before callback

Thanks for the PR, but the current code works just fine actually :).

Hey @phainv , yeah, but it confuse when try to figure out why it needed =
I think better to fix it


Added feature for getting skins by tag

Hey,
I am currently adding a feature that let's you use "tag" as another tab option together with any tag specified in section.
Do not merge since it doesn't work yet (Sorry, I just found out!). It only picks skins from the "tag" page, not from the categories.
Maybe that's because of how your code works and the differences between the tag and the section system (allthough they both add a /[string] behind the URL, so I first assumed using sections for both would work).
If you find a solution, let me know.
Til

I have fully implemented the required functionality. I'll release new version it in a few minutes.
Thanks for the PR! ♥

https://github.com/MrZillaGold/NameMCWrapper/releases/tag/1.7.2


We offer a DeepSpeed training code for rapid prototyping. Check it out if you are interested.

https://github.com/jinxixiang/magic_animate_unofficial

https://github.com/jinxixiang/magic_animate_unofficial

ty. have you achieved anything better? any examples?

From our observations, the model is still in the optimization process. We plan to share examples and weights at a later date. We're uncertain if we can achieve better results.

From our observations, the model is still in the optimization process. We plan to share examples and weights at a later date. We're uncertain if we can achieve better results.

thanks i will watch repo ever if you post better results

tag


Update ChromeDriver link

The document at the previous url said:

Please note that we have migrated to a new ChromeDriver site.
Current site will be deprecated soon.

@googlebot You may use this contribution under CC0, which means you can use, distribute and relicense it under any other license. Just don't come knocking on my door when it burns down your house...  I'm not signing the documents your owner proposes.

@googlebot Yes, yes. I understood you the first time... Tell your owner if they want me to spend time parsing their legal documents and sign them, there are monetary consequences. Good day. Now please stop spamming the comments.

The bot is automated and doesn't report back to anyone. However, without a signature your merge request can't be accepted.


Left/Right Dock AV window breaks with Players

Default(s) with no Mods running.

Players menu is collapsible BELOW the AV div in core Foundry.

Enabling JUST the minimal UI and it's dependency, the Players aside now completely covers the AV controls and makes them(the controls) completely unusable.

Hi @jfrazierjr can you please make sure you have Minimal UI version 1.5.4?

Thanks, that fixed the problem, or at least made the AV controls usable.

Awesome, have fun


Ed/fix english unicode

There was a unicode string ' in place of every ' throughout the bible text

There was a unicode string ' in place of every ' throughout the bible text


Fixes webview responding shortcuts twice on linux

Add a platform condition for the registering of the "did-keydown" event listener.
Avoided transfering keydown events on Linux.
This PR fixes #82670

Looks reasonable. Let's see if this causes any regression for other comments. Please test using the next insiders build

I had to revert this change as it broke keybindings on linux: #85102
Please take another look at the addressing the problem in a different way

I apologize for not testing all the keybindings and the inconvenience brought by it.
And sorry that I have to drop this issue.
Here's something I tried. Surrounding following lines with the !isLinux if-condition would work properly as expected. However, the codes are there for a reason, I tried but failed to figure out what are these lines for. I doubt the change would break something somewhere else.
https://github.com/microsoft/vscode/blob/7521ebdeb48207b6848a9e13627ed653d08c7eb8/src/vs/workbench/electron-browser/window.ts#L160-L165
and the ipc event is sent here, but not listened anywhere else beside lines in window.ts mentioned above.
https://github.com/microsoft/vscode/blob/9c8b2f2f08e03e93a79c6a643b9b43edb4e41a86/src/vs/platform/menubar/electron-main/menubar.ts#L738-L742

Just make sure any changes:

Don't break a normal keybindings for menu items when a webview is open
Don't break a normal keybindings for menu items when a webview is not opened
That everything works properly with both "window.titleBarStyle": "custom" and "window.titleBarStyle": "native"


Restore version usernames

In footer_helper.rb.
#1795

coverage: 94.555%. remained the same
when pulling 6fba6293e0ad5629cb9bd882a6314b2632b2640d on nimmo-version-usernames
into da8d4f0720fe344af7bf5a2d5f722271dac5b225 on main.


What should the API be for write-only properties

Starting in #45, the API has properties.  Some of NI-XNET's properties are write-only.
Options

Set functions (what #45 did)
Write-only setters.  How well does this work?

We should just leave this as set functions.


Improved error handling in the voice client.

This PR makes a few minor changes to improve error handling and debugging.

We explicitly track the initializing state of the VoiceSession as it goes from created -> connecting -> connected -> audio enabled -> started. This is going to make it easier for applications to observe the state of the session and take appropriate action when errors or timeouts occur.
The onError handler carries a VoiceSessionError object with information about the error. This is a simple message for now, but can be expanded later.
Added a few additional places where .onError is called.

The more substantive (perhaps) change is that .warmup is no longer called in the ctor or when the socket closes. I would much rather this be done explicitly by application code, rather than the VoiceSession trying to be too clever. Constructors are not a good place to be doing actions like opening socket connections, anyway, because it's much harder to deal with errors that happen during the ctor. By having .warmup() be called explicitly, we can create the VoiceSession, set up the error handling logic, call .warmup, and deal gracefully with connection errors that might occur.
These changes allow us to have more graceful error handling in the Santa app.

Thanks! PTAL


fix comments and handle err

This PR did:

fix some comments
handle err instead of missing it
return nil explicitly instead of returning a nil err.


Errors trying to run pkger utility in Docker container with Go 1.13

In effort to try out Pkger in place of Packr (v1) I came across an issue trying to get Pkger to properly pack in a docker container with go 1.13.  I was able to get it working with 1.12 in Docker however it seems to work fine outside docker with go 1.13.  When running the app in docker with 1.12 it also logs an error message that doesn't log when running the app outside docker.
Errors I get building docker container
Step 20/28 : RUN go install github.com/markbates/pkger/cmd/pkger
 ---> Using cache
 ---> d231094cc7a4
Step 21/28 : RUN pkger
 ---> Running in 72b571527ef9
2019/11/09 02:33:07 invalid character 'g' looking for beginning of value
go: downloading github.com/stretchr/testify v1.4.0
go: downloading gopkg.in/go-playground/assert.v1 v1.2.1
go: extracting gopkg.in/go-playground/assert.v1 v1.2.1
go: extracting github.com/stretchr/testify v1.4.0
go: downloading github.com/pmezard/go-difflib v1.0.0
go: downloading gopkg.in/yaml.v2 v2.2.5
go: downloading github.com/davecgh/go-spew v1.1.1
go: extracting github.com/pmezard/go-difflib v1.0.0
go: extracting github.com/davecgh/go-spew v1.1.1
go: extracting gopkg.in/yaml.v2 v2.2.5
go: downloading gopkg.in/check.v1 v1.0.0-20190902080502-41f04d3bba15
go: extracting gopkg.in/check.v1 v1.0.0-20190902080502-41f04d3bba15
go: downloading github.com/kr/pretty v0.1.0
go: extracting github.com/kr/pretty v0.1.0
go: downloading github.com/kr/text v0.1.0
go: extracting github.com/kr/text v0.1.0
2019/11/09 02:33:07 stat : no such file or directory
ERROR: Service 'thunderdome' failed to build: The command '/bin/sh -c pkger' returned a non-zero code: 1

Error logged when running the app in docker container with go 1.12
thunderdome_1  | 2019/11/09 02:37:27 &{%!w(string=go) %!w(*errors.errorString=&{executable file not found in $PATH})}:

You can find source code for my application at https://github.com/StevenWeathers/thunderdome-planning-poker

I encountered this issue and found that if I ran go mod download before attempting pkger it would run successfully.

@requaos That solved the initial issue with Go 1.13, thanks!
Now I only get this error upon runtime, doesn't seem to affect my use case though since I'm using it to serve bundled static assets not ones from filesystem during runtime.
thunderdome_1  | 2019/11/11 01:03:02 exec: "go": executable file not found in $PATH:


Contribution Summary

Group must provide a detailed list of the members and their contributions to the group Inception deliverable.

This additional issue is to ensure all key rubric elements are completed.

Contribution Summary was completed and rubric was followed


Default resx files are extremely useful

"We anticipate that many developers won't create a default language resource file"
I have two use cases, both reasons I always create default resource files.

I always move resx files into a separate assembly on their own to cut down on build time
Sometimes I need to emit error messages to the UI (ie a database save failed in an api call so I need to send a friendly error message to the client). By having the public properties (generated file) I can unit test that my method threw an exception and reported the correct messaging. I can assert a string compare with static typing now instead of magic strings

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

ID: d1833676-ff1b-c587-cc9c-81afffa8ef68
Version Independent ID: ad989395-3f49-4d55-521e-cf6fe56281ee
Content: Globalization and localization in ASP.NET Core
Content Source: aspnetcore/fundamentals/localization.md
Product: aspnet-core
Technology: aspnetcore-fundamentals
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

@ryanbrandenburg  should I add this to the doc? Something like:
We anticipate that many developers won't create a default language resource file. You might want to create a default language resource file to:

move resx files into a separate assembly on their own to cut down on build time
other reason above

I just wanted to note that there are definitely good use cases for default/public resx files.
I learned these techniques from people much smarter than me, so I can only assume there are a lot of folks out there using them :)
It might not hurt to add one or both in some way. I'm sure the second bulleted item could be subject to developer philosophy arguments so that may be better served to live in the comments section as is.
I don't think there's any questioning that build times improve when you move them to another assembly that rarely get recompiled (because it only contains resx files). So if you want to add that bullet I can certainly see pointing it out as an example of a valid use case.

Rather than going into depth about why it is or isn't useful to have a default language resource file why not just omit the line We anticipate that many developers won't create a default language resource file.. It's not clear to me what value it adds, and it suggests that we're trying to dissuade people from using them, rather than simply noting a VS behavior which isn't always conducive to their use.
Along that vein we might also remove  That's usually not what you want with ASP.NET Core. You typically don't have a default .resx resource file (a .resx file without the culture name)..

@ryanbrandenburg  Much better.. This issue will be discoverable from the closed tab on that doc if people want to read about this stuff.

I agree completely that makes much more sense. You're right, I remember interpreting that when I read it as dissuading. I thought ok, well I wonder what they're going to dump it and replace it with in the future.
Thanks Rick!


Syntax error when installing on Python 3.5

When installing GPflow from master on Python 3.5 (Windows), I get a syntax error as shown here:

I assume this is an f-string issue?
Relevant information:
* GPflow version: current master
* Tensorflow version: 2.1.0
* Does your tensorflow use GPU or not: no
* Python version: 3.5
* OS: Windows

As noted in the intro (https://github.com/GPflow/GPflow/#what-does-gpflow-do), GPflow no longer supports python 3.5. The minimum required version is 3.6. Would it be helpful to make this clearer? How else should we point this out?

Ah, right. Perhaps update gpflow.org, which is where I checked first. It still says 3.5.

Oh, I was completely unaware of that! Many thanks for bringing that to our attention!

I've just updated gpflow.org - it should all be up to date for now.

Thanks for bringing this to our attention! (personally I think most developers only ever look straight at github so it's easy to fall out of our minds...)


Crandall - Update seqSight for use in ngsQC protocol

please provide a status update for this ticket

Xinyang will run a Salmonella and an E. coli SRA set through seqSight to align reads to both human and bacterial references. seqSight will output #reads, %reads mapped to TaxonIDs. We hope this might be useful as QC for NGS data. We'll give it a test and see what the outputs look like and have some results to discuss by the end of March 2023. Keith and Xinyang are working on this.

Excellent - excited to see the results and how we can incorporate these new QC values.

Moving this to continue on the April Task list.

@kacrandall any movement on this task?

Move to July task list

@kacrandall Any updates for this item? I may put it in the backlog unless you plan to continue this in August

All the requested data have now been uploaded into the system. Our tasks are complete.


StrictParamFixer - must run before NativeFunctionInvocationFixer

:+1:
however, wondering, shouldn't strict_param run in any case? like native and not native called, it is risky already... ?

Thank you @kubawerlos.


Feature Idea - Selection Editor tool - support selecting multiple entities

There is a need to be able to select multiple entities at once to move them or perform other operations on them as a group.  I think initially this would just be a rectangle selection, similar to the zoom to feature, but possibly be able to have other selection methods (freehand, elliptical, selectByType, etc) similar to GIMP or other drawing applications.
I can assist with this PR.

It sounds like a cool idea.
back in the day, we did a simple implementation for it, in SelectionManagerService, checkout the example here.
You can expand this service or create a new util service, we welcome PRs :)


Question about Turtlebot3 Follow Demo

ISSUE TEMPLATE ver. 0.2.0

Which TurtleBot3 you have?

[x] Burger
[ ] Waffle
[ ] Waffle Pi

Which SBC(Single Board Computer) is working on TurtleBot3?

[x] Raspberry Pi 3
[ ] Intel Joule 570x
[ ] etc (PLEASE, WRITE DOWN YOUR SBC HERE)

Which OS you installed in SBC?

[x] Ubuntu MATE 16.04 or later
[ ] Raspbian
[ ] etc (PLEASE, WRITE DOWN YOUR OS)

Which OS you installed in Remote PC?

 It shows like that:


Use _NewEnum in Client.Query instead ItemIndex

Use _NewEnum because SWbemObjectSet does not have ItemIndex on some systems (Win2003, WinXP).
Closes issues #2, #10 and #12
Tested on WinXP Win2003 R2 server and Win2008 R2 server.
go test passed successfully.

Very good fix, hope this gets pushed as soon as possible.

I staged these at https://github.com/StackExchange/wmi/tree/next and will do some testing before merging to master

Looks like this was missing a Release() call for the IEnumVARIANT, which caused a small memory leak.
Fixed in https://github.com/StackExchange/wmi/commit/13dc73378289294629b5c6def49e5724ed4f847f


Fix EntryPointNotFound on Windows 8 due to missing version check

What does the pull request do?
This PR adds proper Windows OS version checks before p/invoke calls to GetDpiForMonitor (shcore.dll), which is only available on Windows 8.1 and later (reference).
Avalonia previously checked whether shcore.dll is available on the system every time before calling that procedure. However, this doesn't cover the case that a system has an older shcore.dll in place without the required GetDpiForMonitor entry point (this affects all Windows 8 machines).
What is the current behavior?
When a new Avalonia window is being created on Windows 8, the application crashes due to an EntryPointNotFoundException while attempting to retrieve DPI information: https://github.com/AvaloniaUI/Avalonia/blob/6bf37a90801c43f4a0add39c06f13f5fcdbc6757/src/Windows/Avalonia.Win32/WindowImpl.cs#L740
Besides this one, there are two more code snippets affected; check the file diff for details.
What is the updated/expected behavior with this PR?
A version check has been added to skip this call on machines running Windows 8 (not 8.1!); same behavior as on Windows 7.
Fixed issues
Fixes #5357

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

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

isnt ShCoreAvailable  a bit uselessSetProcessDpiAwareness

isnt ShCoreAvailable  a bit uselessSetProcessDpiAwareness

isn't ShCoreAvailable a bit useless? all your imports are only available on Windows 8.1
SetProcessDpiAwareness - Minimum supported client	Windows 8.1 [desktop apps only]
GetDpiForMonitor - Minimum supported client	Windows 8.1 [desktop apps only]
GetScaleFactorForMonitor - Minimum supported client	Windows 8.1 [desktop apps only]

isn't ShCoreAvailable a bit useless? all your imports are only available on Windows 8.1
SetProcessDpiAwareness - Minimum supported client	Windows 8.1 [desktop apps only]
GetDpiForMonitor - Minimum supported client	Windows 8.1 [desktop apps only]
GetScaleFactorForMonitor - Minimum supported client	Windows 8.1 [desktop apps only]

please add this one... https://github.com/AvaloniaUI/Avalonia/blob/master/src/Windows/Avalonia.Win32/Win32GlManager.cs#L12
to the same place..
and also put it in Avalonia.Win32... not inside Avalonia.Direct2D

please add this one... https://github.com/AvaloniaUI/Avalonia/blob/master/src/Windows/Avalonia.Win32/Win32GlManager.cs#L12
to the same place..
and also put it in Avalonia.Win32... not inside Avalonia.Direct2D

Environment.OSVersion won't work properly due to it returning Windows 8 on 8.1 and 10 when the program is not manifested for them, a better solution would be to PInvoke LoadLibrary and GetProcAddress and use that to check if the method is present.

Environment.OSVersion won't work properly due to it returning Windows 8 on 8.1 and 10 when the program is not manifested for them, a better solution would be to PInvoke LoadLibrary and GetProcAddress and use that to check if the method is present.

Yes, good point, please use Win32Platform.WindowsVersion we have already implemented this property to avoid issues.

Yes, good point, please use Win32Platform.WindowsVersion we have already implemented this property to avoid issues.

I'd still recommend using GetProcAddress instead, as I've seen a few cases when even RtlGetVersion returned incorrect values.

I'd still recommend using GetProcAddress instead, as I've seen a few cases when even RtlGetVersion returned incorrect values.

I'd still recommend using GetProcAddress instead, as I've seen a few cases when even RtlGetVersion returned incorrect values.

sure, out of scope for this particular PR though.

I'd still recommend using GetProcAddress instead, as I've seen a few cases when even RtlGetVersion returned incorrect values.

sure, out of scope for this particular PR though.

I'd still recommend using GetProcAddress instead, as I've seen a few cases when even RtlGetVersion returned incorrect values.

sure, out of scope for this particular PR though.

https://github.com/AvaloniaUI/Avalonia/blob/master/src/Windows/Avalonia.Win32/Win32Platform.cs#L85

I'd still recommend using GetProcAddress instead, as I've seen a few cases when even RtlGetVersion returned incorrect values.

sure, out of scope for this particular PR though.

https://github.com/AvaloniaUI/Avalonia/blob/master/src/Windows/Avalonia.Win32/Win32Platform.cs#L85

@ThePBone only needs a little work ... and we can get this merged. Hope your still around.


⚠ Bofrost.at has degraded performance

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

HTTP code: 200
Response time: 1222 ms

Resolved: Bofrost.at performance has improved in 6212c85.


Do not update the modification time of tinc.freeze if nothing has c…

…hanged (close #39)

@soenkehahn I think this should solve the issue.

Yes, works. Thanks a lot.


test flake: assignment to nil map in operator deployment

https://cloudnative-k8sci.southcentralus.cloudapp.azure.com/blue/organizations/jenkins/pmem-csi/detail/PR-860/6/pipeline
[2021-01-23T02:00:22.076Z] Jan 23 02:00:21.862: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
[2021-01-23T02:00:22.076Z] panic: assignment to entry in nil map
[2021-01-23T02:00:22.076Z]
[2021-01-23T02:00:22.076Z] goroutine 1756272 [running]:
[2021-01-23T02:00:22.076Z] github.com/intel/pmem-csi/test/e2e/operator.glob..func2.1.1(0xc0007cc080, 0xc0000b90f8)
[2021-01-23T02:00:22.076Z] 	/mnt/workspace/pmem-csi_PR-860/test/e2e/operator/deployment_api.go:106 +0x20b
[2021-01-23T02:00:22.076Z] created by github.com/intel/pmem-csi/test/e2e/operator.glob..func2.1
[2021-01-23T02:00:22.076Z] 	/mnt/workspace/pmem-csi_PR-860/test/e2e/operator/deployment_api.go:99 +0x873
[2021-01-23T02:00:22.076Z] FAIL	github.com/intel/pmem-csi/test/e2e	14455.988s

I suspect that this is a race between
https://github.com/intel/pmem-csi/blob/e521220167b19164fea60d1f9f4b10dbe2ce599f/test/e2e/operator/deployment_api.go#L106
and
https://github.com/intel/pmem-csi/blob/e521220167b19164fea60d1f9f4b10dbe2ce599f/test/e2e/operator/deployment_api.go#L120

The right solution is to wait for the goroutine to stop while cleaning up.

The right solution is to wait for the goroutine to stop while cleaning up.


Navigating between pages doesn't have transition

For actionable issues, provide additional context and any relevant details, video, or sample code.


Improve error reporting on standard functions

At the moment, many of the standard functions have error reporting, but some don't.  Many of them have just placeholder text stating that an error happened, but don't describe it, and don't report the error to the interpreter which results in largely undefined behavior.  Make sure to fix all of this.

Depends on #9
Rework the system before starting to create new error messages.


Add entry for Android 4 VM

Not interested in adding this to the front page right now. It takes too long to boot and uses too many resources.

Not interested in adding this to the front page right now. It takes too long to boot and uses too many resources.

Well, considering that I managed to post on GitHub from it (#575 ), it might be worth at least adding it to the debug page.


PDP: Investigate and document how queries run in the Query Console

The Query Console seems to respect malformed queries and still produce a result.
For example:
await prisma.post.findMany(
  select: didITypeTheCorrectThing
perhapsNot)

returns a pertinent list of results.
[
  {
    "id": 2,
    "createdAt": "2022-06-22T21:51:32.259Z",
    "updatedAt": "2022-06-22T21:51:32.260Z",
    "title": "Follow Prisma on Twitter",
    "content": "https://www.twitter.com/prisma",
    "published": true,
    "viewCount": 42,
    "authorId": 2
  },
  {
    "id": 3,
    "createdAt": "2022-06-22T21:51:32.892Z",
    "updatedAt": "2022-06-22T21:51:32.893Z",
    "title": "Ask a question about Prisma on GitHub",
    "content": "https://www.github.com/prisma/prisma/discussions",
    "published": true,
    "viewCount": 128,
    "authorId": 3
  },
...

The question was whether a badly formed deleteMany does the same. But it doesn't. For example:
await prisma.post.deleteMany({
 whhere: {
   post_id: 1
 }
})

results in the following error:
[
  {
    "error": {
      "type": "PrismaClientUnknownRequestError",
      "code": "unknown",
      "message": "Unknown arg `whhere` in whhere for type AffectedRowsOutput. Did you mean `where`?\n",
      "stack": "Error: Unknown arg `whhere` in whhere for type AffectedRowsOutput. Did you mean `where`?\n\n    at Document.validate (/var/task/node_modules/@prisma/client/runtime/index.js:48195:20)\n    at PrismaClient._executeRequest (/var/task/node_modules/@prisma/client/runtime/index.js:50634:17)\n    at consumer (/var/task/node_modules/@prisma/client/runtime/index.js:50571:23)\n    at /var/task/node_modules/@prisma/client/runtime/index.js:50575:76\n    at runInChildSpan (/var/task/node_modules/@prisma/client/runtime/index.js:49780:12)\n    at /var/task/node_modules/@prisma/client/runtime/index.js:50575:20\n    at AsyncResource.runInAsyncScope (async_hooks.js:197:9)\n    at PrismaClient._request (/var/task/node_modules/@prisma/client/runtime/index.js:50574:86)\n    at requestFn (/var/task/node_modules/@prisma/client/runtime/index.js:49316:65)\n    at /var/task/node_modules/@prisma/client/runtime/index.js:49329:18"
    }
  }
]

👋 we're cleaning up our backlog of issues and are closing everything older than two years. If you still feel that this issue is relevant, please feel free to re-open and our team will take a look. Thank you!


[Feature] WaterButler move n copy

@chrisseto Which waterbutler branch does this depend on?

@sloria https://github.com/CenterForOpenScience/waterbutler/pull/31

Merged into release/0.37.0


Edit of adjacent ranges does not work.

From @vilic on October 31, 2015 17:29
For example:
edit.delete(new Range(1, 1, 1, 2));
edit.delete(new Range(1, 2, 1, 3));

This issue applies to other operations like replace as well.
Copied from original issue: Microsoft/vscode-extensionbuilders#72

From @vilic on November 9, 2015 1:42
@seanmcbreen Any comment on this?

From @jrieken on November 9, 2015 8:55
@alexandrudima  will know

@vilic just mailed Alex to ensure he has seen this.

From @vilic on November 14, 2015 1:32
@alexandrudima The ranges are results of other code, transforming these edits to a single one means for every series of edits I'll need to ensure they do not touch, and if so, merge them properly. Which could be non-trivial work.
Is there a reason why edits of adjacent ranges are not allowed?

From @alexandrudima on November 14, 2015 0:49
@vilic Yeah, the edits are not allowed to touch. As a workaround, why not do a single edit instead?
edit.delete(new Range(1, 1, 1, 3));

From @alexandrudima on November 16, 2015 17:18
@vilic It is some debt left over from how multiple cursors were implemented. I still need to migrate some internal code that I think still depends on this limitation, then I can relax the touching check.

From @vilic on November 17, 2015 1:30
@alexandrudima Thanks for clarification~ Feel free to close this issue if you want it closed for now. :)

Let's track this in #761


tinc: Configuring a hostname as the Address fails

Describe the bug
When specifying a DNS name instead of an IP address as the Address entry for a tinc host, connection will fail with an error like the following:
Aug 10 13:23:50 machine-haless-03.cryto.net tincd[13425]: Error looking up machine-borg2-01.cryto.net port 655: Device or resource busy
Aug 10 13:23:50 machine-haless-03.cryto.net tincd[13425]: Could not set up a meta connection to machine_borg2_01_cryto_net
Aug 10 13:23:50 machine-haless-03.cryto.net tincd[13425]: Trying to re-establish outgoing connection in 30 seconds

When setting the IP address directly, it connects fine, with no further changes.
To Reproduce
Steps to reproduce the behavior:

Create a services.tinc configuration, with AutoConnect = yes in the extraConfig.
Set Address for a remote peer to a DNS name.

Expected behavior
Connection should succeed, assuming a correctly-configured peer.
Additional context
Only one reference can be found on the web for this issue, and it's in the #nixos channel, which suggests that this may be a NixOS-specific bug: https://logs.nix.samueldr.com/nixos/2018-08-30#1522242
Metadata

system: "x86_64-linux"
host os: Linux 4.19.56, NixOS, 19.03.173251.56d94c8c69f (Koi)
multi-user?: yes
sandbox: no
version: nix-env (Nix) 2.2.2
channels(root): "nixos-19.03.173251.56d94c8c69f"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module: services.tinc

DNS resolution seems to work with services.tinc.networks.*.chroot = false.

I'm having this problem on Fedora 34 as well: it does appear related to the chroot not allowing DNS.

This is expected according to Error looking up hydrogen.supersandro.de port 655: Device or resource


Make entity-system a npm module

So that it can be installed with, e.g., npm install entity-system. That would be cool.

Making it available in bower would be super cool as well. And making it a version 1.0 while we're at it.

So all common names are taken on npm or bower, like:

entity
entity-system
entity-system-js
ecs
ecsjs

I'll need to find an original name for this package. ensyja (which stand for ENtity SYstem JAvascript is free, but I'm not sure that's a good name. (Note that ensy is available as well. )
@maxailloud, since you contributed to this, do you have an opinion or a better suggestion?

Maybe something like:

js-entity-system (a bit silly I know)
esm-js (esm is for Entity System Model)

So I went with ensy 'cause whatever. :)
npm: https://www.npmjs.com/package/ensy
bower: http://bower.io/search/?q=ensy (though I can't see it yet, I hope it worked)
Anyone wiling to test this is very welcome! Also I guess a good test would be to update Total Madness Arena to use those packages instead of git submodules.


Modified time on relation

Is your feature request related to a problem? Please describe.
Currently when creating a relation between two nodes that have been connected previously, a new relationship won't be created and/or the previous relation won't be updated.
Describe the solution you'd like
A way to solve this would be to set a property "modifiedOn" o.s. and update existing relationships on a MERGE.

The feature will be as the following.
On configuring the api for a service, the developer will be able to:

Turn on the feature to add Created or Modified dates to the nodes
Turn on the feature to add Created or Modified dates to the relations
Set the key in which they want to have for modified or created dates e.g. modifiedOn, createdOn,....

Then on each merge, if the feature is on and the merge is performing create, it will set a create date and if it is updating it will set a modified date.


CISv2 - ClusterScan is seen in Failed state when there are no failures in the scan

What kind of request is this (question/bug/enhancement/feature request): bug
Steps to reproduce (least amount of steps as possible):

Create a ClusterScan CR and give in invalid value of scanProfileName
The scan is currently stuck in "In progress" state
Edit the clusterScan CR and give in the correct scanProfileName: rke-profile-permissive
The scan run finishes, but the Cluster Scan is seen in "Failed state"

spec:
  scanProfileName: rke-profile-permissive
status:
  conditions:
  - lastUpdateTime: "2020-08-31T19:41:42Z"
    status: "True"
    type: Stalled
  - lastUpdateTime: "2020-08-31T20:36:39Z"
    status: "True"
    type: Created
  - lastUpdateTime: "2020-08-31T20:36:49Z"
    status: "True"
    type: RunCompleted
  - lastUpdateTime: "2020-08-31T20:36:49Z"
    status: "True"
    type: Complete
  - status: Unknown

Expected Result:
ClusterScan should be in Pass/Active state
Other details that may be helpful:
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): master-head - commit id: 8d9cedde93
Installation option (single install/HA): HA

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): custom - 8 nodes - 3 etcd, 2 control and 3 worker nodes
Kubernetes version (use kubectl version):

1.18

This issue has been fixed and available to test via the new tag:

repository: rancher/cis-operator
tag: v0.0.4
The rancher-cis-benchmark chart has been updated to use this tag. https://github.com/rancher/charts/pull/586

Fix provided:

The conditions under the ClusterScan.Status field will be cleared when the scanProfileName is corrected and a new scan is launched. This will update the state of the ClusterScan correctly.

Example: Here is how the clusterscan fields will be displayed that shows the CLUSTERSCANPROFILE used and the STATUS field will reflect the state of the scan as (pass/fail/error/reporting)
$ kubectl --kubeconfig ~/.kube/test_config_master  get clusterscans

NAME           STATUS   CLUSTERSCANPROFILE       TOTAL   PASS   FAIL   SKIP   NOT APPLICABLE   LASTRUNTIMESTAMP
rke-cis        fail     rke-profile-hardened     92      59     13     0      20               2020-09-05T01:18:28Z
rke-cis-perm   pass     rke-profile-permissive   92      58     0      0      34               2020-09-05T01:19:36Z

Verified on master-head - commit id: 3ca11da829

Deploy cis-operator from repo - https://github.com/prachidamle/charts.git branch: cis-v2-chart. chart Images:

  cisoperator:
    repository: rancher/cis-operator
    tag: v0.0.4
  securityScan:
    repository: prachidamle/security-scan
    tag: v0.1.20

Create a ClusterScan CR and give in invalid value of scanProfileName
The scan is currently stuck in "In progress" state
Edit the clusterScan CR and give in the correct scanProfileName: rke-profile-permissive
The scan run finishes, but the Cluster Scan is seen in state Pass but with a red background color.

Expected Result:
The background color of the state Pass should NOT be red. Logging a separate issue to track this. - https://github.com/rancher/cis-operator/issues/23


example: connecting external wallet

Closing this as it mostly served as an example. We're gonna add proper built-in support for external wallets soon: https://github.com/latticexyz/mud/issues/718


Forbid usage of Void

Detekt should warn about using Void since Kotlin has Unit instead.
Although, maybe java.lang.Void::class should be allowed.

Good point. This might be called OptionalVoid to be in line with the existing rule.

I'll take a stab at it.

@egor-n cool! You might want to take a look at #1034

@schalkms I have opened #1059. I don't think this rule falls into the Optional* set. Usage of Void doesn't seem optional to me.

I agree @egor-n


support laravel-modules v11 for laravel 11

Hi @vellea,
Thank you for your valuable contribution. A lot has changed in Nwidart larave-modules v11, including the folder structure (e.g App now becomes app). Furthermore, v11 now only supports for Laravel 11 and not Laravel 10. To still support Laravel 10, we had to release v3.x which only supports laravel-modules v10. To support laravel-modules v11, we will have to do another major release (4.x) which only supports Laravel 11.


Assignment 3

Pretty good markdown. You should use message=FALSE in your r chunks to avoid the messy comments with the hashtags in your output.


failed to authenticate with fastlane API key with Azure pipeline

New Issue Checklist

[x] Updated fastlane to the latest version
[x ] I read the Contribution Guidelines
[x ] I read docs.fastlane.tools
[x ] I searched for existing GitHub issues

Issue Description

Hi Team - We are deploying the iOS mobile app to the app store (PROD) using Fastlane version (2.219.0). we have provided the API key ID, issuer id, and Filepath. however, it asks for the password.
Command executed

Please check the yaml executed and referring lane in Fastlane file.

script: >-
         fastlane ios release appstore \
         --api_key "
             {
                 \"filepath\": \"$(API Key ID)\",
                 \"key_id\": \"$(API Issuer ID)\",
                 \"issuer_id\": \"$(API Key base 64)\"
             }
         "
         build_number: **
         app_version: ***
         team_id: ***
         app_identifier: '******'
         metadata_path: '$(Build.SourcesDirectory)/ios/fastlane/metadata/en-US/release_notes.txt'

       displayName: Promote build to prod release
       workingDirectory: $(Build.SourcesDirectory)/ios/

fastlane file:
default_platform(:ios)
platform :ios do
desc "Release Testflight Build"
lane :release do |options|
deliver(

  automatic_release: true,
  skip_binary_upload: false,
  force: true,
  build_number: options[:build_number],
  submit_for_review: true,
  team_id: options[:team_id],
  app_version: options[:app_version],
  app_identifier: options[:app_identifier],
  metadata_path: options[:metadata_path],
  skip_screenshots: true,
  overwrite_screenshots: false,
  precheck_include_in_app_purchases: false,
  # https://github.com/artsy/eigen/blob/faa02e2746194d8d7c11899474de9c517435eca4/fastlane/Fastfile#L131-L149
  submission_information: {
    add_id_info_uses_idfa: false,
    }
  )

end
end
Complete output when running fastlane, including the stack trace and command used

 [2024-02-15T06:48:57.4858150Z Generating script.
2024-02-15T06:48:57.4866170Z ========================== Starting Command Output ===========================
2024-02-15T06:48:57.4881610Z [command]/bin/bash --noprofile --norc /Users/runner/work/_temp/25151988-457d-4106-8c24-a4965455db04.sh
2024-02-15T06:48:59.4550050Z [06:48:59]: fastlane detected a Gemfile in the current directory
2024-02-15T06:48:59.4551950Z [06:48:59]: However, it seems like you didn't use `bundle exec`
2024-02-15T06:48:59.4552650Z [06:48:59]: To launch fastlane faster, please use
2024-02-15T06:48:59.4552950Z [06:48:59]:
2024-02-15T06:48:59.4553270Z [06:48:59]: $ bundle exec fastlane ios release appstore  --api_key
2024-02-15T06:48:59.4553570Z     {
2024-02-15T06:48:59.4554630Z         "filepath": "***",
2024-02-15T06:48:59.4555030Z         "key_id": "***",
2024-02-15T06:48:59.4556410Z         "issuer_id": "***"
2024-02-15T06:48:59.4557470Z     }
2024-02-15T06:48:59.4558070Z  build_number: ** app_version: *** team_id: *** app_identifier: ***** metadata_path: /Users/runner/work/1/s/ios/fastlane/metadata/en-US/release_notes.txt
2024-02-15T06:48:59.4558840Z [06:48:59]:
2024-02-15T06:48:59.4559320Z [06:48:59]: Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile
2024-02-15T06:49:01.3301470Z [06:49:01]: Sending anonymous analytics information
2024-02-15T06:49:01.3363940Z [06:49:01]: Learn more at https://docs.fastlane.tools/#metrics
2024-02-15T06:49:01.3520980Z [06:49:01]: No personal or sensitive data is sent.
2024-02-15T06:49:01.3547490Z [06:49:01]: You can disable this by adding `opt_out_usage` at the top of your Fastfile
2024-02-15T06:49:01.3569670Z [06:49:01]: ------------------------------
2024-02-15T06:49:01.3600350Z [06:49:01]: --- Step: default_platform ---
2024-02-15T06:49:01.3616120Z [06:49:01]: ------------------------------
2024-02-15T06:49:01.3631850Z [06:49:01]: Driving the lane 'ios release' 🚀
2024-02-15T06:49:01.4161550Z [06:49:01]: ---------------------
2024-02-15T06:49:01.4184130Z [06:49:01]: --- Step: deliver ---
2024-02-15T06:49:01.4213570Z [06:49:01]: ---------------------
2024-02-15T06:49:01.4232790Z [06:49:01]: Successfully loaded '/Users/runner/work/1/s/ios/fastlane/Deliverfile' 📄
2024-02-15T06:49:01.4264130Z [06:49:01]: No values defined in './fastlane/Deliverfile'
2024-02-15T06:49:01.4298140Z [06:49:01]: Login to App Store Connect<EMAIL_ADDRESS>2024-02-15T06:49:01.4568590Z -------------------------------------------------------------------------------------
2024-02-15T06:49:01.4596180Z Please provide your Apple Developer Program account credentials
2024-02-15T06:49:01.4609110Z The login information you enter will be stored in your macOS Keychain
2024-02-15T06:49:01.4634880Z You can also pass the password using the `FASTLANE_PASSWORD` environment variable
2024-02-15T06:49:01.4655290Z See more information about it on GitHub: https://github.com/fastlane/fastlane/tree/master/credentials_manager
2024-02-15T06:49:01.4678090Z -------------------------------------------------------------------------------------
2024-02-15T06:49:01.4697110Z +--------------------------------+
2024-02-15T06:49:01.4727520Z |          Lane Context          |
2024-02-15T06:49:01.4739120Z +------------------+-------------+
2024-02-15T06:49:01.4761310Z | DEFAULT_PLATFORM | ios         |
2024-02-15T06:49:01.4786820Z | PLATFORM_NAME    | ios         |
2024-02-15T06:49:01.4809500Z | LANE_NAME        | ios release |
2024-02-15T06:49:01.4831090Z +------------------+-------------+
2024-02-15T06:49:01.4843850Z [06:49:01]: Missing password for user<EMAIL_ADDRESS>and running in non-interactive shell
2024-02-15T06:49:01.4958420Z
2024-02-15T06:49:01.4975450Z +---------------------------------------+
2024-02-15T06:49:01.4991280Z |           fastlane summary            |
2024-02-15T06:49:01.4999730Z +------+------------------+-------------+
2024-02-15T06:49:01.5011870Z | Step | Action           | Time (in s) |
2024-02-15T06:49:01.5019860Z +------+------------------+-------------+
2024-02-15T06:49:01.5023140Z | 1    | default_platform | 0           |
2024-02-15T06:49:01.5033820Z | 💥   | deliver          | 0           |
2024-02-15T06:49:01.5044370Z +------+------------------+-------------+
2024-02-15T06:49:01.5053110Z
2024-02-15T06:49:01.5082650Z [06:49:01]: fastlane finished with errors
2024-02-15T06:49:01.5119300Z
2024-02-15T06:49:01.5145450Z Looking for related GitHub issues on fastlane/fastlane...
2024-02-15T06:49:01.5145730Z
2024-02-15T06:49:01.6767430Z Found no similar issues. To create a new issue, please visit:
2024-02-15T06:49:01.6824660Z https://github.com/fastlane/fastlane/issues/new
2024-02-15T06:49:01.6860860Z Run `fastlane env` to append the fastlane environment to your issue
2024-02-15T06:49:01.6941490Z /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/credentials_manager/lib/credentials_manager/account_manager.rb:135:in `ask_for_login': \e[31m[!] Missing password for user<EMAIL_ADDRESS>and running in non-interactive shell\e[0m (RuntimeError)
2024-02-15T06:49:01.6981230Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/credentials_manager/lib/credentials_manager/account_manager.rb:56:in `password'
2024-02-15T06:49:01.7015890Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/spaceship/lib/spaceship/client.rb:383:in `login'
2024-02-15T06:49:01.7054950Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/spaceship/lib/spaceship/client.rb:355:in `login'
2024-02-15T06:49:01.7091500Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/spaceship/lib/spaceship/tunes/spaceship.rb:24:in `login'
2024-02-15T06:49:01.7117780Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/spaceship/lib/spaceship/connect_api/client.rb:56:in `login'
2024-02-15T06:49:01.7124160Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/spaceship/lib/spaceship/connect_api/spaceship.rb:85:in `login'
2024-02-15T06:49:01.7138290Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/deliver/lib/deliver/runner.rb:43:in `login'
2024-02-15T06:49:01.7152820Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/deliver/lib/deliver/runner.rb:23:in `initialize'
2024-02-15T06:49:01.7156640Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/fastlane/lib/fastlane/actions/upload_to_app_store.rb:22:in `new'
2024-02-15T06:49:01.7165250Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/fastlane/lib/fastlane/actions/upload_to_app_store.rb:22:in `run'
2024-02-15T06:49:01.7170100Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/fastlane/lib/fastlane/runner.rb:263:in `block (2 levels) in execute_action'
2024-02-15T06:49:01.7179620Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/fastlane/lib/fastlane/actions/actions_helper.rb:69:in `execute_action'
2024-02-15T06:49:01.7183600Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/fastlane/lib/fastlane/runner.rb:255:in `block in execute_action'
2024-02-15T06:49:01.7186070Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/fastlane/lib/fastlane/runner.rb:229:in `chdir'
2024-02-15T06:49:01.7209410Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/fastlane/lib/fastlane/runner.rb:229:in `execute_action'
2024-02-15T06:49:01.7211180Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/fastlane/lib/fastlane/runner.rb:157:in `trigger_action_by_name'
2024-02-15T06:49:01.7216250Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/fastlane/lib/fastlane/fast_file.rb:159:in `method_missing'
2024-02-15T06:49:01.7225680Z 	from Fastfile:23:in `block (2 levels) in parsing_binding'
2024-02-15T06:49:01.7241000Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/fastlane/lib/fastlane/lane.rb:41:in `call'
2024-02-15T06:49:01.7246560Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/fastlane/lib/fastlane/runner.rb:49:in `block in execute'
2024-02-15T06:49:01.7270690Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/fastlane/lib/fastlane/runner.rb:45:in `chdir'
2024-02-15T06:49:01.7290260Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/fastlane/lib/fastlane/runner.rb:45:in `execute'
2024-02-15T06:49:01.7298240Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/fastlane/lib/fastlane/lane_manager.rb:46:in `cruise_lane'
2024-02-15T06:49:01.7310090Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/fastlane/lib/fastlane/command_line_handler.rb:34:in `handle'
2024-02-15T06:49:01.7311100Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/fastlane/lib/fastlane/commands_generator.rb:110:in `block (2 levels) in run'
2024-02-15T06:49:01.7340670Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/commander-4.6.0/lib/commander/command.rb:187:in `call'
2024-02-15T06:49:01.7366470Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/commander-4.6.0/lib/commander/command.rb:157:in `run'
2024-02-15T06:49:01.7417320Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/commander-4.6.0/lib/commander/runner.rb:444:in `run_active_command'
2024-02-15T06:49:01.7443750Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:124:in `run!'
2024-02-15T06:49:01.7466740Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/commander-4.6.0/lib/commander/delegates.rb:18:in `run!'
2024-02-15T06:49:01.7477980Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/fastlane/lib/fastlane/commands_generator.rb:354:in `run'
2024-02-15T06:49:01.7480850Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/fastlane/lib/fastlane/commands_generator.rb:43:in `start'
2024-02-15T06:49:01.7487580Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/fastlane/lib/fastlane/cli_tools_distributor.rb:123:in `take_off'
2024-02-15T06:49:01.7503720Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/bin/fastlane:23:in `'
2024-02-15T06:49:01.7513840Z 	from /usr/local/lib/ruby/gems/3.0.0/bin/fastlane:25:in `load'
2024-02-15T06:49:01.7520850Z 	from /usr/local/lib/ruby/gems/3.0.0/bin/fastlane:25:in `'
2024-02-15T06:49:01.7569390Z /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/credentials_manager/lib/credentials_manager/account_manager.rb:135:in `ask_for_login': Missing password for user<EMAIL_ADDRESS>and running in non-interactive shell (RuntimeError)
2024-02-15T06:49:01.7631630Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/credentials_manager/lib/credentials_manager/account_manager.rb:56:in `password'
2024-02-15T06:49:01.7653300Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/spaceship/lib/spaceship/client.rb:383:in `login'
2024-02-15T06:49:01.7670790Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/spaceship/lib/spaceship/client.rb:355:in `login'
2024-02-15T06:49:01.7687760Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/spaceship/lib/spaceship/tunes/spaceship.rb:24:in `login'
2024-02-15T06:49:01.7710610Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/spaceship/lib/spaceship/connect_api/client.rb:56:in `login'
2024-02-15T06:49:01.7746700Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/spaceship/lib/spaceship/connect_api/spaceship.rb:85:in `login'
2024-02-15T06:49:01.7758280Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/deliver/lib/deliver/runner.rb:43:in `login'
2024-02-15T06:49:01.7771090Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/deliver/lib/deliver/runner.rb:23:in `initialize'
2024-02-15T06:49:01.7773980Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/fastlane/lib/fastlane/actions/upload_to_app_store.rb:22:in `new'
2024-02-15T06:49:01.7777230Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/fastlane/lib/fastlane/actions/upload_to_app_store.rb:22:in `run'
2024-02-15T06:49:01.7779290Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/fastlane/lib/fastlane/runner.rb:263:in `block (2 levels) in execute_action'
2024-02-15T06:49:01.7781970Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/fastlane/lib/fastlane/actions/actions_helper.rb:69:in `execute_action'
2024-02-15T06:49:01.7784160Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/fastlane/lib/fastlane/runner.rb:255:in `block in execute_action'
2024-02-15T06:49:01.7806730Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/fastlane/lib/fastlane/runner.rb:229:in `chdir'
2024-02-15T06:49:01.7813240Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/fastlane/lib/fastlane/runner.rb:229:in `execute_action'
2024-02-15T06:49:01.7829010Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/fastlane/lib/fastlane/runner.rb:157:in `trigger_action_by_name'
2024-02-15T06:49:01.7839020Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/fastlane/lib/fastlane/fast_file.rb:159:in `method_missing'
2024-02-15T06:49:01.7846680Z 	from Fastfile:23:in `block (2 levels) in parsing_binding'
2024-02-15T06:49:01.7883130Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/fastlane/lib/fastlane/lane.rb:41:in `call'
2024-02-15T06:49:01.7883740Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/fastlane/lib/fastlane/runner.rb:49:in `block in execute'
2024-02-15T06:49:01.7884260Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/fastlane/lib/fastlane/runner.rb:45:in `chdir'
2024-02-15T06:49:01.7884850Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/fastlane/lib/fastlane/runner.rb:45:in `execute'
2024-02-15T06:49:01.7899100Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/fastlane/lib/fastlane/lane_manager.rb:46:in `cruise_lane'
2024-02-15T06:49:01.7908440Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/fastlane/lib/fastlane/command_line_handler.rb:34:in `handle'
2024-02-15T06:49:01.7911120Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/fastlane/lib/fastlane/commands_generator.rb:110:in `block (2 levels) in run'
2024-02-15T06:49:01.7926910Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/commander-4.6.0/lib/commander/command.rb:187:in `call'
2024-02-15T06:49:01.7935000Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/commander-4.6.0/lib/commander/command.rb:157:in `run'
2024-02-15T06:49:01.7941820Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/commander-4.6.0/lib/commander/runner.rb:444:in `run_active_command'
2024-02-15T06:49:01.7954560Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:124:in `run!'
2024-02-15T06:49:01.7972210Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/commander-4.6.0/lib/commander/delegates.rb:18:in `run!'
2024-02-15T06:49:01.7975870Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/fastlane/lib/fastlane/commands_generator.rb:354:in `run'
2024-02-15T06:49:01.7979440Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/fastlane/lib/fastlane/commands_generator.rb:43:in `start'
2024-02-15T06:49:01.7983240Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/fastlane/lib/fastlane/cli_tools_distributor.rb:123:in `take_off'
2024-02-15T06:49:01.7998000Z 	from /usr/local/lib/ruby/gems/3.0.0/gems/fastlane-2.219.0/bin/fastlane:23:in `'
2024-02-15T06:49:01.8003050Z 	from /usr/local/lib/ruby/gems/3.0.0/bin/fastlane:25:in `load'
2024-02-15T06:49:01.8009370Z 	from /usr/local/lib/ruby/gems/3.0.0/bin/fastlane:25:in `'
2024-02-15T06:49:01.8037960Z
2024-02-15T06:49:01.8082700Z ##[error]Bash exited with code '1'.
2024-02-15T06:49:01.8152570Z ##[section]Finishing: Promote build to prod release]

Environment

2024-02-15T06:54:52.4234750Z ### Stack
2024-02-15T06:54:52.4307440Z
2024-02-15T06:54:52.4408590Z | Key                         | Value                                            |
2024-02-15T06:54:52.4510300Z | --------------------------- | ------------------------------------------------ |
2024-02-15T06:54:52.4611480Z | OS                          | 12.7.3                                           |
2024-02-15T06:54:52.4712620Z | Ruby                        | 3.0.6                                            |
2024-02-15T06:54:52.4814130Z | Bundler?                    | false                                            |
2024-02-15T06:54:52.4915220Z | Git                         | git version 2.43.0                               |
2024-02-15T06:54:52.5016380Z | Installation Source         | /usr/local/lib/ruby/gems/3.0.0/bin/fastlane      |
2024-02-15T06:54:52.5117600Z | Host                        | macOS 12.7.3 (21H1015)                           |
2024-02-15T06:54:52.5218730Z | Ruby Lib Dir                |<EMAIL_ADDRESS>         |
2024-02-15T06:54:52.5301360Z | OpenSSL Version             | OpenSSL 3.1.1 30 May 2023                        |
2024-02-15T06:54:52.5329800Z | Is contained                | false                                            |
2024-02-15T06:54:52.5402820Z | Is homebrew                 | false                                            |
2024-02-15T06:54:52.5438640Z | Is installed via Fabric.app | false                                            |
2024-02-15T06:54:52.5494480Z | Xcode Path                  | /Applications/Xcode_14.2.app/Contents/Developer/ |
2024-02-15T06:54:52.5537880Z | Xcode Version               | 14.2                                             |
2024-02-15T06:54:52.5569630Z | Swift Version               | 5.7.2                                            |

Gem
Version
Update-Status

fastlane
2.219.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
| ipaddr                          | 1.2.2        |
| io-wait                         | 0.2.0        |
| zlib                            | 2.0.0        |
| resolv                          | 0.2.1        |
| time                            | 0.1.1        |
| open-uri                        | 0.1.0        |
| mutex_m                         | 0.1.1        |
| net-protocol                    | 0.1.1        |
| ostruct                         | 0.3.1        |
| english                         | 0.7.1        |
| erb                             | 2.2.0        |
| strscan                         | 3.0.1        |
| abbrev                          | 0.1.0        |
| io-console                      | 0.5.7        |
| tempfile                        | 0.1.1        |
| delegate                        | 0.2.0        |
| fileutils                       | 1.5.0        |
| tmpdir                          | 0.1.2        |
| base64                          | 0.1.0        |
| singleton                       | 0.1.1        |
| net-http                        | 0.1.1        |
| open3                           | 0.1.1        |
| nkf                             | 0.1.0        |
| prettyprint                     | 0.1.1        |
| pp                              | 0.2.1        |
| find                            | 0.1.0        |
| yaml                            | 0.1.1        |
| psych                           | 3.3.2        |

I believe api_key is an option to deliver but you seem to be passing it the fastlane CLI instead.
See how this is done in the Passing parameters section of the doc.

Hi @lacostej
I have tried the  CLI command:   fastlane ios release  filepath: $(API Key ID) key_id: $(API Issuer ID) issuer_id:$(API Key base 64) build_number: *** app_version:***** team_id:**** app_identifier:*******' metadata_path:'$(Build.SourcesDirectory)/ios/fastlane/metadata/en-US/release_notes.txt'
and fastlane file:
deliver(
api_key = app_store_connect_api_key(
key_id: options[:filepath],
issuer_id: options[:key_id],
key_content: options[:issuer_id],
),
pilot(api_key: api_key),
skip_binary_upload: false,
force: true,
build_number: options[:build_number],
automatic_release: true,
submit_for_review: true,
team_id: options[:team_id],
app_version: options[:app_version],
app_identifier: options[:app_identifier],
metadata_path: options[:metadata_path],
skip_screenshots: true,
overwrite_screenshots: false,
precheck_include_in_app_purchases: false,
# https://github.com/artsy/eigen/blob/faa02e2746194d8d7c11899474de9c517435eca4/fastlane/Fastfile#L131-L149
submission_information: {
add_id_info_uses_idfa: false,
}
)
and receiving "invalid curve issue"


compact header not loading in 0.90.2

Describe the bug:

I get the following error in my chrome console and the compact header does not load :
'''TypeError: Cannot read property 'querySelector' of null
at compact-custom-header.lib.js?v0.2.7:17 '''
Config YAML:
<!-- Paste your lovelace code for the card after this line -->
title: Thús
resources:
  - url: /local/card-tools.js
    type: js
  - url: /local/layout-card.js
    type: js
  - url: /local/custom-lovelace/compact-custom-header/compact-custom-header.js
    type: module
  - url: /local/surveillance-card.js?v=0
    type: module
  - url: /local/tracker-card.js?track=true
    type: module
views:
    # View tab title.
  - title: update
    panel: false
    cards:
      - type: custom:tracker-card
  - title: home
#    panel: true
    cards:
#      - type: custom:layout-card
#      layout: vertical
#      cards:
      - type: entities
        title: Entities card sample
        show_header_toggle: false
        entities:
          - climate.woonkamer
          - climate.slaapkamer
          - climate.studeerkamer
          - climate.warm_water
      - type: entities
        title: Entities card sample
        show_header_toggle: false
        entities:
          - binary_sensor.0x00158d00028de7c1_contact
          - binary_sensor.0x00158d00028de79b_contact
          - binary_sensor.0x00158d0002375c95_water_leak
      - type: picture-glance
        entities: []
        camera_image: camera.dafang3
      - type: weather-forecast
        entity: weather.br_unknown_station
      - type: media-control
        entity: media_player.spotify
      - type: custom:compact-custom-header

HA and/or Browser Error:

'''TypeError: Cannot read property 'querySelector' of null
at compact-custom-header.lib.js?v0.2.7:17 '''
HA, Card, and Browser Versions:

ha : 0.90.2
compact header : 1.0.2b1

Looks like you may have updated from a very old version of CCH. The file compact-custom-header.lib.js no longer exists in the new version. I would reinstall the card manually. Be sure to follow the installation instructions in readme.

@maykar I just installed it for the first time 1-2 months ago and it is updated by custom updater so it seems like I should run the newest version. Also cleared my cache etc. But I'll completely re-install (with the manual method than I suppose) and let you know

There was a complete rewrite that required a manual reinstall a while ago. I took the project off of custom updater for a week and had a warning about it on the github for a month or so. Think you just happened to miss it. Quite a bit of new features have been added since then including header styling and very soon I will be adding conditional styling as well.

Has anyone tried doing conditional styling using the config-template-card?

I thought about that, but I don't think that the header would "update" when a condition is met. Like when a notification comes in or an entity state becomes "on" the header would need to render or a script would need to insert a style into a element.
While I believe it's possible, it would be quite a bit of javascript written into config-template.

My issue was solved after adding the version to the resource in ui-lovelace.yaml. Thanks again!


Added PR Template

Description
We've gotten rid of the Cesium Concierge, who will no longer post handy comments like this.
While CLA checking is still in the works as part of a separate effort, this PR template aims to replace the functionality of that comment.
Issue number and link
Fixes https://github.com/CesiumGS/cesium/issues/6167
Testing plan
I've used the template for this PR.
It will show up for PRs once merged into main.
Author checklist

[x] I have submitted a Contributor License Agreement
[x] I have added my name to CONTRIBUTORS.md
[ ] ~I have updated CHANGES.md with a short summary of my change~ N/A
[ ] ~I have added or updated unit tests to ensure consistant code coverage~ N/A
[ ] ~I have update the inline documentation, and included code examples where relevant~ N/A
[x] I have performed a self-review of my code

The CI failure is due to the latest update of our eslint rules. I'll open a separate PR to resolve it.

It seems like the main two things losing Concierge lost was checking for a lack of changes in specific files. I feel like there should be solutions to do that same check in GHA if we wanted to instead of the checklist that could quickly start to get ignored? Just a thought

Good point. We might be able to do so with GitHub actions instead. I'll take a quick look. Either way, that can be a follow-up to this PR for the time being.

Thanks @jjspace! Updated.

@ggetz One downside to doing the confirmations with checkboxes is that GH considers them tasks and will include the completion count in a handful of places around the site. Might still be handy but it does add a bit of distraction/confusion especially if there is an "actual" tasklist in a PR


Google Chrome - Checksum error

Checklist

[X] I have verified that this is the correct repository, and the package is maintained by the chocolatey-community user.
[X] I have verified that this is happening in the latest available version of the package.

Chocolatey Version
2.2.2
Chocolatey License
None
Package Version
Google Chrome 123.0.6312.58
Current Behaviour
When installing google chrome with either
choco install googlechrome -y
or
choco install googlechrome --version 123.0.6312.58 -y
You will encounter the error that the hashes do not match.
Error - hashes do not match.
Installation will fail and Chrome won't be installed.
Log:
PS C:\WINDOWS\system32> choco install googlechrome --version 123.0.6312.58 -y
Chocolatey v2.2.2
Installing the following packages:
googlechrome
By installing, you accept licenses for the packages.
Progress: Downloading googlechrome 123.0.6312.58... 100%

GoogleChrome v123.0.6312.58 [Approved]
GoogleChrome package files install completed. Performing other installation steps.
File appears to be downloaded already. Verifying with package checksum to determine if it needs to be redownloaded.
Error - hashes do not match. Actual value was 'E9F6EEFCD3D6A45408AB37546B8C25AFD34D5E368ACE6F26588467830967A33C'.
Downloading googlechrome 64 bit
  from 'https://dl.google.com/dl/chrome/install/googlechromestandaloneenterprise64.msi'
Progress: 100% - Completed download of C:\Users\admin.xxx\AppData\Local\Temp\chocolatey\googlechrome\123.0.6312.58\googlechromestandaloneenterprise64.msi (112.05 MB).
Download of googlechromestandaloneenterprise64.msi (112.05 MB) completed.
Error - hashes do not match. Actual value was 'E9F6EEFCD3D6A45408AB37546B8C25AFD34D5E368ACE6F26588467830967A33C'.
ERROR: Checksum for 'C:\Users\admin.xxx\AppData\Local\Temp\chocolatey\googlechrome\123.0.6312.58\googlechromestandaloneenterprise64.msi' did not meet '3091c7cae3d8ae940ed82ef0ba45680195a7f6e7c38195c37c8d8cb36e8ae969' for checksum type 'sha256'. Consider passing the actual checksums through with --checksum --checksum64 once you validate the checksums are appropriate. A less secure option is to pass --ignore-checksums if necessary.
The install of GoogleChrome was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\googlechrome\tools\chocolateyInstall.ps1'.
 See log for details.

Chocolatey installed 0/1 packages. 1 packages failed.
 See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).

Failures
 - GoogleChrome (exited -1) - Error while running 'C:\ProgramData\chocolatey\lib\googlechrome\tools\chocolateyInstall.ps1'.
 See log for details.

Expected Behaviour
To finish the installation, and have Chrome installed
Steps To Reproduce
open powershell
use either of the following commands:
choco install googlechrome -y
or
choco install googlechrome --version 123.0.6312.58 -y
Environment
- Operating System: Microsoft Windows NT 10.0.22635.0
- PowerShell Version: 5.1.22621.2419
- Shell:

Chocolatey Log
PS C:\WINDOWS\system32> choco install googlechrome --version 123.0.6312.58 -y
Chocolatey v2.2.2
Installing the following packages:
googlechrome
By installing, you accept licenses for the packages.
Progress: Downloading googlechrome 123.0.6312.58... 100%

GoogleChrome v123.0.6312.58 [Approved]
GoogleChrome package files install completed. Performing other installation steps.
File appears to be downloaded already. Verifying with package checksum to determine if it needs to be redownloaded.
Error - hashes do not match. Actual value was 'E9F6EEFCD3D6A45408AB37546B8C25AFD34D5E368ACE6F26588467830967A33C'.
Downloading googlechrome 64 bit
  from 'https://dl.google.com/dl/chrome/install/googlechromestandaloneenterprise64.msi'
Progress: 100% - Completed download of C:\Users\admin.xxx\AppData\Local\Temp\chocolatey\googlechrome\123.0.6312.58\googlechromestandaloneenterprise64.msi (112.05 MB).
Download of googlechromestandaloneenterprise64.msi (112.05 MB) completed.
Error - hashes do not match. Actual value was 'E9F6EEFCD3D6A45408AB37546B8C25AFD34D5E368ACE6F26588467830967A33C'.
ERROR: Checksum for 'C:\Users\admin.xxx\AppData\Local\Temp\chocolatey\googlechrome\123.0.6312.58\googlechromestandaloneenterprise64.msi' did not meet '3091c7cae3d8ae940ed82ef0ba45680195a7f6e7c38195c37c8d8cb36e8ae969' for checksum type 'sha256'. Consider passing the actual checksums through with --checksum --checksum64 once you validate the checksums are appropriate. A less secure option is to pass --ignore-checksums if necessary.
The install of GoogleChrome was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\googlechrome\tools\chocolateyInstall.ps1'.
 See log for details.

Chocolatey installed 0/1 packages. 1 packages failed.
 See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).

Failures
 - GoogleChrome (exited -1) - Error while running 'C:\ProgramData\chocolatey\lib\googlechrome\tools\chocolateyInstall.ps1'.
 See log for details.

Anything else?
No response

Can second I'm having this issue on a fresh Chocolatey install on a fresh Windows install

There are currently problems with the Chocolatey Community Repository that is being investigated, until that problem is resolved, a new version of Google Chrome won't be possible to be made available.
Please follow the status message for the community repository related to this: https://status.chocolatey.org/issues/2024-04-01-package-moderation-services-returning-false-test-failures/

This should now be available on the community website.
@memmam and @ENTXawp, can you confirm that this is no longer an issue?

Still getting the same error

@memmam can you please try again?

It worked!

Yep it works v


Refactor fetch endpoint

#16

Hi @Bartek532, thanks for your work! Unfortunately, you used the main branch as a starting point. I should've mentioned that there's a develop branch that is ahead of main by a few commits. Sorry for that!


https://events.google.com/io2015/manifest.json doesn't get parsed

It has some chrome_ extensions which should be fine.

This issue is already fixed in v0.1.3. However, there is another issue with that site. I created a new issue for that one.


Thanks!

Not an issue but wanted to say thanks for this work. It's fantastic. We met a year ago (perhaps you remember?) when you told me about this. I've been using it in various scenarios and was hoping to mention it at a "special" presentation next week in Europe. I've found it to work well with VC on Linux Mint.
Really fantastic work. Thanks

Glad you like it.  I have been told it works on Kali too


Bug in random number generator seed when restarting from checkpoint

I found a bug.

Commit _____ fixes this bug.


[SEVERE] Server crashes every few minutes

Description
Basically every few minutes, all the users from the server get the ''Timed out'' screen and it crashes with the LuckPerms log.
Reproduction steps

Have LuckPerms v5.1.26 along with PaperSpigot 1.8.8
Wait a few minutes
See error

Expected behaviour
Well, the server not to crash after a few minutes.
Environment details
PaperSpigot 1.8.8 + ViaVersion (Dev build)

Server type/version: ExampleSpigot running version 1.12.2 build ???
LuckPerms version: v5.1.26`

Crash error: https://pastebin.com/D9DqG1qE
Any other relevant details

You are quite a number of builds behind, see if it still happens with the latest one https://luckperms.net/download

Also, keep in mind that stack trace you pasted isn't necessarily an error. The crash log includes information from all threads running on the server, and since LuckPerms does most of its work asynchronously, you will probably see a lot of them. If anything, please provide the entire crash log and the whole server log as well (located in logs/latest.log) :)

Nothing there to suggest LP is the cause of a crash