python311Packages.dvc: 3.30.0 -> 3.30.1, python311Packages.dvc-data: 2.21.2 -> 2.22.0

Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

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

14 packages built:

dvc (python311Packages.dvc)
dvc-with-remotes
dvc-with-remotes.dist
dvc.dist (python311Packages.dvc.dist)
python310Packages.dvc
python310Packages.dvc-data
python310Packages.dvc-data.dist
python310Packages.dvc.dist
python310Packages.dvclive
python310Packages.dvclive.dist
python311Packages.dvc-data
python311Packages.dvc-data.dist
python311Packages.dvclive
python311Packages.dvclive.dist


[Snyk] Upgrade superjson from 2.2.1 to 2.2.2

Snyk has created this PR to upgrade superjson from 2.2.1 to 2.2.2.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.

The recommended version was released 24 days ago.

Release notes

Package name: superjson

2.2.2 - 2024-12-05What's Changed

Add unknown class name to deserialization error by @ marcinciarka in #303
fix: don't DOS on nth key by @ Skn0tt in #305

New Contributors

@ marcinciarka made their first contribution in #303

Full Changelog: v2.2.1...v2.2.2

2.2.1 - 2023-11-09What's Changed

fix: target es2020 by @ Skn0tt in #275
docs: add peterbud as a contributor for bug by @ allcontributors in #276

Full Changelog: v2.2.0...v2.2.1

    from superjson GitHub release notes

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:

🧐 View latest project report
📜 Customise PR templates
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Fixed in https://github.com/markwylde/workerbox/pull/37.


431 Request Header Fields Too Large

I tend to get a 431 Request Header Fields Too Large error with express when running serverless offline start (serverless-offline plugin). Deleting event.multiValueHeaders fixes it, but it might break other things, I need to do more research:
exports.handler = (event, context) => {
    delete event.multiValueHeaders;
    return awsServerlessExpress.proxy(server, event, context)
}

The project where I'm having this issue is also using serverless-typescript though.
This issue was very annoying to find so therefor sorry for lack of other information, I'll try to update this issue if I find out more.

Hi @larrybolt, I am facing the same issue with a typescript-express project could you please share any information if you have done or found anything?

I changed library to serverless-http and it worked

Has anyone found a solution to this without using serverless-http?
It only seems to be happening when you are using later versions of node. If I run version 8.10 everything works, but as AWS is deprecating this version I would like to run things locally on the correct versions.

@georgeevans1995 the solution initially suggested, delete event.multiValueHeaders; before passing the event to awsServerlessExpress.proxy seems to work for us.

@larrybolt Sorry I should have said in my previous comment, I tried this but I still got the same error.

Just to add some more detail to this from some testing, the error only seems to occur when I have an authorizer attached to the handler. I'm not sure how or why this would make a difference though?

"Newer" versions of Nodejs limited the size of request headers to 8K.
What aws-serverless-express proxy does, is takes event and context data, serialize it to JSON and stores it as encoded strings in x-apigateway-event and x-apigateway-context request headers. This makes the entire payload of headers before proxying much larger than original. I found that it was even storing request body once, which some nice person fixed here. But it was when a limit in nodejs was 80K.
When running with serverless-offline, the plugin mocks a lot of event and context data (to look real), which cause it to hit the limit of 8K.
I guess there is no easy fix for this, besides downgrading nodejs to the version that has limit of 80K (e.g.  v10.13.0).

Why was this closed (without a comment)?  This is still a major problem and from what I can see the only workarounds are "use an old Node version" or "use another library", neither of which is a practical solution.

@jchadwick Sorry about that, didn't know it was still relevant. Based on the comments it seemed like it was an issue with NodeJS and does work once deployed, thus more an issue with serverless-offline.
Hmm now thinking about it.. it might be possible to fix this with a serverless plugin for those using serverless-offline. But that would be more of a hack.

This is very limiting, passing a large id_token for example, across the query path also invalidates the request. It is not just serverless-offline that is padding the payload.

http.maxHeaderSize can be overridden by max-http-header-size (nodejs >12.6, >10.15)
https://nodejs.org/api/cli.html#cli_max_http_header_size_size (16KB on nodejs 14 by default)
  "start": "node --max-http-header-size=16384 server.js",

http.maxHeaderSize can be overridden by max-http-header-size (nodejs >12.6, >10.15)
https://nodejs.org/api/cli.html#cli_max_http_header_size_size (16KB on nodejs 14 by default)
in package.json
  "start": "node --max-http-header-size=16384 server.js",

Building on top of that I'm using this:
"start": "npx --node-arg=--max-http-header-size=64000 serverless offline",

Fixed in v4

Fixed in v4


Unsupported meshes bug: Index out of range with certain models

Happens with samples from these sources after pressing START PAINT MODE:
https://trockk.itch.io/new-td-turret-lot
https://assetstore.unity.com/packages/3d/animations/1h-swing-low-left-5785

The root cause of the problem is overlapping vertices. The plugin should deal with them.

I am also having this problem with a Synty pack. Some models are fine while others are not.

Hi @mstergtr , please if you could  grab to try the Painter.cs  script to replace in your project that would be of great help to confirm with more model samples.
https://github.com/piXelicidio/DAPolyPaint/blob/mesh-support/Painter.cs
I believe it solves most of the problems with this kind of meshes with overlapping vertices and other weird constructions.
Thanks

The updated Painter script seems to have fixed the problem. Thanks! Great tool so far.


[BUG]: Create API gives 400

When user clicks on Make Payment button Second time Create API gives 400
To Reproduce
Steps to reproduce the behavior:

Make a Submission
Click on Make Payment
Make a Online Payment
Close the new window (Payment window)
Click on Make Payment button
Now we can see Create API gives 400

Expected : Two Demands should not create for the same Submission

Hi @Beehyv-Vinod , plz check this issue in dev env

Hi @Ramu-kandimalla @rajeshcherukumalli,  Tested in Kerala-dev Working fine, Demand is creating only once.

Hi @Ramu-kandimalla  @rajeshcherukumalli, Tested in UAT environment, Demand is creating only once. Working as expected


[DOC] Contributing steps needs to be changed

Problem

The contribution guidelines related to GitHub seem to no longer work as a new update of GitHub has been rolled out. The procedures according to the new update need to be added to help beginners contribute efficiently.

do you mean this step here?


YML Config file cleanup

We need the config file to be consistent in terms of indenting and style.

On it. Also please note that the type for what's currently the "open authentication handler" will be "none" to avoid confusion with oAuth going forward

Merged, looks good ( will just move comments around ).


Create The CLI for comparing 2 License Texts

Create CLI for comparing 2 License Text Files.
Write Tests for each of the function used in Normalize Class.

@anshuldutt21 Either remove the pycache folder from this git diff or add it to .gitignore file.

@goneall @zvr @pombredanne  Review needed.

is it really needed to generalize it? [var matching]

To be able to completely implement the license matching, we do need to support the <<var tags.  Implementing the other normalizations as well as the optional tags are more frequently used and a higher priority, though.  I would suggest adding an issues for implementation later (similar to the approach we took on the optional issue above).

The regex won't allow us to generalize it. I would have to use a different approach for that.

I agree - this will take some design and implementation effort.  When you're ready to look at implementations, we can discuss different possible approaches.

@goneall I have added the support for <> in the above recent commits. Do have a look once you are free.


[Discussion/Proposal] Make strapi-plugin-meilisearch client agnostic (ie: strapi-plugin-search)

I'm currently working on a Strapi project that requires search-engine integration. My initial plan was to go with Meilisearch, but unfortunately  the project is heavily dependent on GeoLocation queries. I am thinking of turning to Typesense for now before switching back to Meilisearch when GeoLocation queries are added.
With that in mind I was a little sad to find out that there were no Typesense-Strapi plugins, and I was contemplating a couple different options.

Registering the Typesense client into Strapi using a hook and then simply using it in the model lifecycles. This is the simplest solution, but its also the most limited.
Clone this repository, and make the necessary modifications to make it work with the Typesense client.

It's while considering option 2. and taking a look at the code in this repo that the thought of a client agnostic search plugin came to me.  Below is a description of what I have in mind.
Description
Make this project client agnostic in a way that is similar to the "Strapi Upload Plugin" where the choice of provider is open to the end-user and is as simple as installing an additional dependency and modifying your config.
This would also be similar to the way instantsearch.js package works were the client can be interchanged based on what backend service you are using (instant-meilisearch, typesense-instantsearch-adapter, etc...).
Rational
Meilisearch has the best search-engine Strapi integration, and making this project client agnostic would create a more robust Strapi ecosystem where this would be the go to "Search Plugin". And as the maintainers of the projects this could also be good exposure for Meilisearch.
Implementation
From what I could tell going through the code (relatively quickly, so sorry if I missed anything) most of the codebase is already client agnostic thanks for the abstraction of the http  client in the services folder. There are a couple other instances of the code being "Meilisearch" specific (Error's and credentials handling), but these should be relatively easy to abstract as well.
And for third party client integration, this plugin would handle loading the client and reading the config, and we could provide an API spec that all third-party clients should meet.

Sorry for the block of text, but I just wanted to get my thoughts down on the paper. And hoping to open a discussion on the topic.

Hello @ghassanachi thanks so much for taking time to develop your idea and for you very kind words. I think your initiative is very good but it does raise some problems:

The plugin has meilisearch written on it so it's already not agnostic in its name
The plugin would gain in complexity if it has to be configurated by the users. Whereas today you don't need configuration.
The plugin still needs a big refactor to make it work.

The maintaining could indeed bring a lot of exposures to MeiliSearch but we also have a lot of other plugins to maintain and to come and we only have so much hands.
Nonetheless, feel free to fork this project and and develop this project as I think it is a very cool idea. I would enjoy contributing to it :)

Thanks for the prompt reply.
I'm not sure I'll have the time in the upcoming weeks to work on the refactor, but if/when I do I'll make sure to let you know.
Thanks again for all the great work, on this project and Meilisearch in general.
I'll leave it up to you to close this issue.


Provide support for SVG xml in icon

Is your feature request related to a problem? Please describe.
It would be great to support custom svg xml as an input for the icon component
Describe the solution you'd like
extend icon to allow in-lining (or file path input reference) for svg xml
https://material.angular.io/components/icon/overview#svg-icons
Describe alternatives you've considered
Haven't tried any other way to add svg to mesop

Thanks for filing an issue. Agree, it would be nice to eventually support this. For now, you should be able to use web components to inline SVGs: https://google.github.io/mesop/web_components/ - let me know if you run into troubles doing that.

Works like a charm, thank you!

