Add option to save cache even if build failed

It still makes sense to save the cache if the build fails. Even if vcpkg itself fails, some dependencies might have been built successfully already, which can save significant time on the next try.

I would also very much like to see this feature, but I am not sure if it is possible to implement it purely in this action. There was an attempt to add a save-always option to the cache action, but that did not (reliably) work (see this issue) and the option will be deprecated and removed. Instead, as documented here, the way to go is to use cache/restore and cache/save separately, which allows to always run the save step. I have never tried this but to me, it seems that setup-vcpkg can therefore only do the restore part. The save step must be run by the user at an appropriate time later.

Implemented as part of 2d431e834f534281ce7f4ee61c23ccfd1769ccd9


Bad Request: 400

I cloned the project
Updated the client id and client Secret inline, rather than running the .sh file
mentioned the file, bucket id everything as said in the instructions, still I am getting 400 Error!!
Did I miss anything ???
{ statusCode: 400, statusMessage: 'Bad Request'

Can you show me how the variables look (just add ***** to your keys, I dont need to see them, but I want to see the file path, file name and bucket)
Also can you make sure your keys have access to use Model Derivative API


DCOS_OSS-1965: Change DC/OS favicon to Mesosphere DC/OS favicon

Change DC/OS favicon to Mesosphere DC/OS favicon to match updated brand.

Alfred retest this please

@orlandohohmeier it doesn't.  I can house it elsewhere.  Does having it here create some complication?


Add ELPP_DISABLE_CHECK_MACROS and ELPP_DISABLE_DEBUG_MACROS

They allow disabling definitions of CHECK and DEBUG
macros, respectively.

Now with a macro for those other macros, and default branch changed to develop (I think).


oneplus cleanup

@ZwX1616 can you review the camerad cleanup?

@deanlee there's probably more room for cleanup here if you're interested, I just did a quick pass


Incompatible with Next.js

Hi,
Though the README for @neoconfetti/react reads "Works seamlessly in NextJS/Remix/Gatsby/Redwood and other Server Side Rendering environments!"
Adding the Confetti import to a Server Side Rendered page provides the error:
<EMAIL_ADDRESS>(211:28) @ Confetti
useRef only works in Client Components. Add the "use client" directive at the top of the file to use it. Read more: https://nextjs.org/docs/messages/react-client-hook-in-server-component

In most cases it's possible to just add "use client", but in apps that need to also be defining page metadata it becomes impossible to use this library and set things like the page title/opengraph data.
For example,
import { Confetti } from '@neoconfetti/react';
import { Metadata } from "next";

const metadata: Metadata = {
  title: "Happy Page!",
}

function HappyPage() {
  return (

      <Confetti/>

  )

}

export default HappyPage;
export { metadata };

You're forced to choose between Confetti (client component) and metadata (server component) ☹
This is with<EMAIL_ADDRESS>and<EMAIL_ADDRESS>

If i put use client in the confetti component, will it work?

Hi,
Though the README for @neoconfetti/react reads "Works seamlessly in NextJS/Remix/Gatsby/Redwood and other Server Side Rendering environments!"
Adding the Confetti import to a Server Side Rendered page provides the error:
<EMAIL_ADDRESS>(211:28) @ Confetti
useRef only works in Client Components. Add the "use client" directive at the top of the file to use it. Read more: https://nextjs.org/docs/messages/react-client-hook-in-server-component

In most cases it's possible to just add "use client", but in apps that need to also be defining page metadata it becomes impossible to use this library and set things like the page title/opengraph data.
For example,
import { Confetti } from '@neoconfetti/react';
import { Metadata } from "next";

const metadata: Metadata = {
  title: "Happy Page!",
}

function HappyPage() {
  return (

      <Confetti/>

  )

}

export default HappyPage;
export { metadata };

You're forced to choose between Confetti (client component) and metadata (server component) ☹
This is with<EMAIL_ADDRESS>and<EMAIL_ADDRESS>
you gotta put the confetti component inside a client component and use it in the react server component.


Proposal: Site foundations

Description
This proposal outlays the general design of the application in terms of tech stack.
UI Framework: Chakra UI - An easy to use and powerful UI framework that allows for css-in-js
Helper functions: lodash - General functional helper tools that can help us do things like empty checks on objects, deep clones, etc
Date Helpers: date-fns - An advanced library to take the pain out of regular Date objects
Icon pack: react-icons - An icon pack recommended by Chakra which allows for many, many icons including font-awesome
Markdown Plugin: react-markdown - Processes .md files to allow us to create blog posts and render them all in a consistent way in the frontend. (For challenges)
Bundler: Vite - Not sure it's possible to use this bundler with NextJS but if so, Vite offers an amazing hot reload and development experience plus a no-hassle build for production.
Database: PostgresQL and GraphQL - Postgres is industry proven and easy to use, GraphQL provides a great interface for database queries.

Closing this issue for now as PR #3 has been merged.


added ability to change FG & BG to GIT_COLORIZE_DIRTY and added color…

Currently you can only change the background color of GIT_COLORIZE_DIRTY.  This pull request allows you to set both the foreground (FG) and background (BG) of GIT_COLORIZE_DIRTY.  I have set the (FG) default to "black" as the original "white" was too hard to read with the default (BG) of "yellow".  Also, the GIT_PROMPT_CLEAN and GIT_PROMPT_DIRTY didn't have any color on the check mark or the X.  I added green to the check mark and red to the X.

:+1:
Thanks for the time and work!


🐛 Bug Report: Inconsistent display of the list of entities

📜 Description
Hello,
There is an inconsistency in the sorting of the list of entities. When the title is different from the name in the yaml file of an entity, the sorting is done by the name but it is the title that is displayed in the table.

👍 Expected behavior
Either sort and display by name or sort and display by title.
👎 Actual Behavior with Screenshots

👟 Reproduction steps
click on the button of the sidebar displaying the list of published entities.
📃 Provide the context for the Bug.
No response
🖥 Your Environment
No response
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
None

Note also that this may be complicated in a future where we have pagination, and not all entities are in memory at the same time. But I've reviewed the PR now.

Closing as this was fixed by #16178


⚠ Fortnite has degraded performance

In 0d92fd5, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1796 ms

Resolved: Fortnite performance has improved in 545a287.


Gradle 7 support

Describe the bug
When running ./gradlew clean build with gradle 7 the build fails.

What went wrong:

A problem was found with the configuration of task ':copyContracts' (type 'ContractsCopyTask').
  - Type 'ContractsCopyTask.Dependency' method 'toStubConfiguration()' should not be annotated with: @Internal.

    Reason: Input/Output annotations are ignored if they are placed on something else than a getter.

    Possible solutions:
      1. Remove the annotations.
      2. Rename the method.

    Please refer to https://docs.gradle.org/7.0/userguide/validation_problems.html#ignored_annotations_on_method for more details about this problem.

With gradle 6.8.3 we had deprecation warnings already:
Type 'ContractsCopyTask.Dependency': non-property method 'toStubConfiguration()' should not be annotated with: @Internal. This behaviour has been deprecated and is scheduled to be removed in Gradle 7.0. See https://docs.gradle.org/6.8.3/userguide/more_about_tasks.html#sec:up_to_date_checks for more details.

Duplicate of https://github.com/spring-cloud/spring-cloud-contract/issues/1636

Ah thanks. Couldn't find it. Searched for open issues only 🤦


Installer Icon on Windows

Testing #33272
Windows
On my home PC I noticed that the icon on the right was very blocky.  I have a 4K monitor.

We are limited in what kind of image resource we can provide to InnoSetup.
/cc @joaomoreno

Yup, hdpi issue.

To keep the number of issues in our inbox on a manageable level, we're closing issues that have been on the backlog for a long time but haven't gained traction: We look at the number of votes the issue has received and the number of duplicates issues filed.
Thanks for your understanding. Happy coding!


(BKR-422) debian7 fails to reboot during smoketest

to fix current smoketest redness change how we connect to beaker boxes
do three separate connection attempts (with retries)

first with ip
then the virtual hostname (vmhostname)
then the name of the box provided by the user (hostname)

Only when all three fail do we fail out
decrease the Net::SSH timeout so that we can move through the various
attempts in a reasonable amount of time
add a sleep post windows reboot, getting reds here because windows
takes so long to come back up

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1248/
Test PASSed.

Green tests!

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1255/
Test FAILed.

Failed to reboot on windows.  I'll take another look.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1256/
Test PASSed.


Issues With Claiming, and Generating

[ ] This issue isn't duplicated - you can check if it is by using the search bar located at the top left hand corner and select "Issues" on the left.
[x] This issue includes appropriate markdown for sections - e.g. code blocks for crash dumps.
[x] This issue is understandable - feel free to use your native language to write issues if you are not comfortable with English.

When I generate a new plot world, it doesnt actually register as a plot world and you cannot claim there.  On old plot worlds, typing /p auto sends you into the ground or void. And typing /p claim gives the Unknown Error message.

Reproducing the issue

Generate a new plot world
Type /p auto, nothing works.

Client information
PocketMine-MP Version:
Plugin Version: API 3.0 branch
PHP version: 7.0.13 (default)

Optional information

The generation issue is known. Please give more information about the claiming issue

What kind of info about it will you need? I will be happy to give you what I can to help this get fixed.

When I do /p claim I get the following message:
You are not standing inside a plot
When I do /p auto I get the following message:
You are not in a plot world
Not sure if this matters but my worlds folder is empty.
-plugins/MyPlot/Worlds

that shouldn't matter, it should generate a new file if its empty..

@NML32 there are many issue that I am working on fixing, but I cannot at the moment due to my computer being broken. I will attempt to resolve all these issues as soon as I can.

I fixed generating! Was so simple! Just remove colors, mcpe just need biome id not color!

I plan on changing the way biomes are changed. The colors were the old method, but instead I will set the chunk biome's Id and resend the info to the client.

@TDMidkwhatisxd that has already been done though. There is another issue that has to do with PocketMine's new chunk system

I dont have problems! At all!

Did you change all FullChunk to Chunk ?

@Lazerplayz  I have on the API3 branch

@jasonwynn10 for your reference this one actually works quite well - https://github.com/jjplaying/MyPlot

but that only removes color, which was already replaced in this version

@jasonwynn10 yes, but it isn't forked off your version, it's forked off the original. Which means that your previous changes may have caused a problem...

maybe this will fix generation? 2b3069c


Round-robin localhost priority

I'm not sure if this feature is already possible or if would be possible a result of implementing #178, if so, feel free to close this.
For example, let's say we  have:
1.mydatabase.service <IP_ADDRESS>
2.mydatabase.service <IP_ADDRESS>
3.mydatabase.service <IP_ADDRESS>

So mydatabase.service will round-robin through each as expected. However, it would be nice if <IP_ADDRESS> was priortised at the top for requests coming from <IP_ADDRESS> as it would prevent unnecessary network traversals. Thoughts?
Edit: This has the benefit of using a localhost instance of a given service when available and falling back to a remote host when not. Note, this scheme can manually implemented for custom clients, however with 3rd party clients using connection pools (redis/rethinkdb) this would not be possible without going into the source and introducing "primary" and "secondary" hostnames.

Interesting feature. But I think this should not be done in the DNS. Why
can't you add those 10 addresses to the loopback interface on those hosts?
On 26 Jul 2015 08:20, "Jaime Pillora"<EMAIL_ADDRESS>wrote:

I'm not sure if this feature is already possible or if would be possible a
result of implementing #178
https://github.com/skynetservices/skydns/issues/178, if so, feel free
to close this.
For example, let's say we have:
1.mydatabase.service <IP_ADDRESS>
2.mydatabase.service <IP_ADDRESS>
3.mydatabase.service <IP_ADDRESS>
So mydatabase.service will round-robin through each as expected. However,
it would be nice if <IP_ADDRESS> was priortised at the top for requests
coming from <IP_ADDRESS> as it would prevent unnecessary network traversals.
Thoughts?
—
Reply to this email directly or view it on GitHub
https://github.com/skynetservices/skydns/issues/213.

That would help in the case where a VM died and all containers on a single machine die at once. However, if container A dies, container B would still think A is on localhost. Whereas, if A had its address in skydns then it would expire and B would correctly route to a remote host.


Remove duplicated CSS

Many of the CSS rules were duplicated for the range.css file; I assume that they got added due to some kind of copy/paste error or similar.
Also add newlines to the end of some files

nice catch, thanks for fixing this! it does look like just an error while copying / pasting


fix(ci): login to ecr to fetch contracts image

need to perform ecr_login before running script on docker image that's deployed on ECR
Checklist:
Remove the checklist to signal you've completed it. Enable auto-merge if the PR is ready to merge.

[ ] If the pull request requires a cryptography review (e.g. cryptographic algorithm implementations) I have added the 'crypto' tag.
[ ] I have reviewed my diff in github, line by line and removed unexpected formatting changes, testing logs, or commented-out code.
[ ] Every change is related to the PR description.
[ ] I have linked this pull request to relevant issues (if any exist).

Benchmark results
Metrics with a significant change:

note_history_trial_decrypting_time_in_ms (10): 353 (+56%)
note_trial_decrypting_time_in_ms (8): 43.7 (+80%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Values are compared against data from master at commit ebdeea3f and shown if the difference exceeds 1%.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
128 txs

l1_rollup_calldata_size_in_bytes
45,444
179,588
716,132

l1_rollup_calldata_gas
222,852
868,208
3,449,600

l1_rollup_execution_gas
841,939
3,595,316
22,204,969

l2_block_processing_time_in_ms
2,248 (+2%)
8,624
36,072 (+1%)

note_successful_decrypting_time_in_ms
335 (+6%)
943 (+2%)
3,453 (+3%)

note_trial_decrypting_time_in_ms
:warning: 43.7 (+80%)
69.7 (+28%)
203 (+2%)

l2_block_building_time_in_ms
20,765 (+1%)
82,851 (+2%)
331,826 (+2%)

l2_block_rollup_simulation_time_in_ms
17,151 (+1%)
68,627 (+2%)
274,506 (+2%)

l2_block_public_tx_process_time_in_ms
3,564 (+2%)
14,072 (+2%)
56,758 (+2%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
24,702 (+1%)
47,604

note_history_successful_decrypting_time_in_ms
2,175 (+2%)
4,169 (+1%)

note_history_trial_decrypting_time_in_ms
162 (-1%)
:warning: 353 (+56%)

node_database_size_in_bytes
2,796,676
5,026,564

pxe_database_size_in_bytes
29,748
59,307

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
201 (-2%)
43,109
20,441

private-kernel-ordering
115 (-4%)
25,833
9,689

base-rollup
2,985 (-2%)
664,108
873

root-rollup
90.6 (+2%)
4,072
1,097

private-kernel-inner
263
64,516
20,441

public-kernel-private-input
173
25,203
20,441

public-kernel-non-first-iteration
170 (-1%)
25,245
20,441

merge-rollup
10.9 (+1%)
2,592
873

Miscellaneous
Transaction sizes based on how many contracts are deployed in the tx.

Metric
0 deployed contracts
1 deployed contracts

tx_size_in_bytes
10,323
25,938


All data should expire within 24 hours

No reason to store players, lobbies, or games forever in redis. Add a TTL of 24 hours to everything.

Resolved by https://github.com/deesejohn/distributed-codenames/pull/79 https://github.com/deesejohn/distributed-codenames/pull/80 https://github.com/deesejohn/distributed-codenames/pull/81


x/pkgsite: replace all internal Googler links

I see links like TODO(b/139530312), which I assume is an issue link I can't access or at least some text that doesn't make any sense to me.
If we're going to use this issue tracker alone in the future, like other x repos, we should replace all of those with links to issues here. Some TODOs are this way already, such as TODO(golang/go#38513).
Current counts:
$ git log -1 --oneline
7f80893 (HEAD -> master, origin/master, origin/HEAD) internal/database: fix bug with error handling in transact
$ git grep 'TODO(b/' | wc -l
26
$ git grep 'TODO(.*#' | wc -l
8

/cc @julieqiu @jba

Thanks for catching! We'll work on fixing these.

There are a few more instances that can be found without the "TODO" prefix:
$ git log -1 --oneline --no-decorate
08e8e66 internal/worker: add /poll and /enqueue endpoints.
$ git grep -E 'b/[0-9]{4}' | wc -l
      12

Only 7 more to go after CL 240187.


Add secure migration for updating CAC for felipe-lee

Summary
Uploading my updated CAC.
Followed instructions on https://dp3.atlassian.net/wiki/spaces/MT/pages/1751089156/How+to+Create+CAC+Access+for+using+Prime+API+and+uploading+Electronic+Orders
I also made a few updates to the instructions, so if you have time, it'd be good for some other eyes on it. Otherwise, we can just get eyes on the changes next time someone uploads a new/updated CAC.
While working on this, I found that some scripts weren't working properly so I opened a separate PR for that in #9683.
Checking Changes

💻
Checking local DB

Run migrations and load data.
make db_dev_run

make db_dev_migrate

Enter psql-dev
psql-dev

Run query to retrieve new client cert:
select sha256_digest from client_certs where subject ILIKE '%felipe-lee%';

Verify the value matches the new value in the migration.

Checking secure migrations

Download secure migrations. The output will tell you where the files can be found.
download-secure-migration<PHONE_NUMBER>5107_felipe_cac.up.sql

Check secure migrations:

Ensure the secure migration files for demo, exp, and stg, and loadtest updates my existing client cert with the new info.
Ensure the secure migration file for prd is just a stub and does not insert a record.

Delete downloaded migrations from tmp folder

Verification Steps for Author
These are to be checked by the author.

[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

Verification Steps for Reviewers
These are to be checked by a reviewer.
Database
Any new migrations/schema changes:

[ ] Follows our guidelines for Zero-Downtime Deploys
[ ] Have been communicated to #g-database
[ ] Secure migrations have been tested following the instructions in our docs

Warnings

:warning:
Please add the JIRA issue key to the PR title (e.g. MB-123)

  Generated by :no_entry_sign: dangerJS against 7d9740547b161d1d8fd9b84601549228e437f242


Defaults for optional parameters

What is the story for defaulting of optionals?
Maybe some constructors like First can be employed for that?

Are you referring to the optional-args library or something else?

optparse-generic provides a way to encode optional arguments by including a field of type Maybe a into the record.
What I was referring to is a way to provide a default for this optional value -- in the same data structure.
Of course the defaulting can be done manually, later, e.g. via fromMaybe -- however in that case optparse-generic would be left without means to document the default value in the help message.

I think the cleanest solution in this case would be to default them manually later.  I would like to avoid type-level machinery to do something that is reasonably easy to do at the value level.
Really the best solution would be for Haskell to provide support for records with defaults and then to expose that information via the same generics API.

So is it not possible for optparse-generic to automatically fill in and display defaults?

It probably is possible in theory but it would require some type-level hacking to get it to derive that information from a datatype definition,

I haven't looked at your way of doing this carefully enough but in the version I've been toying with, it's possible to specify defaults as long as you specify them all.  You just do that by giving a specific value of the data type you used to generate the parser.  The given value then fills in all the options but any you specify on the command-line override the ones you specified in the hard-coded value. That should be possible the way you are doing things as well, I think. It's not a general purpose solution but might work fine for some people's needs.

So I looked more closely into the idea of specifying the defaults for all fields.  The issue I ran into was how to specify the defaults for fields that were lists.  For example, suppose that you have a field like:
data Example = Example { foo :: [Int] }

Normally that would translate to a user interface where the user would supply multiple elements of the list by repeated use of the flag --foo:
$ ./example --foo 1 --foo 2

But suppose that the user wanted to specify a default value for the foo field of the Example type like [3,4].  How would we translate that default back down to optparse-applicative?
Right now the parser for repeated --foo flags is created by first defining a parser for a single --foo flag and then wrapping that in many to permit repetition.  However, that means that we can only define a default value for the parser for a single --foo value (i.e. just a single Int) and not a default value for the field after we've enabled repetition using many.
Also, it's not clear what a default value would mean for a repeated field.  For example, suppose that we did figure out how to specify a default value of [3, 4] for a repeated Int field.  If we supply that default when there are no --foo flags on the command line then the user has no way to override the default with the empty list.

You could use the same trick as for help messages with Default taking the role of KnownSymbol. Make a newtype DefaultValue a = DefaultValue { getDefaultValue :: a }. Propagate the default through the class methods using an extra Maybe a input and a maybe mempty Options.value modifier. Then define instances for
instance (ParseField a, Default (DefaultValue a)) => ParseField (DefaultValue a) where
    parseField _ h m = DefaultValue <$> parseField (getDefaultValue def) h m
instance (ParseFields a, Default (DefaultValue a)) => ParseFields (DefaultValue a)
instance (ParseRecord a, Default (DefaultValue a)) => ParseRecrod (DefaultValue a)

That still doesn't solve the issue of how to interpret a default value for a field that is a list

Arguably, lists (except for strings) should not be able to have defaults which only really make sense for a (missing) single entry field. You should give them and Any, Sum, etc a default of mempty so that trying to define a default gives an overlapping instance type error. A bigger problem is that you can't (without some ugly/confusing hacks) do different defaults for the same type found in a given record which is a very common use case. This would all be easier if we had dependent types ^_^

What I would find very convenient is the ability to specify defaults using an external file (ala configurator). I actually need something a bit more complex as I have to read defaults from different file according to user input. I currently handle this with a make file but it seems a bit overkilled. So for instance make foo ZONE=test would read default configuration from a file called ".env-test" ...
I don't see how to do this in an "extra" library on top of optparse-generic and configurator because ideally the parser should check that every field is present (even if only some of them are provided by the command line and the others from the file).

As I understand it, a full configuration system with configuration files or environment variables is outside of the scope of optparse-generic which is intended only for simple command line parsing. I would do something like this to resolve a configuration between the command line and a configuration file:

example.hs

{-# LANGUAGE DeriveGeneric #-}
{-# LANGUAGE OverloadedStrings #-}
{-# LANGUAGE RecordWildCards #-}

module Main where

import Data.Aeson
import Data.Aeson.Types
import Data.Foldable
import Data.Maybe
import Data.Yaml
import GHC.Generics
import Options.Generic

data PartialCommand = PartialCommand
  { foo :: Maybe Int
  , bar :: Maybe Double
  } deriving (Generic)
instance ParseRecord PartialCommand

data Command = Command
  { cfoo :: Int
  , cbar :: Double
  } deriving (Generic,Show)
instance FromJSON Command where
  parseJSON = genericParseJSON defaultOptions{fieldLabelModifier = tail}

resolveCommand :: Command -> PartialCommand -> Command
resolveCommand Command{..} PartialCommand{..} =
  Command (fromMaybe cfoo foo) (fromMaybe cbar bar)

main = do
  defMaybe <- decodeFile "default.yaml"
  for_ defMaybe $ \def -> do
    command <- resolveCommand def <$> getRecord "command line parser"
    print (command :: Command)

default.yaml

foo: 0
bar: 0

> stack runghc example.hs -- --foo 2
Command {cfoo = 2, cbar = 0.0}

@echatav Thanks. Exactly what I was searching for. Do you know if there is a way to merge the two records in resolveCommand in an automate way (in case there are say more than 10 fields) ?
I do see it is orthogonal concern. Sorry for the distraction.

If you make the record fields Monoids then you can derive a Monoid instance for the entire record using the generic-deriving package: https://hackage.haskell.org/package/generic-deriving-1.10.4/docs/Generics-Deriving-Monoid.html

@PierreR I can't think of a nice way to automate that boilerplate :-/

There is actually a very nice way: A combination of LambdaCase and ViewPatterns and Data.Coerce:
data Args
   = Args { projectdir :: Maybe FilePath O.<?>"directory that the command is executed in"
          , watch      :: FilePath       O.<?> "file/directory to be watched"
          , command    :: Text           O.<?> "command to build executable"
          , exe        :: FilePath       O.<?> "executable to run after rebuild" }
   deriving (Generic)
instance O.ParseRecord Args

main :: IO ()
main = do
  O.getRecord "rebuild a long-running program on source change" >>= \case
    Args { projectdir = fromMaybe "." . O.unHelpful -> pd
         , watch      = coerce -> w
         , command    = O.Helpful cmd
         , exe        = O.Helpful e }
      -> watcher cmd pd w e

You can decide whether you want to do coerce or explicitly use Helpful and unHelpful. Maybe this should be a part of the tutorial?

That's a nice idea!  Would you like to contribute this to the tutorial?  If not, I can write this up

I’m a little full the next days, but I can write it into my todo list once I find the time.

Could use [Symbol] for default values to simply be the default command-line arguments, verbatim. The display of default values in help can just be unwords . (reifystuff :: Proxy [Symbol] -> Text), i.e., exactly as a user would use it.

Apparently there’s now a bit more type-trickery possible with a type-family called :::. From the documentation:
data Example w = Example
    { foo :: w ::: Int    <?> "Documentation for the foo flag"
    , bar :: w ::: Double <?> "Documentation for the bar flag"
    } deriving (Generic)

instance ParseRecord (Example Wrapped)
deriving instance Show (Example Unwrapped)

Depends on personal taste what to use I guess.

@mikeplus64: That's pretty clever.  I like that idea.  I probably don't have time to implement it myself but I'd accept a pull request to add this

note: I understand the "list" objection but also it is worth noticing that there is a default value combinator directly in optparse-applicative: https://hackage.haskell.org/package/optparse-applicative-<IP_ADDRESS>/docs/Options-Applicative.html#v:value
So it seems to me that it is unfortunate that optparse-generic has a portion of the optparse-applicative featureset it just can't provide an interface to here...

Just wanted to say that I think this is an important issue. This library is so much more convenient than directly using optparse-applicative. I always try to use optparse-generic for new applications but this issue usually blocks me. shrug

Alright, if somebody submits a pull request implementing this functionality then I'll accept it

I've trying to import the type operator <!> , but ghci always complains saying:
Module ‘Options.Generic’ does not export ‘type (<!>)’
    |
202 | import           Options.Generic                  (type (<!>))

I imported the module using:
import           Options.Generic                  (type (<!>))

What might I be doing wrong?


arbitrary metrics

What do you think about separating out the completeness and coverage columns and instead having it be metric and value. Then you should store arbitrary metrics about a region in the database, not just completeness and coverage?

That's worth thinking about for sure :smiley:
Just so we are on the same page: are you thinking this would add another table to the schema? That would then be linked to for example interval_data?

I'm a bad person to be thinking about database design but I was thinking instead of say a coverage and completeness column it would instead be like a plyr melted-style statistic and value. Then you could jam whatever statistics you wanted to put in there, so like "coverage", 50 "completeness", 0.5  "cv", 1, etc, without having the extra rigamarole of adding an extra column for every new statistic you wanted to precompute and store.

I understand now! (this is just for my own reference :sweat_smile: )
I will just double the rows in the interval_data (or whatever I name it) and put on each row the "statistic", "value", "sample", and "parent_id". That seems like a very nice and future proof idea - thanks Rory!
I'll add it to the next major release


Replace all usages of texture_descritor.size.* with the helper methods

Objective
A follow-up PR for https://github.com/bevyengine/bevy/pull/10221
Changelog
Replaced usages of texture_descriptor.size with the helper methods of Image through the entire engine codebase

Could you mark the functions as inline?


fix nip98 authorization and actually sign the header

This will fix the problem with upload to nostr.build not being authenticated as it should.

I don't know why, but this causes nostr.build to return a 500 error. I merged it, but I've reverted it for now.


Problems with deploying of repo

Hello, I wanted to test the application. Unfortunately, I can't get both "HL2DepthPlayground" and "SurfaceInteraction" to work.
I have little experience with working with repos, so it may well be that this is the problem.
I would like to explain briefly below what problems I am encountering and what I have already tried.
HL2DepthPlayground:
In Unity the variables Normal Line Renderer and Point Cloud Viszualizer are not assigned under the GameObject PointCloud and at the object SensorTest I get a NullReferenceException.
SurfaceInteraction:
Problems:

@deploy I get the following message

The following GlobalManagers were stripped from the build (Either because they're not used or not supported on this platform):
  ClusterInputManager
  UnityConnectSettings

After the first scene was loaded i get the following exception:
Exception thrown at 0x00007FFBD94C9F5C (KernelBase.dll) in SurfaceInteraction.exe: 0x40080202: WinRT transform error (parameters: 0x0000000080000B, 0x0000000080070490, 0x000000000014, 0x00000058136FCF80).
and the output window of Visual Studio says Stopping research mode afterwards.
After that I get several exceptions and the following error:
(Filename: currently not available on il2cpp Line: -1)

Solution:
Since the project is based on petergu684's info, I checked the steps and added the following to the appmanifest:
mlns:rescap="http://schemas.microsoft.com/appx/manifest/foundation/windows10/restrictedcapabilities"
IgnorableNamespaces="... rescap">
<rescap:Capability Name="perceptionSensorsExperimental" />
If you could assist me in solving, that would be great.
If there are more information need, do not hesitate to contact me.

Hello @Kilsym ,
The SurfaceInteraction project is actually a work in progress, not yet intended for others to use. I hope to get it working soon.
The HL2DepthPlayground project is a bit outdated, but it did work for others. I'll check and see what's wrong.

Thank you very much for the answer. Okay then I will stick with the HL2DepthPlayground and keep experimenting. If there is something I can support you with, I am happy to help.


Integrate Ceph into Mariner

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

[x] The toolchain has been rebuilt successfully (or no changes were made to it)
[x] The toolchain/worker package manifests are up-to-date
[x] Any updated packages successfully build (or no packages were changed)
[x] All package sources are available
[x] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/tools/cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json)
[x] All source files have up-to-date hashes in the *.signatures.json files
[x] sudo make go-tidy-all and sudo make go-test-coverage pass
[x] Documentation has been updated to match any changes to the build system
[x] Ready to merge

Summary

Add Ceph to Mariner
Change Log

Add package set required for Ceph support on Mariner
Adds packages: CUnit, byacc, ceph, docbook5-schemas, leveldb, libstoragemgmt, lsb-release, mailcap, oath-toolkit, python-cachetools, python-cherrypy, python-execnet, python-google-auth, python-jwt,, python-kubernetes, python-logutils, python-nocasedict, python-pecan, python-pywbem, python-remoto, python-repoze-lru, python-routes, python-rsa, python-sphinxcontrib-websupport, python-yamlloader, rdma-core, sgml-common, xmlstarlet, yasm
Changes packages: Cython, bison, libnl3, python-docutils, python-lxml, python-sphinx

Does this affect the toolchain?

YES
Test Methodology

Local build of toolchain and packages

Review was done in the ADO Mariner repository prior to public release- relevant PRs for internal Microsoft reviewers are 3265, 3326, and 3359.

A note for anyone coming across this PR in the future- spec files intentionally remained unchanged from the version previously committed to the ADO repository, even when they go against our newer spec formatting guidelines.


Site Update

The text at the top "Iconoir is now integrated in Framer" should ideally contain a link to the Framer project like it does in the README of this project since this is the top most element of the page with special emphasis.

Done


option to disable partial crash detection

Just as the title say the partial crash detection is really bad written and it cause often problem  with random unnecessary server restart

I believe you mean your server is badly written

This is not a txAdmin issue, this is an issue with your server. Don't go blaming txAdmin for telling you something wrong is happening.

Didn't post your txAdmin version.
Didn't post a screenshot of the diagnostics page.
Didn't post a good description of what is happening.
Didn't post a screenshot of the terminal with the crash message.
Didn't post a screenshot of the txAdmin log.
Okay buddy retard, sure you know better than a system used by thousands and battle-tested for over a year that has 3 REDUNDANT system that checks your server literally 144 THOUSAND times a day.

Anyway i am quite sure that in older version that option was there, and talking about bad written server just tell me why a "well" written server need a "crash detection".
I don't know exactly what cause the problem, we got plenty of ddos attacks recently all througths txadmin port and i don't kwno how they managed to prevent the HB, that cause and unwanted restart.
Removed txadmin and no more random restart.
I told you all i have to say, do as you want if i could i will try to recover more informations\logs etc as soon as possible
this is the image sent me from server "helpers", unfortunately i wasn't connected when this happened

man i have other things to do that review code of a webpanel that fivem just thought to built in their system.
Well, u had the time to create a PR in a Open Source platform literally saying "Its bad written like i say in the title"
Anyway i am quite sure that in older version that option was there, and talking about bad written server just tell me why a "well" written server need a "crash detection".
It wasn't, and the crash detection is there because txAdmin isnt only focused in well developed servers, its for everyone, plus if your server gets attacked while ur asleep txadmin brings it back
Removed txadmin and no more random restart.
Well ofc, txadmin is handling the restart, not FXServer, txadmin is the MONITOR like the resource name says
I told you all i have to say
Without a fundament yes


[RDKDEV-262] DeviceIdentification: syncup from metro version

Module name corrected
Generic implementation added for Linux and Broadcom
RPI: device id fetching support added
Interface aligned for Amlogic, RealTek, RPI and MFR
Cleanup of Deactivation sequence
cmake: cleanup and depedency added from cmake inside DeviceIdentification/cmake

Copyright scan failure
Commit: 4772de423222af8a55c420eaa1d2e2ac00e8d8fc
Report detail: https://gist.github.com/f27cc06b28351c67a5e69eb24d734216

Copyright scan failure
Commit: 4e7bd5db5a6dbd7e36902dd519691b8aaf7c2ea8
Report detail: https://gist.github.com/bad34a6b2f64a895f90acd4ff3128c05

Hi Haseena: This repo is assigned to RDK and needs RDK Apache headers, not Metrological - Martin

Hi Haseena: This repo is assigned to RDK and needs RDK Apache headers, not Metrological - Martin

Copyright updated

Many thanks Haseena!

I believe this breaks a unit test

These changes will work only with the thunder changes add with the hash 331ee30b1eaf82a7e8944ee00b8cb1d1d0aca682. So @npoltorapavlo, could you please update unit test case to use the Thunder corresponding to this hash from R2 branch ?

As your change breaks the tests, can you fix the tests. Thanks

As your change breaks the tests, can you fix the tests. Thanks

@npoltorapavlo Could you please help me to find the location of test ?
From the details it showing error:

/home/runner/work/rdkservices/rdkservices/rdkservices/DeviceIdentification/DeviceIdentification.cpp:146:51: error: ‘struct WPEFramework::PluginHost::ISubSystem::IIdentifier’ has no member named ‘FirmwareVersion’
40
146 |         deviceInfo.Firmwareversion = _identifier->FirmwareVersion();
41
|                                                   ^~~~~~~~~~~~~~~
42
/home/runner/work/rdkservices/rdkservices/rdkservices/DeviceIdentification/DeviceIdentification.cpp:147:43: error: ‘struct WPEFramework::PluginHost::ISubSystem::IIdentifier’ has no member named ‘Chipset’
43
147 |         deviceInfo.Chipset = _identifier->Chipset();
44
|                                           ^~~~~~~
45
make[2]: *** [DeviceIdentification/CMakeFiles/WPEFrameworkDeviceIdentification.dir/build.make:66: DeviceIdentification/CMakeFiles/WPEFrameworkDeviceIdentification.dir/DeviceIdentification.cpp.o] Error 1
46
make[1]: *** [CMakeFiles/Makefile2:435: DeviceIdentification/CMakeFiles/WPEFrameworkDeviceIdentification.dir/all] Error 2
47
make: *** [Makefile:133: all] Error 2
But that is related to the usage of wrong thunder version

@HaseenaSainul @npoltorapavlo - Let's get the thunder R2 version merged to sprint first and then we can update unit tests with the new version. Will work with Karuna to get R2 updated.

It builds now but fails in runtime. DeviceIdentification::Initialize calls IShell::Register which needs COMLink() to be valid. I.e. need to mock COMLink().

@npoltorapavlo, @anand-ky, please wait to get @MFransen69 approval before doing the merge.

Can one of the admins verify this patch?


touchesCancelled Method does not override any method from its superclass

I'm using swift 2.3 branch on Xcode 7 and this error is there for touchesCancelled
ActiveLabel.swift:416: Method does not override any method from its superclass

This should be fixed with the latest changes on swift-2.3. Please check if you have the latest ones.

I got that with cocoapods pod 'ActiveLabel', :git => 'https://github.com/optonaut/ActiveLabel.swift.git', :branch => 'swift-2.3' So it should be the latest

I am not receiving this error when compiling swift-2.3
Could you please do a pod update? Seems like your CocoaPods master repo is not in sync with origin


[Feature Request]: Add traffic Flow Prediction using LSTM

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
Build a model to predict traffic flow using LSTM (Long Short-Term Memory) networks. Utilizing historical traffic data, weather conditions, and event schedules.
Use Case
Time series analysis, sequence modeling, and visualization of predictions.
Benefits
No response
Priority
High
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC contributor
[X] I want to work on this issue
[X] I'm willing to provide further clarification or assistance if needed.

@sanjay-kv
Can you please assign me this issue

@sanjay-kv
Kindly assign me this issue

this is only dealing with stackoverdflow

Ohh okay @sanjay-kv


[SPARK-10304][SQL] Following up checking valid dir structure for partition discovery

This patch follows up #8840.

Merged build triggered.

Merged build started.

Test build #45002 has started for PR 9459 at commit 91ade3f.

Test build #45002 has finished for PR 9459 at commit 91ade3f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45002/
Test PASSed.

Merged build finished. Test PASSed.

Thanks! LGTM. Merging to master.


Trash YUL catalog links on HMOs

example rec:
https://lux.collections.yale.edu/view/object/f205a441-5895-4328-8ad8-655f56f2a7ce
one of those 150 or so links is the actual HMO, but we can't programmatically tell which. unit-data ticket to follow to ask YUL to not link Work bib records to LUX HMO records.
in the meantime, YUL mapper fix to trash subject_of if it's access_point starts "https://search.library.yale.edu/catalog/"
(ticket still being formed, see Teams convo)

Problem to be solved by YUL.


RandomLoadBalance 方法 权重定位性能优化

我阅读Dubbo RandomLoadBalance 源码时发现定位Invoker 使用的算法是遍历，如下
int[] weights = new int[length];
      // The sum of weights
      int totalWeight = 0;
      for (int i = 0; i < length; i++) {
          int weight = getWeight(invokers.get(i), invocation);
          // Sum
          totalWeight += weight;
          // save for later use
          weights[i] = totalWeight;
          if (sameWeight && totalWeight != weight * (i + 1)) {
              sameWeight = false;
          }
      }
      if (totalWeight > 0 && !sameWeight) {
          // If (not every invoker has the same weight & at least one invoker's weight>0), select randomly based on totalWeight.
          int offset = ThreadLocalRandom.current().nextInt(totalWeight);
          // Return a invoker based on the random value.
          for (int i = 0; i < length; i++) {
              if (offset < weights[i]) {
                  return invokers.get(i);
              }
          }
      }

使用weights数组 最后在遍历 时间复杂度为O(N) ，如果服务端的服务特别大的话性能不太好，所以我想可以优化成O(logN)的算法

Please submit a PR if you have any ideas?

Wow ~ Looking forward for O(logN).

If this task is currently unoccupied, I would like to give it a try. I think it can use binary search. @AlbumenJ

We can follow up in this issue if anyone have some ideas.


Update PatternFly version and Red Hat branding

Motivation
Update PatternFly dependencies to use the latest versions. Includes the breaking change from 1.x to 2.x, which is the driver for this large PR.
What
Update PatternFly Core to 2.6.11 and PatternFly React-Core to 3.16.10.
Why
Implement and test the breaking changes introduced with PatternFly v2.x.
How
Update package.json file, run app locally and verify that UI is functional. Any broken aspects were fixed.
Verification Steps

Pull PR locally
Install latest updates (yarn install) and rebuild the app (yarn build)
Run the app and go through a Walkthrough
View Provisioning screen to see the new background w/watermark
Open the About Modal to see the new background w/watermark
Finish a Walkthrough to see the Congratulations screen with new background w/watermark and colors.

Checklist:

[X] Code has been tested locally by PR requester
[ ] Changes have been successfully verified by another team member

Progress

[x] Finished task

Additional Notes

Work based off of the following designs: https://marvelapp.com/5ie30d3/screen/57132557


[FEATURE REQUEST] Decoder Warning / Intel Encoder with Filters

I encode mostly with the Intel HW-Encoder. For performance reasons I set "QVSEncC Intel Hardware" as default Decoder. For most of my sources this is ok.
But when I need to add a filter (beside Crop or Resize), for example a Deinterlace-Filter, the encoding works properly, only the filters are not used because I forgot to select "AviSynth/VapourSynth" as Decoder in Intel-Encoding-Settings.
That happened many times to me and I'm lucky if I find it out and can reencode again correctly before I delete the sources!
So it would be great to get a warning if I use Filters (beside Crop or Resize) in combination with other decoders than "AviSynth/VapourSynth". Or perhaps StaxRip could switch the decoder automatically to "AviSynth/VapourSynth" if I enable such a filter.
Thank you.

I have doubts but think about it. I'm more sure that I can improve thumbnail support.


Find-PSResource is slow to respond to CTRL+C

Can't CTRL+C out of Find-PSResource without waiting ~20 seconds. The only PS repository is PSGallery.

This will be resolved with the release of Preview 11.


Update build for numpy 2 with new methods

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

@conda-forge/help-c-cpp
This seems to be building for numerous numpy versions -- rather than for 2.0 -- how to I get the "new" 2.0 builds?

You need to add the numpy 2.0 migration file to .ci_support/migrations and then rerender.

@conda-forge-admin, please rerender

Finally! thanks @xhochy !

Thanks! still confused about where you need:
# [build_platform != target_platform]
I would have thought that that's what putting it in host meant, but what do I know?


Login problem when checkbox login-form[rememberMe] is not checked

I've installed yii2 and login module using composer and the following issue occured:

After login attempt without setting "remember me" checkbox, there is a redirect to the index page.
E-mail approve link does't login too. But in this case, after transition to the site, on the first page there is a user name on the top of the page firstly, but actually user does not logged in and after refresh page looks as for guest.
If to set checkbox "rememberMe", logged in without problems

You probably do have problems with sessions, you should find them out and fix them yourself.


error[E0635]: unknown feature stdsimd

unknown feature stdsimd : Got below after updating rust to new version rustc 1.78.0-nightly (f067fd608 2024-02-05)
error[E0635]: unknown feature stdsimd
--> C:\SYSTEM\RUST\CARGO\registry\src\index.crates.io-6f17d22bba15001f\ahash-0.7.7\src/lib.rs:33:42
|
33 | #![cfg_attr(feature = "stdsimd", feature(stdsimd))]
|                                          ^^^^^^^
For more information about this error, try rustc --explain E0635.
error: could not compile ahash (lib) due to 1 previous error

Facing similar issue.

Same here on version 0.7.7, it's broken my crate's documentation build on docs.rs but works fine for me locally on Linux and MacOS, not sure why it's only broken in the docs.rs sandbox environment.

This is caused by https://github.com/rust-lang/rust/pull/117372. This problem in ahash was already fixed in https://github.com/tkaitchuck/aHash/pull/183, but a new release hasn't been released yet. CC @tkaitchuck

Fundamentally this is caused by logic in build.rs that auto-enables a nightly feature when it detects that it is built with a nightly rustc. Such logic is fragile and prone to errors as nightly features evolve before stabilization.
Crates should never automatically enable nightly features, this should generally be opt-in. If they try to do it automatically they need to be very careful and account for the fact that nightly features are not stable, and might look very different in future nightly versions.

Same for me

If you’re on 0.8 branch → update to 0.8.7.  See #188.
However, I’m also picking up dependency on 0.7.7 through chain of older dependencies (borsh 0.9 → hashbrown 0.11 → ahash 0.7) which I can’t easily get rid of on my side.  It’d be fantastic if we could get backport to 0.7 branch as well.  I’ve commented that in #188.

Seems like this is breaking trunk and leptos
I was just trying to get into learning leptos, so installing all of the right versions according to the docs and trying to install trunk and cargo-leptos both runs into this bug.
Console output:
> cargo install trunk
error[E0635]: unknown feature `stdsimd`
  --> /Users/medwards/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ahash-0.7.7/src/lib.rs:33:42
   |
33 | #![cfg_attr(feature = "stdsimd", feature(stdsimd))]
   |                                          ^^^^^^^

For more information about this error, try `rustc --explain E0635`.
error: could not compile `ahash` (lib) due to 1 previous error
warning: build failed, waiting for other jobs to finish...
error: failed to compile `trunk v0.18.7`, intermediate artifacts can be found at `/var/folders/9f/w50rg2wj193fh6jv5rt0lk1r0000gn/T/cargo-installif2CRL`.
To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path.```

Not trying to brigade the comments, I'd work on a fix but you probably don't want a Rust noop running around your repo.

It seems that a lot of stuff depends on ahash < 0.8. It would be indeed useful if it was possible to put out a backported patch release for 0.7.

Can confirm that cargo-leptos and trunk both depend on v0.7.7 and don't work now.

@tkaitchuck Would it be possible to remove the build.rs check in the 0.7 series? 0.8 fixes this but:

Not everyone has upgraded to it
This affects MSRV

Fundamentally this is caused by logic in build.rs that auto-enables a nightly feature when it detects that it is built with a nightly rustc. Such logic is fragile and prone to errors as nightly features evolve before stabilization.

I agree with Ralf here: crates shouldn't do this. It makes life harder for crates attempting to support a range of versions: they're either broken on the new version due to the missing feature, or broken on the old version due to an unstable feature.

Opened https://github.com/tkaitchuck/aHash/pull/202
Looks like this feature was already disabled in https://github.com/tkaitchuck/aHash/pull/183

Same as https://github.com/tkaitchuck/aHash/pull/201?

Almost. https://github.com/tkaitchuck/aHash/pull/202 gets us out of the detection business entirely, which is what was already landed in #183

For those in this situation and if your workflow permits, pinning the Rust nightly version to an earlier date might serve as a temporary measure to get unblocked, particularly if you're facing the unknown feature 'stdsimd' error with ahash-0.7.7:
# install specific nightly version (i.e., `2024-02-01`)
rustup toolchain install nightly-2024-02-01

# use this nightly version for your commands
cargo +nightly-2024-02-01 build

This is not, of course, a solution to the issue, but rather a workaround that may help in the interim until a more permanent fix is available.

Why not juse use crates.io version of the thing or something like that? This is a huge pain, all of the dependencies are littered with this and it is impossible to compile on an M1 with stable toolchain

Fixed via #201, and released as 0.7.8

I am still experiencing the issue. I installed the latest stable

I am still experiencing the issue. I installed the latest stable

Working for me with 0.8.8. Don't forget to cargo clean

Don't forget that you have to cargo update ahash to actually get the newest version (either 0.7.8 or 0.8.7+).

Thank you everyone for the quick resolution!
For folks who have both versions in their deps, here is a quick fix that doesn't require clean:
cargo update<EMAIL_ADDRESS>cargo update<EMAIL_ADDRESS>

The issue fixed when version 0.8.7
I have fixed with workspace root Cargo.toml
`[workspace.dependencies]
ahash = "0.8.7"
[workspace.metadata.resolver]
version = "2"`
program Cargo.toml
ahash = { workspace = true }


Fix favicon

Fix favicon with status color (Issue 15). Favicon replaced from data url to png due problems on firefox (canvas too slow - cutting off from data url) and IE (data url). Function createDataUrls is left for testing purpose.

@Tonyko hey, could you squash this into a single commit? :)

Squashed and removed.

thanks for this :)


Why isn't Guid linked to its doc page?

Why isn't Guid linked to its doc page?

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

ID: 475a9bf2-9772-540b-0ccf-dbc2408c85c6
Version Independent ID: a2cc6a86-505b-0a9a-f1f8-1afad2dc5eb8
Content: BluetoothLEAdvertisement.ServiceUuids Property (Windows.Devices.Bluetooth.Advertisement) - UWP app developer
Content Source: https://cpubwin.visualstudio.com/DefaultCollection/windows-uwp/_git/winrt-api-build?path=%2fwinrt-api-build%2fwindows.devices.bluetooth.advertisement.bluetoothleadvertisement.yml&version=GBlive&_a=contents
Product: windows
Git Login: wdg-dev-content
Microsoft Alias: wdg-dev-content

Hi, @cctile. Thanks for filing this issue, and my apologies for the delay in responding.
You're right, the content definitely benefits from a link to GUID. I'll go ahead and add the link.
Thanks!
Steve


Specify Certificate Duration

Hello,
I read through the docs and didn't see it, but is there a way to specify the certificate duration? For example by default our ACME CA provides 1 year certificates, but I would like to do 90 or even shorter length certificates, for dev and test systems.
Thanks!

Hi,
the certificate lifetime is given be the issuing CA. The ACME protocol does not allow to specify that. I agree that short lifetimes are preferable. You could set up a separate CA for dev and test systems, but then you have to manage the trust anchors for that somehow for your clients. Depends on your particular setup how tricky that is.

Hmm that's interesting that Traefik supports it as a configuration https://doc.traefik.io/traefik/https/acme/#certificatesduration, so I had assumed it was specified by ACME.

I was wrong, one can request a notBefore and notAfter and the CA will deny issuing the cert if it does not agree to that.

Coming back to this: I had an exchange with the senior Lets Encrypt engineer on this and there are problems with using notBefore/notAfter in ACME. The spec says, in short, these parts of the Certificate Request must be either obeyed or certificate creation must be rejected.
Let's Encrypt does not support other lifetimes and this is one of the reasons for it. It adds complexities to their business that they do not want (my interpretation). Now other CAs might choose differently. I myself tend to side with Lets Encrypt here. I do not want to handle the issues that I foresee would arise with adding support for this in Apache. Other ACME clients might choose differently and that is totally fine.
If I were to design this feature for an ACME CA, I would let people configure desired lifetimes outside the ACME protocol itself. What I mean by this is that a user should be able to configure a DNS name with cert lifetime information.
Maybe that is done in a CA user configuration (for CA with user accounts) or a specific DNS entry that is looked at by the CA. These would say __acme_lifetime.xxx.yyy.com: 10 days, configured once and done.
Something like that is how I would go about it.

Just an addition to the mastodon thread about this and more explanations: https://chaos.social/@icing/110518749878760014


Slam / Markerless AR

Do you want to request a feature or report a bug?
feature

What is the current behavior?
not supported
If the current behavior is a bug, please provide the steps to reproduce.

Please mention other relevant information such as the browser version, Operating System and Device Name
What is the expected behavior?
If this is a feature request, what is motivation or use case for changing the behavior?
Today Slam or markless ar is a Must for an AR framework
I have reviewed many issues or feature requests , and followed your progress on documenting and adding slam feature in your trello . but no where found any solutions for this .
Is this feature ( slam ) or markerless tracking developed and usable in AR.js ?
thank you very much for your supporting

Hi,
it is not supported at the moment. No plans for the future, we are focusing on making better the location, marker and image tracking.

Today Slam or markless ar is a Must for an AR framework

Well, it depends on use cases :)
You can use AR.js in conjunction with other frameworks libraries that offer that: check WebXR and ModelViewer.


Authereum, Walletconnect and MEW connect aren't working following instructions

I was able to get MetaMask, Torus, Portis and Fortmatic working.
Authereum results in the error: "Class extends value undefined is not a constructor or null|". Following instructions on: https://github.com/Web3Modal/web3modal/blob/master/docs/providers/authereum.md
WalletConnect and MEWConnect both result in "global is undefined errors". I tried several polyfills to resolve the matter, but couldn't get it to work. Following instructions on: https://github.com/Web3Modal/web3modal/blob/master/docs/providers/walletconnect.md and https://github.com/Web3Modal/web3modal/blob/master/docs/providers/mewconnect.md
As mentioned, I was able to get  MetaMask, Torus, Portis and Fortmatic working. I'm using Angular 11, and (perhaps relevant) the ethers.js library.

Having the same issue using VueJS as well..

Hi @startpage-finance @jefflam, you probably need to add node polyfills to your app:
Webpack5: https://github.com/Richienb/node-polyfill-webpack-plugin
Vue 3 + Vite: https://github.com/voracious/vite-plugin-node-polyfills
Vue 3 + Vite example:
import { nodePolyfills } from "vite-plugin-node-polyfills";

export default defineConfig({
  plugins: [
    nodePolyfills({
      protocolImports: true,
    }),
  ],
});

With stable version 2.0.0 of Web3Modal now released, we are officially dropping support for version 1.x
Due to this this issue/pr was marked for closing. It is highly recommended to upgrade as 2.x will be receiving further updates that will enable functionality for some of our newer sdks like auth and push as well as support for WalletConnect v2 (See this post about WalletConnect v1 being deprecated https://medium.com/walletconnect/walletconnect-v1-0-sunset-notice-and-migration-schedule-8af9d3720d2e)
If you need to continue using Web3Modal 1.x and require this feature/fix implemented, we suggest adding it via forking V1 branch.


[Feature] Allow anon users to set alerts to monitor status page for updates

⚠ Please verify that this feature request has NOT been suggested before.

[X] I checked and didn't find similar feature request

🏷 Feature Request Type
New Notification, UI Feature
🔖 Feature description
The idea would be that a user can "Subscribe" to a status page and get notifications for any changes in status. This way an anonmous user can setup alerts for the status page.
Jira's Status page has this functionality

✔ Solution
Add an option to subscribe to service status on the public status page to a non-registered user
❓ Alternatives
Adding many alerts or using a webhook to an external service, but there isnt a clean soultion
📝 Additional Context
Not sure, if you need anything else LMK

I have a OSS page on status page with lots of subscribers and wait to move to uptime kuma, but at this time without this is deal brek :(
https://status.packagist.com.br/

Same of #916

@louislam please close as repetitive or give me access to to so if you want.


Lets encrypt failed and cannot renew certs

It seems that the last update it failed the lets encrypt part and all the sites now are failed due to that , what can we do to have it fixed ?
I get this as error and it was working fine before , I just replaced my domains with domain but you will get the idea.
I tried to delete the old cert to re-generate again , nothing, all failed today and yesterday on renewal process and dead.
Please I need a solution asap. Thanks in advance.
Error: Command failed: /usr/bin/certbot certonly --non-interactive --config "/etc/letsencrypt.ini" --cert-name "npm-20" --agree-tos --email<EMAIL_ADDRESS>--preferred-challenges "dns,http" --domains "g1.domain.network"
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator webroot, Installer None
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for g1.domain.network
Using the webroot path /config/letsencrypt-acme-challenge for all unmatched domains.
Waiting for verification...
Challenge failed for domain g1.domain.network
http-01 challenge for g1.domain.network
Cleaning up challenges
Some challenges have failed.
at ChildProcess.exithandler (child_process.js:308:12)
at ChildProcess.emit (events.js:314:20)
at maybeClose (internal/child_process.js:1022:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:287:5)

To get more details about the failure, could you look at log/letsencrypt/letsencrypt.log, under the directory you mapped to /config?

Beside DNS or other setup errors, this can also be a firewall issue... For example if you have DNSBL lists enabled in OPNsense or Pfsense.

well it seems that you are right the firewall blocked somehow the letsencrypt server to talk to the servers and that was causing the error so i disabled the firewall and tried again and it worked , now i need to find a way to whitelist those let’s encryption servers

Nice! I had a simular issue...
More info: https://community.letsencrypt.org/t/renewal-or-new-issue-behind-a-firewall-fails-due-to-le-operation/135571

So, the problem is caused by ...
Examination of HTTP and LE logs following the renewals revealed that:

LE has only two servers of its own that issue http-01 challenges (outbound1. and outbound2.letsencrypt.org 1)
All other challenges were issued by AWS cloud instances using widely varying IP addresses

The great majority of these AWS issued IP addresses appear in DNS blacklists - presumably because their previous users used them to spray out the very sort of traffic nobody wants passing a firewall protecting Internet facing systems.


[PE-D][Tester A] Possible flaw with creating assignments of the same name with different max score

Two students can have assignments of the same name, but different max score, simply by using the assignIndiv command.
This is potentially problematic because gradeGroup attempts to grade all assignments with the same name, but is unable to grade if the score given is higher. Perhaps it would make more sense to make assignment names unique so this cannot happen.

Labels: type.FeatureFlaw severity.Low
original: Dioclei/ped#2

I think we can just state in the UG that it is the intended behavior that all the assignment under the same group when done using gradeGroup must be below the maxScore


Show hide fields and dialog tabs based on dropdown and checkbox selection

Currently, we can show/hide fields based on the dropdown selection or checkbox checked values.
However, it is not possible to show hide fields based on the combination of both.
Moreover, sometimes there is the requirement to show/hide dialog tabs based on dropdown or checkbox selected value or combination of both. This is currently not possible.
Lastly, if a field has required field validation applied on it and the field is hidden, it is not possible to submit the dialog form, when no value has been provided for the field. This can be very confusing behavior for the user.

PR: https://github.com/Adobe-Consulting-Services/acs-aem-commons/pull/1412

Hi @davidjgonzalez
Can this issue be reopened? I have made the changes based on the review comments in the PR #1412
Thanks!


pulumi up java.lang.NullPointerException

What happened?
When doing pulumi up exception java.lang.UnsupportedOperationException is being thrown
Example
pulumi up
failed with an unhandled exception:
    java.lang.UnsupportedOperationException: Convert [com.pulumi.aws.alb.TargetGroup.targetHealthStates]: Error converting 'java.util.Collections$UnmodifiableRandomAccessList' to 'TypeShape{type=interface java.util.List, parameters=[TypeShape{type=class com.pulumi.aws.alb.outputs.TargetGroupTargetHealthState, parameters=[]}]}'. null
    	at com.pulumi.serialization.internal.Converter.convertObjectUntyped(Converter.java:119)
    	at com.pulumi.serialization.internal.Converter.convertValue(Converter.java:86)
    	at com.pulumi.core.internal.OutputCompletionSource.setValue(OutputCompletionSource.java:95)
    	at com.pulumi.deployment.internal.DeploymentImpl$ReadOrRegisterResourceInternal.lambda$completeResourceAsync$0(DeploymentImpl.java:1187)
    	at java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:642)
    	at java.base/java.util.concurrent.CompletableFuture$Completion.exec(CompletableFuture.java:479)
    	at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:290)
    	at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1020)
    	at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1656)
    	at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1594)
    	at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:177)
    Caused by: java.lang.NullPointerException
    	at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:889)
    	at com.google.common.collect.ImmutableList$Builder.add(ImmutableList.java:813)
    	at com.pulumi.serialization.internal.Converter.tryConvertList(Converter.java:642)
    	at com.pulumi.serialization.internal.Converter.tryConvertObjectInner(Converter.java:277)
    	at com.pulumi.serialization.internal.Converter.convertObjectUntyped(Converter.java:115)
    	... 10 more

Output of pulumi about
CLI
Version      3.94.2
Go Version   go1.21.4
Go Compiler  gc

Plugins
NAME  VERSION
java  unknown

Host
OS       darwin
Version  14.0
Arch     x86_64

This project is written in java: executable='/Users/slawek/.sdkman/candidates/java/11.0.2-open/bin/java' version='openjdk 11.0.2 2019-01-15
OpenJDK Runtime Environment 18.9 (build 11.0.2+9)
OpenJDK 64-Bit Server VM 18.9 (build 11.0.2+9, mixed mode)' java='/Users/slawek/.sdkman/candidates/java/11.0.2-open/bin/java' javac='11.0.2' maven='Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)'

Backend
Name         Name
URL            s3://...
User           slawek
Organizations
Token type     personal

Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

@mrge-slawek-mazur, could you share a small, self-contained program that reproduces the behavior?

Hi, any plans for when this might be fixed?

Hello, I have experienced the same issue and so far have been unable to get Pulumi to add my target group to my load balancer. I am very new to Pulumi and created a Github issue in what I now believe is the wrong place:
https://github.com/pulumi/pulumi-ai/issues/66
It has Java code to reproduce this issue

I tried @cnunciato's example and couldn't repro. But I'm using a more recent version of Java, from pulumi about:
Host
OS       darwin
Version  14.4.1
Arch     arm64

This project is written in java: executable='/opt/homebrew/opt/openjdk/bin/java' version='openjdk 18.0.2 2022-07-19
OpenJDK Runtime Environment Homebrew (build 18.0.2+0)
OpenJDK 64-Bit Server VM Homebrew (build 18.0.2+0, mixed mode, sharing)' java='/opt/homebrew/opt/openjdk/bin/java' javac='18.0.2' maven='Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)' gradle='7.5.1'

@cnunciato, does this still repro for you?


Automatically generate command line reference documentation

Docs on docs site are usually out of date.
Automate the generation of reference docs using https://github.com/spf13/cobra/blob/master/doc/md_docs.md.

cc @Kong/team-docs

Closed by mistake.

FYI for whoever works on this issue, I'm happy to help figure out the markdown formatting for the output.

@lena-larionova So I took a stab at this with #382.

You will need to install Go the machine where you want to generate the docs.
Clone this repo
run make generate-cli-docs and you will have docs generated in docs/cli-docs directory in the repo.

Let me know what you think.

I'm way too slow at noticing github notifications, ack. Thanks for putting this together - I'll take a look and then help build on top of what you've created.


Support WGSL shaders

PlayCanvas is currently using glslang and twgsl to transpile GLSL into WGSL. This doesn't support all new features in WGSL which are not usable now.
Things like

@group(0) @binding(0) var externalTexture : texture_external; for fast video texture support.
@builtin(instance_index) instanceIdx : u32 for hardware instancing.

The shader generator will need to be changed and all current shaders will need to be rewritten. It will need to be possible for developers to provide shader chunks for both GLSL and WGSL at the same time for backwards compatibility.

related: https://github.com/playcanvas/engine/issues/5691


Frame counter, time and best practices

Almar said that the main goal was to get the architectural principles of PyGFX down before version "1".
One challenge I've faced is with time.
It would be convenient for us to access to the concept of "time" so that we may control certain animations.
However, I'm unsure how to add this time to the global state. Integers? Floating point?
We are looking something with "60 fps" granularity, and it seems that if you have a single floating point counter that it would start to accumulate increasing error as time passed. That isn't really nice when you have animations that require "subsecond" accuracy for computing the "phase" of some object.
It would be nice if it were in some shared state dictionary (i remember I found it a while back).
I will say that we do use a hack with our system where we render the same scene multiple times to create a really large image. so it would be nice to be able to "pause" time sometimes ;)

This is a good point. We've already thought about this as part of #495. I can recommend this post about this topic: http://gameprogrammingpatterns.com/game-loop.html
One thing we want to do is decouple rendering from updating animations, so that animations can be updated with a fixed time interval, even when the fps varies.

In terms of additions to #495 it might to add the variables to the stdinfo uniform buffer
https://github.com/pygfx/pygfx/blob/367e02888adea122a78915bdf32085ed7d07830a/pygfx/renderers/wgpu/engine/shared.py#L21
so they can be accessible by shaders ^_^


[Field Change Request] - Table "Document Entry" - Field "Document Type"

We like to request the following change:
Object: Table "Document Entry"
Field:  field(8; "Document Type")
Reason: Please change the type to an enum, to make it extensible so we can add our custom types.
Code to change:
field(8; "Document Type"; Enum "Document Entry Doc Type")

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


examine osquery

https://osquery.io/
https://github.com/osquery/osquery

maybe create a source plugin for it?


DNS resolution different between version 6.20 and 6.25

Hi,
We noticed that cf api api.<my-systen-domain> resolves the hostname under our specific network configuration differently when using CLI version 6.20 and 6.25. Version 6.20 resolves it the same as curl, but version 6.25 resolves it to a different IP (which then doesn't work down the line).
I suspect it's due to Go's default domain name resolver, which is configured during build time (if at all). To troubleshoot this issue further, could someone please help me find the build command used to build the binary versions 6.20 and 6.25 for Linux 64bit which are available on https://github.com/cloudfoundry/cli/releases?
Other ideas are of course also appreciated.
Thanks,
Peter

@petergtz Please check out https://github.com/cloudfoundry/cli/blob/master/ci/cli/tasks/build-binaries.yml#L43.

@dkoper Thanks for your quick response! Your link is what I looked at earlier, but then was surprised, that the two versions still give different results for DNS resolution. Hence, I was wondering if version 6.20 was potentially built differently.
Especially, because https://github.com/cloudfoundry/cli/commit/66d3f5da28f76d08872f5a90f9be678929b841a6 says that the build command was changed with version 6.19, so only slightly before 6.20 was released. Is it possible that somehow this build task was not used just yet for version 6.19 and 6.20 even though it was there already?
Or is there some string baked into the binary who could tell me that?
Really fishing for explanations here, because the results that I see do not make sense to me.

Or is there some string baked into the binary who could tell me that?

Nope.

Really fishing for explanations here, because the results that I see do not make sense to me.

Could it be your OS? These old versions of CLI were built with Go 1.7.x and now we have moved on to Go 1.9.x.
I would suggest that you try the latest and if this is still occurring to reopen this issue and mention what OS and what CLI version you used.
Max and Sebastian

@petergtz You can use strings ./cf | grep 'go1\.' to determine the Golang version a binary was built with.
I am not sure if there is a way with Golang to enable DNS resolving trace output to see what resolver is used.
We reported a change in DNS resolution in the 6.22.0 release notes due to the upgrade to Golang 1.7.1 that resolved some issues introduced around Golang 1.5.
https://github.com/cloudfoundry/cli/releases/tag/v6.22.0

@dkoper I haven't gotten the chance yet to pick up this work again, but your 2 pointers about grepping for strings and also the change in DNS resolution in 6.22 are very helpful. Will dig into that and see if I can find something. Thanks a lot!


WIP: Add support for i18n

Interesting stuff, nice!

Is how this works from translator point of view documented anywhere yet?

Nope, they can use usual tools to edit .po files
Lots of strings are still not translateable.
2016-03-08 8:39 GMT+00:00 Mikaela Suomalainen<EMAIL_ADDRESS>
Is how this works from translator point of view documented anywhere yet?
—
Reply to this email directly or view it on GitHub
https://github.com/znc/znc/pull/1237#issuecomment-193664050.


Log glue - herbs2winston

As we are using practically all herbs projects with winston + kinesis, with code repetition in several places, I imagined that we can create a new herb glue that automatically connects herbs with winston (and still remains compatible for winston connectors ), possible a herbs2winston glue;
I would like to know if you think that there would be a real gain in this implementation and how it could work (breaking as little as possible of what we have today)
Add: Imagine just like the buchu that you can put in .env the audit for it to blow the exception, we can put this glue to log the entire use case execution that happens, I don't know, it was just an idea.
Add: I imagine the lib going more towards, for example, automatically auditing all usecases with a predefined (winston) transport. Or log all usecases that return error automatically.

did you have some suggest for the log metadata and log string/object format?
I will call it like an lib? all usecases will be logger automagincally? how will be the glue usage?

@jhomarolo


Broadcast recent smartcontract activity to users

When a user interacts with the smart contract we can broadcast that to other users so the flatland seems more dynamic and interactive.
Can indicate all interacts:

[User] renamed Square
[User] claimed Square at (x, y)

Could possibly implement this as another side panel and each event can be a toast above the last event

Since this is a relatively large addition (likely needing sub-files) I think it should be in a separate folder from the canvas folder.
Would be nice if it dynamically showed the last few transactions (~6ish) as individual toasts.
The last toast in the list could maybe be a "see all transactions" toast

Definitely agreed. There are two things our app should listen for:

New square claims
Square colour changes

Ok so I have made some progress on this in commit 882ef6c5517179b9abef566f260409d7e3cd56cc
I just wanted to lay out what is left to do:
Placement

[ ]  Implement tabs for 'Square Manager' and 'History'
[ ] Show only 6 most recent events on actual canvas (in a column next to side panel), and show all in History

Content

[ ] Implement the same feature for Colour Change Events
[ ] Make toasts dismissible
[ ] Add square icon on top left of toast
[ ] when toast is clicked, relevant square is selected in canvas above
[ ] Indicate who square owner is in toast

Thanks for all the work so far. I have a few thoughts and comments that we could discuss going forward:

I agree that there should be a separation between the 'Recent Activity' and 'History' tab

The 'Recent Activity' panel
-- Shows the latest transactions
-- # of transactions shown can be a fixed # but in future could consider scaling up and down depending on screen size
-- Can implement as a row with columns. With each update the toast of one column can shift to the next and discarding the last.

History tab
-- I think when assessing the transaction history it would be better to process this information into a table since we are looking at many entries
-- We should limit the table length to latest 100 entries and have the option to load the rest of the entries to help with loading times
-- There could be a toggle to only show the users transactions which will then filter the table accordingly

Side panel
-- I think we could implement another form of history on the side panel to show the history of the clicked square
-- We could have a "show square history" button on the clicked square alert
-- Perhaps we could have the square icon clickable with a tooltip "see square history" instead
-- Could bring up a modal showing a table/toasts from that square only

Other thoughts:
-- Is there value in providing the transaction hash? Maybe we could display it as a tooltip on hover of the toasts and as a column in the table
-- Is there value in adding a User page where all users can access and see the activity of one user?

Hey dude, thanks for the thoughtful comments, my response below:

Recent Activity panel

Yeah I think you're spot on to bring up the responsiveness on the site. Luckily, react-bootstrap handles a lot of this behind the scenes, and if you visit Flatland via the Metamask wallet/browser mobile app, it already looks pretty decent

History Tab

Also agreed, the Toasts don't look great in a grid like that. A paginated table makes much more sense
It would be nice to show who claimed/changed squares. Unfortunately, the smart contract events only share data about 1) the square id and 2) the colour of the affect square. So we would need to update the event emitters in the smart contract

Side Panel

(you said these ideas are controversial but I think they're all great lol)
it would be awesome to see a square's history. Especially when they are transferred between users too. It could say the price it was sold for. (Check out this page for  CryptoPunk # 1

Other thoughts

Transaction hash would be useful - we could create it as an etherscan link so that they can view the tx themselves
Same for address page. The data is all publicly available on the blockchain, so we may as well represent it on our site - again, see the example from CryptoPunks

It seems like the remaining tasks from this issue are now in #70 and #71, so I am going to close this issue. Please re-open if there's something I missed


hail.utils.java.FatalError: ClassFormatError: Too many arguments in method signature in class file

I wonder whether you ever faced the error or whether you can give any suggestions as to why it could be happening for us:
hail.utils.java.FatalError: ClassFormatError: Too many arguments in method signature in class file
when mt.write is run here:
https://github.com/broadinstitute/seqr-loading-pipelines/blob/master/luigi_pipeline/seqr_loading.py#L118
I asked it on Hail forum too:
https://discuss.hail.is/t/hail-utils-java-fatalerror-classformaterror-too-many-arguments-in-method-signature-in-class-file/2767

From the hail forum it looks like you were able to fix this with an updated version of spark and hail, so I will consider this issue resolved

No, it works with old hail, spark but not with the new versions. The new ones actually give the same error.

Hi -- we haven't hit this before and right now are running this pipeline on hail 0.2.97  on GCP dataproc so it seems like you may be onto something with EMR.

Got it, thank you! Will keep looking into EMR.


Add = sign in assignment

=@ embeds the contents, but here we actually want to use @ to simulate file upload, see:
https://github.com/jkbrzt/httpie#request-items

=@ embeds the contents, but here we actually want to use @ to simulate file upload, see:
https://github.com/jkbrzt/httpie#request-items


useService isn't returning the state on first render

Description
When I try to useService, I'm finding that the current state isn't being returned correctly.
Expected Result
The state should be available for use on first render of the component.
Actual Result
The state is undefined.
Reproduction
https://codesandbox.io/embed/crimson-http-eksyg?fontsize=14&hidenavigation=1&theme=dark
Additional context
On my local machine I'm on the latest @xstate/react (0.8.1). The code installed in node modules is clearly only setting current to service.state and not service.state || service.initialState.
function useService(service) {
    var _a = __read(react_1.useState(service.state), 2), current = _a[0], setCurrent = _a[1];
    react_1.useEffect(function () {
        // Set to current service state as there is a possibility
        // of a transition occurring between the initial useState()
        // initialization and useEffect() commit.
        setCurrent(service.state);
        var listener = function (state) {
            if (state.changed) {
                setCurrent(state);
            }
        };
        var sub = service.subscribe(listener);
        return function () {
            sub.unsubscribe();
        };
    }, [service]);
    return [current, service.send, service];
}

Should I just upgrade to 1.0.0-rc1 or is this something that will be fixed on a non-release candidate version?

@Blacktiger Does it work as expected with 1.0.0-rc1?

I tried an upgrade and it seems ok. I'm only using useMachine and useService so I suppose as long those are working fine for me it should be fine to just upgrade. I just didn't have the version initially since npm install doesn't without spelling the version out.

I'd think if you want to close this issue, it's ok since there is a working version but it might be better to leave it open until there is a "stable" version released?

I'll leave it open and we'll release @xstate/react and @xstate/vue v1 soon!

I'm not sure if this is the same issue, but it appears as though the service being returning from useMachine is not initialized so it has no state on the first render unless you start the service yourself:
https://codesandbox.io/s/vigilant-solomon-nfzxw

I can confirm that the service is initialized on initial render for rc.3
https://codesandbox.io/s/mystifying-sun-q2hgc

Things don't seem to be working if you use @xstate/fsm: https://codesandbox.io/s/boring-rubin-5104z

Also for some reason the codesandbox was saying that I needed xstate to use @xstate/react 🤷♂

Things don't seem to be working if you use @xstate/fsm: https://codesandbox.io/s/boring-rubin-5104z

That's because you were trying to use useService for xstate, just import it from @xstate/react/lib/fsm: https://codesandbox.io/s/frosty-night-j6muu

Also for some reason the codesandbox was saying that I needed xstate to use @xstate/react 🤷♂

Can't quite repro this, but it might be related to the former problem.

I'm having this exact same issue:
TypeError: Cannot read property 'state' of undefined
  107 | exports.useMachine = useMachine;
  108 | function useService(service) {
> 109 |     var _a = __read(react_1.useState(service.state), 2), current = _a[0], setCurrent = _a[1];
  110 |     react_1.useEffect(function () {
  111 |         // Set to current service state as there is a possibility
  112 |         // of a transition occurring between the initial useState()

  4 | function Child({service}) {
  5 |
> 6 |   const [state] = useService(service)
  7 |
  8 |   console.log({ childrenValue: state.value });

Once the child reaches its final state the service is undefined and the app crashes.
Repro: https://codesandbox.io/s/heuristic-dew-b2h23?file=/src/child.machine.js (uncomment type: "final" and comment always: "idle")

@ivorpad Try<EMAIL_ADDRESS>to verify that it solves the issue.

Closing this as the latest released work on @xstate/react RC resolves this.


Application Insights CPU metrics is not valid for Azure Spring Apps

Describe the bug
Application Insights CPU metric is not properly measured in Azure Spring Apps. In Azure Spring Apps it is possible to have application with different vCPU assigned, up to 4 vCPU.
However the underlaying virtual machines seems to have 16 cores.
When Application Insights calculates de CPU utilization, for instance in the Live Metrics tab, the maximum CPU utilization it shows corresponds to number of vCPU configured in Azure Spring Apps divided by the host physical CPU.
Eg, if the app has 4vCPU and VM has 16cores the max CPU shown is 4/16 -> 1/4 -> 25%.
If the app has 1vCPU -> 1/16-> 6,25%.
This scenario was detected with Java applications, not verified with other runtimes.
On the app logs detected the following JVM setting injected by Azure Spring Apps:
JAVA_OPTIONS has -XX:ActiveProcessorCount=16
To Reproduce
Steps to reproduce the behavior:

Ensure Azure Spring Apps has Application insights enabled
Create an application in Azure Spring Apps with 1CPU.
Deploy the application (Java).
Execute a load test against the deployed application.
Looking at Java metrics verify that process.cpu.usage/system.cpu.usage is 1 or near 1.
Open Application Insights and Live Metrics. Look for the application. The CPU Total is 1/16 -> 6,25%. This value is not correct, it should show 100%.

Expected behavior
The CPU total in Application Insights should be 100 x process.cpu.usage. In above case 100%.
Screenshots

Additional context
On the app logs detected the following JVM setting injected by Azure Spring Apps:
JAVA_OPTIONS has -XX:ActiveProcessorCount=16
Can we contact you for additional details? Y
If yes, please send us your contact information to<EMAIL_ADDRESS>and include the issue number in the email title.

Is it possible to switch to the metrics from Azure Monitor? App CPU Usage is the most accurate one.

Thanks @LGDoor
I'm using process.cpu.usage and I see that results are aligned with App CPU Usuage. However, the issue that I see is that CPU Total in Application Insights live metric is not real.
In the latest test I'm performing I see it is max 50%. I checked the logs of the application and I see again Setting Active Processor Count to 8:
Setting Active Processor Count to 8
Adding $JAVA_OPTS to $JAVA_TOOL_OPTIONS
Calculated JVM Memory Configuration: -XX:MaxDirectMemorySize=10M -XX:MaxMetaspaceSize=209353K -XX:ReservedCodeCacheSize=240M -Xss1M (Total Memory: 8G, Thread Count: 250, Loaded Class Count: 34548, Headroom: 0%)
Enabling Java Native Memory Tracking
Adding 127 container CA certificates to JVM truststore
Configuring Azure Application Insight properties
Picked up JAVA_TOOL_OPTIONS: -Djava.security.properties=/layers/paketo-buildpacks_microsoft-openjdk/java-security-properties/java-security.properties -XX:+ExitOnOutOfMemoryError -javaagent:/layers/paketo-buildpacks_azure-application-insights/azure-application-insights-java/applicationinsights-agent-3.4.2.jar -XX:ActiveProcessorCount=8 -Deureka.client.service-url.defaultZone=https://fitness-store-prod-vnet.svc.private.azuremicroservices.io/eureka/default/eureka -Xms5800m -Xmx5800m -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=1099 -Dcom.sun.management.jmxremote.local.only=true -Dmanagement.endpoints.jmx.exposure.include=health,metrics -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Dspring.jmx.enabled=true -Dserver.tomcat.mbeanregistry.enabled=true -Dfile.encoding=UTF8  -XX:MaxDirectMemorySize=10M -XX:MaxMetaspaceSize=209353K -XX:ReservedCodeCacheSize=240M -Xss1M -XX:+UnlockDiagnosticVMOptions -XX:NativeMemoryTracking=summary -XX:+PrintNMTStatistics
OpenJDK 64-Bit Server VM warning: Sharing is only supported for boot loader classes because bootstrap classpath has been appended
2023-02-22 11:54:43.001Z INFO  c.m.applicationinsights.agent - Application Insights Java Agent 3.4.2 started successfully (PID 1, JVM running for 3.175 s)
2023-02-22 11:54:43.006Z INFO  c.m.applicationinsights.agent - Java version: <IP_ADDRESS>, vendor: Microsoft, home: /layers/paketo-buildpacks_microsoft-openjdk/jdk

As the application has 4CPU assigned, what I see in Application insights is 4CPU assigned/8 Active Processor Count = 0.5 -> 50%
The integration with Application Insights doesn't work as expected. Same application running on Azure App Services or Azure Container Apps is properly shown in App Insights.
The issue seems related to that Setting Active Processor Count to 8. A couple of months ago I performed same test there was JAVA_OPTIONS has -XX:ActiveProcessorCount=16 in the logs, and CPU in app insights was 4CPU assigned/16 Active Processor Count = 0.25 -> 25%

@felipmiguel I'm assuming that you are using Enterprise tier. It appears that this is related to this buildpacks issue. Waiting for buildpacks to provider a way to stop injecting -XX:ActiveProcessorCount.
In that issue, a workaround is mentioned, which is to manually pass -XX:ActiveProcessorCount= to override the one that buildpacks injects.

Hi @domainname. I'm using Enterprise tier. The behavior will be different if I deploy a jar file instead of using a build?

Jar still uses buildpacks in Enterprise but it may not trigger the same buildpack issue. worth to give it a try.


Add Troubleshooting section for high resource usage on AKS

Related issue
Closes #788
Proposed Changes
Based on our findings in https://github.com/kyverno/kyverno/issues/6539 we want to add a new Troubleshooting section about aks managed clusters and the webhook endless loop.
Checklist

[x] I have read the contributing guidelines.
[x] I have inspected the website preview for accuracy.
[x] I have signed off my issue.

Thanks for addressing this! Seeing that the solution from the Helm chart perspective will not be available until 1.10, two suggestions:

Either remove the Helm comment now so we can accept and make available to the current (1.9) docs or
Accept this PR into main but not make it available on the 1.9 docs.

Thanks for the feedback, since the webhook issue exists already a long time, I would prefer to simply wait for the 1.10 release.
Also I a have one more suggestion (see https://github.com/kyverno/website/issues/788) about the webhook issue in general. Can you share your thoughts about it?
BTW: What is your preferred way of discussing this? Inside the merge request or in the assigned issue?


Better, more tuneable logging

We ought to use a proper logging framework rather than ad-hoc print statements. Should we using tracing? Something else? We should be able to enable or disable specific logging aspects, independently of release/debug mode of compilation. This isn't (yet) high priority, but it will be worthwhile to implement soon.

Now that we are using Warp, and Warp integrates Tracing, this is a tractable problem.


support for linux-arm64 (IDFGH-4663)

I have a number of ESP32-based boards that I'd like to develop against using my arm64-based linux systems.
Following the installation instructions for ESP-IDF results in an error that linux-arm64 isn't supported.
Examination of tools/tools.json shows that there are, indeed, no entries for linux-arm64, though the 32-bit linux-armel builds are there.
Is there something preventing linux-arm64 builds from being provided? The number of linux-arm64 systems in use is only going to increase now that Apple is releasing M1-based hardware.

Hi @DJSundog, we will add arm64 build next time we release the toolchain. I can't give an exact timeline but most likely there will be a release in Q1. We are already tracking this in https://github.com/espressif/esp-idf/issues/6432, so I will close this issue. Please follow the link to that older issue and click "Subscribe" to get notified when the issue is resolved.

Hi @DJSundog, we will add arm64 build next time we release the toolchain. I can't give an exact timeline but most likely there will be a release in Q1. We are already tracking this in https://github.com/espressif/esp-idf/issues/6432, so I will close this issue. Please follow the link to that older issue and click "Subscribe" to get notified when the issue is resolved.

Hey, do you now have a timeline for the next release? The feature is highly appreciated.


optimize: some about rpc optimize.

Ⅰ. Describe what this PR did
1.pull away from the handler, Follow a single principle of responsibility.
2.Reorganize dependencies.
3.create RpcServerBootstrap.
4.(TODO)create processor to handle channelread() logic.
Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #1935 into develop will decrease coverage by 0.1%.
The diff coverage is 3.1%.

@@              Coverage Diff              @@
##             develop    #1935      +/-   ##
=============================================
- Coverage      55.12%   55.01%   -0.11%
+ Complexity      2402     2401       -1
=============================================
  Files            429      430       +1
  Lines          14261    14293      +32
  Branches        1673     1681       +8
=============================================
+ Hits            7861     7863       +2
- Misses          5693     5722      +29
- Partials         707      708       +1

Impacted Files
Coverage Δ
Complexity Δ

...main/java/io/seata/core/rpc/netty/RmRpcClient.java
30.76% <ø> (-1.1%)
9 <0> (-1)

...c/main/java/io/seata/core/rpc/netty/RpcServer.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...va/io/seata/core/rpc/netty/RpcServerBootstrap.java
0% <0%> (ø)
0 <0> (?)

...ava/io/seata/core/rpc/netty/RmMessageListener.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...eata/core/rpc/netty/AbstractRpcRemotingServer.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...ata/core/rpc/DefaultServerMessageListenerImpl.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

server/src/main/java/io/seata/server/Server.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...a/io/seata/core/rpc/netty/AbstractRpcRemoting.java
10.88% <3.22%> (+1.23%)
4 <0> (+1)
:arrow_up:

...va/io/seata/core/rpc/netty/RpcClientBootstrap.java
34.83% <44.44%> (-0.89%)
6 <1> (+1)

...eata/core/rpc/netty/AbstractRpcRemotingClient.java
19.2% <6.34%> (+0.28%)
6 <1> (ø)
:arrow_down:

... and 6 more

@slievrly Conflict resolved.