vdc helm chart install hangs for several minutes before timing out.

initial versions of the vdc chart returned quickly, though ongoing configuration continued in the background.
the current chart can take a long time to return at the command line, which is confusing.
this is probably whilst waiting for initialization & could relate to a misconfiguration.
around 6 minutes in my test on IBMcloud using internal kafka (cp)
➜  charts git:(helm22) ✗ helm install vdc -f ~/cloud.yaml                                                  git:(helm22|✚3
2019/03/07 15:02:12 Warning: Building values map for chart 'cp-kafka'. Skipped value (map[]) for 'image', as it is not a table.
Error: timed out waiting for the condition
need to consider if reasonable, potentially look at configurable timeouts.
Slow kafka initialization is likely the root cause.

Root cause it actually likely to do with Helm and how it handles Jobs...

Helm seems to block until all of the Jobs are running
Since the Jobs run sequentially (would be nice if they could run in parallel!) this means each one has to complete before the next one starts
Each Job is also dependent on the deployment / services on which they depend actually being available before they will execute: so there is an additional wait on that (which may extend even further if the probes on the containers for eg. Atlas detects that it has raced itself and failed, thereby needing to be restarted and adding further delay)

While you can avoid the timeout causing an error by adding a --timeout 900 or the like to the Helm install command (which means a timeout of that many seconds per step rather than overall deployment [default is 300]), you'll still be blocked on returning to the command-line until the install command completes.  This seems to be the expected behaviour of Helm, though...
Also it's documented here (including a suggestion on monitoring the "actual" status):
https://github.com/odpi/egeria/tree/master/open-metadata-resources/open-metadata-deployment#deploying-the-demonstration

Yes I think it's because of the post-install hook which is kicking off the jobs and waiting for completion. It makes some sense, but may be a usability concern. I also don't know how it might affect installing a helm chart from within a catalog on some cloud platforms.
Not urgent, but will leave this open as we consider alternatives.
One suggestion I received was to use an initialization container instead (the original plan) (ensuring idempotency)- though jobs do seem a neater approach and are explicitly run once, in sequence. Nice.. Stateful sets also offer richer control of ordering, but I worry the binding is too tight.
Needs more research into other options. so leaving issue open for now.
Perhaps a hybrid solution might be

initContainers are not really an option -- the normal (non-init) container is blocked from starting until all initContainers have completed: so you'd be trying to configure something through the initContainer that isn't yet running as an actual container...  (Unless you're talking about a series of initContainers on some "dummy" Pod that does nothing but run through a set of initContainers ?)

yes that was the suggestion on one of the helm chats but i'm unconvinced. will discuss with some colleagues in out local teams with more experience - no need to rush into a change, but something we should address if we can (delay, timeout error, reported as failed - though does init, and kubectl status looks good0.

As a point of reference, I just had helm complete successfully - for the first time, on cloud:
➜  charts git:(helm32) helm install vdc -f ~/cloud.yaml                                                                                git:(helm32|)
NAME:   yellow-quail
LAST DEPLOYED: Thu Apr 18 08:09:32 2019
NAMESPACE: egeria
STATUS: DEPLOYED

RESOURCES:
==> v1/ConfigMap
NAME                        DATA  AGE
yellow-quail-openldap-env   6     5m43s
yellow-quail-vdc-configmap  21    5m43s

==> v1/Deployment
NAME                               READY  UP-TO-DATE  AVAILABLE  AGE
yellow-quail-vdc-atlas             1/1    1           1          5m43s
yellow-quail-vdc-egeria            1/1    1           1          5m43s
yellow-quail-vdc-gaian-deployment  1/1    1           1          5m43s
yellow-quail-vdc-ibm-igc           1/1    1           1          5m43s
yellow-quail-vdc-omrsmonitor       1/1    1           1          5m43s
yellow-quail-vdc-postgresql        1/1    1           1          5m43s
yellow-quail-vdc-rangeradmin       1/1    1           1          5m43s
yellow-quail-vdc-ui                1/1    1           1          5m43s

==> v1/Pod(related)
NAME                                                READY  STATUS   RESTARTS  AGE
yellow-quail-openldap-674b4db598-xq92c              1/1    Running  0         5m43s
yellow-quail-vdc-atlas-5b8f558946-ls45b             1/1    Running  0         5m43s
yellow-quail-vdc-egeria-54fcbfbbfb-gwqkp            1/1    Running  0         5m43s
yellow-quail-vdc-gaian-deployment-7dfdd86956-zllxg  1/1    Running  0         5m43s
yellow-quail-vdc-ibm-igc-66897d944b-gd8vb           1/1    Running  0         5m43s
yellow-quail-vdc-omrsmonitor-7769cdd46b-kqzsx       1/1    Running  0         5m43s
yellow-quail-vdc-postgresql-cdc5964b6-btmrp         1/1    Running  0         5m43s
yellow-quail-vdc-rangeradmin-6f5d58578c-bt4tm       2/2    Running  0         5m42s
yellow-quail-vdc-ui-7b78b49ddb-pnjgf                1/1    Running  0         5m42s

==> v1/Role
NAME                       AGE
yellow-quail-vdc-api-role  5m43s

==> v1/RoleBinding
NAME                               AGE
yellow-quail-vdc-api-role-binding  5m43s

==> v1/Secret
NAME                   TYPE    DATA  AGE
yellow-quail-openldap  Opaque  2     5m43s

==> v1/Service
NAME                                  TYPE       CLUSTER-IP      EXTERNAL-IP  PORT(S)                                                                     AGE
yellow-quail-openldap                 ClusterIP  <IP_ADDRESS>  <none>       389/TCP,636/TCP                                                             5m43s
yellow-quail-vdc-atlas-service        NodePort   <IP_ADDRESS>  <none>       21000:31000/TCP                                                             5m43s
yellow-quail-vdc-egeria-service       NodePort   <IP_ADDRESS>   <none>       8080:30080/TCP                                                              5m43s
yellow-quail-vdc-gaian-service        NodePort   <IP_ADDRESS>    <none>       6414:30414/TCP                                                              5m43s
yellow-quail-vdc-ibm-igc-service      NodePort   <IP_ADDRESS>  <none>       8080:30081/TCP                                                              5m43s
yellow-quail-vdc-omrsmonitor-service  NodePort   <IP_ADDRESS>   <none>       58080:31080/TCP                                                             5m43s
yellow-quail-vdc-postgresql-service   NodePort   <IP_ADDRESS>  <none>       5432:30432/TCP                                                              5m43s
yellow-quail-vdc-ranger-service       NodePort   <IP_ADDRESS>   <none>       6080:32080/TCP,6182:30182/TCP,6083:32299/TCP,6183:31210/TCP,3306:31763/TCP  5m43s
yellow-quail-vdc-ui-service           NodePort   <IP_ADDRESS>  <none>       8443:30443/TCP                                                              5m43s

==> v1beta2/Deployment
NAME                   READY  UP-TO-DATE  AVAILABLE  AGE
yellow-quail-openldap  1/1    1           1          5m43s

Worth mentioning as this is 'just' a timeout. If only helm was a little more flexible in this area..

Have you tried this?
$ helm install vdc -f ~/cloud.yaml --timeout 900

Helm does support overriding the timeout, you just need to tell it what value to override it with 😉

i think from prior experiments/reading, that flag governs how long helm waits for individual commands to complete, not how long it waits for jobs etc to complete. there have been some discussions in that area, some changes, and additional timouts in the specs themselves that affect this behaviour.

Correct, it's about timeouts of individual steps (which jobs are part of) rather than the deployment in its entirety -- but that just means that it will only timeout if an individual step takes longer than that value (?)  So you could in theory set it to a lower value and still have it work despite the overall deployment taking a long time (but each step completing in a time under the timeout)...  Adding it works for me 🤷♂


Change vkb::HPPGLTFLoader from a facade over vkb::GLTFLoader to a self-contained class using Vulkan-Hpp.

Description
Includes

slightly improved struct [HPP]Meshlet in [hpp_]api_vulkan_sample.h;
additional facade-functions in common/hpp_utils.h;
a new function is_image_format_supported in HPPPhysicalDevice, that catches the exception thrown on not supported formats;
some minor corrections/improvements in GLTFLoader and scene_graph::Scene
adjustments according to the new scene_graph/component classes in HPPVulkanSample and rendering::subpasses::HPPForwardSubpass;
new facade classes scene_graph::components::HPPCamera, scene_graph::components::HPPLight, scene_graph::components::HPPMesh, scene_graph::components::HPPPBRMaterial, scene_graph::components::HPPSampler, scene_graph::components::HPPTexture, scene_graph::components::HPPTransform, scene_graph::HPPNode, scene_graph::HPPScene, and scene_graph::scripts::HPPAnimation
adjustments in facade classes scene_graph::components::HPPImage and scene_graph::components::HPPSubMesh
fully transcoded classes scene_graph::components::HPPPerspectiveCamera and scene_graph::components::image::HPPAstc
a fix in gshader_to_mshader.mesh.

Build tested on Win10 with VS2022. All hpp-based samples tested on Win10 with NVidia GPU.
General Checklist:
Please ensure the following points are checked:

[x] My code follows the coding style
[x] I have reviewed file licenses
[x] I have commented any added functions (in line with Doxygen)
[x] I have commented any code that could be hard to understand
[x] My changes do not add any new compiler warnings
[x] My changes do not add any new validation layer errors or warnings
[x] I have used existing framework/helper functions where possible
[x] My changes do not add any regressions
[x] I have tested every sample to ensure everything runs correctly
[x] This PR describes the scope and expected impact of the changes I am making

Note: The Samples CI runs a number of checks including:

[x] I have updated the header Copyright to reflect the current year (CI build will fail if Copyright is out of date)
[ ] My changes build on Windows, Linux, macOS and Android. Otherwise I have documented any exceptions

Sample Checklist
If your PR contains a new or modified sample, these further checks must be carried out in addition to the General Checklist:

[x] I have tested the sample on at least one compliant Vulkan implementation
[x] If the sample is vendor-specific, I have tagged it appropriately
[x] I have stated on what implementation the sample has been tested so that others can test on different implementations and platforms
[x] Any dependent assets have been merged and published in downstream modules
[ ] For new samples, I have added a paragraph with a summary to the appropriate chapter in the samples readme
[ ] For new samples, I have added a tutorial README.md file to guide users through what they need to know to implement code using this feature. For example, see conditional_rendering
[ ] For new samples, I have added a link to the Antora navigation so that the sample will be listed at the Vulkan documentation site

Can we discuss this in the next samples call? The PR itself is fine, but it has a lot of framework changes and I'm unsure how these align with the framework direction we recently talked about.

Can we discuss this in the next samples call?

Sure, but I can't attend the next call. Will be back again next year.

@gary-sweet What compiler are you using? Obviously, the compilers in our CI are less picky. Maybe we should add that compiler to our CI? That said, would you please try again if my latest change resolves those errors?

I'm not sure how but I completely missed your reply somehow. Apologies for that.
Sadly the latest changes haven't changed the compile errors.
The compiler is "gcc version 8.3.0 (stbgcc-8.3-1.0) " for aarch64

Closed for now, as the C/Cpp unification takes a different path.


exploitdb: 2022-07-02 -> 2022-07-12

Description of changes
update to 2022-07-12
commit tagged as 2022-07-12: https://github.com/offensive-security/exploitdb/commit/d84f857e94f91c71fcb93041483f661d29023c1e

Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[X] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 181232 run on x86_64-linux 1

1 package built:

exploitdb


[Feature] Support materialized view for external table (step 1/3)

What type of PR is this：

[ ] BugFix
[x] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

#11116
#9792
Problem Summary(Required) ：

In this PR, There are two main feature:

support create mv based on external (hive/hudi) unpartitioned table
support create mv select data from different database

Major changes:

Use BaseTableInfo instead of baseTableIds to represent MV-dependent base tables
Where OlapTable is heavily dependent, use Table instead
Because dbId and tableId are not available for external table, use TableIdentifier to uniquely identify a table

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] I have added user document for my new feature or new function

run starrocks_fe_unittest

run starrocks_fe_unittest

[FE PR Coverage Check]
:disappointed: fail : 121 / 176 (68.75%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/catalog/MaterializedView.java
28
61
45.90%
[81, 82, 83, 84, 85, 86, 89, 90, 92, 97, 98, 100, 105, 109, 113, 117, 132, 137, 138, 139, 141, 149, 377, 445, 446, 448, 449, 450, 452, 453, 460, 464, 465]

:large_blue_circle:
com/starrocks/catalog/HudiTable.java
1
2
50.00%
[171]

:large_blue_circle:
com/starrocks/catalog/HiveTable.java
1
2
50.00%
[176]

:large_blue_circle:
com/starrocks/sql/analyzer/MaterializedViewAnalyzer.java
12
17
70.59%
[131, 132, 133, 145, 146]

:large_blue_circle:
com/starrocks/scheduler/PartitionBasedMaterializedViewRefreshProcessor.java
65
79
82.28%
[320, 336, 401, 460, 465, 474, 531, 532, 533, 538, 539, 540, 548, 552]

:large_blue_circle:
com/starrocks/catalog/Table.java
7
8
87.50%
[174]

:large_blue_circle:
com/starrocks/sql/ast/CreateMaterializedViewStatement.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/server/LocalMetastore.java
5
5
100.00%
[]

[FE PR Coverage Check]
:disappointed: fail : 121 / 177 (68.36%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/catalog/IcebergTable.java
0
1
00.00%
[107]

:large_blue_circle:
com/starrocks/catalog/MaterializedView.java
28
61
45.90%
[81, 82, 83, 84, 85, 86, 89, 90, 92, 97, 98, 100, 105, 109, 113, 117, 132, 137, 138, 139, 141, 149, 377, 445, 446, 448, 449, 450, 452, 453, 460, 464, 465]

:large_blue_circle:
com/starrocks/catalog/HudiTable.java
1
2
50.00%
[171]

:large_blue_circle:
com/starrocks/catalog/HiveTable.java
1
2
50.00%
[176]

:large_blue_circle:
com/starrocks/sql/analyzer/MaterializedViewAnalyzer.java
12
17
70.59%
[131, 132, 133, 145, 146]

:large_blue_circle:
com/starrocks/scheduler/PartitionBasedMaterializedViewRefreshProcessor.java
65
79
82.28%
[320, 336, 401, 460, 465, 474, 531, 532, 533, 538, 539, 540, 548, 552]

:large_blue_circle:
com/starrocks/catalog/Table.java
7
8
87.50%
[174]

:large_blue_circle:
com/starrocks/sql/ast/CreateMaterializedViewStatement.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/server/LocalMetastore.java
5
5
100.00%
[]

run starrocks_admit_test


Make default price in USD and make the price in 48px font

It took drunken Ben way too long to work out how much the service cost. I'm not saying I would've signed up, but still...

Why make the default price in USD?

Actually, don't worry, I can guess why you think that. nm.


chore: publish stylelint-copyright again

Motivation
Not sure to remember why exactly (was related to canary releases and Docusaurus v1) but publish of stylelint-copyright has been disabled
I guess we can safely re-enable it now that v1 is not part of the main branch anymore? 🤷♂
Have you read the Contributing Guidelines on pull requests?
yes
Test Plan
CI

lerna ERR! E403 You do not have permission to publish "stylelint-copyright". Are you logged in as the correct user?

I think I fixed the npm permission so it should work on next run 🤷♂

@Josh-Cena published manually 2.0.0-beta.17


Removed overloading of INSTALL_NAME_DIR with ${CMAKE_INSTALL_LIBDIR} …

Hi. I don't quite understand why this was done in the first place, but it prevents users from specifying CMAKE_INSTALL_NAME_DIR. In particular it breaks linking against libglfw when (for exmaple) in tracy (https://bitbucket.org/wolfpld/tracy/src) when built using pkgsrc framework that relies on being able to pass CMAKE_INSTAL_NAME_DIR (see https://github.com/jsonn/pkgsrc/blob/trunk/mk/configure/cmake.mk, line 46).
Removing those lines make everything work as expected.

Hi, thanks for your PR, but this work change is a duplicate of #1504.


List view

Hi, thanks in advance.
I need a better list view, like the other Windows files.

Merging with #2509.

@sergiosgAGP thank you for your patience, I'm excited to share that a List View layout will be included in the next release.


unix: set sin_len and sin6_len

FreeBSD defines sin_len and sin6_len inside sockaddr_in and
sockaddr_in6. sockaddrs come from getsockname and uv_ip4_addr
will differ in the first byte if libuv doesn't set sin_len correctly.
Refs:

https://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/sockets-essential-functions.html
https://github.com/nodejs/quic/pull/135

Using SIN_LEN6 also for ipv4 now. PTAL.

CI: https://ci.nodejs.org/view/libuv/job/libuv-test-commit/1587/

Doh, I forgot to read the note, disregard my questions :-)

Landed in 645be48a, thank you!


Use kebab-case in config files

Fixes https://github.com/PlasmaFAIR/fortitude/issues/118 (though please confirm before merging!).
We're using a macro library https://github.com/gibfahn/clap_config to automatically generate the config file parser from the CLI args, but while Clap prefers kebab-case for CLI args, this library converts them to snake-case. This PR brings a modified version of that macro into Fortitude, and changes the serialisation to kebab-case. It's licensed under MIT, so as far as I know there shouldn't be any licensing issues. We could continue to build on this macro going forward, or may instead opt to use a more complicated setup that allows for different arguments in the config file versus the command line.

Something I forgot to check before raising this PR: It still doesn't catch unknown args in the config file, so while line-length is now successfully picked up, line_length is now quietly ignored, which isn't ideal.

Currently struggling to figure out why #[serde(deny_unknown_fields)] isn't working in this case, and I can't see where to add any checks to the macro.

Another point against this solution: with #[serde(deny_unknown_fields)], any error in the TOML file results in every field being ignored. I think now might be a good time to come up with a more robust solution!


[Workflow] Examples do not work due to alpha -> beta changes

See the search results for references of v1.0-alpha
https://github.com/search?q=repo%3Adapr%2Fdotnet-sdk+v1.0-alpha1&type=code
These alpha APIs no longer exist and need uplifting to be inline with https://docs.dapr.io/reference/api/workflow_api/
This is causing problems for adopters which has surfaced via Discord

/assign

Fixed with #1194


Ability to upload JS files for extensions/plugins

See also #73 and #60
See https://scratch.mit.edu/users/Sheep_maker/#comments-142357006

also we should be able to download extensions and plugins for the offline editor, and be able to upload them to the htmlifyer

Hmm, it expects a URL to load from; should it just use a data URL?


Incompletable Adventure Seed

Seed URL
https://a.sotn.io/?a36,culexplz
Randomizer version:
3.0.26
Spoilers:
Soul of Bat at Echo of Bat
Fire of Bat at Knight shield
Echo of Bat at Talisman
Force of Echo at Ring of Ares
Soul of Wolf at Holy glasses
Power of Wolf at Royal cloak
Skill of Wolf at Goggles
Form of Mist at Beryl circlet
Power of Mist at Ankh of Life
Gas Cloud at Trio
Cube of Zoe at Icebrand
Spirit Orb at Walk armor
Gravity Boots at Shield Rod
Leap Stone at Form of Mist
Holy Symbol at Holy Symbol
Faerie Scroll at Demon Card
Jewel of Open at Sunstone
Merman Statue at Leap Stone
Bat Card at Sunglasses
Ghost Card at Spike Breaker
Faerie Card at Fire of Bat
Demon Card at Reverse Caverns Garnet
Sword Card at Mormegil
Sprite Card at Gladius
Nosedevil Card at Gold plate
Heart of Vlad at Sword of Hador
Tooth of Vlad at Gram
Rib of Vlad at Mystic pendant
Ring of Vlad at Alucard mail
Eye of Vlad at Twilight cloak
Spike Breaker at Fury plate
Onyx at Cloth cape
Zircon at Alucart sword
Cat-eye circl. at Blood cloak

I think this is due to a typo causing Shield rod location to be a 0-relic check. Should be fixed in 3.0.27.


feat(testing): testing ci fixes

Welcome to Cryostat! 👋
Before contributing, make sure you have:

[ ] Read the contributing guidelines
[ ] Linked a relevant issue which this PR resolves
[ ] Linked any other relevant issues, PR's, or documentation, if any
[ ] Resolved all conflicts, if any
[ ] Rebased your branch PR on top of the latest upstream main branch
[ ] Attached at least one of the following labels to the PR: [chore, ci, docs, feat, fix, test]
[ ] Signed all commits: git commit -S -m "YOUR_COMMIT_MESSAGE"

Fixes: #1
Description of the change:
This change adds allows the users to provide...
Motivation for the change:
This change is helpful because users may want to...
How to manually test:

Insert steps here...
...

Meant to test on fork :))


