Sass enhancement

Related issues

#72

Features

[x] Support loadPaths for SASS: Now we can add custom directories to indicate where SASS should lookup to resolve the absolute imports
[x] Support import ~ for SASS: Now jest-preview can load SASS resources if the project is using tilde imports for SASS
[x] Add example of load paths and import ~ for Vite
[x] Add example of load paths and import ~ for CRA
[x] Update website

Todo

Support import ~ for globally configured scss

Currently, we cannot find the option to pass importer to sass CLI: https://sass-lang.com/documentation/cli/dart-sass#options. So if externalCss includes scss files using import ~, style from those files will not work

@ntt261298 I think we should try to close this PR soon. Thanks.

@ntt261298 I published v0.2.4-alpha.0
Let's do some testing on a real project before we roll out 0.2.4.


no-debugger only when in production

I saw this in someones eslintrc file on the internet. This would help with issues with my autofix eslint on save. I always have to wrestling with my IDE to disable removing debugger on save. Would this work for us?
// allow debugger during development
'no-debugger': process.env.NODE_ENV === 'production' ? 2 : 0

I just worry this will let debuggers slip through in pre-commit or pre-push hooks, which is ideally where we want to catch them. Does VSCode not have an easy way to disable rules from auto-fixes? It's really easy in Atom 😄.

Yeah, it does make me worry too. It's just annoying.
Solution for vscode, add this to vscode settings.json. Should still catch errors in commit/push hooks
  "eslint.options": {
    "rules": {
      "no-debugger": "off"
    }
  }


Conversations: Don't start a conversation if you're under attack or otherwise indisposed

Right now, any text that triggers a conversation will start up a conversation. However, if a Character is in certain states - fighting or resting or what have you - it should probably not do that.
$ say hi pia kung

Pia Kung says, "I can't talk right now, I'm being attacked by {{character}}"

$ say hi pia kung

Pia Kung snarls at you, "You will die for attacking me!"

We should think of some verbs to describe the interactions (snarl, shout, scream, etc.) as well as some pithy one-liners. It should also depend if you're the attacker (in which case, they're more likely to be mean) vs someone just trying to chat about the weather while their life is in mortal peril.

Quickly fixed. I may come back and do more with this later, particularly when we have more intelligent enemies.


epcs-for-existing-domestic-properties

Made changes to editions, versions, datsets.json and topics.json

This pull request was created for trouble shooting changes in the branch santhosh/existing dwellings. All changes in the santhosh/existing-dwellings passes now and there is no need for this pull request.


Frost Pack!

Focused on Frost Orbs and the Freeze mechanic.
Code review may want to look at the FrozenMod, it required some unconventional methods to get it functioning in all use cases.  Tricky timing with end of turn effects and specifically when end of turn for cardmods goes off vs end of turn for powers.  Had to move things around with a lot of trial and error to find just the right spot for it.

Did you have any thoughts on where to start the ratings for this? From looking over the cards, I was thinking something like:

Offense: 2 (not great but there's a few options)
Defense: 5 (knowing whether this is fully justified will require some play experience, but the mini-Glacier seems to me like it will be very good, we already know that Cold Snap is a strong card, and with those at common plus other good defensive cards, that's a lot)
Support: 3 (the freeze effects fit into this, and it has some synergy with other orb packs)
Frontload: 1 (most cards have little immediate impact)
Scaling: 4 (several good options in the pack, including just filling up your orb slots)

i
These ratings look pretty good to me.

Comment from Modargo resolved, thanks for the pass-through.  And glad I landed on a stable implementation for the FrozenMod, took many many attempts.


ROX-13844 Throttle logs generated by the scraper

Description
Makes it so that the logs in ProcfsScraper are throttled. This is part of https://issues.redhat.com/browse/ROX-13962.
Future work will include adding metrics associated with the current logging statements. Determining when a process is defunct, and adding metrics for them. Reporting defunct processes in an API and the UI.
Checklist

[x] Investigated and inspected CI test results
[x] Saw logs throttled in local testing

Testing Performed
git checkout jv-test-defunct
make clean
make
cd defunct-process-test
make
make run
In another terminal
cd to repo root directory
make -C integration-tests TestSocat
grep Could TestSocat-collector.log
[DEBUG   2023/01/25 00:34:44] [Throttled] (ProcfsScraper.cpp:444) Could not open process directory 1250522: No such file or directory
[DEBUG   2023/01/25 00:34:54] [Throttled] (ProcfsScraper.cpp:444) Could not open process directory 1250936: No such file or directory
[DEBUG   2023/01/25 00:34:58] [Throttled] (ProcfsScraper.cpp:444) Could not open process directory 1251107: No such file or directory
[DEBUG   2023/01/25 00:35:00] [Throttled] (ProcfsScraper.cpp:444) Could not open process directory 1251072: No such file or directory
[DEBUG   2023/01/25 00:35:12] [Throttled] (ProcfsScraper.cpp:444) Could not open process directory 1251653: No such file or directory
[DEBUG   2023/01/25 00:35:16] [Throttled] (ProcfsScraper.cpp:444) Could not open process directory 1252017: No such file or directory
[DEBUG   2023/01/25 00:35:22] [Throttled] (ProcfsScraper.cpp:444) Could not open process directory 1252278: No such file or directory
[DEBUG   2023/01/25 00:35:26] [Throttled] (ProcfsScraper.cpp:444) Could not open process directory 1252444: No such file or directory

The CLOG(DEBUG) on line 444 was left as is. If someone is doing debugging they probably want to see everything.


Add an annotation to add a class for reflection in native image

Currently POJOs used with reflection (such as when using JSON-B) need to be manually configured in reflect-config.json for native image.
By introducing a dedicated annotation, we could simplify this for the user.
This is valid both for Helidon SE and MP.
Example:
@Reflected
public class Pokemon {
  private String name;
}

We can add all such classes for reflection in our extension, thus removing the need to add config files.

Fixed in https://github.com/oracle/helidon/pull/2070


Upload App Preview

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I have read the Contribution Guidelines

Issue Description
I'm currently searching how to automate app previews upload, but I can't find it by reading previous issues / documentation. In the end, I'm not sure if fastlane is handling it or not. Reading #9532, I think it is, but I didn't find any documentation about it.
So, the question is simply: is it possible to upload app preview using fastlane?
Thanks!

https://github.com/fastlane/fastlane/issues/9532

@pedrodelavega I read this, but can't find anywhere how to use this :(
I mean, is there a line for this, which one? It should definitely be documented

@tbaranes Agreed that we need to document how to do this, but as mentioned in #9532 and #9660, the current implementation of this feature in fastlane is broken (and crashing) currently. When we have a working solution, we will be sure to update the documentation as part of the release process.
Thanks for the report and I'm sorry that we don't have better news for you. 🚀

Any updates on previews being supported? With iOS11 on the horizon they seem more important than ever to include.

Any news with this? As mentioned above, iOS 11 is putting greater emphasis on App Previews. I have 11 languages and previews for all device sizes. The thought of uploading all these via iTunesConnect is not a pleasant one.

I saw that #10546 has been merged an release, is there any documentation about it yet?

@tbaranes  It seems that to upload previews, it's not as simple as using Deliver. I dig a little bit and apparently you can do it using upload_trailer!(trailer_path, language, device, timestamp = "05.00", preview_image_path = nil)  which is a method inside the spaceship module. You can use Spaceship API manually if you use the command fastlane spaceship (more on this there). Of course, the goal is to automatize uploading which can be done using Fastlane for sure... but I don't know how to do it yet...

Does this get any easier now that Apple has announced support with uploading app previews on transporter?
https://developer.apple.com/news/?id=01312018a

I do think that still an interesting issue 😶


Add ext-intl for reqs

The intl ext is not a requirement, you can use it without via the Symfony Intl component.


Incorrect matrix type coersion in rowsum.y / rowsum.z

These functions use class() to cast reduced matrices to integer, when they should use storage.mode(). Under certain conditions (such as when running simulateCells()), this can cause crashes.

@joshua-d-campbell for general reference: I realized we were writing things like class(mat) = "integer" to try to coerce matrices to the right type. I then realized that class() refers more to the data structure than the type of the actual contained variables. We should use storage.mode(mat) = "integer" instead.


[WIP] Add auditable config option.

TODO:

[ ] add tests
[ ] make sure it fails gracefully if auditable = true + cargo auditable isn't available.

Just needs tests and we're good to go.

This is the current failure mode for auditable = true without cargo-auditable. I have mixed feelings about it — it's not terrible, but something like this is probably better:
Setting `auditable = true` requires `cargo auditable`. You can install it with `cargo install cargo-auditable`

Since our main build environment is GitHub Actions at the moment, and it appears cargo auditable isn't preinstalled there, we should also make sure we handle installing it before doing local builds if it's in use. That'd be more impactful for our users than just telling them they need to install it. (We should also do that for non-CI builds though!)

cargo-auditable uses dist and so we can rely on their installers for our generated workflows and locally https://github.com/rust-secure-code/cargo-auditable/releases/tag/v0.6.4

I suppose then we should also consider: do we install a floating "whatever's latest" version? Or do we pick a known-good version and update it periodically?

@mistydemeo yeah it's a good question- i could see us going either way re pin latest or pick a known good release- both of those options beg the question of a config to override version which seems prudent, because we'll likely need it either way

@Shnatsel do you have thoughts on how we handle the version of cargo-auditable we install for folks?

@ashleygwilliams I treat the CLI as the public API for semver purposes, so installing the latest version in 0.6.x series is a safe bet. That should get you bug fixes without any kind of breakage (unless I mess up really badly).
You can revisit this if/when I ship 0.7.x, which right now is not even on the horizon.

Moving to #1528 because of branch naming making it harder to test.


Multiple logging fix

This branch is having the issue where I can only log user information if they answer their own questions. Otherwise it fixed the multiple logging issue.

The unbind() looks great. Works for me:
I, [2015-09-30T21:05:35.960206 #1563]  INFO -- : User 1 answered yes for question 5
I, [2015-09-30T21:05:44.329539 #1563]  INFO -- : User 1 answered maybe for question 5
I, [2015-09-30T21:05:49.792221 #1563]  INFO -- : User 1 answered no for question 4
I, [2015-09-30T21:05:55.977208 #1563]  INFO -- : User 1 answered no for question 2

However, you'll need to remove commit f62de33, it doesn't appear relevant to this package of work. You  could do a number of things:

git revert it (adds a new commit when nullifies the effect of the reverted commit, see here)
git rebase -i HEAD~2 to remove it completely (and you'll have to do a git push --force to force your origin to accept the fact that you rewrote the history) (see here (about removing commits) and here)
create a new feature branch and git cherry-pick just the relevant commit (103d0c4) onto that one (see here)
create a new feature branch and just make the changes from 103d0c4 (there was only one line changed) and a new commit


[BUG] Average cycle time shows incorrect value

Describe the bug
Average cycle time shows about tenth of the correct value.
The problem is in TcoTaskedSequencer. StopCleanCycleTime() :

On the first cycle StopCleanCycleTime is called _LastCycleTime is T#0MS as it will only be written to by CompleteSequence which is generally called after StopCleanCycleTime. Also for the same reason there is no point calculating _cycleTimeAnalitics.Average, but we need _cycleTimeAnalitics.AverageCleanCycle.

/cib

closes #112


Add project topic "automatic-api"

Hi there! Could you add the tag topic automatic-api to your repository? I am making a list of all projects that automatically expose APIs to databases. (Your Show HN made me do it. :-) I knew about PostgREST and PostGraphQL, but it took adding Datasette to sell me on the concept.) They will be easier to discover if there is a standard GitHub tag, and automatic-api seems as good a candidate as any. Two projects already use it.

Done - thanks for curating these: https://github.com/topics/automatic-api


"@poller=XYZ" classifier seems to be ignored for some Foundry tests

This got revealed when working on https://github.com/grpc/grpc/pull/16478
bazel generates test variants with @poller=XYZ suffix, but it seems that the right poller is not always used.
Here the test is called ...@poller=poll, but logs say  Using polling engine: epollex (which is a debug message, so it's only visible if #16478 is in place).
exec ${PAGER:-/usr/bin/less} "$0" || exit 1
Executing tests from //test/core/end2end:h2_proxy_test@simple_cacheable_request@poller=poll
-----------------------------------------------------------------------------
D0828 08:42:08.516498572      19 test_config.cc:391]         test slowdown factor: sanitizer=1, fixture=1, poller=1, total=1
D0828 08:42:08.518597506      19 ev_posix.cc:170]            Using polling engine: epollex
D0828 08:42:08.519636084      19 dns_resolver.cc:338]        Using native dns resolver
I0828 08:42:08.519993015      19 simple_cacheable_request.cc:39] Running test: test_cacheable_request_response_with_metadata_and_payload/chttp2/fullstack+proxy

The test report:
https://source.cloud.google.com/results/invocations/ba912256-bc77-48f8-9102-b313d978eba3/targets/%2F%2Ftest%2Fcore%2Fend2end:h2_proxy_test@simple_cacheable_request@poller%3Dpoll/log
This is probably only happening for a subset of tests, as I saw some other tests setting GRPC_POLL_STRATEGY correctly (e.g. https://source.cloud.google.com/results/invocations/d913b5a6-36c6-4a3c-9c5a-b3b7a578b88a/targets/%2F%2Ftest%2Fcore%2Fclient_channel%2Fresolvers:dns_resolver_test@poller%3Depollsig/log)

Perhaps something is wrong with https://github.com/grpc/grpc/blob/35501ad1df5799be17cc41894a0dc1d3ed43a8f0/test/core/end2end/generate_tests.bzl#L263?  I don't see the   export GRPC_POLL_STRATEGY=xyz  in the test log anywhere.

The problem is with the shell script end2end_test.sh.
If you compare with the run_with_poller.sh, you could see that a '-z' is needed before the poller argument, yet the bazel file does not seem to include it.

See this PR
https://github.com/grpc/grpc/pull/16481

confirmed that the problem is fixed. Below is the output for the same mismatching test (//test/core/end2end:h2_proxy_test@simple_cacheable_request@poller=poll):
https://source.cloud.google.com/results/invocations/dc8f559a-96c1-409b-9228-c10972b47160/targets/%2F%2Ftest%2Fcore%2Fend2end:h2_proxy_test@simple_cacheable_request@poller%3Dpoll/log
As displayed, the polling engine is now matching.

Thanks for fixing this, Bill!


doc: autopts: Remove WSL setup

Since Zephyr SDK 0.14.0 building under Windows is supported.

The reference to the tester application zephyr/tests/bluetooth/tester/ and the step to build it seems to get lost with this change. Is that intentional?


Re-enable k8s 1.11 and disable k8s 1.12 tests

Check commits for more context.

This change is

test-me-please

What changed since we had to revert? Almost every k8s test failed with 1.11 before.

@tgraf was the failures related with 1.11 or with our flakes? I'll defer to @eloycoto if we are missing anything. But if the tests have a green pass in this PR I don't see any reason why we shouldn't merge it.

@aanm I'm happy to merge this if we can verify this PR with 5 consecutive green builds.

test-me-please

test-missed-k8s

https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/4723/ seems to have been a problem from k8s that didn't retry to create the pod after finding out cilium-cni didn't exist

test-me-please

test-me-please

LGTM, I'll approve when test pass.

ginkgo tests were hit by https://github.com/cilium/cilium/issues/4843
k8s tests passed except the k8s 1.8.15 which was requiring a new CNI version. Already change the provisioning to have a newest version of CNI for k8s 1.8.15.

test-me-please

ginkgo tests were hit again by https://github.com/cilium/cilium/issues/4843
Reverted the k8s upgrade to 1.8.15 as the packaging is broken. Will update to k8s 1.8.15 once the packaging is fixed upstream.

test-me-please

test-me-please

missed-k8s-tests had 2 green builds.
https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-K8s/533/
https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-K8s/537/
ginkgo test had a failure being tracked here https://github.com/cilium/cilium/issues/4847

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

unable to provision k8s 1.8 https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-K8s/546/flowGraphTable/

test-missed-k8s

test-me-please

@eloycoto can you look at this failure? https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/4998/ it seems kubectl apply was not perform correctly for Cilium DS with the geneve option. Better yet, it seems the previous Cilium DS was not removed.

test-missed-k8s

test-me-please

@aanm please ping me for review once the tests have stabilized; I am in agreement with @tgraf that we need consecutive stable builds for this to be validated.

test-me-please

test-me-please

hit https://github.com/cilium/cilium/issues/4850

hit https://github.com/cilium/cilium/issues/4879

test-me-please

test-missed-k8s

test missed k8s got a "NACK" test-missed-k8s

test-missed-k8s

previous missed k8s got a NACK again

test-missed-k8s

test-me-please

test-missed-k8s

hit https://github.com/cilium/cilium/issues/4879

test-me-please

hit https://github.com/cilium/cilium/issues/4879 again

test-me-please

@eloycoto @ianvernon ping for review

@ianvernon was this backported to 1.1? I don't see any reference from a backport PR and the label still says pending.


fix cardinality when params.bowtie2_index used

PR checklist
When given bowtie2_index from a param, it is read in as a value channel but when constructed from bowtie2 build it's a
 [ [:] , path(bowtie2/index/) ]. Meaning it's missing the meta.

[x] This comment contains a description of changes (with reason).
[x] If you've fixed a bug or added code that should be tested, add tests!
[x] If you've added a new tool - have you followed the pipeline conventions in the contribution docs

[x] If necessary, also make a PR on the nf-core/viralrecon branch on the [nf-core/test-datasets] (https://github.com/nf-core/test-datasets) repository. (https://github.com/nf-core/test-datasets/pull/1300)

[x] Make sure your code lints (nf-core lint).
[x] Ensure the test suite passes (nextflow run . -profile test,docker --outdir <OUTDIR>).
[x] CHANGELOG.md is updated.
[x] README.md is updated (including new tool citations and authors/contributors).

Fixes https://github.com/nf-core/viralrecon/issues/440


Shelly 2.5 Roller linked via Hubitat showing up in Google Home as a dimmer

Shelly 2.5 Roller linked via Hubitat showing up in Google Home as a dimmer. Is there a way to have the driver tell Google Home that the device is Blinds/Shades or at least not a light?

No as that is controlled by Hubitat's Google Home interface.


How would you project a field out of a nested object?

Say that my data looks like:
[
  {
    "title": "Pull Request Title 1",
    "repository": {
      "nameWithOwner": "org/repo"
    },
    "author": {
      "login": "isaacsanders"
    }
  },
  {
    "title": "Pull Request Title 2",
    "repository": {
      "nameWithOwner": "org/repo"
    },
    "author": {
      "login": "yesoreyeram"
    }
  }
]

How would one generate a table in Grafana that looks the table below?

Title
Author
Repository

Pull Request Title 1
isanders
org/repo

Pull Request Title 2
yesoreyeram
org/repo

Right now I have a pile of Jsonata, but I don't prefer it much.

Use dot inside the double quotes to access a field.
parse-json
| project "Title", "Author"="author.login", "Repository"="repository.nameWithOwner"

Much appreciated! I’ll close this tomorrow if I can make it work!


Dircheck

…ries
Pull Request
Description
This change adds a function to utils.py that checks whether a provided path leads to a directory or just a file
The aforementioned function is then added to the top of app.py to check whether save_dir and/or save_dir_native are valid paths
I want to add this change because this will save resources in case you input a bad path. Otherwise the script proceeds to make expensive API calls to EUMETSAT etc. to then fail at the very end when it tries pushing files to the provided save_dir and/or save_dir_native paths.
This has not been put on the issues page
How Has This Been Tested?
The following list shows the 3 save_dir paths that been given as arguments and their results after this PR's changes:

A save_dir path that leads to a directory, satip continues executing
A save_dir path that leads to a file, satip logs the error and halts execution
A save_dir path that doesn't lead to a file or directory, satip logs the error and halts execution

Checklist:

[x] My code follows OCF's coding style guidelines
[x] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[x] I have checked my code and corrected any misspellings

Apologies, the name of the branch does not detail what this PR does!

@all-contributors please add @jsbaasi  for code


Repair script can fail if run on multiple instances with same set of repair targets

The repair script is not safe to run on among multiple instances in an AZ at once. There should be some concurrency control to prevent multiple instances from attempting to perform the repair simultaneously. Consider acquiring a mutex, using some sort of work queue, etc.

I'm not so familiar with PowerShell so I may be wrong but I attempted to iterate over the instances in a loop, so they should  not be handled in parallel.
Parallel handling would be difficult because we would have to  use multiple device names and each with its own drive letter.
Again, I have no infrastructure to test this against but my assumption was that the D: drive would be reused for all the volumes.

By "instances" I mean the instances on which the repair is being performed. If the issue I described in #1 occurs, then the repair instances could end up targeting the same instances simultaneously. IOW the loop variables containing the repair targets will be identical.

I see, I now have code that ditches the ASG and creates individual instances, and the Powershell script will terminate the instances after it finishes running.
I also have a test mode that creates a test instance and attempts to run against it.
Now running a few tests against that instance and I'll push the changes as soon as I have it working as expected

Resolved, just pushed the code that removes the ASG and uses individual instances.


Make createdAt, updatedAt optional

 Issue by mavilein
Thursday Sep 07, 2017 at 11:47 GMT
Originally opened as https://github.com/graphcool/api-bugs/issues/257

the user does not have to specify in the types.graphql file
it is still created in the background in the database
ideally it would not be visible in the Client API

So maybe we have to add an isVisible flag to our Fields data structure.

This is now fixed 🙂
The field is not there from the start, once it's added, the values are there. It can be removed and added, and the values will still be there.
fields need to be createdAt: DateTime! and updatedAt: DateTime!.


fix(version): update ngx-fabric8-wit to 6.17.2

@fabric8cd snapshot fabric8-ui is deployed and available for testing at https://fabric8-ui-fabric8-ui-pr-1586.int.rdu2c.fabric8.io


Multiple Azure Subscriptions: Deployment script not providing the option to select a different subscription

When running the deployment script in an environment with multiple subscriptions it picks just one of them. It should prompt the user to select the subscription in case multiple subscriptions are detected and allow the user to select the correct subscription

Fixed


drivers: eth: native_posix: get if_name from env var

Reasoning
Iface name which is used by native posix ethernet driver can only be specified at compile-time. I wanted to run two instances of the same program on native posix but did not want to make two separate builds only to change the iface name. I have implemented getting the iface name from environmental variable.
If it does not find the specified variable it falls back to CONFIG_ETH_NATIVE_POSIX_DRV_NAME
Example usage
prj.conf
CONFIG_ETH_NATIVE_POSIX_GET_DRV_NAME_FROM_ENV=y
CONFIG_ETH_NATIVE_POSIX_DRV_NAME_ENV_VAR="ZETH"

Invocation
ZETH=zeth0 ./zephyr.exe &
ZETH=zeth1 ./zephyr.exe &

@aescolar surely a command line option could be a nicer alternative. I was not aware if there was a way to get command line options inside zephyr application. If there is then i can rewrite it.

@aescolar surely a command line option could be a nicer alternative. I was not aware if there was a way to get command line options inside zephyr application. If there is then i can rewrite it.

This is how the API is used:
https://github.com/zephyrproject-rtos/zephyr/blob/main/drivers/input/linux_evdev.c#L28

Ok so as an alternative to environmental variable I could use command line option.
My proposition would be a --iface-name or --eth-iface option and you'd activate it by CONFIG_ETH_NATIVE_POSIX_DRV_NAME_FROM_CMD_LINE=y.
Of course It could also be enabled by default.
I'll wait for opinion of other reviewers.

@jukkar ^^

My proposition would be a --iface-name or --eth-iface option and you'd activate it by CONFIG_ETH_NATIVE_POSIX_DRV_NAME_FROM_CMD_LINE=y

No big preference, the --iface-name sounds fine to me.

One thing to remember, this new cmd line option + its usage + use case should be documented somewhere, otherwise no one is able to figure this out. Probably https://docs.zephyrproject.org/latest/connectivity/networking/native_sim_setup.html is a good candidate to add this info. Could you add a commit to this PR that does that?

I have made the changes you requested. I've settled on --eth-if option name, since --iface-name does not say if this is an eth interface or for example can.
@jukkar @aescolar take a look and tell me if it looks good (including the docs)


Roadmap

Tests:

[x] Using GoConvey for Behavior Driven Tests/Development

Post:

[ ] Post category #3
[ ] Post cover image #2
[ ] Post sharing link

Others:

[ ] Messages
[ ] Search

Dashboard:

[ ] Page view
[ ] Top pages

Front-end:

[ ] Tidy SCSS files #4
[ ] Rewrite admin dashboard using AJAX #5

Model/Database:

[x] Tidy sql_stmt.go
[ ] Migration from Ghost

API:

[ ] Restful API support #6

@dinever I've got some free time over the next few days to work on #6 here, and it'd be great to get a few more details on what you're looking for.

@samdfonseca Let's try to implement /api/posts first. We can have several parameters to filter the result. For example:
/api/posts?page=1&limit=5&order=published_at should return the first 5 posts order by the field published_at

@samdfonseca wanna work together, or split the work up on the API? I was going to work on it for awhile tonight, I'm on the Gophers Slack if you want to communicate there

@bentranter yea that sounds great. i went ahead and make a dingo gitter room (https://gitter.im/dingoblog) but if slack works better for you im down to use that

Do we have a plan to manage all the vendor packages?
There are some Go package management tools to choose:
Godep
Govendor
godm
vexp
gv
gvt - Recursively retrieve and vendor packages.
govend
Glide

I happened to see on my GitHub feed that @samdfonseca created a vendor branch the other day with Godep (creepy I know, haha). I think I've tried every vendoring tool so far and don't really have a preference, but Godep is a good one. Makes it really easy to update vendored packages too which is nice.

Yep, I tried both Godep & Glide they are both good options.

haha i thought i snuck that in @bentranter. yea that was made out of frustration ive been having dealing with different versions of dependencies. let me know if i should pr it and ill sort out any conflicts if there are any.

@samdfonseca I think you should PR it, I'm cool with using Godep


Load all audio files on all messages page (pagination had been broken…

…), closes #228

Can we merge this, @daguar? Or does this merit further deliberation during City Voice O'clock?

There's some problems with the tests so I want to take a closer look. I'm likely to merge anyway for now because they don't appear to have anything to do with this PR, but rather with Travis changes I made recently.

@jmadans this is merged.


Error trying to queue 3450 songs at once

Is fragmented messages just not supported in yawl or something?
web socket error: Error: fragmented messages not allowed
    at failConnection (/home/josh/dev/groovebasin/node_modules/yawl/index.js:848:13)
    at WebSocketClient._transform (/home/josh/dev/groovebasin/node_modules/yawl/index.js:448:13)
    at WebSocketClient.Transform._read (_stream_transform.js:179:10)
    at WebSocketClient.Transform._write (_stream_transform.js:167:12)
    at doWrite (_stream_writable.js:225:10)
    at writeOrBuffer (_stream_writable.js:215:5)
    at WebSocketClient.Writable.write (_stream_writable.js:182:11)
    at write (_stream_readable.js:601:24)
    at flow (_stream_readable.js:610:7)
    at CleartextStream.pipeOnReadable (_stream_readable.js:642:5)
    at CleartextStream.emit (events.js:92:17)
    at emitReadable_ (_stream_readable.js:426:10)
    at _stream_readable.js:419:7

Interesting. They're supported but I did not realize the HTML websocket API would automatically change the type of large messages to fragmented. This is easily solved.


Annotation start time overflow

Using pyedflib 0.1.17. In EdfWriter.writeAnnotation, it uses np.round(onset_in_seconds*10000).astype(int).   This only allows for onset_in_seconds up to 4.97 days before it overflows int, which is really int32, and bonks. If the data is longer than 4.97 days, and there are annotations that need to go there, how can one write annotations that won't overflow?

Is there a reason you need to use v0.1.17? newest version is v0.1.37
This has been changed to int64 in https://github.com/holgern/pyedflib/pull/176 , so pyedflib>=v0.1.31 supports it


FirebaseDatabase.DefaultInstance.GetReference(".info/connected") not working for Android build

[REQUIRED] Please fill in the following fields:

Unity editor version: 2020.3.25f1
Firebase Unity SDK version: 8.7.0
Source you installed the SDK: .unitypackage
Problematic Firebase Component: Database
Other Firebase Components in use: Auth, Analytics
Additional SDKs you are using: Facebook, AdMob
Platform you are using the Unity editor on: Mac
Platform you are targeting: Android
Scripting Runtime: IL2CPP

[REQUIRED] Please describe the issue here:
My game checks the connection to the realtime database as follows:
`.     using UnityEngine;
using Firebase.Database;
public class NoInternetPanel : MonoBehaviour
{
public GameObject noInternetPanel;
DatabaseReference connectedRef;
bool isConnected;
private void Start()
{
    connectedRef = FirebaseDatabase.DefaultInstance.GetReference(".info/connected");
    connectedRef.ValueChanged += CheckInternetConnection;
}
private void OnDestroy()
{
    connectedRef.ValueChanged -= CheckInternetConnection;
}

public void ActivateNoInternetPanel()
{
    noInternetPanel.SetActive(true);
}

public void CheckInternetConnection(object sender, ValueChangedEventArgs a)
{
    isConnected = (bool)a.Snapshot.Value;
    if(isConnected == true)
    {
        noInternetPanel.SetActive(false);
    }
}

}`
This has been working perfectly for my iOS release this past year, but now that I'm trying to release for Android, it is not working correctly. At almost exactly 1 minute after launching the game, isConnected returns false. Everywhere I look, this seems to be the way to check the connection, and like I mentioned it works on my iOS release of the game. Is there something specific to Android that needs to be done differently either in my code or in the Firebase setup? Completely stuck on this! Many thanks for any help

Hi @rozatlabs, thanks for your report. We'll investigate this and see what we can find.

Hi @rozatlabs, thanks for your report. We'll investigate this and see what we can find.

Thank you for looking into it, any update to this issue?

Hi @rozatlabs,
I've tested your code on an Android build, and I haven't encountered the behavior you described. To be specific, isConnected was set to false or a second, and then it stayed true afterwards. Are there other steps that have to be taken into consideration when trying to replicate this issue?

Hi @paulinon, thank you for looking into it. No other steps needed as far as I am aware of. At what point was isConnected set to false? I was experiencing the issue approx 1 min after app launch. Is there a reason it would be returning false on Android and not iOS?

Hi @rozatlabs,
After the Android app was launched, isConnected is observed to be false for a second, and then it became true right after. There were no changes observed after a few minutes or so. I've tested this on an iOS build, and it shows the same behavior.
It's possible that the network connectivity is causing the issue. Could you try if changing the network shows any difference? Additionally, is there any data that is needed to be stored in the database before launching the app?

Hi @rozatlabs,
After the Android app was launched, isConnected is observed to be false for a second, and then it became true right after. There were no changes observed after a few minutes or so. I've tested this on an iOS build, and it shows the same behavior.
It's possible that the network connectivity is causing the issue. Could you try if changing the network shows any difference? Additionally, is there any data that is needed to be stored in the database before launching the app?

Changing networks from wifi to mobile has same result, after 1 min isConnected returns false. No data needing to be stored before launching. At launch, my app checks database connection and compares timestamps of a user’s last login. That part is working correctly at launch so I know I’m getting a connection. But still after 1 min it returns false.
Just to be sure my listener was working properly, I launched the app, quickly put the device in airplane mode (causing isConnected to return false momentarily) then disengaged airplane mode and isConnected returned true again. So this means isConnected is continuously returning false after 1 minute, until I close the app and relaunch. Does that help narrow things down at all?

Hi @rozatlabs,
Thanks for the additional information. I've also observed this behavior during testing.
Could you verify if this issue persists on other Android devices as well? If so, please provide debug logs from the Android Logcat from app launch to the moment isConnected becomes false so that we can analyze what's causing this.

My apologies for the delay, I've been trying to track down things on my end as much as possible so as not to waste anyone's time/efforts here, however I'm still unable to track down the issue. I unfortunately only have a Samsung Galaxy A32 for testing, but here is the most recent logcat. In Update(), I printed the status of isConnected so you can see when it changes (apologies for this causing it to be quite verbose)
When I create a new player profile, it successfully creates a new auth account, as well as realtime database nodes like the iOS release, so the connection is working properly at that point. I'm stumped as to why it's returning false seemingly randomly. Thanks for your help tracking this down, I hope the logcat helps!
Android logcat 01.31.odt

Thanks for this, @rozatlabs. Version 8.8.0 of the SDK has been released recently. Could you try this version and see if this fixes your issue? If it doesn't, please provide a new set of debug logs so we can analyze what's causing this.

The updated SDK seems to have solved the connection issue! Much appreciated

Glad to hear this, @rozatlabs. That being said, I'll be closing this for now.


run.py referencing missing file

https://github.com/abertsch72/unlimiformer/blob/main/src/run.py#L72
Should this be checked into the repo or is it only meant to be read and not executed?

Hi @stakodiak ,
Thank you for your interest in our work!
Sorry, I will fix this and include all the needed files.
Best,
Uri

Fixed! Please let us know if you have any questions or problems @stakodiak .
Best,
Uri

I'm closing this issue just to make sure we respond to all issues, but feel free to re-open it if you have any questions!


Parallax: background problem when reducing window height

Tested only on Chrome V54 - Windows 10.
When you first load the page, everything works fine. But as soon as you reduce the height of the browser window, white space starts showing up everywhere. Same problem doesn't happen when resizing horizontally.

Thanks for the report. Someone mentioned this on Twitter, I believe. We'll take a look!
/cc @flackr and @surma


Update build-script examples to show new Makefile include where applicable

This is ready for review. Sorry, it's a big one. That helper makefile touches on a lot of documentation.


Fix: changed geojson mimetype

Overview
Closes #528
(as per https://github.com/geopython/pywps/blob/master/CONTRIBUTING.rst#contributions-and-licensing)

[x] I'd like to contribute [feature X|bugfix Y|docs|something else] to PyWPS. I confirm that my contributions to PyWPS will be compatible with the PyWPS license guidelines at the time of contribution.
[x] I have already previously agreed to the PyWPS Contributions and Licensing Guidelines

Coverage remained the same at 74.26% when pulling d39778bc82f34258c3762df3564ac54835a37be1 on fix-223 into 6cfd071fb3b45166fdc9db472e2669042dc7434f on master.

@huard thanks :)


MySQL server has gone away

I get this error from time to time:

SQLSTATE[HY000] [2006] MySQL server has gone away

I just re-run the job multiple times until it works.
This is my conf for MySQL setup:
- name: Setup MySQL
        uses<EMAIL_ADDRESS>        with:
          mysql database: test
          mysql user: test
          mysql password: test

I got the same error when switching from mysql 5.7 to 8.0. Reverting back to 5.7 fixed the issue. @mehdibo did you find a solution to the problem other than reverting back to 5.7?

No, I always had the issue, it would work for sometime and then randomly stops working.
I eventually switched to Travis Ci.
Try building your own docker container, I remember using Github Actions with docker-compose that had a db container and it worked fine.

Adding a sleep 15 command to wait for the mysql server to become available fixed this issue for me
- name: Wait for MySQL
  run: sleep 15

I agree with @almasaeed2010
When i had to make a pipeline for GitLab CI i use the following code before my test execution because sometimes the MySQL service fails.
# Ensure that mysql server is up and running
ping -c 3 mysql

But sleep 15 will lock the docker instance for sure. Adding static cost for the CI process, a better solution than retry the execution hoping that works as a magic trick.

After a lot of time with inconsistent errors, I did this:
(...)
env:
      MYSQL_ROOT_PASSWORD: password

    steps:
      (...) first steps, but the sooner you call MySQL, the better

      - name: Setup MySQL
        uses<EMAIL_ADDRESS>        with:
          mysql root password: $MYSQL_ROOT_PASSWORD

      (...) all other things that don't need MySQL

      - name: Wait for MySQL
        run: |
          while ! mysqladmin ping --host=<IP_ADDRESS> --password=$MYSQL_ROOT_PASSWORD --silent; do
            sleep 1
          done

      (...) steps where you need MySQL

If you think it is a good approach, I don't have a problem adding this note in the README file (and doing a PR) so new users don't waste time.

better add some timeout as well @NBajanca

That should definitely added to README.txt to avoid waste of time.

You may need to add this option:
-P 3800

If you are using:
host port: 3800


Doom upgrade (or refresh or doctor or any) does not work

What did you expect to happen?
I'm having endless problems getting things to work correctly.  I tried various of the doom commands and they stop running with various errors.  The latest is: "Cannot open load file: No such file or directory, subr-x
What actually happened?
I was hopiing for a refresh that would fix a bad file or something.  Doom doctor takes about  10 minutes to run then stops with an error:
The doctor will see you now...

> Checking your Emacs version...
> Checking for Emacs config conflicts...
> Checking for private config conflicts...
> Checking for stale elc files...
x There was an unexpected error:
  Type: error
  Message:
    error
  Data:
    "Variable binding depth exceeds max-specpdl-size"

Run the command again with the -d (or --debug) switch to enable debug
mode and (hopefully) generate a backtrace from this error:

  doom -d doctor

If you file a bug report, please include it!

Of course, there is nothing more included by way of a backtrace or other info when I run with the option.  I'm also puzzled by the giberish mixed in with the text in the message.  (I'm running that in Ubuntu under Windows 10, and Emacs 26.3 under Windows 10).
Additional details:

Include a link to your private config

I don't know what a private config is!

Include screenshots/casts of your issue
If you mention key sequences, include what commands they're bound to (use SPC h k KEY or C-h h k KEY to inspect keys).
Include any warnings or errors logged to *Messages* (use M-x view-echo-area-messages to see it).

From the latest Messages
Doom loaded 157 packages across 29 modules in 6.001s
Failed to load git-commit package incrementally, because: (file-missing Cannot open load file No such file or directory rmail-loaddefs)
Failed to load magit package incrementally, because: (file-missing Cannot open load file No such file or directory rmail-loaddefs)
Failed to load calendar package incrementally, because: (file-missing Cannot open load file No such file or directory cal-loaddefs)
Failed to load org package incrementally, because: (file-missing Cannot open load file No such file or directory cal-loaddefs)
Failed to load org-agenda package incrementally, because: (file-missing Cannot open load file No such file or directory cal-loaddefs)
Failed to load org-capture package incrementally, because: (file-missing Cannot open load file No such file or directory cal-loaddefs)
Failed to load org package incrementally, because: (file-missing Cannot open load file No such file or directory cal-loaddefs)

In trying to add the info you request, I note that no version of Doom runs under my Ubunu now.  I get the same message about the subr-x directory or file missing.
Steps to reproduce:

I had a whole several days of different problems before I attempted Doom upgrade.  The problems I'm describing relate to that.  I tried Doom upgrade and doctor to try to fix a broken or missing file.  Before that I backed out configuration chages thinking that might help.  Of course, there are so many configuration/init files in so many directories I'm not sure if I got them all.  It sure would help to have a list of them all and where they are supposed to live.

This is just the latest of my battles.  Prevously I reinstalled Emacs 26.3 several times and then followed the Doom instructions to install that.  When I saw Doom Doctor I thought this might be a general fix it tool for damaged or missing files.  It does not seem to help ... though it looks like it is trying.
One thought forming in my mind now is that there may be some data entry that points to installation directories and it is getting confused because I installed so many times.  Perhaps it is just confused?  Is there some data item that I could delete that would cause Doom Doctor (or other) to realize that it can't make assumptions?
System information:
From doom info:
Warning: arch-dependent data dir 'c:/Users/mikes/.emacs.d/libexec/emacs/26.3/x86_64-w64-mingw32/': Invalid argument
Cannot open load file: No such file or directory, subr-x
Warning: arch-dependent data dir 'c:/Users/mikes/.emacs.d/libexec/emacs/26.3/x86_64-w64-mingw32/': Invalid argument
Cannot open load file: No such file or directory, subr-x

That's the best I can do with my level of experience and the confused mess I find this to be right now.  Any help you can provide will be appreceated.

These are a lot of weird issues. Many of them complain about missing rmail-loaddefs, cal-loaddefs and subr-x files. I suspect a bad Emacs install, because these are all built-in libraries. i.e. They come included with Emacs.
As I'm not a Windows user, and my Emacs-on-Windows-fu is limited, I can only relay what these installation instructions from other happy Doom+WSL+Ubuntu users. Perhaps they can help:

Setting up Emacs + WSL: https://github.com/hubisan/emacs-wsl
Installing EMacs + Doom without WSL: https://earvingad.github.io/posts/doom_emacs_windows/
https://ethanaa.com/blog/switching-to-doom-emacs/#activate-wsl-and-install-ubuntu-18-04-lts

As of 976a601 I've expended on Doom's documentation for installing Emacs and Doom on windows, which I hope will prevent issues like these in the future. In any case I will consider this resolved.


Better compiler diagnostics (error messages, warnings, hints, etc.)

There is a lot to be done in this area. I would say we should target the level of diagnostic achieved by Rust.
Also, here are some excellent references, collected by @ironcev while working on this RFC for the Sway smart contract language (thanks Igor <3).

Expressive Diagnostics
Shape of errors to come
Compiler Errors for Humans
Compilers as Assistants
Concepts Error Messages for Humans
Compiler Error Messages Considered Unhelpful: The Landscape of Text-Based Programming Error Message Research
Usability improvements in GCC 8

If anything, it would be nice to have unified structure for error messages, such that they can be reliably parsed in tools, such as tact.vim, tact-vscode or linters & such.
Maybe, as a first step on this path Tact should make either a programmatic (import {...} from '@tact-lang/compiler') or a CLI (tact --...) way to output all compilation issue in some machine-readable format (such as JSON, for example). That would remove the current need in parsing error messages by hand (on the user-side), and thus drastically simplify the work for tool makers.
And once that done, proceed think about making unified and user-friendly messages for the stdout.
cc @anton-trunov @byakuren-hijiri what do you think?

@novusnota Yes, having a centralized data structure for all error messages is what we should go for

A good addition to that list:

The Syntax Cliff, from Elm language blog — discusses how to make syntax error messages so nice, that they're actually tutoring the language to people!
Error Message Catalog of Elm, where is a bunch of suggestions and implemented fixes (see closed issues) on error messages: their clarity, readability, preciseness.

There's another language, which also excels at developer experience — Gleam. I didn't see the them do similar discussions on error messages in their blog, though they are very concerned about good tools and convenience of using them and the language — take a look at their 1.0 release package: fledged language design, compiler, build tool, formatter, package manager, language server (LSP spec), and various bindings to WASM/JS. And all those are built-in the compiler binary! Plus, an interactive tour, like seen in Golang and Elm. Btw, it would be nice to make something similar in Nujan, although we have cool https://tact-by-example.org already.
And a bunch of other tools too, I'll post them here for completeness (and later reference):

VSCode extension (as a wrapper around the language server binary)
Tree-sitter grammar
Vim support
Emacs support
And unofficial Sublime Text support

If anything, it would be nice to have unified structure for error messages...

Suggestion: Start with parsing Ohm's syntax error messages, instead of simply adding additional info on top. That way we'll have a structure for representing syntax errors inside the compiler, which may later get re-used for semantical errors, build errors, warnings or hints.
Because at the moment,output of check() from @tact-lang/compiler is not much different from Ohm's output, which isn't helpful for the programmer (at least in the following example):

P.S.: The syntax error with internal() instead of receive() is done intentionally :)


Fix broken documentation links

Note: I am using relative paths ... not sure if that's the way you handle this ;).

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "fix-experimental-doc-links" git@github.com:yoanisgil/docker.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

LGTM. Thank you!
/cc @thaJeztah, @moxiegirl

PS: This PR and #14963 are complementaries.

LGTM

Actually, these features are now (or coming with 1.8) no longer experimental, so, either they should be removed from this list, or a new heading should be added, e.g, "Previously experimental features" (perhaps a better title)
@moxiegirl any preference? I'm leaning towards adding a new heading, so that people landing on this page know what happened to an experimental feature.

@thaJeztah I'd prefer to remove them once they are no longer experimental.  Keeping an old list around seems like extra work --- we already have the material in the new docs.

@moxiegirl sgtm (agreed, maintaining could be an issue)
@yoanisgil could you up date your PR, and remove the links instead?

So we need to identify which of these features are no longer experimental
(I.e they are already present in master) and which one are not. Right ? Is
there an easy way to tell them apart. If not maybe someone with far more
knowledge of the project could help.
Le vendredi 24 juillet 2015, Sebastiaan van Stijn<EMAIL_ADDRESS>a écrit :

Actually, these features are now (or coming with 1.8) no longer
experimental, so, either they should be removed from this list, or a
new heading should be added, e.g, "Previously experimental features"
(perhaps a better title)
@moxiegirl https://github.com/moxiegirl any preference? I'm leaning
towards adding a new heading, so that people landing on this page know what
happened to an experimental feature.
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/pull/14961#issuecomment-124728346.

@yoanisgil Both features are no longer experimental and can be removed from this page. The links should have been removed as part of https://github.com/docker/docker/pull/14659, but we missed that during review, so thanks for spotting that :-)
In future we should just pay better attention that the links are removed as well :-)

Oh! These links are now removed in https://github.com/docker/docker/pull/15106, which makes this PR redundant.
I'll close this PR, but thanks for contributing @yoanisgil, much appreciated!


Incorrect dependency bundling when some related dependencies have additional CPE's

https://github.com/jeremylong/DependencyCheck/blob/25f60ec8bd23ae89d0183ee57ba7f8223d4f230a/core/src/main/java/org/owasp/dependencycheck/analyzer/DependencyBundlingAnalyzer.java#L295C57-L295C57
We have a scenario where cxf-rt-core-2.2.3.jar is identified by cpe:2.3:a:apache:cxf:2.2.3:*:*:*:*:*:*:* alone.
Under cxf-rt-core-2.2.3.jar the relatedDependencies contains 11 items.
However there are 2 additional jars:

cxf-rt-databinding-aegis-2.2.3.jar identified by 2 CPE's - cpe:2.3:a:aegis:aegis:2.2.3:*:*:*:*:*:*:* cpe:2.3:a:apache:cxf:2.2.3:*:*:*:*:*:*:*
cxf-rt-transports-http-jetty-2.2.3.jar identified by 2 CPE's - cpe:2.3:a:jetty:jetty:2.2.3:*:*:*:*:*:*:* cpe:2.3:a:apache:cxf:2.2.3:*:*:*:*:*:*:*

In this scenario aegis:aegis and jetty:jetty have 0 CVE's but the fact that they are listed under the CPE list it makes the bundling logic return a false, and as a side effect of it these 2 JARS report all the CVE's that cxf-rt-core-2.2.3.jar has 2 additional times.
I can see multiple ways of approaching this. Maybe a quick fix would be to ignore CPE's that have 0 vulnerabilities and therefore allowing the CPE's that do have vulnerabilities to be bundled alongside the core jar.
Another fix (albeit a bit more of an architectural change) would be to change the top level grouping to the CPE instead of the JAR and this would stop different CPE's from interfering with any bundling logic since they would work independently of each other. This would fix the issue when more than 1 CPE have vulnerabilities attributed to the same jar.

I think neither approach would be 'correct'.
The jars belong to only a single CPE (the notion of CPE registry is that entry has a 1:m link to software artifacts (sometimes one jar, sometimes multiple, depending on how 'applications' (the item that the cpe:a entries identify) are bundled up.
Due to how DC works with fuzzy-matching it will not always match the correct CPE (and sometimes match more than one for a single jar). The 'correct' way to clean up the report would be to tell DependencyCheck to ignore the 'wrong CPE of those jars.
As the jars appear to be from the Apache CXF project the way to clean it in my view is by suppressing the jetty repectively aegis CPE as a false positive CPE-match (CPE suppression) for the libraries, which then will get them bundled up with the main cxf jar, as there will only remain a single CPE.


How to change pod_player playback speed?

i use youtube and vimeo player
but my podcontroller is not change speed..
How to change pod_player playback speed?

I found a work around. Check issue #127


Bug: monthCalendarView.findFirstVisibleDay()?.date & weekCalendarView.findFirstVisibleDay()?.date returns null after setup the calendar

Library information:

Version: [2.2.0]
View or compose module: [View]

Describe the bug**
I am using Example 1 from the view module and encountered one bug. Once the setup method is called for the monthly and weekly calendars, when I try to get the first & last visible day using monthCalendarView.findFirstVisibleDay()?.date or weekCalendarView.findFirstVisibleDay()?.date, it always returns null.
To Reproduce (if applicable)
Steps to reproduce the behavior:

Go to Example 1
Log the monthCalendarView.findFirstVisibleDay()?.date  or weekCalendarView.findFirstVisibleDay()?.date after the setup. It will be null. The same goes for the last date.

Expected behavior (if applicable)
It should return the first/last date
Can you please look into it, and provide a fix or workaround?
Thanks for the fantastic library!

After the setup, the calendar still needs a layout pass to determine the first/last visible days. Did you try with
calendarView.post {
// find day here
}

Yes, It worked. Thanks


bug(tabs) "dynamic" content disappears when clicking thru tabs

Bug:
Dynamic content(bindings, child components) is rendered only on the first load, when you click on another tab, content never renders there and when you click back to the initial tab, it's gone as well.
What are the steps to reproduce?
http://plnkr.co/edit/cnLk1AuEJzfrG5agxIJe?p=preview
click on Bar and then back on Foo tab.
Which versions of Angular, Material, OS, browsers are affected?
rc.4, alpha.6

@fxck Can you confirm if this can be recreated with the latest version of Angular and Angular Material?  I am not able to recreate this issue with the latest code.

Is there a plunker with latest version?

+1
I'm getting the same bug with the latest version.

The content will show if you click the same tab a second time.

+1

@csepmdat why and how did you manage to unassign @robertmesserle huh.
@jelbourn ?

@fxck Sorry but I have no idea. That was an accident somehow.
@jelbourn Can you reassign him please. Sorry.

Not sure why GitHub displays it that way, but Robert was unassigned since he's no longer working on Angular.

This appears to be working in the latest version, closing..


other distro support

at first: thanks for this great program. i really appreciate it, i have not found another program that is as good as this.
My problem that i have is that there is only a .deb.
I would really appreciate it if you would also provide a .rpm for Fedora/RHEL Users and an AUR for Arch users.

also i have custom font settings that dont work because it uses the root user to run. One thing that i noticed lately is that (if you install vmware workstation) you can run "vmware-netcfg" and it asks in a Gnome GUI for admin permissions

and then it also uses the custom fonts that i set. When i run it with sudo it doesnt. So that somehow works too.
Btw im not a coder, else i would probably do some PRs but im really not into coding lol

Hi,
Thanks, I will look into that custom font settings issue and I am currently looking for help for packaging for other distros.
Meanwhile, can you explain more about the "lag" that you are experiencing?

sure, i figured out its only while using fakeroot. Everything is fine when just running it normally. But the issue was that it just kind of freezed all the time, it just wasnt reacting to my mouse clicks and also i think i couldn't move the window around. Im using Fedora 33 with Gnome on Wayland.

I would like to request a .appimage file. This way we could use SysMonTask on any distro before distribution-specific packages get released (if any). If you were thinking about snap or flatpak then please hold on because both are really bad for various reasons (flatpak is better IMO)

Yes, I think deb or snap or flatpak package is good alternatives as well

Hi all,
The AUR and RPM package has been made and published. The instructions are in the readme.

It's cool seeing progress in this area.
However, supporting Fedora 35 which is still in development is not everything.
Rather than building for the most recent distributive, it's better to built for reasonably-old-enough distributive as package can then be installed on more recent distributives as well due to backward compatibility of libraries.
For example, I'm on Fedora 32 and package for Fedora 35 won't work on my system. Contrary, package for Fedora 32 will work on 35.

It's cool seeing progress in this area.
However, supporting Fedora 35 which is still in development is not everything.
Rather than building for the most recent distributive, it's better to build for reasonably-old-enough distributive as package can then be installed on more recent distributives as well due to backward compatibility of libraries.
For example, I'm on Fedora 32 and package for Fedora 35 won't work on my system. Contrary, package for Fedora 32 will work on 35.

The package build request has already been sent. It will take some time to appear in  f33 and f34 repos.

If you were thinking about snap or flatpak then please hold on because both are really bad for various reasons (flatpak is better IMO)
AppImages are cool because it runs everywhere without you having to install anything, but flatpaks are also really cool, they just work and for example in the spotify package, they fixed a bug thats still to this day in the repo/binary version. Im using flatpak on fedora, maybe its just fedora that integrates it really well, since its also preinstalled i think, but flatpak isnt really that bad as you think.

I use flatpacks too but don’t like them mainly because themes don’t work and also sometimes some features.  Appimages are great but sadly they don’t integrate with system well eg you can’t just type it’s name in the xfce app menu to launch it.

So, Fedora has very old 1.1.1 which crashes a lot
➜  ~ rpm -qa sysmontask
sysmontask-1.1.1-0.5.beta.b.fc33.noarch

Is there a way to ensure automatic builds of recent versions? I'd like 1.3.9 but I don't want to install from source.

So, Fedora has very old 1.1.1 which crashes a lot
➜  ~ rpm -qa sysmontask
sysmontask-1.1.1-0.5.beta.b.fc33.noarch

Is there a way to ensure automatic builds of recent versions? I'd like 1.3.9 but I don't want to install from source.

Hi,
You can track the status of rpm build for sysmontask here
Also, I have included the RPM package file in the releases.

I use flatpacks too but don’t like them mainly because themes don’t work and also sometimes some features.  Appimages are great but sadly they don’t integrate with system well eg you can’t just type it’s name in the xfce app menu to launch it.

AppImages can be integrated and searched for in the start menu, if you can install AppImageLauncher.

I use flatpacks too but don’t like them mainly because themes don’t work and also sometimes some features.  Appimages are great but sadly they don’t integrate with system well eg you can’t just type it’s name in the xfce app menu to launch it.

AppImages can be integrated and searched for in the start menu, if you can install AppImageLauncher.

Maybe snapcraft is a better idea?


sphinx: add requirements.txt to keep track of dependencies

Most sphinx projects have a requirements.txt at the root of their doctree to list sphinx extensions and their versions, currently that's just hidden in the form of a pip install command in jobserv that is pasted twice and doesn't have versions for the packages.
Jobserv will now run pip install -r ./requirements.txt and if we need to add extensions they'll be added to requirements.txt instead of updating the jobserv.yml
I've based the versions in requirements.txt on the latest, since that's what I have been using on my machine and seemingly has no regressions in the html output from what I see hosted online now. However, the actual versions that are being used by jobserv are not listed anywhere.
sphinx-rtd-theme==0.5.0
sphinx==3.1.2
sphinxcontrib-contentui==0.2.5

From jobserv:
ERROR: Invalid requirement: './requirements.txt' Hint: It looks like a path. It does exist.The argument you provided (./requirements.txt) appears to be a requirements file. If that is the case, use the '-r' flag to install the packages specified within it.

I have no idea how I missed that lol. Are force pushes okay?

Docs for b00a1481c3dfb5b78dede19b0cf836f3563f0851 are browesable at: https://ci.foundries.io/projects/fio-docs/builds/483/docs/artifacts/html/index.html

Docs for b6a320b3ca68c5aa8fb855cbff2fd9101d221ccc are browesable at: https://ci.foundries.io/projects/fio-docs/builds/484/docs/artifacts/html/index.html

Additionally I'm adding sphinx-tabs so that we can add cases for various things like shown in this gif.


tedge-mapper-aws prints errors for known non-json mosquitto bridge health status messages

Describe the bug

The tedge-mapper-aws service prints errors on mqtt payloads which aren't valid json. This is a problem because the mosquitto bridge health status is published as a single integer 1 or 0 which is the most likely root cause of these messages.
$ journalctl -fu tedge-mapper-aws -n 100
-- Journal begins at Tue 2023-08-15 14:24:36 CEST. --
Sep 08 00:54:04 lumber tedge-mapper[32138]: 2023-09-07T22:54:04.089756196Z ERROR aws_mapper_ext::converter: Mapping error: invalid type: integer `0`, expected a map at line 1 column 1
Sep 08 00:54:04 lumber tedge-mapper[32138]: 2023-09-07T22:54:04.08980177Z ERROR aws_mapper_ext::converter: Mapping error: invalid type: integer `0`, expected a map at line 1 column 1

To Reproduce

Install thin-edge.io

Configure the tedge-mapper-c8y to connect to AWS (this gist can help guide you through the setup)

Publish a message to simulate the mosquitto bridge health message
tedge mqtt pub tedge/health/mosquitto-aws-bridge 0

Inspect the tedge-mapper-aws logs for any error messages related to mapping/parsing errors
journalctl -u tedge-mapper-aws -n 50

Expected behavior

The aws mapper should ignore parsing errors for known topics like tedge/health/mosquitto-aws-bridge and tedge/health/mosquitto-c8y-bridge etc.
Screenshots

Environment (please complete the following information):

OS [incl. version]: Debian 11 (bullseye)
Hardware [incl. revision]: Raspberry Pi 4
System-Architecture [e.g. result of "uname -a"]: Linux lumber 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr  3 17:24:16 BST 2023 aarch64 GNU/Linux
thin-edge.io version [e.g. 0.1.0]: tedge 0.12.1~237+g7f58cd2

Additional context

QA has thoroughly checked the feature and here are the results:

[ ] Test for ticket exists in the test suite.
[x] QA has tested the bug and could not reproduce it anymore.


No license

Not sure about this one, problem is this is not exactly code so i'm not sure if the licenses i use elsewhere apply here.
May i ask what do you intend to do with it ?
Anyway will do some research, it's either going to be gpl2 to match sysdvr and if that's not applicable will look into something else (creative commons maybe ?).

I wanted to redistribute it.

Unmodified, with your handle and such listed

I've chosen the BSD 3-Clause License which seems to be ok for this.

I wanted to redistribute it.

Just add a link to this repo somewhere and it's fine.


Option to export and save images and attachments

https://support.airtable.com/docs/airtable-attachment-url-behavior

The attachment viewer URL requires a viewer to be logged in via Airtable, whereas the download URL can be publicly accessed via a web browser. This presents a potential security risk for any files that contain sensitive information since a permanently accessible download URL would still be viewable even after a viewer has been removed from an Airtable workspace. For that reason, we introduced expiring attachment download URLs starting November 8th, 2022.
[...]
API - Similar to the previously mentioned CSV downloads, download any attachments from the links attachment obtained via Airtable’s API before those links expire.

This tool should grow a feature to download and save attachments, since the URLs are no longer a useful long-term reference.
How long until they expire? The docs say:

If you, or a third-party integration, are using API processes to obtain attachment URLs from Airtable, then it’s important to note that the URLs obtained will only be active for a short period of time (~2 hours). Using Airtable as a CDN has been and continues to be discouraged in line with this change.

The JSON for a PDF attachment looks like this:
[
    {
        "id": "attHd9sanAvr8PwGk",
        "url": "https://v5.airtableusercontent.com/v1/20/20/1694980800000/eql_yHjtzp6IHoic_KROvw/FjJhJto96zC-1yxspRtNNa_WjWcU8_L2xJDUJd65Hj530F56TDTkxrSUjaUfLfSibHmxEwOkf3rcsoANvGaO0pl2YVUb00YFOlSLhEq_5gA/zsiKz8BHmXq87lkH3o4j2AgV0NTuUsZIcyT5JduLMo0",
        "filename": "ardata.pdf",
        "size": 506898,
        "type": "application/pdf",
        "thumbnails": {
            "small": {
                "url": "https://v5.airtableusercontent.com/v1/20/20/1694980800000/BScJEWFsxF5MOcZJ_i8RsA/tPGX0GFgMelnlR88d41c6DJDl9pa9E3M5y3123HrDPrj_A4Kocl2StxwBLsb3dFSZrwIjcw5csCI0DQZ5d_5vA/zI1iLniIAYc-oZhHonurjZ7h2pu5vxlzbR1NE2DMTx0",
                "width": 28,
                "height": 36
            },
            "large": {
                "url": "https://v5.airtableusercontent.com/v1/20/20/1694980800000/QMvnNnH-ftXXOeBRYJk4fQ/io3cJpspKnpka1q-fAhsEiJCwPmReOow7NeGPl96ogH5HFXtqxQvge85hcz3EIzPJ7rr0-uzdAUoDWfPi4a0mw/mpJk4qmSys6QE8IqSp4whgrc-52UiOR1DD9X7rIiTh8",
                "width": 396,
                "height": 512
            }
        }
    }
]

For an image, this:
[
    {
        "id": "attwPzAABrX7mUpdl",
        "width": 4032,
        "height": 3024,
        "url": "https://v5.airtableusercontent.com/v1/20/20/1694937600000/-Ex6TxOvcFa-QRIDtsSZwg/kZ2Id34JwYwhYwqWUbhlqMLntfqEbe8J95Gnb1eXswOMlCh8lvxIujNMOojCSCJ8l5ZMO1UKsPPNZSLusJHcja8tkPPBnrBtvEpfof_ti6c/2UH1gYdWPHDAKGY1qe97mUSxskh2Q2uPKh_79MRdXmI",
        "filename": "2023-05-24 18.54.28.jpg",
        "size": 5237935,
        "type": "image/jpeg",
        "thumbnails": {
            "small": {
                "url": "https://v5.airtableusercontent.com/v1/20/20/1694937600000/4vruo5I_9EIlxlN7KPLozg/TFof3GLJo3MMxVLeEYqYAL7-g8RHHpD0mn3KzJB-ffPvKV9KXg8wVk_2onpLARuugA87bCEwLdhqMthHFoFr4g/6dCCAksO2neaFKqtEu5Tws0-CRuXrm8OP21XlHWYTFM",
                "width": 48,
                "height": 36
            },
            "large": {
                "url": "https://v5.airtableusercontent.com/v1/20/20/1694937600000/Sjt3pZJeeovYOiVtWEBuMQ/VJx0IHFStQ1CEvOKsaoeMixItvcw3gVQ-MxYDt60q98S9iAOiSxFmw47tUdd-ozsnPJ-bjOAJ8NxOb2eLcLdyQ/EKsuXWiXUzmiFedTTUmnx46s9JFnZXkq2UXcENSPyT8",
                "width": 683,
                "height": 512
            },
            "full": {
                "url": "https://v5.airtableusercontent.com/v1/20/20/1694937600000/uQVk3ZjVPk42MXgkdZ3Cjw/vFhGv1qIgRKSfC8Dah5TRgUqNSFxGW0UUc82KhUFjIt62kyT8Qr173dK91Y7R_keQEohFm25jgdWODR4LvVKMg/4yrXgtkH8nwhC4EsQ0oaQxrseOIQowDsRtOt0HbIRFA",
                "width": 3000,
                "height": 3000
            }
        }
    }
]

What filename should I use?
Two options: there's the id field - which is guaranteed to be unique, but isn't very nice to read. And there's the filename field which might be a duplicate.
Maybe the answer is to store them like this:
attwPzAABrX7mUpdl/2023-05-24 18.54.28.jpg

Or like this:
attwPzAABrX7mUpdl-2023-05-24 18.54.28.jpg

I'm leaning towards the latter - the airtable ID, then a hyphen, then the filename.

Are attachments unique to their tables or bases? Probably, but I can't be 100% sure.

Maybe the CLI grows a --attachments folder/ option which saves all attachments to the specified folder.
Or it could be a flag, so you just pass --attachments and it automatically creates output-folder/attachments/ and saves them in there.
I think I like the latter option better. I'll build that first.

I'm going to download the attachments as a second step, with a progress bar based on the total count of bytes to fetch.
Should I fetch the thumbnails too? I think so - even though that will slightly throw off the progress bar since I won't have the file size of those (it's not in the JSON).
I'll store those as attwPzAABrX7mUpdl-full-2023-05-24 18.54.28.jpg to avoid anything where filenames confuse things. I guess .jpg is the right extension for all thumbnails?
I'll use $airtable_id-original-%filename for the original to namespace it separately from the thumbnails.

Huh, no at least one of the PDF thumbnails turned out to be a PNG. I guess I should set the file extension based on the detected content type.

One slightly tricky thing is that the YAML/JSON flat files may end up with URLs to attachments which don't directly correspond to the files on disk.
Not sure the best way to fix that.
The stored YAML looks like this:
- Attachments:
  - filename: 2022-07-26 11.13.58.jpg
    height: 3024
    id: atttqayAwklSIehzC
    size: 5471198
    thumbnails:
      full:
        height: 3000
        url: https://v5.airtableusercontent.com/v1/20/20/1694930400000/LhLoyhSixZRtUMOIW4rDmQ/diboUo14Z7KGQWOvyTPvG11qQ4FtV-xtDLDMXdETthmjqdM1Aysp-Gwa1f9lvR8ojVSURy1pw1VaL9SEDLQWxQ/_30sml0SbUmdNgkW9moBIQX9xSBVGMG6iLbCvSwIhgE
        width: 3000
      large:
        height: 512
        url: https://v5.airtableusercontent.com/v1/20/20/1694930400000/_afO19TInFwIhO4-QVV-FQ/S-JgJs8MHCKUbV8scsZE4tZKwTrCl1yxq5KCFe0O97yDnSO-4aKqPKvDrv2NX0JRjeD4ecwhgnJJepTyF3BHQg/_G1mqoQr68W8-3QYo-9f2X2eiDzcDBumSDV_7DlerEM
        width: 683
      small:
        height: 36
        url: https://v5.airtableusercontent.com/v1/20/20/1694930400000/17No0cBf3trPUv_1wywegw/360f3uc0uxEj5BCu0pqb4l7RrR6LgYy4RDLImLyhCxgbFQ6g2Ztss-yU1ouxU5BqTpqFP5tI0OWM6PhtnZdlFw/XUp16QgEVA0RvjU94Lm3HZYre_l0a83WxzPAmead57o
        width: 48
    type: image/jpeg
    url: https://v5.airtableusercontent.com/v1/20/20/1694930400000/uZehbrwpqTtVT3f01w7cyQ/z6MGnx2f-cmr8Mrkwnj9m74ImZUwBUDOkYLPf9aAWhAhpEa6JLh7ydwJU_aDvU7B0nyi0_kfP1NERTq0IQz3eOYgrjCJh-z593y8WAzLawo/WuDrxvXaLSmGtf44yeduCy3pbsuwc-YTsvKGEsXpaaE
    width: 4032

I could rewrite this to insert _saved: filename next to each of those url fields.

So I think the full process is:

Export and store the data as YAML/SQLite/etc
Gather together all of those URLs and go and fetch archived copy of them (maybe skipping ones that have been downloaded previously)
Update the stored YAML/SQLite to add the _saved keys pointing to those filenames.

I don't particularly want to have to round-trip the YAML/JSON formats, so I think I'll keep all that data in memory, snapshot it to disk, then do the attachment downloads and snapshot each file to disk again with the extra fields after the attachments have been saved.

Better option: do this on a per-table basis - so it loads a table into memory, snaps it to disk, saves any attachments, updates the snapshot on disk and then moves on to the next table.
I still like the early snapshot because I like that the user won't lose data if they cancel the operation during a large attachment download.

👋 Hi @simonw - thank you for this great repo.
I was wondering if you'd be open to a PR for downloading attachments. I have a pretty simple MVP in this commit that works by downloading files after downloading all records. WDYT?
It's slightly hacky in that it does not rely on --schema also being called and knowing exactly which fields are truly attachment fields, but this keeps the code quite a bit simpler.


ARM64, mrs %0, cntvct_el0 causes gem5::ArmISA::ISA::getGenericTimer(): Assertion `system' failed

Describe the bug
int cycleLo = 0;
asm volatile("mrs %0, cntvct_el0" : "=r"(cycleLo));

These lines in a test program cause simulator to crash.
To Reproduce
import m5
from m5.objects import *

system = System()

system.clk_domain = SrcClockDomain()
system.clk_domain.clock = '1GHz'
system.clk_domain.voltage_domain = VoltageDomain()

system.mem_mode = 'timing'
system.mem_ranges = [AddrRange('512MB')]

system.cpu = ArmTimingSimpleCPU()

system.membus = SystemXBar()

system.cpu.icache_port = system.membus.cpu_side_ports
system.cpu.dcache_port = system.membus.cpu_side_ports

system.cpu.createInterruptController()

system.system_port = system.membus.cpu_side_ports

system.mem_ctrl = MemCtrl()
system.mem_ctrl.dram = DDR3_1600_8x8()
system.mem_ctrl.dram.range = system.mem_ranges[0]
system.mem_ctrl.port = system.membus.mem_side_ports

binary = '<path to test program>'

# for gem5 V21 and beyond
system.workload = SEWorkload.init_compatible(binary)

process = Process()
process.cmd = [binary]
system.cpu.workload = process
system.cpu.createThreads()

root = Root(full_system = False, system = system)
m5.instantiate()

print("Beginning simulation!")
exit_event = m5.simulate()

print('Exiting @ tick {} because {}'.format(m5.curTick(), exit_event.getCause()))

#include <stdio.h>

int main(int argc, char* argv[])
{
    int cycleLo = 0;
    asm volatile("mrs %0, cntvct_el0" : "=r"(cycleLo));
    printf("LETS GOOO!!!\n");
    return 0;
}

Terminal Output
$ build/ARM/gem5.opt configs/tutorial/part1/simple.py
gem5 Simulator System.  https://www.gem5.org
gem5 is copyrighted software; use the --copyright option for details.

gem5 version <IP_ADDRESS>
gem5 compiled Dec  4 2024 15:59:58
gem5 started Dec  4 2024 18:41:36
gem5 executing on BillyGates, pid 1478
command line: build/ARM/gem5.opt configs/tutorial/part1/simple.py

Global frequency set at<PHONE_NUMBER>000 ticks per second
warn: No dot file generated. Please install pydot to generate the dot file and pdf.
src/mem/dram_interface.cc:690: warn: DRAM device capacity (8192 Mbytes) does not match the address range assigned (512 Mbytes)
src/base/statistics.hh:279: warn: One of the stats is a legacy stat. Legacy stat is a stat that does not belong to any statistics::Group. Legacy stat is deprecated.
system.remote_gdb: Listening for connections on port 7000
Beginning simulation!
src/sim/simulate.cc:199: info: Entering event queue @ 0.  Starting simulation...
src/sim/syscall_emul.cc:74: warn: ignoring syscall set_robust_list(...)
src/sim/syscall_emul.cc:85: warn: ignoring syscall rseq(...)
      (further warnings will be suppressed)
src/sim/mem_state.cc:448: info: Increasing stack size by one page.
src/sim/syscall_emul.hh:1075: warn: readlink() called on '/proc/self/exe' may yield unexpected results in various settings.
      Returning '/mnt/c/Users/User/Desktop/gem5_test/gem5/tests/test-progs/hello/src/hello64-static'
src/arch/arm/insts/pseudo.cc:174: warn:         instruction 'bti' unimplemented
src/sim/syscall_emul.cc:74: warn: ignoring syscall mprotect(...)
gem5.opt: src/arch/arm/isa.cc:1396: gem5::ArmISA::BaseISADevice& gem5::ArmISA::ISA::getGenericTimer(): Assertion `system' failed.
Program aborted at tick 315627000
--- BEGIN LIBC BACKTRACE ---
build/ARM/gem5.opt(_ZN4gem515print_backtraceEv+0x30)[0x562e38979450]
build/ARM/gem5.opt(_ZN4gem512abortHandlerEi+0x4c)[0x562e3899d9ac]
/lib/x86_64-linux-gnu/libc.so.6(+0x42520)[0x7ff8c5289520]
/lib/x86_64-linux-gnu/libc.so.6(pthread_kill+0x12c)[0x7ff8c52dd9fc]
/lib/x86_64-linux-gnu/libc.so.6(raise+0x16)[0x7ff8c5289476]
/lib/x86_64-linux-gnu/libc.so.6(abort+0xd3)[0x7ff8c526f7f3]
/lib/x86_64-linux-gnu/libc.so.6(+0x2871b)[0x7ff8c526f71b]
/lib/x86_64-linux-gnu/libc.so.6(+0x39e96)[0x7ff8c5280e96]
build/ARM/gem5.opt(_ZN4gem56ArmISA3ISA15getGenericTimerEv+0x19f)[0x562e369c43af]
build/ARM/gem5.opt(_ZN4gem56ArmISA3ISA11readMiscRegEt+0x301)[0x562e369c92b1]
build/ARM/gem5.opt(_ZNK4gem510ArmISAInst5Mrs647executeEPNS_11ExecContextEPNS_5trace10InstRecordE+0x55)[0x562e372ed485]
build/ARM/gem5.opt(_ZN4gem515TimingSimpleCPU14completeIfetchEPNS_6PacketE+0x264)[0x562e37c83b94]
build/ARM/gem5.opt(_ZN4gem510EventQueue10serviceOneEv+0x16d)[0x562e3898dd5d]
build/ARM/gem5.opt(_ZN4gem59doSimLoopEPNS_10EventQueueE+0x68)[0x562e389b4c38]
build/ARM/gem5.opt(_ZN4gem58simulateEm+0x283)[0x562e389b5233]
build/ARM/gem5.opt(+0x30d8510)[0x562e38906510]
build/ARM/gem5.opt(+0x132fdc4)[0x562e36b5ddc4]
/lib/x86_64-linux-gnu/libpython3.10.so.1.0(+0x128023)[0x7ff8c640f023]
/lib/x86_64-linux-gnu/libpython3.10.so.1.0(_PyObject_Call+0x5c)[0x7ff8c63c8fec]
/lib/x86_64-linux-gnu/libpython3.10.so.1.0(_PyEval_EvalFrameDefault+0x4b16)[0x7ff8c635d776]
/lib/x86_64-linux-gnu/libpython3.10.so.1.0(+0x1c23af)[0x7ff8c64a93af]
/lib/x86_64-linux-gnu/libpython3.10.so.1.0(_PyEval_EvalFrameDefault+0x9d68)[0x7ff8c63629c8]
/lib/x86_64-linux-gnu/libpython3.10.so.1.0(+0x1c23af)[0x7ff8c64a93af]
/lib/x86_64-linux-gnu/libpython3.10.so.1.0(PyEval_EvalCode+0xbe)[0x7ff8c64a43de]
/lib/x86_64-linux-gnu/libpython3.10.so.1.0(+0x1bd96d)[0x7ff8c64a496d]
/lib/x86_64-linux-gnu/libpython3.10.so.1.0(+0x1287b3)[0x7ff8c640f7b3]
/lib/x86_64-linux-gnu/libpython3.10.so.1.0(_PyEval_EvalFrameDefault+0x69de)[0x7ff8c635f63e]
/lib/x86_64-linux-gnu/libpython3.10.so.1.0(+0x1c23af)[0x7ff8c64a93af]
build/ARM/gem5.opt(+0x30be9d7)[0x562e388ec9d7]
build/ARM/gem5.opt(main+0x213)[0x562e3690c8e3]
/lib/x86_64-linux-gnu/libc.so.6(+0x29d90)[0x7ff8c5270d90]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x80)[0x7ff8c5270e40]
--- END LIBC BACKTRACE ---
For more info on how to address this issue, please visit https://www.gem5.org/documentation/general_docs/common-errors/

Aborted (core dumped)

Host Operating System
WSL 2 (Ubuntu 22.04.4 LTS)
Host ISA
X86
Any help is appreciated, thank you in advance!

We should probably make the error more informative.
However, the problem is that there is no GenericTimer in SE mode. Do you have an userspace process trying to read the virtual count register? I guess if that is the case we could mock something up to give some idea of time to the application

Thank you for quick reply. Yea, we have a benchmark that tries to read the timer and we cannot really change the source. If you can tell us how we can get it to work with some mock timer data, it would be great!

You probably need to define a SE generic timer inheriting from BaseISADevice.
Then you would return a reference to it from the ISA::getGenericTimer method.
You only need to implement reads to EL0 registers. In your case, I would for example use the curTick time from the CPU clock domain, and transform tick time to a counter value depending on the counting frequency. (You can copy the default value of operation of the SystemCounter: https://github.com/gem5/gem5/blob/stable/src/dev/arm/GenericTimer.py#L70 )
Feel free to open a PR one you implement this :)

Thank you very much for the info! This issue does not directly relate to our current project, but will take a look into it once we are more familiar with Gem5 (we are true beginners), and will open a PR if we feel competent enough.

Thank you very much for the info! This issue does not directly relate to our current project, but will take a look into it once we are more familiar with Gem5 (we are true beginners), and will open a PR if we feel competent enough.

Sure! Please don't feel intimidated by opening a PR. We have all been beginners at a certain point in time. I'd be happy to review it and provide assistance if needed


[META] Support Windows Server 2022 for RKE2

Required:

[x] RKE2
[x] System Agent Installer RKE2
[x] Update Mirrored Images list to include Pause 3.6 as it is the first to support Windows Server 2022.
Linked Issues:
[x] Fleet
[ ] ~Wins Upgrader~ - No longer relevant in RKE2
[x] Dapper/Drone
[x] Golang images
[x] Rancher

Future:

[x] Monitoring https://github.com/rancher/rancher/issues/35595
[x] Logging

https://github.com/rancher/rke2/issues/1733
https://github.com/rancher/system-agent-installer-rke2/issues/27
https://github.com/rancher/rancher/issues/35487

Looks like to support Windows Server 2022 we will need to upgrade our pause image to 3.6 as the first version that supports 2022.
https://mcr.microsoft.com/v2/oss/kubernetes/pause/tags/list

PR for system-agent-installer-rke2: https://github.com/rancher/system-agent-installer-rke2/pull/28

PR for RKE2: https://github.com/rancher/rke2/pull/2094

currently blocked from adding nodes to custom clusters on this ticket: https://github.com/rancher/dashboard/issues/4581

RKE1 custom clusters blocked from adding windows nodes on https://github.com/rancher/rancher/issues/35614

waiting on the latest rke2 RC (required for testing windows 2022)

filed a blocking ticket: https://github.com/rancher/rancher/issues/35681

@slickwarren The related blocking ticket has been closed. Should this be moved to test?

blocked by https://github.com/rancher/rancher/issues/35851

@slickwarren Should this be moved to test?

Blocked by https://github.com/rancher/rancher/issues/35487

Test Environment:
Rancher version: v2.6-head 6de683b
Rancher cluster type: HA
Docker version: 20.10
Downstream cluster type: 2022 RKE2 custom windows cluster (1 etcd, 1 cp, 1 linux worker, 3 windows workers)
Downstream K8s version: v1.21.7+rke2r2

Network testing:

Create a workload
image: get the image from @luthermonson
ports:

service type: node port
name: any name
private container port: 80
protocol: tcp
listening port: 30000 - 32767 range

curl http://node_ip:listening_port/name.html

issue:
curl: Failed to connect to {node ip} port {port}: Operation timed out

expected:
pod name is returned

see screenshot:
when steps from above are applied to ranchertest/mytestcontainer image deployed to the linux worker node with a node port service created
- pod name is returned

As per @sirredbeard "This appears to be related to a breaking changes made in the Calico chart. "

Tracking issue for upstream issue of node ports not working on Windows Server 2022
https://github.com/rancher/windows/issues/159

To validate before closing:

v3_needs_cluster jenkins (basic network checks) on a WIndows 2022 RKE2 cluster on 1.22RKE2 version - 3 linux nodes, 3 windows worker nodes
k8s upgrade - 1.22 to 1.23
Validate P0 usecase of fleet
Validate P0 usecase of Wins upgrader

@slickwarren here is the existing info about Wins upgrader, we could probably update that to have more details. I will create an issue for it. https://github.com/rancher/wins/blob/main/charts/rancher-wins-upgrader/README.md

tested the following on v2.6-head (b7c9b89):

jenkins job fails due to nodeport being unsupported (known issue with this version of windows, kernel issue iirc)
k8s upgrade -- no longer able to do, as 1.23 is experimental due to issues specifically with windows
p0 use case of fleet -- pass
p0 use case of wins-upgrader -- failed

attempted initial install of wins-upgrader chart with default values -- both pods in daemonset fail to deploy
attempted to upgrade the chart to latest version available (0.2.1) -- fails to deploy the pod in daemonset with error crashloopbackoff however I am unable to view logs of the workload through kubectl or the UI of rancher. Will file a bug for this shortly.

created this dashboard ticket to track wins-upgrader for rke2

Pending wins-upgrader fixes by Luther.

https://github.com/rancher/rancher/issues/37483
CSI Proxy did not support Windows Server 2022 until v1.1.1, which came out approximately a month ago.

There is no wins upgrader for 2022, it is no longer required following RKE1 deprecation, and chart needs to be deprecated.

As of today, Windows Server 2022 is available and supported across the product.
The only remaining item was Wins upgrader, but that is not being used for Windows in RKE2. It was a parity image/chart that is no longer in the design of RKE2


browser-esbuild less-plugin -

Command
build
Is this a regression?

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

The previous version in which this bug was not present was
No response
Description
I tested the esbuild and encountered 2 problems on the less compilation:

in less-plugin:

we have a stack overflow error with the first attempt to direct loading as a relative path:

        // Attempt direct loading as a relative path to avoid resolution overhead
        const directResult = this.loadFileSync(filename, currentDirectory, options, environment);
        // this.loadFileSync => he calls himself

the file resolution doesn't work as expected and all paths configured on stylePreprocessorOptions are not used

Just for my tests and to workaround, I just remove the override function `` to use the original less FileManager.

always in less-plugin the javascriptEnabled options is not enabled so we've got some errors

To workaround this I added the options javascriptEnabled to less.render:
less.render(data, {
      filename,
      paths: options.includePaths,
      plugins: [resolverPlugin],
      rewriteUrls: 'all',
      javascriptEnabled: true,
      sourceMap: options.sourcemap
        ? {
            sourceMapFileInline: true,
            outputSourceFiles: true,
          }
        : undefined,
    } as Less.Options);

Minimal Reproduction

Just create a new project with "inlineStyleLanguage" in less
Add external dependecy<EMAIL_ADDRESS>Import antd default theme: @import (multiple) 'ng-zorro-antd/src/style/themes/dark';
Preprocessor options in angular.json :
"stylePreprocessorOptions": { "includePaths": [   "node_modules" ] },

Exception or Error
First Error :
RangeError: Maximum call stack size exceeded
  at /project/node_modules/esbuild/lib/main.js:1242:27
  at new Promise (<anonymous>)
    at Object.resolve (/project/node_modules/esbuild/lib/main.js:1241:16)
    at AbstractFileManager.loadFile (/project/node_modules/@angular-devkit/build-angular/src/builders/browser-esbuild/stylesheets/less-plugin.js:85:46)
    at AbstractFileManager.loadFileSync (/project/node_modules/less/lib/less-node/file-manager.js:135:21)
    at AbstractFileManager.loadFile (/project/node_modules/@angular-devkit/build-angular/src/builders/browser-esbuild/stylesheets/less-plugin.js:80:47)
    at AbstractFileManager.loadFileSync (/project/node_modules/less/lib/less-node/file-manager.js:135:21)
    at AbstractFileManager.loadFile (/project/node_modules/@angular-devkit/build-angular/src/builders/browser-esbuild/stylesheets/less-plugin.js:80:47)
    at AbstractFileManager.loadFileSync (/project/node_modules/less/lib/less-node/file-manager.js:135:21)
    at AbstractFileManager.loadFile (/project/node_modules/@angular-devkit/build-angular/src/builders/browser-esbuild/stylesheets/less-plugin.js:80:47)
    at AbstractFileManager.loadFileSync (/project/node_modules/less/lib/less-node/file-manager.js:135:21)
    at AbstractFileManager.loadFile (/project/node_modules/@angular-devkit/build-angular/src/builders/browser-esbuild/stylesheets/less-plugin.js:80:47)
    at AbstractFileManager.loadFileSync (/project/node_modules/less/lib/less-node/file-manager.js:135:21)
    at AbstractFileManager.loadFile (/project/node_modules/@angular-devkit/build-angular/src/builders/browser-esbuild/stylesheets/less-plugin.js:80:47)
    at AbstractFileManager.loadFileSync (/project/node_modules/less/lib/less-node/file-manager.js:135:21)
    at AbstractFileManager.loadFile (/project/node_modules/@angular-devkit/build-angular/src/builders/browser-esbuild/stylesheets/less-plugin.js:80:47)

------

Second Error:
✘ [ERROR] Inline JavaScript is not enabled. Is it set in your options? [plugin angular-less]

    node_modules/ng-zorro-antd/src/style/color/bezierEasing.less:110:0:
      110 │ .bezierEasingMixin();
          ╵ ^

  The plugin "angular-less" was triggered by this import

Your Environment
Angular CLI: 16.0.0
Node: 18.12.1
Package Manager: npm 9.6.5
OS: darwin arm64

Angular: 16.0.0
... animations, cdk, cli, common, compiler, compiler-cli, core
... elements, forms, localize, platform-browser
... platform-browser-dynamic, pwa, router, service-worker

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1502.8
@angular-devkit/build-angular   16.0.0
@angular-devkit/core            15.2.8
@angular-devkit/schematics      16.0.0
@schematics/angular             16.0.0
ng-packagr                      16.0.0
rxjs                            7.8.1
typescript                      4.9.5

Anything else relevant?
No response

The call stack relative path resolution issue already has a pending fix and will be available in the first patch release.
The javascriptEnabled option is deprecated by Less and is not recommended due to security concerns. This was actually discussed in 2018 (Angular v6 timeframe) in regards to what appears to be the same package (https://github.com/angular/angular-cli/issues/10430).  Due to potential security concerns with users unintentionally executing JS at build time, further discussion with the team will be needed to determine a long-term path forward.

Well done
Thanks for your reactivity 👍

Typically releases happen on Wednesdays.


TLS Error with chromedp/headless-shell

I have been having trouble finding an answer to this, and I am curious if anyone else has had a similar issue with the headless shell image.  My container is attempting to make API requests out to the Discord API, but I am getting a TLS error within the headless-shell image.  This was working correctly before I added chromedp and headless-shell, but I was just running everything directly in the Go 1.20-alpine.
It could be that I am just missing something here as I am pretty new to this.  Any assistance would be appreciated.

What versions are you running?
$ go list -m github.com/chromedp/chromedp
github.com/chromedp/chromedp v0.9.1
$ google-chrome --version
chromedp/headless-shell:latest
$ go version
1.20

What did you do? Include clear steps.
This is my Dockerfile
FROM golang:1.20-alpine as build
WORKDIR /go/src/app
COPY . ./
RUN go mod init; go mod tidy
RUN go build -o ./dist

FROM chromedp/headless-shell:latest

RUN apt-get update; apt install dumb-init -y
ENTRYPOINT ["dumb-init", "--"]
COPY --from=build /go/src/app/ /tmp
EXPOSE 8081
CMD ["/tmp/dist"]

What did you expect to see?
I expect the API requests to be made successfully
What did you see instead?

chromedp/headless-shell is based on debian:bullseye-slim, which does not have ca-certificates installed by default. See https://github.com/debuerreotype/docker-debian-artifacts/issues/15.
Modify the Dockerfile to install it explicitly:
FROM golang:1.20-alpine as build
WORKDIR /go/src/app
COPY . ./
RUN go mod init; go mod tidy
RUN go build -o ./dist

FROM chromedp/headless-shell:latest

RUN apt-get update && apt install ca-certificates -y
COPY --from=build /go/src/app/ /tmp
ENTRYPOINT ["/tmp/dist"]
EXPOSE 8081

BTW, you don't need dumb-init any more. Just run the container with the --init option (See Specify an init process).


Fix ARMViolations for Microsoft.Solutions

Fix ARMViolations for Microsoft.Solutions

Automation for azure-sdk-for-ruby

Can one of the admins verify this patch?

Automation for azure-sdk-for-python

Automation for azure-sdk-for-node

Automation for azure-sdk-for-go

Automation for azure-sdk-for-java

@marstr Can you please take a look at this validation error? It is not related with my change. It seems that in the file, we have path "/{applianceId}" and "/{applianceDefinitionId}", and validation thinks they are the same path.

Seems like this must be a long-standing issue, as running a git log on this file only shows the activity of me creating it in December as part of a refactor. Because you're not introducing that error, I'm not going to block this PR on that failure.

@sergey-shandar, is this a known issue?

Signing off from ARM side.

@marstr Thanks, please merge this PR.


build_images returning SyntaxError even with python 3.6

I am running python version 3.6.8 in an isolated conda environment.
When I run python build_images.py I get

File "build_images.py", line 33
self.log.info(f"Browsing {directories}")

SyntaxError: invalid syntax

Running python with sudo was running a differente version of python (below 3.6), which was not the python from the conda environment. So, I ran "sudo /full_path_to_conda_env/python build_images.py" and it worked.


Error after upgrading to mesos 0.26

Hi,
I upgraded to latest mesos available from mesosphere ubuntu repositories. Chronos is still at 2.4.0, also installed from mesosphere repo.
My jobs are failing, I can see this in the sandbox section in the mesos UI
Missing required option --launcher_dir

Usage: mesos-docker-executor [options]

  --container=VALUE                    The name of the docker container to run.

  --docker=VALUE                       The path to the docker executable.

  --docker_socket=VALUE                The UNIX socket path to be used by docker CLI for accessing docker
                                       daemon.

  --external_log_file=VALUE            Specified the externally managed log file. This file will be
                                       exposed in the webui and HTTP api. This is useful when using
                                       stderr logging as the log file is otherwise unknown to Mesos.
  --[no-]help                          Prints this help message (default: false)
  --[no-]initialize_driver_logging     Whether to automatically initialize Google logging of scheduler
                                       and/or executor drivers. (default: true)
  --launcher_dir=VALUE                 Directory path of Mesos binaries. Mesos would find health-check,
                                       fetcher, containerizer and executor binary files under this
                                       directory.
  --log_dir=VALUE                      Directory path to put log files (no default, nothing
                                       is written to disk unless specified;
                                       does not affect logging to stderr).
                                       NOTE: 3rd party log messages (e.g. ZooKeeper) are
                                       only written to stderr!
  --logbufsecs=VALUE                   How many seconds to buffer log messages for (default: 0)
  --logging_level=VALUE                Log message at or above this level; possible values:
                                       'INFO', 'WARNING', 'ERROR'; if quiet flag is used, this
                                       will affect just the logs from log_dir (if specified) (default: INFO)
  --mapped_directory=VALUE             The sandbox directory path that is mapped in the docker container.

  --[no-]quiet                         Disable logging to stderr (default: false)
  --sandbox_directory=VALUE            The path to the container sandbox holding stdout and stderr files
                                       into which docker container logs will be redirected.
  --stop_timeout=VALUE                 The duration for docker to wait after stopping a running container
                                       before it kills that container.

{
  "schedule": "R/2015-11-16T00:01:00Z/P1D",
  "scheduleTimeZone": "Europe/Bucharest",
  "name": "my-app-name",
  "container": {
    "type": "DOCKER",
    "image": "my/img:2.0",
    "network": "BRIDGE",
  },
  "cpus": "0.1",
  "mem": "128",
  "disk": "0",
  "uris": [],
  "shell": false,
  "command": "/my/cmd",
  "arguments": [],
}

I had the same problem and found this issue.
On your slave machines create a text file: "/etc/mesos-slave/launcher_dir"  with the content: "/usr/bin"
if you've installed mesos with apt-get.
If you are running meos-slave directly, provide the --launcher_dir=/usr/bin
Maybe upgrade could create this for us but it seems it didn't.

That didn't work for me.
I'm installed on Ubuntu 14.04 from the PPA, my launcher dir is /usr/libexec/mesos but even with the /etc/mesos-slave/launcher_dir present and with the correct path, I still get that error with 0.26.
I've downgraded to 0.25

You should put /usr/libexec as launch_dir. not /usr/libexec/mesos.

I'll give that a shot, thanks

Hi. I upgrade from 0.25 to on 0.27 on Ubuntu 14.04 and hit this issue.
The fix that worked was:
stop mesos-slave
echo "/usr/libexec/mesos" > /etc/mesos-slave/launcher_dir
start mesos-slave

I had the same issue and it was due to the fact that the mesos slaves were still running 0.25.


Enable regex_extract for constant parameters

Work in progress, do not review

PR title is not correct, please also update.