Feature newinit

Coverage decreased (-0.7%) to 56.669% when pulling 4a98a0a2f6186c2e95707022ab6a449fd24cfab5 on feature-newinit into 3d35be589f663ba39ce304943d23de6df3a48737 on master.

Coverage decreased (-0.9%) to 56.494% when pulling ba9295beb1b3f45495d71c1ba3362026f3717b0b on feature-newinit into 3d35be589f663ba39ce304943d23de6df3a48737 on master.

Coverage decreased (-0.9%) to 56.494% when pulling ba9295beb1b3f45495d71c1ba3362026f3717b0b on feature-newinit into 3d35be589f663ba39ce304943d23de6df3a48737 on master.


Key vault access policy related errors due to case sensitivity

Summary
In a recent version of azurerm (2.48), a fix was done to normalize the case of permissions. More details can be found here: Pull request
The error
The fix from the PR (10593) causes the latest version of terraform-azure-mach-shared to fail when running "terraform apply"
This is what happened:

Error: expected certificate_permissions.0 to be one of [Backup Create Delete DeleteIssuers Get GetIssuers Import List ListIssuers ManageContacts ManageIssuers Purge Recover Restore SetIssuers Update], got get
on .terraform/modules/shared_infra/domain.tf line 32, in resource "azurerm_key_vault_access_policy" "frontdoor_access":
32:     "get",
Error: expected certificate_permissions.1 to be one of [Backup Create Delete DeleteIssuers Get GetIssuers Import List ListIssuers ManageContacts ManageIssuers Purge Recover Restore SetIssuers Update], got list
on .terraform/modules/shared_infra/domain.tf line 33, in resource "azurerm_key_vault_access_policy" "frontdoor_access":
33:     "list",

As I can't push a branch and create a PR, here would be a patch for this:
0001-Fix-the-case-of-the-defined-policies.patch.zip


Update Documentation for new Typescript Version Flow

https://github.com/Microsoft/vscode-docs/pull/811


CORE-6698 Vnode reconciler goes down

The problem is, Vnode reconciler goes down.
Vnode reconciler component depends on VirtualNodeInfoWriterComponentImpl (VirtualNodeInfoWriteService is used as the Kafka writer in Vnode info reconciliation).
In VirtualNodeInfoWriterComponentImpl.onConfigChangedEventReceived we would switch coordinator status to DOWN every time we would receive a ConfigChangedEvent to mark that component is down during resources re-creation. However, that is propagated to components depending on this one and therefore to Vnode reconciler.

removes VirtualNodeInfoWriterComponentImpl switching to DOWN every time we receive a ConfigChangedEvent.
improves logging for Vnode reconciler readers and writer.

Please hold on with review as an unwanted commit appeared. Will close and re-open PR against release/os/5.0-DevPreview2

Please hold on with review as an unwanted commit appeared. Will close and re-open PR against release/os/5.0-DevPreview2

Potentially possible to fix-up this PR by force pushing to your branch: kyriakos/CORE-6698-vnode-reconciler-goes-down

Please hold on with review as an unwanted commit appeared. Will close and re-open PR against release/os/5.0-DevPreview2

Potentially possible to fix-up this PR by force pushing to your branch: kyriakos/CORE-6698-vnode-reconciler-goes-down

Thank you @vkolomeyko but unfortunately that didn't work.

Fixed now, is ready for review.


initial code - application-manager

fixes https://github.com/vmware/dispatch/issues/90

Just a minor change and I am fine with this patch :)


feat(js/plugins/ollama): Ollama embeddings

This is a draft of adding Ollama embeddings to Genkit js
together with  https://github.com/firebase/genkit/pull/751 this should resolve the following:
https://github.com/firebase/genkit/issues/728
Checklist (if applicable):

[x] Tested (manually, unit tested, etc.)
[ ] Changelog updated
[ ] Docs updated

could you please also update https://github.com/firebase/genkit/blob/main/docs/plugins/ollama.md


Updating readme with WinRM details

Hi @azooinmyluggage, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;


bug(DatePicker): Incorrect parsing of date when typing YYYY-MM-DD format

Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
Date picker input updates to the previous day when using this specific format: YYYY-MM-DD
You must use hyphens and double digit month and day (from my testing).
Reproduction
Steps to reproduce:

Problem exists in the documentation page = https://material.angular.io/components/datepicker/overview
Manually type in 2023-02-13 into the first test input
Press tab to blur input
See that the date has been updated to 2/12/2023

Expected Behavior
Date should update to 2/13/2023
Actual Behavior
Date actually updates to the previous day, in this case 2/12/2023
Environment

Angular: 15
CDK/Material: 15.1.4
Browser(s): Chrome
Operating System (e.g. Windows, macOS, Ubuntu): Tested in Windows and macOS

I'm going to consider this a non issue because the desired input pattern for that datepicker is MM/DD/YYYY. Your input would work on a different locale - https://material.angular.io/components/datepicker/examples#datepicker-locale


volume control hassles

