text:
New Program ID's from Heat Pump Dryer TWD364WP

Feature request
Hi,
Firstly thanks for making this and sharing it with all.
I've recently got a TWD364WP Heat Pump Dryer and there appears to be a few missing program mappings at the moment as these just show the ID in the sensor. The following details the missing ones.

ID
Program

2
Cottons

3
Minimum iron

4
Woollens handcare

5
Delicates

6
Warm air

8
Express

9
Cottons

12
Proofing

14
Shirts

A note for 9 - the name formats incorrectly in the API and doesn't match the front of panel, nor manual. In both of these it another icon next to it in addition to the name. In the API there's a single space on the end of the program name (there isn't on 2) so it's Cottons  to be accurate. This image shows the icon I mean;

The 9 one doesn't allow any custom settings for the "Cotton" run, all predefined which is the difference I guess and doesn't allow for "Gentle Tumble" 🤷🏻♂  I can't find the actual name of this symbol anywhere - but there is a difference program wise.
For the last ID I saw from the front panel options - 31 - I have had a look through the code mappings and noticed that this one maps to something already - which explains why I was seeing it labelled however 31 on this dryer maps to something else setting wise. Not sure if that's an easy fix or not... ID 31 - Displays "Gentle minimum iron", but on this model that maps to "Bed linen" according to the diagnostics log.
      "state|ProgramID|value_raw": 31,
      "state|ProgramID|value_localized": "Bed linen",
      "state|ProgramID|key_localized": "Program name",

All of these mappings pulled out of debugging after selecting each program on the front of the dryer. I'll be happy to upload all the diagnostics log files if you need them. I could probably attempt a PR also, if so desired 😸 I'm unsure what you'd want to do on ID 31.
What version of the integration are you using?
0.15.1
Anything in the logs that might be useful for us?
No response
Additional information
No response

The program with the "tag" is Cottons ECO.

@darkorb This mapping looks identical to the one of  TCR790WP.
You can make use of custom Localization to correct the program names on your end. This was implemented in https://github.com/astrandb/miele/pull/225.

authors: apeeters darkorb mundschenk-at

repo: astrandb/miele


text:
wip - parse TransactionBody from pbjson

Summary
Brief summary of the changes made, ie "what?"
Background
Brief background on why these changes were made, ie "why?"
Changes

List changes which were made.

Testing
How are these changes tested?
Metrics

List out metrics added by PR, delete section if none.

Breaking Changelist

Bulleted list of breaking changes, any notes on migration. Delete section if none.

Related Issues
Link any issues that are related, prefer full github links.
closes

Closing this because #1696 got merged.

source: gharchive/pull-request

repo: astriaorg/astria

license_type: permissive

license_source: github-api


text:
Integration DAG's : Test in astro-cloud

Create an astro-cloud instance
Run the deployment
Execute all the integration DAG

We have moved the DAGs on Astro Cloud. However, a few DAGs are failing with limited error details. Need to investigate the errors.
Additionally, we're also missing credentials for Azure DAGs which need to be taken from @bharanidharan14

source: gharchive/issue

authors: pankajkoti phanikumv

repo: astronomer/astronomer-providers


text:
Use upstream aws base hook session implementation

We have missing implementation for some auth type so I was thinking if it makes sense to use upstream provider base hook implementation.

@phanikumv wdyt?

@phanikumv wdyt?

yes it makes sense

changing this to draft to avoid accidental merge

authors: pankajastro phanikumv


text:
Deprecate WasbPrefixSensorAsync

Deprecate WasbPrefixSensorAsync and proxy it to its Airflow
OSS provider's counterpart
related: #1412

The implementation work is complete here, but it's waiting for OSS provider release

Verified with RC 9.0.0 that the DAG enters deferral and then succeeds


text:
Add catalog verification pipeline

This might look like a report of what's inside the catalog, to be verified against the catalog owner's expectation of the catalog contents.
Useful things to consider:

total number of sources
column-level schema (names and types)
column-level units
values "close" to original values (identical for integers, "close enough" for floating points)
distribution of radec among points
allow for comparisons against some golden file(s)

Connected with #374, #373, and #375

authors: delucchi-cmu nevencaplar

repo: astronomy-commons/hipscat-import


text:
Add Sphinx Plot Gallery

This PR addresses Issue #12.

@jberlanga – Thanks!
I see you have astroplan/plots/plots.py in this PR. Is that on purpose? Do you think code review for that will be quick (~ 1 day)? If no, I'd suggest you split the addition of the gallery (maybe with a dummy plot) from the PR where your plotting code is discussed.

https://travis-ci.org/astroplanners/astroplan/jobs/70927747#L870
ImportError: No module named sphinxgallery

You probably have to add a line after this one:
https://github.com/astroplanners/astroplan/blob/master/.travis.yml#L101
 - if [[ $SETUP_CMD == build_sphinx* ]]; then $PIP_INSTALL sphinxgallery; fi

@jberlanga – Is this working locally for you? Do you have a place where you can upload the generated html docs for easy review / discussion? (if no, maybe make a screenshot and paste it here?)

@cdeil

I did add plots.py here as a way to use the plotting function directly (since the plotting PR isn't merged yet), but I can delete it and replace the (non-functioning) plot with a dummy.
Ah, yes, I had to install sphinx-gallery, good point!
It's working locally for me in the sense that a gallery is being added (even though the plot itself isn't showing up).

Screenshots:
Astroplan RTD Homepage (see "General Documentation")

Astroplan Plotting Examples

@cdeil   I addressed the sphinx-gallery pip install, as well as another dependency (pillow).  The Travis CI build is still failing on build_sphinx.

@jberlanga – Can you reproduce (and fix) the Sphinx warning locally?
https://travis-ci.org/astroplanners/astroplan/jobs/70949409#L877
Use python setup.py build_sphinx --clean-docs to make sure you do a clean docs build.

plot itself isn't showing up

Can you try and investigate / fix this?
If there's no warning / error that gives an indication, one thing you could try is starting from a working example (https://github.com/sphinx-gallery/sphinx-gallery) and then trying to spot the difference or make our docs build more like theirs, or theirs more like ours.
Leave a comment if you're not getting anywhere with this and I'll have a look tomorrow morning...

@jberlanga – There's one unrelated issue: the API entries (like e.g. Target) are showing up at the top level on the navigation bar on the left (see your screenshot above). Instead there should just be one "Reference / API" entry as it's the case e.g. at http://wcsaxes.readthedocs.org/en/latest/ .
Could you please try to fix this here (e.g. by comparing out index.rst file to the one from wcsaxes) and if it's not clear how to fix it, file a separate issue for that?

@jberlanga - one thing I noticed about why you're not getting the plot output: if you read http://sphinx-gallery.readthedocs.org/en/latest/getting_started.html#setting-up-your-project very closely, you'll see it says it only actually runs code that starts with plot_.  So If I grab this branch and locally build it, it actually tries to execute the plot if you rename airmass.py to plot_airmass.py.

@cdeil

@jberlanga – There's one unrelated issue: the API entries (like e.g. Target) are showing up at the top level on the navigation bar on the left (see your screenshot above). Instead there should just be one "Reference / API" entry as it's the case e.g. at http://wcsaxes.readthedocs.org/en/latest/ .

Could you please try to fix this here (e.g. by comparing out index.rst file to the one from wcsaxes) and if it's not clear how to fix it, file a separate issue for that?

I have a good idea of how to (start to) fix it, but I'd rather keep that separate from the Sphinx-Gallery stuff, so I'll make an issue/separate PR for this.
@eteq

@jberlanga - one thing I noticed about why you're not getting the plot output: if you read http://sphinx-gallery.readthedocs.org/en/latest/getting_started.html#setting-up-your-project very closely, you'll see it says it only actually runs code that starts with plot_. So If I grab this branch and locally build it, it actually tries to execute the plot if you rename airmass.py to plot_airmass.py.

I do believe you are correct!

Plot is now showing up, but is getting cut off on the right.

@jberlanga – I know I said I'd try to help with this today, but I'm very busy, so I'll leave this to you for now to try and resolve the Sphinx warnings / error. But if one of them won't budge, please leave a comment here and I'll have a look.

@cdeil  After playing around with Sphinx Gallery some more, I'm leaning towards using Matplotlib's sphinxext instead.  Sphinx Gallery makes it harder to control exactly how your documentation looks, and doesn't link the gallery page to the navigation bar (you could add a page listed in the navigation bar which contains a link to the gallery page, but that would be more confusing to users trying to find the gallery).

@jberlanga How do you want to use http://matplotlib.org/sampledoc/extensions.html ?
If you mean just use the .. plot:: directive in various parts of the docs, then yes, we should do that.
I don't think it contains something to build a gallery, i.e. a page with thumbnail plots and short descriptions, that are clickable and lead to new pages with code and plots.
I think having a Gallery for astroplan would be nice. It's very popular, even for a more number-crunching-oriented package like http://scikit-learn.org/stable/auto_examples/index.html
I didn't fully understand the issue you described linking the navigation bar and the gallery page.
What I would have expected was a separate page in our docs called "Gallery" that can be reached via an entry called "Gallery" in the navigation bar. Now if that is not easily possible, maybe you can look through the issues and feature requests athttps://github.com/sphinx-gallery/sphinx-gallery/issues and file a question / feature request for this and see if they respond?

@cdeil - just to clarify, the point here is that sphinx-gallery additional complexity which we don't need if there are a fairly limited number of plots - it's straightforward to just hand-create a gallery.  And then contributors don't need to install sphinx-gallery to be able to generate the docs (not a critical thing, but nice).
Part of the issue we encountered is that it's not that trivial to annotate the plots with sphinx-gallery.  You have to embed it in with the examples.  Whereas using the matplotlib stuff you can just have a regular rst file and then link to it and the generated images from an index page.

OK, fine, let's make it a normal RST page with .. plot:: directives, then.
I still would like a slick thumbnail gallery with some Javascript action when hovering over each image. But not enough that I'd actually put in time to get it to work the way we like. So fair enough, thanks for trying!
Do you think it's worth filing a feature request with sphinx-gallery ... maybe they are just not aware what people want and would be willing to implement it.

Yeah, that might be a good idea... It may turn out that the main problem is that they just don't have time/effort to document it fully, but it can't hurt.
It shouldn't be very hard to switch from what @jberlanga is doing back to sphinx-gallery if we want, though: she can just put the RST content as the module docstring in the example, and move the .. plot:: directive out as the actual content.  So there's an easy path if there's more time later.

@cdeil / @eteq  It looks like they will support multiple galleries AND include those in the navigation bar in their newest dev version.

oh wow, that version looks a ton nicer.  It also seems like you can get what you want with inline commentary using the notebook styled examples.  So that suggests to me that you should use the matplotlib approach now but consider switching to sphinx-gallery once they've merged that and done a release.

Sounds like a plan!

This was superceded by #42

authors: cdeil eteq jberlanga

repo: astroplanners/astroplan


text:
IERS A table workaround

Here's one solution to our troubles with the IERS Bulletin A table. I'll try to summarize what this is all about before describing the PR, and hopefully a discussion can emerge from @astroplanners/astroplanners-contributors about whether or not this is an OK fix. I acknowledge the inevitable gripe that this PR should really be to astropy, but for the sake of getting astroplan done before the summer is over, I'm keeping my work in astroplan.
Background
Earth orientation data is necessary to precisely calculate alt/az positions. The Earth orientation data used by astropy comes from IERS, and they post it in two forms. The IERS Bulletin B (denoted throughout astropy as "IERS B" or the "IERS B table") contains the orientation data for the recent past, based only on observations. The IERS Bulletin A has the data in Bulletin B and also extrapolations into the past and future. Leap seconds get factored into the future extrapolations in the IERS A table, making them necessary for precision O(seconds) in the near future. This table gets updated once a week.

See this blog post that I wrote up a few weeks ago for details on how to make those plots with astropy.
In the current version of astropy, the IERS Bulletin B is included in the package, but IERS Bulletin A is not. If you try doing a calculation with a time in the near future, you get:
IndexError: (some) times are outside of range covered by IERS table.

In astroplan so far, we've been running a script to download/cache the IERS Bulletin A (~3 MB) every time the user runs astroplan. This hasn't been a big deal because (1) we're connected to the internet, (2) after the first time you download it, you don't notice it's happening.
Since we want the tests to run without internet access, and we want users to be able to do these calculations without the internet, a workaround is needed that gives users access to IERS Bulletin A without an internet connection.
This PR
The solution here is to include IERS Bulletin A in the astroplan package data/ dir, stored as a text file. When the user accesses astroplan/core.py, a new function get_recent_IERS_A_table in the utils module is called that manages IERS Bulletin A. Here's what it does:

It first opens data/iers_bulletin_a.txt and looks to find the date when the observed Earth orientation data runs out and the predictions begin (which is flagged within the table). This tells you when the file was last updated
If the table has observations <7 days old, that table is returned and used for calculations.
If the table has no observations <7 days old, it tries to download a new copy of the table and store it in the same place as the old one (data/iers_bulletin_a.txt)
If the table has no observations <7 days old and the internet is not accessible, it uses the old (and only available) table and raises a warning like this:

WARNING: OldEarthRotationDataWarning: Your local copy of the IERS Bulletin A
table is 8.2 days old, and the internet can not be accessed to download the latest
copy. Earth rotation calculations will not be as precise as possible until you
reconnect to the internet and attempt to access the IERS Bulletin A table again.
[astroplan.utils]

Thanks for the context and background!
I'm still against including a copy of the table in astroplan because then the file is tied to the release schedule of astroplan. Imagine that releases only happen every 6 months. Then a typical user will install astroplan and have a ~3 month old version of the file. Based on the criteria you outline above for when to grab a new version of the file, all users will have to download a new version of the file anyways...?

RE @adrn :

Then a typical user will install astroplan and have a ~3 month old version of the file.

That's not how this PR works, actually. If the user has internet access, any table more than one week old will get refreshed. If the user does not have internet access, we simply can't do better than using an old table.
It's true though that we have update the astroplan version of the file every so often to ensure that people downloading the package for the first time get a reasonably recent version of the table to fall back on if they don't have consistent internet access.

Sorry, I guess I wasn't clear.
What I mean is this: if the release schedule is every 6 months, and a user installs astroplan 3 months after a release, then their IERS table will be 3 months old. So whenever they use astroplan and have an internet connection, a download will be triggered to get the new version anyways (as it happens now, right?). All I'm saying is that maybe there is a better solution than packaging a perpetually-old version of the table in to astroplan, especially since it is a few MB. For example, there may be a way to include an external file download in setup.py? I'm not sure, but @eteq might know.

So whenever they use astroplan and have an internet connection, a download will be triggered to get the new version anyways (as it happens now, right?).

In the PR, whenever a download is done it gets saved and replaces the data/iers_bulletin_a.txt file. The download only has to happen once a week to be perfectly up-to-date – the download does not happen every time, it just checks whether the present table is up-to-date each time.
Before this PR, the download happens once and gets cached (similar to in this PR, except that it's saved in the astropy cache).
Important Aside
Let's remind ourselves of the precision we're quibbling about. We can only calculate rise/set times to an accuracy of a few seconds right now anyways. For the average user, a few second offset of UTC-UT1 is a negligible difference, and even if the user doesn't connect to the internet for a year, the offset is likely still <3 seconds.

@adrn / @eteq: The current build has an error that looks like weird quantities behavior. In almost all contexts I've been able to compute an inequality for a Quantity that's a time duration (days, minutes) and a TimeDelta, but it's giving an error on some of the builds (but not all), see one here.

I understand that the file is cached now, and I understand the offsets are small. My point is just that even if we include a version of the file in astroplan, most users will still have to download an updated version of the file. I'm not arguing/quibbling about precision, I just don't think we should package the file in astroplan! If most users will need to download a more recent version of the file anyways because the packaged version is out of date, then we should just find a solution that grabs the newest version of the IERS file available on install. Again, I don't know how to do this, but I figure there must be a way!

I think the whole problem that @cdeil was trying to avoid was that users should be able to install/test without downloading anything.

And my point is that -- even with this PR -- the typical user will install astroplan, then immediately try to use it. Meaning it will immediately trigger a download to get the latest version of the file because the packaged version of the file is old. So I'm proposing we look for a solution that does the download on install rather than on first usage of the code. Then we don't have to package the IERS file with astroplan.

(and if that solution I suggest doesn't exist then fine, I give in)

Ok, now I understand.
I'm not disagreeing with you (yet), but is there a significant difference between doing it on install rather than on first use? Astroplan builds a lot of stuff at first use, rather than doing it on install.

In this case, the difference is just not packaging an out of date, 4 MB data file with astroplan that we then have to deal with. I know it doesn't seem like a hassle, but (a) even though it's only MB's, git doesn't like MBs and (b) I'm only making a fuss if there is an easy alternative solution, and this is the kind of something that @eteq will know immediately :)

Got it. Waiting on @eteq!

@bmorris3 – Thanks for implementing a possible solution for this issue! (Apart from https://travis-ci.org/astroplanners/astroplan/jobs/77017285#L555 which needs to be resolved.)
@adrn – I don't think we have to find and implement the long-term solution for this issue when to download or update the IERS table here. Download on install instead of first import has pretty much the same issues, i.e. install and travis-ci tests can fail if the site that hosts the IERS table is not available.
@olebole as Astropy Debian packager – Any advice on when the IERS A table should be downloaded / updated by Astropy (or astroplan for now) so that it would work e.g. for Astropy in Debian?
@bmorris3 – It seems that @adrn's main concern here is with bundling these few MB in the code repo. (And I share this concern a bit, it's not a great solution.)
Can you come up with a different solution that makes the IERS A table completely optional for astroplan? Maybe fall back to the IERS B table only? Or if that is not possible for some reason (the IndexError in Astropy), then fake a IERS A table using the IERS B table as input and adding one entry in the far past and future that does linear interpolation? I think that would be acceptable if a warning is emitted. Not super-high precision results are better than refusing to produce any results!

@eteq – Assigning this PR to you for the final decision.

@cdeil Would you suggest also revising all of the tests to use dates that exist in the IERS B table? Otherwise they'll break.

I think you should still test for dates in the the past and future.
But it's OK if those tests are low precision, at a level that corresponds to 'linear interpolation' of the always-available IERS B table (whatever that means exactly).
There can still be high-recision tests that require the IERS A table, but those should be marked @remote_data if IERS A isn't bundled.

No strong opinion here because this seems like trying to pick the "least bad" thing to do, but given a choice between requiring a download at installation vs. first use I would prefer at installation time.  If the cache freshness period is 7 days then at least tests should succeed without requiring a subsequent download.
What about at least providing a separate option in setup.py to download the table?  Then at least the travis builds can run that step before running tests.  I like the idea of the tests giving a warning that the table is out of date (and maybe should suggest the command to run to refresh the table).

@cdeil I still do not understand the whole context yet (it is the first time I heared about astroplanner :-) ), but I would put the data file into /var/cache/.... If it is used by more than one independent package (so, if astroplanner does not depend on astropy), I would create an extra package for that and  let the others depend on it.
About the update process:  Debian wants that the user keeps control the remote activities like downloads, so an automated download needs to be switched on somehow -- I will find out.

@bmorris3 @adrn - I left some inline suggestions on this (including an important but probably fairly easy-to-implement bit about location of the files).  But I'd also like to give an opinion on the at-install vs as-import question (and hopefully we can resolve this in the telecon later today):
I'm generally in favor of @adrn's idea of downloading at build-time if possible (more on how to do that below).  But I have one question for @bmorris3: do you need the IERS A file for some of this to work at all?  That is, is there functionality that works with even a horribly out-of-date IERS A that won't work with just IERS B?  If yes, then I'd say we have to include one with each release (updated, if possible, immediately before release), because that accounts for the user who gets the package and then later tries to install it without internet access.  So in that case I'm in favor of this PR plus what @adrn is suggesting.
As for the mechanics of downloading at-install: I think this isn't going to be that hard to implement if we follow my second in-line comment above about having the "preferred" IERS A file be in the astropy cache directory.  If that's what we want, all you have to do is do the download into that same location at the end of the install procedure.  Adding a final step to the install isn't too hard because we can just add in a custom install build command that runs a function to do this.  It should be only ~10 lines of code to do that (although it does require a bit of modification to the base level setup.py).

Closing in favor of #71, after conversation over Hangout and Slack.

authors: adrn bmorris3 cdeil ejeschke eteq olebole


text:
Fix ConfigParser in setup.py

Replace the distutils ConfigParser with that from standard library

This has been already covered in #177 (which got only held up with some other upstream issues, but now passes).

Sorry, I looked through the other issues but didn't see anything mentioned, didn't realize it had been covered. Mine also attempts a python3 import first, which may not be what you want. I'll close here. Thanks!

authors: bsipocz wtgee

repo: astropy/astroplan


text:
SupportAnimator

where is supportanimator class? that class is not found

Which class? You mean NineOldAndroids?

no, the SupportAnimator class

I can't get you. Can you write the exact class with package? So we can solve the problem together.

io.codetail.animation.SupportAnimator;

I checked the library 2 times not found the any relationship with that class in project. Maybe, you need to re-download the library again. I can't remember that i created the SupportAnimator class.

please check ur sample at TransitionLoopFragment.java
that class using io.codetail.animation.SupportAnimator;

if you created your own demo class, you need to add dependency compile 'com.github.ozodrukh:CircularReveal:1.0.4@aar' in your build.gradle. If you want to run the demo class provided here you must sync your gradle in project to download and link the dependencies to demo.

i tried but, that dependecy is nor resolve / not found

I found the answer.  CircularReveal have been updated. I will update the demo soon. Now SupportAnimator changed to Animator

repo: asyl/ArcAnimator

license: mit

license_source: bigquery


text:
Improve stability message based on #120 feedback

This brings in the suggestions from #120

Thank you very much. 😁

repo: async-graphql/async-graphql


text:
Studio started with AsyncAPI cli tools does not support version 3.0

When starting the AsyncAPI Studio from the cli tools. The instance complains on not supporting specification 3.0
Can be reproduced with creating a new file with the CLI tools and auto starting Studio:
asyncapi new file
? name of the file? asyncapi.yaml
? open in Studio? Yes
Created file asyncapi.yaml...
Studio is running at http://localhost:3210?liveServer=3210
Watching changes on file asyncapi.yaml

Tested with:
$ asyncapi --version
@asyncapi/cli/1.3.3 darwin-arm64 node-v20.7.0

@asyncapi/studio dependency must be updated to latest version as it uses old 0.17 -> https://github.com/asyncapi/cli/blob/master/package.json#L22
@KhudaDad414 did you plan to bump? automated bump do not work as you did some monorepo stuff in studio repo so I bet standard autobump workflow do not work as expected anymore

They are already working on it, see https://github.com/asyncapi/cli/issues/629

repo: asyncapi/cli


text:
[kafka] Match messages received on  Produce requests with the described messages in the AsyncAPI doc

From Kafka documentation, this is all the info the Produce Request (Took version 8 as example):
Produce Request (Version: 8) => transactional_id acks timeout_ms [topic_data]
  transactional_id => NULLABLE_STRING
  acks => INT16
  timeout_ms => INT32
  topic_data => name [partition_data]
    name => STRING
    partition_data => index records
      index => INT32
      records => RECORDS

The app also knows the broker address the request was made to, It also has the mappings between Brokers and local ports.
At a glance, I see the app could find the channel by checking the topic name on the Produce Request, match it with channels within the AsyncAPI doc with an Operation type of subscribe.
However, this solution won't scale that much since we are assuming operations and messages are a 1:1 relationship, but this is subject to change in version 3 of the spec.
Would it make sense to introduce some identifier in the message so we can validate directly looking by that identifier?

I think that this issue is related https://github.com/asyncapi/spec/issues/458 and messageId will be very handy in this case.

Yup, it is. Once messageId becomes a thing, it will be more easy to identify instead of guessing

authors: magicmatatjahu smoya

repo: asyncapi/event-gateway


text:
chore: cleanup and fix cli build

Description
This PR fixes the CLI build, test and clean up all irrelevant files

/rtm

authors: devilkiller-ag jonaslagoni

repo: asyncapi/modelina


text:
Fix typos in README.md

What Dev Docs changes are you proposing?
Description
There are typos in the README.md file that need correction:

"dociuenting" should be corrected to "documenting".
"Docuentations" should be corrected to "Documentations".

Details

File: README.md

Current Text:

"It's uses Storybook as a frontend workshop and for dociuenting UI components."
"Docuentations for CLI installation and contribution."

Corrected Text:

"It uses Storybook as a frontend workshop and for documenting UI components."
"Documentations for CLI installation and contribution."

Steps to Reproduce

Open the README.md file.
Locate the typos mentioned above.
Replace them with the corrected text.

Screenshots
Screenshots
Below are the screenshots highlighting the typos in the documentation:

Screenshot showing the typo "dociuenting":

Screenshot showing the typo "Docuentations":

Additional Information
These corrections will improve the clarity and professionalism of the documentation.
Code of Conduct

[X] I agree to follow this project's Code of Conduct

I would like to work on this @antoniogarrote @MikeRalphson @scharrier @ceich

I am working on this issue

this is a PR https://github.com/sgnhyperion/website/pull/1/files is duplicate of mine and how did this get merged and not mine @sgnhyperion @fmvilas

authors: Arnavya sgnhyperion

repo: asyncapi/website


text:
🛑 Wedding HTTPS is down

In 5794395, Wedding HTTPS ($WEDDINGHTTPS) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Wedding HTTPS is back up in 3af1bf1.

repo: atatkin/milos-uptime

license: MIT


text:
🛑 Wedding HTTPS is down

In e0c1b34, Wedding HTTPS ($WEDDINGHTTPS) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Wedding HTTPS is back up in 5e84f9b.


text:
🛑 Wedding HTTPS is down

In 214d5bf, Wedding HTTPS ($WEDDINGHTTPS) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Wedding HTTPS is back up in ead515a.


text:
🛑 Wedding HTTPS is down

In f5c1548, Wedding HTTPS ($WEDDINGHTTPS) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Wedding HTTPS is back up in 0ad4611.


text:
🛑 Wedding HTTPS is down

In 4fd3e9a, Wedding HTTPS ($WEDDINGHTTPS) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Wedding HTTPS is back up in ebfa9e4.


text:
🛑 Wedding HTTPS is down

In 676f7ac, Wedding HTTPS ($WEDDINGHTTPS) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Wedding HTTPS is back up in a148d7e.


text:
Update C++ version

Thank you very much for this excellent template.
Just a minor suggestion.
I hope this pull request helps you.
https://docs.ros.org/en/humble/The-ROS2-Project/Contributing/Code-Style-Language-Versions.html#id2

Thanks for the fix!


text:
I want to change frame size to 10ms buffer, what should I do please?

Dear friends:
1, I notice currently you only support 8ms buffer to process, now I want to change to 10ms buffer, I tried to change some parameters, but I find the programme runs crashed, and the output is all zero, so I want to know what should I change for 10ms buffer?
2, I notice you define subband_filter_coef[] in dios_ssp_share_subband.c file, but I do not know how you get this filter, could you give your algorithm? I see it is not just hanning or hamming windows, I think if I want to change to 10ms buffer, I have to change it, correctly?
Thanks

I have fixed it, close.
But if you have any further comment, please feel free to share it.
Thanks

repo: athena-team/athena-signal


text:
Can zoom out but can't zoom in

Hey, firstly, congrats on this project!
Just a quick thing I noticed: I can zoom out with ( CTRL - ) , but then can't zoom back in with ( CTRL + ).
Thanks!

oh interesting. Will look into it

authors: atinylittleshell ninjavis

repo: atinylittleshell/TerminalOne


text:
[DISCUSS] When selecting a source or target field, auto scroll to show the other field involved in the mapping

Migrating this from https://github.com/syndesisio/syndesis-datamapper-ui/issues/55.

We may want to also consider some ability to show all fields involved in the mapping for source and target, possibly using some type of collapsing technique.

authors: jbakermd jpav

repo: atlasmap/atlasmap-ui


text:
Change UI for gitlab import so select button does not jump out of screen

Description
I moved the selected repos message to the bottom in line with the “Load More” and “Select/Cancel” buttons. I adjusted the height of the table to 65vh (not 70vh) since the header “Select repositories” is slightly bigger than how it is for the Bitbucket import page.
Demo: https://www.loom.com/share/fa31cbfed1144b6180fc7d6068318312?sid=6819833e-dc33-49dc-ae08-d8b41dd21bb7
Checklist
Please ensure that each of these items has been addressed:

[X] I have tested these changes in my local environment
[X] I have added/modified tests as applicable to cover these changes
[X] (Atlassian contributors only) I have removed any Atlassian-internal changes including internal modules, references to internal tickets, and internal wiki links

My feedback for this PR is pretty much the same as the Bitbucket one

repo: atlassian-labs/gitlab-for-compass


text:
How to update api token (cleaning up old DVCS connections)

We have Github integrated with Jira. I'm getting emails warning that it is using old style tokens which are insecure.
What is the procedure for updating the tokens for the plusin?
thanks

We have the same issue, unfortunately I didn't configure the integration in the first place and the person who did is no longer around so it's not clear whether we migrated from DVCS to the app. All I can see is that our Jira Cloud instance is showing DVCS as not configured at the organisation level and the "GitHub for Jira" app is installed/configured. From the GitHub side the Jira Github App is installed/configured, plus I can see that there is an OAuth app called "JIRA", which I've rotated the secret for to try to flush out what is using it (I'm assuming it's not the Jira/Github app integration as that still seems to work fine since).
The email certainly seems to suggest that it's a Jira DVCS connector that is causing the issue I just can't work out where from:

We noticed that an application, JIRA, owned by an organization you are an admin of, [SNIP], used a token with an outdated format to access the GitHub API on October 19th, 2021 at 18:07 (UTC), with a user-agent header of JIRA DVCS Connector Vertigo/1001.0.0-SNAPSHOT.

@kourosh-eminence @jgtr-coats thank you for the response. This is a known issue. Even though DVCS integration was deprecated and replaced by the GitHub App, the tokens that had been used by DVCS still live Jira's database. We are now actively working on cleaning up the database and removing them altogether.

I don't quite understand whether they are the same thing or different integration methods.

They are completely different. The old (DVCS) tokens are not used anymore for syncing GitHub data and can be safely revoked on GitHub side because the new integration (this app) is a GitHub App, while the old integration (DVCS) was an OAuth app.
To remove the old OAuth application (that was used for DVCS) from GitHub, you could go navigate to GitHub.com -> [You Org] -> Settings -> Developer Settings -> OAuth apps -> [App name] - > Advanced -> Delete the application
Could you please let me know if it makes sense? I'll update this issue once we finish the cleanup on our end, although even after that you might still would like to revoke the tokens on GitHub side because Jira doesn't have control over it.

Hi - I can understand the old DVCS token sitting around in the Jira database, but the warning email makes it sounds as though Jira has actually used it for an API call. I'd be interested to know why that is?

Hey @aingham. Given that it has been over a month since we last heard from you, I'm going to go ahead and close this issue. Please feel free to reopen/reach out again if you need help with anything.

authors: aingham bgvozdev jgtr-coats kourosh-eminence rachellerathbone

repo: atlassian/github-for-jira


text:
Allow Anonymous Or Actual Snippets To Be Provided As Suggestions And Expanded When Confirmed

[x] Expand snippet when suggestion is confirmed
[ ] Allow providers to specify that a suggestion includes an anonymous snippet that should be inserted
[ ] Ensure triggering of autocomplete doesn't conflict with completion of snippet expansion (e.g. if multiple snippet arguments need to be satisfied)
[ ] Filter snippets from suggestions when the cursor is currently inside of a snippet that is being expanded

Sounds like @park9140 has an implementation in park9140/atom-typescript-tools. Let's bring it in-house!

This is out!

authors: benogle joefitzgerald

repo: atom-community/autocomplete-plus


text:
AltGr is not Alt

Hello,
it might only be a problem of a de-de keyboard but if I can not press AltGr+ß then I can not get a . You need \ for namespaces in PHP. There is no easy way to deactivate alt--keybinding. I've read the CSON manual but couldn't find a clue how to do "nothing" on a keybinding.
For me Atom is useless unless this is not solved.

This is a duplicate of https://github.com/atom/atom-keymap/issues/35. You may want to subscribe there for updates. Additionally, some people have reported good results from using the keyboard-localization package.

authors: lee-dohm ortreum

repo: atom/atom


text:
Uncaught Error: Cannot read property 'object' of undefinedTypeError: Cannot read property 'objec...

[Enter steps to reproduce:]

...
...

Atom: 1.17.0 x64
Electron: 1.3.15
OS: Mac OS X 10.12.5
Thrown From: Atom Core
Stack Trace
Uncaught Error: Cannot read property 'object' of undefined
TypeError: Cannot read property 'object' of undefined
at ObjectsRegistry.get (/Applications/Atom.app/Contents/Resources/electron.asar/browser/objects-registry.js:41:28)
at EventEmitter. (/Applications/Atom.app/Contents/Resources/electron.asar/browser/rpc-server.js:306:31)
at emitMany (events.js:127:13)
at EventEmitter.emit (events.js:201:7)
at WebContents. (/Applications/Atom.app/Contents/Resources/electron.asar/browser/api/web-contents.js:222:13)
at emitTwo (events.js:106:13)
at WebContents.emit (events.js:191:7)
At /Applications/Atom.app/Contents/Resources/electron.asar/renderer/api/remote.js:217

Error: Cannot read property 'object' of undefined
TypeError: Cannot read property 'object' of undefined
    at ObjectsRegistry.get (/Applications/Atom.app/Contents/Resources/electron.asar/browser/objects-registry.js:41:28)
    at EventEmitter.<anonymous> (/Applications/Atom.app/Contents/Resources/electron.asar/browser/rpc-server.js:306:31)
    at emitMany (events.js:127:13)
    at EventEmitter.emit (events.js:201:7)
    at WebContents.<anonymous> (/Applications/Atom.app/Contents/Resources/electron.asar/browser/api/web-contents.js:222:13)
    at emitTwo (events.js:106:13)
    at WebContents.emit (events.js:191:7)
    at metaToValue (/Applications/Atom.app/Contents/Resources/electron.asar/renderer/api/remote.js:217:13)
    at undefined.remoteMemberFunction (/Applications/Atom.app/Contents/Resources/electron.asar/renderer/api/remote.js:113:18)
    at AtomEnvironment.module.exports.AtomEnvironment.getWindowDimensions (/Applications/Atom.app/Contents/Resources/app/src/atom-environment.js:663:1)
    at AtomEnvironment.module.exports.AtomEnvironment.storeWindowDimensions (/Applications/Atom.app/Contents/Resources/app/src/atom-environment.js:697:1)
    at WindowEventHandler.module.exports.WindowEventHandler.handleWindowBlur (/Applications/Atom.app/Contents/Resources/app/src/window-event-handler.js:184:1)
    at /Applications/Atom.app/Contents/Resources/app/src/window-event-handler.js:3:1

Commands
 10x -5:06.2.0 core:move-down (input.hidden-input)
     -5:04.5.0 core:move-right (input.hidden-input)
     -5:04.0 core:move-left (input.hidden-input)
     -5:03.7.0 core:move-right (input.hidden-input)
     -5:03.3.0 core:save (input.hidden-input)
  4x -5:02.9.0 core:move-down (input.hidden-input)
  4x -5:02.1.0 core:move-up (input.hidden-input)
     -5:01.2.0 core:save (input.hidden-input)
  2x -0:35.4.0 pane:show-item-1 (input.hidden-input)
  2x -0:31.6.0 core:move-up (input.hidden-input)
  5x -0:30.8.0 core:move-right (input.hidden-input)
     -0:29.4.0 core:save (input.hidden-input)
 24x -0:29.1.0 core:move-right (input.hidden-input)
  2x -0:26.2.0 core:backspace (input.hidden-input)
     -0:25.8.0 core:move-right (input.hidden-input)
     -0:24.6.0 core:save (input.hidden-input)

Non-Core Packages
atom-cscope 1.0.0
minimap 4.28.2

Thanks for taking the time to contribute!
We noticed that this is a duplicate of #11692. You may want to subscribe there for updates.
Because we treat our issues list as the Atom team's backlog, we close duplicates to focus our work and not have to touch the same chunk of code for the same reason multiple times. This is also why we may mark something as duplicate that isn't an exact duplicate but is closely related.
For information on how to use GitHub's search feature to find out if something is a duplicate before filing, see the How Can I Contribute? section of the Atom CONTRIBUTING guide.


text:
Atom completely broken

Today I started up Atom and it looked like this:

None of the options in the dropdown menu make it go back to it's normal state.  I could not find anything by googling the symptoms.

Launching atom in "Safe Mode" by using atom --safe does not fix the problem.
Windows 7 64 bit
Version: ?? atom --version doesn't print anything and I can't get it from the GUI.
EDIT:
Got this from the debugger:
c:\ProgramData\chocolatey\lib\Atom.0.136.0\tools\Atom\resources\app\src\theme-manager.js:1
(function (exports, require, module, __filename, __dirname) { A��=
^
SyntaxError: Unexpected token ILLEGAL
at exports.runInThisContext (vm.js:73:16)
at Module._compile (module.js:451:25)
at Object.Module._extensions..js (module.js:486:10)
at Module.load (C:\ProgramData\chocolatey\lib\Atom.0.136.0\tools\Atom\resources\app\node_modules\coffee-script\lib\coffee-script\register.js:45:36)
at Function.Module._load (module.js:318:12)
at Module.require (module.js:373:17)
at require (module.js:392:17)
at Atom.module.exports.Atom.initialize (c:\ProgramData\chocolatey\lib\Atom.0.136.0\tools\Atom\resources\app\src\atom.js:199:22)
at Object. (c:\ProgramData\chocolatey\lib\Atom.0.136.0\tools\Atom\resources\app\src\window-bootstrap.js:12:8)
at Object. (c:\ProgramData\chocolatey\lib\Atom.0.136.0\tools\Atom\resources\app\src\window-bootstrap.js:29:4)
at Module._compile (module.js:468:26)
at Object.Module._extensions..js (module.js:486:10)
at Module.load (C:\ProgramData\chocolatey\lib\Atom.0.136.0\tools\Atom\resources\app\node_modules\coffee-script\lib\coffee-script\register.js:45:36)
at Function.Module._load (module.js:318:12)
at Module.require (module.js:373:17)
at require (module.js:392:17)
at window.onload (file:///C:/ProgramData/chocolatey/lib/Atom.0.136.0/tools/Atom/resources/app/static/index.js:20:25)
index.js:29

@mspoehr It does. Also, by now there is a Windows installer (which will come with an auto-updater as well), as you will probably have noticed, and it is recommended to get rid of the choco version.

authors: batjko mspoehr


text:
No menu bar at all with global menus on Linux

Using Arch Linux, KDE 4 with DBusMenu and Atom 1.0.0.  I can’t see a menu bar, I also can’t enable it in any way, and it does not appear on my panel either.  It worked in 0.211.0.
local/libdbusmenu 12.10.2-2
    A library for passing menus over DBus
local/libdbusmenu-glib 12.10.2-4
    A library for passing menus over DBus
local/libdbusmenu-gtk2 12.10.2-3
    A library for passing menus over DBus
local/libdbusmenu-gtk3 12.10.2-4
    A library for passing menus over DBus
local/libdbusmenu-qt4 0.9.3+15.10.20150604-1
    A library that provides a Qt4 implementation of the DBusMenu spec
local/libdbusmenu-qt5 0.9.3+15.10.20150604-1
    A library that provides a Qt implementation of the DBusMenu spec
local/atom-editor-bin 1.0.0-1
    Chrome-based text editor from Github - Precompiled binary from official repository

Fixed by restarting KDE.
And you would think that works for Windows only…


text:
Atom makes numerous requests on start / offers no way to disable

Upon running Atom (on Mac OS 10.9+), I have noticed it wants to connect to the following URLs:

atom.io on TCP port 443 (https)
2001:4860:4860::8888 on UDP port 53 (domain) and (Reverse DNS: google-public-dns-a.google.com)
s3-1.amazonaws.com on port 443 (https)
maps.gstatic.com on port 443 (https)
www-google-analytics.l.google.com on TCP port 443 (https) and (193.229.108.55)

I assumed the first couple were to just check if there were any updates, but the calls to Google have me stumped as to why my local app needs to ping Google. I searched the codebase and didn't find any mention of these URLs.
Perhaps you can explain these requests (or already have somewhere). Additionally, It seems that offering users a way to opt-out / disable these requests would be desirable, especially for the more privacy conscious users.

First three are related to Atom's auto-update mechanism and package updating. The last two are related to the metrics package. See https://github.com/atom/atom/issues/4966 for more details.

authors: bnvk thomasjo


text:
UX: Inconsistent position of "Search in Directory" menu item

If I right click on the project folder, the search button is down there:

However, it's on the top of the menu if I right click on any sub folder:

Thanks for the report! This looks like a duplicate of https://github.com/atom/tree-view/issues/535 – closing this out in favor of that issue.
Also take a look at https://discuss.atom.io/t/id-like-to-report-an-issue-request-an-enhancement-for-atom-where-on-github-do-i-do-that/19290 for a guide on where to post issues.

authors: lbebber mnquintana


text:
Highlighting lines takes 10% of the CPU?

Atom Version: 1.0.19
Environment: Archlinux
Repro steps:

Open a project folder
Open a file (must have some lines in it, more than 10 makes it easier to reproduce)
Hold double-click to select an entire line (keep holding it)
Move mouse down to select a few more lines
Wiggle your mouse up and down and notice that:

two processes go from taking 0% of the processor to 10%+
fan speed increases! (side effect)

Actual behavior:
Process 1:
/usr/share/atom/atom --type=gpu-process --channel=4927.0.1668123424 --no-sandbox --supports-dual-gpus=false --gpu-driver-bug-workarounds=2,27,30,43,52 --disable-accelerated-video-decode --gpu-vendor-id=0x10de --gpu-device-id=0x1187 --gpu-driver-vendor=NVIDIA --gpu-driver-version=355.11

increases by 13% for a simply highlighting lines?

Process 2:
/usr/share/atom/atom --type=renderer --force-device-scale-factor=1 --js-flags=--harmony --no-sandbox --enable-deferred-image-decoding --lang=en-US --node-integration=true --subpixel-font-scaling=false --enable-pinch-virtual-viewport --enable-delegated-renderer --num-raster-threads=2 --use-image-texture-target=3553 --disable-accelerated-video-decode --channel=4927.1.2045218742

increases by ~12%

Expected behavior:
For a simple task such as highlighting lines, is it reasonable to not expect 10% of my processor being used?
Additional Information:
processor: i7-930
gpu: nvidia gtx 760

I can reproduce this bug with ~25% cpu usage/one core.
I'm using the webupd8team repository on a fully patched ubuntu 16.04.1.
It only happens if you follow the instructions carefully:
Double-click to select whole line and then hold left mouse is necessary.
Possibly relevant packages:
highlight-selected@0.11.2
minimap@4.25.6
minimap-highlight-selected@4.4.0
minimap-selection@4.4.0

authors: Wulf nexhub


text:
Update issue templates

⚛👋 Hello there! Welcome. Please follow the steps below to tell us about your contribution.

Copy the correct template for your contribution

🐛 Are you fixing a bug? Copy the template from https://bit.ly/atom-bugfix
📈 Are you improving performance? Copy the template from https://bit.ly/atom-perf
📝 Are you updating documentation? Copy the template from https://bit.ly/atom-docs
💻 Are you changing functionality? Copy the template from https://bit.ly/atom-behavior

Replace this text with the contents of the template
Fill in all sections of the template
Click "Create pull request"

View rendered .github/ISSUE_TEMPLATE/Feature_request.md
View rendered .github/ISSUE_TEMPLATE/bug_report.md

Thanks for reaching out!
We require the template to be filled out on all new issues and pull requests. We do this so that we can be certain we have all the information we need to address your submission efficiently. This allows the maintainers to spend more time fixing bugs, implementing enhancements, and reviewing and merging pull requests.
Thanks for understanding and meeting us halfway :grinning:

authors: Arcanemagus berrylaw


text:
Error: Module did not self-register only on specific pages

On specific pages (google's oauth screen, for example), the spellchecker module for a webview is failing to load (and causing issues). I'm using electron 0.36.5, with spellchecker loaded as part of a preload script. It works without an issue, except when the webview navigates to, as an example: https://accounts.google.com/o/oauth2/auth?access_type=offline.......
To replicate, create a webview with the spellchecker module in a preload script
go to gmail in the webview
click on your user
click on add account
submit necessary information
Error in the console should say "Error: module did not self register" and then any typing that triggers spellchecker will target disconnect / black out the webview.
I'm stumped as to why this is. Any help would be greatly appreciated.

I suspect that this is a dupe of #4025

hrm. Almost certainly. I'll close this out.

authors: aggregatejeff paulcbetts

repo: atom/electron


text:
Fix issue regarding inconsistent black icons

Fixes #200

Thanks for fixing, @NadiaSotnikova 🙏

authors: NadiaSotnikova sindresorhus

repo: atomiclabs/cryptocurrency-icons


text:
at_c: APKAM command builders in packages/atauth

We have our own way of doing enrollment requests, approvals, etc,.

[x] atauth_enrollment_request - user requests for namespace access in atSign | unauthorized app requests for namespace access from authorized app
[ ] atauth_enrollment_approve - authorized app (with atSign keys) approves the user for namespace access
[ ] atauth_enrollment_deny - authorized app (with atSign keys) denies the user for namespace access
[ ] atauth_enrollment_list - authorized app (with atSign keys) lists all the enrolment requests from users
[ ] atauth_enrollment_revoke - authorized app (with atSign keys), when an enrolment request was approved once, can be taken away

To get at_activate over the finish line only enroll:request is required. And that has been implemented. Will take up the rest of the builders once at_activate is finished. Relevant code will be a part of the at_activate PR which is still a draft. Will link the PR once it is ready.

Assigning 3SP to implement the rest of the command builders.

Impl for enroll:request added through https://github.com/atsign-foundation/at_c/pull/423/files

authors: JeremyTubongbanua srieteja


text:
sshnp v3.4.2 has lost the '-P' option!

Describe the bug
-P was in 3.4.0 and is now gone ??
Steps to reproduce

run with -P !

Expected behavior
Specifies the local port number of sshd
Screenshots
No response
Smartphones

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Were you using an atApplication when the bug was found?
No response
Additional context
cconstab@cally:~$ $(sshnp -f @cconstab -t @ssh_1 -h @rv_am -d dragino -P 22)
FormatException: Could not find an option or flag "-P".
cconstab@cally:~$

-P was never in version 3.x.x

The earliest tags of it are v4.0.0+

v3.4.0

Interesting! It was pushed must have got crushed with another PR at some point

authors: XavierChanth cconstab

repo: atsign-foundation/sshnoports


text:
Unable to use cookiecutter with the py launcher on Windows

I am unable to use cookiecutter with Python for Windows using the built-in py launcher:
C:\Users\ivanzlatev>py -3 -m pip install cookiecutter
Requirement already satisfied (use --upgrade to upgrade): cookiecutter in c:\users\ivanzlatev\appdata\local\programs\python\python35-32\lib\site-packages
<..snip..>

C:\Users\ivanzlatev>py -3 -m cookiecutter
C:\Users\ivanzlatev\AppData\Local\Programs\Python\Python35-32\python.exe: No module named cookiecutter.__main__; 'cookiecutter' is a package and cannot be directly executed

@ivanz the pull-request https://github.com/audreyr/cookiecutter/pull/788 include this feature, but will be release only in the next version of cookiecutter (1.5.0)

We release cookiecutter 1.5.0 a few weeks ago! 👍

authors: hackebrot ivanz luzfcb

repo: audreyr/cookiecutter


text:
Update scalajs-dom to 2.6.0

About this PR
📦 Updates org.scala-js:scalajs-dom from 2.1.0 to 2.6.0
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-js", artifactId = "scalajs-dom" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scala-js", artifactId = "scalajs-dom" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, version-scheme:early-semver, commit-count:1

Superseded by #497.

repo: augustjune/canoe


text:
[Proposal] Remove TSLint when it's gets deprecated

@dondish, remove TSLint and upgrade to ESLint when TSLint gets deprecated in early 2020

Closed due of being added in 0.4.0

repo: auguwu/Nino


text:
Link to a live demo?

I don't see a link to a demo page for this that I can try out. Are you able to add one?

Hi Louis,
Thank you for raising this. I've had others asking for a demo too, therefore due to the requests (including yours) I will have one made available later this week.
I will keep you posted. Thanks again. 👍

Hello there,
A live demo for this project has been created and the README.md has been updated to reflect this. You can access the live demo at QuickMenu.org. On desktop you will see inline navigational links, whereas on a mobile device (mobile or tablet) you will see the Quick Menu.
The demo page at the moment is a basic example, the page has no content other than the navigation links. However whenever I am able to spare some time, I will enhance the page with content to provide a better representation of the Quick Menu in use on a site.
All the best,
Arif.

Looks great! Works nicely on my iPhone! I'll be sure to share the tool in my newsletter: https://webtoolsweekly.com/

That sounds brilliant and it is much greatly appreciated. Thank you also for your contribution to improving this project. 😊

authors: aullah impressivewebs

repo: aullah/quickmenu


text:
Close old repository?

Should we remove https://github.com/aurelia-widgets/aurelia-kendoui to avoid confusion?

done

authors: JeroenVinke adriatic


text:
License?

Thanks for this awesome software! It would be nice to have a clear LICENSE.md file if you plan to license this as MIT or similar.

Added license in cea4b03de509ede2d9c6da7ec9375081578e3d11

authors: aurimasg mattdesl

repo: aurimasg/blaze


text:
ZSH installer fails on OSX if user has a restricted account

If the active user doesn't have admin permissions and doesn't have oh-my-zsh, the zsh installer fails with 'No such file or directory'.
Expected Behavior
The installer succeeds and autocomplete works.
Actual Behavior
The installer fails with 'No such file or directory'.

You could try to find a writable path in $FPATH. Another way is to let the user put the script wherever they want.

@lilydjwg Hmm, that might work!  I've been trying to keep the files that tab touches to static list, so that it can clean up after itself with future versions of tab, or environmental changes (like installing oh-my-zsh).  I think I might need to sacrifice on that for the usability improvement in this case.
I even tried adding an entry to FPATH in the installer, but it didn't work because the change to FPATH has to be before autoload -U compinit && compinit in zshrc.
Anyway, thanks for the suggestion! This is a tough one...

authors: austinjones lilydjwg

repo: austinjones/tab-rs


text:
Emacs mode: do we need cl-lib?

There is a line at the beginning that seems unnecessary to me: (require 'cl-lib)
I’ve removed it locally and everything still works.
Asking Emacs for a description with M-x describe-package cl-lisp gives this answer:
Package cl-lib is built-in.

     Status: Built-In.
    Version: 1.0
    Summary: Common Lisp extensions for Emacs
Required by: popup-0.5.8
Other versions: 0.7 (gnu).

These are extensions to Emacs Lisp that provide a degree of
Common Lisp compatibility, beyond what is already built-in
in Emacs Lisp.

This package was written by Dave Gillespie; it is a complete
rewrite of Cesar Quiroz's original cl.el package of December 1986.

Bug reports, comments, and suggestions are welcome!

This file contains the portions of the Common Lisp extensions
package which should always be present. Emacs Lisp.

I thought that austral-mode might use some CL functions/forms but maybe it does not.
My familiarity with elisp and CL is quite rudimentary.

It might just be an archaism on my part. I didn't know cl-lib was built in.

repo: austral/austral


text:
🛑 repl.co is down

In c9b365a, repl.co (https://hello-repl.auteen.repl.co) was down:

HTTP code: 0
Response time: 0 ms

Resolved: repl.co is back up in 871b202.

repo: auteen/autoreplit


text:
Update Readme.md

Hi loved the example very well done. I am not sure how i came across it. i have always known about auth0 this was my first go at implementing it.   Since i just started by pulling the Repo liking from the interwebs I didn't read the massive 8 blog posts you did and getting admin access is not exactly straight forward  even after reading them. So i made a couple of tweaks to readme hopefully save someone some debug time. I think the main gotcha is the default rule namespace. I think a good solution in addition to the readme update would changing Namespace to  to idToken which is was what really got me loved the https vs. http total face palm.

oh might want to add the fact that you need to have a mongo db somewhere you reference mlab which should be good clue for most people but if a total newbie picked this up it might pick up on that.


text:
LoginHandlerError: Login handler failed. CAUSE: Page with dynamic = "error" couldn't be rendered statically because it used request.url.

Checklist

[X] I have looked into the Readme and have not found a suitable solution or answer.
[X] I have searched the issues and have not found a suitable solution or answer.
[X] I have searched the Auth0 Community forums and have not found a suitable solution or answer.
[X] I agree to the terms within the Auth0 Code of Conduct.

Description
I have setup the auth0 for next.js as mentioned on the document. When I was trying to redirect user to /api/auth/login or any of the route mentioned in the document. It is giving me this error:
LoginHandlerError: Login handler failed. CAUSE: Page with `dynamic = "error"` couldn't be rendered statically because it used `request.url`.
    at eval (webpack-internal:///(rsc)/./node_modules/@auth0/nextjs-auth0/dist/handlers/login.js:60:19)
    at eval (webpack-internal:///(rsc)/./node_modules/@auth0/nextjs-auth0/dist/handlers/router-helpers.js:9:20)
    ... 27 lines matching cause stack trace ...
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  code: 'ERR_LOGIN_HANDLER_FAILURE',
  cause: StaticGenBailoutError: Page with `dynamic = "error"` couldn't be rendered statically because it used `request.url`.
      at Object.staticGenerationBailout (webpack-internal:///(rsc)/./node_modules/next/dist/client/components/static-generation-bailout.js:31:15)
      at handleReqBailout (webpack-internal:///(rsc)/./node_modules/next/dist/server/future/route-modules/app-route/helpers/proxy-request.js:93:23)
      at Object.get (webpack-internal:///(rsc)/./node_modules/next/dist/server/future/route-modules/app-route/helpers/proxy-request.js:101:13)
      at eval (webpack-internal:///(rsc)/./node_modules/@auth0/nextjs-auth0/dist/handlers/login.js:54:37)
      at eval (webpack-internal:///(rsc)/./node_modules/@auth0/nextjs-auth0/dist/handlers/router-helpers.js:9:20)
      at eval (webpack-internal:///(rsc)/./node_modules/@auth0/nextjs-auth0/dist/handlers/auth.js:59:30)
      at eval (webpack-internal:///(rsc)/./node_modules/@auth0/nextjs-auth0/dist/handlers/auth.js:35:24)
      at eval (webpack-internal:///(rsc)/./node_modules/next/dist/server/future/route-modules/app-route/module.js:254:43)
      at eval (webpack-internal:///(rsc)/./node_modules/next/dist/server/lib/trace/tracer.js:111:36)
      at NoopContextManager.with (webpack-internal:///(rsc)/./node_modules/next/dist/compiled/@opentelemetry/api/index.js:360:30)
      at ContextAPI.with (webpack-internal:///(rsc)/./node_modules/next/dist/compiled/@opentelemetry/api/index.js:30:58)
      at NoopTracer.startActiveSpan (webpack-internal:///(rsc)/./node_modules/next/dist/compiled/@opentelemetry/api/index.js:953:34)
      at ProxyTracer.startActiveSpan (webpack-internal:///(rsc)/./node_modules/next/dist/compiled/@opentelemetry/api/index.js:993:36)
      at eval (webpack-internal:///(rsc)/./node_modules/next/dist/server/lib/trace/tracer.js:100:107)
      at NoopContextManager.with (webpack-internal:///(rsc)/./node_modules/next/dist/compiled/@opentelemetry/api/index.js:360:30)
      at ContextAPI.with (webpack-internal:///(rsc)/./node_modules/next/dist/compiled/@opentelemetry/api/index.js:30:58)
      at NextTracerImpl.trace (webpack-internal:///(rsc)/./node_modules/next/dist/server/lib/trace/tracer.js:100:32)
      at eval (webpack-internal:///(rsc)/./node_modules/next/dist/server/future/route-modules/app-route/module.js:242:53)
      at AsyncLocalStorage.run (node:async_hooks:346:14)
      at Object.wrap (webpack-internal:///(rsc)/./node_modules/next/dist/server/async-storage/static-generation-async-storage-wrapper.js:42:24)
      at eval (webpack-internal:///(rsc)/./node_modules/next/dist/server/future/route-modules/app-route/module.js:196:97)
      at AsyncLocalStorage.run (node:async_hooks:346:14)
      at Object.wrap (webpack-internal:///(rsc)/./node_modules/next/dist/server/async-storage/request-async-storage-wrapper.js:82:24)
      at eval (webpack-internal:///(rsc)/./node_modules/next/dist/server/future/route-modules/app-route/module.js:195:75)
      at AsyncLocalStorage.run (node:async_hooks:346:14)
      at AppRouteRouteModule.execute (webpack-internal:///(rsc)/./node_modules/next/dist/server/future/route-modules/app-route/module.js:192:56)
      at AppRouteRouteModule.handle (webpack-internal:///(rsc)/./node_modules/next/dist/server/future/route-modules/app-route/module.js:315:41)
      at doRender (/Users/apatel1/Desktop/Projects/cost-plus/costplusdrugs-commerce/node_modules/next/dist/server/base-server.js:1091:56)
      at cacheEntry.responseCache.get.incrementalCache.incrementalCache (/Users/apatel1/Desktop/Projects/cost-plus/costplusdrugs-commerce/node_modules/next/dist/server/base-server.js:1290:46)
      at /Users/apatel1/Desktop/Projects/cost-plus/costplusdrugs-commerce/node_modules/next/dist/server/response-cache/index.js:99:42
      at ResponseCache.get (/Users/apatel1/Desktop/Projects/cost-plus/costplusdrugs-commerce/node_modules/next/dist/server/response-cache/index.js:149:11)
      at DevServer.renderToResponseWithComponentsImpl (/Users/apatel1/Desktop/Projects/cost-plus/costplusdrugs-commerce/node_modules/next/dist/server/base-server.js:1219:53)
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
    code: 'NEXT_STATIC_GEN_BAILOUT'
  },
  status: undefined
}

Reproduction
I have just followed the steps provided in this documents: https://auth0.com/docs/quickstart/webapp/nextjs/01-login
Next.js version: 13.4.16
Additional context
No response

Hi @abhi-codal - thanks for raising this
I've not seen this error before and can't reproduce it on the sample app. Could you share a repo that demonstrates the issue and I'd be happy to debug it for you

i also have the same problem
StaticGenBailoutError: Page with dynamic = "error"couldn't be rendered statically because it usedrequest.url.     at Object.staticGenerationBailout (webpack-internal:///(rsc)/./node_modules/next/dist/client/components/static-generation-bailout.js:31:15)     at handleReqBailout (webpack-internal:///(rsc)/./node_modules/next/dist/server/future/route-modules/app-route/helpers/proxy-request.js:93:23)     at Object.get (webpack-internal:///(rsc)/./node_modules/next/dist/server/future/route-modules/app-route/helpers/proxy-request.js:101:13)     at login (webpack-internal:///(rsc)/./app/api/auth/[auth0]/route.ts:32:64)     at eval (webpack-internal:///(rsc)/./node_modules/@auth0/nextjs-auth0/dist/handlers/auth.js:59:30)     at eval (webpack-internal:///(rsc)/./node_modules/@auth0/nextjs-auth0/dist/handlers/auth.js:35:24)     at eval (webpack-internal:///(rsc)/./node_modules/next/dist/server/future/route-modules/app-route/module.js:254:43)     at eval (webpack-internal:///(rsc)/./node_modules/next/dist/server/lib/trace/tracer.js:111:36)     at NoopContextManager.with (webpack-internal:///(rsc)/./node_modules/next/dist/compiled/@opentelemetry/api/index.js:360:30)     at ContextAPI.with (webpack-internal:///(rsc)/./node_modules/next/dist/compiled/@opentelemetry/api/index.js:30:58)     at NoopTracer.startActiveSpan (webpack-internal:///(rsc)/./node_modules/next/dist/compiled/@opentelemetry/api/index.js:953:34)     at ProxyTracer.startActiveSpan (webpack-internal:///(rsc)/./node_modules/next/dist/compiled/@opentelemetry/api/index.js:993:36)     at eval (webpack-internal:///(rsc)/./node_modules/next/dist/server/lib/trace/tracer.js:100:107)     at NoopContextManager.with (webpack-internal:///(rsc)/./node_modules/next/dist/compiled/@opentelemetry/api/index.js:360:30)     at ContextAPI.with (webpack-internal:///(rsc)/./node_modules/next/dist/compiled/@opentelemetry/api/index.js:30:58)     at NextTracerImpl.trace (webpack-internal:///(rsc)/./node_modules/next/dist/server/lib/trace/tracer.js:100:32)     at eval (webpack-internal:///(rsc)/./node_modules/next/dist/server/future/route-modules/app-route/module.js:242:53)     at AsyncLocalStorage.run (node:async_hooks:338:14)     at Object.wrap (webpack-internal:///(rsc)/./node_modules/next/dist/server/async-storage/static-generation-async-storage-wrapper.js:42:24)     at eval (webpack-internal:///(rsc)/./node_modules/next/dist/server/future/route-modules/app-route/module.js:196:97)     at AsyncLocalStorage.run (node:async_hooks:338:14)     at Object.wrap (webpack-internal:///(rsc)/./node_modules/next/dist/server/async-storage/request-async-storage-wrapper.js:82:24)     at eval (webpack-internal:///(rsc)/./node_modules/next/dist/server/future/route-modules/app-route/module.js:195:75)     at AsyncLocalStorage.run (node:async_hooks:338:14)     at AppRouteRouteModule.execute (webpack-internal:///(rsc)/./node_modules/next/dist/server/future/route-modules/app-route/module.js:192:56)     at AppRouteRouteModule.handle (webpack-internal:///(rsc)/./node_modules/next/dist/server/future/route-modules/app-route/module.js:315:41)     at doRender (/Users/masashiximoto/Documents/Reactproject/mssxmt-xlog/node_modules/next/dist/server/base-server.js:1091:56)     at cacheEntry.responseCache.get.incrementalCache.incrementalCache (/Users/masashiximoto/Documents/Reactproject/mssxmt-xlog/node_modules/next/dist/server/base-server.js:1290:46)     at /Users/masashiximoto/Documents/Reactproject/mssxmt-xlog/node_modules/next/dist/server/response-cache/index.js:99:42     at ResponseCache.get (/Users/masashiximoto/Documents/Reactproject/mssxmt-xlog/node_modules/next/dist/server/response-cache/index.js:149:11)     at DevServer.renderToResponseWithComponentsImpl (/Users/masashiximoto/Documents/Reactproject/mssxmt-xlog/node_modules/next/dist/server/base-server.js:1219:53)     at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {   code: 'NEXT_STATIC_GEN_BAILOUT' }
Next.js@13.4.19

Adding export const dynamic = "force-static" to the end of the routes.ts file will fix this issue. But will probably fail if you are using tauri

authors: abhi-codal adamjmcgrath jLynx mssxmt


text:
Example how to use it with RS256

Hello,
New auth0.js v8 sends jwt signed with RS256 and I can't make it work with Knock. I've added
config.token_signature_algorithm = 'RS256'
and
config.token_public_key = key.public_key
into initializer but still no luck. Key seems to be correct, at least it works in jwt.io
I would be grateful for any help.
Best, Iurii

Hi @fungi-fungi, we're working on a revamp to this sample and the docs that go along with it. In the meantime, check out this open PR for some guidance on using RS256 https://github.com/auth0-samples/auth0-rubyonrails-api-sample/pull/2

@chenkie @fungi-fungi,  I did a lot of work with this and have some working code allow you to toggle between RS256 and HS256, per controller, without the use of Knock.  It's based on the work done in PR #2.  It needs slight DRY refactoring, but I've been swamped and just de-prioritized it.  It's not in in a public repo, but if you're in a hurry, I can try to get a PR going.
The primary motivation is I couldn't get Knock to work without a full User table, which to me, seems antithetical to having an external user store, especially in an API-only or microservice-type app.  Instead, we create an ActiveModel object for  user to achieve a @current_user object on an API call.  You can populate that in an ActiveSupport::Concern on a successful decoding and you can use it in your controllers.
Then just build your decoder to be something like below (which includes a test case too):
require_relative 'base64_decoder'

class Rs256Decoder
  def self.decode(token)
    if Rails.env.test?
        @rsa_private = OpenSSL::PKey::RSA.new ENV.fetch("RSA_PRIVATE")
        @rsa_public = @rsa_private.public_key
        return JWT.decode(token, @rsa_public, true, # Verify the signature of this token
        {
          :algorithm => 'RS256',
          :iss => Rails.application.secrets.auth0_domain,
          :verify_iss => true,
          :aud => Rails.application.secrets.auth0_api_audience,
          :verify_aud => true
        })
    else
      return JWT.decode(token, nil, true, # Verify the signature of this token
      {
        :algorithm => 'RS256',
        :iss => Rails.application.secrets.auth0_domain,
        :verify_iss => true,
        :aud => Rails.application.secrets.auth0_api_audience,
        :verify_aud => true
      }) do |header|
        jwks_hash[header['kid']]
      end
    end
  end

  def self.jwks_hash
    jwks_raw = Net::HTTP.get URI(Rails.application.secrets.auth0_rsa_domain)
    jwks_keys = Array(JSON.parse(jwks_raw)['keys'])
    Hash[
      jwks_keys
      .map do |k|
        [
          k['kid'],
          OpenSSL::X509::Certificate.new(
            Base64.decode64(k['x5c'].first)
          ).public_key
        ]
      end
    ]
  end
end

Thank you so much @chenkie @mrrobby this solved all my problems, I got myself way too focused on using Knock instead of looking for a more direct solution.

Anytime!  Sounds like we can close this one.

authors: chenkie fungi-fungi mrrobby


text:
Added changelog for 1.7.0

🔧 Changes

For ul login added check to filter and identify only support partials. [#1107]
Support for importing auth0_prompt_screen_renderer terraform resource [#1106]

📚 References

🔬 Testing

📝 Checklist

[ ] All new/changed/fixed functionality is covered by tests (or N/A)
[ ] I have added documentation for all new/changed functionality (or N/A)

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

Project coverage is 70.21%. Comparing base (e765aec) to head (20ee8be).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1110   +/-   ##
=======================================
  Coverage   70.21%   70.21%
=======================================
  Files          94       94
  Lines       13267    13267
=======================================
  Hits         9316     9316
  Misses       3405     3405
  Partials      546      546

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

authors: codecov-commenter duedares-rvj


text:
No Content-type found in the mock response

Mock response doesn’t have Content-type in the header , even if we configure it in the mock response.
"response": {
              "status": 200,
               “headers”: {
                    “Content-type” : “application/json”
               },
              "body": —response body—
}

@arunvelusamyd  - Content-type is part of Response Headers and not available as a separate entity. Checkout Readme file as below

test case response should as below -
"response": {
"status": 200,
"headers":{
“Content-type” : “application/json”
},
"body": —response body—
}
Let us know if you still face any issue

Seems like, @arunvelusamyd is fixing this in branch ISS-212-mock-response-content-type (work in progress).
For time being, we can proceed with the PR and unblock Mr Arun. 👍
Note:
1)
This repo https://github.com/authorjapps/api-mock-maker supports all things around mocking and very flexible n easy to create mocks. Also uses JSON DSLs.
We should try to use this for our mocking if we can maintain the mocks separately.
2)
If not, then we can integrate the above code into core module i.e. situations where we want the test-cases to have the mocks in the same JSON file(good for Integration Testing for a Dev-Build or commit-build in Jenkins) as earlier steps. The drawback in this approach is the test-cases become verbose for end-to-end testing as we don't need mocks for black-box testing.
Hence both have merits and pain, let's support both approaches going forward.
Let's do it in a separate ticket 👍 .

@authorjapps  - I don't think we need to fix anything here. Whenever any REST api respond then content comes either part of Header or Body section. Then why do we need to created new entity apart from header/body.
Not sure if I am missing any other information or didn't understand what you are fixing.

@aghorpade
Sorry, it was typo. It was part of response headers. Update my comment.

PR has been merged. This will be available in 1.3.4

Released now.
<dependency>
  <groupId>org.jsmart</groupId>
  <artifactId>zerocode-tdd</artifactId>
  <version>1.3.4</version>
</dependency>

Maven Link: https://search.maven.org/artifact/org.jsmart/zerocode-tdd/1.3.4/jar

authors: aghorpade arunvelusamyd authorjapps

repo: authorjapps/zerocode


text:
Use nilness linter

This will also point out some stuff
go install golang.org/x/tools/go/analysis/passes/nilness/cmd/nilness@latest

nilness ./...

myjson/db.go:348:10: impossible condition: nil != nil
myjson/schema.go:62:9: impossible condition: nil != nil
myjson/schema.go:68:9: impossible condition: nil != nil
myjson/tx.go:220:9: impossible condition: non-nil == nil

done, thanks @marcelloh !


text:
Add a SharePolicy

Problem: we announce documents to all connected peers and we share documents with anyone who knows the document ID. Most applications probably want some control over authorization.
Solution: introduce SharePolicy, which is a trait users implement and pass to Repo::with_share_policy to control when documents are shared.
This is a pretty naive encoding of a SharePolicy trait. In particular it returns a BoxFuture<'static, ..> for each method on SharePolicy, which means we're doing dynamic dispatch on every access control decision. I think this is probably not an issue given that the IO we're doing should dominate runtimes, but if it becomes an issue we can add a generic parameter to Repo and thread that through.

Reviewing...

extract the core state machine of this libary into a separate module

Great idea!
Reviewing...

authors: alexjg gterzian

repo: automerge/automerge-repo-rs


text:
Add support for several other HPO tools

In order to maximize the potential users of DeepCave, we should aim to support more HPO tools. In particular, we should write converters for

SyneTune
BoTorch
HEBO
Ray Tune

See how this relates to #58.

Added Converter for Optuna in #173

authors: alexandertornede sarah-segel

repo: automl/DeepCAVE


text:
MySQLCommunityServer.pkg.recipe does not set pkg_path

MySQLCommunityServer.pkg.recipe is not setting pkg_path because you are using the Copier processor instead of the PkgCopier processor. My suggestion is that you switch to the PkgCopier processor so that subsequent .jss or .jamf recipes pick up the package.

Thanks for the suggestion Graham.  I've made the recommended changes in the above commits.

Thanks!


text:
feat(setup, ansible): add an option for not installing cuda-drivers

Description

According to https://docs.nvidia.com/cuda/eula/index.html#attachment-a, only cuda-drivers have different requirements for redistribution.

The NVIDIA CUDA Driver Libraries are only distributable in applications that meet this criteria:

The application was developed starting from a NVIDIA CUDA container obtained from Docker Hub or the NVIDIA GPU Cloud, and
The resulting application is packaged as a Docker container and distributed to users on Docker Hub or the NVIDIA GPU Cloud only.

I'd like to add an option to install cuda-drivers or not for more flexibility.
The explanation for each meta-package is here: https://docs.nvidia.com/cuda/cuda-installation-guide-linux/index.html#package-manager-metas
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

My test results:
$ ./setup-dev-env.sh
...
TASK [autoware.dev_env.cuda : Install cuda-drivers] ****************************************************************************************************************************
ok: [localhost]

$ ./setup-dev-env.sh --no-cuda-drivers
...
TASK [autoware.dev_env.cuda : Install cuda-drivers] ****************************************************************************************************************************
skipping: [localhost]

Additional information:
$ sudo apt depends cuda-11-7
cuda-11-7
  Depends: cuda-runtime-11-7 (>= 11.7.0)
  Depends: cuda-toolkit-11-7 (>= 11.7.0)
  Depends: cuda-demo-suite-11-7 (>= 11.7.50)

$ sudo apt depends cuda-toolkit-11-7
cuda-toolkit-11-7
  Depends: cuda-compiler-11-7 (>= 11.7.0)
  Depends: cuda-libraries-11-7 (>= 11.7.0)
  Depends: cuda-libraries-dev-11-7 (>= 11.7.0)
  Depends: cuda-tools-11-7 (>= 11.7.0)
  Depends: cuda-documentation-11-7 (>= 11.7.50)
  Depends: cuda-nvml-dev-11-7 (>= 11.7.50)

$ sudo apt depends cuda-runtime-11-7
cuda-runtime-11-7
  Depends: cuda-libraries-11-7 (>= 11.7.0)
  Depends: cuda-drivers (>= 515.43.04)

repo: autowarefoundation/autoware


text:
feat(docker): introduce autoware-core stage

Description

[ ] #4712

This PR adds the autoware-core stage between the base and prebuilt stages.
This is a milestone for the multi-stage per-component builds mentioned in the discussion below. I will break down the prebuilt stage further in the next PR.
https://github.com/orgs/autowarefoundation/discussions/4661
The graph of the stage structure is shown below.

Effects on system behavior

Not applicable.
Interface changes

@mergifyio refresh

authors: xmfcx youtalk


text:
Use meters as altitude format for KML.

Fixes #70

LGTM

authors: pmtischler prattmic

repo: auvsi-suas/interop


text:
Clean up "-D" compile time macros used in pc-linux build

This is the equivalent of trac 17 in the CFE PSP -- see [https://babelfish.arc.nasa.gov/trac/cfs_psp/ticket/17].  The same build flags are duplicated in the OSAL BSP.
The "pc-linux" OSAL BSP defines the following to be added to the compiler CFLAGS:
{{{-D_EL -DENDIAN=EL -DSOFTWARE_LITTLE_BIT_ORDER -D__ix86_ -D_ix86_ -Dposix -DX86PC -D_REENTRANT -D_EMBED_ -DOS_DEBUG_LEVEL=3}}}
These were brought into the cmake build from the original build scripts in order to be consistent just in case any code required it.  However, they are unnecessary, many are not even used anywhere in CFE/OSAL, and potentially even wrong.
The reality is that with Linux, the "pc-linux" is a general purpose PSP that can most likely be used on any general-purpose development machine that runs Linux.  It is not limited to only x86 PC's, and in fact works just fine on ARM, PowerPC, and Microblaze targets too.
I have successfully used the (unmodified) pc-linux BSP to execute unit tests on a BeagleBone Black (ARM) as well as an emulated PowerPC 440 based development machine.  In all these cases, the "x86" macros are wrong, and on the PowerPC, the EL/ENDIAN/SOFTWARE_LITTLE_BIT_ORDER are wrong too.
To summarize - I recommend removing ALL of these macros from the pc- linux build when using the cmake scripts (the old makefiles can stay as- is).

Trac comment by jphickey on 2015-04-14 12:57:48:
This changeset has been rebased to the (unapproved) 2015-04-14 baseline
This is due to a dependency on files added/changed as part of that basline.  Attempting to base this change on the official 2015-02-26 OSAL is potentially possible but will result in merge conflicts when putting these back together again.
Commit [changeset:ce108a3] is ready for review

Imported from trac issue 27.  Created by jphickey on 2015-03-18T12:09:07, last modified: 2015-11-20T16:22:16

Trac comment by sstrege on 2015-05-19 10:53:38:
The SOFTWARE_BIG_BIT_ORDER flag is used in the cFE's ccsds.h file.
The SOFTWARE_LITTLE_BIT_ORDER flag is used in the cFE UTF and elf tool makefiles.

Trac comment by glimes on 2015-05-18 20:11:16:
Accept based on commit [changeset:8662839]
The only flag being removed that I ever saw used
was SOFTWARE_LITTLE_BIT_ORDER, and that code
could and should have been written to not need it.
If it still exists, I'll gladly provide the rewrite.

Trac comment by jphickey on 2015-05-19 11:23:50:
Replying to [comment:3 sstrege]:

The SOFTWARE_BIG_BIT_ORDER flag is used in the cFE's ccsds.h file.
The SOFTWARE_LITTLE_BIT_ORDER flag is used in the cFE UTF and elf tool makefiles.

Re: SOFTWARE_BIG_BIT_ORDER
Thanks for pointing this one out - this is a new one that wasn't there in CFE 6.3.2 which is the version that I am porting all these changes from.
It appears that the related CFE_MAKE_BIG16 macro was also added to some table definitions in the SC app.
Seems relatively easy to modify SC to not need this, though - as it is just hard-coded tables.  Wouldn't it be easier to define the SC table simply as uint8's, and therefore not need any macro magic?
Re: SOFTWARE_LITTLE_BIT_ORDER
These may be left in the makefile due to cut-and-paste, but they are not serving any purpose as the code doesn't use them.  In fact, these would be wrong if building UT for a big endian processor, which is IMO evidence why these //do// need to be purged out.
This change set is only currently removing these macros from the CMake build.

Trac comment by acudmore on 2015-06-01 14:09:56:
Approve as this applies to the CMake build.
Comment 4 looks like a good case for removing the macros in the traditional make system. But we at least have to figure out what to do with the tables.

Trac comment by glimes on 2015-07-13 12:51:23:
Approve.

Trac comment by jphickey on 2015-07-09 14:17:52:
== REBASED AND UPDATED ==
For the 2015-07-14 CCB review/discussion

Commit [changeset:4aaaf64] contains the original modification rebased to the current OSAL development version.
Commit [changeset:543eecb] contains an additional modification to address concerns about code out there that might still depend on {{{SOFTWARE_BIG_BIT_ORDER}}} or {{{SOFTWARE_LITTLE_BIT_ORDER}}}.

Both of these are merged into the {{{ic-2015-07-14}}} integration candidate for evaluation.

Trac comment by sduran on 2015-07-14 11:49:38:
Approve (compatibility macro is good)

Trac comment by jwilmot on 2015-07-14 12:36:37:
Recommend accept.

Trac comment by glimes on 2015-07-16 10:17:16:
Included in [changeset:ec67bd4 2015-07-14 development merge],
now present on Babelfish and IPAS-LIB.


text:
Make admin function for duplicaton of gameversion and scenario

To create alternatives (and translations), duplication of a complete scenario or game version would save a lot of work. All dependent tables except the gameplay tables should be copied in a cascading fashion.

In addition, deletion of unused scenarios, and unused game versions can be added (to delete test versions). For this purpose, it would also be handy to delete a test gamesession. The deletion follows the cloning, but in reverse order.

The code will be added as static helper functions in the SqlUtils class. For cloning, the name will be appended with (1), (2), etc. The user can change this name after cloning.

Cloning and deleting of ScenarioParameters and Scenario has been tested, and it works. Results have been checked in the database as well.

GameVersion, Scenario, and ScenarioParameters can be cloned and cascadingly destroyed.

repo: averbraeck/housinggame-admin


text:
Rework update action settings

The update action settings need to be reworked because the workflow of updates has changed and some options are no longer needed or make sense.

This issue is related to issue #9

repo: avereon/xenon


text:
Add full time period as an option

Right now the biggest time period you can select is one year, it would be nice if there was an option to see the stats for the languages and repositories from the moment you created your github account until the present.

Yeah this feature is really missing

This is finally implemented! Check it out on the website, and note it may take a couple minutes to fetch all your data the first time. Let me know if you run into any issues.

authors: OrangoMango avgupta456 vycdev


text:
@nograd not defined when trying to run teapot_rendering.jl

$ julia --project=. --color=yes teapot_rendering.jl
┌ Warning: Package Colors does not have Printf in its dependencies:
│ - If you have Colors checked out for development and have
│   added Printf as a dependency but haven't updated your primary
│   environment's manifest file, try `Pkg.resolve()`.
│ - Otherwise you may need to report an issue with Colors
└ Loading Printf into Colors from project dependency, future warnings for Colors are suppressed.
┌ Warning: The call to compilecache failed to create a usable precompiled cache file for Flux [587475ba-b771-5e3f-ad9e-33799f191a9c]
│   exception = Required dependency Colors [5ae59095-9a9b-59fe-a467-6f913c188581] failed to load from a cache file.
└ @ Base loading.jl:1041
┌ Warning: Package Colors does not have Printf in its dependencies:
│ - If you have Colors checked out for development and have
│   added Printf as a dependency but haven't updated your primary
│   environment's manifest file, try `Pkg.resolve()`.
│ - Otherwise you may need to report an issue with Colors
└ Loading Printf into Colors from project dependency, future warnings for Colors are suppressed.
WARNING: ImageQualityIndexes.psnr is deprecated, use assess_psnr instead.
  likely near /home/phil/.julia/packages/Images/0SDGT/src/Images.jl:60
┌ Warning: Package RayTracer does not have CUDAnative in its dependencies:
│ - If you have RayTracer checked out for development and have
│   added CUDAnative as a dependency but haven't updated your primary
│   environment's manifest file, try `Pkg.resolve()`.
│ - Otherwise you may need to report an issue with RayTracer
└ Loading CUDAnative into RayTracer from project dependency, future warnings for RayTracer are suppressed.
ERROR: LoadError: LoadError: LoadError: UndefVarError: **@nograd not defined**
Stacktrace:

[1] top-level scope
 [2] include(::Module, ::String) at ./Base.jl:377
 [3] include(::String) at /home/phil/.julia/packages/RayTracer/rEd4h/src/RayTracer.jl:1
 [4] top-level scope at /home/phil/.julia/packages/RayTracer/rEd4h/src/RayTracer.jl:24
 [5] include(::Module, ::String) at ./Base.jl:377
 [6] top-level scope at none:2
 [7] eval at ./boot.jl:331 [inlined]
 [8] eval(::Expr) at ./client.jl:449
 [9] top-level scope at ./none:3
in expression starting at /home/phil/.julia/packages/RayTracer/rEd4h/src/gradients/zygote.jl:364
in expression starting at /home/phil/.julia/packages/RayTracer/rEd4h/src/gradients/zygote.jl:364
in expression starting at /home/phil/.julia/packages/RayTracer/rEd4h/src/RayTracer.jl:24
ERROR: LoadError: Failed to precompile RayTracer [60dacb86-48ff-11e9-0f01-03ab8794bbc9] to /home/phil/.julia/compiled/v1.4/RayTracer/sUryZ_rlO6L.ji.
Stacktrace:
 [1] error(::String) at ./error.jl:33
 [2] compilecache(::Base.PkgId, ::String) at ./loading.jl:1272
 [3] _require(::Base.PkgId) at ./loading.jl:1029
 [4] require(::Base.PkgId) at ./loading.jl:927
 [5] require(::Module, ::Symbol) at ./loading.jl:922
 [6] include(::Module, ::String) at ./Base.jl:377
 [7] exec_options(::Base.JLOptions) at ./client.jl:288
 [8] _start() at ./client.jl:484
in expression starting at /home/phil/build/RayTracer.jl/examples/teapot_rendering.jl:11

Julia v1.4.0
(@v1.4) pkg> status
Status ~/.julia/environments/v1.4/Project.toml
[4c555306] ArrayLayouts v0.2.4
[08437348] AutoMLPipeline v0.1.11
[336ed68f] CSV v0.6.1
[3895d2a7] CUDAapi v4.0.0
[c5f51814] CUDAdrv v6.2.2
[be33ccc6] CUDAnative v3.0.4
[7057c7e9] Cassette v0.3.1
[3a865a2d] CuArrays v2.0.1
[a93c6f00] DataFrames v0.20.2
[31c24e10] Distributions v0.23.2
[ced4e74d] DistributionsAD v0.5.0
[587475ba] Flux v0.10.4
[7073ff75] IJulia v1.21.2
[6218d12a] ImageMagick v1.1.4
[86fae568] ImageView v0.10.8
[916415d5] Images v0.22.1
[e5e0dc1b] Juno v0.8.1
[1902f260] Knet v1.3.5
[1914dd2f] MacroTools v0.5.5
[91a5bcdd] Plots v1.0.10
[60dacb86] RayTracer v0.1.0 #ap/gpu (https://github.com/avik-pal/RayTracer.jl.git)
[37e2e3b7] ReverseDiff v1.2.0
[5e47fb64] TestImages v1.0.2
[e88e6eb3] Zygote v0.4.15
[10745b16] Statistics

@philtomson Seems like you are using an older version of RayTracer. The latest versions I released yesterday, don't yet work on GPU but I hope to work on it in the upcoming weeks.

I am closing this issue as the examples are working in the latest release

authors: avik-pal philtomson


text:
Fixing a spelling issue

There's a very small mistake that could be rectified.

What is the issue ? Where is the problem ?

I cannot find any spelling mistake. Could you point out the mistake?


text:
Disable checksum

Is there any way to disable checksum check? It's a great feature for sure, but sometimes developers are reckless in creating migration files and hence we probably need to change it later otherwise it won't run for new developers (sometimes we forget to handle what if the collection doesn't exist yet).

Hey @haydarai, it's currently not possible to disable checksums.
mongration was created and designed to guarantee some level of "consistency" when migrating the database. One way of making it "unreliable" is disabling checksums.
Now, thinking about it, maybe it's not that bad to do so, as you really want/need to do that. Looking forward to hear what @eberhara thinks about it.
Anyway, I think PR's are welcome to this feature.

authors: haydarai wmartins

repo: awapps/mongration


text:
Do set(ts.samples()) at the top

There are a few places we will end up checking if a node is a sample. We should initialise the set once, perhaps globally (or stored within the tsdate object), using sample_set=set(ts.samples())) and use it throughout, rather than remake it every time it is needed.

I'm re-writing the find_node_tip_weights() function to be the __init__() function of a FindNodeTips class, which takes an (optional) sample_set param. If this is None, it calculates the sample_set, otherwise it will use the one passed in. That seems like a reasonable way to do this.

Sounds great, good idea!

I've ended up doing quite a lot of code changing (putting things into classes, mainly). I'm in the middle of it now, but it might take a while.

authors: awohns hyanwong

repo: awohns/tsdate


text:
Amplify Gen 2 does not seems to work out of the box.

Environment information
System:
  OS: Windows 11 10.0.22631
  CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
  Memory: 16.91 GB / 31.84 GB
Binaries:
  Node: 20.10.0 - C:\Program Files\nodejs\node.EXE
  Yarn: undefined - undefined
  npm: 10.2.5 - C:\Program Files\nodejs\npm.CMD
  pnpm: undefined - undefined
NPM Packages:
  @aws-amplify/backend: 0.12.1
  @aws-amplify/backend-cli: 0.11.1
  aws-amplify: 6.0.16
  aws-cdk: 2.127.0
  aws-cdk-lib: 2.127.0
  typescript: 5.3.3
AWS environment variables:
  AWS_NODEJS_CONNECTION_REUSE_ENABLED = 1
  AWS_SDK_LOAD_CONFIG = 1
  AWS_STS_REGIONAL_ENDPOINTS = regional
No CDK environment variables

Description
When attempting to deploy a Next.js application using AWS Amplify, I encountered multiple issues across different versions of the setup. Initially, with an older setup of Amplify and Next.js, there were problems out of the box, particularly related to image optimization which required significant changes to the codebase to work around limitations that do not exist in alternative deployment solutions like Vercel.
After upgrading to the latest versions of Next.js and AWS Amplify (referred to as GEN 2 in the context of this report), I aimed for a straightforward deployment with minimal to no configuration changes. Despite this approach, I encountered a critical issue related to the Node.js version compatibility.
Steps to Reproduce

Install the latest versions of Next.js and AWS Amplify.
Set up a basic Next.js application without any modifications specific to Amplify.
Attempt to deploy the application using AWS Amplify with the default build settings.
Encounter the Node.js version compatibility error.
Change the Node version to 20 in the build settings and attempt to redeploy.

Expected Behavior
The deployment process should recognize and use the specified Node.js version setting from the Amplify build settings, allowing for a successful build and deployment of the Next.js application.
Actual Behavior
Despite specifying a Node.js version (20) that meets the requirements for Next.js, the deployment process fails, indicating that it's using Node.js 18.13.0 and requiring a version >= v18.17.0. This occurs even after explicitly setting the Node version to 20 in the build settings.
Error Message
You are using Node.js 18.13.0. For Next.js, Node.js version >= v18.17.0 is required.
2024-02-13T02:53:43.688Z [ERROR]: !!! Build failed

Environment
Next.js Version: latest
Node.js Version (Attempted): 18.13.0 (default), 20 (specified in build settings)
This issue highlights a broader concern regarding the clarity and documentation of supported versions for dependencies, particularly Node.js, within the AWS Amplify environment for Next.js applications**. A clearer specification of compatible versions** and better handling of user-specified versions in the build settings would significantly improve the developer experience.

Hey @latheeshvm, thank you for reaching out. you will need to switch the build image to use al:2023 that supports Node.js versions 18 and 20. Refer to the documentation providing this information

@ykethan That worked well. Thank you.

@latheeshvm thank you for the confirmation. Closing the issue, do reach out to us if you encounter any issues.

authors: latheeshvm ykethan

repo: aws-amplify/amplify-backend


text:
Support for Backup infrastructure

All services that store data should have a way to setup backups
amplify add storage

do you want to create automatic backups?

amplify add api

dynamo
do you want to create automatic backups?

amplify add auth

do you want to create automatic backups?

amplify backup (creates a point in time backup)
amplify restore [backup-date/time]

2 years and no response from the team. Nice!

Well @Straubulous put a p4 on this which I assume means the lowest priority...so I guess the Amazon folks just really trust their infrastructure - despite all the complaints about losing data...

And it appears the cli folks in the other ticket are ok with just editing property files...what's the point of a cli if major functionality has to be done in vi....

Any update?

This is an issue for us too, and it's worth pointing out that while editing the global parameters.json to set the DynamoDBEnablePointInTimeRecovery flag to true (as outlined in aws-amplify/amplify-cli/issues/2186) is a welcome respite, it's not ideal:
Not least because we'd like to be able to set this flag on certain environments only and not all of them - e.g. enable backups in Prod and UAT, but not in lower environments such as individual developer environments.

I just published a blog in the AWS Storage channel last week that provides the definition for a CDK custom resource to setup backups with AWS Backup. Take a look and see if this solves for your need.
https://aws.amazon.com/blogs/storage/automate-backups-for-aws-amplify-graphql-backends-with-aws-backup/

authors: GeorgeBellTMH cgaege danrivett kevinschwarz mstoyanovv

repo: aws-amplify/amplify-category-api