Make branch name changeable

Summary
I want to change title when tachikoma was sent a pull request.
Tasks

[x] Make branch name title changeable.
[x] Write a document for the key of branch_name.

Coverage remained the same at 67.647% when pulling 41eba57307f6234fe46ebc87c1dc5356c785735e on sachin21:make_branch_name_changeable into 8adcad1ec54a7c518c29209245596a627c403fcb on sanemat:master.

Kicked houndci-bot. I didn't change anything.

Coverage remained the same at 67.647% when pulling 54e220d6371311f95590f7226def03e54cd6b4c0 on sachin21:make_branch_name_changeable into 8adcad1ec54a7c518c29209245596a627c403fcb on sanemat:master.

Coverage remained the same at 67.647% when pulling 54e220d6371311f95590f7226def03e54cd6b4c0 on sachin21:make_branch_name_changeable into 8adcad1ec54a7c518c29209245596a627c403fcb on sanemat:master.

Coverage remained the same at 67.647% when pulling 54e220d6371311f95590f7226def03e54cd6b4c0 on sachin21:make_branch_name_changeable into 8adcad1ec54a7c518c29209245596a627c403fcb on sanemat:master.

Coverage remained the same at 67.647% when pulling 86f747c93ba93244daa42775d38a238022ac92a6 on sachin21:make_branch_name_changeable into 8adcad1ec54a7c518c29209245596a627c403fcb on sanemat:master.

I think above RuboCop's issues should not be fixed. because does not relate to this pull-req and other lines offend cops. So I suggest creating a pull-req for fix RuboCop issues.

I'll accept this pull request, would you fix the conflicting file? lib/tachikoma/application.rb

Thank you so much! but I'm sorry I'm in work. So I'll fix conflicts at tonight.


Even if you change the name of function, only the cache is changed

:thinking: Sorry, I didn't get what you meant.

