Form elements with the same name

Should we support form elements that share the same name? Current behavior overwrites the previous key.
Maybe we should detect if there's an existing "string" value and convert it to an array and push the new form element to the array?

The php convention of creating an array when the control names are appended with [] might be something to consider. Although, I can see this getting pretty hairy with Formsy.reset where there are no named keys. Other options might be something like dot notation.
Also, in php, the current behaviour (last control with 'name' value clobbers all previous?) is sometimes used for patterns like:
<input type="hidden" name="foo" value="my default value">
<input type="checkbox" name="foo" checked="false" value="my overridden value">


Ignore the jsonrequestobject argument to the getblocktemplate RPC

Motivation
Our stub getblocktemplate RPC will fail if it gets any arguments.
But we want to ignore the optional jsonrequestobject argument instead, because we're not going to support any optional features requested by clients.
Specifications
https://zcash.github.io/rpc/getblocktemplate.html
Designs
Accept an Option<String> argument and ignore it? Does that work?
Related Work
If we discover that clients need optional features, we can parse the argument and implement them later.

Accept an Option<String> argument and ignore it? Does that work?

It seemed to cause ParseErrors for the JsonParameterObject in submitblock when that was called with only one parameter.

Accept an Option<String> argument and ignore it? Does that work?

It seemed to cause ParseErrors for the JsonParameterObject in submitblock when that was called with only one parameter.

I'm not exactly sure how the jsonrpc library argument processing works, but unlike submitblock, getblocktemplate doesn't need any arguments at all.

It's the same problem in submitblock where it needs to accept and ignore an optional argument.
This works:
/// Routes request to `get_block_template` method
#[rpc(name = "getblocktemplate")]
fn get_block_template_with_ignored_json_params(
    &self,
    _json_params: String,
) -> BoxFuture<Result<GetBlockTemplate>> {
    self.get_block_template()
}


Add RBAC proxy to metrics

What type of PR is this?
/kind feature
What this PR does / why we need it:
We now use the kube-rbac-proxy to provide two metrics endpoints. Those
get exposed through the metrics-spod and metrics-controller-runtime
services, serving an authorized self-signed TLS connection.
To be able to retrieve the metrics, it is now required to deploy a
ClusterRole and ClusterRoleBinding for a ServiceAccount. For
example:
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: spo-metrics-client
rules:
- nonResourceURLs:
  - /metrics
  verbs:
  - get
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: spo-metrics-client
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: spo-metrics-client
subjects:
- kind: ServiceAccount
  name: default
  namespace: security-profiles-operator

The above example is also part of the default deployment, and can be
tested via kubectl run within the security-profiles-operator
namespace by running:
> kubectl run --rm -it pod --image=alpine -- sh -c \
    'apk update && apk add bash curl &&
     curl -vsk -H "Authorization: Bearer `cat /var/run/secrets/kubernetes.io/serviceaccount/token`"
     https://metrics-spod/metrics'
…
*   Trying <IP_ADDRESS>:443...
* Connected to metrics-spod (<IP_ADDRESS>) port 443 (#0)
…
> authorization: Bearer xxx
>
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* Connection state changed (MAX_CONCURRENT_STREAMS == 250)!
< HTTP/2 200
< content-type: text/plain; version=0.0.4; charset=utf-8
< date: Wed, 28 Apr 2021 12:00:46 GMT
…
security_profiles_operator_seccomp_profile{operation="update"} 1

Documentation and e2e testing will follow in further patches.
Which issue(s) this PR fixes:

Refers to #422
Does this PR have test?

None
Special notes for your reviewer:
None
Does this PR introduce a user-facing change?

Deploying kube-rbac-proxy sidecar in SPOD for exposing metrics via the new `metrics-spod` and `metrics-controller-runtime` services.

the rbac-proxy isn't using TLS, is it?

It is using a self-signed one right now and we also can provide an external one.

/retest


Sparkc 338 b1.5 proper target

Build against Scala 2.11 finished with success

Build against Scala 2.10 finished with success


added "Favourites" section and fixed the issue 319

Description
For #320,
I've added te favourites section where the user can see their favourite or most important exams/assessment details. The implementation is such that it would not require internet data or any additional user model, and extracts favourited assessments/exams right from the "Alerts" modal class.
Sample video of the implementation: See video of favourites section
For #319,
I've fixed the error in signup_forms_additional_details.dart file. This makes the application's user sign up process exception free.
Before:

After:

Fixes #319, Fixes #320
Have you read the Contributing Guidelines on Pull Requests?

[x] Yes
[ ] No

Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)

Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] My changes generate no new warnings
[x] I have added tests/screenshots(if any) that prove my fix is effective or that my feature works.

Hi @avinashkranjan can you please review this PR? Thank you!


Live

to sync master

Docs Build status updates of commit e2d3d43:
:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@microsteve please merge at your leisure.


Fix params not being hash by default

This fixes a minor thing that has been nagging at me for a while: I always had to do params && params[:foo] in an attribute block because params is undefined unless the controller explicitly passes it. I think we should be able to expect params to always be defined.
The bug occurs when no options are passed and the early return return if options.blank? prevents params being set to {} by default.

Fantastic! Thank you for this fix! :)
On Thu, Oct 18, 2018, 9:31 PM Maros Hluska<EMAIL_ADDRESS>wrote:

This fixes a minor thing that has been nagging at me for a while: I always
had to do params && params[:foo] in an attribute block because params is
undefined unless the controller explicitly passes it.
You can view, comment on, or merge this pull request online at:
https://github.com/Netflix/fast_jsonapi/pull/339
Commit Summary

Fix params not being hash by default

File Changes

M lib/fast_jsonapi/object_serializer.rb
https://github.com/Netflix/fast_jsonapi/pull/339/files#diff-0 (2)
M spec/lib/object_serializer_attribute_param_spec.rb
https://github.com/Netflix/fast_jsonapi/pull/339/files#diff-1 (2)
M spec/lib/object_serializer_spec.rb
https://github.com/Netflix/fast_jsonapi/pull/339/files#diff-2 (6)
M spec/shared/contexts/movie_context.rb
https://github.com/Netflix/fast_jsonapi/pull/339/files#diff-3 (20)

Patch Links:

https://github.com/Netflix/fast_jsonapi/pull/339.patch
https://github.com/Netflix/fast_jsonapi/pull/339.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Netflix/fast_jsonapi/pull/339, or mute the thread
https://github.com/notifications/unsubscribe-auth/AD2OweDw5edb6gh_ryaXEinP0WWdVkfLks5umKXUgaJpZM4XtwvB
.


⚠ Bofrost.be has degraded performance

In 53bc65f, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1831 ms

Resolved: Bofrost.be performance has improved in 515cbcc.


Add support for vision targets and Limelight

See https://github.com/Gongoliers/Robot2019/tree/master/src/main/java/frc/robot/vision


using port report by node instead of from config

in some cases, kubemark may use different ports, the origin code uses static port, which can not connect some kubemark daemons

What type of PR is this?

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

/ok-to-test


"Global Configurations" defined in workflow XML are being lost during Import workflow (or) during "Reset workflow"

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/4984/
Test PASSed.


Reduce WC templates 7

This PR removes 3 more WC templates in checkout according to WC 8.1 which comes on Tuesday next week https://developer.woocommerce.com/2023/08/29/woocommerce-8-1-0-beta-1-released/ and improves the form validation. Tested, works fine and is already live on bootscore.me. Not each file must be reviewed, the overall check is enough.
Checkout shortcode will be replaced by checkout block in WooCommerce in November https://developer.woocommerce.com/2023/08/18/cart-and-checkout-blocks-becoming-the-default-experience/. So, we can delete file in v6.

Before
After

@justinkruit if you like it, merge it ;-)
Closes https://github.com/bootscore/bootscore/issues/343

Checkout shortcode will be replaced by checkout block in WooCommerce in November https://developer.woocommerce.com/2023/08/18/cart-and-checkout-blocks-becoming-the-default-experience/. So, we can delete file in v6.

I'm having my doubts about that. I like the possibility of changing the layout, and I think a lot of developers do so. As far as my research goes, the blocks are way more limited to code editing. So my opinion is to keep the shortcode edits we've made.

Totally agree, but I think we should provide support to the Blocks step-by-step. It seems to be not an impossible thing.

Also agree on that, but maybe keep both supported? The shortcode is far from deprecated, it's just not the default anymore. I think it's best to keep the support in the theme, and focus on how to style both the shortcodes and blocks together.

Also agree on that, but maybe keep both supported?

You're right

Then we agree on that 😉


Add coalesce operator

For Stream, this is a noop because there is no partitioning at all to begin with.
Closes #1.

Codecov Report

Merging #30 into master will increase coverage by 0.02%.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master   #30      +/-   ##
=======================================
+ Coverage   97.97%   98%   +0.02%
=======================================
  Files          17    17
  Lines         148   150       +2
  Branches        3     4       +1
=======================================
+ Hits          145   147       +2
  Misses          3     3

Impacted Files
Coverage Δ

...heide/kontextfrei/stream/StreamBaseFunctions.scala
95% <ø> (ø)
:arrow_up:

...anielwestheide/kontextfrei/syntax/BaseSyntax.scala
100% <100%> (ø)
:arrow_up:

...elwestheide/kontextfrei/rdd/RDDBaseFunctions.scala
100% <100%> (ø)
:arrow_up:

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 7f14cb8...ab026d1. Read the comment docs.


The "Rename" button cannot be translated

The "Rename" button cannot be translated. It is displayed in the Microbit editor.

There are no problems now

There are no problems now


Add a recipe to HaikuPorts

This can be closed, the recipe was added 5 years ago: https://github.com/haikuports/haikuports/commit/3bda0646da97cfd5fe1ddc6c85befb7de6d7f60b


Create showcase page

We want to create a subpage langium.org/showcase in the same style and technology (HTML + Tailwind) as the main page. Eventually this will list DSL examples that will be available each in a subpage. Let's start with the statemachine example. The examples could be listed with cards, similar to https://www.typefox.io/blog/ or so.

Just to make some notes here. My plan is to finish some layout changes that Markus started last week later today. This will be cleaning up the layout for the home page & imprint pages, since there were some issues there while refactoring things to bring in the new showcase page. This is separate from Guillaume, who is focusing on the showcase page directly.

Fixed with #52


Use LF line endings for LKGs

