timezone information is dropped and everything is displayed in UTC for timezoned data

Steps To Reproduce

create a query which returns data with at least one column with timestamp with timezone data, make sure the data is in a non UTC timezone
load it in a page
put it in a datatable and see that data is in UTC format

in the same category if you use a timestamp in a where clause with timezone info no data is returned.
Environment

Node version (node -v): v20.11.1
npm version (npm -v): 10.4.0
OS: archlinux 6.6.10-arch1-1-surface  SMP PREEMPT_DYNAMIC Sat, 13 Jan 2024 00:20:37 +0000 x86_64 GNU/Linux
Browser: firefox
Database: postgresql

Expected Behavior
data is in the timezone that the source was in
Actual Behaviour
data is shown in UTC
Workarounds
to get both the visualization as well as the filtering working it is needed to load the icu extension and then do a double timezone conversion. steps to do this:

add "@duckdb/duckdb-wasm": "1.28.1-dev148.0" to overrides in packages.json and install
add at the top of your page the following snippit:
adjust your filter to use for example time >= TIMESTAMPTZ '2024-01-01 00:00:00 Europe/Amsterdam'
double convert your time column like this: "time" at time zone 'UTC' at time zone 'Europe/Amsterdam' as time

now the data should be correctly filtered and shown
WARNING: this newer version of duckdb-wasm has not been fully tested with evidence! it seems to work but behold for edge cases.
Drawbacks to workaround:
when clicking download data from for example datatable or linechart the data in the csv is shown as being UTC (with the Z) time but that is wrong, its actually in the local timezone specified. this is actually wrong instead of different dispaly then you want so be aware
possible ideas for feature to fix this
as a feedback point it would be great if the timezone shown on a page would be configurable, both as a global default as well as a possible override per page or query

I just wanted to add that I too am running into this issue. My case is specifically with a dateRange component to filter out data. That goes wrong. This makes it for me impossible to use Evidence as almost all our reports have or will have a date based filter.
I do not have any specific timestamptz type of fields in my table but regular timestamp. But as the timezone of the postgresql server I am using is Europe/Amsterdam I guess all timestamp fields are in fact timestamptz.

Just to add some info here, here's some more info about the workaround above:

you need to add an override in your package.json to use a later version of DuckDB WASM than Evidence currently installs
'add at the top of your page' --> I added it in a custom +layout.svelte file (as in https://docs.evidence.dev/reference/themes-and-layouts/ )
the double conversion can be made a little more livable by also adding a macro to the layout as follows and using that

    query(
        "CREATE FUNCTION tz_fix(x, b := 'Europe/Amsterdam') AS (x::TIMESTAMP at time zone 'UTC' at time zone b);",
    );

and then using that for double conversions in time columns like so tz_fix("time"). Also lets you optionally use other time zones in case of need
The handy part about using a macro here is that it should be easier to 'remove' the fix in various places as soon as Evidence has a more permanent solution, simply by changing the function to a no-op

Just to add again, I found that Evidence refuses to make a production build (weird 500 error) if you attempt this hack. The root cause of this is build behavior vs dev behavior, where the timing of the query calls seems to be different.
The way to fix that is to force rendering to wait until the extensions are actually loaded, by adjusting your +layout.svelte something like this. Note that the workaround below can be applied to basically anything async that you want to wait for before any page load.

{#await installICU()}

Loading

{:then result}
    <EvidenceDefaultLayout {data}>
        <slot slot="content" />
    </EvidenceDefaultLayout>
{:catch error}

{error.message}

{/await}

Another addition: use
CREATE OR REPLACE FUNCTION

instead of just
CREATE FUNCTION

to maintain stability with HMR

Another addition:
Unfortunately, this fix does not work well. It breaks (at least) the following functionality on build (not in dev mode):

templates pages do not render
all-queries.json + arrow files do not pregenerate (=query result caching), causing a performance drop in the built dashboard

Use at your own risk!

I have taken some time to chase this down.
Evidence has several stages of it's data pipeline, so I wanted to ensure we know what we are doing at each stage.
Stages
npm run sources

Data in the native DB (eg Postgres, DuckDB), using native DB types
Data gets read by the native nodejs connector, and converted into JS types
Data is mapped from JS types into a set of 4 evidence types (string, number, bool, datetime)
Data is converted from an JS Array into an arrow vector, columnwise, and then into an arrow table
Data is written from arrow table into parquet file on disk

npm run dev
6. DuckDB wasm reads data from parquet file based on markdown query
7. Data is saved in Query Store
8. Components read data from query store (back to JS array)
9. Components format data and display it
Complications

JS does not have a concept of timezone aware timestamps. All timestamps are stored as milliseconds since 1970, in UTC.
Some "databases" do not have a native concept of time (eg SQLite, CSV) and use local time strings to represent time
Some developers choose (or use systems that choose) to store data in timestamps without timezones, but with an implicit timezone choice of their local TZ. If you change the system timezone it can changes the implied timestamp

Evidence Today
I have run an end to end test using DuckDB to confirm current behaviour.

Evidence takes values as they come out of queries, and doesn't change them.
However, some(!) components choose to render these values in UTC. Specifically the DataTable, and the QueryViewer
If they don't have a timezone specified, it assumes they are UTC

Fixes

For databases/sources that do not have timezone support, we should give people the option to configure a timezone.
The DataTable and QueryViewer should not silently convert dates to UTC
(Eventually) We should support allowing users to change the display timezone to one other than their browsers'

Hi Archie,
Thanks for the write up. Perhaps good to mention that in order to get timezone support in duckdb you need to load ICU extention. If you do that you are already 90% there
-------- Original Message --------
On 08/06/2024 10:38, Archie Sarre Wood  wrote:

I have taken some time to chase this down.
Evidence has several stages of it's data pipeline, so I wanted to ensure we know what we are doing at each stage.
Stages
npm run sources

Data in the native DB (eg Postgres, DuckDB), using native DB types
Data gets read by the native nodejs connector, and converted into JS types
Data is mapped from JS types into a set of 4 evidence types (string, number, bool, datetime)
Data is converted from an JS Array into an arrow vector, columnwise, and then into an arrow table
Data is written from arrow table into parquet file on disk

npm run dev
6. DuckDB wasm reads data from parquet file based on markdown query
7. Data is saved in Query Store
8. Components read data from query store (back to JS array)
9. Components format data and display it
Complications

JS does not have a concept of timezone aware timestamps. All timestamps are stored as milliseconds since 1970, in UTC.
Some "databases" do not have a native concept of time (eg SQLite, CSV) and use local time strings to represent time
Some developers choose (or use systems that choose) to store data in timestamps without timezones, but with an implicit timezone choice of their local TZ. If you change the system timezone it can changes the implied timestamp

Evidence Today
I have run an end to end test using DuckDB to confirm current behaviour.

Evidence takes values as they come out of queries, and doesn't change them.
However, some(!) components choose to render these values in UTC. Specifically the DataTable, and the QueryViewer
If they don't have a timezone specified, it assumes they are UTC

Fixes

For databases/sources that do not have timezone support, we should give people the option to configure a timezone.
The DataTable and QueryViewer should not silently convert dates to UTC
(Eventually) We should support allowing users to change the display timezone to one other than their browsers'

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

This should now be unblocked with the latest release of DuckDB WASM


Hovercard anchor is lost when using hide transition effect

This issue was imported from Closure Library's previous home at http://closure-library.googlecode.com
The link to the original issue is:
https://code.google.com/p/closure-library/issues/detail?id=515

From original issue:
What steps will reproduce the problem?

HTML:
ab

JS:
var hc = new goog.ui.HoverCard({ "A": "tooltip" });
hc.setTransition(showTransition, hideTransition)
hc.addEventListener 'beforeshow' ->
hc.getAnchorElement() === undefined

move your mouse from link a to link b

What is the expected output? What do you see instead?
expected: hc.anchor is link b.
actual: hc.anchor is undefined.
What version of the product are you using? On what operating system?
latest.
"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/537.11 (KHTML, like Gecko) Chrome/23.0.1271.64 Safari/537.11"
Please provide any additional information below.
stack trace:
goog.ui.Tooltip.onHide_ (tooltip.js:524)
  > this.anchor = undefined; // this.getState() === goog.ui.Tooltip.State.WAITING_TO_SHOW
goog.ui.AdvancedTooltip.onHide_ (advancedtooltip.js:205)
goog.ui.HoverCard.onHide_ (hovercard.js:344)
goog.ui.PopupBase.continueHidingPopup_ (popupbase.js:624)
(anonymous function) (base.js:1093)
goog.events.Listener.handleEvent (listener.js:178)
goog.events.fireListener (events.js:782)
goog.events.fireListeners_ (events.js:758)
goog.events.dispatchEvent (events.js:881)
goog.events.EventTarget.dispatchEvent (eventtarget.js:181)
goog.fx.Animation.dispatchAnimationEvent (animation.js:451)
goog.fx.TransitionBase.onEnd (transitionbase.js:176)
goog.fx.dom.PredefinedEffect.onEnd (dom.js:117)
goog.fx.dom.FadeOutAndHide.onEnd (dom.js:508)
goog.fx.Animation.stop (animation.js:306)
goog.ui.PopupBase.setVisible (popupbase.js:438)
  > if (this.hideTransition_) this.hideTransition_.stop(); // state_ === goog.fx.TransitionBase.State.PLAYING
goog.ui.Tooltip.positionAndShow_ (tooltip.js:614)
  > this.anchor = el;
goog.ui.Tooltip.maybeShow (tooltip.js:551)
goog.ui.HoverCard.maybeShow (hovercard.js:403)

This issue is being closed as a preparation step before archiving the repository.  See the README for more detail.


Responsive Footer

I changed Footer and also made it responsive such that other components in website does not get affected . Please review it and merge it
Fixes Changed Footer #532
Screenshot :

[x] Responsiveness with respect to website
[x] Code follows the established coding style guidelines
[x] All tests are passing

Please review the changes and merge the code into main code base.

After reviewing your footer contribution , its not fitting and look as expected !
As you can work on another area such as database related or fixing bugs for the application !

I am closing this issue Thank you


refactor importer_yielder.py

Do we really need this file ? Could the importer classes help enclosing these information ?
@pombredanne can you shed a little more light here ?
via https://github.com/nexB/vulnerablecode/wiki/WeeklyMeetings#meeting-on-thursday-2021-07-15-at-1200-utc

Dumping importer_yielder

Simply store data source as concrete lists
Don't store configuration or last run, maybe we can have better Log Importer Runs later. Ticket: https://github.com/nexB/vulnerablecode/issues/526

Consider: https://github.com/nexB/scancode-toolkit/blob/develop/src/packagedcode/init.py#L41
via https://github.com/nexB/vulnerablecode/wiki/WeeklyMeetings#meeting-on-tuesday-2021-08-10-at-1400-utc


Setup of sensor platform kia_uvo is taking over 10 seconds.

Region and Brand of car
UK, Hyundai
Version of the integration
Integration Version: v.2.14.1
Home Assistant Version:  2023.9.3
Describe the bug
A clear and concise description of what the bug is.
Recently the kia_uvo integration has been slowing down the startup of my home assistant installation.
I've noticed the below error logs (included the DEBUG entries prior to this occurring too)
Debug logs if an error occurred
2023-09-30 15:11:37.095 DEBUG (SyncWorker_9) [hyundai_kia_connect_api.KiaUvoApiEU] hyundai_kia_connect_api - get_driving_info responseAlltime {'retCode': 'S', 'resCode': '0000', 'resMsg': {'drivingInfo': [{'drivingPeriod': 0, 'totalPwrCsp': 11784, 'motorPwrCsp': 7041, 'climatePwrCsp': 1503, 'eDPwrCsp': 3240, 'batteryMgPwrCsp': 0, 'regenPwr': 9429, 'calculativeOdo': 96}, {'drivingPeriod': 1, 'totalPwrCsp': 1071, 'motorPwrCsp': 640, 'climatePwrCsp': 136, 'eDPwrCsp': 294, 'batteryMgPwrCsp': 0, 'regenPwr': 857, 'calculativeOdo': 8.727272727272727}], 'drivingInfoDetail': [{'drivingPeriod': 1, 'drivingDate': '202309', 'totalPwrCsp': 1103, 'motorPwrCsp': 604, 'climatePwrCsp': 99, 'eDPwrCsp': 400, 'batteryMgPwrCsp': 0, 'regenPwr': 824, 'calculativeOdo': 8}, {'drivingPeriod': 1, 'drivingDate': '202308', 'totalPwrCsp': 6677, 'motorPwrCsp': 4458, 'climatePwrCsp': 749, 'eDPwrCsp': 1470, 'batteryMgPwrCsp': 0, 'regenPwr': 5901, 'calculativeOdo': 62}, {'drivingPeriod': 1, 'drivingDate': '202307', 'totalPwrCsp': 4004, 'motorPwrCsp': 1979, 'climatePwrCsp': 655, 'eDPwrCsp': 1370, 'batteryMgPwrCsp': 0, 'regenPwr': 2704, 'calculativeOdo': 26}]}, 'msgId': '8ed7df3c-0da2-4b99-9e8c-791149a69b9e'}
2023-09-30 15:11:37.229 DEBUG (SyncWorker_9) [hyundai_kia_connect_api.KiaUvoApiEU] hyundai_kia_connect_api - get_driving_info response30d {'retCode': 'S', 'resCode': '0000', 'resMsg': {'drivingInfo': [{'drivingPeriod': 0, 'totalPwrCsp': 210, 'motorPwrCsp': 10, 'climatePwrCsp': 0, 'eDPwrCsp': 200, 'batteryMgPwrCsp': 0, 'regenPwr': 0, 'calculativeOdo': 0}, {'drivingPeriod': 1, 'totalPwrCsp': 105, 'motorPwrCsp': 5, 'climatePwrCsp': 0, 'eDPwrCsp': 100, 'batteryMgPwrCsp': 0, 'regenPwr': 0, 'calculativeOdo': 0}, {'drivingPeriod': 2}], 'drivingInfoDetail': [{'drivingPeriod': 0, 'drivingDate': '20230913', 'totalPwrCsp': 106, 'motorPwrCsp': 6, 'climatePwrCsp': 0, 'eDPwrCsp': 100, 'batteryMgPwrCsp': 0, 'regenPwr': 0, 'calculativeOdo': 0}, {'drivingPeriod': 0, 'drivingDate': '20230912', 'totalPwrCsp': 104, 'motorPwrCsp': 4, 'climatePwrCsp': 0, 'eDPwrCsp': 100, 'batteryMgPwrCsp': 0, 'regenPwr': 0, 'calculativeOdo': 0}, {'drivingPeriod': 0, 'drivingDate': '20230901', 'totalPwrCsp': 893, 'motorPwrCsp': 594, 'climatePwrCsp': 99, 'eDPwrCsp': 200, 'batteryMgPwrCsp': 0, 'regenPwr': 824, 'calculativeOdo': 8}]}, 'msgId': '9bf7e4c0-ace3-4171-b887-e88e51b1a9e6'}
2023-09-30 15:11:37.229 ERROR (SyncWorker_9) [hyundai_kia_connect_api.KiaUvoApiEU] Failed to parse driving info. Possible reasons:
                                    - incompatible vehicle (ICE)
                                    - new API format
                                    - API outage

Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/hyundai_kia_connect_api/KiaUvoApiEU.py", line 331, in update_vehicle_with_cached_state
    state = self._get_driving_info(token, vehicle)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/hyundai_kia_connect_api/KiaUvoApiEU.py", line 1055, in _get_driving_info
    drivingInfoItem["totalPwrCsp"]
ZeroDivisionError: division by zero

To Reproduce
Restart homeassistant
Expected behavior
Integration to load without error and within acceptable timeframe

Also experiencing this. My guess is that it's due to the component loading all of the vehicle data on startup. Those requests take some time to go through on my end.
Maybe to mitigate this, we store the vehicle data in a table. We can then use a last updated time stamp to determine whether or not we should request new data from BlueLink, rather than load it into memory each time the program starts.
Another way could be by making the request happen asynchronously, since waiting for it blocks HA from finishing startup.

great suggestions, I would go with option 1 because home assistant is signaling all integrations about readiness of the system (if everything is loaded and initialized)
If we skip the initial loading and initialize afterwards in unknown timeframe, we would not give the right signal to the rest of the ecosystem.
Agree on option 1, store the last updated at and check if it is in limits. If yes, use the cached values, if not ask for a new update.
Other than that, I am personally not bothered with this at all.
but the issue coming from @capandcamera is not related to a warning but an actual bug in the code, we should never divide something to zero :)


Hyper should skip automatic Content-Length header for HTTP 304 responses

It's unnecessary, see RFC 7232.
Currently Hyper for empty bodies with Content-Length header unset automatically sets the value 0 which is incorrect for HTTP 304 responses, the correct values are either to not provide Content-Length (recommended by specification)  or to provide Content-Length of a full response.

This gets set here: https://github.com/hyperium/hyper/blob/8d70baca611869c1997571e8513717396b13328b/src/proto/h1/role.rs#L479
A check could be added there for cases when there should be no header added.


CSSProperty should be named CssDeclaration

According to this section of the css specification the correct term for property/value pairs (including the important flag) is Declaration, not Property. AngleSharp currently names this class CssProperty. This is confusing, especially since CSSStyleDeclaration has this:
List<CSSProperty> _declarations;

Suggest changing the name of CSSProperty to CssDeclaration. Note the use of CamelCase - I prefer Css to CSS, in keeping with .net coding conventions. AngleSharp seems divided on the issue :)
Edit: Looks like this (incorrect) naming is used for all derived declaration types as well, so this might be a bigger change. However, that only makes it all the more needed. Hopefully Visual Studio can make the renaming easy.