Trying to do volume control when playing but the only way to do that is through creating a new instance that I then have to keep track of since if it goes out of scope it doesn't play. Perhaps I'm doing it wrong. Ideally I would like to do something like Sound.play(url: url, withVolume:0.3 ....
Is this possible?

Thank you. I made a wrapper.


fix not able to import with 'vue-chemistry'

It was not able to import with the code below.
import { reactify, set } from 'vue-chemistry'

Importing subdirectories was ok.
import { sum } from 'vue-chemistry/math'

Tried with vite 2.0.0-beta.21.

Thanks!

Thanks!


[stable/jenkins] Add optional mapping for Ingress RouterName

Signed-off-by: Mats Faugli<EMAIL_ADDRESS>Is this a new chart
No.
What this PR does / why we need it:
I got this error when running helm install to our Openshift cluster: Error: UPGRADE FAILED: error validating "": error validating data: ValidationError(Route): missing required field "status" in com.github.openshift.api.route.v1.Route. This PR allows to fix this error by setting the attribute .Values.master.route.ingressRouterName.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/ok-to-test

/retest

@fowlie Can you add an entry in CHANGELOG.md?

Sorry for the delay. I noticed the upstream version was bumped in the meantime, so after a rebase I bumped the version number in this PR.

Hm, probably shouldn't have done the rebase. I'm not very used to submitting PRs like this, any tips on how to fix this? :see_no_evil:

This seems related to #20624 although the diff looks cleaner there.


Remove reduce option from F.gaussian_nll

This PR removed reduce option from F.gaussian_nll.
Related to #2558

Following the tentative conclusion I wrote here, I close this PR. Thank you.


new userId module - neustar's fabrick

accompanies https://github.com/prebid/Prebid.js/pull/5802

docs pr needs a change to download.md as well.

Thanks, @jdwieland8282 .  I just updated it.

Thanks, @jdwieland8282 .  What else needs to be done to merge this in?

Hi @andersonbd1 we are just waiting for the pb.js 4.11 release to go out, once that is done we go through and merge all the docs pr's. If this step is missed as happens occasionally just at me and I'll merge. pb.js 4.11 should happen today.

gotcha - thanks for the explanation, @jdwieland8282 .


Does Thanos have a dependency to Log4j CVE-2021-44228

Official statement/comment needed regarding the vulnerability issue mentioned in subject. Thank You.

Hello. Thanos is a Go project and does not have any Java dependencies thus it is not impacted by issues regarding log4j (:

I hope this helps. Closing the issue to keep the issue tracker clean. ;P


feat(data-table-v2): add selectable row styles

Ref: #1303

Adds selectable table styles.
Note: batch actions has still not been styled, this is specifically just row styles.

There's an extra 12px padding to the left and right of each td and 8px on th text. This causes the spacing to be too large between the checkbox and text.

The checkbox component is not 1-to-1 with design specs. That's a checkbox issue, but we would want to make sure it can be updated in data table when that's resolved.


Session.close() should not break job execution within a session

What is the expected feature or enhancement?
The primitives allow for async job execution.  That is to say that one would think that code of the form:

with Session(backend=backend):
    sampler = Sampler()
    estimator = Estimator()
    sampler_job = sampler.run(qc)
    estimator_job = estimator.run(qc2, oper)

would submit two async jobs that execute within the specified Session.  However, when the code inside the context is done, session.close() is implicitly called which causes the jobs to enter the usual fair-share scheduler rather than executing back-to-back like they would inside a session.  This makes async jobs inside a session context pointless as one always has to block and wait for the session to remain alive.
Thus the only way to do actual async job execution is to keep the session alive using:

session = Session(backend=backend)
sampler = Sampler(session=session)
estimator = Estimator(session=session)
job1 = sampler.run(qc)
job2 = estimator.run(qc2, oper)

and calling session.close() only after all jobs are done (or more likely not at all, with a 5min idle duration on the device).
Alternatively session.close() (or something like that) should not break the job execution within the session, but rather be equivalent to the statement "I am done adding jobs to this session".
Acceptance criteria
One can batch jobs async within a session and close the session with jobs still executing within the session

Closing as this was addressed by the recent sessions improvements


Sharing get_pos() between multiple threads?

In an audio playing application (mainly talking about music players here), you'd want to have multiple threads, one that controls playing the music, one that controls the gui / event thread loop, and in the newest version of rodio, one that updates the time elapsed / scrubbing bar on the bottom of the application. (Which is great, I love this addition)
However, I am struggling to see how I can implement this for my application, since the mutex will only allow one thread at a time to read / write to the self.position field, this makes it difficult to adhere to the "multiple threads" concept above, since the music thread will own the sink, and the only way to view that value, is via the sink (sink.get_pos()), which the "time elapsed" thread does not have access to. (Cannot pass &Sink to the thread since iced requires message's contents to impl Debug)
I'm not sure if I am misunderstanding this, or if I am not following the architecture in mind when this api was designed, but a function to maybe return a handle to some wrapper that contains the self.position / Duration would be perfect. I could create a PR, but I have no clue what type I should wrap it in? Especially if we are very performance-conscious, since there would be some overhead writing to an ArcSwap or something, vs the regular mutex.

I had a look at your app. As I read it your app 'waits' until a change is needed try_recv then does something with the sink and gets back to checking for needed changes.
Quick sidenote, why try_recv and not recv().await?
What you could do is each few milliseconds run sink.get_pos() there and send that to the gui through a mpsc. I believe you already get one from iced: sender.
You could try wrapping the recv() call with a timeout (I dont get the difference between an io-future and a 'normal' future in async-std, so maybe this function is the wrong one). And set the timeout duration for about a frame of time. Or even better calculate the timeout such that you send a position every frame.
Then every time you time out you check the position and send it to the gui.
Good luck!

I got it working with what you suggested. I was concerned about the additional overhead of sending the values (and the two calculations that will be performed by the main blocking thread in fn update. I think I'm overthinking the 'performance hit' that occurs.
I'll close the issue, thanks.

I was concerned about the additional overhead of sending the values

A mpsc can easily handle millions of messages a second. Whenever you think something might be a performance hit just try it. Usually it isnt, Rust is great like that :)


add java format style

Add java style in clang-format to avoid format error when writing java code:

Fe use checkstyle check the code. This Pr is not compatible with it.
You can see this.

Sorry, I don't descriple it clearlly, its some editor will use this style file and clang-format to format code when writing code, but now it does not include java style in this file.


Support to show "unassigned" keybindings in the release notes editor

VSCode Version: 1.8.0 Insiders
OS Version: Windows 10

Unlike the website key binding rendering which returns "unassigned" for missing command key bindings, the in-product rendering simply returns the command id string.  To workaround this, we've been manually setting the key binding to "unassigned" in Markdown. This is a poor workaround when a key binding exists for some platforms (ex. Linux) but not others.
Perhaps getKeybindingLabel() could be changed to return "unassigned" instead of 0 for missing key bindings. Note that getKeybindingLabel() is used through out the product so care should be taken that a change doesn't cause a regression somewhere else.

@gregvanl @bpasero I don't understand what this issue is about, see also other comment in the commit. Is this about the website, is this about vscode? Can you share a screenshot where something is wrong?
@bpasero You seem to have an understanding, giving to you for now.

I think this is about showing the proper thing in the release notes editor when a keybinding is unassigned.
@joaomoreno do you know where the release notes editor resolves the keybindings?

I can take this.

I reverted the previous commit to hard-code "unassigned" in the release notes so you can see the difference between the website rendering for unbound commands:

and in-product rendering:


Updating ML extension to use latest public preview for SDKv2

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
The precondition is to put your code inside this repository and upgrade the version in the pull request but do not modify src/index.json.

ML extension


[networking_mapping] Add the instances full mapping logic

As a pull request owner and reviewers, I checked that:

[x] Appropriate testing is done and actually running
[x] Appropriate documentation exists and/or is up-to-date:

[x] README in the role
[x] Content of the docs/source is reflecting the changes

/approve


[stable/opa] Add affinity settings to OPA deployment

Signed-off-by: Igor Belikov<EMAIL_ADDRESS>Is this a new chart
NO
What this PR does / why we need it:
Add the option to specify affinity/anti-affinity settings for OPA deployment, allowing more sophisticated scheduling scenarios. One of the examples is given in values.yaml comments -  scheduling OPA on master nodes, 1 replica per node.
Which issue this PR fixes
N/A
Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/assign @timothyhinrichs


Bitcoin node space occupies too much disk space, how to reduce it and ensure the normal operation of ord data?

Bitcoin node space occupies too much disk space, how to reduce it and ensure the normal operation of ord data?

Running Bitcoin Core in pruned mode is not supported at this time.
It is possible to do so if you were to stub all code that may request blocks outside of your pruned region, but this would be a non-optimal solution and instead I would redesign the indexer logic to not rely on Bitcoin Core outside of initial sync.

Running Bitcoin Core in pruned mode is not supported at this time.
It is possible to do so if you were to stub all code that may request blocks outside of your pruned region, but this would be a non-optimal solution and instead I would redesign the indexer logic to not rely on Bitcoin Core outside of initial sync.

It's actually not possible because the indexing and server both rely on using txindex, which is incompatible with pruning.


Added AsyncLocationLoading

Codecov Report
Attention: 1 lines in your changes are missing coverage. Please review.

Comparison is base (5124aaa) 100.00% compared to head (1b128a5) 95.65%.

Files
Patch %
Lines

...rces/AsyncLocationLoader/AsyncLocationLoader.swift
95.65%
1 Missing :warning:

Additional details and impacted files
@@             Coverage Diff             @@
##              main       #2      +/-   ##
===========================================
- Coverage   100.00%   95.65%   -4.35%
===========================================
  Files            1        1
  Lines            1       23      +22
===========================================
+ Hits             1       22      +21
- Misses           0        1       +1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Adds 'FORCE_COLOR' env option.

See #13 and #17

CC // @simcha @bguiz @rmg @sindresorhus

sweet!
this PR has my vote.
W: http://bguiz.com
On 22 February 2015 at 21:17, Joshua Appelman<EMAIL_ADDRESS>wrote:

See #13 https://github.com/sindresorhus/supports-color/issues/13 and #17
https://github.com/sindresorhus/supports-color/pull/17
[image: demo]
https://camo.githubusercontent.com/4328631a8e75771052d3fce196610ca368a12980/687474703a2f2f672e7265636f726469742e636f2f6330487130366e7569512e676966
CC // @simcha https://github.com/simcha @bguiz
https://github.com/bguiz @rmg https://github.com/rmg @sindresorhus
https://github.com/sindresorhus
You can view, comment on, or merge this pull request online at:
https://github.com/sindresorhus/supports-color/pull/18
Commit Summary

Adds 'FORCE_COLOR' env option.

File Changes

M index.js
https://github.com/sindresorhus/supports-color/pull/18/files#diff-0
(4)
M test.js
https://github.com/sindresorhus/supports-color/pull/18/files#diff-1
(5)

Patch Links:

https://github.com/sindresorhus/supports-color/pull/18.patch
https://github.com/sindresorhus/supports-color/pull/18.diff

—
Reply to this email directly or view it on GitHub
https://github.com/sindresorhus/supports-color/pull/18.


restore: retry if deliver KVs to importer

Signed-off-by: Lonng<EMAIL_ADDRESS>
What problem does this PR solve?
2019/04/28 07:50:23.039  [error] [`db1903_baofu`.`cm_entry`:11] [/data1/hybrid/baofu/db1903_baofu.cm_entry.3771.sql:0] error EOF
2019/04/28 07:50:23.039  [info] [`db1903_baofu`.`cm_entry`:11] encode kv data and write takes 1m11.606816959s (read<PHONE_NUMBER>9, written 392441556)
2019/04/28 07:50:23.039  [error] [`db1903_baofu`.`cm_entry`:11] error EOF

What is changed and how it works?
Retry if deliver KVs to the importer failed.
Check List
Tests

Unit test
Integration test

Side effects
Related changes

/rebuild

/run-all-tests

/run-all-tests

@kennytm @july2993 PTAL

/run-all-tests


[Cross post from original Repo] Invariant Violation: requireNativeComponent: "RNSketchCanvas" was not found in the UIManager

Cross-posting from the original repo seeing as it is likely dead...
I simply have a minimal example of the first code block listed on the repo's NPM page.
I have installed and linked properly. I cannot seem to get around this error.
I am using Expo CLI, if that is relevant.
I believe I have to "Detach" and run with expo kit in order to do anything that requires linking?

Yes, that means the library is not linked properly
I'm not familiar with expo, but if it's possible to detach from it and access the native code so you can link manually or via "react-native link @gigasz/react-native-sketch-canvas" i highly recommend it

I'm closing this issue since it's not a but or a feature request

@Gigasz when using react 61.5 do we still need to link package?


Minor code style edits

Suggesting some minor code style edits to make the script more pythonic (easier to read for python developers). Mostly length checks, use of context manager for file operations, and removal of C-style brackets for condition statements.

I'm actually re-doing majority of the code especially with the newest features being implemented. Most of that was rushed and since I'm used to JS I keep adding unneeded things especially with the conditional statements. I'll keep you updated. 👍

If you would like to further improve this project on the next update feel free to add me on discord
Discord: kiyomi<PHONE_NUMBER>47601674)


Callback function afterFetch or Equivalent

sails version : 1.2.4

Is there a way I can call a function on a model after fetching a record?
Tried Approaches.
tried adding customToJSON to my model configuration but it has not worked.
Is there a callback function equivalent to afterFetch ?

Hi @edmondsylar, You might want to try making a helper that runs logic after .fetch() and call that instead of .find()

@eashaw Thanks a lot for the help, though I got a way around using a policy, it sure achieves what I wanted but has affected how i use the policies meaning I will have to change that and then probably use this. though surely my understanding of helpers is really different, don't know how am supposed to use them in this case, if you can help and elaborate more, it would be surely so good

@edmondsylar Theres an example helper in the Sails docs that might help. https://sailsjs.com/documentation/concepts/helpers/example-helper#an-example-helper

@eashaw Thanks a lot this sure will help


Advanced dupe saves stuck on "opening"

Whenever I open a dupe I make it is stuck on "opening" and I cant open any other dupes and it says "adv dupe is busy". I can open dupes from a long time ago but if I save a new one now this problem happens. Adv dupe is unusable in this state and is impossible to open any new projects.

Duplicate of https://github.com/wiremod/advdupe2/issues/164 and https://github.com/wiremod/advdupe2/issues/163

Will leave open until the error handler is fixed


TinySQLite.Error: SQL error or missing database (1)

I get TinySQLite.Error: SQL error or missing database (1) when trying to save a object.
 let database = SwiftyDB(databaseName: "Elements")

        let element = Element()
        element.id = 1
        element.name = "hu"

        database.asyncAddObjects([element]) { (result) -> Void in
            if let error = result.error {
                // Handle error
                print(error)
            }
        }

What does your Element class implementation look like?
Are you using v1.1.1?

Yes using v1.1.1
Element:
`//
//  Element.swift
//  Elementaert
//
//  Created by Emil Pedersen on 09/05/16.
//  Copyright © 2016 LET Software. All rights reserved.
//
import Foundation
import SwiftyDB
class Element: NSObject, Storable {
var id:Int = 0
var name:String = ""
var symbol:String = ""
var atomicNumber:Int = 0
var atomicWeight:Int = 0
var group:Int = 0
var period:Int = 0
var valenceElectrons:Int = 0
var primaryOxidationStep:Int = 0
var secondaryOxidationStep:Int = 0
var tertiaryOxidationStep:Int = 0
var electronegativity:Double = 0.0

override required init() {
    super.init()
}

}
extension Element: PrimaryKeys {
class func primaryKeys() -> Set {
return ["id"]
}
}`

Try updating now. There was an issue with escaping column names in queries. Should be fixed in 1.1.2

It does not work with async. No database is created. No error is printet.
database.asyncAddObject(element) { (result) -> Void in
if let error = result.error {
// Handle error
print(error)
}
}
But if I use database.addObject(element) it works, so I will use that. Thanks :)

I copied your class and retrieval code, and it worked. I'm not saying that there is no problem, only that i cannot reproduce it. If you could provide a project where the bug is present, I would be very grateful :) If not, make sure that you have updated the Podfile with version greater than 1.1.1, and run pod update


wormhole.test.test_cli.PregeneratedCode.test_slow_text failing

For some reason wormhole.test.test_cli.PregeneratedCode.test_slow_text seems to be failing now on master sometimes (well, "often" might be better word). It doesn't always fail locally, but seems to more reliably fail in CI.
Not sure if related, but wormhole.test.test_wormhole.Wormholes.test_welcome also sometimes fails (with LonelyError instead of the expected WrongPasswordError) .. this also looks like a "timing thing" to me.

I've tried several older Twisted releases and magic-wormhole releases back to 0.11.0 so I'm not sure if something changed or if they just "mostly passed" before ... running one of the "maybe failing" tests with -u is a good way to repeat it (takes < 10 tries for me locally).

I'm convinced at least the LonelyError one is a timing issue because putting a delay in the test very reliably fixes it (250+ iterations no failures).


[Discuss] Bootstrapper package installation should use pinned versions

When an image associated with a pipeline node runs, the bootstrapper script ensures that the set of python packages it needs are their latest versions.  It does this by running the equivalent of pip install --upgrade <package> for each of the top-level packages it requires.  This has the following issues:

The --upgrade flag, by default, updates the top level packages to their latest versions, but does not ensure that dependent packages are also updated to their latest versions.  This can lead to the behavior found in https://github.com/elyra-ai/elyra/issues/437 where the image container still referenced an older submodule.  Using --upgrade-strategy=eager would trigger the updates of all packages to their latest versions - which could also break upstream dependencies.
The fact that the bootstrapper runs on every container invocation implies that should one of these updated versions introduce a fatal issue, exactly zero notebook nodes will succeed at the point in which the flawed package has been released and until the flaw has been addressed.  These failures will be global.
The primary tenant of containers is that they introduce reproducibility.  However, by updating even the top level dependencies to their latest version on each invocation implies that two otherwise identical runs could produce different results.

I believe we should build a manifest of explicit versions for each of the top-level dependencies we need and perform the pip install --upgrade <package>==<version>.  In addition, this manifest should reside within the repository and be referenced by documentation so that users have a means of preparing their own images for use by kfp-notebook.
Here are the top-level packages that the bootstrapper deploys: minio, argparse, papermill, nbconvert, nbformat, ipykernel.   Since important packages like jupyter_client and ipython are not represented, it would be a good idea to include them as well.
Here are their versions as of right now...
minio==5.0.10
argparse==1.4.0
papermill==2.1.1
nbconvert==5.6.1
nbformat==5.0.6
ipykernel==5.2.1

jupyter_client==6.1.3
ipython==7.13.0

We should use these versions - or whatever we qualify with - to produce somewhat[*] consistent, reproducible results.
[*] Note: we should ideally have a complete manifest of sub-packages to totally eliminate the possibility of failure on each run.  Another option would be to use an init container which houses previously installed versions and prepend those packages to the packages of the target container.

Also, if a given image already has an old version of a given dependency (e.g. jupyter_client) then it does not get updated which I think we should always update particularly if we want to get to a set version.


vivaldi: 1.9.818.44-1 -> 1.10.867.38-1

Motivation for this change

Update to version 1.10.867.38-1
Drop i386 arch. Vivaldi has suspended support for Linux 32-bit for Vivaldi 1.10. Unfortunately, this is due to Chromium suspending support for it and maintaining it themselves would take too much resources. See https://forum.vivaldi.net/post/142489.
Update dependency on gtk2 to gtk3.
Move dependency patchelf from buildInputs to nativeBuildInputs.

Things done

[x] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

may be keep 1.9 for i386 ?

may be keep 1.9 for i386 ?

I have asked on IRC and someone expressed the opinion that freezing a web browser engine sounds risky security-wise, and I agree.
Vivaldi is evolving quickly and soon version 1.9 would be lacking too much from upstream. I do not think it should be kept in nixpkgs.


Create rust.yml

Issue
Link your PR to an issue
Fixes #___
Description
Please describe your pull request.
Testing
Describe the best way to test or validate your PR.
Checklist
🚨Please review the guidelines for contributing to this repository.

[ ] 🤔 CONSIDER adding a unit test if your PR resolves an issue.
[ ] ✅ DO check open PR's to avoid duplicates.
[ ] ✅ DO keep pull requests small so they can be easily reviewed.
[ ] ✅ DO build locally before pushing.
[ ] ✅ DO make sure tests pass.
[ ] ✅ DO make sure any new changes are documented.
[ ] ✅ DO make sure not to introduce any compiler warnings.
[ ] ❌AVOID breaking the continuous integration build.
[ ] ❌AVOID making significant changes to the overall architecture.

💔Thank you!

experimentation toward https://github.com/microsoft/electionguard-verifier/pull/15


Exploratory network data science notebooks.

Notebooks which uses different network science techniques and algorithms to explore and analyse real world datasets.

http://snap.stanford.edu/data/index.html

I would be very interested to contribute to the particular issue and project in general. However, it is my first time contributing to any github project so I would appreciate indulgence, support and feedback. In detail, I have worked with the networkx library for a graph analysis assignment so I already have some experience. To my understanding: you would appreciate to have a graph analysis on a real world dataset (of the above link) containing graph theory algorithms and techniques like degree measures, topological properties, clustering effects, bridges, communitites etc. I hope I can be of some assistance to you.

Hello, I think I will make a notebook to explore and analyse Social circles from Facebook (http://snap.stanford.edu/data/ego-Facebook.html)


Set orientation and fill area with hexagons

Lets assume I have one area (size: 1000x800):
+------------------------------+
|  (0,0)             (1000,0)  |
|                              |
|                              |
|  (0, 800)        (1000,800)  |
+------------------------------+
What I now want to do is to fill this area completely with a hex grid. So the cell 0,0 should be at position (0,0) and the hex cell with the "biggest" coordinates should be at position (1000,800).
So what I would need would be:

Ability to setup the hex grid to be aligned top-left (is currently always(?) center)
Ability to calculate how many hexes I would need to fill the rectangle completely

Is this already possible with the library or do I need to develop something on my own?

I would suggest looking add the shapes  module, something like flat_rectangle.
The functions are very simple, so you can always create a new one from there

It may be worth enabling Discussions on this repo so we can migrate questions like this into them :)


from mpl_toolkits.mplot3d import Axes3D fails for older versions of matplotlib

This borks people who don't have a newer matplotlib installation.
Is it possible to not have this dependency?

Which version of matplotlib should i use to try to reproduce?

@dabacon Ping. Would love an example program that does this too.


[PDI-13271] External Ids are not handled properly when incoming key is null

When a null value is provided as an ExternalId in a Salesforce output step the reference field is cleared as expected.
This PR supersedes PR#434.

@jbleuel @mattyb149 Is there anything else I can do to get this PR merged?

The Jira case currently has no Fix Version. If it is selected to be included in the next release (probably 5.4.) then the Fix Version will reflect that and the PR will be merged.

A fix has been merge on #1786. Closing this PR.


Ukrainian translation crashes

Please check the troubleshooting guide in the Wiki before submitting an issue.
Describe the bug
Whenever user select Ukrainian localization, Mod Manager wait for a while (1sec) and then closes, it also displays everything on English in that brief moment. If useer has Ukrainian as default, it will crash on startup with same 1 second of the window on english
To Reproduce
Steps to reproduce the behavior:

Switch to Ukrainian Locale in Settings

Expected behavior
Mod Manager displaying ukrainian language
Screenshot of before (v1.0.5)

Screenshot after (v1.1.0)

Note that i can't do anything while it's in that moment, it's just frozen and crashes after a second
VS shows this (App.xaml.cs line 130):

And the Error message as .txt:
message.txt
Should be all, let me know if i forgot smth

Fixed in ae2232e382878a10474136cf740f46ed1c65c17c


Allow frameworks to specify the minimum Node.js version

All Node.js-based frameworks have a specific minimum Node.js version.
At the moment, if a user runs a framework on Netlify with a Node.js version that's too old, the framework will most likely fail at require()-time with some cryptic error message due to some unsupported JavaScript feature or missing Node.js core method. Users might be confused and think this is a bug in Netlify.
Since we detect frameworks, we could use that knowledge to infer the minimum Node.js version. We could do this by adding a new nodeVersionRange field to the frameworks declarations:

The value would be a semver range like ^10 || >=12 or >=12.20.0 since some frameworks support Node.js version range that are more complex than just >=version.
The minimal version can still be inferred (for example to use as a default Node.js version) using node-semver minVersion() method.

We could use that information to either:

Warn users when using the wrong Node.js version, for example by printing a message in the build logs.
Choose the default Node.js version run in builds

I would personally favor only warning users and not overriding the Node.js version based on that information because:

The logic to decide on the default Node.js version is already quite complicated as mentioned by @ingride
Users might not expect that Node.js version unless documented, and documenting it clearly might be difficult if it's framework-specific.
When using multiple frameworks, their ranges might be in conflict. This could be fixed by using an intersection, but I am wondering whether that intersection might be empty in some cases.
It is consistent with our current strategy for Build plugins. For Build plugins, we not only warn users but fail the build altogether when the Node.js version is incompatible. We do this based on the engines.node field in package.json. This is also consistent with how npm and yarn behave during npm install (although one warns only while the other fails).

That being said, I could also see an argument being made that Netlify users might expect the platform to just use the right Node.js version so things "just work" with their chosen framework.
Note: this discussion was brought up due to Nuxt supporting only Node.js >=12.20.0.
I would be very curious to learn more about what you all think about this idea, especially @ingride @JGAntunes @erezrokah @verythorough @lukeocodes @ascorbic. Thanks!

My concern here is that different versions of frameworks require different versions. Could we read it from the framework's engines.node field, rather than the plugin's?

I guess we need to know before we install it, but we could just grab the framework's package.json before installing the right node version

My concern here is that different versions of frameworks require different versions. Could we read it from the framework's engines.node field, rather than the plugin's?

Yes, this makes lots of sense. Please note that I meant the above to be specific about frameworks, not plugins. I.e. I meant it to be part of the following files.
Since we declare the npm package names using the npmDependencies field, we could use this to extract the engines.node. Some frameworks like Nuxt are missing the engines.node field, so this would require for them to add that field in their package.json (which might be best practice).

Doesn't npm already prints a warning when you npm install a package that requires a Node.js version that doesn't match the one used? I believe yarn install fails when the version doesn't match (same behavior as npm install --engine-strict).
What is the additional gain in implementing the logic ourselves? The benefit I can see is during site creation so we can recommend users which Node.js version to use. However this might be better solved by always using Node.js LTS as the default Node.js version.

As I understand it, we'd do it so we can automatically switch to a supported version. This is why we'd want to know the supported version before running the install.

so we can automatically switch to a supported version

Thanks for clarifying @ascorbic. Will using Node.js LTS by default solve this? My suggestion only works if we are OK with assuming all frameworks support Node.js LTS (I think it's quite safe to assume it).
That way we won't have to maintain additional logic. If we do automatically chose a Node.js version based on the framework's engines field we would also need to communicate that to users property.

That sounds like the simplest solution. I can't think of a scenario where a new site wouldn't work with LTS, but if there were I think it would be rare enough to say that they could set it manually.

This is a reasonable approach @erezrokah :+1:
One potential gotcha is that some frameworks (like Nuxt) do not have an engines.node field. However, that field is best practice and I do not see a reason why a framework would legitimately not want to add it.

Using Node LTS by default sounds great. SvelteKit just dropped support for Node 12 and we're getting a number of complaints that deploys are failing on Netlify now. I sent a PR that I hope fixes this just for SvelteKit, but I'm not quite sure if it does: https://github.com/netlify/framework-info/pull/553. We do specify an engines.node in @sveltejs/kit's package.json already

@benmccann I made the same mistake, but unfortunately setting the env vars in framework-info doesn't work. With the change of the default build image to Focal, we are at least now defaulting to newer Node for builds. Unfortunately that doesn't apply to the lambda runtime, which still defaults to 12. We have an internal issue which covers this, but I think that right now we should default the lambda runtime to 14 (and hope that Amazon does a new release with 16 soon)

I've highlighted this again internally, as I think this is a growing problem. As well as SvelteKit it now affects Gatsby and in some cases Next.js.


Release to pypi github action

Problem
It would be sensible to add a CI/CD workflow action to release to TestPyPI and PyPI when appropriate to remove the risk of human error.
Solution
This uses the suggested approach to add a new job to the CI/CD pipeline.
This means all we have to do to release the package is to create new release via the Github web interface, and then the upload to PyPI is handled automatically.
Also, for every push to main, a package is uploaded to TestPyPI, so we can use this to verify that packages are sound.
This also switches to a versioning system using git tags (using setuptools_scm) so the version no longer has to be set manually, it is derived automatically from the git history.  If there is a git tag, then that is used, otherwise the tag is calculated as appropriate using the distance from the tag.  The default versioning system in setuptools_scm is not permitted by TestPyPI, therefore this has to be overridden to work correctly.
Note that appropriate API tokens need to be created (which I have done).
Additionally, have made the password in side the CI file into a Github secret (for best practice).
Acceptance Criteria
I have tested this using a branch to ensure that it the package gets created and uploaded to TestPyPI when a push occurs.  The packages are created as expected in TestPyPI.

Coverage remained the same at 98.063% when pulling 3a5b402a530bd2d9a548acb2aa0b280f344f2c90 on matthewhegarty:release-to-pypi-action into 1ef3252e13f1f3f6c36b58aeb6bc6ee67d440bd5 on django-import-export:main.

Note that this build failed whenever I pushed changes to my branch.  However, I tested by creating a branch directly within django-import-export, and when I pushed to that branch it built fine and published the packages to TestPyPI.  Note I had to include the name of the branch in the CI yml for this to work.
This test proves that it will publish to TestPyPI when building the main branch, however one issue is that it won't replace existing files in TestPyPI, so this could be an issue unless we increment the file version in dev (__init__.py) prior to each merge into main.

To fix this issue I had to modify setup.py.  I had to include the use of setuptools_scm.  This is a better way of managing versions, because it will create the correct version based on git tags.  Hence there is no manual intervention required to set the version in __init__.py correctly.
It will also update TestPyPI with a new version every time there is a build in main, and it will be created with a version number such as 2.6.2-dev8.  To get this to work, I had to add a simple function in setup.py to set the "local" version number correctly.

@manelclos sending another review your way... It looks like it's just the two of us working on this project at the moment so I hope you don't mind...

I've decided against merging this now.  Will stick with current deployment methods.


Equivalent to the MediaSessionConnector.setMediaMetadataProvider

ExoPlayer has MediaSessionConnector class with a method void setMediaMetadataProvider(@Nullable MediaMetadataProvider mediaMetadataProvider).
This is a good way to update metadata runtime in case of  live streaming, such as Radio Station streaming.
Moving to Media3, it is very hard to find it alternative.
The guidelines mention Remove the MediaSessionConnector and use the androidx.media3.session.MediaSession instead, but particular class has no API to update metadata runtime.
Can you please help to find alternatives on media3?
Appreciate in advance.

Following up on the above question the same story with setEnabledPlaybackActions() method of MediaSessionConnector. Could someone help with this ?

void setMediaMetadataProvider(@Nullable MediaMetadataProvider mediaMetadataProvider)

With Media3, you can call player.replaceMediaItem(..mediaItemWithUpdatedMetadata...) (or controller.replaceMediaItem) to do this. This only works well with the upcoming 1.2.0 release though as a result of the improvements for #33.  You should be able to upgrade to 1.2.0-alpha01 to test this out.

setEnabledPlaybackActions

This can be done with configuring the available commands for the controllers. See https://developer.android.com/guide/topics/media/session/mediasession#commands

void setMediaMetadataProvider(@nullable MediaMetadataProvider mediaMetadataProvider)

With Media3, you can call player.replaceMediaItem(..mediaItemWithUpdatedMetadata...) (or controller.replaceMediaItem) to do this. This only works well with the upcoming 1.2.0 release though as a result of the improvements for #33. You should be able to upgrade to 1.2.0-alpha01 to test this out.

I have just been testing this behaviour and it seems that the DefaultNotification only gets updated when using the ExoPlayer directly to replace the MediaItem. I want to make use of a Controller to update the MetaData. Any suggestions?


Adding support for imagePullSecrets

Fixes #124
Proposed Changes

Adds support for specifying imagePullSecrets for a private registry.
The secrets are specified in the same format they would be on a Deployment
The secret needs to be created in the knative-serving namespace in order to work

I attempted to minimize duplication in the tests by doing a small amount of refactoring as I was reusing examples.
Release Note

Add support for providing imagePullSecrets when using a private registry for the knative images.

/lgtm

/approve
/lgtm


CLKDIV support

Hey all,
I've spent the last few months learning more about fpgas/chip design and I have been playing with various tangnano devices again. I went from learning what PLL's actually are up to the point of looking at AXI and I spent some time playing with sky130. Anyway, I implemented a CLKDIV with a divisor of 5 in Verilog logic but it does not work with the HDMI outputs on the tangnano devices so I want to figure out support for the builtin CLKDIV.
I would love to help implementing this in apicula but still do not know how.
It seems that @yrabbit added CLKDIV to yosys builtins here https://github.com/YosysHQ/yosys/commit/a1dd794ff883286dcd71c73fc21a701402e1078a
Side Note: This is great because it now has a generator instead of manually created code.
Any hints or help would be greatly appreciated for this seemingly last missing piece for HDMI support.

Do you mean DVI? Because any implementation of HDMI without a license invites legal action. Almost a joke.
About the primitive: for CLKDIV it is a very heavy primitive, BSRAM is a child's walk in comparison. Because the input for it is HCLK - the same two wires that run along the sides of the chip.
But, since I don’t know your experience (what if you just need an evening to implement this thing?), the approximate plan of action is as follows:

learn to compare images with each other in order to isolate changing places;
find the fuses responsible for the division coefficient (it's easy);
find MUXes that connect the input of this primitive to HCLK (hard, since these MUXes are scattered throughout the chip);
find MUXs that connect the CLKDIV output to consumers (this can be simple if the consumer can be simple logic and may turn out to be hemorrhoids if the consumers are only IO).

And yes, it’s better to immediately forget about nextpnr-gowin: of course, you can do anything, but if something doesn’t work, then dealing with the non-himbaechel option... I’ll say for myself - there’s no point.

Do you mean DVI? Because any implementation of HDMI without a license invites legal action. Almost a joke.

For my use-case, I am happy with DVI-D to LVDS over the pins. This is for learning purposes.
By saying HDMI I am describing the port on the tangnano device which Sipeed describe as a HDMI connector.
I'll start with the first two steps before I even get to the latter ones.

learn to compare images with each other in order to isolate changing places

I'm not sure what you mean by this.
Does this mean the images of the fpga under a microscope of looking at the gates ?

find the fuses responsible for the division coefficient (it's easy);

I thought one could create some simple verilog examples of CLKDIV and change values to see how it behaves.
I presume that is this part ?

himbaechel

I see commits for this in the nextpnr repo it seems to be something about a newer api to the nextpnr framework for FPGAS with larger LUT counts. I don't know how much of this works atm.

learn to compare images with each other in order to isolate changing places

I'm not sure what you mean by this. Does this mean the images of the fpga under a microscope of looking at the gates ?

I meant to compare the images that you flash into the FPGA. To avoid repetition:
https://github.com/YosysHQ/apicula/issues/185

find the fuses responsible for the division coefficient (it's easy);

I thought one could create some simple verilog examples of CLKDIV and change values to see how it behaves. I presume that is this part ?

Almost. You already KNOW how it behaves, at least in theory, but the bits that make this piece of FPGA behave are unknown (and interesting).

himbaechel

I see commits for this in the nextpnr repo it seems to be something about a newer api to the nextpnr framework for FPGAS with larger LUT counts. I don't know how much of this works atm.

Look in the examples directory. In short, everything that works in legacy gowin works, plus attosoc works on Tangnano9k, Tangnano20k and TangPrimer20k.
https://github.com/YosysHQ/apicula/tree/master/examples/himbaechel

Do you mean DVI? Because any implementation of HDMI without a license invites legal action. Almost a joke.
About the primitive: for CLKDIV it is a very heavy primitive, BSRAM is a child's walk in comparison. Because the input for it is HCLK - the same two wires that run along the sides of the chip.
But, since I don’t know your experience (what if you just need an evening to implement this thing?), the approximate plan of action is as follows:
* learn to compare images with each other in order to isolate changing places;

* find the fuses responsible for the division coefficient (it's easy);

* find MUXes that connect the input of this primitive to HCLK (hard, since these MUXes are scattered throughout the chip);

* find MUXs that connect the CLKDIV output to consumers (this can be simple if the consumer can be simple logic and may turn out to be hemorrhoids if the consumers are only IO).

And yes, it’s better to immediately forget about nextpnr-gowin: of course, you can do anything, but if something doesn’t work, then dealing with the non-himbaechel option... I’ll say for myself - there’s no point.

Hello :)
I'm currently working on this.
I believe I've identified the fuses that configure the DIV_MODE, and I've confirmed that the output of CLK_DIV can be consumed by simple logic (the use case I have an interest in). All that to say that I've done the easy part, lol. Finding the muxes will be more tasking, and there's the extra complication that the output of CLK_DIV in one bank can be routed to other banks.
I have two questions, if you'll be kind enough to answer:

How much is currently known about HCLK itself?
Why do you expect that finding the muxes for CLK_DIV input will be hard, given that CLKDIV seems to be in the same rows/columns that the other IO tiles are on? If we already know how to use HCLK in other IO tiles, maybe this won't be so different :crossed_fingers:

Wow, that was fast! Congratulations.
In addition to what is written in the Gowin documentation, we have the locations of cells with HCLK MUXes for supported chips, as well as the ranges of cells served by each of the 4 HCLK outputs. If the signal from the CLKDIV output is supplied via HCLK, then there may not be any particular difficulties even with switching to another bank - this may have already been decided inside the MUX.
https://github.com/YosysHQ/apicula/blob/f43a0b7e423ea8c946ea18f11bd2d7529f776f4e/apycula/chipdb.py#L730
My assumptions about possible difficulties are probably related to memories of research on these same HCLKs - that the wire numbers coincide with the numbers of the watch spines, but are not connected to them, then that in 9C some HCLK wires have different numbers, but in fact one wire , then in some IO cells the CLK2 wire is actually HCLK - there was a lot of fun there.
But it’s possible that you won’t have to deal with this anymore.

Great job!
Let's start from the end: minimum cover for wires is a cool thing that I dreamed of :) Considering the nature of the application, I vote for the slow option - it’s still faster than what I’m looking for with my eyes, but subconsciously I won’t trust the “approximate” ;)
Regarding the “negative” wires and their fuse, there are many mysterious places in the Gowin IDE tables and this is one of them.
I'm reading lines like "if a given source is connected to a given sink, then the following fuses must NOT be set."
If this is true, then in most cases there is no point in paying attention to the absence of these fuses - the only exception is a line for which there is no “positive pair” - this is a connection when all fuses are cleared, that is, roughly speaking, an empty chip, the default connection.

Thank you!
Haha. Yes, lots of weird stuff, like the alonenode table :). About the wires, the core reason why I think it'll be a good idea to report the negative wires is so that someone like me doesn't get confused in the future. Maybe we can add an argument to the function that determines if it considers the negative wires or not?
I agree with you that the exact solver is better in this case. It might also be a good idea for it to return the top-n solutions rather than just the best one. :thinking:
About 'logicinfo', I'd be grateful if you could kindly clarify as myy understanding of that table might be wrong.
Given that the following entries associated with DIVMODE are in 'shortval':
[15, 0, fuse1, -1, -1, -1 ... -1]
[16, 0, fuse1, -1, -1, -1 ... -1]
[17, 0, fuse1, -1, -1, -1 ... -1]
[18, 0, fuse1, -1, -1, -1 ... -1]
etc.

Is my task to find a 'logicinfo' table that has entries like
(x, 15)
(x, 16)
(x, 17)
(x, 18)

Well, now you remember that there is no point in paying attention to the “negative” wires except for one single one, so maybe it will be enough to just describe it in the documentation? ;)
If you need the "alonenode" table, then you're already doing those complex things so I can retire :)
Now about logicinfo. Its structure is described in the documentation (I think), but I’ll repeat it anyway. Now it is more convenient to work not with raw tables from a dat file, but from db.logicinfo.
We look at the rows of each table as follows:
row_number (attribute, value)

that is, your numbers 15, 16, 17, 18 in the shirtval table are line_number in logicinfo:
...
row 15 [attr_0, val_0]
row 16 [attr_0, val_1]
row 17 [attr_2, val_4]
row 18 [attr_3, val_0]
...

attr is the numeric code of the primitive parameter, val is the parameter value. val can be either the direct value of the parameter (if you write inst.SOME_PARAM=4 in verilog, then val is also 4), or a code (inst.SOME_OTHER_PARAM=DISABLE, then val = some_number)
Although there are few tables (25 or so), searching there by logical parameters is a very “creative” process, but if the parameter has several values, then the situation improves significantly. You're lucky: the DIV_MODE (?) parameter has several values, which means you just need to find those tables where lines 15-18 look like:
15: (x, val0)
16: (x, val1)
17: (x, val2)
18: (x, val3)

that is, where x is the same and val is different.

@Seyviour are you on our matrix channel? We're discussing plans for the coming year, in case you would like to be more actively involved.

Hello @pepijndevos. Yes, I'm on the chat. I'm following the conversation but I haven't had much to say so far.

Okay, then I'll add some updating the documentation to my todo list. parse_tile reporting some negative wires and not others was confusing to me, and someone that doesn't know what's going on might have a similar experience.
Haha. I'm leaving the "alonenode" table alone for now. Maybe that's what it means -- "Leave this table alone" :) :)
Thanks a lot for explaining the 'logicinfo' table.
If the row-numbers start from 0, then it seems "unknown_49" is the table:
These are lines 15 - 24. Lines 20-24 also match up with the fuses for the second HCLK on a side, so I'm pretty confident.
(14, 13),
 (14, 14),
 (14, 15),
 (14, 16),
 (15, 4),
 (16, 13),
 (16, 14),
 (16, 15),
 (16, 16),
 (17, 5)

Great!
Now that you have the logicinfo table number and attribute numbers, I would advise you to do... synthesis.
With a high probability, yosys understands the primitive itself and passes it through itself, but you will have to work with nextpnr.
It needs databases and you will generate the databases :)
You need to place Bels in the right cells. Candidates will be cells with a type that has a table of 45. There may be too many of them, then you will need to experiment and determine the fuses in which cells react to changes in the divisor - there, with a high probability, it will be possible to create Bels.