As an update, I created a stand alone component for this https://github.com/ghchinoy/mesop-svg-icon


Restarting vscode doesn't reopen .ipynb tabs

Bug: Notebook Editor, Interactive Window, Editor cells

Steps to cause the bug to occur

Open a.py + b.ipynb
Close vscode, then reopen vscode

Actual behavior
a.py is automatically reopened, but b.ipynb is not
Expected behavior
Both a.py + b.ipynb are automatically reopened

Your Jupyter and/or Python environment
Please provide as much info as you readily know

Jupyter server running:                       N/A
Extension version:                               2020.2.64397
VS Code version:                                1.42.1
Setting python.jediEnabled:               true
Python and/or Anaconda version:     N/A
OS:                                                     Mac
Virtual environment:                          N/A

Developer Tools Console Output

Microsoft Data Science for VS Code Engineering Team: @rchiodo, @IanMatthewHuff, @DavidKutu, @DonJayamanne, @greazer

Thanks. This is a known limitation as our editors aren't really editors as far as VS code is concerned. Once this bug (#7903) is addressed, this problem will go away.


Improve trimming of images with transparency

Retrieve the background colour alpha value and pass image alpha band to find_trim() if background colour is not fully opaque. Attempt to fix issue #1597

Coverage remained the same at 99.756% when pulling<PHONE_NUMBER>c1a4b0cc0f98c58b693338e7e31ca7 on Monotype:master into fb5c393fbdb936ca2d3b829a6f9ee44cd3884b1c on lovell:master.

Thanks for the PR. Am I correct in thinking that if the top left pixel has any transparency then only the alpha channel is used for the trim? I'm not sure this is the desired behaviour, or at least could break backwards compatibility.
Perhaps a two-step process could be used instead, where if the initial call to find_trim returns zero offsets and the image has an alpha channel, then perform a second call on just the alpha channel.

I've addressed this in commit c41b873, which adds support for trimming images where the alpha channel contains the images (and non-alpha channels are a single colour) and maintains backwards compatibility with existing behaviour.
@muse-monotype Thank you very much for taking the time to submit the original PR Martin, these are always highly appreciated.


Performance issue of AdvancedProducer code example provided by Confluent Kafka .NET

Description
The code in the link below wass modified to send 50 messages of 100 characters. It takes around 50 seconds, which is slow, compared to 300 message/second on other brokers (300 * 50 = 15 000 messages for 50 seconds, 50 vs 15,000).
https://github.com/confluentinc/confluent-kafka-dotnet/blob/master/examples/AdvancedProducer/Program.cs
How to reproduce
Basically, the code below is repeated to run 50 times
var deliveryReport = producer.ProduceAsync(topicName, "", messageWith100Characters);
var result = deliveryReport.Result; // synchronously waits for message to be produced.
Default settings from both Kafka and ZooKeeper are used, both of which are running on Windows 7.
Checklist
Please provide the following information:

[x] Confluent.Kafka nuget version: 0.11.4 https://www.nuget.org/packages/Confluent.Kafka/0.11.4
[x] Apache Kafka version:   kafka_2.11-1.1.0.tgz
[x] Client configuration: .NET CORE 2
[x] Operating system: Windows 7
[ ] Provide logs (with "debug" : "..." as necessary in configuration)
[ ] Provide broker log excerpts
[x] Critical issue

What Linux VM is best for Kafka? For example, the version that is used by Linkedin?
To run Linux on Windows 7, what VM and Linux can you recommend?

Google is a great source for such searches.  This is the wrong forum.


Support multiprocess dataloading for jax backend

Any insight into this? I was trying to multiprocess with the buildin pytorch dataloader and it seems to fail. That's what brought me here. Happy to help out.


Feature/deploy_example

Adding an example that show how to :
-Deploy an OpenZeppelin account
-Deploy an ERC20 contract
-Mint the ERC20 contract
-Transfer tokens from the deployed account to a third-party account
-Document how to provide ETH to the deployed account
Unfortunately, the code can't be tested because of a bug when deploying contracts [#95]

Hello @FlorianRichardSMT,
Thank you for your contribution! We really appreciate the fact that you have found the bug even if we did not corrected yet ;-). We will sort your PR as a tutorial as it is more complete and more task driven than the other examples. Don't worry, I will handle that:
There are a few thinks I would like to see corrected though:
1- I will assume the people that are using Caigo know about Go but might not know a lot about Starknet:

Remove the comments that paraphrase the code. If you need to write a comment, prefer writing a block that is very useful.
I like very much you point useful tools like voyager and the faucet. Can you also explain how to compile the contracts? OR embed the contracts json?

2- There are a few (not many) typos that looks more like the fact you did not pay attention: usefull with 2 f, manualy with 1 l, accout no n. You can probably fix 80% of it yourself.
3- In english there is no space before :
4- Use go workspace (go work init) instead of referencing the project from the directory. The reason is that the way it is done, if I upgrade Caigo, the project will not upgrade.
5- Do not use "get" in the function names, prefer balanceOf rather than getBalanceOf see https://go.dev/doc/effective_go#Getters
6- You might want to keep the private key somewhere so that if the program or the developer fails he does not have to restart everything. As a matter of fact, you can probably fix it with a small comment (in that case) saying if you might not want to use a private key people know about.
7- Make the salt predictable/repeatable, even if you for sure do not want collision. A good practice for instance would be to use your *public" key rather than a timestamp.
I am not a big fan of having a large main() like that. I cannot think of a better way. Maybe you could code with tests or range through a map of functions?
@GregoryGuillou

Thanks for your response @gregoryguillou !
Regarding the 6th item:
writing the hex representation of the private key into a file would be ok ?
For the main size:
In my opinion, it's clearer for the developer to read the code from the main and see all steps one by one. I agree with you, it is quite long but facilitate the understanding of the library.


feat(protocol) :add Dockerfile for packages/protocol use for future testing

Purpose reduce step install pnpm, nodejs, forge
Better for future testing
Can be used for quick on-chain RA .

@smtmfft @d1onys1us Can you help review this later ? Thanks


Add script lwaftrctl

Rebased PR of #206. Configuration files are structured is several folders, so it's easier to add new VMs if necessary.
This script eases the process of running the lwaftr from within a VM. To run lwaftr virtualized is necessary to go through the following steps:

Bring up two NICs from the host using snabbnfv (vhost-user).
Start VM with QEMU.
Run lwaftr from within VM.

The lwaftr is run inside the VM using the virtio_net driver.
Once the lwaftr is running, it should be possible to send packets to and from the guest. Run the "snabb-lwaftr transient" from within the host for testing purposes.
The script exposes the following commands to ease this process:

lwaftrctl snabbnfv start
lwaftrctl vm start
lwaftrctl lwaftr start

A file lwaftrctl.conf, containing all the necessary parameters, must exist within the same folder the lwaftrctl command is run. See lwaftrctl.conf.example.
It is also necessary to create user VM_USER in the VM. This user must be in the list of sudoers. It is necessary to create a script "run_lwaftr.sh" in VM_USER home. See run_lwaftr.sh.example.

lgtm, thank you!


V14 updates for button

Starts the V14 update process and includes some quality of life features.

Removes all generated files from git. npm install will now generate these on the fly.
Cleans any built files prior to running npm start. This will help avoid confusion with errors when trying to develop with built artifacts.
Adds an .npmrc file to ensure we are pulling from the public registry.
Adds node-sass, some of the newer material modules no longer have built dist css files
adds the TouchTarget component
Updates Button to V14

Codecov Report

Merging #816 (6736999) into next (f8fe852) will increase coverage by 0.14%.
The diff coverage is 94.11%.

:exclamation: Current head 6736999 differs from pull request most recent head bf2eded. Consider uploading reports for the commit bf2eded to get more accurate results

@@            Coverage Diff             @@
##             next     #816      +/-   ##
==========================================
+ Coverage   80.66%   80.81%   +0.14%
==========================================
  Files         107      108       +1
  Lines        3336     3351      +15
  Branches      767      768       +1
==========================================
+ Hits         2691     2708      +17
+ Misses        640      638       -2
  Partials        5        5

Impacted Files
Coverage Δ

src/textfield/textfield-foundation.tsx
82.60% <0.00%> (ø)

src/button/index.tsx
100.00% <100.00%> (ø)

src/select/select/foundation.tsx
77.11% <100.00%> (+0.11%)
:arrow_up:

src/touch-target/index.tsx
100.00% <100.00%> (ø)

src/list/foundation.tsx
75.83% <0.00%> (+1.66%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Fix class encapsulation issue in ZeroMunge\Forms\Main.cs

CodeFactor found an issue: A C# document may only contain a single class at the root level unless all of the classes are partial and are of the same type.
It's currently on:
ZeroMunge\Forms\Main.cs:4284
Commit e66a7391ee405be98e62b9a4b2c66dc427400160

Issue fixed in b452def - closing.


Updating the notebook.ipynb file

Closes #33

First step, the dependencies are fixed.

@clatapie  let me know if you need any help on this. :)


Ripple directive does not work

Ripple directive does not work with the Tailwind setup.

For me it did, but after making changes it stopped working for an yet unknown reason. Even after reverting my repo to the moment it did work. It's unclear to me what is going on. Here are the things I tried to bring it back, but without success:

Restart dev server
Using a different browser
Clearing Vite cache
Deleting node_modules folder and re-installing
Building
Restarting PC

It does show in the html, but it's not visible for some reason:

Note that I use a fade effect when active, the ripple is not present

Source of example above

Default

Source of prime vue plugin
import PrimeVue from 'primevue/config';
import Ripple from 'primevue/ripple';
import defaultTheme from '../themes/defaultTheme';

export const primeVuePlugin = {
    install(app) {
        app.use(PrimeVue, {
            ripple: true,
            unstyled: true,
            pt: defaultTheme
        });

        app.directive('ripple', Ripple)
    }
}

Adding a custom example results in this:

It's a real head-scratcher for me.

I found the problem!
It basically comes down to the colors in tailwind. In wind/ripple/index.js the color bg-surface-0/50 is used.
In my case I modified the color variables in my app.css:
Example:
:root {
    /* ... */
    --surface-50: 248, 249, 250;
    /* ... */
}

Notice the comma's, I didn't think it would make a difference if I would leave them in since it worked, but after removing them the effect was restored. So to fix it I did:
-    --surface-50: 248, 249, 250;
+    --surface-50: 248 249 250;

for all my colors.
TL;DR:
The tailwind color being used for the ripple effect does not exist, not correctly defined or is not compatible to make transparent.

Ah, yes, good catch! It's the commas that are causing the issue.


