Hotfix/static collecting

Purpose
OSErrors unrelated to files already existing (such as permissions errors) caught during collect_static() should not be allowed to pass silently.
Closes https://github.com/CenterForOpenScience/modular-file-renderer/issues/138
Changes
When an OSError is caught, check to see if the path exists. If not, it's an unrelated error and is raised.
Side Effects
OSErrors might be raised.

Pass finished. :tractor:

Pass comment fixed


Call periphery.scan with augments

It seems that we can pass argument like we could in command line --
Do you confirm and if yes what is the proper syntax please @manicmaniac

@aiKrice
It converts method's arguments into command-line arguments here.
https://github.com/manicmaniac/danger-periphery/blob/933547119491ef2ec8f766a3356bc2c9a04f9d92/lib/periphery/runner.rb#L22-L39
The rule is simple.

Remove leading hyphens (--)
Substitute _ to -
If the option takes an argument, put it as value of Hash
If the option takes multiple arguments, surround it with an Array
If the option does not take arguments, just put true

Thus, for example,

--schemes Foo,Bar would be schemes: ["Foo", "Bar"]
--retain-objc-accessible would be retain_objc_accessible: true

Thank you mate for your reactivity ❤

Hello @aiKrice!
How can I pass the -destination argument to xcodebuild when running periphery scan?
I’m trying to use periphery scan within a CI pipeline, and I need to specify the -destination argument for xcodebuild (e.g., -destination 'platform=iOS Simulator,name=iPhone 15 Pro Max'). How can I achieve this when using the Danger plugin for Periphery?
Thanks for your help!

Ah, sorry I missed that. Arguments after double-hyphens -- are currently not supported.

I will add this feature by adding options like build_args.

Thanks a lot @manicmaniac!

Thank you @Xopoko, the feature has been shipped in 0.4.0 :rocket:


Reproducible audits

Code and tests for the reproducible audits class.

@JacobALussier @brownsarahm Do we need to merge 07_reproducible_audits.ipynb? Seems nothing useful in it.

Why there exist tests/.ipynb_checkpoints/Untitled-checkpoint.ipynb and tests/.ipynb_checkpoints/Untitled1-checkpoint.ipynb?

@JacobALussier will you be able to make the requested changes?


Have a progress indicator as part of the navbar