I don't believe this has been fixed - the latest code still has CssProperty.
This is a pretty important name error - you say above that MDN uses the term properties, but if so, that's sloppy and does not match the specification: The combination of property name, colon, and property value within a ruleset is called a declaration everywhere I've seen.

I don't think this is an important naming error. Actually it is pretty accurate. A declaration is the combination of a name and a value. The instances of the property classes carry name and value pairs and are called declarations. However, the specific scheme for a certain name is the class, which is called property. I think this is as accurate as you could describe it. If you would name these classes declaration, then you would infer a specific value, however, the value is generic, while the naming is not.

However, the specific scheme for a certain name is the class, which is called property.

That is what is confusing. Why is the class called property? The class name should be Declaration, since it has no other purpose.
Sorry if this seems difficult, but this really makes the AngleSharp API and class hierarchy confusing.
As one more piece of evidence, see the specification which says:

To serialize a CSS declaration with property name property, value value and optionally an important flag set, follow these steps:

Therefore property names are called property. The combination of property name and value is called a declaration.

That is what I wrote above (please read it carefully - property is the name of a declaration, but it is also the class of declaration). A declaration is the actual instance that connects a value to a property.

[...] the specific scheme for a certain name is the class, which is called property

Naming will always be subject for discussion. But right now I don't see any reason to change. Especially since the naming aligns with other engines.

property is the name of a declaration

That could mean two things:
a) Declaration.Name is called property. If that's what you mean, please don't call it the name of a declaration, it is the property name.
b) The declaration itself is called property (that's what the ordinary use of "name" means.)
Language gets confusing in the meta-world :)

Especially since the naming aligns with other engines.

Could you give an example? All the parsers I've seen use the term Declaration consistently...
Obviously, If you've decided this is not going to change, then I won't say anymore. But I still haven't heard any justification for this naming which leads to code like:
List<CSSProperty> _declarations;

There is plenty of justification above. And besides: I don't need justification. But then again: An instance of a property class is a declaration, hence a list of property class instances are declarations. Its just a name: Get over it.

And besides: I don't need justification.
Its just a name: Get over it.

Try telling that to these folks.
I can't take offense because statements like this come from the ego.
Let me ask directly - do you want such feedback or not? I'm not interested in wasting my time or getting into pissing matches. Great code is my concern. If you are interested in sincere, sometimes difficult discussions, fine, otherwise I won't bother.

Great code yes, but this has nothing to do with the naming guidelines or anything else. Besides, the document you reference is a guideline. If somebody violates the guidelines, this can be intentional and beneficial depending on the scenario.
In don't see a pissing match here. I closed the issue and I justified this. There are users of the library which would be angry by name changes. This is one of the reasons why I want to stay with the current naming. It is not completely inaccurate and I had my reasons.
Just to come back to your statement:

But I still haven't heard any justification

This is not about ego or "being pissed", but why would I need to justify anything here. Any justification is optional. This is important. A discussion is highly welcome, but if I decide in favor of one or the other thing, then I probably have my reasons. Have these reasons been good or bad? That depends on the perspective. Some have been good, some could have been better. Would I have picked the Declaration naming initially, I wouldn't change it to Property now. But I made that decision and it was released prior to the discussion.
A name can be good or bad as well. But a name is really just a label. Nothing more. Therefore I would appreciate discussions about behavior and code and get over a name like that. In that case I evaluated the impact and I considered it not worth the change.
That you are not pleased with that decision is obvious. But I would focus on something else, or the future of the project, instead of moaning about the past.

There are a couple of things going on here.

It seemed to me you agreed with me initially:

The naming you propose fits, and I will rename it accordingly
If you hadn't agreed, we wouldn't be having this discussion.