Motion > amendment: formatting change in amendment plus original text leads to wrong diff

Describe the bug
Part I: If an amendment change also includes a formatting change in amendment and original text, the diff will be wrong displayed. The whole paragraph will be shown as diff not the relevant parts.
Part II: If a motion paragraph includes for example a bold format in two sentences and an amendment is created in the second sentence with an additional word and a change in the bold content, than the diff is wrong displayed. The whole paragraph will be shown as diff.
Part I - Original motion:

Part I - Amendment with red marked diff (amendment plus original text):

Part I - Outcome view:

Part II - Original motion paragraph

Part II - changes done in the amendment - changes are red marked:

Part II - Outcome:

How to Reproduce
Steps to reproduce the behavior:

open a meeting
open motions > create a motion with two paragraphs. Add in the second paragraph a bold formatting of one word in the first and in the second sentence. > save it.
Part I - create an amendment in first paragraph and change one word. mark the new word and an original word in bold. > save diff
Part I - visual should now be broken like in the example above
Part II - create an amendment in second paragraph and change the second sentence as follow: add one new word right before the bold word and add content to the bold word > save diff

Expected behavior
If an amendment contains text and fomat changes, the diff visual should clearly display differences and should not show a change in the whole paragraph.
Important: Bold format is just an example. This problem also occurs for italic, underlined, strikethrough and color changes. This should not happen for all of these format changes. - FYI: I've tested all of this format types with Part I. At least for this, same problems occur.
This issue is part of the Meta Diff issue. #2956

[ ] changed title
[ ] extended problems with the counterpart of formatting
[ ] added a new examples
[ ] changed the expected behavior with additional requirements

https://github.com/OpenSlides/openslides-client/pull/4461
As mentioned in the PR, this does not fix all possible scenarios, but some relatively easy ones, including the first mentioned one here.

Part of this Issue was fixed and approved
I' ll remove the staging label for now

Hi! I hope this fixes some of the remaining issues? https://github.com/OpenSlides/openslides-client/pull/4479

It might well be that while trying to replicate the issue, I stumbled over another one. This isolated HTML snippet here definitively helps. One more attempt in the updated MR.


New-RubrikAPIToken    returns  Invoke-WebRequest : Request needs authentication!

Current Behavior:
When using  Connect-Rubrik  and Toekn to conenct to Rubrik cluster  and trying to create new Token in same session,
The command New-RubrikAPIToken fails and  returns "Invoke-WebRequest : Request needs authentication!"
Provide information about the failure by issuing the command using the -Verbose command. Ensure that any identifiable information (server names, tokens, passwords) is removed from your logs before sharing this on GitHub.

$RubrikAPIToken = Get-AzKeyVaultSecret -VaultName $AKV -Name $SecretName -AsPlainText
Connect-Rubrik -Server $RubrikClusterName -Token  $RubrikAPIToken     (Successfull)
Get-RubrikAPIToken -Verbose      (Sucessfull)
New-RubrikAPIToken -Tag "TestToken-01" -Expiration 100 -Verbose   (ERROR)

Paste the verbose output from the command here

New-RubrikAPIToken -Tag "TestToken-01" -Expiration 100 -Verbose
VERBOSE: Validate the Rubrik token exists
VERBOSE: Found a Rubrik token for authentication
VERBOSE: Gather API Data for New-RubrikAPIToken
VERBOSE: Selected 5.0 API Data for New-RubrikAPIToken
VERBOSE: Load API data for New-RubrikAPIToken
VERBOSE: Description: Create an API Token
VERBOSE: Build the URI
VERBOSE: URI = https://rubrikcluster.mydomain.com/api/internal/session
VERBOSE: Build the query parameters for
VERBOSE: URI = https://rubrikcluster.mydomain.com/api/internal/session
VERBOSE: Body = {
"initParams":  {
"apiToken":  {
"tag":  "TestToken-01",
"expiration":  100
}
}
}
VERBOSE: Submitting the request
VERBOSE: Submitting "Post" request as "text/plain; charset=utf-8"
VERBOSE: Invoking request with a custom timeout of 100 seconds
VERBOSE: POST https://rubrikcluster.mydomain.com/api/internal/session with -1-byte payload
Invoke-WebRequest : Request needs authentication!
At C:\Users\UserName\Documents\WindowsPowerShell\Modules\Rubrik\Private\Invoke-RubrikWebRequest.ps1:36 char:23

...   $result = Invoke-WebRequest -UseBasicParsing -TimeoutSec $rubrikOpt ...

            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebException
FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand

Expected Behavior:
New-RubrikAPIToken uses curernt Token as authentication and don't requests authenticatino again.
Steps to Reproduce:
Please provide detailed steps for reproducing the issue.

Step 1    Connect-Rubrik -Server $RubrikClusterName -Token $RubrikAPIToken (Successfull)
Step 2    New-RubrikAPIToken -Tag "TestToken-01" -Expiration 100 -Verbose
Step 3 (and so on)

Context:
Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.

Rubrik PowerShell Module Version: Use Get-Module -ListAvailable Rubrik
6.0.1
PowerShell Version: Use $PSVersiontable.PSVersion
5.1
Operating System: Use $PSVersiontable.PSVersion on PowerShell 6 and later, use (Get-WMIObject win32_operatingsystem).Name for Windows PowerShell
Microsoft Windows Server 2019

Failure Logs
Please include any relevant log snippets or files here, IMPORTANT all information will be visible publicly on GitHub. Do not include computer or user names, passwords, API tokens or any identifiable information when submitting failure logs.

.EXAMPLE
New-RubrikAPIToken -Expiration 10080 -Tag "Dev Org Weekly Token" -OrganizationId "Organization:::11111111-2222-3333-4444-555555555555"
This will generate a new API Token named "Dev Org Weekly Token" that lasts for 10080 minutes (7 days) in the organization matching id value "Organization:::11111111-2222-3333-4444-555555555555".
This assumes that the current session that is requested the token has authority in that organization.
What authority or role is needed for New-RubrikAPIToken?

We see the same issue here.
Also tried with more direct API calls:
$$token = …(my current token)…
$headers = @{
         'Authorization' = "Bearer $($token)"
       }

$par = @{
       'initParams'= @{
         'apiToken'= @{
            'expiration'= '3600'
            'tag'= 'API Generated Token'
         }
       }
    }

Then use Get-RubrikUser  to fetch my User_ID
And then:
$res = invoke-webrequest -Headers $headers -Method POST -Uri "https://rubrika.mydomain.com/api/internal/session?user_id=...(user_ID)..." -Body $par

invoke-webrequest : Request needs authentication!

I'm attempting to use a Service Account (with Administrator Role), and have the same problem/error message. It is unlikely an authority issue.

Any work around for this issue?

I have ran into the same issue. I have tried passing creds several different ways. If you make the call manually using the api address and passing creds it will return the key. However, if you're using this powershell command it has the error.


Push Plugin register failed - iOS

I'm new to app development. I have received following error while registering iOS device ,
Error:
PushPlugin.register: setting badge to false
PushPlugin.register: clear badge is set to 0
Push Plugin register failed
Thanks in advance

Try adding iOS Development provisioning file, not distribution. it worked for me.

@muvaffak
Thanks for your response. Its works :+1:

Also got this issue and same exact message after upgrading to Xcode 8 and iOS 10, for whatever reason the "Push Notifications" switch in the "Capabilities" tab of my Xcode project had been switched back to "OFF". Switching this back fixed the issue.

@sirhodes You sir have my thank.
Can't believe something this simple was the issue I was struggling with since yesterday.

@rishabh-altimetrik glad that I could help! 👍

Oh my....after fighting with Xcode, App Dev Center (went through certificates and App IDs and the lots!!), ionic, this and that.... you sir, @sirhodes , pointed me in the right direction!
It was the Push Notifications on Capabilities tab of Xcode that was triggering the dreaded "Push Plugin register failed" on Xdebug console for Phonegap push plugin registration step. Kudus to you @sirhodes 👍

Same issue for me, thanks @sirhodes for the fix, saved me a few hours!

Thanks @sirhodes , I went through the same trouble until I saw this.

Thanks, @sirhodes!

Thanks @sirhodes you saved many headaches.

Thanks @sirhodes

i am not able to get the device token from the ios or version 10.0 it returns the value of undefined please help me out to solve the problem and it is working fine in ios 9 and also ipad


Revert "Revert "Support multi-threaded signing for golden SEI generation

This reverts commit 719a24f21b833871a1adcf4927a17b5366b2da7d.
Describe your changes
Please include a summary of the change, a relevant motivation and context.
Issue ticket number and link

Fixes #(issue)

Checklist before requesting a review

[ ] I have performed a self-review of my own code
[ ] I have verified that the code builds perfectly fine on my local system
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have verified that my code follows the style already available in the repository
[ ] I have made corresponding changes to the documentation

Already pushed through a different PR


SAM-3029 auto submit job can cause no submissions to process

auto submit job can cause no submissions to process when type isn't guessed correctly.

