Implementing Rrule package

New Pull Request for #400, related to #298
Currently working in example:

[x] can build daily or weekly recurring events.
[x] can build monthly or yearly events.
[x] can build complex (eg. multi days a week) events.
[x] can delete all events in the chain.
[x] can delete single events.
[x] can delete this and following instances

Hurdles (all should be solved before merge):

[x] rrule changes are published.
[x] most features are working / non-working features hidden and labeled.
[x] re-enable lower API support (full or partial), or document why they should be dropped.

Hmm, it doesn't fix git tracing as good as I hoped
I'm trying the old-fashioned way, cherrypicking each commits and resolving stuff.

Sorry all this merging and conflict solving had me a bit confused...
I added two more commits as it seems that it wasn't pushed correctly yesterday.

@GoldenSoju I can only get some of the features working right now. Is this intended?

@thomassth no, not at all intended.
(My working version branch)[https://github.com/GoldenSoju/device_calendar/tree/develop_rrule] works fine...
Let me try to compare my working branch and this branch to see what went missing during the merge.

I've added a checklist to the top.
Feel free to add lines and check items that are done.
(Do you think we need a separate checklist for android and iOS?)

I think you have pulled all of the changes bar some dependency updates.
Maybe it's the example 's problem?
https://github.com/GoldenSoju/device_calendar/compare/GoldenSoju:develop_rrule...fast_merge_develop_rrule

Hm just some minor corrections were needed but now it should work fine.
I also had to correct something in my version of the Rrule package, I guess that was the main bug for the monthly and yearly recurrences to fail.
Deletion also seems to work fine.

Some bugs in current build:
Weekdays/weekends seems fixed
“first Monday of Jan, yearly” also includes all Mondays of current January, similar things on monthly (every month becomes every week)
“Every 2 years” not working
I think I’m going to write some tests.

Hm it works on my side (testing mainly with google calendar).
Can you please try again after flutter clean and flutter pub get ? Maybe you don't have the newest version of the Rrule dependency.
Also in the example app, file calendar_events.dart you might want to change line 135 to something with a bigger end date.
Sth like final endDate = DateTime.now().add(Duration(days: 365 * 4));.
Atm it only catches events from -/+ 30 days.

I'll try later today.
Either way your rrule package need to be merged to the main branch first.
If you think it's ready go submit a PR.

I just submitted the pull request for the rrule package.

@thomassth
The Rrule package supports now JSON(iCAL format) and I applied the changes to the Flutter and Android part.
I will start working on the iOS part today/tomorrow.
If you want to check, I commited the newest changes to this branch

@thomassth
iOS implementation is also finished.
I tested daily/weekly/monthly and yearly recurrences and it seems all to work and the resulting recurrence rule strings also are all correct as far as I've seen. Therefore I think Android/iOS parts are fine, while minor errors might occur due to the example app (add event page).

@thomassth
Ok I also merged all outstanding commits from the main branch into this one. So it is up to date.
I got everything working so far, except All Day events in the example app. Haven't figured out yet how to solve the problem though.

@thomassth
Hi!
I implemented the device_calendar package with rrule package in one of my projects and found some shortcomings in the previous pull requests.
The newest version fixes those problems and the example is also now working correctly (there are no specified tests yet, but so far manual testing works fine on Android and iOS).
The only functionality still missing at the moment would be multi-all-day-events (with or without recurrence) on iOS, but I saw there was another pull request/discussion for that problem.
Please check the newest version if you have time.

After rebase, I can confirm all these are working with rrule on android. But they need to be tested on iOS:
(use the delete button within the details page)

[ ] can build daily or weekly recurring events.
[ ] can build monthly or yearly events.
[ ] can build complex (eg. multi days a week) events.
[ ] can delete all events in the chain.
[ ] can delete single events.
[ ] can delete this and following instances

Also needs to check if it overwrites other PRs, since this is quite beefy

@thomassth
I checked on iOS, below all points work without problems.

[x]  can build daily or weekly recurring events.
[x]  can build monthly or yearly events.
[x]  can build complex (eg. multi days a week) events.
[x]  can delete all events in the chain.
[x]  can delete single events.
[x]  can delete this and following instances

Also all tests were passed on iOS.

Also needs to check if it overwrites other PRs, since this is quite beefy
Especially https://github.com/builttoroam/device_calendar/pull/410

Seems like your latest commits reflect all changes made in develop branch of builttoroam/device_calendar. All seems to be up-to-date according to comparison.

Great!
One last thing, @GoldenSoju are you participating in Hacktoberfest? I can add the tag in

@thomassth

Great!
One last thing, @GoldenSoju are you participating in Hacktoberfest? I can add the tag in

Thanks for asking, that would be nice! :)


Blog post LUKS performance impact

Add blog post "Performance impact of disk encryption using LUKS"
Add ppkuschy community member profile
Signed-off-by: Paul-Philipp Kuschy<EMAIL_ADDRESS>

Closes https://github.com/osism/issues/issues/368

Wow, this blog post looks really awesome. Have a look at the staging preview: https://sovereigncloudstack.github.io/website/2023/02/24/impact-of-disk-encryption/
From a technical standpoint, this looks good to me. I'll let @fkr have a look at the content though.


Refactor the don't-hardcode-urls branch

PR is now properly merging into 73-dont-hardcode-urls rather than master.

Next step is to verify if the Bitcoin Core tor service is running right now.

Converted to draft until I find and test the correct .onion address.

Next step is to verify if the Bitcoin Core tor service is running right now.

It's not:
https://github.com/bitcoin-core/bitcoincore.org/issues/985
Lets swap the order of the attempts until the issue closes.

Lets swap the order of the attempts until the issue closes.
Resolved with https://github.com/BenWestgate/Bails/pull/94/commits/8ac8b39079e727460c90ab57c0b9157f521c8aea

Passed my manual testing.
Due to rebasing against master, shellcheck is now being enforced.
Will address lint issues then re-test.

Rebased and resolved conflicts.

Fixed lint issues. Need to retest and resolve open review comments.


Setting initial polling offset

Would it be possible to set the initial poling offset at startup?
I would really like to be able to store the last processed message id in a database and ensure that I don't miss any messages that come in during down time.
If you want, I could probably figure it out and submit a pull request, if I can find the time.

I believe you can set the offset variable.
See: https://core.telegram.org/bots/api#getupdates

By default the offset value is null, so Telegram will send all unconfirmed msgs.
"By default, updates starting with the earliest unconfirmed update are returned."

This feature has been added in v0.27.0. See the constructor option, options.polling.params.
You would do sth like:
const bot = new TelegramBot(TOKEN, {
  polling: {
    params: {
      offset: getOffsetSomeHow(), // we shall start polling with this value!
    },
  },
});

Thanks @Onfire7 and @Illyism for your time and effort in adding this feature.

@GochoMugo I did it with you said but not work.what is the problem?


glz::read format glz::csv infinite loop and memory exhaustion

reading csv with invalid file format is causing infinite loop and when last column is string also memory exhaustion without issues reported from asan or ubsan. Expected by me would be getting syntax error with invalid files.
struct glaze_test_struct_t
  {
  std::vector<int> num1{};
  std::vector<std::string> str1{};
  };
constexpr std::string_view invalid_record_1 =
  R"(num1,str1
11,Warszawa
33,Krakow,some text,
55,Gdynia
77,Reda)";

constexpr std::string_view invalid_record_2 =
  R"(num1,str1
11,Warszawa
33,Krakow,some text
55,Gdynia
77,Reda)";
static void test_galze_internal()
  {

  "glz invalid_record_1"_test = []
  {
    glz::context ctx{};
    glaze_test_struct_t value;
    glz::parse_error glaze_err{
      glz::read<glz::opts{.format = glz::csv, .layout = glz::colwise}>(value, std::string{invalid_record_1}, ctx)
    };
    ut::expect(bool(glaze_err));
  };

  "glz invalid_record_2"_test = []
  {
    glz::context ctx{};
    glaze_test_struct_t value;
    glz::parse_error glaze_err{
      glz::read<glz::opts{.format = glz::csv, .layout = glz::colwise}>(value, std::string{invalid_record_2}, ctx)
    };
    ut::expect(bool(glaze_err));
  };
  }

Thanks for pointing out this bug. Will work on fixing it.

The problem is  in logic here
Instead of verification and expecting end of line You are testing for end of line and if that not happens row is not incremented and another set of keys is read from completely wrong position
for csv those conditionals maybe should be changed to expectations and report failure ..

Yep this fixes code and tests for me maybe not efficient but correct

This would be more efficient.

PR or You want to fix it Yourself ?

It will probably be fixed faster if you're able to issue a PR

ok, I will work on it.

Fixed in #771


update stats

Motivation
New endpoints to modify user stats
Summary of changes

Added new /stats endpoints
GET /addWin
GET /addLoss
POST /updateRating -> request body { ratingDifferential: 26 } // can be a possitive number to add rating or a negative number to substract it
Connected wins and losses endpoints to frontend (Rating system is not implemented yet)

Checklist

[x] Tested the changes locally.
[x] Reviewed the changes on GitHub, line by line.
[ ] Unit tests added.
[x] This change requires new documentation.

[x] Documentation has been added/updated.

***user stats are visible in /profile

those endpoints should be "PUT" , not "GET" or "POST"


i cant install mythril (urgent please respond fast)