Building with LF line endings makes the ./lib folder (which we publish to NPM) a little over 200KB smaller than building with CRLF.
As a useful aside, it also means if one person builds the LKG on a Windows machine, and the next person on a Mac/Unix machine, that the diff isn't the entire file contents (unless you suppress whitespace changes while diff'ing).

You could consider adding ./lib/**/* text eol=lf to the .gitattributes file to enforce this line ending scheme on clone.

:+1:

Why not use LF all the time?

IIRC, our .gitattributes say check in/out as-is, so committing it as line feeds will keep it that way.

Also, mentioning that this fixes #6630.
Assuming only LKG triggers turning off debug mode, this looks fine. :shipit:

Couple of good points here. There are generally 2 flows:

Someone builds locally and both publishes and checks in. In that case, how they check in/out the files doesn't matter (as they overwrote them when building locally), so we need to build with LF.
Someone pulls the repo to get the latest and then publishes. In that case, it doesn't matter how we build locally if they just checked out the files they are publishing.

This changes addresses the first, @weswigham makes a good point and that would address the second. I'll update the .gitattributes.
@mhegazy Are you stating we should just use LF all the time (as in, for all files we build)? My concern there was I've seen many folks open/edit in historical tools such as Notepad for quick changes locally, which often don't handle LF line endings well. If we think this is a non-issue, I'm happy to make all build have LF line endings.
As a broader topic - why do we remove all conversion on our source and check-in/out "as-is"? Why not just normalize all src files (i.e. are LF in the repo, but OS specific when checked out)? Thus .gitattributes would look something like:
* text=auto
lib/* eol=lf

We have to keep things as-is so that our test cases don't get normalized -- this would cause the potential for bugs to slip through where tests passed on one OS but not the other (say, if we broke ASI only in the case where it was LF-only)

Ah, fair enough. Thanks @RyanCavanaugh (though we could still exclude just the tests dir only from normalization perhaps?)
FWIW: Making our ./lib directory be LF only by adding the line lib/* text eol=lf to .gitattributes makes that directory 430K smaller.

If it's possible to make /tests/ be as-is and everything else be OS-specific, that'd be great. I don't think we knew about that option of .gitattributes when we set up the repo.

already addressed by https://github.com/Microsoft/TypeScript/pull/9026


App client deprecation

AlgorandClient deprecation pass of app-client, transaction and debugging modules (last ones left!) and associated documentation changes. Also added a v7 migration guide.
Breaking changes:

Moved ExecuteParams type from /types/composer to /types/transaction
executeParams in params input to appDeployer.deploy collapsed into the params object itself (not a breaking change from v6 since this is a new feature from last pull request)
persistSourceMaps now takes appManager rather than client

Deprecations

getAppClient -> algorand.client.getAppClientById, algorand.client.getAppClientByCreatorAndName or algorand.client.getAppFactory (for create or deploy)
getAppClientById -> algorand.client.getAppClientById or algorand.client.getAppFactory (for create or deploy)
getAppClientByCreatorAndName -> algorand.client.getAppClientByCreatorAndName or algorand.client.getAppFactory (for create or deploy)
encodeTransactionNote -> AlgoKitComposer.arc2Note for ARC-2 and let devs convert to string or Uint8Array themselves otherwise
getSenderAddress -> Use algorand.client to interact with accounts, and use .addr to get the address and/or move from using SendTransactionFrom to TransactionSignerAccount and use .addr instead.
getTransactionWithSigner -> Use AlgorandClient / AlgoKitComposer to construct transactions instead or construct an algosdk.TransactionWithSigner manually instead.
getSenderTransactionSigner -> Use TransactionSignerAccount instead of SendTransactionFrom or use algosdk.makeBasicAccountTransactionSigner / algosdk.makeLogicSigAccountTransactionSigner.
signTransaction -> Use AlgorandClient / AlgoKitComposer to sign transactions or use the relevant underlying account.signTxn / algosdk.signLogicSigTransactionObject / multiSigAccount.sign / TransactionSigner methods directly.
sendTransaction -> Use AlgorandClient / AlgoKitComposer to send transactions.
sendParams property in the input to sendAtomicTransactionComposer -> new executeParams property
performAtomicTransactionComposerDryrun (deprecated Algorand feature)
sendGroupOfTransactions -> Use AlgoKitComposer (algorand.newGroup()) or AtomicTransactionComposer to construct and send group transactions instead.
capTransactionFee -> Use AlgoKitComposer and the maxFee field in the transaction params instead.
controlFees -> Use AlgoKitComposer and the maxFee and staticFee fields in the transaction params instead.
getTransactionParams -> Use suggestedParams ? { ...suggestedParams } : await algod.getTransactionParams().do() instead (AlgoKitComposer takes care of this for you so not likely to be needed anymore)
getAtomicTransactionComposerTransactions -> Use atc.clone().buildGroup() instead.
ApplicationClient -> AppClient and AppFactory
algorand.client.getAppClientByCreatorAndName returns an AppClient rather than an ApplicationClient
algorand.client.getAppClientById returns an AppClient rather than an ApplicationClient

New features

Added appManager.getGlobalState
Added AlgorandClientInterface type to decouple taking a dependency on AlgorandClient with creation of a circular dependency loop
Added current draft ARC-56 types to /types/app-arc56 with the root type being Arc56Contract
Added getABIEncodedValue, getABIDecodedValue, and getTupleType methods to /types/app-arc56 that allow you to encode and decode ABI values that use ARC-56 type strings (may reference structs, which can be nested)
Added AppFactory and AppClient classes and added algorand.client.getAppFactory and algorand.client.getAppClientByNetwork methods (and changed algorand.client.getAppId and algorand.client.getAppClientByCreatorAndName now return AppClient)
Added arc32ToArc56 method to /types/app-spec to allow conversion from ARC-32 to ARC-56 for backwards compatibility
Added addTransaction to AlgoKitComposer so you can add a transaction (with optional signer) to the transaction group
Added simulate to AlgoKitComposer so you can simulate a transaction group
Added AlgoKitComposer.arc2Note method to get an ARC-2 transaction note

I find the deprecations a bit confusing in this PR. First, I'd propose we come up with a better naming differentiator than AppClient vs ApplicationClient, for example using ARC56Client.
I also don't think it makes sense to deprecate individual ApplicationClient methods. The class itself is being deprecated, so it just makes things much more confusing to have some of the methods marked as deprecated. For example
Use appClient.appId and appClient.appAddress from an AppClient instance instead.

Was rather confusing to me because it wasn't immediately obvious AppClient was a different class.
If someone is using a deprecated class, all of the class/instance methods are defacto deprecated so I think individual depcreation messages just make things more confusing.

It's rare that people will even need to interact with the class name itself since it's all exposed via AlgorandClient, but I'm not opposed to renaming it to Arc56Client if we think that's beneficial, but I don't think it's particularly necessary.
The old classes and methods will be deleted after the next major version bump after this one so it's a temporary problem there are two classes with similar names and I was mostly thinking about what the end state of this will look like (also why it's in the same file rather than a different one because the end state that makes sense is to use that export path).
I agree it's unusual that there are per-method deprecations for a deprecated class, but they are purely there to provide migration hints for end users. Neil has been migrating Lora to AlgorandClient and commented that the deprecation notes had been extremely helpful with the migration process so I was trying to replicate that experience.

I also don't think it makes sense to deprecate individual ApplicationClient methods. The class itself is being deprecated, so it just makes things much more confusing to have some of the methods marked as deprecated. For example

Marking a class as deprecated only tells the user that they need to switch to something else, it doesn't give enough granular detail about how they should do that and maintain the existing behaviour. Having methods marked as deprecated allows us to inform the user how to transition to the new code in a way that maintains the previous behaviour.

@robdmoore minor comment but worth removing the zenhub workflows from gh workflows folder too as they aren't needed.

@robdmoore ci runs using node v18, but getting rollup errors on v22 when running locally:
➜ algokit-utils-ts (app-client-deprecation) ✔ npm run build

><EMAIL_ADDRESS>build
> run-s build:*

><EMAIL_ADDRESS>build:0-clean
> rimraf dist coverage

><EMAIL_ADDRESS>build:1-compile
> rollup -c --configPlugin typescript

loaded rollup.config.ts with warnings
(!) [plugin typescript] @rollup/plugin-typescript: Rollup 'sourcemap' option must be set to generate source maps.
[!] SyntaxError: Unexpected identifier 'assert'
    at compileSourceTextModule (node:internal/modules/esm/utils:337:16)
    at ModuleLoader.moduleStrategy (node:internal/modules/esm/translators:166:18)
    at callTranslator (node:internal/modules/esm/loader:436:14)
    at ModuleLoader.moduleProvider (node:internal/modules/esm/loader:442:30)
    at ModuleJob._link (node:internal/modules/esm/module_job:106:19)

ERROR: "build:1-compile" exited with 1.

Could be addressed as a minor enhancement outside of pr scope though but just wanted to note

Thanks @aorumbayev! Looks like the assert error is coming from within the rollup typescript plugin. https://github.com/wessberg/rollup-plugin-ts/issues/228
In the meantime, this library won't be able to be built on node.js 22


CC-1188: add crystal dependency resolution

@ryan-gang let's spend some time today thinking about how we can avoid the precompile commenting situation, and how we can make this more transparent to the user

Gonna keep this on hold for a bit - will revisit soon


[CI] Build with torch-nightly

Ugly, but simple (if it works).
I'd be ok with that for now.

Yes looks ok. Shall we also test with 1.6?

Yes, let's do that as well

/rebase

Very nice!

Don't know..
It's not the first time it happens.

Approved solution: https://github.community/t/manually-restart-actions-and-entire-workflows/16262/2
:joy: :joy: :joy:

I've been told it only works with that exact commit message

I'm wondering if it's necessary to run the tests 6 times


feat(client): :sparkles: Show hands in lobby

Controllers are rendered as 3d crossairs, hands are rendered as wireframe skeleton.
This is the last requirement for AppLab

I wonder how to enable this?


Add setting to allow explicit setting of isInline

I recently upgraded to 1.7.1 and discovered autoclose was no longer being respected.
Our use case involved a div as a trigger surrounding an input field that we populate on a changeDate event. Due datepicker being called on that div rather than an input, the isInline logic was resolving to true, which then essentially disables the autoclose behaviour.
I'd like to suggest a setting to force isInline such that developers can better control this behaviour.

@vsn4ik any thoughts on this PR?

Thanks @lukeburden!


Which metric is the most important one

Hi,
I did 2 experiments on the same route (short route 05):
*** Experiment 1:**
In the first experiment (and as you can see in the first attached screen-shot), I got a failure for the RouteCompletionTest with a value: 40.91%. For the OutsideRouteLanesTest,  CollisionTest, RunningRedLightTest, and RunningStopTest, I got a success with 0% for each one of these metrics.
*** Experiment 2:**
In the second experiment (and as you can see in the second attached screen-shot), I got a failure for the RouteCompletionTest with a value: 47.27%. For the  RunningRedLightTest, and RunningStopTest, I got a success with 0% for each one of these metrics. However, for the OutsideRouteLanesTest I got a failure with 3.11%, and for the CollisionTest I got a failure since I had "1 times" value for this metric.
So the questions are the following ones:
1- In a general context, which metric among these ones (RouteCompletionTest, OutsideRouteLanesTest, CollisionTest, RunningRedLightTest, RunningStopTest, InRouteTest, AgentBlockedtest) is the most important one? And If there is a metric that is more important than the other among these metrics, would you please give the order of priority for each one of them ?
2- For the specific context (context of comparing the results of the 2 experiments), the RouteCompletionTest metric in experiment 2 is higher than the one in experiment 1, but experiment 2 had  a failure with 3.11%, for OutsideRouteLanesTest metric and "1 times" value for the CollisionTest. So the question is: Which one between these 2 experiments reflects a better performance for the autonomous vehicle ?

The CARLA leaderboard has a metric called driving score, which is an aggregate metric that tells you which of these models are better.
It is described in section 4.5 Metrics in the paper.
The driving score is not printed on screen but logged in the results.json file that the leaderboard produces.
Also we recommend using the result parser to analyse the json file as it fixes some bugs in the metric calculation.


Sentiment analysis on Financial statements

💥 Proposal
Dataset: https://www.kaggle.com/datasets/sbhatti/financial-sentiment-analysis
To predict the patterns in the statements through sentiments which is helpful for determining the stock markets in the finance sector.
@khusheekapoor

Hi,
I'm Babar Rasheed (Contributor GSSOC'23) a data scientist.
I am working on that. could you assign I am giving you my best.

@rimi0602 - you can go ahead! We are assigning you 21 days for this project, after which it will be assigned to someone else if not completed. All the best!
Name the file as: algorithm_dataset.ipynb and link it in the readme of the labeled directory as algorithm - dataset.
@BabarRasheed - since we are following the first-come-first-serve policy, we will not be able to assign you this issue. However, you can create another issue on the similar lines.


Poor visualisation performance for Sugarscape Example

The Sugarscape visualisation performance is very poor, and does not render agents in the expected 2D square grid.
Sugarscape agents are discrete and have the agent variable location_id for visualisation purposes, rather than x/y.
x and y are calculated using location_id and population_width during output_agent_agent_to_VBO in visualisation.cu.
int population_width = (int)floor(sqrt((float)get_agent_agent_default_count()));
....
vbo[index].x = (agents->location_id[index] % population_width) - centralise.x;
vbo[index].y = floor((float)agents->location_id[index] / (float)population_width) - centralise.y;

get_agent_agent_default_count() returns xmachine_memory_agent_MAX defined at compile time
#define xmachine_memory_agent_MAX 1048576

There are 65536 agents in examples/Sugarscape/iterations/0.xml, not 104857.
2 solutions:

[x] Adjust the model file to only allow 65k agents, fixing the visualisation for when the number of agents is the maximum defined at compile time
[ ] Fix the root issue of using the maximum number of agents not the actual number of agents for the visualisation.

Solving the root issue is more complex, maybe something to defer until V2 @mondus ?

Discrete agents always use the maximum size for visualisation etc, so this is the intended behaviour


Update to Expressive 3.0.0alpha4

This patch updates the skeleton to use zend-expressive 3.0.0alpha4 or later. That release brings in two fixes that allow the unit tests to pass.

This patch has also uncovered a problem with using mimimum-stability: dev; when running with --prefer-lowest, it will grab the lowest stable dependency, even if it's lower than the alpha version specified.
The only libraries we're using that do not have alpha tags currently are zend-auradi-config and zend-pimple-config. I'd argue we should issue those, and I can then update this patch to set the mimimum stability to alpha.
@webimpress and @xtreamwayz — is this doable?

@weierophinney I think we can release alpha version of pimple/auradi-config packages, but please remember about the issue with (non-)shared services in these containers, see:

https://github.com/zendframework/zend-servicemanager/pull/248
https://github.com/zendframework/zend-pimple-config/pull/6
(we need to check it also in AuraDi).


db/security

regarding the measrurements[]
luckily we are using PostgreSQL so the database supports scalar lists natively. Double checked the syntax with Prisma Docs and it's right. However: lists cannot not be optional --> not possible: measurements[]?

that is good.

Regarding the new raltions within the user model
shouldn't the attribute be singular and the relation at maximum one
authtoken authokens
also, I think the raltion to projects and devices should be optional as it should be possible that the user/project exists without any project/device
Or am wrong with the annotation? Though   equals to 1...1,  [] equals to 1...n and ? equals to 0...n

no. because the user has many projects therefore he has many authtokens


RS42

Key
Value

View
https://database.shabados.com/sources/3/page/4/line/61

Source
Vaaran Bhai Gurdas Ji

Page
4

ID
RS42

Line
piqqu pivqR cilqu kir; piqswh isir Dir suKu pwieAw [

@Sarabveer please confirm whether it's supposed to be two characters or if there is a combo character available: cilqRü


chore: replace html5-qrcode with qr-scanner

Describe the changes you have made in this PR
Replaces html5-qrcode with qrscanner
Link this PR to an issue [optional]
Fixes #1832
Type of change
(Remove other not matching type)

chore: Bug fix (non-breaking change which fixes an issue)

Screenshots of the changes [optional]
Eariler vs Now:

How has this been tested?
Manually, Video:
https://user-images.githubusercontent.com/64399555/207346421-d051bbc2-724c-4f9c-8e95-7cf37dd12e25.mov
In Settings:

Checklist

[x] My code follows the style guidelines of this project and performed a self-review of my own code
[x] New and existing tests pass locally with my changes
[x] I checked if I need to make corresponding changes to the documentation (and made those changes if needed)

Not one of your changes but was wondering about the code here:
https://github.com/getAlby/lightning-browser-extension/blob/8f4f93330bc4f70bbca23a590c4b4457c4c02eea/src/app/components/QrcodeScanner/index.tsx#L136
Can't we remove the anonymous function and just pass handleStopScanning as an onclick handler?

@im-adithya two things I noticed during testing:

cannot read QR codes in Chrome when placing the QR code near the camera (when it's really big but still in focus). I always need to move it back about 15-20cm away from the camera to have any success. I didn't compare this to the QR lib on master. We should add a warning / instructions for users to make sure their scanning success rate is high.
cannot read QR codes in Firefox at all. I suspect this is because the "dynamic import" the qr-scanner README mentions doesn't seem to work in our setup!? Firefox does not have built-in support for the Barcode API i mentioned in my GH issue, Chrome has that support built in. What's the best way to force loading the worker?

(https://www.npmjs.com/package/qr-scanner?activeTab=explore)
the OLD README notes here could be helpful to get an idea what's happening: https://github.com/nimiq/qr-scanner/commit/60a2b3b2ced7d2e7567cfe030319df848816f1d4 I'm not sure how best to enforce the loading of worker in our setup / their NEW README confuses me and I have trouble seeing how to solve our problem!?

this demo using the legacy QR code library from unkpg.com works for me in Firefox (just like their official demo here which uses the dynamic import via Webpack - I suppose we cannot use something like that in a browser extension):
https://codepen.io/jankoegel/pen/yLEmGxJ?editors=1111
tested with the first QR code from this demo page.
the highlightScanRegion: true option helps a lot to show users where to place their QR code.
I was able to load the legacy qr-code package into my development extension and called the createWorker function from it. I had no luck scanning any QR code with it so far. Not sure if we need to do more to set things up properly, perhaps i'm also calling createWorker in the wrong place!?

I had no luck getting this PR to work in Firefox. @im-adithya please check with your Firefox whether you can get it running. I managed to load the legacy version of the script here (WIP code):
https://github.com/getAlby/lightning-browser-extension/tree/task-qr_jans-sandbox
this Codepen works for me in Firefox, so there has to be a way:
https://codepen.io/jankoegel/pen/yLEmGxJ?editors=1111

Closing this because of CSP issues


Deleting an Affiliation that is checked as Primary should remove the Primary Affiliation from the Contact record

Thread here: https://powerofus.force.com/0D580000034bdBK

**lurch: add

Tracking W-016962


Inbound tenant qualified URLs for webapps cannot be processed in normal tenant context

Description:
When tenant qualifying URLs for normal tenants for the Authentication Endpoint (web apps), the endpoint cannot be accessed with the tenant qualified URL due to the custom Tomcat session manager requiring all flows to be in the Super Tenant context [1].
org.wso2.carbon.webapp.mgt.CarbonTomcatSessionManager is engaged when accessing JSPs of the webapp. The session manager checks whether the tenant owning the session manager (Super Tenant) and the tenant in which the webapp is deployed are the same. Due to this, there will be an authorization failure when accessing JSPs using tenant context.
With regard to Identity Server, there are no webapp deployment use cases that should enforce a web app to be accessed only in the deployed tenant space. Therefore, for IS we should be able to use the Tomcat StandardManager over CarbonTomcatSessionManager.
[1] CarbonTomcatSessionManager
[2] TomcatWebappsDeployer

@ashendes can we close this issue?

Fixed


PDFs sobre Python

Ao invés de PDFs não poderia ser ebooks/livros gratuitos e pagos?

Python - Por onde começar?: Nesse texto o Vinicius Assef lista vários livros gratuitos inclusive.

Excelentes ebooks online gratuitos :

Problem Solving with Algorithms and Data Structures using Python

Written by Brad Miller and David Ranum. Published in Paper format by Franklin Beedle and Associates

How to Think Like a Computer Scientist: Interactive Edition

Based on the original open source book. Learn Python, try examples, answer questions, interactively, right in the book!

Automate the Boring Stuff with Python

Practical programming for total beginners. Written by Al Sweigart.

EbookFoundation/free-programming-books

This list was originally a clone of stackoverflow - List of Freely Available Programming Books by George Stocker.
The list was moved to GitHub by Victor Felder for collaborative updating and maintenance. It grew to become one of the most popular repositories on Github, with over 80,000 stars, over 4000 commits, over 800 contributors, and over 20,000 forks.
The repo is now administered by the Free Ebook Foundation, a not-for-profit organization devoted to promoting the creation, distribution, archiving and sustainability of free ebooks. Donations to the Free Ebook Foundation are tax-deductible in the US


#697: Parse regexp before regex validation

@deepakchethan Can you please push another commit ( can be a dummy commit in the app/client folder) in order to get the tests to re-run? There seems to be have been an issue with the test cases. I'd like to verify if it was an intermittent CI issue or something in this PR that caused it.
Sorry that you hit this snag.

This is the new behaviour after the fix:

Hey @deepakchethan we had an issue with our CI runs which did not run the tests properly. Can you rebase/merge the latest release branch into your branch to fix this?


Do default configuration values favor performance?

Hi,
I've been using your script for a while now. It really makes the process a lot easier.
One thing I've noticed though the performance is really bad.
Here is how it looks without VPN

And with VPN

This is running on a Vultr 4 core, 4GB, SSD VPS. The machine is definitely not pushed to the limit. Resources are plenty. I've even tested their network and the VPS performance by doing a speed test with SSH proxy instead of VPN and the speeds are very close to the no VPN graph.
Any ideas? Could this be related to OpenVPN configuration?
Thanks

The script is quite "performance friendly". It is designed to maintain a good balance between performance and security, but it is not likely that processing power is the bottleneck here.
There are many other factors to consider and a speed test isn't always a good measure of real internet performance:

Is the speed test data compressible? This is a factor to consider when testing over protocols which have compression enabled by default.

Does your ISP suck? This is a very real possibility. 2 ms of latency suggests that the speed test server is located inside their network or with extremely good direct peering. This is not representative of real performance and a dishonest practice often done to confuse customers.

Is the VPN route congested at any point? Again a very real possibility and related to the second point, we would need to investigate further to determine that. Except in New Jersey, Vultr network is not that good in my experience. At least it was the case some time ago. This can be combined with a shitty domestic ISP for disastrous results.

My suggestion is to maybe try a different ISP for the server. One closer to you and hopefully with either direct peering or quality transit to your domestic ISP.
I'm closing since this isn't an issue with the script, but feel free to let us know if you perform further troubleshooting.

Thanks. I will investigate further. One thing that led me to believe that this might be a configuration issue was that when I run the speed test through a SSH proxy to the same server intead of VPN, the speeds are OK. So that I think leaves ISP faults out.

Well, not all kinds of connections and protocols perform the same over one line. Try OpenVPN over TCP maybe? UDP usually has lower priority with many ISPs.
Other than that, make sure you are using a relatively recent version of the script, it did implement some improvements on the buffers.

Dear Nyr,
Thanks for the great script which makes setting up OpenVPN server so much easier.
You mentioned that current script 'maintains a good balance between performance and security'. Wondering if you can please share some expertise on how to twist the script to favor either performance or security?
A bold idea is we can add an option at the start of the script and let script user pick among 'Performance Favored', 'Security Favored', 'Balanced'.
Kind Regards

@DonZheng the script is pretty secure as is and generally speaking, "upgrading security" would only decrease performance without improving real world security. Performance wise, the configuration is also pretty fast and shouldn't cause bottlenecks except in very slow systems or very fast connections, but improving performance would require way too many sacrifices to be worth it.

Dear @Nyr,
Thank you for your prompt reply, as always.
Could you please share some guidance on what one should do to achieve
maximized performance, and what sacrifice/compromise is at cost?
I have googled around but most threads are too broad. In the context of
your working script, I hope we can get more executable advice from you.
THanks in advance
On Tue, Oct 22, 2019 at 7:38 AM Nyr<EMAIL_ADDRESS>wrote:

Closed #243 https://github.com/Nyr/openvpn-install/issues/243.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Nyr/openvpn-install/issues/243?email_source=notifications&email_token=AJXRGUYVPK7NI3FEFTNGUJTQPY4PRA5CNFSM4C223JM2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOULILW5A#event-2731588468,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJXRGU3XMO24RCESYA2GMOTQPY4PRANCNFSM4C223JMQ
.

The developers at OpenVPN take great care to ensure the best balance of security verses performance.

Anyone wanting to divert from the very sane defauts configured by this script should do their own informed research. For 99.9% of the users the default choices are the best option and for the rest, they should know their own specific needs (I don't).


Missing entities from 5n1 Weather Station

Hey Jeff. I stumbled on your YT video on the weekend.  GREAT video and add-on   I picked up the RF dongle and successfully installed your add-on.
I can see my 5 in 1 Weather Station but I'm not getting complete information from the 5n1 2313.  I'm getting radio info, wind direction & speed, and total precipitation but that's it.  There's no current temperature, precipitation, or humidity entities.  Is there a way to expose more of the data from the device?

Nevermind. I waited a bit and other entities appeared


Upgrade Gradle to 5.1.1

[x] This is a small change
[ ] This change has been discussed in issue #0 and the solution has been agreed upon with maintainers.

Description:
Upgrade Gradle to 5.1.1 and the Android gradle-plugin to equivalent version 3.4.1 in all demo apps. Biggest motivation for doing this is the HTTP retries feature.
Disclaimer: the feature may not be fully functional as described in this report to gradle. I hope it'd be ok for us nevertheless.

Build fails on CI because RN < 0.59.9 has issues with new versions of gradle. I've thus upgraded RN from 59.8 to 59.9 - things seem to be okay.

With respect to these limitations, however, I've also wanted to make sure that the detox .aar built with gradle version >=5 will be properly supported by apps with older gradle.
I've tested it so in these two custom builds (branch), where I've upgraded Gradle only for the lib, and not the demo apps themselves:

https://jenkins-oss.wixpress.com/view/Tree/job/detox-demo-projects-android-59-8-master/196/
https://jenkins-oss.wixpress.com/view/Tree/job/detox-android-59-8-master/460/

(the 1st of the two is more significant seeing that it prebuilts the .aar and uses it as its detox dep artifact).


adding Icospheres 6, 7, 8

@lukem12345, does there need to be some code to make these accessible from the package?

I knew there was something that had to get updated codewise. I thought those functions lived in this repo, but it makes sense that they are in CombinatorialSpaces.


python312Packages.google-cloud-secret-manager: 2.20.2 -> 2.21.0

Changelog: https://github.com/googleapis/google-cloud-python/blob/google-cloud-secret-manager-v2.21.0/packages/google-cloud-secret-manager/CHANGELOG.md

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/)
24.11 Release Notes (or backporting 23.11 and 24.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.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 351381

x86_64-linux

:white_check_mark: 4 packages built:

python311Packages.google-cloud-secret-manager
python311Packages.google-cloud-secret-manager.dist
python312Packages.google-cloud-secret-manager
python312Packages.google-cloud-secret-manager.dist


XML with DOCTYPE declaration rejected by xml2hash

An XML file with a <!DOCTYPE ...> declaration is rejected with the error 'Invalid XML'.
A sample XML file that I am attempting to parse is attached (extension changed to txt due to GitHub restrictions)
min.txt
.

Thanks for being interested.
This feature is not implemented yet, I need to find some free time to do it.

I implemented the parser for DTD, but with partial support, because full support too complex.
The parser will only skip DTD block, perhaps this will be enough.


Dropdown gets ugly when "selection" attribute is missing.

the border is missing, there's no minimum width for input or placeholder, etc.
any quick fixes?
I'm doing something like this
       <Dropdown placeholder='Select Baskets..' search className={styles.root}>
          <Dropdown.Menu>
            { this.props.values.map((option) =>
              <Dropdown.Item key={option.value} >
                <Icon name='attention' className='right floated' />
                 {option.text}
              </Dropdown.Item>
              )}
          </Dropdown.Menu>
        </Dropdown>

This is intentional.  The Dropdown can be either a dropdown menu:

Or a selection dropdown:

any quick fixes?

It is not clear what is broken or what your expectations are.  With a little more info, I may be able to point you in a better direction.  What exactly are you trying to achieve?

Oh I see, I didn't realize it was intended behavior. I guess the problem is that I've defined my Dropdown items using JSX so I get this error when using the selection attribute
Warning: Failed prop type: Prop selection in Dropdown conflicts with props: children. They cannot be defined together, choose one or the other.
in Dropdown (created by AssignBasketDropdown)
in AssignBasketDropdown (created by Connect)
in Connect (created by AssignBasketModal)
in div (created by ModalContent)
in ModalContent (created by AssignBasketModal)
in div (created by Modal)
is this part of #1380 ?

TL;DR #1380 does not resolve the warning but tries to clarify why it is temporarily present.
More info:
The error was attempted to be clarified in #1380 by updating the examples and the info messages shown above each example, however, the issue itself was not resolved.
The Dropdown's parent-child coupling with the items can only be instantiated if you use the options prop and allow the Dropdown to create the children.  During creation, the coupling is managed along with future state changes.
If you use children, there is no way for the Dropdown to add the necessary event handlers to the items.  Therefore, the Dropdown cannot manage the state of the items for you.  Hence, we show a warning as using with selection will result in a Dropdown that appears as a select but does not correctly function like one.  You'd have to wire all your own event handlers and state management, which, for this component is no small undertaking :)  The component is about ~1200 LOC to do what it currently does.

i see. thanks for the clarification!

Does it mean that if I want to create the dropitem explicitly by <Dropdown.Item>xxxx</Dropdown.Item>, then I cannot rely on the 'onChange' props of the  to get onChange event?
I really want to customize the Dropdown.Item. I want to color the label in a different color(not the default color options). Thank you.

Does it mean that if I want to create the dropitem explicitly by <Dropdown.Item>xxxx</Dropdown.Item>, then I cannot rely on the 'onChange' props of the to get onChange event?

Yes.  This makes since if you think about it.  You aren't calling onChange when a user clicks the Dropdown.Item.  When you use options, we add the appropriate handlers and state management to call onChange with the correct data.
If you skip our options prop you skip our construction of the items.  Therefore, you're left to your own code to handle those cases.

I really want to customize the Dropdown.Item. I want to color the label in a different color(not the default color options). Thank you.

You can customize the labels of a multiple section Dropdown with the renderLabel callback prop.
https://react.semantic-ui.com/modules/dropdown

How to avoid this warning where you are intentionally choosing to add selection prop and doing your own options management rendering Dropdown.Items with his owns onClick etc, because its always screaming the warning message but we are already managing our own state and data inside the Dropdown, there should be a way where you can make this appear as a select but behave like you wanted.

@ManuelPereira2016 technically, I think you can just add className='selection' to your Dropdown component to get the missing class and styles.


Support ignoreForTracing param

The jdbc instrumentation v0.0.8 has support for a param that ignores specified queries. If this is a good first issue, I could start working on adding that here

Opened #175

Did not see #144 already handling this issue. Closing


requestRichPresence returns nothing

Describe the bug
I'm trying to get rich presence of user, but it no more working. Actually it was working ok couple month ago, since that moment im never changed code, but updated lib sometimes. Now requestRichPresence returns empty users.
Versions
"steam-user": "4.25.0",
Screenshots and Error Logs
export class AppService extends SteamUser {
  constructor() {
    super({
      autoRelogin: true,
    });

    this.init()
  }

  async init() {
     this.logOn({
      accountName: config.STEAM_USERNAME,
      password: config.STEAM_PASSWORD,
    });

    this.on('disconnected', (e) => {
      console.log(`Disconnected, ${e}`);
    });

    this.on('loggedOn', (e) => {
      this.setPersona(1);
      this.gamesPlayed([570], true);
    });

    this.on('error', (e) => {
      console.log(e);
    });
  }

  getPresences(accIds: string[]) {
    this.requestRichPresence(570, accIds, 'english', async (error, data) => {
      if (error) {
        console.log(error);
        return
      }
      console.log(data.users)
  }
}

Actually my code is bigger, i just cutted extra noise. https://github.com/Satont/tsuwari/blob/cb22017d0dc1a5cc44d665e305a3d2bd354d6720/apps/dota/src/app.service.ts
accIds in [ '76561199211789795', '76561199062875574' ] format.

Tried that outside of project, might be problem on my side, becuase
import Steam from 'steam-user'

const s = new Steam({
  autoRelogin: true,
})

s.logOn({
  accountName: '',
  password: '',
})

s.on('loggedOn', (e) => {
  s.setPersona(1);
  s.gamesPlayed([570], true);
  s.requestRichPresence(570, ['76561198085222222'], 'english', async (error, data) => {
    if (error) {
      console.log(error);
      return
    }
    console.log(data.users)
  })
});

Working.

import Steam from 'steam-user';
import SteamID from 'steamid';

const s = new Steam({
    autoRelogin: true,
});

s.logOn({
    accountName: config.STEAM_USERNAME,
    password: config.STEAM_PASSWORD,
});

s.on('loggedOn', (e) => {
    s.setPersona(1);
    s.gamesPlayed([570], true);
});

s.on('appLaunched', () => {
    setInterval(() => {
        const id = SteamID.fromIndividualAccountID(343380297);
        s.requestRichPresence(570, [id], 'english', async (error, data) => {
            console.log(id.getSteamID64(), error, data);
        });
    }, 1000);
});

Always logging<PHONE_NUMBER>3646025 null { users: {} } even player in match.

You probably need to wait for a user event to emit indicating that the user is online. appLaunched is emitted synchronously when you call games played, so you're requesting RP data synchronously on the same tick as your setPersona call.

You probably need to wait for a user event to emit indicating that the user is online. appLaunched is emitted synchronously when you call games played, so you're requesting RP data synchronously on the same tick as your setPersona call.

yes, but i'm doing it in an interval, you think user never emitted then?

I think i found problem. That happens when users set this privacy setting to not public, so not an issue with library.


Why do we have a memory parameter in the node.ovc schema?

See: https://github.com/Jumpscale/ays9/tree/master/templates/nodes/node.ovc
Why do we have a memory parameter in the schema?
The value of memory will always be overridden by the value set for sizeID
Do we keep it just so that you can easily read it once the VM got deployed, without having to check the used size?

OK I understand, I think... if you don't specify a sizeID, it will use the values set of memory + bootdiskSize
How does it then know the number of virtual CPU core to use?

Closing, and rephrasing my question into #42


How to validate xmp packets are proper xmp?

How to validate xmp packets are proper xmp?

Validate based on the RDF schemas since it's JSON-LD

Peer review said it's ok.


Implements 'Overview' (you can see it in the wiki too)

Hasn't been tested with a deploy since my repo name is weird. I'll see it in the preview!
I'd love everyone's input first, but I think it would be good to merge this soon and tweak it after.

Just looked at it on the docs landing page - looks great!

It's not replacing the readme. That's why I called it 'overview' instead.

I guess it could replace the readme if we put what's in the readme at the top.

Sorry but currently it looks like it is replacing the readme - at least, I see changes in both OVERVIEW.md and README.md on Github.

@ethanbb : There are changes in both, but the change in the README.md should just be to add a link to the overview.

Wait... wat?!

Ok, that should be better. Weird.

Right now, working from these comments (mine and others'):

the rent subsidy is sort of an input and an output. It's an input for current values, but can't be an input for future values.

you can't put something as an input if it's already a calculated result from the app.

OK, I think the new version is very clear, thanks!


feature request?

Thank you so much for publishing your code. It's been useful in my attempt for tortoise TTS. You referenced Futamata et al. "Phrase break prediction with bidirectional encoder representations in Japanese text-to-speech synthesis". Futamata apparently combines the BiLSTM and BERT features to finally predict phrase breaks ("Explicit features from BiLSTM and implicit features from BERT are finally concatenated, and then the method determines whether a phrase break should be labeled after each token.")
Any hint on how to do this in your respository? Thanks so much!

I did not implement combining BiLSTM and BERT features for phrase break prediction. I perform phrase break prediction using BiSTM and BERT features separately and compare the two.
One issue that I see in combining BiLSTM and BERT features, is that the tokenisation is different in both cases. In the case of BiLSTM the learnt features (embedding) are word embeddings i.e. the tokenisation of the input text is at the word level (whitespace tokenisation). In the case of BERT, I use the standard BERT tokeniser from HuggingFace, which tokenizes text at the sub-word level.
If you are interested we can collaborate to implement this features. Please let me know if you are interested in the same.

Thank you very much. I would absolutely love to collaborate with you, although I have to be honest, that I have a computer science degree from long ago, and am a beginner in machine learning. I would be very interested in working with you as best I can. I am a quick learner! ;)


SafeShow

Create package to derive safe hashed/secret Show instances for newtypes
https://groups.google.com/forum/#!topic/yesodweb/vYsSZ1zHvXU

Irrelevant, let's just use standard show


Unable to change colour for Bullets/Numbered lists counts/dots colour.

Is there an existing issue for this?

[X] I have searched the existing issues

Flutter Quill version
flutter_quill: ^8.6.4
Other Flutter Quill packages versions
No response
Steps to reproduce
flutter_quill is not giving support to change the color of dots and numbers for both Bullets and Numbered Lists. There should be the ability to set the colors for this.

Expected results
There should be the ability to set the colors for Bullets/Numbered list counts/dots.
Actual results
There should be the ability to set the colors for Bullets/Numbered list counts/dots.
Code sample
Code sample
[Paste your code here]

Screenshots or Video

Logs
Logs
[Paste your logs here]

Hello there, on behalf the Flutter Quill Team I would like to thank you for opening your first issue. Your inputs and insights are valuable in shaping a stable and reliable version for all our users. Thank you for being part of the open-source community!

Hi, thank you for the report, until now I'm not a Quill js expert and I haven't taken a deep look at QuillRawEditor yet
but tell me if you want me to ask another maintainer to take a look at this
@adil192 You might be interested

Hey @freshtechtips, can you please confirm if it's assigned to someone?

Hey @freshtechtips, can you please confirm if it's assigned to someone?

Sorry, I really can't right now it's not up to me, well I can assign it to myself, but it will take a few months
Do you still want me to?

Example of customizing the color:

We just added that option in the dev branch
If that's what you want please confirm so I close the issue but it will take a while before it will published and breaking changes may introduced
If not, please tell me how we can help you?

Thanks dear, yes. Just one thing is this dynamic? Like if i select a color red and start adding this list then both number/dot and list test will should be red.

No, it's static, you choose the color for all the items, and you have two options, one for the ordered and unordered list, and you change the font color as well background
is there anything else you want to?

It should be dynamic as I mentioned above for smooth experience

Thanks dear, yes. Just one thing is this dynamic? Like if i select a color red and start adding this list then both number/dot and list test will should be red.

Wait, you mean select the color red as a user to any item the user selects? that's not what we did and we can but we will have to change the quill delta and add more custom data so I don't think that's confirm to Quill Js
If you mean you want to change it and customize it then that's it
but if you want a different color for each item, then can I ask how will you pick a different color for each item?? you don't have much info

1¹32q3³

It should be dynamic as I mentioned above for smooth experience

I'm not sure what you mean by dynamic?

1¹32q3³

Is this a typo or something? because I still can't understand what you mean

Check attached screenshot, This is how its currently working.
Text is in red but numbers color is black that should also be red if I selected red color from toolbar or by controller.
If you think it will effect the other users then you can add a bool parameter instead of the parameters you added to enable and disable this functionality.

Sorry for the typo.
Don't use your new changes you just made, ignore it.
Have you tried adding the lists after changing color to red?
Like select color to red from toolbar and add numbered lists you will see all the text in red but the color of numbers will be black. Numbers color should also be red.
Just give it a try please.

Hi, by adding the lists after changing the color to red. What do you mean by that? Can you explain in more detail?
We are in the middle of other processes, so we can't get you very easily
That's why I want to ask you to explain in more deep and simple details
Because in the screenshots you attached,
I get it. You just want to change the font and background color
If that's not what you meant, then can you edit the issue

Hey @freshtechtips, Any update over this

We will work on it later

It turns out this bug is pretty easy to fix

Is this what you expected?

Hi again, I'm closing the issue as solved, if you have the time please confirm if it worked like you expected it to work.

@ellet0
Hi, would it maybe be possible to also implement the static version for the color customization, like in the one screenshot you posted? In my case I don't use the colors in the quill editor but rather set the textstyle according to my current background so the dots/numbers always stay black.

Not able to spot the backgroundColor property in the QuillEditorOrderedListElementOptions or QuillEditorUnOrderedListElementOptions,
in version 10.4.5


Disable bootstrap horizontal scroll

I am trying to disable the horizontal scroll on my site. Bootstrap users suggested using
body {overflow-x: hidden;} which works, but also disables all Skrollr movement. Any ideas?

you  can look up the code of original website .maybe it works

The horizontal scroll comes from using the Bootstrap plugin, but I need to find a way to disable it without affecting Skrollr

body {overflow-x: hidden;} shouldn't affect skrollr at all as it uses y-scrolling. Or am I missing something? Also why is there horizontal scrolling in the first place?


[EPIC] Ensure disaster recovery backups for home directories

(Part of the new internal engineering roadmap, see https://github.com/2i2c-org/meta/issues/1234 for more information)
User home directories contain very important data, and we must have backups for disaster recovery. We currently have it for AWS (and it has saved us multiple times), but we need to have that for all cloud providers.
### Tasks
- [ ] https://github.com/2i2c-org/infrastructure/issues/624
- [ ] https://github.com/2i2c-org/infrastructure/issues/4391
- [ ] https://github.com/2i2c-org/infrastructure/issues/4291
- [ ] https://github.com/2i2c-org/infrastructure/issues/4424
- [ ] https://github.com/2i2c-org/infrastructure/issues/4425
- [ ] https://github.com/2i2c-org/infrastructure/issues/4487
- [ ] https://github.com/2i2c-org/infrastructure/issues/4426

Are we tracking exploration for an Azure solution for this beyond the work already done?
I met with a Microsoft rep at UKRSECon24 who recommended snapshots as a DR solution for NFS. However, it is only available on the Premium storage tier.

@sgibson91 I think we should let Azure be for now, and perhaps plan on moving people to jupyterhub-home-nfs eventually.


Ran once, then exits every time

i was able to run the gradio once. it downloaded a bunch of stuff. but didnt do any conversion. tried it again and it failed to load the UI, gave this error
Starting app...
Running on local URL:  http://<IP_ADDRESS>:7860
Traceback (most recent call last):
File "F:\F5-TTS\gradio_app.py", line 591, in
main()
File "F:\F5-TTS\venv\lib\site-packages\click\core.py", line 1157, in call
return self.main(*args, **kwargs)
File "F:\F5-TTS\venv\lib\site-packages\click\core.py", line 1078, in main
rv = self.invoke(ctx)
File "F:\F5-TTS\venv\lib\site-packages\click\core.py", line 1434, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "F:\F5-TTS\venv\lib\site-packages\click\core.py", line 783, in invoke
return __callback(*args, **kwargs)
File "F:\F5-TTS\gradio_app.py", line 586, in main
app.queue(api_open=api).launch(server_name=host, server_port=port, share=share, show_api=api)
File "F:\F5-TTS\venv\lib\site-packages\gradio\blocks.py", line 2465, in launch
raise ValueError(
ValueError: When localhost is not accessible, a shareable link must be created. Please set share=True or check your proxy settings to allow access to localhost.

Hi @TanvirHafiz .
It's probably an issue with proxy literally. Check if vpn used.
Maybe turn off tunnel mode, or if you could reach huggingface directly, just not use proxy

Didn't use proxy or any of the other stuff. No idea what's happening.
Anyway I don't forget easy way to install using pinokio. I will try that
On Tue, 22 Oct 2024, 10:29 am Yushen CHEN, @.***> wrote:

Hi @TanvirHafiz https://github.com/TanvirHafiz .
It's probably an issue with proxy literally. Check if vpn used.
Maybe turn off tunnel mode, or if you could reach huggingface directly,
just not use proxy
—
Reply to this email directly, view it on GitHub
https://github.com/SWivid/F5-TTS/issues/210#issuecomment-2428211543, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/A3IB2HQZTTF4RSJVVFVWCHDZ4XICPAVCNFSM6AAAAABQKVRDUWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRYGIYTCNJUGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

try use gradio_app.py --share to see if this working

@TanvirHafiz try use gradio_app.py --share to see if this working

this seems to work. thanks

as fixed, will close this issue.
feel free to open if further questions~


Configure script optimization flags don't work

The default optimization switches that are set when running the configure script do not change the compiler settings.  The values are put into the bazel.rc file.  They don't get into the gcc command line.  For example if I run ./configure with all of the default answers the optimization should be "-march=native".  I have tested this on multiple Ubuntu 16.04 systems with don't have CUDA.
If I then build the pip package with 'bazel build --c opt -s  ...' one example compile is this:

/usr/bin/gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -B/usr/bin -B/usr/bin -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer -g0 -O2 '-D_FORTIFY_SOURCE=1' -DNDEBUG -ffunction-sections -fdata-sections '-std=c++0x' -MD -MF bazel-out/local-opt/bin/external/farmhash_archive/objs/farmhash/external/farmhash_archive/src/farmhash.pic.d '-frandom-seed=bazel-out/local-opt/bin/external/farmhash_archive/objs/farmhash/external/farmhash_archive/src/farmhash.pic.o' -fPIC -iquote external/farmhash_archive -iquote bazel-out/local-opt/genfiles/external/farmhash_archive -iquote external/bazel_tools -iquote bazel-out/local-opt/genfiles/external/bazel_tools -isystem external/farmhash_archive/src -isystem bazel-out/local-opt/genfiles/external/farmhash_archive/src -isystem external/bazel_tools/tools/cpp/gcc3 -fno-canonical-system-headers -Wno-builtin-macro-redefined '-D__DATE="redacted"' '-D__TIMESTAMP__="redacted"' '-D__TIME__="redacted"' -c external/farmhash_archive/src/farmhash.cc -o bazel-out/local-opt/bin/external/farmhash_archive/_objs/farmhash/external/farmhash_archive/src/farmhash.pic.o)

If I explicitly set the compile options with 'bazel build --c opt --copts=-march=native -s  ...' I get the correct results:

/usr/bin/gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -B/usr/bin -B/usr/bin -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer -g0 -O2 '-D_FORTIFY_SOURCE=1' -DNDEBUG -ffunction-sections -fdata-sections '-march=native' '-std=c++0x' -MD -MF bazel-out/local-opt/bin/external/farmhash_archive/objs/farmhash/external/farmhash_archive/src/farmhash.pic.d '-frandom-seed=bazel-out/local-opt/bin/external/farmhash_archive/objs/farmhash/external/farmhash_archive/src/farmhash.pic.o' -fPIC -iquote external/farmhash_archive -iquote bazel-out/local-opt/genfiles/external/farmhash_archive -iquote external/bazel_tools -iquote bazel-out/local-opt/genfiles/external/bazel_tools -isystem external/farmhash_archive/src -isystem bazel-out/local-opt/genfiles/external/farmhash_archive/src -isystem external/bazel_tools/tools/cpp/gcc3 -fno-canonical-system-headers -Wno-builtin-macro-redefined '-D__DATE="redacted"' '-D__TIMESTAMP__="redacted"' '-D__TIME__="redacted"' -c external/farmhash_archive/src/farmhash.cc -o bazel-out/local-opt/bin/external/farmhash_archive/_objs/farmhash/external/farmhash_archive/src/farmhash.pic.o)

The performance is slower for the first example.  Somehow the optimizations in bazel.rc are not getting through to the compiler command line.

You have to build with --config=opt rather than -c opt

Thanks.  I didn't understand the explanation printed by the configure script.  It would help to have this explained in the manual.

Would you like to send a pr to fix it?
On Feb 4, 2017 9:47 AM, "Tom Baker"<EMAIL_ADDRESS>wrote:

Thanks. I didn't understand the explanation printed by the configure
script. It would help to have this explained in the manual.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/7259#issuecomment-277462389,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABaHGsoGNNuEZe8j13SYbhSZTw2a491ks5rZLmjgaJpZM4L3MlA
.

BTW, here's the recipe I use for making pull requests
https://gist.github.com/yaroslavvb/bdb0a92f2a516ebbe2d386c48f5e2c45

We have updated our documentation, and configure script at head.
But I am happy to accept another change do either our docs or the explanation printed by configure script.

@tbaker2 Are you happy with the change?  We'd be happy to accept clarifying PRs.

I don't see where the changes are.  The only commit from @gunan that I see is about cuDNN library handling.  I would like to contribute more information about optimization.  It would help to have some feedback from the TensorFlow maintainers about what the default should be.  For example, why is '--config=opt' not recommended when building with the '-c opt' flag?

config=opt was added in https://github.com/tensorflow/tensorflow/commit/c4e3d4a74e86fce3a09badd20952f067ff340f32#commitcomment-20600666 and documented in https://github.com/tensorflow/tensorflow/pull/7211
-c opt means "compilation mode=opt"
If you do --config=opt and -c opt, you are adding -c opt option twice because it's one of the options added when you do --config=opt

I see it now.  I was looking on the tensorflow.org site.  Everything looks good.

It's on master version of "Get Started/Os Setup" -- https://www.tensorflow.org/versions/master/get_started/os_setup#optimizing_cpu_performance , which means it'll eventually be on tensorflow.org default version. Closing issue since it seems resolved


k3s: Massive data corruption on ordinary system shutdown.

Describe the bug
Containers and k3s is not stopped before the filesystems are unmounted. This results in a complete loss of state and data during a completely ordinary system shutdown.
Steps To Reproduce
Steps to reproduce the behavior:

Shutdown your system.
Watch containerd shutdown after the filesystem has unmounted your disks, resulting in corruption and loss.

Expected behavior
Shutdown
k3s-killall.sh
umount
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Notify maintainers
cc @euank @Mic92 @yajo
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
 - system: `"x86_64-linux"`
 - host os: `Linux 6.1.52, NixOS, 23.05 (Stoat), 23.05.3427.e5f018cf150e`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.13.5`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Can you provide a little more information about this? Is this a nixos bug, or a k3s/containerd/something-else bug?
Looking upstream at the k3s.service they ship, I see no ExecStop or such, which is the main thing that makes me question if this is NixOS specific.
I also haven't observed issues here. I haven't yet seen anything I'd consider data-loss or corruption when shutting down (or just yanking the power cord) on my machines running k3s.
So, to try and ask some clarifying questions:

What state/data are you referring to? The k3s state (i.e. the info about what pods should be running, etc, stored in sqlite or etcd by k3s)? The state of specific pods or containers?
If k3s state, what datastore, and is the datastore saved on a separate disk (i.e. /var/lib/rancher or such isn't on your root filesystem)
If it's container's state, what volume plugin, and again is it a separate filesystem they're stored on?

Can you provide a little more information about this? Is this a nixos bug, or a k3s/containerd/something-else bug?
Looking upstream at the k3s.service they ship, I see no ExecStop or such, which is the main thing that makes me question if this is NixOS specific.

That is correct, I've had to update this on Ubuntu. It's not a native package there, though.

I also haven't observed issues here. I haven't yet seen anything I'd consider data-loss or corruption when shutting down (or just yanking the power cord) on my machines running k3s.
So, to try and ask some clarifying questions:

What state/data are you referring to? The k3s state (i.e. the info about what pods should be running, etc, stored in sqlite or etcd by k3s)? The state of specific pods or containers?

The containers all operate as if they crashed, with sqlite taking the brunt of the damage. Same goes with applications reporting back their network state on shutdown, which cannot happen when this corruption happens.

If k3s state, what datastore, and is the datastore saved on a separate disk (i.e. /var/lib/rancher or such isn't on your root filesystem)? What's the underlying filesystem?

Local xfs disk.

If it's container's state, what volume plugin, and again is it a separate filesystem they're stored on? What's the underlying filesystem?

(Different) local xfs disks.

Thanks for the quick response and additional info, appreciated!
I'm still not sure I completely follow or see any issue here though

The containers all operate as if they crashed

To me, that sounds like it's working as intended so far for a default k8s setup.
Have you set the k8s graceful node shutdown options (off by default) for the kubelet? I think enabling them is what's supposed to make pods terminate on kubelet shutdown in more cases.
I don't use those options personally, so I can't say they do work for the nixos package of k3s, but without those set, I think it's more or less expected behavior for pods to not shutdown gracefully on node termination.

with sqlite taking the brunt of the damage

Can you explain what you mean there? sqlite on XFS shouldn't become corrupted, even with an unexpected powerloss.
Is it becoming corrupted where k3s can't read it anymore on restart? Something else?

Same goes with applications reporting back their network state on shutdown, which cannot happen when this corruption happens

That's application-specific logic running on k3s, right? K8s in general doesn't guarantee graceful shutdown of pods (it can't, you might pull the plug on the machine), so it seems like that logic would need to handle this case anyway somehow.
Is there other k3s data-loss or corruption you can be more specific about, for example "After a restart, running this 'k3s kubectl' command gives an error, or presents corrupt data'", or "k3s or containerd refuses to launch with this error"?

Thanks for the quick response and additional info, appreciated! I'm still not sure I completely follow or see any issue here though

The containers all operate as if they crashed

To me, that sounds like it's working as intended so far for a default k8s setup.
Have you set the k8s graceful node shutdown options (off by default) for the kubelet? I think enabling them is what's supposed to make pods terminate on kubelet shutdown in more cases.
I don't use those options personally, so I can't say they do work for the nixos package of k3s, but without those set, I think it's more or less expected behavior for pods to not shutdown gracefully on node termination.

That's OK, but again there's a forced disk umount while the containers are running, and before they're ever notified that there's a shutdown going on. That's not good, and clearly leaves the entire application state unclean, and in some cases, corrupted.

with sqlite taking the brunt of the damage

Can you explain what you mean there? sqlite on XFS shouldn't become corrupted, even with an unexpected powerloss.

I'm unclear, just had a couple applications straight die on me in containers when this happens. Adding the shutdown hook fixed the corruption.

Adding the shutdown hook fixed the corruption.

So, you found a workaround? Could you share it please?

[Unit]
Description=rke2-cleanup
DefaultDependencies=no
Before=shutdown.target

[Service]
Type=oneshot
ExecStart=/usr/local/bin/rke2-killall.sh
TimeoutStartSec=0

[Install]
WantedBy=shutdown.target

Then you change the requires on the production service to point to the mounts. Obviously there's better solutions.

[Unit]
Description=rke2-cleanup
DefaultDependencies=no
Before=shutdown.target

[Service]
Type=oneshot
ExecStart=/usr/local/bin/rke2-killall.sh
TimeoutStartSec=0

[Install]
WantedBy=shutdown.target

Then you change the requires on the production service to point to the mounts. Obviously there's better solutions.

Sounds like a good solution to me.

I guess it should be this: https://docs.k3s.io/upgrades/killall

The killall script from k3s looks also not better than what systemd would do: https://github.com/k3s-io/k3s/blob/550dd0578f79882e1a78d8468fdbefa95faa145c/package/rpm/install.sh#L571
It also just uses kill -9

Also the rke2 variant doesn't look great: https://github.com/rancher/rke2/blob/7466261e4792e68baa2cc0c2afd3dcc929d72061/bundle/bin/rke2-killall.sh#L26

A proper shutdown would probably drain the node first, but than what about stateful data?

Drain is too much for a simple reboot. HA apps should survive a node being rebooted without problem. Actually, they should survive a node explosion.
However, it would be useful to at least cordon the node before shutdown.

Does cordon also stops containers?

No, it just informs k3s that the node is under maintenance. However, I'm thinking that adding that automatism by default can have undesired side effects. For example, if the node shuts down for unexpected reasons (an upgrade, low on battery... who knows?), workloads wouldn't be rescheduled by k8s. That's probably bad in some scenarios.

https://github.com/NixOS/nixpkgs/issues/255768 there is this bug as well with a classic switch. The kill, although brutal, would help there as well.

Going back to this issue, I think this is how k3s is designed. Quoting from the docs:

To allow high availability during upgrades, the K3s containers continue running when the K3s service is stopped.
To stop all of the K3s containers and reset the containerd state, the k3s-killall.sh script can be used.

However, I agree that nixos could provide an option to add that killall as a pre-shutdown hook.

Just passing by and linking a very related issue: https://github.com/NixOS/nixpkgs/issues/98090

Now that k3s-killall.sh script is available, it is possible to trigger it on shutdown. I'm considering this possible solution:
systemd.services.killall-k3s = {
    # "killall-k3s" is used as service name, because naming `k3s-*` introduces a loop at `k3s-killall.sh`, delaying shutdown.
    description = "Executes k3s-killall.sh on shutdown";
    wantedBy = [ "multi-user.target" ];
    serviceConfig = {
      Type = "oneshot";
      User = "root";
      # RemainAfterExit=true is required when ExecStart is missing because systemd won't
      # attempt to run ExecStop if it thinks that the service is not running.
      # RemainAfterExit=true causes systemd to believe that the service is running,
      # thereby causing it to run ExecStop at shutdown.
      RemainAfterExit = "yes";
      Restart = "no";
      # Shutdown order is the reverse of startup order. Hence the script has to be placed in ExecStop.
      ExecStop = "${pkgs.k3s}/bin/k3s-killall.sh";
    };
  };

@KyleSanderson Can you test if this solves the data corruption problem you mentioned?

I have not experienced data corruption on node shutdown so far, but it's true that node shutdown isn't flawless. If you want to make sure that all containers on a node are terminated properly (if possible) before the node shuts down, you should use the graceful node shutdown feature, as mentioned by @euank. I use it for all nodes and am very satisfied. You could do this by configuring the kubelet accordingly, something along the lines (not tested)
services.k3s.extraFlags = toString [
  "--kubelet-arg="shutdownGracePeriod=30s"
  "--kubelet-arg="shutdownGracePeriodCriticalPods=10s"
];

The killall script isn't so graceful and will just send SIGKILL to all containerd processes that were spawned by k3s. This should also happen at some point during shutdown, so I'm not sure that the killall script will fix whatever causes your corruption.
There is also an issue with local path provisioner v0.0.26, which is used by default by the latest k3s release,  that lets it ignore shutdown requests. The underlying issue originates from the sig-storage-lib-external-provisioner dependency and is there already fixed on master (by #159). However, there is no release including the fix and it was also not backported so far, although there is a corresponding issue. The whole thing affected me in the sense that systemd run into a timeout when shutting down the local-path-provisioner pod, I haven't noticed it to cause any data corruption. Anyway, if this also is an issue for you, I'm happy to provide a patch that let's you build a fixed local-path-provisioner container image.

⚠ This configuration from https://github.com/NixOS/nixpkgs/issues/255783#issuecomment-2113157680 won't work:

services.k3s.extraFlags = toString [
  "--kubelet-arg="shutdownGracePeriod=30s"
  "--kubelet-arg="shutdownGracePeriodCriticalPods=10s"
];

The docs say it clearly:

To configure these options, you edit the kubelet configuration file that is passed to kubelet via the --config flag

Instead, use this one:
{
  services.k3s.extraFlags = "--kubelet-arg=config=/etc/rancher/k3s/kubelet-config.yaml";
  environment.etc."rancher/k3s/kubelet-config.yaml" = {
    text = builtins.toJSON {
      apiVersion = "kubelet.config.k8s.io/v1beta1";
      kind = "KubeletConfiguration";
      shutdownGracePeriod = "30s";
      shutdownGracePeriodCriticalPods = "10s";
    };
  };
}

Do other people have opinions about using the kill-all script? Maybe we could add a k3s module to srvos.

We likely should expand NixOS module for kubelet config and codify the solution for graceful node shutdown as a sane default. Because everyone will need this. [If this is actually working. I have not tested yet.]

Do other people have opinions about using the kill-all script?

For which purpose?
For working around the data corruption issue, the current proposed solution is to use graceful node shutdown.

Maybe we could add a k3s module to srvos.

I don't have a need for that. But we have docs. If you think some example is missing, docs can be improved.

For which purpose?
For working around the data corruption issue, the current proposed solution is to use graceful node shutdown.

I thought that this comment https://github.com/NixOS/nixpkgs/issues/255783#issuecomment-2114508450 suggested the kill-all script instead of the graceful shutdown.

I thought that this comment #255783 (comment) suggested the kill-all script instead of the graceful shutdown.

In this case, seems the upstream patch should be applied. And then, the kill all script isn't necessary. Does it make sense?

I think https://github.com/NixOS/nixpkgs/pull/328385 should appear in the changelog.
AFAICS it won't be compatible with current solution from https://github.com/NixOS/nixpkgs/issues/255783#issuecomment-2230357277.

Big news. @rorosen solution got merged:
https://github.com/rancher/local-path-provisioner/pull/445
A beautiful solution awaits. :-)
Thanks @rorosen for the amazing work you are doing!

Since local-path-provisioner v0.0.29 release, the correct 'workaround' for this issue is:

kubectl -n kube-system set image deployment/local-path-provisioner local-path-provisioner=rancher/local-path-provisioner:v0.0.29

K3s v1.31.2+k3s1, released on October 25th, includes local-path-provisioner v0.0.30, so graceful shutdown should be working with that version.


micro:bit connected by WebUSB but getting error

   Uncaught (in promise) Error: Device in use or not found.
at o.connectAsync (pxtapp.js:1)
at async DAPWrapper.reconnectAsync (editor.js:3313)

A browser refresh got back to a good state.

Can't repro easily.

Might be better now that we actively disconnect.


Does VertexSource::decode need to return a Box?

While looking into #1408 , I've been messing around with the VertexSource implementations, trying to make it more generic. The decode trait method takes a generic source as an argument, and it's expected to return a Vec<Box<dyn BufferAccess + Send + Sync>>. I noticed that all of the existing VertexSource implementors take one or more BufferAccess types as input, box them, and then return them again. This round-tripping seems entirely unnecessary, and adds an additional Box layer.
I wonder if it would make sense to remove this part of the return value, so that decode only returns (usize, usize). The trait is presumably written to be relatively generic, so that other kinds of sources can be used that cannot be passed through in this fashion, but this flexibility is not used in practice by anything inside Vulkano. Also, if this is removed, then it may even be possible to remove the annoying requirement to wrap buffers in a Vec when doing draw calls.

VertexSource doesn't exist anymore, so I'm closing this.


integration with laravel and apache

I've deployed this project together with framework laravel on apahce, but it's not working. Is not possible ?

for what are you using Laravel? calling web services?

Hi, thank you for replying...
So, in my company we can't use nodejs and we would like to implement the
backend with laravel and front-end with angularjs...
We like so much of implementation, we have made in this way:
1- created new laravel project;
2- downloaded your implementation in public folder and executed ng build
for creating dist folder.
3- configured in laravel view.php file the path of index of angular.
In this moment, I've not created any controller. I would like only to make
your demo to work.
I'm for my English. I hope you  understand.
On Dec 15, 2017 11:29, "Camilo Soto Montoya"<EMAIL_ADDRESS>wrote:
for what are you using Laravel? calling web services?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/csotomon/Angular2-AdminLTE/issues/27#issuecomment-352005887,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AChe2MmdkuoTV97hhJ3nJ6_SjdT1k_fnks5tAnRJgaJpZM4RC8YG
.

@efcjunior angular is just a frontend framework, and works independent from the backend implementation.
You can use Laravel to create an RESTful API and call it from the angular app using the HttpClient module.
Maybe this couple of links can help you.
https://medium.com/codingthesmartway-com-blog/angular-4-3-httpclient-accessing-rest-web-services-with-angular-2305b8fd654b
https://appdividend.com/2017/09/22/laravel-5-5-angular-4-tutorial-example-scratch/


Support for Basic Auth

Ability to specify basic auth authentication scheme for the REST requests.
For example, this capability is needed to connect to Azure HBase which exposes REST end-point behind basic auth gateway: http://azure.microsoft.com/en-us/documentation/articles/hdinsight-hbase-get-started/

so no feature ?


Fix invalid billing request payload

Pull Request
Description
The xml payload had the wrong values inside "CreditorReferenceID" -> it needs to be the IK number of the entity that sends the invoice request.
Additionally the amount values inside "SpecifiedTradeSettlementHeaderMonetarySummation" need to be rounded to maximal two decimals according to the gkv
It was tested with actual codes from the AOK (own endpoint solution) and DAK-Gesundheit (bitmark api endpoint)

thank you for another important contribution @gtuk ! I will look into this tomorrow and release a new version if everything works (which Im sure it will)

1.1.2 has been released with these changes!

@fongie thanks again for the fast merge. Glad to help out with some improvements/bug fixes


The last chord is missing

I started writing a program to translate midi files into c source code for a digital music box created by @technoblogy
http://www.technoblogy.com/show?11TQ
I downloaded the midi file for this tune:
https://musicboxmaniacs.com/explore/melody/scarborough-fair_4694/
The notes collection contains all the notes, but the chords collection is missing the last chord of 4 notes.

Hi Stephen,
Thank you for pointing this out. There was a bug with chords collecting. I fixed it by 12df08beaf9a32a5a86399343d4b6e68bd8e4136 in develop branch. The fix will be in the next release. Or you can take the last version of sources from develop branch and build them to use in your application.
Can you confirm the bug is resolved?

Yes, that change fixes what I was seeing.
Thanks!


Added option to write execution time to a dict

Currently only for the simple decorator

Thanks, I'll update your change to update the measured time using the function's name as a key.


feat(website): add solidity docs

adding docs in a separate PR so the review is easier

When solidity files change, the website shall also be auto-deployed to reflect documentation change.


request definition for RiotControl

Please add the definition for RiotControl
a very small and stable library (15 lines)

Please create an issue in the definition repository: https://github.com/borisyankov/DefinitelyTyped. This repository does not hold any definitions.


Song does not play on Linux but does on Windows

Please describe your problem in as much detail as possible:
When I use the same play command on Linux and on Windows only Windows plays the song whether as Linux clears the queue and doesn't play anything.
Further information:
FFmpeg version 5.0.0 has been installed on both systems, libsodium has been installed too and also opus and libopus on their latest versions.

DisTube version: 3.3.4
discord.js version: 13.7.0
Node.js version: 16.15.1
Operating system: Arch Linux

This is the package.json
{
  "name": "galactica-bot",
  "version": "3.0.0",
  "description": "A discord bot coded in TypeScript using the Discord.js v13 library!",
  "main": "/src/main.ts",
  "scripts": {
    "dev": "nodemon",
    "format": "prettier --write \"src/**/*.{ts,js,json}\"",
    "build": "node buildCleanup.mjs && tsc",
    "clean": "node buildCleanup.mjs",
    "lint": "eslint . --ext .ts"
  },
  "repository": {
    "type": "git",
    "url": "git+https://github.com/jebediah47/galactica-bot.git"
  },
  "author": "jebediah47",
  "license": "GPL-3.0",
  "bugs": {
    "url": "https://github.com/jebediah47/galactica-bot/issues"
  },
  "homepage": "https://github.com/jebediah47/galactica-bot#readme",
  "dependencies": {
    "@discordjs/opus": "^0.7.0",
    "@discordjs/voice": "^0.10.0",
    "@distube/soundcloud": "^1.1.0",
    "@distube/spotify": "^1.2.1",
    "@distube/yt-dlp": "^1.0.2",
    "@iamtraction/google-translate": "^1.1.2",
    "axios": "^0.27.0",
    "discord-tictactoe": "^3.0.0",
    "discord.js": "^13.7.0",
    "distube": "^3.3.4",
    "ffmpeg-static": "^5.0.0",
    "libsodium-wrappers": "^0.7.10",
    "mathjs": "^10.6.1",
    "typescript": "^4.6.3"
  },
  "devDependencies": {
    "@swc/core": "1.2.196",
    "@swc/helpers": "0.3.17",
    "@types/node": "17.0.36",
    "@typescript-eslint/eslint-plugin": "5.27.0",
    "@typescript-eslint/parser": "5.27.0",
    "eslint": "8.17.0",
    "eslint-config-prettier": "8.5.0",
    "eslint-plugin-prettier": "4.0.0",
    "nodemon": "2.0.16",
    "prettier": "2.6.2",
    "regenerator-runtime": "0.13.9",
    "ts-node": "10.8.1",
    "tslib": "2.4.0"
  },
  "engines": {
    "node": "16.15.1"
  }
}