This looks good to me! Trunk is closer to this but I think this patch should also be applied to trunk at least for this query (if there's no other changes to the query). Most of the stuff for Extended Time was refactored out but this part was left around and was actually important!


Ignore upper/lower case data files

My version of Resident Evil 2 has all source files in lowercase.
So I'm getting errors like this: ESP file doesn't exist: data/Common/DATP/CORE00.ESP
I've actually got the file, but mine is: OpenBiohazard2/data/common/datp/core00.esp

I made a code change to check whether the game folders exist. If the folder doesn't exist, the game will throw an exception. Can you confirm the data files are in the correct directory and all the folders exist?

It seems to be working but the message is not very helpful:
Validating game folders exist...
Folder data/ exists and has 11 files
2023/05/16 23:23:21 Missing data error: Unable to find folder: data/Common/. Error: <nil>

I'm open to add some logic for reading game data in base of different regions in order to avoid upper/lower case problems.
Let me know if you would like to have this feature.

The file loading didn't work because you should have seen the message "Validated game folders exist". In your case, the game isn't able to find the "Common" folder under your data directory. What does the file structure look like on your local machine?
When I run the game, this is the output for the file validation:
Validating game folders exist...
Folder data/ exists and has 6 files
Folder data/Common/ exists and has 5 files
Folder data/Common/bin/ exists and has 9 files
Folder data/Common/Door/ exists and has 56 files
Folder data/Pl0/ exists and has 5 files
Folder data/Pl0/RDP/ exists and has 250 files
Folder data/Common/DATP/ exists and has 104 files
Validated game folders exist

The topmost level should be "data" and the "Common" folder should be under "data". When I run it on Windows, I was still able to load all the files regardless of whether COMMON_FOLDER is uppercase or lowercase. If you are sure your file directory is correct and the problem is a case issue, you can manually change COMMON_FOLDER in resource.go to match your folder name and rebuild.

I've been able to make it works. But it's not enough just by changing COMMON_FOLDER.
BTW I'm on Linux.
This is the output:
Validating game folders exist...
Folder data/ exists and has 11 files
Folder data/common/ exists and has 5 files
Folder data/common/bin/ exists and has 9 files
Folder data/common/door/ exists and has 56 files
Folder data/pl0/ exists and has 5 files
Folder data/pl0/rdp/ exists and has 250 files
Folder data/common/datp/ exists and has 104 files
Validated game folders exist

I had to replace all leading uppercase by lowecase in resource.go, it now looks:
const (
        BASE_FOLDER         = "data/"
        COMMON_FOLDER       = BASE_FOLDER + "common/"
        COMMON_BIN_FOLDER   = COMMON_FOLDER + "bin/"
        ROOMCUT_FILE        = COMMON_BIN_FOLDER + "roomcut.bin"
        ITEMDATA_FILE       = COMMON_BIN_FOLDER + "itemdata.bin"
        ESPDATA1_FILE       = COMMON_BIN_FOLDER + "espdat1.bin"
        ESPDATA2_FILE       = COMMON_BIN_FOLDER + "espdat2.bin"
        COMMON_DOOR_FOLDER  = COMMON_FOLDER + "door/"
        DOOR_FILE           = COMMON_DOOR_FOLDER + "door%02x.do2"
        PL_FOLDER           = BASE_FOLDER + "pl0/"
        LEON_MODEL_FILE     = PL_FOLDER + "pld/pl00.pld"
        ENEMY_FILE          = PL_FOLDER + "emd0/em%03x.emd"
        RDT_FOLDER          = PL_FOLDER + "rdp/"
        RDT_FILE            = RDT_FOLDER + "room%01d%02x%01d.rdt"
        COMMON_DATA_FOLDER  = COMMON_FOLDER + "datp/"
        CORE_SPRITE_FILE    = COMMON_DATA_FOLDER + "core00.esp"
        INVENTORY_FILE      = COMMON_DATA_FOLDER + "st0_pl.tim"
        MENU_IMAGE_FILE     = COMMON_DATA_FOLDER + "Tit_bg.adt"
        MENU_TEXT_FILE      = COMMON_DATA_FOLDER + "tmojipal.bin"
        ITEMALL_FILE        = COMMON_DATA_FOLDER + "itemall.bin"
        SAVE_SCREEN_FILE    = COMMON_DATA_FOLDER + "type00.adt"
        COMMON_SOUND_FOLDER = BASE_FOLDER + "common/sound/"
)

The issue seems to show up if the filesystem is case-sensitive. I thought the issue was related to the file structure because another person reported a similar issue with loading the files.

It makes sense, would you like have some control over this?
I can work on that

If you are interested, you can make improvements.


List topic lag?

Thanks for making this one, really neat!
Is there a way to get the lag per topic?
Thanks!

Thanks @dnaeon. If I understood you correctly, trubka list group-offsets <group_name> will give you the lag for all the topics under that consumer group. You can also check the local offsets for a specific topic usingtrubka list local-offsets <topic> command. Hope that's answered your question.

Great, thanks!


how to get perturbations in shapeshifter2d.py?

I read and run the code, but don't get perturbations image.I guess line 133 code: input_images_ = create_composited_images(args.batch_size, textures_, textures_masks).But I am not sure.I truly appreciate your  help.

If you save the output via --logdir, you can then point Tensorboard to that directory and see the perturbation evolve over the attack iterations. You can then save the perturbation by right clicking on the image and saving via your web browser. All this logic happens in https://github.com/shangtse/robust-physical-attack/blob/master/shapeshifter.py#L614


Fix #31 - Update twitter status to change in karma

Move twitter status updating into the main loop

Remove checking for an increase in karma before updating status

Add karma_yesterday() to parse karma.txt and determine the amount
of karma gained during the previous day

Moved reddit comment string into a variable called message_template
Reformatted a few lines for line length
Change already_done to a set instead of a list for performance

Requesting a code review and test

I have been testing this.
I would like very verbose testing due the issues we've been facing lately. Everything so far looks good and is working.
Going to test this for at least two hours for the new karma stuff.

So far, so good.
Twitter desc is updating properly.

We should change the message to have "karma" after "{karma}"

On Jan 18, 2015, at 1:16 PM, Blade Nelson<EMAIL_ADDRESS>wrote:
So far, so good.
Twitter desc is updating properly.
—
Reply to this email directly or view it on GitHub.

I think that's enough testing? Everything works great. Just add karma after {karma} when updating Twitter description.
Ready to merge when you add that.

Okay, it's ready to be merged then.


Writing get_mints module

Wrote module and pushed to Upstream.
NOTE: numpy was not imported in my module!


tabBarVisible is ignored for nested scenes

With react-navigation before 2.0, setting tabBarVisible: false at any level in the navigation tree would cause the tab bar to be hidden, this behaviour is now broken.
Current behaviour
Setting tabBarVisible: false on any scene below the top level tab scenes will have no effect, making the setting largely useless because the top-level is probably the place where you can guarantee not wanting this behaviour.
Expected behaviour
I'd expect the tab bar to be hidden regardless of where in the navigation tree it is used, as seen in pre-2.0.
Code sample
https://snack.expo.io/@andrewingram/broken-tabbarvisible
Features 3 different usages of tabBarVisible: false, but only one of them works. In previous versions of React-Navigation, all 3 worked.
What have you tried
Looking at _renderTabBar in createBottomTabNavigator.js, it seems that only the top-level options are ever looked at.
Your Environment

software
version

ios or android
/

react-native
0.55.2

react-navigation-tabs
0.2.0

node
/

npm or yarn
/

It seems like this is part of the bigger change to how navigationOptions work, but seems like a pretty major regression.

A regression describes a behavior change that was unintentional so maybe the wording is wrong here. It was a very intentional change as you can see with the RFC.
I updated the Snack you provided to make tabBarVisible work as you expected: https://snack.expo.io/Sk7Go1WRM
Notice that in each case only the child screen of the tab navigator is aware that it's inside of a tab navigator. This is very intentional for the reasons I described in the RFC.
It's also worth mentioning an alternative solution to the behavior in the "First" tab, where you want to hide the tab bar on nested screens. What you could do here instead (and what I'd recommend doing in order to avoid layout jumping when the tab disappears/re-appears) is put another stack on top of the tab bar and navigate to that. See the following Snack where I reworked the "First" tab accordingly: https://snack.expo.io/SkXH2J-CG
So, I'm still waiting to see cases where this causes legitimate problems that can't be expressed using the techniques I applied above. If someone can present these then I'd be happy to discuss how we can improve the API!

Also, I meant it to be a regression in the expected behavior of tabBarVisible, because I'm guessing the way I was doing it is how most people would have been using it.

@AndrewIngram I struggled with this issue but got it to work here's the link that helped:
https://reactnavigation.org/docs/en/navigation-options-resolution.html#a-tab-navigator-contains-a-stack-and-you-want-to-hide-the-tab-bar-on-specific-screens
The tricky part was that instead of checking index (navigation.state.index > 0) the main navigation I had to do that in the nested navigation, the index on the main navigation never changed from 0.  I hope this helps.

@AndrewIngram Thanks!

Yes this example from snack works
https://snack.expo.io/Sk7Go1WRM
StackA.navigationOptions = ({navigation})=>{
let { routeName } = navigation.state.routes[navigation.state.index];
let navigationOptions = {};
if (routeName === 'BrainStormScreen') {
navigationOptions.tabBarVisible = false;
}
return navigationOptions;
}
but on v1 version of react-navigation i was able to place tabBarVisible to false inside of screen that i wanted that kind of behavior :
export default class EventsScreen extends Component {
static navigationOptions = {
//Nav options can be defined as a function of the navigation prop:
headerTitle: 'Events',
headerStyle: { backgroundColor: 'white'},
headerBackTitle: null,
tabBarVisible: false,
};
...
just wanted to ask is this possible on 2.0+ versions ?

The decision, like this, is bad:
StackA.navigationOptions = ({navigation})=>{
let { routeName } = navigation.state.routes[navigation.state.index];
   let navigationOptions = {};
   if (routeName === 'BrainStormScreen') {
      navigationOptions.tabBarVisible = false;
   }
    return navigationOptions;
}

TabBar disappears before switching between screens and it looks twitched.

Second @igor-shyrnin statement. It would be nice if there was a smoother animation when hiding the tab-bar or providing a way for users to specify that. It looks unprofessional at the moment. But I'm just complaining right now.
Also the recommended solution in the docs is kind of wanky. It recommends us to create a stack navigator at the same level as our our Tab navigator.
Although that may work, I don't think that should be the recommended solution because Its illogical to put a child screen at a higher level.
Logically, it doesn't always make sense to put a child screen of a screen listed inside tabnavigator at the same level as tabnavigator. Why should for example, my PostDetailScreen not live in the same navigator as my PostScreen? That poses potential problems on folder structure, hierarchy, and can be a cause of many confusions. It would be nice if someone can clear up the reasoning behind the recommended solution, I'm probably missing something here.

Current solution:
const TabNavigator = createBottomTabNavigator(
  {
    ...
  },
  {
    initialRouteParams: { isTabBarChild: true },
  },
);

const setTabBarVisible = (tabBarVisible, navigation) => {
  let curr = navigation;
  while (!curr.getParam('isTabBarChild', false)) {
    curr = curr.dangerouslyGetParent();
  }
  const tabBarChild = curr;
  tabBarChild.setParams({ tabBarVisible });
};

this explains what to do: https://reactnavigation.org/docs/en/navigation-options-resolution.html#a-tab-navigator-contains-a-stack-and-you-want-to-hide-the-tab-bar-on-specific-screens


Conda alternative

Hi,
I see that the only two options for the dependency management are local or conda.  But from what I understand of the TOS of anaconda/miniconda, using their conda repository is possibly not free if someone is part of a for profit organization with 200+ individuals.
So, is there are any plans on using something else?  Or maybe the preferred way is to implement homemade decorators to call pip  manually?
Maybe I misunderstood the situation.  If this is the case, simply dismiss this question with my apologies.

Giving another option (around the pip ecosystem) is something that is definitely being looked at but we haven't yet been able to dedicate resources/time to it. I can say with a fair amount of certainty that it will happen but can't really give you a precise timeline right now.
In the meantime though, you can use the conda-forge channnel which IS free for everyone. It doesn't always have all the packages but it has quite a few. Basically, anything except the anaconda channel is fair game.

Thanks for the clarification

See also https://github.com/Netflix/metaflow/issues/24. Especially have a look at this temporary solution: https://github.com/Netflix/metaflow/issues/24#issuecomment-571976372

https://docs.metaflow.org/scaling/dependencies/libraries#pypi-in-action


Add support for only one parent

It were impossible to add only one parent. I fixed it via adding foo parent and hiding it.

Hi @osya!
Thanks for the pull request and engaging with the dTree community!
Having a single parent is however already possible. It's a bit unclear from the documentation (in fact it maybe undocumented, my bad!) but by adding the children into the node of a parent directly the children will descend from that parent.
Like this:
{
  name: "Father",
  class: "node",
  textClass: "nodeText",
  children: [{                          // List of children nodes
      name: "Child",
    }]
}]