NextStrain -> Taxonium import

We would make a new file kind of like https://github.com/theosanderson/taxonium/blob/master/taxonium_web_client/src/utils/processNewick.js to read from NextStrain json files

We did it! e.g. https://github.com/theosanderson/taxonium/pull/318


[Android] React error when declaring a component as content

Hey guys! I'm having some trouble declaring a component at the content. This is the output I'm having:

This is my component code (DashboardComponent.js):
<View>
      <Text>Test</Text>
</View>

This is the way I'm declaring the component:
const SECTIONS = [
  {
    title: "Dashboard",
    content: <Dashboard />
  }
]

My package.json
   "react-native": "0.54.1",
    "react-native-collapsible": "^0.10.0",

If I remove the View, the component loads fine. The problem is that I need the View. Does this package supports nested views? Is there any workaround for it? Thanks!

You can control any logic of display in the renderContent prop. Here's an example using a component like your example above. https://snack.expo.io/SJW5eXxTG

It worked! Thank you very much :smile:


Descenders in H1 are sometimes cut off

The default theme specifies a line height of 1em for the h1 title, causing descenders on the last line in some fonts like Arial Black to get cut off.

Is this caused by the background-clip: text? It shouldn’t normally matter that the line-height: 1 doesn’t fit the descenders. Also, this isn’t the default theme; it’s simply the index page on the default template.