error: subprocess-exited-with-error
× Building wheel for blake2b-py (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [48 lines of output]
Running maturin pep517 build-wheel -i /usr/bin/python3 --compatibility off
⚠  Warning: Please use maturin in pyproject.toml with a version constraint, e.g. requires = ["maturin>=0.13,<0.14"]. This will become an error.
Compiling proc-macro2 v1.0.43
Compiling unicode-ident v1.0.4
Compiling quote v1.0.21
Compiling syn v1.0.100
Compiling proc-macro-hack v0.5.19
Compiling memchr v2.5.0
Compiling serde_derive v1.0.145
Compiling serde v1.0.145
Compiling serde_json v1.0.85
Compiling regex-syntax v0.6.27
Compiling ryu v1.0.11
Compiling autocfg v1.1.0
Compiling itoa v1.0.3
Compiling lazy_static v1.4.0
Compiling unindent v0.1.10
Compiling libc v0.2.133
Compiling version_check v0.9.4
Compiling inventory v0.1.11
Compiling spin v0.5.2
Compiling num-traits v0.2.15
Compiling aho-corasick v0.7.19
Compiling paste-impl v0.1.18
Compiling regex v1.6.0
Compiling paste v0.1.18
Compiling pyo3-derive-backend v0.8.5
Compiling ghost v0.1.6
Compiling inventory-impl v0.1.11
Compiling ctor v0.1.23
Compiling indoc-impl v0.3.6
Compiling pyo3cls v0.8.5
Compiling indoc v0.3.6
Compiling pyo3 v0.8.5
error: failed to run custom build command for pyo3 v0.8.5
  Caused by:
    process didn't exit successfully: `/tmp/pip-install-n6zvbcia/blake2b-py_9ed9b4adc94c4309b3180b370b3e1766/target/release/build/pyo3-a52f5be9adf5b73b/build-script-build` (exit status: 101)
    --- stderr
    thread 'main' panicked at 'Error: pyo3 requires a nightly or dev version of Rust.', /root/.cargo/registry/src/github.com-1ecc6299db9ec823/pyo3-0.8.5/build.rs:542:9
    note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
  💥 maturin failed
    Caused by: Failed to build a native library through cargo
    Caused by: Cargo build finished with "exit status: 101": `"cargo" "rustc" "--release" "--message-format" "json" "--lib"`
  🍹 Building a mixed python/rust project
  🔗 Found pyo3 bindings
  🐍 Found CPython 3.10 at /usr/bin/python3
  Error: command ['maturin', 'pep517', 'build-wheel', '-i', '/usr/bin/python3', '--compatibility', 'off'] returned non-zero exit status 1
  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for blake2b-py
Failed to build blake2b-py
ERROR: Could not build wheels for blake2b-py, which is required to install pyproject.toml-based projects

Hi, just switch to using python 3.9, it should work

Im using latest version of ubuntu and i uses python 3.10
I couldnt switch to 3.9
Any advice on that ?

A virtual environment to python 3.9, or use the docker container


Why the Gated CNN Blocks are not 24 layers？

I think its necessary to set 24 layers of MambaOut in memory of Kobe Bryant.

They can also set 8 layers, but they did not either. Man!

They can also set 8 layers, but they did not either. Man!

its worth discussing and i think its necessary to reproduce the code and change the layers to test result.

It will be a meaningful work!

就你这个issue显得格格不入。伟大无需多言！

《changed the title 什么罐头我说？ Why the Gated CNN Blocks are not 24 layers？》hhhhhh

Thank you so much for your suggestion. We released MambaOut-Kobe model, a Kobe Memorial version with 24 Gated CNN blocks. MambaOut-Kobe achieves really competitive performance, surpassing ResNet-50 and ViT-S with much fewer parameters and FLOPs. For example, MambaOut-Kobe outperforms ResNet-50 by 0.2% accuracy with only 36% parameters and MACs.

Model
Resolution
Params
MACs
Top1 Acc

ResNet-50
224
25.5M
4.1G
79.8*

ViT-S
224
22.1M
4.6G
79.8

MambaOut-Kobe
224
9.1M
1.5G
80.0

The result is cited from "ResNet strikes back" paper, a very strong version of ResNet trained for 300 epochs.

Thank you so much for your suggestion. We released MambaOut-Kobe model, a Kobe Memorial version with 24 Gated CNN blocks. MambaOut-Kobe achieves really competitive performance, surpassing ResNet-50 and ViT-S with much fewer parameters and FLOPs. For example, MambaOut-Kobe outperforms ResNet-50 by 0.2% accuracy with only 36% parameters and MACs.
Model	Resolution	Params	MACs	Top1 Acc
ResNet-50	224	25.5M	4.1G	79.8*
ViT-S	224	22.1M	4.6G	79.8
MambaOut-Kobe	224	9.1M	1.5G	80.0

The result is cited from "ResNet strikes back" paper, a very strong version of ResNet trained for 300 epochs.

Man! Hahahaha

Thank you so much for your suggestion. We released MambaOut-Kobe model, a Kobe Memorial version with 24 Gated CNN blocks. MambaOut-Kobe achieves really competitive performance, surpassing ResNet-50 and ViT-S with much fewer parameters and FLOPs. For example, MambaOut-Kobe outperforms ResNet-50 by 0.2% accuracy with only 36% parameters and MACs.
Model	Resolution	Params	MACs	Top1 Acc
ResNet-50	224	25.5M	4.1G	79.8*
ViT-S	224	22.1M	4.6G	79.8
MambaOut-Kobe	224	9.1M	1.5G	80.0

The result is cited from "ResNet strikes back" paper, a very strong version of ResNet trained for 300 epochs.

its a meaning work, what can i say?

Thank you so much for your suggestion. We released MambaOut-Kobe model, a Kobe Memorial version with 24 Gated CNN blocks. MambaOut-Kobe achieves really competitive performance, surpassing ResNet-50 and ViT-S with much fewer parameters and FLOPs. For example, MambaOut-Kobe outperforms ViT-S by 0.2% accuracy with only 41% parameters and 33% FLOPs.
Model	Resolution	Params	MACs	Top1 Acc
ResNet-50
(ResNet strikes back)	224	25.5M	4.1G	79.8
ViT-S	224	22.1M	4.6G	79.8
MambaOut-Kobe	224	9.1M	1.5G	80.0

omg love work 🤣

What a great suggestion!


Update dockerfile with dvc dependency

Summary of changes
Changes introduced in this pull request:
Reference issue to close (if applicable)

Closes

Codecov Report

Merging #252 (05ce1ac) into main (c204b33) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #252   +/-   ##
=======================================
  Coverage   78.60%   78.60%
=======================================
  Files          74       74
  Lines        4660     4660
=======================================
  Hits         3663     3663
  Misses        997      997

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


Run Mailpit tests (Mua) by default

Context: https://github.com/swoosh/swoosh/pull/982

Or maybe it can be a separate job/test/etc.?


Memory RAM of pp parallel process gradually increases, till Out-of-Mem

RAM usage by the parallel pp thread increases over time and later blows up (eg 20-40GBs 2-4h later), when using a virtual env with the below library versions:
python 2.7.12 (gcc 5.4)
numpy 1.16.0
nibabel 2.3.3
pp 1.6.5
tensorflow 1.12.0
Stable environent without such problems (Normal RAM usage by pp is 4-8 GBs when sampling):
python 2.7.12 (gcc 5.4)
numpy 1.14.3
nibabel 2.2.1
pp 1.6.5
tensorflow 1.8.0
I am expecting the problem is in some latest version of nibabel, eg not releasing memory of the loaded volumes similarly to previous ones. I need time to investigate.
Until then, if you run into memory issues, try downgrading the versions of the libraries towards the above.
(
You can identify it's this issue by using htop.
There will be two processes when dm is running:

The main one, which should take ~4GBs.
A secondary -pp thread, which is the parallel process that samples patches from the input volumes. This should fluctuate normally between 4-8 GBs. If this issue is present, over time, usage of this thread should built up upwards, until memory gets filled and the process dies.
)

After changed released with v0.7.1, which has replaced pp with multiprocessing, I have not re-encountered this problem of memory usage pilling up. RAM usage of default DM with 2 parallel processes is between 8-14 GBs usually (depending on how many modalities in the database).
Tests run with:
Python 3.5.2
Tensorflow 1.12.0
nibabel 2.3.3
numpy 1.16.1
(same libraries, but using Python 2.7.12 was also fine.)
I will close this.


Add a progress bar

https://github.com/a-luna/console-progress-bar
Would be an optional --progress command.
Will require some reworking to be able to enumerate without extracting. Perhaps a separate API?

Won't fix.


Generate a pom.xml

@briandealwis @patflynn
fix #131

I only gave a very cursory look, but this looks like creating a Maven archetype project.  Rather than reinvent that wheel,  I think we should have different streams for creating a new project:

Create a native new WTP AppEngine project, with appropriate facets.  This is pretty much the path you're following right now, though it should be transitioned to using faceted projects, and I realize that some of the code generation you're doing should be transitioned into facet actions instead.
Create a new Maven AppEngine project

This should hook into the M2Eclipse support and creates a project using the appropriate archetype
Using the new Maven Project wizard is painful as it seemingly doesn't come configured out of the box to use the Maven Central Archetype Catalog, which is baffling
and there are several appengine archetypes and it's not clear which is the right one, so there's definite value here

Create a new Gradle AppEngine project

This PR isn't the final build system. The team asked me to throw in a quick pom.xml so we could have a CLI build in place for now. #134 and #118 are about getting more of this working inside Eclipse. I think we're leaning against making the build inside Eclipse maven based, though that could change with a strong enough case in favor or maven. If we do go all the way down the maven road, we'll need to understand how changes in the pom.xml sync back into the Eclipse build.
One question about facets: do these indeed work in regular Eclipse for Java? I.e. not Eclipse for Java EE? From what I'm reading they seem like an EE thing.
Gradle we're still discussing in #132. How much do you think Eclipse developers use Gradle? Our impression is that it's more common in the IntelliJ space, but it's easy enough to add a build.gradle file in addition to the pom and everything else.

LGTM

One question about facets: do these indeed work in regular Eclipse for Java? I.e. not Eclipse for Java EE? From what I'm reading they seem like an EE thing.

Faceted Projects are a WTP feature; they never migrated further into the platform.  They're almost equivalent to natures, but natures don't have the ability to place constraints like pre-reqs and anti-reqs.  There's nothing preventing using a faceted project for a Java project, but I guess it's rare for non-WTP projects to mix different languages and libraries.


Cannot connect to plug after latest Homebridge update

Describe The Bug
I have just updated Homebridge on PI to v1.6.0 and node.js to v18.13.0
The previously working connection to TP-Link 110 plug now returns:
Failed to get info about: <IP_ADDRESS> | The first argument must be of type string or an instance of Buffer, ArrayBuffer, or Array or an Array-like Object. Received undefined
Expected behavior
Connecting as before with no errors
Logs
Error sending command: deviceInfo AxiosError: connect EHOSTUNREACH <IP_ADDRESS>:80
at Function.AxiosError.from (/var/lib/homebridge/node_modules/homebridge-tp-link-tapo/node_modules/axios/lib/core/AxiosError.js:89:14)
at RedirectableRequest.handleRequestError (/var/lib/homebridge/node_modules/homebridge-tp-link-tapo/node_modules/axios/lib/adapters/http.js:533:25)
at RedirectableRequest.emit (node:events:513:28)
at ClientRequest.eventHandlers. (/var/lib/homebridge/node_modules/homebridge-tp-link-tapo/node_modules/follow-redirects/index.js:14:24)
at ClientRequest.emit (node:events:513:28)
at Socket.socketErrorListener (node:_http_client:496:9)
at Socket.emit (node:events:513:28)
at emitErrorNT (node:internal/streams/destroy:151:8)
at emitErrorCloseNT (node:internal/streams/destroy:116:3)
at processTicksAndRejections (node:internal/process/task_queues:82:21) {
port: 80,
address: '<IP_ADDRESS>',
syscall: 'connect',
code: 'EHOSTUNREACH',
errno: -113,
config: {
transitional: {
silentJSONParsing: true,
forcedJSONParsing: true,
clarifyTimeoutError: false
},
adapter: [ 'xhr', 'http' ],
transformRequest: [ [Function: transformRequest] ],
transformResponse: [ [Function: transformResponse] ],
timeout: 0,
xsrfCookieName: 'XSRF-TOKEN',
xsrfHeaderName: 'X-XSRF-TOKEN',
maxContentLength: -1,
maxBodyLength: -1,
env: { FormData: [Function], Blob: [class Blob] },
validateStatus: [Function: validateStatus],
headers: AxiosHeaders {
Accept: 'application/json, text/plain, /',
'Content-Type': 'application/json',
'User-Agent': 'axios/1.2.2',
'Content-Length': '352',
'Accept-Encoding': 'gzip, compress, deflate, br'
},
method: 'post',
url: 'http://<IP_ADDRESS>/app',
data: '{"method":"handshake","params":{"key":"-----BEGIN PUBLIC KEY-----\nMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQD8XhXr4scHW9S2Y9TOF2gZlq73\nipHPI4s5gwyv8rfZerWUIfbGvzL+BnOcjyFpvIkH5zS6h7+d4LtDiRDOuhwElrV3\nJOyuixyk/Eiah6BRK32ZU0GE8rZpk+QwN6BSNCgR5pYpoQ5qBLmSk2T/bF/3jGM5\nEIsHZTDz2yer+O1wFwIDAQAB\n-----END PUBLIC KEY-----\n"},"requestTimeMils":1674215209914}'
},
request: <ref *1> Writable {
_writableState: WritableState {
objectMode: false,
highWaterMark: 16384,
finalCalled: false,
needDrain: false,
ending: false,
ended: false,
finished: false,
destroyed: false,
decodeStrings: true,
defaultEncoding: 'utf8',
length: 0,
writing: false,
corked: 0,
sync: true,
bufferProcessing: false,
onwrite: [Function: bound onwrite],
writecb: null,
writelen: 0,
afterWriteTickInfo: null,
buffered: [],
bufferedIndex: 0,
allBuffers: true,
allNoop: true,
pendingcb: 0,
constructed: true,
prefinished: false,
errorEmitted: false,
emitClose: true,
autoDestroy: true,
errored: null,
closed: false,
closeEmitted: false,
[Symbol(kOnFinished)]: []
},
_events: [Object: null prototype] {
response: [Function: handleResponse],
error: [Function: handleRequestError],
socket: [Function: handleRequestSocket]
},
_eventsCount: 3,
_maxListeners: undefined,
_options: {
maxRedirects: 21,
maxBodyLength: Infinity,
protocol: 'http:',
path: '/app',
method: 'POST',
headers: [Object: null prototype],
agents: [Object],
auth: undefined,
beforeRedirect: [Function: dispatchBeforeRedirect],
beforeRedirects: [Object],
hostname: '<IP_ADDRESS>',
port: '',
agent: undefined,
nativeProtocols: [Object],
pathname: '/app'
},
_ended: false,
_ending: true,
_redirectCount: 0,
_redirects: [],
_requestBodyLength: 352,
_requestBodyBuffers: [ [Object] ],
_onNativeResponse: [Function (anonymous)],
_currentRequest: ClientRequest {
_events: [Object: null prototype],
_eventsCount: 7,
_maxListeners: undefined,
outputData: [],
outputSize: 0,
writable: true,
destroyed: false,
_last: true,
chunkedEncoding: false,
shouldKeepAlive: false,
maxRequestsOnConnectionReached: false,
_defaultKeepAlive: true,
useChunkedEncodingByDefault: true,
sendDate: false,
_removedConnection: false,
_removedContLen: false,
_removedTE: false,
strictContentLength: false,
_contentLength: '352',
_hasBody: true,
_trailer: '',
finished: false,
_headerSent: true,
_closed: false,
socket: [Socket],
_header: 'POST /app HTTP/1.1\r\n' +
'Accept: application/json, text/plain, /\r\n' +
'Content-Type: application/json\r\n' +
'User-Agent: axios/1.2.2\r\n' +
'Content-Length: 352\r\n' +
'Accept-Encoding: gzip, compress, deflate, br\r\n' +
'Host: <IP_ADDRESS>\r\n' +
'Connection: close\r\n' +
'\r\n',
_keepAliveTimeout: 0,
_onPendingData: [Function: nop],
agent: [Agent],
socketPath: undefined,
method: 'POST',
maxHeaderSize: undefined,
insecureHTTPParser: undefined,
path: '/app',
_ended: false,
res: null,
aborted: false,
timeoutCb: null,
upgradeOrConnect: false,
parser: null,
maxHeadersCount: null,
reusedSocket: false,
host: '<IP_ADDRESS>',
protocol: 'http:',
_redirectable: [Circular *1],
[Symbol(kCapture)]: false,
[Symbol(kBytesWritten)]: 0,
[Symbol(kEndCalled)]: false,
[Symbol(kNeedDrain)]: false,
[Symbol(corked)]: 0,
[Symbol(kOutHeaders)]: [Object: null prototype],
[Symbol(errored)]: null,
[Symbol(kUniqueHeaders)]: null
},
_currentUrl: 'http://<IP_ADDRESS>/app',
[Symbol(kCapture)]: false
},
cause: Error: connect EHOSTUNREACH <IP_ADDRESS>:80
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1487:16) {
errno: -113,
code: 'EHOSTUNREACH',
syscall: 'connect',
address: '<IP_ADDRESS>',
port: 80
}
}
Plugin Config
{
"addresses": [
"<IP_ADDRESS>"
],
"name": "Study Plug",
"email": "XXXXXXXX",
"password": "XXXXXXXX",
"platform": "HomebridgeTPLinkTapo"
}
Plugin Version
3.2.2
Homebridge Version
1.6.0
Node.js Version
18.13.0
NPM Version
7.5.2
Operating System
Raspbian GNU/Linux 11 (bullseye)