I'll have to have a closer look if this new solution is better. Either way I think the old notation is better rather than hiding the other parent using a special attribute.
/Erik

Hello, @ErikGartner
Thanks for your clarification. You solution for one-parent by placing children node just under person's node is worked. According to this PR I can say the following:

this PR can be used as another solution for one-parent. In your solution connector line between one-parent and his child becomes broken. In this solution connector line between one-parent and his child straight
this PR can be used just for node hiding functionality. So I suppose PR should be renamed


Added bootstrap list to Front End Development

Added the bootstrap awesome list located at https://github.com/therebelrobot/awesome-bootstrap

https://github.com/therebelrobot/awesome-bootstrap
BOOTSTRAP!!! This list is about all things amazing bootstrap. Themes, libraries, and UI Kits.
By submitting this pull request I confirm I've read and complied with the below requirements.
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.

I have read and understood the contribution guidelines and the instructions for creating a list.
This pull request has a descriptive title.For example, Add Name of List, not Update readme.md or Add awesome list.
The entry in the Awesome list should:

Include a short description about the project/theme of the list. It should not describe the list itself.Example: - [Fish](…) - User-friendly shell., not - [Fish](…) - Resources for Fish..
Be added at the bottom of the appropriate category.

The list I'm submitting complies with these requirements:

Has been around for at least 30 days.That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
It's the result of hard work and the best I could possibly produce.
Non-generated Markdown file in a GitHub repo.
Includes a succinct description of the project/theme at the top of the readme. (Example)
The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
Not a duplicate.
Only has awesome items. Awesome lists are curations of the best, not everything.
Includes a project logo/illustration whenever possible.

Either fullwidth or placed at the top-right of the readme. (Example)
The image should link to the project website or any relevant website.
The image should be high-DPI. Set it to maximum half the width of the original image.

Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
Includes the Awesome badge.

Should be placed on the right side of the readme heading.
Should link back to this list.

Has a Table of Contents section.

Should be named Contents, not Table of Contents.
Should be the first section in the list.
Should only have one level of sub-lists, preferably none.

Has an appropriate license.

That means something like CC0, not a code licence like MIT, BSD, Apache, etc.
If you use a license badge, it should be SVG, not PNG.

Has contribution guidelines.

The file should be named contributing.md. Casing is up to you.

Has consistent formatting and proper spelling/grammar.

The link and description are separated by a dash. Example: - [AVA](…) - JavaScript test runner.
The description starts with an uppercase character and ends with a period.
Drop all the A / An prefixes in the descriptions.
Consistent and correct naming. For example, Node.js, not NodeJS or node.js.

Doesn't include a Travis badge.You can still use Travis for list linting, but the badge has no value in the readme.

Go to the top and read it again.

Cool list. While I dont think bs is the best solution an awesome list is always good to have.

@sindresorhus Hey, checking the status of this pull request. Do you have anything I need to change to get us on the list?

Please read the guidelines more closely. Multiple points not followed from it. Try going through the list point for point and check that you follow it. :)

And use your own email in https://github.com/therebelrobot/awesome-bootstrap/blob/master/code-of-conduct.md, not mine.

Ping

still planning to go back and get these fixed.

Ping

Closing for lack of response.
If you ever want to get back to this, open a new PR, and please also see #1363.


operator trustify-operator (0.1.0-alpha.2)

Automated changes by create-pull-request GitHub action

Closing in favor of https://github.com/redhat-openshift-ecosystem/community-operators-prod/pull/4745


Container signing

Issue: AAH-1265
https://issues.redhat.com/browse/AAH-1265
Depends on https://github.com/ansible/galaxy_ng/pull/1414

@MilanPospisil notice that there is a case when container is not a push but synced from a remote and those containers needs an extra parameter on the sign/ api as explained on https://hackmd.io/@rochacbruno/SkQmp8-09#1-Images-synced-from-remotes

Test failure unrelated, fixing in https://github.com/ansible/ansible-hub-ui/pull/2503

Test failures in container-signing.js are happening because nobody enabled container signing on CI.
Looks like https://galaxyng.netlify.app/config/container_signing/ documents how to enable it, if anyone can add this, please do, if not, I'll look into it after PTO.

https://github.com/ansible/galaxy_ng/pull/1434 must be merged first in order to merge this.


New theme: Vitae

Theme submission
Please make sure that you have read the theme submission guidelines before submitting a theme. The guidelines provide all relevant information and requirements that have to be fulfilled before the submission. Please tick the relevant boxes for your theme in the checklist below:
Link to my theme repository: https://github.com/dataCobra/hugo-vitae
I made sure that...

[X] the repository contains a good README.md describing my theme
[X] an open source license has been added to LICENSE.md
[X] all metadata have been added to theme.toml
[X] screenshots have been added in the images/ folder with the required dimensions
[X] in case I'm using a customized demo via the exampleSite folder that

[X] https://example.com is set as base url in exampleSite/config.{toml, yaml, json} to avoid the abuse of unused domains
[X] I tested that my theme's demo works with the content directory of gohugoio/HugoBasicExample

[X] I tested my theme against the gohugoio/HugoBasicExample

[X] I've checked the developer tools' console in my browser for error messages

[ ] in case my theme is using Hugo Pipes features like toCSS and PostCSS that I have committed the /resources directory with all generated assets, for my theme to work in the basic version of Hugo

N.B. By submitting a theme to the Hugo Themes Showcase you understand that you need to maintain your theme. You will need to keep an eye on whether your theme's demo generates on the Hugo website, whenever there is a new release. We are a very small team and we just cannot keep up opening issues in the various theme repositories to notify authors. Whenever a theme demo breaks and remains broken then at some point it will be removed from the list without prior warning. If you no longer wish to maintain a theme please let us know.
Feel free to ask questions. We're glad to help.

Hello Ben,
thank you for sharing this theme with the Hugo community. As far as I can see Vitae is a fork of Ink, which itself has been forked from the Ezhil theme. Could you highlight the changes that have been made that make Vitae distinct enough from Ink and Ezhil to list it as a new theme (not just a fork)?
While we always appreciate new theme submissions but also want to avoid multiple versions of a theme that are quite similar.

Hello @digitalcraftsman,
The differences can be looked up in the features of the README.md
or do you want me to explain theme in this issue? :slightly_smiling_face:

The frontend looks quite the same, but I used a different approach in the backbone of the theme.

The differences can be looked up in the features of the README.md
or do you want me to explain them in this issue?

I meant more a list of changes / additions so that users don't have to compare the feature list of Vitae and Ink / Ezhil. It's just easier to get an overview :wink:
After comparing your theme with Ezhil and Ink the list of changes / additions includes

being more GDPR-friendly
(Fully responsive, optimized for all kind of devices)
choosing FontAwesome icons for navbar
FontAwesome and Roboto(-Slab) as available fonts

Is there there more to add to the list that I may overlooked? :slightly_smiling_face:

I will try to make this clearer in the README.md :slightly_smiling_face:

Hey @digitalcraftsman,
I've changed the README.md to be more clear about what is new with Vitae and also some information about the foundation of the theme. :slightly_smiling_face:
What do you say about these changes?

That's looks good :+1:
While starting a local Hugo server to test your theme I've got the following error messages:
ERROR 2019/12/18 18:45:01 render of "page" failed: "/home/master/dev/github.com/gohugoio/hugoThemes/hugo-vitae/layouts/_default/single.html:28:19": execute of template failed: template: _default/single.html:28:19: executing "_default/single.html" at <$taxo>: range can't iterate over tags
ERROR 2019/12/18 18:45:01 render of "page" failed: "/home/master/dev/github.com/gohugoio/hugoThemes/hugo-vitae/layouts/_default/single.html:28:19": execute of template failed: template: _default/single.html:28:19: executing "_default/single.html" at <$taxo>: range can't iterate over tags

Are you able to reproduce them?

Did you try that with my exampleSite or with another example?

I fixed the issue. I forgot to remove a param in the exampleSite/config.toml for a feature that is WIP.

The error is now fixed and the demo looks fine.
Your theme should appear soon on Hugo's theme site. Next, I'll promote your theme on Hugo's official Twitter account.

Thank you very much. :slightly_smiling_face:

Would it be possible to credit the authors of the Ink (and maybe Ezhil) theme in the theme.toml as well?
You're already doing this in the README but there might come up a case were we're using the meta data provided in the theme.toml file.
Dir noch einen schönen Abend :wink:


feat: change function should return allways an array

The change function in https://github.com/surrealdb/surrealdb.js/blob/main/src/index.ts#L395 returns a single object or an array of objects.
I personaly think it would be nice to allways return an array, This can be done with a simple change this is therefore a discussion if that would be a good idea.

I had an idea of inferring the return type from the passed id, since it would only return an array if the first param is a table name, right?
If we can infer it by checking if the first param matches ":" we could predict that the return type is a single object and an array otherwise.
(We can safely do this since we already decide for the array with typeof id === "string" && id.includes(":"))
It could look something like this:
	change<Thing extends string, T extends object, U extends object = T>(
		thing: Thing,
		data?: Partial<T> & U
	): Thing extends `${infer Table}:${infer ID}`
		? Promise<T & U & { id: string }>
		: Promise<Array<T & U & { id: string }>> {
		const id = guid();
		return this.wait().then(() => {
			return new Promise((resolve, reject) => {
				this.once(id, (res) =>
					this.#output(res, "change", thing, resolve, reject)
				);
				this.#send(id, "change", [thing, data]);
			});
		});
	}

I wasn't able to get the types to become properly compatible but I think the idea gets through.
With that the consumer could work comfortably with the change method with the correct return type for the use case.

@btmnk Looks good! woll give it a try. I currently don't know what happens if the Table only has 1 row...