And this is the play command.
import { Command } from "../../interfaces";
import { MessageEmbed } from "discord.js";

export const command: Command = {
  name: "play",
  description: "Plays a song on the voice channel you are currently talking.",
  options: [
    {
      name: "song",
      description: "Any song name or url",
      type: "STRING",
      required: true,
    },
  ],
  run: (client, interaction, args) => {
    if (!interaction.member.voice.channel) {
      const noVoiceChannel = new MessageEmbed()
        .setColor("RANDOM")
        .setTitle("❌ Error!")
        .setDescription("You must be in a voice channel to use this command!")
        .setTimestamp();
      return interaction.reply({ embeds: [noVoiceChannel] });
    }
    const music = args.getString("song");
    if (!music) return;
    if (interaction.channel?.type === "GUILD_TEXT") {
      client.distube?.play(interaction.member.voice.channel, music, {
        member: interaction.member,
        textChannel: interaction.channel,
      });
      interaction.reply("You added a song to the queue!");
    }
  },
};

I will see if it works with Fedora and Ubuntu so I know if it's an Arch Linux problem

Check this first: Frequently Asked Questions

Check this first: Frequently Asked Questions

thanks I'll check if it works and I will reply soon!

Check this first: Frequently Asked Questions

Thank you, this worked on all of my Linux and Windows servers, but for those who don't know what to do:
uninstall ffmpeg-static npm package as @skick1234 said
on Windows install ffmpeg from their website
on Linux:
install gcc & g++ compilers required for the @discordjs/opus build script
install opus and development packages if available
install libsodium with development & static packages if available
install ffmpeg with development and lib packages if available

I have the install guide in the FAQ too.


Connection with dynamic backend based on connection string

Are there any plans to support Connection that can switch to any of the supported database connections at runtime? Might look something like the following in Python SQLAlchemy. Connection trait object doesn't work due to trait object safety.
It would be useful for code that can dynamically change the connection backend based on the connection string.

That's more or less out of scope for diesel, because diesel depends on compile time on knowing what database is used and then generates the corresponding sql specific to that database.
Also it will prevent using unsupported sql features at compile time. (For example you could only use Unsigned<Integer> using the MySql backend. For all other connections/backends this results in a compiler error. Adding a generic connection type would result in one of the two following strategies:

Support only a common subset of sql that is supported on all backends (if that even exists and if it's usefull)
Possibility to generate sql that is invalid (We should not do that, in my opinion.)

(Closed because this is nothing directly actionable for the diesel team. Use our discourse forum for feature requests.)