Not planning on fixing this.


How to set "bold" style to spinner title, but for popup items not bold (usual) style?

Try the below codes.
<com.skydoves.powerspinner.PowerSpinnerView
  android:layout_width="match_parent"
  android:layout_height="wrap_content"
  android:textStyle="bold"

@skydoves this will makes text in popup bold too. But I need only bold only for title, whan spinner is closed.

Ah, I understood.
There is the only way to implement it is by using a custom adapter now.
I will consider adding an attribute related to it.
Thanks!

Hi, @Pirokar
The new version 1.1.6 has been released.
If you use IconSpinnerAdapter, you can change each items' text style (Typeface).
  val text: CharSequence,
  val icon: Drawable? = null,
  @DrawableRes val iconRes: Int? = null,
  @Px val iconPadding: Int? = null,
  val iconGravity: Int = Gravity.START,
  val typeface: Int? = null,
  val gravity: Int? = null,
  val textSize: Float? = null,
  @ColorInt val textColor: Int? = null,

Thanks for your issue!


BUGFIX: properly set ID for device allocator

The umpire::resource::resource_to_device_id() method has logic to detect the device ID based on the name of the memory resource. However, if the calling code has set a particular GPU to the process, e.g., via calling cudaSetDevice() or hipSetDevice(), the default device allocator that Umpire provides may have the wrong device ID. Consequently, all memory allocations/operations would be directed to the wrong GPU on the system.
This commit fixes this issue by adding logic to query the CUDA or HIP runtime for the correct device ID to use if the caller has not encoded the device ID to the name of the memory resource.
Resolves #798 #799