[Wave 6: Drafts] Update the OpenReport to start fetching the next steps for the expense reports

Part of https://github.com/Expensify/Expensify/issues/308213
Coming from the Doc here, we need to start returning the next steps for expense reports in the OpenReport api command

This can be closed now I think


Feature: Add graphviz

[x] I have read the CONTRIBUTING guidelines
[ ] I've had a conversation on the #cli-development Slack channel about this request.

I can't seem to access the slack channel.  The email I receive says the following:
It looks like there isn’t an account on SDKMAN! tied to this email address.

Feature request

schemacrawler has a secondary requirement for graphing to use graphviz.  wondering if that would be easy to add to sdkman

Hi @kansasSamurai, sorry, but we've moved to Discord. I must have forgotten about this template, so I'll update it accordingly.
Graphviz isn't a JVM SDK, so unfortunately, we can't include it on SDKMAN. We only allow SDKs that form part of the JVM ecosystem (requires a JRE/JDK to run). I suggest installing Graphviz through your system's package manager.

Thanks for doing the leg work.  I just assumed it was a jvm based tool since schemacrawler used it.  Will close the request, thanks.


add client flag to specify if messages are text only

This PR adds an option to specify if your messages are text only. This is useful because some text-only models like DeepSeek expect messages with the following format:
{"role": "user", "content": "some message"}