We have a navbar (#11) at the top of the page. Within each section / page there should be a visual indication of how many steps have to be done and how many heave already been completed.
E.g.:

if we have 20 columns to categorize on the categorization page, there should be 20 steps in the progress bar for this section
if there are 5 diagnostic values for the diagnosis column in the annotation page, then each one should be one step in the progress bar

Closing this. May revisit in the future.


Make it compatible with Z

So, there is this piece of code that substitutes cd, it uses frequency and recent directories for that and it is pretty handy.
For example if i were to go to ~/Workspace/Python/mysite/, i would z my<tab> and z would complete it to the fullpath z /Users/MyUser/Workspace/Python/mysite/. So it doesn't really matter where i am in the system. I like to think of it as if it creates dynamically  aliases for paths i cd into recently or frequently.
I wonder how hard would it be to make autoenv play nice with z.

It would have been great if you had provided a link to z.
As autoenv, z uses builtin which prevents alias usage: code
You can try to replace builtin cd in the z source code with autoenv_cd. Does this work for you?

I just started using z a few days ago and noticed this problem this morning. Did the replacements in the z source code as recommended and can confirm that so far it appears to work perfectly.

For what it's worth, fasd also cooperates fine with autoenv with no modifications. It hooks into $PROMPT_COMMAND and just calls whatever cd is out there, no builtin. This way autoenv (which replaces cd with a shell function) still gets a chance to do its thing.
I can't say objectively whether that's a good thing or a bad thing—I seem to recall some folks having strong opinions about it one way or another—but It Works for Me™.

I have been trying to get this to work too.
BTW, for Oh-My-ZSH, the z tool has been replaced with https://github.com/agkozak/zsh-z.

@dasJ's comment helped me to fix this issue upstream.
I opened this PR https://github.com/agkozak/zsh-z/pull/76 which introduces a way to overwrite the builtin cd command.

HEAD now introduces a documented AUTOENV_PRESERVE_CD variable, for use in situations like this. As the documentation states, setting it to a non-empty variable when sourcing activate.sh will skip overriding any user-definied cd function. This makes it easier to create custom cd functions that call both autoenv's autoenv_cd and whatever Z's equivalent function that is meant to be called on every cd invocation.


Keyword arguments as attributes for Tags

Could keyword arguments be automatically used as attributes for Tags?
I'm thinking something like:
class Tag:
    def __init__(self: Self, **kwargs: str) -> None:
        self.attributes: dict[str, str] = {}
        for key, value in kwargs.items():
            self.attributes[key] = value

Improved:
class Tag:
    def __init__(self: Self, name: str, text: str = '', **attributes: str) -> None:
        self.name = name
        self.text = text
        self.attributes: dict[str, str] = attributes
        self.children: list[Tag] = []

I'd also recommend that the .attribute() and .id() methods be removed since they are not useful.

Code would have to be remade to support the deprecation of these methods, since the class Tags has nested classes that inherit Tag, and then use .attribute().


Update terra.md

concept ACK

This one will have to wait for now, but thank you for the PR. 🤣

concept nACK @dwightjl


Documentation about shards and shard spaces

Hi folks,
This is more a question than an issue. I have an influxdb database in production used to store collectd metrics and to display them with grafana.
I created my db with default options and as is expected after a while I'm noticing how influxdb is taking storage space because I didn't define any retention or storage policies.
My question is how I can see the current settings for my db and how I can change them? The documentation is not clear in this regard: http://influxdb.com/docs/v0.8/advanced_topics/sharding_and_storage.html.
The documentation includes this: "You must set up shard spaces when you create your database.".
Does this mean I have to recreate my db?
In general, I'm unable to find any kind of GET request in the API to check current settings.
I don't want to try the POST requests examples in documentation that change things in the db without an understanding of what is going on.
Thanks,

Hi Paul,
I have a production setup of influxdb v0.8.8 , can I change existing database default retention policies..? if I cannot, can you guide me how to change the existing database path.


Fixed #35441 -- Fleshed out reference docs for django.template.Context

Trac ticket number

ticket-35441
Branch description
Provide a concise overview of the issue or rationale behind the proposed changes.
Checklist

[x] This PR targets the main branch.
[x] The commit message is written in past tense, mentions the ticket number, and ends with a period.
[x] I have checked the "Has patch" ticket flag in the Trac system.
[x] I have added or updated relevant tests.
[x] I have added or updated relevant docs, including release notes if applicable.
[x] I have attached screenshots in both light and dark modes for any UI changes.

@felixxm Ready for review again!

Ready for review again.


Plot plugin: add/remove, pause/resume individual topics  (ros-pkg ticket #5471)

From @tfoote on January 31, 2013 19:25
Plot plugin:

[ ] add/remove individual topics
[ ] pause/resume individual topics
[ ] persist/restore list of topics via settings
[x] auto-complete topic name (?)
[ ] clear-plot button

trac data:

Owner: dorianscholz
Reporter: dthomas
Reported at: Wed Jun 20 19:31:06 2012
URL: https://code.ros.org/trac/ros-pkg/ticket/5471

Copied from original issue: ros-visualization/rqt_common_plugins#27

From @tfoote on January 31, 2013 19:25
[dorianscholz] - merged plot and matplot plugins for consistent behavior

added removal for individual topics
save/restore topics is work in progress...

From @trainman419 on June 2, 2014 22:3
It looks like the following features have been implemented since this was last updated:

add/remove individual topics
persist/restore is implemented. It has a few open bugs.
there is a clear plot button. It does not do what I expect (see #231)


chore: automated PR to update ReleaseNotes for 202409.13.0 VHD

This is an automated PR to bump ReleaseNotes for the VHD release with image version 202409.13.0

Pull Request Test Coverage Report for Build<PHONE_NUMBER>6
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 71.271%

Totals

Change from base Build<PHONE_NUMBER>8:
0.0%

Covered Lines:
2590

Relevant Lines:
3634

💛  - Coveralls


Include full stacktraces from LogTestDurationListener test hang monitor

See https://github.com/prestosql/presto/runs/1497472672

tests apparently hanged
one test thread is here:

2020-12-04T07:53:43.1535741Z "pool-2-thread-2" prio=5 Id=16 BLOCKED on org.testng.TestClass@2a78dd6a owned by "pool-2-thread-1" Id=15
2020-12-04T07:53:43.1537790Z 	at app//org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:158)
2020-12-04T07:53:43.1539747Z 	-  blocked on org.testng.TestClass@2a78dd6a
2020-12-04T07:53:43.1540972Z 	at app//org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:108)
2020-12-04T07:53:43.1542880Z 	at java.base@11.0.9/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
2020-12-04T07:53:43.1545474Z 	at java.base@11.0.9/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
2020-12-04T07:53:43.1547540Z 	at java.base@11.0.9/java.lang.Thread.run(Thread.java:834)
2020-12-04T07:53:43.1548037Z
2020-12-04T07:53:43.1548486Z 	Number of locked synchronizers = 1
2020-12-04T07:53:43.1549747Z 	- java.util.concurrent.ThreadPoolExecutor$Worker@7cedfa63

the information who owns TestClass@2a78dd6a is not present, probably because every stacktrace is limited to 8 frames.

see full thread dump -- https://github.com/prestosql/presto/runs/1497472672  or  https://gist.github.com/findepi/2f87bad4047976bee6af9223f5d3ff6c

The relevant code is here:
https://github.com/prestosql/presto/blob/e7c36e313809310f94ee94491937a663aa037365/presto-testng-services/src/main/java/io/prestosql/testng/services/LogTestDurationListener.java#L149

@findepi A solution could be to copy the existing ThreadInfo.toString() method since all it needs is to override the default Max Frame limit.
Taking this method, we can suit it to our needs and call it some new method for example getFullStackTrace
The final method would look something like this:
private static String getFullStackTrace(ThreadInfo threadInfo) {
        StringBuilder sb = new StringBuilder("\"" + threadInfo.getThreadName() + "\"" +
                " Id=" + threadInfo.getThreadId() + " " +
                threadInfo.getThreadState());
        if (threadInfo.getLockName() != null) {
            sb.append(" on " + threadInfo.getLockName());
        }
        if (threadInfo.getLockOwnerName() != null) {
            sb.append(" owned by \"" + threadInfo.getLockOwnerName() +
                    "\" Id=" + threadInfo.getLockOwnerId());
        }
        if (threadInfo.isSuspended()) {
            sb.append(" (suspended)");
        }
        if (threadInfo.isInNative()) {
            sb.append(" (in native)");
        }
        sb.append('\n');

        StackTraceElement[] stackTrace = threadInfo.getStackTrace();
        int i = 0;
        final int MAX_FRAMES = 50;
        for (; i < stackTrace.length & i < MAX_FRAMES; i++) {
            StackTraceElement ste = stackTrace[i];
            sb.append("\tat " + ste.toString());
            sb.append('\n');
            if (i == 0 && threadInfo.getLockInfo() != null) {
                Thread.State ts = threadInfo.getThreadState();
                switch (ts) {
                    case BLOCKED:
                        sb.append("\t-  blocked on " + threadInfo.getLockInfo());
                        sb.append('\n');
                        break;
                    case WAITING:
                    case TIMED_WAITING:
                        sb.append("\t-  waiting on " + threadInfo.getLockInfo());
                        sb.append('\n');
                        break;
                    default:
                }
            }

            for (MonitorInfo mi : threadInfo.getLockedMonitors()) {
                if (mi.getLockedStackDepth() == i) {
                    sb.append("\t-  locked " + mi);
                    sb.append('\n');
                }
            }
        }

        if (i < stackTrace.length) {
            sb.append("\t...");
            sb.append('\n');
        }

        LockInfo[] locks = threadInfo.getLockedSynchronizers();
        if (locks.length > 0) {
            sb.append("\n\tNumber of locked synchronizers = " + locks.length);
            sb.append('\n');
            for (LockInfo li : locks) {
                sb.append("\t- " + li);
                sb.append('\n');
            }
        }
        sb.append('\n');
        return sb.toString();
    }

This allows us to continue reading up to 50 frames rather than the default. This could easily be configured by changing the value of MAX_FRAMES to a higher or lower number, or be accessible by making this a public statically available constant within the LogTestDurationListener class itself.

A solution could be to copy the existing ThreadInfo.toString() method since all it needs is to override the default Max Frame limit.

That would be good from technical perspective, but unfortunately it is not possible due to licensing reason.
The JDK is distributed under GPL (with classpath exception) license, and so the code from JDK cannot be copied into Apache License-licensed project.
We want to have the exact same behavior though, so the code needs to be written anew, taking at most inspiration only from the JDK code.

We want to have the exact same behavior though, so the code needs to be written anew, taking at most inspiration only from the JDK code.

Sounds like this is something I could work on implementing. Mind if I give it a shot?
A couple of questions for moving forward:

Do we need to even set a limit of max lines? As if we want all of the information we might as well let it work to through every single stack trace element.
Should we display information regarding the number of blocks/waits that occur? (Using getBlockedCount() & getWaitedCount(), etc) as the current toString() method does not display this information.
Should we display how long the blocks/waits take?

Mind if I give it a shot?

go for it, thanks!

Do we need to even set a limit of max lines?

no need for a limit

Should we display information regarding the number of blocks/waits that occur? (Using getBlockedCount() & getWaitedCount(), etc)

My personal opinion is that we do not need this.

Should we display how long the blocks/waits take?

If a thread is currently blocked, having information how long it is blocked could be useful
You didn't ask for this, but to be sure we're on the same page, the pretty important part of the output is

owned locks  ("locked" & "locked synchronizers")
locks being attempted

as the most common thing to look for is potential deadlock or livelock (as eg it was recently the case around https://github.com/square/okio/pull/818)

@findepi I went with creating a new class called StackTraceUtil that has a singular public method to retrieve full stack trace information as this could be used anywhere that ThreadInfo would like to be inspected. This goes a little more in-depth than the normal toString() function on ThreadInfo, by adding the following information:

DAEMON status
Time spent on blocked/waiting threads
Locked Synchronizer class name/hash code
Unlimited stack trace frames (rather than the default of 8)

As well as using an easier to read format:

Header section showing Thread ID, State, Suspension Status, In Native, Is Daemon, and any lock that was incurred with the associated owner tagged along with it, only if they are accessible.
Sections with headers for ThreadState information, locked monitors per stack trace element.
Locked Synchronizers section displaying all locked synchronizers

See the mentioned PR here #6236


Make Material UI depend on Emotion

When Material UI is re-enabled in #53, we should probably make it depend on Emotion like Chakra UI does.

Now tracked in #53 itself.


fix(tf): lock versions of terraform-google-modules/kubernetes-engine

fixes terraform validate issues in v3.0.0

/gcbrun


Only show 'next' link if there are more entries

Coverage increased (+0.002%) to 94.409% when pulling e7e3589f5ef5dbb29a6cae5c4808156b2a3861a9 on cody-fix-next-link into b81791dca3caeb26a222146e3da408022e74e29c on main.


Show Shift as icon

Hi there! it would be great if SHIFT could be shown as a modifier when used with letters, instead of showing the upper-case letter. Or maybe add it as a option under preferences.
#104 already asked but it's old and there has been no movement. Another look at #140 would also be great.
Other than that great tool, thanks!

#140 is a bit subtle and there might not be a zero-sum fix to address it. Totally agree with you about #104, let's keep the conversation there. Thanks!

I think we'll do this as a part of #187 -- keycap mode would show the shift key, whereas input mode would show the resulting shifted input key.

I think we'll do this as a part of #187 -- keycap mode would show the shift key, whereas input mode would show the resulting shifted input key.

Has there been any progress on this? I would like to bump the topic.

This will be the behavior in v0.9.10, it may become toggle-able in a later release.


clippy

WIP clippy lint
Will be merged when all warnings are fixed.

MFW there's an xclippy command.
So, clippy has something that turns all warnings into errors. See https://github.com/MegatonHammer/linkle/blob/master/ci/script.sh#L16 (-D warnings means "deny warnings")

Closes #68


privilege spec 1.11 (2019) is generating mstatush CSR in trap handler which is not defined in that version.

Hi.
I am using default privilege version in riscof which is using version 1.11 (2019). With the latest version (3.8.0) I am seeing mstatush being present in Trap handler (which is not defined in version 1.11), due to which tests having exceptions are going to mstatush csr in trap handler, then taking illegal exception and not ending.
Can you please check on this once...

Ah, yes; that should only be accessed for RV32 && H-exstension implemented.

We can close this issue, as it has been resolved in PR #406

closing, as above


Error in UIControl Callback

I get the following error when processing my file, and I'm not sure why. My .wav files should all be the same but I get this error on a couple of them when I try to process the file.
The logical indices in position 2 contain a true value outside of the array bounds.
Error in syllable_activity_file_stats (line 72)
syllable_data=syllable_data(:,syllable_use==1);
Error in compute_musv (line 93)
[syllable_data, syllable_stats, filestats] = syllable_activity_file_stats(handles, audiofile,
TotNbFrames, syllable_data);
Error in process_file (line 7)
[syllable_data, syllable_stats, filestats,
fs]=compute_musv(wav_dir,wav_items(selected_wav),handles);
Error in processAudioFile_Callback (line 2)
handles=process_file(handles);
Error in
matlab.graphics.internal.figfile.FigFile/read>@(hObject,eventdata)processAudioFile_Callback(hObject,eventdata,guidata(hObject))
Error while evaluating UIControl Callback.

Can you share a wav file for us to reproduce and debug this issue?

Hi, we are also experiencing this issue. Here are the files. Thanks!

I have fixed this problem.
FIX:
Find the following lines in the file "syllable_activity_file_stats.m"  :
if isempty(syllable_use)
syllable_use=ones(1,length(syllable_data));
end
and replace them with the following
if isempty(syllable_use)
syllable_use=ones(1,size(syllable_data,2));
end
Save the new version of the code and rerun.
Explaination:
The problem is that the cell array "syllable_data" has 9 rows and a number of columns equal to the number of detected calls in the file.  The errors you pasted above come from the lines in "syllable_activity_file_stats.m"  where the variable "syllable_use" is defined.  Those lines are:
if isempty(syllable_use)
syllable_use=ones(1,length(syllable_data));
end
If the number of syllables is less than 9, the length function will return the number 9 (it returns the max of the size of the array) and not the number of columns.  Then, when it is used in the line
syllable_data=syllable_data(:,syllable_use==1);
it will try to access 9 columns when there are only less than that and it will throw and error.
For example, say a file has 8 calls.  Then the size of "syllable_data" will be (9,8), i.e., 9 rows and 8 columns (one for each syllable).  Then length(syllable_data) will return 9 instead of 8.  Then when the line syllable_data=syllable_data(:,syllable_use==1); is executed, it will through an error since it is trying to access 9 columns of the data when there are only 8.


Geometry column duplication 👻 mystery issue 👻

This issue has to do with as yet unpublished code, importing filings using st_read function
Here's the pertinent snippet:
connect <- dbConnect(PostgreSQL(),
                     dbname=local_db_name,
                     host="localhost",
                     port=5432)
query <- "select * from filings as f left join plaintiffs as p on p.docket_id = f.docket_id"

filings <- st_read(connect, query=query) %>% st_set_geometry("geometry") %>%
  modify_at("docket_id.1", ~NULL) %>% modify_at("id", ~NULL) %>% modify_at("id.1", ~NULL)

When running the std_split_addresses function on the filings table (street column), I get the error:
Can't transform a data frame with duplicate names.
The problem is, before running the method, there were no duplicate column names in my filings table.
After running it, I have two geometry columns. Why?!
After commenting out most of the std_split_addresses function, I think the problem is happening at this extract function: https://github.com/ericrobskyhuntley/deduplicate-owners/blob/main/deduplicate-owners.R#L288
None of this makes any sense, and therefore seems to me that there might be a low-level bug somewhere. With lines 289 to 326 commented out, I am able to reproduce it consistently.
The current hacky solution is adding a "drop column" right after the extract function, hopefully that works.

Both r modify_at("geometry", ~NULL) and r  st_drop_geometry() cause the same error: ```Error in if (!setting_geom) { : missing value where TRUE/FALSE needed

Moving the drop column call past the mutate function results in the old error ```! Can't transform a data frame with duplicate names.

Interesting - my best guess here is that you're dealing with the downstream impact of working with a spatial dataframe. I'm not going to have time to play with this today, but here's what I'd try...
First of  all, st_drop_geometry() should always be your go-to for getting rid of a geometry column (it changes the dataframe object type to a non-spatial df).
Second of all, it sounds like it's having trouble identifying the geometry column, which can cause some strange behavior. See what the geometry column is called when you read it in. (E.g., it might "geom", not "geometry"?) Then run st_set_geometry("geometry_column _name") %>% st_set_geometry("geometry") to set and rename. (See https://github.com/ericrobskyhuntley/deduplicate-owners/blob/main/deduplicate-owners.R#L798 ).

Also, that std_split_addresses() function is by FAR the hackiest function in the script... check to make sure that none of your columns going in use the same names as the columns that it creates in separating the address and street fields.

I added the hacky fix:
 %>% st_set_geometry("geometry") %>%
    st_drop_geometry("geometry") %>%

The column and its duplicate are both called geometry. Tried various drop/set combinations and this one seems to work. I chalk it up to R language's fault, as none of this makes much sense.

I BELIEVE this should be fixed as of 261d39b ... see the (kind of unwieldy, but still helpful, process_records() function.


Feature request: Initialize StoreProvider with defaultState

I'm trying to implement something like this library: https://github.com/charkour/zustand-di
I'm using the utility helper from this library(zustand-slices) to create the Provider, but I'm still dealing with the TS Type inference to make it type-safe.
Could you provide a example of this feature?
It's really helpful for testing. I don't wanna use stores without Provider because it's really hard to test.
Any idea?
I want to get the Provider like this
<GlobalStoreProvider defaultState={initialState}>
where initialState infers the type based on my store, thanks!

If I understand it correctly, the question is about how to type React Context, which is not specific to Zustand.
How does zustand-di solve it?
Please try to create a very very small example to illustrate what you would like to accomplish with https://www.typescriptlang.org/play.

Hi, a bit busy with my little one today. I'll make a demo tonight and share it with you. Thanks

Hi @dai-shi , I've written an example and added some comments. https://stackblitz.com/edit/45xjf7?file=index.tsx

Unfortunately, the example doesn't help me understand the problem. Is it modified after you created?
I have a few comments:

What you request should be possible on your end. You can use Context and zustand-slices and create store using props.
If your question isn't tied to zustand-slices, you might want to open a discussion in the zustand repo. More people will look
In general, it's not certain if using Context only for testing is ideal. I would avoid adding code in production which is only required for testing.


Check if there is a more customized method for adding css

While we can import every type of css file it would be a mess to find out what is happening with 15 different subpages.
The thymeleaf syntax documentation can be found Here

No.


react native 0.65 not compatible with version 1.9.1 and up

Summary
version 1.9.1 and up require node >= 18, but react native 0.65 depends on node v16
Reproducible sample code
<MapView
  initialRegion={{
    latitude: 37.78825,
    longitude: -122.4324,
    latitudeDelta: 0.0922,
    longitudeDelta: 0.0421,
  }}
/>

Steps to reproduce
npx react-native init MyNewProject --version 0.65
yarn add<EMAIL_ADDRESS>yarn react-native start
yarn react-native run-android
Expected result
successfully build the project
Actual result
should able to build project with node v16, since react native 0.65 depends on node v16
React Native Maps Version
1.10.0
What platforms are you seeing the problem on?
Android
React Native Version
0.65.3
What version of Expo are you using?
Not using Expo
Device(s)
Xiaomi 11T Pro
Additional information
No response

@vellvj this is not a bug .. the library is constantly being updated to use the latest react-native, backward compatibility is ensured by simply using older versions of the library.


Update rtest.py to the standardized version

This allows us to consolidate the two rtest xml files. See https://github.com/ROCmSoftwarePlatform/rocSOLVER/pull/319.

The gfx906 build is passing.

@tfalders @eidenyoshida @lawruble13 @jzuniga-amd, could we try to get this in?

No prob. I wasn't expecting this to be important. It came as a bit of a surprise that it was necessary (and sufficient) to fix the build.


chore: migrate to Trampoline V2

I think pupulate-secrets.sh is now using the service account attached
to the Kokoro VM, so I updated the comments in that file.
.trampolinerc will be sourced from trampoline_v2.sh in its early
stage. .trampolinerc calls populate-secrets.sh.
I hope this works.
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[ ] Make sure to open an issue as a bug/issue before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[ ] Ensure the tests and linter pass
[ ] Code coverage does not decrease (if any source code was changed)
[ ] Appropriate docs were updated (if necessary)

Fixes #<issue_number_goes_here> 🦕

Samples test succeeded with weird message:
================================================================
2020-09-14T18:30:23Z: Running the tests in a Docker container.
================================================================
npx: installed 31 in 2.598s
Error: Wanted node version 10 (>=10.0.0 <11.0.0)
node: 12.18.3
To install node, run `nvm install 10` or see https://nodejs.org/
coverage is only reported for Node 10
================================================================
2020-09-14T18:30:32Z: Build finished with 0
================================================================

I think we should confirm that populate-secrets.sh successfully populate at least one secret.
Maybe we can experiment with one of the presubmit builds.

I confirmed that populate-secrets.sh works as expected in this build. Here is the log:
2020-09-14 14:09:45 Secret written to /tmpfs/src/gfile/secret_manager/npm_publish_token

I'll revert the change for this experiment.

@bcoe It sounds good. If you have a specific repository in your mind? I'd be happy to create a similar PR there.

@tmatsuo actually, the best approach might be to make the change here:
https://github.com/googleapis/synthtool/tree/master/synthtool/gcp/templates/node_library/.kokoro
Then I can run synthtool from a branch on any of our repos, and we can see if it works; I was thinking I'd pick a library like nodejs-phishing-protection.

@bcoe Yeah, but in the first step of the migration, it's easier to work on the actual repo.

I think this would be a good choice:
https://github.com/googleapis/nodejs-phishing-protection
It was useful to see this in action, but I should have thought of the fact that we don't have sample tests on this repo (sorry about the extra work).

@bcoe No problem, I'll create a similar PR there.


🐞 Dont spellcheck none spellable texts

Issue:
We spell check all our text inputs, most of our text inputs do not require spell checking
Screenshot:

addressed by https://github.com/kubev2v/forklift-console-plugin/pull/1238


cleanup(falco): consolidate falco::grpc::server in one class

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind cleanup

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area engine

What this PR does / why we need it:
I was investigating the following warning from UBSan
/home/ubuntu/dev/falcosecurity/falco/userspace/falco/grpc_request_context.cpp:53:24: runtime error: member call on address 0x7fff2627bce0 which does not point to an object of type 'server'
0x7fff2627bce0: note: object has a possibly invalid vptr: abs(offset to top) too big
 eb 55 00 00  40 01 08 00 20 61 00 00  00 00 00 00 00 00 00 00  88 c6 24 9c eb 55 00 00  40 01 08 00
              ^~~~~~~~~~~~~~~~~~~~~~~
              possibly invalid vptr
    #0 0x55eb96fef9bb in falco::grpc::request_stream_context<falco::outputs::service, falco::outputs::request, falco::outputs::response>::process(falco::grpc::server*) /home/ubuntu/dev/falcosecurity/falco/userspace/falco/grpc_request_context.cpp:53
    #1 0x55eb96e11637 in falco::grpc::server::thread_process(int) /home/ubuntu/dev/falcosecurity/falco/userspace/falco/grpc_server.cpp:115
    #2 0x55eb96e92a4d in void std::__invoke_impl<void, void (falco::grpc::server::*)(int), falco::grpc::server*, int>(std::__invoke_memfun_deref, void (falco::grpc::server::*&&)(int), falco::grpc::server*&&, int&&) (/home/ubuntu/dev/falcosecurity/falco/build-sanitizers-
local/userspace/falco/falco+0xb069a4d)
    #3 0x55eb96e91398 in std::__invoke_result<void (falco::grpc::server::*)(int), falco::grpc::server*, int>::type std::__invoke<void (falco::grpc::server::*)(int), falco::grpc::server*, int>(void (falco::grpc::server::*&&)(int), falco::grpc::server*&&, int&&) (/home/ub
untu/dev/falcosecurity/falco/build-sanitizers-local/userspace/falco/falco+0xb068398)
    #4 0x55eb96e90777 in void std::thread::_Invoker<std::tuple<void (falco::grpc::server::*)(int), falco::grpc::server*, int> >::_M_invoke<0ul, 1ul, 2ul>(std::_Index_tuple<0ul, 1ul, 2ul>) (/home/ubuntu/dev/falcosecurity/falco/build-sanitizers-local/userspace/falco/falco
+0xb067777)
    #5 0x55eb96e840e5 in std::thread::_Invoker<std::tuple<void (falco::grpc::server::*)(int), falco::grpc::server*, int> >::operator()() (/home/ubuntu/dev/falcosecurity/falco/build-sanitizers-local/userspace/falco/falco+0xb05b0e5)
    #6 0x55eb96e6eac3 in std::thread::_State_impl<std::thread::_Invoker<std::tuple<void (falco::grpc::server::*)(int), falco::grpc::server*, int> > >::_M_run() (/home/ubuntu/dev/falcosecurity/falco/build-sanitizers-local/userspace/falco/falco+0xb045ac3)
    #7 0x7f3b6cadc252  (/lib/x86_64-linux-gnu/libstdc++.so.6+0xdc252)
    #8 0x7f3b6be94ac2 in start_thread nptl/pthread_create.c:442
    #9 0x7f3b6bf2684f  (/lib/x86_64-linux-gnu/libc.so.6+0x12684f)

Essentially, what's happening is that request_stream_context<outputs::service, outputs::request, outputs::response>::process(server* srv) is trying to invoke (srv->*m_process_func)(*m_stream_ctx, m_req, res); which is assigned to &server::get. Now, the get() function is not defined in server (the type of srv) but in its base class server_impl. I read through some posts and documentation and I could not be convinced if this is undefined behavior (like UBSan was saying) or not.
However, after looking at these classes it looks like that there is only one derived class of server_impl which is server, where server acts as an interface with the rest of the code. Since it looked a bit odd that the interface derives from the implementation and there is no other use of this inheritance, I think it's safe to use a single class for the server. Any potential UB is gone and the files are a bit easier to read.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

NONE

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: LucaGuerra
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [LucaGuerra]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/milestone 0.38.0

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP, LucaGuerra
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [FedeDP,LucaGuerra]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 4b46e2706c339ca4a3f84efa2989c03725f4bf69

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, FedeDP, LucaGuerra
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,FedeDP,LucaGuerra]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


docs: fix react sample startup guide & add needful dependency …

Description
Refined the guidance for example and added a required dependency that otherwise would have prevented the sample service from starting due to dependency and build issues.
Checklist:

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings

Type of change.

[ ] FIX - a PR of this type patches a bug.
[ ] FEATURE - a PR of this type introduces a new feature.
[ ] BUILD - a PR of this type introduces build changes.
[ ] CI - a PR of this type introduces CI changes.
[x] DOCS - a PR of this type introduces DOCS improvement.
[ ] STYLE - a PR of this type introduces style changes.
[ ] REFACTOR - a PR of this type introduces refactoring.
[ ] PERFORMANCE - a PR of this type introduces performance changes.
[ ] TEST - a PR of this type adds more tests.
[ ] CHORE - a PR introduces other changes than the specified above.

Please change the initial branch merge to DEV. Thanks!

done

@AlienegraGeek Sorry for jumping in, but I'd like to invite you to participate in the Race of Sloths - a fun and gamified open-source contributions program. Consider mentioning @race-of-sloths user in your github comment or PR description to join!
See how the flow works here: https://github.com/near/nearcore/pull/11778

@race-of-sloths

@AlienegraGeek Thank you for your contribution! Your pull request is now a part of the Race of Sloths!
New Sloth joined the Race! Welcome!

Current status: waiting for scoring
We're waiting for maintainer to score this pull request with @race-of-sloths score [0,1,2,3,5,8,13] command
What is the Race of Sloths

Race of Sloths is a friendly competition where you can participate in challenges and compete with other open-source contributors within your normal workflow
For contributors:

Tag @race-of-sloths inside your pull requests
Wait for the maintainer to review and score your pull request
Check out your position in the Leaderboard
Keep weekly and monthly streaks to reach higher positions
Boast your contributions with a dynamic picture of your Profile

For maintainers:

Score pull requests that participate in the Race of Sloths
Engage contributors with fair scoring and fast responses so they keep their streaks
Promote the Race to the point where the Race starts promoting you
Grow the community of your contributors

Feel free to check our website for additional details!

Bot commands

For contributors

Include a PR: @race-of-sloths include to enter the Race with your PR

For maintainers:

Assign points: @race-of-sloths score [1/2/3/5/8/13] to award points based on your assessment.
Reject this PR: @race-of-sloths exclude to send this PR back to the drawing board.
Exclude repo: @race-of-sloths pause to stop bot activity in this repo until @race-of-sloths unpause command is called

❌ PR inactive
This PR has been inactive for two weeks. It's now marked as stale.

[!TIP]
If you think it's a mistake, you can restart the bot with include command to proceed 🔄


Editing Home.js causes full reload

As description states, hot loading should work.

I don't get this error when I try to edit Home.js, and don't know what's causing it.


bot command for ai generated songs (https://this-voice-does-not-exist…

….com/music)

blocked by #35

🎺


Need tester/feedback for homebrew formula

I am considering a simpler installation for OSX users via a homebrew formula.
Please report any issues/suggestions here -- all feedback welcome.

Thanks a lot for making this available as a brew formula, it is a great tool!

Do the dependencies install correctly? (fzf, codeutils, findutils, etc)

The only dependency that was not automatically installed for me was ggrep, which it seems is not part of coreutils and is used by the bash p() function. There is a brew formula called grep that I manually installed to remedy this.

Does homebrew automatically make the binary fast-p available in your $PATH?

Yes it does.

Thanks a lot or the feedback! I added the grep dependency.

Could you break the formula into two?

fast-pdf-finder: has dependencies on (a newly introduced) fast-p, codeutils, findutils, etc.
fast-p: with dependencies only poppler and pkg-config.

So that, if we want to use fd for the ag -U -g ".pdf$" part, we won't have ag automatically installed.

@soraros : is an un extra possibly unused dependency such as ag an issue?
The current formula is built automatically with goreleaser, nothing is modified by hand. Two formulae and the loss of the automatic built would add complexity and make it harder to maintain.

@bellecp Oh, I meant fast-pdf-finder as a wrapper around the fast-p, with brew install fast-p behaving like download the prebuilt package from the release page, because building fast-p itself shouldn't need grep etc, right? Maybe I'm just making some false assumptions.
The formula works fine and unused dependency is not a big problem, so big thank you anyway!

Thanks for the pull request on the other repo. As explained there, your modification would be overwritten by the automatic build of the formula.
I prefer to keep all dependencies as it is now, so that all the tools needed for default bashrc code are installed. This is a trade-off, but I think the cost of extra dependencies is minor compared to the possible confusion where one installs the formula without recommended dependencies and the default formula fails to work.

I just discovered this repository after looking to search my 3000+ pdf files using fzf.
I followed the Homebrew install instructions in the README.md, added p () to my .zshrc and was up and running in less than 1 minute. No issues whatsoever! 🎉
I must say I'm really impressed with the performance and usability. Thanks a lot for making and sharing this!

The formula seems to be working so far, closing this.


bugfix#55: timestamp handling and insertion with correct timezone

The difference in the time zone offsets between the PostgreSQL and H2 databases is likely due to the different ways each database handles timestamps with time zones.
In PostgreSQL, when you insert a timestamp with a time zone using the format '2022-06-06T12:00:00', it is interpreted as being in the default time zone of your PostgreSQL server, which might be set to UTC. Therefore, the timestamp is stored in the database with a time zone offset of +00:00.
On the other hand, in H2, when you insert a timestamp with a time zone using the format '2024-06-06 12:00:00+01:00', the timestamp is explicitly specified with a time zone offset of +01:00. H2 will store the timestamp with this specified offset.
So set database timezone to Europe/Paris and define the TIMESTAMP offset in both insert scripts fixed the problem.


How to install ?

How do you install the extention ?
[notice] To update, run: python3.10 -m pip install --upgrade pip
frappe@erp:~/frappe-bench/env/bin$ ./pip install git+https://github.com/nathanIL/openiban
Collecting git+https://github.com/nathanIL/openiban
Cloning https://github.com/nathanIL/openiban to /tmp/pip-req-build-djfk4cne
Running command git clone --filter=blob:none --quiet https://github.com/nathanIL/openiban /tmp/pip-req-build-djfk4cne
Resolved https://github.com/nathanIL/openiban to commit cb12ac2914b60d0e77785809ead0e2cf6311220f
ERROR: git+https://github.com/nathanIL/openiban does not appear to be a Python project: neither 'setup.py' nor 'pyproject.toml' found.

Hi,
haven't touched it for a while now.
I will try to install & fix if necessary later today.
thanks for asking 🙏


fix: prevent sending user data to guests

Description
Guests shouldn't be able to see the name of those who created an event. While the UI respects this, the data is still being sent from the server and that data is visible in devtools.

This PR excludes the user data from the JSON response when the user is not logged in.

Note: Didn't run frontend tests.

Type of change
Please select everything applicable. Please, do not delete any lines.

[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 not work as expected)
[ ] This change requires a documentation update
[ ] This change requires an update to testing

Issue

[ ] Is this related to a specific issue? If so, please specify:

Checklist:

[X] This PR is up to date with the main branch, and merge conflicts have been resolved
[X] I have executed npm run test and all tests have passed successfully or I have included details within my PR on the failure.
[X] I have executed npm run lint and resolved any outstanding errors. Most issues can be solved by executing npm run format
[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[X] I have commented my code, particularly in hard-to-understand areas
[X] My changes generate no new warnings

Accessing the event view modal while not logged in and not mocking a user returns these errors.


Web page is not being navigated sequentially with the Tab key, Design issue.

Describe the bug
Web page is not being navigated sequentially with the Tab key, Design issue. The sequence of focus is unordered.
To Reproduce
Steps to reproduce the behavior:
Go to Design  (http://localhost:9992/cm/app/?view=design&pathType=unknown)
Use Tab key to focus on different components of the screen.
Focus is not moving in sequence on Create Site, Create Folder, create Page etc.
Expected behavior
Web page should be navigated sequentially with the Tab key.
Additional context
Navigate all the options available for similar issue and fix.

Fixed with https://github.com/percussion/percussioncms/issues/779


Remove bound from MvccReader

Signed-off-by: Breezewish<EMAIL_ADDRESS>
What have you changed?
They are not used any more, so simply remove it.
What is the type of the changes?

Engineering (engineering change which doesn't change any feature or fix any issue)

How is the PR tested?

Unit test

@mapleFU Please click "Approve" if you think this PR is ok.

/run-all-tests

/merge


Use Mapillary vector tiles and switch to v4

Edit: This PR has now been updated to use the new (v4) Mapillary API.
The old API will be shutting down soon so, in order to keep the Mapillary integration working, it would be great if this PR could be merged as soon as possible.

Hello, this PR updates the Mapillary integration and now it uses our vector tiles as the data source for images, sequences and map features (traffic signs and points).
With this change the loading of Mapillary data should be much faster (you should observe an improvement in loading speed of 1000%+ in very densely mapped areas).
Changes
Switched to using vector tiles instead of the Mapillary API
Updated the data and cache structure to match new data source
Fixed a bug with clicking on a Mapillary image marker
Updated how Mapillay JS is initialized (version 3.0.0 introduced some breaking changes)
Removed user filter for Mapillary images (vector tiles don't have usernames right now)
Cleaned up the code and used a bit more modern JS where possible
You can test a preview of the changes here: https://id-mapillary-tiles.netlify.app/
Check the old PR for previous discussion: https://github.com/openstreetmap/iD/pull/8367 as this is a new branch with all the changes and bug fixes in a single commit, based on the latest develop
Let me know if you have any question or suggestions.
Thanks!

@quincylvania This PR also prepares the Mapillary integration for the upcoming changes to our API. Here's a blog post with more details: https://blog.mapillary.com/update/2021/03/03/preparing-for-the-new-mapillary-api.html
The plan is to create another PR which would just update the URLs to the new API (when it's available) and this should hopefully make for a smooth transition.

@nickplesha the speed improvements sound great!
However, I was really happy to finally see a username-filter added only recently https://github.com/openstreetmap/iD/issues/5307 and it would be a sad thing to see it go … 😿
Looking at https://blog.mapillary.com/update/2021/03/03/preparing-for-the-new-mapillary-api.html it sounds like, that usernames will be filterable soon again, so you would be able to re-add them soon?

Filtering will happen on the client side of the vector tiles (for example filtering image point data by a date range, a set of usernames, or spatial overlap with a polygon)

Or does this part reference the fact, that filtering need to be done in iD now, so it still could be there but needs to be reworked?

Updated PR with the switch to the v4 Mapillary API and vector tiles.

Fixed merge conflicts.

@mbrzakovic Thanks for reviewing the code!
I was wondering if there are plans make a new release of iD soon? I'm asking as the currently deployed version still uses Mapillary API v3 which we plan to shut down on August 18th.

@mbrzakovic Thanks for reviewing the code!
I was wondering if there are plans make a new release of iD soon? I'm asking as the currently deployed version still uses Mapillary API v3 which we plan to shut down on August 18th.

Yes, I was going to ask you what is the eol date for v3, thanks for the info!
I can't say anything official yet but you can expect the answer/announcement in the next week or two.
Its good to know that we have time on this and hopefully we won't get too close to the deadline.

Hey @nickplesha,
I was doing some local testing and found that translation for some mapillary map features are missing.
Can you repro the attached img?
If so, I think its due to Mapillary v4 using new set of feature objects and iD/data/core.yaml[mapillary_map_features] section is out-of-date.
Where can the list of feature object names be found? Curious on how often does Mapillary update this list?

@mbrzakovic I think it was from the map feature titles, but we don't use them at all so I've removed them and I think this should fix those errors.

@mbrzakovic I think it was from the map feature titles, but we don't use them at all so I've removed them and I think this should fix those errors.

@nickplesha yes this fixes the error, unfortunately the change also disables the tooltips (hover over the mapillary features).
Can you please look closer into the code to see if we could have the solution that would eliminate the error and keep the tooltip.
From the quick look it seems to me that we would require full list of possible feature object types labels (e.g.: object--sign--advertisement) so that we could include them into core.yaml [translation files] and enable tooltips for multiple languages.

@mbrzakovic OK, so that's what's it for, I haven't noticed the tooltips before. :) I brought them back now, and I've updated core.yaml to include all of our map feature classes and their names.

@mbrzakovic OK, so that's what's it for, I haven't noticed the tooltips before. :) I brought them back now, and I've updated core.yaml to include all of our map feature classes and their names.

@nickplesha Yes, thanks.
Sorry but when I go to urban areas with console on I am still seeing few more missing:
mapillary_map_features.construction.flat.driveway
mapillary_map_features.construction.barrier.temporary
mapillary_map_features.object.traffic_sign.direction_front
mapillary_map_features.object.traffic_sign.front
mapillary_map_features.object.traffic_sign.back
mapillary_map_features.object.sign.other
As mentioned above, I am curious on how often does Mapillary update this list?

@mbrzakovic Thanks, I've added those classes. The last time we updated the list was two years ago and I don't anticipate significant changes in the future.


Ensure all TOB updates are applied to ICOB

Ensure any commits to TOB are also applied to ICOB (https://github.com/bcgov/indy-catalyst).
Updates were last sync'ed on July 26 so any TOB updates since then must be manually applied to ICOB.

@andrewwhitehead do you have anything to do for this?  If not, please close with a note.

My changes have all been applied


Backport "Improve composability of mkShell" to release-19.03

Motivation for this change
Backport of https://github.com/NixOS/nixpkgs/pull/63701 to release-19.03.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

I'm not sure that this kind of change is suitable for backported since there is a risk that it introduces a regression.

I actually expected mkShell to compose shellHooks like it composes build inputs (it's for shells after all) and got surprised when it didn't. So this could be considered a fix bringing mkShell to expected behaviour. However I know this is stretching it and I agree this has a risk of introducing a regression for someone relying on the old behaviour not adding more shellHooks to their nix-shell.
Shall I revert?

As long as it doesn't break back-compat it doesn't need to be reverted, but I agree with Eelco, it's a new feature

However I know this is stretching it and I agree this has a risk of introducing a regression for someone relying on the old behaviour not adding more shellHooks to their nix-shell.

It broke our setup at least. This is effectively an API change, and not one I would expect to have to deal during a normal update. :-)

@adamtulinius Thanks for the report. I've reverted this on release-19.03.


Comment back with link to the created discussion

Closed by 29a76c6: Comment back on PR with success. Added graphql schema …


Date Format

using date range picker with bootstrap 4 ,tried to change default date format "dd/mm/yy" but it isn't .
 $('#toDate').datepicker({          uiLibrary: 'bootstrap4',          iconsLibrary: 'fontawesome',          dateFormat:"dd-mm-yy",          maxDate:today,         minDate: function () {              return $('#fromDate').val();          }      });

I'm not able to replicate that issue. You can see some examples at https://gijgo.com/datepicker/configuration/format


offline signing issue

Im trying to sign transaction, but get this traceback
Traceback` (most recent call last):
  File "/usr/local/bin/piston", line 11, in <module>
    sys.exit(main())
  File "/usr/local/lib/python3.6/site-packages/pistoncli/__main__.py", line 1242, in main
    steem = Steem(**options)
  File "/usr/local/lib/python3.6/site-packages/piston/steem.py", line 133, in __init__
    self.rpc.register_apis(["account_by_key", "follow"])
AttributeError: 'NoneType' object has no attribute 'register_apis'

I get AttributeError: 'NoneType' object has no attribute 'register_apis' even if I am online. @xeroc

Updating steem seemed to solve the problem
pip3 install graphenelib --upgrade
pip3 install steem --upgrade

actually pip install steem installs a different library than piston.

@Netherdrake Oddly enough, graphenelib didn't update, but steem did, and immediately resolved the following error
AttributeError: 'NoneType' object has no attribute 'register_apis'

steem installs Piston fork, not Piston.


Copy zlib.h to zlib-ng.h

Create initial version of zlib-ng.h by using contents of zlib.h.

Had to do a rebase to fix some conflicts with what has been going into the develop branch lately.
Please rebase and resubmit PR.
Was looking good btw :)


I tried following the instruction on MacOS and get the error described below

I tried following the instruction on MacOS and get the error described below when I ran python -m vtk_reserve in the root directory of the repo after installing pyvista.
(streamlit) JustinGosses_per:vtk_reserves justingosses$ python -m vtk_reserves
Traceback (most recent call last):
  File "/Users/justingosses/anaconda/envs/streamlit/lib/python3.7/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/Users/justingosses/anaconda/envs/streamlit/lib/python3.7/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/Users/justingosses/Code/junk/vtk_reserves/vtk_reserves.py", line 129, in <module>
    usage_gui(__doc__)
  File "/Users/justingosses/Code/junk/vtk_reserves/_gui.py", line 1226, in usage_gui
    AppTk(usage).mainloop()
  File "/Users/justingosses/Code/junk/vtk_reserves/_gui.py", line 2067, in __init__
    self._iconfile = Branding().name
  File "/Users/justingosses/Code/junk/vtk_reserves/_gui.py", line 2191, in __init__
    self._choice = os.environ['USERDOMAIN']
  File "/Users/justingosses/anaconda/envs/streamlit/lib/python3.7/os.py", line 679, in __getitem__
    raise KeyError(key) from None
KeyError: 'USERDOMAIN'

I suspect the problem is with this line of code in https://github.com/pemn/vtk_reserves/blob/main/_gui.py
# images for window icon and watermark
class Branding(object):
  _gc = []
  def __init__(self, f='ICO', size=None, choice=None):
    if choice is None:
      self._choice = os.environ['USERDOMAIN']
    else:
      self._choice = choice

    self._format = f

    self._image = Image.new('RGBA', (800, 800))
    draw = ImageDraw.Draw(self._image)

    if self._choice=='VALENET':
      # Vale logo
      draw.polygon((430, 249, 397,698, 803,160,  766,139, 745,132, 727,130, 692,130, 655,142, 618,160, 571,188, 524,216, 477,236), "#eaab13")
      draw.chord((-80,105, 413,588), 228, 312, "#008f83")
      draw.polygon((0,165, 397,698, 720,270, 454,270, 454,270, 429,248, 328,165), "#008f83")
      draw.chord((403,-40, 770,327), 44, 136, "#eaab13")
    else:
      # open souce logo
      draw.pieslice([40, 40, 760, 760], 110, 70, '#3fa648')
      draw.ellipse([288, 288, 512, 512], Image.ANTIALIAS)

It was looking for the enviroment variable USERDOMAIN which is Windows only. I added a check to avoid this error.


Update Composer dependencies (2024-01-05-00-15)

Visual regression test passed!
View the visual regression test report


fix: throw an error if another base is picked for cidv0

Me and @gozala went through details of CID design, v0 vs v1, what does each piece mean and we came with a lot more clarity from that discussion, you can find the log here:
https://botbot.me/freenode/ipfs/2017-01-21/?msg=79711046&page=1
To avoid further confusion, I changed the behaviour of a CIDv0.toBaseEncodedString to only allow base58, throwing an error that informs the user they need to migrate to v1. Added a test for this

I'm requested as a reviewer here but I don't have enough context/knowledge about CIDv0 vs CIDv1 to be able to approve or deny this. I'll leave this for @dignifiedquire to verify.


grunt-bower-task is the wrong way

Hey @smies
Thank you for this generator.
I tried it and it works well, but the underlying grunt-bower-task just doesn't work in the real world.
The reason for that is not the  grunt-bower-task, but the fact that people have different understandings of the bower.json file.
Example: Bootstrap
Installing bootstrap with grunt-bower-task will create the following Directory:
Directory: assets/vendor/bootstrap
bootstrap.css 						// References a non existing source map
bootstrap.js 						// Do I must use all bootstrap js components?
bootstrap.less						// Useless since references are missing
glyphicons-halflings-regular.eot	// Useless since not properly referenced by .css
glyphicons-halflings-regular.svg	// Useless since not properly referenced by .css
glyphicons-halflings-regular.ttf	// Useless since not properly referenced by .css
glyphicons-halflings-regular.woff	// Useless since not properly referenced by .css

This is just one example why the grunt-bower-task is just not usable.
Proposal: Using bower with sails.js
1. Create a .bowerrc file.
{
	"directory": "assets/bower_components"
}

This tells bower to install all components in the assets folder.
2. Add extra clean task
File: tasks/config/clean.js
module.exports = function(grunt) {

	grunt.config.set('clean', {
		dev: ['.tmp/public/**'],
		build: ['www'],
		bower: ['.tmp/public/bower_components/**']
	});

	grunt.loadNpmTasks('grunt-contrib-clean');
};

3. Modify grunt prod task
We don't want to deploy entire git repos to production.
File: tasks/config/clean.js
module.exports = function (grunt) {
	grunt.registerTask('buildProd', [
		'compileAssets',
		'concat',
		'uglify',
		'cssmin',
		'linkAssetsBuildProd',
		'clean:bower',
		'clean:build',
		'copy:build'
	]);
};

4. Exclude assets/bower_components from the watch task
module.exports = function(grunt) {

	grunt.config.set('watch', {
		options: {
			livereload: true
		},
		api: {

			// API files to watch:
			files: ['api/**/*']
		},
		views: {

			// View files to watch:
			files: ['views/**/*']
		},
		assets: {

			// Assets to watch:
			files: ['assets/**/*' , '!assets/bower_components/**', 'tasks/pipeline.js'],

			// When assets are changed:
			tasks: ['syncAssets' , 'linkAssets']
		}
	});

	grunt.loadNpmTasks('grunt-contrib-watch');
};

Pros/Cons
Pros

Now we can reference all files direct from the git repo. This allows us to pick only the files we need.
Use bower directly without extra layer

Cons

More complex to integrate.

What do you think of this approach?

If anyone has the same issue, this is the right "exportsOverride" of the bower.json to install bootstrap correctly :
  "exportsOverride": {     "bootstrap": {       "js": "dist/js/*.min.*",       "css": "dist/css/*.min.*",       "fonts": "dist/fonts/*.*"     }   }


RegularGridData needs positive spacing

I encountered this in https://github.com/evetion/GeoArrays.jl/blob/master/src/interpolate.jl#L12, where I use the spacing available in the GeoArray. In the case of GDAL created geotiffs, these are always negative for the y direction.
Is there a reason why we don't support negative spacing? In the meantime I guess I can force the spacing to be positive (just taking the abs) for both the RegularGridData and the RegularGrid, which should produce the same results.

That is an interesting question. It seems natural at first to allow negative spacing to mirror the grid, but this can have major impacts in the assumptions we've made in the algorithms. For example, we can always compute the volume of a grid cell when the spacing is positive by simply raising the spacing to the dimension s^N of the grid. In 3D, the formula would produce negative volume for the cell if one of the spacing is negative. This is a simple example, but maybe there are other more advanced used cases that would be more complicated to implement if we allow negative spacing. What do you think?
I wonder if the origin of the GDAL-loaded grid could be shifted to the to lower left origin of the grid without penalties? I don't know to what extent it is easy to generalize the origin of the RegularGrid to some other reference corner without breaking algorithms.

Shifting is possible, but needs a flip of the array itself, which can be costly. Since I use it purely for interpolation, I've made the spacing always positive in https://github.com/evetion/GeoArrays.jl/commit/9b16e9e7c40a18d755afb10fae5c7645b85ec7b2#diff-fca3de692a5cfd93374010b5667e1829R12. This shouldn't affect the interpolation itself, as the distances, neighbors etc. remain the same.
I agree that negative spacing could and will present problems in algorithms. Especially if some implementations assumes positive spacing but quietly allows for negative ones because we changed it here. So let's keep this as it is now.


Build fails on Arch Linux

When building with the instructions in https://github.com/chrxh/alien/issues/100#issuecomment-2308899636, I get the following error.
CMake Error at /usr/share/cmake/Modules/Internal/CMakeCUDAFindToolkit.cmake:104 (message):
  Failed to find nvcc.

  Compiler requires the CUDA toolkit.  Please set the CUDAToolkit_ROOT
  variable.
Call Stack (most recent call first):
  /usr/share/cmake/Modules/CMakeDetermineCUDACompiler.cmake:85 (cmake_cuda_find_toolkit)
  CMakeLists.txt:24 (project)

Building branch v4.10.2 or with the instructions in the README also fails. building with cmake .. -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_COMPILER=gcc-11 -DCMAKE_CXX_COMPILER=g++-11 -DCMAKE_CUDA_COMPILER=/opt/cuda/bin/nvcc, I get
[...]

Call Stack (most recent call first):
  /usr/share/cmake/Modules/CMakeDetermineCompilerId.cmake:8 (CMAKE_DETERMINE_COMPILER_ID_BUILD)
  /usr/share/cmake/Modules/CMakeDetermineCompilerId.cmake:53 (__determine_compiler_id_test)
  /usr/share/cmake/Modules/CMakeDetermineCUDACompiler.cmake:131 (CMAKE_DETERMINE_COMPILER_ID)
  CMakeLists.txt:24 (project)

I am using the Arch CUDA package.

Have you checked archlinux wiki for cuda?
What is the output of nvidia-smi in your case?

Thank you for your reply. I have the read the Arch Wiki article but didn't find a solution. Here is output of nvidia-smi on my system:
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 565.57.01              Driver Version: 565.57.01      CUDA Version: 12.7     |
|-----------------------------------------+------------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id          Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |           Memory-Usage | GPU-Util  Compute M. |
|                                         |                        |               MIG M. |
|=========================================+========================+======================|
|   0  NVIDIA GeForce RTX 4070 ...    Off |   00000000:01:00.0 Off |                  N/A |
| N/A   40C    P8              1W /   85W |      15MiB /   8188MiB |      0%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+

+-----------------------------------------------------------------------------------------+
| Processes:                                                                              |
|  GPU   GI   CI        PID   Type   Process name                              GPU Memory |
|        ID   ID                                                               Usage      |
|=========================================================================================|
|    0   N/A  N/A      1045      G   /usr/lib/Xorg                                   4MiB |
+-----------------------------------------------------------------------------------------+

It is OK to build ALIEN with the newest environment in ArchLinux, if some error appeared, comment the add_compile_options($<$<COMPILE_LANGUAGE:CXX>:-Werror>) in /alien/CMakeLists.txt. In this case, I suggest you using the newest tools and alien project.
Besides, more information could help solving the problem.
Then your error on building is about the cuda compiler path. This should not be an error since it could be identified generally. To find the problem, could you check the path first?
Ensure nvcc is on the right folder:
which nvcc
example:
/opt/cuda/bin/nvcc

Ensure nvcc is installed correctly:
nvcc --version
example:
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2024 NVIDIA Corporation
Built on Tue_Oct_29_23:50:19_PDT_2024
Cuda compilation tools, release 12.6, V12.6.85
Build cuda_12.6.r12.6/compiler.35059454_0

Check if nvcc identified by cmake:
grep -i cuda CMakeCache.txt in the build folder
examples:
//CUDA compiler
CMAKE_CUDA_COMPILER:FILEPATH=/opt/cuda/bin/nvcc
//Flags used by the CUDA compiler during all build types.
CMAKE_CUDA_FLAGS:STRING=
//Flags used by the CUDA compiler during DEBUG builds.
CMAKE_CUDA_FLAGS_DEBUG:STRING=-g
//Flags used by the CUDA compiler during MINSIZEREL builds.
CMAKE_CUDA_FLAGS_MINSIZEREL:STRING=-O1 -DNDEBUG
//Flags used by the CUDA compiler during RELEASE builds.
CMAKE_CUDA_FLAGS_RELEASE:STRING=-O3 -DNDEBUG
//Flags used by the CUDA compiler during RELWITHDEBINFO builds.
CMAKE_CUDA_FLAGS_RELWITHDEBINFO:STRING=-O2 -g -DNDEBUG
CUDAToolkit_CUPTI_INCLUDE_DIR:PATH=/opt/cuda/targets/x86_64-linux/include/../../../extras/CUPTI/include
CUDAToolkit_rt_LIBRARY:FILEPATH=/usr/lib/librt.a
CUDA_CUDART:FILEPATH=/opt/cuda/lib/libcudart.so
CUDA_OpenCL_LIBRARY:FILEPATH=/opt/intel/oneapi/compiler/2024.1/lib/libOpenCL.so
CUDA_cuFile_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libcufile.so
CUDA_cuFile_rdma_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libcufile_rdma.so
CUDA_cuFile_rdma_static_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libcufile_rdma_static.a
CUDA_cuFile_static_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libcufile_static.a
CUDA_cublasLt_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libcublasLt.so
CUDA_cublasLt_static_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libcublasLt_static.a
CUDA_cublas_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libcublas.so
CUDA_cublas_static_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libcublas_static.a
CUDA_cuda_driver_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/stubs/libcuda.so
CUDA_cudart_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libcudart.so
CUDA_cudart_static_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libcudart_static.a
CUDA_cudla_LIBRARY:FILEPATH=CUDA_cudla_LIBRARY-NOTFOUND
CUDA_cufft_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libcufft.so
CUDA_cufft_static_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libcufft_static.a
CUDA_cufft_static_nocallback_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libcufft_static_nocallback.a
CUDA_cufftw_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libcufftw.so
CUDA_cufftw_static_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libcufftw_static.a
CUDA_culibos_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libculibos.a
CUDA_cupti_LIBRARY:FILEPATH=/opt/cuda/extras/CUPTI/lib64/libcupti.so
CUDA_cupti_static_LIBRARY:FILEPATH=/opt/cuda/extras/CUPTI/lib64/libcupti_static.a
CUDA_curand_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libcurand.so
CUDA_curand_static_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libcurand_static.a
CUDA_cusolver_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libcusolver.so
CUDA_cusolver_lapack_static_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libcusolver_lapack_static.a
CUDA_cusolver_metis_static_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libcusolver_metis_static.a
CUDA_cusolver_static_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libcusolver_static.a
CUDA_cusparse_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libcusparse.so
CUDA_cusparse_static_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libcusparse_static.a
CUDA_nppc_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libnppc.so
CUDA_nppc_static_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libnppc_static.a
CUDA_nppial_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libnppial.so
CUDA_nppial_static_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libnppial_static.a
CUDA_nppicc_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libnppicc.so
CUDA_nppicc_static_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libnppicc_static.a
CUDA_nppicom_LIBRARY:FILEPATH=CUDA_nppicom_LIBRARY-NOTFOUND
CUDA_nppicom_static_LIBRARY:FILEPATH=CUDA_nppicom_static_LIBRARY-NOTFOUND
CUDA_nppidei_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libnppidei.so
CUDA_nppidei_static_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libnppidei_static.a
CUDA_nppif_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libnppif.so
CUDA_nppif_static_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libnppif_static.a
CUDA_nppig_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libnppig.so
CUDA_nppig_static_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libnppig_static.a
CUDA_nppim_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libnppim.so
CUDA_nppim_static_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libnppim_static.a
CUDA_nppist_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libnppist.so
CUDA_nppist_static_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libnppist_static.a
CUDA_nppisu_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libnppisu.so
CUDA_nppisu_static_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libnppisu_static.a
CUDA_nppitc_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libnppitc.so
CUDA_nppitc_static_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libnppitc_static.a
CUDA_npps_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libnpps.so
CUDA_npps_static_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libnpps_static.a
CUDA_nvJitLink_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libnvJitLink.so
CUDA_nvJitLink_static_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libnvJitLink_static.a
CUDA_nvToolsExt_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libnvToolsExt.so
CUDA_nvfatbin_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libnvfatbin.so
CUDA_nvfatbin_static_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libnvfatbin_static.a
CUDA_nvgraph_LIBRARY:FILEPATH=CUDA_nvgraph_LIBRARY-NOTFOUND
CUDA_nvgraph_static_LIBRARY:FILEPATH=CUDA_nvgraph_static_LIBRARY-NOTFOUND
CUDA_nvjpeg_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libnvjpeg.so
CUDA_nvjpeg_static_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libnvjpeg_static.a
CUDA_nvml_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/stubs/libnvidia-ml.so
CUDA_nvml_static_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/stubs/libnvidia-ml.a
CUDA_nvperf_host_LIBRARY:FILEPATH=/opt/cuda/extras/CUPTI/lib64/libnvperf_host.so
CUDA_nvperf_host_static_LIBRARY:FILEPATH=/opt/cuda/extras/CUPTI/lib64/libnvperf_host_static.a
CUDA_nvperf_target_LIBRARY:FILEPATH=/opt/cuda/extras/CUPTI/lib64/libnvperf_target.so
CUDA_nvptxcompiler_static_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libnvptxcompiler_static.a
CUDA_nvrtc_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libnvrtc.so
CUDA_nvrtc_builtins_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libnvrtc-builtins.so
CUDA_nvrtc_builtins_static_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libnvrtc-builtins_static.a
CUDA_nvrtc_static_LIBRARY:FILEPATH=/opt/cuda/targets/x86_64-linux/lib/libnvrtc_static.a
CUDA_pcsamplingutil_LIBRARY:FILEPATH=/opt/cuda/extras/CUPTI/lib64/libpcsamplingutil.so
//ADVANCED property for variable: CMAKE_CUDA_COMPILER
CMAKE_CUDA_COMPILER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CUDA_FLAGS
CMAKE_CUDA_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CUDA_FLAGS_DEBUG
CMAKE_CUDA_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CUDA_FLAGS_MINSIZEREL
CMAKE_CUDA_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CUDA_FLAGS_RELEASE
CMAKE_CUDA_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CUDA_FLAGS_RELWITHDEBINFO
CMAKE_CUDA_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDAToolkit_CUPTI_INCLUDE_DIR
CUDAToolkit_CUPTI_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDAToolkit_rt_LIBRARY
CUDAToolkit_rt_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_CUDART
CUDA_CUDART-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_OpenCL_LIBRARY
CUDA_OpenCL_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_cuFile_LIBRARY
CUDA_cuFile_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_cuFile_rdma_LIBRARY
CUDA_cuFile_rdma_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_cuFile_rdma_static_LIBRARY
CUDA_cuFile_rdma_static_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_cuFile_static_LIBRARY
CUDA_cuFile_static_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_cublasLt_LIBRARY
CUDA_cublasLt_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_cublasLt_static_LIBRARY
CUDA_cublasLt_static_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_cublas_LIBRARY
CUDA_cublas_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_cublas_static_LIBRARY
CUDA_cublas_static_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_cuda_driver_LIBRARY
CUDA_cuda_driver_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_cudart_LIBRARY
CUDA_cudart_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_cudart_static_LIBRARY
CUDA_cudart_static_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_cudla_LIBRARY
CUDA_cudla_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_cufft_LIBRARY
CUDA_cufft_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_cufft_static_LIBRARY
CUDA_cufft_static_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_cufft_static_nocallback_LIBRARY
CUDA_cufft_static_nocallback_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_cufftw_LIBRARY
CUDA_cufftw_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_cufftw_static_LIBRARY
CUDA_cufftw_static_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_culibos_LIBRARY
CUDA_culibos_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_cupti_LIBRARY
CUDA_cupti_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_cupti_static_LIBRARY
CUDA_cupti_static_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_curand_LIBRARY
CUDA_curand_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_curand_static_LIBRARY
CUDA_curand_static_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_cusolver_LIBRARY
CUDA_cusolver_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_cusolver_lapack_static_LIBRARY
CUDA_cusolver_lapack_static_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_cusolver_metis_static_LIBRARY
CUDA_cusolver_metis_static_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_cusolver_static_LIBRARY
CUDA_cusolver_static_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_cusparse_LIBRARY
CUDA_cusparse_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_cusparse_static_LIBRARY
CUDA_cusparse_static_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_nppc_LIBRARY
CUDA_nppc_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_nppc_static_LIBRARY
CUDA_nppc_static_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_nppial_LIBRARY
CUDA_nppial_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_nppial_static_LIBRARY
CUDA_nppial_static_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_nppicc_LIBRARY
CUDA_nppicc_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_nppicc_static_LIBRARY
CUDA_nppicc_static_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_nppicom_LIBRARY
CUDA_nppicom_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_nppicom_static_LIBRARY
CUDA_nppicom_static_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_nppidei_LIBRARY
CUDA_nppidei_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_nppidei_static_LIBRARY
CUDA_nppidei_static_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_nppif_LIBRARY
CUDA_nppif_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_nppif_static_LIBRARY
CUDA_nppif_static_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_nppig_LIBRARY
CUDA_nppig_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_nppig_static_LIBRARY
CUDA_nppig_static_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_nppim_LIBRARY
CUDA_nppim_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_nppim_static_LIBRARY
CUDA_nppim_static_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_nppist_LIBRARY
CUDA_nppist_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_nppist_static_LIBRARY
CUDA_nppist_static_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_nppisu_LIBRARY
CUDA_nppisu_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_nppisu_static_LIBRARY
CUDA_nppisu_static_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_nppitc_LIBRARY
CUDA_nppitc_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_nppitc_static_LIBRARY
CUDA_nppitc_static_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_npps_LIBRARY
CUDA_npps_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_npps_static_LIBRARY
CUDA_npps_static_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_nvJitLink_LIBRARY
CUDA_nvJitLink_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_nvJitLink_static_LIBRARY
CUDA_nvJitLink_static_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_nvToolsExt_LIBRARY
CUDA_nvToolsExt_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_nvfatbin_LIBRARY
CUDA_nvfatbin_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_nvfatbin_static_LIBRARY
CUDA_nvfatbin_static_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_nvgraph_LIBRARY
CUDA_nvgraph_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_nvgraph_static_LIBRARY
CUDA_nvgraph_static_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_nvjpeg_LIBRARY
CUDA_nvjpeg_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_nvjpeg_static_LIBRARY
CUDA_nvjpeg_static_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_nvml_LIBRARY
CUDA_nvml_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_nvml_static_LIBRARY
CUDA_nvml_static_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_nvperf_host_LIBRARY
CUDA_nvperf_host_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_nvperf_host_static_LIBRARY
CUDA_nvperf_host_static_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_nvperf_target_LIBRARY
CUDA_nvperf_target_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_nvptxcompiler_static_LIBRARY
CUDA_nvptxcompiler_static_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_nvrtc_LIBRARY
CUDA_nvrtc_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_nvrtc_builtins_LIBRARY
CUDA_nvrtc_builtins_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_nvrtc_builtins_static_LIBRARY
CUDA_nvrtc_builtins_static_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_nvrtc_static_LIBRARY
CUDA_nvrtc_static_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CUDA_pcsamplingutil_LIBRARY
CUDA_pcsamplingutil_LIBRARY-ADVANCED:INTERNAL=1
//Details about finding CUDAToolkit
FIND_PACKAGE_MESSAGE_DETAILS_CUDAToolkit:INTERNAL=[/opt/cuda/targets/x86_64-linux/include][/opt/cuda/lib/libcudart.so][/opt/cuda/bin][v12.6.85()]
_CMAKE_CUDA_LINKER_PUSHPOP_STATE_SUPPORTED:INTERNAL=TRUE

If the only problem is in CMake, you may try reinstall the CMake (uninstall then install), and manually add the cuda path into your terminal configuration file, like .bashrc file.

comment the add_compile_options($<$<COMPILE_LANGUAGE:CXX>:-Werror>)

I have also tried this, but the same compile error occurs.

Ensure nvcc is on the right folder

/opt/cuda/bin/nvcc --version returns the following:
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2024 NVIDIA Corporation
Built on Tue_Oct_29_23:50:19_PDT_2024
Cuda compilation tools, release 12.6, V12.6.85
Build cuda_12.6.r12.6/compiler.35059454_0

Check if nvcc identified by cmake

Interestingly, grep -i cuda CMakeCache.txt only returns this:
//CUDA compiler
CMAKE_CUDA_COMPILER:STRING=/opt/cuda/bin/nvcc
//ADVANCED property for variable: CMAKE_CUDA_COMPILER
CMAKE_CUDA_COMPILER-ADVANCED:INTERNAL=1

For reference, this is the complete compile error for cmake .. -DCMAKE_BUILD_TYPE=Release -DCMAKE_CUDA_COMPILER=/opt/cuda/bin/nvcc.

Since the err.txt contains
CMake Deprecation Warning at external/vcpkg/scripts/buildsystems/vcpkg.cmake:40 (cmake_policy):
  Compatibility with CMake < 3.10 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value.  Or, use the <min>...<max> syntax
  to tell CMake that the project requires at least <min> but has been updated
  to work with policies introduced by <max> or earlier.
Call Stack (most recent call first):
  build/CMakeFiles/3.31.1/CMakeSystem.cmake:6 (include)
  CMakeLists.txt:24 (project)

this warning, could you update the cmake to the newest version and try again?

My installation is on the latest version.
$ cmake --version
cmake version 3.31.2
[...]

This seems to be an issue with the CMakeLists.txt file.

Oh, i've seen the err.txt fully.
The problem here is that your compile tools:
There are reported build issues with (updated: 2024-06-22)
* GCC 12+ (version 11 should work)
* Visual Studio 17.10 (version 17.9 should work)
* CUDA 12.5 (version 12.4 should work)

This is a copy of README.md, may you follow that and adjust the gcc version?

This was one of the first things I tried. Compiling with GCC 11 for example results in the same error.
$ CUDACXX=/opt/cuda/bin/nvcc cmake .. -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_COMPILER=gcc-11 -DCMAKE_CXX_COMPILER=g++-11 -DCUDAToolkit_ROOT=/opt/cuda/bin
[...]
Call Stack (most recent call first):
  /usr/share/cmake/Modules/CMakeDetermineCompilerId.cmake:8 (CMAKE_DETERMINE_COMPILER_ID_BUILD)
  /usr/share/cmake/Modules/CMakeDetermineCompilerId.cmake:53 (__determine_compiler_id_test)
  /usr/share/cmake/Modules/CMakeDetermineCUDACompiler.cmake:131 (CMAKE_DETERMINE_COMPILER_ID)
  CMakeLists.txt:24 (project)


Adding 2-FA Release Note

Description of the change:
Reason for the change:
Link to original source:

Closes #

Hello @Whatthefoxsays,Thanks again for the PR! We appreciate your contribution and look forward to                                              continued collaboration. Thanks!                                             Team SendGrid DX


Update README.md

I propose you some update concerning the display of the Readme, in order to make more clear and markdown conciliant

I propose you some update concerning the display of the Readme, in order to make more clear and markdown conciliant

Awesome, thanks.


Add CLI Relative Path Fallback

In PR #130 we moved the data directory into morpheus/data and installed it with the python package. This required changing some of the default CLI arguments from relative paths like data/labels_nlp.txt to absolute paths like morpheus.DATA_DIR/labels_nlp.txt.
To make it easy for the user to see how to change the labels file, we respecified the default argument value in documentation (i.e. --labels_file=data/labels_nlp.txt). Now that this needs to be an absolute path, the command in the documentation does not work. Adding absolute paths in the documentation is not feasible since this would require very long paths that would change from machine to machine.
Instead, if the user specifies a data file with a relative path, we first check to see if a file exists relative to the current working directory. If it doesnt exist, then we check for a relative file to the current morpheus install. This allows commands from the documentation like: morpheus run pipeline-nlp --labels_file=data/labels_nlp.txt to find the correct path. We only choose the fallback value when no other file is found.
Related to PR #200

Merging this to test with release packages tomorrow.

@gpucibot merge


How to have greaterthan() or lessthan() assertions in Tap

I am bit new to this process as I am migrating some tests back to Tap. I couldn't help but notice there aren't specific assertions for the following to compare numbers. How can I write a similar test for them in Tap. I thought of using t.ok where I can formulate the expression into truthy value for my test but that didn't work out well. I feel I can add some more examples regarding comparisons other than just equal values.
.toBeGreaterThan(number | bigint)
.toBeGreaterThanOrEqual(number | bigint)
.toBeLessThan(number | bigint)
.toBeLessThanOrEqual(number | bigint)

Reference

This could be an ideal solution -  t.ok(inputValue >= outputValue, Values are correct.. Test passed)

I use
t.ok(counter >= 5, `expected ${counter} >= 5`)

I put the value in the message because t.ok() just shows truthy / falsey.

Back to tap? This is the repo for tape.

My bad,


Missing package for RC1 and RC2 for Microsoft.SemanticKernel.Planners.Core

After updating to RC1 or RC2 I've noticed that the package Microsoft.SemanticKernel.Planners.Core has no version for RC. This means that SequentialPlanner is not usable anymore, since if you use the one from beta8 it does not work due to the breaking changes.
I'd like to understand if it is a bug (package publishing went bad) or if the package is really removed from the RC and how we can use the classes originalli in Planners.Core.
To Reproduce
Create a solution, reference Microsoft.SemanticKernel.Planners.Core, try to use sequentialPlanner and it does not compile because it still search IKernel interface.
Expected behavior
In Nuget I'm expecting package Microsoft.SemanticKernel.Planners.Core to be aligned with RC.

Actually if we open the solution we can see that we have only Handlebars implementation of the planner, the one of OpenAi has no test and seems to have no planner.

This is the situation of the tag dotnet-1.0.0-beta8 where we can see that we actually have the old name of the project that actually depends on handlebars.

This suggests me that the project was renamed but no deprecation was done in package in nuget repository leading to this confusion

It seems to be an issue of the Microsoft.SemanticKernel.Planners.Core not just having been published, e.g. the IKernel interface have been removed in the main branch of Planners.Core 2 weeks ago and in the Microsoft.SemanticKernel.Abstractions rc3 published package but Planners.Core beta8 still relies on IKernel and is the latest package available on Nuget.

I can't instantiate StepwisePlanner since kernel.Build() gives a Kernel and not IKernel as required for instantiation.. What is the workaround / packages to use?

Thanks for raising this. Our current plan is to keep the old planners <1.0 because the new ones (Handlebars and FunctioncallingStepwise) perform much better during our internal testing. I will be providing a blog later this evening on the steps required to migrate from the previous planners to the new ones.


C  code failed to compile

What version of Go are you using (go version)?

$ go version

Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (go env)?
go env Output
$ go env

What did you do?

What did you expect to see?
What did you see instead?

Please complete the issue template

check50 cs50/problems/2020/x/mario/less
#include <cs50.h>
#include <stdio.h>
int main(void)
{
int n;
do
{
n = get_int("Height: ");
}
while (n < 8 && n > 1);
for (int i = 0; i < n; i++)
{
for (int j = 0; j < n; j++)
{
if ( i + j < (n-1))
printf("  ");
else
printf("#");
printf(" \n");
}
}

What did you do?
what did you see when you did it?

There isn’t any Go code here, how is this problem related to Go

suggestions not at all?

I’d this problem is unrelated to the use of CGO then it is likely you have raised your issue in the wrong place. Please explain how your problem related to Go or close this issue. Thank you


The second datepicker doesn't close

When open the first datepicker, change the month, then open the second one, and the first doesn't close.
Screenshot:
http://dl3.joxi.net/drive/0004/1007/275439/160113/5826535989.jpg

Thanks for the report.  Looks like this applies to any two pickers on the example page.

This is a limitation of react-onclickoutside, namely the ignore-react-onclickoutside class.  When clicking on another picker, the click doesn't trigger the first picker to close because of the class.

Should be fixed by #319


Add region covering by point and radius

This will be part of the 0.0.2 release once this gets merged.

Test cases were generated against the s2sphere python lib:
import s2sphere

ll = s2sphere.LatLng.from_degrees(40.7033, -73.9881)
radius = 1000
angle = s2sphere.Angle(radius / 6371010.0)
cap = s2sphere.Cap.from_axis_angle(ll.to_point(), angle)

coverer = RegionCoverer()
coverer.max_level = 12
coverer.min_level = 12

cells = coverer.get_covering(cap)

for c in cells:
  print(c.to_token())


Changes to support displaying temperature for the current hour.

Created two new props on the WeatherData model.

CurrentHourlyTemp
CurrentFeelsLikeTemp

Set main window to use the new properties.

In response to https://github.com/rocksdanister/weather/issues/13

I already worked on this 😅
I made the modification on the client side so its abstracted from the UI and also took timezone into consideration.


TypeError: must be real number, not NoneType

Not sure if it's an ESPHome bug, but I get this only with esphome-opentherm. After I restart Home Assistant, the integration fails with this error:
Error setting up entry opentherm for esphome
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 382, in async_setup
    result = await component.async_setup_entry(hass, self)
  File "/usr/src/homeassistant/homeassistant/components/esphome/__init__.py", line 370, in async_setup_entry
    infos, services = await entry_data.async_load_from_store()
  File "/usr/src/homeassistant/homeassistant/components/esphome/entry_data.py", line 228, in async_load_from_store
    infos.append(cls.from_dict(info))
  File "/usr/local/lib/python3.10/site-packages/aioesphomeapi/model.py", line 87, in from_dict
    return cls(**init_args)
  File "<string>", line 16, in __init__
  File "/usr/local/lib/python3.10/site-packages/aioesphomeapi/model.py", line 73, in __post_init__
    super().__setattr__(field_.name, convert(val))
  File "/usr/local/lib/python3.10/site-packages/aioesphomeapi/util.py", line 49, in fix_float_single_double_conversion
    if value == 0 or not math.isfinite(value):
TypeError: must be real number, not NoneType

This is the yaml configuration:
substitutions:
  devicename: opentherm
  upper_devicename: Opentherm

esphome:
  name: $devicename
  platform: ESP8266
  board: d1_mini
  esp8266_restore_from_flash: true

external_components:
  source: github://arthurrump/esphome-opentherm@main

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password
  ap:
    ssid: "${devicename} Fallback"
    password: !secret wifi_password

web_server:
  port: 80

captive_portal:
logger:
api:
  encryption:
    key: <redacted>
ota:
  password: <redacted>

opentherm:
  in_pin: 12
  out_pin: 14
  ch_enable: true
  dhw_enable: true

output:
  - platform: opentherm
    t_set:
      id: t_set
      min_value: 15
      auto_max_value: true
      zero_means_zero: true

number:
  - platform: opentherm
    t_dhw_set:
      name: "Boiler DHW Setpoint"
      auto_min_value: true
      auto_max_value: true
    max_t_set:
      name: "Maximum allowable CH water setpoint"

sensor:
  - platform: opentherm
    rel_mod_level:
      name: "Boiler Relative modulation level"
    t_boiler:
      name: "Boiler water temperature"
    ch_pressure:
      name: "Boiler Water pressure in CH circuit"
    t_dhw:
      name: "DHW temperature"
    t_dhw_set:
      name: "Domestic hot water temperature setpoint"
  - platform: homeassistant
    id: ch_room_temperature
    entity_id: sensor.ble_temperature_a4c1384e0601
    filters:
      # Push room temperature every second to update PID parameters
      - heartbeat: 1s

binary_sensor:
  - platform: opentherm
    ch_active:
      name: "Boiler Central Heating active"
    dhw_active:
      name: "Boiler Domestic Hot Water active"
    flame_on:
      name: "Boiler Flame on"
    fault_indication:
      name: "Boiler Fault indication"
      entity_category: diagnostic
    diagnostic_indication:
      name: "Boiler Diagnostic event"
      entity_category: diagnostic
    dhw_present:
      name: "Configuration: DHW present"
      entity_category: diagnostic
    ch2_present:
      name: "Configuration: CH2 present"

switch:
  - platform: opentherm
    ch_enable:
      name: "Boiler Central Heating enabled"
      mode: restore_default_on

climate:
  - platform: pid
    name: "Central heating"
    heat_output: t_set
    default_target_temperature: 20
    sensor: ch_room_temperature
    control_parameters:
      kp: 0.4
      ki: 0.004
    deadband_parameters:
      threshold_high: 0.3°C       # deadband within +/-0.5°C of target_temperature
      threshold_low: -0.3°C
    visual:
      temperature_step: 0.5 °C

This happens with ESPHome 2023.2.4. Any idea what could trigger that error?

I put some logs and I see that the info dictionary at entry_data.py:228 contains something like:
{'object_id': 'boiler_dhw_setpoint', 'key':<PHONE_NUMBER>, 'name': 'Boiler DHW Setpoint', 'unique_id': 'openthermnumberboiler_dhw_setpoint', 'disabled_by_default': False, 'icon': '', 'entity_category': 0, 'min_value': 0.0, 'max_value': 127.0, 'step': None, 'unit_of_measurement': '°C', 'mode': 0, 'device_class': ''}
Maybe it doesn't like that None value for 'step'?


Improve documentation for IISWebAppDeployment task

Fix some types and improve readability of the parameter documentation

Looks good.. Signing Off


Metamodel entity changes

Proposed changes
Added Attributes for Span Type Retrieval, Inference:
Added attributes for Retrieval and Inference Span Types.
The format used is:(https://github.com/monocle2ai/monocle/blob/2bae8a1443a1958e701396886c1ee12e4539f6f5/src/monocle_apptrace/metamodel/spans/span_example.json)
Updated wrap_common.py:
Modified the wrap_common.py file to include logic for updating attributes related to span type retrieval and inference.
Types of changes
What types of changes does your code introduce to this project?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices apply)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have read the CONTRIBUTING doc
[ ] I have signed the CLA
[ ] Lint and unit tests pass locally with my changes
[x] I have added tests that prove my fix is effective or that my feature works
[ ] I have added the necessary documentation (if appropriate)
[x] Any dependent changes have been merged and published in downstream modules

Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

Include sample json in the description with the new format.

Could you confirm if test samples update is planned in separate PR

Could you confirm if test samples update is planned in separate PR

I have updated testcase in same PR