Did an implementation of the above concept in #80


Add AIMNet2 model

Modulus Pull Request
Description
This is a Modulus port of AIMNet2 model.
Checklist

[x] I am familiar with the Contributing Guidelines.
[x] New or existing tests cover these changes.
[ ] The documentation is up to date with these changes.
[ ] The CHANGELOG.md is up to date with these changes.
[x] An issue is linked to this pull request.

Dependencies

/blossom-ci

/blossom-ci

/blossom-ci

/blossom-ci


Understanding response of /transactionInfo.pinpoint

[x] I have checked the FAQ, and issues and found no answer.

hi,
I'm trying to make application which uses Pinpoint web APIs, I'm unable to understand the response for this API: /transactionInfo.pinpoint
full api request is something like this:
http://myweb-pinpoint.com/transactionInfo.pinpoint?agentId=<..>&spanId=<..>&traceId=<..>&focusTimestamp=<..>&useStatisticsAgentState=<..>
And the response is:
{
    "transactionId": "tid",
    ...
    "callStackIndex": {
        ...
    },
    "callStack": [
        [
            "",
<PHONE_NUMBER>841,
<PHONE_NUMBER>841,
            false,
            "my-tomcat-app",
            0,
            "1",
            "",
            true,
            true,
            "Servlet Process",
            "/internal/healthcheck",
            "01:14:15 841",
            "0",
            "0",
            "0",
            "0",
            "",
            "100",
            "TOMCAT",
            "Gha4oasdfgZ9rfOhde4w",
            true,
            false,
            true,
            " "
        ],

    ],
    "applicationMapData": {
        "nodeDataArray": [
            ...
        ]
    }
}

I'm trying to understand the "callStack" part. Tried to check Angular code for rendering this data but was not able to understand though. Any help is appreciated.

EDIT:
Figured out that data is as follows:
{
  callStackIndex.keys[i]: callStack[callStackIndex[i]]
}


kivy: 2.0.0 -> 2.1.0

Description of changes
https://github.com/kivy/kivy/blob/ce0bf8c7dcc7cdf93a32c5fb9965cc973e373357/doc/sources/changelog.rst#core-providers
("Use NSString instead of..." patch seems to have been upstreamed)
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

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

tested by using an external dependent (smoopi) build on this, it works... (and its now requires this version)

23.05 Release Notes (or backporting 22.11 Release notes)