In the course of researching #38 I saw the latest code where the name hadn't changed, so came back here and found the issue closed.

I asked about this, and rather than just saying you had changed your mind and decided to do nothing, you provided several reasons, which seemed invalid:

You said other engines use this term, but no examples were given, so I did some research to see what the actual consensus out there is, and they all seem to use the term Declaration.
The language you use, I must gently suggest, may make sense to you but tends to be unclear and imprecise. That's why I try to be as detailed and sharp - no generalizations or philosophy.
The idea that the name of a class is unrelated (and in this case means something totally different) to the names of instances of the class is just... weird.

Only in the last comment did you touch on something approaching justification, namely that you're not changing this for compatibility reasons. Fine. I'm simply restating my opinion that this is a wart, IMHO, in the api. We differ on one thing - to me names in code are extremely important, and make the difference between a clear, pleasurable codebase and an annoying, unpleasant one. This particular name is, to me, one of the more confusing ones I've come across. Otherwise I would not have bothered to bring it up.
You must realize for someone to take such a matter seriously is the kind of thing that should be encouraged. That's the best part of open source. Projects run on dogma tend to get forked and/or sidelined in the long run.
The fact that you initially agreed and then closed the issue without comment and now appear to be irritable is - disconcerting.
BTW - our english usage seems to be different, so I'll keep American slang out in the future. A pissing match is not about "being pissed." Also my link to the naming guidelines was ironic, and because it was not realized makes it doubly ironic :)

If we're done with this issue, why not discuss #38 - that's much more interesting :)

Sorry that I did not spot your irony. The discussion so far did not indicate that you are being ironic about such things. Hence an emoticon just like the one above would have been enough to provide a hint ;).
Anyway, yes I initially agreed and I am still not totally opposed to that name (I never said that it is wrong or not true, I just wrote that the current name is not completely wrong, even though it is less accurate -- but again: the impact would have not justified the refactoring step).
Since you are still interested in other engines I only want to mention WebKit (but Blink naturally, Gecko and from the internals also IE are similar). You can see an example at the header file of the CSS property http://trac.webkit.org/browser/trunk/Source/WebCore/css/CSSProperty.h.
Sorry but the name of the class and the instance are unrelated in general. If I make a class for only a single instance, then something may be fishy. The name of a particular instance might be close or related to the class, but in general there is no such requirement.
Also the "being pissed" was totally unrelated to the "pissing match". See above. It was a reference to the ego statement:

I can't take offense because statements like this come from the ego.

I don't know why you connected them, just because both contain "piss" does not mean that one was a reference to the other.
So let's close this issue for good and focus on the future instead of the past.


build: move database dependencies to group

I noticed that the pyproject.toml file had a 'database dependencies' comment, so this pull request moves it to its own group instead of it being under a the main group.

Not needed in this case, I prefer to not use groups because I prefer the simplicity, the comment is just for me. In the case of Monty, all of these dependencies are required for imports and whatnot, they aren't to be installed separately by any means.


faker override to much for nested object

What are the steps to reproduce this issue?
Have a nested schema
What happens?
faker generated code is using same override argument for nested objects
also overrideResponse should/could be Partial<UserDto> instead of any
export const getResponseMock =
  (overrideResponse: any = {}): UserDto => ({
    created_at: `${faker.date.past().toISOString().split('.')[0]}Z`,
    created_by: faker.word.sample(),
    email: faker.word.sample(),
    address: faker.helpers.arrayElement([
      { countryCode: faker.word.sample(), ...overrideResponse },
      undefined,
    ]),
    id: faker.word.sample(),
    ...overrideResponse,
  });

What were you expecting to happen?
I expect override to apply to root only and overrideResponse to be typed Partial<UserDto> instead of any
…
Any logs, error output, etc?
…
Any other comments?
…
What versions are you using?
Operating System: …
Package Version: …
Browser Version: …

@melloware can you please take a look at this PR
if PR is good then please merge it and create a new release as we're blocked from using latest orval version.
Orval version that is currently in our project has other bugs that are already fixed in latest orval


Fix Typo in import-container-app-with-oas.md

Typo fixed: creategg -> create

Learn Build status updates of commit 7470fe4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/api-management/import-container-app-with-oas.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@robibobi - thanks!


Fix variable naming p_e_ratio -> p_s_ratio