There was not enough explanation:(
When changing the function name using F2, only the cache is changed, the actual function file position and the function command path are not changed.
However, it certainly happens, but it does not always happen.

I'm not sure about the details, but it happened even with v2.0.0.

:tada: This issue has been resolved in version 3.0.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Custom TS453Dmini

{"model":"DS920+","version":"7.2.0-64551","jun":"1","lkm":"test","maxlanport":"7","internalportcfg":"0xffff","netif_num":"2","vid":"0x88aa","pid":"0x88aa","modules":"r8125"}

delete builds

delete builds


Secondary storage isn't getting attached to the cluster from v6.0.0 product version

Please note that secondary storage isn't getting attached to the cluster from v6.0.0 product version of Red Hat OpenShift Container Platform on VPC landing zone.
Please see below attached screenshot.
It used to attach the 300 GB secondary storage in previous product versions such as v5.31.2.
I was using the same override.json file for cluster creation before too.

override.json

Fixed in v6.0.1


[release-1.12] Update proxy sha (#100)

June CVE fix

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@dgn

@Kmoneal: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio_release-1.12
ee1fe861f1be3bae87fda1a355bd49f5f51d7f58
link
true
/test release-notes_istio_release-1.12

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Kmoneal: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio_release-1.12
ee1fe861f1be3bae87fda1a355bd49f5f51d7f58
link
true
/test release-notes_istio_release-1.12

integ-telemetry-mc_istio_release-1.12
ee1fe861f1be3bae87fda1a355bd49f5f51d7f58
link
true
/test integ-telemetry-mc_istio_release-1.12

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test release-notes_istio_release-1.12

/test integ-telemetry-mc_istio_release-1.12


Added policy evaluation section

Description of changes: The only place policy evaluation was described in any detail in the docs was in the terminology section. The topic is big enough to warrant its own section. So I pulled the existing text out and expanded it. In the process I changed some of the terminology/description to more closely match the code and formal spec.
Added page rendered
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Thanks! I noticed that the nav_order indicator at the top of the file was inadvertently changed to nav*order -- might need to change back for the docs-generation stuff to work?

Simliar no*toc.  Maybe other occurrences


Fix windows maven package failed.

Result:
Fixes #402
If there is no issue then describe the changes introduced by this PR.

@leizhiyuan So sad, I need a windows env to fix the shell.

or maybe you can set
 <phase>compile</phase>

to test? so user can compile ,but they can not run test in console.

@leizhiyuan Now the phases are compile and test, the propose is trying to start nacos server before test and ending it after test.

@leizhiyuan Setting to test phase could not confirm nacos server install before running test cases, I try to set to test-compile, It can work fine on mvn clean install -Dmaven.test.skip=true.
But still should use -DskipTests to avoid this execution when running mvn package. So just using mvn clean package -DskipTests instead of mvn clean package -Dmaven.test.skip=true, It can work fine.


[Tracking Issue] PyTorch Frontend Operator Support

torch.nn.functional operators
non-linear activations

[ ] elu
[ ] relu
[ ] relu6
[ ] celu
[ ] hardsigmoid
[ ] sigmoid
[ ] hardtanh


squash: Start update of examples.

started the express example.  1 failure in the curl statement
Signed-off-by: Lucas Holmquist<EMAIL_ADDRESS>
Proposed Changes

Description

Fixes Issue #249
Version:

I noticed something with the express example.  The last curl statement for v03 fails with an "Invalid Payload" error.
A Binary One with Base 64 Encoding
curl -X POST \
<EMAIL_ADDRESS>\
     -H'Content-Type:application/json' \
     -H'ce-specversion:0.3' \
     -H'ce-type:com.github.pull.create' \
     -H'ce-source:https://github.com/cloudevents/spec/pull/123' \
     -H'ce-id:45c83279-c8a1-4db6-a703-b3768db93887' \
     -H'ce-time:2019-06-21T17:31:00Z' \
     -H'ce-datacontentencoding:base64' \
     http://localhost:3000/

If you remove that ce-datacontentencoding header, it will work,  but I don't think that is the right approach.   The error is happening during this section of code:  https://github.com/cloudevents/sdk-javascript/blob/master/src/event/spec.ts#L33, when testing if the data is Binary.  but at this point,  the data, at least in the example, is an object, so that check fails
@lance  thoughts?

@lholmquist interesting... I've worked out what the problem is. See https://github.com/cloudevents/sdk-javascript/issues/284. I've got a fix, but need to add tests and check behavior with the structured receiver as well.

@lholmquist ok I have pushed a PR for a fix. I don't think that this deserves a quick version bump because it only affects encoded data on v0.3 events.


Update middleware types

Description

Update middleware types and fix ordering for native SQ queries

Breaking Changes
NA
JIRA Link
DA-253
Checklist

[ ] Updated the Readme.md (if required) ?

src/middleware/typesV2.ts seems big to me at 31K lines.
Is that coming from SubQuery? Any ideas on being able to use a smaller file instead somehow?

Yeah it is coming from SQ, I am not sure what changed but apparently the unsafe aggregate functions got exposed somehow (without even specifying), which caused multiple new options to be generated.
For now, I have used the staging-native GQL to generate the types and seems to have reduced again back to previous form. I think once I updated my local subql-node version that may have caused it, but I'm not sure how those got exposed.  (Can you try it in your local machine once @polymath-eric ?)

:tada: This PR is included in version 15.1.1-beta.1 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 16.0.0-alpha.2 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 16.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Purge database

Hi,
I use the SQLite database, but it seems to be indefinitely growing (currently bigger than 100mb). It would be great if you could clear old data at server start or stop.
Thanks!

As a tip: If it becomes such a huge size, you can clean up it yourself by opening it with SQLite DB Browser (http://sqlitebrowser.org/) and the following sql commands:
DELETE FROM shop_log;
VACUUM;
UPDATE sqlite_sequence SET seq = 0 WHERE name = 'shop_log';
This should clean out the shop log (that's the only table that may cause such a huge size and the only one you can clean up).
Remember to make a backup copy of that database before editing it manually!
And by the way: As far as I have seen in the code, ShopChest do vacuum the database on every server stop. So there's nothing more to do.  If you don't want to edit the database on your own at first, you can try to disable the log by setting enable-economy-log to false in your config.yml. This way you can see if it stops growing.

What I'm asking here is more like auto-deletion of old logs (+30 days for instance), so we don't have to do this manually.

I've implemented a way to enable / disable auto log cleanup and to set a time diff in days:
https://github.com/sigmaroot/ShopChest/commit/c70f8d9e2491006d8361a389a98b9c79528de29d
PR will follow!


HELP

 connection.query("SELECT * FROM `case` WHERE `id` !=0 AND `status` =1", function (err, rows) {

            for (num = 0; num < count(rows); num++) {
                connection.query("SELECT count(*) FROM `items` WHERE `price` > " + rows[num].price + " AND `counts` >0 ", function (err, item) {
                    console.log(num);
                    rows[num].counstitem = item[0]['count(*)'];
                    console.log(rows[1]);
                });
            }
        }
    );

TypeError: Cannot set property 'counstitem' of undefined

If you have 10 results in the outer query at the time the inner Query is executed num equals 10. (Last increment of num after the last element of rows array.)
rows[10] is undefined. (the last defined item would be rows[9] because the counting arrays start at 0)
Please consult google for some tutorials on "asyncron programing in Node.js" and why it is a very bad idea to "declare anonymous function inside a for-loop", especially if the function is used as "asyncron callback" and how outer count-variables are referenced in the "declaration of inner anonymous functions".
Closed. Not an node-mysql issue.


Deprecate old Stream::concat

Just creating this so we can track it for the 0.2 clean-up.
Deprecate the current Stream::concat method and rename Stream::concat2 to Stream::concat.

@alexcrichton could you add the 0.2-cleanup label here?

Certainly!

This was done in https://github.com/rust-lang-nursery/futures-rs/pull/731 for 0.2, so closing


Unify DDoc Makefile build variables

Ideally this should cleanup our Ddoc variables mess. It's noteworthy that Druntime uses completely different ones, so the idea is to change the build files at Druntime afterwards.
If I did it right, no changes should be detected by DAutoTest.

@realpath resolves symlinks and unnecessarily exposes implementation details in log files or even built files. We should get rid of it and just use $(pwd) instead.

You mean $(shell pwd), right?
Done.

Thanks!

Cloning into '/dev/shm/dtest/work/repo/dlang.org/../phobos-2.074.1'...

Looks like there's still a readlink somewhere...

The term DDOC_VARS_STABLE doesn't relate to DDOC_VARS_HTML and DDOC_VARS_VERBATIM.
Following the existing naming schemas, it prolly should be named DDOC_VARS_HTML_STABLE,

https://github.com/dlang/dlang.org/pull/1714

You also added a subtle breakage, now this makefiles requires any DMD or such variables to be absolute, while previously could deal well with relative paths.


Added a new feature to log the final thoughts of each agent 🚀

A really helpful feature to have is that we know what each agent produced as their final answer (not the entire chain of thought) which was fed to the next agent in line in a sequential system.
For example, one agent X writes code and another agent Y explains that code. Then instead of having just the final explanation, it would be nice to retrieve what code was actually written by X. See my project on this here.

I have added a class variable called logs in the Crew class. Every time _execute_tasks() is called, logs is updated (overwritten) with the latest thoughts of the current agent. The idea is - for each task_index the last update will always be the agent's final thought - which is the final answer (see translations/en.json for more clarity).
Thus, after kickoff() completes execution, logs has the final answer of each intermediate agent stored as a dictionary with the integer keys denoting the order of execution of tasks starting from 0.
If somebody wants just the raw output and not the entire mess of TaskOutput, then just write -
logs[<task_number>][0].raw
Hope this helps 😀

Hey @shiladityasarkar at the end of the crew execution you should be able to get the final result and call .tasks_output on it to get the results of each individual task, isn't that exactly what you need? I might be missing something, sorry if that is the case

Hi @shiladityasarkar,
Could you please take a moment to see if this makes sense in light of @joaomdmoura’s comments?
I’d appreciate it if you could also share a test or use case for it.
Thanks


No more ZCSLicense

Since the last scheduled downtime of license server (2023-11-06) the command:
wget -q --no-check-certificate --no-proxy -O /tmp/zcs/ZCSLicense.xml "https://license.zimbra.com/zimbraLicensePortal/public/STLicense?IssuedToName=MyCompany&IssuedToEmail=noone@$DOMAIN"
return the error :
ERROR 404: (no description)
Can you do something ?

Yes new license server does not support getting a trial license, looking for a work-around ATM


limit selectable-rows to one

Is it possible to limit selectable-rows to one? i want to disable multiple selection on the table.
Thanks in advance

I implemented row selection limits...but it's still in progress. Feel free to examine my fork/branch though and see if the changes may help with your needs:
https://github.com/rcheuk/mdDataTable/commit/d33bcb26e68c2768df65334901e627caf7bf0eb2
You can pull the release from this commit.

Hi @themaniac , this is a very good question. I haven't think about it before, but it's definitely a need in my eyes. Will put it on my list and will come back here after I did it.


show usage when no args supplied

also add -h as alias for --help
Signed-off-by: Arnav Gupta<EMAIL_ADDRESS>

Thanks... Can you Plesse check what is up with travis there?

@stefanjudis done :)

Thx. :)


Specify crop settings? Will adding a 'crop' parameter to _config.yml work?

Do you want to apply the same crop to:

all images -> global setting
every image with the same preset -> preset setting
single images -> additional syntax in Liquid tag

I would like to add it as a preset setting. I think that would be most flexible for me

I would love to see support for more of the transformation tools too. I think presets are a good place to start.

@kry8vmedia @aarongustafson I will try to take time soon to look how I can do this!

I've got it pretty much working. Pull request coming tomorrow.

@aarongustafson awesome, thanks!

INCOMING!

You should be able to use crop in your presets now: https://github.com/nhoizey/jekyll-cloudinary/blob/master/lib/jekyll/cloudinary.rb#L26

@aarongustafson do you plan to make a PR with a few additions about this in the README? ;-)

Can you add an issue and assign me? I may be able to tackle it on the plane
next week.

@aarongustafson I created the issue, but I can't assign it to you until you accept my invitation to be a collaborator on the project… ;-)
#27


[Breaking] Allow initial responses from supabase to be reused from the server when doing SSR

This is basically the SvelteKit version of #396, which is why I have not created a new issue.
Also, this is the first time I'm doing a PR for this project, so please do point out if some things should be done differently.
What kind of change does this PR introduce?
One of SvelteKit's features is that if you use the fetch function provided in the load functions, you can avoid fetching data the server just fetched when the client loads.
This is a breaking change, requiring a slight change to the hooks.server.ts/js file. Specifically:

In the src/hooks.server.js we also need to whitelist some Supabase headers to prevent them from being stripped out by SvelteKit:
If you don't have a custom handle hook, then you can add the following:

import { allowSupabaseServerSideRequests } from '@supabase/auth-helpers-sveltekit';
export const handle = allowSupabaseServerSideRequests;
> Otherwise, you can add the following to your existing `handle` hook:
> ```ts
import { RequiredWhitelistedHeaders } from '@supabase/auth-helpers-sveltekit';

export async function handle({ event, resolve }) {
  // ... your existing code

  const response = await resolve(event, {
    // This is the important bits.
    filterSerializedResponseHeaders(name: string, _value: string): boolean {
      return RequiredWhitelistedHeaders.includes(name);
    }
  });

  // ... More of your code

  return response;
}

I also fixed #409 to enable TypedSupabaseClient to be imported directly from @supabase/auth-helpers-sveltekit while I was here.
What is the current behavior?
Data is loaded twice, first on the server, then on the client on the initial navigation.
What is the new behavior?
Data is only loaded once, server side, on the initial load. Afterwards purely client side loading is used.

Thanks alot for mentioning this issue! As be are about to release the new version of auth helpers that include this functionality i´m going to close this issue.


Handle undefined currLocation in MainSlider

Sometimes the currLocation is uninitialised which can cause a crash, so handle that case gracefully by adding a check.

Hi aspiers,
This fix was implemented in Reactime v12.
Closing PR. Thanks!


Remove version: eibol.FFmpegBatchAVConverter version 2.8.1

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://sourceforge.net/projects/ffmpeg-batch/files/FFBatch_AV_Converter_2.8.1_64bit.exe/download
OK
(Automated message - build 923)

Close with reason: Duplicate;


Build CI pipeline using GitHub Actions

Even if the instrumented tests aren't working, the unit tests could definitely be automated

Run unit tests from command line:
gradlew.bat testDebugUnitTest -Dorg.gradle.java.home="C:\Program Files\Android\Android Studio\jre" --stacktrace

Added unit tests, a new issue will be made when instrumented tests are ready


chore(main): release 0.3.0

:robot: I have created a release beep boop
0.3.0 (2023-10-05)
Features

ci trigger release build (b70f9b4)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/radoslavirha/hikers-book/releases/tag/0.3.0 :sunflower:


discord voice

related: https://github.com/ai16z/eliza/issues/244
This PR aims to improve and fix the Discord bot's voice functionality and enhance the code structure for better usability.
1. Fix Bot Voice Singleton Issue
Resolved an issue where the bot's voice functionality failed because the service instance was shared as a singleton across different services. Introduced a Map to ensure each service type has its own singleton instance. This guarantees only one instance of each subclass is created and reused.
2. Add shouldRespond Function
Added a shouldRespond function for the bot's voice feature to control when the bot should respond to user voice inputs.
3. Refactor Transcription Process
Refactored the transcription process by adding a debounce function, ensuring voice messages are processed only when silence is detected.
4. Enable Bot to Respond to Text Messages in Voice Channels
Updated the bot to handle text messages sent in voice channels.
5. Move Template Functions to templates.ts
Relocated template-related functions to a new templates.ts file for reusability in message.ts and voice.ts.
6. Add Optional DISCORD_VOICE_CHANNEL_ID in .env
Introduced a new constant, DISCORD_VOICE_CHANNEL_ID, in the .env file to allow users to specify a voice channel the bot should join.
7. Implemented Audio Playback Interrupt Mechanism
Add a sliding window buffer that monitors the audio volume while the agent is speaking. If the average volume of the user's audio exceeds the defined threshold, it indicates active speaking. When active speaking is detected, stop the agent's current audio playback to avoid overlap.

Closing this PR due to too many conflicts. I’ll create a new PR with a clean base to address the issues.


Create Finals Schedule Card

Create Finals Schedule Card that appears in the Home view (after the Special Events Card if active).

Added basic template for the Finals Card with a ListView with all the finals sorted by their days.


CA startup params defined values unclear

The doc states that the cluster autoscaler uses startup parameters that are defined by the Azure platform, but what are those values set to? The doc points to https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#what-are-the-parameters-to-ca for info about the parameters themselves but isn't explicit about whether or not the default values are the Azure platformed defined values

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

ID: 077f1bb5-2ba9-490c-2c6e-0de292266539
Version Independent ID: 0fd87b4f-88a4-c2eb-3ebc-f2b113ac203c
Content: Use the cluster autoscaler in Azure Kubernetes Service (AKS)
Content Source: articles/aks/cluster-autoscaler.md
Service: container-service
GitHub Login: @mlearned
Microsoft Alias: mlearned

Thanks for the question. We are currently investigating and will update you shortly.

Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

This is indeed an issue as this makes autoscaler behavior unclear, and we are not able to refer to the official cluster autoscaler project reference.

Any update? Autoscaler configuration would be nice to have.

@jluk Can you please help identifying the right person who can update the doc with this information. Thanks. :)

@mlearned owns this document, we are working on exposing this via AKS API calls and more importantly - enable custom setting of these flags.
Please track this issue for the timing of this feature: https://github.com/Azure/AKS/issues/1055
Upon release we will update this document for instructions how to GET and UPDATE these settings.

@vyta As shared in the comment above, this document will be updated upon release of the work that has been in progress.
We will now close this issue. If there are further questions regarding this matter, please tag me in a comment. I will reopen it and we will gladly continue the discussion.


Linux and communication errors

Hello!
In Linux, when we try to read from port and wait fo data, we have a io.EOF error, and can hande it.
Code (simplified):
var n int = 0
var err error
res:=make([byte, 1024])

for n==0{
n, err =port.Read(res)
if err!=nil && err!=io.EOF{
log.Printf("port.Read: %v", err)
}
log.Printf("Read: %v bytes", n)

But, when connection lost occurs, the error is also io.EOF ! How can I distinguish disconnection and waiting for data case?
Now, when I get io.EOF error, I check if /dev/tty* file phisically exists on disk, to recognize a cable disconnection. But, this method is quite ugly.
And, in addition, can you advise me, what is the best way to handle IO errors , using your package? In Windows, when cable is re-connected, I can continue work without closing and re-opening port, but in Linux, I have "bad descriptor" error. So I can not use "defer port.Close()", And, additionally,manual  closing of port causes crash of the stack of all functions , which used the descriptor at the moment. Is there a way to "renew" descriptor or some another practice?

I'm having this same issue on Linux but on Windows it seems to block like normal.


Not running because of pywidevine error

Hi! I have moved to a new PC and had to reinstall everything including gamdl (which I used without problems in the past).
I did everything as required but when I try to launch gamdl, I receive the following errors:
C:\Users\Valentin>gamdl
Traceback (most recent call last):
  File "c:\users\valentin\appdata\local\programs\python\python37\lib\runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "c:\users\valentin\appdata\local\programs\python\python37\lib\runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "C:\Users\Valentin\AppData\Local\Programs\Python\Python37\Scripts\gamdl.exe\__main__.py", line 4, in <module>
  File "c:\users\valentin\appdata\local\programs\python\python37\lib\site-packages\gamdl\cli.py", line 11, in <module>
    from .downloader import Downloader
  File "c:\users\valentin\appdata\local\programs\python\python37\lib\site-packages\gamdl\downloader.py", line 17, in <module>
    from pywidevine import PSSH, Cdm, Device, WidevinePsshData
ImportError: cannot import name 'WidevinePsshData' from 'pywidevine' (c:\users\valentin\appdata\local\programs\python\python37\lib\site-packages\pywidevine\__init__.py)

Thank you!

Fixed on the new release.

Hi, thank you for the fast update!
Unfortunately I got another error that I have never seen.
Traceback (most recent call last):
  File "c:\users\valentin\appdata\local\programs\python\python37\lib\http\cookiejar.py", line 1782, in __init__
    filename+""
TypeError: unsupported operand type(s) for +: 'WindowsPath' and 'str'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "c:\users\valentin\appdata\local\programs\python\python37\lib\runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "c:\users\valentin\appdata\local\programs\python\python37\lib\runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "C:\Users\Valentin\AppData\Local\Programs\Python\Python37\Scripts\gamdl.exe\__main__.py", line 7, in <module>
  File "c:\users\valentin\appdata\local\programs\python\python37\lib\site-packages\click\core.py", line 1157, in __call__
    return self.main(*args, **kwargs)
  File "c:\users\valentin\appdata\local\programs\python\python37\lib\site-packages\click\core.py", line 1078, in main
    rv = self.invoke(ctx)
  File "c:\users\valentin\appdata\local\programs\python\python37\lib\site-packages\click\core.py", line 1434, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "c:\users\valentin\appdata\local\programs\python\python37\lib\site-packages\click\core.py", line 783, in invoke
    return __callback(*args, **kwargs)
  File "c:\users\valentin\appdata\local\programs\python\python37\lib\site-packages\gamdl\cli.py", line 341, in main
    downloader.setup_session()
  File "c:\users\valentin\appdata\local\programs\python\python37\lib\site-packages\gamdl\downloader.py", line 89, in setup_session
    cookies = MozillaCookieJar(self.cookies_location)
  File "c:\users\valentin\appdata\local\programs\python\python37\lib\http\cookiejar.py", line 1784, in __init__
    raise ValueError("filename must be string-like")
ValueError: filename must be string-like

I tried to give the exact path of the cookies.txt file with -c but it doesn't make a difference.
Maybe I've done something wrong...
Thank you!


Update build to build VAL via CMake

Specific commit was pinned as part of #188

Closing as wontfix; the project is finished and the repository is to be archived.


About FSDP，deepspeech.

Hello，
May I know if the current FSDP and DeepSpeech are stable and available for use? Do they support multi-machine multi-card and LORA fine-tuning?

Sorry that they are not stable. Anyway Welcome PR :)

fsdp has a bug: sharding_strategy needs “ShardingStrategy” not “str”

fsdp 有一个错误：sharding_strategy 需要“ShardingStrategy”而不是“str”

你解决了吗？ @fclearner

fsdp 有一个错误：sharding_strategy 需要“ShardingStrategy”而不是“str”

你解决了吗？ @fclearner

yes，try this:https://github.com/wenet-e2e/wenet/blob/24375c51c8ccbf1dac0724f5734a6eae4ac9c428/wenet/utils/train_utils.py#L410

https://github.com/X-LANCE/SLAM-LLM/pull/153


Fix for issue #49

Fix issue #49

Added a new definition for the term "distribution"
Highlighted some API methods that need a distribution to function
Left relevant links to use cases such as repository mirroring

Hi, @YanisaHS please check out my PR and let me know what you think. I'm happy to make necessary corrections.

Hey @ade555! It looks like you might have branched off of your other WSL branch to make these changes. No problem :smiley: but can you remove the WSL-related files from this PR so it's only the Landscape "distribution" term stuff?
It's not blocking my review, but I just want to get that cleaned up to not conflict with your other PR. I'll tag you here and on the other PR when I'm ready for you to address any suggestions. Thanks!

Hi, @YanisaHS. Thank you very much for your feedback. I learned something important from the corrections you made. I'm also glad you found my contribution a bit impressive.
I already made changes to reflect the corrections you made. Kindly review it once more. Thank you!

@ade555 Thanks so much for your wonderful contribution!! :rocket: :partying_face: :balloon: You can see it live here: https://ubuntu.com/landscape/docs/explanation-distribution (yay!!)
Hope to work with you again soon! And if you have any feedback on this PR process or contributing to Canonical's Open Documentation Academy, please feel free to leave it as a comment here.

Yay! It's really nice to see this go live. I really enjoyed collaborating with you on this PR and I will definitely like to work with you again. Your corrections helped me improve.
@YanisaHS


entire site

Suggest we add a TITLE tag with the name that is selected to all pages.

We are changing the name to NoshAlert. This is being addressed in another issues list I am closing this out.


Layout width miscalculation

Hello @gliechtenstein,
I fell on a problem of width that is miscalculated.
Here an example: https://jasonbase.com/things/lXmo
Like you can see, the 2nd image is cut, I have to manually set the width of the horizontal layout.
I am trying to understand from where the problem comes from but maybe you have any clue.

Sorry for the bad explanation, I was on the hurry in the train, it was to be sure not forgetting. Too much drink maybe :beers: :cocktail: :tada:
So let's do this with more professionalism.
Description
Architecture of layout is like that:
sections [
    label_0,
    horizontal [ image, label_1 (with fixed size), image ],
    label_0
]

If label_1 size is not fixed, all works as expected. By setting a size, total width of horizontal is miscalculated. Here a minimal jason example: https://jasonbase.com/things/lXmo
Screenshots
If I don't set a width to the label, width calculation of horizontal is good:

If I set the width to the label, horizontal width is too small and doesn't surround the image:

I think that when calculating the width of horizontal, jasonette doesn't take into account the fixed width. Instead of taking the fixed width, it takes the size of the label.
@gliechtenstein Don't hesitate to ask more information, it should be pretty clear now :wink:

@realitix I think the problem is you've used horizontal layout within a horizontal layout, which is not really an intended usage. Is there a reason why you wanted to use that pattern? The vertical/horizontal layouts are meant to be flexible containers that expand and contract based on its children so when you try to contain a horizontal layout inside another horizontal layout, both of them are flexible and result in an unexpected behavior. Note that this is different from when you nest a horizontal layout inside a vertical layout or vertical layout inside a horizontal, which doesn't have a problem.
In this particular example I think you should consolidate all the horizontal components into a single level components array, like I've done here https://jasonbase.com/things/WedA.json
If there's a special case where you can't employ this type of technique and MUST use horizontal inside horizontal layout please let me know, maybe I'm missing something.


Lack of mention to WithAttributeFiltering

Hi,
Thanks for this example of using the attribute.
I noticed that in the website  where I found this code, it does not indicate about the registration of the class using this attribute with the WithAttributeFiltering(). It is added in your code in:
    builder.RegisterType<MyService>().As<IMyService>().WithAttributeFiltering();
    builder.RegisterType<GetWelcome>().WithAttributeFiltering();

This part is critical :D
Thanks a lot for this code!
Juan

Thanks for the feedback. Glad it could help!


Add support for RedisJSON 2.0

Please notice all the commands can now get full jsonpath, i.e. dynamic paths that start with a $ sign.
As a result all the commands can now return multi parts of the JSON.
see: https://oss.redis.com/redisjson/commands/

https://github.com/RedisJSON/RedisJSON/releases/tag/v2.0.4


[FEDE-4580] Upgrade Arrow version to 4.0.0

Codecov Report

:exclamation: No coverage uploaded for pull request base (siren-changes@3a4b22d). Click here to learn what that means.
The diff coverage is n/a.

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

@@               Coverage Diff                @@
##             siren-changes      #16   +/-   ##
================================================
  Coverage                 ?   78.68%
================================================
  Files                    ?      286
  Lines                    ?    64537
  Branches                 ?        0
================================================
  Hits                     ?    50781
  Misses                   ?    13756
  Partials                 ?        0

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3a4b22d...55b59a5. Read the comment docs.

In the pr https://github.com/apache/arrow/pull/6729, ArrowBuf was moved into Arrow's package and made independent of Netty library.

Yes, we will likely need to update references to ArrowBuf in Federate after upgrading to this version of arrow.
However, we should ensure that we continue to use netty allocator. We could evaluate other allocators in another story.

@rendel  Do we need to shade apache arrow to ensure our version of the ArrowBuf is used ? E.g., in case another ES plugin uses also arrow.

@scampi good point, but not in this PR. Let's track and plan this in another story

The build for arrow fails with package siren.io.netty.buffer does not exist although we shade the io.netty to siren.io.netty see
https://github.com/sirensolutions/arrow/blob/3d7bd90d35868361453df90c51c7bff47993b513/java/memory/memory-netty/pom.xml#L68
netty is built as a module in the arrow memory pom
https://github.com/sirensolutions/arrow/blob/3d7bd90d35868361453df90c51c7bff47993b513/java/memory/pom.xml#L26
therefore, it seems the build uses the original pom of netty instead of the shaded pom dependency-reduced-pom which is created in the netty module. Therefore the shaded package siren.io.netty.buffer is not visible to the arrow vector

@fabiocorneti this is the pr with a comment on the arrow-vector build failure

The commit https://github.com/sirensolutions/arrow/pull/16/commits/6d94b43cecde43cbf6465b48d790a2229c28daa9 adds the shaded netty artifact to the arrow-vector which makes the packages siren.io.netty.buffer accessible in the project.

I will make the release from branch-siren-4.0.x


Flink version update

Summary
Fix the Beam build issue to run against latest Flink version.
Testing
Tested for all versions of Flink and now Beam is able to fetch the latest Flink artifacts.
./gradlew :runners:flink:1.16:build
./gradlew :runners:flink:1.15:build
./gradlew :runners:flink:1.14:build
./gradlew :runners:flink:1.13:build
./gradlew :runners:flink:1.12:build

Where are we setting the new flink version (11600.3)?

Fixed the code.

Could you please verify the dependency by ./gradlew :runners:flink:1.16:dependenies? I want to make sure we are using our flink versions indeed. Thanks.

Verified the changes locally.
`+--- org.apache.beam:beam-vendor-grpc-1_48_1:0.1 ()
+--- org.slf4j:slf4j-api:1.7.30
+--- joda-time:joda-time:2.10.10
+--- args4j:args4j:2.33
+--- org.apache.flink:flink-clients:11600.3
|    +--- org.apache.flink:flink-core:11600.3
|    |    +--- org.apache.flink:flink-annotations:11600.3
|    |    |    +--- org.slf4j:slf4j-api:1.7.32 -> 1.7.30
|    |    |    +--- com.google.code.findbugs:jsr305:1.3.9 -> 3.0.2
|    |    |    --- org.apache.flink:flink-shaded-force-shading:15.0
|    |    +--- org.apache.flink:flink-metrics-core:11600.3
|    |    |    +--- org.apache.flink:flink-annotations:11600.3 ()
|    |    |    --- org.apache.flink:flink-shaded-force-shading:15.0
|    |    +--- org.apache.flink:flink-shaded-asm-9:9.2-15.0
|    |    +--- org.apache.flink:flink-shaded-jackson:2.12.4-15.0
|    |    +--- org.apache.commons:commons-lang3:3.3.2 -> 3.9
|    |    +--- com.esotericsoftware.kryo:kryo:2.24.0 ()
|    |    +--- commons-collections:commons-collections:3.2.2
|    |    +--- org.apache.commons:commons-compress:1.21
|    |    +--- org.apache.flink:flink-shaded-guava:30.1.1-jre-15.0
|    |    +--- org.slf4j:slf4j-api:1.7.32 -> 1.7.30
|    |    +--- com.google.code.findbugs:jsr305:1.3.9 -> 3.0.2
|    |    --- org.apache.flink:flink-shaded-force-shading:15.0
|    +--- org.apache.flink:flink-runtime:11600.3
|    |    +--- org.apache.flink:flink-core:11600.3 ()
|    |    +--- org.apache.flink:flink-rpc-core:11600.3
|    |    |    +--- org.slf4j:slf4j-api:1.7.32 -> 1.7.30
|    |    |    +--- com.google.code.findbugs:jsr305:1.3.9 -> 3.0.2
|    |    |    --- org.apache.flink:flink-shaded-force-shading:15.0
|    |    +--- org.apache.flink:flink-rpc-akka-loader:11600.3
|    |    |    +--- org.apache.flink:flink-core:11600.3 ()
|    |    |    +--- org.apache.flink:flink-rpc-core:11600.3 ()
|    |    |    +--- org.apache.flink:flink-shaded-force-shading:15.0
|    |    |    +--- org.slf4j:slf4j-api:1.7.32 -> 1.7.30
|    |    |    --- com.google.code.findbugs:jsr305:1.3.9 -> 3.0.2
|    |    +--- org.apache.flink:flink-java:11600.3
|    |    |    +--- org.apache.flink:flink-core:11600.3 ()
|    |    |    +--- org.apache.commons:commons-lang3:3.3.2 -> 3.9
|    |    |    +--- org.apache.commons:commons-math3:3.6.1
|    |    |    +--- com.twitter:chill-java:0.7.6
|    |    |    |    --- com.esotericsoftware.kryo:kryo:2.21 -> 2.24.0 ()
|    |    |    +--- org.slf4j:slf4j-api:1.7.32 -> 1.7.30
|    |    |    +--- com.google.code.findbugs:jsr305:1.3.9 -> 3.0.2
|    |    |    --- org.apache.flink:flink-shaded-force-shading:15.0
|    |    +--- org.apache.flink:flink-queryable-state-client-java:11600.3
|    |    |    +--- org.apache.flink:flink-shaded-netty:4.1.70.Final-15.0
|    |    |    +--- org.apache.flink:flink-shaded-guava:30.1.1-jre-15.0
|    |    |    --- org.apache.flink:flink-shaded-force-shading:15.0
|    |    +--- org.apache.flink:flink-hadoop-fs:11600.3
|    |    |    +--- org.apache.flink:flink-core:11600.3 ()
|    |    |    --- org.apache.flink:flink-shaded-force-shading:15.0
|    |    +--- commons-io:commons-io:2.11.0 -> 2.7
|    |    +--- org.apache.flink:flink-shaded-netty:4.1.70.Final-15.0
|    |    +--- org.apache.flink:flink-shaded-guava:30.1.1-jre-15.0
|    |    +--- org.apache.flink:flink-shaded-jackson:2.12.4-15.0
|    |    +--- org.apache.flink:flink-shaded-zookeeper-3:3.5.9-15.0
|    |    +--- org.apache.commons:commons-lang3:3.3.2 -> 3.9
|    |    +--- commons-cli:commons-cli:1.5.0
|    |    +--- org.javassist:javassist:3.24.0-GA
|    |    +--- org.xerial.snappy:snappy-java:<IP_ADDRESS> -> <IP_ADDRESS>
|    |    +--- org.lz4:lz4-java:1.8.0
|    |    +--- org.apache.flink:flink-shaded-force-shading:15.0
|    |    +--- org.slf4j:slf4j-api:1.7.32 -> 1.7.30
|    |    --- com.google.code.findbugs:jsr305:1.3.9 -> 3.0.2
|    +--- org.apache.flink:flink-optimizer:11600.3
|    |    +--- org.apache.flink:flink-core:11600.3 ()
|    |    +--- org.apache.flink:flink-runtime:11600.3 ()
|    |    +--- org.apache.flink:flink-java:11600.3 ()
|    |    +--- org.apache.flink:flink-shaded-guava:30.1.1-jre-15.0
|    |    +--- org.apache.flink:flink-shaded-jackson:2.12.4-15.0
|    |    +--- org.slf4j:slf4j-api:1.7.32 -> 1.7.30
|    |    +--- com.google.code.findbugs:jsr305:1.3.9 -> 3.0.2
|    |    --- org.apache.flink:flink-shaded-force-shading:15.0
|    +--- org.apache.flink:flink-java:11600.3 ()
|    +--- commons-cli:commons-cli:1.5.0
|    +--- org.apache.flink:flink-streaming-java:11600.3
|    |    +--- org.apache.flink:flink-core:11600.3 ()
|    |    +--- org.apache.flink:flink-file-sink-common:11600.3
|    |    |    --- org.apache.flink:flink-shaded-force-shading:15.0
|    |    +--- org.apache.flink:flink-runtime:11600.3 ()
|    |    +--- org.apache.flink:flink-java:11600.3 ()
|    |    +--- org.apache.flink:flink-shaded-guava:30.1.1-jre-15.0
|    |    +--- org.apache.commons:commons-math3:3.6.1
|    |    +--- org.slf4j:slf4j-api:1.7.32 -> 1.7.30
|    |    +--- com.google.code.findbugs:jsr305:1.3.9 -> 3.0.2
|    |    --- org.apache.flink:flink-shaded-force-shading:15.0
|    +--- org.slf4j:slf4j-api:1.7.32 -> 1.7.30
|    +--- com.google.code.findbugs:jsr305:1.3.9 -> 3.0.2
|    --- org.apache.flink:flink-shaded-force-shading:15.0
+--- org.apache.flink:flink-streaming-java:11600.3 ()
+--- org.apache.flink:flink-core:11600.3 ()
+--- org.apache.flink:flink-metrics-core:11600.3 ()
+--- org.apache.flink:flink-java:11600.3 ()
+--- org.apache.flink:flink-runtime:11600.3 ()
+--- org.apache.flink:flink-optimizer:11600.3 ()
+--- project :model:fn-execution ()
+--- project :model:pipeline ()
+--- project :model:job-management ()
+--- project :sdks:java:fn-execution ()
+--- com.fasterxml.jackson.core:jackson-databind:2.14.1 ()
+--- org.apache.flink:flink-annotations:11600.3 ()
+--- org.apache.flink:flink-statebackend-rocksdb:11600.3
|    +--- com.ververica:frocksdbjni:6.20.3-ververica-1.0
|    +--- org.slf4j:slf4j-api:1.7.32 -> 1.7.30
|    +--- com.google.code.findbugs:jsr305:1.3.9 -> 3.0.2
|    --- org.apache.flink:flink-shaded-force-shading:15.0
--- com.fasterxml.jackson.module:jackson-module-jaxb-annotations:2.14.1
+--- com.fasterxml.jackson.core:jackson-annotations:2.14.1 ()
+--- com.fasterxml.jackson.core:jackson-core:2.14.1 ()
+--- com.fasterxml.jackson.core:jackson-databind:2.14.1 ()
+--- jakarta.xml.bind:jakarta.xml.bind-api:2.3.3
|    --- jakarta.activation:jakarta.activation-api:1.2.2
+--- jakarta.activation:jakarta.activation-api:1.2.2
--- com.fasterxml.jackson:jackson-bom:2.14.1 ()
(c) - dependency constraint
(*) - dependencies omitted (listed previously)
(n) - Not resolved (configuration is not meant to be resolved)
A web-based, searchable dependency report is available by adding the --scan option.
Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
See https://docs.gradle.org/7.5.1/userguide/command_line_interface.html#sec:command_line_warnings
BUILD SUCCESSFUL in 24s
11 actionable tasks: 1 executed, 10 up-to-date`


Allow Tokens to be specified per request

Description
Users would like to create one WebClient and specify any team specific data on each request.
What type of issue is this? (place an x in one of the [ ])

[ ] bug
[x] enhancement (feature request)
[ ] question
[ ] documentation related
[ ] testing related
[ ] discussion

Requirements (place an x in each of the [ ])

[X] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[X] I've read and agree to the Code of Conduct.
[X] I've searched for any related issues and avoided creating a duplicate issue.

The implementation will be as below. I'm planning to add this feature in v2.7+
client = WebClient(token="xoxb-111")
client.chat_postMessage(channel="#random", text="Hello!") # with xoxb-111
client.chat_postMessage(token="xoxb-222", channel="#random", text="Hello!") # with xoxb-222


Access token refresh retry limit exceeded.

Describe the bug
Sometime I got such error:"Access token refresh retry limit exceeded." Application is waiting a time(white screen presents) and start after that How to get rid of such error?

This happens when you open the app when there is no internet connection. Supabase currently requires internet connection to work.


IE11 cannot access apollo project page normally

[ ] I have searched the issues of this repository and believe that this is not a duplicate.
[ ] I have checked the FAQ of this repository and believe that this is not a duplicate.

Describe the bug
I try to use IE11 to access apollo, but when i login and browser the project page, i find that the page cannot display normally. I use the demo address to test it (http://<IP_ADDRESS>/). For my local environment it does not work too.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
apollo project page can not be displayed
Screenshots
(i don't why i can't upload the screeshots)
Additional Details & Logs

Version: apollo 1.6.1
Error logs
Configuration
Platform and Operating System

Please use Chrome or Firefox instead


Fix logo ratio in README.md

Description
Fix logo ratio in README.md by removing with incorrect width attribute.
Why
Because it looks pretty 💅

Oh I completely forgot that you left Qwant on Thursday when I read your PR, we'll miss you :cry:
I'll merge this then. Thanks a lot for the fix! :heart:


From latest version 0.6.20 - error:- Error retrieving keys for Storage Account

Describe the bug
From the latest version 0.6.20 - our pipelines are failing with errors
Initializing modules...
- staticwebsite in ../../modules/staticwebsite

Initializing the backend...

Successfully configured the backend "azurerm"! Terraform will automatically
use this backend unless the backend configuration changes.

Error: Failed to get existing workspaces: Error retrieving keys for Storage Account "tamops12345": storage.AccountsClient#ListKeys: Failure responding to request: StatusCode=404 -- Original Error: autorest/azure: Service returned an error. Status=404 Code="ResourceGroupNotFound" Message="Resource group 'tamops12345' could not be found."

##[error]Terraform command 'init' failed with exit code '1'.:  Failed to get existing workspaces: Error retrieving keys for Storage Account "tamops12345": storage.AccountsClient#ListKeys: Failure responding to request: StatusCode=404 -- Original Error: autorest/azure: Service returned an error. Status=404 Code="ResourceGroupNotFound" Message="Resource group 'tamops12345' could not be found."
##[error]

Error: Failed to get existing workspaces: Error retrieving keys for Storage Account "tamops12345": storage.AccountsClient#ListKeys: Failure responding to request: StatusCode=404 -- Original Error: autorest/azure: Service returned an error. Status=404 Code="ResourceGroupNotFound" Message="Resource group 'tamops12345' could not be found."

To note:- The service principal (backendServiceArm) is configured initially on a separate subscription to where the storage account is located, previous versions we added this to our Terraform provider
terraform {
  required_version = ">= 0.13.0"

  backend "azurerm" {
    subscription_id  = "xxxx-xxxx-xxxx-xxxxx"
  }

To Reproduce
Steps to reproduce the behavior:

Example task that was working in previous versions

      - task: TerraformCLI@0
        displayName: terraform init
        inputs:
          command: init
          workingDirectory: '$(System.DefaultWorkingDirectory)/components/${{ parameters.component }}'
          backendType: azurerm
          backendServiceArm: '${{ parameters.service_connection }}'
          backendAzureRmResourceGroupName: 'tamops12345'
          backendAzureRmStorageAccountName: 'tamops12345'
          backendAzureRmContainerName: '${{ parameters.backendAzureRmContainerName }}'
          backendAzureRmKey: '${{ parameters.component }}.tfstate'

provider.tf
terraform {
  required_version = ">= 0.13.0"

  backend "azurerm" {
    subscription_id  = "xxxx-xxxx-xxxx-xxxxx"
  }

Expected behavior
Terraform to init correctly as previous versions of this task.
Current behaviour is mentioned in Describe the Bug
Current fix/workaround
Added commandOptions with '-backend-config=subscription_id=xxxx-xxxx-xxxx-xxxxx'  to my task, to allow terraform init to work correctly with correct storage account & subscription
      - task: TerraformCLI@0
        displayName: terraform init
        inputs:
          command: init
          workingDirectory: '$(System.DefaultWorkingDirectory)/components/${{ parameters.component }}'
          backendType: azurerm
          backendServiceArm: '${{ parameters.service_connection }}'
          backendAzureRmResourceGroupName: 'tamops12345'
          backendAzureRmStorageAccountName: 'tamops12345'
          backendAzureRmContainerName: '${{ parameters.backendAzureRmContainerName }}'
          backendAzureRmKey: '${{ parameters.component }}.tfstate'
          commandOptions: '-backend-config=subscription_id=xxxx-xxxx-xxxx-xxxxx'

My ask
Is it a bug or known that this issue we found has been introduced in  0.6.20 & going forward? Hopefully this issue assists with others who may be facing same issue if so.

Hi @thomast1906, I believe that setting subscription_id in the template worked in previous versions because the task was still using the old configuration variables that have the arm_ prefix before 0.6.20 (i.e. arm_subscription_id. The use of subscription_id probably took precedence over the old/deprecated arm_subscription_id variable.
With the release of terraform 0.15, terraform stopped supporting the arm_ prefixed configuration and using these would cause terraform to fail. This task was forced to switch over to the new supported configuration to get users pipelines running again. After that switch, the backend-config is now using subscription_id which probably rendered your original approach no longer usable.
There are currently no plans to adjust the task to accommodate this scenario since 0.15 requires use of subscription_id. Furthermore, terraform exe itself would be responsible for whether subscription in the template or on the command line takes precedence. With that said, I would suggest two things. First, the approach you are using is valid. You could also use self-configured option which will prevent the task from supplying any backend-config options. Others that use self-configured option store their SPN creds in a ADO secure file which is encrypted and not readable by human after upload. Second, there is an open issue to allow backend to exist on a different subscription than what is targeted by the provider/deployment (#257). I would suggest having a look at that issue and see if it maps to your case. If so, thumbs up the opening post or comment.

Cheers @charleszipp - we are happy with the commandOptions mentioned above


[BUG] response_model does not work with inter-field validator

Describe the bug
For a model used with response_model, its validators are called twice, the second time with empty values, thus causing a validation error when validating one field which depends on another.
To Reproduce

Create a file main.py with the following.

from typing import List

from fastapi import FastAPI
from pydantic import BaseModel, validator

app = FastAPI()

class Item(BaseModel):
    name: str
    description: str = None
    price: float
    tax: float = None
    tags: List[str] = []

    @validator('tax')
    def _validate_ratio_of_price_to_tax_is_ten_to_one(cls, tax, values):
        print(f'values = {values}')
        print(f'cls = {cls}')

        assert 'price' in values # FAILS on second validation call

        assert values['price'] / tax == 10
        return tax

@app.post("/items/", response_model=Item)
async def create_item(item: Item):
    return item

from starlette.testclient import TestClient
client = TestClient(app)

client.post(
    "/items/",
    json={
        "name": "string",
        "price": 10,
        "description": "string",
        "tax": 1,
        "tags": [
            "string"
        ]
    }
)

Run with python main.py

Expected behavior
The validator to only be called once and with values being set to the values I pass in.
Actual output
cls = <class '__main__.Item'>
values = {'name': 'string', 'price': 10.0, 'description': 'string'}
cls = <class 'Item'>
values = {}

Traceback (most recent call last):
...
AssertionError assert 'price' in values

Environment:

OS: macOS
fastapi==0.36.0
python version = Python 3.6.9 :: Anaconda, Inc.

Additional context
The first time the validator gets called, values is set correctly. Also, when I remove response_model, the request is successful (because the validator is not called at all).

It seems this was solved at some point in a recent version, I can't reproduce the bug in the latest version.


All components ported to work on Vue 1.0

@yuche This should be it. Pretty much all components are ported and tested.
However I will need your help with getting the Carousel/Slider working properly. I've just been stuck with the parent/child event handling here and since I don't intend to use this much in my project, I think this can be left pending until beta.
There have been major changes with the typeahead component. Since dynamic ${this.template} rendering is no longer supported, I'm using named partials. Unfortunately the user now needs to use two variables (templateName, and template). And the scoped name of the variable is defined as item.
Anyways, some documentation updates will probably be needed, I won't have time to work on this further.
Thanks for creating this project, and I hope my contribution helped.

@amanpatel You've done a great job :+1:

@amanpatel :+1:
Great help. Thank you.


Metrics should be standardized

Describe the feature you'd like and what it will do
The MakeDataCount effort to standardize metrics collection and reporting is worthwhile for us to aspire to. We probably don’t want to actually get audited and become a member, but we can still implement the COUTERr5 standards.
Additional context
HS v 2.8
I found this set of notes helpful: https://www.projectcounter.org/wp-content/uploads/2017/07/Tech_Notes_20170710.pdf
Datacite has a simplified list of the basic things we will want to track in order to be compliant with the COUNTER Code of Practice
Set of minimal fields:

Date and time
Request IP address
Session cookie ID: an ID kept in a session cookie which only lives as long as the browser/session is open
User cookie ID: an ID that identifies a user session that may persist past the closing of the browser window to future visits
Username or user ID: identifies a user of the system because they have logged in or identified themselves
The requested URL
The DOI name. The DOI Identifier which uniquely identifies this dataset
The size of the dataset. Size (only needed for requests which download a dataset and not for investigations which display landing pages or metadata about a dataset)
The user-agent string being sent by the client

It also requires the following metadata about the resource:

title
publisher
publisher Id
creators
publication date
version of dataset
URL
publication year

If we ever want to, it looks like we could use a tool like counter-processor to actually process our logs into a more compliant (submittable) format.

related to https://github.com/hydroshare/hydroshare/issues/4733


[Feature request] suppurt vlees and reality

Hello
Please add vless and reality to the panel
Also explain how to configure hysteria protocol
thank you

Hello Please add vless and reality to the panel Also explain how to configure hysteria protocol
thank you

To add all v2ray configs to the v2board panel such as reality, vless, tcp+http, fingerprint, alpn, etc., as well as the v2board telegram bot for automatic sales, which connects to the panel through api, you can message me on telegram @dream4network. All features are output automatically on the client and there is no need for manual adjustment by the user. Bot is comprehensive and has all features of panel.


Personal Portfolio

A portfolio website I'm creating using html-css-js

Already created by someone