Thanks @davidbeckingsale!


Make ./mill without any arguments point you towards --help, flesh out --help into a cheat sheet

Fixes https://github.com/com-lihaoyi/mill/issues/3547
I added the cheat sheet for task syntax and compacted the flag documentation so it all fits on one page in the default macbook pro 15" terminal half screen at the default font size, with some room to spare vertically and horizontally: ~55 characters tall and ~100 characters wide. Could always squeeze it more or less, and the choice of target size is arbitrary, but this should be both concise and information-dense while still giving newbies a lot of useful tips and pointers. Notably, having too much detail in any part of this blurb is a net negative: it needs to be maximally concise while still containing the most useful pieces of information. More detailed explanations and exposition can go to the doc-site, which I linked at the bottom of the cheat sheet
I also split the usageText into shortUsageText which is printed on ./mill, and long usage text which is printed on ./mill --help, with the short usage text pointing you at ./mill --help for more details:
lihaoyi mill$ ./mill
Mill Build Tool, version 0.12.0-RC2-13-921d96-DIRTY16b6c61b
usage: mill [options] [[target [target-options]] [+ [target ...]]]
Run `./mill --help` for more details

lihaoyi mill$ ./mill --help
Mill Build Tool, version 0.12.0-RC2-13-921d96-DIRTY16b6c61b
usage: mill [options] [[target [target-options]] [+ [target ...]]]

target cheat sheet:
  ./mill resolve _                 # see all top-level tasks and modules
  ./mill resolve __.compile        # see all `compile` tasks in any module (recursively)

  ./mill foo.bar.compile           # compile the module `foo.bar`

  ./mill foo.run --arg 1           # run the main method of the module `foo` and pass in `--arg 1`
  ./mill -i foo.console            # run the Scala console for the module `foo` (if it is a ScalaModule)

  ./mill foo.__.test               # run tests in module within `foo` (recursively)
  ./mill foo.test arg1 arg2        # run tests in the `foo` module passing in test arguments `arg1 arg2`
  ./mill foo.test + bar.test       # run tests in the `foo` module and `bar` module
  ./mill '{foo,bar,qux}.test'      # run tests in the `foo` module, `bar` module, and `qux` module

  ./mill foo.assembly              # generate an executable assembly of the module `foo`
  ./mill show foo.assembly         # print the output path of the assembly of module `foo`
  ./mill inspect foo.assembly      # show docs and metadata for the `assembly` task on module `foo`

  ./mill clean foo.assembly        # delete the output of `foo.assembly` to force re-evaluation
  ./mill clean                     # delete the output of the entire build to force force re-evaluation

  ./mill path foo.run foo.sources  # print the task chain showing how `foo.run` depends on `foo.sources`
  ./mill visualize __.compile      # show how the `compile` tasks in each module depend on one another