[x] (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.

removed the comment about the removed patch too
this comment was added along with switching from fetchPypi to fetchFromGitHub
i'm not aware of a reason to switch back to fetchPypi


support geo type mapping resolutions

coming from #389
e.g. query all counties of the state of California
possible mappings:

nation -> state
state -> county
hrr -> state

this might be more easily implemented in delphi_utils.geomap, possibly as an extension of /variation on get_geo_values():
https://github.com/cmu-delphi/covidcast-indicators/blob/261b3a3868abd1527d8ac9867a8aca78f8ef46eb/_delphi_utils_python/delphi_utils/geomap.py#L559-L576

Now that https://github.com/cmu-delphi/covidcast-indicators/pull/1159 has been merged, the following has to happen:

[ ] @korlaxxalrok to pull the release lever in covidcast-indicators (no earlier than Monday 9 Aug)
[ ] design a syntax for specifying contained/child regions as a URL parameter of a covidcast request
[ ] implement in the API server by decoding the new syntax and applying delphi_utils.geomap.GeoMapper.get_geos_within()

I don't have any huge preferences on syntax, so long as we avoid the possibility where the same geo_id parameter value could be interpreted as multiple geo types. @sgratzl may have guidance?


loading dataset from local files

Required prerequisites

[X] I have searched the Issue Tracker and Discussions that this hasn't already been reported. (+1 or comment there if it has.)
[X] Consider asking first in a Discussion.

Motivation

It seems like currently we can only load dataset from huggingface Datasets, it would be great if safe-rlhf supports loading dataset from local files.
Solution
Ideally, we can have something like:
python train.py --data_path path/to/local/files ...

class AlpacaDataset(RawDataset):
    NAME = 'alpaca'

    def __init__(self, data_path: str=None) -> None:
        if data_path is not None:
            type = data_path.split(".")[-1]  # e.g. json
            self.data = load_dataset(type, data_files=data_path, split="train")
        else:
            self.data = load_dataset('tatsu-lab/alpaca')['train']

    def __getitem__(self, index: int) -> RawSample:
        data = self.data[index]
        input = (  # pylint: disable=redefined-builtin
            ' '.join((data['instruction'], data['input'])) if data['input'] else data['instruction']
        )
        answer = data['output']
        return RawSample(input=input, answer=answer)

    def __len__(self) -> int:
        return len(self.data)

Alternatives
No response
Additional context
No response

Ideally, we can have something like:
python train.py --data_path path/to/local/files ...

Hi @haorannlp, thanks for raising this! This feature would be really useful but we should evaluate some of its implementation details.
The point here is passing a dataset from an arbitrary file path would be difficult to determine which preprocess procedure we should use. From your example in https://github.com/PKU-Alignment/safe-rlhf/issues/12#issue-1718960322, you are assuming the --data_path argument is passed with:
python train.py --data_path path/to/local/alpaca.json ...

However, the method we used for different datasets can vary. We cannot validate and determine whether the file path is the Standard Alpaca dataset rather than something else.
Another concern is, in your dataset abstraction, you can pass multiple datasets for training at once instead of only one dataset (e.g., Alpaca only). For example:
python train.py --datasets alpaca hh-harmless-dialog:0.7 hh-helpful-dialog:0.8 --other-options

This will use 100% Alpaca dataset + randomly split 70% HH harmless dialog + randomly split 80% HH helpful dialog for training.

For your use case, you can have:
from datasets import load_dataset
from safe_rlhf.datasets import AlpacaDataset

class AlpacaLocalDataset(AlpacaDataset):
    NAME = 'alpaca-local'

    def __init__(self) -> None:
        self.data = load_dataset('path/to/alpaca.json')['train']

then use the following in the command line:
python train.py --dataset alpaca-local ...

自定义的dataset文件，命名成myname.py ，然后保存在datasets/raw目录下面吗？不知为何，没有生效

自定义的dataset文件，命名成myname.py ，然后保存在datasets/raw目录下面吗？不知为何，没有生效

@flaviadeutsch 该文件应该在导入 dataset 前被执行。例如你可以在 safe_rlhf/datasets/__init__.py 中添加一个 import statement.

safe_rlhf/datasets/__init__.py 中本来就有 from safe_rlhf.datasets.raw import *，还需要自己再import吗？

需要，from xxx.raw import * 是 import 文件 raw/__init__.py 中的 member。并不会自动 import 文件夹下的文件。你也可以在 safe_rlhf/datasets/raw/__init__.py 添加一行 import 你自己的数据集，或者在你的 train script 中 import.


Unquoted attributes that contain slashes can't be parsed

see https://github.com/prettier/prettier/issues/8210

Reported at angular/angular#36932.


Nginx Documentation

Rough draft is complete.  Still needs further revision and editing, but I wanted to share what I've gotten done so far.
View-able at http://smcdougall.github.io/Pico/nginx/
Any input is appreciated. :smiley:

Please refer to #343 for feedback about this PR. Thank you @smcdougall for this PR! :+1:

I wasn't sure about those.  I had just based it on another page, so I left them in.  Thanks.

Thanks, those semi-colons are the bane of my existence.  I leave them off at least once every time I edit a config file. >.<
Unfortunately, it won't work in the Pico location block.  It needs to send the variable externally to PHP, and because of how the blocks are processed, it won't "remember" it from the Pico block when it gets to the php block.
It's a two-step process, first the url is rewritten to "/?some/page/url" using the Pico block, then it checks it again and matches it against the PHP block.  It then sends the page to php-fpm for external processing, which is when it needs to know the variable.

Ah, ic, thanks for the explanation :smiley:

Huh, wow, I did not notice that.  Why does it work in nginx.md then?  Wouldn't they be processed the same?

Oops, that was supposed to reissue the same commit... guess I did it wrong. :laughing:

Ah, no, Kramdown does support fenced code blocks, but it requires you to add a empty line before and after the fenced code block.

Ah, okay.  Should be fixed now.

Yeah, that was written with the original example in mind.  What do you think it should say?
"While the example... starting point, here we will provide a more in-depth look at Nginx configuration."

you're also covering the general webserver config, so shouldn't it be four?

I don't know, I counted it separately since it wasn't something specific to Pico...

Getting started

General Server Configuration
Denying Access to Pico’s Internal Files
PHP Configuration
URL Rewriting

I used "Getting Started" as an introduction to the tutorial portion of the page.  Before that, it was more informative than instructive.  It was just meant to be a transition, so I'm not sure if all the other steps should be part of it.
If you're configuring the URL Rewriting, you aren't really "getting started" anymore.
It would work okay as a subsection though, but maybe called something other than "Getting Started".  "Nginx Configuration" for example, but something that isn't also the title of the page.

I don't think that blocks is a actual "name". Just "Nginx's server configuration is broken into sections." should be fine :smiley:

https://www.nginx.com/resources/wiki/start/topics/examples/server_blocks/

Can you please add a URL to a tutorial how to configure HTTPS with Nginx (plus a sentence that SSL isn't covered by this example, but its use is recommended)? Nowadays HTTPS is what you should want to use 99% of the time :smile:

Good idea, I'll probably link to Let's Encrypt.  I've tried it, and it's really easy to use.  Much more so than other solutions I've tried.

since they're disabled unless specified in Nginx, but this isn't always the case in Apache

This is also the case in Apache, but it's a common misconfiguration. I'm not sure whether this is true for nginx, too.

I'm not sure.  I had too look up the configuration of Indexes when I was writing that part.  I think this is what you have to use: http://nginx.org/en/docs/http/ngx_http_autoindex_module.html
I had to search for it, and hadn't come across it at all beforehand.  I've never seen any examples specify "autoindex off" in the same way that many .htaccess files do.
So yeah, I'm not sure, but I haven't really seen it mentioned anywhere as an issue.

This rule also affects non-Pico subdirectories, isn't it? Especially blocking access to content globally may cause trouble with other software. Does Nginx allow cascading location blocks? Otherwise a users needs to adjust the base path (i.e. / or /pico/) manually :unamused:

Yes, it blocks access to them anywhere.  I thought it'd be better than having to customize it depending on your subfolder.  I found the subfolder issue a little annoying, so I tried to condense it all into the Rewrite section.  Having "Pico in Document Root" and "Pico in a subfolder" for every section sounded too confusing.  I've been trying to avoid differing configurations wherever possible.
Nginx does allow nesting location blocks though, so there is some potential there.
Keep in mind though, this configuration only affects a given virtual host.  But, I guess I could see the issue if they were for example, running Pico in /pico/ and a forum in /forum/, /forum/content/ would then be blocked.
sigh This is the trouble with coming up with a single example that works in all cases.

In general: Shouldn't this section come after the PHP configuration or is this necessary because of Nginx's processing order? The document should follow a golden thread from "General Configuration" to "Pico's configuration" - at least as long as Nginx's configuration order doesn't foil it.

It needs to come before PHP.  If it comes after PHP, then Nginx will match that rule first, meaning any PHP files (config.php for example) won't get denied.

The difference between Apache and Nginx is that Linux distributions ship more intelligent default configurations for Apache, so Apache users don't have to deal with this on their own.

Ouch.  lol.
How would you have me explain the differences then?  It's still somewhat internal vs external, as mod_php is part of Apache, while php-fpm is a separate software from Nginx.
I feel like most of your issue would be addressed by removing is more streamlined.  It and combining the two sentences.  Maybe also drop It does not handle PHP itself., to minimize the comparison between the two.

Your example isn't OS-Dependant. Apart from file paths (i.e. where the FastCGI socket is located, more precisely /var/run/php5-fpm.sock) you can use the same config for Windows :smiley:

Good to know, but I mainly wanted a reason why a user shouldn't copy and paste it (and also, I haven't tested it on anything but my own server).  Should I just say that configuration "differs slightly" depending on your OS?

Shouldn't this be try_files as discussed in #343 (comment)?

I never got a chance to test that and I guess it got lost in the discussion afterward.  If you know it to be working, I'll replace the if statement with that.  Otherwise I want to test it first and make sure it protects against the security issue.

Yay, I've caught up with you. :wink:
This comment thread is just about as out-of-order as it could be.

I'll probably link to Let's Encrypt.

Have you tried Let's Encrypt before?  I believe it's fairly new.  Just wondering if it should be a casual recommendation or a project-backed one.  Probably something like "You can check out" vs "We recommend."

Why is Document Root formatted as code?

Sometimes I like how it formats things.... :unamused:

Reading this, we can save a round trip by directly rewriting to /index.php?$uri&$args.

I don't know if it really saves a "round trip" or not.  My assumption for how it works is that it would just "tack on" the name of the index file if unspecified.
Either way, I'll add index.php to match it up closer with .htaccess.

Considering you're from Germany.... it would probably be in poor taste to call you a "Documentation Nazi", huh? :unamused:
In case that's too lost in translation, It was a play on the term "Grammer Nazi" more than anything.
Seriously, I appreciate all the help. :wink:
...debated way too long before sending this comment :unamused:

I think it's a good idea to let the components directly link to the appropriate sections above :smiley:

:+1:

I've tested test try_files $uri =404; and it seems to work properly.  Oddly enough, even with cgi.fix_pathinfo = 1, my server returned an "Access Denied" message from PHP (it was not a message from Nginx).  There must be another security option somewhere else in Ubuntu's default config that I don't know about.

:unamused: I just realized I could have replied to each of your comments inside the line-note.
I don't know,  I guess I just thought that button was for adding a new note. :disappointed:

Okay, I've finished reading. Reading and fixing should never happen simultaneous :wink: You can btw directly answer to my comments by clicking the Add a line note button, otherwise the comments get completely out of order and it's extremely hard to follow the discussion. Anyway, I'll answer your comments here this time.

General notes:
I love it! :heart: Sure, there are small issues, but none of them is even close to being "mission critical" :smiley: As you've already noticed (:smile:) I'm a perfectionist (:wink:), so please don't be offended by so many comments - they are all just very minor issues I stumbled over. I could have fixed them after merge myself, but it's your document, so I thought it would be better to tell you where I see open issues instead.
After you've finished your work I'll read it again and merge it. Again, I cannot emphasise enough that the document is great! :+1:
Section "Getting Started", first paragraph: https://github.com/picocms/Pico/pull/345#issuecomment-215705468

While the example... starting point, here we will provide a more in-depth look at Nginx configuration.

Yeah, I like that! :+1:
Splitting the document into subsections: https://github.com/picocms/Pico/pull/345#issuecomment-215708293

I used "Getting Started" as an introduction to the tutorial portion of the page.

True. "Nginx Configuration" sounds good. This is completely up to you, it just came to my mind immediately after reading this sentence.
How to name blocks: https://github.com/picocms/Pico/pull/345#issuecomment-215708912
Then maybe simply just "Nginx's server configuration is broken into blocks." or something like that? I just stumbled over it while reading :smile:
Nginx and HTTPS: https://github.com/picocms/Pico/pull/345#issuecomment-215709592 + https://github.com/picocms/Pico/pull/345#issuecomment-215731584
Yeah, I'm using Let's Encrypt, too (and I love it). 353a17bbc3f623e4728b92dd6810c54d75065e6f is a absolute perfect solution! :+1:
Directory listing (autoindex off; and Options -Indexes): https://github.com/picocms/Pico/pull/345#issuecomment-215711817
Ah, I see. Yeah, then it's probably best to simply remove the half sentence in brackets as it doesn't apply to nginx anyway.
Denying access globally: https://github.com/picocms/Pico/pull/345#issuecomment-215719269
I look forward to your solution for it :smiley:
Moving the "Deny access" section below "PHP Configuration": https://github.com/picocms/Pico/pull/345#issuecomment-215719269
Ah, okay, thanks for clarifying this!
PHP with nginx vs. PHP with Apache: https://github.com/picocms/Pico/pull/345#issuecomment-215724461
Yep, simply remove the comparison, it's just fine then :smiley:
OS-Dependant examples: https://github.com/picocms/Pico/pull/345#issuecomment-215725785
Hmm... I don't have a real solution for this. But you had one :wink: 353a17bbc3f623e4728b92dd6810c54d75065e6f is just fine!
try_files instead of the very complex location regex, fastcgi_split_path_info and if: https://github.com/picocms/Pico/pull/345#issuecomment-215726643 + https://github.com/picocms/Pico/pull/345#issuecomment-215756031
Yes, I've tested it, works like a charm. :smiley:

[That line you removed about answering me this one time]

My excuse is that I was thinking that adding a new line note would put it at the end of the thread anyway.  I didn't realize until I clicked on it that it would create a little sub-thread for the reply.  It makes sense though, and seems handy.  I'll use that next time.

I'm a perfectionist (:wink:)

Me too.  I understand. :laughing:

try_files instead of the very complex location regex, fastcgi_split_path_info and if

So it's safe to remove fastcgi_split_path_info?  I haven't tried that myself, but the point of the line seems to be to separate out any path following the .php file (example.com/index.php/some/url) and give it to PHP as a variable.  Since Pico instead uses a query string internally, I can see why that wouldn't be needed.  Just wanted to make sure there's no other purpose it might server for us.
Honestly, I've just been including the line because I've seen it a lot in examples... I don't actually know what purpose it serves on the PHP side of things or what that path information is used for. :sweat_smile:

Yes, you can safely remove fastcgi_split_path_info. You can also use a much simpler regex like location ~ \.php$ { }.
The purpose of this directive is to imitate the PATH_INFO feature to allow SEO-like URLs out-of-the-box. PATH_INFO actually is part of the official CGI specification (see https://tools.ietf.org/html/rfc3875#section-4.1.5), but is practically limited to Apache (see https://httpd.apache.org/docs/2.2/mod/core.html#acceptpathinfo). Alternative webservers (like nginx - or IIS, lighttpd, httpd...)support PATH_INFO with workarounds only. Many configurations out there don't have those workarounds enabled. Thus it's usually a bad idea to use PATH_INFO. However, there are (better) alternatives - like QUERY_STRING.

sigh So I don't really have a better option for the denial rule at the moment.  I added a little note about it in-case it causes issues.  I don't really think it's worth the extra effort at this point when I'll probably have to rewrite half the document for 1.1 anyway.
In the future, a solution might be a location block containing all the Pico rules.  Using a setup like that, there should be a way to state Pico's location once and have all the other rules conform to it.
I experimented a little while back with adding a separate root declaration inside of a location block and it did successfully change the $document_root variable inside the location block.  The problem was that it didn't impact $uri at all.  I think this was due to the change being after Nginx had created the $uri (it was inside the rewrite rule block).
Perhaps by declaring a Pico location with a new root, we could treat all the nested locations (the existing blocks) as if Pico were installed in Document Root.  If this worked, we could potentially provide one Nginx example that would work no matter where Pico was installed.  You'd enter Pico's location once and all subsequent rules would use it.  This would also make all our rules affect only Pico, and eliminate the need to worry about interfering other software on the same virtual host.
Just speculating at the point, but it would be worth looking into in the future. :smile:

Also, in regards to adding a new subsection to the document where Getting Started is...  I'm not sure it's necessary.  I'm just looking at the rendered page and imagining adding a new header.  It feels a little redundant.  There would only be two sections not inside it (Example Config and Advanced Tips), so it feels a bit like the entire document would be inside the new section.  The document as a whole is about "Nginx Configuration", and every section in it is directly related to that topic (except for where I've already broken it down).
I don't know.  As always, I'm open to any arguments you have in favor of it, I just don't think it adds any benefit right now.

And, I think that's everything.  Let me know if I've forgotten to address any points we discussed.
And sorry for the extra long reply. :sweat_smile:

Using root sounds promising, I look forward to your changes for Pico 1.1. I'm fine with not adding a superior section, it was just an idea. Maybe when you update the document for Pico 1.1. We'll see :smiley:
I've merged your PR with some very minor changes (see fa07158a032b22cdc841e0ff0208f58096c57c93). :tada: Thank you for your efforts! :+1: :smiley:


changed formatter name

Summary
Changing the formatter name from Image to ImageName so we don't get the Vue warning: Vue warn]: Do not use built-in or reserved HTML elements as component id: Image
Fixes #9235

This PR would have produced a compile warning
 WARNING  Compiled with 1 warning                                                                                10:26:28

 warning  in ./shell/detail/pod.vue?vue&type=script&lang=js&

"export 'IMAGE' was not found in '@shell/config/table-headers'

Which when resolved would have avoided https://github.com/rancher/dashboard/pull/9315


Error when try to use the Test Option

Always crash when i try to change test for True in the startup.py

Do you have details about the error?


Remove unreachable code so we can pass go vet

This makes gocode pass go vet ./....

It will break compilation on older versions of Go. Although to be honest, I'm not sure if gocode compiles there. So, I'll probably accept the patch, will think about it for a few days. Probably nobody uses Go versions 1.4 and older.

Go is pretty unique among programming languages in that most of the community is using a recent version. Upgrades are pretty smooth because the language doesn't change much. The Go team only officially supports the two most recent major versions (currently 1.8 and 1.9). Older versions do not receive security updates. It's up to you, but I think it's ok to not support 1.7 and older.


Programmatically raise click events TextField

Is there a way to simulate click event for TextField ? I am using HTML 5 validation to validate a form that has textfield. I populated the helperText and helperTextValidationMsg to indicate a particular field is missing. In validation method I want to raise onclick so that gives the error is similar to onBlur for TextField.

Currently your best bet is to give it an id and get it by id.
But in your particular case a better choice is to grab a reference to the form element and call a method named something like checkValidity() (not sure if that is the correct name), it will even return you a value that indicates whether everything is correct.

@cromefire I have implemented the functionality to see if a field is valid using html5 checkValidity. But I want to simulate the functionality as if the user touched the Textfield. Is this possible ?

const ele = document.getElementById("<some id>");
ele.click();

You can just use plain dom methods, we just don't export the input element yet


cmd/vet: possible to get a printf false positive with big.Int

What version of Go are you using (go version)?

$ go version
go version go1.12 linux/amd64

Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/karalabe/.cache/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/tmp/go"
GOPROXY=""
GORACE=""
GOROOT="/opt/google/go"
GOTMPDIR=""
GOTOOLDIR="/opt/google/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build576186895=/tmp/go-build -gno-record-gcc-switches"

What did you do?
Here's a full repro:
$ mkdir /tmp/go
$ GOPATH=/tmp/go
$ go get github.com/karalabe/govetrepro2/...
$ cd /tmp/go/src/github.com/karalabe/govetrepro2/
$ go test ./...
# github.com/karalabe/govetrepro2/bn256/google
bn256/google/main_test.go:16:3: Logf format %d has arg n of wrong type *math/big.Int
ok  	github.com/karalabe/govetrepro2/bn256/cloudflare	0.065s
FAIL	github.com/karalabe/govetrepro2/bn256/google [build failed]

What did you expect to see?
The exact same test code (main_test.go) is present in both bn256/cloudflare and bn256/google. I expect either both to fail with the format error, or neither of them.
What did you see instead?
Cloudflare always passes, Google always fails.

Thanks for the detailed report! This is a false positive, as math/big.Int implements fmt.Formatter, so the printf vet check should skip it.
This tiny program reproduces the bug:
$ cat f.go
package p

import (
        "math/big"
        "testing"
)

func f(t *testing.T) {
        t.Logf("%d\n", big.NewInt(4))
}
$ go vet f.go
# command-line-arguments
./f.go:9:9: Logf format %d has arg big.NewInt(4) of wrong type *math/big.Int

It seems like the issue is that vet assumes that a program must import fmt to implement fmt.Formatter. Which is correct, but not the way it's used in the vet check. In this case, it's imported in the package that implements fmt.Formatter, which is math/big, and not the current package.
You can see that this is the cause because adding an import _ "fmt" makes the false positive go away.
I'll send a CL to the tools repo later today, and I'm sure we can include a backport for 1.12.1's cmd/vet. /cc @alandonovan

@alandonovan now that cmd/vet is out of repo, how can we easily backport single commits? With git it should be possible to cherry-pick the x/tools commit into cmd/vendor/golang.org/x/tools, but I don't know if you have a better plan.

I also messed up the "Fixes" line in the x/tools commit, as usual. But that's actually good, as the issue isn't fixed in neither master nor 1.12.

I don't have any better ideas than simply applying the same change to both repos. The x/tools/go/analysis tree is subject to the release freeze, so I don't think there's any situation in which they should deviate.

Ah right, I keep forgetting that x/tools has a 1.12 branch as well. I presume we can just cherry-pick into its 1.12 branch, and update Go's 1.12 branch to vendor x/tools' updated 1.12 branch.

The x/tools piece was merged over a month ago; this just needs someone to update the vendored copy into a Go 1.12.x release. Unassigning myself, as I'm not needed for that bit.

(for completeness, the 1.12 tools CL was https://go-review.googlesource.com/c/tools/+/164657)


[OSD-8943] ocm-agent health check

What type of PR is this?
(feature/refactor)
What this PR does / why we need it?
As an SRE I want the ocm-agent to present a health URL which can be polled to determine the agent's operating health.
Which Jira/Github issue(s) this PR fixes?
Fixes # OSD-8943
Special notes for your reviewer:
OSD-8943 acceptance criteria didn't mentiion /readyz endpoint, but I felt it made sense to add it to the  healthcheck package
Pre-checks (if applicable):

[ ] Tested latest changes against a cluster
[x] Included documentation changes with PR
[x] Ran make lint command locally to validate code changes
[x] Ran make test command locally to validate code changes

/label tide/merge-method-squash

Codecov Report

Merging #12 (58b2db7) into master (f81d2b2) will increase coverage by 1.56%.
The diff coverage is 34.69%.

@@            Coverage Diff             @@
##           master      #12      +/-   ##
==========================================
+ Coverage   26.27%   27.84%   +1.56%
==========================================
  Files           7        8       +1
  Lines         137      176      +39
==========================================
+ Hits           36       49      +13
- Misses        100      124      +24
- Partials        1        3       +2

Impacted Files
Coverage Δ

pkg/cli/serve/serve.go
13.33% <0.00%> (+0.21%)
:arrow_up:

pkg/healthcheck/handlers.go
32.50% <32.50%> (ø)

pkg/types/handler.go
100.00% <100.00%> (ø)

pkg/webhookreceiver/handlers.go
84.61% <100.00%> (ø)

/lgtm
/hold
Adding hold for others to review

/approve

/unhold


How do you refer to yourself?

The weekly usually refers to people in the third person:

JP Simard rewrote the entire compiler to be much faster.

What happens if the author and the subject of the sentence are the same person? For example, in issue 39, I wrote:

Brian Gesiak sent a pull request to mark internal variables as final, which works around the bug in some cases.

Should I instead write this?

I sent a pull request to mark internal variables as final, which works around the bug in some cases.

On the one hand, it's weird to refer to myself in the third-person. On the other, "I" isn't in line with the rest of the document.
Thoughts? 🙌

Although I can image it sounds weird, I think it's the easiest to refer to yourself in 3rd person. Because there are different people writing the Weekly Brief now, using "I" can become confusing.

Yeah -- I've done both in the past I think (can't remember).
But, I think I agree that 3rd-person is probably the least confusing.

Agree, third person it is. Thanks!


[Request-For-External] [Event Request] Page 9223 "Item Statistics Matrix"

Describe the request
I want to calculate and display quantity values in the Item Stat. Matrix. Therefore, I request to add a new OnBeforeCalculation event and to change the global IncludeExpected variable to protected.
local procedure Calculate(SetColumnFilter: Boolean) Amount: Decimal
begin
	//NEW BEGIN
	OnBeforeCalculation(ItemBuffer, Amount, Qty, Rec.Name, SetColumnFilter);
	//NEW END
	case ItemBuffer."Line Option" of
		ItemBuffer."Line Option"::"Profit Calculation",
		ItemBuffer."Line Option"::"Cost Specification":
			case Rec.Name of
				ItemBuffer.FieldCaption("Sales (LCY)"):
					Amount := CalcSalesAmount(SetColumnFilter);
				ItemBuffer.FieldCaption("COGS (LCY)"):
					Amount := CalcCostAmount(SetColumnFilter);
	//...
[IntegrationEvent(true, false)]
local procedure OnBeforeCalculation(var ItemBuffer: Record "Item Statistics Buffer"; var Amount: Decimal; var Qty: Decimal; Name: Text; SetColumnFilter: Boolean)
begin
end;

//NEW BEGIN
protected var
        IncludeExpected: Boolean;
//NEW END

Additional context
I want to calculate and display quantity values in the Item Stat. Matrix.
I can add them to the Dim. Code Buffer, but in order to calculate the values i need a new event before the default calculation and also access to the global IncludeExpected variable.
Internal work item: AB#544578

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


fixed command to get cores hopefully

Closes #13 hopefully

Version 1.1.1 released in Pypi, ok to run pip3 install findpi -U now.


yabai is not working after updating macos

I recently updated my mac to Sonoma 14.5. After updating, yabai was not working. I am trying to uninstall and install everything again but it is still not working. Do you have any suggestion? Below are my installation steps:
brew install koekeishiya/formulae/yabai
cp /path/to/my/yabairc ~/.yabairc
yabai --start-service
# then I gave yabai accessibility
yabai --restart-service

and nothing happen with my windows
Thank you for your consideration.

Have you tried this steps here for reinstalling?
https://github.com/koekeishiya/yabai/wiki/Installing-yabai-(latest-release)#updating-to-the-latest-release
and yes you also have to go to Privacy & Security > Accessibility remove yabai from there before re-installing, then go back and allow it

Thank you for your response.
I tried this to reinstall the latest and I got this error even using sudo
sudo curl -L https://raw.githubusercontent.com/koekeishiya/yabai/master/scripts/install.sh | sh /dev/stdin

Password:
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  3000  100  3000    0     0  64079      0 --:--:-- --:--:-- --:--:-- 65217
Error: User does not have write permission for man-page target directory '/usr/local/share/man/man1'.

Do you have any suggestion? Thank you for your help.

Hi @ovidb , @koekeishiya , sorry for bothering you guys lately. Could you please take a look at my issue? Thank you a lot for your consideration

Solved here: https://github.com/koekeishiya/yabai/issues/1222#issuecomment-2259682586


Project status

This project seems to be quite heavily used, but has not received any updates since 2015. @miki725 is it dead?

sorry. initially created for a tool at work. tool no longer used... didnt had a chance to dedicate much time due to other load. plan to catch up with some bugs in upcoming holiday... or find a need for it at work again so I can allocate some time to bring it back to live

No worries! I might be available to assist if you would find that helpful.

Please update the package, and also create a vids tutorial

Great Tool.
Over at graphene-django the creator also was taken in a different direction at work. Fortunately, after some effort for sure, a community is now collectively maintaining the project and issuing releases. Just food for thought. Thank you for creating this project.

@miki725 if you can't maintain it anymore, please transfer ownership to https://github.com/jazzband. It's an organizastion of django open-source maintainers, aimed toward taking maintainer of projects which the original maintainer can't maintain anymore. Please do it. If you don't, django-rest-framework-bulk will rot and die, and many projects and people will suffer.

@miki725 can you consider the proposition? This project is too popular and important to just be left abandoned.