fix: add custom property fallbacks for IE11

Alaska Airlines Pull Request
Summary:
The component was not importing the custom property fallbacks needed for IE11. This caused the SVGs to appear way too large.
This also updates the tests to use a stubbed fetch so that we are not reliant on unpkg for tests to succeed.
Before:

After:

Type of change:
Please delete options that are not relevant.

[x] Revision of an existing capability

Checklist:

[x] My update follows the CONTRIBUTING guidelines of this project
[x] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.
Thank you for your submission!
-- Auro Design System Team

On a side note, how was this missed for the V1 release? Was IE11 not tested?

Also, the component tests seem very flaky. Sometimes they pass locally and sometimes they don't (especially when running pre-commit).

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


update Vulkan sample with external memory and semaphore sharing

Updates the Vulkan sample to use external memory sharing and external semaphore sharing, when supported.
On one of my systems, this improves the performance from:

host cop, host sync: 1100 fps
external memory sharing, host sync: 3400 fps
external memory, external semaphore sharing: 4400 fps

Note: be sure to use the latest drivers!
Note: still need to test Linux (but it should work in theory).

Hmm, well, Linux still isn't quite working.  I can get an image with host synchronization, but it is corrupted.  I'll eitner need newer drivers, or I'll need to figure out what I am doing wrong.

Linux appears to be working now - excellent!  I plan to merge this shortly.


Add "Application Runtime" as a valid category

This category could be used for operators managing application runtimes
such as applications servers or some application frameworks.

/cc @anik120 @galletti94 @dmesser

@galletti94 it seems this category is not present yet on operatorhub.io.
What are the steps to make it available (so that I can update the WildFly Operator to reference this category)?


cmd/cue: vet behaves inconsistently with disjunction

What version of CUE are you using (cue version)?

$ cue version
cue version +ecb17c94 linux/amd64

Does this issue reproduce with the latest release?
Yes
What did you do?
# vet a.json using #A
exec cue vet x.cue justa.cue a.json

# vet b.json using #B
exec cue vet x.cue justb.cue b.json

# Ensure a.json does not vet with #B
! exec cue vet x.cue justb.cue a.json

# Ensure b.json does not vet with #A
! exec cue vet x.cue justa.cue b.json

# vet a.json using #A | #B
exec cue vet x.cue both.cue a.json

# vet b.json using #A | #B
exec cue vet x.cue both.cue b.json

-- a.json --
{
	"a": "test"
}
-- b.json --
{
	"b": 42
}
-- both.cue --
package x

#A | #B
-- justa.cue --
package x

#A
-- justb.cue --
package x

#B
-- x.cue --
package x

#A: {a: string}
#B: {b: int}

What did you expect to see?
The test to pass.
What did you see instead?
# vet a.json using #A (0.028s)
> exec cue vet x.cue justa.cue a.json
# vet b.json using #B (0.029s)
> exec cue vet x.cue justb.cue b.json
# Ensure a.json does not vet with #B (0.030s)
> ! exec cue vet x.cue justb.cue a.json
[stderr]
field not allowed: a:
    ./a.json:2:2
    ./justb.cue:1:1
    ./justb.cue:3:1
    ./x.cue:1:1
    ./x.cue:4:5
[exit status 1]
# Ensure b.json does not vet with #A (0.028s)
> ! exec cue vet x.cue justa.cue b.json
[stderr]
field not allowed: b:
    ./b.json:2:2
    ./justa.cue:1:1
    ./justa.cue:3:1
    ./x.cue:1:1
    ./x.cue:3:5
[exit status 1]
# vet a.json using #A | #B (0.029s)
> exec cue vet x.cue both.cue a.json
[stderr]
field not allowed: a
[exit status 1]
FAIL: /tmp/testscript469010135/repro.txt/script.txt:14: unexpected command failure
error running repro.txt in /tmp/testscript469010135/repro.txt

Which demonstrates two problems:

cue vet x.cue both.cue a.json failed when it should not have done (for completeness' sake, cue vet x.cue both.cue b.json does work as expected)
cue vet x.cue both.cue a.json elides all the details from the error message (although this is something of a moot point because this command should not error)

I happened to run into this same issue (I believe) using
$ cue version
cue version 0.4.0 linux/amd64

$ ########

$ cat a.cue
#Test: { a: int } | { b : string }

test : #Test & { a: 3 }

$ cue export --out json -e test a.cue | tee a.json
{
    "a": 3
}

$ cue vet a.json a.cue -d '#Test'
#Test: field not allowed: a

$ ########

$ cat b.cue
#Test: { a: int }

test : #Test & { a: 3 }

$ cue export --out json -e test b.cue | tee b.json
{
    "a": 3
}

$ cue vet b.json b.cue -d '#Test'

$ # OK exit status

My work-around for now is something along the lines of
$ jq '{v:.}' a.json > vettable-a.json ; cue vet vettable-a.json a.cue -d '{v: #Test}'

Thanks @rycee, especially for the repro (FYI in case you are looking to provide multi-file reproducers, this wiki provides some tips). Looks like this isn't limited to embedded disjunctions, a plain disjunction is sufficient.

@mpvl @myitcv I've most likely found a bug concerning disjunctions and @myitcv kindly referred me to this issue.
You can see the details at #1512 . I am not sure if the symptoms fit entirely, to be honest.
Can I do something to else fix this?
Thanks in advance

Just to be clear, that has not been merged yet, but will likely be very soon assuming no further issues come up.

Thanks @myitcv I've tested out the patched code and it seems to work with the examples mentioned above. I'll wait for the merge and the release. :wave:


Link scores

Special mode should be possible to invoke by checkbox or something like that.
In this mode, every link in the list should have 3 buttons:

+ increases link's score
- decreases link's score
0 resets link's score to zero

By default, any link has score zero. Score is useful for prioritizing links.
Related feature: https://github.com/ARK-Builders/ARK-Shelf-Desktop/issues/7

Implemented in #11


Added channels to the index, added channel filtering, cleaned doc

This PR adds channels into the index, this combined with the added channel filtering parameter allows us to search specific channels for content.
While adding the code for filtering I split the search query into individual parts so it easier can be edited and read.
The documentation has been changed to swagger, which now means we follow the OpenAPI spec.
We now use the swagger spec to generate API documentation with the help of the yarn run gendoc command, which gets the latest API documentation from in line and adds it to the swagger file located in ./docs/swagger.json
This PR has been tested and is working locally. I still want someone else to test it to be sure that the indexing is working as it should.

@kauffj Now we can add a search bar on the channel page to search for content specific to a channel

https://github.com/lbryio/lbry-desktop/issues/1735

I will test this soon

@filipnyquist Can we make this 2 pull requests? the swagger stuff is flooding things and I am not sure if I missed anything important. Also the api docs are not really required for the functioning of the api. So worse case scenario we get the channel parameter and a little later we get the docs for example.
Overall great work man! how long did that swagger file take to create!? I know those things are tedious.

 I´ll split this into two PRs. Closing this for now.

Moved the channel stuff to #92, doc will be in its own PR soon.


Swift Version on Pod spec

Fixes this error during RN macOS init:
[!] Unable to determine Swift version for the following pods:  - lottie-react-native-macOS does not specify a Swift version and none of the targets (bluewallet-macOS) integrating it have the SWIFT_VERSION attribute set. Please contact the author or set the SWIFT_VERSION attribute in at least one of the targets that integrate this pod.

I'm using "lottie-react-native": "4.0.2", and  s.swift_version = "5.0" is not on my podspec. Was it really merged afterall?


Add PubSub I/O support to Python DirectRunner

This change allows the DirectRunner to support the streaming wordcount example.

R: @aaltay

LGTM

Some tests are failing with ImportError: Google Cloud PubSub not available, please install apache_beam[gcp]. You probably need to skip tests if gcp is not installed.

Coverage decreased (-0.009%) to 70.868% when pulling e9766b924a6ae049b4718f3faaa47cabc1777329 on charlesccychen:directrunner-pubsub into beb21f472a32114c826a663eb635708ef0da1d69 on apache:master.

Coverage decreased (-0.01%) to 70.864% when pulling eb51ffb77014d01315086b70c9c262d60344a7dc on charlesccychen:directrunner-pubsub into beb21f472a32114c826a663eb635708ef0da1d69 on apache:master.

LGTM


[Imgpx] Unable to load animated webp

Original file: https://res.cloudinary.com/curben/20190812/containers-webp.webp
I tried:

https://cdn.statically.io/img/res.cloudinary.com/curben/20190812/containers-webp.webp
https://cdn.statically.io/img/res.cloudinary.com/curben/20190812/containers-webp.webp?auto_format=false

Both links gave "HTTP 400 Bad Request".

Static webp is fine
Original: https://res.cloudinary.com/curben/20190812/container-settings.webp
CDN: https://cdn.statically.io/img/res.cloudinary.com/curben/20190812/container-settings.webp?auto_format=false

Another feature request is automatically convert gif to (animated) webp.

Sure! that's something to consider. I will try to provide it as soon as I can. I'll keep this one open.


The description of the before value of the payload of a push event is incorrect.

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
https://docs.github.com/ko/rest/using-the-rest-api/github-event-types?apiVersion=2022-11-28#event-payload-object-for-pushevent
What part(s) of the article would you like to see updated?

after and before are being translated the same.
You should translate before as '푸시 전 ref에 대한 가장 최근 커밋의 SHA입니다.'
Additional information
No response

@Yaminyam Thanks for reaching out, and flagging this! Since we us an internal, automated solution for our translated docs, I will flag your request for our team 💛
For more information on translations, please see https://github.com/github/docs/blob/main/contributing/types-of-contributions.md#earth_asia-translations ✨

Thank you for your feedback. We will review the issue (ICX ADO Tracking Reference: 1016834).


Non ASCII characters are missing from error messages.

Before submitting the issue

[x] I have checked that the bug is not a duplicate or, if it is, it needs to be reopened
[x] I have checked that I am running the latest version of WingetUI
[ ] I have tried resetting and reinstalling WingetUI and the issue persisted or happened again
[x] I have checked the FAQ section for solutions
[x] I have read the contributing guidelines and I agree with the Code of Conduct

Describe the bug
Non ASCII characters are missing from error messages.
Example:
Access denied in czech shows this:
Pstup k cest C:\ProgramData\chocolatey\lib\rufus\.chocolateyPending byl odepen.
instead of this:
Přístup k cestě C:\ProgramData\chocolatey\lib\rufus\.chocolateyPending byl odepřen.
To Reproduce
Steps to reproduce the behaviour:

Try to install some package with language that reports errors with non ASCII characters and fail

Expected behaviour
Error message should have non ASCII characters

Hello,
Does this issue still happen in the latest beta? (https://github.com/marticliment/WingetUI/releases/tag/2.0.0-beta3)

Still issue in 2.0.1


Use enchannel helper functions

I believe these are the changes required for the new helper functions introduce in https://github.com/nteract/enchannel/pull/9 .  Make sure to publish enchannel before merging

Looks like we'll also need a Travis file for ick, unrelated to this PR.

I put up a PR before making a release: https://github.com/nteract/enchannel/pull/10

Are you picking this one up now that we've taken in all the other changes?

Sure, I'll look at this separate to this PR


hi, there is a style error in the Microsoft Edge

When I set the value of the currentSelected 2 , the viewer show the first image. However I tested the official website that show the same error.

Hi,
Thanks for your feedback :100:
I'll check it soon.


Ensure inclusive language is used in SS

I would be great to ensure we're using the best language we can.
i.e
Making changes like this

old
new

master
main

master
dispatcher

slave
responder

blacklist
blocklist

whitelist
allowlist

blacklist
denylist

whitelist
acceptlist

Obviously these changes can be wide reaching, (effecting private, property names and more) so it makes the most sense to incorporate this into the major release of CMS 5.
Thankfully it doesn't seem to be a lot present in here.
Searching the above on 5 branch only turned up 72 hits for whitelist mostly in comments.
Shouldn't be too hard to fix.
Companion Issue for silverstripe-cms https://github.com/silverstripe/silverstripe-cms/issues/2848

I'm going to close https://github.com/silverstripe/silverstripe-cms/issues/2848 for now as a duplicate to focus discussion to a single issue - we can reopen it based on the outcome of the discussion.
I suspect (without having checked myself) that a lot of the usage of this language is in the names of methods, configuration properties, classes, or method parameters. For those scenarios, we can't make changes without introducing breaking changes (with exception to any non-configuration scoped private) - and the window for that in CMS 5 has passed.
Any comments which refer to the above we also can't make, because then the comment will use different wording than the API which could lead to confusion.
It might be best to leave this for a time when we can introduce breaking changes again, which is whenever we start work on CMS 6. That said - are there a lot of instances of non-inclusive language which, if changed, would not introduce breaking changes or confusion?

Some decent reading and so on here: https://inclusivenaming.org/faqs/
I think it's pretty hard to measure things that aren't happening, if you know what I mean. I can't see how this is anything but a positive change - granted it's likely a breaking one unless you convert a whole pile of methods in to "proxy" methods with deprecation warnings i.e.
public function getWhiteList()
{
  Deprecation::warning('Will be gone in CMS6'); // or whatever the syntax is
  return $this->getAllowList();
}

but to that end, if people are asking for it I think it's worth pursuing.

Very late to the party, but I definitely support these naming changes. Even if I (white CIS woman) am not in a group that feels the echoes of those words as strongly - and I do feel deeply uncomfortable with "slave", and to a lesser degree "master", "black/whitelist", etc - even if the majority of people who see these terms aren't, it's still a good thing to do to avoid quietly hurting people, in so much as is practical without turning the codebase into knots.

Lets not turn this into a discussion about who is responsible for the meaning or interpretation of various words or phrases, please. This is a discussion about the feasibility and value of making the proposed change.
I will speak to your point which was on topic though:

There is industry jargon that is very well established and well understood by the programming community and has been for a long time

Terms like "allowlist" and "denylist" are just as easy to understand as (if not more so than) "whitelist" and "blacklist". Regardless of connotations, I'd support changing these terms because "allow" and "deny" are immediately better at conveying their purpose without requiring a previous understanding of industry jargon.


[Configuration] Allow for dynamic settings changes

Might be best to use a database lookup for each setting option when it is required.

Moved to Jira


Service start is broken on Debian > 8.0

Hello,
On Debian 8.2, (and 8.x globally), catalogue compilation is broken with this message:
Error: /Stage[main]/Consul::Run_service/Service[consul]: Could not evaluate: Could not find init script for 'consul'
Notice: /Stage[main]/Consul::Reload_service/Exec[reload consul service]: Dependency Service[consul] has failures: true
Warning: /Stage[main]/Consul::Reload_service/Exec[reload consul service]: Skipping because of failed dependencies
Notice: /Stage[main]/Consul/Anchor[consul_last]: Dependency Service[consul] has failures: true
Warning: /Stage[main]/Consul/Anchor[consul_last]: Skipping because of failed dependencies

Puppet try to launch the service with init because provideris not set on service declaration
This is a bug with the puppet provider, for more informations, see this bug
2 workarounds are possible:

Dirty method -> configure service globally

  Service { provider => 'systemd'}

  class { '::consul':
    config_hash => {
      'bootstrap_expect' => 1,
      'data_dir'         => '/opt/consul',
      'datacenter'       => 'eu-west-1',
      'log_level'        => 'INFO',
      'node_name'        => "${::fqdn}",
      'server'           => true,
    }
  }

Clean method -> change module behaviour

Add a switchcase on service declaration and set providerif necessary.
For informations:
puppet-client version: 3.8.6-1puppetlabs1
puppetmaster version:  3.8.6-1puppetlabs1
debian version: 8.2

Can you make a PR to make it work on the platform you use?
The code hint is probably here:
https://github.com/solarkennedy/puppet-consul/blob/3e43a74949df1ff9892f93ac5deb2a8fdc9d6362/manifests/params.pp#L52

Hey, this not the PR https://github.com/solarkennedy/puppet-consul/pull/125 ?

:+1:

I've merge #125. Please try master.

with your last commit, puppet is able to start consul :+1:


Minor typo in readme

err = webcam.StartStreaming()
should be
err = cam.StartStreaming()

@riomhaire, thank you very much for a report.


添加后lldb无法调试，提示有冲突

error: instance method 'operationDictionary' has incompatible result types in different translation units ('NSMutableDictionary *' vs. 'JPOperationsDictionary *' (aka 'NSMutableDictionary *'))
instance method 'operationDictionary' also declared here

Try version 3.0 please.


FundMe- TypeError: "send" and "transfer" are only available for objects of type "address payable", not "address".

Here is the function that throws the error:
function withdraw() public payable onlyOwner {
msg.sender.transfer(address(this).balance);
for (
uint256 funderIndex = 0;
funderIndex < funders.length;
funderIndex++
) {
address funder = funders[funderIndex];
addressToAmountFunded[funder] = 0;
}
//funders array will be initialized to 0
funders = new address;
}
I get the following error:
CompilerError: solc returned the following errors:
TypeError: "send" and "transfer" are only available for objects of type "address payable", not "address".
----msg.sender.transfer(address(this).balance);
Thank you for help!

msg.sender is of type address. Wrap payable around msg.sender to change it to type address payable -> payable(msg.sender).transfer(address(this).balance)
I believe this was a change made in Solidity version 0.8.`

Thank you!


wrong name for sponsors.ts page test

Describe the bug
sponsors.ts is not recognized by cypress due to file name
To Reproduce

cd website
run Cypress
e2e
note lack of page

Expected behavior
Page should appear
Screenshots
already fixed
System
please complete the following information:

OS: Windows
Version: 10

Additional context

fixed


Modification and addition of new utility classes

Modification and addition of new utility classes to the existing CSS code have been made to enhance the styles and provide additional customization options. New utility classes like .flex-center, .py-4, .text-xl, .border, .blurred, and .rotating have been introduced to aid in various layout and design requirements. Additionally, the original scrollbar styles, base styles, and animated image styles have been preserved.

invalid


[FEATURE]

I think name should persist i.e I should not need to fill in my name when taking a new test. Also volume should persist too.(In my opinion).
You can assign me this one :)

Hey @Kahono0, thanks for this feature suggestion. Actually, a new test means that everything will reset to default and a completely new test will be started with new details and properties. So this feature is not really required according to me. If you have any more points to explain why it can be helpful then we can move forward, or else close this issue.
Happy Contributing!

Thank you @prakhartiwari0 for replying. Having to write a name for every new test seems to me like an unnecessary extra step.

You have closed this issue so I think it's not much needed.


[Governance] Open HRMP channel with Robonomics

Problem statement
We have our Substrate bridge that enables SORA <-> Kusama parachain transfers. Now we want to open HRMP channels with parachains to enable users to transfers their assets and trade them on Polkaswap.
We start with opening the HRMP Channel on Rococo, then move forward with opening the channel on Kusama.
Description
No response
Definition of Done

[ ] Open HRMP channels on Rococo
[ ] Register Kintsugi assets on the SORA mainnet (Rococo)
[ ] Confirm SORA assets are registered in the Kintsugi chain (Rococo)
[ ] Open HRMP channels on Kusama
[ ] Register Kintsugi assets on the SORA mainnet (Kusama)
[ ] Confirm SORA assets are registered in the Kintsugi chain (Kusama)

Requirements
Opening HRMP Channels

Under vote by SORA Kusama parachain Council on motion 4
https://cloudflare-ipfs.com/ipns/dotapps.io/#/council/motions


Allow to disable transformer

Some of the transformers should be able to use disable flag so its only executed when selected. It's usefull for example for transformers that refactor deprecated code (old for loops) and we dont need to run it everytime.
@transformer(disable=True)

That way when executing:
robotidy <src>

Robotidy will execute all transformers except the ones with disable=True. To run it we need to call it by name:
robotidy - -transform DisabledTransformation

Done in #71. Instead of using decorator I've opted for optional class attribute ENABLED .When it's present and set to False then given transformer will be disabled by default.


HAWKULAR-748 Error on empty notes

Minor fix for a bug found this morning during some local tests @pilhuhn, can you review and merge ? thx

Merged #610


Adds example of reading/writing RSA keys to/from file

Hello,
I started working with the rsa crate today, and it took me a while to figure out the idiomatic ways of reading/writing keys to and from .pem files. In retrospect, I can see that the re-export of the pkcs# crates offered those methods, but it took a while (I actually re-implemented the with std::fs::read_to_string and other methods before finding them).
I figured that other people might run into a similar issue at some point, so figured I might offer an example in the repository in addition to the documentation, as suggested in #7. I've added the cargo build --examples --all to the  Github Actions CI, and clippy should be happy. Thanks for your consideration, and happy to make any changes or answer any questions!

The CI is obviously very unhappy with me at the moment--I'll spend some time soon trying to replicate the failure and hopefully fix it before pushing more commits. Sorry about this!

Closing until I can make time to solve this in a separate branch


[New] serialize ODEScenario object

Summary of this new feature
Serialize ODEScenario object. This is related to #741 regarding deprecated Scenario class.
We can skip building baseline scenario when we have saved JSON file.
(Optional) Solution with the current version
import covsirphy as cs
filer = cs.Filer(directory="input", prefix="jpn")
snr_build = cs.ODEScenario.auto_build(geo="Japan", model=cs.SIRFModel)
# Dump
json_file = snr_build.to_json(**filer.json(title="scenarios"))
# Restore
snr = cs.ODEScenario.from_json(json_file)
# Check
snr_build == snr
snr.summary()

CovsirPhy version I used: 2.27.1

Documentation will be updated later.

With #1257,

update documentation
remove ODEScenario.__eq__ and ODEScenario.__ne__ because they are unstable


Create initial manifesto sections

Provide some high level policy areas to get things started and check
everything is working

This proposal is open for discussion and voting. If you are an eligible voter on this project (and not the proposer), you may cast your vote on whether or not it is accepted.
How to vote
Vote by entering one of the following symbols in a comment on this pull request. Only your last vote will be counted, and you may change your vote at any time until the change is accepted or closed.

vote
symbol
type this
points

Yes
:white_check_mark:
:white_check_mark:
1

No
:negative_squared_cross_mark:
:negative_squared_cross_mark:
-1

Abstain
:zipper_mouth_face:
:zipper_mouth_face:
0

Block
:no_entry_sign:
:no_entry_sign:
-10

Proposals will be accepted and merged once they have a total of 2 points when all votes are counted. Votes will be open for a minimum of 7 days, but will be closed if the proposal is not accepted after 90.
Votes are counted automatically here, and results are set in the merge status checks below.
Changes
@jt-nti, if you want to make further changes to this proposal, you can do so by clicking on the pencil icons here. If a change is made to the proposal, no votes cast before that change will be counted, and votes must be recast.

Current status:

problems creating new proposals
voting requires having a proposal approved!

Working on fixes, and improved getting started instructions.
In the mean time, comments and suggestions are very welcome, either using comments on this proposal, or using the "Ideas" menu... if either of those options work!


add support for pre-update hook

I'm experimenting with adding support for the preupdate hook. This hook is fired before any INSERT, UPDATE, or DELETE operations are committed to the database, and gives you access to the old values and the new values. I don't know if the current maintainers are interested in having this, but regardless I'd like some feedback on implementing it. If you all do not want to merge this I can keep this patch locally.
This allows you to do this:
const sqlite3 = require('./sqlite3');
const db = new sqlite3.Database(":memory:");

function onUpdate(type, db, table, oldValues, newValues) {
  if(type === "insert") {
    console.log("inserted:", newValues);
  }
  else if(type === "update") {
    console.log("updated:", oldValues, " to ", newValues);
  }
}

db.addListener("preupdate", onUpdate);

db.run('CREATE TABLE foo (id INTEGER PRIMARY KEY,  name TEXT NOT NULL UNIQUE);', function() {
  db.run('INSERT INTO foo (name) VALUES ("James")', function() {
    db.run('UPDATE foo SET name="Sarah"', function() {
      db.removeListener("preupdate", onUpdate)
      db.close();
    });
  });
});

The output is:
inserted: [ 1, 'James' ]
updated: [ 1, 'James' ]  to  [ 1, 'Sarah' ]

The first big change is I need to update to sqlite 3.14. The preupdate hook does not exist in the version current bundled into node-sqlite.
Then, I needed to compile it with the SQLITE_ENABLE_PREUPDATE_HOOK option.
The rest of the code mostly follows the conventions of the profile and trace events. However, the preupdate hook is a bit more work. Because it gives you access to changed rows, I need to construct two Row values that I can emit with the event. A few problems with this:

Row and Values is not available in database.cc as they are defined in statement.h. I needed to move them into database.h but this is probably not desirable. A better approach would be to create a new header file that both can include.
The preupdate hook does not give you access to the column names. Only index and value. So I need to only create an array, not an object, so I can't reuse RowToJS from statement.cc. This also means any of the Values::Field objects need a "placeholder" name that I don't actually use. Again, there's probably a better way to do this.

The user is expected to query the column names on app startup, as there would surely be a big perf penalty by querying them on every preupdate event.
I'm looking for general feedback; is this the right approach? Any obvious memory leaks, etc?

Coverage decreased (-6.05%) to 79.745% when pulling c7ec3fb7b79f7b6395a9219f27e94306faf706a1 on jlongster:master into ef7c28445533b56dea626a5018c9f33fdf1d3a6a on mapbox:master.

Nice!
Maybe getting the column names is not so slow because the fist database page (where schemas are stored) may be cached in memory. I use this code below to get the columns names. Note that it does not use sqlite3_step, just sqlite3_prepare is sufficient:
sqlite3_stmt * get_table_columns(sqlite3 *db, const char *table) {
   sqlite3_stmt *stmt=0;
   char *sql=0;

   sql = sqlite3_mprintf("SELECT * FROM %s WHERE 1=0", table);
   if (sql == 0) goto loc_exit;

   if (sqlite3_prepare_v2(db, sql, -1, &stmt, NULL) != SQLITE_OK) {
      sqlite3_finalize(stmt);
      stmt=0;
   }

loc_exit:
   if (sql) sqlite3_free(sql);
   return stmt;

}

It returns the prepared statement with the columns names. Then we can use sqlite3_column_name(stmt, ncol).

Yeah, after a bunch of research I found someone else suggesting that as well. Still, I didn't know how much work prepare does.

Maybe getting the column names is not so slow because the fist database page (where schemas are stored) may be cached in memory.

Does sqlite3 manually do this? Keep some sort of cache? Or do you mean we will most likely not hit the disk as it will already be cached by the OS?

Looks like emitting an object with column names is significantly slower:
# Emitting an array without column names:
jlong-16106:~/projects/node-sqlite3(master)% time node lib/index.js
node lib/index.js  0.49s user 0.05s system 145% cpu 0.367 total

jlong-16106:~/projects/node-sqlite3(master)% time node lib/index.js
node lib/index.js  0.47s user 0.05s system 143% cpu 0.359 total

jlong-16106:~/projects/node-sqlite3(master)% time node lib/index.js
node lib/index.js  0.48s user 0.05s system 143% cpu 0.368 total

# Emitting an object with column names:
jlong-16106:~/projects/node-sqlite3(master)% time node lib/index.js
node lib/index.js  1.21s user 0.21s system 150% cpu 0.938 total

jlong-16106:~/projects/node-sqlite3(master)% time node lib/index.js
node lib/index.js  1.19s user 0.20s system 151% cpu 0.924 total

jlong-16106:~/projects/node-sqlite3(master)% time node lib/index.js
node lib/index.js  1.19s user 0.20s system 152% cpu 0.913 total

jlong-16106:~/projects/node-sqlite3(master)% time node lib/index.js
node lib/index.js  1.21s user 0.21s system 149% cpu 0.942 total

Goes from an average of ~.36s to ~.92. My test case is simple:
function onUpdate(type, db, table, oldValues, newValues) {
}

db.addListener("preupdate", onUpdate);

db.run('UPDATE transactions SET description="foo" WHERE amount < 40000', function(err) {
});

This is run against a database containing thousands of rows, and the query affecting 21568 of them. My first guess was that maybe creating JS objects are slower than arrays, but that shouldn't be true so there isn't much extra JS allocation. Must be the process of preparing a statement and getting the column names.

This is an interesting result.
You can just retrieve the column names without creating the javascript object, just to check the speed.
And yes, the SQLite has a page cache but I guess it is used for modified pages to be kept on memory before a transaction is commited. I am not sure if the same page cache is used when running a second SQL query. I can test it.

Coverage decreased (-6.2%) to 79.609% when pulling 51a63488051dd213857ba9d6f8a9cb005a18c29f on jlongster:master into ef7c28445533b56dea626a5018c9f33fdf1d3a6a on mapbox:master.

Maybe it's because the hook function is being called for each modified row.
What is your goal with this code? Synchronization?

Maybe it's because the hook function is being called for each modified row.

Yes, which is why I didn't set it up that way in the first place. It's an advanced feature so users are expected to manage the column names themselves.

What is your goal with this code? Synchronization?

I'm developing a specialized app that needs to know when things change. Hard to explain without going into the details of the app. I'm expecting to maintain a fork for now and if there's interest I can help merge this in, but as said earlier I wouldn't be surprised if the maintainers didn't want this right now.

So there are 2 bad things still going on with this PR:

The preupdate events may fire after the callback to db.run is called (most of them fire before, but if firing a lot some come through later). It's unclear to me what is desirable. Should we enforce an order? Doing so may block the process for a while, if you're always waiting for all preupdate events to fire before finishing. Maybe the order is nondeterministic. Personally, I don't know enough about libuv to know how to enforce the order. This is all based on the async.h implementation which uses libuv signals.

Much more serious, the app doesn't seem to exit sometimes. I've banged my head against the wall for a while on this. I have no idea why. It must be something with the async.h watchers not getting cleared out or something. You can repro this by checking out git clone -b hang-repro https://github.com/jlongster/node-sqlite3.git and running node lib/index.js (I even committed the local db for testing). Run it several times and eventually the app won't exit, it just hangs.

I tried compiling a version of sqlite without mutexes just in case it was a race condition, but that didn't help.  I think it only happens when it fires the hook a lot of times (here, about ~20000). Any guidance for how to debug this would be great.

Figured it out! These lines are problematic: https://github.com/mapbox/node-sqlite3/blob/master/src/async.h#L65-L69
If sending thousands of events, node just never shuts down.

This is the latest code that works pretty well for me. Got some help with the race condition and it is solved in https://github.com/mapbox/node-sqlite3/pull/705 (thanks!).
The last issue is that the preupdate hook isn't guaranteed to be done firing before the run callback is called. Updates that trigger the hook may still come through after the run callback if thousands of them are coming through. This happens because the hook dispatches messages via libuv and as far as I can tell the run callback is called immediately when it's done, so there may still be preupdate messages about to be fired.
I think this is a problem, but not big enough to block me. I'll have to fix it at some point, so if anyone has pointers, that'd be great. Otherwise I'll fix it later.

Coverage decreased (-6.3%) to 79.474% when pulling ed16f6bd0b27752ec32c6a0d452713fc3a5b7231 on jlongster:master into 7322ea714b13451bab75d5232a1dd2a05fcb5052 on mapbox:master.

Coverage decreased (-6.4%) to 79.439% when pulling 4a40a728a8663427d927c9ad41742bce2596ef74 on jlongster:master into 7322ea714b13451bab75d5232a1dd2a05fcb5052 on mapbox:master.

Found this thread looking for this feature, any reason why this never got merged?

Hey @jlongster, would you be able to rebase the PR? 🙂

No worries 🙂 I'm going to close this PR for now, but I may look into implementing this in the near future


customFields for kinesis not work

Hello!
Seems like customFields for kinesis not work. I tested it on my cluster with settings like this:
kinesis:
  accessKeyID:
  secretAccessKey:
  secretRef: ""
  region: ru-central1
  endpoint:
  streamName: reports
  minimumPriority: ""
  skipExistingOnStartup: true
  customFields:
    cluster-id: test-cluster888888888

helm install policy-reporter policy-reporter/policy-reporter \
..
--set target.kinesis.customFields.cluster-id="test-cluster888888888" \
..

and i dont see this custom fields in target event
{
    "Category": "Pod Security Standards (Baseline)",
    "Message": "validation rule 'adding-capabilities' passed.",
    "Policy": "disallow-capabilities",
    "Priority": "info",
    "Properties": {},
    "Resource": {
        "APIVersion": "v1",
        "Kind": "Pod",
        "Name": "pod2",
        "Namespace": "default",
        "UID": "2d6d8482-008b-43fe-9d7a-5e51b9708abd"
    },
    "Rule": "adding-capabilities",
    "Scored": true,
    "Severity": "medium",
    "Source": "Kyverno",
    "Status": "pass",
    "Timestamp": "2022-10-27T10:23:19Z"
}

my college find that from the config this setting is not transferred to the sender
https://github.com/kyverno/policy-reporter/commit/573a1108c7891e7f34146123775451b8b0f67787
https://github.com/kyverno/policy-reporter/blob/a3c09d08222554429ddb6c33d05df4cc36b88cf7/pkg/config/target_factory.go#L634
maybe someone from your team will be able to complete this function?

hey, which version of the helm chart do you use? I released  yesterday a new version which should fix this issue.

Hm es, you're right. I will work on a fix today.

I released v2.13.4 of the Helm Chart with a fixed app version

thank you very much !

You're welcome, thanks for reporting the issue


My new

Problems needed to work on

the toggle visibility in the form
wasn't any feedback after clicking the input
needed to be responsive to different screen sizes.
What changes are made to solve these:
created a JavaScript file
to add more functionality to the page
now the toggle password is working
user will get feedback when a specific input field is selected

Good work!
Looks good to me.


Keyboard appears over PIN entry when backgrounding the app while the keyboard is visible

Describe the bug
Any time the keyboard appears on screen and the application is backgrounded, bringing the app into the foreground shows the keyboard over the PIN entry screen.
To Reproduce

Go to Contacts
Tap the search / filter bar
The on-screen keyboard will appear
Background the application
Restore the application
Observe that the keyboard appears over top of the PIN entry screen

Expected behavior
The keyboard should be dismissed when the application is backgrounded.
Screenshots

Smartphone (please complete the following information):

Device: All
OS: All
Version: Any

Additional context
N/A

This is fixed in #184


Demo Video not accessible, if using ad-blocker on Youtube

Youtube has blocked the access completely for me, because I don't want ads.
I think it is time, to search a different place, where videos can be stored without restrictions.

Try Opera for Youtube :)
На ср, 25.10.2023 г., 00:16 ч. Daniel Schöni @.***>
написа:

Youtube has blocked the access completely for me, because I don't want ads.
I think it is time, to search a different place, where videos can be
stored without restrictions.
—
Reply to this email directly, view it on GitHub
https://github.com/ilian6806/stable-diffusion-webui-state/issues/54, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABWTAW25OCXU5SHL2GPZADTYBAV4TAVCNFSM6AAAAAA6OKNRZCVHI2DSMVQWIX3LMV43ASLTON2WKOZRHE3DAMBZGI2DONQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

This is really strange... However, I upload them in a cloud, so you can  watch them here.


Ycash links to payment uri don't work

Subject of the issue
The donate button on the app faq gives an error
Your environment

version of YWallet: 1.3.3
platform and version: Android 10

Steps to reproduce
Click on the donate link on
https://ywallet.app/faq/ gives an invalid payment uri error.
Expected behaviour
Should allow you to send 10 yec
Actual behaviour
Payment uri error, invalid scheme

It works when there is an active ycash account.


Intermittent issues browsing albums

On some albums, instead of letting your browse down into their contents mopidy gives out a traceback instead.
ERROR    JellyfinBackend backend caused an exception.
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/mopidy/core/library.py", line 19, in _backend_error_handling
    yield
  File "/usr/lib/python2.7/site-packages/mopidy/core/library.py", line 112, in _browse
    result = backend.library.browse(uri).get()
  File "/usr/lib/python2.7/site-packages/pykka/threading.py", line 52, in get
    compat.reraise(*self._data['exc_info'])
  File "/usr/lib/python2.7/site-packages/pykka/compat.py", line 12, in reraise
    exec('raise tp, value, tb')
  File "/usr/lib/python2.7/site-packages/pykka/actor.py", line 201, in _actor_loop
    response = self._handle_receive(message)
  File "/usr/lib/python2.7/site-packages/pykka/actor.py", line 295, in _handle_receive
    return callee(*message['args'], **message['kwargs'])
  File "/usr/lib/python2.7/site-packages/Mopidy_Jellyfin-0.2.6-py2.7.egg/mopidy_jellyfin/library.py", line 39, in browse
    return self.backend.remote.get_tracks(album_id)
  File "/usr/lib/python2.7/site-packages/Mopidy_Jellyfin-0.2.6-py2.7.egg/mopidy_jellyfin/remote.py", line 223, in get_tracks
    key=lambda k: k['IndexNumber']
  File "/usr/lib/python2.7/site-packages/Mopidy_Jellyfin-0.2.6-py2.7.egg/mopidy_jellyfin/remote.py", line 223, in <lambda>
    key=lambda k: k['IndexNumber']
KeyError: u'IndexNumber'

Caused by incomplete metadata when a track was missing a track number.  Fixed by adding a fallback value in 85259cac670a7d10331c06bf97e8e8df03c028c2


BERT model does not have expected output names

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): No
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): macOS 10.15
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: N/A
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): 2.1.0
Python version: 2.7
Bazel version (if compiling from source): N/A
GCC/Compiler version (if compiling from source): N/A
CUDA/cuDNN version: N/A
GPU model and memory: N/A

Describe the current behavior
# model is from: https://tfhub.dev/tensorflow/bert_en_cased_L-12_H-768_A-12/1

saved_model_dir = "path/to/bert_en_cased_L-12_H-768_A-12/1"
loaded_model = tf.saved_model.load(saved_model_dir)
concrete_func = loaded_model.signatures["serving_default"]
prediction = concrete_func(**inputs)

As an user, I'm expecting output names to be ["Identity", "Identity_1"] as shown:
concrete_fn.outputs
Out[4]:
[<tf.Tensor 'Identity:0' shape=(None, 768) dtype=float32>,
 <tf.Tensor 'Identity_1:0' shape=(None, None, 768) dtype=float32>]

However, actual prediction returns a dict with different output names:
["bert_model", "bert_model_1]
prediction.keys()
Out[5]: [u'bert_model_1', u'bert_model']

Describe the expected behavior
Expecting the prediction output has same name as concrete_func.outputs.

https://tfhub.dev/tensorflow/bert_en_cased_L-12_H-768_A-12/1 (and now also version /2) is a TF2 SavedModel. Please see https://www.tensorflow.org/hub/tf2_saved_model for how to reuse it, In particular, the discussion of serving signatures vs tf.function API under the heading "what to expect from the SavedModel after loading". Bottom line: use loaded_model(), not loaded_model.signature["..."]().
Also, please note that signatures are meant to map between externally visible names (the keys you observed) and in-graph names (as reported in a tf.Tensor's string representation).


Offset sign convention is different between LineString and Point queries

When requesting line strings, positive offsets are to the Left Hand Side when travelling in the direction of increasing SLK.

Correct

When requesting point features, positive offsets are to the Right Hand Side when traveling in the direction of increasing SLK.

Incorrect

The behaviour of point queries will be changed in the next release to be consistent with the current LineString Offset behaviour.
Code from LineString queries (note the negation):
let degree_offset:f64 = convert_metres_to_degrees(query.offset.into());
match b.offset_basic(-degree_offset){
...

Code from Point queries:
match lsm.offset_basic(convert_metres_to_degrees(query.offset.into())) {
    Some(vec_of_vector2)=> Some(LineStringMeasured::from(vec_of_vector2)),
...

Fixed by in release tag v0.8.0


Update the rust API reference

landing page (crate-level docs)
archetypes module
etc

We should also import archetype::* into the rerun module jut like we do for Python, and write rerun::Points3D instead of rerun::archetypes::Points3D everywhere

It's pretty good now. Probably good enough.


Removal of unsupported vendor prefixes for @viewport

Fix issue #19871.

LGTM
@cvrebert @mdo : any objections to merge this?


On dismissed?

This might already be solved, but i'd like to do the following: Get notified when the user taps outside of the info window thus it being "cancelled". The reason for that is i'd like to do the exact same thing in the demo, but without needing to write in each of the descriptions "To close this, tap on the highlighted item" or similar. To us it may be obvious but it'd be great if simply tapping anywhere allowed me to display the next info item.

Thanks for reporting. This is actually not supported as of now, but definitely should be.
I imagine appending onCancel to the listener interface would suffice. Does that sound good to you?

That'd be perfect i'd say! :+1:
An aside, everything is working just beautifully!

Cool. I can fix this in a few hours. Feel free to submit a PR in the meantime if you need it sooner

No problem, no rush required!
------ Original Message ------
From: "Hilal Alsibai"<EMAIL_ADDRESS>To: "KeepSafe/TapTargetView"<EMAIL_ADDRESS>Cc: "Joe Scott"<EMAIL_ADDRESS>"Author"<EMAIL_ADDRESS>Sent: 13/09/2016 15:31:04
Subject: Re: [KeepSafe/TapTargetView] On dismissed? (#1)

Cool. I can fix this in a few hours. Feel free to submit a PR in the
meantime if you need it sooner
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Improve docker networking

After a careful code review, this PR should be rebased and merged into master (but #42 should be merged to master first, as this branch was checked out from that one).


Use parameter properties to simplify constructors across codebase

Small refactoring of constructors across code base to use parameter properties.
There was also a couple of places where constructors on derived classes were just passing arguments through to a base class with no additional logic, so i have removed those where I could see them.
Fixes #619

Thanks @bencoveney!


Use offset adjusted value in ModulusAnimatedNode

Modulus animation computation should use the value adjusted for offset, not the raw value.
See the JS implementation here:
https://github.com/facebook/react-native/blob/master/Libraries/Animated/src/AnimatedImplementation.js#L1338
cc @ryangomba

@shergin Could you ship this one too


Draw wrapped lines of text

A simple wrapper function around drawText that automatically wraps lines at a specified length.

This is exactly what I need...

@scottie-schneider It's very easy to monkeypatch into your project from this PR.
You may want to do that since I suspect this might take a while to merge because I haven't included any testing. I was waiting to get some feedback before going ahead with that.

@multiplegeorges Got it working, thanks to your examples and code. Thanks sir!

Hello @multiplegeorges! Thank you very much for working on this. It's a feature that's been on my mind but that I haven't had the time to work on. I think it will be a great addition that many users will find very helpful.
Here are my thoughts after looking the PR over:

I'm not sure about the API. Specifically, I don't think I like the addition of the drawWrappedText method. I do like the maxWidth option though. What do you think about removing the drawWrappedText method and adding the maxWidth to the existing drawText method? If the user doesn't specify maxWidth, we can just default to the existing behavior. But if they do specify it, then we can branch into the code you've written to do the line wrapping.

I'm concerned about the efficiency of the implementation. There are 2 opportunities I can see for improving this:

Reuse candidateString instead of re-running words.slice(startIndex, i).join(' ').
Measuring the width of a string can be a somewhat expensive operation. Perhaps we could measure the width of each word and sum their widths to compute the full line's width. This would allow the word widths to be cached (within or across drawText calls).

However, I would be interested in having some concrete numbers on how long it takes to compute the layout before and after the optimizations. I think we want optimization #1 for sure. But optimization #2 is a bit more involved, and I wouldn't want to add that complexity if it doesn't provide tangible performance benefits. Would you be willing to collect these numbers for large blocks of text with standard and embedded fonts?

Splitting by whitespaces may prove difficult for languages that don't use space as word separators (i.e. Chinese), and in rare cases, a very long Latin word.
I suggest a word breaking character wordBreak = "-" as the default for English users, while Chinese users can put an empty string for their specific use cases.
I can do the word-breaking logic in a separate PR on top of this.
Site-node: @Hopding Word-splitting, especially in Chinese paragraphs, may render pre-calculated word widths in suggestion #2 a waste of resources though. What do you think?

Thanks again for everybody's work on this. I've merged a variant of this code in https://github.com/Hopding/pdf-lib/pull/198. It will go out in the next release of pdf-lib. If anybody would like to document the maxWidth and wordBreak options in the README or API docs, that'd be awesome. These options are currently undocumented.

Version 1.1.1 is now published. It contains the maxWidth and wordBreak options for the PDFPage.drawText() method. The full release notes are available here.
You can install this new version with npm:
npm install<EMAIL_ADDRESS>
It's also available on unpkg:

<EMAIL_ADDRESS><EMAIL_ADDRESS>


Unable to start container with a service account

The container fails to start when you attempt to run it with a service account due to a permission value on this line
https://github.com/wouterdebie/locast2tuner/blob/47cc62e1a4881143c37d7737aca338fcc76ebeb1/src/config.rs#L157
Steps to reproduce the behavior:

On a Debian machine
Create a system user sudo adduser --system locast
Create the locast2tuner config and docker config file in /home/locast and set ownership to the system account chown -R locast:nogroup /home/locast
Get the uid and gid of the new user id locast
In docker compose set the user to be the system account with user: <uid>:<gid> for the system account
Start the container

** Logs **
thread 'main' panicked at 'Unable to create directory "/var/empty/.locast2tuner": Os { code: 13, kind: PermissionDenied, mess$
ge: "Permission denied" }', src/config.rs:179:14
stack backtrace:
   0:           0x91ead0 - std::backtrace_rs::backtrace::libunwind::trace::h3eef70d8f61bd364
                               at /rustc/c755ee4ce8cae6ea977d65a0288480940db721d9/library/std/src/../../backtrace/src/backtrac
e/libunwind.rs:90:5
   1:           0x91ead0 - std::backtrace_rs::backtrace::trace_unsynchronized::hdb800973714224e8
                               at /rustc/c755ee4ce8cae6ea977d65a0288480940db721d9/library/std/src/../../backtrace/src/backtrac
e/mod.rs:66:5
   2:           0x91ead0 - std::sys_common::backtrace::_print_fmt::h27461aa20e7698ec
                               at /rustc/c755ee4ce8cae6ea977d65a0288480940db721d9/library/std/src/sys_common/backtrace.rs:67:5
   3:           0x91ead0 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::hebf5ea6a86cc314
b
                               at /rustc/c755ee4ce8cae6ea977d65a0288480940db721d9/library/std/src/sys_common/backtrace.rs:46:2
2
   4:           0x95e89f - core::fmt::write::h4441a937b7e1b475
                               at /rustc/c755ee4ce8cae6ea977d65a0288480940db721d9/library/core/src/fmt/mod.rs:1094:17
   5:           0x918995 - std::io::Write::write_fmt::h0ff5303ac0545869
                               at /rustc/c755ee4ce8cae6ea977d65a0288480940db721d9/library/std/src/io/mod.rs:1580:15
   6:           0x9209bb - std::sys_common::backtrace::_print::hb745e885b5aa6a5d
                               at /rustc/c755ee4ce8cae6ea977d65a0288480940db721d9/library/std/src/sys_common/backtrace.rs:49:5
   7:           0x9209bb - std::sys_common::backtrace::print::hd68c9ca4e2a2ce4b
                               at /rustc/c755ee4ce8cae6ea977d65a0288480940db721d9/library/std/src/sys_common/backtrace.rs:36:9
   8:           0x9209bb - std::panicking::default_hook::{{closure}}::hf4e6910d621f9df1
                               at /rustc/c755ee4ce8cae6ea977d65a0288480940db721d9/library/std/src/panicking.rs:208:50
   9:           0x92049d - std::panicking::default_hook::h76827c3ad104d96e
                               at /rustc/c755ee4ce8cae6ea977d65a0288480940db721d9/library/std/src/panicking.rs:225:9
  10:           0x920f6d - std::panicking::rust_panic_with_hook::h3d031148c54b1f39
                               at /rustc/c755ee4ce8cae6ea977d65a0288480940db721d9/library/std/src/panicking.rs:591:17
  11:           0x920b67 - std::panicking::begin_panic_handler::{{closure}}::h256c064cccbc9d44
                               at /rustc/c755ee4ce8cae6ea977d65a0288480940db721d9/library/std/src/panicking.rs:497:13
  12:           0x91ef8c - std::sys_common::backtrace::__rust_end_short_backtrace::hf2447f9118ce1847
                               at /rustc/c755ee4ce8cae6ea977d65a0288480940db721d9/library/std/src/sys_common/backtrace.rs:141$
18
  13:           0x920ac9 - rust_begin_unwind
                               at /rustc/c755ee4ce8cae6ea977d65a0288480940db721d9/library/std/src/panicking.rs:493:5
  14:           0x41bab1 - core::panicking::panic_fmt::hceb86924f693208a
                               at /rustc/c755ee4ce8cae6ea977d65a0288480940db721d9/library/core/src/panicking.rs:92:14
  15:           0x41bba3 - core::result::unwrap_failed::hdc7ce9e88097fff7
                               at /rustc/c755ee4ce8cae6ea977d65a0288480940db721d9/library/core/src/result.rs:1355:5
  16:           0x484c65 - locast2tuner::config::Config::from_args_and_file::h1e9c4a5e4239105c
  17:           0x4acaff - locast2tuner::main::{{closure}}::h9f18ec02eda4a6ea

** Configuration **
version: "3"
services:
  locast2tuner:
    image: ghcr.io/wouterdebie/locast2tuner
    restart: unless-stopped
    user: "123:65534"
    container_name: locast2tuner
    volumes:
      - /home/locast/config.d:/app/config
      # - /home/locast/:/home/locast # workaround
    expose:
      - 6077
    networks:
      - web
    environment:
      - RUST_BACKTRACE=full
      # - HOME=/home/locast # workaround

networks:
  web:
    external: true

Environment
Debian 11
Additional context
You can work around the issue by manually mounting the service account home directory and setting the Home environment variable.

I'm not a Docker expert, but it seems that the problem is the fact that you create a system user and for some reason the home dir of that user is /var/empty, which is probably wrong. Can you try adding --home /home/locast to your adduser command?

That might be it, or the user may have to be created inside the container in Dockerfile.
Alternatively, add the locast user to the docker group in /etc/group and run docker-compose as that user.
You'd have to get into a shell in the container to really see what's happening.

@armaros Any update on this?

Closing this issue, because there has been no response


kitti stream example on headless cloud machines

Hi team,
I am trying to run the kitti stream example on a headless cloud machine. This is what I followed:
# server side
$ git clone https://github.com/uber/xviz.git
$ cd xviz && yarn bootstrap
$ ./scripts/download-kitti-data.sh
$ ./scripts/run-kitti-example.sh

# client side
$ git clone https://github.com/uber/streetscape.gl.git
$ cd streetscape.gl.git && yarn bootstrap
$ cd examples/get-started
$ yarn
$ yarn start-streaming-local

Both server and client have successfully started but I only see an (almost) empty page when I tried to connect to CLOUD_MACHINE_IP:8080.
Everything works fine on my local machine with a browser page popping out when launching the client.
Then I tried to find out what happened. I used a tool called wscat to check whether client has connected with server. Here is the github link to wscat:
https://github.com/websockets/wscat
On the cloud machine, I used "wscat -l 8081" to listen 8081 port and launched client with "yarn start-streaming-local". It did not show 'client connected" while it showed on the local machine with the same operation.
Then I deleted the "--open" option of "start-streaming-local" command in the package.json file in get-started folder in my local machine, and restarted server and client again. No browser page popped out automatically and no connection was established with server. Only after I opened my browser and type localhost:8080, the server showed that it established connection.
Does it need to have a web browser open "localhost:8080" and then the client can send connection request to server? I tried to use "curl" or open CLOUD_MACHINE_IP:8080, nothing happened. How can I establish all things on the cloud and only use local web browser to get display?

solved


Discordjs V13 support

Does this package supports dicord.js v13

Does this package supports dicord.js v13

@pauldb09 it only supports discord.js v11. it needs to be get updated to the latest version.

Does this package supports dicord.js v13

@pauldb09 it only supports discord.js v11. it needs to be get updated to the latest version.

uh ok thanks for the answer still if its one year later 👀


[BUG] v112 to v120 upgrade: helm-install-rancher-monitoring job failed due to BackoffLimitExceeded

Describe the bug

Observed from here: https://github.com/harvester/harvester/issues/4537#issuecomment-1735987068, added to EPIC: https://github.com/harvester/harvester/issues/4553
The v112 to v120 upgrade was successful, the the rancher-monitoring addon failed to be installed.
The Harvester dashboard is not showing any graphs.
The underlying Rancher shows that the helm-install-rancher-monitoring job failed
due to [BackoffLimitExceeded] Job has reached the specified backoff limit.

In the source code, we wait 6 minutes for the rollout of rancher-monitoring, it seemed this behaviour avoid blocking the whole upgrade process. With leaving this, we have the chance to manually fix it after the ugprade.
    # loop wait for at most 6 minutes (36 * 10s)
    loop_wait_rollout_monitoring 36

To Reproduce
Steps to reproduce the behavior:

v112 to v120 upgrade;  rare chances to reproduce.

Expected behavior

No failure.
Support bundle

Environment

Harvester ISO version: Harvester v1.1.2 to v1.2.0 upgrade
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630): 3-node clusters

Additional context
Add any other context about the problem here.
(1) The rancher-monitoring addon was fixed manually.
(2) Why the helm-install job failed is under investigation.
(3) Add issue and workaround to known issue in Harvester doc.
cc @bk201 @starbops @Vicente-Cheng @ibrokethecloud

Issue was not encountered in later upgrade, close as finished.


Swift global functions. Missing Array one.

Temporary solution for #14

Forgot to push a Bridging header. If possible, I'll push a Swift version of Cham next week

Wowwww! Thanks so much @bre7. Definitely wanted to get this done, but haven't had the time. :confused: You rock for this! :tada:  Woah excited to see a swift version. Really glad the community is contributing. :smiley:

ty for Chameleon :wink:


Charrom glitches on hardware when using "widescreen" mode

On hardware, running OS V0.22c in "widescreen" mode (force uploaded pB v0.19f), I get charrom glitches as I toggle between new and old character sets (CTRL + N and CTRL + O)

The charrom glitching doesn't happen in "narrow" mode.

Confirmed it happens on multiple systems with same configuration. Not specific to the original system discovered on.

Thanks Sean for reporting! I found the issue and making a fix for it.


Keybase updated on Sierra fail

I get this error message periodically when the keybase app is open on my computer, running Sierra

my log id: 3e6aea31627089713d13051c

Thanks for the bug report. This is a known issue and we are working on a fix.

Timeout issues are resolved in recent builds.


Samsung galaxy S4 (GT-I9506) : Failed to begin session

Hi All, I am trying to install CyanogenMod on my galaxy S4 following this guide:
https://wiki.cyanogenmod.org/w/Install_CM_for_ks01lte
I cannot flash the custom recovery, I get the error message: The device does not recognize the command
Steps I have taken:
-boot the phone into ODIN mode (home-volume-down-power, then volume up to accept
-connect the phone
-run zadig, replace driver (keep zadig running)
-run usbpcap, filename: S4
-run heimdall
-open S4 file in wireshark
S4.zip
Messages of Heimdall:
heimdall.exe flash --RECOVERY twrp-3.0.2-0-ks01lte.img --no-reboot
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
libusbx: error [winusbx_submit_bulk_transfer] ReadPipe/WritePipe failed: [22] The device does not recognize the command.
libusbx: error [winusbx_submit_bulk_transfer] ReadPipe/WritePipe failed: [22] The device does not recognize the command.
libusbx: error [winusbx_submit_bulk_transfer] ReadPipe/WritePipe failed: [22] The device does not recognize the command.
libusbx: error [winusbx_submit_bulk_transfer] ReadPipe/WritePipe failed: [22] The device does not recognize the command.
libusbx: error [winusbx_submit_bulk_transfer] ReadPipe/WritePipe failed: [22] The device does not recognize the command.
ERROR: Failed to begin session!
Releasing device interface...
Messages of the phone after booting into ODIN mode:
ODIN MODE
PRODUCTNAME: GT-I9506
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE
AP SWREV: S1, T1, A1, A1, P1
SECURE DOWNLOAD : ENABLE
UDC START
In wireshark, the phone has source: 2.1.0, but wireshark shows it as a galaxy SII:
Frame 1239: 46 bytes on wire (368 bits), 46 bytes captured (368 bits)
USB URB
[Source: 2.1.0]
[Destination: host]
USBPcap pseudoheader length: 28
IRP ID: 0xfffffa80091c1530
IRP USBD_STATUS: USBD_STATUS_SUCCESS (0x00000000)
URB Function: URB_FUNCTION_CONTROL_TRANSFER (0x0008)
IRP information: 0x01, Direction: PDO -> FDO
URB bus id: 2
Device address: 1
Endpoint: 0x80, Direction: IN
URB transfer type: URB_CONTROL (0x02)
Packet Data Length: 18
[Request in: 1238]
[Time from request: 0.001000000 seconds]
Control transfer stage: Data (1)
DEVICE DESCRIPTOR
bLength: 18
bDescriptorType: 0x01 (DEVICE)
bcdUSB: 0x0200
bDeviceClass: Communications and CDC Control (0x02)
bDeviceSubClass: 2
bDeviceProtocol: 0
bMaxPacketSize0: 64
idVendor: Samsung Electronics Co., Ltd (0x04e8)
idProduct: GT-I9100 Phone [Galaxy S II] (Download mode) (0x685d)
bcdDevice: 0x0100
iManufacturer: 1
iProduct: 2
iSerialNumber: 0
bNumConfigurations: 1
My versions:
Heimdall v1.4.0
Windows 7 Ultimate SP1 64bit, 8GB ram
USBPcap <IP_ADDRESS> http://desowin.org/usbpcap/
wireshark 2.2.1 https://www.wireshark.org/

Try to use Heimdall v1.4.1 (see Releases). Or download this repo and build Heimdall from source.

Hi Iamantony,
Where is the compiled windows version of v1.4.1? I can't find them in these locations:
https://bitbucket.org/benjamin_dobell/heimdall/downloads
https://github.com/Benjamin-Dobell/Heimdall/releases/tag/v1.4.1
Cheers,
Cedric

I have compiled Heimdall v1.4.1 on arch linux. After using a better USB cable I succeeded in installing the custom recovery.
Thank you for your work on this program. If I can be of assistance for testing something on my GT-I9506 phone, please let me know.
Best, Cedric

Good news)
I would suggest you to close this issue because you have solved problem.


Capture OSX credentials from the Prompt Module in the Empire DB

Yeah, I know this isn't into the DEV branch - but this is a simple change.  The other changes I'll push over to DEV and we'll do some more testing on them first.

Tested and approved!

Nice. Thanks!
On Tue, Aug 15, 2017 at 8:54 AM Steve Borosh<EMAIL_ADDRESS>wrote:

Tested and approved!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/EmpireProject/Empire/pull/636#issuecomment-322472222,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMJRZU-96nq1_EfnPuL2lge-6NgQl4pXks5sYaMCgaJpZM4O3GKs
.


Delay building an exception backtrace array

Previously, we were building a backtrace array when initializing an
exception object. Sometimes though we do not want to print the backtrace
which makes generating it useless.
This patch tries to delay building the backtrace array, until it will
actually be used.
This should impact a lot of code slightly, because exceptions are
sometimes used for control-flow in the language itself (LocalJumpError
for example).
Benchmark:
10000.times do |n|
  begin
    raise Exception, 'message'
  rescue Exception
  end
end

On MRI:
real    0m0.100s
user    0m0.080s
sys     0m0.020s

On Natalie (master):
real    0m0.247s
user    0m0.237s
sys     0m0.010s

On Natalie (with this patch):
real    0m0.190s
user    0m0.189s
sys     0m0.000s

This is pretty cool! :tada:


increment build number for 3.12

graphql-core 3.2.3
Destination channel: defaults
Links

PKG-4483
Upstream repository
Upstream changelog/diff
Relevant dependency PRs:

moto (for 3.12 build only)

Explanation of changes:

...

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_89fanlypyw/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:16: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
===== Final Report: =====
1 Error and 0 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_cfko9tb021/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:21: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.

===== ERRORS =====

clone/recipe/meta.yaml:21: missing_wheel: For pypi packages, wheel should be present in the host section
===== Final Report: =====
1 Error and 1 Warning were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_69gd6xm1zh/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:21: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.

===== ERRORS =====

clone/recipe/meta.yaml:21: missing_wheel: For pypi packages, wheel should be present in the host section
===== Final Report: =====
1 Error and 1 Warning were found

@JamesRobertsonGames There is an issue with poetry-core 1.5.2 for py312:
14:29:44
    └─ python >=3.12,<3.13.0a0  is not installable because it conflicts with any installable versions previously reported.

In the logs the host environment has:
    poetry-core:      1.5.1-py312h06a4308_0  defaults
    python:           3.12.3-h996f2a0_0      defaults

but checking the defaults channel there are:
https://repo.anaconda.com/pkgs/main/linux-64
poetry-core-1.5.2-py310h06a4308_0.tar.bz2
poetry-core-1.5.2-py311h06a4308_0.tar.bz2
poetry-core-1.5.2-py38h06a4308_0.tar.bz2
poetry-core-1.5.2-py39h06a4308_0.tar.bz2
https://repo.anaconda.com/pkgs/main/linux-aarch64
poetry-core-1.5.2-py310hd43f75c_0.tar.bz2
poetry-core-1.5.2-py311hd43f75c_0.tar.bz2
poetry-core-1.5.2-py38hd43f75c_0.tar.bz2
poetry-core-1.5.2-py39hd43f75c_0.tar.bz2
https://repo.anaconda.com/pkgs/main/linux-s390x
poetry-core-1.5.2-py310ha847dfd_0.tar.bz2
poetry-core-1.5.2-py311ha847dfd_0.tar.bz2
poetry-core-1.5.2-py38ha847dfd_0.tar.bz2
poetry-core-1.5.2-py39ha847dfd_0.tar.bz2
https://repo.anaconda.com/pkgs/main/osx-64
poetry-core-1.5.2-py310hecd8cb5_0.tar.bz2
poetry-core-1.5.2-py311hecd8cb5_0.tar.bz2
poetry-core-1.5.2-py38hecd8cb5_0.tar.bz2
poetry-core-1.5.2-py39hecd8cb5_0.tar.bz2
https://repo.anaconda.com/pkgs/main/osx-arm64
poetry-core-1.5.2-py310hca03da5_0.tar.bz2
poetry-core-1.5.2-py311hca03da5_0.tar.bz2
poetry-core-1.5.2-py38hca03da5_0.tar.bz2
poetry-core-1.5.2-py39hca03da5_0.tar.bz2
https://repo.anaconda.com/pkgs/main/win-64
poetry-core-1.5.2-py310haa95532_0.tar.bz2
poetry-core-1.5.2-py311haa95532_0.tar.bz2
poetry-core-1.5.2-py38haa95532_0.tar.bz2
poetry-core-1.5.2-py39haa95532_0.tar.bz2

@JamesRobertsonGames There is an issue with poetry-core 1.5.1 for py312:
14:29:44
    └─ python >=3.12,<3.13.0a0  is not installable because it conflicts with any installable versions previously reported.

But In the logs the host environment has:
    poetry-core:      1.5.1-py312h06a4308_0  defaults
    python:           3.12.3-h996f2a0_0      defaults

This might be why most of the poetry-core dependent packages lock to 1.0.0? That's what I've seen over the last few months

@JamesRobertsonGames the problem is not related to poetry-core.
The following packages are incompatible
├─ pytest-benchmark >=3.4,<4  is installable with the potential options
│  ├─ pytest-benchmark 3.4.1 would require
│  │  └─ python >=3.10,<3.11.0a0 , which can be installed;
│  ├─ pytest-benchmark 3.4.1 would require
│  │  └─ python >=3.11,<3.12.0a0 , which can be installed;
│  ├─ pytest-benchmark 3.4.1 would require
│  │  └─ python >=3.6,<3.7.0a0 , which can be installed;
│  ├─ pytest-benchmark 3.4.1 would require
│  │  └─ python >=3.7,<3.8.0a0 , which can be installed;
│  ├─ pytest-benchmark 3.4.1 would require
│  │  └─ python >=3.8,<3.9.0a0 , which can be installed;
│  └─ pytest-benchmark 3.4.1 would require
│     └─ python >=3.9,<3.10.0a0 , which can be installed;
└─ python >=3.12,<3.13.0a0  is not installable because it conflicts with any installable versions previously reported.


Add dedicationOfAParticularChurch to general.js

dedicationOfAParticularChurch celebration definition should be moved from particular calendars to general.js. It is celebrated on 26 Oct as solemnity in churches of which the date of consecration is unknown.

I'm not sure about moving to general, because this solemnity will overwrite the feria or any other celebration on this day. And this might not be relevant for all church.
And actually, "optional solemnity" doesn't exist in romcal.

After searching a bit on the Internet, you might be right. Even with your implicit suggestion to remove this celebration from romcal (non-parish calendars) altogether. Then, in a separate repo, we could create the modification of romcal for local church calendars (i.e. the diocesan and parish calendars).
Wiki has several celebration definitions in different particular or religious calendars (and on different dates). It even adds the following:

The calendar for a diocese is typically based on a national calendar, such as those listed above, with a few additions. For instance, the anniversary of the dedication of the cathedral is celebrated as a Solemnity in the cathedral church and as a Feast in all the other churches of the diocese. The feast day of the principal Patron saint of the diocese is celebrated as a Feast throughout the diocese. ( General Norms for the Liturgical Year and the Calendar, Table of Liturgical Days according to their order of precedence, 4 and 8.)
The calendar of a parish is based on the calendar of its diocese, but—in addition to the celebrations in the diocesan calendar—there are other celebrations, including the anniversary of the dedication of the parish church and the feast day of the principal Patron saint of the church, both of which are celebrated as Solemnities.

It has just occured to me that we could add a romcal option (like addDedicationOfAParticularChurch) that would add the celebration to the output if set to true (else it would not output it; false by default), because many Ordos (Slovakia, Poland, Canada, etc) are including it. IMO if we want to implement #20, we should want to have all options available in order to be as faithfull as possible.

I still think that using a romcal option (e.g. addDedicationOfAParticularChurch) is the best idea, as it is usually not celebrated at all.
On the other hand, we should merge all dedication_of_consecrated_churches* keys into one dedication_of_consecrated_churches key.

I have just noticed that #431 introduced a potential anomaly.
es and pt-br are the only locale that has dedication_of_consecrated_churches_on_last_sunday_of_october and dedication_of_consecrated_churches_on_october_25 keys localised.
# grep -r dedication_of_consecrated_churches lib/
lib/general-calendar/proper-of-saints.ts:    dedication_of_consecrated_churches_on_october_25: {
lib/general-calendar/proper-of-saints.ts:      customLocaleId: 'dedication_of_consecrated_churches',
lib/general-calendar/proper-of-saints.ts:    dedication_of_consecrated_churches_on_last_sunday_of_october: {
lib/general-calendar/proper-of-saints.ts:      customLocaleId: 'dedication_of_consecrated_churches',
lib/locales/la.ts:    dedication_of_consecrated_churches: 'In Dedicatione Ecclesiæ, cuius dies consecrationis ignotus est',
lib/locales/pl.ts:    dedication_of_consecrated_churches: 'Rocznica poświęcenia kościoła własnego',
lib/locales/cs.ts:    dedication_of_consecrated_churches: 'Výročí posvěcení kostela',
lib/locales/es.ts:    dedication_of_consecrated_churches_on_last_sunday_of_october:
lib/locales/es.ts:    dedication_of_consecrated_churches_on_october_25: 'Dedicación de iglesias consagradas el 25 de octubre',
lib/locales/sk.ts:    dedication_of_consecrated_churches: 'Výročie posviacky chrámov, ktorých deň posviacky nie je známy',
lib/locales/en.ts:    dedication_of_consecrated_churches: 'The Dedication of Consecrated Churches Whose Date of Consecration is Unknown',
lib/locales/pt-br.ts:    dedication_of_consecrated_churches_on_last_sunday_of_october: 'Dedicação de Igrejas Consagradas no Último Domingo de Outubro',
lib/locales/pt-br.ts:    dedication_of_consecrated_churches_on_october_25: 'Dedicação de Igrejas Consagradas em 25 de Outubro',
lib/particular-calendars/slovakia.ts:    dedication_of_consecrated_churches_on_october_25: {
lib/particular-calendars/slovakia.ts:    dedication_of_consecrated_churches_on_last_sunday_of_october: {
lib/particular-calendars/poland.ts:    dedication_of_consecrated_churches_on_october_25: {
lib/particular-calendars/canada.ts:    dedication_of_consecrated_churches_on_october_25: {
lib/particular-calendars/canada.ts:    dedication_of_consecrated_churches_on_last_sunday_of_october: {
lib/catalog/martyrology.ts:    dedication_of_consecrated_churches: {

While those keys are used in some calendars (canada, poland, slovakia), IMHO they are used incorrectly.
grep -r dedication_of_consecrated_churches lib/particular-calendars/ -A2
lib/particular-calendars/slovakia.ts:    dedication_of_consecrated_churches_on_october_25: {
lib/particular-calendars/slovakia.ts-      dateDef: { month: 10, date: 26 },
lib/particular-calendars/slovakia.ts-    },
--
lib/particular-calendars/slovakia.ts:    dedication_of_consecrated_churches_on_last_sunday_of_october: {
lib/particular-calendars/slovakia.ts-      drop: true,
lib/particular-calendars/slovakia.ts-    },
--
lib/particular-calendars/poland.ts:    dedication_of_consecrated_churches_on_october_25: {
lib/particular-calendars/poland.ts-      drop: true,
lib/particular-calendars/poland.ts-    },
--
lib/particular-calendars/canada.ts:    dedication_of_consecrated_churches_on_october_25: {
lib/particular-calendars/canada.ts-      dateDef: { month: 10, date: 22 },
lib/particular-calendars/canada.ts-    },
--
lib/particular-calendars/canada.ts:    dedication_of_consecrated_churches_on_last_sunday_of_october: {
lib/particular-calendars/canada.ts-      drop: true,
lib/particular-calendars/canada.ts-    },

IMHO the correct way to use these keys is the way it is done in proper-of-saints.ts:
$ grep -r dedication_of_consecrated_churches lib/general-calendar/ -A3
lib/general-calendar/proper-of-saints.ts:    dedication_of_consecrated_churches_on_october_25: {
lib/general-calendar/proper-of-saints.ts-      precedence: Precedences.ProperSolemnity_DedicationOfTheOwnChurch_4b,
lib/general-calendar/proper-of-saints.ts:      customLocaleId: 'dedication_of_consecrated_churches',
lib/general-calendar/proper-of-saints.ts-      dateDef: { month: 10, date: 25 },
lib/general-calendar/proper-of-saints.ts-      isOptional: true,
lib/general-calendar/proper-of-saints.ts-    },
--
lib/general-calendar/proper-of-saints.ts:    dedication_of_consecrated_churches_on_last_sunday_of_october: {
lib/general-calendar/proper-of-saints.ts-      precedence: Precedences.ProperSolemnity_DedicationOfTheOwnChurch_4b,
lib/general-calendar/proper-of-saints.ts:      customLocaleId: 'dedication_of_consecrated_churches',
lib/general-calendar/proper-of-saints.ts-      dateDef: { month: 10, lastDayOfWeekInMonth: 0 },
lib/general-calendar/proper-of-saints.ts-      isOptional: true,
lib/general-calendar/proper-of-saints.ts-    },

However, IMHO this celebration should not be defined in the GRC and therefore they should be removed. Then, dedication_of_consecrated_churches_on_* would not be needed to be dropped in the particular calendars.
WDYT, @emagnier? Should we remove the celebration from the GRC? Should we define the celebration in the particular calendars using customLocaleId? Finally, should we remove dedication_of_consecrated_churches_on_* l10n keys from es and pt-br?
I can do it, I just want to hear you opinion first. :pray:

These two elements dedication_of_consecrated_churches_on_october_25 and dedication_of_consecrated_churches_on_last_sunday_of_october are included in the Missal and are part of the general Roman calendar; therefore, their definitions should remain in the calendar.

Which Roman Missal you refer to? AFAIK:

yes, they are part of the Roman Missal in vernacular;
no, they aren’t part of the Latin Roman Missal:

even if I am wrong and they are listed in the Latin Roman Missal, they are not part of the GRC;
as per this comment of mine, I think they should be part only of (generic) national/country calendars and lower calendars (diocesan/parish/church calendars) (when the exact dedication date is unknown), but not of the GRC.

Anyway, If possible, I’d like to see the source where they are both listed in one calendar. :pray:

They are actually the same thing, but since they can be optionally placed on 2 possible dates, they need to be defined twice due to technical limitations in Romcal.

Okay, even if we keep the celebrations defined as they are, IMHO we should have a single l10n key which would be the value of customLocaleId of those celebrations.

The decision to keep either of them, or to entirely remove them, lies with the specific calendars of churches, parishes, or dioceses.

Okay, but have you encountered a particular calendar with more than one date for the unkown church dedications? (Known church dedication dates are always preferred AFAIK.)

Furthermore, both of these definitions have a customLocaleId property, and the value is the same for both. This value (dedication_of_consecrated_churches) corresponds to the translation key to be used by the translation tool (i18next in our case). When the customLocaleId property is not specified, the key of the calendar item is used instead (which is the case most of the time).
TL;DR 1: dedication_of_consecrated_churches_on_october_25 and dedication_of_consecrated_churches_on_last_sunday_of_october will never be used by the translation tool because both of these definitions have a customLocaleId property specifying a different translation key.
TL;DR 2:

dedication_of_consecrated_churches_on_october_25 and dedication_of_consecrated_churches_on_last_sunday_of_october should be removed from the localization files, but kept in the general Roman calendar file.
dedication_of_consecrated_churches should be kept on the localization files.

Okay, I’ll remove the dedication_of_consecrated_churches_on_* l10n keys. Thanks! :pray:

Indeed, you are correct. These celebrations are well indicated in the common of the missal (both in Latin and in vernacular). However, they are not mentioned in the GRC.
It is only suggested for specific countries/diocese on particular dates.
In the third and latest edition of the missal in French (2021), for France, Belgium, and Luxembourg, this celebration is indeed proposed on two possible dates: October 25th or the last Sunday of October.

For example, click here to see an extract from the proper of France.

Good news is that in the work I have done on the 'optimization-ex' branch, it is already possible to integrate these celebrations on a case-by-case basis into particular calendars, without having to redefine them from scratch.
And for your information, I have the latest editions of the missals in Latin and French (in print), as well as Italian (in PDF).

In the third and latest edition of the missal in French (2021), for France, Belgium, and Luxembourg, this celebration is indeed proposed on two possible dates: October 25th or the last Sunday of October.

I presume the two possible dates are because the celebration could be transfered to (usually the nearest/following) Sunday. Yes, the previous Sunday is not an option, but in general, I believe the rules are not that strict. Even in our parish, when the patron saint feast fall on a weekday, it is actually celebrated solemnly during either the previous or the following weekend. I assume the same is the case even for churches with unknown consecration date in French-speaking countries (I can be wrong though).
→ Therefore, my suggestion for the france*.ts calendars is to use dedication_of_consecrated_churches and a single celebration definition per calendar with a n option in the celebration definition which would define whether it should be transferred to the last Sunday of October. YMMV.

And for your information, I have the latest editions of the missals in Latin and French (in print), as well as Italian (in PDF).

Awesome! When you have time and wish to take some pictures of select pages, I want to make them the first-party sources of our l10n data in romcal. OFC, no hurry, as I am currently working on hu.ts, then I want to finally finish #393 (which I need to start again, beginning with taking the very same pictures of mr_sk_2021_ed3, as previously I based my work on Ordo 2023 which differs in some way from mr_sk_2021_ed3). That said, I wish you could contribute this publicly, so that I could publish it on gDrive.
Simply put: I have some much work and tasks (work, family, romcal; and even within romcal) that I need to prioritise and the tasks in order. Hopefully, I can devote more time to romcal in the upcoming months, as I have some ideas (even regarding the monorepo, but more on that later).

I'm on board with keeping only one of the two definitions of celebrations in the particular calendars I mentioned above. Then, it's up to a sub proper calendar (under france-*) to transfer or remove that date if necessary.
Following this logic through, we should remove this celebration from the GRC.

Following this logic through, we should remove this celebration from the GRC.

I believe that is the correct way, as the pure GRC is nowhere used, it is just a base calendar from which derive all the others.


Can't create project/function without internet

Repro steps:

With wifi on, create  project/function (to make sure that the templates get cached)
Turn wifi off
Restart VS Code
Create a project or function

Expected:
Success (we should use the cached templates)
Actual:
Action: azureFunctions.createFunction
Error type: RequestError
Error Message: Error: getaddrinfo ENOTFOUND aka.ms aka.ms:443
Version: 0.9.0
OS: darwin

Fixed in https://github.com/Microsoft/vscode-azurefunctions/pull/373


Binary version of Scala.js turned to "1", not "1.0" as of version 1.0.0

This leads to errors when retrieving artifacts in the form of eg.:
Could not resolve dependency slinky-core_sjs1.0_2.13 in me.shadaj
Mill had to change some hardoded cases, which I guess is the case for seed too?

Thanks for the bug report! I have merged a fix. Feel free to try it with the latest pre-release.
Please note that Seed does not officially support Scala.js v1.0 modules yet because Bloop v1.3.2 cannot link them. Once the next stable Bloop version has been released, I am hoping to add integration tests.

Great! I did a smaller more hackish workaround in seed on my local machine, but I ran into the bloop issue, so I didn't think it merited a pull request.


Update bot.py

details in #601 issue

Codecov Report

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

@@            Coverage Diff             @@
##           master     #603      +/-   ##
==========================================
+ Coverage   38.22%   38.25%   +0.02%
==========================================
  Files          26       26
  Lines        2174     2175       +1
==========================================
+ Hits          831      832       +1
  Misses       1343     1343

Impacted Files
Coverage Δ

instabot/bot/bot.py
62.53% <100%> (+0.11%)
:arrow_up:

Continue to review full report at Codecov.

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

Just the user_id does not identify the post, you should also include the media_id

Could you also not use camelCase?

I think that @basnijholt means that you need the media_id to not like again the same post. Am I right @basnijholt ?
Or @lukasz00500 do you want to simply not like anymore the users at all? I think is better to not like again the same post than stop liking the user forever.

i want to not like this user anymore -  This is useful when using the function:
like_user_followers
like_user_following
and you cant like all users in one bot session, you do not want to like the same users next day right ?

@lukasz00500 Thank you for the pull request! You have done a great job!
Please fix your code style according to Python Standards (pep 8) to pass Travis code style tests. Also please add tests that covers your code improvements (this is not obligable).

i just added this function because for now this bot is not checking if user is in liked.txt or skipped.txt before request to Instagram api. Scanning of this list should performed before downloading any data from user

The code is obsolete, bug has been fixed in new version


you are stupid and should be ashamed

if i did some searching or maybe if i paid any attention when doing the optics chapter i'd know that
(distance to object / focal length) = (size of object / size of the image of the object)

and that can be rearranged to
size of image of object = size of object * focal length / distance to object

and then if you know the cameras sensor size and its resolution then you can work out the image size in pixels.
no need to use polynomial functions to try and model this stuff

no u


Add a warning about try-with-resource to auto-close spans.

Fixes https://github.com/census-instrumentation/opencensus-java/issues/646
Thanks @adriancole for reporting this a while ago.

Codecov Report

Merging #1362 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##             master   #1362   +/-   ##
========================================
  Coverage      83.2%   83.2%
  Complexity     1393    1393
========================================
  Files           221     221
  Lines          6586    6586
  Branches        620     620
========================================
  Hits           5480    5480
  Misses          930     930
  Partials        176     176

Impacted Files
Coverage Δ
Complexity Δ

...src/main/java/io/opencensus/trace/SpanBuilder.java
94.44% <ø> (ø)
4 <0> (ø)
: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 b0c487b...171f650. Read the comment docs.


296 - migrate keycloak

Started implementing this via the JSON Alec added to 1pass though currently I'm blocked by my lack of IDIR.

@matthieu-foucault this is ready for re-review.