options:
  -D --define <k=v>    Define (or overwrite) a system property.
  --allow-positional   Allows command args to be passed positionally without `--arg` by default
  -b --bell            Ring the bell once if the run completes successfully, twice if it fails.
  --bsp                Enable BSP server mode.
  --color <bool>       Toggle colored output; by default enabled only if the console is interactive
  -d --debug           Show debug output on STDOUT
  --disable-callgraph  Disables fine-grained invalidation of tasks based on analyzing code changes.
                       If passed, you need to manually run `clean` yourself after build changes.
  --help               Print this help message and exit.
  -i --interactive     Run Mill in interactive mode, suitable for opening REPLs and taking user
                       input. This implies --no-server. Must be the first argument.
  --import <str>       Additional ivy dependencies to load into mill, e.g. plugins.
  -j --jobs <int>      The number of parallel threads. It can be an integer e.g. `5` meaning 5
                       threads, an expression e.g. `0.5C` meaning half as many threads as available
                       cores, or `C-2` meaning 2 threads less than the number of cores. `1` disables
                       parallelism and `0` (the default) uses 1 thread per core.
  -k --keep-going      Continue build, even after build failures.
  --meta-level <int>   Select a meta-level to run the given targets. Level 0 is the main project in
                       `build.mill`, level 1 the first meta-build in `mill-build/build.mill`, etc.
  --no-server          Run without a background server. Must be the first argument.
  -s --silent          Make ivy logs during script import resolution go silent instead of printing
  --ticker <bool>      Enable ticker log (e.g. short-lived prints of stages and progress bars).
  -v --version         Show mill version information and exit.
  -w --watch           Watch and re-run the given tasks when when their inputs change.
  target <str>...      The name or a pattern of the target(s) you want to build.

Please see the documentation at https://mill-build.org for more details

In the process I shortened the names and docs of a lot of the flags that were IMO overly verbose. Especially for more advanced features like --meta-level we can get away with a more terse explanation here since the docs go into much more detail
As we do not guarantee bincompat for the mill.runner package, so we do not need to add shims and forwarders as we evolve the case class MillCliConfig
Notably this default blurb does not include any information about the current build, and is very generic. I don't know what the best way of inferring which modules and tasks are "important" and which are not, and so for now I just punted on the issue and just try to show syntax and tasks that should be useful for any Mill build. For now still somewhat JVM specific with compile and assembly and test; if in the future we start having more non-JVM stuff built using Mill we can make further changes then

We should add the syntax guide from your sceenshot to mill --help in general.
Otherwise, this is a nice topic for bikeshedding, but I would prefer shorter two line error message saying there is no target and indicating that mill --help will reveal more information.

We should add the syntax guide from your screenshot to mill --help in general.
Otherwise, this is a nice topic for bikeshedding, but I would prefer shorter two line error message saying there is no target and indicating that mill --help will reveal more information.

A bit more motivation. The long error message might help beginners, but the long message might always get in the way now and then to the power user, when she fingered or pressed enter too fast. Needing to scroll back to focus on what the last action/output/command was.

I put back the enableTicker/disableTicker flags but marked them as hidden/deprecated. They still work, but they don't show up in the UI. I guess we can leave them there in perpetuity.
I also split the usageText into shortUsageText which is printed on ./mill, and long usage text which is printed on ./mill --help, with the short usage text pointing you at ./mill --help for more details:
lihaoyi mill$ ./mill
Mill Build Tool, version 0.12.0-RC2-13-921d96-DIRTY16b6c61b
usage: mill [options] [[target [target-options]] [+ [target ...]]]

Run `./mill --help` for more details
lihaoyi mill$ ./mill --help
Mill Build Tool, version 0.12.0-RC2-13-921d96-DIRTY16b6c61b
usage: mill [options] [[target [target-options]] [+ [target ...]]]

target cheat sheet:
./mill resolve _                 # see all top-level tasks and modules
./mill resolve __.compile        # see all `compile` tasks in any module (recursively)

./mill foo.bar.compile           # compile the module `foo.bar`

./mill foo.run --arg 1           # run the main method of the module `foo` and pass in `--arg 1`
./mill -i foo.console            # run the Scala console for the module `foo` (if it is a ScalaModule)

./mill foo.__.test               # run tests in module within `foo` (recursively)
./mill foo.test arg1 arg2        # run tests in the `foo` module passing in test arguments `arg1 arg2`
./mill foo.test + bar.test       # run tests in the `foo` module and `bar` module
./mill '{foo,bar,qux}.test'      # run tests in the `foo` module, `bar` module, and `qux` module

./mill foo.assembly              # generate an executable assembly of the module `foo`
./mill show foo.assembly         # print the output path of the assembly of module `foo`
./mill inspect foo.assembly      # show docs and metadata for the `assembly` task on module `foo`

./mill clean foo.assembly        # delete the output of `foo.assembly` to force re-evaluation
./mill clean                     # delete the output of the entire build to force force re-evaluation

./mill path foo.run foo.sources  # print the task chain showing how `foo.run` depends on `foo.sources`
./mill visualize __.compile      # show how the `compile` tasks in each module depend on one another

options:
  -D --define <k=v>    Define (or overwrite) a system property.
  --allow-positional   Allows command args to be passed positionally without `--arg` by default
  -b --bell            Ring the bell once if the run completes successfully, twice if it fails.
  --bsp                Enable BSP server mode.
  --color <bool>       Toggle colored output; by default enabled only if the console is interactive
  -d --debug           Show debug output on STDOUT
  --disable-callgraph  Disables fine-grained invalidation of tasks based on analyzing code changes.
                       If passed, you need to manually run `clean` yourself after build changes.
  --help               Print this help message and exit.
  -i --interactive     Run Mill in interactive mode, suitable for opening REPLs and taking user
                       input. This implies --no-server. Must be the first argument.
  --import <str>       Additional ivy dependencies to load into mill, e.g. plugins.
  -j --jobs <int>      The number of parallel threads. It can be an integer e.g. `5` meaning 5
                       threads, an expression e.g. `0.5C` meaning half as many threads as available
                       cores, or `C-2` meaning 2 threads less than the number of cores. `1` disables
                       parallelism and `0` (the default) uses 1 thread per core.
  -k --keep-going      Continue build, even after build failures.
  --meta-level <int>   Select a meta-level to run the given targets. Level 0 is the main project in
                       `build.mill`, level 1 the first meta-build in `mill-build/build.mill`, etc.
  --no-server          Run without a background server. Must be the first argument.
  -s --silent          Make ivy logs during script import resolution go silent instead of printing
  --ticker <bool>      Enable ticker log (e.g. short-lived prints of stages and progress bars).
  -v --version         Show mill version information and exit.
  -w --watch           Watch and re-run the given tasks when when their inputs change.
  target <str>...      The name or a pattern of the target(s) you want to build.

Please see the documentation at https://mill-build.org for more details

usage: mill [options] [[target [target-options]] [+ [target ...]]]

I think this synopsis isn't correct. The first target isn't optional, except when running with --version or --help.

usage: mill [options] [[target [target-options]] [+ [target ...]]]

I think this synopsis isn't correct. The first target isn't optional, except when running with --version or --help.

Updated it to
usage: mill [options] target [target-options] [+ target ...]

So the first target is necessary, the target-options is optional ,and the + target ... is also optional

lihaoyi mill$ ./mill
> ./mill
Mill Build Tool, version 0.12.0-RC2-13-921d96-DIRTY16b6c61b
usage: mill [options] [target [target-options] [+ [target ...]]]
Run `./mill --help` for more details

We now just say, look at the help, without telling what the problem is, although we know the problem, a missing target.
Should be:
 Mill Build Tool, version 0.12.0-RC2-13-921d96-DIRTY16b6c61b
+ A target is missing.
+
-usage: mill [options] [target [target-options] [+ [target ...]]]
+Usage: mill [options] [target [target-options] [+ [target ...]]]
 Run `./mill --help` for more details

Also removed all the leading ./ since those don't really convey any meaning and add a lot of visual noise to the cheatsheet


Index page text derivative, if one exists

Index text of a NewspaperPage to a dynamic Solr index named full_text_tesi — if the text is available as a derivative file with a .txt extension, read that file and index its contents.
The primary use for this is the indexing of OCR-extracted text, or any text saved for page on any other type of ingest.
Scope

Indexing is limited to NewspaperPage and any more elaborate indexing of parent NewspaperIssue for text is out of the scope at the moment (esp. until we figure out how we want to manage the UX for search re: transitive relationships).

Fixed via #50.


ios or android file cannot be recreated (dont work react-native eject)

🐛 Bug Report
i using v0.59.0-rc.3.
I get the following error when I run the react-native eject command when I want to delete and re-create the iOS or Android file.

It looks like this is an issue related to the CLI - please open an issue in the dedicated https://github.com/react-native-community/react-native-cli/issues and create a series of steps to reproduce the issue, or even better provide a repro.


fixed a tiny typo

Coverage remained the same at 100.0% when pulling 6aad67af2397000c05214e6e605118de732443de on thelostt:patch-1 into 0767290c2605cb238865260da261c7d294b83edd on nlohmann:develop.

Thanks a lot!


How to add new currency

Hello . since am new in peatio i really will appreciate to guide me on hot to add new currency and exchange in peatio .
For example i want to add GalaxyCash . can you please guide me from the start till the end .
thanks a lot .

please contact with me.
this is my fork
https://github.com/Apollo-IT/peatio

https://peatio.io/


wrong required type: Changed String -> int

Good call! Fixed in https://github.com/udacity/ud851-Exercises/commit/055629c9ef62a8152ad53da6db6327b67257f2eb
Pull requests don't really work in this repo because of some secret sauce we're using to generate the steps.


[Package] Fix Limit API. Fix go vet complaints.

The NewLimit API has wrong implementation and is not idiomatic in Go, this commit brings a simple impl.
Fix some go vet complaints.

Updated.


OMIM alignment - January 2024

Addresses #7211
(1st commit includes removal of some omim x-ref)

@nicolevasilevsky, this PR is ready for review. There were many QC to address, but I got almost all of them.
I am still having a QC issue: FAIL Rule ../sparql/qc/mondo/qc-omimps-should-be-inherited.sparql: 16 violation(s)
I understand the error that is reported: terms with OMIMPS equivalent that do not have a "has_characteristic some inherited" axiom
BUT: the terms reported as errors DO HAVE these axioms from their parents.
Should these axioms be asserted instead of inferred? Is that the problem? (tagging @matentzn too).
Thanks!