Hey, the error suggests an issue with the device, try the following:

Un plug an replug the device
Re pair the device
Change account password
Create a new account and pair the devices there

That worked perfectly. Thank you for your help and for being so quick.

Anytime! Glad it works!


[BUG]: Non-descriptive error message from drizzle-kit up

What version of drizzle-orm are you using?
v0.29.4
What version of drizzle-kit are you using?
v0.20.14
Describe the Bug
> drizzle-kit up:pg --config=./drizzle.config.ts

drizzle-kit: v0.20.14
drizzle-orm: v0.29.4

Reading config file '.../server/drizzle.config.ts'
Everything's fine 🐶🔥

Can't really give you more than that since the error is not very descriptive. I'm not necessarily asking for help on this specific issue, but maybe propagate errors to to the console, making these thing are easier to debug.
Expected behavior
No response
Environment & setup
No response

I don't believe this is an error; per the documentation drizzle-kit up:{dialect} is a utility command to keep all metadata up to date..
And glancing at the source-code it will print Everything's fine 🐶🔥 regardless of success.


Enhancement: Removal of DWriteCore traces in User folder.

The distributed DWriteCore (DWrite.dll) component creates the directory "DWriteCore" inside of;

XP and below: "C:\Documents and Settings\%USERNAME%\Local Settings\Application Data"
Vista and higher: "C:\Users\%USERNAME%\AppData\Local"

only containing the "FontSet-v3.dat" file.
Directory and file appear to be useless and can be deleted, even during runtime, without triggering a "file in use" error. Directory and file do not get regenerated until the next restart of Supermium.
I'd like to propose the prevention of the creation of said directory and file as they seem to serve no purpose, cause unnecessary writes and just clutter up the Users folder structure.

In my case it actually creates in C:\ which is even more annoying

@zdland
Now that's odd, I can't reproduce that at all. What Windows are you using?

I don't want to remove the font cache altogether, but I can move it to the Supermium folder.

@win32ss
Hold on, that's supposed to be cache? How come it's only generated once per startup and then, seemingly, never used? I've never even seen it increase in size.
But if keeping it has some benefit/functionality, then that's okay too. As long as it is modified to be inside of Supermiums program folder instead, as it appears to somehow generate in other places for other Users.

@zdland
Now that's odd, I can't reproduce that at all. What Windows are you using?

It may be related to the installation (all users or current user), rather than the operating system. I'm using Windows 2003


Add smart insert

Hi @dpeter99 - something you'd like me to review / merge? or should we close it out?

Ohh kinda forgot about this. Yeah we can close it, might re-open when I have time to make it more configurable.

Closed out for now. Thanks!


Roadmap

Is there a Roadmap for Files?  I'd hate to submit requests only to get back -- it's already on the roadmap but hasn't been implemented yet.  Or worse, it's there but I haven't discovered it.
For what its worth I really miss the Quick access list from Windows 7 File Manager.  I really like the clarity of relying on Drives and Folders as the chief organizing metaphor. MS has managed to mangle that completely in the evolution of File Manager.
Thanks for this effort,
Max

Hi @MaxYaffe you can refer to Github issues or the project board to know what it's currently planned or being worked on.
For example a search for "quick access" leads to issue #2322 which sounds like what you are requesting here.
The "triage approved" label means that a feature request is on the roadmap but hasn't been implemented yet.

@MaxYaffe As @gave92 said, you can check the project board to see what's already been approved. If you don't see an issue for a feature you would like added, make sure to open a proposal so that we can review/add it to the plans 😃.


Add support for DA2 and DA3 device attributes reports

Summary of the Pull Request
This PR adds support for the DA2 (Secondary Device Attributes) and DA3 (Tertiary Device Attributes) escape sequences, which are standard VT queries reporting basic information about the terminal.
PR Checklist

[x] Closes #5836
[x] CLA signed.
[x] Tests added/passed
[ ] Documentation updated. If checked, please file a pull request on our docs repo and link it here: #xxx
[ ] Schema updated.
[ ] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx

Detailed Description of the Pull Request / Additional comments
The Secondary Device Attributes response is made up of a number of parameters:

An identification code, for which I've used 0 to indicate that we have the capabilities of a VT100 (using code 0 for this is an XTerm convention, since technically DA2 would not have been supported by a VT100).
A firmware revision level, which some terminal emulators use to report their actual version number, but I thought it best we just hardcode a value of 10 (the DEC convention for 1.0).
Additional hardware options, which tend to be device specific, but I've followed the convention of the later DEC terminals using 1 to indicate the presence of a PC keyboard.

The Tertiary Device Attributes response was originally used to provide a unique terminal identification code, and which some terminal emulators use as a way to identify themselves. However, I think that's information we'd probably prefer not to reveal, so I've followed the more common practice of returning all zeros for the ID.
In terms of implementation, the only complication was the need to add an additional code path in the OutputStateMachine to handle the > and = intermediates (technically private parameter prefixes) that these sequences require. I've done this as a single method - rather than one for each prefix - since I think that makes the code easier to follow.
Validation Steps Performed
I've added output engine tests to make sure the sequences are dispatched correctly, and adapter tests to confirm that they are returning the responses we expect. I've also manually confirmed that they pass the Test of terminal reports in Vttest.

For the record, I'm happy to consider returning a genuine version number in DA2 and some kind of ID in DA3 if that's preferable, but I thought we'd probably want to remain essentially anonymous. For more info on how these sequences are implemented and used, see issue https://github.com/microsoft/terminal/issues/5836#issuecomment-648204837.