In util/valuation.py, firmValuationPS() has the variable p_s_ratio. It should be p_e_ratio.
(Related: https://github.com/oceanprotocol/tokenspice2/issues/2 and https://github.com/oceanprotocol/tokenspice2/pull/3)

Actually, it should be p_s_ratio. So we're ok.


Build paper sooner to cache tectonic downloads

It looks like cortex is currently caching the conda installation and the tectonic cache folder, but according to the docs, travis uploads the cache after script but before after_success.  This means the cache misses all the tex files that cortex pulls down, and will have to re-download them on every build (and this is dominating the building cost for longer papers for me).
It seems like we could get around this by just moving the paper build to the script section -- but I'm not sure if there's any reason not to do this?

Thanks for looking into this! There's no reason at all not to do this -- can you issue a PR?

Addressed in PR #7


Bandit 1.7.5 false positive for request_without_timeout (B113)

Describe the bug
Bandit is incorrectly marking calls to requests library without a timeout while the code it's actually not calling directly the requests library and the timeout is already set elsewhere.
Reproduction steps

Define this code:

from mylibrary import my_session

class Repro:

    def __init__(self):
        self.requests = my_session(timeout=5)

    def get(self, uri):
        return self.requests.get(uri)

Run bandit: bandit -l -i -r --skip B404,B603 somepath/

Get an error:

>> Issue: [B113:request_without_timeout] Requests call without timeout
   Severity: Medium   Confidence: Low
   CWE: CWE-400 (https://cwe.mitre.org/data/definitions/400.html)
   More Info: https://bandit.readthedocs.io/en/1.7.5/plugins/b113_request_without_timeout.html
   Location: repro.py:10:15
9	    def get(self, uri):
10	        return self.requests.get(uri)
11

Expected behavior
Bandit should not report any error because the session has a default timeout set via an HTTPAdapter in another library.
The code calls self.requests that could be any kind of object, does bandit do code inspection of the object to detect that is actually a requests session?
I don't think so as it triggered the issue also with my pseudo code that doesn't import the real library.
If it was indeed doing introspection, it should probably also check if there is a default timeout set in the session.
Bandit version
1.7.5 (Default)
Python version
3.9,3.10
Additional context
[note] The dropdown menu of the issues template here on Github has a Python 3.1 version and is missing 3.10, possibly a typo in the template.

Yes, if you look back at PR #743 that created this new check, there was concern over introducing such a low confidence plugin. The best course of action for now would be to skip
the test if you're getting too many false positives.

I've found a few more examples of false positives.

Getting merge requests with the GitLab client: merge_request = project.mergerequests.get(pull_request_id, lazy=True)
Setting up mocks with requests_mock: requests_mock.post("https://example.org", json={})

This repros...
import requests
requests.post(
  "https://httpbin.org/post", timeout=60 * 3
)

Should be fixed with #1011

@ericwb, this still hits on 3260f137873798b4b0c0c289373cc5e8fa2d93ed:
>> Issue: [B113:request_without_timeout] Requests call without timeout
   Severity: Medium   Confidence: Low
   CWE: CWE-400 (https://cwe.mitre.org/data/definitions/400.html)
   More Info: https://bandit.readthedocs.io/en/1.7.6/plugins/b113_request_without_timeout.html
   Location: sscce.py:2:0
1       import requests
2       requests.post(
3         "https://httpbin.org/post", timeout=60 * 3
4       )

Should I open a new issue?

@tucked Good catch. Seems timeout arg gets missed as the node is an ast.BinOp. The context._get_literal_value() doesn't handle BinOp and defaults to None.

I've been meaning to comment on this as well. If the above isn't possible to evaluate, I dont know if that means this is even harder (or easier) to catch. But this is how we use it when it triggers false positives (deployer configured values).
current_user_req = requests.get(
    f"{USER_LOOKUP_API}/{user_key}",
    cert=(cert_file.name, key_file.name),
    verify=ca_file.name,
    timeout=float(REQUEST_TIMEOUT),
)


Move entry refresh to Update()

Done in https://github.com/Micrologist/MicroEngineer/pull/11/commits/9c9ae3c65cccda056accb86aa8fcc261e9182223


Scope of expansion?

This issue is a bit of offtrack/out of scope issue and mingle of several thoughts which - software-wise pin on different aspects ig, but overall contribute to same thing - a nice and smooth UI/UX flow for 4 of the windows elements - taskbar, start, system tray, and action center.
This issue also consist of questions on suggestion for customising other elements than taskbar.
This can be considered as overexpansion of https://github.com/ChrisAnd1998/TaskbarX/issues/781
i know such issues are generally not welcome, but thought to discuss it since it's appeal felt huge to me.

Ohkay now, on with it:

#781 itself - ability to style the start menu - that will be so nice. I am pretty content with organisability side of Start Menu of Windows 10 specifically, but theming wise it lacks. So, this will cover that thing.
Can the styling part be extended to action center too? Can means

is it possible/doable in a clean way? and
can it be in TaskbarX's scope/roadmap?

~And title bar too? So, effectively like superseding "Accent Color" system wide?~ This is bit too much, and not my wish item either.

^

Any way, or recommended software with which i can modify system tray?

Specifically, i wanna remove/change the action center icon so that it doesnt occupy sooo much space. This will make it Win 11 like as well.
As a totally overkill bonus, making the systray widgets' color and start button color to auto change between black and white based on bg will be cool too. t'll help when the taskbar is set to transparent/similar (Re: in the hack mentioned for accomplishing https://github.com/ChrisAnd1998/TaskbarX/issues/772#issuecomment-913128677 )

^

Any way to modify action center?
It is implemented sooo poorly. it is thing of an utter disgrace in my opinion. Considering all the following points, i'd really like a way to tweak/replace windows action center. Similar to how i wanted to do to Taskbar before finding TaskbarX.

it doesnt show the time and date - which becomes crucial soo many times when giving online exams - which are often held in full screen that is taskbar and systray is inaccessible.
there's no way to go to dedicated setting of wifi/bluetooth etc. so, to change them, it requires going to system tray again. - although this aspect is on its way to getting fixed in windows 11 - but ugh, let's not touch "windows 11" wormcan.
It doesnt stick with taskbar location - always appears on right.
the all settings tile is just wasting space there.
it can be potentially made more aligned with system tray - both things have soo much potential to be unified. giving an awesome clean look AND better UX.
W.r.t. point 1, 4, 5, 2 take android ≥ 9 for example - showing time/battery status, and settings icon besides it. Tap and hold opens dedicated settings. smooth UX flow.

Current TBX (TaskbarX) Version:
Dont remember exactly, but most likely was <IP_ADDRESS>

To be able to focus on major/current bugs I had to close all issues. The issues section has gotten very messy to a point that I couldn't follow it anymore. Most issues are duplicates, very old or are already fixed/solved. Feel free to reopen this issue if you still have this issue on the latest version of TaskbarX to get my attention. All feature requests have been put in a list here: 💡| Feature requests #870
I hope you understand ❤

Update: 2022.05.29

That kind of thing is called an alternative "windows shell'
... which is essentially a replacement for explorer.exe - source
Other alternative shells: windows-alternative-shell
Found this whole trail via: cairo shell
... which is alternativeto: modernflyouts which was listed on ms-store-app-awards


Voice channel mention

This pull request...

[ ] Fixes a bug
[ ] Introduces a new feature
[x] Improves an existing feature
[ ] Boosts code quality or performance

Description
I recently noticed voice channels can be mentioned just like text channels. A small change to the code to implement this feature.

The top example is the current way the bot would mention a channel, the bottom is what I wish it would look like.
This my first pull request. I have not tested this change as I consider it to be too simple and don't expect it to fail.
Purpose
Aesthetics, ease of use. Clicking on the mentioned channel will automatically connect you to it.

Additionally, my IDE has found another 3 usages that you've missed:
https://github.com/jagrosh/MusicBot/blob/b83028fb97318825c7adaa12caa4a3b94513c652/src/main/java/com/jagrosh/jmusicbot/audio/AudioHandler.java#L205
https://github.com/jagrosh/MusicBot/blob/b83028fb97318825c7adaa12caa4a3b94513c652/src/main/java/com/jagrosh/jmusicbot/commands/general/SettingsCmd.java#L60
https://github.com/jagrosh/MusicBot/blob/b83028fb97318825c7adaa12caa4a3b94513c652/src/main/java/com/jagrosh/jmusicbot/utils/FormatUtil.java#L77
Update these accordingly.

Thanks for the elaborate feedback.
I agree with getAsMention() being more appropriate than "<#"+vc.getId()+">".
I also applied these changes to the 3 other usages that I had missed earlier.
After successfully compiling the project, I ran the commands and got some good results, a few of which you can see below:


[Sandbox] Apicurio Registry

Application contact emails
<EMAIL_ADDRESS>Project Summary
Apicurio Registry is a runtime server system that stores a specific set of artifacts (primarily schemas and API designs) as files and manages evolution of artifact versions. Apicurio Registry enables you to add, update, and remove the artifacts from the store using a REST API or a Web UI.
Project Description
API Registry
The key use case for the Apicurio community is as an API registry, which is a system that enables you to register your designs (OpenAPI, AsyncAPI, GraphQL, Apache Avro, Google Protocol Buffers, JSON Schema, Kafka Connect schema, WSDL and XML Schema (XSD)) so that potential API consumers can do the following:

Browse, update, or search the list of APIs available
Configure, and execute artifact rules
View details about a single available API
Learn how to use an API using auto-generated documentation
Generate client SDKs for an API

Schema Registry
In the messaging and event streaming world, data published to topics and queues often must be serialized or validated using a schema (OpenAPI, AsyncAPI, GraphQL, Apache Avro, Google Protocol Buffers, JSON Schema, Kafka Connect schema, WSDL and XML Schema (XSD)). Schemas can be packaged in each application, but it is often a better architectural pattern to register schemas in an external system and then reference them from each application. A schema registry provides the following benefits:

Schemas do not have to be bundled together with consumer or producer applications
Potential to upgrade producers without upgrading consumers thanks to the configuration and execution of both validity and compatibility rules for schemas
Central location to track all schemas used in a specific environment
Document the data format required for each use case
Centralized control of data format and schema evolution
Enabled the automation of upgrade procedures such as canary/blue-green

Org repo URL (provide if all repos under the org are in scope of the application)
N/A
Project repo URL in scope of application
https://github.com/Apicurio/apicurio-registry
Additional repos in scope of the application
No response
Website URL
https://www.apicur.io/registry
Roadmap
https://github.com/orgs/Apicurio/projects/6
Roadmap context
Over time, all applications face organic growth. We’re no different in that sense, and we’re planning a new major release for the project. For example, the project supports different storage options, like storing the application data in a Kafka topic or storing the information in a relational database. Due to some technical constraints, in the past, we had to release a new container image per each storage option (even for separate database drivers) but these constraints have been removed and, with the new major version, we will be releasing just one container image for all the storage options.
In addition to addressing some technical limitations we also started adding some new major features, like a GitOps implementation that can be used to store the application data.
We have also introduced a new client library for the application that relies on Kiota, an exciting technology developed by Microsoft as an open source tool that allows us to generate client SDKs from OpenAPI definitions.
Contributing Guide
https://github.com/Apicurio/apicurio-registry/blob/main/CONTRIBUTING.md
Code of Conduct (CoC)
https://github.com/Apicurio/apicurio-registry/blob/main/CODE_OF_CONDUCT.md
Adopters
N/A
Contributing or Sponsoring Org
https://www.redhat.com
Maintainers file
https://github.com/Apicurio/apicurio-registry/blob/main/pom.xml#L38-L70
IP Policy

[X] If the project is accepted, I agree the project will follow the CNCF IP Policy

Trademark and accounts

[X] If the project is accepted, I agree to donate all project trademarks and accounts to the CNCF

Why CNCF?
Community and Ecosystem Support.
Neutral Governance.
Increased Visibility.
Interoperability and Standards.
Marketing and Recognition.
Graduation Path.
Legal and Intellectual Property Support.
Benefit to the Landscape
This question can be resolved by mentioning the multiple reasons why a project like Apicurio Registry is a good “Cloud Native” fit, like the ones described below. Another big benefit to the landscape is the close integration with an existing project like Strimzi.
Cloud Native 'Fit'
A schema registry like Apicurio Registry is considered a good fit for cloud-native architectures for several reasons:

Decentralized Microservices:

In cloud-native environments, applications are often built as microservices. Each microservice may use different data formats and schemas. A schema registry helps in maintaining a centralized repository for schemas, making it easier for microservices to understand and communicate with each other.

Dynamic Scaling:

Cloud-native applications often need to scale dynamically based on demand. As the number of services or instances increases or decreases, having a centralized schema registry ensures that all services can quickly adapt to changes in the schema without requiring extensive coordination.

Compatibility and Versioning:

Microservices are developed and deployed independently, and they may evolve at different rates. A schema registry enables versioning and backward/forward compatibility checks, ensuring that newer versions of services can communicate with older versions without causing data mismatches or errors.

Contract Testing:

Cloud-native applications benefit from contract testing, where each service's compatibility is verified against the contracts defined in the schema registry. This ensures that changes to a service don't break the contracts established with other services.

Schema Evolution:

Cloud-native systems often require the ability to evolve schemas over time without disrupting existing services. A schema registry facilitates controlled schema evolution, allowing for the introduction of new fields or changes while ensuring backward compatibility.

Interoperability:

In multi-cloud or hybrid cloud environments, where different services may be deployed on different platforms, a schema registry promotes interoperability by providing a standardized way for services to share and understand data formats.

Real-time Data Governance:

A schema registry provides a central point for managing and governing data schemas. This is crucial for maintaining data quality, ensuring consistency across services, and enforcing data governance policies in real-time.

Tooling Integration:

Cloud-native ecosystems often come with a variety of tools for monitoring, logging, and debugging. A schema registry can integrate with these tools, providing insights into data changes and ensuring that the data flowing through the system adheres to predefined schemas.

Security and Access Control:

Schema registries typically offer features for managing access control and security. In a cloud-native environment, where security is a top concern, having centralized control over who can access and modify schemas is crucial for maintaining the integrity of the data.

In summary, a schema registry like Apicurio Registry is well-suited for cloud-native architectures because it addresses the challenges associated with the dynamic, decentralized, and scalable nature of microservices-based applications, providing a robust foundation for data interoperability and evolution.
Cloud Native 'Integration'
Apicurio Registry has a “native” clear integration with Strimzi in various ways.

Apicurio Registry can be configured on the Strimzi Kafka cluster as the Schema Registry. A common integration would look as follows:

Deploy Apicurio Registry:

Deploy Apicurio Registry on your Kubernetes cluster.

Configure Strimzi:

Configure your Strimzi Kafka cluster to use Apicurio Registry as the schema registry for your Kafka topics. This involves updating your Kafka custom resource (Kafka CR) or KafkaConnect custom resource, depending on your specific use case.

Update Producer and Consumer Configurations:

Update your Kafka producer and consumer configurations to point to Apicurio Registry for schema management. This includes specifying the Apicurio Registry URL and any other required configurations.

Schema Registration:

When producing messages to Kafka, ensure that the Avro or other schema is registered with Apicurio Registry first. This might involve making API calls to the Apicurio Registry or using client libraries that handle schema registration.

Using the Kafka Cluster managed and created by Strimzi as the persistent storage for Apicurio Registry. Essentially, with this configuration, Apicurio Registry has an internal database that is used for reads and writes that are made to a Kafka topic and synchronized back into the internal database.
In a microservices system, Apicurio Registry can be deployed in the target environments maintaining the source of truth of the API contracts produced and consumed by the services. Making it easy and enabling the automation of seamless upgrades.

Cloud Native Overlap
This project does not have an overlap with any other CNCF project.
Similar projects
https://github.com/confluentinc/schema-registry
Landscape
https://landscape.cncf.io/?selected=apicurio-registry
Business Product or Service to Project separation
Even though there is a Red Hat product based on Apicurio Registry, we acknowledge the importance of maintaining independence and transparency. Our approach involves emphasizing the clear distinction between the upstream project and downstream products or services.
The project itself, referred to as the upstream, is maintained as an open-source endeavor with a distinct identity. We commit to keeping it separate from any specific Red Hat product or service, ensuring its autonomy.
Any downstream products or services developed by Red Hat based on the project will have their own organizational structure and development processes. We recognize the significance of avoiding a direct overlap between the project and any commercial offerings.
While Red Hat is currently a significant contributor and maintainer, we recognize the importance of ensuring the project's independence.
We actively encourage and welcome contributions from external contributors. We understand the need for diverse perspectives and are committed to fostering an open environment where regular contributors can become maintainers, ensuring a broader range of opinions and contributions.
Project presentations
No
Project champions
No response
Additional information
No response

Couple of questions:

Does Apcurio support the CloudEvents standard for messages?
Are there ways to use Apcurio with the Kubernetes API?

Couple of questions:

Does Apcurio support the CloudEvents standard for messages?

Yes, we currently support firing events the the CloudEvents format for the different operations happening in Apicurio Registry to both and HTTP sink or to Kafka . Aditionally, we did some PoCs in the past around the standard, like this one.

Are there ways to use Apcurio with the Kubernetes API?

No, we do have a Kubernetes operator to manage Apicurio Registry, but the artifacts managed by Registry cannot be managed through the Kubernetes API.

@carlesarnal could you and the Apicurio Registry team come present to TAG App Delivery at our general meeting on February 7, 2024?

@carlesarnal could you and the Apicurio Registry team come present to TAG App Delivery at our general meeting on December 20, 2023?

Hi @angellk, yes! I have no problem presenting next week.
Thanks

Are there ways to use Apcurio with the Kubernetes API?

No, we do have a Kubernetes operator to manage Apicurio Registry, but the artifacts managed by Registry cannot be managed through the Kubernetes API.

I was asking about the other way around: can I use Apicurio to manage the Kubernetes API?

Hello @carlesarnal! I am reaching out on behalf of TAG Runtime. It would be great to have you present Apicurio at our bi-weekly meeting to understand the project roadmap.
The next occurrence of the meeting is on 4th Jan 2024. Let me know if that works for you else we can find some other time!

Hello @rajaskakodkar,
Based on some internal conversations we've been having, I think we should postpone the Apicurio presentation until we can get clarification on some key questions.
I'll write here again once we're ready to present.
Thanks!

Hello all,
For now, we will defer contributing to the project, since we have some branding issues that have to be resolved before contributing it. That said, we might resume the activity in the future whenever we have a more mature version of some other parts of our projects. In any case, for now, we have engaged with the Discovery API working group to get engaged with  https://github.com/xregistry initiative, which might create a more organic opportunity for the contribution.
Thanks everyone for your time. For now, I'll close this issue.

Are there ways to use Apcurio with the Kubernetes API?

No, we do have a Kubernetes operator to manage Apicurio Registry, but the artifacts managed by Registry cannot be managed through the Kubernetes API.

I was asking about the other way around: can I use Apicurio to manage the Kubernetes API?

We have a Kubernetes Operator to manage the application deployment, but nothing beyond that.


http request error during downloading NYUv2 dataset

Hi, thank you so much for sharing the code!
When I tried to download data from
http://www.cs.berkeley.edu/~sgupta/eccv14/eccv14-data.tgz ,
I cannot connect to the server.
The same thing happened to the pretrained models.
How can I solve it?
Thank you !

Sorry for the delay, I ave made the data available here:
https://www.dropbox.com/sh/zyewldvlivyhwwj/AAD0llrV-R-DfAmfbTzX6I2ua?dl=0
Let me know if you need anything else.
On Wed, Jan 30, 2019 at 8:22 AM Whitebear<EMAIL_ADDRESS>wrote:

Hi, thank you so much for sharing the code!
When I tried to download data from
http://www.cs.berkeley.edu/~sgupta/eccv14/eccv14-data.tgz ,
I cannot connect to the server.
The same thing happened to the pretrained models.
How can I solve it?
Thank you !
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/s-gupta/rcnn-depth/issues/46, or mute the thread
https://github.com/notifications/unsubscribe-auth/ACLxrdKAKyBcYMr8cXA3Sd5AXnV_-NzDks5vIZyggaJpZM4aaMRV
.

Hi, thank you for the reply!
I could download the data from the URL!
Thank you so much, and closing the issue.


[BUG] - Operator gets stuck deploying a slinkee cluster when nodes have taints (e.g,. control plane nodes)

Describe the bug
The slinkee operator gets stuck deploying a slinkee cluster when there are nodes with taints that will not have a slurmabler deployed on them. The reason is that the operator waits until each node has been labelled, however the slurmabler will not be scheduled on nodes with a taint.
In many Kubernetes clusters the control plane will be tainted so regular workloads cannot be scheduled on them, so on many Kubernetes clusters this will be an issue.
To Reproduce
Steps to reproduce the behavior using a Kind cluster:

Create a kind cluster config for one control plane node and one worker node in /tmp/one-node-kind.yml:

kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
nodes:
- role: control-plane
- role: worker

Create a kind cluster with the config:

kind create cluster --config /tmp/one-node-kind.yml

Deploy slinkee via helm

helm install -f helm/slinkee/values.yaml slinkee ./helm/slinkee/

Deploy the simple slinkee cluster

kubectl apply -f payloads/simple.yaml

Wait for the slinkee-operator to create the slurm-ablers and observe how the worker node will get labels and the control plane node will not:

kubectl get nodes --show-labels

In the logs of the slinkee-operator you can see it is waiting for nodes to be labelled:

kubectl logs slinkee-operator-767fb59df6-7w66j --tail 10
2024-06-21T11:34:52.987Z	INFO	slurm/create_slurmabler.go:102	github.com/vultr/slinkee/pkg/slurm.buildSlurmablerDaemonSet	node lacking labels...	{"host": "<IP_ADDRESS>", "hostname": "slinkee-operator-767fb59df6-7w66j", "pid": 1}
2024-06-21T11:34:53.993Z	INFO	slurm/create_slurmabler.go:102	github.com/vultr/slinkee/pkg/slurm.buildSlurmablerDaemonSet	node lacking labels...	{"host": "<IP_ADDRESS>", "hostname": "slinkee-operator-767fb59df6-7w66j", "pid": 1}
2024-06-21T11:34:54.999Z	INFO	slurm/create_slurmabler.go:102	github.com/vultr/slinkee/pkg/slurm.buildSlurmablerDaemonSet	node lacking labels...	{"host": "<IP_ADDRESS>", "hostname": "slinkee-operator-767fb59df6-7w66j", "pid": 1}
2024-06-21T11:34:56.006Z	INFO	slurm/create_slurmabler.go:102	github.com/vultr/slinkee/pkg/slurm.buildSlurmablerDaemonSet	node lacking labels...	{"host": "<IP_ADDRESS>", "hostname": "slinkee-operator-767fb59df6-7w66j", "pid": 1}
2024-06-21T11:34:57.012Z	INFO	slurm/create_slurmabler.go:102	github.com/vultr/slinkee/pkg/slurm.buildSlurmablerDaemonSet	node lacking labels...	{"host": "<IP_ADDRESS>", "hostname": "slinkee-operator-767fb59df6-7w66j", "pid": 1}
2024-06-21T11:34:58.020Z	INFO	slurm/create_slurmabler.go:102	github.com/vultr/slinkee/pkg/slurm.buildSlurmablerDaemonSet	node lacking labels...	{"host": "<IP_ADDRESS>", "hostname": "slinkee-operator-767fb59df6-7w66j", "pid": 1}
2024-06-21T11:34:59.027Z	INFO	slurm/create_slurmabler.go:102	github.com/vultr/slinkee/pkg/slurm.buildSlurmablerDaemonSet	node lacking labels...	{"host": "<IP_ADDRESS>", "hostname": "slinkee-operator-767fb59df6-7w66j", "pid": 1}
2024-06-21T11:35:00.033Z	INFO	slurm/create_slurmabler.go:102	github.com/vultr/slinkee/pkg/slurm.buildSlurmablerDaemonSet	node lacking labels...	{"host": "<IP_ADDRESS>", "hostname": "slinkee-operator-767fb59df6-7w66j", "pid": 1}
2024-06-21T11:35:01.039Z	INFO	slurm/create_slurmabler.go:102	github.com/vultr/slinkee/pkg/slurm.buildSlurmablerDaemonSet	node lacking labels...	{"host": "<IP_ADDRESS>", "hostname": "slinkee-operator-767fb59df6-7w66j", "pid": 1}
2024-06-21T11:35:02.046Z	INFO	slurm/create_slurmabler.go:102	github.com/vultr/slinkee/pkg/slurm.buildSlurmablerDaemonSet	node lacking labels...	{"host": "<IP_ADDRESS>", "hostname": "slinkee-operator-767fb59df6-7w66j", "pid": 1}

Remove the taint from the control plane node:

kubectl taint node kind-control-plane node-role.kubernetes.io/control-plane:NoSchedule-

Now watch the slinkee simple cluster being deployed

kubectl get pods -n default -w

Expected behavior
The slinkee operator should ignore the nodes that do not have a slurmabler scheduled on them because of taints.
Additional context
Commit of repo used for testing: 55388067c0a7469742bec558c9c8dc52fcbc9570
Kind version: kind v0.22.0 go1.21.7 darwin/arm64

@t1mk1k can you try newest build and let me know if that resolves?

@vultj I've changed the image tags in the Helm chart to v0.0.2 and now a cluster is deployed successfully.
However, one of the deployments is still trying to schedule a pod on a control plane node:
✗ kubectl get pods -owide
NAME                                       READY   STATUS    RESTARTS   AGE    IP           NODE          NOMINATED NODE   READINESS GATES
slik-operator-6bf7848d88-wqxqh             1/1     Running   0          102m   <IP_ADDRESS>   kind-worker   <none>           <none>
test-kind-control-plane-78c96648b7-jms5g   0/2     Pending   0          99m    <none>       <none>        <none>           <none>
test-kind-worker-cb684697f-9bfhr           2/2     Running   0          99m    <IP_ADDRESS>   kind-worker   <none>           <none>
test-slurm-toolbox-64bf746f8c-7s2pl        2/2     Running   0          99m    <IP_ADDRESS>   kind-worker   <none>           <none>
test-slurmabler-kz6xb                      1/1     Running   0          99m    <IP_ADDRESS>   kind-worker   <none>           <none>
test-slurmctld-dbfcd569f-r7cfd             2/2     Running   0          99m    <IP_ADDRESS>   kind-worker   <none>           <none>

✗ kubectl get deployments.apps test-kind-control-plane -owide
NAME                      READY   UP-TO-DATE   AVAILABLE   AGE    CONTAINERS   IMAGES                                SELECTOR
test-kind-control-plane   0/1     1            0           102m   slurmd       ewr.vultrcr.com/slurm/slurmd:v0.0.2   app=test-slurmd,host=kind-control-plane

It does not appear to affect the SLURM cluster, but probably good to filter out nodes with taints at the deployment stage too.

Likely, but I welcome any PRs that add such functionality.


Simplify the logs retrival

Here's the simplification I'd introduce at this point to have the PR merged. Please add tests to the new parts of the code.

Ok, so you we are bailing on --all-containers?

--all-containers will should be added as a separate PR on top of this.


Tailwind changes dont work

i have install it 1:1 up to yor YT video, but the tailwind dont show the changes like background color changes ? anybod can help ?

@TobiasSol happening here too, did you fix it?


Add functionality to call out deprecated attributes

aria-grabbed and aria-dropeffect are deprecated attributes for all elements/roles.
ARIA 1.2 also deprecates aria-disabled, aria-errormessage, aria-haspopup, and aria-invalid from being global attributes.  They are instead allowed on specific roles where their usage still makes sense.
aria-disabled, aria-errormessage, aria-haspopup, and aria-invalid supported on
application, columnheader, combobox, gridcell, rowheader, searchbox, slider, spinbutton, textbox
aria-disabled, aria-haspopup supported on
button, link, menuitem, menuitemcheckbox, menuitemradio, tab, treeitem
aria-disabled, aria-errormessage, and aria-invalid supported on
checkbox, listbox, radiogroup, switch, tree, treegrid
aria-disabled supported on
grid, group, menu, menubar, option, radio, row, scrollbar, separator (if focusable), tablist, toolbar

Hi @scottaohara, thank you for this list. I've added it to my list for the next update.

@gezlemon another thing which i almost forgot to mention, specific to aria-invalid.
See https://github.com/w3c/html-aria/issues/366, but the quick version is that aria-invalid=true | false are valid on all the roles i mentioned in my op.  While deprecated, aria-invalid=spelling | grammar | false, are still allowed on all other elements until a new attribute is created to expose these states.

Hi @scottaohara I've updated the script to deprecate the attributes you've listed, and included an exception for aria-invalid when "spelling", "grammar", and "false" are used.

Thanks @gezlemon.  Though it seems that not all cases are covered?
for example, the test case i had (https://w3c.github.io/html-aria/tests/deprecated-attrs.html) used aria-grabbed and aria-dropeffect on divs.  but the deprecation notice isn't called out.   When i added a role=group to the divs, then the message showed up.

Thanks, @scottaohara  I've updated the script to check for deprecated attributes for elements without an ARIA role.


[ger] Adds German Phone list, filtered TSV file

[x] Updated Unreleased in CHANGELOG.md to reflect the changes in code or data.

Got it!

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kylebgorman/wikipron/pull/309#issuecomment-756957482,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKKPU5CBEVR5RJUJA7BKRODSY5N4VANCNFSM4V23CZ6A
.

Got it!

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kylebgorman/wikipron/pull/309#issuecomment-756957482,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKKPU5CBEVR5RJUJA7BKRODSY5N4VANCNFSM4V23CZ6A
.

Which test did you run?
On Fri, Jan 8, 2021, 2:39 PM Kyle Gorman<EMAIL_ADDRESS>wrote:

@kylebgorman approved this pull request.
LGTM but there's an issue with the tests...checking now.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kylebgorman/wikipron/pull/309#pullrequestreview-564530126,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKKPU5DAYRULA763HU3ZHOLSY5NNLANCNFSM4V23CZ6A
.

Which test did you run?
On Fri, Jan 8, 2021, 2:39 PM Kyle Gorman<EMAIL_ADDRESS>wrote:

@kylebgorman approved this pull request.
LGTM but there's an issue with the tests...checking now.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kylebgorman/wikipron/pull/309#pullrequestreview-564530126,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKKPU5DAYRULA763HU3ZHOLSY5NNLANCNFSM4V23CZ6A
.

tests/test_data/test_summary.py. It runs automatically after every PR (or commit to a previously submitted PR):

I think you should be able to see the result if you look above where it currently says "some checks were not successful"...

tests/test_data/test_summary.py. It runs automatically after every PR (or commit to a previously submitted PR):

I think you should be able to see the result if you look above where it currently says "some checks were not successful"...

Yes :) thank you!
On Fri, Jan 8, 2021, 2:52 PM Kyle Gorman<EMAIL_ADDRESS>wrote:

tests/test_data/test_summary.py. It runs automatically after every PR (or
commit to a previously submitted PR):
[image: Screenshot 2021-01-08 at 2 51 19 PM]
https://user-images.githubusercontent.com/159289/104057988-04713c80-51c1-11eb-8d43-2b9c1860b51c.png
I think you should be able to see the result if you look above where it
currently says "some checks were not successful"...
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kylebgorman/wikipron/pull/309#issuecomment-756961325,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKKPU5AI4LSV7STHNI4FS53SY5O7FANCNFSM4V23CZ6A
.

Yes :) thank you!
On Fri, Jan 8, 2021, 2:52 PM Kyle Gorman<EMAIL_ADDRESS>wrote:

tests/test_data/test_summary.py. It runs automatically after every PR (or
commit to a previously submitted PR):
[image: Screenshot 2021-01-08 at 2 51 19 PM]
https://user-images.githubusercontent.com/159289/104057988-04713c80-51c1-11eb-8d43-2b9c1860b51c.png
I think you should be able to see the result if you look above where it
currently says "some checks were not successful"...
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kylebgorman/wikipron/pull/309#issuecomment-756961325,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKKPU5AI4LSV7STHNI4FS53SY5O7FANCNFSM4V23CZ6A
.


User account redesign

No new functionality, just a redesign (source):

Notifications: CartoDB/cartodb#4592
Differences between single user and org owner user: none.
Differences between single user and non-owner, org user:

Profile:

No Disqus shortname.

Account:

No billing plan.
Can't delete the account.

No Billing.
When a contact email is displayed, it should display admin_email  (see CartoDB/cartodb#4403).

cc @saleiva

Question here: should I change current texts for the ones in the redesign?
For example, in /profile "Edit your profile settings" -> "Your profile information"
cc/ @brittanymicek @csobier

Texts at the design seem fine, use design ones. @brittanymicek @csobier will suggest any change to them if there's something wrong.

Copy that :+1:

Notes on text:
For profile tab:
Under Choose Image
Recommended images should be 128x128 of size change to “128x128 pixels”*
Other users can search and contact you by your public name
For account tab:
Why is there copy “Delete your account”? Is that supposed to be a button or a hyperlink?
underneath it says: “You sure? Delete my account and all my data”
Suggestion:
make “Delete your account” a button or hyperlink
and have “You sure? Yes, delete my account and all my data.” as a pop-up window when they click “Delete your account”

@saleiva that design has a problem that went unnoticed to me the account type section:

Box doesn't know about plans or prices. So we're doing an small modification:
1.- Don't display the price.
2.- The text of the button comes out from the account_type column at users.
3.- It links Central.
Please also note that should be only displayed at SaaS, not open source or onpremise.
cc @MariaCheca , this should clear all doubts, isn't it?

Ok, so the only thing that we will miss is the price?
On Aug 14, 2015 5:06 PM, "Juan Ignacio Sánchez Lara" <
<EMAIL_ADDRESS>wrote:

@saleiva https://github.com/saleiva that design has a problem that went
unnoticed to me the account type section:
[image: screen shot 2015-08-14 at 16 49 02]
https://cloud.githubusercontent.com/assets/932968/9276784/49c4d448-42a6-11e5-8ab6-530afe024fef.png
Box doesn't know about plans or prices. So we're doing an small
modification:
1.- Don't display the price.
2.- The text of the button comes out from the account_type column at users
.
3.- It links Central.
Please also note that should be only displayed at SaaS, not open source or
onpremise.
cc @MariaCheca https://github.com/MariaCheca , this should clear all
doubts, isn't it?
—
Reply to this email directly or view it on GitHub
https://github.com/CartoDB/cartodb/issues/4878#issuecomment-131140254.

Yep, and account type is not exactly the same than price plan name, although I can't find a case where there's a mismatch on that right now. Not a big deal, but I wanted you to know.

Ok
On Aug 14, 2015 5:12 PM, "Juan Ignacio Sánchez Lara" <
<EMAIL_ADDRESS>wrote:

Yep, and account type is not exactly the same than price plan name,
although I can't find a case where there's a mismatch on that right now.
Not a big deal, but I wanted you to know.
—
Reply to this email directly or view it on GitHub
https://github.com/CartoDB/cartodb/issues/4878#issuecomment-131142483.

Currently there's no reference in the redesign mockups for the organization users API keys. If it's ok I'll preserve these parts as they are in the current design, waiting for an update:

At org owner panel:

At organization user details (owner view):

cc/ @saleiva

cc'ing @josecruz so he is aware.

Closing since it is done, for pending behaviour or functionality, new tickets please.


Fix npm version in 14.16 in readme

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Allow ability to configure TLS

I notice from here:
https://github.com/allangood/rtlamr2mqtt/blob/1a2c69ffb0d068673a006c1b2bd14b005dca2a4e/rtlamr2mqtt.py#L73-L76
...that TLS is always assumed to be excluded. I host my MQTT broker behind TLS and would love to be able to utilize that here.

Thank you for your feedback. This really should be addressed! :)
I will be working on it and release it in the next version.

Added on version 1.7.0 by PR #104

FWIW I'm not sure how necessary this is if you're using the automatic MQTT configuration. Presumably you get a local docker IP address to talk to, so the network traffic won't ever be leaving your computer

@JeffreyFalgout That only applies to a very specific scenario. In my case, my rtlamr2mqtt and my MQTT broker are on different hosts.

I can confirm that 1.7.0 implements this and that everything works. Thank you!


Expose self.sess for GAIL

Unlike all of the other models, the GAIL class does not expose its attribute self.sess. Instead, one has to reach into the TRPO attribute and reference self.trpo.sess. This leads to displeasing code like:
if isinstance(model, GAIL):
    model.trpo.sess.close()
else:
    model.sess.close()

I propose we expose the attribute with the code below, similar to this line
# In the GAIL constructor
self.sess = self.trpo.sess

Hi,
This is a good remark, but I think we should go further and use magic methods (__get_attr__ and __set_attr__) to make GAIL just a wrapper around trpo.
For instance, that would allow to avoid overwritting get_env() and set_env().
Don't hesitate to ask if what I wrote is a little too obscure ;)

I agree. This suggestion is both more elegant and more comprehensive.


cmake fail at ODBC

Can't find include files and lib files.
replace cmake/modules/FindODBC.cmake with version 3.2.2 , can fix this .

Sorry there is absolutely not enough information here to allow doing anything about it, in particular I have no idea what and why does it fail to find for you.


openssl version

I can't seem to be able to compile it.
What version of OpenSSL did you use? Any package other than libssl-dev?
Thank you

The default openssl that comes with Arch Linux.
Post errors.

The symbol SSL_COMP_free_compression_methods is undefined, it was added on 1.0.2 and I have 1.0.1 apparently. Oh well.

Time to update.

Using Debian.

Heh


Deletion of shippingMethod is possible now.

@emmenko please review. Is this enough?

@mmoelli also here https://github.com/sphereio/sphere-node-sdk/blob/master/src/spec/client/client.spec.coffee#L97


fix insert default values statements not parsing

Problem
The insert statement below does not parse, but it should based on it being valid syntax
INSERT INTO mytable DEFAULT VALUES

Solution

Add additonal unit tests scenarios
Add isOnlyDefaultValues, setOnlyDefaultValues and withOnlyDefaultValues methods to the Insert object
Update InsertDeParser and JSqlParserCC.jjt

Please note
To get the change to JSqlParserCC.jjt to work I needed to add DEFAULT as a reserved keyword, meaning it cannot be used as an alias. This seems fine based on DEFAULT being a reserved keyword in Postgres documentation

Clean and nice work! Thank you for your contribution and effort!


Added individual output for C2F

Data tables and feeds for individual fire perimeters.

Looks good to me! I forget, did you get a chance to test the DB update with something like the Banff example library?


Close resources in FeignLogbookLogger

Closes resources in FeignLogbookLogger to avoid http clients connections leak.
Description
FeignLogbookLogger reads response data from original InputStream into byte array and creates copy of original Response based on read byte array.
But it doesn't close original InputStream and doesn't close original Response.body(close implementation for apache http 5 client).
Motivation and Context
For some feign client implementations it leads to connections leak. I experienced leak for feign + apache 5 http client with pool of connections.
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.

@Nazukin-Dmitry, The changes make sense to me. Could you please make sure all the commits for the PR are signed? I can't merge the PR.

@kasmarian thanks for review, I force-pushed signed commit (I hope I did it correctly)

@msdousti could you re-approve?

@msdousti could you have a look and re-approve?


fix(ingest/lookml): add view load failures to cache

This ensures that we don't try to read the same file multiple times when we already failed the first time.
Checklist

[ ] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[ ] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

Summary by CodeRabbit

Improvements

Enhanced error handling and reporting for better debug information during Looker view file loading.
Improved cache management to optimize the performance of loading and parsing Looker view files.

@hsheth2 there are mypy failures


chore(deps): upgrade runtime dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-runtime-dependencies-1.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 2030

Questions ?
Please refer to the Backport tool documentation


#957 Ghost image offset incorrect on Chrome browser when dragging fro…

…m the palette
Fixes: #957
Developer's Certificate of Origin 1.1
   By making a contribution to this project, I certify that:

   (a) The contribution was created in whole or in part by me and I
       have the right to submit it under the Apache License 2.0; or

   (b) The contribution is based upon previous work that, to the best
       of my knowledge, is covered under an appropriate open source
       license and I have the right under that license to submit that
       work with modifications, whether created in whole or in part
       by me, under the same open source license (unless I am
       permitted to submit under a different license), as indicated
       in the file; or

   (c) The contribution was provided directly to me by some other
       person who certified (a), (b) or (c) and I have not modified
       it.

   (d) I understand and agree that this project and the contribution
       are public and that a record of the contribution (including all
       personal information I submit with it, including my sign-off) is
       maintained indefinitely and may be redistributed consistent with
       this project or the open source license(s) involved.

It looks like Chrome works but Firefox I see it offset.


Using '.' in url parameters

I am not sure if this is actually an issue. But at least we should discuss it.
Using e.G. ch.disable as a key suggests that in e.G. JSON there is an object ch with key disable. Maybe we should think about converting the .to _?

This should be properly handled from us (I hope :)). The intention behind this is exactly this: to create an object ch with several keys. E.g. in the config we have routing.xy=1 and routing.ab=2, then in a later json config this becomes routing: {xy=1, ab=2}

Ok, then it's fine. I just got an js exception because of that and thought it might be worthwhile to discuss it.

Does this exception occur also in our web module and what exactly went wrong?

No, otherwise I'd reported it. I use a library that expects that json objects (like api params) don't contain  characters like ..


Breakpoint variants are not sorted properly

Config:
unocss.config.ts
export default defineConfig({
...
  theme: {
    breakpoints: {
      'xs': '320px',
      'sm': '640px',
      'md': '768px',
      'lg': '1024px',
      'xl': '1280px',
      '2xl': '1536px',
      'xxl': '1536px',
    },
...
})

HTML code:
<template>
  <div class="grid xs:grid-cols-2 sm:grid-cols-3 md:grid-cols-4 lg:grid-cols-5">
    <Item v-for="(item, index) in products" :key="index" :item="item" />
  </div>
</template>

Result:

Playground
xs breakpoint has the highest priority with the lowest value
UPD: If i will add custom breakpoints with same values, then the order becomes correct
Playground

I'm also observing this issue.  Another quirk is that using at-xs creates rule matching xs > w > xxl instead of expected xs > w > sm, where w is viewport width

Most likely this is due to how js object are merged. The default values are here:
https://github.com/unocss/unocss/blob/9de788ae4b980a2ff72466f05626a6f154b6a59a/packages/preset-mini/src/theme/misc.ts#L2-L8
Adding custom breakpoints will append the keys at the end of the theme config.

UPD: If i will add custom breakpoints with same values, then the order becomes correct

Use this workaround for now.

I guess we could sort it instead of relying on the object key order?

I'm afraid sorting may cause other problem with numbers with different units.
(Tailwind's for reference)

I'm afraid sorting may cause other problem with numbers with different units.
(Tailwind's for reference)

Maybe we can use generator.userConfig to acces the breakpoints keys to sort them on the variant.

ok, using the breakpoints from the userConfig if present instead merged from theme works, PR in a few minutes.
On playground just adding the breakpoints works:

on node also works:


Change quad_form shape

Describe the bug
cp.quad_form currently has shape (1,1), but should be scalar, i.e., ().
#2067 Fixes a special case for subsequent matrix multiplication, but the proper fix is to correct the shape with the next major release.
To Reproduce
import cvxpy as cp
import numpy as np

x = cp.Variable(2)
P = np.eye(2)
print(cp.quad_form(x, P).shape)
>>> (1,1)

y = np.arange(2)
print((y.T @ P @ y).shape)
>>> ()

Note: PR should also remove the comment about the wrong shape of quad_form added in #2067.

Fixed


Added function to reset IStateGroup

Everytime a new model is parsed, the IStateGroup is not being cleared and thus is growing.
As far as I remember, the simulation is working, but the Network::initStates execution duration keep increasing.
So in my code, everytime I reload the model, I'm calling this function to clear the IStateGroup.
Maybe the call should be added to the end of the parsing code, or at the beginning of the checkAndComplete function.

I added the call at the beginning of the config parse function.


Visual Studio Developer Command Prompt and Developer PowerShell not working

This issue has been moved from a ticket on Developer Community.

[severity:It bothers me. A fix would be nice] [regression] [worked-in:16.10.0]
I recently uninstalled python 3.9.5 from my computer and I had issues with getting a python interpreter to work after trying to install python 3.7.8 through Visual Studio Installer. I then used the repair option in Visual Studio Installer and that got python to work but also made the Developer Command Prompt and Developer PowerShell stop working. I get "The terminal process has exited with exit code -1073741502." The Developer Command Prompt and Developer PowerShell under Tools->Command Line work fine. I am using Windows 10.0.19042.1052. I also tried uninstalling and reinstalling Visual Studio but I get the same problem. I also recently updated Visual Studio.
Also, Firefox and Firefox Developer Edition stopped working. It says "The code execution cannot proceed because VCRUNTIME140_1.dll was not found. Reinstalling the program may fix this problem." Microsoft Edge and Chrome work fine.

Original Comments
(no comments)

Original Solutions
(no solutions)

Thanks for the question, but unfortunately, this is more likely a bug in the Python uninstaller. The easiest solution is to reinstall Python 3.9.5.


Enabling Kubeflow stuck

I am trying to enable kubeflow on Linux by the command:
microk8s.enable kubeflow
It shows:
Enabling dns...
Enabling storage...
Enabling ingress...
Enabling metallb:<IP_ADDRESS>-<IP_ADDRESS>...
Waiting for other addons to finish initializing...
But I get nothing after this. Please help

Could you please attach the tarball created by microk8s inspect ?

@ktsakalozos I have attached the tarball.
inspection-report-20210607_152008.tar.gz


Javascript novice requesting assistance

Please could somebody tell me explicitly how to use this code (in particular to convert an image into a prime)

Do I need to save the code, its dependencies or the image I wish to convert anywhere specific?
What should I type into node in order to run the program?

I've tried pictoprime -V , pictoprime -i , $ pictoprime -V etc.

This is not an issue with the code, it's an issue with my knowledge and I would really appreciate it if someone could tell me how to use it. I initially started to learn javascript (in a few spare hours) to figure out how to use this code, but it and the instructions given are just as opaque to me as they were before. Please help :)

After installing the Dependencies you can run the program in one of two ways;

Clone the repo and run the file directly

In short, here are the terminal commands;
git clone https://github.com/TotalTechGeek/pictoprime folder/to/use/
npm i # or `yarn` if you use yarn, or `pnpm i` if you use pnpm
node index.js [options]
# to dump the prime number image to a text file for viewing; (I'm uncertain if this works on windows or not)
node index.js --image ./examples/headshot.png -x ascii > outFile.txt

git clone ... copies the code here in the repo to your computer so you can run it.
npm i will install the node dependencies (but not these dependencies)
node index.js [options] is your access point to the tool, pass in the options you want to use
node index.js --image ... is an example of turning the headshot of Matt into a prime number in a text file.
--image ./examples/headshot.png tells the program to use the image headshot.png in the examples folder
-x ascii tells the program to print the text to the terminal as plain text
-q tells the program to be silent until it's ready to print the plain text, it might seem like it's frozen but it's actually working fine in silence
> outFile.txt tells your terminal to take whatever the program outputs, and to write it in the file outFile.txt. (note that you may have to delete the file to run again unless you change the "outFile" name)

Use pictoprime as an npm executable

In short, here are the terminal commands;
npx pictoprime [options]
# to dump the prime number image to a text file for viewing; (I'm uncertain if this works on windows or not)
npx pictoprime --image ./examples/headshot.png -x ascii > outFile.txt

these two commands do the same as their option 1 counterparts beginning with node index.js

Getting an image output doesn't appear to be a capability of this program yet, but you can still take a screenshot of the text file if you want an image.


make the blockly i18n sync quieter

Codecov Report

Merging #250 into main will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #250   +/-   ##
=======================================
  Coverage   59.26%   59.26%
=======================================
  Files          95       95
  Lines       11767    11767
=======================================
  Hits         6974     6974
  Misses       4793     4793

Continue to review full report at Codecov.

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


Suggestion : Add "Added Date" to Items in the List

Hi, It would be great if each item in the list had an "added date" or something to help users identify newly added items.
Thanks!

Hi, It would be great if each item in the list had an "added date" or something to help users identify newly added items.
Thanks!

Any suggestions on how I could do this other than putting all the data from the README in a table?

Hi, It would be great if each item in the list had an "added date" or something to help users identify newly added items.
Thanks!

Any suggestions on how I could do this other than putting all the data from the README in a table?

I guess just put the current date you are adding the new links , in the end of the text  just put - 2024-06-30 for example or different date format doesnt matter , I think this is okay

we can add the date as a badge or tag at the end of each item line:
aceternity-ui - Copy paste the most trending react components without having to worry about styling and animations.

we can add the date as a badge or tag at the end of each item line:
aceternity-ui - Copy paste the most trending react components without having to worry about styling and animations.

This is great idea solution

we can add the date as a badge or tag at the end of each item line:
aceternity-ui - Copy paste the most trending react components without having to worry about styling and animations.

This is great idea solution

so is this gonna be the last option and you'll do this ? I like it

we can add the date as a badge or tag at the end of each item line:
aceternity-ui - Copy paste the most trending react components without having to worry about styling and animations.

This is a great idea but I still think it might be hard to spot latest ones with respect to dates.
New ones can simply shown with a different badge as
instead of Date, make it more easy for people to spot new ones and when a PR is merged the action will remove NEW and replace with the Date format above as per commit history.
![NEW](https://img.shields.io/badge/-NEW-61DAFB), you can adjust colors and all on shields.io site

we can add the date as a badge or tag at the end of each item line:
aceternity-ui - Copy paste the most trending react components without having to worry about styling and animations.

This is a great idea but I still think it might be hard to spot latest ones with respect to dates.
New ones can simply shown with a different badge as  instead of Date, make it more easy for people to spot new ones and when a new PR is merged the action will remove NEW and replace with the Date format above as per commit history.
![NEW](https://img.shields.io/badge/-NEW-61DAFB), you can adjust colors and all on shields.io site

This way it would be better to identify it, but would it be up to whoever created the PR to add this badge or would it be easier for me to add it by hand whenever a new PR appears?

we can add the date as a badge or tag at the end of each item line:
aceternity-ui - Copy paste the most trending react components without having to worry about styling and animations.

This is a great idea but I still think it might be hard to spot latest ones with respect to dates.
New ones can simply shown with a different badge as  instead of Date, make it more easy for people to spot new ones and when a new PR is merged the action will remove NEW and replace with the Date format above as per commit history.
![NEW](https://img.shields.io/badge/-NEW-61DAFB), you can adjust colors and all on shields.io site

This way it would be better to identify it, but would it be up to whoever created the PR to add this badge or would it be easier for me to add it by hand whenever a new PR appears?

If there was some CI/CD for this it would have been better but I think that can be left to you if you wish to add it or the person creating the PR, before merging you can ask the person creating the PR to add the change, I'll try looking into making a CI/CD pipeline if possible next week.

Thanks for the suggestion, but I think the README layout wouldn't look very nice. If it were a table it would make sense as it is on the site today.

Thanks for the suggestion, but I think the README layout wouldn't look very nice. If it were a table it would make sense as it is on the site today.

we can add the date as a badge or tag at the end of each item line:
aceternity-ui - Copy paste the most trending react components without having to worry about styling and animations.

This is a great idea but I still think it might be hard to spot latest ones with respect to dates.
New ones can simply shown with a different badge as  instead of Date, make it more easy for people to spot new ones and when a new PR is merged the action will remove NEW and replace with the Date format above as per commit history.
![NEW](https://img.shields.io/badge/-NEW-61DAFB), you can adjust colors and all on shields.io site

This way it would be better to identify it, but would it be up to whoever created the PR to add this badge or would it be easier for me to add it by hand whenever a new PR appears?

If there was some CI/CD for this it would have been better but I think that can be left to you if you wish to add it or the person creating the PR, before merging you can ask the person creating the PR to add the change, I'll try looking into making a CI/CD pipeline if possible next week.

If we add this New badge, how could we make it disappear after a while and how long would that be? What would the README layout look like?


[Card] Style audit

What package is this for?

[x] React
[ ] Angular

1. Card (basic)
The title on the card sits a little high compared to the design. The header productive-heading-02 should be vertically centered to the 48px height space with no subtitle (update top-margin from 8 to 13)
Design spec: https://pages.github.ibm.com/ai-applications/design/components/card/style
Storybook: https://next.carbon-addons-iot-react.com/?path=/story/1-watson-iot-card--basic

Current

Proposed

———
2. Card with subtitle
For the card with a subtitle, the card header space is actually 64px. The top margin for the header is the same as the card with no subtitle.
Design spec: https://pages.github.ibm.com/ai-applications/design/components/card/style#title-and-subtitle
Current
Storybook: https://next.carbon-addons-iot-react.com/?path=/story/1-watson-iot-card--with-date-time-picker-range-selector-existing-value

Proposed

———
3. Card with footer
Adjust ghost button placement and size of footer.
Current
Storybook: https://next.carbon-addons-iot-react.com/?path=/story/1-watson-iot-card--with-ellipsed-title-tooltip-external-tooltip

Proposed
(spec from #2145)

(The spec isn't on the design site right now but we are also updating the site to include the footer option)

4. Card with empty/error state
We should be consistent on the empty states and have the empty state content be left aligned (not centered).
Already available in code.
For small cards, we can use the option without the icon
Current
Storybook: https://next.carbon-addons-iot-react.com/?path=/story/1-watson-iot-card--error

#3 may be difficult to achieve, as the card margin would need to be removed for the footer section only

Not sure if this helps, but here's the C&CS storybook example of the same: https://ibm-cloud-cognitive.netlify.app/?path=/story/cloud-cognitive-components-cards-productivecard--supplemental-bottom-bar


Builds fail for components requiring window

Hi there!
Really great work on this, very nice alternative to Next + Gatsby and very slick. I've been getting errors on my build, I have 2 components that need the browsers window object and they crash the build process, I've tried a few different thinks like ErrorBoundary etc. My project runs just fine in the dev environment (minus my font but ill get to that later).
Here is the error: ReferenceError: window is not defined
Here is the Repo
Anyway, thanks for this killer project, deff gonna use this for some more things in the future.

Since react-static builds static versions of your site, most times you'll need to make sure the window object is available (which is essentially making sure you are in a browser environment). For most cases, simply wrapping your browser-only code in something like this is sufficient:
if (typeof window !== 'undefined') {
  // browser-only code
}

Hi guys !
Is React static can be used in other context than browser ?
If no, could we assume document and window are globally available and get rid on conditionnal imports and stuff like that everywhere ? Or better, a option to make some variables globally accessible in the react static config, to let the project versatile.
if (typeof window !== 'undefined') {
    const SmoothScroll = require('smooth-scroll')
}

this exemple works, but when you are using multiple front libraries it quickly become a mess ^^
What you think ?

You must write node safe code. Using window without a document check will error in the build stage because there is no DOM.  https://react-static.js.org/docs/concepts#writing-universal-node-safe-code


user object is undefined after successful redirect

Hi there, thanks for all your great work on this library!
I was wondering if you had any clue to what I'm doing wrong here. I am using Dex as my idp. I am able to sign in and am successfully redirected to my /callback route, however when I inspect the user object, it's undefined:

The url bar looks like:
http://localhost:3000/callback?code=wvhdzqi2ergpw5szga2zoycza&state=9b4d6656a0f948948d938b8aff82a21e
Here is my UserManager config:
const config = {
  client_id: "example-app",
  redirect_uri: `http://localhost:3000/callback`,
  silent_redirect_uri: `http://localhost:3000/callback`,
  response_type: "code",
  scope: "openid profile",
  grant_type: "authorization_code",
  authority: "https://localhost:5556/dex",
  issuer: "https://localhost:5556/dex",
  metadata: {
    authorization_endpoint: "https://localhost:5556/dex/auth",
    jwks_uri: "https://localhost:5556/dex/keys"
  },
  post_logout_redirect_uri: `http://localhost:3000`,
  automaticSilentRenew: true,
  filterProtocolClaims: true,
  loadUserInfo: true
};

Hi,
it looks like the user object itself is not undefined, but rather its content (access_token, session_state, etc.) This suggest a problem with oidc-client and dex. I suggest you raise an issue there as I sadly can't help you here.

@maxmantz Ah yes, sorry, poor wording on my part. Thanks for taking a look!


Update ssl configuration

This PR upgrade ssl configuration in order to use latest Mozilla recommendation (version 5.0) for the modern, intermediate and old profile.
Moreover, it add an option to change the default ssl policy defining the SSL_POLICY environment variable on the nginx-proxy container itself. Other containers can still change the ssl policy for their virtual host by setting the SSL_POLICY environment variable on itself as before.

@jwilder Please merge this. The current defaults generated are outdated and the addition of a global option to specify the default SSL policy is a great addition. We are currently using this container in a production environment with a decent amount of containers. In order to conform to PCI standards we must disable TLSv1.0 but cannot currently do so without specifying a per-container SSL_POLICY setting.


accuracy compares with VITS?

accuracy compares with VITS? does it faster and accurator?

We didn't compare with VITS in our paper quantitatively. Perceptually, the sound quality and prosody of PortaSpeech and DiffSpeech are similar with VITS. The differences between our models and VITS are:

Our models are acoustic models, which need an external vocoder (HiFi-GAN in our case) to build a TTS system, while VITS is an end-to-end TTS model.
Our models can train faster than the end-to-end TTS model since we can fix the vocoder part, which makes the model tuning easier.
End-to-end TTS models do not need to consider the quality gap between the generated and ground-truth intermediate features (mel-spectrogram), which avoids the error propagation problem.

So e2e TTS model and non-e2e TTS model have different usage scenarios.

i think PortaSpeech + MB MelGAN  can work on cpu very well, VITS need gpu to work.

i think PortaSpeech + MB MelGAN can work on cpu very well, VITS need gpu to work.

Yes, you can use other vocoders with PortaSpeech.


Gurps - Version 2.8.0

Submission Checklist
Required

[x] The pull request title clearly contains the name of the sheet I am editing.
[x] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[x] The pull request makes changes to files in only one sub-folder.
[x] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

Changes / Description
Version 2.8.0

Repeating Ranged Table. If the malfunction value is used and the malfunction value is lower than the effective skill, the malfunctin  value will be used as the effective skill. This will prevent confusion if your roll is says hit but the malfunction description appears.
Repeating Skills Table. Added new Conditionals textarea. Useful for keeping track of conditional modifiers for a skill. Such as Navigation (Land): +1 from Compass.
Add note to armor divisor, values are rounded down.
Combat Tab. Melee sub-tab. Add Slam calculator tool, taylored to the slam tools, instead of using the generic collision/falling damage tool.
Combat Tab. Defense sub-tab. Removed misleading success notes for Dodge & Retreat rolls. Reported by Uncle Mojo.

Character Sheet Info Roll20 Internal Use only.


Fix up column widths on distillery list page

Adding a description for Frey Ranch threw everything into a state of madness.

Closing as this will be better addressed in #105


Validate that the IM will ignore tags it doesn't understand (for forward compatability)

Problem
Validate that the various IM-related messages will ignore tags it doesn't understand to setup well for forward compatibility.

resolved