You can try to update the SPARQL query
FILTER NOT EXISTS {
    ?entity rdfs:subClassOf* [ rdf:type owl:Restriction ;
    owl:onProperty <http://purl.obolibrary.org/obo/RO_0000053> ;
    owl:someValuesFrom <http://purl.obolibrary.org/obo/MONDO_0021152> ] .
  }

By adding that rdfs:subClassOf* * expression and see if it works - not sure how SPARQL fares with subclass of anonymous expressions.
Generally, there is a lot of redundancy in mondo-edit.obo, and there is no problem with that. During the release, the redundant axioms will be removed again. So either way is fine: changing the qc, and adding the assertion everywhere!


WIP Add label and description text fields to each WIT field.

NOTE: This PR is written against my PR branch that isn't in master yet.
Fixes https://github.com/almighty/almighty-core/issues/848

@hectorj2f thank you


License of this repository and model

What is the license of this repository and model?

MIT License

Can you please add a license to make it more explicit? Thank you.

done@weisrc

@weisrc done


Fix nested resources creating N+1 queries on includes

Added include_directives support to resource relationships to avoid N+1 queries from includes on a nested route.
I had a route of /resource1/:id/resource2?include=resource3 and noticed it was creating N+1 queries for each resource3 access.
I've patched JSONAPI::RelationshipBuilder.build_to_many to follow the same logic JSONAPI::Resource.find

@mgoodings Thanks!


Tabula API version: <IP_ADDRESS>92117 - Internal Server Error (500)

In the attached pdf you'll find two types of table, a wider one and a taller one. Selecting either or both tables of the same type produce the expected results but the following error appears when selecting both types of table at the same time.
Amazonas.pdf
Tabula API version: <IP_ADDRESS>92117

Filename: Amazonas.pdf
Internal Server Error (500)

        Request Method:
        POST

        Request URL:
        http://<IP_ADDRESS>:8080/pdf/76a93f5d522062829219ecd8615b8092d1622c88/data

@joevector: please try the newest version of Tabula. I think this error has been fixed (or at least, I can't replicate it now)


Ensure DDS sets correct roles for access control

DDS no longer acts as broker/bridge, but still knows DLCS Role URIs
It needs to map METS access conditions to these URIs
DLCS takes care of mapping Auth0 claims to these URIs.
Slack discussion
https://digirati.slack.com/archives/CBT40CMKQ/p1648716914566629

DDS is reading access conditions from Premis and mapping them to DLCS role URLs for asset registration. No new access conditions are expected in the near future.


Silent warnings

See original issue on GitLab
In GitLab by [Gitlab user @Qinusty] on Aug 21, 2018, 15:17
Background
Add project configuration silent-warnings to silence warnings which are configurable.
Task description

[ ]  Add project configuration item
[ ]  Validate no overlap between fatal and silent warnings

silent-warnings:
- overlaps

Acceptance Criteria
Configurable warnings can be silenced on a project by project basis.

In GitLab by [Gitlab user @Qinusty] on Aug 21, 2018, 15:22
changed the description

In GitLab by [Gitlab user @tristanvb] on Aug 22, 2018, 11:46
Was this feature proposed anywhere ?
Is it just an assumption that since we have fatal warnings, we must want to silence them also ?
I don't think I agree with this feature, for instance; the overlap warnings have an explicit feature for whitelisting specific files such that they are not considered overlaps; a blanket statement to silence this warning would not necessarily be a good thing.

In GitLab by [Gitlab user @Qinusty] on Aug 22, 2018, 14:02
No proposal has been done formally for this, it was created out of a thought during !700, in which two CoreWarnings were added. I can imagine that we may want to produce some warnings which certain projects may choose to silence.
E.g. A warning suggesting that aliases are used throughout projects.
This feature not desired but just a thought in the back of my head during other work.

In GitLab by [Gitlab user @tristanvb] on Nov 4, 2020, 09:56
Let's close this.


RFM - inter

I DON'T Want To Become The Maintainer

[x] I have followed the Package Triage Process and I do NOT want to become maintainer of the package;
[x] There is no existing open maintainer request for this package;

Checklist

[x] Issue title starts with 'RFM - '

Existing Package Details
Package URL: https://community.chocolatey.org/packages/inter
Package source URL: (there appears to be no packageSourceUrl defined).
Date the maintainer was contacted (in YYYY-MM-DD): 2023-11-12
How the maintainer was contacted: Contact Maintainers form from Package URL

I will pick this up.

I'm ready to submit the updated package to the repo, but I need to be assigned maintainer status.

Added @teknowledgist as a maintainer in response to request via Site Admins

This is (long) submitted and approved by moderators and can be closed.


Use branch "real_coord" of SymPDE

This PR is linked to https://github.com/pyccel/sympde/pull/170 .
After the change that coordinates must be real, the symbols used in the tests to write the exact solution must also be declared as real.


MINOR: Fix setCameraGeolocationAndZoom.

fix method.

Codecov Report

Merging #992 into master will decrease coverage by 0.05%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #992      +/-   ##
==========================================
- Coverage   48.21%   48.16%   -0.06%
==========================================
  Files         242      231      -11
  Lines       21932    21731     -201
  Branches     4986     4957      -29
==========================================
- Hits        10574    10466     -108
+ Misses      11358    11265      -93

Impacted Files
Coverage Δ

@here/harp-mapview/lib/Utils.ts
59.6% <ø> (-0.11%)
:arrow_down:

@here/harp-mapview/lib/ThemeHelpers.ts
6.55% <0%> (-0.68%)
:arrow_down:

@here/harp-datasource-protocol/lib/Outliner.ts
100% <0%> (ø)
:arrow_up:

...ere/harp-materials/lib/LuminosityHighPassShader.ts
100% <0%> (ø)
:arrow_up:

...p-geoutils/lib/tiling/QuadTreeSubdivisionScheme.ts
100% <0%> (ø)
:arrow_up:

@here/harp-utils/lib/Mixins.ts
70% <0%> (ø)
:arrow_up:

@here/harp-materials/lib/CopyMaterial.ts
100% <0%> (ø)
:arrow_up:

...e/harp-geoutils/lib/tiling/MercatorTilingScheme.ts
100% <0%> (ø)
:arrow_up:

@here/harp-omv-datasource/lib/OmvTile.ts
50% <0%> (ø)
:arrow_up:

...ere/harp-geoutils/lib/projection/EarthConstants.ts
100% <0%> (ø)
:arrow_up:

... and 26 more

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 303a9ec...8ab9bbe. Read the comment docs.


Blockfrost exploration

Here's how blockfrost API endpoints map to our needs:
ctl-server
apply-args - not supported, we will implement it eventually on frontend
eval-ex-units - /utils/txs/evaluate
finalize - not needed (will be dropped eventually)
ogmios

utxo - /addresses/:address/utxos
getProtocolParameters - /epochs/:number/parameters
systemStart - /genesis
currentEpoch - /epochs/latest

Example response:
{
    "epoch": 210,
    "start_time":<PHONE_NUMBER>,
    "end_time":<PHONE_NUMBER>,
    "first_block_time":<PHONE_NUMBER>,
    "last_block_time":<PHONE_NUMBER>,
    "block_count": 2002,
    "tx_count": 8121,
    "output": "56485150782946429",
    "fees": "2913192162",
    "active_stake": "15044495200974246"
}

eraSummaries - not supported

We use it in  in Types.Interval  for slotToPosixTime and posixTimeToSlot (the latter is used inScriptLookups to implement MustValidateIn posixTimeRange constraint).
In both functions, EraSummary is only used to find current era based on current time. CurrentEra is passed to relTimeFromAbsTime, relSlotFromRelTime and absSlotFromRelSlot.
EraSummary is defined as
  { start :: EraSummaryTime
  , end :: Maybe EraSummaryTime
  , parameters ::
    { epochLength :: EpochLength -- 0-18446744073709552000 An epoch number or length.
    , slotLength :: SlotLength -- <=<PHONE_NUMBER>3709552000 A slot length, in seconds.
    , safeZone :: SafeZone  } -- 0-18446744073709552000 Number of slots from the tip of

We can get start and end from /epochs/* endpoints.
From parameters record, we only use slotLength, which seemingly can be acquired from /genesis.
Thus our use-case in its current form can be re-implemented with blockfrost instead of ogmios.

chainTip - /blocks/latest

Example response:
{
    "time":<PHONE_NUMBER>,
    "height": 3617406,
    "hash": "247b93ef3bbcdfeabdc8fd0ea1bae21d636f56246ebce0b9364e0f22fdda0e77",
    "slot": 60416711,
    "epoch": 210,
    "epoch_slot": 66311,
    "slot_leader": "pool18yslg3q320jex6gsmetukxvzm7a20qd90wsll9anlkrfua38flr",
    "size": 3543,
    "tx_count": 7,
    "output": "84480521968151",
    "fees": "1253244",
    "block_vrf": "vrf_vk1sleujze3zraykllkafvrxggcmpts3hp6zxrpazdkdzp9g07kkehsnmy8ka",
    "previous_block": "c519d70c1d08a9645648fb3cb36b218496b6c3dc342552f57e7c487a10320122",
    "next_block": null,
    "confirmations": 0
}

submitTx - /tx/submit
evaluateTx - /utils/txs/evaluate

ogmios-datum-cache

GetDatumByHash - scripts/datum/:datum_hash
GetDatumsByHashes - not supported, but it's just a batched version of the above

Blockfrost can help with getting number of confirmations for transaction:

get Tx block ID by Tx ID
get number of block confirmations by block ID

This ended up being on Catalyst: https://cardano.ideascale.com/c/idea/420791/

Note: this list is going to be expanded with staking-related endpoints when we merge #1135
TODO: find if/how we can use blockfrost for that.

@jy14898 how do you know it's using Ogmios?

@klntsky https://docs.blockfrost.io/#tag/Cardano-Utilities/paths/~1utils~1txs~1evaluate/post The response mentions its the same as Ogmios, which to me means with almost certainty they're using ogmios to handle that endpoint

Closing. We will be ready to merge #1260 soon


Do not instantiate load balance if there is no invokers (#1297)

Currently, we'll instantiate the load balance with a default instance if no invokers found. However, we don't need to use it.
Closes #1297

Codecov Report

Merging #1376 into master will decrease coverage by 0.17%.
The diff coverage is 50%.

@@            Coverage Diff            @@
##           master   #1376      +/-   ##
=========================================
- Coverage   32.57%   32.4%   -0.18%
=========================================
  Files         691     691
  Lines       34537   34537
  Branches     6812    6812
=========================================
- Hits        11252   11192      -60
- Misses      21357   21412      +55
- Partials     1928    1933       +5

Impacted Files
Coverage Δ

...bo/rpc/cluster/support/AbstractClusterInvoker.java
68.62% <50%> (ø)
:arrow_up:

...bo/rpc/cluster/support/FailbackClusterInvoker.java
71.79% <0%> (-12.83%)
:arrow_down:

...mon/serialize/support/dubbo/GenericDataOutput.java
65.61% <0%> (-9.83%)
:arrow_down:

...baba/dubbo/rpc/protocol/dubbo/DubboCountCodec.java
84.37% <0%> (-6.25%)
:arrow_down:

...mmon/serialize/support/dubbo/GenericDataInput.java
58.3% <0%> (-5.41%)
:arrow_down:

...a/dubbo/remoting/transport/netty/NettyChannel.java
61.25% <0%> (-5%)
:arrow_down:

.../com/alibaba/dubbo/monitor/dubbo/DubboMonitor.java
73.14% <0%> (-2.78%)
:arrow_down:

.../dubbo/rpc/protocol/dubbo/filter/FutureFilter.java
54.54% <0%> (-2.03%)
:arrow_down:

...bo/remoting/transport/netty/NettyCodecAdapter.java
55.22% <0%> (-1.5%)
:arrow_down:

...baba/dubbo/remoting/transport/mina/MinaClient.java
57.97% <0%> (-1.45%)
:arrow_down:

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 2c20d99...b185422. Read the comment docs.


Picking up on an event

I am using EZTime together with a DS3231 RTC so that the clock will operate correctly even if there is no network connection. For instances where a network connection is available is there any way to pick up on the event that occurs when an NTP update completes so I can use the new time setting to correct the RTC if necessary.
I currently have the RTC periodically updating the local clock but would like to correct the RTC  if a new time is received from the NTP. Using the DEBUG setting I can see the messages
Querying pool.ntp.org ... success (round trip 46 ms)
Received time: Friday, 02-Nov-18 20:32:29.319 UTC (internal clock was 1237 ms fast)
from the DEBUG but I am not sure how to pick up on the events completion.
Hardware is an ESP WROOM 32 module on a custom PCB with DS3231 chip, using the rtc_by_manuka library for the DS3231.

I guess you could turn off NTP updates with setInterval(0) and then from your own event call queryNTP (which doesn't actually set the time) and then setTime and whatever else you want to do. How about something like this. (Untested...)
[...]

void setup() {
    [...]
    setInterval(0);
    timeSyncEvent();
}

void timeSyncEvent() {
    time_t t;
    unsigned long measured_at;
    if (queryNTP("pool.ntp.org", t, measured_at)) {
        setTime(t, millis() - measured_at);
    }

    // Insert whatever you want to with the received time here

    // run again in an hour
    UTC.setEvent(timeSyncEvent, now() + 3600;
}

I do plan for some future version to make the time updates such that time only goes forward (monotonous time) and corrections are done by adding or subtracting a few milliseconds here or there.
I'll also think about how to support RTC clocks, GPS receivers and the like.

Thanks for the ideas, excellent software library.


switch to org.wildfly package

It should be even more separate, so org.wildfly.betavia. and whatever under it.
You need to make sure that same package name doesn't come from any other wildfly related project. otherwise there will be issues with jigsaw...

Very good point @ctomc , thanks!
I propose org.wildfly.transformer.asm package @scottmarlow
for asm based transformer considering jigsaw limitations.

Thanks @ctomc!  Good point.
Moved to org.wildfly.transformer.asm for now.


Coming soon component

Task Description
We should have a coming soon component to display where there is a feature that we want to show on the UI and will come in the next couple of releases.
Technical Considerations
Additional Considerations

Resolved in https://github.com/Kerosz/biolnk/commit/bc3354796f40fc36d2936292d10854c6228ef932


Potential savings in attributes transpilation

Is there any reason why empty attributes
 are getting transpiled into empty=""? As I understand by default HTML understands empty as "" value. Getting rid of ="" could reduce the build size while still persisting the same effect.
https://github.com/ryansolid/dom-expressions/blob/62bd00e61c2cf217cae818be21ace06a32c8dfd0/packages/babel-plugin-jsx-dom-expressions/src/dom/element.js#L528
- results.template += value ? `="${value.value}"` : `=""`;
+ results.template += value ? `="${value.value}"` : "";

I also noticed another case that could prevent generating more templates.
In many cases the templates differs only by attributes.
    <>

          Hello
          !

          Hello
          !

    </>

Currently this syntax would generate 2 the same templates with just a different attribute value:
const _tmpl$ = template(`<div><div class="bang">Hello<span>!</span></div></div>`, 6),
      _tmpl$2 = template(`<div><div class="h1">Hello<span>!</span></div></div>`, 6);

We could optimize it by treating attributes always as dynamic:
setAttribute(_el$2, "my-attr", "value");

That why we could reduce build size drastically reducing the amount of templates.
I am aware that currently this can be achieved by wrapping each attr with template literals but this is inconvenient for DX

We use innerHTML to generate template elements and sometimes it corrects bad HTML my previous mechanism was to string equal the template vs the result in the innerHTML in dev mode. The browser adds the ="" so I had done that to match. Now I just count the number of tags which is less precise but means that probably doesn't matter to do anymore.
I've always optimized for runtime speed over size, even if negligible. I wonder how much we get back from gzip anyway which should be able to reduce duplication in the template strings pretty handedly. While calling helpers definitely can be reduced more by the minifier I think it would depend a lot on the type of templates you are using.

Thanks Ryan for your answers! :)

The browser adds the ="" so I had done that to match.
Hmm, when I set empty string attribute on the element using pure browser API, it does not add ="". Did I miss some something?

I've always optimized for runtime speed over size, even if negligible. I wonder how much we get back from gzip anyway which should be able to reduce duplication in the template strings pretty handedly. While calling helpers definitely can be reduced more by the minifier I think it would depend a lot on the type of templates you are using.

I think in bigger apps, with a lot of templates this make a huge difference in delivery. Do you have an access to some mature Solid app, or some OSS project? We could do some benchmarking to validate :)

Hmm, when I set empty string attribute on the element using pure browser API, it does not add ="". Did I miss some something?
Yes try setting the boolean attribute in an innerHTML and then look what is generated. Like create template with just the boolean property naked. The HTML it generates will have the ="" or at least it did in every browser I checked about 2 years ago.

Yeah I don't have anything of that size to make a comparisn. But I do know that cloning is faster than separately setting from microbenchmarks.

That's correct. The inner html as text will contain the ="" however the nodes will not have it.

Setting innerHTML as '

' is exactly the same as '

'
I think this could save some size without any side effect. It's still a valid HTML to pass just the attribute without assignment so browsers will interpret it anyway as ="". I guess it's like const test = undefined vs const test. Implicit value assignment.

But I do know that cloning is faster than separately setting from microbenchmarks.

That's true. Im just wondering about the impact the duplicated templates will have on the bundled size. I know that is some apps the templates can be like 80% of the size with very complex structure. It might be the case that the cost of setting attributes can be justified in order to trim the bundle by eg. 50%.
There is also one more option instead of using setAttribute we could interpolate the template with attributes to create the final template. I think that would lead to template compilation where structure is shared and all static data is precompiled- not sure what do you think about that.

An example of how we could use template literals for that:
function template(strings, ...keys) {
  return (function(...values) {
    let dict = values[values.length - 1] || {};
    let result = [strings[0]];
    keys.forEach(function(key, i) {
      let value = Number.isInteger(key) ? values[key] : dict[key];
      result.push(value, strings[i + 1]);
    });
    return result.join('');
  });
}

const genericTemplate = template`<button ${0}><div>${1}</div><span></span></button>`

const html = genericTemplate('my-attr="value"', 'Hello there!')

Yeah for the ="" as I was saying it was mostly because I needed the string comparison to be equal. Now that I don't that's probably an easy reduction. So I see no issue with us removing that.
The template thing is trickier. I looked at stuff like bytecodes etc doing my own encoding and I wasn't happy with the performance. And mostly that I needed to bring in the code to do it which was larger than the gains I was shaving from the template. Strings really have the benefit of being easily Gzippable. And I felt all I was doing was implementing my own compression algorithm.
I think there are some heuristics that make sense. Like if templates are sufficiently small like a single element we probably could look at using document.createElement and attribute helpers assuming that those helpers would be there anyway and wouldn't add more code size. Right now template sharing would only be applicable within the same file. And I don't see it applying to partials but whole sections. Like if the initial example here is in a div instead of fragment no gain. But it also seems complicated for a scenario that I'm not sure how often you'd hit or would get reasonably handled by GZip. I'm not saying I can't picture this scenario but I suspect the wins aren't clear cut.

I've removed the ="" from 0.29.15.

Seems like this issue can be closed

Well I only ever did half of the suggestion and the OP was going to investigate the other half. But I agree this one is stale.


sp-os-wg co-chair nomination

Hi, I'm @mauromorales, I was nominated as co-chair for the Special-Purpose Operating System Working Group, here's the announcement from the latest TAG Runtime update during Kubecon SLC https://youtu.be/pF2r6VfTXPU?si=v8mkK7h8vlj_zcB3&t=1374
Thank you so much for the consideration to being part of this group and this wonderful community. Looking forward to keeping working together to make it even better :)
Short bio: I was born and raised in Guatemala, but currently living in Ghent, Belgium. I'm one of the maintainers of Kairos https://github.com/kairos-io/kairos a SPOS for running kubernetes at the edge. In the last years, I rediscovered my passion for running, which is why I think I should be part of the TAG Runtime 🥁 (working on my dad jokes)
There's already a PR for the changes here https://github.com/cncf/tag-runtime/pull/194, but it was reverted here https://github.com/cncf/tag-runtime/pull/197 since this issue was missing for the process to be complete. Please let me know if we can re-revert or if I should re-open the original PR.

Sorry for the delay and missing this part of the process originally. @miao0miao and I are the current co-chairs of the Special Purpose OS working group. We had spoken to Mauro at KubeCon US 2024 in SLC asking if he would be interested in joining us as a co-chair. Mauro has been very active in the group and has helped drive discussions and community activities such as panel discussions about SPOS at events.
So this is my +1 to adding Mauro as a co-chair to the group. Thanks for all you've been doing to keep things going.

Hi @sfc-gh-raravena @srust @raravena80 @angellk, could you take a look at this issue? It was requested during https://github.com/cncf/tag-runtime/pull/194 Thanks 🙏 !

I met Mauro in SLC and talked with Danielle and Sean at the time as well and approve of this nomination.

+1 for the nomination!

+1 for the nomination!

@angellk, @dims, @cathyhongzhang can we get a +1 here?  Thx.