Currently cosette only generates messages with the format below which throws an error when calling the  DeepSeek API. This isn't unique to DeepSeek. The same error occurs with models hosted by other providers like Groq.
{"role": "user", "content": [{"type": "text", "text": "some message"}]}

This looks like pretty much the same format as claudette. Could you see if you can pull some of that functionality out into some shared utilities or base class or something?

This looks like pretty much the same format as claudette. Could you see if you can pull some of that functionality out into some shared utilities or base class or something?

To complete the conversation, this comment led to the creation of the msglm package which was added to cosette in #7.

@jph00 this PR is ready for review when you get a chance.

Coming back to the original question -- do we really need text_only? What if instead we automatically created the text only form when there's only a text message?

@jph00 how would we like mk_msg handle a list of strings? For example
[
	"What is the capital of France?",
	"What is the capital of Spain?",
	"Only include the cities in your response."
]

There are at least 4 options:

1. Concatenate
Concatenate the list into a single string and create one message.
    {
    	"role": "user",
    	"content": "What is the capital of France? What is the capital of Spain? Only include the cities in your response."
    }

If we select this option, what would be a sensible delimiter? Just a space? Perhaps we could create a messages xml like this?
    <messages>
      <message>"What is the capital of France?"</message>
      <message>"What is the capital of Spain?"</message>
      <message>"Only include the cities in your response."</message>
    </messages>

Or maybe allow the user to provide a custom delimiter or formatting function?

2. Separate Messages
Create a separate message for each item in the list.
    [
    	{"role": "user", "content": "What is the capital of France?"},
    	{"role": "user", "content": "What is the capital of Spain?"},
    	{"role": "user", "content": "Only include the cities in your response."},
    ]

The main downside of this approach is that it breaks the alternating user/assistant paradigm.

3. Content List
Create a content list with types. This will work for multimodal models but text_only models will throw an error.
{
   "role": "user",
   "content": [
        {"type": "text", "content": "What is the capital of France?"},
        {"type": "text", "content": "What is the capital of Spain?"},
        {"type": "text", "content": "Only include the cities in your response"}
  ]
}

 4. Raise Error
Don't allow lists of text under any circumstances and raise an error.

I'm leaning towards option 1 with a maybe a single space delimiter? wdyt?

Closing this PR as msglm now uses the simpler text format by default which means we no longer need the text_only flag in cosette.

@jph00 how would we like mk_msg to handle a list of strings? For example
[
  "What is the capital of France?",
  "What is the capital of Spain?",
  "Only include the cities in your response."
]

There are at least 4 options:

Concatenate
Separate Messages
Content List
Raise Error
I'm leaning towards option 1 with a single space delimiter? wdyt?

From an offline discussion, we opted to use the simpler format when the content is a string or a list comprised of a single string item. In all other cases the more detailed data structure will be used. This behaviour has been added to msglm.

Closing this PR as it is no longer needed. msglm has been updated to use the simpler text format be default so we don't need this text_only flag in cosette.


Explicitly set constructor binding should stop convention from running

    public class Project
    {
        public Project(string name, int anotherProp)
        {
            Name = name;
            AnotherProp = anotherProp;
        }

        public Project(string name, string lastname)
        {
            Name = name;
            Lastname = lastname;
        }

        public Project(string name, string lastname, int anotherProp)
            : this(name, lastname)
        {
            AnotherProp = anotherProp;
        }

        public Guid Id { get; set; }
        public string Name { get; set; }
        public string Lastname { get; set; }
        public int AnotherProp { get; set;  }
    }

        protected override void OnModelCreating(ModelBuilder modelBuilder)
        {
            // Configure model
            modelBuilder.Entity<Project>(e =>
            {
                e.Property(p => p.Name).UsePropertyAccessMode(PropertyAccessMode.FieldDuringConstruction);
                e.Property(p => p.AnotherProp).UsePropertyAccessMode(PropertyAccessMode.FieldDuringConstruction);
                e.Property(p => p.Lastname).UsePropertyAccessMode(PropertyAccessMode.FieldDuringConstruction);
            });
        }

Unhandled Exception: System.InvalidOperationException: Two constructors were found with the same number of parameters that could both be used by Entity Framework. The constructor to use must be configured explicitly. The two constructors are 'Project(string, int)' and 'Project(string, string)'.
   at Microsoft.EntityFrameworkCore.Metadata.Conventions.Internal.ConstructorBindingConvention.Apply(InternalModelBuilder modelBuilder)
   at Microsoft.EntityFrameworkCore.Metadata.Conventions.Internal.ConventionDispatcher.ImmediateConventionScope.OnModelBuilt(InternalModelBuilder modelBuilder)
   at Microsoft.EntityFrameworkCore.ModelBuilder.FinalizeModel()
   at System.Lazy`1.ViaFactory(LazyThreadSafetyMode mode)
   at System.Lazy`1.ExecutionAndPublication(LazyHelper executionAndPublication, Boolean useDefaultConstructor)
   at System.Lazy`1.CreateValue()
   at Microsoft.EntityFrameworkCore.Internal.DbContextServices.CreateModel()
   at Microsoft.EntityFrameworkCore.Internal.DbContextServices.get_Model()
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScoped(ScopedCallSite scopedCallSite, ServiceProviderEngineScope scope)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, ServiceProviderEngineScope scope)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScoped(ScopedCallSite scopedCallSite, ServiceProviderEngineScope scope)
   at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService(IServiceProvider provider, Type serviceType)
   at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService[T](IServiceProvider provider)
   at Microsoft.EntityFrameworkCore.DbContext.get_DbContextDependencies()
   at Microsoft.EntityFrameworkCore.DbContext.get_InternalServiceProvider()
   at Microsoft.EntityFrameworkCore.Internal.InternalAccessorExtensions.GetService[TService](IInfrastructure`1 accessor)
   at Microsoft.EntityFrameworkCore.Infrastructure.DatabaseFacade.get_DatabaseCreator()
   at Microsoft.EntityFrameworkCore.Infrastructure.DatabaseFacade.EnsureDeleted()
   at EFSampleApp.Program.Main(String[] args) in D:\code\EFSampleApp\EFSampleApp\Program.cs:line 15

EF Core version: 2.2.0-rtm-35637

This is currently by-design per: #10852, but also see #10865.
The constructor binding can be set explicitly using internal code.

Warning: internal code should be used with caution, since it may be changed or removed in a breaking way in any new release.

modelBuilder.Entity<Project>(e =>
{
    var nameProperty = e.Property(p => p.Name).Metadata;
    var anotherProperty = e.Property(p => p.AnotherProp).Metadata;
    var lastNameProperty = e.Property(p => p.Lastname).Metadata;

    e.Metadata[CoreAnnotationNames.ConstructorBinding]
        = new DirectConstructorBinding(
            typeof(Project).GetConstructor(new [] { typeof(string), typeof(string), typeof(int) }),
            new []
            {
                new PropertyParameterBinding(nameProperty),
                new PropertyParameterBinding(lastNameProperty),
                new PropertyParameterBinding(anotherProperty),
            });
});

However, I found while working on this that the convention still runs and throws even though its result would not be used--this is a bug. I was able to workaround this by adding a private parameterless constrctor to the entity type:
public class Project
{
    private Project()
    {
    }

    ...
}

This allows the convention to succeed, with the result being that the explicitly configured constructor is used.

Hi All
There is any update about when this bug will be fixed?
Thanks a lot in advance.

@ahedreville Currently planned for the 3.0 release; that's why the issue is in the "3.0" milestone.


[BUG] Can't login Kiali after update rancher-istio:103.1.0+up1.19.6

Rancher Server Setup

Rancher version: v2.8.2
Installation option (Docker install/Helm Chart): Helm Chart

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): k3s

Proxy/Cert Details:

Information about the Cluster

Kubernetes version: v1.27.11 +k3s1
Cluster Type (Local/Downstream): Downstream

If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider): Imported

User Information

What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom)

If custom, define the set of permissions:
Admin

Describe the bug

After update rancher-istio:103.1.0+up1.19.6 from rancher-istio:103.0.0+up1.18.2, I can't auto-login kiali via rancher gui, it needs token.
To Reproduce

update rancher-istio:103.1.0+up1.19.6
click istio->kiali

Result
Expected Result

I can auto-login kiali via rancher gui
Screenshots

Additional context

Same issue with Rancher v2.8.2, v1.27.11+rke2r1, rancher-istio:103.1.0+up1.19.6

I found a workaround for this situation. Just get the Kubernetes token by typing:
kubectl -n istio-system create token kiali

Ref:  https://kiali.io/docs/faq/authentication/

If you are only accessing it through the Rancher UI you can set the kiali auth strategy to be anonymous in the helm chart values to bypass the need to generate a token every time you access it:
kiali:
  auth:
    strategy: anonymous

I think this should be okay since access to the Kiali dashboard is limited to cluster administrators by default. Unsure if this setting may change that behaviour though. This likely isn't very secure though and shouldn't really be an accepted solution but saves you having to generate a token every time you want to access it.


remove scorehud

remove scorehud after end game and back to lobby

Create a new issue with a more details.


Final config

After this is implemented, please close #5, #10, #13 and #22.

2 general advices:

Try to create small commits, even tiny ones (at least until you push for review) - treat them as building blocks for your PR.
Use git rebase -i HEAD~NN frequently and get comfortable with that tool. With tiny blocks/commits you can rearrange your building/PR easily with e.g. fixup (correct and commit each problem separately at the end of the branch and then fix to different points in your branch) or squash (commit each file/class/function/code block separately and then squash if they are functionally/logically related).
Run CI jobs locally to solve problems as soon as possible. With small commits, comfort in using rebase command and utilizing developer scripts you can easily run each CI test on your dev environment. A good practice would be e.g.

(before commit or during rebase)
1. make some changes
2. ./tools/prep_test.sh
3. pylint + pytest -> make corrections -> pylint + pytest
4. ./tools/prep_commit.sh
5a. git commit
5b. git add && git rebase --continue

Follow up in #41 and #51.


Init proj DayOfWeek

Git
Screen

11.06.2020 / 13.06.2020
Norm

incorrect label, need to use another
incorrect commit format, should be repeated in the next lesson (remind me)
need screenshots of the program, not a code


Header templates

I'm thinking a way to define header templates would be nesting a header tag in the column attribute like this: http://www.screencast.com/t/6AA4MlbNd
Currently only way to do this is annoying via the column template callback.
Any thoughts?