So, it looks like xterm (344) responds to DA2 as a "VT420", firmware version "344", 0 (^[[>41;344;0c) in the default configu shipped with Debian buster.
I know that Vim, as an example, uses the xterm version, but I don't know if it uses DA2 or \e[>0q to do so.
For what it's worth, I can't get that build of xterm to respond to \e[>0q, and vim fails to autodetect it ... :smile: so I'm guessing it doesn't use DA2.
Regardless; how much should we pretend to be xterm and how much should we not? Open question!

I do like the idea of remaining anonymous; I don't want people taking dependencies (like vim has done with xterm) on our implementation details especially when they change so rapidly in Terminal (and so slowly in Windows).
There's also no stable version number that we can use across Windows conhost and OpenConsole that would be monotonically increasing such that an application could rely on it.

I see now that you literally covered everything I just said, in the comment I opened to "read after I wrote my comments". Sorry. 😬

Note that the \e[>0q sequence is a relative new thing. XTerm only added it in April (patch 354). I think it arose from discussions about standardising the TERM_PROGRAM and TERM_PROGRAM_VERSION environment variables (which is issue #1040 for us). But I'm in agreement with you that we're better off remaining anonymous and not supporting stuff like that until the app is more stable.


Auto slider

This and the other themes and plugins are amazing, and we really appreciate the work you have been doing.
Is there any way to implement auto sliding? Or maybe using the Bootstrap carousel but for multiple posts per slider.
Thanks.

Thank you!
There are 2 templates, cards and hero. Hero slider has autoplay. Maybe I add a new card template for autoslide cards. But for now if you want to use autoslide in card template you can set init to
               autoplay: {                     delay: 4000,                 },
in swiper-init.js.
When doing this, delete folder update in root folder, open main.php and delete snippet from line 12 to 18. Otherwise your changes will be lost by new update. Check the docs https://bootscore.me/documentation/bs-swiper/ for using the plugin templates.
Does that help?

Thanks I will check it.


db init

This fails on first run (for the app demo):
$ docker compose up

Error:
# ...
web_1  | ActiveRecord::NoDatabaseError (FATAL:  database "yams_api_development" does not exist
web_1  | ):

This works to demo the app:
$ docker compose -f docker-compose.cypress.yml up

You need to run docker compose run --rm web bin/rails db:prepare first (and make sure it's successful and finishes).


Valid Scope name

When trying to run conversation.py this error pops up
File "/Users/Mohannad/anaconda3/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 2908, in name_scope
raise ValueError("'%s' is not a valid scope name" % name)
ValueError: 'the context text' is not a valid scope name
Any idea what is this or how t solve it ?
Thanks

I don't have this problem, we probably have different versions of Keras. I also saw that you have Python 3.6 and this code was developed in Python 2.7. Either way, you can remove all the parameters name, e.g. name='Encode context'. These parameters are important only to generate the model figure (see the readme file). In this case you can also remove the line: plot_model(model, to_file='model_graph.png').

yes, removing  the name parameter stopped this error from popping up !!
Thanks a lot !!


libpannellum is not defined at onImagLoad (pannellum.js:475)

Hello,
I am trying to run the standalone from v2.5.4.
I have all the files in a directory running on ngix.
/standalone
pannellum.htm (renamed to pannellum.html)
standalone.css
standalone.js
myimage.jpg
/standalone/js/
libpannellum.js
pannellum.js
/standalone/css/
pannellum.css
This is my html file
<!DOCTYPE HTML>

  <meta charset="utf-8">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <title>Pannellum</title>
  <link type="text/css" rel="Stylesheet" href="css/pannellum.css"/>
  <link type="text/css" rel="Stylesheet" href="standalone.css"/>

Javascript is required to view this panorama.
(It could be worse; you could need a plugin.)

I then navigate to this URL.
http://localhost/standalone/pannellum.html?panorama=/standalone/R0010501.jpg&title=My Test&author=Test&autoLoad=true
But I get this error in the console.
Uncaught ReferenceError: libpannellum is not defined
at onImageLoad (pannellum.js:476)
at Image.panoImage.onload(pannellum.js:392)
If I replace

With...


Exposed tool_manager header file.

Exposed access to the tools manager (i.e. moved the tool manager header file to the common include folder). This way, a panel plugin can also gain access to a Tool.

Actually, I just noticed that this targets foxy.  We usually want to target the latest first, and then backport as needed.  Can you retarget this to the ros2 branch?

Thanks @clalancette for your feedback. A new pull request targeted to 'ros2' will be created.


Are you still taking PR's for this project?

I've noticed that you're moving away from this project in favor of heroku slash commands. I just wanted to verify that you're officially deprecating this project.

I am. We're actively working to retire our hubot at heroku.

Thank you for getting back to me


Add doc XML to Assertions and to BotAdapter

With tweaks to two assertion methods: use IEnumerable in place of List or T[].

@cleemullins , some comments with respect to the code:

in BotAdapter.RunPipeline, it now looks like context.Activity should never be null now, so the else block is in theory unreachable now.
in BotAdapter.ContinueCoversation, reference.GetPostToBotMessage return an activity of type "message". According to Steve, on the JS side, they're using an activity with an unassigned type for proactive messaging.


net.liftweb.json.XmlExamples failing in Scala 2.12 community build

seen at https://scala-ci.typesafe.com/job/scala-2.12.x-integrate-community-build/1080/consoleFull and https://scala-ci.typesafe.com/job/scala-2.12.x-integrate-community-build/1081/consoleFull
failing commit is 79d036703eedf32a27485574ded1bf2805421ead
last green commit 16f61a0c8d3f647188b0978456e47fc18ecc7293
[lift-json] [info] XML Examples
[lift-json] [info]
[lift-json] [info] + Basic conversion example
[lift-json] [info] + Conversion transformation example 1
[lift-json] [info] + Conversion transformation example 2
[lift-json] [info] + Primitive array example
[lift-json] [info] + Lotto example which flattens number arrays into encoded string arrays
[lift-json] [error] x Band example with namespaces
[lift-json] [error]  'JObject(List(JField(b:band,JObject(List(JField(name,JString(The Fall)), JField(genre,JString(rock)), JField(influence,JString()), JField(playlists,JObject(List(JField(playlist,JArray(List(JObject(List(JField(name,JString(hits)), JField(song,JArray(List(JString(Hit the north), JString(Victoria)))))), JObject(List(JField(name,JString(mid 80s)), JField(song,JArray(List(JString(Eat your self fitter), JString(My new house)))))))))))))))))'
[lift-json] [error]
[lift-json] [error]   is not equal to
[lift-json] [error]
[lift-json] [error]  'JObject(List(JField(b:band,JObject(List(JField(name,JString(The Fall)), JField(genre,JString(rock)), JField(influence,JString()), JField(playlists,JObject(List(JField(playlist,JArray(List(JObject(List(JField(name,JString(hits)), JField(song,JArray(List(JString(Hit the north), JString(Victoria)))))), JObject(List(JField(name,JString(mid 80s)), JField(song,JArray(List(JString(Eat your self fitter), JString(My new house)))))))))))))))))' (XmlExamples.scala:80)
[lift-json] [error] Actual:   ...(rock[)), JField(influence,JString()), JField(playlists,JObject(List(JField(playlist,JArray(List(JObject(List]
[lift-json] [error] [(JField(name,JString(hits)), JField(song,JArray(List(JString(Hit the north), JString(Victoria)))))), JObject(List(JField(name,JString(mid 80s)), JField(song,JArray(List(JString(Eat your self fitter), ]
[lift-json] [error] [JString(My new house)))))))))))))))))]
[lift-json] [error] Expected: ...(rock[]
[lift-json] [error] []
[lift-json] [error] []
[lift-json] [info]

in the community build, I will freeze at 16f61a0c8d3f647188b0978456e47fc18ecc7293 for now

Hmmm… Funkalicious. Particularly since the two things in the example are in fact equal, and this passed our CI build. Perhaps there's an odd interaction with 2.12... Will try that angle when I get a chance if no one picks it up first.

I have a test run going at https://scala-ci.typesafe.com/job/scala-2.12.x-integrate-community-build/1082/consoleFull to confirm that freezing at the previous commit makes the problem go away.
the community build is on scala-xml 1.0.6 these days, not sure if that might make a difference, I see you're still on 1.0.5
if you want to try against the latest 2.12.x nightly build of Scala to see if there's actually some 2.12 change that tickled this, see http://stackoverflow.com/a/40622879/86485 for instructions

:thumbsup: appreciate the pointers!

(Notably, this may well be on us---this started failing immediately after we merged some changes to the JSON parser. Only weird thing to look at is that it worked fine in our continuous build but failed in the community one, so may be something concurrency-related.)

(reverting to the older commit made our run go green again)

Believe we should have a fix in #1822; will post here when that is merged.

Whoops, keeping this open until @SethTisue gets a chance to confirm that things are playing nice again.

test run in progress at https://scala-ci.typesafe.com/job/scala-2.12.x-integrate-community-build/1116/consoleFull

compile errors, because you're on ScalaCheck 1.13.x now but the community build is still on 1.12.x — that's https://github.com/scala/community-builds/issues/13
for now I will disable compiling/running of tests. once we get the ScalaCheck upgrade done (hopefully in the next few months) we'll attempt to re-enable them

Quick question re: the ScalaCheck issue---I believe we were on ScalaCheck 1.13 on the previous builds, too (since we've been building on 2.12, I believe). Did something change on your end?

The community build builds everything from source, so only source compatibility matters, not whether the version numbers are the same. I think that before, you declared a dependency on 1.13 (the community build ignores the number) but were using it in a way that was source-compatible with 1.12. There was no issue until you started using 1.13 specific API.

Hmmm… Interesting. Okay, thanks!


Plugins disabled on their own (1.5-beta)

This is a COPY of Issue 427: Plugins disabled on their own (1.5-beta), filed on Google Code before the project was moved on Github.

Submitted on 2010-08-03T23:04:01.000Z by<EMAIL_ADDRESS>Status: Invalid

Please review the original issue and especially its comments. Comments here on closed issues will be ignored. Thanks.
Original description
**What steps will reproduce the problem?**
1. Enable plugins
2. Wait and return later
3. Plugins are disabled

**What is the expected output? What do you see instead?**
Plugins are disabled when I return later

**Please write in your current versions of YOURLS, Web server, PHP, OS,**
**Browser if applicable, etc...**
Using 1.5-beta
Centos5 VPS, Firefox 3.6.8

**Please provide any additional information below.**
This issue may have occurred when restarting httpd and mysql (IE rebooting the VPS), but it has happened when they were running the whole time, and they have stayed enabled when rebooting aswell.

The entry for active_plugins under yourls_options in the mysql database is
a:4:{i:0;s:26:"hyphens-in-urls/plugin.php";i:1;s:25:"sample-toolbar/plugin.php";i:2;s:25:"random-keyword/plugin.php";i:3;s:31:"quickshare-on-tumblr/plugin.php";}

Occurred on my server for Random Keywords plugin.

@liruqi please open a new issue with your setup's details. This one is almost six years old.


[BUG]: Detect GPU arch at config time or plz mention in README

Description
Was building and running the CUDA test suite; every test but one was failing with 500 (named symbol not found).  It went over my head for a minute
Reproduce
Build & run tests with sub 80 hardware
Expected Behavior
For the tests to run and complete calls to CUDA kernels
Environment
WSL2, gcc 11.3,  CUDA 12.1, CMake 3.22.1
OS + Version:
Ubuntu 22.04.1 LTS
Cargo Version:
Not installed
GPU type:
GTX-2060RTX
Additional context
Well, at least with CMake 3.24, this is available:
native architecture

thanks @Geof23 -  we are looking into it and will update soon

Hi @Geof23,
as you correctly pointed out, the tests fail on older architectures than 8.0.
This is because the default architecture in is set to 8.0 here: https://github.com/ingonyama-zk/icicle/blob/main/icicle/CMakeLists.txt#L11-L14 .
You can still build for a different architecture by setting CMAKE_CUDA_ARCHITECTURES to your desired architecture(s) when running the build script by modifying the cmake -S . -B build command and adding the CMAKE_CUDA_ARCHITECTURES definition, for example like this: cmake -S . -B build -DCMAKE_CUDA_ARCHITECTURES=70.
I suggest that the library maintainers mention this option in the README.
Please let me know if this solves your problem.

Thank you for your responses

@vhnatyk/ @LeonHibnik  please update Readme


Auto Shutdown

Description of the new feature / enhancement
Please add auto shutdown feature.
we select time and close windows auto.
Thank you.
Scenario when this would be used?
Auto shutdown
Supporting information
No response

I also wanted something like this. So I created a PowerAutomate Desktop Flow for it:
http://aaron-junker.github.io/PowerAutomateShutdown/

Thank you Aaron,  I'm looking.

Thank you Aaron, I'm looking.

https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/shutdown
Chances are we'd build this into Awake via #12191
/dup #12191


[BUG] Connection Refused on Startup

Describe the bug
When running the binary, I am greeted with a lovely connection refused. The site that is sending connection refused is http://vps1.jiveoff.fr:3000/presences/102697445. Is your server down?
To Reproduce
Steps to reproduce the behavior:

Run the binary.

Expected behavior
I expected it to work.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: Windows
Version: windows 10 (idk build sorry)

Hello there,
I will look into it now.

Should be resolved now, thanks for the report!


Fixed case of null HttpRequestInitializer

:+1:

:+1:

:+1:

@wuman any thoughts on this one?

Aha just figured out a way to avoid the null issue by setting a new HttpRequestInitializer in the builder:
https://github.com/wuman/android-oauth-client/pull/55/commits/1db2a39b6cd0e3ad06627a96a2d500646bb5ad5a
Seems to solve the issue, but it would be better if the library was hardened to protect against builders who don't explicitly set it.

Fixes #40


Error to validate vcf file from stacks (gstack tools reference mapping)

I worked with stacks2, and I want to submit this data to EBI I have the following errors after applying vcf_validator_linux and vcf_debugulator_linux:
According to the VCF specification, the input file is not valid
Error: Sample #5, field GL does not match the meta specification Number=G (expected 3 value(s)). This occurs 1842 time(s), first time in line 3160.
Warning: A valid 'reference' entry is not listed in the meta section. This occurs 1 time(s), first time in line 3160.
Error: Sample #7, field GL does not match the meta specification Number=G (expected 3 value(s)). This occurs 1107 time(s), first time in line 3161.
Error: Sample #3, field GL does not match the meta specification Number=G (expected 3 value(s)). This occurs 1509 time(s), first time in line 3162.
.
.
.

I Don't Know if the useful tools for handling VCF files that recommend on the EBI submissions help page are mandatory because Stacks generate VCF files directly. Any insight about the error above is helpful for us.
PD.
I worked with 40 individuals of Cavia Porcellus from RAD-seq sequencing and use the Scaffolds genome as reference (cavpor3)

The GL field is supposed to contain Genotype likelihood. for a diploid individual there should be 3 values for 3 possible genotypes (AA/AB/BB). My guess is that stacks outputs something slightly different overloading the GL field. That makes the field incompatible with downstream tools and the VCF specification.
You can remove the GL field from the VCF file with bcftools
bcftools annotate -x FORMAT/GL file.vcf.gz


Is there any plan to support index on MessagePack?

Is there any plan to support index on MessagePack?

No. I don't have any plans to build features to support the MessagePack format.


Increasing max_phrase_words runs into memory issues

Hi, first of all, thank you very much for the repository!  :)
I want to retrain the model using a larger number of keyphrases and output longer keyphrases in general.
To achieve this I:

increase the number of max_phrase_words from 5 to 10 in scripts/config.py
increase max_gram from 5 to 10 parameter in my model (in bertkpe/networks/)

However, I see that every number bigger than 5 makes me run out of memory during the step
"start preparing (train) features for bert2joint (bert) ..."
I can also see that if I increase the numbers to 6, I run out of memory at a much later stage in the preparation step than if I increase it to something higher like 10, even though the operation is performed on batches. I suspect that there is a memory leak in one of the data loader functions.

Which dataset are you using? In which line does the OOM you mentioned occur? I may need more information.


css3 animation-play-state please

css3 animation-play-state please

This issue was imported from Google Moderator
Moderator votes: +5
Issue added by Kim SJ on 2014-03-25
To vote this issue up or down, simply include +1 or -1 in your comment.

+1

+1

+1

+1:

+1

+1

+1

+1, at least finding http://caniuse.com/#feat=css-animation, as animation-play-state is defined in https://www.w3.org/TR/css3-animations/#animation-play-state-property as well, if the support matches animation.
Links:

http://www.w3schools.com/cssref/css3_pr_animation-play-state.asp
https://developer.mozilla.org/de/docs/Web/CSS/animation-play-state

+1

+1

+1

+1

+1

+1

+1, at least mdn shows the browser support https://developer.mozilla.org/en-US/docs/Web/CSS/animation-play-state Would be awesome to also have it on caniuse! :)

Now available at https://caniuse.com/#feat=mdn-css_properties_animation-play-state


'One or more of the CNAMEs you provided are already associated with a different resource.'

Describe the bug
I am deploying a basic next.js application that generates an entire "static" site in terms of next.js.
I had deployed this site multiple times before a few days ago. I came back to do an update and get the following error CNAMEAlreadyExists: One or more of the CNAMEs you provided are already associated with a different resource.
To Reproduce
frontend:
  component: "serverless-next.js"
  inputs:
    domain: "..domain here"

serverless
...site begins to deploy

error:
  CNAMEAlreadyExists: One or more of the CNAMEs you provided are already associated with a different resource.
    at Request.extractError (/Users/bradybrown/.serverless/components/registry/npm/serverless-next.js@1.9.4/node_modules/aws-sdk/lib/protocol/rest_xml.js:53:29)
    at Request.callListeners (/Users/bradybrown/.serverless/components/registry/npm/serverless-next.js@1.9.4/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
    at Request.emit (/Users/bradybrown/.serverless/components/registry/npm/serverless-next.js@1.9.4/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
    at Request.emit (/Users/bradybrown/.serverless/components/registry/npm/serverless-next.js@1.9.4/node_modules/aws-sdk/lib/request.js:683:14)
    at Request.transition (/Users/bradybrown/.serverless/components/registry/npm/serverless-next.js@1.9.4/node_modules/aws-sdk/lib/request.js:22:10)
    at AcceptorStateMachine.runTo (/Users/bradybrown/.serverless/components/registry/npm/serverless-next.js@1.9.4/node_modules/aws-sdk/lib/state_machine.js:14:12)
    at /Users/bradybrown/.serverless/components/registry/npm/serverless-next.js@1.9.4/node_modules/aws-sdk/lib/state_machine.js:26:10
    at Request.<anonymous> (/Users/bradybrown/.serverless/components/registry/npm/serverless-next.js@1.9.4/node_modules/aws-sdk/lib/request.js:38:9)
    at Request.<anonymous> (/Users/bradybrown/.serverless/components/registry/npm/serverless-next.js@1.9.4/node_modules/aws-sdk/lib/request.js:685:12)
    at Request.callListeners (/Users/bradybrown/.serverless/components/registry/npm/serverless-next.js@1.9.4/node_modules/aws-sdk/lib/sequential_executor.js:116:18) {
  message: 'One or more of the CNAMEs you provided are already associated with a different resource.',
  code: 'CNAMEAlreadyExists',
  time: 2020-03-18T02:08:48.581Z,
  requestId: 'redacted',
  statusCode: 409,
  retryable: false,
  retryDelay: 50.114298601339804
}

  34s › frontend › CNAMEAlreadyExists: One or more of the CNAMEs you provided are already associated with a different resource.

Desktop (please complete the following information):

OS: OSX
Version: 10.15.3 (19D76)

Here is the debug log
serverless --debug

  DEBUG ─ Resolving the template's static variables.
  DEBUG ─ Collecting components from the template.
  DEBUG ─ Downloading any NPM components found in the template.
  DEBUG ─ Analyzing the template's components dependencies.
  DEBUG ─ Creating the template's components graph.
  DEBUG ─ Syncing template state.
  DEBUG ─ Executing the template's components graph.
  DEBUG ─ Deploying bucket exktrms-21ijq2l in region us-east-1.
  DEBUG ─ Checking if bucket exktrms-21ijq2l exists.
  DEBUG ─ Setting acceleration to "true" for bucket exktrms-21ijq2l.
  DEBUG ─ Bucket exktrms-21ijq2l was successfully deployed to the us-east-1 region.
  DEBUG ─ Starting upload to bucket exktrms-21ijq2l in region us-east-1
  DEBUG ─ Starting upload to bucket exktrms-21ijq2l in region us-east-1
  DEBUG ─ Starting upload to bucket exktrms-21ijq2l in region us-east-1
  DEBUG ─ Starting upload to bucket exktrms-21ijq2l in region us-east-1
  DEBUG ─ Uploading file /Users/bradybrown/Developer/bradybrowninfo/.next/serverless/pages/index.html to bucket exktrms-21ijq2l
  DEBUG ─ Uploading file /Users/bradybrown/Developer/bradybrowninfo/.next/serverless/pages/index.html to bucket exktrms-21ijq2l
  DEBUG ─ Uploading directory /Users/bradybrown/Developer/bradybrowninfo/.next/static to bucket exktrms-21ijq2l
  DEBUG ─ Starting upload to bucket exktrms-21ijq2l in region us-east-1
  DEBUG ─ Uploading file /Users/bradybrown/Developer/bradybrowninfo/.next/serverless/pages/404.html to bucket exktrms-21ijq2l
  DEBUG ─ Uploading directory /Users/bradybrown/Developer/bradybrowninfo/public to bucket exktrms-21ijq2l
  DEBUG ─ File /Users/bradybrown/Developer/bradybrowninfo/.next/serverless/pages/404.html uploaded with key static-pages/404.html
  DEBUG ─ File /Users/bradybrown/Developer/bradybrowninfo/.next/serverless/pages/index.html uploaded with key static-pages/index.html
  DEBUG ─ File /Users/bradybrown/Developer/bradybrowninfo/.next/serverless/pages/index.html uploaded with key static-pages/index.html
  DEBUG ─ Starting deployment of lambda exktrms-oqh8qv to the us-east-1 region.
  DEBUG ─ Syncing role exktrms-e8kq28d in region us-east-1.
  DEBUG ─ Saved state for role exktrms-e8kq28d.
  DEBUG ─ Role exktrms-e8kq28d was successfully deployed to region us-east-1.
  DEBUG ─ Deployed role arn is arn:aws:iam::052969257673:role/exktrms-e8kq28d.
  DEBUG ─ Packaging lambda code from /Users/bradybrown/Developer/bradybrowninfo/.serverless_nextjs/default-lambda.
  DEBUG ─ Uploading exktrms-oqh8qv lambda code.
  DEBUG ─ Updating exktrms-oqh8qv lambda config.
  DEBUG ─ Successfully deployed lambda exktrms-oqh8qv in the us-east-1 region.
  DEBUG ─ Starting deployment of CloudFront distribution to the us-east-1 region.
  DEBUG ─ Updating CloudFront distribution of ID E6RQD4GKD4ZLU.
  DEBUG ─ CloudFront deployed successfully with URL: https://d3r6s6rf1kuqun.cloudfront.net.
  DEBUG ─ Starting Domain component deployment.
  DEBUG ─ Validating inputs.
  DEBUG ─ Formatting domains and identifying cloud services being used.
  DEBUG ─ Getting the Hosted Zone ID for the domain bradybrown.info.
  DEBUG ─ Searching for an AWS ACM Certificate based on the domain: bradybrown.info.
  DEBUG ─ Checking the status of AWS ACM Certificate.
  DEBUG ─ Adding www.bradybrown.info domain to CloudFront distribution with URL "https://d3r6s6rf1kuqun.cloudfront.net"

  error:
  CNAMEAlreadyExists: One or more of the CNAMEs you provided are already associated with a different resource.

Im adding this here as documentation for anyone else who runs into this issue. I resolved this by performing the following (note - I am not sure what part/s of the following steps actually fixed the problem, but what I did below fixed it and thats the important thing)
rm -rf .next
rm -rf .serverless
rm -rf .serverless_nextjs
rm -rf node_modules

Go to AWS Cloudfront console
remove all distributions associated with your domain
serverless # should now work

Experience this a lot when deploying from different machines. I was looking in to setting up CI/CD for my Next.js project but it looks like this will be an issue if running builds on different machines/instances does not work

@jolosimeon maybe this will help: https://github.com/danielcondemarin/serverless-next.js/issues/328#issuecomment-604733316

This problem occurs because as of today this component doesn't reliably detect if the deployment already has the resource. So after a few deploys, it tries to create a new CF distribution and tries to attach the domain & fails since it is already attached to the older deployment! I'm struggling this issue for some time now and tried many workarounds but nothing is reliable.

I have the same problem. It is a blocker when the plugin can not detect if the deployment (domain) already has been set.

This issue is documented in the readme - you need to make sure you keep your .serverless folder between deploys. If you are using multiple machines then set up a simple CI/CD process triggered by a merged pull request that syncs it from and back to an S3 bucket and do not deploy from your machine.

This issue is documented in the readme - you need to make sure you keep your .serverless folder between deploys. If you are using multiple machines then set up a simple CI/CD process triggered by a merged pull request that syncs it from and back to an S3 bucket and do not deploy from your machine.

Ok. I don't want to have .serverless. in repository. As I understand I can use this example: https://gist.github.com/hadynz/b4e190e0ce10e5811cb462920a9c678f
How about this PR: https://github.com/serverless-nextjs/serverless-next.js/issues/477
When can it be merged?

Yes that's correct. I don't think that PR will bypass the requirement for keeping state as there are other resources created during the deployment of this component, not just CloudFront.

I've documented the .serverless sync solution here and the PR mentioned above is already available, so assuming this can be closed. Let us know if there are any other related issues. Thanks!


:seedling: Create framework images for each flavor

This is an alternative to #972 and supersedes it.
Framework images now contains the whole framework:

kairos-agent
elemental-cli
luet
base cloud configs
grub configuration files
services for inits

The images are pushed during release as:
quay.io/kairos/framework:<version>_<flavor>

So can be used directly in Dockerfiles as such:
FROM fedora:36

## Copy the framework image depending on the distro family
COPY --from=quay.io/kairos/framework:v2.0.0_fedora / /

## Install kernel and packages..
RUN ...

## Generate initrd
RUN kernel=$(ls /boot/vmlinuz-* | head -n1) && \
            ln -sf "${kernel#/boot/}" /boot/vmlinuz
RUN kernel=$(ls /lib/modules | head -n1) && \
            dracut -v -N -f "/boot/initrd-${kernel}" "${kernel}" && \
            ln -sf "initrd-${kernel}" /boot/initrd && depmod -a "${kernel}"
RUN rm -rf /boot/initramfs-*

Part of https://github.com/kairos-io/kairos/issues/755

somehow, alpine is broken, having a look at it..

Found the reason I think, fixed in https://github.com/kairos-io/kairos/pull/973/commits/00074e0c300b7eda7c8ab5f4fb8aca213e24464c. Should be good to go

Codecov Report

Merging #973 (318bf62) into master (cb2e7c0) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##           master     #973   +/-   ##
=======================================
  Coverage   22.79%   22.79%
=======================================
  Files          22       22
  Lines        1610     1610
=======================================
  Hits          367      367
  Misses       1179     1179
  Partials       64       64

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

@mauromorales need another review here :pray:


Consolidate Cardano Nix inputs in a common/shared repo

Managing revisions of our dependencies is difficult, that's why across MLabs we've settled on a temporary solution to use github:mlabs-haskell/bot-plutus-interface as the canonical source of Nix derivations that are used across projects.
This repo assures that all dependencies are compatible at compilation level and provides one place where the efforts of upgrading library versions take place. It also makes it easy to communicate across projects which derivation set is used (essentially bpi revision).
Having this stashed in BPI is not ideal, and we should consider making a special repo with that specific purpose in mind stand alone.
Regardless, we should consider supporting this mini project from CTL side as well as we introduced all the flake inputs explicitly which is not ideal.

I definitely like the idea of having a public repo for this. Although hopefully this won't be necessary in the end for CTL :)

We only need to remove one more endpoint (the hardest one!) then we can remove CTL's server component, so this won't be necessary eventually


Move to next screen on Enter

hey, this works but the "proper" way to do this is to use a <form> element so I'm going to do some add-on commits to this, will involve some layout changes


x:description/attribute(xquery-version)

This pull request derives from #496. So needs to be handled after that.

x:description has @xslt-version but it doesn't have a facility to specify the XQuery version.
This pull request provides it: x:description/@xquery-version
I didn't name it @query-version (without x of the first letter), because @xslt-version isn't @stylesheet-version.
Commits

fba935a62d0376c8bf07d9324443a1dc82b995a2 defines @xquery-version in the schema.

I verified manually that oXygen picks it up with the annotation.
The type of the attribute (text) is based on XQueryX schema (<xsd:element name="version" type="xsd:string"/>).

39038b3c0c52c5aa97478b21cf033733a05fd641 annotates @xslt-version in the schema.

The annotation highlights the difference from @xquery-version.
I verified manually that oXygen picks up the annotation.

c984615c98ff485934e2e862c63cfb73a8470808 generates the version declaration when compiling XSpec for XQuery.

c79b7cb04b443408e14901eabfebe0d7b88bc809 verifies that @xquery-version is actually declared in the compiled module.

1b60e1e123c5011a86d02895dd42a6029e1f4531 enables test/*.xspec to be run on XQuery 3.1.
Saxon 9.6 doesn't support 3.1. 9.7 supports 3.1 only when -qversion:3.1 is specified. 9.8 and 9.9 support 3.1 by default but reject -qversion. build.xml and generate.xsl work together to find the best route in the matrix:

Saxon-HE 9.9: Travis, AppVeyor

Saxon-HE 9.8: Travis, AppVeyor

Saxon-EE 9.7:
$ ./run-xspec-tests-ant.sh -silent
...
xquery.supports.3-1.default=false
xquery.supports.3-1.qversion=true
...
Testing xquery-version_3.1.xspec [q]
passed: 1 / pending: 0 / failed: 0 / total: 1

Saxon-EE 9.6:
$ ./run-xspec-tests-ant.sh -silent
...
xquery.supports.3-1.default=false
...
xquery.supports.3-1.qversion=false
Skipping xquery-version_3.1.xspec: Requires XQuery 3.1 processor

@galtm
This PR adds an attribute to the schema, So I thought this should be reviewed by someone.
The immediate reason for introducing this new attribute is #498 (ce552c60fc96bbd0eba6a3b8e730ed204d9964b1 in particular where testing #355 requires XPath 3.1).

@cirulls
Merged this new feature.


Can you setup multi qr code reader at same time?

review zxing.js ， if it have multi decode we can copy to this complement

zxing.js no such function


Don't clear modifier state on focus change

I believe that the underlying issue that caused the stuck modifier keys was resolved in the 0.29 winit keyboard refactor.
This probably needs to tested on other desktop platforms however since I am only able to test this on windows 11.

Closes https://github.com/emilk/egui/issues/2332

Let's try it and see if we regress :)
Do you have a link for the winit-side fix for posterity?


[0.2.0] Metadata Implementation

Description

The metadata component for single table and multi table.
Motivation and Context

This metadata is used to describe:

the base attribute (data type, pii, format, etc) of each column in table;
the relationship between columns;
the relationship between tables (parent table, child table);
etc.

Also, metadata will also provide methods to:

auto inspections;
add/change attributes;
add/change/remove relationship;
check the validation of relationship;
etc.

How has this been tested?

Types of changes

[ ] Maintenance (no change in code, maintain the project's CI, docs, etc.)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

Currently, metadata is in the design stage.
I will probably complete the specific design tomorrow,  I plan to initiate a discussion when completing the design.

We can ignore the multi-table scenario for now and get the single table fields done. The table-to-table relationship (A.a vs. B.a) can be considered separately from the field (a,b,c,d) case within the table.
I'd like to know what is necessarily contained in a single table Metadata, such as the currently implemented discrete columns: https://github.com/hitsz-ids/synthetic-data-generator/blob/main/sdgx/data_models/inspectors/discrete.py

We can ignore the multi-table scenario for now and get the single table fields done. The table-to-table relationship (A.a vs. B.a) can be considered separately from the field (a,b,c,d) case within the table.

Yes, we will first update the metadata of a single table.
Currently, the metadata of a single table has the following new information (please help me check if there are any gaps):

Primary key: primary key information, here we need to be compatible with composite primary keys;
Data type of each column: Use dict description, key is the column name, and value is the DataType object of each column. Different attributes/methods can be provided according to the different DataType.

I'd like to know what is necessarily contained in a single table Metadata, such as the currently implemented discrete columns: https://github.com/hitsz-ids/synthetic-data-generator/blob/main/sdgx/data_models/inspectors/discrete.py

I think this is very necessary. We may start from support 5 basic types:

ID
Numeric value
Discrete value
DataTime
Bool value

However, the multi-table scenario is also the focus of our work.
We have faced the need for multi tables in some actual work, and existing solutions cannot solve their needs.
After finishing single table metadata, I will implement metadata for multi tables based on SingleTableMetadata.

Seems no need to intro a submodule as metadata
metadata.py for single table and relationship.py + The-Multi-Table-Combiner.py for multi table is enough.

Seems no need to intro a submodule as metadata
metadata.py for single table and relationship.py + The-Multi-Table-Combiner.py for multi table is enough.

It’s okay, there aren’t many new modules in metadata.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

:exclamation: No coverage uploaded for pull request base (main@97daa04). Click here to learn what that means.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main      #81   +/-   ##
=======================================
  Coverage        ?   75.95%
=======================================
  Files           ?       55
  Lines           ?     2100
  Branches        ?        0
=======================================
  Hits            ?     1595
  Misses          ?      505
  Partials        ?        0

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

There may be a need for more design on how Relationships reflect multi-table relationships, as it stands, Relationships reflect a pair of foreign key relationships, but in reality, the foreign key relationships are one-to-many. This is mostly related to how multi-table emulation is implemented, is the current design sufficient for this?

is the current design sufficient for this?

I think the current design of relationship is sufficient to describe existing multi-table relationships.
In synthetic data, the multi-table relationships we currently implement are limited to “one-to-one” or “one-to-many”, that is, a parent table is associated with different child tables through foreign keys. In the current design, relationship is like a line in this correspondence, and each relationship only describes the relationship between two tables. We use multi-table combiner to combine table's meatadata and relationships.

Sounds fine, looking forward to more commits!

Could you please add some tests on Metadata.save and Metadata.load? Although they still seem to be working fine.
I think this PR can be merged at the moment, and one or more PRs may be needed next to intro Relationship and multi-table model code.

Could you please add some tests on Metadata.save and Metadata.load? Although they still seem to be working fine.

No problem, I will merge after completing the tests of Metadata.save and Metadata.load.


v2: Explicitly specifying the implicit role of a fieldset element changes the styling

Describe the issue
First of all thank you so much for Pico, I love it!
According to the docs:

role="group" is used to stack children horizontally.

The examples there use a fieldset element, but the implicit role of fieldset is already group and a11y complains about a redundant role: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/fieldset#technical_summary
This kind of issue might affect other elements too, I haven't checked.
Current Behavior
Explicitly specifying the default role of a fieldset element changes the styling.
Expected Behavior
It should not make a difference to the style whether the role of an element is implicit or explicit. I'm not sure what the best solution is, but maybe the default styling for a fieldset should be the group styling (ie horizontal), and the other styling (ie vertical) can be triggered by setting the role to none or presentation?
Reproduction URL
n/a
Environment
n/a

@willclarktech, thanks.
What tool do you use to see some a11y complains?
I can't see any in Chrome or with Visual Studio linting tools.
I would not remove role="group" now to avoid a breaking change.
But eventually we could change the documentation to use a div instead of a fieldset.
Not sure yet.

Hm, I thought it was standard a11y linting, but it seems this is raised by Svelte for VSCode: https://svelte.dev/docs/accessibility-warnings#a11y-no-redundant-roles
To be clear, this isn't a blocker for me. I just thought default roles were worth considering.

As role="group" can be used with a div, and we can't ship a breaking change, we should not change anything.
Perhaps the documentation could be improved.

Hello,
As ARIA selectors are already in Pico, shouldn't we use aria-orientation ?

What tool do you use to see some a11y complains?

I've found that the W3C validator also complains about this usage of role. For example, on pico's docs about it the following diagnostic is returned, among others:

[!warning]
The group role is unnecessary for element fieldset.

It's also worth noting that this isn't really an "accessibility complaint" (am i misunderstanding what "a11y complains" means in prior discussion?). It's unnecessary here because the group role is implicit; specifying it here is supposed to make absolutely no difference whatsoever. Pico has two different ways here to style what is supposed to be two identical elements.

@sodiboo Correct, this isn't specifically an accessibility complaint. Svelte's accessibility tooling is just how I came across the general issue that explicitly specifying the implicit role of an element can affect the styling, which indicates that roles are being somewhat abused by the current approach.

What about using aria-roledescription="inline" ?
Isn't it the whole purpose of it, to describe how we use a role ?


Add Multi-Radar Multi-Sensor (MRMS) forcing reader

This update adds the capability to read MRMS forcing as well as an option within the reader that allows the user to input dynamically varying masks to delineate where the radar data should/should not be used.
Test case data can be found at /discover/nobackup/projects/wldas/share/mrms_testcase
This resolves trac tickets #538, #597, #625

Would you please give me read permission to your mrms_testcase files?

Sorry about that! You should have permission now.

Hello,
My run of the mrms test case crashes at line 70 in finalize_mrms_grib.F90.
From what I see, the run will use nearest neighbour interpolation for the MRMS data, but LIS is crashing trying to deallocate the array needed for upscaling.
Would you please review the logic in finalize_mrms_grib.F90?
I suspect the problem is in (res.eq.0.01).  Even though res is 0.01, it is not 0.01 w.r.t. floating point.
A simpler approach maybe to just check each array like this:
if ( allocated(mrms_grib_struc(n)%rlat1) ) then
   deallocate(mrms_grib_struc(n)%rlat1)
endif


Shumway is NOT "verified"...

I don't even CARE if this has already been logged.
Mozilla has seen fit to block the ability to load/run "unverified" add-ins as a "security" measure (which is the same mistake Microsoft made with their plugin framework...)   I had two extensions/plugins that got screwed up upon update to Build 43.  APK downloader being one of them.  Shumway being the other.
If you can't get your own act together...get the larger team to wise up...  Seriously guys...

Shumway being the other.

Shumway extension is automatically signed. Closing as wfm. Please provide more details to back up you claim.

Notice the extension hosted at http://www.areweflashyet.com/shumway/ and shall be used by testers, researchers and developers only. The version for end-users was never released.

So...as an off and on researcher...I'm to pound sand?   Wrong answer to be
blunt.
You are guilty of Security Theater here.  Shameful
On Dec 28, 2015 9:25 AM, "Yury Delendik"<EMAIL_ADDRESS>wrote:

Notice the extension hosted at http://www.areweflashyet.com/shumway/ and
shall be used by testers, researchers and developers only. The version for
end-users was never released.
—
Reply to this email directly or view it on GitHub
https://github.com/mozilla/shumway/issues/2406#issuecomment-167587742.

Did you try these two answers on the FAQ to enable it on a nightly build of
Firefox?
https://github.com/mozilla/shumway/wiki/Frequently-Asked-Questions#extension
Can I install Shumway extension for Firefox?
The Firefox extension is provided for the developers and tester -- end user
shall use Firefox Nightly to try it (see below). The extension is published
athttp http://www.areweflashyet.com/shumway/extension/firefox/shumway.xpi
:// http://www.areweflashyet.com/shumway/extension/firefox/shumway.xpi
www.areweflashyet.com
http://www.areweflashyet.com/shumway/extension/firefox/shumway.xpi/
http://www.areweflashyet.com/shumway/extension/firefox/shumway.xpishumway
http://www.areweflashyet.com/shumway/extension/firefox/shumway.xpi
/extension/
http://www.areweflashyet.com/shumway/extension/firefox/shumway.xpifirefox
http://www.areweflashyet.com/shumway/extension/firefox/shumway.xpi/
http://www.areweflashyet.com/shumway/extension/firefox/shumway.xpi
shumway.xpi
http://www.areweflashyet.com/shumway/extension/firefox/shumway.xpi and
automatically updated. The extension requires click-to-play enabled (for
Firefox 21+) and Flash plugin set to "Ask to Activate" (for Firefox 23+).
It is possible to configure the extension (e.g. when the Flash plugin is
not installed) to ignore click-to-play settings and always show the Shumway
player. Seehttps
https://github.com/mozilla/shumway/wiki/Debugging-and-Configuring-Shumway#using-the-extension
://
https://github.com/mozilla/shumway/wiki/Debugging-and-Configuring-Shumway#using-the-extension
github.com
https://github.com/mozilla/shumway/wiki/Debugging-and-Configuring-Shumway#using-the-extension
/
https://github.com/mozilla/shumway/wiki/Debugging-and-Configuring-Shumway#using-the-extension
mozilla
https://github.com/mozilla/shumway/wiki/Debugging-and-Configuring-Shumway#using-the-extension
/
https://github.com/mozilla/shumway/wiki/Debugging-and-Configuring-Shumway#using-the-extension
shumway
https://github.com/mozilla/shumway/wiki/Debugging-and-Configuring-Shumway#using-the-extension
/wiki/Debugging-and-Configuring-Shumway#using-the-extension
https://github.com/mozilla/shumway/wiki/Debugging-and-Configuring-Shumway#using-the-extension
for
more information.
I heard Shumway is a part of the Firefox Nightly. How can I use it?
The Shumway code is disabled by default (see bug 904346
https://bugzilla.mozilla.org/show_bug.cgi?id=904346). You have to enable
it by opening the web browser at about:config and changing the
preference shumway.swf.whitelistto "*" and shumway.disabled tofalse.
The Nightly downloads can be found athttp://nightly.mozilla.org/.
On Dec 28, 2015 2:34 PM, "Frank Earl"<EMAIL_ADDRESS>wrote:

So...as an off and on researcher...I'm to pound sand? Wrong answer to be
blunt.
You are guilty of Security Theater here. Shameful
On Dec 28, 2015 9:25 AM, "Yury Delendik"<EMAIL_ADDRESS>wrote:

Notice the extension hosted at http://www.areweflashyet.com/shumway/ and
shall be used by testers, researchers and developers only. The version
for
end-users was never released.
—
Reply to this email directly or view it on GitHub
https://github.com/mozilla/shumway/issues/2406#issuecomment-167587742.

—
Reply to this email directly or view it on GitHub
https://github.com/mozilla/shumway/issues/2406#issuecomment-167635578.

@madscientist42 No, it means that the extension is unstable until a stable version for end users is released. Unstable implies that things can break from time to time, even though we all do our best to minimize the chances of that happening.
The extension signing process is relatively new and was quickly enabled in Firefox, so there has not been too much time to implement extension signing for projects (Shumway being one, but there are more projects) and an API for this was not available until a few weeks ago. However, it has been implemented in the meantime in https://github.com/mozilla/shumway/commit/1a32b7365f65a5c69f849d33163fc97bbc371cdd. For the extension signing we had to change the extension ID in https://github.com/mozilla/shumway/commit/c219d3beaa440028beececc1c6ab9a08440bdbf0, meaning that you need to uninstall the previous extension manually and install the new extension from http://mozilla.github.io/shumway/extension/firefox/shumway.xpi. This extension is signed; I just checked that for you.
If you reinstall the extension you will see that it is in fact signed, so you are blaming people here for no reason. Please be more polite: contributors are really always willing to help you out and to look into solving issues, but not when they are spoken to in such a way.


Edition of the collected data.

Allow opening of the Gathering Form for edit collected data using the edit button provided on the balloon of the Marker.

ok, this improvements was implemented.


Types no longer working

Describe the bug
Since version 0.14.1 the types are no longer working.
Your types point to 'dist/index.d.ts' which is not present.
As a result all TS compilations now fail ;(

fixed #115

is this fix available on npm yet?

Not yet.

published


Multiple Users in one Message (Bulk/Broadcast Message)

Problem
To send a single message, e.g. an update alert message to users, or even a greeting for the holiday, I have to add a message for each user separately. This could clog up the database, specially since all the messages are the same, just the user is different.
Possible solution
A separate table with User -> Message mapping,  an admin form/action for Bulk messages, etc.
Describe alternatives you've considered
Alternatives can be Firebase Messaging, but I would prefer a DRF-only solution.

Interesting idea there, though I think this should be as an add-in to this package.
About the problem
I must point that usually messages from this package should not be persistent, and get deleted as soon as they are not relevant. This design is replicating the Django Messages framework, where the messages are stored in the session, and get deleted on logout.
With this in mind, it reduces the weight of creating many messages in the DB, because they will eventually get cleared when they will be read.
Stuff to think about

We must store for each user separately whether they have read the message or not
We must include them through the same API from DBStorage and MessagesViewSet
We must design it in a way that bulk messages could be cleared eventually, preferably in the same logic as regular messages

Design Idea
As you've said, create a new model that will store relation between a message and multiple users, each with info whether they've read the message or not.
Create a new storage object that will include those messages in the filtering, providing a similar interface like they are regular messages. This new storage should implement a way to send bulk messages to a list of users.
The user submitting the broadcast message, will create a new "master message" with relation for him.
Any other recipient of that message will have a row in the bulk message model. The "master message" should not get deleted until all related bulk messages are read.
Create a new API view set to create and check status of bulk messages.
How I would implement such thing
A new model that will obtain the relation between the user and the message:
class BulkMessage(models.Model):
    message = models.ForeignKey(Message, on_delete=models.CASCADE)
    user = models.ForeignKey(get_user_model(), on_delete=models.CASCADE)

    created = models.DateTimeField(auto_now_add=True)

    class Meta:
        constraints = [
            models.UniqueConstraint(fields=("message", "user"), name="unique_bulk_message"),
        ]

It will contain a manager like on the classic Message that will have a filter for messages for a user and mark as read.
Some improvements for the DBStorage to replace any place the do mark_read with a storage method that will mark any unread messages as read (aka. self.get_unread_queryset().mark_read()). This will later be overriden.
Implement a new BulkDBStorage object that will inherit DBStorage and override functions:

get_queryset -> To include message relevant to the request by the relation with the user through BulkMessage
get_unread_queryset - > To include unread message from the relation through BulkMessage
mark_all_read -> Mark read any messages that are directly attached to the request.user, and also any BulkMessage for that user.

There a new method can be implemented like:
def add_bulk(self, recipients: Sequence[User], level: int, message: str, extra_tags=''):
    message = Message.objects.create_message(self.request, message, level, extra_tags=extra_tags)
    BulkMessage.objects.bulk_create([
        BulkMessage(message=message, user=user)
        for user in recipients
    ])

Implement a viewset, with the methods:

create -> Send a new bulk message
list -> List all bulk messages with count aggregation for recipients and read messages
get -> Get specific bulk message with the list of recipients (users)

Tests for implementation

Create a new bulk message

As the sender, should see bulk message on my "unread messages"
As a recipient, should see it on my "unread messages"
After sender reads the master message, it is not deleted
After recipient reads a bulk message, the master message is not marked as read
After recipient reads a bulk message, the bulk message is marked as read
All recipients have read the message, it can be / have been deleted

Where to implement
Three possible locations to add this feature:

As a "contrib" app, separately from the main package app (such as drf_message.bulk_messages)
As a separate PyPI package inside this repo, with dependency drf-messages (such as drf-messages-bulk)
As a separate repo as stand-alone PyPI package with dependency for drf-messages

Please provide you thoughts on my design


address is not showing up in individual invoices

Address is added in postico but it's not showing up in the individual transaction invoices.
It shows up in the monthly one.

Do you have an example where it's broken? I see the address for my own subscriptions.

emailed you one

closed via https://github.com/opencollective/opencollective-website/pull/801


Nantahala Sidings

Taking @Wren idea from discord. No turntable, as I understand that its difficult, or impossible to add. But at least add an additional siding or two at Nantahala for additional locomotives or etc.

No idea of complexity level, but due to the fact that most banking locos live here, any chance of a proper 3 or 4 road shed and proper coal facilities and water in the same place (would need to be behind a chunky milestone but if you've got this far in company mode...


Chutes cause game crash

Describe the Bug
with the latest update placing a chute just crashes the client, closes any servers to the point they have to be reverted from backup
Reproduction Steps

place chute
watch everything die

Expected Result
to have chutes placed without crashing
Screenshots and Videos
No response
Crash Report or Log
https://pastebin.com/fq303tAv
Operating System
Windows 10
Mod Version
0.5.0i
Minecraft Version
1.19.2
Other Mods
No response
Additional Context
No response

I need the full crash log.

after a bit of poking it seems to work fine in a fully vanilla environment so ima try to find the issue myself as well but here, just in case you can do anything about it too
https://mclo.gs/ZdplipX

it seems you have porting lib manually installed. This forced the old version to load, so API that Create requires is missing. Remove it and use the built-in version.

yeah i noticed that too after testing, i have it for a different mod that didnt embed it, updating to the newest fixes it tho, thanks for the help


当加载的 pdf 比较大的时候，会爆内存的问题，

200 page。。。

Guess that's memory but Chinese is not the language to use.. use english

When the PDF file is large. The document has several hundred pages. After you open it, scroll through it, and after you turn over the pages, memory starts to jump, and then OOM. How to solve this problem. big shot. Save me ~

😂      My English is not very good. Can you see what that means?

The file is not very big, the content is more, there are about 250 pages, the file 3.4m.

Documents are internal documents that are not easily disclosed.

Can I turn off the cache? Or the native memory is cleared away. I can accept every reload. Thank you, big brother! (from youdao. 😂）

Add 60-70m memory footprint per page load. Look at the number of pages more than 680m after more than 10 pages. The page crashed.

用的是库的例子。

If you want to send the pdf I can test this, I use pdf files 60mb or larger with no issues.

@Rdxer See Issue 495: https://github.com/barteksc/AndroidPdfViewer/issues/495
Your pages aren't being cleared fast enough by the GC. You'll need to implement something that'll manually close them so they don't all build up in memory.

您用PDFView这个加载pdf的时候，写的是左右滑动吗？您知道怎么写成类似ios那种左右滑动的吗？

can you post a copy of the pdf, i have not seen my memory usage no where near 700mb.

@1stmetro
这问题解决了吗？我也遇到相同的问题
Has the problem been solved?I have the same problem。I use pdf files about 80mb


Added UT2003 (Demo) working with openspy as well.

The demo was released on Linux/Windows in 2002, updated several times and a lively community kept playing the demo only for years. More info and win32 binary here

Do UT2003 demo servers just appear in the regular UT2003 server list? You did not change any code, so I'm wondering how exactly you would get the relevant servers.


MRG: Generalize cov and pick functions

This is some private function refactoring that cleans up our code a bit in case we need to use scalings other places. For example it is necessary for https://github.com/mne-tools/mne-sandbox/pull/25.

LGTM

Current coverage is 85.59% (diff: 80.00%)

Merging #3909 into master will increase coverage by <.01%

@@             master      #3909   diff @@
==========================================
  Files           347        347
  Lines         61927      61934     +7
  Methods           0          0
  Messages          0          0
  Branches       9493       9491     -2
==========================================
+ Hits          53007      53015     +8
+ Misses         6256       6255     -1
  Partials       2664       2664

Powered by Codecov. Last update 2169dd3...1300c35

Thanks @Eric89GXL


feat: add error parsing for the invalid argument type

Is your pull request closing an issue?
Please explain the main changes of your pull request
Handles INVALID_ARGUMENT error type which can be thrown for instance by the getAddress method.
Checklist

[x] Have you added any new returned codes to the README file ?
[x] Have you added new tests for your change?

Codecov Report

Merging #47 (f7314ef) into main (f9dc429) will not change coverage.
The diff coverage is 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff            @@
##              main       #47   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            7         7
  Lines          666       691   +25
  Branches        79        81    +2
=========================================
+ Hits           666       691   +25

Impacted Files
Coverage Δ

lib/__tests__/getParsedEthersError.test.ts
100.00% <100.00%> (ø)

lib/constants.ts
100.00% <100.00%> (ø)

lib/utils/getTopLevelKnownError.ts
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Hi, I'm not sure this is the way to go since, in that case, the original error has more data (especially the argument property which could be programmatically used). Making this PR to open the discussion.
As an alternative, could it be considered that some ethers error should be kept as they are ? Or maybe to add an extra property to the ReturnValue to hold a context object ?


build(deps): bump actions/setup-node from 2.5.1 to 3.0.0

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

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Docker image??

Will the Lychee server be available as a docker image as well ?
regards, hitam4450

Please take a look at the Docker section in the readme.


docs(breaking) fix broken grid layout link

Pull request checklist
Please check if your PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been reviewed and added / updated if needed (for bug fixes / features)
[ ] Build (npm run build) was run locally and any changes were pushed
[ ] Lint (npm run lint) has passed locally and any fixes were made for failures

Pull request type

Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[x] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Issue Number: N/A
What is the new behavior?

Grid layout link points to correct page

Does this introduce a breaking change?

[ ] Yes
[x] No

Other information

Merged. Thank you!


Wrong generation of name for named routes.

Hey all :+1:
Just picked up this one today..
when doing something like this in the routes.rb file:
resources :horses

will result in this:
hors GET, HEAD  /horses                        Routertest::Controllers::Horses::Index
new_hors GET, HEAD  /horses/new                    Routertest::Controllers::Horses::New
hors POST       /horses                        Routertest::Controllers::Horses::Create
hors GET, HEAD  /horses/:id                    Routertest::Controllers::Horses::Show
edit_hors GET, HEAD  /horses/:id/edit               Routertest::Controllers::Horses::Edit
hors PATCH      /horses/:id                    Routertest::Controllers::Horses::Update
hors DELETE     /horses/:id                    Routertest::Controllers::Horses::Destroy

Thinking it was something related to it ending in 'es' (which i'm still not 100% convinced it isn't) i tried other words such as :moustaches and :stones and they worked fine. Intriguing huh? ;-)
This is on 0.5.0 and has been around for quite sometime as far as I can tell.. I know that :horses is not the most common name in the world for a resource and this may very well be a super-duper edge case.. But it shouldn't happen anyways ;-)
I'll try to look into it in the next few days and report back or send PR this way.
Cheers

Hey @theocodes this has been fixed. :wink:

@theocodes FYI - Since Lotus v0.6.0, there will be possible to customize inflections: https://github.com/lotus/utils/pull/90

@jodosha cool! The will come in handy for sure! :)