done in 0.4.0!


Angular momentum ints and magnetic dipoles

Description
Add optional for attaching angular momentum integrals and computing magnetic dipoles.
Todos
Notable points that this PR has either accomplished or will accomplish.

[x] Add angular momentum ints
[x] Add magnetic dipoles
[ ] Add test case

Status

[ ] Ready to go

Codecov Report

Merging #3 (63b4525) into main (225abd2) will decrease coverage by 0.49%.
The diff coverage is 64.28%.

:exclamation: Current head 63b4525 differs from pull request most recent head 4f43799. Consider uploading reports for the commit 4f43799 to get more accurate results


Airflow use Problem

Airflow_install_airflow -webserver_1 docker user password, I installed hive plugin in there without GCC, install GCC without permission

Hi there ! I'm going to redirect you to the Airflow Issues to report this. We typically don't handle these type of issues :)

thank you


Use repo1.maven.org/maven2 instead of default apache central url

fix #8153
repo.maven.apache.org is unstable right now.
change the default to repo1.maven.org/maven2

build

all external mvn commands pass as expected


Feature/issue 1457 boost 1.58

Summary:
Update Stan to use Boost 1.58.
Intended Effect:
Allow use of RStan with the latest release of R package BH (Boost headers), which is Boost 1.58.
How to Verify:
Run tests.
Note the updated Wishart RNG tests that now include a seed.  They weren't passing by a small numerical margin, but look to be OK.
Side Effects:
Will no longer run with Boost versions lower than 1.56
Documentation:
Nothing user facing. (the license doc in the language manual no longer mentions versions)
Reviewer Suggestions:
Anyone.

Hint:  other than Wishart tests, the changes are all in lang/grammars/*_def.hpp and are all the same

This is a FAIL for me too on Linux
src/test/unit/io/dump_test.cpp:73: Failure

I'm trying to get a patch for Boost 1.58 ASAP so that
we can upgrade RStan so that everyone's installs will start
working again.  This is my only priority at the moment and
I've spent the better part of three days on this already.
The last commit but one worked on Mac.  The most recent
commit breaks everything and needs to be backed out --- I
inadvertently brought in a C++11 dependency for expm1.
Windows is still broken.
Linux is uncertain.
So far, I've fixed the semantic actions in the parser due
to changes in Boost's lazy evaluation, fixed the dump parser
due to changes in Boost's underflow exception handling just on
Windows, and now need to figure out why Boost's expm1() is
failing on Windows --- I think it's boundary conditions
again on overflow/underflow, which we're carefully testing
and hence failing on when things change.

Bob

On May 28, 2015, at 2:13 AM, Stan buildbot<EMAIL_ADDRESS>wrote:
Refer to this link for build results (access rights to CI server needed):
http://d1m1s1b1.stat.columbia.edu:8080/job/Stan Pull Request/391/
Build Log
last 20 lines
[...truncated 11 lines...]

/usr/local/git/bin/git rev-parse refs/remotes/origin/origin/pr/1460/merge^{commit} # timeout=10
Checking out Revision 839dc712f326e12a3a635e8984d6cc649317c5f4 (refs/remotes/origin/pr/1460/merge)
/usr/local/git/bin/git config core.sparsecheckout # timeout=10
/usr/local/git/bin/git checkout -f 839dc712f326e12a3a635e8984d6cc649317c5f4
First time build. Skipping changelog.
Starting build job Stan Pull Request - Doc - Doxygen.
Starting build job Stan Pull Request - Doc - Reference Manual.
Finished Build : #391 of Job : Stan Pull Request - Doc - Doxygen with status : SUCCESS
Finished Build : #385 of Job : Stan Pull Request - Doc - Reference Manual with status : SUCCESS
Starting build job Stan Pull Request - Tests - Header.
Starting build job Stan Pull Request - Tests - Integration.
Starting build job Stan Pull Request - Windows - Tests - Unit.
Starting build job Stan Pull Request - Tests - Unit.
Finished Build : #206 of Job : Stan Pull Request - Windows - Tests - Unit with status : FAILURE
Finished Build : #357 of Job : Stan Pull Request - Tests - Header with status : ABORTED
Finished Build : #359 of Job : Stan Pull Request - Tests - Integration with status : ABORTED
Finished Build : #359 of Job : Stan Pull Request - Tests - Unit with status : ABORTED
Build step 'MultiJob Phase' marked build as failure
Setting status of d352ef6666ed5af0df634e05b5f8603a3ebc8675 to FAILURE with url http://d1m1s1b1.stat.columbia.edu:8080/job/Stan Pull Request/391/ and message: Build finished.

Test FAILed.
—
Reply to this email directly or view it on GitHub.

The expm1 error is happening on Linux when C++11=false. If true, it seems
to be okay.

Ben, how do I turn off C++11 in clang++? I've searched for the flag for the
last hour and I can't find it.
On Thu, May 28, 2015 at 3:53 AM, bgoodri<EMAIL_ADDRESS>wrote:

The expm1 error is happening on Linux when C++11=false. If true, it seems
to be okay.
—
Reply to this email directly or view it on GitHub
https://github.com/stan-dev/stan/pull/1460#issuecomment-106219115.

Is C++11 the default for clang++ on a Mac these days? If so, you would
probably have to put -std=g++99 or something into make/os_mac.
On Thu, May 28, 2015 at 9:38 AM, Daniel Lee<EMAIL_ADDRESS>wrote:

Ben, how do I turn off C++11 in clang++? I've searched for the flag for the
last hour and I can't find it.
On Thu, May 28, 2015 at 3:53 AM, bgoodri<EMAIL_ADDRESS>wrote:

The expm1 error is happening on Linux when C++11=false. If true, it seems
to be okay.
—
Reply to this email directly or view it on GitHub
https://github.com/stan-dev/stan/pull/1460#issuecomment-106219115.

—
Reply to this email directly or view it on GitHub
https://github.com/stan-dev/stan/pull/1460#issuecomment-106313682.

I can't get the -std flag to prevent C++11 features. I've tried all the
standards I can find, which is really tough to do, btw:
http://stackoverflow.com/questions/21870283/how-to-get-list-of-supported-standards-in-clang
On Thu, May 28, 2015 at 10:17 AM, bgoodri<EMAIL_ADDRESS>wrote:

Is C++11 the default for clang++ on a Mac these days? If so, you would
probably have to put -std=g++99 or something into make/os_mac.

Do you know of any other flags that will force clang++ to fail to compile
if C++11 is used?
On Thu, May 28, 2015 at 11:36 AM, Daniel Lee<EMAIL_ADDRESS>wrote:

I can't get the -std flag to prevent C++11 features. I've tried all the
standards I can find, which is really tough to do, btw:
http://stackoverflow.com/questions/21870283/how-to-get-list-of-supported-standards-in-clang
On Thu, May 28, 2015 at 10:17 AM, bgoodri<EMAIL_ADDRESS>wrote:

Is C++11 the default for clang++ on a Mac these days? If so, you would
probably have to put -std=g++99 or something into make/os_mac.

Which feature are you trying to remove?  Remember that there
is the standard (-std) and then the standard library (-stdlib).
Even if you force, say, -std=c++03, you might still call the
implementations in the newer standard library.
On May 28, 2015, at 4:38 PM, Daniel Lee<EMAIL_ADDRESS>wrote:

Do you know of any other flags that will force clang++ to fail to compile
if C++11 is used?
On Thu, May 28, 2015 at 11:36 AM, Daniel Lee<EMAIL_ADDRESS>wrote:

I can't get the -std flag to prevent C++11 features. I've tried all the
standards I can find, which is really tough to do, btw:
http://stackoverflow.com/questions/21870283/how-to-get-list-of-supported-standards-in-clang
On Thu, May 28, 2015 at 10:17 AM, bgoodri<EMAIL_ADDRESS>wrote:

Is C++11 the default for clang++ on a Mac these days? If so, you would
probably have to put -std=g++99 or something into make/os_mac.

�
Reply to this email directly or view it on GitHub.

I'm trying to compile with strict C++98 compliance. Windows doesn't have
std::expm1, that's been introduced as of C++11. It's a lot easier testing
locally than it is getting to the Windows machine and back for compliance.
On Thu, May 28, 2015 at 12:01 PM, Michael Betancourt <
<EMAIL_ADDRESS>wrote:

Which feature are you trying to remove? Remember that there
is the standard (-std) and then the standard library (-stdlib).
Even if you force, say, -std=c++03, you might still call the
implementations in the newer standard library.
On May 28, 2015, at 4:38 PM, Daniel Lee<EMAIL_ADDRESS>wrote:

Do you know of any other flags that will force clang++ to fail to compile
if C++11 is used?
On Thu, May 28, 2015 at 11:36 AM, Daniel Lee<EMAIL_ADDRESS>wrote:

I can't get the -std flag to prevent C++11 features. I've tried all the
standards I can find, which is really tough to do, btw:

http://stackoverflow.com/questions/21870283/how-to-get-list-of-supported-standards-in-clang

On Thu, May 28, 2015 at 10:17 AM, bgoodri<EMAIL_ADDRESS>wrote:

Is C++11 the default for clang++ on a Mac these days? If so, you would
probably have to put -std=g++99 or something into make/os_mac.

�
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub
https://github.com/stan-dev/stan/pull/1460#issuecomment-106444706.

Have you tried forcing the older standard library implementation, -stdlib=libstdc++?
On May 28, 2015, at 5:04 PM, Daniel Lee<EMAIL_ADDRESS>wrote:

I'm trying to compile with strict C++98 compliance. Windows doesn't have
std::expm1, that's been introduced as of C++11. It's a lot easier testing
locally than it is getting to the Windows machine and back for compliance.
On Thu, May 28, 2015 at 12:01 PM, Michael Betancourt <
<EMAIL_ADDRESS>wrote:

Which feature are you trying to remove? Remember that there
is the standard (-std) and then the standard library (-stdlib).
Even if you force, say, -std=c++03, you might still call the
implementations in the newer standard library.
On May 28, 2015, at 4:38 PM, Daniel Lee<EMAIL_ADDRESS>wrote:

Do you know of any other flags that will force clang++ to fail to compile
if C++11 is used?
On Thu, May 28, 2015 at 11:36 AM, Daniel Lee<EMAIL_ADDRESS>wrote:

I can't get the -std flag to prevent C++11 features. I've tried all the
standards I can find, which is really tough to do, btw:

http://stackoverflow.com/questions/21870283/how-to-get-list-of-supported-standards-in-clang

On Thu, May 28, 2015 at 10:17 AM, bgoodri<EMAIL_ADDRESS>wrote:

Is C++11 the default for clang++ on a Mac these days? If so, you would
probably have to put -std=g++99 or something into make/os_mac.

�
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub
https://github.com/stan-dev/stan/pull/1460#issuecomment-106444706.

—
Reply to this email directly or view it on GitHub.

there's no -stdlib option specified in the compilation
On Thu, May 28, 2015 at 12:28 PM, Michael Betancourt <
<EMAIL_ADDRESS>wrote:

Have you tried forcing the older standard library implementation,
-stdlib=libstdc++?
On May 28, 2015, at 5:04 PM, Daniel Lee<EMAIL_ADDRESS>wrote:

I'm trying to compile with strict C++98 compliance. Windows doesn't have
std::expm1, that's been introduced as of C++11. It's a lot easier testing
locally than it is getting to the Windows machine and back for
compliance.
On Thu, May 28, 2015 at 12:01 PM, Michael Betancourt <
<EMAIL_ADDRESS>wrote:

Which feature are you trying to remove? Remember that there
is the standard (-std) and then the standard library (-stdlib).
Even if you force, say, -std=c++03, you might still call the
implementations in the newer standard library.
On May 28, 2015, at 4:38 PM, Daniel Lee<EMAIL_ADDRESS>wrote:

Do you know of any other flags that will force clang++ to fail to
compile
if C++11 is used?
On Thu, May 28, 2015 at 11:36 AM, Daniel Lee<EMAIL_ADDRESS>wrote:

I can't get the -std flag to prevent C++11 features. I've tried
all the
standards I can find, which is really tough to do, btw:

http://stackoverflow.com/questions/21870283/how-to-get-list-of-supported-standards-in-clang

On Thu, May 28, 2015 at 10:17 AM, bgoodri <
<EMAIL_ADDRESS>wrote:

Is C++11 the default for clang++ on a Mac these days? If so, you
would
probably have to put -std=g++99 or something into make/os_mac.

�
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub
https://github.com/stan-dev/stan/pull/1460#issuecomment-106444706.

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub
https://github.com/stan-dev/stan/pull/1460#issuecomment-106466169.

Sure, which should then resort to the default which will be -stdlib=libc++
on new versions of clang.  Explicitly setting -stdlib=libstdc++ should force
the compiler to link to the older (pre C++11) implementation of the
standard library that doesn’t include the C++11 functions.
On May 28, 2015, at 5:31 PM, Daniel Lee<EMAIL_ADDRESS>wrote:

there's no -stdlib option specified in the compilation
On Thu, May 28, 2015 at 12:28 PM, Michael Betancourt <
<EMAIL_ADDRESS>wrote:

Have you tried forcing the older standard library implementation,
-stdlib=libstdc++?
On May 28, 2015, at 5:04 PM, Daniel Lee<EMAIL_ADDRESS>wrote:

I'm trying to compile with strict C++98 compliance. Windows doesn't have
std::expm1, that's been introduced as of C++11. It's a lot easier testing
locally than it is getting to the Windows machine and back for
compliance.
On Thu, May 28, 2015 at 12:01 PM, Michael Betancourt <
<EMAIL_ADDRESS>wrote:

Which feature are you trying to remove? Remember that there
is the standard (-std) and then the standard library (-stdlib).
Even if you force, say, -std=c++03, you might still call the
implementations in the newer standard library.
On May 28, 2015, at 4:38 PM, Daniel Lee<EMAIL_ADDRESS>wrote:

Do you know of any other flags that will force clang++ to fail to
compile
if C++11 is used?
On Thu, May 28, 2015 at 11:36 AM, Daniel Lee<EMAIL_ADDRESS>wrote:

I can't get the -std flag to prevent C++11 features. I've tried
all the
standards I can find, which is really tough to do, btw:

http://stackoverflow.com/questions/21870283/how-to-get-list-of-supported-standards-in-clang

On Thu, May 28, 2015 at 10:17 AM, bgoodri <
<EMAIL_ADDRESS>wrote:

Is C++11 the default for clang++ on a Mac these days? If so, you
would
probably have to put -std=g++99 or something into make/os_mac.

�
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub
https://github.com/stan-dev/stan/pull/1460#issuecomment-106444706.

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub
https://github.com/stan-dev/stan/pull/1460#issuecomment-106466169.

—
Reply to this email directly or view it on GitHub.

Thanks, Bob. I walked through the changes and they look good. We'll merge once it passes tests.

This is fine. I fixed the performance test.
On Fri, May 29, 2015 at 12:52 AM, Stan buildbot<EMAIL_ADDRESS>wrote:

Refer to this link for build results (access rights to CI server needed):
http://d1m1s1b1.stat.columbia.edu:8080/job/Stan Pull Request/393/
Build Log
last 20 lines
[...truncated 20 lines...]
Starting build job Stan Pull Request - Tests - Header.
Starting build job Stan Pull Request - Tests - Integration.
Starting build job Stan Pull Request - Tests - Unit.
Starting build job Stan Pull Request - Windows - Tests - Unit.
Finished Build : #359 of Job : Stan Pull Request - Tests - Header with status : SUCCESS
Finished Build : #361 of Job : Stan Pull Request - Tests - Integration with status : SUCCESS
Finished Build : #208 of Job : Stan Pull Request - Windows - Tests - Unit with status : SUCCESS
Finished Build : #361 of Job : Stan Pull Request - Tests - Unit with status : SUCCESS
Starting build job Stan Pull Request - CppLint.
Starting build job Stan Pull Request - Math Dependencies.
Finished Build : #95 of Job : Stan Pull Request - Math Dependencies with status : SUCCESS
Finished Build : #136 of Job : Stan Pull Request - CppLint with status : SUCCESS
Starting build job Stan Pull Request - Performance.
Finished Build : #114 of Job : Stan Pull Request - Performance with status : FAILURE
Starting build job Stan Pull Request - Interface - CmdStan.
Finished Build : #97 of Job : Stan Pull Request - Interface - CmdStan with status : SUCCESS
Starting build job Stan Pull Request - Distribution Tests.
Finished Build : #213 of Job : Stan Pull Request - Distribution Tests with status : SUCCESS
Setting status of c4e127d4d40339c7d57a375dc3e7a530baccd2c5 to FAILURE with url http://d1m1s1b1.stat.columbia.edu:8080/job/Stan Pull Request/393/ and message: Build finished.
Test FAILed.
—
Reply to this email directly or view it on GitHub
https://github.com/stan-dev/stan/pull/1460#issuecomment-106684536.


Read-only / Unmanaged models

Problem

When dealing with databases that is managed by another service, we’d prefer to use prisma to treat some tables as a read only service.

Since prisma doesn’t have native view support, it’s currently impossible to treat views as read only models and manually manage the view creation and updates.

Suggested solution
It’d great prisma allows us to mark certain models as unmanaged / readonly with a “@@readonly” constraint

Views are now being implemented, so that use case is not relevant any more: https://github.com/prisma/prisma/issues/17335

Is there a way to mark a model as unmanaged by Prisma and use it as read-only?
I'm currently migrating off of a django-based backend to a TS+prisma based one.
Ideally I'd like to run them in tandem as we gradually migrate them over multiple releases.


check_rabbitmq_cluster thresholds should be inverted

Currently the warning and critical threshold trigger when the number of nodes is above the number set in the threshold. They should trigger when the number of nodes goes below the threshold.
# ./check_rabbitmq_cluster -w 2,2 -c 1,1
RABBITMQ_CLUSTER CRITICAL - nb_running_node CRITICAL (3) nb_running_disc_node CRITICAL (3), nb_running_ram_node OK (0)
# ./check_rabbitmq_cluster -w 4,4 -c 5,5
RABBITMQ_CLUSTER OK - nb_running_node OK (3) nb_running_disc_node OK (3) nb_running_ram_node OK (0)

Hi, after reading table 3 here https://nagios-plugins.org/doc/guidelines.html#THRESHOLDFORMAT it is clear why it behaves the way it does. And it also suggests how do it in a way it could be useful.
I cannot work with perl, and do not know if its possible in some more elegant way, but i assembled it to work:
REM: $critical = $critical{$metric} if (defined $critical{$metric} and $critical{$metric} ne -1);
ADD: $critical = '' . $critical{$metric} . ':' if (defined $critical{$metric} and $critical{$metric} ne -1);
And the same for warning


Fix link to sharing trial capacitues

Content had a { rather than a [ so link wasn't working

@mihart
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


Make sure rcore.o gets compiled in more situations

Currently doing the following:
make
touch rcore_desktop.c
make

Will not result in rcore.o getting compiled again, despite that rcore_desktop.c has changed
This commit resolves that
The one downside this has is that for example, when building for desktop, if rcore_web.c is modified, rcore.c will get compiled again, despite that its changes are not used in this situation - I think this is unimportant, though, as make clean would be required to switch between platforms anyway

Two legit question:

Shouldn't those get ifeq'd by PLATFORM_*?
Shouldn't the prereqs be on a single line?

they could be, but it's not necessary. I'm only adding them as prerequisites so that the makefile considers rcore.o outdated of the modification time of any of those files is newer than it.
it doesn't matter, the for example, the following are equivalent in make

game: graphics.o physics.o input.o
graphics.o: graphics.c
physics.o: physics.c
input.o: input.c

And:
game: graphics.o
game: physics.o
game: input.o
graphics.o: graphics.c
physics.o: physics.c
input.o: input.c

New prerequisites are appended to the previous prerequisites
Does that clear everything up?
@ubkp

Just to make it clear, the "downside" I talked about at the end of the PR comment is the consequence of not putting all the C files in the ifeq (PLATFORM_WHATEVER) ...
I don't deem it important enough to hinder the readability of the makefile, but perhaps ray thinks otherwise

@Peter0x44 Yup, thank you very much for the answers. :+1:

@Peter0x44 thanks for the review! Also a bit concerned about the different platforms, not sure if it could have any downside...

@raysan5 I don't believe this has any downsides
The only one which (might) be an issue is that the makefile will give an error if any of the prerequisites don't have a file that exists
Example:
example.o : nonexistent.c

make: *** No rule to make target 'nonexistent.c', needed by 'example.o'.  Stop.
However, this can be solved quite easily by simply adding a build rule that does nothing
example.o : nonexistent.c

nonexistent.c :

make: Nothing to be done for 'example.o'.
I'm happy to submit this change as a follow up if it's a desired behavior


Add EPyGrAM

Insert URLs to the project here: https://github.com/UMR-CNRM/EPyGrAM

[x] The projects is active, documented, open source licensed, shows usage from external parties and is directly targeting environmental sustainability. Find more details in the Contribution Guide.

All issues labeled as Good First Issue of the project listed on OpenSustain.tech will be visible on ClimateTriage.com. This is a great way to welcome new community members to your project.
All projects listed will be posted on our Mastodon channel

@AlexandreMary @SebastienRietteMTO


Allow HttpClientBuilder subclasses to customize the underlying builder

This change adds an overridable method which will allow io.dropwizard.client.HttpClientBuilder subclasses to customize the underlying org.apache.http.impl.client.HttpClientBuilder that is used. For example, this should allow the injection of HTTP client caching, as proposed in #1633.

Coverage increased (+0.005%) to 82.366% when pulling 102b7a3d152b92b1cf7aa8788c6f59915fc0801b on evnm:dropwizard-client/customizable-httpclientbuilder into de8c7e3b9e1b98dfd1a13c9ce562209cb4e6f5f1 on dropwizard:master.

Looks good to me, thanks for contributing!


Add files via upload

@H-Vkers First stage of verification passed, official domain is vtibrugge.be as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@H-Vkers Pull request merged. Thank you.


bump deps

/run-e2e internal

@JorTurFer @Eldarrin seems like there's some problem with the GitHub scaler. It keeps failing on the main branch, I try it in this PR and we can see that it fails.

/run-e2e github

spinning it up at home to check

It was a transient error deploying KEDA, not related with GH

It was a transient error deploying KEDA, not related with GH

hmmm, but that problem on main was there consistent. Sorry @Eldarrin for the confusion.

No problem


ir: Don't assume template instantiation argument with vtable implies vtable

Fixes #691

 Warning

These commits modify unsafe code. Please review it carefully!

r? @fitzgen

@bors-servo r+

:pushpin: Commit b40f9f0 has been approved by fitzgen

:hourglass: Testing commit b40f9f06dc543afaaba0fee60fb5c4feb2f3ecf0 with merge 2d88dd106bf33807679f531051546f3c9889161e...

:sunny: Test successful - status-travis
Approved by: fitzgen
Pushing 2d88dd106bf33807679f531051546f3c9889161e to master...


Add utility class for interacting with JMX

This is a utility class that's needed for testing CASSANDRA-8993, but should come in handy elsewhere.  It makes it quite easy to use JMX from within python.

oh, that's cool. I was currently doing  some work with metrics and was thinking about something like that. However, I was more thinking about the ability to tell CCM to record these metrics automatically. So maybe we could add that feature in ccm too based on this work. (not necessary now... just thinking out of loud)

@thobbs I don't know really these Java libs.... but is there any reason to use Jolokia instead of mx4j ? (just curious)

There are a couple of reasons I went with Jolokia over mx4j.  The first is that with mx4j, we'd need to get the jar into the classpath before starting Cassandra; that's a bit more complicated than simply attaching to a running process with Jolokia.  Second, the mx4j api is xml-centric, whereas Jolokia uses a pretty simple JSON api.
By the way, I tried integrating this into ccm before I opted for dtests.  The main problem that I ran into was around shipping the jar with the ccm package.  If ccm gets installed as an egg (preventable in some cases, but, for example, not preventable when you do python setup.py install, as far as I could tell), we'd have to handle reading from the zip and writing out to a separate file somewhere.  That was looking like a serious pain, and by comparison, using it from the dtests was much simpler.

I see. Thanks for the info. I'll review the PR later today.
On Mar 24, 2015 5:11 PM, "Tyler Hobbs"<EMAIL_ADDRESS>wrote:

There are a couple of reasons I went with Jolokia over mx4j. The first is
that with mx4j, we'd need to get the jar into the classpath before starting
Cassandra; that's a bit more complicated than simply attaching to a running
process with Jolokia. Second, the mx4j api is xml-centric, whereas Jolokia
uses a pretty simple JSON api.
By the way, I tried integrating this into ccm before I opted for dtests.
The main problem that I ran into was around shipping the jar with the ccm
package. If ccm gets installed as an egg (preventable in some cases, but,
for example, not preventable when you do python setup.py install, as far
as I could tell), we'd have to handle reading from the zip and writing out
to a separate file somewhere. That was looking like a serious pain, and by
comparison, using it from the dtests was much simpler.
—
Reply to this email directly or view it on GitHub
https://github.com/riptano/cassandra-dtest/pull/205#issuecomment-85692300
.

LGTM! Thanks!


Incompatibility with Iris

crash-2022-01-16_14.36.54-client.txt
Versioning Information
Minecraft version 1.18, Fabric 0.12.12, LED Version 1.2.0, Sodium Version 0.4.0.alpha6+build.14, Iris version 1.1.5, Indium version 1.0.2-alpha2.
Issue Description
LED seems to be incompatible with Iris. Removing either mod solves the crash.
Steps To Reproduce
Run game with Indium, Sodium, Iris, and LED installed. Crashes without going to loading screen.

Thanks for the report, I will look into this

LED internally uses JMX which uses FREX which is not compatible with other rendering systems than Canvas, so this is not resolvable
until now it thought that is worked if indium was used but this is sadly not the case, i will remove the note about indium from the CF page, thanks for bringing this to my attention


Webpack setup

We have to setup a webpack bundle, so it can be translated to older javascript and then we can use Imports instead of require.

Taking this one too.

https://github.com/LucasLeandro1204/Pornsearch/pull/10


Analyzer should always display the completition dropdown menu if the user is typing

This issue was originally filed by @Emasoft

Analyzer should always display the completition dropdown menu if the user is typing.
Currently there are big delays in the display of the completition dropdown menu because of the index that is currently updating. But the dropdown menu should always be displayed even if the index is under update. The partial completition dropdown should just display an "updating" message or animated icon to communicate its partial and "in progress" state to the user.
Also if a dropdown menu is shown too early, because the index is not being updated yet, the user receive an erroneus information about the current available members. Forcing him to press ctrl-space again and again after some intervals is NOT the correct way to handle this. The completition dropdown menu be updated in realtime and should display to the user the current state of the index update.
Otherwise it's just impossible for the user to know what is going on, and he ends thinking that if a method or a member is not listed it doesn't exist.
It should NEVER be necessary to press ctrl-space, for two reasons:
1 - Because if the user have no clue that a completition dropdown list is incomplete, he almost certainly don't know that he need to press ctrl-space a second time. He would just assume that the first completition list is complete and start coding accordingly.
2 - Because the autocompletition system objective is to allow a quicker typing, and forcing the user to stop the current word he is typing and change the hands position to press a key combination would invalidate the very reason d'etre of the autocompletition system, making it an hindrance instead of an help.
For this reasons the best way is to ALWAYS update the dropdown completition menu in realtime, while it is open floating above the word that is being typed. An animated icon and a message like "updating.." should be always visible at the bottom or at the top of the menu if the index is currently incomplete.
Also,for the same reasons mentioned, the dropdown completition menu should ALWAYS appear instantly while the user is typing, even if the index has not been updated yet or the list is still empty. In this way the feedback of the response will be fast and responsive, and at the same time the user will be able to know the current state of the indexing process. It should always be shown, even when we start typing an empty line. For example if I start typing "v", the menu should appear and "void" should be suggested together with all methods, keywords or classes beginning with v.
Always for the same reasons, the auto completition option for some very common code structures (like declaring a class, a method, writing a property getter/setter, adding a switch or a while or if loop) should not require the user to use some contextual menu, but they should be suggested as the first entries of the completition dropdown menu together with all the other entries. Many refactoring options can also be easily integrated in the same completition dropdown menu, avoiding to the user to stop his typing streak to search for some obscure menu option.
The slow performance of eclipse is already hindering the coding process. Anticipating the display of the completition options means anticipating the needs of the user, and consequently make the coding environment much more responsive than an environment that waits the user input to act.

This issue has been moved to dart-lang/eclipse3#39.


conformance: do not use (and mutate) DefaultClient

This is a global variable. Since we import the tests and then run other tests, this broke our other tests which depend on DefaultClient.
What type of PR is this?
/kind bug
What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Does this PR introduce a user-facing change?:

Thanks!
/lgtm


Disable warning C6326 (potential comparison of a constant) in recently added azure-core tests.

https://github.com/Azure/azure-sdk-for-cpp/pull/2089

Ah, you beat me to it :)
Do you mind updating the PR title of yours and also fix the comment typo?

/azp run cpp - core


Add Cova to CLI library list.

Commands, Options, Values, and Arguments by @00jciv00 will be Zig's flagship comptime CLI builder for years to come: https://github.com/00JCIV00/cova

Also, if you want to add it to this list, please submit a PR.

Zig's flagship comptime CLI builder

I wonder how you came to this conclusion...

For months now I've been working with the developer to enrich it's customizability and robustness, but from the beginning I could tell it was a well-made piece of software. That's my background on this.

Zig's flagship comptime CLI builder

I wonder how you came to this conclusion...

Hey, I think @p7r0x7 is being very gracious with their words here. They've been a great help in testing and coming up with ideas, and are deservedly passionate about the project. Ultimately Cova is a library that I've put a lot of effort into in hopes of making it as robust and easy to use as possible.
I didn't know about this list previous to this. It would be great if I can get Cova on here and if a PR is the right way of doing that, I'll proceed accordingly. Appreciate the guidance!

why not create a pull request ?

why not create a pull request ?

I was away for a bit. Just submitted a PR<PHONE_NUMBER>163eedd44a2331370b1c88539601af). Thank you!


Idea: RoPE position scaling to diagonally align text and speech

This is an idea from E1 TTS that I thought was an interesting alternative to the interpolated character embedding. Basically, rescale the RoPE sequence for speech by (n_text / n_speech), so text positions are monotonically increasing integers and speech positions are monotonically increasing fractions that are "diagonally aligned" to each other.
Note that they use a concatenated embedding in a single model, so the setup is a little different, but it could be worth a shot! The RotaryEmbedding here is the same as in x-transformers with the forward_from_seq_len_and_scale() method added.

Nm, I tried this and it seems worse. 😬

@lucasnewman haha, worth a shot!

think that idea is hard to apply here since the tokens overlap, but maybe if you separate the dimension into two spaces for audio vs text and then do learned token duration?
would take a ton of time and experiments to prove out

think that idea is hard to apply here since the tokens overlap, but maybe if you separate the dimension into two spaces for audio vs text and then do learned token duration?
would take a ton of time and experiments to prove out

Yeah, agree, not really worth the complexity vs. just having it align naturally, which it can do with enough compute.


Website responsiveness

@kevgo @charlierudolph
Responsiveness for the website.

:ship:

I can't believe you merged a PR here. This is the Git Town repo, you have to use Git Town's git ship here next time!  ;)


retroarch: detect api availability for snes

Fixes incompatibility between SNI and RA snes9x core, which doesn't support RA's READ_CORE_MEMORY.
I'll test this some more, but would like to have feedback/discussion on the approach (and code style, of course).
This also fixes the issue someone brought up recently in which SNI inconveniently displays a non-SNES RetroArch device when they wanted to connect to a different SNES emulator.

Force pushed to fix Printf at raclient.go:207

Force pushed to revert inadvertent spacing change in 5 unmodified lines in driver.go

Realized SNI READ_CORE_RAM implementation never knew about RAM @ 0, so added a third state in the latest commit:

RCR==false : use RCM
RCR==true && rcrHasBusMapping==true : old RCR has the semantics of modern RCM (to maintain compatibility with old versions of RA)
RCR==true && rcrHasBusMapping==false : RAM @ 0, SRAM @ 0x20000 (SRAM not available for SnesABus clients due to A-bus ambiguity with unknown mapping)

Changed 'Attach' command behavior so SNI no longer drops the connection if it can't access the ROM.
I do need to test this more.

2 issues with the current PR:

Transitioning between bsnes-mercury and snes9x (let's say with different roms) causes the wrong memory API to be used. I will try to fix this with polling and/or error self recovery to update the mapping and RA API in use.
.. * Also brought up with jsd that I hope there can be a 'rom change detection' feature in SNI since many clients want to be detecting it; moreover, the player switching between RA bsnes-mercury and RA snes9x cores presents both a) a more difficult, non-obvious client implementation for rom change detection, and b) new opportunities within SNI's own necessary detection to surface a known rom change error to the client.

It breaks ROM access in (HiROM and ExHiROM games, where SRAM size <=0x2000) for RA versions between 1.9.1 and 1.10.1. 'Secret of Evermore' and DKC3 are the only example games I know of with a client. All LoROM games, and all (Ex)HiROM games with >0x2000 bytes of SRAM, are already broken in terms of ROM or SRAM access support in those RA versions, so providing ROM+SRAM only, via RCR, per the pull request, is sufficient in that majority of games. (For posterity: the HiROM large SRAM bug was actually fixed in RA 1.10.3.) black-sliver, the owner of the SoE client, said they don't care if we drop ROM support (and thus AP SoE support) for that range of RA versions, though others might. DKC3 client came out after RA 1.10.1 with instructions to use at least 1.10.3. So in the PR I am tempted to continue de-supporting ROM access in these old-ish RA versions, unless, by fixing 1., it becomes convenient to do some HiROM-only RCM mappings to fix this. The test matrix is already becoming quite large for RA.

Definitely in favor of dropping support for RA versions before 1.10.1 or whatever the latest best is. If there is a valid reason to expend extra effort to make an older version work then that can be discussed when/if that ask comes up.

Im also tempted to clean things up in RA (via
PR) and return extra metadata like core name, system, rom file name, rom hash, etc with each command response. Probably a memory domain system would be great to have there too.


Min Admin Requirement - Projects, Events

Related to tickets, https://opencollective.freshdesk.com/a/tickets/180297 and https://opencollective.freshdesk.com/a/tickets/180037.
For projects and events the admins of the parent collective should be inherited. However when the host has the min admin requirement set even if the parent collective has the correct number of admins the child collectives show the banner incorrectly.
To Reproduce:

Go to host setttings -> policies and set the min admins to 2 and the freeze collective checkbox.

Go to a hosted collective and make sure to add two or more admins.

Create a new project or event.

Notice that the new project or event shows the banner (as shown below) even-though the event/project has the correct number of admins inherited by the parent collective.

Another one reported at, https://opencollective.freshdesk.com/a/tickets/181113


Make unique filenames for uploaded team images

Currently two teams uploading a "logo.jpg" file will overwrite each other.  We'll need to make sure filenames are unique.

For my own reference:
http://stackoverflow.com/questions/1190697/django-filefield-with-upload-to-determined-at-runtime

This has been merged and committed


TouchableOpacity loose context

[x] Review the documentation: https://facebook.github.io/react-native
[x] Search for existing issues: https://github.com/facebook/react-native/issues
[x] Use the latest React Native release: https://github.com/facebook/react-native/releases

Environment
React Native Environment Info:
    System:
      OS: macOS High Sierra 10.13.6
      CPU: x64 Intel(R) Core(TM) i7-3615QM CPU @ 2.30GHz
      Memory: 27.57 MB / 8.00 GB
      Shell: 5.3 - /bin/zsh
    Binaries:
      Node: 10.6.0 - ~/.nvm/versions/node/v10.6.0/bin/node
      Yarn: yarn install v0.20.3
[1/4] Resolving packages...
success Already up-to-date.
Done in 0.70s. - /usr/local/bin/yarn
      npm: 6.1.0 - ~/.nvm/versions/node/v10.6.0/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 11.4, macOS 10.13, tvOS 11.4, watchOS 4.3
      Android SDK:
        Build Tools: 23.0.1, 25.0.0, 25.0.1, 26.0.1, 26.0.2, 26.0.3, 27.0.3, 28.0.0
        API Levels: 21, 23, 25, 26, 27, 28
    IDEs:
      Android Studio: 3.1 AI-173.4819257
      Xcode: 9.4.1/9F2000 - /usr/bin/xcodebuild
    npmPackages:
      react: 16.4.1 => 16.4.1
      react-native: 0.56.0 => 0.56.0
    npmGlobalPackages:
      create-react-native-app: 1.0.0
      react-native-cli: 2.0.1

Description
There is an issue with TouchableOpacity.
This issue got only in app environment. When i create new clean project everything is ok.
Can you tell me where to look?

Reproducible Demo
https://github.com/Crysp/solver
Update
Add link to repo with reproducible error

Is there any way you can get this to reproduce on a brand new app? This is a minimum requirement as otherwise a contributor would have no way of testing a fix.

@hramos, Add link to repo with reproducible error

small correction. all projects in my env reproduce this issue


Github Oauth UserName Issues

Hello,
I have been wrestling with this for a while, and (in the absence of a Go environment) I cannot figure out from the Go code how GitHub Oauth picks up the username it is getting.  I am using auth_request and am getting back, instead of the login returned by GitHub's /user endpoint, the first portion of the email address.
The code here seems to very clearly show grabbing Login off of the /user endpoint:
https://github.com/bitly/oauth2_proxy/blob/b0c1c851770ec12b72e211e4c68c3dd37d5f9638/providers/github.go#L238-L279
The only caveat would be if the Session object already has a User defined, which does not seem to be case based on the GitHub documentation I have read.
https://github.com/bitly/oauth2_proxy/blob/a94b0a8b25e553f7333f7b84aeb89d9d18ec259b/oauthproxy.go#L248-L253
The only other possibility I could figure would be based on what is entered in the form, but that is the same as GitHub login.  Needless to say, I am lost, as the result I am getting back from the Oauth proxy is the following (where login is myuser, no period):
GET / HTTP/1.1
Connection: close
X-User: my.user
X-Email<EMAIL_ADDRESS>Host: oauth2-debug:8080

Reason: To do authorization within the app, I want to be able to reproduce the username values, and stripping the @... off of the email seems kinda ugly, not to mention impossible to do before the Oauth handshake has taken place (most emails are hidden on Github).
Related question - there are log.Printf statements in the code that are not being rendered to standard out.  Is there an option for increasing log verbosity?  I am happy to put in a PR for doc updates if there is an undocumented option for doing so - I couldn't find anything in the code, but again I am not a Go programmer. :)
Thanks!

Oh, and this is where the XAuthUser is set... which should be what I am picking up:
https://github.com/bitly/oauth2_proxy/blob/a94b0a8b25e553f7333f7b84aeb89d9d18ec259b/oauthproxy.go#L692-L697

The GitHub provider code you're looking at was merged after the v2.2 release of oauth2_proxy so you'll need to build the master branch from source.

Confirmed that this is the case! Building from source resolved. Thanks so much for the help!
If there are any options on log verbosity that are in the code but are not documented, please point me to them and I will be happy to make a PR documenting the options.


Provide a recipe for "graalvm"

Provide a recipe for GraalVM. Both the Oracle JDK and GraalVM are downloads from Oracle perhaps the Java recipe is a good source of inspiration for this.
Why would one want this?
GraalVM is the next great thing in JVM land and manual downloads from anything from the Oracle website involves manually agreeing to their license every single time and a sacrifice. Lots of kittens could be saved from having homebrew do this.

You asking for a formula, so this issue belongs in Homebrew/core.
But if I recall correctly, formula requests are not accepted, and if you want it you’ll need to at least try to make a pull request.

@vitorgalvao thanks for the clarification!


Black color wtch digit on 2.5.2 Ulanzi

Hi. Now upgrade Ulanzi 001 watch to 2.5.2. version. But I can't set any color for wach digit. When I change it to any color, it steel black after reboot.

I have the same problem

I have the same issue on my D1 mini version. It is always defaulting to color black and stays black. During boot I can see the Pixel IT logo and shortly the days "lines" at the bottom, so the LEDs are generally working.

Hello everyone,
i was able to recreate the error.
Can you please take a look at the clock color settings? Is the color code #000000 stored here?
If so, can you change this and see if the time is then given?
Greetings rliegmann

I tried this, but after the reboot it does on applying the settings, it will go back to black.

Please go back to 2.5.1. We check the reason at the moment.

Fixed with https://github.com/pixelit-project/PixelIt/releases/tag/2.5.2 (b96b63a46c339c9a9bfa2b0d64a3a4e9f74936ed)

Fixed with https://github.com/pixelit-project/PixelIt/releases/tag/2.5.2 (b96b63a)

Can confirm on my D1 mini 👍 thanks!


How to run the script?

Exactly how do you run it?  Directions are not even serious.  Where do you cut and paste, and how does youtube trigger the script?

https://github.com/Niedzwiedzw/youtube-publish-drafts/blob/60716b443ffc20b3d607d7680e94eceb80e47e7d/README.md?plain=1#L8 F12 opens browser's devtools. You go to console tab and paste it there. Documentation PRs are werlcome


Add  Data Structure & Algorithm's with Interview problems in JAVA

Is your feature request related to a problem? Please describe.
Alot of Newbies Like me we want better DSA & Algorithm in Java description with actual Relevant problems like on Leetcode hard/medium/easy solutions but there are very few shattered resources available I want them to be available in one single repository free for all
Describe the solution you'd like
I would love to provide freecodecamp my solutions in its repository for java DSA course with Leetcode solutions
1539. kth missing positive number

Describe alternatives you've considered
Anyone can add their questions of Leetcode into the repository like i added above as sample
Additional context
This is gonna a massive Resources & solution to learn DSA in Java quickly using theory less more solution & implementation with relevant FAANG interview Questions

Easy
Medium
Hard

freeCodeCamp aims to be self-sufficient, if you want to discuss this more I think contribution section in our discord is a good start.
P.s
Because you seem passion about helping, and I am worried that you may create steps on your own, I want to warn you about leetcode terms of services. It has this paragraph in it

You agree that all content is our sole and exclusive property. We may use all content for any purpose, including for commercial or promotional use without restriction or compensation to you. You agree not to copy, redistribute, publish or otherwise exploit any Content in violation of the intellectual property rights. You represent and warrant that any User Content that you submit, post or display through the Services does not infringe or violate any of the copyright, patent, trademark, trade name, trade secrets or any other personal or proprietary rights of any third party.

So be careful using their work.


[BEAM-4176] Tests for running Python on Flink.

This provides a fairly comprehensive tests of the basic runner compatibility expectations for Python on Flink. Surprisingly, the suite only takes a minute or so to run, so totally feasible to run on presubmit.
Copy of https://github.com/apache/beam/pull/5942
Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.


python310: 3.10.7 -> 3.10.8; python39: 3.9.14 -> 3.9.15

https://docs.python.org/release/3.10.8/whatsnew/changelog.html
https://docs.python.org/release/3.9.15/whatsnew/changelog.html
Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Darwin fails elsewhere. Passthru tests succeed on Linux.


[BUG] GpuSort fails on tables containing arrays.

On spark-rapids 0.6 + cudf-0.20, when GpuSort is called on a table containing arrays, one sees the following failure:
21/04/21 19:31:14 WARN TaskSetManager: Lost task 5.0 in stage 3.0 (TID 43, <IP_ADDRESS>, executor driver): ai.rapids.cudf.Cu
dfException: cuDF failure at: ../src/merge/merge.cu:246: Unsupported type for merge.
        at ai.rapids.cudf.Table.merge(Native Method)
        at ai.rapids.cudf.Table.merge(Table.java:1524)
        at com.nvidia.spark.rapids.GpuSorter.$anonfun$mergeSort$2(SortUtils.scala:204)
        at com.nvidia.spark.rapids.Arm.withResource(Arm.scala:55)
        at com.nvidia.spark.rapids.Arm.withResource$(Arm.scala:53)
        at com.nvidia.spark.rapids.GpuSorter.withResource(SortUtils.scala:65)
        at com.nvidia.spark.rapids.GpuSorter.$anonfun$mergeSort$1(SortUtils.scala:200)
        at com.nvidia.spark.rapids.Arm.withResource(Arm.scala:28)
        at com.nvidia.spark.rapids.Arm.withResource$(Arm.scala:26)
        at com.nvidia.spark.rapids.GpuSorter.withResource(SortUtils.scala:65)
        at com.nvidia.spark.rapids.GpuSorter.mergeSort(SortUtils.scala:196)
        at com.nvidia.spark.rapids.GpuOutOfCoreSortIterator.$anonfun$mergeSortEnoughToOutput$2(GpuSortExec.scala:407)
...

I haven't boiled it down yet, but I suspect that it's possible to reproduce this with a simpler case: On a large table containing an array column, run:
SELECT * FROM mytable ORDER BY non_array_column;

The following is a query where I see this occur:
val mybench = spark.read.parquet("/path/to/large.parquet")
mybench.createOrReplaceTempView("mytable")

val query = """
    SELECT uid,
           SUM(dollars)
               OVER ( PARTITION BY uid
                       ORDER BY cast(dateLong/1000 AS TIMESTAMP)
                       RANGE BETWEEN INTERVAL 14 DAYS PRECEDING AND CURRENT ROW) sum_dollars_14_days,
           COLLECT_LIST(dollars)
               OVER ( PARTITION BY uid
                       ORDER BY CAST(dateLong/1000 AS TIMESTAMP)
                       RANGE BETWEEN INTERVAL 14 DAYS PRECEDING AND CURRENT ROW) collect_dollars_14_days
    FROM mytable
"""

val top_earners_query = s"""
  SELECT uid, collect_dollars_14_days, sum_dollars_14_days FROM ($query) ORDER BY sum_dollars_14_days DESC
""

sql(top_earners_query).show

Data schema:
|col_name|data_type|comment|
+--------+---------+-------+
|     uid|   bigint|   null|
|   uname|   string|   null|
|dateLong|   bigint|   null|
|      dt|     date|   null|
| dateStr|   string|   null|
| dollars|      int|   null|
+--------+---------+-------+

I have now confirmed that this fails with rapids-4-spark*-0.5 + cudf-0.19, as well as rapids-4-spark*-0.6 + cudf-0.20.

From the error you posted it looks like the merge sort API is not happy with arrays. I know it cannot support them as a key, but just going along for the ride I thought it would, but I should have done better testing.  I am not sure how it is implemented internally, but in either case we should file an issue against cudf for this, and also verify that structs work for it too.
As a work around we can detect arrays in the table that we get to merge and switch to first concat the tables together and then sort them.  This is not going to be nearly as fast as merge is, but it will work in the short term.

I know it cannot support them as a key, but just going along for the ride I thought it would...

I found this surprising as well. A trivial/hasty test with a nested-type table and a primitive sort key didn't reproduce the problem when I tried it. I'll need to spend a little longer trying to boil this down.
(For the moment, the test above does repro this reliably.)

Small sorts will not work because you need to do a merge sort.  The simplest way to do that is like with the new test that I added in recently.
https://github.com/NVIDIA/spark-rapids/blob/6274fadf2393ebf7d47ead7e322e672776cbefc1/integration_tests/src/main/python/sort_test.py#L165-L173
You would need to modify it to include another column with the type you want to test.
Or you could do some unit tests for merge itself.

Thanks for closing this, @revans2. I just confirmed that #2251 does fix the issue.


Race condition between stopping and notifying operation completion listener

Expected Behavior
A build service may also be registered as a operation completion listener via BuildEventsListenerRegistry.onTaskCompletion(). Such listener should either be invoked even after the service is stopped (causing it to be reinstantiated), or not invoked at all.
Current Behavior
Right now, there is a race condition in which it is possible that a build service will be stopped while some other thread is trying to invoke onFinish() on the build service. The result is a NullPointerException like this:
java.lang.NullPointerException: Cannot invoke "org.gradle.internal.Try.get()" because "this.instance" is null
at org.gradle.api.services.internal.RegisteredBuildServiceProvider.getInstance(RegisteredBuildServiceProvider.java:121)
at org.gradle.api.services.internal.RegisteredBuildServiceProvider.calculateOwnValue(RegisteredBuildServiceProvider.java:111)
at org.gradle.api.internal.provider.AbstractMinimalProvider.calculateOwnPresentValue(AbstractMinimalProvider.java:73)
at org.gradle.api.internal.provider.AbstractMinimalProvider.get(AbstractMinimalProvider.java:93)
at org.gradle.internal.build.event.DefaultBuildEventsListenerRegistry$ForwardingBuildEventConsumer.handle(DefaultBuildEventsListenerRegistry.java:261)
at org.gradle.internal.build.event.DefaultBuildEventsListenerRegistry$ForwardingBuildEventConsumer.handle(DefaultBuildEventsListenerRegistry.java:238)
at org.gradle.internal.build.event.DefaultBuildEventsListenerRegistry$AbstractListener.run(DefaultBuildEventsListenerRegistry.java:180)
at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
at org.gradle.internal.concurrent.AbstractManagedExecutor$1.run(AbstractManagedExecutor.java:47)

Context (optional)
This method is not thread safe:
    private T getInstance() {
        listener.beforeGet(this);
        synchronized (this) {
            if (instance == null) {
                instance = instantiate();
            }
        }
        return instance.get();
    }

as we attempt to access a field that is mutated from different threads without synchronization.
Fixing the race condition so the NPE no longer happens would be easy, but it is unclear whether we would want the listener to be invoked while the service is stopped, have the service be reinstantiated, the listener not to be invoked at all, or something else.
Steps to Reproduce
This was spotted in Gradle's own builds:
https://ge.gradle.org/s/wiwsly5z2uwty/tests/:configuration-cache:embeddedIntegTest/org.gradle.configurationcache.ConfigurationCacheBuildServiceIntegrationTest/build service registered as listener in an included build with no work is not restored?expanded-stacktrace=WyIwIiwiMC0xLTIiXQ&top-execution=1
I was only able to reproduce it by tweaking the flaky test to run a thousand times (failed on attempt #684 for me, YMMV) :
---
Index: subprojects/configuration-cache/src/integTest/groovy/org/gradle/configurationcache/ConfigurationCacheBuildServiceIntegrationTest.groovy
===================================================================
diff --git a/subprojects/configuration-cache/src/integTest/groovy/org/gradle/configurationcache/ConfigurationCacheBuildServiceIntegrationTest.groovy b/subprojects/configuration-cache/src/integTest/groovy/org/gradle/configurationcache/ConfigurationCacheBuildServiceIntegrationTest.groovy
--- a/subprojects/configuration-cache/src/integTest/groovy/org/gradle/configurationcache/ConfigurationCacheBuildServiceIntegrationTest.groovy	(revision 9b74f67f363d2e5a25289f027afa222b869d645c)
+++ b/subprojects/configuration-cache/src/integTest/groovy/org/gradle/configurationcache/ConfigurationCacheBuildServiceIntegrationTest.groovy	(date<PHONE_NUMBER>787)
@@ -43,6 +43,7 @@
 import org.gradle.tooling.events.task.TaskFinishEvent
 import spock.lang.IgnoreIf
 import spock.lang.Issue
+import spock.lang.Unroll

 import javax.inject.Inject
 import java.util.concurrent.atomic.AtomicInteger
@@ -718,6 +719,7 @@
     }

     @Issue("https://github.com/gradle/gradle/issues/23700")
+    @Unroll("test repeated #i time")
     def "build service registered as listener in an included build with no work is not restored"() {
         def onFinishMessage = "You won't see me!"
         withListenerBuildServicePlugin onFinishMessage
@@ -756,5 +758,8 @@
         then:
         configurationCache.assertStateLoaded()
         outputDoesNotContain onFinishMessage
+
+        where:
+        i << (1..1000)
     }
 }

Not completely sure the use of included builds is required to recreate the issue.
Gradle version
8.1
Build scan URL (optional)
https://ge.gradle.org/scans/tests?search.timeZoneId=Europe/Berlin&tests.container=org.gradle.configurationcache.ConfigurationCacheBuildServiceIntegrationTest&tests.test=build service registered as listener in an included build with no work is not restored
Your Environment (optional)
No response

Another example is accessing a build service from a buildScan.buildFinished callback.

Additional testing made the issue trivially reproducible (by running it multiple times) in the presence of included builds, but could not reproduce it without involving included builds.

Is there a workaround for this issue?

Not that I know of.

I encounter this issue too with included builds.


chore(Order.RelIso): remove some porting notes

We get the CoeFun through FunLike which seems the current idiom. The changes are reducibly defeq to the porting remnants.

!bench

bors merge


Provide cryptographic signatures for all builds

This is so that users can validate the integrity of their downloads, and protect themselves against their tokens and wallet being stolen. Ideally, provide gpg signatures for all builds.

Added file hashes in release page.
https://github.com/neo-project/neo-gui/releases/tag/v2.0.2

Would you also be open to the possibility of adding PGP signatures?

@chenzhitong Can you look into it?


[7.x] Adds higher order "when" proxy

As per the suggestion in laravel/ideas#1881, this PR adds the ability to use higher order messaging when using the when (and unless) functions in query builders/collections.

The two failing tests in the first build (for PHP 7.2) don't seem to be related to these changes, as far as I can tell.

#29777

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.

That's sad, really sad. @kayrunm could you please consider to create a package with this?